Related
Fastboot Mode
PRODUCT NAME - tuna
VARIANT - maguro 16gb
HV VERSION - 9
BOOTLOADER VERSION - PRIMELC03
BASEBAND VERSION - I9230XXLH1
CARRIER INFO - NONE
SERIAL NUMBER - XXXXXXXXXXXXXXXX
SIGNING - production
LOCK STATE - unlocked
When it says unlocked, is it talking about my SIM or my bootloader?
Do Nexus's come bootloader unlocked, I mean; they are dev friendly.
Don't make fun of me, I'm only curious and trying to start learning about android and maybe even develop things considering I do know alot about graphics.
Thanks in advance.
Edit: I forgot it meant bootloader (blonde moment?), but is this regular for nexus devices?
I'm almost certain it's talking about your bootloader but to be certain reboot your device. If you see an unlocked padlock under Google when you turn on your device your bootloader is unlocked.
063_XOBX said:
I'm almost certain it's talking about your bootloader but to be certain reboot your device. If you see an unlocked padlock under Google when you turn on your device your bootloader is unlocked.
Click to expand...
Click to collapse
Yeah it is, I know that; i edited my post after realizing that.
But what I'm asking is; Is it typical for nexus devices to come with unlocked bootloaders or not?
I got my from i wireless and I believe it is a imported device.
It's not. Probably was returned/refurbished.
Haaah.
What are the chances that it's rooted and how can I check?
I traded in my One S and got this phone as a replacement.
Strange that it came in the original boxing with everything.
Thanks man.
If it doesn't have superuser then it isn't rooted.
Thanks.
I'm gonna be a noob and ask one more question.
Is it easy to brick your phone from rooting?
Or SuperSU. Try rootchecker. "Is it easy to brick your phone from rooting?" Not from rooting but perhaps flashing if you tend to jump into things..
brainfart moments can give you a softbrick pretty easily, but with fastboot and (we arent quite fans of this like the fascinate people were) ODIN you would have to realllllly screw up and probably try to completely brick it. make sure you have fastboot set up and working correctly before doing anything questionable. it will save your ass lol
edit: speaking of fastboot, i would probably use it to format and reflash all partitions with the latest stock image before messing around since it sounds like your phone has been screwed with before you got it (you never know what other people did to it). theres a really good guide about resetting to stock in either the general or q/a section here. dont worry about relocking the bootloader, there isnt really a way to unlock it wrong... it either works or doesnt. since you sound pretty tech savvy, please dont use toolkits, learn fastboot. it seems like toolkits are a one click problem, not a one click fix lol.
electro` said:
Thanks.
I'm gonna be a noob and ask one more question.
Is it easy to brick your phone from rooting?
Click to expand...
Click to collapse
Practically impossible. You'd have to not read anything and then willfully do something to ruin your device. And even then it's almost certainly recoverable so not bricked.
It seems nearly impossible to brick your device. x.x
I installed ParanoidAndroid last nigh but for some reason I tried installing a mod and I lost the status bar and home buttons.
I was so pissed off, I had to unroot my device and reflash the stock rom.
I'm going to try using CyanogenMod 10.1 and see where it gets me. It will probably be better considering you can make alot more customizations to your device ui and such.
Thanks 063_XOBX.
My bootloader is still locked and I've never had root on this phone got it too late to unlock. I'd like to root and if I can get a custom recovery and flash a rom. Can anyone help?
Sent from my XT907 using Xparent Cyan Tapatalk 2
Gblake13 said:
My bootloader is still locked and I've never had root on this phone got it too late to unlock. I'd like to root and if I can get a custom recovery and flash a rom. Can anyone help?
Click to expand...
Click to collapse
Right now, there is no way to root or unlock the bootloader in your situation. It sucks, but it's where we are.
Don't hold your breath for an exploit, either. Motorola/Verizon closed all known holes for BL-unlocking in the penultimate Jellybean OTA, and the only root method that worked in the last JB no longer works here.
Enough with the KK unlock and root threads.
I'm going to start reporting people that make these threads without doing some homework first.
If you have a locked bootloader, you're pretty much up the creek without a paddle. End of discussion
If there is an exploit available, trust me, you'll know about it.
gtmaster303 said:
Enough with the KK unlock and root threads.
I'm going to start reporting people that make these threads without doing some homework first.
If you have a locked bootloader, you're pretty much up the creek without a paddle. End of discussion
If there is an exploit available, trust me, you'll know about it.
Click to expand...
Click to collapse
We can say this in every thread where they ask about root. We put warnings out prior to the OTA. Heck, we could probably put a sticky thread in this section about there being no root on KK, yet people will still ask. Why? Because they refuse to take 5 minutes to read through the other 37 KK related threads.
RikRong said:
We can say this in every thread where they ask about root. We put warnings out prior to the OTA. Heck, we could probably put a sticky thread in this section about there being no root on KK, yet people will still ask. Why? Because they refuse to take 5 minutes to read through the other 37 KK related threads.
Click to expand...
Click to collapse
I of course can't speak for anyone else, but I knew the risks well before taking the update, and updated anyway.
I knew it was the very un-XDA thing to do, but frustration with the short battery life and UI lag on my phone was nearing a breaking point.
I tried to make the most of it; hence the "list of changes" thread, which hopefully has scared away locked users who are still n JB.
Any luck with a rootkeeper/root survival of any kind?
pnwsr6 said:
Any luck with a rootkeeper/root survival of any kind?
Click to expand...
Click to collapse
Haven't seen it yet.
Strife89 said:
I of course can't speak for anyone else, but I knew the risks well before taking the update, and updated anyway.
Click to expand...
Click to collapse
My story is somewhat different. I tried to find a way to get rooted KK on my phone (trying to play junior hacker again), ended up soft-bricking my phone to where the only way to fix it was to flash stock KK using RSDLite (did try RSD'ing JB first, but my bootloader was having none of that).
So now I'm hopelessly stuck with a completely stock phone without root.
I feel like the only way to get past this is to attack it politically, like if every single Verizon XDA user banded together and flooded Verizon corporate inboxes with legitimate reasons why we need unlocked bootloaders.
Or maybe if someone is good friends with a politician who is more left of center and concerned about consumer rights over corporations. Maybe convince them that it's better for the environment because potentially millions of phones could be saved from going into landfills if we mandate companies must allow bootloader to be unlocked when certain conditions are fulfilled, like if a phone reaches 1-year of age.
Strife89 said:
I of course can't speak for anyone else, but I knew the risks well before taking the update, and updated anyway.
I knew it was the very un-XDA thing to do, but frustration with the short battery life and UI lag on my phone was nearing a breaking point.
I tried to make the most of it; hence the "list of changes" thread, which hopefully has scared away locked users who are still n JB.
Click to expand...
Click to collapse
I new I was losing root with it as well. I liked the features that KK brought with the update and still did it. The update finally got me using Smart Actions and I'm getting pretty decent battery life, nothing mind blowing, but pretty good. Buying a portable battery pack has pretty much solved the problem I had with nonroot. Now I can go about 2 days as long as I carry it around, lol. Luckily it's small.
if I have an unlocked BL, and the latest stock version on KK, how would I get root? Is it possible?
thanks.
Ahoalton said:
if I have an unlocked BL, and the latest stock version on KK, how would I get root? Is it possible?
thanks.
Click to expand...
Click to collapse
Flash a custom recovery via fastboot, and then flash SuperSU zip in recovery.
http://forum.xda-developers.com/moto-x/orig-development/root-4-4-x-pie-motorola-devices-t2771623 <-- this thread (not saying it works) is getting popular with Motorola devices. I attempted it myself and got errors just like some other people. Only difference is they still had root and I don't. I suggest following the thread and seeing if it does someday work for us or somebody could attempt it themselves. I'm currently on windows 8.1 so that could be a problem.
megaghostgamer said:
http://forum.xda-developers.com/moto-x/orig-development/root-4-4-x-pie-motorola-devices-t2771623 <-- this thread (not saying it works) is getting popular with Motorola devices. I attempted it myself and got errors just like some other people. Only difference is they still had root and I don't. I suggest following the thread and seeing if it does someday work for us or somebody could attempt it themselves. I'm currently on windows 8.1 so that could be a problem.
Click to expand...
Click to collapse
^^^He doesn't need an exploit since he has an unlocked BL. Also, this has been checked on the M and HD family of devices, it WILL NOT work because the the current KK updates have already patched the hole that this exploit is meant to take advantage of.
Ahoalton said:
if I have an unlocked BL, and the latest stock version on KK, how would I get root? Is it possible?
thanks.
Click to expand...
Click to collapse
Yes!.. Just use URL="http://androidhosting.org/Devs/Dhacker29/msm8960/CWM6049-RAZR-HD_M-KITKAT.img"]custom recovery[/URL] and flash Superuser zip
And what about aka test points? Many Motorola models had such special test points using which you could get unlock of BL. How about our XT907? Any ideas about test points or shortcircuit of contacts?
No need now! Towelroot will root stock KK, and what magic it does allows Motopocalypse to unlock BL again.
http://www.droid-life.com/2014/06/16/motorola-bootloader-unlock-razr-hd-towelroot/
Confirmed working!
Root and bootloader unlock!
Sent from my Droid RAZR M
GnatGoSplat said:
No need now! Towelroot will root stock KK, and what magic it does allows Motopocalypse to unlock BL again.
Click to expand...
Click to collapse
Towel Root only allows the root access that Motopocalypse needs. The old trust zone was accidentally (or purposely) put back into this OTA, that's what Motopocalyse exploits.
Sent from my HTC6525LVW using Tapatalk
RikRong said:
Towel Root only allows the root access that Motopocalypse needs. The old trust zone was accidentally (or purposely) put back into this OTA, that's what Motopocalyse exploits.
Click to expand...
Click to collapse
Ah, I see. Good to know. :good:
I just want to make sure that everything is crystal clear. I have spent weeks and many, many hours pouring over numerous, differing guides on how to root the 910V and run a custom 6.0+ ROM - all of them missing different vital chunks of information. Correct me if I am wrong:
You have to temp-root the device and quickly run an unlocking script written by an unknown source before the phone completely locks up and reboots itself. Then if you're lucky and the script is successful after 17 attempts and 4 battery re-charges, the stock 5.1.1 ROM will refuse to boot and you'll only be able to access the stock recovery with an "unlocked" flag on it. Then you'll go to install TWRP, try and flash a custom MM ROM only to find that wifi, camera, and all sensors don't work on any MM ROM without flashing the updated CPD1 bootloader firmware (this is not explicitly mentioned in multiple different guides for rooting and unlocking, including the official): Example here and here. Oh, and good luck using the thread search tool to find replies that mention this wifi issue in any of the 500 pages of replies that follow the official rooting and unlocking guide! The search tool has been broken for weeks and you'll get: "Sorry, we encountered an error processing your request. Please go back and retry or wait a minute. The Administrators have been notified of this error". Clearly Admins either aren't being contacted or don't care.
Then if you are repeatedly unsuccessful in flashing the updated bootloader firmware using the BPA1-CPD1 Hybrid Lollipop ROM developed by hsbadr in this guide, you might try and flash the stock 6.0+ bootloader firmware found here, (because you can't find anything with the broken search tool, it seems like a logical thing to do, and there are absolutely NO write-ups that mention extremely simple things - (like whether or not the updated stock VZW bootloader firmware will re-lock the bootloader.) However, if you do this, the bootloader re-locks itself, the phone bricks itself into a boot loop, and you have to factory flash VZW's MM ROM. If you manage to do that without completely losing your sanity, then you have to flash VZW's 5.1.1 ROM while on 6.0.1 firmware, which will take 6+ tries to get working and might not work at all. Then you have to boot into 5.1.1, re-temp root, quickly re-run the shady bootloader unlocker script before the phone force-restarts, go back to having an unbootable ROM, re-flash TWRP, then flash a custom 6.0+ ROM.
Am I understanding all of this right? I just want to make sure that I am not unaware of something, because god forbid anyone ever be unaware of something, lest this YOU DIDN'T READ!!! YOU DIDN'T READ!!!!! mantra get thrown around - as if any of you could seriously have the audacity to claim that these cluttered, fragmented guides on 15 different links represent some sort of fool-proof cohesive and coherent guide in your warped minds.
So am I missing anything? Some crucial step that I still might be unaware of? No? Great. Rant done. TL;DR: This process is waaaaaay too complicated for most people. I put myself in this category as a professional engineer that's rooted and flashed custom ROMs on many different phones.
notedroidbrokedroid said:
I just want to make sure that everything is crystal clear. I have spent weeks and many, many hours pouring over numerous, differing guides on how to root the 910V and run a custom 6.0+ ROM - all of them missing different vital chunks of information. Correct me if I am wrong:
You have to temp-root the device and quickly run an unlocking script written by an unknown source before the phone completely locks up and reboots itself. Then if you're lucky and the script is successful after 17 attempts and 4 battery re-charges, the stock 5.1.1 ROM will refuse to boot and you'll only be able to access the stock recovery with an "unlocked" flag on it. Then you'll go to install TWRP, try and flash a custom MM ROM only to find that wifi, camera, and all sensors don't work on any MM ROM without flashing the updated CPD1 bootloader firmware (this is not explicitly mentioned in multiple different guides for rooting and unlocking, including the official): Example here and here. Oh, and good luck using the thread search tool to find replies that mention this wifi issue in any of the 500 pages of replies that follow the official rooting and unlocking guide! The search tool has been broken for weeks and you'll get: "Sorry, we encountered an error processing your request. Please go back and retry or wait a minute. The Administrators have been notified of this error". Clearly Admins either aren't being contacted or don't care.
Then if you are repeatedly unsuccessful in flashing the updated bootloader firmware using the BPA1-CPD1 Hybrid Lollipop ROM developed by hsbadr in this guide, you might try and flash the stock 6.0+ bootloader firmware found here, (because you can't find anything with the broken search tool, it seems like a logical thing to do, and there are absolutely NO write-ups that mention extremely simple things - (like whether or not the updated stock VZW bootloader firmware will re-lock the bootloader.) However, if you do this, the bootloader re-locks itself, the phone bricks itself into a boot loop, and you have to factory flash VZW's MM ROM. If you manage to do that without completely losing your sanity, then you have to flash VZW's 5.1.1 ROM while on 6.0.1 firmware, which will take 6+ tries to get working and might not work at all. Then you have to boot into 5.1.1, re-temp root, quickly re-run the shady bootloader unlocker script before the phone force-restarts, go back to having an unbootable ROM, re-flash TWRP, then flash a custom 6.0+ ROM.
Am I understanding all of this right? I just want to make sure that I am not unaware of something, because god forbid anyone ever be unaware of something, lest this YOU DIDN'T READ!!! YOU DIDN'T READ!!!!! mantra get thrown around - as if any of you could seriously have the audacity to claim that these cluttered, fragmented guides on 15 different links represent some sort of fool-proof cohesive and coherent guide in your warped minds.
So am I missing anything? Some crucial step that I still might be unaware of? No? Great. Rant done. TL;DR: This process is waaaaaay too complicated for most people. I put myself in this category as a professional engineer that's rooted and flashed custom ROMs on many different phones.
Click to expand...
Click to collapse
The processes were easy enough...and some like me had temp root on first or second try. If you've spent weeks and weeks trying to figure this all out, I'm not sure anyone can help you. There are people in these threads that have answered every question you've brought up, and helped people get through. I know you must be some kind of troll with your "one post" and claiming you've been rooting blah blah blah....engineer...blah blah blah, you should be embarrassed by your lack of understanding and ability to root and unlock. Go read some of the dopey posts by people who can't follow instructions or put a sentence together, yet were successful! I guess what I'm saying is stfu and go away.
Sent from my SM-N910V using XDA-Developers mobile app
gcounts said:
The processes were easy enough...and some like me had temp root on first or second try.
Click to expand...
Click to collapse
You can follow all of the links I posted and verify that the information I have claimed is missing, is indeed missing. I have pointed out what is missing from where and concisely explained exactly why the process for this particular phone is dangerous without said information.
Congrats on your effortless unlock and custom ROM flash. Your anecdotal success and unsubstantiated claims regarding the successes of others does not make the process objectively "easy", nor straightforward. I have flashed custom ROMs onto many devices, and this one is the most complicated, convoluted, and frustrating of them all.
gcounts said:
you should be embarrassed by your lack of understanding and ability to root and unlock.
Click to expand...
Click to collapse
Ahhh, the "YOU DIDN'T READ!!!!" mantra begins! I don't know if you're aware of this, but failure is how things are learned. It's how more cohesive, better written guides surface, and it's how people like you enjoy a successful root and custom ROM. There are lots and lots of people who have ruined phones from attempting this process. I'd be willing to bet money that the people who developed these hacks certainly went through a couple.
notedroidbrokedroid said:
You can follow all of the links I posted and verify that the information I have claimed is missing, is indeed missing. I have pointed out what is missing from where and concisely explained exactly why the process for this particular phone is dangerous without said information.
Congrats on your effortless unlock and custom ROM flash. Your anecdotal success and unsubstantiated claims regarding the successes of others does not make the process objectively "easy", nor straightforward. I have flashed custom ROMs onto many devices, and this one is the most complicated, convoluted, and frustrating of them all.
Ahhh, the "YOU DIDN'T READ!!!!" mantra begins! I don't know if you're aware of this, but failure is how things are learned. It's how more cohesive, better written guides surface, and it's how people like you enjoy a successful root and custom ROM. There are lots and lots of people who have ruined phones from attempting this process. I'd be willing to bet money that the people who developed these hacks certainly went through a couple.
Click to expand...
Click to collapse
You know what? The people that wrote the guides did so out of the goodness of their hearts as have all of the people here that have helped others to root their phones. There's nothing like you coming in here and slapping those people in the face.
Perhaps they're not the best writers. I think it unlikely that writing is what they do for a living. But you know what? If you'd taken the time to read the entire threads, you would have seen every possible way to **** up and how to deal with it. But no. Assholes like you think there should be a one touch root because you're too ****ing lazy to learn a little bit about your phone. Sorry, bub. It didn't happen with this phone. It took almost 18 months to discover and develop the exploits that allowed us without developer editions to root our phones.
I should apologize. I should be sorry that you're too ****ing stupid to read through hundreds of posts on how to unlock a bootloader and root your phone.
Have you sent any money to the guys that developed the exploit? How much are you paying for any of what's here on this forum? STFU.
douger1957 said:
You know what? The people that wrote the guides did so out of the goodness of their hearts as have all of the people here that have helped others to root their phones. There's nothing like you coming in here and slapping those people in the face.
Perhaps they're not the best writers. I think it unlikely that writing is what they do for a living. But you know what? If you'd taken the time to read the entire threads, you would have seen every possible way to **** up and how to deal with it. But no. Assholes like you think there should be a one touch root because you're too ****ing lazy to learn a little bit about your phone. Sorry, bub. It didn't happen with this phone. It took almost 18 months to discover and develop the exploits that allowed us without developer editions to root our phones.
I should apologize. I should be sorry that you're too ****ing stupid to read through hundreds of posts on how to unlock a bootloader and root your phone.
Have you sent any money to the guys that developed the exploit? How much are you paying for any of what's here on this forum? STFU.
Click to expand...
Click to collapse
- Has anybody bothered to state that 40% of the battery charge disappears every time you run Kingoroot? Nope. Nowhere in the guides.
- Has anybody mentioned that the CPD1 VZW bootloader firmware is also locked and will not boot a ROM flagged as custom? Nope! Nowhere. You heard it here first!
- Has anyone examined the content of the BPA1-CPD1 hybrid 5.1.1 ROM to determine whether it contains OEM VZW firmware or a custom firmware revision developed by someone on this forum? No. Nobody has done that.
You don't have to "write full-time" to have good written communication skills. I could write a very respectable COMPREHENSIVE guide on the process involved, but do you know what would happen to it? The admins would never sticky it and it would get buried under a thousand other threads. Somebody decided that there can be ONLY ONE ["Official"] guide, even though the current one is a stupid, incoherent mess that's maintained by an OP who refuses to amend or add anything to it.
And lazy? At least I perused the source code before I blindly copied a script claiming to unlock my bootloader. I doubt you have the slightest clue on either how to look at it or what malicious code looks like.
Lastly and most importantly, you're a fool for being content with giving your money to a phone manufacturer that rails you in the ass for wanting more control over it. After I brought my Note 4 back from the grave, I bought a Nexus. You think donating your change to the Devs is going to fix this problem long-term when you give Samsung $800 to continue doing this to you? I don't have enough crayons to further explain to you what an idiot you are.
Ok as this really is nothing more then a rant I will close this up with a few passing thoughts.
Things like this are not meant to be done by the average guy. This is a developers site. So yes you are expected to do lots of research before you do anything.
Next. No one in their right mind uses that root process. The battery drain is it connecting to the internet and downloading what ever it is they use to root the device after then get your imei and store it.
Also lets leave the name calling for the playground or the next name that will be called is banned.
On Friday (1/6) I opened my freshly purchased pixel XL and was happy to see it was still on 7.1. Given the status of many of the how to threads for the XL (Op not fully updated), I struggled to unlock the bootloader. I left the SIM card in and activated the phone. I even punched in my wifi password and got to the "checking for updates screen" before I started to read everything. I eventually got through it an unlocked the bootloader, slapped TWRP on it and flashed root. So far so good...
Then I started to read through the pain of updating manually to 7.1.1. No thanks. Kind of annoyed, I went about my merry way and just decided I'd hassle through it when something really important mandated it.
Fast forward to today, I noticed a bunch of apps had updated over night and something just seemed odd. So I checked the phone build number and it was updated to 7.1.1. Horrified, I installed quickboot and rebooted to recovery without issue, including SuperSU providing it root....whew!
My question - How did I get the OTA without losing TWRP and root? From what I've read, if you side load the OTA updates, you have to flash it again. I'm on the latest TWRP (RC1) and I've updated SuperSU binaries the easy way.
EDIT- By the way, this is the Verizon version (can't beat $15/m no trade in).
Because sideloading an OTA is a different update. You took the incremental OTA, which is a lot smaller and doesn't include installing to partitions that will break root. When you sideload the OTA, it's a "full OTA" and includes much more.
I would strongly suggest you disable automatic system updates and only manually update from here on out. It's far more risky taking incremental OTA's while rooted and modified than sideloading an OTA yourself when you can control it and flash everything you need to not bootloop.
Consider yourself lucky that you took it and didn't bootloop. But you are even more lucky that you got a 7.1 from Verizon! Nice.
xnatex21 said:
On Friday (1/6) I opened my freshly purchased pixel XL and was happy to see it was still on 7.1. Given the status of many of the how to threads for the XL (Op not fully updated), I struggled to unlock the bootloader. I left the SIM card in and activated the phone. I even punched in my wifi password and got to the "checking for updates screen" before I started to read everything. I eventually got through it an unlocked the bootloader, slapped TWRP on it and flashed root. So far so good...
Then I started to read through the pain of updating manually to 7.1.1. No thanks. Kind of annoyed, I went about my merry way and just decided I'd hassle through it when something really important mandated it.
Fast forward to today, I noticed a bunch of apps had updated over night and something just seemed odd. So I checked the phone build number and it was updated to 7.1.1. Horrified, I installed quickboot and rebooted to recovery without issue, including SuperSU providing it root....whew!
My question - How did I get the OTA without losing TWRP and root? From what I've read, if you side load the OTA updates, you have to flash it again. I'm on the latest TWRP (RC1) and I've updated SuperSU binaries the easy way.
EDIT- By the way, this is the Verizon version (can't beat $15/m no trade in).
Click to expand...
Click to collapse
What pain of updating to 7.1.1.
xnatex21 said:
On Friday (1/6) I opened my freshly purchased pixel XL and was happy to see it was still on 7.1. Given the status of many of the how to threads for the XL (Op not fully updated), I struggled to unlock the bootloader. I left the SIM card in and activated the phone. I even punched in my wifi password and got to the "checking for updates screen" before I started to read everything. I eventually got through it an unlocked the bootloader, slapped TWRP on it and flashed root. So far so good...
Then I started to read through the pain of updating manually to 7.1.1. No thanks. Kind of annoyed, I went about my merry way and just decided I'd hassle through it when something really important mandated it.
Fast forward to today, I noticed a bunch of apps had updated over night and something just seemed odd. So I checked the phone build number and it was updated to 7.1.1. Horrified, I installed quickboot and rebooted to recovery without issue, including SuperSU providing it root....whew!
My question - How did I get the OTA without losing TWRP and root? From what I've read, if you side load the OTA updates, you have to flash it again. I'm on the latest TWRP (RC1) and I've updated SuperSU binaries the easy way.
EDIT- By the way, this is the Verizon version (can't beat $15/m no trade in).
Click to expand...
Click to collapse
I bought the verizon version a while back, unlocked the bootloader. Here is the thing now, when you unlock the bootloader, you'll be good. You can download the google factory images, and flash your phone to the latest version, then you can reflash twrp and super su again. You'll not use the ability to add TWRP everytime because restoring or flashing the images, vendor, even stock recovery does not lock the bootloader. You can also have a custom rom for a piece of mind flashed, I am currently on pure-nexus, which is great and stable for me. I understand if you want to stay fully stock. Did I make any sense to you?
toknitup420 said:
What pain of updating to 7.1.1.
Click to expand...
Click to collapse
Exactly. It doesn't get much easier than double clicking a flashall.bat.
toknitup420 said:
What pain of updating to 7.1.1.
Click to expand...
Click to collapse
spotmark said:
Exactly. It doesn't get much easier than double clicking a flashall.bat.
Click to expand...
Click to collapse
I guess I'm just used to downloading a rom and gapps on my phone, clicking reboot to recovery, wipe/flash/wipe (or just dirty flash). Involving a PC, downloading the latest twrp, supersu, rom and whatever the tool of the day, is a pain comparatively...not to mention having to read pages and pages of threads because the OP isn't up to date and one step that is buried is critical. I understand this may come across as ungrateful. It isn't meant that way. I appreciate the many thankless hours people are putting into this. But from a user point of view, jumping through the hoops and risking bricking a $800 phone because the steps aren't short and simple, doesn't have the same value as when it is easy.
xnatex21 said:
I guess I'm just used to downloading a rom and gapps on my phone, clicking reboot to recovery, wipe/flash/wipe (or just dirty flash). Involving a PC, downloading the latest twrp, supersu, rom and whatever the tool of the day, is a pain comparatively...not to mention having to read pages and pages of threads because the OP isn't up to date and one step that is buried is critical. I understand this may come across as ungrateful. It isn't meant that way. I appreciate the many thankless hours people are putting into this. But from a user point of view, jumping through the hoops and risking bricking a $800 phone because the steps aren't short and simple, doesn't have the same value as when it is easy.
Click to expand...
Click to collapse
It will change. This phone is very different, it's not as open during the boot process as it used to be. Going to take some time to pull it all together. You won't brick it. You may soft brick it but a factory image and flashall.bat will pretty much always save you.
xnatex21 said:
I guess I'm just used to downloading a rom and gapps on my phone, clicking reboot to recovery, wipe/flash/wipe (or just dirty flash). Involving a PC, downloading the latest twrp, supersu, rom and whatever the tool of the day, is a pain comparatively...not to mention having to read pages and pages of threads because the OP isn't up to date and one step that is buried is critical. I understand this may come across as ungrateful. It isn't meant that way. I appreciate the many thankless hours people are putting into this. But from a user point of view, jumping through the hoops and risking bricking a $800 phone because the steps aren't short and simple, doesn't have the same value as when it is easy.
Click to expand...
Click to collapse
The Pixels are a little trickier than Nexus devices of the past in terms of flashing stuff, but you'd almost have to TRY to brick the phone. As long as you keep your bootloader always unlocked, you will always have a way to restore it.
In the future, if you keep your stock recovery, you can sideload OTA's through ADB by downloading the OTA from the Google site, and then using adb sideload ota.zip inside recovery with sideload selected. Alternatively, you can download the entire factory image for the new version, use Notepad to edit the flash-all.bat to remove "-w" from the file - it's in the middle of a flash command - and it will prevent it from wiping your device. But it will wipe out all your system modifications, if you made any.
I hit a "no command" recovery bootloop once when I tried manually updating, and didn't think I'd be able to get out of it because even flash-all.bat was not working (insufficient space error) for no good reason, and no article online has the proper new manual fastboot flash commands for Nougat devices using seamless updates. I think I know the commands now, but the SkipSoft Unified Toolkit is a GREAT tool (simplifies a lot of modification processes for a lot of devices) and automatically flashed the entire factory image for me, fixing the device.
xnatex21 said:
I guess I'm just used to downloading a rom and gapps on my phone, clicking reboot to recovery, wipe/flash/wipe (or just dirty flash). Involving a PC, downloading the latest twrp, supersu, rom and whatever the tool of the day, is a pain comparatively...not to mention having to read pages and pages of threads because the OP isn't up to date and one step that is buried is critical. I understand this may come across as ungrateful. It isn't meant that way. I appreciate the many thankless hours people are putting into this. But from a user point of view, jumping through the hoops and risking bricking a $800 phone because the steps aren't short and simple, doesn't have the same value as when it is easy.
Click to expand...
Click to collapse
Updating this phone is easy as hell. You sound like someone who isn't willing to put in the effort to learn how to properly do this stuff. Using fastboot is extremely easy. To sit there and say jump through hoops is ridiculous. You won't brick you're 800$ device if you know what you're doing. And there's plenty of guides out there on how to use fastboot that a complete noob can understand. This stuff isnt meant to be short and simple. Don't modify you're device if you don't want to learn how to properly do it.
toknitup420 said:
Updating this phone is easy as hell. You sound like someone who isn't willing to put in the effort to learn how to properly do this stuff. Using fastboot is extremely easy. To sit there and say jump through hoops is ridiculous. You won't brick you're 800$ device if you know what you're doing. And there's plenty of guides out there on how to use fastboot that a complete noob can understand. This stuff isnt meant to be short and simple. Don't modify you're device if you don't want to learn how to properly do it.
Click to expand...
Click to collapse
Nice troll or you didn't read and understand what I wrote. Maybe typing it again will help you, the "noob" at comprehension. Looking at your username, I'm probably wasting my time though.
It's not easy compared to download, wipe, flash, wipe. Are you really questioning this?
The guides on XDA are riddled with one off steps buried pages into the thread. I know people are working on this in their spare time so updating a guide is grunt work compared to coding and compiling. But for someone who just got the phone and can't even set it up for fear of losing the ability to unlock their bootloader without reading every page of every thread, it's a bit much.
Did anyone make me do any of this? Of course not. But thanks for your permission to not do it going forward.
To everyone else who replied in this thread respectfully, thank you.
xnatex21 said:
Nice troll or you didn't read and understand what I wrote. Maybe typing it again will help you, the "noob" at comprehension. Looking at your username, I'm probably wasting my time though.
It's not easy compared to download, wipe, flash, wipe. Are you really questioning this?
The guides on XDA are riddled with one off steps buried pages into the thread. I know people are working on this in their spare time so updating a guide is grunt work compared to coding and compiling. But for someone who just got the phone and can't even set it up for fear of losing the ability to unlock their bootloader without reading every page of every thread, it's a bit much.
Did anyone make me do any of this? Of course not. But thanks for your permission to not do it going forward.
To everyone else who replied in this thread respectfully, thank you.
Click to expand...
Click to collapse
Troll? Seriously? Because you're a lazy user who doesn't want to put in the time and effort to properly mod you're device. Can't wait to see you're thread about help I'm soft bricked and don't know what to do. I only wanted you to take the time to learn everything so you don't mess up you're phone. But apparently you think it's too much of a pain. Enjoy you're future bricked phone.
Sadly this is what it's like on many xda threads.
One must read hundreds or in many cases thousands of posts to find out what could have been summed up on the op's original message with a simple 1-10 steps.
And if you call anyone out on it you get the backlash that you received in this thread. It's just the way it is here. Some nice helpful folks and many that just look for a fight.
This thread turned into a mess. All anyone with a Verizon model needs to know is that if you are on 7.1 you can unlock your bootloader. If you are already on 7.1.1 you can't unlock your bootloader and likely will never be able to.
Once you unlocked it you have nothing to worry about. It will ONLY get locked again if you yourself lock it via fastboot with the appropriate command. If you are not rooted and do not have twrp installed you will still get OTA notifications and be able to install just like you normally would. Your bootloader being unlocked has nothing to do with OTA updates.
I do agree with the previous post though. There's no denying that the pixel is different so things aren't as simple and we have some extra steps in order to keep root and twrp and also install updates. To whoever responded to him saying he was lazy is just looking for drama. Ignore it
rfranken said:
Sadly this is what it's like on many xda threads.
One must read hundreds or in many cases thousands of posts to find out what could have been summed up on the op's original message with a simple 1-10 steps.
And if you call anyone out on it you get the backlash that you received in this thread. It's just the way it is here. Some nice helpful folks and many that just look for a fight.
Click to expand...
Click to collapse
what's sad is you guys feel you shouldn't have to read like the people who has been around for years when there was no one to ask. Just should ask and get spoon feed help I just don't get it. I can build kernels from source Roms I do mad mods to my personal setup how did I learn by spending weeks of my time reading and learning. Guess I should have just come here begging for help instead right? And @toknitup420 works we me he can do pretty much everything I can do and people wonder why we don't post our work on XDA cause of users like in this thread. It's a shame entitled users are ruining XDA or users that think their entitled.
---------- Post added at 10:28 PM ---------- Previous post was at 10:26 PM ----------
xnatex21 said:
Nice troll or you didn't read and understand what I wrote. Maybe typing it again will help you, the "noob" at comprehension. Looking at your username, I'm probably wasting my time though.
It's not easy compared to download, wipe, flash, wipe. Are you really questioning this?
The guides on XDA are riddled with one off steps buried pages into the thread. I know people are working on this in their spare time so updating a guide is grunt work compared to coding and compiling. But for someone who just got the phone and can't even set it up for fear of losing the ability to unlock their bootloader without reading every page of every thread, it's a bit much.
Did anyone make me do any of this? Of course not. But thanks for your permission to not do it going forward.
To everyone else who replied in this thread respectfully, thank you.
Click to expand...
Click to collapse
By his username WTH does that mean? Smh
He has 420 in his username. Google it if you don't know the reference. Or do we need to "spoon feed" it to you?
Tigerstown said:
what's sad is you guys feel you shouldn't have to read like the people who has been around for years when there was no one to ask. Just should ask and get spoon feed help I just don't get it. I can build kernels from source Roms I do mad mods to my personal setup how did I learn by spending weeks of my time reading and learning. Guess I should have just come here begging for help instead right? And @toknitup420 works we me he can do pretty much everything I can do and people wonder why we don't post our work on XDA cause of users like in this thread. It's a shame entitled users are ruining XDA or users that think their entitled.
---------- Post added at 10:28 PM ---------- Previous post was at 10:26 PM ----------
By his username WTH does that mean? Smh
Click to expand...
Click to collapse
First off why don't you read before you make a post like this. Nothing bad or disrespectful was posted. The other person was simply talking about the pixel being more complicated then other devices and stuff like that. It was no indication of him being too lazy to read threads. Then your "boy" felt the need to comment and start useless drama twisting the other guys words. You sit here and say "this is why I left XDA" yet you are the one who just went out of your way to continue the pointless drama that started because neither you nor your friend can read. YOU and YOUR post are the reason people get fed up with this place. You are contributing to drama your friend started on a forum for a device you clearly don't even own. Didn't you say you left XDA? So why are you posting here? I'm sure you're "mad skills" would be more useful somewhere else. Seriously grow up and at least read and know the story before you comment.
aholeinthewor1d said:
First off why don't you read before you make a post like this. Nothing bad or disrespectful was posted. The other person was simply talking about the pixel being more complicated then other devices and stuff like that. It was no indication of him being too lazy to read threads. Then your "boy" felt the need to comment and start useless drama twisting the other guys words. You sit here and say "this is why I left XDA" yet you are the one who just went out of your way to continue the pointless drama that started because neither you nor your friend can read. YOU and YOUR post are the reason people get fed up with this place. You are contributing to drama your friend started on a forum for a device you clearly don't even own. Didn't you say you left XDA? So why are you posting here? I'm sure you're "mad skills" would be more useful somewhere else. Seriously grow up and at least read and know the story before you comment.
Click to expand...
Click to collapse
when did I say I left XDA? Your right I can't read get a clue I wonder how I program CNC machines everyday when I can't read. I didn't read the post I replied clearly.
---------- Post added at 01:05 AM ---------- Previous post was at 01:02 AM ----------
rfranken said:
He has 420 in his username. Google it if you don't know the reference. Or do we need to "spoon feed" it to you?
Click to expand...
Click to collapse
Yeah spoon feed it to me please!! Google it your funny I'm a grown man I partake in it myself as it's legal..Once again I still don't see the point of why his username has anything to do with it. You sound very butt hurt are you a snowflake?
Tigerstown said:
when did I say I left XDA? Your right I can't read get a clue I wonder how I program CNC machines everyday when I can't read. I didn't read the post I replied clearly.
---------- Post added at 01:05 AM ---------- Previous post was at 01:02 AM ----------
Yeah spoon feed it to me please!! Google it your funny I'm a grown man I partake in it myself as it's legal..Once again I still don't see the point of why his username has anything to do with it. You sound very butt hurt are you a snowflake?
Click to expand...
Click to collapse
Notice how every post you feel the need to try and brag? We just met you and we already know you build kernels, do "mad mods" to your phone, and you program CNC machines.. You both were looking for drama where the was none is the bottom line. So why not end it
aholeinthewor1d said:
First off why don't you read before you make a post like this. Nothing bad or disrespectful was posted. The other person was simply talking about the pixel being more complicated then other devices and stuff like that. It was no indication of him being too lazy to read threads. Then your "boy" felt the need to comment and start useless drama twisting the other guys words. You sit here and say "this is why I left XDA" yet you are the one who just went out of your way to continue the pointless drama that started because neither you nor your friend can read. YOU and YOUR post are the reason people get fed up with this place. You are contributing to drama your friend started on a forum for a device you clearly don't even own. Didn't you say you left XDA? So why are you posting here? I'm sure you're "mad skills" would be more useful somewhere else. Seriously grow up and at least read and know the story before you comment.
Click to expand...
Click to collapse
Wait I clearly don't own a pixel XL that's too funny you don't even know me yet you know what phone I own... I left XDA you said but I'm the one that can't read wow
This isn't a pixel XL :good:
Hi guys,
Got an M9 that updated to Nougat as soon as i laid hands on it. I have very few experience with the HTC world, and would like some information where should i head after here.
I'll definitely need root and am familiar with flashing through fastboot and unlocking through the HTC DEV Token.
I am also aware that a few flashing methods dont work with an unlocked bootloader, so currently i dont want to rush right there.
What is absolutely a myth to me, is S-OFF. Never managed to reach it in any device, and the way of getting it seems a bit unfair (sorry if it doesn't agree with anyone's views).
So this is what i have.
Status: LOCKED and S-ON
ROM: 7.0
Software: 4.16.166.1
Build: CL839204
CID: VODAP110
Baseband: 01.01_U114401011_117.00.61117G_2_F
Has Download mode available.
Thanks in advance.
Sad, sad to have found out that on XDA, barely any helper comes around the Help threads.
And even sadder to the fact that a certain feature to give control over the device have been monopolised in OEM fashion, adding a certain fee too.
The loop of options:
YOU CAN ONLY:
Unlock the device officially, temper with custom roms and recoveries.
The moment you want the benefits of a newer release (baseband, etc), one needs to relock back, that means backing up, go through wiping and locking and back.
YOU CANT:
Certain features that depend on S-OFF. From changing phones origin to updating without bothering locking or not.
Long story short, you cant do anything useful without reaching the pocket.
This concludes as my last HTC phone ever.
PlutoDelic said:
Sad, sad to have found out that on XDA, barely any helper comes around the Help threads.
Click to expand...
Click to collapse
I can only speak for myself but I'm not online 24/7. I answer if and when I have time for answering. Then you need to be aware that the M9 forum never was that active and the user base is even decreasing since the phone is already older than two years. If you expect fast replies, then a not so active device forum is definetely the wrong place for asking a question.
Aside from that, there's the ReadMe thread that got pinned at the top of the General and the Q&A section. It contains all answers to your questions. After all the time that I'm maintaining that thread I still don't understand why people prefer creating a new Q&A thread instead of reading what already got written.
PlutoDelic said:
And even sadder to the fact that a certain feature to give control over the device have been monopolised in OEM fashion, adding a certain fee too.
Click to expand...
Click to collapse
Please, not that discussion, again. S-OFF is absolutely not needed for using this phone. It's optional.
PlutoDelic said:
Unlock the device officially, temper with custom roms and recoveries.
The moment you want the benefits of a newer release (baseband, etc), one needs to relock back, that means backing up, go through wiping and locking and back.
Click to expand...
Click to collapse
Incorrect. If you had read the ReadMe thread you would know that relocking is absolutely not needed (and even not recommended). Not to forget that this phone is EOL. If you update to the latest version before starting to tinker you will never have to deal with this "problem" of getting back to stock. Aside from that, it was Google that introduced the block-based OTAs with android 5, not HTC. You'll face the same "problem" with every phone that gets shipped with android 5 or newer.
PlutoDelic said:
YOU CANT:
Certain features that depend on S-OFF. From changing phones origin to updating without bothering locking or not.
Long story short, you cant do anything useful without reaching the pocket.
Click to expand...
Click to collapse
Not sure how you define useful but rooting and installing custom roms is working fine without S-OFF. Most M9 owners have never heard of xda, rooting or custom roms and the majority of the rest doesn't need more than what they already can achieve with S-ON. (The part with the locking already got corrected above.)
Flippy498 said:
I can only speak for myself but I'm not online 24/7. I answer if and when I have time for answering.
Click to expand...
Click to collapse
Obviously, i have the same experience on a few Samsung threads, very understandable, although rare does someone have such enthusiastic reply for something positive. But anyway, i'll throw a thanks as i am not here for cynicism or arrogance.
Flippy498 said:
Then you need to be aware that the M9 forum never was that active and the user base is even decreasing since the phone is already older than two years.
Click to expand...
Click to collapse
Very well noticed.
Regarding S-OFF, i "just" need it, and was very much disappointed with the solution.