Related
i have a fix for restoring product code back to original for the captivate. Working with a vibrant owner who has messed up nv_dat.bin and product code and trying to port my fix for him but need some hex code info to make sure i convert the fix properly.
I am asking any willing vibrant owners who have correct product code (SGH-T959ZKATMB)
to download the free market app HEX EDIT and report some info for me.
What i need to know is the Hex code for 4 specific lines of your correct nv_data.bin (if vibrant)
1. Use Hex Editor App from market (free)
2. Open the nv_data file (once in hex editor use capacitive menu button to get to options)
3. Goto the options again and JUMP TO line 0188008 will take you to line 00188008. Will need the data from it and three other lines you will see below it.
There will 8 block of data between the line # and the text at the right that you reposted. Please post the #'s/letters for each corresponding block so i can ensure that i convert properly.
00188008 | | | | | | | | |
00188010 | | | | | | | | |
00188018 | | | | | | | | |
00188020 | | | | | | | | |
what i would need is the two numeral/letter codes for each of the blocks listed next to corresponding line #'s. Each line has 8 blocks. Also the text to the far right of the final block would help as well.
if preferred you can provide this data in a PM
If you don't want to manually transcribe the data over to a message you could snap a screen shot of the hex editor with these lines visible and post.
00188000 - ff ff ff ff 52 45 56 50 - . . . . R E V 0
00188008 - 2e 33 00 00 00 00 ff 54 - . 3 . . . . . T
00188010 - 4d 42 00 00 00 00 53 47 - M B . . . . S G
00188018 - 48 2d 54 39 35 39 5a 4b - H - T 9 5 9 Z K
00188020 - 42 54 4d 42 00 00 00 00 - B T M B . . . .
00188028 - 00 00 01 50 02 4e 03 4e - . . . P . N . N
silow said:
00188000 - ff ff ff ff 52 45 56 50 - . . . . R E V 0
00188008 - 2e 33 00 00 00 00 ff 54 - . 3 . . . . . T
00188010 - 4d 42 00 00 00 00 53 47 - M B . . . . S G
00188018 - 48 2d 54 39 35 39 5a 4b - H - T 9 5 9 Z K
00188020 - 42 54 4d 42 00 00 00 00 - B T M B . . . .
00188028 - 00 00 01 50 02 4e 03 4e - . . . P . N . N
Click to expand...
Click to collapse
thank you much
will let you know if this helps him.
Hi
I have recently bought a Samsung Galaxy S2 I9100P locked on Orange France.
I have tried to unlock it using th nv_data method.
What I did was to modify the nv_data.bin file and put FFs @ offset 0x180049.
But apparently it didn't work since it still says network lock.
I have compared with several nv_data files from this forum (original and patched) reported to work and I have seen that the number of non FFs is larger in my file
For example in a file on this forum I find these bytes @ offset 0x180049:
32 33 34 33 30 23 32 33 34 33 31 23 FF FF FF FF FF FF
While in my file I have:
32 30 38 30 31 23 33 34 30 30 31 23 36 34 37 30 30 23
I am attaching the file here maybe someone can figure it out.
Furthermore in my /efs directory there is another hidded .nv_data.bak that is different from my original nv_data.bin What is with that file ?
Thanks
Hey guys... I need help!
Let me tell a little history about my E10a.
I'd buyed my phone with simlock enabled.
I'ved try many free ways to unlock sim, but nothing has works.
Looking at youtube and internet, i'ved found a way to do this using "Omnius for SE".
Worked fine using original kernel.
To unlock bootloader i'ved try to use Flashtool. But, because the simlock status was different to SEMC, the only way i found to flash TFT was using Omnius too.
Today I decided to update my phone.
I'ved download last version of Omnius, downloaded 2.6.32.60-nAa-jb-02 kernel.
Let's flash!
At first time, Omnius has show me a message telling me: You can't update your kernel because you don't have credits anymore and blablabla...
I forced to update checking the "Unsigned flashing".
So, now my phone wont power up anymore. I'ved try force shutdown using power + home, but nothing happens.
Sorry my very poor english. I'm from Brazil and I'm very nervous about this situation.
Plz anyone can help me? My experience with flashing android phones was since out'11. I'm not total n00b.
Next, the last log showed in Omnius:
Code:
Action journal
14:55:49 Flash
14:55:49 Allows to change languages supported by the phone and upgrade its firmware.
14:55:49 Operating system: Microsoft Windows 7 Home Premium Edition Service Pack 1 (build 7601), 64-bit
14:55:49 Application version: 1.40.4823
14:55:49 . The action name is 'Flash'
14:55:49 Selected phone type: Xperia™ X10 mini
14:55:49 i Instructions
14:55:49 i 1. Make sure the phone battery is charged to at least 50%.
14:55:49 i 2. Switch off the phone!
14:55:49 i 3. Remove the phone battery and wait at least 5 seconds, then insert the battery back to the phone!
14:55:49 i 4. Press and hold the return back button, then connect the cable to the phone!
14:55:49 . The action started waiting for the user
14:55:57 . The action finished waiting for the user
14:55:57 Connecting via SEMC USB Flash Device (USB2)...
14:55:57 Device driver version: 3.0.0.0
14:55:57 Detected chipset: MSM7227
14:55:57 Boot mode: EROM
14:55:57 IMEI: 01231300503142
14:55:57 Sending loader...
14:55:59 i Waiting for connection to the server...
14:56:05 Receiving news...
14:56:06 i News
14:56:06 i Omnius for Samsung v1.18 - Experimental unlock code read for Samsung Galaxy S II and similar, FREE
during test period
14:56:06 i Omnius 1 Year licenses purchased after 1st Oct 2011 now gained
unlimited android unlocking!
14:56:11 Unlocking loader...
14:56:16 i Unsigned flashing is enabled.
14:56:16 Writing file X10_V1_BLRelock.ftf...
14:56:20 e Failed!
14:56:20 . The action entered shutdown phase
14:56:20 . The action reported failure
Error code
# 973C36BE0FC7F2B7
Error details
---
67 5B 47 A0 8F 07 C1 3C D3 F0 24 A5 87 5E D7 31
FA 32 7D 70 C3 C1 C1 03 23 52 65 F4 D0 EF F9 26
4B 79 1D 41 7F 86 9F 12 8D 2E CB 30 27 D1 4E F1
35 1B 1D 90 31 FC 06 C3 68 3C 55 05 77 AE 99 7C
22 5D B8 92 E1 9A FF 76 56 F0 79 77 6A A7 C1 B1
69 6F 17 E9 AC F4 62 55 D7 5D 09 EA D2 37 6B 4E
D4 F5 3F 81 EC 15 62 FE 00 C7 C6 07 CB A7 56 97
97 07 F0 83 2D 71 34 9E 51 51 E8 0C 08 3A 90 87
E8 08 9B 61 0C 92 1E EA E8 CC C9 A3 42 8C 05 EB
3F C3 4D B1 E2 DF AC 69 7F 94 8C E6 C8 22 A7 C0
AA 82 AC 20 77 9F 6D F5 95 2B 28 E9 2D D7 D8 02
C5 1C FC 99 DD 13 2B AE 86 B2 D5 79 09 D2 19 76
09 09 DE 83 CF DB 81 7C 93 2C AB B8 B9 5A 17 67
3C BC 6D 31 11 56 51 9E C0 61 FB 06 C7 13 B9 9C
0B 3C D3 82 AB 45 71 45 CD 02 F5 32 5E B3 55 CC
F5 6A 23 B0 8F C4 F1 4C 83 8A F6 FE 74 38
---
Thank's a lot for any help!
Format /system
Hello,
did you format /system before flashing the new kernel?
http://forum.xda-developers.com/showthread.php?t=2138771:
Read through this post. Don't rush into flashing. Be sure you understand the process before you start or you risk damaging your device
This is a custom 2.6.32 kernel developed for Android Jellybean 4.x. This kernel only works for mimmi, a.k.a. X10miniPro
Do NOT try this kernel on other Android versions or phones - you are totally unsupported
This kernel uses a custom mtd partitioning with larger /system partition to hold the extra JB calories. If you are moving from another custom kernel, EXCEPT 2.6.29-nAa-jb to this one, you MUST first format /system /data and /cache via the embedded CWM recovery
Click to expand...
Click to collapse
gmamorim said:
Hey guys... I need help!
14:56:11 Unlocking loader...
14:56:16 i Unsigned flashing is enabled.
14:56:16 Writing file X10_V1_BLRelock.ftf...
14:56:20 e Failed!
Thank's a lot for any help!
Click to expand...
Click to collapse
You didn't flash the nAa-kernel but the Bootloader Relock kernel for the X10, your phone is probably bricked. If you can't get it into flash-mode anymore, it may need JTagging at a repair shop to get it back up working.
phone bricked, because it flashed the X10_V1_BLRelock.ftf, you will need to take it to a repair shop.
Do your PC react when connect the phone via USB?!
ferotakis said:
Do your PC react when connect the phone via USB?!
Click to expand...
Click to collapse
No... don't react
another newbie who bite the disaster...
Sent from my E10i using xda app-developers app
R3v3nGe said:
another newbie who bite the disaster...
Sent from my E10i using xda app-developers app
Click to expand...
Click to collapse
Thank you guy so much!
That's i want to hear...
...NOT!
Man, if you can't help, don't post things like this!
This is bull****! And won't help anybody!
Or maybe you think have a bigger post count is a great advantage!
"Another forum newbie..."
How old r u? 15?
hi bro does your x10 mini bootup or not??? sorry bro.... im only 14 years old and post count and rank does not matter here... this is a forum that has no competition...
Sent from my E10i using xda app-developers app
You hardbricked your phone, your bootloader is damaged.
JTAG is the solution, search for a repair center.
Hello all,
My device
I have a Rikomagic MK 802 IIIS mini PC with the following specs:
Model MK802 IIIS 8GB Dual Core
CPU RK3066 Dual Core - Cortex-A9 Up to 1.6GHz
GPU Quad- Core 2D/ 3D/ OpenGL ES2.0(AMD Z430)/ OpenVG1
OS Android 4.1
RAM 1GB DDR3
Memory 8GB Flash
Expansion Micro SD T-Flash(Maximum support 32GB)
Video Format WMV/ASF/MP4/3GP/3G2M4V/AVI/MJPEG/RV10/DivX/VC-1/MPEG-2/MPEG-4/H.263/H.264/1280*720P HD 30 fps, 1080P/720*480 D1 30fps
Audio Format MP3/WMA/APE/FLAC/AAC/OGG/AC3/WAV
Picture format Max.8000x8000 JPEG BMP GIF PNG
WiFi 802.11 b/g/n
Flash Supports flash 11.1
HDMI(male),Micro SD slot, USB host*1,USB OTG*1, USB power port; LED(Blue)
My primary problem (long story short): I managed to brick the MK802 IIS device in the process of installing Pi****u Linux on it. After trying to install the Linux kernel on the recovery partition manually, by doing from Android cmdline "busybox dd if=ug802recovkernel.img of=/dev/block/mtd/by-name/recovery bs=8192" and then "su" and "reboot recovery", I ended up with a non-booting system. I tried several times power off + power on cycles, but Android is not loading anymore. So, I would like to reflash the factory firmware on my device, to have the Android 4.1 booting again ... and I know about RKAndroidTool v1.35 for Windowses, but ...
... I am not using Windows OSes (better said, I avoid using them as much as I can, by trying to find *nix based solutions).
Therefore my main question: Is there Linux software to restore factory firmware on a Rikomagic MK802 IIIS device?
During my research, after googling for "rkandroidtool for linux" I found this promising link on our XDA community: http://forum.xda-developers.com/showthread.php?t=1286305
This "rkflashtool for Linux and rk2808, rk2818 and rk2918 based tablets" is reported to work fine by many, and later on in the above thread, user "frankjt" says:
there are good news, updated with ProductID 0x300a like this:
. . .
if (!(h = libusb_open_device_with_vid_pid(c, 0x2207, 0x300a)))
. . .
rkflashtool works on Cube's rk3066 tablets too (all functions: r, w, b).
Thanks to Ivop's excellent tool my Cube U30GT-H (firmware 1.02) is rooted now.
Click to expand...
Click to collapse
So, it seems this rkflashtool for Linux does a great job on rk3066 tablets, but is it working on mini PCs too?
Has anyone tried this tool on miniPC ? Preferably Rikomagic MK802 IIIS, but if you have experience on similar models, please share them here.
Is there a guide on how to reflash miniPCs with Linux software only? Please post it.
What are the hexadecimal addresses to be used when attempting to write an .img file on the Rikomagic MK802 IIIS mini PC?
Any advice, or feedback on these questions are very welcomed!
Regards.
Hi,
Doing a little bump of this thread.
After doing more google research, this time for "rk3066 flash tool linux" I've found:
armtvtech dot com and the rest of the link is: /armtvtechforum/viewtopic.php?f=66&t=350
slatedroid dot com and the rest of the link is: /topic/42826-flashing-rk3066-with-linux/
So definetly I'm not a singular case in my frustrations.
It seems that recommandations point to the rkflashtool that I mentioned in my previous post:
arctablet dot com and the rest of the link is: /wiki/index.php/Update_tablet_using_Linux (see the "Preparation" section)
Now the main question that remains: Anyone tested (successfully or not) Linux rkflashtool on a Rikomagic MK 802 IIIS mini PC?
Or, to put it simpler: Anyone tested Linux rkflashtool on any RK3xxx based android stick computer (aka mini PC) ?
If yes, please post your stories here.
PS: Sorry for the cryptic weblinks syntax, but I am still a new member, not allowed to post these ..
PSS(off-topic): Sorry for giving Pic Untu a "bad name" in the opening post, it wasn't my intention
Never mind, I was thinking of a different device.
Sent from my One X using xda app-developers app
---------- Post added at 08:49 PM ---------- Previous post was at 08:37 PM ----------
This person reports success with rkflashtool on an mk808: http://www.slatedroid.com/topic/460...08-from-linux/page__view__findpost__p__631970
ragesoss said:
Never mind, I was thinking of a different device.
Sent from my One X using xda app-developers app
---------- Post added at 08:49 PM ---------- Previous post was at 08:37 PM ----------
This person reports success with rkflashtool on an mk808: slatedroid com /topic/46001-writing-images-to-the-mk808-from-linux/page__view__findpost__p__631970
Click to expand...
Click to collapse
Thanks a lot, ragesoss!
I read the tutorial and the feedback, looks very promising!!
I'll test it myself on my MK802 IIIS and post the results here.
Very frustrating: seems that rkflashtool restore isn't working on Rikomagic MK802IIIS
First of all, the explanation for why I bricked my Rikomagic MK802 IIIS: when trying to install Pic Untu, I did that dd command on the recovery partition (see the first post in this thread for the exact command). Well, the procedure is not working like this because when accessing the mtdblock devices with normal *nix commands (dd, cat), the mtdblock Android driver is not handling I/O as usual and it causes data corruption on all the mtd device. That's why I bricked the device.
So, not having a backup before, I had to use a WindowsXP vmware VM with windows RK flashing utility. I restored the device to firmware "Rikomagic MK802IIIS 4GB, 8GB Recovery Software (20130121)" downloaded from rikomagic.co.uk.
Restoring was successfull so here I am with a fully functional Android which boots up OK. All fine for a day...
I decided to make a full device backup using Linux rkflashtool which I downloaded from the thread I mentioned in my first post (http://forum.xda-developers.com/showthread.php?t=1286305), this is the link: http://forum.xda-developers.com/attachment.php?attachmentid=785592&d=1321547155
I modified the source so that the rk3066 chipset is recognized (I added the 2207 usb vendor id).
The OS/computer I've used: Kubuntu 12.04 LTS 64 bit on a Thinkpad T420:
Code:
[email protected]:~# uname -a
Linux awesome 3.2.0-49-generic #75-Ubuntu SMP Tue Jun 18 17:39:32 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Now follows the copy/paste of commands & output of the backup operation, with the mention that: of course I put the device in flashing mode first, using paperclip + power-on cable in device's OTG connector linked to laptop :
Code:
[email protected]:~# ./rkflashtool r 0x00000000 0x01000000 > /mnt/media/mk802iiis_android_backup_20130706.bin
[email protected]:~# du /mnt/media/mk802iiis_android_backup_20130706.bin
8388608 /mnt/media/mk802iiis_android_backup_20130706.bin
[email protected]:~# du -h /mnt/media/mk802iiis_android_backup_20130706.bin
8.0G /mnt/media/mk802iiis_android_backup_20130706.bin
[email protected]:~#
[email protected]:~# hexdump -C /mnt/media/mk802iiis_android_backup_20130706.bin |head -10
00000000 50 41 52 4d 5b 02 00 00 46 49 52 4d 57 41 52 45 |PARM[...FIRMWARE|
00000010 5f 56 45 52 3a 34 2e 30 2e 34 0d 0a 4d 41 43 48 |_VER:4.0.4..MACH|
00000020 49 4e 45 5f 4d 4f 44 45 4c 3a 72 6b 33 30 73 64 |INE_MODEL:rk30sd|
00000030 6b 0d 0a 4d 41 43 48 49 4e 45 5f 49 44 3a 30 30 |k..MACHINE_ID:00|
00000040 37 0d 0a 4d 41 4e 55 46 41 43 54 55 52 45 52 3a |7..MANUFACTURER:|
00000050 52 4b 33 30 53 44 4b 0d 0a 4d 41 47 49 43 3a 20 |RK30SDK..MAGIC: |
00000060 30 78 35 30 34 31 35 32 34 42 0d 0a 41 54 41 47 |0x5041524B..ATAG|
00000070 3a 20 30 78 36 30 30 30 30 38 30 30 0d 0a 4d 41 |: 0x60000800..MA|
00000080 43 48 49 4e 45 3a 20 33 30 36 36 0d 0a 43 48 45 |CHINE: 3066..CHE|
00000090 43 4b 5f 4d 41 53 4b 3a 20 30 78 38 30 0d 0a 4b |CK_MASK: 0x80..K|
As you can see, the resulted backup file has 8 GB size, and the hexdump of it shows the usual stuff for a non-corrupted backup.
Note1: I avoided to "spam" the thread with the whole header of the hexdumped backup file, but I assure you that it has the boot command line with the size/offset of all the partitions. So, it is a backup successfully created.
Note2: The backup operation took about 25-30 minutes, no errors in the system logs.
After backup was done, Android still boots OK, all is fine. Until the nightmare came...
I decided to test the restore process, so I added the device once more in flashing mode (with paperclip & OTG), and did:
Code:
[email protected]:~/rk3066-rkflashtool/rk3066-rkflashtool-master/trunk# ./rkflashtool e 0x00000000 0x01000000
rkflashtool: info: interface claimed
rkflashtool: info: erasing flash memory at offset 0x00ffff00
[email protected]:~# ./rkflashtool w 0x00000000 0x01000000 < /mnt/media/mk802iiis_android_backup_20130706.bin
...
...
...
rkflashtool: info: writing flash memory at offset 0x00fffe80
rkflashtool: info: writing flash memory at offset 0x00fffea0
rkflashtool: info: writing flash memory at offset 0x00fffec0
rkflashtool: info: writing flash memory at offset 0x00fffee0
rkflashtool: info: writing flash memory at offset 0x00ffff00
rkflashtool: info: writing flash memory at offset 0x00ffff20
rkflashtool: info: writing flash memory at offset 0x00ffff40
rkflashtool: info: writing flash memory at offset 0x00ffff60
rkflashtool: info: writing flash memory at offset 0x00ffff80
rkflashtool: info: writing flash memory at offset 0x00ffffa0
rkflashtool: info: writing flash memory at offset 0x00ffffc0
rkflashtool: info: writing flash memory at offset 0x00ffffe0
Note1: Writing operation took 2 hours and 8 minutes, no errors in the system logs..
Note2: ... but it was the end of my working mk802iiis !
When I reconnected the device, Android won't boot, instead the device seems to enter the flashing mode again. I say it "seems" because I am not really sure, actually it should not even attempt to enter flashing mode because I'm not touching the little oriffice with the paperclip.
So that's it on short: Android does not start!
When I specifically manually entered flashing mode again, I tried to read several megabytes from near the start addresses of the flash memory. Unfortunately, I get garbage:
Code:
[email protected]:~# hexdump -C recoverytry.bin |head -10
00000000 ae e6 ff a7 75 26 3e 6f ee b7 d3 66 33 f7 e7 fa |....u&>o...f3...|
00000010 97 b4 e6 fe bf da 10 4e 70 b6 a7 d9 db 9f 3b b7 |.......Np.....;.|
00000020 6b 3d f6 7f fe ff bf 5e e1 af ef 3e ff df 93 f7 |k=.....^...>....|
00000030 d7 ee 3f ef 31 d2 cb cc ef eb db f7 f7 ff 7f e7 |..?.1...........|
00000040 cf 6d 96 e9 dd a5 d6 9f f7 11 67 ef 6d dc dd fd |.m........g.m...|
00000050 5e 4b f3 77 7d fd bd cd 9f 15 f9 17 83 fb f7 5b |^K.w}..........[|
00000060 b9 11 fd 61 b4 cd dd 93 b9 f7 de d7 f8 d1 9b ef |...a............|
00000070 76 fe bf 1f 67 77 f5 5f 67 e2 97 96 15 f7 ae 7f |v...gw._g.......|
00000080 e4 ce 7d e5 36 fb fe 56 ce e6 fb ca f3 f7 d0 37 |..}.6..V.......7|
00000090 3d af 49 cd d5 71 ff f9 33 db fe 34 f6 17 d3 1d |=.I..q..3..4....|
Compare the output above with the first 10 lines of my backup file posted earlier and you can understand what I mean by garbage.
So to resume:
1) I managed to create a correct backup of mk802iiis using rkflashtool ("rkflashtool r" worked as expected)
2) Rkflashtool failed to restore the backup ("rkflashtool w" doesn't work, at least not for restoring all 8 GB).
Does anyone experienced similar situations?
Is 8 GB too much to backup at once?
Is there some workaround for this?
Could be a PC problem or device problem?
Is 2 hours too long(or too short) for flashing 8 GB to NAND?
Please help.
Regards,
Lexminriko
An important omission from my previous post (my apologies for not realizing the importance of the following):
Using Linux rkflashtool on my Kubuntu 12.04 64bit I was able to successfully backup /restore partitions.
For example, I could restore recovery partition with the command:
Code:
./rkflashtool w 0x000010000 0x000008000 < /mnt/media/mk802iiis_original_recovery_part_20130706.bin
The "brickeage" occured only when I tried to restore all NAND in one step, with the command already mentioned in my previous post:
Code:
./rkflashtool w 0x00000000 0x01000000 < /mnt/media/mk802iiis_android_backup_20130706.bin
Main questions remain:
Anyone experienced similar situations on Rikomagic MK802 IIIS ?
Is there a way to fix this bricked device in Linux(with rkflashtool or other Linux software), given the command that caused the damage?
If you experienced similar troubles, please post.
Regards,
Lexminriko
lexminriko said:
Hello all,
My device
I have a Rikomagic MK 802 IIIS mini PC with the following specs:
Model MK802 IIIS 8GB Dual Core
CPU RK3066 Dual Core - Cortex-A9 Up to 1.6GHz
GPU Quad- Core 2D/ 3D/ OpenGL ES2.0(AMD Z430)/ OpenVG1
OS Android 4.1
RAM 1GB DDR3
Memory 8GB Flash
Expansion Micro SD T-Flash(Maximum support 32GB)
Video Format WMV/ASF/MP4/3GP/3G2M4V/AVI/MJPEG/RV10/DivX/VC-1/MPEG-2/MPEG-4/H.263/H.264/1280*720P HD 30 fps, 1080P/720*480 D1 30fps
Audio Format MP3/WMA/APE/FLAC/AAC/OGG/AC3/WAV
Picture format Max.8000x8000 JPEG BMP GIF PNG
WiFi 802.11 b/g/n
Flash Supports flash 11.1
HDMI(male),Micro SD slot, USB host*1,USB OTG*1, USB power port; LED(Blue)
My primary problem (long story short): I managed to brick the MK802 IIS device in the process of installing Pi****u Linux on it. After trying to install the Linux kernel on the recovery partition manually, by doing from Android cmdline "busybox dd if=ug802recovkernel.img of=/dev/block/mtd/by-name/recovery bs=8192" and then "su" and "reboot recovery", I ended up with a non-booting system. I tried several times power off + power on cycles, but Android is not loading anymore. So, I would like to reflash the factory firmware on my device, to have the Android 4.1 booting again ... and I know about RKAndroidTool v1.35 for Windowses, but ...
... I am not using Windows OSes (better said, I avoid using them as much as I can, by trying to find *nix based solutions).
Therefore my main question: Is there Linux software to restore factory firmware on a Rikomagic MK802 IIIS device?
During my research, after googling for "rkandroidtool for linux" I found this promising link on our XDA community: http://forum.xda-developers.com/showthread.php?t=1286305
This "rkflashtool for Linux and rk2808, rk2818 and rk2918 based tablets" is reported to work fine by many, and later on in the above thread, user "frankjt" says:
So, it seems this rkflashtool for Linux does a great job on rk3066 tablets, but is it working on mini PCs too?
Has anyone tried this tool on miniPC ? Preferably Rikomagic MK802 IIIS, but if you have experience on similar models, please share them here.
Is there a guide on how to reflash miniPCs with Linux software only? Please post it.
What are the hexadecimal addresses to be used when attempting to write an .img file on the Rikomagic MK802 IIIS mini PC?
Any advice, or feedback on these questions are very welcomed!
Regards.
Click to expand...
Click to collapse
You can use the official Linux tool called 'upgrade_tool' ... simply do a google search for 'linux upgrade_tool' and you'll get a several sites with guides and useful info about it.
hello all, is there a cyanogenmod rom for Acer Liquid Z3 (Z130)
Thanks
bryan-k said:
hello all, is there a cyanogenmod rom for Acer Liquid Z3 (Z130)
Thanks
Click to expand...
Click to collapse
here stock rom for z130 bro : http://www.acer.com.sg/ac/en/SG/content/drivers/4889;-;Z130
:victory:
is there any custom rom that would work on the z3 ?
((
micdarau85 said:
is there any custom rom that would work on the z3 ?
((
Click to expand...
Click to collapse
Mhh, just found this post, was never a ROM for this phone developed?
I just would like to skin down the stock rom and make it lighter...
g
Rom developing
It is possible to root the acer liquid Z3 (Z130) as well as installing TWRP. I'm about to develop Cyanogenmod for it. I hope that admins will give me a thread to start posting instructions:
Howto root it: root it using the app framaroot: http://forum.xda-developers.com/apps/framaroot/root-framaroot-one-click-apk-to-root-t2130276
Howto flash it with TWRP: Install and execute rashr and flash recovery with TWRP:
https://docs.google.com/file/d/0B0XQigIT17uEcDQtaDJ3U0UtOWc/edit?pli=1
The kernel source is availible at http://us.acer.com/ac/en/US/content/drivers
The supposed procedure in getting the z130 specific image is (excerpt of kernel source readme):
Build steps:
1. Download Android 4.2.2 source code from google
2. Modify buildGPL.sh, replace the Your_Toolchain_PATH with your tool path in android code.
for example: android/prebuilts/gcc/linux-x86/arm/arm-linux-androidYour_Toolchain_PATHeabi-4.6/bin
3. Run the script under your shell
./buildGPL.sh
Thanks!
Click to expand...
Click to collapse
I'm happy if I get a companion while developing. If you're new to cyanogenmod you can start with:
http://wiki.cyanogenmod.org/w/Build_for_a700#Build_CyanogenMod_and_ClockworkMod_Recovery
Give me a thread and device section !
Greets,
wendenerp
going on
My main motivation in getting cyanogenmod running is to get a german android system language. Since I bought the Z130 in the Phlippines
it only came with English and a couple of Asian languages. None of the language programs (morelocale2, locale, Sprache) could change the system language to german even while rooted. Today I tried to flash a system partition of the Acer homepages' Update images, namely the OS_Acer_AV052.Z130.1.007.00.LA.GEN1s_A42J_A
TWRP worked fine, but it didn't boot. I could rescue to the old system.ext4.win after the Acers' image failed.
I already contacted Acer. Maybe they will at least tell me which image has the german system language and works with the dual sim kernel... I'm still considering cyanogenmod's images though.
I added some detailed german instructions on rooting the liquid z3 and installing TWRP: http://www.wendenerp.de/Sonstiges.html
So far,
wendenerp said:
My main motivation in getting cyanogenmod running is to get a german android system language. Since I bought the Z130 in the Phlippines
it only came with English and a couple of Asian languages.
Click to expand...
Click to collapse
i have the single sim version with european languages. i wish i could get some asian languages on this phone X)
I started a cyanogenmod project on github for the Acer liquid Z3: https://github.com/wendenerp/android_device_acer_zx. I had some trouble with the local manifest file, but I think this should be alright:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="wendenerp/android_device_acer_zx" path="device/acer/zx" remote="github" revision="cm-11.0" />
</manifest>
Click to expand...
Click to collapse
Next thing is to get the vendor specific programs and drivers out of the original firmware...
I'm having some problems with getting the ramdisk image out of boot.img.
The boot.img is 6 mb in size. I tried unpackbootimg, unmkbootimg and split_bootimg. All of these tools split the same way:
The kernel gets 4mb and the ramdisk 600k, which adds up to 4.6mb. Additionally the ramdisk is of file type data:
Code:
file boot_img.lzma
boot_img.lzma: data
so neither gunzip nor lzma -dc works to extract the initramfs. I assume there is a bug in all of these split tools or acer made up some strange boot.img format...
boot.img split error
Unfortunately the split utilities don't split the boot image correctly.
The image should contain the size and location of the kernel and ramdisk inn the first bytes of the boot.img, but this is how it looks like:
Code:
[email protected]:~/Android-Hacking/z130_full_backup$ hd boot.emmc.win |grep 'ANDROID' -n4
1:00000000 41 4e 44 52 4f 49 44 21 58 36 3d 00 00 80 00 10 |ANDROID!X6=.....|
2-00000010 34 bc 09 00 00 00 00 11 00 00 00 00 00 00 f0 10 |4...............|
3-00000020 00 01 00 10 00 08 00 00 00 00 00 00 00 00 00 00 |................|
4-00000030 31 33 37 37 37 30 33 33 30 39 00 00 00 00 00 00 |1377703309......|
5-00000040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
The split_bootimg.scrip takes the values out of the first too rows in little endian to determine the sizes and locations:
Code:
[email protected]:~/Android-Hacking/z130_full_backup$ ./split_bootimg.pl boot.emmc.win
Page size: 2048 (0x00000800)
Kernel size: 4011608 (0x003d3658)
Kernel location: 268468224 (0x10008000)
Ramdisk size: 638004 (0x0009bc34)
Ramdisk location: 285212672 (0x11000000)
Second size: 0 (0x00000000)
Board name: 1377703309
Command line:
Writing boot.emmc.win-kernel ... complete.
Writing boot.emmc.win-ramdisk.gz ... complete.
Unfortenutely the location exceeds the size of the boot.img:
Code:
[email protected]:~/Android-Hacking/z130_full_backup$ hd boot.emmc.win
...
0046fc30 00 81 11 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
0046fc40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00600000
So it looks like the scipt only pulls some random data from the memory for the kernel and for the ramdisk
In fact the ramdisk starts at a different location:
Code:
[email protected]:~/Android-Hacking/z130_full_backup$ hd boot.emmc.win |grep '1f 8b 08'
00005220 6e 20 65 72 72 6f 72 00 1f 8b 08 00 00 00 00 00 |n error.........|
003d4200 1f 8b 08 00 00 00 00 00 00 03 ec 7d 0b 7c 54 c5 |...........}.|T.|
All 3 split utilities do the same:
unpackbootimg, unmkbootimg, split_bootimg
---------- Post added at 12:41 PM ---------- Previous post was at 11:42 AM ----------
since the bootloader is u-boot I think the image has a different format:
HTML:
http://www.compulab.co.il/workspace/mediawiki/index.php5/U-Boot:_Images#Image_format
progress
I also was able to extract the ramdisk out of the boot.img and added it together with the mkvendor.sh output at github.
I was also able to compile the kernel from sources provided at acer.com. I requested the sources of the u-boot image too.
You are doing great job dude keep going )))
U-Boot Source Code request
This is my request to Acer for the U-Boot source:
Dear Sir/Madam,
thank you for your reply. Software licensed under the GPL2 can be reused and modified and sold with the restriction of handing out the source and build instructions for the sold product.
In case of the Acer Liquid Z130, Acer has aquired and modified the following Software:
Linux Kernel, the Android OS, the U-boot bootloader, of which the linux kernel and U-boot is licensed under the GPL2, meaning that acer is obliged to hand out the source code of its modified U-boot and the modified kernel plus the build instructions. Since Acer only handed out the instructions and source of the modified linux kernel on its webpage, it hasn't yet met its obligations.
Since Android uses a different licence, you can refuse to hand out part of its code but you can gain popularity in the opensource community by doing so.
Yours sincerely
Denis Wentland
The request dates from 3th of July. How much time to give them and how to proceed in case they don't follow?
U-boot
While investigating usb-traffic, I encountered some CDC-ACM messages on the powered off, battery removed, usb-connected device . For 1 second the device opens its USB serial port and spams some READYREADYREADY messages . Then it closes it for some 8 seconds again.
On factory mode it asks for the input password on the /dev/ttyACM0 port.
I hope I can find out the password and enter U-Boot command prompt.
Since U-boot is under GPL Acer should hand out the source for me to find out the pasword.
hexdumping the boot loader firmware it has some uboot-messages:
000277f0 2d 20 0a 00 5b 25 73 5d 20 55 6e 70 6c 75 67 67 |- ..[%s] Unplugg|
00027800 65 64 20 43 68 61 72 67 65 72 2f 55 73 62 20 62 |ed Charger/Usb b|
00027810 65 74 77 65 65 6e 20 50 72 65 2d 6c 6f 61 64 65 |etween Pre-loade|
00027820 72 20 61 6e 64 20 55 62 6f 6f 74 20 69 6e 20 4b |r and Uboot in K|
00027830 65 72 6e 65 6c 20 43 68 61 72 67 69 6e 67 20 4d |ernel Charging M|
00027840 6f 64 65 2c 20 50 6f 77 65 72 20 4f 66 66 20 0a |ode, Power Off .|
but unfortunetaly not the Serial output messages
I have a french Acer Z3 Single SIM and as many on XDA i am a kind of flasholic.
I found a file .ZIP opened it and found boot.zip, system.img, recovery.zip that I I flashed from ADB\Fastbboot.
Was able to boot the phone but it’s from dual SIM update Thaï operator.
This one : Update_Acer_AV052_Z130_1.005.00_AAP_AISH https://www.dropbox.com/s/5s07i8g1hq3ekga/Z130SingleSIM_Tha%C3%AFSTOCK_ROM.zip
I don’t get any network signal from it. If it can help…maybe?
WARNING: if some of you decide to dowload this, please do not install it on your phone, because you will not be able to install another System.zip. Or unless you want an asian DUO SIM THAÏ Operator ok! :good:
wendenerp said:
While investigating usb-traffic, I encountered some CDC-ACM messages on the powered off, battery removed, usb-connected device . For 1 second the device opens its USB serial port and spams some READYREADYREADY messages . Then it closes it for some 8 seconds again.
On factory mode it asks for the input password on the /dev/ttyACM0 port.
I hope I can find out the password and enter U-Boot command prompt.
Since U-boot is under GPL Acer should hand out the source for me to find out the pasword.
hexdumping the boot loader firmware it has some uboot-messages:
000277f0 2d 20 0a 00 5b 25 73 5d 20 55 6e 70 6c 75 67 67 |- ..[%s] Unplugg|
00027800 65 64 20 43 68 61 72 67 65 72 2f 55 73 62 20 62 |ed Charger/Usb b|
00027810 65 74 77 65 65 6e 20 50 72 65 2d 6c 6f 61 64 65 |etween Pre-loade|
00027820 72 20 61 6e 64 20 55 62 6f 6f 74 20 69 6e 20 4b |r and Uboot in K|
00027830 65 72 6e 65 6c 20 43 68 61 72 67 69 6e 67 20 4d |ernel Charging M|
00027840 6f 64 65 2c 20 50 6f 77 65 72 20 4f 66 66 20 0a |ode, Power Off .|
but unfortunetaly not the Serial output messages
Click to expand...
Click to collapse
sory idk what it means. but does that mean we cant get it on our z3?
---------- Post added at 06:32 AM ---------- Previous post was at 06:30 AM ----------
hello guys. may i know what bloatware that can safely be remove from this phone? its full with useless app. wish i could uninstall all of it to make it more like stock android
Salut,
as-tu trouver une roms stock pour le z3 ?
Merci
Hi,
Anybody have an original stock ROM for z130 EMEA ?
Please help me. I have lost mine...
Thx...
Sent from my Nexus 5 using XDA Free mobile app
hi guys..
is there Polish language for this device..?
http://www.acer.com.sg/ac/en/SG/content/drivers/4889;-;Z130