I really messed my new phone up. - Nexus 6 Q&A, Help & Troubleshooting

Just got a new Verizon Nexus 6. Never rooted or messed with android in my life. I installed Android M on it (with hours of frustration) and then was following a guide to root it while being on Android M. Somehow I deleted EVERYTHING on the phone, it says the phone is corrupt and wont start when I try to turn it on. (I have Team Win Recovery Project v2.8.7.1) How can I fix this ASAP? Have no idea how. I just need a working phone. Please help thanks!

If you can boot into TWRP just download a ROM and push it to the device and flash it. If you can get into bootloader you can flash a factory image to fix.
If you've never rooted, let alone even used Android, why the hell are you installing a dev preview onto your device? Guess you found out the hard way. Just saying....
Sent from my Nexus 6 using Tapatalk

Highway 55 said:
If you can boot into TWRP just download a ROM and push it to the device and flash it. If you can get into bootloader you can flash a factory image to fix.
If you've never rooted, let alone even used Android, why the hell are you installing a dev preview onto your device? Guess you found out the hard way. Just saying....
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yeah I agree. I need some one with skype to walk me though it. I literally followed step by step guides on youtube without knowing what I was doing, it was my fault.

Did you ever figure it out. I have no problem walking you through it. Just shoot me a pm and we can go from there.
Nick

I hope everything turns out okay and you get your phone working again. I would Skype with you but I'm on dad duty with my kids tonight. Good luck!
Sent from my Nexus 6 using Tapatalk

Jaimbi said:
Just got a new Verizon Nexus 6. Never rooted or messed with android in my life. I installed Android M on it (with hours of frustration) and then was following a guide to root it while being on Android M. Somehow I deleted EVERYTHING on the phone, it says the phone is corrupt and wont start when I try to turn it on. (I have Team Win Recovery Project v2.8.7.1) How can I fix this ASAP? Have no idea how. I just need a working phone. Please help thanks!
Click to expand...
Click to collapse
That was your mistake. If never messed with Android worst thing you could do is jump right on a Beta build.
---------- Post added at 08:14 PM ---------- Previous post was at 08:08 PM ----------
Easy to fix if unlocked and have TWRP. Recommend going to stable build first and work your way up. At least will have a working phone. Make a backup up stable build and then play all you want. Could have made backup of stock before even flashed M and would have been golden.

What did you do when you got the corrupt message? I'm asking because many people get this message but if you ignore it, it should boot up anyway.

slosrtnick said:
Did you ever figure it out. I have no problem walking you through it. Just shoot me a pm and we can go from there.
Nick
Click to expand...
Click to collapse
yeah I got it! i watched a video on re-flashing M? I think? It works now, I'm still not sure how to back up my stuff properly but I have a working phone! Thanks for the reply!

Jaimbi said:
Just got a new Verizon Nexus 6. Never rooted or messed with android in my life. I installed Android M on it (with hours of frustration) and then was following a guide to root it while being on Android M. Somehow I deleted EVERYTHING on the phone, it says the phone is corrupt and wont start when I try to turn it on. (I have Team Win Recovery Project v2.8.7.1) How can I fix this ASAP? Have no idea how. I just need a working phone. Please help thanks!
Click to expand...
Click to collapse
It sounds like all you need to do is: when you get to that "phone is corrupt" screen, press volume down and then the power button to continue.

Related

Nexus 6 Flashing TEAMWIN STUCK?

