Database Users

Need help with WiFi Xoom partial brick

Basically last year I was unlocked and rooted...I went back stock when ICS first dropped and havent been rooted since. However, I can't relock my device. I was trying to watch a movie i rented from the Play Store and kept getting "error fetching licence". So I assumed that even though I was able to get my OTA official from Google for Jellybean direct from Google while Unlocked that the cause was DRM and i needed to relock my device. I did just that (locked Xoom) and now I am stuck at Motorola symbol. I get that red linux error..Well i used to until I tried the FIRST Root My Xoom.
I have been in ADB all day and last-night and can not get it do anything other than lock and unlock over and over again and neither does anything. So I decided to say screw it if it's easier just to root and flash a custom ROM because I NEED my tablet ASAP.
I tried EASY ADB and I can control the reboots and put it in fastboot and all that. I get an error when attepting to flash recovery through ADB "error: cannot load 'recovery-Tiamat-R4c-10061-1150-cwm.img" : No Error
I guess it can't read the SD because no ROM is there. I suppose the OTA is just an update to the last version and not the full ROM maybe so when I locked it that caused it to wipe and there's nothing there to restore from and that caused my loop.
Now what I need from you guys is a possible ONE CLICK option. Tried searching the forum and one guys lAIOS thingy I can't figure out for anything. The other one click was deleted by the OP..I really need help and I appreciate anyone that can point me because the last 14hrs of ADB is driving me insane.
THANK YOU IN ADVANCE!!!!!!!!!!!
UPDATE
I was able to get em all set. Up and running 4.2 now. I guess a MOD can delete this or close it now.

Flash Stock image
Your best bet is to flash back to a stock image (which will basically be Honeycomb). Download the correct img from your model and use the instructions from this site:
rootzwiki.com/topic/1586-stock-images
On your computer running ADB use the following commands
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot erase userdata (if no img in zip)
(Warning: If you have an external SD card, remove it. This will save you a lot of headache. I found that Stock Honeycomb would not update with a external SD card inside). Once you get Honeycomb successfully on, you can use OTA to update til you get to Jellybean (if you have the Wifi Model, or ICS if you have a 4G model).
Good Luck
Freshly_Snipes said:
Basically last year I was unlocked and rooted...I went back stock when ICS first dropped and havent been rooted since. However, I can't relock my device. I was trying to watch a movie i rented from the Play Store and kept getting "error fetching licence". So I assumed that even though I was able to get my OTA official from Google for Jellybean direct from Google while Unlocked that the cause was DRM and i needed to relock my device. I did just that (locked Xoom) and now I am stuck at Motorola symbol. I get that red linux error..Well i used to until I tried the FIRST Root My Xoom.
I have been in ADB all day and last-night and can not get it do anything other than lock and unlock over and over again and neither does anything. So I decided to say screw it if it's easier just to root and flash a custom ROM because I NEED my tablet ASAP.
I tried EASY ADB and I can control the reboots and put it in fastboot and all that. I get an error when attepting to flash recovery through ADB "error: cannot load 'recovery-Tiamat-R4c-10061-1150-cwm.img" : No Error
I guess it can't read the SD because no ROM is there. I suppose the OTA is just an update to the last version and not the full ROM maybe so when I locked it that caused it to wipe and there's nothing there to restore from and that caused my loop.
Now what I need from you guys is a possible ONE CLICK option. Tried searching the forum and one guys lAIOS thingy I can't figure out for anything. The other one click was deleted by the OP..I really need help and I appreciate anyone that can point me because the last 14hrs of ADB is driving me insane.
THANK YOU IN ADVANCE!!!!!!!!!!!
UPDATE
I was able to get em all set. Up and running 4.2 now. I guess a MOD can delete this or close it now.
Click to expand...
Click to collapse
---------- Post added at 04:38 PM ---------- Previous post was at 04:18 PM ----------
Wanted to add, there are 2 methods of flashing imgs to you your machine.
You can flash from the tablet using recovery, or you can flash from a another machine running the Android development kit. My post uses the second method, so it should not matter which recovery image is on your machine.

johnsry said:
Your best bet is to flash back to a stock image (which will basically be Honeycomb). Download the correct img from your model and use the instructions from this site:
rootzwiki.com/topic/1586-stock-images
On your computer running ADB use the following commands
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot erase userdata (if no img in zip)
(Warning: If you have an external SD card, remove it. This will save you a lot of headache. I found that Stock Honeycomb would not update with a external SD card inside). Once you get Honeycomb successfully on, you can use OTA to update til you get to Jellybean (if you have the Wifi Model, or ICS if you have a 4G model).
Good Luck
---------- Post added at 04:38 PM ---------- Previous post was at 04:18 PM ----------
Wanted to add, there are 2 methods of flashing imgs to you your machine.
You can flash from the tablet using recovery, or you can flash from a another machine running the Android development kit. My post uses the second method, so it should not matter which recovery image is on your machine.
Click to expand...
Click to collapse
You must have missed the update at the bottom of the post. I got it to go now. Thank you though so much for offering help.
Sent from my Nexus 4 using Tapatalk 2

Stuck In BootLoop While updating lollipop

i used nexus root tool kit to update nexus 4 from 4.4 to 5.0... all done in pc but mobile is stuck in boot loop. can anyone tell me how can i restore my phone to normal working...
Please help me i am noob here

is there any one who can help me here
i thought i will get ans with in 1hr... still waiting if someone can help

letsnexus said:
i thought i will get ans with in 1hr... still waiting if someone can help
Click to expand...
Click to collapse
This is why we don't recommended using tool kits. You should try flashing the factory image using fastboot.
Sent from my Nexus 9 using XDA Free mobile app

