Search results

Right, I would say the bootmod1.img was missing when @karim-ps tried to flash. Yes, I made it on my shield non pro 16 GB version, pro is the one with 500GB drive. AFAIK it should work on both. Double check your path and command line.

You're missing something, you have to expand spoiler blocks.

Hi I would say no. AFAIK the provided zip files here are archives, not flashable packages. So you would have to download the archive, extract and flash img files according to the procedure provided in the first post (using fastboot / USB debugging). You can probably keep your current recovery...

If you see something in logcat you can try the procedure here : https://forum.xda-developers.com/t/guide-remapping-android-tv-remote-buttons.4433617/ Unfortunately, the FireTV remote app buttons are not detected at all.

Hi, Have someone been able to detect FireTV remote app button (Netflix, Prime...) using Automat with an android TV device? I try to use these buttons with my Shield but I am unable to detect anything in any ways. I tried but the app does not show anything, not sure I am doing right though. All...

If you just want to clean your system without risk, you can enable USB debugging in developer options (usng network is more practical as you don't have to plug a cable) Then using ADB you disable all the package you don't need. For example, I stick to the 8.2.3 version and I don't want to be...

I use magisk delta 25.2, I think it is the latest version. Did it by flashing modified boot.img available in 2019 section.

Hi, Check this thread, it offers both 2019 and 2017 shield models, and since this week-end the boot.img for latest versions are available. I can attest it works. https://forum.xda-developers.com/t/patched-boot-imgs-achieve-root-on-stock-firmware-and-keep-stock-apps-2017-2019.4524873/

Thanks, I solved my issue with the following adb command : adb shell pm uninstall -k --user 0 com.android.documentsui It removed the android's stock file app and then Magisk asked for another file manager to load the file. EDIT : I don't recommend to do this as it will cause some issue, please...

Hi, thanks @jenneh for your tutorial. I just got a 2017 Shield TV and flashed 8.2.3 stock version, then successfully rooted it with your instructions. I just cannot install safety net package in Magisk as I am unable to select the file, I can't understand why. Using remote or controller, no way...

Just dirty flash your current rom over with same version.

I tried latest 2.4 Sphinx kernel on Globerom 9.1.17 and i still have the issue i've had everytime i tried this kernel (version 1.7, 2.0, 2.2...) : a drastically reduced battery life. I can't understand why, no particular wakelock found, no draining app or setting, just battery drain. Each time...

Thanks, i will stick to stock kernel till update of Sphinx.

Thanks for the new version :) Can anyone confirm the touch firmware 8.12.10 is the same as the firmware used in 8.12.13 xiaomi.eu rom ? Because it is far better than previous one and i don't want to revert back.

With 2.0 on 8.12.13, i've had screen flickering and bad responsiveness of touchscreen. Had to revert back to stock. Maybe kernel needs latest commits to solve those issues.

8.12.13 is far better than 8.12.7 which was clearly laggy. Far from perfect but one of the best management of poco touchscreen since the beginning. I am afraid that touch will never be perfect on this device, i think hardware is obiously weak.

Just flashed 2.0 kernel on Globerom 8.12.7 (based on xiaomi.eu 8.12.7 V2). Everything is OK and wifi is fine too. I want to thank you milouk for your great work, i used version 1.7 for a while and it always worked flawlessly, and i have to say i am very pleased to see how much you are active...

Magisk 17.3, no lags or at least not worse than stock MIUI :)

Hi, I flashed this kernel after root with magisk (Globerom with root integrated) and it works perfectly fine, wifi is OK too. So i guess after is fine.

It was an advice for calisthenics995 , i put his name so he can view you suggestion. ;) If it is not done yet, i would try dirty flash as first step as he would lost his data using miflash.

Just dirty flash your current rom over, it will replace kernel by stock one (or custom one if you use a custom). Wipe cache and dalvik to make things cleaner.

No major changes between july and september, so i would say yes. You can always backup boot, system and data in TWRP to be totally safe.

