Related
There is no way to flash supersu on my phone on any rom, on freedomos rom when i select install supersu doesnt work with neither elementalx or stock patched kernel, i tried flashing stock unpatched kernel and then supersu neither that work, it always comes to boot image patcher and then says failure aborting, i had the same problem with other roms, can someone tell me whats the problem ?
Flash modded twrp http://forum.xda-developers.com/devdb/project/dl/?id=21065
Credits to @ eng.stk for this. I had the same issue.
ungeeked said:
Flash modded twrp http://forum.xda-developers.com/devdb/project/dl/?id=21065
Credits to @ eng.stk for this. I had the same issue.
Click to expand...
Click to collapse
Can I use this recovery for every rom in future or I have to go back to official one?
ach3fck said:
Can I use this recovery for every rom in future or I have to go back to official one?
Click to expand...
Click to collapse
No need to go back to official
ungeeked said:
No need to go back to official
Click to expand...
Click to collapse
Ok thanks, sorry to bother you, but should I flash the ROM again via Aroma or I should just flash SuperSu?
Just flash SuperSU. That should do it
Flashed SuperSU and got stuck in a bootloop, did a clean flash again and it worked, thanks a lot!
And now this, f*ck, maybe it could be because I restored backed up data partition, will try to do a clean flash and let you know.
I had this issue yesterday and fixed it today.
try deleting the su binary in twrp.
goto: /data/system/xbin
delete su
flash your SuperSU.zip again.
worked for me, because i had an systemless supersu installed, but an old su file in xbin.
I was trying to get help on Reddit but I wasn't able to get any help.
I was able to find the Twrp image to Boot into but Magisk isn't installing when I go to try to install it.
I'm using 13.4 for my pixel XL and I tried 13.3
Any ideas why they aren't working? No errors in Twrp when installing.
DudeThatsErin said:
I was trying to get help on Reddit but I wasn't able to get any help.
I was able to find the Twrp image to Boot into but Magisk isn't installing when I go to try to install it.
I'm using 13.4 for my pixel XL and I tried 13.3
Any ideas why they aren't working? No errors in Twrp when installing.
Click to expand...
Click to collapse
Hello,
Not sure if Magisk is even working on O but you would want to flash a kernel like ElementalX first or the modified stock. Flash the kernel, then Magisk but again I am not sure if it is actually working yet. If you do get it installed and working be sure to report back to all. Also if you had SU + SUhide prior then you will want to flash the Magisk remover first, then kernel then Magisk.
Cheers
jschill31 said:
Hello,
Not sure if Magisk is even working on O but you would want to flash a kernel like ElementalX first or the modified stock. Flash the kernel, then Magisk but again I am not sure if it is actually working yet. If you do get it installed and working be sure to report back to all. Also if you had SU + SUhide prior then you will want to flash the Magisk remover first, then kernel then Magisk.
Cheers
Click to expand...
Click to collapse
Yup. Just verified it doesn't work. I booted into twrp, installed ElementalX, then Magisk 13.4 and rebooted, still doesn't work.
Then I booted into twrp, installed ElementalX and Magisk 13.3 and rebooted. Nothing.
I also installed TWRP RC2 and it works fine. If you want I can upload the bootable image for twrp and RC2 that I used. At least now I have a way of testing it out (well, to keep testing it out, when I'm at work).
DudeThatsErin said:
Yup. Just verified it doesn't work. I booted into twrp, installed ElementalX, then Magisk 13.4 and rebooted, still doesn't work.
Then I booted into twrp, installed ElementalX and Magisk 13.3 and rebooted. Nothing.
I also installed TWRP RC2 and it works fine. If you want I can upload the bootable image for twrp and RC2 that I used. At least now I have a way of testing it out (well, to keep testing it out, when I'm at work).
Click to expand...
Click to collapse
So you have twrp installed with no issues?
humdrum2009 said:
So you have twrp installed with no issues?
Click to expand...
Click to collapse
Correct
I'm using a 6p with a pixel on the way. I had it working on the 6p with Oreo. I'm pretty sure I had to download an apk as well as flash the zip. Have you done this?
the pixel has a special magisk version because of boot a/b system stuff from my understanding. So it doesn't matter if it works on any other google phone.
It sucks too because i heavily rely on magisk due to how good it is on hiding...goodwin_c is my only hope. hanging on a thread here...
If you mention other root hiding methods just know that no...they all suck lol
j_mullet said:
I'm using a 6p with a pixel on the way. I had it working on the 6p with Oreo. I'm pretty sure I had to download an apk as well as flash the zip. Have you done this?
Click to expand...
Click to collapse
Zizzy2020 said:
the pixel has a special magisk version because of boot a/b system stuff from my understanding. So it doesn't matter if it works on any other google phone.
It sucks too because i heavily rely on magisk due to how good it is on hiding...goodwin_c is my only hope. hanging on a thread here...
If you mention other root hiding methods just know that no...they all suck lol
Click to expand...
Click to collapse
What Zizzy2020 said. It is annoying. I can't wait for the next magisk to be released.
Check out this post, it works like a charm.
Managed to install it on OP3T but it won't work on OP3
Here is what i am doing, please correct me if i am doing anything wrong
Cleaning Super User from Updated UnSU.zip which works fine. Flashing Stock Boot.img (OK)
Flashing Magisk 14.3 (OK)
reboot and Stuck on oneplus logo
Doing it all again and flashing Magisk 14.5 and again Bootloop.
any help is highly appreciated Thanks
Good to know?
Sent from my OnePlus 3 using Tapatalk
Use the uninstaller and completely remove Magisk: https://forum.xda-developers.com/attachment.php?attachmentid=4339479&d=1511372903
Then install the v14.5(1456) beta: https://forum.xda-developers.com/attachment.php?attachmentid=4340290&d=1511453617
Working fine here with OOS 5.0
arcslt18 said:
Hello, i am having trouble installing Magisk 14.3 and 14.5
Click to expand...
Click to collapse
great description of your problem mate.
noone can help you if you dont tell whats your exact problem and what you did.
MarcTremonti said:
great description of your problem mate.
noone can help you if you dont tell whats your exact problem and what you did.
Click to expand...
Click to collapse
i posted that from xda app. text was missing. please check now. Thanks
Cyda said:
Use the uninstaller and completely remove Magisk: https://forum.xda-developers.com/attachment.php?attachmentid=4339479&d=1511372903
Then install the v14.5(1456) beta: https://forum.xda-developers.com/attachment.php?attachmentid=4340290&d=1511453617
Working fine here with OOS 5.0
Click to expand...
Click to collapse
Which device are you using? Twrp version? and magisk? please read my post now, as some text was missing when i posted it. i was using Xda App
Explorer23 said:
Good to know?
Sent from my OnePlus 3 using Tapatalk
Click to expand...
Click to collapse
Sorry some text was missing. please read post now. Thanks
arcslt18 said:
Which device are you using? Twrp version? and magisk? please read my post now, as some text was missing when i posted it. i was using Xda App
Click to expand...
Click to collapse
OP3, using the latest blue_spark TWRP and the version of Magisk I linked above.
Cyda said:
OP3, using the latest blue_spark TWRP and the version of Magisk I linked above.
Click to expand...
Click to collapse
Thanks for helping me, i tried Blu spark and magisk from your link, i'm getting bootloop again, No luck
for me - coming from a custom lineage 7.1.2 rom - it worked the following way (but it completely formatted the phone due to an encryption issue)
- flash blu spark TWRP for Oreo
- wipe system, data, cache, dalvik
- flash OB27 ROM
- flash blu spark again
- reboot to recovery
- flash magisk 14.3
Are you having a boot loop (phone reboots again and again) or is it booting up forever with the boot logo on the screen? you are describing both in your post.
I'm using 14.5 and ask works great here on OP27 Oreo was using 14.3 and that all worked great too and did nothing special part from install
Ok, i have the same problem, I am on OB28 and working SU root. i want to change to magisk, so I completely unrootet the phone and tried to flash magisk via newest twrp. But it stuck at bootlogo. do I really have to flash for magisk the twrp.enkgst? will it work then?
OK, solved, flashed spark twrp flashed magisk uninstaller, flashed magisk 14.5 I'm fine
Hey Can someone please find out a supported Viper4android for OP7T.
Installing through magisk gives a bootloop
Installing drivers directly through the Viper4android app too gives a Bootloop
Already tried the existing method updated on xda for getting Viper4android to work on android 10. Unfortunately it gives a bootloop too.
I've been racking my brain trying to find a solution, have yet to find one. All thus far end in bootloop.
Not giving up hope.
oneszero said:
I've been racking my brain trying to find a solution, have yet to find one. All thus far end in bootloop.
Not giving up hope.
Click to expand...
Click to collapse
Have you managed to remove the module? Or still in a bootloop?
Also, have you tried this one?
https://zackptg5.com/downloads/v4afx-rootless_08.18.2019.zip
Sent from my OnePlus7TPro using XDA Labs
Lossyx said:
Have you managed to remove the module? Or still in a bootloop?
Also, have you tried this one?
https://zackptg5.com/downloads/v4afx-rootless_08.18.2019.zip
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
Is this one functional?
oneszero said:
Is this one functional?
Click to expand...
Click to collapse
I am not sure, I just thought if you've factory reset to remove the bootloop, I guess you have nothing to lose if you try this one. If that's not the case, you're in the same boat as me, not wanting to risk a factory reset in case it doesn't work. Not having a recovery really sucks...
Sent from my OnePlus7TPro using XDA Labs
Lossyx said:
Have you managed to remove the module? Or still in a bootloop?
Also, have you tried this one?
https://zackptg5.com/downloads/v4afx-rootless_08.18.2019.zip
Click to expand...
Click to collapse
I was able fix the boot loop if i flash the stock boot img. However someone posted a custom boot img just to get out of such a situation without any sort of factory reset.
Lossyx said:
Have you managed to remove the module? Or still in a bootloop?
Also, have you tried this one?
https://zackptg5.com/downloads/v4afx-rootless_08.18.2019.zip
Click to expand...
Click to collapse
Is it suppose to be flashed via magisk?
And can you share the original thread where you got this link from?
passi77 said:
I was able fix the boot loop if i flash the stock boot img. However someone posted a custom boot img just to get out of such a situation without any sort of factory reset.
Click to expand...
Click to collapse
Can you link the custom boot image?
https://forum.xda-developers.com/an...iper4android-fx-2-6-0-0-t3774651/post80054209
https://forum.xda-developers.com/an...iper4android-fx-2-6-0-0-t3774651/post80053180
This should be able to flash in EXKM or Franco kernel Manager. It zip uses anykernel which makes be believe it only modifies the boot image. If I'm correct, you should be able to restore with just flashing stock boot.
Also,
https://forum.xda-developers.com/an...iper4android-fx-2-6-0-0-t3774651/post80721099
Sent from my OnePlus7TPro using XDA Labs
Lossyx said:
Can you link the custom boot image?
https://forum.xda-developers.com/an...iper4android-fx-2-6-0-0-t3774651/post80054209
https://forum.xda-developers.com/an...iper4android-fx-2-6-0-0-t3774651/post80053180
This should be able to flash in EXKM or Franco kernel Manager. It zip uses anykernel which makes be believe it only modifies the boot image. If I'm correct, you should be able to restore with just flashing stock boot.
Also,
https://forum.xda-developers.com/an...iper4android-fx-2-6-0-0-t3774651/post80721099
Click to expand...
Click to collapse
This doesn't seem to work. Everything installs without a bootloop but the driver does not seem to detect the installation or the driver doesn't successfully install.
Sent from my OnePlus7TPro using XDA Labs
I guess its because of the Dolby Atmos which is built in. I tried to tweak the settings to match Viper, but no where close.
sathya said:
I guess its because of the Dolby Atmos which is built in. I tried to tweak the settings to match Viper, but no where close.
Click to expand...
Click to collapse
Can you try freezing Dolby and redo everything?
grandpajiver said:
Can you try freezing Dolby and redo everything?
Click to expand...
Click to collapse
I've tried that and it didn't work for me unfortunately. (Getting viper to work)
Sent from my OnePlus7TPro using XDA Labs
I tried to install viper4android as well, I should have researched this thing first.
Here is my story so far:
the module did not seem to do anything.
Installed the apk, which wanted to install drivers, I finally gave in and allowed it to install.
After a reboot the device rebooted to fastboot, hit start.
Device goes back to fasstboot (does not reach bootanimation, then restarts to fasstboot)
Clearing cache from Recovery did not help.
No TWRP, full SE Linux and no way to mount those secured filesystems
So I tried booting the unpatched boot image, this works, my phone is not dead yay.
-> flashed unpatched boot.img, phone able to boot again, but no root
Opened Magisk manager, repatched a stock boot image,
20.2 a6e62e07 (20102)
Tried booting:
-> patched with safe mode (not sure what this does), hangs at fasstboot mode screen, force turn off
-> patched without safe mode, restarts to fasstboot
I can boot the test-TWRP, but I could not find anything relevant to either extract or replace / disable.
I tried finding a way to flag something so that Magisk would not try to load the viper module
The only logs I could find were related to the TWRP boot, so I cant see what error might be causing this.
I flashed the OTA 10.0.4 again in the hopes it would unpatch whatever the viper install did.
Luckily I got to keep data, but now I fear there might be something lingering somewhere...
Anyone have any advice on what to try next?
Is a factory reset really the only way to get back Magisk?
Hey guys, here is a zip I modified for the OP7T and 7T Pro. Please report if viper from this file works. All credits to:
- ahrion
- zhuhang
- osm0sis
- Viper's Audio (Official blog)
- viper520
- Team_DeWitt
EDIT: This may work with a permissive selinux. Use this app before installing the magisk module. If it doesn't work, just boot the magisk core only image and then delete the magisk module.
https://forum.xda-developers.com/android/apps-games/app-selinux-switch-t3656502
f41lbl0g said:
Hey guys, here is a zip I modified for the OP7T and 7T Pro. Please report if viper from this file works. All credits to:
- ahrion
- zhuhang
- osm0sis
- Viper's Audio (Official blog)
- viper520
- Team_DeWitt
Click to expand...
Click to collapse
doesnt work its the same as the other one. hangs at fastboot. flashed stock boot image to boot back up.
Now am stuck without root unless I perform a factory reset and start the whole process again
v.konvict said:
doesnt work its the same as the other one. hangs at fastboot. flashed stock boot image to boot back up.
Now am stuck without root unless I perform a factory reset and start the whole process again
Click to expand...
Click to collapse
Try to boot (not Flash) the magisk core-only image from this post :
https://forum.xda-developers.com/newreply.php?do=newreply&p=80775151
Then uninstall the V4A module and reflash your magisk patched boot.
sasho36 said:
Try to boot (not Flash) the magisk core-only image from this post :
https://forum.xda-developers.com/newreply.php?do=newreply&p=80775151
Then uninstall the V4A module and reflash your magisk patched boot.
Click to expand...
Click to collapse
Thanks already did a clean install of everything. Am gonna stay away from anything viper for a while now. Until it is confirmed working
v.konvict said:
doesnt work its the same as the other one. hangs at fastboot. flashed stock boot image to boot back up.
Now am stuck without root unless I perform a factory reset and start the whole process again
Click to expand...
Click to collapse
I'm so sorry. I don't have a 7T yet so I was not able to test. According to a 7T pro thread it is because of post-fs-data that viper causes the phone to go to fastboot. So i removed the lines in there that lead to post-fs-data but it still crashes.
EDIT: Forgot to add that you may need to change your selinux to permissive before installing the module. Use this app.
https://forum.xda-developers.com/android/apps-games/app-selinux-switch-t3656502
f41lbl0g said:
I'm so sorry. I don't have a 7T yet so I was not able to test. According to a 7T pro thread it is because of post-fs-data that viper causes the phone to go to fastboot. So i removed the lines in there that lead to post-fs-data but it still crashes.
EDIT: Forgot to add that you may need to change your selinux to permissive before installing the module. Use this app.
https://forum.xda-developers.com/android/apps-games/app-selinux-switch-t3656502
Click to expand...
Click to collapse
It's not working because you are just modifying the installed module, not the actual installer, which we do not have the source code of.
If anyone is interested, follow this to create your custom recovery. Then you can remove the post-fs-data via adb from the recovery.
https://forum.xda-developers.com/7t...n-os-stock-recovery-adb-t3991865/post80866897
Sent from my OnePlus7TPro using XDA Labs
Lossyx said:
It's not working because you are just modifying the installed module, not the actual installer, which we do not have the source code of.
If anyone is interested, follow this to create your custom recovery. Then you can remove the post-fs-data via adb from the recovery.
https://forum.xda-developers.com/7t...n-os-stock-recovery-adb-t3991865/post80866897
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
I am pretty sure the installer is open source. It is called Unity. And I did modify the installer. Post-fs-data is magisk file that loads a script on boot. In the case of the OP7T, this script causes it to crash to fastboot. I'm pretty sure the only reason it didn't work for the other user was because their selinux was enforcing instead of permissive.
Hi guys, I rooted my redmi note 8 yesterday. Everything went well except two things: on boot the error message said that "there is an internal problem" and the phone reboots/shuts down itself.
Any thoughts?
cicish said:
Hi guys, I rooted my redmi note 8 yesterday. Everything went well except two things: on boot the error message said that "there is an internal problem" and the phone reboots/shuts down itself.
Any thoughts?
Click to expand...
Click to collapse
You should explain the problem obviously if you want a help, if your phone still working you should flash twerp.img to be able to root it and solve any existing problem by flashing new rom
niceman2007 said:
You should explain the problem obviously if you want a help, if your phone still working you should flash twerp.img to be able to root it and solve any existing problem by flashing new rom
Click to expand...
Click to collapse
Hey thanks for answer.
Actually i did everything correctly, flashed latest twrp, tried several roms, oficial, unoficial etc., But still no result. After all these, ive flashed the stock rom which solved the problem but phone is no more rooted. So..
cicish said:
Hey thanks for answer.
Actually i did everything correctly, flashed latest twrp, tried several roms, oficial, unoficial etc., But still no result. After all these, ive flashed the stock rom which solved the problem but phone is no more rooted. So..
Click to expand...
Click to collapse
If you still want to root it again,after flasing new rom go to twero and then go to wipe then format,you should format your phone after rom flashing,try this and inform me
Yes yes! I want to root phone once again. So the steps are these:
1) booting into twrp with adb from pc.
2) from the twrp menu wiping and formating the data
3) instaling new rom
Is this true?
Thanks!
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Leeban Joseph said:
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Click to expand...
Click to collapse
You mean that its possible to have root access on stock rom?
Leeban Joseph said:
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Click to expand...
Click to collapse
Hey, I was able to flash magical using twrp but can't flash dm-verity. It gives me some error 1 with no description. I could flash magisk. What can the problem be? Thanks!
cicish said:
Hey, I was able to flash magical using twrp but can't flash dm-verity. It gives me some error 1 with no description. I could flash magisk. What can the problem be? Thanks!
Click to expand...
Click to collapse
From your stock rom extract the boot.img and place it on your SD card. Flash the boot image using twrp or you can also flash in fastboot, then reboot. Now boot to twrp recovery and flash dm-verity first and then magisk zip. Worked for me I'm having root permission with stock rom.
Leeban Joseph said:
From your stock rom extract the boot.img and place it on your SD card. Flash the boot image using twrp or you can also flash in fastboot, then reboot. Now boot to twrp recovery and flash dm-verity first and then magisk zip. Worked for me I'm having root permission with stock rom.
Click to expand...
Click to collapse
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
cicish said:
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
Click to expand...
Click to collapse
UPDATE: after another custom rom install failure, i got back to stock miui 11 with miflash tool. the problem is now that when i unlock the bootloader and try to flash magisk and disable-dm-verity, the system refuses to boot. the redmi note 8 logo is sticked on boot. i dont understand what i am doing incorrectly. if there are any suggestions im ready to try.
cicish said:
UPDATE: after another custom rom install failure, i got back to stock miui 11 with miflash tool. the problem is now that when i unlock the bootloader and try to flash magisk and disable-dm-verity, the system refuses to boot. the redmi note 8 logo is sticked on boot. i dont understand what i am doing incorrectly. if there are any suggestions im ready to try.
Click to expand...
Click to collapse
Is your bootloader unlocked right now or did you lock it while flashing using miflash tool.
Leeban Joseph said:
Is your bootloader unlocked right now or did you lock it while flashing using miflash tool.
Click to expand...
Click to collapse
the bootloader was unlocked. everything went kinda fine, until i flashed youtube vanced from magisk: when i did that, the system was unable to boot. i don't know what's happening. is there anything to do with kernel or something? really interesting what i am doing wrong.
cicish said:
the bootloader was unlocked. everything went kinda fine, until i flashed youtube vanced from magisk: when i did that, the system was unable to boot. i don't know what's happening. is there anything to do with kernel or something? really interesting what i am doing wrong.
Click to expand...
Click to collapse
I think it may be because of YouTube vanced module. If you remove the module you might be able to boot. In twrp in the advanced option select file manager and then select data/adb/magisk/ in that you will find the list of installed modules, select the one which is causing the problem and delete that folder and try to reboot.
Leeban Joseph said:
I think it may be because of YouTube vanced module. If you remove the module you might be able to boot. In twrp in the advanced option select file manager and then select data/adb/magisk/ in that you will find the list of installed modules, select the one which is causing the problem and delete that folder and try to reboot.
Click to expand...
Click to collapse
I've already flashed the stock rom but this will help me next time! Thanks!
I'll stop trying for some days cause I'm really tired with tweaking so thanks and will get back!
cicish said:
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
Click to expand...
Click to collapse
Your device reboots randomly on custom rom because probably it was made for tianma display and you have hauxing display
the_weird_aquarian said:
Your device reboots randomly on custom rom because probably it was made for tianma display and you have hauxing display
Click to expand...
Click to collapse
Hey, thanks for the answer. i've just googled about it and you are right. checked the TP version and it says that i have huaxing display. in the Lineage OS thread the moderator wrote that the next update will fix that bug. hopefully ill be able to install custom rom. also if you know, are there any custom roms for huaxing display? thank you man!
cicish said:
Hey, thanks for the answer. i've just googled about it and you are right. checked the TP version and it says that i have huaxing display. in the Lineage OS thread the moderator wrote that the next update will fix that bug. hopefully ill be able to install custom rom. also if you know, are there any custom roms for huaxing display? thank you man!
Click to expand...
Click to collapse
currently bootleggers rom,PE official and unofficial and drepfest all have reboot issues in huaxing display. Haven't tried any other rom yet..still on MIUI..waiting to get the issue fixed asap.
the_weird_aquarian said:
currently bootleggers rom,PE official and unofficial and drepfest all have reboot issues in huaxing display. Haven't tried any other rom yet..still on MIUI..waiting to get the issue fixed asap.
Click to expand...
Click to collapse
i've tried Lineage OS too and it also has reboot issue. i've checked a thread here https://forum.xda-developers.com/redmi-note-5-pro/development/derp-kernel-clang-4-4-138-t3804996 that flashing a different kernel when you have flashed a custom rom can fix the problem. idk if its safe to do
cicish said:
i've tried Lineage OS too and it also has reboot issue. i've checked a thread here https://forum.xda-developers.com/redmi-note-5-pro/development/derp-kernel-clang-4-4-138-t3804996 that flashing a different kernel when you have flashed a custom rom can fix the problem. idk if its safe to do
Click to expand...
Click to collapse
that thread is for redmi note 5 pro..and flashing different kernel probably won't solve it because I know few guys flashed genom kernel but still ended up with reboot in huaxing display. Maybe waiting for fix is better.