• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

[SOLVED] rooting IDER A10 box

I have the same problem. Please, upload the file once again

for those who still need the files... here they are:

update file (using stock "upgrade" apk)

update.root.yareg.march.2012.zip - download here

UimageRecovery (just in case u need it)

uImage_recovery - - download here

I did it, just a minute ago and works nice like a charm!

I'll this post as [SOLVED] in order to make it easy for the community to find out the IDERA10 rooted!!!

my special txs to @wolfgangpauli for finding the rooting method. Genius! my credits for u ;-)
 
Hola Walter,
Muchas gracias por todo y saludos cordiales desde el viejo continente ;-)

To clarify things:
THE REAL GENIUS IS YAREG, SO WE ALL HERE THANK HIM.
I just did the risky experiment to try if his method words for our box.

Sorry, I did not follow this thread recently. So thanks again for doing my job and reposting the files from yareg.

Cheers,
wolfgang

PS: My box is still out of order. Want to get all switches from the PCB to the casing...
 
Sorry for not responding earlier. In the meantime Walteroa did my job and reposted the necessary files.
Could you please drop a message here if you finally got it rooted?

Thanks,
wolfgangpauli
 
Dear wolfgangpauli Thank you for you effort to root this device, but i am unable to download the firmware to root it, kindly will you please re upload the files again, i will be feeling much obliged , thanks again :)

Sorry for not responding earlier. In the meantime Walteroa did my job and reposted the necessary files.
Could you please drop a message here if you finally got it rooted?

Thanks,
wolfgangpauli
 
Hola Walter,
Muchas gracias por todo y saludos cordiales desde el viejo continente ;-)

To clarify things:
THE REAL GENIUS IS YAREG, SO WE ALL HERE THANK HIM.
I just did the risky experiment to try if his method words for our box.

Sorry, I did not follow this thread recently. So thanks again for doing my job and reposting the files from yareg.

Cheers,
wolfgang

PS: My box is still out of order. Want to get all switches from the PCB to the casing...

Hi wolfgang... just let me know how can I help (board pictures or others..)
Cheers!
 
Hello,

Here - as requested - I share the UART infos:

uart.jpg



uart2.jpg



Here is my assembly of the android box at the left hand side connected to a notebook via a cheap
1
USB-to-UART converter. You can get this device really cheap for some dollars from
1
ebay.

The UART on the PCB of the android box is a 6-pin connector. Have a look at the PCB at the left and right-hand side of the connector. The numbers "1" and "6" indicate the numbering.

UART ----> UART-USB-Converter

1 ------------> not connected
2 ------------> TX
3 ------------> not connected
4 ------------> RX
5 ------------> not connected
6 ------------> GND (it is the bottommost connector in the upper picture and the black connector on the right
hand side of the lower picture)

Don't be confused that there is NO VCC (+5V). DON'T ever connect +5/+3.3 of the UART-USB-Converter to a terminal of corresponding voltage of the android box !!!

There are ONLY 3 (!) connections between the box and the UART-USB-Converter

The UART-USB-Converter is attached to a virtual serial port. Under Linux /dev/ttyUSB0 (or similar) or a COM port under MS-Windows. Use the program "putty" to read from / talk to the box @ 115 200 baud, 8-N-1
Connect everything first, start putty and THEN power on the android box. It immediately starts to talk (no screen @ android hdmi required) via its bootloader "uboot".

Be aware that via putty you can communicate with the android box. The keyboard mapping is completely odd.

Here is a GNUmeric file (freeware spread sheet software) with the keyboard mapping (for a German keyboad).
The codes here are "ALT" codes, i.e., if you keep the "ALT"-key pressed and enter "43" the you get a "j" and so on. The mapping is fairly complete for ordinary use (booting, etc).

I use PERL scripts to send sequences of characters as commands to the android box.


Hope this helps.
If further information is required, pls., drop me a note here. I keep following the discussions... ;-)

Cheers & good luck,
wolfgang
 
Hi guys,

I've been reading through this thread with some interest. I have a Sumvision Cyclone Android MKV Media Player which looks like it is the same box.

The update.zip file seems to be pretty straightforward, a script to place superuser and su in the right directory and give them the correct permissions. This would fit with information I have from elsewhere that these boxes have a rooted kernel by default, they just need su and superuser to take advantage of that.

I tried bthovens method but the screen went blank after the "A9" logo. Is this right? Should I have waited longer? (I gave it about two minutes before panicking and rebooting).

I already have the Sumvision uImage_recovery file in the root of the sd card. Is uImage_recovery.bin solely for the Ider A10?
 
I think your problem may be the incorrect name of uimage recovery. It was the same with me, check my previous post, n 32.

what do you mean by kernel enabled root? :-)
 
Hi leodfs. I have already the Sumvision file uImage_recovery in the root of my sd card, which has worked fine to upgrade the OS from 2.3.2 to 2.3.4. I wrote the name wrongly in my post (now amended) but it was right, or are you referring to the difference between uimage_recovery and uimage_recovery.bin? Is the device you describe rooting a Sumvision too?

