Would anyone help me get root on doogee bl 12000? This is a version without a pro so this is a different topic than this one.
No kingoroot or framaroot programs work.
I have flashtoola and rom for this phone. I tried using adb to upload files with the 12000 pro doodge but there was always some error.
I also tried to upload files via flashtoola and recovery. However, without success.
Root Doogee BL12000
Hallo there. I'm trying to root my Bl12000. I've got a TWRP from twrp builder. It works, but whatever zip file I'm trying to install I always get "failed to mount data", invalid argument. The twrp also tells me, that there's bo OS installed, but there is. Phone is working fine after reboot. SuperSu can't be installed. Full wipe is not possible, also "failed to mount" and so on.
any help ?
Tia, Chris
I think it's the encryption. Any ideas how to remove it?
Installed twrp via fastboot and sp flash tool, but I can't boot phone into it. Searched dozens of sites, no success. Flashed the twrp again with sp flash tool and according to sp it was successful. I tried several ways to boot the phone into it afterwards, no luck
My goal is to root this phone only. I'm not very experienced so if anyone could please give me a hand here and tell me where or what I'm doing wrong, that'd would be great and much appreciated. Thanks.
Ok. If I flash the twrp with Sp flash tool and type "fastboot reboot" on the adb console, sending the command while I hold vol+ and power-, the phone boots into the twrp. Next time it will be gone, so I have to flash it again. Noticed that, done.
But all this is taking me nowhere, because the encryption still prevents me from installing any zip file or format a partition. Yuck ?
Root Bl12000
Since the SuperSu method took me nowhere I decided to try Magisk. And.......HURRAY !!!!!!.......it worked.....for a moment. Booted the patched boot.img and got superuser. But with the first reboot I got stuck in bootloop. Tried again, in case I missed something, but same ****.
IT WORKS !!!!! My mistake was to assume, that Magisk works the same way as rooting with SuperSu does. So after rooting with Magisk I tried to install root apps as I was used to, but Magisk does not work that way.
Well, it'll take me awhile to figure this out ?
Why does an app keep coming back on my phone after I have done factory reset?
Christian1968.Bolz said:
Hallo there. I'm trying to root my Bl12000. I've got a TWRP from twrp builder. It works, but whatever zip file I'm trying to install I always get "failed to mount data", invalid argument. The twrp also tells me, that there's bo OS installed, but there is. Phone is working fine after reboot. SuperSu can't be installed. Full wipe is not possible, also "failed to mount" and so on.
any help ?
Tia, Chris
I think it's the encryption. Any ideas how to remove it?
Installed twrp via fastboot and sp flash tool, but I can't boot phone into it. Searched dozens of sites, no success. Flashed the twrp again with sp flash tool and according to sp it was successful. I tried several ways to boot the phone into it afterwards, no luck
My goal is to root this phone only. I'm not very experienced so if anyone could please give me a hand here and tell me where or what I'm doing wrong, that'd would be great and much appreciated. Thanks.
Lucky Patcher 9Apps VidMate
Ok. If I flash the twrp with Sp flash tool and type "fastboot reboot" on the adb console, sending the command while I hold vol+ and power-, the phone boots into the twrp. Next time it will be gone, so I have to flash it again. Noticed that, done.
But all this is taking me nowhere, because the encryption still prevents me from installing any zip file or format a partition. Yuck
Click to expand...
Click to collapse
This Recovery is only supported for Doogee BL12000
You should have either PC or Laptop.
Make sure to charge your phone for at least 50%.
Download and install latest Doogee USB Drivers on your PC/Laptop [All Android USB Drivers]
Download the SP Flash Tool Software
VCOM driver: Download – Instal the VCOM Driver on your computer (still compatible with MT67xx phones)
Before flashing a custom recovery, you need to unlock the bootloader on Doogee BL12000
Take a full backup just in case if you need it later
TWRP+root bl 12000
joachim97 said:
Would anyone help me get root on doogee bl 12000? This is a version without a pro so this is a different topic than this one.
No kingoroot or framaroot programs work.
I have flashtoola and rom for this phone. I tried using adb to upload files with the 12000 pro doodge but there was always some error.
I also tried to upload files via flashtoola and recovery. However, without success.
Click to expand...
Click to collapse
On the forum 4pda can be found for bl 12000
TWRP+ROOT
when you install twrp formatting you can not do it, but immediately install magisk and reboot ...
Related
Hi to all. I'm new in Honor world and I've stopped my Android experience with KitKat so I'm a little bit confused ...
I've read several guides (on XDA too) that that three steps to obtain root are unlock bootloader, flash TWRP via ADB and then install Magisk or SuperSU via TWRP. But in the thread on TWRP is clearly written that to install Magisk decryption is needed and to have decryption we must flash a kernel with encryption disabled in fstab. But no guide says anything about this step. Can someone explain me how encryption/decryption work doing a standard installation of TWRP ? Is needed a flash of a modified kernel ? And where find it ?
And another question (if it's not too much ). Since I don't need to install custom rom (I want root only to use some apps like Titanium) how can I make a backup of stock rom, boot.img, efs partition and all that can be useful to restore phone to the starting point if, by chance, I need Huawei warranty ?
Thanks a lot
Hi, apparently there's a way to get root on an encrypted system. Follow the rebrand guide and then flash supersu in TWRP via ADB sideload. It worked for me and a few others, there is no comment from the developers as of right now.
So basically in short follow this guide until you are finished with the TWRP section:
https://forum.xda-developers.com/honor-9/how-to/one-guide-recovery-os-roms-t3661829
Then
- enter twrp
- adb sideload supersu
Afterwards follow the "rooting!" section with point 2
Thank for your answer... I'd like to try to install Magisk instead of SuperSU. In several places is written that this should be right. I'll try....
unvisigoth said:
Thank for your answer... I'd like to try to install Magisk instead of SuperSU. In several places is written that this should be right. I'll try....
Click to expand...
Click to collapse
The method is also working fine with Magisk. Let me know if you need help
zxz0O0 said:
The method is also working fine with Magisk. Let me know if you need help
Click to expand...
Click to collapse
Finally done with a couple of hours of panic. This is the story if can be useful to someone...
Unlock bootloader....done TWRP install... done. Copy magisk (apk and zip) on phone than install apk without opening it. Reboot to recovery wipe all, factory reset. Trying to boot.....BOOTLOOP But I don't have installed Magisk zip. Only apk without opening it.
Nothing to do. Bootloop and then erecovery. I try to restore the backups previously done with TWRP. I restore boot and system partition. All wipes ...no luck. I don't know what has happened. While downloading full firmware to try to reinstall it I try to install magisk.zip. Install via TWRP. All wipes and then magically (it's such a case ) phone boots. Powered off and on several times no problem. Root (verified with root checker) ok.
I habe b100 release but I don't think to update to b130. I wait for Oreo...
The only two things that I can say are these: first TWRP even after flashing magisk gave an error (unable to mount system). Two while installing magisk it seems that magisk itself has patched something.
If someone has an explanation is welcome...
unvisigoth said:
Finally done with a couple of hours of panic. This is the story if can be useful to someone...
Unlock bootloader....done TWRP install... done. Copy magisk (apk and zip) on phone than install apk without opening it. Reboot to recovery wipe all, factory reset. Trying to boot.....BOOTLOOP But I don't have installed Magisk zip. Only apk without opening it.
Nothing to do. Bootloop and then erecovery. I try to restore the backups previously done with TWRP. I restore boot and system partition. All wipes ...no luck. I don't know what has happened. While downloading full firmware to try to reinstall it I try to install magisk.zip. Install via TWRP. All wipes and then magically (it's such a case ) phone boots. Powered off and on several times no problem. Root (verified with root checker) ok.
I habe b100 release but I don't think to update to b130. I wait for Oreo...
The only two things that I can say are these: first TWRP even after flashing magisk gave an error (unable to mount system). Two while installing magisk it seems that magisk itself has patched something.
If someone has an explanation is welcome...
Click to expand...
Click to collapse
So do you have some step-by-step instructions for someone who wants to unlock and root the phone with magisk?
shiboby said:
So do you have some step-by-step instructions for someone who wants to unlock and root the phone with magisk?
Click to expand...
Click to collapse
Here what I have done:
Unlock bootloader
install adb drivers (find something that is right for your PC. For example minimal ADB found on XDA weren't suitable for me. Google adb drivers...). Open a command windows (shift+right click). If typing "adb devices" your phone is found that's ok
Enable usb debugging and oem unlock (or in other words disable FRP, factory reset protection)
Put the phone in fastboot mode ("adb reboot bootloader"). If all ok typing "fastboot devices" your phone is found
Type "fastboot oem unlock xxxxxxxx" (xxxxxxxx is the code provided by Huawey)
Bootloader unlocked
Flash TWRP
Download TWRP recovery for Honor 9 (link found on other thread on this forum)
Put the phone in fastboot mode
Type "fastboot flash recovery xxxxx.img" (where xxxx.img is the recovery downloaded)
Reboot phone directly in Recovery to avoid erecovery overwrite TWRP. Booting on TWRP let TWRP patch to avoid erecovery booting
Now here I've had some issues as said (read previous post). My tip is the following:
after rebooting in TWRP make all wipes then reboot again in TWRP
Install Magisk.zip (for me download here https://geekaxe.com/root-honor-9-twrp-bootloader-unlocking/)
Reboot recovery
All wipes
Reboot to system
If it's all OK you can install magisk.apk and you are rooted
I suggest after flashing TWRP to make backup of all partitions on external SD (for some reasons, maybe encryption, backup on internal storage gives error). Again I suggest to copy all files that you need (i.e. magisk files) on external sd before starting all.
Pay attention that if you update firmware after this procedure I think that you must repeat all. For me I remain on original firmware found on phone (B100). B130 seems to have some bugs, B120 doesn't seem improve much. Moreover all releases are 7.0 based. I wait for Oreo, hopefully in some custom rom!
To add to this, a bootloop or two might be normal. Let it sit for a few minutes before considering re-flashing everything.
Thanks for your guide!
Zuzler said:
To add to this, a bootloop or two might be normal. Let it sit for a few minutes before considering re-flashing everything.
Thanks for your guide!
Click to expand...
Click to collapse
You're right. But after 20 minutes of bootlops I've chosen another way....:laugh::laugh:
unvisigoth said:
You're right. But after 20 minutes of bootlops I've chosen another way....:laugh::laugh:
Click to expand...
Click to collapse
So is it fixed?
Sent from my Honor 8 Pro using XDA Labs
adriansticoid said:
So is it fixed?
Sent from my Honor 8 Pro using XDA Labs
Click to expand...
Click to collapse
Yes sure. As said previously installation of magisk.zip fixed the bootloop problem. I think (but I could be wrong) that installation of TWRP corrupted the boot partition and magisk fixed it. But it's only an hypothesis...
unvisigoth said:
Yes sure. As said previously installation of magisk.zip fixed the bootloop problem. I think (but I could be wrong) that installation of TWRP corrupted the boot partition and magisk fixed it. But it's only an hypothesis...
Click to expand...
Click to collapse
Observe and be careful man.
Sent from my Honor 8 Pro using XDA Labs
unvisigoth said:
Yes sure. As said previously installation of magisk.zip fixed the bootloop problem. I think (but I could be wrong) that installation of TWRP corrupted the boot partition and magisk fixed it. But it's only an hypothesis...
Click to expand...
Click to collapse
Which TWRP version did you use?
I had a similar problem after formatting all data with the OpenKirin TWRP 3.1.1 Perhaps its an issue with this TWRP release?
I was able to recover in similar circumstances by flashing a stock boot.img over fastboot. Based on this, it's looking like Magisk is really the way to go for rooting atm. Making sure to pull my twrp backup with adb this time though.
If I'm lucky enough to install magisk and not get a bootloop the safetynet always fails. Anyone got a valid method of actually getting magisk working fully?
Hi guys, i got my H9 yesterday and because i thought i read enough on this forums i wanted to unlock it then install TWRP and install superSU to gain root access and stick with the stock firmware.
Unlocking went perfectly fine,phone booted to OS, than i flashed twrp 3.1.1-1 as advertised here and made a factory reset. Phone was stuck in bootloop for unknown reason.
I made several wipes and somehow managed to check all boxes in the wipe menu which erased the whole OS.
Now i read here that others have the "no OS" problem too but because i still have all unlocked fastboot and twrp i wanted to ask which method is best to flash back the original FW.
Which stock ROM is safe to install? i have european H9 is STF-L09C432B170 the right one for me?
Which method is the best to install it? Copy the 3 zips to internal stoagre via OTG device and install it out of twrp? I read that there is also a force method where users can push vol up, vol down and power simultaneously and enter the huawei install force mode.
I am quite sad that the phone was stuck in bootloop after twrp install and still dont know what caused it. When i install it from twrp there are 3 zips: update, data full public , hw eu. In which order do they have to e installed and is one of them overwriting the TWRP recovery?
Please give me a short hint/procedure, im quite afraid that i cant get my phone back to work and it is brand new. I dont know what caused the unsolvable bootloop.
Best regards and many thanks
Hi.
Check this:
https://forum.xda-developers.com/showpost.php?p=73334439&postcount=1
This help you.
Regards
thanks for the hint but i cant find a solution for me there.
ut this
i copied the 3 .zip files to internal today but TWRP doenst allow me to write them it fails with "write err errno 9"
then i tried to copy the update.pp in DLOAD folder on micro sd but this is not possible because filesize is over 2gb. i tried to format micro sd with twrp to exfat but it till doesnt work. please give me a little hint what to do im completely desperate about the situation.
Today i installed Huawei Multitool and extracted the .img file out of the update.app files, i was able to flash all 4, system, boot, recovery and cust.
Now the rec. menu is back to stock and everything got installed but the phone still isnt booting. i think it is because i missed the userdata.img which i cant find anywhere.
Other users here have the same problem. Is there a firmware package which includes all 5 .img data?
Best regards
i found the official huawei service full repair firmware with all necessary files for unbrick (system, cust, recovery, userdata, boot) flashed them via fastboot but stil device is "hanging" after the warning message that its unlocked. i think it is because i wiped vendor data in twrp but i cant flash vendor.img in fastboot. it is included in the fw package but cant be transfered to phone via fastboot. it stops at part 1/2 because the filesize allowd is around 470mb max but the extracted file has a size of 670. anyone know what to do?
Best regards
You need to go via the Rebrand way with no rebrand. I had the same problem and was trying to use the multitool without success. The oeminfo can be flashed alternatively if it fails during the HWOTA process.
https://forum.xda-developers.com/honor-9/help/how-flash-oeminfo-t3657499
ok i download all the folders with the .bat file. Then i download C432B150 from the czech site and add it to the update folder. Than i rename the 3 files accoding to the manual and run the .bat file but without rebranding right?
Des this tool any different than the HuaweiMultiTool or fastboot with flash command?
Best regards
I treid out HWOTA, the first step installing twrp is successful than i disattach usb cable as described and enter twrp. Then it says in twrp i have to connect again and press enter but then the bat file stops and doenst go on. i dont come to the point where i can choose rebrand or flash firmware.
Whats wrong here?
edit: i saw in the .sh file that the script executes wait_adb but my phone is not entering adb mode as it seems when in main screen of twrp. is this normal or do i have to set it manually in twrp
best regards
I was able to install the B130 now via 3 button recovery. Now im on B130 but cant update elsewhere. Also the 2 capacitive buttons are not working. Bootloader is locked again. Everything is stock and the phone runs great. When i update with the 3 buton method from external sd, which firmware should i use? i tried B150 full OTA but it aborts after 5% with an error. Do i only need to get a small OTA package now?
How can i put my cap. buttons back to work? Too bad only the 3 button method worked to recover the phone.
Best regards and many thanks.
I did the HWOTA with b120 firmware and then used firmware finder to update to b150.
The bug with capacitive buttons is present till Oreo. I use the home button gestures anyways.
Hope it helps.
ok, thats bad but they worked with the initial revision of b130 and b150 when i downloaded it OTA. Is this something like a fuse like.knox at samsung which happens at custom flashing?
Sent from my GT-I9300 using Tapatalk
the HWOTA method doesnt work, the batch file gets stuck after connecting the phone in twrp back to computer. in script it says wait_adb but it is not recognized somehow.
do u know a solution? anotherone here got that problem too.
im very afraid of that, i read here that everything related to twrp 3.1.1-0 and 3.1.1-1 is problematic a lot of people cant boot after installing twrp and can wipe whtever they want the phone never boots fully
whats the difference in the B130/B120 the phone came from huawei and the version flashed via tools? when i got it everything worked
i have this version.
ok so install twrp have frq and bootloader unlocked and then do backup out of recovery? with your file? can you provide download link? is this then a zip file?
I want to solve the thread and how i solved problem.
The B130 service firmware by huawei could be installed via 3 button method, than i was able to go up to the newest B180 via firmwarefinder and DNS method but with not working cap. buttons and flash etc.
Yesterday i installed TWRP 3.1.1-1(temporary) via HWOTA.zip method (ireplaced the older twrp in recovery folder) and successfully installed B120 and got the buttons etc working again. Then installed root and now system works fine and is rooted. My mistake was to install twrp over B130 or B150 which i downloaded OTA at the first day i got the phone. I tested this yesterday to install TWRP along with B150 and unlocked bootloader, infinite bootloop again. With B120 the TWRP 3.1.1-1 works out of the box without any loops.
The 2 trouble solvers where B130 service firmware and HWOTA with B120.
The external SD had to be inserted in card reader on PC because of the large filesize of the B130.
I would recommend to everyone before starting to play with the H9 to move the B130 folders to phone while it is still accessible. When everything bricks like in my case and u still have twrp than you can go to twrp main screen and connect phone to computer to rename the folder with B130 to "dload" and arrange update.app accordingly on PC or in TWRP file manager.
Can i set this topic to [SOLVED] myself?
Best regards
https://forum.xda-developers.com/honor-9/development/firmware-huawei-honor-9-stf-l09-stock-t3696892
this works flawlessly with 3 button method
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.
as stated above, i can't seems to find a workable root method for this device. i've already tried kingroot, kingoroot, and some unknown website that claimed have solution to root this device and make my phone restart and restart and restart.. luckily, my phone still can be saved.
im now at dead end. can someone help me how to root this device, and a clear tutorial since, im not good with android system..
thanks..
bump
while waiting for someone to come out with help. I've found a website which have "unofficial" twrp.
https://unofficialtwrp.com/doogee-bl12000-pro/
I want a comfirmation if this site is trustworthy.
I've tried flash the twrp into my phone but it keep booting at recovery and can't boot into system.
I'm flashing using CMD like this:
fastboot oem unlock
fastboot flash recovery recovery.img
fastboot boot recovery.img
Click to expand...
Click to collapse
and what the function of "fastboot flashing unlock"?
I'm thinking of using magisk to root my phone but I don't know what "stock boot image dump".
bump
seems that https://unofficialtwrp.com/doogee-bl12000-pro/ really work, but for my case, it's required me to decrypt password, while im not had any password.
after many times of rooting effort, it success. for those who have problem that occur to me:- BOOTLOOP at RECOVERY and RECOVERY can't read SDCARD or STORAGE
1. Root your phone using the twrp above
2. if bootloop to recovery, make sure you have sdcard and have supersu flash file inside it.
3. in twrp, go to wipe. and then format factory
4. go to mount and choose media sdcard
5. at the homescreen, go to install and then flash the supersu flash file.
6. done
Click to expand...
Click to collapse
in my case my phone gained root permission, but lose twrp recovery. i don't really know about phone, so i hope someone can add something to make this clear to who's that read.
my goal is to root, so without having twrp doesn't concern me much.
well.. my mistake.. the TWRP is there. i dindt realize it.
hello
Please help me
I mistakenly gave the recovery TRWP model 12000 to the phone
And now the phone is turned on and off
What should I do to be right?
please somebody help me
I just bought a Nuu R1 Rugged Phone. It has Oreo 8.1.0 on it.
It is an "unlocked" phone. But I don't know if unlocked refers to the phone carrier or to the boot loader. (I'm thinking phone carrier.)
The last I rooted my tablets was Android 5, which required using a custom script that a dev here wrote that temporarily ran CW via fast boot.
I would like to root my R1. I hear now that Magisk is the way to go. (Instead of SU.)
Most every Guide says that I have to have TWRP installed before installing Magisk. But there's no TWRP for the R1. And I am incapable of compiling my own.
I learned, from Nuu Tech Support, that I can get into the phone's Recovery mode with some hidden button pushes. Here's a screen shot:
My first question is, could I simply install Magisk by selecting "Update from SD card"?
If it's not that easy, then, second: I can also get to a fastboot screen. (Not shown here.) Could I install Magisk from ADB on my computer?
I suppose a third question: Is there a version of TWRP that's compatible with this phone? And if so, how do I find it? It would be nice to have a Nandroid backup.
I am willing to show various screens that come up from various button pushes if that would help a dev here.
More data for TWRP'ing
So, I see that one needs an image of the OEM ROM to compile TWRP. I found two sites on the web that claim to have the ROM. (Before the R1 was officially released.) Sounds sketchy. Will try to get an image from Tech Support.
In the meantime, I found that the bootloader can be unlocked (or allowed to be unlocked) via a setting under Developer Options.
I contacted Nuu Mobile Support and they were kind to send me the MediaTek USB drivers for the R1.
It was a two step process to get the driver installed for ADB. But now I have access to the R1 via ADB.
I read here on the forums that I can boot TWRP via fastboot, and not risk ruining/corrupting the R1's Recovery Partition.
Anyone know of a TWRP model version that's close enough to work on the R1? (I presume a TWRP for another MediaTek device might work?)
I would hate to try KingRoot to get root.
I found a website called unofficialtwrp.com. It has a TWRP for the MediaTek 6739, running Oreo 8.1, with 16/2 GB. That's exactly what the Nuu Mobile R1 has.
So, hopeful that this would allow me to root my R1, I tried it. (Short version: Didn't work.)
I already had ADB installed and could talk to my R1 via ADB.
But once the R1 had booted into fastboot mode via ADB, I got a message from fastbood devices that it was "waiting."
I learned that that message means that I didn't have drivers for fastboot.
I ended up installing a fresh version of Win8.1 and using the Windows' updater to find the needed drivers. I had to have the R1 plugged in to the USB in fastboot mode for this to work. After that, I could talk to the device via the fastboot command.
So I unlocked the boot loader (which wiped my data - not every Guide warns you about that) and I did "fastboot boot recovery.img."
I got the message that the recovery file had transferred. After abotu 15 seconds, the phone rebooted. But no TWRP.
Rats.
I didn't want to try the fastboot flash command in case this unoffiical twrp from an unofficial site bricked my phone. If I understand things correctly, booting in fastboot to the recovery.img should give me a temporary instance of TWRP.
Presumably, after copying Magisk into memory, I would be able to get root that way.
PMikeP said:
I found a website called unofficialtwrp.com. It has a TWRP
Click to expand...
Click to collapse
Whoa you have been busy you must've heard XDA helps those who help themselves.. :highfive:
I just dropped by to say, 1st rule of modding is taking a pristine stock backup..
For MTK devices, there is a tool called SP Flash Tools, a quick search will help you take a full backup using this tool.
Afterward, you can even try using SP Flash Tools to flash a Magisk patched boot image to your device for ROOT!
Hope this helps!
Thanks. I did see SP Flash Tools mentioned and I did take a look at it. While I've rooted before, I'm trying to get my head around a Scatter File.
Everything I've read so far - well, almost everything - says that I need TWRP to get Magisk installed. But if you think it can be done via SP Flash Tools, I'll start playing with it.
Root nuu r1
Did u ever manage to figure out how to do this & get TWRP to install? :fingers-crossed:
No, I haven't had time to play with rooting lately. I still would like to root it tho.
Anyone know how to root the nuu phones?
someone has the boot.img i need the image
I will port TWRP for you in case you have stock recovery.img
jjgvv said:
I will port TWRP for you in case you have stock recovery.img
Click to expand...
Click to collapse
plis
do you have stock rom?