So I accidentally flashed a wrong boot.img while on my current ROM (AOSiP 8.1) The wrong flash caused my system to be somewhat destroyed (Can't mount and others). The only hope I had was to do the FastBoot method which somehow worked but returned me to MIUI 9.
I did all the rooting and recovery process again and decided to flash the AOSiP ROM again with the proper procedures but as soon as I install after wiping I get the error something like "twfunc failed to flash repacked image". I thought it was just a corrupt download but after downloading twice and using another ROM it was still the same. Can somebody please help me? It's a hassle going through the FastBoot flash method again and it might get worse if not yet fixed ASAP.
ClockUpEx said:
So I accidentally flashed a wrong boot.img while on my current ROM (AOSiP 8.1) The wrong flash caused my system to be somewhat destroyed (Can't mount and others). The only hope I had was to do the FastBoot method which somehow worked but returned me to MIUI 9.
I did all the rooting and recovery process again and decided to flash the AOSiP ROM again with the proper procedures but as soon as I install after wiping I get the error something like "twfunc failed to flash repacked image". I thought it was just a corrupt download but after downloading twice and using another ROM it was still the same. Can somebody please help me? It's a hassle going through the FastBoot flash method again and it might get worse if not yet fixed ASAP.
Click to expand...
Click to collapse
Did you try using redwolf recovery? Also do this. Go to en.miui.com and dl the latest miui zip. Using redwolf try to flash it. If you are able to do it then possibly it's something with stock twrp. If not then you might need to fastboot flash miui again. The last option would be to use edl mode.
I tried FastBoot method flashing the latest MIUI 9 build. Worked out fine but after Rooting again and adding Recovery, flashing ROMs give me Error7 most of the time. What I did is I accidentally clicked the Clear All on the MiFlash and resulted to my problem being fixed while losing all files in my internal. Noooooo!
ClockUpEx said:
I tried FastBoot method flashing the latest MIUI 9 build. Worked out fine but after Rooting again and adding Recovery, flashing ROMs give me Error7 most of the time. What I did is I accidentally clicked the Clear All on the MiFlash and resulted to my problem being fixed while losing all files in my internal. Noooooo!
Click to expand...
Click to collapse
Soo? Is it fixed now? Is that what you mean?
Hello,
I was wondering if some could help me please. I wanted to flash RR Rom 6.0 on my BLA-L09(I think that what's it is) phone.
I was able to unlock my boot loader, and flash TWRP my device but my dumb s*** flashed TWRP to my file system use FLASH SYSTEM instead of FLASH RECOVERY. Now, I can't fix it ?. I know I can use sideload so I'm not panicking just yet however I know I messed up the file system.
Could someone tell me what file system system I should be using (fat, exfat, ext4, etc...) and what to do to get this think to boot backup.?
I've tried and side loading "update_full_BLA-L29_hw_la.zip" stock ROM but no luck... I keep getting this error message:
"check_write_data_to_partition,write data error
Update_huawei_pkg_from_ota_zip: update package from zip failed
Updated process ended with error: 9"
HELP.!!!
me too..... following searching for a solution
Shandroid_94 said:
me too..... following searching for a solution
Click to expand...
Click to collapse
If you find anything, let me know.!
Just boot to fastboot, flash RR to system and TWRP to recovery_ramdisk?
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.
Got an update notification on my nexus 6p with installed RR-P-v7.0.2 on it. After installing this OTA update i got an infinite booting screen. I loaded back into twrp and got a password prompt to mount partitions (i didn't have any passwords anywhere on my phone before). I could neither access internal storage from within recovery, nor from pc. Installed newest version of TWRP (3.4.0), didn't help. Did a full wipe, which finally helped and allowed me to see and transfer files to my internal storage. Downloaded RROS-Q-8.5.9 zip from official site, tried to install again, which resulted in same error as before. Then i found out that i can load the system even with this error presenting, but i CAN'T install magisc. I don't know if it is me, who does something wrong or is it error in system zip? Also before each attempt to reinstall RROS-Q-8.5.9 i see logs, that magisc binaries r missing, i don't know if that might be the reason of vendor error in the end. The only way i can fix it is flash official vendor.img and flash older system image. But i really want to have RROS-Q-8.5.9 on my phone, with magics. Initially i posted it in 'Nexus 6P Q&A, Help & Troubleshooting', but no1 responded, so i duplicated this post here in case some1 knows the answer. Please help.
I'm sorry for being unfriendly. I'm lazy.
Most android10rom for angler cannot be flashed without using this twrp. If you want to switch back to pie rom, use the official twrp.
Then your latest post is on the nexus6 shamu thread.
Everyone makes a mistake because the terminal names are very similar. So don't complain to kae.
https://androidfilehost.com/?fid=4349826312261691698
For the time being, there are few posts on this device, so I think it's okay to write here.
https://forum.xda-developers.com/nexus-6p/development/9-0-resurrection-remix-v7-0-t3892786
Thank you for your response anyway. Tho i managed to flash the rom without getting this vendor error at the end. Steps i did: flashed back to RR7.1.2, did a backup, wiped everything including system, than flashed new RR8.6.0, which flashed fine with no errors. After this i flashed magisk right away, and it went fine (it couldn't before, cuz of the error 'failed to mount /vendor' after attempting to flash OS zip), with exception of an error 'failed to mount /vendor (no such device)'. Still i've got nexus 6p with android 10 and root, which can't update, cuz of the permanent vendor error after i flashed magisk.
Next time i will need to flash anything, i will use TWRP u suggested. Thank you again.
So I just rooted my pixel 6 using the correct original img from google and Magisk. This worked great and I got root access (active boot partition was a if it’s somehow relevant). Now I wanted to use all the functions of nethunter (which I downloaded and installed from nethunter store or something like that), so I wanted to install the nethunter Kernel for my device. Pixel 6 is not officialy supported by kali or not leaked yet so I found pre build nethunter kernel for pixel 6 on xda developers.: https://forum.xda-developers.com/t/...o-oriole-raven-kernel-kali-nethunter.4461589/
So I went in to the mega folder and into the mad-kali-maxhunter-kernel folder. Then into the p6_p6pro folder. Then I just downloaded the maxhunter zip thing for oriole because it stands for p6 ig. Then I flashed this zip file using the Franco kernel manager as recommended in the thread. My device restart and didn’t start up again. So I just tried getting in fast boot and I got it. Now I thought i would just flash the patched magisk img I made for rooting the device previousl. So I did that using fastboot flash boot and so on. Next my device was in an bootloop still, so then I flashed the very original google official img for the device. Still boot loop, so then I wanted to do recovery from fastboot on the phone when I started factory reset mode the phone was just stuck in the google logo. Then I wiped all data using the fast boot tools from my computer. It wiped it but said stuff like the file system is not formatted or not the right format or so but still wiped the data. Still boot loop. So now I switched the active boot partition from a to b. This time the phone said like waiting for command and so on. So I watched a tutorial and got further, now I was able to get to the factory reset mode did. a reset and started. Nothing realy happened and it jumped back to fastboot mode. I thought maybe because in boot b is no img to boot. So I flashed the official google img again but on b. Still bootloop. Now I have a problem. Pls help me.
You should consider trying Google's official Android Flash Tool, it might succeed where your manual flashing failed -- especially considering it was set up by Google and might have better/further checks and such...
Yes, I would recommend Android Flash Tool also. Its helped me a couple times to recover when I couldn't boot. It gives you options for boot.img right before flashing your phone so everything you'll need should be there
@simplepinoi177 i would really like to use it but its using adb and adb is not passible only fastboot so my device isnt available. EDIT: Nvermind i didnt read correctly.
Thank y'all so much it worked!!!
Great. Android Flash tool ftw again