Related
This thread is created so everyone can just meet in one thread and solve a common problem, which is to root the HTC Vivid.
Let's start by looking at the problem. Temp-root is possible but superuser disappears from system folder.
What about putting superuser is the data/app folder?
Would not having the bootloader unlocked have any issues with rooting?
Sent from my T-Mobile G1 using XDA App
if you download superuser from the market it goes in /data/app/ thats not the problem. the problem is the su binary, and busybox. you could probably symlink them, but the symlink wont stay. the problem with the locked bootloader, is that every time you reboot it wipes away any configurations you have done to anything in /system
What if /system is already mounted at boot, that way the bootloader will be denied access to it since it is already mounted.
Edited: Never mind. Thats not a good idea. The OS runs of the /system folder. So mounting it will stop the OS from running.
Pirateghost said:
if you download superuser from the market it goes in /data/app/ thats not the problem. the problem is the su binary, and busybox. you could probably symlink them, but the symlink wont stay. the problem with the locked bootloader, is that every time you reboot it wipes away any configurations you have done to anything in /system
Click to expand...
Click to collapse
mohsinkhan47 said:
What if /system is already mounted at boot, that way the bootloader will be denied access to it since it is already mounted.
Click to expand...
Click to collapse
not sure i know how that would be possible....
the bootloader from htc doesn't work either?
mohsinkhan47 said:
the bootloader from htc doesn't work either?
Click to expand...
Click to collapse
AT&T users dont have any way to unlock the bootloader right now. The Raider can get an unlocked bootloader by using the HTCDev.com website.
if you have an unlocked bootloader, you can have permanent root.
The latest script upload from rpendrik seems to have made the su binary properly sticky. I'm going on 14 hours right now and it hasn't disappeared.
have you guys tried this out:
http://forum.xda-developers.com/showthread.php?t=1296916
or
entering this in from a computer.
"fastboot oem unlock"
mohsinkhan47 said:
have you guys tried this out:
http://forum.xda-developers.com/showthread.php?t=1296916
or
entering this in from a computer.
"fastboot oem unlock"
Click to expand...
Click to collapse
that is how we have been getting temp root.
fastboot oem unlock will not work. we have to get the unlock code from HTC, and they wont give it to us, likely because of AT&T
as of right now, this very instant, there is no way of unlocking the bootloader and achieving permanent root (that we have discovered)
THIS ONLY APPLIES TO THE AT&T VIVID
the Rogers RAIDER is unlockable and the permanent rootable.
Could be completely off in thinking this, but:
Would it be possible to compare multiple Rogers/Bell identifier tokens, against their corresponding unlock.bin files (as they're both the same hex lengths)
and see if an algorithm can be found? And apply said algorithm to ATT Vivid's and see if we could generate our own unlock_code.bin from our identifier tokens?
Just the way I was looking at it, sorry if I'm completely off base.
Get me the files and I'll see if I can do something... oh and
pirate or anyone, could get the spl.img so I can mess with it
rpendrick said:
Could be completely off in thinking this, but:
Would it be possible to compare multiple Rogers/Bell identifier tokens, against their corresponding unlock.bin files (as they're both the same hex lengths)
and see if an algorithm can be found? And apply said algorithm to ATT Vivid's and see if we could generate our own unlock_code.bin from our identifier tokens?
Just the way I was looking at it, sorry if I'm completely off base.
Click to expand...
Click to collapse
Sent from my T-Mobile G1 using XDA App
My curious got goin this morning and I wonder, would it be possible to use the same or similar process on the Vivid to s-off and root that's used on the DHD/Inspire?
If the firmware can be temp flashed using the gold card trick to use the Ca or Kor version then exploit it, in theory this could work, no?
Saved and Texan by the grace of God, Redneck by choice.
Tx Redneck said:
My curious got goin this morning and I wonder, would it be possible to use the same or similar process on the Vivid to s-off and root that's used on the DHD/Inspire?
If the firmware can be temp flashed using the gold card trick to use the Ca or Kor version then exploit it, in theory this could work, no?
Saved and Texan by the grace of God, Redneck by choice.
Click to expand...
Click to collapse
I was actually thinking the same thing last night but I figured that attn1, who figured out the Inspire root, would have already thought of or tried it. I'm also not sure if the boot-loader was actually "locked" on the Inspire.
pside15 said:
I was actually thinking the same thing last night but I figured that attn1, who figured out the Inspire root, would have already thought of or tried it. I'm also not sure if the boot-loader was actually "locked" on the Inspire.
Click to expand...
Click to collapse
I don't think attn1 has the device. You remember the thread he made about boycotting it?
Sent from my HTC PH39100 using xda premium
He doesn't have one... and I doubt he will either.
pside15 said:
I was actually thinking the same thing last night but I figured that attn1, who figured out the Inspire root, would have already thought of or tried it. I'm also not sure if the boot-loader was actually "locked" on the Inspire.
Click to expand...
Click to collapse
The bootloader was locked, it's just that HTC has very aggressively closed those exploits.
dbaser said:
He doesn't have one... and I doubt he will either.
Click to expand...
Click to collapse
*le sigh, I sooooo wish he'd try hackin on one.
doktor buknasty said:
I don't think attn1 has the device. You remember the thread he made about boycotting it?
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
Yea, but I just assumed that if the same exploit would have worked he may not have been adamant about boycotting it.
---------- Post added at 11:58 AM ---------- Previous post was at 11:55 AM ----------
Tx Redneck said:
The bootloader was locked, it's just that HTC has very aggressively closed those exploits.
Click to expand...
Click to collapse
Oh, I didn't know it was locked on the Inspire. I just didn't remember seeing it say "Locked" at the top of the bootloader screen on my Inspire like it does on my Vivid.
So trying the ace hack kit would be a no-go?
Sent from my HTC PH39100 using xda premium
doktor buknasty said:
So trying the ace hack kit would be a no-go?
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
As it is now would definitely be a no go. Not sure if it could be edited to work with the Vivid or not. I don't think so but I don't know enough about development to know for sure either way.
Can you guys provide me with a link to what you guys are talking about...
pside15 said:
As it is now would definitely be a no go. Not sure if it could be edited to work with the Vivid or not. I don't think so but I don't know enough about development to know for sure either way.
Click to expand...
Click to collapse
Sent from my T-Mobile G1 using XDA App
It started here:
http://forum.xda-developers.com/showthread.php?t=2530605
I followed this post.
http://forum.xda-developers.com/showthread.php?t=2509676
Got nowhere because of the puttytel window timeout problem.
Related to this post was this post:
http://forum.xda-developers.com/showthread.php?p=47749358#post47749358
I have an unlocked bootloader on Moto X from sprint. I just need the easiest way to root.
This looked confusing. http://forum.xda-developers.com/showthread.php?t=2536200. Gotta be another way.
Have considered restoring to stock and taking the dang thing back http://atsgadgets.com/how-to-restor...lite-att-t-mobile-sprint-verizon-us-cellular/. So frustrated.
I've offered paypal to those who can do it successfully. I am so burnt out on trying to make this work. This PITA is not worth android. I have a one click jailbroken phone now. And I have successfully rooted and installed custom roms before but this is totally out of hand how complex this is for me. Maybe I'm just remedial but it seems several are having trouble with this model. For open source, this should not be this tough.
/rant. Almost ready to throw in the towel, but still listening.....
Sorry for the multiple posts. Just trying to get some new opinions. HTC Evo 4 g was done in 10 minutes. This has taken 4 days.
:crying:
bullpen7979 said:
I have an unlocked bootloader on Moto X from sprint. I just need the easiest way to root.
This looked confusing. http://forum.xda-developers.com/showthread.php?t=2536200. Gotta be another way.
Have considered restoring to stock and taking the dang thing back http://atsgadgets.com/how-to-restor...lite-att-t-mobile-sprint-verizon-us-cellular/. So frustrated.
I've offered paypal to those who can do it successfully. I am so burnt out on trying to make this work. This PITA is not worth android. I have a one click jailbroken phone now. And I have successfully rooted and installed custom roms before but this is totally out of hand how complex this is for me. Maybe I'm just remedial but it seems several are having trouble with this model. For open source, this should not be this tough.
/rant. Almost ready to throw in the towel, but still listening.....
Sorry for the multiple posts. Just trying to get some new opinions. HTC Evo 4 g was done in 10 minutes. This has taken 4 days.
:crying:
Click to expand...
Click to collapse
Are you on 4.4 and what computer OS are you using?
I am on android version 4.2.2 and windows xp SP 3. thanks for your response, sir.
bullpen7979 said:
I am on android version 4.2.2 and windows xp SP 3. thanks for your response, sir.
Click to expand...
Click to collapse
Here, go into Settings -> About Phone and tell me what your Build Number is (at the very bottom).
Do not put in the cmd window mfastboot, just try fastboot flash recovery twrp 2.6.3.1-ghost-4.4.img. Now also put the recovery image in the same folder as fast boot, I believe its SDK tools folder
Sent on my Moto X
bullpen7979 said:
I am on android version 4.2.2 and windows xp SP 3. thanks for your response, sir.
Click to expand...
Click to collapse
The method that you thought was confusing, is the one you should use. If I have time, I could try helping you with it.
ALU0506, the build number is 13.9.0Q2.X-116-MX-17-57-1. Thanks everyone for your help.
I have downloaded the files mentioned in the thread. Thats as far as i have gotten. If you have time to help, that would be great. I mean like over the top great
bullpen7979 said:
I have downloaded the files mentioned in the thread. Thats as far as i have gotten. If you have time to help, that would be great. I mean like over the top great
Click to expand...
Click to collapse
I can try helping over gtalk.
bullpen7979 said:
I have downloaded the files mentioned in the thread. Thats as far as i have gotten. If you have time to help, that would be great. I mean like over the top great
Click to expand...
Click to collapse
Plug in your phone and put it into fastboot by typing adb reboot bootloader then type fastboot devices does it show that you are connected?
I will try that as soon as I can and get back to you. I have two computers one at my hotel and one here. I'm not sure I have the ADB tools on my netbook
Sent from my XT1056 using xda app-developers app
bullpen7979 said:
I will try that as soon as I can and get back to you. I have two computers one at my hotel and one here. I'm not sure I have the ADB tools on my netbook
Sent from my XT1056 using xda app-developers app
Click to expand...
Click to collapse
if you are still looking for help i can help you get this done on gtalk as well. send me a pm with your username. it will take virtually no time at all
jayboyyyy said:
if you are still looking for help i can help you get this done on gtalk as well. send me a pm with your username. it will take virtually no time at all
Click to expand...
Click to collapse
especially since he already unlocked the bootloader. Just flash recovery, then flash supersu.zip.
aooga said:
especially since he already unlocked the bootloader. Just flash recovery, then flash supersu.zip.
Click to expand...
Click to collapse
ya during his four days of misery, he could have just read for 1 hour on the stuff so it would seem confusing anymore and then he would have had a rooted phone. But either way, his problem is solvable with a few simple instructions.
OK Jay/Aooga.
Finally back from work.
Plug in your phone and put it into fastboot by typing adb reboot bootloader then type fastboot devices does it show that you are connected?
open cmd window, typed adb reboot bootloader, and got:
T063202TFL and fastboot, and then a prompt.
OK Jay/Aooga.
Finally back from work.
Plug in your phone and put it into fastboot by typing adb reboot bootloader then type fastboot devices does it show that you are connected?
open cmd window, typed adb reboot bootloader, and got:
T063202TFL and fastboot, and then a prompt.
Phone is in fastboot mode with white, yellow green text.
Device is unlocked. Status code 3.
Battery OK Charging
Transfer mode USB connected.
It looked as though I had to be able to accept the 4.4 kitkat OTA in order to get this done. but when i went to the usual spot to look for system updates it said there were none available.
Anyhow, I am super grateful for your help. Sorry to be such a remedial doofus
Looks like we can wait till tomorrow. Or today. Or whatever timeline it is.
This would be great to begin the Development section.
Links to Motorola drivers
Link to SDK & where to put it
Enabling unlock on the phone
When / how to run the fastboot commands
So if one of you could do this before someone else temporarily soft - bricks their phone? Please?
The instructions are no different from unlocking any nexus device with the exception that you need to check a box in developer settings. Just do a Google search.
Sent from my Nexus 6 using XDA Free mobile app
akellar said:
The instructions are no different from unlocking any nexus device with the exception that you need to check a box in developer settings. Just do a Google search.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
I myself have no problem with this, but
IMHO, I think the instructions need posting in said section. Lots of folks are getting a Nexus for 1st time. Are we going to advise all of them just to do a Google search? If that is the consensus, then so be it.
wtherrell said:
I myself have no problem with this, but
IMHO, I think the instructions need posting in said section. Lots of folks are getting a Nexus for 1st time. Are we going to advise all of them just to do a Google search? If that is the consensus, then so be it.
Click to expand...
Click to collapse
Fair but then write them or provide a link.
Sent from my Nexus 6 using XDA Free mobile app
akellar said:
Fair but then write them or provide a link.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
I think there are many more qualified than I to do that. But I will try to devote some time this week to finding drivers, lollipop SDK for windows, etc. Then, when I get the phone unlock it and record all the steps. Then (if successful) post them. Hoping all the while that someone else beats me to it.
Well for one thing you won't need to download the SDK at all.
Just get this: [TOOL]Minimal ADB and Fastboot Just tested it on Windows 10 and it works fine.
I searched for N6 drivers and couldn't find any. Motorola has a "software & drivers" section but it's empty right now.
No TWRP yet, either.
wtherrell said:
No TWRP yet, either.
Click to expand...
Click to collapse
It will come after root but google needs to post the factory images first.
Also of you download the google SDK then tap build number 7 times to enable Dev options you will be able to check he box that says allow OEM unlock. Then it's just a quick fastboot command
Pilz said:
It will come after root but google needs to post the factory images first.
Also of you download the google SDK then tap build number 7 times to enable Dev options you will be able to check he box that says allow OEM unlock. Then it's just a quick fastboot command
Click to expand...
Click to collapse
Thought I would use TWRP to flash SU update zip.
Guess I could root 1st, then flash recovery later.
Pilz said:
It will come after root but google needs to post the factory images first.
Also of you download the google SDK then tap build number 7 times to enable Dev options you will be able to check he box that says allow OEM unlock. Then it's just a quick fastboot command
Click to expand...
Click to collapse
It seems to work even without checking the OEM unlock in developer settings. I forgot all about that and ran fastboot unlock the second I opened the box and it worked without any issues.
wtherrell said:
Thought I would use TWRP to flash SU update zip.
Guess I could root 1st, then flash recovery later.
Click to expand...
Click to collapse
Yeah but TWRP took a week or two to get on the Nexus 9 after it was rooted so it will be a while. I just want root so I can install a new camera app that I have to manually move.
---------- Post added at 09:30 AM ---------- Previous post was at 09:28 AM ----------
eep2378 said:
It seems to work even without checking the OEM unlock in developer settings. I forgot all about that and ran fastboot unlock the second I opened the box and it worked without any issues.
Click to expand...
Click to collapse
Someone else did that without hitting the box and they got a softbrick so you got lucky. It's dumb that they added that extra step but I'm glad it's still unlockable.
Pilz said:
Someone else did that without hitting the box and they got a softbrick so you got lucky. It's dumb that they added that extra step but I'm glad it's still unlockable.
Click to expand...
Click to collapse
If you're referring to the other thread here, that isn't what caused his problem. Him powering down while it was formatting something likely was.
akellar said:
If you're referring to the other thread here, that isn't what caused his problem. Him powering down while it was formatting something likely was.
Click to expand...
Click to collapse
Yeah I let it sit for a while to do its thing then rebooted from fastboot. No issues. Not sure what is going on with the OP he said he let it sit for a long time and still nothing.
eep2378 said:
Yeah I let it sit for a while to do its thing then rebooted from fastboot. No issues. Not sure what is going on with the OP he said he let it sit for a long time and still nothing.
Click to expand...
Click to collapse
It could be something else that he did or and on his phone.
akellar said:
If you're referring to the other thread here, that isn't what caused his problem. Him powering down while it was formatting something likely was.
Click to expand...
Click to collapse
One of the softbricks came from selecting an incorrect device, IIRC.
gtalum said:
One of the softbricks came from selecting an incorrect device, IIRC.
Click to expand...
Click to collapse
Selecting an incorrect device? Not sure what you're referring to there.
akellar said:
Selecting an incorrect device? Not sure what you're referring to there.
Click to expand...
Click to collapse
Ignore that, I remembered something incorrectly.
Bjray said:
I searched for N6 drivers and couldn't find any. Motorola has a "software & drivers" section but it's empty right now.
Click to expand...
Click to collapse
You need to use the Google USB Drivers found here http://developer.android.com/sdk/win-usb.html#
akellar said:
Selecting an incorrect device? Not sure what you're referring to there.
Click to expand...
Click to collapse
That one was using the Wugfresh NRT somewhat prematurely. Quicker to use fastboot, I think.
jay_em113 said:
You need to use the Google USB Drivers found here http://developer.android.com/sdk/win-usb.html#
Click to expand...
Click to collapse
Thanks for the drivers link.
I recieved my nexus 6 today and couldn't wait to power it up. To my dismay I find that my phone is not set up for "consumer use!" My question is could I root it and flash a different ROM on it or do I have to return it to motorola and wait for them to send me another. I'd hate to have to wait for them to ship me a new phone?
indoz said:
I recieved my nexus 6 today and couldn't wait to power it up. To my dismay I find that my phone is not set up for "consumer use!" My question is could I root it and flash a different ROM on it or do I have to return it to motorola and wait for them to send me another. I'd hate to have to wait for them to ship me a new phone?
Click to expand...
Click to collapse
Wth . that's up to you . You may want to call them , I think I would .
But you don't have to root . just unlock you Bootloader ( Fastboot OEM unlock ) then flash the stock IMG from google https://developers.google.com/android/nexus/images go into recovery do a factory reset then restart ... After it boots go back to Bootloader and relock ( Fastboot oem lock) or leave it unlocked . then your done . a
This is pretty much why the AT&T stores had that recall from Motorola.
drawde40599 said:
Wth . that's up to you . You may want to call them , I think I would .
But you don't have to root . just unlock you Bootloader ( Fastboot OEM unlock ) then flash the stock IMG from google https://developers.google.com/android/nexus/images go into recovery do a factory reset then restart ... After it boots go back to Bootloader and relock ( Fastboot oem lock) or leave it unlocked . then your done . a
Click to expand...
Click to collapse
Thank you! That's exactly what I needed:good:
BTW, try to get a system dump before you flash Lollipop!
Diviance said:
This is pretty much why the AT&T stores had that recall from Motorola.
Click to expand...
Click to collapse
Ohhhhhh , that makes total sense . knowing this I wouldn't even call them then just flash 5.0
johnny grep said:
BTW, try to get a system dump before you flash Lollipop!
Click to expand...
Click to collapse
How would I go about getting a dump? I can do that while I wait for the files to dl
Yes, please hold off on flashing. You essentially got a unicorn Nexus and many people would like to experiment with what you have.
Edit: Try this http://forum.xda-developers.com/nex...talled-rom-t2937029/post56781001#post56781001
Make sure you copy and paste and don't type those commands manually.
I'd contact a dev in here like simms22 before you try it though. He'd probably be very interested.
Thanks I'll get the files shortly
I appreciate the willingness. I do want to emphasize that you should contact a dev first so he can explain it better. That dd linux command can be dangerous if done improperly. I'd love to see a successful dump of your rom, but not without ensuring that any risks are taken care of. I don't have a 6 yet, so I can't test it first.
Sent from my VS985 4G using XDA Free mobile app
Please let a dev play with this phone. Dum dum's like myself could really use that filesystem right now. I wiped half my partition layout out and am without sensors or anything.
Nopcodex90 said:
Please let a dev play with this phone. Dum dum's like myself could really use that filesystem right now. I wiped half my partition layout out and am without sensors or anything.
Click to expand...
Click to collapse
I want to see it too but don't get how this would help you any more than the current stock images do.
Sent from my VS985 4G using XDA Free mobile app
JesusFreak316 said:
I want to see it too but don't get how this would help you any more than the current stock images do.
Sent from my VS985 4G using XDA Free mobile app
Click to expand...
Click to collapse
The stock images do not contain an ATT OEM partition.
Ah, thanks.
Sent from my VS985 4G using XDA Free mobile app
JesusFreak316 said:
I want to see it too but don't get how this would help you any more than the current stock images do.
Sent from my VS985 4G using XDA Free mobile app
Click to expand...
Click to collapse
It could get dalvik back on the phone so people could use xposed framework etc
Sent from my Nexus 6 using Xparent BlueTapatalk 2
first, as other have said PLEASE PLEASE PLEASE get a system dump before you do anything.
Second, an ATT rep who seemed to know a bit more than the average rep told me that if this happens the phone probably wont ever work as intended because there are also issues with the modem portion and it wont get proper service or data. It is possible that you may be able to reflash the radio and maybe get that part fixed, but personally once you get the system dump for all of us to work with it would be best if you got an RMA so you started with a proper device
nexus6R3plicant said:
It could get dalvik back on the phone so people could use xposed framework etc
Sent from my Nexus 6 using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Nah, I get that. He was saying it would help him fix his partition layout and I didn't see how it would help more than the factory usage but I didn't know the factory image leaves out partitions like /OEM.
just curious if you got a system dump of this before trying to flash 5.0??
was a back up able to be made of this would be fun to install on my nexus 6 or maybe use with multirom for fun.
qnc said:
was a back up able to be made of this would be fun to install on my nexus 6 or maybe use with multirom for fun.
Click to expand...
Click to collapse
I have the same Idea, and MultiROM is already on Google Play Supporting NEXUS6 since April 6th, so, where we can have the 444 ROM Dump to install it?
im getting a nexus 6 tomorrow , ive researched the root methods for it, but nothing was verizon secific. i know nothing of nexus hones, so i was wondering will all root methods work?
sparkmate said:
im getting a nexus 6 tomorrow , ive researched the root methods for it, but nothing was verizon secific. i know nothing of nexus hones, so i was wondering will all root methods work?
Click to expand...
Click to collapse
All nexus 6 devices in North America are technically identical.
sparkmate said:
im getting a nexus 6 tomorrow , ive researched the root methods for it, but nothing was verizon secific. i know nothing of nexus hones, so i was wondering will all root methods work?
Click to expand...
Click to collapse
I'm on Verizon and followed this guide. Other than alittle trouble getting usb drivers working it was easy peasy...http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
Is there a way of recovering from a brick with a locked boot loader?
sparkmate said:
Is there a way of recovering from a brick with a locked boot loader?
Click to expand...
Click to collapse
Only if you have TWRP installed. Otherwise, most likely not.
If you unlock it, root it, modify it, you have no reason at all to relock the boot loader.
Just don't lock the boot loader - idk why you would want to do that anyway.
I know when I rooted mine and decrypted, I used Wugfresh's Nexus Root Toolkit. It made things really simple and easy to understand. I just watched some videos from RootJunky on YouTube going through the process and it worked great.
Sent from my Nexus 6
Othoric said:
I know when I rooted mine and decrypted, I used Wugfresh's Nexus Root Toolkit. It made things really simple and easy to understand. I just watched some videos from RootJunky on YouTube going through the process and it worked great.
Sent from my Nexus 6
Click to expand...
Click to collapse
That's cool and it's good you did watch videos but alot of developers and rc's told me they prefer for people to use fasboot that way if something goes awry with the toolkit they can help us straighten things out and you'll have some knowledge of fastboot and it'll be setup on your computer already. It might be apples and oranges but that just what I was told by people that know more than me. Keep in mind that this is not to diminish Wugfresh. He worked very hard and knows a great deal to come up with a toolkit.