Same here, i tried re-flashing many times. Darn that nexus root toolkit

any suggetion or link which can help me to use fastboot use and install stock rom
thank alot for help

I am currently in the same position ! Used a toolkit too, always have.

This is why you never use a Toolkit, it's always been mentioned around in XDA that this has always been a developer website of learning and knowledge. You must always know what goes on behind than just blindly flashing things. It's a rule of thumb that you're more likely to brick your phone with a Toolkit than by yourself. Easiest step as follows.
1. Download factory image
2. Download ADB files
3. Make a folder and extract the adb files and factory image inside the same folder.
4. Plug the phone in bootloader mode or simply type adb reboot bootloader (Developer options must be enabled and USB Debugging) by exiting the folder, holding shift, right clicking the folder and pressing open command window and typing the command.
5. Every factory image comes with a flashall.bat, double click it and voila. Updates like it should. (User data will be wiped)
If you don't want your userdata to be wiped, simply open flashall.bat with notepad++, erase the '-w' in "fastboot -w update image" and save the file and launch it again.
Sent from my HTC One_M8 using Tapatalk

I will try that way later when I get in, I would have assumed that the toolkit did exactly those steps though, just an easy to use frontend

hazwheel said:
I will try that way later when I get in, I would have assumed that the toolkit did exactly those steps though, just an easy to use frontend
Click to expand...
Click to collapse
Go to stock recovery and do factory data reset and reboot phone. First time boot takes very long time (around 10 to 15 minutes). After successfully boot into android L check for the storage space. If it says only 5 GB available instead of 12 GB (My nexus is 16GB) then Go to Settings > Backup & Reset and select Factory data reset.
I had experienced these issues when upgrading to Lollypop and solved them on my own.
Note: If you were not able to boot into stock recovery, try twrp recovery. you have to install it using fastboot
fastboot flash recovery <filename.img>

letsnexus said:
any suggetion or link which can help me to use fastboot use and install stock rom
thank alot for help
Click to expand...
Click to collapse
although the link is for kitkat but the same method applies to flashing lollipop
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312

moorthidaniel said:
Go to stock recovery and do factory data reset and reboot phone. First time boot takes very long time (around 10 to 15 minutes). After successfully boot into android L check for the storage space. If it says only 5 GB available instead of 12 GB (My nexus is 16GB) then Go to Settings > Backup & Reset and select Factory data reset.
I had experienced these issues when upgrading to Lollypop and solved them on my own.
Note: If you were not able to boot into stock recovery, try twrp recovery. you have to install it using fastboot
fastboot flash recovery <filename.img>
Click to expand...
Click to collapse
OK, I was able to get into recovery with this method, and wipe but I get can't mount cache errors during the wipe , waiting for the phone to reboot now, hopefully it will and get out of the bootloop. stupid thing is I'm not a noob, but stumped by this. Good excuse to upgrade to the N5 I guess
---------- Post added at 03:14 PM ---------- Previous post was at 02:55 PM ----------
Wow, this method worked! Brilliant! Thanks, and dammit, it worked, 10 minutes after she agreed to me getting am upgrade !

For all of you whom are stuck in bootloop a fastboot oem lock comand when in fastboot will solve the problem.
So go into bootloader and run "fastboot oem lock" for some reason on some devices Android 5.0 won't boot with unlocked bootloader.

hazwheel said:
OK, I was able to get into recovery with this method, and wipe but I get can't mount cache errors during the wipe , waiting for the phone to reboot now, hopefully it will and get out of the bootloop. stupid thing is I'm not a noob, but stumped by this. Good excuse to upgrade to the N5 I guess
---------- Post added at 03:14 PM ---------- Previous post was at 02:55 PM ----------
Wow, this method worked! Brilliant! Thanks, and dammit, it worked, 10 minutes after she agreed to me getting am upgrade !
Click to expand...
Click to collapse
OK great. Cheers, I helped someone today in this forum.

bett3rthan said:
For all of you whom are stuck in bootloop a fastboot oem lock comand when in fastboot will solve the problem.
So go into bootloader and run "fastboot oem lock" for some reason on some devices Android 5.0 won't boot with unlocked bootloader.
Click to expand...
Click to collapse
That did NOT work for me, the getting into recovery and wiping the device DID work though.
---------- Post added at 04:05 PM ---------- Previous post was at 04:03 PM ----------
moorthidaniel said:
OK great. Cheers, I helped someone today in this forum.
Click to expand...
Click to collapse
Yes, Thanks, unfortunately, she has withdrawn the offer of an early upgrade :silly:

thax
Misledz said:
This is why you never use a Toolkit, it's always been mentioned around in XDA that this has always been a developer website of learning and knowledge. You must always know what goes on behind than just blindly flashing things. It's a rule of thumb that you're more likely to brick your phone with a Toolkit than by yourself. Easiest step as follow
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Thank you alot, you help in really good manner
and teached us not to use toolkit
will learn more abt rooting and flashing thank you once again

I am hitting this problem now, I got a OTA. After restarting its keep on looping waiting for more than 20mins still it's looping.

Tried going to boot-menu and did factory reset and it booted good after ~10 mins.

sububack said:
I am hitting this problem now, I got a OTA. After restarting its keep on looping waiting for more than 20mins still it's looping.
Click to expand...
Click to collapse
Power off, hold Vol Down + Power, when you get to the Android laying down, press volume up + pwr, then wipe the /cache from the menu (you do not need to do a full factory wipe, just wiping cache will do), and then reboot and wait. It will boot this time properly. @WugFresh is aware of the issue and said will put a fix in 1.9.9 for the N4

