Related
I have the factory restore utility available for the 3T but not sure how to upload it or link to it since it exceeds the allowable upload size limit. It's a 1.2GB 7z file.
Split it up with WinRAR and then upload it to gdrive, Mega, mediafire... The server is up to you!
guisantes said:
I have the factory restore utility available for the 3T but not sure how to upload it or link to it since it exceeds the allowable upload size limit. It's a 1.2GB 7z file.
Click to expand...
Click to collapse
Please try the attached torrent file.
guisantes said:
Please try the attached torrent file.
Click to expand...
Click to collapse
I'm trying it. It's just a matter of time before I need something like this ;
I'm ~30% done so should be downloaded for me in ~60-80 minutes+.
Thanks.
---------- Post added at 04:51 PM ---------- Previous post was at 04:09 PM ----------
hachamacha said:
I'm trying it. It's just a matter of time before I need something like this ;
I'm ~30% done so should be downloaded for me in ~60-80 minutes+.
Thanks.
Click to expand...
Click to collapse
I've got the file downloaded, unpacked, and am wondering if there's a README that came with it? I can see a lot of the usual ways to use the components via fastboot, etc, but thought this was meant to be a .. "utter disaster recovery tool" ;. Or am I missing something?
Yes, it is and utter disaster recovery tool.
You may need the qualcomm drivers - 64 bit windows driver is attached. I believe mine autoinstalled without needing the files
**** NOTE: This procedure will completely wipe your entire device ****
To use the recovery tool.
1. With the phone turned off, press and hold the volume up button while inserting the USB cable attached to your PC.
2. Windows will recognize the Qualcomm driver and if you're lucky will auto install the driver.
3. Run the MsmDownloadTool V3.0.exe file with administrator privileges (right click and run as administrator)
4. One of the lines in the window should show COMM or something that is not "No Device" when your phone is attached and recognized as the Qualcomm loader
5. Click on that line item, then select Start
6. The whole procedure should take about 5 minutes and the line item will turn green when completed.
guisantes said:
Yes, it is and utter disaster recovery tool.
You may need the qualcomm drivers. I believe these can be easily found but if not, then I can upload them as well.
**** NOTE: This procedure will completely wipe your entire device ****
To use the recovery tool.
1. With the phone turned off, press and hold the volume up button while inserting the USB cable attached to your PC.
2. Windows will recognize the Qualcomm driver and if you're lucky will auto install the driver.
3. Run the MsmDownloadTool V3.0.exe file with administrator privileges (right click and run as administrator)
4. One of the lines in the window should show COMM or something that is not "No Device" when your phone is attached and recognized as the Qualcomm loader
5. Click on that line item, then select Start
6. The whole procedure should take about 5 minutes and the line item will turn green when completed.
Click to expand...
Click to collapse
Thanks, that seems very useful. Thanks for making it available here.
hachamacha said:
Thanks, that seems very useful. Thanks for making it available here.
Click to expand...
Click to collapse
No problem.
I've used a very similar tool previously for my oneplus one which would not power up Hopefully I won't need it for my 3T !
Here are the missing Qualcomm 64 bit drivers.
Can we make this a sticky or mention in the OP the recovery procedure from post #5? I know this will become invaluable later on as the few devs that bought this phone start fully getting into test mode.
Delete fixed. Never mind.
You should place this in general with the guides in the op with some pictures , I think many will benefit rather than diving through the QnA section for it
if i restore factory mode.what's the next?
---------- Post added at 07:35 PM ---------- Previous post was at 07:29 PM ----------
guisantes said:
Please try the attached torrent file.
Click to expand...
Click to collapse
when i restore, after reboot, have some error, it says: md5 checksum failed!
help me!
mgbotoe said:
You should place this in general with the guides in the op with some pictures , I think many will benefit rather than diving through the QnA section for it
Click to expand...
Click to collapse
I agree: Over on OP and here, I find myself recommending this guide and software nearly each day to someone that just "bricked" their phone. It's really good. As was just said, sticky it in "Guides" area. Thanks.
guisantes said:
Please try the attached torrent file.
Click to expand...
Click to collapse
Do you have the password from the OnePlus support?
FYI.. OP3T finally has an official section on the OP downloads page
http://downloads.oneplus.net/
martinklaus said:
Do you have the password from the OnePlus support?
Click to expand...
Click to collapse
There is no password on this archive.
mahonlee said:
if i restore factory mode.what's the next?
---------- Post added at 07:35 PM ---------- Previous post was at 07:29 PM ----------
when i restore, after reboot, have some error, it says: md5 checksum failed!
help me!
Click to expand...
Click to collapse
I used it without issue on my 3T. Are you still seeing the problem?
I uploaded it on megaNZ but I can't send links in here, so if you want it, send me a message. Btw: Thanks for the torrent, works perfectly!
guisantes said:
There is no password on this archive.
Click to expand...
Click to collapse
Yes, but on the original file from the support.
That's correct. I repackaged the files without a password after tech support extracted them via a remote session on my PC. Their archive password was very long with lots of non alpha-numeric characters.
I have signed out of huawei ID as I dont want to use any of their services. I think all is fine except for this function called HiSearch - where you scroll down from home screen in an empty space, it will bring down a HiSearch. Something like what you see on iOS. Now it kept asking me to sign in which I obviously dont want to.
Any way to disable this?
Find my thread how to debloat. You can remove almost every Huawei service including login in settings.
Please backup first. Sometimes you can cause a bootloop if you remove to much
Remove 'HiSearch'
===========================
Mate 20 Pro tips and tricks
===========================
Are you accidentally swiping the annoying 'HiSearch' feature on your new Huawei Mate 20 Pro?
Well, now you can safely remove it and it's not that hard if you pay attention to the instructions below.
(It probably works on other 'Mate 20' versions but I've only tested it on the 'Pro' version.)
First, we need to play with your phone.
---------------------------------------
On your phone, open 'Settings'. Scroll down to 'System'. Tap on 'About Phone'.
Scroll down to 'Build number' and tap on it about 5-7 times to enable developer options.
Next, go to 'Settings' > 'Developer Options' > 'USB Debugging', and enable it.
Finally, in 'Developer Options' scroll down to 'Select USB configuration' and choose 'Media Transfer Protocol (MTP)'.
On your computer...
-------------------
1) Download the ADB zip file to your Windows desktop computer or laptop.
Direct link to the ADB zip file is here:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Unzip the contents of the zip file to your desktop.
There will be a new folder called 'platform-tools'.
2) Connect your phone to the computer through a USB port and (if prompted) enable USB Debugging on your phone.
(There may be a pop up on your phone asking you to do this.)
Open the 'platform-tools' folder that you just unzipped and open a 'command prompt' from inside that folder.
Put your mouse somewhere in the folder, hold 'shift' and right click your mouse. Select 'Open command window here'.
3) Type "adb devices" then enter.
This just proves that you are connected to your phone.
The long ID number of your phone will show up if you are.
4) Type "adb Shell" then enter.
5) Type "pm list packages" then enter.
This will show you a long list of packages installed on your phone.
6) Type "pm uninstall -k --user 0 com.huawei.search" then enter.
7) Did you see the word "Success"?
8) You did it. Aren't you clever! No more accidental 'HiSearch' swipes on your phone.
Getting rid of Huawei p20 crap
Couldn't believe how simple this was to do. Hisearch has been so annoying and now its gone along with other crap.Thanks
I get an error doing this, it states Failure [not installed for 0]
I do get 2 search related packages from the list:
com.huawei.indexsearch
com.huawei.indexsearch.observer
I still have the annoying swipe down search on my P20 Pro
Also have listed under Com.Huawei....
package:com.huawei.mirrorlink
package:com.huawei.camera
package:com.huawei.synergy
package:com.huawei.android.launcher
package:com.huawei.hidisk
package:com.huawei.hiview
package:com.huawei.iaware
package:com.huawei.bluetooth
package:com.huawei.android.thememanager
package:com.huawei.android.chr
package:com.huawei.android.hsf
package:com.huawei.imedia.dolby
package:com.huawei.nearby
package:com.huawei.android.FloatTasks
package:com.huawei.desktop.systemui
package:com.huawei.motionservice
package:com.huawei.appmarket
package:com.huawei.recsys
package:com.huawei.android.totemweather
package:com.huawei.trustcircle
package:com.huawei.phoneservice
package:com.huawei.desktop.explorer
package:com.huawei.screenrecorder
package:com.huawei.himovie.overseas
package:com.huawei.videoeditor
package:com.huawei.securitymgr
package:com.huawei.iconnect
package:com.huawei.KoBackup
package:com.huawei.hiviewtunnel
package:com.huawei.imedia.sws
package:com.huawei.hiai
package:com.huawei.hwid
package:com.huawei.tips
package:com.huawei.systemserver
package:com.huawei.livewallpaper.paradise
package:com.huawei.android.instantshare
package:com.huawei.indexsearch.observer
package:com.huawei.trustagent
package:com.huawei.indexsearch
package:com.huawei.android.internal.app
package:com.huawei.hwasm
package:com.huawei.omacp
package:com.huawei.wifiprobqeservice
package:com.huawei.systemmanager
package:com.huawei.nb.service
package:com.huawei.HwMultiScreenShot
package:com.huawei.vassistant
package:com.huawei.languagedownloader
package:com.huawei.vision.server
package:com.huawei.watch.sync
package:com.huawei.hwstartupguide
package:com.huawei.fido.uafclient
package:com.huawei.android.mirrorshare
package:com.huawei.contactscamcard
package:com.huawei.android.totemweatherwidget
package:com.huawei.hitouch
package:com.huawei.compass
package:com.huawei.android.hwaps
package:com.huawei.android.hwouc
package:com.huawei.android.wfdft
package:com.huawei.mmitest
package:com.huawei.powergenie
package:com.huawei.android.instantonline
package:com.huawei.android.projectmenu
package:com.huawei.android.totemweatherapp
package:com.huawei.android.remotecontroller
package:com.huawei.android.pushagent
package:com.huawei.wifieapsimplmn
package:com.huawei.scanner
package:com.huawei.hwdetectrepair
package:com.huawei.hwusbearphoneupdate
package:com.huawei.android.karaoke
package:com.huawei.bd
package:com.huawei.aod
package:com.huawei.ims
package:com.huawei.lbs
jonboi said:
I get an error doing this, it states Failure [not installed for 0]
I do get 2 search related packages from the list:
com.huawei.indexsearch
com.huawei.indexsearch.observer
I still have the annoying swipe down search on my P20 Pro
Also have listed under Com.Huawei....
package:com.huawei.mirrorlink
package:com.huawei.camera
package:com.huawei.synergy
package:com.huawei.android.launcher
package:com.huawei.hidisk
package:com.huawei.hiview
package:com.huawei.iaware
package:com.huawei.bluetooth
package:com.huawei.android.thememanager
package:com.huawei.android.chr
package:com.huawei.android.hsf
package:com.huawei.imedia.dolby
package:com.huawei.nearby
package:com.huawei.android.FloatTasks
package:com.huawei.desktop.systemui
package:com.huawei.motionservice
package:com.huawei.appmarket
package:com.huawei.recsys
package:com.huawei.android.totemweather
package:com.huawei.trustcircle
package:com.huawei.phoneservice
package:com.huawei.desktop.explorer
package:com.huawei.screenrecorder
package:com.huawei.himovie.overseas
package:com.huawei.videoeditor
package:com.huawei.securitymgr
package:com.huawei.iconnect
package:com.huawei.KoBackup
package:com.huawei.hiviewtunnel
package:com.huawei.imedia.sws
package:com.huawei.hiai
package:com.huawei.hwid
package:com.huawei.tips
package:com.huawei.systemserver
package:com.huawei.livewallpaper.paradise
package:com.huawei.android.instantshare
package:com.huawei.indexsearch.observer
package:com.huawei.trustagent
package:com.huawei.indexsearch
package:com.huawei.android.internal.app
package:com.huawei.hwasm
package:com.huawei.omacp
package:com.huawei.wifiprobqeservice
package:com.huawei.systemmanager
package:com.huawei.nb.service
package:com.huawei.HwMultiScreenShot
package:com.huawei.vassistant
package:com.huawei.languagedownloader
package:com.huawei.vision.server
package:com.huawei.watch.sync
package:com.huawei.hwstartupguide
package:com.huawei.fido.uafclient
package:com.huawei.android.mirrorshare
package:com.huawei.contactscamcard
package:com.huawei.android.totemweatherwidget
package:com.huawei.hitouch
package:com.huawei.compass
package:com.huawei.android.hwaps
package:com.huawei.android.hwouc
package:com.huawei.android.wfdft
package:com.huawei.mmitest
package:com.huawei.powergenie
package:com.huawei.android.instantonline
package:com.huawei.android.projectmenu
package:com.huawei.android.totemweatherapp
package:com.huawei.android.remotecontroller
package:com.huawei.android.pushagent
package:com.huawei.wifieapsimplmn
package:com.huawei.scanner
package:com.huawei.hwdetectrepair
package:com.huawei.hwusbearphoneupdate
package:com.huawei.android.karaoke
package:com.huawei.bd
package:com.huawei.aod
package:com.huawei.ims
package:com.huawei.lbs
Click to expand...
Click to collapse
I had the same issue on 8.1 Oreo. It does show up in 9 Pie - and removes easily as stated above.
ePearl said:
I had the same issue on 8.1 Oreo. It does show up in 9 Pie - and removes easily as stated above.
Click to expand...
Click to collapse
Thanks
I'm still on 8.1.0.159. I'm not updating to Pie yet, waiting til some issues have been ironed out first. Guess i'll wait til then.
I can not do this it keeps saying I have "error: more than one device/emulator" I am unsure how to stop this error can someone please help this Hisearch is driving me crazy
Thank you
I disabled mine flawlessly. Not sure why it doesn't work for you
The Restless Soul said:
I disabled mine flawlessly. Not sure why it doesn't work for you
Click to expand...
Click to collapse
it keeps saying I have an emulator running, I try to kill it then it lists the phone but soon as that happens the emulator starts again it's killing me I hate this Hisearch
---------- Post added at 03:03 PM ---------- Previous post was at 02:54 PM ----------
The Restless Soul said:
I disabled mine flawlessly. Not sure why it doesn't work for you
Click to expand...
Click to collapse
it works but wont do it with my desktop only surface pro for some reason
Thanks mate. I did it 5 min ago without any problem
In my case, for it to work I had to put the following in cmd:
PS C:\platform-tools> adb uninstall -k --user 0 com.huawei.search
Thanks :good:
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.
Hello Everyone.
My ROG Phone II (WW_16.0631.1910.44.0) is not showing up in ADB (Terminal and Powershell) It only shows 'List of devices attached' but shows no actual device.
I also have a Xiaomi 4x (Santoni) which my computer is able to detect in CMD.
Troubleshooting done:
Ensured that my 'USB Debugging' is 'On'.
Tried selecting each option one by one: PTP, MIDI, No data transfer, etc, while also keeping my display on.
Platform-tools I have downloaded is r29.0.5.
I have a Windows 7, and when I connect my ROG II it said that it installed the drivers successfully. Restarted my computer & phone numerous times.
Please help.
Platinum_Pyth0n said:
Hello Everyone.
My ROG Phone II (WW_16.0631.1910.44.0) is not showing up in ADB (Terminal and Powershell) It only shows 'List of devices attached' but shows no actual device.
I also have a Xiaomi 4x (Santoni) which my computer is able to detect in CMD.
Troubleshooting done:
Ensured that my 'USB Debugging' is 'On'.
Tried selecting each option one by one: PTP, MIDI, No data transfer, etc, while also keeping my display on.
Platform-tools I have downloaded is r29.0.5.
I have a Windows 7, and when I connect my ROG II it said that it installed the drivers successfully. Restarted my computer & phone numerous times.
Please help.
Click to expand...
Click to collapse
I think you are missing Asus drivers. Install these drivers as I encountered same problem and in device manager I found out that drivers were missing.
---------- Post added at 09:13 AM ---------- Previous post was at 09:07 AM ----------
Drivers are given in Guides section under thread "Latest guide to covert......1910.35" on page 7.
zohaibshafijutt said:
I think you are missing Asus drivers. Install these drivers as I encountered same problem and in device manager I found out that drivers were missing.
---------- Post added at 09:13 AM ---------- Previous post was at 09:07 AM ----------
Drivers are given in Guides section under thread "Latest guide to covert......1910.35" on page 7.
Click to expand...
Click to collapse
Thank you very much! Couldn't find the drivers anywhere.
When moving the redmi Note 9 the screen turns on by itself. I have disabled the "lift to activate" option, but the screen keeps turning on when moving.
Someone can help me please?
When the winds of change blow, some build walls, others build windmills
antz_77 said:
When moving the redmi Note 9 the screen turns on by itself. I have disabled the "lift to activate" option, but the screen keeps turning on when moving.
Someone can help me please?
When the winds of change blow, some build walls, others build windmills
Click to expand...
Click to collapse
Mine does this also when "Raise to wake" is on ( settings > lockscreen > raise to wake), but after switching this off I can wave the phone about all I like and the screen remains off
Have you tried restarting in safe mode? Just wondering if you might have an app which is keeping your phone from sleeping
thesoupthief said:
Mine does this also when "Raise to wake" is on ( settings > lockscreen > raise to wake), but after switching this off I can wave the phone about all I like and the screen remains off
Have you tried restarting in safe mode? Just wondering if you might have an app which is keeping your phone from sleeping
Click to expand...
Click to collapse
I disabled raise to wake, but screen is turning on yet when moving (only when moving)
When the winds of change blow, some build walls, others build windmills
antz_77 said:
I disabled raise to wake, but screen is turning on yet when moving (only when moving)
When the winds of change blow, some build walls, others build windmills
Click to expand...
Click to collapse
Try toggling raise to wake of on on then off, then reboot the phone - sounds like something is stopping the setting taking effect
Clearly not normal behaviour
Nuclear option would be to reset to factory settings, but I'd be slow enough to do that
Why not just put pocket mode on and leave it at that?
thesoupthief said:
Try toggling raise to wake of on on then off, then reboot the phone - sounds like something is stopping the setting taking effect
Clearly not normal behaviour
Nuclear option would be to reset to factory settings, but I'd be slow enough to do that
Why not just put pocket mode on and leave it at that?
Click to expand...
Click to collapse
I tried it, but nothing. Screen continue turning on whe moving the phone. I put pocket mode (even cover frontal cámara) and same result.
I have thinking about factory reset, but one user tried a factory reset ( another xiaomi forum ) , without results.
When the winds of change blow, some build walls, others build windmills
Not sure if it's relevant but I'm on the QJOEUXM build - so the EU ROM - 4gb, 128gb redmi note 9
You too?
If so it seems very odd that we're having such different experiences
i have the same problem! thought im going crazy
i try update the system and will update afterwards
Mine has the same problem on global firmware but not on china firm
After a bit of searching i found the solution for this using adb.
All you have to do is run these 2 commands
adb shell
settings put secure wake_gesture_enabled 0
Click to expand...
Click to collapse
Natedanver_99 said:
After a bit of searching i found the solution for this using adb.
All you have to do is run these 2 commands
Click to expand...
Click to collapse
thanks for the tip with adb it works perfectly
Natedanver_99 said:
After a bit of searching i found the solution for this using adb.
All you have to do is run these 2 commands
Click to expand...
Click to collapse
It works for me. Thank you.
When the winds of change blow, some build walls, others build windmills
i think i got a permission error
how do i give permission?
merlin:/ $ settings put secure wake_gecture_enables 0
Security exception: Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS
java.lang.SecurityException: Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS
at com.android.providers.settings.SettingsProvider.enforceWritePermission(SettingsProvider.java:2050)
at com.android.providers.settings.SettingsProvider.mutateSecureSetting(SettingsProvider.java:1570)
at com.android.providers.settings.SettingsProvider.insertSecureSetting(SettingsProvider.java:1530)
at com.android.providers.settings.SettingsProvider.call(SettingsProvider.java:437)
at android.content.ContentProvider.call(ContentProvider.java:2177)
at android.content.ContentProvider$Transport.call(ContentProvider.java:477)
at com.android.providers.settings.SettingsService$MyShellCommand.putForUser(SettingsService.java:375)
at com.android.providers.settings.SettingsService$MyShellCommand.onCommand(SettingsService.java:277)
at android.os.ShellCommand.exec(ShellCommand.java:104)
at com.android.providers.settings.SettingsService.onShellCommand(SettingsService.java:49)
at android.os.Binder.shellCommand(Binder.java:881)
at android.os.Binder.onTransact(Binder.java:765)
at android.os.Binder.execTransactInternal(Binder.java:1021)
at android.os.Binder.execTransact(Binder.java:994)
thesoupthief said:
Not sure if it's relevant but I'm on the QJOEUXM build - so the EU ROM - 4gb, 128gb redmi note 9
You too?
If so it seems very odd that we're having such different experiences
Click to expand...
Click to collapse
Version here is QJOMIXM. Same problem.
arik100 said:
i think i got a permission error
how do i give permission?
merlin:/ $ settings put secure wake_gecture_enables 0
Security exception: Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS
java.lang.SecurityException: Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS
at com.android.providers.settings.SettingsProvider.enforceWritePermission(SettingsProvider.java:2050)
at com.android.providers.settings.SettingsProvider.mutateSecureSetting(SettingsProvider.java:1570)
at com.android.providers.settings.SettingsProvider.insertSecureSetting(SettingsProvider.java:1530)
at com.android.providers.settings.SettingsProvider.call(SettingsProvider.java:437)
at android.content.ContentProvider.call(ContentProvider.java:2177)
at android.content.ContentProvider$Transport.call(ContentProvider.java:477)
at com.android.providers.settings.SettingsService$MyShellCommand.putForUser(SettingsService.java:375)
at com.android.providers.settings.SettingsService$MyShellCommand.onCommand(SettingsService.java:277)
at android.os.ShellCommand.exec(ShellCommand.java:104)
at com.android.providers.settings.SettingsService.onShellCommand(SettingsService.java:49)
at android.os.Binder.shellCommand(Binder.java:881)
at android.os.Binder.onTransact(Binder.java:765)
at android.os.Binder.execTransactInternal(Binder.java:1021)
at android.os.Binder.execTransact(Binder.java:994)
Click to expand...
Click to collapse
You must enable first these 2 options in developers menu
I'm stupid and I don't know how to do this and have the same issue, could someone walk me trough with how to get into ADB and use the commands
I have the same problem, I upgraded to MIUI12 and it didn't solve ... the solution would be only with adb ...
---------- Post added at 02:01 PM ---------- Previous post was at 01:25 PM ----------
Natedanver_99 said:
After a bit of searching i found the solution for this using adb.
All you have to do is run these 2 commands
Click to expand...
Click to collapse
...have a link that teaches "step by step" how to do this.....
Natedanver_99 said:
After a bit of searching i found the solution for this using adb.
All you have to do is run these 2 commands
Click to expand...
Click to collapse
Thanks! That did the trick!!
And after a proper cleanup my GF's brand new Note 9 is really a good buy!
Removal/disabling pre-installed 'crapware' is always a good start, regardless of brand!
Solved!
I created my xda accout just to say thanks, this worked perfectly.
Natedanver_99 said:
After a bit of searching i found the solution for this using adb.
All you have to do is run these 2 commands
Click to expand...
Click to collapse
logan3103 said:
I created my xda accout just to say thanks, this worked perfectly.
Click to expand...
Click to collapse
Pls help me how to perform this process i have the issue
---------- Post added at 01:47 AM ---------- Previous post was at 01:43 AM ----------
Zah5 said:
thanks for the tip with adb it works perfectly
Click to expand...
Click to collapse
Pls help me how to perform this action i have the same issue redmi note 9 global
---------- Post added at 02:06 AM ---------- Previous post was at 01:47 AM ----------
Zah5 said:
thanks for the tip with adb it works perfectly
Click to expand...
Click to collapse
Pls help me how to perfom this trick..i have the same issue
1- Activate developers options on your phone.
For this you have to open Settings>About phone and tap on MIUI Version for about 7-10 time.
Now you go back to settings>adittional settings > Developer Options. Make sure you have USB Debugging and
USB Debugging(Security settings) are activated. For this last one i think you have to be logged in your MI account.
2- Install ADB(Android Debug Bridge) on your computer.
If you are on Windows, install ADB Universal drivers first.
Then download the ADB files.
3- Excecute commands.
Open a Command prompt (or shell) on the directory where you have the adb files.
Connect your phone with a USB cable. Change the USB mode to “file transfer".
In the Command Prompt window, enter the following command to launch the ADB daemon: adb devices.
You should get a prompt on your phone to allow (or deny) USB Debugging. Allow it and re enter on command prompt the "adb devices" command.
Now you should see your phone serial number. And you just have to enter the mentioned commands.
adb shell
settings put secure wake_gesture_enabled 0
exit (to exit adb shell)
And that`s all. Your phone screen should stay locked when you move it at this point.
Hope this helps you.
Dadaonacsil09 said:
Pls help me how to perform this process i have the issue
---------- Post added at 01:47 AM ---------- Previous post was at 01:43 AM ----------
Pls help me how to perform this action i have the same issue redmi note 9 global
---------- Post added at 02:06 AM ---------- Previous post was at 01:47 AM ----------
Pls help me how to perfom this trick..i have the same issue
Click to expand...
Click to collapse