HTC VIVID Super User Problems.... - HTC Vivid, Raider, Velocity

So I am a new person and therefor can not post this in the development thread under the forum where I feel it would belong with the other root related questions.... So i followed the SUPER GUIDE to root my phone (Thank you so much Slapshot and PirateGhost, I was beginning to regret not getting a skyrocket until I found your thread). My super user is running into an issue I can not seem to fix.....
Maybe this is simple or maybe I really messed something up....
Basically none of my apps have root anymore (they did at one point and to my knowledge I change nothing...)
When I go to the Super User app to update my binaries and hopefully get any issues resolved I am greeted by the following error message in the update log: "Failed to find currently installed SU binary. Update cannot continue"
Is there a resolution for this? I have not found anyone even running into the same issue on the Vivid.....
A little nervous.... I didnt have near this many issues rooting my ATRIX and modding the living daylights out of that.

Have you checked with Root Checker Basic to see if you even have Root? If you didn't follow the Super Guide step by step your phone could have relocked after you turned your phone off/on.
If it still fails to update you could try SuperUser Update Fixer.

Yes I have check with root checker.
This may be a dumb question but how do I uninstall Superuser? When I go to the typical application management it does not give me the option. I have done an install again to overwrite the files and nothing changed there.
I followed the instructions step by step (though obviously I messed up somewhere...)
Sent from my HTC PH39100 using XDA App

Kraizk said:
So I am a new person and therefor can not post this in the development thread under the forum where I feel it would belong with the other root related questions.... So i followed the SUPER GUIDE to root my phone (Thank you so much Slapshot and PirateGhost, I was beginning to regret not getting a skyrocket until I found your thread). My super user is running into an issue I can not seem to fix.....
Maybe this is simple or maybe I really messed something up....
Basically none of my apps have root anymore (they did at one point and to my knowledge I change nothing...)
When I go to the Super User app to update my binaries and hopefully get any issues resolved I am greeted by the following error message in the update log: "Failed to find currently installed SU binary. Update cannot continue"
Is there a resolution for this? I have not found anyone even running into the same issue on the Vivid.....
A little nervous.... I didnt have near this many issues rooting my ATRIX and modding the living daylights out of that.
Click to expand...
Click to collapse
Interesting... maybe your root didn't stick. We had a little trouble with that before but pirateghost fixed the CWM ROOT zip. You have a working CWM Recovery, correct?
In the superguide, I have a second option for root in case the first doesn't work. In your case, go ahead and try the second option. The one involving the supertool. That should get you perm root. If that doesn't even work, then we might have to put you back to stock and go at it again.
EDIT: BEFORE TRYING THE SUPERTOOL, try flashing the new CWM ROOT VER2 zip from CWM recovery and see if root sticks.

Slapshot, thank you for checking the General Thread, I really do appreciate that. I have tried both methods multiple times since the root failure seeing as so many people said they had to run the methods multiple times to make them stick (this admittedly may be part of the issue). The most recent one has been the CWM ROOT VER2. Still no dice. Is there a method to remove and re install super user? Or am I reading into the error too literally and instead I just basically do not have root.

Kraizk said:
Slapshot, thank you for checking the General Thread, I really do appreciate that. I have tried both methods multiple times since the root failure seeing as so many people said they had to run the methods multiple times to make them stick (this admittedly may be part of the issue). The most recent one has been the CWM ROOT VER2. Still no dice. Is there a method to remove and re install super user? Or am I reading into the error too literally and instead I just basically do not have root.
Click to expand...
Click to collapse
No problem. At this point I think you may just not have root... but first, go ahead and go into bootloader (power off, then power on while holding power and vol down). Does your device say unlocked?

*Just a clarification*
You have to unroot your phone to get rid of it Idk why I put uninstall/reinstall earlier...still out there from last night I guess.

slapshot30 said:
No problem. At this point I think you may just not have root... but first, go ahead and go into bootloader (power off, then power on while holding power and vol down). Does your device say unlocked?
Click to expand...
Click to collapse
Yes the device still says unlocked. That was one of the first things I checked... Haha....
As I said ive flashed the rooted CWM and it says it went over successfully.
If i use the Zerg exploit it still seems to go over successfully (I realize this has a tenancy to mess with internal storage and only provide a temp root but i do not even get that temp root).
How would I unroot my device? Do you mean flash to stock and relock my boot loader?
As I said I have flashed several devices in the past (Atrix, eee pad transformer, HTC Inspire, HTC DINC, SAMSUNG GALAXY S T-Mobile) but I am not completely up to date on all of the technical terms...

