I got a m8 yesterday after switching to T-mobile and I would really like to unlock/root/mod it. I've rooted other phones before and haven't had this much trouble with them.
I get through all of the steps, run fastboot flash unlocktoken Unlock_code.bin which runs fine (gives option to unlock or not, I select yes with the power button) and reboots the phone. The phone is wiped as it's supposed to be, and I turn off the fast boot and turn on usb debugging in the options after the basic set up. When I boot it into fastboot to install the recovery, it still says *** LOCKED *** at the top of the screen, and I get this when I try to install it
XXX-Inspiron-N5010:~/Downloads/fastboot$ sudo fastboot flash recovery Recovery.img
[sudo] password for XXX:
target reported max download size of 1830608896 bytes
sending 'recovery' (14818 KB)...
OKAY [ 1.635s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.169s
I've tried this on two different computers and with different recovery files, one running Windows 8 and the other Ubuntu five times and I can't find anyone else that has had the same problem. I would appreciate any help with this as it's getting quite frustrating
Ditt0 - I have the same problem
Kittycatpenut said:
I got a m8 yesterday after switching to T-mobile and I would really like to unlock/root/mod it. I've rooted other phones before and haven't had this much trouble with them.
I get through all of the steps, run fastboot flash unlocktoken Unlock_code.bin which runs fine (gives option to unlock or not, I select yes with the power button) and reboots the phone. The phone is wiped as it's supposed to be, and I turn off the fast boot and turn on usb debugging in the options after the basic set up. When I boot it into fastboot to install the recovery, it still says *** LOCKED *** at the top of the screen, and I get this when I try to install it
XXX-Inspiron-N5010:~/Downloads/fastboot$ sudo fastboot flash recovery Recovery.img
[sudo] password for XXX:
target reported max download size of 1830608896 bytes
sending 'recovery' (14818 KB)...
OKAY [ 1.635s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.169s
I've tried this on two different computers and with different recovery files, one running Windows 8 and the other Ubuntu five times and I can't find anyone else that has had the same problem. I would appreciate any help with this as it's getting quite frustrating
Click to expand...
Click to collapse
I'm experiencing the same thing. Can't flash recovery. Have followed instructions to Unlock bootloader through HTCdev and have gone through the process numerous times on different machines without any apparent error. Please help!
target reported max download size of 1830608896 bytes
sending 'recovery' (16576 KB)...
OKAY [ 1.479s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.093s
Dumb question #1
Have you tried different USB ports just to zero out all variables
---------- Post added at 07:07 AM ---------- Previous post was at 07:07 AM ----------
Either of you two
---------- Post added at 07:54 AM ---------- Previous post was at 07:07 AM ----------
@Kittycatpenut
@andersonwittekind
I would ask in the T-Mobile forum only cause you might find an answer faster
http://forum.xda-developers.com/showthread.php?t=2725099
Hi all.
Here Android N for Swift
Needed files here -> https://secure.wlfx.tech
Latest = DP2
Manual:
Unlock bootloader
Install TWRP
Install OEM
Download OEM oem.img
Enter commands into fastboot
Code:
fastboot -i 0x2970 erase oem
Code:
fastboot -i 0x2970 flash oem oem.img
Download files from here (Only System and Boot)
Flash files
Code:
fastboot flash boot boot.img
Code:
fastboot flash system system.img
Reboot into TWRP
Make wipe data & wipe cache
Reboot phone
All works fine.
Sorry for my bad english and russian site server.
FindYanot said:
Hi all.
Here Android N for Swift
Needed files here -> https://secure.wlfx.tech/ANDROIDN
Manual:
Wipe data
Bot into fastboot
Use this commands:
fastboot flash boot boot.img
fastboot flash oem oem.img
fastboot flash system system.img
All works fine.
Sorry for my bad english and russian site server.
Click to expand...
Click to collapse
IFlashed. Works fine so far. Gapps are included in preview. Many thanks
FindYanot said:
Hi all.
Here Android N for Swift
Needed files here -> https://secure.wlfx.tech
Manual:
Wipe data
Bot into fastboot
Use this commands:
fastboot flash boot boot.img
fastboot flash oem oem.img
fastboot flash system system.img
All works fine.
Sorry for my bad english and russian site server.
Click to expand...
Click to collapse
Just curious. Does it have root? I am going to flash if in an hour or 2
---------- Post added at 05:55 AM ---------- Previous post was at 05:33 AM ----------
yasteellutch said:
Just curious. Does it have root? I am going to flash if in an hour or 2
Click to expand...
Click to collapse
Does it have OTA?
---------- Post added at 06:32 AM ---------- Previous post was at 05:55 AM ----------
yasteellutch said:
Just curious. Does it have root? I am going to flash if in an hour or 2
---------- Post added at 05:55 AM ---------- Previous post was at 05:33 AM ----------
Does it have OTA?
Click to expand...
Click to collapse
I am having an issue flashing. I flash using TWRP and when I reboot it says "No OS Installed". Also when I tried via fastboot. Is there any thing I am missing?
No root and OTA.
Before flashing via fastboot wipe data through twrp.
mermigas said:
No root and OTA.
Before flashing via fastboot wipe data through twrp.
Click to expand...
Click to collapse
Could you upload a screenshot?
mermigas said:
No root and OTA.
Before flashing via fastboot wipe data through twrp.
Click to expand...
Click to collapse
I did exactly that and still stuck in boot
http://4pda.ru/forum/index.php?showtopic=730213&st=120#entry47858392
Use Google translate to see instructions
Phew! some development on the Crackling!
:good:
Very impressed... TWRP method didn't wrk, fastboot worked fine! thankyou for bringing it here too, my Russian is non existent
My 1st impressions:
Very good, I haven't encountered any major issues..... I'll keep testing
Well, I just installed on my trusty Wileyfox Swift.
Overall I'm impressed, however the sensors are not working- gyro/ accelerometer/ proximity. There is some conflict with libraries when starting a game.
With a few more updates (fingers crossed) I can see myself using it as a daily driver
Everything else works and works really well. The phone seems a lot faster, the SDcard was formatted (haven't tested using an app from it but games are out of the question anyway), dual-window will be neat and is fine at the moment.
There is a lot to like here with few issues.
PS: After reading a bit from the older threads on XDA and from 4pda.ru , it seems the sensor issue is connected to the bridge to enable Android One roms with FindYanot's oem image on our crackling. Really impressive thus far. I wonder if we can flash General Mobile 4G firmware with QFIL?
I've tried this firmware on my phone and I'd like to share both experience and expressions.
Main laptop is MacBook Air, so it was quite hard to find working fastboot, adb ot GUI utilities.
Finally, I've installed them with command:
Code:
bash <(curl -s https://raw.githubusercontent.com/corbindavenport/nexus-tools/master/install.sh)
Then I tried to unlock the bootloader and flash images:
Code:
Sergeys-MacBook-Air:tools cleversokol$ adb devices
List of devices attached
adb server is out of date. killing...
adb I 4550 408520 usb_osx.cpp:259] Found vid=2970 pid=2282 serial=bf2ecad9
adb I 4550 408520 usb_osx.cpp:259]
* daemon started successfully *
bf2ecad9 unauthorized
Sergeys-MacBook-Air:tools cleversokol$ adb reboot bootloader
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Sergeys-MacBook-Air:tools cleversokol$ adb reboot bootloader
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
bf2ecad9 fastboot
Sergeys-MacBook-Air:tools cleversokol$ fastboot -i 0x2970 oem unlock-go
< waiting for any device >
^C
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
bf2ecad9 fastboot
As you can see, I had failed unlocking the bootloader and I did not install TWRP. Also, without TWRP I had not done wipe.
Code:
Sergeys-MacBook-Air:tools cleversokol$ fastboot reboot
rebooting...
finished. total time: 0.002s
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
Sergeys-MacBook-Air:tools cleversokol$ adb reboot bootloader
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
bf2ecad9 fastboot
Sergeys-MacBook-Air:tools cleversokol$ fastboot -i 0x2970 oem unlock-go
< waiting for any device >
^C
Sergeys-MacBook-Air:tools cleversokol$ fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (18457 KB)...
OKAY [ 0.667s]
writing 'boot'...
OKAY [ 1.835s]
finished. total time: 2.502s
Sergeys-MacBook-Air:tools cleversokol$ fastboot flash oem oem.img
target reported max download size of 268435456 bytes
sending 'oem' (6128 KB)...
OKAY [ 0.224s]
writing 'oem'...
OKAY [ 0.734s]
finished. total time: 0.958s
Sergeys-MacBook-Air:tools cleversokol$ fastboot flash system system.img
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 1.131s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.011s]
writing 'system'...
OKAY [ 21.393s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.789s]
writing 'system'...
OKAY [ 20.547s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.854s]
writing 'system'...
OKAY [ 20.591s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.522s]
writing 'system'...
OKAY [ 20.518s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.106s]
writing 'system'...
OKAY [ 21.263s]
sending sparse 'system' (23028 KB)...
OKAY [ 0.978s]
writing 'system'...
OKAY [ 1.729s]
finished. total time: 165.433s
Sergeys-MacBook-Air:tools cleversokol$ fastboot reboot
rebooting...
finished. total time: 0.001s
Sergeys-MacBook-Air:tools cleversokol$ fastboot reboot
< waiting for any device >
After flashing this three images I got a brick. Phone showed Wileyfox logo once and turned off. After ejecting/inserting battery, it responsed (once) to Power button, but showed only logo and turned off again.
Eject/insert battery again and pressing Power + VolDown took me to some menu. From it I've reached fastboot menu.
With windows-laptop and WileyFox Tool utility I pressed Check bootloader status button. Phone restarted and I got Android N boot animation. Then restarted again and finally I'm in Android N First Setup Utility.
Working:
— screen, touchscreen, brightness ajustment (manual)
— mic, speaker
— charging
— GPS
— 4G
— Wi-Fi
— camera (video does not work)
— night mode
— multi-window mode
Not working:
— sensors
— some apps show library mismatch
Also, Power + VolDown button now does not take me to recovery menu. It shows android with red exclamation point. I think it's not right.
cleversokol said:
I've tried this firmware on my phone and I'd like to share both experience and expressions.
Main laptop is MacBook Air, so it was quite hard to find working fastboot, adb ot GUI utilities.
Finally, I've installed them with command:
Code:
bash <(curl -s https://raw.githubusercontent.com/corbindavenport/nexus-tools/master/install.sh)
Then I tried to unlock the bootloader and flash images:
Code:
Sergeys-MacBook-Air:tools cleversokol$ adb devices
List of devices attached
adb server is out of date. killing...
adb I 4550 408520 usb_osx.cpp:259] Found vid=2970 pid=2282 serial=bf2ecad9
adb I 4550 408520 usb_osx.cpp:259]
* daemon started successfully *
bf2ecad9 unauthorized
Sergeys-MacBook-Air:tools cleversokol$ adb reboot bootloader
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Sergeys-MacBook-Air:tools cleversokol$ adb reboot bootloader
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
bf2ecad9 fastboot
Sergeys-MacBook-Air:tools cleversokol$ fastboot -i 0x2970 oem unlock-go
< waiting for any device >
^C
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
bf2ecad9 fastboot
As you can see, I had failed unlocking the bootloader and I did not install TWRP. Also, without TWRP I had not done wipe.
Code:
Sergeys-MacBook-Air:tools cleversokol$ fastboot reboot
rebooting...
finished. total time: 0.002s
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
Sergeys-MacBook-Air:tools cleversokol$ adb reboot bootloader
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
bf2ecad9 fastboot
Sergeys-MacBook-Air:tools cleversokol$ fastboot -i 0x2970 oem unlock-go
< waiting for any device >
^C
Sergeys-MacBook-Air:tools cleversokol$ fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (18457 KB)...
OKAY [ 0.667s]
writing 'boot'...
OKAY [ 1.835s]
finished. total time: 2.502s
Sergeys-MacBook-Air:tools cleversokol$ fastboot flash oem oem.img
target reported max download size of 268435456 bytes
sending 'oem' (6128 KB)...
OKAY [ 0.224s]
writing 'oem'...
OKAY [ 0.734s]
finished. total time: 0.958s
Sergeys-MacBook-Air:tools cleversokol$ fastboot flash system system.img
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 1.131s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.011s]
writing 'system'...
OKAY [ 21.393s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.789s]
writing 'system'...
OKAY [ 20.547s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.854s]
writing 'system'...
OKAY [ 20.591s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.522s]
writing 'system'...
OKAY [ 20.518s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.106s]
writing 'system'...
OKAY [ 21.263s]
sending sparse 'system' (23028 KB)...
OKAY [ 0.978s]
writing 'system'...
OKAY [ 1.729s]
finished. total time: 165.433s
Sergeys-MacBook-Air:tools cleversokol$ fastboot reboot
rebooting...
finished. total time: 0.001s
Sergeys-MacBook-Air:tools cleversokol$ fastboot reboot
< waiting for any device >
After flashing this three images I got a brick. Phone showed Wileyfox logo once and turned off. After ejecting/inserting battery, it responsed (once) to Power button, but showed only logo and turned off again.
Eject/insert battery again and pressing Power + VolDown took me to some menu. From it I've reached fastboot menu.
With windows-laptop and WileyFox Tool utility I pressed Check bootloader status button. Phone restarted and I got Android N boot animation. Then restarted again and finally I'm in Android N First Setup Utility.
Working:
— screen, touchscreen, brightness ajustment (manual)
— mic, speaker
— charging
— GPS
— 4G
— Wi-Fi
— camera (video does not work)
— night mode
— multi-window mode
Not working:
— sensors
— some apps show library mismatch
Also, Power + VolDown button now does not take me to recovery menu. It shows android with red exclamation point. I think it's not right.
Click to expand...
Click to collapse
I've had the opposite experience. Fastboot works without fail on Mac and Linux. Windows- not so much with the Swift.
Flash TWRP manually - fastboot flash recovery your_recovery_image.img (replace with the file name for TWRP)
You've just installed the patched oem.img (to allow code name "seed" images) along with boot and system. Can't boot to recovery if you don't have one
Steer away from flashing other files from the Android One stock image (it will be even messier hardbrick and you would have to follow the instructions from the other thread).
If you want to return to stock COS, follow the instructions from these awesome people : http://forum.cyanogenmod.org/topic/118287-manual-flashing-of-stock-cyanogenos/
PS: For some reason, unlocking the bootloader for me worked with: fastboot oem unlock-go
but not with:
fastboot -i 0x2970 oem unlock-go
Locking with: fastboot oem lock-go , worked as expected
Can I use this TWRP? I did not found Wileyfox Swift among supported devices.
cleversokol said:
Can I use this TWRP? I did not found Wileyfox Swift among supported devices.
Click to expand...
Click to collapse
I believe this is the one I've used.
In case the Windows tool for Wileyfox works for you (I'm missing some C# utilities on mine and can't deal with it atm), you can add TWRP from there as well.
PS: I used it only to install initially this preview. I haven't used it after.
Sucessfully installed TWRP3.0 (CM13-nightly-recovery did not work for me. Keep getting image of Android with red exclamation mark), wiped cache, data and installed CM13-nightly + GAPPS Mini. Booted into CM, did basic setup. After that I wanted to re-lock the bootloader.
With
Code:
fastboot oem lock-go
it worked, but after this command I got brick-phone again.
Only replacing the battery + re-unlocking the device helped to restore it.
Is there a way to keep device working with locked bootloader?
Lock the bootloader only if you'll be using stock signed images of CyanogenOS. That is in case you will have to return the device due to hardware fault- dead pixels, non functioning microphones/ speakers, etc. Another reason as of why you might want to relock, is to ensure that you'll be using CyanogenOS recovery and no problems with future OTAs (no guarantee there as encrypted devices had problems with first official update but things are looking nice for future official OTAs).
If you want to use custom recovery- TWRP/CMRecovery by itself or along with CyanogenMod13 or any other custom ROM- do not lock the bootloader.
These are your options Keep the bootloader unlocked unless you have the need/ desire to return it to true stock.
I tried to install it again and it doesn't work. I flashed stock and unlocked my bootloader. I managed to flash OEM and BOOT but it doesn't want to flash the system partition at all. I tried everything. I tried 4pda method too. Am I missing something?
yasteellutch said:
I tried to install it again and it doesn't work. I flashed stock and unlocked my bootloader. I managed to flash OEM and BOOT but it doesn't want to flash the system partition at all. I tried everything. I tried 4pda method too. Am I missing something?
Click to expand...
Click to collapse
System img is big and post propably your fastboot installer cannot handle it.
Try this fastboot installer
http://forum.xda-developers.com/showthread.php?t=2588979
This is the one I'm using. Mininimal adb and and fastboot . it won't work. Even tried with android studio
---------- Post added at 12:26 PM ---------- Previous post was at 12:25 PM ----------
yasteellutch said:
This is the one I'm using. Mininimal adb and and fastboot . it won't work. Even tried with android studio
Click to expand...
Click to collapse
It keeps on saying sending sparse system img(0kb)
yasteellutch said:
This is the one I'm using. Mininimal adb and and fastboot . it won't work. Even tried with android studio
---------- Post added at 12:26 PM ---------- Previous post was at 12:25 PM ----------
It keeps on saying sending sparse system img(0kb)
Click to expand...
Click to collapse
Just try this
http://androidhost.org/P2XKs
unzip to your root directory - copy Android N images to this directory and give it a try.
mermigas said:
Just try this
http://androidhost.org/P2XKs
unzip to your root directory - copy Android N images to this directory and give it a try.
Click to expand...
Click to collapse
This is what I get
Hi, I have a OnePlus 3 that boot loops, with no recovery. Holding Volume Button + Power does not work, the only option is fast boot.
When trying to Flash a new recovery i get the following ..
Code:
c:\>fastboot flash recovery cm-13.0-20160814-NIGHTLY-oneplus3-recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (14952 KB)...
OKAY [ 0.397s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.445s
c:\>fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.016s
My Question, Is there a way to unlock partitions via fastboot. or can you sugest a thread or solution to this issue.
Thanks
You must be able to toggle the "Allow OEM Unlock" switch in developer options to unlock the bootloader so unless you can get there then you've got a brick.
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
[GUIDE] Mega Unbrick Guide for A Hard Bricked OnePlus 3
I was stuck here as well. You can push an update through fastboot/adb. It takes FOREVER, but you'll at least have a phone that works. Try and push recovery once you can oem unlock
This Worked.
Thanks, This Worked for me.
mohsen8 said:
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
[GUIDE] Mega Unbrick Guide for A Hard Bricked OnePlus 3
Click to expand...
Click to collapse
Hi all,
I seen this community and some peoples very expert of honor 7x in many post pls help me to up to life my phone....... i continusly testing honor 7x because i love this model but something went wrong this time........... i forget to install twrprecovery and unfortunatly lock bootloader because in my mind i think when lock or relock the phone do hard reset and all partition go in right place.......but........ i think the phone erase all data and now i have bootloader loked frp loked and twrp screen bootloop when try to open phone with all conbination of key + pc don't recognized fastboot metod.... so i unmonted honor 7x and unmounted battery press volume down+power+usb cable and only in this way i can put file in phone with rescue mode fastboot and adb recognized the device "fastboot devices" with serial but frp and bootloader still locked.....
P.s.
-IF SOME ONE CAN HELP ME I WANT ONLY PUT STOCK RECOVERY OR TWRP then i can unbrick myself.. thank's hope in a responze me i'm so mad for this unluky brick because i do many attention when mod android device -_- but this time evil come to brick.....
-OR REMOUNT ALL IMAGES FILE BUT WITH DEVICE IN THIS STATE IS VERY difficult.....
-OR UNLOCK BOOTLOADER WITHOUT ENTER IN DEVELOPPERS OPTION I MEAN IN FAST BOOT BECAUSE I ONLY CAN USE RESCUE MODE..
here the results of fast boot mode hlep me and i can support you:
PS C:\adb> fastboot oem get-product-model
...
(bootloader) BND-L21
OKAY [ 0.000s]
finished. total time: 0.000s
PS C:\adb> fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.016s
PS C:\adb> fastboot oem get-build-number
...
(bootloader) :BND-L21 8.0.0.302(C432log)
OKAY [ 0.016s]
finished. total time: 0.016s
PS C:\adb> fastboot getvar rescue_enter_recovery
getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
finished. total time: 0.016s
PS C:\adb> fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :BND-L21C432B121CUSTC432D001
OKAY [ 0.016s]
finished. total time: 0.016s
FAILED dload folder with oreo update.app single file or with other files in the zip..........
FAILED TO flash in fastboot rescue mode system (fastboot flash system system.img or other files .img).......
FAILED ALL TENTATIVES TO FLASH RECOVERY MANY TYPE ... because bootloader is closed.........
PS C:\adb> fastboot boot C:\adb\twrpimgmount_ramdisk.img
downloading 'boot.img'...
OKAY [ 0.501s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.517s
PS C:\adb> fastboot boot C:\adb\BND-RECOVERY-NoCheck.img
downloading 'boot.img'...
OKAY [ 1.222s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 1.238s
PS C:\adb> fastboot boot C:\adb\twrp_openkirin_sudeep.img
downloading 'boot.img'...
OKAY [ 0.851s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.853s
PS C:\adb> fastboot boot C:\adb\twrp_ramdisk_oreo_19-4-18.img
downloading 'boot.img'...
OKAY [ 0.801s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.801s
PLEASE TELL ME YOUR OPINION or if i paied FUNKY HUAWEI SOFTWARE for unbrick ..... or buy new mainboard.............
BEST REGARDS TO ALL COMUNITY....
JKmamba$ said:
Hi all,
I seen this community and some peoples very expert of honor 7x in many post pls help me to up to life my phone....... i continusly testing honor 7x because i love this model but something went wrong this time........... i forget to install twrprecovery and unfortunatly lock bootloader because in my mind i think when lock or relock the phone do hard reset and all partition go in right place.......but........ i think the phone erase all data and now i have bootloader loked frp loked and twrp screen bootloop when try to open phone with all conbination of key + pc don't recognized fastboot metod.... so i unmonted honor 7x and unmounted battery press volume down+power+usb cable and only in this way i can put file in phone with rescue mode fastboot and adb recognized the device "fastboot devices" with serial but frp and bootloader still locked.....
P.s.
-IF SOME ONE CAN HELP ME I WANT ONLY PUT STOCK RECOVERY OR TWRP then i can unbrick myself.. thank's hope in a responze me i'm so mad for this unluky brick because i do many attention when mod android device -_- but this time evil come to brick.....
-OR REMOUNT ALL IMAGES FILE BUT WITH DEVICE IN THIS STATE IS VERY difficult.....
-OR UNLOCK BOOTLOADER WITHOUT ENTER IN DEVELOPPERS OPTION I MEAN IN FAST BOOT BECAUSE I ONLY CAN USE RESCUE MODE..
here the results of fast boot mode hlep me and i can support you:
PS C:\adb> fastboot oem get-product-model
...
(bootloader) BND-L21
OKAY [ 0.000s]
finished. total time: 0.000s
PS C:\adb> fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.016s
PS C:\adb> fastboot oem get-build-number
...
(bootloader) :BND-L21 8.0.0.302(C432log)
OKAY [ 0.016s]
finished. total time: 0.016s
PS C:\adb> fastboot getvar rescue_enter_recovery
getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
finished. total time: 0.016s
PS C:\adb> fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :BND-L21C432B121CUSTC432D001
OKAY [ 0.016s]
finished. total time: 0.016s
FAILED dload folder with oreo update.app single file or with other files in the zip..........
FAILED TO flash in fastboot rescue mode system (fastboot flash system system.img or other files .img).......
FAILED ALL TENTATIVES TO FLASH RECOVERY MANY TYPE ... because bootloader is closed.........
PS C:\adb> fastboot boot C:\adb\twrpimgmount_ramdisk.img
downloading 'boot.img'...
OKAY [ 0.501s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.517s
PS C:\adb> fastboot boot C:\adb\BND-RECOVERY-NoCheck.img
downloading 'boot.img'...
OKAY [ 1.222s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 1.238s
PS C:\adb> fastboot boot C:\adb\twrp_openkirin_sudeep.img
downloading 'boot.img'...
OKAY [ 0.851s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.853s
PS C:\adb> fastboot boot C:\adb\twrp_ramdisk_oreo_19-4-18.img
downloading 'boot.img'...
OKAY [ 0.801s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.801s
PLEASE TELL ME YOUR OPINION or if i paied FUNKY HUAWEI SOFTWARE for unbrick ..... or buy new mainboard.............
BEST REGARDS TO ALL COMUNITY....
Click to expand...
Click to collapse
this needs to come here n the open, not in my PM.
PS C:\adb> fastboot flash rescue_recovery_ramdisk C:\adb\twrp_openkirin_sudeep.img
target reported max download size of 471859200 bytes
sending 'rescue_recovery_ramdisk' (25164 KB)...
OKAY [ 0.854s]
writing 'rescue_recovery_ramdisk'...
OKAY [ 0.031s]
finished. total time: 0.885s
PS C:\adb> fastboot reboot
rebooting...
Click to expand...
Click to collapse
recovery flashed while frp and bootloader locked.
!!!!!!!!!!!!!
---------- Post added at 06:55 PM ---------- Previous post was at 06:16 PM ----------
What happens after reboot, try to boot to recovery with volume button, when you use
Code:
fastboot flash rescue_recovery_ramdisk RECOVERY_RAMDIS.img
recovery_ramdisk
does phone still have your broken twrp or the stock recovery?
JKmamba$ said:
https://ibb.co/nKOuRT
https://ibb.co/ccECD8
https://ibb.co/m1qxfo
for new users prevented post external link sorry .... you can for me?
Click to expand...
Click to collapse
so the fastboot command shows ok flashed, but its not changing the loaded recovery image.
don't know what to suggest next.
JKmamba$ said:
Hi all,
I seen this community and some peoples very expert of honor 7x in many post pls help me to up to life my phone....... i continusly testing honor 7x because i love this model but something went wrong this time........... i forget to install twrprecovery and unfortunatly lock bootloader because in my mind i think when lock or relock the phone do hard reset and all partition go in right place.......but........ i think the phone erase all data and now i have bootloader loked frp loked and twrp screen bootloop when try to open phone with all conbination of key + pc don't recognized fastboot metod.... so i unmonted honor 7x and unmounted battery press volume down+power+usb cable and only in this way i can put file in phone with rescue mode fastboot and adb recognized the device "fastboot devices" with serial but frp and bootloader still locked.....
P.s.
-IF SOME ONE CAN HELP ME I WANT ONLY PUT STOCK RECOVERY OR TWRP then i can unbrick myself.. thank's hope in a responze me i'm so mad for this unluky brick because i do many attention when mod android device -_- but this time evil come to brick.....
-OR REMOUNT ALL IMAGES FILE BUT WITH DEVICE IN THIS STATE IS VERY difficult.....
-OR UNLOCK BOOTLOADER WITHOUT ENTER IN DEVELOPPERS OPTION I MEAN IN FAST BOOT BECAUSE I ONLY CAN USE RESCUE MODE..
here the results of fast boot mode hlep me and i can support you:
PS C:\adb> fastboot oem get-product-model
...
(bootloader) BND-L21
OKAY [ 0.000s]
finished. total time: 0.000s
PS C:\adb> fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.016s
PS C:\adb> fastboot oem get-build-number
...
(bootloader) :BND-L21 8.0.0.302(C432log)
OKAY [ 0.016s]
finished. total time: 0.016s
PS C:\adb> fastboot getvar rescue_enter_recovery
getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
finished. total time: 0.016s
PS C:\adb> fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :BND-L21C432B121CUSTC432D001
OKAY [ 0.016s]
finished. total time: 0.016s
FAILED dload folder with oreo update.app single file or with other files in the zip..........
FAILED TO flash in fastboot rescue mode system (fastboot flash system system.img or other files .img).......
FAILED ALL TENTATIVES TO FLASH RECOVERY MANY TYPE ... because bootloader is closed.........
PS C:\adb> fastboot boot C:\adb\twrpimgmount_ramdisk.img
downloading 'boot.img'...
OKAY [ 0.501s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.517s
PS C:\adb> fastboot boot C:\adb\BND-RECOVERY-NoCheck.img
downloading 'boot.img'...
OKAY [ 1.222s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 1.238s
PS C:\adb> fastboot boot C:\adb\twrp_openkirin_sudeep.img
downloading 'boot.img'...
OKAY [ 0.851s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.853s
PS C:\adb> fastboot boot C:\adb\twrp_ramdisk_oreo_19-4-18.img
downloading 'boot.img'...
OKAY [ 0.801s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.801s
PLEASE TELL ME YOUR OPINION or if i paied FUNKY HUAWEI SOFTWARE for unbrick ..... or buy new mainboard.............
BEST REGARDS TO ALL COMUNITY....
Click to expand...
Click to collapse
HI, You said if you could put stock recovery then you can unbrick yourself. Can you elaborate on this please? Also, you tried the load method with the update.app so can you tell me where did you get that file? I'm in the same situation. I locked myself out completely trusting that the dload update.app method so that I could go back to complete stock as I was stuck in the emui 8 beta earlier with twrp installed with twrp backups. I have stock recovery "RECOVERY_RAMDIS.IMG" installed on my phone. I flashed it to get rid of TWRP so I could be on stock recovery.
I flashed stock recovery, relocked bootloader and tried the dload method and every time it fails at 5%. I'm using BND AL10C675 (INDIAN) so now I can't unlock bootloader because I need to enable "OEM unlock" in settings and I can't do that cos I can't boot into system as the system is formatted (NO OS) and so I can't install twrp or any system images nothing. I just locked myself out and I can't believe it. **** does happen
Thetpcguy said:
HI, You said if you could put stock recovery then you can unbrick yourself. Can you elaborate on this please? Also, you tried the load method with the update.app so can you tell me where did you get that file? I'm in the same situation. I locked myself out completely trusting that the dload update.app method so that I could go back to complete stock as I was stuck in the emui 8 beta earlier with twrp installed with twrp backups. I have stock recovery "RECOVERY_RAMDIS.IMG" installed on my phone. I flashed it to get rid of TWRP so I could be on stock recovery.
I flashed stock recovery, relocked bootloader and tried the dload method and every time it fails at 5%. I'm using BND AL10C675 (INDIAN) so now I can't unlock bootloader because I need to enable "OEM unlock" in settings and I can't do that cos I can't boot into system as the system is formatted (NO OS) and so I can't install twrp or any system images nothing. I just locked myself out and I can't believe it. **** does happen
Click to expand...
Click to collapse
let me chek man take a pictures of all single screen you'll see... RECOVERY, AFTER RECOVERY (bootloop logo, black screen ecc), and FAST BOOT MODE.. maybe i help you ... i won't to roll back my device because oreo is very perfomance but so buggy for exemple bluethoot don't worck multy shut on photograf bugged or many root application work and after 5 min close with (root with magisk -_-")... in nougat don't have ever this problem root with only super su and all unlocked....
Hi
Boot loader unlock issue on zui 2.5.104st nugat based os it will not unlocked properly
That message will be appeared like this
fastboot -i 0x2b4c flash unlock unlock_bootloader.img
target reported max download size of 1610612736 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.028s]
writing 'unlock'...
FAILED (remote: unlock failed)
finished. total time: 0.061s"
Any one know this issue please help me how to solve this issue
Thankyou
Same issue
---------- Post added at 04:44 PM ---------- Previous post was at 04:41 PM ----------
Mine says 'writing unlock FAILED < remote: partition doesn't exist >'