Mod edit: Removed content
I tried it just to see what happens, can't get it to recognize the command. entered adb shell but still says command not recognized.
3aucla1r3 said:
I tried it just to see what happens, can't get it to recognize the command. entered adb shell but still says command not recognized.
Click to expand...
Click to collapse
It need htc adb document.But I cant load them.
I can share you with Google Drive. And I just know a part of the way. It seems that something I dont have .Maybe Usb Hub.
通过我的 Pixel XL 上的 Tapatalk发言
This way is apply to 7.12
from taptalk
Are you sure this even applies to the Pixel? This seems like a way to get SuperCID on a traditional HTC device like the M9.
Sure， Someone unlocked bl by this way
from taptalk
Alcolawl said:
Are you sure this even applies to the Pixel? This seems like a way to get SuperCID on a traditional HTC device like the M9.
Click to expand...
Click to collapse
Sure， Someone unlocked bl by this way
from taptalk
sceptical doesn't even cover it.
i'm looking at lots of htc stuff for a starter...
a link to firmware for S1_WHL - which i can pretty much bank on not being pixel... or pixel xl.
something here really doesn't add up
y2grae said:
sceptical doesn't even cover it.
i'm looking at lots of htc stuff for a starter...
a link to firmware for S1_WHL - which i can pretty much bank on not being pixel... or pixel xl.
something here really doesn't add up
Click to expand...
Click to collapse
http://cloud.tapatalk.com/s/597b425cbe9c8/htc_fastboot_driver.ziphttp://cloud.tapatalk.com/s/597b427b3c1e5/htc_Fastboot.ziphttp://cloud.tapatalk.com/s/597b431280892/usb-over-network-64bit.zip
from taptalk
chenery said:
Sure， Someone unlocked bl by this way
Click to expand...
Click to collapse
Proof? A link perhaps? Traditionally on HTC phones the command
Code:
fastboot oem writecid
doesn't work unless the bootloader is unlocked. -___-
My bootloader is unlocked, and I tried that command. It did not work. I also tried his fastboot and that did not work either.
This thread is Fake News.
cant do anything if its locked down. need temp root
Darn. Just when I thought there was a light at the end of the tunnel. :|
stever87 said:
Darn. Just when I thought there was a light at the end of the tunnel. :|
Click to expand...
Click to collapse
you should've known not to trust a no post account claiming miracles
Captain Hindsight said:
you should've known not to trust a no post account claiming miracles
Click to expand...
Click to collapse
Miracles are what I depend on now after making a rookie mistake of re-locking my bootloader.
Since this method apparently does not work, pointless thread is pointless. Thread closed.
Cheers,
Magnum_Enforcer
FSM
Related
Does it bug anyone that one click rooting takes way more than 1 click? (Not that I use one click programs for my Xoom)
No. It bothers me that people are so stupid that they want and use the so called one click methods period. Even more so on a device with a unlocked bootloader.
Sent from my Xoom using Tapatalk
albundy2010 said:
No. It bothers me that people are so stupid that they want and use the so called one click methods period. Even more so on a device with a unlocked bootloader.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
What's wrong with that method? I haven't rooted yet partly due to lack of knowledge.
Sent from my Xoom using XDA App
haha. me too. its asking for a bricked device if u ask me
That's the point. Acquire the knowledge.
Sent from my Xoom using Tapatalk
RadDudeTommy said:
What's wrong with that method? I haven't rooted yet partly due to lack of knowledge.
Sent from my Xoom using XDA App
Click to expand...
Click to collapse
You dont need alot of knowledge and the guids are ez to follow. The problem with one click's are they dont expose you to ADB so when something goes wrong with the one click you wont know what to do. ADB is something that I avoided but with an unlocked bootloader its a good place to learn. just my opinoin
sgtagem said:
You dont need alot of knowledge and the guids are ez to follow. The problem with one click's are they dont expose you to ADB so when something goes wrong with the one click you wont know what to do. ADB is something that I avoided but with an unlocked bootloader its a good place to learn. just my opinoin
Click to expand...
Click to collapse
Very well said. I have rooted two android devices previously, but the Xoom gave me my first experience using adb. It came in very handy when I got into a soft brick and was able to negotiate my way out of it. I still experience some anxiety whenever I'm about to mod my Xoom, but it helps to have some basic knowledge (and know what you don't know). Also, read and follow the directions and get everything prepared in advance.
okantomi said:
Very well said. I have rooted two android devices previously, but the Xoom gave me my first experience using adb. It came in very handy when I got into a soft brick and was able to negotiate my way out of it. I still experience some anxiety whenever I'm about to mod my Xoom, but it helps to have some basic knowledge (and know what you don't know). Also, read and follow the directions and get everything prepared in advance.
Click to expand...
Click to collapse
so true. i hate soft bricks. I still worry about messing it up but knowing commands help.
I'm not sure what is up, this isn't a new thing, but people keep coming to me (1-2 a day) with this issue.
If your phone isn't stock, DO NOT RELOCK your bootloader. You will 'soft brick' it, and at this time there is no easy route to fixing it.
If you are on EE UK, Verizon or another carrier blocking bootloader unlocks, and you used dePixel8 to unlock it, DO NOT relock your bootloader unless you are sure you don't want it unlocked again.
Finally, dePixel8 is UNSUPPORTED. Don't come to me if you can't get it to work, don't come to me if you used it them messed up your phone by flashing something bad or whatever. Its on you.
What's the fix if this does happen?
infamousjax said:
What's the fix if this does happen?
Click to expand...
Click to collapse
There isn't one and no guarantee there will be one. Don't do this.
tw1tch175 said:
There isn't one and no guarantee there will be one. Don't do this.
Click to expand...
Click to collapse
Fair enough. Thanks
This should be pinned!!
Mods?
It was all just an illusion
Interesting.. glad this didn't happen to me. I did relock my bootloader once because i was having issues activating my SIM card. I wanted see if that was the reason. Once i did manage to get the SIM activated i went through the process of unlocking using the dePixel8 method again. I guess i won't be doing that again.
Hah this would have been nice to see first. I ended up soft-bricked on my pixel xl. I hope a fix comes soon. Even a jtag or direct method somehow.
Flashing needs to be done directly since fastboot reads oem unlock and denys it.
Cataire said:
Hah this would have been nice to see first. I ended up soft-bricked on my pixel xl. I hope a fix comes soon. Even a jtag or direct method somehow.
Flashing needs to be done directly since fastboot reads oem unlock and denys it.
Click to expand...
Click to collapse
This isnt a new warning, its pretty much standard "Dont relock with non stock firmware".
JTAG is a no go, would have to attack to the ufs and rewrite at the best least the boot.img
Eh things happen. I know better now. And now I need to learn how to make it right
I don't understand why anyone WOULD relock the bootloader of not stock
318sugarhill said:
I don't understand why anyone WOULD relock the bootloader of not stock
Click to expand...
Click to collapse
Some people are not as experienced as us. Not hard to imagine, just noobs, no offense guys. You live and learn, no biggie. I say respect them and help them, I say welcome noobs.
If we expect our community to grow, we need to be respective of new comers.
318sugarhill said:
I don't understand why anyone WOULD relock the bootloader of not stock
Click to expand...
Click to collapse
I've heard of people doing it to try to reenable Android Pay since it won't work with an unlocked bootloader.
Alpione said:
I've heard of people doing it to try to reenable Android Pay since it won't work with an unlocked bootloader.
Click to expand...
Click to collapse
This is honestly the biggest reason I can see as to why this happens
Sent from my Pixel XL using Tapatalk
DELETED
ScytheSniper said:
First of all, I'd like to say thanks to all the hard work put into the dePixel8 BL unlock.
With that said, I would like to say a couple things about this particular statement.
1. It is slightly misleading, you can relock your bootloader and still unlock it again under the right circumstances. If your software is all stock and you use dePixel8 after relocking, it will unlock again.
2. This statement contradicts the previous one. You should probably avoid telling people "they can never unlock their bootloader again if they relock it" if there is ANY possibility that they can. After reading this statement from you in the unlocking thread I spent about 2 hours scouring threads to find out if this statement was always true, which it is not.
Again, thank you for all the hard work on getting this unlock out. The intent of my post here is only to help improve communication of potential problems.
Click to expand...
Click to collapse
There is nothing misleading about the post. The statements are true. Wait til tomorrow, when complaints start coming in about how people cant seem to unlock.
DELETED
ScytheSniper said:
I'm sorry, but this is just not the case. I have verified this myself with my own Pixel XL from Verizon. On a stock image load I can unlock and lock the bootloader as many times as I want using dePixel8 to perform the unlock. Your statement in my opinion implies that if I relock the bootloader AT ALL it will fail to unlock ever again.
This may not be your intention to be misleading, but I know I am not alone in my interpretation of your statement. All I am asking is that you not make statements like the one I quoted which are provably false. Also, I did not say that your entire post was misleading, only the statement in quotes is.
Click to expand...
Click to collapse
I'm not sorry. You are lacking information/knowledge on the subject. The OP statement is accurate.
The statement was made with good reason, based on fact and prior knowledge. You will see why tomorrow, when people start complaining.
DELETED
ScytheSniper said:
I'm sorry, but this is just not the case. I have verified this myself with my own Pixel XL from Verizon. On a stock image load I can unlock and lock the bootloader as many times as I want using dePixel8 to perform the unlock. Your statement in my opinion implies that if I relock the bootloader AT ALL it will fail to unlock ever again.
This may not be your intention to be misleading, but I know I am not alone in my interpretation of your statement. All I am asking is that you not make statements like the one I quoted which are provably false. Also, I did not say that your entire post was misleading, only the statement in quotes is.
Click to expand...
Click to collapse
The next security release should rollout tomorrow... And with that there will be a fix for VZW models preventing depixel8 from working. So IF you relock your bootloader after taking this update, we'll you'll be SOL. It's only misleading if you don't have prior knowledge of pretty much anything android.
I mean of course you can lock and unlock as many times as you want right NOW. Tomorrow will be a different story I guarantee.... But go ahead and be our guinea pig. I for one just say thank you @jcase and @beaups and listen to their advice. They've been around a long time and given us lots of goodies. I don't question them.
ScytheSniper said:
If I am lacking in knowledge and information why am I able to unlock and relock my bootloader at will on my Pixel purchased at Verizon?
Click to expand...
Click to collapse
I'm guessing you dont understand how depixel8 works.
I'm guessing you dont realize that google could remotely nix this in the butt any any moment
I'm guessing you are unaware of NDE63X at this point and it's effect on the situation.
Why don't you lock your bootloader for a few days, then try? or just sit back, watch ppl ignore the PSA, then start compaling about being stuck locked.
I actually work for Sprint and would consider picking up this phone if it got some decent developer support. If anyone has any basic questions about the device or its specs feel free to ask as I have played with it pretty extensively. It's an HTC device so hopefully it has an unlockable bootloader?
I should be receiving my Bolt in a few days, but I recall HTC stating that phones 2011 and newer will be able to unlock their bootloaders but certain models will be unlockable due to operators restriction.
Hopefully this phone gets some decent developer support.
Nice. As far as we can get it - m9 will get N faster) I'm also wanting to take a look at bolt's audio system, but system dump needed.
UltraM8 said:
Nice. As far as we can get it - m9 will get N faster) I'm also wanting to take a look at bolt's audio system, but system dump needed.
Click to expand...
Click to collapse
By N do you mean nougat? Cause the Bolt comes with Nougat 7.0 out of the box. First HTC phone to get it.
Also I'm not sure if XDA's description of the Bolt where it states the device is a mid range one from HTC is accurate. This is clearly intended to be a flagship. Sure it has the SD 810, but even in 2016 that is hardly a mid range SOC, and the device has many flagship qualities like a 5.5 inch quad HD display, an all metal unibody design with water resistance, large battery, USB type C, expandable storage, latest version of Android, etc.
There is even the whole LTE plus support thing which is a quality that other flagship on Sprint do not have. Oh and it has a 16mp camera with OIS. How exactly is this a mid range?
I have played with this phone a lot at work and it is very responsive. I don't think the SD 810 makes a difference.
elsamuraiguapo said:
By N do you mean nougat? Cause the Bolt comes with Nougat 7.0 out of the box. First HTC phone to get it.
Also I'm not sure if XDA's description of the Bolt where it states the device is a mid range one from HTC is accurate. This is clearly intended to be a flagship. Sure it has the SD 810, but even in 2016 that is hardly a mid range SOC, and the device has many flagship qualities like a 5.5 inch quad HD display, an all metal unibody design with water resistance, large battery, USB type C, expandable storage, latest version of Android, etc.
There is even the whole LTE plus support thing which is a quality that other flagship on Sprint do not have. Oh and it has a 16mp camera with OIS. How exactly is this a mid range?
I have played with this phone a lot at work and it is very responsive. I don't think the SD 810 makes a difference.
Click to expand...
Click to collapse
I care only about audio man) Bolt seems to be a slightly upgraded version of m9, which i'm very happy with. I just want to put my hands on Bolt's system dump asap)
Just picked mine up today... Any devs need a system dump?
I got mine today
HTC has the latest 1.17.651.11 RUU posted, I'm downloading then will posted imgs as well as firmware & stock rooted rom
OMJ said:
HTC has the latest 1.17.651.11 RUU posted, I'm downloading then will posted imgs as well as firmware & stock rooted rom
Click to expand...
Click to collapse
Please can you share the new apk's clock (with widget) and the new camera (with panorama selfie)?
drob311 said:
Just picked mine up today... Any devs need a system dump?
Click to expand...
Click to collapse
Yes!! I want to port usb audio stuff to m9. Also wanna take a look at new SRS/DTS stuff) PM me, bro.
anyone try S-off yet?
OMJ said:
anyone try S-off yet?
Click to expand...
Click to collapse
I didn't do the HTC unlock. I tried sunshine in hopes of getting lucky and not having to use HTC unlock... No luck... Once I unlock bootloader, I'll try sunshine again.
drob311 said:
I didn't do the HTC unlock. I tried sunshine in hopes of getting lucky and not having to use HTC unlock... No luck... Once I unlock bootloader, I'll try sunshine again.
Click to expand...
Click to collapse
I don't think sunshine will work yet...their website shows it supports up to android 6.0.1...jcase needs some partitions pulled to be able to update
Well... After my pizza arrives, I'll start the process of rooting this bad boy. My plan is HTC unlock, flash twrp, flash SuperSU. Once I get root, I'll pull whatever info jcase needs... What's all this talk about data partition getting corrupted after unlock?
drob311 said:
Well... After my pizza arrives, I'll start the process of rooting this bad boy. My plan is HTC unlock, flash twrp, flash SuperSU. Once I get root, I'll pull whatever info jcase needs... What's all this talk about data partition getting corrupted after unlock?
Click to expand...
Click to collapse
cool...I believe after unlocking it factory resets
I would like a system Dump. Work got me one I will have it shortly
hawknest said:
I would like a system Dump. Work got me one I will have it shortly
Click to expand...
Click to collapse
I have the system img posted here...http://forum.xda-developers.com/bolt/development/ruu-sprint-htc-bolt-1-17-651-11-updated-t3502778
Sorry for the dumb question does the bolt have a unlocked boot loader
Sent from my SM-N910P using Tapatalk
sliverr7x said:
Sorry for the dumb question does the bolt have a unlocked boot loader
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
all HTC devices come locked by default, but yes the Bolt can be unlocked via htcdev.com
sliverr7x said:
Sorry for the dumb question does the bolt have a unlocked boot loader
Click to expand...
Click to collapse
You can unlock it but obtaining root is a different story... I've been slowly working on it with OMJ's help. I can't get SuperSU to flash and actually mod the boot.img...
If you have any luck, please let me know what you did. Thanks!
So I am warranting out my phone though Verizon because my screen has burn in (yeah wonderful).... Anyway I have an unlocked model now. Am I screwed now with this new one? Will have no way to root or unlock?
mdonnelly1127 said:
So I am warranting out my phone though Verizon because my screen has burn in (yeah wonderful).... Anyway I have an unlocked model now. Am I screwed now with this new one? Will have no way to root or unlock?
Click to expand...
Click to collapse
Let us know when you find out.
Sent from my Pixel using XDA-Developers Legacy app
bobby janow said:
Let us know when you find out.
Click to expand...
Click to collapse
Lol okay? Can I get an actual response?
mdonnelly1127 said:
Lol okay? Can I get an actual response?
Click to expand...
Click to collapse
We don't know.
If you want a guess..I would guess 7.1.1 since it will be a refurb.
mdonnelly1127 said:
So I am warranting out my phone though Verizon because my screen has burn in (yeah wonderful).... Anyway I have an unlocked model now. Am I screwed now with this new one? Will have no way to root or unlock?
Click to expand...
Click to collapse
You will most likely get a 7.1.1 device. Warranty it through Google
From the posts I have read about it, your warranty replacement will be a VZW refurb most likely on 7.1.1. If you get a new device from VZW it is still coming on 7.1 NDE63P.
One member posted getting a warranty replacement through Google still on 7.1 but he had to request it that way...
I just got my RMA from vzw it had Oct's software on it. I'd say you're fine. Also if you want to go through Google, I've seen post on Reddit where Google will send you a non VZW version.
Already processed the Warranty through Verizon, getting it tomorrow. Hopefully I get a model with old software... If not then I guess I'm screwed then? Lol
mdonnelly1127 said:
Already processed the Warranty through Verizon, getting it tomorrow. Hopefully I get a model with old software... If not then I guess I'm screwed then? Lol
Click to expand...
Click to collapse
The info sticker on the back of the RMA device has the software version. So I knew before I even turned it on.
mdonnelly1127 said:
Already processed the Warranty through Verizon, getting it tomorrow. Hopefully I get a model with old software... If not then I guess I'm screwed then? Lol
Click to expand...
Click to collapse
If not, then yes you are correct. You do realize this thread is totally pointless since there is nothing you can do about it. Good luck though.
Sent from my Pixel using XDA-Developers Legacy app
jordy787 said:
You will most likely get a 7.1.1 device. Warranty it through Google
Click to expand...
Click to collapse
Can you still root without unlocking?
mdonnelly1127 said:
Can you still root without unlocking?
Click to expand...
Click to collapse
You might want to rethink rooting if you need an answer to that question. Why do you want root anyway?
Sent from my Pixel using XDA-Developers Legacy app
bobby janow said:
You might want to rethink rooting if you need an answer to that question. Why do you want root anyway?
Click to expand...
Click to collapse
Substratum themes honestly
mdonnelly1127 said:
Substratum themes honestly
Click to expand...
Click to collapse
Then yes you need to unlock the bootloader. But please do yourself a favor and research the crap out of unlocking and rooting before you do it. Also the benefits and drawbacks. Those themes can also boot loop your device if you're not careful and make sure you have a fail safe way to recover.
Sent from my Pixel using XDA-Developers Legacy app
Root is possible without unlock, but no one is going to burn a root method on a phone with an unlockable bootloader. Get the model that unlockable.
Like previously stated this thread is moot. Warranty through Google or deal with a locked bootloader. End of story.
Sent from my Pixel XL using Tapatalk
superchilpil said:
Root is possible without unlock, but no one is going to burn a root method on a phone with an unlockable bootloader. Get the model that unlockable.
Like previously stated this thread is moot. Warranty through Google or deal with a locked bootloader. End of story.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Root possible without bootloader unlock? You just changed the thread from moot to interesting. How would one do that?
bobby janow said:
Root possible without bootloader unlock? You just changed the thread from moot to interesting. How would one do that?
Click to expand...
Click to collapse
+1,000
https://www.xda-developers.com/verizon-google-pixel-2-bootloader-unlock/
Anyone tried this on a OG pixel yet?
baknblack said:
Anyone tried this on a OG pixel yet?
Click to expand...
Click to collapse
No I haven't yet, but if anyone hasn't when I get home, I'll try it.
ztotherad said:
No I haven't yet, but if anyone hasn't when I get home, I'll try it.
Click to expand...
Click to collapse
Just tried it. No love. It just sits there saying waiting for any device.
---------- Post added at 10:59 AM ---------- Previous post was at 10:26 AM ----------
baknblack said:
Just tried it. No love. It just sits there saying waiting for any device.
Click to expand...
Click to collapse
Fastboot is not recognizing my device for some reason. It's the factory cable. Will try another computer when i get home.
Finally got fastboot to work. The command just returns already locked. SOL
baknblack said:
Finally got fastboot to work. The command just returns already locked. SOL
Click to expand...
Click to collapse
damn.. and I wanted that badly!
edit: newest fastboot/adb and newest update on your pixel, correct?
ztotherad said:
damn.. and I wanted that badly!
edit: newest fastboot/adb and newest update on your pixel, correct?
Click to expand...
Click to collapse
Yeah, latest everything.
Sent from my Pixel using Tapatalk
My guess is the pixel can be unlocked in the same manner. It's a program bug in the latest version of fastboot. It will be easy for Google to patch it. However, if someone with knowledge of assembly language programing patched our version of fastboot to jump to the unlock routine on the pixel it should do the same thing.
Unfortunately I have no assembly language experience. Maybe someone that does could run with this.
Sent from my Pixel using Tapatalk
baknblack said:
My guess is the pixel can be unlocked in the same manner. It's a program bug in the latest version of fastboot. It will be easy for Google to patch it. However, if someone with knowledge of assembly language programing patched our version of fastboot to jump to the unlock routine on the pixel it should do the same thing.
Unfortunately I have no assembly language experience. Maybe someone that does could run with this.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
wonder what assembly language it'd use..
ztotherad said:
wonder what assembly language it'd use..
Click to expand...
Click to collapse
Assembly is raw machine code. It's the same on Linux or windows. I dabbled with it back in the early 80s but never could get the hang of it. A lot of good programmers use an assembly debugger to bypass software licenses. Ie, crack a program. They would run fastboot on a pixel 2 with the debugger run and watch to see what exact instructions were being passed between the phone and computer. Then patch the fastboot executable to issue the same code to the regular pixel. All this is pure speculation on my part and is based on the premise that the same bug exists in the fastboot binary on the regular pixel.
This is all above my pay grade, lol.
Sent from my Pixel using Tapatalk
baknblack said:
Assembly is raw machine code. It's the same on Linux or windows. I dabbled with it back in the early 80s but never could get the hang of it. A lot of good programmers use an assembly debugger to bypass software licenses. Ie, crack a program. They would run fastboot on a pixel 2 with the debugger run and watch to see what exact instructions were being passed between the phone and computer. Then patch the fastboot executable to issue the same code to the regular pixel. All this is pure speculation on my part and is based on the premise that the same bug exists in the fastboot binary on the regular pixel.
This is all above my pay grade, lol.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
yeah sounds like a bunch of gibberish to me lol. I'd love to figure out the way to get this to unlock it. it'd be worth it to me, but idk anyone that would know.
Yeah assembly is garbage to learn and understand and actually use but if you happen to find someone who knows it well enough they'd probably enjoy messing with this(especially if you throw a few bucks their way). No guarantee of the bounty actually being fulfilled but you never know what you may find when messing with such low level code