Develop Bugs

[Q] FB Mode question

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.

Do google know that we've unlocked the bootloader?

Do google know that we've unlocked the bootloader? (as Sony do as they ask for email adresses etc and confirm the ulock)
Wondering about warranty.

there is a notice about unlocking of bootloader may violate warranty . thing is it is stated in a somewhat vague manner, it is not like CAUTION YOU ARE ABOUT TO VIOLATE WARRANTY but rather worded like you may be in violation of warranty. anyway, i think it does violate and yes there is most likely a software switch that sets a value in hardware register which can be recovered to determine that the bootloader was unlocked. if you have the least bit of concern do not unlock.

dkryder said:
there is a notice about unlocking of bootloader may violate warranty . thing is it is stated in a somewhat vague manner, it is not like CAUTION YOU ARE ABOUT TO VIOLATE WARRANTY but rather worded like you may be in violation of warranty. anyway, i think it does violate and yes there is most likely a software switch that sets a value in hardware register which can be recovered to determine that the bootloader was unlocked. if you have the least bit of concern do not unlock.
Click to expand...
Click to collapse
Ok thanks.
One last google noob question; does rooting usually need an unlocked bootloader?
On xperia root is more difficult to achieve with a locked bootloader, but can be done, thanks to the devs.
I guess I will read the 6P thread to get a feel for the situation.
Cheers again.

i do not know if it is possible, in practice as far as i know it is necessary to unlock if any modification is wanted. recently it is popular to gain root without mod of /system partition. hopefully that is what is achieved with the pixel c.
edit: never done this but, fastboot boot recovery recovery.img then flash a superuser from temp recovery. however it seems you would still be restricted from mod of /system
in future.

dkryder said:
i do not know if it is possible, in practice as far as i know it is necessary to unlock if any modification is wanted. recently it is popular to gain root without mod of /system partition. hopefully that is what is achieved with the pixel c.
edit: never done this but, fastboot boot recovery recovery.img then flash a superuser from temp recovery. however it seems you would still be restricted from mod of /system
in future.
Click to expand...
Click to collapse
If you use fastboot boot then you do not need to specify a partition (only if using fasboot flash *partition* image.img).
The device is still very new but im sure a custom recovery will be released soon so an easy root can be achieved.
MArk.

mskip said:
If you use fastboot boot then you do not need to specify a partition (only if using fasboot flash *partition* image.img).
The device is still very new but im sure a custom recovery will be released soon so an easy root can be achieved.
MArk.
Click to expand...
Click to collapse
I sure hope so. That's one of the only things keeping me from buying it already. It's kind of worrisome that the development forums are almost completely dead (save for the one thread trying to get root without a custom recovery, of course). I guess I'm just spoiled by using only Nexus devices, so having very active development is usually the norm.

well, the thing was only a rumor about sales start up until a report in a german site on 12/5 or so that sales would start 12/8 and then on 12/8 a confirm that at 1pm eastern u.s.a. sales would begin. talk about giving people a decent notice about a device this pixel c was a new low for google. it's almost they decided to sell them as android tablet at last moment instead of tossing in trash as a complete failure as chrome os tablet so, yeah, it will take a while for anyone that has skill to develop this device to ante up the funds and take delivery. if bootloader remains locked and boot temp recovery to flash supersu does that restrict the root in any way? i am just curious about this as my bootloader is unlocked.

Losing features upon bootloader unlock/root?

Hey everyone,
I've tried to google around and search the forums on XDA but there is no straight up answer to some questions I have. This is the first HTC device I own and although I have been rooting/unlocking devices since the Nexus 4, I am afraid to go ahead with this one. I just wanted the answers to the following questions, if anyone here knows them please:
1. Unlocking the bootloader seems straight-forward and supported by HTC. I'm in the UK which means no Uh-Oh protection. If something was to happen to the device and I sent it back under warranty, would I be ****ed or would HTC replace/repair it? HTC UK's call center was worse than useless and HTC US' policy doesn't apply to us so I thought I should ask here.
2. Does unlocking the bootloader and rooting mean I will lose access to the fingerprint scanner, camera quality or anything 'stock'? I know Android Pay won't work but at the moment I am not too bothered either way because it's a hit and miss thing with it.
3. Finally, is there a way to completely revert unlocking the phone/s-off and going back to S-ON/Locked without any signs of having messed around with the device? I ask in relation to question 1. If unlocking the bootloader voids the warranty for UK users, is there a way to go back to stock and make the phone as though NOTHING was done to it?
Thank you to anyone who helps answer even 1 of these questions :victory:. I want to root and get xposed onto my new device but not at the cost of losing features on a brand new phone or losing warranty on it either :silly:

