Related
Hi guys, think i've bricked up my x10
after SEUS update the phone wont boot.. it vibrates on power but then stays black.
tried to reflash using the SEUS..
SEUS "recognizes" the phone (says "firmware already installed blabla.. reflash?) but at the flash progress it hangs at the beginning and finally aborts with an error message.
any ideas?
This might work.
tried the flashtool too.. no success
log:
28/041/2011 21:41:26 - ERROR - Please plug you device in flash mode
28/041/2011 21:41:27 - INFO - Searching Xperia....
28/041/2011 21:41:27 - INFO - Found at USB\VID_0FCE&PID_ADDE\5&284A1E07&0&5
28/041/2011 21:41:27 - INFO - Start Flashing
28/041/2011 21:41:27 - INFO - VER="R8A013";DATE="20100119";TIME="17:24:00";
28/041/2011 21:41:27 - INFO - Flashing loader
28/042/2011 21:42:33 - INFO -
28/046/2011 21:46:55 - INFO - Flashing kernel.sin
28/048/2011 21:48:10 - ERROR - Error flashing. Aborted
28/048/2011 21:48:10 - INFO - Now unplug the device and power it on
28/048/2011 21:48:10 - INFO - Then go to application settings
28/048/2011 21:48:10 - INFO - turn on Unknown Sources and Debugging
just tried the omnious for se v0.20 flasher.. same result
log:
Action journal
22:30:16 Flash
22:30:16 Allows to change languages supported by the phone and upgrade its firmware.
22:30:16 Operating system: Microsoft Windows XP Professional Service Pack 2 (build 2600)
22:30:16 Application version: 0.20.3728 (beta)
22:30:16 . The action name is 'Flash'
22:30:16 Selected phone type: Xperia™ X10
22:30:16 i Instructions
22:30:16 i 1. Make sure the phone battery is charged to at least 50%.
22:30:16 i 2. Switch off the phone!
22:30:16 i 3. Remove the phone battery and wait at least 5 seconds before reinserting it!
22:30:16 i 4. Press and hold the return back button, then connect the cable to the phone!
22:30:16 . The action started waiting for the user
22:30:31 . The action finished waiting for the user
22:30:31 Connecting via SEMC USB Flash Device (USB1)...
22:30:31 Device driver version: 2.2.0.5
22:30:31 Detected chipset: QSD8250
22:30:31 Boot mode: EROM
22:30:31 IMEI: 35941903911402
22:30:31 Sending loader...
22:40:18 e Failed!
22:40:18 . The action entered shutdown phase
22:40:18 . The action reported failure
Error code
# FEF0FA7628628BE2
Error details
---
6E 4B 0E AC 0D 8F E5 78 57 5C C8 E9 35 0A CD 05
FF EE E1 9C 03 D2 1B 5F 59 BE 49 60 E2 A1 63 F7
B1 6A E1 B5 BD 4E 7B 96 F7 C6 E7 54 95 F8 E5 8B
31 07 7F 7C 6D 28 21 90 98 0F 47 6D BB A6 C3 3A
F1 30 F6 46 4D 8F DB 48 69 F8 0D 96 71 9E A3 21
C1 3A DF AE 9B 52 4C 2D 49 63 89 AC 5B CC 90 25
D5 23 5F E0 83 72 C5 26 C9 EE 59 B8 63 FD C0 73
---
Flash stock 1.6 rom with flash tools and all will be good
Sent from my HD2 using XDA App
another problem occurs.. its seems, that the battery wont be charged anymore.
i wanted to try the 1.6 stock but i cant "boot" up in the flashmode.
i press the "back"-button then plugin the usbchord but no green led..insted the red led blinks up every ~2sec for a short period.
blmn1337 said:
another problem occurs.. its seems, that the battery wont be charged anymore.
i wanted to try the 1.6 stock but i cant "boot" up in the flashmode.
i press the "back"-button then plugin the usbchord but no green led..insted the red led blinks up every ~2sec for a short period.
Click to expand...
Click to collapse
Red LED means that battery is drained, should wait and charge battery without booting and you should be fine. If it still doesn't charge then buy a new battery.
it's working again
i think it was a battery charging problem.
plugged in for charging in the morning and when i got home, the system was booted up and the battery fully charged.
now everything is normal again.
thx for support, mates
i found out, that the battery is charged normally.
the problem happened again.
when holding power on it vibrates and nothing else.. black screen, no bootup logo, no background-light
halp pls
Did you sort this I had the same problem
sent with a geordie kiss using wb 2.3.3
1.download the global 2.1 stock flashable file
2.put it inside your firmware folder in flash tool folder
3.dont connect ur phone
4.hit flash and select the global firmware and wait till the flash tool ask u to connect ur phone
5.now remove ur phone battery
6.connect usb cable into ur phone with the battery is removed and now press and hold the back button on ur phone and insert the battery
I had the same problem and I fixed it using the above procedure.
All the best buddy...
runaway_bunny said:
1.download the global 2.1 stock flashable file
2.put it inside your firmware folder in flash tool folder
3.dont connect ur phone
4.hit flash and select the global firmware and wait till the flash tool ask u to connect ur phone
5.now remove ur phone battery
6.connect usb cable into ur phone with the battery is removed and now press and hold the back button on ur phone and insert the battery
I had the same problem and I fixed it using the above procedure.
All the best buddy...
Click to expand...
Click to collapse
i've tried but doesn't work for me.. not able to flash anything
still have the problem
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 i just tryed to unlock my Airtel E5573Cs-609 using Balong tool but i got error 0000: ED 05 FA 53 C0 *í.úSÀ please help me how can i unlock?
Ashwinkol said:
Hello i just tryed to unlock my Airtel E5573Cs-609 using Balong tool but i got error 0000: ED 05 FA 53 C0 *í.úSÀ please help me how can i unlock?
Click to expand...
Click to collapse
contact balwinder 27 his whastapp +919646599249
he can unlock your modem
Code:
To XDA moderators : There's no sub-forum for these 4 models.
Nokia C2 Tava, Tennen and 2 V Tella are basically same device. Please move this topic when available, thanks.
Hi all,
Recently I got Nokia C2 Tennen and C5 Endi bootloader unlocked again.
If you guess I achieved that by utilizing prototype firmware, then you're right.
However I don't have other retail device to test, anybody would like to give it a try?
I would be definitely interested to try it out. I have a c5 needing bootloader unlock
Legendanubis said:
I would be definitely interested to try it out. I have a c5 needing bootloader unlock
Click to expand...
Click to collapse
Alright.
May I know if you're familiar with operating SP flash tool?
i wouldl love to try it. I have got a locked c2 tava that i am unable to factory reset. A friend brought the phone to me to FRP bypass (bought it cheap from someone that said it just needed to be charged, gave a false pin and here we are) That was a month ago. Im very new to all of this and while ive been studying bootloaders and root i havnt actually had the pleasure. Any advice is welcome on this TA-1218. I cannot find ANYTHING on the EXACT model. All help is appreciated. Thanks
jh
hikari_calyx said:
Alright.
May I know if you're familiar with operating SP flash tool?
Click to expand...
Click to collapse
I am not familiar with it, I currently use bugjaeger to flash my phone's. But would love to get this c5's bootloader unlocked so if I can't use my program to flash I would definitely learn the sp flash tool
Bootloader unlock done with Hydra Tools. Also put a work root and magisk root on as well.
Hydra MediaTeK Tool Ver 1.0.3 Build 77
Windows 10 (Version 10.0, Build 19042, 64-bit Edition)
Intel(R)Core(TM) i5-2410M CPU @ 2.30GHz
Intel(R) HD Graphics 3000
Ram Installed : 4 GB
Windows Access Right : Admin
Software Run As Admnistrator
******* Dongle Info *******
Version : Hydra Tool v 1.20
Serial : [removed]
Initialize : OKAY
Status : Activated
Life : [removed]
=====================================
Searching for MTK Device... Found
Port Identification : Flashmode BROM
FriendlyName : MediaTek USB Port_V1633 (COM10)
Device : 6&13d9c38d&0&3
SymbolicName :\\??\\USB#VID_0E8D&PID_0003#6&13d9c38d&0&3#\[removed]
Driver Ver : 01/22/2015,3.0.1504.0
Opened handle..
Handshaking... Ok
Identifying Hardware ID.....
Reading Device hardware info..
hw code : 0717 MT6761 [6761]
hw subcode : 8A00
hw version : CA01
sw version : 0200
Target config : E3
SBC : 01 (True)
SLA : 02 (True)
DAA : 00 (False)
SWJTAG : 02 (True)
EPP : 00 (False)
CERT : 00 (False)
MEMREAD : 20 (True)
MEMWRITE : 40 (True)
CMD_C8 : 80 (True)
Exploiting Device...
Exploit Sent..
Successfully Exploited...
Handshaking... Ok
\\HydraTool_FullPackage_08-01-2021\backup\\Preloader_dump\\prel.tmp
Handshaking...
Identifying Hardware ID.....
Reading Device hardware info..
hw code : 0717 MT6761 [6761]
hw subcode : 8A00
hw version : CA01
sw version : 0200
Target config : 00
SBC : 00 (False)
SLA : 00 (False)
DAA : 00 (False)
SWJTAG : 00 (False)
EPP : 00 (False)
CERT : 00 (False)
MEMREAD : 00 (False)
MEMWRITE : 00 (False)
CMD_C8 : 00 (False)
MEID : [removed]
Stage 1.. [Size:232216]
Sending : Please wait.. Accepted
Identifying Protocol...
Protocol : New
Synchronization... [ERROR]- NOT SYNC
=============================================
Reasons why it fails due to the following"
1. Harware problem/issues
2. If you did Testpoint Kindly check the parts you Touch/TP
3. Powershortage, try to connect Battery
4. Check or replace usb cable and plug directly to your pc usb port.
=============================================
SYNC
Preloader Initialization...
Parsing prel.tmp
Init : Accepted
Executing : SYNC
Reading Device UniqueID, RAM and Flash Chip Info...
UNIQUE ID : [removed]
ERAM Size : 0x0000000000039000 -228 KB
IRAM Size : 0x0000000080000000 -2 GB
eMMC BOOT1 : 0x0000000000400000 -4 MB
eMMC BOOT2 : 0x0000000000400000 -4 MB
eMMC RPMB : 0x0000000001000000 -16 MB
eMMC USER : 0x0000000747C00000 -29.121 GB
eMMC CID : [removed] - QD63MB
Executing : ACCEPTED...
Reading GPT0 -EMMC [0x00008000] 0 130 Items
0
Autobackup Partitions
-preloader [0x00000000] 512 KB -> preloader.bin...1 Ok0
-> Renaming Preloader.... preloader_armstrong.bin0
Creating Scatter file... \\HydraTool_FullPackage_08-01-2021\\\backup\\Auto\\0717__111921012459\\MT6761_Android_scatter.txt
-pgpt [0x00000000] 8 MB -> pgpt.bin...1 Ok
-frp [0x02D80000] 1024 KB -> frp.bin...1 Ok
-nvdata [0x04E80000] 64 MB -> nvdata.bin...1 Ok
-protect1 [0x0C51A000] 8 MB -> protect1.bin...1 Ok
-protect2 [0x0CD1A000] 10.898 MB -> protect2.bin...1 Ok
-persist [0x0E000000] 48 MB -> persist.bin...1 Ok
-nvram [0x1A900000] 64 MB -> nvram.bin...1 Ok
Done!!!0
\\HydraTool_FullPackage_08-01-2021\\\backup\\Auto\\0717__111921012459
MTK Phone Loader is NOW RUNNING.
Reading Device UniqueID, RAM and Flash Chip Info...
UNIQUE ID : 2 [removed]
ERAM Size : 2 0x0000000000039000 -228 KB
IRAM Size : 2 0x0000000080000000 -2 GB
eMMC BOOT1 : 0x0000000000400000 -4 MB
eMMC BOOT2 : 0x0000000000400000 -4 MB
eMMC RPMB : 0x0000000001000000 -16 MB
eMMC USER : 0x0000000747C00000 -29.121 GB
eMMC CID : [removed] - QD63MB
Reading GPT0 -EMMC [0x00008000] 0 130 Items
-------------------------------------
Operation : Unlock Bootloader
Processing...
-------------------------------
Bootloader Status...
Bootloader : Locked
-------------------------------
Verifying status after operation...
-------------------------------
Bootloader Status...
Bootloader : Unlocked
-------------------------------
Action Result : 0 Ok
Elapsed Time : 00:01:04
(its been a while. i know)
i successfully got my c2 tennen (ta-1218) bootloader unlocked and rooted.
im still running on stock tho.
plus no custom recoveries yet.
Quartzbreaker said:
i wouldl love to try it. I have got a locked c2 tava that i am unable to factory reset. A friend brought the phone to me to FRP bypass (bought it cheap from someone that said it just needed to be charged, gave a false pin and here we are) That was a month ago. Im very new to all of this and while ive been studying bootloaders and root i havnt actually had the pleasure. Any advice is welcome on this TA-1218. I cannot find ANYTHING on the EXACT model. All help is appreciated. Thanks
Click to expand...
Click to collapse
Have you ever found a solution to your problem? Im having same issue and cant seem to find a fix for it.
This may mot be the correct thread and if so please accept my apology but I'm trying to unlock the bootloader for a Moto g pure and neither Motorola or at&t will give the bootloader codes. I saw reference here to sp flash tool and wondered if someone could help me utilizing that. I do not have a desktop or laptop and all I have to work with is mobile. Mtkclient won't run because I can't get PySides6 dependencies to install in Termux. I was able to install NetHunter , the one for no rooted devices, but so far I can't find a way to force flash
hikari_calyx said:
Code:
To XDA moderators : There's no sub-forum for these 4 models.
Nokia C2 Tava, Tennen and 2 V Tella are basically same device. Please move this topic when available, thanks.
Hi all,
Recently I got Nokia C2 Tennen and C5 Endi bootloader unlocked again.
If you guess I achieved that by utilizing prototype firmware, then you're right.
However I don't have other retail device to test, anybody would like to give it a try?
Click to expand...
Click to collapse
SUCCESS! [BOOTLOADER UNLOCK] Nokia C2 Tava TA-1218.
[BOOTLOADER UNLOCK] Nokia C2 Tava TA-1218. I was actually approached by a person from XDA named @Soadeathdealer who gave me remote access to unlock his phone's bootloader. This phone bootloader was successfully unlocked using Unlock Tool which...
forum.xda-developers.com
cagedbadger said:
This may mot be the correct thread and if so please accept my apology but I'm trying to unlock the bootloader for a Moto g pure and neither Motorola or at&t will give the bootloader codes. I saw reference here to sp flash tool and wondered if someone could help me utilizing that. I do not have a desktop or laptop and all I have to work with is mobile. Mtkclient won't run because I can't get PySides6 dependencies to install in Termux. I was able to install NetHunter , the one for no rooted devices, but so far I can't find a way to force flash
Click to expand...
Click to collapse
I don't think the moto g pure has been unlocked yet. At least boost variant.