Related
This method creates the ability to debloat the Verizon GS7 (non-Edge Snapdragon) by modifying @jrkruse's method for the S7 edge posted here. Huge thanks to jrkruse for making the GS7 what it should be without massive bloat.
After my OP, he and @CVertigo1 evolved the method to fix the safetynet fail issues, so it now should work perfectly. I personally have not yet tried the updated method but will do so tomorrow. I'm copying instructions from the CVertigo1 thread here, but also keeping the old instructions below in post 1.
Knox counter is still 0x0, and I can confirm I have repeatedly used Samsung pay.
New CVertigo1 method:
CVertigo1 said:
Yet again, all thanks go to @jrkruse for this one. I have modified his zip to work on the Verizon S7 flat. The ROM is silky smooth since it uses the factory kernel. I'm going to tweak his instructions to work for the flat. I can confirm that SafetyNet passes using this method.
Download
ODIN v3.12.3.zip
Firmware bundle for the G930. Includes VZW and TMO firmware (G930VVRU4BQA2 and G930TUVU4BQB1) as well as engineering bootloader and stock boot_recovery.image
S7_SU_2_79_Root_Unroot_WO_Tweaks.zip
VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V5_VZWS7FLAT.zip
Install Instructions From Any Build
Warning: This will wipe your device. Some of these instructions are redundant, but they will ensure that everything goes as planned. If you don't follow them to the T, don't complain.
1) Unzip Odin and the firmware bundle zips. Boot the phone into download mode and flash the G930T BL, AP, and CP files in Odin.
2) Don't bother logging into any accounts, as the phone will get wiped again. Copy the FlashFire.apk and VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V5_VZWS7FLAT.zip to your SD card.
3) Shut off the phone and boot into download mode (volume down, home, and power). Flash the S7 Nougat root kernel in the AP slot in Odin. This file was in the firmware bundle.
4) When the phone reboots, unlock developer options and enable USB debugging. Unzip the S7_SU_2_79_Root_Unroot_WO_Tweaks.zip and run root.bat from your PC.
5) Now install FlashFire. Go into FlashFire settings and click option to allow flashing Bootloaders.
6) Now click flash firmware and chose AP_G930TUVU4BQB1_CL10376601_QB12449107_REV02_user_low_ship_MULTI_CERT_meta.tar.md5 SELECT ALL OF THE PARTIONS!!!
7) Now click install zip and choose VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V5_VZWS7FLAT.zip Make sure to click mount system when FlashFire asks. View attachment 4073928
VERY IMPORTANT NOTE: MAKE SURE TO UNCHECK INJECT ROOT AFTER ADDING THE ZIP!!!!!!!- Thanks @dclutter1
8) The phone will restart and FlashFire will flash the firmware first(it will take a couple minutes to find and flash everything), then the Aroma installer will start.
9) In Aroma, select wipe data(DO NOT KEEP SU)
10) The phone will say custom status on first boot, but it goes away after setup and reboot.
Click to expand...
Click to collapse
older method just for the record
Here is an OLDER METHOD with ADB install
Download stuff:
ODIN v3.12.3.zip
Firmware bundle for the G930. Includes VZW and TMO firmware (G930VVRU4BQA2 and G930TUVU4BQB1) as well as engineering bootloader and stock boot_recovery.image
ROM: There are two basic options to choose from:
PlayStore Rom - so called because it has almost NO apps and you download what you want from the PlayStore. Has an experience very similar to the Pixel.
Hybrid ROM - close to Samsung Stock experience by massively debloated
Method:
Reboot phone to recovery wipe data
Reboot to bootloader
In odin flash:
In BL slot: BL_G930TUVU4BQB1_CL10376601_QB12449118_REV02_user_ low_ship_MULTI_CERT.tar.md5
In AP slot: AP_G930TUVU4BQB1_CL10376601_QB12449118_REV02_user_ low_ship_MULTI_CERT_meta.tar.md5
In CP slot: CP_G930TUVU4BQB1_CL10376601_QB12449107_REV02_user_low_ship_MULTI_CERT.tar.md5
Leave CSC slot Blank
Go through setup don't add any accounts your going to wipe again when finished reboot back to bootloader
In odin Flash Engineering Boot.img from above (in AP slot)
When phone reboots and computer reconnects to phone Open HYBRID_PLAYSTORE_ROM.zip folder
Click Verizon_TMO_PlayStore_Install.bat
When done click press to continue the phone will reboot back to download mode
In odin flash:
In CSC slot: CSC_VZW_G930VVZW4BQA2_CL10280325_QB12417265_REV02_user_low_ship_MULTI_CERT.tar.md5
In AP slot: G930TUVU4BQB1_Boot_Recovery_Image.tar.md5.tar
Phone will reboot to recovery and fail
In Recovery click Mount System
Wipe data
Reboot phone
During Boot Phone will Say Custom Status this will change after phone is setup and a reboot is performed
Once through setup open Rom Control App
Navigate to Phone and Settings
Click on IMS Settings
Choose Ims service switch
Click on MMTEL switch
Click on RCS switch
Under MMTEL section I enabled all the options
Click Back Button until your back to Phone and Settings Menu in Rom Control
Choose Activate Advanced Calling
Make sure under Advanced Calling that HD and Video calls are enabled
Activate WifiCalling
Known issues:
Safety net check fails (so Venmo does not work)
Some sites are blocked. Turning on "data saver" in Chrome settings worked for me but not everyone
I found that I had to go into settings > applications > phone and explicitly choose the phone as my default application for calls before it would correctly create a notification when the phone rang.
Some slightly more varsity moves:
Keeping apps from your stock:
You can modify the .bat file to not remove any apps you want to keep.
For example, I wanted to keep the "always on" display, so I deleted these lines from the .bat file:
Code:
adb shell rm -r /system/priv-app/AODService_v20
You can also further delete apps. Essentially during steps 5 - 7 above, the phone is rooted. During that time you can remove other packages. (My advice would be to pull them to your computer so you can push them back if needed)
For instance, I wanted to remove Hangouts, the AOSP browser (I use Chrome) and VisualVoiceMail. So I repeated step 5, then did:
Code:
adb root
adb remount
adb pull /system/app/VisualVoicemail
adb shell rm -r /system/app/VisualVoicemail
adb reboot bootloader
Then repeat steps 9 - 11
Wipe CACHE, (NOT data)
Reboot
Cool, cant wait to walk a friend thru this.
Just got up and running on PlayStore, everything seems good except I can't get the call recording to work. Thanks for putting this together
Sent from my SM-G935V using Tapatalk
JPSloan1 said:
...
7. Click Verizon_TMO_PlayStore_Install.bat.
...
Click to expand...
Click to collapse
Where is this .bat file?
Also, on jrkruse's thread, I only see a single ROM for download: VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V2.zip. Am I missing something?
Edit: I found the Play Store ROM; it contains the .bat file. The new ROM in jrkruse's OP won't work with this method, I assume.
thrillerbee said:
Where is this .bat file?
Also, on jrkruse's thread, I only see a single ROM for download: VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V2.zip. Am I missing something?
Edit: I found the Play Store ROM; it contains the .bat file. The new ROM in jrkruse's OP won't work with this method, I assume.
Click to expand...
Click to collapse
Yes It appears he updated his method to one that uses a different kind of temporary root as well as flashable files. I'll have to look at it and see if it's customizable the way the other one was, but it looks like you found the correct playstore ROM zip from before. Here is the other ROM. Sorry for the confusion.
Do we need to flash the Verizon modem? And if so would you have a flashable file? Thanks,
if i want to just put the tmobile firmware on my verizon phone and still use verizon service, do i just flash the tmobile firmware and then the verizon csc file and call it a day? not looking for the debloat and all that other stuff. just straight up tmobile firmware working on verizon.
t1231 said:
Do we need to flash the Verizon modem? And if so would you have a flashable file? Thanks,
Click to expand...
Click to collapse
I tried but the .zip kept failing so maybe I didn't create it right.... So ultimately I did not bother and my service seems just fine at the moment.
Hobson318 said:
if i want to just put the tmobile firmware on my verizon phone and still use verizon service, do i just flash the tmobile firmware and then the verizon csc file and call it a day? not looking for the debloat and all that other stuff. just straight up tmobile firmware working on verizon.
Click to expand...
Click to collapse
I think that would work (and wouldn't think you need to bother with the engineering bootloader steps either then) but to be honest it might be safer to ask jrkruse, because I don't deeply understand it - really just adapted his method for the S7 flat.
You speak of rebooting into recovery and wiping the cache. How exactly? All I seem to get is a dead robot on my screen.
Am I missing something?
Attempting this on a G930V, FWIW.
S3NTYN3L said:
You speak of rebooting into recovery and wiping the cache. How exactly? All I seem to get is a dead robot on my screen.
Am I missing something?
Attempting this on a G930V, FWIW.
Click to expand...
Click to collapse
After which step?
At one point I did get a robot with a yellow triangle saying "no instructions" or something, but I waited a DL few minutes and pressed a few buttons and it booted into recovery.
JPSloan1 said:
After which step?
At one point I did get a robot with a yellow triangle saying "no instructions" or something, but I waited a DL few minutes and pressed a few buttons and it booted into recovery.
Click to expand...
Click to collapse
Step 10.
Hmm, It seems that I wasn't holding the buttons down long enough.
If DL = Damn Long, then, yes, I agree.
OK, made it to step 15 and now I'm boned.
I had to install that ROM Control app manually as it didn't get pushed to the phone for some reason.
While attempting to follow along by clicking on IMS Settings, a toast message complains about no CSC binary or customer.xml
EDIT:
Hmm, I'll just wait a bit until you all get this sorted out I guess. In the meantime, it's back to stock for me.
S3NTYN3L said:
OK, made it to step 15 and now I'm boned.
I had to install that ROM Control app manually as it didn't get pushed to the phone for some reason.
While attempting to follow along by clicking on IMS Settings, a toast message complains about no CSC binary or customer.xml
EDIT:
Hmm, I'll just wait a bit until you all get this sorted out I guess. In the meantime, it's back to stock for me.
Click to expand...
Click to collapse
If ROM control didn't install manually it's because the .bat file didn't execute correctly. Did you modify it? Did it successfully acquire root and execute all the commands all the way through to the "click to continue" prompt? OR did it give error messages along the way? (There will be a few during the remove steps because it's removing packages that only exist on the S7 edge, not flat.
I would try it again if you have the patience.
I didn't modify anything.
I only recall a few minor errors regarding removal of non-existent directories.
Yes, the script went through to the end.
Yes, the phone had root and the TMobile rom wouldn't let me forget it, lol.
It kept complaining the whole way through.
JPSloan1 said:
Basically this method temporarily roots the phone to modify the packages installed, removes a ton of them, and then reverts. So with this method, Knox counter is still 0x0, and I can confirm I have repeatedly used Samsung pay
Click to expand...
Click to collapse
Can you do me a huge favor and install 'Phone info *Samsung*' from the PlayStore and upload a screenshot of the firmware page. I replicated jrkruse method since he changed it, but swapped the boot.img for the S7 flat images. Everything works great, but I fail SafetyNet. I need to find out where I'm mixed up. If I can figure this out, then I believe I can make a simple zip to take care of everything else.
CVertigo1 said:
Can you do me a huge favor and install 'Phone info *Samsung*' from the PlayStore and upload a screenshot of the firmware page. I replicated jrkruse method since he changed it, but swapped the boot.img for the S7 flat images. Everything works great, but I fail SafetyNet. I need to find out where I'm mixed up. If I can figure this out, then I believe I can make a simple zip to take care of everything else.
Click to expand...
Click to collapse
Yeah attached. I think I also have this problem as do those in the other thread, and that's why I get an error on device check with Venmo.
I thought you posted that Samsung Pay worked for you in the OP.
CVertigo1 said:
I thought you posted that Samsung Pay worked for you in the OP.
Click to expand...
Click to collapse
I followed the method in the OP, installed Play Store version. Samsung Pay is working for me.
Sent from my SM-G935V using Tapatalk
I´m using the latest firmware available for oneplus 3 and the volume on call is low! Using whatsapp the volume is good.
I´ve instaled and existing fix and the problem is solved but everytime that oneplus launch an firmware update I need to root the phone and install the fix!
Anyone with the same problem?
romaolp said:
I´m using the latest firmware available for oneplus 3 and the volume on call is low! Using whatsapp the volume is good.
I´ve instaled and existing fix and the problem is solved but everytime that oneplus launch an firmware update I need to root the phone and install the fix!
Anyone with the same problem?
Click to expand...
Click to collapse
I have the same. Which fix do you installed?
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
sakarya1980 said:
I have the same. Which fix do you installed?
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Click to expand...
Click to collapse
I use this fix https://androidfilehost.com/?fid=673368273298967516 - TWRP-OxygenOS-Low-InCall-Volume-Fix.zip
But in every update that is launched by oneplus you need to install it.
romaolp said:
I use this fix https://androidfilehost.com/?fid=673368273298967516 - TWRP-OxygenOS-Low-InCall-Volume-Fix.zip
But in every update that is launched by oneplus you need to install it.
Click to expand...
Click to collapse
Does this fix still work? I need to find a solution to the low volume when using the earpiece on the latest OxygenOS (5.0.1) with Oreo 8.0. I thought was a configuration issue, so tried a factory reset but the issue continues.
If I try this, when installing TWRP recovery, the device will lose all data, right? or this will not be the case?
pulsorock said:
Does this fix still work? I need to find a solution to the low volume when using the earpiece on the latest OxygenOS (5.0.1) with Oreo 8.0. I thought was a configuration issue, so tried a factory reset but the issue continues.
If I try this, when installing TWRP recovery, the device will lose all data, right? or this will not be the case?
Click to expand...
Click to collapse
Unlocking bootloader or wiping internal storage will result in loss of data. Mere flashing TWRP, if your bootloader is unlocked already, will not affect your data.
tnsmani said:
Unlocking bootloader or wiping internal storage will result in loss of data. Mere flashing TWRP, if your bootloader is unlocked already, will not affect your data.
Click to expand...
Click to collapse
Thank you @tnsmani. Yes, I just remembered that. I don't recall unlocking the bootloader on this device before.
So, can anyone using OxygenOS with Oreo 8.0 confirm if this patch works, I could go ahead and try it. It would suck going to the steps and wiping everything for it not to resolve the low volume issue.
Thanks!
Low volume in custom roms using nos
i can tell you for sure that it does not work, better, that specific ZIP does not wwork on Oreo.
The folder is wrong, you could simply extract the xml file and drop it to
Code:
/system/vendor/etc/mixer_paths_tasha.xml
Then it should work, i'm checking right now, report back if working. Maybe i'll update the zip too..
Edit:
Tested, almost broke my ear, here is the link for the fixed one for Android Oreo (I don't know if it works with AOSP)
TWRP-OxygenOS-5.0.1-Oreo-Low-InCall-Volume-Fix.zip
Enjoy
davide136 said:
i can tell you for sure that it does not work, better, that specific ZIP does not wwork on Oreo.
The folder is wrong, you could simply extract the xml file and drop it to
Code:
/system/vendor/etc/mixer_paths_tasha.xml
Then it should work, i'm checking right now, report back if working. Maybe i'll update the zip too..
Edit:
Tested, almost broke my ear, here is the link for the fixed one for Android Oreo (I don't know if it works with AOSP)
TWRP-OxygenOS-5.0.1-Oreo-Low-InCall-Volume-Fix.zip
Enjoy
Click to expand...
Click to collapse
I OEM unlocked my OP3 and then flashed TWRP (3.2.1-0). After flashing, I rebooted into recovery to make sure TWRP was installed. Then I rebooted the system. After booting system, it went back to stock recovery (when I checked again).
Tried again flashing TWRP and flashing your attached zip file immediately before rebooting the system again. Still, very low volume on call and it also went back to stock recovery again. How can I avoid this? Is it goes back to stock recovery does it means the patched file will be overwritten?
When flashing TWRP, do I need to "allow system modifications" the first time TWRP is flashed? I read that will cause a boot loop. I really don't need root, just need to be able to have the volume louder.
Thanks!
Does it give you any error during flash of the zip?
pulsorock said:
I OEM unlocked my OP3 and then flashed TWRP (3.2.1-0). After flashing, I rebooted into recovery to make sure TWRP was installed. Then I rebooted the system. After booting system, it went back to stock recovery (when I checked again).
Tried again flashing TWRP and flashing your attached zip file immediately before rebooting the system again. Still, very low volume on call and it also went back to stock recovery again. How can I avoid this? Is it goes back to stock recovery does it means the patched file will be overwritten?
When flashing TWRP, do I need to "allow system modifications" the first time TWRP is flashed? I read that will cause a boot loop. I really don't need root, just need to be able to have the volume louder.
Thanks!
Click to expand...
Click to collapse
After flashing twrp.. Reboot into recovery and root your phone
---------- Post added at 12:46 PM ---------- Previous post was at 12:45 PM ----------
Is there a similar file for low loudpeaker volume fix?
davide136 said:
Does it give you any error during flash of the zip?
Click to expand...
Click to collapse
No, no error at all. Everything looks like it worked fine. just after reboot system, it seems it did nothing the patch. Then when rebooting recovery, it was reverted to stock.
---------- Post added at 08:12 AM ---------- Previous post was at 08:10 AM ----------
drfox96 said:
After flashing twrp.. Reboot into recovery and root your phone
Click to expand...
Click to collapse
So rooting is required to avoid twrp being replaced by stock recovery again?
pulsorock said:
No, no error at all. Everything looks like it worked fine. just after reboot system, it seems it did nothing the patch. Then when rebooting recovery, it was reverted to stock.
---------- Post added at 08:12 AM ---------- Previous post was at 08:10 AM ----------
So rooting is required to avoid twrp being replaced by stock recovery again?
Click to expand...
Click to collapse
Yes
davide136 said:
i can tell you for sure that it does not work, better, that specific ZIP does not wwork on Oreo.
The folder is wrong, you could simply extract the xml file and drop it to
Then it should work, i'm checking right now, report back if working. Maybe i'll update the zip too..
Edit:
Tested, almost broke my ear, here is the link for the fixed one for Android Oreo (I don't know if it works with AOSP)
TWRP-OxygenOS-5.0.1-Oreo-Low-InCall-Volume-Fix.zip
Enjoy
Click to expand...
Click to collapse
Hi, I tried your fix on Open Beta Experience ROM 8.0. The volume issue was sorted but it broke the wake up system. I use face unlock and the moment I click any button, it wakes up my screen and looks for my face. After this patch, don't know how but phone stopped waking up. I had to use my fingerprint to unlock the phone. No other button was waking up the phone. Also the phone started getting hot and there was a tremendous amount of lag. I had to reflash the original OS to get it back to normal.
Know why ?
phrozenwire said:
Hi, I tried your fix on Open Beta Experience ROM 8.0. The volume issue was sorted but it broke the wake up system. I use face unlock and the moment I click any button, it wakes up my screen and looks for my face. After this patch, don't know how but phone stopped waking up. I had to use my fingerprint to unlock the phone. No other button was waking up the phone. Also the phone started getting hot and there was a tremendous amount of lag. I had to reflash the original OS to get it back to normal.
Know why ?
Click to expand...
Click to collapse
I can tell you that i tested with my phone and this never happened, considering that's not touching any file but this "/system/vendor/etc/mixer_paths_tasha.xml", I think it's something else causing what happened to your phone. Did you flash something else? Otherwise i'll take it down
amg_driver said:
i took a look in this file/fix.
my advice: dont flash this. imo the values are set too high and this fix could damage the hardware. as davide136 said "almost broke my ear"...
Encloused my fix created for latest NOS (Oreo).
But should work on other roms as well (if path to mixer_paths_tasha.xml is /system/vendor/etc/)
Try "88-fix". If it's a bit too low for you than flash "90-fix" - as filename suggets, its 2db louder.
Click to expand...
Click to collapse
Is it Oneplus 3T compatible?
Thank you for your work!
Hello everyone, i want to clarify something, it was never a software issue.it's just DUST, believe me.
After trying all the mods and flashable zips and increasing the values, it only increase the volume but it becomes like a walkie talkie and not clear at all. So i decided to open the phone and it's very simple you can watch a video, nothing very dagerous.
Remove the 2 screws and the sim tray, carefully try to rise the screen with a credit card from the lower part of the phone.
Disconnect the battery, remove the 8 screws and remember their placement( there is one hidden screw middle left under the white stick)
Remove the signal cable and screen and extentions ones, and carefully unclip the motherboard from the top middle and try to rise it, slowly
I advice to put some ductape on the camera lenses so no dust can go in
Remove your speaker
You'll find it clean and be surprised, but the remove the black mesh a'd then you'll be shocked.
Clean the black one with alcohol and then use alcohol+toothbrush to clean the speaker grill on the phone
Clean it till you can see light through it and when you blow on it air can pass through
Reassemble your phone and connect the battery at lassst you dont provoke a shortcut when you screw or something and VOILAAA
Hello, I have this weird bug, after a reboot I always get this message. It seems to appear only when flashing magisk, had this issue on LineageOS, CRdroid and AICP.
Only fix is to reboot again until the message is gone.
Also I flashed magisk after phone setup.
Does anybody know a solution, it seems that this happened to more people across the ROM threads but no reports in the magisk tread.
Don't use Magisk 18.1 as of now. Flash Magisk 18.0.
bravonova said:
Don't use Magisk 18.1 as of now. Flash Magisk 18.0.
Click to expand...
Click to collapse
Tried Magisk 18.0 on LineageOS, still get the message.
I have a work around for it. Extract the boot.img file from your ROMs zip file. Transfer it to you phone. Then open magisk manager and tap install, and then install again. Then select the Patch Boot Image File option. Select the extracted boot.img file and let magisk do it's business. After it's done it will save the file as patch_boot.img. Next time you flash your ROM, or upgrade or simply get stuck, reboot into recovery. Then select install and then select image file. Select the patch_boot.img file and flash it as your boot Image. Reboot and everything should be fine.
It's a but annoying but that's what works for me 100% of the time.
dsahai said:
I have a work around for it. Extract the boot.img file from your ROMs zip file. Transfer it to you phone. Then open magisk manager and tap install, and then install again. Then select the Patch Boot Image File option. Select the extracted boot.img file and let magisk do it's business. After it's done it will save the file as patch_boot.img. Next time you flash your ROM, or upgrade or simply get stuck, reboot into recovery. Then select install and then select image file. Select the patch_boot.img file and flash it as your boot Image. Reboot and everything should be fine.
It's a but annoying but that's what works for me 100% of the time.
Click to expand...
Click to collapse
Thanks man, I will try it:laugh:
Does this mean I can flash the ROM, set it up and flash the patched boot.img and this bug should not reappear?
Mr. Cube said:
Thanks man, I will try it:laugh:
Does this mean I can flash the ROM, set it up and flash the patched boot.img and this bug should not reappear?
Click to expand...
Click to collapse
I guess
Whenever I get stuck in the "Phone is starting", I just reboot into recovery and flash the patch_boot.img and it seems to fix the issue The bug may reappear if you flash some Magisk modules, or update. So just keep that img file ready.
bravonova said:
Don't use Magisk 18.1 as of now. Flash Magisk 18.0.
Click to expand...
Click to collapse
I've flashed 18.0, then I updated through the Manger to 18.1 and working great!
TRY Magisk 18.2
https://forum.xda-developers.com/on...l-twrp-xposed-framework-t3910141#post79103367
DoR3M3 said:
I've flashed 18.0, then I updated through the Manger to 18.1 and working great!
Click to expand...
Click to collapse
I tried Magisk 18.0 but got the "phone is starting" bug four times in a row, than I gave up.
Strangely this also happens on OOS to me but there it disappears 10 seconds after boot
Mr. Cube said:
I tried Magisk 18.0 but got the "phone is starting" bug four times in a row, than I gave up.
Strangely this also happens on OOS to me but there it disappears 10 seconds after boot
Click to expand...
Click to collapse
I've been using 18.0 on OOS 5.1.7 and my ROM OOS[microG] which is OOS 5.1.7 and no problems ever...
I'd say install 17.1 then upgrade from there and see how it goes, and you can also try "Canary" Branch of Magisk and might have better luck with it...
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
If Magisk is a cause, it's not the only cause. I don't use Magisk but get the bug on both my OP3T and OP5 running crDroid. I've also seen it reported on Official LOS. Still looking for common factors, but it might be VPN related. Does anyone here use one? Could be a problem with 3rd Party Launchers. What is everyone using? The only logcat information we have to go on so far is:
Code:
03-13 14:44:37.070 1324 2483 W ActivityManager: Service.startForeground() not allowed due to bg restriction: service com.nordvpn.android/de.blinkt.openvpn.core.OpenVPNService
https://forum.xda-developers.com/showpost.php?p=79109320&postcount=492
There's the possibility that it's just a sporadic bug that could happen to anyone at any time. Could just be a gerenic way of saying "phone ran into something it didn't like during boot" I've only seen reports of this on Pie. Only had it myself on Pie.
The best thing we can do is to get a logcat when it happens. Providing you're in front of your PC, have USB Debugging enabled, and can connect to ADB while the phone is stuck on 'Phone Is Starting', running
adb logcat -d > logcat.txt. should work. (Correct the syntax if i've got that wrong)
I had this problem also on my 5T and got rid of it by using magisk uninstaller. I had this problem on MSM Extended AND crDroid, both the latest versions. I do not use any VPN-apps, but I do use a custom launcher, in my case thats Nova premium.
Are you trying to unlock your phone via fingerprint? For me, the behaviour is consistent: on boot, after entering SIM PIN, try to unlock phone with fingerprint, which leads to unclock code entry as this is the first boot and you need to enter your code. Enter code, and "Phone is starting". If, instead, after entering the SIM PIN, without touching the fingerprint sensor in any way, I manually swipe and enter the unlock code, the phone starts, no problem. Tested repeatedly.
If anyone has any idea where to report this bug, I'll gladly do so, but since apparently it isn't tied to Magisk, nor a specific ROM, I have no clue.
Dirk said:
If Magisk is a cause, it's not the only cause. I don't use Magisk but get the bug on both my OP3T and OP5 running crDroid. I've also seen it reported on Official LOS. Still looking for common factors, but it might be VPN related. Does anyone here use one? Could be a problem with 3rd Party Launchers. What is everyone using? The only logcat information we have to go on so far is:
https://forum.xda-developers.com/showpost.php?p=79109320&postcount=492
There's the possibility that it's just a sporadic bug that could happen to anyone at any time. Could just be a gerenic way of saying "phone ran into something it didn't like during boot" I've only seen reports of this on Pie. Only had it myself on Pie.
The best thing we can do is to get a logcat when it happens. Providing you're in front of your PC, have USB Debugging enabled, and can connect to ADB while the phone is stuck on 'Phone Is Starting', running
adb logcat -d > logcat.txt. should work. (Correct the syntax if i've got that wrong)
Click to expand...
Click to collapse
I'm not sure if it's magisk related but for me the only workaround to get it working again is the solution mentioned by @dsahai. When I flash the patched_boot.img it works again.
Also, I don't use any VPN service but a 3rd party launcher.
I will try to take a log on next reboot and report it to the LOS dev. :silly:
Mr. Cube said:
Also, I don't use any VPN service but a 3rd party launcher.
I will try to take a log on next reboot and report it to the LOS dev. :silly:
Click to expand...
Click to collapse
I use a 3rd party launcher too. The only reason i mention it is because the point where the 'phone is starting' message freezes the phone is at the point where the launcher loads. (or fails to load, which is more accurate to say). Of course everything else is trying to load at that point too so it might just be coincidence.
@Dirk
Someone has made a patch trying to fix the phone is starting bug
Just flash the fix-phone-is starting.zip in twrp and reboot
If it does not work, just flash the restore.zip
you can join op5/t official tg group to give your feedback
https://t.me/joinchat/GQS-ghNaf-1YMpjSbh_puQ
huluhola said:
@Dirk
Someone has made a patch trying to fix the phone is starting bug
Just flash the fix-phone-is starting.zip in twrp and reboot
If it does not work, just flash the restore.zip
you can join op5/t official tg group to give your feedback
https://t.me/joinchat/GQS-ghNaf-1YMpjSbh_puQ
Click to expand...
Click to collapse
That's interesting. Someone must think they've found the problem. What do we know about this?
On crDroid for the OP5 there's something in the latest build that's supposed to be a fix too. I assume it's the same changes. I haven't tried that new build yet so i'm happy to try the zip if it's okay to flash on the OP5?
Dirk said:
That's interesting. Someone must think they've found the problem. What do we know about this?
On crDroid for the OP5 there's something in the latest build that's supposed to be a fix too. I assume it's the same changes. I haven't tried that new build yet so i'm happy to try the zip if it's okay to flash on the OP5?
Click to expand...
Click to collapse
Just flash the fix.zip on ur op5
don't worry u can flash the restore.zip if it doesn't work
huluhola said:
Just flash the fix.zip on ur op5
don't worry u can flash the restore.zip if it doesn't work
Click to expand...
Click to collapse
Thanks.
It's infrequent for me. Perhaps once in a dozen or more reboots. Could be a while before i could say definitively that it's helped, but i'll try it and see. :good:
huluhola said:
@Dirk
Someone has made a patch trying to fix the phone is starting bug
Just flash the fix-phone-is starting.zip in twrp and reboot
If it does not work, just flash the restore.zip
you can join op5/t official tg group to give your feedback
https://t.me/joinchat/GQS-ghNaf-1YMpjSbh_puQ
Click to expand...
Click to collapse
I dont use Telegram. Can you keep us updated here with any news from this Patch? Has anybody reported anything yet?
Hi there,
after unbricking the device I'm able to start TWRP on it. Using fastboot, ADB can't connect, even if TWRP ADB Sideloading is started - strange. Lineage OS 16 can by installed from ZIP after copying it on the Device using explorer.
But neither LOS nor TWRP can't be installed to last on the device.
Before I managed it to get at least TWRP permanently on the phone, but after playing around even this won't work.
Has anyone ever successfully installed LOS on a M3M-Version of the bootloader?
Is there way to get back to stock and then flash LOS?
How to get a real clean restart?
Thanks a lot!
BrickingsSoFunny said:
Hi there,
after unbricking the device I'm able to start TWRP on it. Using fastboot, ADB can't connect, even if TWRP ADB Sideloading is started - strange. Lineage OS 16 can by installed from ZIP after copying it on the Device using explorer.
But neither LOS nor TWRP can't be installed to last on the device.
Before I managed it to get at least TWRP permanently on the phone, but after playing around even this won't work.
Has anyone ever successfully installed LOS on a M3M-Version of the bootloader?
Is there way to get back to stock and then flash LOS?
How to get a real clean restart?
Thanks a lot!
Click to expand...
Click to collapse
Update: Also managed to install this https://forum.xda-developers.com/z2...m-tmo-z2-force-27-1-5-flashall-march-t3917070
But that's not what I want. Nobody Lineage on the Device?
BrickingsSoFunny said:
Update: Also managed to install this https://forum.xda-developers.com/z2...m-tmo-z2-force-27-1-5-flashall-march-t3917070
But that's not what I want. Nobody Lineage on the Device?
Click to expand...
Click to collapse
Since I'm just talking with myself in this thread: From the TMO Stock I managed to install TWRP to last on the device. But anytime I install the LOS ROM and restart the phone stays black and is bricked.
Any ideas? Just to be not so alone?
Heyyo, if you're installing LineageOS, please ensure you're following the steps in the LineageOS wiki as that is what I followed to go from stock to LineageOS and it worked perfectly.
https://wiki.lineageos.org/devices/nash/install
ThE_MarD said:
Heyyo, if you're installing LineageOS, please ensure you're following the steps in the LineageOS wiki as that is what I followed to go from stock to LineageOS and it worked perfectly.
https://wiki.lineageos.org/devices/nash/install
Click to expand...
Click to collapse
Yes, especially
- install os, reboot and THEN gapps and stuff
- if u don't have both slots active (for example, if u flash stock and then immediately go for los) u will have problems , unless u use the pre-los zip, u can find it here somewhere
@Dany XP that is not advised. As the wiki mentions
Sideload the LineageOS .zip package:
On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
On the host machine, sideload the package using: adb sideload filename.zip
(Optionally): If you want to install any additional add-ons, run adb reboot sideload, then adb sideload filename.zip those packages in sequence.
NOTE: If you want Google Apps on your device, you must follow this step before booting into LineageOS for the first time!
Click to expand...
Click to collapse
The reason is when your device boots to system, it is at that point that it should "handshake" with the Google Play servers or there's a risk of stability issues with the Google Play services.
Dany XP said:
Yes, especially
- install os, reboot and THEN gapps and stuff
- if u don't have both slots active (for example, if u flash stock and then immediately go for los) u will have problems , unless u use the pre-los zip, u can find it here somewhere
Click to expand...
Click to collapse
Can you explain the second solution (about the both slots active and the pre-los.zip)
Alruse122 said:
Can you explain the second solution (about the both slots active and the pre-los.zip)
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=80232409&postcount=264
(In my case, without both slots active, I have bootloops and crashes from turning it on the device...)
Dany XP said:
https://forum.xda-developers.com/showpost.php?p=80232409&postcount=264
(In my case, without both slots active, I have bootloops and crashes from turning it on the device...)
Click to expand...
Click to collapse
But the Download is "XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-7_LOS-Prep.zip"
i have an android Pie and XT1789-05, it will work anyway?
Alruse122 said:
But the Download is "XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-7_LOS-Prep.zip"
i have an android Pie and XT1789-05, it will work anyway?
Click to expand...
Click to collapse
No, that's for TMO oreo. Don't flash the prep zip
41rw4lk said:
No, that's for TMO oreo. Don't flash the prep zip
Click to expand...
Click to collapse
I supposed, so, what you recommend ti actívate both slots un pie?
Dany XP said:
Yes, especially
- install os, reboot and THEN gapps and stuff
- if u don't have both slots active (for example, if u flash stock and then immediately go for los) u will have problems , unless u use the pre-los zip, u can find it here somewhere
Click to expand...
Click to collapse
I can't believe it's installed and running after all. I used the pre-los ZIP installed, LOS 16 nightly and opengapps pico...
BUT there is a little problem:
The phone recognizes one and two SIM card correctly, but displays empty signal icons.
Anytime I wan't to make a call it says I should disable flight mode to make calls, but flightmode IS of course disabled... tried to disable and reenable it, cleared dalvik und cache restarted etc.
So: Does anybody know, how to resolve this? Seems to be kind of missing carrier support...
BrickingsSoFunny said:
I can't believe it's installed and running after all. I used the pre-los ZIP installed, LOS 16 nightly and opengapps pico...
BUT there is a little problem:
The phone recognizes one and two SIM card correctly, but displays empty signal icons.
Anytime I wan't to make a call it says I should disable flight mode to make calls, but flightmode IS of course disabled... tried to disable and reenable it, cleared dalvik und cache restarted etc.
So: Does anybody know, how to resolve this? Seems to be kind of missing carrier support...
Click to expand...
Click to collapse
"One and two Sim cards..." That means u r NOT in tmo right? U must be on -05 or 06 I don't remember...
Sorry but the pre-los zip is onlynfor tmo devices (at least that's my understanding)
Hi there,
I've combined some custom-kernel-like tweaks into a single flashable .tar file and I wanted to share it with you.
This .tar file contains:
-patched vbmeta image
-working magisk root with full Android 11 support
-magisk manager helper preinstalled
-a cleaned up boot screen + no bullsh*t on boot screen
-a cleaned up unlocked bootloader screen + no bullsh*t on unlocked bootloader screen
Prerequisites
-an unlocked bootloader
-firmware version CTL1 (A11)/BTJ3 (A10) or newer
-Odin 3.XX.X
-all data backed up
-fully functional brain
-stock recovery and firmware (this will not work if you have a custom recovery or run a custom rom)
STOCK BASED ROMS LIKE BEYONDROM WILL ALSO NOT WORK!
PLEASE NOTE:
-I am not responsible for a bricked device, please make backups and make sure to
always have the official firmware if something goes wrong
-flashing this requires you to factory reset your phone or else the phone won't boot
Instructions:
-unlock your phone's bootloader
-boot into download mode
-in Odin uncheck auto-reboot
-put the .tar file into the AP slot (If it doesn't work try USERDATA)
-after flashing boot into recovery with the key combination
-select factory reset and confirm (This will wipe everything from your phone)
-after factory reset reboot into system
-setup the phone and restore your backup (if you made one)
-Install Magisk and you're good!
If you have any problems
Please don't just comment "Doesn't work" and instead tell me about
the errors you encountered, your software info and other information
you think would be helpful.
Happy flashing!
If you still have questions make sure to ask them below
DOWNLOAD CTL1+: https://1drv.ms/u/s!AtNTTTF5vqOe73aVGDPSRGr5aria?e=dICFlS
DOWNLOAD BTJ3+: https://drive.google.com/file/d/1KqOGRbAy4fY1ghro4HoP-eDDYh4G7b5Z/view?usp=sharing
Tried it on my friend's phone,works great.Thanks
Can i flash it as my firmware version starts with QP1A.??(build number)..
Thanks in advance and cheers..
@[email protected] said:
Can i flash it as my firmware version starts with QP1A.??(build number)..
Thanks in advance and cheers..
Click to expand...
Click to collapse
This doesn't say anything. Can you tell me what custom ROM you are running? If you are on rooted stock also tell me.
Hi,yes,phone is rootedAndroid 10,,one Ui,v 2.1,build number QP1A 190711.020.G988BXXU1ATCT..
@[email protected] said:
Hi,yes,phone is rootedAndroid 10,,one Ui,v 2.1,build number QP1A 190711.020.G988BXXU1ATCT..
Click to expand...
Click to collapse
Geeeeeez! Update your phone! You have to have OneUI 2.5 BTJ3 or OneUI 3.0 CTL1 at least. What are you doing on 2.1? If you don't update, this will break your phone.
Okay buddy,ty..will do that.
Hi again m8,can i update Android 11,,One GUi 3.0,RP1A200720.012 G988B...
And ,or which file i have to use??
@[email protected] said:
And ,or which file i have to use??
Click to expand...
Click to collapse
Depends on the version. I don't want to be rude but how did you even manage to root your phone with this lack of knowledge?
If you update to Android 11/One UI 3.0 you chose the One UI 3.0 one. If you only update to 2.5 you chose 2.5. Remember to check the end of your firmware number:
There are supported firmware endings:
One UI 2.5:
-BTJ3
-BTJ4
One UI 3.0:
-CTL1
-CTL6
-Any One UI 3.0 firmware above that.
Download SM-G988B / Galaxy S20 Ultra 5G SM-G988B in Samfw - Samsung firmware download
Pick your CSC there, chose the newest one preferably (A11), press "Download on website", unzip it and flash it with Odin while in download mode. You should know how to do that.
After it's finished, complete setup (do not restore any backups yet!) and go into download mode again. Flash the file as AP or USERDATA (whatever works) and perform another factory reset. Done.
So i just reflashed stock because Beyond rom is givving me issues, says you removed all the BS from the boot screens but i still have that unlocked bootloader msg. i flashed in AP with no issues, that msg mean it didnt work?
BCityModz said:
So i just reflashed stock because Beyond rom is givving me issues, says you removed all the BS from the boot screens but i still have that unlocked bootloader msg. i flashed in AP with no issues, that msg mean it didnt work?
Click to expand...
Click to collapse
The unlackiert bootlaoder Massage Stars Tiere just wichtig Themen Bulletin
Edit: German Autocorrection sorry wait haha
JanBoyGamer23 said:
The unlackiert bootlaoder Massage Stars Tiere just wichtig Themen Bulletin
Edit: German Autocorrection sorry wait haha
Click to expand...
Click to collapse
Ok disabled the autocorrection. What I was trying to say is: The unlocked bootloader message is still there just without the bull**** about your phone being vulnerable to hackers and this other ****. It now just says that it is unlocked.
JanBoyGamer23 said:
Ok disabled the autocorrection. What I was trying to say is: The unlocked bootloader message is still there just without the bull**** about your phone being vulnerable to hackers and this other ****. It now just says that it is unlocked.
Click to expand...
Click to collapse
Ok sweet, so Im no pro at any of this but i know the basics to flash. and wasnt able to unlock my last phone because the unlock option never popped up in settings. but now my camera isnt working, i open it up and its just black, no errors or anything.
BCityModz said:
Ok sweet, so Im no pro at any of this but i know the basics to flash. and wasnt able to unlock my last phone because the unlock option never popped up in settings. but now my camera isnt working, i open it up and its just black, no errors or anything.
Click to expand...
Click to collapse
That can't be an issue with the script as it doesn't modify anything related to the camera
JanBoyGamer23 said:
That can't be an issue with the script as it doesn't modify anything related to the camera
Click to expand...
Click to collapse
Ok I may have to make a copy of my girls phone and flash original back to the phone and go again.
JanBoyGamer23 said:
That can't be an issue with the script as it doesn't modify anything related to the camera
Click to expand...
Click to collapse
yea IDK, did it all over again, even booting up to make sure the cam was working. same thing black screen when i open the camera app.
ok, i tried searching to see if this trips knox...so i am gonna ask at the risk of appearing stupid...
Does it trip knox??
frostmore said:
ok, i tried searching to see if this trips knox...so i am gonna ask at the risk of appearing stupid...
Does it trip knox??
Click to expand...
Click to collapse
Short answer: Yes
Long answer: You are unlocking your bootloader and flashing a custom image so you lose your warranty and trip knox
frostmore said:
ok, i tried searching to see if this trips knox...so i am gonna ask at the risk of appearing stupid...
Does it trip knox??
Click to expand...
Click to collapse
If you want to use s health: Download build.prop editor, grant it root access and and change the value of 'ro.config.tima' from 1 to 0