If I use the current version of VISIONary (r14) and ONLY temp-root my MT4G, will ANY residual effects be left once I reboot?
I remember when using VISIONary on my MT3G, it seemed to cause permanent changes even though I only used "temp" root.. eventually my phone seemed to have conflicts with apps and it never really "unrooted"
It's my understanding that VISIONary should be completely safe as it does not write to the system partition..?
Please move this to q&a......
From my don't talk about changelog CM7 Glacier
Anyone?? Need some advice here.
$pitacular1 said:
Anyone?? Need some advice here.
Click to expand...
Click to collapse
VISIONary.apk was designed to only be used on the HTC Vision and the HTC Glacier.
Nandroot was designed to be use on the HTC Magic and HTC Dream. and later came the desktop client SuperOneClick.
If i didn't know any better the reason your Magic went FUBAR is because you used the wrong method and installed something that didn't belong.
But to answer your question my wife's phone is temp rooted with VISIONary.apk and she has had zero usability problems after a reboot.
neidlinger said:
VISIONary.apk was designed to only be used on the HTC Vision and the HTC Glacier.
Nandroot was designed to be use on the HTC Magic and HTC Dream. and later came the desktop client SuperOneClick.
If i didn't know any better the reason your Magic went FUBAR is because you used the wrong method and installed something that didn't belong.
But to answer your question my wife's phone is temp rooted with VISIONary.apk and she has had zero usability problems after a reboot.
Click to expand...
Click to collapse
In the modaco forum I read earlier today that someone was having constant reboots from using VISIONary for temp root.
You said your wife's phone "had zero usability problems after a reboot". What about after temp-rooting, but before rebooting? Any issues there?
$pitacular1 said:
In the modaco forum I read earlier today that someone was having constant reboots from using VISIONary for temp root.
You said your wife's phone "had zero usability problems after a reboot". What about after temp-rooting, but before rebooting? Any issues there?
Click to expand...
Click to collapse
Nope she uses it all day everyday.
Thank you, much appreciated.
Temp-Root here I come!
Btw, is she using the latest version (r14) ?
Noticed no problems
I've seen no problems after a reboot with Visionary r14. On another point, I had it originally set to automatically temproot after every reboot, but once I discovered that the programs that Titanium Pro freezes stay frozen after a reboot even if you're not temprooted, I no longer temproot. Have to use it, though, if I want to add/subtract frozen programs.
ecdy said:
I've seen no problems after a reboot with Visionary r14. On another point, I had it originally set to automatically temproot after every reboot, but once I discovered that the programs that Titanium Pro freezes stay frozen after a reboot even if you're not temprooted, I no longer temproot. Have to use it, though, if I want to add/subtract frozen programs.
Click to expand...
Click to collapse
I wonder if that's normal. It was residual root-like effects like that I was wondering about.
neidlinger said:
VISIONary.apk was designed to only be used on the HTC Vision and the HTC Glacier.
Nandroot was designed to be use on the HTC Magic and HTC Dream. and later came the desktop client SuperOneClick.
If i didn't know any better the reason your Magic went FUBAR is because you used the wrong method and installed something that didn't belong.
But to answer your question my wife's phone is temp rooted with VISIONary.apk and she has had zero usability problems after a reboot.
Click to expand...
Click to collapse
On another note, I had previously experimented on my MT3G with Universal Androot which worked perfectly.. it was only later after the 2.2 update that I needed a root alternative as they had patched the exploits Universal Androot used to get root.. VISIONary was a perfect solution. The only problem is it resulted a permanent "partial" root instead of a temporary root or a full perm root. It was still an excellent tool to use for the job though.. nothing went "FUBAR" lol I was still able to SAPPIMG and then manually update to the official Froyo.
I was just curious if I was going to get the same perm root issue with the MT4G, as I have not yet familiarized myself with the process of restoring the 4G to stock although I am aware of PD15IMG.. just haven't read through the specifics. I swear I'm not a total noob I promise.. I've written tutorials on root for the MT3G
Ok, so last night I used VISIONary for temp root only..
Immediately after temp rooting, my phone started acting weird.. syncing extra long, everything was slow (even after the syncing).. it just seemed to be severly affecting the performance of my device.
I don't know if perhaps I have an active app it was having issues working with or what, all I know is without temp root my phone flies 24-7.
Once I rebooted, everything went back to normal. Don't think I'll be using VISIONary anymore
$pitacular1 said:
Ok, so last night I used VISIONary for temp root only..
Immediately after temp rooting, my phone started acting weird.. syncing extra long, everything was slow (even after the syncing).. it just seemed to be severly affecting the performance of my device.
I don't know if perhaps I have an active app it was having issues working with or what, all I know is without temp root my phone flies 24-7.
Once I rebooted, everything went back to normal. Don't think I'll be using VISIONary anymore
Click to expand...
Click to collapse
i guess you are one in a million who have experienced problems with VISIONary.apk.
I guess if you are that bent on rooting you can do it the old fashioned way.
neidlinger said:
i guess you are one in a million who have experienced problems with VISIONary.apk.
I guess if you are that bent on rooting you can do it the old fashioned way.
Click to expand...
Click to collapse
Well last night when I first tried it, I had not enabled USB debugging..
So this morning, I tried it again, but made sure it was enabled the FIRST time lol..
and it's working flawlessly. I guess my initial idiocy caused something.. but it's fine now!
$pitacular1 said:
Well last night when I first tried it, I had not enabled USB debugging..
So this morning, I tried it again, but made sure it was enabled the FIRST time lol..
and it's working flawlessly. I guess my initial idiocy caused something.. but it's fine now!
Click to expand...
Click to collapse
That's cool. Glad to hear it is working.
Related
The only thing I have done to this phone is root.
My phone several times today has had it's screen blacked out and cannot be awoken or used because all buttons on the phone become unresponsive. However, I know the phone is still working because it still receives notifications and I can hear it.
I have to take out the battery to fix this. Has happened about 5 times today.
Anyone else with this issue?
That certainly isn't normal. I would return it.
Also noticed that when using adb that it kicks my phone out after a certain time... something like 1 minute. Does this happen to anyone else?
I often have to do adb kill-server in order to see my device again.
I too have the same problem (though less frequently).
I have a rooted Epic using Joey Krim's method (raidagainstthecage-arm5.bin). I attributed it to the Overclock Widget which I have uninstalled to see if it gets any better. I like that widget for throttling down the CPU while the screen is off.
I guess it is best to start collecting data on this.
Phone was purchased at BestBuy.
Hardware version: D700.0.5
Anyone else seeing similar behavior? How about on a non-rooted Epic?
I was running SetCPU but uninstall the application and it was still happening to me. I have a feeling it has to do with the root method. My girlfriend's phone doesn't have root and it hasn't happened to her at all.
@jspielberg did you root via the one click method or manually with adb?
I rooted via adb.
Other root required apps installed:
Titanium Backup
Wireless-Tether Experimental (adhoc mode only working currently on the Epic it looks like)
Overclock Widget (now removed)
I think that is it for SU needed apps.
jspielburg did you use OS X by any chance to do your root? Couldn't get this thing to connect on windows so used my mac to root.
This happened to me not 30 minutes ago. And I'm 100% sure its root.
Sent from my SPH-D700 using XDA App
volcomjerk said:
jspielburg did you use OS X by any chance to do your root? Couldn't get this thing to connect on windows so used my mac to root.
Click to expand...
Click to collapse
I did indeed use my mac also for root via ADB...
I can't see how that would matter, but it is good data nonetheless.
Very odd. I have not had a single issue with a blackout, or unresponsive buttons after I rooted 11am yesturday. Then again, I removed most of the sprint bloatware, and removed more useless crap from startup. All the rooted app's are working as expected.
antidelldude said:
Very odd. I have not had a single issue with a blackout, or unresponsive buttons after I rooted 11am yesturday. Then again, I removed most of the sprint bloatware, and removed more useless crap from startup. All the rooted app's are working as expected.
Click to expand...
Click to collapse
Yeah everything is working fine. But I went to pick up the phone to make a call and it was dead. Complete blackout screen, not lights. Nothing.
@Fixter that happened to me too.
Everyone having this problem please state how you rooted. I have a feeling the EPIC doesn't like being on ADB through OS X or 64-bit OS's apparently.
I rooted Tuesday morning using Windows 7 32 bit mode, ran cmd as Administrator and followed Joeykrim's manual instructions.
I have had no problems with the screen being able to be turned back on and I have been on my phone performing various tasks for hours at a time.
volcomjerk said:
@Fixter that happened to me too.
Everyone having this problem please state how you rooted. I have a feeling the EPIC doesn't like being on ADB through OS X or 64-bit OS's apparently.
Click to expand...
Click to collapse
I rooted via ADB on 64-bit Ubuntu using joeykrim's method, not a single issue.
Sent from my SPH-D700 using XDA App
ImSoHungry said:
I rooted via ADB on 64-bit Ubuntu using joeykrim's method, not a single issue.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I rooted with One Click Root. Windows 7 32bit.
I rooted using quick root on Windows 7 then did a full reset after I started having problems and still am having problems with the screen not turning on unless I pull out the battery
Is there a way to undo the "one click root" I did from the instructions here on XDA yesterday?
I rooted last night via OSX 64bit and have not experienced this issue. But now i am very afraid...
killahkosha said:
I rooted using quick root on Windows 7 then did a full reset after I started having problems and still am having problems with the screen not turning on unless I pull out the battery
Click to expand...
Click to collapse
Wow, after doing a full reset without root I am not seeing problems yet but this post makes me worried that it's not just related to root or unrelated to root at all.
I did a full reset through the menu on the phone, I haven't tried doing one through the holding volume down while booting method but I will after work
What does that mean? Anyone got that? Could it be the temp root?
myTouch4G (Glacier)
Ok I guess I was the only one. I did another battery pull with a manual root. For some reason visionary doesn't want to root on its own. It always freezes up. I'll just do it myself after ever boot.
Anyway, I'll keep an eye out on my phone to see if it will reboot again on its own. I hope it doesn't!
myTouch4G (Glacier)
Ok I got to bring this post back up! I got another random reset yesterday and today.
Yesterday reset had to do with me watching a video thru RockPlayer I had put on my phone via PC. Right after the video was over it resetted.
Today I had some network issues and that made it reset.
What's going on? Anyone else got any random resets? This is my 5th one since I made this thread. All started after I did that first battery pull...
How do I fix this ...that's if there is an solution.
editted due to not paying att
tiger013,
Ok, I don't get it. I already have permroot. That's if what you're trying to get at.
which version are you using? how did you permroot? did you turn s-off?
I used version r11 to permroot cuz that's the one that was available. Does that have to do with my reset?
My first reset started off when I had visionary from the Market and that was before permroot. But I'm not sure it's visionary. It never resetted until I did my first battery pull. I don't know...
EDIT: Yes S=OFF (Check my sig) and I permroot through this guide. Link below...
http://forum.xda-developers.com/showthread.php?t=834225
sorry i didnt enven look at sig, have you gone unrooted for a while to see if it still happens
tiger013,
Actually no I haven't...
i would try a logcat
someone might be able to tell you whats going wrong or go back to stock and have tmo send ya a new one
Ok, I'll try the logcat and repost in the OP. Thanks for your replies!
sorry i couldnt help ya,
I'm using alogcat and it's taking forever! It's suppose to take this long? Just says reading log, please wait.
MYT4G (Glacier)
get the logcat from the market, run it. then use the phone like you would normally and when it reboots the app will have it.
in every phone I've ever had, if it starts re-setting, you need to get a new phone. It isn't going to get better. It's a loose connection someplace or a bad battery.
I need a clear answer on this one and the right direction to thread if there is one?
Don't think there truly is a "one and right direction", but check this thread out.
I would personally recommend sqlite and making sure that the setting survived a full shutdown and restart.
Pretty sure sqlite doesn't work, but okay.
khaytsus said:
Pretty sure sqlite doesn't work, but okay.
Click to expand...
Click to collapse
As far as I know there's one guy who reported it not working for him. I'd liek to see more datapoints before making up my mind on this.
FWIW, I did the OTAcerts thing on my wife's nook and never got an update from 1.01. I subsequently did sqllite to both and added otacerts to mine (which was on 1.1). Haven't been brave enough to turn on wireless and test if they still hold though for 1.2.
doncaruana said:
FWIW, I did the OTAcerts thing on my wife's nook and never got an update from 1.01. I subsequently did sqllite to both and added otacerts to mine (which was on 1.1). Haven't been brave enough to turn on wireless and test if they still hold though for 1.2.
Click to expand...
Click to collapse
If you do a nandroid backup, you can always get back to the prior status.
Of course, you won't be able to *stay* at the prior status if you ever turn on Wi-fi again if my experience is indicative of anything. It pushed the update to me twice in as many days, despite doing OTA certs and sqlite.
As others have noted, I'm just one data point. But this data point could not stay with rooted 1.01 past Monday. It never gave me the 1.1 update, either. That did seem to be successfully blocked. But after flashing my nandroid backup three times (and even trying a modified build.prop), I concluded I couldn't stop 1.2 unrooting me, so I gave up and loaded CM7 despite the irritating battery issues.
Hi all,
My MS2 has been randomly restarting and was wondering if it (or Android in general) has a way to see what happened directly before the restart, or more helpfully, what actually caused it to restart?
It hasn't restarted on me while I use it, but seems to restart when it's just sitting around and hasn't been used for a while (ranges from 10 mins or a couple hours) - I know it restarts only by the vibrator going off a little as it boots back up.
The phone is running the stock ROM, and I don't recall installing any new apps recently that may be causing it (such as system apps or anything etc, but NFI really).
Any and all help much appreciated!
Edit: "vBulletin Message Sorry, search is temporarily unavailable. Please try again in 20-30 minutes." in before flames.
So I'm not going to read through pages and pages of posts to find one specific issue which may/may not have been asked etc.
mine restarts 4 out of 5 times i reboot, its really annoying
still dont know the cause, does it with both stock and argen2stone, so it seems like hardware
normally it boots properly when its cold
dont know if this has any relevance... but yeah
weird. im using stock 2.2 AsiaRetail firmware and i have never experienced such a problem - random reboots. perhaps you have some sort of very buggy software that you installed, or perhaps you tampered with something after rooting your phone (if you did)? in any case this is very odd, as it should not just reboot out of the blues. do check each and every downloaded software to see if that is the cause.
I don't have the same problem with UK 2.2.2 running on it.
But random restarts do exist when I was using Argen2Stone 1.8, so I don't think this is hardware problem?
agent008my said:
weird. im using stock 2.2 AsiaRetail firmware and i have never experienced such a problem - random reboots. perhaps you have some sort of very buggy software that you installed, or perhaps you tampered with something after rooting your phone (if you did)? in any case this is very odd, as it should not just reboot out of the blues. do check each and every downloaded software to see if that is the cause.
Click to expand...
Click to collapse
actually, my phone was being pretty stubborn when i tried to root it. had to do a few battery pulls cos it never finished rooting, just kept spinning and spinning. Ive done factory restores with sbf's too, didnt seem to fix it?
I had reboots, but only very few. Not worth mentioning but it occured when I restarted the phone once. It seems to be faulty software.
Sent from my MotoA953 using XDA App
scottyn said:
actually, my phone was being pretty stubborn when i tried to root it. had to do a few battery pulls cos it never finished rooting, just kept spinning and spinning. Ive done factory restores with sbf's too, didnt seem to fix it?
Click to expand...
Click to collapse
what do u mean by stubborn when you tried rooting it? if your phone is still rooted, try unrooting it and see if the problem still exists
agent008my said:
what do u mean by stubborn when you tried rooting it? if your phone is still rooted, try unrooting it and see if the problem still exists
Click to expand...
Click to collapse
stubborn in that z4root wouldnt finish no matter how long i left it. took forever, so i had to reset or batterypull. had to do that about 3 times before the process actually finished
might try unrooting it, such a hassle *sigh*
ill get around to it when exams finish
scottyn said:
stubborn in that z4root wouldnt finish no matter how long i left it. took forever, so i had to reset or batterypull. had to do that about 3 times before the process actually finished
might try unrooting it, such a hassle *sigh*
ill get around to it when exams finish
Click to expand...
Click to collapse
I couldn't root stock 2.2 asia retail with z4root. Try superoneclick. It worked for me
Sent from my MotoA953 using Tapatalk
scottyn said:
stubborn in that z4root wouldnt finish no matter how long i left it. took forever, so i had to reset or batterypull. had to do that about 3 times before the process actually finished
might try unrooting it, such a hassle *sigh*
ill get around to it when exams finish
Click to expand...
Click to collapse
u should have used one click when z4 didnt work. i tried z4 several times, and when it just didnt root i tried one click instead. btw it really is no hassle unrooting. just click unroot on z4 if that does solve the problem, try re-rooting it, but use one click instead. i believe ur set has the RageAgainstTheCage loophole sealed too
agent008my said:
weird. im using stock 2.2 AsiaRetail firmware and i have never experienced such a problem - random reboots. perhaps you have some sort of very buggy software that you installed, or perhaps you tampered with something after rooting your phone (if you did)? in any case this is very odd, as it should not just reboot out of the blues. do check each and every downloaded software to see if that is the cause.
Click to expand...
Click to collapse
Yeah I suspect it might be a downloaded app (hoping so anyway) but I dont want to have to uninstall everything or try a trial'n'error uninstallation process as that will take forever.
I was hoping someone would know if there are logs that show kernel panics or last processes run prior to the reboot...
Sent from my Milestone 2 using XDA app
Bump
Sent from my Milestone 2 using XDA app
I was experiencing some stuck and random reboots when I was using 2.2 with my class 10 sd card, so I decided to try the 2.2.2 sbf, and it kept the same behavior, them i saw the thread about problems with high speed cards, and since i saw it i'm using the original card and experiencing no more stuck or reboots.
Sent from my A953 using XDA Premium App
lucasdss said:
...i'm using the original card and experiencing no more stuck or reboots.
Sent from my A953 using XDA Premium App
Click to expand...
Click to collapse
Thanks for the reply, but im still using the SD card that came in the phone
Sent from my Milestone 2 using XDA app
cobo_ said:
Thanks for the reply, but im still using the SD card that came in the phone
Sent from my Milestone 2 using XDA app
Click to expand...
Click to collapse
try using lookout security (free)...just to see if any apps you have downloaded are contain malwares. i also heard such reboots can be caused by external wifi scanning/searching apps.
Thanks I might try lookout and see what it says...is itself trustworthy tho?
Also I dont use wifi and have it disabled.
Can anyone else offer any further suggestions?
Sent from my Milestone 2 using XDA app
bump...anyone know if MS2 has kernel logs or sth to help me narrow down these random restarts?
I didn't meet with random restart problem at all. using uk 2.2. only once it restarts again and again, and that turned out to be caused by my battery.
sometimes when my tombstone is too hot (above 48℃), it will shut down automaticly to cool down itself. and my battery reports a wrong value of current temperature to system sometimes, then cool down mode will be startup and shut down my phone.
Sent from my Milestone 2
cobo_ said:
bump...anyone know if MS2 has kernel logs or sth to help me narrow down these random restarts?
Click to expand...
Click to collapse
Type dmesg and logcat on terminal.
Also, download live dmesg and live logcat from market, they are bootanimations with live logs apearing on the screen. Pro version suports both at the same time.
Sent from my Milestone 2 XDA App
dangpzanco said:
Type dmesg and logcat on terminal.
Also, download live dmesg and live logcat from market, they are bootanimations with live logs apearing on the screen. Pro version suports both at the same time
Click to expand...
Click to collapse
Awesome thanks for this! I wasn't sure what stuff came with android re unix utils so these will come in handy
Sent from my Milestone 2 using XDA app
With stock ROM and all OTAs applied, my G2 picked up a strange behavior recently. It will play one specific music randomly. In most of the time it's triggered by my action (like unlock the phone), sometime it just starts playing even when the screen is shut.
I didn't root my phone and when the music plays, I can find two Music processes. The only way to turn of the music is to silence the phone or power off.
The behavior seems starts from a few days ago when I tried to temp root with Visionary v14. The temp root was failed and give nothing back.
Now I'm stuck. I can't get rid of the behavior. The only way in my mind is factory reset.
Any suggestion on fixing the problem will be appreciated.
if temp root truly failed..then there's nothing to do. either it succeeded or it didn't. its like being pregnant...either you are or you are not. Virus? naaaah
Sent from my obgyn
Thanks for the reply. It's already midnight for you.
I don't think that's the problem either but I didn't root my phone and I already pass the phase of trying all kinds of apps. The few new app I installed are all popular (like launch pro free).
Visionary can quite easily brick your phone, you should stay well away from it if you want root.
-Nipqer
agreed... when i saw that visionary will most likely brick your phone... i headed straight away to the wiki... and oh joy! my phone is permrooted now
———————————————
sent from a phone... 'nuf said
btw... justin bieber sucks
———————————————
Just for the record, there are no viruses on Android. It's not a PC. There are malicious apps, but not viruses in the traditional sense.
Sent from my T-mobile G2 using Tapatalk
also for the record -- steve jobs has absolutely no rights whatsoever to android, it was not stolen. ftw.