Thanks , I have tried clearing the cache and started waiting for an hour. Since it was still looping tried after factory reset/wiping user data. And then after 10min it came good.

I post this on Google Product Forum 2 days ago. Hope it helps
https://productforums.google.com/fo...ce=footer#!msg/nexus/Lv8fHtyJOPQ/wDzRUm4b2UsJ
(updated 29/11/2014)[not perfect but it is a SOLUTION]
The idea of this is to downgrade your nexus 4 without wiping your data, which means stuff you will need includes:
1. adb and fastboot on your computer (I am using mac but you can find it on windows as well. There are tones of website and forums telling you the latest method of getting it onto your computer)
2. factory image of nexus 4(I use 4.4.4, since that's what it was. I don't have the time and energy to try to do the same thing with lollipop. you can try can leave a comment).
update: do NOT try to flash 5.0 rom using this method. You will be stuck at boot loop again
3. usb cable
4. nexus 4 with unlocked bootloader(the process of unlocking bootloader will wipe your device)
5. computer
steps
1. unzip the factory image (something.tgz)
2. for me, after unzipping the .tgz, I still find another .zip inside. unzip that too.
3. hold vol+, vol-, and power button simultaneously to enter fastboot mode
4. open terminal(mac)(it would probably be cmd for windows)
5. connect your nexus 4(in fastboot)
6. to make sure it connect successfully, type "fastboot devices". if something like "005040c0d54bb291 fastboot" appears, you are good. Otherwise, try reconnect your device/boot to fastboot again/use another usb cable
7.now we need to tell the terminal to navigate to the location of the unzipped factory image. to do that, i suggest you put the unzipped folder to somewhere easy to find, like desktop. these are some commands to help you navigate:
"ls" allows you to look at whats inside the current directory of the terminal. For example, this is the output after typing "ls" for me:
some folder Photos
nexus4image.tgz how many folders do you have
5.zip occam-ktu84p
more folder occam-ktu84p.zip
after knowing where you are, use "cd" (below) to go to your folder
"cd" means change directory. For example. "cd Photos" will brings me to the "Photos" folder. And then if I type ls, I will see a whole bunch of photos in my photos. If you go to the wrong folder, type "cd ..", and it will bring you back to the previous folder.
8. flash bootloader.
enter the following command, BUT REMEMBER TO CHANGE THE NAME TO FIT YOURS(DIFFERENT VERSIONS HAVE SLIGHTLY DIFFERENT FILE NAME AT THE END(type ls first to help you type the correct name)
fastboot flash bootloader bootloader-mako-makoz30d.img
9. reboot bootloader. just copy and paste
fastboot reboot-bootloader
10. flash radio
enter the following command, BUT REMEMBER TO CHANGE THE NAME TO FIT YOURS(DIFFERENT VERSIONS HAVE SLIGHTLY DIFFERENT FILE NAME AT THE END(type ls first to help you type the correct name)
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.03.img
11. reboot bootloader. just copy and paste
fastboot reboot-bootloader
12. flash system
system.img is located inside the zip, use ls to help you navigate. This steps takes the longest time, total time on this step is 87 seconds while the others are less then 1 second
fastboot flash system system.img
13. flash boot
boot.img is located inside the zip, use ls to help you navigate.
fastboot flash boot boot.img
14. flash recovery
fastboot.img is located inside the zip, use ls to help you navigate.
fastboot flash recovery recovery.img
15. format cache(not the memory, so everything should be fine)
fastboot format cache
16. reboot and wait
this will reboot your device. You probably have to wait for a while to initialise all the apps. after than you are good to go!
fastboot reboot
credit: my friend for giving me this idea + http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312 + HelpMyNexus

Your device is corrupt. It can't be trusted and may not work properly. help!

Long story short, hopped over to android following years and years of using IOS.
Bought a nexus 6p, learnt about root, gained root access to the 6p, and began installed root apps.
This morning, i installed Gsam battery monitor root companion, found out it broke the normal Gsam battery monitor app, tried to uninstall the gsam root companion several times. Everytime i uninstalled it and rebooted, it would just reappear on the phone and wouldn't actually uninstall properly at all.
On the third go, it rebooted into the red triangle " Your device is corrupt. It can't be trusted and may not work properly." and is stuck on the google logo.
Accessed recovery and tried to restore the nandroid backup, no luck, still boots up to red triangle and is stuck on google logo.
Accessed recovery and tried to restore to factory default, no luck, still boots up to red triangle and is stuck on google logo.
How do i fix my phone now? Any help would be greatly appreciated.

red triangle with the android mascot logo?
if so, put it into fastboot and reinstall recovery and see if that worked

gd6noob said:
red triangle with the android mascot logo?
if so, put it into fastboot and reinstall recovery and see if that worked
Click to expand...
Click to collapse
Its just a red triangle with an exclamation mark inside.
I can't post an image because i am a new member and need at least 10 posts.

https://support.google.com/nexus/answer/6185381?hl=en - It says it should dismiss by itself.

chichu_9 said:
- It says it should dismiss by itself.
Click to expand...
Click to collapse
The red logo does disappear and the device transitions to the black and white google boot logo.
It is here where the device becomes hung, i assume it is because the boot.img or boot files have been damaged, but i'm just guessing. What i am confused about is if the boot files are damaged, the nandroid restore should fix this problem (shouldn't it?), but it doesn't.

radaga5t said:
Long story short, hopped over to android following years and years of using IOS.
Bought a nexus 6p, learnt about root, gained root access to the 6p, and began installed root apps.
This morning, i installed Gsam battery monitor root companion, found out it broke the normal Gsam battery monitor app, tried to uninstall the gsam root companion several times. Everytime i uninstalled it and rebooted, it would just reappear on the phone and wouldn't actually uninstall properly at all.
On the third go, it rebooted into the red triangle " Your device is corrupt. It can't be trusted and may not work properly." and is stuck on the google logo.
Accessed recovery and tried to restore the nandroid backup, no luck, still boots up to red triangle and is stuck on google logo.
Accessed recovery and tried to restore to factory default, no luck, still boots up to red triangle and is stuck on google logo.
How do i fix my phone now? Any help would be greatly appreciated.
Click to expand...
Click to collapse
After a root went bad I had the same thing happen. I just used SkipSoft ToolKit and restored back to a stock image (MDB08L).
The corruption message disappeared.

Take a look at this guide By Heisenberg as it will help with some details.
The few times I flashed/reset the phone, I accidentally muddled up some steps. Specifically the flashing the boot and bootloader images.
Code:
[U]fastboot flash bootloader X:/bootloader.img[/U]
fastboot reboot bootloader
fastboot flash radio X:/radio.img
fastboot reboot bootloader
[U]fastboot flash boot X:/boot.img[/U]
fastboot erase cache
fastboot flash cache X:/cache.img
fastboot flash recovery X:/recovery.img
fastboot flash system X:/system.img
fastboot flash vendor X:/vendor.img
I would accidentally flash the bootloader.img image over the boot.img and cause the error, specifically the one you mentioned. I had to go through the flashing process VERY carefully again, and when flashing .imgs for root acess over to the stock ones.
I know is sounds trivial and I'm not saying you don't understand it, but give it a try and see if this resolves the issue. double check your lines and triple check your images (make sure there are NO spaces in the bootloader/boot img file directories. or_replace_spaces_with_underscores). I don't know how many times I have screwed up and it was because of a dash in the wrong spot or space in the .img directory. Let us know how you go.

Awesome!
Thank you very much everyone. I will try once i get home from work.
You have all been so helpful. Such a good community.

I hoped it worked out for you

urbanpitch said:
I hoped it worked out for you
Click to expand...
Click to collapse
Yep i was able to restore the phone via the heisenberg guide. Thanks!

radaga5t said:
Yep i was able to restore the phone via the heisenberg guide. Thanks!
Click to expand...
Click to collapse
Was just about to post a link to my guide but it looks as though you already got everything sorted out. I'm glad my little guide was able to assist you.

Heisenberg said:
Was just about to post a link to my guide but it looks as though you already got everything sorted out. I'm glad my little guide was able to assist you.
Click to expand...
Click to collapse
I'm having the very same issue and I don't understand what I'm supposed to do. Exact same issue a OP. I use the Mskip toolkit to the letter and that got me a bootloop. I have TWRP installed and I can access it. How can I recover my phone? Thanks in advance
---------- Post added at 11:24 PM ---------- Previous post was at 11:17 PM ----------
radaga5t said:
Awesome!
Thank you very much everyone. I will try once i get home from work.
You have all been so helpful. Such a good community.
Click to expand...
Click to collapse
Hey man, could you tell me the exact steps you took to fix yours? I'm having the same exact issue after having use that toolkit.

barondebxl said:
I'm having the very same issue and I don't understand what I'm supposed to do. Exact same issue a OP. I use the Mskip toolkit to the letter and that got me a bootloop. I have TWRP installed and I can access it. How can I recover my phone? Thanks in advance
Click to expand...
Click to collapse
Just go to my guide and follow the instructions in section 9. You'll need to look at the prerequisites section at the beginning of the OP first so you can install the latest version of adb/fastboot via the SDK.

Heisenberg said:
Just go to my guide and follow the instructions in section 9. You'll need to look at the prerequisites section at the beginning of the OP first so you can install the latest version of adb/fastboot via the SDK.
Click to expand...
Click to collapse
Cool ill give it a shot. Thank you. I'm all out of thanks for today
---------- Post added at 11:53 PM ---------- Previous post was at 11:35 PM ----------
Heisenberg said:
Just go to my guide and follow the instructions in section 9. You'll need to look at the prerequisites section at the beginning of the OP first so you can install the latest version of adb/fastboot via the SDK.
Click to expand...
Click to collapse
Im sorry but I'm completely lost. I have downloaded the factory images of my build, I have extracted the files but there isn't any bootloader.img and radio.img. When I click the extracted file it asks me if I want to download a windows application to open it.

barondebxl said:
Cool ill give it a shot. Thank you. I'm all out of thanks for today
---------- Post added at 11:53 PM ---------- Previous post was at 11:35 PM ----------
Im sorry but I'm completely lost. I have downloaded the factory images of my build, I have extracted the files but there isn't any bootloader.img and radio.img. When I click the extracted file it asks me if I want to download a windows application to open it.
Click to expand...
Click to collapse
You'll need to find a program that can extract the "tar.gz" compression format.

Heisenberg said:
You'll need to find a program that can extract the "tar.gz" compression format.
Click to expand...
Click to collapse
Ok thank you. 7zip works

barondebxl said:
I'm having the very same issue and I don't understand what I'm supposed to do. Exact same issue a OP. I use the Mskip toolkit to the letter and that got me a bootloop. I have TWRP installed and I can access it. How can I recover my phone? Thanks in advance
---------- Post added at 11:24 PM ---------- Previous post was at 11:17 PM ----------
Hey man, could you tell me the exact steps you took to fix yours? I'm having the same exact issue after having use that toolkit.
Click to expand...
Click to collapse
Basically i followed step 9 of Heisenberg's guide.
Code:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
So i flashed all of the above minus the user data and re-locking the bootloader.
Let me know if you need any more info.

radaga5t said:
Basically i followed step 9 of Heisenberg's guide.
Code:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
So i flashed all of the above minus the user data and re-locking the bootloader.
Let me know if you need any more info.
Click to expand...
Click to collapse
Thanks bud. I'm lost still. I have all the files needed in a folder I called " images" on my desktop. Do I have to write these commands you posted word for word? I mean I know I have to replace with my file name but for example I have the MDB08L so do I do : fastboot flash bootloader C:\angler\images\bootloader-angler-angler-02.01.img ( in my case) even though the folder is on my desktop?
Edit: I tried and it gave me an error saying it cant load it. So frustrating

barondebxl said:
Thanks bud. I'm lost still. I have all the files needed in a folder I called " images" on my desktop. Do I have to write these commands you posted word for word? I mean I know I have to replace with my file name but for example I have the MDB08L so do I do : fastboot flash bootloader C:\angler\images\bootloader-angler-angler-02.01.img ( in my case) even though the folder is on my desktop?
Edit: I tried and it gave me an error saying it cant load it. So frustrating
Click to expand...
Click to collapse
You got an error because you're pointing fastboot to a location where the file doesn't exist. If you had followed my guide and placed the files in C:\angler\images\ then the command would be correct, but you've placed the files in a different location, therefore you need to type the commands so that they include the path to where the files are actually located on your PC.
There's an easy way to do it, type the first portion of the command, for example "fastboot flash bootloader " (make sure there's a space after the last character), then you can grab the appropriate file with your mouse and drag/drop it into the command terminal window and the file path will be completed automatically for you, then just hit enter to execute the command.

