Related
Hi,
I'm using the last CM7 ROM (20110509 update)
I have two main issue:
1. My battery get down in ~10% every 1 hours mean my phone can work for only 10 minutes without heavy functions, I'm using sync every 1 hours not push and short phone call.
Any idea ?
2.
I can't send MMS, tried to restart, try using other MMS APS like goSMS but still can't send MMS
I cant get the google apps to work. I did install gapps in recovery mode but the apps does not show in my galaxy.
cm 7 faq & discussion thread : http://forum.cyanogenmod.com/topic/15278-all-models-cyanogenmod-7-faq-user-discussion/
You should post questions over there...
But anyways, for the battery, there are many things you can try.
1) go to the wifi advanced settings and put wifi sleep to "never", it may make the phone unable to sleep otherwise
2) disable sync.
3) look for any app that might be using battery in the background (in battery stats) and delete it (if you don't need it) or kill it every time...
4) try undervolting with a custom kernel such as tk-glitch's : http://forum.xda-developers.com/showthread.php?t=1041532
5) if you DO have a custom kernel, try reinstalling stock cm7 (or see if the kernel has an update) and see if the kernel is the culprit
6) lower your screen brightness, disable wifi/gps/bluetooth, the usual stuff...
7) reboot in recovery with a full battery and wipe battery stats (also, wipe cache/dalvik cache while you're at it)
For the MMS I don't know, I read something about it being fixed but I never actually tried it.
About gapps : factory reset? There might be another solution though, but I have no clue...
Check if your message center number has been set properly...
Sent from my GT-I9000 using XDA App
in the subsequent posts below, you will find all the info you need for not only the device but the ROMs I have had my hands in.
each person who I pulled the files from will get a thanks in the posts as necessary
NonSense 1.04
Disclamer: these files are meant specifically for the HTC Desire 510. Use these files at your peril, you assume any responsibility for loss or damage that may result from use of these files or procedures. what has been included in this tutorial is for the HTC Desire 510
You have been warned.
note: from now on CRI signifies cricket, and B-S signifies sprint/boost if those signifiers aren't used, it applies to both type of this phone
now to the goodies.....
List of supplies:
1. Phone (HTC Desire 510)
2. USB cord that syncs with the PC
3. USB drivers installed for the phone
4. the zip files from this location. click here
4.1 there are 2 different versions of the same ROM, but the *1.04-lean.zip is US only (refer to changes to see why).
4.2 CRI for cricket/att, B-S for boost/sprint
5. read these instructions completely before attempting
before we get started make sure you have supersu (which can be downloaded from here), and NonSense1.04.zip copied to the root of your external SD card
NETWORK UNLOCK (I.E. switching services)
as this phone is LTE compatible, it takes a SIM card no matter the service to receive calls and data. so it stands to presume all you need to do is network unlock the device (Sprint calls it UICC unlock, others it's the Network Unlock Code)
the phone needs to be network (SIM) unlocked in order to switch it from cricket to sprint, or from sprint to virgin mobile, etc.
to network unlock the phone:
1. make sure you are on stock ROM (the one that came with the phone, not the one listed in this post nor CM)
2. call the respective original service provider of the phone (i.e. cricket, sprint, etc.) and tell them that you are leaving the country (like to Australia) and you want to unlock the SIM so you can use your device for service down there.
2.1 if you bought the phone second-hand or don't have service on it, you will have to find a reputable unlock service online
2.2 for sprint customers, your account HAS to be at least 6 months old before they will give you the UICC(SIM unlock) code
2.3 for boost customers, your account HAS to be at least a year before they will give you the UICC(SIM unlock) code
3. once you have the SIM unlock code, pull battery from phone, remove the original SIM, put your services respective SIM in (i.e. originally a cricket phone now running a T-Mobile SIM), put in battery, boot phone, and enter the unlock code where it asks.
4. once your back into device, you'll notice you will have no data.
4.1 what needs to be done is to program the APN (google will be your best friend here - for example sprint lte apn settings, or T-Mobile lte apn settings).
5. now that you have the APN settings, you can program them into the phone.
5.1 APNs can be found in the device by going to settings, then mobile data, clicking on access point names. in there in the upper right hand corner should be 3 dots that are verticle. click on that and then on new APN.
5.2 add the respective settings, click save and then make sure it has a green dot next to it.
6. sit back and enjoy the fruits of your labor
APNs for this device can only be written once the phone has been UNLOCKED and the original (cricket) service providers SIM is NOT inserted, and your using another service Provider ( sprint, T-Mobile, etc.) SIM.
UNLOCKING BOOTLOADER
1. for the drivers, use the ones contained here in the HTCDrivers.zip and extract them to the desktop
1. extract and use the file contained in adb.zip to flash unlock token
2. follow this tutorial and choose all other supported devicess when it asks about device.
INSTALLING TWRP AND KERNEL
in the adb file you should notice a file called recovery.img. that is TWRP recovery for the device
there is also a file called boot.img. this will allow read/write permissions at the System level once root is obtained
if you have either the sprint, boost or another service provider's variety of this phone, try flashing their respective kernel after you install the ROM or before you root (no guarantees that flashing the respective kernel will work. as I have the cricket variety of this phone, I am only developing for that one)
1. from home screen, go to settings and scroll down to power and then scroll all the to the bottom of that and uncheck "fast boot"
2. shut down phone completely
3. go back into fastboot (vol down + power)
4. Select fastboot from the menu list and press the power button.
5. open command prompt and use the CD command to get it to the root of the adb folder (CD C:/users/sky/desktop/adb).
6. plug in device and wait for it to say fastboot USB
7. type in command prompt "fastboot flash recovery recovery.img' (should complete within 4 seconds)
8. in the same command window type "fastboot flash boot boot.img" (should complete within 4 seconds)
8.1 step 8 can be skipped if your just flashing *NonSense1.04*.zip
9. pull battery once that is completed and put it back in.
10. power device on (skip this step if rooting)
OBTAINING ROOT (can be skipped if installing NonSense1.04 as it's already rooted)
1. re-enter fastboot mode and choose recovery. press power to select it
2. once in recovery select install and go to external SD and select the supersu update package.
3. once selected, you should see a slider on the bottom of the screen that says swipe to confirm. do so
4. once package is installed you should see a button that says reboot device. do so
5. wait for it to fully load
INSTALLING NonSense 1.04
1. re-enter fastboot mode and choose recovery. press power to select it
2. once in recovery select install and go to external SD and select the NonSense1.04.zip.
3. once selected, you should see a slider on the bottom of the screen that says swipe to confirm. do so
3.1 beware, it may take a bit to install. just be patient, it's working.
4. once package is installed you should see a button that says reboot device. do so
5. wait for it to fully load. be forewarned, it may take about 15 minutes to load
CHANGES
CRI versions
1. DEODEXed the ROM
2. added external SD support into the ROM
3. fixed FC on clock app (switched clock/alarm from stock worldclock.apk to AOSP clock)
4. changed bootanimation.zip, boot sound, and stock ringtones and sounds.
5. added more stable kernel to flash file.
6. added Pandora (no-ads vers. 5.5), SpiritUL (FM radio support), Facebook, RootBrowser, Adobe reader, Adobe flash player, and Viper4android (DSP/equalizer)
6.1 all apps that have been listed in 6 can be uninstalled without the need for root
7. root and SU have been added and are up to date in this rom as of 11:45PM MST on 3/1/215
8. added apns-conf.xml from CyanogenMod
9. got native APP2sd support thanks to pattyboi's kernel
B-S versions
1. mostly DEODEXed the ROM
2. fixed FC on clock app (switched clock/alarm from stock worldclock.apk to AOSP clock)
3. changed bootanimation.zip, boot sound, and stock ringtones and sounds.
4. added more stable kernel to flash file.
5. added Pandora (no-ads vers. 5.5), SpiritUL (FM radio support), Facebook, RootBrowser, Adobe reader, Adobe flash player, Wifi Tether, and Viper4android (DSP/equalizer)
5.1 all apps that have been listed in 5 can be uninstalled without the need for root
6. root and SU has been added
*1.04-lean
list of removed apps
1. Dropbox (can be found in playstore)
2. Google plus (can be found in playstore)
3. Hangouts (can be found in playstore)
4. HTC Dot View(can be found in playstore)
5. keyboard language packs for Arabic, Chinese, English UK, French, German, Greek, Italian, Portuguese, Russian, and Spanish (not in play store) if needed, flash language.zip found here
6. VPN dialogs (not in play store) if needed, flash missing.zip found here
7. HTC Zoe (can be found in playstore)
BUGS
CRI versions
1.USB internet pass-through not working
2.WiFi direct (miracast) not working
3. want to get rid of annoying volume too loud warning
B-S versions
1. native hotspot says internet when connected to win 7 machine, but will not allow it to go through. Have included wifi tether as a workaround until the issue can be resolved
THANKS
CRI versions
I thank wolfaas12345 for his awesome tutorial on bootloader unlocking, pattyboi for providing a more stable kernel, and chainfire for providing a great solution to provide the SU binary and app for rooted devices. and of course, CraviingCritic for providing the original ROM in which this wouldn't be possible
B-S versions
I thank wolfaas12345 for his awesome tutorial on bootloader unlocking, pattyboi for providing the current kernel, and chainfire for providing a great solution to provide the SU binary and app for rooted devices. and of course, LarryBoyG for providing the original ROM in which this wouldn't be possible
please feel free to let me know if there's any issues with this release and i will fix them as they are found for now as this device is the one i primarily use as of right now.
I will also be keeping the links updated for as long as I own the device (being that my HTC Desire 510(Cricket) is network unlocked, that may be a long time - or until I get a better device).
UPDATES
for those of you who have downloaded the ROM since first release, I will include an CRI_NSupdate.zip or B-S_NSupdate.zip file found here. it will include the changes I have made to the rom since it's initial upload.
the file by the name of NSupdate.szip will include update that pertain to both the CRI and B-S ROMS
to install the updates, just put the update file onto the root of the SD card, reboot into recovery, choose install, pick the update file, swipe the blue button on the bottom, reboot and enjoy.
EDITING THE BOOTUP
location of files mentioned is in /system/customize/resource
to change boot animation
1. find your favorite boot animation
2. rename it to AIO_bootup.zip
3. copy/move and overwrite the original with a root explorer to /system/customize/resource
to change the boot sound
1. find a sound file you like and want to hear every time the phone boots (can be changed at any time)
2. convert it to wav (the file has to be wav in order for the phone to recognize it)
3. rename it to CRICKET_LOGO_24bit28k_STEREO.wav
4. copy/move and overwrite the original with a root explorer to /system/customize/resource
reboot and enjoy...
THINGS NOTICED WHILE CREATING ROMs
1. both (cricket and boost/sprint) phones are exactly the same except for the boost/sprint ones contain a CDMA chipset.
1.1 the only things I had to change from the cricket rom to the boost rom was apns.xml in framework-res, apns-conf.xml, and the preferred network type in build.prop.
2. all kernels work for both (US) versions
3. the same recovery is used on both (US based) devices
so essentially, if we develop for the boost/sprint version of the device, change a few things, it will be ready to roll for the cricket version as well
TO FIX NATIVE TETHER ON B-S VERSIONS
1. Install Script Manager – SManager app from the Play Store.
2. Open the app and grant it root access when prompted.
3. Now, navigate to /system/etc/init.d and tap “tether” script.
4. Click on SU and Boot (Android skull and gear icons, respectively)
5. Click on Run and Save options.
The issue should be fixed now. Reboot and enjoy!
thanks goes to qwerty6532 and LarryBoyG for the fix. now to add that permanently to the ROMs and then they'll be absolutely stable enough for me to be happy and start working on CM11
CM11
I will be building CM11 for the device for both the cricket and boost models. look for the info here as I update it a I need
****edit**** ok so I figured out some of the issue with CM11 not wanting to install apps. I got the internal memory pulling the 1.1 gbs but now I need to symlink the external memory where it goes.
****edit**** so I have figured out what needs to be done...... the kernel for CM11 needs to be built from the ground, up (or one needs to be built that is compatible with it). i'll upload the current one that fixes the memory error (look in downloads).
reserved
so as i have not been actively developing on the phone i will no longer supply updates. all flash files are up to date as of 8 months ago and should be working with out an issue.
again, reserved
same to you...
This would have to be one of the most comprehensive tutorials I have read. 10 out of 10 and kudos. Pity I have a 64 bit device and can't use most of it lol.
Burtrum57 said:
This would have to be one of the most comprehensive tutorials I have read. 10 out of 10 and kudos. Pity I have a 64 bit device and can't use most of it lol.
Click to expand...
Click to collapse
if I had a 64-bit version for this device, I would have it out as soon as I could. and thanks
Great job. Off and running now
I'm not sure how to add the tether fix to the ROM. Not really a developer more of a tester.. Wish I could get into developing don't really know where to start lol.
If you need any help testing or working on CM11 for Boost shoot me a PM I'd be glad to help
Sent from my 0PCV1 using XDA Free mobile app
Question to you Schizoidd......If I install the new 1.04lean over the previous build, do I still need to flash that update or is is already included in 1.04lean. I already falshed that some time ago when you first put it out, so I'm just not sure if its needed again or not. Thanks bro.
CSP III said:
Question to you Schizoidd......If I install the new 1.04lean over the previous build, do I still need to flash that update or is is already included in 1.04lean. I already falshed that some time ago when you first put it out, so I'm just not sure if its needed again or not. Thanks bro.
Click to expand...
Click to collapse
When you flash the new one, wipe the system partition and then use an explorer to remove v4a from the user apps. Which is located in /data/apps and reboot
qwerty6532 said:
I'm not sure how to add the tether fix to the ROM. Not really a developer more of a tester.. Wish I could get into developing don't really know where to start lol.
If you need any help testing or working on CM11 for Boost shoot me a PM I'd be glad to help
Sent from my 0PCV1 using XDA Free mobile app
Click to expand...
Click to collapse
Well it's added to it. It just needs to be activated for now until I can figure out how to add it to automatically start from the first run of the Sprint/boost ROM
schizoidd said:
When you flash the new one, wipe the system partition and then use an explorer to remove v4a from the user apps. Which is located in /data/apps and reboot
Click to expand...
Click to collapse
Sorry, not following "wipe the system partition" ???
CSP III said:
Sorry, not following "wipe the system partition" ???
Click to expand...
Click to collapse
if you in recovery, go to wipe and then advance wipe and check system. wipe it like u would as if ur doing a factory reset
schizoidd said:
if you in recovery, go to wipe and then advance wipe and check system. wipe it like u would as if ur doing a factory reset
Click to expand...
Click to collapse
Yeah, I figured as much. Should have been clearer with my ? Is that before or after I flash the new lean. I though if I did it after, that it would set me back to square one. As in having to start fresh setting everything up again, which I really dont want to have to do. Apologies for my unclearness.
CSP III said:
Yeah, I figured as much. Should have been clearer with my ? Is that before or after I flash the new lean. I though if I did it after, that it would set me back to square one. As in having to start fresh setting everything up again, which I really dont want to have to do. Apologies for my unclearness.
Click to expand...
Click to collapse
it'll leave ur data alone, just delete the OS. do not touch internal memory, davlik, data, or cache and ur stuff will be safe. I have done it and my stuff is fine
schizoidd said:
it'll leave ur data alone, just delete the OS. do not touch internal memory, davlik, data, or cache and ur stuff will be safe. I have done it and my stuff is fine
Click to expand...
Click to collapse
Right on buddy. I'll take you at your word on it. I've never had to do that before so it naturally made me a little nervous. Not that I couldnt have just restored a backup, but still . Many thanks.
Problems
System UI force closes and power button doesn't turn the screen back on when I flash the latest cricket version.
schizoidd said:
I
for those of you that build the kernels, do you think u can build one that is AOSP and compatible with the device for android 4.4.4?
Click to expand...
Click to collapse
we cant really do a "aosp" kernel because of htc's modifications to the board and pins,and they have their own dtb issues...im 99% sure mine works with android 4.4.x because of larry using it in gpe,just repack the ramdisk the zimage and it should be okay
Bobby060 said:
System UI force closes and power button doesn't turn the screen back on when I flash the latest cricket version.
Click to expand...
Click to collapse
If you're going from bone stock to this, you need to do a factory data reset. Just make ssure you back up your data and use nandroid manager to pull it data back into the new ROM
ROM IS TESTED ON 2 DEVICES AND FORCE CLOSES SHOULD BE GONE. AFTER RUNNING DO CHECK PERMISSIONS IN MiASSISTANT (check also accelarator/settings/disable "lock screen boost" and set protected apps list ; also set right permissions for apps not to sleep/stop....) AND PERMISSIONS UNDER BATTERY SETTINGS PHONE....
Made an AROMA SL!M DF!NR rom of the chinese A2017 V2.0 B13 MiFavor 5.0 version focused on :
* Force closes on google apps
* JoJoc Battery Tweak : https://forum.xda-developers.com/axon-7/how-to/tweak-jojoc-tuning-battery-focused-t3704831
Thnx @nfsmw_gr for our work together ! Gave me an amazing 8.30h SOT !
*EDIT : as this BXSRVEngine tweak may interfere in some cases with your dialer app and may cause a higher volume on your in-call or speakermode and can not be adjusted in some cases, I advice better not to install this tweak in aroma features - it was just intended to have some better pics/video quality but then again not that necessary.
BXSRVEngine : https://forum.xda-developers.com/an...recompeliren-bravia-engine-x-reality-t3141461
SUITED FOR ALL VERSIONS
Just follow procedure in detail and you should be OK !
Hope you’ll E N J O Y !!!
Based on : A2017 V2.0 B13 MiFavor 5.0
INSTALL : ( TWRP ) IN FOLLOWING ORDER !
I do advice to install :
JoJoc and (BXRVEngine) and either SuperSU or Magisk to check all features are working
Let’s begin….
0. In case you want to reflash your own apps backup your personal apps with f.e. TB, ZipMe... (or whatever)
00. running TWRP 3.1.1.0 (!)
1. Make a full backup of your current device in TWRP ! (use it to RESTORE if necessary) DON’T FORGET !
2. Wipe cache / dalvik / data / system
3. Install but do not boot : A2017 V2.0 B13 AROMA MiFavor 5.0 SL!M DF!NR : https://androidfilehost.com/?fid=673791459329066042
3a When ready in aroma, DO NOT REBOOT. Stay in TWRP and go to (4)
4. CHOOSE ! : 4a or 4b
4a. Install : bootstack B13 FIX 2 when coming from another rom : https://androidfilehost.com/?fid=745849072291693516
GOTO (5)
4b. Install : bootstack Universal B15 “adapted 3.1.1.0” when already on a MiFavor 5.0 rom
https://androidfilehost.com/?fid=673791459329066038
GOTO (5)
5. Install : MODEM (G) : https://androidfilehost.com/?fid=962021903579492190
( flash modem for A2017U model : https://androidfilehost.com/?fid=817550096634745612 )
( flash modem for A2017 model : https://androidfilehost.com/?fid=457095661767137840 )
6. REBOOT :
6a When you were already on a MiFavor rom ( and of course did 4b ), you’ll normaly have a clean (double) boot
6b When you came from another rom ( and did 4a ), your phone will power off (3 red led). Don’t reboot ! Hold power+vol+ to enter back into twrp. Just flash B15 adapted (4b) with TWRP3.1.1.0 and reboot. No need to flash TWRP3.1.1.0 again. You’ll have a clean boot too.
6c. Once booted : When you’ve chosen JoJoc tweak AND Magisk togheter, go back in TWRP and install this installer for Jojoc Magisk. It enables just the script : https://androidfilehost.com/?fid=889964283620770880 (Jojoc+SuperSU : no need to do anything extra)
7. IMPORTANT ! Follow steps !
7a. setup WIFI/data
7b. go into SuperSU or Magisk and check if all ok
7c. tap ADAWAY and give permissions
7d. see if the JoJoc Battery tweak has enabled with the proper values (https://forum.xda-developers.com/showpost.php?p=74752134&postcount=39)
7e. tap addless youtube app. You’ll be asked to log in and update google services ! Do so and wait.
7f. tap google playstore, settings/disable autoupdates
7g. go to google services ( even if you’re on the latest 11.9.51 (440-177350961) or 11.7.46 (440-175121617)) Uninstall ! Reboot, go into youtube app again and update services AGAIN ! YEP !
7h. try an app like google maps(enable gps and get a fix), hangouts or chrome and you’ll normaly see that force closes should be gone !
Everything is working as far as i can see...
INFO :
AROMA Features to choose from :
Debloat almost all remaining apps
Choose SuperSU 2.82 or Magisk14.0 (safetynet asure)
Add Google Dialer
Add Google Keyboard, Touchpal (activate in settings)
Double tap to camera
JoJoc Battery tweak ( gave me 8.30h SOT with this rom ! )
(BXSRVEngine Bravia4, Super-Vivid, X-reality )
.....
Stripped off :
....
Zte clock replaced by Google Clock
Zte calendar replaced by Google Calendar
....
Baked into :
AdAway
Google Calender
Google Clock
YouTube Adfree Black Themed (dont update !)
Minor Modifications :
Boot :
• Init.d enabled
• Dm-verity disabled
Zip aligned apk’s
Build.prop tweaks : (remove them in system/build.prop if not needed)
• Improved performance
• Faster boot
• Phone rings immediately
• Wifi scan interval 180sec
• Better call voice quality
• Better network signal
Added sounds LOS
Faster UI (thanks ADM)
Magisk 14.0 (more stable to safetynet imo)
SuperSU 2.82
Busybox 1.27.2
Hope you'll E N J O Y !!!
Contributors :
me, myself and I
Credits :
@_alexndr
@amarullz
@SuperR.
@bkores (for our work together on DoubleTapCamera , thnx !)
@Plamb1r (BXRSV Engine)
@nfsmw_gr (for our work together on his JoJoc tweak , thnx !)
@joaste ( testing/follow up – Big Thnx !)
@Ayush Singh
@ZaneZam (iYTB Thnx !)
@Chainfire
@topjohnwu
@jcadduono
@Didgeridoohan
ROM OS Version : 7.1.1 Nougat MiFavor 5.0 (chinese)
Source : ZTE stock-rom A2017UV2.0.0B13 / original ZTE upload/reuploaded : https://androidfilehost.com/?fid=889764386195932870
Kernel : stock
Version Information :
Status : Stable
Created : 2017-12-04
Release : 2017-12-08
Lookin' great man, congrats.
nfsmw_gr said:
Lookin' great man, congrats.
Click to expand...
Click to collapse
Yeah, hope so. And hope they'll enjoy your JoJoc tweak as i do for my battery :good:
Thank you Very much, will Flash this Later
Lycidias said:
Thank you Very much, will Flash this Later
Click to expand...
Click to collapse
When flashed do update on battery usage - SOT, force closes. Thnx !
Hi !
Thx for this ROM.
Out of couriosity I installed this ROM (exactly followed the instructions).
Even if it's good looking I have problems with this ROM. Some of the applications simply don't start.
e.g. google play games hangs on start screen. as well as google maps.
Any ideas, what's wrong or going on?
No more experiances with this ROM yes, as I just installed it
regards
flushbeer said:
Hi !
Out of couriosity I installed this ROM (exactly followed the instructions).
Even if it's good looking I have problems with this ROM. Some of the applications simply don't start.
e.g. google play games hangs on start screen. Even phone restart hangs so that the phone cannot be rebooted.
Any ideas, what's wrong or going on?
No more experiances with this ROM yes, as I just installed it
regards
Click to expand...
Click to collapse
Thnx for feedback.
We've tested play games too (like maps, chrome, hangouts...) and had no issues at all. As a matter of fact I tested them all working together, opening closing opening and so on, no problems.
What about your boot is strange. Did you install B15 adapted as described? We had no issues booting.
Perhaps wipe all again and redo because this sounds weird.
Which model and Rom were you on?
PS : did you deinstall / reinstalled services like described?
flushbeer said:
Hi !
Thx for this ROM.
Out of couriosity I installed this ROM (exactly followed the instructions).
Even if it's good looking I have problems with this ROM. Some of the applications simply don't start.
e.g. google play games hangs on start screen. as well as google maps.
Any ideas, what's wrong or going on?
No more experiances with this ROM yes, as I just installed it
regards
Click to expand...
Click to collapse
I agree with raystef66. I would restart from scratch.
Start by making sure you're on twrp 3.1.1, that system is mounted. Wipe system, data cache and dalvik (internal storage is not necessary).
Try installing the b13 bootsack file first, then reboot recovery.
Install the b15 fix2 file and reboot recovery.
Install the ROM and reboot.
Hi !
Thx for your feedback (both of you).
boot is ok (no idea what happened)
google maps: it starts, but it seems that it takes ages after a reboot.
play games: still does not start.
I installed exactly like joaste desribed, but I will try again.
thx
regards
flushbeer said:
Hi !
Thx for your feedback (both of you).
boot is ok (no idea what happened)
google maps: it starts, but it seems that it takes ages after a reboot.
play games: still does not start.
I installed exactly like joaste desribed, but I will try again.
thx
regards
Click to expand...
Click to collapse
Did you disable play services and re enable it?
Once done and play services has been updated, go to settings, apps, maps and clear cache and data then open maps.
What happens?
flushbeer said:
Hi !
Thx for your feedback (both of you).
boot is ok (no idea what happened)
google maps: it starts, but it seems that it takes ages after a reboot.
play games: still does not start.
I installed exactly like joaste desribed, but I will try again.
thx
regards
Click to expand...
Click to collapse
Sure. As we have the same phone all should work. At the moment I've all those app installed and running. And no hitches. I'm on supersu.
BTW, this morning started with 100 % battery, after 1h SOT, still on 88%. With full use of phone, on wifi, 4g. So like said, the jojoc tweak does its work for me. Never had above average of 5h, now always above 7.30 depending use.
EDIT : 2h SOT still 78% :cyclops:
flushbeer said:
Hi !
Thx for your feedback (both of you).
boot is ok (no idea what happened)
google maps: it starts, but it seems that it takes ages after a reboot.
play games: still does not start.
I installed exactly like joaste desribed, but I will try again.
thx
regards
Click to expand...
Click to collapse
Check if you have anything frozen or disabled and restore them to their normal state.
Also go to play store and make sure everything is updated.
The notify flash option in settings force closes
Raffikie said:
The notify flash option in settings force closes
Click to expand...
Click to collapse
Have checked these options again but no fc's there....dont see why btw.
As said, i'm days on this version now and all ok. No fc's, sync ok and so on.
In previous version i had some fc's too from time to time, but with this one imo all is ok.
Important : follow all procedure, check permissions, deinstall existing services and reinstall services till you get latest 11.9.51 (440-177350961)
Also don't forget the B15 adapted...
Should be all running ok.
Perhaps some other users (50 downloads now over one night ) can give feedback too as we're interested :good:
BTW : as i see the ROM download is almost double as for the new B13 fix2 and B15 adapted...i can imagine some things go wrong, so download all files....and use them...
Hey
I installed it and everything as good as it should.
It took some time to set itself, but now is well.
I got the G version and it was installed flawlessly.
But I must confirm that notice flash crashes here as well. But I don't care 'cause I don't know what it is for :angel:
Sent from my ZTE A2017U using XDA Labs
Orlando.Rodriguez said:
Hey
I installed it and everything as good as it should.
It took some time to set itself, but now is well.
I got the G version and it was installed flawlessly.
But I must confirm that notice flash crashes here as well. But I don't care 'cause I don't know what it is for :angel:
Sent from my ZTE A2017U using XDA Labs
Click to expand...
Click to collapse
Thnx for your feedback ! Much appreciated :good:
Btw, now on 3h05 SOT already and 60% left
Raffikie said:
The notify flash option in settings force closes
Click to expand...
Click to collapse
Orlando.Rodriguez said:
Hey
I installed it and everything as good as it should.
It took some time to set itself, but now is well.
I got the G version and it was installed flawlessly.
But I must confirm that notice flash crashes here as well. But I don't care 'cause I don't know what it is for :angel:
Sent from my ZTE A2017U using XDA Labs
Click to expand...
Click to collapse
OK, now i understand. I thought you were mentioning the notifications under settings.
But indeed the "notice flash" under advanced settings was some feature in previous version, but in russian and i left it out.
I was just an app that did make your flash go off when a notification came in.
But as said, it was in russian and imo : useless.
update:
I went through the installation procedure again, now everything seems to run fine. I have no idea what happened after the first install.
No force closes yet (but didn't check notice flash)
I cannot report on screen on time because phone ist not running long enough with this ROM.
thx
regards
flushbeer said:
update:
I went through the installation procedure again, now everything seems to run fine. I have no idea what happened after the first install.
No force closes yet (but didn't check notice flash)
I cannot report on screen on time because phone ist not running long enough with this ROM.
thx
regards
Click to expand...
Click to collapse
Ok nice to know ! :good:
The notice flash was an app in russian and rather useless imo and left it out. Still in settings though but then again not that important.
Hello,
Im having some trouble disabling the on-screen buttons through build.prop, I already disabled disemmcwp via ADB on a PC and from an terminal emulator app. It reboots and I stillt reverts my build.prop.
And clues on how to fix this?
sincerely, me
First of all i highly recommend you update your phone to latest version of Flyme as of day i write this guide newest stable version is 7.0.0.0G. It brings various bug fixes as well as security update and new functions. It fixed the weather problem too when it would not appear on secondary screen. This is my experience based on the standard model with Helio P25 chip.
JUST IN CASE BACKUP ALL OF YOUR DATA FIRST
Grab it at http://www.flymeos.com/firmwarelist?modelId=88&type=1
Installation is pretty straightforward:
-switch off your phone
-now press volume up button and power button at same time, then release power button when meizu logo appears
-phone now will enter update mode, connect it to pc and it should show up as removable drive named recovery, copy the update.zip over it
-once copied tap the start button to begin. the process itself and first boot will take a while
-when done and phone boots up just log in to your accounts and set up everything as normal or whatever
ta-dah ! you should be running latest software now.
Next problem i've encountered was big number of unwanted apps and you will need working ADB for that. I've always used custom roms which did not contain bloatware. Now im giving you one of the way of disabling them (not permanent removal).
For this to be done you need to activate developer mode and usb debugging, simply go to settings->about phone->and now tap on your build number several times
After you activate it it will be available in accessibility options under developer settings. just check the usb debugging and you're good to go
DISCLAIMER: dont ask me about adb drivers for your phone, since i had issues installing them under win 10 x64 build 1803 i thought "aw f*ck it" and just did it on linux where everything worked out of the box.
The application you will need is called Ice Box (you will find it here https://play.google.com/store/apps/details?id=com.catchingnow.icebox&hl=en_US) and install it.
After you install the app its necessary that you remove ALL of your accounts including your Google account. We will need to grant the app device owner permission. Also if multi-user or guest mode has been set on your device, it need to be closed or deleted.
When you have that done just type in your command line , terminal or whatever "adb shell dpm set-device-owner com.catchingnow.icebox/.receiver.DPMReceiver "
Now reboot and add your accounts back, and disable/freeze uwanted apps.
Last - the night mode. As its no longer availble in Flyme 7 if you want to use it you need to manually bring it back by installing Flyme Lab and enabling it trough quickshortcutmanager. Install both apps, then open quickshortcutmanager and search for Flyme Lab. expand it and choose the activity named com.meizu.flymelab/com.meizu.flymelab.component.nightmode.NightModeSettingsActivity .Create shortcut and open it. You should be able to enter the night mode.
Nice guides, thanks.
It's also nice that Flyme 7 still supports rooting, therefore I'm using Titanium Backup to freeze unwanted apps. I bought it when I was using another phone so, for me, it's still worth it. Altough, for uninstalling system apps I'm using separate ADB commands for each app.
cris2d2 said:
Nice guides, thanks.
It's also nice that Flyme 7 still supports rooting, therefore I'm using Titanium Backup to freeze unwanted apps. I bought it when I was using another phone so, for me, it's still worth it. Altough, for uninstalling system apps I'm using separate ADB commands for each app.
Click to expand...
Click to collapse
Its first time for me writing a guide so good word is always appreciated. What im trying to show here is the no root way of getting rid of apps for ppl like me who dont want to root their phone. As i bought it literally two days ago and i dont want to mess with it too much and loose warranty or/and OTA updates.
I also been considering posting a root guide once i tried it myself to confirm it working.
non.verbal said:
Its first time for me writing a guide so good word is always appreciated. What im trying to show here is the no root way of getting rid of apps for ppl like me who dont want to root their phone. As i bought it literally two days ago and i dont want to mess with it too much and loose warranty or/and OTA updates.
I also been considering posting a root guide once i tried it myself to confirm it working.
Click to expand...
Click to collapse
Well, before I discovered a rooting method for Flyme 7, I used to uninstall apps by using ADB commands. So, yes, it is possible to remove unwanted system apps without root. But now, after rooting Flyme 7, I'm only using Titanium Backup to freeze unwanted system apps, not removing them.
As far as I know, rooting Meizu phones by the official method (from Settings) does not lead to losing warranty. Only OTA updates are lost, but this is not important, at least to me, because I can always check Flyme website for new updates and, if I want to update, I just download the file and flash it through standard Flyme recovery. There is no need, for me, to maintain OTA capability. Anyhow, Flyme updates are slow to non-existent, so we can't really complain about losing an update.
Thank you all. I'm happy with this phone at all, but software has few shortcomings and design flaws, in my opinion. Especially related to the integration with "flyme login" and Touchpal. This last one is very annoying because although I try to stop it, at each software update it comes back, more annoying than ever. So, I have some questions: which is the adb command to stop and freeze bloatware without rooting? Which is the official way to root the phone? Once rooted, is it possible to revert to the unrooted state? Some apps, actually, do not work on rooted phones. Thanks
pask876 said:
Thank you all. I'm happy with this phone at all, but software has few shortcomings and design flaws, in my opinion. Especially related to the integration with "flyme login" and Touchpal. This last one is very annoying because although I try to stop it, at each software update it comes back, more annoying than ever. So, I have some questions: which is the adb command to stop and freeze bloatware without rooting? Which is the official way to root the phone? Once rooted, is it possible to revert to the unrooted state? Some apps, actually, do not work on rooted phones. Thanks
Click to expand...
Click to collapse
I can't freeze (or disable) apps with ADB commands, only uninstall.
You need [email protected], App Inspector or similar (to find exact name of package for an app) and these commands:
adb devices
adb shell
pm uninstall -k --user 0 name_of_package
Example, for gmail:
pm uninstall -k --user 0 com.google.android.gm
Regarding rooting, as far as I know, the only method that works on Pro 7 / Pro 7 Plus is also supported by Meizu (but it breaks OTA updates).
The method is described in this video (in russian) but it's quite easy.
If you want to remove root (or if root breaks functionality) you have to reflash the same ROM from Recovery (without wipe).
Any air update coming soon? Or manually installation single option?
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!