Nexus 5 OTA no command error - Nexus 5 Q&A, Help & Troubleshooting

I have a rooted Nexus 5 stock aside from root. Installed the 4.4.2 OTA yesterday and now the phone is stuck in a boot loop. I have reset the phone and wipes the cache but it displays a dead andriod and a dialogue that says no command.
Not sure how to fix this I can get into fastboot mode and the recovery. Any sugested on how to proceed is this a corrupt boot loader?

Flash a factory image.
See general forum for stickies.

rootSU said:
Flash a factory image.
See general forum for stickies.
Click to expand...
Click to collapse
Thanks - refreshed the whole device
http://forum.xda-developers.com/showthread.php?t=2513701

Related

[Q] Stuck in boot loop after recovery attempt

I'm trying to recover to stock after having a custom ROM for a few days (Cyanogenmod, nothing too fancy).
I was using this guide over on the Nexus dev forum:
http://forum.xda-developers.com/showthread.php?t=2513701
Everything went smoothly until after I flashed the bootunlocker zip to revert the tampered flag back to normal. Then the reboot loop happened.
I've flashed multiple times using both methods to no avail. I also updated the driver on Windows 7.
dabockster said:
I'm trying to recover to stock after having a custom ROM for a few days (Cyanogenmod, nothing too fancy).
I was using this guide over on the Nexus dev forum:
http://forum.xda-developers.com/showthread.php?t=2513701
Everything went smoothly until after I flashed the bootunlocker zip to revert the tampered flag back to normal. Then the reboot loop happened.
I've flashed multiple times using both methods to no avail. I also updated the driver on Windows 7.
Click to expand...
Click to collapse
Try to get into recovery and clear the caches and do a data factory reset. Just hold power down and power at the same time and select recovery.
gee2012 said:
Try to get into recovery and clear the caches and do a data factory reset. Just hold power down and power at the same time and select recovery.
Click to expand...
Click to collapse
This works, and it gets me working again. But I would like to reset that flag if possible. It all breaks when I flash the zip found here:
http://forum.xda-developers.com/showthread.php?t=2239421
The NexusBootUnlocker script is what is being referenced in the restoration guide.
dabockster said:
This works, and it gets me working again. But I would like to reset that flag if possible. It all breaks when I flash the zip found here:
http://forum.xda-developers.com/showthread.php?t=2239421
The NexusBootUnlocker script is what is being referenced in the restoration guide.
Click to expand...
Click to collapse
Did you boot into TWRP to flash the Bootlocker.zip? In cmd type `fastboot boot twrp.img` (or the name you have given it) and reboot?
dabockster said:
This works, and it gets me working again. But I would like to reset that flag if possible. It all breaks when I flash the zip found here:
http://forum.xda-developers.com/showthread.php?t=2239421
The NexusBootUnlocker script is what is being referenced in the restoration guide.
Click to expand...
Click to collapse
You can use that script with twrp by booting it as mentiomed above or if u r rooted then u can also use nexus bootunlocker from play store.
gee2012 said:
Did you boot into TWRP to flash the Bootlocker.zip? In cmd type `fastboot boot twrp.img` (or the name you have given it) and reboot?
Click to expand...
Click to collapse
Yep. I have done the guide to the letter and followed the video. Nothing.
And it might be worth noting that I am doing this on a red Nexus 5 (the new color). Maybe Google changed something?
dabockster said:
Yep. I have done the guide to the letter and followed the video. Nothing.
And it might be worth noting that I am doing this on a red Nexus 5 (the new color). Maybe Google changed something?
Click to expand...
Click to collapse
No, that doesn`t make a difference. What do you see when you type in cmd: `fastboot oem device-info` with the phone in bootloader?
gee2012 said:
No, that doesn`t make a difference. What do you see when you type in cmd: `fastboot oem device-info` with the phone in bootloader?
Click to expand...
Click to collapse
It shows that the bootloader is locked and the tampering flag is false, just like the tutorial said. However, normal boot results in a loop.
dabockster said:
It shows that the bootloader is locked and the tampering flag is false, just like the tutorial said. However, normal boot results in a loop.
Click to expand...
Click to collapse
So it worked, now go into recovery and wipe the caches and do a data factory reset and then it should boot normaly.
Don't use the zip then. Unlock the bootloader, root the phone and download bootunlocker app.
Then, reset tamper and lock from the app. Unroot using supersu
Sent from my Nexus 5 using Tapatalk
gee2012 said:
So it worked, now go into recovery and wipe the caches and do a data factory reset and then it should boot normally.
Click to expand...
Click to collapse
Nope, won't boot to recovery. All I have is the adb at the bootloader.
EDIT: Tried unplugging the USB while it was booting. This fixed everything! Thanks for the help!
dabockster said:
Nope, won't boot to recovery. All I have is the adb at the bootloader.
Click to expand...
Click to collapse
What happens when you type in cmd: fastboot reboot recovery ?
dabockster said:
Nope, won't boot to recovery. All I have is the adb at the bootloader.
Click to expand...
Click to collapse
When you say it won't boot into recovery do you get the dead android with the red exclamation mark? That is recovery just hit vol up
Sent from my Nexus 5
dabockster said:
Nope, won't boot to recovery. All I have is the adb at the bootloader.
Click to expand...
Click to collapse
You can't use adb at the bootloader
Only fastboot works
Sent from my Nexus 5 using Tapatalk
So I just tried booting it while unplugged from my computer and it worked flawlessly. This bit should be added to future unroot guides.
Thanks for the help!

