Database Users

[Q] How fast your Nexus 7 defects appeared?

I have my N7 for a week now. I really want to root ant take full control of my tablet. I just don't want to void my warranty just now, just in case any defects would appear.

You wont void your warranty. If your confident enough to root it then you should be confident enough to restore it to stock if it ever needs to be returned. Not to mention that if you wait then decide to unlock the bootloader then you will be spending more time putting everything back on it.
Sent from my Magnetised Banana using xda app-developers app

I have no problems with boot unlocking and rooting,done it numerous times for friends and @ work. I just don't want end up having screenlift or sth and warranty would refuse just cause unlocked bootloader.
Sent from my Nexus 7 using XDA Premium HD app

a got a replacement nexus 7 two weeks ago, my old seven stopped charging. i sent it back to google with an unlocked bootloader, twrp recovery, rasbean jelly rom, and the trinity kernel. the only thing is they forgot to thank me
if there is a hardware related problem, having an unlocked bootloader and rooted shouldnt be an issue.

Google Nexus 7 TOOLKIT V4.0.0
found out that Google Nexus 7 TOOLKIT V4.0.0 can relock the bootloader.

Deivi_Z said:
found out that Google Nexus 7 TOOLKIT V4.0.0 can relock the bootloader.
Click to expand...
Click to collapse
"Re-lock" not "Lock"
So its no better than having it un-locked.
But yeah, if its hardware issue they cannot refuse a fix.
Software issues on the other hand, they will blame on custom ROM's etc.
But thats fair?

noob question

Been a nexus user for a while till I sold it last year to get the s7 but I recently came back to the 6p, and my question is, will rooting it cause that bootloop of death some people been getting? I'm not under warranty since I bought it off a friend so I wanna b very cautious when proceeding to rooting and changing roms. Any help is appreciated

shooterlgk said:
Been a nexus user for a while till I sold it last year to get the s7 but I recently came back to the 6p, and my question is, will rooting it cause that bootloop of death some people been getting? I'm not under warranty since I bought it off a friend so I wanna b very cautious when proceeding to rooting and changing roms. Any help is appreciated
Click to expand...
Click to collapse
Many people are getting the BOD on stock with the bootloader locked. Rooting has nothing to do with the BOD

shooterlgk said:
Been a nexus user for a while till I sold it last year to get the s7 but I recently came back to the 6p, and my question is, will rooting it cause that bootloop of death some people been getting? I'm not under warranty since I bought it off a friend so I wanna b very cautious when proceeding to rooting and changing roms. Any help is appreciated
Click to expand...
Click to collapse
Well, I have switched ROMs about 4-5 times this week itself. Started off by going to 6.0.1 from 7.1.1 without any issues. Also flashed EX and franco kernels a couple of times. As for root, it has never been a problem. If flashing SuperSU causes bootloop, then the simple fix is to reflash the ROM or restore a Nandroid backup.
Don't get skeptic when you have a Nexus :good: If there is going to be a major issue at all, then it can only be an hardware failure. :highfive:

DJBhardwaj said:
Well, I have switched ROMs about 4-5 times this week itself. Started off by going to 6.0.1 from 7.1.1 without any issues. Also flashed EX and franco kernels a couple of times. As for root, it has never been a problem. If flashing SuperSU causes bootloop, then the simple fix is to reflash the ROM or restore a Nandroid backup.
Don't get skeptic when you have a Nexus :good: If there is going to be a major issue at all, then it can only be an hardware failure. :highfive:
Click to expand...
Click to collapse
Ok thanks I feel more comfortable rooting now. For the January update is it the same procedure?

shooterlgk said:
Ok thanks I feel more comfortable rooting now. For the January update is it the same procedure?
Click to expand...
Click to collapse
Yes. Just have TWRP installed and flash SuperSU v2.79. Link: https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip

About downgrading and

