Latest product reviews
ARCHOS 50 Diamond
ARCHOS GamePad2
ARCHOS
Smartphones
ARCHOS
TV Connect
ARCHOS 101 XS

A A A
Avatar

Please consider registering
Guest

Search

— Forum Scope —






— Match —





— Forum Options —





Minimum search word length is 3 characters - maximum search word length is 84 characters

Register Lost password?

ClockworkMod (CWM) Recovery easy install for RK3066 and RK3188 -- TWRP/CWM Flash-Tool and root for RK3288

 Please donate to support OMA and CrewRKTablets firmware work, thank you !

sp_Feed sp_TopicIcon
[ RK3288 ROM ] Insignia Flex Elite LP 5.0.2 custom root firmware (2015/08/08)
Avatar
graphdarnell
Active Member
Forum Posts: 41
Member Since:
2015/12/29
sp_UserOfflineSmall Offline

Thanks Received: 1
91
2016/08/15 - 20:45
sp_Permalink sp_Print

I can open the tab in a flash.  No problema.  Just tell me what to do.  I've enclosed a picture of the motherboard with the shield removed and components exposed.  If need be, I can send higher resolution images.  Thanks again for the help.[Image Can Not Be Found]FlexMB.jpgImage Enlarger

Avatar
Oma7144

Moderator

Firmware Guru
Forum Posts: 6315
Member Since:
2012/10/06
sp_UserOfflineSmall Offline

Thanks Received: 1374
92
2016/08/15 - 20:53
sp_Permalink sp_Print

You need to start the Mask-Rom modus by shorting pin 8/9 of the Foresee chip. In principle like here.

- Oma -

The following users say thank you to Oma7144 for this useful post:

graphdarnell
Avatar
graphdarnell
Active Member
Forum Posts: 41
Member Since:
2015/12/29
sp_UserOfflineSmall Offline

Thanks Received: 1
93
2016/08/16 - 03:07
sp_Permalink sp_Print

Setup as follows:  

1.  RKAndroidtool on (Found One Loader); Tab in Bootloader Mode.

2.  Batchtool with Admin. rights on (device square green).

3.  Short pins 8-9.

4.  Short pins 7-8 would restart the tab.

Same result as before:  commands from tools will neither format nor write to NAND

Foresee NAND question: 

I'm  not familiar with the NAND architecture.  Judging from experience, I assumed Green spot to be where the dimple or dot normally would be (see cut corner on PCB) and where pin 1 is located.  That's how I get to pins 8 & 9 (Red rectangle).  Having seen no result from said scheme, I then switched to Blue spot as pin 1 and counting to pins 8 & 9 (Yellow rectangle), still no dice.

I guess either (1) I got pin 1 location wrong; or (2) the pin assignment on this NAND is different.  I did try to locate a schematic of this NAND, all without success.  What do you think? NAND.jpgImage Enlarger

Avatar
graphdarnell
Active Member
Forum Posts: 41
Member Since:
2015/12/29
sp_UserOfflineSmall Offline

Thanks Received: 1
94
2016/08/16 - 10:13
sp_Permalink sp_Print

"Progress" Report:

I was able to enter MaskRom Mode at last.  However, even though I could erase flash, then flashed bootloader 2.19, I could go no further.  In both Win and Linux, I couldn't get it to LF,  though apparently it would read and write at some level.  The enclosed pictures tell the story.MaskRomA.jpgImage EnlargerMaskromB.jpgImage EnlargerMaskRomC.jpgImage EnlargerMaskRomD.jpgImage EnlargerMaskRomE.jpgImage EnlargerMaskRomF.jpgImage Enlarger


Avatar
graphdarnell
Active Member
Forum Posts: 41
Member Since:
2015/12/29
sp_UserOfflineSmall Offline

Thanks Received: 1
95
2016/08/16 - 10:17
sp_Permalink sp_Print

BTW, par curiosité, vous habitez dans quel quartier de Paris?

Avatar
Astralix
Germany

Firmware Guru
Forum Posts: 27
Member Since:
2012/12/28
sp_UserOfflineSmall Offline

Thanks Received: 7
96
2016/08/16 - 10:49
sp_Permalink sp_Print

Hey guys!

Apparently this FORESEE NCEFBS98-16G is not a dump raw NAND as it was in the old tablets. It is a full sized eMMC memory that complies JEDEC eMMC v4.51 specifications. I need to check some things before finding a solution but there are some details in your problem description that make me wonder...

