Develop Bugs

[Q] Can't go back to 4.3 stock rom.

I'm fairly new to custom roms and flashing. On my AT&T Galaxy S3, I decided to update to 4.3. However, I tried updating ota using the About Phone > Software Update, however, that wasn't working for me (It kept saying: No updates available). I knew this wasn't true, so I searched around and found an option (In which all I had to use was the stock recovery and flash it on there, so I did. However, I found out about Knox and how rooting is not an option with knox, so I decided to look into custom roms. I got a custom recovery, noticed warranty bit 1, don't really care about that since I'm out of warranty anyways. So I flashed a lot of custom roms and their versions (Cm 10.2/11, Paranoid Android, Slim Bean, Illusion, and more) only to find out that I can't play any videos (browser, youtube, 3rd party apps, gallery, and even recording camera didn't work)(Also audio doesn't work at all). Now I want to switch back to regular stock 4.3 using the same file I used before. I tried flashing with a custom recovery (twrp and cwm) and it kept giving me:
(assert failed: file_getprop("/system/build.prop". robuild.fingerprint")
== "samsung/d2uc/d2att:4.1.2/JZO54K/I747UCMG2:user/release-keys" ||
file_getprop("/system/build.prop". robuild.fingerprint")
== "samsung/d2uc/d2att:4.3/JSS15J/I747UCUEMJB:user/release-keys"
E:Error in /sdcard/update43.zip
(status 7)
Installation aborted)
I searched around, and other people got this error mostly on a nexus when trying to get back to stock firmware. I found out that I need the stock recovery for the samsung galaxy s3 At&t, which I've searched around, and I can't find. Does anyone know a thread, or can upload their at&t samsung galaxy s3 stock recovery?

Status 7 is an error in the updater script. You may have a bad zip. Have you checked the MD5SUM in the zip that you downloaded?

codemonkey98 said:
Status 7 is an error in the updater script. You may have a bad zip. Have you checked the MD5SUM in the zip that you downloaded?
Click to expand...
Click to collapse
I re-downloaded the zip (which worked before on stock recovery). I don't know how to check the md5sum (On most roms, maybe this one since this one doesn't get to the point where it checks for it, it says checking for md5sum, then later says no md5sum found and skips). Maybe this is because It's expecting me to be on the "samsung/d2uc/d2att:4.1.2/JZO54K/I747UCMG2" version so I can update to the "samsung/d2uc/d2att:4.3/JSS15J/I747UCUEMJB" version. On Keyes 3 under my device apparently my current version is:
I747UCUEMJ2/I747ATTEMJ2//I747UCUEMJ2
And Keyes tells me that my devices current firmware is not supported to update firmware via keyes. Any ideas how to get back to stock? Also, does anyone have a clue why any sound and any video won't work on custom roms for me?

danman0 said:
I re-downloaded the zip (which worked before on stock recovery). I don't know how to check the md5sum (On most roms, maybe this one since this one doesn't get to the point where it checks for it, it says checking for md5sum, then later says no md5sum found and skips). Maybe this is because It's expecting me to be on the "samsung/d2uc/d2att:4.1.2/JZO54K/I747UCMG2" version so I can update to the "samsung/d2uc/d2att:4.3/JSS15J/I747UCUEMJB" version. On Keyes 3 under my device apparently my current version is:
I747UCUEMJ2/I747ATTEMJ2//I747UCUEMJ2
And Keyes tells me that my devices current firmware is not supported to update firmware via keyes. Any ideas how to get back to stock? Also, does anyone have a clue why any sound and any video won't work on custom roms for me?
Click to expand...
Click to collapse
I've had this issue before, VERY annoying. What I did was I downloaded a program for Windows called Notepad++ which allows you to edit the md5sum file.
What you need to do is unzip the file and search for the md5sum file and open it in Notepad++. Delete the lines that read "assert" and have the troublesome ID you mentioned in the OP. Re-zip the file and try flashing it again. Should be fine.

n_alvarez2007 said:
I've had this issue before, VERY annoying. What I did was I downloaded a program for Windows called Notepad++ which allows you to edit the md5sum file.
What you need to do is unzip the file and search for the md5sum file and open it in Notepad++. Delete the lines that read "assert" and have the troublesome ID you mentioned in the OP. Re-zip the file and try flashing it again. Should be fine.
Click to expand...
Click to collapse
I already have notepad++, but where do I search for the md5sum, since I've wanted to use Odin to flash this but it isn't a tar or md5 file. Should I check the updater script? And is this the reason audio and video don't work on any custom room I try?