Heisenberg said:
You got an error because you're pointing fastboot to a location where the file doesn't exist. If you had followed my guide and placed the files in C:\angler\images\ then the command would be correct, but you've placed the files in a different location.
You need to type the commands so that they include the path to where the files are actually located on your PC. There's an easy way to do it, type the first portion of the command, for example "fastboot flash bootloader " (make sure there's a space after the last character), then you can grab the appropriate file with your mouse and drag/drop it into the command terminal window and the file path will be completed automatically for you, then just hit enter to execute the command.
Click to expand...
Click to collapse
Thanks guys I finally figured it out. I'm at flashing the system and its taking a while obviously. Its actually easy...when you know what youre doing. Thank you so very much to the both of you!
Edit: back up and running! I was just frustrated cause I just got the phone this afternoon that's why. You guys are awesome
---------- Post added at 01:48 AM ---------- Previous post was at 01:36 AM ----------
barondebxl said:
Thanks guys I finally figured it out. I'm at flashing the system and its taking a while obviously. Its actually easy...when you know what youre doing. Thank you so very much to the both of you!
Edit: back up and running! I was just frustrated cause I just got the phone this afternoon that's why. You guys are awesome
Click to expand...
Click to collapse
One last question, whats the best method to root MDB08L? I want that chroma rom

