Trying to root mate s and failed
got this massage :
sending 'recovery' (24454 KB)...
OKAY [ 0.522s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.523s
How to fix "FAILED (remote: Command not allowed)"
can any one help?
it looks like your boogloader is locked..
so you need to unlock the bootloader first before you can flash anything..
search around the threads for getting the unlock code and how to..
Gesendet von meinem HUAWEI CRR-L09 mit Tapatalk
blueIBI said:
it looks like your boogloader is locked..
so you need to unlock the bootloader first before you can flash anything..
search around the threads for getting the unlock code and how to..
Gesendet von meinem HUAWEI CRR-L09 mit Tapatalk
Click to expand...
Click to collapse
I think that is right
I tried to unlock bootloader through Huawei site but failed to did that
their site unlocking page is not working in the last stage
I cannot get another way to do this
thank you
unfortunately there is no other way..
if you are licky you can try the "U" method..
search around the forum how to do this..
Gesendet von meinem HUAWEI CRR-L09 mit Tapatalk
Finally I got the unlock code from China site:
http://emui.huawei.com/plugin/hwdownload/download
It is working
and did the root by this way :
http://forum.xda-developers.com/mate-s/general/how-to-crr-609-proper-root-mm-b321-t3387887
every thing is OK by now
Thank you
Related
Hey all, after a couple of tutotials I came to a conclusion that trying to remove the unlocked bootloader screen bricks my phone everytime with the flash failure error...
Right now i'm unable to use my phone, since it is bricked, and i'm trying to flash it to work.
Any ideas why I can't change the boot screen? It keeps giving me this none signed image error
EDIT: Can't seem to make it work at all now. Is there a way to erase everything from the phone and flash a new ics?
I could be wrong, but I thought I read someone saying that this was possible with ICS, but with JB this has been locked/disabled from modification.
AW: [Q] Razr i bootloader unlock screen help
Download an JB Fastboot and flash the ulogo back > problem solved.
Gesendet von meinem XT890 mit Tapatalk 2
---------- Post added at 11:56 PM ---------- Previous post was at 11:41 PM ----------
Edit: If you're still on ICS forget the part about the JB Fastboot and grap this one.
http://forum.xda-developers.com/showthread.php?p=36437955
Gesendet von meinem XT890 mit Tapatalk 2
Hello, i got a question if some one more has this problem, when i try to unlock the bootload from sonys site,
http://developer.sonymobile.com/unlockbootloader/
when i use fastboot devices i found my device.
Next step is the code for the unlockboot load
C:\sdk\platform-tools>fastboot -i 0x0fce oem unlock ***************
...
FAILED (remote: Command not allowed)
finished. total time: 0.005s
C:\sdk\platform-tools>but why do i get FAILED commando not allowed some one know the answer please help me.
oem unlock
you must in developer setings allow "unlock oem"
GameboyZA said:
you must in developer setings allow "unlock oem"
Click to expand...
Click to collapse
And turn off my Xperia
Sent from my Xperia XA using XDA Labs
His bootloader could be carrier locked the even changing oem unlock it will still not unlock and will give error
Sent from my F8131 using Tapatalk
GameboyZA said:
you must in developer setings allow "unlock oem"
Click to expand...
Click to collapse
i think that will work the settings was off, so i will try again to day
i just tried this to day and now i got this error
FAILED (remote: Command did not succeed)
finished. total time: 0.042s
In 5 Days comes my New Huawei P9 at Home. Can I root the Device without Unlock Bootloader or Unlock requaire.
I dont wanna flash Roms how the Last Years with all my Devices ia want just Root
Gesendet von meinem Pixel mit Tapatalk
I didnt manage to root P9 without unlocking bootloader and flashing recovery as twrp. Only then i was able to root p9 (eva-L19)
Hi guys ,,
I have P10 Lite and I went ask Can I Flash Custom Recovery "TWRP" Without unlock Bootloader ?
Thanxs
Without unlocked BL you are not able to flash anything. Although I do not know exactly if this is true but the allow unlocking option in develeoper settings should be the answer..
Gesendet von meinem VTR-L09 mit Tapatalk
freibergisch said:
Without unlocked BL you are not able to flash anything. Although I do not know exactly if this is true but the allow unlocking option in develeoper settings should be the answer..
Gesendet von meinem VTR-L09 mit Tapatalk
Click to expand...
Click to collapse
thanks bro for answer me
But i have problem if i unlocked BL i cant lock again my phone enter in loop boot only
i think i need flash stock boot.img and Recovery.img then lock again ? right!
This could be possible. Flash them and turn on the unlock option. Then you should be able to flash whatever you want to.
Gesendet von meinem VTR-L09 mit Tapatalk
Hi guys
I just succeed to unlock with potatoNV my ale L21.
but, its looks like there is no twrp for the 2015 version?
Im having this last one and it looks like 99% of xda regarding ale_L21/p8Lite towards 2017 version.
Isnt it possible to know how to switch to twrp/lineage with 2015 hw version?
I tried lot of twrp files regarding "looks like" 2017 ver (none says 2015, so I guess it's 2017):
FAILED (remote: image verification error)
fastboot oem lock-state info
...
(bootloader) FB LockState: UNLOCKED
(bootloader) USER LockState: UNLOCKED
OKAY [ 0.000s]
finished. total time: 0.000s
I thank you vm
lm8lm8 said:
Hi guys
I just succeed to unlock with potatoNV my ale L21.
but, its looks like there is no twrp for the 2015 version?
Im having this last one and it looks like 99% of xda regarding ale_L21/p8Lite towards 2017 version.
Isnt it possible to know how to switch to twrp/lineage with 2015 hw version?
I tried lot of twrp files regarding "looks like" 2017 ver (none says 2015, so I guess it's 2017):
FAILED (remote: image verification error)
fastboot oem lock-state info
...
(bootloader) FB LockState: UNLOCKED
(bootloader) USER LockState: UNLOCKED
OKAY [ 0.000s]
finished. total time: 0.000s
I thank you vm
Click to expand...
Click to collapse
I run into the same problem and managed to fix this. You have to run the potatoNV again, keeping the testpoint shorten during the reboot, and DO NOT check the "unlock FB" checkbox this time. This checkbox actually effectively locks the bootloader.