Related
[Q&A] Hyperdrive Rom Note 10.1 2014 ║ Non-Development Discussion ║ Support
Hyperdrive Rom Support Thread
This Thread is Started for Help and Support for those Members who cannot post in development threads or do not have enough posts to do so.
You may ask your general questions/issues here.
Please respect all members, especially those trying to provide you with help.
Please read the Frequently Asked Questions in the Rom Thread HERE before asking questions
Thank you
smart scrolling ???
Hello ,
I flashed Hyperdrive+RLS3 after wipe data/cache/dalvik cache ,
with hope that smart scroll will work , but it's not working at all,apart from flashing eye in notification panel.
Please solve that problem some how ....
By the way nice work on rom :good: and .
Missing Lock Settings?
To begin, I am reporting a (possible) bug for Hyperdrive RLS3 on my SM-P600 on TWRP 2.7.0.2. I have verified the md5 on my zip prior to each flash. I have been able to replicate/repeat this "bug" on multiple installs (where I have fully/cleanly wiped the device each time).
I've found that my lock screen security detailed options are forever set to those for "swipe" regardless of what I have chosen for my lock screen security option. Even if I set a pattern, pin, password, etc. lock, the options below are always set to those as if I had chosen "swipe" as my lockscreen setting. The lock option that I am selecting still works, but I am unable to see or tweak any of the specific settings associated with each of the particular lock screen security options (e.g. I am unable to toggle the visibility of my pattern, as this option doesn't appear, if I choose the "pattern" lock option. However, the device still asks me for a pattern to unlock with). I can only ever see/modify the "swipe options" such as the "unlock effect", "ink effect", etc.
Is anyone else having this problem too?
Good day all, I just installed rls3 and everything is working fine so far except the penwindow/multi window manager. Adding the apps I want follwed by saving and rebooting does not do anything for me? Anybody have the same issue or am I not doing to correctly?
shooterf15 said:
Good day all, I just installed rls3 and everything is working fine so far except the penwindow/multi window manager. Adding the apps I want follwed by saving and rebooting does not do anything for me? Anybody have the same issue or am I not doing to correctly?
Click to expand...
Click to collapse
Observed, I will look into it and hopefully fix
Latest Netflix Working
I have installed RLS3.1 and Netflix v.3.7.1 is working fine for me…no xposed module and no version rollback.
Here are a few of the choices I made when installing Hyperdrive. Maybe this information can help the developer or other users figure out where the problem with signing in is (or isn’t).
I steered clear of many of the eye candy options simply due to personal preference.
I mainly use Hyperdrive for the fixes, battery life and speed compared to stock.
Full system wipe through TW…not just data/cache.
Hyperdrive TW Note 10.1 Launcher
Hyperdrive Light Note Pro UI
Very few of the Samsung apps (Dropbox, Font Pack, Link, STranslate)
No Weather Widget
No Email App (I use K-9)
No Audio Mod
Stock Note Boot Animation
Ad Blocking
ES File Manager (even though I use X-plore)
Very few Google AOSP (Maps, Youtube, Camera)
Samsung Music Player
No additional keyboard (I use Dashlane’s)
Tubemate
Stock 4.4 Kernel
Once set up I installed Nova Launcher, TiBu, Lux and Greenify.
I also used ROM Toolbox to edit build.prop product model entry to say SM-P600 instead of SM-T800.
The only HD Tweaks are show Network Traffic, Date Style, Battery Style, and Ink Effect.
The only xposed modules active are App Settings, Greenify, and NlpUnbounce.
That’s about it for system related apps/settings.
I hope this helps.
Not certain but that change might have fixed netflix app for me.
I made the change, rebooted, cleared the app cache and i could sign in. I couldn't before.
Whistler1813 said:
I also used ROM Toolbox to edit build.prop product model entry to say SM-P600 instead of SM-T800.
Click to expand...
Click to collapse
ultim said:
Not certain but that change might have fixed netflix app for me.
I made the change, rebooted, cleared the app cache and i could sign in. I couldn't before.
Click to expand...
Click to collapse
That's good to know. If that is, in fact, the fix then it's a heck of a lot easier for folks to implement than re-wiping and selecting different system mods.
I hope some other Hyperdrive folks that are having problems with Netflix try this out as well. I'm also wondering if maybe the model number mismatch is causing some app or system issues that only seem to affect certain people and not others with otherwise the exact same configuration.
wake up problem
Everything works totally fine except wake up it takes 5-8 sec ... can u please help
Donation
Long time lurker, and have never signed in to post before, therefore I don't have enough posts to write in the Development section, but I just wanted you to know Scott I just slid you $40.00 for a new tablet. Keep this awesome rom moving onwards!
Transaction Id: 55K23427EM124153F
unstabl1 said:
Long time lurker, and have never signed in to post before, therefore I don't have enough posts to write in the Development section, but I just wanted you to know Scott I just slid you $40.00 for a new tablet. Keep this awesome rom moving onwards!
Transaction Id: 55K23427EM124153F
Click to expand...
Click to collapse
Thanks for your support!
Not sure if it's a kernel or rom issue but I'm on hyperdrive 3.0 with xluco and I bought this dual flashdrive:
Kingston Digital 64GB Data Traveler Micro Duo USB 3.0 Micro USB OTG (DTDUO3/64GB) https://www.amazon.com/dp/B00LIXJ54K/ref=cm_sw_r_awd_uVaqub148TMN0
Which works perfect on my S4 with KK, it gets detected without problems by the SM-P600 but I cannot explore with either My Files or ES Explorer, it gives me a systemui FC.
Anybody else can test?
Sent from my SGH-I337M using Tapatalk
refurbed Note 10.1
Newegg has refurbished 16GB notes for $350 now and Groupon matches and also has the 32GB for $20 more. Hopefully we'll see another Hyperdrive version - I'm planning on installing mine this week
Hyperdrive ROM, Pen window manager not working
So I installed Hyperdrive rom RLS 3.1 for my sm-p600, problem is that the pen window manager app is not working, I select my app (MX video player) in the options of pen window manager to enable it in pen mode but after restarting it still does not show up when i try to edit the apps available for pen windows using the s-pen
Edit: I fixed it, problem was that I have a separate app for the pen window manager that I restored using titanium backup. I uninstalled it in the play store and used the native pen window manager via the Hyperdrive rom tweak app..
wiped to reinstall: cmd adb cant locate the device
I may seem like it, but im not a noob... long story short, Im dealing with a TBI, so im a bit rusty.
I have a sm-p600, flashed Chain fire with, installed nandroid and backed everything up, flashed 4.4.2 firmware with odin. I flashed twrp recovery and sideloaded hyperdrive custom rom via adb.
Everything was great, excellent rom! I had a few issues with it, mainly touchWiz would crash if I tried to change the lock screen wallpaper via pressing and holding the home screen. Also, settings would also randomly crash as well. I did some research through the forums and came to the conclusion that I might have messed up on selecting the options during installation (something with the launcher). SOOOO, my dumb a** attempts to re-install the rom. I factory reset, wiped, and cleaned the whole thing with bleach ( metaphorically aka twrp). I reboot in TWRP recovery, go to advanced--->sideload--->... then my win 7 pc fails to install the MTP drivers. I reboot, replug, "overlap drivers", get it to detect, but adb cant detect the device. So, I bust open ctrl panel uninstall the samsung drivers, adp drivers, and pdanet; then, i reinstalled different drivers that i found from another thread and i cant detect the device from cmd adb commands.
I think it might be a usb debugging issue, because if everything was left constant as far as drivers go and it was wiped, the issue must be occurring on the tablet.
I forgot about that thought when I woke up and messed around with the drivers downloading universal drivers and what not. Device manager now recognizes the device as google nexus adb interface but cmd adb still cant find the device.
Please help!
105
I have a question. I have used xkat 4 rom for two weeks and my battery life is 8,30-9 ours SOT. I know every device and user is different, but how many ours of SOT do you get with this rom? Just to know, because I am doubting to change to this rom.
Thank you
should i start from scratch or throw the the custom rom on an external
xdaprotege said:
I may seem like it, but im not a noob... long story short, Im dealing with a TBI, so im a bit rusty.
I have a sm-p600, flashed Chain fire with, installed nandroid and backed everything up, flashed 4.4.2 firmware with odin. I flashed twrp recovery and sideloaded hyperdrive custom rom via adb.
Everything was great, excellent rom! I had a few issues with it, mainly touchWiz would crash if I tried to change the lock screen wallpaper via pressing and holding the home screen. Also, settings would also randomly crash as well. I did some research through the forums and came to the conclusion that I might have messed up on selecting the options during installation (something with the launcher). SOOOO, my dumb a** attempts to re-install the rom. I factory reset, wiped, and cleaned the whole thing with bleach ( metaphorically aka twrp). I reboot in TWRP recovery, go to advanced--->sideload--->... then my win 7 pc fails to install the MTP drivers. I reboot, replug, "overlap drivers", get it to detect, but adb cant detect the device. So, I bust open ctrl panel uninstall the samsung drivers, adp drivers, and pdanet; then, i reinstalled different drivers that i found from another thread and i cant detect the device from cmd adb commands.
I think it might be a usb debugging issue, because if everything was left constant as far as drivers go and it was wiped, the issue must be occurring on the tablet.
I forgot about that thought when I woke up and messed around with the drivers downloading universal drivers and what not. Device manager now recognizes the device as google nexus adb interface but cmd adb still cant find the device.
Please help!
Click to expand...
Click to collapse
Sorry to double post, but can I just throw hyperdrive rom on a external sd and flash threw twrp? or do I have to download stock 4.4.2 firmware flash with odin, rootcheck/reroot, and sideload hyperdrive rom via sideload if it detects after the firmware flash?
xdaprotege said:
Sorry to double post, but can I just throw hyperdrive rom on a external sd and flash threw twrp? or do I have to download stock 4.4.2 firmware flash with odin, rootcheck/reroot, and sideload hyperdrive rom via sideload if it detects after the firmware flash?
Click to expand...
Click to collapse
i just read real quick but yes you can put on ext. sd card and flash from there with twrp.Just make sure when you hit install your checking external card.It should show up.Are you already rooted ?Im having the same problem when trying to connect my tablet to my pc.It doesnt reconize it and i also cant pull any files off with a decompile program cause it doesnt or adb doesnt see it.
Softbrick
mikep2323 said:
i just read real quick but yes you can put on ext. sd card and flash from there with twrp.Just make sure when you hit install your checking external card.It should show up.Are you already rooted ?Im having the same problem when trying to connect my tablet to my pc.It doesnt reconize it and i also cant pull any files off with a decompile program cause it doesnt or adb doesnt see it.
Click to expand...
Click to collapse
I was rooted, but im not 100% sure I still am after i did the advance wipe. Twrp asks if I want to install super su right before I reboot, so I assume I am. I'm not exactly sure what you did and what your symptoms are, but I personally did a twrp advance wipe including the internal storage which was where my rom was located. As a result, the tablet is soft bricked b/c it doesnt have an OS.
You can use odin to AP/PDA flash the stock firmware, but it HAS to be the same firmware build version of your device before the brick occurred. AKA bricked on 4.4.2 custom kitkat, then flash stock 4.4.2 kitkat via odin. Just make sure the software is for your device and country before installing.(http://www.galaxynote3update.com/fi...-the-unbrick-and-recovery-guide-just-for-you/).
Here's a helpful link that you might find useful: http://forum.xda-developers.com/showthread.php?t=2608951
My question is: can I just flash the custom rom back onto the device or do I have to flash the orignal firmware?
Install on Note Pro
Hi I have the 12.2 Note Pro and was wondering if this ROM will work on it?
I'd like to know if I should update or not. A while back I had updated to a version that didn't support usb otg (on my LG G2) without realizing it. I had decided to do a clean wipe of everything and reinstall from my meenova, but surprise,no usb otg. I didn't have access to a computer and had to use the wife's phone to adb push the ROM over to my phone etc. It was nice to improvise and find a solution, but I felt like a jacka__ for not paying attention in the first place. I'm currently running 2.8.6.1 -Do I "need" to update? Are there any pros or cons? (For instance, if I remember correctly there is a change in how files are "pushed over". In the past the file itself was transferred over to the unit... Now the file stays on the host and twrp grabs it as needed. ) I may be off base so if someone would like to use this question as a teaching moment, I'm all ears. Thanks in advance for your replys.
I like to stay up to date w/ the latest version, that being 2.8.7.0 currently. You can read up on the fixes and updates in the newest version here...
https://twrp.me/site/update/2015/06/22/twrp-2.8.7.0-released.html
Broken Screen Castriginally Rooted Sunshine, Viper Rom, data wiped, safety net fail
Hello, hopefully someone can help me. I have a HTC 10 unlocked US version that I rooted a bit ago with Sunshine and had Chainfire SuperSU installed. A big reason I ended up with the HTC was the root support as my Samsung S6 proved unrootable and thus I was not happy with it since I couldn't use Titanium Backup or use AppRadio Unchained with Miracast due to needing root to allow the touchscreen touches on the Pioneer radio to communicate with the phone. Before I was using an S4 with an MHL cable but the microUSB port gave out on me.
I was still using the stock ROM after root as I was happy with it. On occasion I need to use Barnacle or WiFi Tether router but had problems getting them to work very well. I ended up deciding to switch to Viper Rom which was actually what I had on the S4. I picked Magisk root so I could use Android Pay in the future if I wanted. I did a full backup in TWRP before this. After installing I tried to use Screen Cast to my Screen Beam Mini 2 and it failed, I then tried with the Smart TV and that failed as well. Both of these worked on the stock rooted ROM.
I restored the backup from TWRP but when it booted, it asked me for an encryption password which was my lock screen password. Problem was I've never had either on this phone and tried the 2 pins that I use for most things to no avail. I gave up since I had Titanium Backups and did a Wipe all data in TWRP. This got Android back up and going again, so I reinstalled Viper Rom and it still fails the SafetyNet check in there. Hide is turned on and I chose every google app during install and have not installed anything else at all.
Does anyone have any idea what may be the issue? Venom Tweaks and Venom Hub are on there and it still will not connect to any wireless display. So after wiping my phone which was working great except for the screen casting, I'm not any farther ahead. The firmware is still 6.0 if that matters. If the Viper Rom won't work with Screen Cast, will any of the custom Roms or do I need to go back to stock rooted? It was quite the disappointment when I did the restore and couldn't access the phone without wiping first, defeats the purpose of a backup which I've never had an issue with before.
I found some guides but they were all about if you had SuperSU on there before which with the full wipe I assume does not apply.
Ironically maybe, my new job is customer support for software and the machines it runs and that is more then frustrating as there is not many help documentation and there are all kinds of things that can go wrong and the error messages are not very good at all. For the guys with years of experience it's probably not as bad, but the job requires travel too, so they aren't always around. It's bad enough when my own stuff has problems I struggle to figure out but when someone else is trying to do their job and you are their lost resort to fix things, it's pretty stressful. So I apologize if this was something found by an easy search, I really do try before I ever post anything but just like work, there are so many variables and I don't know which ones matter in this case.
Anyway, thanks to anyone in advance that may be able to help, I"m out of ideas aside from flashing stock firmware and rooting from scratch again, which was months ago and I don't remember the process. Things were a lot easier back in KitKat it seems.....
sevenspeed said:
Hello, hopefully someone can help me. I have a HTC 10 unlocked US version that I rooted a bit ago with Sunshine and had Chainfire SuperSU installed. A big reason I ended up with the HTC was the root support as my Samsung S6 proved unrootable and thus I was not happy with it since I couldn't use Titanium Backup or use AppRadio Unchained with Miracast due to needing root to allow the touchscreen touches on the Pioneer radio to communicate with the phone. Before I was using an S4 with an MHL cable but the microUSB port gave out on me.
I was still using the stock ROM after root as I was happy with it. On occasion I need to use Barnacle or WiFi Tether router but had problems getting them to work very well. I ended up deciding to switch to Viper Rom which was actually what I had on the S4. I picked Magisk root so I could use Android Pay in the future if I wanted. I did a full backup in TWRP before this. After installing I tried to use Screen Cast to my Screen Beam Mini 2 and it failed, I then tried with the Smart TV and that failed as well. Both of these worked on the stock rooted ROM.
I restored the backup from TWRP but when it booted, it asked me for an encryption password which was my lock screen password. Problem was I've never had either on this phone and tried the 2 pins that I use for most things to no avail. I gave up since I had Titanium Backups and did a Wipe all data in TWRP. This got Android back up and going again, so I reinstalled Viper Rom and it still fails the SafetyNet check in there. Hide is turned on and I chose every google app during install and have not installed anything else at all.
Does anyone have any idea what may be the issue? Venom Tweaks and Venom Hub are on there and it still will not connect to any wireless display. So after wiping my phone which was working great except for the screen casting, I'm not any farther ahead. The firmware is still 6.0 if that matters. If the Viper Rom won't work with Screen Cast, will any of the custom Roms or do I need to go back to stock rooted? It was quite the disappointment when I did the restore and couldn't access the phone without wiping first, defeats the purpose of a backup which I've never had an issue with before.
I found some guides but they were all about if you had SuperSU on there before which with the full wipe I assume does not apply.
Ironically maybe, my new job is customer support for software and the machines it runs and that is more then frustrating as there is not many help documentation and there are all kinds of things that can go wrong and the error messages are not very good at all. For the guys with years of experience it's probably not as bad, but the job requires travel too, so they aren't always around. It's bad enough when my own stuff has problems I struggle to figure out but when someone else is trying to do their job and you are their lost resort to fix things, it's pretty stressful. So I apologize if this was something found by an easy search, I really do try before I ever post anything but just like work, there are so many variables and I don't know which ones matter in this case.
Anyway, thanks to anyone in advance that may be able to help, I"m out of ideas aside from flashing stock firmware and rooting from scratch again, which was months ago and I don't remember the process. Things were a lot easier back in KitKat it seems.....
Click to expand...
Click to collapse
Hi,
I'm not quite sure what you're wanting help with. Get screen casting working, or getting back to stock?
Hello, I'd just like to get screencast working on Viper or another custom ROM if possible, if it's not possible I should be able to figure out how to go back to stock and root again. Screencast was working on the stock ROM with root. Being able to restore my backup would be nice but I think when I installed Viper I did not check the force decryption as it said you had to format the data in TWRP and I tried it without a wipe, which did work. I still don't get how it set a password when I was never prompted for one and never had a lockscreen password of any sort. I didn't unfortunately do a backup of Viper.
Tarima said:
Hi,
I'm not quite sure what you're wanting help with. Get screen casting working, or getting back to stock?
Click to expand...
Click to collapse
I did a data format from TWRP which uninstalled Magisk I suppose and the Manager app says System not Rooted yet still fails the safetynet check, that makes no sense to me.
sevenspeed said:
Hello, I'd just like to get screencast working on Viper or another custom ROM if possible, if it's not possible I should be able to figure out how to go back to stock and root again. Screencast was working on the stock ROM with root. Being able to restore my backup would be nice but I think when I installed Viper I did not check the force decryption as it said you had to format the data in TWRP and I tried it without a wipe, which did work. I still don't get how it set a password when I was never prompted for one and never had a lockscreen password of any sort. I didn't unfortunately do a backup of Viper.
Click to expand...
Click to collapse
I cast my screen with Viper10 and Chromecast. It might be the casting app you are using.
Thanks, at this point I guess I'm going to flash the stock RUU and then figure out how to get twrp and Viper with the Magisk back on there since I've already wiped the data and my backup is encrypted. Is it okay to use Sunshine or do I need to use another method?
I was trying to use the HTC connect, maybe that is the issue. I need to cast with Miracast not chromecast, is there an app that will work for that? My Screen Beam Mini 2 actually got broken in a traffic jam, laptop bag fell off the seat when I had to slam the brakes and caught and ripped the power jack out of it I tried a chromecast instead so I could possibly use that just to watch a video or something without the cell screen on, but using the phone for the hotspot does not let it connect to the chromecast I found, so I went back and exchanged for another Miracast dongle.
Thanks again for the help btw, since I lost my data I just need to figure out how to get to Viper rom with Magisk after flashing the stock RUU and then if I need an app besides HTC connect to use Miracast, what that app would be.
xunholyx said:
I cast my screen with Viper10 and Chromecast. It might be the casting app you are using.
Click to expand...
Click to collapse
sevenspeed said:
Thanks, at this point I guess I'm going to flash the stock RUU and then figure out how to get twrp and Viper with the Magisk back on there since I've already wiped the data and my backup is encrypted. Is it okay to use Sunshine or do I need to use another method?
I was trying to use the HTC connect, maybe that is the issue. I need to cast with Miracast not chromecast, is there an app that will work for that? My Screen Beam Mini 2 actually got broken in a traffic jam, laptop bag fell off the seat when I had to slam the brakes and caught and ripped the power jack out of it I tried a chromecast instead so I could possibly use that just to watch a video or something without the cell screen on, but using the phone for the hotspot does not let it connect to the chromecast I found, so I went back and exchanged for another Miracast dongle.
Thanks again for the help btw, since I lost my data I just need to figure out how to get to Viper rom with Magisk after flashing the stock RUU and then if I need an app besides HTC connect to use Miracast, what that app would be.
Click to expand...
Click to collapse
For returning to full stock, go on HTC's site and get the latest ruu for Unlocked. Run it from your pc, while being mindful of the instructions and warnings that come with the file. After that, if you want a custom rom, flash the latest twrp and whichever rom you want.
You don't need Sunshine for anything you mentioned - Sunshine is to get s-off on your phone while is not needed here.
Tarima said:
For returning to full stock, go on HTC's site and get the latest ruu for Unlocked. Run it from your pc, while being mindful of the instructions and warnings that come with the file. After that, if you want a custom rom, flash the latest twrp and whichever rom you want.
You don't need Sunshine for anything you mentioned - Sunshine is to get s-off on your phone while is not needed here.
Click to expand...
Click to collapse
Thanks for the help. I did end up doing the ruu ( which on windows 10 took some work,) then flashed twrp again and installed magisk 13. Safety net passed and screen cast worked. Then I installed viper Rom. Safety net failed but it had overwrote with magisk 12. I flashed magisk 13 again and then safety net passed so looks like that was the issue even if not the only one. Looks like titanium backup has put everything back on too.
So only thing left to figure out is how to do a backup that doesn't encrypt the data with an unknown password but it appears everything is working including the battery charge limiter app.
Thanks again
sevenspeed said:
Thanks for the help. I did end up doing the ruu ( which on windows 10 took some work,) then flashed twrp again and installed magisk 13. Safety net passed and screen cast worked. Then I installed viper Rom. Safety net failed but it had overwrote with magisk 12. I flashed magisk 13 again and then safety net passed so looks like that was the issue even if not the only one. Looks like titanium backup has put everything back on too.
So only thing left to figure out is how to do a backup that doesn't encrypt the data with an unknown password but it appears everything is working including the battery charge limiter app.
Thanks again
Click to expand...
Click to collapse
Glad it worked. What is the battery charge limit app you mentioned?
Hi guys,
I am using the stock rom now since the day I got it and unlocked the BL and installed Magisk for root and SafetyNet. Phone worked fine all the time (lazy me never changed the rom) until recent.
Most applications like Instagram, Snapchat (and all that garbage) and others randomly crash recently.. Application stopped working or process.media whatever stopped. Did try to do the usual stuff removing cache, but now this also does not work anymore. Also it's time to update because the WiFi driver has this RCE flaw(CVE-2017-13292) in it and well, lots of other bugs in the rom. The most irritating bugs that all my android devices had. The flashlight stops working because of the camera initialization or something, need to reboot the phone in order to use the flashlight again (when I was with a hot soldering iron in my car waiting for the device to reboot to solder some ****ing wires under the dashboard pissed me off really good. Though long time ago, but you get the idea... )
I did try to update my device using OTA (I knew it wasn't going to work, because mine is rooted). I did try it and the update failed(lol), luckily the phone still booted :cyclops:
What should I do now, can I just flash a stock rom using twrp or is there another stable rom that is clean like the lenovo roms without all the garbish? Which ones are advised?
The version of the rom I am using as of now is in my signature. I do not really need Magisk anymore for now, I had it installed mostly for NFC emulator but the company I emulated the card for no longer exists so meh.. No need for emulating anymore Pachting ads away with luckypatcher is also not worth it and there's like no proper way of blocking ads so I'll rather live with it instead of messing around and putting effort in it.
NiTrOwow said:
Hi guys,
I am using the stock rom now since the day I got it and unlocked the BL and installed Magisk for root and SafetyNet. Phone worked fine all the time (lazy me never changed the rom) until recent.
Most applications like Instagram, Snapchat (and all that garbage) and others randomly crash recently.. Application stopped working or process.media whatever stopped. Did try to do the usual stuff removing cache, but now this also does not work anymore. Also it's time to update because the WiFi driver has this RCE flaw(CVE-2017-13292) in it and well, lots of other bugs in the rom. The most irritating bugs that all my android devices had. The flashlight stops working because of the camera initialization or something, need to reboot the phone in order to use the flashlight again (when I was with a hot soldering iron in my car waiting for the device to reboot to solder some ****ing wires under the dashboard pissed me off really good. Though long time ago, but you get the idea... )
I did try to update my device using OTA (I knew it wasn't going to work, because mine is rooted). I did try it and the update failed(lol), luckily the phone still booted :cyclops:
What should I do now, can I just flash a stock rom using twrp or is there another stable rom that is clean like the lenovo roms without all the garbish? Which ones are advised?
The version of the rom I am using as of now is in my signature. I do not really need Magisk anymore for now, I had it installed mostly for NFC emulator but the company I emulated the card for no longer exists so meh.. No need for emulating anymore Pachting ads away with luckypatcher is also not worth it and there's like no proper way of blocking ads so I'll rather live with it instead of messing around and putting effort in it.
Click to expand...
Click to collapse
Android Pie ROMs are pretty stable and usable now (everything works but be aware that all custom ROMs will have darker video recording in comparison to stock)
ROMs of choice:
On Oreo: RR(Unofficial final builds by fullbustah),CrDroid,Arrow or Xtended
On Pie: CrDroid(has an extended desktop bug), SuperiorOs,ArrowOs,AospExtented
I also recommend installing a modded Gcam version because that will significantly boost your camera quality without any throwback or setback.
To install a pie ROM, I have written a tutorial somewhere in our guides section. You will find it pretty quickly.
Also Magisk 18.1 (latest for now) and Adaway still blocks ads perfectly. (Systemless hosts enabled in Magisk settings needed)
I recommend joining Lenovo P2 telegram group for latest news, support and download links.
sm00th4f3 said:
Android Pie ROMs are pretty stable and usable now (everything works but be aware that all custom ROMs will have darker video recording in comparison to stock)
ROMs of choice:
On Oreo: RR(Unofficial final builds by fullbustah),CrDroid,Arrow or Xtended
On Pie: CrDroid(has an extended desktop bug), SuperiorOs,ArrowOs,AospExtented
I also recommend installing a modded Gcam version because that will significantly boost your camera quality without any throwback or setback.
To install a pie ROM, I have written a tutorial somewhere in our guides section. You will find it pretty quickly.
Also Magisk 18.1 (latest for now) and Adaway still blocks ads perfectly. (Systemless hosts enabled in Magisk settings needed)
I recommend joining Lenovo P2 telegram group for latest news, support and download links.
Click to expand...
Click to collapse
Alright thanks for the information. I will try to flash my phone next week. I do have one more question. Is there a hardware selftest or test menu in the stock recovery or bootloader because I have a bad feeling that my board might be about to fail. I think this because all kinds of funky things did happen the last few days (I hope the mainboard is still fine, fingers crossed).. I know my old Lenovo had this menu and this way I found out it was dead. Well it was obviously dead but for sure after the test failed because Android didn't boot anymore, and was not able to flash another rom and get that one to boot up.
NiTrOwow said:
Alright thanks for the information. I will try to flash my phone next week. I do have one more question. Is there a hardware selftest or test menu in the stock recovery or bootloader because I have a bad feeling that my board might be about to fail. I think this because all kinds of funky things did happen the last few days (I hope the mainboard is still fine, fingers crossed).. I know my old Lenovo had this menu and this way I found out it was dead. Well it was obviously dead but for sure after the test failed because Android didn't boot anymore, and was not able to flash another rom and get that one to boot up.
Click to expand...
Click to collapse
I'm not sure if the p2 owns a menu like that.
You might wanna boot to bootloader and navigate through the small menu via volumekeys.
But otherwise...no idea.
Good luck!
Does anyone have experience with this Official LineageOS Rom in Pixel 3a?
Official Device Info/Wiki:
https://wiki.lineageos.org/devices/sargo
Official Installation instructions:
Install LineageOS on sargo | LineageOS Wiki
wiki.lineageos.org
Official Download Link for LineageOS ROM and Lineage RECOVERY:
LineageOS Downloads
download.lineageos.org
Horninho10 said:
Does anyone have experience with this Official LineageOS Rom in Pixel 3a?
Official Device Info/Wiki:
https://wiki.lineageos.org/devices/sargo
Official Installation instructions:
Install LineageOS on sargo | LineageOS Wiki
wiki.lineageos.org
Official Download Link for LineageOS ROM and Lineage RECOVERY:
LineageOS Downloads
download.lineageos.org
Click to expand...
Click to collapse
Yes, it runs nice and smooth, I was recently on LOS.
The post I'm about to make is not related to anything technical, so I'm not sure if it's appropriate on this forum, but I'm going to post it anyway...
Is there any advantages lineage has over stock? Seems like it's not really worth it. Right? What do you guys think about build?
pojr said:
The post I'm about to make is not related to anything technical, so I'm not sure if it's appropriate on this forum, but I'm going to post it anyway...
Is there any advantages lineage has over stock? Seems like it's not really worth it. Right? What do you guys think about build?
Click to expand...
Click to collapse
I personally am running stock for SafetyNet purposes at the moment. I do think it's worth checking out if you want a few more options for customization. It was a very smooth ROM, but LOS in specific is not my cup of tea.
MoistPicklez said:
I personally am running stock for SafetyNet purposes at the moment. I do think it's worth checking out if you want a few more options for customization. It was a very smooth ROM, but LOS in specific is not my cup of tea.
Click to expand...
Click to collapse
That is a very good point actually. That is one thing I was never a big fan of with the stock OS, is just the lack of options you have to customize your device. Might be worth getting it, even though it's a downgrade to Android 10
pojr said:
That is a very good point actually. That is one thing I was never a big fan of with the stock OS, is just the lack of options you have to customize your device. Might be worth getting it, even though it's a downgrade to Android 10
Click to expand...
Click to collapse
Test it out if you're interested, but A11 ROMs are likely around the corner. I bet we'll get a build or two of something else down the road. Cheers!
I've personally had GPS issues (while using OpenGapps Pico) with the official release. Hoping A11 builds fix it.
Aah, a much needed rom option for sargo/pixel 3a ! There has been a lot of silence around the pixel 3a in this regard.
I'm trying it out now. First thing I noticed is SIM manager keeps crashing every minute or so (I'm in the Netherlands on the Ben/T-mobile network). If there is a dev out there I can supply a logcat or something like it if needed.
Meanwhile I disabled the SIM manager to get rid of the constant crash notifications. I'll try and report back any issues I encounter (But if there are too many of them, I'll have to revert back to Dirty Unicorns, although that rom development seems to have stalled pretty much).
I seem to have overcome my GPS woes! My installation process was the following:
Install the last Android Q factory image
Flash LOS boot, go to recovery
Factory reset
Install update > adb sideload LOS zip
Very important(?) - go back to main menu, advanced, reboot to recovery
Install update > adb sideload opengapps pico zip > yes, install anyway
Sign in to your Google account during the initial setup process
Test GPS with an app (Google Maps, Waze, OSMAnd, Pokémon Go... )
The only issue I seem to have now is that the Google Fi app doesn't seem to get that my Fi service is ESIM based, and prompts me to order a physical SIM card, but playing with the mobile service settings seems to have gotten my service set up anyway.
EDIT: After talking with Google Fi support, going to Settings > System > Reset Options > Reset Wi-Fi, mobile & Bluetooth, check erase downloaded SIMs, then trying to activate Google Fi again in the app, it worked.
In addition to the helpful tips from @Mokura3rd. My two cents: I had some gps issues as well, but didn't test it to great extent. Here's a description of my (rather weird issue):
When I first installed Lineageos (jan16 - my previous comment), Google maps and Gps status were able to find gps signal (and quicky), but strava didn't find any gps signal (it didn't even ask for permission, which I granted manually - to no avail).
Some time after the first OTA update, I checked strava again. And it worked without issue. So there might have been merged some bugfixes that fixed gps issues on recent builds.
guys, is it true you have to jump down to Android 10 in order to get the latest lineage? that doesn't make sense. Don't you have to wipe your phone in order to switch from stock to custom anyway? seems pointless to downgrade to stock 10 first. what's your guys stance on this?
pojr said:
guys, is it true you have to jump down to Android 10 in order to get the latest lineage? that doesn't make sense. Don't you have to wipe your phone in order to switch from stock to custom anyway? seems pointless to downgrade to stock 10 first. what's your guys stance on this?
Click to expand...
Click to collapse
Because lineageos 17.1 is based on Android 10, you have to revert to stock Android 10 before you install it. The same goes for any ROM that is based on Android 11.
MoistPicklez said:
Because lineageos 17.1 is based on Android 10, you have to revert to stock Android 10 before you install it. The same goes for any ROM that is based on Android 11.
Click to expand...
Click to collapse
Thank you for clearing that up with me. Now I at least have an answer on that. With that said, why would that be? Don't you have to wipe your phone in order to switch from stock to custom anyway? Is the ROM gonna say "we have somehow detected the you once had Android 11 before you wiped your OS"
pojr said:
Thank you for clearing that up with me. Now I at least have an answer on that. With that said, why would that be? Don't you have to wipe your phone in order to switch from stock to custom anyway? Is the ROM gonna say "we have somehow detected the you once had Android 11 before you wiped your OS"
Click to expand...
Click to collapse
Android changes quite a bit between versions like dynamic partitions and other jazzy stuff. For example TWRP. It works on Android 9, but changes to our device made TWRP incompatible with A10 and A11. (Good news on that though, we just got TWRP 3.5.0_9-0, though I have not tested it.)
MoistPicklez said:
Android changes quite a bit between versions like dynamic partitions and other jazzy stuff. For example TWRP. It works on Android 9, but changes to our device made TWRP incompatible with A10 and A11. (Good news on that though, we just got TWRP 3.5.0_9-0, though I have not tested it.)
Click to expand...
Click to collapse
did not realize we got a new twrp version. thats a step in the right direction. with that said, that info is good to know. i'm a lazy ass and prolly not gonna test out lineage os until it gets on 11 lmao.
For whoever needs it. I sure did after a derped update last week!
tl;dr install update, disable all modules before booting, get the latest recovery image and patch it, install with fastboot. long version below, just in case.
How To OTA With Magisk, Painlessly:
Open updater and download the OTA.
Press install and let it do its thing, but DON'T REBOOT YET.
Go to Magisk and disable all your modules.
Okay, you can reboot now. It might take longer than usual, it's a system update.
Open Magisk and note that it's no longer installed, don't panic.
Download the recovery image matching your update from here: https://download.lineageos.org/sargo
Open Magisk and patch the img you just downloaded.
Copy the magisk_patched_(random).img to a folder on your computer where you're able to access fastboot.
Reboot your phone to bootloader: either by the advanced power menu, enabled in developer settings, or by restarting and holding Volume Down while the phone boots up.
Open up your terminal/commandline/etc where you moved the image file.
Type the command "fastboot flash boot magisk_patched_*****.img", where the last part is the random string that got generated in the patching process. Press Enter.
After the command finishes, use the volume keys to scroll through the bootloader menu until you see "Start". Press the power button.
Your phone should reboot back to the OS, you can now go back to Magisk and re-enable your modules at your leisure.
So the one problem 'I've been having is with custom kernels. I've tried Elemental X & Gats Gulch. With both I lose wifi capability. Once I restore my lineage kernel viola problem solved. Now I've used both these kernels in the past on different builds so I know it isn't the kernel itself rather something related to the lineage build itself & the act of installing a custom kernel. Both kernels returned exactly the same type of error. WIFI attempts to turn on but returns to the off Position. If one attempts to activate the Wifi Icon dropdown during the System UI Crashes. Any input would be great. Other than this little hiccup
Lineage is running absolutely great. Best battery life of any custom OS by far. Sargo stays snappy, my kernel tweaks remain in place. Root maintains over system restores. Love it.
EDIT: ## By the way using Elemental X Kernel Manager App to flash ##
harryharryharry said:
Aah, a much needed rom option for sargo/pixel 3a ! There has been a lot of silence around the pixel 3a in this regard.
I'm trying it out now. First thing I noticed is SIM manager keeps crashing every minute or so (I'm in the Netherlands on the Ben/T-mobile network). If there is a dev out there I can supply a logcat or something like it if needed.
Meanwhile I disabled the SIM manager to get rid of the constant crash notifications. I'll try and report back any issues I encounter (But if there are too many of them, I'll have to revert back to Dirty Unicorns, although that rom development seems to have stalled pretty much).
Click to expand...
Click to collapse
Just go into app settings and kill now & disable. I noticed that if you installl gapps, get rooted, setup the phone you prefer. Backup with google backup....use the lineage recovery to do a factory reinstall. Once you recover all the sim issues, installation issues simply stop.
nylar357 said:
So the one problem 'I've been having is with custom kernels. I've tried Elemental X & Gats Gulch. With both I lose wifi capability. Once I restore my lineage kernel viola problem solved. Now I've used both these kernels in the past on different builds so I know it isn't the kernel itself rather something related to the lineage build itself & the act of installing a custom kernel. Both kernels returned exactly the same type of error. WIFI attempts to turn on but returns to the off Position. If one attempts to activate the Wifi Icon dropdown during the System UI Crashes. Any input would be great. Other than this little hiccup
Lineage is running absolutely great. Best battery life of any custom OS by far. Sargo stays snappy, my kernel tweaks remain in place. Root maintains over system restores. Love it.
EDIT: ## By the way using Elemental X Kernel Manager App to flash ##
Click to expand...
Click to collapse
The kernel issues might be because they're targeted toward Android 11, and LOS 17.1 is based on Android 10.
harryharryharry said:
[...] First thing I noticed is SIM manager keeps crashing every minute or so (I'm in the Netherlands on the Ben/T-mobile network). [...]
Meanwhile I disabled the SIM manager to get rid of the constant crash notifications.[...]
Click to expand...
Click to collapse
It happened to me the same way. I am in the German T-Mobile network. I also disabled 'SIM Manager'.
Unfortunately, I do not receive any 'missed call'-SMS in case the mobile phone was in flight mode.
I think the app could have something to do with it because everything fits on the ISP side. So far, I haven't found an option to reactivate the App in the settings. Apparently it's some kind of hidden app. Can someone help please?
EDIT: There is a "hidden" "System-apps" option in the app settings. Unfortunately the error still occurs.