]]>Mon, 23 Jan 2017 09:36:12 +0100ghanashyaml2 on [ RK3288 ROM ] Insignia Flex Elite LP 5.0.2 custom root firmware (2015/08/08)http://www.arctablet.com/blog/forum/rk3288-entwicklung-und-customroms-development-and-croms/rk3288-rom-insignia-flex-elite-lp-5-0-2-custom-root-firmware-20150808/page-11/#p59629
RK3288 Entwicklung und CustomRoms (Development and cRoms)http://www.arctablet.com/blog/forum/rk3288-entwicklung-und-customroms-development-and-croms/rk3288-rom-insignia-flex-elite-lp-5-0-2-custom-root-firmware-20150808/page-11/#p59629Hi guys, I stumbled upon this thread while searching for info on unblocking my Tronsmart R68. My tv box is bricked and also has Foresee eMMC which is discussed in this thread. I am however, for the life of me, unable to get this into loader or mask rom mode no matter what I try. Even shorting pins 8-9 while starting the power isn't getting it into mask rom mode.

I have been scouring the net looking for a solution to my non-working tablet. I've heard about Oma and seen plently of links to his files, but not till now have I stumbled across an active forum. 🙂 Jackpot!

I have an Insignia Tablet Model NS-P10A6100. I had installed KingRoot and sometime later, it started acting wierd (not sure if it was related to KR) so I rebooted it. The Insignia logo just pulses there.

I can get into Recovery Mode. In "Load from ADB", the device shows up and I can see it with "ADB devices". RKFactoryTool I don't see it at all, though. When I try to sideload anything, it fails when the tablet opens it up. I do have acess to the SDCard, but not sure what I should try to send through that.

I've read through this whole thread, and am wondering if these methods would work on my tablet.

I'm running on Windows 10. However, I have a second PC I can run Linux on if need to (will have to install it first).

Thanks for the help.

Kori

]]>Tue, 20 Sep 2016 04:15:41 +0200mjsharon on [ RK3288 ROM ] Insignia Flex Elite LP 5.0.2 custom root firmware (2015/08/08)http://www.arctablet.com/blog/forum/rk3288-entwicklung-und-customroms-development-and-croms/rk3288-rom-insignia-flex-elite-lp-5-0-2-custom-root-firmware-20150808/page-11/#p58934
RK3288 Entwicklung und CustomRoms (Development and cRoms)http://www.arctablet.com/blog/forum/rk3288-entwicklung-und-customroms-development-and-croms/rk3288-rom-insignia-flex-elite-lp-5-0-2-custom-root-firmware-20150808/page-11/#p58934Successfully installed CWM 1.1 img using terminal emulator on tab. Think I'll stick with this version. Many thanks.
]]>Tue, 06 Sep 2016 21:30:14 +0200graphdarnell on [ RK3288 ROM ] Insignia Flex Elite LP 5.0.2 custom root firmware (2015/08/08)http://www.arctablet.com/blog/forum/rk3288-entwicklung-und-customroms-development-and-croms/rk3288-rom-insignia-flex-elite-lp-5-0-2-custom-root-firmware-20150808/page-11/#p58930
RK3288 Entwicklung und CustomRoms (Development and cRoms)http://www.arctablet.com/blog/forum/rk3288-entwicklung-und-customroms-development-and-croms/rk3288-rom-insignia-flex-elite-lp-5-0-2-custom-root-firmware-20150808/page-11/#p58930Talked to an acquaintance today who tried to install CWM on his. Reported that he couldn't use the CWM3.0.img, although the 1.1.img flashed ok. Thereafter, he said it backuped without problems. Given they are both 6.0.5.1 version, I don't see why one should be preferred to the other, so long as they work. I just make a note here for those who might run into the same problem.

Edit: I toyed around with the recovery and made myself a flashable zip for CWM 3.0. Once again, I guinea-pigged myself and flashed it with the installed CWM 1.1. Seems to work fine in case someone wants to "upgrade" from CWM 1.1.img to CWM 3.0.img, though I'd be damned if I can tell the difference between the two. In any case, here's the link:

Oma7144 said
The stock recovery running first will format all user partitons. In TWRP or CWM one will get the same doing a factory reset.

So, to recap:

- we can now flash the rooted system.img and CWM.img through adb (with dd comand)
- in case of a bricked tab it is necessary to flash the repacked build in MaskRom mode

Do I miss something?

- Oma -

Correct, with one small different detail. A factory reset will not clear a (data) partition of residual data (recognized but unseen and unreadable by Explorer) from a failed update. For that, a total format of internal storage is necessary.

Edit: Can't dash the question I asked above about formatting the internal storage. I was able to do it with CWM and reclaim the "lost" storage. Also I did restore the tab with CWM backup, and it worked quite well. At least if you install CWM through ADB shell, we don't have to worry about OTAs bricking the tab like it happened to a few of us before. Big step forward, I'd say.

It does contain the mini-loader, the stock parameter file (for max partition sizes) and a CWM.