1. I can't comment on this simply because I don't know and don't want to spread false information.
2. You will not lose any features at all. In fact, I'm running a bootloader unlocked and rooted setup and Android Pay still seems to work fine for me. It let me add a debit card but I haven't yet been able to actually try to purchase something.
3. Yes, if you are S-Off you can completely revert back to a locked bootloader with S-On if you want to.
I'd recommend both unlocking and S-Off so you can revert back to stock in the future for a warranty claim just to be safe.

jaredkzr said:
1. I can't comment on this simply because I don't know and don't want to spread false information.
2. You will not lose any features at all. In fact, I'm running a bootloader unlocked and rooted setup and Android Pay still seems to work fine for me. It let me add a debit card but I haven't yet been able to actually try to purchase something.
3. Yes, if you are S-Off you can completely revert back to a locked bootloader with S-On if you want to.
I'd recommend both unlocking and S-Off so you can revert back to stock in the future for a warranty claim just to be safe.
Click to expand...
Click to collapse
Hey, thanks for the reply! Only just saw this, not sure why it didn't notify me.
Right no worries about point one seeing as point 3 makes it irrelevant if I can revert back and save my warranty anyway. Just to be sure on points 2 and 3, I can definitely 100% go back to Locked/S-On status and the system won't show I have messed around at all? As for Android Pay, that's cool! Did you set it up before or after rooting? And does your fingerprint scanner work? Can you make payments on google play by authorising with your fingerprint?
Thank you again for your help!

Devzz said:
Hey, thanks for the reply! Only just saw this, not sure why it didn't notify me.
Right no worries about point one seeing as point 3 makes it irrelevant if I can revert back and save my warranty anyway. Just to be sure on points 2 and 3, I can definitely 100% go back to Locked/S-On status and the system won't show I have messed around at all? As for Android Pay, that's cool! Did you set it up before or after rooting? And does your fingerprint scanner work? Can you make payments on google play by authorising with your fingerprint?
Thank you again for your help!
Click to expand...
Click to collapse
Yep, you can definitely 100% go back to Locked/S-On state assuming you were previously S-Off. There will be no signs that the device was messed with.
For Android Pay, I had initially set it up prior to rooting but the rooting process wiped my phone. I had no issues setting it up again on a freshly rooted install.
Google Play and every other app that uses it still fully supports authorization via fingerprint. From what I can tell, I have lost absolutely no features by rooting. There really is nothing to lose once you get past the initial phone wipe that occurs when you unlock the bootloader.

jaredkzr said:
Yep, you can definitely 100% go back to Locked/S-On state assuming you were previously S-Off. There will be no signs that the device was messed with.
For Android Pay, I had initially set it up prior to rooting but the rooting process wiped my phone. I had no issues setting it up again on a freshly rooted install.
Google Play and every other app that uses it still fully supports authorization via fingerprint. From what I can tell, I have lost absolutely no features by rooting. There really is nothing to lose once you get past the initial phone wipe that occurs when you unlock the bootloader.
Click to expand...
Click to collapse
Ah that's great! Would've thought HTC would implement some kind of security thing where rooting may cause the fingerprint scanner to not work like Samsung/Sony have. Good on HTC :highfive: I'm gonna start reading up now and unlock/s-off/root the phone in the next few hours! :fingers-crossed:

Devzz said:
Ah that's great! Would've thought HTC would implement some kind of security thing where rooting may cause the fingerprint scanner to not work like Samsung/Sony have. Good on HTC :highfive: I'm gonna start reading up now and unlock/s-off/root the phone in the next few hours! :fingers-crossed:
Click to expand...
Click to collapse
Yeah, it really is a great thing they've done! HTC is being really friendly to developers and power users. If you have questions or need some help with the unlocking or rooting feel free to drop me a PM!

Help - Bricked HTC m9 - Not rooted - Advice needed -

