Samsung A3 medical device Root/Custom Firmware? - Android Q&A, Help & Troubleshooting

Hello,
I am new to this forum but maybe I have an interesting thing.
I found a Samsung A3 (SM-310F 16GB) wich was going to trash. It seems it acts as a medical device for monitoring heart diseases. It has a custom launcher loaded on wich you can only load the monitoring program. It has the Android top bar with time bluetooth-status battery and so on, but you can´t swipe down to access preferences or else. You also can´t take screenshot due to security guidelines and you can´t connect to it with a PC.
So my question, is it possible to do a root on this device. Or to flash it with a stock firmware to use it as anormal phone?
I´m wondering if anyone has an idea about this.
Thanks
Dirk

The door to any Android device is ADB ( read: Android Debug Bridge ). If device isn't accessable by means of ADB then you can NOTHING do with it, IMHO.

jwoegerbauer said:
The door to any Android device is ADB ( read: Android Debug Bridge ). If device isn't accessable by means of ADB then you can NOTHING do with it, IMHO.
Click to expand...
Click to collapse
Ok, so how do I know if it is accessable with ADB?
And just for understanding, how do you customize a normal android device (smartphone), that it won´t act like a phone anymore? Just custom firmware, or custom chips?

igel81 said:
Ok, so how do I know if it is accessable with ADB?
Click to expand...
Click to collapse
You on Windows computer
install the Android USB driver suitable to this phone
install ADB
Then you connect Windows computer and phone via USB-cable, power on phone, and run this ADB command
Code:
adb devices
Look also inside here.

jwoegerbauer said:
You on Windows computer
install the Android USB driver suitable to this phone
install ADB
Then you connect Windows computer and phone via USB-cable, power on phone, and run this ADB command
Code:
adb devices
Look also inside here.
Click to expand...
Click to collapse
Thanks. I tried this, but unfortunately it shows no device. By holding up and home at start, it boots into a firmware update mode. From here I can connect with adb in sideload mode. Don´t know if this is helpfull...

@igel81
If you can boot phone into ADB Sideload mode
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
then you can flash a ROM as a whole.

jwoegerbauer said:
@igel81
If you can boot phone into ADB Sideload mode
then you can flash a ROM as a whole.
Click to expand...
Click to collapse
Too bad, it doesn´t work. It says "footer is wrong" and "signature verification failed". It seems you can only install roms signed by that medical company.

Related

adb in recovery: "error: device offline"

I have adb 1.0.31. It works when I boot system.
If I try use it in recovery mode got:
error: device offline
Any way to fix?
PC Ubuntu trusty
Android 4.4.2 CWM
svs57 said:
I have adb 1.0.31. It works when I boot system.
If I try use it in recovery mode got:
error: device offline
Any way to fix?
PC Ubuntu trusty
Android 4.4.2 CWM
Click to expand...
Click to collapse
Whats your device and which recovery version / rom is installed?
LS.xD said:
Whats your device and which recovery version / rom is installed?
Click to expand...
Click to collapse
I am getting this too on the Galaxy Nexus. I'll try and run .adb and it won't connect. I will then get a message from Windows saying that the USB is not recognizable. X.x
LS.xD said:
Whats your device and which recovery version / rom is installed?
Click to expand...
Click to collapse
SGS4 SGH-I337 LOKI, Omega 28 (XXUFNC9), Kernel: KT-SGS4-KK4.4-TW-ATT-04.02.2014, Modem: I337UCUAMDL, Recovery OUDHS (CWM),
ADB
Try to access ADB in root. I have never used Windows for connecting ADB but for linux, its the code:
Code:
adb root
adb devices
If still it shows device as offline, remove the plug, reconnect and start adb as root again.
You can also use commands like adb kill-server and adb start-server.
If still you get the problem, try to plug the cable on another USB port and try again.
Hope it works.
#Su said:
Try to access ADB in root. I have never used Windows for connecting ADB but for linux, its the code:
Code:
adb root
adb devices
If still it shows device as offline, remove the plug, reconnect and start adb as root again.
You can also use commands like adb kill-server and adb start-server.
If still you get the problem, try to plug the cable on another USB port and try again.
Hope it works.
Click to expand...
Click to collapse
Thank you! Works. I also never use Windows Brother?
It's strange. Long time I use adb including in revovery.
I can't remember what I did but suddenly got "offline" message.
I plug, unplug, remove ~/.android and /data/misc/adb, start adb from root, reboot phone and PC, even rebuild adb from latest sources.
Nothing help
adb devices offline
Can anyone help me??
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Philips9 said:
Can anyone help me??View attachment 3120299
Click to expand...
Click to collapse
Same is happening with me. Don't know what to do. :/