I guess it is possible to flash this firmware in Loader-Mode now.

Can somebody try to flash the CWM, pls (see attached picture)? It is a limited risk. If the loader will not work it won't flash anything.

- Oma -

I'll try to flash CWM in Loader Mode tonight and report back. One thing I forgot to mention is that if you flash Oma's Rom using the stock (lollipop) parameters, you'll get stuck at the Insignia Logo page. You need Oma's parameters instead.

BTW, Oma, how do I format the data partition thoroughly as with TWRP? CWM does it in a flash, and I don't think that's thorough because I still miss about 4GB of space afterwards. I ran eMMC Brickbug Check and memory block check and they both came back positive. Or if you point me to a site that shows how to do that with ADB, I'd appreciate it. I've been looking online, but no one provides complete analysis and instructions. Thanks.

Flashed CMW through ADB shell without incident. Tested with full NAND backup successfully. However, I'm a bit concerned about testing restore since I don't know if it works reasonably well. Any precautions I should take?

On the side, I see no difference between package 2.2 and 3.0 insofar as the CWM.img, apart from the volume buttons' function. I got 6.0.5.1 both times, I believe.

Lastly, you mentioned in post #69 about the possibility of using another kernel and system.img. I assume the stock kernel can't be modified to activate touch for TWRP. Any chance that the other kernel might do it? Hopefully my tinkering would be of help to others.

I know you're way too busy so I'll wait until whenever. I do appreciate your guidance very much. Thanks again.

mjsharon said
Hi - trying to install the rom. Everything is fine until I get to step 13 - installing system.img. Won't install and says "Operation not permitted". All help appreciated.

Thanks.

If I were you, I'd make sure of the following:

1. The system.img is not corrupted in any way. This could happen during download, extraction, and copying;

2. Recheck for syntax errors;

3. Use the PC to issue commands instead of Terminal Emulator. The touch sensitivity on this model is not the best I've seen.

Good luck.

BTW, has anyone experienced this tab not connecting to Linux as an MTP Device? There's obviously communication in Linux since I can issue ADB commands, just not as a media device. Mine shows up fine in Win 7, but not otherwise. Wonder why.

graphdarnell said
Finally some great news. I flashed successfully! It's working fine now. I will recount the process in details later in case people need to replicate it to resuscitate their stuck tablet. Again many thanks to Oma the Man. You beat it!

Fine. I can repack the build later. Pls try the TWRP first. Rename it to recovery and flash it, just ticking parameter, misc and recovery.

- Oma -

Tried flashing. Came out ok as you can see in the picture, except touch functionality is not there. No touch, period. OTG mouse likewise does not work because the 5V supply is unavailable. A CWM alternative might, if one exists, but what do I know? Tempted to try THIS, but maybe should wait for your advice thereon.

Question on the side: We had to resort to MaskRom Mode where there's no ADB because no OS. However, if ADB in developer's options is available, can we not flash the recovery through ADB shell, the way you and bobb did it with all images?

1. Peel the silver tape off the surface of the board. Be careful where it sticks to the lcd amber ribbon underneath as you might tear it with too much force. Go slowly;

2. Pry off the metal shield covering the CPU with a pointed flat blade at the tiny clips around the perimeter. Be careful not to insert the blade too deeply as some components are tiny and can be easily damaged;

3. With the components exposed, locate the FORESEE chip; locate pins 8-9 and mark them (see Post # 93 – red rectangle). I had to count the pins under a magnifier because they're so close together;

4. Copy all files in the rockdev/image folder + the “oma_parameter_lp.txt” in the zip package in post # 1 to the same folder in the package in post # 129. Launch RKTool of the # 129 package. In the GUI, select all the correct files. Uncheck all but the loader (first column);

5. Ain't no other damn way to flash the loader with this thing. With power off, connect the data micro USB cable to the tab; short and hold 8-9 with a tiny flat screwdriver tip, then connect the USB cable to the PC. Done correctly, the GUI should switch from “No DEVICE Found” to “Found One MASKROM Device” at the bottom. If not, repeat this step again. Before repeating, make sure the tab is completely off again (I had to do it several times at each attempt to get it right so don't expect it to work at first try).

6. Flash the loader. If successful, the GUI will show “Found One LOADER”;

7. Lower Format the tab;

8. Uncheck loader; re-check all other items; flash them all.

It takes quite a few minutes (in my case) to finish. Once the download is complete, the tab will reboot on its own. First boot might take some minutes so be patient. When it gets to the “Oma” animation, you know you're good to go. Have fun.

Illustration: Motherboard with metal shield removed.

Yellow: mesh tape patch. There are 2: one covering the metal shield that needs to be peeled off first.

Blue: this is where the lcd ribbon connects. Be careful in separating the covering tape from the ribbon.

Red: clips holding the metal shield (I did not highlight them all, but you get the idea).

graphdarnell said
Finally some great news. I flashed successfully! It's working fine now. I will recount the process in details later in case people need to replicate it to resuscitate their stuck tablet. Again many thanks to Oma the Man. You beat it!

