+- Sinisterly (https://sinister.li)
+-- Forum: Hacking (https://sinister.li/Forum-Hacking)
+--- Forum: Social Engineering (https://sinister.li/Forum-Social-Engineering)
+--- Thread: Point-of-Sale Activation (/Thread-Point-of-Sale-Activation)
RE: Point-of-Sale Activation - chesterbeatdeath - 09-19-2018
(09-17-2018, 03:07 AM)SammyWii Wrote: Just picked up one of these RCA Voyager 3 tablets cheap not knowing that this DiSa crap would be so annoying to resolve. I've been able to use the "hit escape a bunch of times" method to get into the tablet as normal and turn on USB debugging. However, adb doesn't seem to show me any obvious packages to uninstall. Below is the list that I get from "adb package list." I'm not an Android guy, so maybe there is something unexpected there that I didn't notice.
Also, I can also look at files via adb (as well as Windows explorer), but there is no .disatest or anything like that that I can find.
Any help would be appreciated. Thanks!
$ pm list packages
package:com.google.android.youtube
package:com.android.providers.telephony
package:com.google.android.googlequicksearchbox
package:com.android.partnerLayout
package:com.android.providers.calendar
package:com.android.providers.media
package:com.google.android.apps.docs.editors.docs
package:com.google.android.onetimeinitializer
package:com.android.wallpapercropper
package:com.android.documentsui
package:com.android.galaxy4
package:com.android.externalstorage
package:com.google.android.apps.enterprise.dmagent
package:com.android.htmlviewer
package:com.rfi.sams.android
package:com.android.mms.service
package:com.google.android.apps.docs.editors.sheets
package:com.google.android.apps.docs.editors.slides
package:com.android.providers.downloads
package:com.google.android.apps.genie.geniewidget
package:com.google.android.configupdater
package:com.intel.thermal
package:com.android.soundrecorder
package:com.walmart.android
package:com.android.defcontainer
package:com.android.providers.downloads.ui
package:com.android.vending
package:com.android.pacprocessor
package:com.android.certinstaller
package:com.google.android.marvin.talkback
package:android.rockchip.update.service
package:android
package:com.android.contacts
package:com.android.camera2
package:com.android.eboda.usermanual
package:com.android.backupconfirm
package:air.com.vudu.air.DownloaderTablet
package:com.google.android.launcher
package:com.android.statementservice
package:com.google.android.gm
package:com.android.wallpaper.holospiral
package:com.android.phasebeam
package:com.google.android.setupwizard
package:com.android.providers.settings
package:com.android.sharedstoragebackup
package:com.google.android.music
package:com.android.printspooler
package:com.android.dreams.basic
package:com.android.rk
package:com.android.inputdevices
package:com.google.android.apps.cloudprint
package:com.android.musicfx
package:com.google.android.apps.docs
package:com.google.android.apps.maps
package:com.google.android.apps.plus
package:com.google.android.webview
package:com.android.server.telecom
package:com.google.android.syncadapters.contacts
package:com.android.facelock
package:com.android.keychain
package:com.android.chrome
package:com.example.tablettestv2
package:com.android.gallery3d
package:com.google.android.packageinstaller
package:com.google.android.gms
package:com.google.android.gsf
package:com.google.android.tag
package:com.google.android.tts
package:com.google.android.partnersetup
package:com.google.android.videos
package:com.android.proxyhandler
package:com.intel.internal.telephony.OemTelephonyApp
package:com.android.inputmethod.latin
package:com.google.android.feedback
package:com.google.android.apps.photos
package:com.android.ebodalxz.rca
package:com.google.android.calendar
package:com.android.managedprovisioning
package:com.android.noisefield
package:com.android.providers.partnerbookmarks
package:com.google.android.gsf.login
package:com.android.smspush
package:com.android.wallpaper.livepicker
package:com.cghs.stresstest
package:com.google.android.backuptransport
package:com.android.bookmarkprovider
package:com.android.settings
package:com.android.calculator2
package:com.google.android.apps.books
package:com.android.wallpaper
package:com.autoreboot.android
package:com.android.vpndialogs
package:com.rockchip.rftesttool
package:com.google.android.keep
package:com.google.android.talk
package:com.android.email
package:com.android.phone
package:com.android.shell
package:com.android.providers.userdictionary
package:com.android.location.fused
package:com.android.deskclock
package:com.android.systemui
package:com.android.exchange
package:com.android.bluetoothmidiservice
package:com.DeviceTest
package:com.google.android.play.games
package:com.google.android.apps.magazines
package:com.android.bluetooth
package:com.android.providers.contacts
package:com.android.captiveportallogin
package:android.rk.RockVideoPlayer
Thanks,
Sammy
Adb devices
Adb shell
pm uninstall --user 0 com.android.yfdisa
Done.
That's all it is. Cannot patch around what I did. I'm confident it works on anything that the adb recognizes including ANY mobile device w a DiSa lock.
I tried to tell them I could fix it for them because a lock that doesn't shut all the way provides no protection. They told me to fuck off and called me a script kiddie so they can gargle my sack.
Here's a more rational and concise methodology: https://sinister.li/Thread-A-Full-On-Guide-to-Nextbook-Activation-Intel-and-A64-SUCCINCT
Both Intel and ARM64 version cracks. Everyone spread this!
RE: Point-of-Sale Activation - SammyWii - 09-20-2018
(09-19-2018, 06:23 AM)thehorridness Wrote: Adb devices
Adb shell
pm uninstall --user 0 com.android.yfdisa
Done.
That's all it is. Cannot patch around what I did. I'm confident it works on anything that the adb recognizes including ANY mobile device w a DiSa lock.
I tried to tell them I could fix it for them because a lock that doesn't shut all the way provides no protection. They told me to fuck off and called me a script kiddie so they can gargle my sack.
Here's a more rational and concise methodology: https://sinister.li/Thread-A-Full-On-Guide-to-Nextbook-Activation-Intel-and-A64-SUCCINCT
Both Intel and ARM64 version cracks. Everyone spread this!
Thanks for the reply, but that is exactly what I tried earlier. When I do that, it tells me that package is not installed. That is why I posted the package listing hoping someone would see a name out of place in there. Here is what I get with your uninstall line:
$ pm uninstall --user 0 com.android.yfdisa
Failure - not installed for 0
Am I doing something wrong? Or have the DiSa folks changed something again? Any help would be appreciated.
Thanks,
Sammy
RE: Point-of-Sale Activation - chesterbeatdeath - 09-21-2018
(09-20-2018, 04:42 AM)SammyWii Wrote:(09-19-2018, 06:23 AM)thehorridness Wrote: Adb devices
Adb shell
pm uninstall --user 0 com.android.yfdisa
Done.
That's all it is. Cannot patch around what I did. I'm confident it works on anything that the adb recognizes including ANY mobile device w a DiSa lock.
I tried to tell them I could fix it for them because a lock that doesn't shut all the way provides no protection. They told me to fuck off and called me a script kiddie so they can gargle my sack.
Here's a more rational and concise methodology: https://sinister.li/Thread-A-Full-On-Guide-to-Nextbook-Activation-Intel-and-A64-SUCCINCT
Both Intel and ARM64 version cracks. Everyone spread this!
Thanks for the reply, but that is exactly what I tried earlier. When I do that, it tells me that package is not installed. That is why I posted the package listing hoping someone would see a name out of place in there. Here is what I get with your uninstall line:
$ pm uninstall --user 0 com.android.yfdisa
Failure - not installed for 0
Am I doing something wrong? Or have the DiSa folks changed something again? Any help would be appreciated.
Thanks,
Sammy
DiSa is still trying to get their wall of bullshit penetrated. PM me and we can have a chat about my year plus experience in just this item. I think I can help your connection titrate off slowly. If there is an allmighty being controlling shit he has a personal vendetta against me and my byass words. There is too, too much proprietary software that is easily uninstalled without harming shit is what you're looking to shut down. Keep an eye out for a Wallyworld when things get too hectic. For the one staff member in electronics. But I REALLY want the Tech Support Treasure Hunting. Make sure your price is right by having the deskman do a POS scan just to check. If I have to go to someone's house, meaning I can't take the bus there,
Hit me back up if you'd like to know more. Intel and E-Fun have written the book on the shittiest place in the in my opinion
Send me your twitter chat usename or something and I'll keep you updated on every step of every fix.
RE: Point-of-Sale Activation - bloodrain - 09-21-2018
I have a couple RCA Voyager (ARM64) which do not appear to have a testdisa file or a disa package to uninstall. Perhaps there is a new version of DiSa now. Additionally if you plug in a normal USB OTG cable to the RCA tablet the device shuts down. I got around this by making my own OTG cable with the shield and ground wires disconnected. Not sure if the USB is on purpose or not. Still working on it for now trying to find where they have hidden this file. I have also discovered that the DiSa lock screen is integrated into the Settings apk instead of its own app and there is a DiSa entry in the About tab in settings which shows a DiSa relock function and a DiSa menu which is password protected.
RE: Point-of-Sale Activation - recklessfnarkery - 09-21-2018
(09-20-2018, 04:42 AM)SammyWii Wrote:(09-19-2018, 06:23 AM)thehorridness Wrote: Adb devices
Adb shell
pm uninstall --user 0 com.android.yfdisa
Done.
That's all it is. Cannot patch around what I did. I'm confident it works on anything that the adb recognizes including ANY mobile device w a DiSa lock.
I tried to tell them I could fix it for them because a lock that doesn't shut all the way provides no protection. They told me to fuck off and called me a script kiddie so they can gargle my sack.
Here's a more rational and concise methodology: https://sinister.li/Thread-A-Full-On-Guide-to-Nextbook-Activation-Intel-and-A64-SUCCINCT
Both Intel and ARM64 version cracks. Everyone spread this!
Thanks for the reply, but that is exactly what I tried earlier. When I do that, it tells me that package is not installed. That is why I posted the package listing hoping someone would see a name out of place in there. Here is what I get with your uninstall line:
$ pm uninstall --user 0 com.android.yfdisa
Failure - not installed for 0
Am I doing something wrong? Or have the DiSa folks changed something again? Any help would be appreciated.
Thanks,
Sammy
Also, download "Application Manager" from the Play Store to see what background processes are actually doing. If any program pops up that you didn't install or you did install it, but it doesn't have Admin level access, thus I think you'd like App Manager because it tells you EVERYTHING running, fore or background and gives you full access to stop process on every single package that isn't visible to non-rooted phones file manager's, including yfdisa is revealed in the process list.
It's there. Check the link in my signature to see all my research compiled after more than a year working these things every which way. pm uninstall -k --user 0 com.android.yfdisa
It hasn't changed since the newest version came out, and it uses SELinux commands in the terminal, so my command like should work like that as long as you put the correct commands for the distro being used.
so
"pm uninstall -k --user 0 com.yfdisa.android"
I has never failed me on the hundreds distros I've used. pm uninstall is a very powerful command.
Just try it for yourself or google which part of my instructions seem wrong.
But this command has NEVER failed to help me out.
RE: Point-of-Sale Activation - chesterbeatdeath - 09-21-2018
(09-21-2018, 03:10 AM)recklessfnarkery Wrote:(09-20-2018, 04:42 AM)SammyWii Wrote:(09-19-2018, 06:23 AM)thehorridness Wrote: Adb devices
Adb shell
pm uninstall --user 0 com.android.yfdisa
Done.
That's all it is. Cannot patch around what I did. I'm confident it works on anything that the adb recognizes including ANY mobile device w a DiSa lock.
I tried to tell them I could fix it for them because a lock that doesn't shut all the way provides no protection. They told me to fuck off and called me a script kiddie so they can gargle my sack.
Here's a more rational and concise methodology: https://sinister.li/Thread-A-Full-On-Guide-to-Nextbook-Activation-Intel-and-A64-SUCCINCT
Both Intel and ARM64 version cracks. Everyone spread this!
Thanks for the reply, but that is exactly what I tried earlier. When I do that, it tells me that package is not installed. That is why I posted the package listing hoping someone would see a name out of place in there. Here is what I get with your uninstall line:
$ pm uninstall --user 0 com.android.yfdisa
Failure - not installed for 0
Am I doing something wrong? Or have the DiSa folks changed something again? Any help would be appreciated.
Thanks,
Sammy
Also, download "Application Manager" from the Play Store to see what background processes are actually doing. If any program pops up that you didn't install or you did install it, but it doesn't have Admin level access, thus I think you'd like App Manager because it tells you EVERYTHING running, fore or background and gives you full access to stop process on every single package that isn't visible to non-rooted phones file manager's, including yfdisa is revealed in the process list.
It's there. Check the link in my signature to see all my research compiled after more than a year working these things every which way. pm uninstall -k --user 0 com.android.yfdisa
It hasn't changed since the newest version came out, and it uses SELinux commands in the terminal, so my command like should work like that as long as you put the correct commands for the distro being used.
so
"pm uninstall -k --user 0 com.yfdisa.android"
I has never failed me on the hundreds distros I've used. pm uninstall is a very powerful command.
Just try it for yourself or google which part of my instructions seem wrong.
But this command has NEVER failed to help me out.
Good for you checking and actually reading the posts I've made on this exact topic; Nextbooks. You wasted no time adapting to the hacks and cracks I've put into their Android version. So, kudos! No one ever wants to listen to me, but you've made it abundantly clear that you are a freaking study freak. Thanks for proving out my concepts!
RE: Point-of-Sale Activation - trapthot - 09-21-2018
i see you guys are still attempting to crack this. i figured it out 2-3 years ago but never actually done it
you would actually need to leave your house and physically be in the store . other than that it's easy as long as the security cams don't see you
if you don't want to leave your house your only options is remote access to the store POS but you still need login credentials to the system so you can to SE an employee
RE: Point-of-Sale Activation - WoWSuchFluffy - 09-30-2018
Talking about site development, I want to add that sometimes it occurs that without a help of pros you can't handle it. Thankfully, with BI solutions it's much easier. They can provide you with useful information and also help with developing itself. I rely on them.
RE: Point-of-Sale Activation - BIGRED42069 - 10-14-2018
(09-27-2017, 04:14 PM)pcrepairscody Wrote: Not trying to bump an old post or grave-diggin. Figured i should just pick up on the same thread we've already been discussing the issue in.Need a activation code for my next book ares 10a sn yfgv0417024599 model nx16a10132s ps ..
So i have been pulling my damn hair and teeth out on this S.O.B. I have managed to find another serial, diSa, and activation code for another NX16A10132 PS..
DiSa #-1001290322
Activation Code
423711
Serial Number
YFGV0317123284
Model Number
NX16A10132S PS
Now the problem is, maybe somebody can shed some light on my brain-dead stupidity. without the actual testdiSa file from that particulare devices storage, i cant decode where the hell there getting the activation code from..
Now looking at how the same diSa company did the model RCT6973W43 SD tablets activation codes, i see no formula or logic to determin the activation code from the serial, upc, or disa number. so it has to be in the testdiSa file.. ok. lost track of topic......... .......
Example:
disa-1001290309
Activation Code
118822
Serial Number
Model Number
RCT6973W43 SD
disa-1001290321
Activation Code
910131
Serial Number
Model Number
RCT6973W43 SD
disa-1001290343
Activation Code
430132
Serial Number
Model Number
RCT6973W43 SD
disa-1001290218
Activation Code
988771
Serial Number
Model Number
RCT6973W43 SD
disa-1001290251
Activation Code
601671
Serial Number
Model Number
RCT6973W43 SD
disa-1001290242
Activation Code
223285
Serial Number
Model Number
RCT6973W43 SD
disa-1001290226
Activation Code
179909
Serial Number
Model Number
RCT6973W43 SD
disa-1001290219
Activation Code
678360
Serial Number
Model Number
RCT6973W43 SD
disa-1001290201
Activation Code
141859
Serial Number
Model Number
RCT6973W43 SD
////////////////////
and then the Nextbook one...... Memberberries- Same diSa company- does that mean same logic?
disa-1001290322
Activation Code
423711
Serial Number
YFGV0317123284
Model Number
NX16A10132S PS
Back on track....
This Tablet is:
Model-NX16A10132S PS
DiSa-1001290314
Serial #-YFGV0317003014
Says Manufacture date March 2017
Now i thought the UPC would have something to do with it, but cant find any correlation.
UPC-4727500149
PM or email me for the testdiSa file from the tablet. i have 2 copies. the original from when it was given to me and the one after i tried 2 codes. the file changes every-time to try a code. guessing its keeping track of failed attempts to lock it down.
Would like to do something with the tablet, otherwise i don't make anything, loose all this time spent, and gives me bad rep.
THANKS EVERYONE. hope we can all help each-other out. This is going to be a reacquiring problem with all future devices.....................
RE: Point-of-Sale Activation - lugnut2099 - 10-17-2018
Hi everybody. Been following this thread since practically the beginning but wasn't ever able to post before due to some screwup that kept occurring everytime I'd try to sign up. Anyway, now that I finally can post, I'll contribute something that may be useful even:
If you have a Voyager III and A). Cannot locate the testdisa file, and/or B). Have had no success with attempting to uninstall com.yfdisa.android, then try this:
0). Gain access to the system via the old OTG-Keyboard / Esc button trick. Go to Settings, enable Developer Options and USB Debugging, all the usual.
1). Now this step MAY be entirely unneccessary, but it's the way I went about it, so I'll mention it just in case. Go to your app manager while in Settings and go ahead and uninstall the Sam's Club, Walmart and Vudu apps. I'm fairly positive the Sam's and WM apps are benign, but you don't need 'em anyway. The Vudu app however, may be part of the DISA problem - as noted somewhere else in the thread - so defintely delete that one just in case. There's a few other apps you can safely disable while you're in there, but I'll leave that up to you.
2). Now pull up a command line and connect an ADB shell. I assume you've already found that you get a "not installed" error when attempting to remove com.yfdisa.android or you wouldn't be bothering with this. So forget about that, and type the following: "pm uninstall -k --user 0 com.example.weibu.disa"
3). Does it show "Success" after running that command? If yes, I think you're done - go ahead and reboot and you shouldn't have the DISA lockscreen anymore.
That's it. I have no idea if this works on any Nextbooks or other DISA-locked Androids, but I think between the earlier method and this one, we've got the Voyagers down cold. (Unless there's a third variant lurking out there somewhere...)