To Content farms like GETDROIDTIPS: DO NOT REPOST OR REFORM MY TOPIC ON YOUR WEBSITE WITHOUT INFORMING ME!
Recent Android 10 update fixed support for TA-1054 hardware, so we can do global conversion right now. Anything older will break the phone and you have to disassemble the phone and utilize EDL to unbrick it (test point indicated below).
Therefore, we have to install Android 10 directly, but for some reason, the bootloader will be reverted back to locked state, so it has to be unlocked again via some tricks.
This guide will tell you how to install Android 10 into TA-1054. If you don't have unlocked bootloader, you have to unlock it first.
If you don't have unlocked bootloader, you may need to look for Global conversion service online.
PLEASE MAKE SURE YOU HAVE BACKED UP EVERYTHING BEFORE YOU DO SO.
Step 1: Change SKUID
To change SKUID, you need to ensure your phone is rooted, or your phone booted to TWRP (official TWRP for Nokia 6.1 is OK to use) to allow us change SKUID written in deviceinfo partition.
If you booted to TWRP via these commands under Download mode:
Code:
fastboot reboot-bootloader
fastboot boot twrp-3.4.0-0-PL2_sprout.img
Once phone booted to TWRP (even if stuck at splash screen is OK), then you can dump the devceinfo and securefs partition:
Code:
adb shell dd if=/dev/block/bootdevice/by-name/deviceinfo of=/tmp/deviceinfo.img
adb shell dd if=/dev/block/bootdevice/by-name/securefs of=/tmp/securefs.img
adb pull /tmp/deviceinfo.img
adb pull /tmp/securefs.img
The reason why I suddenly mentioned securefs partition is, it contains Widevine DRM key that related to video-on-demand services like Netflix.
You have to back it up just in case.
Then follow this guide to edit SKUID written in deviceinfo into 600WW:
https://forum.xda-developers.com/nokia-7-plus/how-to/guide-how-to-change-skuid-to-worldwide-t3808520
Once SKUID changed, write the deviceinfo partition back:
Code:
fastboot flash deviceinfo deviceinfo_600WW.img
After SKUID changed, you'll find the launcher becomes weird, which is expected behavior.
Step 2: Install Android 10 full OTA
Please download it from here:
https://android.googleapis.com/pack.../c6260831df0acdfe9828f18bcea7ffb556f4b2e5.zip
And rename it into PL2-9999-0-00CN-B99-update.zip. Copy it to root directory of internal storage, and dial *#*#874#*#* to install it.
Once install complete, you might be asked for erasing userdata, just erase it.
Step 3: Unlock bootloader again (optional)
If you think it's OK to use Android 10 without unlocked bootloader, then that wraps up the procedure and enjoy it.
But if you want to unlock the bootloader again, you have to follow some trick.
Once the phone booted to welcome screen again, power it off, boot to Download mode by using this command:
Code:
fastboot oem alive
And connect the powered off phone to PC, it will be booted to Download mode again.
Next, check which slot is Android 10 installed:
Code:
fastboot getvar current-slot
If current-slot is A, execute this:
Code:
fastboot --set-active=b reboot-bootloader
If current-slot is B, execute this:
Code:
fastboot --set-active=a reboot-bootloader
Once slot changed, you'll be switched back to the previous version with unlocked bootloader.
Now you have to downgrade the abl/xbl to allow it being unlockable again.
Now check which slot is Chinese Nokia 6.1 Android build installed:
Code:
fastboot getvar current-slot
If current-slot is A, execute these:
Code:
fastboot flash abl_b C1N-0-0430-abl_service.elf
fastboot flash xbl_b C1N-0-0430-xbl_service.elf
fastboot --set-active=b reboot-bootloader
If current-slot is B, execute these:
Code:
fastboot flash abl_a C1N-0-0430-abl_service.elf
fastboot flash xbl_a C1N-0-0430-xbl_service.elf
fastboot --set-active=a reboot-bootloader
Both C1N-0-0430-abl_service.elf and C1N-0-0430-xbl_service.elf can be obtained from https://fih-firmware.hikaricalyx.com/hmd_en.html#c1n (extract it from C1N-0-0430-0-00CN-B05 firmware).
Then you can unlock the bootloader again with what you have done before:
Code:
fastboot flash unlock unlock.bin
fastboot flashing unlock_critical
(confirm bootloader unlock on the phone)
(while waiting for erasing, execute this immediately)
fastboot oem alive
fastboot flash unlock unlock.bin
fastboot oem unlock-go
(confirm unlock again)
(while waiting for erasing, execute this immediately)
fastboot oem alive
After we unlocked the bootloader, we have to switch back to previous Chinese Nokia 6.1 Android build to reinstall Android 10.
Check which slot is Android 10 installed:
Code:
fastboot getvar current-slot
If current-slot is A, execute this:
Code:
fastboot --set-active=b reboot
If current-slot is B, execute this:
Code:
fastboot --set-active=a reboot
Repeat the step 2 to reinstall Android 10 Full OTA, and enjoy Android 10 on Chinese Nokia 6.1 with unlocked bootloader.
Under Android 10, if bootloader unlocked, you'll lose Widevine DRM key permanently, that's why I asked you to backup securefs partition.
Is the shorting wires solution to unbrick the phone or to change china to global version?
Ok, pins shorted. Whats now?
Spacepl said:
Ok, pins shorted. Whats now?
Click to expand...
Click to collapse
flash nbo Nokia 6 2018 firmware with OST LA
Sent from my TA-1054 using Tapatalk
juwelrana091 said:
flash nbo Nokia 6 2018 firmware with OST LA
Click to expand...
Click to collapse
Do i need to unlock the bootloader to do this?
And if so can so post a link for a way that doesnt require the app provided by nokia?
J0NS3N said:
Do i need to unlock the bootloader to do this?
And if so can so post a link for a way that doesnt require the app provided by nokia?
Click to expand...
Click to collapse
Is your phone already bricked? Then shorting the pins will trigger EDL mode and then you can use Qualcomm tools to flash the abl and xbl. That can make the phone usable again, but yes you will still need to flash the CN firmware as Global will not be usable on this device.
help
hello i tried shortening all 4, or one of the 2 sets but it did not trigger EDL, my phone is stuck in Download mode as soon as it turns on, my pc only recognizes it as Fastboot device, my bootloader is locked, i have the exact same model, can you help me??
Could you please clarify:
is it possible to install PL2-410C-0-00WW-B03 on TA-1054 China Version , i.e. convert it into Android 10 Global Version? So it is impossible to install earlier global versions, but it is possible to install PL2-410C-0-00WW-B03?
Thank you.
vanechka25 said:
Could you please clarify:
is it possible to install PL2-410C-0-00WW-B03 on TA-1054 China Version , i.e. convert it into Android 10 Global Version? So it is impossible to install earlier global versions, but it is possible to install PL2-410C-0-00WW-B03?
Thank you.
Click to expand...
Click to collapse
Yes, but remember to change SKUID to 600WW before installing PL2-410C-0-00WW-B03.
Also, flash PL2-410C-0-00WW-B03 into bootloader unlocked TA-1054 will revert the bootloader back to locked state, you have to unlock it again with some trick, will talk about that later.
If you use some flashing tool that can elevate like NTool, just go ahead and flash PL2-410C firmware.
hikari_calyx said:
Yes, but remember to change SKUID to 600WW before installing PL2-410C-0-00WW-B03.
Also, flash PL2-410C-0-00WW-B03 into bootloader unlocked TA-1054 will revert the bootloader back to locked state, you have to unlock it again with some trick, will talk about that later.
If you use some flashing tool that can elevate like NTool, just go ahead and flash PL2-410C firmware.
Click to expand...
Click to collapse
Thank you for the quick answer!
Hmm... Is it possible to change SKUID for this phone with locked bootloader?
I know, for some other phones it could be done using fastboot command like this:
fastboot oem CustomerSKUID set 600WW
but I'm not sure that this method is applicable to TA-1054. I checked the command CustomerSKUID:
fastboot oem CustomerSKUID get
and it is unknown.
Do you know any easy way to change SKUID without unlockng / rooting?
What will happen if I try to flash PL2-410C-0-00WW-B03 without SKUID changing?
Actually, the main reason to update the phone is the problem with mobile internet. My local mobile operator SIM does't allow to use it, but the voice service works OK. When I set this SIM to another phone, internet works, when I set SIM of another operator to TA-1054 - it works again. So, certain operator internet settings and settings in chinese ROM are different. I suppose, it is required to change bands modes or something like this, but I dont't know the real reason of this issue.
Maybe you could give me an advice about this internet problem, so I don't need to update phone to global ROM at all.
vanechka25 said:
Thank you for the quick answer!
Hmm... Is it possible to change SKUID for this phone with locked bootloader?
I know, for some other phones it could be done using fastboot command like this:
fastboot oem CustomerSKUID set 600WW
but I'm not sure that this method is applicable to TA-1054. I checked the command CustomerSKUID:
fastboot oem CustomerSKUID get
and it is unknown.
Do you know any easy way to change SKUID without unlockng / rooting?
What will happen if I try to flash PL2-410C-0-00WW-B03 without SKUID changing?
Actually, the main reason to update the phone is the problem with mobile internet. My local mobile operator SIM does't allow to use it, but the voice service works OK. When I set this SIM to another phone, internet works, when I set SIM of another operator to TA-1054 - it works again. So, certain operator internet settings and settings in chinese ROM are different. I suppose, it is required to change bands modes or something like this, but I dont't know the real reason of this issue.
Maybe you could give me an advice about this internet problem, so I don't need to update phone to global ROM at all.
Click to expand...
Click to collapse
If you don't have some special flashing utility (requires USB dongle), you cannot change SKUID without unlocked bootloader.
You can search about global conversion service remotely which could be paid.
Install global firmware with mismatch SKUID will cause the OS itself buggy, many feature missing and cannot pass Google Play Certification.
hikari_calyx said:
If you don't have some special flashing utility (requires USB dongle), you cannot change SKUID without unlocked bootloader.
You can search about global conversion service remotely which could be paid.
Install global firmware with mismatch SKUID will cause the OS itself buggy, many feature missing and cannot pass Google Play Certification.
Click to expand...
Click to collapse
Thank you very much for the answer. You clarified a lot of things!
Downgrade from android 10 to android 9
vanechka25 said:
Thank you very much for the answer. You clarified a lot of things!
Click to expand...
Click to collapse
Hey can you help me for downgrading android 10 to android 9 with locked bootloader .i want to unlock bootloader to downgrading to android 9 and also i am facing wifi disconnected and mobile restarting issues .also what this ss show is that bootloader locked or unlocked
hikari_calyx said:
If current-slot is A, execute these:
Code:
fastboot flash abl_b C1N-0-0430-abl_service.elf
fastboot flash xbl_b C1N-0-0430-xbl_service.elf
fastboot --set-active=b reboot-bootloader
If current-slot is B, execute these:
Code:
fastboot flash abl_a C1N-0-0430-abl_service.elf
fastboot flash xbl_a C1N-0-0430-xbl_service.elf
fastboot --set-active=a reboot-bootloader
Both C1N-0-0430-abl_service.elf and C1N-0-0430-xbl_service.elf can be obtained from https://fih-firmware.hikaricalyx.com/hmd_en.html#c1n (extract it from C1N-0-0430-0-00CN-B05 firmware).
Then you can unlock the bootloader again with what you have done before:
Click to expand...
Click to collapse
A very complete guide, thank you, but I have a question. From what I've seen both C1N-0-0430-abl_service.elf and C1N-0-0430-xbl_service.elf refer to Nokia 7 (android OS 7.1.1), is it ok to flash them on a Nokia 6.1 with android OS 8.1 ?
21prods said:
A very complete guide, thank you, but I have a question. From what I've seen both C1N-0-0430-abl_service.elf and C1N-0-0430-xbl_service.elf refer to Nokia 7 (android OS 7.1.1), is it ok to flash them on a Nokia 6.1 with android OS 8.1 ?
Click to expand...
Click to collapse
Yes it will work on both Nokia 6.1 and 7.
hikari_calyx said:
Yes it will work on both Nokia 6.1 and 7.
Click to expand...
Click to collapse
Thank you
Hello, EveryoneMy Nokia 6.1 2018 Hmd Global TA-1054 with Build number - 00WW_3_270 will receive a global system update and security update. Will this method described above work for me? So you will get a global version of version 10 or have to wait. My latest security fix for Android is from October 1, 2018. Can you explain in detail what steps to take to make the updates.
Related
Hi, I've got the 6045Y model which I've been trying to install twrp on, but I can't unlock the bootloader; it says oem unlock is not allowed.
I've tried on os x and linux with sudo but it's the same on both sides. As my phone isn't carrier locked, I don't understand why it's not allowing me to unlock the bootloader. There's also no oem unlock option in the developer options.
Any help?
You must do something wrong?
Can you trY with Windows
You need Alcatel Drivers+Minimal Adb and Fastboot
connect device you must enable debugging and then
-type "adb reboot-bootloader" to reboot into bootloader. The device should reboot to the screen showing "alcatel onetouch...powered by android". This is bootloader mode.
-Then type "fastboot -i 0x1bbb devices" should show some numbers and "fastboot" after the numbers
-Type "fastboot -i 0x1bbb oem device-info" shows device info including bootloader status (e.g. locked).
-Type "fastboot -i 0x1bbb oem unlock" to unlock the bootloader; after this you should get, for device info,
-Type "fastboot -i 0x1bbb oem device-info" and you should see "Device unlocked: true"
-To reboot normally: "fastboot -i 0x1bbb reboot"
Alek Dev said:
You must do something wrong?
Can you trY with Windows
You need Alcatel Drivers+Minimal Adb and Fastboot
connect device you must enable debugging and then
-type "adb reboot-bootloader" to reboot into bootloader. The device should reboot to the screen showing "alcatel onetouch...powered by android". This is bootloader mode.
-Then type "fastboot -i 0x1bbb devices" should show some numbers and "fastboot" after the numbers
-Type "fastboot -i 0x1bbb oem device-info" shows device info including bootloader status (e.g. locked).
-Type "fastboot -i 0x1bbb oem unlock" to unlock the bootloader; after this you should get, for device info,
-Type "fastboot -i 0x1bbb oem device-info" and you should see "Device unlocked: true"
-To reboot normally: "fastboot -i 0x1bbb reboot"
Click to expand...
Click to collapse
I tried on windows just now and the same thing happened: "FAILED (remote: oem unlock is not allowed)". I should mention though, I flashed twrp before unlocking the bootloader. I wonder if this is what's causing the problem.
I dont remember if this option was there, but you can try. Go into Settings/About Phone, scroll down and click on “build number” continuously until you see a toast notification telling you that you've enabled Developer Options. Go back to your Settings menu and enter Developer Options, scroll down and click on the “Enable OEM Unlock” checkbox, also make sure you enable USB Debugging while you're in the Developer Options menu.
DallasCZ said:
I dont remember if this option was there, but you can try. Go into Settings/About Phone, scroll down and click on “build number” continuously until you see a toast notification telling you that you've enabled Developer Options. Go back to your Settings menu and enter Developer Options, scroll down and click on the “Enable OEM Unlock” checkbox, also make sure you enable USB Debugging while you're in the Developer Options menu.
Click to expand...
Click to collapse
I have the same problem an update was pushed to the UK version last week 6045Y 5.0.2 -010 02 now unable to unlock bootloader i tried everything, so the bootloader must of changed BTW the update was about 458mb.
aradalien said:
I have the same problem an update was pushed to the UK version last week 6045Y 5.0.2 -010 02 now unable to unlock bootloader i tried everything, so the bootloader must of changed BTW the update was about 458mb.
Click to expand...
Click to collapse
same here in the uk have same version and cannot unlock bootloader anyone been sucssesful
aradalien said:
I have the same problem an update was pushed to the UK version last week 6045Y 5.0.2 -010 02 now unable to unlock bootloader i tried everything, so the bootloader must of changed BTW the update was about 458mb.
Click to expand...
Click to collapse
Same problem with same UK model and installed that patch too. I managed to flash TWRP and install PAC ROM still bootloader claims to be locked.
fastboot -i 0x1bbb oem unlock
FAILED (remote: oem unlock is not allowed)
fastboot -i 0x1bbb oem device-info
(bootloader) Device tempered:false
(bootloader) Device Unlock:false
easiest way is to download stock firmware with flsh tool for panasonic eluga switch (rebranded idol3),. Flash it with using the included flash tool. then unlock bootloader. Then use mobile upgrade Q 5.0.6 to go back to stock. And you are on stock uk firmware with unlocked bootloader.
I flashed someone's stock 6045Y(Europe) Firmware: 5.0.2-010 03 but couldn't unlock it either. After that I flashed 6045-i806-DCZ. I was really surpriced it let me do that while claiming to be locked and untempered. After that I did factory reset and flashed PAC-ROM. I'm not sure why should I bother to unlock bootloader if I already have TWRP and PAC-ROM flashed. I've no idea how can I even flash rom's with locked bootloader? Maybe oem device-info is bugged.
Anyways I download panasonic eluga switch firmwire, gonna test it after taking backups.
Reippi said:
I flashed someone's stock 6045Y(Europe) Firmware: 5.0.2-010 03 but couldn't unlock it either. After that I flashed 6045-i806-DCZ. I was really surpriced it let me do that while claiming to be locked and untempered. After that I did factory reset and flashed PAC-ROM. I'm not sure why should I bother to unlock bootloader if I already have TWRP and PAC-ROM flashed. I've no idea how can I even flash rom's with locked bootloader? Maybe oem device-info is bugged.
Anyways I download panasonic eluga switch firmwire, gonna test it after taking backups.
Click to expand...
Click to collapse
the Panasonic firmware flash also the aboot partition which has bootloader unlock enabled. without unlocked bootloader you could end with bricked device and the only solution is mobile upgrade q.
I did as you said and finally got bootloader unlocked, yey! Hopefully I don't have to go thought that process anytime soon. Thanks and thumps up!
Reippi said:
I did as you said and finally got bootloader unlocked, yey! Hopefully I don't have to go thought that process anytime soon. Thanks and thumps up!
Click to expand...
Click to collapse
no, its permanent.
I try to unlock my bootloader but two problems : oem unlock is not allowed and eluga sotware stuck at 2 %!!! I want install MM and I have stock rom can install the same the MM upgrade without unlock the bootloader? Regards
camelotto said:
I try to unlock my bootloader but two problems : oem unlock is not allowed and eluga sotware stuck at 2 %!!! I want install MM and I have stock rom can install the same the MM upgrade without unlock the bootloader? Regards
Click to expand...
Click to collapse
1-You didnt wrote phch model do you have.
2-newer heard of this issue . Install the drivers from the eluga firmware app, reboot, turn off your device, connect device to computer, run the download form the eluga firmware app.
jlocohustler said:
I tried on windows just now and the same thing happened: "FAILED (remote: oem unlock is not allowed)". I should mention though, I flashed twrp before unlocking the bootloader. I wonder if this is what's causing the problem.
Click to expand...
Click to collapse
And do you have sucess in flash? It worked? Do you have TWRP????
---------- Post added at 10:34 AM ---------- Previous post was at 10:30 AM ----------
Reippi said:
I flashed someone's stock 6045Y(Europe) Firmware: 5.0.2-010 03 but couldn't unlock it either. After that I flashed 6045-i806-DCZ. I was really surpriced it let me do that while claiming to be locked and untempered. After that I did factory reset and flashed PAC-ROM. I'm not sure why should I bother to unlock bootloader if I already have TWRP and PAC-ROM flashed. I've no idea how can I even flash rom's with locked bootloader? Maybe oem device-info is bugged.
Anyways I download panasonic eluga switch firmwire, gonna test it after taking backups.
Click to expand...
Click to collapse
That is the point from my previouse question! If you flash TWRP, your bootloader is unlocked by default!
persona78 said:
And do you have sucess in flash? It worked? Do you have TWRP????
---------- Post added at 10:34 AM ---------- Previous post was at 10:30 AM ----------
That is the point from my previouse question! If you flash TWRP, your bootloader is unlocked by default!
Click to expand...
Click to collapse
After flashing panasonic rom, you have unlockable bootloader.
Look here
http://forum.xda-developers.com/idol-3/general/guide-repair-idol-3-t3372076
I have 6045Y and panasonic rom work!
fastboot is detecting device but oem unlock/flashing unlock command not working.
I think that command has been changed since this june month security patch.
yash_rathore25 said:
fastboot is detecting device but oem unlock/flashing unlock command not working.
I think that command has been changed since this june month security patch.
Click to expand...
Click to collapse
It looks like MM update dont include aboot with commands for unlocking bootloader. You have to use mobile upgrade Q PC aPP, or Panasonic eluga firmware flash tool (for 6045Y) to go back to 5.0.2. Then unlock bootloader, and flash update to MM (or when on panasonic firmware youhave to use mobile upgrade Q to go back to stock). When on stock, wat for OTA MM or flash MM from XDA thread.
DallasCZ said:
It looks like MM update dont include aboot with commands for unlocking bootloader. You have to use mobile upgrade Q PC aPP, or Panasonic eluga firmware flash tool (for 6045Y) to go back to 5.0.2. Then unlock bootloader, and flash update to MM (or when on panasonic firmware youhave to use mobile upgrade Q to go back to stock). When on stock, wat for OTA MM or flash MM from XDA thread.
Click to expand...
Click to collapse
but fastboot flash command is working and also sending data to phone but unable to write on phone as bootloader is locked
yash_rathore25 said:
but fastboot flash command is working and also sending data to phone but unable to write on phone as bootloader is locked
Click to expand...
Click to collapse
because they have erased this command/s from aboot partition (bootloader)
We flashing v35 engineering bootloaders
1. enable USB-Debugging
2. Enable OEM unlock
3. enter into 9008 mod
4. do step by step instructions. Video youtube: p8Z0KOUNw7Q
5. And then "fastboot oem unlock" will work.
LG_LG+G7+Unlock+Bootloader.zip on mega nz
#!P2wDBa4R!NLS6k9QAK0-I2PWdACqEOiKdUpGzisrxnh1876cRTKU
copy of instructions from youtube on mega nz
#!XuhDDCRJ!8kUG3MWgQCeDhKIJqRcKJc0TTvAeNeP7RodkbZ-mGrs
Because when you 'fastboot oem unlock' successful.
you phone just unlocked bootloader, so you can flash root booted to root you phone.
Flashing back to Stock KDZ: we can flash the stock KDZ for the G7 and keep booloader unlocked but -- depending on version -- we loose access to fastboot commands. To avoid this he mentions using patched LGUP to flash the KDZ, making sure to uncheck the bootloader partitions
Please be aware that the v35 bootloader will hard brick your phone, if you flash stock pie kdz without bootloader partitions. I was in that situation and only recovery option was octoplus again.
The owner of that video is @motogvasyag
https://forum.xda-developers.com/lg-v40/how-to/remote-unlocking-bootloader-models-t-t3946648
cheeze.keyk said:
The owner of that video is @motogvasyag
https://forum.xda-developers.com/lg-v40/how-to/remote-unlocking-bootloader-models-t-t3946648
Click to expand...
Click to collapse
yes. and i link his youtube channel
It works using Pie?
If I flash KDZ and lost Fastboot I can install another KDZ to recover fastboot access?
Why not t-mobile?
There appears to be a post (from two days back) on one of the famous Russian forums showing a way to do this without Octoplus by temporarily booting using a rooted boot and then replacing the bootloader using a root terminal and finally doing the unlock using "fastboot oem unlock". Has anyone here tried it / have any thoughts on it?
can keep Fastboot on Slot a when update to Android Pie
LG G6 ThinkQ Unlocking Product
ruvhell said:
We flashing v35 engineering bootloaders
1. enable USB-Debugging
2. Enable OEM unlock
3. enter into 9008 mod
4. do step by step instructions. Video youtube: p8Z0KOUNw7Q
5. And then "fastboot oem unlock" will work.
LG_LG+G7+Unlock+Bootloader.zip on mega nz
#!P2wDBa4R!NLS6k9QAK0-I2PWdACqEOiKdUpGzisrxnh1876cRTKU
copy of instructions from youtube on mega nz
#!XuhDDCRJ!8kUG3MWgQCeDhKIJqRcKJc0TTvAeNeP7RodkbZ-mGrs
Because when you 'fastboot oem unlock' successful.
you phone just unlocked bootloader, so you can flash root booted to root you phone.
Flashing back to Stock KDZ: we can flash the stock KDZ for the G7 and keep booloader unlocked but -- depending on version -- we loose access to fastboot commands. To avoid this he mentions using patched LGUP to flash the KDZ, making sure to uncheck the bootloader partitions
Click to expand...
Click to collapse
I have a question about the Octoplus Pro Box. Is this product better than the Infinite Box Chinese Miracle II? We have some ex demo phones without an IMEI where we need the boot sector unlocked. We want to flush the OS to install a new OS, e.g lineage or ubuntu., preferably an open source linux version. Do you recommend the Octoplus Pro Box or the Chinese Infinite Box Miracle II and why would you prefer one over the other? Thanks for your feedback.
Hello,
Did anyone managed to unlock bootloader on Realme 5i ?
I flashed the latest Android 10 firmware from RealMe website, everything went ok, but now I want to unlock bootlader to root the device, and it seems that nothing helps.
Please help, thanks
how to unlock the bootloader in Realme 5i RMX2030
Here is a good guide that worked for me to unlock the bootloader:
www ytechb com/how-to-root-realme-5i-and-unlock-bootloader/
The root part didn't work, Magisk complains about unknow boot image format
G0bl1n said:
Here is a good guide that worked for me to unlock the bootloader:
www ytechb com/how-to-root-realme-5i-and-unlock-bootloader/
The root part didn't work, Magisk complains about unknow boot image format
Click to expand...
Click to collapse
I've done the in-depth test and it's on the Fastboot screen but when I type fastboot flashing unlock in a command window it just shows me the help text for fastboot, which doesn't show any command or option for either flashing or unlock, so how can I get it to work if those aren't valid commands?
fastboot devices shows my phone, so the device is recognised.
EDIT: I'm still on Android 9 A.15. I understand that there's no unlocked for Android 10 yet.
EDIT: Nevermind. I was using adb/fastboot from the link in this guide, which is v1.3 https://www.ytechb.com/how-to-root-realme-5i-and-unlock-bootloader/
After I updated to minimal v1.43 from here it worked https://androidmtk.com/download-minimal-adb-and-fastboot-tool
My problem was same. But i successfully downgrade to color os 6. I guess you can try it too.
Enable USB Debugging and Allow unlock boot loader option in USB debugging.
Connect your mobile with PC and use following Command.
adb reboot bootloader
fastbook flashing unlock
Check mobile for unlock option.
How did you downgraded to colour os 6?
I'm trying to root my realme 5i that i upgraded to 10.
Can you help me?
M. Farhad said:
My problem was same. But i successfully downgrade to color os 6. I guess you can try it too.
Enable USB Debugging and Allow unlock boot loader option in USB debugging.
Connect your mobile with PC and use following Command.
adb reboot bootloader
fastbook flashing unlock
Check mobile for unlock option.
Click to expand...
Click to collapse
what's the next step
Hello to everyone that read and thanks you for the time passing to read my problem.
First of all : this is not my native language so excuse me for my english ... :/
After that, this is my first thread ... :/
And then , i'm tryin to learn but i'm pretty newbie on computing ... :/
(i'm trying to root my phone like every newbie does first by following slowly and accurately this tutorial: https://www.getdroidtips.com/root-wiko-view-3-lite/
i'm gonna details all i did step by step but at the end cause i don't think that the problem come from here)
so after etablishing the connection between my device and the PC using a wiko usb driver
i tried to flash my Wiko View 3 Lite ROM to boot the patched "boot.img" via Minimal ADB and Fastboot V1.4.3 (latest version)
so once i enter the command : fastboot flash boot "MyPatchedBootFile".img
i got a :
Failed.(flashing lock flag is locked. Please unlock it first!)
so i should able the flashing option somehow somewere ?
i tried several fastboot command but nothing... (btw i is there a way to kow all the comandes i can do on my PC cause i see the command changing depending phones or fastboot )
that's what i have :
FAILED (remote :Not implemet.)
i'm not sure to understand what "no implemet" mean ??
I can't find any useful info exept this one unfortunately that could be the same for my phone's model :
Rooting a wiko jerry is impossible due to all fastboot commands lock the phone
On Linux: All fastboot commands lock. Particularly fastboot oem unlock or fastboot flashing unlock. After removing and re-attaching the phone to the usb port (without turning it off), the phone bec...
android.stackexchange.com
i'm continuing to look for anwsers, can someone have an idea ??
( that's what i did:
1/ i've downloaded magisk.apk's last vertion on my phone
2/ found a Wiko View 3 Lite full ROM online for the rom.pac file
3/ converted it w the SPD flash tool (i didn't really understood this step :/) : https://www.getdroidtips.com/patch-boot-img-root-spreadtrum-device/
4/ sent it to my phone
5/converted it agan via magisk.apk on my phone
6/ took it back from my computer to the same folder that i launch the ADB and fastboot comand prompt
7/last step normally :/ i should write the command: fastboot flash boot xxxxxxxxx.img and i gotstuck here ....
)
thanks again for all your help guys ))
Hakodu13 said:
...
so once i enter the command : fastboot flash boot "MyPatchedBootFile".img
i got a :
Failed.(flashing lock flag is locked. Please unlock it first!)
so i should able the flashing option somehow somewere ?
i tried several fastboot command but nothing... (btw i is there a way to kow all the comandes i can do on my PC cause i see the command changing depending phones or fastboot )
that's what i have :
FAILED (remote :Not implemet.)
i'm not sure to understand what "no implemet" mean ??
I can't find any useful info exept this one unfortunately that could be the same for my phone's model :
Rooting a wiko jerry is impossible due to all fastboot commands lock the phone
On Linux: All fastboot commands lock. Particularly fastboot oem unlock or fastboot flashing unlock. After removing and re-attaching the phone to the usb port (without turning it off), the phone bec...
android.stackexchange.com
i'm continuing to look for anwsers, can someone have an idea ??
...
Click to expand...
Click to collapse
Before trying to deal with phone's bootloader, will say running any Fastboot commands, you have to enable "OEM unlock" option in phone's Android Settings->Developer option. If done so, reboot phone. Afterwards run Fastboot commands
Code:
fastboot devices
fastboot oem unlock <- or: fastboot flashing unlock
jwoegerbauer said:
Before trying to deal with phone's bootloader, will say running any Fastboot commands, you have to enable "OEM unlock" option in phone's Android Settings->Developer option. If done so, reboot phone. Afterwards run Fastboot commands
Code:
fastboot devices
fastboot oem unlock <- or: fastboot flashing unlock
Click to expand...
Click to collapse
Hey
Thanks for your awnser,
i did it already, i've activated EOM unlock , USB debug and also desactivated the standby when the phone is plugged
also i think all fastboot command work cause i can reboot my phone using "fastboot reboot"command
fastboot devices reconize my phone
fastboot flashing unlock dosn't work
it is writed: FAILED (remote: Not implemet.)
fastboot oem unlock dosn't work,
it is writed: FAILED (remote: unknown cmd.)
something interesting is when i write fastboot "AnithingElse" unlock
it says: fastboot: usage: unknown command "AnithingElse"
and no: FAILED (remote: unknown cmd.)
like if adbandfastboot know the commannd " fastboot oem unlock " somehow but not my phone.
thanksthanksthanks again for your awnser!!!
My guess is that running Fastboot commands is denied by OEM/Carrier. And that's not wondering me because phone is based on UniSoc chipset.
AFAIK to get Fastboot working on such phones you have to request from OEM/Carrier the unlock-code as 1st thing of all things and when received have to flash it to phone.
jwoegerbauer said:
My guess is that running Fastboot commands is denied by OEM/Carrier. And that's not wondering me because phone is based on UniSoc chipset.
AFAIK to get Fastboot working on such phones you have to request from OEM/Carrier the unlock-code as 1st thing of all things and when received have to flash it to phone.
Click to expand...
Click to collapse
Ye i guessed the commands is denied on purpose
but why ? just for me not to have root acces ?
and what if i want to flash or reflash my ROM just to have back a new fresh boot ?
do a lot of phone constructor use that radical trick ?
and what is OEM/Carrier ? where can i find this ? i can't find anything online ...
merci ))
OEM is an acronym and stands for Original Equipment Manufacturer ( e.g Samsung )
Carrier is the is cell phone company that provide cellular service to cell phone users ( e.g. AT&T, Verizon )
Hi, i am loading booting to bootloader from adb with commnad (adb reboot bootloader) this isnt working, only restart its instantly switch to normal os, any ideas ?
Run
Code:
adb reboot
or
Code:
fastboot reboot
oh sorry man, i am idiot, and i am say it wrong.. I trying boot to fastboot but not working instantly switch to os, any ideas please ?
Unlock bootloader if not done yet.
where i unlock bootloader ? In developer settings ? (i have unlocked)
Enabling OEM Unlock in Developer options doesn't unlock the bootlader, it simply prepares the bootloader to get unlocked via fastboot command.
More info here:
How to Unlock Bootloader via Fastboot on Android
Unlocking the bootloader via Fastboot is the easiest thing to do. But not all Android devices support straightforward bootloader unlocking. Many manufacturers put up a setup on their devices to let…
nerdschalk.com
xXx yYy said:
Enabling OEM Unlock in Developer options doesn't unlock the bootlader, it simply prepares the bootloader to get unlocked via fastboot command.
More info here:
How to Unlock Bootloader via Fastboot on Android
Unlocking the bootloader via Fastboot is the easiest thing to do. But not all Android devices support straightforward bootloader unlocking. Many manufacturers put up a setup on their devices to let…
nerdschalk.com
Click to expand...
Click to collapse
Only I have a small problem I don't unlock my bootloader via fastboot when it doesn't work :/ It immediately jumps to my system when I boot fastboot, even with a command like ,,adb reboot fastboot"
Matyas66055 said:
Only I have a small problem I don't unlock my bootloader via fastboot when it doesn't work :/ It immediately jumps to my system when I boot fastboot, even with a command like ,,adb reboot fastboot"
Click to expand...
Click to collapse
I have new thread, where i am writing all info :/ https://forum.xda-developers.com/t/zte-blade-a7-2019-fastboot-mode-missing.4462035/
I don't know if you are still interested in accessing Fastboot but you can access it using a specific firmware version.
Still, let me tell you that unlocking the bootloader is virtually impossible. Since the well-known generic method doesn't work for the SoC SC9863A, you need to have a special Fastboot's program version and a dedicated private key that only they provide.... and I emphasize the word "dedicated" since apparently ZTE did not use a generic key to sign their ROMS. At least on this device.
Unless they decide to release the key or give support to unlocking the bootloader, all we can do is wait for them to change their minds. Because they don't want to provide it. I know because I tried to order it several times.