You're busy and don't have time to wait, which is why you need to stop reading this thread and get back to organizing your Pogs. Rate this thread to express how the OnePlus 3 performs when multitasking. A higher rating indicates that the OnePlus 3 keeps many apps in memory so that they don't need to reload, and that when moving between apps, transitions are smooth and performance is excellent.
Then, drop a comment if you have anything to add!
Incredible after applaying the memory fix by settig the app limit to 42
Julius1993 said:
Incredible after applaying the memory fix by settig the app limit to 42
Click to expand...
Click to collapse
Any idea on how this affects battery life?
airchicken said:
Any idea on how this affects battery life?
Click to expand...
Click to collapse
So I also switched my background processes to 42, and I ended up dialing it back to 32, because I do think it affects battery life a bit. To be honest, at 42, I was using 5GB of RAM at a time, which was amazing (SO MANY apps in RAM), but honestly, while it's fun, it's not really helpful in day to day use. But the default setting of 20 is too low.
airchicken said:
Any idea on how this affects battery life?
Click to expand...
Click to collapse
Batterylife might be effected, but its perfectly fine for me. Im getting around 4h of SOT with brightness at 100% (adaptive) Wifi and Bluetooth turned on, connectet to my huawei watch and using it quite a lot. And there was literally no app cleared from ram. I will test it again with the value set to 36 though!
Its such a great experience to have a phone which doesn't have to start up an App twice.
Sounds great... but for me stock settings only end up getting about 2h of SOT wich seems to be not that much... Seems like Android System drains a lot...
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
By default limit is low but i think for day to day usage it is fine
I able to use only 3 to 4 apps daily for multi tasking and it is fine and giving me good battery experience.
Sent from my ONEPLUS A3003 using Tapatalk
Julius1993 said:
Incredible after applaying the memory fix by settig the app limit to 42
Click to expand...
Click to collapse
By stating a memory fix you are referring to rooting the phone prior to adjusting the value, correct?
Can someone post on how to do this without root - please give the adb commands. I know that a quora post was provided to do without root using adb etc but was not able to do this..
I was able to do the screen display density to 400 without root using adb commands (density) but was not able to do this. I will be very thankful if someone can do this.
airchicken said:
Any idea on how this affects battery life?
Click to expand...
Click to collapse
harharryhar said:
Can someone post on how to do this without root - please give the adb commands. I know that a quora post was provided to do without root using adb etc but was not able to do this..
I was able to do the screen display density to 400 without root using adb commands (density) but was not able to do this. I will be very thankful if someone can do this.
Click to expand...
Click to collapse
Go on Youtube and search vor "OnePlus 3 - How to Root". The Channel is called C4ETech. The Guy in the video gives you perfect instructions.
In the video description you will also find all the downloads you will need!
---------- Post added at 09:14 AM ---------- Previous post was at 09:10 AM ----------
harharryhar said:
Can someone post on how to do this without root - please give the adb commands. I know that a quora post was provided to do without root using adb etc but was not able to do this..
I was able to do the screen display density to 400 without root using adb commands (density) but was not able to do this. I will be very thankful if someone can do this.
Click to expand...
Click to collapse
You can not do this without root!!! All you can do wihtout root, is to pull the build.prop via adb (adb pull /system/build.prop <your desired location>), but you cannnot push it back to your phone, because you need access to your phones root directory which is read only out of the box.
---------- Post added at 09:20 AM ---------- Previous post was at 09:14 AM ----------
The simplest way to apply the memory fix is the following:
-Go on Youtube. Search for "OnePlus 3 - How to Root". The Channel is called C4ETech. The Guy in the video gives you perfect instructions. Its really easy, you will find all the downloads in the videos description.
-then download the build prop editor app from the play store and look for the right value (ro.sys.fw.gb_apps_limit=20) and change it.
Julius1993 said:
You can not do this without root!!! All you can do wihtout root, is to pull the build.prop via adb (adb pull /system/build.prop <your desired location>), but you cannnot push it back to your phone, because you need access to your phones root directory which is read only out of the box.
Click to expand...
Click to collapse
Thanks for your reply..but in the xda article on how to fix it , it says:
http://www.xda-developers.com/how-t...-management-almost-double-the-apps-in-memory/
"There are many ways to edit the build.prop, including pulling it through ADB without root or using root apps specifically designed for build.prop editing. I personally used Root Explorer this time around, but all methods should work."
The word ADB is linked to a quora page where the methods are mentioned, but I have not been able to get it to work:
https://www.quora.com/How-do-I-edit-the-build-prop-file-in-Android-without-Rooting-it
So there is no way to do without root as the article refers?
Incase of root ( I am worried about security), if there is a way to unroot it (will have to find it), the OTA update might change it back to 20, so do we have to keep the root on?
So will be really thankful if someone can give the exact ADB commands. Thanks for your help.
harharryhar said:
Thanks for your reply..but in the xda article on how to fix it , it says:
http://www.xda-developers.com/how-t...-management-almost-double-the-apps-in-memory/
"There are many ways to edit the build.prop, including pulling it through ADB without root or using root apps specifically designed for build.prop editing. I personally used Root Explorer this time around, but all methods should work."
The word ADB is linked to a quora page where the methods are mentioned, but I have not been able to get it to work:
https://www.quora.com/How-do-I-edit-the-build-prop-file-in-Android-without-Rooting-it
So there is no way to do without root as the article refers?
Incase of root ( I am worried about security), if there is a way to unroot it (will have to find it), the OTA update might change it back to 20, so do we have to keep the root on?
So will be really thankful if someone can give the exact ADB commands. Thanks for your help.
Click to expand...
Click to collapse
You can change the build prop without root, but you cannot push it back on your device. i have tried it without root, but its simply not possible and it doesnt make sense either. if you dont have access to write on your root directory you cannot change anything there.
i really recommend rooting. just by the fact, that you can get rid of all the in app commercials! (really awesome)
Also rooting will not void your warranty on your 1+3. you can alway unroot your device by flashing the stock rom back on your device!
You will find all the ADB commands in the video i was talking about before.
-adb devices
-adb reboot bootloader
-fastboot devices
-fastboot oem unlock (will wipe your device!)
-fastboot flash recovery recovery.img (TWRP Recovery [is needed])
-then reboot the device into recovery manually by using the volume and power button, not by the command fastboot reboot.
-install superuser
-Done
-Edit build.prop with buildprop editor and allow super user access.(easiest way for noobs)
Julius1993 said:
You can change the build prop without root, but you cannot push it back on your device. i have tried it without root, but its simply not possible and it doesnt make sense either. if you dont have access to write on your root directory you cannot change anything there.
i really recommend rooting. just by the fact, that you can get rid of all the in app commercials! (really awesome)
Also rooting will not void your warranty on your 1+3. you can alway unroot your device by flashing the stock rom back on your device!
You will find all the ADB commands in the video i was talking about before.
-adb devices
-adb reboot bootloader
-fastboot devices
-fastboot oem unlock (will wipe your device!)
-fastboot flash recovery recovery.img (TWRP Recovery [is needed])
-then reboot the device into recovery manually by using the volume and power button, not by the command fastboot reboot.
-install superuser
-Done
-Edit build.prop with buildprop editor and allow super user access.(easiest way for noobs)
Click to expand...
Click to collapse
I believe there is a utility that does this all for you as well. I don't have my OP3 yet but I have used utilities with my Moto G3 and it simplified the process a lot.
There is no Utility for the op3. And it already is very simple
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
Julius1993 said:
You can change the build prop without root, but you cannot push it back on your device. i have tried it without root, but its simply not possible and it doesnt make sense either. if you dont have access to write on your root directory you cannot change anything there.
i really recommend rooting. just by the fact, that you can get rid of all the in app commercials! (really awesome)
--
-Edit build.prop with buildprop editor and allow super user access.(easiest way for noobs)
Click to expand...
Click to collapse
I'm just an "interloper" curious about this new phone and noticed this while browsing the forum, and I've modified / files without root being "installed" on many phones before as long as someone had already created a custom recovery for it that worked (and supported adb when booted to custom recovery)::
Should be something like :
Code:
Boot to custom recovery ::
open shell and adb shell,
su // this should just work since recovery's are by definition already rooted and you're booted into it.
Make sure system is mounted (mount -o remount,rw /system) (or whichever switches it requires)
modify your file using the terminal mode or editor provided by TWRP/{other} and save
remount as read (mount -o remount, ro /system)
reboot.
I hope that helps, if not, I will shut up in this forum. I'm assuming TWRP for this device is about the same as for nearly every other one. Sorry if not,.
Cheers.
That's actully true! Haven't thought about that. You can Mount/remount by using a custom Recovery. But still I would recommend rooting, since it doesn't even Void your warranty
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
Dunno guys,i just got my phone yesterday,barely installed anything,like 3 apps running in the background and my Nonstop Knight game reloads in 7/10 tries.
With OOS 3.2 the RAM can (well, could) be used to its fullest. I simply could not throw enough at it to fill up. Five big, full 3D games, 20+ Chrome tabs, all my apps (30ish) open and still 1Gb remaining whilst load-less app-switching
The multitasking on this device is awesome! Good job OnePlus
If this phone had 4GB of RAM, I think it wouldn't have changed anything.
Related
GUIDE: Getting some old features back
INTRO: For those who dislike some of the changes/features made to roms as they are developed and are asking how to get them back, here is a how to. It is usually a simple matter of pushing the old files from previous builds into your current rom. Keep in mind that the devs are building a rom as they see fit. As with any rom that you don't build yourself, there will always be things you want to change.
-If there is a bug, post it in the thread.
-If there is a change that you personally want, then do it yourself. Don't expect the dev, and everyone else who uses the rom, to accommodate your specific needs/wants. You may not have noticed, but you aren't the only one using the rom!
NOTE: This guide and code are meant for the virtuous sense rom, but the concept is universal. For example, if you are using some rom and the new version is posted with, say the amazon mp3 apk removed, and you want it back, refrain from cluttering up the dev's thread with a request to have it back. This is both selfish and a waste of posting space. If you are to the point of installing custom roms, you should first be able to type basic adb/terminal emulator commands to copy/delete files. In this case you would extract the amazon mp3 apk from an old .zip and push/install it into your current one. Now wasn't that easier than waiting and hoping that someone will do it for you?
NOW TO THE GUIDE:
Auto brightness mod - To revert from the auto brightness 'mod', which is far too sensitive, to the original, simply pull the services.jar and framework-res.apk from a rom before the patch, and push them to your framework folder. I've attached them to the second post for ease.
Reboot into recovery
Code:
adb shell mount /system
adb shell rm /system/framework/services.jar
adb shell rm /system/framework/framework-res.apk
adb push [directory of saved file]\services.jar /system/framework
adb push [directory of saved file]\framework-res.apk /system/framework
Reboot
-------------------
Keyboard mapping - The www/com key has been changed to a tab, which is good, as it was non-functional before. However the user keys have been changed too. I've modified a file which keeps the www/com key as TAB but also keeps the user keys as user assignable keys. Also attached to second post.
Reboot into recovery
Code:
adb shell mount /system
adb shell rm /system/usr/keylayout/vision-keypad.kl
adb push [directory of saved file]\vision-keypad.kl /system/usr/keylayout
Reboot
-------------------
Rosie auto-rotate - If you want to keep it so that rosie will only be in portrait mode with the keyboard closed, but dont want to turn off auto-rotate throughout all apps, just push the old rosie. Also attached to second post.
Reboot into recovery
Code:
adb shell mount /system
adb shell rm /system/app/com.htc.launcher.apk
adb push [directory of saved file]\com.htc.launcher.apk /system/app
Reboot
Attachments:
You need to rename "services.jar.zip" back to "services.jar" and "vision-keypad.kl.zip" back to "vision-keypad.kl". This is because the forum wont let you upload .kl and .jar extensions as attachments.
Thanks so much for this. I'll definitely be pushing the auto-brightness mod back, and I may do the keyboard, too (might let others do that one first, or see if rmk40/eViL release an update with that first).
Thanks for this!
Sent from my HTC Vision using Tapatalk
Couldn't make the quick key to work.. maybe I might be doing it wrong but I couldn't make it work.. ill keep trying
sent from t-mobile g2 using HTC sense
android602 said:
Couldn't make the quick key to work.. maybe I might be doing it wrong but I couldn't make it work.. ill keep trying
sent from t-mobile g2 using HTC sense
Click to expand...
Click to collapse
What version of virtuous are you running? Did you rename it and remove the .zip from the end?
I'm using that exact file w/ no issues
calendar/lockscreen
Is it possible to replace the sense lockscreen/calendar with the vanilla versions? I have tried searching but can't find find any instructions for how to do this
felixk87 said:
Is it possible to replace the sense lockscreen/calendar with the vanilla versions? I have tried searching but can't find find any instructions for how to do this
Click to expand...
Click to collapse
Lockscreen - no.
Calendar - maybe, haven't tried. However I did find these 2 threads by typing in the words "htc calendar" in the search box (which means you didn't search very hard )
http://forum.xda-developers.com/showthread.php?t=795222
http://forum.xda-developers.com/showthread.php?t=723761]
They may help you.
Good idea with this thread. It's impossible for us to please everyone and this is absolutely the most constructive way to deal with everyone's personal preferences. There is one key consideration for everyone. If we make other changes to the frameworks which you DO want, pushing files from this thread which have not been updated with said features will eliminate those changes as well. Point is, the concept here is good but it needs to be maintained.
Also, the intention with Virtuous is to provide options. The ROM isn't finalized so ROM Manager isn't populated with all the variants it will eventually have. Case in point, we had to re-base on the new Egypt RUU and are in the process of re-applying all our changes. If we had a variety of options, we would have to redo all of those as well. Once we're in a more "final" state, you'll start to see a lot more choices officially supported with the ROM.
The keyboard mod you have here will probably just become part of Virtuous 0.8.0, by the way. I had not realized our replacement eliminated the quick key customizations (oversight).
Chances are I'm not doing it right, as I'm only about 2% oriented in using ADB, but after following the code, pushing the files, etc, the phone boots up with perpetual errors and crashes. (Phone cannot be launched, etc.)
The process in which I did it was:
Wipe the G2, install v0.7.0, update to 0.7.4, remain in recovery and use adb and followed the code you provided above. (Everything says it works, in terms of mounting, pushing, etc.)
I've also tried it where I reboot after updating, let the phone launch fully, then go back to recovery to push the mod files. Same errors occur.
The only two mods I was interested in were the auto-brightness one and the orientation one.
Any idea what I did wrong?
felixk87 said:
Is it possible to replace the sense lockscreen/calendar with the vanilla versions? I have tried searching but can't find find any instructions for how to do this
Click to expand...
Click to collapse
You could possibly try pushing the lockscreen apk from SuperVillainZ.
NANDROID 1ST THOUGH!!!!!
Sent from my HTC Vision using XDA App
fox-orian said:
Chances are I'm not doing it right, as I'm only about 2% oriented in using ADB, but after following the code, pushing the files, etc, the phone boots up with perpetual errors and crashes. (Phone cannot be launched, etc.)
The process in which I did it was:
Wipe the G2, install v0.7.0, update to 0.7.4, remain in recovery and use adb and followed the code you provided above. (Everything says it works, in terms of mounting, pushing, etc.)
I've also tried it where I reboot after updating, let the phone launch fully, then go back to recovery to push the mod files. Same errors occur.
The only two mods I was interested in were the auto-brightness one and the orientation one.
Any idea what I did wrong?
Click to expand...
Click to collapse
Well from what you are saying, it sounds like the methods are correct. Did you make sure to remove the ".zip" from the end of the services.jar.zip file?
Can this be modified to restore ".com/www" to G2's?
the1wingedangel said:
Well from what you are saying, it sounds like the methods are correct. Did you make sure to remove the ".zip" from the end of the services.jar.zip file?
Click to expand...
Click to collapse
Yup, and I have "always show extension" enabled in folder options, so I definitely got rid of the .zip.
Maybe I'll fiddle with it a little more, see if I missed something.
All right, here's the error I get after removing the files for the brightness mod, and pushing the ones you attached in:
"The application Google Services Framework (process com.google.process.gapps) has stopped unexpectedly."
Basically the launcher is completely inaccessible, the phone remains perpetually in the settings screen because I suppose it's the only thing that it can load without the launcher. It also can't get a signal except for wi-fi, "Mobile Networks" in the settings remains unchecked, and it can't be turned on. Hahaha pretty severe for a rather simple mod.
Here's a full step-by-step of exactly what I did:
Wipe User Data, Wipe Cache
Install virtuous v0.7.0, then v0.7.4 from zip
Remain in Recovery
Open command prompt Change directory to ADB (c:\AndroidSDK\tools)
Entered the following codes one at a time:
- adb shell mount /system (mounts)
- adb shell rm /system/framework/services.jar (file removed)
- adb shell rm /system/framework/framework-res.apk (file removed)
- adb push C:\services.jar /system/framework (success 0.250s)
- adb push C:\framework-res.apk /system/framework (success 1.80s)
(I just have the files on C temporarily for the ease of it.)
Reboot
Then the errors hit once I unlock the screen.
Heheh, I can't really think of any other way to approach it. Hmmmm.
Any idea what I'd need to put back for video codecs? I'm running CM 6.1 but it doesn't run streaming videos from the NHL Gamecenter unlike the stock rom. I'm assuming its a codec issue and was wondering what I'd want to replace.
fox-orian said:
All right, here's the error I get after removing the files for the brightness mod, and pushing the ones you attached in:
"The application Google Services Framework (process com.google.process.gapps) has stopped unexpectedly."
Basically the launcher is completely inaccessible, the phone remains perpetually in the settings screen because I suppose it's the only thing that it can load without the launcher. It also can't get a signal except for wi-fi, "Mobile Networks" in the settings remains unchecked, and it can't be turned on. Hahaha pretty severe for a rather simple mod.
Here's a full step-by-step of exactly what I did:
Wipe User Data, Wipe Cache
Install virtuous v0.7.0, then v0.7.4 from zip
Remain in Recovery
Open command prompt Change directory to ADB (c:\AndroidSDK\tools)
Entered the following codes one at a time:
- adb shell mount /system (mounts)
- adb shell rm /system/framework/services.jar (file removed)
- adb shell rm /system/framework/framework-res.apk (file removed)
- adb push C:\services.jar /system/framework (success 0.250s)
- adb push C:\framework-res.apk /system/framework (success 1.80s)
(I just have the files on C temporarily for the ease of it.)
Reboot
Then the errors hit once I unlock the screen.
Heheh, I can't really think of any other way to approach it. Hmmmm.
Click to expand...
Click to collapse
Weird, I have no idea why that won't work for you. Anyway, there is another way around it. Just open up your patch.zip (from 0.7.0 to 0.7.4), go to the framework folder, and remove the services.jar and framework-res.apk from it. Then go about the wipe/install of both zips like normal. That way the patch zip will no longer replace those two files. Anything that you don't want changed in a patch zip can just removed from it.
Snap Jackel Pop said:
Any idea what I'd need to put back for video codecs? I'm running CM 6.1 but it doesn't run streaming videos from the NHL Gamecenter unlike the stock rom. I'm assuming its a codec issue and was wondering what I'd want to replace.
Click to expand...
Click to collapse
Sorry cant help on that one, I haven't run a CM rom since like 1 or 2.0 haha. You may try to see if others are having that problem, or if it is a known issue with the 6.1 and streaming videos. Is it only that site? Maybe a flash player version problem?
rmk40 said:
Good idea with this thread. It's impossible for us to please everyone and this is absolutely the most constructive way to deal with everyone's personal preferences. There is one key consideration for everyone. If we make other changes to the frameworks which you DO want, pushing files from this thread which have not been updated with said features will eliminate those changes as well. Point is, the concept here is good but it needs to be maintained.
Also, the intention with Virtuous is to provide options. The ROM isn't finalized so ROM Manager isn't populated with all the variants it will eventually have. Case in point, we had to re-base on the new Egypt RUU and are in the process of re-applying all our changes. If we had a variety of options, we would have to redo all of those as well. Once we're in a more "final" state, you'll start to see a lot more choices officially supported with the ROM.
The keyboard mod you have here will probably just become part of Virtuous 0.8.0, by the way. I had not realized our replacement eliminated the quick key customizations (oversight).
Click to expand...
Click to collapse
Yea, I assumed it would be out-dated soon anyway, as changes are made to your roms. I'll adjust it to keep up if the need is there though. It was just a couple of the more simple alterations that I made, and after seeing so many people cluttering up your thread with posts about them, I decided to post this.
Mostly, though, I just wanted to remind people that many simple issues/personal needs (like an app being removed from a rom, or a small change to one or two apps) can be solved with a little bit of thought and some adb knowledge - both of which should be present if you are working with a rooted phone in the first place!
the1wingedangel said:
many simple issues/personal needs can be solved with a little bit of thought and some adb knowledge - both of which should be present if you are working with a rooted phone in the first place!
Click to expand...
Click to collapse
I really cant emphasise this enough!
Sent from my sweet G2
Do you know if there is anyone to return the power down message. I remember before there being and option to restart the phone, hibernate, power off, or reboot into recovery. I liked having that. Is there anyway to return this feature?
Sent from my sweet G2
felixk87 said:
Is it possible to replace the sense lockscreen/calendar with the vanilla versions? I have tried searching but can't find find any instructions for how to do this
Click to expand...
Click to collapse
ddotpatel said:
You could possibly try pushing the lockscreen apk from SuperVillainZ.
NANDROID 1ST THOUGH!!!!!
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
by chance, did anyone try this? if not, I will try it in a few...
After seeing lots of users struggle to root their phone with the existing guides (or worse, brick their phones), often times because of an inability to install/use ADB correctly (so they hobble together steps from multiple guides), I decided to write up a guide for rooting without the need for ADB. This guide uses the Visionary program to achieve temporary root and then gfree to achieve permanent root. Visionary is used only for the temporary root and nothing else (since many on these forums are wary of the app for permanent rooting). All of the gfree steps were scripted together to make things more convenient (and allow less room for user error in typing things in). This has been tested to work with multiple G2s and theoretically should work with the Desire Z as well (if you have the 1.72 OTA though, you will need to downgrade first in order to root as per the instructions in the wiki). All credit goes to the original developers of these programs and those others who aided in achieving root originally (I didn't add anything new content-wise, just bundled it up nicely).
WARNING: A few Desire Z users have reported being stuck on the HTC logo after following this guide. Without having a Desire Z myself, it is difficult to figure out why (since this simple automates known working methods). For the time being, I recommend Desire Z users obtain permanent root using one of the other guides out there.
Instructions
1. Install Terminal Emulator and a file manager (such as Astro File Manager) from the Market.
2. Extract the contents of the zip file to the SD card (this will create a directory called root_files on the card). When done, make sure you unmount your SD card from your computer if you had mounted it as a storage device to transfer the files.
3. Enable Unknown Sources (under Settings->Applications) and USB Debugging (under Settings->Applications->Development).
4. Using your file manager, navigate to the root_files directory on your SD card and select "com.modaco.visionaryplus.r14.apk" to install the Visionary app.
5. Start the Visionary app.
6. Click on "Temproot now." Leave all other settings unchecked.
7. Start the Terminal app.
8. Type the following commands (the $ and # symbols represent the command prompt and should not be typed):
Code:
$ su
# cp /sdcard/root_files/perm_root /data/local/perm_root
# chmod 777 /data/local/*
# /data/local/perm_root
You will see multiple messages scroll by as the programs run. Once you are returned to the prompt in terminal, you will have permanent root (S-OFF), as well as subsidy unlock and SuperCID. At this point, you can also choose to flash the engineering hboot as explained in the wiki. Flashing this hboot allows you to use the flashboot program to flash images from your computer to your phone (which can be very helpful when stuck in a bootloop for example). Note, this is often times the step that bricks people's phones when following other guides. To help mitigate the danger involved, I created a script that first checks the md5 of the hboot file to ensure it didn't get corrupted and then actually performs the flash (many times the bricking occurs because of a typo in this command). If you wish to flash the engineering hboot, type the following command in terminal if you have a G2:
Code:
# /data/local/tmp/flash_hboot
Or this command if you have a Desire Z
Code:
# /data/local/tmp/flash_hboot_z
If you get a verification failed message, you should re-download the files, re-extract them to your SD card, and run the flash_hboot script again.
If you don't want the engineering hboot, just reboot your phone. You can verify you have permanent root by holding volume down while powering on (you'll see S-OFF in the first line of the bootloader). You are now free to install a new recovery and start flashing custom ROMs. If you don't want to flash a new ROM, it's safe to uninstall the Visionary app at this point.
And if you are curious, you can open the perm_root and flash_hboot files in a text editor to see what they are actually doing...
thnak you bro man this was way better !!!
does this apply to someone who just bought the G2.currently on stock 2.2?
GHOST99K said:
does this apply to someone who just bought the G2.currently on stock 2.2?
Click to expand...
Click to collapse
YES!!!! Especially you! This is much easier than the previous ways!
NICE!
I wish I had seen this last night before I spent 4 hour trying to get ADB to see my wife's new phone. Oh well got it working the hard way
Copy flash_hboot
Do you need to copy the flash_hboot like the perm_root file?
Crey23 said:
YES!!!! Especially you! This is much easier than the previous ways!
NICE!
Click to expand...
Click to collapse
cool i guess 2 of my friends will be pleased to hear this cuz i'll be helping them to root their phones.
worked like a charm! sweet man, saved me a lot of time by making this thread and guide, definitely should be added to wiki or sticky thread.
I just bought a T-mobile G2 as well, and I love the phone as is, but I just want to root it, so I can over-clock the cpu just a little bit (maybe about 1Ghz is fine). Can I use this method and keep the phone as is? Or does this method delete everything and I need to use custom rom? I'm coming from original MyTouch 3G (without 3.5 jack) rooted with CM, but I am still a newb.
misterykid89 said:
I just bought a T-mobile G2 as well, and I love the phone as is, but I just want to root it, so I can over-clock the cpu just a little bit (maybe about 1Ghz is fine). Can I use this method and keep the phone as is? Or does this method delete everything and I need to use custom rom? I'm coming from original MyTouch 3G (without 3.5 jack) rooted with CM, but I am still a newb.
Click to expand...
Click to collapse
Once you root the phone, everything will stay as is. Here's a link to overclock to at least 1 GHz on stock ROM: http://theunlockr.com/2010/10/20/t-mobile-g2-overclocked-to-1-42ghz-how-to-overclock-your-t-mobile-g2/
However, it's required you first set up ADB.
I can't just download setCPU and over-clock? I thought as long as the phone is rooted, I can do that...
misterykid89 said:
I can't just download setCPU and over-clock? I thought as long as the phone is rooted, I can do that...
Click to expand...
Click to collapse
You can still download SetCPU, but just having the app itself won't let you overclock the phone. You can try flashing a different ROM and you'll be overclocked once you run that ROM.
Wait, but the recommended and safest way is still with Rage and GFree, right? VISIONary was found to do something with the phones file system that messes up some phones I thought, right? I thought that is why scotty2 made Rage, or am I wrong?
KoolKidsKlub said:
Wait, but the recommended and safest way is still with Rage and GFree, right? VISIONary was found to do something with the phones file system that messes up some phones I thought, right? I thought that is why scotty2 made Rage, or am I wrong?
Click to expand...
Click to collapse
Rage/G-Free is still the safest but they both require ADB, which can be quite a hassle to install for many. True that Visionary has been found to mess one's phone up, but this method only implements the temp root procedure from Visionary (which doesn't require ADB) and the perm root procedures from Rage/G-Free for a more simple way to root one's G2.
so its more like the best of both methods then... i gave up cus i couldnt figure out the ADB but this way looks way easier so ima give this a try thanks for this
Worked perfectly first try. Thanks!
What exactly is kernel? I've seen some people saying they are running over-clock on their G2 with a modded kernel on stock ROM.
misterykid89 said:
What exactly is kernel? I've seen some people saying they are running over-clock on their G2 with a modded kernel on stock ROM.
Click to expand...
Click to collapse
Search google for "Kernel Operating System"
What I meant was is it okay to just change the kernel and run stock ROM that came with my T-mobile G2? Would it not change anything except for the clock speed?
misterykid89 said:
What I meant was is it okay to just change the kernel and run stock ROM that came with my T-mobile G2? Would it not change anything except for the clock speed?
Click to expand...
Click to collapse
Different kernels can be compatible only with certain ROM's. Check on on the kernel before you flash to stock ROM
I DO NOT TAKE CREDIT FOR THE WORK. I ONLY TRANSLATED THE SCRIPTS TO ENGLISH .
I AM NOT RESPONSIBLE IF YOU BRICK OR BREAK YOUR FUJITSU.
I have managed to find a bat file which will allow you to root your F-02E japanese phone.
I have also found a script to allow system R/W made by kikuhare
Steps Involved:
Make sure your phone has 100% charge.
Download the Root + System Mount
Extract the zip's to different folders.
Enable USB debugging under Menu > Settings > Developer Options.
Point to the folder where you extracted drivers from "usb_driver_F-02E_1.0.zip". Wait for drivers to install.
Make sure the phone is connected as PTP not MTP.
CMD into the folder "f-02e_oneclick_su_installer". It is inside the "Root + System Mount_1" files folder.
Run the runme.bat.
Download "Root Checker by joeykrim" from the Play Store.
Run the "Root Checker" app
Wait for the process to finish.
UPDATE System R/W
Connect phone to computer
Download the System Read Write Mounter_1.zip <<<<<< Only need to download if you did not download the "Root + System Mount_1.zip" file.
CMD into the "F-02E_system-mounter" It is inside the "Root + System Mount_1" files folder.
Extract the file and run the"START.bat"
Run everytime the system restarts to mount system as R/W.
Enjoy root .
NOTE: This method does not give full root permissions. You will still be able to underclock the CPU to some degree and use the CoreControl app to disable cores. I will have to run start.bat inside F-02E_system-mounter folder everytime the phone restarts to get system R/W
Drivers: usb_driver_F-02E_1.0.zip
Root Includes System Mount: Root + System Mount_1.zip
System R/W Mounter: System Read Write Mounter_1.zip
Screenshots:
Feel free to ask questions.
anaschillin said:
Hi, I have managed to find a bat file which will allow you to root your F-02E japanese phone. I do NOT take CREDIT for the work. I have merely found the zip. I have tested it and it works. I AM NOT RESPONSIBLE IF YOU BRICK OR BREAK YOUR FUJITSU.
Steps Involved:
Make sure your phone has 100% charge.
Extract the zip's to different folders.
Enable USB debugging under Menu > Settings > Developer Options.
Point to the folder where you extracted drivers from usb_driver_F-02E_1.0.zip. Wait for drivers to install.
CMD into the folder where you extracted the f-02e_oneclick_su_installer.zip files.
Run the runme.bat.
Download RootChecker from the Play Store. https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en
Reboot the phone.
Run the RootChecker app
Wait for te process to finish.
Enjoy root .
NOTE: This method does not give full root permissions. You will still be able to underclock the CPU to some degree and use the CoreControl app to disable cores.
Drivers:
http://www.4shared.com/zip/kGmw0Suu/usb_driver_F-02E_10.html?
Root: http://www.4shared.com/zip/D90h9kH2/f-02e_oneclick_su_installer.html?
Feel free to ask questions.
Click to expand...
Click to collapse
I havent even got the phone yet but are there any custom roms that work on this phone? Thanks
the-blind-bandit said:
I havent even got the phone yet but are there any custom roms that work on this phone? Thanks
Click to expand...
Click to collapse
No, not enough developers and interest for the phone outside Japan. I doubt anyone will be willing to put in effort as well
Oh well, but it is a very good phone, i think ill still get it though. I just wanted to know is half of it in Chinese even if you select english, i just heard this on youtube about another one of fujitsu's phones?
Sent from my Xperia T
the-blind-bandit said:
Oh well, but it is a very good phone, i think ill still get it though. I just wanted to know is half of it in Chinese even if you select english, i just heard this on youtube about another one of fujitsu's phones?
Sent from my Xperia T
Click to expand...
Click to collapse
Only Docomo and Fujistu apps are in Japanese. Everything else is in English.
Thats fine i suppose with root explorer i can delete those apps by deleting the apk in system app? Also if you have xposed app settings you can change the language per app would that also work?
Sent from my Xperia T
the-blind-bandit said:
Thats fine i suppose with root explorer i can delete those apps by deleting the apk in system app? Also if you have xposed app settings you can change the language per app would that also work?
Sent from my Xperia T
Click to expand...
Click to collapse
I have just frozen them, just incase if the phone needs the at somepoint. Xposed framework doesnt work as it need system R/W and the root method has not allowed system R/W mainly because the phone bootloader not unlocked. Secondly make sure you do not uninstall/disable the Phonebook and Phonebook Service provided by Docomo. Its key to allowing you to add and sync contacts.
So Xposed wont work at all then, thats a shame what about lucky patcher, does that need R/W?
Sent from my Xperia T
Improved the .bat file. Now you will have system R/W
Download the root file again and run it. Follow the steps starting at 10 if you have already rooted. :good:
Thanks
Sent from my Xperia T
anyone else besides the OP got their f02 rooted with this?
I may not be able to help any further. I have boot looped my phone. I cannot get it past the NTT Docomo screen. I think I know what is causing it but I cannot get the phone connected to the PC. I may need to send it into Fujitsu.
Good luck on fixing it
Sent from my Xperia T
I tried the following OP method didnt work for me
Thank! i just got the F-02e today. will try to root it.
btw, have you overcome a heating and self-shutting off prob on this phone?
anaschillin said:
Hi, I have managed to find a bat file which will allow you to root your F-02E japanese phone. I do NOT take CREDIT for the work. I have merely found the zip. I have tested it and it works. I AM NOT RESPONSIBLE IF YOU BRICK OR BREAK YOUR FUJITSU.
Steps Involved:
Make sure your phone has 100% charge.
Extract the zip's to different folders.
Enable USB debugging under Menu > Settings > Developer Options.
Point to the folder where you extracted drivers from usb_driver_F-02E_1.0.zip. Wait for drivers to install.
CMD into the folder where you extracted the f-02e_oneclick_su_installer-improved.zip files.
Run the runme.bat.
Download RootChecker from the Play Store. https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en
Run the RootChecker app
Wait for the process to finish.
UPDATE
Download ES File Explorer. Run it.
Press Menu then scroll down the list and click Root Explore.
Change the directory to root. (Meaning where you can see all system folders)
Look for system and hold the folder, then press more then properties.
Press Change in permissions.
Tick all the boxes at the bottom.
Enjoy root .
NOTE: This method does not give full root permissions. You will still be able to underclock the CPU to some degree and use the CoreControl app to disable cores. I have not been able to mount system as R/W and I had trouble installing BusyBox.
Drivers: usb_driver_F-02E_1.0.zip
Root: f-02e_oneclick_su_installer-improved.zip
Screenshots:
Feel free to ask questions.
Click to expand...
Click to collapse
anaschillin said:
I may not be able to help any further. I have boot looped my phone. I cannot get it past the NTT Docomo screen. I think I know what is causing it but I cannot get the phone connected to the PC. I may need to send it into Fujitsu.
Click to expand...
Click to collapse
i hope they can fix it immedietly, only you have work for this device (i hope any other)
question:
anyone have a stock rom for this device? may show me that's link?
Click to expand...
Click to collapse
Hi I am in the same situation, uninstall many applications in Japanese that I have the phone now in its box sirbe not all, send email to the seller took days with him and a solution is supposedly looking for me if I were to fix it passeth forums or sbrire a new post with the solution that would not be other than the original rom flaseo greetings
GattacaWroclaw said:
Hi I am in the same situation, uninstall many applications in Japanese that I have the phone now in its box sirbe not all, send email to the seller took days with him and a solution is supposedly looking for me if I were to fix it passeth forums or sbrire a new post with the solution that would not be other than the original rom flaseo greetings
Click to expand...
Click to collapse
You can reset the factory settings. Reboot the phone and hold the volume up, the phone will boot into recovery mode. You will be able to do a factory recovery.
armei said:
Thank! i just got the F-02e today. will try to root it.
btw, have you overcome a heating and self-shutting off prob on this phone?
Click to expand...
Click to collapse
I have not been able to overcome the issue. It is a design issue. Because it is waterproof phone the heat cannot disperse.
The only thing I have been able to do is keep the CPU frequency down to lower the time it takes for the phone to heat up.
garynsa said:
I tried the following OP method didnt work for me
Click to expand...
Click to collapse
What does it, when you run the root file?
Could you also tell your build number. Is it VR17xxx or VR16xxx?
[Tut]How To Systemless Root+Root+More!
This was fully tested on SM-G928A;Baseband:UCU2AOJ1 on 5.1.1
Just in case needed //SM-G928A\\ **Full Odin Restore G928AATT2AOJ1**
$<Download Mode & Odin Systemless Root Flash>
Requirements:
1.A Windows Computer
2.Your Phone Device SM-G92-0/5/8A
3.Odin 3.10.7
4.Kernel_Root_Android_5.1.1_AT&T_SamFirm.NET
5.USB Drivers(Most of the time if connect the phone to the computer using the usb cord that comes with the device it will install all of the drivers if your computer is connected to the internet.
____________________
Okay now assuming that everything has been required, we can begin.
Turn off your phone and open Odin with admin rights on the computer & connect your phone to the computer using the usb cable that comes with the phone.
On the phone now hold all of these following buttons down, Volume Down+Home Key+Power Soon after once you see the blue screen release those buttons and press the Volume Up key to enter Downloading Mode.
Now in Odin on the computer, it should have recognized your device now press the "AP" button and open up for example, "G928A_Kernel_Root_5.1.1_SamFirm.NET.tar.MD5" now just press start and sit back and relax and soon you will have Systemless Root!(Note your phone will reboot which is normal after the flash.
--------------------
#<Obtaining Root Access>
Requirements:
1.A Windows Computer
2.Your Phone Device SM-G92-0/5/8A
3.USB Drivers(Most of the time if connect the phone to the computer using the usb cord that comes with the device it will install all of the drivers if your computer is connected to the internet.
4.Flashed The Systemless Root
5.Kingo Root
6.Root Checker Cost $FREE
7.SuperSU Cost $FREE
8.BusyBox Cost $FREE
9.Developer Options (USB Debug)
____________________
Okay now assuming that everything has been required, we can begin.
Go into Settings>System>About Device & Enable Developer Options.(Keep tapping the "Build Number" category until it says Developer options have been enabled.
Connect your device with your usb that which comes with the phone on the computer. Open "Kingo ROOT" on your computer with admin rights, and once the program asks you to turn USB Debug on, go on your phone into Settings>System>Developer options and make sure it is enabled as well as usb debugging. Wait for kingo root to find your device and once found, it will ask you to either "Reroot,Root, or Remove Root, click "Reroot" then wait for it to start.(After it starts you should see on your phone the kingo root usb app pop-up and show the same thing you see on your computer)
After it is done it should confirm you have been rooted and will ask to donate.
Now you may exit out of the program on the computer and the phone and once out of the app and back on your phone, you will want to look in your app drawer for the kingo root "Superuser" and uninstall this. Then head on over to the playstore if haven't all ready and install "SuperSU" & "Busybox" if want to. Once have the SuperSU app open it and install the su binary updates with the "Normal" option not the recovery one since we don't have that.... & once done just press OK DO NOT REBOOT or you will bootloop and will have to use Odin to reflash your system of your phone to get it back working out of the box "state"
UPDATE Have a pc around and can still boot with root:
Yamaha169 said:
You can restart the device while rooted... but you have to have ADB to do so...
When you reboot ... you will get stuck at the ATT logo... at this point... plug your phone in to your pc...
Open up ADB (COMMAND WINDOW)
type in
ADB devices
until your device # appears in adb... (this can take a minute for your pc to find your phone) so don't panic
This means the phone is found...
From this point... type
ADB ROOT
ADB SHELL
YOU will now be inside the shell of the device with root permissions
Now type
setenforce 0
(MAKE SURE LOWERCASE just like seen. "setenforce 0" if do Setenforce 0 it won't be found.....)
This will set selinux to permissive ... allowing the phone to boot...
Someone with enough experience could probably create a selinux permissive stock kernel ... but I've contacted several developers with no response ...
Click to expand...
Click to collapse
Now open up the root checker app & click verify to see if you truly do have root.(You must grant root access so allow once it pops up.) Enjoy your root but never ever reboot.
UPDATE: How to Root If Possibly not allowing you to root!!!
Step one you will need to of downloaded "Android Studio
Step two you will now need to install all of the updates(Well that's what I did) inside the studio program.
Step three now locate 'program tools" which for me was located here: C:\Users\NameofComputer\AppData\Local\Android\android-sdk\platform-tools
Step four make a cmd.exe file to go in the platform-tools simply just clicking on the "start button" on windows and searching "cmd" then dragging the cmd file to the folder.(Rename it to something like ADB Root or something different than just cmd)
Step FIVE download the su binary which can be located HERE and place it in the "platform-tools" folder.
Step SIX now almost there. Open the cmd file(ADB Root.exe) and once opened, plug the phone into the computer with the cable that came with your phone.
Step Seven:^.^ now with the phone plugged in and the program start, type this command to make sure your device is found:
Code:
adb devices
and if found you will see your attached devices and if more than one or can't see your device, you can do
Code:
adb kill-server
command and it will restart adb.
Step Eight: MAGIC time lol now that your phone is connected and you can see it is indeed listed, type these commands as followed:
Code:
adb root
adb remount
adb push su /system/bin/su
adb shell
chown 0:0 /system/bin/su
chmod 6755 /system/bin/su
You don't really have to do the other commands after pushing su it's just for pre-caution.
Step Nine: Now do the following at the top and try to use the Kingo root once more and click root or reroot.
If this doesn't work try to press unroot and restart phone then try this again.
Also like down below I talk about if you did reboot before you unrooted, you can still unroot but sometimes it's tricky and it needs you to do the adb remount before will work so just remember that...
--------------------
$#$<UnRooting & Keeping Systemless Root So You Can Reboot & Reroot>
Requirements:
1.Your Phone Device SM-G92-0/5/8A
2.Root Access(Superuser rights)
3.SuperSU Cost $FREE
4.Root Checker Cost $FREE
____________________
This is very simple and easy to do, all you must do after every root and before every reboot is to go into "SuperSU" and go into the settings and scroll down until you see "Fully Unroot" and click that and once done verify with the root checker that you are indeed unrooted but still have adb shell and once done that you may freely reboot with no bootloop and then if want root once more just use "Kingo Root" on the computer to reroot once more.(I'm hoping someone will come out with an app that does the same thing and works so we don't need the computer anymore which would make it much easier..)
Edit/Update:
I found that if you maybe forgot to unroot before a reboot that you can still unroot without the need of going into odin and reflashing stock system just by connecting your phone to the computer via the usb that which comes with your phone and opening up Kingo Root and waiting for it to find your phone then click unroot and wait for it after you have unrooted and you will hear a sound which means it's fixed! So just force shutdown the device with pressing both: Volume Down+Home Button+Power then it will boot back up as normal!
-------------------- ____________________ -------------------- ____________________
~My Findings Through Long Research & Errors~:
<How to Fix Wifi Bug That Comes With Flashing Systemless Root>
Requirements:
1.Your Phone Device SM-G92-0/5/8A
2.Root Access(Superuser rights)
3.SuperSU Cost $FREE
4.BuildProp Editor Cost $FREE
____________________
On your phone open up the "BuildProp Editor".
click on the search button and search for "ro.securestorage.support=true" now once found change the =true to =false and save. Now you must reboot for it to take place but remember to UNROOT before you reboot.
Now doing this your wifi will stay connected and you no longer have to enter your password millions of times so it will be nicer to keep systemless root.
--------------------
<How to Enable AT&T Hotspot System FULLYApp>
Requirements:
1.Your Phone Device SM-G92-0/5/8A
2.Root Access(Superuser rights & .SuperSU Cost $FREE)
3.Root Explorer Cost $3.99
4.NEW Modded TetheringProvision .apk Cost $FREE(Also can be found in this thread in attachments.
5.ADB Root cmd knowledge or Download SQLite Editor Cost $2.99
6.BuildProp Editor Cost $FREE
____________________
Okay my fellow members that stayed on 5.1.1 with me, this tut did once work but then at&t blocked me and it stopped working but now rejoice becase there is a bypass once more!!!
NEW WAY:
I'm not sure which worked so I'm gonna just tell you everything that I did...
1.I first rooted obviously
2.I found a new TetheringProvision.apk which I have uploaded down in the attachment and at the top.
3.I used adb root for this but this can also be done with sqlite editior so I'll explain both ways, first way will be the easy way the adb root...>>>
Step 1: Ensure you have the correct OEM drivers installed for your handset on the computer
Step 2: Download and install the necessary ADB drivers (v1.4.2)
Step 3: Enable USB debugging on your Android handset:
Go to Settings > About Device, and tap the build number 7 times or until you see 'You're now a developer' message.
Return to Settings > Developer options and use the toggle button to turn on USB debugging. Then tap OK button to accept the warning and continue.
Step 4:Connect your device to PC with original USB cable.
Step 5: Launch a command window on your Windows PC.
Step 6: Access ADB shell and run the following command:
adb shell now just type " settings put global tether_dun_required 0 " and enter.
________----------Now the sqlite way
Step 1:Go into sqlite editor and allow root rights...
Step 2: Locate "Settings Storage" and click on "Settings.db then click on "global"
Step 3:Locate tether_dun_required 0 and if not there add by clicking on the +
then fill out name as " tether_dun_required " >>And value as " 0 " and then save file and unroot then reboot.
Now then after all of that I downloaded the build.prop which I know you don't have to but it makes it easier for me to do so and probably for you too...
Step 1:Get build.prop editor from the playstore and open it to grant root rights.
Step 2:Click on the pencil icon on the top right where the search icon is.
Step 3: Scroll all the way down to an open line.(If not one make one.)
and put this in the line....>>> " net.tethering.noprovisioning=true " and then click the save button at the top right and then save it and unroot then reboot.
Then replacing the Tetherprovision.apk . >>>
Step 1: Download the NEW modded TetherProvision.apk at top or at bottom.
Step 2: get a root explorer and go to System/App/TetheringProvision
Step 3: Rename the actual TetheringProvision.apk to TetheringProvision.apk.bak
Step 4: in the same location, go into "arm64" and rename the TetheringProvision.odex to TetheringProvision.odex.bak
Step 5: Now locate the modded TetheringProvision.apk you've just downloaded and place it in System/App/TetheringProvision/ now should be two TetheringProvision, the TetheringProvision.apk.bak and the modded one, TetheringProvision.apk.
Step 6: change the property promissions of the tetheringprovision.apk to give it root rights by changing the promissions to look just like the actual one which is " rw-r--r-- "
Step 7: save and unroot then reboot!
Now youre wifi tether and usb should work!!! enjoy!
--------------------
<How to disable OTA & Security Notification>
Requirements:
1.Your Phone Device SM-G92-0/5/8A
2.Root Access(Superuser rights & .SuperSU Cost $FREE)
3.Titanium Backup & Titanium Backup Pro License Cost $Free | $5.99
____________________
Open up titanium back with pro license and freeze these following apps:
1.SecurityLogAgent(This is that annoying notification that which comes with the systemless flash root that keeps annoying you to reboot and undo what you done.)
AT&T Software Update(This will make it so AT&T won't push any updates to your device anymore so no need to worry about installing an update ota and losing your root or something else like bootlooping.
And again, all of this sticks after you unroot and reboot!
___________________________________________
<How to Get Youtube RED (Sort of) FREE!>
Requirements:
1.Your Phone Device SM-G92-0/5/8A
2.OGYoutube Cost $Free
Basically all you do here is download the modded sort of youtube app(OGYoutube) and install it then done! You now can download videos/music on the app and have access to run audio in the background plus NO ADS!!! (if there are I haven't seen any yet...)
Best part of this too since can't be used fttb, no need for XPOSED apk!
_____________________________
<How To Install Viper4android>
Requirements:
1.Your Phone Device SM-G92-0/5/8A
2.Root Access(Superuser rights & .SuperSU Cost $FREE)
3.Fast Reboot
4.Soft Reboot
5.Viper4Android V2.3.4.0
6.Audio_Effect.Config
7.Titanium Backup & Titanium Backup Pro License Cost $Free | $5.99
8.IRS Impulse Response Sample files
9.Root Explorer Cost $3.99
~~~~~~~~~~~~~
To Read the tuts yourself than rather follow my tut, you may do so by following This Link & This Link
~~~~~~~~~~~~~~~~~~
Alright, I decided to do my own detail tut to make it much easier so follow me and you'll have viper4android in no time : )
So let's get begin, download if not already, the busybox,SuperSU,TitaniumBackup,Fast reboot,Soft Reboot, & Root explorer. Now having all that done open up Busybox and allow it root rights and you may wait for it to research for a smart intall, or just press install. Once you installed it in the default location System/xbin, click on the will be installed to location and choose System/bin and install it there too.(Not sure why but that's what the tut called for.)
Now let's download the folders for viper4android, go ahead and download Audio_Effect.Config.zip file,IRS Impulse Response Sample files, & the Viper4Android V2.3.4.0 folder.
Now open up the root explorer and unzip all that which is zipped up.(Which is all of the files;Audio_Effect.Config.zip file,IRS Impulse Response Sample files.zip, & the Viper4Android V2.3.4.0 folder.zip
)
Now once all are extracted, we will begin putting what is needed where.
Let's start off with the ViPER4Android_FX_A4.x (The actual name of the folder) you're gonna want to long press it and copy this folder. Once done, you're gonna want to paste this folder in System>Priv-app and make sure to change the permission of the .apk to 0644 rw-r--r-- & the FOLDER to 0755 rwxr-xr-x(The folder should have the same permissions as the other folders in that location.) which is inside the folder to give it root access which is 0644;rw-r--r-- and if not sure what root permission should look like, refer to this link Or Google what it looks like, then save/press ok.
Now go back to where you extracted your folders, and this time copy the "audio_effects.conf and go to System>etc and find and rename the actual audio_effects.conf to audio_effects.conf.bak and then paste the copied modded audio_effects.conf here & DONT FORGET change the permissions to give it root rights.
Now after all is done, open the app "Titanium Backup Pro" and look for and freeze these following applications: 1.Adapt Sound 4.0 & SoundAlive 3.0 now open the app "Soft Reboot (Root) and click yes you want to do a soft reboot. Then once back up(If want you can click the "Fast reboot app" to quickly refresh the system) and running you should see the viper app inside your app drawer. Open it and install the update/software when ask you to and once done it should ask for you to reboot just click on ok and then go out and back to the "Soft Reboot (Root) then do another soft reboot.
Now almost DONE!!! Once back up and running again, go to your root explorer again where you extracted the folders and grab the folder of "ViPER4Android and move it to your device storage ex; Storage/emulated/0 (It's where the download folder is and dcim folder is.. Then finally, go toSettings>Device>Sounds and notifications>Sound quality and effects and toggle on all of the listings[NOTE YOU MUST PUT EARPHONES IN FOR THESE TOGGLES TO SHOW]; UHQ Upscaler|SoundAlive+|Tube Amp Pro now you're done enjoy viper4android via editing the settings in the app.
Edit
You need to download SELinux Mode Changer and give root rights and just click on permissive mode and all done. Also might need to use compatible mode in the Viper4Android settings.
I found that this mod works with Pandora and Youtube app but not with google music or the default music app and not sure how to fix that....
__________________________________0
This is some more quick finds which you don't need a tut for just information I'd like to share so you all know.
I found out that you can use Titanium Backup Pro Cost $5.99 and freeze anything you want such as bloatware and that annoying notification that appears every time you reboot if have systemless root installed "SecurityLogAgent" and as long as you UNROOT before you reboot, it is safe and everything you froze stays frozen.
Now I haven't tried uninstalling any system apps so I wouldn't advise doing that unless you wanted to but I don't see the point except to free space up since you can just freeze anything and does the same thing except for freeing space....
I haven't been able to unlock the bootloader in my research and errors which probably never gonna happen anytime soon....
I also never found an app that could root the device yet without a computer....
And yeah that's it! I just was so happy to find out all of this and just had to share it with xda members which are on the same boat as me that has been wanting some "freedom" which now can have a piece of it. : )
If found these tuts to be helpful, feel free to hit thanks button and if want donate.
AngelRyu said:
Just gonna get right to it and be fast.
Odin Flash Kernel for systemless root.
obtain root
Download SuperSU
After rooted download some sort of buildprop editor and search for " ro.securestorage.support=true" Now change =true to =false. and save!
Now go into the superSU app and fully unroot then reboot and also keep adb shell root!
So you fix the wifi bug plus keep the adb shell so you can obtain root once more! Now we just need some app that can give root access with 1 click without needing a pc and this would work for me until we can actually reboot with root without it bootlooping anyways.... I still can't find a wifi tether app or a method that works for the at&t hotspot app though...
Click to expand...
Click to collapse
Question for clarification.
So current method for rooting g928a is this systemless root.
Question 1, will it brick my phone with this root if i reboot, because i read somewhere on here that the phone will just keep on rebooting.
You mention using superSU app to unroot to reboot. So basically I have to unroot with superSU whenever I want to reboot then reflash again to get root?
fuzmik said:
Question for clarification.
So current method for rooting g928a is this systemless root.
Question 1, will it brick my phone with this root if i reboot, because i read somewhere on here that the phone will just keep on rebooting.
You mention using superSU app to unroot to reboot. So basically I have to unroot with superSU whenever I want to reboot then reflash again to get root?
Click to expand...
Click to collapse
Yes you must unroot to remove the su binary so the system acts like nothing has happen. I use kingo root for windows and it works every time with root all you need to do is hit "root" or it may say "reroot" and works every time. I have been playing with this a lot trying to do things to get it to reboot with root but have failed so far.... I wish someone with more experience would approach this so we could have an app to use at least so we not have to use pc every time to reroot until we get the ability to keep root and reboot.
Kingo root can be found here : https://www.kingoapp.com/android-root.htm
and this works after flashing the kernel from odin. This was the only way I actually found to be able to get root was with this because manually pushing su just didn't work for me....
Thanks for being much clearer on the instructions and idoit proof. I was worried about the bootloop and I thought there was no exit strategy on this expensive phone until you mention reflash. With your extensive tinkering on this, did your knox security trip up?
If this is the only possible way, maybe the community could make some sort of app that if we have to shutdown or reboot the phone specifically for g928a, it will safely unroot it for us.
TASKER?!
Anyone know if this still works after taking the latest OTA a few days ago?
The problem is this isn't root. I restart my phone several times a day. There is no point especially if I can't get a custom OS. However, thanks for making the instructions clear. And for anyone who doesn't understand systemless root, it's temp root. When you reboot dmverity sees the false file structure and tries to rewrite and reverse the changes, effectively removing root. On the Note 5 AT&T for temp root you didn't have to unroot before reboot as it wouldn't boot loop, it would just remove root and let you continue on. So something in this version must be getting farther in breaking past dmverity if it's causing the OS to bootloop.
tonys.94 said:
The problem is this isn't root. I restart my phone several times a day. There is no point especially if I can't get a custom OS. However, thanks for making the instructions clear. And for anyone who doesn't understand systemless root, it's temp root. When you reboot dmverity sees the false file structure and tries to rewrite and reverse the changes, effectively removing root. On the Note 5 AT&T for temp root you didn't have to unroot before reboot as it wouldn't boot loop, it would just remove root and let you continue on. So something in this version must be getting farther in breaking past dmverity if it's causing the OS to bootloop.
Click to expand...
Click to collapse
I was wondering if maybe we could place SU somewhere else so we might could trick it to reboot with root but haven't done it yet and or maybe keep SU on the sdcard/storage and use the terminal on the phone to push su to xbin every reboot but just hoping maybe can get root working without making the stupid thing bootloop.... Like I said I been doing a lot of dumb stuff with my phone because I have been so disappointed in this phone with not having wifi tether at the most really but now that got that I'm much happier but I'm still on the research of keeping root and being able to reboot.
I won't be updating until something maybe for sure comes along with 6.0 I can wait because my galaxy s4 I had stayed on stock version forever because was able to do everything so was no need to update really.... Anyways yeah lol maybe someone greater or maybe my playing around will work. WE can only hope...
Oh yeah, to the other guy NO it did not trip knox doing any of the things I've done. which I wouldn't care if could unlock the bootloader lol...
Edit:
I've done all I can think of and didn't work to keep root on a reboot except it did keep root without bootloop with a soft reboot...
I found out to maybe later will add tut up top but for now I'd like to tell you or whoever, if you do bootloop due to not being able to access the su unroot in time, you can still connect your device with Kingo Root in that bootloop and can unroot to save you from having to reflash every time... Might have to reboot as soon as you hear the found from the unroot though.
Oh and on a factory reset everything sticks excepts what was frozen becomes unfrozen just fyi...
Yeah, that's all I can find so I'm done with it hope someone can help later on but I'm just happy with wifi tether so much : )
So what all can we do with this root
Thank you for your hard work. it's very much appreciated!!!
Will pay part of my bounty which is 50 dollars pay day!!
But, please reply. what all can we do with this root!?
O0Gjulian said:
So what all can we do with this root
Thank you for your hard work. it's very much appreciated!!!
Will pay part of my bounty which is 50 dollars pay day!!
But, please reply. what all can we do with this root!?
Click to expand...
Click to collapse
Hi, I didn't come up with anything but the fix for wifi bug and hotspot app.
I just made a very detail tut to help others, but thanks.
I would wait on the bounty to be paid to someone who can make it possible to keep root on and still be able to reboot.
So in theory with this method I can root, install a modified tetheringprovisions, unroot (as hotspot is the only feature I actually desire), and go about my business without worrying about bootlooping or knox being tripped? Feels too good to be true, but I want to believe.
Just a reminder that Android 6.0.1 is right around the corner. If you don't fully go back to stock before the upgrade it will not flash and could possibly wipe the data partition. Both the system and boot images need to be 100% stock.
antizombie said:
So in theory with this method I can root, install a modified tetheringprovisions, unroot (as hotspot is the only feature I actually desire), and go about my business without worrying about bootlooping or knox being tripped? Feels too good to be true, but I want to believe.
Click to expand...
Click to collapse
It's true, that's how my phone is rolling with frozen apps and the modded hotspot without root, but still the systemless root remains in the system but doesn't do anything with out a computer or applying the kingo root to true root it.
I haven't tested the adaway yet so idk if will work or not.... and I been wanting xpose to work to disable youtube ads but haven't tried that either. . I might root tonight and try out adway tho.
But yeah to your question you are 100% safe and will not change anything or trip anything; phone can reboot all it wants with no bootloops with the modded tether is what I'm trying to say lol .. .
Edit:
Yeah adaway works after unroot and reboot. . . But I decided not to use it because a lot of people us adfly and it wouldn't let me access the link so yeah.....
On another note I froze a lot of stuff and done a lot of things not sure which part caused it but it doesn't bother me because I don't use samsung pay but in the end I had to freeze samsung framework for samsung pay because it kept saying force closed but which again Idc about that app so no biggy to me : )
Was Samsung Pay crashing before you started freezing apps? I have yet to use Pay but I'd prefer to keep my options open if possible.
antizombie said:
Was Samsung Pay crashing before you started freezing apps? I have yet to use Pay but I'd prefer to keep my options open if possible.
Click to expand...
Click to collapse
Honestly, I'm not sure but it had to be either the freezing at&t update or securityagent because it seemed to happen after that... Or could be the hotspot mod but I didn't get any crashes until i froze those 2 apps so idk...
Package Disabler in play store freezes apps so what's the point?
Can you fully remove with TiBu and be safe unrooted?
---------- Post added at 03:55 PM ---------- Previous post was at 03:40 PM ----------
navalynt said:
Just a reminder that Android 6.0.1 is right around the corner. If you don't fully go back to stock before the upgrade it will not flash and could possibly wipe the data partition. Both the system and boot images need to be 100% stock.
Click to expand...
Click to collapse
Yeah and from what I've seen of the nightmares people have been having with their Note 5's on Marshmallow, I'm staying FAR away from it!
I can confirm this works. Sorta a pain to have to reroot but hey, It's progress. We may never have a custom ROM option or recovery, But this is the next big thing. If we can find a app that'll just reroot us. it's perfect. (somewhat) Just rooted a few minutes ago. Going to play around. More than likely I'll re flash stock and make a youtube video for anyone needing questions or wanting to see it be done.
And I lied.. So, My experience was weird. Lagging constantly and weird download issues with a fresh wipe.
I'm sadly gonna have to unroot and hope that a better method would come out.
):
O0Gjulian said:
I can confirm this works. Sorta a pain to have to reroot but hey, It's progress. We may never have a custom ROM option or recovery, But this is the next big thing. If we can find a app that'll just reroot us. it's perfect. (somewhat) Just rooted a few minutes ago. Going to play around. More than likely I'll re flash stock and make a youtube video for anyone needing questions or wanting to see it be done.
And I lied.. So, My experience was weird. Lagging constantly and weird download issues with a fresh wipe.
I'm sadly gonna have to unroot and hope that a better method would come out.
):
Click to expand...
Click to collapse
I'm not sure why you would experience "lag" because I have no lag what so ever. Maybe try going to settings>system>developer options and change both transition animation scale and window animation scale to 0.5x
I've reflashed stock many of times due to to trying to find everything there is to find and I've had no "lag" but also you could download the soft reboot and fast reboot from market. Fast reboot frees up memory via closing and restarting certain apps, and soft reboot kills zygote and does a "hot reboot" without going through whole start up process .
Please reply I'm gonna try and help you : )
Also @
joe3681 said:
Package Disabler in play store freezes apps so what's the point?
Can you fully remove with TiBu and be safe unrooted?
---------- Post added at 03:55 PM ---------- Previous post was at 03:40 PM ----------
Yeah and from what I've seen of the nightmares people have been having with their Note 5's on Marshmallow, I'm staying FAR away from it!
Click to expand...
Click to collapse
I can confirm freezing anything won't harm the system on a reboot after unrooting but not sure about removing the apps would be safe. I have however remove the youtube app and reinstalled it in play store and it didn't harm anything.
AngelRyu said:
I'm not sure why you would experience "lag" because I have no lag what so ever. Maybe try going to settings>system>developer options and change both transition animation scale and window animation scale to 0.5x
I've reflashed stock many of times due to to trying to find everything there is to find and I've had no "lag" but also you could download the soft reboot and fast reboot from market. Fast reboot frees up memory via closing and restarting certain apps, and soft reboot kills zygote and does a "hot reboot" without going through whole start up process .
Please reply I'm gonna try and help you : )
Thanks for helping me! I went ahead and flashed stock and followed your steps!
Working great now!
NOW, My next question... What difference would it make if I used package disabler pro VS TBU?
Wouldn't both of these apps freeze the processes? Or would it make a difference with root and SU access?
Click to expand...
Click to collapse
O0Gjulian said:
AngelRyu said:
I'm not sure why you would experience "lag" because I have no lag what so ever. Maybe try going to settings>system>developer options and change both transition animation scale and window animation scale to 0.5x
I've reflashed stock many of times due to to trying to find everything there is to find and I've had no "lag" but also you could download the soft reboot and fast reboot from market. Fast reboot frees up memory via closing and restarting certain apps, and soft reboot kills zygote and does a "hot reboot" without going through whole start up process .
Please reply I'm gonna try and help you : )
Thanks for helping me! I went ahead and flashed stock and followed your steps!
Working great now!
NOW, My next question... What difference would it make if I used package disabler pro VS TBU?
Wouldn't both of these apps freeze the processes? Or would it make a difference with root and SU access?
Click to expand...
Click to collapse
I'm not sure because I've never heard of that program, but I did buy it just now for about $1.89 and the activation keeps failing so I can't test it to see the difference but with titanium you can do everything not just freeze stuff but back up apps and their data and much more.
Titanium backup has been around for ages which is why I recommend it.
Click to expand...
Click to collapse
I use package Disabler. Works like TiBu without root. Only reason to root would be to fully remove apps but would it boot okay after?
I've tried over 5+ different treble ROMs and the mobile data will not work. My friend @Spaceminer had helped me try to solve it by finding an apns-conf.xml as well as a flashable zip but no luck.
I'm using the Moto G6 Play XT1922-7 Boost Mobile Variant.
I'm sorry I haven't provided much detail to the issue but this basically sums it up.
Thank you for any help.
Same problem here with 1922-4 retail variant, i have tried to flash the vendor.img over gsi's via fastboot but it just get stuck in a bootloop. The only option i have is stay in stock pie
Alphita said:
Same problem here with 1922-4 retail variant, i have tried to flash the vendor.img over gsi's via fastboot but it just get stuck in a bootloop. The only option i have is stay in stock pie
Click to expand...
Click to collapse
Did you try to flash the vendor.img on TWRP?
sinkoo1979 said:
Did you try to flash the vendor.img on TWRP?
Click to expand...
Click to collapse
Yes and got another bootloop and the 'failed to mount /vendor' message when you try to flash anything. Idk if there's a possible fix for mobile networks
Alphita said:
Yes and got another bootloop and the 'failed to mount /vendor' message when you try to flash anything. Idk if there's a possible fix for mobile networks
Click to expand...
Click to collapse
You have to find your correct apns-config.xml, place it in /system/etc and set permissions to 0644. Then reboot, open your mobile network settings and reset your apn.
If you ever want to go from Pie to Oreo, grab your very last Oreo firmware and flash everything like normal. Some things won't flash, and that's okay. If that happens, just skip it and flash the next items in line. When you're done, reboot it normally and let it encrypt at least once. If you don't let it encrypt first it can cause a recovery bootloop and you'll have to flash everything again.
Spaceminer said:
You have to find your correct apns-config.xml, place it in /system/etc and set permissions to 0644. Then reboot, open your mobile network settings and reset your apn.
If you ever want to go from Pie to Oreo, grab your very last Oreo firmware and flash everything like normal. Some things won't flash, and that's okay. If that happens, just skip it and flash the next items in line. When you're done, reboot it normally and let it encrypt at least once. If you don't let it encrypt first it can cause a recovery bootloop and you'll have to flash everything again.
Click to expand...
Click to collapse
How do i set those permissions? Thanks in advance
Alphita said:
How do i set those permissions? Thanks in advance
Click to expand...
Click to collapse
Use a root explorer, navigate to the file, long press it and select permissions and set them to rw-r--r--. It should prompt you to mount the system automatically to make the changes. Mine does anyhow. (See sceenshot)
Or;
In TWRP, select mount > system. Then select advanced > file manager > navigate to and select the apn file, and you'll have an option to change permissions. Select it, delete the 0000 and enter 0644 then swipe to confirm. Reboot.
Or;
Using an Android Terminal enter;
su
mount -o rw,remount /system
chmod 0644 /system/etc/apns-config.xml
reboot
Spaceminer said:
Use a root explorer, navigate to the file, long press it and select permissions and set them to rw-r--r--. It should prompt you to mount the system automatically to make the changes. Mine does anyhow. (See sceenshot)
Or;
In TWRP, select mount > system. Then select advanced > file manager > navigate to and select the apn file, and you'll have an option to change permissions. Select it, delete the 0000 and enter 0644 then swipe to confirm. Reboot.
Or;
Using an Android Terminal enter;
su
mount -o rw,remount /system
chmod 0644 /system/etc/apns-config.xml
reboot
Click to expand...
Click to collapse
Thanks! I will try this the next time i flash a rom
Would someone be so kind enough to share their BOOST apn.config.xml that the replaced the one on with that does NOT work on these GSI's?? If you do I'll follow you and hit thanks all day. ??
Here's (see screenshot) the closest I've ever gotten far as having data on a gsi. I must have the wrong xml file. I am fully aware of the process described above and have even done it multiple ways after I knew the way described and how I was adding the apn xml was correct and I have zero data.
If someone will attach their apn.config.xml, the one that they acquired data from using the boost Mobile network I'll be extremely thrilled and forever greatful to add it to the thread I made over in guides section so that in the future people can solve this issue fast and get her running and have a jolly day. ? I made that thread (I'll change the name later today) initially to consolidate as much info as I could and put it all in the op so we can be a bit more organized. I just haven't figured out anything else so I can't add to it just yet. ? This would be a great addition if someone would be so cool enough to kick me down some knowledge far as what's the correct apn.config.xml to replace the og one in gsi to get data working. I've deleted the current apn xml and replaced it with the one I have, I've overwritten it, I've tried countless times messing with the telephony.db and I obviously can't do it. Please pleeeaasee post the proper apn xml so I can get this phone going and add to op over there. @Starkiller2
I hope everyone is having a good day. It hot as **** where I'm at today. ??
I got nothing on xml. I only ever found one way to get it to work on boost, that was with the sqlite editor.
https://play.google.com/store/apps/details?id=com.dundastech.sqlitemasterlight
Starkiller2 said:
I got nothing on xml. I only ever found one way to get it to work on boost, that was with the sqlite editor.
https://play.google.com/store/apps/details?id=com.dundastech.sqlitemasterlight
Click to expand...
Click to collapse
Next time you're running a custom rom and you get data working, you can just copy /system/etc/apns-conf.xml and save it for later. You won't have to mess with any apps after that.
Starkiller2 said:
I got nothing on xml. I only ever found one way to get it to work on boost, that was with the sqlite editor.
https://play.google.com/store/apps/details?id=com.dundastech.sqlitemasterlight
Click to expand...
Click to collapse
Vague and unhelpful. Need better directions on that I messed with sqlite editor for days on end swapping out telephony.db things and never did get it going.
Did you swap both of them??
Did you swap other files in telephony.db too?
Details...?
What files exactly did you extract in telephony.db?
Vague comments never help anyone. Better to not post at all then post some two word comment with a link.
I apologise, I'm driving across country and was making an effort to help in the little time I had, but you're right, better to not try at all. Which may be why you aren't getting any answers to your questions. Some info is usually better than none and can sometimes lead you in the right direction, but you won't even get that much snapping at everyone who doesn't immediately solve the problem you have and then rage quitting when you can't do it yourself. It makes people not want to put in any effort. You have 4000 posts I assumed you could figure out how to edit apns with an app from the play store. You're right. I should absolutely stop offering any input at all, but rather I should just start *****ing and whining when I'm not spoon fed like I see so much here.
And as I have posted directions in multiple other threads, I assumed you had done at least a cursory search for your answer(as per forum rules) which would've found those posts but I was apparently wrong there as well.
---------- Post added at 07:00 PM ---------- Previous post was at 06:45 PM ----------
Spaceminer said:
Next time you're running a custom rom and you get data working, you can just copy /system/etc/apns-conf.xml and save it for later. You won't have to mess with any apps after that.
Click to expand...
Click to collapse
Thank you. That's good to know
hi, there is in the web a file apns-conf.xml to download? or sombody take us a backup? Thanks
Hey gang, I too am having issues trying to simply get mobile data working on GSI's. I have a Pixel 3a, and have tried multiple Android 10 GSI's, all of them don't allow me to use mobile data. I have not tried the apns-conf.xml trick yet, as I am unsure if that's the answer if it hasn't worked for others. Android 11 does not use an apns-conf.xml in system/etc/ so I couldn't extract it from my current setup unfortunately. Wish you all luck, post back if you get something working.
not working, moist do you have rooted phone? because only on rooted phones you can do this trick
doid1 said:
not working, moist do you have rooted phone? because only on rooted phones you can do this trick
Click to expand...
Click to collapse
I'll probably flash a ROM this weekend and pull my xml to test this. I have Telus so I unfortunately can't help with the Boost users, but can at least help confirm whether this method works or not.
ok thanks i wait, my phone seems to be dead on 4g.. says: no registration..
I tried everything imaginable and perhaps even the unimaginable .. heheheh .. but the result is always the same: no recording on the 4g, so I'm more and more inclined that it is a hardware failure or even a damage to the eeprom memory because 'I have formatted everything and the mobile phone has recharged everything correctly but it was useless ..
I tried to see that maybe it has a sim locked, but I didn't manage to enter meta mode and try to force it also because only with miracle box there is a guide ... umh ... and I do not stop until I succeed in the objective, and then the next step will be to take a complete image of another mobile phone identical to mine and copy it over it (but it is almost impractical because I cannot find anyone who gives me a full backup of this phone) and then I will brutally try to put another image of another working smartphone on it, leaving only the crucial sectors intact (system, boot, vendor, recovery, preloader, everything else I format it hehehehh) I will know..
Well I have a ROM flashed and found the apns-conf.xml, which is not included on my stock ROMs (10 or 11). Now going to flash a GSI or two and do some tests to see if I can get any data working.
Edit: Couldn't get the apns-conf.xml to work. However, I did find out the some GSI's work right out of the box for my Pixel 3A, those included AOSP 10 / 11 by Phh, and the CAOS R build. Bless, qidroid, havoc booted fine but did not have mobile data working.