Fine. I can repack the build later. Pls try the TWRP first. Rename it to recovery and flash it, just ticking parameter, misc and recovery.

Finally some great news. I flashed successfully! It's working fine now. I will recount the process in details later in case people need to replicate it to resuscitate their stuck tablet. Again many thanks to Oma the Man. You beat it!

Fine. I can repack the build later. Pls try the TWRP first. Rename it to recovery and flash it, just ticking parameter, misc and recovery.

Oma7144 said
Yes. Flash the loader in MaskRom first. LowerFormat and then Run.

- Oma -

Finally some great news. I flashed successfully! It's working fine now. I will recount the process in details later in case people need to replicate it to resuscitate their stuck tablet. Again many thanks to Oma the Man. You beat it!

Edit: Better yet, I'll wait to see if there's any interest from anyone first. The only thing I forgot to test was to flash the TWRP custom recovery, though I have the feeling it wouldn't have gone well since as soon as the RK Tool finished flashing the system.img, the tab automatically rebooted. Also the Tool Oma provided didn't have a slot for recovery. A custom recovery would've been a great help.

Oma7144 said
Yes. Flash the loader in MaskRom first. LowerFormat and then Run.

- Oma -

Finally some great news. I flashed successfully! It's working fine now. I will recount the process in details later in case people need to replicate it to resuscitate their stuck tablet. Again many thanks to Oma the Man. You beat it!

Edit: Better yet, I'll wait to see if there's any interest from anyone first. The only thing I forgot to test was to flash the TWRP custom recovery, though I have the feeling it wouldn't have gone well since as soon as the RK Tool finished flashing the system.img, the tab automatically rebooted. Also the Tool Oma provided didn't have a slot for recovery. A custom recovery would've been a great help.

Copy over the firmware files in folder rockdev/Image and flash incl. LowerFormat.

- Oma -

Oma:

Are you asking me to do this or someone else? If it's me, should I flash the uboot file in MaskRom mode first before doing the others? Failing this, is there anyway to restore a backup of stock rom on mine? If possible, can I ask Buzzly to make a backup of your stock rom without any personal info and upload it somewhere? Thanks a lot guys.

]]>Sun, 28 Aug 2016 10:23:54 +0200graphdarnell on [ RK3288 ROM ] Insignia Flex Elite LP 5.0.2 custom root firmware (2015/08/08)http://www.arctablet.com/blog/forum/rk3288-entwicklung-und-customroms-development-and-croms/rk3288-rom-insignia-flex-elite-lp-5-0-2-custom-root-firmware-20150808/page-9/#p58763
RK3288 Entwicklung und CustomRoms (Development and cRoms)http://www.arctablet.com/blog/forum/rk3288-entwicklung-und-customroms-development-and-croms/rk3288-rom-insignia-flex-elite-lp-5-0-2-custom-root-firmware-20150808/page-9/#p58763I know..I know... The devs have grown tired of my silly questions, but I ran across THIS link where I found a tool called "create-sdcard" that supposedly would create a nand out of an external sd card and boot the tablet from there instead of the internal storage. The author specifically mentioned this method would help where the tablet would not boot from the internal storage.

So I executed the tool using Oma's update-img and all kind of went well up to the point where it began to unpack the image and failed: "unpacking of Android image unsuccessful...exiting" Has anybody tried this? If not, does anyone have an idea why the update.img cannot be unpacked?

I have this tab that's lying around doing nothing so I might as well try to destroy it and learn something in the process. Thanks in advance for any input.

Take the circuit board off the old battery and solder it onto the new battery (remove circuit board from new battery also and solder short wires onto it, to be then soldered onto old circuit board).

Thanks. Brought two of them.

Then I found a maybe better fit one at Aliexpress/eBay : 3.7v 6000mah 38110114 lithium polymer battery. Basically the size is 3.8 x 110 x 114 mm. Oh well. I have 3 tab all together. May be I will try this one after I perform successful surgery on the first two.

Astralix said
I checked your photo, even it is not very big... I cannot see any obvious test-points. But there are several cables and stickers on it where I can't see through. On one tablet I had, all the test-pins where on the bottom side, on several others these two pins, together with a ground pin where routed to an exposed position...

I don't see RX or TX anywhere on this board. The back side has a mylar insulation, and there's no visible testpoints. I would think those would be exposed as there's no point having them hidden.

But the issue is not so much whether the RKAndroidTool would work as there's anything that works at all. So my question to either Oma or Astralix is this: bobb's method obviously works. I'd done it myself before the catastrophe befell my previous tab. Only, it requires ADB. Another member (psiufoxx) reported that her tab was stuck at the pulsating logo (exactly like mine), and s/he only had access to stock recovery (See posts # 71 & 74).

Nevertheless, s/he was able to flash most anything (I assumed from this recovery) per bobb's instructions except the system.img. The only ADB I could see on stock recovery is Sideload. I tried to sideload Oma's update.img but the machine reported no signature, so no go. However, if this functions as ADB, then is it possible to flash with all the files on the external sd card, and issuing ADB commands from PC per bobb's instructions?