No OS Installed While Flashing Android N OTA In TWRP

So yeah I accidentally wiped my partitions as if I were installing a rom. Am I screwed until I get to a pc?
P.s. Out of all days to delete my backup rom file ?

Just set it to boot loader mode and flash stock images...I'm sure there's a tutorial on how to do it..I have the program installed on my computer ready for any time I brick my phone lol but I don't remember the name of the program right now
Edit: heres the link to the method I use http://forum.xda-developers.com/showthread.php?t=3258493

I'm assuming the OP doesn't have a PC due to the last statement he made. I would say yes, nothing you can do until you can get to a PC and flash stock images via Fastboot. Unless you have a ROM zip on your phone that is....which I'm assuming you don't.

You're kinda stuck, you need a PC to flash the factory images. TWRP can't flash OTA's anyway, so don't try that again either. I'd strongly recommend not using a toolkit to flash the factory images too. I have a detailed guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

Hey guys, having a similar issue than zachbuilds. While rooting my nexus 6p on NRD9M, I formatted to system partition for root to stick and noticed twrp stated I have no OS installed. At that point I was going to flash stock image file when my nexus reverted from default MTP to charge only and now my Mac is unable to recognize my device Ann's now adb is non operable. I tried to fastboot adb commands but that isn't working either. Any one have any suggestions. I'm on stock with twrp custom recovery, no other changes were made to my device. Also, recovery and bootloader are accessible. Thanks for any help given.

Snakielols1984 said:
Hey guys, having a similar issue than zachbuilds. While rooting my nexus 6p on NRD9M, I formatted to system partition for root to stick and noticed twrp stated I have no OS installed. At that point I was going to flash stock image file when my nexus reverted from default MTP to charge only and now my Mac is unable to recognize my device Ann's now adb is non operable. I tried to fastboot adb commands but that isn't working either. Any one have any suggestions. I'm on stock with twrp custom recovery, no other changes were made to my device. Also, recovery and bootloader are accessible. Thanks for any help given.
Click to expand...
Click to collapse
Can fastboot see your device when you're in bootloader?

Yes fastboot is able to reconize my device.

Snakielols1984 said:
Yes fastboot is able to reconize my device.
Click to expand...
Click to collapse
Best just to flash back to factory images. Be cautious if you've flashed the Android N OTA though, there are some strange things going on with people trying to flash back to M. Read up before you flash.

