Database Info

[Q] Root on 30O

I have just received my new phone... updated to the 30O OTA. Is there anyway for me to obtain root without unlocking the bootloader or flashing custom recovery??
Thanks!

You'll need to unlock your bootloader and flash a custom recovery.
No way around that, on XNPH25R there was a way. I don't really follow the whole "root without unlocking", but if you're going to obtain root etc.. just unlock your bootloader. I've said this analogy many times,
On a OPO (or Nexus Device or HTC), we have a way of unlocking our bootloaders without the need of a exploit to gain root access (e.g. Samsung, LG, etc). Think of it this way, since we have a OPO... you're pretty much given a key (fastboot oem unlock) to unlock the doors to your house. Don't make it difficult on yourself and break into your house through your windows when you can just unlock the door with the key you have.
Besides, OnePlus gave you the option to make your life easier, just unlock it it'll make your life easier.

Rooting Moto G LTE (XT1045) without unlocking Bootloader?

I would like to keep my limited Motorola warranty. So I don't want to unlock the bootloader.... I just want root for basic things. But rooting this phone seems twice as difficult than my Galaxy S5.
I've searched around and found temp root methods. But no permanent ones.
I wouldn't mind unlocking the bootloader if it could be locked again and Motorola wouldn't know.
So I could use some help/guidance.
Thanks
Sent from my SM-G900V using XDA Free mobile app

xmguy said:
I would like to keep my limited Motorola warranty. So I don't want to unlock the bootloader.... I just want root for basic things. But rooting this phone seems twice as difficult than my Galaxy S5.
I've searched around and found temp root methods. But no permanent ones.
I wouldn't mind unlocking the bootloader if it could be locked again and Motorola wouldn't know.
So I could use some help/guidance.
Thanks
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
Sorry bro, when you wish to unlock the boot loader, you send your device id to Motorola, so even if you relock the bootloader, they'll still have it in their records....
To get permanent root, the only current method is through unlocking the bootloader to be allowed to flash root.
Cheers

I used to worry about warranty too.
Now I just don't care anymore, and I've never regretted unlocking, on some 25+ test devices now.
If the device was returned to a store, I don't think they'll check Moto's database.
If I was worried about a bootup warning, and I didn't feel there were any moral issues (device is broken already anyway), I would just brick the phone. They can recover from that at the service centre anyway.
I DID return a phone to a store once which would not boot at all. They FREAKED out because they said they needed to boot it to see a number. Maybe they were just looking for tamper evidence, I don't know.
Anyway, that's 40 minutes of my life (plus the drive) I'll never get back, because they could not follow the normal return procedures.
And in the end they had to accept the return of course. You'd think they must have had SOME returns of completely dead phones before...

[Q] Z3 Root Reality Check