Would someone show me which 6000mah battery purchased from Aliexpress would fit this tab? A link would be very helpful. TIA.

]]>Wed, 24 Aug 2016 14:56:12 +0200Astralix on [ RK3288 ROM ] Insignia Flex Elite LP 5.0.2 custom root firmware (2015/08/08)http://www.arctablet.com/blog/forum/rk3288-entwicklung-und-customroms-development-and-croms/rk3288-rom-insignia-flex-elite-lp-5-0-2-custom-root-firmware-20150808/page-8/#p58714
RK3288 Entwicklung und CustomRoms (Development and cRoms)http://www.arctablet.com/blog/forum/rk3288-entwicklung-und-customroms-development-and-croms/rk3288-rom-insignia-flex-elite-lp-5-0-2-custom-root-firmware-20150808/page-8/#p58714I checked your photo, even it is not very big... I cannot see any obvious test-points. But there are several cables and stickers on it where I can't see through. On one tablet I had, all the test-pins where on the bottom side, on several others these two pins, together with a ground pin where routed to an exposed position...
]]>Tue, 23 Aug 2016 14:41:23 +0200graphdarnell on [ RK3288 ROM ] Insignia Flex Elite LP 5.0.2 custom root firmware (2015/08/08)http://www.arctablet.com/blog/forum/rk3288-entwicklung-und-customroms-development-and-croms/rk3288-rom-insignia-flex-elite-lp-5-0-2-custom-root-firmware-20150808/page-8/#p58713
RK3288 Entwicklung und CustomRoms (Development and cRoms)http://www.arctablet.com/blog/forum/rk3288-entwicklung-und-customroms-development-and-croms/rk3288-rom-insignia-flex-elite-lp-5-0-2-custom-root-firmware-20150808/page-8/#p58713I don't see TX and RX testpoints on the board; or if there are, they are unmarked. I guess we have to let it go at that since even RK can't help. I did try to flash the loader in MaskRom mode 3 times. They all came out ok but only up to that point. Never seen anything like that. But thanks again for all the help.
]]>Tue, 23 Aug 2016 12:23:42 +0200Astralix on [ RK3288 ROM ] Insignia Flex Elite LP 5.0.2 custom root firmware (2015/08/08)http://www.arctablet.com/blog/forum/rk3288-entwicklung-und-customroms-development-and-croms/rk3288-rom-insignia-flex-elite-lp-5-0-2-custom-root-firmware-20150808/page-8/#p58712
RK3288 Entwicklung und CustomRoms (Development and cRoms)http://www.arctablet.com/blog/forum/rk3288-entwicklung-und-customroms-development-and-croms/rk3288-rom-insignia-flex-elite-lp-5-0-2-custom-root-firmware-20150808/page-8/#p58712The issue I have is, that I cannot see, what your tablet is really doing...
Are you able to attach a 3V serial port adapter to the RX and TX tespoints of your tablet? I do not know if you can do that or even have such a thing. Beware, that there are 5V (Arduino) adapters and 3V3 versions. The 5V version will kill your SOC, so if you can do that, take care.

If not... It is a bit difficult to analyze the issue without having more details...

]]>Tue, 23 Aug 2016 08:53:06 +0200graphdarnell on [ RK3288 ROM ] Insignia Flex Elite LP 5.0.2 custom root firmware (2015/08/08)http://www.arctablet.com/blog/forum/rk3288-entwicklung-und-customroms-development-and-croms/rk3288-rom-insignia-flex-elite-lp-5-0-2-custom-root-firmware-20150808/page-8/#p58711
RK3288 Entwicklung und CustomRoms (Development and cRoms)http://www.arctablet.com/blog/forum/rk3288-entwicklung-und-customroms-development-and-croms/rk3288-rom-insignia-flex-elite-lp-5-0-2-custom-root-firmware-20150808/page-8/#p58711Thanks for sending in the request. As said above, I flashed the specific loader (2.19.04) fine in MaskRom Mode. But thereafter when I tried to flash the parameters along with the kernel in "Found One Loader Device" Mode, the Tool ran the "test device" routine, returned with "test device fail" and would go no further.

Another direction perhaps? If I remember correctly, you designed a rom once for the Nextbook 7.85 equipped with an RK3188 to run off the external SD Card. Is such a scheme feasible at all with the current CPU (3288)?

On my tab, I know the firmware has been erased. However, it acts as if it's still searching for the rom to boot up, going past the initial big logo (INSIGNIA) to the second page where it beams the small "insignia" and remains frozen there. If I leave it on long enough, it would restart the tab to go through the same stages again and again. Is it even possible to get it to read the external SD at this point?

