Related
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
Hi,
I just purchased a used Xperia Z1 C6903 and I am trying to put the latest Nougat Resurrection Remix on it. I need to get TWRP going first which I got stuck at trying to flash it.
I was able to get the phone downgraded to 14.1.G.1.534 using flash tool (ver 0.9.24.3). I did this following the guide here https://forum.xda-developers.com/showthread.php?t=2439328.
I was able to root it using Kingoroot.
I was able to unlock the bootloader using flashtool. Using *#*#7378423#*#*, the phone now reports Bootloader Unlocked: yes. See attached screenshot.
The part that I got stuck at is trying to flash TWRP in Fastboot. The command lines and error are below. The main error being "FAILED (remote: Command not allowed)"
I don't have an option in developer's options to "Unlock OEM bootloader". I read some other Xperia users being able to fix this problem by checking this.
I am running Windows 8.1. I am relatively sure that my drivers are correct. I had gotten a "drivers too old" error before in Flashtools but I was able to correct it by reinstalling new drivers.
I tried having debugging checked and unchecked before going into Fastboot and made no difference.
Tried both twrp-2.8.7.0-honami and twrp-3.0.2.0-honami with no success. Tried shortening file name to trp.img with no success.
Tried different 2 different adb files around the web with no success.
I read somewhere someone mentioned briefly that TWRP can be flashed using Flashtools. Is that true? I wasn't able to find a full guide for it.
Any help would be appreciated!
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery trp.img
target didn't report max-download-size
sending 'recovery' (13672 KB)...
OKAY [ 0.433s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.439s
Well I was able to get TWRP on there by installing the XY Dual Recovery. The problem with it is that the Resurrection Remix's installation instruction says to use TWRP 3x or higher. TWRP on XY is only at 2.8.7.0. I couldn't find a TWRP 3x flashable zip file for Honami and TWRP wouldn't flash TWRP 3x IMG file I found. Fastboot is still giving me the same Command Not Allowed error.
Any ways, I went ahead and flashed RR with 2.8.7.0. When I tried to flash GAPPs after it says there is insufficient space. I have at least 9GB+ internal storage. So not sure what the deal is there.
I also lost Dual Recovery and root after first RR boot.
Looking into getting re-rooted and reinstalling XY Dual Recovery now.. And then flashing GAPPS after.
Anyone know what the consequences are for installing RR with a lower rev of TWRP?
So the RR Rom does have root but it just doesn't have apps root. Only ADB root. I cant flash the su add on from Lineage's site since I lost recovery. I ended up FTF back to stock and then reflashed everything, the ROM then pico version of GAPPs (pico worked) and then the su addon. The su addon had an error when flashing in TWRP.
Any ways, long story short the whole thing didn't work. Still stuck with RR Without recovery. Su addon didnt work from the flash. And for whatever reason my SIM is not detected and I lost my IMEI in RR. I read that this is a known issue with C6902 but I have the C6903 and I had confirmed this through the service menu before ROM flash. Maybe problems with flashing RR without the latest TWRP.
The Command Not Allowed is still an issue that I dont know how to resolve. So I still can't flash newer version of TWRP.
Any help would be appreciated....
I guess I will try to find a ROM that 's compatible with TWRP 2.8.7.0.
OK! I figured out what the Command Not Allowed problem is!
I've been following the flash guides from a few websites. And they all reference this syntax for flashing TWRP.
Fastboot flash recovery twrp.img.
This syntax didn't work for me. All those websites properly copycat each other.
That syntax is either incorrect or just didnt work for my setup for some reason. I kept searching for ways to flash TWRP and found another website that uses a different syntax. I gave it a go and TWRP flashed right away. This is the syntax that worked for me.
Fastboot flash boot twrp.img
At least that part of the problem is resolved.
Even after flashing RR with TWRP 3.0.20, the SIM/IMEI is still not showing. Recovery is still lost on first boot. Reinstalling TWRP on top of RR causes RR to not boot any more. I will have to look into the RR thread to investigate more.
I will mark this thread as Solved for the Command Not Allowed.
Crossed out everything cause that was not the correct solution. Striked them out to keep them as part of the troubleshooting steps history.
Oops duplicated post.
OK! So it looks like I have to correct myself here on my previous solution.
My solution from earlier for using "Fastboot flash boot twrp.img" is incorrect apparently. Don't use this!
That was the reason why my TWRP was lost after RR boot. The recovery partition comes after the boot and system partition. By flashing the recovery into boot, it screws up the order.
Nevertheless, the Command Not Allowed was still a problem if I tried to use "Fastboot flash recovery twrp.img"
Any ways I was still looking into this problem and started looking into the boot.img stuff and saw someone uses this command line: "fastboot erase boot". This helps someone being able to flash a boot.img when the user was having the Command not Allowed problem trying to flash a different img for the boot partition.
This gave me an idea to try and use "fastboot erase recovery".
I gave it a try and I was able to use "fastboot flash recovery twrp.img" afterwards! It was done in a second.
Then I went through the normal steps of flashing RR and TWRP stayed this time. So now all is good with everything!
Any ways to recap, my full steps used for my RR Installation:
1. Flashtool to flash an Android 5.1.1 stock rom. I used C6903_14.6.A.1.236_1276. (obtained through Flashtool, Xperifirm) Your phone has to run in 5.1.1 for the SIM and IMEI to work in RR. Don't need to flash modem.zip, that's for C6902 only.
2. Fastboot flash erase recovery
3. Fastboot flash recovery twrp.img
4. Follow instructions to flash RR normally.
5. Resize system partition size (for flashing GAPPS micro size or larger).
6. Flash GAPPS.
7. Flash su addon from Lineage's website to allow root for apps and ADB.
I hope this helps someone with similar problems in the future. Thanks to those who stop in to see me ramble to myself about silly stuff
I had the same error message and was able to successfully flash using the phone and the Android Studio Emulator app.
I was already rooted and had an unlocked bootloader.
I tried this solution and it said error: cannot "recovery": No such file or directory LOL even though it's right here and I use it all the time..........I just can't figure it out.
hello to all the brothers and sisters.
today I managed to root 100% of my HTC DESIRE 10 PRO DUAL.
I confirm that you work, tested personally.
I list the procedures in brief to do (for those with a minimum of familiarity)
1. disconnect the bootloader ...... HTCDEV select last item (all other devices)
2. install the recovery mod (TWRP) with adb - PC
3. Make backup nadroid TWRP your phone.
4. Install the Magisk-v17.1.zip file on TWPR ---------DOWNLOAD here
enjoy the 100% FUCTION ROOT
Have you found Oreo ROMs? That can be used, mine is HTC d10i (10 Pro Desire Dual SIM), is yours the same. I cannot find any ROMs for this phone.
Cheers Mark
Stuck with: FAILED (remote: download for partition 'recovery' is not allowed writing
I am not a newbie, but I only do ROOT once every few years!
I got the same phone [taiwan OS 2.22.709.2] and cannot flash TWRP, I keep getting:
FAILED (remote: download for partition 'recovery' is not allowed writing 'recovery'
Note: when I bootload, I see it is unlocked - so HTC unlock went OK - but I see S-ON - should it be S-OFF?
If so, how do I S-OFF ?
It might just be that.
I always managed to ROOT phone except a M8s - do not know why and left it alone.
Thanks
M
Stuck, same as M8s last year!
Anyone?
Managed to Flash TWRP
Also managed to put SuperSu and Magisk in internal memory
When running fastboot reboot recovery - nothing happens ... waiting for device ...
I checked with adb devices and it is detected [only one]
Note: at normal boot still see Orange State, it still is S-ON Unlocked !
We've GOT DONE with this phone, because it does not use Qualcom !
We've GOT DONE with this phone, because it does not use Qualcom !
i.e. no Custom ROM, that I could find yet.
Although I am still trying to find a page where someone seems to have flashed Pixel 2 in it !
Really?
xdamodded said:
Anyone?
Managed to Flash TWRP
Also managed to put SuperSu and Magisk in internal memory
When running fastboot reboot recovery - nothing happens ... waiting for device ...
I checked with adb devices and it is detected [only one]
Note: at normal boot still see Orange State, it still is S-ON Unlocked !
Click to expand...
Click to collapse
xdamodded said:
Stuck with: FAILED (remote: download for partition 'recovery' is not allowed writing
I am not a newbie, but I only do ROOT once every few years!
I got the same phone [taiwan OS 2.22.709.2] and cannot flash TWRP, I keep getting:
FAILED (remote: download for partition 'recovery' is not allowed writing 'recovery'
Note: when I bootload, I see it is unlocked - so HTC unlock went OK - but I see S-ON - should it be S-OFF?
If so, how do I S-OFF ?
It might just be that.
I always managed to ROOT phone except a M8s - do not know why and left it alone.
Thanks
M
Click to expand...
Click to collapse
hey iam SEXA
i used to install TWRP succcessfully by following command on adb fastboot in Htc Desire10 pro
dont worry about what inside of zip file name.you just type file file name what ever it live in
firstly put the file by copying in adb fastboot folder.which you wanna flash then
Effective1: fastboot oem rebootRUU
FINALL command -fastboot flash recovery recovery.img
1000% workable. i become succcessful after about 1 year.
Hey guys,
I just bought the Honor 10 lite and I am not really a big fan of Huawei's EMUI. That's why I wondered if there is already any custom ROM somewhere out there for this phone? I know it's pretty new and I couldn't find anything so far..
Would still appreciate any information, if somebody knows more about it.
Thanks guys :highfive:
You need to unlock bootloader 1st and that's currently impossible for honor 10 lite with Android 9
Even paid service isn't an option.
Niight Knight said:
You need to unlock bootloader 1st and that's currently impossible for honor 10 lite with Android 9
Even paid service isn't an option.
Click to expand...
Click to collapse
Oh alright, forgot that they stopped providing unlock-code's.. Hope someone figures out something, still not a friend of EMUI.
Thanks for the reply man ?
Niight Knight said:
You need to unlock bootloader 1st and that's currently impossible for honor 10 lite with Android 9
Even paid service isn't an option.
Click to expand...
Click to collapse
I just noticed that with the latest fw update as of today (9.0.1.142), the OEM unlock option can be now changed from the developer options menu, I guess it is still impossible to unlock it but well, now at least it lets you to change the option (before the update it wasn't even possible to do so). I'm not now able to but someone should give it a try to see if by any chance they messed up with OEM...
I think we'll have to wait many months before someone finds an hack to unlock bootloader. This is a very recent smartphone and also Huawei and Honor are not for modding, since it's everything locked and they're not providing unlock codes anymore. Too bad I discovered it after I bought it !
tomax80 said:
I think we'll have to wait many months before someone finds an hack to unlock bootloader. This is a very recent smartphone and also Huawei and Honor are not for modding, since it's everything locked and they're not providing unlock codes anymore. Too bad I discovered it after I bought it !
Click to expand...
Click to collapse
Hello. I have an unlocked Honor 10 Lite, but can't to install Magisk. Who can help me with this question?
Shlendr said:
Hello. I have an unlocked Honor 10 Lite, but can't to install Magisk. Who can help me with this question?
Click to expand...
Click to collapse
How did you unlock the bootloader?
To install magisk you need to install twrp first, then flash magisk zip from there. But there's no twrp for our device so far, maybe you can try running a twrp of a device with our same socket without installing it, from fastboot, and see if it works. For example
Code:
fastboot boot twrpfilename.img
If it works, then you can try flashing magisk from there.
tomax80 said:
How did you unlock the bootloader?
To install magisk you need to install twrp first, then flash magisk zip from there. But there's no twrp for our device so far, maybe you can try running a twrp of a device with our same socket without installing it, from fastboot, and see if it works. For example
Code:
fastboot boot twrpfilename.img
If it works, then you can try flashing magisk from there.
Click to expand...
Click to collapse
I got the phone from presentation. So, it is already unlocked from factory.
I'm not realy understand how can i use the twrpfilename.img? And where i can get this file? Did you have some manual?
I tried to flash twrpkirin.img from Honor 8x, but all system sections are encrypted. So i can't flash magisk.zip
---------- Post added at 08:59 AM ---------- Previous post was at 08:40 AM ----------
tomax80 said:
How did you unlock the bootloader?
To install magisk you need to install twrp first, then flash magisk zip from there. But there's no twrp for our device so far, maybe you can try running a twrp of a device with our same socket without installing it, from fastboot, and see if it works. For example
Code:
fastboot boot twrpfilename.img
If it works, then you can try flashing magisk from there.
Click to expand...
Click to collapse
I have an error:
C:\adb>fastboot boot JSNtwrp.img
downloading 'boot.img'...
OKAY [ 0.550s]
booting...
FAILED (remote: invalid command)
finished. total time: 0.550s
I got the phone from presentation. So, it is already unlocked from factory.
I'm not realy understand how can i use the twrpfilename.img? And where i can get this file? Did you have some manual?
I tried to flash twrpkirin.img from Honor 8x, but all system sections are encrypted. So i can't flash magisk.zip
I have an error:
C:\adb>fastboot boot JSNtwrp.img
downloading 'boot.img'...
OKAY [ 0.550s]
booting...
FAILED (remote: invalid command)
finished. total time: 0.550s
Click to expand...
Click to collapse
There's no manual, just try booting phone in bootloader mode then use that command I told in the previous post. It's just a try , there are no tutorials for this phone so far
TWRP Recovery Honor 10 Lite
tomax80 said:
There's no manual, just try booting phone in bootloader mode then use that command I told in the previous post. It's just a try , there are no tutorials for this phone so far
Click to expand...
Click to collapse
Already done. Got an error
Shlendr said:
Already done. Got an error
Click to expand...
Click to collapse
Ok then probably that version of twrp doesn't work with our phone , we just need to wait for a compatible one.
TWRP Recovery Honor 10 Lite
tomax80 said:
Ok then probably that version of twrp doesn't work with our phone , we just need to wait for a compatible one.
Click to expand...
Click to collapse
I can send all nesessary data of the phone, which will help to creat a workable TWRP. But who can do this?)
Shlendr said:
I can send all nesessary data of the phone, which will help to creat a workable TWRP. But who can do this?)
Click to expand...
Click to collapse
I have no idea sincerely, I think we just need to wait patiently till someone works on it . And it's also not granted that it's going to happen, since it's everything blocked.
guys, what about Android root apps? can those apps help?
TWRP Recovery Honor 10 Lite
cyrusiranmehr said:
guys, what about Android root apps? can those apps help?
Click to expand...
Click to collapse
No
locked after i got into bootloader
hey guys, i tried using bootloader first time and got myself into some situation:
C:\Users\USAKg\AppData\Local\Android\Sdk\platform-tools>adb reboot bootloader
adb server version (39) doesn't match this client (40); killing...
* daemon started successfully
C:\Users\USAKg\AppData\Local\Android\Sdk\platform-tools>fastboot flash recovery_ramdisk twrp_bkl_0.7.img
Sending 'recovery_ramdisk' (23542 KB) OKAY [ 0.711s]
Writing 'recovery_ramdisk' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
Does anyone know how to unlock this one? or do i have to buy unlock bootloader code?
from site named: global unlocking solutions.miiduu ???
GraveDanger said:
hey guys, i tried using bootloader first time and got myself into some situation:
C:\Users\USAKg\AppData\Local\Android\Sdk\platform-tools>adb reboot bootloader
adb server version (39) doesn't match this client (40); killing...
* daemon started successfully
C:\Users\USAKg\AppData\Local\Android\Sdk\platform-tools>fastboot flash recovery_ramdisk twrp_bkl_0.7.img
Sending 'recovery_ramdisk' (23542 KB) OKAY [ 0.711s]
Writing 'recovery_ramdisk' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
Does anyone know how to unlock this one? or do i have to buy unlock bootloader code?
from site named: global unlocking solutions.miiduu ???
Click to expand...
Click to collapse
Bootloader is locked and you can't flash anything till it's locked. There are paid services to unlock it but so far our device is not supported. Though there's no sense to pay a lot of money to unlock it, also if it was supported, just to have root (if you're lucky) , since there are no custom ROMs for Honor 10 lite. Our device is not made for modding. The only solution on my opinion is to wait patiently till someone finds an hack to unlock it for free, or sell your phone and buy a Xiaomi. You can unlock bootloader very easily and there are plenty of custom ROMs for it.
TWRP Recovery Honor 10 Lite
GraveDanger said:
hey guys, i tried using bootloader first time and got myself into some situation:
C:\Users\USAKg\AppData\Local\Android\Sdk\platform-tools>adb reboot bootloader
adb server version (39) doesn't match this client (40); killing...
* daemon started successfully
C:\Users\USAKg\AppData\Local\Android\Sdk\platform-tools>fastboot flash recovery_ramdisk twrp_bkl_0.7.img
Sending 'recovery_ramdisk' (23542 KB) OKAY [ 0.711s]
Writing 'recovery_ramdisk' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
Does anyone know how to unlock this one? or do i have to buy unlock bootloader code?
from site named: global unlocking solutions.miiduu ???
Click to expand...
Click to collapse
Hello. What the twrp_bkl_0.7.img? Where did you get it?) Is it workable?
You can always install a different launcher like Nova Launcher
this link claims you can use TWRP from Huawei P9 lite
https://unofficialtwrp.com/root-twrp-hry-lx1-hry-lx2-hry-al00
Hey whatsup. I recently decided to unlock my bootloader again. Worked flawless. However, Ive used this
Tutorial as always to flash TWRP(Update on first comment actually) and it always worked. However I encountered an error using the ADB fastboot method.
Sending 'boot.img' (131072 KB) OKAY [ 2.812s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Not Found')
fastboot: error: Command failed
Looks like this...this is new for me. And now Im stuck in fastboot mode and cant restart my phone, neither turn it off in any way.
Any solution?
Nevermind...it was my fault. I flashed a new rom through Xiaomi Flash Tool V2. Just worked through MiiManager. And when I looked through my folder Ive seen it: TWRP 3.5.2 "mojito". Ive used the wrong TWRP. Mines for sweet devices.
Regards
romuser87 said:
Nevermind...it was my fault. I flashed a new rom through Xiaomi Flash Tool V2. Just worked through MiiManager. And when I looked through my folder Ive seen it: TWRP 3.5.2 "mojito". Ive used the wrong TWRP. Mines for sweet devices.
Regards
Click to expand...
Click to collapse
You're lucky the installation didn't go through .
Whats the worst thing that wouldve happened? full brick?