I managed to borrow a Samsung Satellite laptop, so I could root and unlock my Nexus 6. Laptop is brand new. Everything was great on unlocking and rooting using Wogfresh's Nexus Tool Kit.
Then I decided to stop the forced encryption. Used Wug's Tool Kit again. At the end it says phone will reboot in 15 minutes. I waited over a half hour. Then I tried rebooting the phone. Now it flashed teamwin.
I can get it turned off. And I can still get it into recovery, bootloader mode, etc. I worked on this from 16:30 - 05:30 yesterday. I have been working today for another 3-4 hours.
Wug's Tool, the computer will not recognize the phone. Any help would be greatly appreciated. This is sooooo frustrating! I have uninstalled drivers, updated drivers, usbs too. I did everything Wug's kit said to do.
Sent from my SGH-I337 using Tapatalk
first off, stop using toolkits!
doing it properly is just as easy, and takes about 4-5 minutes, to unlock the bootloader, flash the recovery, flash the supersu zip, and to flash a custom kernel that wont bring on encryption(but you have format data for un-encryption to work).
Good looking out! Thanks for all the information. I am positive that you must be of Wug's caliber, dev wise, right?
It's a real shame everyone doesn't know everything like you, huh? Also appreciate the directions on doing it your way, in 4-5 minutes.
Sent from my SGH-I337 using Tapatalk
addcancercat said:
Good looking out! Thanks for all the information. I am positive that you must be of Wug's caliber, dev wise, right?
It's a real shame everyone doesn't know everything like you, huh? Also appreciate the directions on doing it your way, in 4-5 minutes.
Sent from my SGH-I337 using Tapatalk
Click to expand...
Click to collapse
assuming you got the driver installed..
1. while in bootloader.. fastboot oem unlock(this will unlock the bootloader
2. fastboot flash twrp recovery
3. flash the latest supersu with twrp recovery
this will give you root
4. flash any custom kernel(if you want to decrypt).
5. in twrp recovery, format data.
6. reboot and youll be rooted and unencrypted.
thats the basics, for any nexus. root toolkits can be used, if you already know what to do. if you are clueless of the process, youll learn ziltch using a roit toolkit, and will remain without any knowledge. so when you need to do some basic upkeep, you will be clueless, and will feel as your device is bricked. at that point youll start a pointless thread..
Thanks again. Did you read my post?
No I don't have drivers installed.
The computer does not recognize the phone now.
Please spare me anymore help.
Sent from my SGH-I337 using Tapatalk
simms22 said:
assuming you got the driver installed..
1. while in bootloader.. fastboot oem unlock(this will unlock the bootloader
2. fastboot flash twrp recovery
3. flash the latest supersu with twrp recovery
this will give you root
4. flash any custom kernel(if you want to decrypt).
5. in twrp recovery, format data.
6. reboot and youll be rooted and unencrypted.
thats the basics, for any nexus. root toolkits can be used, if you already know what to do. if you are clueless of the process, youll learn ziltch using a roit toolkit, and will remain without any knowledge. so when you need to do some basic upkeep, you will be clueless, and will feel as your device is bricked. at that point youll start a pointless thread..
Click to expand...
Click to collapse
Dude lay off! You are forever on here giving ppl **** about the posts they make. Sorry if most ppl arnt as skilled as you and might actually need some help. Just cause your "recognized" doesnt make you a mod. If they have a problem with what someone post let them deal with it.
addcancercat said:
Thanks again. Did you read my post?
No I don't have drivers installed.
The computer does not recognize the phone now.
Please spare me anymore help.
Sent from my SGH-I337 using Tapatalk
Click to expand...
Click to collapse
have you went through and installed it yet? here is the page for the android adb driver as well, it should also work http://adbdriver.com/
---------- Post added at 07:45 PM ---------- Previous post was at 07:41 PM ----------
chris6278 said:
Dude lay off! You are forever on here giving ppl **** about the posts they make. Sorry if most ppl arnt as skilled as you and might actually need some help. Just cause your "recognized" doesnt make you a mod. If they have a problem with what someone post let them deal with it.
Click to expand...
Click to collapse
lay off what? with helping him out? no, im not a mod, nor do i want to be a mod(i have said no to xda mod offers before). but, i will always fight against lies and untruth, no matter what, no matter who says it. i dont come here, to xda, to learn. i mostly come here to help people out. if you dont want any help, thats fine, let me know and i wont help you. but if you are just here to give me crap about nothing except me going against what others say, get the fxxk out of here.
simms22 said:
have you went through and installed it yet? here is the page for the android adb driver as well, it should also work http://adbdriver.com/
---------- Post added at 07:45 PM ---------- Previous post was at 07:41 PM ----------
lay off what? with helping him out? no, im not a mod, nor do i want to be a mod(i have said no to xda mod offers before). but, i will always fight against lies and untruth, no matter what, no matter who says it. i dont come here, to xda, to learn. i mostly come here to help people out. if you dont want any help, thats fine, let me know and i wont help you. but if you are just here to give me crap about nothing except me going against what others say, get the fxxk out of here.
Click to expand...
Click to collapse
Help ppl? All you do is give ppl ****. Ive seen numerous posts where you act like an a55 just cause someone needed some help or putting ppl down for using toolkits. Look i dont come here to start anything with anybody but if i see ppl unfairly treated cause they are new or dont have much experience your gonna get called out on it. As far as "getting the fxxk out of here" nah i think ill stay
chris6278 said:
Help ppl? All you do is give ppl ****. Ive seen numerous posts where you act like an a55 just cause someone needed some help or putting ppl down for using toolkits. Look i dont come here to start anything with anybody but if i see ppl unfairly treated cause they are new or dont have much experience your gonna get called out on it. As far as "getting the fxxk out of here" nah i think ill stay
Click to expand...
Click to collapse
show me one post where i acted like an ass when someone needed help.
Simms is correct, its much easy to unlock using fastboot rather than a tool kit. When I first started modding it took me >5 minutes to learn how to do this. It always works and can really help you if you mess something up using a tool kit. If the OC doesn't recognize your phone, what screen is it showing (the TWRP logo) have you tried to hold power and volume down to boot into the boot loader? If you can boot into BL then you can flash anything via fastboot and fix this problem easily.
I am unlocked and rooted. When I tried change the forced encryption is when the phone became useless. I can get it into recovery (factory) and restart bootloader, etc.
But now it justs stay on the black and white Google when your first reboot your phone.
I have downloaded all the tools. I don't know the commands or the proper order.
My computer is not reconizing my phone after the encryption attempt.
addcancercat said:
I am unlocked and rooted. When I tried change the forced encryption is when the phone became useless. I can get it into recovery (factory) and restart bootloader, etc.
But now it justs stay on the black and white Google when your first reboot your phone.
I have downloaded all the tools. I don't know the commands or the proper order.
My computer is not reconizing my phone after the encryption attempt.
Click to expand...
Click to collapse
first thing you need to do is get the driver installed, so that your device would be disabled to your computer to adb/fastboot. you are going to have to flash the factory.img through your bootloader via fastboot. or, you can fastboot oem unlock your bootloader, flash a custom recovery, and adb push/sideload a rom/gapps/supersu to your phone and flash them via your new recovery.
simms22 said:
first thing you need to do is get the driver installed, so that your device would be disabled to your computer to adb/fastboot. you are going to have to flash the factory.img through your bootloader via fastboot. or, you can fastboot oem unlock your bootloader, flash a custom recovery, and adb push/sideload a rom/gapps/supersu to your phone and flash them via your new recovery.
Click to expand...
Click to collapse
Man you wouldn't know where I might find a more detailed step by step instructions on how exactly to do this. Then I could probably do it.
I have been updating drivers, uninstalling drivers, etc.
The tiol kit was great for unlocking and rooting. Then I tried to undo the forced encryption.
Sent from my SGH-I337 using Tapatalk
addcancercat said:
Man you wouldn't know where I might find a more detailed step by step instructions on how exactly to do this. Then I could probably do it.
I have been updating drivers, uninstalling drivers, etc.
The tiol kit was great for unlocking and rooting. Then I tried to undo the forced encryption.
Sent from my SGH-I337 using Tapatalk
Click to expand...
Click to collapse
this should help you out. if you have anything to adk about it, ask there or here. good luck! http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008

help with no data on any ROM coming back from M from maybe?

Hey guys, I am having some problems going from JDX down to a 5.1 ROM. I cannot get data on any of the ROMS I am trying.
I have tried to download a few radios seperate and flash them at the start, or after the fact and still nothing. I also manually went to the apn to set it up but the correct one is already there and that didn't work.
Is there something I need to flash to make it work correctly? I'm stumped!
thanks!
none
Did you check and make sure the bootloader was configured correctly? I don't know if it even changes it, I will see what mine says. If you have to downdrage it, you will have to search further, I don't know how to do that on this particular phone
Read this http://www.gottabemobile.com/2015/06/15/5-reasons-to-skip-android-m-beta-preview/
Downgrading is a Hassle
If you do decide to try the Android M beta release, you’ll have to completely erase your entire device and start over from a fresh install of Android. Users will need to backup apps and pictures, transfer all their data, re-download everything and set of the device the way they’d like. Then, if you decide you want to go back to Android 5 Lollipop, users will need to erase the device and do this all over again. It can be quite the hassle, time consuming, and frustrating for those new to Android, or aren’t used to doing this often.
Here is a youtube vid on how to downgrahttps://www.youtube.com/watch?v=TazsmCuA5Cwde
BL moto-apg8084-71.08 (sha-32b8854, then the date it was made
baseband d4.0-9625-02.95
product variant shamu xt1103 32gb p3a0
cpu apq8084 esi.1
That's what mine says, and your issue does sound like the BL got changed
Sorry I'm not more help, but that's what comes to mind rightaway
wow thank you do much for replying. That is what I thought too. I had 0 problems before with any ROM then I decided to try the JDX M preview ROM and since then going back hasn't worked.
I tried to download several bootloaders and radios and flashing them and using the toolkit to flash them. No luck I will watch that video and read that post and see if it helps me any.
Again, thank you!
so I downloaded it his way and flashed it his way and I still get no data.
gah!
none
You flashed the stock RUU? right? you should have gone to a google page that had the stock roms in them, it had links as well on the YT link I gave you, try again, I watched the vid and the maker was talking pretty fast, if you still have issues DL teamviewer to your computer and I will get on your puter and help ya out
lol, downgrading the bootloader will do nothing. im on m, with the m bootloader, and have hone to 5.1.1 a few times. always keeping my m bootliader.
if your apn is 100% correct, id just boot up, and eventually youll catch the signal, as long as its not disabled, or data isnt disabled.
of course, your sim card cohld have gone bad. they do die every now and then.
musicman625 said:
You flashed the stock RUU? right? you should have gone to a google page that had the stock roms in them, it had links as well on the YT link I gave you, try again, I watched the vid and the maker was talking pretty fast, if you still have issues DL teamviewer to your computer and I will get on your puter and help ya out
Click to expand...
Click to collapse
Hi Hi sorry for the delayted response.
Basically for whatever reason no CM ROMS would work at all. I tried some AOSP ones and they are completely fine and have no problems with them.
I Downloaded ROM Manager and will give a look into other CM ROMs in a little while to see if it works.
Thanks so much for all the help!
Mackie011 said:
Hi Hi sorry for the delayted response.
Basically for whatever reason no CM ROMS would work at all. I tried some AOSP ones and they are completely fine and have no problems with them.
I Downloaded ROM Manager and will give a look into other CM ROMs in a little while to see if it works.
Thanks so much for all the help!
Click to expand...
Click to collapse
Glad you got it back
---------- Post added at 09:05 AM ---------- Previous post was at 09:04 AM ----------
simms22 said:
lol, downgrading the bootloader will do nothing. im on m, with the m bootloader, and have hone to 5.1.1 a few times. always keeping my m bootliader.
if your apn is 100% correct, id just boot up, and eventually youll catch the signal, as long as its not disabled, or data isnt disabled.
of course, your sim card cohld have gone bad. they do die every now and then.
Click to expand...
Click to collapse
How do you like M? I was thinking about giving it a twirl, decided to wait until the bugs were gone, and it's more refined

H811 completely dead

Hey there everyone, here to report unfortunate news about my g4 has died all out. Was using it to navigate using maps to a job yesterday, when suddenly my phone reboots and gets in boot loop. I take off battery to boot up phone back on, but turns out it doesn't at all respond to turn on, I try the hard master reset buttons to then boot to twrp but not even that responds. Weird cuz I had 40 percent battery left, connected phone to my charger and three more and no response at all in boot up or even sign of life. What can I do?
I have the same problem, phone wont respond at all and it was doing a boot loop, now it just wont turn on or respond to charging/no led light, nothing.
What are my options?
Rooted/No Insurance.
ExhumedWolf said:
I have the same problem, phone wont respond at all and it was doing a boot loop, now it just wont turn on or respond to charging/no led light, nothing.
What are my options?
Rooted/No Insurance.
Click to expand...
Click to collapse
That's weird how this has happened when i was running completely stock rom 10n rooted. Sucks that my screen has a very thin hairline crack which T-Mobile told me that LG won't accept it for warranty since it has physical damage.
Is there a way to restore the phone to complete stock using download mode? I'm in the same boat and now need to research a solution before returning to T-Mobile. This happened to a friend, too.
In my case, I was playing Fallout Shelter, the phone froze, so I did a battery pull. Now it won't boot up. Sometimes I can get it to go as far as the "Android is upgrading screen, " but then it either freezes again or goes into a bootloop. Tried booting into TWRP, but it either won't, or it'll freeze while inside before I can attempt to restore a backup or anything.
partylikeaninjastar said:
Is there a way to restore the phone to complete stock using download mode? I'm in the same boat and now need to research a solution before returning to T-Mobile. This happened to a friend, too.
In my case, I was playing Fallout Shelter, the phone froze, so I did a battery pull. Now it won't boot up. Sometimes I can get it to go as far as the "Android is upgrading screen, " but then it either freezes again or goes into a bootloop. Tried booting into TWRP, but it either won't, or it'll freeze while inside before I can attempt to restore a backup or anything.
Click to expand...
Click to collapse
Tried to boot in download mode and haven't been able since this occured. Nothing at all works for me in booting up to anything through the buttons, hopefully you can get DL mode working so you can get your g4 working back to normal.
wadamean said:
Tried to boot in download mode and haven't been able since this occured. Nothing at all works for me in booting up to anything through the buttons, hopefully you can get DL mode working so you can get your g4 working back to normal.
Click to expand...
Click to collapse
When I tried, I was able to boot into download mode, I didn't have any KDZ or whatever downloaded already or the flash tool in order to actually do anything so it was pointless, but it appears to boot into DL mode with no issue. For all I know, though, even though it booted into DL mode, it could have been completely frozen and unresponsive.
I think I found a thread with instructions and a link to the KDZ I need to download. Going to give this a try when I get home from work in twelve hours. If that fail, it's off to T-Mobile I go....
I have the same issue. I was browsing G+ then the phone just froze and now I can't get it to boot up or get into twrp. It will only boot loop.
Edit 1: I got my phone to boot and did a factory reset but it just ended up freezing and rebooting just like before. I'm going to try and get into twrp and flash the 10n stock then go to t-mobile to try and get them to get me a new one. I have insurance but the phone just randomly died, no dropping, didn't get it wet, so I don't want to have to pay a deductible.
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
---------- Post added at 02:25 PM ---------- Previous post was at 02:23 PM ----------
That's to the lasted 10n version boot loader,DO NOT I REPEAT DO NOT FLASH THE BOOTLOADER TO A LOWER VERSION THEN YOU ALREADY HAVE! you will be beyond ****ed and not even lg can help you at that point..the bootladers have backwards protection to if you haven't updated to marshmallow flash the 10n bootloader( the most lasted bootloader for lp) and you should be fine.the lg flash tool should be included but be careful guys..I can't stress enough how important it is you flash the right BL..you will perma brick
mr turtle droid said:
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
---------- Post added at 02:25 PM ---------- Previous post was at 02:23 PM ----------
That's to the lasted 10n version boot loader,DO NOT I REPEAT DO NOT FLASH THE BOOTLOADER TO A LOWER VERSION THEN YOU ALREADY HAVE! you will be beyond ****ed and not even lg can help you at that point..the bootladers have backwards protection to if you haven't updated to marshmallow flash the 10n bootloader( the most lasted bootloader for lp) and you should be fine.the lg flash tool should be included but be careful guys..I can't stress enough how important it is you flash the right BL..you will perma brick
Click to expand...
Click to collapse
Thanks for the reminder. That's the thread I found and I also already made a mental note to flash the right image. My friend had this same problem and the person she tasked with fixing her phone flashed the wrong image and perma bricked her. Fortunately, T-Mobile still replaced her phone, though.
Sent from my LG-D851 using Tapatalk
mr turtle droid said:
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
---------- Post added at 02:25 PM ---------- Previous post was at 02:23 PM ----------
That's to the lasted 10n version boot loader,DO NOT I REPEAT DO NOT FLASH THE BOOTLOADER TO A LOWER VERSION THEN YOU ALREADY HAVE! you will be beyond ****ed and not even lg can help you at that point..the bootladers have backwards protection to if you haven't updated to marshmallow flash the 10n bootloader( the most lasted bootloader for lp) and you should be fine.the lg flash tool should be included but be careful guys..I can't stress enough how important it is you flash the right BL..you will perma brick
Click to expand...
Click to collapse
That's true and I have not flashed nothing at all and only remained all on 10n rom and bootloader and modem. Yet this still happened to me.
My phone lives!
partylikeaninjastar said:
My phone lives!
Click to expand...
Click to collapse
That's amazing news!!!!
Actually, I take it back. It stopped working after an hour and started doing the same thing. On my way to T-Mobile in a bit.
Sent from my LG-D851 using Tapatalk
partylikeaninjastar said:
My phone lives!
Click to expand...
Click to collapse
partylikeaninjastar said:
Actually, I take it back. It stopped working after an hour and started doing the same thing. On my way to T-Mobile in a bit.
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
Let us know how it goes with T-Mobile. I was planning on getting my phone back to stock and then going to T-Mobile. I haven't had any luck bringing my phone back.
WillDeC said:
Let us know how it goes with T-Mobile. I was planning on getting my phone back to stock and then going to T-Mobile. I haven't had any luck bringing my phone back.
Click to expand...
Click to collapse
No hassle at all. Surprisingly. He just asked me what happened, then ordered my replacement to be delivered. Will have a new phone on Tuesday.
Sent from my LG-D851 using Tapatalk
WillDeC said:
Let us know how it goes with T-Mobile. I was planning on getting my phone back to stock and then going to T-Mobile. I haven't had any luck bringing my phone back.
Click to expand...
Click to collapse
I have great news everyone! Today I was cleaning my room. And just moved my g4 around onto my bed and then I see that the screen comes on saying I need to charge it. Which then I plug in and it charges now. I then wait a good while, get it to magically boot onto twrp. So excited and only option was to wipe all except the storages. I did, then flashed 10n rom again, not its back to life with no issues. Need to go to T-Mobile to connect it back on.
partylikeaninjastar said:
No hassle at all. Surprisingly. He just asked me what happened, then ordered my replacement to be delivered. Will have a new phone on Tuesday.
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
Good to hear. I just want to try and get it to stock. Sometime I can get to boot twrp and don't want to have to deal with them questioning about if they try and factory reset it or something.
WillDeC said:
Good to hear. I just want to try and get it to stock. Sometime I can get to boot twrp and don't want to have to deal with them questioning about if they try and factory reset it or something.
Click to expand...
Click to collapse
Reason why this issue has occurred is most likely in my opinion because of xposed. There is versions that work and those that aren't so stable in certain devices. What I advise you to do is boot into twrp when you get the chance, wipe all except the storages. You will notice how stable the phone gets and won't be bootlooping, which is what I noticed. Then flash whatever rom you have. Boot up, skip all intro steps, download the zip to get it to stock so you get the replacement. Keep telling T-Mobile that maybe at the moment it seems stable but it does this and you have gotten so fed up with it and won't be leaving until a replacement takes place. Either warranty or at store.
wadamean said:
Reason why this issue has occurred is most likely in my opinion because of xposed. There is versions that work and those that aren't so stable in certain devices. What I advise you to do is boot into twrp when you get the chance, wipe all except the storages. You will notice how stable the phone gets and won't be bootlooping, which is what I noticed. Then flash whatever rom you have. Boot up, skip all intro steps, download the zip to get it to stock so you get the replacement. Keep telling T-Mobile that maybe at the moment it seems stable but it does this and you have gotten so fed up with it and won't be leaving until a replacement takes place. Either warranty or at store.
Click to expand...
Click to collapse
I've never put xposed on this phone. I put twrp, rooted and was using a debloated rom. I had actually removed root so I could use android pay. It was working fine then just froze and constant reboots and freezing. I've only been able to get into twrp once without it freezing and rebooting,
WillDeC said:
I've never put xposed on this phone. I put twrp, rooted and was using a debloated rom. I had actually removed root so I could use android pay. It was working fine then just froze and constant reboots and freezing. I've only been able to get into twrp once without it freezing and rebooting,
Click to expand...
Click to collapse
You shouldn't have removed root and just used root cloak so that android pay thinks your unrooted. That's what I have been using. Because debloated roms always come injected with root and at times it becomes their core use within to function. When you get the chance to boot into twrp. Wipe all except storages and then reflash.

Nexus 6 bootloop when updating to android 5.1

Hey everyone I'm looking here as my last resort before sending my phone back to Motorola.
Bought a Nexus 6 from motorola uk which was delivered yesterday, switched phone on and all the Google apps on the phone updated, then had a notification OTA to download and install android 5.1 which I did, towards the end of the install process I had an error with the green android and a red exclamation mark.
I powered the device off with the power button and it turned back on and ever since it says "Android is starting" "Optimizing app 1 of 125" once it goes through all the apps it gets to the android boot screen then just goes back to the "Android is starting" "Optimizing app 1 of 125" over and over and over. (Infinite bootloop)
Pointers: The phone is not unlocked or rooted as I'm a noob its just fresh out the box, also I never opened/unlocked the developer options.
I have tried various recovery mode fixes, wiping cache and wiping all data and then rebooting the device with no luck.
Is there anyway I can hook my N6 up to my computer and fix this with a tool kit etc? I'm willing to try but I'd need basic instructions and reassurance it wouldn't muck up my warranty if it didn't work as my only other option is to exchange for a new device.
I'm a noob so I need detailed basic step by step instructions.
Any help, advice etc would be hugely appreciated. Thanks
Just send it back, no point messing about with it if it brand new could down to a fault with the hardware itself.
ixon2001 said:
Just send it back, no point messing about with it if it brand new could down to a fault with the hardware itself.
Click to expand...
Click to collapse
Iv'e heard this is a common problem with the N6 whilst trying to update the OTA 5.1 I had no other apps on the phone it was fresh, I did nothing wrong, I know someone who has been through 4 devices with the same bloody issues! In the end he had to sideload 6.0 and I'm not confident in being able to do that.
Well best bet is to download wugfresh toolkit 2.10 i think is the latest version, follow the instructions carefully because first you need to unlock the bootloader then flash 6.0.1 which has just come out.
Using Wugfresh is the best way to go if your new to flashing & you can't really go wrong with it.
ixon2001 said:
Well best bet is to download wugfresh toolkit 2.10 i think is the latest version, follow the instructions carefully because first you need to unlock the bootloader then flash 6.0.1 which has just come out.
Using Wugfresh is the best way to go if your new to flashing & you can't really go wrong with it.
Click to expand...
Click to collapse
I`am sure most xperienced users (me included) will not agree with you The best way to unlock, flash and root is still adb/fastboot. Especialy for lesser xperienced users that are lost is something goes wrong while using the toolkit, wich happens frequently btw. Just check the help threads.
gee2012 said:
I`am sure most xperienced users (me included) will not agree with you The best way to unlock, flash and root is still adb/fastboot. Especialy for lesser xperienced users that are lost is something goes wrong while using the toolkit, wich happens frequently btw. Just check the help threads.
Click to expand...
Click to collapse
Lol it's not rocket science using adb, been doing that way for years but for somebody that never flashed, rooted ect I still think the toolkit best way to go at first because everything is done for you at a click of a button.
Yes things can go tits up when using toolkits, mainly because they don't follow simple instructions.
ixon2001 said:
Lol it's not rocket science using adb, been doing that way for years but for somebody that never flashed, rooted ect I still think the toolkit best way to go at first because everything is done for you at a click of a button.
Yes things can go tits up when using toolkits, mainly because they don't follow simple instructions.
Click to expand...
Click to collapse
Lets agree to disagree
OK
ixon2001 said:
Yes things can go tits up when using toolkits, mainly because they don't follow simple instructions.
Click to expand...
Click to collapse
No, but because toolkits are always behind at least one version with marshmallow. People kept bricking their devices with toolkits when marshmallow came out and they thought they could root it. As 6.0.1 came out they'll do something else wrong.
Toolkits are not help. It's the lazy way if everything is already working and up to date.
Also what can a toolkit do if this phone doesn't even have developer options turned on? If it's in boot loop, as the OP said, then the Enable OEM unlocking was never set, then the only solution is to send it back. Unless there's a toolkit magic we don't know about.
Sent from my Nexus 6 running cyosp using Tapatalk
istperson said:
N
Also what can a toolkit do if this phone doesn't even have developer options turned on? If it's in boot loop, as the OP said, then the Enable OEM unlocking was never set, then the only solution is to send it back. Unless there's a toolkit magic we don't know about.
Click to expand...
Click to collapse
I think op created another thread http://forum.xda-developers.com/nexus-6/help/nexus-6-stuck-bootloop-trying-to-update-t3266100 for this issue - and was somehow able to unlock the bootloader (not sure how that worked if OEM unlock was never set)
jj14 said:
(not sure how that worked if OEM unlock was never set)
Click to expand...
Click to collapse
It was said that some of the first Nexus 6s with the original 5.0 came out with a bootloader that didn't check for this switch.

help, stuck in bootloop and adb wont recognize

I have an LG V40Thinq running the unlocked US Pie rom. never had issues running it before, just tried uninstalling viper through magisk and rebooting. Now its stuck in bootloop and I cant even get adb to recognize it. Im very new to rooting phones and paid someone on here to root it and flash the new rom onto it, but I have been running that build for over a month now with no issues. Any help is greatly appreciated as I dont have much of an alternative to use atm.
SlipperyHank said:
I have an LG V40Thinq running the unlocked US Pie rom. never had issues running it before, just tried uninstalling viper through magisk and rebooting. Now its stuck in bootloop and I cant even get adb to recognize it. Im very new to rooting phones and paid someone on here to root it and flash the new rom onto it, but I have been running that build for over a month now with no issues. Any help is greatly appreciated as I dont have much of an alternative to use atm.
Click to expand...
Click to collapse
I ended up in a similar situation (with the same root and rom as you) and I asked vlad to redo everything. He only charged me $7 the second time. Definitely worth it!
nyttliv7 said:
I ended up in a similar situation (with the same root and rom as you) and I asked vlad to redo everything. He only charged me $7 the second time. Definitely worth it!
Click to expand...
Click to collapse
Even with adb not recognizing the device he was able to redo the flash? Cuz I cant seem to get it to load into custom recovery or get it recognized on my pc
SlipperyHank said:
Even with adb not recognizing the device he was able to redo the flash? Cuz I cant seem to get it to load into custom recovery or get it recognized on my pc
Click to expand...
Click to collapse
You should be able to get into 9008 mode like the first time
Vlad did the QDLoader9008 mode for me! I didn't want to do anything myself...
---------- Post added at 00:33 ---------- Previous post was at 00:32 ----------
SlipperyHank said:
Even with adb not recognizing the device he was able to redo the flash? Cuz I cant seem to get it to load into custom recovery or get it recognized on my pc
Click to expand...
Click to collapse
Yes!

Categories

Resources