Related
Small app for managing some HD2 specific tasks (auto backlight, button auto-off...) and few other things. This is early preview beta just for bug testing and "market research". This basically means "if you want some more functions, give me an idea !" .
Also in later stage i will activate Hot BootLoader for loading linux distros from android, and some other nifty tricks like kernel swapping, "on the fly" user data remount, and other...
For all updates follow me on twitter...
Enjoy
UPDATE: Released new version with Hot BootLoader and sample linux distro (debian with xfce4). For more information go to appropriate forum: LINK
And please all questions regarding HBL put in other thread !
Reserved
Reserved space...
any screenshot pls ?
Looks good so far, the hot bootloader function alone will make the app worth having once implemented.
Would also be great to have hot recovery (cwm via mgldr or clk- dont ask me how to pull that off lol)
and maybe a hot mgldr option if possible,
and screen density.
Shows real potential !
Tried to up a couple of screen shots, but tapatalk isn't letting me
Sent from my HTC HD2 using XDA App
What's the different between backlight control using microp vs std android?
Sent from my HTC HD2 using XDA App
Hot reboot would be a nice feature to include
It has hot reboot already, restart zygote (the davlik vm, that's how most programs hot reboot anyways) it's under misc in the menu.
mstrk242 said:
It has hot reboot already, restart zygote (the davlik vm, that's how most programs hot reboot anyways) it's under misc in the menu.
Click to expand...
Click to collapse
You just took words out of my mouth I should probably rename this button so more users would know what it means.
mstrk242 said:
It has hot reboot already, restart zygote (the davlik vm, that's how most programs hot reboot anyways) it's under misc in the menu.
Click to expand...
Click to collapse
Tried this and I got stuck on the boot animation screen. Had to pull battery out and then it booted fine.
Sent from my HTC HD2 using XDA App
Thx for your app, the hot reboot is awesome !!
Note that after an hot reboot, I have to enable/disable flight mode because the network connection doesnt work anymore (I could receive calls but no internet).
Again, what's the different between backlight control using microp vs std android ?
And would you include a trick to make the led notifications working ?
i would love to boot ubuntu 0.3 from android 2.3.3, hope you can do something about that..
At dan1j3l I just recently installed a app called Boot Anomation that can be found here on XDA. This app lets you imstall a new boot animation, back up your boot animation and download new boot animations. It is a fairly new app so it not a lot of boot animations to download just yet but it works great. I think your HD2 Tool Box app would be awsome with something like this in it.
Also no rush but I am looking forward to being able to use the Hot Boot function, any news on that as of right now?
Version update
New version with HBL released, for info go to new thread
hi first big thanks for your hard work.
now i need some help to get linux running from HBL.
i´m using kingdom sense3 rom from dungphp.
i installed hd2 toolbox and copied linux folder to root of sd card.
i installed HBL (Busybos is installed in version 1.19.x.x) i took rootexplorer and give /system/bin/ write permissions for owner/groups/others.
But i need initd support: what i have to do to get this?? or is it on my rom?
please help cause at the moment i´ve bootloops everytime i want to boot linux.
On the goomanager app when I browse compatible roms there are quite a few besides nightly. I know what nightly is, but what are the others? Like teamdouche,aokp, eyeballer, teambroccoli, etc.
I've never heard of teamdouche or eyeballer. I've also never used goomanager so I dont know if it displays ROMs only for the TouchPad or all ROMs in general. But the difference between CM9 and any other ROM is each ROM has their own set of features. Most arent that different. Some have more tweaks than others. All you can do is try them out and see what you like better.
EDIT: Just did a search and I guess teamdouche and eyballer are the devs of the their own ROMs. Again, they probably just have their own features.
jsgraphicart said:
I've never heard of teamdouche or eyeballer. I've also never used goomanager so I dont know if it displays ROMs only for the TouchPad or all ROMs in general. But the difference between CM9 and any other ROM is each ROM has their own set of features. Most arent that different. Some have more tweaks than others. All you can do is try them out and see what you like better.
EDIT: Just did a search and I guess teamdouche and eyballer are the devs of the their own ROMs. Again, they probably just have their own features.
Click to expand...
Click to collapse
yes. you can also go here to see more about different dev roms
http://forum.xda-developers.com/forumdisplay.php?f=1248
also in goo manager app i would advise against installing open recovery script from the menu options. It doesn't play well with touchpad. just use your regular recovery like cwm.
In answer to the OP's question about which is which:
Nightly is the official CM9 nightlies
AOKP is for the Android Open Kang Project (based on the CM9 tree)
Eyeballer is the one who was doing the unofficial nightlies until the official ones got up and running.
Philicibine is host to the CherryKang project (also based on the CM9 tree)
TeamBroccoli hosted a separate mod of AoKP called AOKPCB (again, based on CM9 tree)
TeamDouche is where the official Alpha's were hosted (alpha0, 0.5, 0.6, and Alpha2)
TravP624 created his own cang version of it called BlackICE (not sure about this one).
GooManager only shows you the ROM's that are compatible with your device (based on your build.prop) So if you left your device as a standard cm_tenderloin, you'll see all of the available ROM's for the TouchPad.
And I must disagree with your last statement there, haxin. The OpenRecovery Script installed TWRM, which allows me to start the flash, wipe cache and Dalvik, right from the app itself on the next reboot, then when it's done, it reboots back into CM9. So instead of me having to go in, manually wipe Cache and Dalvik, then flash the ROM, then reboot, it does it all for me with a couple of quick touches. Plus it's a touch-readable recovery - meaning you don't have to use the Vol-Up and Vol-Down buttons, just touch the screen. I DEFINITELY recommend it, as it is a simplification tool that makes our lives easier. However, it is completely up to you which recovery you use.
ve6ay said:
In answer to the OP's question about which is which:
Nightly is the official CM9 nightlies
AOKP is for the Android Open Kang Project (based on the CM9 tree)
Eyeballer is the one who was doing the unofficial nightlies until the official ones got up and running.
Philicibine is host to the CherryKang project (also based on the CM9 tree)
TeamBroccoli hosted a separate mod of AoKP called AOKPCB (again, based on CM9 tree)
TeamDouche is where the official Alpha's were hosted (alpha0, 0.5, 0.6, and Alpha2)
TravP624 created his own cang version of it called BlackICE (not sure about this one).
GooManager only shows you the ROM's that are compatible with your device (based on your build.prop) So if you left your device as a standard cm_tenderloin, you'll see all of the available ROM's for the TouchPad.
And I must disagree with your last statement there, haxin. The OpenRecovery Script installed TWRM, which allows me to start the flash, wipe cache and Dalvik, right from the app itself on the next reboot, then when it's done, it reboots back into CM9. So instead of me having to go in, manually wipe Cache and Dalvik, then flash the ROM, then reboot, it does it all for me with a couple of quick touches. Plus it's a touch-readable recovery - meaning you don't have to use the Vol-Up and Vol-Down buttons, just touch the screen. I DEFINITELY recommend it, as it is a simplification tool that makes our lives easier. However, it is completely up to you which recovery you use.
Click to expand...
Click to collapse
I guess I just got used to managing all the recovery flash options through rom toolbox pro, it is one of my MUST have apps for sure. I always liked using the non touch recoveries because its only a matter of time before you acidentally tap an option you didnt mean to and mess something up. I went back to the regular cwm recovery after this happened 3 or 4 times to me. maybe i'm just not very coordinated. I do however love goomanager it is a must have app.
The nice thing with TWRM is that you have to confirm everything each and every time by a long swipe - not even just a "Tap here for OK", it's a swipe toggle, like the slider unlock from CM7 or CM6 phones. Makes it a LOT easier to not screw up. Because I agree, if it was just a tap-tap-done, it would be bad. A swipe, that's a little harder to screw up (Don't get me wrong, it can be done, but it's harder).
ve6ay said:
The nice thing with TWRM is that you have to confirm everything each and every time by a long swipe - not even just a "Tap here for OK", it's a swipe toggle, like the slider unlock from CM7 or CM6 phones. Makes it a LOT easier to not screw up. Because I agree, if it was just a tap-tap-done, it would be bad. A swipe, that's a little harder to screw up (Don't get me wrong, it can be done, but it's harder).
Click to expand...
Click to collapse
ok well that is alot better than some of the cwm touch recoveries that I tried a while back.
Yeah, I really like it. The other huge bonus is again that it scripts to run all your updates through the recovery from GooManager. So this way, you can tell it to flash a series of two zips (For example, your rom, then gapps), as well as clear your cache / Dalvik, and even do a full data wipe, all from GooManager, then it reboots, does it, and restarts into Android for you. I can't say that I've come across anything that allows me to do that in CWM.
ve6ay said:
--SNIP--
GooManager only shows you the ROM's that are compatible with your device (based on your build.prop) So if you left your device as a standard cm_tenderloin, you'll see all of the available ROM's for the TouchPad.
--SNIP--
Click to expand...
Click to collapse
Lately, TWRP shows the TP as a hercules. I've checked build.prop and build information in Settings, and they all indicate tenderloin. Any idea why TWRP would think it's a hercules?
shumash said:
Lately, TWRP shows the TP as a hercules. I've checked build.prop and build information in Settings, and they all indicate tenderloin. Any idea why TWRP would think it's a hercules?
Click to expand...
Click to collapse
Hercules is the code name for a T-mobile Samsung galaxy SII (T989) as used by rohan32 in his supreme mods for compatibility with gameloft games, if you flash his mod that's what goo manager will find
Sent from my CyanogenMod9 TouchPad using TapaTalk 2
Summarized Standard Disclaimer: use at your own risk. I use it at mine
*Full wipe recommended if coming from another rom due do the settings database varying and no way to make them compatible*
My personal Omni Rom 5.0 is based on omnirom with the following additions:
CM12 File Manager
CM11 ssh terminal commands
Bash shell
Nano text editor
Koush's full featured open source superuser integrated into settings***(see potential quirk)
Cyanogenmod custom host name
Cyanogenmod screen off volume key long press music control
The list of personal touches isn't very long right now but they include
Battery percent displayed next to battery icon
Battery icon changes color based on percent: 0-15 red, 16-50 yellow, 51-100 green
Disabled lock screen full screen music.
Disabled SELinux at the kernel
Up to 1.6GHz CPU OC
Automatic 400MHz GPU OC
Not Working/Quirky
Bluetooth audio
Mic can be quirky.
Stock camera (not included) would crash on camera change, photo/video change. Try this open source alternative instead. Full featured, nice and fast.
AOSP keyboard swipe doesn't work: google's fault.
Cellular data probably doesn't work. phone call audio doesn't work. The rest is reported ok.
Flashing SuperSU might cause issues since the su daemon is started by the ram disk script since boot scripts apparently don't work.
Plugging in a charger when turned off causes the tablet to turn on with the touch screen disabled.
Everything else not listed as a quirk probably works.
*First Time*
-Read second post FAQ and other important information
-Make titanium backup (highly recommended)
-Flash TWRP 2.8.1.0
-Flash fixed twrp 2.8.0.0 for TMobile users
-Reboot into new recovery
-Make recovery backup (meh, I don't usually do it but you have been warned)
-Full wipe
-Format system
-Install rom
-install gapps (you can use another one if you want. I always provide the most minimum gapps)
-reboot
-TURN ON WIFI IMMEDIATELY AS SOON AS POSSIBLE
*Subsequent flashes*
-TURN ON WIFI BEFORE REBOOT RECOVERY
-Install ROM
-Install gapps
-Reboot into rom
-Reapply any adblocking hosts file.
Downloads
Mediafire folder (discontinued)
Gapps Android File Host
TWRP Android File Host
Wifi ROM Android FIle Host
3G ROM Android FIle Host
TMobile ROM Android File Host
Credits:
-decatf: your patches were vital to the rom
-drewwalton19216801: used your gapps for the minimal gapps package
-kasper_h: I learned a lot from doing kitkat with you last year
-pershoot: original device/vendor base
-omni team: providing rom
-cyanogenmod team: rom extras
Sources https://github.com/AAccount?tab=repositories
Screenshots: a picture is worth 1000 words but a video is worth exactly 30 pictures/second (mostly).
XDA:DevDB Information
Omni 5.0, ROM for the Samsung Galaxy Tab 10.1
Contributors
AAccount
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.1.x
Based On: Omni
Version Information
Status: Weekly
Created 2014-11-24
Last Updated 2014-11-23
Delete
FAQ:
OMFFFFFFG: insane boot loop 10 seconds after lock screen: install any rom from the year 2015.
Missing gapps: remember to reflash after every rom.
Adblock hosts stopped working: remember to reapply ad block hosts after ever flash.
Google maps 9+ doesn't work due to an illegal instruction exception. No practical way to fix it. Install google maps 8.4 it works now. Make sure you use the latest google maps.
No keyboard: Settings --> Language & Input --> Current Keyboard --> Hardware (show input method) turn this on.
AOSP swipe doesn't work: apparently google removed these lines of code from aosp keyboard.
Launcher 3 crashes on boot since Feb 8 build: I switched to CM's launcher since it has some customizability. Go to /data/data/com.android.launcher3 FROM RECOVERY and erase this folder.
THIS IS A TEST ROM. PLEASE REMEMBER THAT
For those of you who are itching to try the android 5.1 build I've done some basic quick testing and I like how it's going. The chromium bug I got this afternoon seems to be taken care of with 2 commits. Look at them if you want to know the secret
Installation Instructions (may not be complete as I've installed a lot of zip files. Please try and fill in the missing holes as the rom does install and boot)
Reboot recovery
Wipe data
Format system
RE reboot into recovery
install rom
install my recommended android 5.0 gapps (have heard issues using others but not tried it myself)
try it out
report the bugs
What works: everything thing that worked in 5.0 should continue working.
The camera app has a bit of a "confidence" problem. It will crash on switching to front/back photo/video but if you open it again it will do what you wanted. Sometimes it doesn't crash. Give the camera app patience.
Link: https://www.androidfilehost.com/?fid=95916177934541869
Great news. Downloading asap.
Is just enough to have WiFi on, or it must also connect to some network to avoid bootloop? I'm concerned what happens if I turn it on in the desert where there's no Wi-Fi whatsoever?
Hi.For p4 expected? Thanks.
jaibar said:
Great news. Downloading asap.
Is just enough to have WiFi on, or it must also connect to some network to avoid bootloop? I'm concerned what happens if I turn it on in the desert where there's no Wi-Fi whatsoever?
Click to expand...
Click to collapse
Just on. No connection necessary. You can also feel free to turn it off after a few minutes of just being on. Just remember to turn it back on before a reboot or weekly flash.
@AAccount thanks for bringing omni 5 to the tab was running ur kitkat build, however not sure if anyone else is having install issues, installed twrp 2.8.0.0, factory reset and wiped system, but when trying to install zip i get the following error:
Set_perm: some changes failed
Error excuting binary in zip
Error flashing zip
Any help or info would be appreciated.
Thanks
emu1982 said:
@AAccount thanks for bringing omni 5 to the tab was running ur kitkat build, however not sure if anyone else is having install issues, installed twrp 2.8.0.0, factory reset and wiped system, but when trying to install zip i get the following error:
Set_perm: some changes failed
Error excuting binary in zip
Error flashing zip
Any help or info would be appreciated.
Thanks
Click to expand...
Click to collapse
Well in that case try using the new twrp 2.8.1.0 I just posted. I used that later on in the testing of flashing the rom. It's in the first page instructions under first time flashing. I added a link to the new recovery.
AAccount said:
Well in that case try using the new twrp 2.8.1.0 I just posted. I used that later on in the testing of flashing the rom. It's in the first page instructions under first time flashing. I added a link to the new recovery.
Click to expand...
Click to collapse
Thanks for the reply, but still get the same issue, however if i flash decatf's build first im able to dirty flash your build on top...
emu1982 said:
Thanks for the reply, but still get the same issue, however if i flash decatf's build first im able to dirty flash your build on top...
Click to expand...
Click to collapse
Maybe you should pull a recovery log and post it here so @AAccount can see what's going on.
Can't download twrp2810-wifi.zip from mediafire, always only download 2m then interrupted.
Anybody who can send me a twrp2810-wifi.zip, my email is
[email protected]
Thank you very much!
mediafire failing to download any file I try to download from it
Can't download twrp2810-wifi.zip from mediafire , I am having a problem too with mediafire, each time I click on download , it refreshes loops the download page, no file is able to access, I think it has something to do with our ISP, we moved into a place that you can only use hughesnet to access the web, I can't get DSL from the house my parents got etc.. , I tried the cleaning the cache like this page
http://topkpop.wordpress.com/2010/05/10/solution-for-mediafire-continuous-refresh-download-problem/
it says that removing cookies fixies this but it is not , still failing to access any files off of mediafire, I was able to create a mediafire account , and download their desktop software, but can't get files like from your links to work, it seems , I have tried internet explorer, firefox, and google chrome, each browser doesn't want to let me download etc to save the file, The only thing I have yet to try is use my android tablet to access the links, I don't no if mediafire will work right or not over my android, if my download pc doesn't download it, from my wireless network ,
my android tablet also can't access the files. I just tried to download twrp2810-wifi.zip from mediafire off of browser on android , when you click download it keeps looping and freshing the page, but what it doesn't do is download, I am in US, CA so it shouldn't be blocking me from downloading files, not sure why this seems to be happening, it was not a problem with our old isp before me moved etc..
I don't no if this explains it, but on android , when click download it reloads this page"http://www.mediafire.com/download/6hc9ws7sd96j3nn", instead of this "http://www.mediafire.com/download/6hc9ws7sd96j3nn/twrp2810-wifi.zip" I been tried to click download over and over , even the repair download thing, doesn't do anything , after clicking on download a few, times I got that message.
I am able to use
Downloads
Mediafire folder
Click on the files, and use the copy to my accounts folder option, which sync it to the desktop software, that feature is working for me, just not mediafire download pages
anyway can you give me access to the folder, that has Flash file TWRP 2.8.1.0, since then I could click the copy feature of mediafire, and transfer it to my account on mediafire, and it will download and sync the file to my folder on my computer, thats the only way or simplist way to get passed that looping on download page problem, or maybe copy the file into your mediafire folder if that also possible I hope,
don't have to have the newest version to flash right away , but it would be nice if I was able to access it, to flash anyway, I still got the 2.7 version of twrp, after using android 4.4.4 nameless etc.. before I got problems with mediafire from my web browser problem, and access to cwm boot flash manager too, which I found files on the web for flashing with touch screen option, while browsing the forums here
attached downloads will download no problem, and other websites besides mediafire will also work just fine for me, since it seems to be a mediafire download page problem only bug,
also talking about bugs, does this rom have that power on charging , bug like the rom [AOSP] Android 5.0.0 Lollipop (LRX21V) has?
"Whenever I try to charge the tab while it's turned off, it boots up. Is this a new feature of Android 5.0? Also it doesn't respond to touches. " , on its last page I read that its a new feature of the android 5.0 based on aosp rom, it reads " It turns out there is a new feature in Lollipop to boot from charger but it is not enabled by default. It is only for one specific device at the moment. I reverted the code anyways but the problem still exists. So the issue lies deeper some where." , source information can be found here, http://forum.xda-developers.com/gal...-5-0-0-lollipop-lrx21m-p4wifi-t2938870/page17
if this rom doesn't have that problem, maybe something can be learned from it , to fix the bug in the other rom, since our tablets , don't like that feature, since it locks up our tablets touchscreen from doing anything but hard rebooting them etc.. when plugged into power when in off mode etc...
emu1982 said:
Thanks for the reply, but still get the same issue, however if i flash decatf's build first im able to dirty flash your build on top...
Click to expand...
Click to collapse
Same here, switched from CWM to TWRP 2.8.1.0 and I'm still getting the error D:
AAccount said:
Well in that case try using the new twrp 2.8.1.0 I just posted. I used that later on in the testing of flashing the rom. It's in the first page instructions under first time flashing. I added a link to the new recovery.
Click to expand...
Click to collapse
Was able to download TWRP and gapps just fine but the ReCaptcha you have to complete in order to download the ROM won't load a picture. I have tried on my tablet, phone and computer... Able to pass a ReCaptcha on other pages just fine, clearly an issue with this specific download page. Anyone else having this issue?
L3R0N said:
Maybe you should pull a recovery log and post it here so @AAccount can see what's going on.
Click to expand...
Click to collapse
http://pastebin.com/xSr4TLCY
@AAccount here is a twrp log of the install issue i had trying to install after a full wipe. Hope it helps..
For people with download problems, will it be ok if I register for an account here:
https://www.androidfilehost.com/user/?w=register
Will that be a good file hosting site?
I know its still early development for 5.0 rom versions of android 5.0, do you guys know why scummvm version 1.7.0 release will not download and install, it keeps failing to download for me on android 5.0, from google play website, also the development version 1.8.0 direct from scummvm will install but crashes on play, off of http://scummvm.org/
I know that scummvm app, worked for android 4.4.4 nameless rom, I used it under that android before, never crashed that I can remember, I hope as android 5.0 builds makes progress that whatever causing it to crash gets fixed. I am not sure if its something that needs to be fixed in the android os system of 5.0, or if its something that needs fixing in the scummvm app, that causes it to crash under android 5.0, maybe future development builds of scummvm will fix the crashing under android 5.0.
and below a fix to the charging bug I think its a fix I have yet to test it from this page, since both our based on android 5.0 I am guessing that these files will fix booting on both
source page "http://forum.xda-developers.com/galaxy-tab-10-1/development/rom-android-5-0-0-lollipop-lrx21m-p4wifi-t2938870/page17"
decatf said:
Charging mode should be working now although there are still some issues to be ironed out. Note(!) that ADB is running in while in charger mode. I haven't figured out why yet.
It only requires an update to the boot partition. Flash and reboot.
bootimg-p4-lp-20141125.zip
bootimg-p4wifi-lp-20141125.zip
The problem is that Samsung did not follow the Android method of booting into charger mode. With Android 5.0 this method of booting is not working. So I ported it to work with the Android method. Which means it is booting slightly differently than the old charger mode.
Someone others mentioned issues with overclocking. I have not had a chance to look into this yet.
Click to expand...
Click to collapse
Omni 5.0 p4wifi Nov 23
Re scumm vm... Could it be dalvik vs ART? I have done very little research.. Just know that xposed -framework- (and most modules?) require dalvik.. Put another way, not (yet?) compatible with ART
5.0 has no option for dalvik, whereas 4.4.4 can do both
One possible test: reflash 4.4.4, switch to ART, then see if scumm works?
Or if I am off base, hopefully someone else will chime in...
I never tried the android 4.4.4 under art, so maybe it would of crashed scummvm too , I don't no if its compatable with art maybe thats why, also I did want to note , that unlike the AOSP android 5.0 rom, in this one, google now launcher seems to crash , but I didn't notice crashing in the other android 5.0 , is it because it has had more time to fix the bugs in the os system, since Omni 5.0 p4wifi is a newer rom? I am correct or is their something that needs to be fixed in google now launcher or the build of the rom?
Hi guys, I had bought this device in anticipation that this will also see as much development as first gen, and was disappointed. But here's a hacky sort of way to flash new ROMs on the MTK variant.
1) Make sure you are running the same STOCK Android version of which you want to install the ROM. I am on 6.0.1 and will be using CM 13
2) Find yourself a "sprout4" ROM which you would like to flash.
3) Boot into TWRP, then backup your boot partition and perform a clean wipe.
4) Flash the ROM, then restore the boot image backup.
5) Reboot. Enjoy!
Bugs :
Of course, there have to be some.
1) Battery percentage : Battery percentage will always be around 3000+, can't help that. Deal with it.
2) Sudden lockups : When I was on OmniROM, sometimes the quick settings drawer refused to open, and home button only worked when in recent apps. I created a guest user, then switched back to my own and these bugs vanished.
3) Some ROMs may not work : I couldn't boot Resurrection Remix on this, so maybe some more ROMs exist that cannot do that as well.
I am not responsible for any damage you may end up doing this method. I was successful using it and therefore decided to share it with everyone only after I was sure that stuff worked.
Thread closed at OP's request
I created a new ROM with WifiCalling: [ROM][TMOBILE][S7_SM-G930T][Oreo 8.0 Rooted][WifiCalling]
ROM last updated: 9/24/2018
Introduction:
HUGE thanks to the guys that got this going like root & figuring out hybrid stocks! This thread here is just my take and customization on what they already did. Ultimately, I wanted Oreo rooted & modded, but I couldn't find a single guide. And the ROMs that existed weren't exactly what I was looking for. I wanted something exclusive to Tmobile. So I did a ton of reading and compiled it all together into a HOPEFULLY easy guide to follow. PS If you like Samsung bloatware, this is NOT for you!
Description:
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.
Everything possible I replace Samsung with Google
Solid ROM, very fast
There are very few options in Aroma to limit issues & repeatability. There are many options once booted up after initial setup
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.
Aroma installer layout is a little wonky, apologies (If anyone knows how to fix this please chime in )
This will delete all of your data! This is the only way so don't ask. Backup your data!
Features:
Optional Tmobile Apps
Optional Google Apps
Root Features: See Downloads->Recommended Root Zip & thank him for his work!!
Debloated
Deodexed
De-Knoxed
Zipalign
Instant Face Unlock mod
Disable signature verification
S9 Dolby Atmos
Memory Saver
OperMax
More Toggles
Mulit User
Private Mode
Unlock Stock NetWork Speed
Build Prop Tweaks
Device Status Official
White Page
CallRecord
Capture and Record Screen
Remove Volume Safe Warning
Remove brightness Warning
Added Bike Mode
Allow fingerprint unlock after a reboot
Google MarkUp
Force always visible Free Form Menu item in notifications
Substratum Theme
Dual speaker
Samsung Weather
Samsung Video Editor and Trimmer
LancControl Mods:
Ui Mods
3Mint Clock
Gradient statusbar
Virtual Lock Home Recent Button
Phone Mods
Clock Face Setting Aod
AdAway
Dpi Changer
Disable/Enable Apps
Kernel Adiutor
TW Mods:
Adaptive Fast Charging
Wireless Fast Charging
Usb Plug in/out Wakeup
OutDoor Mode
HardKey Lights
TouchLight
Recents Menu Mods:
Tasks Changer
Blur recent and Notification Menu
Download Links:
Base.7z & Oreo_Kevin71246Modded_v1.zip
VoLTE Fix
Steps:
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!
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
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)
OPTIONAL: (Testing, WIP...) Backup with Titanium Backup (or whatever) at this time the following apps so they work in the end: Visual Voicemail, Wifi...
OPTIONAL: (Testing, doesnt work. Please provide a fix if you know!) VoLTE Icon Fix: via FlashFire app: Flash OREO_VOLTE_ICON_HOTSPOT_FIX.zip (Flashes fine but doesnt fix it!!)
*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
Download & copy Oreo_Kevin71246Modded_v#.zip to phone
Flashfire
Open Flashfire on phone
Red + symbol->Flash ZIP or OTA-> Select Oreo_Kevin71246Modded_v#.zip-> Default options-> Check mark-> Lighting bolt at bottom-> OK
Phone will reboot to Aroma
Aroma Setup
Choose options as desired (Use vol up/down+power buttons to select! Touch is offset so if you use this touch BELOW your option to select)
Use very Bottom Right "Next" button if you see multiple
*Wait 3-5min on loading screen. If it doesn't boot after 10min: Hold Vol Down+Pwr buttons (~10sec) until phone restarts. After restarts, IMMEDIATELY hold VolUp + Home buttons. Should say Recovery. Wipe Data/Factory & Wipe cache. Restart Phone. Should load to Setup.
OPTIONAL: Root: Follow "Root Instructions" above, again.
Followup-Steps:
Fix Dialer: Phone Settings->Apps->Menu->Default Apps->Calling App->Select Phone
Known Issues:
Wifi Calling not working despite flashing Tmobile Wifi & Tmobile Wifi Settings app
Visual Voicemail not working (disabled until we can figure this out)
VoLTE Icon wont go away despite flashing known working fixes
Changelog:
Version 1: First build
Immediate References:
[Rom][ALL_CARRIERS_G930_CRF1][Stock_Oreo_Hybrid][Safestrap_Preinstalled]
Root For S7/S7Edge Oreo And Nougat
Project L s7 Google/Samsung Oreo Rom CRF1 Base
Credits:
(Im copying/pasting credits from other links since so many people participated I dont want to miss anyone!)
- @jrkruse & @klabit87 for root
- @Lanc-City for ROM base
- @gustco for eng boot.img
- @Raymonf for modified odin
- @afaneh92 for safestrap
- @me2151 for finding this method
- @tytydraco for some instructions
- @mweinbach for some instructions
- @Craz Basics for xposed on non rooted
- @partcyborg for finding the root method!
- @elliwigy for being great help and original S8 root
- @rayan-refoua for boot animation
- @FatalONEM8 - For posting Oreo OTA
- @stang5litre
- @jds3118
- @Krog18
- @klabit87 for S7 Safestrap
- @amarullz Aroma Installer
- @mrRobinson for adaway
- @Chainfire for Flashfire
- @JaeKar99 for Reactor_BootAnimation
- echoe rom and noname rom
- stang5litre Test Group
- Please PM me if you were forgotten!
Reserved1
Reserved2
Reserved3
Ayy mentioned. Good work on the rom ?
Okay I don't know what's going on here but I have never talked to you or never given you permission to reuse my Rom/work this is stealing my rom is still being worked on this thread must come down this is not cool
IF YOU WANT TO share something Make your own Rom My Rom/Work is not to be reused in any type of way I put a lot of time and work into it
Lanc-City said:
Okay I don't know what's going on here but I have never talked to you or never given you permission to reuse my Rom/work this is stealing my rom is still being worked on this thread must come down this is not cool
IF YOU WANT TO share something Make your own Rom My Rom/Work is not to be reused in any type of way I put a lot of time and work into it
Click to expand...
Click to collapse
Meant no offensive at all, I assure you. Did I completely misunderstand the point of the xda community? I clearly gave you credit and didn't say I created this from scratch, rather pieced it together, literally what every Dev here does. I am not doing this for money. I mentioned & thanked you, which is probably how you found this thread. All I am trying to do is give back to the community. I spent a TON of time going through guides, updating what I found, creating a guide, and testing this - I didn't just rebrand it.
That said, I did use part of your work so I'll give you the choice: can I use part of your work and allow the xda community to benefit, or do you want me to remove your segment & Lanc app this comes with?
Btw see the post above yours. And shouldn't this chat be on PM? For reference, what I used from you was your apks so I didn't have to redownload & retest them and aroma script for a starting point, but the script is 90% different at this point.
Again, I did not mean to offend, but please let me know if I have your permission. Thank you
Good news! We got @Lanc-City 's blessing to continue to use his base ROM & LancControl app. This XDA community is AWESOME! Don't forget to go and check out his original Mod'd ROM: Project L s7 Google/Samsung Oreo Rom CRF1
VoLTE icon fix
Not sure if this will work for everyone. Download System UI Tuner by Zach Wander from Play Store. Once in menu, go to TouchWiz, scroll down to IMS VoLTE Icon and toggle on then off. I did not apply the fix that you have the link for above, and I was able to uninstall the app and the icon does not come back.
Hey, I am trying to use your ROM but after I flash the zip file and finish set up with Aroma and reboot, I get stuck in the boot screen where the rainbow colored X symbol is spinning. I followed the guide exactly so I'm not sure what I'm doing wrong. Maybe my default options in flash fire are not correct? All the boxes in that screen are unchecked. Should I mount /system read/write? I just hit the checkmark and flash. Also I did hit Install Root with Interactive Governor, if that makes a difference. Any help? Thanks.
infamouz421 said:
Hey, I am trying to use your ROM but after I flash the zip file and finish set up with Aroma and reboot, I get stuck in the boot screen where the rainbow colored X symbol is spinning. I followed the guide exactly so I'm not sure what I'm doing wrong. Maybe my default options in flash fire are not correct? All the boxes in that screen are unchecked. Should I mount /system read/write? I just hit the checkmark and flash. Also I did hit Install Root with Interactive Governor, if that makes a difference. Any help? Thanks.
Click to expand...
Click to collapse
deleted, wrong thread
infamouz421 said:
Hey, I am trying to use your ROM but after I flash the zip file and finish set up with Aroma and reboot, I get stuck in the boot screen where the rainbow colored X symbol is spinning. I followed the guide exactly so I'm not sure what I'm doing wrong. Maybe my default options in flash fire are not correct? All the boxes in that screen are unchecked. Should I mount /system read/write? I just hit the checkmark and flash. Also I did hit Install Root with Interactive Governor, if that makes a difference. Any help? Thanks.
Click to expand...
Click to collapse
Copying/Pasting PM I sent you for others, and added some things:
Did you let the "rainbow" sit there for at least 10 min? (It should be 3-5 but who knows.) Are you soft-bricked in your current situation? If you start again, at "Install Stock Oreo:" does this at least restore your phone back to stock Oreo? If so, then try again and proceed with ALL the remaining steps again, CAREFULLY reading the instructions again & again.
Also, what phone model do you have? And I admit I haven't tested the CPU governors in the root script ; I ALWAYS chose none - I'll remove those options in the next version since I have tested them and there are plenty of CPU overclocking options once booted inside the ROM.
If you are able to restart this process and get stock Oreo back, AND chose NO CPU governors in the root script, maybe you want to either try "NO" to Google & Tmobile options just to make sure you can get Android booted- If it boots fine, then try the ROM again and pick Google and/or Tmobile to isolate any issues (things that are breaking)
Have you used ONLY what I provided, such as ODIN (version is important), etc?
Re Flashfire: Default options should be fine. The ROM script will set all the partitions, mounts, permissions, etc.
Good luck!
*Above response I guess is for overall troubleshooting the ROM, if any issues present themselves.
On another note: I'm actively working on this ROM as time allows. Trying to ease the install process, correct some issues, further customize, & improve...
kevin71246 said:
Copying/Pasting PM I sent you for others, and added some things:
Did you let the "rainbow" sit there for at least 10 min? (It should be 3-5 but who knows.) Are you soft-bricked in your current situation? If you start again, at "Install Stock Oreo:" does this at least restore your phone back to stock Oreo? If so, then try again and proceed with ALL the remaining steps again, CAREFULLY reading the instructions again & again.
Also, what phone model do you have? And I admit I haven't tested the CPU governors in the root script ; I ALWAYS chose none - I'll remove those options in the next version since I have tested them and there are plenty of CPU overclocking options once booted inside the ROM.
If you are able to restart this process and get stock Oreo back, AND chose NO CPU governors in the root script, maybe you want to either try "NO" to Google & Tmobile options just to make sure you can get Android booted- If it boots fine, then try the ROM again and pick Google and/or Tmobile to isolate any issues (things that are breaking)
Have you used ONLY what I provided, such as ODIN (version is important), etc?
Re Flashfire: Default options should be fine. The ROM script will set all the partitions, mounts, permissions, etc.
Good luck!
*Above response I guess is for overall troubleshooting the ROM, if any issues present themselves.
On another note: I'm actively working on this ROM as time allows. Trying to ease the install process, correct some issues, further customize, & improve...
Click to expand...
Click to collapse
So I did let it sit for a long time, maybe like 30 mins, but nothing happened. So I tried again from installing from stock and repeating each step. I'm using the odin files you supplied. Same thing. I was using install Google Apps and No T-mobile apps, and interactive governor for both situations. Stuck on boot animation screen. I did not try the options you suggested above since I eventually got it to work. So while stuck on the boot animation screen, I just ended up holding the Vol down, power and home until it rebooted and said entering recovery mode and let go before it went into download mode. From there I just wiped data, and cache, which may not be necessary, and then rebooted, and everything works. Thanks.
infamouz421 said:
So I did let it sit for a long time, maybe like 30 mins, but nothing happened. So I tried again from installing from stock and repeating each step. I'm using the odin files you supplied. Same thing. I was using install Google Apps and No T-mobile apps, and interactive governor for both situations. Stuck on boot animation screen. I did not try the options you suggested above since I eventually got it to work. So while stuck on the boot animation screen, I just ended up holding the Vol down, power and home until it rebooted and said entering recovery mode and let go before it went into download mode. From there I just wiped data, and cache, which may not be necessary, and then rebooted, and everything works. Thanks.
Click to expand...
Click to collapse
That's odd since the installer does exactly that. But I added this to the guide. Thanks for the feedback!
Thanks for the tutorial. Deeply appreciate the effort you put in foraging the resources and putting all the pieces together. The rom works great and all but I can't seem to get the lockscreen to display the wallpaper. It's just black lol. The adaptive clock works however. Would be grateful if you could drop a fix for this.
Alkan3 said:
Thanks for the tutorial. Deeply appreciate the effort you put in foraging the resources and putting all the pieces together. The rom works great and all but I can't seem to get the lockscreen to display the wallpaper. It's just black lol. The adaptive clock works however. Would be grateful if you could drop a fix for this.
Click to expand...
Click to collapse
(Not sure why I didn't get an email from XDA for this post.) Mind walking me through the exact place this setting is? Here? PhoneSettings->Lock screen and security->Clock and Facewidgets->Clock Style->Select a style for "Lock screen" tab at top->Done? (Im able to get these to work)
BTW, Im glad you found this thread resourceful! & Im working on another one, which will be better & more original. Takes a TON of time!
Hey i have two questions, if i'm on oreo already do i need to flash base? And, does this need an unlocked bootloader?
nam2amna said:
Hey i have two questions, if i'm on oreo already do i need to flash base? And, does this need an unlocked bootloader?
Click to expand...
Click to collapse
Your stock oreo should work without issues but I always flash his stock firmware just in case(it's smoother too I think). And no, it doesnt require an unlocked bootloader.
Oh and happy modding
Alkan3 said:
Your stock oreo should work without issues but I always flash his stock firmware just in case(it's smoother too I think). And no, it doesnt require an unlocked bootloader.
Oh and happy modding
Click to expand...
Click to collapse
There are a couple ways an installer can work for custom rom mods like this: start with base then remove everything we don't want. OR: delete everything then add in what we want. This rom happens to work with the latter method. You can see why the base would be so important with the first method. (Because if we don't start with a given base then we can't predict the results because we don't know what u froze or deleted). Regardless, for expected & reliable results, I would always start with an Odin flash of stock for a rom like this. Roms like this are different than vanilla AOSPs because we strip what Samsung & tmobile brewed up, and we often then refer to it as a hybrid- as opposed to vanilla aosp which would be google only & only Samsung for drivers, etc. Hope that helps.
Btw I'm working on another rom with tmobile wifi calling working. I had to start from scratch, literally to get it working. Btw I'm curious if anyone else got it to work after the fact with a custom rom. If so, PLEASE chime in & let me know. Thanks!