Kraizk said:
Yes the device still says unlocked. That was one of the first things I checked... Haha....
As I said ive flashed the rooted CWM and it says it went over successfully.
If i use the Zerg exploit it still seems to go over successfully (I realize this has a tenancy to mess with internal storage and only provide a temp root but i do not even get that temp root).
How would I unroot my device? Do you mean flash to stock and relock my boot loader?
As I said I have flashed several devices in the past (Atrix, eee pad transformer, HTC Inspire, HTC DINC, SAMSUNG GALAXY S T-Mobile) but I am not completely up to date on all of the technical terms...
Click to expand...
Click to collapse
Yes, I mean relock the bootloader and back to stock rom, then try again. Do you know how to get back to stock?

slapshot30 said:
Yes, I mean relock the bootloader and back to stock rom, then try again. Do you know how to get back to stock?
Click to expand...
Click to collapse
actually that one I do not know how to do... I realize this is probably somewhat annoying because I am sure you have said how to do it before.... Some help would be greatly appreciated

Kraizk said:
actually that one I do not know how to do... I realize this is probably somewhat annoying because I am sure you have said how to do it before.... Some help would be greatly appreciated
Click to expand...
Click to collapse
I haven't told anyone how to do it surprisingly, and I'm more than happy to help . I was honestly thinking about adding reverting back to stock to the superguide, and I think I just may do that. Here is the link. Pirateghost is the man.
http://forum.xda-developers.com/showpost.php?p=20821226&postcount=4

Thank you for this and all of your help, people like you and ghostpirate are why i still feel like I can turn to the XDA community. I will try this firs thing in the morning and give an update on how things went. I would try it tonight but lets be honest, its the 1st of the year and the last thing I need to be doing is messing with technology.....

Kraizk said:
Thank you for this and all of your help, people like you and ghostpirate are why i still feel like I can turn to the XDA community. I will try this firs thing in the morning and give an update on how things went. I would try it tonight but lets be honest, its the 1st of the year and the last thing I need to be doing is messing with technology.....
Click to expand...
Click to collapse
It's no problem, this isn't a dumb question or easy issue by any means. If the method I directed to you doesn't work, let me know. There is another way to do it without all the code.

slapshot30 said:
I haven't told anyone how to do it surprisingly, and I'm more than happy to help . I was honestly thinking about adding reverting back to stock to the superguide, and I think I just may do that. Here is the link. Pirateghost is the man.
http://forum.xda-developers.com/showpost.php?p=20821226&postcount=4
Click to expand...
Click to collapse
Worked perfectly. I flashed it back to stock using the thread you linked me to. Then I did the CWM Root method and so far so good. I appreciate all of your help

Nice, I'm glad you were able to get everything working.
Sent from my HTC PH39100 using xda premium

Related

Reset to new

