Hey there. Is it possible to somehow add "reboot to 2nd rom" under the reboot option in the power menu?
(Or make a shortcut to it from STweaks since I have that option inside STweaks.)
Im running cm10.1 nightly on sgs2
/ Jonis
look at here..
the little app doesn´t work for me..maybe for you..
you can do it in terminal or via shellscript with su (i prefer smanager..but thats your choice )
1st rom:
echo 1 > /sdcard/.nextboot ; sync ; reboot
2nd rom:
echo 2 > /sdcard/.nextboot ; sync ; reboot
15 minutes when we not using wifi tethering is not too much, right? Never stop or after 2 hours of inactivity is better :laugh: .
1. Thanks to TrevE :good:
2. Root
3. Download WiFi Tether for Root Users 3.3-pre2 *** EXPERIMENTAL ***
4. Install
Code:
wifi_tether_v3_3-pre2.apk
5. Run WiFi Tether - TrevE Mod
6. Press Menu button and then settings
7. Now Settings that worked for me:
* Change Device-Profile --> Generic ICS/JB (wlan1)
* Change Setup-Method --> Auto
* Check --> Enable WiFi-Encryption
* Change Passphrase --> must be between 8 and 30 characters long
* Change SSID --> AndroidAP (You can try another one, maybe will work)
* Change Channel --> Channel 11 (2462 MHz)
* Optional: Check --> Idle Shutdown
* Set Idle Limit --> 1 - 120 minutes
* Change LAN --> 192.168.2.0/24
* Check --> Routing fix
* Change preferred DNS --> 8.8.8.8
* Change alternate DNS --> 8.8.4.4
* Check --> Disable Wake-Lock
* Press back button
* Now You can press to start really usable tethering on our beloved phone
* Tethering start with one error --> Enabling MSS Clamping... (Menu --> Show Log) Don´t worry
I really hope that works for You Too.
For this settings I´m use hostapd.conf file in /system/etc/wifi directory
I will try it.
Enviado desde TheDarkRoom
settings on the thrill 4g - ICS
Not working on the thrill 4G with stock ICS AT&T rom (v30b) and rooted. I dont even get the data counters at the bottom. I tried tho! thanks for the thread!
Sorry for little misleading. This tut was created for ported xbsalls ics rom.
Sent from my LG-P920 using xda app-developers app
.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
OFFICIAL CyanogenMod CM13
for SGH-M919 (T-Mobile) jfltetmo
.
I will not be held responsible for you messing up your phone. It worked for me.. It SHOULD work for you.
This does trip your Knox Warranty Bit. This does void your warranty..
= Windows 7 ONLY: Download to your PC: Samsung KIES3 - found [HERE].
= Download to your PC: ODIN 3 v3.10.7 - found [HERE]
= Download to your PC: TWRP Recovery 2.8.4.0 - found [HERE].
= Download to your Phones External MicroSD Card: TWRP Recovery 3.0.2-0 - found [HERE].
= Download to your Phones External MicroSD Card: OFFICIAL CM13 ROM - found [HERE].
= Download to your Phones External MicroSD Card: Open GApps 6.0.1 Nano - found [HERE] (Look for 'ARM-6.0-NANO-[DATE].zip').
= Download to your Phones External MicroSD Card: MakePermissive-CM13-GalaxyS4 - found [HERE].
= Download to your Phones External MicroSD Card: SuperSU-v2.68 - found [HERE].
= Power ON your phone and boot into the normal system.
= CHARGE YOUR PHONE TO AT LEAST 80%.. if your battery runs out while your flashing or loading you will be in trouble!!
= Windows 7 ONLY: Install KIES3 on your PC -- You must install KIES3 in order to install the Samsung phone drivers -- You do not actually need to use it. (Windows 8/8.1/10 does this automatically on the next step).
= Win 7/8/8.1/10: Plug your phone into your PC via USB cable.. WAIT for your PC to finish installing drivers.
= TRANSFER all the needed files to your phone now.. put the files in a 'ROM' folder on your External MicroSD Card.
= Unplug your phone from your PC.
= Power OFF your phone.
= Bookmark this page on your PC.. then REBOOT your PC to ensure you exited out of KIES3 install and/or fully installed the drivers.
= Boot your phone into DOWNLOAD MODE (While Powered OFF - HOLD Power, Home, and Volume DOWN buttons for 6 secs, let go as soon as the screen changes).. then press the Vol UP button.
= Run ODIN3-v3.10.7 on your PC -- use "Run as Administrator".
= Plug in your phone (phone is still in Download Mode) via USB cable to your PC.
= In ODIN3: Make sure you see "COM #" and "ADDED!!" -- SEE HELP IMAGE HERE
* If you Do NOT see the 'COM#' and 'ADDED!!' then Samsung Drivers is Installed INCORRECTLY!
* If you DO see the 'COM#' and 'ADDED!!' then you Can Continue Below to the Next Step.
= Insert the 'TWRP-2.8.4.0-jfltetmo.tar' file in "AP" - Click START -- SEE HELP IMAGE HERE
= Wait for your phone to reboot into system.
= You can unplug your USB cable now.
= Power OFF your phone.
= Boot into TWRP Recovery (While Powered OFF - HOLD Power, Home, and Volume UP buttons for 6 secs).. Let go of the buttons after the vibrate but just before you see the small blue writing appear at the top.. I was holding mine down for too long and it would just boot like normal and not recovery mode.
= Install TWRP 3.0.2-0 by Clicking 'INSTALL' > 'Select Storage' (near the bottom) > 'Micro SDCard' > 'OK' > Click 'INSTALL IMAGE' > Find your TWRP-3.0.2-0.img you downloaded > Select 'RECOVERY' > 'Swipe to Install'.
= Go back to Main Menu > Reboot > Recovery
* This will reboot you back into TWRP and your Recovery version should be changed to the 3.0.2-0.
* Your custom recovery is now successfully installed!
= MAKE A CURRENT BACKUP: Tap 'Select Storage' near the bottom > Select "Micro SDCard" > then "OK"
= Backup: Tick (enable): EFS Only > Swipe to Backup -- Hint: Change the filename from 'Auto-Generate' to 'EFS-ONLY-'
* Note: You should only backup EFS by itself.. You only need to backup EFS one (1) time ever.
= Backup: Tick (enable): Boot, Cache, Data, Preload, Recovery, and System > Swipe to Backup
= Go back to Main Menu
= 'WIPE' > 'ADVANCED WIPE' > Tick (enable): Dalvik/ART Cache, Cache, Data, Internal Storage, Preload, and System.
= 'SWIPE TO WIPE'
= Go back one menu then 'FORMAT DATA' - type 'YES' and press blue checkmark.
= Go back to Main Menu
= Install CM13 ROM by Clicking 'INSTALL' > 'Select Storage' (near the bottom) > 'Micro SDCard' > 'OK' > Find your Official CM13 ROM you downloaded.
= Install Open GApps by Clicking 'ADD MORE ZIPS' > Find your Open GApps you downloaded.
= Install MakePermissive by Clicking 'ADD MORE ZIPS' > Find your MakePermissive you downloaded. (see Root/Superuser notes below!)
= Install SuperSU by Clicking 'ADD MORE ZIPS' > Find your SuperSU you downloaded. (see Root/Superuser notes below!)
= 'SWIPE to Confirm Flash'.
= Wait for completion.
= 'Wipe Cache and Dalvik'.
= 'REBOOT' into system.
* Your System is now successfully Installed!
* After your initial setup you need to tweak a few things:
= Settings > About Phone > Build Number > tapped 7 times = 'Developer Options'.
= Settings > Developer Options > Advanced Reboot = ENABLED.
= Settings > Developer Options > Root Access > Apps and ADB enabled.
= Settings > Location > Change to 'Device Only'.
= Settings > Location > 3-Dots > Scanning > DISABLE (untick) Wifi Scanning and Bluetooth Scanning.
= Pull-Down Notification Panel > GPS (Device Only) changed to disabled.
= App Drawer > Google > 3-Lines > Settings > Now Cards > Turn OFF
= App Drawer > Google > 3-Lines > Settings > Voice > OK GOOGLE Detection > Turn OFF
= RUN SuperSU from App Drawer > SuperSU. (See SuperSU notes below)
= Install and RUN Busybox by Stephen (Stericson) from the Play Store.
= Enjoy!
* ROOT/SUPERUSER NOTES:
= A basic Superuser is pre-installed with this Rom. It does Not give you control. You will not be able to use the traditional SuperSU from the Play Store (updating the SuperSU binaries will FAIL). That's why I included the new 'SuperSU-v2.68'. It has updated binaries and works great with our phones with OFFICIAL CM13 ROM. SuperSU Pro Key can be installed from the Play Store. Busybox must be also downloaded from the Play Store and Installed.
= When flashing SUPERSU you will get a bootloop unless you flash 'MAKEPERMISSIVE'. MakePermissive is needed to change the SELinux Kernel from Enforcing to Permissive.. It does need to be flashed BEFORE you flash the SuperSU. SELinux is a Linux kernel security module that provides a mechanism for supporting access control security policies.
* NOTES:
= Restore during setup does not restore properly from any previous CM12.1/CM13 build, what I mean is that I first selected my most recent setup restore and it went to 'Checking..' then looped right back to 'Choose Restore Point'.. so I chose "Don't Restore".. then it still restored all my Apps.. so thats a bit strange.
* IF YOU HAVE ANY PROBLEMS WITH MOBILE DATA, PHONE CALLS, OR TEXT MESSAGES ALWAYS CHECK YOUR APN SETTINGS! *
.
.
Official CM13
Custom Boot Animation(Flashable .ZIP for TWRP Recovery).
[DOWNLOAD HERE]
.
.
I have made an Ultimate Audio collection which includes a TWRP Flashable ZIP that contains over 1000 RINGTONES, NOTIFICATIONS, and ALARM SOUNDS.. pretty much every sound ever included in a device.. LOL! Its 181 MB... It might be a little too much but its also AWESOME!
If they all don't show up then you need to reboot so it can rescan for new audio files. Mine didn't detect them all right after I flashed them but after a reboot they all showed up.. File Permissions are already changed for you so its ready to go.
I cleaned up all the crap that didn't play and had crazy filenames. I can confirm that all files are playable.
CM13-Ultimate_Audio >> https://www.androidfilehost.com/?fid=24533100289590866
.
BT crashes during call, not usable when using for call...music works fine with BT....also Android.acore is keeps on crashing making phone unusable....reverted to Jdct....
Sent from my SGH-M919 using Tapatalk
smilingcruel said:
BT crashes during call, not usable when using for call...music works fine with BT....also Android.acore is keeps on crashing making phone unusable.
Click to expand...
Click to collapse
You are correct.. when making Bluetooth calls is freezes and must be rebooted.
Creeper36 said:
You are correct.. when making Bluetooth calls is freezes and must be rebooted.
Click to expand...
Click to collapse
Yup...I don't understand, but I may be asking a dump question...if jdcteam is sourced from cm13, why not official cm13 BT doesn't work...I never had any BT issues with official cm 12 or optimized cm13 jdcteam... Not sure why!!!![emoji33]
Sent from my SGH-M919 using Tapatalk
smilingcruel said:
Yup...I don't understand, but I may be asking a dump question...if jdcteam is sourced from cm13, why not official cm13 BT doesn't work...I never had any BT issues with official cm 12 or optimized cm13 jdcteam... Not sure why!!!![emoji33]
Click to expand...
Click to collapse
Things are forked differently from build to build.. it takes some trial and error to find the right fork then edit it to work with the ROM. I expect problems (like SuperSU not working right) and it will take some time but Official CM13 for jfltetmo is HHUUGGEE! Its the first step in Official CM13 Status.
Creeper36 said:
Things are forked differently from build to build.. it takes some trial and error to find the right fork then edit it to work with the ROM. I expect problems (like SuperSU not working right) and it will take some time but Official CM13 for jfltetmo is HHUUGGEE! Its the first step in Official CM13 Status.
Click to expand...
Click to collapse
I agree....I was eagerly waiting for official cm13 for m919...I tried several 6.0.1 Roms but settled with JDCTeam as it was 100% prefect for me....may be I wait for few weeks and then I will test again official cm13....thanks
Sent from my SGH-M919 using Tapatalk
Hopefully will improve with the time
smilingcruel said:
I agree....I was eagerly waiting for official cm13 for m919...I tried several 6.0.1 Roms but settled with JDCTeam as it was 100% prefect for me....may be I wait for few weeks and then I will test again official cm13....thanks
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Ditto on the JDCTeam. CM13 was hanging on me every time I ended a call using the Bluetooth, plus it was constantly giving me the Bluetooth Sharing error. Here's my review on that release.
I last used the 4/20 nightly before switching. How has everyone's experience been since?
BTW - Thank you Creeper36 and all the other maintainers and CM developers. I really appreciate your efforts and bringing CM13 to our devices.
I'm swinging back and forth without any problems and it looks like CM13 official is getting smoother each nightly version....
Only thing is work around for Bluetooth that if you have device that can pair phone and media you have to tick one off to work....except that I have very good battery with custom doze setting that will go to right after my screen is off and I can go 2 days without using surfing ....ordinary usage
Sent from my SGH-M919 using XDA-Developers mobile app
---------- Post added at 01:11 AM ---------- Previous post was at 12:47 AM ----------
Like you seehttps://vimeo.com/165256220
Sent from my SGH-M919 using XDA-Developers mobile app
---------- Post added at 01:20 AM ---------- Previous post was at 01:11 AM ----------
I would like to know how many of you are using same modern
Sent from my SGH-M919 using XDA-Developers mobile app
samprocat said:
I would like to know how many of you are using same modern
Click to expand...
Click to collapse
M919UVUFOK3 is the most current, up-to-date version of the bootloader and modem for the SGH-M919. I am using this and it works great!
Any one tested BT in the latest build...looks like Optimized CM13 by JDCT is having a solution for BT issue.....
Odin3 gives me a "PASS!", but when trying to boot to TWRP recovery mode, it just loads the stock android recovery. I've used all the versions listed above and am on an Galaxy S4 SGH-M919. Any troubleshooting tips?
[SOLUTION] Under 'Options' untick the Auto Reboot tab. After you get the "PASS!" message, remove battery and put back in place, then go directly into recovery mode with the usual button holds.
Will this also work on s4 E300K? If not can I get a link for CM13 on e300k? Thanks.
fonefonefone said:
Odin3 gives me a "PASS!", but when trying to boot to TWRP recovery mode, it just loads the stock android recovery. I've used all the versions listed above and am on an Galaxy S4 SGH-M919. Any troubleshooting tips?
[SOLUTION] Under 'Options' untick the Auto Reboot tab. After you get the "PASS!" message, remove battery and put back in place, then go directly into recovery mode with the usual button holds.
Click to expand...
Click to collapse
I also ran into this problem of only being able to boot into stock recovery and not TWRP-2.8.4.0, after installing it through Odin. Unfortunately, at the time, I didn't see the checkbox you mention here.
So what I did was:
1 - Rooted the phone through Odin with CF-Auto-Root (download M919 4.4.4.rar)
2 - Updated to the latest SuperSU
3 - Ran SuperSU and disabled KNOX (in case that was what did the overwriting)
4 - Reinstalled TWRP-2.8.4.0 through Odin, and then flipped out the battery right after Odin had successfully completed.
I was then able to boot into TWRP recovery using the usual button combination. I wish I had seen this checkbox last night!
I've done all steps and i'm on cm13, the only drawback i'm experiencing is that the charge is not lasting as much as i'm used to, and sometimes the phone overheats a little bit with no activity at all. Thanks for the guide is pretty good.
I've have my cell with KK version, i can install it?
Hi, I am new in here. I am trying to install my first ROM on my S4 device, but when I click on Download I get an error saying "Over Quota". Anyone know any other place where I can download this ROM or something better?
Thanks
Not responsible for any damage.
OmniROM Android 6.0 for Panasonic P81
Requirements: Root & CWM installed
Root download*Framaroot apk open the Framaroot application in your smartphone. Once done, select â??Install Superuserâ? under â??Select an action to execute after rootâ? and then select â??Barahirâ? exploit. This will start the rooting process.
To start the CWM recovery installation process, you will need to download*MTKVCOM Drivers*and*MTKDroidTools*to your PC. Connect pc to device and enable usb debugging. (password: awaisking)
Extract the MTKDroidTools zip package and run.
Now Click on the â??root, backup, recoveryâ? tab. Now in that tab, choose â??To use Boot from Phoneâ? option and click on â??Recovery and Bootâ??.
Now a Pop up window will ask you to automatically make CWM Recovery Click Yes. Want to flash Patched Boot.img. Click on â??Noâ??. Want to install the created recovery to phone. Click on â??Yesâ??.
Now Reboot in recovery clear cache, data and install the zip file. Once done reboot the device.
Download:
ROM OmniRom r62
Gapps Google Apps
SuperSu SuperSU
What's working ?
> Camera working*
> Video rec working via Camu app
> No Need to reboot for apps to apear in app drawer
>*Hotspot*Fixed
> BT Fixed
> FM fixed
> GPS fixed
> Data working
> 1080p playback in gallery fixed
> youtube 720p fixed
> youtube live playback fixed
> No Sim fixed
> No Network drop found
> USSD Fixed
> Autorotation Fixed
> All sensors working
> After Reboot QuickSetiings Too
> Rest Are As CM13
> Too many features
Bugs :-
VPN
Camera FC after few clicks and video rec in stock cam (Workaround :- Use Camu app from Playstore)
Thanks:
Credits/Thanks To:-
[email protected]
Tirth Patel (Built from Source)
TLS
Omni Devs (https://omnirom.org)
Ferhung
Fire855
It's been aborting installation by showing operation not supported on transport end point...what I have to do? I can't flash this ROM
Mod edit: Thread closed