I've been chat for a while thru skype with ider support, requesting for root access.
After 3 hour giving the explanations why should i have to have root, they ask their developers (fortunately online) and the answer was textually:
"the product does not support root" and " the software doesnt support this function"
So, as a conclusion:
if you bought this box.. no root possible.
You can think you have a brick? maybe yes. but you can deal with it...
anyway; great support for the overseas agent: Mrs. Snow Yin thru skype.
The Following User Says Thank You to walteroa For This Useful Post:
Maybe. The ider A-10, Sumvision Cyclone Android Media Centre and my no-name box from AsiaPads seem different brands of one and the same box.
I 'll try to flash a modified FW in order to get it "rooted".Will let u know the results soon.
The Following 3 Users Say Thank You to wolfgangpauli For This Useful Post:
Ladies (if any) and Gentlemen,
for the moment I am not allowed to post links nor photos here due to some restrictions that I understand quite well. As soon as this changes I will post here all the information that I have on this box. Mine is disassemled and I am very interested already what my investigation on the 2 (?) UARTS will show. So keep on reading...
Cheers,
wolfgang pauli
The Following User Says Thank You to wolfgangpauli For This Useful Post:
In advance I can give you the "phone info" of my box. It resembles very much to what walteroa posted already (walteroa, are you spanish or where did you buy your box?)
Here you can also get the firmware files, but I warn to no install these, Finally I ended up that I cannot return to recovery mode...;-(
So you know why I have to dig a bit deeper in oder to get control over the machine.
Cheers,
wolfgangpauli
The Following User Says Thank You to wolfgangpauli For This Useful Post:
In advance I can give you the "phone info" of my box. It resembles very much to what walteroa posted already (walteroa, are you spanish or where did you buy your box?)
I bought in China, but I'm living in Latin America.. Argentina Precisely...
Anyway, I can change the lenguage and take a new picture if neccesary!!
comming back to chinese clone boxes, the only difference seems to be the compilation number or version (the one that I have, cames from Ider itself, refer to details in this post ..)
so, now its your turn to try and let us know about experiences!!!
Hola Walteroa,
no es necesario cambiar el idioma. Manejo el castellano bastante bien ;-)
Here is a foto of my opened box. You can see the (suspected) UART (?) connector next to the external SATA port (top of the image). For the moment no further results. Keep you updated.
De hecho tengo buenas noticias. - I have good news, indeed.
With the encouraging hints of a colleague (credits to Henrik H.) of mine I found out that the 6pin connector in my picture posted above is indeed an UART (serial device) that spits out masses of valuable information about the boot process.
This is probably the clue for debugging and - hopefully - also for rooting. Though I am not able to give an instruction yet on how to root this device it may give others a hint how to manipulate it or get valuable debug info about the boot process or for unbricking the device ...
Hasta pronto,
wolfgang
Last edited by wolfgangpauli; March 19th, 2012 at 06:42 PM.
The Following User Says Thank You to wolfgangpauli For This Useful Post:
The last 3 weeks have revealed some further secrets of this box.
1) The bootloader is a customised (i.e., not all commands work) version of
U-Boot 2010.06(dvbc_8726m1_v1@trunk) (Jan 09 2012 - 15:02:36)
2) The 6pin connector on the right-hand side of the SATA connector is an UART. Connecting an USB-to-UART bridge one can listen and talk to the machine (i.e. debugging console and uboot command line)
3) The keyboard setting is a bit strange, but systematic with respect to the ASCII table. In order to execute uboot commands I send ASCII character sequences to the device using the PERL programming language.
4) The debugging console actually showed me that the recovery mode of my box does not work any more.
### ERROR ### Please RESET the board ### is the last line that I get out of the box after starting by pressing the recovery button
5) Nevertheless, it is possible to boot into recovery mode. I set up a linux box as tftp-Server and provide the uImage_recovery file via this box (it is necessary to set the corresponding parameters in order to match one's network configuration). Uboot command 'tftpboot' allows booting via a tftp-server on the network.
6) As soon as a display is connected via HDMI the debugging console / uboot command line stop working
7) At the moment I can only imagine the following ways of 'rooting' the box:
* find a suitable android 2.3.4 exploit
* find a way to get 'su' and 'superuser.apk' integrated into the ROM
that passes by the signature check of android recovery <3>
* get a manipulated android recovery <3> that does not check the or try
android recovery <2> (i do not know if this is possible)
8) ASAP I'll write up all the results and steps that I went through as a basis for further experiments with the aim of finally getting it 'rooted'.
Last edited by wolfgangpauli; April 11th, 2012 at 05:04 PM.
The Following 3 Users Say Thank You to wolfgangpauli For This Useful Post:
WARNING!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
DO NOT APPLY THE BELOW MENTIONED METHOD FOR ROOTING! I AM FACING STRANGE BOOT BEHAVIOUR THE DAY AFTER. I DO NOT YET KNOW WHY. THE MACHINE HANGS AT THE "A9"-SCREEN
I HAVE TO INVESTIGATE FURTHER WHAT COULD BE THE REASON (WLAN, HDMI, USB...)
wolfgang_pauli
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!
Dear Enthusiasts,
I am happy to announce to have successfully rooted the box.
I did not unzip the file but renamed it to update.zip. I put it on a USB stick (fat 16 formatted).
Booted into recovery mode und applied the update (this adds superuser privileges to your already existing Android 2.3.4 system)
That's all!
Please be warned, this worked for me but may not work for you. I may not be held reliable for any damages of your box!!!!!!!!!!
Best regards,
wolfgang_pauli
PS: Comments and reports of successful "rooting" highly appreciated!
Last edited by wolfgangpauli; April 22nd, 2012 at 12:57 AM.
The Following 3 Users Say Thank You to wolfgangpauli For This Useful Post:
O.k., I think it is 99,9% safe to apply this method in order to get the device rooted. The 'hangs' at the 'A9' screen are rather to be attributed to a connected USB stick or to the USB-UART-bridge that seems to interfere a bit with a connected HDMI device.
Since for the non-hacker all above-mentioned reasons for a 'hang' are irrelevant, this "rooting" method can be applied in a rather simple manner without opening the device.
The "update" (as I anderstand it) just copies the programs 'superuser.apk' and 'su' to the corresponding locations within the operating system and sets the corresponding permissions.
Besides the systematic 'hangs' already described I have not faced further odd behaviour after the rooting the device.
Best regards,
wolfgang_pauli
PS: As soon as I have time I'll write up the information promised some posts earlier.
PPS: By rooting your device you may lose the warranty. Furthermore you may brick your device and reduce system security. Be warned and root your device only if you know what your are doing!!
Last edited by wolfgangpauli; April 24th, 2012 at 02:29 PM.
The Following User Says Thank You to wolfgangpauli For This Useful Post:
Since "rooting" is easy once you know how to do it, here is a small "guide 4 dummies":
1) Take an SD card and format it FAT32 (I tried it with an 8GB SDHC card)
2) copy this http://dl.dropbox.com/u/4546860/update.root.yareg.march.2012.zip file to the SD card and rename it to update.zip (do not unzip, just change the file name). On M$-Windows rename it "update", the extension ".zip" should be preserved anyway, when changing the name of a ZIP-file.
3) put the SD card into the switched-off android device
4) press the "update button" at the bottom of the device and power the device while still holding the button
5) When the display shows "Android system recovery <3e>" try to navigate with the up/down buttons of the remote control. The menu has 5 entries.
6) Choose "apply update" with the "enter button" of the remote control. Enter into submenu "sdcard/" where you should now see the content of the SD card, i.e. the file "update.zip"
7) Select the file "update.zip" and press "enter". This will install the update (= copy the superuser.apk and su files with corresponding permissions).
8) Choose reboot. The device is now "rooted". Enjoy!
PS: Be careful, never unplug the device from mains during a system update!
PPS: Read all about the consequences of "rooting" an android device
Best regards,
wolfgang_pauli
Last edited by wolfgangpauli; April 28th, 2012 at 02:20 PM.
The Following 2 Users Say Thank You to wolfgangpauli For This Useful Post:
If one does the above root can you preserve and stay rooted in anyway because there is now a beta 4.0 sandwich upgrade available from sumvision for cyclone nano slim.
mm316,
The sumvision cyclone nano slim differs from the box described in thread.
I'd need more information about your box in order to recommend or advice you.
Since the problem you describe here is a completely new one not related to the "ider a10", pls. open a new thread.
Maybe you could title it "Rooting the Sumvision cyclo nano slim". As soon as the new thread exists, pls. let us know. Start the thread with as much information as you can get about your box. pictures, system info, webpage links to the firmware etc.
4) press the "update button" at the bottom of the device and power the device while still holding the button
5) When the display shows "Android system recovery <3e>" try to navigate with the up/down buttons of the remote control. The menu has 5 entries.
wolfgang_pauli
Couldn't get the update do boot in recovery, it only stand on A9 logo. You said something about boot using tftboot of uboot, can this be done on this way? Could it be done thought tftpboot?
EDIT : I did it. The catch was that uImage_recovery , must be in the sdcard or youll get stuck on A9 logo. Cant post link of the firmware, but the file name is ku7YucGFydDEucmFy=.rar. you dont even need the cf03ref-eng.zip inside it, only the uimage_recovery to root.
Last edited by leodfs; May 17th, 2012 at 05:59 PM.
The Following User Says Thank You to leodfs For This Useful Post:
Couldn't get the update do boot in recovery, it only stand on A9 logo. You said something about boot using tftboot of uboot, can this be done on this way? Could it be done thought tftpboot?
EDIT : I did it. The catch was that uImage_recovery , must be in the sdcard or youll get stuck on A9 logo. Cant post link of the firmware, but the file name is ku7YucGFydDEucmFy=.rar. you dont even need the cf03ref-eng.zip inside it, only the uimage_recovery to root.
You are completely right. I noticed this recently.
Yes, put uImage_recovery onto the SD card, and press the recovery button when powering up. This will get you to the Android recovery.
I tried to store uImage_recovery somewhere in the boxes memory, but now that I know how to enter recovery I will not try further. There is some risk to overwrite something that afterwards does not work any more.
Have you rooted your box already?
The Following 2 Users Say Thank You to wolfgangpauli For This Useful Post:
You are completely right. I noticed this recently.
Yes, put uImage_recovery onto the SD card, and press the recovery button when powering up. This will get you to the Android recovery.
I tried to store uImage_recovery somewhere in the boxes memory, but now that I know how to enter recovery I will not try further. There is some risk to overwrite something that afterwards does not work any more.
Have you rooted your box already?
Well, in fact i haven't had enought time. I hope i can start next week. Cheers!!
My unity is rooted. Running samba file sharing app. How cool is that?
A bit off topic, but that was the main reason for me to root: get bluetooth dongle working. But cant even find the btusb.ko and bluetooth.ko modules for our kernel, to begin with. Any tips on that?
And thanks one more time.
My box is temporarily out of order. I try to get all switches outside in order not to have to fiddle with toothpicks.
@leodfs: Would you, pls., confirm that the rooting method that I described above was successful for you or did you do something completely different in order to the the box "rooted".
I think this would be helpful for others.
Cheers,
wolfgang_pauli
PS: Bluetooth -> unplug the usb-transceiver of the wireless keyboard, plug the Bluetooth dongle in, then reattach the usb-transceiver of the keyboard. I remember some issue on this...... and keep me informed, pls., if this was successful 4 you.
Sure thing dude, I will just copy and paste everything you posted and add one thing on 2.1:
1) Take an SD card and format it FAT32 (I tried it with an 8GB SDHC card)
2) copy this http://dl.dropbox.com/u/4546860/update.root.yareg.march.2012.zip file to the SD card and rename it to update.zip (do not unzip, just change the file name). On M$-Windows rename it "update", the extension ".zip" should be preserved anyway, when changing the name of a ZIP-file.
2.1 Download this file and put on root of your sdcard: https://www.dropbox.com/s/vvllelkeryvu009/uImage_recovery . (If you got stuck on A9 logo, is because you don't have it, if you can't move the options on recovery with remote, it is not the right uImage_recovery. This happenend when I used the Sumvision Cyclone one. The one that worked was the one I found on the chinese official szider ider a10 page with date 2012-3-9. I did the upgrade, by the way, and the root worked as well. the only thing a notice on this update was the option Account and Sync on Settings)
3) put the SD card into the switched-off android device
4) press the "update button" at the bottom of the device and power the device while still holding the button
5) When the display shows "Android system recovery <3e>" try to navigate with the up/down buttons of the remote control. The menu has 5 entries.
6) Choose "apply update" with the "enter button" of the remote control. Enter into submenu "sdcard/" where you should now see the content of the SD card, i.e. the file "update.zip"
7) Select the file "update.zip" and press "enter". This will install the update (= copy the superuser.apk and su files with corresponding permissions).
8) Choose reboot. The device is now "rooted". Enjoy!
You got BT working? You raised my hopes, but the official firmware don't even have BT options on settings.
Someone can post the links of downloadable files from vhinese site of ider a10?
The english site is not updated and i'm italian with no possibility to surf chinese site...
Newest firmware link?
Newest uimage recovery image file link?
Any other lin for download or manual or document?
I still have problem with the market that shows few apps.
I have erased cache and data fo market... flashed a new firmware (updated 11 january 2012) but i have wifi issue (wifi error when i switch on). So i downgrade to the original firmware of 25 november 2011).
You just go to English site, memorize the position of the Download button, on the Chinese site, the position is the same. You will have two different download for our model, one bellow another. Is in fact a multivolume rar. You have to download both to extract.
Last edited by leodfs; May 26th, 2012 at 07:27 AM.
@tapottolo : Mettiamoci d' accordo di non fare segreti qui. Quali sono i link della nuova firmware. grazie ;-)
: Let us agree not have secrets here. Pls., share the links with us to the new firmware.
@walteroa : hoy no tengo mas la fuerza de escribir en castellano, saludos cordiales w.p.
saluti cordiali da Austria,
saludos cordiales desde Austria
greeeeeetz from Austria
wolfgang_pauli
@leodfs: Where are u from?
Last edited by wolfgangpauli; May 26th, 2012 at 06:12 PM.
I have upgraded to new firmware 7 march 2012... After some apps restoring i reboot the box and the wifi gives error. I lose mac address and wifi doesn't work. I have to switch off the box and then reflash after wipe. Any idea ?
I have play store fully. Simply rooted with written procedure. My only problem is that if I switch off the box and then switch on quickly, the wifi doesn't work and give me error... I have to wait among five minutes to reboot... Anyone with this problem? Bye.
True, this is a problem, I guess it is caused by how abruptly the process of turn off is made. It does not affect me much because I use Lan. When it happens could you please check the content and size of /system/etc/wpasupplicant.conf. I guess it is getting corrupted.
I have play store fully. Simply rooted with written procedure. My only problem is that if I switch off the box and then switch on quickly, the wifi doesn't work and give me error... I have to wait among five minutes to reboot... Anyone with this problem? Bye.
Great. Which firmware version you are using?
Could you share download link of the firmware you are using?
Can you also extract your build.prop and vending.apk from your box and shared with me? Thanks.
Last edited by bthoven; June 4th, 2012 at 07:55 PM.
True, this is a problem, I guess it is caused by how abruptly the process of turn off is made. It does not affect me much because I use Lan. When it happens could you please check the content and size of /system/etc/wpasupplicant.conf. I guess it is getting corrupted.
ok leodfs i will try... should be a solution to copy the good version of wpasupplicant.conf and then when the box restart with wifi error paste the correct file on the corrupted?
I have found that is possible to restart the wifi module with a number combination but our box doesn't have phone module...
What do you think? I'm using the firmware of 7.03.2012 with the link
For non chinese users, you have to download two part from the link and then rename the file erasing the little cubes character in the file names otherwise zip will give you error corrupted files...
When i come back to home i will share build.prop and vending.apk...
ok leodfs i will try... should be a solution to copy the good version of wpasupplicant.conf and then when the box restart with wifi error paste the correct file on the corrupted?
I have found that is possible to restart the wifi module with a number combination but our box doesn't have phone module...
What do you think? I'm using the firmware of 7.03.2012 with the link
For non chinese users, you have to download two part from the link and then rename the file erasing the little cubes character in the file names otherwise zip will give you error corrupted files...
When i come back to home i will share build.prop and vending.apk...
this wifi problem is very bad and annoying...
Thanks...but the link is not working. Never mind, I got the 7 March firmware from the vendor. Not sure what are improvements on this version when comparing with the Jan version.
Do you want me to get wpasupplicant.conf from my box?