• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

Search results

  1. F

    Post [APP][6.0+] NetGuard - No-root firewall

    Indeed it does. Is there anything you can do about it or am I just screwed until Huawei manages to fix this? :eek:
  2. F

    Post [APP][6.0+] NetGuard - No-root firewall

    Thanks for the info, but it's not about stuff not coming through. Netguard spits out an error message in a notification complaining about being unable to start the VPN properly after some time. Until that, all works fine.
  3. F

    Post [APP][6.0+] NetGuard - No-root firewall

    Netguard crashing on Mate 10 Pro running EMUI 8.0 Hi Guys I recently got a Mate 10 Pro running Oreo and EMUI 8.0. When running Netguard on this (v2. 164 from github with all Pro features purchased), I experience crashes and subsequent issues with connectivity after a while. Seems like Huawei...
  4. F

    Post [Q] BT wakelock - Z3 never deep sleep

    I see you are using 'Sleep as an Android' app. Altough I'm using a Z3C, I suspect we suffer from the same issue - a permanent wakelock that has to do with Bluetooth. The app can use a Wear smartwatch for sleep tracking (if available). I noticed that when my Sony SW3 is not connected to the...
  5. F

    Post [ROOT] Root for SHIELD Tablet 2.0 (Lollipop)

    Don't hold them both, only hold Vol down and press power. If it's not working, google will help you how to do it properly ;) And if you don't get it working, please switch to the Q&A thread in order not to spam everything here... Gesendet von meinem Nexus 5 mit Tapatalk
  6. F

    Post [ROOT] Root for SHIELD Tablet 2.0 (Lollipop)

    Are you booted into bootloader while trying fastboot? Gesendet von meinem Nexus 5 mit Tapatalk
  7. F

    Post [ROOT] Root for SHIELD Tablet 2.0 (Lollipop)

    Does it respond to ADB/Fastboot? If yes, you can flash a factory image. Go to https://developer.nvidia.com/develop4shield#OSR, download the image for your model and follow the instructions. Gesendet von meinem Nexus 5 mit Tapatalk
  8. F

    Post [Q&A] [ROOT] Root for SHIELD Tablet 2.0 (Lollipop)

    No, you need to boot into recovery. ADB is working there, too (maybe you need to install the drivers again on your computer - look for a device like Android ADB interface or similar in your device manager if you cannot get a connection). Gesendet von meinem Nexus 5 mit Tapatalk ---------- Post...
  9. F

    Post [Q&A] [ROOT] Root for SHIELD Tablet 2.0 (Lollipop)

    boot-root.img needs to be in the same folder as the ADB tools (or, if not, you need the exact path to the file) on your computer.
  10. F

    Post [APP][4.0+] Backup+ [Beta]- App backup and restore

    No busybox installed perhaps?
  11. F

    Post [Q&A] [ROOT] Root for SHIELD Tablet 2.0 (Lollipop)

    ADB and fastboot: use Google or XDA search to get only the necessary parts. As an alternative, you can also download the Android SDK where these tools are in a subfolder (but that's overkill as the package is huge). You do not need to flash boot-root.img anymore if you use SuperSU 1.27 Beta...
  12. F

    Post [ROOT] Root for SHIELD Tablet 2.0 (Lollipop)

    Can confirm everything working fine using SuperSU 1.27, no modified kernel required anymore...
  13. F

    Post [Q&A] [ROOT] Root for SHIELD Tablet 2.0 (Lollipop)

    I just successfully updated to Lollipop and rooted my Shield Tablet LTE (locked bootloader) without flashing the modified kernel, but using SuperSU 1.27. Everything working fine so far! [emoji108]
  14. F

    Post [Q&A] [ROOT] Root for SHIELD Tablet 2.0 (Lollipop)

    Here you go: https://developer.nvidia.com/gameworksdownload#?search=Shield tablet Windows USB You can find all Shield Tablet related stuff here: https://developer.nvidia.com/develop4shield
  15. F

    Post [APP][2.3+] Lux Auto Brightness

    Lollipop does not allow apps to get a list of all running apps anymore afaik, so Lux cannot detect the current app and wont go to sleep. For the moment it should be working if you put it to sleep manually... no guarantees, though. Gesendet von meinem Nexus 5 mit Tapatalk
  16. F

    Post [MOD][FEB 10] MultiROM v33

    Sure, just flash the new kernel to the primary (internal) ROM. The secondary ROM will remain untouched, you just cannot boot into it if the new primary kernel doen't have the kexec patch. As soon as you reflash one with this patch included, you can boot to the secondary ROM again.
  17. F

    Post [ROM] [44433.001 - 2015-11-15] Eureka-ROM - Based on OTA 44433

    Don't know if it's related, but I also have issues with the screen casting tile. If I'm connected to bluetooth and playing music, then pull down the bar, the audio is not played through BT anymore, but through the phones' speakers. Anyone else with this problem?
  18. F

    Post [MOD][FEB 10] MultiROM v33

    As long as there exists a kernel for your primary ROM that has kexec-hardboot support, you can use it with MultiBoot. For SlimKat I think the aosp/stock kernel from the first/second post should work.
  19. F

    Post [MOD][FEB 10] MultiROM v33

    Each ROM has its own data partition, which means ic you do this, they take up 2x the space.
  20. F

    Post [MOD][FEB 10] MultiROM v33

    MultiROM itself does not use a noticeable amount of space. Adding and deleting ROMs is a very easy and straightforward process. But this is Nexus 7 thread, make sure to install the correct version for your N4. The best way is to download the MultiROM Manager app from Playstore and use it to set...
  21. F

    Post [MOD][FEB 10] MultiROM v33

    If you 'do not share kernel', then the ROM's default kernel will be used for secondary - it's really a straightforward thing, just go ahead and try :)
  22. F

    Post [MOD][FEB 10] MultiROM v33

    See the second post for a list of compatible kernels. Furthermore, leave the default setting of 'do not share kernel' enabled upon installation of a secondary ROM.
  23. F

    Post [MOD][FEB 10] MultiROM v33

    Yes. Every ROM is completely separate from the others, you need to flash & install the stuff separately...
  24. F

    Post [MOD][FEB 10] MultiROM v33

    Just pick the right kernel for your current internal ROM. If it's CM-based, pick one of the CM-kernels, if its AOSP-based, pick one of the stock kernels. Furthermore, you need to get the correct version (CM 10.2 or 11 / Stock 4.2.2, 4.3, 4.4, 4.4.x).
  25. F

    Post [MOD][FEB 10] MultiROM v33

    Make sure to flash the kexec-kernel to your internal ROM and not the secondary one. You do this using the normal 'install' button in recovery (and *not* something in the multirom-part/menu of the recovery).
  26. F

    Post [ROM][4.4.4] overSTOCK v6.0.1 --Nexus 5 UI-- [KTU84P][OTA-updates][AROMA]

    Aroma should actually be compatible with MultiROM, tasssadar took care of this already some time ago. I had no problems whatsoever installing your ROM as secondary (but it was the version before the most recent one).
  27. F

    Post [MOD][FEB 10] MultiROM v33

    Just search for MultiROM in G+ Communities. You'll find a new version linked in one of the recent posts regarding mako...
  28. F

    Post [MOD][FEB 10] MultiROM v33

    During what process? Why does it fail, is there any error message? Maybe a dirty flash of your ROM helps, did you try that already? Gesendet von meinem Nexus 7 mit Tapatalk
  29. F

    Post [MOD][FEB 10] MultiROM v33

    In any case you don't need to wipe, if it's not working just flash the MultiROM uninstaller zip from the first/second post. You need the modified recovery for MultiROM to install ROMs etc, it is not sufficient to have a normal TWRP installed. Try to redownload the MR ZIP and flash it again, I...
  30. F

    Post [MOD][FEB 10] MultiROM v33

    I'm currently running a beta by tasssadar which changes/adresses touchscreen & hw key issues in the boot menu. Seems working fine now... See G+ community for the test version download. ---------- Post added at 10:15 PM ---------- Previous post was at 10:13 PM ---------- @Tasssadar...
  31. F

    Post [Kernel][GPL][4.4.1/2][Jan 12][0.1.3] m_plus kernel for mako

    Thanks for adding kexec patches, I really appreciate that! :)
  32. F

    Post [MOD][FEB 10] MultiROM v33

    The file is META-INF/com/google/android/updater-script The relevant part is on the first few lines.
  33. F

    Post [MOD][FEB 10] MultiROM v33

    Had the same problem recently. You can modify the installer script in your ROM ZIP and change the device check at the beginning to the requested device. Tassadar explained in a quote of one of my posts how the recovery does the test.
  34. F

    Post [4.4/4.4.x][PATCH] Qualcomm-optimized Dalvik & Bionic libraries

    I get a reboot to recovery when flashing the dalvik patch on my Nexus 4, using stock 4.4.2 and XPosed framework. Anything I need to change for it to work? Would appreciate any hints...
  35. F

    Post [APP][2.3+] Lux Auto Brightness

    I'm using Lux Pro (latest) on a Nexus 4, including the root plugin. I'm on 4.4.2 stock using SuperSU. Two problems: - root plugin does not work for subzero levels (just doesn't adjust below zero), while subzero works when the plugin is disabled. Logcat doesn't show anything special. -...
  36. F

    Post [Kernel][GPL][4.4.1/2][Jan 12][0.1.3] m_plus kernel for mako

    Now that's a fast answer ;) I would very much appreciate it, as there are only few kernels out there that do support it, and they are all more or less heavily modified. I'm looking for a kernel like yours - only useful stuff added/changed. However, I rely on MultiROM for testing new ROMs...
  37. F

    Post [Kernel][GPL][4.4.1/2][Jan 12][0.1.3] m_plus kernel for mako

    thracemerin: Does your kernel implement Tasssadars kexec-hardboot patches, i.e. does it support MultiROM? If not, would you consider merging this?
  38. F

    Post [MOD][FEB 10] MultiROM v33

    Yes, working fine (using stock ROM).
  39. F

    Post [MOD][FEB 10] MultiROM v33

    Better be safe than sorry ;) The TWRP recovery modified by our genius Tasssadar takes care of these topics. It will skip/avoid the recovery flashing. Paths for user data etc. are mapped before an installation takes place, as well as other necessary paths (it's the same with system, too - if...
  40. F

    Post [MOD][FEB 10] MultiROM v33

    There's no problem in doing this, as long as you use a flashable zip of the stock image. Keep the following things in mind: - do not share kernel if Android versions are different (4.4 vs. 4.3 vs 4.2) - pay attention to the radio compatibility if you are using a device with a mobile radio
  41. F

    Post [MOD][FEB 10] MultiROM v33

    I just checked the zip, it indeed only tests for ro.product.device. As this passes only for grouper, I was out of luck. Any idea where I would modify AOSP code in order to include both properties in the updater-script? If not I'll have to do proper research by myself ;) Gesendet von meinem...
  42. F

    Post [MOD][FEB 10] MultiROM v33

    Yes. Search for a flashable zip of the stock rom and you're good to go.
  43. F

    Post [MOD][FEB 10] MultiROM v33

    So I already thought you had a simple solution in place, and I was right ;) Will check tomorrow and report back... Gesendet von meinem Nexus 4 mit Tapatalk
  44. F

    Post [MOD][FEB 10] MultiROM v33

    Did you test if stock 4.4 kernel works with 4.4.1 yet? If yes, there's no problem using CM 10.2 as secondary ROM. Just make sure to choose "Don't share kernel" (=default) when installing it. Furthermore, I think you need to be on the JB version of the radio (.84 I think) as the newest (.97) is...
  45. F

    Post [MOD][FEB 10] MultiROM v33

    Tasssadar: I just tried to install a self-built AOSP ROM (no modifications, built straight from aosp source) on my Tilapia as a secondary ROM. Install process aborts with 'device is a grouper'. If I remember correctly, you modified TWRP to accept both, grouper and tilapia, in earlier versions...
  46. F

    Post [MOD][FEB 10] MultiROM v33

    You will soon be wondering how you could ever live without MultiROM if you have the flashaholic genes... ;) Gesendet von meinem Nexus 7 3G mit Tapatalk
  47. F

    Post [MOD][FEB 10] MultiROM v33

    No, I think you misunderstood - you can restore a nandroid backup to a secondary ROM: Add ROM -> Backup (instead of 'ZIP file'). Key is to add a 'new' ROM, I don't think you can restore a nandroid to an existing ROM - but it doesn't matter anyway. I don't know why Tasssadar put this warning...
  48. F

    Post [MOD][FEB 10] MultiROM v33

    You can create a secondary ROM from a TWRP backup if that's what you want. Otherwise you could use TitaniumBackup or a similar app. But why do you need to start from scratch when updating a secondary ROM? Are you aware that you can flash ZIPs for a ROM using 'list ROMs'? That's also valid for...
  49. F

    Post {ROM} {4.4} {Swigs' Omnirom} {Build 2}

    Until swiggins gets around to including this, you can install the XPosed framework which thenn offers a module for this purpose (named something with network speed, can't remember exactly). Only make sure you use the KitKat compatible xposed beta. Gesendet von meinem Nexus 7 3G mit Tapatalk
  50. F

    Post {ROM} {4.4.1} {Swigs' Slimrom} {Build 5}

    Saw some new repos on your github. Are you going forward with the rebase to omni? Gesendet von meinem Nexus 7 3G mit Tapatalk