Hi,
My wife HTC m9(UK, Vodaphone, latest stock ROM, No root) was turned off last night to charge.
When booted up it does the below. It does not load into the OS. Every boot loops into the below.
https://drive.google.com/file/d/0B8n21CQX7535cjF4MnZqV2E1dGM/view?usp=sharing
It says the software has been modified?
My wife was very insistent that I never root or change ROMS on her phone.
Does anyone have a fix or is this send off for replacement?
Any advice would be greatly appreciated.
Thanks
Ca1v

ca1v said:
Hi,
My wife HTC m9(UK, Vodaphone, latest stock ROM, No root) was turned off last night to charge.
When booted up it does the below. It does not load into the OS. Every boot loops into the below.
https://drive.google.com/file/d/0B8n21CQX7535cjF4MnZqV2E1dGM/view?usp=sharing
It says the software has been modified?
My wife was very insistent that I never root or change ROMS on her phone.
Does anyone have a fix or is this send off for replacement?
Any advice would be greatly appreciated.
Thanks
Ca1v
Click to expand...
Click to collapse
What happens if you try to boot to Download Mode? I guess you see the black screen that is mentioned in Q7, right? If that's the case there isn't much you can do...

Download mode seems to be working (https://drive.google.com/file/d/0B8n21CQX7535cEFhTlpnajF5anM/view?usp=sharing)
If this is the case, can you point me in the right direction to get resolved?
Many thanks for the help

Flippy498 said:
What happens if you try to boot to Download Mode? I guess you see the black screen that is mentioned in Q7, right? If that's the case there isn't much you can do...
Click to expand...
Click to collapse
Download mode seems to be working (https://drive.google.com/file/d/0B8n...ew?usp=sharing)
If this is the case, can you point me in the right direction to get resolved?
Many thanks for the help

Interesting. Your video in post 1 shows a security warning. That means that the OS got deleted. This is only possible if you unlock the bootloader and delete it manually via TWRP or if the EMMC gets broken. Since the phone's S-ON and its bootloader is locked and not unlocked or relocked I assumed that the latter happened*.
As long as the download mode is working you can restore the system with the help of a RUU. Instructions can be found in the thread I linked in my last post. Be aware that all data on the phone is going to get erased.
* Well, it is possible to get the phone's status back to S-ON and locked with S-OFF but you said you never tinkered with that phone...

Flippy498 said:
Interesting. Your video in post 1 shows a security warning. That means that the OS got deleted. This is only possible if you unlock the bootloader and delete it manually via TWRP or if the EMMC gets broken. Since the phone's S-ON and its bootloader is locked and not unlocked or relocked I assumed that the latter happened*.
As long as the download mode is working you can restore the system with the help of a RUU. Instructions can be found in the thread I linked in my last post. Be aware that all data on the phone is going to get erased.
* Well, it is possible to get the phone's status back to S-ON and locked with S-OFF but you said you never tinkered with that phone...
Click to expand...
Click to collapse
Just thought I'd bring to your attention that apps are now being written that will try to obtain root without you knowing. The reason is that they can steal any information they want and sell it to corporations for as little as 4 pence/6c a record.
It is possible that it is a failed root by an app.
"I'm safe, I only download my apps from google playstore" - nope, you're not.
"I only use signed apps and the checksum is always correct" - nope, checksum can be matched with padding.
"I only use external sources to update genuine apps" - nope, see the Google playstore comment above.
"I have all my security and privacy set to super strict, I have my apps verified by google" - nope, still not secure because alerts are only written when the malicious/bad code is found.
Be warned, my fellow xda'ers. There is a whole new breed of security breach and it is terminal to root as a whole. Apps like kingoroot etc are issuing the wrong type of people with the wrong type of information and they are using it for the wrong purposes.
Google will stuggle to put a lid on these types of apps because they attack the hardware for access to software (a simple memory buffer overflow attack), inject a few lines of code and you're in, permanently. It will eventually result in a total lockdown at the manufacturer and bye bye root access, roms, mods etc, you'll get what you're given.
How do we prevent this?. We don't and we can't. We just have to sit back and watch as the world takes our privacy while bricking our devices one by one just to "try" to earn a poxy 4p.
Beamed in by telepathy.

@shivadow: I'm actually not sure what you're trying to achieve with your post. Malicious apps that can root your device without letting the user know about that exist since several years now. (Click here for a random example from 2011) Smartphones aren't completely safe and they never were. Everyone who's claiming the opposite either doesn't know what he/she is talking about or is simply lying.
To name just a few more android security flaws/exploits that emerged in the past: rageagainstthecage, gingerbreak, heartbleed, stagefright, the master key vulnerability, the futex bug, rootnik...
All of these have more or less been used for manipulating android phones. There is no absolute security. Android is still as secure/insecure as it's always been.
In addition, several OEMs are already trying to prevent their customers from rooting their phones since several years. Samsung's KNOX is a perfect example. (I don't want to discuss whether they're successful. That's a whole different topic.)
But let's get back to the deleted OS of the OP's phone: I've never heard about failed root attempts that erase a complete system partition. Therefore, I highly doubt that a malicious app caused all the trouble. Failed root attempts may cause a bootloop but they don't wipe your phone. Just think about the following: How should the dev of such app gain money if the app deletes OSes? Without OS there is no information you can steel and if you have no information you could sell/abuse/whatsoever you don't gain any money. Oh and not to forget that most apps on the play store already collect more than enough data from your phone they can sell afterwards without having to root it.

I meant failed root could be the cause, if the op didn't then who did?. If no-one modded it then dead nand is the only player..
I agree with every thing else but I don't trust those apps that try to gain root in the background to steal data and I think it's too easy for them to bugger your phone just for the sake of making a few coins. Face it, if I was doing it, once I had what I wanted I wouldn't care about the device. Sod the gracious exit and all that jazz.. No evidence, no conviction.
Maybe I'm being ott but my questions and points are still valid.
This is a proper "who dunnit" because I doubt it died of its own accord.
Knox is for businesses btw. If knox is triggered, which is very easy to do, the business is advised not to buy the device as it "may" have been compromised. But if no company secrets are being held on the device then it's still good to use. Knox protection was counteracted by supersu. In a nutshell, unless you run a company knox is of no concern to the everyday user.
Just thought I'd chuck that in there, I'm versed in the arts of the s3 i9300. I moved from that phone to this m9.
Beamed in by telepathy.

Should I unlock my bootloader for safety reasons

I've always had my devices rooted and running a custom rom or at least a custom kernel or something of the sort "But" ever since I got my pixel about a year ago I haven't felt the need to root at all, stock rom is just perfect and so battery life and I don't see a reason to.
However I was just thinking that now with locked bootloader if for any reason my phone gets bricked then I'm probably [email protected]*t out of luck because I won't be able to flash a factory image to bring the phone back to life.
Should I unlock my bootloader just in case the worse does happen or is there another workaround for such a situation?

Getting bricked is the direct result of flashing images.

nabbed said:
Getting bricked is the direct result of flashing images.
Click to expand...
Click to collapse
I could not disagree more. There are countless threads of individuals taking OTAs and running into boot loop. Additionally I have read through multiple threads where individuals were simply using their phone to play a game, text, phone call etc and the phone shuts off and goes into a loop.
The users with an unlocked bootloader were able to salvage the device. Users without a locked bootloader looked for a RMA.
To the OP- I personally will never own an Android device with a constantly locked bootloader. The safety net of being able to factory reset and flash stock images is something I've always cherished and do not wish to get rid of.
There are security risks to having an unlocked BL. If an Android savvy criminal were to steal your device they could do a lot of damage with obtaining personal information. For me, I'm much more worried about my phone going in to boot loop than I am some criminal being able to take my phone from me.

Sab3elbromba said:
Should I unlock my bootloader just in case the worse does happen or is there another workaround for such a situation?
Click to expand...
Click to collapse
if for any reason, something did get corrupted on your phone with a lockedbootloader and it tripped verified boot. you would be locked out, no course of action but to get an RMA... so if u plan on tinkering with your phone or just would like a failsafe, at least with an unlocked phone. you would be able to flash firmware, etc...
just remember, not to relock your bootloader; unless your phone is running stock firmware and is wiped.... otherwise you will trip verified boot and brick it...
nabbed said:
Getting bricked is the direct result of flashing images.
Click to expand...
Click to collapse
no, it's not. getting a bricked phone is pretty much always because the person did something ill advised or dumb... like relocking their bootloader running custom firmware...
so a diect result of user error, nothing to do with flashing images.