You didn't mentionned your present build, so i assume you use august build. You can dirty flash over the previous version, i did it and everything works fine (just wipe cache / dalvik).

You are not alone, i am really disapointed too with GPS fix since a while (can't remember when it started though), fix is very long. Update A-GPS data (using GPS test) helps a bit (placebo?) but it used to be far quicker.

Obviously not :laugh: Just trying to help you to dig a bit more before concluding to a rom bug, but he will surely answer you ;)

I am sure you are not a rookie, but you talk about a bug, and a real bug should affect all (or at least most) rom users, that's why i replied. Nobody else seems to report such issue (or i don't remember), so maybe you have something particular that causes it (app or setting...).

I put my phone in airplane mode every night, and bluetooth remains off if it was off before airplane mode. If bluetooth was on, it will be on again after exiting airplane mode, this seems to be a normal behavior to me.

Maybe by checking which app is authorized to manage wifi connection.

No such issue for me. Maybe you have an app that keeps wifi on ?

OK, now i understand why i didn't face that issue. So it is Pie related.

Had a 30mn call yesterday, no problem with R8. Do you mean with pie rom ou Oreo rom ?

No random reboot for me, and flashlight QS works as usual. Maybe it is due to LOS as i didn't face any reboot since installation of JasperKernel R8 on RR.

Most of apps don't need google services. Don't forget Xiaomi sold (and maybe still sell) phones without google apps in China. Those users can use apps though, fortunately! ;)

Of course but if you cannot use Playstore to install apps you have to find apps apk to install manually.

Search for "the SELinux switch" on XDA, very simple selinux toggle app, no need of magisk module.

R7 installed. Be sure we all greatly appreciate your kernel and yout work ;)

You mean backup efs partition before flashing kernel new version and restore efs partition after flashing ? EDIT : It occured again today so it is probably my phone which is in cause. :(

Last week i've had several times a day a "Missing SIM" error, after flashing R6 version of the kernel. Reboot or eject and insert again SIM card solved it but it occured many times. After reverting to R5 version, no more SIM issue. Anyone else faced this issue on R6 ?

I have many options for each button below, that's weird you cannot see that.

Dirty means flashing without formating data, you just flash over previous version and wipe cache and dalvik only. If you use TWRP, you just flash over and hit the "wipe cache and dalvik" button at end of flash.

No problem here, you should try calibrate your battery. The only way i know to change vibration intensity is to use custom kernel (i recommend Jasperkernel) and set vibration level using kernel Adiutor.

Please, read changelog on 3rd post.

Just flashed R4, everything is OK, good to see warning is gone. :) May i ask why is it necessary to reflash rom before the kernel ?

Yes it may help, i've always had to enable camera2api to get the camera working on RR. I am not sure flashing may build and then update to july to be the best option as treble support was added in june, and several users reported issues when appling later updates on may builds.

I don't use Redwolf but i've read that treble mode has to be activated in redwolf settings. If you have any problem, flash the treble TWRP R2, i use it and it works flawlessly. https://sourceforge.net/projects/tea...d/TWRP/Treble/ ---------- Post added at 11:02 AM ---------- Previous post was...

Hi Read a few pages back, Magisk issue is due to corrupt file. First be sure to have a treble compatible recovery and to enable treble if needed. you can find a working magisk here : https://forum.xda-developers.com/showpost.php?p=77062410&postcount=1322 No problem using stock camera or others...

It has been reported many times... Treble recovery is mandatory, if you have not already install it, pick the R2 version here : https://sourceforge.net/projects/team-reloaded/files/land/TWRP/Treble/ You can find a working magisk 16.4 here ...

The option will work in RR if you set it in RR settings, advanced menu is disabled by default.

You have V36, the latest is V52, that seems a bit old to me... That said, if you already have installed custom rom and if all network functions work fine, you don't really have to update.

Yes, just flash with twrp, this is what i've done. :)