Database Develop

Stock Unlocked Nexus One + root = voided warranty?

Hey Guys
I have bought myself a stock unlocked AT&T version of the Nexus one
It has never been rooted and I am on FRF85 at the moment (that was upgraded from EPE54b to FRF85 using the manual update method
Questions:
1. Does unlocking the bootloader mean you basically sim-unlock your phone?
2. If I have a stock unlocked phone, do I need to unlock the bootloader to root?
3. If I dont need to unlock the bootloader, when/if I decide to root my N1, will I lose warranty?
I guess question 3 is dependent on 2 above
Thanks

Unlocking the bootloader has nothing to do with sim unlocking your phone, these are two complete separate things
1 no. but I think there is no locked n1 available, so it is unlocked quite sure
2 maybe, depends on your build number. I think you have to unlock your bootloader with the att version
3 no

watercool said:
Unlocking the bootloader has nothing to do with sim unlocking your phone, these are two complete separate things
1 no. but I think there is no locked n1 available, so it is unlocked quite sure
2 maybe, depends on your build number. I think you have to unlock your bootloader with the att version
3 no
Click to expand...
Click to collapse
regarding rooting without unlocking bootloader, see the sticky in the nexus android development section

@flybyme - thanks for your reply - i had a look at the sticky thread you were talking about rooting without unlocking the bootloader.
1. what's easier? Rooting with unlocking the bootloader or without the bootloader?
2. What's more fool-proof so-to-speak?
3. What would you recommend?
Sorry for so many questions but thanks for reading

1. With unlocking the bootloader is alot simplet BUT you will loose your waranty.
2. Once either process is complete there's no real difference since you can use the custom recovery in exactly the same way to flash any further roms.
3. I would suggest _without_ unlocking the bootloader. At least give it a try, the worst that can happen is it doesnt work.

[Q] Partially Bricked HD7 / Cotulla's HSPL installed

So,
Here is what happened, I've got an HD7 that has been laying around my office for months, it was actually never used and it has never been updated.
Unfortunately I lost my previous phone and I decided to use that one, but... It was carrier locked to T-Mobile and I did not want to either purchase or beg t-mobile for a code.
Next thing I did was to carefully read every post I could find regarding HD7 carrier unlocking and found myself with only one option: Install a custom ROM on my phone.
The phone had the SPL 1.20 so I decided to install Cotulla's HSPL and then install a Custom ROM, but it failed twice to flash the device, once at 20% and then at 80%.
Right now the Phone goes right into the bootloader screen (It does show cotulla's HSPL as installed) after a short load atempt (obviously the OS is only partially installed).
Im looking forward to get advise on how to install the custom ROM and what I might be doing wrong.

Masticore26 said:
So,
Here is what happened, I've got an HD7 that has been laying around my office for months, it was actually never used and it has never been updated.
Unfortunately I lost my previous phone and I decided to use that one, but... It was carrier locked to T-Mobile and I did not want to either purchase or beg t-mobile for a code.
Next thing I did was to carefully read every post I could find regarding HD7 carrier unlocking and found myself with only one option: Install a custom ROM on my phone.
The phone had the SPL 1.20 so I decided to install Cotulla's HSPL and then install a Custom ROM, but it failed twice to flash the device, once at 20% and then at 80%.
Right now the Phone goes right into the bootloader screen (It does show cotulla's HSPL as installed) after a short load atempt (obviously the OS is only partially installed).
Im looking forward to get advise on how to install the custom ROM and what I might be doing wrong.
Click to expand...
Click to collapse
well if you can get to the bootloader screen...why don't you install a custom ROM using Task29 ?? that should work...

Well, I tried to install the factory ROM but it fails as well, it always gets stuck at some point beyond 80%.

I was able to install Deepshining ROM, but the sim lock remains... I guess I will have to buy an unlock code. ¿Can someone tell me what is the site site to buy one?

Masticore26 said:
I was able to install Deepshining ROM, but the sim lock remains... I guess I will have to buy an unlock code. ¿Can someone tell me what is the site site to buy one?
Click to expand...
Click to collapse
i also had this problem

Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A

savvyone
Dollyena said:
i also had this problem
Click to expand...
Click to collapse
You don't have to buy the unlock code. Call T-Mobile, ask for technical support (bypass customer service, it will take too long), and request the unlock code. Have the IMEI # for your phone available. They will email the unlock code to you usually within 24-48 hours. I did this last month and got the code the same day.

[Q] Flashing ROM + Bootloader Xperia T

Hey guys, I am fairly new to the android phones, (recently came from an iPhone) but I had heard so much about the freedoms with the Android os so I decided to switch.
I purchased the Sony Xperia T (LT30a) locked on the Bell mobility LTE network. I have really wanted to unlock the bootloader, so when I went in to check it said "Bootloader Unlock Allowed: NO". after some searching I read that it was my carrier preventing the bootloader from being unlocked, and that if I followed the following simple steps, it would change the message to :"Bootloader Unlock Allowed: YES". so here is what I did:
1. Flashed a Generic firmware to my phone (ICS it was a uk generic) which then changed my model number in "About phone" from LT30a to LT30p and removed all the bell branding.
2. Using an IMEI number, i was able to get an unlock code and unlocked the phones sim card to work on any network, and have tested and it does work.
the problem I am having is that even after doing this, the bootloader is still "locked" and can not be unlocked. I have taken a look at the methods for the test pin, but that involves removing the battery to view the motherboard, which sucks because this phone the battery is not removable. if anyone know a free or paid way to unlock the bootloader on the Xperia T LT30a or LT30p models, please let me know! thanks.

I dont know where you read that, but it is wrong and there is no way to change that message.
If it says no, then your bootloader can not be unlocked.
Its not Sony's fault, its not googles fault, its Bells fault for being a dev unfriendly provider.
Test point method will not work even if we could remove the battery, that loophole has been closed in 2012 devices.

gregbradley said:
I dont know where you read that, but it is wrong and there is no way to change that message.
If it says no, then your bootloader can not be unlocked.
Its not Sony's fault, its not googles fault, its Bells fault for being a dev unfriendly provider.
Test point method will not work even if we could remove the battery, that loophole has been closed in 2012 devices.
Click to expand...
Click to collapse
ok well thank you very much! I guess my next question is.. is there any way at all to install a custom ROM such as cyanogen mod 10 ? or if you know of any better ones while my bootloader is locked?

Robe8691 said:
ok well thank you very much! I guess my next question is.. is there any way at all to install a custom ROM such as cyanogen mod 10 ? or if you know of any better ones while my bootloader is locked?
Click to expand...
Click to collapse
You can only install stock based custom roms because you wony be able to flash a custom kernel with a locked bootloader. Therefore there is no hope for cyanogenmod, AOKP or MUIU
There are several in the Dev section to choose from, ranging from early ICS firmwares to the latest JB firmware.
I dont recommend Roms (Even my own) as choosing a rom should be a personal thing, but the I am currently on Timin8rs rooted and deodexed JB rom which you can flash.
You will need to root your phone in order to flash a recovery, then flash the .zip for the rom using that recovery.
Find all instructions for doing that in the All in one thread. Its the first thread in the Q&A section.
good luck and if you need extra help after reading up on what you need to do then ask. But remember to read up first!

gregbradley said:
You can only install stock based custom roms because you wony be able to flash a custom kernel with a locked bootloader. Therefore there is no hope for cyanogenmod, AOKP or MUIU
There are several in the Dev section to choose from, ranging from early ICS firmwares to the latest JB firmware.
I dont recommend Roms (Even my own) as choosing a rom should be a personal thing, but the I am currently on Timin8rs rooted and deodexed JB rom which you can flash.
You will need to root your phone in order to flash a recovery, then flash the .zip for the rom using that recovery.
Find all instructions for doing that in the All in one thread. Its the first thread in the Q&A section.
good luck and if you need extra help after reading up on what you need to do then ask. But remember to read up first!
Click to expand...
Click to collapse
thank you very much! hopefully sometime in the near future they come out with a way to fix this problem, and believe me, I do not blame sony at all for this

Sorry for the double post! But I just wanted to say, that if anyone needs help testing different roms and/or ways of unlocking a locked bootloader, I do have a sim unlocked xperia T and just wanted to throw this out, but if sony does not "perma lock" the bootloader, and if it is infact the carrier, then would this not prove that it is sonething in the firmware? I spoke with my sister who is a manager for a bell store here, acording to her, Bell is not authorized to open, or attempt to fix this phone, it is simply sent to sony for repairs.. Just makes me wonder because if Bell can not open the phone, then they must have used some sort of software.. I have always thought of software as "semi-permenant" that it can be reversed , and that its only a matter of figuring out how to reverse it?
Sent from my LT30p using xda app-developers app

Questions From a Would be Owner

Hello guys,
Just a few questions so I know what I am getting into
1) The phone can be rooted. However, if i want to run on a custom ROM or use mods such as the music mod, I would have to unlock the bootloader, yes?
2) Once the bootloader is unlocked, I would lose the 'Bravia Engine' feature of the phone. What else will I lose? For those who have lost it, is the trade off, of being able to run Custom ROMs and mods while losing the 'Bravia Engine' feature worth it?
3) If I have to send the phone for warranty, I could just re-lock the bootloader and send it back for warranty. Is there a chance somehow that they'll reject the phone if they detected that the phone's bootloader was tempered with?

