Develop Bugs

[Q&A] Hyperdrive Rom Note 10.1 2014 ║ Non-Development Discussion ║ Support

[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?

[Q] CyanogenMod not getiing installed. SuperSU Crashing.

Hello All,
I am a beginner to all this stuff. I wanted to root my phone after seeing OnePlus One running on CyanogenMod. So, first I tried to directly install the Mod using the softwares downloaded from Cyanogen's website. But the software gave the error "Unsupported Firmware". Then I researched a bit on manually installing the mod. I followed the instructions.
- First I rooted my phone with Odin 3.09v
- Installed ROM Manger on my phone (Meanwhile the SuperSU app kept on crashing)
- Somehow I managed to install ClockworkMod (What I did was downloaded SuperSU apk, installed it again. It started working and then, not losing the chance I installed ClockworkMod).
- Then I tried to install CyanogenMod through ROM Manager
- My phone re-booted and then gave a error "Can't install package on incompatible data".
- I'm having the latest snapshot version on CyanogenMod.
- Then I left the things as it is. No rooting, unrooting, etc.
- So, now I tried to take backup of my current ROM, in case something happens at least I'll be having something with me to recover
- I used ROM Manager to take backup. But it gave the error "Can't create the image"
So, now I'm stuck between middle of nowhere. Please help me out to reach to some point.

svikramajit said:
Hello All,
I am a beginner to all this stuff. I wanted to root my phone after seeing OnePlus One running on CyanogenMod. So, first I tried to directly install the Mod using the softwares downloaded from Cyanogen's website. But the software gave the error "Unsupported Firmware". Then I researched a bit on manually installing the mod. I followed the instructions.
- First I rooted my phone with Odin 3.09v
- Installed ROM Manger on my phone (Meanwhile the SuperSU app kept on crashing)
- Somehow I managed to install ClockworkMod (What I did was downloaded SuperSU apk, installed it again. It started working and then, not losing the chance I installed ClockworkMod).
- Then I tried to install CyanogenMod through ROM Manager
- My phone re-booted and then gave a error "Can't install package on incompatible data".
- I'm having the latest snapshot version on CyanogenMod.
- Then I left the things as it is. No rooting, unrooting, etc.
- So, now I tried to take backup of my current ROM, in case something happens at least I'll be having something with me to recover
- I used ROM Manager to take backup. But it gave the error "Can't create the image"
So, now I'm stuck between middle of nowhere. Please help me out to reach to some point.
Click to expand...
Click to collapse
Ok, first I think your SuperSu is not working properly. Open the Supersu app to see if it needs to update binaries. If it continues to crash, go into recovery manually (not using rom manager) and flash the latest SuperSu. Wipe Cache, go to advanced and Wipe Dalvik. Reboot. Your phone will say "android is upgrading" for a bit. Once it's booted up, go back into the supersu app and see if it needs to update binaries, if so- let it update, if not- move on. Here's a link to download SuperSu 2.02
Go back into recovery manually and select backup and restore-> backup to sdcard (or sdcard1, external sd, is my preference) This will start the backup process.
Once that is done, you need to find the CyanogenMod file specific to your phone, then you can enter recovery and flash it.
If you have trouble entering recovery, you can flash a new one via recovery or with odin.

Hello absinthesummer,
I followed every instruction you told. Now I'm done till creating backup. The problem now I'm facing is this 'Status 7' error. It says "Can't install package on incompatible data.....". Now what to do?

Status 7 is a very specific error. It means your recovery is out of date. Get the absolute newest you can find and try again. This is good news though, you've got progress!
---------- Post added at 11:48 AM ---------- Previous post was at 11:46 AM ----------
Edit: flash the latest recovery you can find via Odin. You probably won't be able to do it in recovery while you're getting the status 7 error.

absinthesummer said:
Status 7 is a very specific error. It means your recovery is out of date. Get the absolute newest you can find and try again. This is good news though, you've got progress!
---------- Post added at 11:48 AM ---------- Previous post was at 11:46 AM ----------
Edit: flash the latest recovery you can find via Odin. You probably won't be able to do it in recovery while you're getting the status 7 error.
Click to expand...
Click to collapse
No, I've got the latest recovery. But I figured out the problem. It was with the package I downloaded. The CM 11 M9 version was giving errors. I researched and tried few fixes, but still it didn't work.
The fixes I tried :-
1. Deleting some coding lines from the updater-script file. But this fix gave the status 6 error.
2. Changing the updater-script file format to UNIX format. Then again it gave the status 7 error.
So, what I did, when I had no more brain to fix it, I downloaded the CM 11 M6 version and tried installing it. And VOILA! It worked. Then I updated it to M9 version through phone. Now it's working. Though it has some bugs. And some features are missing too that I wanted badly.

svikramajit said:
No, I've got the latest recovery. But I figured out the problem. It was with the package I downloaded. The CM 11 M9 version was giving errors. I researched and tried few fixes, but still it didn't work.
The fixes I tried :-
1. Deleting some coding lines from the updater-script file. But this fix gave the status 6 error.
2. Changing the updater-script file format to UNIX format. Then again it gave the status 7 error.
So, what I did, when I had no more brain to fix it, I downloaded the CM 11 M6 version and tried installing it. And VOILA! It worked. Then I updated it to M9 version through phone. Now it's working. Though it has some bugs. And some features are missing too that I wanted badly.
Click to expand...
Click to collapse
Awesome! I'm glad you got it working. You can also try comparing the two files to see what's different, or maybe swap the updater script. Maybe you'll be able to get the one you wanted working with a little modification

absinthesummer said:
Awesome! I'm glad you got it working. You can also try comparing the two files to see what's different, or maybe swap the updater script. Maybe you'll be able to get the one you wanted working with a little modification
Click to expand...
Click to collapse
Thanks to you. You too helped me in working it out!
But, I have some more questions
Question 1 : If I flash stock ROM on my rooted phone, will I receive the new updates? If yes, will I be able to install them via Kies on my phone without getting into any trouble?
Question 2 : If I install stock ROM of any other phone, say Galaxy S5, will it work on my phone properly without any problems? If yes, will I receive the updates for that too and able to install them via Kies? If no, is there any way to install it? Cause I have seen people using S5 ROM on Note 2.

First question the answer is yes. As long as you have the stock recovery and stock kernel (along with the stock rom) you will receive ota updates. You can use ota root keeper (an app) to keep root during an ota update. There are many people who choose to stay fully stock but root to get rid of bloatware & stuff. However, if you want to get ota, I recommend freezing the bloatware instead of uninstalling, because an ota usually replaces old bloatware with new bloatware and can sometimes abort the ota if those apps are missing... but keep on mind this is not always the case, only certain devices.
Second question, no you cannot. Roms from other devices have to be ported to be compatible. But if you look in the development forums, you can find many roms that are basically stock but have specific features from other roms, along with the system ui (ie S5, note 3, & so forth). These rom devs have ported either parts/features or full on roms to be compatible on our device. They are excellent! I recommend reading up them and if you see some you like, try them out!

absinthesummer said:
First question the answer is yes. As long as you have the stock recovery and stock kernel (along with the stock rom) you will receive ota updates. You can use ota root keeper (an app) to keep root during an ota update. There are many people who choose to stay fully stock but root to get rid of bloatware & stuff. However, if you want to get ota, I recommend freezing the bloatware instead of uninstalling, because an ota usually replaces old bloatware with new bloatware and can sometimes abort the ota if those apps are missing... but keep on mind this is not always the case, only certain devices.
Second question, no you cannot. Roms from other devices have to be ported to be compatible. But if you look in the development forums, you can find many roms that are basically stock but have specific features from other roms, along with the system ui (ie S5, note 3, & so forth). These rom devs have ported either parts/features or full on roms to be compatible on our device. They are excellent! I recommend reading up them and if you see some you like, try them out!
Click to expand...
Click to collapse
- Stock Recovery
- Stock Kernel
- OTA Root Keeper
- Bloatware
Well, to be honest, just right now I learned these new terms but know nothing about them. Can you please give me a brief description for these four terms so that when I do advanced search on them, I'd have a idea in my mind about what these are. It will make it easy for me to understand the advance things.
And I'm looking for S5 ROM for my phone. Let's see what I get.

One more question. I made a backup of my rooted stock ROM via latest ClockwordMod, manually. Now, if I reset the binary counter using Triangle Away and then wipe Cache and Dalvik and then flash my stock ROM which is located on my memory card and then after flashing I use SuperSU to unroot and then a factory reset (I don't know the method of factory reseting cause I'm confused. Whether to do it manually, like going into recovery mode or just from the phone settings. So please tell me this also.), will my phone be unrooted totally?
And sorry for bugging you so much. I hate to do that, but I don't want to take risk with my phone. So I am just collecting information. I hope so many queries are not a problem for you.

Ok...
You already know what a rom is. A kernel is a lower-level base. It controls the hardware. So when you do something on the interface, in the rom, it tells the hardware how to react. (Ie if you're playing music it tells which speakers to play and how loudly). The kernel controls almost everything you can't see, it relates to performance. Most stock kernels can be limiting as they underclock the cpu by a certain percentage. Because of this, people seek out custom kernels to max out their device's potential. Louder speakers, faster cpu, better graphics, etc. This is all stuff the kernel can optimize... but because you can change so many factors there is a risk of instability if you push your device too hard (max performance) or limit it too much (max battery saving).
Recovery is exactly what it sounds like. When you boot your device the very first screen that pops up is the bootloader. It's giving you time to boot in 3 different modes. The first mode, by doing nothing, is a normal boot into the rom/OS. The second mode, which you get to by one button combination, takes you to recovery. The stock recovery is very limited. It gives you the option to factory restore, wipe cache, update, or boot normally. Stock recovery only exists for emergencies, if your phone fails to boot normally. We have custom recoveries so we can do more stuff, flash custom roms and tinker with things. The third mode is download mode/Odin mode. This is the bootloader interface itself. It's the last resort for recovery if your recovery has been damaged or corrupted. It allows you to connect to Odin or kies and perform an emergency recovery of the device. If you damage your bootloader, your device is completely bricked.
So the order of operation is this:
Lowest level- bootloader
Second level- recovery
Third level- kernel
Fourth level- rom
Bloatware is all the pre-installed apps that your carrier adds to your phone. Most people don't use it, don't like it, and don't want it. That why we root. Without root we basically are just guest users of the device. With root we become the administrators of the device. Until you root, your carrier has admin rights over your phone (to use windows terms).
When you receive an ota update, your carrier can make it to where the update won't proceed if their pre-installed apps have been removed (although this isn't always the case). Additionally, the update package itself checks the integrity of the device. It checks recovery, kernel, and rom. If any have been altered, it will not proceed because it could cause conflict and potentially brick your device. That's why those things have to be stock.
Ota root keeper is simply an app that backs up your superuser rights before an update and restores them after its done.
You should be able to find plenty of roms with S5 features. I'm using one that makes my device fully like an S5 (my device even thinks it is an S5 and every app identifies it as such) I can think of at least 2 others as well. There's plenty to choose from, and if you see a rom you like but it's mudding a particular feature, you can probably find that feature as a stand-alone installation in the forum's themes & apps section. Just about every feature of S5, S4, and note 3 has been ported to this device, so look around!
Also, for future reference, if someone helps you on the forum, hit the thanks button instead of saying it. I don't mind either way, but some people get annoyed and will stop helping them if they don't hit that button lol. It's silly, but it's part of "forum decorum"
---------- Post added at 12:54 AM ---------- Previous post was at 12:44 AM ----------
svikramajit said:
One more question. I made a backup of my rooted stock ROM via latest ClockwordMod, manually. Now, if I reset the binary counter using Triangle Away and then wipe Cache and Dalvik and then flash my stock ROM which is located on my memory card and then after flashing I use SuperSU to unroot and then a factory reset (I don't know the method of factory reseting cause I'm confused. Whether to do it manually, like going into recovery mode or just from the phone settings. So please tell me this also.), will my phone be unrooted totally?
And sorry for bugging you so much. I hate to do that, but I don't want to take risk with my phone. So I am just collecting information. I hope so many queries are not a problem for you.
Click to expand...
Click to collapse
You're fine, I don't mind answering your questions. Yes, you can unroot fully in the way you just mentioned but you don't even have to go through all the trouble of factory reset. Just unroot in the app. The app can be uninstalled afterwards via the play store.
You can factory reset either way, the same commands are given no matter which way you go about it. But it can be more efficient to do it from recovery because when you do it from the rom it has to create a wipe script for when it reboots, and it has to shut down the rom first. If you do it from recovery it doesn't have to anything, the rom isn't running and it can execute the wipe command immediately. (The wipe command is wipe /data /cache etc)

Thanks again for all that great info!
Questions : Is there no way to fix the Bootloader if it gets damaged by chance? And which S5 ROM are you using?

svikramajit said:
Thanks again for all that great info!
Questions : Is there no way to fix the Bootloader if it gets damaged by chance? And which S5 ROM are you using?
Click to expand...
Click to collapse
If you damage the bootloader it's a hard brick and you would have to send it in for jtag services (this is a low level emmc chip flash service) The bootloader won't get damaged unless you do something to corrupt it. If you ever feel the need to flash a new bootloader, do it via Odin, never recovery! If you remember that you should be fine.

svikramajit said:
Thanks again for all that great info!
Questions : Is there no way to fix the Bootloader if it gets damaged by chance? And which S5 ROM are you using?
Click to expand...
Click to collapse
I meant to tell you I'm using DN3 rom. It has an aroma installer that lets you choose whether you want an S5 ui, a note 3 ui or a mixed ui. Choosing S5 ui & S5 build prop allows your device to work with S5 apps & it looks just like an S5. It's not the only rom out there, but it's beautiful, fast, and stable & the team works hard on it.

absinthesummer said:
I meant to tell you I'm using DN3 rom. It has an aroma installer that lets you choose whether you want an S5 ui, a note 3 ui or a mixed ui. Choosing S5 ui & S5 build prop allows your device to work with S5 apps & it looks just like an S5. It's not the only rom out there, but it's beautiful, fast, and stable & the team works hard on it.
Click to expand...
Click to collapse
Hey absinthesummer!
I tried to unroot my phone with the method I told you. But in the restore option, I am stuck at 'Checking MD5 Sums..'. What to do now?

MD5 checking takes forever! You have to wait it out. Most recoveries offer a way to turn it off. You shouldn't have to factory reset though, just click unroot in the super su app and then uninstall the app from the play store.

absinthesummer said:
MD5 checking takes forever! You have to wait it out. Most recoveries offer a way to turn it off. You shouldn't have to factory reset though, just click unroot in the super su app and then uninstall the app from the play store.
Click to expand...
Click to collapse
I waited and the system was restored. But I got an error on 'Restoring Data'. I rebooted the phone and now it's showing glowing Samsung logo from like 3-4 minutes.

I've seen that before. Can you get back into recovery? You may have to flash stock in Odin, flash recovery and then do the Restore again. Data got messed up.

absinthesummer said:
I've seen that before. Can you get back into recovery? You may have to flash stock in Odin, flash recovery and then do the Restore again. Data got messed up.
Click to expand...
Click to collapse
I'll try removing the battery now. Let's see what happens.

Ok if you can get into recovery, do a fresh flash and then try to restore again. And see if it offers a way to turn off MD5 checking. That's why I use philz or twrp, they offer that and move much faster through MD5 check by default.
---------- Post added at 11:13 AM ---------- Previous post was at 11:12 AM ----------
If you still fail on data, flash stock in Odin, flash custom recovery, then you should be able to enter recovery and have a successful restore.

LG G3 - Unremovable Bloatware?

Short history of what I've done/where I'm at now:
The History
Wanted to upgrade rooted D855 from 4.4.2KK to 5.X Lollipop
De-rooted using SuperSU. Rebooted, and went to update center to apply update. Message saying "Phone has been noted to be rooting. Software update not available for rooted phones." or something thereabouts.
Decide to factory reset phone. Does nothing.
Follow this guide (Link) to completely wipe and start fresh. All goes well.
Bunch of bloatware comes pre-installed. What the hell?
Decide to combat this by following this guide (The KDZ way) (Link) and this Image (3 UK variant) to attempt to get back to my original version.
Used this one-click root (Link) to re-root my Android 5.0 variant (question on this later)
Goes well pretty much; everything seems about right. However, here are the problems.
The Problems
I have rooted and have Titanium Backup Pro; tried using this to remove the bloatware. Doesn't do anything, and if I try to do them individually I get the message "cannot remove System app. Failed to locate the APK file." This is my #1 problem. I have a bunch of European apps that I can't pronounce, plus rubbish like 'Orange Antivirus'. Even things like Deezer is now pre-installed system crap, listed under the Software center portion of the LG Updates area on the phone.
My 3 splash screen no longer comes up, which is fine, makes the booting either faster or just seem smoother. However, it makes me wonder whether I'm on the right version of Android now; will I miss updates to future version of Android from hereon out?
Is Android 5.0 the latest update for the EU D855? I heard 5.0 was having problems on the G3, hence why I've updated so late. However, if I'm now stuck on the version WITH the problems, that's not good.

Bump; anyone? This is driving me nuts!

Hi,
1. To uninstall the antivirus you need to remove it from the phone administrators.
2. There should be at least the LG boot animation.
3. Yes. The latest update is still 5.0.
I suggest that you move to a custom Rom based on stock like cloudy 2.5.
Much better Rom and free of bloatware.
Regards
Sent from my phone

ypsmav said:
Hi,
1. To uninstall the antivirus you need to remove it from the phone administrators.
2. There should be at least the LG boot animation.
3. Yes. The latest update is still 5.0.
I suggest that you move to a custom Rom based on stock like cloudy 2.5.
Much better Rom and free of bloatware.
Regards
Sent from my phone
Click to expand...
Click to collapse
I gave up on waiting (the bloatware was driving me crazy, not usually so impatient), and just installed TWRP, wiped it and reinstalled a fully stock ROM, so all sorted now. Any benefit to using Cloudy 2.5 over complete stock? Any performance/battery benefits?
Thanks for your response though

BRPW said:
I gave up on waiting (the bloatware was driving me crazy, not usually so impatient), and just installed TWRP, wiped it and reinstalled a fully stock ROM, so all sorted now. Any benefit to using Cloudy 2.5 over complete stock? Any performance/battery benefits?
Thanks for your response though
Click to expand...
Click to collapse
Felt faster for me plus a load of newer updated app versions for stock apps and a lot more customization options :good:

Will_Xda said:
Felt faster for me plus a load of newer updated app versions for stock apps and a lot more customization options :good:
Click to expand...
Click to collapse
Maybe I'll look into it then On another note, you're from Leicester? Where abouts you from?

Zenfone 2 ZE551ML - Updating System after rooting with TWRP and Unlocked Bootloader?

I got the new phone 15 days ago, thinking it'll be as amazing as Zenfone Max ZC550KL (Great Camera, everlasting battery) but it had super annoying issues, specially the battery draining too fast. Even during deep sleep (screen off for hours) the battery drained from 100% to 70% in like an hour or so, without any SIM/WiFi/Hotspot.
I had to fix this as it was impossible to go outside for a day and not have it switch off on my face when I needed it. None of the power saving settings helped.
So, I unlocked the bootloader following a youtube guide (it was a batch file on windows, not the original app which I found out about 10 mins ago), and flashed TWRP into it. Took a full system backup of all partitions and rooted it by flashing the latest SuperSU Binary. Worked like a charm. Installed CPU Tuner, deleted all triggers and set frequency to manually locked 500 MHz. When I need to play a game or do something which needs performance, I'd just go and manually pull the slider ahead to 2.3 GHz.
The avg. battery drain during deep sleep or screen off for hours, reduced from 1120 mAh to 10 mAh which is HUGE (found out with an app I cant remember). I'm happy with it as now it can last about a day and about 3 days if I'm mostly not using it, with WiFi on all the time. Its just slightly not as butter smooth with the UI as before.
Now, the camera quality is the worst I've ever seen. During dark, the PixelMaster Camera makes things crippling dark and too much purple pixelated noise and grain, pics taken from it look like from my Galaxy Tab 2 which I bought in 2012, and I tried different camera apps and everything I could, no luck. Where, the image taken from almost the same place at the same time, both phones held side by side, my old phone ZC550KL takes a million times clearer picture, brighter, perfectly visible and great looking. I also tried setting the same enhancements and stuff but nothing helped.
Some posts on googling it, suggest to update the system firmwire to improve camera quality but it requires the original recovery mode to be there, where I have TWRP.
I want to update the system as I have nothing to lose, already have 4-5 complete TWRP backups of every state (Original before rooting, rooted once, some modifications later, etc). Just if the phone gets bricked or doesn't boot anymore, that would be the problem.
I've messed around with almost everything I could on my Windows 7 and Windows 10 Desktop over past 6 years, so I have an idea about how things work.
Now, how do I update the system?
I think I could flash an update manually downloaded on my PC using adb and fastboot drivers... If so, how?
Current Software Information:
Current Android Version: Lollipop v5.0
Build Number:
LRX21V.WW-ASUS_Z00A-2.20.40.184_20160504_4658_user_044030427
Available System Update from the inbuilt app:
Last Check: 09/14/2017 12:00 PM (today)
Build Number: WW_2.20.40.198_20160930_8756_user_rel (93.31 MB)

CaptianXLAB said:
I got the new phone 15 days ago, thinking it'll be as amazing as Zenfone Max ZC550KL (Great Camera, everlasting battery) but it had super annoying issues, specially the battery draining too fast. Even during deep sleep (screen off for hours) the battery drained from 100% to 70% in like an hour or so, without any SIM/WiFi/Hotspot.
I had to fix this as it was impossible to go outside for a day and not have it switch off on my face when I needed it. None of the power saving settings helped.
So, I unlocked the bootloader following a youtube guide (it was a batch file on windows, not the original app which I found out about 10 mins ago), and flashed TWRP into it. Took a full system backup of all partitions and rooted it by flashing the latest SuperSU Binary. Worked like a charm. Installed CPU Tuner, deleted all triggers and set frequency to manually locked 500 MHz. When I need to play a game or do something which needs performance, I'd just go and manually pull the slider ahead to 2.3 GHz.
The avg. battery drain during deep sleep or screen off for hours, reduced from 1120 mAh to 10 mAh which is HUGE (found out with an app I cant remember). I'm happy with it as now it can last about a day and about 3 days if I'm mostly not using it, with WiFi on all the time. Its just slightly not as butter smooth with the UI as before.
Now, the camera quality is the worst I've ever seen. During dark, the PixelMaster Camera makes things crippling dark and too much purple pixelated noise and grain, pics taken from it look like from my Galaxy Tab 2 which I bought in 2012, and I tried different camera apps and everything I could, no luck. Where, the image taken from almost the same place at the same time, both phones held side by side, my old phone ZC550KL takes a million times clearer picture, brighter, perfectly visible and great looking. I also tried setting the same enhancements and stuff but nothing helped.
Some posts on googling it, suggest to update the system firmwire to improve camera quality but it requires the original recovery mode to be there, where I have TWRP.
I want to update the system as I have nothing to lose, already have 4-5 complete TWRP backups of every state (Original before rooting, rooted once, some modifications later, etc). Just if the phone gets bricked or doesn't boot anymore, that would be the problem.
I've messed around with almost everything I could on my Windows 7 and Windows 10 Desktop over past 6 years, so I have an idea about how things work.
Now, how do I update the system?
I think I could flash an update manually downloaded on my PC using adb and fastboot drivers... If so, how?
Current Software Information:
Current Android Version: Lollipop v5.0
Build Number:
LRX21V.WW-ASUS_Z00A-2.20.40.184_20160504_4658_user_044030427
Available System Update from the inbuilt app:
Last Check: 09/14/2017 12:00 PM (today)
Build Number: WW_2.20.40.198_20160930_8756_user_rel (93.31 MB)
Click to expand...
Click to collapse
very first of all you must update to MM latest MM it has improved battery life and there are also security related issues fixed. the very best thing to do is.. go to the following link. see the section flash firmware without AFT. (you do not need to change recovery or boot image or any thing just follow the instruction)
reboot your phone in fastboot mode and run each and every command step by stem. even if some of them fails.. not reboot, after first boot go to recovery mode and factory reset. start again and then again sideload latest MM from asus website
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785

Not so sure I wana upgrade to MM though. Feels like something will definitely go bad during that.
On ASUS support site, in the firmwire tab, I found a LOT of options to download. It'll take time to find the correct version.
Say I found the correct version (or ROM) and downloaded it. (about 1.2 GB), what are the steps to flash it on my phone? Can it be done using TWRP?

Worth upgrading to Marshmallow IMHO
No freezing, less ram usage, better battery usage especially with a new battery, more compatibility to newer apps, Permissions control (love it)
If you say that you are handy on PC then great, cos you may need to be
ASUS ZenFone2 (ZE551ML) software Image: V4.21.40.352 for WW SKU only*(andriod M)
Thats the current version of MM
Download and place onto SD card, unplug cord and system should recognise.
Plenty of info on the web about upgrading however you need to unroot and renable all disabled.
More then likely will brick phone but piss easy once you have done many times lolol
Check out the Unbrick threads
https://forum.xda-developers.com/zenfone2/general/guide-fix-bricked-ze550ml-ze551ml-usb-t3405840
https://forum.xda-developers.com/zenfone2/general/guide-recover-fastboot-bricked-zenfone-t3284337
And what i initially used
http://www.techyoutubers.com/2017/04/fixed-how-to-fix-zenfone-2-hard-brick.html
https://www.youtube.com/watch?v=fsAse5F5xtM

CaptianXLAB said:
Not so sure I wana upgrade to MM though. Feels like something will definitely go bad during that.
On ASUS support site, in the firmwire tab, I found a LOT of options to download. It'll take time to find the correct version.
Say I found the correct version (or ROM) and downloaded it. (about 1.2 GB), what are the steps to flash it on my phone? Can it be done using TWRP?
Click to expand...
Click to collapse
as i suggested it is foolproof method to update to MM. i am 100 percent sure you will not brick if you follow what i suggested. don't see multiple threads. multiple instructions. do as i told earlier

Sorry to be away for such a long time... I'm back. xD
As soon as my exams are over, to do this upgrade.
I'll do it like this:
1. Copy the update zip file to MicroSD. [Filename: UL-Z00A-WW-4.21.40.352-user.zip]
2. Full system image backup using TWRP - All Partitions to MicroSD, then transfer to my PC (Just because I want to xD )
3. Clean format all partitions on my phone (I've had enough "errors after updating" issues on PC, so)
4. Select the update zip file from TWRP, flash it.
5. HOPEFULLY there won't be any errors (If there will, I'll simply restore everything from the backup I just made on step 2. Nothing lost!)
6. Reboot and pray for it to work xD
[if it still works and boots just fine]
7. Remove SIMs, MicroSD, etc., Factory Reset (again. Just cos I want to xD )
[Hope for it to still work on rebooting]
8. Check if everything's working (all apps, calling, playstore, etc. just to make sure)
9. Install everything, sync up, make it my phone again
10. Reboot, boot into Recovery (to see if TWRP is still there?)
11. if TWRP isn't there, Boot into Fastboot, flash a stable TWRP recovery to replace the default one using my PC.
12. Create a MM (before-root) backup of all partitions. (Actually, I'll create THREE backups, can't risk any failures xD )
13. Download the latest SuperSU, Flash it. Download a supported Viper4AndroidFX v5 apk or flashable zip, install/flash that too.
14. Set up root apps (CPU Tuner, Titanium Backup, BusyBox, etc) and first thing to see if Viper4Android works.
[Cos if my phone aint havin' v4a, everything above is useless for me because I can't live without that perfected sound and I'll just revert! xD ]
That seems to be about it. Will all this work? Any suggestions?
Some questions I still have -
There's also a recovery.img file in that zip. Will it overwrite TWRP?
Will the bootloader be locked again after this update? (unlocking it was a long search for android LP)
And the main reason not-that-tech-related I'm wanting an upgrade now (Substratum!):
Spoiler
Will Substratum Theme Engine work with MM? (I just want EVERYTHING BLACK - to rest my eyes. I'll buy themes too)
How well can substratum skin my phone? (I want literally everything dark themed, as much as possible)
Will backgrounds of apps like messenger/facebook be dark themed?

Rooted T-800 (wifi model), looking to update to Android Nougat or Later

So I had rooted my Tab S back in 2016 or so (if you check the forums here you'll see my posts for this...). Have had that working for a while now. It tripped the Knox (I didn't personally care about this) except now I want to install a couple streaming apps on the tablet and the OS is too old to handle it
I had loaded TWRP onto the Tab S and rooted it with Lollipop stock ROM and loaded it with SuperSU. It has worked like a charm up till now, issues with Link2SD notwithstanding (I have ZERO intentions of going back to that app).
My question is: what do I need to do to install the newest possible version of Android that the tablet can take? I know it's an older tablet now but I still use it for reading and other stuff, and I'd like to keep it alive a bit longer by installing a new Android OS and ROM on it.
(aside: I did remove a bunch of stuff once I rooted it, so I am not sure how much this may interfere with any attempt to update it to a newer version of Android)
(aside #2: I never updated SuperSU through the app store as I was afraid it would break the root process, so I left that app alone and eventually it stopped showing up in my update list on google play. I'd have to check the tablet to see what version of it I have installed at present)

Funny, I just updated my Tab S this weekend. Same as you, was running into apps that no longer support older OS. I updated mine to Lineage 14.1 version. So far working fine. I know there is a newer version but after reading the threads, this version seemed to be reported as working better. Just follow the instructions in the thread to upgrade.

cbb77 said:
Funny, I just updated my Tab S this weekend. Same as you, was running into apps that no longer support older OS. I updated mine to Lineage 14.1 version. So far working fine. I know there is a newer version but after reading the threads, this version seemed to be reported as working better. Just follow the instructions in the thread to upgrade.
Click to expand...
Click to collapse
Hey thanks for your reply!
Do you need to update the android version to get Lineage OS installed?

No you do not. You just have to update the bootloader. Instructions are in the thread on how to as well as to have to confirm.

Hi again,
Sorry could you point me in the direction of said thread?

cbb77 said:
No you do not. You just have to update the bootloader. Instructions are in the thread on how to as well as to have to confirm.
Click to expand...
Click to collapse
Wait I think I found it. Was this it?
https://forum.xda-developers.com/galaxy-tab-s/development/rom-lineageos-14-1-sm-t800-t3545080

bsquared938 said:
Wait I think I found it. Was this it?
https://forum.xda-developers.com/galaxy-tab-s/development/rom-lineageos-14-1-sm-t800-t3545080
Click to expand...
Click to collapse
Yes, that is the correct thread.

cbb77 said:
Yes, that is the correct thread.
Click to expand...
Click to collapse
Perfect. Will also update this table to give it a further lease on life .
Thanks man!

cbb77 said:
Yes, that is the correct thread.
Click to expand...
Click to collapse
@cbb77
Cannot find the Lineage OS ROM image, I think it may have been removed from their site given the age.
Do you have a working download link for this?
Edit: please ignore post, I found it as soon as I posted this -.-

T800 https://download.exynos5420.com/LineageOS-14.1-Deathly/chagallwifi/
Pretty bood performance and battery,also GPU OC.Load this with Gapps.

Trung Gs said:
T800 https://download.exynos5420.com/LineageOS-14.1-Deathly/chagallwifi/
Pretty bood performance and battery,also GPU OC.Load this with Gapps.
Click to expand...
Click to collapse
I assume I have to load the marshmallow bootloader before I do anything?

bsquared938 said:
I assume I have to load the marshmallow bootloader before I do anything?
Click to expand...
Click to collapse
Personally I like the Resurrection Remix rom. https://forum.xda-developers.com/ga...om-resurrection-remix-n-sm-t800-wifi-t3606243
Just do the standard stuff. You've got TWRP installed, so you're most of the way there. Back up whatever you want to back up, and then:
1. Wipe System, Data, Cache, and Dalvik Cache.
2. Install OS.
3. Install Magisk (if you want to use Magisk for your rooting needs. It seems to be the popular root tool now. It's pretty boss.)
4. Reboot into system, then back into recovery, and:
5. Install GApps or whatever. I like NanoDroid myself. It's the alternative to GAPPS. There are a few odd programs that just plain won't work with it yet, but the official Google apps have an annoying habit of wasting processing power on pointless background nonsense, so I prefer the alternative. Also there's an Xposed module that improves compatibility. https://nanolx.org/nanolx/nanodroid

Hmm I'll take a look at this other ROM
Currently, I have a rooted stock ROM (SuperSU ad root manager), and interested in moving to a custom ROM that is well supported
My only 2 concerns before starting are:
1) Do I need to update SuperSu
2) Do I need to update the bootloader before doing anything else (even the ROM that you suggested @FailSafeNow ? )

Anyone who was wondering what happened:
Process I used (done 2 days ago as of this post):
0) transferred all relevant files to device for the operation, backed up stuff I wanted
1) Updated bootloader to marshmallow via ODIN
2) Updated TWRP to 3.x (forgot exact version) from within TWRP
3) Wiped system + data + cache (I could have probably wiped internal memory but there wasn't much there anyways)
4) Installed Lineage OS 14.1 and Nano Gapps from within TWRP (in that order)
( full disclosure: I had wrong Gapps .zip file the first time and had to get the right one afterwards)
While I had the superSU package, I decided not to root the tablet again. I don't think I need the customization that root offers this time around especially since Lineage OS is already so lightweight compared to the stock ROM I just replaced...
Thanks all for your help!!
Over and out
Thanks all! Nice super fast tablet with amazing battery life now

bsquared938 said:
Anyone who was wondering what happened:
Process I used (done 2 days ago as of this post):
0) transferred all relevant files to device for the operation, backed up stuff I wanted
1) Updated bootloader to marshmallow via ODIN
2) Updated TWRP to 3.x (forgot exact version) from within TWRP
3) Wiped system + data + cache (I could have probably wiped internal memory but there wasn't much there anyways)
4) Installed Lineage OS 14.1 and Nano Gapps from within TWRP (in that order)
( full disclosure: I had wrong Gapps .zip file the first time and had to get the right one afterwards)
While I had the superSU package, I decided not to root the tablet again. I don't think I need the customization that root offers this time around especially since Lineage OS is already so lightweight compared to the stock ROM I just replaced...
Thanks all for your help!!
Over and out
Thanks all! Nice super fast tablet with amazing battery life now
Click to expand...
Click to collapse
I know this is a somewhat old thread. I have a T800 myself and am looking for a ROM. Want to try Lineage OS 14.1 like you have tried. Was curious as to whether you still have it and if you still liked it? If so, what version are you running now and how is your battery life compared to stock? Thanks so much! :good: