Related
So My nexus 6 decided not to turn on anymore after plugging into the charger last night. Pressing on the power button for hours it would only power on once and then stay stuck on this message across the screen "ap fastboot flash mode (secure)" in red. After about a minute it proceeded to the bootloader which looks like its been messed up, on the top right where you would see the options "recover", "restart", etc the word appears without any of the coloring behind it.. I've tried to boot to recovery (using TWARP) but it just restarts and goes right back to the same screen with the same message. If I attempt to shut off the phone it won't turn back on for another several hours of pressing the power button. I know it charges because I've seen the battery icon when off and it was full, I've also tried different outlets and chargers and tried those outlets and chargers on my Nexus 7 in which it works fine. I've also tried a wireless charger as well to completely rule out it being a charging issue.
I managed to get it back on again and decided to plug it into my PC. I was able to detect it with fastboot devices and then proceeded to completely restore to factory setting using the stock google images assuming the bootloader could be damaged. When I ran the command to flash the updated bootloader it failed. Then again the bootloader was on the screen in which it looked distorted
:~/Android/Nexus 6/shamu-lrx22c$ fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.122s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to flash partition
FAILED (remote failure)
finished. total time: 6.104s
~/Android/Nexus 6/shamu-lrx22c$ fastboot devices
ZX1G222NKR fastboot
~/Android/Nexus 6/shamu-lrx22c$ fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.123s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to flash partition
FAILED (remote failure)
finished. total time: 6.105s
:~/Android/Nexus 6/shamu-lrx22c$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
Click to expand...
Click to collapse
This is where I am at now. What I've noticed is that at one point I was able to boot directly into the bootloader using power and volume down and in that the bootloader seems normal. But as of now I am unable to do that.
My next step is to get the phone on again and try to manually boot into bootloader and attempt to flash again.
Any ideas or suggestions or questions?
I hope I'm not speaking out of my butt here... I do remember reading on here that you were actually able to boot the device using the boot image on the pc without actually flashing it. If I read that right, and if I remember correctly, it was fastboot boot.img instead of fastboot flash boot.img.
Hope this helps.
Larzzzz82 said:
I hope I'm not speaking out of my butt here... I do remember reading on here that you were actually able to boot the device using the boot image on the pc without actually flashing it. If I read that right, and if I remember correctly, it was fastboot boot.img instead of fastboot flash boot.img.
Hope this helps.
Click to expand...
Click to collapse
Sounds like something to try but my phone won't power on at all. So I can't even attempt this. I was thinking could the bootloader be damaged? would that cause the phone not to power on?
No clue.
stock or rooted..decrypted..
Fiftysilver said:
Sounds like something to try but my phone won't power on at all. So I can't even attempt this. I was thinking could the bootloader be damaged? would that cause the phone not to power on?
Click to expand...
Click to collapse
Whats the status of your phone before you got into this mess..Are you on stock or custom rom? Most phone doesnt go off like yours unless its an hardware issue.
as was mentioned you can try and boot recovery from RAM basically via the pc, but the device needs to be in fastboot mode first
the command would be fastboot boot recovery_image_name.img
That reboots device with the recovery loaded into RAM. I only tried it with TWRP but assume Stock would do the same....
Another thing to check maybe the fastboot executable as well, I had to update to latest SDK
paztine said:
Whats the status of your phone before you got into this mess..Are you on stock or custom rom? Most phone doesnt go off like yours unless its an hardware issue.
Click to expand...
Click to collapse
The only thing I did with my phone was root it on stock and unlock the bootloader. I was on 5.0.1.
paztine said:
Whats the status of your phone before you got into this mess..Are you on stock or custom rom? Most phone doesnt go off like yours unless its an hardware issue.
Click to expand...
Click to collapse
I'm going to go with it being a hardware issue because now it won't turn on at all anymore. But what I want to figure out is how did it come to that point. I'm thinking a power surge or a defect in the turbo charger. TBH I never trusted that Motorola turbo charger, something about pumping a lot of juice into my phone to charge it quicker screams potential short circuit.
But hopefully I can get the phone replaced via my warranty.. But my bootloader was unlocked so I don't know how well that would go.. But then again the phone can't turn on.
Hello, everyone.
So, about an week ago, I posted a thread to ask for your help regarding my broken N6. Since then, nothing has changed(but got worse, I guess...?). Here is what is happening with my N6 right now.
1) It powers up(thank god) but goes straight to the boot-loader screen(I believe this means that my device doesn't have system image file within the device)
2) On boot-loader menu(Start, Restart bootloader, Recovery mode, Power off, Factory, Barcodes, BP Tools, QCOM, Bootlaoder logs), only few are working(Restart bootlodaer, Power off, Barcodes). When I try to perform other than these, it just goes back to main boot-loader screen.
3) I tried to use both Nexus Root Tool kit and manual installation of each image but doesn't work for both of them(From this, I believe that my phone is just BROKEN)
With this happening, conclusion that I can think of is
1) There is no 'Recovery' available in my device(that's why I can't do anything to recover my device)
2) ADB is not functioning.
Only solution that I can think of from this point is that contact Motorola and replace my device(which is what I am currently doing but Motorola has huge problem with their customer service that I am waiting for their answer for about 2 weeks now)
If possible, would there other options that I can repair this device by myself?
I appreciate your attention.
Sincerely.
Adb has no impact on bootloader. What do you mean doesn't work when you fastboot the factory image?
Sent from my Nexus 6 using XDA Free mobile app
your problem is the use of toolkits. stay away from them, unless you know what you are doing!
your phone doesnt have any rom on it. you can.. 1. flash the factory img via fastboot, like you are supposed to do(not via a toolkit), or 2. unlock the bootloader, flash a custom recovery then while in the custom recovery adb push a rom, gapps, and supersu and flash them that way. what you did does not give you the right for a trade in.
The two previous posters are correct. You just need to fastboot flash the factory rom and factory recovery. It is fairly simple, if you take the time to read how to do it. There are posts all over XDA for beginners on how to do this. And I cannot stress how correct @simms22 is. Toolkits may seem to make things easy, but when there is a problem, you need to know how to manually fix it. I just personally stay away from toolkits. And I was in your shoes. I didn't know jack about flashing roms and such. Just reading XDA got me to where I am. (and i am still learning!)
Like the others have pointed out, you are fine. You have access to your bootloader screen, this is a Nexus. Take a deep breath. Take some time and read this site about flashing a factory image. Please do it the best way - manually with fastboot commands. If you get stuck come back here and someone will help. It really is easy. Please repeat after me "I will avoid all toolkits from now one".
Start with this and read lots.
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Flashing the factory image should still work from boot loader with fast boot.
Follow the second link for manual flashing after downloading the zip from the first link.
https://developers.google.com/android/nexus/images
If you run into the missing system.img problem here is the link to fix it:
http://www.androidpolice.com/2014/11/12/running-into-the-dreaded-missing-system-img-error-flashing-android-5-0-factory-images-heres-how-to-get-around-it/
This way you can start from the beginning.
Problem with flashing factory image manually.
First, thanks everyone for helping me by providing useful information but there is a problem when I flash factory image manually.
Whenever I try to flash image(for example, 'boot.img', or other images, I always get the same error 'FAILED <remote failure>' and not installed on my device. From here, I have no idea what to do.
chg911225 said:
First, thanks everyone for helping me by providing useful information but there is a problem when I flash factory image manually.
Whenever I try to flash image(for example, 'boot.img', or other images, I always get the same error 'FAILED <remote failure>' and not installed on my device. From here, I have no idea what to do.
Click to expand...
Click to collapse
first off, does fastboot see your device?? you can check by typing.. fastboot devices
if it doesnt see your device, do you have the driver instslled?
simms22 said:
first off, does fastboot see your device?? you can check by typing.. fastboot devices
if it doesnt see your device, do you have the driver instslled?
Click to expand...
Click to collapse
fastboot detects my device. but when I tried to TWRP recovery, it shows following error.
sending 'recovery' <11668 KB>...
OKAY [ 0.375s]
writing 'recovery'...
<bootloader> Failed to erase partition
<bootloader> Failed to flash partition recovery
FAILED <remote failure>
finished. total. time: 6.133s
chg911225 said:
fastboot detects my device. but when I tried to TWRP recovery, it shows following error.
sending 'recovery' <11668 KB>...
OKAY [ 0.375s]
writing 'recovery'...
<bootloader> Failed to erase partition
<bootloader> Failed to flash partition recovery
FAILED <remote failure>
finished. total. time: 6.133s
Click to expand...
Click to collapse
look for the command to erase the recovery partition. youll have to google it as i dont know(or remember) it. i dont even own a computer :angel:
then youll have to reflash the recovery.
simms22 said:
look for the command to erase the recovery partition. youll have to google it as i dont know(or remember) it. i dont even own a computer :angel:
then youll have to reflash the recovery.
Click to expand...
Click to collapse
found the command "fastboot erase recovery" but not working with following error message.
fastboot erase recovery
erasing 'recovery'
<bootloader> Erase allowed in unlocked state
<bootloader> Failed to erase partition
FAILED <remote failure>
finished. total time: 5.763s
*my phone is unlocked for sure(I checked 'fastboot oem unlock' and it said
fastboot oem unlock
...
<bootloader> Device already unlocked!
FAILED<remote failure>
finished. total time: 0.003s
chg911225 said:
found the command "fastboot erase recovery" but not working with following error message.
fastboot erase recovery
erasing 'recovery'
<bootloader> Erase allowed in unlocked state
<bootloader> Failed to erase partition
FAILED <remote failure>
finished. total time: 5.763s
*my phone is unlocked for sure(I checked 'fastboot oem unlock' and it said
fastboot oem unlock
...
<bootloader> Device already unlocked!
FAILED<remote failure>
finished. total time: 0.003s
Click to expand...
Click to collapse
i have no idea, but this is a good thread to read and post questions about fastboot in http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500
RIP. What did you do to your N6?
OP how did you install your fastboot. I would assume you did it from within a toolkit. That is probably your problem. If that is the case, please do this. Go here and install the .exe: http://developer.android.com/sdk/index.html#Other
It's big I know it but just do it please.
Make sure everything (SDK) gets installed in a folder path like c:\android or something you will easily remember. This is very important because it is within this folder you will place the extracted factory image files (.img). Place all full unzipped .img files in this folder.
Please follow method #2 in this excellent guide:
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
zetsumeikuro said:
RIP. What did you do to your N6?
Click to expand...
Click to collapse
One day it just shut down by itself and since then it's like this. I just contact Motorola and they are going to ship me new device with different color(idk y they are still having problem with their stocking their devices in because what I had was Cloud White 32Gb but only model that were present when I contact them was Midnight blue with 32Gb, other options are all out of stock. really wished they had a white color...)
This phone is a damn Nexus, it can't die. It's user error.
Sent from my Nexus 6
So, I was BROWSING REDDIT, and an app starts downloading in the background. Which somehow caused google play services to crash, along with everything running on my phone. Then bootloop. Completely unprompted. Still at a loss here.
My nexus 6 is unlocked, no custom kernel or xposed installed, just running AOSiP 3.3 android 6.0.1. havent flashed anything other than that, which i flashed more than a month ago.
So, my troubleshooting thus far.
./fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.002s
device still says UNLOCKED STATUS CODE 3
next i tried:
./fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (12004 KB)...
OKAY [ 0.378s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.382s
and lastly, I tried:
./fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (8196 KB)...
OKAY [ 0.259s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 0.264s
So, i'm kinda at a loss here. Recovery is failing to mount to storage, etc. Again, I was BROWSING REDDIT and this happened. I'd like to save my data at all costs. if anyone has any ideas, please, I am desperate. thank you.
Sorry but why open a new thread on the same issue? Did you think you would get a different answer than what you were getting in your original thread?
alryder said:
Sorry but why open a new thread on the same issue? Did you think you would get a different answer than what you were getting in your original thread?
Click to expand...
Click to collapse
to condense, summarize and make clear what i have already tried, and to seek further troubleshooting to my issue. there must be someone with an idea of how to fix this. if not, does it really hurt the forum? i am a person with a problem, seeking advice.
While I agree it's good to summarize the issue and layout what you've tried to resolve it, it could have been done as a post in your original thread to avoid the clutter of having two threads about the same issue. I also think you got the correct answer in the original thread that, however it happened, your bootloader has somehow became locked and in all likelihood the device is beyond repair. Sorry to say so but that's the way I see it.
alryder said:
While I agree it's good to summarize the issue and layout what you've tried to resolve it, it could have been done as a post in your original thread to avoid the clutter of having two threads about the same issue. I also think you got the correct answer in the original thread that, however it happened, your bootloader has somehow became locked and in all likelihood the device is beyond repair. Sorry to say so but that's the way I see it.
Click to expand...
Click to collapse
how is that even possible?
I'm super curious on what downloaded in the background...
Sent from my Nexus 6 using Tapatalk
MrBlob69 said:
I'm super curious on what downloaded in the background...
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
automatic update of some sort. it crashed my phone as soon as it was finished updating. didnt know a background app update could relock my bootloader and brick my phone. not sure why some are suggesting the bootloader is locked when it still displays status code 3 device is unlocked.
Post a screenshot of the bootloader screen
Sent from my Nexus 6 using XDA Free mobile app
The only thing that I can think of is you could try formatting /system and /boot separately and then try again flashing the system and boot images???
Sent from my Nexus 6 using Tapatalk
MrBlob69 said:
The only thing that I can think of is you could try formatting /system and /boot separately and then try again flashing the system and boot images???
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
This won't work as if the bootloader is locked, you cannot wipe/flash img files to the phone.
To answer your question OP, we can't tell you how this happened, or what the download was that happened in the background, we simply weren't there and don't know what you have installed to your phone. This line indicates that "Allow OEM Unlocking" is not enabled in Developer Options:
Code:
(bootloader) [B]Check 'Allow OEM Unlock' in Developer Options.[/B]
FAILED (remote failure)
finished. total time: 0.002s
With that not enabled, you cannot issue:
Code:
fastboot oem unlock
You also cannot flash factory images to the device, or wipe the device either. I'm afraid that this device is bricked since it appears your bootloader is locked.
scottshebs said:
So, I was BROWSING REDDIT, and an app starts downloading in the background. Which somehow caused google play services to crash, along with everything running on my phone. Then bootloop. Completely unprompted. Still at a loss here.
My nexus 6 is unlocked, no custom kernel or xposed installed, just running AOSiP 3.3 android 6.0.1. havent flashed anything other than that, which i flashed more than a month ago.
So, my troubleshooting thus far.
./fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.002s
device still says UNLOCKED STATUS CODE 3
next i tried:
./fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (12004 KB)...
OKAY [ 0.378s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.382s
and lastly, I tried:
./fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (8196 KB)...
OKAY [ 0.259s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 0.264s
So, i'm kinda at a loss here. Recovery is failing to mount to storage, etc. Again, I was BROWSING REDDIT and this happened. I'd like to save my data at all costs. if anyone has any ideas, please, I am desperate. thank you.
Click to expand...
Click to collapse
i guess all the time i devoted to you yesterday means absolutely nothing to you, and you learned nothing.. thanks
RMarkwald said:
This won't work as if the bootloader is locked, you cannot wipe/flash img files to the phone.
To answer your question OP, we can't tell you how this happened, or what the download was that happened in the background, we simply weren't there and don't know what you have installed to your phone. This line indicates that "Allow OEM Unlocking" is not enabled in Developer Options:
Code:
(bootloader) [B]Check 'Allow OEM Unlock' in Developer Options.[/B]
FAILED (remote failure)
finished. total time: 0.002s
With that not enabled, you cannot issue:
Code:
fastboot oem unlock
You also cannot flash factory images to the device, or wipe the device either. I'm afraid that this device is bricked since it appears your bootloader is locked.
Click to expand...
Click to collapse
forgive me, but how can the phones bootloader lock itself? this is the fastboot screen still saying code 3 unlocked. sorry if i am stubborn, just refusing to believe my 300 dollar device bricked itsself while i literally did nothing. never seen anything like this.
31ken31 said:
Post a screenshot of the bootloader screen
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
just posted, still status code 3.
Thread closed.
Not sure why the OP started 2 similar threads (like THIS) and ignored the help provided already....
Long time lurker first time poster, but I need help!!!
Getting tired of waiting for my OTA 7.11 and after a long night at work decided rather than just manually flashing the file that I would use the NRT. I must've encountered an error as it left me in Fastboot so I try to manually flash everything with it being stuck on the "Google" pre-boot screen. I try again with the version that I was on prior to update (NBD91X) and still the same results. Looking at the log from my Command Prompt I notice upon flashing the bootloader I have this error:
sending 'bootloader' (4071 KB)...
OKAY [ 0.219s]
writing 'bootloader'...
(bootloader) Motoboot: invalid GPT
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.408s
I am only able to boot into Fastboot and unable to boot into Recovery. What are my options to getting my N6 back?
Thank you all for the help.
Hi. Download last adb + fastboot executables here:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Extract the files somewhere.
Download Google factory image and extract it in the same folder you have the fastboot executable.
Boot in bootloader "power + volume down" and follow this guide:
https://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
I always choose the second option (manually flashing all files).
Good luck..!
5.1 said:
Hi. Download last adb + fastboot executables here:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Extract the files somewhere.
Download Google factory image and extract it in the same folder you have the fastboot executable.
Boot in bootloader "power + volume down" and follow this guide:
https://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
I always choose the second option (manually flashing all files).
Good luck..!
Click to expand...
Click to collapse
Thanks for your reply. Even after getting a fresh download of adb/fastboot files I'm still encountering this error when trying to flash the bootloader;
c:\Users\matt\Downloads\platform-tools>fastboot devices
ZX1G3249HB fastboot
c:\Users\matt\Downloads\platform-tools>fastboot flash bootloader C:\Users\matt\D
ownloads\platform-tools\shamu-n6f26r\bootloader-shamu-moto-apq8084-72.01.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (4071 KB)...
OKAY [ 0.134s]
writing 'bootloader'...
(bootloader) Motoboot: Preflash validation for aboot
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.433s
Any other suggestions?
bootloader is locked correct?
SynisterWolf said:
bootloader is locked correct?
Click to expand...
Click to collapse
The bootloader has been unlocked from the day I took it out of the box. I still have the little "unlocked" icon at the bottom of the "Google pre-boot" screen that it stays stuck at when I try to boot the phone.
Can you issue this command while in bootloader:
fastboot oem device-info
"Remote failure" sounds like as the bootloader is locked...
Also your problem sounds similar to this one:
https://forum.xda-developers.com/nexus-6/help/bricked-t3523844
I really don't know what you can do now sorry
5.1 said:
Can you issue this command while in bootloader:
fastboot oem device-info
"Remote failure" sounds like as the bootloader is locked...
Also your problem sounds similar to this one:
https://forum.xda-developers.com/nexus-6/help/bricked-t3523844
I really don't know what you can do now sorry
Click to expand...
Click to collapse
I just issued the command and got this back:
C:\Users\matt\Downloads\platform-tools>fastboot devices
ZX1G3249HB fastboot
C:\Users\matt\Downloads\platform-tools>fastboot oem device-info
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) 'device-info' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.011s
I hope I'm not screwed like the thread you suggested. At this point if I could just get a fresh install I'd be happy with that. Otherwise I guess I could start looking for an N6 replacement...I've put my sim card in my old MotoX 2013 and boy is this phone smaller than I remember.
AGGHHHHH!!! Thanks for your help and please let me know if there is anything else you could suggest for me to try.
Try: fastboot getvar all
Paste the result. Just hide you imei...
5.1 said:
Try: fastboot getvar all
Click to expand...
Click to collapse
I'm not sure, but wasn't it possible to unbrick the n6 by flashing the 7.0 developer preview image????
coremania said:
I'm not sure, but wasn't it possible to unbrick the n6 by flashing the 7.0 developer preview image????
Click to expand...
Click to collapse
That's interesting. I'd be game for whatever weird ass technique there is to get it up and running.
the200sx said:
That's interesting. I'd be game for whatever weird ass technique there is to get it up and running.
Click to expand...
Click to collapse
But I can't find a download of any early preview, maybe a member here has made backup. If you get a copy, try to flash it step by step without inserted simcard
Edit: may najoor has the original file for you
https://forum.xda-developers.com/nexus-6/general/android-n-preview-2-npc91k-flashable-t3358335
coremania said:
But I can't find a download of any early preview, maybe a member here has made backup. If you get a copy, try to flash it step by step without inserted simcard
Edit: may najoor has the original file for you
https://forum.xda-developers.com/nexus-6/general/android-n-preview-2-npc91k-flashable-t3358335
Click to expand...
Click to collapse
I just read through the entire thread, while it sounds like method 2 would most likely be the option considering how I can't get into recovery, I wasn't able to find where anyone talked about it unbricking the phone. At this point I'm ready to try just about anything, but I had hoped there would be a method to keep data. It may have to wait until tomorrow so I can dedicate enough time to it. In the meantime, if anyone can point me into the direction of someone being stuck similarly to me and what they did to get out of it, I would be extremely grateful.
Thanks
Hmm... Could you just try to flash twrp?
https://dl.twrp.me/shamu/twrp-3.0.3-0-shamu.img
Place the file in fastboot folder open a cmd, cd in fastboot folder and flash it:
fastboot flash recovery twrp-3.0.3-0-shamu.img
There's 0.01% it works but doesn't anything to try at this point...
5.1 said:
Hmm... Could you just try to flash twrp?
https://dl.twrp.me/shamu/twrp-3.0.3-0-shamu.img
Place the file in fastboot folder open a cmd, cd in fastboot folder and flash it:
fastboot flash recovery twrp-3.0.3-0-shamu.img
There's 0.01% it works but doesn't anything to try at this point...
Click to expand...
Click to collapse
I'll give it a shot
the200sx said:
I just read through the entire thread, while it sounds like method 2 would most likely be the option considering how I can't get into recovery, I wasn't able to find where anyone talked about it unbricking the phone. At this point I'm ready to try just about anything, but I had hoped there would be a method to keep data. It may have to wait until tomorrow so I can dedicate enough time to it. In the meantime, if anyone can point me into the direction of someone being stuck similarly to me and what they did to get out of it, I would be extremely grateful.
Thanks
Click to expand...
Click to collapse
Ok, I didn't remember this right, the developer preview ota sideloading with adb was for fixing the Google ota update which bricked some devices as the n previews were released.
But you have nothing to loose, so you may try to do this. Here's a working download in the link, if you don't sideloading the userdata your data may stay intact. https://www.reddit.com/r/nexus6/comments/49txh3/bricked_nexus_6_after_android_n_ota_update_stock/
5.1 said:
Hmm... Could you just try to flash twrp?
https://dl.twrp.me/shamu/twrp-3.0.3-0-shamu.img
Place the file in fastboot folder open a cmd, cd in fastboot folder and flash it:
fastboot flash recovery twrp-3.0.3-0-shamu.img
There's 0.01% it works but doesn't anything to try at this point...
Click to expand...
Click to collapse
It looks like it pushed the TWRP recovery but I still can't seem to get it to boot it into recovery. Only the main fastboot screen pops up trying to Power + Vol and when I VOL select it recovery, it will just reboot back to the main fastboot screen.
Damn... Try:
fastboot erase cache
And try to boot in twrp again?
5.1 said:
Damn... Try:
fastboot erase cache
And try to boot in twrp again?
Click to expand...
Click to collapse
That didn't work either. However it made it take a split-second longer to restart, which gave me a moment of hope. Hope Crushed!!!
Last question... When you power your phone, does it stay on Google logo, or boot animation forever? Or directly bootloader?
If one of the first two, is the phone detected on your computer device manager? If yes, how?
Hello guys.
So, I recently bought a new phone and thought "let's try rooting my old one" and tried it on my G7+. I ended up not liking out it turned out (Netflix DRM, Vanced didn't work properly, etc).
So I reflashed the stock ROM and put the comand fastboot oem lock.
The thing is, after I boot the device again, all the messages still appear, like Your device has loaded a different operating system" and below that "ID: " (blank) and I also get "Verity mode is set to disable".
The thing is, every tutorial I come across to relock the bootloader(regular G7, G7 Power, G6, etc), says that when you enter the command "fastboot oem lock" two times, the message that you should only flash signed images, does not appear. I instantly get the state flashing_locked, and I can't continue flashing the stock firmware like every other tutorial shows.
In short, once you enter the command "fastboot oem lock", it's locked for good, and you can't do anything unless you unlock it again, starting the whole process again.
The problem is, even with the bootloader locked again, my device still shows as "insecure", Netflix is nowhere to be found on the app store, and the state of my device is not certified.
I wouldn't have unlocked If I knew it was going to be this difficult to get it back. Selling it now would be next to impossible.
Here are some examples of the errors I'm getting:
C:\ProgramData\LMSA\Download\RomFiles\LAKE_QPWS30.61_21_18_7_subsidy_DEFAULT_regulatory_XT1965_2_SUTEL_DS_CFC.xml>fastboot oem lock
...
(bootloader) ***************************************
(bootloader) WARNING: This command erases user data!
(bootloader) Please re-run this command to confirm.
(bootloader) ***************************************
OKAY [ 0.022s]
finished. total time: 0.024s
C:\ProgramData\LMSA\Download\RomFiles\LAKE_QPWS30.61_21_18_7_subsidy_DEFAULT_regulatory_XT1965_2_SUTEL_DS_CFC.xml>fastboot oem lock
...
(bootloader) Bootloader is now locked
OKAY [ 0.045s]
finished. total time: 0.046s
C:\ProgramData\LMSA\Download\RomFiles\LAKE_QPWS30.61_21_18_7_subsidy_DEFAULT_regulatory_XT1965_2_SUTEL_DS_CFC.xml>fastboot oem lock
...
(bootloader) Already locked
OKAY [ 0.012s]
finished. total time: 0.014s
C:\ProgramData\LMSA\Download\RomFiles\LAKE_QPWS30.61_21_18_7_subsidy_DEFAULT_regulatory_XT1965_2_SUTEL_DS_CFC.xml>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (23537 KB)...
OKAY [ 0.618s]
writing 'boot_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.678s
Click to expand...
Click to collapse
Does anyone know how to fix this?
Did you ever get this sorted ? I have the same problem on my G7 Plus. I unlocked, then loaded Lineagos, but then decided to go back to stock, I used LMSA to rescue the phone, but still got the warning and boot time "Your phone has loaded a different OS" and I can't use GPay. I tried the fastboot OEM lock (worked) and fastboot flashing lock, but I still get the warning and I can't use GPay.
I think in my case the LMSA rescue didn't work because I was originally on Android 9 and the rescue took me straing to Android 10
Elrom said:
Hello guys.
So, I recently bought a new phone and thought "let's try rooting my old one" and tried it on my G7+. I ended up not liking out it turned out (Netflix DRM, Vanced didn't work properly, etc).
So I reflashed the stock ROM and put the comand fastboot oem lock.
The thing is, after I boot the device again, all the messages still appear, like Your device has loaded a different operating system" and below that "ID: " (blank) and I also get "Verity mode is set to disable".
The thing is, every tutorial I come across to relock the bootloader(regular G7, G7 Power, G6, etc), says that when you enter the command "fastboot oem lock" two times, the message that you should only flash signed images, does not appear. I instantly get the state flashing_locked, and I can't continue flashing the stock firmware like every other tutorial shows.
In short, once you enter the command "fastboot oem lock", it's locked for good, and you can't do anything unless you unlock it again, starting the whole process again.
The problem is, even with the bootloader locked again, my device still shows as "insecure", Netflix is nowhere to be found on the app store, and the state of my device is not certified.
I wouldn't have unlocked If I knew it was going to be this difficult to get it back. Selling it now would be next to impossible.
Here are some examples of the errors I'm getting:
Does anyone know how to fix this?
Click to expand...
Click to collapse
You can try downloading each versions from your region (RETUS, RETEU, etc) and retry the relock process until you find the correction version.
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com