looking for boot.img z5c compatible with 32.0.A.6.200_R4B - Xperia Z5 Compact Q&A, Help & Troubleshooting

Hi Guys,
I wanted to backup my TA partition on my z5c so I donwgraded using an Australian Stock ROM found in a step by step tutorial (32.0.A.6.200_R4B). So far so good, backup worked with ivoryroot. After unlocking the bootloader I wanted to flash twrp on the recovery partition. I porbably was not concentrated so I typed "fastboot flash boot ...." instead of "fastboot flash recovery .....". Is there anything to do about it or did I hard brick my device? Perhaps I could generate a boot.img out of the ftf file? but if yes how? Thanks for suggestions in advance.
Cheers
ncls
Edit: I managed to reflash the whole rom (which did not work yesterday) an got it to work - sorry for bothering you!

Related

[Q] Stuck on Sony Logo

So I thought of installing a new ROM to my XZU today. First I rooted my device using the following guide : https://www.youtube.com/watch?v=BkQT3nX5yWM. (As I had updated my device to Android 4.4.4 and had .108 FW). I successfully rooted the phone and took a TA Backup. Afterwards, I went on to unlock the bootloader and unlocked it successfully as well. As I wanted to install the ParanoidAndroid 4+ ROM, I downloaded it and got the boot.img from the ZIP file, and flashed it using the Flashtool. However, afterwards, when I tried to go the recovery mode, it is stuck on the Sony Logo, and doesn't blink the notification LED in order to do so.
Did I do anything wrong? I am quite a noob when it comes to XZU related stuff..so I would really appreciate if someone can help me out..
Thanks in advance!
EDIT: (Thought of editing this thread rather than deleting it so that it could be an help for someone who faces a similar problem) I was able to make my device up and running again by flashing the FTF found in this thread: http://forum.xda-developers.com/showthread.php?t=2798690.
Now, I have again come to the status where I have installed a recovery successfully and unlocked my bootloader, and I want to install PA 4+ to my device. Would really appreciate if anyone can guide me on how to do this
It doesn't sound like you did any thing wrong.
Do you have [NUT]'s recovery installed now?
Do a nandroid backup if you do, saves the whole flashing a FTF step if something goes wrong
Did you get the correct PA? what date?
PA should install fron [NUT]'s recovery or you could hotboot the boot.img with flashtool (this wont over write you current kernel) this will let you test if it does work
blueether said:
It doesn't sound like you did any thing wrong.
Do you have [NUT]'s recovery installed now?
Do a nandroid backup if you do, saves the whole flashing a FTF step if something goes wrong
Did you get the correct PA? what date?
PA should install fron [NUT]'s recovery or you could hotboot the boot.img with flashtool (this wont over write you current kernel) this will let you test if it does work
Click to expand...
Click to collapse
Thank you. Yes, I read quite a lot yesterday and found out that I have followed the steps properly. So I am wondering if it has got anything to do with the boot.img from the PA ROM?
And yes I did a nandroid backup previously as well, however, I was not aware of how to restore it because I couldn't access the recovery mode. Can I do the restore using the FlashTool? or some other tool in such a scenario?
I downloaded "pa_togari-4.5-BETA1-20140805.zip" available in this link: http://aospal.hostingsharedbox.com/aospal/roms/togari/ . Should I try the last stable release rather than the beta one?
I am sorry for this noobish question, but what exactly is the purpose of "boot.img"? Is it the kernel of the new ROM that I am going to install? or is it something else? I kinda think that the problem might have been with the way I flashed the boot.img previously. I used the option "SELECT SYSTEM TO FLASH" under the fastboot of FlashTool in order to do so. Is it wrong? Should I use the "SELECT KERNEL TO FLASH"?
Thank you again
EDIT: I used the "SELECT KERNEL TO FLASH" option in the Flashtool, to flash the boot.img and I was able to flash the PA 4+ successfully! ..Thank you!
Prabash said:
EDIT: I used the "SELECT KERNEL TO FLASH" option in the Flashtool, to flash the boot.img and I was able to flash the PA 4+ successfully! ..Thank you!
Click to expand...
Click to collapse
Good to hear you got it sorted, but I'll run through what you did wrong...
Thank you. Yes, I read quite a lot yesterday and found out that I have followed the steps properly. So I am wondering if it has got anything to do with the boot.img from the PA ROM?
Click to expand...
Click to collapse
So you now know it wasn't the boot.img :laugh:
And yes I did a nandroid backup previously as well, however, I was not aware of how to restore it because I couldn't access the recovery mode. Can I do the restore using the FlashTool? or some other tool in such a scenario?
Click to expand...
Click to collapse
Normally the way to recover would be to flash a boot.img that works and then enter recovery rand restore, easy when you flash the boot.img correctly
I am sorry for this noobish question, but what exactly is the purpose of "boot.img"? Is it the kernel of the new ROM that I am going to install? or is it something else?
Click to expand...
Click to collapse
The boot image is the kernel and recovery backed into one (it's a Sony thing ) and it belongs on the /boot partition
I kinda think that the problem might have been with the way I flashed the boot.img previously. I used the option "SELECT SYSTEM TO FLASH" under the fastboot of FlashTool in order to do so. Is it wrong? Should I use the "SELECT KERNEL TO FLASH"?
Click to expand...
Click to collapse
I think you have figured that one out now :cyclops:. So what you did was write the kernel and recovery to the /system partition, not to where it belongs ie /boot
You can also use the "select kernel to boot (hotboot)" (or what ever words it uses) to boot a kernel/recovery and not change the one on the /boot partition - can be handy at times
I hope that helps you understand some bits about your new Sony ZU
Yep! thanks a lot for your help! Really appreciate it! :victory:

[Q] A small question about flashing cm 12

Hi, everyone, I just got my z3 tablet and I am in love with it except i don't like the interface. So i decide to root my tablet without unlocking the bolted and I did made it and i did install TWRP. I have a question, since I have TWRP is it possible for me to install cm 12 rom or I need to have a unlock boot loader in order to install it?
Sorry for my bad english and thank you for answering my questions.
kokorolove said:
Hi, everyone, I just got my z3 tablet and I am in love with it except i don't like the interface. So i decide to root my tablet without unlocking the bolted and I did made it and i did install TWRP. I have a question, since I have TWRP is it possible for me to install cm 12 rom or I need to have a unlock boot loader in order to install it?
Sorry for my bad english and thank you for answering my questions.
Click to expand...
Click to collapse
You need to unlock to flash a custom kernel which would be needed by the cm12 to run. So first.
1.Backup drm keys
2.Unlock BL
3. Flash CM kernel via fastboot
4. Flash CM Rom via recovery.
Sent from my SGP621 using XDA Free mobile app
I just bought a Z3 tablet compact, which should be here at the end of next week. I haven’t found a tutorial which includes all steps to get from the standard rom to CM12. Did I miss any steps or does the following steps include everything?
Root tablet on the original Sony rom
Backup TA partition (I guess that's where the DRM keys are?)
Unlock bootloader
Flash a recovery (any recommendations?) I found this tutorial, but I only need one recovery and I don’t want to flash that zip every time I install a new rom.
Flash CM12. Are there any kernels beside that one included in the CM12 zips?
Cyberratchet said:
I just bought a Z3 tablet compact, which should be here at the end of next week. I haven’t found a tutorial which includes all steps to get from the standard rom to CM12. Did I miss any steps or does the following steps include everything?
Root tablet on the original Sony rom
Backup TA partition (I guess that's where the DRM keys are?)
Unlock bootloader
Flash a recovery (any recommendations?) I found this tutorial, but I only need one recovery and I don’t want to flash that zip every time I install a new rom.
Flash CM12. Are there any kernels beside that one included in the CM12 zips?
Click to expand...
Click to collapse
I guess you should just flash the kernel via fastboot after unlocking the bootloader, that would eliminate the need to flash a recovery. It's hitting 2 birds and one stone and besides CM uses a different kernel than stock so later you would really need to flash kernel.
Sent from my SGP621 using XDA Free mobile app
Thanks for your reply. The whole flashing procedure is a lot more complicated than on my S3, so I have a follow-up question.
Should I just backup the TA partition, unlock the tablet, flash this kernel which should give me root and TWRP and then flash another recovery and CM12?
I found this recovery which is only semi-permanent, because you have to flash it before you upgrade/install a new CM12 version. It’s not big deal tbh, but is there a permanent recovery, which I only have to install once.
I'm also curious about this.
Right now, I'm trying to download the Flashtool program from Sony, but apparently, you need to "register" for it. Where did you guys download your Flashtool from?
Cyberratchet said:
Thanks for your reply. The whole flashing procedure is a lot more complicated than on my S3, so I have a follow-up question.
Should I just backup the TA partition, unlock the tablet, flash this kernel which should give me root and TWRP and then flash another recovery and CM12?
I found this recovery which is only semi-permanent, because you have to flash it before you upgrade/install a new CM12 version. It’s not big deal tbh, but is there a permanent recovery, which I only have to install once.
Click to expand...
Click to collapse
Correct, make sure the kernel is compatible with CM
Sent from my SGP621 using XDA Free mobile app
The whole procedure is really frustrating, maybe someone can help me here.
I did a backup of the TA partition and unlocked the bootloader. I tried flashing the boot.img from the cm.zip, but I have no idea how to flash the rom via the cm-recovery.
Flashing the advanced kernel to get TWRP wasn’t successful as well. I tried the fastboot mode of the Flashtool and flashed the kernel, but nothing changed.
Can someone post a brief guide with the next steps to get CM12 running (with cmd commands pls)?
EDIT: I just tried to use “adb sideload” in the CM recover, but “adb devices” doesn’t show the tablet .
EDIT2: EDIT: Seems like I got it to work after all. The DualRecover Installer worked, even without SuperSU installed.
Cyberratchet said:
The whole procedure is really frustrating, maybe someone can help me here.
I did a backup of the TA partition and unlocked the bootloader. I tried flashing the boot.img from the cm.zip, but I have no idea how to flash the rom via the cm-recovery.
Flashing the advanced kernel to get TWRP wasn’t successful as well. I tried the fastboot mode of the Flashtool and flashed the kernel, but nothing changed.
Can someone post a brief guide with the next steps to get CM12 running (with cmd commands pls)?
EDIT: I just tried to use “adb sideload” in the CM recover, but “adb devices” doesn’t show the tablet .
EDIT2: EDIT: Seems like I got it to work after all. The DualRecover Installer worked, even without SuperSU installed.
Click to expand...
Click to collapse
I ran into the same problem usin the cm12 nightlies from 27th march 2015:
Sideloading would not work because the tablet is not recognized by the computer. I tried with Windows 7 and gentoo Linux.
Installing from the sd-card in recovery mode was also not possible due to a error of missing "/misc".
I solved the problem by manually choosing the driver in Windows 7. I booted the tablet into recovery. Choose update using adb as detailed in this post:
http://forum.xda-developers.com/z3-...t/root-root-locked-bootloader-sgp621-t3013534
Then I found the device in the windows device manager. Here I manually choose the adb driver that I installed earlier from the flashtool package. After that the device was correctly recognized by Windows and I could Sideloade the cm12 image.

[Q] Root Xperia with Lollipop?

Hi, I'm kind of a noob, so sorry if this is a dumb question.
I just installed the new Lollipop Fimware on my Z2, using Flashtool. Now I want to root the device, but reading through articles on XDA or XperiaBlog, they all said you need to use older firmware. So my question is, can you root the Z2 with Lollipop?
I'd be grateful for helpful answers.
ICripzHD said:
Hi, I'm kind of a noob, so sorry if this is a dumb question.
I just installed the new Lollipop Fimware on my Z2, using Flashtool. Now I want to root the device, but reading through articles on XDA or XperiaBlog, they all said you need to use older firmware. So my question is, can you root the Z2 with Lollipop?
I'd be grateful for helpful answers.
Click to expand...
Click to collapse
Things needed:
PC, fastboot driver, know how to boot to bootloader(fastboot mode) and recovery mode
Now you can without having old kernel (not firmware)
go to http://forum.xda-developers.com/xperia-z2/development/kernel-andropluskernel-v10-t2974841 extract boot.img from the zip file.
Boot your phone to fastboot mode and in command:
Code:
fastboot flash boot boot.img
Go to recovery mode after restarting and then get UPDATE-SuperSU-v2.46.zip and flash it via newly installed TWRP recovery.
themightydeity said:
Things needed:
PC, fastboot driver, know how to boot to bootloader(fastboot mode) and recovery mode
Now you can without having old kernel (not firmware)
go to http://forum.xda-developers.com/xperia-z2/development/kernel-andropluskernel-v10-t2974841 extract boot.img from the zip file.
Boot your phone to fastboot mode and in command:
Code:
fastboot flash boot boot.img
Go to recovery mode after restarting and then get UPDATE-SuperSU-v2.46.zip and flash it via newly installed TWRP recovery.
Click to expand...
Click to collapse
And for locked bootloaders it is a different story
HellRoot said:
And for locked bootloaders it is a different story
Click to expand...
Click to collapse
Yep totally different story.
So there's no way yet for locked bootloaders?
themightydeity said:
Things needed:
PC, fastboot driver, know how to boot to bootloader(fastboot mode) and recovery mode
Now you can without having old kernel (not firmware)
go to http://forum.xda-developers.com/xperia-z2/development/kernel-andropluskernel-v10-t2974841 extract boot.img from the zip file.
Boot your phone to fastboot mode and in command (how ?) :
Code:
fastboot flash boot boot.img
Go to recovery (how? which recovery ? there is one installed by default?) mode after restarting and then get UPDATE-SuperSU-v2.46.zip and flash it via newly installed TWRP recovery (what ?).
Click to expand...
Click to collapse
Thats a terribly bad answer right ? I've rooted another devices but but can't undestand almost a thing of the process you just posted.
Imagine for the noob dude ?
zeehkaev said:
Thats a terribly bad answer right ? I've rooted another devices but but can't undestand almost a thing of the process you just posted.
Imagine for the noob dude ?
Click to expand...
Click to collapse
Same here. I'm a noob wanting to learn how to root. But this went over my head :/
Would using PRF creator work? If you bundled the lollipop firmware with supersu.zip and flashed it would it give you lolipop with root? Because this is what i did to update to 4.4.4 with root. For anyone that doesnt know PRF creator is a program which combines 3 files which is are firmware of your choice, a superSU.zip and a recovery.zip. It combines them into a .zip that you can flash in recovery and have the firmware with superSU and a custom recovery on it.
I have a locked bootloader and mines rooted, do you want me to say how?
If its on lollipop, i would very much like to know how.
Isn't this the exact same answer as rooting 4.4.4?
Downgrade to 4.4.2
Root
Install recovery
Install rooted lollipop zip in recovery
If you don't understand this or the method posted above don't root. Also, if.you can't google things like fastboot to understand what it is don't root.
K-NineHD said:
I have a locked bootloader and mines rooted, do you want me to say how?
Click to expand...
Click to collapse
it would be kindly appreciated!
Bootloop
Everything was fine, till i tried superSU. Twrp flashed it fine, but then when i tried to reboot, the device got stuck in a bootloop.
wipe cache/delvik also didnt help.
I have a new z2, then unlocked the bootloader, and then got the Norway rom using xperifirm.
Norway rom installed fine. twrp installed fine. But i am facing a bootloop now that i have flashed UPDATE-SuperSU-v2.46.zip
Anybody else face this issue?
0charbless said:
Everything was fine, till i tried superSU. Twrp flashed it fine, but then when i tried to reboot, the device got stuck in a bootloop.
wipe cache/delvik also didnt help.
I have a new z2, then unlocked the bootloader, and then got the Norway rom using xperifirm.
Norway rom installed fine. twrp installed fine. But i am facing a bootloop now that i have flashed UPDATE-SuperSU-v2.46.zip
Anybody else face this issue?
Click to expand...
Click to collapse
try wiping just "Dalvik Cache" and restart again. I have also face similar strange issue when I was using FlashTool a couple of times.
If that doesn't work try normal wiping from TWRP and install firmware using FlashTool.
themightydeity said:
try wiping just "Dalvik Cache" and restart again. I have also face similar strange issue when I was using FlashTool a couple of times.
If that doesn't work try normal wiping from TWRP and install firmware using FlashTool.
Click to expand...
Click to collapse
Thanks. I tired wiping , but it didnt work.
I just reflashed with 17.x firmware, and upgraded using the rooted rom "D6503_Customized BAL_1282-0827_23.1.A.0.690_R3C_SuperSU_XZDR2.8.3"
ICripzHD said:
Hi, I'm kind of a noob, so sorry if this is a dumb question.
I just installed the new Lollipop Fimware on my Z2, using Flashtool. Now I want to root the device, but reading through articles on XDA or XperiaBlog, they all said you need to use older firmware. So my question is, can you root the Z2 with Lollipop?
I'd be grateful for helpful answers.
Click to expand...
Click to collapse
Hi,
FIRST: you need to downgrade your phone
http://forum.xda-developers.com/showthread.php?t=2759934
Flash it using FLASHTOOL
SECOND: Root your phone
http://forum.xda-developers.com/showthread.php?t=2783750
THIRD: Install Recovery for flashing zip ROMs
http://forum.xda-developers.com/showthread.php?t=2785598
FOURTH: Use this to flash Lollipop
http://forum.xda-developers.com/xperia-z2/development/stock-d6503-23-1-0-690-bal-rooted-t3057150
Just make sure you follow all the steps and you're good.
[CREDITS]
Credits goes to all OP of the Threads
Please press THANKS if this helped you.
yavhin said:
Hi,
FIRST: you need to downgrade your phone
http://forum.xda-developers.com/showthread.php?t=2759934
Flash it using FLASHTOOL
SECOND: Root your phone
http://forum.xda-developers.com/showthread.php?t=2783750
THIRD: Install Recovery for flashing zip ROMs
http://forum.xda-developers.com/showthread.php?t=2785598
FOURTH: Use this to flash Lollipop
http://forum.xda-developers.com/xperia-z2/development/stock-d6503-23-1-0-690-bal-rooted-t3057150
Just make sure you follow all the steps and you're good.
[CREDITS]
Credits goes to all OP of the Threads
Please press THANKS if this helped you.
Click to expand...
Click to collapse
I'm no Android/Lollipop/Rooting expert but using an unlocked boot loader I was able to root Lollipop (23.1.A.0.690 ) easily using the kernel from:
http://forum.xda-developers.com/xpe...ot-stock-flashable-kernel-23-1-0-690-t3061816
My steps were:
1. Install Lollipop
2. fastboot flash boot boot.img (to install above mentioned kernel with TWRP recovery)
So far so good.
PS: To use fastboot you'll likely need the drivers from flashtool (http://www.flashtool.net/index.php) and if on Win 8.1 you'll need to search for instructions on how to install unsigned drivers.
ICripzHD said:
Hi, I'm kind of a noob, so sorry if this is a dumb question.
I just installed the new Lollipop Fimware on my Z2, using Flashtool. Now I want to root the device, but reading through articles on XDA or XperiaBlog, they all said you need to use older firmware. So my question is, can you root the Z2 with Lollipop?
I'd be grateful for helpful answers.
Click to expand...
Click to collapse
check out my tutorial if you need help https://www.youtube.com/watch?v=0msKcElz3Ow
tfcarlin said:
and if on Win 8.1 you'll need to search for instructions on how to install unsigned drivers.
Click to expand...
Click to collapse
If you're not on mobile, you can check out my signature to disable signed driver enforcement for windows 8 and 8.1. It sticks after reboots too.
yavhin said:
Hi,
FIRST: you need to downgrade your phone
http://forum.xda-developers.com/showthread.php?t=2759934
Flash it using FLASHTOOL
SECOND: Root your phone
http://forum.xda-developers.com/showthread.php?t=2783750
THIRD: Install Recovery for flashing zip ROMs
http://forum.xda-developers.com/showthread.php?t=2785598
FOURTH: Use this to flash Lollipop
http://forum.xda-developers.com/xperia-z2/development/stock-d6503-23-1-0-690-bal-rooted-t3057150
Just make sure you follow all the steps and you're good.
[CREDITS]
Credits goes to all OP of the Threads
Please press THANKS if this helped you.
Click to expand...
Click to collapse
Is there root only for Baltic ROM? I am on Nordic and I want root is that possible?

Nokia 1 TA-1056 ROM issue

Hello everyone, after a long attempt at unlocking the bootloader i finally got it, i flashed TWRP and got a prompt for encryption password, and my password wasn't working and i also tried default_password,so i read that the format data option will decrypt the phone and people said wouldn't do anything to system, so i did it and now everytime i reboot it boots straight into recovery no matter what i try, it will also boot into fastboot, so i tried to find a stock ROM for TA-1056 but couldn't find it anywhere, the only the i found was a single ROM for the TA-1060, can anyone help? i really appreciate it!
Completely Bricked
Me too need a stock rom of ta 1056. Please help if you could manage to provide a helping hand... ?
I had the same issue like yours, looping in twrp. then i tried to flash it with a so called stock rom from net, guess what it went completely bricked and I donnow what to do. ??
mrabudi said:
Hello everyone, after a long attempt at unlocking the bootloader i finally got it, i flashed TWRP and got a prompt for encryption password, and my password wasn't working and i also tried default_password,so i read that the format data option will decrypt the phone and people said wouldn't do anything to system, so i did it and now everytime i reboot it boots straight into recovery no matter what i try, it will also boot into fastboot, so i tried to find a stock ROM for TA-1056 but couldn't find it anywhere, the only the i found was a single ROM for the TA-1060, can anyone help? i really appreciate it!
Click to expand...
Click to collapse
It's simple. just get the stock recovery (and boot, optional) to flash it with fastboot and go to recovery and wipe it and you'll be ok.
and also using the twrp on this phone is not a great idea to wipe.
if you wanna wipe. please use "fastboot -w" to wipe the phone while bootloader is unlocked. or stock recovery to wipe.
Because twrp built this recovery with only formatting option was ext4 to /data and /cache. So the phone cannot operate properly. Which leads to fake failed decryption notification.
Data partition must need to be formatted under f2fs format.
And finding rom for this phone is pretty easy. Just find some nb0 file for this phone (any variant of this phone should work) and extract it with "nb0 extractor" and then flash it with SP Flash tool by mediatek.
That's my way. I don't know how will you do. But normally you only need the nb0 file and then flash it with OST LA (Nokia's flash tool based off Intel's SUT L1/L3 tool).
My Nokia 1 TA-1047 stuck at Nokia logo screen
Hi guys, sorry I'm newbie so after a long time surfing for solutions, I couldn't solve my own problem. That's why I come here to ask for your supports
Firstly I unlocked bootloader, installed TWRP and rooted my device and enjoyed it. But after decided to wipe (factory reset) this phone with TWRP, and my problem began...
1. I got stuck in TWRP loop booting. After that I tried to fastboot system.bin, cache.bin and recovery.bin from Stock Firmware but it still hung at Nokia logo booting
2. I still kept trying with SP Flash Tool, Miracle Box but there was still no hope:
- SP Flashtool v5_1548 gave me error: BROM ERROR: S_BROM_CMD_STARTCMD_FAIL (2005)
- Miracle Box 2.27A told me there was an error (i don't remember the code) occured in the location (i can't remember its code either)...
Anyone can solve it please help!!!! I love this phone much and as of now still suffering day by day since I can't do anything with it.
Kindly appreciate any suggestion and solution.
Thank you all!
cuantonhonhoi said:
Hi guys, sorry I'm newbie so after a long time surfing for solutions, I couldn't solve my own problem. That's why I come here to ask for your supports
Firstly I unlocked bootloader, installed TWRP and rooted my device and enjoyed it. But after decided to wipe (factory reset) this phone with TWRP, and my problem began...
1. I got stuck in TWRP loop booting. After that I tried to fastboot system.bin, cache.bin and recovery.bin from Stock Firmware but it still hung at Nokia logo booting
2. I still kept trying with SP Flash Tool, Miracle Box but there was still no hope:
- SP Flashtool v5_1548 gave me error: BROM ERROR: S_BROM_CMD_STARTCMD_FAIL (2005)
- Miracle Box 2.27A told me there was an error (i don't remember the code) occured in the location (i can't remember its code either)...
Anyone can solve it please help!!!! I love this phone much and as of now still suffering day by day since I can't do anything with it.
Kindly appreciate any suggestion and solution.
Thank you all!
Click to expand...
Click to collapse
So here's the thing. The rom you downloaded from internet (about 2 GB) or ripped from your phone and reflashing from flash tool will NOT WORK.
The first reason you can't flash the ROM was:
You got into flashing mode but you didn't do the right way so it failed the downloading DA for the phone. Try again and it should work (Don't go into fastboot mode)
2nd reason:
Because of the unsupported chip that MiracleBox read. It said the phone was 6573 or something while the phone chip is 6737M.
So the app will create the wrong version of the scatter for the phone. Leads to the flash tool app downloading the wrong command and Download Agent for the phone makes the phone can't be flashed.
You need to get the official nb0 file for this phone (TA-1060 or 66 should also works, mine was TA-1047. Since it's a universal ROM so any variant of the phone can also work) and then extract the ROM. Then you can get the scatter text file from that nb0 ROM and then flash it over flash tool (version 5 recommended, version 3 more likely not work).
Remember to look at line with partition "metadata" and then edit "boundary_check" to false.
PLUS:
If you flash it with your own dumped EMMC rom or flash it by dd-ing the partition in recovery will kinda work. But when you update the ROM over OTA (Google Play services's System Update app)
It will most likely bootlooped the phone when it's trying to verify the 2nd partition of the same recovery or kernel flashed into the phone (https://source.android.com/security/verifiedboot) and flash the updated one.)
So flashing from official ROM is mandatory.
And you can flash it over Intel's (Nokia modified) flash tool app SUTL3 (aka. OST LA) but I can't get it to work so you just stick with Flash Tool v5 from MediaTek and you'll be good.
Link:
The nb0 ROM (Security update around May 2018): https://drive.google.com/file/d/1XqwEAGG7GMaspzV2J_yzCxnRei8zsOJd/view
(Source: https://romprovider.com/2018/09/nokia-1-ta-1060-firmware/)
nb0 extractor, requires java installed (If extracting hurts your hard disk performance aka. frozen or lag. Don't worry, It actually works, DON'T DO ANYTHING. It will notify you once it's done.): https://forum.xda-developers.com/general/general/tool-unpack-repack-nb0-rom-t3495091
Smart Phone Flash Tool from MediaTek: https://spflashtools.com/
My fixed scatter file that actually works from nb0 file: https://drive.google.com/open?id=1gRoADGHBm4vIAw3NeDyc_h9QWj12XUrC
And don't use twrp for wiping the phone. Use "fastboot -w" to wipe or use stock recovery.
TWRP will wipe the data parition but in ext4 format and make the phone bootlooped. We need f2fs in order to make the phone's /data partition run correctly. (Unless you know how to make the phone not having encryption flag when booting up every first time. Or modify TWRP to wipe the /data partition with make_f2fs and not make_ext4 app. Or using make_f2fs in recovery to directly wipe /data partition over terminal, the actual partition is in /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/userdata.)
Or you just do this (I'm not tested it yet): Google "twrp f2fs format"
kutiz21 said:
So here's the thing. The rom you downloaded from internet (about 2 GB) or ripped from your phone and reflashing from flash tool will NOT WORK.
The first reason you can't flash the ROM was:
You got into flashing mode but you didn't do the right way so it failed the downloading DA for the phone. Try again and it should work (Don't go into fastboot mode)
2nd reason:
Because of the unsupported chip that MiracleBox read. It said the phone was 6573 or something while the phone chip is 6737M.
So the app will create the wrong version of the scatter for the phone. Leads to the flash tool app downloading the wrong command and Download Agent for the phone makes the phone can't be flashed.
You need to get the official nb0 file for this phone (TA-1060 or 66 should also works, mine was TA-1047) and then extract the ROM. Then you can get the scatter text file from that nb0 ROM and then flash it over flash tool (version 5 recommended, version 3 more likely not work).
Remember to hide/delete line with partition "metadata" in scatter.txt and you can flash it perfectly.
PLUS:
If you flash it with your own dumped EMMC rom or flash it by dd-ing the partition in recovery will kinda work. But when you update the ROM over OTA (Google Play services's System Update app)
It will most likely bootlooped the phone when it's trying to verify the 2nd partition of the same recovery or kernel flashed into the phone (https://source.android.com/security/verifiedboot) and flash the updated one.)
So flashing from official ROM is mandatory.
And you can flash it over Intel's (Nokia modified) flash tool app SUTL3 (aka. OST LA) but I can't get it to work so you just stick with Flash Tool v5 from MediaTek and you'll be good.
Link:
The nb0 ROM (Security update around May 2018): https://drive.google.com/file/d/1XqwEAGG7GMaspzV2J_yzCxnRei8zsOJd/view
(Source: https://romprovider.com/2018/09/nokia-1-ta-1060-firmware/)
nb0 extractor, requires java installed (If extracting hurts your hard disk performance aka. frozen or lag. Don't worry, It actually works, DON'T DO ANYTHING. It will notify you once it's done.): https://forum.xda-developers.com/general/general/tool-unpack-repack-nb0-rom-t3495091
Smart Phone Flash Tool from MediaTek: https://spflashtools.com/
My fixed scatter file that actually works from nb0 file: https://drive.google.com/open?id=1gRoADGHBm4vIAw3NeDyc_h9QWj12XUrC
And don't use twrp for wiping the phone. Use "fastboot -w" to wipe or use stock recovery.
TWRP will wipe the data parition but in ext4 format and make the phone bootlooped. We need f2fs in order to make the phone's /data partition run correctly. (Unless you know how to make the phone not having encryption flag when booting up every first time. Or modify TWRP to wipe the /data partition with make_f2fs and not make_ext4 app. Or using make_f2fs in recovery to directly wipe /data partition over terminal, the actual partition is in /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/userdata.)
Or you just do this (I'm not tested it yet): Google "twrp f2fs format"
Click to expand...
Click to collapse
Thanks for your comment. I have recently bought that version (TA-1047) and I see that is more complicated to root it securely than I thought… Your comment gave me hope to try it. So, could you please say me if it is posible to do it without breaking it? I will read your comment when I have more time but I thank you for it!
As I see there is only stock rom for TA-1060 version, but as you say it is posible to recover it in case of breaking it, isn't it?
Thanks. :fingers-crossed:
pabloluih said:
Thanks for your comment. I have recently bought that version (TA-1047) and I see that is more complicated to root it securely than I thought… Your comment gave me hope to try it. So, could you please say me if it is posible to do it without breaking it? I will read your comment when I have more time but I thank you for it!
As I see there is only stock rom for TA-1060 version, but as you say it is posible to recover it in case of breaking it, isn't it?
Thanks. :fingers-crossed:
Click to expand...
Click to collapse
It's really easy to root the phone actually. Just unlock bootloader, install twrp recovery and install magisk.
And if you broke the phone's ROM. Just bring it to Nokia. Or flash it by yourself with the ROM I linked above by SP Flash Tool software.
Anyway the ROM is universal. So any variant of the phone can be flashed. (Proves that the elabel partition has 5 certifications images for 5 different models)
Just take sometime and read my words there.
kutiz21 said:
It's really easy to root the phone actually. Just unlock bootloader, install twrp recovery and install magisk.
And if you broke the phone's ROM. Just bring it to Nokia. Or flash it by yourself with the ROM I linked above by SP Flash Tool software.
Anyway the ROM is universal. So any variant of the phone can be flashed. (Proves that the elabel partition has 5 certifications images for 5 different models)
Just take sometime and read my words there.
Click to expand...
Click to collapse
Many thanks! At the moment I achieved to root it with twrp. OEM unlock > installed twrp > fastboot -w > magisk.
At the moment all is okey but I have not been able to unencrypt DATA partition (I have done fastboot -w, but with no success, I have not tried TWRP format because of your advice). That's the only point I can complain about.
I hope I do not have to use the stock rom to unbrick, but I have your advice if I do.
Thanks again!
pabloluih said:
Many thanks! At the moment I achieved to root it with twrp. OEM unlock > installed twrp > fastboot -w > magisk.
At the moment all is okey but I have not been able to unencrypt DATA partition (I have done fastboot -w, but with no success, I have not tried TWRP format because of your advice). That's the only point I can complain about.
I hope I do not have to use the stock rom to unbrick, but I have your advice if I do.
Thanks again!
Click to expand...
Click to collapse
That's weird. If you unlocked the bootloader and install adb/fastboot (must be latest version. Older version will not recognize the phone, download platform-tools from google dev site, don't download adb tools off XDA) + Nokia's driver from emulated CD drive (every time you plug the phone to computer with official rom, you'll see it) properly then it should be able to work.
You need to check the fastboot device driver Device Manager (devmgmt.msc) and see if the driver is properly installed yet.
You can only use "fastboot -w" once the bootloader is unlocked. And booting up the phone. It will say the bootloader is in Orange state.
You need to unlock oem bootloader from developer settings when the stock rom is there. And in fastboot too
Here is how you unlock it:
Enable oem unlock from dev settings
Then reboot to fastboot mode (bootloader)
Do this:
"fastboot oem key "serial number string converted to md5, not imei strings" "
"fastboot oem unlock"
Volume up
Then you are actually unlocked the bootloader.
Unlock from developer settings only will not do the trick. It only allows you to have ability unlock the bootloader in fastboot.
If you stuck on the Encryption unsuccessful screen. Try wipe it with stock recovery or "fastboot -w" (if you properly unlocked the bootloader)
If you think you can't do anything anymore. Just flash the ROM provided you above.
If you need the extracted ROM for SP flash tool and the fastboot driver. I can link it to you.
Most of all drivers will automatically install off Windows Update if you're on Windows 10 (except the fastboot driver, and yes. SP flash tool drivers are also provided by Windows 10 too)
Also. You should update the phone to the latest software update when flashing stock rom too. Because newer builds for this phone is compatible-friendly with GSI rom (Treble ROMs like AOSP Android 9 or 8.1 by phhusson)
Updates on Android 9/10
pabloluih said:
Many thanks! At the moment I achieved to root it with twrp. OEM unlock > installed twrp > fastboot -w > magisk.
At the moment all is okey but I have not been able to unencrypt DATA partition (I have done fastboot -w, but with no success, I have not tried TWRP format because of your advice). That's the only point I can complain about.
I hope I do not have to use the stock rom to unbrick, but I have your advice if I do.
Thanks again!
Click to expand...
Click to collapse
Nokia might harden the security of the device so you can't use Magisk on stock rom.

Question Root redmi note 11s

As i'm not familiar with MTK devices i ask for your help.
I've try to patch the image file and flash It with standard fastboot flash boot boot.img.
The phone restart and wifi and bluetooth not works.
After 1 reboot phone can't boot. Restore with fastboot and works now.
I read a guide wich Say to flash both partitions of boot ( i wasn't aware of this before ) as boot_a and boot_b partition.
Is the right metod to patch the boot image and than flash It to both partition?
Thanks for the help
To root? You shouldn't need to flash both boot partitions to root. I'd flash everything with one of the bundled flash_all.bat scripts so you've got a clean slate to work with for your next attempts.
aricooperdavis said:
To root? You shouldn't need to flash both boot partitions to root. I'd flash everything with one of the bundled flash_all.bat scripts so you've got a clean slate to work with for your next attempts.
Click to expand...
Click to collapse
I've already flash It with flash_all.bat, same was done before. So even with 1 boot should work? Why have 2 different partitions? I Just don't understand that.
It's unusual to see wifi and bluetooth broken like that, it's not my First ride, i've flash and root lot and lot of phones but it's my First Time with double partitions as i mention and not so familiar with MTK devices.
Did your have sucessfully root your 2 partitions devices with Just 1 boot IMG flashed?
Have anyone sucessfully root this phone?
Can anyone post a guide for this phone?
I tried a lot without success. Any working procedure?
I'm still stuck, i haven't try to flash both a-b boot partition... I'm too scared... What have u tried?
Have you followed this? If so are you downloading the right boot.img? https://forum.xda-developers.com/t/root-poco-m4-pro-4g-fleur-using-magisk.4449193/
Can anyone help US??

Categories

Resources