Bootloader mode lost and device not anymore recognize under windows

Hello there,
my issue is that when i go in bootloader mode, i have a blackscreen, then my phone switch off. The system ui (custom rom Crdroid) and the recovery (orange fox) are working well.
I recognize also that when i reboot, i don't have anymore the MI logo where you have the status of your bootloader when it's unlocked.
More of it, when i plug it on windows , i cannot access to its usb storage (i tried also in mounting it through twrp, but same issue), nothing appears. For example, with an "adb devices" cmd command, no device can be found.
When i check the Windows devices manager, i can see an "unknown usb device" (i tried to force to reinstall drivers on it like the latest google usb driver, but windows refuse it, saying that it has the best and latest one for it).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Debugging mode is well enabled
Drivers have been reinstalled (the latest miflashtool install all what is needed)
Nothing appears on my smartphone when i plug it to windows (before i had a notification ot choose in charge mode, usb mode, etc...)
Plug to different usb port has been done without succeess
The phone doesn't appear in miflashtool obv
Restoring a previous backup didn't change the issue (i'm using the custom rom crdroid).
I guess all the things are linked but how i can fix it if i don't have access anymore to my bootloader mode to be able to flash some *.img via fastboot or if i cannot transfer files to my phone to operate in recovery, and more WHAT to do?
I hope you guys, will be able to help. The issue can be really annoying, and stuck me in "no rom update and no transfers of anything possible" situation.
Thank you beforehand
@bonbonboy
Try flashing the firmware through recovery from here https://androidfilehost.com/?fid=11410963190603850663 then reboot device and send it to bootloader via command adb reboot bootloader
It works like a charm!
Mi logo back, adb commands run, usb transfers work and no more error in the device manager.
You saved my day :good::good::good: Thanks a lot !

Backing up from recovery mode using adb?

Hi,
my Pixel 4 got stuck booting on the G logo. I tried rebooting from recovery, but no luck.
I sidloaded Android 11 hoping that would fix it, but no luck.
So my option I guess it's to factory reset. But in order to avoid losing data, can anyone give me pointers to backup the phone?
The bootloader is unlocked, but not rooted. Developer settings were enabled and usb debugging should on by default.
From recovery adb devices sees an unknown device I cannot successful run backup commands on as the device is unauthorized.
Any help is appreciated
andreadoli96 said:
The bootloader is unlocked, but not rooted. Developer settings were enabled and usb debugging should on by default.
From recovery adb devices sees an unknown device I cannot successful run backup commands on as the device is unauthorized.
Click to expand...
Click to collapse
You can't establish a valid ADB connection because on phone the ADB RSA keys didn't get confirmed
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That's what the "unauthorized" ADB-message means.
FYI: When you click to always allow, Android appends the public key from ADB on the computer into a specific file ( /data/misc/adb/adb_keys ) on the phone.
jwoegerbauer said:
You can't establish a valid ADB connection because on phone the ADB RSA keys didn't get confirmed
That's what the "unauthorized" ADB-message means.
FYI: When you click to always allow, Android appends the public key from ADB on the computer into a specific file ( /data/misc/adb/adb_keys ) on the phone.
Click to expand...
Click to collapse
So considering that I can't turn the phone on to confirm that is there a workaround?
@andreadoli96
Don't know whether this will work or not
Code:
adb devices
adb push %USERPROFILE%\.android\adbkey.pub /data/misc/adb/adb_keys
adb reboot
adb devices
Good luck.
BTW:
Take note that if your Android version has encryption enabled out of the box ( there’s no way to remove encryption !!! ) then trying to backup the user-data ( will say pulling them out by means of ADB ) may work, but is senseless because you can't decrypt them.