The eMMC does do the complete wear-leveling internally. So an IDB in front and a hand full of reserved spare memory at the end are not needed with this kind of flash. But the flash tool writes an IDB (may be for compatibility reasons) but when it fails it looks like this error that we know from the raw NAND flash devices if your image is too large and reaches into the spare section reserved for wear-leveling by the rk_nand driver.

For the forced recovery: You cannot just short the pins from the NAND as this eMMC has a totally different structure. It does connect to different pins ind a different way. You can think of it as a very fast and 8-bit wide SD-Card. The eMMC does have a reset pin that you could pull low to get the mask-rom loader going, but I don't know if this pin is available at the NAND pins you can contact, or if there is a test-point on the PCB. I need to check the datasheet of the RK3288 for this.

CeeYa
Astralix

The following users say thank you to Astralix for this useful post:

admin
Avatar
Oma7144

Moderator

Firmware Guru
Forum Posts: 6315
Member Since:
2012/10/06
sp_UserOfflineSmall Offline

Thanks Received: 1374
97
2016/08/16 - 16:05
sp_Permalink sp_Print sp_EditHistory

Just discussing this within the team. RK-Tool wise the handling of the eMMC is not different to the handling of NAND.

What are the pins? Maybe you need do press the keys or plug the usb in at the same time.

Can you pls try to flash the latest loader in Mask-Rom first? http://crewrktablets.arctablet.com/?wpfb_dl=2945

Loading something into the tool see picture.

- Oma -

flash_kernel.pngImage Enlarger

The following users say thank you to Oma7144 for this useful post:

graphdarnell
Avatar
graphdarnell
Active Member
Forum Posts: 41
Member Since:
2015/12/29
sp_UserOfflineSmall Offline

Thanks Received: 1
98
2016/08/16 - 20:41
sp_Permalink sp_Print sp_EditHistory

The MaskRom Mode is obtained by shorting pins 8 & 9 (red rectangle in picture above) with power off and plugging the USB cable into the PC simultaneously.  The new loader (2.30.10) flashes ok.  However, as soon as that's done, the tab reverts to Loader Mode and the inability to flash anything else persists as before.  Thus, no change or progress.

Trying to DI the parameters right after "loader ok" gives "test device innormal, exit download page!"  

Avatar
Astralix
Germany

Firmware Guru
Forum Posts: 27
Member Since:
2012/12/28
sp_UserOfflineSmall Offline

Thanks Received: 7
99
2016/08/17 - 08:24
sp_Permalink sp_Print

graphdarnell,
could you please provide me the log file from the Android Tools program directory. There is a log file generated with every flash process you try. This log file is more informative as the small window on the right hand side.
I need that log to request the correct information from RK for you.

The following users say thank you to Astralix for this useful post:

graphdarnell
Avatar
graphdarnell
Active Member
Forum Posts: 41
Member Since:
2015/12/29
sp_UserOfflineSmall Offline

Thanks Received: 1
100
2016/08/17 - 08:50
sp_Permalink sp_Print

With pleasure.  The one "test device fail" remains a constant across several platforms.

01:09:52 Upgrade Tool ver 1.21
01:10:02 Upgrade Tool ver 1.21
01:10:06 Upgrade Tool ver 1.21
01:11:41 Upgrade Tool ver 1.21
01:32:26 Upgrade Tool ver 1.21
01:47:29 Upgrade Tool ver 1.21
02:15:19 Upgrade Tool ver 1.21
23:12:14 Upgrade Tool ver 1.21
23:15:46 Upgrade Tool ver 1.21
23:26:00 Error:RKU_Write failed,err=-4
23:26:00 Error:LowerFormatDevice-->RKU_TestDeviceReady failed,subCode(0x0),RetCode(-3)
23:26:01 Error:RKU_Write failed,err=-4
23:26:01 Error:LowerFormatDevice-->RKU_TestDeviceReady failed,subCode(0x0),RetCode(-3)
23:26:02 Error:RKU_Write failed,err=-4
23:26:02 Error:LowerFormatDevice-->RKU_TestDeviceReady failed,subCode(0x0),RetCode(-3)
23:27:11 Upgrade Tool ver 1.21
23:29:00 Upgrade Tool ver 1.21
23:29:00 Test Device Start
23:29:00 <LAYER 1-5> ERROR:TestDevice-->RKU_TestDeviceReady failed,Total is zero
23:29:00 Test Device Fail
23:31:23 Upgrade Tool ver 1.21
23:31:23 ERROR:download_parameter-->RKU_TestDeviceReady failed,Total is zero
23:32:09 Upgrade Tool ver 1.21
23:32:09 get_parameter_loader-->RKU_TestDeviceReady failed,Total is zero
23:33:07 Upgrade Tool ver 1.21
23:33:07 get_parameter_loader-->RKU_TestDeviceReady failed,Total is zeroUpgradeToolLog.jpgImage Enlarger

