Related
KF HDX only boots into fastboot, I'm trying to install TWRP Recovery, then hopefully after an image
fastboot -i 0x1949 flash recovery thor-twrp-3.0.0-0.img
target reported max download size of 536870912 bytes
sending 'recovery' (9294 KB)...
OKAY [ 0.391s]
writing 'recovery'...
FAILED (remote: flashing not allowed for locked hw)
finished. total time: 0.442s
fastboot -i 0x1949 oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
./fastboot -i 0x1949 oem idme
...
FAILED (remote: oem idme not allowed for locked hw)
finished. total time: 0.055s
I get ADB for a few seconds before it goes into fastboot
[email protected]:/ $ cat /sys/block/mmcblk0/device/manfid
0x000015
[email protected]:/ $ cat /sys/block/mmcblk0/device/serial
0x8c0f5453
I'v created the unlock file
fastboot -i 0x1949 flash unlock unlock.signed
target reported max download size of 536870912 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.090s]
writing 'unlock'...
FAILED (remote: Unlock code is NOT correct) **** I've checked this several times
finished. total time: 0.153s
Is it terminal?
Do you follow the steps of this thread correctly?
https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
I had the same issue some time ago, in my case the problem was some strange windows 10 compatibility which block /denied flash the code.
I repeat the process on my old windows Vista desktop ,without errors, dont ask why changed between systems, but works for me.
Check the drivers are installed correctly, aboot and twrp files
Remeber first get the unlock code, second use adb to send TWRP and Aboot files to the Kindle, and finally proceed flash unlock code.
RealSlimShady72 said:
KF HDX only boots into fastboot, I'm trying to install TWRP Recovery, then hopefully after an image
fastboot -i 0x1949 flash recovery thor-twrp-3.0.0-0.img
target reported max download size of 536870912 bytes
sending 'recovery' (9294 KB)...
OKAY [ 0.391s]
writing 'recovery'...
FAILED (remote: flashing not allowed for locked hw)
finished. total time: 0.442s
fastboot -i 0x1949 oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
./fastboot -i 0x1949 oem idme
...
FAILED (remote: oem idme not allowed for locked hw)
finished. total time: 0.055s
I get ADB for a few seconds before it goes into fastboot
[email protected]:/ $ cat /sys/block/mmcblk0/device/manfid
0x000015
[email protected]:/ $ cat /sys/block/mmcblk0/device/serial
0x8c0f5453
I'v created the unlock file
fastboot -i 0x1949 flash unlock unlock.signed
target reported max download size of 536870912 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.090s]
writing 'unlock'...
FAILED (remote: Unlock code is NOT correct) **** I've checked this several times
finished. total time: 0.153s
Is it terminal?
Click to expand...
Click to collapse
How did the device get into this state?
Did you install the vulnerable aboot before attempting to flash TWRP? If not the installation will fail. Nor can a non-vulnerable bootloader be unlocked.
If you can not establish a stable adb (not fastboot) session you will need to force the device into 'bulk mode' and then attempt to install the vulnerable bootloader.
Yousucks2 said:
Do you follow the steps of this thread correctly?
https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
I had the same issue some time ago, in my case the problem was some strange windows 10 compatibility which block /denied flash the code.
I repeat the process on my old windows Vista desktop ,without errors, dont ask why changed between systems, but works for me.
Check the drivers are installed correctly, aboot and twrp files
Remeber first get the unlock code, second use adb to send TWRP and Aboot files to the Kindle, and finally proceed flash unlock code.
Click to expand...
Click to collapse
Davey126 said:
How did the device get into this state?
Did you install the vulnerable aboot before attempting to flash TWRP? If not the installation will fail. Nor can a non-vulnerable bootloader be unlocked.
If you can not establish a stable adb (not fastboot) session you will need to force the device into 'bulk mode' and then attempt to install the vulnerable bootloader.
Click to expand...
Click to collapse
KF was working okay with Nexus 4.4.4 and TWRP I think was 2.7.x, my goal was to install a later Andriod OS. I had an issue with the KF where I only have one USB cable in the house that charges the tablet, the port on the tablet is not the best and if the cable moves slightly I lose the connection. KF was originally unlocked and via fastboot I was flashing TWRP 3.0 to the KF when the cable moved and lost connection, after that I get 'FAILED (remote: flashing not allowed for locked hw)' error when trying to reflash now
adb I get about 20 seconds before the KF continues to fastboot - I don't no how to halt from going to fastboot
From Windows 10 I can use adb but when the KF goes to fastboot I get a triangle on the device file (Windows Device Manager), fastboot does not see the device - I've also installed the KF drivers
OS X I can see the device from both adb and fastboot
Think its terminal now, only going into fastboot.....no more adb
RealSlimShady72 said:
KF was working okay with Nexus 4.4.4 and TWRP I think was 2.7.x, my goal was to install a later Andriod OS. I had an issue with the KF where I only have one USB cable in the house that charges the tablet, the port on the tablet is not the best and if the cable moves slightly I lose the connection. KF was originally unlocked and via fastboot I was flashing TWRP 3.0 to the KF when the cable moved and lost connection, after that I get 'FAILED (remote: flashing not allowed for locked hw)' error when trying to reflash now
adb I get about 20 seconds before the KF continues to fastboot - I don't no how to halt from going to fastboot
From Windows 10 I can use adb but when the KF goes to fastboot I get a triangle on the device file (Windows Device Manager), fastboot does not see the device - I've also installed the KF drivers
OS X I can see the device from both adb and fastboot
Click to expand...
Click to collapse
RealSlimShady72 said:
Think its terminal now, only going into fastboot.....no more adb
Click to expand...
Click to collapse
Too many variables in play (bad port, questionable cable, uncertain damage to bootloader and/or recovery, unreliable operation in current state). You need to address hardware issues before pursuing the sensitive business of attempting to rebuild your device which most likely will involve a trip through 'bulk mode'.
Davey126 said:
Too many variables in play (bad port, questionable cable, uncertain damage to bootloader and/or recovery, unreliable operation in current state). You need to address hardware issues before pursuing the sensitive business of attempting to rebuild your device which most likely will involve a trip through 'bulk mode'.
Click to expand...
Click to collapse
Properly not worth spending much more time now, been a bit of a learning curve though.
Cheeky call to Amazon and asked if they do repairs - NO but have 15% off:cyclops: another Kindle Fire Purchase so I got the $49.99 HD 8- 15%
RealSlimShady72 said:
Properly not worth spending much more time now, been a bit of a learning curve though.
Cheeky call to Amazon and asked if they do repairs - NO but have 15% off:cyclops: another Kindle Fire Purchase so I got the $49.99 HD 8- 15%
Click to expand...
Click to collapse
Nice score
Some real good progress thanks to Draxie ISO :good:. I've now got a recovery TWRP 3.1.1-1
Also now my unlock code worked!!
./fastboot -i 0x1949 flash unlock unlock.signed
target reported max download size of 536870912 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.085s]
writing 'unlock'...
OKAY [ 0.079s]
finished. total time: 0.164s
NO adb though
./adb devices
List of devices attached
D06FA0A0352200A9 unauthorized
EDIT:Tried for a couple of hours now and can't push an image to the KF HDX, there is no OS on the device and even in recovery I've tried to sideload adb but still can't push an image
Also tried to mount data to my Win 10 Pro PC but here now I'm getting a yellow triangle on MTP device.
Is there an system image for KF HDX Thor to installed via fastboot?
We have a fully working KF HDX :cyclops:
Followed the guide here to get MTP device drivers working
https://forum.xda-developers.com/showthread.php?t=2612503&nocache=1
copy over an image and off we go:laugh:
RealSlimShady72 said:
Some real good progress thanks to Draxie ISO :good:. I've now got a recovery TWRP 3.1.1-1
Also now my unlock code worked!!
:
EDIT:Tried for a couple of hours now and can't push an image to the KF HDX, there is no OS on the device and even in recovery I've tried to sideload adb but still can't push an image
Also tried to mount data to my Win 10 Pro PC but here now I'm getting a yellow triangle on MTP device.
Is there an system image for KF HDX Thor to installed via fastboot?
Click to expand...
Click to collapse
RealSlimShady72 said:
We have a fully working KF HDX :cyclops:
Followed the guide here to get MTP device drivers working
https://forum.xda-developers.com/showthread.php?t=2612503&nocache=1
copy over an image and off we go:laugh:
Click to expand...
Click to collapse
Well done - especially notable given the various obstacles that you faced. Demonstrates difficult device recoveries are possible with sufficient time, talent and research (occasionally a dab of luck). Enjoy your rejuvenated HDX!
Davey126 said:
Well done - especially notable given the various obstacles that you faced. Demonstrates difficult device recoveries are possible with sufficient time, talent and research (occasionally a dab of luck). Enjoy your rejuvenated HDX!
Click to expand...
Click to collapse
Lucky for me I had Win 10 and OS X
Windows was good for ADB and mounting the device with MTP but could not get fastboot working with Windows
OSX was good for ADB, fastboot and @draxie 1-click but fastboot was very limited as everything I threw at resulted in a 'FAILED (remote: flashing not allowed for locked hw)'
Be interesting to know which part off 1-click unlocked and pushed over the recovery.
Today I have a Gen 7 HD8 arriving, wonder how long that will take to break
adb sideload
RealSlimShady72 said:
EDIT:Tried for a couple of hours now and can't push an image to the KF HDX, there is no OS on the device and even in recovery I've tried to sideload adb but still can't push an image
Click to expand...
Click to collapse
I know it doesn't really matter anymore,
but I still wonder if it's only me that reads
too much into a hasty comment or were
you actually trying 'adb push' instead of
'adb sideload' to get your ROM over to
TWRP waiting to sideload? The reason
I'm asking is that had used adb sideload
numerous times (I even double-checked
when you were asking) and sideload had
always worked as expected...
draxie said:
I know it doesn't really matter anymore,
but I still wonder if it's only me that reads
too much into a hasty comment or were
you actually trying 'adb push' instead of
'adb sideload' to get your ROM over to
TWRP waiting to sideload? The reason
I'm asking is that had used adb sideload
numerous times (I even double-checked
when you were asking) and sideload had
always worked as expected...
Click to expand...
Click to collapse
Okay you've cleared this one up, I'm not familiar with adb or fastboot.....I tried to take in too much last few days
At no point did I try 'adb sideload' - I didn't even know that was an option but you've cleared that one up for me, I only ever used adb push even when I put the device into adb sideload via TWRP.
So my mistake as I overlooked the sideload option on the CLI
RealSlimShady72 said:
Lucky for me I had Win 10 and OS X
Windows was good for ADB and mounting the device with MTP but could not get fastboot working with Windows
OSX was good for ADB, fastboot and @draxie 1-click but fastboot was very limited as everything I threw at resulted in a 'FAILED (remote: flashing not allowed for locked hw)'
Be interesting to know which part off 1-click unlocked and pushed over the recovery.
Today I have a Gen 7 HD8 arriving, wonder how long that will take to break
Click to expand...
Click to collapse
Thanks for feedback. For others benefit there's a Windows driver package referenced in the another thread (here) that has proven reliable for HDX fastboot access on multiple Windows instances...mine and everyone else who has reported back. Just works despite being targeted for a different device. Call me crazy but I like things that are easy, work and carry no side effects. Kinda radical ...
Good day: I have a similar issue with showing
PS C:\Users\learned\Downloads\KindleFire\unlock> fastboot -i 0x1949 flash unlock unlock.code
target reported max download size of 1073741824 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.078s]
writing 'unlock'...
FAILED (remote: Unlock code is NOT correct)
finished. total time: 0.141s
My ADB and fastboot are working well and the Apollo HDX tablet is working fine.
You mentioned flashing aboot before trwp, etc. prior to unlocking. I thought the posts indicated that neither root nor twrp was required to unlock the boot loader?
I created an unlock code for both Thor and Apollo and, both were created successfully. Thor has root and recovery and Apollo has not been altered at all. Trying to run to flash the respective unlock code to both Thor and Apollo fails showing me "FAILED (remote: Unlock code is NOT correct)"
Why would the unlock code be incorrect?
When I created the unlock code for Apollo moments ago, I received two codes at the powershell prompt.
1664 KB/s (506072 bytes in 0.296s)
0x000015 0xfc155609
0 KB/s (256 bytes in 1.000s)
Press any key to continue . .
I presume the two hex codes I received should be correct? Can I manually push the two unlock codes to the tablet aside from the unlock.bat file? I am not sure what is in the unlock.code file created by the get_code.bat file.
galearned said:
You mentioned flashing aboot before trwp, etc. prior to unlocking. I thought the posts indicated that neither root nor twrp was required to unlock the boot loader?
Click to expand...
Click to collapse
A 'vulnerable' aboot must be flashed prior to installing TWRP and/or unlocking the bootloader. You can only flash aboot if: 1) root is available; or 2) the device is placed in 'bulk mode'. Both approaches have their pros/cons.
Please consult the first post in this lengthy thread for an overview of the process then skip to a post near the end by @ReichMann for a nice compilation of files and associated procedures. Note this is only one of several ways to get the job done.
Update to Unlock Code Incorrect
galearned said:
Good day: I have a similar issue with showing
PS C:\Users\learned\Downloads\KindleFire\unlock> fastboot -i 0x1949 flash unlock unlock.code
target reported max download size of 1073741824 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.078s]
writing 'unlock'...
FAILED (remote: Unlock code is NOT correct)
finished. total time: 0.141s
My ADB and fastboot are working well and the Apollo HDX tablet is working fine.
You mentioned flashing aboot before trwp, etc. prior to unlocking. I thought the posts indicated that neither root nor twrp was required to unlock the boot loader?
I created an unlock code for both Thor and Apollo and, both were created successfully. Thor has root and recovery and Apollo has not been altered at all. Trying to run to flash the respective unlock code to both Thor and Apollo fails showing me "FAILED (remote: Unlock code is NOT correct)"
Why would the unlock code be incorrect?
When I created the unlock code for Apollo moments ago, I received two codes at the powershell prompt.
1664 KB/s (506072 bytes in 0.296s)
0x000015 0xfc155609
0 KB/s (256 bytes in 1.000s)
Press any key to continue . .
I presume the two hex codes I received should be correct? Can I manually push the two unlock codes to the tablet aside from the unlock.bat file? I am not sure what is in the unlock.code file created by the get_code.bat file.
Click to expand...
Click to collapse
Update: After reading various opinions on whether you need aboot to write the unlock code including one post stating clearly that the OP step 1 and 3 were independent of step 2 (aboot and twrp), I finally installed aboot and cubed twrp. Suddenly, after issuing adb reboot (which booted the tablet into fastboot as predicted), I was then able to issue the unlock command (fastboot flash -i 0x1949 unlock unlock.code) with success so it seems the vulnerable aboot is required to unlock. Now I have a final question about the fact that with the special aboot and twrp, the tablet will boot only into fastboot which is fine for flashing a custom ROM.
While I am going to now find a good stable customer ROM to flash, what does it take to keep the stock OS booting and, maintain the unlocked bootloader? If the user wanted to stay on the stock OS either for a short while or long term, what steps are needed? Flash a more traditional TWRP?
galearned said:
Update: After reading various opinions on whether you need aboot to write the unlock code including one post stating clearly that the OP step 1 and 3 were independent of step 2 (aboot and twrp), I finally installed aboot and cubed twrp. Suddenly, after issuing adb reboot (which booted the tablet into fastboot as predicted), I was then able to issue the unlock command (fastboot flash -i 0x1949 unlock unlock.code) with success so it seems the vulnerable aboot is required to unlock. Now I have a final question about the fact that with the special aboot and twrp, the tablet will boot only into fastboot which is fine for flashing a custom ROM.
While I am going to now find a good stable customer ROM to flash, what does it take to keep the stock OS booting and, maintain the unlocked bootloader? If the user wanted to stay on the stock OS either for a short while or long term, what steps are needed? Flash a more traditional TWRP?
Click to expand...
Click to collapse
This may sound a bit snarky; sometimes brevity is better:
- there are opinions and there are facts; sometimes they align, sometimes they don't
- fact: a vulnerable (ie: exploitable) bootloader (aboot) is required to apply the unlocking methods discussed in this forum
- fact: a stock device running a natively obtained version of FireOS > 3.2.3.2 does not have an aboot with an known vulnerability that can be leveraged by the signature forging exploit (hence the reason it must be replaced with an older vulnerable version)
- fact: steps #1 & #3 are independent of step #2 which can be performed first but is a prerequisite for step #3 if the stock aboot is not vulnerable
For all practice purposes you're done with FireOS after unlocking the bootloader. Enjoy the wide selection of custom ROMs for this device. FireOS can be reinstated with some work; has nothing to do with the version of TWRP.
Amazon Fire 5th generation Need bootloader unlocl
Fire OS 5.3.6.4
Need Bootloader unlock
And
Fastboot mode cmd is " the command you input is restricted on locked hw " problem
Please Replay ?
Dear all,
I have made numerous attempts to unlock the bootloader of my Wiko U Feel Prime, but to no avail.
(My goal is to flash TWRP, root with Magisk and install LineageOS.)
USB debugging and OEM unlocking are enabled in the developer settings.
ADB recognises the device. When I execute adb reboot bootloader, the device reboots, and doesn't get past the "powered by Android" screen – but is nonetheless found by fastboot when I run fastboot devices. Seems like the USB drivers are functioning properly, correct?
Now, when I run fastboot oem unlock, I get the following response:
Code:
...
FAILED (remote: unknown command)
finished. total time: -0.000s
The command fastboot flashing unlock gives the same result.
Moreover, fastboot getvar all displays no unlocked variable. The command fastboot getvar unlocked yields
Code:
unlocked:
By the way, this phone was shipped SIM unlocked.
I've spent hours looking around the web for solutions, but everyone (including guides specifically written for Wiko U Feel Prime) simply says "unlock the bootloader" as if it's a trivial task. And I've run out of ideas. Could anyone help?
Thank you very much.
The overall procedure is too simple, let me tell you how.
UPDATE: Looks like it's also applicable on Nokia 2.1 V by analyzing aboot. So previous NB1-Collision reserved as reference of EDL method, in case HMD may block it soon.
Please let me know if it doesn't work on your current firmware version. I'm working on make the overall procedure much more stable.
UPDATE: Looks like NB1-Collision is the only way to unlock the bootloader. Please read this topic to acquire the tool and attempt to unlock it: https://forum.xda-developers.com/showthread.php?p=79825293
If Android 9 firmware installed, phone disassembly and wire trick required.
So we recommend users unlock the phone immediately once bought.
Following procedure is archived.
Step 1: Download firmware which consists the service bootloader file
You can download it from https://fih-firmware.hikaricalyx.com/hmd_en.html#e2m
Please download E2M-0390-0-00WW-B02 one in this case. If you're using Android 9, download E2M-108C-0-00WW-B01.
Then, extract E2M-0-0390-00WW-1-2-emmc_appsboot_service.zip to get service bootloader file, and the extract password is "WLBGFIH123".
Step 2: Boot your phone to Download mode (Fastboot mode)
You can execute following command then connect your phone when powered off, or use any other method you're familiar with:
Code:
fastboot oem alive
Step 3: Flash service bootloader
Code:
fastboot oem dm-verity (md5_of_serial_number)
Surprised huh? This command is still usable on Nokia 2.1, even on Android 9 basis, not sure why.
For example, if your Serial Number is E2MGAHIKARICALYX, the md5 checksum is 0ab1b1e9f3aacc85849341cd5fb21412, then command will be:
Code:
fastboot oem dm-verity 0ab1b1e9f3aacc85849341cd5fb21412
You can simply Google a website to calculate md5 checksum of a string.
And flash service bootloader:
Code:
fastboot flash aboot /path/to/E2M-0-0390-00WW-1-2-emmc_appsboot_service.mbn
fastboot reboot-bootloader
Step 4: Unlock the bootloader
Your phone will reboot to service bootloader. Then grant unlock permission with following commands:
Code:
fastboot oem dm-verity (md5_of_serial_number)
fastboot oem fih on
fastboot oem devlock allow_unlock
Then unlock the bootloader:
Code:
fastboot oem flashing unlock_critical
When your phone is erasing userdata, then:
Code:
fastboot oem alive
(wait for triggering to download mode)
fastboot oem dm-verity (md5_of_serial_number)
fastboot oem fih on
fastboot oem devlock allow_unlock
fastboot oem unlock-go
All done. Your phone has unlocked bootloader.
Then reboot your phone to Download mode again and restore deviceinfo:
That wraps up the overall unlock procedure.
In case HMD will block this method, you can use EDL method to downgrade aboot partition from this article: https://forum.xda-developers.com/nokia-2-1/how-to/nb1-collision-how-to-unlock-bootloader-t3938072/
Many thanks,,
I think it would be too much to ask right now for Nokia 8.1 , but as 8.1 is very popular Nokia device right now and it's launched in many countries too,,,is it possible that we would see smthng like this for Nokia 8.1 tooo
I'm stuck on a locked bootloader on my 6.1 plus
Would this work on a Nokia 2?
Hey... How to I unlock NOKIA 2 Bootloader?... TA-1029
so i manually rebooted my nokia 2.1 to download mode but fastboot commands not working cuz my windows does not detect my phone i tried installing drivers manually but after fastboot commant it's stuck at <waiting for device> ,plz help guys
souhail sboui said:
so i manually rebooted my nokia 2.1 to download mode but fastboot commands not working cuz my windows does not detect my phone i tried installing drivers manually but after fastboot commant it's stuck at <waiting for device> ,plz help guys
Click to expand...
Click to collapse
Me too, I don't know what's up
scaryguadian said:
Me too, I don't know what's up
Click to expand...
Click to collapse
when device is ON ,adb detect it and adb commands works but when on download mode fastboot commands not working it have to be a driver issue but i tried a lot but no hope
souhail sboui said:
when device is ON ,adb detect it and adb commands works but when on download mode fastboot commands not working it have to be a driver issue but i tried a lot but no hope
Click to expand...
Click to collapse
Can someone suggest a driver we can use or a link to the WORKING nokia 2.1 drivers
souhail sboui said:
when device is ON ,adb detect it and adb commands works but when on download mode fastboot commands not working it have to be a driver issue but i tried a lot but no hope
Click to expand...
Click to collapse
oh, its already working for me, just disable signature driver if you are on window 8, 8.1 or 10 and reinstall the drivers thats all.
---------- Post added at 05:19 PM ---------- Previous post was at 05:09 PM ----------
hikari_calyx said:
The overall procedure is too simple, let me tell you how.
UPDATE: Looks like it's also applicable on Nokia 2.1 V by analyzing aboot. So previous NB1-Collision reserved as reference of EDL method, in case HMD may block it soon.
Please let me know if it doesn't work on your current firmware version. I'm working on make the overall procedure much more stable.
Step 1: Download firmware which consists the service bootloader file
You can download it from https://fih-firmware.hikaricalyx.com/hmd_en.html#e2m
Please download E2M-0390-0-00WW-B02 one in this case. If you're using Android 9, download E2M-108C-0-00WW-B01.
Then, extract E2M-0-0390-00WW-1-2-emmc_appsboot_service.zip to get service bootloader file, and the extract password is "WLBGFIH123".
Step 2: Boot your phone to Download mode (Fastboot mode)
You can execute following command then connect your phone when powered off, or use any other method you're familiar with:
Code:
fastboot oem alive
Step 3: Flash service bootloader
Code:
fastboot oem dm-verity (md5_of_serial_number)
Surprised huh? This command is still usable on Nokia 2.1, even on Android 9 basis, not sure why.
For example, if your Serial Number is E2MGAHIKARICALYX, the md5 checksum is 0ab1b1e9f3aacc85849341cd5fb21412, then command will be:
Code:
fastboot oem dm-verity 0ab1b1e9f3aacc85849341cd5fb21412
You can simply Google a website to calculate md5 checksum of a string.
And flash service bootloader:
Code:
fastboot flash aboot /path/to/E2M-0-0390-00WW-1-2-emmc_appsboot_service.mbn
fastboot reboot-bootloader
Step 4: Unlock the bootloader
Your phone will reboot to service bootloader. Then grant unlock permission with following commands:
Code:
fastboot oem dm-verity (md5_of_serial_number)
fastboot oem fih on
fastboot oem devlock allow_unlock
Then unlock the bootloader:
Code:
fastboot oem flashing unlock_critical
When your phone is erasing userdata, then:
Code:
fastboot oem alive
(wait for triggering to download mode)
fastboot oem dm-verity (md5_of_serial_number)
fastboot oem fih on
fastboot oem devlock allow_unlock
fastboot oem unlock-go
All done. Your phone has unlocked bootloader.
Then reboot your phone to Download mode again and restore deviceinfo:
That wraps up the overall unlock procedure.
In case HMD will block this method, you can use EDL method to downgrade aboot partition from this article: https://forum.xda-developers.com/nokia-2-1/how-to/nb1-collision-how-to-unlock-bootloader-t3938072/
Click to expand...
Click to collapse
thanks a lot. I have followed the above instructions, but when I tried the second command, I got an error, here is my log
C:\Users\HP620\Documents\Minimal ADB and Fastboot>fastboot devices
E2MBA81107001697 fastboot
C:\Users\HP620\Documents\Minimal ADB and Fastboot>fastboot oem alive
...
OKAY [ 0.005s]
finished. total time: 0.006s
C:\Users\HP620\Documents\Minimal ADB and Fastboot>fastboot oem dm-verity 6e4b6d5
21a65f379bd4ebf94d462005e
...
FAILED (remote: unknown command)
finished. total time: 0.036s
scaryguadian said:
oh, its already working for me, just disable signature driver if you are on window 8, 8.1 or 10 and reinstall the drivers thats all.
---------- Post added at 05:19 PM ---------- Previous post was at 05:09 PM ----------
thanks a lot. I have followed the above instructions, but when I tried the second command, I got an error, here is my log
C:\Users\HP620\Documents\Minimal ADB and Fastboot>fastboot devices
E2MBA81107001697 fastboot
C:\Users\HP620\Documents\Minimal ADB and Fastboot>fastboot oem alive
...
OKAY [ 0.005s]
finished. total time: 0.006s
C:\Users\HP620\Documents\Minimal ADB and Fastboot>fastboot oem dm-verity 6e4b6d5
21a65f379bd4ebf94d462005e
...
FAILED (remote: unknown command)
finished. total time: 0.036s
Click to expand...
Click to collapse
thnx but it didn't work i still can't make the fastboot commands detect the device and am sure the drivers are right
scaryguadian said:
oh, its already working for me, just disable signature driver if you are on window 8, 8.1 or 10 and reinstall the drivers thats all.
---------- Post added at 05:19 PM ---------- Previous post was at 05:09 PM ----------
thanks a lot. I have followed the above instructions, but when I tried the second command, I got an error, here is my log
C:\Users\HP620\Documents\Minimal ADB and Fastboot>fastboot devices
E2MBA81107001697 fastboot
C:\Users\HP620\Documents\Minimal ADB and Fastboot>fastboot oem alive
...
OKAY [ 0.005s]
finished. total time: 0.006s
C:\Users\HP620\Documents\Minimal ADB and Fastboot>fastboot oem dm-verity 6e4b6d5
21a65f379bd4ebf94d462005e
...
FAILED (remote: unknown command)
finished. total time: 0.036s
Click to expand...
Click to collapse
It won't work. Only very old bootloaders supported dm-verity.
Sent from my Nokia 8.1
singhnsk said:
It won't work. Only very old bootloaders supported dm-verity.
Click to expand...
Click to collapse
So, what do you suggest I do??
scaryguadian said:
So, what do you suggest I do??
Click to expand...
Click to collapse
The unlock can only be done via any of the two:
1. Disassemble > Trigger EDL mode.
2. The paid remote unlock service.
Sent from my Nokia 8.1
thnx for the guide man keep it up
some one posted the same problem : after the "fastboot oem dm-verity (md5_of_serial_number)" command it shows "FAILED (remote: unknown command)" ,any solution so i can continue unlocking my device ??
im also getting "FAILED (remote: unknown command)"
EDM not working either
singhnsk said:
It won't work. Only very old bootloaders supported dm-verity.
Click to expand...
Click to collapse
Can i downgrade then?
anyone who had the "FAILED (remote: unknown command)"
try typing your serial number in uppercase, that worked for me, but now im stuck on "fastboot oem fih on" i get the remote error
singhnsk said:
It won't work. Only very old bootloaders supported dm-verity.
Click to expand...
Click to collapse
Can i downgrade then?
---------- Post added at 11:42 AM ---------- Previous post was at 11:41 AM ----------
Shmegma said:
anyone who had the "FAILED (remote: unknown command)"
try typing your serial number in uppercase, that worked for me, but now im stuck on "fastboot oem fih on" i get the remote error
Click to expand...
Click to collapse
Still doesn't work, what update are you running
hikari_calyx said:
The overall procedure is too simple, let me tell you how.
UPDATE: Looks like it's also applicable on Nokia 2.1 V by analyzing aboot. So previous NB1-Collision reserved as reference of EDL method, in case HMD may block it soon.
Please let me know if it doesn't work on your current firmware version. I'm working on make the overall procedure much more stable.
UPDATE: Looks like NB1-Collision is the only way to unlock the bootloader. Please read this topic to acquire the tool and attempt to unlock it: https://forum.xda-developers.com/showthread.php?p=79825293
If Android 9 firmware installed, phone disassembly and wire trick required.
So we recommend users unlock the phone immediately once bought.
Following procedure is archived.
Step 1: Download firmware which consists the service bootloader file
You can download it from https://fih-firmware.hikaricalyx.com/hmd_en.html#e2m
Please download E2M-0390-0-00WW-B02 one in this case. If you're using Android 9, download E2M-108C-0-00WW-B01.
Then, extract E2M-0-0390-00WW-1-2-emmc_appsboot_service.zip to get service bootloader file, and the extract password is "WLBGFIH123".
Step 2: Boot your phone to Download mode (Fastboot mode)
You can execute following command then connect your phone when powered off, or use any other method you're familiar with:
Code:
fastboot oem alive
Step 3: Flash service bootloader
Code:
fastboot oem dm-verity (md5_of_serial_number)
Surprised huh? This command is still usable on Nokia 2.1, even on Android 9 basis, not sure why.
For example, if your Serial Number is E2MGAHIKARICALYX, the md5 checksum is 0ab1b1e9f3aacc85849341cd5fb21412, then command will be:
Code:
fastboot oem dm-verity 0ab1b1e9f3aacc85849341cd5fb21412
You can simply Google a website to calculate md5 checksum of a string.
And flash service bootloader:
Code:
fastboot flash aboot /path/to/E2M-0-0390-00WW-1-2-emmc_appsboot_service.mbn
fastboot reboot-bootloader
Step 4: Unlock the bootloader
Your phone will reboot to service bootloader. Then grant unlock permission with following commands:
Code:
fastboot oem dm-verity (md5_of_serial_number)
fastboot oem fih on
fastboot oem devlock allow_unlock
Then unlock the bootloader:
Code:
fastboot oem flashing unlock_critical
When your phone is erasing userdata, then:
Code:
fastboot oem alive
(wait for triggering to download mode)
fastboot oem dm-verity (md5_of_serial_number)
fastboot oem fih on
fastboot oem devlock allow_unlock
fastboot oem unlock-go
All done. Your phone has unlocked bootloader.
Then reboot your phone to Download mode again and restore deviceinfo:
That wraps up the overall unlock procedure.
In case HMD will block this method, you can use EDL method to downgrade aboot partition from this article: https://forum.xda-developers.com/nokia-2-1/how-to/nb1-collision-how-to-unlock-bootloader-t3938072/
Click to expand...
Click to collapse
Hi, what am I doing wrong?
Code:
C:\adb>fastboot oem dm-verity ca5943eaee14c601267c58d289f50dd2
FAILED (remote: 'unknown command')
fastboot: error: Command failed
C:\adb>fastboot flash aboot E2M-0-0390-00WW-1-2-emmc_appsboot_service.mbn
Sending 'aboot' (954 KB) OKAY [ 0.032s]
Writing 'aboot' FAILED (remote: 'Critical partition flashing is not allowed')
fastboot: error: Command failed
Hi,
I've now spent quite a few frustrating hours trying to root my Alcatel 1c (model 5003D, running Android 8.1 Go) and nothing seems to work. A short overview of some of the rabbit holes I've gone down:
Root tools
Started with the obvious: root tools. In short, none that I ran work. There's a couple I haven't tried because the instructions were mostly in Russian and some googling turned up quite a few mentions of them containing malware, but other than that I've pretty much tried all the major ones.
Flashing images via fastboot
Naturally, the next place I turned was the awesome resource that is this forum. This thread gave me plenty of hope, but I was soon flummoxed by my device's fastboot mode for which a bunch of the normal features are either broken or are simply not implemented. Some examples of things that should work (and indeed work on other Alcatel phones, notably, it seems, ones that are not based on Spreadtrum) but didn't:
Code:
~/D/platform-tools > ./fastboot oem unlock
FAILED (remote: 'unknown cmd.')
fastboot: error: Command failed
Code:
~/D/platform-tools > ./fastboot oem unlock-go
FAILED (remote: 'unknown cmd.')
fastboot: error: Command failed
Code:
~/D/platform-tools > ./fastboot oem unlock-go --wipe
FAILED (remote: 'unknown cmd.')
fastboot: error: Command failed
Code:
~/D/platform-tools > ./fastboot flashing unlock
FAILED (remote: 'Not implemet.')
fastboot: error: Command failed
(note the spelling error in the error message...)
Code:
~/D/platform-tools > ./fastboot flash recovery ../recovery.img
Sending 'recovery' (28266 KB) OKAY [ 1.582s]
Writing 'recovery' FAILED (remote: 'Flashing Lock Flag is locked. Please unlock it first!')
fastboot: error: Command failed
That last one was particularly intriguing, as it suggests there is a Flashing Lock Flag that can be unlocked. I tried all of the fastboot commands that seemed relevant but couldn't find any way of setting that flag or even figuring out if it actually exists. I even rand the boot.img through strings to see if I could find something interesting, but didn't turn up anything.
Just to be clear, before doing all this I set the phone to Developer Mode and checked the "OEM unlocking" feature.
Flashing tools
I tried various tools with which it's possible to flash phones. A lot of them use fastboot under the covers which doesn't work (see above). Some of them don't but didn't work on my phone all the same, for various reasons:
SPD flash tool - After yet more Googling I stumbled upon the SPD flash tool,built specifically to flash Spreadtrum-based devices. I downloaded the latest version, installed all of the necessary USB drivers and tried to flash the phone with the stock ROM. No dice. The tool fails to connect to the device via the USB2Serial thing that it uses to communicate. No idea what's going on or why it won't work, and haven't yet mustered the courage to dive into the source code. Of course, if I do get it to work, then I have to figure out how to actually root the device using this tool. I'm guessing it will involve unpacking the ROM (a PAC file), modifying the recovery.img to a TWRP (or similar), repacking it and flashing the result. I've only managed the unpacking so far, no clue as to the other 2 steps. BTW, the SPD flash tool site als has a "factory" and a "research" tool, besides the "upgrade" tool that I tried. Unless I'm missing something, all three seem to be exactly the same (save for the color scheme).
Alcatel Mobile Upgrade S - Installs just fine and then allows you to choose your phone out of a dropdown... that doesn't include my model.
Sugar MTK/QCT - Installed it and the necessary drivers but it can't find my phone, no matter what I try. Also, I keep reading that it needs login credentials (wut?)
Conclusion: argh!
So, nothing so far. Since it's a Spreadtrum phone it has an engineering mode that can be explored with an APK I found in this thread. Nothing in the settings it reveals appears to be of any help though. I also contacted the makers of the AIO Alcatel toolkit to see if they had any ideas, but after I explained the situation one of them concluded "Hmmm. New one on me". Needless to say I also tried searching this forum for more tips, but googling 'site:forum.xda-developers.com "5003D"' returns no hits.
For now, I'm forced to conclude that there is a lot of really awesome tooling out there created by some very talented people, but none of it works on my phone. As of yet the 5003D appears pretty unrootable. If anyone has any tips to help me along or point me in the right direction, I would be very appreciative.
bump
bump
Then type the command to show the device
fastboot -i 0x1bbb devices
Execute the next command which will show device info including bootloader status (e.g. locked).
fastboot -i 0x1bbb oem device-info
This command is to unlock the bootloader on Alcatel device
fastboot -i 0x1bbb oem unlock
Repeat Step and you should see “Device unlocked: true”
To reboot normally type:
fastboot -i 0x1bbb reboot
Done
This command is to unlock the bootloader on Alcatel device
fastboot -i 0x1bbb oem unlock
Click to expand...
Click to collapse
I've tried that a bunch of times in an bunch of different ways, and unfortunately that doesn't work for this particular phone.
lotus118 said:
I've tried that a bunch of times in an bunch of different ways, and unfortunately that doesn't work for this particular phone.
Click to expand...
Click to collapse
Rooting your phone's Android does NOT require you fiddle around with its boot-loader. Forget trying to make use of Fastboot.
So how would I go about this without using fastboot?
lotus118 said:
So how would I go about this without using fastboot?
Click to expand...
Click to collapse
1. Open Windows command prompt and input the following comand
Code:
adb devices
2. Start the ADB sideload in your phone's recovery
3. Then input the following command in the Windows command prompt
Code:
adb sideload <filename.Zip>
where <filename.zip> must of course be the real full filepathname of ZIP to get flashed
hi I have an alcatel 1b 5002d I would like to root it but I always have this error and it does not unlock the bootloader
C: \ sdk> fastboot oem unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
with any fastbooot command it is the same error, only with fastboot devices it gives me the serial, I have already installed all the drivers, I would not know how to do anything else if someone has some solution app like kingroot do nothing I have no security screen locks, drivers installed, developer options unlocked oem and usb debugging
roberto167 said:
hi I have an alcatel 1b 5002d I would like to root it but I always have this error and it does not unlock the bootloader
C: \ sdk> fastboot oem unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
with any fastbooot command it is the same error, only with fastboot devices it gives me the serial, I have already installed all the drivers, I would not know how to do anything else if someone has some solution app like kingroot do nothing I have no security screen locks, drivers installed, developer options unlocked oem and usb debugging
Click to expand...
Click to collapse
Hello and good morning, @roberto167
Prior to your next posting please read the guidances that are stuck on top of every forum like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
and the others. I've moved the thread to Android Q&A.
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
roberto167 said:
hi I have an alcatel 1b 5002d I would like to root it but I always have this error and it does not unlock the bootloader
C: \ sdk> fastboot oem unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
with any fastbooot command it is the same error, only with fastboot devices it gives me the serial, I have already installed all the drivers, I would not know how to do anything else if someone has some solution app like kingroot do nothing I have no security screen locks, drivers installed, developer options unlocked oem and usb debugging
Click to expand...
Click to collapse
Is that your phone? https://forum.xda-developers.com/c/alcatel-1.8103/
joke19 said:
È il tuo telefono? https://forum.xda-developers.com/c/alcatel-1.8103/
Click to expand...
Click to collapse
mine is model 1b with 2gb ram and android 11
assuming you have enabled OEM unlocking in developer options, try
fastboot flashing unlock
aIecxs said:
assuming you have enabled OEM unlocking in developer options, try
fastboot flashing unlock
Click to expand...
Click to collapse
as said already done and gives me the said error, enter fastboot mode
fastboot oem unlock
FAILED (remote: 'unknown command')
did you actually notice the difference between what I wrote and what you did?
aIecxs said:
did you actually notice the difference between what I wrote and what you did?
Click to expand...
Click to collapse
also given that command and also
fastboot flashing unlock
so what was the error message then
seems unlocking is disabled in aboot therefore no common unlock method will work. at least there is a working firehose programmer for that device, so you can dump boot.img off the eMMC and try to modify with AIK and Magisk (AVBv2 signing required)
source
aIecxs said:
seems unlocking is disabled in aboot therefore no common unlock method will work. at least there is a working firehose programmer for that device, so you can dump boot.img off the eMMC and try to modify with AIK and Magisk (AVBv2 signing required)
source
Click to expand...
Click to collapse
it seems very complicated as a procedure, being never done
usual error message looks like this
jorgen.bumajnikov said:
I'm trying to unlock phone’s bootloader using
Code:
fastboot flashing unlock
, but getting error message:
Code:
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.021s
Checked fastboot devices command and it found my device connected.
Click to expand...
Click to collapse
but your error sounds hopeless
FAILED (remote: 'unknown command')
So if you're looking for easy solution you're reading the wrong section.
Nevertheless you could give a last try
Code:
fastboot -i 0x1bbb oem unlock
fastboot -i 0x1bbb flashing unlock
aIecxs said:
usual error message looks like this
but your error sounds hopeless
FAILED (remote: 'unknown command')
So if you're looking for easy solution you're reading the wrong section.
Nevertheless you could give a last try
Code:
fastboot -i 0x1bbb oem unlock
fastboot -i 0x1bbb flashing unlock
Click to expand...
Click to collapse
even if it appears with the command fastboot devices, with these commands it remains waiting for any devices
Alcatel 1B Stock ROM / SIM unlock / etc....
ALCATEL 1B MEGATHREAD ( veken/seoul/TCL L7)...
forum.xda-developers.com
"UNLOCKING BOOTLOADER / ROOTING
For now, it is not possible... However mentions of secret key is spread all around the phone partitions (mainly abl file)
So if you have any experience editing bootloaders you can unlock...."