Corrupt device really need help! - Nexus 6 Q&A, Help & Troubleshooting

Problem fixed! Thank you for you help! I didn't know this message was just a google scare thing.
Thank you XDA! Please delete

Did you research at all? You are supposed to do this...In order: unlocked bootloader > Flash Custom Recovery > Flash SuperSU zip.
Can you provide a screenshot with another phone or type the code. First rule is don't panic. Also you might be to sideload a zip of Android n to boot into Android.
Sent from my Nexus 6 using XDA-Developers mobile app

nexus_6_user said:
I was trying to root my phone using Androidrootz tool but now my device says it is corrupt. I'm very confused about flashing etc etc and really need some help. I have a 64gb version that was unlocked. I don't know which factory image to use. If someone could explain adb and connecting my phone that might be a good start for me. I can get into boot loader and recovery.
Click to expand...
Click to collapse
Does the phone boot after it gives you the corrupt message? All that means is the phone detected the /system was modified which in a lot of rooting methods is commonplace. Also there's a guide around somewhere about how to flash factory images which is more indepth than I'd be willing to type up right now.

ignore the message that you see, its googles way of scaring you. that's all that is.

StykerB said:
Does the phone boot after it gives you the corrupt message? All that means is the phone detected the /system was modified which in a lot of rooting methods is commonplace. Also there's a guide around somewhere about how to flash factory images which is more indepth than I'd be willing to type up right now.
Click to expand...
Click to collapse
But with the bootloader being locked (I assume it is) him rooting it that specific way didn't corrupt it just sent trips of the bootloader police. Security checks fail.
Sent from my Nexus 6 using XDA-Developers mobile app

Related

[Q] [PURE] Stuck in bootloop