The device isn't worth much now. It makes little economic sense to try to save it. Nevertheless, I'm still interested in solving the technical problems. Why the glitch?

]]>Tue, 23 Aug 2016 08:27:09 +0200Astralix on [ RK3288 ROM ] Insignia Flex Elite LP 5.0.2 custom root firmware (2015/08/08)http://www.arctablet.com/blog/forum/rk3288-entwicklung-und-customroms-development-and-croms/rk3288-rom-insignia-flex-elite-lp-5-0-2-custom-root-firmware-20150808/page-8/#p58710
RK3288 Entwicklung und CustomRoms (Development and cRoms)http://www.arctablet.com/blog/forum/rk3288-entwicklung-und-customroms-development-and-croms/rk3288-rom-insignia-flex-elite-lp-5-0-2-custom-root-firmware-20150808/page-8/#p58710Hi,
I requested this loader from RK for you. They confirmed that it is certified for this type of eMMC. Just give it a try and please report if works.
]]>Tue, 23 Aug 2016 06:55:44 +0200graphdarnell on [ RK3288 ROM ] Insignia Flex Elite LP 5.0.2 custom root firmware (2015/08/08)http://www.arctablet.com/blog/forum/rk3288-entwicklung-und-customroms-development-and-croms/rk3288-rom-insignia-flex-elite-lp-5-0-2-custom-root-firmware-20150808/page-8/#p58709
RK3288 Entwicklung und CustomRoms (Development and cRoms)http://www.arctablet.com/blog/forum/rk3288-entwicklung-und-customroms-development-and-croms/rk3288-rom-insignia-flex-elite-lp-5-0-2-custom-root-firmware-20150808/page-8/#p58709Could you tell me if this is a revised version of the 2.19 loader? The version I used initially was 2.19.07, enclosed in the original rom package. This one bears the designation 2.19.04, which normally means it's older. But so long as it's different, I'll be willing to give it a try. Can you confirm? Thank you.

Edit: flashed 2.19.04 successfully. The rest is same old.... "test device fail"...LF stuck at 0%. From what I can gather, people have had no problems flashing RK3288-based devices with RKAndroidTool, just not with Foresee eMMcs?

I only recently acquired 3 used Flex Elite tab (just tab, no cable) for my kids. My understanding is that the original supplied USB cable is an OTG-USB cable. That's why I was GUESSING an OTG-USB cable may be needed for certain communication/connection.

However, I personally had one USB cable that had contact problems and while trying to short the flash, hold the tablet, press the buttons, there is a lot of movement... So yes, trying a different cable is always a good idea.

However it is only a rare chance for the logged problem of incorrectly identified eMMC / NAND... But yes, try a different cable, just to be sure.

]]>Wed, 17 Aug 2016 08:50:54 +0200Astralix on [ RK3288 ROM ] Insignia Flex Elite LP 5.0.2 custom root firmware (2015/08/08)http://www.arctablet.com/blog/forum/rk3288-entwicklung-und-customroms-development-and-croms/rk3288-rom-insignia-flex-elite-lp-5-0-2-custom-root-firmware-20150808/page-7/#p58623
RK3288 Entwicklung und CustomRoms (Development and cRoms)http://www.arctablet.com/blog/forum/rk3288-entwicklung-und-customroms-development-and-croms/rk3288-rom-insignia-flex-elite-lp-5-0-2-custom-root-firmware-20150808/page-7/#p58623graphdarnell,
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.
]]>Wed, 17 Aug 2016 08:24:32 +0200graphdarnell on [ RK3288 ROM ] Insignia Flex Elite LP 5.0.2 custom root firmware (2015/08/08)http://www.arctablet.com/blog/forum/rk3288-entwicklung-und-customroms-development-and-croms/rk3288-rom-insignia-flex-elite-lp-5-0-2-custom-root-firmware-20150808/page-7/#p58613
RK3288 Entwicklung und CustomRoms (Development and cRoms)http://www.arctablet.com/blog/forum/rk3288-entwicklung-und-customroms-development-and-croms/rk3288-rom-insignia-flex-elite-lp-5-0-2-custom-root-firmware-20150808/page-7/#p58613The 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.

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.

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.

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?

]]>Mon, 15 Aug 2016 20:53:20 +0200graphdarnell on [ RK3288 ROM ] Insignia Flex Elite LP 5.0.2 custom root firmware (2015/08/08)http://www.arctablet.com/blog/forum/rk3288-entwicklung-und-customroms-development-and-croms/rk3288-rom-insignia-flex-elite-lp-5-0-2-custom-root-firmware-20150808/page-7/#p58589
RK3288 Entwicklung und CustomRoms (Development and cRoms)http://www.arctablet.com/blog/forum/rk3288-entwicklung-und-customroms-development-and-croms/rk3288-rom-insignia-flex-elite-lp-5-0-2-custom-root-firmware-20150808/page-7/#p58589I 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]
]]>Mon, 15 Aug 2016 20:45:37 +0200Oma7144 on [ RK3288 ROM ] Insignia Flex Elite LP 5.0.2 custom root firmware (2015/08/08)http://www.arctablet.com/blog/forum/rk3288-entwicklung-und-customroms-development-and-croms/rk3288-rom-insignia-flex-elite-lp-5-0-2-custom-root-firmware-20150808/page-6/#p58578
RK3288 Entwicklung und CustomRoms (Development and cRoms)http://www.arctablet.com/blog/forum/rk3288-entwicklung-und-customroms-development-and-croms/rk3288-rom-insignia-flex-elite-lp-5-0-2-custom-root-firmware-20150808/page-6/#p58578The bootloader doesn't like to communicate with us. In such cases we need the 1st stage bootloader, which is in the SoC. Is it possible to open the tab?

]]>Mon, 15 Aug 2016 10:40:15 +0200graphdarnell on [ RK3288 ROM ] Insignia Flex Elite LP 5.0.2 custom root firmware (2015/08/08)http://www.arctablet.com/blog/forum/rk3288-entwicklung-und-customroms-development-and-croms/rk3288-rom-insignia-flex-elite-lp-5-0-2-custom-root-firmware-20150808/page-6/#p58572
RK3288 Entwicklung und CustomRoms (Development and cRoms)http://www.arctablet.com/blog/forum/rk3288-entwicklung-und-customroms-development-and-croms/rk3288-rom-insignia-flex-elite-lp-5-0-2-custom-root-firmware-20150808/page-6/#p58572Thanks for the instructions. AndroidToolRK in Windows has no problem recognizing the tab. But just as reported earlier by DanEE, it cannot write anything to the NAND. Low level format gets stuck at 0% and won't progress further. To flash according to Bobb's method requires that the tab boot up, which it doesn't in my situation. But I will try Linux to see what happens. Again thanks for the reply. I know you have bigger fish to fry and do appreciate your taking the time to answer trivial questions like mine.
]]>Sun, 14 Aug 2016 22:30:04 +0200Oma7144 on [ RK3288 ROM ] Insignia Flex Elite LP 5.0.2 custom root firmware (2015/08/08)http://www.arctablet.com/blog/forum/rk3288-entwicklung-und-customroms-development-and-croms/rk3288-rom-insignia-flex-elite-lp-5-0-2-custom-root-firmware-20150808/page-6/#p58566
RK3288 Entwicklung und CustomRoms (Development and cRoms)http://www.arctablet.com/blog/forum/rk3288-entwicklung-und-customroms-development-and-croms/rk3288-rom-insignia-flex-elite-lp-5-0-2-custom-root-firmware-20150808/page-6/#p58566The stock recovery is only good to format partitions. Other functionality is not given by fact.