danman0 said:
I already have notepad++, but where do I search for the md5sum, since I've wanted to use Odin to flash this but it isn't a tar or md5 file. Should I check the updater script? And is this the reason audio and video don't work on any custom room I try?
Click to expand...
Click to collapse
Sorry for sounding like a noob, but I am new to all of this. All I need is some help, I would prefer to run custom roms over stock (I like Illusion) except for video won't work as well as audio? Is there any way to fix that at least, or is there a way to fix my rom/recovery?

danman0 said:
Sorry for sounding like a noob, but I am new to all of this. All I need is some help, I would prefer to run custom roms over stock (I like Illusion) except for video won't work as well as audio? Is there any way to fix that at least, or is there a way to fix my rom/recovery?
Click to expand...
Click to collapse
http://www.sammobile.com/firmwares Search for you're model and download the LATEST firmware. Returning to 4.1.2 or lower will brick you're phone

Ali7000 said:
http://www.sammobile.com/firmwares Search for you're model and download the LATEST firmware. Returning to 4.1.2 or lower will brick you're phone
Click to expand...
Click to collapse
Can't do that since At&t update 4.3 (Latest) is pretty much ota and can't be downloaded from that site. It only goes up to 4.04.

danman0 said:
Can't do that since At&t update 4.3 (Latest) is pretty much ota and can't be downloaded from that site. It only goes up to 4.04.
Click to expand...
Click to collapse
http://www.sammobile.com/2013/11/20/android-4-3-rolling-out-for-the-att-galaxy-s-iii/ Just a news update

Have you tried this rom?
http://forum.xda-developers.com/showthread.php?t=2252932
I have been running this and have had no problems with anything working. As others have said don't flash anything besides 4.3 or you risk bricking your phone.

COfatboy said:
Have you tried this rom?
http://forum.xda-developers.com/showthread.php?t=2252932
I have been running this and have had no problems with anything working. As others have said don't flash anything besides 4.3 or you risk bricking your phone.
Click to expand...
Click to collapse
I am flashing this right now. I hope that this will work. It turns out that only mxplayer videos work, and no other third party video app. I looked around and these issues are most likely from not updated binaries or something, as mentioned in some threads.

Turns out that this rom: http://forum.xda-developers.com/show....php?t=2252932 doesn't work on my phone since it just never boots from the glowing samsung logo. I have attached a link to my video of how audio and video don't workand and only work on mxplayer.
http://www.youtube.com/watch?v=231HdNzlauQ

danman0 said:
Turns out that this rom: http://forum.xda-developers.com/show....php?t=2252932 doesn't work on my phone since it just never boots from the glowing samsung logo. I have attached a link to my video of how audio and video don't workand and only work on mxplayer.
http://www.youtube.com/watch?v=231HdNzlauQ
Click to expand...
Click to collapse
I tried a bit later and got this rom to boot, but I'm having same issues with audio and video. Also, I can't turn on wifi.

danman0 said:
I tried a bit later and got this rom to boot, but I'm having same issues with audio and video. Also, I can't turn on wifi.
Click to expand...
Click to collapse
You will need to flash a kernel to get the wi-fi to work. Try this one. works for me and many others who have suggested it. http://www.androidfilehost.com/?fid=23196940996968860
Post # 3 here, http://forum.xda-developers.com/showthread.php?t=2498233, is where I got that kernel. Be sure to thank him when it works.

BCSC said:
You will need to flash a kernel to get the wi-fi to work. Try this one. works for me and many others who have suggested it. http://www.androidfilehost.com/?fid=23196940996968860
Post # 3 here, http://forum.xda-developers.com/showthread.php?t=2498233, is where I got that kernel. Be sure to thank him when it works.
Click to expand...
Click to collapse
I got the wifi to work, but I still can't record video or hear audio. However, youtube does play up to 4 seconds of video, then the video freezes, but the bar resets to 0 and keeps moving forward and I don't see any more video other than the frozen frame. Could this be because of my custom binary count being 13?

danman0 said:
I got the wifi to work, but I still can't record video or hear audio. However, youtube does play up to 4 seconds of video, then the video freezes, but the bar resets to 0 and keeps moving forward and I don't see any more video other than the frozen frame. Could this be because of my custom binary count being 13?
Click to expand...
Click to collapse
The custom binary count just means you have been busy flashing non-official stuff. It is not related to your audio problem. Are you still on S3rx? Have you Factory wiped since discovering these issues?

BCSC said:
The custom binary count just means you have been busy flashing non-official stuff. It is not related to your audio problem. Are you still on S3rx?
Click to expand...
Click to collapse
Yes, I'm still on S3rx. When I first reboot my phone, I can't see the clock widget on the lock screen, but when i unlock and relock, it appears. Also, my imei and phone info is wiped, but since that doesn't explain audio and video not working, it doesn't matter at the moment. What else could be causing audio and video to not work?

