Hi XDA guys, so i have this trouble and i don't know what to do, the problem is that my phone get bricked after updating whatsapp and now i can only boot the phone into fastboot an when i try to unlock the bootlader i get this, so help me please!!
Code:
(bootloader) BLKDISCARD ioctl /dev/block/mmcblk0 fail
(bootloader) Erase userdata fail
(bootloader) General Unlock failure!
(bootloader) OEM unlock failure!
FAILED (remote failure)
finished. total time: 8.603s
Victor Gtz said:
Hi XDA guys, so i have this trouble and i don't know what to do, the problem is that my phone get bricked after updating whatsapp... [/CODE]
Click to expand...
Click to collapse
Hi, maybe you could give us some more clear infos of what you have done exactly...
Why you want to unlock your bootloader?
Try to reflash an original firmware with RDS and if you want root use "TwerkMyMoto"...
5m00v3 said:
Hi, maybe you could give us some more clear infos of what you have done exactly...
Why you want to unlock your bootloader?
Try to reflash an original firmware with RDS and if you want root use "TwerkMyMoto"...
Click to expand...
Click to collapse
Well mi phone was working fine with stock firmware and locked bootlader, so i recive this whatsapp update and after this installation the phone shut down and get on again but with the boot logo of motorola and get stuck in it, and if i enter in fastboot non of the options work only the phone gets frized, so i was triyin to unlock the bootloader, for a chance to fix the problem with an update via RSD, but when i try to unlock the bootlader it gives me the error as i mention in the first post and i dont know what do
Victor Gtz said:
...so i was triyin to unlock the bootloader, for a chance to fix the problem with an update via RSD...
Click to expand...
Click to collapse
you dont need to unlock the bootloader to reflash your original firmware via RSD-Lite!
Follow this to install stock rom: http://forum.xda-developers.com/showthread.php?t=2643779
I got yesterday also an Update-Information from whatsapp. I will NOT install until it is confirmed as non-bricking. Thx for your info/warning!
5m00v3 said:
you dont need to unlock the bootloader to reflash your original firmware via RSD-Lite!
Follow this to install stock rom: http://forum.xda-developers.com/showthread.php?t=2643779
I got yesterday also an Update-Information from whatsapp. I will NOT install until it is confirmed as non-bricking. Thx for your info/warning!
Click to expand...
Click to collapse
i Just try using RDS Lite but in the step 4 the reboot never boot and the flash fail
Can you enter recovery? Selecting it in the fastboot menu, what happens? In RSD does it flashes and only in the reboot portion it fails? Did you try to turn it on without the external SD card?
As far as i can tell the device is trying to use the linux discard command, it seems like a wipe that gone wrong.
regnotp synagogue
thiagomtl said:
Can you enter recovery? Selecting it in the fastboot menu, what happens? In RSD does it flashes and only in the reboot portion it fails? Did you try to turn it on without the external SD card?
As far as i can tell the device is trying to use the linux discard command, it seems like a wipe that gone wrong.
Click to expand...
Click to collapse
Hi thiagomtl let me answer your questions, when i try to enter in recovery the phone gets stuck again with the motorola boot logo and after a while returns to fastboot mode, and when i try to flash whit RSD in the step 4 that is reboot, on the phone stays a command that says Rebooting Droidboot and nothing happens, and yeah when i do this operaions i always remove the sim card and the sd card , so if you now something ill appreciate a lot it!!
Try those in fastboot:
fastboot erase data
fastboot erase cache
After try RSD again.
5m00v3 said:
you dont need to unlock the bootloader to reflash your original firmware via RSD-Lite!
Follow this to install stock rom: http://forum.xda-developers.com/showthread.php?t=2643779
Click to expand...
Click to collapse
Are you sure about that ?
For original firmware there is no need to unlock
thiagomtl said:
Try those in fastboot:
fastboot erase data
fastboot erase cache
After try RSD again.
Click to expand...
Click to collapse
I already do that but im still getting this error
BLKDISCARD ioctl /dev/block/mmcblk0 fail
I am guessing that is an error in the emmc, the problem is that i don't know how to fix it
Victor, I'm having the exact same problem. Did you find any solution?
I'm having the exact same problem!!
What I did was that when it gets stuck waiting for reboot I did reboot it manually into fastboot mode again and process continues. The problem is that it gets stuck again when flashing the system partition. Bootloader won't let me erase the partition nor flash it.
Tried unlocking the bootloader and:
(bootloader) BLKDISCARD ioctl /dev/block/mmcblk0 fail
(bootloader) Erase userdata fail
(bootloader) General Unlock failure!
(bootloader) OEM unlock failure!
FAILED (remote failure)
finished. total time: 9.666s
Is there a way to know the original provider of the phone, to make sure I'm using the correct firmware?
ismael_mj23 said:
I'm having the exact same problem!!
What I did was that when it gets stuck waiting for reboot I did reboot it manually into fastboot mode again and process continues. The problem is that it gets stuck again when flashing the system partition. Bootloader won't let me erase the partition nor flash it.
Tried unlocking the bootloader and:
(bootloader) BLKDISCARD ioctl /dev/block/mmcblk0 fail
(bootloader) Erase userdata fail
(bootloader) General Unlock failure!
(bootloader) OEM unlock failure!
FAILED (remote failure)
finished. total time: 9.666s
Is there a way to know the original provider of the phone, to make sure I'm using the correct firmware?
Click to expand...
Click to collapse
You got a serious bug. There is a huge change your device is now broken beyond repair, i hope not. But can u access the recovery partition? Can u flash a custom boot image?
Hazou said:
You got a serious bug. There is a huge change your device is now broken beyond repair, i hope not. But can u access the recovery partition? Can u flash a custom boot image?
Click to expand...
Click to collapse
I also having the same problem after force power on/off when hang during TWRP format. Now the unit in hard brick. If able to force temporary boot into recovery using ram instead of rom, might have some hope. But it looks like no way to boot from ram. :crying:
same prob as victor gtz
fsd lite freezes at step 4, unlock bootloader doesnt work and so on and so forth, so anybody got a clue what to do?
Dudes
Same problem here, rsdlite didnt work for me and the bootloader cant be unlocked with the same error message. Theres any way to solve this? i read once that you can recover the android from the dead even if the boot isnt working, maybe thats not true at all.....
Neyzik said:
Dudes
Same problem here, rsdlite didnt work for me and the bootloader cant be unlocked with the same error message. Theres any way to solve this? i read once that you can recover the android from the dead even if the boot isnt working, maybe thats not true at all.....
Click to expand...
Click to collapse
It's true, but not for all devices. And if u have the above, the nand memory is broken. That can only be repaired by some kind of powercycle on chip level or anything.
Related
Hi man, i have a problem.... Let's start: i had a eu moto x (xt1052) with fr firmware, moto is stock, so locked bootloader, stock recover and no root, i had received the ota to 4.4.4 but it cause me some connectivity problem, i have done the full wipe but i didnt solve; so i try to flash again the ota file but the installation fail and when i try to restart i had a bootloop (moto remain to the M screen).
i'm able to open recovery, to charge it and pc see it; how can i solve?
i also try to use rsd but there is no 4.4.4 firmware and i cant flash 4.4.2 (downgrade)
Need more details.
Since the OTA ZIp usually erases itself from the phone after successful install, how did you try and re-install it? Where did you get it from? When you say it failed, exactly what do you mean? (did you get an error? of so, what did it say?)
And you are right... DO NOT TRY AND DOWNGRADE!! Once you have 4.4.4. on there, stick with 4.4.4 or you risk bricking or setting yourself up to brick.
Since you can get into stock recovery, try and wipe data and cache from in there. Does the phone still bootloop?
ok, so it was an ota zip that someone in the italian's forum use, when i try to flash it it fail after some passage and show something like impossible rename the file? or similar.
i have try to do wipe data and wipe cache from recovery but it's the same.
how can i solve?
i try to do a fastboot erase cache and a fastboot erase data.
the first said:
(bootloader) variable not supported!
erasing 'cache'...
okay and after the seconds
with the second
(bootloader) variable not supported!
erasing 'data'...
(bootloader) invalid partition name data
FAILED (remote failure)
finished
so?
daniele1992 said:
i try to do a fastboot erase cache and a fastboot erase data.
the first said:
(bootloader) variable not supported!
erasing 'cache'...
okay and after the seconds
with the second
(bootloader) variable not supported!
erasing 'data'...
(bootloader) invalid partition name data
FAILED (remote failure)
finished
so?
Click to expand...
Click to collapse
The partition isn't named "data", it's "userdata"
Try again with the correct command:
fastboot erase userdata
no error here but i have the same bootloop
daniele1992 said:
no error here but i have the same bootloop
Click to expand...
Click to collapse
Hmmm ok. There is only ONE safe way to fix you back up. It won't be the easiest thing in the world to do since you will have to have someone on the EXACT SAME variant help you with this.
Re-flash TWRP. You'll need to find someone on the exact same XT1052 firmware (who also has TWRP) make a backup of JUST system and boot (not userdata).
They will share the backup with you, and you will flash it using TWRP (restore). That should fix you up -- it is the ONLY safe way to get back on track without downgrading and risking a brick..
hard to find but i will try, other question if i flash the new 4.4.4 firmware (when it will be relased) will i solve?
daniele1992 said:
hard to find but i will try, other question if i flash the new 4.4.4 firmware (when it will be relased) will i solve?
Click to expand...
Click to collapse
Almost certainly. Hopefully the full SBF/FXZ (Full XML Zip) for your specific variant is released very soon. Good Luck with it. :good:
samwathegreat said:
Hmmm ok. There is only ONE safe way to fix you back up. It won't be the easiest thing in the world to do since you will have to have someone on the EXACT SAME variant help you with this.
Re-flash TWRP. You'll need to find someone on the exact same XT1052 firmware (who also has TWRP) make a backup of JUST system and boot (not userdata).
They will share the backup with you, and you will flash it using TWRP (restore). That should fix you up -- it is the ONLY safe way to get back on track without downgrading and risking a brick..
Click to expand...
Click to collapse
Can anyone please help me with TWRP "backup of JUST system and boot" for XT1052 with stock 4.4.4 OTA (212.44.26.en.03)?
Hey All,
I was looking for a "Return to stock" guide but couldnt find any. Does anyone here know where I can find stock images perhaps?
Need to sent it back to the retailer and gotta have it stock.
Hope someone can help me.
Thanks!
nerotix said:
Hey All,
I was looking for a "Return to stock" guide but couldnt find any. Does anyone here know where I can find stock images perhaps?
Need to sent it back to the retailer and gotta have it stock.
Hope someone can help me.
Thanks!
Click to expand...
Click to collapse
What did you do to it that you can't manually undo?
_MetalHead_ said:
What did you do to it that you can't manually undo?
Click to expand...
Click to collapse
Nothing it all, I just unlocked bootloader like everyone else and rooted it. But now when I try to do it manualy I get 2 errors, I do this:
fastboot oem lock begin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
On the boot.img and recovery.img flash I get this error for both:
D:\android-sdk\sdk\platform-tools>mfastboot flash recovery recovery.img
sending 'recovery' (10280 KB)...
OKAY [ 0.370s]
writing 'recovery'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.596s
I also tried it with mfastboot, both didnt work.. and when I do fastboot oem lock I get :
D:\android-sdk\sdk\platform-tools>mfastboot oem lock
...
sst lock failure!
OKAY [ 0.026s]
finished. total time: 0.026s
If you didn't flash a custom recovery and kernel, there is no reason to try and flash recovery or boot. Just hit the unroot option in SuperSU, and relock the bootloader and you should be good to go.
_MetalHead_ said:
If you didn't flash a custom recovery and kernel, there is no reason to try and flash recovery or boot. Just hit the unroot option in SuperSU, and relock the bootloader and you should be good to go.
Click to expand...
Click to collapse
That's the thing.. if I type fastboot oem lock it says I must begin with fastboot oem lock begin and then start flashing signed files or something.
So I tried that but no luck.
Thx for your reply.
nerotix said:
That's the thing.. if I type fastboot oem lock it says I must begin with fastboot oem lock begin and then start flashing signed files or something.
So I tried that but no luck.
Thx for your reply.
Click to expand...
Click to collapse
That's weird, I've never heard of that before . It must be something unique to the X. Sounds like we need the stock boot and recovery images to relock the bootloader. Are the signed images even available to us yet? I have no clue...
nerotix said:
That's the thing.. if I type fastboot oem lock it says I must begin with fastboot oem lock begin and then start flashing signed files or something.
So I tried that but no luck.
Thx for your reply.
Click to expand...
Click to collapse
Sadly motorola hasn't put up any factory images on their website as far as i know. In their support forums they said they'll be coming up soon a month ago though. There's a tool posted on the Moto X dev forums which seemed to have a system.img and other images embedded, just read that up and see if it helps.
Alternatively, there's no real need for you to relock, most likely no one's gonna notice it. And if yours is not a pure edition they would know if they checked your imei if you have unlocked or not irrespective of you locking the bootloader or not. So the best and quick solution for you is to unroot, flash the logo.bin file posted on the Moto X dev forums so that you dont have any message showing up that you have unlocked the bootloader on starting up your device.
nexus 6 can not run the system, only the logo on the screen does not move
I tried to brush oem unlock firmware but failed.
I guess I broke the Recovery partition.
How can I do it? Help me!:angel::angel:
Please give a bit more detail about your setup and what happened before this
rootSU said:
Please give a bit more detail about your setup and what happened before this
Click to expand...
Click to collapse
I installed android 5.1.
root
Installed TWRP Recovery
Then I run "fastboot oem lock" this time we can not normally enter the system.
I found that running fastboot -w can enter the system, so I entered the "TWRP Recovery" to restore the backup method used to restore a backup Recovery partition.
So, let me get it straight...
You unlocked the bootloader
You then rooted
Installed recovery
THEN relocked the boot loader?
...why?
You won't be able to do anything to any partition until the boot loader is unlocked again - try that. Unlock the boot loader (make sure to enable it in Dev settings) and then it should all work again.
Good job, I think you bricked yourself.
Not sure if anyone found a work around for this.
http://forum.xda-developers.com/nexus-6/general/relock-bootloader-time-updating-to-5-1-t3053497
Leo D said:
nexus 6 can not run the system, only the logo on the screen does not move
I tried to brush oem unlock firmware but failed.
I guess I broke the Recovery partition.
How can I do it? Help me!:angel::angel:
Click to expand...
Click to collapse
If you have TWRP recovery installed and ONLY if you have TWRP installed, boot into bootloader. Issue the fastboot commands:
fastboot format userdata
fastboot format cache
If you do have TWRP installed, this should allow you to boot to TWRP recovery.
See if you can accomplish this and let us know.
Evolution_Freak said:
If you have TWRP recovery installed and ONLY if you have TWRP installed, boot into bootloader. Issue the fastboot commands:
fastboot format userdata
fastboot format cache
If you do have TWRP installed, this should allow you to boot to TWRP recovery.
See if you can accomplish this and let us know.
Click to expand...
Click to collapse
I went into recovery mode, nothing happens.
View Bootloader logs
Invalid boot image size!
failed to validate recovery image
Boot up failed
iRub1Out said:
So, let me get it straight...
You unlocked the bootloader
You then rooted
Installed recovery
THEN relocked the boot loader?
...why?
You won't be able to do anything to any partition until the boot loader is unlocked again - try that. Unlock the boot loader (make sure to enable it in Dev settings) and then it should all work again.
Click to expand...
Click to collapse
fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.028s
Options appear before acceptance and rejection does not appear on the phone screen.
You probably bricked it.
It's been known to happen after 5.1 if you're not careful (or, in this case, relock the BL after modifying)
Why did you relock it? I still can't wrap my head around any reason for doing that?
Sent from my Nexus 6
Leo D said:
fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.028s
Options appear before acceptance and rejection does not appear on the phone screen.
Click to expand...
Click to collapse
The phone is bricked. RMA to Motorola
Or if you're feeling adventurous: http://forum.xda-developers.com/showthread.php?t=3059518
brando56894 said:
Or if you're feeling adventurous: http://forum.xda-developers.com/showthread.php?t=3059518
Click to expand...
Click to collapse
Thanks for your help. But there are some questions I still do not understand.
Now the phone connected to the computer and did not see QHSUSB_BULK in Device Manager. In the Device Manager to see BootLoader interface or adb interfaces.
How can I make the phone run QHSUSB_BULK state?
I have the Moto Nexus 6 (xt1100) with TRWP installed no backup saved, OEM bootloader locked and no OS currently on the phone and i cant reflash nethunter or any stock roms through TRWP or fastboot. PLZ HELP ME OUT.
You could to install by adb sideload some full ota.
There is a Android N preview that could be applied by adb sideload, once you have access to your phone, you could unlock bootloader and apply any other rom
lulzwolf said:
I have the Moto Nexus 6 (xt1100) with TRWP installed no backup saved, OEM bootloader locked and no OS currently on the phone and i cant reflash nethunter or any stock roms through TRWP or fastboot. PLZ HELP ME OUT.
Click to expand...
Click to collapse
Push a custom rom to your phone and flash it in TWRP. Command: adb push namerom.zip /sdcard/, or sideload a custom rom in also in TWRP recovery. And don`t ever relock your bootloader again if you are flasher If you have enabled ENABLE OEM UNLOCK in developer options its best to unlock it first
gee2012 said:
Push a custom rom to your phone and flash it in TWRP. Command: adb push namerom.zip /sdcard/, or sideload a custom rom in also in TWRP recovery. And don`t ever relock your bootloader again if you are flasher If you have enabled ENABLE OEM UNLOCK in developer options its best to unlock it first
Click to expand...
Click to collapse
He can't flash any ROM with a locked bootloader.
You should be able to fastboot flash a stock image, but if your fastboot isn't working then you're kinda screwed.
All I can say is give the fastboot flash another try, maybe from a different PC. Use method 2 in this guide to return to stock, then use the stock recovery to factory reset and boot it up
noidea24 said:
He can't flash any ROM with a locked bootloader.
You should be able to fastboot flash a stock image, but if your fastboot isn't working then you're kinda screwed.
All I can say is give the fastboot flash another try, maybe from a different PC. Use method 2 in this guide to return to stock, then use the stock recovery to factory reset and boot it up
Click to expand...
Click to collapse
I tried Macon's method but i am still unable to flash the phone back to stock. The OEM bootloader is locked and i cant access it without an OS installed. Is there a way i can bypass the OEM bootloader aka hack/root the phone to reflash it?
It should work if you run these commands (with the phone in bootloader) prior to flashing the custom rom zip in TWRP:
Fastboot format cache
Fastboot format userdata
Didgeridoohan said:
It should work if you run these commands (with the phone in bootloader) prior to flashing the custom rom zip in TWRP:
Fastboot format cache
Fastboot format userdata
Click to expand...
Click to collapse
"""
Created filesystem with 11/16384 inodes and 2089/65536 blocks
sending 'cache' (6248 KB)...
writing 'cache'...
(bootloader) Unlock before flashing
"""
"""
Created filesystem with 11/1738080 inodes and 153124/6951904 blocks
sending 'userdata' (139061 KB)...
writing 'userdata'...
(bootloader) Unlock before flashing
"""
Im still locked out of the bootloader. how do i circumvent the OEM bootlock? can i hack pass it? it is password protected somewhere, if it is can i bruteforce the password? how can i get pass it guyz?!?!
The OEM bootloader is locked and i cant gain access to the developer optios because i dont have an OS to boot into. Im looking for a way i can "bypass" "circumvent" "hack" "disable" or any other word you can think of to get around the bootloader lock and flash my phone. i can start an "adb shell" and gain access to the command line on the phone, but i dont know where i can find the "OEM Bootloader" part of the phone for modification. I have also tried running "fastboot oem get_unlock_data" but it says "(bootloader) This command is not needed to unlock. Run fastboot oem unlock" WTF.... DAMMIT FUK FUK FUK FUUUUUUUUUUUUUUUUUUUUUUUUUUJK
"""
The command i used below and its output message.
"""
[email protected]# fastboot oem unlock
"""
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.005s
"""
lulzwolf said:
"""
Created filesystem with 11/16384 inodes and 2089/65536 blocks
sending 'cache' (6248 KB)...
writing 'cache'...
(bootloader) Unlock before flashing
"""
"""
Created filesystem with 11/1738080 inodes and 153124/6951904 blocks
sending 'userdata' (139061 KB)...
writing 'userdata'...
(bootloader) Unlock before flashing
"""
Im still locked out of the bootloader. how do i circumvent the OEM bootlock? can i hack pass it? it is password protected somewhere, if it is can i bruteforce the password? how can i get pass it guyz?!?!
Click to expand...
Click to collapse
Sorry to hear that... The suggested method used to work for people unable to unlock their bootloader due to not having the setting checked in developers settings (if they had TWRP installed, of course).
I do believe you are screwed...
@lulzwolf: Contact Motorola and/or Google, because you screwed yourself by not leaving "Enable OEM Unlock" checked after you modified the firmware. There is no way to brute force the lock, unless you happen to be immortal. The encryption on the bootloader is sufficiently strong that you'll be dead long before a computer could successfully unlock it.
Lesson of the day folks: if you modify your Nexus 6, even if only to root it, leave "Enable OEM Unlock" checked! Yes, it will make your device less secure since a knowledgeable person can flash a factory image, but it's better than being permanently locked out of the device.
Just flash any rom trough TWRP. For god's sake, it even supports MTP. What's your problem?
@Lawstorant: Did you read the thread? His bootloader is locked, meaning he cannot flash anything.
@Strephon Alkhalikoi
It doesn't work that way. Locked bootloader only means that he cannot flash anything using fastboot, but he clearly said that he has TWRP. TWRP doesn't relay on fastboot (common knowledge 1) because it's a totally seperate thing, hence locked bootloader doesn't affect TWRP in any way. He can still do anything he likes. The simplest solution is to flash ANY rom trough TWRP and unlock bootloader with "Boot unlocker" app.
Locked bootloader means you cannot use fastboot, partitions are not unaccesible.
1. If you lock your Windows OS with password you can't acces it, but if you have Linux there's nothing that prevents you from browsing filse on windows partition (only encryption, but still, you can wipe it and put in, anything you want).
TL;DR You're wrong, go learn some more.
@Lawstorant, your attitude and tone need a bit of adjustment. If I am wrong, that's one thing. There is however no need to be a smart ass about it, especially with the TL;DR bit. It's juvenile, and uncalled for. That said, you are correct in that lulzwolf may not be totally screwed. Virtually everyone, including myself, has assumed he has to flash a stock image, but he really doesn't. We'll need him to answer one way or another, but the instructions to restore his device are as follows.
Boot into bootloader.
Use fastboot and issue the following commands: fastboot format userdata, fastboot format cache.
Reboot into TWRP.
Flash a custom ROM.
Unlock the bootloader, and leave it unlocked.
lulzwolf did in fact get at least as far as the two fastboot commands, but he does not say whether he got back into TWRP. Now that he has gotten the userdata and cache formatted he should be able to boot into TWRP and install a custom ROM. From there he should be able to unlock the bootloader.
So @lulzwolf, where are you getting stuck? You may not be done yet, as I erroneously assumed.
@Lawstorant: Did you read the thread? His bootloader is locked, meaning he cannot flash anything.
Click to expand...
Click to collapse
no need to be a smart ass about it,
Click to expand...
Click to collapse
formating trough fastboot won't succed, because he needs access to these partitions. Why would anyone even recommend fastboot when bootloader is locked? He's better of formatting them trough TWRP.
TWRP is answer to all questions. I don't even know why he's tinkering with his phone if he can't figure it out on his own.
Ask The_Merovingian. He wrote the guide. I simply copied it from his thread.
However, you and I do agree on one very important thing. If he doesn't know what he's doing he shouldn't be messing about with his phone, period. He did say in his opening post that he couldn't flash ROMs through TWRP, but given what's been posted, there shouldn't be any reason he can't flash a ROM, except he has a bigger issue than not having the OS.
Ok so i have solved my problem by installing a custom ROM called "Cataclysm" through the TRWP recovery tool. My problem was I tried flashing to stock with fastboot when fastboot had no access to the partitions. so i used adb to push a custom ROM and installed it in TRWP.... BOOM it was fixed! so in conclusion we have learned that fastboot cannot access partitions while the OEM bootloader is locked but TRWP can. thank you all for commenting and helping me out, and hopefully this thread can help out others who run across this problem in the future.
lulzwolf said:
I have the Moto Nexus 6 (xt1100) with TRWP installed no backup saved, OEM bootloader locked and no OS currently on the phone and i cant reflash nethunter or any stock roms through TRWP or fastboot. PLZ HELP ME OUT.
Click to expand...
Click to collapse
rofl, way to go
lulzwolf said:
Ok so i have solved my problem by installing a custom ROM called "Cataclysm" through the TRWP recovery tool. My problem was I tried flashing to stock with fastboot when fastboot had no access to the partitions. so i used adb to push a custom ROM and installed it in TRWP.... BOOM it was fixed! so in conclusion we have learned that fastboot cannot access partitions while the OEM bootloader is locked but TRWP can. thank you all for commenting and helping me out, and hopefully this thread can help out others who run across this problem in the future.
Click to expand...
Click to collapse
Which is exactly what gee2012 suggested that you should do in the second reply to your cry for help. (And at least I assumed you had tried without success. Serves me right for assuming...)
Glad it worked out. :good:
I hope you learned more than just that from this exercise. I know I did, namely a reminder to "practice what I preach". I tell people like you to search before posting and I failed to do just that. Mea culpa.
Long story short, woke up with my N6 stuck at the bootloader screen and cannot do anything at it. I can only see my serial number and if I try anything else, it reloads bootloader. I am trying to flash back to a stock 6.0.1 image, however I keep getting this error while trying to do so.
C:\Program Files (x86)\Android\android-sdk\platform-tools> fastboot flash bootloader bootloader-shamu-moto-apq8084-71.15.img
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (10387 KB)...
OKAY [ 0.332s]
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: 11.542s
I have tried Nexus Root Toolkit, tried flashing all and tried flashing each image one by one but I still get this "(bootloader) Failed to flash partition FAILED (remote failure)" on all attempts. Phone does show up if I try fastboot devices, and I have tried this on two different computers. Device is also unlocked as well, and I even tried flashing older versions of Lolipop but they all give me the same error. Drivers work fine, and I have everything up to date in terms of bootloader and Andriod SDK. I am starting to think that there is physical damage inside the phone, however I do not know how or why this occurred randomly. Any help would be awesome, as I am very new to flashing images onto my phone and frankly I am 99% sure that my warranty is out, and I really don't want to pay $175 cost .
You can try to use minimal adb and fastboot drivers, unpack for example latest npreview 5 factory Image into same folder and flash each .IMG step by step with cmd window, i always flash this way, if everything else fails.
http://forum.xda-developers.com/showthread.php?t=2317790
And here method 2:
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
May this helps you
coremania said:
You can try to use minimal adb and fastboot drivers, unpack for example latest npreview 5 factory Image into same folder and flash each .IMG step by step with cmd window, i always flash this way, if everything else fails.
http://forum.xda-developers.com/showthread.php?t=2317790
And here method 2:
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
May this helps you
Click to expand...
Click to collapse
I've already tried method 2 before so I tried method 1 with the program, and it gives me the same exact error as before. Thanks for the help though, it was worth a shot!
Are you able to enter twrp ? Try to reflash Bootloader through twrp
coremania said:
Are you able to enter twrp ? Try to reflash Bootloader through twrp
Click to expand...
Click to collapse
I did not have TWRP installed on my phone since I had it completely stock and unrooted, so I tried installing it in the hopes of that some chance it would work and I could access it. Still getting the same error as before (grumble grumble). It is starting to look like more of a physical problem to me, but thanks for the advice. Here is what I got...
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (11585 KB)...
OKAY [ 0.468s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 6.380s
Bootloader is unlocked i guess, may your Bootloader is messed up, did you try to flash only one Factory Image ? Corrupt Download possible ?
What happens if you try unlock command
Try to flash the latest full ota with these steps.
https://developers.google.com/android/nexus/ota
Since you already in the bootloader, select recovery and fpllow the steps from there.
blanco2701 said:
Try to flash the latest full ota with these steps.
https://developers.google.com/android/nexus/ota
Since you already in the bootloader, select recovery and fpllow the steps from there.
Click to expand...
Click to collapse
This was going to be my suggestion!!
Sent from my Nexus 6 using XDA-Developers mobile app
coremania said:
Bootloader is unlocked i guess, may your Bootloader is messed up, did you try to flash only one Factory Image ? Corrupt Download possible ?
What happens if you try unlock command
Click to expand...
Click to collapse
Any image I even try to flash I get the error with, no matter what order or which one I pick. I redownloaded the image again and still nothing, so I don't think it's a corrupt download. What is the unlock command? Sorry for being a noob, never heard of it since all my knowledge is from reading tons of flashing guides on the internet lol.
blanco2701 said:
Try to flash the latest full ota with these steps.
https://developers.google.com/android/nexus/ota
Since you already in the bootloader, select recovery and fpllow the steps from there.
Click to expand...
Click to collapse
Alright, I downloaded the OTA file and got the process to about 47% when suddenly I keep running into the error of "E:Can't open /cache/recovery/log" then followed by more things it can't open. I tried the OTA twice and it gets stuck on that same exact spot. I tried the wipe data/factory reset option from the recovery mode and I get a similar error of "Can't mount", "Can't open", "failed to mount" the recovery log. It seems like there is a problem with the recovery log files (or the folder) on my phone, but I have no idea what that means. I will mess around with some more and try Googling the source of error, but thank you for the help.
fastboot oem unlock
With this command you can unlock your Bootloader, better read here
first http://forum.xda-developers.com/showpost.php?p=56938530&postcount=1 , if have 47% done, may you can use twrp now. Good luck
Did you try the erase function from bootloader that may or may not help??
Sent from my Nexus 6 using XDA-Developers mobile app
coremania said:
fastboot oem unlock
With this command you can unlock your Bootloader, better read here
first http://forum.xda-developers.com/showpost.php?p=56938530&postcount=1 , if have 47% done, may you can use twrp now. Good luck
Click to expand...
Click to collapse
Oh yes, my device has already been unlocked from the start so that wasn't a problem. I still get the same error when I try to flash anything, including TWRP which means I have to install the OTA. The problem is a get a separate error when I try to install the OTA, which the only solution being to flash my device (or at least that is what most people have been saying when I googled the can't open cache recovery error) so this is a giant goose chase which leads me back to the start :/. I will keep trying however, I refuse to give up after going this far!
holeindalip said:
Did you try the erase function from bootloader that may or may not help??
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Should I try fastboot erase cache and then fastboot format cache? Would refresh the cache on there? I only just learned the erase command so I am not exactly sure what I should try.
Should be able to erase any partition if your unlocked
http://androidforums.com/threads/list-of-fastboot-command.714676/
Sent from my Nexus 6 using XDA-Developers mobile app
I don't know the commands to erase everything from the bootloader but I would try this:
Flash latest twrp and boot into recovery.
Assuming you don't care about anything that's on the phone, go to advance wipe and wipe EVERYTHING lol... reboot into bootloader and try to flash everything from scratch. If this doesn't work, I'll guess your phone have problems.
holeindalip said:
Should be able to erase any partition if your unlocked
http://androidforums.com/threads/list-of-fastboot-command.714676/
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
I get the same failure error while trying to format and erase, so I am guessing something is really wrong with my phone or the bootloader is messed up beyond repair. I guess it could be the cable I am using as well, that is one thing I did not take into factor so I will try with another cable if I find a spare. Flashing might be beyond my solution at this rate though... Thanks anyways for the help.
blanco2701 said:
I don't know the commands to erase everything from the bootloader but I would try this:
Flash latest twrp and boot into recovery.
Assuming you don't care about anything that's on the phone, go to advance wipe and wipe EVERYTHING lol... reboot into bootloader and try to flash everything from scratch. If this doesn't work, I'll guess your phone have problems.
Click to expand...
Click to collapse
I really should have had TWRP installed before I guess lol, but I still get the same failure error. My phone has more problems than a teenager going through puberty I swear, thanks for the help though.
Yes try another cable, if it stops at 47%, the Bootloader should be replaced. May try everything without simcard, don't ask me why, i read something similiar in a Moto forum
fastboot erase recovery doesn't help ?
---------- Post added at 19:58 ---------- Previous post was at 19:34 ----------
http://forum.xda-developers.com/nexus-6/general/to-save-bricked-nexus-device-t3334660 otherwise try this, but read completely first, adb sideload with a npreview ota rom may help you.
coremania said:
Yes try another cable, if it stops at 47%, the Bootloader should be replaced. May try everything without simcard, don't ask me why, i read something similiar in a Moto forum
fastboot erase recovery doesn't help ?
---------- Post added at 19:58 ---------- Previous post was at 19:34 ----------
http://forum.xda-developers.com/nexus-6/general/to-save-bricked-nexus-device-t3334660 otherwise try this, but read completely first, adb sideload with a npreview ota rom may help you.
Click to expand...
Click to collapse
I tried it with another wire and nothing changed, and then I tried taking out my sim card and trying it.... and it worked! It flashed everything normally and loaded up just fine. I don't know whether I should be furious or happy but thank you and everyone who helped. Who would have known just taking out the sim card could have saved me 2+ days of stressing and trail and error. Once again thanks, you really saved me lol.
You're welcome, nice your phone works again !
Don't forget to activate oem unlock and debugging in the Developer options, and flash twrp, so maybe more save for upcoming problems
skipsoft android toolkit maybe help you in future