[Q] Help! problems after instaling twrp 2.7

Ok so today i wanted to root my nexus 5 so i unlocked bootloader via androidSDK slim everything went fine but i did not power up my device yet thet i flash the recovery.img of twrp after that i booted into recovery and for a second it displayed some error i could not see it but it said could not read /e..... or i think so and it reboted itself and started booting android and now i think im stuck in boot loop because its booting up for 10 mins. can someone help me?
So now your Bootloader is unlocked, right?
First boot after unlocking the Bootloader takes time... Wait for 10 more mins and then reboot once again and see whether you can get the OS to bootup...
If you can't, you can either try factory reseting from Bootloader or you can flash a custom recovery and then install a custom rom of your choice.
Or you can also go full stock and start over again by flashing a factory image...
-Sent from an IceCold Hammerhead!
You're supposed to reboot the bootloader before flashing anything.
vin4yak said:
So now your Bootloader is unlocked, right?
First boot after unlocking the Bootloader takes time... Wait for 10 more mins and then reboot once again and see whether you can get the OS to bootup...
If you can't, you can either try factory reseting from Bootloader or you can flash a custom recovery and then install a custom rom of your choice.
Or you can also go full stock and start over again by flashing a factory image...
-Sent from an IceCold Hammerhead!
Click to expand...
Click to collapse
yes it is unlocked as i sad and i installed twrp so i have custom recovery ok ill wait a bit more and see what happends. what happens if i factory reset from bootloder?
rootSU said:
You're supposed to reboot the bootloader before flashing anything.
Click to expand...
Click to collapse
after it sad that unlocking is done with ulocking on command promt on my pc and on my phone i flashed the recovery right away. Now i turned my phone down by pressing power and vol down button and booted recovery and it did boot fine in twrp no with errors like first time so i gone to reboot and then system and it said that my phone is not rooted and to install super su i did that and now its booting up for like 10mins again still cant boot up into android. what can i do to fix this?
Alexandar92zr said:
after it sad that unlocking is done with ulocking on command promt on my pc and on my phone i flashed the recovery right away
Click to expand...
Click to collapse
This was your first mistake
Alexandar92zr said:
i turned my phone down by pressing power and vol down button and booted recovery and it did boot fine in twrp no with errors like first time so i gone to reboot and then system and it said that my phone is not rooted and to install super su i did that
Click to expand...
Click to collapse
And this the second mistake. Nothing should have been done before first restarting the bootloader.
Alexandar92zr said:
what can i do to fix this?
Click to expand...
Click to collapse
Flash the factory images from google for the nexus 5. There is a guide in General.
Once your phone boots, flash a recovery
rootSU said:
This was your first mistake
And this the second mistake. Nothing should have been done before first restarting the bootloader.
Flash the factory images from google for the nexus 5. There is a guide in General.
Once your phone boots, flash a recovery
Click to expand...
Click to collapse
can you link me the tutorial how to do that?
Alexandar92zr said:
can you link me the tutorial how to do that?
Click to expand...
Click to collapse
It's in General.
rootSU said:
This was your first mistake
And this the second mistake. Nothing should have been done before first restarting the bootloader.
Flash the factory images from google for the nexus 5. There is a guide in General.
Once your phone boots, flash a recovery
Click to expand...
Click to collapse
rootSU said:
It's in General.
Click to expand...
Click to collapse
sorry im a bin nervous becausemy phone is not working. i ment a tutorial how to flash factory images.
Alexandar92zr said:
sorry im a bin nervous becausemy phone is not working. i ment a tutorial how to flash factory images.
Click to expand...
Click to collapse
Don't be tense, you will tend to do more damage. Calm down m8.
here you go: http://forum.xda-developers.com/showthread.php?t=2513701
vin4yak said:
Don't be tense, you will tend to do more damage. Calm down m8.
here you go: http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
i found a tutorial on yt and now my phone is ok and running now i will flash custom recovery. thanks anyway and thanks a lot @rootSU
Alexandar92zr said:
sorry im a bin nervous becausemy phone is not working. i ment a tutorial how to flash factory images.
Click to expand...
Click to collapse
That was the answer. The tutorial is in the general forum here. ALL our important tutorials are in general
rootSU said:
That was the answer. The tutorial is in the general forum here. ALL our important tutorials are in general
Click to expand...
Click to collapse
now im rooted and everything is working as it should be thanks