danman0 said:
Yes, I'm still on S3rx. When I first reboot my phone, I can't see the clock widget on the lock screen, but when i unlock and relock, it appears. Also, my imei and phone info is wiped, but since that doesn't explain audio and video not working, it doesn't matter at the moment. What else could be causing audio and video to not work?
Click to expand...
Click to collapse
Sorry but I'm gonna ask a few more questions and see what I can find,
1. When you last tried to flash the stock 4.3 update, did you use the OTA zip that includes Knox and the bootloader?
2. Have you attempted to flash the stock rooted Att S3 image without the bootloader attached. See here:http://forum.xda-developers.com/showthread.php?t=2540998
3. Without imei you aren't receiving service are you?
The reason I'm asking so much about the stock ROMs is because somehow the audio/video issue you are having may be fixed by going back to stock and wiping everything and reinstalling your kernel again. I have not experienced an issue like this myself, these are just the steps I would take.

BCSC said:
Sorry but I'm gonna ask a few more questions and see what I can find,
1. When you last tried to flash the stock 4.3 update, did you use the OTA zip that includes Knox and the bootloader?
2. Have you attempted to flash the stock rooted Att S3 image without the bootloader attached
3. Without imei you aren't receiving service are you?
The reason I'm asking so much about the stock ROMs is because somehow the audio/video issue you are having may be fixed by going back to stock and wiping everything and reinstalling your kernel again. I have not experienced an issue like this myself, these are just the steps I would take.
Click to expand...
Click to collapse
I don't remember what a bootloader is, but I downloaded the stock firmware from here http://www.smartphonejam.com/2013/11/upgrade-att-galaxy-s3-official-android43-i747ucuemjb-ota-update.html since software update option wasn't showing any updates for me. Later on I installed loserskater's 4.3 noknox and selinux permissive version but i had the same problems as i do with S3rx right now. Then I decided to go to custom roms, thats when sound and video don't work at all.
I don't know how to unattach the bootloader image (if there is one).
Yes, I don't receive and service http://www.youtube.com/watch?v=231HdNzlauQ

danman0 said:
I don't remember what a bootloader is, but I downloaded the stock firmware from here http://www.smartphonejam.com/2013/11/upgrade-att-galaxy-s3-official-android43-i747ucuemjb-ota-update.html since software update option wasn't showing any updates for me. Later on I installed loserskater's 4.3 noknox and selinux permissive version but i had the same problems as i do with S3rx right now. Then I decided to go to custom roms, thats when sound and video don't work at all.
I don't know how to unattach the bootloader image (if there is one).
Yes, I don't receive and service http://www.youtube.com/watch?v=231HdNzlauQ
Click to expand...
Click to collapse
I'd recommend heading here and installing the upndwn4par stock ROM again. You did flash the one with the bootloader via that link you sent me. This link does not contain that bootloader. It has already been removed. Flash this and then wipe everything (cache,dalvik and full wipe/factory reset). http://forum.xda-developers.com/showthread.php?t=2540998. This could fix your video/audio issue.
s for your IMEI problem you may find your answer here: http://forum.xda-developers.com/showthread.php?t=2374063

[Guide] Sound on F240 on CM11 E980 rom

Issue: You flash e980 CM11 rom on F240 devices and get absolutely no sound.
Solution: I remember reading and trying somewhere that skvalex' Alsamixer app brings back sound with e980 rom on F240. Problem was, same app did not work with 4.4.2.
1. So I grabbed the files introduced by that app and copied them in their respective places.
2. chmod -R 755 /system/xbin/alsa* (Change permissions of alsa_ctl, alsa_aplay, alsa_mixer to rwxw-xr-x). I did that from adb. I guess it can be done through root-explorer too.
3. Open terminal:
$> su
#> alsa_amixer
It throws some error but It's okay.
And voila! let there be sound...
Why this works: It was obvious that alsa driver for the sound card was not being loaded by default in CM11_e980. skvalex' alsamixer enables this for lot more devices because he wants his app CallRecorder to work on all those devices.
I am sure there's a more convenient method of doing this by editing alsa cards list for your device or something instead of dirty hack. If you know, please share.
Issues:
- This is not persistent. Every time you reboot your device, you got to run alsa_amixer again (or you can do it through some init scripts).
- I have only tested music and notifications. Not sure about calls.
- Not sure about compatibility issues as I just picked these files and copied them to 4.4.2 tree.
- You tell me...
I have attached the files here.
skvalex is the one deserving credit for all the work. I just used his work to our convenience.
EDIT:
I just replaced the original with a flashable zip. After flashing this, you still need to run step 3 as root after every reboot. I tried on CM11 rom and SlimKat. Works fine,