So i rooted my phone using the universal root in this forum, the day after i accidentally updated android and it broke the root, also i have noticed some bugs. I am trying to put the phone back to how it was when i got it in the post. i tried a "factory data reset" but it didnt do what i am trying to do, just deleted all the apps etc. Any ideas how i can do this? I dont mind if i have root access still.
Cheers!
Read my signature, the bigger link. I'm sure you'll find the info on rooting FRG83 there (because I've put it there).
Okay i think i need some help, i have downloaded the official rom an put it on the sd card but cant work out how to flash it, im holding down the track ball and resetting but cant see the option to flash anything, is this because it wasnt rooted properly where android updated?
this sux on an epic scale. when my phone was ****ed.. no one posted with a signature that had information about how to install stuff to phone without unlocking bootloader .
grrr...
dude read the wiki... its all there
Ive been reading this tutorial: /showthread.php?t=614850 but not sure how to run the commands on steps 8 - 13
To make it even easier, these are the words you need to concentrate on looking for:
Jack_R1 said:
rooting FRG83
Click to expand...
Click to collapse
I supposed my post would say it clearly enough that your idea of restoring the ROM to the older version won't work.
Just managed to root it, then got totally lost, might have to leave it like this..
Yes, that was the idea. Root it, and stay with it. If you post the bugs, they might have solutions / workarounds.
Plus, it might be a good time to try custom ROM Or even customized plain FRF91 you were looking for.

Please help. Phone not bricked but cant root

Good Evening everyone. As the title says i need help.
I have had my phone rooted fine in the past but went ahead and did the .893 update wich is where something went screwy. It booted fine after doing the .893 update however after doing a reboot it would not boot. just stayed at the M dual core. I think something went wrong on the update because all my apps were still there when it did boot.
So i tried doing a return to stock using the RSD lite program..that fails right away no matter what i do.
So i went and tried to do the One click fastboot system restore program.
Now when i did that the INFOpreflash validation failure showed up however everything else went through fine. the phone reboots and everything works just not great the signal strenght is very low.
The version that got installed says 5.5.1_84_dbn-55. So i try Pete's root method and it go thru to step 2 but then fails at rebooting for the second time saying it could not get root via local.prop.
If anyone could please help me get back to normal stock it would be much appreciated
Not to be a jerk, but did you READ any thread on here before you did this??
1) Unless you used p3droid's forever root method, you're done. No root.
2) Wrong forum - should be in general
3) RSD won't work.
4) I don't feel sorry for you. You should have researched more. If you would have taken the time to read a few threads, you would have known the answers before you did this.
Enjoy your new build - you'll be with it for awhile.
Sent from my DROID BIONIC using xda premium
P.S. You are stock now.
Sent from my DROID BIONIC using xda premium
harsh, but true...has nobody heard of google...?
Sent from my DROID BIONIC using XDA App
dubsx said:
harsh, but true...has nobody heard of google...?
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
Or XDA?
Sent from my DROID BIONIC using xda premium
I did do the forever root and i did read that thread three times b4 i attempted it. I know i am stock. I checked the mount_ext3.sh file and those three lines are no longer there.
And i also have googled this but cannot find an answer hence why i am asking on here..all options i have found to try to reroot have failed
that too, haha...
Sent from my DROID BIONIC using XDA App
Sidewind75 said:
I did do the forever root and i did read that thread three times b4 i attempted it. I know i am stock. I checked the mount_ext3.sh file and those three lines are no longer there.
And i also have googled this but cannot find an answer hence why i am asking on here..all options i have found to try to reroot have failed
Click to expand...
Click to collapse
Well, you didn't list that in the OP.
At this point, I don't know. Here is all I got: enter stock recovery and wipe everything. Reboot. Cross your fingers.
Sent from my DROID BIONIC using xda premium
mistawolfe said:
Not to be a jerk, but did you READ any thread on here before you did this??
1) Unless you used p3droid's forever root method, you're done. No root.
2) Wrong forum - should be in general
3) RSD won't work.
4) I don't feel sorry for you. You should have researched more. If you would have taken the time to read a few threads, you would have known the answers before you did this.
Enjoy your new build - you'll be with it for awhile.
Sent from my DROID BIONIC using xda premium
Click to expand...
Click to collapse
Not to be a jerk...(goes on to be a jerk)
I love when people preface their statements with stuff like "I'm not racist BUUUUTTT". It's like a contrition...but in reverse!
quentin0 said:
Not to be a jerk...(goes on to be a jerk)
I love when people preface their statements with stuff like "I'm not racist BUUUUTTT". It's like a contrition...but in reverse!
Click to expand...
Click to collapse
Sometimes the truth hurts. He messed up. Don't shoot the messenger.
Moderator Message
Breathe in, breathe out!!!!
I'll breathe when this .893 goes through and I keep root
There is also some very seriously contradictory info in the OP. While castigating him for being a noob did anyone notice that he claims to have flashed the update and then reverted to stock?
This is impossible from our current understanding of how the bootloader works.
More information about the exact steps followed and the exact results at each step would be very helpful to try and figure out what really happened.
OK?
Less heat and more light...
I just got a little frustrated, as every time I open XDA today I see the same/similar post.
Cell - I didn't see in the OP where he said he flashed back. I read where he tried, but I didn't see any mention of 896.
I could not get the .893 to boot after a reboot so i used the One-click fastboot restore and root which brought back to stock but also made it so that i can no longer root. It fails every time on the local.prop process saying adb could not get root access. I did try the stock recovery and still no go. I also tried the adb fix that was posted to remove local.prop but when i tried it says file not found. I have rooted and messed with many phones in the past from Droid 1 and up and this is the first problem that i couldnt solve so as i said any help would be appreciated.
Oh and i have also tried to unroot it..it also fails at adb not being able to gain root access
Sidewind75 said:
I could not get the .893 to boot after a reboot so i used the One-click fastboot restore and root which brought back to stock but also made it so that i can no longer root. It fails every time on the local.prop process saying adb could not get root access. I did try the stock recovery and still no go. I also tried the adb fix that was posted to remove local.prop but when i tried it says file not found. I have rooted and messed with many phones in the past from Droid 1 and up and this is the first problem that i couldnt solve so as i said any help would be appreciated
Click to expand...
Click to collapse
This isn't going to help your current issue, but how long did you let it sit (after installing 893) before you decided it wouldn't boot? I ask because the guy who was ballsy enough to do it here said the first boot takes about 7 minutes.
EDIT: Nevermind - mine booted in 2 minutes.
it was fully booted and operational. i just did a power off after a half our or so and power back on and it just sat at the M dual core screen...i dont know why it would not boot. I tried pulling the battery. taking out the sim card and all that. the only thing that would get it booted was the One-click fastboot restore and root program so I at least have a working phone but for some reason the signal strength is horrible
Sidewind75 said:
it was fully booted and operational. i just did a power off after a half our or so and power back on and it just sat at the M dual core screen...i dont know why it would not boot. I tried pulling the battery. taking out the sim card and all that. the only thing that would get it booted was the One-click fastboot restore and root program so I at least have a working phone but for some reason the signal strength is horrible
Click to expand...
Click to collapse
Try to do the fastboot again and root it through there. Or, if you did that already (root in fastboot restore) try rooting afterwards.
Might sound dumb, but did you forget to save the chmod changes to the build file? It's a fairly easy mistake and it is the only thing I can think of.
tghockey07 said:
Might sound dumb, but did you forget to save the chmod changes to the build file? It's a fairly easy mistake and it is the only thing I can think of.
Click to expand...
Click to collapse
yes I did and i checked it twice after making sure root explore was closed reopened and checked the file the chmods where there...but now they are not. and seeing as how i cant root i cannot get them back on it