We do not know this behaviour from any other RK tab. It does not make sense that the bootloader on the NAND cannot communicate with the FlashTool.

Other typical major issue is the driver installation under Windows. Unsigned RK driver and Win8, Win10 are not friends

I found myself in a similar situation as yours, where my tab would go as far as recovery and ADB sideload. I've been trying to load Oma's rom (or parts thereof) without success because of the signature requirement. Wonder if it would be at all possible for you to upload your stock rom that you restored on your tablet in its skeletal form (minus the personal and custom stuff thereon, of course) so I can try to revive mine.

I've been looking for a stock rom in vain. I'd appreciate it very much if you could help. Thanks again.

G. Darnell.

Oma:

In the alternative, is it possible to have a copy of DanEE's stock rom that you used as the basis for your rom? As said, I've only access to stock recovery so flashing anything other than stock is not feasible. Thanks again.

psiufoxx said
I got it to work! Was able to restore a backup, and then before doing anything else I followed bobb's instructions exactly and got OMA on there. Very nice ROM you got here. 😉 Thanks all!

This thread has been inactive for a while so I'm not sure if anyone is following, but I stake my chance just in case. psiufoxx may I ask how you managed to make a backup where no custom recovery can be installed? Also, my unit right now is boot-looping at the insignia logo flashing and dimming stage. I've tried to sideload the img's in OMa's rom but it would not update because of the signature or lack thereof.

1. Would anyone be lucky enough to have the official OTA somewhere that I can download? I'd appreciate that very much.

2. Failing that, can I ask Oma if there's a way to flash your rom at the bootloader screen with something similar to fastboot command? Or is this function totally locked? If yes, is there anything else I can try? The tab is totally stuck at the moment so I'm ready for whatever risky procedure there is. Thanks again for any reply.

PS: Oma, I did try the method you suggested some time ago for flashing the TWRP recovery. The android tool recognized the loader (tablet) but as DANee posted at the beginning, the tool did nothing. I can't do the dd script because the tablet won't finish booting.

I'm trying to follow your instructions to install OMA rom on the Insigna Flex Elite, and while it mostly works, when I get to the system.img step I always get "No space left on device" after running the command.

5. take the microsd card and plug it into your tablet, turn tablet on.

6. Using esfile explorer, copy the above files onto the sdcard in your tablet (not into a folder on the sdcard, just the sdcard itself)

7. Open terminal emulator, type in 'su' without quotes and hit enter.

8. you will see a # at end of the next line (means you have super user access)

9. type in 'dd of=/dev/block/mmcblk0p3 if=/mnt/sdcard/resource.img bs=4096' without quotes, hit enter (it will say it copied a file across for all of these as you do them, system.img will take some time)

