Related
kexec is now fully working!
Kexec host kernel: https://github.com/willcast/ubuntu-kernel-tenderloin branch is "kexec"
Graphical bootloader: https://github.com/willcast/kexecboot
Compiled host kernel uImage UPDATED: https://docs.google.com/file/d/0B4WUjKii92l2RHJoNE93c2dVRlU/edit?usp=sharing
THE ATTACHED KERNEL PATCH (decomp_copy_atags.diff) _MUST_ BE APPLIED for ANY kernel to be bootable FROM kexec.
YouTube: http://www.youtube.com/watch?v=ko_4cOj_5iM
Kexec kernel and OS installation is best performed through SmackMe2, which is available in its own thread on this site.
I have no idea what you are saying, but keep up the great work!
Keep up the good work man , one question with you work in the future can we delete web os from the touchpad forever?
I imagine that's already possible. Use lvm to delete all the logical volumes not tied to another OS and then delete the uImage.webOS symlink. That deletes webOS, frees mostof its space and removes it from the moboot menu.
If you choose to do that, though, using the doctor to restore WEBOS will be even more difficult because you'll have to wipe out everything AND potentially need to "unbrick" your TP (using the method involving NovaCom, the small boot image ripped from the doctor and a string of LVM commands that is posted on sone or other forum.)
Lvm? Can you make a tutorial? How to remove webos from touchpad?
Thank you
Before this is complete or posted for testing, I think we will need a tutorial and links to files of how to fix the tp from a full brick such as issues with removing and restoring webos.
Great job if your boot loader works as planned we will have a full multi-boot device with a few restrictions(drivers for untested ports, etc).
Keep it up.
Sent from my cm_tenderloin using xda app-developers app
Awesome that you're resuming development castrwilliam! Can't help you with kexec though, sorry. I hang around in the Motorola Defy forums and some developers like Quarx have tried pursuing the kexec route in order to load custom kernels onto the Defy, might be worthwhile to throw him a PM. Would be great to have a more flexible bootloader!
I anyone needs a full restore, this thread helped me out. I followed the instructions when I screwed up and doctored without removing partitions. I believe WebOS Doctor handles repartitioning, so it should work:
http://forum.xda-developers.com/showthread.php?t=1426244
WORKING (but non-Kexec) Android multiboot for TouchPad.
DON'T TRY ANYTHING UNTIL YOU HAVE READ THE WHOLE POST!!
Beta 2 Updated with support for my Froyo Qcom kang.
I created a script that can install multiple versions of Android on the HP Touchpad, side by side, such that they can be selected at the MoBoot menu and operate independently. The script modifies them, on the Touchpad itself, to work with the new names for the partitions.
I want your feedback on this installer. It is used in the same way as ACME Installer but only shares one line of actual code with it (and it also uses the same binaries and config files on the initial ramdisk image, but they are Open Source so that should'nt matter.) I'll be posting this on XDA in a minute, my username there is also "castrwilliam".
If you do choose to use (TEST!) this:
- You need to create a folder on your media partition (the one that is shown when you select USB mode) with the following zips:
moboot [moboot_0.3.5.zip]
(the rest are optional but I recommend using them all so that you can help me test everything)
Froyo Test [Froyo-2.2.1-Qcom-Kang-Touchpad-a0.1-incl-gapps.zip]
CM7 alpha3.5 [update-cm-7.1.0-tenderloin-a3.5-fullofbugs.zip]
CM9 latest nightly [cm-9-xxxxxxxx-NIGHTLY-tenderloin.zip]
CM10 latest preview [cm-10-xxxxxxxx-EXPERIMENTAL-tenderloin-FOR_LIMITED_TESTING_ONLY_CAM.zip]
2.3.x gapps [gapps-gb-xxxxxxxx.zip]
4.0.x gapps [gapps-ics-xxxxxxxx.zip]
4.1.x gapps [gapps-jb-xxxxxxxx.zip] MAKE SURE not to use 4.2 gapps!
(NO Android Recovery will work yet, so don't try. It will reject TWRP and CWM at least.)
- If you already have Android and/or Moboot and/or native Linux (Ubuntu, etc.) installed:
* back up any data on your media volume. webOS should back up your apps for you.
* make both a nandroid (which WON'T work to restore in a multiboot config, but if you go back to single boot, it will be fine) and a Titanium backup [which should be portable to the same OS.]
* run ACMEUninstaller and then run SmackMe-Installer.
* if you have native Linux, backup your /etc and /home (I recommend the lovely GNU tar and gzip/bzip2). That should be the majority of what to keep.
* ALSO uninstall any native Linux you may be using after you back it up.
* lastly unzip and novacom boot the SmackMe-Installer.
If you don't already have Android, MoBoot OR native Linux, just:
* back up any data on your media volume. webOS should back up your apps for you.
* then unzip and novacom boot the SmackMe-Installer.
youtube demo:
http://www.youtube.com/watch?v=8Hhy20lzhR4&feature=youtu.be
File should be attached. Report bugs by PM'ing me, or posting in this thread
Can i remove webos with this multiboot? And stay only on android and ubuntu?
This is strictly an installer. I was going to write a webOS removal script. However, android doesn't have the needed binaries. That leaves me two options: make another thing like SmackMe to do it or do it under whatever version of native Ubuntu you are running. Either way, I really don't want to have to test it myself. If I need to I'll have to doctor my touchpad EVERY TIME I do it. That's a lot of doctoring and a lot of flash write wear. So the answer is basically "find me a dev that wants to remove webos too. They'll either make you one or beta test mine." Sorry man.
Amazing keep up the good work castrwilliam !
Strange request
Hey, does anyone here still have the 2011 Froyo (2.2.1) system dump for Touchpad? It wasn't CM6, just something that HP accidentally released and someone over at Rootzwiki dumped. I'm posting this here because I have no account and they'd think I'm a noob there. All the links are down to it and I want to try messing around with its files, just for kicks. Maaaaybe I can get it to boot, and add support for it to the SmackMe installer, so at least I can have *four* versions of Android on my touchpad.
http://forum.xda-developers.com/showthread.php?t=1234381
You know, 'cause I'm just that crazy.
Wow it's been hard to find it but i think this is the good dump:
http://download.digiex.net/Consoles/Tablets/HP-Touchpad-Android2.2.1-Disk-Images.zip
sources:
http://digiex.net/downloads/downloa...hpad-android-2-2-1-system-image-download.html
it's alive! (sorta)
Somebody on XDA found a link that I thought was dead. It was the mmc dump of someone who had Froyo leaked by HP onto their fire-sale Touchpad.
FAQ:
"Obviously nobody wants this. Everybody's running Jelly Bean."
That's exectly why I did it. My point is to do the most outrageous and downright unnecessary things possible with commonplace hardware.
"What doesn't work?"
Rotation, sound, wi-fi, softkeys (i.e. Home, Back, Menu, Search.)
"What does work?"
Camera (OH HAYULL YA), touchscreen, battery reading, power button, volume button (but it dosen't matter b/c sound is borked).
"I can haz Modded Froyo?!"
Not yet.
YouTube: http://www.youtube.com/watch?v=zX29IcTIB14
Hah awesome work, I think you hold the record of most different OS'es on one device now! It looks quite functional already.
Oh and about the "Obviously nobody wants this. Everybody's running Jelly Bean." quote, I only run WebOS and your Ubuntu 12.10 port on the TP!
As soon as I get my power button sorted out I am on this!
Sent from my slim_tenderloin using xda app-developers app
Hey everyone! Froyo here!
I've just zipped up my Froyo kang such that it will work if flashed from SmackMe, and if you're crazy enough to run it alone, hopefully also Android recovery.
sound works!!
The Wi-Fi works now BUT YOU NEED A STATIC IP ADDRESS. (problems with dhcpcd)
The buttons are hacked to work (by my new shell script: /system/bin/buttond, check it out) as follows:
Volume Down is Back
Volume Up is Menu
Center is Home.
Obviously once the audio works (if ever) that will be an issue. My embarrassing secret (at least probably to the devs here) is that I don't know Java. That makes it difficult to mod on any touchscreen buttons...
The real audio library is /system/lib/libaudioflinger.real.so and the stub one (default via a symlink) is /system/lib/audioflinger.so. Using the real one causes bootloops.
Auto rotation still won't function.
Google Apps and even Facebook are included in this ROM. (It's not CM6.) So are some potentially geeky Qualcomm apps.
Don't set up your Google Account during first boot, because it will ask you to slide the keyboard open. That sounds pretty impossible onn this device. Set it up from Settings later, and you shouldn't have that issue.
UPDATED due to install issues with actual Android Recovery. Redownload.
Download Initial Version (Alpha Minus-One-Point-One): https://www.dropbox.com/s/wcs2mra8aedj1hf/Froyo-2.2.1-Qcom-Kang-Touchpad-a0.1-incl-gapps.zip
Download Second Version (Alpha 0.2): https://www.dropbox.com/s/t1cptjj5i02epas/Froyo-2.2.1-Qcom-Kang-Touchpad-a0.2-incl-gapps.zip
^^^
I wanted to try froyo soo bad when I heard about those dumps last year (I think) lol. I still want to try it.
Now, if I read correctly, I can flash this from TWRP/CWM right?
jacobas92 said:
^^^
I wanted to try this soo bad when I heard about it last year lol. I still want to try it.
Now, if I read correctly, I can flash this from TWRP/CWM right?
Click to expand...
Click to collapse
It should work from that. I only tried with my SmackMeInstaller from the last page. That said... MAKE A NANDROID, because it WILL delete your current Android install, and if anything goes wrong (or even if it works but you see a CWM/TWRP error/warning), tell me and I'll fix it.
castrwilliam said:
It should work from that. I only tried with my SmackMeInstaller from the last page. That said... MAKE A NANDROID, because it WILL delete your current Android install, and if anything goes wrong (or even if it works but you see a CWM/TWRP error/warning), tell me and I'll fix it.
Click to expand...
Click to collapse
Ok, thanks!
Desire C people!
This stuff is good. Probably you heard about it already, now I tried it and seems to work very well, especially the memory management. Quite a sophisticated tool as far as me noob understand ugh,ugh! :cyclops:
So basically a collection of kernel and memory management tweaks, but has a lot of other like SD card tweaks and maintenance scripts which you can also schedule with SManager. And the download page has some other useful stuff like 3G turbocharger and battery calibrator.
In all it seems like a must have for DC users.
http://forum.xda-developers.com/showthread.php?t=991276
Once you used it a bit it's pretty straight forward and explains everything in details when running the script, and you have the option to "unsupercharge", but have a nandroid backup at hand.
I used two guides, but the first is for Galaxy and the second is less detailed:
http://forum.xda-developers.com/showthread.php?t=1603953
http://forum.xda-developers.com/showthread.php?t=1908505
And for Desire C, check the post below
Many thanks for nikhil16242 for recommending me this, many scripts are in his Customiser already, he would have integrated the whole V6 Supercharger, but Aroma doesn't like it. That would be awesome though!
All credits to zeppelinrox for these truly awesome scripts:good:
One wonders why android doesn't have some of them by default.
V6 Supercharger Install Guide for Desire C
~ v6 supercharger install guide for desire c ~
aka how I have done it, so it's not an absolute one.
zeppelinrox's original thread is here.
Originally Posted by zeppelinrox
What's it do?
It makes your phone FAST... super snappy with better multitasking!
It rearranges and fixes the OOM Groupings and Priorites and lowmemorykiller values.
So basically, it's a COMPLETE MEMORY MANAGEMENT FIX!
It's the ONLY one of it's kind
NO LAUNCHER REDRAWS, faster than ever, multitasking is better... why?
Because it works with the lowmemorykiller and letting it work the way it's meant to work.
Also, because of the rearrangement, it works the same on all roms!
The problem with using minfree tweakers like AMM or AKMO is that it doesn't work the same on all roms.
Secondary apps may be in slot 3 on some roms but in slot 5 in others!
That's why you hear people comment "I tried AKMO but it didn't do anything..."
Most likely it didn't do anything because the apps weren't sitting where they were expected to be.
So fasten your seat belts and enjoy the ride!
Click to expand...
Click to collapse
NOTE: Delete all conflicting scripts from init.d folder, otherwise it will be laggy and annoying!
Conflicting scripts I have found so far:
- all the thunderbolt except miuiCMremount (V6 does most of these like sd card tweaks and zipalign anyway)
- mpengine and laserdroid (also from /system and /xbit)
If you don't know which scripts are from where, unzip nikhil16242's Customiser and check the folders.
Also do not install everything on one breath. Do it gradually (v6 - nullifier - engine flush and so on), test with a demanding game like Temple Run, so you can opt out any possible problems.
What you need:
All V6 scripts are here.
ScriptManager [download]
- If you have stock ROM:
Download Supercharger Starter Kit from the V6 scripts, on the page it's explained how to use it, couldn't be more simple:
Using SuperCharger Starter Kit (Prepares your ROM with the fixed su binary, zipalign binary, sqlite3 binary and busybox v1.19.4... and does NOT include the V6 SuperCharger scipt):
- Extract the zip to the root of the sdcard and it will all be in /sdcard/SuperCharger_Starter_Kit
- With Script Manager, just run StartMeUp.sh to install everything at once.
- Or, in terminal do: su, enter, sh /sdcard/Super*/Start*
Click to expand...
Click to collapse
All the rest is the same as the following:
- If you are on custom ROM:
then busybox is already installed, so you don't need the starter kit.
I. SUPERCHARGER INITIAL SETUP
The script guides you through the process, so watch it closely. In the setup it automatically determines some optimal settings, but you can change them any time.
Step 1. Put the latest V6_SuperCharger_for_Android-UpdateX_XXX (X is the actual version number) on your SD card
Step 2. In SManager:
--- 1. make sure you have granted SuperUser access, and set browse in root (long press recent apps button > Menu > Advanced > Configuration > Browse as root), but if you used before it's already set
--- 2. open the script on your SD card, set the properties to: Favorites (star icon), Root (green android skull icon) and tap Run to execute the script installer.
Step 3. A bunch of text start to come up, watch it closely, it guides you through the installer. Home Locked in Memory? n (No) and press enter and another enter to continue to drivers console.
First it goes to Pit Stop to set Driver Options, where you will be asked for Scroll Speed but also various tweaks which can improve the performance. Go through each and decide if you want them or not (I enabled most of them in he script)
When asks Use Build.Prop? : n (No) to use local.prop - I chose this, it sounds safer.
Step 4. You need to patch services.jar. It can be done automatically or manually (however the script recommends manual, and when I did it automatically for the first time, it did not backup services.jar and could not unsupercharge, only by restoring it from the rom .zip) Don't worry, doing it manually couldn't be easier:
In the Driver's Console choose:
25. Jelly ISCream Parlor {Install services.jar}Choose manual mode, which will take you to the [RC9] ULTIMATIC RC6! [EXE]-=Ultimate Jar Power Tools=-With Maximum MultiTasking Mods! thread in your default browser, from which the essential instructions are the following:
--- 1. Connect your Android to your PC with Android Debugging ENABLED and Mass Storage DISABLED so your device has access to your sdcard. I just put it in Charge Only mode...
--- 2. Download the latest Ultimatic_Jar_Patcher_Tools_XXX_Windows.exe.zip to your PC - Windows exe is NOT zipped. Just remove the .zip extension!
--- 3. Start the exe and follow the instructions in the script. It will ask you which mode you want to use your Launcher in: Hard To Kill Launcher, Die-Hard Launcher or BulletProof Launcher. Choose Hard to Kill (HK), it is the best for our device.
You can add Maximum Multitasking mod as well, according to tests it works fine, but I did not install it in the beginning, then didn't bother
If follow the instructions in the script till the end, your services.jar should be patched, and the script will confirm this.
--- 4. On your phone in V6 script, you are still in the menu 25., right? Press x (exit), which takes you again to the Driver's Console. Choose: 32. SuperClean & ReStart! (ie. Wipe Dalvik Cache & Reboot)
Step 5. Press enter to return to Drivers Console. Pressing enter will automatically run Quick V6 Cust-OOMizer and will calculate optimum SuperMinFree values
Apply SuperMinFree Calculator Settings? : y (Yes) to apply calculated MinFree (low memory killer - lmk) values so you don’t need to choose, but you can change it after completing the initial setup and then running the script again in menu point:
10. Quick V6 Cust-OOMizer.Or if you type n (No), you can choose manually right away, doesn't make a difference. If it was set automatically, go to step 5. and come back later if you want to change it:
For a low memory device like ours, 512 HP recommended, these are the options in menu points:
5. UnLedded (Multitasking) {8,14,40,50,60, 75}
6. Ledded (Balanced) {8,14,55,70,85,100}
7. Super UL (Aggressive) {8,14,75,90,95,125} - it does 130-140MB
However the best setting recommended me by educated colleague nikhil16242 and I tried is:
10 15 25 45 80 100 (slot1 - slot2 and so on)
with this I always have 120-130MB free RAM and no lag, Temple Run is butter smooth Basically it kills processes below that level (but still prioritises them - really smart script), which means less multitasking, but two-three apps that I needed in multitask were working perfectly, I didn't notice any difference, but snappier phone.
Try whichever suits you best.
Step 6. Press Enter - this action will backup Re-SuperCharger files to SD Card, in case you want to restore your Supercharger settings.
Step 7. SuperClean & ReStart : y (Yes), this will wipe your dalvik-cache so bootup time will take longer this time.
Step 8. After restart, open SManager and:
--- 1. Go to /system/etc/init.d (you can bookmark it for later access)
--- 2. Tap on S99SuperCharger and set the following properties:
------ a. Favorites (star icon)
------ b. Root (green android skull icon)
------ c. Start on Boot (gear icon)
--- 3. Tap on Save, close Script Manager and Restart your phone
NOTE:
If you don’t follow step 8., you will get an error the next time you run the script and it will show you owner’s handbook on your default web browser.
II. OOMIFIER & LAUNCHER
If you patched services.jar and choose SuperMinFree values manually then you have this already. If not, then:
OOM Grouping Fixes will determine which are the more priority apps and keeps them alive better. The Launcher mode determines how easy it will be for the mem killer to kill the launcher in case of low memory. Works flippin good, I'm tellin ya
Step 9. After restart, open SManager and Run V6_SuperCharger_for_AndroidX_XXX script again (make sure you run it in root [skull icon] but not boot [gear icon])
--- 1. SuperCharger will run Test Drive, just wait for it to finish and then continue to the Drivers Console.
During the install it should set the optimal mode automatically, which was BulletProof for me, probably because I chose the aggressive memory kill (sounds convincing lol) mode. Anyway, this means the Launcher will never get killed, about which some say it's not recommended.
--- 2. So on the Drivers Console you can choose between these launcher modes in the menu points, in reverse order of toughness:[/INDENT]
11. OOM Grouping Fixes + Hard To Kill Launcher
12. OOM Grouping Fixes + Die-Hard Launcher
13. OOM Grouping Fixes + BulletProof LauncherEventually I changed it to Hard To Kill, but it's up to you.
--- 3. Hard To Kill? : y (Yes) to apply
Press Enter to go back to Drivers Console
III. NITROLAG NULLIFIER
It's an experimental feature, don't know what it does exactly, but I switched it on Everything is flawless for me since, so I say go for it.
Step 10. In the Drivers Console, select:
21. Nitro Lag Nullifier {Experimental}Enter (N)ullify, (U)n-Nullify, E(X)it: N (Nullify) to apply Nitro Lag Nullifier
After applying Nitro Lag Nullifier, press enter to go back to Drivers Console.
IV. 2 in 1 ENGINE FLUSH
It flushes the RAM cache so the phone doesn't get sluggish after days of usage.
The 2 Modes are: -=Fast Engine Flush=- for instant flush and -=Engine Flush-O-Matic=- for automation.
Step 11. In the Drivers Console, select:
17. Engine Flush-O-Matic {ReCoupe RAM Booster}Continue and drop all file system caches? : y (Yes) to clear system cache on RAM
It will ask you (gives you 20 s to decide lol) if you want to automate it, so you don't need to schedule it in SManager. If yes, you set an interval between 1-24, which counts as hours, so it determines how frequently flushes the RAM cache. Some people set it for every hour, so why not, I did that too. Hmmm that was good
After Engine Flush, press enter to go back to Drivers Console.
V. SUPERCLEAN AND RESTART
Wipes dalvik and reboots the phone, you need that before you start to using it.
Step 12. In the Drivers Console, select:
30. SuperClean & ReStart {Wipe Dalvik & Reboot}Do you want to SuperClean & ReStart now? : y (Yes)
VI. VERIFY SUPERCHARGER STATUS
Step 13. After restart, open SManager and run V6 SuperCharger again. You should see Supercharger Level: 100%, then you are good to go.
As the script rolls it indicates your settings so you know what is set and what's not. You can check out the other menu points, and number:
27. Owner's Guide {Open !SuperCharger.html}This opens the... Owners Guide! ...in the default browser, you can wise yourself up about the different options.
VII. KICKASS KERNELISER
Downolad the script and launch it the same way as V6. Look at the text, wisen up and choose KickAss (k).
It will place S98KickAssKerneliser script in init.d, skull it and gear it, and reboot the phone.
TIPS & TROUBLESHOOTING
If you are only 75% supercharged, that probably means MinFree (the mem killer) settings doesn't stick (so you see you have the usual low amount of free RAM). Check the S99Supercharger script in SManager if it has the root and boot privileges (In /system/etc/init.d or Long pressing recent apps button > Menu > Scripts), set them again if they were not and reboot the phone. If it's not set again, open Owner's Guide to figure out what's next, but if you followed the steps properly, you should be fine.
Check the note in the beginning of the post for deleting conflicting scripts!
All the scripts and backups are in two places:
1. on SD card /V6_SuperCharger folder
2. /data/V6_SuperCharger
and the logs and manuals under them.
When you run a script in SuperCharger, it places a separate one in the folders, so you can make widgets with SManager for fast access:
- Long press home screen, select SManager from widgets, locate the SuperCharger folder and select the script you want to have at hand.
- For example for quick change between MinFree modes, the scripts will be in V6SuperCharger/PowerShift_Scripts (you need to run them in SuperCharger first in order to be created separately, or if you installed the additional V6 scripts (or something like that) in nikhil16242's Customiser before, they will be in init.d already).
You'll know you have chosen a suitable MinFree mode if if you play Temple Run with no lags at all shaboooooom!!!!
See, wasn't too hard and you are SuperCharged now.
Enjoy it like a Boss!
Kudos to CarlDeanCatabay and Androidmarketuser for the guides that helped me and are in the OP.
And most of all to zeppelinrox for V6 SuperCharger :good:
Started reading looks great but by ekk I'm finding it hard to get my old head round some of it. Usually when I'm like this I have to read read read till it starts making sense .So will prolly take me a bit of time.
Re: [Script][TWEAKS] V6 Supercharger
This script is really awesome once you get everything done properly,just takes a while to read the entire OP though .
Ram management is another very essential thing to be done on a low ram device like ours.Stock ram management seems to be poor imo so I use this and the results are truely amazing .
Sent from my HTC Desire C using xda app-developers app
thanks
neoyoli said:
Desire C people!
This stuff is good. Probably you heard about it already, now I tried it and seems to work very well, especially the memory management. Quite a sophisticated tool as far as me noob understand ugh,ugh! :cyclops:
So basically a collection of kernel and memory management tweaks, but has a lot of other like SD card tweaks and maintenance scripts which you can also schedule with SManager. And on the download page has some other useful stuff like 3G turbocharger and battery calibrator.
In all it seems like a must have for DC users.
http://forum.xda-developers.com/showthread.php?t=991276
Once you used it a bit it's pretty straight forward and explains everything in details when running the script, and you have the option to "unsupercharge", but have a nandroid backup at hand.
I used this detailed guide, but it's for Galaxy so use your brain
http://forum.xda-developers.com/showthread.php?t=1603953
Here's is an other one, just in case, but less detailed:
http://forum.xda-developers.com/showthread.php?t=1908505
Many thanks for nikhil16242 for recommending me this, many scripts are in his Customiser already, he would have integrated the whole V6 Supercharger, but Aroma doesn't like it. That would be awesome though!
All credits to zeppelinrox for these truly awesome scripts:good:
One wonders why android doesn't have some of them by default.
Click to expand...
Click to collapse
works great
guide updated
Hey guys, well actually i have an issue while i'm trying to run the v6 supercharger. It succesfully passes the drive test but it gets stuck at the next step. it throws me a lot of lines like 'find system/lost+found/ Too many open files' and i can't get rid of it, please help
this guide is quite old now, supercharger has been updated since numerous times. if you have a nandroid backup restore it, if not then ask zeppelinrox in his original thread. also supercharger does automatic backup before you apply the settings, which can be restored from the menu if something goes wrong, try it.
This is place where you can come and ask questions regarding support as well as any other general discussion for the Null rom. Please keep the development thread to just that DEVELOPMENT. The developer of this rom is here to develop and not here to answer your questions because you can't take the time to figure out the answer yourself. This will be a community driven thread. Therefore, if you feel something needs to be added to the OP please mention me in a post and I'll take a look
If you need to download the rom free to stop by the dev thread to download. However, if I see you ask a question in here and then go to that thread to ask the same question I will be handing out infractions. Please consider this your only warning.
On a side note, I'll be transferring the OP of this thread to a person with this device in due time. However, for the moment this needed to be created. If you are willing to take the OP from me please feel free to send me a PM. The only requirement that I would have is that you keep it updated properly.
FAQ / IT DOESNT WORK ! WAH
INTERNET ACCESS
GO INTO "FULL SETTINGS -> BLUETOOTH -> SELECT YOUR PHONE SETTING ICON (ON THE RIGHT OF PHONE NAME) -> TICK INTERNET ACCESS".
ENSURE BLUETOOTH TETHERING IS ENABLED ON YOUR PHONE BEFORE HAND OBVIOUSLY.
*NOTE* ENSURE YOUR MOBILE DEVICE SUPPORTS TETHERING, US VARIANT PHONES HAVE RESTRICTIONS INPLACE. REFER TO THE US INTERNET TETHERING THREAD.
*NOTE 2* BLUETOOTH TETHERING DOES NOT AUTO RECONNECT, INSTALL THIS THIRDPARTY SOLUTION ON YOUR GEAR TO ENABLE AUTO RECONNECT.
PLAYSTORE / GOOGLE ACCOUNT MANAGER HAS STOPPED..
VERIFY YOU HAVE A BLUETOOTH INTERNET TETHERING CONNECTION ESTABLISHED BEFORE ATTEMPTING TO ADD A GOOGLE ACCOUNT.
MUST NOT BE USING THIRD PARTY TETHERING, EG. PDANET.
HOW DO I FULL WIPE?
BOOT INTO RECOVERY MODE AND SELECT THE "RECOVERY" OPTION. DO THIS AFTER FLASHING THE ROM
UNABLE TO WAKE GEAR WHILE IN PHONE CALL
THIS IS CAUSED BY THE HOME BUTTON REMAP MOD, THE HOME BUTTON MUST BE PRESSED IN ORDER TO WAKE THE GEAR UP IN THIS STATE.
ONLY WORK AROUND IS TO EITHER USE THE WRIST WAKEUP GESTURE OR DISABLE THE HOME BUTTON REMAP MOD.
*NOTE* BY DISABLING THE HOME BUTTON REMAP MOD, THIS WILL DISABLE THE ABILITY TO MANUALLY LOCK THE SCREEN WHILE USING A CUSTOM LAUNCHER.
DOUBLE TAP BRIGHTNESS/SOUND TOGGLE HAS DISAPPEARED
THIS IS CAUSED BY USING THE FULL SYSTEM UI, SIMPLY PUT IT REPLACES THE DOUBLE TAP WINDOW WITH THE NOTIFICATION SHADE. BY USING GRAVITYBOX YOU CAN ADD ADDITIONAL TOGGLES LIKE BRIGHTNESS & SOUND TILES TO THE FULL NOTIFICATION SHADE.
OTHERWISE SIMPLY REFLASH THE ROM WITH THE FULL SYSTEMUI OPTION UNTICKED.
SCREEN FLICKERING/GITTERING
THIS IS CAUSED BY THE INITIAL BOOTUP, REBUILDING THE CACHE AND INITIALIZING ALL THE APPS. GIVE YOUR GEAR A FEW MINUTES TO SETUP AND RESTART.
SCREEN UNLOCKS TO NOVALAUNCHER PAGE PREVIEW?
GO INTO "NOVA SETTINGS -> GESTURES -> HOME BUTTON -> NONE".
ENABLE DEVELOPER SETTINGS / USB DEBUGGING
GO INTO "SETTINGS -> GEAR INFO -> ABOUT GEAR", TAP SOFTWARE VERSION 10 TIMES.
ENABLE UNKNOWN SOURCE APK INSTALLATION
GO INTO "FULL SETTINGS -> SECURITY -> TICK UNKNOWN SOURCES".
ENABLE MTP
GO INTO "FULL SETTINGS -> STORAGE -> MENU BUTTON (TOP RIGHT OF SCREEN) -> USB COMPUTER CONNECTION -> MEDIA DEVICE (MTP)".
WATCH STYLER NOT WORKING
ENSURE ITS SELECTED AS THE DEFAULT WATCHFACE IN GEAR MANAGER.
IF CLOCK FACE DOES NOT UPDATE UPON CHANGING, RESTART GEAR.
DOUBLE CLICK HOME BUTTON DOESNT WORK ON TOUCHWIZ LAUNCHER !
*NOTE* DO NOT DO THE FOLLOWING IF YOU ARE USING NOVALAUNCHER, YOU WILL NOT BE ABLE TO MANUALLY LOCK YOUR GEAR.
*NOTE 2* YOU CAN SIMPLY REFLASH THE ROM WITHOUT WIPING AND DISABLE THE HOME BUTTON REMAP MOD.
NAVIGATE/PULL THE FOLLOWING FILE FROM YOUR GEAR: /SYSTEM/USR/KEYLAYOUT/GPIO-KEYS.XML
EDIT IN A TEXT EDITOR SO IT LOOKS LIKE THE BELOW:
Code:
key 115 VOLUME_UP WAKE
key 114 VOLUME_DOWN WAKE
key 116 POWER WAKE
[B]key 172 HOME WAKE[/B]
edit
Amazing. This thread is very much needed song as how the dev thread keeps getting cluttered with posts that wouldn't be there if some one would have read
sent from my Note 3 or Galaxy Gear
Yeah this thread is an awesome idea to leave the general discussion and support issues out of the other thread.
Whenever I select "recovery" it doesn't give me an option to install the rom?
I followed the steps for the root and the add the .zip to my SD card on the phone. When I select the option for recovery it just does a system restore on it. Any help?
You need to flash twrp first
sent from my Note 3 or Galaxy Gear
feature request
[what about to include support fpr AquaMail client?
I'm using it and I think it is the better at the moment
The developer could be interesting....
Just a quick (somewhat noob) enquiry about the Gear and what this ROM can do for it, as I'm thinking of picking up a Note3 + Gear from work (Vodafone), as the watch is free.
Firstly, I hate Touchwiz with a passion! I don't wish for anyone to read that in an angry way, but I'm really not fond of the colours, themeing, etc. of that particular UI. I much prefer vanilla Android and, as such, would look to root the Note3 and install CM or an equivalent on it.
Would I then lose any functionality of the Gear? Can the GearManager APK be installed on a non-TW ROM?
I'll need a bit of an idiot's guide for the whole thing, but it's nothing I can't research.
Pepski said:
Just a quick (somewhat noob) enquiry about the Gear and what this ROM can do for it, as I'm thinking of picking up a Note3 + Gear from work (Vodafone), as the watch is free.
Firstly, I hate Touchwiz with a passion! I don't wish for anyone to read that in an angry way, but I'm really not fond of the colours, themeing, etc. of that particular UI. I much prefer vanilla Android and, as such, would look to root the Note3 and install CM or an equivalent on it.
Would I then lose any functionality of the Gear? Can the GearManager APK be installed on a non-TW ROM?
I'll need a bit of an idiot's guide for the whole thing, but it's nothing I can't research.
Click to expand...
Click to collapse
No. Sadly not.
Or at least not with all the bells and whistles working.
I actually am testing CM11 on my note 3 as I type. I was wondering if someone could link me to the latest gear manager so I could test how it works.
Sent from my Note 3 w/ CM11
ktetreault14 said:
I actually am testing CM11 on my note 3 as I type. I was wondering if someone could link me to the latest gear manager so I could test how it works.
Sent from my Note 3 w/ CM11
Click to expand...
Click to collapse
Here's 2 versions. The latest and the previous one, a lot of people are having problems with the latest, and even Samsung supposedly admitted it was bugged and they were going to release a new one. The previous version seems to work fine for people, and there's no real functional updates on the latest one anyway, so you might prefer it.
Latest version - 1.5.121601
Previous version - 1.5.120903
I couldn't get cm11 to download the necessary apks for gear manager so I restored a tw backup and backed up the apks themselves. When I went to restore them the only ones that would not restore were the weather and svoice. It is paired now with gear manager running in the notifications. Still testing out what works and what doesn't
Sent from my Note 3 w/ CM11
Running 16, removed Ms. Pac-Man for running too slow on the Gear, everything's running smooth.
Sent from Spaceball One.
I have nexus 5 rooted and running null16, could anyone please point me out how to make gear manager to work?has anyone made notifications work? so far i can just make calls from it and syncs the time.I have read everywhere but nothing works so far and i can't seem to find a reliable sorce of information. If we could make something like an app and null to be modified to work with that so we lose gear manager dependency i belive that would be a game changer . Fomey i will donate something pretty soon as i allways apreciate work from people creative like yourself .
EDIT: 15 AUD for you Fomey, thank you for your work !
reboot after install of null_16
i have attempted several times now to install the null_16 on my galaxy gear. after each time i attempt to go into the recovery mode to actually install it, it reboots and resets the device. i have read numerous times to flash the null_03_TWRP2.7.tar.md5 file and i have done this with odin and received a pass at the top left of the odin program and then it reboots the galaxy gear. i then install the null_16 file on the root of the sd card directory with wondershare mobilego (left zipped as noted in several videos i have watched) after this i remove device from charging device and this is when i try to go to recovery modeto install. after getting to recovery and holding power button for approximately 3 seconds and release this is when it reboots and has reset itself. any help would greatly be appreciated and yes it is rooted with supersu. I am sure i am doing something wrong but not sure what.
ernie36564 said:
i have attempted several times now to install the null_16 on my galaxy gear. after each time i attempt to go into the recovery mode to actually install it, it reboots and resets the device. i have read numerous times to flash the null_03_TWRP2.7.tar.md5 file and i have done this with odin and received a pass at the top left of the odin program and then it reboots the galaxy gear. i then install the null_16 file on the root of the sd card directory with wondershare mobilego (left zipped as noted in several videos i have watched) after this i remove device from charging device and this is when i try to go to recovery modeto install. after getting to recovery and holding power button for approximately 3 seconds and release this is when it reboots and has reset itself. any help would greatly be appreciated and yes it is rooted with supersu. I am sure i am doing something wrong but not sure what.
Click to expand...
Click to collapse
Read.
ernie36564 said:
i have attempted several times now to install the null_16 on my galaxy gear. after each time i attempt to go into the recovery mode to actually install it, it reboots and resets the device. i have read numerous times to flash the null_03_TWRP2.7.tar.md5 file and i have done this with odin and received a pass at the top left of the odin program and then it reboots the galaxy gear. i then install the null_16 file on the root of the sd card directory with wondershare mobilego (left zipped as noted in several videos i have watched) after this i remove device from charging device and this is when i try to go to recovery modeto install. after getting to recovery and holding power button for approximately 3 seconds and release this is when it reboots and has reset itself. any help would greatly be appreciated and yes it is rooted with supersu. I am sure i am doing something wrong but not sure what.
Click to expand...
Click to collapse
Download mk7 for your country.... I don't care if you are already on it just do it! Flash with Odin then flash twrp recovery..... Use adb to boot to recovery....... Trust me it works!
Sent from my Note 3 SM-N900A rooted by Designgears
OMG i got it running!
thanks so much for all the work done with this rom... Everything seems to be running perfect...
At first i couldn't get it to flash properly... I was trying everything. Took hours to initially get the recovery going. It ended up being a driver issue and after a lot of reading and troubleshooting i was finally able to get it up and running.
One question that i have that i couldn't find the answer too... Is there any way to have the watch widget (either the stock clocks or watch styler) appear as a full screen widget without the launcher or the status bar at the top... yet keep the status bar and launcher on the other pages? I am assuming that i can't do it after reading countless of pages... Because i do like the full screen watch face.
Thanks again for all the hard work!
---------- Post added at 09:05 PM ---------- Previous post was at 09:00 PM ----------
eroracing said:
Download mk7 for your country.... I don't care if you are already on it just do it! Flash with Odin then flash twrp recovery..... Use adb to boot to recovery....... Trust me it works!
Sent from my Note 3 SM-N900A rooted by Designgears
Click to expand...
Click to collapse
I had to follow this step in order to get the recovery to stick. No matter what i did including flashing the stock recovery then flashing twrp i couldnt get it going until i did this:
almulder1092 said:
Installing Null_ TWRP: (Version as of this tutorial is Null_ 03 TWRP)
Thanks to fOmey for this Null_ TWRP
Installing Null_ TWRP:
Preparation:
Download Null_ TWRP - fOmey
READ THE NULL_ TWRP Original Post
Installation:
Put your Gear into Download Mode
Connect your Gear to you PC.
Open Odin
Click on the PDA Button
Locate the Null_ TWRP file and select it. (It should be a .md5 file, if it is zipped, then unzip it)
Press Start
Once it is completed it will reboot the gear.
Null Quote:
If you find the recovery is not sticking & your Gear wipes when attempting to access recovery after flashing, you must root your Gear prior to installing TWRP again & Run the following commands in ADB:
*NOTE* You will gave to accept a supersuser request popup when executing "SU" command
*NOTE 2* Probably a good idea to run this prior to first installation (To save time)
Code:
$ adb shell
$ su
# mount -o rw,remount /dev/block/mmcblk0p20 /system
# rm /system/recovery-from-boot.p
ADB stands for Android Debug Bridge
If needed "ADB" can be found here on xda - Thanks to shimp208
.[/CENTER]
Click to expand...
Click to collapse
gypsydigi said:
OMG i got it running!
thanks so much for all the work done with this rom... Everything seems to be running perfect...
At first i couldn't get it to flash properly... I was trying everything. Took hours to initially get the recovery going. It ended up being a driver issue and after a lot of reading and troubleshooting i was finally able to get it up and running.
One question that i have that i couldn't find the answer too... Is there any way to have the watch widget (either the stock clocks or watch styler) appear as a full screen widget without the launcher or the status bar at the top... yet keep the status bar and launcher on the other pages? I am assuming that i can't do it after reading countless of pages... Because i do like the full screen watch face.
Thanks again for all the hard work!
---------- Post added at 09:05 PM ---------- Previous post was at 09:00 PM ----------
I had to follow this step in order to get the recovery to stick. No matter what i did including flashing the stock recovery then flashing twrp i couldnt get it going until i did this:
Click to expand...
Click to collapse
You cannot do what you are asking.... But you can set clock widget. Use Nova settings to hide notification bar, dock and scroll indicators then use gesture and button settings to create gesture to accommodate just about anything! I have swype down to open notification bar..... Swipe up open notification app.... Double tap opens app drawer and 2 finger Swipe up opens my dialer! Just set widget long press and resize to full screen. You may have to adjust colums and rows in Nova settings to accommodate whatever widget you are using in order to center properly. Hope this helps!
Sent from my Note 3 SM-N900A rooted by Designgears
On the newest release (16) there is support for custom boot animation and includes the null boot animation. Is that a part of the aroma installer or is the custom null boot animation a part of the rom that you cannot remove? I'd rather stick with the stock if you don't mind.
Root SM-T707A on Lollipop with SuperSu - Xposed & Debloated - Part II
Where are we right now?
* Part I: Flash Stock Lollipop 5.0.2.
* Part II: Gain Root access for Lollipop with SuperSU. <---- YOU ARE HERE!
* Part III: Flash Xposed Framework thru Flashfire.
* Part IV: Debloat the tablet from both AT&T and most of Samsung stuff.
* Part V: Improve usability and aspect with Xposed Modules.
Once again, some words of our sponsors: NO, I'm NOT resposible for any consequence originated from the use of this guide, being that the death of your tablet, or your smart tv, the Panama Papers or Luis Suarez just playing rough with Filipe Luiz's foot. Whatever happens to your tablet, it's ON YOU.
Introduction (PLEASE READ!):
This guide works as a continuation of Part I, so we assume you flashed KitKat and applied Lollipop updates as described.
If you are already on Lollipop and have several weeks using it, of course you can try this guide, but I STRONGLY SUGGEST to start from zero, backup your files and use the guidelines on Part I of this guide.
Part II: Gain Root access for Lollipop with SuperSU
IMPORTANT - During the first boot on our brand new lollipop, don't try to connect to your WiFi and remove your SimCard if availble before even selecting any option. We don't want any internet at this time.
Our first move in Lollipop is to Reject all the AT&T offers..
Then accept terms of Samsung EULA (and hit No Thanks below)...unless you want to share information with Sammy.
Then you can put your name (I didn't), it' s up to you.
Disable the 3 checkboxes for location services (you can enable this later).
Then skip the Samsung Account creation and hit also Next on my "Find my mobile" screen without doing nothing.
Finally, you'll reach the Android Desktop.
Setting the stage for rooting with KingRoot
Still avoiding any conection to the internet, go to your apps and tap Settings.
Before doing nothin, I strongly suggest you change your language to english in case you use another.
If your first language is English, you're good.
If it's not, you can change it on General TAB, then "Language and Input".
After this, tap the Device tab, choosing then Display option on the left.
Choose Screen timeout and select 10 minutes.
Now select Lock screen on your left and Screen lock on your right. Tap "None".
Now go to "General" tab and tap "Security".
Enable the Unknown sources checkbox and press OK on the popup.
Press home button. Now you can connect to your Wifi.
The moment you got Internet, Samsung will start forcing some updates on your tablet.
At the same time, several Google popups will ask you to "regularly check device for security".
Decline them all the time!
There is a "Games" app that loves to open itself without asking
When that happens, it will introduce you to an agreement that you will REJECT.
If it doesn't show, better. But it will eventually.
Now enter the Play Store and Log in with your credentials.
Accept the playstore conditions when prompted. If you are kicked out of the app just enter again.
Still inside Playstore, now swipe from your left side border to gain access to the menu.
Tap "My Apps" and use the "Update All" button on the right.
Accept all APP Permisions (seven times in my case).
The update process will start. This will take some time so BE PATIENT and do nothing else.
When everything is updated, you'll notice some warning on your status bar.
Swipe down your status bar. It will ask several times to Update Google Play Services.
Tap any of update offers for Play Services. Playstore will open again offering the update.
Hit Update and Accept. When the update of Google Play Services is finished, hit the Open button.
You gain access to Google Settings. Tap Security.
Disable "Remote locate this device" - "Allow remote lock and erase".
Disable also "Scan device for security threats" and "Improve harmfull app detection" (unless is greyed out).
Hit the home button and go back to desktop.
Installing KingRoot
For the next step, you need to download these files on your PC:
* Kingroot V4.90
* RemoveKing
Copy them on your tablet's internal memory. Specifically on the root of your internal memory. If you copy them inside a folder, later commands will fail.
Back to your tablet's desktop, look for the folder icon on the bottom left corner. This will open the Samsung File Manager. Look for "Device Storage" on the left column. If you copied the files correctly, you'll find both on the right pane of the display. Extract the RemoveKing.zip file by tapping it and clicking "OK". A RemoveKing folder will appear on the root of your filesystem.
Now open the Kingroot V4.90 file. Hit Next and then Install.
If a google warning appears citing - "Installation blocked". Hit "Install anyway" (unsafe).
If it doesnt, just hit Open. A blue screen shows up with the legend "ROOT auth".
Swipe upwards twice (assuming you're holding your tablet in portrait).
Now hit the "Try it" button. The app will verify root status in a matter of seconds.
Now tap the "TRY THE ROOT" button at the bottom.
When the root is sucessful, you'll be asked to "Forbid Knox".
Tap Cancel and press the home button. Now you are rooted with Kingroot.
Installing and preparing Terminal Emulator
Now that we are rooted, enter the playstore and install the app "Terminal Emulator for Android". Open it. You'll notice some small font selected so, hit the 3 dots on the right upper corner and go to preferences. On Font Size choose 24 pt. Hit the back physical button of the tablet. Now the "white letters" become readable. And it shows something like:
Code:
klimtlteatt:/ $
Next type the following and hit enter:
Code:
su
A Kingroot popup will ask for root permission. Tap "Allow".
Now the $ symbol will change for #.
Next you hit the HOME button to exit the app briefly (don't close the app in any other way, just hit the HOME button).
Uninstalling KingRoot
After that, go to your apps and enter the KingRoot app.
Now tap the 3 dots on the upper right corner and select "General Setting". Disable "Smart Authorization", then disable "Enable Root Authorization". Finally choose below "Uninstall KingRoot". Hit Continue. Uncheck "Backup Root" when prompted and hit OK. When all is over, you're back to the desktop. Go back again to your apps and uninstall Purify.
Applying the Scripts
Open again Terminal Emulator app (thru the app Icon) . Now we need to hit a couple of scripts by moving first to our extracted folder by entering the following command on the terminal (plus enter):
Code:
cd /sdcard/RemoveKing/
To run the first script type (then press enter):
Code:
./step0.sh
It just takes 3 seconds, then type the following and press enter:
Code:
./step1.sh
This last script will ask for a confirmation during its process.
Type just an "y" and hit enter: (WARNING, the Y won't appear on your display after typing it)
Code:
y
You'll notice a bunch of errors, don't mind them.
Installing SuperSU
Now hit the home button and go to the play store.
Search and Install SuperSU (free version). Open it. Choose Expert.
The app will ask "The SU binary needs to be updated, continue?".
Hit Continue and then choose "Normal" when asked on the next popup.
You'll receive an "Installation Sucess!". Tap the Reboot option.
Congratulations! You are now rooted with SuperSU.
After rebooting, enter the Terminal app once more, and tap the X on the right upper corner and hit OK.
That will finish the current terminal session.
If you're interested in getting Xposed Framework, go to part 3 of this guide.
If you're just interested in debloating the SM-T707A and improve its performance, go to part 4 (Soon).
Part 5 is where I discuss the modules I'm using on Xposed and also some Playstore apps to improve functionality, and remove as much Touchwiz as possible, while also working on better battery life (Soon too).
Final Considerations (suggested reading - not mandatory)
While this guide may seem easy to carryout, it took me almost a month to get SuperSu to work on Lollipop.
I'm no coder (a soon to be Certified Public Accountant), and the real magic to pull this off was to try many combinations of different app versions, different situations with google services and several strategies with the script and superSU. In fact, most of KingRoot versions don't work on this tablet to get root, also tried SuperSume app from the playstore. The same could be said for KingoRoot (don't confuse it with KingRoot), it worked but I couldn't remove it without losing root.
Why I'm telling you this? Because using KingRoot and similar apps to root this tablet, your mileage may vary while doing it. In fact, even while applying my first two guides there's a respectable chance of KingRoot tool failing to root your tablet. If you followed this couple of guides to the last comma, your chances of success are very close to 100%. But I have noticed in similar Galaxy Tab S threads, that the use of KingRoot and KingoRoot to achieve root is just a matter of using the root tool many times until it works, and I wanted to avoid you guys going thru that. To take sucess rate as close as it gets to 100%, we took all of this steps. They were included to avoid many failures. I believe they're are 99% flawless to achieve root on Lollipop with SuperSU.
Also, the second script won't remove many KingRoot files, because it was thought for KingoRoot on KitKat.
I have to give myself more time to develop something that could really clean up the last traces of KingRoot.
Special Thanks
* @chixvicious - For showing how to achieve the same over KitKat and KingoRoot instead.
* @bakageta - For creating these scripts for the Alcatel smartphone over KingoRoot.
* @Kingxteam - For developing KingRoot to allow us to root our device.
Oh wow, I had forgotten all about those scripts. Glad to see someone getting some use out of them.
bakageta said:
Oh wow, I had forgotten all about those scripts. Glad to see someone getting some use out of them.
Click to expand...
Click to collapse
They were life-savers, thanks a lot for them!!
Broken links?
First and foremost, thank you for the thorough walkthrough.
I've come across an issue with the provided links to KingRoot and RemoveKing. When I click on either, I receive the following message:
"Invalid Attachment specified. This can happen for a variety of reasons-- most likely because the thread or post you are trying to view has been moved or deleted. Please return to the forum home and browse for another similiar post."
Do you have any alternate links available?
EDIT: I did find an alternate method that worked for proper replacement of KingRoot with SuperSU. All good, and glad for the compatible xposed framework.
zopert said:
First and foremost, thank you for the thorough walkthrough.
I've come across an issue with the provided links to KingRoot and RemoveKing. When I click on either, I receive the following message:
"Invalid Attachment specified. This can happen for a variety of reasons-- most likely because the thread or post you are trying to view has been moved or deleted. Please return to the forum home and browse for another similiar post."
Do you have any alternate links available?
EDIT: I did find an alternate method that worked for proper replacement of KingRoot with SuperSU. All good, and glad for the compatible xposed framework.
Click to expand...
Click to collapse
Thanks for the heads up!!. I'll check them ASAP.
EDIT: All links are fixed!!
kainanmaki said:
Thanks for the heads up!!. I'll check them ASAP.
EDIT: All links are fixed!!
Click to expand...
Click to collapse
Man, can't thank you enough for this...So great for someone like me with little knowledge for all this magic. I am gonna do this when I get back from vacation. Can't wait for the rest of it!
Thanks again
ElCid43 said:
Man, can't thank you enough for this...So great for someone like me with little knowledge for all this magic. I am gonna do this when I get back from vacation. Can't wait for the rest of it!
Thanks again
Click to expand...
Click to collapse
I hope to get part IV and V in no more than 10 days...
I'm in the process of testing removing/freezing many services, just a sneak preview:
So far I was able to disable close to 180-190 apps/services from a total 250-260 (can't remember the exact number).
Of course there are some key services removed (for e.g multi windows, but that's just one service).
Still you can easily remove like 165 without losing any stock functionality. That's how much bloated the tablet is.
Removing useless stuff from samsung and 3rd party (eg. VPN, Policy Updates) or more evident like MultiWindow, the gallery app or even the file browser.
Or the weird ones like the phone app that is hidden and you can't use (you can disable it and still keep LTE Data).
More to come.
Need Help - Having Untimely Reboot Issues
Wow...Thanks SO MUCH for this guide! It gives me hope that I can actually enjoy using my T707A to the fullest!
Alas, I need some assistance PLEASE:crying:
I'm following your guide to the letter, and I've successfully achieved Part 1. Part 2, however, alludes me even after many, many tries. Here is what is going right and wrong:
a) Achieved root with KingRoot
b) installed and achieved SU with Terminal
c) ISSUE - KingRoot (or something) reboots the tablet during Uninstall, which kills SU access obtained with Terminal
d) ISSUE - after reboot, I no longer have permission to run the scripts to uninstall KingRoot
Is there another way for me to do this? As long as the tablet is rebooting during uninstall of KingRoot I have no SU access, so can't do anything but start over and experience the same thing time after time.
ANY assistance would be so very much appreciated...MOST humbly & sincerely...Tom
Where did you find the alternate method??
zopert said:
First and foremost, thank you for the thorough walkthrough.
I've come across an issue with the provided links to KingRoot and RemoveKing. When I click on either, I receive the following message:
"Invalid Attachment specified. This can happen for a variety of reasons-- most likely because the thread or post you are trying to view has been moved or deleted. Please return to the forum home and browse for another similiar post."
Do you have any alternate links available?
EDIT: I did find an alternate method that worked for proper replacement of KingRoot with SuperSU. All good, and glad for the compatible xposed framework.
Click to expand...
Click to collapse
Hi...I am VERY interested in your "alternate" method for replacement of KingRoot with SuperSU that actually worked. Would you be so kind as to share that with me? I'm having huge troubles (see my post) replacing KingRoot as it reboots thus killing my SU access necessary to run the uninstall scripts provided in OP. Any help would be GREATLY appreciated. MOST humbly & sincerely...Tom
TomandJonna said:
Wow...Thanks SO MUCH for this guide! It gives me hope that I can actually enjoy using my T707A to the fullest!
Alas, I need some assistance PLEASE:crying:
I'm following your guide to the letter, and I've successfully achieved Part 1. Part 2, however, alludes me even after many, many tries. Here is what is going right and wrong:
a) Achieved root with KingRoot
b) installed and achieved SU with Terminal
c) ISSUE - KingRoot (or something) reboots the tablet during Uninstall, which kills SU access obtained with Terminal
d) ISSUE - after reboot, I no longer have permission to run the scripts to uninstall KingRoot
Is there another way for me to do this? As long as the tablet is rebooting during uninstall of KingRoot I have no SU access, so can't do anything but start over and experience the same thing time after time.
ANY assistance would be so very much appreciated...MOST humbly & sincerely...Tom
Click to expand...
Click to collapse
I had that problem many times, the uninstall reboots the tablet before you can establish SuperSu.
The most reliable way I found of overcoming this is to follow the exactly in this order and without stopping to much because google wants to run updates behind scenes that mess with our process (that's why sometimes it works and sometime it doesn't). My recommendation is to start over from scracth again (I know it's boring). I'll probably do it again on my tablet just to validate and to try some other things related to the original services).
TomandJonna said:
Hi...I am VERY interested in your "alternate" method for replacement of KingRoot with SuperSU that actually worked. Would you be so kind as to share that with me? I'm having huge troubles (see my post) replacing KingRoot as it reboots thus killing my SU access necessary to run the uninstall scripts provided in OP. Any help would be GREATLY appreciated. MOST humbly & sincerely...Tom
Click to expand...
Click to collapse
Other thing I forgot to ask, did you started clean from the first part or just started with part 2 of the guide?
Will this method trip Knox?
i need * RemoveKing file now...
Updated version of this ROM: [ROM][TMOBILE][S7_SM-G930T][Oreo 8.0 Rooted][WifiCalling]G930TUVU4CRI2
ROM last updated: 10/30/2018
Introduction:
HUGE thanks to the guys that got this going like root & figuring out hybrid stocks! This ROM is a complete rewrite of my ROM [ROM][TMOBILE][S7_SM-G930T][Oreo Rooted] That ROM doesnt have WifiCalling & I couldn't get it to work for the life of me, so I rewrote it. I started with stock, and slowly stepped back making changes, reinstalling each time, confirming it still worked. About 200 installs later & 1000s of changes, this is the result. Yes, it took a LONG time. Hope you enjoy it! Don't forget to say Thanks so I know it is actually helpful to others, and continue doing this!
Description:
Stock Tmobile Oreo 8.0 modified (G930TUVU4CRF1)
EXTREMELY debloated! Nearly bare minimum, while still retaining hardware functionality. Eg, Samsung Gallery & Camera exist so we get 4k recording, and there aren't errors when we pull up the Gallery to edit, etc. Yes, this means NO Samsung or Android Pay. There could be more apps to debloat but Im out of time for now! (Please provide suggestions if interested)
Everything possible I replace Samsung with Google
Solid ROM. It was actually kind of slow for me, but I'm curious how this works for others.
Xposed is part of the guide, which will give you infinite customization & tweak-ability
If you hate Samsung SW and just want a solid working ROM with very few install options to get you up and running this is for you.
This will delete all of your data on the phone! (Not external SD card) This is the only way so don't ask. Backup your data!
Features:
Tmobile Wifi Calling works, along with Visual Voicemail & Mobile Hotspot
Many Aroma Installer app options
(Optional) KevinsFavorites option in Aroma. I'm not sure I'd recommend it due to my tastes. If you're looking for some good common apps tho, it includes: Amazon, AmazonMusic, AquaMail, Gmail, GoogleDrive, GoogleKeep, GooglePhoto, Hangouts, IFTTT, Pandora, RootBrowserClassic, TitaniumBackup, Uber, & Wink (If you install these and want to remove them later, use TitaniumBackup (or similiar) to uninstall
Root Features: See Downloads->Recommended Root Zip & say Thanks!
Debloated
De-Knoxed
Decrypted /data/ partition
OTAs disabled
Speed & Build Prop Tweaks
Dual speaker
Ruthless Launcher
Apps
AdAway
AOD Clock Face Themes
CPUSpy
DisableService
Kernel Adiutor
Samsung Video Editor and Trimmer
Xposed
Many more...
Download Links:
Base.7z & Oreo_Kevin71246Modded_v3.#.#.zip
Installation:
This will delete all of your data! If you continue, you acknowledge that the Author is NOT responsible for anything that happens to your phone!
Summary (for Pros)
Flash Oreo stock
Root
Flashfire
Oreo_Kevin71246Modded_v3.1.##, Auto-mount, Mount /system read/write Option
Go through Aroma setup. When finished, it should boot to Recovery (if not do this). Do a "Wipe data/factory reset"->Reboot
Detailed Steps
Install Stock Oreo:
Download mode & Setup
Make sure you have latest device drivers setup on your PC
Enable USB Debugging on phone in Developer Settings
Boot phone into Download Mode:
Turn off your device
Press and hold Volume Down + Home + Power button
When you see the warning screen, release buttons & press Vol UP. Phone should say "Downloading..."
Download and unzip Base.7z to PC (This contains stock Oreo, ODIN, & root)
ODIN
Open ODIN on PC (\Base\Odin_313.exe)
Connect USB from PC to phone. ID:COM in Odin should turn Blue with a COM port
Select AP, BL, CP and CSC files from the \Oreo_Stock\Base\ folder for corresponding files
Select HERO2QLTE_USA_VZW.pit
Select Start
Finished: Phone will reboot & show Carrier screen for 3-5mins. Wait until Setup screen & go through quickly (bare minimum) since you'll wipe it again. Once in Android, go to Settings->Display->Screen resolution->WQHD->Apply
Root Instructions: (+Flashfire, SuperSU)
Reboot phone into Download mode
Odin
AP: Select \Base\Root\AP_SM_G930_OREO_ENG_BOOT.tar
Start-> Wait for phone to boot to Android OS
Root
Double-click \Base\Root\cmd-here.exe & Type: root.bat [enter]
Option: 1 (Install Root No tweaks) (Or pick whatever you want)
*Note: With this system root, do not update su binary. Disable notifications for SuperSU app. Don't flash any superuser zips in recovery that are not made by jrkruse
Install Custom Hybrid ROM & Xposed
Download & copy Oreo_Kevin71246Modded_v##.zip to phone
Flashfire
Open Flashfire on phone
Red + symbol->Flash Zip or OTA->Oreo_Kevin71246Modded_v#, Auto-mount, Mount /system read/write Option->Check mark
Click Lighting bolt at bottom-> OK
Phone will reboot to Aroma. Go through setup. (See above for what's in KevinsFavorites)
When finished, allow Aroma to exit.
It should reboot into Recovery (If not, do this: immediately hold Vol-Up btn+Home btn until you see recovery on screen. If you missed it, try again: hold Vol-Down+Pwr btn ~10sec until phone restarts & immediately hold Vol-Up btn+Home btn until you see recovery on screen.)
In recovery: Factory Reset->Yes->Restart phone
*Wait 5-10min on loading screens
Go thru Android setup. Ignore "Xposed Installer has stopped" error
Followup-Steps:
Set Dialer: Phone Settings->Apps->Menu->Default Apps->Calling App->Select Phone
Recommendations:
Xposed
Setup Xposed: Xposed Installer app:Install framework option & restart phone
Xposed Installer app: Settings button (3 lines)->Download->Search "GravityBox [O]"->Click it->Versions tab->Download->Install->Back arrow (upper left)->Settings->Modules->Check box next to GravityBox [O]->Restart phone
GravityBox [O] Tweaks: (Open GravityBox app)
Battery indicator: Statusbar tweaks->Battery settings->Turn on Master switch->Battery indicatory style: None->Battery percent text...->Back
Clock: Statusbar tweaks->Clock settings->Turn on Master switch->Center clock...
Firefds Kit [O] Tweaks: (Install same way as Gravity box)
This is a supplement to Gravitybox. Things of note: Advanced power menu, call recording, & disable bluetooth toggle popup, etc
Known Issues:
Visual Voicemail may fail to register, but restart phone and give it a few hours. It works eventually.
RCS (Rich Communication Services/AdvancedMessages/Chat) texts don't show up in Android Messages & Textra, etc apps (This is an issue on stock as well!!)
Fix: (Use Samsung Messages)
How to Install Samsung Messages via ADB (Easiest way though is just reinstall!):
Download Messaging_SEP81.zip, unzip, & manually copy apk to phone via usb/Windows My Computer
adb shell (Get into shell to run beow commands)
su (Run as root)
mount -o rw,remount /system (Mount system read/write since default it read-only)
chmod 755 /system/priv-app/Messaging_SEP81 (Set permissions on folder)
chmod -R 644 /system/priv-app/Messaging_SEP81 (Set permissions on apk file)
ls -l /system/priv-app/Messaging_SEP81 (Check permissions - Should be: -rw-r--r-- 1 root root - not sure what 1 & 2 is)
ls -l /system/priv-app | grep "Messaging" (Check permissions - Should be: drwxr-xr-x 2 root root)
reboot (Reboot device)
Changelog:
Version 3.1.32: First stable build
Ver 3.1.36:
-Disabled encryption on /data/ partition to resolve "Bluetooth paired devices deleted after reboot" issue & so mods play nicer with ROM
-Fixed "Device not supported" error on Google Phone app
Ver 3.1.37:
-Added most of the apps I replaced or added as options in Aroma Installer now
Credits:
- @jrkruse & @klabit87 for Root
- @partcyborg for helping jrkruse
- @jrkruse for his similar ROMs as guides & help
- @Lanc-City for assistance in ROM modding
- @gustco for eng boot.img
- @Raymonf for modified odin
- @amarullz for Aroma Installer
- @Chainfire for FlashFire & SuperSU
- @rovo89 for Xposed
- @JaeKar99 for the cool & colorful boot animation
- @mrRobinson for AdAway ADAway.org
- Brandon Valosek for CPUSpy
- WangQi for DisableService
- Willi Ye for Kernel Adiutor
- @shubby for Ruthless Launcher
- @Craz Basics for Dual Speaker Mod
...
- Please PM me if you were forgotten!
Some screenies:
Saved2
Saved3
Well nice job!
jrkruse said:
Well nice job!
Click to expand...
Click to collapse
...but your'e the best! (You & I both know I couldnt have done it without all your other work!)
Once I FINALLY got WifiCalling to work, I thought... Imagine ALL the S7 XDA members out there with crappy Tmobile signal across Rural America that could TOTALLY use Wifi Calling!!! Haha, but seriously!! & that thought was the birth of this thread
kevin71246 said:
...but your'e the best! (You & I both know I couldnt have done it without all your other work!)
Once I FINALLY got WifiCalling to work, I thought... Imagine ALL the S7 XDA members out there with crappy Tmobile signal across Rural America that could TOTALLY use Wifi Calling!!! Haha, but seriously!! & that thought was the birth of this thread
Click to expand...
Click to collapse
Is this Ufirm firmware?
jrkruse said:
Is this Ufirm firmware?
Click to expand...
Click to collapse
I have so many FW packages on my PC at this point, from so many places that I used while trying to get this to work, but I think it might be a package from one of your threads(?) Since I'm not exactly sure what you're asking regarding "Ufirm FW", I'll elaborate hoping that answers your question. (Tho I'm thinking you mean the U variation/unlocked. So based on these stock files below I guess the answer is no.) If you're question is really, "is it possible to get tmobile wifi calling to work on a U model #", then I'd have to really think about that. But at this point I don't have an answer. I can tell you a million dependencies about it tho! (I seriously have hundreds of revisions I made while testing, & notes. The symbolic & meta links in Aroma initially broke it, as I found out after a week or so of testing - wish I knew a bit more about them, and why they're all there, then I'd know what was wrong about them...)
High-level process:
1)Flash Base/Stock/Oreo Rom:
- AP_G930TUVU4CRF1.tar
- BL_G930TUVU4CRF1.tar
- CP_G930TUVU4CRF1.tar
- CSC_TMB_G930TTMB4CRF1.tar
- HEROQLTE_USA_VZW.pit
2)Root with your method
3)Flash Xposed framework & my ROM (it's a "start with stock then remove what we don't want" type of Aroma/Edify script)
jrkruse said:
Is this Ufirm firmware?
Click to expand...
Click to collapse
BTW, any idea how to prevent the "verification failed" error I mention in the OP steps, after flashing Xposed framework? I tried flashing dm-noverity but no luck. At least my guide covers it at this point tho... Thanks again
kevin71246 said:
BTW, any idea how to prevent the "verification failed" error I mention in the OP steps, after flashing Xposed framework? I tried flashing dm-noverity but no luck. At least my guide covers it at this point tho... Thanks again
Click to expand...
Click to collapse
If you choose the keep safestrap option during root the it will flash the system/vendor/etc/ fstab.qcom that totally removes data encryption but when that fstab.qcom is flashed it also requires a data wipe for phone to boot then when you install xposed you won’t see that error but either way you end up wiping data so your choice
Sent using some kind of device I modified
It works perfectly!!
I have not had any problems so far, here I leave you for the link to download and try those who are interested in VIPER4ANDROID: https://drive.google.com/file/d/1572ORe6TOrsRBuxWWBChH-WMnxkvcUjH/view?usp=drivesdk
You just have to flash it with Flashfire, but if you do not pull them, let me know Thank you very much !!! Kevin for the effort!
---------- Post added at 10:17 PM ---------- Previous post was at 10:15 PM ----------
I have not had any problems so far, here I leave you for the link to download and try those who are interested in VIPER4ANDROID: https://drive.google.com/file/d/1572ORe6TOrsRBuxWWBChH-WMnxkvcUjH/view?usp=drivesdk
You just have to flash it with Flashfire, but if you do not pull them, let me know Thank you very much !!! Kevin for the effort!
First, I want to thank you so much kevin71246. I tried your previous version as I was sick and tired of how sluggish my phone felt after the last two T-Mobile OTA updates. So far the experience on the phone has been great but I wanted to post about an issue I had with that version to see if anyone else has come across it or can figure out what is going on. The reason I am making this a reply in this thread instead of your other is because I will be flashing this update shortly but I want to get the ball rolling on the issue first.
I went through the whole process, installing the minimum with Google Apps, though I did restore everything previously installed once I log in with my Goggle Account. I am unsure if this contributed to the problem but I will not be restoring apps on the next try. It seems no matter what process I attempt to connect my Ticwatch E to my S7 the Wear OS app will not recognize it which causes the watch to get stuck in the setup phase, making it useless. This was after multiple and different connection attempts, resets, reboots and factory (watch only) restores. The watch will show up under bluetooth and create the initial connection but it will not stay connected. Anyone have any idea? Is this ROM missing something?
Edit: Mid way through the install, I wanted to note that I checked for the issue after doing the "Install Stock Oreo" but before Root and everything worked as it should. Wear OS sees the watch instantly and Bluetooth connects fine.
Edit: So I am a day into using the ROM and I am still having issues. While it will connect and work perfectly fine now, when ever I do a reboot of the phone the watch no longer connects. I will just get constant Bluetooth Connection Requests, every single time the watch tries to get data, and it never actually connects. To fix this I need to do a complete reset of the watch and do the whole setup process again. As you can imagine this is no good, expecting to wipe my watch every time my phone reboots makes it still almost useless.
charredchar said:
First, I want to thank you so much kevin71246. I tried your previous version as I was sick and tired of how sluggish my phone felt after the last two T-Mobile OTA updates. So far the experience on the phone has been great but I wanted to post about an issue I had with that version to see if anyone else has come across it or can figure out what is going on. The reason I am making this a reply in this thread instead of your other is because I will be flashing this update shortly but I want to get the ball rolling on the issue first.
I went through the whole process, installing the minimum with Google Apps, though I did restore everything previously installed once I log in with my Goggle Account. I am unsure if this contributed to the problem but I will not be restoring apps on the next try. It seems no matter what process I attempt to connect my Ticwatch E to my S7 the Wear OS app will not recognize it which causes the watch to get stuck in the setup phase, making it useless. This was after multiple and different connection attempts, resets, reboots and factory (watch only) restores. The watch will show up under bluetooth and create the initial connection but it will not stay connected. Anyone have any idea? Is this ROM missing something?
Edit: Mid way through the install, I wanted to note that I checked for the issue after doing the "Install Stock Oreo" but before Root and everything worked as it should. Wear OS sees the watch instantly and Bluetooth connects fine.
Edit: So I am a day into using the ROM and I am still having issues. While it will connect and work perfectly fine now, when ever I do a reboot of the phone the watch no longer connects. I will just get constant Bluetooth Connection Requests, every single time the watch tries to get data, and it never actually connects. To fix this I need to do a complete reset of the watch and do the whole setup process again. As you can imagine this is no good, expecting to wipe my watch every time my phone reboots makes it still almost useless.
Click to expand...
Click to collapse
I believe I know what the issue is, I'm testing a fix (for THIS ROM) as we speak. Stay tuned. Maybe tomorrow if I have time and it works I'll update the OP. BTW, this ROM and my other ROM are TOTALLY different. Thanks for the feedback!
FranMLG said:
I have not had any problems so far, here I leave you for the link to download and try those who are interested in VIPER4ANDROID: https://drive.google.com/file/d/1572ORe6TOrsRBuxWWBChH-WMnxkvcUjH/view?usp=drivesdk
You just have to flash it with Flashfire, but if you do not pull them, let me know Thank you very much !!! Kevin for the effort!
Click to expand...
Click to collapse
What do you mean by this? "but if you do not pull them, let me know"
And tell me more about Viper4Android, and if it works solid for you on this ROM...then I'll consider adding it. Thanks!
New version, see change log in OP for details.
Yeah i.a give this a shot in a little. Do I need to root phone or can I just flash through Odin. Sorry not used to this locked bootloader crap..... s8crj1 are the last 6 digits of the software I'm on. I did receive the latest update will this effect me installing this. Sorry as I said not used to this locked bootloader crap.
jrkruse said:
If you choose the keep safestrap option during root the it will flash the system/vendor/etc/ fstab.qcom that totally removes data encryption but when that fstab.qcom is flashed it also requires a data wipe for phone to boot then when you install xposed you won’t see that error but either way you end up wiping data so your choice
Sent using some kind of device I modified
Click to expand...
Click to collapse
Hi, why you have to flash this - HEROQLTE_USA_VZW.pit on 930t, is it ROM specified? if I do and don't then what are pro and cons?
---------- Post added at 01:36 PM ---------- Previous post was at 01:26 PM ----------
josh2020glacier said:
Yeah i.a give this a shot in a little. Do I need to root phone or can I just flash through Odin. Sorry not used to this locked bootloader crap..... s8crj1 are the last 6 digits of the software I'm on. I did receive the latest update will this effect me installing this. Sorry as I said not used to this locked bootloader crap.
Click to expand...
Click to collapse
since bootloader is locked you can't use TWRP so you have to use Flashfire to install this ROM, as you know flashfire required root so you have to setup the base per OP and then root the base then install the ROM and then root it again, read the first page I don't think you will get a instructions more detailed then his
Okay so I just realised I was posting comments on the old thread, my bad. Coming back to the question, can the boot animation be changed? I've messed with the qmg files in an attempt to replace the weird, nauseating rainbow animation but even after overwriting the latter, it persists. Looking forward to a reply kek
Alkan3 said:
Okay so I just realised I was posting comments on the old thread, my bad. Coming back to the question, can the boot animation be changed? I've messed with the qmg files in an attempt to replace the weird, nauseating rainbow animation but even after overwriting the latter, it persists. Looking forward to a reply kek
Click to expand...
Click to collapse
Nauseating rainbow? LOL. Sorry. This is much more of a general question though, that wouldn't exactly pertain to this ROM specifically. And given I don't have an answer, I'd try searching BootAnimation How-Tos to get this customized. The ONLY thing I did regarding this was replaced the existing files with the rainbow ones. That's it. Apologies in advance.
Just discovered an issue: RCS (Rich Communication Services / Chat) texts don't show up in Android Messages app. See "Known Issues" in OP for a solution. BTW I posted a new ROM version a few days back that allows many choices in Aroma Installer. Make sure to pick Samsung Messages (instead of Google), so you get RCS chat text messages!