While in the Sony Tablet Bootloader Discussion I have created a R5A ADB Recovery Driver.
This will overwrite your Sony Tablet S ADB driver.
This does support x86 and x64.
Please note that the recovery is going to disallow most if not some adb commands, I created this so people can access the recovery with the new recovery address via ADB, hopefully someone would be able to bypass and hack the recovery using this.
This uses the ADB from the system so it is ok to install.
EDIT: I was really suppose to use adb install to install an application.
EDIT 2: Sideload just throws back an error, I have not tested ADB install and I doubt that would work.
Screeny of the commands that would work if I had a flashable zip file and also if the recovery allowed such thing:
{
"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"
}
Download and Installation instructions here: http://caftp.pcsat.tv/drivers/puredriver_sts_r5a_adb
andyabc said:
While in the Sony Tablet Bootloader Discussion I have created a R5A ADB Recovery Driver.
This will overwrite your Sony Tablet S ADB driver.
This does support x86 and x64.
Please note that the recovery is going to disallow most if not some adb commands, I created this so people can access the recovery with the new recovery address via ADB, hopefully someone would be able to bypass and hack the recovery using this.
This uses the ADB from the system so it is ok to install.
EDIT: I was really suppose to use adb install to install an application.
EDIT 2: Sideload just throws back an error, I have not tested ADB install and I doubt that would work.
Screeny of the commands that would work if I had a flashable zip file and also if the recovery allowed such thing:
Download and Installation instructions here: http://caftp.3owl.com/Drivers/PureDriver_STS_R5A_ADB/
Click to expand...
Click to collapse
says install method not supported for this type of file. I was hoping to use this to allow flashing on my soft brick tab that I just can't seem to get going again.
jamminjon82 said:
says install method not supported for this type of file. I was hoping to use this to allow flashing on my soft brick tab that I just can't seem to get going again.
Click to expand...
Click to collapse
Yeah the install command is just for installing applications...
Sent from my Nexus 4 using Tapatalk 4
Can we run adb shell and “ dump_image boot /sdcard/boot.img “ to port CWM
Plays2 said:
Can we run adb shell and “ dump_image boot /sdcard/boot.img “ to port CWM
Click to expand...
Click to collapse
Nope, unfortunately Sony did block most of the ADB commands and I assume it is blocked with either ADB unlock code or some file which is required to unlock the commands.
Sent from my Nexus 4 using Tapatalk 4
Related
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. :/
Hello,
I'm trying to unlock the bootloader of my kindle fire Apollo, i'm using this tutorial Link., i'm getting most of it, but this i just dont understand:
download the attachment on the following post: http://forum.xda-developers.com/show...2&postcount=46
Then place the file inside the attachement to C:\Python27 should be C:\Python\cuberHDX.py
Click to expand...
Click to collapse
I've just put the cuberHDX file in my python27 directory, and tried following everything else. I think most of it worked, i've gotten a .unlock file, but when i try to flash it to my device it just says <waiting for device>.
I hope you guys can help me out here...:angel:
HybridLion said:
Hello,
I'm trying to unlock the bootloader of my kindle fire Apollo, i'm using this tutorial Link., i'm getting most of it, but this i just dont understand:
I've just put the cuberHDX file in my python27 directory, and tried following everything else. I think most of it worked, i've gotten a .unlock file, but when i try to flash it to my device it just says <waiting for device>.
I hope you guys can help me out here...:angel:
Click to expand...
Click to collapse
Try these drivers. Might require reboot and/or dis- and re-connection of the HDX. Worked for me right away though.
Cl4ncy said:
Try these drivers. Might require reboot and/or dis- and re-connection of the HDX. Worked for me right away though.
Click to expand...
Click to collapse
THANK YOU!
This is a giant leap forward, now my device actually shows up in fastboot. But when i try to flash the .unlock file it says:
{
"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"
}
any idea's?
btw my kindle says: "getvarartition-type:unlock...Ok."
You must change dir (cd) to your ADB Directory, enter cd\adb and then the fastboot command.
Alternatively you can try to add the path of your ADB Directory to the .unlock file, e.g. c:\adb\0x155.....unlock.
Cl4ncy said:
You must change dir (cd) to your ADB Directory, enter cd\adb and then the fastboot command.
Alternatively you can try to add the path of your ADB Directory to the .unlock file, e.g. c:\adb\0x155.....unlock.
Click to expand...
Click to collapse
You Sir are amazing!
Now i'm going to have to install some sort of recovery... i was thinking of using this one: http://forum.xda-developers.com/kin...ecovery-twrp-recovery-2-8-1-0-apollo-t2991155, are there any alternatives or better options?
TWRP is the best you can get for the HDX.
HybridLion said:
You Sir are amazing!
Now i'm going to have to install some sort of recovery... i was thinking of using this one: http://forum.xda-developers.com/kin...ecovery-twrp-recovery-2-8-1-0-apollo-t2991155, are there any alternatives or better options?
Click to expand...
Click to collapse
You can only install a recovery that has been customized for your device type (HDX Apollo or Thor). Any other will either leave you with a non-functioning recovery (best case) or a useless brick (more likely). Word to the wise: don't deviate from the script when messing with an HDX. Hard to tame and nearly impossible to recover. Standard bag of 'android' recovery tricks (eg: factory cables, fastboot, etc) won't work with this device.
Hi Guys,
after a lot of struggle I managed to get FireOS Stock back on my HDX 7" 2013.
The speakers on my device don't work anymore and I want to use the warranty on amazon.
Therefore I should remove TWRP I guess...
I got Safestrap 3.75 (TWRP v2.7.1.0) on my device and already tried the following threads for removing TWRP and having Stock FireOS on the device:
http://forum.xda-developers.com/showthread.php?t=1638452 (2nd Post starting with "Reverting to stock software")
-> still being able to access TWRP
http://forum.xda-developers.com/showthread.php?t=2409435
-> still being able to access TWRP
Also I read this: "If you Kindle Fire is booting directly into TWRP, without you doing it manually, then your device is stuck in fastboot mode.
You can issue the following commands through adb on your computer:
adb shell su -c "idme bootmode 4000"
adb reboot"
-> I am only able to use adb commands when I am booted into a ROM and not from TWRP. Is that normal? When I issue the command (booted into FireOS) I get: "C:\adb-tools>adb shell su -c "idme bootmode 4000"
/system/bin/sh: su: not found"
And when trying "adb shell idme bootmode 4000" I get: "Could not open /dev/block/mmcblk0boot0!
Can't read the idme."
Although I believe these bootmode changes won't remove TWRP... My idea was just to use this so Amazon Support won't notice the changes made to the device...
Can anyone tell me how I remove TWRP and stay with my currently working FireOS (with broken speakers...)
Thanks a lot!
~finchson
If you have Safestrap you do NOT have the "real" TWRP!
Safestrap should be removed by un-installing it's app via Safestrap itself. Be sure to remove secondary slots before un-installation, if you created any.
Cl4ncy said:
If you have Safestrap you do NOT have the "real" TWRP!
Safestrap should be removed by un-installing it's app via Safestrap itself.
Click to expand...
Click to collapse
But I don't have Safestrap (the App) installed anymore. Currently there is only FireOS Stock ROM active and I don't even know if that one is rooted...
{
"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"
}
The Safestrap I used seems to be unavailable and the links are not working anymore: http://forum.xda-developers.com/showthread.php?t=2556677 and http://blog.hash-of-codes.com/downloads/safestrap/
I was lucky enough to find the apk here: http://www.mechno.com/goog/
But I no longer got Root on the Stock ROM and therefore cant remove Safestrap.
Luckily towelroot worked just fine so my Stock ROM was rooted and I could remove Safestrap.
I now rebooted the device and everything seems to be ok.
My warranty device already is on it's way.
Thanks for the tip Cl4ncy
in order to install prerooted marshmallow i had downloaded and flashed this d6503 23.0.1.A.3.12 file.its a kitkat version.i can't find any thread for rooting and installing recovery for this particular version.can anyone help me to root and install recovery on this android version.thanks in advance.
jamshadebay said:
in order to install prerooted marshmallow i had downloaded and flashed this d6503 23.0.1.A.3.12 file.its a kitkat version.i can't find any thread for rooting and installing recovery for this particular version.can anyone help me to root and install recovery on this android version.thanks in advance.
Click to expand...
Click to collapse
You are going to have to get an earlier version. The easiest to do are the 17.x versions. Someone more knowledgeable than me might be able to help you with that version.
Sent from my SGP311 using XDA Free mobile app
You don't need a 17.x version. Any kitkat is fine.
To root, download towelroot or kingroot and click the button.
Once rooted, to install twrp just dd Install Method (Requires Root):
Run the following commands via adb shell or a terminal emulator app:
su
dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Towelroot: https://towelroot.com/
Twrp: https://twrp.me/devices/sonyxperiaz2.html
Did you search at all?
Sent from my D6503 using Tapatalk
thanks,can you explain in detail.i didn't unlocked boot loader.i have little doubts about twrp installation.how to run the command adb shell or a terminal emulator app.i am a beginer.i have no idea about terminal emulator app or adb shell.please explain in detail.
You can use adb or terminal Emulator app (I just use terminal emulator app (rom toolbox)). A terminal emulator just gives you access to a command line on you phone.
{
"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"
}
Su gives you root accessing the command line.
Dd is a command that allows you to copy files and write to different areas of Linux that users generally can't access. About of info about dd http://superuser.com/questions/456132/what-exactly-does-the-dd-command-do
FOTAKernel is not your normal kernel. It doesn't require an unlocked boatloads. The FOTA partition is used for OTA updates. Once you root your phone you can't use OTA updated anyway so they flash recovery into this partition.
Sent from my D6503 using Tapatalk
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.