Hi,
I have a stock ANE-LX1 9.1.0.355(C55E8R1P6)
I just can't root the phone!!!!
I tried both flashing the Magisk zip from TWRP and patching the recovery_ramdis.img from the app and then flashing from fastboot, but
Magisk Manager just doesn't see Magisk.
Plz help, thanks
David
DP FH said:
Hi,
I have a stock ANE-LX1 9.1.0.355(C55E8R1P6)
I just can't root the phone!!!!
I tried both flashing the Magisk zip from TWRP and patching the recovery_ramdis.img from the app and then flashing from fastboot, but
Magisk Manager just doesn't see Magisk.
Plz help, thanks
David
Click to expand...
Click to collapse
Hey dude try this way out...
- Download Magisk manager apk. , patched recovery_ramdisk and TWRP for 9.1:
https://mega.nz/#!ohkgwSzb!xD32btG_3Sax-V7bn6xbWR5fH0crPrry06cCxusf5Hg
https://mega.nz/#!tkcTlATI!A8UJGPBGtxJbLcUOJoxCGJj5PFZXzCnjbb3OkwqKTP8
https://mega.nz/#!xkd2ibKY!JCLNMNKRI1e0FI1bJ4YI5Lr9Hdg9eo4A9kv0MhxgIdA
Copy TWRP and patched recovery_ramdisk to SD Card, install Magisk manager apk.
- Install TWRP over eRecovery: flash downloaded TWRP 9.1 from fastboot, boot in TWRP, select storage - SD Card, select "Install image". Find TWRP-9.1.img file , mark eRecovery and confirm. Reboot system.
- When the yellow unlocked phone warning appears, press and hold Volume Up , phone will boot into TWRP.
- Select Install image, find Recovery_ramdisk-patch.img , mark Recovery, confirm.
- Go back to the main TWRP's menu > Reboot > Reboot recovery. Phone will reboot via Recovery , but not into Recovery mode. Now every time you want to boot phone with root access must hold volume up and power at the beginning . if you boot phone normaly (not thro recovery comand) your phone will not be rooted!
Now you have a rooted phone with TWRP on board.
Ok thanks, isn't it possible to workaround the volume up stuff? How do I boot twrp after I finished? Vol+ and power button or vol+ and cable? To my understanding, this boots two different recoveries?? Why is it so complicated lol
DP FH said:
Ok thanks, isn't it possible to workaround the volume up stuff? How do I boot twrp after I finished? Vol+ and power button or vol+ and cable? To my understanding, this boots two different recoveries?? Why is it so complicated lol
Click to expand...
Click to collapse
Is your patched_ramdisk "universal" ? I meant will it work on phone with different cust (mine is c55, most have c432 and maybe with different emui version? Where did you get it?)
- it is just an alternative, the method with patched recovery_ramdisk and fastboot should also work. Maybe you're doing something wrong.
- It is complicated due to emui 9.1, the ramdisk partition no longer exists. As a workaround, Magisk will be installed to the recovery_ramdisk partition.
- AFAIK partitions Recovery and eRecovery are the same for all build numbers and regions (we are talking about ANE- models and EMUI 9.1), so it should work.
- "How do I boot twrp after I finished?" - read carefully please: " Reboot system. When the yellow unlocked phone warning appears, press and hold Volume Up , phone will boot into TWRP."
P.S.: I never try to convince anyone of anything, it's your choice .
If you do not understand something here, than the tutorial might not be suitable for you.
There are plenty of guides on how to do these things. GL!
-Alf- said:
-the method with patched recovery_ramdisk and fastboot should also work.
Click to expand...
Click to collapse
I tried the following:
Booting into TWRP, getting recovery_ramdisk with dd, patching image with manager, boot into twrp, flash new recovery_ramdisk with dd, reboot.
Getting recovery_ramdisk from official update, patching etc.
Flashing official Magisk v21.1 with zip. The new image is flashed because the second time it will say "magisk patched image detected" (even if i reboot into twrp again), but still no root.
Sincerely I do not understand what I'm doing wrong. I know myself it should be easy.
I understand the tutorial (and thank you for it, you are a very kind person) I just don't understand why huawei made things so unnecesarely complicated. How does the phone boot without a ramdisk? Is "normal" ramdisk included in the kernel partition or in the recovery_ramdisk partition? Ok I get it, if there is no ramdisk the phone boots directly from the system on root partition, so magisk should mod that partition but it can't because it defeats the purpose of "systemless". Right?
There are plenty of guides, yeah, but everyone says the same thing (magisk zip or patched ramdisk) and people just say it works... but in my case it just... doesn't
Will try to follow your guide to the letter... Thank you again...
Ramdisk is included in the recovery_ramdisk, that's why Magisk will be installed to the recovery_ramdisk partition. Read carefully bro
Note: if you want use TWRP on rooted EMUI 9.1, you MUST install TWRP over eRecovery.
DP FH said:
I tried the following:
Flashing official Magisk v21.1 with zip.
Click to expand...
Click to collapse
Try with lower version , v20.0 or v20.4
Ok, thank you for your tips. I will update you once I have time to spend on this.
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?
Prefix: my xz1 died on me so I was forced to buy a new phone and therefore I won not be maintaining this thread any further. The guide should be relevant even without my help but I just won't be answering any questions regarding this thread or anything to do with the xz1.
YOU DO NEED TO UNLOCK YOUR BOOTLOADER AND THEREFORE WILL LOSE YOUR DRM KEYS!
NONE OF THIS IS MY ORIGINAL WORK BUT MY PROCESS IS ORIGINAL. YOU CAN THANK @modpunk FOR HIS PORT OF TWRP TO THE XZ1 AND YOU CAN THANK @janjan FOR HIS HARD WORK IN CREATING THE FIRST FULLY FUNCTIONAL KERNEL THAT SUPPORTS MAGISK AND STILL OFFERS A WORKING CAMERA AND SONY FEATURES
Here we go.....
1: Download modpunk's port of TWRP from this thread: https://forum.xda-developers.com/xperia-xz1/development/recovery-twrp-3-2-1-t3727602
Make sure to check the dates on the files and always download the latest version.
2: Download Janjan's kernel and DRM package here:
https://forum.xda-developers.com/xperia-xz1/development/kernel-sony-xz1-23-january-2018-t3739586
Make sure to check the dates on the files and always download the latest version.
3: Enable developer settings and enable ADB Debugging. I shouldn't have to say this part but something tells me if i don't then i'll get loads of questions about not being able to connect to the phone, lol.
4: Connect the phone to your pc and copy the 3 zip files contained in the janjan download to your phone. You don't need to copy the boot.img to your phone.
5: Open a cmd window on your pc and type the following:
adb reboot bootloader
6: Once the pc recognizes the phone in bootloader mode then type:
fastboot flash boot path/to/the/boot.img (I usually just type "fastboot flash boot " and then just drag and drop the boot image into the cmd window.
7: Once the boot image is flashed unplug the cable from the phone then reboot it. Once it's running then make sure the kernel info has changed to say "[email protected] #1
8: Once again, boot into bootloader by running the adb command
adb reboot bootloader
9: Once in the bootloader type into the cmd window:
fastboot flash recovery path/to/the/recovery.img
10: Reboot to system and then power off the phone.
11: Once it's off, boot into TWRP manually by holding the power button + the vol down button until the phone vibrates once, then let go and it'll boot into TWRP.
NOTE: It will ask you for your password to decrypt the data partition. This password is whatever your pin number or password you use on your phone lockscreen. If you don't use any lockscreen security then the password is: default_password.
12: Once in TWRP flash 2-Patching_drm_Su and 3-Magisk and then reboot to system and check that magisk is installed.
13: Finally open magisk and open the Modules section then tap the + icon and locate and flash the last zip 4-kernel_permissive and then reboot the phone and open magisk and check the modules section to ensure the Magisk SELinux Permissive Script is active.
Now you have a fully functional XZ1 with Magisk root and a properly functioning camera and Sony features.
Enjoy!
N1ghtr08d
Sorry.You forgot to flash SR5-SuperSU-v2.82-SR5-20171001224502.zip in TWRP recovery after step 13
Posting not relevant anymore!!!
1:st posting fixed by N1ghtr08d
Thanks bro. I had edited it and I must have missed putting that back in. Fixing it now
Any try to use Magisk instead of SuperSU ? I need to use some apps witch don't work with root phone.
If you turn the phone off, press and hold 'Volume Up' and attach a USB Cable from your PC it will boot into the bootloader. The LED will be blue then ...
Thanks modpunk, that is very true. I guess my preference is just to use ADB.
As far as magisk is concerned, I believe that none of the magisk releases work with this device. I would prefer to use magisk also so if anyone figures out how to install it successfully without putting the phone in a bootloop, please share it here and I will update this guide. I'd rather have SuperSU than no root at all.
Does anybody have any tips for installing Viper4android? I renamed the audioeffects file in System/Vendor/Etc and installed the Nougat test io fix version and when I opened the app and allowed it to update the drivers, everything went well and looked successful, however upon reboot and opening the app to set it up, it just tells me to update the drivers and reboot again and even doing that just lands me back at the same point.
Does anybody know how I can get it installed and running properly?
Coincidentally V4A installs and runs perfectly now that it can be installed through Magisk Manager!
What FOTA kernel.img are you referring to? There wasn't one linked in the post, and Sony's fotakernel files are in .sin formats. Flashing just the boot.img linked in your post results in a brick. Flashing the fotakernel_X-FLASH-ALL-C93B.sin included in Sony's firmware also results in a brick. Has anyone got this to work?
trevorftard said:
What FOTA kernel.img are you referring to? There wasn't one linked in the post, and Sony's fotakernel files are in .sin formats. Flashing just the boot.img linked in your post results in a brick. Flashing the fotakernel_X-FLASH-ALL-C93B.sin included in Sony's firmware also results in a brick. Has anyone got this to work?
Click to expand...
Click to collapse
Flash boot.img to both boot partition and FOTAKerner partition
fastboot flash boot boot.img
fastboot flash FOTAKernel boot.img
---------- Post added at 02:50 PM ---------- Previous post was at 02:45 PM ----------
Can I use the aledoom's port of the Andro+ kernel at https://mega.nz/#!00l3mABT!RCuCfvwxROggim9D_GwfdhZDTPQJomNrfWZy_lsq0-U for the new 47.1.A.8.49 release?
pergoteborg said:
Flash boot.img to both boot partition and FOTAKerner partition
fastboot flash boot boot.img
fastboot flash FOTAKernel boot.img
Click to expand...
Click to collapse
What FOTAKernel boot.img though? Am I supposed to download one from somewhere? It's not in OP or in the Sony firmware that I've downloaded.
trevorftard said:
What FOTAKernel boot.img though? Am I supposed to download one from somewhere? It's not in OP or in the Sony firmware that I've downloaded.
Click to expand...
Click to collapse
The link https://mega.nz/#!00l3mABT!RCuCfvwxROggim9D_GwfdhZDTPQJomNrfWZy_lsq0-U is the download link for boot.img
fastboot flash FOTAKernel boot.img
The parameters is:
fastboot - An Android SDK command and library used to communicate with a connected android device
flash - The fastboot command you wish to execute. "fastboot flash" takes two parameters, which are:
FOTAKernel - The partition on the connected phone you want to flash and
boot.img - The file you want to flash into FOTAKernel partition.
In this case is the same file (boot.img) flashed into BOTH boot partition(fastboot flash boot boot.img) and into FOTAKernel partition(fastboot flash FOTAKernel boot.img)
Thank you for the help Pergoteborg. I thought the guide was fairly self explanatory.
I pointed out in the op that the one boot image I provided in the download is to be flashed to 2 different partitions.
If you follow my instructions as provided you will have success. It's really easy to follow along if you read it properly.
pergoteborg said:
Can I use the aledoom's port of the Andro+ kernel at https://mega.nz/#!00l3mABT!RCuCfvwxROggim9D_GwfdhZDTPQJomNrfWZy_lsq0-U for the new 47.1.A.8.49 release?
Click to expand...
Click to collapse
I tested myself and answer is NO. Therefor no magisk for 47.1.A.8.49 yet since we do not have kernel support. Root achieved by SuperSU
So I :
Got phone in flash mode (Vol- when putting in computer USB cable, Green light). Ran NewFlasher with 47.1.A.8.49
Booted phone, turned it of and set it to fastboot mode (Vol+ when putting in computer USB cable, Blue light)
Flashed TWRP: fastboot flash recovery twrp-3.2.1-0-poplar-patchlevel-2017-11-05.img
Booted phone, Uninstalled Magisk manager, Installed SuperSU App from Google Play.
Turned off phone, booted into TWRP (Vol- and pwr, release pwr button when phone vibrates, hold on the Vol- button)
Installed Magisk-uninstaller-20171123.zip to get rid of Magisk. Installed SR5-SuperSU-v2.82-SR5-20171001224502.zip to get SU
HIPP!!!
pergoteborg said:
The link https://mega.nz/#!00l3mABT!RCuCfvwxROggim9D_GwfdhZDTPQJomNrfWZy_lsq0-U is the download link for boot.img
fastboot flash FOTAKernel boot.img
The parameters is:
fastboot - An Android SDK command and library used to communicate with a connected android device
flash - The fastboot command you wish to execute. "fastboot flash" takes two parameters, which are:
FOTAKernel - The partition on the connected phone you want to flash and
boot.img - The file you want to flash into FOTAKernel partition.
In this case is the same file (boot.img) flashed into BOTH boot partition(fastboot flash boot boot.img) and into FOTAKernel partition(fastboot flash FOTAKernel boot.img)
Click to expand...
Click to collapse
Thanks for being actually helpful. I wasn't familiar with the FOTAKernel partition. I though it was a typo that was supposed to be the name of some boot.img. I'm familiar with everything else about fastboot. I'm still getting a glitchy display after flashing the boot.img to the boot and FOTAKernel partitions. I think I'll just check out and give up on this one.
Hi There
Thank's to my hero aledoom who ported XZ1 (G8342) FW47.1.A.8.49 to Androplus we can now enjou latest FW and Magisk
Download the patched kernel here (aledoom´s direct link here)
If you currently have root with SU, get rid of it by flasching UPDATE-unSU-signed.zip in TWRP
Then follow the OP, but use kernel from here instead of OP boot.img.
I currently testing MAGISK 15.0 and it's working fine except there is no modules ported to the new template just yet,
Hi all, do you think that TWRP, Androplus kernel et Magisk work on a XZ1 Dual ?
I don't know. To be honest, you'd need to check with modpunk and aledoom if their recovery and kernel are compatible
So this is actually my first official post as a new member on this site but have been a long time user of the guides here. I have a question but I want to root my xz1 to optimize the performance and what not and just cause haha. My question is about what's being lost. I noticed something called xreality or something won't be accessible. What is this? Reason I'm asking is that I playmobile legends and this phone and only this phone I've found has an in game option for. "high frame rate" mode.. I'm not interested in rooting it if all I'll do is make it perform less rather then the opisite anywho Sony's alot different then most android im finding so I figure what the hell better make an account finally and ask.
I have no idea what xreality is. Is it a Sony app?
As far as what's lost, you lose the DRM keys so the camera stops working correctly, as in when you take a photo it just turns out as a green image instead of the picture you intended.
Now with that being said, someone over on the root bounty thread apparently discovered a fix for this that allows the camera to function fully as before. I have tried flashing this fix on my personal device and it didn't work as expected however I'm using magisk for root instead of SuperSU like the poster stated so I'm waiting on a reply from him regarding the usage of magisk Vs SuperSU with his fix.
Here's the thread in question. He posted right at the end of the thread just before me.
https://forum.xda-developers.com/xp...z1-compact-lb-root-drm-backup-t3672176/page16
Hi! I was trying to root Nokia 1
I flash TWRP through fastboot and it worked! But the problem was I was unable to see my files there.I think because of encryption..
So, I accidentally factory reset my phone through TWRP and then, I was unable to boot into system again..
I was stuck in TWRP
So, I go to fastboot and flash stock_recovery.IMG and after that when I reboot. I am seeing a black screen. I can feel vibration when press home key or home + volume up/down. but screen is black
Please help...
abdul_manan said:
Hi! I was trying to root Nokia 1
I flash TWRP through fastboot and it worked! But the problem was I was unable to see my files there.I think because of encryption..
So, I accidentally factory reset my phone through TWRP and then, I was unable to boot into system again..
I was stuck in TWRP
So, I go to fastboot and flash stock_recovery.IMG and after that when I reboot. I am seeing a black screen. I can feel vibration when press home key or home + volume up/down. but screen is black
Please help...
Click to expand...
Click to collapse
Use micro SD card for twrp. You can't remove encryption just by factory reset. I know how to remove encryption on Nougat but that method doesn't work on Oreo. When you flashed TWRP flash SuperSU (not Magisk) then boot to system, after that boot to twrp recovery again and wipe factory reset and wipe internal storage. You have removed encryption. SuperSU needs to be updated to patch plat and non play file contexts to remove encryption on Oreo. Or someone can make flashable zip to remove encryption.
First find nb0 file for Nokia 1 and try to flash rom with OST.
SkaboXD said:
Use micro SD card for twrp. You can't remove encryption just by factory reset. I know how to remove encryption on Nougat but that method doesn't work on Oreo. When you flashed TWRP flash SuperSU (not Magisk) then boot to system, after that boot to twrp recovery again and wipe factory reset and wipe internal storage. You have removed encryption. SuperSU needs to be updated to patch plat and non play file contexts to remove encryption on Oreo. Or someone can make flashable zip to remove encryption.
First find nb0 file for Nokia 1 and try to flash rom with OST.
Click to expand...
Click to collapse
Thanks for the reply!
Can you please tell me where can I find the nb0 file of Nokia 1 with Android 8.1 Oreo Go edition TA-1047?
abdul_manan said:
Thanks for the reply!
Can you please tell me where can I find the nb0 file of Nokia 1 with Android 8.1 Oreo Go edition TA-1047?
Click to expand...
Click to collapse
currently it's not available, you need to wait someone to upload it.
Nokia1 uses MTK CPU right? If you can get the ota zip of the current update on your phone, you can extract the boot.img file then boot into download mode and type fast boot flash boot <boot.img file>
redweaver said:
Nokia1 uses MTK CPU right? If you can get the ota zip of the current update on your phone, you can extract the boot.img file then boot into download mode and type fast boot flash boot <boot.img file>
Click to expand...
Click to collapse
Can you please explain a little bit more!
How to get ota zip file? (My phone is not working as mentioned above)
Where can I get boot.img?
How to extract and where boot.img?
How to boot into download mode?
abdul_manan said:
Hi! I was trying to root Nokia 1
I flash TWRP through fastboot and it worked! But the problem was I was unable to see my files there.I think because of encryption..
So, I accidentally factory reset my phone through TWRP and then, I was unable to boot into system again..
I was stuck in TWRP
So, I go to fastboot and flash stock_recovery.IMG and after that when I reboot. I am seeing a black screen. I can feel vibration when press home key or home + volume up/down. but screen is black
Please help...
Click to expand...
Click to collapse
I'm having a kind of similar issue. I flashed twrp and now its stuck in a twrp loop. It boots only in twrp and not system. What should I do?
Ludba Amb said:
Can you please explain a little bit more!
How to get ota zip file? (My phone is not working as mentioned above)
Where can I get boot.img?
How to extract and where boot.img?
How to boot into download mode?
Click to expand...
Click to collapse
http://www.mediafire.com/file/0xgn9o0b711wcw0/Nokia_1_TA-1047_MT6735_V8.1.0_180401.zip
Stock Rom for 1047
Download it.
Extract boot.img from that
boot into download mode/recovery
adb reboot recovery
answers to all your questions.... not the answer to fix your problem I think... But have a go.
And last but not least... Please use the search option first or google instead of asking all questions at once.
Or try to get familiar with rooting first...…
good luck buddy.
hello everyone i have nokia 1 oreo go edition i don't have any idea how to root
please help me by sending links for :
1 ) nokia 1 (ta-1047 ) TWRP
2 ) nokia 1 custom rom
3 ) nokia 1 current rom (for security)
(remenber thats only model ta-1047)
seriously i want to root it because there are many issues like multitouch screen problem or missing some system apps and also device getting hot because the memory (ram) is lagging (1gb ram is not enough to run android oreo correctly 2018 )
{PLEASE HELP}
help me please !
can you send me a twrp for nokia 1 ta-1047
i need to root my device to dowoad custom rom
MyTH30 said:
I'm having a kind of similar issue. I flashed twrp and now its stuck in a twrp loop. It boots only in twrp and not system. What should I do?
Click to expand...
Click to collapse
Same here. Seems that the decryption does not work. Better make sure your phone is not encrypted before messing with twrp (3.2.3).
Be careful
Some Nokia 1 are a TA 1060 variant number and if you flash the wrong file you are going to have further problems.
The process to root and get TWRP on the nokias Is complicated enough without everyone suggesting wrong model variants / numbers.
I guarantee someone will download the wrong file for the wrong model and come here crying.
is this the real firmware?
inkepinkje said:
http://www.mediafire.com/file/0xgn9o0b711wcw0/Nokia_1_TA-1047_MT6735_V8.1.0_180401.zip
Stock Rom for 1047
Download it.
Extract boot.img from that
boot into download mode/recovery
adb reboot recovery
answers to all your questions.... not the answer to fix your problem I think... But have a go.
And last but not least... Please use the search option first or google instead of asking all questions at once.
Or try to get familiar with rooting first...…
good luck buddy.
Click to expand...
Click to collapse
hi, i needed to know if this is the real one, they show it's mt6735 instead mt6737m, I've already downloaded a file with the similar name nd it has scatter file of mt6735, that's while in the sp flash tool,i don't see all of the partitions being detected to flash
Hey i am facing the same issue but i didn't flash any other recovery mode my phone Nokia 1 TA-1056 am getting black screen and only feel the vibration when i press power key and when i put my phone on charging then its shows the display and boot into recovery mode directly can anyone help me how i can overcome this issue
Requirements / Downloads
Honor 10 view BKL-09 with unlocked bootloader (I not tested in other version)
Minimal ADB & Fastboot
Patched Recovery_Ramdisk BKL
Rooting your device
1. Unzip Minimal ADB & Fastboot to any folder of your PC
2. Download the patched file for your device and copy it to Minimal ADB & Fastboot folder.
3. Start your smartphone in fastboot mode pressing [Vol-]+[Power] and connect it to your PC.
4. Open a Powershell window in your Minimal ADB & Fastboot folder by [Shift]+[Rightclick].
5. Flash the Recovery_Ramdisk:
Code:
fastboot flash recovery_ramdisk name_of_your_patched_file.img
Adjusting Magisk Manager and patching files by yourself
1. Download Magisk Manager canary build to your phone and install.
2. Change in Magisk settings the update channel to "custom" inserting this URL. https://t2m.io/wuAFCrwO
Magisk Manager now will find the canary builds.
3. Check "force encryption" and "AVB 2.0" boxes.
To patch yourself recovery_ramdisk:
4.a) Patch your *.img, that you have copied in any folder to your smartphone by pressing "Install" --> "Install" --> "Patch boot image" in Magisk Manager.
ORIGINAL RECOVERY_RAMDISK BKL-09 PIE version 9.0.0.162 C432
5. Transfer the patched file (You will find it in your download folder of your smartphone. It will be called "patched_boot.img".) to your PC, start Smartphone in fastboot mode and flash:
Code:
fastboot flash recovery_ramdisk name_of_your_patched_file.img
(You must adapt the file name to the real name of your file, e.g. patched_boot.img)
To actualize Magisk:
4.b) Choose in Magisk Manager: "Install" --> "Install" --> "Direct Install (Recommended)" --> Restart
Thanks
Thanks a lot for this great guide!
Hello, will this also be on my bkl-l09c432? I have rom
blazios said:
Hello, will this also be on my bkl-l09c432? I have rom
Click to expand...
Click to collapse
If your device is on pie ?, yes
What should I use twrp?
blazios said:
What should I use twrp?
Click to expand...
Click to collapse
OP never mentioned anything about twrp. That is not needed
I Have same version as you Android Pie and everythin firmware and region... But no matter how i try i get UNABLE TO UNPACK BOOT IMAGE... Instalation failed... why is that? i have TWRP installed... and everything as is your phone firmware and version 9.0.0.162 C432...
BlueMan_86 said:
I Have same version as you Android Pie and everythin firmware and region... But no matter how i try i get UNABLE TO UNPACK BOOT IMAGE... Instalation failed... why is that? i have TWRP installed... and everything as is your phone firmware and version 9.0.0.162 C432...
Click to expand...
Click to collapse
Flash in bootloader mode. Not in twrp.
Android pie not work with twrp for now.
I am on ROOTED EMUI 8.0 (BKL-L09 8.0.0.130). How do I update to pie and then root? First unroot than update than root? or just update and root with the instructions in post#1?
Sadly it does not work for me. Tried it with your patches bootimage and with my own. Flashing the ramdisk works fine but after restart I don't have root.
I dont need Magisk installed if I use the pre patches bootimage right? Nevertheless I tried with Magisk installed and without. In the Huawei Mate Forum I read that one might need to shutdown the phone after flashing and then to start it with Volume Up and Power Button pressed. But this also does not work. Or any Idea how exactly to start with this Key combination?
Any other suggestions?
Today I updated from OREO with root to PIE same version as you have in pictures 9.0.0.162(C432E4R1P9). Tried both steps (with your patched file and me patching file) to root my phone but even I always got OK in fastboot mode I still have no root
Hello,
Sadly applying the guide does't not work for me to. I tried with the given patched bootimage and with my own one. When flashing the ramdisk image in fastboot mode, i got this error :
"FAILED (remote: partition length get error)".
Please help!
resdano said:
Hello,
Sadly applying the guide does't not work for me to. I tried with the given patched bootimage and with my own one. When flashing the ramdisk image in fastboot mode, i got this error :
"FAILED (remote: partition length get error)".
Please help!
Click to expand...
Click to collapse
I get the same error
any advise ?
Worked like a breeze for me. Shoutout to @ante0 and @shashank1320 who kept their calm in guiding me through and suggesting me this method.
@ante0 made things easier for me and it worked excellently for me. The steps are-
Download and install Magisk canary builds from the mentioned link. Change in Magisk settings the update channel to "custom" inserting*this*URL.*https://t2m.io/wuAFCrwO
Magisk Manager now will find the canary builds.
Check "force encryption" and "AVB 2.0" boxes.
Transfer stock recovery ramdisk to phone, open Magisk Mnager and hit install - > patch boot image, select recovery_ramdisk.img. Take patched_boot.img from /sdcard/Download/ and transfer to computer, reboot to fastboot and flash patched_boot.img to recovery_ramdisk. Unplug USB, holv vol up + power to reboot to recovery, which will now boot phone with Magisk. If you reboot and don't hold vol up it will boot to system without root.
---------- Post added at 02:08 PM ---------- Previous post was at 02:01 PM ----------
Huge thanks @fabio84
Finally have root privileges on Pie.
resdano said:
Hello,
Sadly applying the guide does't not work for me to. I tried with the given patched bootimage and with my own one. When flashing the ramdisk image in fastboot mode, i got this error :
"FAILED (remote: partition length get error)".
Please help!
Click to expand...
Click to collapse
davidsiv said:
I get the same error
any advise ?
Click to expand...
Click to collapse
Emui9 doesn't have a ramdisk partition. You flash to recovery_ramdisk, then when you reboot hold volume up to get to recovery (unplug USB as it will take you to erecovery if you have it plugged in).
This is the only way to get root on Emui9, currently.
It will not boot to recovery, it will boot to system with Magisk.
Not flash ramdisk. Need flash recovery_ramdisk!
worked, thanks
fabio84 said:
Not flash ramdisk. Need flash recovery_ramdisk!
Click to expand...
Click to collapse
@ante0 has been helping me get root access and we still are working on it.
@fabio84 did you by a chance experience issues in using root applications especially root explorer or root Uninstaller? For some reason they won't just work for me, just titanium and root checker works. On further scrutinising, I found the su binary files missing probably why the applications won't load for me. Any help?
ankan1993 said:
@ante0 has been helping me get root access and we still are working on it.
@fabio84 did you by a chance experience issues in using root applications especially root explorer or root Uninstaller? For some reason they won't just work for me, just titanium and root checker works. On further scrutinising, I found the su binary files missing probably why the applications won't load for me. Any help?
Click to expand...
Click to collapse
Update: @ante0 helped me yet again to figure it out. Apparently was because of pie's aggressive background restrictions. Root is now working full fledgedly. Thanks everyone. Big cheers to @ante0
Hello,
It finally worked for me. Thank you so much!
ante0 said:
Emui9 doesn't have a ramdisk partition. You flash to recovery_ramdisk, then when you reboot hold volume up to get to recovery (unplug USB as it will take you to erecovery if you have it plugged in).
This is the only way to get root on Emui9, currently.
It will not boot to recovery, it will boot to system with Magisk.
Click to expand...
Click to collapse
Hi everyone. I have android 9.1.0.132. Trying to root with magisk via twrp, but not working. Anyone did root EMUI 9?
You need to patch your recovery ramdisk image. backup image with twrp or fastboot, patch with magisk manager and flash as recovery (same way you'd flash twrp)
You then need to boot your phone every time via recovery. It'll boot into android as normal but with root.
I don't know how to backup image with fastboot. Im twrp pretoriano80 don't know whitch partition backup. Please some insruction
you need to be bootloader unlocked
here are magisk patched recovery from 9.1.0.134 emui 9 version
next, you need in fastboot "fastboot flash recovery_ramdisk magisk_patched.img" flash it (hope you know how to flash img ??)
then, you need fastboot reboot, remuve usb
this is critical, when you see:
""your device unlocked and cant be trusted
1 pres power to boot
2 pres volume up 3 sec to boot in erecovery
3 dont do anything ... """
when you see this, pres and hold volume up and power button till phone reboot and you see different warning, then relase buttons and wait till phone boots in system
next, instal magisk manager, find in google!
Great dude, awesome, it's working. Sometimes recovery must be flashed again (don't know why is happens). After next restart must flash it again or will be working each time?
THANKS!!!!!!!
Cisuwek said:
Great dude, awesome, it's working. Sometimes recovery must be flashed again (don't know why is happens). After next restart must flash it again or will be working each time?
THANKS!!!!!!!
Click to expand...
Click to collapse
When restarting your phone, make sure you press volume up + power, to boot in recovery. That way you should not have to flash again. If however, you forget to press this combo, your recovery get's replaced with the stock and you'll have to flash it again.
ConsoleHax said:
When restarting your phone, make sure you press volume up + power, to boot in recovery. That way you should not have to flash again. If however, you forget to press this combo, your recovery get's replaced with the stock and you'll have to flash it again.
Click to expand...
Click to collapse
i was thinking that when we use your guide then we do not have twrp installed if we need the stock recovery_ramdisk patched.. so use the erecovery_ramdisk for twrp, also its easyer to enter .. its just to hold the vol+ for 3 sek ... and bum your in twrp..
it works tested it...
ps.
fastboot will not let us flash erecovery_ramdisk so before replacing recovery_ramdisk use twrp to flash the twrp into erecovery_ramdisk ..
then replace recovery_ramdisk with patched img
@brokenworm: could you please explain your ps? I am not really a newbie, but I have no glue, what you talking about?!
oTTo001 said:
@brokenworm: could you please explain your ps? I am not really a newbie, but I have no glue, what you talking about?!
Click to expand...
Click to collapse
Answer is simple ... First fastboot flash recovery_ramdisk TWRP.img .... then enter recovery..
Now from Twrp recovery flash TWRP.img into Erecovery_ramdisk... Now flash the magisk patched recovery_ramdisk either with fastboot or from twrp before exiting into partition recovery_ramdisk.
Erecovery_ramdisk can only be flashed like that becoes fastboot blocks it.
The solution for still having twrp in 9.1 emui roms... Also editing vendor give us the solution to backup and restore a complete nandroid backup. AND this way you do not need to hold a button every time you restart .. from twrp you only need to push reboot recovery to enter the rom ONCE ! AND it will stick .. only "bug" is your phone can not poweroff .. actually good if it gets stolen..
Look here : https://forum.xda-developers.com/hu...w-to-remove-data-encryption-emui-9-1-t3953946
Recovery_ramdisk = vol+ & power.
Erecovery_ramdisk = vol+
Bootloader = vol- & power
This way we dont need to hold a button when rebooting....... twrp fixes that automaticly .. you need to boot in to rom from twrp placed in erecovery_ramdisk by selecting "reboot recovery" instead of "reboot system"... Then it will boot correctly everytime.
And you only have to do this one time.
I have not try but thanks
Hi!
I own an ANE-LX1 device with EMUI9.1
I did everything exactly as described in this or in other threads but I am still unable to root
Just to quickly summarize:
1. my bootloader is unlocked
2. using Magisk app I patched the stock recovery image (recovery_ramdis.img)
3. using fastboot I flashed the patched image
4. now the next step is pretty much unclear for me: reboot the system to what target? all XDA threads (including this one) description at this point sucks! sorry for bad words but this is true
5. anyway tried to reboot to the recovery - this is not possible - I only see exactly the below messages, no matter how long I wait:
Code:
Your device has been unlocked and can't be trusted.
To learn more visit:
http://zh.ui.vmall.com/emotiondownload.php?mod=restore
Your device is booting now...
Tried any possible combination, like disconnect USB cable, keep USB cable, reboot normally, reboot to eRecovery, no matter which one, the result is:
When I check in the Magisk manager app, itt tells: Magisk is not installed.
So please anybody who has successfully rooted, can u make a video showing the whole rooting process, but especially with the step after fastboot flash, i.e. how exactly to reboot, what buttons to press/hold up to the state where the Magisk Manager app shows: Rooted.
I am able to pay for the video! Seriously!!!
PS:
Besides all the description and tutorial it is not clear for me, why should be the system rooted, when we patch only the recovery_ramdisk image/partition. It somehow makes no sense.
I need root for my running EMUI system, and not for the recovery.
Thanks and regards,
Ladislav
Videophile said:
You need to patch your recovery ramdisk image. backup image with twrp or fastboot, patch with magisk manager and flash as recovery (same way you'd flash twrp)
You then need to boot your phone every time via recovery. It'll boot into android as normal but with root.
Click to expand...
Click to collapse
What do you exactly mean by
"You then need to boot your phone every time via recovery."?
Can u pls explain it step by step?
What and how did you do after fastboot flash?
Also see my previous comment...
I have rooted my P20 lite with the steps from this thread. Today my phone notified my that there was a firmware update (from 9.1.0.200 to 9.1.0.208). But I'm stuck in the update process. I can not boot to a recovery to update. Can anyone get me some advice?
Kwakkel said:
I have rooted my P20 lite with the steps from this thread. Today my phone notified my that there was a firmware update (from 9.1.0.200 to 9.1.0.208). But I'm stuck in the update process. I can not boot to a recovery to update. Can anyone get me some advice?
Click to expand...
Click to collapse
With Huawei HiSuite program and the device's fastboot mode you can restore the device.
Once u successfully restored it, can u pls make a video where you show, how did you root your phone and shar it with me?
Kwakkel said:
I have rooted my P20 lite with the steps from this thread. Today my phone notified my that there was a firmware update (from 9.1.0.200 to 9.1.0.208). But I'm stuck in the update process. I can not boot to a recovery to update. Can anyone get me some advice?
Click to expand...
Click to collapse
Before update you need in fastboot flash original recovery, because magisk patched recovery are booting in system with root acces, so you can't update phone while it are rooted
---------- Post added at 12:16 PM ---------- Previous post was at 12:13 PM ----------
ladislav.heller said:
With Huawei HiSuite program and the device's fastboot mode you can restore the device.
Once u successfully restored it, can u pls make a video where you show, how did you root your phone and shar it with me?
Click to expand...
Click to collapse
Hei!
Your phone are bootloader locked or unlocked ?
If you have not bootloader code, aka unlocked bootloader, you can't root phone, because we need patch ramdisk.img with magisk manager and flash it in fastboot using fastboot flash recovery_ramdisk magiskpatchedramdiak.img
Arnys said:
Hei!
Your phone are bootloader locked or unlocked ?
If you have not bootloader code, aka unlocked bootloader, you can't root phone, because we need patch ramdisk.img with magisk manager and flash it in fastboot using fastboot flash recovery_ramdisk magiskpatchedramdiak.img
Click to expand...
Click to collapse
Check the post #11 please. I desribed everything there.
Tapatalkkal küldve az én ANE-LX1 eszközömről
ladislav.heller said:
Check the post #11 please. I desribed everything there.
Tapatalkkal küldve az én ANE-LX1 eszközömről
Click to expand...
Click to collapse
when will be next phone software update i will create video, how i update it, how i root, etc. works for you.?
its like ~40 days, i hope update will come sooner than that!!
Da hell, i can try it now , will flash original, then pach it with magisk ,and then, wait video!
lol, 10 min 1gb video file, i will edit it litle bit, convert etc...
okey. Video redy.
Before you patsch recovery_ramdisk with magisk manager, use thease setings, see picture here : Picture, lol
Chek all 3 boxes in advanced setings! then patch recovery_ramdis.img
video here : youtube (not the best quality, sorry, did it in fast)
my files here : magisk_patched.img for root, RECOVERY_RAMDIS208.img original, to update phone, app-release.apk magisk manager i used
Oh, and buttons i presed after fastboot flash recovery_ramdisk magisk_patched.img is volume up and power!
But, there are BUT, if you previous played with root, and did some strange things, your phone can stuck in huawei logo, if thats happens, you need to restore original software with dload method!!
@ladislav.heller
Arnys said:
when will be next phone software update i will create video, how i update it, how i root, etc. works for you.?
its like ~40 days, i hope update will come sooner than that!!
Da hell, i can try it now , will flash original, then pach it with magisk ,and then, wait video!
lol, 10 min 1gb video file, i will edit it litle bit, convert etc...
okey. Video redy.
Before you patsch recovery_ramdisk with magisk manager, use thease setings, see picture here : Picture, lol
video here : youtube (not the best quality, sorry, did it in fast)
my files here : magisk_patched.img for root, RECOVERY_RAMDIS208.img original, to update phone, app-release.apk magisk manager i used
But, there are BUT, if you previous played with root, and did some strange things, your phone can stuck in huawei logo, if thats happens, you need to restore original software with dload method!!
@ladislav.heller
Click to expand...
Click to collapse
Thank you!!!
Tapatalkkal küldve az én ANE-LX1 eszközömről
Arnys said:
when will be next phone software update i will create video, how i update it, how i root, etc. works for you.?
its like ~40 days, i hope update will come sooner than that!!
Da hell, i can try it now , will flash original, then pach it with magisk ,and then, wait video!
lol, 10 min 1gb video file, i will edit it litle bit, convert etc...
okey. Video redy.
Before you patsch recovery_ramdisk with magisk manager, use thease setings, see picture here : Picture, lol
Chek all 3 boxes in advanced setings! then patch recovery_ramdis.img
video here : youtube (not the best quality, sorry, did it in fast)
my files here : magisk_patched.img for root, RECOVERY_RAMDIS208.img original, to update phone, app-release.apk magisk manager i used
Oh, and buttons i presed after fastboot flash recovery_ramdisk magisk_patched.img is volume up and power!
But, there are BUT, if you previous played with root, and did some strange things, your phone can stuck in huawei logo, if thats happens, you need to restore original software with dload method!!
@ladislav.heller
Click to expand...
Click to collapse
I did exactly what you did in video, but I still can't properly reboot.
When I press Volume Up + Power after flash, the device reboots and stucks at the screen after Huawei logo and I see only the well known:
Code:
Your device is booting now...
message but it never starts the system, at least I did wait 10 minutes and nothing happened, while on your video after reboot with key combination your phone booted into normal system after cca. 1 minute.
I'll try to reflash the whole system via dload method and try again from beginning.
OK, so finally I also was able to root my ANE-LX1.
But it worked only after I reflashed the whole system via dload method.
Many thanks, @Arnys for the tips!