C:\Users\Jason\Downloads>moto-fastboot devices
TA20705TET fastboot
C:\Users\Jason\Downloads>moto-fastboot erase recovery
erasing 'recovery'... FAILED (remote: (00180001))
C:\Users\Jason\Downloads>moto-fastboot flash recovery recovery-green-atrix3.2.im
g
sending 'recovery' (4780 KB)... OKAY [ 0.498s]
writing 'recovery'... FAILED (remote: (00180002))
C:\Users\Jason\Downloads>
---------- Post added at 05:51 AM ---------- Previous post was at 05:50 AM ----------
Ok so I'm not sure why but it wouldnt let me type anymore on original post. Anyways, i am trying to flash using fastboot the atrix unlocked CWM. However when i type the commands i keep getting errors. Any ideas on what this is?
jason.hamilton said:
C:\Users\Jason\Downloads>moto-fastboot devices
TA20705TET fastboot
C:\Users\Jason\Downloads>moto-fastboot erase recovery
erasing 'recovery'... FAILED (remote: (00180001))
C:\Users\Jason\Downloads>moto-fastboot flash recovery recovery-green-atrix3.2.im
g
sending 'recovery' (4780 KB)... OKAY [ 0.498s]
writing 'recovery'... FAILED (remote: (00180002))
C:\Users\Jason\Downloads>
---------- Post added at 05:51 AM ---------- Previous post was at 05:50 AM ----------
Ok so I'm not sure why but it wouldnt let me type anymore on original post. Anyways, i am trying to flash using fastboot the atrix unlocked CWM. However when i type the commands i keep getting errors. Any ideas on what this is?
Click to expand...
Click to collapse
Did you find your solution because I'm stuck at the same thing. I had touch screen issues after flashing a ROM. So I RSD back to stock but the touch screen problem persist. I read of the PDS fix in a post and I'm getting the same error but with trying to erase/write my PDS backup to the phone.
Make sure you put the image you are trying to flash in the same folder as your fastboot.
Vangelis13 said:
Make sure you put the image you are trying to flash in the same folder as your fastboot.
Click to expand...
Click to collapse
OP said it fails when trying to erase as well. So it's not file placement issues.
Speedily sent from CM7 Beta
Having same problem here... any solution?
why not just flash the one from rom manager then flash the zip to the one you want through that. thats what i did works perfect!
Related
I have a phone with HBOOT 1.01 S-off.
Code:
LEGEND PVT SHIP S-OFF
HBOOT-1.01.0000
I'm trying to flash the CWM. In the fastboot via adb:
Code:
fastboot flash image image.img
Get the error:
Code:
sending 'recovery' (3112 KB)
OKAY [ 0.410s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.410s
What am I doing wrong? How do I flash the image of CWM recovery?
P.S. Sorry for my bad English...
clever_man said:
I have a phone with HBOOT 1.01 S-off.
Code:
LEGEND PVT SHIP S-OFF
HBOOT-1.01.0000
I'm trying to flash the CWM. In the fastboot via adb:
Code:
fastboot flash image image.img
Get the error:
Code:
sending 'recovery' (3112 KB)
OKAY [ 0.410s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.410s
What am I doing wrong? How do I flash the image of CWM recovery?
P.S. Sorry for my bad English...
Click to expand...
Click to collapse
I think it is; fastboot flash recovery image.img
Hitmax117 said:
I think it is; fastboot flash recovery image.img
Click to expand...
Click to collapse
You're right, but I made a mistake when he wrote the post, in fact I am writing
Code:
fastboot flash recovery image.img
Log shows that trying to flash the recovery, but can't.
Ajafri86 said:
hi guys,
i am also have the same problem. When i try to flash cwm recovery.img through OneX tool kit or using the adb, i get the same error
writing 'recovery'... FAILED (remote: not allowed)
I have recently installed the official ics firmware on my sensation. Have been trying to root but stuck with the cwm recovery.
Need suggestions / guidance.
Click to expand...
Click to collapse
Wrong forum.
Sent from my Transformer TF101 using xda app-developers app
I had niles business rom on my phone and it kept messing up on me. so i downloaded the toolkit for s-off. After many tries i was able to get s-off. Now here is where my problem is there is no recovery on my phone now and when i try and do a fastboot in the cmd for my phone it will not write the Amon Ra recovery file. I now get this.
C:\Android\sdk-tools>fastboot flash boot boot.img
sending 'boot' (3896 KB)... OKAY [ 0.814s]
writing 'boot'... FAILED (remote: not allowed)
finished. total time: 1.130s
what should i do?
eggbert81 said:
I had niles business rom on my phone and it kept messing up on me. so i downloaded the toolkit for s-off. After many tries i was able to get s-off. Now here is where my problem is there is no recovery on my phone now and when i try and do a fastboot in the cmd for my phone it will not write the Amon Ra recovery file. I now get this.
C:\Android\sdk-tools>fastboot flash boot boot.img
sending 'boot' (3896 KB)... OKAY [ 0.814s]
writing 'boot'... FAILED (remote: not allowed)
finished. total time: 1.130s
what should i do?
Click to expand...
Click to collapse
So your trying to flash it as a boot.img? Amon Ra should be flashed as fastboot flash recovery recovery.img. Also if your on stock HBoot i think you need a modified HBoot for fastboot commands or unlocked eve on S-Off
sorry should have been
C:\Users\jamie\Desktop\Fastboot>fastboot flash recovery recovery-ra-vigor-3.15-gnm.img
sending 'recovery' (7078 KB)... OKAY [ 1.426s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 1.742s
eggbert81 said:
sorry should have been
C:\Users\jamie\Desktop\Fastboot>fastboot flash recovery recovery-ra-vigor-3.15-gnm.img
sending 'recovery' (7078 KB)... OKAY [ 1.426s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 1.742s
Click to expand...
Click to collapse
Do you have a stock HBoot? if so i think it has to be unlocked for fastboot commands even on s-off unless you have a modified Hboot that allows for fastboot commands while locked.
jon7701 said:
So your trying to flash it as a boot.img? Amon Ra should be flashed as fastboot flash recovery recovery.img. Also if your on stock HBoot i think you need a modified HBoot for fastboot commands or unlocked eve on S-Off
Click to expand...
Click to collapse
i was reading about flashing the boot image so i also tried to take the boot.img out of CleanROM Standard 4.5 and tried to flash the boot and that didnt work either
i do have s-off and i can get my phone to say FASTBOOT USB but everything i try and write to it says sending OKAY then writing FAILED ( remote: not allowed)
eggbert81 said:
i was reading about flashing the boot image so i also tried to take the boot.img out of CleanROM Standard 4.5 and tried to flash the boot and that didnt work either
i do have s-off and i can get my phone to say FASTBOOT USB but everything i try and write to it says sending OKAY then writing FAILED ( remote: not allowed)
Click to expand...
Click to collapse
Well if your bootloader is locked i would unlock it or get a modified bootloader that allows fastboot commands while locked. If those dont work then youll have to ask a dev
somehow i didnt even notice that was locked. ok got recovery on. now going to try and get a rom on it. with all this headache i almost miss my GNex but it has tons of issues
eggbert81 said:
somehow i didnt even notice that was locked. ok got recovery on. now going to try and get a rom on it. with all this headache i almost miss my GNex but it has tons of issues
Click to expand...
Click to collapse
Glad i could help :highfive:
got it all to work. Thanks
eggbert81 said:
got it all to work. Thanks
Click to expand...
Click to collapse
i didt understand much
still a newbie
first how do u know if the bootloader is locked or not
and how did u workout the problem
im having the same issue please help
& thnx:good:
When your in bootloader there will be a big pink highlight that says locked or unlocked
Sent from my ADR6425LVW using xda app-developers app
Deleted
i was trying to flash the new chinese jb rom on my motorola xt910 following this
forum http://forum.xda-developers.com/showthread.php?t=2135350
i had backed up my cid but when i restored my ics stock rom again using rsd lite... i rooted by device and then tried restoring my cid using terminal emulator but it keeps saying it does not have the right to restore or permission not granted. what to i do ???
p.s i had kept a copy of my cid in the sd card too
---------- Post added at 06:39 PM ---------- Previous post was at 06:36 PM ----------
Irthu said:
i was trying to flash the new chinese jb rom on my motorola xt910 following this
forum http://forum.xda-developers.com/showthread.php?t=2135350
i had backed up my cid but when i restored my ics stock rom again using rsd lite... i rooted by device and then tried restoring my cid using terminal emulator but it keeps saying it does not have the right to restore or permission not granted. what to i do ???
p.s i had kept a copy of my cid in the sd card too
Click to expand...
Click to collapse
But first you can try following in your terminal emulator:
Type SU and hit Enter, it should ask you for Root permissions, grant them and after that you should be able to restore CID using dd !
IF DOESNT WORK TRY THIS
Reboot your phone in AP fastboot
First i've flashed following
fastboot flash mbm allow-mbmloader-flashing-mbm.bin (i took this file from Chinese JB ROM)
than after that i've rebooted to bootloader
fastboot reboot-bootloader
than i've flashed CID
fastboot flash cid cid.img (you need to copy CID.img backup to your computer)
Than you can reboot
fastboot reboot
And everything should work !
C:\fastboot>fastboot flash mbm allow-mbmloader-flashing-mbm.bin
sending 'mbm' (512 KB)...
OKAY [ 0.030s]
writing 'mbm'...
OKAY [ 0.498s]
finished. total time: 0.529s
C:\fastboot>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.007s
C:\fastboot>fastboot flash cid cid.img
sending 'cid' (512 KB)...
OKAY [ 0.029s]
writing 'cid'...
OKAY [ 0.806s]
finished. total time: 0.836s
C:\fastboot>fastboot reboot
rebooting...
finished. total time: 0.007s
>>> Still the same Customer Error ... Thank you, shmank you razrguy...
vonz33 said:
C:\fastboot>fastboot flash cid.img
Click to expand...
Click to collapse
"fastboot flash cid cid.img"
I just copied your commands, read again.. Even repeated the operation 3 times to make sure.
Flash the ICS kernel after restoring cid
Sent from my MOTOROLA RAZR using Tapatalk 2
Which one? Can I flash just the kernel?
My System Version is 672.180.33.XT910.Retail.en.EU Kernel 3.0.8-g71323c3
Thanks
maybe you can try restoring cid via BMM
well how would you do this
TRY THIS
vonz33 said:
well how would you do this
Click to expand...
Click to collapse
using BMM
be sure that you have cid.img on the root of your internal memory
enter recovery after press screen during boot (when green android appears)
select Firmware flashing
then Restore CID
select cid.img using power button (and navigate with volume keys)
confirm
reboot
E:/error in/preinstall/bootmenu/script/radio.zip
(status0)
Flashing aborted
---------- Post added at 07:19 PM ---------- Previous post was at 06:36 PM ----------
I have used bmm 0.2.7 as its the one with green robot on splash screen
for what i can see your cid was restored successfully.
get rsd lite if you don't have it.
get a firmware from where http://sbf.droid-developers.org/umts_spyder/list.php for example http://sbf.droid-developers.org/umt...PDRICSRTCEE_HWp2b_Service1FF_fastboot.xml.zip which is latest retail central europe or whatever you want.
go to rsd lite open firmware, get into fastboot if you are not already. flash the firmware, wait until is ok.
boot to normal recovery from cmd: adb reboot recovery
wipe data/factory reset
and you should be good to go.
Why? Whats wrong with the ROM i've installed? what makes you say that it will work with these?
My CID.img file is lost
Hello friends,
Can anyone mail me the cid.img file.....
mine is lost and i am unable to restore back my XT910 to ics....
the phone is not mine and i am screwed as i need to return the phone to my friend. but now as the cid.img file is lost, i am unable to restore it to the original state...
please someone help me.
my mail id is [email protected]
thanks:crying:
Of what I've heard you cannot do this as your motherboard will accept only the ONE cid.img that it's been build to work with. You apparently will have to send your phone back and it will cost you big $$ to get the parts replaced and matched.
---------- Post added at 01:52 PM ---------- Previous post was at 01:46 PM ----------
Sisqo said:
for what i can see your cid was restored successfully.
get rsd lite if you don't have it.
get a firmware from where http://sbf.droid-developers.org/umts_spyder/list.php for example http://sbf.droid-developers.org/umt...PDRICSRTCEE_HWp2b_Service1FF_fastboot.xml.zip which is latest retail central europe or whatever you want.
go to rsd lite open firmware, get into fastboot if you are not already. flash the firmware, wait until is ok.
boot to normal recovery from cmd: adb reboot recovery
wipe data/factory reset
and you should be good to go.
Click to expand...
Click to collapse
SPDREM_U_01.6.7.2-180_SPU-19-TA-11.6_SIGNEuropeAustraliaEMEA_USASPDRICSRTCEE_HWp2b_Service1FF_fastboot.xml
Is the one you are suggesting.
And this is the one I have installed, prior to run the cid.img flash operation that gave me an error and stated clearly that the flashing was aborted
SPDREM_U_01.6.7.2-180_SPU-19-TA-11.2_SIGNEuropeAustraliaEMEA_USASPDRICSRTGB_HWp2b_Service1FF_fastboot.xml
What is this going to change.. It would be nice a clear explaination before I reset my phone again
I appreciate your efforts in helping somehow but it does not seem to be going anywhere at this stage.
A lot of us are having this same error and most have let go of it and are doomed to boot via bp tools. I think it would be a good idea to explain the whole logic behind the actions in order to fix the error, this wont be helping just me
Cheers mate
Your system and data will be wiped, the internal and external sdcard will not be affected, I gave this solution to restore your mobile to the default firmware you had.
If restoring the cid and flashing ics kernel doesn't work, that is the only way.
Your data might remain if you flash the firmware and then boot normally it happened to me once but if it doesn't boot you need to enter default recovery and wipe data/factory reset before using the phone.
Sent from my XT910 using Tapatalk 2
Okay mate, it's what I thought... you did not read propperly what I said and it did not work. Still the same error. Total waste of time. Next time make sure you understand what people say before trying to help them.
C:\Android\sdk\platform-tools>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (31748 KB)...
OKAY [ 1.053s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 1.076s
C:\Android\sdk\platform-tools>fastboot flashing unlock ...
(bootloader) Device already : unlocked!
OKAY [ 0.012s]
finished. total time: 0.013s
I have both oem unlock and usb debugging checked on the developer options plus i was able to unlock the devices oem through fastboot. I opened the command prompt in androids/sdk/platform tools but nothing happens just repeats recovery failed. I also get the android laying down with a red exclamation point while in recovery mode. What am I doing wrong? (My goal is to download twrp onto my lg V10)
Which directory is your recovery located. It needs to be in your adb folder. And what version of Android are you on? If you're on MM then Fastboot commands will not work. But if you're on LP it should still work.
---------- Post added at 11:02 PM ---------- Previous post was at 10:58 PM ----------
-Atlas__ said:
C:\Android\sdk\platform-tools>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (31748 KB)...
OKAY [ 1.053s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 1.076s
C:\Android\sdk\platform-tools>fastboot flashing unlock ...
(bootloader) Device already : unlocked!
OKAY [ 0.012s]
finished. total time: 0.013s
I have both oem unlock and usb debugging checked on the developer options plus i was able to unlock the devices oem through fastboot. I opened the command prompt in androids/sdk/platform tools but nothing happens just repeats recovery failed. I also get the android laying down with a red exclamation point while in recovery mode. What am I doing wrong? (My goal is to download twrp onto my lg V10)
Click to expand...
Click to collapse
..
I have been Having the same problem
I recently updated my H901 to MM and have been receiving this error every time. I have attempted this on multiple computers that have been used to successfully root the phone before on LP. I am convinced this is a phone issue related to MM.
None of the root guides available online seem to address this type of problem.
is there a new process for MM?
---------- Post added at 04:13 PM ---------- Previous post was at 04:09 PM ----------
spencercnorton2012 said:
I recently updated my H901 to MM and have been receiving this error every time. I have attempted this on multiple computers that have been used to successfully root the phone before on LP. I am convinced this is a phone issue related to MM.
None of the root guides available online seem to address this type of problem.
is there a new process for MM?
Click to expand...
Click to collapse
http://forum.xda-developers.com/lg-v10/help/how-root-lg-v10-android-6-0-rooted-t3346387
spencercnorton2012 said:
I recently updated my H901 to MM and have been receiving this error every time. I have attempted this on multiple computers that have been used to successfully root the phone before on LP. I am convinced this is a phone issue related to MM.
None of the root guides available online seem to address this type of problem.
is there a new process for MM?
---------- Post added at 04:13 PM ---------- Previous post was at 04:09 PM ----------
http://forum.xda-developers.com/lg-v10/help/how-root-lg-v10-android-6-0-rooted-t3346387
Click to expand...
Click to collapse
Fastboot commands are blocked onthe MM update. therefore no recovery can be flashed atm.
This worked for me
Hi. Im a newbie, so I can't post links yet, but I was having the same error, but I found a method that worked for me. It began:
HOW TO ROOT LG V10 T-MOBILE H901 RUNNING ANDROID 6.0 MARSHMALLOW
Download the KDZ ROM and save it to your desktop.
Download the TOT TWRP file and save it to your desktop.
Download the LGUP tool and save it to the desktop.
Note- This is tested on BKL-L09 C675 Indian variant and BKL-L09 C432 EU variant but will work on any variant of V10.
Hi Folks,
As I shared my experience on the issues I faced while moving back to stock from custom ROMs here , in this thread, I will share the detailed steps to go back to on stock avoiding any issues.
If you are on any custom ROM i.e. with Android/EMUI 8.1 TWRP backup will not work except BKL-L04. And only way that comes handy is fastboot (haven't tested the dload method myself yet as didnt had the SD card when I faced the issue but you can follow that, it will not break anything).
So before you start moving further to stock, please have these 3 files handy-
1- Stock recovery ramdisk
2- Stock boot ramdisk
3- system.img
Case 1- Custom ROM + Stock Boot + Stock Recovery (Applicable for new Open Kirin ROMs- RR and LOS which needs stock Ramdisk and if you are not using magisk)
On custom ROM, connect your phone with USB debugging enabled. (please make sure all the drivers are installed, it will already be as you may have the same which flashing the custom ROM)
Run the command to boot to fastboot
Code:
adb reboot bootloader
On fastboot screen, you will have bootloader state as Unlocked and FRP Unlocked.
Flash System image as below, Wait for process to finish, it may take 1-2 minutes for entire flash (93 seconds in my case)
Code:
PS C:\adb> fastboot flash system BKL-C432B130_system.img or fastboot flash system <system_filename>.img
target reported max download size of 471859200 bytes
sending sparse 'system' (456507 KB)...
OKAY [ 11.572s]
writing 'system'...
OKAY [ 2.669s]
sending sparse 'system' (457797 KB)...
OKAY [ 11.722s]
writing 'system'...
OKAY [ 2.630s]
sending sparse 'system' (457585 KB)...
OKAY [ 11.793s]
writing 'system'...
OKAY [ 3.417s]
sending sparse 'system' (460798 KB)...
OKAY [ 12.008s]
writing 'system'...
OKAY [ 2.611s]
sending sparse 'system' (413494 KB)...
OKAY [ 10.682s]
writing 'system'...
OKAY [ 2.631s]
sending sparse 'system' (453913 KB)...
OKAY [ 11.785s]
writing 'system'...
OKAY [ 2.973s]
sending sparse 'system' (227740 KB)...
OKAY [ 5.856s]
writing 'system'...
OKAY [ 1.260s]
finished. total time: 93.634s
Once the system image is flashed successfully, run the command to boot but immediately remove USB and press volume up key to boot to recoevery rather than system (even if you skip, it may not boot to system)
Code:
fastboot reboot
Remove USB and press volume up key to boot to recovery.
Perform factory reset and wipe data as well.
Once completed, reboot to system.
Case 2- Custom ROM + Stock Recovery + Magisk (Root) ( applicable for New open Kirin ROMs- RR and LOS which needs stock ramdisk and if you are using magisk)
I forgot that I had magisk and had to gone through more issues as post boot, my IMEI was missing and no SIM service but if you have magisk installed, please be more careful and flash stock boot (attached for BKL-L09 EU version)
Run the command to boot to fastboot
Code:
adb reboot bootloader
On fastboot screen, you will have bootloader state as Unlocked and FRP Unlocked.
Flash the stock boot ramdisk.img as
Code:
fastboot flash ramdisk BKL-L09_ramdisk.img
Or fastboot flash ramdisk <ramdisk_File_Name>
Flash System image as below, Wait for process to finish, it may take 1-2 minutes for entire flash (93 seconds in my case)
Code:
PS C:\adb> fastboot flash system BKL-C432B130_system.img or fastboot flash system <system_filename>.img
target reported max download size of 471859200 bytes
sending sparse 'system' (456507 KB)...
OKAY [ 11.572s]
writing 'system'...
OKAY [ 2.669s]
sending sparse 'system' (457797 KB)...
OKAY [ 11.722s]
writing 'system'...
OKAY [ 2.630s]
sending sparse 'system' (457585 KB)...
OKAY [ 11.793s]
writing 'system'...
OKAY [ 3.417s]
sending sparse 'system' (460798 KB)...
OKAY [ 12.008s]
writing 'system'...
OKAY [ 2.611s]
sending sparse 'system' (413494 KB)...
OKAY [ 10.682s]
writing 'system'...
OKAY [ 2.631s]
sending sparse 'system' (453913 KB)...
OKAY [ 11.785s]
writing 'system'...
OKAY [ 2.973s]
sending sparse 'system' (227740 KB)...
OKAY [ 5.856s]
writing 'system'...
OKAY [ 1.260s]
finished. total time: 93.634s
Once the system image is flashed successfully, run the command to boot but immediately remove USB and press volume up key to boot to recoevery rather than system (even if you skip, it may not boot to system)
Code:
fastboot reboot
Remove USB and press volume up key to boot to recovery.
Perform factory reset and wipe data as well.
Once completed, reboot to system.
Case 3- Custom ROM + Custom Recovery + (Stock Ramdisk/ modified Ramdisk with Magisk) (Applicable for any custom ROM installed with TWRP and on stock boot or Magisk)
I forgot that I had magisk and had to gone through more issues as post boot, my IMEI was missing and no SIM service but if you have magisk installed, please be more careful and flash stock boot (attached for BKL-L09 EU version)
Run the command to boot to fastboot
Code:
adb reboot bootloader
On fastboot screen, you will have bootloader state as Unlocked and FRP Unlocked.
Flash the stock Recovery Ramdisk as
Code:
fastboot flash recovery_ramdisk recovery_ramdisk_bak.img
Or fastboot flash recovery_ramdisk <Recovery_File_Name>.img
If you have stock Boot Ramdisk, proceed to flashing system image and skip flashing the boot ramdisk.
If you have installed magisk, flash the stock boot ramdisk.img as
Code:
fastboot flash ramdisk BKL-L09_ramdisk.img
Or fastboot flash ramdisk <ramdisk_File_Name>
Flash System image as below, Wait for process to finish, it may take 1-2 minutes for entire flash (93 seconds in my case)
Code:
PS C:\adb> fastboot flash system BKL-C432B130_system.img or fastboot flash system <system_filename>.img
target reported max download size of 471859200 bytes
sending sparse 'system' (456507 KB)...
OKAY [ 11.572s]
writing 'system'...
OKAY [ 2.669s]
sending sparse 'system' (457797 KB)...
OKAY [ 11.722s]
writing 'system'...
OKAY [ 2.630s]
sending sparse 'system' (457585 KB)...
OKAY [ 11.793s]
writing 'system'...
OKAY [ 3.417s]
sending sparse 'system' (460798 KB)...
OKAY [ 12.008s]
writing 'system'...
OKAY [ 2.611s]
sending sparse 'system' (413494 KB)...
OKAY [ 10.682s]
writing 'system'...
OKAY [ 2.631s]
sending sparse 'system' (453913 KB)...
OKAY [ 11.785s]
writing 'system'...
OKAY [ 2.973s]
sending sparse 'system' (227740 KB)...
OKAY [ 5.856s]
writing 'system'...
OKAY [ 1.260s]
finished. total time: 93.634s
Once the system image is flashed successfully, run the command to boot but immediately remove USB and press volume up key to boot to recoevery rather than system (even if you skip, it may not boot to system)
Code:
fastboot reboot
Remove USB and press volume up key to boot to recovery.
Perform factory reset and wipe data as well.
Once completed, reboot to system.
Once booted on any of the case, you will be on full stock with unlocked bootloader. (you need to either dload to lock the bootlaoder or run the command - fastboot oem urelock <16 digit bootlaoder code> to relock the bootlaoder).
Working and tested myself and confirmed by one more user(Sandeep Dash). So, if you follow the steps correctly, you should not face any issue but in case you get stuck anywhere or not clear with steps and I will try to help as much as I can.
Attached files for BKL-L09 EU version. I will add other files as an when I get it.
Stock Ramdisk for BKL-L09 EU version - Thanks to @topjohnwu for sharing here
Stock Recovery for BKL-L04 EU version -I extracted this but thanks to @shihabsoft for sharing the step which helped me doing this.
Stock system image for BKL-L09 EU Version - Thanks to @surdu_petru for sharing here
Will these method work on bkl l09 model (indian variant)?
Really nice guide! Just one thing: Aren't you missing a
Code:
fastboot flash recovery_ramdisk <recovery_ramdisk_file>
step somewhere?
mondalakash said:
Will these method work on bkl l09 model (indian variant)?
Click to expand...
Click to collapse
Yes it will, 100%. The case 1 confirmation from Sandeep is for Indian variant only.
Smaehtin said:
Really nice guide! Just one thing: Aren't you missing a step somewhere?
Click to expand...
Click to collapse
Thanks. Nope buddy, as you already have stock recovery (for new Open Kirin ROMs) and only boot ramdisk was modified (for Magisk)
But yes, if you flashed twrp then you need it. Thanks for highlighting it, i will fix this.
shashank1320 said:
Yes it will, 100%. The case 1 confirmation from Sandeep is for Indian variant only.
Click to expand...
Click to collapse
Thanks for the confirmation...one question should i use the official twrp or the unofficial one for installing custom roms , decrypting internal storage and so on...
shashank1320 said:
Thanks. Nope buddy, as you already have stock recovery and only boot ramdisk was modified.
But yes, if you flashed twrp then you need it. Thanks for highlighting it, i will fix this.
Click to expand...
Click to collapse
Oh, I see. I was just a little confused about this part then:
shashank1320 said:
So before you start moving further to stock, please have these 3 files handy-
1- Stock recovery ramdisk
2- Stock boot ramdisk
3- system.img
Click to expand...
Click to collapse
mondalakash said:
Thanks for the confirmation...one question should i use the official twrp or the unofficial one for installing custom roms , decrypting internal storage and so on...
Click to expand...
Click to collapse
FOr me it was unofficial as I was using OpenKirin ROM as per requirement it should be stock recovery only.
for other ROMs or backup, you can try the unofficial one as official doesnt work on Android 8.1 and it will show random content or character in TWRP so you can not restore or say access the stuffs on your internal memory. I used the unofficial one given here
shashank1320 said:
FOr me it was unofficial as I was using OpenKirin ROM as per requirement it should be stock recovery only.
for other ROMs or backup, you can try the unofficial one as official doesnt work on Android 8.1 and it will show random content or character in TWRP so you can not restore or say access the stuffs on your internal memory. I used the unofficial one given here
Click to expand...
Click to collapse
Did you try dirty unicorn RC latest build?
Smaehtin said:
Oh, I see. I was just a little confused about this part then:
Click to expand...
Click to collapse
Fixed in OP. Added one more case for custom recovery users.
Thanks for valuable input buddy.
mondalakash said:
Did you try dirty unicorn RC latest build?
Click to expand...
Click to collapse
Nope buddy. Did you? Any feedback?
shashank1320 said:
Nope buddy. Did you? Any feedback?
Click to expand...
Click to collapse
using this method relocks bootloader?
mondalakash said:
using this method relocks bootloader?
Click to expand...
Click to collapse
No. It wont
Only dload or manual relock does
shashank1320 said:
No. It wont
Only dload or manual relock does
Click to expand...
Click to collapse
Thanks buddy
shashank1320 said:
No. It wont
Only dload or manual relock does
Click to expand...
Click to collapse
Same bootloader unlock can be used multiple times for unlocking? Any idea
mondalakash said:
Same bootloader unlock can be used multiple times for unlocking? Any idea
Click to expand...
Click to collapse
Yes. Code will remain the same throughout the phone lifecycle. It is based on phone serial number, product if amd IMEI which remains the same and unique for every phone
shashank1320 said:
Yes. Code will remain the same throughout the phone lifecycle. It is based on phone serial number, product if amd IMEI which remains the same and unique for every phone
Click to expand...
Click to collapse
Thanks buddy for these quick reply..I guess these recovery issues rom bootlopping issues will be fixed if huwaie gave l09 variants 8.1 update
---------- Post added at 07:07 PM ---------- Previous post was at 06:53 PM ----------
shashank1320 said:
Yes. Code will remain the same throughout the phone lifecycle. It is based on phone serial number, product if amd IMEI which remains the same and unique for every phone
Click to expand...
Click to collapse
Bro if flash system IMG of EU variant will this mean that I will on the EU update cycle?..I mean the dev pulled the system IMG from his V10 EU variant.…
mondalakash said:
Thanks buddy for these quick reply..I guess these recovery issues rom bootlopping issues will be fixed if huwaie gave l09 variants 8.1 update
---------- Post added at 07:07 PM ---------- Previous post was at 06:53 PM ----------
Bro if flash system IMG of EU variant will this mean that I will on the EU update cycle?..I mean the dev pulled the system IMG from his V10 EU variant.…
Click to expand...
Click to collapse
It will not allow to flash or wont boot.
You may need to flash the oeminfo file first and then system img. Had this been this easy, i would have rebranded to Indian version. See one of my debranding guide in signature
shashank1320 said:
It will not allow to flash or wont boot.
You may need to flash the oeminfo file first and then system img. Had this been this easy, i would have rebranded to Indian version. See one of my debranding guide in signature
Click to expand...
Click to collapse
Or I can pull my system ,boot,ramdisk by ADB since I haven't messed with the device apart from unlocking it
---------- Post added at 08:19 PM ---------- Previous post was at 08:11 PM ----------
mondalakash said:
Same bootloader unlock can be used multiple times for unlocking? Any idea
Click to expand...
Click to collapse
Using erecovery would be easier if u have fast internet and I heard it doesn't relock the bootloader
I mean the relock doesn't matter according to u as we can just use the code several times ...then I guess dload is easier only need a SD card...I mean it doesn't even matter which one of the scenarios we are in as mentioned by u in the OP.
mondalakash said:
Or I can pull my system ,boot,ramdisk by ADB since I haven't messed with the device apart from unlocking it
---------- Post added at 08:19 PM ---------- Previous post was at 08:11 PM ----------
Using erecovery would be easier if u have fast internet and I heard it doesn't relock the bootloader
I mean the relock doesn't according to u as we can just use the code several times ...then I guess dload is easier only need a SD card...I mean it doesn't even matter which one of the scenarios we are in as mentioned by u in the OP.
Click to expand...
Click to collapse
Erecovery download is difficult and give error many times.
Dload actually lock the bootloader and you will be on full stock.
In my case, i had to relock the bootloader as it was in bootloop and i knew relocking will give me erecovery to download.