I've been watching the developer board regarding the root and locked bootloader issue, and I've spent hours researching this and have yet to find a solution that's known to work without loss of something, likely a permanent or semi permanent loss. My device is a Z3 model D6616. I'm unhappy with the phone for several other reasons, but haven't owned an un-rooted phone for some time, and prefer keeping this phone if I can root it successfully. Root with stock firmware is my objective and am only interested in responses from people that have themselves rooted (and dealt with bootloader issues) a Z3.
- Root phone installing current T-mobile stock firmware.
- Known loss of function: Sony DRM dependant features/funtion only (from memory, mostly related to camera low light performance and DRM playback issues)
- Other loss of function experienced with stock features, or any other problem with any other app. Especially concerned with root dependant features of Play apps? Also ad blockers?
- Waranty loss (potential) and loss of OTA updates understood.
- Feature/function loss with workarounds or fixed that survive power cycle?
- Expect permament bootlocker inability to relock
- A link to the specific process you used, any problems you encountered whatever the cause. For example it usually takes me at least 3 attempts to root using any complex process, and I always read through 5 times before starting and download every needed file and program in advance.
Again: Sony Xperia z3 D6616 T-mobile
Firmware: 4.4.4 23.0.3.1.123
Software: D6166 R16B
In the past, I've had the most problems when an understood part of a process is not explicitly stated, or I've ignored or misunderstood a step. Plugging and unplugging from usb to PC a typical example. I don't have the technical know how to critique or ignore, so always attempt to follow all instructions without variance. I've had some problems, and most were solved by starting the process again. I hesitate to ask for help since the last time I did that I was attacked for witholding information when asked if I had backed up the phone. Since i didn't have access to the PC at the time of the question I honestly answered I didn't know (since I had attempted to but couldn't confirm). If you've ever answered a question here implying the request or requester is stupid or dishonest, I'm fully aware of my ignorance and my own integrity, and other personality traits, so please ignore this request, which accepts my lack of knowlege and has no tolerance for your issues not previously resolved through your own peaceful and respectful process.
Please only respond if you have personally rooted this specific phone model. If you have not, but know someone who has, please ask them to review this post and respond.

Nobody has rooted this phone without unlocking the bootloader. If you unlock to root, you will permanently lose DRM keys from the TA partition with no way to recover. No current root method works on 4.4.4 on the Z3. No one knows when or if an exploit will be found. We all want root. If you want it now, unlock the bootloader. If you can wait, wait. It's your call either way. As soon as a root method surfaces, best believe it will be in these forums. I'll be waiting with you...

First of all, check *#*#7378423#*#* to see if you bootloader can be unlocked or not.
Coz I think 6616's bootloader is unlockable.

freddy1991 said:
First of all, check *#*#7378423#*#* to see if you bootloader can be unlocked or not.
Coz I think 6616's bootloader is unlockable.
Click to expand...
Click to collapse
This is true. D6616 owner here, T-MO not unlockable yet :/ eagerly awaiting root as well as I really enjoy the z3, maybe even more than my Nexus 6 (gasp, blasphemy!)

Thanks For the Responses
freddy you addressed my concern, exactly. My phone reports:
Rooting Status:
Boot Unlocker Allowed: No
Although variants of the z3 have been bootlocker unlocked and rooted, I have not found a clear claim that was successfully done with D6616 z3. Since I'm a new T-mobile customer, this and their attitude about it are a poor way to start. I have a HTC phone I haven't returned, maybe I can get them to take the Z3 back instead. While I have benefited from and appreciate the great work so many people have done to make our phones usable and available to us, I've seen how carriers, mfgs, and users push good phones to market crippled by junk and unecessarily locked down. it's time to consider the mamufacturers that have been successful building good phones and selling in places like China at much lower prices.
Regarding any loss of DRM, I couldn't care less. This phone takes worse low light photos and video than my rooted Samsung G3, making it functionaly useless to me. Add to that the lack of a rational UI for telephony and IM, and done with Sony.
To be clear, if the bootloader can be unlocked and the phone can be rooted and you have done this yourself, please post.

Well...
I think there is no way you could unlock the bootloader of 6616.
The only way is to wait for the root on locked bootloader.
Check here http://forum.xda-developers.com/showthread.php?t=2940539
But that means you have to stick in the .93 firmware, even if the exploit is also usable for Z3.
Or return your 6616 and buy a 6603 or 6653 variant.

BREAKING NEWS
http://forum.xda-developers.com/crossdevice-dev/sony/giefroot-rooting-tool-cve-2014-4322-t3011598

Man, No bootloader unlock = Useless phone

HORiZUN said:
BREAKING NEWS
http://forum.xda-developers.com/crossdevice-dev/sony/giefroot-rooting-tool-cve-2014-4322-t3011598
Click to expand...
Click to collapse
Nope.
http://forum.xda-developers.com/showpost.php?p=58468332&postcount=815

I'm similarly confused about this whole thing, this new Giefroot program means we can all potentially get root for our devices, but we still lose the DRM keys right? So that means we can never have the Sony camera/image processing processes back again right?

Thwwack said:
I'm similarly confused about this whole thing, this new Giefroot program means we can all potentially get root for our devices, but we still lose the DRM keys right? So that means we can never have the Sony camera/image processing processes back again right?
Click to expand...
Click to collapse
NO
Unlocking the bootloader = loss of DRM
Rooting that does not involve unlocking the bootloader means you keep the DRM keys

gregbradley said:
NO
Unlocking the bootloader = loss of DRM
Rooting that does not involve unlocking the bootloader means you keep the DRM keys
Click to expand...
Click to collapse
Thanks, I'm new to Android and this is all over my head. To clarify, Giefroot does this without unlocking the bootloader?
It's all pretty frustrating, I gotta say... I'd love to install Cyanogenmod on this, but losing key features on the device is a pretty harsh trade off.

Thwwack said:
Thanks, I'm new to Android and this is all over my head. To clarify, Giefroot does this without unlocking the bootloader?
It's all pretty frustrating, I gotta say... I'd love to install Cyanogenmod on this, but losing key features on the device is a pretty harsh trade off.
Click to expand...
Click to collapse
Yes, giefroot does not unlock the boot. There is only one way to do that and that is to obtaining the code from sony and fastboot it either manually or using flashtool.

Delete

Flash Google store Pixel image over Verizon Pixel phone???

Hey guys, I'm wondering if anyone has done this, or knows if it's possible to (after unlocking bootloader) flash the Google stock Pixel system image instead of the Verizon one? I'm assuming the hardware and firmware are identical, but am not sure and am not skilled enough (or at all) in code to know if its possible. I bought my phone through Verizon, only because nowhere else had stock. I use it on T-Mobile, but fear there may be some behind the scenes Verizon stuff going on that may hinder my phone on T-Mobile. I haven't experienced any issues yet, but with the Nov security update mentioning a specific fix for wifi calling in New Mexico only on the Verizon pixels, it makes me weary that there is more happening beneath the surface than I am aware of. Thanks for any and all help! Appreciate it.

newbienic said:
Hey guys, I'm wondering if anyone has done this, or knows if it's possible to (after unlocking bootloader) flash the Google stock Pixel system image instead of the Verizon one? I'm assuming the hardware and firmware are identical, but am not sure and am not skilled enough (or at all) in code to know if its possible. I bought my phone through Verizon, only because nowhere else had stock. I use it on T-Mobile, but fear there may be some behind the scenes Verizon stuff going on that may hinder my phone on T-Mobile. I haven't experienced any issues yet, but with the Nov security update mentioning a specific fix for wifi calling in New Mexico only on the Verizon pixels, it makes me weary that there is more happening beneath the surface than I am aware of. Thanks for any and all help! Appreciate it.
Click to expand...
Click to collapse
I did yesterday, bought mine from Best Buy and I unlock the BL. Sideload the OTA yesterday and I used NDE63V that comes with new radio. oh I'm also on Tmobile

jay661972 said:
I did yesterday, bought mine from Best Buy and I unlock the BL. Sideload the OTA yesterday and I used NDE63V that comes with new radio. oh I'm also on Tmobile
Click to expand...
Click to collapse
Awesome! Thanks for the info... Really glad to know I can convert if need be. Thanks again!

jay661972 said:
I did yesterday, bought mine from Best Buy and I unlock the BL. Sideload the OTA yesterday and I used NDE63V that comes with new radio. oh I'm also on Tmobile
Click to expand...
Click to collapse
Interesting side note on this...
I went ahead and unlocked my bootloader and flashed Google's stock Pixel image. All went well, no problems... Until I tried to use Android Pay. It's telling me my software can't be verified. And I out of curiosity checked, and the "allow OEM unlocking" in developer options is still greyed out, and not selectable, even though my BL is unlocked. Hoping this doesn't mean that we can't take an OTA. Weird, I guess we'll have to wait and see when next month's security update comes out...

newbienic said:
Interesting side note on this...
I went ahead and unlocked my bootloader and flashed Google's stock Pixel image. All went well, no problems... Until I tried to use Android Pay. It's telling me my software can't be verified. And I out of curiosity checked, and the "allow OEM unlocking" in developer options is still greyed out, and not selectable, even though my BL is unlocked. Hoping this doesn't mean that we can't take an OTA. Weird, I guess we'll have to wait and see when next month's security update comes out...
Click to expand...
Click to collapse
Just having an unlocked bootloader trips SafetyNet now and you can't use Android Pay without a custom kernel.

ITGuy11 said:
Just having an unlocked bootloader trips SafetyNet now and you can't use Android Pay without a custom kernel.
Click to expand...
Click to collapse
And the OEM unlock option appears to be dependent on device ID (imeid? Ccid?), And not the software. So don't relock it, and you're fine
Sent from my Pixel using Tapatalk

danaff37 said:
And the OEM unlock option appears to be dependent on device ID (imeid? Ccid?), And not the software. So don't relock it, and you're fine
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
One thing I just realized, is in Developer Options, its greyed out like I mentioned, but also says "Bootloader is already unlocked". Which I actually remember seeing on my Nexus 5x when the bootloader was unlocked. It's got me really curious about re locking the bootloader. Mainly cause I actually use Android Pay. Had no idea bootloader unlocks are actually tripping safety net now. Major bummer. If anyone has gone through this process with a Verizon pixel and has actually relocked their bootloader with no issues I'd certainly appreciate any info you have. Otherwise, I may have to dive in blind and hope for the best.

If you want to use Android pay, flash a custom kernel but don't root. Works for me.
Don't relock if you ever want to have it rooted, custom, etc. The unlock method isn't going to survive another security update.
Sent from my Pixel using Tapatalk

danaff37 said:
If you want to use Android pay, flash a custom kernel but don't root. Works for me.
Don't relock if you ever want to have it rooted, custom, etc. The unlock method isn't going to survive another security update.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Hypathetically, if I didn't want root or anything custom at all, do you think that relocking the bootloader could cause an issue while using the Stock Google image on a Verizon Pixel? I wish I had more knowledge on this, but I'm pretty in the dark on this stuff as of late... Thanks for your help!

Should be fine if all stock I think, just know that you may not be able to unlock later.
Sent from my Pixel using Tapatalk

newbienic said:
One thing I just realized, is in Developer Options, its greyed out like I mentioned, but also says "Bootloader is already unlocked". Which I actually remember seeing on my Nexus 5x when the bootloader was unlocked. It's got me really curious about re locking the bootloader. Mainly cause I actually use Android Pay. Had no idea bootloader unlocks are actually tripping safety net now. Major bummer. If anyone has gone through this process with a Verizon pixel and has actually relocked their bootloader with no issues I'd certainly appreciate any info you have. Otherwise, I may have to dive in blind and hope for the best.
Click to expand...
Click to collapse
Contrary to what people are saying. You CAN relock your bootloader and then unlock it again later. However, keep in mind that at some point there will likely be an update that blocks the use of dePixel8 and you will no longer be able to unlock the bootloader unless someone writes another exploit.
I would like to find a way to permanently unlock VZW Pixels but until I get one from the Google Store to compare with my Verizon one I don't think I will make much progress.
Relocking your bootloader is as simple as running the "fastboot oem lock" command from the terminal window.
Lastly. If you want to relock the bootloader, make sure your phone is 100% stock image or you risk bricking the phone

If I were to buy the Verizon pixel and flash the unlocked (non European) image. How do you think updates would work? Would I get seamless updates from Google or would I need to flash every Ota manually. Might be too early to tell

b316kane said:
If I were to buy the Verizon pixel and flash the unlocked (non European) image. How do you think updates would work? Would I get seamless updates from Google or would I need to flash every Ota manually. Might be too early to tell
Click to expand...
Click to collapse
This is exactly what I did, and I am curious as well... We'll see next month I guess, but I'm guessing it will take the OTA just fine. My wife has a Pixel from the Google store, and mine is from Verizon. I've compared everything (including booloaders) since flashing the Google store Pixel image, and every informational detail is identical. Not sure if there is some other place hidden to me that might indicate a difference, but I'm thinking that Verizon's Pixel is only different in its official software image... And, that may be it. Please don't take my word for it, I'm no developer, and know very little about any of this, but in my comparisons, they are identical now since flashing Googles official (Non Verizon, Non European) image.
Sidenote, I have yet to try this, but I'm thinking that since I am on Googles image, that if I re-lock my bootloader, that I WILL be able to unlock again after locking. I think Verizon used Googles "Allow OEM Unlocking" software toggle in developer options as the only method to actually keep people from unlocking the bootloader (again speculative), and now that I'm on Googles image, that software "block" should no longer be present, so I should in theory, be free to lock/unlock the same as Pixels purchased from the Google store... Again, I've got no proof, or actual skill to back this up, but it's a theory I have, and if I end up locking my BL again, I'll post what I find...

newbienic said:
I have yet to try this, but I'm thinking that since I am on Googles image, that if I re-lock my bootloader, that I WILL be able to unlock again after locking.
Click to expand...
Click to collapse
In the Verizon unlocking threads the people that tried relocking reported that they were unable to unlock again without depixel8, which is the same as how the Verizon phone typically works. Some people seem to have gotten into situations that could have been corrected with an unlocked bootloader, but because they had a locked bootloader that couldn't be unlocked using depixel8 they had no easy solution to get their phone working again at this time.
http://forum.xda-developers.com/pixel-xl/how-to/psa-read-relocking-bootloader-t3494615

alluringreality said:
In the Verizon unlocking threads the people that tried relocking reported that they were unable to unlock again without depixel8, which is the same as how the Verizon phone typically works. Some people seem to have gotten into situations that could have been corrected with an unlocked bootloader, but because they had a locked bootloader that couldn't be unlocked using depixel8 they had no easy solution to get their phone working again at this time.
http://forum.xda-developers.com/pixel-xl/how-to/psa-read-relocking-bootloader-t3494615
Click to expand...
Click to collapse
Thanks for the heads up!!! Like I said, I really know nothing, just speculating. Appreciate you looking out.

newbienic said:
Thanks for the heads up!!! Like I said, I really know nothing, just speculating. Appreciate you looking out.
Click to expand...
Click to collapse
I forget where, but I saw written or implied that the "checking for updates" screen about third of way through initial setup of first boot uses WiFi AND sim carrier data to install Verizon custom restrictions and settings that among other effects make depixel8 required.
Even on "non Verizon phones" (which you are saying use the same build images byte to byte?)... You have to either use a SIM card or wifi and google account to allow the developer options to enable OEM unlock.
My theory: In other words, if you don't allow via SIM and a network wifi or data connect, for Verizon to mark your phone, or another carrier, then the phone can not be unlocked. So carrier models may indeed be differentiated from current factory images AFTER boot and setup.
There is a post in Q&A of someone trying to unlock bootloader without loading into the device, not having luck. This is why oem unlock toggle is so important and why people are bricking from locked bootloaders that won't unlock (so no wipe and factory images cannot be flashed.)
Another thing to consider: SIM network lock will not be flashed over.
Sent from my sailfish using XDA Labs

Sprint one plus 7pro oem/root question

I was reading through and people say the OEM was locked. Has anyone found a work around to this I want to get this phone for the mod friendliness however if the OEM unlocking is locked it would be impossible. Any work around? I really want to have access to hotspot with no issues

Not currently. I don't have the phone yet, ordered Friday probably won't be getting it til Monday. If it seems impossible to root, I'll trade it in for the note 10+.

Unfortunately not. You either have to meet Sprints requirements for them to unlock it (phone paid in full and active for 60 days or more on their network) or we have to wait and see if an amazing devs can help us out.

Wait does that mean that sprint will actually unlock the phone for you? If they do, is root possible or would someone still have to develop something for it?

dakoellis said:
Wait does that mean that sprint will actually unlock the phone for you? If they do, is root possible or would someone still have to develop something for it?
Click to expand...
Click to collapse
Pretty sure the post about Sprint unlocking the device is confusing SIM unlock with bootloader unlock. Which of course are 2 very different things. I've never heard of carriers having anything to do with unlocking the bootloader. But unlocking the SIM, yes (they have to by law now).
Otherwise, the requirements stated would not be that hard to meet, and plenty of folks would already be unlocking their Sprint 7 Pro bootloaders.
Unlocking the bootloader is the main barrier to root. I don't see why (with an unlocked bootloader) you couldn't just root with one of the existing methods (flash patched boot img with fastboot, or boot TWRP and flash Magisk) and no real development would be needed. But it's that locked bootloader that is the kicker!

So is there any no root workaround for use of the native hotspot on the sprint version of this device?
Or would we just have to use an app?