Related
Hi !
I think that I followed all of the unlocking the bootloader instructions, and then root,
but I am not sure if I have been successful.
I install-superboot-windows.bat with the himem option and all seemed to go well.
but trying to run Torch, just gives me a black SU Request screen.
Is there another way to prove whether I have successfully rooted or not?
for example, 'about information' shows build plus rooted?
Any advice appreciated!
Ofiaich
http://forum.xda-developers.com/showthread.php?t=630021
St.Jimmy!
thanks for your quick reply!
Off for a read before I sleep...
Ofiaich
Go to terminal on your Mac (or whatever it is on PC)
type "adb root"
If you get a message saying it is already running then you are rooted.
thanks cymru,
I will try that,
got a reply from another forum,
"I had the same problem before. It happened to me because I hadnt
Enabled USB debugging, So do that and then run Torch.
It should request superuser permissions and show a screen asking for
it. Just hit always allow and your good to go.
(That should prove your rooted.. if it works, im not sure of any other
ways to tell)"
and it worked... but don't understand why..
Ofiaich
Hi guys,
I used unrevoked2 to root my phone.
I have the Superuser app and everything seems fine.
I wanted to use the patch to see all the app in the market, but when using the terminal from my mac I try to mount, it says permission denied.
I read somewhere that it could be the Superuser app that doesn't work properly. So I tried to update it, but when I download it from the market is says "Package file was not signed correctly ". I tried to follow the instruction in the thread of Superuser but again I can't mount or delete the previous application.
On another forum I read that when the phone is rooted, when rebooting in HBOOT it should say S-OFF, but mine is S-ON.
So the question is, is there something wrong in my rooting? Is there something wrong elsewhere?
im not a big pro but...
isnt unreovked3 is the oldest version that can root a wildfire? Oo
I'm pretty sure that only unrevoked3 works on the wildfire, not unrevoked 2 as they updated it for the wildfire.
Thanks for your reply.
I used unrevoked2 because on their website they say that they are working on same bugs on the 3rd and that is possible to use unrevoked2. Unrevoked3 is not available for download.
I'm looking for the mac version on the internet but I still haven't found. If you have a source it would be helpful.
Looking carefully it seems that I actually used unrevoked3 since I downloaded from here ->unrevoked.com/rootwiki/doku.php/public/unrevoked2
The page says 2 (and there is and advice in a previous page that says that they "have taken the tool down for a short while until we're satisfied") but the source of the download says 3.14. I'm a little bit confused.
Anyway, if I have the Superuser app should be rooted. Or not?
EDIT: I found the unrevoked3 and tried again all the procedure but it doesn't work. I can't patch, I can't delete the old Superuser app, it still says S-ON.
Ok, I have tried every single method to unroot my MT4G and not luck. the only thing I have not tried is through ADB, but for some reason I cannot get it setup correctly (followed the guide too).
I need help rooting this phone. Anyone?
If possible you can also PM me. Thank you in advance.
EDIT: SORRY... wrong section. Please DELETE.
marcos.lennis said:
Ok, I have tried every single method to unroot my MT4G and not luck. the only thing I have not tried is through ADB, but for some reason I cannot get it setup correctly (followed the guide too).
I need help rooting this phone. Anyone?
If possible you can also PM me. Thank you in advance.
EDIT: SORRY... wrong section. Please DELETE.
Click to expand...
Click to collapse
for ADB
Use True_Blue's ADB EZ guide link is in my signature
What type of errors are you getting when you try the other methods.?
neidlinger said:
for ADB
Use True_Blue's ADB EZ guide link is in my signature
What type of errors are you getting when you try the other methods.?
Click to expand...
Click to collapse
I already rooted the phone (3rd time doing it). I just had forgotten to push gfree to data/local file. That was the only thing I was forgetting. Thank you for your help.
As the title says. I'm currently using 1.83 via SBF flash. Today I received a notification to download and install 1.83 OTA. Kinda strange.
My only thought for cause could be that I'm using gingerblur and it changes the build.prop to look as if I'm using 1.57.
Anyone else getting this?
You can use TiBU to freeze updater. there are several 2 post threads that say the exact same thing..
Must have been in threads that weren't created to address this specific issue and didn't have a title to reflect the same
Sent from my MB860 using XDA Premium App
This happened to me also, so today i flashed back to 1.2.6 and redid everything back to 1.8.3. I had Greyblur installed over 1.8.3 priviously and i was getting that pusshed to me so i redid everything and used the 3.1 version of gingerblur and its perfect.
http://forum.xda-developers.com/showthread.php?t=1053057
http://forum.xda-developers.com/showthread.php?t=1064871
WiredPirate said:
http://forum.xda-developers.com/showthread.php?t=1053057
http://forum.xda-developers.com/showthread.php?t=1064871
Click to expand...
Click to collapse
neither one of these are relevant to this thread. If I had asked "How do I make it stop asking me to update?" then, yes, you would be correct. But I didn't, so you're not.
If you re-read the OP, you will notice that I am inquiring if anyone else ALREADY has 1.83, but yet is STILL being pushed update notifications for.... 1.83.
You used the 1.5 gig SBF file for 1.8.3 correct? I'm GingerBlurred 3.1 on the 1.8.3 and it's fine for me.
Typically when I SBF I go at least one update back and do the OTA update instead.
That's right. I did the full 1.87 SBF, not the little upgrade version
This is happening to me as well... BUT I flashed 4.1.5.7 then did the OTA update. After that I rooted with Gingerbreak and enabled sideloading with Gladenable. Anybody have any idea other than TiBu to fix this issue?
I had this same problem. On a whim, I decided to let it try and apply the update. It rebooted, froze. Pulled the battery, put it back in, restarted. Booted to home screen, said "update failed!" Then I went to check for updates (Settings->About Phone) and it said up to date.
I tried allowing the update. It now says "An update is currently being downloaded. You will be notified when the download is complete" When I click the "OK" box it waits awhile and then says "Failed to download update. The update package is not available at this time. No further action is required."
Now a new question... Can anyone here tell me what to freeze in TiBu to stop this "failed to download update" message??
Thanks!
holtenc said:
neither one of these are relevant to this thread. If I had asked "How do I make it stop asking me to update?" then, yes, you would be correct. But I didn't, so you're not.
If you re-read the OP, you will notice that I am inquiring if anyone else ALREADY has 1.83, but yet is STILL being pushed update notifications for.... 1.83.
Click to expand...
Click to collapse
Okay I see you wanted to know if anybody else was experiencing the issue but had no desire to resolve it. Gotcha.
vertigocreative said:
I tried allowing the update. It now says "An update is currently being downloaded. You will be notified when the download is complete" When I click the "OK" box it waits awhile and then says "Failed to download update. The update package is not available at this time. No further action is required."
Now a new question... Can anyone here tell me what to freeze in TiBu to stop this "failed to download update" message??
Thanks!
Click to expand...
Click to collapse
Freeze 'updater'.
Okay... thanks... done... Now is there any good reason I should want to actually try to fix the problem (maybe by re-flashing?) or am I ok just masking the problem with the freeze?... or is it really even a "problem"?
Sorry if these are stupid questions. I really appreciate the help you guys give here.
I'm stock rooted when I restore my back up when trying to unlock it when I type my pin or used swipe code it doesn't authorize it
http://forum.xda-developers.com/nex...y-twrp-2-8-7-0-touch-recovery-t3234976/page21
read that page, others are having same issue
http://forum.xda-developers.com/nexus-6p/general/psa-twrp-backups-lockscreen-security-t3245070 Remove any security before you backup.
Close this thread
ncsuwolfs said:
http://forum.xda-developers.com/nex...y-twrp-2-8-7-0-touch-recovery-t3234976/page21
read that page, others are having same issue
Click to expand...
Click to collapse
I looked and didn't find anything but thanks for the link