Honor Note 8 B356 Full Rooted Stockrom - Huawei Honor Note 8 ROMs, Kernels, Recoveries, & O

Here is the last Update B356 for Honor Note 8 Android 7 Emui 5.0.1
Full Stock Rom
Boot_Insecure_B356_Fix-adb_dm-verity.img v3 (Spezial Thanks to franzroy from the Mate 8 Forum)
Rooted with Magisk
Busybox
Adblock (is Disable by Default,turn it on yourself if you want)
Integrated Google Apps (Playstore,Play Service,Gmail,Google, Contacts and Calender Sync....
Download
Requirement:
Bootloader Unlocked
Twrp installed
How to install:
Boot into Twrp (I use 3.1.1-1 Open Kirin Twrp)
Format Data with yes
Wipe all in advanced Wipe System,Data,Internal Memory,Dalvik Cache and Cache.
Install the Rom,enjoy
For People was not working Root (Magisk) download the File from Attachment and flash in Recovery (TWRP)​
I do not accept responsibility for Bricked Devices,or any other damage!
Everyone needs to know what he is doing!​

Link mirror error.
---------- Post added at 09:18 PM ---------- Previous post was at 09:17 PM ----------
Now works!!!
Great.

karolingio said:
Link mirror error.
---------- Post added at 09:18 PM ---------- Previous post was at 09:17 PM ----------
Now works!!!
Great.
Click to expand...
Click to collapse
Ok,thanks

Can we install over B353?

Magisk
letschky said:
Ok,thanks
Click to expand...
Click to collapse
Hello,
I install your custom rom and works very well but it is no rooted as default as written in your first post
How can I root it with Magisk ( Magisk manager is already installed )
I saw also that in your zip file(b356) the boot.img as the same size as "boot_insecure_b356...", so I didn't flash it
Am I right ?
Thanks for your help
AD

zorglubzorglub said:
Hello,
I install your custom rom and works very well but it is no rooted as default as written in your first post
How can I root it with Magisk ( Magisk manager is already installed )
I saw also that in your zip file(b356) the boot.img as the same size as "boot_insecure_b356...", so I didn't flash it
Am I right ?
Thanks for your help
AD
Click to expand...
Click to collapse
aha,for me works root with Magisk.
ok you can extract the Rom and in Magisk folder is the Magisk.zip inside.
Copy the Magisk.zip on your SD Card and flash via twrp,i think this fix the issue

coco1476 said:
Can we install over B353?
Click to expand...
Click to collapse
i don´t know,install fresh,fresh install is better,but make a Nandroid Backup and flash the 356 over 353

letschky said:
aha,for me works root with Magisk.
ok you can extract the Rom and in Magisk folder is the Magisk.zip inside.
Copy the Magisk.zip on your SD Card and flash via twrp,i think this fix the issue
Click to expand...
Click to collapse
Hello Letschky,
I use TWRP 3.1.1-1
I tried to install magisk from your custom rom but failed : " boot image patched by othe program, please restore stock boot image" and update process ended with ERROR: 1
The boot image is the one from your custom rom
Could you help me
Best Regards
Alain

zorglubzorglub said:
Hello Letschky,
I use TWRP 3.1.1-1
I tried to install magisk from your custom rom but failed : " boot image patched by othe program, please restore stock boot image" and update process ended with ERROR: 1
The boot image is the one from your custom rom
Could you help me
Best Regards
Alain
Click to expand...
Click to collapse
Before you have the rom installed, you have everything wiped?
Wipe Data with - yes
System,Cache,Dalvik Cache,Data
Reboot again into Recovery
install the rom
for me works without any Problem

letschky said:
Before you have the rom installed, you have everything wiped?
Wipe Data with - yes
System,Cache,Dalvik Cache,Data
Reboot again into Recovery
install the rom
for me works without any Problem
Click to expand...
Click to collapse
****************
Yes I wiped everything the only difference is that I didn't reboot after the WIPE and the INSTALLATION of the ROM
will do it again tonite
Cheers

letschky said:
Before you have the rom installed, you have everything wiped?
Wipe Data with - yes
System,Cache,Dalvik Cache,Data
Reboot again into Recovery
install the rom
for me works without any Problem
Click to expand...
Click to collapse
I did exactly the same as you but without rebooting between all the wipes and the installation of the ROM
Now I did exactly the same as you and I have the same problem : not rooted
during the installation of the rom I saw just after the message "install boot.img" failed to mount /data file exists and and at the end of the installtion "script succeeded result [ E: unknown command [1]]
boot is unlocked

zorglubzorglub said:
I did exactly the same as you but without rebooting between all the wipes and the installation of the ROM
Now I did exactly the same as you and I have the same problem : not rooted
during the installation of the rom I saw just after the message "install boot.img" failed to mount /data file exists and and at the end of the installtion "script succeeded result [ E: unknown command [1]]
boot is unlocked
Click to expand...
Click to collapse
Same for me, but my solution was simple:
1 installed ROM
2 flashed SU via twrp !
That's all folks!
This worked for me.

karolingio said:
Same for me, but my solution was simple:
1 installed ROM
2 flashed SU via twrp !
That's all folks!
This worked for me.
Click to expand...
Click to collapse
Yes I did the same and it works but I wish to test MAGISK but no success
Thanks

zorglubzorglub said:
I did exactly the same as you but without rebooting between all the wipes and the installation of the ROM
Now I did exactly the same as you and I have the same problem : not rooted
during the installation of the rom I saw just after the message "install boot.img" failed to mount /data file exists and and at the end of the installtion "script succeeded result [ E: unknown command [1]]
boot is unlocked
Click to expand...
Click to collapse
the error messages do not matter

but strangely it has just flashed again and it works without problems,
but when it works with supersu also works well

ectract the boot img from tje rom and flash with adb or in twrp and flash the MAGISK.zip again if you want to have MAGISK

Good Afternoon
Loaded B356 last night and for me it works better than the B353 version, seems a lot smoother and I'm loving the magazine covers on my lock screen
Can't get Magisk to work but that does not matter as the phone rooted anyway
I'll carry on road testing and will report back with any issues
Keep up the good work letschky

Hello Letschky.
I've flashed this ROM via TWRP over 356 OTA (it was not completely rooted, it was not possible to mount the /data in TWRP). Wipe and flashing process were successful, but now the reboot to system does not work. The screen is black. ADB can find the device, but it says that the the device is in recovery mode.
Can You please help me.

vimmr said:
Hello Letschky.
I've flashed this ROM via TWRP over 356 OTA (it was not completely rooted, it was not possible to mount the /data in TWRP). Wipe and flashing process were successful, but now the reboot to system does not work. The screen is black. ADB can find the device, but it says that the the device is in recovery mode.
Can You please help me.
Click to expand...
Click to collapse
I advise you to factory reset and reflash the zip that letschky has uploaded
Thats what I did and to be honest its working flawlessly for me, I was previously on B353
On an unrelated side note, can anyone advise if the substratum theme engine works with this ROM
Thanks in advance

Thanks Letschky! I loaded your B356 rom to my honor note 8 last night, looks great.
One issue, the google apps are there, but there is no way to sync the Contacts for Calendar? The option is not there under settings, accounts, google. The option is there for sync app data, sync gmail, sync googlefit, sync people details. But no option for Contacts or Calendar? When I open the phone dialer, there are no contacts!
I loaded the Contacts app from play store, and when I go to add my account it says "the account is already loaded" but still no contacts.
Thanks!
UPDATE: I found this file https://www.apkmirror.com/apk/googl...cts-sync-7-1-2-android-apk-download/download/ and installed it to the phone and now the contacts are appearing in the dialer, but the option to sync contacts is still not appearing in settings, accounts, google.

Related

[RECOVERY][ROOT] TWRP 3.0.2-1 for Samsung Galaxy SM-J710F

This is TWRP 3.0.2-1 ported from official SM-J700 to SM-J710 using stock kernel (zImage) from SM-J710FN, and it fortunately works (atleast to root this thing).
Disclaimer: Flashing this gon' trip knox & you lose your (device's) warranty.
Built from official SM-J700F recovery
Kernel & Device Tree from SM-J710F 6.0.1
No "SEANDROID ***" red warning
Flash via ODIN & enjoy
TWRP: https://www.androidfilehost.com/?fid=24533103863141296
Kernel: https://www.androidfilehost.com/?fid=24533103863141293 (Stock 6.0.1 with disabled dm-verity & encryption)
Note: As per my experiences, it is recommended to flash the Kernel, then recovery, then "FORMAT DATA" (not just wipe) to disable encryption. Otherwise, TWRP will not be able to mount /data.
I flashed this SuperSU in system-less mode & I was rooted with no (visible) issues. Anything else like backing up, I didn't try.
EDIT:
If you want to keep encryption, simply flash recovery & upload SuperSU package via sideload.
EDIT:
Recommended Installation Flow:
Flash TWRP via ODIN
Flash Kernel via ODIN
Reboot to Recovery (TWRP)
Wipe > Format Data > "yes"
Reboot to Recovery (TWRP)
Flash latest SuperSU zip (anything > 2.46)
@vaibhavpandeyvpz
OMG!! you did it :good:
Thank you soo much...
Edit
Cannot boot into recovery mode just gets stuck on Galaxy J7(6) logo?
Disable DM-Verity & Encryption
Prince Chandela said:
@vaibhavpandeyvpz
OMG!! you did it :good:
Thank you soo much...
Edit
Cannot boot into recovery mode just gets stuck on Galaxy J7(6) logo?
Click to expand...
Click to collapse
I, myself have recently met this issue just now. The /data encryption & dm-verity might be causing such issue. Please check updated download links in post to download extracted kernel image from 6.0.1 stock ROM with modifed ramdisk and slightly updated TWRP which now boots fine everytime I try to as of yet.
vaibhavpandeyvpz said:
I, myself have recently met this issue just now. The /data encryption & dm-verity might be causing such issue. Please check updated download links in post to download extracted kernel image from 6.0.1 stock ROM with modifed ramdisk and slightly updated TWRP which now boots fine everytime I try to as of yet.
Click to expand...
Click to collapse
This didn't work i was able to boot in recovery but i can't see files and folders in storage (OTG,Internal,External)
On top of this
DEVICE DOESN'T BOOT now stuck on boot animation
Prince Chandela said:
This didn't work i was able to boot in recovery but i can't see files and folders in storage (OTG,Internal,External)
On top of this
DEVICE DOESN'T BOOT now stuck on boot animation
Click to expand...
Click to collapse
When I was stuck at the bootloader logo, I rebooted to Download mode and did hit Cancel to restart normally.
EDIT:
If you want to restore original recovery, I can provide you with the stock image as well from SM-J710FN.
EDIT:
If you want to root but can't see your files within, you can always sideload.
vaibhavpandeyvpz said:
When I was stuck at the bootloader logo, I rebooted to Download mode and did hit Cancel to restart normally.
EDIT:
If you want to restore original recovery, I can provide you with the stock image as well from SM-J710FN.
EDIT:
If you want to root but can't see your files within, you can always sideload.
Click to expand...
Click to collapse
Please provide me stock recovery and kernel image.
EDIT
i no longer need them. the cause of boot loop was your kernel. I tried to sideload supersu zip but i still can't get rooted this is because twrp can't access /data partition and supersu requires that in system less root.
vaibhavpandeyvpz said:
This is TWRP 3.0.2-1 ported from official SM-J700 to SM-J710 using stock kernel (zImage) from SM-J700FN, and it fortunately works (atleast to root this thing).
Disclaimer: Flashing this gon' trip knox & you lose your (device's) warranty.
Built from official SM-J700F recovery
Kernel & Device Tree from stock 6.0.1 recovery
No "SEANDROID ***" red warning
Flash via ODIN & enjoy
TWRP: https://www.androidfilehost.com/?fid=24533103863141296
Kernel: https://www.androidfilehost.com/?fid=24533103863141293 (Stock 6.0.1 with disabled dm-verity & encryption)
Note: As per my experiences, it is recommended to flash the Kernel, then recovery, then "FORMAT DATA" (not just wipe) to disable encryption. Otherwise, TWRP will not be able to mount /data.
I flashed this SuperSU in system-less mode & I was rooted with no (visible) issues. Anything else like backing up, I didn't try.
EDIT:
If you want to keep encryption, simply flash recovery & upload SuperSU package via sideload.
Click to expand...
Click to collapse
why you don't use j710 kernel and dt image to build it to have fully working twrp ?
messi2050 said:
why you don't use j710 kernel and dt image to build it to have fully working twrp ?
Click to expand...
Click to collapse
It's already using the kernel from the new device, it was a typo. Edited OP.
Prince Chandela said:
Please provide me stock recovery and kernel image.
EDIT
i no longer need them. the cause of boot loop was your kernel. I tried to sideload supersu zip but i still can't get rooted this is because twrp can't access /data partition and supersu requires that in system less root.
Click to expand...
Click to collapse
TWRP cannot access the /data partition because it is encrypted. I did "FORMAT DATA", then rebooted to recovery via TWRP > Reboot > Recovery. Now the TWRP should be able to mount /data and you could install supersu.
vaibhavpandeyvpz said:
TWRP cannot access the /data partition because it is encrypted. I did "FORMAT DATA", then rebooted to recovery via TWRP > Reboot > Recovery. Now the TWRP should be able to mount /data and you could install supersu.
Click to expand...
Click to collapse
But this will wipe all my apps but I'm not using a screen lock nor i setup storage encryption. i don't wanna lose my apps.
Edit:
OP it's mentioned to sideload supersu and it will work with encryption but it didn't
Prince Chandela said:
But this will wipe all my apps but I'm not using a screen lock nor i setup storage encryption. i don't wanna lose my apps.
Click to expand...
Click to collapse
I do understand that it will wipe all the data over the phone. But as per my experiences with S7 & S7E, encryption is enabled by default on Android 6.0 MM. Unless you disable encryption & reformat data, TWRP won't be able to mount /data. The kernel image I posted does not encrypt the /data partition so that you would be able to mount it in TWRP. But after flashing kernel, a FORMAT DATA is required to flush previously encrypted /data. I am sorry, but this is how things seems to work with Android 6.0. Unless TWRP includes support for encrypted partitions, we need to wipe it fully to be able to access it.
vaibhavpandeyvpz said:
I do understand that it will wipe all the data over the phone. But as per my experiences with S7 & S7E, encryption is enabled by default on Android 6.0 MM. Unless you disable encryption & reformat data, TWRP won't be able to mount /data. The kernel image I posted does not encrypt the /data partition so that you would be able to mount it in TWRP. But after flashing kernel, a FORMAT DATA is required to flush previously encrypted /data. I am sorry, but this is how things seems to work with Android 6.0. Unless TWRP includes support for encrypted partitions, we need to wipe it fully to be able to access it.
Click to expand...
Click to collapse
Okay i understand :good:
Is there any way to backup apps with their data without root?
@vaibhavpandeyvpz
I tried to flash kernel then twrp and then wiping /data partition but twrp cannot wipe data partition?
How do I flash this to my device?
@vaibhavpandeyvpz
Any updates?
when iflash Twrp File Via Ordin its fail
ithink becuse secure download is enabled
or fap lock is on ?
help please
isee that massage in download mode (coustom binary(recovery) blocked by fap lock)
thelastbad said:
when iflash Twrp File Via Ordin its fail
ithink becuse secure download is enabled
or fap lock is on ?
help please
isee that massage in download mode (coustom binary(recovery) blocked by fap lock)
Click to expand...
Click to collapse
Table build number 7 times to enable developer option then goto developer option and enable OEM-Unlock
Also follow this thread for further process
Prince Chandela said:
Table build number 7 times to enable developer option then goto developer option and enable OEM-Unlock
Also follow this thread for further process
Click to expand...
Click to collapse
it works now irooted mm thank you ^_^
---------- Post added at 02:16 PM ---------- Previous post was at 02:03 PM ----------
thelastbad said:
it works now irooted mm thank you ^_^
Click to expand...
Click to collapse
are there is root hacks program or wifi hacks?
Is there a root for my j7 2016 sm-j710gn
Sent from my SM-J710GN using XDA-Developers mobile app
Anybody pls help me
I want to root sm-j710gn ,
I try sm-j710f twrp now stcuck logo