As regards to rooted kernel that is how I rooted my Galaxy S, installed a rooted kernel from Chainfire along with su and superuser. I assume the kernel of these machines is already rooted. Or have I misunderstood the rooting process?
 
OK. I figured out why my screen was going blank, the unit was connected via AV and the system recovery only works in HDMI

Having connected via HDMI and run "Apply Update" I get the following:
Finding update package...
Opening update package...
Verifying update package...
E:failed to seek in tmp/sideload/package.zip (Invalid argument)
E:signature verification failed
Installation aborted

Help anyone?
 
Hi dude, unfortunately the update file is not for your device. As you noticed, it put some important files on the /system folder and set special permission to the su binary.

For that power, those update files must be signed correctly, according to your system's recovery..

You can try to use Ider A10 recovery image on the root of your sdcard, but you must rename it according. It may not work, when i tried to do it with the recovery of your device, it loaded, but i couldn't use the remote to navigate.
 
I think that what chainfire did was an exploit to the kernel to have root permissions and then do manually what you see on the update.zip.

In a way every android/linux devices are rooted, because they have the root user. What people call "root the device", is in fact give the control of that user for the owner B-).
 
Hmm. If I can install CWM Recovery I can turn signature verification off and install the update via CWM Recovery.

Update: CWM doesn't have a recovery mod for this device. Grr!
 
Update. I discovered the update.zip file had become corrupted during transferral from my Android phone to my Sumvision.

Transferred the file again from desktop to sd card, ran "Upgrade" from applications and selected yareg's file and the upgrade was successfully installed.

I now have a rooted device and am experimenting with vnc server/viewer combinations to control the box from my phone!
 
I never do. I've got VNC working, almost. The problem is input. Anyone have any ideas on how to get that working with these devices?
 
No, I can do that already with the OEM remote control.

What I'd like to do is open applications and select options on the Sumvision from my phone. I use ES Explorer for media streaming as it works really well, 10 times better than XBMC but it hasn't got a good 20ft interface.

I am using a VNC server on the box that allows me to enter paths for keyboard and touchpad. I've found; event0, event1, mice, mouse0 and mouse1 in /dev/input/ but have had little success trying to use these.
 
Did anyone successfully fix the wifi? I have reflashed with stock rom but still receiving wifi "ERROR" when trying to enable.
 
Hi, Im trying to install the firmware and the android 2.3.4 install but
im having this trouble:
assert(!less_than_int(1323765653, getprop("ro.build.date.utc")));

im need it so bad i cant find this update all over the network,
any idea anyone?
TNX
 
Hi, Im trying to install the firmware and the android 2.3.4 install but
im having this trouble:
assert(!less_than_int(1323765653, getprop("ro.build.date.utc")));

im need it so bad i cant find this update all over the network,
any idea anyone?
TNX


Since links become outdated here I post a complete firmware (Android 2.3.4) set in order to get the box rooted:

1) Download these 3 files to a fat formatted SD card

https://www.dropbox.com/s/tsj62km8aeo3p66/uImage_recovery

https://www.dropbox.com/s/73krx346zsqcs1a/c03ref-ota-eng.rwf.zip

https://www.dropbox.com/s/tyrz0ivl3rs0x1p/update.root.yareg.march.2012.zip


You need these 3 files at once on the SD card, c03ref-ota-eng.rwf.zip is the android firmware, uImage_recovery is the recovery software (android recovery) and update.root.yareg.march.2012.zip is Yareg's rooting update (once again thanks to him, since he did all the actual work. I was just the first to apply his patch to our box).

2) put the SD into the SD slot of the box, press down the update button and power up the box. Release the update button.

2a) alternately with remote control: put the SD card into the slot, attach the power supply, switch off the devices (red led lit). Press the update button and press the power switch of the remote control


3) Both ways 2 or 2a should bring you to recovery mode. Keep in mind that concerning this box the uImage_recovery and the c03ref-ota-eng.rwf.zip fit perfectly together. This means you can find many files with these names, but in general they do not fit together and then you get e.g. error messages like

assert(!less_than_int(1323765653, getprop("ro.build.date.utc")));

4) When in recovery mode (This uImage_recovery allows you to browse through the recovery menu by USING THE REMOTE COMMAND "UP" and "DOWN" and "ENTER" button. No external keyboard needed here).

5) In the recovery menu go to UPDATE -> /sdcard/ and chose c03ref-ota...
press enter and wait till it is done.

6) wipe the caches and do a factory reset

7) follow the instructions 1-5, but in point 4 chose update.root.yareg.march.2012.zip
(this will modify permissions in the firmware and copy superuser.apk and su to the box)

8) reboot

9) you will now have a fully rooted android TV box running Android 2.3.4


10) Have fun!


Legal disclaimer:
I have tested this procedure with my box. I cannot guarrantee that this will work for you. By no means I may be held responsible for any damages to your device!
If you do not know what you do, better hands off!

Best regards,
wolfgangpauli
 
Back
Top Bottom