is it possible to use On The Go cable "OTG cable" with our beloved Galaxy Wonder?
{
"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"
}
Aw mawi gawdh ! Not this sh*t again
Kindest sire next time use SEARCH button !
Sent from a hybrid phablet !
Samsung Galaxy W does NOT support USB OTG, period!
just curious,is it a hardware issue or software issue?
vetusa2 said:
just curious,is it a hardware issue or software issue?
Click to expand...
Click to collapse
Hardware.
-- Sent from a GT-I8150 running ICS perfectly well. F'U, Sams#!t --
No the SGW doesn't have USB OTG, it will never have USB OTG and even if it did I don't think anyone here except 2 or 3 people would even care since its a pretty useless feature.
pepoluan said:
Hardware.
-- Sent from a GT-I8150 running ICS perfectly well. F'U, Sams#!t --
Click to expand...
Click to collapse
galaxy w has usb host support having chip msm 8255..and the software support(driver)is not enabled and evryone is right it doesnot have usb otg bt it has host support..it can mount usb storage devices if enabled through kernel with external power requirement!
farisnanosoft said:
galaxy w has usb host support having chip msm 8255..and the software support(driver)is not enabled and evryone is right it doesnot have usb otg bt it has host support..it can mount usb storage devices if enabled through kernel with external power requirement!
Click to expand...
Click to collapse
MSM8255 is *not* enough for USB OTG support.
You need the USB OTG Transceiver to perform as USB Root Controller.
Here, let me show you an abridged documentation on how USB OTG works:
http://www.maximintegrated.com/app-notes/index.mvp/id/1822
-- Sent from a GT-I8150 running ICS perfectly well. F'U, Sams#!t --
pepoluan said:
MSM8255 is *not* enough for USB OTG support.
You need the USB OTG Transceiver to perform as USB Root Controller.
Here, let me show you an abridged documentation on how USB
-- Sent from a GT-I8150 running ICS perfectly well. F'U, Sams#!t --
Click to expand...
Click to collapse
read carefully..i said about usb host support not usb otg!
you can see here msm 8255 supporting usb host
developer.qualcomm.com/sites/default/files/snapdragon-specs.pdf
anyway nice post about usb otg wrkng..thnks!
farisnanosoft said:
read carefully..i said about usb host support not usb otg!
you can see here msm 8255 supporting usb host
developer.qualcomm.com/sites/default/files/snapdragon-specs.pdf
Click to expand...
Click to collapse
And *you* should read carefully the link I give.
USB OTG is just a catchy name to denote a device that can act as a USB Peripheral *and* USB Host (of course, not at the same time) and how it is supposed to do such transformation magic.
Here, I'll quote for you:
OTG introduces the dual-role device (DRD), capable of functioning as either host or peripheral.
Click to expand...
Click to collapse
right out of the first paragraph of the article.
-- Sent from a GT-I8150 running ICS perfectly well. F'U, Sams#!t --
pepoluan said:
And *you* should read carefully the link I give.
USB OTG is just a catchy name to denote a device that can act as a USB Peripheral *and* USB Host (of course, not at the same time).
-- Sent from a GT-I8150 running ICS perfectly well. F'U, Sams#!t --
Click to expand...
Click to collapse
so why does xperia ray and galaxy mini supports usb devices..xperia ray do have msm 8255 and galaxy mini hav msm7227??
farisnanosoft said:
so why does xperia ray and galaxy mini supports usb devices..xperia ray do have msm 8255 and galaxy mini hav msm7227??
Click to expand...
Click to collapse
They are equipped with USB OTG Transceiver, which the W doesn't have.
Why doesn't the W have USB OTG Transceiver? I don't know; ask Samsung.
-- Sent from a GT-I8150 running ICS perfectly well. F'U, Sams#!t --
pepoluan said:
They are equipped with USB OTG Transceiver, which the W doesn't have.
Why doesn't the W have USB OTG Transceiver? I don't know; ask Samsung.
-- Sent from a GT-I8150 running ICS perfectly well. F'U, Sams#!t --
Click to expand...
Click to collapse
mini dnt hav otg capability..both galaxy w and mini supports usb 2.0 hs host or peripheral...read this doc
https://developer.qualcomm.com/sites/default/files/snapdragon-specs.pdf
i jst wnt to knw about the things that are present and not the one that doesnot exist...thnks for your kind and valuable reply!
farisnanosoft said:
mini dnt hav otg capability..both galaxy w and mini supports usb 2.0 hs host or peripheral...read this doc
https://developer.qualcomm.com/sites/default/files/snapdragon-specs.pdf
i jst wnt to knw about the things that are present and not the one that doesnot exist...thnks for your kind and valuable reply!
Click to expand...
Click to collapse
"Peripheral or Host" *is* USB OTG.
Before USB OTG Supplement was released, a USB Device can only act as Host *or* Peripheral, permanently.
After USB OTG Supplement is released, we now have an additional class of device called 'DRD' (Dual Role Devices) that can act as Host *and* Peripheral (but not at the same time).
To change MSM8255 into Host Mode requires a suitable driver.
BUT
the pinouts are completely wrong. Other USB Devices will never ever detect the W as a Host device.
-- Sent from a GT-I8150 running ICS perfectly well. F'U, Sams#!t --
pepoluan said:
"Peripheral or Host" *is* USB OTG.
Before USB OTG Supplement was released, a USB Device can only act as Host *or* Peripheral, permanently.
After USB OTG Supplement is released, we now have an additional class of device called 'DRD' (Dual Role Devices) that can act as Host *and* Peripheral (but not at the same time).
To change MSM8255 into Host Mode requires a suitable driver.
BUT
the pinouts are completely wrong. Other USB Devices will never ever detect the W as a Host device.
-- Sent from a GT-I8150 running ICS perfectly well. F'U, Sams#!t --
Click to expand...
Click to collapse
thats what i said first..to enable host mode, driver is needed in kernal !..by pinout do you mean microusb pinout?
farisnanosoft said:
thats what i said first..to enable host mode, driver is needed in kernal !..by pinout do you mean microusb pinout?
Click to expand...
Click to collapse
That and all necessities of signaling (electrically) to other device that the W is now a Host.
The 'wiring' (maybe that's the more accurate term) is just plain wrong; pins that should be shunted to ground using a 1500 ohms resistor... don't get shunted. Signals that should have a certain polarity is inverted.
So, enabling Host Mode is USELESS.
Why would anyone develop something that will be USELESS?
-- Sent from a GT-I8150 running ICS perfectly well. F'U, Sams#!t --
farisnanosoft said:
mini dnt hav otg capability..both galaxy w and mini supports usb 2.0 hs host or peripheral...read this doc
https://developer.qualcomm.com/sites/default/files/snapdragon-specs.pdf
!
Click to expand...
Click to collapse
Yeh, and that doc also states that the 8255 supports 12MP camera and Bluetooth 4.0 - but the Galaxy W doesn't have those either!!!
hundred_miles_high said:
Yeh, and that doc also states that the 8255 supports 12MP camera and Bluetooth 4.0 - but the Galaxy W doesn't have those either!!!
Click to expand...
Click to collapse
the doc says chipset supports cam upto 12 and w has 5mp and those are external but host controller is inside the chipset!
farisnanosoft said:
the doc says chipset supports cam upto 12 and w has 5mp and those are external but host controller is inside the chipset!
Click to expand...
Click to collapse
Look, if you (or anyone) wants to develop a driver to flip the MSM8255 to Host Mode, no one will prevent you/him/her from doing it.
However, all drivers *must* be tested.
Now, since the W lacks the proper wiring ... how the heck can a developer test if the driver works or not?
And a slight correction: the USB component in the MSM8255 is *not* a controller; it's a microprocessor able to process the Host-side protocols. The controller is the combination of microprocessor + transceiver... and the W has a peripheral-only transceiver, not a switchable transceiver.
Please, READ the following article in its entirety: http://www.maximintegrated.com/app-notes/index.mvp/id/1822
Let me quote the conclusion of the article:
Three additions make the transceiver OTG compatible:
Switchable pull-up and pull-down resistors on D+/D- to allow peripheral or host functionality.
Circuitry to monitor and supply 5V power on VBUS as an A-Device, and to monitor and pulse VBUS as a B-Device initiating SRP.
An ID input pin, which is made available as an output to the ASIC.
For this system to operate as a dual-role OTG device, the ASIC, DSP, or whatever is connected to the transceiver must be capable both of functioning as a peripheral or host, and of switching roles on-the-fly as a result of HNP.
Click to expand...
Click to collapse
The MSM8255 is "the ASIC, DSP, or whatever" part. The transceiver is yet another part. MSM8255 + USB OTG transceiver = USB OTG DRD Controller.
.
pepoluan said:
Look, if you (or anyone) wants to develop a driver to flip the MSM8255 to Host Mode, no one will prevent you/him/her from doing it.
However, all drivers *must* be tested.
Now, since the W lacks the proper wiring ... how the heck can a developer test if the driver works or not?
And a slight correction: the USB component in the MSM8255 is *not* a controller; it's a microprocessor able to process the Host-side protocols. The controller is the combination of microprocessor + transceiver... and the W has a peripheral-only transceiver, not a switchable transceiver.
Please, READ the following article in its entirety: http://www.maximintegrated.com/app-notes/index.mvp/id/1822
Let me quote the conclusion of the article:
The MSM8255 is "the ASIC, DSP, or whatever" part. The transceiver is yet another part. MSM8255 + USB OTG transceiver = USB OTG DRD Controller.
.
Click to expand...
Click to collapse
how do you know galaxy w has peripheral only transciever and galaxy mini has both!??
Related
Apparently, Its done for Nexus One.
What If I go around that USB hub thing and Separately supply 5V 1A to my USB flashdrive and hardwire it with to be used by my Kaiser's Mini USB connector? (common ground ofcourse)
Also, What should be needed other than this. I am a bit noob but would love to do this experiment. (Maybe using my PC keyboard with Kaiser in future )
I have a Naked coverless 4GB Datatraveler I would love to interface it with my Kaiser. Am I right that right now Android lacks Host functionality but can do if supplied with valid kernel and drivers ? (Ofcourse separate bus powersupply for USB peripherals).
Lets discuss
Techies: have a look http://sven.killig.de/android/N1/2.2/
usb_host/
For Nexus One
Android version: 2.2.2; Kernel version: 2.6.32.9-27240-gbca5320; Build number: FRG83G
As dzo wrote month ago, the kaiser chip isn't host capable.
awww damn
I am doing research for UnBrickable Mod on the Galaxy Nexus. UnBrickable Mod will provide a method of recovering a dead device and guarantee unlocked bootloaders for those with the mod.
I just sorted through the 5,000 page OMAP 4430 processor manual. I believe this OMAP 4430 to be very similar to OMAP 4460 used in the Galaxy Nexus http://focus.ti.com/pdfs/wtbu/OMAP4430_ES2.x_Public_TRM_vK.zip
Rebellos and I will require 2 Galaxy Nexus devices to make this technique work. I've done the research and I thoroughly believe UnBrickable Mod on the Galaxy Nexus is possible.
First Galaxy Nexus will be torn down. The processor must be removed and signal endpoints will be documented.
Second Galaxy Nexus will have the modification applied to it. The device will then be shipped to Poland or worked on remotely from Poland by Rebellos.
{
"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"
}
If this device is anything like previous Galaxy devices which I have worked on, the SysBoot will be locked to OneNAND.. 0b100110. To enable Boot from USB, a hardware modification must be performed to change that to 0b000110. This will allow boot from USB then boot from OneNAND.
Keep in mind this is a Texas Instruments chip...
The first thing that struck me as odd is that OneNAND used to be a Samsung technology.. The next thing was the fact that the SysBoot pins function similarly to the Samsung S5PC110/Exynos xOM pins... on S5PC110, xOM5 must be brough high to enable boot from USB then OneNAND. the OMAP4 allows this same functionality by modifying SysBoot5... I believe Samsung helped develop the OMAP4 chip.
Code:
27.4.1 Booting Overview
27.4.1.1 Booting Types
Booting is the process of starting a bootstrap from one of the booting devices.
The ROM code has two functions for booting: Peripheral booting and memory booting.
• In peripheral booting, the ROM code polls a selected communication interface such as UART or USB,
downloads the executable code over the interface, and executes it in internal RAM. Downloaded
software from an external host can be used to program flash memories connected to the device. This
special case of peripheral booting is called preflashing; software downloaded for preflashing is called
the flash loader. The flash loader burns a new client application image in external flash memory. Initial
software is a generic term for bootstrap, downloaded software, and flash loader. After the image is
burnt, a software (warm) reset can be performed.
• In memory booting, the ROM code finds the bootstrap in permanent memories such as flash memory
or memory cards and executes it. This process is normally performed after a cold or warm device
reset.
The ROM code detects whether the device should download software from a peripheral interface (USB or
UART) by using the sys_boot[5:0] pin configuration. This mechanism encompasses initial flashing in
production (external memory is empty) and reflashing in service (external memory is already
programmed).
27.4.1.2 ROM Code Architecture
Figure 27-4 shows the ROM code architecture. It is split into three main layers with a top-down approach:
high-level, drivers, and hardware abstraction layer (HAL). One layer communicates with a lower-level layer
through a unified interface.
• The high-level layer performs the main tasks of the public ROM code: multicore startup, watchdog and
clock configurations, interrupt management, interaction with the power-management IC, and main
booting routine.
• The driver layer implements the logical and communication protocols for any booting device in
accordance with the interface specification.
• The HAL implements the lowest level code for interacting with the hardware infrastructure IPs. End
booting devices are attached to the device I/O pads.
Figure 27-4 shows the three layers with their modules.
5198
With all the similarities between S5PC110, Exynos, and OMAP4, there is still alot left to do.
If somebody has got ANY info about this device like used chipset models, internal pictures, service manuals, chipset documentations (especially for the CPU, there are few huge manuals from TI about OMAP4460 covering various aspects) please post it or send to Adam or me through PM. This is what we also do need.
Thanks in advance.
^^what he said... we can hardware unlock the bootloader within hours of release if we can get one for destructive teardown.
With more information, we can really unleash the potential.
Love your work Mr Outler, genius..
congrats
edit: and Rebellos you guys go so far beyond, thanks so much!
http://focus.ti.com/pdfs/wtbu/OMAP4460_ES1.0_PUBLIC_TRM_vF.zip
i already love the development on this device <3
you guys are awsome.
Here's the bootmode pins we are concerned with.
h_SYSBOOT_0 pin: F26
h_SYSBOOT_1 pin: E27
h_SYSBOOT_2 pin: E26
h_SYSBOOT_3 pin: E25
h_SYSBOOT_4 pin: D28
h_SYSBOOT_5 pin: D27
--we are not concerned with the following--
h_SYSBOOT_6 pin: AF8
h_SYSBOOT_7 pin: AE8
These values are for the OMAP4430 and should follow on the OMAP4460
Found a dev board based on OMAP4460.. It's called VAR-SOM-OM44
Here are a few things we unearthed in the Galaxy Nexus:
Silicon
CPU: Texas Instruments OMAP4460 (same as the Droid RAZR and Archos G9 tablets), 2047.7 BogoMIPS
GPU: Imagination Technologies PowerVR SGX 540 (same as the Galaxy S and Nexus S)
Wifi / Bluetooth module: Broadcom BCM4330 (same as in the Galaxy S II)
Audio codec: Texas Instruments TWL6040
HDMI: Silicon Image MHD SiI9234 transmitter over MHL (same as Infuse 4G and GSII)
USB Switch: Fairchild semiconductors fsa9480 (industry standard)
Framebuffer controller: Samsung S6E8AA0 MIPI LCD with Gamma correction driver
Sensors
Geomagnetic sensor: Brand new tri-axial Yamaha YAS530
TouchScreen sensor: Melfas MMSxxx touchscreen
Optical / proximity sensor: GP2A (same as Galaxy S and Nexus S)
Barometric pressure sensor: BOSCH BMP180 (first of its kind in a smartphone)
Triaxial acceleration sensor: BOSCH BMA250
Triple Axis MEMS Gyroscope: InvenSense MPU3050
Fuel Gauge (algorithm to track battery's state of charge): MAXIM MAX17040
Misc. internals
Facial recognition elements (Face Unlock): left eye, right eye, nose base, head, face
Available resolution for standard apps: 720 x 1184px
Refresh rate: 60Hz
LCD Density: 320
Default display color depth: 32bit
Camera uses OMAP Ducati Subsystem, on-screen preview size is 768 x 576
Linux kernel: 3.0.1 compiled for SMP with voluntary kernel preemption for best interactivity
Android ROM: version 4.0.1, built October 13, 2011
Device name: Maguro
Main input/output type supported: Headphone, Speaker, Microphone, Bluetooth, Voice, FM, S/PDIF over HDMI; USB Audio DAC (digital-to-audio converter with USB input and stereo outputs) should also be supported
engadget, by Francois
borce_razor said:
CPU: Texas Instruments OMAP4460 (same as the Droid RAZR and Archos G9 tablets), 2047.7 BogoMIPS
Click to expand...
Click to collapse
great for confirmation. This is what we have been researching
USB Switch: Fairchild semiconductors fsa9480 (industry standard)
Click to expand...
Click to collapse
This means 301kohm resistor will work (if wired internally) and we can also get 619Kohm resistor UART output as well. This is awesome. No changes to my setup needed.
Linux kernel: 3.0.1 compiled for SMP with voluntary kernel preemption for best interactivity
Click to expand...
Click to collapse
Very interesting... I didn't think they had a 3.0 mobile kernel yet. This is good to know. It may need a new version of the SuperUser binary compiled for it.. Many of the currently existing binaries we use may break.
Thanks! And thanks Supercurio!
I'm definitely on board. What's the goal? ~$1,500?
caffeineighted said:
I'm definitely on board. What's the goal? ~$1,500?
Click to expand...
Click to collapse
We're not asking for money yet. I'd rather not ask for money at all. I don't like working with that. Money makes things complicated. I'm a horrible businessman, I realize this... I could capitolize on this.. I don't want to deal with money though.
I'm hoping that someone will donate one for research -or- gets one with a warranty which they can blindly let me borrow for a day or two.
Now I realize that it seems underhanded to warranty a device after destroying it, but keep in mind... This modification has potential to help people who would have warrantied their device in the first place... If this modification keeps just 2 people from sending their device in for service, the manufacturers and warranty providers begin saving money for each UnBrickable Mod performed. The users have less to worry about when flashing ROMs. The developers have less stress about bricking their device while developing.
u make a awesome point.
AdamOutler said:
We're not asking for money yet. I'd rather not ask for money at all. I don't like working with that. Money makes things complicated. I'm a horrible businessman, I realize this... I could capitolize on this.. I don't want to deal with money though.
I'm hoping that someone will donate one for research -or- gets one with a warranty which they can blindly let me borrow for a day or two.
Now I realize that it seems underhanded to warranty a device after destroying it, but keep in mind... This modification has potential to help people who would have warrantied their device in the first place... If this modification keeps just 2 people from sending their device in for service, the manufacturers and warranty providers begin saving money for each UnBrickable Mod performed. The users have less to worry about when flashing ROMs. The developers have less stress about bricking their device while developing.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I897 using XDA App
I'd like to also point out that the service manual on the i9000 instructs the service centers to put the device into download mode and download firmware. If the firmware flash fails then it's hardware damage and the board has to be replaced.
Ergo, a bad software flash = a bad board and the board gets replaced
I use i9000 as an example because i9000 is the only example we have of a Galaxy class device service manual.
This is great im so glad there are already devs working hard on making this a reality, im selling my EVO 3D ASAP so i can get this phone as soon as its released!
If there's a fastboot mmc erase function, won't that simply be enough to get it into USB boot mode?
i9100 service manual
borce_razor said:
i9100 service manual
Click to expand...
Click to collapse
I declare and ordain this as understated post of the week.
AdamOutler said:
I declare and ordain this as understated post of the week.
Click to expand...
Click to collapse
with simple words, useful or not ?
ydaraishy said:
If there's a fastboot mmc erase function, won't that simply be enough to get it into USB boot mode?
Click to expand...
Click to collapse
Yeah... but if you erase fastboot than you're screwed
Also, rumor has it that this device will have locked bootloaders... this will help to unlock them.
borce_razor said:
with simple words, useful or not ?
Click to expand...
Click to collapse
Yes
I am doing research for UnBrickable Mod on the Galaxy Nexus. UnBrickable Mod will provide a method of recovering a dead device and guarantee unlocked bootloaders for those with the mod.
I just sorted through the 5,000 page OMAP 4430 processor manual. I believe this OMAP 4430 to be very similar to OMAP 4460 used in the Galaxy Nexus http://focus.ti.com/pdfs/wtbu/OMAP4430_ES2.x_Public_TRM_vK.zip
Rebellos and I will require 2 Galaxy Nexus devices to make this technique work. I've done the research and I thoroughly believe UnBrickable Mod on the Galaxy Nexus is possible.
First Galaxy Nexus will be torn down. The processor must be removed and signal endpoints will be documented.
Second Galaxy Nexus will have the modification applied to it. The device will then be shipped to Poland or worked on remotely from Poland by Rebellos.
{
"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"
}
If this device is anything like previous Galaxy devices which I have worked on, the SysBoot will be locked to OneNAND.. 0b100110. To enable Boot from USB, a hardware modification must be performed to change that to 0b000110. This will allow boot from USB then boot from OneNAND.
Keep in mind this is a Texas Instruments chip...
The first thing that struck me as odd is that OneNAND used to be a Samsung technology.. The next thing was the fact that the SysBoot pins function similarly to the Samsung S5PC110/Exynos xOM pins... on S5PC110, xOM5 must be brough high to enable boot from USB then OneNAND. the OMAP4 allows this same functionality by modifying SysBoot5... I believe Samsung helped develop the OMAP4 chip.
Code:
27.4.1 Booting Overview
27.4.1.1 Booting Types
Booting is the process of starting a bootstrap from one of the booting devices.
The ROM code has two functions for booting: Peripheral booting and memory booting.
• In peripheral booting, the ROM code polls a selected communication interface such as UART or USB,
downloads the executable code over the interface, and executes it in internal RAM. Downloaded
software from an external host can be used to program flash memories connected to the device. This
special case of peripheral booting is called preflashing; software downloaded for preflashing is called
the flash loader. The flash loader burns a new client application image in external flash memory. Initial
software is a generic term for bootstrap, downloaded software, and flash loader. After the image is
burnt, a software (warm) reset can be performed.
• In memory booting, the ROM code finds the bootstrap in permanent memories such as flash memory
or memory cards and executes it. This process is normally performed after a cold or warm device
reset.
The ROM code detects whether the device should download software from a peripheral interface (USB or
UART) by using the sys_boot[5:0] pin configuration. This mechanism encompasses initial flashing in
production (external memory is empty) and reflashing in service (external memory is already
programmed).
27.4.1.2 ROM Code Architecture
Figure 27-4 shows the ROM code architecture. It is split into three main layers with a top-down approach:
high-level, drivers, and hardware abstraction layer (HAL). One layer communicates with a lower-level layer
through a unified interface.
• The high-level layer performs the main tasks of the public ROM code: multicore startup, watchdog and
clock configurations, interrupt management, interaction with the power-management IC, and main
booting routine.
• The driver layer implements the logical and communication protocols for any booting device in
accordance with the interface specification.
• The HAL implements the lowest level code for interacting with the hardware infrastructure IPs. End
booting devices are attached to the device I/O pads.
Figure 27-4 shows the three layers with their modules.
5198
With all the similarities between S5PC110, Exynos, and OMAP4, there is still alot left to do.
If somebody has got ANY info about this device like used chipset models, internal pictures, service manuals, chipset documentations (especially for the CPU, there are few huge manuals from TI about OMAP4460 covering various aspects) please post it or send to Adam or me through PM. This is what we also do need.
Thanks in advance.
^^what he said... we can hardware unlock the bootloader within hours of release if we can get one for destructive teardown.
With more information, we can really unleash the potential.
Love your work Mr Outler, genius..
congrats
edit: and Rebellos you guys go so far beyond, thanks so much!
http://focus.ti.com/pdfs/wtbu/OMAP4460_ES1.0_PUBLIC_TRM_vF.zip
i already love the development on this device <3
you guys are awsome.
Here's the bootmode pins we are concerned with.
h_SYSBOOT_0 pin: F26
h_SYSBOOT_1 pin: E27
h_SYSBOOT_2 pin: E26
h_SYSBOOT_3 pin: E25
h_SYSBOOT_4 pin: D28
h_SYSBOOT_5 pin: D27
--we are not concerned with the following--
h_SYSBOOT_6 pin: AF8
h_SYSBOOT_7 pin: AE8
These values are for the OMAP4430 and should follow on the OMAP4460
Found a dev board based on OMAP4460.. It's called VAR-SOM-OM44
Here are a few things we unearthed in the Galaxy Nexus:
Silicon
CPU: Texas Instruments OMAP4460 (same as the Droid RAZR and Archos G9 tablets), 2047.7 BogoMIPS
GPU: Imagination Technologies PowerVR SGX 540 (same as the Galaxy S and Nexus S)
Wifi / Bluetooth module: Broadcom BCM4330 (same as in the Galaxy S II)
Audio codec: Texas Instruments TWL6040
HDMI: Silicon Image MHD SiI9234 transmitter over MHL (same as Infuse 4G and GSII)
USB Switch: Fairchild semiconductors fsa9480 (industry standard)
Framebuffer controller: Samsung S6E8AA0 MIPI LCD with Gamma correction driver
Sensors
Geomagnetic sensor: Brand new tri-axial Yamaha YAS530
TouchScreen sensor: Melfas MMSxxx touchscreen
Optical / proximity sensor: GP2A (same as Galaxy S and Nexus S)
Barometric pressure sensor: BOSCH BMP180 (first of its kind in a smartphone)
Triaxial acceleration sensor: BOSCH BMA250
Triple Axis MEMS Gyroscope: InvenSense MPU3050
Fuel Gauge (algorithm to track battery's state of charge): MAXIM MAX17040
Misc. internals
Facial recognition elements (Face Unlock): left eye, right eye, nose base, head, face
Available resolution for standard apps: 720 x 1184px
Refresh rate: 60Hz
LCD Density: 320
Default display color depth: 32bit
Camera uses OMAP Ducati Subsystem, on-screen preview size is 768 x 576
Linux kernel: 3.0.1 compiled for SMP with voluntary kernel preemption for best interactivity
Android ROM: version 4.0.1, built October 13, 2011
Device name: Maguro
Main input/output type supported: Headphone, Speaker, Microphone, Bluetooth, Voice, FM, S/PDIF over HDMI; USB Audio DAC (digital-to-audio converter with USB input and stereo outputs) should also be supported
engadget, by Francois
borce_razor said:
CPU: Texas Instruments OMAP4460 (same as the Droid RAZR and Archos G9 tablets), 2047.7 BogoMIPS
Click to expand...
Click to collapse
great for confirmation. This is what we have been researching
USB Switch: Fairchild semiconductors fsa9480 (industry standard)
Click to expand...
Click to collapse
This means 301kohm resistor will work (if wired internally) and we can also get 619Kohm resistor UART output as well. This is awesome. No changes to my setup needed.
Linux kernel: 3.0.1 compiled for SMP with voluntary kernel preemption for best interactivity
Click to expand...
Click to collapse
Very interesting... I didn't think they had a 3.0 mobile kernel yet. This is good to know. It may need a new version of the SuperUser binary compiled for it.. Many of the currently existing binaries we use may break.
Thanks! And thanks Supercurio!
I'm definitely on board. What's the goal? ~$1,500?
caffeineighted said:
I'm definitely on board. What's the goal? ~$1,500?
Click to expand...
Click to collapse
We're not asking for money yet. I'd rather not ask for money at all. I don't like working with that. Money makes things complicated. I'm a horrible businessman, I realize this... I could capitolize on this.. I don't want to deal with money though.
I'm hoping that someone will donate one for research -or- gets one with a warranty which they can blindly let me borrow for a day or two.
Now I realize that it seems underhanded to warranty a device after destroying it, but keep in mind... This modification has potential to help people who would have warrantied their device in the first place... If this modification keeps just 2 people from sending their device in for service, the manufacturers and warranty providers begin saving money for each UnBrickable Mod performed. The users have less to worry about when flashing ROMs. The developers have less stress about bricking their device while developing.
u make a awesome point.
AdamOutler said:
We're not asking for money yet. I'd rather not ask for money at all. I don't like working with that. Money makes things complicated. I'm a horrible businessman, I realize this... I could capitolize on this.. I don't want to deal with money though.
I'm hoping that someone will donate one for research -or- gets one with a warranty which they can blindly let me borrow for a day or two.
Now I realize that it seems underhanded to warranty a device after destroying it, but keep in mind... This modification has potential to help people who would have warrantied their device in the first place... If this modification keeps just 2 people from sending their device in for service, the manufacturers and warranty providers begin saving money for each UnBrickable Mod performed. The users have less to worry about when flashing ROMs. The developers have less stress about bricking their device while developing.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I897 using XDA App
I'd like to also point out that the service manual on the i9000 instructs the service centers to put the device into download mode and download firmware. If the firmware flash fails then it's hardware damage and the board has to be replaced.
Ergo, a bad software flash = a bad board and the board gets replaced
I use i9000 as an example because i9000 is the only example we have of a Galaxy class device service manual.
This is great im so glad there are already devs working hard on making this a reality, im selling my EVO 3D ASAP so i can get this phone as soon as its released!
If there's a fastboot mmc erase function, won't that simply be enough to get it into USB boot mode?
i9100 service manual
borce_razor said:
i9100 service manual
Click to expand...
Click to collapse
I declare and ordain this as understated post of the week.
AdamOutler said:
I declare and ordain this as understated post of the week.
Click to expand...
Click to collapse
with simple words, useful or not ?
ydaraishy said:
If there's a fastboot mmc erase function, won't that simply be enough to get it into USB boot mode?
Click to expand...
Click to collapse
Yeah... but if you erase fastboot than you're screwed
Also, rumor has it that this device will have locked bootloaders... this will help to unlock them.
borce_razor said:
with simple words, useful or not ?
Click to expand...
Click to collapse
Yes
xperia ray has same chipset as galaxy w and it works USB otg function .then galaxy w can also be supported.isn't it ?
Someone should work on kernel to support USB OTG
If I can make the kernel better, I would prefer to complete the CM10 first than it
Isn't this Bulls.it enough?
Abdulshamseer said:
xperia ray has same chipset as galaxy w and it works USB otg function .then galaxy w can also be supported.isn't it ?
Someone should work on kernel to support USB OTG
Click to expand...
Click to collapse
You allready have a topic for begging USB OTG
Code:
http://forum.xda-developers.com/showthread.php?t=1900959
and two other posts of you related to this topic:
http://forum.xda-developers.com/showpost.php?p=33216895&postcount=42
http://forum.xda-developers.com/showthread.php?p=33418397#post33418397
and always the same answer
SAMSUNG GALAXY W aka Wonder aka ANCORA doesn't have USB CONTROLLER HARDWARE!
Click to expand...
Click to collapse
{
"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"
}
PLEASE, do some researches and use your brain wisely before posting any sh*t like this. and yes, wrong section, mate.
dewadg said:
If I can make the kernel better, I would prefer to complete the CM10 first than it
Click to expand...
Click to collapse
+1
i prefer to have stable and fast kernel first rather than adding features which is still unknown
hotheabilly said:
O rly? Should this on dev section?
-sent from my awesome phone-
Click to expand...
Click to collapse
some people misinterpret dev section as a "dev" place for his own sake. too sad
Sent from my GT-I8150
Abdulshamseer said:
xperia ray has same chipset as galaxy w and it works USB otg function .then galaxy w can also be supported.isn't it ?
Someone should work on kernel to support USB OTG
Click to expand...
Click to collapse
This is getting tiresome.
*In addition* to a baseband chipset that supports USB OTG HNP (Host Negotiation Protocol), to function as a USB OTG Host, a device must also be equipped with a host controller chip (a.k.a Root Controller) that will perform (among others) the necessary 1) pull-up resistance, 2) signal switch, and 3) power supply instead of draw.
Xperia Ray comes with a host controller chip.
Samsung Galaxy W doesn't.
Now, stop bugging us with stupid requests!
-- Sent from a GT-I8150 running ICS perfectly well. F'U, Sams#!t --
pepoluan said:
This is getting tiresome.
*In addition* to a baseband chipset that supports USB OTG HNP (Host Negotiation Protocol), to function as a USB OTG Host, a device must also be equipped with a host controller chip (a.k.a Root Controller) that will perform (among others) the necessary 1) pull-up resistance, 2) signal switch, and 3) power supply instead of draw.
Xperia Ray comes with a host controller chip.
Samsung Galaxy W doesn't.
Now, stop bugging us with stupid requests!
-- Sent from a GT-I8150 running ICS perfectly well. F'U, Sams#!t --
Click to expand...
Click to collapse
So it means Galaxy Mini has the host controller?
dewadg said:
So it means Galaxy Mini has the host controller?
Click to expand...
Click to collapse
Never owned one.
-- Sent from a GT-I8150 running ICS perfectly well. F'U, Sams#!t --
wow
Sent from my GT-I8150 using xda premium
yupps, you should ask this not in development thread but general topic, and you see below comments they know that galaxy w doesnt support USB OTG, and I really dissapoint because samsung never give something important hardware that we really need that, I suggest you if you want USB OTG maybe you should buy galaxy s(need price from galaxy w), and xperia, etc
rizky syahputra said:
yupps, you should ask this not in development thread but general topic, and you see below comments they know that galaxy w doesnt support USB OTG, and I really dissapoint because samsung never give something important hardware that we really need that, I suggest you if you want USB OTG maybe you should buy galaxy s(need price from galaxy w), and xperia, etc
Click to expand...
Click to collapse
it's not samsung's fault, it's your fault by buying without knowing the spec
if you really need otg why don't you just buy other phone or wait for any development on otg
hadidjapri said:
it's not samsung's fault, it's your fault by buying without knowing the spec
if you really need otg why don't you just buy other phone or wait for any development on otg
Click to expand...
Click to collapse
because galaxy w reach some particular specifications, although some hardware is lacking, and as I said samsung give some specific smartphones and certain specifications that its market behavior, and some topics besides galaxy w, I often see why ics, jelly bean. not provided by Samsung that makes them upset, xperia example: xperia miro that's ARMv6 and his rival galaxy ace but provide ICS for xperia miro while galaxy ace not
rizky syahputra said:
because galaxy w reach some particular specifications, although some hardware is lacking, and as I said samsung give some specific smartphones and certain specifications that its market behavior, and some topics besides galaxy w, I often see why ics, jelly bean. not provided by Samsung that makes them upset, xperia example: xperia miro that's ARMv6 and his rival galaxy ace but provide ICS for xperia miro while galaxy ace not
Click to expand...
Click to collapse
when i said spec i'm not only talking about hardware spec. read gsm arena carefully and you'll see OS spec exists there
Sent from my GT-I8150
Stop asking for USB OTG. The SGW will never have USB OTG and even if it does it will drain the already poor battery life even more than usual and surely even if the SGW has USB OTG then only what 2 or 3 people would see it as a fantastically useful feature while the rest of us couldn't give a **** about this useless feature that people keep requesting.
pepoluan said:
Never owned one.
-- Sent from a GT-I8150 running ICS perfectly well. F'U, Sams#!t --
Click to expand...
Click to collapse
Galaxy Mini now can use USB OTG. But it's limited to only for flashdisk. Mini has no enough power to hold devices such as joystick. I am still confused about the main requirement of a device to use USB OTG. Is it the host controller or the kernel
---------- Post added at 06:56 PM ---------- Previous post was at 06:54 PM ----------
hadidjapri said:
it's not samsung's fault, it's your fault by buying without knowing the spec
if you really need otg why don't you just buy other phone or wait for any development on otg
Click to expand...
Click to collapse
Agreed with you, blaming Samsung here brings nothing
hadidjapri said:
when i said spec i'm not only talking about hardware spec. read gsm arena carefully and you'll see OS spec exists there
Sent from my GT-I8150
Click to expand...
Click to collapse
well I guest galaxy w enough for hardware spec, better games, therefore 512mb ram but I it's ok and better music. I guest all I need better OS, more new more better therefore there are some bugs I guest it's ok, that's why we must give thanks to arco for his project and we user of galaxy w must give a pray and give a support for his project to get a new better OS android.
lastime open thread about bigmem kernel that dint give anything to community, and now this? if can vote banning people, i vote u 1st. hahahhaa
Sent from my GT-I8150 using xda premium
I made a clear research about USB otg and USB host
its having hardware specification for galaxy w having chipset msm 8255 supporting usb host not otg....xperia ray has otg and is not mentioned even by sony but somebody found..
https://developer.qualcomm.com/sites/default/files/snapdragon-specs.pdf
Its having spec for galaxy mini too..just need to enable it in kernal like in galaxy s and mini
Galaxy w must support USB host because galaxy mini has older chip and host support same as galaxy w..
Those who are working with kernel.they can build it
http://forum.xda-developers.com/showthread.php?t=1450298
if it works, it may sometimes require external power
Abdulshamseer said:
I made a clear research about USB otg
reply there this..its having hardware specification for galaxy w having chipset msm 8255 supporting usb host not otg..also mention xperia ray has otg and is not mentioned even by sony but somebody found..
https://developer.qualcomm.com/sites/default/files/snapdragon-specs.pdf
Its havin spec for galaxy mini too..just need to enable it in kernal like in galaxy s and mini
Galaxy w must USB host because galaxy mini has older chip and host support same as galaxy w..
Those who are working with kernel.they can build it
http://forum.xda-developers.com/showthread.php?t=1450298
Click to expand...
Click to collapse
It's really deep mate, and I really confused why Usb Host Controller support for galaxy w in google play. and you should know that galaxy w not enough battery for running USB OTG.
rizky syahputra said:
It's really deep mate, and I really confused why Usb Host Controller support for galaxy w in google play. and you should know that galaxy w not enough battery for running USB OTG.
Click to expand...
Click to collapse
look at to the last line
I`ve just bought the Vensmile U1, It seems to be the same as Unuiga S905 (2gb model) under a different name, knowing that unuiga didn`t reach the crowfunding campaign.
Checking on the specs, modules are practically the same Amlogic S905 Quad Core, ARM Cortex-A53 2GB RAM, 32GB eMMC, wifi (Im not quiet sure if it`s the same module), ethernet gigabit, and bluetooth 4.0. Physically are just the same (u can google 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"
}
I had several problems resizing windows, finding upgrades via OTA, using a tv with 4k the audio and video were flickering, after reboot USB ports didn't worked at all. It comes with Remix OS 2.0 Installed, the 2016-04-05 version.
But (here comes the funny thing), I tried to update the box to 20160506 straight from Remixos official website jide.com/remixos/devices/unuigas905 , Unuiga S905 model. It shows me an error: "E: signature verification failed". I haven`t been able to root it.
***Edited***
After a few days, the seller sent me and .img file with the 2.0.300 remix os version... BUT It can not be upgraded as usual, so I used the USB Burning Tool for amlogic devices. After a few drawbacks it worked! Resizing windows are pretty smooth now, there are no 4k troubles, Wifi is a little weak, but it still works, plus LAN cable.
Here you are the file that the seller (vensmile) sent me to upgrade it, it is almost the same as the one on Jide website. The difference is that this one, comes with the playstore activated and kodi installed.
File from Vensmile:
https://mega.nz/#!3hQ12TyT!csp043S32K5GQM2BULfem1j6AxrcsFFHFdGyUMwtrcM
I haven't been able to root it, is there any way I can root the .img file before installing it?
i hope this information would be useful for those who want to buy it. It is definitely a great device. These are the specs of both devices:
SoC – Amlogic S905 quad core ARM Cortex-A53 @ up to 2.0GHz with penta-core Mali-450MP GPU
System Memory – 2GB RAM
Storage – micro SD slot; 32GB flash
Video Output – HDMI 2.0, AV
Audio – HDMI, AV, coaxial S/PDIF
Gigabit Ethernet
WiFi – dual band 802.11 b/g/n/ac
Bluetooth 4.1
USB – 2x USB 2.0 host ports (the USB port in the middle is one with OTG capability)
IR receiver (I havent tried this one), touch button for power on/off and standby (long pulse on boot and u r on recovery mode)
Dimensions – 11.2 x 11.2 x 2 cm
(Sorry about my english)
Greetings from Mexico!
chavez.isr said:
I`ve just bought the Vensmile U1, It seems to be the same as Unuiga S905 (2gb model) under a different name, cuz unuiga didn`t reach the crowfunding campaign.
Checking the specs, modules are practically the same Amlogic S905 Quad Core, ARM Cortex-A53 2GB RAM, 32GB eMMC, wifi (Im not quiet sure if it`s the same module), ethernet gigabit, and bluetooth 4.0. Physically are just the same (u can google it)
I had several problems resizing windows, finding upgrades via OTA, using a tv with 4k the audio and video were flickering, after reboot USB ports didn't worked at all. It has Remix OS 2.0 Installed, the 2016-04-05 version.
But (here comes the funny thing), I tried to update the box to 20160506 straight from Remixos official website jide.com/remixos/devices/unuigas905 , Unuiga S905 model. It shows me an error: "E: signature verification failed". I haven`t been able to root it.
***Edited***
After a few days, the seller sent me and .img file with the 2.0.300 remix os version... BUT It can not be upgraded as usual, so I used the USB Burning Tool for amlogic devices. After a few drawbacks it worked! Resizing windows works pretty smooth, there are no 4k troubles, Wifi is a little weak, but it still works with a LAN cable.
Here you are the file that the seller (vensmile) sent me to upgrade it, it is almost the same as the one on Jide website. The difference is that this one, comes with the playstore activated and kodi installed.
File from Vensmile:
mega.nz/#!msM0WJjT!csp043S32K5GQM2BULfem1j6AxrcsFFHFdGyUMwtrcM
I haven't been able to root it, is there any way I can root the .img file and then install it on the box?
i hope this information would be useful for those who wants to buy it. It is definitely a great device. These are the specs of both devices:
SoC – Amlogic S905 quad core ARM Cortex-A53 @ up to 2.0GHz with penta-core Mali-450MP GPU
System Memory – 2GB RAM
Storage – micro SD slot; 32GB flash
Video Output – HDMI 2.0, AV
Audio – HDMI, AV, coaxial S/PDIF
Gigabit Ethernet
WiFi – dual band 802.11 b/g/n/ac
Bluetooth 4.1
USB – 2x USB 2.0 host ports (the USB port in the middle is one with OTG capability)
IR receiver (I havent tried this one), touch button for power on/off and standby (long pulse on boot and u r on recovery mode)
Dimensions – 11.2 x 11.2 x 2 cm
(Sorry about my english)
Greetings from Mexico!
Click to expand...
Click to collapse
I would like to download the file, but it's encrypted and need to enter a decryption key.
basjke said:
I would like to download the file, but it's encrypted and need to enter a decryption key.
Click to expand...
Click to collapse
Hello @basjke
Thanks, I've just changed the link, u will need a Male to male USB cable.
have you find a way a to root it?
chavez.isr said:
Hello @basjke
Thanks, I've just changed the link, u will need a Male to male USB cable.
have you find a way a to root it?
Click to expand...
Click to collapse
Thanks for updating the link. I haven't received my Vensmile yet, but was already taking precautions :laugh:
Are you still satisfied with the performance of the box overall, and how weak is weak Wifi?
chavez.isr said:
Hello @basjke
Thanks, I've just changed the link, u will need a Male to male USB cable.
have you find a way a to root it?
Click to expand...
Click to collapse
Oh! I see, u wont regret buying it.
I bought a Micro SD U3 and downloaded all of my torrent videos there. Remix os + Adblock + frostwire + Air mouseKeyboard U will love it! It seems to be pretty stable, I use it on a LG 4k TV, and find no problems at all when playing x265 videos (u can use mx player or kodi, VLc sucks in here ).
I only use it to download TV series and movies, Netflix, HBO GO. U should try Game of thrones and Flash XD .
I havent made any pro test on the wifi signal, it has one bar less than my laptop (LOL), Pretty usual on this kind of devices i think.
Hi,
pls check this post http://forum.xda-developers.com/general/general/root-remix-os-pc-t3292933.
i ordered one a week ago. let me know if it works i would like to use adblock and other stuff ....
Thank for ur answer. good luck
chavez.isr said:
I`ve just bought the Vensmile U1, It seems to be the same as Unuiga S905 (2gb model) under a different name, knowing that unuiga didn`t reach the crowfunding campaign.
Checking on the specs, modules are practically the same Amlogic S905 Quad Core, ARM Cortex-A53 2GB RAM, 32GB eMMC, wifi (Im not quiet sure if it`s the same module), ethernet gigabit, and bluetooth 4.0. Physically are just the same (u can google it)
I had several problems resizing windows, finding upgrades via OTA, using a tv with 4k the audio and video were flickering, after reboot USB ports didn't worked at all. It comes with Remix OS 2.0 Installed, the 2016-04-05 version.
But (here comes the funny thing), I tried to update the box to 20160506 straight from Remixos official website jide.com/remixos/devices/unuigas905 , Unuiga S905 model. It shows me an error: "E: signature verification failed". I haven`t been able to root it.
***Edited***
After a few days, the seller sent me and .img file with the 2.0.300 remix os version... BUT It can not be upgraded as usual, so I used the USB Burning Tool for amlogic devices. After a few drawbacks it worked! Resizing windows are pretty smooth now, there are no 4k troubles, Wifi is a little weak, but it still works, plus LAN cable.
Here you are the file that the seller (vensmile) sent me to upgrade it, it is almost the same as the one on Jide website. The difference is that this one, comes with the playstore activated and kodi installed.
File from Vensmile:
https://mega.nz/#!3hQ12TyT!csp043S32K5GQM2BULfem1j6AxrcsFFHFdGyUMwtrcM
I haven't been able to root it, is there any way I can root the .img file before installing it?
i hope this information would be useful for those who want to buy it. It is definitely a great device. These are the specs of both devices:
SoC – Amlogic S905 quad core ARM Cortex-A53 @ up to 2.0GHz with penta-core Mali-450MP GPU
System Memory – 2GB RAM
Storage – micro SD slot; 32GB flash
Video Output – HDMI 2.0, AV
Audio – HDMI, AV, coaxial S/PDIF
Gigabit Ethernet
WiFi – dual band 802.11 b/g/n/ac
Bluetooth 4.1
USB – 2x USB 2.0 host ports (the USB port in the middle is one with OTG capability)
IR receiver (I havent tried this one), touch button for power on/off and standby (long pulse on boot and u r on recovery mode)
Dimensions – 11.2 x 11.2 x 2 cm
(Sorry about my english)
Greetings from Mexico!
Click to expand...
Click to collapse
Hi
I have bought the new Ugoos AM1 device which also has a similar specs. It is currently running Android 5.1. Do you thing the link you sent me will work for me as well. What is the process to flash an amlogic device - can you please direct me to any step by step instructions to do this?
oki7 said:
Hi,
pls check this post http://forum.xda-developers.com/general/general/root-remix-os-pc-t3292933.
i ordered one a week ago. let me know if it works i would like to use adblock and other stuff ....
Thank for ur answer. good luck
Click to expand...
Click to collapse
I couldnt root it it shows me an error, did u do it succesfully?
sany said:
Hi
I have bought the new Ugoos AM1 device which also has a similar specs. It is currently running Android 5.1. Do you thing the link you sent me will work for me as well. What is the process to flash an amlogic device - can you please direct me to any step by step instructions to do this?
Click to expand...
Click to collapse
Hello! I dont know if it can work, u can make a full backup of your box and try to install the remix OS img file using the <USB Burning Tool for amlogic devices> ... Good luck!
I have a Beelink Mini MXIII, seems the rame hardware!
Hi friend so... I have one but when I try to put subtitles in the movie player by default... The subtitles are in a side not in the center!!N some help please
Hello, after so much I could revive my unuiga u1, I have the vergence of 2gb ram and 16gb internal storage. Install the firmware but I left without wifi and apparently without blutoot also could not find the exact firmware for my unuiga
You can upgrade for remix 3.0?
Kracoss said:
You can upgrade for remix 3.0?
Click to expand...
Click to collapse
nop, sadly theres no support for this Box
I'm looking for the remote.conf.
Can someone help me?
Edit: Found it.
http://www79.zippyshare.com/v/DfRakCEk/file.html