Hi folks
When I get back the device from Huawei services, I receive a boot.img without encryption that let me able to backup and restore the firmware hundred times without errors .
In this tutorial I'll show you how to do that without need to bring the phone to Huawei services to reset the software, starting from now can be done as well.
Requirements:
Unlocked bootloader, you know how to do that.
My own TWRP, that authorized Huawei store told should use my own TWRP to restore the phone, so get it from here by downloading the latest version.
Stock firmware, click here to download it, it's for single sim only.
Stock IMGS that needed for decrypt and to re-enable the encryption once firmware has been done with restoration, click here to download them.
7 zip to unpack the tar.gz.
Code:
[CENTER][COLOR="Red"][SIZE="4"][FONT="Comic Sans MS"]Please read the steps carefully because I'm not going to repeat them for each user, thanks[/FONT][/SIZE][/COLOR][/CENTER]
Reset Steps:
Download the C432B161.
Unpack the .tar.gz archive with 7 zip.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Rename from C432B161 to TWRP.
Copy to the Internal Storage.
Reboot to TWRP Recovery by the following command.
in the IMGS archive you will find a bootimage called boot.img, rename it to boot.emmc.win and copy to TWRP->BACKUPS->57UDU17709001769->2017-10-18--12-03-00_NRD90M_test-keys -> replace it and then follow the video
Go to the TWRP.
Wipe everything except the external_sd (the path where you copy the backup)
Tab on Restore.
Choose the copied backup make sure to rename from C432B161 to TWRP to match.
Select all partitions.
Swipe the screen and wait until finish.
Reboot to bootloader once done.
In the IMGS.tar.gz there is a file caller boot.img flash via fastboot as boot and will get booted like charm
Warning:
You are not allowed to copy or steal the files of my guide without ask my permissions.
Because I take almost week to upload the firmware after many times of failing upload.
Mention this guide for who looking helps to restore this device.
If I saw any piece of my contents in other threads, I'll report as abuse and ask a moderator to close his thread because I already saw someone rename my recovery and put it inside his thread without asking permission. that's all.
This guide could be helpful for who want to debrand his device, so we need tester.
to enable dual sim: you must flash an oeminfo partition from dual sim firmware.
Happy restoring.
Can I change from dualsim to monosim with this guide?
Wire1122 said:
Can I change from dualsim to monosim with this guide?
Click to expand...
Click to collapse
to be honest, I can't confirm since is the full backup from my single device.
in case dual sim still appear even after restore, you have to flash the single sim oeminfo partition.
when I must flash oeminfo?
Wire1122 said:
when I must flash oeminfo?
Click to expand...
Click to collapse
post firmware restoring
Wire1122 said:
when I must flash oeminfo?
Click to expand...
Click to collapse
not works to me. Pralx1c432b182 such before restoring
Wire112233 said:
not works to me. Pralx1c432b182 such before restoring
Click to expand...
Click to collapse
whats not work restoring firmware or converting from dual to single?
haky 86 said:
whats not work restoring firmware or converting from dual to single?
Click to expand...
Click to collapse
converting from dual to single. But after restoring the fw remains b182, not 161
Wire112233 said:
converting from dual to single. But after restoring the fw remains b182, not 161
Click to expand...
Click to collapse
yup because some partitions is upgraded to b182 (dual sim), same thing happen to me b181 (single sim). for converting to single sim, I'll upload the oeminfo partition soon.
Note: this operation might will lock bootloader/frp automatically, so I recommend to check them via fastboot mod.
When oeminfo?
Sent from my HUAWEI PRA-LX1 using XDA Labs
Looks like the images gone bad, and now point:
Wipe the following partitions like in the screenshot.
Click to expand...
Click to collapse
can be quite challenging
Wiped cache/data/system and restored everything that I was allowed to from your backup.
Meanwhile I changed name of directory: TWRP\BACKUPS\57UDU17709001769\2017-10-18--12-03-00_NRD90M_test-keys to
TWRP\BACKUPS\9DC7N17A17006059\2017-10-18--12-03-00_NRD90M_test-keys in order to make the backup visible in TWRP Restore menu.
(Hope that didn't change anything?)
Then I completed your "Reset Steps" tutorial, reboot and [...]
that hilarious green screen is still in place of previous Huawei:
After initial configuration my first impression was that I downloaded wrong backup, cause it looks more like the Elite ROM V6 (5 icons at bottom-screen menu, google searchbar, additional options (4 rows instead of 2) in upper-scroll menu and the pinkish-purple wallpaper) even the blinking NFC problem I had with that ROM is present there, but yet it's not that one. All informations in settings>about phone are from your backup, I even checked if the Android Studio will find my phone - and it did! That was unavaible in HassanMirza01's ROM.
So there's my question - does it suppose to look that way? Or I just messed something really hard and the visual theme files from previous OS's stayed somehow on my phone?
Don't take me wrong - after this tutorial I ended up with fully functional, nice looking (as soon as I change the pinkish wallpaper...) smartphone, so I'm really happy thanks to you!
Anyway I found it also interesting how the GreenScreen could ended up in such a place, so I'll try to figure that out.
Sixter said:
Looks like the images gone bad, and now point:
can be quite challenging
Wiped cache/data/system and restored everything that I was allowed to from your backup.
Meanwhile I changed name of directory: TWRP\BACKUPS\57UDU17709001769\2017-10-18--12-03-00_NRD90M_test-keys to
TWRP\BACKUPS\9DC7N17A17006059\2017-10-18--12-03-00_NRD90M_test-keys in order to make the backup visible in TWRP Restore menu.
(Hope that didn't change anything?)
Then I completed your "Reset Steps" tutorial, reboot and [...]
that hilarious green screen is still in place of previous Huawei:
After initial configuration my first impression was that I downloaded wrong backup, cause it looks more like the Elite ROM V6 (5 icons at bottom-screen menu, google searchbar, additional options (4 rows instead of 2) in upper-scroll menu and the pinkish-purple wallpaper) even the blinking NFC problem I had with that ROM is present there, but yet it's not that one. All informations in settings>about phone are from your backup, I even checked if the Android Studio will find my phone - and it did! That was unavaible in HassanMirza01's ROM.
So there's my question - does it suppose to look that way? Or I just messed something really hard and the visual theme files from previous OS's stayed somehow on my phone?
Don't take me wrong - after this tutorial I ended up with fully functional, nice looking (as soon as I change the pinkish wallpaper...) smartphone, so I'm really happy thanks to you!
Anyway I found it also interesting how the GreenScreen could ended up in such a place, so I'll try to figure that out.
Click to expand...
Click to collapse
might the elite rom v6 cause that issue, try to restore it again perhaps it will gone..I didn't get that green and red screen
Hey, any have oeminfo for single sim fw? its impossible to find
http://www.mediafire.com/file/0tnrmliuudsz9qo/OemInfo_EU_SS.zip
https://mega.nz/#F!0xcUWCBZ!FAXGLF3WC_uFsc5r--BqEQ
Wire1122 said:
http://www.mediafire.com/file/0tnrmliuudsz9qo/OemInfo_EU_SS.zip
https://mega.nz/#F!0xcUWCBZ!FAXGLF3WC_uFsc5r--BqEQ
Click to expand...
Click to collapse
Thanks for the help! For what version is this oem? (b161?)
dannyzamora said:
Thanks for the help! For what version is this oem? (b161?)
Click to expand...
Click to collapse
I don't know Sorry It is monosim c432
Wire1122 said:
I don't know Sorry It is monosim c432
Click to expand...
Click to collapse
Thx! One question... I have now installed b182, can i "downgrade" installing the b161 twrp backup with the tutorial and later install this oem?
Enviado desde mi PRA-LX1 mediante Tapatalk
dannyzamora said:
Thx! One question... I have now installed b182, can i "downgrade" installing the b161 twrp backup with the tutorial and later install this oem?
Enviado desde mi PRA-LX1 mediante Tapatalk
Click to expand...
Click to collapse
even if downgraded will keep on b182 because some partitions will not downgraded since my twrp is designed to backup/restore only necessary partitions for fully worked firmware.
I also had to rename TWRP\BACKUPS\57UDU17709001769\2017-10-18--12-03-00_NRD90M_test-keys to
TWRP\BACKUPS\<my device ID visible in adb devices>\2017-10-18--12-03-00_NRD90M_test-keys in order to make the backup visible in TWRP Restore menu, thanks @Sixter. Please update the first page accordingly.
But even doing so, when coming to Huawei eRecovery I'm still stuck with "Getting package info failed" issue, I cannot get back EMUI yet. Any hint?
bagage said:
I also had to rename TWRP\BACKUPS\57UDU17709001769\2017-10-18--12-03-00_NRD90M_test-keys to
TWRP\BACKUPS\<my device ID visible in adb devices>\2017-10-18--12-03-00_NRD90M_test-keys in order to make the backup visible in TWRP Restore menu, thanks @Sixter. Please update the first page accordingly.
But even doing so, when coming to Huawei eRecovery I'm still stuck with "Getting package info failed" issue, I cannot get back EMUI yet. Any hint?
Click to expand...
Click to collapse
You might want to try the Recovery MITM approach but its a tad more complicated. https://forum.xda-developers.com/p8lite/p8-lite-2017-discussion/guide-local-recovery-server-t3714900
Related
Hey guys, I have an XT1064 US GSM Moto G.
I followed the tutorial here and flashed the appropriate image to restore the phone to stock: http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
Now, my wifi no longer works no matter what I do.
I have tried deleting the wpa_supplicant.conf file, flashing a different kernel, rebooting without the sim, and wifi will not turn on no matter what. As soon as I slide it on the button snaps back to the off position
Some help would be very much appreciated!! Thanks!
EDIT: Also, every line of flashing has returned [OKAY], and I've run the phone with stock recovery, CWM, and TWRP and no difference
Is it possible I have to relock my bootloader? I don't see how that would affect it but im not an expert
I have the exact same problem... But my device is a XT1069.
Still waiting for a solution... :/
Bl00dyMurd3r said:
Hey guys, I have an XT1064 US GSM Moto G.
I followed the tutorial here and flashed the appropriate image to restore the phone to stock: http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
Now, my wifi no longer works no matter what I do.
I have tried deleting the wpa_supplicant.conf file, flashing a different kernel, rebooting without the sim, and wifi will not turn on no matter what. As soon as I slide it on the button snaps back to the off position
Some help would be very much appreciated!! Thanks!
EDIT: Also, every line of flashing has returned [OKAY], and I've run the phone with stock recovery, CWM, and TWRP and no difference
Is it possible I have to relock my bootloader? I don't see how that would affect it but im not an expert
Click to expand...
Click to collapse
Did you download your XT1064 firmware from here:
http://sbf.droid-developers.org/phone.php?device=36
We are not supposed to install XT1069 firmware on XT1064
rafaelbrunner said:
I have the exact same problem... But my device is a XT1069.
Still waiting for a solution... :/
Click to expand...
Click to collapse
me too xt1068
Thanks for the link, but i did not flash XT1069 firmware, I followed the guide steps to flash "Blur_Version.21.11.17.titan_retuaws.retuaws.en.US" as I have the US gsm model
This will only happen if you updated the phone with latest OTA, you can't downgrade the bootloader, if you apply the latest OTA the problem should be solved.
MiguelPT said:
This will only happen if you updated the phone with latest OTA, you can't downgrade the bootloader, if you apply the latest OTA the problem should be solved.
Click to expand...
Click to collapse
I tried applying the update from this thread from the stock recovery: http://forum.xda-developers.com/moto-g-2014/general/ota-update-t2880432
The recovery starts to verify the package and then I get "Installation aborted."
It does this with both locked and unlocked bootloader
Any other help would be great, thanks!
Bl00dyMurd3r said:
I tried applying the update from this thread from the stock recovery: http://forum.xda-developers.com/moto-g-2014/general/ota-update-t2880432
The recovery starts to verify the package and then I get "Installation aborted."
It does this with both locked and unlocked bootloader
Any other help would be great, thanks!
Click to expand...
Click to collapse
According to Q18 from this page you need to select full unroot option from the Super Su:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then follow the "[Restore to Stock][XT1068][All Dual Sim Model][4.4.4][Lock Bootloader]" and use XT1064 firmware just to see if your wifi works or not.
pleomaxell said:
According to Q18 from this page you need to select full unroot option from the Super Su:
Then follow the "[Restore to Stock][XT1068][All Dual Sim Model][4.4.4][Lock Bootloader]" and use XT1064 firmware just to see if your wifi works or not.
Click to expand...
Click to collapse
Thanks, I'll give it a shot!
Well, tried that and no luck. This is my 3rd android device and I've never heard of Wifi being borked like this
Bl00dyMurd3r said:
Well, tried that and no luck. This is my 3rd android device and I've never heard of Wifi being borked like this
Click to expand...
Click to collapse
Sorry, I don't know what to suggest, it looks like another user was facing a similar problem and no one could provide a solution to him too.
Can't you return the phone and get it replaced?
pleomaxell said:
Sorry, I don't know what to suggest, it looks like another user was facing a similar problem and no one could provide a solution to him too.
Can't you return the phone and get it replaced?
Click to expand...
Click to collapse
It looks like I'll have to. Amazon customer service is top notch, but I'll have to flash over the unlocked bootloader warning and then relock it, hopefully all bases will be covered
Bl00dyMurd3r said:
It looks like I'll have to. Amazon customer service is top notch, but I'll have to flash over the unlocked bootloader warning and then relock it, hopefully all bases will be covered
Click to expand...
Click to collapse
I had no success in re-locking my device's bootloader...
Did you have any luck with that?
rafaelbrunner said:
I had no success in re-locking my device's bootloader...
Did you have any luck with that?
Click to expand...
Click to collapse
Yes, on my 1064 i issued these commands while on the bootloader:
mfastboot.exe oem lock begin
mfastboot.exe oem lock
It returned a [FAILED] in cmd, but after reboot the bootloader reported it was indeed locked. The unlocked bootloader warning still appeared however, but the logo fix could probably be applied prior to re-locking
Bl00dyMurd3r said:
Yes, on my 1064 i issued these commands while on the bootloader:
mfastboot.exe oem lock begin
mfastboot.exe oem lock
It returned a [FAILED] in cmd, but after reboot the bootloader reported it was indeed locked. The unlocked bootloader warning still appeared however, but the logo fix could probably be applied prior to re-locking
Click to expand...
Click to collapse
me the saame....i think there isnt solution.....:crying:
WIFI fix
Hi Guys,
Cause of problem: I formated partition /persist on my moto G. I am stupid, I know. Unfortunately this partition is untouched by any flashes you will do, so you you can flash any Roms or factory images, Wifi will not work.
Here's how to fix it (you MUST be rooted):
1. ROOT your phone
2. download this http://forum.xda-developers.com/attachment.php?attachmentid=2531514&d=1390364984
3. download Root explorer from play store
4. download Rar archiver from play store
5. then unrar downloaded file
6. copy the unrared file from /storage/sdcard0/download to /persist with root explorer
7. reboot and your WiFi should work.
Simple thanks is enough
linasmit said:
Hi Guys,
Cause of problem: I formated partition /persist on my moto G. I am stupid, I know. Unfortunately this partition is untouched by any flashes you will do, so you you can flash any Roms or factory images, Wifi will not work.
Here's how to fix it (you MUST be rooted):
1. ROOT your phone
2. download this http://forum.xda-developers.com/attachment.php?attachmentid=2531514&d=1390364984
3. download Root explorer from play store
4. download Rar archiver from play store
5. then unrar downloaded file
6. copy the unrared file from /storage/sdcard0/download to /persist with root explorer
7. reboot and your WiFi should work.
Simple thanks is enough
Click to expand...
Click to collapse
IT WORKS!!! Tested here on XT1069!
Thank you once is not enough... Thanks a MILLION, brother! :good:
linasmit said:
Hi Guys,
Cause of problem: I formated partition /persist on my moto G. I am stupid, I know. Unfortunately this partition is untouched by any flashes you will do, so you you can flash any Roms or factory images, Wifi will not work.
Here's how to fix it (you MUST be rooted):
1. ROOT your phone
2. download this http://forum.xda-developers.com/attachment.php?attachmentid=2531514&d=1390364984
3. download Root explorer from play store
4. download Rar archiver from play store
5. then unrar downloaded file
6. copy the unrared file from /storage/sdcard0/download to /persist with root explorer
7. reboot and your WiFi should work.
Simple thanks is enough
Click to expand...
Click to collapse
Oh my god thank you so much!! My phone is back to life!! :laugh:
I am glad that all of you found a solution to this problem.
in case anyone lands here from google...
I successfully upgraded to 5.02 and WiFi was working initially.
but then i had to change the custom recovery and superSU, and changed the logo.bin, now the WiFi is no longer working.
--- EDIT ---
after careful examination, found out it was caused by xt1064_lollipop_boot.img
in the end I flashed back to the stock boot.img from 5.02
and then flashed twrp-2.8.6.0-titan.img
now everything is great!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My-RoM based on clear stock B609. System is slimmed down with unnecessary applications and add-ons and You can install it simply by custom recovery (CWM).
In my idea every custom ROM it should be a stable and smoother minimal base for other users to customize and experiment it by own.
My-RoM current version: v3.3 (B609)
AnTuTu result:
Features:
Full Rooted
Removed unwanted apps
Caller picture re-sized
AddAway
Xposed
xLed - Custom led notifications
Double tap to sleep
Clock color changer
CrappaLinks
Holo Light Reboot
Swiftkey Keyboard
Kitkat External Card fixed
Boot sound removed
Custom splash
Custom boot animation
Other changes...
Known bugs:
If You found report
Requirements:
Bootloader unlocked
EMUI 3.0 ROM installed.
If you currently on EMUI 2.3 than update it to B602 or B609 ROM.
Download:
My-RoMv3.3.zip
Installation: (All wanted files inside package !)
Backup your important data (use HW Backup application)
Unpack downloaded files to external SD card
Install Stock recovery B609 (by fastboot) and wipe data/factory reset (by stock recovery)
Install CWM recovery (by fastboot)
Install P7-My-RoM_v3.3.zip (by CWM recovery)
Install SuperSU-v2.40.zip (by CWM recovery)
Reboot
When CWM ask for fixing root - select YES
Configure system
Settings -> Screen saving -> On
Open XPosed app
Modules -> Select all (or wanted) preinstalled modules
Framework -> Installation mode -> Disabled resource hooks
Framework -> Install/update
Reboot
Open HW Backup
Restore data from backup
Gaps to optional installation by CWM
Swype keyboard
Sim Tool Kit
My-RoM_gapps.zip
Remains !
If somebody don't want my custom logo/splash or boot animation just install (by CWM recovery) original one from downloaded package (HW_oem_logo.zip or HW_oem_anim.zip).
Reverting to EMUI 2.3 ROMs
Just install your old ROM by local update (sc card/dload/update.apk)
Previous versions:
My-RoM v3.1 (B602)
My-RoM v3.2 (B609)
Notice !
Everything you are doing on your own RISK !
Donators:
Godworrior1 - 5 USD
Fuijj - 1 USD
Mik Komarov - 10 USD
Shifa - 5 USD
rubberduck84 - 10 EUR
Thanks very much for donators
http://forum.xda-developers.com/donatetome.php?u=6041257
Credits:
Google
Huawei
Razziell
Shaftamle
XDA users
Swiftkeys
Everyone who compiled at least one line of included aps !
----------------------------------------------------------------------------------------------------
XDA:DevDB Information
My-RoM, ROM for the Huawei Ascend P7
Contributors
Ziolek67
ROM OS Version: 4.4.x KitKat
ROM Firmware Required: B602 or later
Version Information
Status: Stable
Current Beta Version: 3.3
Beta Release Date: 2015-01-18
Created 2014-12-18
Last Updated 2015-02-08
Welcome to the arena
Welcome back to the arena for developers and common users like me, who enjoy testing and installing technological stuff for fun or for work. I hope you can give the credits to the people who deserve it, and to design your own projects as well. You are famous, people from HTC mania have tested your roms too. Happy to see you again !!!!:good:
2 hours with the rom and.....
I tested almost all the rom 3.1 and you are doing an excellent job since s-view cover is fixed, now you can record phone calls. it has only essential apps for daily use. it is stable so far. Antutu Benchmark gave me 29000..
Humble Recommendation: you do not need to put "Myrom" in the first booting screen. All people who use your rom will know what rom it is about. How about eliminating "HICARE", who cares to know the phone numbers of Huawei or send messages to huawei staff. If you need them just google it or email it. Finally how about eliminating the browser or at least the shortcuts and place another custom browser in it like chrome, Maxthon,etc. I hate to see things in chinese like this:
It's possibile upgrade from MyRom 3.0 ?
How can I downgrade to b133 for reinstall all with clean installation??
It is very simple
teto78 said:
How can I downgrade to b133 for reinstall all with clean installation??
Click to expand...
Click to collapse
I have written this procedure several times in different posts. You must put B133 file called UPDATE.APP in a carpet called /dload/ in the sd card, you can create it. then install it via update---local update. That's it (Remember put the stock recovery 3.0 before performing actions for downgrading).
Godwarrior1 said:
I ...you do not need to put "Myrom" in the first booting screen. ...
Click to expand...
Click to collapse
Inside uploaded ROM package is HW_oem_logo.zip which include stock Huawei splash screen and script to install it.
If somebody don't like my splash screen can just install it by recovery after ROM installation. That is possible also to use this script to installing your own logo/splash accordingly to my tutorial.
Godwarrior1 said:
How about eliminating "HICARE", who cares to know the phone numbers of Huawei or send messages to huawei staff. If you need them just google it or email it. Finally how about eliminating the browser or at least the shortcuts and place another custom browser in it like chrome, Maxthon,etc. I hate to see things in chinese like this:
Click to expand...
Click to collapse
Hm... some people hate stock browser but some ask about it . ROM is fully rooted and it it's easy to deleting this apps by Root Explore. Next version (if will) I'll try to install as user applications. In that case it'll be easy to uninstalling it by user. But I remember from previously roms that stock browser can't work properly as user application. We'll see.
onurb said:
It's possibile upgrade from MyRom 3.0 ?
Click to expand...
Click to collapse
I think that is possible and it should work well. But I always recommend to make factory reset using stock recovery after every re installation from other versions.
Finally.
In my idea every custom ROM it should be a stable and smoother minimal base for other users to customize and experiment it by own. :fingers-crossed:
I made clean install..ROM works very well..clap clap !
Not working
Followed the procedure yet stuck on booting after flashing Rom and Kinguser. It stuck on booting and go into recovery instead. And now my phone is locked! When I connect my phone through fastboot, it is detected as the Lenovo Composite Device. What the heck is happening?
Free to choose
Finally.
In my idea every custom ROM it should be a stable and smoother minimal base for other users to customize and experiment it by own. :fingers-crossed:[/QUOTE]
Exactly,
so in my opinion you don't need to put any app that anyone can do it by himself.
Neither xposed or keyboard ,anything at all.
btw- good work
Cannot download the file
Is there any other link. I try to download the file and almost at the end I got a network error. Is there any other way to download the files. I really love your ROMS as they are super smooth. Please help.
I always recommend
amruhaidy said:
Followed the procedure yet stuck on booting after flashing Rom and Kinguser. It stuck on booting and go into recovery instead. And now my phone is locked! When I connect my phone through fastboot, it is detected as the Lenovo Composite Device. What the heck is happening?
Click to expand...
Click to collapse
I always recommend installing CWM Recovery before installing any custom Rom and do a full wipe of data and wipe dalvik cache to eliminate all traces from the old rom. Another thing I recommend to see if you come from 2.3 to 3.0 emui, you must install the right /dload/ Filein the sdcard, and to have factory recovery and the installation should be executed with the options update/local update.
[Solved] Force update B133SP01
Godwarrior1 said:
I always recommend installing CWM Recovery before installing any custom Rom and do a full wipe of data and wipe dalvik cache to eliminate all traces from the old rom. Another thing I recommend to see if you come from 2.3 to 3.0 emui, you must install the right /dload/ Filein the sdcard, and to have factory recovery and the installation should be executed with the options update/local update.
Click to expand...
Click to collapse
Thanks for your response but I've actually mentioned that I've had followed the instructions, none was left behind so obviously I've has flashed CWM Recovery first and did the rest. Anyhow, I have solved the problem myself. Here's the funny thing, my device was locked (seen from bootloader), I have EMUI3.0 on, I put B133SP01 update.app in the dload and force update. Somehow, I have my phone working again with B133SP01 installed and EMUI2.3 on board! Funny when it's not supposed to work out since downgrading from EMUI3.0 to 2.3 is a daunting task. But Thanks again for your response, I really appreciate it. Merry Christmas! :cheers:
The same to you
amruhaidy said:
Thanks for your response but I've actually mentioned that I've had followed the instructions, none was left behind so obviously I've has flashed CWM Recovery first and did the rest. Anyhow, I have solved the problem myself. Here's the funny thing, my device was locked (seen from bootloader), I have EMUI3.0 on, I put B133SP01 update.app in the dload and force update. Somehow, I have my phone working again with B133SP01 installed and EMUI2.3 on board! Funny when it's not supposed to work out since downgrading from EMUI3.0 to 2.3 is a daunting task. But Thanks again for your response, I really appreciate it. Merry Christmas! :cheers:
Click to expand...
Click to collapse
The same to you. Merry Christmas and Happy New Year !!!!
amruhaidy said:
... I've has flashed CWM Recovery first and did the rest. Anyhow, I have solved the problem myself. Here's the funny thing, my device was locked...
Click to expand...
Click to collapse
Hm... I am wondering what could happen with your device. First time I hear about situation that bootloader was locked during flashing room. Are you sure that you flash appropriate files (especially recovery or kernel) by fastboot? What was you previous system?
bolleyjara said:
Is there any other link. I try to download the file and almost at the end I got a network error. Is there any other way to download the files. I really love your ROMS as they are super smooth. Please help.
Click to expand...
Click to collapse
Mirror added to first post.
Ziolek67 said:
Hm... I am wondering what could happen with your device. First time I hear about situation that bootloader was locked during flashing room. Are you sure that you flash appropriate files (especially recovery or kernel) by fastboot? What was you previous system?
Wysłane z mojego HUAWEI P7-L10
Click to expand...
Click to collapse
Hahaha..it keeps me wondering even till now. I've been around a few roms and I know how to work things out so yeah I really followed the instructions. My previous rom was Se7en and if you are going to say wipe dalvik and full wipe, believe mw, I did it already..haha
Sent from my HUAWEI P7-L10 using XDA Free mobile app
Wow… fast and no lags ?
The perfect rom ever.
But I use superuser pack from v3.0 its work like charm and its full rooted
:thumbup:
Thanx a lot
Sent from my HUAWEI P7-L10 using XDA Free mobile app
If somebody have any problems after installation it means that they didn't installation procedure exactly. Especially wiping data before installation by using the supplied stock recovery.
I suggest that if you previously used custom rom that reset factory data (by supplied B602 stock recovery ) also after installation My-RoM and reinstall it again (kinguser too) .
It is important to totally removing any remains of previous rom.
Notice! TWRP doesn't wiping all data correctly. Use stock recovery to do this exactly.
Sent from my HUAWEI P7-L10
Ziolek67 said:
If somebody have any problems after installation it means that they didn't installation procedure exactly. Especially wiping data before installation by using the supplied stock recovery.
I suggest that if you previously used custom rom that reset factory data (by supplied B602 stock recovery ) also after installation My-RoM and reinstall it again (kinguser too) .
It is important to totally removing any remains of previous rom.
Notice! TWRP doesn't wiping all data correctly. Use stock recovery to do this exactly.
Sent from my HUAWEI P7-L10
Click to expand...
Click to collapse
can u add sound to your flashable stock boot animation zip please?
thnx
DISCLAIMER:
Code:
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
TWRP 3.1.1-0 for Huawei Nova
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Notes
1) It has been confirmed that's working on EMUI 4.1. However, it haven't been tested on EMUI 5 and i don't know if encryption is working. If it is working, you won't have to format /data. So, i would be glad if someone could test it.
2) I've chose the red color because it looks kinda cool and it's also easy to know which recovery you're using. In future, i may change it back to blue or i may change it to other color (like teal). I may also do it like @Meticulus did for his TWRP's (red color when you're on EMUI and blue when you're on LineageOS etc.) or maybe a new color every time you go to recovery lol.
3) There are still some things with blue color. I'll look into it more as I'd like to change the whole blue color. I wanna do it in the source code.
Click to expand...
Click to collapse
Introduction
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Click to expand...
Click to collapse
Requirements
Huawei Nova
Unlocked bootloader ( here's a guide about how to unlock it)
Click to expand...
Click to collapse
Installation
If you already have a TWRP installed:
1) Boot in TWRP.
2) Select "Install", then "install image".
3) Select the recovery.img where you've placed it and then choose recovery from the partition list.
5) Reboot recovery if you wanna boot in TWRP or reboot system.
Click to expand...
Click to collapse
If you don't have any TWRP installed:
1) Unlock your bootloader. Here's a guide about how to do it.
2) Run the following command in terminal (linux) or command prompt (windows, e.g. minimal ADB and fastboot):
Code:
[COLOR="red"]/* If you are doing this on Linux,
then run fastboot with [B]sudo[/B]: sudo fastboot blabla */[/COLOR]
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Download
AndroidFileHost | Mediafire
Sources
TWRP: https://github.com/omnirom/android_bootable_recovery/tree/android-7.1
Device tree: https://github.com/skinzor/android_device_huawei_hwcan/tree/android-7.1
Kernel: https://github.com/skinzor/android_kernel_huawei_msm8953-1/tree/cm-14.1
Click to expand...
Click to collapse
Credits
@abhishek987
@Meticulus
@ TWRP team
@ OmniROM
@ Huawei
XDA:DevDB Information
[RECOVERY][UNOFFICIAL] TWRP 3.1.1-0, Tool/Utility for the Huawei Nova/Nova Plus
Contributors
#Henkate
Source Code: https://github.com/omnirom/android_bootable_recovery/tree/android-7.1
Version Information
Status: Stable
Stable Release Date: 2018-01-20
Created 2018-01-20
Last Updated 2018-01-20
Reserved
Reserved
Nice job on red TWRP...flashed and working great
not working on EMUI 5
we have to password to encrypt Data .... (lol no one know pw )
So we have to format Data like you said ....
Thanks for updates.
And waiting your kenel.
Do not know whether he supports Chinese? The red UI is cool and I want to try ?
To Young said:
Do not know whether he supports Chinese? The red UI is cool and I want to try ?
Click to expand...
Click to collapse
just trying ... no problem ... u can reflash old version
To Young said:
Do not know whether he supports Chinese? The red UI is cool and I want to try ?
Click to expand...
Click to collapse
If you meant chinese language, then it doesn't have it as far as i can see. If you meant the chinese model of Nova, well it should work on all models.
Just like @babysocola1x said, you can try.
babysocola1x said:
just trying ... no problem ... u can reflash old version
Click to expand...
Click to collapse
Thank you ?
---------- Post added at 10:13 AM ---------- Previous post was at 10:12 AM ----------
#Henkate said:
If you meant chinese language, then it doesn't have it as far as i can see. If you meant the chinese model of Nova, well it should work on all models.
Just like @babysocola1x said, you can try.
Click to expand...
Click to collapse
I mean Chinese, I will try it
Nice, but how to make a nandroid backup ?
it dosnt mount any storage, i've even tried otg using a usb flash drive.
what gives?
Axims said:
Nice, but how to make a nandroid backup ?
it dosnt mount any storage, i've even tried otg using a usb flash drive.
what gives?
Click to expand...
Click to collapse
I don't have any problem with backups. I've made backups and restored them without any problem. As for OTG, I don't have the possibility to test that.
Please share the recovery log.
#Henkate said:
I don't have any problem with backups. I've made backups and restored them without any problem. As for OTG, I don't have the possibility to test that.
Please share the recovery log.
Click to expand...
Click to collapse
Well, seems the sd card was buggy, replaced it with a new samsung evo and
everything went smooth from there. (seems ext sd is the only selectable storage).
Now, have you noticed the warning about "project" part during backup?
is it normal?
Axims said:
Now, have you noticed the warning about "project" part during backup?
is it normal?
Click to expand...
Click to collapse
I'm not sure what you mean and I don't remember seeing this, but it's also possible that I've just missed it.
Could you share a screenshot? You can take screenshots in recovery just like you do when your phone is booted. You can also share a recovery log.
Actually, It's Product no Project!
I PM'd you the recovery.log
nothing important I guess?
Axims said:
Actually, It's Product no Project!
I PM'd you the recovery.log
nothing important I guess?
Click to expand...
Click to collapse
I haven't received any PM. Maybe it's XDA's fault as it looks like it's fucked up. All my posts were delayed today and noticed the same thing at other users.
Well, I didn't have this problem, but /product has some files (like acdbata, needed for audio) which EMUI uses and LineageOS or other ROMs too (since it's using blobs from EMUI). So, this could be a problem for ROMs like Lineage, but I think you can just fastboot the product.img after you extract it from update.app (stock firmware).
You can also try to restore this TWRP backup of product partition and restore it.
#Henkate said:
I haven't received any PM. Maybe it's XDA's fault as it looks like it's fucked up. All my posts were delayed today and noticed the same thing at other users.
Well, I didn't have this problem, but /product has some files (like acdbata, needed for audio) which EMUI uses and LineageOS or other ROMs too (since it's using blobs from EMUI). So, this could be a problem for ROMs like Lineage, but I think you can just fastboot the product.img after you extract it from update.app (stock firmware).
You can also try to restore this TWRP backup of product partition and restore it.
Click to expand...
Click to collapse
Thanks, as you may read the log later, it gave 2 errors at beginning and the end that it could not read or open Product. something like that.
I'm still on B151 MM Rom , will this backup of product work with any version?
Ok , my fear came true, long story short: I installed latest rom via FF app and bootloop began.
tried many ways, didnt work. flashed twrp again and tried to restore that nandroid backup, turns out those 2 errors were serious: failed to mount cust, failed to mount product, system goes near end then another error and quits. only boot and data seems restored fine.
while i'm going to try that smoochi's backup (bless him) , can you please recheck to see if my case was some isolated issue or there is something to fix about this reccovery?
thanks
Hi...youve learned the lesson...never install from FF...ive been using twrp for quite a while on my nova plus and never had such problems except once cuz i tried to restore a backup that ive done format/data...then got into bootloop..
What are you planning to use...emui4 or 5 ?
virusdunil said:
Hi...youve learned the lesson...never install from FF...ive been using twrp for quite a while on my nova plus and never had such problems except once cuz i tried to restore a backup that ive done format/data...then got into bootloop..
What are you planning to use...emui4 or 5 ?
Click to expand...
Click to collapse
I was on emui 4 (B151) everything was fine until I got an itch to try android 7!
Ok, I restored with smoochi backup then updated to B341 , now cust is gone
(no update in setting either) so went to reflash this twrp , but it seems unlocking bootloader is not enough, now says FRP locked! wtf??
I already hate this android 7! I'll get back to 6 first chance i get !
I had same problem...theme manager not working...file and updade manager gone so...
Frp locked is OEM unlock in developement...it must be ON...
Im still on emui4 and will stay on it ?
I just looked up a few threads about rooting EMUI 9.
The one and only who kinda managed to do it is the developer of Magisk John Wu.
If you wanna stay updated about rooting EMUI 9 on Huawei P20pro, you should follow this guy:
EMUI9 root
still NO EMUI 9 kernel sources released
Rooting / Magisk is one thing. I think in addition to that we also need a working twrp or some recovery for Emui 9 to be able to flash stuff with relative ease. On top of that the OEM unlock option is greyed out which is problematical itself. So, this is all gonna be a bit complicated.
Well, there is a modded versions of TWRP Mate Rs Porsche with working decryption and for most people including me, oem-unlock is not greyed out when you have unlocked frp and unlocked bootloader.
I'm on the final of EMUI 9. So the last important thing would be a rooted EMUI 9 to get some important things working.
mrabcx said:
Rooting / Magisk is one thing. I think in addition to that we also need a working twrp or some recovery for Emui 9 to be able to flash stuff with relative ease. On top of that the OEM unlock option is greyed out which is problematical itself. So, this is all gonna be a bit complicated.
Click to expand...
Click to collapse
ArtaxXP said:
and for most people including me, oem-unlock is not greyed out when you have unlocked frp and unlocked bootloader.
Click to expand...
Click to collapse
Unlocked frp = oem unlock enabled in dev options
Unlock bootloader and frp itself doesn't cause "enable oem unlock" being greyed out. It's not getting greyed out just by upgrading to pie either. Upgrade to pie and factory reset does!
Good to know about twrp working on p20 pro
Hello, i changed my system font by using huawei themes.
Now it's not possible anymore, to edit photos and use different fonts for editing.
Does anybody have an idea, what i can do?i want to keep the new system font.
I hope to get a usefull help, i really would be grateful.
Sorry for this comment, i doesn't belong at this page
there is already something new on this topic?
not much but some
Heinzx3 said:
there is already something new on this topic?
Click to expand...
Click to collapse
some good news
good news
Rooted on 9.0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my CLT-L04 using Tapatalk
Dene_Bluesman said:
Rooted on 9.0 View attachment 4673784
Sent from my CLT-L04 using Tapatalk
Click to expand...
Click to collapse
Yeah awesome! Well done!
John Wu just released some info in a post: EMUI9 root
Dene_Bluesman said:
Rooted on 9.0 View attachment 4673784
Sent from my CLT-L04 using Tapatalk
Click to expand...
Click to collapse
Link pls
mr.mgmg said:
Link pls
Click to expand...
Click to collapse
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
Sent from my CLT-L04 using Tapatalk
Dene_Bluesman said:
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
Sent from my CLT-L04 using Tapatalk
Click to expand...
Click to collapse
There are alot files
https://github.com/topjohnwu/magisk_files/tree/master/canary_builds
Any file i must download and flash
mr.mgmg said:
There are alot files
https://github.com/topjohnwu/magisk_files/tree/master/canary_builds
Any file i must download and flash
Click to expand...
Click to collapse
Would like someone to drop round and flash it for you too? Do some reading, or don't flash.
purple patch said:
Would like someone to drop round and flash it for you too? Do some reading, or don't flash.
Click to expand...
Click to collapse
I think the Q not for you, just keep silent
mr.mgmg said:
I think the Q not for you, just keep silent
Click to expand...
Click to collapse
his point is, even you got the question wrong,
no files from that list will root your emui 9 simply by flashing any of it,
you gonna need a copy of RECOVERY_RAMDIS.img pulled from update.app of latest emui 9.0 firmware,
copy it to device with latest canary magisk & magisk manager installed,
patching the .img using that canary manager, and you will get patched_boot.img stored in download folder in that device,
copy it to your pc and flash it to recovery_ramdisk partition using fastboot,
or if you really are that lazy, simply download the prepatched one here : https://drive.google.com/file/d/1rhl405-ALbYrtGHilrNUR5Fuq4yATvTH/view?usp=drivesdk
and flash it from fastboot to your recovery_ramdisk partition
boot by holding vol up button
otonieru said:
his point is, even you got the question wrong,
no files from that list will root your emui 9 simply by flashing any of it,
you gonna need a copy of RECOVERY_RAMDIS.img pulled from update.app of latest emui 9.0 firmware,
copy it to device with latest canary magisk & magisk manager installed,
patching the .img using that canary manager, and you will get patched_boot.img stored in download folder in that device,
copy it to your pc and flash it to recovery_ramdisk partition using fastboot,
or if you really are that lazy, simply download the prepatched one here : https://drive.google.com/file/d/1rhl405-ALbYrtGHilrNUR5Fuq4yATvTH/view?usp=drivesdk
and flash it from fastboot to your recovery_ramdisk partition
boot by holding vol up button
Click to expand...
Click to collapse
Thanks for help
It will seem dumb for some of you but important to me and others (i Hope there are some lol)..... so just to be clear :
1- do we have to follow these steps AFTER installing emui 9 ? coming from emui 8.1 161 with evira kernel and using mods i wanna start 100% fresh because first time i installed emui 9 163 i came back a week later because of battery consuption that was way worse and real bad SOT so it's major to me to proceed the best way - i have to go first to twrp and wipe all, data+system+caches before flashing emui 9 ?
2- any reason not to use the easiest way ? why to prefer the complicated one : pulling the file from update.app and copy and etc....?
3- magisk modules will be usable ?
Thanks to those of you who will bring light or give me confident in re-installing pie.
And of course merry Christmas everyone
deltaman83 said:
It will seem dumb for some of you but important to me and others (i Hope there are some lol)..... so just to be clear :
1- do we have to follow these steps AFTER installing emui 9 ? coming from emui 8.1 161 with evira kernel and using mods i wanna start 100% fresh because first time i installed emui 9 163 i came back a week later because of battery consuption that was way worse and real bad SOT
2- any reason not to use the easiest way ? why to prefer the complicated one : pulling the file from update.app and copy and etc....?
3- magisk modules will be usable ?
Thanks to those of you who will bring light or give me confident in re-installing pie.
And of course merry Christmas everyone
Click to expand...
Click to collapse
1. Steps is for rooting, if you wanna start fresh, you can consider wiping /data after update. So none of your previous mods data no cache will tag along to your EMUI 9
2. Reason is, the difference of firmware versioning betweem region. You told me you updated to .163. My prepatched ramdisk is from C636 .168, although most of the time it can work universally across region and version (just like how custom recovery work in a universal way), there's no telling what huawei actually did between version update. So its always best to use and patch your own file. Since it will give you confidence, its your own doing after all.
3. I use youtubevanced, LKT, systemless host, swap torpedo, busybox and detach magisk modules, all work just fine on EMUI 9. You only need to redownload and reinstall all the modules (if you didnt wipe data, like me), because installation from oreo version wont work straight away on EMUI 9.
for extra information, SafetyNet and MagiskHide all working as well. I can use my banking app just fine.
as for precaution info,
i suggest you to use the flashy tools to install EMUI 9 from PC instead of using HuRU,
i did the HuRU way, and ends up with a messed up software serial number and broken recovery partition, meaning i can't flash TWRP, stock recovery nor a patched recovery ramdisk to acquired root. It will all fall to an error screen, telling me no recovery image available inside the system, and ask me to update system again. Fortunately the phone still boot just fine to system.
scratched my heads for hours until i manage to resolved it by flashing Recovery META and Recovery Vendor image through fastboot. After that i can reflash stock recovery, and the patched one (after i confirm stock one work fine)
Thanks a lot for your answers.
---------- Post added at 06:42 PM ---------- Previous post was at 06:24 PM ----------
otonieru said:
1. Steps is for rooting, if you wanna start fresh, you can consider wiping /data after update. So none of your previous mods data no cache will tag along to your EMUI 9
Click to expand...
Click to collapse
One thing no clear to me is what i do of the magisk canary Zip file...?.... ? As twrp not working on emui 9...
Hi. I am new to this site.
I want to root my Redmi Note 11 but I don't know how to.
I tried looking up online but all I could find were guides on other devices. And outdated too.
I read about Magisk and Magisk Hide which allows you to pass SafetyNet but I also read that it's developer joined Google. So I don't know if it will work or not.
Please help me.
How can I root my phone and pass SafetyNet?
Device Specs:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The first step is to unlock your bootloader which usually takes a week. Do that first, then you can browse more and wait for answers while you wait
I have already requested Mi for permission to unlock bootloader. I had to wait 5 days and today is the last day.
parker_04 said:
I have already requested Mi for permission to unlock bootloader. I had to wait 5 days and today is the last day.
Click to expand...
Click to collapse
Make sure to backup all your data before unlocking bootloader as it will wipe them.
I strongly recommend flashing Xiaomi.eu Stable ROM first as it offers more features than stock and also, you don't have to look for the boot.img again. But in case you want to keep it stock, you want to find the flashboot ROM with the exact same version as the one you have right now and extract the boot.img from it. Then you want to get magisk on your phone, transfer the boot.img to your phone, patch it, transfer it back to your computer, and then use ADB to flash the boot.img
parker_04 said:
Hi. I am new to this site.
I want to root my Redmi Note 11 but I don't know how to.
I tried looking up online but all I could find were guides on other devices. And outdated too.
I read about Magisk and Magisk Hide which allows you to pass SafetyNet but I also read that it's developer joined Google. So I don't know if it will work or not.
Please help me.
How can I root my phone and pass SafetyNet?
Device Specs:
View attachment 5807325
Click to expand...
Click to collapse
notBradPitt said:
Make sure to backup all your data before unlocking bootloader as it will wipe them.
I strongly recommend flashing Xiaomi.eu Stable ROM first as it offers more features than stock and also, you don't have to look for the boot.img again. But in case you want to keep it stock, you want to find the flashboot ROM with the exact same version as the one you have right now and extract the boot.img from it. Then you want to get magisk on your phone, transfer the boot.img to your phone, patch it, transfer it back to your computer, and then use ADB to flash the boot.img
Click to expand...
Click to collapse
Thank you for replying.
I am quite newbie in rooting.
I can understand enough to follow your instructions but not enough to really know what I am doing.
Can you please elaborate each step and what it does?
Or maybe refer me to a trusted guide where I can understand the tidbits.
parker_04 said:
Thank you for replying.
I am quite newbie in rooting.
I can understand enough to follow your instructions but not enough to really know what I am doing.
Can you please elaborate each step and what it does?
Or maybe refer me to a trusted guide where I can understand the tidbits.
Click to expand...
Click to collapse
I think this sums it pretty well: https://forum.xda-developers.com/t/installing-miui-eu-rom-and-root.4426937/
- Backing up data: Back up your data so it won't be lost during bootloader unlock
- Unlock bootloader: allows you to flash into your phone
- Flashing Xiaomi.eu (optional): Their ROM is based on MIUI Global/China which has way more features than region based ROMs and no bloatware. Cons is you have to manually update it and you can't update system apps (as they're also modified to disable ads). Pros is, you know the version you just flashed and the boot.img is also there.
- Finding boot.img: This is the file you want to patch if you want to root your phone. You can find this by extracting the fastboot ROM and it should be inside. In case of stock MIUI, you have to download the exact version that you have right now on https://xiaomifirmwareupdater.com/ , get the flashboot version, extract, and boot.img should be inside
The rest should be explained in the post above and I think this will also help in installation of Magisk https://topjohnwu.github.io/Magisk/install.html
@notBradPitt Hey, is this the correct fastboot rom for my device?
https://sourceforge.net/projects/xi...MNote11_V13.0.5.0.SGKMIXM_v13-12.zip/download
parker_04 said:
@notBradPitt Hey, is this the correct fastboot rom for my device?
https://sourceforge.net/projects/xi...MNote11_V13.0.5.0.SGKMIXM_v13-12.zip/download
Click to expand...
Click to collapse
Yes. After unlocking bootloader, make sure USB debugging is enabled (because you just reset the phone), boot into flashboot mode, and run the "first install" script. Make sure your cables are connected properly so it doesn't corrupt any files. First time booting will take around 15-20 minutes for me, so this is normal and you shouldn't panic.
After that you can continue with the root process. The boot.img should be in "images" folder. Once you are done with it, you can try the tools listed here (https://www.xda-developers.com/how-to-pass-safetynet-android/) to pass SafetyNet. You can test the SafetyNet using the tool in Magisk or you can use YASNAC (from Google Play or GitHub)
notBradPitt said:
Yes. After unlocking bootloader, make sure USB debugging is enabled (because you just reset the phone), boot into flashboot mode, and run the "first install" script. Make sure your cables are connected properly so it doesn't corrupt any files. First time booting will take around 15-20 minutes for me, so this is normal and you shouldn't panic.
After that you can continue with the root process. The boot.img should be in "images" folder. Once you are done with it, you can try the tools listed here (https://www.xda-developers.com/how-to-pass-safetynet-android/) to pass SafetyNet. You can test the SafetyNet using the tool in Magisk or you can use YASNAC (from Google Play or GitHub)
Click to expand...
Click to collapse
Thank a lot for your help!
Reply from recently flashed Xiaomi Eu ROM.
parker_04 said:
Thank a lot for your help!
Reply from recently flashed Xiaomi Eu ROM.
Click to expand...
Click to collapse
No problem How do you like it? Have you proceeded with root yet?
notBradPitt said:
No problem How do you like it? Have you proceeded with root yet?
Click to expand...
Click to collapse
It's nice.
Xiaomi eu is certainly cleaner than stock. Adless and bloatless. It has new features although some of the stock's features are missing. Play Store is jittery for unknown reasons.
And when I try to open a file in another app, the app list appears quite late and it's laggy too. But that's all and I don't mind it.
Thanks again for recommending it.
notBradPitt said:
Have you proceeded with root yet?
Click to expand...
Click to collapse
Yeah. Rooting with magisk is so easy. And it's uninstallation is easy too.
parker_04 said:
I have already requested Mi for permission to unlock bootloader. I had to wait 5 days and today is the last day.
Click to expand...
Click to collapse
Yo I'm new to rooting ,so during the 168 hours period can I switch from data to Wi-Fi and use it for like watching videos and playing games?
creepystaircase66 said:
Yo I'm new to rooting ,so during the 168 hours period can I switch from data to Wi-Fi and use it for like watching videos and playing games?
Click to expand...
Click to collapse
Yes, data is only needed when you request for permission
Assuming you have unlocked the bootloader
Step by Step Guide:
1. Download Magisk APK and install it
2. Patch your Recovery (Stock, TWRP, Skyhawk, etc) in magisk app and copy the patched img to Computer
3. Switch it off, then boot to bootloader, and type "fastboot flash boot recovery_patched.img" where recovery_patched.img is your file name.
4. Reboot (Might take longer than usual) and open magisk to confirm the the result of actions.