Related
I picked up a G9600 and it has a knox enterprise certificate that configures the phone upon initial setup. It is not locked out yet and I can still return it but I’m also trying to figure this weird setup out and possibly clean it up. Rent-A-Center is renting phones that can be remote controlled by them, they supposedly buy them directly from Samsung like this. It’s very interesting!
To remove all of the knox and mdm stuff you have to do this:
Open Samsung Calculator and type in (+30012012732+, this will pop up drp mode, then type in the *#0808#, select DM+Modem+ADB, and hit reboot. You should now have ADB! (you have to do this same method after every reboot)
Once you enable ADB, then you can run these commands to disable knox enrollment center:
"adb shell pm disable-user --user 0 com.sec.knox.kccagent"
"adb shell pm disable-user --user 0 com.planetcellinc.ressvc"
"adb shell pm disable-user --user 0 com.absolute.android.agent"
"adb shell pm disable-user --user 0 com.sec.enterprise.knox.cloudmdm.smdms"
From here you can also now grant SystemUItuner adb permissions to disable animations and modify your status bar/quick settings. FYI, none of this will survive a reset.
Now all I have left to do is figure out how to enable developer options so that I can OEM unlock. I successfully got CROM app to unlock it, I just have no way to access the toggle. After 7 days the prenormal KG Status did go away.
EDIT: I no longer have the phone so I cannot continue digging into this. It worked on all version of Oreo, I never got to try it on Pie.
At Least link the original post dude
M4xh3dr00m said:
At Least link the original post dude
Click to expand...
Click to collapse
The YouTube video I learned it from? Lol or the multiple multiple multiple internet pages that I had to such through for each individual step?
Soure: Google Fu
kekistaneerefugee said:
The YouTube video I learned it from? Lol
Click to expand...
Click to collapse
Anywhere you got it from otherwise you are taking credit for someone else's work
kekistaneerefugee said:
The YouTube video I learned it from? Lol or the multiple multiple multiple internet pages that I had to such through for each individual step?
Soure: Google Fu
Click to expand...
Click to collapse
Well, maybe.
https://forum.xda-developers.com/showpost.php?p=78584395
I post this in January 3rd.
Maybe is not the full set of instructions, then you post the rest and now its a full solution (i think). I dont want credits or whatever, i just want to point you must link the info for reference. Videos, Posts and other stuff. If you post the link to the Youtube Video, can be useful.
The work of recopilation its yours, but the info is for all.
This is a community dude.
M4xh3dr00m said:
Well, maybe.
https://forum.xda-developers.com/showpost.php?p=78584395
I post this in January 3rd.
Maybe is not the full set of instructions, then you post the rest and now its a full solution (i think). I dont want credits or whatever, i just want to point you must link the info for reference. Videos, Posts and other stuff. If you post the link to the Youtube Video, can be useful.
The work of recopilation its yours, but the info is for all.
This is a community dude.
Click to expand...
Click to collapse
Your comment is the only one that I found after using THIS, obtaining ADB, and disabling knox. Yours wasn't complete so I posted a working solution, for the community dude.
If I do this on my Note 9 will I be able to flash a new firmware without being blocked by frp/mdm?
---------- Post added at 09:56 PM ---------- Previous post was at 09:55 PM ----------
*N9600 from Rent A Center.
Nickdroid86 said:
If I do this on my Note 9 will I be able to flash a new firmware without being blocked by frp/mdm?
---------- Post added at 09:56 PM ---------- Previous post was at 09:55 PM ----------
*N9600 from Rent A Center.
Click to expand...
Click to collapse
Like the OP said, this method cant survive a Reset.
Hello, need a little help with a note 9 from RAC. I was able to get into phone by bypassing set up but I'm limited with what I can use do to samsungs knox modified by RAC. I tried the calculator method from this post by I't didnt work because of the limitations I suppose. Is there any way that you can grant root access to an app like file explorer from a PC to remove frp setting so that I can Odin flash an unmodified RAC firmware.
dandel0074 said:
Hello, need a little help with a note 9 from RAC. I was able to get into phone by bypassing set up but I'm limited with what I can use do to samsungs knox modified by RAC. I tried the calculator method from this post by I't didnt work because of the limitations I suppose. Is there any way that you can grant root access to an app like file explorer from a PC to remove frp setting so that I can Odin flash an unmodified RAC firmware.
Click to expand...
Click to collapse
Wrong forums, this is the S9 forum, not the Note 9
https://forum.xda-developers.com/galaxy-note-9
*Detection* said:
Wrong forums, this is the S9 forum, not the Note 9
https://forum.xda-developers.com/galaxy-note-9
Click to expand...
Click to collapse
Yes I kind of got that but I figured it would be the same process and all on how disable samsungs modified by RAC Knox and as it seems to work for me on a temporary disable as listed etc. I know of some apps that need root access can be granted through a PC my question was in how to do that to try and change it through fike explorer. Has it been attempted?
kekistaneerefugee said:
I picked up a G9600 and it has a knox enterprise certificate that configures the phone upon initial setup. It is not locked out yet and I can still return it but I’m also trying to figure this weird setup out and possibly clean it up. Rent-A-Center is renting phones that can be remote controlled by them, they supposedly buy them directly from Samsung like this. It’s very interesting!
To remove all of the knox and mdm stuff you have to do this:
Open Samsung Calculator and type in (+30012012732+, this will pop up drp mode, then type in the *#0808#, select DM+Modem+ADB, and hit reboot. You should now have ADB! (you have to do this same method after every reboot)
Once you enable ADB, then you can run these commands to disable knox enrollment center:
"adb shell pm disable-user --user 0 com.sec.knox.kccagent"
"adb shell pm disable-user --user 0 com.planetcellinc.ressvc"
"adb shell pm disable-user --user 0 com.absolute.android.agent"
"adb shell pm disable-user --user 0 com.sec.enterprise.knox.cloudmdm.smdms"
From here you can also now grant SystemUItuner adb permissions to disable animations and modify your status bar/quick settings. FYI, none of this will survive a reset.
Now all I have left to do is figure out how to enable developer options so that I can OEM unlock.
Click to expand...
Click to collapse
I have a S9+ sm-G9650U variant from R.A.C. ... you can still get to developer options via the apps that shortcut to there in the play store but it's hidden from normal settings area anyway even when enabled also attempting to flash results in "cannot flash MDM mode" message and phone auto reset to the out of box remote set up. also it seems oem unlock is permanent locked (supposedly) via MDM somehow...as I asked this at rent a center and was told at the end of the lease/rental agreement MDM is removed and oem unlock will be enabled so idk if it can be done without MDM issuing it... also attached is the app i use to access developer options.
dandel0074 said:
Yes I kind of got that but I figured it would be the same process and all on how disable samsungs modified by RAC Knox and as it seems to work for me on a temporary disable as listed etc. I know of some apps that need root access can be granted through a PC my question was in how to do that to try and change it through fike explorer. Has it been attempted?
Click to expand...
Click to collapse
There should be no difference between the S9 and Note 9, I only had access to the S9 for testing. I doubt the Android Pie update still allows this, I got rid of the phone before that came out but I was on latest Oreo update with it still working.
Yes
kekistaneerefugee said:
I picked up a G9600 and it has a knox enterprise certificate that configures the phone upon initial setup. It is not locked out yet and I can still return it but I’m also trying to figure this weird setup out and possibly clean it up. Rent-A-Center is renting phones that can be remote controlled by them, they supposedly buy them directly from Samsung like this. It’s very interesting!
To remove all of the knox and mdm stuff you have to do this:
Open Samsung Calculator and type in (+30012012732+, this will pop up drp mode, then type in the *#0808#, select DM+Modem+ADB, and hit reboot. You should now have ADB! (you have to do this same method after every reboot)
Once you enable ADB, then you can run these commands to disable knox enrollment center:
"adb shell pm disable-user --user 0 com.sec.knox.kccagent"
"adb shell pm disable-user --user 0 com.planetcellinc.ressvc"
"adb shell pm disable-user --user 0 com.absolute.android.agent"
"adb shell pm disable-user --user 0 com.sec.enterprise.knox.cloudmdm.smdms"
From here you can also now grant SystemUItuner adb permissions to disable animations and modify your status bar/quick settings. FYI, none of this will survive a reset.
Now all I have left to do is figure out how to enable developer options so that I can OEM unlock. I successfully got CROM app to unlock it, I just have no way to access the toggle. After 7 days the prenormal KG Status did go away.
EDIT: I no longer have the phone so I cannot continue digging into this. It worked on all version of Oreo, I never got to try it on Pie.
Click to expand...
Click to collapse
thanks bro it worked but it's not permanent solution.
By the way thanks for your contribution
You're the only guy helping with this problem. Full solution isn't allowed to be discussed here. Thank you very much for contribution despite the irrelevant comments.
mattfirey said:
You're the only guy helping with this problem. Full solution isn't allowed to be discussed here. Thank you very much for contribution despite the irrelevant comments.
Click to expand...
Click to collapse
Yeah, XDA mods are bad. The full solution seems to be the better solution in the long run anyway. I hope anyone who actually needs to use this goes the full solution route.
I tried something simulre back several months ago when I first picked up an unlocked S9 from Amazon from a 3rd party seller, was never able to get it bypassed, and even If I did didnt trust it. I ended up calling the number which was a local store number, they looked up the imei and it was reported stolen. So back to the seller it went.
If you trip knox on purpose it goes away perm. First to get rid of the problem of not being able to wipe it you have to get combo firmware use Odin to flash it in but be sure to check nand erase all on options tab and boom it's now able to be wiped. For a lot of units you're done just flash full firmware. However on some devices you have to extract the boot.img.lz4 from the ap file from full firmware file (not combo) then use 7zip to extract boot.img from boot.img.lz4 now copy the boot.img to a device that has magisk manager running on it. Tap install magisk select boot.img it creates a patched boot.img in your downloads folder. Copy back to PC use 7zip to put boot.img into a tar. Put device in download mode flash new tar it in you will see an error about knox. Put back in download mode confirm knox is tripped (samsung pay and other knox stuff won't work) flash full firmware. The notice about reenrollment will pop up but once u connect to wifi itll just go through normal setup because it's no longer "fit" for knox enrollment. Boom. Any questions let me know.
kekistaneerefugee said:
I picked up a G9600 and it has a knox enterprise certificate that configures the phone upon initial setup. It is not locked out yet and I can still return it but I’m also trying to figure this weird setup out and possibly clean it up. Rent-A-Center is renting phones that can be remote controlled by them, they supposedly buy them directly from Samsung like this. It’s very interesting!
To remove all of the knox and mdm stuff you have to do this:
Open Samsung Calculator and type in (+30012012732+, this will pop up drp mode, then type in the *#0808#, select DM+Modem+ADB, and hit reboot. You should now have ADB! (you have to do this same method after every reboot)
Once you enable ADB, then you can run these commands to disable knox enrollment center:
"adb shell pm disable-user --user 0 com.sec.knox.kccagent"
"adb shell pm disable-user --user 0 com.planetcellinc.ressvc"
"adb shell pm disable-user --user 0 com.absolute.android.agent"
"adb shell pm disable-user --user 0 com.sec.enterprise.knox.cloudmdm.smdms"
From here you can also now grant SystemUItuner adb permissions to disable animations and modify your status bar/quick settings. FYI, none of this will survive a reset.
Now all I have left to do is figure out how to enable developer options so that I can OEM unlock. I successfully got CROM app to unlock it, I just have no way to access the toggle. After 7 days the prenormal KG Status did go away.
EDIT: I no longer have the phone so I cannot continue digging into this. It worked on all version of Oreo, I never got to try it on Pie.
Click to expand...
Click to collapse
After you do the above, you'll be able to uninstall "com.absolute.android.agent", "com.sec.knox.kccagent", and "com.planetcellinc.ressvc" from within Settings > Apps.
Then you can go into Settings > Developer Settings > OEM Unlock
***I don't think this step matters, but I did it anyway just to be sure***
Go back to adb use the "adb shell pm disable-user --user 0 <package name>" command on everything that has the word "knox" and "enterprise" in the package name.
Then power off the device.
Hold Bixby + Volume Down while you connect phone to the computer.
This will bring you to download mode. You'll see 3 options:
Volume Up for Download mode
Volume Up for 7 seconds for Bootloader Unlock
Volume Down and Power for Cancel/Restart Phone
Choose the Bootloader Unlock option
Your phone will factory reset, but I guess since it unlocks the bootloader, it factory resets the phone to stock samsung firmware and not the rent a center controlled firmware..
You'll go through the initial setup but it will skip the rent a center knox configure step and go right into the phone as normal.
When it loads, go back to Developer Settings, double check to see that OEM Unlock is on AND grayed out, rather than OEM Unlock being off and grayed out.
This will remove all Rent A Center phone control, but I'd assume they could still blacklist your IMEI number.
Hey everybody.
I've been testing this but I can't select DM+Modem+ADB because I don't have that option.
I have RMNET+DM+MODEM+ADPL
I installed some adb drivers with that option but I get no response from adb devices and can't continue with commands.
Any tip is appreciated.
I have a Note 9 with Verizon that has Oreo 8.1.0 on it. I have been trying to avoid downloading the Pie update. I had developer options on and auto updates were turned off, yet the update still got downloaded. How can I delete the downloaded software and stop these the installation reminders? It says I can delay the update only 8 more times before it automatically installs it My phone is not rooted and I don't know the first thing about rooting a phone. Any help would be appreciated!
I dont think you can permanently stop it without running some adb command. Too my knowledge there is no root currently available for the Snapdragon version of the Note 9.
Other users on here might know the adb command to run though but I'm not knowledgable on it.
*Hooligan* said:
I dont think you can permanently stop it without running some adb command. Too my knowledge there is no root currently available for the Snapdragon version of the Note 9.
Other users on here might know the adb command to run though but I'm not knowledgable on it.
Click to expand...
Click to collapse
Thank you for replying. I hope someone knows something.
Try using package disabler pro to disable the update services. Might work.
popeye0777 said:
I have a Note 9 with Verizon that has Oreo 8.1.0 on it. I have been trying to avoid downloading the Pie update. I had developer options on and auto updates were turned off, yet the update still got downloaded. How can I delete the downloaded software and stop these the installation reminders? It says I can delay the update only 8 more times before it automatically installs it My phone is not rooted and I don't know the first thing about rooting a phone. Any help would be appreciated!
Click to expand...
Click to collapse
is your update of from settings aswell ? Adhell 3 you can disable updates from there!
N1NJATH3ORY said:
is your update of from settings aswell ? Adhell 3 you can disable updates from there!
Click to expand...
Click to collapse
Yes, it is disabled from there as well which is the weird part. It still downloaded the update.
Nwpayton said:
Try using package disabler pro to disable the update services. Might work.
Click to expand...
Click to collapse
I'm trying that now hopefully my next scheduled installation reminder doesn't pop up.
popeye0777 said:
Yes, it is disabled from there as well which is the weird part. It still downloaded the update.
Click to expand...
Click to collapse
What you can do is hard reset your phone! Make sure you back up everything first that way the update will get wiped off your phone! Also when you re set it up, do not connect to network! Make sure NO Wi-FI NO Sim! Once your at home screen! Disable all auto updates from settings and dev options then install Adhell 3 disable all update packages and you will be fine!
quote "Adhell 3 can easily block any package plus it has the added benefit of system wide ad-blocking. Use this guide to setup: https://forum.xda-developers.com/gal...tance-t3873831 (its post 3 or 4 I think that has the instructions). Enjoy!" Not mine--> He posted this another thread! @mtweisenbarger777
Yes that would work too^ I'm just blocking the services and seem to have done the job for me so far as I had that same concern as I just downgraded from pie and don't want to accidently update again
I stopped the updates by going to the Note 9 U1 XAA firmware. No Verizon branding. No VZW updates.
popeye0777 said:
I'm trying that now hopefully my next scheduled installation reminder doesn't pop up.
Click to expand...
Click to collapse
Nwpayton said:
Try using package disabler pro to disable the update services. Might work.
Click to expand...
Click to collapse
Thanks again for the suggestion. The package disabler seems to have done the trick.
popeye0777 said:
Thanks again for the suggestion. The package disabler seems to have done the trick.
Click to expand...
Click to collapse
Glad to help
I to can confirm PDM the Version from the dev's direct download works. I disabled 3 apps after searching within the app "update"
Photo's[emoji2398] by Sully using SM-N960U or SM-870A
Package disabler apps must be purchased? But why not just disable with adb? (it's built in to your Note9 and free)
https://android.stackexchange.com/questions/176727/stop-galaxy-s7-upgrade-nag-screen/176739#176739
I just did this, so we'll see if this works over the next few days and doesn't break anything else:
adb shell
to find packages:
pm list packages | grep soagent
pm list packages | grep wssyncmldm
to disable:
pm disable-user --user 0 com.sec.android.soagent
pm disable-user --user 0 com.wssyncmldm
enable later:
pm enable-user --user 0 com.sec.android.soagent
pm enable-user --user 0 com.wssyncmldm
gruuvin said:
Package disabler apps must be purchased? But why not just disable with adb? (it's built in to your Note9 and free)
https://android.stackexchange.com/questions/176727/stop-galaxy-s7-upgrade-nag-screen/176739#176739
I just did this, so we'll see if this works over the next few days and doesn't break anything else:
adb shell
to find packages:
pm list packages | grep soagent
pm list packages | grep wssyncmldm
to disable:
pm disable-user --user 0 com.sec.android.soagent
pm disable-user --user 0 com.wssyncmldm
enable later:
pm enable-user --user 0 com.sec.android.soagent
pm enable-user --user 0 com.wssyncmldm
Click to expand...
Click to collapse
I cannot figure out how to get to the place where I can perform ADB commands.
Directions say to select PTP mode, but I do not have that as a choice in the status bar, when I connect my Note 9 on Oreo to Windows 10 laptop. I think that is why no commands work in the Powershell as administrator window, opened in the Platform Tools folder.
Do I start in Recovery or Download Mode?
I also read that ADB commands can be performed in ODIN, but I don't see where to type.
In Power Shell for Fastboot I receive the following error, when entering "adb devices"
adb : The term 'adb' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ adb devices
+ ~~~
+ CategoryInfo : ObjectNotFound: (adb:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Click to expand...
Click to collapse
pizza_pablo said:
I cannot figure out how to get to the place where I can perform ADB commands.
Directions say to select PTP mode, but I do not have that as a choice in the status bar, when I connect my Note 9 on Oreo to Windows 10 laptop. I think that is why no commands work in the Powershell as administrator window, opened in the Platform Tools folder.
Do I start in Recovery or Download Mode?
I also read that ADB commands can be performed in ODIN, but I don't see where to type.
In Power Shell for Fastboot I receive the following error, when entering "adb devices"
Click to expand...
Click to collapse
1. Use cmd not powershell
2. Use. "Cd c:/your folders/folder-where-adb.exe-is" and replace the filepath with the filepath that leads to where your ADB.exe file is. Most likely in platform tools folder.
3. Go Into developer settings, enable USB debugging.
4. Plug phone into computer using file transfer mode, check your phone and allow your phone to "trust" your PC Always when the box comes up.
5. Now type ADB shell into the cmd prompt and you should get a $: instead of C: on the blinking line. Now you can execute PM Commands
Bober_is_a_troll said:
1. Use cmd not powershell
2. Use. "Cd c:/your folders/folder-where-adb.exe-is" and replace the filepath with the filepath that leads to where your ADB.exe file is. Most likely in platform tools folder.
3. Go Into developer settings, enable USB debugging.
4. Plug phone into computer using file transfer mode, check your phone and allow your phone to "trust" your PC Always when the box comes up.
5. Now type ADB shell into the cmd prompt and you should get a $: instead of C: on the blinking line. Now you can execute PM Commands
Click to expand...
Click to collapse
Placing the 'Cd" in front of the folder address in CMD Prompt worked like magic.
I've been butting my head against the wall for a few hours.
Thank you for responding with a great tip! :good:
---------- Post added at 08:18 PM ---------- Previous post was at 07:42 PM ----------
Bober_is_a_troll said:
1. Use cmd not powershell
2. Use. "Cd c:/your folders/folder-where-adb.exe-is" and replace the filepath with the filepath that leads to where your ADB.exe file is. Most likely in platform tools folder.
3. Go Into developer settings, enable USB debugging.
4. Plug phone into computer using file transfer mode, check your phone and allow your phone to "trust" your PC Always when the box comes up.
5. Now type ADB shell into the cmd prompt and you should get a $: instead of C: on the blinking line. Now you can execute PM Commands
Click to expand...
Click to collapse
As you can see from the attached screenshot, ADB could not find the wssyncmldm app, but CCSWE App Manager listed the OS update apps as shown at the bottom of the screenshot and I was able to disable those.
View attachment 4836423
Am I set to prevent OS updates and stay on Oreo or did I do a bad thing?
Apologies, for the small pic in the post above!
Here a phone screen shot showing disabled apps.
The software update all with the green icon is still enabled.
pizza_pablo said:
Placing the 'Cd" in front of the folder address in CMD Prompt worked like magic.
I've been butting my head against the wall for a few hours.
Thank you for responding with a great tip! :good:
---------- Post added at 08:18 PM ---------- Previous post was at 07:42 PM ----------
As you can see from the attached screenshot, ADB could not find the wssyncmldm app, but CCSWE App Manager listed the OS update apps as shown at the bottom of the screenshot and I was able to disable those.
View attachment 4836423
Am I set to prevent OS updates and stay on Oreo or did I do a bad thing?
Click to expand...
Click to collapse
Some apps are not installed under --user 0, and instead are system apps. Try removing --user 0 and see if to uninstalls.
Note: I've only tried this on Oppo Find X2 Lite running Color OS 11.1 (Android 11), and I'm not responsible if you screw up something.
Note: you don't have to revert before every monthly update. But just to be safe, revert back before a major software update (like the Android 12 update).
This method doesn't require root nor a custom recovery. it's simple and you can revert back if you wish.
The reason why we can't get the Google Discover Feed on the home screen is because of Oppo's Smart Assistant app. So we'll be uninstalling it (kinda, see Note 2 at the end of the post), as soon as that's done, you'll get the Discover feed on the left page of your home screen (of course you'll need to have the Google app installed). If you would like to get Smart Assistant back, follow the steps in the To Revert back section.
By the way, if you don't want to bother with Command prompt, you can always just use a custom launcher like Lawnchair, that will give you the ability to use Google Discover without any ADB commands. If you want the safest route, go with this.
Steps:
1- Enable Developer Options (by going to Settings>About Phone>Version then clicking Build Number a bunch of times).
2- On your PC, download Platform Tools from this link: https://developer.android.com/studio/releases/platform-tools .
3- Extract the zip file to a folder.
4- Copy the path to that folder, then open open Command Prompt as an administrator and type "cd (the path you copied)" (example: cd C:/platform-tools ).
5- Enable ADB Debugging (by going to Settings>Additional Settings>Developer options then enable USB debugging).
6- Plug your phone to your PC, then change the connection method on your phone to "Transfer Files / Android Auto".
7- A pop-up saying " Allow USB debugging? " will appear, click Allow.
8- On your the command prompt window on your PC, type "adb devices" , you should see: "[your serial number] device".
9- Now type
Code:
adb shell pm uninstall -k --user 0 com.coloros.assistantscreen
and hit enter, wait for it to finish.
10- Reboot your phone, you should see the Discover Feed on the the left screen. Enjoy !
To Revert back:
If you want to bring back Smart Assistant, repeat steps 4 through 8, then type in command prompt
Code:
adb shell cmd package install-existing com.coloros.assistantscreen
Notes:
- After you're done, I recommend going back to Settings>Additional Settings>Developer options and disabling USB Debugging.
- The command doesn't actually delete the app from the phone, it just removes it for the main user, i.e. you.
- the monthly system updates don't bring back Smart Assistant, but I'd recommend reverting back before updating to Android 12 (if we're getting it ).
Full credit goes to @klanbo78 for this, thank you so much !
Thanks for the guide!
Have you been able to test it out on ColorOS 12?
zonzo3 said:
Thanks for the guide!
Have you been able to test it out on ColorOS 12?
Click to expand...
Click to collapse
I still didn't receive the ColorOS 12 update on my device. Although I can confirm that this still works in the ColorOS 11.1 March 2022 update.
Have you managed to receive the ColorOS 12 update on this device? if so, would you mind mentioning from which country?
NOTE - THIS GUIDE IS ONLY FOR THE REALME GT NEO 2T (RMX3357)
For the X7 Max or GT Neo/GT Neo Flash Edition, please refer to the excellent guide by @mahotlov found here.
(The X7 Max subforum seemed the best place for this guide, but please let me know if there's a better place!)
------------------------------------------------------------------------------------------------------------------Preamble: I recently purchased a Realme GT Neo 2T under the assumption it could take Realme X7 Max ROMs. The specs and design were an exact match, and since Realme has a history of releasing existing phones with new model numbers and sparklier plastic, I felt pretty good about compatibility. I quickly learned I was mistaken - both stock and custom ROMs for the X7 Max cause the display on the Neo 2T to stop working. Flashing back the stock bootloader fixed the display, but the phone would only boot into recovery, which had no touch support. Flashing the stock recovery brought back touch support, but nothing I tried could get the ROM to boot. Clearly there are changes under the hood.
Unfortunately, that left precious few options for turning the Neo 2T into a usable phone. The hardware is amazing for the price, and ColorOS is pretty decent, but the amount of non-removable bloatware and lack of Android Auto and Hey Google to activate Google Assistant was a dealbreaker for me. In the end, I decided to take matters into my own hands.
------------------------------------------------------------------------------------------------------------------
This guide will show you how to:
- Unlock your bootloader.
- Root your phone. (Magisk)
- Bypass SafetyNet. (Universal SafetyNet Fix Magisk module)
- Install Android Auto and Google apps as system apps. (BusyBox-NDK and Terminal Systemizer Magisk modules)
- Remove Realme bloatware. (ADB)
- Flash device with SP Tools and stock ROM to recover from a softbrick or restore to factory state. (SP Tools)
(Some sections are still being written and will be available soon.)
------------------------------------------------------------------------------------------------------------------
THE GUIDE ASSUMES YOU ARE USING WINDOWS 10. SOME STEPS MAY BE DIFFERENT FOR OTHER OPERATING SYSTEMS
PLEASE READ THROUGH ALL INSTRUCTIONS FIRST BEFORE PROCEEDING. ALL REQUIRED FILES CAN BE FOUND ATTACHED TO THIS POST.
UNLOCKING YOUR BOOTLOADER WILL VOID YOUR WARRANTY. THIS PROCESS WILL WIPE ALL DATA FROM YOUR PHONE. I AM NOT RESPONSIBLE FOR LOST DATA. I AM ALSO NOT RESPONSIBLE IF YOU DAMAGE OR KILL YOUR DEVICE, YOUR PROPERTY, YOUR LOVED ONES OR YOURSELF BY FOLLOWING THESE INSTRUCTIONS. YOU HAVE BEEN WARNED!
------------------------------------------------------------------------------------------------------------------
STEP 1: Unlock your bootloader.
Spoiler: Click here for instructions.
First, we need to enable developer mode. On the Neo 2T:
- Open Settings.
- Choose "About Phone".
- Choose "Version - Baseband & Kernel"
- Tap "Build Number" until developer mode is enabled.
Next, we need to turn on USB Debugging and allow OEM Unlock. On the Neo 2T:
- Go back to Settings.
- Choose "Additional Settings".
- Choose "Developer Options".
- Turn on "OEM Unlock" and "USB Debugging".
We need to get the Deep Testing app to unlock the bootloader. On your PC:
- Download "DeepTesting_GT_NEO_2T.apk" attached to this post.
- Plug the Neo 2T into your PC.
Now, we need to allow file transfers. On the Neo 2T:
- Select "Transfer Files" on the "Use USB to" popup.
Time to send the .apk to the Neo 2T. On your PC:
- Copy the "DeepTesting_GT_NEO_2T.apk" file you downloaded to the "Download" folder on the internal storage of the Neo 2T.
We're ready to request unlocking of the bootloader. On the Neo 2T:
- Open the "File Manager" app.
- Choose the "APK" option.
- Find "DeepTesting_GT_NEO_2T.apk" and open it.
- Follow the instruction to install the app. You may need to allow installing from the "File Manager" app.
- Once install is finished, launch the app.
- Click "Start Applying".
- Tick the checkbox to agree to the disclaimer. Due to a bug, the disclaimer text itself may or may not appear.
- When you see "Application Submitted", click "Back."
- Go grab a coffee. It can sometimes take up to an hour for the bootloader unlock request to be approved.
- You can close the app and use your phone as normal in the meantime. Periodically open the app and click "Query Verification Status" to check your request. Once you see "Application Approved" we are done with this step.
- Unplug the Neo 2T from your PC.
- Click "Start Deep Testing".
- The Neo 2T will reboot into "Fastboot" mode. You should see a black screen with small white text.
- Plug the Neo 2T into your PC.
Now we need to install the ADB drivers. On your PC:
- Download "ADB_DRIVERS.zip" attached to this post.
- Unzip the files somewhere. Remember the location.
- Right-click on your start menu button and choose "Device Manager".
- Find the device called "Android".
- Right-click the device and choose "Update Driver".
- Choose "Browse My Computer for Drivers".
- Choose "Let Me Pick From a List of Available Drivers On My Computer".
- Click "Have Disk".
- Click "Browse".
- Navigate to the folder where you extracted the files.
- Choose "android_winusb.inf".
- Choose "Android Bootloader Interface".
- Click "Finish" to close the driver wizard once it has finished.
We need to use Fastboot to unlock the bootloader. On your PC:
- Download "ADB_FASTBOOT.zip" attached to this post.
- Unzip the files somewhere. Remember the location.
- Open a command prompt pointing to the extracted files. (The fastest way to do this is to open the folder, then replace the file path with "cmd" end hit enter.)
- Enter this command to check that your phone is detected: fastboot.exe devices
- You should see your device represented by a long string of numbers and letters followed by "fastboot".
- If you don't see this, or it doesn't say "fastboot", double-check your USB cable or port, and make sure you installed the drivers as instructed previously.
- Enter this command: fastboot.exe flashing unlock
Your phone will now ask you to confirm unlocking of the bootloader. On the Neo 2T:
- REMINDER: THIS WILL WIPE ALL YOUR DATA!
- Read the text on the screen and follow the instructions to confirm the bootloader unlock.
Next we reboot the phone. On your PC:
- Enter this command: fastboot.exe reboot
- Your phone will now warn you during boot that the bootloader is unlocked.
- Unplug the Neo 2T from your PC.
Now we need to enter Fastboot again. On the Neo 2T:
- Allow the phone to fully boot to the initial setup wizard.
- Turn off the phone by holding down the power button until the power actions slider appears.
- Slide down to turn off the phone.
- While holding down Vol-, press and hold the power button.
- Release the power button when you feel the phone vibrate.
- Release the Vol- button when you have entered Fastboot mode. You should see a black screen with small white text.
- Plug the Neo 2T into your PC.
We will use Fastboot to get into recovery mode. On your PC:
- Open the folder where you extracted the "ADB_FASTBOOT.zip" (Done previously during Step 1: Unlock your bootloader.)
- Open a command prompt pointing to the extracted files. (The fastest way to do this is to open the folder, then replace the file path with "cmd" end hit enter.)
- Enter this command to check that your phone is detected: fastboot.exe devices
- You should see your device represented by a long string of numbers and letters followed by "fastboot".
- If you don't see this, or it doesn't say "fastboot", double-check your USB cable or port, and make sure you installed the drivers as instructed previously.
- Enter this command: fastboot.exe reboot recovery
- Wait for phone to reboot into recovery
Finally, we will wipe the data partition to ensure a clean state for future steps. On the Neo 2T:
- Select your language.
- Select "Wipe data".
- Select "Format data".
- Enter the code displayed on the screen.
- Select "Format".
- Data will be wiped. Select "OK" when finished. Phone will reboot.
- Once the phone has booted, proceed through the first time setup until you reach the home screen.
- Setup WiFi or verify/configure a data connection which will be needed for the next steps.
- If still plugged into your PC, or upon the next connection, the phone will show a popup to allow USB debugging. Check "always allow from this computer" and select OK.
- We can now move on to rooting!
STEP 2: Root your phone.
Spoiler: Click here for instructions.
First we need to reboot the phone into fastboot. On the Neo 2T:
- Unplug the Neo 2T from your PC.
- Turn off the phone by holding down the power button until the power actions slider appears.
- Slide down to turn off the phone.
- While holding down Vol-, press and hold the power button.
- Release the power button when you feel the phone vibrate.
- Release the Vol- button when you have entered Fastboot mode. You should see a black screen with small white text.
- Plug the Neo 2T into your PC.
We need to use Fastboot to root the phone. On your PC:
- Open the folder where you extracted the "ADB_FASTBOOT.zip" (Done previously during Step 1: Unlock your bootloader.)
- Open a command prompt pointing to the extracted files. (The fastest way to do this is to open the folder, then replace the file path with "cmd" end hit enter.)
- Enter this command to check that your phone is detected: fastboot.exe devices
- You should see your device represented by a long string of numbers and letters followed by "fastboot".
- If you don't see this, or it doesn't say "fastboot", double-check your USB cable or port, and make sure you installed the drivers as instructed previously.
- Enter this command: fastboot.exe flash boot magisk.img
- Enter this command: fastboot.exe flash vbmeta --disable-verity --disable-verification vbmeta.img
- Enter this command: fastboot.exe reboot
- Wait for phone to reboot.
Complete Magisk setup. On the Neo 2T:
- Open Magisk from your app drawer.
- Accept the request to install the full version of Magisk.
- Allow Magisk to install apps in the resulting popup.
- Open Magisk from your app drawer.
- Accept the request to reboot to complete installation.
- Once the phone has rebooted, the process is complete and we can move on to bypassing SafetyNet!
STEP 3: Bypass SafetyNet.
Spoiler: Click here for instructions.
First we grab the SafetyNet module for Magisk. On your PC:
- Download "safetynet-fix-v2.2.1.zip" attached to this post.
- Plug the Neo 2T into your PC.
Now, we need to allow file transfers. On the Neo 2T:
- Select "Transfer Files" on the "Use USB to" popup.
Time to send the .apk to the Neo 2T. On your PC:
- Copy the "safetynet-fix-v2.2.1.zip" file you downloaded to the "Download" folder on the internal storage of the Neo 2T.
We're ready to install the module. On the Neo 2T:
- Open the "Magisk" app.
- Open Settings.
- Turn on "Zygist (Beta)" and "Enforce DenyList".
- Exit settings.
- Go to the "Modules" tab.
- Select "Install From Storage".
- Find "safetynet-fix-v2.2.1.zip" and open it.
- Wait until installation of the module is complete.
- Click the "Reboot" button that appears to reboot the phone.
- Once the phone has rebooted, the process is complete and we can move on to installing Android Auto and Google apps as system apps!
STEP 4: Install Android Auto and and Google apps as system apps.
Spoiler: Click here for instructions.
First we grab the BusyBox-NDK and Terminal Systemizer modules for Magisk. On your PC:
- Download "busybox-v1.34.1.zip" attached to this post.
- Download "terminal_systemizer_v17.4.1.zip" attached to this post.
- Plug the Neo 2T into your PC.
Now, we need to allow file transfers. On the Neo 2T:
- Select "Transfer Files" on the "Use USB to" popup.
Time to send the .apks to the Neo 2T. On your PC:
- Copy the "busybox-v1.34.1.zip" file you downloaded to the "Download" folder on the internal storage of the Neo 2T.
- Copy the "terminal_systemizer_v17.4.1.zip" file you downloaded to the "Download" folder on the internal storage of the Neo 2T.
We're ready to install the BusyBox-NDK module. On the Neo 2T:
- Open the "Magisk" app.
- Go to the "Modules" tab.
- Select "Install From Storage".
- Find "busybox-v1.34.1.zip" and open it.
- Wait until installation of the module is complete.
- Click the back button.
We're ready to install the Terminal Systemizer module. On the Neo 2T:
- Go to the "Modules" tab.
- Select "Install From Storage".
- Find "terminal_systemizer_v17.4.1.zip" and open it.
- Wait until installation of the module is complete.
- Click the "Reboot" button to reboot the phone.
Time to get the Google Play Store app. On your PC:
- Download "Google_Play_Store_29.9.16-21.apk" attached to this post.
- Plug the Neo 2T into your PC.
Now, we need to allow file transfers. On the Neo 2T:
- Select "Transfer Files" on the "Use USB to" popup.
Time to send the .apk to the Neo 2T. On your PC:
- Copy the "Google_Play_Store_29.9.16-21.apk" file you downloaded to the "Download" folder on the internal storage of the Neo 2T.
We're ready to install the Google Play Store. On the Neo 2T:
- Open the "Files" app.
- Choose the "APK" option.
- Find "Google_Play_Store_29.9.16-21.apk" and open it.
- Follow the instruction to install the app. You may need to allow installing from the "File Manager" app.
- Once install is finished, launch the app.
We need to install our apps before we can systemize them. On the Neo 2T:
- Open the Google Play Store and sign in.
- Update any apps that have updates available.
- Use the Google Play Store to install Android Auto, Google Assistant, and the Google app.
We need to use ADB to systemize Android Auto and Google Assistant. On your PC:
- Open the folder where you extracted the "ADB_FASTBOOT.zip" (Done previously during Step 1: Unlock your bootloader.)
- Open a command prompt pointing to the extracted files. (The fastest way to do this is to open the folder, then replace the file path with "cmd" end hit enter.)
- Enter this command to check that your phone is detected: adb.exe devices
- You should see your device represented by a long string of numbers and letters followed by "device".
- If you don't see this, or it doesn't say "device", double-check your USB cable or port, and make sure you installed the drivers as instructed previously.
- Enter this command: adb shell
- Have your phone unlocked and at the ready, then enter this command: su
Allow root for ADB Shell. On the Neo 2T:
- Select "Forever" on the superuser request popup for Shell. Click "Grant".
Now we can systemize Android Auto and Google. On your PC:
- Enter this command: systemize
- Type 1 and hit enter to choose "Systemize Installed Apps (Listed)".
- You should see a numbered list of apps after a few seconds of loading. Find the numbers for "Android Auto" and "Google" and type them with a space in between. For example, if you see "1 - Android Auto" and "2 - Google", type 1 2 followed by enter.
- Type 2 and hit enter to choose "/system/priv-app" for the first app.
- Type 2 and hit enter to choose "/system/priv-app" for the second app.
Reboot the phone. On the Neo 2T:
- Hold down the power button until the power actions slider appears.
- Slide up to reboot the phone.
- Once rebooted, Android Auto will soon disappear from your app launcher now that is a system app. This is by design.
- Use the Google Play Store to install "Android Auto for Phone Screens".
- Open the "Android Auto for Phone Screens" app. Complete all setup steps.
- Open the "Android Assistant" app. Complete all setup steps.
- Open the "Google" app. Go to More > Settings > Google Assistant > Hey Google & Voice Match.
- Turn on "Hey Google". Complete all setup steps.
- In the Google Assistant settings in the Google app, you should now be able to turn on "Hey Google" voice activation.
- Hold down the power button until the power actions slider appears.
- Slide up to reboot the phone.
- Upon reboot, Android Auto should now work both on the phone and with Android Auto compatible vehicles head units.
- Hey Google should now work as long as the screen is on.
- Time for debloating!
STEP 5: Remove Realme bloatware.
Spoiler: Click here for instructions.
First we need to install an alternative input method, since we will be removing the stock keyboard. On the Neo 2T:
- Use the Google Play Store to install an input method of your choice, such as GBoard.
Now we can run the debloat script. On your PC:
- Plug the Neo 2T into your PC if it is not already.
- Open the folder where you extracted the "ADB_FASTBOOT.zip" (Done previously during Step 1: Unlock your bootloader.)
- Double-click the RMX3357_A14_DEBLOAT_NO_ROOT.bat file to run the non-root debloat script.
- Press Enter to run the script.
- Close the window or press Enter to exit once finished.
We need to use ADB to remove a few system apps. On your PC:
- Open the folder where you extracted the "ADB_FASTBOOT.zip" (Done previously during Step 1: Unlock your bootloader.)
- Open a command prompt pointing to the extracted files. (The fastest way to do this is to open the folder, then replace the file path with "cmd" end hit enter.)
- Enter this command to check that your phone is detected: adb.exe devices
- You should see your device represented by a long string of numbers and letters followed by "device".
- If you don't see this, or it doesn't say "device", double-check your USB cable or port, and make sure you installed the drivers as instructed previously.
- Enter this command: adb shell
- Enter this command: su
- Enter this command: pm uninstall --user 0 com.android.email
- Enter this command: pm uninstall --user 0 com.coloros.safecenter
- Enter this command: pm uninstall --user 0 com.heytap.book
- Enter this command: pm uninstall --user 0 com.heytap.market
- Enter this command: pm uninstall --user 0 com.heytap.themestore
- Enter this command: pm uninstall --user 0 com.nearme.gamecenter
Reboot the phone. On the Neo 2T:
- Hold down the power button until the power actions slider appears.
- Slide up to reboot the phone.
- You're done! Enjoy your debloated phone!
UH OH: Unbricking and Factory Restore.
Spoiler: Click here for instructions.
Click here for the ROM, use SP tools to flash. Guide coming soon, for now use the guide here.
------------------------------------------------------------------------------------------------------------------Realme GT Neo 2T Tips:
- If you find yourself needing to force your phone to power off for any reason, on the Neo 2T you must hold Vol+, Vol- and Power at the same time for around 10 seconds.
- The stock messaging app is com.android.mms, otherwise known as Mms.apk. It seemingly cannot be removed without breaking SMS/MMS.
- Removing Breeno will replace it with Google Feed when swiping left on the stock launcher fi the Google app is installed.
- There's a good chance the APN settings the phone chose are incorrect or nonexistent. Double-check them to make sure you have working data and MMS for your SIMs.
- Android Auto forces the phone to 60Hz and locks the settings, even once disconnected. Seems to be a common issue across a bunch of phones. Reboot to fix.
- If an app isn't showing notifications or is otherwise misbehaving:
>>> Make sure the app has been opened at least once since the phone was last powered on or rebooted.
>>> Check that notifications are enabled in Settings > Notifications & Status Bar > Manage Notifications > [Your App].
>>> If that doesn't help, try allowing background activity in Settings > Battery > App Battery Management > [Your App].
>>> Lastly, you can disable battery optimization for an app in Settings > Battery > More Battery Settings > Optimize Battery Use > [Your App].
------------------------------------------------------------------------------------------------------------------
Spoiler: SOURCES
Guide by @mahotlov I shamelessly stole bits from: https://forum.xda-developers.com/t/x7-max-and-gt-neo-flash-ubrick-instructions.4337339/
Magisk: https://github.com/topjohnwu/Magisk
SafetyNet-Fix: https://github.com/kdrag0n/safetynet-fix
BusyBox NDK: https://github.com/Magisk-Modules-Repo/busybox-ndk
Terminal Systemizer: https://github.com/Magisk-Modules-Repo/terminal_systemizer
Reserved #1.
Hi, thanks for topic!
Have any room stock global? Need with language Portuguese of Brazil, i'm using the app MoreLocale to change, but this is not automatic
J_Eudes said:
Hi, thanks for topic!
Have any room stock global? Need with language Portuguese of Brazil, i'm using the app MoreLocale to change, but this is not automatic
Click to expand...
Click to collapse
Unfortunately there is no global ROM for the GT Neo 2T, I specifically asked Realme and they said they have no plans to release one.
Hi @MatinatorX, can you help to extract framework-res.apk and settings.apk? I would like to explore the possibility of decompiling those apk and adding languages. thank you!
dewidoj461 said:
Hi @MatinatorX, can you help to extract framework-res.apk and settings.apk? I would like to explore the possibility of decompiling those apk and adding languages. thank you!
Click to expand...
Click to collapse
Sure, here you go.
Hey, Is there a notification solution? to come from everyone?
AngelXTR91 said:
Hey, Is there a notification solution? to come from everyone?
Click to expand...
Click to collapse
Haven't had any issues with notifications myself. I'd check these:
- Make sure the app has been opened at least once since the phone was last powered on or rebooted.
- Check that notifications are enabled in Settings > Notifications & Status Bar > Manage Notifications > [Your App].
- If that doesn't help, try allowing background activity in Settings > Battery > App Battery Management > [Your App].
- Lastly, you can disable battery optimization for an app in Settings > Battery > More Battery Settings > Optimize Battery Use > [Your App].
Who faced such a (another) problem, let's say I have a working chat in a telegram, and today I read it through a smart watch while I was busy, but noticed that if there are more than 5+ unread notifications in the chat, then it stops even making a sound that something new has come, is there a way to treat this? and a similar story with viber as well. (translate.google)
AngelXTR91 said:
Who faced such a (another) problem, let's say I have a working chat in a telegram, and today I read it through a smart watch while I was busy, but noticed that if there are more than 5+ unread notifications in the chat, then it stops even making a sound that something new has come, is there a way to treat this? and a similar story with viber as well. (translate.google)
Click to expand...
Click to collapse
Unfortunately I'm not sure why that might be happening. I don't have a smartwatch and I don't use Telegram or Viber. I can tell you that Slack and Wyze both keep giving me notifications well after 5 of them. Maybe someone else might know.
My Neo 2T just arrived and upon further inspection, seemed to be preinstalled with Indian firmware by the seller which has Google Play Services and the languages I needed. Posted a screenshot of build number in case it helps anyone.
If anyone knows how to backup my ROM file, I'm willing to try and share it for everyone.
Edit: Out of ideas. MTK Droid Tool reports "Unknown ROM structure, backup NOT possible!"
dewidoj461 said:
My Neo 2T just arrived and upon further inspection, seemed to be preinstalled with Indian firmware by the seller which has Google Play Services and the languages I needed. Posted a screenshot of build number in case it helps anyone.
If anyone knows how to backup my ROM file, I'm willing to try and share it for everyone.
Edit: Out of ideas. MTK Droid Tool reports "Unknown ROM structure, backup NOT possible!"
Click to expand...
Click to collapse
As much as I'd love to find some sort of global ROM for this phone, that looks identical to my build number etc. when I first got the phone and probably the China ROM. Latest now is A14. When I asked, Realme was pretty adamant that this phone will never see a global ROM. They had also installed Google Play and a long list of languages for me before shipping, but these just bolt on to the stock China ROM.
I'm not sure how to tell 100% if it's actually the China ROM or not, but I'd give "Hey Google" a try, or Android Auto if you have an AA compatible vehicle. Would also be curious to know if your phone came with a bunch of bloatware apps and Breeno.
As for backing up, SP Tools is what worked for me. I recommend taking a proper backup ASAP just in case something goes wrong later. That said, I'm not sure how to anonymize the files it spits out (empty data partition, remove your IMEI etc) so it's safe to share.
I can confirm that "Hey Google" works, no chinese apps and breeno too. FYI, the bootloader was already unlocked when I got the phone. I noticed the Region defaulted to India so it's probably a custom firmware tailored to this phone. The box and manuals were chinese though.
As for the SP Flash Tool, how do I load the DA? This error appears after selecting the scatter file and clicking readback.
dewidoj461 said:
I can confirm that "Hey Google" works, no chinese apps and breeno too. FYI, the bootloader was already unlocked when I got the phone. I noticed the Region defaulted to India so it's probably a custom firmware tailored to this phone. The box and manuals were chinese though.
Click to expand...
Click to collapse
Oh wow. A proper global ROM for this phone would be amazing. I'll see if I can figure out how to turn a backup into something flashable. In the meantime I think I'm going to email Realme again and see if their tune has changed.
Would it be possible to share where you bought the phone? I got mine from "realme Direct Store" on AliExpress.
I bought it from a reseller in shopee malaysia. I've asked the seller for the source to no avail, they just said it was the supplier who installed the rom.
I sent Realme an email directly, hopefully I get a more favorable answer this time. Will update if I hear anything. My AndroidFileHost account finally got upload perms so if I manage to get the ROM out of them it'll be easy to share.
Managed to take a proper backup after reading the guide by mahotlov linked in your thread. Just let me know which files you'd need anytime and I'd be willing to share.
Edit: Wifi and bluetooth no longer works after flashing your magisk.img & vbmeta.img. Restored my backup and it works again, interesting
I have a DM from someone else who also has an India A13 ROM shipped with their Neo 2T, so this is definitely a thing, but Realme responded to me yesterday and is still claiming it doesn't exist. They are having similar issues with the China ROM I uploaded breaking things. I seriously hope there aren't multiple hardware versions under the RMX3357 model number messing everything up.
As for your backup, I think it should be possible to just pick some of the files from your backup and use them to replace the matching .img file in the China ROM upload. This is assuming the partition structure and other things are the same and only the contents of the partitions are different (which it should be, but you never know). Only thing I'm not 100% sure on is which partitions would be safe to share and which ones might have personal info like IMEI or bits of your data partition.
dewidoj461 said:
Just let me know which files you'd need anytime and I'd be willing to share.
Click to expand...
Click to collapse
Please check here scatter to backup phone on sp flash tool and give me link download ROM_0-55 except ROM_14,15,18,19,24(ram, nvdata, nvcfg, protect1, protect2) in folder SP Flash tool.
Andy_men2 said:
Please check here scatter to backup phone on sp flash tool and give me link download all ROM_0-55
Click to expand...
Click to collapse
I would advise against this @dewidoj461. One of those ROMs has your IMEI info in it, and if you had been using the phone before your backup there is likely personal info somewhere too, especially if SIMs were installed. Maybe the intent here is not malicious but that user account is brand new and you would absolutely be giving sensitive information by supplying your full backup.
EDIT: I'm also suspicious about that RAR. The scatter file is only 54kb while that RAR is 2.1MB.
Hello XDA people
Today we will be showing you how to enable push notifications while being able to update Push Notifications
before we start, this tutorial is all thanks to @badmania98, so credit goes to him
Let's get started!
Requirements:
A PC, ADB Drivers and platform-tools(they will be linked), Your Huawei phone being updated to the latest EMUI with GMS
Steps:
1. Download ADB Drivers and platform-devices onto your PC with these links:
ADB Drivers: https://adb.clockworkmod.com
platform-devices: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
2. Once downloaded extract platform-devices then open your phone and go to Settings --> About Phone and tap the build number 7 times, you should become a developer
3. Go to developer options on Settings --> System & Updates --> Developer Options, and Enable USB Debugging
4. Again, go to Settings and search for HDB, then enable HDB as well
5. Go to your PC and open CMD as an admin, then write the following "cd (drag and drop the platform-tools extracted folder)" then press enter
6. Plug your phone to your PC, and set it to Transfer Files and this is VERY important, turn on airplane mode(make sure when you plug the phone and press Transfer File, it should ask if you should access RSA Key on your phone, press yes/ok not sure which one of them was it)
7. after that, write the following on CMD through the pc "adb devices" and you should get your device on the CMD, if not you've done something wrong, so redo the steps or message me on telegram and I'll help
8. once done, write the following on CMD "adb shell pm disable-user --user 0 com.google.android.gsf"
9. Once you've done that, go to your phone and go to Settings --> Apps --> Apps --> Press the 4 dots on the top right and press Show System Process, then search for Google Account Manager, then go to Storage and clear data
10. Once done, reboot your phone(keeping sure that airplane mode is enabled throughout the process) and after its done rebooting go ahead and disable Airplane Mode
11. Go to the Play Store (Or Aurora store if you have Play Store frozen) and search for "Play Service Info" https://play.google.com/store/apps/details?id=com.weberdo.apps.serviceinfo&hl=en&gl=US, install it and open it, then press on Play Store button and go ahead and update Google Services
If you can't find the app, you can install it from here https://play-services-info.en.uptodown.com/android
And you're done! GMS is fully updated and now you no longer get the Play Certification Error and have Push Notifications working!
If you have questions or things don't work, message my telegram or comment it below
My Telegram: https://t.me/MohammedAwsXDA
Hello, with this procedure, Can we reboot the phone without use the airplane metode?
parotris2 said:
Hello, with this procedure, Can we reboot the phone without use the airplane metode?
Click to expand...
Click to collapse
you need airplane mode until the phone is rebooted
Thank you!
Thankyou buddy, I've tried many ways but it was working only for one or two days, but this one is the best for sure!
I still get message ask permission for Google location service when any apps want to use Google location service. Some apps can do correctly after tap "OK" but some apps keep ask for permission even I tap "OK" many times and cannot use app after that. Help me, please.
EDIT: after step "adb shell pm disable-user --user 0 com.google.android.gsf" and I cannot do step 11. My Google Maps is very very slow when try to get direction.
This is great, thanks. Although no access to play store or apps that use Geolocation, is there any way to fix this?