Trouble flashing TWRP onto my Huawei Honor 6X
{
"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"
}
I'm having trouble flashing TWRP onto my Huawei Honor 6X.
I was able to unlock the phone (had to pay DC Unlocker for the code, only 4 euros) and get it to boot into fastboot with ADB.
But when I try to flash TWRP, it seems to work, but it goes WAY too fast, or so it seems to me. Here's the DOS output:
C:\adb>fastboot flash recovery twrp-3.1.0-0-berlin.img
target reported max download size of 471859200 bytes
sending 'recovery' (25226 KB)...
OKAY [ 0.712s]
writing 'recovery'...
OKAY [ 0.179s]
finished. total time: 0.894s
Click to expand...
Click to collapse
.....................................
That seems a bit fast to flash a 25mb file. I tried two different TWRP images.
After this apparent ADB flash of TWRP, when I try to boot in to recovery, it just takes me to the normal Huawei EMUI recovery, not TWRP. I have successfully done this with other devices, but I've never had this problem.
Am I missing something? Can I try a different Recovery? ( I did not find another custom recovery but i install all of the TWRP Version match with my Phone from TWRP.me but i can't log into twrp just huawei eRecovery opened...)
Also the device is definitely unlocked as I get an unlocked warning on boot.
my ROM Device is: STOCK android 7.0 EMUI 5.0.4
I searched almost the entire internet cannot find any another custom ROM like lineageos or cyanogenmod...
deadking said:
Trouble flashing TWRP onto my Huawei Honor 6X
I'm having trouble flashing TWRP onto my Huawei Honor 6X.
I was able to unlock the phone (had to pay DC Unlocker for the code, only 4 euros) and get it to boot into fastboot with ADB.
But when I try to flash TWRP, it seems to work, but it goes WAY too fast, or so it seems to me. Here's the DOS output:
.....................................
That seems a bit fast to flash a 25mb file. I tried two different TWRP images.
After this apparent ADB flash of TWRP, when I try to boot in to recovery, it just takes me to the normal Huawei EMUI recovery, not TWRP. I have successfully done this with other devices, but I've never had this problem.
Am I missing something? Can I try a different Recovery? ( I did not find another custom recovery but i install all of the TWRP Version match with my Phone from TWRP.me but i can't log into twrp just huawei eRecovery opened...)
Also the device is definitely unlocked as I get an unlocked warning on boot.
my ROM Device is: STOCK android 7.0 EMUI 5.0.4
I searched almost the entire internet cannot find any another custom ROM like lineageos or cyanogenmod...
Click to expand...
Click to collapse
Just try patching your boot.img by magisk and flashing it to disable dm verity. Then try flashing your TWRP.
Tab E said:
Just try patching your boot.img by magisk and flashing it to disable dm verity. Then try flashing your TWRP.
Click to expand...
Click to collapse
dear TAb E thanks for your Answer... i don't have the Boot.img file just TWRP Recovery... where i can find the boot.img and magisk ? can u send me any guide ? sorry for ask to ask... im not looking for a bite to eat just confused... i dont have any custom ROM and i cant find any rom on the internet... if i flash magisk on my STOCk rom its not break ?
deadking said:
dear TAb E thanks for your Answer... i don't have the Boot.img file just TWRP Recovery... where i can find the boot.img and magisk ? can u send me any guide ? sorry for ask to ask... im not looking for a bite to eat just confused... i dont have any custom ROM and i cant find any rom on the internet... if i flash magisk on my STOCk rom its not break ?
Click to expand...
Click to collapse
Installation
The Magic Mask for Android
topjohnwu.github.io
You can get the boot.img form your phones stock firmware
Tab E said:
Installation
The Magic Mask for Android
topjohnwu.github.io
You can get the boot.img form your phones stock firmware
Click to expand...
Click to collapse
Dear Tab E Hello Again,
sry for any inconvenience.
I am installing magisk and I have a question, There are two options in the installation process: Preserve AVB 2.0/dm verity and Preserve force encyption... The first option is not checked but Second option checked by default... Do I need to choose also the first option or not?
thanks for your help <3
deadking said:
Dear Tab E Hello Again,
sry for any inconvenience.
I am installing magisk and I have a question, There are two options in the installation process: Preserve AVB 2.0/dm verity and Preserve force encyption... The first option is not checked but Second option checked by default... Do I need to choose also the first option or not?
thanks for your help <3
Click to expand...
Click to collapse
Untick preserve avb
Untick fore encryption.
by default you want to check both but if you want full control and freedom over your device uncheck both
ineedroot69 said:
by default you want to check both but if you want full control and freedom over your device uncheck both
Click to expand...
Click to collapse
Hello Dear thx for your help and your reply, when i uncheck two of option when i flash it on my device , ita got soft brick and i cant boot my phone anymore... just show Huawei logo then reboot... again nd again...and need install stock firmware again... anyway i think i cant uncheck both there is any way to uncheck without break ?
Looks like your phone is not booting with magisk. Is there any thing called 'vbmeta' in your stock rom?
If yes go to fastboot and use these commands
fastboot –disable-verity –disable-verification flash vbmeta vbmeta.img
fastboot erase recovery
fastboot flash recovery recovery.img
Fastboot boot recovery.img
fastboot reboot
Tab E said:
If yes go to fastboot and use these commands
fastboot –disable-verity –disable-verification flash vbmeta vbmeta.img
fastboot erase recovery
fastboot flash recovery recovery.img
Fastboot boot recovery.img
fastboot reboot
Click to expand...
Click to collapse
Dear TAB E, I sincerely thank you for your help.
i check the UPDATE.APP STOCK FirmWare There was no file named vbmeta.img in it,I repeated the installation steps in MAGISK But this time I did not make any special changes in the settings. Preserve AVB 2.0/dm verity is uncheck second option is checked by Default... There was no problem and the phone turned on, i wanna changin my serial number where i can find that ROOT FILE from my phone ? any address ?
DELETED
Sorry I misread the question
Tab E said:
Sorry I'm not able to find the issue that is causing this. Would you please downlaod the magisk manager app and tell me the status of ramdisk?
Click to expand...
Click to collapse
yes it's write YES. I managed to install it, when i unCheck two option i got soft brick. so i UNCHECK just DM VERITY and its working for me. now i use the ROOT ACCESS. just i have one question dear TAB E where i can find the file of IMEI and serial number ? Which folder in root access ? do you know ? cause i use XPOSED and Device ID changer it work fine for IMEI but my Serial number not changed i use so apps... but just IMEI changed and Serial number still STOCK. where i can find serial number file/Folder ?
Sincerely thanks for your replies...
DELETED. SORRY AGAIN MISREAD THE QUESTION
deadking said:
yes it's write YES. I managed to install it, when i unCheck two option i got soft brick. so i UNCHECK just DM VERITY and its working for me. now i use the ROOT ACCESS. just i have one question dear TAB E where i can find the file of IMEI and serial number ? Which folder in root access ? do you know ? cause i use XPOSED and Device ID changer it work fine for IMEI but my Serial number not changed i use so apps... but just IMEI changed and Serial number still STOCK. where i can find serial number file/Folder ?
Sincerely thanks for your replies...
Click to expand...
Click to collapse
Oh you were talking about imei. You can get that on your mobile box. There is normally a sticker on that box. Please be careful with a wrong imei. A wrong imei or changing an IMEI is a crime in some nations
Tab E said:
Oh you were talking about imei. You can get that on your mobile box. There is normally a sticker on that box. Please be careful with a wrong imei. A wrong imei or changing an IMEI is a crime in some nations
Click to expand...
Click to collapse
yes dear i know official imei write on the BOX but i wanna change it from root access. my question is: where i can find IMEI System file from root ACCESS ? which folder or file ? i need to change my STATUS device INFO like imei and serial number
Tab E said:
Sorry I don't know about that. You can check system/buildprop but I'm not sure.
Click to expand...
Click to collapse
deadking said:
yes it's write YES. I managed to install it, when i unCheck two option i got soft brick. so i UNCHECK just DM VERITY and its working for me. now i use the ROOT ACCESS. just i have one question dear TAB E where i can find the file of IMEI and serial number ? Which folder in root access ? do you know ? cause i use XPOSED and Device ID changer it work fine for IMEI but my Serial number not changed i use so apps... but just IMEI changed and Serial number still STOCK. where i can find serial number file/Folder ?
Sincerely thanks for your replies...
Click to expand...
Click to collapse
Have you orderd the phone online? If yes the online bill also contains the imei and serial number.
UOTE="deadking, post: 84768353, member: 6928731"]
yes dear i know official imei write on the BOX but i wanna change it from root access. my question is: where i can find IMEI System file from root ACCESS ? which folder or file ? i need to change my STATUS device INFO like imei and serial number
[/QUOTE]
Tab E said:
Have you orderd the phone online? If yes the online bill also contains the imei and serial number.
Click to expand...
Click to collapse
yes i buy it from online store but not officially for that reason i search in ROOT/System file for find SERIAL Number FILE to change it from STOCK to Custom. i dont want to use stock serial number I do not want anyone to search the phone
Related
this thread is solved !
you basically only need to flash the AP part of an original stock rom which you can download from here:
https://updato.com/firmware-archive-select-model
flash it with odin in downloadmode (you even keep all your apps and settings) ..
{
"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"
}
-------------------------------------------------------------------------------------------------------------------
device: SM-G930F ...
on stock firmware , oreo september 2018 update
installed twrp and magisk
i dont know why it happend
maybe
A) because i finally made a google account ( i didnt want to but thought i just remove it after downloading apps from the appstore )
or B) forgetting to RE-enable oem unlock option, after installing twrp and magisk ...
the frp lock began after i once went into download mode (but didnt flash anything , i wanted to go to twrp but pressed the wrong button so i ended up in download mode)
but it could also be the google lock .
anyways the phone doesnt start anymore so i cannot input my google account credentials .
DO I JUST HAVE TO WAIT FOR 72 HOURS ?
this is the code in odin mode :
I have a full twrp backup of everything on my sdcard , can this help me ?
I also know my google credentials and my phone number is registered.
MY QUESTIONS:
1) which image should i flash ? the newest oreo (8.0) update from december or an earlier version ?
2) do i have to wait for 72 hours ?
3) im in the eu and the phone is 4 days old , should i just claim my warranty or ist it even fixable ? the version before was from september 2018
see here for all versions : which one should i choose ?
https://updato.com/firmware-archive...0F&exact=1&r=VD2&v=Oreo(Android+8.0.0)&rpp=15
thanx in advance , please help me guys
edit: i read that if nothing help i have to flash combination rom for bootloader v3 , is this the correct combination rom ?
http://forum.gsmhosting.com/vbb/f777/g930f-combination-binary-3-download-no-password-2471123/
Ulf3000 said:
device: SM-G930F ...
on stock firmware
installed twrp and magisk
i dont know why it happend
maybe
A) because i finally made a google account ( i didnt want to but thought i just remove it after downloading apps from the appstore )
or B) forgetting to RE-enable oem unlock option, after installing twrp and magisk ...
the frp lock began after i once went into download mode (but didnt flash anything , i wanted to go to twrp but pressed the wrong button so i ended up in download mode)
but it could also be the google lock .
anyways the phone doesnt start anymore so i cannot input my google account credentials .
DO I JUST HAVE TO WAIT FOR 72 HOURS ?
this is the code in odin mode :
I have a full twrp backup of everything on my sdcard , can this help me ?
I also know my google credentials and my phone number is registered.
MY QUESTIONS:
1) which image should i flash ? the newest oreo (8.0) update from december or an earlier version ?
2) do i have to wait for 72 hours ?
3) im in the eu and the phone is 4 days old , should i just claim my warranty or ist it even fixable ? the version before was from september 2018
see here for all versions : which one should i choose ?
https://updato.com/firmware-archive...0F&exact=1&r=VD2&v=Oreo(Android+8.0.0)&rpp=15
thanx in advance , please help me guys
edit: i read that if nothing help i have to flash combination rom for bootloader v3 , is this the correct combination rom ?
http://forum.gsmhosting.com/vbb/f777/g930f-combination-binary-3-download-no-password-2471123/
Click to expand...
Click to collapse
Your twrp backup should save you..... That happened most likely cause you flashed twrp without OEM unlocked set in developer settings
[emoji3436]I Willl Scarfice For Those That I Love [emoji3434]
PoochyX said:
Your twrp backup should save you..... That happened most likely cause you flashed twrp without OEM unlocked set in developer settings
can i flash or convert the twrp backup ? twrp on the phone is not accessable at the moment , i can only boot into download mode
it happend because you have to wipe and after wiping the developer options are reset ... no tutorial specifically mentions to enable oem unlock again after rooting ...
Click to expand...
Click to collapse
Ulf3000 said:
PoochyX said:
Your twrp backup should save you..... That happened most likely cause you flashed twrp without OEM unlocked set in developer settings
can i flash or convert the twrp backup ? twrp on the phone is not accessable at the moment , i can only boot into download mode
Click to expand...
Click to collapse
You would have to flash stock rom in Odin then go threw the setup process go into developer settings activate the oem unlock twrp and then you should be fine...
[emoji3436]I Willl Scarfice For Those That I Love [emoji3434]
Click to expand...
Click to collapse
PoochyX said:
Ulf3000 said:
You would have to flash stock rom in Odin then go threw the setup process go into developer settings activate the oem unlock twrp and then you should be fine...
ok the latest version from december ? or an older version ? i have downloaded this one :
https://updato.com/firmware-archive-select-model?record=92A63C2C07D011E99F15FA163EE8F90B
edit: is it enough to flash ap ? thats the bootloader and os image i guess ?
edit2:
BL=Bootloader
AP=Applikationen
CP =Modem
CSC=Country Specific Code
correct ? do i have to flash them all or is bl and ap enough or just bl ?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Ulf3000 said:
PoochyX said:
Ulf3000 said:
You would have to flash stock rom in Odin then go threw the setup process go into developer settings activate the oem unlock twrp and then you should be fine...
ok the latest version from december ? or an older version ? i have downloaded this one :
https://updato.com/firmware-archive-select-model?record=92A63C2C07D011E99F15FA163EE8F90B
edit: is it enough to flash ap ? thats the bootloader and os image i guess ?
Click to expand...
Click to collapse
If it's the one you was just using you should be good to go if it's an older one it could not work cuss bootloader locks after certain versions and you can only go up [emoji115]
[emoji3436]I Willl Scarfice For Those That I Love [emoji3434]
Click to expand...
Click to collapse
Click to expand...
Click to collapse
HOLY **** ! it worked
i ONLY flashed AP btw (i installed twrp and magisk to AP ), i didnt flash the other files.
Then it installed
restartet
upgraded system
went into recovery
and then i had to just reboot .. the apps were prepared and istalled and everything is back to normal, just magisk, twrp and xposed are gone ...
NOW IS THERE A WAY TO COMPLETELY DISABLE FPR checking so this can never happen again ???
------------------------------------------------------------------------------------------------------------
edit: thank you so much for ensuring me to just do it ,. i was hesitant becasue i read a lot of horror stories here !
Ulf3000 said:
HOLY **** ! it worked
i ONLY flashed AP btw (i installed twrp and magisk to AP ), i didnt flash the other files.
Then it installed
restartet
upgraded system
went into recovery
and then i had to just reboot .. the apps were prepared and istalled and everything is back to normal, just magisk, twrp and xposed are gone ...
NOW IS THERE A WAY TO COMPLETELY DISABLE FPR checking so this can never happen again ???
------------------------------------------------------------------------------------------------------------
edit: thank you so much for ensuring me to just do it ,. i was hesitant becasue i read a lot of horror stories here !
Click to expand...
Click to collapse
You welcome.....
[emoji3436]I Willl Scarfice For Those That I Love [emoji3434]
mods please put a [SOLVED] in the thread title ,
i think many people fail because BL=Bootloader cannot be flashed when frp bootloop is happening and they try to install all modules at once and then give up or go for unorthodox methods and hardbrick
Ulf3000 said:
mods please put a [SOLVED] in the thread title ,
i think many people fail because BL=Bootloader cannot be flashed when frp bootloop is happening and they try to install all modules at once and then give up or go for unorthodox methods and hardbrick
Click to expand...
Click to collapse
As long as you back up and running [emoji125]
[emoji3436]I Willl Scarfice For Those That I Love [emoji3434]
This is the OnePlus 7's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"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"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
Is TWRP out for the OP7 yet? Or is this AIO tool basically still a work in progress (not all functions operational yet)?
I don't see the OnePlus 7 posted on TWRP's official website. Or on xda for that matter. I can find a couple dodgy "how to root" guides for the OP7, but they just look like clickbait. One just links to the TWRP main page (instead of an actual file download specific to the OP7). Another actually contains links for the OP6! Not just deceptive, but can possibly cause folks problems!
redpoint73 said:
Is TWRP out for the OP7 yet? Or is this AIO tool basically still a work in progress (not all functions operational yet)?
I don't see the OnePlus 7 posted on TWRP's official website. Or on xda for that matter. I can find a couple dodgy "how to root" guides for the OP7, but they just look like clickbait. One just links to the TWRP main page (instead of an actual file download specific to the OP7). Another actually contains links for the OP6! Not just deceptive, but can possibly cause folks problems!
Click to expand...
Click to collapse
Hi, this tool has all function ready for op7 and op7 pro ( i'm only waiting for the branded unlock bootloader procedure). Actually for what i know there is not a twrp available, but in all cases the tool allow you to flash a third part twrp.img and not only the twrps in the list (I can update the twrp list without updating the tool, so when a new working twrp will be released i will add it in the twrp list). The other functions, like reboots, bootloader unlock,or apk installer/uninstaller are perfectly working because they are a bit generic. For the root is the same problem, the tool use the twrp to root the device so without it you can't root the device with the tool. This tool is available for all others OnePlus devices and i'm official TWRP maintainer for Op6 and Op6T, so when a stock rom will be released i will start also to work on the TWRP and the others features.
anyone got the stock recovery for the Oneplus 7?
Thanks for the good work. However, the tool fails for me. I have an unlocked bootloader.
Version: 1.1.1.6
1. MD5 check error after TWRP download
2. Skip MD5 check throws "unable to open zip file" error
3. Deleted all files and tried again - still the same.
hohinder said:
Thanks for the good work. However, the tool fails for me. I have an unlocked bootloader.
Version: 1.1.1.6
1. MD5 check error after TWRP download
2. Skip MD5 check throws "unable to open zip file" error
3. Deleted all files and tried again - still the same.
Click to expand...
Click to collapse
Thanks, give me a second i will check soon
mauronofrio said:
Thanks, give me a second i will check soon
Click to expand...
Click to collapse
after unlocking bootloader google play shows device not certified..
prachetas13 said:
after unlocking bootloader google play shows device not certified..
Click to expand...
Click to collapse
It's normal
hohinder said:
Thanks for the good work. However, the tool fails for me. I have an unlocked bootloader.
Version: 1.1.1.6
1. MD5 check error after TWRP download
2. Skip MD5 check throws "unable to open zip file" error
3. Deleted all files and tried again - still the same.
Click to expand...
Click to collapse
Should be fixed now
mauronofrio said:
It's normal
Because if it netflix does not start.and its tripping safetynet.
will unlock again when magisk support is available.
Click to expand...
Click to collapse
I want to switch to Oxygen OS from hydrogen OS.
How can I switch from hydrogen OS to Oxygen OS using this tool, please?
prachetas13 said:
after unlocking bootloader google play shows device not certified..
Click to expand...
Click to collapse
Magical hide the play store if it bothers you
Hello Dear Creator
I would like to say thanks to you
I have sucessful rooted my Oneplus 7 indian variant (1901) with your latest unofficial twrp img, installer and magisk
Its was too easy to root it
please help me... how unbreak OP7 GM1900??
IlyaSBD said:
please help me... how unbreak OP7 GM1900??
Click to expand...
Click to collapse
You are in an aosp recovery, what do you.need?
mauronofrio said:
You are in an aosp recovery, what do you.need?
Click to expand...
Click to collapse
I can't clean date or reinstall the firmware. when you turn on the phone hangs the Android logo.
IlyaSBD said:
I can't clean date or reinstall the firmware. when you turn on the phone hangs the Android logo.
Click to expand...
Click to collapse
Go in fastboot mode and flash again the twrp
mauronofrio said:
Go in fastboot mode and flash again the twrp
Click to expand...
Click to collapse
Failed / (remote : Flashing is not allowed in Lock State)
Bootloader is locked. And unlocking is blocked...
IlyaSBD said:
Failed / (remote : Flashing is not allowed in Lock State)
Bootloader is locked. And unlocking is blocked...
Click to expand...
Click to collapse
So you should.use the msmtool
mauronofrio said:
So you should.use the msmtool
Click to expand...
Click to collapse
But where can I find MSM for GM1900 ?
IlyaSBD said:
But where can I find MSM for GM1900 ?
Click to expand...
Click to collapse
You should ask to oneplus or you can try to use the msmtool for gm1913 or gm1917.
Your is the chinese version, so you should search for hydrogeng os msmtool
Team Win Recovery Project 3.6.1
{
"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"
}
Special Notes:
DON'T FORGET TO ENABLE "OEM UNLOCK" (located in Developers options)
KNOX will be tripped once you flash custom binaries to your phone. Your warranty may be voided. However this may not affect you if your country forces Samsung to provide hardware warranty regardless of software status
Samsung Firmware OTA (aka System Updates) will no longer work once you flash custom binaries. You can flash custom ROMs if you want to keep the OS up-to-date
All apps that use KNOX like Samsung Pay, Secure Folder and maybe more will no longer work
Download:
Recovery
VBMeta
Multidisabler
Changelog:
21.10.2021
Rebased kernel source to CUH4
16.06.2021
Rebased kernel source to CUC2
03.05.2020
Rebased kernel source to BTB8
25.04.2020
Rebased kernel source to ATA4
07.12.2019
Initial Release
Guide:
If you already have a custom recovery installed:
Boot to your custom recovery
Flash the recovery image
If you are starting from scratch:
Go to Developer Settings and enable "OEM Unlock" option
Power off the device and boot in download mode
In download mode, you will see the long press and volume up option to unlock the bootloader
Unlock the bootloader. That will wipe your device so be sure you made a backup of your data
After bootloader unlock, boot up the phone and make sure it is connected to the internet or it will trigger rmm prenormal
Setup the phone without google account and others
Reboot in download mode and flash the recovery and vbmeta images
Boot to TWRP
Format data in TWRP
Flash the Multidisabler zip
Now you can reboot
Contributors
ponces, geiti94, ianmacd
Source Code: https://github.com/TeamWin/android_device_samsung_a40
Kernel Source Code: https://github.com/ponces/android_kernel_samsung_universal7904
Reserved
I'm really tempted to flash this TWRP and root my A40. Though I know Android 10 has been announced (at least in my region) for April 2020. Should I wait until then? My main concern is, if i flash it now, how easy will it be to upgrade to Android 10 then?
The only real thing I use root privileges for is to remove bloatware completely and edit the hosts file, so I can wait a few months. Also what about dm-verity? Are there any problems there?
My question and can I use this recovery on ITV-A405FNXXU2ASK2-20191218161204?
bishsop said:
I'm really tempted to flash this TWRP and root my A40. Though I know Android 10 has been announced (at least in my region) for April 2020. Should I wait until then? My main concern is, if i flash it now, how easy will it be to upgrade to Android 10 then?
The only real thing I use root privileges for is to remove bloatware completely and edit the hosts file, so I can wait a few months. Also what about dm-verity? Are there any problems there?
Click to expand...
Click to collapse
The choice of waiting is only yours.
In my case I need this as I'm using a custom Treble ROM and not Samsung's firmware.
The ease to upgrade to Android 10 relies only on the your expertise on how to flash the original firmware using ODIN.
At the time of the upgrade you need to use ODIN to flash an original firmware from Android 9 to be able to fully restore the original behavior and flash Android 10.
As far as I'm concerned, DM-Verity is related with both DT and DTBO partitions and those partitions are not even touched during this process.
The ones that are changed are BOOT, RECOVERY and VBMETA to disable a few security procedures from Samsung to be able to flash and boot custom binaries.
Because of this, take in consideration the "Special Notes" section in the first post.
Nevertheless, if the need of changing the hosts file is to block ads, you can reach the same goal by using the "Private DNS" feature introduced in Android 9 as explained here.
costa11 said:
My question and can I use this recovery on ITV-A405FNXXU2ASK2-20191218161204?
Click to expand...
Click to collapse
As you can see in the first post, this TWRP version is for the firmware A405FNXXU2ASJ1 (October's update).
I am still waiting for Samsung to drop A405FNXXU2ASK2 (December's update) sources here to update TWRP.
I'll keep you posted when the sources drop and work on TWRP update begins.
ponces said:
As you can see in the first post, this TWRP version is for the firmware A405FNXXU2ASJ1 (October's update).
I am still waiting for Samsung to drop A405FNXXU2ASK2 (December's update) sources here to update TWRP.
I'll keep you posted when the sources drop and work on TWRP update begins.
Click to expand...
Click to collapse
So I tried to install this recovery on the ASK2 firmware and it worked, there is only one problem when it goes down the brightness does not return anymore remains low! Then another thing I rooted with Magisk is it's not working, come up with an error and then I'll try to take a screenshot!
thank you again for your job
i just updated my rom to the SK2 (downloaded the rom, flashed it with Odin)
then installed you twrp (the SJ1 is OK)
then flashed with magisk manager the boot.img to Root the Rom
and then flashed the param.bin with a better boot logo
thank you so much for your job !!
costa11 said:
Then another thing I rooted with Magisk is it's not working, come up with an error and then I'll try to take a screenshot!
Click to expand...
Click to collapse
Magisk-Root is working for me.
I did this:
[*]Backup of ASJ1 with TWRP
[*]Complete odin flash of ASK1
[*]TWRP - ASJ1 - Version
[*]direct reboot into TWRP
[*]Format Data
[*]Flash Multidisabler
[*]Full Boot
[*]Install Magisk.APK from sd-card
[*]Reboot into TWRP
[*]Flash Magisk
[*]Full boot to check of root access => ok
[*]Reboot into TWRP
[*]Restore of ASJ1-Data
Everything working!
Thanks for the recovery, is working fine with latest ITV (Italian no brand) firmware, to have root is only simple necessary to flash latest Magisk ZIP via twrp (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)
i have a big problem about twrp on my phone
I have followed this thread
But when i flash twrp (i have uncheck "reboot" on odin of course) i can't get access to the recovery mode, when i do power button + volume up it doesn't do nothing and show this :
(I have already unlock my boot loader)
I think its DM VERITY who block the access to recovery mode but i can't disable this, cause i can't get access to twrp :/
Thanks for any answers c:
cioce said:
Thanks for the recovery, is working fine with latest ITV (Italian no brand) firmware, to have root is only simple necessary to flash latest Magisk ZIP via twrp (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)
Click to expand...
Click to collapse
Can confirm it works with ATA4 (region DBT). Same procedure my post above. With restoring Data as last step there isn't anything lost as well... :good:
Be sure to enable usb debugging after flash of new firmware. Otherwise TWRP flash would fail...
:good:
Leak.dll said:
i have a big problem about twrp on my phone
I have followed this thread
But when i flash twrp (i have uncheck "reboot" on odin of course) i can't get access to the recovery mode, when i do power button + volume up it doesn't do nothing and show this :
...
(I have already unlock my boot loader)
I think its DM VERITY who block the access to recovery mode but i can't disable this, cause i can't get access to twrp :/
Thanks for any answers c:
Click to expand...
Click to collapse
I had some similar problem.
It was a wrong TWRP, I had to try 3 different ones until it finally worked (the one for AJ1 worked for me).
If you are in a bootloop you still can press Volume UP + DOWN and at the same time put the USB cable in when booting. This should set your phone into the download mode and you can flash TWRP or OS again.
Has anyone tried this TWRP build with ATB1 February patch version? It has increased BL version (2->3) so it is not possible to roll back to any older FW...
From my information ATB1 is still the same security patch level as ATA4.
General question: How can I judge the BL version of the firmware?
ruffyrisco said:
Magisk-Root is working for me.
I did this:
Backup of ASJ1 with TWRP
...
Click to expand...
Click to collapse
what TWRP is this and how did you manage to install it before being rooted?
toshibashi said:
what TWRP is this and how did you manage to install it before being rooted?
Click to expand...
Click to collapse
I used the modified TWRP from post #1: https://androidfilehost.com/?fid=4349826312261685733
ruffyrisco said:
From my information ATB1 is still the same security patch level as ATA4.
General question: How can I judge the BL version of the firmware?
Click to expand...
Click to collapse
Well, my info comes from samfw.com/firmware/SM-A405FN/TMZ, not sure how do they extract it.
both ATB1 - samfw.com/firmware/SM-A405FN/TMZ/A405FNXXS3ATB1 and ATA4 - samfw.com/firmware/SM-A405FN/XEZ/A405FNXXU3ATA4 seems like BL (or some OTP bits, I am noob with android internals) bumped from 2 to 3.
(sorry about URL formatting, as a XDA newbie, I am no allowed to post URLs)
xorly said:
both ATB1 - samfw.com/firmware/SM-A405FN/TMZ/A405FNXXS3ATB1 and ATA4 - samfw.com/firmware/SM-A405FN/XEZ/A405FNXXU3ATA4 seems like BL (or some OTP bits, I am noob with android internals) bumped from 2 to 3.
Click to expand...
Click to collapse
As I mentioned earlier ATA4 firmware works fine with TRWP.
But I'm not sure if ATA4 has BL 3.
Does the digit 10 in the firmware number represents the BL?
ruffyrisco said:
But I'm not sure if ATA4 has BL 3.
Click to expand...
Click to collapse
Then reboot into Download mode (you have to do it manually, not via ADB command) and look into top left corner. On ATB1, one of last lines says
Code:
AP SWREV B:3 K:3 S:3
I assume that some fo those numbers (B?) is OTP number set by BL version.
ruffyrisco said:
Does the digit 10 in the firmware number represents the BL?
Click to expand...
Click to collapse
I am not sure which *10* do you mean. It looks like version prefix is bootloader version, number 3 in A405FNXXS3ATB1 or number 2 in A405FNXXU2ASK2. It is the only number which seems to corellate with BL version.
Also, now I can confirm that that this TWRP build (based on A405FNXXU2ASJ1) works with ATB1 firmware! (february sec. patch) Successfuly tested with Phhussons Android 10 GSI quack v213.
Today I will be giving a tutorial on how to root the Huawei P20 Lite using STOCK ROM (ANE-LX1 ANE-L01 ANE-L21)
If you need bootloader unlock code
----------------------------------------
You can use dc-unlocker but, only if you can rollback to 8.0.0.146 or lower (i was on 8.0.0.46 when i used dc-unlocker).
You can try to use PotatoNV, but that will require testpoint access (haven't tested yet).
You can use HCU client with a 3day account pass, which is quite expensive (I have not actually tested this yet).
Rollback EMUI 9 to EMUI 8
-----------------------------
This is where my frustrations with this phone began.
You can try to use dload method, but in my experience this DOES NOT WORK when you're on EMUI 9.
It will just give you an error about incompatible version, every time.
Forced dload was also a complete bust for me, 24 hours wasted
I was finally able to rollback from HiSuite 11. I was on 9.1.0.200 when I had the option to rollback and it rolled me back to 8.0.0.163.
From 8.0.0.163 I could use normal dload to rollback further until I could use dc-unlocker.
I made the mistake of upgrading to EMUI 9 after I unlocked my bootloader. My advise: if you can manage to get to 8, stay there. It's less bloated and feels smoother. I have not received the option to rollback after I re-upgraded to 9 since. And I have not found AANNYY method to rollback to 8 since then, I pretty much gave up and stayed on EMUI 9.
EMUI 8
---------
copy magisk23.zip to sdcard
flash twrp to recovery_ramdisk.img
Code:
fastboot flash recovery_ramdisk "twrp-3.2.1-0.img"
EDIT: ***NEW official TWRP version*** TWRP 3.6.2.0_9-0
Code:
fastboot flash recovery_ramdisk "twrp-official-3.6.2_9-0-anne.img"
Code:
fastboot reboot recovery
Once in twrp install the magisk23.zip file.
This will patch the boot.img from recovery_ramdisk.img with magisk v23
Reboot -> System
Once in android you will get the usual magisk app, open and allow to perform additional tasks like installing the manager app.
Pretty straight forward
EMUI 9
---------
While still on stock firmware, update your android to the highest possible firmware (HiSuite or on phone -> Settings -> System ....)
1. When your back in android power off phone.
2. Go into fastboot (USB cable plugged in -> Power + Vol Down)
3. Flash twrp into recovery_ramdisk
Code:
fastboot flash recovery_ramdisk twrp-3.2.1-0.img
Code:
fastboot reboot recovery
Now In TWRP
4. Install Image -> twrp-3.2.1-0.img into eRecovery partition
5. Install Image -> magisk23_patched-ane.img into Recovery Partition
6. Reboot -> Recovery
Note: So booting into recovery mode gives you a ROOTED environment and System Mode gives you NON-ROOTED.
EDIT: *** With the new TWRP 3.6.2.0_9-0 you will have to boot into recovery (by holding Vol Up + Power till the screen comes on) every time you boot the phone or it will boot into normal system where the root environment isn't present ***
That's it. Now you should have root access.
You can still use twrp, but you have to access it like you would access eRecovery. So from power off (coldstart) -> Hold Vol Up while plugging in the USB Cable, continue to hold Vol Up, till you get the twrp logo.
Caution: This overwrites eRecovery, this can be dangerous, as eRecovery is the only thing standing between you can a hard brick if twrp wont boot anymore. This is due to fastboot not being able to flash eRecovery. You can only flash eRecovery from twrp. This is particularly dangerous if your data partition gets corrupted, this can happen when formatting data through twrp 3.4.0 and above. When your data partition is corrupt, twrp will freeze on the loading logo, leaving you no way to flash the original eRecovery.
Note: I think you can flash the eRecovery_ramdisk.img over the normal recovery_ramdisk in case of a brick situation. Though I haven't tested that idea yet, im just planning on going that route if I run into such a scenario. The eRecovery is particularly usefull as it can recover almost any situation by using wifi to download a stock rom and full flash that entire rom.
This way is robust, no need for key combo's when restarting the device etc.
All Downloads (GDrive):
Gdrive
After the root, you might find yourself needing safetynet attest pass.
This can be achieved by:
1. Open Magisk and setup MagiskHide ( Search on XDA if you don't know how to do this )
2. Magisk Modules -> Install Riru
3. Magisk Modules -> Install from storage -> Select safetynet-fix-v2.1.0.zip
note: If PropsConfig is installed, remove it first and reboot
If you need to use Smali then it's once again kinda straight forward.
1. Copy /system/framework to sdcard (anywhere u can copy it from)
2. Copy the framework folder onto pc
3. Open SmaliPatcher.exe -> Select the framework folder -> select patch options and patch
4. Copy the created magisk module zip file onto sdcard
5. Install magisk module -> Magisk -> Modules -> Install from storage
Hope you have a smooth experience rooting this device.
External links:
Tested custom recoveries from -Alf-
Source of rooting and flashing information by -Alf-
Credits:
@-Alf- for the magisk patched image. I only repatched his recovery_ramdisk from magisk v21 to v23
And also for the twrp recovery 3.2.1-0 GAGUGA Edition
RESERVED
gh0stza said:
And I have not found AANNYY method to rollback to 8 since then,
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/losq-lir-lineageos-17-1-18-1-unofficial-gsi.4219291/post-85379393
gh0stza said:
eRecovery is the only thing standing between you can a hard brick if twrp wont boot anymore
Click to expand...
Click to collapse
there is one more thing - Service ROM aka 'full stock ROM' & dload method
gh0stza said:
your data partition gets corrupted, this can happen when formatting data through twrp.
Click to expand...
Click to collapse
Can happen only with TWRP 3.4.0 and above.
Regards
No matter what I did, dload failed, I must have downloaded 30 roms and tried every which way with dload. Nothing worked!!!!!
dload only worked on same EMUI. So nope sorry dude dload was a no go for me. Maybe it works for someone else, which is why I mentioned it.
And yes, TWRP 3.4.0 and above. I was using a twrp(3.5.2_9-0) from official twrp repository for ANE-LX1 when I formatted my data partition. However, that's not the point.
Someone else is absolutely BOUND to fall into this trap too, and as I said that TWRP came from the official chain.
So my only intention is to warn the next guy who might just be using that version or for whatever other reason twrp doesn't start anymore. I'm just saying - BE CAREFUL
gh0stza said:
No matter what I did, dload failed, I must have downloaded 30 roms and tried every which way with dload. Nothing worked!!!!!
dload only worked on same EMUI. So nope sorry dude dload was a no go for me. Maybe it works for someone else, which is why I mentioned it.
And yes, TWRP 3.4.0 and above. I was using a twrp(3.5.2_9-0) from official twrp repository for ANE-LX1 when I formatted my data partition. However, that's not the point.
Someone else is absolutely BOUND to fall into this trap too, and as I said that TWRP came from the official chain.
So my only intention is to warn the next guy who might just be using that version or for whatever other reason twrp doesn't start anymore. I'm just saying - BE CAREFUL
Click to expand...
Click to collapse
this is why we have this article here: https://forum.xda-developers.com/t/recommended-and-tested-twrp-recovery.4199099/
-Alf- said:
this is why we have this article here: https://forum.xda-developers.com/t/recommended-and-tested-twrp-recovery.4199099/
Click to expand...
Click to collapse
Shiet dude, 3 full days rooting this device and I didn't come upon this post once. Now I'm gonna have to try to downgrade again with HuRUpdater and that twrp.
That's a nice post - thanks
gh0stza said:
Shiet dude, 3 full days rooting this device and I didn't come upon this post once. Now I'm gonna have to try to downgrade again with HuRUpdater and that twrp.
That's a nice post - thanks
Click to expand...
Click to collapse
What is your regional variant?
-Alf- said:
Oreo and Pie Stock & Custom ROMs:
3.2.1-0 by pretoriano80 (data decryption on Android 8 ) - on Pie use this TWRP e.g. if you want to downgrade to Oreo via HuRupdater.
https://mega.nz/#!Fgd0xa4R!1o5ejzDnkLJLG2tAZG-STtlJ4nnNCHfwwZdOlmOkrVw
Click to expand...
Click to collapse
Are you saying I should try to use this TWRP to use HuRUpdater to downgrade to 8?
I plan on using the HiSuite downloaded firmware ANE-LX1 8.0.0.163(C185) with HuRUpdater.
Current folder stucture:
ANE-LX1 8.0.0.163(C185)\full\update.zip
ANE-LX1 8.0.0.163(C185)\full\ANE-L01_hw_meafnaf\update_full_ANE-L01_hw_meafnaf.zip
Planned folder structure after renames:
ANE-LX1 8.0.0.163(C185)\full\update.zip
ANE-LX1 8.0.0.163(C185)\full\update_all_hw.zip
ANE-LX1 8.0.0.163(C185)\full\HuRUpdater_0.4.zip
Then flash HuRUpdater_0.4.zip in twrp 3.2.1-0 by pretoriano80 like the quoted text suggests?
Am I getting this right?
PS: The twrp I am using now -> 3.2.1-0 GAGUGA Edition (Also the one in my download hyperlink)
EDIT: I am on 9.1.0.355(C185) now. But, it is still trying to give me OTA update of the exact same build, so dunno what thats about
gh0stza said:
The twrp I am using now -> 3.2.1-0 GAGUGA Edition (
Click to expand...
Click to collapse
Read carefully bro: https://forum.xda-developers.com/t/losq-lir-lineageos-17-1-18-1-unofficial-gsi.4219291/post-85380241
You need 3 .zip files - update, hw and data
{
"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"
}
gh0stza said:
Are you saying I should try to use this TWRP to use HuRUpdater to downgrade to 8?
Click to expand...
Click to collapse
Bingo!
Then I have a problem.
Not one single downloaded firmware anywhere gave me 3 files. It's always just the update.zip (or update_sd.zip for dload) and the hw update.
How can HiSuite flash that firmware then? I just need to flash this 163 rom. But nothing works
***EDIT***
Know what, doesn't matter. I'm pretty fed up with this phone and how Huawei implemented this phones partitioning style and just everything.
I mean where is Odin for Huawei? And just how they withdrew support to get unlock code, limited fastboot command etc.
Just everything about huawei....
I got my ANE-LX1 to a stable root with everything I need working perfectly, so Imma call it a win and move on.
But, you've been great dude and basically almost all useful information I got either came from you ( @-Alf- ) or XDA, so thnx everyone
gh0stza said:
Then I have a problem.
Not one single downloaded firmware anywhere gave me 3 files. It's always just the update.zip (or update_sd.zip for dload) and the hw update.
How can HiSuite flash that firmware then? I just need to flash this 163 rom. But nothing works
***EDIT***
Know what, doesn't matter. I'm pretty fed up with this phone and how Huawei implemented this phones partitioning style and just everything.
I mean where is Odin for Huawei? And just how they withdrew support to get unlock code, limited fastboot command etc.
Just everything about huawei....
I got my ANE-LX1 to a stable root with everything I need working perfectly, so Imma call it a win and move on.
But, you've been great dude and basically almost all useful information I got either came from you ( @-Alf- ) or XDA, so thnx everyone
Click to expand...
Click to collapse
Try this way out...
Flash via dload
https://androidhost.ru/1lsA
and try downgrade via HiSuite.
-Alf- said:
Try this way out...
Flash via dload
https://androidhost.ru/1lsA
and try downgrade via HiSuite.
Click to expand...
Click to collapse
Ok, download started
First thing tomorrow morning, even though I just got everything just right with EMUI 9.
You think it's worth it?
gh0stza said:
I made the mistake of upgrading to EMUI 9 after I unlocked my bootloader. My advise: if you can manage to get to 8, stay there.It's less bloated and feels smoother.
Click to expand...
Click to collapse
gh0stza said:
You think it's worth it?
Click to expand...
Click to collapse
dunno how to respond to that....
I'll keep it in my back pocket, when i'm bored some time this week I might try it.
Else screw it, to hell with you huawei.
PS: Still better then the LG G6, which is unrootable (short of opening it up) due to the total inablility to get unlock code.
so do we run this to keep the stock eRecovery?
Install Image -> twrp-3.2.1-0.img into eRecovery partition
coz i got stuck in a situation where the phone would boot to twrp only and nothing else, somehow managed to get back to stock
khal_nayak said:
Install Image -> twrp-3.2.1-0.img into eRecovery
Click to expand...
Click to collapse
this is only necessary if you want to have both Magisk root and TWRP on board at the same time. (on EMUI 9.1 ramdisk is
included in the recovery_ramdisk).
If you don't need TWRP, just flash magisk_patched_recovery in fastboot mode.
ok but i was trying to remove bloatware i caused the rom to bootloop and then tried factory reset from twrp and now other than twrp nothing boots, where can i get factory image from to get it back to working?
all i need is root with magisk and want to keep the stock erecovery.
if there are better custom roms with volte etc all working then im willing to try it out
khal_nayak said:
tried factory reset from twrp
Click to expand...
Click to collapse
That was not a good idea. On Huawei phones, you can only perform a factory reset from stock recovery.
khal_nayak said:
where can i get factory image from to get it back to working
Click to expand...
Click to collapse
Depends on your build number - model, EMUI version, region variant (Cxxx). What is your b.number?
khal_nayak said:
custom roms with volte etc all working
Click to expand...
Click to collapse
All Treble GSI ROMs on Huawei have common bugs - no VoLTE, no offline charging, no native call recording...
since now i can only boot to twrp and fastboot mode how do i know the model and region?
i bought the phone as nova3e in UAE and currently was on emui 9.1, if i can just get the erecovery back then can make it download the firmware and flash it
This thread going to guide you on how you can root Realme GT NEO 2 Device with RUI 3.0 installed.
This boot image is fresh, and it's patched for root access.
Caution: Before flashing, you need to have your bootloader unlocked, for bootloader unlocking, go to this link and follow the procedure to get approval and unlock your device bootloader.
Link: https://forum.xda-developers.com/t/bootloader-unlock-realme-gt-neo-2-rmx3370-all-variants.4391679/
After you get approval, you are ready to root your device!
For this tutorial, I gonna use a windows device.
WARNING!
I am not responsible for anything. proceed at your own risk. Rooting or Unlocking the Bootloader voids the device warranty, keep it in your mind.
STEP - ONE
Only follow this step, if you get approval for the bootloader, and you didn't unlock this device or your flashing environment needs to be configured. You need to visit the following link to set up your environment for flashing a custom boot image.
Link: https://njpsmultimedia.blogspot.com/2022/04/realme-gt-neo-2-bootloader-unlock.html you just need to follow the video tutorial on this website.
STEP - TWOIt's assumed that your environment is properly configured. Let's flash this boot image to root your device.
Download this zip file from here https://drive.google.com/file/d/1Xk1yBp5EDCZbl3i3jMtOhjfaVtTCQqYB/view?usp=sharing and copy the boot.img file to platform-tools folder.
Then open the terminal and cd to the platform-tools folder.
Then, shut down your device and hold the vol up + vol down + power button together to boot this device into fastboot mode.
First, you need to run
Code:
fastboot devices
to check if your device is properly connected to the bootloader interface. If it shows something then your device is properly connected, If not, try to install the device driver, change the cable, or boot into the bootloader mode again.
If your device is connected properly, then you will see a screen like this:
{
"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"
}
And then run this command:
Code:
fastboot flash boot boot.img
Then,
Code:
fastboot reboot
You are done! Congratulation.
Note: This method was tested with Realme UI 3.0 android 12 on GT NEO 2. Do not try this method on RUI 2.0 or on other devices.
SCREENSHOTS
Note
If you face NO WIFI, Sound issue on the C04 version, you are advised to flash this alternate version from here: https://forum.xda-developers.com/t/...uide-on-gt-neo-2.4435919/page-2#post-86985433
Do you lose all data ? On the root part the bootloader is already unlocked
theogr91 said:
Do you lose all data ? On the root part the bootlocker is already unlocked
Click to expand...
Click to collapse
- it is necessary to have the bootloader unlocked before flash (instructions on how to unlock the bootloader can be found in the video in the post above or here on the forum)
- after flash just install Magisk manager
no data loss, tested and functional
theogr91 said:
Do you lose all data ? On the root part the bootlocker is already unlocked
Click to expand...
Click to collapse
If your bootloader is already unlocked, no data loss. but If your device bootloader is not unlocked, then unlocking your device data will be erased.
Do we flash magisk or other way of root ?
theogr91 said:
Do we flash magisk or other way of root ?
Click to expand...
Click to collapse
You need not flash anything extra than flashing customized boot.img. Just simply follow this step and your device will be rooted.
Worked like charm thanks. Will the phone be ok after an OTA update ?
Help...After flashing boot image and rebooted , Wifi is not scanning the networks and I am unable to take calls but 4g(internet) is working fine. Please reply me for any fix. I followed the exact steps you mentioned. My Device Realme Gt neo 2 UI 3.0
mahesh.pujala said:
Help...After flashing boot image and rebooted , Wifi is not scanning the networks and I am unable to take calls but 4g(internet) is working fine. Please reply me for any fix. I followed the exact steps you mentioned. My Device Realme Gt neo 2 UI 3.0
Click to expand...
Click to collapse
In my case, all is fine.
You can try backup data and then reset your device through recovery.
theogr91 said:
Worked like charm thanks. Will the phone be ok after an OTA update ?
Click to expand...
Click to collapse
After the OTA update, you may need to flash this boot image again.
Help...After flashing boot image and rebooted , Wifi is not scanning the networks and I am unable to take calls but 4g(internet) is working fine. Please reply me for any fix. I followed the exact steps you mentioned. My Device Realme Gt neo 2 UI 3.0
Nurujjamanpollob said:
In my case, all is fine.
You can try backup data and then reset your device through recovery.
Click to expand...
Click to collapse
Thanks for the reply . Any way I reverted back to previous state by flashing stock boot image and firmeware. Now everthing works fine. I will think about rooting later..
Removed root and updated to RMX3370_11_C.04 is it safe to reflash root image on this version?
theogr91 said:
Removed root and updated to RMX3370_11_C.04 is it safe to reflash root image on this version?
Click to expand...
Click to collapse
I just tried this and it worked for me...
Meanwhile I realised that my wifi and my phone don't work anymore... I have no idea if this boot image is the cause.
Grobie13 said:
Meanwhile I realised that my wifi and my phone don't work anymore... I have no idea if this boot image is the cause.
Click to expand...
Click to collapse
I have no wifi after the flash and i have no twp on RMX3370_11_C.04 any way to fix it ?
theogr91 said:
I have no wifi after the flash and i have no twp on RMX3370_11_C.04 any way to fix it ?
Click to expand...
Click to collapse
No solution so far. I think first everything was fine, after flashing the magisk boot image it's gone worse... But I'm not sure.
I do not recommend updating on RMX3370_11_C.0. After flashing boot image (without Magisk) wifi no longer working.
I flashed clean firmware and lock bl i am done moding this device only adb debloat.. And after clean flash netflix still wont open login screen...
Grobie13 said:
No solution so far. I think first everything was fine, after flashing the magisk boot image it's gone worse... But I'm not sure.
Click to expand...
Click to collapse
What device variant you use? India or global?
Probably I gonna update this boot image today with latest update.
Nurujjamanpollob said:
What device variant you use? India or global?
Probably I gonna update this boot image today with latest update.
Click to expand...
Click to collapse
It's global respectively EU. But I start from scratch yesterday. I flashed twrp, format data and flashed magisk. But other people need your patched boot image. Thanks for providing.