[Q] Cannot figure out how to root phone AAAARRRGGG!

OK. I started out this adventure to root my phone because I want to use it as a wifi hotspot for my Ipad and not pay AT&T $50/month for that "privelage." I can't figure it out!!!
Phone Info. - Samsung Captivate with Froyo kb2 build. It has the 2.1 adroid when I got it then I updated to 2.2 through the Keis program when it was available.
Before anyone starts with "read and search" lecture, I'll tell you that I've been on this site for a combined 9 hours reading and searching and nothing seems to work. I've tried one-click root programs, I've installed a rooted version of my stock ROM, Ive downloaded more apps, files, or software programs than I can remember. I know how to get the phone into download mode and I know how to boot into recovery mode, but nothing works. Everything seems to come back to the 3e Recovery I have because when I think I am almost there, I get a failed signature error.
I tried the 3e Recovery Mod and that didn't seem to do anything. Is anyone out there willing to help me through this? I am not a programmer, and I don't have any android experience whatsoever, but I can follow direction and am willing to learn. Everytime I find a new thread I seem to get more confused because I'm unclear on the jargon being used, or the thread is on a different ROM or phone so I don't know if it will work. I know "brick" is a bad thing so I don't want to do that.
I any of the experts had my phone what would you do? Do you need more information from me? Also, once I get this figured out, I'de love some recomendation on a better, faster ROM to install.
ANY HELP WOLD BE GREATLY APPRICIATED. Sorry for the frustration.
When I was on the Official Froyo 2.2 the first thing I used to successfully get root was this... View attachment SuperOneClickv1.6.5-ShortFuse.zip
This version was the only one at the time that would work. Extract it and run the SuperOneClick application. Be sure to have the usb debugging on.-- Menu /Settings /Applications /Development /then check the USB debugging.
Hmmmm.....very odd. Froyo is super easy.
Do you have Super User showing up in the apps drawer?
AND DON'T USE KIES ANY MORE FOR UPDATING !! YOU CAN BE IN FOR NASTY SURPRISES.
Been there. I'll try it again, but I think it still can't get around the 3e verification stuff. I'll let you know.
No SuperUser as of yet. I guess that is the point. Once I get rooted, I should get SuperUser status.
DaytonGuy said:
Been there. I'll try it again, but I think it still can't get around the 3e verification stuff. I'll let you know.
Click to expand...
Click to collapse
That requires a custom kernel
*Get Chance and Luck*
DaytonGuy said:
No SuperUser as of yet. I guess that is the point. Once I get rooted, I should get SuperUser status.
Click to expand...
Click to collapse
After u try the SuperOneClick from my previous post, reboot ur phone and then see what u have.
After nearly 9 hours of trying...I have cracked this thing. Turn out there were two threads about the 3e recovery mod. I tried the manual thread with no success. I just found this one that has a one click script to do it.
http://forum.xda-developers.com/showthread.php?t=833423
Once I did that, I used Captivate One Click Root and presto....I now have SuperUser permissions. Sweet.
Thanks to everyone that responded to my questions. I'm sure I'll have more about ROMs and such.
^ Good deal. Glad u got it.
I figured I would be back.
Anyone have a link to a clear explaination on how to CID unlock the Captivate? A video would be fantastic, but I know how that goes. Also, is there a way to tell if it is unlocked or not?
Thanks
DaytonGuy said:
I figured I would be back.
Anyone have a link to a clear explaination on how to CID unlock the Captivate? A video would be fantastic, but I know how that goes. Also, is there a way to tell if it is unlocked or not?
Thanks
Click to expand...
Click to collapse
Maybe this: http://forum.xda-developers.com/showthread.php?t=872455
If you want to go with this - BACK UP YOUR nv_data.bin TO YOUR COMPUTER as soon as you can. DON'T LEAVE IT ONLY ON THE PHONE !!!!
Or have you heard of Samsung Tool v10.7...... here: http://forum.gsmhosting.com/vbb/f45...orld-just-one-more-revolution-update-1327536/
Register and go to "Download Area"
Jesus....tht will have to wait. That looks pretty complicated..... lol
I'll see what I can do later this week.
Thanks!
Galaxy s unlock in the market.
Use the option to back up, then after copy the galaxys unlock folder on your sdcard to your PC someplace safe...
Galaxy s unlock in the market.
Use the option to back up, then after copy the galaxys unlock folder on your sdcard to your PC someplace safe...
Click to expand...
Click to collapse
I tried that early on because it looked so easy. All I get is "Sorry, no codes found unknown error" Is there a way to tell if I'm CID unlocked or not? I haven't done that yet that I know of. I did click the unlock button is Super One Click, but it did nothing. By that I mean the program, nor the phone seemed like anything happened. Early on in this process I found the completly rooted version of my stock Froyo 2.2 and installed that on my phone thinking that it would root the phone. Later realized it doesn't work like that. How do I check the CID lock? I'de like to try one of these cool ROM's I keep reading about.
unless you are planning on running the captivate on another carrier, you dont need to unlock it.
I was under the impression that I needed to CID unlock the phone to flash any ROM not produced or signed by the carrier. I thought SIM unlock was what allowed you to take the phone to another carrier?
As you can see, I know enough to be dangerous, but I'm slowly learning.
DaytonGuy said:
I was under the impression that I needed to CID unlock the phone to flash any ROM not produced or signed by the carrier. I thought SIM unlock was what allowed you to take the phone to another carrier?
As you can see, I know enough to be dangerous, but I'm slowly learning.
Click to expand...
Click to collapse
CID unlocks do not apply to Samsung phones.
once you have a kernel that has CWM built into it, you can start flashing. nothing else required. you dont even need root if you arent planning on using something like titanium backup before you flash.
Cool.
So any recomendations on my first custom ROM install?
I tried installing a custum boot animation last night and had no luck. I used CWM to flash the file I downloaded, but no change. I tried to copy a new customanimation.zip (I think that's what it's called I'm going from memory here) but I don't have RW access to the System folder. I tried using CWM to mount system and then fix permissions through recovery mode, but that doesn't do it. I'm using Droid Explorer to copy the file but it won't copy. There is a customamination.zip file in system/media so I tried to rename it .zp and it won't take. I assume that is a permissions thing.
I guess I'll try Root Exploer from the market. People seem to be having luck with that.
you cant use a bootanimation.zip on a stock kernel. It just be enabled in a custom kernel.
Go read some more bro. A LOT MORE.
OK. so it looks like I downloaded a custom animation zip file, but I need to flash a kernel that allows me to use the anmation. I ran across a post about that so I can find it.
Was was confusing to me was the uploader of the animation called it "flashable" so I thought that was the kernel and all, but I'm now guessing that by flashing it it simply installed it into the system/media folder for me???
Still looking for any suggestions for my first ROM.

Anyone working on a root for Zv8?

New Revo won't work with A I O, can't stand the bloat someone tell me please. Is anyone working on a root for this POS update.
oh im sure
im sure MT is on the job, but im sure a lil donatin to him would motivate him a lil.... but yeah anyway the thread "keep root through zv8" or whatever is still the only way that the general public knows about... but im sure u already knew that.
I figured as much about MT, (your the man) but i ask because my old revo worked fine with his AIO and maintain root method, but the new one i got that came pre-loaded with Zv8 wont, even after flashing several times back to zv7 and so on.
If you're readin this MT i am to poor to donate money but im willing to be a guinea pig. lol
HighLimit said:
I figured as much about MT, (your the man) but i ask because my old revo worked fine with his AIO and maintain root method, but the new one i got that came pre-loaded with Zv8 wont, even after flashing several times back to zv7 and so on.
If you're readin this MT i am to poor to donate money but im willing to be a guinea pig. lol
Click to expand...
Click to collapse
There is something you aren't doing right even if on ZV8.. You can downgrade to ZV7, then Root only with the original AIO, then create the local.prop file then download the update, then use the 2nd AIO to maintain root, install CWM, then Broken Out.
I'm inclined to believe you because aio worked the first time but then zv8 would fail to regain root and install cwm it would say failed to find path, then flashing back with .tot to zv7 and even doin a factory reset back to stock and trying again now aio won't even root zv7 it just says failed to find path and runs through real quick, if you have any suggestions I would appreciate them.
And by the first time I mean I flashed back to zv7 rooted, flashed maintain root then ota updated then zv8 aio would fail
I have tried many processes over and over again and can recall once the first all in one wouldn't root my phone. I just did a factory reset then after reboot ran the lg-setup then flashed the v7.tot again then was able to root only after that reboot.
If that doesn't work, I don't know what will but good luck
Yah tried that, no luck, well see what mt comes up with. This is a new recertified phone and it has some wierd usb issues, everytime I reflash I have to reboot to be able to use change usb connection, plus now when flash tots I dont lose phone settings like I used to,
i have money!!!!
LaggyWizard said:
im sure MT is on the job, but im sure a lil donatin to him would motivate him a lil.... but yeah anyway the thread "keep root through zv8" or whatever is still the only way that the general public knows about... but im sure u already knew that.
Click to expand...
Click to collapse
Money is something I have, root, I do not. It sounds like MT is the man when it comes to rooting. I would be glad to make a sizeable donation thru pay pal if I knew it would go directly to helping me game root access for my lg revolution running zv8.
See I would do the downgrading option everyone is talking about but those methods are only for pc ( I mean those download files ). I run a mac.
But seriously, I would love to have root. I used to use an iphone and was always jailbreaking. I love having that type of access so any help would be awesome!!
HighLimit said:
Yah tried that, no luck, well see what mt comes up with. This is a new recertified phone and it has some wierd usb issues, everytime I reflash I have to reboot to be able to use change usb connection, plus now when flash tots I dont lose phone settings like I used to,
Click to expand...
Click to collapse
That means nothing. I flash TOT's all the time and never loose settings or apps.
As for MT developing a root process for this phone, while I appreciate all the work he has put into this phone and his skill set, what he does and what root exploiters do are two entirely different things. MT is just gracious enough to create easy to use AIO scripts for everyone to use. I do not see a new root process coming unless another exploit is found and works on this phone.
If I am incorrect about this then MT can feel free to correct me.
Haxcid said:
That means nothing. I flash TOT's all the time and never loose settings or apps.
As for MT developing a root process for this phone, while I appreciate all the work he has put into this phone and his skill set, what he does and what root exploiters do are two entirely different things. MT is just gracious enough to create easy to use AIO scripts for everyone to use. I do not see a new root process coming unless another exploit is found and works on this phone.
If I am incorrect about this then MT can feel free to correct me.
Click to expand...
Click to collapse
+1 For root all I have found is the exploit for keeping root through the update. As for writing a fresh exploit, there are a couple of guys that specialize in it. Jcase and djrbliss are 2 of the best around. The only problem I see is that zv8 has 0 access to the data partition without root, and so what other partitions are blocked. That is why the spectrum version does not work right off of the bat.
Sent from my VS920 4G using Tapatalk 2
Haxcid said:
That means nothing. I flash TOT's all the time and never loose settings or apps.
As for MT developing a root process for this phone, while I appreciate all the work he has put into this phone and his skill set, what he does and what root exploiters do are two entirely different things. MT is just gracious enough to create easy to use AIO scripts for everyone to use. I do not see a new root process coming unless another exploit is found and works on this phone.
If I am incorrect about this then MT can feel free to correct me.
Click to expand...
Click to collapse
nevermind, just had to push cwm through adb still don't know why aio zv8 failed oh well im good now, and mt thanks for debloating and debingin. lovin broken out
Well I THINK I have found WHY I cant OTA ZV8
OK. I have found somthing interesting. I have 2 Revos. BOTH are now in test mode for reasons I am to embarrased to go into. (dang Noob screwups)
ANYWAY I was playing around in LGNPST last night and discovered the Warranty Date (assuming Expiration) on one phone was 4/4/12 Ironicly the same day I unbricked it using the Phonebook emergency recovery. (what puts the the phone in test mode. )
BOTH phones are flagged in my Verizon account (VZW online) as NON VZW Phones. (even though they originally were)
I am starting to think that when you do an emergency recovery you flag not only test mode but the warranty date & some Verizon flag as well. So while the phone is functional ALL Verizon support goes Bye Bye (I.E. OTA updates) EVEN if you flash back to Stock. I know that none of my old Not so smart phones will update past the Warranty date, I suspect this might be somthing similar.
Can anyone VERIFY this? I can SEE the potential problem but my skills stop there. (for now.) Can anyone tell me how I might be able to dig deeper?
I'd be happy with a rooted ZV8, let alone broken out, at this time.
I dont think anyone has figured a way around test mode yet except flashing back to zv4.
If it doesn't boot after flashing .tot:
1. Pull Battery and replace
2. push power and down until you get option to wipe
3. press power to confirm and reboot.
you will be stuck in zv4 and any flashing forward after that will put you back in test mode but at least you will be able to use your phone like normal until someone figures this out, but from what I read it appears improbable.
Yeah not looking good. Test mode I can live with it's the other issues thats killing me.
Sent from my Gingervolt'ed Revolution using the XDA app.
I would like to see this happen but i am poor lol. Well i wouldnt mind sticking around for a root for V8 i dont mind waiting its just i dont want to downgrade and loose everything on my phone. I would not mind being a beta tester either for it I would just like to root my damn phone.
ch4d said:
I would like to see this happen but i am poor lol. Well i wouldnt mind sticking around for a root for V8 i dont mind waiting its just i dont want to downgrade and loose everything on my phone. I would not mind being a beta tester either for it I would just like to root my damn phone.
Click to expand...
Click to collapse
If you downgrade to Zv7 so you can root install cwm and eventually get to rooted Zv8 you will not lose anything on your phone if you do it correctly.
Just Flash the Zv7 Tot and use mt's AIO method, (stopping short of broken out)
if done correctly you will lose nothing.
Google LG_Esteem_root_v2_windows
Sent from my LG-MS910 using XDA

Nexus 6 bootloop when updating to android 5.1

Hey everyone I'm looking here as my last resort before sending my phone back to Motorola.
Bought a Nexus 6 from motorola uk which was delivered yesterday, switched phone on and all the Google apps on the phone updated, then had a notification OTA to download and install android 5.1 which I did, towards the end of the install process I had an error with the green android and a red exclamation mark.
I powered the device off with the power button and it turned back on and ever since it says "Android is starting" "Optimizing app 1 of 125" once it goes through all the apps it gets to the android boot screen then just goes back to the "Android is starting" "Optimizing app 1 of 125" over and over and over. (Infinite bootloop)
Pointers: The phone is not unlocked or rooted as I'm a noob its just fresh out the box, also I never opened/unlocked the developer options.
I have tried various recovery mode fixes, wiping cache and wiping all data and then rebooting the device with no luck.
Is there anyway I can hook my N6 up to my computer and fix this with a tool kit etc? I'm willing to try but I'd need basic instructions and reassurance it wouldn't muck up my warranty if it didn't work as my only other option is to exchange for a new device.
I'm a noob so I need detailed basic step by step instructions.
Any help, advice etc would be hugely appreciated. Thanks
Just send it back, no point messing about with it if it brand new could down to a fault with the hardware itself.
ixon2001 said:
Just send it back, no point messing about with it if it brand new could down to a fault with the hardware itself.
Click to expand...
Click to collapse
Iv'e heard this is a common problem with the N6 whilst trying to update the OTA 5.1 I had no other apps on the phone it was fresh, I did nothing wrong, I know someone who has been through 4 devices with the same bloody issues! In the end he had to sideload 6.0 and I'm not confident in being able to do that.
Well best bet is to download wugfresh toolkit 2.10 i think is the latest version, follow the instructions carefully because first you need to unlock the bootloader then flash 6.0.1 which has just come out.
Using Wugfresh is the best way to go if your new to flashing & you can't really go wrong with it.
ixon2001 said:
Well best bet is to download wugfresh toolkit 2.10 i think is the latest version, follow the instructions carefully because first you need to unlock the bootloader then flash 6.0.1 which has just come out.
Using Wugfresh is the best way to go if your new to flashing & you can't really go wrong with it.
Click to expand...
Click to collapse
I`am sure most xperienced users (me included) will not agree with you The best way to unlock, flash and root is still adb/fastboot. Especialy for lesser xperienced users that are lost is something goes wrong while using the toolkit, wich happens frequently btw. Just check the help threads.
gee2012 said:
I`am sure most xperienced users (me included) will not agree with you The best way to unlock, flash and root is still adb/fastboot. Especialy for lesser xperienced users that are lost is something goes wrong while using the toolkit, wich happens frequently btw. Just check the help threads.
Click to expand...
Click to collapse
Lol it's not rocket science using adb, been doing that way for years but for somebody that never flashed, rooted ect I still think the toolkit best way to go at first because everything is done for you at a click of a button.
Yes things can go tits up when using toolkits, mainly because they don't follow simple instructions.
ixon2001 said:
Lol it's not rocket science using adb, been doing that way for years but for somebody that never flashed, rooted ect I still think the toolkit best way to go at first because everything is done for you at a click of a button.
Yes things can go tits up when using toolkits, mainly because they don't follow simple instructions.
Click to expand...
Click to collapse
Lets agree to disagree
OK
ixon2001 said:
Yes things can go tits up when using toolkits, mainly because they don't follow simple instructions.
Click to expand...
Click to collapse
No, but because toolkits are always behind at least one version with marshmallow. People kept bricking their devices with toolkits when marshmallow came out and they thought they could root it. As 6.0.1 came out they'll do something else wrong.
Toolkits are not help. It's the lazy way if everything is already working and up to date.
Also what can a toolkit do if this phone doesn't even have developer options turned on? If it's in boot loop, as the OP said, then the Enable OEM unlocking was never set, then the only solution is to send it back. Unless there's a toolkit magic we don't know about.
Sent from my Nexus 6 running cyosp using Tapatalk
istperson said:
N
Also what can a toolkit do if this phone doesn't even have developer options turned on? If it's in boot loop, as the OP said, then the Enable OEM unlocking was never set, then the only solution is to send it back. Unless there's a toolkit magic we don't know about.
Click to expand...
Click to collapse
I think op created another thread http://forum.xda-developers.com/nexus-6/help/nexus-6-stuck-bootloop-trying-to-update-t3266100 for this issue - and was somehow able to unlock the bootloader (not sure how that worked if OEM unlock was never set)
jj14 said:
(not sure how that worked if OEM unlock was never set)
Click to expand...
Click to collapse
It was said that some of the first Nexus 6s with the original 5.0 came out with a bootloader that didn't check for this switch.

Categories

Resources