Remote: flash write failure

Again...
Three days ago, I wake up and the Nexus 5 doesn't work. I reboot it, and it is stuck on the Google logo screen. When I went in the TWRP recovery, I couldn't find nothing. Everything erased. Today I received my PC (Ram problems with it) and I tried to flash the factory image 4.4.4, but, when writing the bootloader, the cmd says "remote: flash write failure".
It is happened one month ago, and I had to send it to a LG Center because nothing worked (here the post)
There is something that I can do or I have to send it again to a LG Center? And why diid it happened again?
Again it's probably dead eMMC lol
Giolte_ said:
Again...
Three days ago, I wake up and the Nexus 5 doesn't work. I reboot it, and it is stuck on the Google logo screen. When I went in the TWRP recovery, I couldn't find nothing. Everything erased. Today I received my PC (Ram problems with it) and I tried to flash the factory image 4.4.4, but, when writing the bootloader, the cmd says "remote: flash write failure".
It is happened one month ago, and I had to send it to a LG Center because nothing worked (here the post)
There is something that I can do or I have to send it again to a LG Center? And why diid it happened again?
Click to expand...
Click to collapse
Emmc is corrupt you have to send it again. Juat coincedence that it happened again
So I have to send again to LG?
Giolte_ said:
So I have to send again to LG?
Click to expand...
Click to collapse
I just said that -.-
Sorry, I have reloaded the page when only Lethargy had posted
Strange thing... I was following this post, and when I do fastboot boot twrp.img it reboots to twrp and it reboots again, and now there is on my screen the SlimKat boot animation since 5 minutes (SlimKat is the rom that I was running 3 days ago)... what I have to do?
Giolte_ said:
Strange thing... I was following this post, and when I do fastboot boot twrp.img it reboots to twrp and it reboots again, and now there is on my screen the SlimKat boot animation since 5 minutes (SlimKat is the rom that I was running 3 days ago)... what I have to do?
Click to expand...
Click to collapse
Sure looks like you have to rma the device again
Sent from my Nexus 5 using XDA Free mobile app
I can't RMA, I buy it from a retail, in fact I have to reset the temper flag, but when I do this it reboots the system...
Giolte_ said:
I can't RMA, I buy it from a retail, in fact I have to reset the temper flag, but when I do this it reboots the system...
Click to expand...
Click to collapse
Have you tried LG Flashtool?
No, I have not understood how to use it..
I have not understood things like the factory version change, and I don't want to brick the phone... there is anything else that I can do?
The phone is already pretty much bricked imo.. Flash write failure means write access to the eMMC has gone kaappuuuttt!
You need to send the device back to LG as already stated by others. It's very unfortunate that this happened to you twice in such a short period.
Sorry for all these posts, but I don't understand this:
I have locked the bootloader, than I unlock it again. When I navigate to start and "click" it, the device opens TWRP recovery and run a process called "Open Recovery" or something like this.
How is it possible? If I unlock the bootloader why the TWRP recovery is always here?
___
Yes Vin, but how can I send it to LG if I don't reset it?
Giolte_ said:
Sorry for all these posts, but I don't understand this:
I have locked the bootloader, than I unlock it again. When I navigate to start and "click" it, the device opens TWRP recovery and run a process called "Open Recovery" or something like this.
How is it possible? If I unlock the bootloader why the TWRP recovery is always here?
___
Yes Vin, but how can I send it to LG if I don't reset it?
Click to expand...
Click to collapse
Locking the bootloading doesn't wipe your recovery. You will need to flash the stock recovery via fastboot to replace twrp. However, I doubt whether you will be able to replace it since the eMMC has gone bad. Anyways, there;'s nothing to loose.. Give it a shot.
I only have to flash the stock recovery in the google factory image 4.4.4 or I have to do particular passages?
Giolte_ said:
I only have to flash the stock recovery in the google factory image 4.4.4 or I have to do particular passages?
Click to expand...
Click to collapse
1. Unlock the bootloader (if it's locked).
2. Flash stock recovery.img via fastboot.
3. Reboot and use command "fastboot boot twrp.img" //This will boot your device into twrp.
4. Sideload this file in twrp: http://forum.xda-developers.com/attachment.php?attachmentid=2467503&d=1387666907
The above file will reset the tamper flag and lock the bootloader!
When I extract the files from the zip, the boot, system and recovery are dated 12/12/2008... is this normal?
Yes..
Ok, last questions... if I'll flash the zip, I have to use in sideload this: "adb sideload cwm-Nexus.BootUnlocker.zip"?
And why, there is "cwm" in the name? Sorry for all these questions, but I don't want to burn my last hope...

Nexus 5 Stuck On 'Formatting /Data' After Factory Image Flashing

Nexus 5 stuck on 'formatting /data' screen after factory image flashing
Sorry for the long post. I just want to ensure I am providing all relevant history.
I have a Nexus 5 (Hammerhead) 32gb device, stock with no rooting. I mean, I had never done anything special on it ever.
1. Recently I started getting Google Play Store related problems, first 194 error and then couple of days back 495 (I think). After trying switching on/off, clearing cache and some other similar ways to fix this, I decided to do a factory reset :crying:
2. I backed up all my data, and followed the documented steps for factory reset. The phone got stuck on 'erasing'. After waiting for over 24 hours, I finally figured out that this 'erasing' is not going to complete, ever.
3. So I again did some research and figured that I should do a fastboot recovery. Tried that with no difference. Recovery again took me to 'erasing' screen.
4. Some more research and then I decided to flash a factory image using ADB. I was (and still am) a complete newbie, so first I figured out what was ADB and how to get to it. After completing the installation, I found out Nexus 5 factory images. There was no mention of which ones to chose, so I just picked up the latest one.
This is what I really followed:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
https://www.youtube.com/watch?v=DRp5jJO34PE
5. Having learnt my lessons, I read the flashing instructions many times and also watched some videos 3-4 times. Once I was confident that no more information was going to be had, and the phone was unlocked (fastboot oem unlock) I went ahead with the flashing. I did it step by step - bootloader, radio and they recovery image. The last one failed.
6. I did some more research and found a method which told me to unzip the last image and flash the component images one by one. I did. Success! However, the phone did not reboot by itself as the guide said it would. So I tried to boot it manually.
7. I did not get the dead android with red exclamation mark. Instead, I got an alive android with gears whirring on its tummy and back. Pressing power + vol-up button told me that this was the 'formatting /data' screen. I am unable to get past this screen. I am supposed to get to a screen where I can wipe data and cache etc. But I cannot get to it.
8. I have tried to wait it out (16 hours) and tried flashing the images again. Ultimately, I end up here.
9. I am unable to find any answers on what to do if stuck on this screen. So this is the end? Is my phone bricked? Is there anything else I can try? Will trying TWRP way help or is that just another way to same failure?
I would appreciate if there is anybody out there who can help me get my phone working again, or point me to a thread which helps me do it. Thanks!
Just wait it took me 5 hours of waiting
Try flashing Android 4.4.4 and see if that will boot. If that does not work try installing a custom recovery like TWRP, and do the wipes from there.
dicecuber said:
Just wait it took me 5 hours of waiting
Click to expand...
Click to collapse
I doubt it. 12 more hours have passed with no change.
eross said:
Try flashing Android 4.4.4 and see if that will boot. If that does not work try installing a custom recovery like TWRP, and do the wipes from there.
Click to expand...
Click to collapse
Thanks. I was thinking of trying TWRP anyway. I will try this today.
How does one select which image to flash? Is it always the latest one? In this case, how do I know which one is Android 4.4.4, and why are you recommending this specific one? I had purchased this phone in 2013 Feb (I think). So is there any specific image to be selected or the latest one is always to be picked?
Tom2403 said:
Thanks. I was thinking of trying TWRP anyway. I will try this today.
How does one select which image to flash? Is it always the latest one? In this case, how do I know which one is Android 4.4.4, and why are you recommending this specific one? I had purchased this phone in 2013 Feb (I think). So is there any specific image to be selected or the latest one is always to be picked?
Click to expand...
Click to collapse
UPDATE: Flashing 4.4.4. did not work. I again got the 'formatting /data' screen again instead of the phone booting up. However, the formatting screen with the android with diamond circling in the tummy also has a blue line below, possibly a progress bar. It is not growing though, just there... sizzling. Pressing power+vol-up buttons shows me that this is 'formatting /data' screen.
Will try custom recovery from TWRP now.
Tom2403 said:
UPDATE: Flashing 4.4.4. did not work. I again got the 'formatting /data' screen again instead of the phone booting up. However, the formatting screen with the android with diamond circling in the tummy also has a blue line below, possibly a progress bar. It is not growing though, just there... sizzling. Pressing power+vol-up buttons shows me that this is 'formatting /data' screen.
Will try custom recovery from TWRP now.
Click to expand...
Click to collapse
Reboot your phone into bootloader and download latest hammerhead 5.1.1 from Google. Extract everything and then extract the images. First use these commands
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Then fastboot flash everything including bootloader.
Use this as a guide http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
Then after finished reboot phone and leave it alone it will boot right up in 5-10 mins no need to go to recovery. In future don't format partitions.
try this: fastboot format cache
matt1515 said:
Reboot your phone into bootloader and download latest hammerhead 5.1.1 from Google. Extract everything and then extract the images. First use these commands
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Then fastboot flash everything including bootloader.
Use this as a guide http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
Then after finished reboot phone and leave it alone it will boot right up in 5-10 mins no need to go to recovery. In future don't format partitions.
Click to expand...
Click to collapse
Sorry for the late update. I was traveling over the weekend.
Thank you so much! Your post solved my issue. I wish I had this advice earlier!
First time it did not work, with reboot leading to a blank screen. Next time I following the guide completely, following the order in which different images were flashed. The phone went into boot animation for 5.1.1 and finally booted up, with all 32gb storage available.
Thanks again!
Tom2403 said:
UPDATE: Flashing 4.4.4. did not work. I again got the 'formatting /data' screen again instead of the phone booting up. However, the formatting screen with the android with diamond circling in the tummy also has a blue line below, possibly a progress bar. It is not growing though, just there... sizzling. Pressing power+vol-up buttons shows me that this is 'formatting /data' screen.
Will try custom recovery from TWRP now.
Click to expand...
Click to collapse
Tom2403 said:
Sorry for the late update. I was traveling over the weekend.
Thank you so much! Your post solved my issue. I wish I had this advice earlier!
First time it did not work, with reboot leading to a blank screen. Next time I following the guide completely, following the order in which different images were flashed. The phone went into boot animation for 5.1.1 and finally booted up, with all 32gb storage available.
Thanks again!
Click to expand...
Click to collapse
Glad to hear you got it up and running! No problem at all feels great to bring something f'd back to life.
Tom2403 said:
Sorry for the late update. I was traveling over the weekend.
Thank you so much! Your post solved my issue. I wish I had this advice earlier!
First time it did not work, with reboot leading to a blank screen. Next time I following the guide completely, following the order in which different images were flashed. The phone went into boot animation for 5.1.1 and finally booted up, with all 32gb storage available.
Thanks again!
Click to expand...
Click to collapse
I have same problem. I did everything that was written above but still my phone shows android with rotating cube on its tummy. Any ideas? Thanks in advance
dmuml10 said:
I have same problem. I did everything that was written above but still my phone shows android with rotating cube on its tummy. Any ideas? Thanks in advance
Click to expand...
Click to collapse
Go into bootloader and format the cache: fastboot format cache
inimaitimepass said:
Go into bootloader and format the cache: fastboot format cache
Click to expand...
Click to collapse
I did that but nothing changed. Still shows android with rotating gears.
Does anyone know what does that animation mean ?
dmuml10 said:
I did that but nothing changed. Still shows android with rotating gears.
Does anyone know what does that animation mean ?
Click to expand...
Click to collapse
How long did you leave at that? Sometimes it may take long time depending upon the storage size of your phone. Usually between 20 to 40 mins.
inimaitimepass said:
How long did you leave at that? Sometimes it may take long time depending upon the storage size of your phone. Usually between 20 to 40 mins.
Click to expand...
Click to collapse
I left it more than an hour.
Is it normal that my phone shows this Android animation after I flushed new factory image? Why is it trying to still "Format /data..." after new image flush?
Is there any other way to flush android factory image from scratch? I already used nexus root toolkit and fastboot
dmuml10 said:
I left it more than an hour.
Is it normal that my phone shows this Android animation after I flushed new factory image? Why is it trying to still "Format /data..." after new image flush?
Is there any other way to flush android factory image from scratch? I already used nexus root toolkit and fastboot
Click to expand...
Click to collapse
I'm really sorry that you are stuck in this mess. It is normal but more than 1 hour is way too much. I'm not sure about the causes, but you can try two more things and see how it goes. One is to use flash-all.bat script. If that didn't work then you can flash a custom ROM like Chroma and then try flashing the stock ROM.
inimaitimepass said:
I'm really sorry that you are stuck in this mess. It is normal but more than 1 hour is way too much. I'm not sure about the causes, but you can try two more things and see how it goes. One is to use flash-all.bat script. If that didn't work then you can flash a custom ROM like Chroma and then try flashing the stock ROM.
Click to expand...
Click to collapse
Thanks for help.
I flashed philz_touch recovery. From there I did factory reset and after that I executed this commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot flash bootloader "name of bootloader"
fastboot reboot-bootloader
fastboot flash radio "name of radio"
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot reboot
Now my phone works.:victory:
dmuml10 said:
Now my phone works.:victory:
Click to expand...
Click to collapse
Good to hear. Weren't you using a custom recovery before philz'?
inimaitimepass said:
Good to hear. Weren't you using a custom recovery before philz'?
Click to expand...
Click to collapse
No. I only used stock recovery before philz.

Hard Bricked pixel 3

SO... I did a dumb thing... my friend asked me to install android Q beta on her phone, so I did a sideload.... never checking if it was a verizon phone first... the sideload never errored looked like all was good until the reboot.... operating system corrupt warning... boot to recovery same message... only fastboot with a locked verizon boot loader... did some research looks like I need a firehose... yep.. cant find one... any suggestions or perhaps someone able to help me out?
Did you already try to flash the factory image?
Can be found here: developer.android.com/preview/download#flash (sorry, I cannot post links yet)
First try to flash it without the "-w" flag. If it still does not start, try it with the "-w" flag, but that will delete all data on the phone.
// EDIT if that does not work you might want to head over to the Pixel 3 XL guys here: https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849/page10
I can not flash anything in fastboot due to locked bootloader it always says not permitted. booting recovery or OS always says corrupted with the triangle, recovery does NOT show the android guy, just a warning message. fastboot and qualcomm EDL is all I have available.
LSDemon said:
I can not flash anything in fastboot due to locked bootloader it always says not permitted. booting recovery or OS always says corrupted with the triangle, recovery does NOT show the android guy, just a warning message. fastboot and qualcomm EDL is all I have available.
Click to expand...
Click to collapse
If you are sure that you can't get into recovery I'd suggest getting an RMA for your friend who has been without the device for 4 or 5 days.

Categories

Resources