I've actually tried flashing stock images but every time I tried to run fastboot command I get these errors, "command not found" and I believe the other erro is "file path not found". There's another error that I can't remember off the top of my head what it. When I get home I'll try to run the commands again and see what errors I get
---------- Post added at 11:09 PM ---------- Previous post was at 11:08 PM ----------
elfrosto said:
Best just to flash back to factory images. Be cautious if you've flashed the Android N OTA though, there are some strange things going on with people trying to flash back to M. Read up before you flash.
Click to expand...
Click to collapse
on another note I have not flashed Android N OTA. I downloaded that and install via OTA.

wrong thread

so just attempted to flash stock images and I get an error "cannot load bootloader-angler-angler-03.54.img". the tutorial I am using is Heisenberg's How-To Guide For Beginners. I followed the instructions step by step. Please is anyone can chime in, please do. Greatly appreciated!

Snakielols1984 said:
so just attempted to flash stock images and I get an error "cannot load bootloader-angler-angler-03.54.img". the tutorial I am using is Heisenberg's How-To Guide For Beginners. I followed the instructions step by step. Please is anyone can chime in, please do. Greatly appreciated!
Click to expand...
Click to collapse
What bootloader version are you on currently? Although updated bootloader is recommend, you should be able to skip this step without any issues.

Sorry for late response but currently I am bootloader: angler-3.58
---------- Post added at 12:27 AM ---------- Previous post was at 12:19 AM ----------
This is the error I get when using fastboot commands to flash stock images "error: cannot load 'MacintoshHD/angler/images/radio-angler-angler-03.61.img'". I received same error when trying to flash bootloader

Snakielols1984 said:
Sorry for late response but currently I am bootloader: angler-3.58
---------- Post added at 12:27 AM ---------- Previous post was at 12:19 AM ----------
This is the error I get when using fastboot commands to flash stock images "error: cannot load 'MacintoshHD/angler/images/radio-angler-angler-03.61.img'". I received same error when trying to flash bootloader
Click to expand...
Click to collapse
Please post the entire command you are using, as written in your terminal prompt. "No command" sounds like an unrecognized command is being issued. We must use ./ in addition to the fastboot or adb command in order for OSX to execute the action. If following Heisenberg's guide for fastboot, the lone change you need to make for OSX is:
./fastboot devices
./fastboot flash
./fastboot reboot
./ADB devices
Try this out and post your results.
Sent from my Nexus 5X using Tapatalk

Just throwing this out there, it is possible to flash an OTA in TWRP. You still need a PC but its do-able.... I flashed Android N Final to my 6P yesterday by copying the OTA zip (uploaded thanks to another member) to SD, Wiped device as I normally would with any other ROM (left SD intact obviously), Flashed OTA ZIP, rebooted straight to bootloader after flash, fastboot erase boot, fastboot erase recovery, fastboot flashed DECRYPTED BOOT.img (which can be found easily), fastboot flashed TWRP 3.0.2-1 (version just released for N), fastboot format userdata, fastboot format cache, reboot from bootloader directly into TWRP, flashed superSU 2.74, reboot system..... Phone runs beautifully. Not a single issue. Entire process from start to finish was less than 10 minutes.
Its not the most practical route but it does indeed work. OTA just hes to contain the entire Image. I should also mention that this was a jump from a Marshmallow based rom (RR) so you don't have to be on an N preview in order to do this....

How to fix boot loop without OEM unlocking allowed or allow it using fastboot?

I have recently purchased Nexus 6P which has boot loop problem and I know that I could potentially fix this issue by side loading OTA image via adb or flashing full factory image via fastboot. Side loading has completed successfully, but it hasn't fixed boot loop issue. Also I cannot flash full factory image because OEM unlocking wasn't allowed.
Maybe someone knows how to allow OEM unlocking using fastboot? I will appreciate any help. Thanks in advance!

anokmik said:
I have recently purchased Nexus 6P which has boot loop problem and I know that I could potentially fix this issue by side loading OTA image via adb or flashing full factory image via fastboot. Side loading has completed successfully, but it hasn't fixed boot loop issue. Also I cannot flash full factory image because OEM unlocking wasn't allowed.
Maybe someone knows how to allow OEM unlocking using fastboot? I will appreciate any help. Thanks in advance!
Click to expand...
Click to collapse
Not possible. If the bootloader is locked and you can't boot into Android OS to allow OEM unlocking, you won't be using fastboot. Any luck using stock recovery to factory reset after a sideload? FYI all data on the phone will be lost.

RoyJ said:
Not possible. If the bootloader is locked and you can't boot into Android OS to allow OEM unlocking, you won't be using fastboot. Any luck using stock recovery to factory reset after a sideload? FYI all data on the phone will be lost.
Click to expand...
Click to collapse
You mean by factory reset formatting cache and data from recovery options?
Also I'm currently on MTC20F/6.0.1 build. Maybe it is reasonable to sideload more recent version?

anokmik said:
You mean by factory reset formatting cache and data from recovery options?
Also I'm currently on MTC20F/6.0.1 build. Maybe it is reasonable to sideload more recent version?
Click to expand...
Click to collapse
Yeah that's what I meant. Factory reset and cache wipe from stock recovery options. I guess it couldn't hurt to try sideloading 7.1.1.
It sort of sounds like the issue people had with the bugged versions of TWRP when restoring a backup, but the phone has stock recovery, right? I'll post a link to the thread where a bunch of people were collaborating to try to figure it out. You can search the thread to see if any suggestions help you out. I don't personally follow the thread, since I never had the issue and generally don't restore nandroid backups unless I absolutely have to. Usually if I need to restore I just plug into a PC and restore manually.
Edit: http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page44
Not sure if a solution is there for you, but can't hurt to check out.