15. KingRoot will let you turn off some things at start (Auto-start), I uninstalled Purify (in KingRoot).

16. I also installed droidwall to stop apps from accessing internet as KingRoot tries to contact some server sometimes.

Hope this covers it...

Many thanks to Oma!

I'm trying to follow your instructions to install OMA rom on the Insigna Flex Elite, and while it mostly works, when I get to the system.img step I always get "No space left on device" after running the command.

copied the oma.../system/lib/libdrmdecrypt.co to /system/lib/ on tablet

copied the oma... /system/vendor/lib to /system/vendor/lib on tablet

]]>Tue, 16 Feb 2016 00:09:44 +0100resinis on [ RK3288 ROM ] Insignia Flex Elite LP 5.0.2 custom root firmware (2015/08/08)http://www.arctablet.com/blog/forum/rk3288-entwicklung-und-customroms-development-and-croms/rk3288-rom-insignia-flex-elite-lp-5-0-2-custom-root-firmware-20150808/page-5/#p56237
RK3288 Entwicklung und CustomRoms (Development and cRoms)http://www.arctablet.com/blog/forum/rk3288-entwicklung-und-customroms-development-and-croms/rk3288-rom-insignia-flex-elite-lp-5-0-2-custom-root-firmware-20150808/page-5/#p56237Trying to get OMA rom on mine. I bought it used and someone must have been messing with the rom because it runs like dogpoo.

forcesystemclose at startup and it takes about 5 min to boot. i dont think its hardware issue because once i eventually get it into an app it works really fast.

just got it rooted with kingroot, but now it boots to a black screen, all i have is the home buttons and the nav bar on top. frustrating

I know it's a lot to ask but have we given up on the RK flash tool insofar as recovery or flashing other stuff? I did ask the only member (bobb) who reported to have successfully flashed the firmware according to your instructions of command lines (p. 3, I think), but no response was posted. Is it possible to flash the custom recovery via command lines, and if so, what are they? Thanks a bunch in advance.

bobb said
Netflix not working, just stays at loading...
Seems to boot faster with some of the telephone stuff removed, and others disabled (Hangouts, etc.).
The only way to keep root for terminal emulator is to re-install busybox after each shut down.
Ordered a battery (6000mah) from aliexpress, will be a few weeks before it arrives.

Antutu v6 score 46,254 with Oma's rom, was 48,920 before Oma's rom was installed, thought it would increase with removal of apps.

A word of caution: I dropped the thing today and the touchscreen cracked. Opened it to see if it could be replaced. The battery is a particular pain to remove. It is glued to the back of the lcd display by two strips of unusually strong adhesive running the length of it. You will see two blue tabs at the top. The strips begin there and end at the bottom.

The only way to get it off is to scrape the adhesives off. Since the glue is really strong, you might tear the outer silver lining of the battery even when using a thin blade to slice through. Moreover, if you exert too much pressure to the back of the display, you might break its super thin and brittle surface (cheap material?). I've worked on quite a few touchscreens, but have never seen anything this fragile. If you crack it, the only way is to buy a new tablet.

The touchscreen is "fused" to the display with LOCA, and glued to the plastic frame with the same insane adhesive. A hairdryer won't mollify it; a heatgun will melt and deform the plastic frame. A combo digitizer/lcd in a new frame is not available anywhere, and if it is, it would cost almost as much as a new tablet. Best Buy clearly doesn't want its customers to fool around with the hardware. So be warned.

]]>Thu, 07 Jan 2016 11:33:51 +0100bobb on [ RK3288 ROM ] Insignia Flex Elite LP 5.0.2 custom root firmware (2015/08/08)http://www.arctablet.com/blog/forum/rk3288-entwicklung-und-customroms-development-and-croms/rk3288-rom-insignia-flex-elite-lp-5-0-2-custom-root-firmware-20150808/page-4/#p55772
RK3288 Entwicklung und CustomRoms (Development and cRoms)http://www.arctablet.com/blog/forum/rk3288-entwicklung-und-customroms-development-and-croms/rk3288-rom-insignia-flex-elite-lp-5-0-2-custom-root-firmware-20150808/page-4/#p55772Netflix not working, just stays at loading...
Seems to boot faster with some of the telephone stuff removed, and others disabled (Hangouts, etc.).
The only way to keep root for terminal emulator is to re-install busybox after each shut down.
Ordered a battery (6000mah) from aliexpress, will be a few weeks before it arrives.

Antutu v6 score 46,254 with Oma's rom, was 48,920 before Oma's rom was installed, thought it would increase with removal of apps.

Bobb said to use es explorer to transfer the files from Sd card to internal storage. I was able to transfer, only from PC directly to internal storage. Otherwise, I couldn't for the life of me, get the utility to see the external sd card at all. What am I missing? Or is it just the limitations of this machine. Please enlighten me.