Hi all, total newb here. (Sorry I know you probably hate these kinds of threads).
I apologize in advanced if this is a very simple case / has been discussed in the forums.
I've literally read everything I can in regards to this topic but being such a total newbie at this, I'm still not 100% sure if I got this right.
So basically my phone is XT1095 - which I didn't root or unlock boatlader (simply because I don't know why), that suddenly got into a boot loop.
So on that AP Fastboot screen.
So all options (including normal powerup, recovery and factory reset) produces
'failed to validate system image.
boot up failed'.
What should I do at this point? I've read on jcase's thread that this is a simple matter of "easily fixed by flashing proper boot.img".
Where can I find the "stock boot.img"?
I know graffixnyc has KXE21.187-42 files on his website which can be flashed. Is it pre-rooted though?
Or can I just easily use bhp090808's Multi Tool to fix this?
Can it be used while the phone is still in this bricked / bootlooped condition?
Honestly I dont mind being rooted if it means getting my phone fix. But if I can get it done without rooting it then it would be 'great' since if I fail in any way I won't void my warranty.
Sorry for asking a lot of things. As you can notice, I'm totally new at this. I've successfully rooted and install a custom ROM once in my old S3 but it was only because there was a thorough step to step process.
Again, thanks in advance and I really appreciate anyone's help
Cheers.
anyone?
koflok1234 said:
anyone?
Click to expand...
Click to collapse
I wouldn't unlock or root!!! You could lose your warranty. You can try a factory reset, else return your phone for warranty
godutch said:
I wouldn't unlock or root!!! You could lose your warranty. You can try a factory reset, else return your phone for warranty
Click to expand...
Click to collapse
Not a response I expect would found from XDA
I tried factory reset but it's stuck on that screen. Fail to validate image. I think the recovery.img is corrupted?
koflok1234 said:
Not a response I expect would found from XDA
I tried factory reset but it's stuck on that screen. Fail to validate image. I think the recovery.img is corrupted?
Click to expand...
Click to collapse
I doesn't make sense to void warranty to try to fix a problem that is covered under warranty. Maybe your emmc is defective or something like that, don't make matters worse.... You unlock your device when you have verified that everything is working, not when things start failing
I am under warranty but I am currently overseas so sending the phone and process the return is a bit of a hassle. So 'other' options is to do a local repair outside warranty here but that costs a bit.
So if I can fix it myself with a simple procedure then it might be the best way.
I'm having the same issue as well if anyone has figured out how to fix this I would be extremely grateful. I am still under warranty, but I'm nervous they will send me a replacement in worse shape than my current device.
My pure edition was stuck at the splash screen and I didn't previously unlock my bootloader. I also didn't have USB debugging checked so I couldn't find my phone using ADB. Unlocking a pure edition bootloader DOES NOT VOID warranty!!! So I unlocked my bootloader and flashed the factory files and restored the use of my phone. I then updated to lollipop, rooted my phone and checked USB debugging. That way I have full control of my phone and can fix it myself if something comes up. There is the thread saying the warranty won't be void after unlock.
https://forums.motorola.com/posts/677736c888?page=2
The problem now is that it is impossible to root or do anything else with me phone that doesn't involve fastboot
sianaka said:
The problem now is that it is impossible to root or do anything else with me phone that doesn't involve fastboot
Click to expand...
Click to collapse
same here. anybody solved the issue? can we recover through fastboot? anything we can try?
this happend after trying to root the device (step 7 in multi-too to be specific
You should be able to recover via fastboot if you have the factory image, there are some floating around here.
If it's an official one you don't even need to unlock your phone because the image is signed by Moto.
Here is a link to an official guide on how to flash.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
pwvandeursen said:
same here. anybody solved the issue? can we recover through fastboot? anything we can try?
this happend after trying to root the device (step 7 in multi-too to be specific
Click to expand...
Click to collapse
solved.
used fastboot to flash the files from multi-tool (recovery, system boot) booted back up, only pushed root (not TWRP), an d now fully functional again
pwvandeursen said:
solved.
used fastboot to flash the files from multi-tool (recovery, system boot) booted back up, only pushed root (not TWRP), an d now fully functional again
Click to expand...
Click to collapse
Can you possibly explain this step by step? Sorry I'm kind of new to this.
Also, will I be able to do this if my battery is low?
koflok1234 said:
Hi all, total newb here. (Sorry I know you probably hate these kinds of threads).
I apologize in advanced if this is a very simple case / has been discussed in the forums.
I've literally read everything I can in regards to this topic but being such a total newbie at this, I'm still not 100% sure if I got this right.
So basically my phone is XT1095 - which I didn't root or unlock boatlader (simply because I don't know why), that suddenly got into a boot loop.
So on that AP Fastboot screen.
So all options (including normal powerup, recovery and factory reset) produces
'failed to validate system image.
boot up failed'.
What should I do at this point? I've read on jcase's thread that this is a simple matter of "easily fixed by flashing proper boot.img".
Where can I find the "stock boot.img"?
I know graffixnyc has KXE21.187-42 files on his website which can be flashed. Is it pre-rooted though?
Or can I just easily use bhp090808's Multi Tool to fix this?
Can it be used while the phone is still in this bricked / bootlooped condition?
Honestly I dont mind being rooted if it means getting my phone fix. But if I can get it done without rooting it then it would be 'great' since if I fail in any way I won't void my warranty.
Sorry for asking a lot of things. As you can notice, I'm totally new at this. I've successfully rooted and install a custom ROM once in my old S3 but it was only because there was a thorough step to step process.
Again, thanks in advance and I really appreciate anyone's help
Cheers.
Click to expand...
Click to collapse
Well i booted his file, now my device is in a bootloop. i requested the original img file from the motorola site. Search it up in google. I will try it right now. Hope it works!!!

[Q] Think I soft-bricked my Nexus 6...any ideas?

Some background...Rooted and unlocked. I removed encryption right after I bought it.
I attempted to flash 5.1 the update. I flashed the bootloader and radio first, and rebooted the bootloader. Everything went fine until I tried to flash the system image. I got a lot of "sparse" errors.
When it rebooted it re-encrypted the device. But now nothing works. Phone, NFC ect shows errors. I can get into the bootoader, and I can flash stuff, but the recovery menu is gone,. It's just an error icon with "no connection" now.
Any ideas on how I can salvage this? I already backed everything up before I started. Is there a way I can just wipe everything and go back to stock? Even if it is 5.01?
EDIT - My bootloader is still showing as unlocked. I did not re-lock it.
JeffDenver said:
Some background...Rooted and unlocked. I removed encryption right after I bought it.
I attempted to flash 5.1 the update. I flashed the bootloader and radio first, and rebooted the bootloader. Everything went fine until I tried to flash the system image. I got a lot of "sparse" errors.
When it rebooted it re-encrypted the device. But now nothing works. Phone, NFC ect shows errors. I can get into the bootoader, and I can flash stuff, but the recovery menu is gone,. It's just an error icon with "no connection" now.
Any ideas on how I can salvage this? I already backed everything up before I started. Is there a way I can just wipe everything and go back to stock? Even if it is 5.01?
EDIT - My bootloader is still showing as unlocked. I did not re-lock it.
Click to expand...
Click to collapse
Install factory images using fastboot
https://developers.google.com/android/nexus/images
You might have "soft bricked" it, but if you still have bootloader access you are fine
I actually tried that, but it will not recognize it from ADB...I can flash stuff via fastboot, but ADB does not see it.
I did fully update the android SDK before I started. Should'nt that have updated all the drivers needed for ADB?
JeffDenver said:
I actually tried that, but it will not recognize it from ADB...I can flash stuff via fastboot, but ADB does not see it.
I did fully update the android SDK before I started. Should'nt that have updated all the drivers needed for ADB?
Click to expand...
Click to collapse
you update via fastboot, while youre in the bootloader. adb has nothing to do with it.
When I go to the platform tools folder, and use "adb devices", it tells me nothing after "list of devices attached". As if it does not see the phone.
When I attempt to "fastboot -w update image-shamu-lmy47d.zip", a window comes up and scrolls 3 or 4 lines too fast to see, and then exits. Nothing happens.
JeffDenver said:
When I go to the platform tools folder, and use "adb devices", it tells me nothing after "list of devices attached". As if it does not see the phone.
Click to expand...
Click to collapse
Have you updated the SDK? Drivers installed? Also, read up on how to use fastboot. Fastboot only works from bootloader, not when booted into Android.
I'm all for adb, but save yourself a headache and get wugs toolkit and use force flash.
Sent from my Nexus 6 using XDA Free mobile app
Better to learn some basics first then you shall fear no soft brick ever!
http://forum.xda-developers.com/showthread.php?t=2277112
Evolution_Freak said:
Have you updated the SDK? Drivers installed? Also, read up on how to use fastboot. Fastboot only works from bootloader, not when booted into Android.
Click to expand...
Click to collapse
SDK is updated. I assumed it updated drivers as well. If not, where do I get those?
I do understand that fastboot only works while in the bootloader. I have not attempted to use it while in Android.
JeffDenver said:
When I attempt to "fastboot -w update image-shamu-lmy47d.zip", a window comes up and scrolls 3 or 4 lines too fast to see, and then exits. Nothing happens.
Click to expand...
Click to collapse
Just extract the .zip and flash the things inside separately using fastboot. You can skip user data I believe (or not if you don't care about erasing your device). Using the -w switch would have erased it anyway. The commands are easy, just "fastboot flash system system.img" and the like. Change "system" and "system.img" for the file you're flashing.
Evolution_Freak said:
Have you updated the SDK? Drivers installed? Also, read up on how to use fastboot. Fastboot only works from bootloader, not when booted into Android.
Click to expand...
Click to collapse
Konfuzion said:
I'm all for adb, but save yourself a headache and get wugs toolkit and use force flash.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Where do I get that from?
JeffDenver said:
Where do I get that from?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=56913254
Sent from my Nexus 6 using XDA Free mobile app
---------- Post added at 12:56 PM ---------- Previous post was at 12:55 PM ----------
Evolution_Freak said:
Better to learn some basics first then you shall fear no soft brick ever!
http://forum.xda-developers.com/showthread.php?t=2277112
Click to expand...
Click to collapse
Better fear the bootloader downgrade soft brick
Sent from my Nexus 6 using XDA Free mobile app
Konfuzion said:
I'm all for adb, but save yourself a headache and get wugs toolkit and use force flash.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Are you sure you know what adb is?
:/
rootSU said:
Are you sure you know what adb is?
:/
Click to expand...
Click to collapse
What's it to you? Yeah I'm fine with adb thanks. If you want to discuss something other than helping the OP go ahead and pm me.
Sent from my Nexus 6 using XDA Free mobile app
mwalt2 said:
Just extract the .zip and flash the things inside separately using fastboot. You can skip user data I believe (or not if you don't care about erasing your device). Using the -w switch would have erased it anyway. The commands are easy, just "fastboot flash system system.img" and the like. Change "system" and "system.img" for the file you're flashing.
Click to expand...
Click to collapse
Ok, I did this. It appeared to work correctly, but...
My phone looks like it did before. In "about" I see it shows 5.1 as the version. I have lost root. Shouldn't I be reset to factory appearance since I overwrote the entire system? Everything looks intact, including nova launcher.
Phone appears to be working normally. I am on the phone on hold as I type this. I am just worried about problems down the road. Do I need to flash anything else? Can I assume the bootloader and radio installed correctly?
Konfuzion said:
What's it to you? Yeah I'm fine with adb thanks. If you want to discuss something other than helping the OP go ahead and pm me.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Its just you mentioned a toolkit as an alternative to adb but adb has nothing to do with any of this so if you're going to be helping the OP, I thought I'd better check that you know what you're talking about. ...which I don't think you do... So back to the point, how I'm helping the OP is by telling him to ignore everything you say. THAT'S "what's it" to me. Cheeky chops
@JeffDenver, ignore this guy. Use fastboot. Read general > all in one guide > question 28 for any info you may need, including drivers.
to repeat again, you use fastboot to flash the factory img, while youre in the bootloader. it should take you just several minutes to do, or a little bit longer if you are being very carefull. adb has nothing to do with it.
JeffDenver said:
Ok, I did this. It appeared to work correctly, but...
My phone looks like it did before. In "about" I see it shows 5.1 as the version. I have lost root. Shouldn't I be reset to factory appearance since I overwrote the entire system? Everything looks intact, including nova launcher.
Phone appears to be working normally. I am on the phone on hold as I type this. I am just worried about problems down the road. Do I need to flash anything else? Can I assume the bootloader and radio installed correctly?
Click to expand...
Click to collapse
its probably a good idea to factory reset since you're going up a major version and have already had problems.
rootSU said:
Its just you mentioned a toolkit as an alternative to adb but adb has nothing to do with any of this so if you're going to be helping the OP, I thought I'd better check that you know what you're talking about. ...which I don't think you do... So back to the point, how I'm helping the OP is by telling him to ignore everything you say. THAT'S "what's it" to me. Cheeky chops
@JeffDenver, ignore this guy. Use fastboot. Read general > all in one guide > question 28 for any info you may need, including drivers.
Click to expand...
Click to collapse
The reason I suggested wugs, is the first thing it has you do after installation is walks you through removing old drivers and installing the correct drivers and making sure that the phone is recognized. Then it will download the needed files and check the md5's which would help to avoid further problems.
Sent from my Nexus 6 using XDA Free mobile app

stuck in boot loop android is starting optimizing apps after update

sorry if this has been covered but i cant find anything the same as my situation and im pretty stuck.
I have just bought a nexus 6 and the phone prompted me to update to 5.1 so i have, once it restarted i am now stuck in a boot loop with it saying optimizing apps then restarts and the same again, i have tried booting into recovery and wipe data but just get the same.
I have tried using nexus root toolkit (wugsfresh) however cannot find fastboot connectivity so im stuck there.
The phone is not rooted and i cant seem to get access through adb ( i have not turned usb debugging on as the phone is new)
I really am not too clued up so im sorry if i need things explaining abit more.
Thanks in advance
viper1402 said:
sorry if this has been covered but i cant find anything the same as my situation and im pretty stuck.
I have just bought a nexus 6 and the phone prompted me to update to 5.1 so i have, once it restarted i am now stuck in a boot loop with it saying optimizing apps then restarts and the same again, i have tried booting into recovery and wipe data but just get the same.
I have tried using nexus root toolkit (wugsfresh) however cannot find fastboot connectivity so im stuck there.
The phone is not rooted and i cant seem to get access through adb ( i have not turned usb debugging on as the phone is new)
I really am not too clued up so im sorry if i need things explaining abit more.
Thanks in advance
Click to expand...
Click to collapse
flash a factory image, your update went no good. if you havent ever done this, i DO NOT RECOMMEND using a toolkit. toolkits are good for people who know what they are doing. if you dont kniw, you will remain clueless, and could make things much worse.
simms22 said:
flash a factory image, your update went no good. if you havent ever done this, i DO NOT RECOMMEND using a toolkit. toolkits are good for people who know what they are doing. if you dont kniw, you will remain clueless, and could make things much worse.
Click to expand...
Click to collapse
am i able to flash a factory image without being able to connect the device via adb? i just wasnt able to find the device on it
Thanks for the reply
viper1402 said:
am i able to flash a factory image without being able to connect the device via adb? i just wasnt able to find the device on it
Thanks for the reply
Click to expand...
Click to collapse
factory images are only flashed while youre in your bootloader, via fastboot. thetes a stick for directions in the general thread.
simms22 said:
factory images are only flashed while youre in your bootloader, via fastboot. thetes a stick for directions in the general thread.
Click to expand...
Click to collapse
right got it sorted thanks for the help now its saying i have an update for 5.1.1 is it worth doing this or is there a strong chance it will bootloop again ?
viper1402 said:
right got it sorted thanks for the help now its saying i have an update for 5.1.1 is it worth doing this or is there a strong chance it will bootloop again ?
Click to expand...
Click to collapse
I'd suggest avoiding the OTA's and fastboot flash the latest factory image. LMY48I
IMHO....
viper1402 said:
right got it sorted thanks for the help now its saying i have an update for 5.1.1 is it worth doing this or is there a strong chance it will bootloop again ?
Click to expand...
Click to collapse
is it worth it? YES! if you want, you can flaah the factory image for 5.1.1 instead of taking the ota. but chances are that the ota will be fine.
viper1402 said:
right got it sorted thanks for the help now its saying i have an update for 5.1.1 is it worth doing this or is there a strong chance it will bootloop again ?
Click to expand...
Click to collapse
How did u get it sorted? I just had a friend call me with exactly the same problem! He's not very tech savvy so it's proving difficult talking him thru it, so if u found an easy solution for me to pass on that would be great ?
boxa72 said:
How did u get it sorted? I just had a friend call me with exactly the same problem! He's not very tech savvy so it's proving difficult talking him thru it, so if u found an easy solution for me to pass on that would be great
Click to expand...
Click to collapse
As stated before. Forget OTA. Unlock bootloader and fastboot flash the images manually. Do not take OTA with bootloader locked. If OTA fails have to RMA. No fix.
I had the same issue today and like PRDOG1 said I was talking to him on my forum post. As soon as you get the phone unlock that bootloader, then just do flashes through the bootloader. It is safer, and as long as that bootloader is unlocked you can go ahead and load up any image you want thats factory and you will be fine.
Well it should be fine then coz the carriers in Aussie don't lock bootloaders. I just told him to bring the phone to me n I'll re-flash a stock image for him but I thought u may have found another way as I'm more familiar with Samsung and Windows than I am with Nexus. It seems pretty common this bootloop stuff after OTA with the N6.
Sent from my SM-G920I using Tapatalk
I suspect you are confusing carrier SIM lock with bootloader lock.
Carriers do not usually do anything with bootloader lock - they may force a SIM lock to their SIM cards however.
On the Nexus 6 however, unlocking the bootloader is pretty easy (assuming you can boot to the OS and select the option to allow OEM unlock). I'd recommend leaving the bootloader unlocked and flashing twrp asap, in case of any issues later.
Altho in Australia they don't carrier lock bootloaders the software comes locked for security reasons. If he didn"t unlock prior to the OTA update it is bricked and will require RMA.

Any Help/Ideas would be appreciated

Ok so I have a stock, rooted, unlocked but encrypted Nexus 6. Last night it took a bad fall. The glass only cracked in one spot, however the LCD is cracked in several areas. Turning the phone on resulted in a black display. it flickers a few small bars of convoluted color, then goes black. The phone was still on and with launch everywhere I could still "Ok Google..." to do a few things.
Now, like the total idiot I am, for some damn reason I turned the phone off after getting off the phone with Asurion. And because of encryption and the screen being unresponsive (black display) I can't enter the damn screen pattern to unlock it, so I can't boot it up to drag and drop files or use adb to wipe the phone.
Does anyone have any suggestions to where I can somehow either access my files or at the very least wipe the phone? Most of my info that was on the phone is backed up to Googles servers. The are few items that aren't, that I hope I can get, but if I can't, I need to make sure are wiped. Can I enter fastboot without the pattern unlock? Or should I look into someone to repair the screen to at least get it turned on and functional to do what I need?
Thanks in advance!
Phaded said:
Can I enter fastboot without the pattern unlock?
Click to expand...
Click to collapse
If memory serves me right, you can run fastboot commands without having to enter the pattern/pin.
jj14 said:
If memory serves me right, you can run fastboot commands without having to enter the pattern/pin.
Click to expand...
Click to collapse
OK thanks. I will try that when I get home and just flash the factory image to wipe. thanks!
Hmm... from Google support pages:
If your device is running Android 5.1 or higher: Your device is protected to prevent other people from using it if it's been reset to factory settings. To ensure that it's really you doing the reset, you'll need to enter a Google username and password associated with the device after factory reset. If you don't have this information, you won't be able to finish the setup process and use the device at all after factory reset.
Does this mean even if I wipe it, the phone won't be usable for anyone?? they can't refurbish the phone because the phone will need my google info??
Eh screw it... Just gonna send it into Motorola
Phaded said:
Hmm... from Google support pages:
If your device is running Android 5.1 or higher: Your device is protected to prevent other people from using it if it's been reset to factory settings. To ensure that it's really you doing the reset, you'll need to enter a Google username and password associated with the device after factory reset. If you don't have this information, you won't be able to finish the setup process and use the device at all after factory reset.
Does this mean even if I wipe it, the phone won't be usable for anyone?? they can't refurbish the phone because the phone will need my google info??
Click to expand...
Click to collapse
yup, mean even after you wipe it, lets say 100 times, itll still ask you for your password. its security, there would be no point if you could wipe it away. but, there is a way to get rid of it, by flashing the 5.0 or 5.0.1 factory images.
simms22 said:
yup, mean even after you wipe it, lets say 100 times, itll still ask you for your password. its security, there would be no point if you could wipe it away. but, there is a way to get rid of it, by flashing the 5.0 or 5.0.1 factory images.
Click to expand...
Click to collapse
oh so if i flash an older factory image that didn't have that security feature it'll work? thanks.
Phaded said:
oh so if i flash an older factory image that didn't have that security feature it'll work? thanks.
Click to expand...
Click to collapse
yes, as long as your bootloader is unlocked. those images didn't have the security yet.
Phaded said:
they can't refurbish the phone because the phone will need my google info??
Click to expand...
Click to collapse
Hate to say this, but that's their problem You can bet that Google/Motorola will know how to get around it
---------- Post added at 01:42 PM ---------- Previous post was at 01:40 PM ----------
simms22 said:
yes, as long as your bootloader is unlocked. those images didn't have the security yet.
Click to expand...
Click to collapse
Wasn't there some issue with downgrading the bootloader causing problems? Or am I confusing with some other device?
jj14 said:
Hate to say this, but that's their problem You can bet that Google/Motorola will know how to get around it
---------- Post added at 01:42 PM ---------- Previous post was at 01:40 PM ----------
Wasn't there some issue with downgrading the bootloader causing problems? Or am I confusing with some other device?
Click to expand...
Click to collapse
It's my understanding, but I am new to the N6 so correct me if I am wrong, you can downgrade the 5.0 or 5.0.1 factory img as long as you don't downgrade to 71.05 bootloader.
byrdcfmma said:
It's my understanding, but I am new to the N6 so correct me if I am wrong, you can downgrade the 5.0 or 5.0.1 factory img as long as you don't downgrade to 71.05 bootloader.
Click to expand...
Click to collapse
that sounds about right. Just wanted to make sure op didn't flash all images in the factory image
jj14 said:
that sounds about right. Just wanted to make sure op didn't flash all images in the factory image
Click to expand...
Click to collapse
Maybe someone with more exp can give the exact process. I assume you are looking for a img with no bootloader, recovery, and radio like these http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052 but older img's
I just got my N6 yesterday, and been reading my a$$ off so I don't mess anything up. So far I have unlocked the bootloader, rooted and installed TWRP.
byrdcfmma said:
Maybe someone with more exp can give the exact process. I assume you are looking for a img with no bootloader, recovery, and radio like these http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052 but older img's
I just got my N6 yesterday, and been reading my a$$ off so I don't mess anything up. So far I have unlocked the bootloader, rooted and installed TWRP.
Click to expand...
Click to collapse
One can always go to the google developer images site (developers.google.com/android/nexus/images) and download the image they need. Unzip the downloaded file, and unzip the resulting file. In that, you'll find yet some img files, and yet another zip file that will contain the rest of the img files. Choose which one you want, and flash away
Ok so I was able to get it so the lock screen pattern is gone.
At this point I'm about to do insurance claim.
I want to pull my data (pics etc) off.
I have twrp installed and can get into recovery. Adb devices results in showing my device.
Adb/USB debugging isn't active when booted normally as I flashed new system
Tried using a tool to pull using adb, but no data gets pulled
Anyone have a method for pulling my data off? It's set to charge mode by default so it doesn't show in windows explorer.
Thanks
Sent from my Nexus 6 using XDA Free mobile app
I'm currently in the exact same predicament. Let me know how it goes.
Phaded said:
Ok so I was able to get it so the lock screen pattern is gone.
At this point I'm about to do insurance claim.
I want to pull my data (pics etc) off.
I have twrp installed and can get into recovery. Adb devices results in showing my device.
Adb/USB debugging isn't active when booted normally as I flashed new system
Tried using a tool to pull using adb, but no data gets pulled
Anyone have a method for pulling my data off? It's set to charge mode by default so it doesn't show in windows explorer.
Thanks
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Use adb pull from booted into recovery.
danarama said:
Use adb pull from booted into recovery.
Click to expand...
Click to collapse
Do you happen to know what path I would enter to pull from? I have to specify the target correct? I tried using an adb recovery tool, but when it went to /sdcard it said that path didn't exist.
I believe right now I flashed a 5.0 image (pre forced encryption?)
Sent from my Nexus 6 using XDA Free mobile app
This is the tool I tried to use:
http://forum.xda-developers.com/showthread.php?t=2339530
Sent from my Nexus 6 using XDA Free mobile app
Phaded said:
Do you happen to know what path I would enter to pull from? I have to specify the target correct? I tried using an adb recovery tool, but when it went to /sdcard it said that path didn't exist.
I believe right now I flashed a 5.0 image (pre forced encryption?)
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Is it lollipop?
You need to mount data or sdcard first.
this should work
Code:
adb shell
mount /data
exit
adb pull /data/media/0/* c:\users\phaded\desktop\mybackup\
I've made some assumptions above.
danarama said:
Is it lollipop?
You need to mount data or sdcard first.
this should work
Code:
adb shell
mount /data
exit
adb pull /data/media/0/* c:\users\phaded\desktop\mybackup\
I've made some assumptions above.
Click to expand...
Click to collapse
Yes it's lollipop, just an earlier version of it that didn't have the pattern lock (or whatever security) prompt at boot. I think 5.0.1.
I'm not rooted, does that matter for adb shell in recovery?
/data/media/0/ is my whole sd card correct? Is there a command that will show my directory in that path so I can cherry pick the folders to extract?
Sent from my Nexus 6 using XDA Free mobile app

Bricked Nexus 6

Hi guys -
I'm somewhat a newbie here. I think I have bricked my Nexus 6. I had root and an unlocked bootloader. I had Chroma riom installed and was trying to go back to stock rom, unrooted with locked bootloader and through TWRP i deleted everything, including the OS I believe. So now my phone is locked on the Google startup screen (unlocked bootloader) . Suggestions?
Thanks -
John
if your bootloader is unlocked you should be able to fastboot clear cache and user data , then flash a rom from twrp. I would refrain from ever locking the bootloader back up since the update where you have to enable unlock bootloader in Dev Options.
droidstyle said:
if your bootloader is unlocked you should be able to fastboot clear cache and user data , then flash a rom from twrp. I would refrain from ever locking the bootloader back up since the update where you have to enable unlock bootloader in Dev Options.
Click to expand...
Click to collapse
me too I'm have Nexus 6 5.1.1 no recovery...except the bootloader that's locked Code: 2 , i can't unlock it, any solution !!?
hadifreestyler said:
me too I'm have Nexus 6 5.1.1 no recovery...except the bootloader that's locked Code: 2 , i can't unlock it, any solution !!?
Click to expand...
Click to collapse
no you are bricked unfortunately. the unlock bootlader option in dev options really seems to have caused more issues then good.
I am wondering if Jtag will fix these devices?
jpl81905 said:
Suggestions?
Click to expand...
Click to collapse
Stop.
Read.
A lot.
You have an unlocked nexus with custom recovery installed, and you don't know what to do? You shouldn't be messing with this stuff. You lack VERY basic understanding. Read the stickies.
https://developers.google.com/android/nexus/images?hl=en
Factory images. Follow their directions.
scryan said:
Stop.
Read.
A lot.
You have an unlocked nexus with custom recovery installed, and you don't know what to do? You shouldn't be messing with this stuff. You lack VERY basic understanding. Read the stickies.
https://developers.google.com/android/nexus/images?hl=en
Factory images. Follow their directions.
Click to expand...
Click to collapse
Thank you. I think.
jpl81905 said:
Hi guys -
I'm somewhat a newbie here. I think I have bricked my Nexus 6. I had root and an unlocked bootloader. I had Chroma riom installed and was trying to go back to stock rom, unrooted with locked bootloader and through TWRP i deleted everything, including the OS I believe. So now my phone is locked on the Google startup screen (unlocked bootloader) . Suggestions?
Thanks -
John
Click to expand...
Click to collapse
The easiest way if you are not familiar with ADB is to download the nexus tool kit located on these forums from WUGFRESH. That tool will walk you through a step by step process on how to flash stock back. You are far from bricked. I have deleted my entire phone many a times and just re flashed stock back easily. As long as your boot loader is unlocked you are fine
Link to toolkit: http://www.wugfresh.com/nrt/
The option you are going to want to use is on the front of the toolkit called flash stock + un-root. You can watch some videos on his website as well for flashing stock. That is all you need to do .
Any questions let me know, send me a PM
backdown00 said:
The easiest way if you are not familiar with ADB is to download the nexus tool kit located on these forums from WUGFRESH. That tool will walk you through a step by step process on how to flash stock back. You are far from bricked. I have deleted my entire phone many a times and just re flashed stock back easily. As long as your boot loader is unlocked you are fine
Link to toolkit: http://www.wugfresh.com/nrt/
The option you are going to want to use is on the front of the toolkit called flash stock + un-root. You can watch some videos on his website as well for flashing stock. That is all you need to do .
Any questions let me know, send me a PM
Click to expand...
Click to collapse
It is not the easiest option. The easiest option is plug the USB cable in, boot to TWRP, enable MTP mode and copy a rom to the sdcard.
Also, many senior members here will discourage the use of toolkits for those who are not familiar with adb or fastboot. It is best to learn these and use them at least once before starting to use toolkits. Toolkits do not "walk you through". They take you through without explaining anything.
danarama said:
It is not the easiest option. The easiest option is plug the USB cable in, boot to TWRP, enable MTP mode and copy a rom to the sdcard.
Also, many senior members here will discourage the use of toolkits for those who are not familiar with adb or fastboot. It is best to learn these and use them at least once before starting to use toolkits. Toolkits do not "walk you through". They take you through without explaining anything.
Click to expand...
Click to collapse
In a perfect world, I am sure we would all love to dive in and discover everything and be experts in all fields as time would not be a factor. I do not disagree it is helpful to learn ADB and fastboot commands and understand what they do. At this point in time though, the end goal here is to get his phone back up and running as fast as possible and then he can do the post-mortem to figure out what he did wrong and how to fix it .
I am guessing hes not very familiar with TWRP since he wound up in this situation. The toolkit alleviates the need for knowledge and gets the job done. I'm sure after this, the OP will research how to use his phone before trying to do anything next.
backdown00 said:
In a perfect world, I am sure we would all love to dive in and discover everything and be experts in all fields as time would not be a factor. I do not disagree it is helpful to learn ADB and fastboot commands and understand what they do. At this point in time though, the end goal here is to get his phone back up and running as fast as possible and then he can do the post-mortem to figure out what he did wrong and how to fix it .
I am guessing hes not very familiar with TWRP since he wound up in this situation. The toolkit alleviates the need for knowledge and gets the job done. I'm sure after this, the OP will research how to use his phone before trying to do anything next.
Click to expand...
Click to collapse
..but even so, your method is overkill. It is really simple to boot into TWRP and look in the menu for the "Enable MTP" option. Once that is done, the phone appears in "Computer" as an MTP device, just like when you boot into android. Then, simply dragging and dropping a ROM onto that device then flashing it via recovery will get him back up and running. There is nothing simpler or quicker than this.
Sorry, I do not intend to be confrontational here.

Categories

Resources