arvin2212 said:
Hello guys,
Just a few questions so I know what I am getting into
1) The phone can be rooted. However, if i want to run on a custom ROM or use mods such as the music mod, I would have to unlock the bootloader, yes?
Click to expand...
Click to collapse
no
arvin2212 said:
Hello guys,
Just a few questions so I know what I am getting into
2) Once the bootloader is unlocked, I would lose the 'Bravia Engine' feature of the phone. What else will I lose? For those who have lost it, is the trade off, of being able to run Custom ROMs and mods while losing the 'Bravia Engine' feature worth it?
Click to expand...
Click to collapse
No clue since mine isn't/can't be unlocked. The only reason for me to unlock the BL (Even though it can't be done) would be, to flash a custom kernel, beside that I don't see any other reasons why I should unlock it.
arvin2212 said:
Hello guys,
Just a few questions so I know what I am getting into
3) If I have to send the phone for warranty, I could just re-lock the bootloader and send it back for warranty. Is there a chance somehow that they'll reject the phone if they detected that the phone's bootloader was tempered with?
Click to expand...
Click to collapse
Once it's unlocked there is no way back.
So if you want to root your phone, use custom roms (without custom kernels) you don't need to unlock the bootloader.

Dsteppa said:
no
No clue since mine isn't/can't be unlocked. The only reason for me to unlock the BL (Even though it can't be done) would be, to flash a custom kernel, beside that I don't see any other reasons why I should unlock it.
Once it's unlocked there is no way back.
So if you want to root your phone, use custom roms (without custom kernels) you don't need to unlock the bootloader.
Click to expand...
Click to collapse
Thank you very much for the reply.
I assumed as such from reading some posts initially, but then I went to the ROM section (If i am not mistaken) and there is a post on how to unlock the bootloader and then there is the Why section where it says that you could then use custom ROMs and mods which then confused me.
If i can use custom roms and mods without unlocking the bootloader, then I'll definitely be getting this phone.

I'll take advantage of this thread to ask one simple question: once we rooted the XZ and flash the Mods we find useful, we no longer get updates from the official Sony firmware in the future, right?

labroste said:
I'll take advantage of this thread to ask one simple question: once we rooted the XZ and flash the Mods we find useful, we no longer get updates from the official Sony firmware in the future, right?
Click to expand...
Click to collapse
First backup your firmware with http://forum.xda-developers.com/showthread.php?t=2188129
You can go back at any time to your original firmware and you can have the updates via pcc or sus.
Sent from my C6602 using xda premium

Question Help, i did something stupid.

Hello
Hoping somebody can help getting my phone up and running again.
I wanted to unroot my phone, because i was having issues with danish "MitId". And was a bit sloppy with it.
First i tried using SuperSU to remove root. Because i didnt feel like setting everything up again. Didnt work.
Then I locked the OEM Lock in developer settings. Not thinking this would be a fatal error.
Got home from work, and said to myself. Jusk lock the bootloader and the phone will reset itself.
But this is not the case, when you have been stupid enough to lock the OEM lock.
Now I am stuck on "No valid operating system could be found. The device will not boot"
I can get in to fastboot by pushning power+vol down. But cannot flash anything since the phone thinks the OEM Lock is locked on it.
Does anyone know of a solution for me. Or is it going to the shop tommorow and say that my phone is going this. And hope they will sort it for me?

Can't you fix stuff by using https://flash.android.com/ ?

No, unfortuantly not. It fails:
Device Unlock Disabled​For security reasons, you need to enable "OEM unlocking" in order to flash your device. See the device preparation instructions for more information.

Pearsondk said:
No, unfortuantly not. It fails:
Device Unlock Disabled​For security reasons, you need to enable "OEM unlocking" in order to flash your device. See the device preparation instructions for more information.
Click to expand...
Click to collapse
Try sideloading the full OTA. You don't need an unlocked bootloader for that.

Unfortuatly not, if I try to enter recovery mode. The phone just goes back to the screen saying "No valid operating system could be found. The device will not boot"
ADB is not available to me

If you can't sideload the OTA, I'm afraid there is not much else you can do with a locked bootloader except try to RMA it.

Can you get into recovery at all. Even if it's the stock you can attempt a sideload of the stock OTA.zip from Google. You may also try if your on boot slot A
fastboot --set-active=b
On b use
fastboot --set-active=a
Try to see if the other boot slot has an a bootable OS.
*****I apologize I just saw it's actually still locked****"
Contact U-break I-fix if I typed that correctly. The third party warranty repair center for Google's warranty. I believe they can attempt to switch the boot slot with a locked bootloader with the equipment they use to reflash these devices. If anything it's under warranty get the RMA and if the bootloader is locked on it trade someone or sell it and use it to make buying a new cheaper..

JovialQuestion said:
Can you get into recovery at all. Even if it's the stock you can attempt a sideload of the stock OTA.zip from Google. You may also try if your on boot slot A
fastboot --set-active=b
On b use
fastboot --set-active=a
Try to see if the other boot slot has an a bootable OS.
Click to expand...
Click to collapse
No, I can get into fastboot and that is it.
But everything I try in fastboot gets rejected, since it says the phone is locked.

Does the bootloader screen on the phone have the option to boot into Rescue. This has a ADB connection but I am not sure if adb sideload works

Really mad that Google intentionally locks phones this way, turning them into completely functional, but useless piece of junk. I guess that's late stage capitalism for you xD

JovialQuestion said:
Does the bootloader screen on the phone have the option to boot into Rescue. This has a ADB connection but I am not sure if adb sideload works. Use the volume keys and power button to select it
Click to expand...
Click to collapse
Kofa1 said:
Really mad that Google intentionally locks phones this way, turning them into completely functional, but useless piece of junk. I guess that's late stage capitalism for you xD
Click to expand...
Click to collapse
Google is not responsible for phone's with locked bootloaders. They make the device with the specifications the carrier that sells it stipulates. Google themselves allows the unlock.

Lughnasadh said:
If you can't sideload the OTA, I'm afraid there is not much else you can do with a locked bootloader except try to RMA it.
Click to expand...
Click to collapse
Iam guessing the same. Phone doesnt want to do anything.
And since i cant get into the phone to oem lock i am stuck. Live in Denmark, so by law I havnt voided the warrenty by rooting.

Pixel warranty is always valid even if you unlock and root. Google doesn't void the warranty. Go to Google pixel support page. Find warranty and act as if your submitting a RMA and it will tell you after you enter the device IMEI how long your warranty is valid for

Delete

If that were true. Android flash tool https://flash.android.com/welcome
Would work as it's the same process for the browser to flash the very same file. Motorola allowed signed factory img on locked. Google had never allowed that in fastboot as far as I am aware

DroidRommer said:
All you need to do is go here Factory pixel firmwares and scroll down to pixel 7 panther assuming you're not on the pro (cheetah)
-select the latest version for your model whether that's Verizon or whatever if you have the carrier unlocked one like myself just choose the Feb firmware that doesn't have a carrier name at the end of the firmware number (you should have your phone plugged into your PC and in fastboot mode) click flash and follow the steps. These are Googles factory images so it doesn't matter if your bootloader is unlocked or not as long as you choose the latest version and the correct version for your phone. Tbh you can't really brick the pixel 7 as long as you have a PC and are able to put the phone in fastboot mode (holding the volume down and power button while powering on)
-Anytime you run into some kind of bootloop issue or wanna get rid of root flashing the stock firmware from this website will factory reset and revert your phone to the way it was the very first time it was pulled out of the box and powered on. If you have already tried this and you know forsure you did everything correctly then I must admit I have never had this happen and I'm someone who flashes custom roms and goes back to stock to get the latest security update just to turn around and flash another custom rom right after lol. If you need any help or advice feel free to pm me whenever. I have been rooting phones for a long time and have to say that the Google pixel is by far the most user friendly phone I've ever owned when it comes to custom rooms, rooting etc. You can ALWAYS go back as long as you know what steps to take. Sorry for the rant especially if you already figured it out.
Happy Customizing!
DROIDROMMER
Click to expand...
Click to collapse
Their bootloader is locked. You cannot flash a factory image like that with a locked bootloader. They also turned off OEM Unlocking in the developer settings. If they had left this enabled they would be able to use Android Flash Tool as that tool will unlock your bootloader if OEM Unlocking is enabled.

Kofa1 said:
Really mad that Google intentionally locks phones this way, turning them into completely functional, but useless piece of junk. I guess that's late stage capitalism for you xD
Click to expand...
Click to collapse
This wouldn't be Google, they basically encourage you too unlock the bootloader and root if you want as they give you all the tools you need and factory firmware options to go back if you make a mistake. Tbh if you are able to unlock and root the phone to start then you can go back. Even with a locked bootloader you can always flash the latest factory image on googles dev website, you just can't downgrade firmware or install different carrier firmware without the unlocked bootloader. If we really wanna poke at some phone developers I vote Samsung as I have had multiple people ask me to root their phones and if it's a US snapdragon version it cannot be done its so frustrating lol thanks for letting me vent, have a great day if you have the the carrier unlocked dev edition of the pixel 7 and ever need any help feel free to pm me. I have been rooting and romming pixels for a long time
Edit: I was not aware you couldn't flash the stock firmare using googles dev page without oem unlock. I apologize for jumping to conclusions. I thought I had every possible bad scenario happen to me by now but apparently I learned something new today.

DroidRommer said:
This wouldn't be Google, they basically encourage you too unlock the bootloader and root if you want as they give you all the tools you need and factory firmware options to go back if you make a mistake. Tbh if you are able to unlock and root the phone to start then you can go back. Even with a locked bootloader you can always flash the latest factory image on googles dev website, you just can't downgrade firmware or install different carrier firmware without the unlocked bootloader. If we really wanna poke at some phone developers I vote Samsung as I have had multiple people ask me to root their phones and if it's a US snapdragon version it cannot be done its so frustrating lol thanks for letting me vent, have a great day if you have the the carrier unlocked dev edition of the pixel 7 and ever need any help feel free to pm me. I have been rooting and romming pixels for a long time
Click to expand...
Click to collapse
Dude. You cannot flash factory images of any kind on any Google phone with the bootloader in locked status. Please stop giving false information on here. If you want to talk up Samsung do it on a Samsung post. Let's not confuse everyone please

DroidRommer said:
Even with a locked bootloader you can always flash the latest factory image on googles dev website, you just can't downgrade firmware or install different carrier firmware without the unlocked bootloader.
Click to expand...
Click to collapse
To use Android Flash Tool, you have to have OEM Unlocking enabled in Developer Options for it to be able to unlock the bootloader.
To flash the factory image in fastboot you must have an unlocked bootloader.

Lughnasadh said:
Their bootloader is locked. You cannot flash a factory image like that with a locked bootloader. They also turned off OEM Unlocking in the developer settings. If they had left this enabled they would be able to use Android Flash Tool as that tool will unlock your bootloader if OEM Unlocking is enabled.
Click to expand...
Click to collapse
Okay my bad you are right fortunately I have never had this happen. And like someone else said if he can't get into recovery then he can't sideload a factory ota... sorry I'm at a loss on this one. Some custom roms use "fastboot update file.zip" would that do anything in this case or would that command not even work with a locked bootloader I'm assuming. I apologize for trying to act like a know it all I've just never heard of this happening