Avatar
graphdarnell
Active Member
Forum Posts: 41
Member Since:
2015/12/29
sp_UserOfflineSmall Offline

Thanks Received: 1
101
2016/08/17 - 08:59
sp_Permalink sp_Print

Also see post # 89

Avatar
Astralix
Germany

Firmware Guru
Forum Posts: 27
Member Since:
2012/12/28
sp_UserOfflineSmall Offline

Thanks Received: 7
102
2016/08/17 - 09:22
sp_Permalink sp_Print

Thank you!

I my memories these tools where much more talkative than that. However, forwarded. Let's see if I get a reply.

The following users say thank you to Astralix for this useful post:

graphdarnell
Avatar
graphdarnell
Active Member
Forum Posts: 41
Member Since:
2015/12/29
sp_UserOfflineSmall Offline

Thanks Received: 1
103
2016/08/17 - 09:50
sp_Permalink sp_Print

I'm sorry, that was just from the Upgrade Tool in Linux.  Below are logs from the AndroidTool and BatchTool.  

Avatar
graphdarnell
Active Member
Forum Posts: 41
Member Since:
2015/12/29
sp_UserOfflineSmall Offline

Thanks Received: 1
104
2016/08/17 - 09:57
sp_Permalink sp_Print sp_EditHistory

And this is from the latest upgrade to Loader 1.30.10 with UpgradeTool:

10:28:47 Upgrade Tool ver 1.21
10:30:54 Upgrade Tool ver 1.21
10:34:20 Upgrade Tool ver 1.21
10:34:32 Upgrade Tool ver 1.21
10:34:32 Download Boot Start
10:34:34 Download Boot Success
10:34:34 Wait For Maskrom Start
10:34:34 Wait For Maskrom Success
10:34:34 Test Device Start
10:34:34 Test Device Success
10:34:34 Check Chip Start
10:34:34 Check Chip Success
10:34:34 Get FlashInfo Start
10:34:34 INFO:FlashInfo: 0 80 CE 1 0 4 4 0 28 0 1
10:34:34 Get FlashInfo Success
10:34:34 Prepare IDB Start
10:34:34 INFO:CS(1) (14800MB) (SAMSUNG)
10:34:34 Prepare IDB Success
10:34:34 Download IDB Start
10:34:36 Download IDB Success
10:34:36 Reset Device Start
10:34:38 Reset Device Success
10:37:39 Upgrade Tool ver 1.21
10:37:39 ERROR:download_parameter-->RKU_TestDeviceReady failed,Total is zero
10:37:45 Upgrade Tool ver 1.21
10:37:45 ERROR:download_parameter-->RKU_TestDeviceReady failed,Total is zero
10:38:02 Upgrade Tool ver 1.21
10:38:02 ERROR:download_parameter-->RKU_TestDeviceReady failed,Total is zero
10:38:19 Upgrade Tool ver 1.21
10:38:19 ERROR:download_parameter-->RKU_TestDeviceReady failed,Total is zero

 

BTW, you're not friends with Oblalix, are you?

Avatar
buzzly
Member
Forum Posts: 14
Member Since:
2016/08/16
sp_UserOfflineSmall Offline

Thanks Received: 1
105
2016/08/17 - 16:43
sp_Permalink sp_Print

Could all these connection trouble caused by not using the original OTG-USB cable?  Just guessing.

The following users say thank you to buzzly for this useful post:

mussonero1
Forum Timezone: Europe/Paris

Most Users Ever Online: 749

Currently Online: fritske
138 Guest(s)

Currently Browsing this Page:
1 Guest(s)


Devices in use: Desktop (121), Phone (18)

Top Posters:

finless: 604

DarthJabba: 551

maikal: 394

mussonero1: 350

alex: 252

damo: 243

DanielVd: 237

Mark06: 222

Newest Members:

Altaaj

Robbiehaierpaduser

polyflex

muzammilarif

fritske

luiz.melges

Forum Stats:

Groups: 10

Forums: 185

Topics: 6030

Posts: 60484

 

Member Stats:

Guest Posters: 43

Members: 261453

Moderators: 5

Admins: 1

Administrators: admin

Moderators: globula_neagra, exelletor, JochenKauz, Oma7144, cracktech


CrewRKTablets moderators: JochenKauz and Astralix