anokmik said:
I have recently purchased Nexus 6P which has boot loop problem and I know that I could potentially fix this issue by side loading OTA image via adb or flashing full factory image via fastboot. Side loading has completed successfully, but it hasn't fixed boot loop issue. Also I cannot flash full factory image because OEM unlocking wasn't allowed.
Maybe someone knows how to allow OEM unlocking using fastboot? I will appreciate any help. Thanks in advance!
Click to expand...
Click to collapse
When did you purchase the phone?
Was it used before purchasing?
What version of Android was running on the phone when it bootlooped?
Does your phone boot upto Android colorful dots animation or boots upto Google logo only?
Please answer these questions to give us insight about your problem.

RoyJ said:
Yeah that's what I meant. Factory reset and cache wipe from stock recovery options. I guess it couldn't hurt to try sideloading 7.1.1.
It sort of sounds like the issue people had with the bugged versions of TWRP when restoring a backup, but the phone has stock recovery, right? I'll post a link to the thread where a bunch of people were collaborating to try to figure it out. You can search the thread to see if any suggestions help you out. I don't personally follow the thread, since I never had the issue and generally don't restore nandroid backups unless I absolutely have to. Usually if I need to restore I just plug into a PC and restore manually.
Edit: http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page44
Not sure if a solution is there for you, but can't hurt to check out.
Click to expand...
Click to collapse
Yep, this device has stock recovery and I will try to sideload 7.1.1 with factory reset and will reply here with the result. Also thanks for thread link! I will read it and maybe follow up in this thread with some questions.
fapste said:
When did you purchase the phone?
Was it used before purchasing?
What version of Android was running on the phone when it bootlooped?
Does your phone boot upto Android colorful dots animation or boots upto Google logo only?
Please answer these questions to give us insight about your problem.
Click to expand...
Click to collapse
1. Yes, it was used previously by someone.
2. 6.0.1. I guess. This is the build version that is specified in the stock recovery.
3. Unfortunately only Google boot logo appear on device's screen.
Will be very happy if this could help.

anokmik said:
Yep, this device has stock recovery and I will try to sideload 7.1.1 with factory reset and will reply here with the result. Also thanks for thread link! I will read it and maybe follow up in this thread with some questions.
1. Yes, it was used previously by someone.
2. 6.0.1. I guess. This is the build version that is specified in the stock recovery.
3. Unfortunately only Google boot logo appear on device's screen.
Will be very happy if this could help.
Click to expand...
Click to collapse
Can you manually get the device into the bootloader? If so you should be able to flash the full factory image following the instructions on Google's image download page. The flash.bat.all command works even with a locked bootloader and even if USB debugging is not enabled. It saved me a few times when I was soft bricked and nothing else helped.

jhs39 said:
Can you manually get the device into the bootloader? If so you should be able to flash the full factory image following the instructions on Google's image download page. The flash.bat.all command works even with a locked bootloader and even if USB debugging is not enabled. It saved me a few times when I was soft bricked and nothing else helped.
Click to expand...
Click to collapse
are you sure you can flash the factory img with a locked bootloader? I'm counting on this because I can flash rescue OTAs in recovery successfully but nothing changes after OTA sideload. I was hoping I can flash factory img but unfortunately my bootloader is locked.

Alsen Lea said:
are you sure you can flash the factory img with a locked bootloader? I'm counting on this because I can flash rescue OTAs in recovery successfully but nothing changes after OTA sideload. I was hoping I can flash factory img but unfortunately my bootloader is locked.
Click to expand...
Click to collapse
Try fastboot flashing unlock or fastboot oem unlock to unlock your bootloader.
---------- Post added at 09:04 AM ---------- Previous post was at 08:59 AM ----------
jhs39 said:
Try fastboot flashing unlock or fastboot oem unlock to unlock your bootloader.
Click to expand...
Click to collapse
I thought I read that flash-all.bat worked even with a locked bootloader but that may have been wrong. But if you can get into fastboot you should be able to unlock the bootloader.

RoyJ said:
Yeah that's what I meant. Factory reset and cache wipe from stock recovery options. I guess it couldn't hurt to try sideloading 7.1.1.
It sort of sounds like the issue people had with the bugged versions of TWRP when restoring a backup, but the phone has stock recovery, right? I'll post a link to the thread where a bunch of people were collaborating to try to figure it out. You can search the thread to see if any suggestions help you out. I don't personally follow the thread, since I never had the issue and generally don't restore nandroid backups unless I absolutely have to. Usually if I need to restore I just plug into a PC and restore manually.
Edit: http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page44
Not sure if a solution is there for you, but can't hurt to check out.
Click to expand...
Click to collapse
Steps that I have done from stock recovery:
1. Wipe cache
2. Wipe data/ factory reset
3. Sideload 7.0 (angler-ota-nbd91k-32c2eac8) and the result is successful "script succeded: result was [1.000000]"
4. Wipe cache
5. Wipe data/ factory reset
6. Power off
7. Power on
Unfortunately boot loop persists and if I go back to recovery there is the same build version MTC20F (6.0.1).
jhs39 said:
Can you manually get the device into the bootloader? If so you should be able to flash the full factory image following the instructions on Google's image download page. The flash.bat.all command works even with a locked bootloader and even if USB debugging is not enabled. It saved me a few times when I was soft bricked and nothing else helped.
Click to expand...
Click to collapse
jhs39 said:
Try fastboot flashing unlock or fastboot oem unlock to unlock your bootloader.
I thought I read that flash-all.bat worked even with a locked bootloader but that may have been wrong. But if you can get into fastboot you should be able to unlock the bootloader.
Click to expand...
Click to collapse
For "fastboot oem unlock" command prompt returns "failed: remote: unknown command". I think this is because Google has changed such command to "fastboot flashing unlock", which gives me "failed: remote: oem unlock is not allowed". This because OEM unlocking hasn't been allowed from Developer Options by previous owner and now I cannot get there because of boot loop. Also have tried "flash-all.bat" from 7.0 latest factory image and on each step it returns error "failed: remote: device is locked. cannot flash images" and this is because of locked bootloader.
Possible solution?
In Stock recovery I have "Mount /system" option. Maybe someone can clarify what does it mean and could it potentially fix boot loop in some way? I have tried google for it, but unfortunately have no luck in finding information about this option.
Thanks in advance for any information!