TWRP + CM13 Error 7 ?

Hi folks, i am struggling with this issue the last 2 days,
first i kinda bricked my X, i followed this guide to bring it back on
http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
i made all updates available to 3.1.4... i unlocked boot loader, flashed TWRP blu_sp★rk r175 and afterwards tryed to flash latest CM13 nightly
but with no luck, i am always receiving Error 7.. does anyone has a solution to this?
thanks in advance!
Tommyr84 said:
Hi folks, i am struggling with this issue the last 2 days,
first i kinda bricked my X, i followed this guide to bring it back on
http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
i made all updates available to 3.1.4... i unlocked boot loader, flashed TWRP blu_sp★rk r175 and afterwards tryed to flash latest CM13 nightly
but with no luck, i am always receiving Error 7.. does anyone has a solution to this?
thanks in advance!
Click to expand...
Click to collapse
There's no blu spark kernel for ROMs/OOS with updated bootloader . Not sure if that's what causing the error 7 but its a start. Try using. Sultans uodated twrp I don't have any issues with it.
Exodusche said:
There's no blu spark kernel for ROMs/OOS with updated bootloader . Not sure if that's what causing the error 7 but its a start. Try using. Sultans uodated twrp I don't have any issues with it.
Click to expand...
Click to collapse
hmmm.. ok, i will give it a try! Thanks, i will tell if this works out
Tommyr84 said:
hmmm.. ok, i will give it a try! Thanks, i will tell if this works out
Click to expand...
Click to collapse
V175 is a kernel
You certainly flashed BS TWRP V41.
Kéno40 said:
V175 is a kernel
You certainly flashed BS TWRP V41.
Click to expand...
Click to collapse
so i tried sultans TWRP (Sultan-TWRP-onyx-3.0.2-3_2016-10-23)... also flashed SuperSU.. worked like a charm!
But when i am trying to flash CM13 (cm-13.0-20161122-NIGHTLY-onyx) i still get Error 7 ...
You tried to flash TWRP for CM13 sultan rom ?
Tommyr84 said:
so i tried sultans TWRP (Sultan-TWRP-onyx-3.0.2-3_2016-10-23)... also flashed SuperSU.. worked like a charm!
But when i am trying to flash CM13 (cm-13.0-20161122-NIGHTLY-onyx) i still get Error 7 ...
Click to expand...
Click to collapse
Flash twrp from here
http://forum.xda-developers.com/one...al-twrp-3-0-2-0-recovery-onyx-t3471584/page10
Fap4k said:
Flash twrp from here
http://forum.xda-developers.com/one...al-twrp-3-0-2-0-recovery-onyx-t3471584/page10
Click to expand...
Click to collapse
ok, i flashed this Twrp version, same error ! Error : 7 Error installing zip file
i realy don't know which point i am missing, i downloaded the CM13 nightly fresh from the official side...
i can't be the only one who is facing this error
Update the Boot-loader first, you can follow a post found in home page of opx, u still have to use another TWRP recovery (not official) after updating bootloader. U vil get all info in the thread.
raj.ify said:
Update the Boot-loader first, you can follow a post found in home page of opx, u still have to use another TWRP recovery (not official) after updating bootloader. U vil get all info in the thread.
Click to expand...
Click to collapse
Hi, according to your post, i followed this description http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
flashed "OPXBLUpdateOOS3.1" and new TWPR afterwards "twrp-3.0.2-2_blu_spark.v41-onyx_by-engstk.img" with no error!
rebooted into recovery, tried to install "cm-13.0-20161204-NIGHTLY-onyx" ... and guess what?! ERROR 7 again!
so i am defenetly on new bootloader, i tried all 3 options from the threat above (flashed via ADB and via SD card) no problem! also got bootloader unlocked info form ADB.
everything works, till i try to flash a CM image... then i receive ERROR 7 ;(
Hey There,
I`m stuck with the same Error.
The only Recovery i can boot ist the normal TWRP Recovery.
The blu Spark TWRP Recovery, the Stock Recovery and the CM13 Nighty Onyx Recovery wont work. I get the fastboot DTB not found Error.
And I cant install any custom ROM. I Always get the Error 7, ZIP could not be installed from Z://
If i erase the Assets it boots directly in to Bootloader (without saying Fastboot Mode on the screen, but with the OnePlus Logo).
If I flash one of the CM14 versions it gives no error 7 but boots into the Bootloader as well.
I have no custom kernel installed.
My plan was to flash the CM13 Nighty Onyx Recovery but I cant get around the DTB error,
Thanks for Help.
Greetings Clon
EDIT:
I tied the BL Update from the mentioned thread above.
aaaaand: Error 7
Here is my complete error:
Code:
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
[COLOR="Red"]Updater ended with ERROR: 7
Error installing zip file '/sdcard/ROMs/cm-13.0-20161122-NIGHTLY-onyx.zip'[/COLOR]
---------- Post added at 05:33 PM ---------- Previous post was at 04:56 PM ----------
Okay I have a Solution, but I dont know how I did it.
This is what I made.
1. I did a factory reset.
2. I did a factory reset. (Why not tho)
3. I restarted the recovery.
4. I did a factory reset.
5. I changed the filesystem for data partition. (It was on ext4, but I changed it to ext4 although to get Errors out or something like that.
6. I rebooted into Bootloader.
7. I flashed and booted this recovery: http://forum.xda-developers.com/devdb/project/dl/?id=20236&task=get (and got no dtb error. yay!)
8. I installed the nightly CM, and the latest gapps (and i got no error 7. yay!)
I know its a bit random but i think the error has to do something with the data partition and the filesystem....
Void your warranty!

Again on recovery, root, etc.

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?

Step-by-step Rooting Guide with SuperSU for MI 8

I wanted to make sure everyone read this part first so that you know it's critical to backup because it happened to me figuring things out. If for any reason you are stuck in a boot loop, just reload twrp recovery and restore boot.img that you backed up for an easy quick fix.
Install drivers and adb on your PC.
Open command prompt or search 'cmd'.
Navigate to the directory with adb.exe
Download and store TWRP 2.2.2 (preferred) in the same directory where adb is located. Recommend renaming recovery file to recovery.img
Enable usb debugging on device by going to settings > about > and click on MIUI version repeatedly until developer settings are enabled. Go back and select additional settings to enable usb debugging.
Run the command: adb devices - to verify if able to connect to device (the serial number of your device will populate if so.
Run the command: adb reboot bootloader and phone device should say "Fastboot" in blue font
Run the command: fastboot boot recovery.img
Recovery will show in Chinese, click on the bottom right button to select English
May require to enter your default password you use to unlock your phone normally.
Click backup and be sure to backup system, boot, and recovery most of all so it's easy to recover your device moving forward.
Download and save SuperSU (I have been unsuccessful in getting Magisk to work at this time) onto storage device from PC to MI 8 that should appear with your Internal storage
Click on "Mount" in TWRP and unselect read-only
Click "Install" and flash SuperSU then reboot (my device rebooted one time and fully boot up the 2nd time so you're not alarmed)
Links:
SuperSU: https://download.chainfire.eu/1122/SuperSU/SR3-SuperSU-v2.82-SR3-20170813133244.zip?retrieve_file=1
TWRP: https://forum.xda-developers.com/mi-8/development/recovery-twrp-3-2-2-0703-t38126005
Appreciate any feedback, ideas, thoughts, or suggestions where all can collaborate and expand where we help each other further. Look forward to the future development of the MI 8 folks! Please note, I wanted to share the method that seemed to work best for me, but please be aware each and every single MI 8 device is not always exactly the same and the end result may vary and I'm not held accountable or responsible should you choose to follow the directions listed above. However, I wanted to share this information to help avoid any frustration going forward and save you time.
p.s. - If someone could help me figure out how to get twrp recovery to hold and not end up being replaced by mi recovery I would be most grateful as this has been an issue for me (I tried flashing, booting, and installing the img through twrp with no success). Thank you.
Hello thanks for your guide but i think we first need to unlock bl And for the twrp recovery to stick and not to be replaced by xiaomi recovery we need to flash something called "dm-verity " it basically removes that check, which replaces any other recovery by xiaomi recovery
Have a nice day and thanks for your work
I thought so as well, unfortunately I just haven't had much luck with dm verity which led to a soft brick on my device. I'll have to look over the code as it may vary in comparison to other xiaomi devices.
Sent from my MI 8 using Tapatalk
Fastboot flash recovery Command should do it ..
mekaziah said:
I wanted to make sure everyone read this part first so that you know it's critical to backup because it happened to me figuring things out. If for any reason you are stuck in a boot loop, just reload twrp recovery and restore boot.img that you backed up for an easy quick fix.
Install drivers and adb on your PC.
Open command prompt or search 'cmd'.
Navigate to the directory with adb.exe
Download and store TWRP 2.2.2 (preferred) in the same directory where adb is located. Recommend renaming recovery file to recovery.img
Enable usb debugging on device by going to settings > about > and click on MIUI version repeatedly until developer settings are enabled. Go back and select additional settings to enable usb debugging.
Run the command: adb devices - to verify if able to connect to device (the serial number of your device will populate if so.
Run the command: adb reboot bootloader and phone device should say "Fastboot" in blue font
Run the command: fastboot boot recovery.img
Recovery will show in Chinese, click on the bottom right button to select English
May require to enter your default password you use to unlock your phone normally.
Click backup and be sure to backup system, boot, and recovery most of all so it's easy to recover your device moving forward.
Download and save SuperSU (I have been unsuccessful in getting Magisk to work at this time) onto storage device from PC to MI 8 that should appear with your Internal storage
Click on "Mount" in TWRP and unselect read-only
Click "Install" and flash SuperSU then reboot (my device rebooted one time and fully boot up the 2nd time so you're not alarmed)
Links:
SuperSU: https://download.chainfire.eu/1122/SuperSU/SR3-SuperSU-v2.82-SR3-20170813133244.zip?retrieve_file=1
TWRP: https://forum.xda-developers.com/mi-8/development/recovery-twrp-3-2-2-0703-t38126005
Appreciate any feedback, ideas, thoughts, or suggestions where all can collaborate and expand where we help each other further. Look forward to the future development of the MI 8 folks! Please note, I wanted to share the method that seemed to work best for me, but please be aware each and every single MI 8 device is not always exactly the same and the end result may vary and I'm not held accountable or responsible should you choose to follow the directions listed above. However, I wanted to share this information to help avoid any frustration going forward and save you time.
p.s. - If someone could help me figure out how to get twrp recovery to hold and not end up being replaced by mi recovery I would be most grateful as this has been an issue for me (I tried flashing, booting, and installing the img through twrp with no success). Thank you.
Click to expand...
Click to collapse
Skickat från min MI 8 via Tapatalk
what issues do you get with magisk? I was able to flash it without any issues.
superior8888 said:
Fastboot flash recovery Command should do it ..
Skickat från min MI 8 via Tapatalk
Click to expand...
Click to collapse
Yes it does. Don't know why anyone would run SuperSU though.
mekaziah said:
I thought so as well, unfortunately I just haven't had much luck with dm verity which led to a soft brick on my device. I'll have to look over the code as it may vary in comparison to other xiaomi devices.
Click to expand...
Click to collapse
MAKE SURE U HAVE UNLOCKED BOOTLOADER
here is wat i do
first i boot into twrp
(make sure u have rom.zip magisk/superuser.zip an twrp.img) on internal storage
then i wipe
dalvik cache
cache
data (NOT FORMAT)
system
then i flash
rom.zip
twrp.img
then i reboot recovery
fkash magisk.zip
then reboot system
now i have new rom an still have twrp on
-fluffy- said:
here is wat i do
first i boot into twrp
(make sure u have rom.zip magisk/superuser.zip an twrp.img) on internal storage
then i wipe
dalvik cache
cache
data (NOT FORMAT)
system
then i flash
rom.zip
twrp.img
then i reboot recovery
fkash magisk.zip
then reboot system
now i have new rom an still have twrp on
Click to expand...
Click to collapse
Would you mind stating the version of Magisk?
Strange Guide no Attention for Unlok Bl.
barrielui said:
Would you mind stating the version of Magisk?
Click to expand...
Click to collapse
16.4
magisk has been working fine for me for a while
samwise110712 said:
what issues do you get with magisk? I was able to flash it without any issues.
Click to expand...
Click to collapse
What's your ROM version? I flash twrp then magisk, bootloop...
-fluffy- said:
MAKE SURE U HAVE UNLOCKED BOOTLOADER
here is wat i do
first i boot into twrp
(make sure u have rom.zip magisk/superuser.zip an twrp.img) on internal storage
then i wipe
dalvik cache
cache
data (NOT FORMAT)
system
then i flash
rom.zip
twrp.img
then i reboot recovery
fkash magisk.zip
then reboot system
now i have new rom an still have twrp on
Click to expand...
Click to collapse
Hello how did you flash the TWRP through the TWRP ???
What version of MiUi you have ???
omek07 said:
Hello how did you flash the TWRP through the TWRP ???
What version of MiUi you have ???
Click to expand...
Click to collapse
simple put twrp.img on ur storage
then flash img from twrp
-fluffy- said:
simple put twrp.img on ur storage
then flash img from twrp
Click to expand...
Click to collapse
Yes but its asking after in which partition.
What partition you chose ?
---------- Post added at 08:26 AM ---------- Previous post was at 07:41 AM ----------
-fluffy- said:
simple put twrp.img on ur storage
then flash img from twrp
Click to expand...
Click to collapse
Could you please tell me what rom you have ???
Thank you
omek07 said:
Yes but its asking after in which partition.
What partition you chose ?
---------- Post added at 08:26 AM ---------- Previous post was at 07:41 AM ----------
Could you please tell me what rom you have ???
Thank you
Click to expand...
Click to collapse
u choose recovery
im using miui eu
magisk is running without any issue.
i am on the newest xiaomi eu beta rom and flashed magisk 16.7 without any issue right now
(after waiting horrible 15 days for unlocking the bootloader)
Ok so both of you have the xiaomi eu. I have global stable 9.5.11. so maybe that's the problem
---------- Post added at 06:30 AM ---------- Previous post was at 06:29 AM ----------
So both of you have xiaomi eu rom. I have global stable 9.5.11. maybe that's the problem.
omek07 said:
Ok so both of you have the xiaomi eu. I have global stable 9.5.11. so maybe that's the problem
---------- Post added at 06:30 AM ---------- Previous post was at 06:29 AM ----------
So both of you have xiaomi eu rom. I have global stable 9.5.11. maybe that's the problem.
Click to expand...
Click to collapse
I have the lastest global version, I cannot get the root access...
Someone tell me flash the Chinese verision then flash xiaomi.eu and magisk.
felixrao said:
I have the lastest global version, I cannot get the root access...
Someone tell me flash the Chinese verision then flash xiaomi.eu and magisk.
Click to expand...
Click to collapse
My friend i changed to the Xiaomi eu and everything worked. You dont have to flash the Chinese Version first you can go from Global to Xiaomi.eu. Just dont forget to do FORMAT data and not only Wipe Data.

Is there a custom rom for the HUAWEI P30 lite?

Hey guys,
I want to buy a new phone for around 200€, while searching for a good one my eyes fell on the HUAWEI P30 lite.
But I would like to use the phone for a longer time, so here's my question:
"Does anybody know if theres a working custom rom for the HUAWEI P30 lite?"
I've allready looked up on the webpages of DitryUnicorny, LineageOS, Pixel expirience,... also here I couldn't find a rom, or even a unofficial version,
so if anybody knows more about it, or knows a phone about 200 with "rom compatibility" let me know about it .
Thx
did yu find any custom rom for P30 Lite ?
only EMUI9.0 support custom roms
Check this https://forum.xda-developers.com/t/huawei-p30-lite-root.3954205/post-85181981
trying to keep ths device alive.
I want to get a working TWRP for this device, pbbly soon, if everything works I will try and get a custom ROM done as well.
blzbh said:
Check this https://forum.xda-developers.com/t/huawei-p30-lite-root.3954205/post-85181981
trying to keep ths device alive.
I want to get a working TWRP for this device, pbbly soon, if everything works I will try and get a custom ROM done as well.
Click to expand...
Click to collapse
hi at the other forum i read that you got root working on huawei p30 lite but i am having trouble getting it rooted. i have unloced bootloader and now i am stuck because when i download magisk i need boot.img to modify and get root. any help would be awesome
NacoRaco said:
hi at the other forum i read that you got root working on huawei p30 lite but i am having trouble getting it rooted. i have unloced bootloader and now i am stuck because when i download magisk i need boot.img to modify and get root. any help would be awesome
Click to expand...
Click to collapse
Hi there mate.. do you have TWRP running?
The only image that works is TWRP Recovery 3.2.1.0 (HiSilicon Kirin 710).
You can flash that to recovery **make sure to disable password protection, face recognition or any other locking mechanism before doing so**
Then from TWRP install magisk zip using the install option
tnx for the replay. so the problem is that i found a post that that version of twrp should work and its supposed to be https://www.androidweblog.com/huawei-p30-lite-root-install-twrp-recovery/ but their linked twrp doesn't work and it just redirects you to illegal copy of JNews and you cant download it. If you have an url to the twrp than that would be awesome. but i did get twrp but i think it was for Huawei Y9 and everything was encrypted and it couldn't mount a bunch of stuff so it couldn't install magisk but i did successfully install lineage os but all files were encrypted so it wasn't usable. Tnx again for all the help and your time.
blzbh said:
Hi there mate.. do you have TWRP running?
The only image that works is TWRP Recovery 3.2.1.0 (HiSilicon Kirin 710).
You can flash that to recovery **make sure to disable password protection, face recognition or any other locking mechanism before doing so**
Then from TWRP install magisk zip using the install option
Click to expand...
Click to collapse
thank you for your time above i wrote my problem
That should be the one.. Y9 Uses twrp 3.2.1.0 for Kirin 710... If You have troubles with encryption you can reformat the data partition .. that worked for me... or factory reset and without running initial setup boot TWRP... there are a few tips around the forum for this..
blzbh said:
That should be the one.. Y9 Uses twrp 3.2.1.0 for Kirin 710... If You have troubles with encryption you can reformat the data partition .. that worked for me... or factory reset and without running initial setup boot TWRP... there are a few tips around the forum for this..
Click to expand...
Click to collapse
So i installed twrp and i tried to format data and factory reset and delete data partition and i install twrp and when i get to the setup screen phone gives warning your phone is rooted but there is no magisk and if i install app it says its N/A. all the data is decrypted on the phone and i have no idea how to enable root. when i flash magisk it says failed to mount /cust, /product, /system, /vendor, /version, /odm. and if i go to twrp again data is encrypted and i didn't set any lock up on setup. Thank you for all your help. you can add me on discord Naco_Raco#3100
NacoRaco said:
So i installed twrp and i tried to format data and factory reset and delete data partition and i install twrp and when i get to the setup screen phone gives warning your phone is rooted but there is no magisk and if i install app it says its N/A. all the data is decrypted on the phone and i have no idea how to enable root. when i flash magisk it says failed to mount /cust, /product, /system, /vendor, /version, /odm. and if i go to twrp again data is encrypted and i didn't set any lock up on setup. Thank you for all your help. you can add me on discord Naco_Raco#3100
Click to expand...
Click to collapse
Have you cleared the dalvik cache??
Please try that first, then in twrp shell run: mount -o remount,rw <partition>
Just change partition to the actual name in the errors.. /system /product etc...
Then flash magisk.
Usually at this point if you get the data partition re-encrypted you can re format the partition to get access again...
blzbh said:
Have you cleared the dalvik cache??
Please try that first, then in twrp shell run: mount -o remount,rw <partition>
Just change partition to the actual name in the errors.. /system /product etc...
Then flash magisk.
Usually at this point if you get the data partition re-encrypted you can re format the partition to get access again...
Click to expand...
Click to collapse
unfortunately it did not work. I filmed it again and posted on YouTube and it might help you find a problem. P.S before i filmed the video i cleared delvik and cache after installing magisk and it still didn't work. If you still have that twrp that worked for you could you send it over and i can try with that file?

Categories

Resources