Overview
This is a patched recovery image which bypasses the usual checks performed during a firmware flash, allowing you to flash unapproved OTA firmwares. For example, the latest FullOTA-MF b394:
{
"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"
}
You can also downgrade without using the b300 rollback package (untested)
Prerequisites
Unlocked bootloader
Rooted
Backup your data (flashing may cause bootloader to re-lock or restore factory default etc. - don't blame me if it goes wrong!)
Instructions
Download firmware:
Use Huawei Firmware Finder (Play Store link) to download the latest firmware files - you will need all 3 zip files:
- update.zip
- update_data_full_public.zip
- update_full_EVA-L09_hw_eu.zip
Tips: check for the latest number (102064 for b394) and ensure you have the larger filesize (around 2GB). For example, these are the latest at time of writing b394:
Flash nocheck recovery:
Reboot device to fastboot mode (power off fully, hold down volume button and connect USB cable)
Run the following to flash recovery:
Code:
fastboot flash recovery eva_l09b391_nocheckrecovery.img
fastboot reboot
Send commands via ADB
Phone should be booted back to system - connect phone via adb and allow root prompt:
Code:
adb shell
su
Create HWOTA folder:
Code:
mkdir /data/update/HWOTA
Copy firmware to HWOTA folder (replace 102064 below with correct value - this is for b394):
Code:
cp /sdcard/HWFF/102064/update* /data/update/HWOTA/
Paste recovery command:
Code:
echo "--update_package=/data/update/HWOTA/update.zip" > /cache/recovery/command
echo "--update_package=/data/update/HWOTA/update_data_full_public.zip" >> /cache/recovery/command
echo "--update_package=/data/update/HWOTA/update_full_EVA-L09_hw_eu.zip" >> /cache/recovery/command
exit
Finally reboot to recovery to start firmware upgrade:
Code:
adb reboot recovery
Firmware should install and reboot automatically
Extras
You can probably Re-Brand to alternative customers too i.e. c636 (Asian region) to c432 (European region). Follow the tutorial here: https://forum.xda-developers.com/honor-8-pro/how-to/oeminfo-c432-t3625886 - you'll need the correct OEMINFO files, this is untested.
Thanks
- Olddroid
- Mankindtw
- Hackslash
- DkiOnline (L09 tester)
- jimz6 (L19 tester)
- LastStandingDroid
XDA:DevDB Information
EVA NoCheck Recovery, Tool/Utility for the Huawei P9
Contributors
Atarii
Version Information
Status: Stable
Created 2017-11-14
Last Updated 2017-11-17
Changelog
31-01-2018
Added L29 recovery image
17-11-2017
Added L19 recovery image
14-11-2017
Initial release
THX, i try and successfully, i am on latest firmware now
rafitcu said:
THX, i try and successfully, i am on latest firmware now
Click to expand...
Click to collapse
Great - thanks for the feedback
Update: I've added the L19 recovery image after successful feedback
updated succesfully.
only two points, on prerequisites I think you should add that the phone should be rooted cause after I flashed the nochechrecovery I needed to reflash twrp and root.
and the second point is that there is missing a / before de * in the step when you copy the 3 zips to data.
nice to know there is a method to bypass the verification on firmwares :good::good:
Can any one try downgrade after update to b394 using b300???
Can one modify the recovery.img file for a certain firmware version other than B391?
kukubau said:
Can one modify the recovery.img file for a certain firmware version other than B391?
Click to expand...
Click to collapse
You haven't read OP #1?
Tecalote said:
You haven't read OP #1?
Click to expand...
Click to collapse
You didn't understand my question.
Can one modify the recovery.img from another firmware package, other than B391?
Let's say I'd like to do a HEX file diff between two image files and modify the img file myself.
Is this possible? What should I look for?
For learning purposes.
kukubau said:
You didn't understand my question.
Can one modify the recovery.img from another firmware package, other than B391.
Let's say I'd like to do a HEX file diff between two image files and modify the img file myself.
Is this possible? What should I look for?
For learning purposes.
Click to expand...
Click to collapse
You can use this recovery with any firmware and ignore the version - I just used b391 as the base as that's the firmware I was on at the time.
You can't modify other recovery images by diffing the hex - you need to disassemble the recovery binary and overwrite the checks with arm assembly
@Atarii
Do you try downgrade using b300 update.app and then to b136 or b182???
Your method it's safe?? What when we brick device
Atarii said:
You can use this recovery with any firmware and ignore the version - I just used b391 as the base as that's the firmware I was on at the time.
You can't modify other recovery images by diffing the hex - you need to disassemble the recovery binary and overwrite the checks with arm assembly
Click to expand...
Click to collapse
Thanks for the clarification.
I've flashed the L19 B391 recovery image and flashed the B391 OTA using your method, but the phone didn't boot afterwards.
I'll try the B390 OTA later today, to see if it makes a difference.
kukubau said:
Thanks for the clarification.
I've flashed the L19 B391 recovery image and flashed the B391 OTA using your method, but the phone didn't boot afterwards.
I'll try the B390 OTA later today, to see if it makes a difference.
Click to expand...
Click to collapse
if not, boot up and hold vol+ like you would enter to twrp, then it should flash automatically.
kukubau said:
Thanks for the clarification.
I've flashed the L19 B391 recovery image and flashed the B391 OTA using your method, but the phone didn't boot afterwards.
I'll try the B390 OTA later today, to see if it makes a difference.
Click to expand...
Click to collapse
Did you use the 2GB file?
Atarii said:
Did you use the 2GB file?
Click to expand...
Click to collapse
Yes.
---------- Post added at 02:55 PM ---------- Previous post was at 02:53 PM ----------
dkionline said:
if not, boot up and hold vol+ like you would enter to twrp, then it should flash automatically.
Click to expand...
Click to collapse
I've flashed my phone and unbricked it hundreds of times.
I've even posted an unbrick guide here on XDA forums.
I guess I know how to force flash it using the three key combo.
chudy_85 said:
@Atarii
Do you try downgrade using b300 update.app and then to b136 or b182???
Your method it's safe?? What when we brick device
Click to expand...
Click to collapse
I haven't personally tested this but I know others have for other device - so use at your own risk
kukubau said:
Yes.
---------- Post added at 02:55 PM ---------- Previous post was at 02:53 PM ----------
I've flashed my phone and unbricked it hundreds of times.
I've even posted an unbrick guide here on XDA forums.
I guess I know how to force flash it using the three key combo.
Click to expand...
Click to collapse
Im not using 3 key, only 1.
If not boot, you have manually boot with key i posted before.
This is so nice. Is it possible to make one for PO Plus, VIE-L09 and VIE-L29? Thanks
dkionline said:
Im not using 3 key, only 1.
If not boot, you have manually boot with key i posted before.
Click to expand...
Click to collapse
Doesn't boot into android os, no matter what.
I'll post a follow up after I try the B390 fw, maybe incremental updates are required.
Related
Hi
I created root method for the last version of samsung J2 Prime G532G - G532GDXU1APL1.
It based on modified stock recovery with custom keys (mine), which allow to install a special zip that signed with those keys.
This method include's a patched boot.img (sepolicy), in order the root work properly. (this is normal system root - not systemless, and from Android 6.0 or samsung 5.1.1 and above need also pathed boot)
The phone must be with G532GDXU1APL1 version, or it wont work.
It can be downloaded from here
G532GDXU1APL1
Instructions:
Download this file, and extract it to some folder.
G532GDXU1APL1_root_by_avicohh
Open odin and flash the .tar file inside the folder (In AP).
This file contains the custom recovery, a patched boot, and an empty cache.img in order the phone will restart to recovery after flashing.
In recovery choose "Apply update from ADB".
Run the .bat script file from the "SuperSU sideload installer" folder.
Wait until it finish, the phone will restart automatically with SuperSU inside.
Good luck!
Credits:
@Chainfire for SuperSU
@osm0sis for AIK
P.S. (for devs)
This method can be modified to another build / device, by patching the sepolicy inside boot.img (see here), and replacing the res / keys file inside the recovery.img with my keys. (Attached)
You can unpack and repack boot and recovery images with this tool. (It recomanded to this on linux in order to keep the files permissions)
The stock recovery doesn't support the standart SuperSU installer bacause it bash script, so i wrote another one in Edify. (this zip should work on any device with android 5.11 - 6.0.1 and armv7)
I am waiting new method root for G532G (G532GDXU1APL1)
Now..
great work ,,thanks bro .......I 'm so happy .....
Manual instruction recovery_custom_keys.7z ??? thank
---------- Post added at 02:11 PM ---------- Previous post was at 02:07 PM ----------
avicohh said:
Hi
I created root method for the last version of samsung J2 Prime G532G - G532GDXU1APL1.
It based on modified stock recovery with custom keys (mine), which allow to install a special zip that signed with those keys.
This method include's a patched boot.img (sepolicy), in order the root work properly. (this is normal system root - not systemless, and from Android 6.0 or samsung 5.1.1 and above need also pathed boot)
The phone must be with G532GDXU1APL1 version, or it wont work.
It can be downloaded from here
G532GDXU1APL1
Instructions:
Download this file, and extract it to some folder.
G532GDXU1APL1_root_by_avicohh
Open odin and flash the .tar file inside the folder (In AP).
This file contains the custom recovery, a patched boot, and an empty cache.img in order the phone will restart to recovery after flashing.
In recovery choose "Apply update from ADB".
Run the .bat script file from the "SuperSU sideload installer" folder.
Wait until it finish, the phone will restart automatically with SuperSU inside.
Good luck!
Credits:
@Chainfire for SuperSU
@osm0sis for AIK
P.S. (for devs)
This method can be modified to another build / device, by patching the sepolicy inside boot.img (see here), and replacing the res / keys file inside the recovery.img with my keys. (Attached)
You can unpack and repack boot and recovery images with this tool. (It recomanded to this on linux in order to keep the files permissions)
The stock recovery doesn't support the standart SuperSU installer bacause it bash script, so i wrote another one in Edify. (this zip should work on any device with android 5.11 - 6.0.1 and armv7)
Click to expand...
Click to collapse
recovery_custom_keys.7z hướng dẫn tay ??? cảm tạ
I don't understand, what instructions?
ask something
this root files include custom recovery?
Yes, but no TWRP. Modified stock recovery.
not only G532GDXU1APL1
Not only G532GDXU1APL1 is working but also G532GDXU1AQA4 is rooted smoothly i have tested on my device. So thanks a lot.:fingers-crossed:
Brother. Can you explain to me ste by step to root sm-g532g on aq4 firmware? Please
:fingers-crossed:
bolda.mia said:
Not only G532GDXU1APL1 is working but also G532GDXU1AQA4 is rooted smoothly i have tested on my device. So thanks a lot.:fingers-crossed:
Click to expand...
Click to collapse
Just do the instruction in the first post.
Hei avicoh
avicohh said:
just do the instruction in the first post.
Click to expand...
Click to collapse
sometimes i have an error when daemon start in cmd, maybe my pc's problem? I used win7 64 bit
Upload log
Log is here
avicohh said:
Upload log
Click to expand...
Click to collapse
{
"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"
}
HELP ME
I ALSO USE STOCK FIRMWARE THAT U GIVE ABOVE G532GDXU1APL1 ,
sometimes there is a messege in CMD that saying ADB out of date :/
I believe it something in your computer.
Try another one.
avicohh said:
Upload log
Click to expand...
Click to collapse
avicohh said:
I believe it something in your computer.
Try another one.
Click to expand...
Click to collapse
another one??????
alfanjawa8 said:
I ALSO USE STOCK FIRMWARE THAT U GIVE ABOVE G532GDXU1APL1 ,
sometimes there is a messege in CMD that saying ADB out of date :/
Click to expand...
Click to collapse
@avicohh WHY SUPERUSER CANNOT BE READ?
Try with another computer.
I my god it is now ask for password, and i have no z2x box to unlock it :/
So maybe @bolda.mia is wrong.
The reason the device ask for password is because the custom boot is based on G532GDXU1APL1 and you have a newer system version. (I think is something related to storage encryption, I don't know exactly)
That's why I said this method should work only on G532GDXU1APL1.
Anyway, flash the stock version back. I believe it will fix the problem even without wipe.
before root, I already flash to lower version brother
avicohh said:
so maybe @bolda.mia is wrong.
The reason the device ask for password is because the custom boot is based on g532gdxu1apl1 and you have a newer system version. (i think is something related to storage encryption, i don't know exactly)
that's why i said this method should work only on g532gdxu1apl1.
Anyway, flash the stock version back. I believe it will fix the problem even without wipe.
Click to expand...
Click to collapse
i know exactly, that i already flashing with the lower rom such as pl1 pk3 etc. And the result is same, ask for password my brother!
{
"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"
}
This is only for Honor 9 (STF)
Code:
OpenKirin presents unofficial TWRP for stock EMUI 5.x.
Intended for usage on stock emui 5.x in combination with unlocked bootloader .
Installation Instructions
Code:
1. Enter fastboot mode on unlocked device
2. flash recovery using the following command: fastboot flash recovery twrp-3.1.1-1-stf.img
3. reboot to recovery!
Downloads
Code:
[LIST]
[STRIKE][URL="https://mega.nz/#!C0RmiCZT!2LwBaeWnNDM-cMVjQCq19a60crWOUytS4y_5Ml8sDhk"][U]download twrp-3.1.1-0-stf.img[/U][/URL][/STRIKE]
Temporary Solution
[URL="https://www.androidfilehost.com/?fid=745849072291684672"]twrp-3.1.1-1-stf.img[/URL] md5: db84a0c2780e010369c6e365277d17e7
[/LIST]
FAQ
Code:
Q: What's the code status?
A: 9. August 2017
Q: which H9 models are supported?
A: every model should be supported.
Q: Can i use this TWRP with decrypted /data?
A: Yes you can! (Check FAQ)
Q: Can i install Magisk?
A: No (encrypted /data), Yes (decrypted /data)
Q: Does official SuperSU work?
A: No (encrypted /data), Yes (decrypted /data)
Q: ETAs?
A: No.
Going back from decrypted -> encrypted?
Code:
1. Format /data inside of TWRP
2. Flash eRecovery & Kernel from your currently installed Stock ROM Build
3. Do a factory reset inside of eRecovery
5. Let device boot up
6. Install your current firmware hw_data package & SuperSU using TWRP again
Want to decrypt? No problem.
Code:
1. Format /data inside of TWRP
2. Flash a kernel with fileencryption disabled in fstab
3. bootup your device
Special Thanks
Code:
* [URL="https://forum.xda-developers.com/member.php?u=2335078"]surdu_petru[/URL]
* [URL="https://forum.xda-developers.com/member.php?u=7354786"]XePeleato[/URL]
* [user=2235607]@Svetius[/user]
XDA:DevDB Information
TWRP, Tool/Utility for the Honor 9
Contributors
OldDroid, surdu_petru, XePeleato
Source Code: https://github.com/OpenKirin
Version Information
Status: Beta
Created 2017-08-10
Last Updated 2017-10-28
Hi
How do I decrypt data?
alorenz87 said:
Hi
How do I decrypt data?
Click to expand...
Click to collapse
Please, are you able to read the OP
Awesome, Thanks OpenKirin & Old Droid!! Cant wait for a LineageOS
Switched from HTC 10 to H9. My Device is coming in the next 2 Day's.
TWRP is must have!
I would thank u for ur work!
SuperSU 2.82 SR2 confirmed working, have it running atm on my H9.
Can i flashable this in Chinese twrp?
Sorry for the noob question, but how to i enter twrp once its flashed?
I can enter eRecovery but this doesnt seem to be the right thing.
Edit: i found it: Volume up + tap power button: Recovery mode (reboot / factory reset / wipe cache options or TWRP if flashed)
albiboard said:
Sorry for the noob question, but how to i enter twrp once its flashed?
I can enter eRecovery but this doesnt seem to be the right thing.
Edit: i found it: Volume up + tap power button: Recovery mode (reboot / factory reset / wipe cache options or TWRP if flashed)
Click to expand...
Click to collapse
Power + VOL up is right
new update soon - data decryption has been fixed up to a certain extend, thanks to our dear team member and developer @XePeleato. TWRP will be able to decrypt your personal data when no loclscreen password/pin/pattern/fingerprint is set (because this is bound to your decryption key).
Backup of decrypted data will be possible aswell.
Best regards
What is the exact difference to the chinese TWRP Version?
Also can I just flash the image via the chinese TWRP?
Great! I edited my thread recommending every user to use this official TWRP.
Anybody can explain a beginner (me) what's up with that encrypted /decrypted thing?
When I use fingerprint all my Data is encrypted and when I remove Fingerprint it's decrypted?
I know flashing recovery only from other smartphones, just flash it and done that encrypted/decrypted thing is confusing me a bit. So what I need to do to get it exactly to work. Step-by-step guide would be appreciated.
screenshot is from encrypted h9!
device booted fine, update soon ...
OldDroid said:
screenshot is from encrypted h9!
device booted fine, update soon ...
Click to expand...
Click to collapse
I'll keep my fingers crossed
OldDroid said:
screenshot is from encrypted h9!
device booted fine, update soon ...
Click to expand...
Click to collapse
That is magnificent, good job
4r44444 said:
Anybody can explain a beginner (me) what's up with that encrypted /decrypted thing?
When I use fingerprint all my Data is encrypted and when I remove Fingerprint it's decrypted?
I know flashing recovery only from other smartphones, just flash it and done that encrypted/decrypted thing is confusing me a bit. So what I need to do to get it exactly to work. Step-by-step guide would be appreciated.
Click to expand...
Click to collapse
Yep, I am with you! Coming from OnePlus 1 I never had sth to do with decrypt/encrypt.
Can I do a temporary boot into TWRP with an locked bootloader? Just use fastboot to boot into TWRP once?
My phone is like factory right now (locked BL, no root and I dont know encryption status etc) and I don't wanna root or anything just yet so I can get stock updates more easily. But I just want to push and pull a few phone files using adb on my PC.
I mean I'm wondering, can I run adb commands to push and pull system files and set their permissions using the stock recovery?
Zorigo said:
Can I do a temporary boot into TWRP with an locked bootloader? Just use fastboot to boot into TWRP once?
My phone is like factory right now (locked BL, no root and I dont know encryption status etc) and I don't wanna root or anything just yet so I can get stock updates more easily. But I just want to push and pull a few phone files using adb on my PC.
I mean I'm wondering, can I run adb commands to push and pull system files and set their permissions using the stock recovery?
Click to expand...
Click to collapse
Nope and you'll brick your phone if you relock bootloader after installing twrp (or at least it won't boot).
lsvet1 said:
Nope and you'll brick your phone if you relock bootloader after installing twrp (or at least it won't boot).
Click to expand...
Click to collapse
Best case scenario is it will trigger FRP lock.
Sent from my Honor 8 using XDA Labs
So when it comes to the newly released EMUI8 for Honor 9 things get a little bit tricky, as we don't have any official update for our region yet (only for C900 and AL variants - chinese).
Every file i provided have been built during the way finding how stuff works on oreo - and alot of stuff changed EDIT: Official update is out for C432 - i recommend to not use the provided TWRP for daily, reliable usage.
PART 1
0. download the B360a zip from my mega folder
1. read README.txt from fw zip and follow the steps carefully (easy install)
2. have fun with official oreo
Rollback instructions
1. copy the rollback zip and nocheck recovery (!!oreo version!!) to the root of your MicroSD card
2. enable usb debugging in developer options
3. connect your phone to your computer, start an adb shell and issue the following commands:
Code:
dd if=/storage/sdcard1/STF_RECOVERY_OREO_NoCheck.img of=/dev/block/bootdevice/by-name/recovery_ramdisk
dd if=/storage/sdcard1/STF_RECOVERY_OREO_NoCheck.img of=/dev/block/bootdevice/by-name/erecovery_ramdisk
echo --update_package=/sdcard/update_rollback_al10c00b190.zip > /cache/recovery/command
4. last but not least reboot recovery, again in adb shell:
Code:
reboot recovery
5. your device should start to flash a chinese version of nougat (EMUI 5.1)
hint: if you get an error during the installation, just press the reboot button, it still boots.
device crashes during boot? do a low-level data partition format, boot into erecovery when you get asked to.
6. prepare the MicroSD (8gb atleast, exFAT formatted)
download the C432 firmware and extract it
copy the dload folder you extracted to the root of your MicroSD
7. if required unlock your bootloader
8. flash the nocheck recovery (nougat version) to recovery and recovery2 partition using fastboot
Code:
fastboot flash recovery STF_RECOVERY_NoCheck.img
fastboot flash recovery2 STF_RECOVERY_NoCheck.img
9. boot your device into force dload mode (keep vol+, vol- and power pressed until the installation starts)
10. you should boot into a fresh L09C432B100 installation
I've uploaded every file you need for the process to mega.nz - please do not mirror any of the stuff provided!
[url]https://mega.nz/#F!W1QUAIbZ!7Gbf79dC6NwD1e_zdY_O3Q[/URL]
Huge thanks to @LastStandingDroid for providing the modified SuperSU installation package.
Best Regards,
OldDroid
To fix the file manager, open your root file explorer and follow the steps carefully:
1. create a folder called "normal" in /cust/hw
2. create a second folder in the previously created one, name it "app"
3. now move HwCloudDrive_Local folder from /cust/hw/eu/app to /cust/hw/normal/app
4. reboot
Thank you!
I'll try it!
Does bootloader uncloked ?
After I done the factory reset my themes lost again, and the boot animation too...and the apps....
I mean, I done everithing what you said and the themes come back...but after i relocked the bootloader its gone....like if i didn't do anithing :S (sorry for my bad English)
Should i try again?
BobekMark said:
After I done the factory reset my themes lost again, and the boot animation too...and the apps....
I mean, I done everithing what you said and the themes come back...but after i relocked the bootloader its gone....like if i didn't do anithing :S (sorry for my bad English)
Should i try again?
Click to expand...
Click to collapse
don't relock the bootloader after the whole process
OldDroid said:
don't relock the bootloader after the whole process
Click to expand...
Click to collapse
Ohh.... i see...ty
i will try it again
---------- Post added at 06:14 PM ---------- Previous post was at 05:19 PM ----------
{
"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"
}
This is my result. :\
It's okay, or there should be some other apps? Or should it be C432 instead of C900 ? :S
(There is no Huawei Account option :S )
BobekMark said:
Ohh.... i see...ty
i will try it again
---------- Post added at 06:14 PM ---------- Previous post was at 05:19 PM ----------
This is my result. :\
It's okay, or there should be some other apps?
(There is no Huawei Account option :S )
Click to expand...
Click to collapse
which h9 version do you have, C432?
OldDroid said:
which h9 version do you have, C432?
Click to expand...
Click to collapse
Yes (I updated the pictures)
BobekMark said:
Yes (I updated the pictures)
Click to expand...
Click to collapse
thats normal, your phone is still running c432, this is just a ui thing, if it disturbs you i can post the path where the version is beeing set
OldDroid said:
thats normal, your phone is still running c432, this is just a ui thing, if it disturbs you i can post the path where the version is beeing set
Click to expand...
Click to collapse
And the apps are ok?
When i was in the root explorer i still see applications like File Manager and Huawei apps :S
BobekMark said:
And the apps are ok?
When i was in the root explorer i still see applications like File Manager and Huawei apps :S
Click to expand...
Click to collapse
where did you find them?
I have problem with installation.
I have NTFS system files on my SD card and i can't mount this card in TWRP.
What i have to do?
Format to FAT32 or what?
So awesome, thank you for that.
Is there a version of this that will work the same or similar on the P10 (standard P10). Thanks
OldDroid said:
where did you find them?
Click to expand...
Click to collapse
There
BobekMark said:
There
Click to expand...
Click to collapse
Install em as normal apk it'll be visible.
I don't like your settings it looks so color less
[emoji6]
Sent from my DUK-L09 using Tapatalk
LastStandingDroid said:
Install em as normal apk it'll be visible.
I don't like your settings it looks so color less
[emoji6]View attachment 4337715View attachment 4337718View attachment 4337719
Sent from my DUK-L09 using Tapatalk
Click to expand...
Click to collapse
Ok...but i don't have Huawei "Support" or account or idk what.....but for example...the themes app is different, because i can't log in any Huawei Account ...it's not an option to log in :\
Hi! And first of all, thanks a lot for this guide as you just gave hopeless H9 owners a bit of light...
Now I haven't gone through the process yet but I got a bit confused as of part.3 (that is recommended but not needed), should we unroot BEFORE flashing Ramdisk and Recovery Ramdisk? I then have an old UnSu script by Osmosis, would it work or the "Full Unroot" option from the SuperSu app is okay?
Thanks in advance for your reply and Thanks again for this guide!! Cheers
BobekMark said:
Ok...but i don't have Huawei "Support" or account or idk what.....but for example...the themes app is different, because i can't log in any Huawei Account ...it's not an option to log in :\
Click to expand...
Click to collapse
Install huawei services from play store but it won't help ;P
Because online themes is disabled by default
Sent from my DUK-L09 using Tapatalk
EXAMPLE: USE IN ROM NA V1.18
1) Install Magisk.apk.
2) Unpack ROM V1.18 and copy file boot.img of system to smartphone.
3) Open app Magisk in smartphone and pick line Magisk -> Install -> Install -> "Select file patch" and pick file boot.img copy of 2).
4) Please wait Magisk flash ok and copy file /Download/magisk_patched.img to folder adb in PC.
5) Connect smartphone to PC=cable USB Type C and Open cmd in folder adb and type line command:
adb devices
adb reboot bootloader
fastboot devices
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash boot magisk_patched.img
6) Please wait flash ok and reboot system. Enjoy
***NO DATA LOSS***
*Picture:
{
"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"
}
Pic 1: https://drive.google.com/file/d/1-GbpwW1GuotqBLxFBfID43EQwfkaYrY1/view?usp=drivesdk
Pic 2: https://drive.google.com/file/d/1-MIidp3OlzApxgcGkhRyQO2N25vPza6r/view?usp=drivesdk
It wont remove my data right? And it's safe?
---------- Post added at 04:20 PM ---------- Previous post was at 04:18 PM ----------
One more question how to get the boot.img in the first place?
souma_rox said:
It wont remove my data right? And it's safe?
---------- Post added at 04:20 PM ---------- Previous post was at 04:18 PM ----------
One more question how to get the boot.img in the first place?
Click to expand...
Click to collapse
Extract it from Rom zip.
Enviado desde mi NX629J mediante Tapatalk
Tryed it. Resulted in a your device is corrupt.
Easy fox if you guys try this.
Download the recovery tool posted. Fallow those instructions. Then download the NA ROM red magic and put the zip in the root of the phone. On the phone go to system update and update front hat zip and you are back up and running on V1.18
bignazpwns said:
Tryed it. Resulted in a your device is corrupt.
Easy fox if you guys try this.
Download the recovery tool posted. Fallow those instructions. Then download the NA ROM red magic and put the zip in the root of the phone. On the phone go to system update and update front hat zip and you are back up and running on V1.18
Click to expand...
Click to collapse
He left out an important step. This needs to be done BEFORE doing anything on the phone.
"4. open cmd, then type adb reboot bootloader , then phone will reboot to fastboot mode.
5. Use fastboot flashing unlock, use volume key select unlock , confirm with power button , then the phone will do factory reset and reboot. Now the phone is unlocked"
Can I do that on my red magic 3s?
Thank
thanks finally
So I can flash without unlocking bootloader? I've got to much info on this phone to just let it be erased. And don't have the time to copy everything before doing it. I appreciate your time
gdaddy3315 said:
So I can flash without unlocking bootloader? I've got to much info on this phone to just let it be erased. And don't have the time to copy everything before doing it. I appreciate your time
Click to expand...
Click to collapse
Nope. U have to unlock first which will erase ur drive. I think the instructions here are incomplete to unlock the bootloader. Search for main thread
Can i hv the changelogs?
good work but lost my wifi i.e bricked
I try yhis 100 time . Totally i got : device is corrupt . What problem why some pple can root it and others cant.
hoichemgio9x said:
EXAMPLE: USE IN ROM NA V1.18
1) Install Magisk.apk.
2) Unpack ROM V1.18 and copy file boot.img of system to smartphone.
3) Open app Magisk in smartphone and pick line Magisk -> Install -> Install -> "Select file patch" and pick file boot.img copy of 2).
4) Please wait Magisk flash ok and copy file /Download/magisk_patched.img to folder adb in PC.
5) Connect smartphone to PC=cable USB Type C and Open cmd in folder adb and type line command:
adb devices
adb reboot bootloader
fastboot devices
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash boot magisk_patched.img
6) Please wait flash ok and reboot system. Enjoy
***NO DATA LOSS***
*Picture:
Click to expand...
Click to collapse
I want to unroot my phone and restore stock boot image so what should I do first? Uninstall magisk or flash the stock boot image first?
souma_rox said:
I want to unroot my phone and restore stock boot image so what should I do first? Uninstall magisk or flash the stock boot image first?
Click to expand...
Click to collapse
You flash stock boot image and device unroot
souma_rox said:
I want to unroot my phone and restore stock boot image so what should I do first? Uninstall magisk or flash the stock boot image first?
Click to expand...
Click to collapse
sherreer said:
I try yhis 100 time . Totally i got : device is corrupt . What problem why some pple can root it and others cant.
Click to expand...
Click to collapse
you may have missed or missed a certain step
ghostknightfire said:
good work but lost my wifi i.e bricked
Click to expand...
Click to collapse
People still function normally. Which ROM do you flash for?
ghostknightfire said:
Can i hv the changelogs?
Click to expand...
Click to collapse
Please describe in more detail
lionhealth said:
Can I do that on my red magic 3s?
Thank
Click to expand...
Click to collapse
yes. You can. Good luck
gdaddy3315 said:
So I can flash without unlocking bootloader? I've got to much info on this phone to just let it be erased. And don't have the time to copy everything before doing it. I appreciate your time
Click to expand...
Click to collapse
Unlocking bootloader not loss data
Greeting!
Anyone here that can help me. I have a Realme C12 a year ago It was updated to Android 11 but it was very unstable so I flashed back to Android 10. Now I want to flash Android 11 again but I tried flashing RMX2189_11_C.11 but it bricked my phone. Anyone know where I can download Android 11 Firmware for Sp Flash Tool.
Where you got C.11 update file to flash?
HemanthJabalpuri said:
Where you got C.11 update file to flash?
Click to expand...
Click to collapse
There are so many website to download them.
Such as:
Download Realme C12 RMX2189 Stock Firmware [Flash File]
www.firmware27.info
Realme C12 Firmware (RMX2189, RMX2184) - Realme Firmware
Realme C12 Firmware (RMX2189, RMX2184), Official Flash File (Stock ROM). flash your phone using realme flashtool or MSM Download tool.
realmefirmware.com
I have tried every file. OZIP. Ofp. Every version with Ui 2.0 on both my Realme C12 but they don't work. Realme Flash Tool also say a error that suggest that the file is not for this device. But it is.
So if you can help me. Find Realme Ui 2.0 so I can flash with Realme Flash Tool, or using recovery, or SP Flash tool. I would really appreciate.
Btw I have flash the stock ROM which I got from here:
but I still need Ui 2.0. Also one of my Realme C12 did get the updated RMX2189_11_C.04. I updated it normally from the settings and all but that also made my phone stuck on Orange State. So I flashed back to stock.
@RehanRashid
I made C.11 ozip that you can flash in TWRP, so unlock bootloader and flash TWRP to flash this ozip. Don't forget to use nocrypt variant of TWRP from my thread. Also Format Data using `fastboot -w` after flashing ozip.
RMX2189_11.C.11_1110_202203092226.zip
drive.google.com
Let me know if you get any issues
Thanks
HemanthJabalpuri said:
@RehanRashid
I made C.11 ozip that you can flash in TWRP, so unlock bootloader and flash TWRP to flash this ozip. Don't forget to use nocrypt variant of TWRP from my thread. Also Format Data using `fastboot -w` after flashing ozip.
RMX2189_11.C.11_1110_202203092226.zip
drive.google.com
Let me know if you get any issues
Thanks
Click to expand...
Click to collapse
Thanks Bro. I will update you.
HemanthJabalpuri said:
@RehanRashid
I made C.11 ozip that you can flash in TWRP, so unlock bootloader and flash TWRP to flash this ozip. Don't forget to use nocrypt variant of TWRP from my thread. Also Format Data using `fastboot -w` after flashing ozip.
RMX2189_11.C.11_1110_202203092226.zip
drive.google.com
Let me know if you get any issues
Thanks
Click to expand...
Click to collapse
Bro I have booted into TWRP nocrypt variant. But upon clicking Install or File Manager. All the folders are showing as random names or numbers. The non nocrypt variant works fine.
RehanRashid said:
Bro I have booted into TWRP nocrypt variant. But upon clicking Install or File Manager. All the folders are showing as random names or numbers. The non nocrypt variant works fine.
Click to expand...
Click to collapse
Yeah, it is because decryption is removed from that variant. I thought you can use Micro SD Card. ADB sideload will work too.
HemanthJabalpuri said:
Yeah, it is because decryption is removed from that variant. I thought you can use Micro SD Card.
Click to expand...
Click to collapse
Can you link me the way to do it through ADB Sideload?
HemanthJabalpuri said:
Yeah, it is because decryption is removed from that variant. I thought you can use Micro SD Card. ADB sideload will work too.
Click to expand...
Click to collapse
How to Flash Custom ROM using ADB sideload [Easy Steps]
Flash Custom ROM zip file with ADB and Fastboot commands on any Android phone. Install Custom Firmware without TWRP recovery using CMD.
www.droidthunder.com
This guide?
RehanRashid said:
How to Flash Custom ROM using ADB sideload [Easy Steps]
Flash Custom ROM zip file with ADB and Fastboot commands on any Android phone. Install Custom Firmware without TWRP recovery using CMD.
www.droidthunder.com
This guide?
Click to expand...
Click to collapse
Yes, in short
- Enable enable 'Skip Treble compatible error' in TWRP Settings
- Go to Advanced => ADB Sideload
- Swipe the bar and connect to PC
- Place the .ozip in your PC and run sideload command
- `adb sideload C.11.ozip`
- After completing, boot to bootloader mode and run `fastboot -w`
HemanthJabalpuri said:
Yes, in short
- Enable enable 'Skip Treble compatible error' in TWRP Settings
- Go to Advanced => ADB Sideload
- Swipe the bar and connect to PC
- Place the .ozip in your PC and run sideload command
- `adb sideload C.11.ozip`
- After completing, boot to bootloader mode and run `fastboot -w`
Click to expand...
Click to collapse
Stupid Question but does it matter if the file extension is .zip or .ozip?
HemanthJabalpuri said:
Yes, in short
- Enable enable 'Skip Treble compatible error' in TWRP Settings
- Go to Advanced => ADB Sideload
- Swipe the bar and connect to PC
- Place the .ozip in your PC and run sideload command
- `adb sideload C.11.ozip`
- After completing, boot to bootloader mode and run `fastboot -w`
Click to expand...
Click to collapse
Thanks it worked! Btw how did you get the Zip file. For some reason I dont get update in settings so when the next update rolls out, How can I update then?
RehanRashid said:
Stupid Question but does it matter if the file extension is .zip or .ozip?
Click to expand...
Click to collapse
Ah, I forgot that it is a zip file. Anyway, it doesn't matter ozip or zip.
RehanRashid said:
Thanks it worked! Btw how did you get the Zip file. For some reason I dont get update in settings so when the next update rolls out, How can I update then?
Click to expand...
Click to collapse
I got C.11 update(at that time it latest) when I am on C.05 and grabbed the update. I don't know how to update to newer versions like C.13 if you can't get it in settings. I can't make newer versions right now since I don't have PC anymore to experiment things.
Thanks
@RehanRashid
I guess you are still in C.11 and if it is then Can you please run below commands and give me getprop.txt file in Internal Storage please. with this I will try to make C.13 zip
`adb shell`
`getprop >/sdcard/getprop.txt`
HemanthJabalpuri said:
@RehanRashid
I guess you are still in C.11 and if it is then Can you please run below commands and give me getprop.txt file in Internal Storage please. with this I will try to make C.13 zip
`adb shell`
`getprop >/sdcard/getprop.txt`
Click to expand...
Click to collapse
{
"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"
}
Sorry bro for some reason, I never got an notification for your message. Hopefully, I can still help.