bobb said
I ran an mp4 movie on loop (the file was on my external sd card) with brightness set at 50% and volume off and wifi turned off and the movie ran for 5.5 hrs.

Overall, I believe battery life is better, I get about 4+ hours surfing the net, etc.

On standby, with the setting to drop wifi connection when sleeping, over night (10 hours) battery only decreased 5%.

I was able to install Omas Rom following your instructions. So thank you for that. The RK tool Oma provided still doesn't work. I wonder if there's a way to flash the custom recovery via fastboot instead. Thanks again for your work.

5. take the microsd card and plug it into your tablet, turn tablet on.

6. Using esfile explorer, copy the above files onto the sdcard in your tablet (not into a folder on the sdcard, just the sdcard itself)

7. Open terminal emulator, type in 'su' without quotes and hit enter.

8. you will see a # at end of the next line (means you have super user access)

9. type in 'dd of=/dev/block/mmcblk0p3 if=/mnt/sdcard/resource.img bs=4096' without quotes, hit enter (it will say it copied a file across for all of these as you do them, system.img will take some time)

This is still a flash driver issue. Use the tool set from post #27. Update.img see post #20.

- Oma -

]]>Mon, 19 Oct 2015 06:44:01 +0200rrobinson1216 on [ RK3288 ROM ] Insignia Flex Elite LP 5.0.2 custom root firmware (2015/08/08)http://www.arctablet.com/blog/forum/rk3288-entwicklung-und-customroms-development-and-croms/rk3288-rom-insignia-flex-elite-lp-5-0-2-custom-root-firmware-20150808/page-2/#p54601
RK3288 Entwicklung und CustomRoms (Development and cRoms)http://www.arctablet.com/blog/forum/rk3288-entwicklung-und-customroms-development-and-croms/rk3288-rom-insignia-flex-elite-lp-5-0-2-custom-root-firmware-20150808/page-2/#p54601Would love to get this working! Tried on two computers so far but might try more at work tomorrow. Followed all the instructions, but the tool never sees the device - also, to see it, shouldn't the device notice the computer when Debugging is turned on and ask you to 'trust' the device? The computer I tried also seemed to love attempting to install other drivers as well.

]]>Thu, 13 Aug 2015 20:52:55 +0200TesseractSpace on [ RK3288 ROM ] Insignia Flex Elite LP 5.0.2 custom root firmware (2015/08/08)http://www.arctablet.com/blog/forum/rk3288-entwicklung-und-customroms-development-and-croms/rk3288-rom-insignia-flex-elite-lp-5-0-2-custom-root-firmware-20150808/page-2/#p53427
RK3288 Entwicklung und CustomRoms (Development and cRoms)http://www.arctablet.com/blog/forum/rk3288-entwicklung-und-customroms-development-and-croms/rk3288-rom-insignia-flex-elite-lp-5-0-2-custom-root-firmware-20150808/page-2/#p53427I'm getting the same result. I'm no engineer so I'm afraid I can't pop it open and mess with it, but I too get 0% of the lowerformat when I try to do so, as well as test fail.
]]>Thu, 13 Aug 2015 20:06:13 +0200Oma7144 on [ RK3288 ROM ] Insignia Flex Elite LP 5.0.2 custom root firmware (2015/08/08)http://www.arctablet.com/blog/forum/rk3288-entwicklung-und-customroms-development-and-croms/rk3288-rom-insignia-flex-elite-lp-5-0-2-custom-root-firmware-20150808/page-2/#p53403
RK3288 Entwicklung und CustomRoms (Development and cRoms)http://www.arctablet.com/blog/forum/rk3288-entwicklung-und-customroms-development-and-croms/rk3288-rom-insignia-flex-elite-lp-5-0-2-custom-root-firmware-20150808/page-2/#p53403I don't see any reason why this should not work, except the hardware is corrupted. We will see if there is other feedback.

I have come to the conclusion that the bootloader is a special build. I think only way to root it and get a new ASOP ROM using the AndroidTool would be to get into the MASKROM mode. This may be a second shooter on the grassy knoll theory.

The lower 2K*32bit space where the bootloader resides cannot be read other than the CMDLINE area. This prevents me from dissembling bootloader.

The internal images on the FCC site show a different board with a pressure switch that can be activated by squeezing the cover. This is not present on the production card. I suspect this was used to recover bricks during development.

I think that the manufacturer has a version of the AndroidTool that can send a special command to unlock the bootloader to enable reflashing for units. Unless this get leaked and posted, the MASKROM must be used for the AndroidTool.

Maybe there will be an update for this tablet in the future that fixes the short comings that the firmware has right now. Other than an undersized battery, the hardware is very good. Most of the issues seem to be in the firmware. RockChip could compete with Samsung, Qualcomm and others if they would just clean up the SDK and help the manufacturers with the firmware. This chip seems to have more support for set top boxes than tablets.

Until there is a field update that can be examined to find another approach, this is going on the back burner for now. I have too much going on to devote much time to this now. I may go ahead and magwire the eMMC clock someday, however as an engineer I am working on stuff that is more challenging and fun.