anokmik said:
Yep, this device has stock recovery and I will try to sideload 7.1.1 with factory reset and will reply here with the result. Also thanks for thread link! I will read it and maybe follow up in this thread with some questions.
1. Yes, it was used previously by someone.
2. 6.0.1. I guess. This is the build version that is specified in the stock recovery.
3. Unfortunately only Google boot logo appear on device's screen.
Will be very happy if this could help.
Click to expand...
Click to collapse
Seems like the previous owner had upgraded to NOUGAT and then downgraded to 6.0.1 when he put the device up for sale. This issue occurs because of nougat. Star this issue on Google's website to bring to Google's attention to it
https://code.google.com/p/android/issues/detail?id=230848&thanks=230848&ts=1482412796

You might want to take a look at this:
https://drive.google.com/file/d/0Bz6x7k-VkpUJRjl6WjRhVmdXU0E/view
They are instructions for applying a rescue OTA, which supposedly works even if your bootloader is locked.
---------- Post added at 11:39 AM ---------- Previous post was at 11:29 AM ----------
There is also a toolkit you might want to take a look at:
http://www.wugfresh.com/nrt/

fapste said:
Seems like the previous owner had upgraded to NOUGAT and then downgraded to 6.0.1 when he put the device up for sale. This issue occurs because of nougat. Star this issue on Google's website to bring to Google's attention to it
https://code.google.com/p/android/issues/detail?id=230848&thanks=230848&ts=1482412796
Click to expand...
Click to collapse
Issue has star from me now. Thanks for the link!
jhs39 said:
You might want to take a look at this:
https://drive.google.com/file/d/0Bz6x7k-VkpUJRjl6WjRhVmdXU0E/view
They are instructions for applying a rescue OTA, which supposedly works even if your bootloader is locked.
There is also a toolkit you might want to take a look at:
http://www.wugfresh.com/nrt/
Click to expand...
Click to collapse
I have tried applying rescue OTA and that tool, but they doesn't help me.
The reason for my issue is that OEM unlocking hasn't been allowed by previous owner. So I'm looking for some options how to enable it from fastboot.

anokmik said:
Issue has star from me now. Thanks for the link!
I have tried applying rescue OTA and that tool, but they doesn't help me.
The reason for my issue is that OEM unlocking hasn't been allowed by previous owner. So I'm looking for some options how to enable it from fastboot.
Click to expand...
Click to collapse
Are you running the latest versions of ADB and Fastboot?

This sounds like an issue that would have been covered under warranty --for the original owner. Did you buy the phone knowing about the boot loop problem?

jhs39 said:
Are you running the latest versions of ADB and Fastboot?
Click to expand...
Click to collapse
These are the outputs from command prompt:
adb:
Android Debug Bridge version 1.0.36
Revision 0e9850346394-android
fastboot:
fastboot version 0e9850346394-android
I think that they are the latest, because I'm an Android dev and I'm updating SDK with tools as soon as new version come in.
jhs39 said:
This sounds like an issue that would have been covered under warranty --for the original owner. Did you buy the phone knowing about the boot loop problem?
Click to expand...
Click to collapse
Yep, I have known that device has boot loop issue and it was selling as-is for repair. Also I have known that this issue could be fixed, so it was hit or miss. Now I think that this was a miss.

It's starting to look that way. You would think there would be a way to reformat the drive and start from scratch like a computer. Maybe someone with programming knowledge will find a fix for you. It's odd the owner didn't RMA the phone rather than sell it as is/not working. Huawei was even fixing phones with similar issues for free a couple months out of warranty.

jhs39 said:
It's starting to look that way. You would think there would be a way to reformat the drive and start from scratch like a computer. Maybe someone with programming knowledge will find a fix for you. It's odd the owner didn't RMA the phone rather than sell it as is/not working. Huawei was even fixing phones with similar issues for free a couple months out of warranty.
Click to expand...
Click to collapse
Maybe there are some options for me to contact Huawei and ask for replacement? What are the requirements?

anokmik said:
Maybe there are some options for me to contact Huawei and ask for replacement? What are the requirements?
Click to expand...
Click to collapse
I don't think the warranty is transferable but it won't cost you anything to contact Huawei and see if they will help you out.
http://consumer.huawei.com/in/support/warranty-query/index.htm
You can go to this site to check if the device is still under warranty. I have read about them allowing RMA on 6Ps that were out of warranty so it's worth a try at least.

http://consumer.huawei.com/us/support/warranty-query/index.htm
Sorry this is the site to check if phone is in warranty within the US. Other site was for India.