Firstly, I want to say thanks to those people for their help!
@hikari_calyx for getting a prototype ABL for the Nokia X10 for bootloader unlocking!
@singhnsk for providing me with his service, and guidance on the steps to unlock the bootloader + root the phone!
And secondly, a disclaimer:
Code:
/*
* The bootloader unlocking requires you to wipe your own data (by flashing new firmware).
* So, of course, I'm NOT RESPONSIBLE for any data loss caused by the process.
*/
Alright, with the credits and warning out of the way, here's some proof for the unlocking!
{
"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"
}
Steps to unlock the bootloader:
1. Unlock flashing permission with HDK (sorry, can't provide info on that tri-color company tool, but there are 3rd-party services for you to try, ask @singhnsk!)
2. Flash the prototype ABL, via those commands:
Code:
fastboot flash abl SCW-abl.elf
fastboot reboot-bootloader
fastboot oem unlock-go
3. Once the bootloader unlocking is done, flash a stock ROM (get them from here, and get the big ones (~1.7-2GB), NOT the security packages.) in order to get the ABL back to normal.
By the way, if you want to receive small, monthly security patches, please get the stock Android 12 firmware, then do an OTA upgrade to 13 when you're setting up your device.
As for the rooting, just grab a guide from XDA about using Magisk, or something....
However, there are a few things you need to take note of when using Magisk:
DO NOT USE THE BOOT IMAGE FROM OLD FIRMWARE YOU'VE DOWNLOADED FOR FLASHING IN THE BOOTLOADER UNLOCKING PROCESS BEFORE FOR MAGISK PATCHING IF YOU UPGRADED YOUR PHONE TO A NEWER VERSION DURING SETUP (e.g: using the boot.img file from Android 12 firmware when your phone already upgraded to Android 13 during setup process.) Doing this WILL BRICK YOUR WI-FI.
However, if you're already on Android 13 (with build number 3.370), but your phone upgraded to a newer security patch (e.g: March 2023 patch, build number 3.370_SP1) after rebooting, you can still use the old boot.img from the original Android 13 firmware, without any consequences.
Glad that everything went well with your Nokia X10.
AltFantasy said:
Firstly, I want to say thanks to those people for their help!
@hikari_calyx for getting a prototype ABL for the Nokia X10 for bootloader unlocking!
@singhnsk for providing me with his service, and guidance on the steps to unlock the bootloader + root the phone!
And secondly, a disclaimer:
Code:
/*
* The bootloader unlocking requires you to wipe your own data (by flashing new firmware).
* So, of course, I'm NOT RESPONSIBLE for any data loss caused by the process.
*/
Alright, with the credits and warning out of the way, here's some proof for the unlocking!
View attachment 5907045
View attachment 5907047
Steps to unlock the bootloader:
1. Unlock flashing permission with HDK (sorry, can't provide info on that tri-color company tool, but there are 3rd-party services for you to try, ask @singhnsk!)
2. Flash the prototype ABL, via those commands:
Code:
fastboot flash abl SCW-abl.elf
fastboot reboot-bootloader
fastboot oem unlock-go
3. Once the bootloader unlocking is done, flash a stock ROM (get them from here, and get the big ones (~1.7-2GB), NOT the security packages.) in order to get the ABL back to normal.
By the way, if you want to receive small, monthly security patches, please get the stock Android 12 firmware, then do an OTA upgrade to 13 when you're setting up your device.
As for the rooting, just grab a guide from XDA about using Magisk, or something....
However, there are a few things you need to take note of when using Magisk:
DO NOT USE THE BOOT IMAGE FROM OLD FIRMWARE YOU'VE DOWNLOADED FOR FLASHING IN THE BOOTLOADER UNLOCKING PROCESS BEFORE FOR MAGISK PATCHING IF YOU UPGRADED YOUR PHONE TO A NEWER VERSION DURING SETUP (e.g: using the boot.img file from Android 12 firmware when your phone already upgraded to Android 13 during setup process.) Doing this WILL BRICK YOUR WI-FI.
However, if you're already on Android 13 (with build number 3.370), but your phone upgraded to a newer security patch (e.g: March 2023 patch, build number 3.370_SP1) after rebooting, you can still use the old boot.img from the original Android 13 firmware, without any consequences.
Click to expand...
Click to collapse
Just installed a banking app today, and apparently, the app kept on whining about how my device is rooted, even though I put it in the Magisk DenyList. I did manage to fix the problem, though, by installing Shamiko.
AltFantasy said:
Firstly, I want to say thanks to those people for their help!
@hikari_calyx for getting a prototype ABL for the Nokia X10 for bootloader unlocking!
@singhnsk for providing me with his service, and guidance on the steps to unlock the bootloader + root the phone!
And secondly, a disclaimer:
Code:
/*
* The bootloader unlocking requires you to wipe your own data (by flashing new firmware).
* So, of course, I'm NOT RESPONSIBLE for any data loss caused by the process.
*/
Alright, with the credits and warning out of the way, here's some proof for the unlocking!
View attachment 5907045
View attachment 5907047
Steps to unlock the bootloader:
1. Unlock flashing permission with HDK (sorry, can't provide info on that tri-color company tool, but there are 3rd-party services for you to try, ask @singhnsk!)
2. Flash the prototype ABL, via those commands:
Code:
fastboot flash abl SCW-abl.elf
fastboot reboot-bootloader
fastboot oem unlock-go
3. Once the bootloader unlocking is done, flash a stock ROM (get them from here, and get the big ones (~1.7-2GB), NOT the security packages.) in order to get the ABL back to normal.
By the way, if you want to receive small, monthly security patches, please get the stock Android 12 firmware, then do an OTA upgrade to 13 when you're setting up your device.
As for the rooting, just grab a guide from XDA about using Magisk, or something....
However, there are a few things you need to take note of when using Magisk:
DO NOT USE THE BOOT IMAGE FROM OLD FIRMWARE YOU'VE DOWNLOADED FOR FLASHING IN THE BOOTLOADER UNLOCKING PROCESS BEFORE FOR MAGISK PATCHING IF YOU UPGRADED YOUR PHONE TO A NEWER VERSION DURING SETUP (e.g: using the boot.img file from Android 12 firmware when your phone already upgraded to Android 13 during setup process.) Doing this WILL BRICK YOUR WI-FI.
However, if you're already on Android 13 (with build number 3.370), but your phone upgraded to a newer security patch (e.g: March 2023 patch, build number 3.370_SP1) after rebooting, you can still use the old boot.img from the original Android 13 firmware, without any consequences.
Click to expand...
Click to collapse
Hmhm
World First - Nokia HMD Fire Tool V1.4 Nokia Online Game Over
About Nokia HMD Fire Tool V1.4: Nokia HMD Fire Tool V1.4 is a Windows base Tool for Services Nokia Devices, its allowed users to Unlock or flash all Nokia Android devices without Test Point(TP). it needs to buy a credit for used this tool. Nokia HMD Fire Tool V1.4 Latest Update: Nokia HMD...
www.martview-forum.com
so far isn't running on my PC to get in to X10.
am I doing something wrong?
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
Alvy123 said:
Hmhm
World First - Nokia HMD Fire Tool V1.4 Nokia Online Game Over
About Nokia HMD Fire Tool V1.4: Nokia HMD Fire Tool V1.4 is a Windows base Tool for Services Nokia Devices, its allowed users to Unlock or flash all Nokia Android devices without Test Point(TP). it needs to buy a credit for used this tool. Nokia HMD Fire Tool V1.4 Latest Update: Nokia HMD...
www.martview-forum.com
so far isn't running on my PC to get in to X10.
am I doing something wrong?
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
Click to expand...
Click to collapse
um, that tool doesn't let you enable flashing permission, or more like: the provider used to provide the service, but now, they no longer offer that sort of thing.
Related
This is the stock Rom of N & M for Yoga Book LTE & WIFI for the needers
if any dev want to help me developing a dual boot for Yoga Book, just PM me or join Telegram Group for Yoga Book devs and users:
MOD EDIT: LINK REMOVED
Prees the Thanks button if that helps you
How to install it:
Be careful, these steps will erase all your data on tablet and will downgrade rom (stock marshmallow)
First of all: read and understand all of the instructions.
1. Download the stock ROM
https://cloud.kolyandex.su/index.php/s/4WDt6ghOzHAyP4s (Nougat WiFi version)
https://easy-firmware.com/home/browse/category/id/19521/ (Marshmallo LTE version)
https://androidfilehost.com/?fid=817550096634799507 (Marshmallo WiFi version)
2. Extract it to some folder
3. Download Intel Platform Tool Lite from here: https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
4. Install Intel Platform Tool Lite
4. Boot into fastboot mode
5. Run Intel Platform Tool Lite
6. Make sure your tablet is recognized by the tool (otherwise you need to enable USB-debug in Developer settings)
7. Select "flash_update_from_eng.json" from folder in (2)
8. Push "start to flash"
9. Wait... (You should check tablet's screen in order to lock/unlock bootloader (it should be locked after flash in order to install OTA updates))
10. Reboot tablet
11. Your keyboard might not work: that is normal (just use on-screen keyboard for now)
12. After initial setup: open Contacts app, create new one (if there are no contacts yet), tap search and enter ####6020#
13. Choose your region
14. Reboot
15. Setup again (now halo should work)
16. Go into settings -> about -> updates and update till the last version (may take several hours)
17. Say thanks for alexjustes for his Amazing Steps
Thank you so much for posting this!
Have you tried flashing this through @danjac's TWRP build? I know trying to restore any nandroid backup made after the OTA upgrade to Nougat results in a boot loop.
beltani said:
Thank you so much for posting this!
Have you tried flashing this through @danjac's TWRP build? I know trying to restore any nandroid backup made after the OTA upgrade to Nougat results in a boot loop.
Click to expand...
Click to collapse
Unfort. no, because i dont have a YB Android Version, i have win ver.
THE MAXIMUM POWER said:
Unfort. no, because i dont have a YB Android Version, i have win ver.
Click to expand...
Click to collapse
I'm 99% sure this isn't flashable in custom recovery, at least without some modification and repackaging. It's a package designed for Intel Phone Flash Tools.
Still a huge asset, though, so thanks again!
beltani said:
I'm 99% sure this isn't flashable in custom recovery, at least without some modification and repackaging. It's a package designed for Intel Phone Flash Tools.
Still a huge asset, though, so thanks again!
Click to expand...
Click to collapse
Same, it can only flashed through fastboot mode
I got myself into quite the pickle today. I've been considering selling my Yogabook to switch to a Chromebook 2-in-1. I wanted to get the device back to as full vanilla as possible. I "thought" the first step was to lock the bootloader again and then do a full factory reset, apparently not... After booting back up from locking the bootloader I kept getting an Intel "bootloader error code 01" and Android would not start. It would take me to fastboot mode on it's own but I was unable to use the power button to make a selection and the device would just power off after 5 minutes. Thankfully from there or fore powering off I could hold Volume up on startup and get to fastboot manually or recovery. It being in a locked state now though I couldn't do much of anything else, no flashing anything other than loader, no format, no erase, and TWRP was not able to be booted.
Anyway I finally read a post about DNX mode and how to get to it, but nothing on how to really use it or any decent information imho. After finally finding some users on another part of the forum discussing a DNX flashing tool made for their devices HTC I went searching for a tool for the Lenovo. Lenovo has nothing for this (shame on you Lenovo!) but Intel does have it and it can be used with the recovery image posted above in this thread (and I assume all the others running around). And here is the URL for the tool
https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
You just have to load a valid JSON file containing the proper config information for the ROM you are flashing iwithin the Intel tool. For this particular version of the ROM I did have to modify the "flash_recover_dnx.json" file to remove this section
Code:
{
"duration" : 5000,
"restrict" : null,
"tool" : "sleep"
},
Otherwise the flash tool would not load it due to the a bad tool from this JSON config named "tool". No other changes to the settings of the Intel flashing tool were needed.
Just click "Start to Flash" and once it was done all was well. Took a little over five minutes, it unlocked, flashed, and locked the device again itself.
{
"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"
}
No more Intel error stating the device isn't secure every reboot. I did lose all my data that was on it doing this but I wasn't worried about that going into it.
After initial setup in Android I did have to do the trick noted here to get the Halo keyboard working again which then required initial setup once more.
Hope this helps others.
@MarkAllen, thank you for your valuable information. This will help people unbrick their devices.
MarkAllen said:
I got myself into quite the pickle today. I've been considering selling my Yogabook to switch to a Chromebook 2-in-1. I wanted to get the device back to as full vanilla as possible. I "thought" the first step was to lock the bootloader again and then do a full factory reset, apparently not... After booting back up from locking the bootloader I kept getting an Intel "bootloader error code 01" and Android would not start. It would take me to fastboot mode on it's own but I was unable to use the power button to make a selection and the device would just power off after 5 minutes. Thankfully from there or fore powering off I could hold Volume up on startup and get to fastboot manually or recovery. It being in a locked state now though I couldn't do much of anything else, no flashing anything other than loader, no format, no erase, and TWRP was not able to be booted.
Anyway I finally read a post about DNX mode and how to get to it, but nothing on how to really use it or any decent information imho. After finally finding some users on another part of the forum discussing a DNX flashing tool made for their devices HTC I went searching for a tool for the Lenovo. Lenovo has nothing for this (shame on you Lenovo!) but Intel does have it and it can be used with the recovery image posted above in this thread (and I assume all the others running around). And here is the URL for the tool
https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
You just have to load a valid JSON file containing the proper config information for the ROM you are flashing iwithin the Intel tool. For this particular version of the ROM I did have to modify the "flash_recover_dnx.json" file to remove this section
Code:
{
"duration" : 5000,
"restrict" : null,
"tool" : "sleep"
},
Otherwise the flash tool would not load it due to the a bad tool from this JSON config named "tool". No other changes to the settings of the Intel flashing tool were needed.
Just click "Start to Flash" and once it was done all was well. Took a little over five minutes, it unlocked, flashed, and locked the device again itself.
No more Intel error stating the device isn't secure every reboot. I did lose all my data that was on it doing this but I wasn't worried about that going into it.
After initial setup in Android I did have to do the trick noted here to get the Halo keyboard working again which then required initial setup once more.
Hope this helps others.
Click to expand...
Click to collapse
Thank You for the INFOS
The tool does not recognized my device
Please help to flash my yoga book.
Got these with the stock .json file as described above:
06/18/18 12:00:01.188 ERROR : No description value in command sleep
06/18/18 12:00:01.188 ERROR : Cannot create command with tool "sleep"
06/18/18 12:00:01.188 ERROR : Tool sleep not found or invalid tool configuration
Opened that file in notepad and deleted the sleep section - started flashing.
The usb drivers are definitely required, I lost the connection because they weren't loaded. I installed them and refreshed device manager and she started receiving the flash.
Used Win7 to flash also, the intel page says its not supported.
Flash success and locked bootloader after entering the country code - thanks very much all!
jeitana said:
Please help to flash my yoga book.
Click to expand...
Click to collapse
Try installing Android SDK drivers in you PC
Guys, if anyone faced a Probleme during his way to flash the ROM, PLZ tell me the problems with More Details
_Deeb0_ said:
Got these with the stock .json file as described above:
06/18/18 12:00:01.188 ERROR : No description value in command sleep
06/18/18 12:00:01.188 ERROR : Cannot create command with tool "sleep"
06/18/18 12:00:01.188 ERROR : Tool sleep not found or invalid tool configuration
Opened that file in notepad and deleted the sleep section - started flashing.
The usb drivers are definitely required, I lost the connection because they weren't loaded. I installed them and refreshed device manager and she started receiving the flash.
Used Win7 to flash also, the intel page says its not supported.
Flash success and locked bootloader after entering the country code - thanks very much all!
Click to expand...
Click to collapse
Is this compatible with the Yoga Book A12?
I have been away for a while. Why should I want to install this rom?
Ok I wanted to reset this tablet because the SystemUI ap was using %25 of the cpu constantly, I do not know when and hopw this piece of **** got to that level of crappy update, must be some google crap
- Can I unlock the OEM bootloader?
- Can I still use the twrp->Magisk method to root this?
thanks
Shawnki91 said:
Is this compatible with the Yoga Book A12?
Click to expand...
Click to collapse
Sorry but no
hajkan said:
I have been away for a while. Why should I want to install this rom?
Click to expand...
Click to collapse
No Need to reinstall this Rom if you have already your System, both are 100 % same
hajkan said:
Ok I wanted to reset this tablet because the SystemUI ap was using %25 of the cpu constantly, I do not know when and hopw this piece of **** got to that level of crappy update, must be some google crap
- Can I unlock the OEM bootloader?
- Can I still use the twrp->Magisk method to root this?
thanks
Click to expand...
Click to collapse
Reinstall the Rom will fix this, but doing factory reset will fix this too
In case anyone wants the wifi only M firmware here it is https://androidfilehost.com/?fid=817550096634799507
If you want to repost this guide to other websites, please let me know before you repost.
For Chinese users: 中文版教程将会在dospy发布。
Click to expand...
Click to collapse
So after you unlock the bootloader successfully, you definitely want to install custom ROM, or at least root the phone, right?
Here's the guide about rooting Nokia 3.2 / 4.2.
This guide could probably work on Nokia 6.2 / 7.2 in the future.
Step 1: Unlock the bootloader
https://forum.xda-developers.com/nokia-4-2/how-to/guide-how-to-unlock-bootloader-nokia-4-2-t3962402
For Nokia 3.2, you'll need to read this as well: https://forum.xda-developers.com/nokia-3-2/how-to/guide-how-to-trigger-nokia-3-2-to-edl-t3962841
Step 2: Acknowledge current slot
You have two methods.
Method 1: After USB debugging enabled, execute this command:
Code:
adb shell getprop ro.boot.slot_suffix
Method 2: Under fastboot mode, execute this command:
Code:
fastboot getvar current-slot
We assume the current slot is b.
Step 3: Trigger the phone to EDL mode again
There's a hidden command in aboot known as "fastboot reboot-emergency".
However, normal fastboot binary doesn't have that command at all, so we need to compile a binary or hack the binary.
For Windows users, I've provided the fastboot binary that can use this command, and I renamed it to edl-fastboot.exe. You can download it on the attachment below.
For macOS/Linux distro users, I'm afraid you have to fork the source code, edit related content and compile yourself.
So with this special version of fastboot binary, we can boot the phone to EDL mode directly:
Code:
edl-fastboot.exe reboot-emergency
But wait, why didn't you mention this command when you released bootloader unlock guide?
That's because, if you attempt to use this command under locked bootloader, bootloader will response "Permission denied, auth needed. " and refuse to proceed the command.
I don't know how the authentication is done yet, but it's definitely not something that average developers can access to.
Click to expand...
Click to collapse
Step 4: Use partition manager to dump the partition
If you've came so far when unlocking the bootloader, you have already know the great partition manager.
Still, we assume the COM port number is 8 (COM8).
When the partition list appears, find "boot_b" (or boot_a if the current slot is a), right click on it, choose "Manage Partition Data" and click "Read Data". Then fh_loader binary will dump the boot image to your PC.
For Windows users, it's located at
Code:
%AppData%\Qualcomm\QFIL\COMPORT_8
Where %AppData% is actually C:\Users\your_user_name\AppData\Roaming .
The filename looks like this: ReadData_emmc_Lun0_0x3a000_Len65536_DT_07_09_2019_13_55_54.bin
Now close the partition manager, your phone will exit EDL mode and boot normally.
If you're interested in dumping full eMMC storage, you may want to read this: https://forum.xda-developers.com/android/general/guide-how-to-dump-write-storage-t3949588
Step 5: Install Magisk Manager and patch the boot image you dumped
I think everyone who reading this guide knows where to download Magisk Manager.
Copy the boot image you dumped with QFIL to Download directory in your phone's internal storage, and rename it to boot.img for your convenience.
In case you don't know how to patch, read this guide: https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
Step 6: Flash patched boot image and reinstall Magisk for ensurance
After you pulled patched boot image from your phone, reboot your phone to fastboot mode, then execute these commands:
Code:
fastboot flash boot magisk_patched.img
fastboot reboot
Note, temporarily boot method introduced back for old A/B devices like Nokia 7 Plus no longer works on Nokia 3.2 / 4.2 - it will boot your phone to Qualcomm 900E mode.
Once your phone booted to normal OS, open Magisk Manager, and reinstall Magisk and required runtime to make the root much more effective.
You may want to read this guide if you want to inherit root along with OTA update: https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Extra info about custom rom:
I've tested PHH-Treble GSI on Nokia 4.2 and it made me disappointed.
The vendor compatibility is worse than FIH made Android Phones.
You may want to read this for more details: https://github.com/phhusson/treble_experimentations/wiki/Nokia-4.2
Next preview: Stock firmware reinstallation guide. Note, Nokia 3.2 / 4.2 are not made by FIH, so OST LA no longer works on both devices.
Special thanks:
@topjohnwu for Magisk
Wingtech for leaking prototype units
Reserved
not detected
my pc doesn't detect the phone when its in edl mode. before people start asking I unlocked the bootloader by enabling oem unlock in the phone settings.
I have a TA-1156 (a 3.2 variant) that has a different mainboard layout. For quite a while, I tried in vain to bring it into EDL mode - until I just tried the fastboot command "flash unlock" which worked.
I guess I should have tried that right away as I did have the OEM unlocking option in the developer setup.
Anyway, now I'm unlocked but can't access the partitions with the QFIL partition manager. I suspect the phone expects a different programmer than prog_emmc_firehose_8937_ddr.
I can enter EDL mode easily now with the patched fastboot exe. The correct driver is active and QFIL detects the phone. However, as soon as I follow the instructions by setting the programmer, and then try to start the partition manager, the phone stops responding.
After a while, I get a "sahara" error about no reply from the phone.
I wonder if someone has a stock boot.img of the Nokia 3.2 (build 00EEA) lying around ...
Here is someone else's photo of the mainboard (I just realized that it's actually from hikari_calyx!) but on mine, the right one of the test points you marked in your 3.2 variant does not exist, so I edited it out in the photo:
{
"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"
}
JFDee said:
Anyway, now I'm unlocked but can't access the partitions with the QFIL partition manager. I suspect the phone expects a different programmer than prog_emmc_firehose_8937_ddr.
Click to expand...
Click to collapse
My guess was right. Now I'm able to reply to myself with a solution.
I tried a different prog_emmc_firehose_8937_ddr than the one provided by @hikari_calyx in the unlock thread
There is a programmer with the same name in this firmware:
sprout-015B-0-00WW-B01 .rar
It's provided by @bouyhy01 in his rooting thread.
The size of the programmer file is slightly different:
Code:
hikari_calyx: 428,936 bytes
Firmware: 428,944 bytes
Long story short: the different programmer worked in QFIL, so the partition manager worked as well, I got my own boot image, patched, flashed and had root - finally ... Thanks for all the research work, hikari_calyx and bouyhy01 !
Attached is the working programmer file, in case anyone else stumbles upon the same problem. By the way, my phone has the October security patch installed which is currently the latest available.
View attachment prog_emmc_firehose_8937_ddr_from_fw.zip
.
JFDee said:
Here is someone else's photo of the mainboard (I just realized that it's actually from hikari_calyx!) but on mine, the right one of the test points you marked in your 3.2 variant does not exist, so I edited it out in the photo:
View attachment 4867461
Click to expand...
Click to collapse
I guess the only point can be connected to the ground, for example, the RF shield is grounded.
JFDee said:
Attached is the working programmer file, in case anyone else stumbles upon the same problem. By the way, my phone has the October security patch installed which is currently the latest available.
View attachment 4869373
.
Click to expand...
Click to collapse
Thanks for info. Mine Nokia 3.2 is a prototype unit, so I don't know the situation of other versions of Nokia 3.2.
Hello, I have tried this manual for rooting Nokia 4.2 with last security update of 5th of November. After 5 step (flashing patched boot image) my phone try to reboot and then asked for factory reset (Can't load android system - Your data may be corrupt). After making factory reset there were no root at all.
What can i do next ?
PS. It's strange enough when i download boot_b image it was 63.4 Mb snd when i have patched it by Magisk manager - the size od magisk_patched.img became 10.2 Mb
{
"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"
}
Note - Iam Not Responsible for bricked devices
Disclaimer
This is specially designed for Nokia 6.1 . With the help of this tool we can flash any stock home brew Roms and the links will be attached below .
How to use this?
Note - Make sure your phone bootloader is unlocked
1. Download Nokia-SDM660-Tool.zip & Copy Nokia-Tool.exe
2. Download latest HOME BREW Stock Rom And extract in one Folder and name it as STOCK ROM
3. Now add Nokia-Tool.exe in to that respective STOCK ROM Folder
4. Now connect phone to pc
5. Go to download mode
6. Now Open Nokia-Tool.exe
7. Now select Button according to your Phone code
8. Example Iam Using Nokia 6.1 Plus & My phone code DRG & so i will choose [ DRG B2N CTL PL2 ] same option for 6.1 , 7.1 & 7+ but for 7.2 & 6.2 users choose [DDV SLD]
9. i will click on [ DRG B2N CTL PL2} According to my phone as i explained in point no.8
10. wait for 10 min Tool will flash the rom & your phone reboots to system.
11. So finally this is what the exact standard method to flash stock rom on Your devices
Download Tool
Download stock roms
Credits
Massive thank you for hikari_calyx ( Without him and his support during hmd journey iam nothing )
&
My entire Nokia 6.1 community Thank you all for your massive support Again
XDA:DevDB Information
Stock-Rom Flash Tool Nokia 6.1
Contributors
Raghu varma , hikari_calyx
Source Code:
https://github.com/RaghuVarma331/Nokia-Tool.git
Version Information
Status: Stable
Current Stable Version: 1.5
Stable Release Date 2019-12-23
Created 2019-12-23
Last Updated 2020-04-07
Now Some common Questions
Q1. we still receive monthly updates?
A. obviously you will receive updates as like before
Q2. Can we try this on Locked Bootloader?
A. No
Q3. Can we use this without Adb Tools?
A. No
Q4. Can we use this tool on any Android version?
A. Yes works On Oreo , pie & Q but keep this point in your mind update your platform tools time to time due to For Q & Pie & Oreo all these 3 having different different platform tools so if you face any erros don't get scared just download latest adb platform tools
Raghu varma said:
Now Some common Questions
Q1. we still receive monthly updates?
A. obviously you will receive updates as like before
Q2. Can we try this on Locked Bootloader?
A. No
Q3. Can we use this without Adb Tools?
A. No
Q4. Can we use this tool on any Android version?
A. Yes works On Oreo , pie & Q but keep this point in your mind update your platform tools time to time due to For Q & Pie & Oreo all these 3 having different different platform tools so if you face any erros don't get scared just download latest adb platform tools
Click to expand...
Click to collapse
as of now i cnt find a way how to unlock my nokia 6.1 2018 boatloader ...plsss share how you unlock your nokia 6.1 plssss
Please guide me, how to unlock Nokia 6.1 (2018) TA-1043.
zkengz said:
Please guide me, how to unlock Nokia 6.1 (2018) TA-1043.
Click to expand...
Click to collapse
we have the same device
MOD EDIT: Do NOT quote full OP.
Did everything as mentioned but nothing happened, my phone restarted to old OS only...
shad.man92 said:
Did everything as mentioned but nothing happened, my phone restarted to old OS only...
Click to expand...
Click to collapse
Download the correct zip and extract in ur folder where all ADB and fastboot files are present.
Then use Nokia tool from same folder and tap on pl2410c box and let it flash.
Milind Goel said:
Download the correct zip and extract in ur folder where all ADB and fastboot files are present.
Then use Nokia tool from same folder and tap on pl2410c box and let it flash.
Click to expand...
Click to collapse
This is correct ss. Lul i selected wrong ss first
Dear all,
I have to remove some posts due to insulting language. Please do follow our rules when you post and respect all users on XDA. Thank you.
Rule refresher:
2. Member conduct. 2.1 Language: XDA is a worldwide community. As a result, what may be OK to say in your part of the world, may not be OK elsewhere. Please don't direct profanity, sexually explicit language or other offensive content toward Members or their work. Conversely, while reading posts from other members, remember that the word you find offensive may not be offensive to the writer. Tolerance is a two-way street.
2.2 Nudity: XDA is used by people of all ages, including minors. It is unacceptable to post nude or pornographic imagery, which includes the exposure of male or female genitalia and / or female breasts.
2.3 Flaming / Lack of respect: XDA is about sharing and this does not involve virtual yelling (flaming) or rudeness. Flaming or posting with a lack of respect is unacceptable. Treat new members in the manner in which you would like to have been treated when you were a new member. When dealing with any member, provide them with guidance, advice and instructions when you can, showing them respect and courtesy. Never post in a demanding, argumentative, disrespectful or self-righteous manner.
2.4 Personal attacks, racial, political and / or religious discussions: XDA is a discussion forum about certain mobile phones. Mobile phones are not racial, political, religious or personally offensive and therefore, none of these types of discussions are permitted on XDA.
2.5 All members are expected to read and adhere to the XDA rules.
Windows block it saying it contain a virus Trojan:Win32/Emali.A!cl
Magister54 said:
Windows block it saying it contain a virus Trojan:Win32/Emali.A!cl
Click to expand...
Click to collapse
Well iam using windows 10 with windows 10 defender protection on nothing issues with my pc more over the exe tool file was compiled under visual studio with proper license so nothing to worry just avoid. If you want
any chance 6.1 rom will work on TA-1041 (C1N) just as is (without modifications)?
i`ve flashed Android 10.0.0 PL2410C HOME BREW on my Nokia 6.1 with unlocked bootloader, but now I cannot even boot using fastboot in TWRP, I even tried UNOFFICIAL TWRP 3.4.0-0 by Raghu and it hangs on Android One, am I doing something wrong?
carbpm said:
i`ve flashed Android 10.0.0 PL2410C HOME BREW on my Nokia 6.1 with unlocked bootloader, but now I cannot even boot using fastboot in TWRP, I even tried UNOFFICIAL TWRP 3.4.0-0 by Raghu and it hangs on Android One, am I doing something wrong?
Click to expand...
Click to collapse
How did you unlock your Nokia 6.1? Please share
XRT10 said:
How did you unlock your Nokia 6.1? Please share
Click to expand...
Click to collapse
check your messages. for anyone else reading this: it is a paid service costing anywhere between ~$7 and $10 USD. the one I used is on techmesto. if you want to do this for free, you need to decrypt the unlock key algorithm yourself or something.
carbpm said:
i`ve flashed Android 10.0.0 PL2410C HOME BREW on my Nokia 6.1 with unlocked bootloader, but now I cannot even boot using fastboot in TWRP, I even tried UNOFFICIAL TWRP 3.4.0-0 by Raghu and it hangs on Android One, am I doing something wrong?
Click to expand...
Click to collapse
have you tried the following in fastboot:
fastboot flash recovery twrp.img
(it will throw an error about a/b partitions)
fastboot boot twrp.img
if you are unable to get to fastboot/download mode then don't freak out! i had accidentally bricked my phone, but there was a fix for me. in the terminal, type
fastboot reboot-bootloader
then you plug your phone in, and it should hopefully take you from recovery to download mode (if you were stuck in recovery that was bootlooping)
3Dota said:
any chance 6.1 rom will work on TA-1041 (C1N) just as is (without modifications)?
Click to expand...
Click to collapse
i doubt it. the image files need to be signed by nokia i believe. you need an unlocked bootloader to bypass that restriction
{
"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"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Supported Models:
Galaxy A02s A025F, A025M and A025G.
Download & Guide:
1. Unlock your bootloader.
2. Download Galaxy A02s : a02q.
3. Reboot to download mode and flash vbmeta_disabled.tar in AP slot and reboot. Device will reboot to stock recovery mode prompting you to wipe data so wipe data and reboot to download mode again.
4. Put the TWRP tar for your device with Odin in the AP slot and click start.
5. Reboot to recovery via recovery key combo.
6. Disable encryption:
- Go to Advanced > Terminal, type: multidisabler.If vendor complain about free space left on device, will attempt to resize vendor. and it ask to - Run multidisabler again!.- Type: multidisabler again. will see - Finished. when done.7. Go back to Wipe > Format Data > type yes.
8. Reboot to recovery.
9. Flash magisk apk in twrp.
10. Reboot to system, Enjoy.
Note:
To disable encryption manually:
You need to replace fileencryption=ice with encryptable=ice only in userdata line (maybe rest lines) in vendor/etc/fstab.qcom
To avoid stock recovery restoration manually:
Rename system/recovery-from-boot.p to recovery-from-boot.p.bak
Click to expand...
Click to collapse
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram:
Link
Bugs:
- Encryption not fully working.
Thanks:
TWRP team
@jesec for unlock guide
@ianmacd for multidisabler
@CFKod & @Topser99 for testing
Sources:
Kernel tree
Device tree
Changelog:
29.11.2021 - Update to TWRP 3.6.0
- Add Symlinked dynamic partitions to fstab
- Update multidisabler
- fstab clean up
20.06.2021 - Initial Release.
Works perfectly. Thanks man.
Hello
Is it possible to build a kernel on a Samsung Galaxy A02S with mode SElinux permissive ?
Stalkerkhandoga said:
Hello
Is it possible to build a kernel on a Samsung Galaxy A02S with mode SElinux permissive ?
Click to expand...
Click to collapse
yes, my kernel source is there you can build it.
Tethank you friend.amazing
50Jaybla said:
Did you hack me
Click to expand...
Click to collapse
?
Hello
I disabled the bootloader and AVB. I installed TWRP with the Odin program. Although PASS appears, the stock recovery menu appears instead of the TWRP menu. What is the reason for this?
alemir25 said:
Hello
I disabled the bootloader and AVB. I installed TWRP with the Odin program. Although PASS appears, the stock recovery menu appears instead of the TWRP menu. What is the reason for this?
Click to expand...
Click to collapse
Need to be quick to enter twrp
Has anyone tried this on the sm-a025u unlocked variant? I'm about to get one of those phones and I will try this. I will report back on what happens.
hi. i want to configure your kernel for nethunter support. how can i do that?
thebestofall007 said:
Has anyone tried this on the sm-a025u unlocked variant? I'm about to get one of those phones and I will try this. I will report back on what happens.
Click to expand...
Click to collapse
If you can unlock bootloader why not, but device is lunched with march security update and my unlock service most likely wont work.
afaneh92 said:
If you can unlock bootloader why not, but device is lunched with march security update and my unlock service most likely wont work.
Click to expand...
Click to collapse
If I can unlock the bootloader by going into the developer options and turn on the "oem unlocking" option and then go to the download mode and hold down power+Vol down for 2 secs to enable the unlock option like I have read in the tutorials, that would be swell. I recently returned an sm-a025v verizon variant to Walmart that didn't have that option due to verizon locking the bootloader.
When you mention unlock service, what do you mean and what part of the tutorial do we do that?
thebestofall007 said:
If I can unlock the bootloader by going into the developer options and turn on the "oem unlocking" option and then go to the download mode and hold down power+Vol down for 2 secs to enable the unlock option like I have read in the tutorials, that would be swell. I recently returned an sm-a025v verizon variant to Walmart that didn't have that option due to verizon locking the bootloader.
When you mention unlock service, what do you mean and what part of the tutorial do we do that?
Click to expand...
Click to collapse
Yes if you can do that. But you cant on US devices.
[Android][UNSAMLOCK] Bootloader Unlock for Samsung US/Canada Devices
This thread is @svetius approved Important notice: Do not update to April 2023 security update (XXXXXXXXXXWCX) or later. Examples: G998USQS6EWCA, N986USQU4HWD1. Samsung has patched the bootloader unlock again on those updates. NOTE: The OneUI...
forum.xda-developers.com
Unfortunately it's a US model as afaneh92 said. I returned it and got me a Motorola Moto G power 2021 instead that does have an unlockable bootloader. I wanted to get the models named in this tutorial or an international variant, but there are none that I could find that support CDMA networks like Verizon, which I'm using.
thebestofall007 said:
Unfortunately it's a US model as afaneh92 said. I returned it and got me a Motorola Moto G power 2021 instead that does have an unlockable bootloader. I wanted to get the models named in this tutorial or an international variant, but there are none that I could find that support CDMA networks like Verizon, which I'm using.
Click to expand...
Click to collapse
Currently we can unlock any US device with February security update or older, your device shipped with march security update.
Does anyone know if this method works on the sm-a025m version?
thanks
cater2 said:
Does anyone know if this method works on the sm-a025m version?
thanks
Click to expand...
Click to collapse
Yes, read OP next time.
I managed to root my galaxy A02S . To my surprise, once everything was set up, I didn't have to do anything to pass on SafetyNet. Why ?
Another question is , if I want to go back to stock , would the steps I have to follow be these ?
1) Uninstall Magisk from the app?
2)Then enter Download mode and flash a stock rom ?
Or am I mistaken?
thanks
=====================
solved
Just boot to download mode and flash stock firmware with Odin .
After flashingis done , relock the bootloader...
cater2 said:
I managed to root my galaxy A02S . To my surprise, once everything was set up, I didn't have to do anything to pass on SafetyNet. Why ?
Another question is , if I want to go back to stock , would the steps I have to follow be these ?
1) Uninstall Magisk from the app?
2)Then enter Download mode and flash a stock rom ?
Or am I mistaken?
thanks
Click to expand...
Click to collapse
solved
Just boot to download mode and flash stock firmware with Odin .
After flashingis done , relock the bootloader...
I am perfom this Sorry for my english, I am from Ukraine
Download archive!
We unpack. Install the adb and mtk preloader drivers, if they are not installed, restart the computer.
In the smart, turn on the developers menu, in it - "Allow OEM unlock" and "USB debugging" and connect the smart to the computer.
We drop valuable photo data from the smart to the computer for any, and, without disconnecting the smart from the PC, run the script (with the phone connected to the PC and loaded into the android phone. Reboot_to_fastboot_getvar current-slot.bat (not from the admin, just click twice).
Smart will look like this:
{
"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"
}
we allow - put a daw, ok. We are waiting for the smart to reboot into fastboot, when the barcode appears on the smart screen, before that we do not press anything in the script
I did the scripts step by step, after each operation in the script window, press enter to continue, and so on until each script is closed
We look at our current slot in the window and remember the letter - a or b:
In the script, press enter so that the smart reboots and the script closes.
Run flash_tool.exe, go to this tab and check the boxes, as in the screenshot:
So we consider the necessary versions of orig. files, so as not to download and sew a specific firmware version for this instruction.
(And best of all, all the checkboxes, except for system, vendor, userdata - they are not critical, if they are not removed, it will take up a lot of space on the computer up to +74 gb, but I did not put these checkboxes, there must be some risk and passion )
We press "Read Back" and only then we connect the switched off smart to the PC, we wait, at the end we disconnect the bodies, do not touch it: sveta:
Go to this tab, remove all checkboxes! And we only put on lk_ with the letter of a non-your slot that we looked at, for example, you had slot "a" - so we put a check on lk_b and vice versa :
Click "Download" and connect the switched off smart to the PC (it was already turned off: sveta
As it flashes, we close the USB flash drive window, disconnect and turn on the smart, after loading, we connect it to the PC again, we already run the script
Unlock_Moto_E6S.bat, wait until the body reboots into a fastboot (to the barcode on the screen) and only then press the input step by step to continue in the script until it is completely closed.
Everything, the bodies are unlocked. Now you can get an excellent and fast root from Magisk, try other firmware, unsubscribe which one is buggy, which one flies. I haven't tried yet. Now I will write how to flash orig. kernel with magisk root (attached magisk boot for xt2053-1 4/64 fw RETEU 288-60-6-29 https://mirrors.lolinet.com/firmware/moto/fiji/official/RETEU/
Additionally, there is a script in the folder to delete the message when loading that the bootloader is unlocked, it does not interfere much, but I deleted it. Since this is not important, I separated it from the main script, since I did not test it on different versions of the firmware, in theory it should work on all versions, you can try after unlock. Or throw off ROM_45 from your firmware, I'll remove it from it. I now have the latest firmware flashed, it is on the server, but for some reason it did not fly through the air. If you flash it, then you can safely delete the message from the bootloader with my script, there is a file from it)
I am flash in slot_b Android 12 GSI, work. And i have in slot_a original system
severagent007 said:
I am flash in slot_b Android 12 GSI, work. And i have in slot_a original system
Click to expand...
Click to collapse
dude!! followed all your steps and i now have a bootloader unlocked and rooted device. how did you figure out the lk and signature to unlock that??
proof attached below
Слава Украине!!!
can the mods move this to the moto e6s forum so we can spread the news?
luridphantom said:
can the mods move this to the moto e6s forum so we can spread the news?
Click to expand...
Click to collapse
I took the first firmware I got to try from here: https://4pda.to/forum/index.php?showtopic=892755
but the firmware itself is everywhere, for example here:
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
DeveloperLuke Roms - Browse /GSIs at SourceForge.net
sourceforge.net
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
You can try to sew any GSI arm64 a/b from anywhere you find and choose the one you like, because smart supports Project Treble.
If you like one and will look cool and work firmware, post links here!
Tested it and it worked! Thanks a lot!
Now looking for delevoping some roms to this device
Im having a little problem, i tried to flash a GSI with "fastboot -u flash system gsi.img", the device didn't boot. Then i tried to flash the stock with the SP Flash Tool, and i throws an error (status_sec_dl_ forbidden), then i flashed it with Lenovo Rescue and Smart Assistant. I tried to flash via fastboot the patched magisk image but it throws an signature error.
Any help? Tha device still says that is unlocked
refrigerador67 said:
Im having a little problem, i tried to flash a GSI with "fastboot -u flash system gsi.img", the device didn't boot. Then i tried to flash the stock with the SP Flash Tool, and i throws an error (status_sec_dl_ forbidden), then i flashed it with Lenovo Rescue and Smart Assistant. I tried to flash via fastboot the patched magisk image but it throws an signature error.
Any help? Tha device still says that is unlocked
Click to expand...
Click to collapse
did you use the auth file that comes with sp flash tool? without that your device wont boot properly
Yes, i used the correct download agent and auth file
interesting, i followed all his steps and had no problem rooting it. try backtracking with his scripts again?
Solved it, also me and a developer are working on a new, more simple and automated script. Still haven't figured out how to flash the lk via script.
When is done i will post a complete guide in the moto e6s forums on how to do it, i think it might work well, but i would have to test in a non-unlocked device
Can someone please make a video with explanation, I didn't understand very well what is done, so I won't touch anything, but I thank those who record a video explaining it to me (I'm Brazilian)
Here you have a more straight forward guide, note that is still in testing
[GUIDE] How to unlock bootloader on E6s
Hello, in this guide i will show you how to unlock the bootloader on Moto E6s ;) (Sadly for now this guide is Windows only) CAUTION You are doing this AT YOUR OWN RISK! I will NOT take responsibility if you brick your device! Also, remember to...
forum.xda-developers.com
Excuse my ignorance, do you think it is compatible for the XT2053-5 model?
cannot use fastboot flash boot magiskboot.img
sign failed
partition flash is not allowed
hey is the moto e6+ twrp work on e6s