If you've followed my prototype ABL image release topics so far, then you should know where it comes from.
This topic will be edited later if X20 one is available.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WARNING: This is not a guide! Prototype ABL binaries are provided as-is, flashing them can be risky!
DO NOT FLASH IT INTO X20 OR IT WILL CAUSE DEAD BRICK!
1. Enable flashing permission with HDK (an internal flash tool used by triple-color company, sorry can't disclose more details about that). Please search for related service online, we don't provide or promote such service.
2. Download Prototype ABL from following URL:
Click here for Nokia X10 (ScarletWitch)
Click here for Nokia X100 (Deadmau5)
3. Flash prototype ABL manually, then you can confirm bootloader unlock:
Code:
(Nokia X10) fastboot flash abl SCW-abl.elf
(Nokia X100) fastboot flash abl DM5-abl.elf
fastboot reboot-bootloader
fastboot oem unlock-go
4. Once bootloader unlock completed, please reinstall stock OS to restore ABL back to normal.
SHA256 checksum of ABL image:
Code:
SCW-abl: 3a949e4b27c1b559cfd016a894fc1a4bb81d01c9ab323a86ab2603c313f4177b
QKS-abl: missing
DM5-abl: f16bafb998925b7a3f7651eb21edba8bb4283113f56628d9b0b685882015696b
Root Key Hash of ABL images:
Code:
Nokia X10: F552CB7380F2F46F92B4CC25AB923A8A234A45357601BEE1CC06D42C0790C4A0
Nokia X20: 2FDC6D616C061309BBADDDCA9C69CA0F3F8CA0E1CDF5F74F274E34B77F5CE8B6
Nokia X100: 05C8E21116890E3DAF3879ED4939F7F6267A3CA2085E3E943743E938C80C28C1
I'll have a go, thanks!
Alvy123 said:
I'll have a go, thanks!
Click to expand...
Click to collapse
it requires you to gain access of the tool from tri-color company, which is.... actually impossible.
The only way one can use it without any restrictions is if the same one is Nokia's customer support....
hikari_calyx said:
If you've followed my prototype ABL image release topics so far, then you should know where it comes from.
This topic will be edited later if X20 one is available.
WARNING: This is not a guide! Prototype ABL binaries are provided as-is, flashing them can be risky!
DO NOT FLASH IT INTO X20 OR IT WILL CAUSE DEAD BRICK!
1. Enable flashing permission with HDK (an internal flash tool used by triple-color company, sorry can't disclose more details about that). Please search for related service online, we don't provide or promote such service.
2. Download Prototype ABL from following URL:
Click here
3. Flash prototype ABL and OEM unlock enabled frp partition manually, then you can confirm bootloader unlock:
Code:
fastboot flash abl SCW-abl.elf
fastboot reboot-bootloader
fastboot oem unlock-go
4. Once bootloader unlock completed, please reinstall stock OS to restore ABL back to normal.
SHA256 checksum of ABL image:
Code:
3a949e4b27c1b559cfd016a894fc1a4bb81d01c9ab323a86ab2603c313f4177b
Root Key Hash of ABL images:
Code:
Nokia X10: F552CB7380F2F46F92B4CC25AB923A8A234A45357601BEE1CC06D42C0790C4A0
Nokia X20: 2FDC6D616C061309BBADDDCA9C69CA0F3F8CA0E1CDF5F74F274E34B77F5CE8B6
Click to expand...
Click to collapse
can I use 3rd-party tools (e.g: Fire Tool) to enable flashing perms, instead of HDK?
I presume that this is all supposed to be a bit of a mystery.
I have a custom abl on a different device.
I just de-engineered it, patched it, re-hashed it.
But thiat device does not have SecureBoot enabled.
That's a rarity.
Renate said:
I presume that this is all supposed to be a bit of a mystery.
I have a custom abl on a different device.
I just de-engineered it, patched it, re-hashed it.
But thiat device does not have SecureBoot enabled.
That's a rarity.
Click to expand...
Click to collapse
Oh wow, that's interesting. Mind telling me the full details about what you did?
AltFantasy said:
Mind telling me the full details about what you did?
Click to expand...
Click to collapse
Here's a whole thread on abl packing: https://forum.xda-developers.com/t/qualcomm-abl-android-bootloader-packing-signing.4473815/
Then there's the reverse engineering, probably using Ghidra or Ida.
Ghidra annoys me so I use my own custom stuff that simply annotates what objdump puts out.
I feel closer to the metal that way.
After unpacking/patching/packing abl you've got a modified abl that the signing is wrong.
If you're Nokia, you just take your super-secret private key and resign the abl.
If SecureBoot is not enabled on your device it does not need to be signed, but it needs to be hashed.
Hashing is not at all secret, it's just SHA256 or SHA384 on the program segments (one of which you altered).
My qcomview.exe can do that easily, it's in the sig.
I tested it for somebody; the unlock works by utilizing this abl. Thanks for the share
so far, not much luck
Nokia X10 (X20) Android 13 chances of new ROM/ some-any ways to override settings/ "jail-break"???
In short : X10, UK, Android 13 - thanks, no thanks! 0 actual improvements as per discussed to some degree on Nokia "support forum". Silly bloatware "features" added, but nothing what would be useful. Have tried 50 apps of different kinds...
forum.xda-developers.com
However, since security update, in "developer mode", I've had an option to unlock OEM loader- DONE! restarted the phone- still shows the same- bootloader UNLOCKED
Alvy123 said:
so far, not much luck
Nokia X10 (X20) Android 13 chances of new ROM/ some-any ways to override settings/ "jail-break"???
In short : X10, UK, Android 13 - thanks, no thanks! 0 actual improvements as per discussed to some degree on Nokia "support forum". Silly bloatware "features" added, but nothing what would be useful. Have tried 50 apps of different kinds...
forum.xda-developers.com
However, since security update, in "developer mode", I've had an option to unlock OEM loader- DONE! restarted the phone- still shows the same- bootloader UNLOCKED
Click to expand...
Click to collapse
that option is actually useless.
Related
[GUIDE] Unlock the bootloader of OnePlus X without using fastboot & wiping userdata
Introduction
As we know, the official way to unlock the bootloader of OnePlus X is through fastboot.
For a untouched device, the status of the bootloader should be:
Code:
fastboot oem device-info
...
(bootloader) Device tampered: [COLOR="Red"]false[/COLOR]
(bootloader) Device unlocked: [COLOR="Red"]false[/COLOR]
To unlock the bootloader, you need to enable 'OEM unlocking' under Developer options first, then via bootloader/fastboot interface:
Code:
fastboot oem unlock
It'll eventually erase the userdata.
Then the status of the bootloader should be:
Code:
fastboot oem device-info
...
(bootloader) Device tampered: [COLOR="Red"]false[/COLOR]
(bootloader) Device unlocked: [COLOR="Red"]true[/COLOR]
Inspired by the findings on similar devices, we can actually unlock the bootloader of OnePlus X without using fastboot, while keeping the userdata intact.
How-to
Warning!
It is dangerous! This whole thing is basically one giant hack - which is not intended to be done by normal users. It is messing with the bootloader partition, so it is possible that something goes wrong and you will have a nice & costly brick in your pocket. Be prepared to revive the device from a hard-brick.
1.
Enable 'OEM unlocking' under Developer options. You may need to tap the Build number 7 times under About phone to get the Developer options under Settings.
2.
We need root access (kinda expected!). To root the device without unlocking bootloader, use KingRoot. Use the Android version.
Now there is a catch! KingRoot can root the device, cause the latest build of Oxygen OS (2.2.1 ATM) contains such vulnerabilities which can be exploited by the root exploits used by KingRoot. But we can't ensure about future.
See here for more info.
3.
After being rooted, use adb shell or any terminal emulator to dump the 'aboot' i.e bootloader partition in internal sdcard:
Code:
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img
4.
Now we need to modify the dumped image using hex-editor. For OnePlus X:
Code:
Unlock Bit Position - 0x000FFE10 Hex
Tamper Bit Position - 0x000FFE14 Hex
'00' means false, '01' means true. So to set the bootloader as unlocked, we just need to change the following:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Save the modified image as 'abootmod.img' inside your sdcard.
5.
Now its time to flash back the modded bootloader. Execute the following from adb shell or any terminal emulator:
Code:
su
dd if=/sdcard/abootmod.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Do a reboot & voila! You have unlocked the bootloader! Don't just believe me - check the status of the bootloader to ensure.
Note
1. We can also reset the tamper bit using this procedure.
2. If you prefer GUI, then you can use this fantastic app by @wanam.
3. This is tested on an Asia/EU (E1003) variant of OnePlus X running Oxygen OS 2.2.1. Please test & post feedback to ensure compatibility.
4. I'm not providing pre-modified images as it increases the risk of bricking the devices having older/newer bootloaders - please do it yourself. The offsets should be unchanged in future, though.
Credits
1. @osm0sis
2. @segv11
3. @Mnt-XDA
4. My sister - for risking her device for this experiment.
5. Users of XDA & OnePlus forums.
Happy tinkering! :highfive: :good:
Reserved for future.
Where is the 000FFE14 hex ?
Found 000FFE10 hex but no 14?
Can you provide the aboutmod.img?
Sent from my ONE E1003 using XDA-Developers mobile app
sifatrhmn said:
Where is the 000FFE14 hex ?
Found 000FFE10 hex but no 14?
Can you provide the aboutmod.img?
Click to expand...
Click to collapse
It is on the same line of OOOFFE10 after four positions you will see 1 it is 000FF14 change that to O
shravanv3 said:
It is on the same line of OOOFFE10 after four positions you will see 1 it is 000FF14 change that to O[/QUOTE
where can i found line of bootloader on another device ?
there is somthing special to identified the bootloader line ?
thanks
Click to expand...
Click to collapse
deleco said:
shravanv3 said:
It is on the same line of OOOFFE10 after four positions you will see 1 it is 000FF14 change that to O[/QUOTE
where can i found line of bootloader on another device ?
there is somthing special to identified the bootloader line ?
thanks
Click to expand...
Click to collapse
No 000FF10 is for bootloader
Click to expand...
Click to collapse
shravanv3 said:
deleco said:
No 000FF10 is for bootloader
Click to expand...
Click to collapse
excuse me but cant understand
i mean line to identified the bootloader to change 00 to 10
where can i found it on another devices ?
hope you can understand me now
thanks
Click to expand...
Click to collapse
Avoid and pass by a fool and a madman
Wow, great post and great work bro, this post is very informative indeed. I hope that you can finish you tool soon, I can help testing it if you need testers.
wga0 said:
Universal Image Extractor:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It seems that I succeeded in making the Universal Image Extractor. With the latest update engine, it works on any ota for any brand, any version, including the incremental also. But still, lots of work remained....
Complete Fastboot ROMs:
Now, you can build the complete Fastboot ROMs with some more info in your phone, even if your phone's manufacture never release it. To make it complete, you need to include the other roms which is not inside the ota(update.zip), and some more info such as partition type&align, because android has dynamic partitions and it can be changed between the different versions. If your roms were deleted and the partition info gone, you need it definitely.
Unfortunately, this(backup other roms not contained in the ota) requires root or rooted recovery. If you done root, backup all of your roms except userdata, all of the partition info, and keep it safe. If possible, make the fastboot rom yourself with those files/info. In black shark 2/pro cases, fortunately, the partition info is not changed upto now...
First, these code should come first to recover the partition info. It does re-partitioning and align including the two slots.
Code:
%fastboot_cmd% flash partition:0 gpt_both0.bin
%fastboot_cmd% flash partition:1 gpt_both1.bin
%fastboot_cmd% flash partition:2 gpt_both2.bin
....(all partitions)
In BS2/pro cases, it has align.bin info. It also should be flashed here to align the partition position
Second, the bootloader needed to be changed as the fastboot roms uses, and reboot into bootloader again. In cases that the bootloader has changed, extreme caution is required. If compatibility is not guaranteed, never try this (Fastboot ROMs). When doing this, flash only one bootloader to check the boot compatiblity, and after reboot successfully, flash the other slot.
Code:
%fastboot_cmd% flash abl_a abl.img
%fastboot_cmd% reboot-bootloader
timeout /t ....
In BS2/pro Android 10 cases, it's changed completely, you should never try this (Fastboot ROMs)
Third, re-setting and flash all the roms (including which is not inside the ota) are required to be fully recovered
Code:
%fastboot_cmd% oem simconfig set SS
%fastboot_cmd% flash avb_custom_key pkmd.bin
%fastboot_cmd% erase ddr
%fastboot_cmd% erase userdata
%fastboot_cmd% erase ....(all security key related)
%fastboot_cmd% flash roms...
More than Fastboot ROMs & Factory OTAs:
And now with the tool, it seems that I found a way to build a flashable update.zip, same as the factory OTA or Fastboot ROMs. It seems like it has both pros. It doesn't require rooting, unlocking bootloader, etc... Even if your phone's manufacturer never release the factory OTA, even if your phone never boot(bricked), you still could build and flash(update/rollback/recover) it without rooting & unlocking...
Here's the idea. (I found this inside the update_engine & OTA packaging sources)
With the universal image extractor, you can build any images and that images are stock(factory) images signed by the manufacturer. So, if I add(import) that ota packaging sources into the tool, I can build the factory OTA itself anytime with the tool. But unfortunately, although that factory OTA contains all signed, stock images & info, zip file itself isn't signed by the manufacturer and rejected by the system. (can't be flashed using 1027 code). Then... what if I can use it in bootloader or recovery? Stock recovery of BS has only one function, factory reset. Then fastboot?
It seems that I found a way to build an update.zip, same as the Factory OTA but can be used in bootloader, and a way to update(not flash) it in bootloader, bypassing the signature check of update.zip itself. So ideally, it doesn't require anything root or unlock, and can be updated and boot successfully through the locked bootloader because all of the images inside the zip are signed by manufacturer. Further, you don't need to push it into phone anymore. After entering bootloader, one command is enough. It's easier and powerful than both Fastboot and Factory OTA images. (not as powerful as complete Fastboot ROMs that contains all the roms which is not in OTAs...)
A bad things is..... this is just an possibility(idea) found inside the source codes currently.... and requires a lots of works in windows, like the universal image extractor.
Click to expand...
Click to collapse
Thank you for your thread. I'm going to study this!
I'm posting on here as no thread for Honor 6X exists.
For context, I'm trying to root my Honor X6 (not 6X). My plan was to unlock its bootloader, flash a patched vbmeta image, fetch the boot partition to patch with Magisk, and flash the boot img to root it (no custom ROM or kernel as none exist to my knowledge).
Considering that the phone is very recent (Sept 2022), I initially thought no methods existed to unlock its bootloader. I booted it into download mode (here's a screenshot):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Running fastboot flashing unlock prompts me to unlock the bootloader, as shown here:
Restarting to the OS causes a bootloop, indicating an unlock bootloader, only fixed by relocking it. However, running any privilidges commands in fastboot returns Command not allowed as if it's still locked, and rebooting into download mode shows the first picture.
With this in mind, I want to ask you all how (or can) I properly unlock my phone's bootloader?
Zolaxity said:
I'm posting on here as no thread for Honor 6X exists.
Click to expand...
Click to collapse
Hello and good morning, @Zolaxity
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 your thread to Android Q&A.
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
Zolaxity said:
I'm posting on here as no thread for Honor 6X exists.
For context, I'm trying to root my Honor X6 (not 6X). My plan was to unlock its bootloader, flash a patched vbmeta image, fetch the boot partition to patch with Magisk, and flash the boot img to root it (no custom ROM or kernel as none exist to my knowledge).
Considering that the phone is very recent (Sept 2022), I initially thought no methods existed to unlock its bootloader. I booted it into download mode (here's a screenshot):
View attachment 5782787
Running fastboot flashing unlock prompts me to unlock the bootloader, as shown here:
View attachment 5782791View attachment 5782797
Restarting to the OS causes a bootloop, indicating an unlock bootloader, only fixed by relocking it. However, running any privilidges commands in fastboot returns Command not allowed as if it's still locked, and rebooting into download mode shows the first picture.
With this in mind, I want to ask you all how (or can) I properly unlock my phone's bootloader?
Click to expand...
Click to collapse
Huawei does not allow unlocking the bootloader without a code.
Step 1. Take apart the phone
Step 2. Use the testpoints with potatonv
Step 3: Put it back together
Step 4: OEM unlock it with your code
Step 5: Unlock it from fastboot
NOTE: YOUR CHIPSET MAY NOT BE SUPPORTED
Got it.
Seems the Honor X6 uses MediaTek - which isn't a supported chipset - so unlocking the bootloader may not be possible.
Zolaxity said:
Got it.
Seems the Honor X6 uses MediaTek - which isn't a supported chipset - so unlocking the bootloader may not be possible.
Click to expand...
Click to collapse
https://github.com/bkerler/mtkclient try this to unlock the bootloader
I've tried without shorting the testpoint, with no phone detection by mtkclient. I'm now searching for any knowledge of the Honor X6's testpoint (although it's unlikely anything will show up).
Can I just attempt as many "points" of the phone until one works with mtkclient as the testpoint, or could this be unsafe? (just in case)
You should've already figured out where are these binaries from. I can't help further for these 2 models.
WARNING: This is not a guide! Prototype ABL binaries are provided as-is, flashing them can be risky!
I'm not responsible for potentially permanent brick!
Nokia 3.4 prototype ABL image has been proved functional.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To use it:
1. Enable flashing permission with HDK (an internal flash tool used by triple-color company, sorry can't disclose more details about that). Please search for related service online, we don't provide or promote such service.
2. Download Prototype ABL from following URL:
Click here for NOKIA 3.4 (DoctorStrange ZQL1838)
Click here for NOKIA 5.4 (DoctorDoom ZQL1849)
3. Flash prototype ABL and OEM unlock enabled frp partition manually, then you can confirm bootloader unlock:
Code:
(for Nokia 3.4) fastboot flash abl DRS-abl.elf
(for Nokia 5.4) fastboot flash abl DRD-abl.elf
(IMPORTANT, DO NOT SKIP) fastboot flash frp frp_oemunlock.img
fastboot reboot-bootloader
fastboot flashing unlock_critical
fastboot oem unlock-go
4. Once bootloader unlock completed, please reinstall stock OS to restore ABL back to normal.
SHA256 checksum of ABL images:
Code:
Nokia 3.4: 79d49737009b1c87f452d814ba6cf5669ccd35a2983f4413f817a7595cb67cfc
Nokia 5.4: 333b221671ed9abe6bd471f29d3c0b14cfeaeebcdc587f882097740f244b93a9
Root Key Hash of ABL images - technically they may interchangable due to same RKH.
Code:
Nokia 3.4: 35631A56E4F0D69967853A758FEF4FF742CF7C6A71B84CE863FE3FCBC70CC394
Nokia 5.4: 35631A56E4F0D69967853A758FEF4FF742CF7C6A71B84CE863FE3FCBC70CC394
This procedure requires specific version of Android? The HDK tool is provided only by the manufacturer?
Rierei said:
This procedure requires specific version of Android? The HDK tool is provided only by the manufacturer?
Click to expand...
Click to collapse
Specific Android version is not required.
HDK access is required to allow you flash any bootloader partitions.
where can i get frp_oemunlock.img and stock os?
are they available with HDK?
Hi guys, I have bootloader unlocked and rooted my Nokia 5.4! however when I tend to delete apps from the system as usual there is always some error! Android 12 February Security Patch!
if anyone wants a recovery image to do a TWRP I can give it!
Someone made it for 3.4?
thimemoria said:
Hi guys, I have bootloader unlocked and rooted my Nokia 5.4! however when I tend to delete apps from the system as usual there is always some error! Android 12 February Security Patch!
Click to expand...
Click to collapse
May you describe how did you manage to unlock the bootloader? Do you have HDK access?
false96 said:
May you describe how did you manage to unlock the bootloader? Do you have HDK access?
Click to expand...
Click to collapse
I got in touch via Telegram with the guy who does the unlocking via TeamViewer or Anydesk and he unlocked it, since the Root process is a little different I had to flash a different boot .img
As I probably can't post links here, whoever wants it I'll send it by PV
Guys, I made a port of TWRP from A3 to Nokia 5.4! Normal boot but need to edit fstab I'll do that and study how it works anything I'll let you know or create a topic!
thimemoria said:
Guys, I made a port of TWRP from A3 to Nokia 5.4! Normal boot but need to edit fstab I'll do that and study how it works anything I'll let you know or create a topic!
Click to expand...
Click to collapse
Great work! Thanks for your efforts. I hope one day we'll have some custom roms.
thimemoria said:
if anyone wants a recovery image to do a TWRP I can give it!
Click to expand...
Click to collapse
could you let me get a copy for the Nokia 5.4
thimemoria said:
As I probably can't post links here, whoever wants it I'll send it by PV
Click to expand...
Click to collapse
hey, I also want one for my Nokia X10!
I´m also interestet in the TWRP for Nokia 5.4 - could you send it to me by PV? Thanks on behalf
thimemoria said:
Hi guys, I have bootloader unlocked and rooted my Nokia 5.4! however when I tend to delete apps from the system as usual there is always some error! Android 12 February Security Patch!
Click to expand...
Click to collapse
That's likely because the system is only mounted as r/o. You can't write there. But maybe I am wrong?
thimemoria said:
if anyone wants a recovery image to do a TWRP I can give it!
Click to expand...
Click to collapse
I never received a message from you about the twrp for Nokia 5.4
does anyone have the twrp for Nokia 5.4
[email protected] said:
does anyone have the twrp for Nokia 5.4
Click to expand...
Click to collapse
eh, no one does. The phone has just had its ABL for bootloader unlocking released, so, of course, there are no TWRP ports for it.
However, you can learn how to port TWRP into the phone (though, really, it'll require you to learn programming and whatnot).
I was going by this post further up the thread.
thimemoria said:
if anyone wants a recovery image to do a TWRP I can give it!
For the last few days, I've wanted to install lineage on my phone, because the stock OS is very bad and uses 90% of the ram on idle, and it is full of bloatware and stupid issues. and the UI is not very good.
This whole post is long explaing about my failed efforts, you should read it all to avoid telling me stuff that i tried already.
What i tried?I tried using the basic way, for any android device. I got adb, and fastboot, and did the required steps. When i get into fastmode (after a whole day of fixing why my device is not detected by fastboot by the way), i tried many commands, they all DO NOT WORK in a confusing way, they are not recognized by the phone.
The following are the commands i tried, the response is always the same.
Bash:
fastboot oem unlock
fastboot flashing unlock
fastboot unlock
fastboot flashing unlock_critical
fastboot flashing get_unlock_ability
fastboot oem device-info # Yes! even this doesn't work...
And all of them give me the EXACT same response
Bash:
FAILED (remote: unknown command)
finished. total time: 0.002s # The time changes obviously
Ok then i got accross this post. According to the post, i had to use their fastboot. Which.. did not work, because it was stuck at < waiting for device >.
But i did not give up and i looked a bit through github, and i found this repository. I tried it and hopefully it detected my phone. However, the commands mentioned by the post, also gave me the same output of the previous commands, so it was not helpful.
Attempts #2So after this massive and confusing failure, i decided to try again, my friend told me i can use mediatek flash tool (stuff that i can barely understand currently) to flash TWRP, and use it to flash lineage. (Note: The Processor is MT6768)
So. i did a bit of research and i tried a few tools, for example TFTUnlock, SP Flash Tool. We managed to get the scatter file, and it should have worked... but it never did
So the problem with them is when i tried the fastboot method in TFTUnlock, it would try but also get unknown command, even the get device info button had the same problem. I tried the BROM Unlock which did not end up working, because the phone is probably not detected, when i plug it in (even while holding VOL+ and VOL-) i just hear window's sounds about device connection (actually multiple) then it continues charging, as if nothing happened. the application was still waiting for device. (and yes i got the drivers installed, and i had testmode on with driver enforcement disabled).
Wait but only one app did something different. The Smart Phone flash Tool had a special error when i connected usb (even if i do not hold VOL+ and VOL-) i had a special error, instead of just stuck at waiting. here's the error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Other Notes
I tried both Windows 10 and Windows 11
I tried Fedora (fastboot method) and i got the same results
Flashing with fastboot will end up in error Verify State Locked
fastboot getvar command actually gives an output which includes some information, in which says that the bootloader is locked.
I did not forget to enable OEM Unlocking, in case this is on your mind
I had kaspersky on my phone which gave me a weird warning about a firmware change (although i did not success in anything). Here's the screenshot
Thanks in advance for the absolute masters who will help me get this done!
To unlock this phone's bootloader this command is the correct one
Code:
fastboot bbk unlock_vivo
If you get a confirmation message on your screen, reply in affirmative (‘Yes’, ‘I agree’, Unlock the Bootloader’, etc).
jwoegerbauer said:
To unlock this phone's bootloader this command is the correct one
Code:
fastboot bbk unlock_vivo
If you get a confirmation message on your screen, reply in affirmative (‘Yes’, ‘I agree’, Unlock the Bootloader’, etc).
Click to expand...
Click to collapse
I tried that, it says unknown command, as i mentioned already
If Fastboot returns
FAILED (remote: unknown command)
Click to expand...
Click to collapse
then the Fastboot driver you use is a wrong one, means not suitable to phone. Point.
jwoegerbauer said:
If Fastboot returns
then the Fastboot driver you use is a wrong one, means not suitable to phone. Point.
Click to expand...
Click to collapse
Sorry I've been struggling for DAYS about drivers, could you send me the right drivers for my phone?
To be on the safe side request it directly from Vivo.
vivo Support - User Guides, FAQs, Service Center, System Update | vivo Global
Home of official the vivo support services. Here you can check the service center, IMEI, query spare parts prices, system updates, FAQs, and more.
www.vivo.com
jwoegerbauer said:
Request it directly from Vivo.
vivo Support - User Guides, FAQs, Service Center, System Update | vivo Global
Home of official the vivo support services. Here you can check the service center, IMEI, query spare parts prices, system updates, FAQs, and more.
www.vivo.com
Click to expand...
Click to collapse
Interesting, but why would they provide me that? I mean, I'm not a technician or a shop I'm just a user trying to improve my personal phone
jwoegerbauer said:
To be on the safe side request it directly from Vivo.
vivo Support - User Guides, FAQs, Service Center, System Update | vivo Global
Home of official the vivo support services. Here you can check the service center, IMEI, query spare parts prices, system updates, FAQs, and more.
www.vivo.com
Click to expand...
Click to collapse
I tried using the driver but same results