I have managed to boot to rEFInd on my Toshiba Encore in preparation for booting Ubuntu from a microSD card natively. I have not written up a guide yet from my notes because I don't think there will be much demand for this here on XDA. If enough people want to do this, I will turn this post into a guide. This boots directly from the UEFI partition with no USB stick needed. You DO need a USB stick to do the actual install.
Toshiba Encore booting to rEFInd: http://postimg.org/image/4lx3mnxzr/
Toshiba Encore booting to Grub2: http://postimg.org/image/p3rgtpqkp/
__________________________________________________________________________
Installing Ubuntu 14.10 to a microSD card on the Toshiba Encore:
Note: There are many problems right now with Ubuntu on the Encore. Touchscreen driver is broken as of kernel version 3.16. It's some kind of regression bug in the atmel-maxtouch driver(here is a program to debug our touchscreen: https://github.com/atmel-maxtouch/obp-utils).
You will need to prepare with:
A USB stick to do the install
Ubuntu 14.10 64 bit ISO(Daily build) http://cdimage.ubuntu.com/daily-live/current/
A microUSB OTG cable(if you use the StarTech cable mentioned below then you don't need this)
A high speed microSD card(Partitioned: 200MB FAT32 EFI partition, a large EXT4 partition, and a swap partition). I used this(was $21 on sale) http://www.amazon.com/gp/product/B00IVPU894/ref=oh_aui_detailpage_o04_s00?ie=UTF8&psc=1
A Linux box to compile the latest versions of a few programs used to boot into Grub2 and Ubuntu. I will post the compiled versions but you should compile them yourself for security reasons.
Read this to get an idea what's needed to get rEFInd installed: http://www.rodsbooks.com/refind/installing.html#windows (there are extra steps not listed there)
The install will go from the usb stick booted from rEFIind to the microSD card. The Samsung PRO I am using only does ~20MBps so I'm guessing that is a hardware limit. I did the install without a swap partition and Ubuntu was unusable after opening up 4 or more programs so I added a swap partition to the end of my microSD card.
Getting rEFInd booting:
Turn off Secure Boot in the Encore bios. It should be possible to boot Ubuntu from a USB stick without turning off Secure Boot but I doubt it will ever be possible to do from a microSD card because the Toshiba Encore has no option to boot from a microSD card in the bios boot options.
Get rEFInd here: http://www.rodsbooks.com/refind/getting.html
Run these commands in an elevated permissions Windows command shell:
powercfg /h off
manage-bde -status c: (checks bitlocker status)
powershell
PS C:\> Disable-BitLocker -MountPoint "C:"
manage-bde -status c: (after above command finishes, makes sure your disk is really decrypted.)
Then follow this: http://www.rodsbooks.com/refind/installing.html#windows
All the commands are explained on rodsbooks website except disabling Bitlocker. This is optional but if something goes wrong along the way, you might find Windows 8 encrypted and unbootable.
Note: The command: "bcdedit /set {bootmgr} path \EFI\refind\refind_x64.efi" to get rEFInd set as the default EFI boot program did not take the first time I did it. You might have to run that commend a few times rebooting each time until your tablet boots into rEFInd. Once it does, you will see a graphic to boot Windows 8. I suggest changing rEFInd to text mode so that you can use the VOL UP, VOL DOWN, and Windows button(as enter) to scroll through the boot options. Use "textonly" option in the rEFInd config file to set this: http://www.rodsbooks.com/refind/configfile.html#adjusting
Installing Ubuntu(bleeding edge) 14.10:
Touchscreen does not work yet so I will update this section when I get it working.
_________________________________________________________________________
If you want to have power to your tablet and USB OTG access at the same time, here is what you need(both Amazon prime eligible):
http://www.amazon.com/gp/product/B0047AALS0/ref=oh_aui_detailpage_o03_s00?ie=UTF8&psc=1
http://www.amazon.com/gp/product/B00KQES55M/ref=oh_aui_detailpage_o03_s00?ie=UTF8&psc=1 (Any usb gender bender like this will do...there are cheaper ones)
Attach the USB gender changer to the black end of the StarTech cable and the attach a USB hub to the other end of the gender changer. Plug the red end into a 2.1 amp USB power source and the microUSB end into the Encore. Now the tablet will say "plugged in, not charging". You can now attach any USB device to the hub and Windows or Linux with see them. The tablet will have power but the battery will not charge.
bads3ctor said:
I have managed to boot to rEFInd on my Toshiba Encore in preparation for booting Ubuntu from a microSD card natively. I have not written up a guide yet from my notes because I don't think there will be much demand for this here on XDA. If enough people want to do this, I will turn this post into a guide. This boots directly from the UEFI partition with no USB stick needed.
Toshiba Encore booting to rEFInd: http://postimg.org/image/4lx3mnxzr/
Toshiba Encore booting to Grub2: http://postimg.org/image/p3rgtpqkp/
Click to expand...
Click to collapse
Hi
I wanna boot ubuntu on my encore Can You write the instructions how to, step by step?
Nice, not sure how many others own this tablet, the Venue 8 Pro seems more popular. But I bought an Encore for the microHDMI so I would love to see a guide.
Thank You, I would love to see a guide also, I own a Toshiba encore 32gb
Touch working? Wifi?
Thanks for posting the guide though!
Touchscreen driver works but needs calibration
SebMKd said:
Touch working? Wifi?
Thanks for posting the guide though!
Click to expand...
Click to collapse
Touchscreen bug:
Code:
i2c_hid i2c-ATML1000:00: failed to retrieve report from device.
Supposed to be fixed in kernel version 3.16 but so far in Ubuntu 14.10(kernel 3.16.0-23) TS is still broken. Internal WIFI works with a few tweaks. I am using a USB Atheros WIFI device for now.
I am running Windoze 8 and every few weeks I update Ubuntu 14.10 to see if the touchscreen works. I used to hack away at bleeding kernels to fix bugs like this but I am just going to wait for the Linux kernel devs to fix the touchscreen driver.
Edit: Booted into Ubuntu 14.10 after updating to the newest kernel and:
dmesg | grep i2c-ATML
[ 8.053603] input: ATML1000:00 03EB:8C12 as /devices/platform/80860F41:05/i2c-5/i2c-ATML1000:00/0018:03EB:8C12.0005/input/input6
Touchscreen works but is badly calibrated and the Unity side bar refuses to appear when the mouse is pushed to the left side of the screen. Not a very good trade-off! On the bright side, the former useless USB keyboard windows key now brings up the Unity sidebar.
Code:
[email protected]:~$ xinput list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ MOSART Semi. 2.4G Wireless Mouse id=9 [slave pointer (2)]
⎜ ↳ ATML1000:00 03EB:8C12 id=10 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Video Bus id=6 [slave keyboard (3)]
↳ Logitech USB Keyboard id=7 [slave keyboard (3)]
↳ Logitech USB Keyboard id=8 [slave keyboard (3)]
↳ gpio-keys id=11 [slave keyboard (3)]
↳ gpio-keys id=12 [slave keyboard (3)]
[email protected]:~$ xinput list-props 10
Device 'ATML1000:00 03EB:8C12':
Device Enabled (130): 1
Coordinate Transformation Matrix (132): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
Device Accel Profile (253): 0
Device Accel Constant Deceleration (254): 1.000000
Device Accel Adaptive Deceleration (255): 1.000000
Device Accel Velocity Scaling (256): 10.000000
Device Product ID (248): 1003, 35858
Device Node (249): "/dev/input/event5"
Evdev Axis Inversion (257): 0, 0
Evdev Axis Calibration (258): 1271, 1282, 3196, 3115
Evdev Axes Swap (259): 1
Axis Labels (260): "Abs MT Position X" (280), "Abs MT Position Y" (281), "None" (0), "None" (0)
Button Labels (267): "Button Unknown" (262), "Button Unknown" (262), "Button Unknown" (262), "Button Wheel Up" (136), "Button Wheel Down" (137)
Evdev Scrolling Distance (261): 0, 0, 0
Evdev Middle Button Emulation (268): 0
Evdev Middle Button Timeout (269): 50
Evdev Third Button Emulation (270): 0
Evdev Third Button Emulation Timeout (271): 1000
Evdev Third Button Emulation Button (272): 3
Evdev Third Button Emulation Threshold (273): 20
Evdev Wheel Emulation (274): 0
Evdev Wheel Emulation Axes (275): 0, 0, 4, 5
Evdev Wheel Emulation Inertia (276): 10
Evdev Wheel Emulation Timeout (277): 200
Evdev Wheel Emulation Button (278): 4
Evdev Drag Lock Buttons (279): 0
Edit2: Here is the problem....the coordinates for calibration are off because the tablet is attached to an external monitor:
Code:
[email protected]:~$ xrandr
Screen 0: minimum 8 x 8, current 3200 x 1080, maximum 32767 x 32767
HDMI1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 983mm x 576mm
1920x1080 60.0*+ 50.0 59.9 30.0 25.0 24.0 30.0 24.0
1920x1080i 60.1 50.0 60.0
1600x900 60.0
1280x1024 60.0
1360x768 60.0
1280x720 60.0 50.0 59.9
1440x576i 50.1
1024x768 60.0
1440x480i 60.1 60.1
800x600 60.3
720x576 50.0
720x480 60.0 59.9
640x480 60.0 59.9
DP1 disconnected (normal left inverted right x axis y axis)
DSI1 connected 1280x800+1920+0 right (normal left inverted right x axis y axis) 0mm x 0mm
800x1280 60.0*+
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
very interesting. It's what I need :good:
Any more news on this?
I managed to install Refind. Also, I managed to install ubuntu on sdcard. But in Refind not appears Ubuntu. How I can edit Refind to search the OS on sdcard?
Thanks!!
PainToad said:
Any more news on this?
Click to expand...
Click to collapse
Sorry for not getting back earlier on this but I wanted to exhaust all options before giving up on running Ubuntu on this tablet. The deal killer turns out to be the MicroSD card bandwidth. From what I can tell from the tests I have done while running Ubuntu from the MicroSD card, the BIOS is set to run the SD bus in DDR25 mode with no option to set it to DDR50 mode. DDR25 mode maxes out at about 18 MB/Sec and this is causing Ubuntu to lockup when disk I/O gets saturated.
With no option in the BIOS to set the SD bus to DDR50 mode, it is effectively a hardware limitation preventing Ubuntu from running properly.
bads3ctor said:
If you want to have power to your tablet and USB OTG access at the same time, here is what you need(both Amazon prime eligible):
http://www.amazon.com/gp/product/B0047AALS0/ref=oh_aui_detailpage_o03_s00?ie=UTF8&psc=1
http://www.amazon.com/gp/product/B00KQES55M/ref=oh_aui_detailpage_o03_s00?ie=UTF8&psc=1 (Any usb gender bender like this will do...there are cheaper ones)
Attach the USB gender changer to the black end of the StarTech cable and the attach a USB hub to the other end of the gender changer. Plug the red end into a 2.1 amp USB power source and the microUSB end into the Encore. Now the tablet will say "plugged in, not charging". You can now attach any USB device to the hub and Windows or Linux with see them. The tablet will have power but the battery will not charge.
Click to expand...
Click to collapse
I have a question. This method won't be charging my tablet, so my battery won't be destroyed?
BTW another question. Why card reader in this tablet is that slow? I have sandisk extreme micro sd (64MB/s write - ~ 60MB/s in my PC card reader) but reader in toshiba can only read/write ~26MB/s. I thought that this card will be great for my tablet, but now I fell like I wasted my money. I could better buy standard class 10 micro sd card...
rascal0pl said:
I have a question. This method won't be charging my tablet, so my battery won't be destroyed?
Click to expand...
Click to collapse
The tablet will receive a charge but the battery will not be charged. If your battery is at 100% then it will stay at 100%.
rascal0pl said:
BTW another question. Why card reader in this tablet is that slow? I have sandisk extreme micro sd (64MB/s write - ~ 60MB/s in my PC card reader) but reader in toshiba can only read/write ~26MB/s. I thought that this card will be great for my tablet, but now I fell like I wasted my money. I could better buy standard class 10 micro sd card...
Click to expand...
Click to collapse
It is an internal firmware limitation. There is supposed to be a BIOS setting to set the SD slot to a higher bandwidth level but this tablet does not have that option in the BIOS.
Card Reader of Bay Trail tablets is broken
The Card Reader of Bay Trail tablets is slow because is broken, no linux boot and is a read-only device with stock linuxes. You can patch the kernel and install some boot stuff in new partitions of Windows disk, but you can't boot from microSD. I also installed Android x86 and run fast, Android 4 and 6 stable versions, but I couldn't activate sound nor battery status. At least for my research, until today, if you have the 32 GB disk is very difficult you can play with dual boot, Windows is slow and wastes the hard disk, tablet mode of windows has no attractive (while Android is near perfection) and desktop mode is not friendly for touch-screen use, but for now it is stable and all the other tablet's devices works (touchscreen, GPS, Bluetooth, cameras, sensors, miracast), the battery management in this Atom environment has issues with linux and under Windows this x86 system doesn't seem so far away from ARM efficiency. I installed many GPL portable Windows applications in a minimal disk space, so for now linux and Android are worse for this tablet that seemed created for a Microsoft's skinhead.
UEFI boot
I forgot I have a 10 inches version of this tablet, 32 GB, Windows 10 32 bits upgrade (first upgrade) and BIOS 2.0
UEFI multi-boot is not so difficult with: rEFInd, easyUEFI Windows application (because Windows changes boot order), linux's Unetbootin for USB boot, bootia32.efi archive for some linux's installations (Ubuntu-gnome 16.04.1 64 bits requires at least 7-10 GB and swap, may be 32 bits is a bit better because it's less RAM hunger), ... before tests, you have to disable Windows's Bitlocker encryption (AES-128 Windows disk software encryption for this model of the Atom processor, I think without hardware assistance, that it's seamless for the user because UEFI includes shared key, if disk key is deleted Microsoft online user account stores a large password), secure boot, fast boot, windows session identification (Microsoft online authentication sometimes locks session start, probably cause some autocheck of a efi boot manipulation... may be was "default_selection" option of rEFInd for booting last selected OS), backup efi boot partition (copy the files after mount partition)... then I gparted the Windows disk form USB (with no data loss).
And if someone can the microSD boot, Raspberry Pi community recommends Samsung EVO+ 32 GB, for about 10 $/€ (be warned about scam versions), with the best by far random IO, far less from 20 MB/s, but may be important for linux, although I don't know if max random IO of the card reader had been reduced too (most probably yes... and a lot).
Another chance is wubi EFI, a Ubuntu Windows installer that now supports UEFI 32 bits (the non approved by free-software community secure boot only with UEFI 64 bits), this install linux in a big file (resizable) of a NTFS Windows disk (again microSD doesn't boot, it requires a rEFInd's Card Reader firmware and is not available) and linux runs in loop mode inside this file. I installed Ubuntu-gnome 64 bits and 32 bits (in this case the installer requires a command-line option). UEFI32 too requires EasyUEFI and secure boot and bitlocker disabled, I utilized a USB wifi stick (TL-WN722N) until internal wifi was configured... I found lots of issues, including slow internal-wifi, soundcard, battery status, processor stepping and hangs, and other users's solutions for different tablets have not always worked... then no usability research here. Anyway, wubi is not the best way to install linux, although it works and it's easy, and Windows complain less.
A last possibility for linux could be VirtualBox 32 bits, this supports microSD use and Atom processor includes hardware assistance supporting even linux 64 bits. Virtualize linux on this tablet is very slow and touchscreen is a pain.
After some time I returned the tablet to its original state with no data loss*, USB boot still there or the install in a fast (if well chosen) microUSB 3.0 stick or microSD-adapter... but no charger without the use of a less portable, and manipulation disconnections, cable adapter. I utilized a cheap "octopussy" cable from China (3 USB 2.0+ microUSB for charge... 3-4 $/€ or less), but this tablet is incompatible for simultaneous operation (USB OTG+charge), it don't charge while USB use and only I can do slow charge with a tricky: connect with charge mode, change to OTG mode and connect USB devices (warning: some Amazon's users report issues or damages in other tablets).
*bitlocker key changed with a new online password stored for recovery, and Toshiba recovery (Bios option) was broken, may be caused by gparted or some UEFI boot application or some of the installed OS, who knows... normal fixes solutions don't work, although windows own recovery partition worked. Toshiba utilizes a particular EFI directory and Windows doesn't repair it, I copied Toshiba BCD backed up file or, in case it doesn't work, BCD file from Windows recovery boot directory (may be a normal fixboot is required first).
Bug issues under Windows 10 update
After some time of use this tablet suffers issues, cause of its Bay Trail buggy platform, under Windows 8.1 and 10 (worse): Wifi disconnections and poor speed, laggy applications and touchscreen sometimes is unresponsive, miracast disconnections and choppy sound, although the whole system doesn´t hang. I did try linux last updates from http://linuxiumcomau.blogspot.com.es/ and now most work better (July 2017), probably in a short time I will uninstall Windows 10.
I managed to get into developer mode on my new NGP, there's no more "build number" as I've seen in several blog posts with the latest update you click on the Nook icon on the About page it takes you to Developer mode. I've been able to install a few apps, but here's what I'd like to do.
I'd like to plug in a USB keyboard and use it to SSH into another machine through my WiFi hotspot to do some HTML/JS/CSS text editing while I'm outdoors (at the pool, the park, etc) as my other laptops/tablets aren't visible at all outdoors with glare. This would be a nice portable solution if I could get it to work, even editing locally on the device through some editor and sending via SFTP would be just fine.
However, I can get my USB OTG cable and USB keyboard to work on my Samsung J3 phone just fine, but not on my NGP it does nothing when plugged in, keyboard caps lock doesn't activate. Is there a way to get it to work, and does it require rooting the NGP? I haven't rooted the device yet.
JohnnyFriendly said:
However, I can get my USB OTG cable and USB keyboard to work on my Samsung J3 phone just fine, but not on my NGP it does nothing when plugged in, keyboard caps lock doesn't activate. Is there a way to get it to work, and does it require rooting the NGP? I haven't rooted the device yet.
Click to expand...
Click to collapse
As a workaround I put a VNC client on it so I can access my other devices and do the typing from there, that way I can use my RPI3 as the system with a keyboard on battery power and do some Python (Django)/NodeJS/ReactJS from the NGP using it as a monitor outdoors, but if I issue the following commands via adb to rotate into landscape mode I lose input on the NGP and have to reboot:
adb shell settings put system accelerometer_rotation 0
adb shell settings put system user_rotation 1
Any ideas?
I believe I looked at this once.
At least one of the problems is that the ID pin on the micro USB connector is not connected through to the processor.
B&N has never shown any interest in putting Bluetooth in a Nook.
We'll have to see if the latest "Nook Glowlight 3" will have either OTG or BT.
It is happened that I needed to obtain UART access on Galaxy S7. I tried Google search, apparently. I have found several threads on XDA dedicated to this question; however, they all are a bit outdated (2012-2013 years), containing information about an old loader.
Moreover, they are describing information in a very limited way, mostly telling the reader only about how to use UART with loader and do not going deeper into details.
Finally, despired to find any valuable piece of information, I performed my own research and here I will structure all the information I gathered and discovered.
To begin with, there is an USB multiplexing unit between USB-connector and USB-controller, aimed to measure the value of resistance between ID and GND, and setup a USB controller mode in dependance of that. That is not a new thing: the same way works, for instance, USB OTG.
But there exist other work modes which are hidden from the normal user. These work modes are utilized by a special device which is used by Samsung engineers. One can order a device like this on Ebay, but I do not se any reason for. Source codes of the mobile phone kernel are available for download and include a multiplexing unit driver.
The S7's MUIC name is MAX77854, which comes with lack of documentation, but we have a driver, which, obviously, has source codes which are available here: drivers/muic/max77854-muic.c. Going through the sources, I found an actual table of the resistance values and work modes for this device:
OTG =*GND
MHL = 1K
VZW_ACC = 28.7K
VZW_INCOMPATIBLE = 34K
RDU_TA = 40.2K
HMT = 49.9K
AUDIODOCK = 64.9K
USB_LANHUB = 80.07K
CHARGING_CABLE = 102K
GAMEPAD = 121K
TYPE1_CHG = 200K
JIG_USB_OFF = 255K
JIG_USB_ON = 301K
DESKDOCK = 365K
TYPE2_CHG = 442K
JIG_UART_OFF = 523K
JIG_UART_ON = 619K
TA = OPEN
USB = OPEN
CDP = OPEN
UNDEFINED_CHARGING =*UNDEFINED
ATTACHED_DEV_NUM = NUM
I have no idea what the listed most modes mean, but I see one very interesting mode JIG_UART_ON, which has been researched a bit and which allowes us to connect a device through USB-UART adapter and get a SBOOT boot log. I was inspired by an article about SBOOT where a guy researched the possibility of hijacking the boot loader and discovered a way how to change boot parameters including kernel boot parameters.
First of all, we need to build a JIG(UART) adapter. For that purpose we need to have any USB-UART adapter (I used FT232) and resistance unit for 619kOm (I have purchased one for 620kOm in the shop next to my house). Then we need to get them together as on the scheme:
{
"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 newly created adapter we need to plug in to the computer and wait for a new device name (on my system it set as /dev/ttyUSB0), then connect to this device through a terminal application (I used minicom).
Code:
sudo minicom -D /dev/ttyUSB0
I am not sure what settings will you have for your terminal application, that's why I highly recommend you to set up your port settings and disable the hardware flow control setting. After all things done, you have to plug a mobile phone to this adapter and turn it on using the key combo: Vol-(Volume Down) + Power.
As symbols on the screen start displaying, you need to quickly press Enter key as minimum as 3 times until we see the command line. Congratulations! We are in the SBOOT console! Run the following command:
Code:
setenv CMDLINE console=ttySAC4,115200 loglevel=4
saveenv
After its execution complete, press and hold Vol-(Volume Down) (if the above mentioned key has not been pressed, SBOOT will not print anything in the console) and enter the command into the SBOOT console:
Code:
reset
The device will reboot and we will see a SBOOT boot log and a part of kernel boot log. Why only a part? Because as of my research, a small bug is located in the kernel sources, I give you a patch for it below:
Code:
diff --git a/drivers/muic/universal/muic_apis.c b/drivers/muic/universal/muic_apis.c
index 342bc51..5af193c 100755
--- a/drivers/muic/universal/muic_apis.c
+++ b/drivers/muic/universal/muic_apis.c
@@ -796,7 +796,7 @@ int detach_jig_uart_boot_off(muic_data_t *pmuic)
*/
int attach_jig_uart_boot_on(muic_data_t *pmuic, muic_attached_dev_t new_dev)
{
- int com_index = COM_OPEN;
+ int com_index = COM_UART_AP;
int ret = 0;
pr_info("%s:%s JIG UART BOOT-ON(0x%x)\n",
After it has been applied, we will be able to see all the kernel boot log; however, we will break the GSM component of the mobile device. This UART port is used be system to communicate with a GSM modem. At this stage we can use it for kernel debugging, but it wasn't our goal.
Now let's get mobile device console access through UART, using the information received above.
To achieve this, we have to install TWRP on our device and using it, get root access. Then we have to install busibox, which includes getty application and that is the only its difference from the original. Afterwards, we boot our device, install a terminal emulator and switch the device to the airplane mode.
Now start the emulator and enter the following commands:
Code:
su
echo 1 > /sys/devices/virtual/sec/switch/uart_en
echo AP > /sys/devices/virtual/sec/switch/uart_sel #на этом этапе должен появиться лог ядра
su root -c "getty -n -L -l /system/bin/sh 115200 ttySAC4 vt102"
Useful links:
xda old forum thread
SBOOT hacking
and you connected the 3.3v line -why- exactly? the samsung won't power your max232 (if it does, like with usb otg, it will supply 5v, not 3.3 or usb converter and 3.3v won't power the samsung. just txd rxd and gnd is enough. also the 301ohm one always turns on the phone and boots to factory 'odin' mode for mass deployment of new firmware. (normal usb tho). when using them with the rs232 resistor value they'll output some crap at 115k2 during the bootloader.
cb3rob said:
and you connected the 3.3v line -why- exactly? the samsung won't power your max232 (if it does, like with usb otg, it will supply 5v, not 3.3 or usb converter and 3.3v won't power the samsung. just txd rxd and gnd is enough. also the 301ohm one always turns on the phone and boots to factory 'odin' mode for mass deployment of new firmware. (normal usb tho). when using them with the rs232 resistor value they'll output some crap at 115k2 during the bootloader.
Click to expand...
Click to collapse
I connected 3.3v because it normal to connect this line and it works. Probably without this line it will work. Everything that I write was tested by me. If you see crap during bootloader check minicom config.
lSDriim said:
I connected 3.3v because it normal to connect this line and it works, ft232 won't power Samsung because it's not working like that. Everything that I write was tested by me. If you see crap during bootloader check minicom config.
Click to expand...
Click to collapse
connecting a 3.3v line to a 5v line (regardless of which way the power goes) doesn't seem very practical for long time use. at least for 'factory odin' mode the phone can be powered from the 5v usb side during the firmware deployment (as usually the batteries aren't all too full when we pull them out of the box anyway
nah not crap as in frame errors and random bytes crap. crap as in some status messages but nothing useful. could not find any way to stop it and drop into a machine language monitor, get any type of prompt, inject code to be booted, or anything else that would be useful from there. it literally just seems to be some debug messages of the bootloader(s)
1650 pages of leaked "samsung confidential" datasheet but finding how to actually -use- the things for anything 'not android' (as in registers, memory map instruction set)? nah. it's more work to figure out how samsung screwed things up and get rid of all their 'monopoly' code which they try to pass off as 'security' than to just design a new phone and order it into production
anyway, the age of the post of the resistor values doesn't matter. the values are the same for every samsung device i've tried (we only use s7's but i got boxes full of other models, including very old ones. the resistor cables work exactly the same way all of those - although the 'magic bytes' for samsungs 'modified' simg format are different for each model, as are obviously the partition sizes. and really old ones seem to use a different and incompatible version of the odin protocol alltogether). haven't tried it with those usb-c connectors on those j5/a5 or whatever those things are called, as i don't have usb-c male pcb connectors in stock, but most likely there too. it's also not very picky on the actual resistor value. 300 ohm instead of 301 is fine. as long as it's 'close enough' it'll go to the desired mode. (as their specified values are weird, you can't buy 301 ohm resistors (pretty much all of them do uart mode and turn on+odin factory mode)
cb3rob said:
connecting a 3.3v line to a 5v line (regardless of which way the power goes) doesn't seem very practical for long time use. at least for 'factory odin' mode the phone can be powered from the 5v usb side during the firmware deployment (as usually the batteries aren't all too full when we pull them out of the box anyway
nah not crap as in frame errors and random bytes crap. crap as in some status messages but nothing useful. could not find any way to stop it and drop into a machine language monitor, get any type of prompt, inject code to be booted, or anything else that would be useful from there. it literally just seems to be some debug messages of the bootloader(s)
1650 pages of leaked "samsung confidential" datasheet but finding how to actually -use- the things for anything 'not android' (as in registers, memory map instruction set)? nah. it's more work to figure out how samsung screwed things up and get rid of all their 'monopoly' code which they try to pass off as 'security' than to just design a new phone and order it into production
anyway, the age of the post of the resistor values doesn't matter. the values are the same for every samsung device i've tried (we only use s7's but i got boxes full of other models, including very old ones. the resistor cables work exactly the same way all of those - although the 'magic bytes' for samsungs 'modified' simg format are different for each model, as are obviously the partition sizes. and really old ones seem to use a different and incompatible version of the odin protocol alltogether). haven't tried it with those usb-c connectors on those j5/a5 or whatever those things are called, as i don't have usb-c male pcb connectors in stock, but most likely there too. it's also not very picky on the actual resistor value. 300 ohm instead of 301 is fine. as long as it's 'close enough' it'll go to the desired mode. (as their specified values are weird, you can't buy 301 ohm resistors (pretty much all of them do uart mode and turn on+odin factory mode)
Click to expand...
Click to collapse
I write from my phone, because I am on vacation now and can't write long messages(too lazy now). But in this guide I write how to get bootloader prompt and change kernel start command and you can change kernel and boot anything you want... I already do this to boot up normal linux. In links there are link to guy that tried to hack sboot, may be he can help you.
We've had USB host mode working on the NST using a bit of poking with my UsbMode.apk
I just figured out how to get it working on the Glow2 (and it will probably work on the Glow3, though I haven't tried it yet) and it works fine on the Glow3 also.
USB host mode means that you can connect USB accessories like keyboards, audio, flash drives.
The simple stuff (like keyboards or an HID device) works easily, some of the other stuff might need work.
I quickly checked a flash drive and the drivers loaded, so at most it's a question of getting it mounted.
The current downside is that we can't get power out of the Glows.
That means that you need to use a back-powering hub.
You still need an OTG adapter (or at least a reversing cable) to connect the Glow to the input port of the hub.
To see this for yourself is simple if you have busybox installed.
This turns host mode on:
Code:
# busybox devmem 0x20e03d0 32 0x130b1
This turns host mode off:
Code:
# busybox devmem 0x20e03d0 32 0x1b0b1
You can use my UsbMode.apk (in the signature) to see the USB tree, although I haven't added the above poking to the app yet.
I made a daemon that allows playing with this pin padctrl without you having to lower the protection on /dev/mem
I added the option to a private build of UsbMode and it works fine switching into usb host mode.
Unfortunately, even though the bit twiddling back to peripheral mode works just fine, the USB gadget stuff is screwed up.
So, in short, if you wanted to use this (not yet released), you could dock and push a button to go to host mode, but you'd need to reboot to get it working on peripheral and ADB.