nice catch man...anybody with f240 already tested this?
will try to download cm11 roms and definitely going to try this one...

Thank you!
notohp said:
Issue: You flash e980 CM11 rom on F240 devices and get absolutely no sound.
Solution: I remember reading and trying somewhere that skvalex' Alsamixer app brings back sound with e980 rom on F240. Problem was, same app did not work with 4.4.2.
1. So I grabbed the files introduced by that app and copied them in their respective places.
2. chmod -R 755 /system/xbin/alsa* (Change permissions of alsa_ctl, alsa_aplay, alsa_mixer to rwxw-xr-x). I did that from adb. I guess it can be done through root-explorer too.
3. Open terminal:
prompt> alsa_amixer
It throws some error about module not found or something. It's okay.
And voila! let there be sound...
Why this works: It was obvious that alsa driver for the sound card was not being loaded by default in CM11_e980. skvalex' alsamixer enables this for lot more devices because he wants his app CallRecorder to work on all those devices.
I am sure there's a more convenient method of doing this by editing alsa cards list for your device or something instead of dirty hack. If you know, please share.
Issues:
- This is not persistent. Every time you reboot your device, you got to run alsa_amixer again (or you can do it through some init scripts).
- I have only tested music and notifications. Not sure about calls.
- Not sure about compatibility issues as I just picked these files and copied them to 4.4.2 tree.
- You tell me...
I have attached the files here.
skvalex is the one deserving credit for all the work. I just used his work to our convenience.
EDIT:
I just replaced the original with a flashable zip. After flashing this, you still need to run step 3 as root after every reboot. I tried on CM11 rom and SlimKat. Works fine,
Click to expand...
Click to collapse
That is what I wanted. I was searching this for few weeks. I will test it today! oolay... by the way did you mean that Step 3 by this "Open terminal: prompt> alsa_amixer" ??? Can we just flash it after flashing ROMs? Thank you!

esaintor said:
That is what I wanted. I was searching this for few weeks. I will test it today! oolay... by the way did you mean that Step 3 by this "Open terminal: prompt> alsa_amixer" ??? Can we just flash it after flashing ROMs? Thank you!
Click to expand...
Click to collapse
Yes just that. You can flash it right after flashing roms. :good:

no luck.
notohp said:
Yes just that. You can flash it right after flashing roms. :good:
Click to expand...
Click to collapse
I flashed it after flashing omni. And wrote on terminal as you suggest " alsa_amixer ". But it shows me error amixer: mixer attach default error. No such file or directory. So I rebooted my phone. Still no sound? What do I do now?

esaintor said:
I flashed it after flashing omni. And wrote on terminal as you suggest " alsa_amixer ". But it shows me error amixer: mixer attach default error. No such file or directory. So I rebooted my phone. Still no sound? What do I do now?
Click to expand...
Click to collapse
Ignore that error. You should have sound soon after you execute that command. Don't reboot. Just check it in settings > sound. Let me know how it goes.

Still...
notohp said:
Ignore that error. You should have sound soon after you execute that command. Don't reboot. Just check it in settings > sound. Let me know how it goes.
Click to expand...
Click to collapse
I wrote the command. I waited so long. 30mins. No sound comes to me. I replaced all files to flashable ROM. And flash it from CWM. Now I am waiting the sound. Could you upload the ROM you had installed successfully?

notohp said:
Ignore that error. You should have sound soon after you execute that command. Don't reboot. Just check it in settings > sound. Let me know how it goes.
Click to expand...
Click to collapse
I tried on omni but no success
I executed this command didn't restart still no sound

esaintor said:
I wrote the command. I waited so long. 30mins. No sound comes to me. I replaced all files to flashable ROM. And flash it from CWM. Now I am waiting the sound. Could you upload the ROM you had installed successfully?
Click to expand...
Click to collapse
Okay I will test it with omni rom once I am back home. Could you point me to the link?

here is the link
notohp said:
Okay I will test it with omni rom once I am back home. Could you point me to the link?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2562998

GOT IT!!!
esaintor said:
http://forum.xda-developers.com/showthread.php?t=2562998
Click to expand...
Click to collapse
I figured it out how to make it successful. You forgot something to mention that ONE LINE before the command alsa_amixer.
$ su
# alsa_amixer
This is it. SU command makes the terminal rooted. So it can do whatever I want. Now we have to give a command alsa_amixer.
I have installed AOSP for E988. Sound is working fine. Thank you for your replies and cares.