Hi,
My Nexus 6p has 32GB Samsung emmc.
I upgraded it to 7.11 several days ago and used it for 2 days before I knew many Nexus 6p has a boot loop problem(luckily I didn't have it when I was using 7.0). So I flashed back to 6.0.
My question is, since I had tried 7.11, downgraded it, and good with 6.0 since then. Does it prove that I don't have a hardware problem and I can use 7.1.1 safely?
The reason I'm using Nexus 6p is I really want the latest updates.
p.s it's my first thread on XDA.
Thanks for any thoughts and comments.

Real1minshen said:
Hi,
My Nexus 6p has 32GB Samsung emmc.
I upgraded it to 7.11 several days ago and used it for 2 days before I knew many Nexus 6p has a boot loop problem(luckily I didn't have it when I was using 7.0). So I flashed back to 6.0.
My question is, since I had tried 7.11, downgraded it, and good with 6.0 since then. Does it prove that I don't have a hardware problem and I can use 7.1.1 safely?
The reason I'm using Nexus 6p is I really want the latest updates.
p.s it's my first thread on XDA.
Thanks for any thoughts and comments.
Click to expand...
Click to collapse
Nobody knows for sure what causes the boot loop of death, which is what I assume you are concerned about, but multiple people who stayed on Marshmallow and never updated to Nougat reported that they got it anyway. If you want to run Nougat you should do a clean install of the full factory image and see if you still have the problem. As long as your bootloader is unlocked and USB debugging is enabled in developer options you should be relatively safe should you encounter problems again. I have been running 7.11 or roms based on 7.1.1 for as long as I have had this phone and have never encountered any serious issues. The vast majority of 6P owners don't have serious issues with Nougat. I personally wouldn't go back to Marshmallow because I got the 6P to be up to date as well.

jhs39 said:
Nobody knows for sure what causes the boot loop of death, which is what I assume you are concerned about, but multiple people who stayed on Marshmallow and never updated to Nougat reported that they got it anyway. If you want to run Nougat you should do a clean install of the full factory image and see if you still have the problem. As long as your bootloader is unlocked and USB debugging is enabled in developer options you should be relatively safe should you encounter problems again. I have been running 7.11 or roms based on 7.1.1 for as long as I have had this phone and have never encountered any serious issues. The vast majority of 6P owners don't have serious issues with Nougat. I personally wouldn't go back to Marshmallow because I got the 6P to be up to date as well.
Click to expand...
Click to collapse
Thank you~

Nexus 6P mainboard replaced, still save to root.

My Nexus 6P went in a bootloop recently.
It was shortly after I unlocked the bootloader and rooted the phone.
I tried everything I could (stock firmware 7.1, 7.0 and the oldest that was available) but nothing worked.
I still had warranty so I sent it back to webshop where I bought it.
Now I got my phone back and the note says 'Mainboard replaced'.
What I want to know:
- Can it be my fault the phone broke, I know the Nexus 6P has some issues concerning bootloops.
- Can I safely root again? Or would you not recommend it?
Thanks for your answers.
I have a backup phone, but I don't want to f*** my 6P up again.

Search for BLOD. You will answer your own question in no time. Lol No you are not to blame. It had or is happening to probably hundreds of phones by now. You will also see there are many different roms, 6&7, root or stock that have the problem.
Sent from my Nexus 6P using XDA-Developers Legacy app

Rooting doesn't cause the boot loop of death. Flashing something sometimes triggers it (including flashing a normal OTA on pure stock) but it is almost certainly a hardware issue.

Does unlocked bootload still causes bootloop for stock ROMs?

Hi all,
Oneplus 5 is an awesome device(except it is a little too big), I have being using it for almost a year now. I stopped flashing ROMs since beginning of the year after a OTA updating to oreo, the cause was the unlocked bootloader, any of those oreo rom won't work with unlocked bootloader. Not so many people talked about it I actually I just accidentally found it on the forum.
Right now my OOS version is 5.1.3, it works fine but restrict you from doing anything, oneplus does have a custom recovery, but it can only be used for sideloading their stock systems, I couldn't find any technical docs about their recovery as well, just some guy on the forums said the recovery does the verification before doing the flashing. I think my options now is either staying with OTA updates or going straightly to ublock+TWRP+custom ROMs.
I am not sure if this bootloader locking enforcement has being default for oneplus 5. I wonder if anyone is using a stock oreo OOS now with a unlocked device now.
Thanks,

unlocked boot never caused bootloop, hmmmmm
you need or to read forum more, or to do more experiments by yourseld till you find out why it happened to you

more_than_hater said:
unlocked boot never caused bootloop, hmmmmm
you need or to read forum more, or to do more experiments by yourseld till you find out why it happened to you
Click to expand...
Click to collapse
Yes, you might not believe it, and pls don't take this as an offence. Some on the OnePlus Forum did not experience the boot loop, some experienced the problem like me. It was what really happened to me, soon as I locked the bootloader the phone booted fine.

it sounds loke nonsense. im absolutely sure u did smth wrong

I never had bootloop with my unlocked bootloader with custom or with oos since the furet day i have flash rom 1 yearling ago. Read more thread on xda for more information.