Related
Hello I'm trying to flash stock ROM via adb, specifically cust.img, boot.img, system.img, Because I've bricked my phone and it stuck on huawei logo, but when i try to flash, i got the following error "FAILED (remote: Command not allowed)"
Code:
C:\adb>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (304183 KB)...
OKAY [195.875s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 195.899s
c:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (21690 KB)...
OKAY [ 13.671s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 13.694s
c:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [314.622s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 314.665s
Please how I can unbrick my phone and reinstall the firmware
Obs. My bootloader is unlocked and I'm using TWRP recovery
Is your phone really shows Unlocked in red color when it's in fastboot mode?
Was your phone rooted, if yes, with which method?
You should try doing:
fastboot erase cache
fastboot erase userdata
These commands perform the same thing as Factory Reset do.
If it's not working, try to do the "dload" method with your original firmware your phone was shipped with.
Create a folder, called "dload" in your sdcard root, put the UPDATE.APP file of the firmware in it, and without connecting it to PC, press Vol + and Vol - and Power button until it starts flashing the firmware, and see what happens.
In later days, we've got a lot of troubleshooting topic opened up with your problem, the users cannot flash even with unlocked bootloader, and yet, there's no real solution to them.
I suggest that you use Windows 10? If I'm right sometimes this version of Windows cannot be used to flash via adb
I recommend you to use Windows 8.1 or 7 . My best way is of course using Linux
daviddosa said:
Is your phone really shows Unlocked in red color when it's in fastboot mode?
Was your phone rooted, if yes, with which method?
You should try doing:
fastboot erase cache
fastboot erase userdata
These commands perform the same thing as Factory Reset do.
If it's not working, try to do the "dload" method with your original firmware your phone was shipped with.
Create a folder, called "dload" in your sdcard root, put the UPDATE.APP file of the firmware in it, and without connecting it to PC, press Vol + and Vol - and Power button until it starts flashing the firmware, and see what happens..
Click to expand...
Click to collapse
Yes, it shows PHONE unlocked in red name, and I've made the root using an app called kingroot
I've tried to erase cache and userdata using adb but I can't, still got the same error "FAILED (remote: Command not allowed)"
I can't make dload method because I don't have stock recovery, and I can't flash the stock recovery using adb because its keep saying "FAILED (remote: Command not allowed)".
I don't know what to do
sokkoban said:
I suggest that you use Windows 10? If I'm right sometimes this version of Windows cannot be used to flash via adb
I recommend you to use Windows 8.1 or 7 . My best way is of course using Linux
Click to expand...
Click to collapse
I'm using windows 7 is this moment, maybe I try to flash using Linux later
Seems like all the guys with the same problem used KingRoot to root...that is the common thing amongst all.
I dont't think you need the stock recovery to update via the "dload" method, but I'm not sure.
If you don't have your original firmware's UPDATE.APP yet, download it, as well as the Huawei Update Extractor.
Load your file into the program, select ONLY BOOT.IMG, CUST.IMG(if it has one), SYSTEM.IMG and RECOVERY.IMG(optional, if selected, restores original recovery) right click on one, and press Create Flashable Zip.
Copy this to your sdcard and try to flash it.
I did not thest this above method, and don't know it the created flashable zip is really flashable, but I'm running out of possible solutions slowly.
Let us know what happens.
daviddosa said:
Seems like all the guys with the same problem used KingRoot to root...that is the common thing amongst all.
I dont't think you need the stock recovery to update via the "dload" method, but I'm not sure.
If you don't have your original firmware's UPDATE.APP yet, download it, as well as the Huawei Update Extractor.
Load your file into the program, select ONLY BOOT.IMG, CUST.IMG(if it has one), SYSTEM.IMG and RECOVERY.IMG(optional, if selected, restores original recovery) right click on one, and press Create Flashable Zip.
Copy this to your sdcard and try to flash it.
I did not thest this above method, and don't know it the created flashable zip is really flashable, but I'm running out of possible solutions slowly.
Let us know what happens.
Click to expand...
Click to collapse
So I tried to create a flashable zip using the Huawei Update Extractor however, was not possible, it's showing the following message "no suitable files selected. Check profiles.xml"
I've tried also creating flashable zip manually and flash it using TWRP, but TWRP reboot every time I try to flash theses files, that's why I think dload method work only with stock recovery
Hello,
I created the script for flash via fastboot if you want try this method
Extract BOOT.img, Cust.img, Recovery.img, System.img and copy to fastboot folder.(attachment)
Enable developer options and USB debugging
Simply run file FLASH-ALL.bat file
sokkoban said:
Hello,
I created the script for flash via fastboot if you want try this method
Extract BOOT.img, Cust.img, Recovery.img, System.img and copy to fastboot folder.(attachment)
Enable developer options and USB debugging
Simply run file FLASH-ALL.bat file
Click to expand...
Click to collapse
Thanks for the help but this method didn't work, everytime I try to flash the files, I got the same error "FAILED (remote: Command not allowed)” I don't know what is happening my bootloader is unlocked, why I can't flash the files with adb
Code:
target max-download-size: 450MB
sending 'boot' (21690 KB)...
OKAY [ 13.912s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 13.919s
target max-download-size: 450MB
sending 'recovery' (34264 KB)...
OKAY [ 21.963s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 21.985s
target max-download-size: 450MB
sending 'cust' (304183 KB)...
OKAY [191.580s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 191.603s
target max-download-size: 450MB
Sparse-Flash is enabled!
sending sparse 'system' (460798 KB)...
OKAY [366.120s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 366.144s
ROM flashed , if all went well
You must be restarted.
If you leave the recovery to hard reset and restart the phone
Created by sokoban. Thank you for using my release
rebooting...
finished. total time: 0.054s
Pressione qualquer tecla para continuar. . .
This is very strange. May be you really have locked bootloader
Post answer from this command in fastboot mode:
Code:
fastboot oem get-bootinfo
sokkoban said:
This is very strange. May be you really have locked bootloader
Post answer from this command in fastboot mode:
Code:
fastboot oem get-bootinfo
Click to expand...
Click to collapse
This was the result
Code:
C:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
As you can see the ADB says that the bootloader is unlocked, but I'm still having trouble
Same issue with Huawei G6-U10
I'm having the same problem with Huawei Ascend G6-U10
Currently running on ROM b146, since it has some issues I was trying to downgrade or upgrade ( there is a b330 out).
I'm not an expert.
This morning I've unlocked the boot loader and then tried to flash a couple of different ROMs and I always get the same error message:
c:\adb>fastboot flash BOOT ./G6-U10verb330/boot.img
target reported max download size of 536870912 bytes
sending 'BOOT' (9696 KB)...
OKAY [ 0.310s]
writing 'BOOT'...
FAILED (remote: Command not allowed)
finished. total time: 0.321s
c:\adb>fastboot oem get-bootinfo
(bootloader) Bootloader Lock State: UNLOCKED
(bootloader) System State: Bootloader in UNLOCKED state
(bootloader) Bootloader Version: 001.001.000
I'm guessing this is not a G6-U10 specific issue so if anyone can give any hint it'll be very appreciated.
Thanks.
I have the same problem with a honor 4x.
Rooted with kingroot. We haven't writing permission in /system. That's why we can't install the recovery. If you try to install superSU and update the binary I guess you get an error.
Now the question is: how we can do to make writeble /system with fast boot?
"mount -o rw,remount -t ext3 /dev/block/xxxxxxxxx /system" in terminal doesn't work...
Similar thing happened to me. Even if command for showing unlocked bootloader said it was unlocked that was false because I used Kingroot previously. Only thing that helped was to unlock the bootloader through fastboot again. Then it was really unlocked and I could flash recovery (in my case TWRP) which before I was unable to.
Diego Sousa said:
This was the result
Code:
C:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
As you can see the ADB says that the bootloader is unlocked, but I'm still having trouble
Click to expand...
Click to collapse
Have you tried it with linux yet?
And have you used the Update.APP and dload method?
Maybe a driver problem? Have administrator rights? And debug mode on?
Try to connect your phone (power on) to the pc and wait to be recognized. In cmd type this:
Code:
adb devices
It has to show you your serial number right? If doesn't your device is not being recognized by adb.
Next type:
Code:
adb reboot-bootloader
This will restart your phone into fastboot and now you can type "fastboot devices" like first command and it has to show you your serial number again.
Try rebooting into bl with this, not by plugin in the phone, and install the rom again
Huawei P8 Lite
Hello I have a problem with my phone. I do not know how to hell I fix it.
It says error cannot load system.img but still I can install boot.img and others.
I¨d tryed that "dload" with update.app doesnt work.
phone is Huawei P8 Lite
this is my first time here
Have you tried install it in twrp? You don't have a twrp backup of stock rom?
In this case if you go in the Huawei eRecovery you can restore stock rom and twrp will be overwrited downloading the last rom , i tried it with my p8 lite 2017 .
Tuki2 said:
Hello I have a problem with my phone. I do not know how to hell I fix it.
It says error cannot load system.img but still I can install boot.img and others.
I¨d tryed that "dload" with update.app doesnt work.
phone is Huawei P8 Lite
this is my first time here
Click to expand...
Click to collapse
What are you using to go into fastboot mode? Is it ADB from Android SDK?? It turns out that using ADB from Android SDK lets you flash small files but not large files... I suggest you try flashing the file through Minimal ADB & Fastboot
sokkoban said:
Hello,
I created the script for flash via fastboot if you want try this method
Extract BOOT.img, Cust.img, Recovery.img, System.img and copy to fastboot folder.(attachment)
Enable developer options and USB debugging
Simply run file FLASH-ALL.bat file
Click to expand...
Click to collapse
i have the same issue as well, but just with Cust.img
I'm new to XDA and flashing my Nexus, I had a buddy of mine unlock and flash a custom ROM on my device. I'm working on getting my system to stock and upgrading to Android 'N'. I followed the guide http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 I had success in flashing all the images one time and rebooted the device. Only to find that it will not start so I loaded up the bootloader once again, checking recovery, still nothing. Now I'm rerunning the flash process everything runs fine all the way up to flashing vender.img
Code:
C:\SDK\platform-tools>fastboot flash vender C:\Angler\Images\vendor.img
target reported max download size of 494927872 bytes
sending 'vender' (185129 KB)...
OKAY [ 4.528s]
writing 'vender'...
FAILED (remote: Permission denied!)
finished. total time: 4.544s
This is where I'm stuck. Thanks for any help on this matter.
Hey, no problem bro! It's called vendor, not vender, and the command is: fastboot flash vendor etc. This should solve your problem (Sorry for my english)
NHagney said:
I'm new to XDA and flashing my Nexus, I had a buddy of mine unlock and flash a custom ROM on my device. I'm working on getting my system to stock and upgrading to Android 'N'. I followed the guide http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 I had success in flashing all the images one time and rebooted the device. Only to find that it will not start so I loaded up the bootloader once again, checking recovery, still nothing. Now I'm rerunning the flash process everything runs fine all the way up to flashing vender.img
Code:
C:\SDK\platform-tools>fastboot flash vender C:\Angler\Images\vendor.img
target reported max download size of 494927872 bytes
sending 'vender' (185129 KB)...
OKAY [ 4.528s]
writing 'vender'...
FAILED (remote: Permission denied!)
finished. total time: 4.544s
This is where I'm stuck. Thanks for any help on this matter.
Click to expand...
Click to collapse
I'm a Linux guy so you may wish to take this with a grain of salt. I have a vague memory of the same error and it was a case of a misspelled and/or miscapitalized command. I am assuming 2 things -
1) everything has worked up to this point
2)the code presented is exactly what you typed on your computer
Your error may simply be that your misspelled vendor after "fastboot flash"
Thats what i get for being hung over. I'm over here trying to run this as admin all kinds of nonsense. Wondering why this went so smooth last night now running into this. I still don't have a working device. After restarting the device I don't get the OS only the initial google screen. Edit: nevermind. It just posted. TY guys. On to Android 'N' maybe Nuttybar?
I want to install cm13 because I'm tired of using the buggy stock ROM. I have the right driver installed but when I enter fastboot mode the phone is not recognised. Can any1 tell me how to fix this?
SaraKumar said:
I want to install cm13 because I'm tired of using the buggy stock ROM. I have the right driver installed but when I enter fastboot mode the phone is not recognised. Can any1 tell me how to fix this?
Click to expand...
Click to collapse
Did you followed this guide
http://forum.xda-developers.com/zuk-z1/general/guide-how-to-unlock-root-install-twrp-t3394037
Or where you start at? Usb debugging activated?
Sent from my Z1 using my hand
strongst said:
Did you followed this guide
http://forum.xda-developers.com/zuk-z1/general/guide-how-to-unlock-root-install-twrp-t3394037
Or where you start at? Usb debugging activated?
Click to expand...
Click to collapse
Yes I followed this guide. I enabled USB debugging and OEM unlock. Fastboot devices did not show my device, so I installed driver once again. Still having the same problem.
SaraKumar said:
Yes I followed this guide. I enabled USB debugging and OEM unlock. Fastboot devices did not show my device, so I installed driver once again. Still having the same problem.
Click to expand...
Click to collapse
Sounds like the drivers are not installed correctly, is your zuk visible in windows device manager?
You can try this drivers too, https://drive.google.com/file/d/0B4Zy8uoEfFKLSC0wNXhaRVRWWEk/view?usp=drivesdk
Sent from my Z1 using my hand
strongst said:
Sounds like the drivers are not installed correctly, is your zuk visible in windows device manager?
You can try this drivers too, https://drive.google.com/file/d/0B4Zy8uoEfFKLSC0wNXhaRVRWWEk/view?usp=drivesdk
Click to expand...
Click to collapse
It is visible under portable devices. There is also something called ShenQi composite ADB interface under ShenQi ADB device. I tried this driver too didn't work.
dude I got exactly the same problem. need to flash a new rom as stock is unusable. tried everything; USB debugging, own unlock, reinstalling drivers, different USB cables, etc.
shows as shenqi hs-usb in device manager, then just as android device with a yellow exclamation mark when in fastboot.
Someone pls help us we can't root our phone!!! Maybe because we use 64bit windowed and the drives are 32 bit? Senior members please help
SaraKumar said:
Someone pls help us we can't root our phone!!! Maybe because we use 64bit windowed and the drives are 32 bit? Senior members please help
Click to expand...
Click to collapse
The drivers also work on 64bit, I used windows 10 64bit and no problem. Which drivers u use?
Edit: OK, I remember... If you follow the all in one tool it should work also like using without tool over adb.
Sent from my Z1 using my hand
strongst said:
The drivers also work on 64bit, I used windows 10 64bit and no problem. Which drivers u use?
Edit: OK, I remember... If you follow the all in one tool it should work also like using without tool over adb.
Click to expand...
Click to collapse
Please provide link to all in one tool I'll test and update. Thanks for your help
SaraKumar said:
Please provide link to all in one tool I'll test and update. Thanks for your help
Click to expand...
Click to collapse
It's in Original Android Development marked as TOOL, easy to find [emoji6]
Sent from my Z1 using my hand
I tried that, no luck.
I did see somewhere that the Zuk Z1 isn't recognised as a fastboot device and there's some code you need to write after fastboot in adb?
Timoh2010 said:
I tried that, no luck.
I did see somewhere that the Zuk Z1 isn't recognised as a fastboot device and there's some code you need to write after fastboot in adb?
Click to expand...
Click to collapse
Does som1 know what code this is? How come some people can root without any problems? Are our phones buggy? This is frustrating there is no cos 13 and we can't use cm13 too.
SaraKumar said:
Does som1 know what code this is? How come some people can root without any problems? Are our phones buggy? This is frustrating there is no cos 13 and we can't use cm13 too.
Click to expand...
Click to collapse
I did it with these codes:
C:\Users\anwender\AppData\Local\Android\sdk\platform-tools>adb reboot bootloader
C:\Users\anwender\AppData\Local\Android\sdk\platform-tools>fastboot -i 0x2b4c oem unlock-go
...
(bootloader) erasing userdata.
OKAY [ 3.563s]
finished. total time: 3.578s
C:\Users\anwender\AppData\Local\Android\sdk\platform-tools>adb reboot bootloader
C:\Users\anwender\AppData\Local\Android\sdk\platform-tools>fastboot -i 0x2b4c flash recovery z1.twrp.2.8.7.0.By.Breadcrust-UPDATE3.img
target reported max download size of 1610612736 bytes
sending 'recovery' (8686 KB)...
OKAY [ 0.266s]
writing 'recovery'...
OKAY [ 0.141s]
finished. total time: 0.406s
C:\Users\anwender\AppData\Local\Android\sdk\platform-tools>
Sent from my Z1 using my hand
strongst said:
I did it with these codes:
C:\Users\anwender\AppData\Local\Android\sdk\platform-tools>adb reboot bootloader
C:\Users\anwender\AppData\Local\Android\sdk\platform-tools>fastboot -i 0x2b4c oem unlock-go
...
(bootloader) erasing userdata.
OKAY [ 3.563s]
finished. total time: 3.578s
C:\Users\anwender\AppData\Local\Android\sdk\platform-tools>adb reboot bootloader
C:\Users\anwender\AppData\Local\Android\sdk\platform-tools>fastboot -i 0x2b4c flash recovery z1.twrp.2.8.7.0.By.Breadcrust-UPDATE3.img
target reported max download size of 1610612736 bytes
sending 'recovery' (8686 KB)...
OKAY [ 0.266s]
writing 'recovery'...
OKAY [ 0.141s]
finished. total time: 0.406s
C:\Users\anwender\AppData\Local\Android\sdk\platform-tools>
Click to expand...
Click to collapse
I didn't try the -i ,0x part. I'll try and update
So, I bricked my phone, iw won't boot into the bootloader is unlocked menu even though it is unlocked, when I install a recovery this is what appears
target reported max download size of 471859200 bytes
sending 'recovery' (28928 KB)...
OKAY [ 1.050s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.057s
can anyone help me with this? the 3 button method doesnt work, it always says software installation failed, I really need to restore my phone, any help would be appreciated
i have had the same problem some days ago.
Re unlock bootloader and re try
unloadedluck said:
So, I bricked my phone, iw won't boot into the bootloader is unlocked menu even though it is unlocked, when I install a recovery this is what appears
target reported max download size of 471859200 bytes
sending 'recovery' (28928 KB)...
OKAY [ 1.050s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.057s
can anyone help me with this? the 3 button method doesnt work, it always says software installation failed, I really need to restore my phone, any help would be appreciated
Click to expand...
Click to collapse
This thread may help you https://forum.xda-developers.com/hu...ution-bl-unlockedfrp-locked-fastboot-t3684302
Neo Markson said:
This thread may help you https://forum.xda-developers.com/hu...ution-bl-unlockedfrp-locked-fastboot-t3684302
Click to expand...
Click to collapse
okay, so, I fixed my phone and stuff, but there seems to be a problem, I can't force update my phone through the 3 button method, the zip I donwload aren't corrupted the version is compatible, it just says "Software install failed" is there a solution to this? I can only flash through twrp
to have b390 i do like this:
B160 -> B370(TWRP) -> B390 (Firmwre finder DNS method)
unloadedluck said:
okay, so, I fixed my phone and stuff, but there seems to be a problem, I can't force update my phone through the 3 button method, the zip I donwload aren't corrupted the version is compatible, it just says "Software install failed" is there a solution to this? I can only flash through twrp
Click to expand...
Click to collapse
You should try to nstall stock rom from your region. But NOTE: you shouldn't select that option on firmware finder(incase u use another phone) or you'll end up with test keys.
Hello,
I have been rooted my phone for a couple of months, but got it broken a few weeks ago. Then I have with the help of this forum restored my phone with a rollback.
But since my phone works again many features are disabled and I seem to have only a testkey. Could someone please help me if I get back to the original version?
Thanks in advance (Sorry for my bad English!).
UselessIdiot said:
Hello,
I have been rooted my phone for a couple of months, but got it broken a few weeks ago. Then I have with the help of this forum restored my phone with a rollback.
But since my phone works again many features are disabled and I seem to have only a testkey. Could someone please help me if I get back to the original version?
Thanks in advance (Sorry for my bad English!).
Click to expand...
Click to collapse
Yup bro, i'm bricking my mate 8 countless already..and twice got test-keys..haha..the easiest solution is with go to eRecovery..yup, but need strong wifi signal..Btw, what is your mate 8 variant?
You can try my tuto in this link - https://forum.xda-developers.com/mate-8/general/solved-nrd90m-test-keys-nougat-stock-t3841805
ceriqdesign said:
Yup bro, i'm bricking my mate 8 countless already..and twice got test-keys..haha..the easiest solution is with go to eRecovery..yup, but need strong wifi signal..Btw, what is your mate 8 variant?
You can try my tuto in this link - https://forum.xda-developers.com/mate-8/general/solved-nrd90m-test-keys-nougat-stock-t3841805
Click to expand...
Click to collapse
It says "Getting package info failed"
My internet connection should be ok.
But I didn't try factory reset yet.
Shall I try?
ceriqdesign said:
Yup bro, i'm bricking my mate 8 countless already..and twice got test-keys..haha..the easiest solution is with go to eRecovery..yup, but need strong wifi signal..Btw, what is your mate 8 variant?
You can try my tuto in this link - https://forum.xda-developers.com/mate-8/general/solved-nrd90m-test-keys-nougat-stock-t3841805
Click to expand...
Click to collapse
A few informations:
Huawei Mate 8
Original model number: NXT-L29C432B582 (current: NXT-L29)
Original build number: QHC0215C28010192 (current: NRD90 test-keys)
IMEI: 868407020986939/868407020966378
Android version: 7.0
EMUI version: 5.0
UselessIdiot said:
A few informations:
Huawei Mate 8
Original model number: NXT-L29C432B582 (current: NXT-L29)
Original build number: QHC0215C28010192 (current: NRD90 test-keys)
IMEI: 868407020986939/868407020966378
Android version: 7.0
EMUI version: 5.0
Click to expand...
Click to collapse
Did you already unlocked bootloader and have TWRP installed?if yes you can try the method using HuRUpdater..use B583 and download all update.zip, update_data_full_public.zip and NXT-L29_hw_eu.zip from Firmware Finder.
UselessIdiot said:
A few informations:
Huawei Mate 8
Original model number: NXT-L29C432B582 (current: NXT-L29)
Original build number: QHC0215C28010192 (current: NRD90 test-keys)
IMEI: 868407020986939/868407020966378
Android version: 7.0
EMUI version: 5.0
Click to expand...
Click to collapse
Download b560 fullota-MF-PV !!!
Flash it using twrp open Kirin edition the one here on the forums
First flash the update zip and then the second file with it
U will be back to stock & receive updates
If anything happens & the system ask for reset simply erase data and redo the process and that's it {I did this many times since I always brick my phone with testing & always worked}
ceriqdesign said:
Did you already unlocked bootloader and have TWRP installed?if yes you can try the method using HuRUpdater..use B583 and download all update.zip, update_data_full_public.zip and NXT-L29_hw_eu.zip from Firmware Finder.
Click to expand...
Click to collapse
The Bootloader is unlocked but TWRP isn't installed.
UselessIdiot said:
The Bootloader is unlocked but TWRP isn't installed.
Click to expand...
Click to collapse
Try to unlock bootloader once again..that happened to me too..after unlock again should be can flash twrp..
ceriqdesign said:
Try to unlock bootloader once again..that happened to me too..after unlock again should be can flash twrp..
Click to expand...
Click to collapse
>fastboot flash recovery twrp-3.0.2-0-next.img
target reported max download size of 471859200 bytes
sending 'recovery' (22020 KB)...
OKAY [ 0.626s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.637s
OEM-Unlock is not Enabled
And I cant relock the bootloader.
ceriqdesign said:
Try to unlock bootloader once again..that happened to me too..after unlock again should be can flash twrp..
Click to expand...
Click to collapse
Update: I hate myself XD
I did a factory reset.
Tried to unlock FRP.
When I wanted to enter the Wi-Fi password, I noticed that I have no keyboard but only the google language input. And I can not change that either. (The voice input does not work of course)
Thank you for your help :angel:
UselessIdiot said:
Update: I hate myself XD
I did a factory reset.
Tried to unlock FRP.
When I wanted to enter the Wi-Fi password, I noticed that I have no keyboard but only the google language input. And I can not change that either. (The voice input does not work of course)
Thank you for your help :angel:
Click to expand...
Click to collapse
I'm sorry..but there always a way to the solution..don't give mate..haha..just give a try..download gboard from another phone then transfer to your phone..
ceriqdesign said:
I'm sorry..but there always a way to the solution..don't give mate..haha..just give a try..download gboard from another phone then transfer to your phone..
Click to expand...
Click to collapse
I can't transfer Gboard from another phone, bacause my phone is stuck in the establishment phase.
I can't give my PC access to my files.
So i cant fill in my google account and because the FRP is still active i cant bypass the google protection. xD
Done! My mobile phone works again XD
But I would like to get away from the test keys.
UselessIdiot said:
Done! My mobile phone works again XD
But I would like to get away from the test keys.
Click to expand...
Click to collapse
did you already tried HuRUpdater method?
ceriqdesign said:
did you already tried HuRUpdater method?
Click to expand...
Click to collapse
TWRP isn't installed.
>fastboot flash recovery twrp-3.1.0-0-next.img
target reported max download size of 471859200 bytes
sending 'recovery' (22108 KB)...
OKAY [ 0.629s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.639s
Could this possibly be related to the not activated oem unlock or FRP (which I can not enable because I can not relock the bootloader)?
UselessIdiot said:
TWRP isn't installed.
>fastboot flash recovery twrp-3.1.0-0-next.img
target reported max download size of 471859200 bytes
sending 'recovery' (22108 KB)...
OKAY [ 0.629s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.639s
Could this possibly be related to the not activated oem unlock or FRP (which I can not enable because I can not relock the bootloader)?
Click to expand...
Click to collapse
is it your oem unlock grey out? what your FRP status?is it still lock?
try this TWRP..download link https://github.com/OpenKirin/androi...leases/download/3.1.1-1/twrp-3.1.1-1-next.img or this one https://mega.nz/#!Y40XCQRD!YGebCrwhMOOTsvyH7d9PMEhJI8x4tg49Ab604_Qbnj8
ceriqdesign said:
is it your oem unlock grey out? what your FRP status?is it still lock?
try this TWRP..download link https://github.com/OpenKirin/androi...leases/download/3.1.1-1/twrp-3.1.1-1-next.img or this one https://mega.nz/#!Y40XCQRD!YGebCrwhMOOTsvyH7d9PMEhJI8x4tg49Ab604_Qbnj8
Click to expand...
Click to collapse
OEM unlock is grey out. FRP still Lock.
Recovery img from dlink doesn't work.
FAILED (remote: Command not allowed)
UselessIdiot said:
OEM unlock is grey out. FRP still Lock.
Recovery img from dlink doesn't work.
FAILED (remote: Command not allowed)
Click to expand...
Click to collapse
try look at this video https://www.youtube.com/watch?v=1CuNxOHgS5E or this https://www.youtube.com/watch?v=fKJuxkfQzmw.. might be help you bro..i'm also stuck in FRP before but forgot how i managed to solved it.
ceriqdesign said:
try look at this video https://www.youtube.com/watch?v=1CuNxOHgS5E or this https://www.youtube.com/watch?v=fKJuxkfQzmw.. might be help you bro..i'm also stuck in FRP before but forgot how i managed to solved it.
Click to expand...
Click to collapse
I bypassed the FRP but in fastboot mode it still shows "FRP lock".
Still cant flash TWRP
">fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (25236 KB)...
OKAY [ 0.718s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.728s"
UselessIdiot said:
I bypassed the FRP but in fastboot mode it still shows "FRP lock".
Still cant flash TWRP
">fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (25236 KB)...
OKAY [ 0.718s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.728s"
Click to expand...
Click to collapse
sorry..but have you renamed twrp to recovery.img?
if it showed FRP Lock in bootloader with green font it's mean that the bypassed is not successful..did you try both method in the video?