esaintor said:
I figured it out how to make it successful. You forgot something to mention that ONE LINE before the command alsa_amixer.
$ su
# alsa_amixer
This is it. SU command makes the terminal rooted. So it can do whatever I want. Now we have to give a command alsa_amixer.
I have installed AOSP for E988. Sound is working fine. Thank you for your replies and cares.
Click to expand...
Click to collapse
Glad you got it worked...may be this line ..."I just replaced the original with a flashable zip. After flashing this, you still need to run step 3 as root after every reboot. I tried on CM11 rom and SlimKat. Works fine," had a brief mention but anyway...I will edit the OP...:good:

i have sound already but it reboot when make a call, maybe kernel is not compatible with F240

nguyenthienqui said:
i have sound already but it reboot when make a call, maybe kernel is not compatible with F240
Click to expand...
Click to collapse
Yeap, that's right. I have faced this problem yesterday. I restored stockish. Also CM11 for F240S drains my battery. Never find good ROM.

esaintor said:
Yeap, that's right. I have faced this problem yesterday. I restored stockish. Also CM11 for F240S drains my battery. Never find good ROM.
Click to expand...
Click to collapse
i had same problem with my f240k Android OS drained alot of battery so I switched to Mokee 4.4.2, its AOSP so like 99% CM
battery problem is fixed so is sound....get around 4 hours of SOT
try it if you like:
http://forum.xda-developers.com/showthread.php?t=2639469

Tested of F240L
Just tried this using the CM11 E980 nightlies it worked on my F240L.
Its incompatible with the voice calls however as phone reboots upon dialing a number.
Good Work though as the sound issue had been driving me nuts trying to figure out.