Doogee S88 pro - <waiting for device> during fastboot commands

Hello everyone!
This is my first post here so I hope everything I try to explain is according to the rules as far as I read it.
I need to root my Doogee S88 pro mobile since I need test and develop some AR stuff. The standard apps are not accesible by the playstore so I need to bypass that. For doing that I need to root my phone (this is what I read at least).
So... I installed the doggee usb drivers from their website for my phone, usb debugging is activated and OEM is activated as well. I downloaded the most recen platform tools and the usb-cable should be fine since I find the phone with
Code:
adb devices
I execute the following commands:
Code:
adb devices
adb reboot bootloader
fastboot devices
I get the small Fastboot text in the lower left corner. Then if I try to execute
Code:
fastboot flashing unlock
or
fastboot flashing unlock-critical
I only get back <waiting for device>
As said I installed the usb drivers provided by doogee. But: In the device manager I can see the following:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also I periodically (every 10 seconds) hear the sound as if a usb-device is disconnected. Afterwards the device manager refreshes the list.
So... it is a driver issue? I tried updating the drivers but picking manually the folder where driver files are located leads to no result. Automatic search as well. If it is a driver issue - where can I get the appropriate driver files? Thank you for any hint.
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
Unfortunately that didnt help either. Dunno... What I did was: I switched to my Lnux OS and over there it worked out of the box (only needed to install adb and fastboot from repositories).

Can we root this tablet?

Hello,
Can we root the Android tablet YC-83T?
Specs: https://portworld-solu.com/portfolio-item/yc-83t-portable-8-inch-android-10-wifi-tablet/
Runs Android 10 (go)
Ram: 1GB
Storage: 32gb
It's not locked down, as in it has google services and it can install APK files
I don't think so, I can't seem to find a custom recovery, you might be able to use adb sideload to install magisk or superuser though, good luck though
running adb reboot bootloader gets stuck on the boot logo, nice
17lifers said:
running adb reboot bootloader gets stuck on the boot logo, nice
Click to expand...
Click to collapse
could you send a picture of what it's stuck on?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
OEM Logo, not bricked as it can boot fine without usb cable (yes tablet was given away for free lol)
17lifers said:
OEM Logo, not bricked as it can boot fine without usb cable (yes tablet was given away for free lol)
Click to expand...
Click to collapse
lucky you, what you planning on rooting a tablet for?
oh and what model does it say you have in your settings?
YC-38T
might have an idea, does the tablet bootloop whilst adb is on? or does it just not turn off at all?
only with adb on, i can disconnect cable, force off the device, and boot it back up then it'll turn on fine
so it doesn't turn off at all?
no
17lifers said:
no
Click to expand...
Click to collapse
whilst it's stuck, could you run the fastboot devices command?
will try again, currently charging it (18:54 in the netherlands )
nope, no response
17lifers said:
nope, no response
Click to expand...
Click to collapse
It could have a non-standard VID/PID on the bootloader.
Is it even detected as anything?
What does DeviceManager say?
hm, if possible, can you go to recovery and use adb sideload? you should probably do the devicemanager thing first though
shows up as usb download gadget
17lifers said:
View attachment 5856319
shows up as usb download gadget
Click to expand...
Click to collapse
that's odd, what about entering recovery?
no command ¯\_(ツ)_/¯
we need usb drivers thats why, gonna install them

Categories

Resources