i only got to the stage of unlocking the phone. didnt know how to isntall the rom for oxygenos with magisk.
now my phone is unlock i want to lock it because i want to use gpay.
i tried to use the command fastboot oem lock. it said: failed (remote: unknown command)
finished. total time: 0.001s
any help please?
don't unless you want to roll the dice on bricking.
just install safetynet fix
grand_deluxe said:
i only got to the stage of unlocking the phone. didnt know how to isntall the rom for oxygenos with magisk.
now my phone is unlock i want to lock it because i want to use gpay.
i tried to use the command fastboot oem lock. it said: failed (remote: unknown command)
finished. total time: 0.001s
any help please?
Click to expand...
Click to collapse
you have to use this adb command: fastboot flashing lock
Good luck
g96818 said:
don't unless you want to roll the dice on bricking.
just install safetynet fix
Click to expand...
Click to collapse
U won't brick relocking if nothing was altered in the system or the phone is back to factory state.
the_rooter said:
U won't brick relocking if nothing was altered in the system or the phone is back to factory state.
Click to expand...
Click to collapse
Tell that to those who have bricked with everything back to a factory state.
g96818 said:
Tell that to those who have bricked with everything back to a factory state.
Click to expand...
Click to collapse
And I will obviously they didn't take the time to make sure everything was back to stock and the system was unchanged... if u relocate your bootloader and it bricked...that's the cause of user error.
Related
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.
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?
Hi everyone,
i've the phone can only go into eRecovey and fastboot. I think that the corrupted file is oeminfo.bin, bacause i was replaced with file explorer to have the exact version of the firmware.
Recovery i've tried to download by wifi the firmware, but when install return with authentication info failed error red exclamation dot. I've tried with full wipe but after reboot it return into eRecovery.
Into fastboot return with FAILED (remote: Command not allowed).
Bootloader after update was began locked and i cannot unlock, so TWRP is cutted out.
There's some method to flash the .img system etc like odin for samsung?
i've also the old version of oeminfo.bin on my PC, if i have a method to flash it trough ADB, but i don't know how to unbrick.
Thanks
frencisis said:
Hi everyone,
i've the phone can only go into eRecovey and fastboot. I think that the corrupted file is oeminfo.bin, bacause i was replaced with file explorer to have the exact version of the firmware.
Recovery i've tried to download by wifi the firmware, but when install return with authentication info failed error red exclamation dot. I've tried with full wipe but after reboot it return into eRecovery.
Into fastboot return with FAILED (remote: Command not allowed).
Bootloader after update was began locked and i cannot unlock, so TWRP is cutted out.
There's some method to flash the .img system etc like odin for samsung?
i've also the old version of oeminfo.bin on my PC, if i have a method to flash it trough ADB, but i don't know how to unbrick.
Thanks
Click to expand...
Click to collapse
Run these commands in fastboot and report back
fastboot oem get-product-model
fastboot getvar vendorcountry
danifilth4king said:
Run these commands in fastboot and report back
fastboot oem get-product-model
fastboot getvar vendorcountry
Click to expand...
Click to collapse
Thanks, the resuls are:
C:\adb>fastboot devices
LCL0218428003429 fastboot
C:\adb>fastboot oem get-product-model
...
FAILED (remote: FAIL)
finished. total time: 0.006s
C:\adb>fastboot getvar vendorcountry
getvar:vendorcountry FAILED (remote: cannot get vendorcountry in oeminfo)
finished. total time: 0.011s
C:\adb>
frencisis said:
Thanks, the resuls are:
C:\adb>fastboot devices
LCL0218428003429 fastboot
C:\adb>fastboot oem get-product-model
...
FAILED (remote: FAIL)
finished. total time: 0.006s
C:\adb>fastboot getvar vendorcountry
getvar:vendorcountry FAILED (remote: cannot get vendorcountry in oeminfo)
finished. total time: 0.011s
C:\adb>
Click to expand...
Click to collapse
As your normal eRecovery method isn't working you could try using the FunkyHuawei eRecovery method to flash firmware but you'd have to pay for credits and there's no guarantee it would work. Problem is knowing which firmware to choose as we don't know if your rebrand was successful.
You could try a firmware that matches what your model and region of your phone was originally and if that doesn't work try the firmware meant for the model/region you were trying to rebrand to?
Other than that I'm out of ideas if you can't unlock your bootloader :/
danifilth4king said:
As your normal eRecovery method isn't working you could try using the FunkyHuawei eRecovery method to flash firmware but you'd have to pay for credits and there's no guarantee it would work. Problem is knowing which firmware to choose as we don't know if your rebrand was successful.
You could try a firmware that matches what your model and region of your phone was originally and if that doesn't work try the firmware meant for the model/region you were trying to rebrand to?
Other than that I'm out of ideas if you can't unlock your bootloader :/
Click to expand...
Click to collapse
I've tried to contact Funky Huawei, but they answered to me that: "Unfortunately in your situation recovery might not be possible".
So the last one is to try with warranty into Huawei service.
I hope they could repair it with less money as possible. Maybe they will replace the main board or just re flash he firmware with special method?:crying:
not possible to flash firmware in downloade mode?
mrt box
elvis87 said:
mrt box
Click to expand...
Click to collapse
Have you seriously just answered a 2 years old thread?..
Dude, I have the same problem with a P20 Pro since january!
Usb-c pendrive with proper firmware did the trick for me last time. Nothing else worked. Erecovery is useless crap.
deucecorp said:
Usb-c pendrive with proper firmware did the trick for me last time. Nothing else worked. Erecovery is useless crap.
Click to expand...
Click to collapse
Can I pm you for details?
Hello all,
I think I messed my Nexus 6 badly.
I stupidly re locked the bootloader, then did a factory wipe in TWRP.
So there is no more way the phone boot to configure 'Allow OEM Unlock' in Developer Options
So I'm stuck:
C:\SDK\android-sdk-windows\platform-tools>fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.003s
C:\SDK\android-sdk-windows\platform-tools>
Any Idea ???
Please help
Thanks
Pas
Can you still boot to TWRP?
Deleted
runekock said:
Can you still boot to TWRP?
Click to expand...
Click to collapse
Thanks for replying.
It's on Stock recovery now.
But in TWRP flashing always fails because the bootloader is locked.
now I need to unlock the bootloader but how if "fastboot oem unlock" does not work
it give the FAILED (remote failure)
When the phone reboot it's stuck with a white Google display and nothing happen.
If you're on the stock recovery, installing the final OTA update (N8I11F) should get your device up and running so you can then enable OEM Unlocking in Android.
Strephon Alkhalikoi said:
If you're on the stock recovery, installing the final OTA update (N8I11F) should get your device up and running so you can then enable OEM Unlocking in Android.
Click to expand...
Click to collapse
Yes, the OTA update did it.
Installed fine with the ADB sideload option in stock recovery .
It finally boot up to enable OEM Unlocking
Thanks a lot
Best
Pas