UG007 Original firmware?

[DavX]

Thanks DavX, the Finless ROM 1.4 is now also working on my UG007

I just hat some touble with windows 8 and the driver. Your drivers wasnt working for me anyway, i used the driver which are included in the firmware.

If you are jusing Windows 8 x64 you have to disable the Driver verification (its a little bit tricky)

i have kubuntu 64 bit, win 7 64 bit, win 8 64 bit...but for this works i use only win xp 32bit !!!

the differents between mx1 and ug007 stock rom:

- root on mx1
- different animation on load
- original rom have a icon for hide the android bar

but i used the original rom only few minute....it brick at third reboot!!

[andrea_ita]

Also I have used my UG007 for 2 hours, I see a film in streaming and the STOP working

[vincenzo697]

Update to the new imito stock firmware and after flash only the kernel from imito finless 1.4 Rom so WIFI to work. For me this is the best companion for full working firmware untill BOB does his magic again.

[Fitzy]

Hi there. I am having some real trouble fixing my bricked device.
I received it yesterday, plugged it in and it booted up fine, let me connect to WiFi and enter in my google details. It then proceeded to update from the Playstore and froze. That's the last time it worked. I have tried different cords, usb plugs etc. It wont even boot up now and I know I selected 'Allow USB debugging', but it doesn't appear to have worked.

I now can't flash anything because it is not recognised as being connected in ADB. I tried the short-out method but couldn't get that to work. I have the drivers installed on my PC, but when I try to use the Flash Tool included in the MX1 Rom download from here it tells me that there is no msc device connected (it does say 'Found RKAndroid Loader Rock Usb' down the bottom. I also don't know how I am supposed to see something on the screen as I am only connected to the PC via the mini-usb plug. Am I supposed to have it connected via the HDMI plug into a TV as well ? Not sure how I would do that and be able to short out the plugs.

Would really love some help please. I am going nut's trying to make it work. I'm not stupid, but feel like it at the moment.

Cheers

[lambstone]

I am able to flash the MX1 custom rom by bob and everything seems to be working fine.

However, since there is no touch screen, it seems that the touch emulation by sixaxis controller app will not work. Does anyone have any ideas on making it work?

[Fitzy]

anyone,pl easehelp.

[loociddreemr]

anyone,pl easehelp.

Besides selecting USB debugging, you might also have to select "connect to PC" mode from the menu settings >USB.

[Fitzy]

Besides selecting USB debugging, you might also have to select "connect to PC" mode from the menu settings >USB.

Thanks for the reply mate. Prob is that I can't get it to boot at all so I can't select anything ..

[loociddreemr]

Ah, I see. I'm working on a system dump. If I can get it, than I'll figure out how to help you use it to flash the original firmware.

[Fitzy]

Ah, I see. I'm working on a system dump. If I can get it, than I'll figure out how to help you use it to flash the original firmware.

Thanks a lot mate.

[loociddreemr]

I need help dumping the system. I am using romdump. I am able to sucessfully complete the dump, but I cannot locate the dumped files. Any suggestions?

heres my CMD screen for the first pass

adb push romdump /data/local/
3076 KB/s (1149900 bytes in 0.365s)

adb shell
root@android:/ # chmod 755 /data/local/romdump
chmod 755 /data/local/romdump
root@android:/ # /data/local/romdump
/data/local/romdump
Android ROM dumper v0.82b
(c)2011 Sebastian404
Device : rk30sdk-eng 4.1.1 JRO03H eng.ant.20121108.175527 test-keys

Creating required files... done.
Opening mtd table... done.
Dumping kernel config... sh: cat: /proc/config.gz: No such file or directory
done.
Dumping boot partition... done.
Dumping recovery partition... done.
Dumping system partition... done.
Creating Checksums... done.
Cleaning up... done.
All done.

I couldn't find the dumped files so I tried again, but it says that the files already exist.

adb shell
root@android:/ # /data/local/romdump
/data/local/romdump
Android ROM dumper v0.82b
(c)2011 Sebastian404
Device : rk30sdk-eng 4.1.1 JRO03H eng.ant.20121108.175527 test-keys

Creating required files... gzip: can't open '/sdcard/romdump//system.info.gz': F
ile exists
done.
Opening mtd table... done.
Dumping kernel config... sh: cat: /proc/config.gz: No such file or directory
done.
Dumping boot partition... done.
Dumping recovery partition... done.
Dumping system partition... done.
Creating Checksums... done.
Cleaning up... done.
All done.

[loociddreemr]

Firmware can be extracted using ADB. You can dump it with DD (do not try to use rkdump). What we need is backup.img if it is not blank. If it is blank, we need all the other IMG and will have to make up a parameter file.

See this post for how to dump:

http://www.freaktab.com/showthread.php?401-Dumping-ROM-using-ADB-guide

Bob

Bob,

As you can see, I'm working on the system dump. You can see from my previous post that I'm having troubles retrieving the files after the romdump. With DD comands, I'm more sucessful. I need help with the file extensions though. What will I need from the following partitions and what format/extension?

root@android:/ # cat /proc/mtd
cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00400000 00004000 "misc"
mtd1: 00800000 00004000 "kernel"
mtd2: 01000000 00004000 "boot"
mtd3: 01000000 00004000 "recovery"
mtd4: 18000000 00004000 "backup"
mtd5: 08000000 00004000 "cache"
mtd6: 20000000 00004000 "userdata"
mtd7: 00400000 00004000 "kpanic"
mtd8: 20000000 00004000 "system"
mtd9: 175000000 00004000 "user"

Heres an example of the recovery partition

root@android:/ # dd if=/dev/mtd/mtd3 of=/sdcard/recovery.img
dd if=/dev/mtd/mtd3 of=/sdcard/recovery.img
32768+0 records in
32768+0 records out
16777216 bytes transferred in 0.817 secs (20535148 bytes/sec)

Is this correct?

[Finless]

Yes your doing it right. Most devices backup.img contains the full original ROM flash. So we want to try and get that first. If it is blank then we need
system, boot, recovery ata minimum. Also see if you can dump the begining of NAND to get the parameter file details. Linux RKflash tool should be able to grab that.

Bob

[loociddreemr]

Yes your doing it right. Most devices backup.img contains the full original ROM flash. So we want to try and get that first. If it is blank then we need
system, boot, recovery ata minimum. Also see if you can dump the begining of NAND to get the parameter file details. Linux RKflash tool should be able to grab that.

Bob

Bob,

How do I dump the beginning of NAND to get the parameter file details? Is this done with your tool? If not can you send me a link to the tool that I need? If I have to use terminal or adb shell commands, can you give me some pointers?

[Finless]

On XDA is a post about a linux based RKFLash tool. I will dump all NAND.

http://forum.xda-developers.com/showthread.php?t=1286305

Bob