mudu8 said:
Just tried this using the CM11 E980 nightlies it worked on my F240L.
Its incompatible with the voice calls however as phone reboots upon dialing a number.
Good Work though as the sound issue had been driving me nuts trying to figure out.
Click to expand...
Click to collapse
Actually the problem of calls not going through is not an issue for me. I am an avid music listener and am always on earphones. The problem with rebooting on calls is because of proximity sensor.
So basically, if you're on earphones, then you proximity sensor doesn't come into play and you can make/receive calls.
If I find a fix for this one that doesn't involve flashing another kernel, I will post it here. Actually there's a trick but that involves hacking sensors file in the kernel and would render proximity sensor useless. I have used it once as I don't care about that sensor anyway. But it causes little inconvenience in my flashoholicism.
EDIT:
May be someone can try this (http://forum.xda-developers.com/showthread.php?t=2436999? Am at work and only have my work device with me currently.

notohp said:
Actually the problem of calls not going through is not an issue for me. I am an avid music listener and am always on earphones. The problem with rebooting on calls is because of proximity sensor.
So basically, if you're on earphones, then you proximity sensor doesn't come into play and you can make/receive calls.
If I find a fix for this one that doesn't involve flashing another kernel, I will post it here. Actually there's a trick but that involves hacking sensors file in the kernel and would render proximity sensor useless. I have used it once as I don't care about that sensor anyway. But it causes little inconvenience in my flashoholicism.
EDIT:
May be someone can try this (http://forum.xda-developers.com/showthread.php?t=2436999? Am at work and only have my work device with me currently.
Click to expand...
Click to collapse
Thanks but i think the least involving method would be to extract the kernel from this CM11 am running it on my phone got it on a chinese site.
Here's the link http://pan.baidu.com/share/link?shareid=802794836&uk=1392791443 password is "yxnj" to enable download of the file.
It works on F240L but i think also S/K are supported but it comes with lots of chinese bloatware so if we could get the kernel.
We could just flash it on top of E980 Nightlies directly from CM themselves bypassing the chinese bloat and also keep up to date with new bug fixes and updates.

mudu8 said:
Thanks but i think the least involving method would be to extract the kernel from this CM11 am running it on my phone got it on a chinese site.
Here's the link http://pan.baidu.com/share/link?shareid=802794836&uk=1392791443 password is "yxnj" to enable download of the file.
It works on F240L but i think also S/K are supported but it comes with lots of chinese bloatware so if we could get the kernel.
We could just flash it on top of E980 Nightlies directly from CM themselves bypassing the chinese bloat and also keep up to date with new bug fixes and updates.
Click to expand...
Click to collapse
Yeah that's the quickest way and I have tried that kernel. But for my usage, I find CM kernel more stable. Also, I want to try other kernels (present and future) that are out there for E980. With CM11 converging on a stable release for E980, I sure want to use that with it's kernel. But, again, that's a personal preference.

notohp said:
Yeah that's the quickest way and I have tried that kernel. But for my usage, I find CM kernel more stable. Also, I want to try other kernels (present and future) that are out there for E980. With CM11 converging on a stable release for E980, I sure want to use that with it's kernel. But, again, that's a personal preference.
Click to expand...
Click to collapse
I'm not very conversant with the methods of kernel extraction etc.
I reckon you could compare the chinese CM11 Kernel to the stock CM11 one and see which files need manipulating in order to get it working and also what differences exist between the E98X and F240x models.
No pressure though it just my opinion.
It seems F240 models get little support around here, so if we could figure this out it would be great.

[ROM][Status Official] Verizon TMO Hybrid method for Debloating Stock ROM With Knox

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

How I Rooted my S7 on Nougat. PlayStore ROM V3 *outdated but still working*

*I TAKE NO CREDIT FOR ANY OF THIS, IM JUST TELLING HOW I DID IT. I AM ALSO NOT GUARANTEING YOU WILL HAVE THE SAME OUTCOME*
*I recommend going to this new update guide by CVertigo1 in the ROM's section as this version of the PlayStore ROM is outdated.*
Credit for Root and PlayStore Rom goes to jrkruse (https://forum.xda-developers.com/member.php?u=1949695)
ROOTING
1)Flashed stock Nougat ROM
2)Flashed ENG-ROOT found here https://www.androidfilehost.com/?fid=457095661767141717
- Make sure to flash the correct kernel included in the zip file
3) Install SuperSU. Link: https://www.androidfilehost.com/?fid=529152257862710010
- I used the regular Root.bat not the one with tweaks
FIXING LAG
1)Install Flashfire from PlayStore
2)Download the PlayStore Rom from https://www.androidfilehost.com/?fid=457095661767144652
-Transfer the file to the S7
3)Open Flashfire and flash the zip choosing only Mount/ system read/write
4)Now AROMA Installer will pop up and go through all of the terms and conditions
-When asked what to wipe I choose to wipe everything
-Next when asked what bloat to remove I choose the PlayStore Rom which removes all bloat and replaces stock apps with google apps (To see full list of changes refer to the PlayStore thread)
5)Now when my S7 boot it showed no launcher, I simply held the home button down which opened the google search, in there I searched for the playstore app and installed Nova Launcher.
-Now reinstall SuperSU by double clicking the root.bat like before
6) Installed the following apps to help with lag; Lspeed, Greenify, Kernal Auditor, LeanDroid, Force Doze, and SSD Boost
-I used most of the settings found on Lag fix threads for the MM root
My S7 is smooth as butter after all of this, no lag spikes and random crashes like I was experiencing with just the ENG Root flashed.
EXTRA
1)I did have to to a reboot to get the camera to work properly
2) I had to download a Dialer/Contacts and Message app from the playstore because the stock ones were deleted in this process. But the store ones work just fine, I am recieving calls and messages like normal.
3) *Battery life is just a little worse than stock, might be worth waiting for Xposed to released for Nougat.*
Credit for Root and PlayStore Rom goes to jrkruse (https://forum.xda-developers.com/member.php?u=1949695) :good:

setup wizard keeps stopping...
I have followed your step with my phone (Galaxy S7 Verizon - Android 7), but when go to step no 5 my phone always alert (The process com.android.phone has stopped, Setup Wizard keep stopping...). I tried to hold HOME button but still nothing and message always alert even reboot phone.
Please help. thank in advance

Bunrin said:
I have followed your step with my phone (Galaxy S7 Verizon - Android 7), but when go to step no 5 my phone always alert (The process com.android.phone has stopped, Setup Wizard keep stopping...). I tried to hold HOME button but still nothing and message always alert even reboot phone.
Please help. thank in advance
Click to expand...
Click to collapse
Weird, did you wipe your S7 completely before doing the process? I would flash fresh nougat and try again.

UPDATE
Went through the entire process once more and found that wiping but keeping SU image works the best, I chose "no wipe" but it caused random reboots. I then wiped my phone and did as stated in my original post and it is working smooth once again.

ikoyhn said:
Weird, did you wipe your S7 completely before doing the process? I would flash fresh nougat and try again.
Click to expand...
Click to collapse
My S7 model (SM-G930V). it's not compatible with VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V6.zip? while installing show DEVICE: Samsung Galaxy S7 G935V

Bunrin said:
My S7 model (SM-G930V). it's not compatible with VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V6.zip? while installing show DEVICE: Samsung Galaxy S7 G935V
Click to expand...
Click to collapse
The rom is for Verizon and T mobile devices. Your good to go.

Blade22222 said:
The rom is for Verizon and T mobile devices. Your good to go.
Click to expand...
Click to collapse
Bunrin said:
My S7 model (SM-G930V). it's not compatible with VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V6.zip? while installing show DEVICE: Samsung Galaxy S7 G935V
Click to expand...
Click to collapse
Yup it says G935 but it also works with the G930.

ikoyhn said:
Yup it says G935 but it also works with the G930.
Click to expand...
Click to collapse
When install finish after reboot my phone show "Setup Failed....". any ideas. thanks

Bunrin said:
When install finish after reboot my phone show "Setup Failed....". any ideas. thanks
Click to expand...
Click to collapse
Did you start on a factory fresh Nougat? It must be trying to run the setup that you first have to do when you get/wipe your phone. But you should have already done this prior IF you wiped your phone completely and started from there.
Here is another guide that you might find helpful: https://forum.xda-developers.com/verizon-galaxy-s7/development/rom-t3576124

ikoyhn said:
Did you start on a factory fresh Nougat? It must be trying to run the setup that you first have to do when you get/wipe your phone. But you should have already done this prior IF you wiped your phone completely and started from there.
Here is another guide that you might find helpful: https://forum.xda-developers.com/verizon-galaxy-s7/development/rom-t3576124
Click to expand...
Click to collapse
Thanks for your support.

Is this for the Qualcomm processor?

Gon Rouge said:
Is this for the Qualcomm processor?
Click to expand...
Click to collapse
Yes the *US*S7 does have the Qualcomm processor, and this ROM does work with it. If you are looking to see if it will work for another device with the processor then I recommend looking here: https://forum.xda-developers.com/member.php?u=1949695, for more information on the ROM and compatibility.

ikoyhn said:
Yes the S7 does have the Qualcomm processor, and this ROM does work with it. If you are looking to see if it will work for another device with the processor then I recommend looking here: https://forum.xda-developers.com/member.php?u=1949695, for more information on the ROM and compatibility.
Click to expand...
Click to collapse
Not all s7s are Qualcomm, we sometimes get international users in here.

Blade22222 said:
Not all s7s are Qualcomm, we sometimes get international users in here.
Click to expand...
Click to collapse
Whoops forgot about that, I fixed my reply. Thanks for pointing it out:good:

My phone is now stuck on the boot text (Samsung Galaxy S7) have yet to see past it.

IDCM said:
My phone is now stuck on the boot text (Samsung Galaxy S7) have yet to see past it.
Click to expand...
Click to collapse
-After what step did it get stuck on the boot text?
-Did you start factory fresh?

ikoyhn said:
-After what step did it get stuck on the boot text?
-Did you start factory fresh?
Click to expand...
Click to collapse
I've got it all in working order, but to address the issue.
It was just straight after using the first Odin file. (Flashed ENG-ROOT)
Although with hours of sitting here and determination, I came to a solution using this post and many others.
I now have my S7 (Verizon) rooted and functioning with no issues.
Thank you for sharing. :highfive: :good:

IDCM said:
I've got it all in working order, but to address the issue.
It was just straight after using the first Odin file. (Flashed ENG-ROOT)
Although with hours of sitting here and determination, I came to a solution using this post and many others.
I now have my S7 (Verizon) rooted and functioning with no issues.
Thank you for sharing. :highfive: :good:
Click to expand...
Click to collapse
Glad you got it all sorted out:good:

I haven't rooted a phone in a few years but I feel like I missed a fundamental step of the root process so I have a stupid question: I get to the rom flashing step and my phone can't reboot because "Custom binary locked by SECURE BOOT (boot.img)." Then I reflash the ENG-ROOT boot.img and that same secure boot blocks because of the custom modem binary. So I just reflashed stock to get it working again, but it still gives that message if I try to install something like magisk. Am I missing something?

fjgrf said:
I haven't rooted a phone in a few years but I feel like I missed a fundamental step of the root process so I have a stupid question: I get to the rom flashing step and my phone can't reboot because "Custom binary locked by SECURE BOOT (boot.img)." Then I reflash the ENG-ROOT boot.img and that same secure boot blocks because of the custom modem binary. So I just reflashed stock to get it working again, but it still gives that message if I try to install something like magisk. Am I missing something?
Click to expand...
Click to collapse
You cannot use any custom kernels on us snapdragon models. No magisk or anything. The only root option is engboot and root.bat plus the setups to smooth it out or no root at all

Moto z problems

Phone - Moto Z play XT1635-02-DS
Android- 7.1.2
Installed TWRP 3.1.1.0
Viper addison 7.1.2
Here are my problem:
1. Flashed with supersu v2.79 and also v2.82, neither works. Phone still not rooted. When i tried toa access supersu app, it says "there is no su binary installed and supersu can't install it..."
2. Camera does open but it doesn't function, it stays dark. (I have custom gapps 7.1.x)
3. Proximity sensor does not seem to be working in other cases, but the phone goes dark as soon as i press dial or as soon as i pick a call and remains so untill the other party cuts the call. Otherwise i need to shut down the phone if i have to end the call from my phone.
4. When i shut down the phone, in order to reboot manually from recovery-reboot-bootloader. Otherwise it remains in twrp recovery.
Can anyone help please?

Have you tried flashing back to stock and seeing if that fixed these issues?

Pal Guite said:
Phone - Moto Z play XT1635-02-DS
Android- 7.1.2
Installed TWRP 3.1.1.0
Viper addison 7.1.2
Here are my problem:
1. Flashed with supersu v2.79 and also v2.82, neither works. Phone still not rooted. When i tried toa access supersu app, it says "there is no su binary installed and supersu can't install it..."
2. Camera does open but it doesn't function, it stays dark. (I have custom gapps 7.1.x)
3. Proximity sensor does not seem to be working in other cases, but the phone goes dark as soon as i press dial or as soon as i pick a call and remains so untill the other party cuts the call. Otherwise i need to shut down the phone if i have to end the call from my phone.
4. When i shut down the phone, in order to reboot manually from recovery-reboot-bootloader. Otherwise it remains in twrp recovery.
Can anyone help please?
Click to expand...
Click to collapse
This is not really a problem with the phone per se but the rom you chose to flash. The reboot issue can be checked by setting a command at bootloader using "fastboot oem fb_mode_clear".

gman88667733 said:
Have you tried flashing back to stock and seeing if that fixed these issues?
Click to expand...
Click to collapse
Thanks. But i don't have the stock rom. I didn't intend to use a custom rom. I tried to root it to recover some deleted photos and the moron that i am, i didn't back up the stock firmwares and while tweaking around in the recovery i somehow deleted the stock rom. This is my 1st time...

DroneDoom said:
This is not really a problem with the phone per se but the rom you chose to flash. The reboot issue can be checked by setting a command at bootloader using "fastboot oem fb_mode_clear".
Click to expand...
Click to collapse
Thanks... I tried the above command (it does recognize my device) bur this is what i get :
{bootloader} slot-count: not found
{bootloader} slot-suffixes: not found.

Pal Guite said:
Thanks... I tried the above command (it does recognize my device) bur this is what i get :
{bootloader} slot-count: not found
{bootloader} slot-suffixes: not found.
Click to expand...
Click to collapse
Is there an option for the bootloader in developer settings in your rom similar to the screenshot I attached? Make sure it's enabled.

DroneDoom said:
Is there an option for the bootloader in developer settings in your rom similar to the screenshot I attached? Make sure it's enabled.
Click to expand...
Click to collapse
Thanks for your concern. Developer option is 'on' and Multiprocess webView renderers seperately - 'on'. But i get the same problem. (and how do you attach screenshots ? I don't see any option for attaching files) In anycase, like you said, i think the problem has more to do with the rom. Can you please suggest me another rom or if possible link from where i can download stock rom for my phone.

Pal Guite said:
Thanks for your concern. Developer option is 'on' and Multiprocess webView renderers seperately - 'on'. But i get the same problem. (and how do you attach screenshots ? I don't see any option for attaching files) In anycase, like you said, i think the problem has more to do with the rom. Can you please suggest me another rom or if possible link from where i can download stock rom for my phone.
Click to expand...
Click to collapse
If your on xda with your browser, it's the paperclip icon to attach files. If you are using a 3rd party app that wraps xda into it then I can't help you there. As for going back to stock, Motorola made things a little critical when they released Nougat. Depending on how far you were on keeping the device up to date through stock, flashing the available stock images (which aren't signed) could brick the device if you aren't careful. There use to be an account on androidfilehost that uploaded current stock packages but it seems they're all gone now. If you remember the build number of the device before you rooted, that will help in picking the right stock files. I've taken a break in keeping my device rooted so I haven't kept track of the resources used to help go back to stock but they're in the MZP guide threads.
EDIT: a word of caution when reverting to stock:
-Don't use flash tools that don't let you see/edit the fastboot commands
-Do not use commands that touch modem/radio or gpt partitions
Found an upload of the latest build release keep it around when you figure out what you need to flash. It's best to clear system, data, and cache before flashing. Also have a rom (and twrp) at hand to adb sideload in case stock doesn't boot.
https://androidfilehost.com/?a=show&w=files&flid=215703
This Android version 7.1.1
Security patch: Sept 2017
Build number: NPN26.118-22-2

Thanks alot... ?