Hello guys,
This is possibly the first ever phone I have bricked. Since I moved from Chroma to Euphoria my Nexus 6 was reporting 23GB of total available storage, that's 3GB less than what I was getting with Chroma.
So I decided to revert back to stock hoping that would have sorted the partition layout but found myself in a bootloop. I tried several factory versions with no go, bootloop was still persisting. At that point I was like I am going to relock the bootloader to see if that makes any difference, and when I realized it did not and I tried to unlock it again, from that point on I realized I was very much screwed.
The current situation. I flashed a 5.0.1 factory stock that is in bootloop, bootloader is locked, no access to the stock recovery.
I have made a ton of researches and it seems I will have to send the device on repair.
Any idea of what else I could possibly try to rescue this phone?
How's that there's not a way to force unlocking the bootloader from fastboot when the system is not in a operational state?
I will appreciate any help.
Thanks
Segnale007 said:
Hello guys,
This is possibly the first ever phone I have bricked. Since I moved from Chroma to Euphoria my Nexus 6 was reporting 23GB of total available storage, that's 3GB less than what I was getting with Chroma.
So I decided to revert back to stock hoping that would have sorted the partition layout but found myself in a bootloop. I tried several factory versions with no go, bootloop was still persisting. At that point I was like I am going to relock the bootloader to see if that makes any difference, and when I realized it did not and I tried to unlock it again, from that point on I realized I was very much screwed.
The current situation. I flashed a 5.0.1 factory stock that is in bootloop, bootloader is locked, no access to the stock recovery.
I have made a ton of researches and it seems I will have to send the device on repair.
Any idea of what else I could possibly try to rescue this phone?
How's that there's not a way to force unlocking the bootloader from fastboot when the system is not in a operational state?
I will appreciate any help.
Thanks
Click to expand...
Click to collapse
Do you have TWRP or stock recovery?
cam30era said:
Do you have TWRP or stock recovery?
Click to expand...
Click to collapse
Nope I do not. I don't even have access to the stock recovery. For some reason when I select the stock recovery the recovery menu does not appear. It just comes up a dead android with a question mark and nothing else..
Segnale007 said:
Nope I do not. I don't even have access to the stock recovery.
Click to expand...
Click to collapse
I'm sorry to tell you that the only thing you can do is return it for repair/replacement. FWIW: if you had left the bootloader unlocked, we could have helped you.
cam30era said:
I'm sorry to tell you that the only thing you can do is return it for repair/replacement. FWIW: if you had left the bootloader unlocked, we could have helped you.
Click to expand...
Click to collapse
I kinda knew it.. This Nexus 6 was bought outside of the Play Store. Will Motorola either replace it or repair it?
I am just gonna say I woke up in the morning and found the phone in bootloop..
Segnale007 said:
I kinda knew it.. This Nexus 6 was bought outside of the Play Store. Will Motorola either replace it or repair it?
I am just gonna say I woke up in the morning and found the phone in bootloop..
Click to expand...
Click to collapse
You have nothing to loose by contacting them and asking.
What 5.0.1 factory stock file did you flash?
Mega Montana said:
What 5.0.1 factory stock file did you flash?
Click to expand...
Click to collapse
This one right here https://dl.google.com/dl/android/aosp/shamu-lrx22c-factory-ff173fc6.tgz
Flashing that file following the correct steps should not have sent the phone in a bootloop. Gonna need a bit more info to know what got screwed up. Also, have you connected your phone to your PC to see if it recognizes it? You said you can't boot into recovery but what about the bootloader, power + vol down?
Mega Montana said:
Flashing that file following the correct steps should not have sent the phone in a bootloop. Gonna need a bit more info to know what got screwed up. Also, have you connected your phone to your PC to see if it recognizes it? You said you can't boot into recovery but what about the bootloader, power + vol down?
Click to expand...
Click to collapse
Depends if he had a 5.1 bootloader before or not. Attempts to downgrade the BL from 5.1 will result in a loop.
If it appears when connecting to the PC as qhsusb mode, then it's fixable. If it appears normally as a fastboot device, then it needs repairing.
Guys after 6 hours of nightmare I am glad to say it all ended up in a big scare.
Here is how I managed to get around the bootloop and get android to boot up.. http://forum.xda-developers.com/showpost.php?p=61079544&postcount=312
Thanks for the help
Segnale007 said:
Guys after 6 hours of nightmare I am glad to say it all ended up in a big scare.
Here is how I managed to get around the bootloop and get android to boot up.. http://forum.xda-developers.com/showpost.php?p=61079544&postcount=312
Thanks for the help
Click to expand...
Click to collapse
How did you do that with a locked bootloader?
cam30era said:
How did you do that with a locked bootloader?
Click to expand...
Click to collapse
I have reason to believe that the procedure outlined in the link I posted did not help me. What rather helped me must have been that I flashed userdata an cache from 5.1.1 factory stock to the 5.0.1 factory stock I had bootlooping.
I just felt to mention that I followed that procedure, but I bet its not what managed to help me booting back in android.
Segnale007 said:
I have reason to believe that the procedure outlined in the link I posted did not help me. What rather helped me must have been that I flashed userdata an cache from 5.1.1 factory stock to the 5.0.1 factory stock I had bootlooping.
I just felt to mention that I followed that procedure, but I bet its not what managed to help me booting back in android.
Click to expand...
Click to collapse
Well, I'm glad for you. But I still don't understand how you could flash anything with a locked bootloader.
cam30era said:
Well, I'm glad for you. But I still don't understand how you could flash anything with a locked bootloader.
Click to expand...
Click to collapse
Maybe he had the downgrade "brick" as i suggested a page back. Only way I know to flash when locked.
Or maybe the format part of a flash fixed itm
rootSU said:
Maybe he had the downgrade "brick" as i suggested a page back. Only way I know to flash when locked.
Or maybe the format part of a flash fixed itm
Click to expand...
Click to collapse
Aahh. That makes sense. I'm still amazed that recovery was this easy.
cam30era said:
Well, I'm glad for you. But I still don't understand how you could flash anything with a locked bootloader.
Click to expand...
Click to collapse
rootSU said:
Maybe he had the downgrade "brick" as i suggested a page back. Only way I know to flash when locked.
Or maybe the format part of a flash fixed itm
Click to expand...
Click to collapse
I am not sure whether I had a softbrick or a downgrade brick, all I know is that with a locked bootloader I was able to format and flash only cache and userdata, and btw while googling I have also found other people in the same situation as the one I have been that were also able to format and flash userdata and cache partitions with a locked bootloader.
I am just surprised to see the phone booting with a userdata and cache files from a newer version of android. That's what probably saved my butt.
Segnale007 said:
I am not sure whether I had a softbrick or a downgrade brick, all I know is that with a locked bootloader I was able to format and flash only cache and userdata, and btw while googling I have also found other people in the same situation as the one I have been that were also able to format and flash userdata and cache partitions with a locked bootloader.
Btw I was surprised to see the phone booting with a userdata and cache files from a newer version of android.
Click to expand...
Click to collapse
Most of those who were able to successfully format cache and userdata still had TWRP installed. You are very lucky. Should buy a lotto ticket today.
Segnale007 said:
I am not sure whether I had a softbrick or a downgrade brick, all I know is that with a locked bootloader I was able to format and flash only cache and userdata, and btw while googling I have also found other people in the same situation as the one I have been that were also able to format and flash userdata and cache partitions with a locked bootloader.
I am just surprised to see the phone booting with a userdata and cache files from a newer version of android. That's what probably saved my butt.
Click to expand...
Click to collapse
You can format cache and userdata with a locked bootloader. You cannot flash cache or userdata with a locked bootloader... Unless your bootloader is "bricked" as per the thread you linked to ultimately.
FYI formatting has the exact same result as flashing userdata and cache. So the options are:
1) you formatted which fixed it
2) you were bootloader bricked and had to use a gpt.bin to fix it.
Related
My nexus 6 is unlocked and is running stock 5.0.1, rooted. . It has twrp and is decrypted.
I tried to sideload the 5.1 ota but it doesnt work.
I tried flashing the new 5.1 factory image but that doesnt work.
I'm tired of all this now, I just want my phone running stock 5.1 , locked , encrypted ,unrooted so I can just get ota next time from Google whenever they send it out.
Any guidance on what I need to do would be appreciated.
Use Wug's Nexus Root Toolkit :good:
Edit : Now I'm currently "Optimising app..." loop.
I tried using tge NRT to flash it back to stock but it didn't work.
I would first make a TWRP backup, then I would flash the boot image (decrypted if you want and make sure its the new one), system, radio and then reboot. I flashed everything fine while keeping twrp on my phone but I didn't like not having a custom ROM plus it was a little laggy so I restored a TWRP backup. My phone did bootloop for a while but eventually it booted 5.1. I would be careful since 5.1 seems to be having some issues in general.
http://forum.xda-developers.com/nex...gs-nexus-root-toolkit-v1-9-8-t2947452/page101
Quote:
Originally Posted by baudi11
Same thing happened to me. Here's what I did.
1. Press and hold power, volume up, and volume down. Keep holding them down until the phone boots into bootloader mode.
2. Go back to the toolkit and click the radio button labeled "Soft bricked/bootloop"
3. Click "Flash stock plus unroot"
4. Check all the boxes under "Settings", including "Post-flash factory reset" then click OK.
5. Follow the toolkit instructions from there.
This got me out of the bootloop, successfully installed 5.1, and kept all my apps and settings. Good luck.
Click to expand...
Click to collapse
It worked for me after that. Now I'm booted in 5.1
When I try to flash the factory images directly from Google I get the following errors even though the MD5 checks out.
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778070480 bytes
error: update package missing system.img
Press any key to exit...
celeriL said:
http://forum.xda-developers.com/nex...gs-nexus-root-toolkit-v1-9-8-t2947452/page101
It worked for me after that. Now I'm booted in 5.1
Click to expand...
Click to collapse
Thanks so much! This worked perfectly. Exactly what I needed. The past couple days have been so annoying but now it's over. Thanks again!
Giuseppe1010 said:
Thanks so much! This worked perfectly. Exactly what I needed. The past couple days have been so annoying but now it's over. Thanks again!
Click to expand...
Click to collapse
Glad to help!
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
rootSU said:
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
Click to expand...
Click to collapse
HaHaa. Tried and true. Always works.
prdog1 said:
HaHaa. Tried and true. Always works.
Click to expand...
Click to collapse
rootSU said:
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
Click to expand...
Click to collapse
I agree that always works without fail and is much easier than a tool kit. I don't like tool kits because people need to learn the correct way to flash things before using one because its better to understand what you are flashing should there be an error.
Pilz said:
I agree that always works without fail and is much easier than a tool kit. I don't like tool kits because people need to learn the correct way to flash things before using one because its better to understand what you are flashing should there be an error.
Click to expand...
Click to collapse
I totally agree. Have done successful manual flash when tool kits failed. Seen on Nexus 6 already.Saved my soft brick with manual flash when tool kit failed.
Pilz said:
I agree that always works without fail and is much easier than a tool kit. I don't like tool kits because people need to learn the correct way to flash things before using one because its better to understand what you are flashing should there be an error.
Click to expand...
Click to collapse
I don't have anything against toolkits on some devices, so long as it is not used as a shortcut to learning the basics. That said, on a nexus, I don't really see any need to be honest.
rootSU said:
I don't have anything against toolkits on some devices, so long as it is not used as a shortcut to learning the basics. That said, on a nexus, I don't really see any need to be honest.
Click to expand...
Click to collapse
Thats how I feel because its so easy my wife could do it and she doesn't know anything about flashing. Toolkits are good for non Nexus devices, I just don't see a point when we need to learn things the correct way first.
I hope the bugs get sorted out so people don't hard brick their phones anyone
rootSU said:
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
Click to expand...
Click to collapse
Im a complete fastboot novice since this is my first nexus device (always had samsung phones up until now) and although I managed to root and unlock the boot loader I want to make sure I learn all the basics including flashing (side loading?) subsequent updates.
So Im currently rooted, unlocked bootloader on a 5.01. custom rom. How would I go about flashing the 5.1 update manually?
Im assuming that once I extract the update zip file I will find all the images that need to be flashed....what order do i do them in? How do I take into account the boot loader locking issue people have been facing that results in a bricked device?
Thanks in advance.
EDIT: I found this thread which outlines what I need to do http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
I only have two question now:
1. Im assuming the system image will wipe out the custom rom im on but not the data will leaving the data cause a problem? whats the command line to wipe data?
2. This doesnt address the boot loader locking issue causing a brick that people have been facing. This process involves updating the boot loader what do i have to do to make sure I dont brick my device?
Thanks again
kingofkings11 said:
Im a complete fastboot novice since this is my first nexus device (always had samsung phones up until now) and although I managed to root and unlock the boot loader I want to make sure I learn all the basics including flashing (side loading?) subsequent updates.
So Im currently rooted, unlocked bootloader on a 5.01. custom rom. How would I go about flashing the 5.1 update manually?
Im assuming that once I extract the update zip file I will find all the images that need to be flashed....what order do i do them in? How do I take into account the boot loader locking issue people have been facing that results in a bricked device?
Thanks in advance.
EDIT: I found this thread which outlines what I need to do http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
I only have two question now:
1. Im assuming the system image will wipe out the custom rom im on but not the data will leaving the data cause a problem? whats the command line to wipe data?
2. This doesnt address the boot loader locking issue causing a brick that people have been facing. This process involves updating the boot loader what do i have to do to make sure I dont brick my device?
Thanks again
Click to expand...
Click to collapse
You could simply not update the bootloader. Bare minimum requirements is update system and boot (kernel). if you want to learn more about fastboot, go to general > All in one guide > Question 28.
If you do not update the bootloader, you'll never get an OTA but it doesn't seem like you're wanting that anyway.
In regards to data, yes it could cause a problem if you're using a custom rom. You can use fastboot erase data command. This also wipes your /sdcard though.
I broke the screen on my Verizon Nexus 6 and our internet went out today, but I wanted to flash it to stock before going to Verizon and seeing if they'll replace it. So I had a stock rom on my phone, flashed that, then locked the bootloader. I wasn't thinking about the recovery... So now, I can't unlock the bootloader because when I try to boot up the device, the TWRP screen comes up, but it just boot loops back to that screen. All I can boot into is the bootloader but without adb access, I don't know what to do.... Anybody have any ideas?
WyldOne91 said:
I broke the screen on my Verizon Nexus 6 and our internet went out today, but I wanted to flash it to stock before going to Verizon and seeing if they'll replace it. So I had a stock rom on my phone, flashed that, then locked the bootloader. I wasn't thinking about the recovery... So now, I can't unlock the bootloader because when I try to boot up the device, the TWRP screen comes up, but it just boot loops back to that screen. All I can boot into is the bootloader but without adb access, I don't know what to do.... Anybody have any ideas?
Click to expand...
Click to collapse
From bootloader use the fastboot commands:
fastboot format userdata
fastboot format cache
This will allow you back into TWRP and you can restore a backup or flash a ROM. Then you can start over.
Evolution_Freak said:
From bootloader use the fastboot commands:
fastboot format userdata
fastboot format cache
This will allow you back into TWRP and you can restore a backup or flash a ROM. Then you can start over.
Click to expand...
Click to collapse
Thank you so much! I just tried this and while it didn't go into TWRP, it did boot into the OS. So either way, I can work with it now.
WyldOne91 said:
Thank you so much! I just tried this and while it didn't go into TWRP, it did boot into the OS. So either way, I can work with it now.
Click to expand...
Click to collapse
No problem. Glad you're up and running!
Thank you so much! Just bought the nexus 6 like 4 hours ago and did the same thing as WyldOne91! Allready said good bye to my new nexus, but you saved my/our day!
Antochrist said:
Thank you so much! Just bought the nexus 6 like 4 hours ago and did the same thing as WyldOne91! Allready said good bye to my new nexus, but you saved my/our day!
Click to expand...
Click to collapse
Thank YOU for reading and finding the solution. :good:
Trying to sell my Nexus 6 I believe I bricked it. After rooting the device I used Chainfire 3d program and it made me stuck on google sign. I tried literally everything. I can boot into teamwin TWR recovery. I tried factory resetting wiping cache and delvic. Problem is my bootloader is coming up locked. Tried using fastboot many times to flash everything back keep getting remote failure. Need help, is it possible im just screwed at this point. Ive used about everything it is just stuck saying Google. PLEASE HELP!!!!
chainfires 3d program hasnt worked on a nexus in years. and you do need to boot back up to enable unlocking the bootloader in the developer options. have you tried wiping data in twrp recovery?
zacrivera24 said:
Trying to sell my Nexus 6 I believe I bricked it. After rooting the device I used Chainfire 3d program and it made me stuck on google sign. I tried literally everything. I can boot into teamwin TWR recovery. I tried factory resetting wiping cache and delvic. Problem is my bootloader is coming up locked. Tried using fastboot many times to flash everything back keep getting remote failure. Need help, is it possible im just screwed at this point. Ive used about everything it is just stuck saying Google. PLEASE HELP!!!!
Click to expand...
Click to collapse
Relax, deep breath. You need to use fastboot from bootloader. Issue these commands:
fastboot format cache
fastboot format userdata
That should get you into TWRP and from there you can transfer a ROM to internal, flash it and go from there.
Evolution_Freak said:
Relax, deep breath. You need to use fastboot from bootloader. Issue these commands:
fastboot format cache
fastboot format userdata
That should get you into TWRP and from there you can transfer a ROM to internal, flash it and go from there.
Click to expand...
Click to collapse
well, he wrote that he can boot into twrp recovery already. wiping data should fix his use of chainfires app. but flashing a new rom would do the same
simms22 said:
well, he wrote that he can boot into twrp recovery already. wiping data should fix his use of chainfires app. but flashing a new rom would do the same
Click to expand...
Click to collapse
Yeah, guess I missed that part.
Evolution_Freak said:
Yeah, guess I missed that part.
Click to expand...
Click to collapse
thinking about it now.. with the bootloader locked, would twrp let you flash anything?
simms22 said:
thinking about it now.. with the bootloader locked, would twrp let you flash anything?
Click to expand...
Click to collapse
Yes, it has been done to fix the soft brick I thought we were dealing with here. Only if TWRP is installed though.
Doesn't chainfire 3d modify system? I though it did. May need to flash a rom zip after a factory reset.
rootSU said:
Doesn't chainfire 3d modify system? I though it did. May need to flash a rom zip after a factory reset.
Click to expand...
Click to collapse
honestly, i dont remember. its been about 3-4 years since last thinking of that app. if it does, a rom flash would be needed.
Since pepole have no knolege of what they are doing and kind of blame me for it i will not provide the images anymore.
Please lock this thread.
Thank you so much!
Question: Do we have to flash the stock recovery after flashing the rooted system image? I prefer to have TWRP recovery anyways.
akarol said:
Thank you so much!
Question: Do we have to flash the stock recovery after flashing the rooted system image? I prefer to have TWRP recovery anyways.
Click to expand...
Click to collapse
worst case just reflash TWRP =]
akarol said:
Thank you so much!
Question: Do we have to flash the stock recovery after flashing the rooted system image? I prefer to have TWRP recovery anyways.
Click to expand...
Click to collapse
You can use whatever recovery you would like, the system image does not affect the recovery in any way.
Thanks - flashed your bootloader files which got me out of a never ending boot animation issue
j32olger said:
Thanks - flashed your bootloader files which got me out of a never ending boot animation issue
Click to expand...
Click to collapse
The bootloop have nothing to do with my bootloader files, they are completley stock from the ota file!
If you installing the new bootloader files on older roms you are asking for troubles.
Boot the watch in bootloader mode and flash the files as described and you watch will work.
Af if it bootlooping run a "Fastboot -w" after flashing.
Greetings, Is the newly released OTA compatible with your rom?
drmcatchr said:
Greetings, Is the newly released OTA compatible with your rom?
Click to expand...
Click to collapse
No ota files will only work with stock untouched rom.
bunny0007 said:
No ota files will only work with stock untouched rom.
Click to expand...
Click to collapse
Are you planning on releasing a pre-rootet image of the latest ota?
Would be greatly appreciated!
2k4ever said:
Are you planning on releasing a pre-rootet image of the latest ota?
Would be greatly appreciated!
Click to expand...
Click to collapse
Have added it today.
I tried this using the update (LCA44B) and now the watch doesn't even turn on. No LG logo or anything.
GuiyeC said:
I tried this using the update (LCA44B) and now the watch doesn't even turn on. No LG logo or anything.
Click to expand...
Click to collapse
And you did follow the instuctions?7
Flash bootloader stuff
Flash system image
Flash boot image
Have testet it serval times without errors.
bunny0007 said:
And you did follow the instuctions?7
Flash bootloader stuff
Flash system image
Flash boot image
Have testet it serval times without errors.
Click to expand...
Click to collapse
Yep, just like in the steps, the thing did show a FAILED (anti-rollback) when flashing the 'aboot'. I just used everything that was on the zip, now the watch doesn't even show the LG logo, I've tried plugging it on and off and keeping the reset button pressed for a while. I really don't know what else to try.
I'm waiting for it to run out of battery, but I don't even know if it's "on".
GuiyeC said:
Yep, just like in the steps, the thing did show a FAILED (anti-rollback) when flashing the 'aboot'. I just used everything that was on the zip, now the watch doesn't even show the LG logo, I've tried plugging it on and off and keeping the reset button pressed for a while. I really don't know what else to try.
I'm waiting for it to run out of battery, but I don't even know if it's "on".
Click to expand...
Click to collapse
Did just ran it on my own watch and everything working.
If you aboot fails flashing your watch might have another problem, i assume that your watch have an unlocked bootloader??
bunny0007 said:
Did just ran it on my own watch and everything working.
If you aboot fails flashing your watch might have another problem, i assume that your watch have an unlocked bootloader??
Click to expand...
Click to collapse
Yes, it had the boot loader unlocked, and I can't try again flashing the aboot because I can't get it to recovery mode or fast boot mode or anything.
Who can I get the images from?
bunny0007 said:
Since pepole have no knolege of what they are doing and kind of blame me for it i will not provide the images anymore.
Please lock this thread.
Click to expand...
Click to collapse
By people, do you mean 1 person ???
Pretty unfair for other, isn't it ?
I am looking for bootloader files for the G Watch R to flash over what I believe to be a corrupt bootloader on my device. It will only boot when on the charging stand, and so far I have only been able to get it to boot to 5.0.1 successfully. Once the device tries to pull down the OTA update it reboots and proceeds to run the update and then it fails and powers off.
Currently I can access fastboot and I can get it to boot a stock recovery and twrp with the 5.0.1 boot.img flashed to my device.
Can anyone who has downloaded the original package from this thread PM me the files? I need to reflash my bootloader files to attempt to fix a booting issue with my watch. Any help would be appreciated and I will not hold anyone accountable if I hard brick my device.
fnj00 said:
Can anyone who has downloaded the original package from this thread PM me the files? I need to reflash my bootloader files to attempt to fix a booting issue with my watch. Any help would be appreciated and I will not hold anyone accountable if I hard brick my device.
Click to expand...
Click to collapse
Hi there ,
Why don't you try this one ??
http://forum.xda-developers.com/g-w...edroid-r-urbane-port-v1-0-0-june-6th-t3128850
I somehow managed to soft brick my N6 using NRT to flash 6.0 factory image. At the time, N6 was stock no root. It will not boot past the Google boot screen. I have tried factory/data reset, clearing cache, and manually flashing fastboot files which fail at system.img during process...I l am also getting a "target reported max download of 5326722560 bytes" message prior to every file flash but it seems to complete. I currently can boot into bootloader and customer recovery....no OS loaded at the moment. Any assistance would be greatly appreciated...
Nexus 6 XT1103 64GB
nexus 6
dray said:
i somehow managed to soft brick my n6 using nrt to flash 6.0 factory image. At the time, n6 was stock no root. It will not boot past the google boot screen. I have tried factory/data reset, clearing cache, and manually flashing fastboot files which fail at system.img during process...i l am also getting a "target reported max download of 5326722560 bytes" message prior to every file flash but it seems to complete. I currently can boot into bootloader and customer recovery....no os loaded at the moment. Any assistance would be greatly appreciated...
Nexus 6 xt1103 64gb
Click to expand...
Click to collapse
i have the same problem . I tried nrt and cannot get the bootloader to unlock, only thing is i am rooted. No os loaded at the time either on teamwin.
dray said:
I somehow managed to soft brick my N6 using NRT to flash 6.0 factory image. At the time, N6 was stock no root. It will not boot past the Google boot screen. I have tried factory/data reset, clearing cache, and manually flashing fastboot files which fail at system.img during process...I l am also getting a "target reported max download of 5326722560 bytes" message prior to every file flash but it seems to complete. I currently can boot into bootloader and customer recovery....no OS loaded at the moment. Any assistance would be greatly appreciated...
Nexus 6 XT1103 64GB
Click to expand...
Click to collapse
Whats the system.img failure? Is it that it's too big? If so, your fastboot is out of date Update it to the latest.
drizzel57 said:
i have the same problem . I tried nrt and cannot get the bootloader to unlock, only thing is i am rooted. No os loaded at the time either on teamwin.
Click to expand...
Click to collapse
Nothing you can do. Send it for repair. There is no fix.
Ok I followed this tutorial to a tee and it worked like a champ:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
drizzel57 said:
i have the same problem . I tried nrt and cannot get the bootloader to unlock, only thing is i am rooted. No os loaded at the time either on teamwin.
Click to expand...
Click to collapse
My situation was a little different...I managed to unlock bootloader and load custom recovery before things went a little wonky
dray said:
Ok I followed this tutorial to a tee and it worked like a champ:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Click to expand...
Click to collapse
I nay have jut foudn the culperate, i flashed the ewer 7.1.1 onto my ohne afte factory resttubg then i rebooted anyeverthing was greatso i decided to go back int recovery and fkash thaoks for the 7.1.1 ans the enwest auperau 79, or whicher its at now
Valhalla875 said:
I nay have jut foudn the culperate, i flashed the ewer 7.1.1 onto my ohne afte factory resttubg then i rebooted anyeverthing was greatso i decided to go back int recovery and fkash thaoks for the 7.1.1 ans the enwest auperau 79, or whicher its at now
Click to expand...
Click to collapse
Wow dude... Now that was one hell of a hard to read post...
5.1 said:
Wow dude... Now that was one hell of a hard to read post...
Click to expand...
Click to collapse
You instantly made me laugh. I almost forgot about looking a solution for my problem