Related
I stumbled across this method while I was trying to flash my Boost Moto G over to Page Plus the traditional way with DFS/CDMA Workshop. I was having some trouble with it and ran into some issues flashing CM11 and bootlooping so I ended up needing to flash back to stock firmware. I decided to give the stock Verizon G firmware a try, hoping it wouldn’t brick my brand new phone, and it works beautifully. Everything works including stock OTA programming so there’s no need to mess around too much with flashing tools (except for one or two easy steps). A big plus to this method is the 3G data settings/keys get programmed properly OTA so you don’t need a donor phone or to pay someone $$ to flash it for you. It’s a little bit of a process but if you can follow the steps properly it’s fairly easy. Note: These are just the steps I took to make this work. Some may not be necessary but follow them anyway if you aren’t 100% sure of what you’re doing.
Edit: I've tested PAC ROM and Pink Kernel after flashing the Verizon firmware and voice and 3g still work and the rom is stable so far so most custom ROMs that work with the boost moto g should be fine to flash.
Disclaimer:
I am not responsible for anything you do. If you brick your phone or it explodes, don’t blame me. This method was tested by me and worked for me but if you choose to follow this guide you do so at your own risk. If you’re not somewhat technically savvy or are very unsure about any of the steps below please have someone else help you or consider paying for a flash.
Edit (3/16): If you end up with a bootloop/brick please try to flash the stock Boost firmware again as this should bring your device back. You can get version 4.3 here and version 4.4.2 here.
Requirements:
Your Phone’s MEID Activated With Page Plus
Unlocked Bootloader (See Motorola Bootloader Unlock Site)
Minimal ADB and Fastboot
DFS Demo
Verizon Stock Firmware Image (Check your "Android version" under Settings -> About Phone)
> Android 4.3
> Android 4.4.2
> Firmware Flashing Guide (Written for version 4.3, see below for an additional step for 4.4.2 and automated scripts that are safer to use)
Motorola USB Drivers
Your Phone’s MSL/SPC Code (From Boost Activation or MSL Reader App)
Edit: For activating your MEID with Page Plus I recommend going through Kitty Wireless. They currently have a promotion going where you'll receive a free "The $12" plan with any new activation or port in and the service is free as well.
Steps:
1) Go to the Boost Mobile website and activate your phone. You can do this without actually paying for the first month. The only reason we do this is to get the MSL/SPC code for your phone that is listed on the last page of the activation process. Make sure you save this code somewhere safe. Now I did the Hands Free Activation on my phone, and I don’t think you really need to, but it can’t hurt so I’d suggest you do it as well.
Edit (3/16): Apparently it's not necessary to OTA activate with Boost before flashing your phone so you can simply install this MSL Reader on your phone to get your SPC code without activating with Boost. Copy the apk to your SD card and then open and install it with a file manager or push it from your PC with "adb install SPCUtility.apk".
2) Unlock your bootloader. Go to Motorola’s bootloader unlocking site and follow their instructions. They tell you to install the Android SDK but it can be a large download so just get the Minimal ADB and Fastboot zip as that’s all you need to complete this process. Make sure you install the Motorola USB drivers as instructed because we’ll need them later on for DFS.
3) Now we need to reset your phone’s SPC to “000000” so Verizon OTA programming will work properly. You’ll need to start your phone in Fastboot mode (power off then hold the volume down and power button together until you boot into a system menu) then select the “BP Tools” option in that menu. This will boot your phone with the diagnostic port needed for DFS enabled. If the drivers fail to install automatically you’ll need to manually install them by going into Device Manager, finding the one with the red X called “Motorola QC Diagnostic Interface”, right-clicking and selecting “Update Driver Software…”, clicking “Browse my computer for driver software” then “Let me pick…”, choose the device type “Ports (COM & LPT)” and click next, then selecting the manufacturer “Motorola” and the driver “Motorola QC Diag Port” from the list. This is the only one we actually need so if there are others with a red X you can leave them as they are. Now, open DFS. Click “Ports” on the top left. Double-click on the port named “Motorola QC Diag Port”. DFS will automatically connect to your phone. Next we need to send the MSL code we got from the Boost activation. Type it into the “SPC” box under the “Ports” button and click the arrow to the left of the box. The log window should show “DEVICE UNLOCKED”. Now go to the “Programming” tab and click “Read” in the SPC section. It’ll show the MSL code you used and you need to change it to “000000” then click “Write”. Finally, click the “Reset” button on the top right and your phone will reboot. Make sure you do this because the changes won’t stick unless you do.
4) The next step is to flash the stock Verizon firmware to your phone. There’s already an excellent guide on that process so just download the Verizon image and follow those instructions.
Edit (3/16): The flashing guide linked here references version 4.3 of the firmware. If you're installing version 4.4.2 following the guide there are additional commands you need to execute. Here are all the commands necessary for 4.4.2:
fastboot flash aboot emmc_appsboot.mbn
This needs to be stickied. Would have gone with a Boost Mobile Moto G if I'd known it was this simple. I'm stuck with a Verizon Moto G.
thanks Heranthius! Super useful info!
Makes me wonder if flashing Verizon firmware is necessary. Or if you could just upload a pageplus /Verizon PRL to your phone and reset your SPC to 000000 and then try the ota programming?
Super interesting! Wish I had the money to buy another to play with!
edit: typos. kinda hate typing on phones at times.
Sent from my XT1031 using Tapatalk
I can say for sure it won't work that way. I tried it that way before I discovered this method. You can get voice and SMS but the way Sprint programs the data settings is completely different from Verizon so you won't get 3G or MMS working properly without manual flashing and a donor phone.
this is exactly what I was going to try out, but you beat me to it I had already changed my SPC to 000000 but my Boost mobile didn't end until yesterday, I was also surprised that no one else had tried this yet either. Thanks for the guide too! Cheers.
Heranthius said:
I can say for sure it won't work that way. I tried it that way before I discovered this method. You can get voice and SMS but the way Sprint programs the data settings is completely different from Verizon so you won't get 3G or MMS working properly without manual flashing and a donor phone.
Click to expand...
Click to collapse
I see. Thanks again for the post! I got mine working the manual way but had tried so many different things. I had no idea how to write a tutorial. Seems like this could be a simple fool proof way for people!
Sent from my XT1031 using Tapatalk
Heranthius said:
I'd also recommend that you also install CWM/TWRP recovery and root your phone because the Verizon firmware has a ton of bloat pre-installed.
Click to expand...
Click to collapse
So, do you have a CM11 Moto G nightly installed to get away from the bloatware? or just the basic moto g android? also, thanks for this. I was wondering if I could get the OTA to do a few things for me. and yet i'm almost thru the manual way.
glad to see all this work and sharing on the moto g to selectel and pageplus
@cedarknoll - No problem, this was my first attempt at writing a guide too. I just wanted to make sure everyone knows there's a really easy way to do this without wasting $35 on a professional flash or spending hours manually flashing. There's definitely a lot of research to do when trying to flash by hand and I know it took me many hours to get my G set up the way I wanted. Even if you have a working manual flash I would still recommend going with the Verizon firmware because it's less of a hack, you can update your PRL and profile OTA if necessary, and most importantly for me the voicemail notifications work as intended so you don't need the Voicemail Notifier apk from Viper's thread.
Sent from my Page Plus Moto G using Tapatalk
I followed this guide to the letter. I got it to activate with talk and text, but no data. Looks like it still needs manual tweaking after the fact - which I will do this weekend.
@Flinkly - Right now I'm just running the stock Verizon rom. All I did was use Rom Toolbox to freeze all of the bloat apps. Like I said in the OP, the first time I flashed CM11 I had a bootlooping issue and I haven't had time yet to try and sort it out. I love this phone though so far and I hope some devs start coming out with Verizon roms soon. The Moto G is amazing for the price and one of the best prepaids available right now I think.
Sent from my Page Plus Moto G using Tapatalk
@micallen - That's odd. When you look in the DFS settings did it write any of the Verizon information under Data and Mobile IP? What version of Android are you on? I did the OTA update to 4.4.2 before flashing my phone. Also, did you do the Boost hands free activation before flashing the Verizon firmware? I read somewhere in another thread that you may need to do that in order to unlock/make writable the NV items for the data settings.
Sent from my Page Plus Moto G using Tapatalk
Heranthius said:
...and most importantly for me the voicemail notifications work as intended so you don't need the Voicemail Notifier apk from Viper's thread.
Click to expand...
Click to collapse
that's some super good info to know!! That apk doesn't seem to work on the moto g anyway. I think most people are using the youmail app as an alternative. Even some of the paid flashers just put you mail on there for people.
Sent from my XT1031 using Tapatalk
Nice job man!
Sent from my XT907 using Tapatalk
Heranthius said:
@micallen - That's odd. When you look in the DFS settings did it write any of the Verizon information under Data and Mobile IP? What version of Android are you on? I did the OTA update to 4.4.2 before flashing my phone. Also, did you do the Boost hands free activation before flashing the Verizon firmware? I read somewhere in another thread that you may need to do that in order to unlock/make writable the NV items for the data settings.
Sent from my Page Plus Moto G using Tapatalk
Click to expand...
Click to collapse
4.2.2
I tweaked the settings (couldn't wait) in DFS and have 3G now. 1.3 down and 1.0 up. Thanks for the guide !
Nice method, I don't have a moto g with me at the moment but I am wondering if only some of the images from verizon package need to be flashed.
Is only:
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
required? the other image seemed more related to just the android system, recovery and booting. I'l be nice if someone that had a boost motog with them could test out which ones are actually required.
@micallen - Awesome, I'm glad it worked for you. You're welcome! Could you post the settings you had to tweak so people trying this method can know what they need to change in DFS? When I flashed my phone I had to tweak the "Primary & Secondary HA Address" and "Min HA & AAA SPI set" boxes on the "Mobile IP" tab.
Sent from my Page Plus Moto G using Tapatalk
@imkey - I think you need to flash the whole system because it's the setup/activation apk of the rom that actually programs the data settings and that's why you need the one from the Verizon firmware in order to OTA program the 3G settings successfully.
Sent from my Page Plus Moto G using Tapatalk
OK I'm a noob at this and this is where I'm stuck any help would be greatly appreciated The next step is to flash the stock Verizon firmware to your phone. There’s already an excellent guide on that process so just download the Verizon image and follow those instructions.
It won't let me open up mfastboot. It just flashes and disappears
I have all the files in falcon_boost_user_4.3_14.10.0Q3.X-84-9_11_release-keys-cid9.xml folder. I just can't figure out how to load the V Firmware on this phone. I'm actually surprised I got this far LOL I have the phone in "fastboot mode" and I'm here in .cmd mode F:\MOTO G\Minimal ADB and Fastboot>
@blueyzfr6 - I'm not near my computer right now but I can try to help from memory. It sounds like you have the Boost firmware downloaded from the "boost" in that folder title. You need to check what version of android you have under settings -> about phone and download the Verizon firmware for that version. It'll either be 4.3 or 4.4.2 and the 4.4.2 one is called "Blur_Version.173.44.20.falcon_cdma.Verizon.en.US" on the download page. Once you get that and extract it there should be a .bat file inside the folder with the firmware title as the file name (I think). Open it in notepad (right click -> edit) and after the line that says "%fastboot% reboot-bootloader" add "pause" on a new line then save it. Double click the bat file to run it. If you get an error that it can't find fastboot.exe there's a sub-folder in there that has fastboot.exe and 2 .DLL files. Copy those into the folder with the .bat file and run it again. Your phone should reboot right away and the console window will say press any key to continue. Wait for the phone to get back into the fastboot menu then press enter. Now it should flash all the image files and when your phone reboots you should have the Verizon firmware and then just perform the activation steps as instructed.
Sent from my Page Plus Moto G using Tapatalk
Thank you so much for this mini-guide. I followed it all and everything seems to work until activating. I did DL the regular verizon firmware, not the Blue one. Don't know what that is for or the difference. I live out of reception, so it's a bit more challenging for me to see what works. I drove to a place with reception, tried to activate it (while showing roaming) and it failed to activate it. I did have the phone already activated on Boost so am not sure if this actually needs to happen. I did submit an ESN change and it went through, though when i checked the ESN verification, it came back "Unknown"
More to come once I try making a phone call and try the internet.
I HAVE A SM-G930F S7
GOT IT FROM ONE OF THOSE RENT TO OWN PLACES AND IT IS STUCK WITH THERE FIRMWARE
and i can not upgrade to the latest nougat build
was wondering how do i determine what the factory shipped firmware should be so i could download
it from sammobile... but i can not find my region code on the site..
I LIVE IN SAGINAW,MICHIGAN USA
any help would be appreciated
BASEBAND: G930FXXU1APB4
BUILD NUMBER:MMB29K.G930FXXU1APB4_RAC_V1.0.0
WOULD LIKE TO BE ABLE TO UPGRADE
I'm coming across the same issue - did you ever figure it out? I'm thinking of flashing a stock firmware (but can only find an updated one), then rooting. But without being able to access developer options, I'm leary of doing even that.
stgibson said:
I'm coming across the same issue - did you ever figure it out? I'm thinking of flashing a stock firmware (but can only find an updated one), then rooting. But without being able to access developer options, I'm leary of doing even that.
Click to expand...
Click to collapse
It might depend on who your carrier is.
Not being able to access developer options? What are you talking about? Go to system settings>about>build number or system settings>about>software info>build number or something similar, find the "build number" or "build no.", tap it 7 or 8 times quickly untli you see the notification that you've unlocked developer options.
Sent from my LGL84VL using Tapatalk
Droidriven said:
It might depend on who your carrier is.
Not being able to access developer options? What are you talking about? Go to system settings>about>build number or system settings>about>software info>build number or something similar, find the "build number" or "build no.", tap it 7 or 8 times quickly untli you see the notification that you've unlocked developer options.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Thanks, @Droidriven! I'm going to be using it on AT&T, then on China Unicom. And I want it unlocked. Thus why I got the G930f, not g930a. This phone hasn't locked me out of the system (yet). I did manage to find a build with the same base as mine (G930FXXU1APB4 at https://updato.com/firmware-archive-select-model?record=07054BA22E5811E6815B0CC47A44B7B2). But my build is MMB29K.G930FXXU1APB4_RAC_v1.0.0, and device status says "custom". When I go into the software info, I can tap on everything else and get a "greyed" response, but not when I tap on build number. Seems to be a locked down version. [Edit: downloading a "developer options" app lets me get to it.] That said, I think this thread (https://forum.xda-developers.com/galaxy-s7/how-to/s7-sm-g930f-rent-center-lock-workaround-t3518682) may work, even though my device hasn't locked me out like some people have had. I'll try that method this morning with the similar stock build and see.
My main concern is causing an issue because of not having USB debugging and /or OEM unlock enabled. Especially if I go straight to a newer version that may require the pin unlock for boot (I saw one of the stock rom pages, can't find it again right now, with 8.0 roms had warnings all over that pin unlock on boot had to be enabled prior to flashing, otherwise you'd flash it and it'd ask for the pin and no luck).
So do you see any problem being able to flash according to the link above without the developer options enabled? [Edit: now that I can get access to developer options through the app, I'm less worried.]
For future reference, this worked, following the instructions (modified slightly here) by bishopag at https://forum.xda-developers.com/galaxy-s7/how-to/s7-sm-g930f-rent-center-lock-workaround-t3518682 worked, using the G930FXXU1APB4 baseband at https://updato.com/firmware-archive-select-model?record=07054BA22E5811E6815B0CC47A44B7B2.
1. Install one of the "bootloader options" from Play Store, use it to ensure that OEM unlock and USB debugging (optional?) are enabled
2. Download the Stock firmware of your choice from Sammobile [or from above link]
3. Unzip/unrar it and pull out the BL and CP for bootloader and modem
4. Grab TWRP from https://dl.twrp.me/herolte/twrp-3.2.3-0-herolte.img.tar.html
5. Grab Odin 3.12 from http://odindownload.com/SamsungOdin/#.WFBEZsmB3mE
6. Put the Device in Download Mode (Hold Vol Down, Power, Home)
7. Use Odin to flash TWRP to the device (AP)
8. Reboot into Recovery Mode (Hold Vol Up, Power, Home)
9. In TWRP use Advanced Wipe to Wipe everything except the SD Card. If it fails use Reset Data first, then Wipe
10. Go to Advanced -> Terminal Command -> hit "Select"
11. type these comands
dd if=/dev/zero of=/dev/block/sda11
dd if=/dev/zero of=/dev/block/sda13
(Note: I got a message that storage was full, but on inspection I could see that the data had been written based on input & output bytes)
12. Do a factory reset with the recovery
13. Reboot into Download mode from TWRP Reboot menu
14. Use Odin to Flash the BL, CP, and AP
15. That's it. Wait for it to boot and setup (might take 5-10 min)
stgibson said:
Thanks, @Droidriven! I'm going to be using it on AT&T, then on China Unicom. And I want it unlocked. Thus why I got the G930f, not g930a. This phone hasn't locked me out of the system (yet). I did manage to find a build with the same base as mine (G930FXXU1APB4 at https://updato.com/firmware-archive-select-model?record=07054BA22E5811E6815B0CC47A44B7B2). But my build is MMB29K.G930FXXU1APB4_RAC_v1.0.0, and device status says "custom". When I go into the software info, I can tap on everything else and get a "greyed" response, but not when I tap on build number. Seems to be a locked down version. [Edit: downloading a "developer options" app lets me get to it.] That said, I think this thread (https://forum.xda-developers.com/galaxy-s7/how-to/s7-sm-g930f-rent-center-lock-workaround-t3518682) may work, even though my device hasn't locked me out like some people have had. I'll try that method this morning with the similar stock build and see.
My main concern is causing an issue because of not having USB debugging and /or OEM unlock enabled. Especially if I go straight to a newer version that may require the pin unlock for boot (I saw one of the stock rom pages, can't find it again right now, with 8.0 roms had warnings all over that pin unlock on boot had to be enabled prior to flashing, otherwise you'd flash it and it'd ask for the pin and no luck).
So do you see any problem being able to flash according to the link above without the developer options enabled? [Edit: now that I can get access to developer options through the app, I'm less worried.]
Click to expand...
Click to collapse
I'm very familiar with flashing stock firmware on Samsung devices but I'm not familiar with the things that you are freaking out about.
Flashing a full stock firmware "should" remove the custom binary, it should say "official" when you're done.
As for build number, that shouldn't matter so much, as long as you are flashing a firmware that is meant for your model number. If you'll be using it on AT&T then flashing the AT&T stock firmware for G930F "should" work.
I've never encountered the issues that you are running circles around so I'm not sure my advice will do you any good. I don't want to walk you into any issues that I'm not sure I can help you solve.
Edit: It looks like the member that posted above has the solution you need, give it a try.
Sent from my LGL84VL using Tapatalk
PREWARNING
THIS GUIDE IS !!ONLY!! FOR N9600 (INTERNATIONAL Snapdragon Model)
DO NOT ATTEMPT ON SPRINT, VERIZON, T-MOBILE, AT&T, OR ANY OTHER US (United States) MODEL PHONE.
BEWARE!! N960U or N960U1 HAS A LOCKED BOOTLOADER WHICH CAN NEVER BE UNLOCKED!
IF YOU ATTEMPT TO ROOT ON ANY US MODEL, YOU WILL BRICK YOUR PHONE!
If you have an N9600 international snapdragon model, please proceed. If not, read for your pleasure or future consideration but DO NOT attempt on a US model.
This guide can also be useful for N960F or N960FD international Exynos models, but you would have to change some things like use the right links.
==================================================================================================
Intro Notes:
I REPEAT: THIS GUIDE IS !!ONLY!! FOR N9600 (INTERNATIONAL Snapdragon Model)
If you have an N9600 international snapdragon model, please proceed. If not, read for your pleasure or future consideration but DO NOT attempt on a US model.
After much thought, research, reading, and contemplation, between Note 8, Galaxy S9+, and Note 9, I have decided on the Note 9.
Out of the available options for rooting, there are the devices, N960F, N960FD, and N9600.
Of course, N960F N960FD are Exynos. Unfortunately, these will not work on Verizon, so I would have to switch to T-Mobile. To stay on Verizon it would have to be N9600.
Ultimately, I decided on N9600. Why? Because with Detonator, I can root the N9600 on Verizon, and it's the only model that I can use on Verizon fully rooted. (There is a partial root on N960U, the US Snapdragon variant, but the root is only partial and will have bugs or may not wok.) I could root with a partial root the Note 8 US version, but it is not that much cheaper and it would only be a partial root, so I decided on N9600.
You can root fine on the Exynos versions, but you could not use Detonator for WIFI calling and other features on Verizon.
Rooting Guide
0. Battery must be above 82% before rooting.
1. Root N9600 using TWRP method (Beta)
PLEASE READ ALL INSTRUCTIONS THERE FOR ROOTING.
https://forum.xda-developers.com/ga...ecovery-twrp-galaxy-note9-snapdragon-t3845536
(Official XDA Magisk Install Guide, don't follow directly just reference)
2. RMM State Fix (Prevent "Prenormal")
IMMEDIATELY after getting into TWRP, flash the RMM-State_Bypass_Mesa_v2.zip (linked below).
If you do not, then you will get locked out for 7 days in the event you flash anything or flash a new OS or downgrade to Oreo, etc.
You have to do this EVERY TIME you flash something to prevent RMM state to going to "Prenormal" which means wait 7 days before you can flash any non-samsung firmware.
3. How to fix: Stuck on Prenormal and didn't bypass, OEM Unlock missing
You might be stuck because you didn't do the RMM bypass above. In this event, you will be blocked from flashing custom binaries including TWRP. The only thing you will be able to flash is original Samsung firmware.
How to bypass now? There are two solutions for solving Prenormal RMM state. I have done both successfully. There is a third but it rarely seems to work (date hack, available at many sites.)
METHOD 1: Long way around. Wait 7 days.
First wipe your whole device again and reflash your original OS in ODIN. If you don't do this then it's possible that after 7 days, OEM unlock will not show up.
Now wait 7 days.
Do not reboot your device, just for good measure. I did reboot my device, several times, and it still appeared after 7 days and a reboot. Don't know if you'll have the same luck.
The second time after turning on OEM Unlock, however, when it wiped my device, I did NOT reflash the whole OS again. And, after 7 days again, it did NOT show up.
METHOD 2: I waited 7 days, but no OEM unlock! Solution: Chimera application for windows. NOT FREE!
I was tired of waiting so I decided to try it, and it worked.
Activate Developer options
Activate USB Debugging (in Developer Options)
DISABLE "Verify apps via USB" (in Developer Options)
Go to https://chimeratool.com/
Buy the 3 days trial.
Download after paying in PayPal.
Install full application and all drivers. Don't customize it just install full.
Put your phone into Download mode
Turn off phone.
Hold Bixby & Volume Down
Plug phone into PC.
Press volume up at prompt. Download mode will be activated.
Now in Chimera application in Windows it will find your phone.
Choose the option "UNLOCK".
Choose the sub option, "RMM Unlock".
SUCCESS!! NO WAITING!! OEM Unlock activated. Worth every penny in my opinion (because it wasn't too many pennies).
Proceed to install TWRP and DO NOT FORGET TO INSTALL RMM BYPASS AFTER EVERY SINGLE FLASHING OF ANYTHING!!
4. After rooted, flash Detonator
File: Verizon EFS/CSC Detonator: Detonator v3 for Oreo 8.1 (linked in file list below)
(There is no Detonator for Pie on Verizon as of this writing, only Oreo)
0. Download DETONATOR_XXX_OREO_VZW_EFS-CSC_vx.x_INT_TEKHD.zip to your phone.
Maybe just copy to your SD card, easiest way.
In order to flash detonator, in TWRP select every box on the Mount screen (OTB will not be available unless you have one connected, but everything else).
Backup all partitions via TWRP.
Then go to Install (in TWRP) and flash the zip file for Detonator which applies to you. (Do NOT flash right after flashing a ROM!; First boot ROM at least one time… then go back to TWRP and flash Detonator)
After you successfully flash detonator and there are no errors, now if you want to remove the Verizon boot screen now go ahead and flash (through Install screen in TWRP) the Samsung BootAnimation zip on the Detonator website. This will replace your boot with the stock black samsung boot.
After doing these, please remember to flash the RMM State zip file. Always do this again after every flash of anything in TWRP!
Detonator features (from the website):
*With the Verizon Detonator you will get:
– VoLTE, Wifi-Calling /4G/LTE/ONLINE services & features.
– AdAway
– AppLock
– OperaMax (VPN/Data Saving)
– Caller ID & Spam Protection
– Phone and messaging Firewall
– Floating Messages
– Screencast/ScreenRecorder
– Ultra Data Saving Mode
– When booting for the first time… turn off “Confirm Network Connection” Under Settings -> Connections… (*IF AVAILABLE*) (see image below)
Changelog for Verizon Detonator:
v3 – CSC Features added / Wi-Fi Calling APK Update
vPRE-2.2 – Smart Manager Device Security Fix
vPRE-2.1 – Added Mobile Data Toggle to Power Menu.
vPRE-2 – Fixed XML Code / Features Added
vPRE-1 – Initial Release. (Test Phase)
NOTE: After installing Detonator, WIFI Calling button disappeared. I confirmed that I do NOT have WIFI calling, sadly. It doesn't work.
Test it by turning on airplane mode, then connecting to WIFI, then try to make a call. You will get a popup with option to turn on WIFI calling. If you try, it will result in an error, "Unable to activate WIFI Calling at this time, please try again later".
There is presently no solution I am aware of, but maybe someone else knows how, search the forums. Also maybe it has to do with the particular OS I decided to use. I could start over from scratch and try again, but it would be a lot of work and I am out of time for now.
Keep in mind you have to activate on Verizon (see below) before trying to make a call.
5. ACTIVATE ON VERIZON:
Activating on Verizon cannot be done through their site, it will result in an error that your device is incompatible, so don't bother with that.
0. In order to activate you just need an already working SIM card.
Activate a new Verizon SIM card on your PREVIOUS device.
If you need an excuse say you need it for your new phone and YOU will activate it yourself right in the store. Then say it's not working let's try activating on my old phone first.
After the new SIM is working on your OLD phone, leave the store and go home. Now, at your leisure remove the SIM from your old phone and now insert it into your N9600.
Reboot. Now you will be activated on Verizon! (NOTE: YOU MUST ALREADY HAVE DONE DETONATOR, FOLLOW ALL STEPS ABOVE FIRST.)
After you do the rooting below, you'll get messages from SecurityLogAgent saying "security error your device was modified, reboot to revert the changes". You can eliminate this by going into Titanium Backup and FREEZE the following:
SecurityLogAgent
Security policy updates
Software update
Configuration Update
6. Magisk Manager
Boot into phone. If you see Magisk Manager it means you are rooted, probably.
To check it open the Magisk Manager app on your phone.
Feel free to update Magisk. I updated it in the app to 19.3 for Magisk and the installer (flashed from the zip in TWRP) is 7.2
Tap to start safetynet, and accept all prompts.
Reboot
Test if rooted by installing Titanium Backup. If it asks for SuperSU permission then Grant, and it means you are rooted!
7. After rooted, install Xposed
Download xposed from the link in the files section below. If you have a Note 9 on Oreo 8.1 then your file is the SDK 27 for Arm64.
In TWRP, flash the zip file.
Now flash the RMM State zip file. Always do this again after every flash of anything in TWRP!
Backup if desired.
Boot your phone.
Go to the xposed links and get the APK file for xposed. This will be the app you use to manage xposed.
WARNING:
One or more of the settings in the xposed module GravityBox [O] causes bugs and removes your Verizon compatibility. In order to solve the error "No SIM card inserted" (but it is inserted!), what you have to do is to go back into TWRP, and do all steps for the Detonator instructions that I wrote above (it will NOT wipe your device, so don't worry). Once you re-flash Detonator, your Verizon will work again and the SIM card message will be gone.
WARNING 2:
There was another xposed module that caused a similar issue but worse. The issue in reference is you get a black screen at the lock screen but nothing can come up but the reboot menu. You cannot get into the phone. I was about to consider having to factory reset before I solved the issue. Since the issue was an xposed module, then the solution is to:
Download the most recent arm64 xposed uninstaller .zip file from here: https://dl-xda.xposed.info/framework/uninstaller/
Boot into TWRP, flash the xposed uninstaller zip.
Clear the cache and dalvik cache like it suggests using that button on the screen there.
Now flash the RMM State zip file. Always do this again after every flash of anything in TWRP!
Reboot into your phone, your problem is now solved!
Finally, go into Xposed Installer and find the Module that was causing the issue, long-press on it and choose uninstall. I know you want to keep it, but it's too bad, you can re-download it later, you will be unable to simply unselect it. You have to uninstall it.
Now you can go back into TWRP and reinstall xposed.
Last step: flash the RMM State zip file. Always do this again after every flash of anything in TWRP!
Files Needed
ODIN: https://odindownload.com/
- Odin 13.3.1
TWRP: https://forum.xda-developers.com/devdb/project/?id=29220#downloads
- TWRP_3.2.3-0_N9600_beta3.tar.md5
- boot.img (he recommends to use this, see tutorial)
- Encryption disabler.zip
MAGISK: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
- Magisk 16.7 19.3 (can I use latest version 19.3? Answer: YES, I used 19.3 without any problems.)
USB DRIVERS: https://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
- SAMSUNG_USB_Driver_for_Mobile_Phones.zip
BYPASS RMM STATE: https://forum.xda-developers.com/showpost.php?p=75360965
- RMM-State_Bypass_Mesa_v2.zip
DETONATOR: http://tekhd.com/detonator-o/
- DETONATOR_N9_OREO-8.x_VZW_EFS-CSC_v3_INT_TEKHD.zip
DIRECT LINK (VZW v3): https://androidfilehost.com/?fid=11410963190603842742
MIRROR: https://mega.nz/#!cP52EYKS!L9Oc7nihQ2RoXddZPAPXCPdVLvzhXq3VZtaZXGzBtDQ
(link is was down but I have the file which I uploaded for you: [EDIT: TekHD link is back up now! The domain was expired but I spent some time on the phone with GoDaddy trying to renew their domain for them, maybe the dev was able to see it since I told them to reach out to him specifically. GoDaddy refused to let me donate to renew his domain for him. Again update it appears the site is down again. But not expired this time, it just says "pageok". I do have all the data from that site so I will upload it for the community sometime.]
XPOSED (for Oreo 8.1): https://dl-xda.xposed.info/framework/sdk27/arm64/
- xposed-v90-sdk27-arm64-beta3.zip
XPOSED UNINSTALLER (to fix a bad module. See Warning 2.): https://dl-xda.xposed.info/framework/uninstaller/
- xposed-uninstaller-20180117-arm64.zip
OREO 8.1 FIRMWARE (for downgrade):
- N9600ZHS1ASB1 / N9600OWA1ARL5 (N9600 8.1 Oreo 2019-02-01 Chile) https://www.sammobile.com/firmwares/galaxy-note9/SM-N9600/CHL/download/N9600ZHS1ASB1/259310/
- N9600ZHU1ARG6 / N9600OWA1ARG6 (N9600 8.1 Oreo 2018-07-01 Dom Rep) https://www.sammobile.com/firmwares/galaxy-note9/SM-N9600/CDR/download/N9600ZHU1ARG6/231741/
- N9600ZHU1ARG6 / N9600OWE1ARG6 (N9600 8.1 Oreo 2018-07-01 Ecuador) https://www.sammobile.com/firmwares/galaxy-note9/SM-N9600/ALE/download/N9600ZHU1ARG6/231755/
** These three files have been removed from sammobile as of today 2019-05-25, because they were there yesterday. You can still view directly but they will no longer show on the page for the N9600 because sammobile is no longer showing any Oreo (8.0, 8.1) firmwares for the N9600 on their site, only Pie firmwares (9). It's likely these will be removed soon, so I will upload mirrors to the firmwares once they are finished downloading.
(NOTE: DO NOT download firmware N9600ZHS1ASA7_N9600OWT1ARK1_SAM because it will after initializing forcefully change your boot branding to a bright baby blue screen with Movistar carrier branding instead of a normal black samsung boot screen. This will be removed by re-flashing so it's harmless, just annoying. Instead use the above linked. So far I have only tested N9600ZHS1ASB1 above which is fine, it is on the Clara carrier and installs minimal carrier bloat which can be removed after rooting. I linked the other two which I will try as they use pre-August 2018 firmware so hopefully I can get the OEM Unlock to show since I didn't know about the RMM state fix before flashing Pie down to Oreo.)
UPDATE:
This guide is now completed and released. The steps are fully working to get your N9600 working on Verizon.
Someone asked me if regular calling works if they don't have WIFI. Of course. Your phone will fully work on Verizon as normal. In addition to fully working, WIFI calling also works (for some firmwares).
UPDATE 2:
DEAR EVERYONE:
Sorry it took so long for me to upload the files. It appears that TekHD website is now dead for good. It's been down for months. So, since I already had downloaded all the content from the website, including the website pages themselves, I'm now uploaded everything from TekHD for your use. I'm also including all of my rooting files for your use and enjoyment.
Will update the links here when the uploads complete. Enjoy!
EDIT: Here's the link!
https://mega.nz/#F!UbZFSAwC!FObELw39ZmADygAJOFVlyw
-
[moved content from here into original post]
[reserved]
I used a exynos S9+ and I'm using a note 9 exynos on Verizon. You don't need to flash anything because if you use shortcutmaster to bring up Ims settings, with root of course, you can enable all you need.
But you don't have wifi calling or several other things right?
I also had to do a RMM state flash. But I didn't know and now I am blocked from doing anything for a week after downgrading OS. Wish someone would have told me ahead of time. The hacks to change date to bypass and re-enable OEM lock DOES NOT WORK. Trying many things, wasted my whole saturday needlessly.
I finally got the OEM unlock to show.
STEPS:
1. Using Odin flash the whole OS from sammobile. I used 8.1 which is compatible with Detonator.
2. During setup, DO NOT CONNECT TO INTERNET.
3. Choose a date some time in the past like a month or even a year ago. I chose a year ago.
4. finish setup disabling everything.
5. General Management → Date and time. DISABLE Automatic date and time.
6. Enable developer options.
a. Settings > About phone
b. tap seven times on ‘Build number’
7. Settings > Developer options > DISABLE Auto update system
8. It will not work unless you also log into a samsung account.
a. Connect to internet now.
b. Cloud and accounts > Accounts > Add account
c. Sign in or create a new Samsung account.
d. You have to log in and add the account, go back and it should say added.
9. DISCONNECT FROM INTERNET
10. Go to date and time. Choose a date in the future. I chose a few months in the future.
11. Settings > Software update > tap on Download updates automatically (it will error because not connected. It's fine. Don't connect!)
12. REBOOT
13. Settings > Developer options. The OEM unlock option should be visible now.
I think the above is what I did. I might have the order above wrong because I tried so many times I can't remember if that's the exact order. I think it is, but if it doesn't work try a few different ways and eventually you'll get it.
EDIT: When I tried again, above does not work so I must not have remembered what I did perfectly, OR for some reason it just didn't work the second time.
[.]
Before I bust out the Type-C cable, I must ask, will this work on the Sprint variant?
Any plan to ad sprint to the list
eastside08 said:
Before I bust out the Type-C cable, I must ask, will this work on the Sprint variant?
Click to expand...
Click to collapse
NO!!! BEWARE, N960U or N960U1 HAS A LOCKED BOOTLOADER.
IF YOU ATTEMPT TO ROOT ON ANY US MODEL, YOU WILL BRICK YOUR PHONE!
The ONLY Snapdragon model that can be rooted is the INTERNATIONAL N9600. I specifically bought the N9600 for this. This N9600 has an unlocked bootloader.
I was planning on running Detonator on the Oreo 8.1 since the developer TekHD has not yet developed a Detonator for Pie on Verizon. Plus, I read that many people prefer Oreo over Pie. Moreover, Oreo will have more dev support than Pie since Pie is still very new.
I am still working on this so will continue progress updates.
Right now I am stuck because I didn't know about the RMM State so I am stuck on Prenormal, which means 7 days waiting. I had gotten the OEM unlock to show because I was going to disable and re-enable OEM unlock, and when I proceeded it wiped, and then changed to Prenormal preventing from installing TWRP again.
If I had known ahead of time, I could have flashed the RMM fix zip while I had TWRP on there and could have avoided this fiasco. If I get OEM unlock to show again then I will use that to avoid future lockouts.
Right now I am downloading a July 2018 version of Oreo 8.1. I tried flashing several Oreo 8.1 and that is easy with Odin, but could not get the OEM unlock to show up again no matter what I tried. According to this page** (link below), the method of switching the time doesn't work on pre- August 2018 firmwares. That's not entirely accurate as I got it to show up the first time, but I may be stuck now.
So in an effort to try anything, I am downloading and will flash the earlier version of 8.1 from July. Then will try the date method to try to get it to show up. Hopefully it works.
** NOTE: link from above is https://www.thecustom droid.com/prenormal-rmm-state-on-samsung-galaxy-guide/ (remove the space between custom and droid)
For future reference, guides go in the guides section, not development.
Update: I can't get OEM unlock to show up and ran out of time. So, I have to take the long way around and wait a week for it to show up. So, I'll be back on Sunday if OEM unlock shows up.
Im guessing this trips knox ?
why put 'Verizon Full Rooting Guide' when rooting has nothing to do with carriers.
the guide is to get verizon csc on a n9600. you should change the way you named the thread if you dont want to get a gazilion questions from n960u uers.
i sure am confused.
are you able to root a international note9 and use it on verizon network in the usa, or not?
i know elliwigy is working on getting root for a specific model of note9, i think for the usa unlocked or verizon locked model, but it's not useable on stock firmware yet.
UPDATE:
After 7 days, a reboot, and pressing check for updates (but not updating), then checking for the OEM unlock, it did in fact show up.
Unfortunately, enabling OEM unlock also factory resets your phone which AGAIN puts the 7 day lock - which is f*ing ridiculous.
So now I have to wait ANOTHER 7 days before proceeding, so that Prenormal will be able to go to Normal and I can flash TWRP and custom binaries.
Will update again in another week.
bober10113 said:
why put 'Verizon Full Rooting Guide' ... if you dont want to get a gazilion questions from n960u uers.
Click to expand...
Click to collapse
Please note the tag [N9600], if N960U users fail to read the full title, that's their fault. I put all the disclaimers in red anyway just in case, so they can know.
This indeed is about using an international N9600 on Verizon in the USA. I am still working on this and as per my previous post, in another week once the 7 day wait period is over again so I can finish the root and flashing, then I will continue to update about how to get the N9600 working on Verizon.
It is worth noting that you are required to root the N9600 in order to use Detonator.
siriom said:
Im guessing this trips knox ?
Click to expand...
Click to collapse
The answer to this is Yes. It trips Knox. You cannot root without tripping Knox.
dumbfone said:
are you able to root a international note9 and use it on verizon network in the usa, or not?
i know elliwigy is working on getting root for a specific model of note9, i think for the usa unlocked or verizon locked model, but it's not useable on stock firmware yet.
Click to expand...
Click to collapse
The answer to this is hopefully yes, and I have known others to get the N9600 working on Verizon. But I have to wait another week before I can proceed, so please check back next week to see my progress and additional instructions.
Hello everyone,
I have wonderful and amazing news. I have completed fully rooting my Note 9 N9600 and also getting it fully working on Verizon. I am updating the original post now with the details and remaining steps.
It's worth noting that after the second 7 days, OEM unlock would NOT show up. I waited hours more, but still no luck. Instead, I used an application called Chimera which I actually paid for in order to get OEM unlock to finally show up, and it worked.
Update: See the above completed and updated guide.
zxzxzxzxzxzxzxzxzx said:
Update: See the above completed and updated guide.
Click to expand...
Click to collapse
so the way to do it is just flashing the latest detonator?
http://tekhd.com/detonator/
(apparently with full wifi calling support too..)
http://tekhd.com/detonator-o/#vzwdetonator
(or go to detonator telegram channel for possibly modded comunity version...rumor i heard)
implicitly, people probably already know how to root by following the steps outlined from the snapdragon thread..
Hi, Everyone
I'm new to this community. I'm having trouble gaining access to the OEM Bootloader Unlock option in developer options. Here are things I've tried already based on what I researched before my attempt.
Android 10 is the current OS installed after unboxing.
1. Disable Automatic Date and time
2. Select a date more than 7 days prior to current date of attempt.
3. Under Settings > About Phone > Software Information. Select/Tap Build Number 7-8 times to unlock Developer Option.
4. Disable Auto Update System (Apply Updates When Device Restarts) - *This was somehow already disabled the first time I entered Developer options*
5. Under Software Updates > Disable Automatic Updates -*This was also already disabled on unboxing and it says Automatically download updates over Wifi. It does not say Automatic Updates*
6. Reboot device and return to Developer Options after booting to OS.
7. The OEM Bootloader Unlock option should appear greyed out at this point. Toggle it to unlock bootloader with consideration that it will wipe the device data.
These are the steps I've found and tried with no success in gaining access to the Bootloader unlock option. I am also certain that my device is the international model with Exynos chipset and Mali-G72 GPU. Something else to note, I did uncheck many default options to improve privacy on the device before attempting the steps to gain access to the bootloader unlock option. I do not know if that would make a difference. If there is any other information I can provide to get some help with this problem, please add it to your reply. Thanks for any help that comes my way.
Did you get anywhere with this? I'm in the same position, I can't get the OEM unlock option to display despite trying the method described.
More discussion in this thread, but the answer there was to just turn on WiFi which didn't work for me. This thread (much more recent) implies that it's definitely possible on this device, but that's about it.
I've asked a Samsung Support agent and they've told me to submit a bug report, but I'll also try signing in with a Google and Samsung account, and installing all available updates, then trying again.
I recently purchased a used Moto G7 Power (US version) and discovered after flashing Lineage OS that the phone was still locked to T-Mobile. The seller thought he had successfully unlocked it and contacted T-mobile on my behalf since he's still a current customer. They told him to complete the unlock he needed to complete the following command, "Settings > More Connection Settings > Network Unlock > Permanent Unlock" Since I'm currently running LOS on the phone, I no longer have these options.
So it seems like I'd need to flash back to the T-Mobile stock ROM to successfully unlock the phone. Is that correct?
If so, would the following guide accomplish this? I'm not experienced with flashing software so I wanted to get a 2nd opinion before I start mucking around and inadvertently brick the phone.
T-Mobile Motorola G7 Power Firmware | Stock ROM Guide
In this guide, we'll be sharing the easy steps to install the T-Mobile Motorola XT1955-5 (G7 Power) firmware flash file (codenamed Ocean). As an
www.getdroidtips.com
Any guidance is appreciated.
This thread has links to get stock firmware, and a guide to install it:
[GUIDE] Moto G7 Power/Supra [All Versions] Flash Back to Stock Firmware
Broke your G7 Power? No worries! As long as you can still get to fastboot, you can fix it. Note that this WILL wipe all data on the phone! First download the stock firmware for your model here...
forum.xda-developers.com
You probably want the TMO version.
The article has outdated links (404) to the firmware files, but both the article and the XDA thread are linking to the same website.
The XDA thread and the Article are listing slightly different "fastboot" commands, but either guide might work. I haven't tried it.
gemst10 said:
I recently purchased a used Moto G7 Power (US version) and discovered after flashing Lineage OS that the phone was still locked to T-Mobile. The seller thought he had successfully unlocked it and contacted T-mobile on my behalf since he's still a current customer. They told him to complete the unlock he needed to complete the following command, "Settings > More Connection Settings > Network Unlock > Permanent Unlock" Since I'm currently running LOS on the phone, I no longer have these options.
So it seems like I'd need to flash back to the T-Mobile stock ROM to successfully unlock the phone. Is that correct?
If so, would the following guide accomplish this? I'm not experienced with flashing software so I wanted to get a 2nd opinion before I start mucking around and inadvertently brick the phone.
T-Mobile Motorola G7 Power Firmware | Stock ROM Guide
In this guide, we'll be sharing the easy steps to install the T-Mobile Motorola XT1955-5 (G7 Power) firmware flash file (codenamed Ocean). As an
www.getdroidtips.com
Any guidance is appreciated.
Click to expand...
Click to collapse
Hi! I understand what u feel. And now there's a much easier way to restore your Motorola phone without much fear... Just put it in fastboot mode: Hold (Volume down+Power) While the phone is off. Let the software auto detect it... It will download the firmware version of the phone or the lastest one and Flash it for you. in just a few click . Oh you will need to register to the software that's all and it's all free..