yashsingh1/xdaforums huggingface dataset:
[Android General] blakegriplingph:
Alright, noted. I did manage to get one recovery to compile once; it just baffles me that this doesn't. :/

EDIT: Got even further with the build, but feel free to correct and/or test if necessary. It's that for some reason my build environment's a bit messed up and is in need of a refresh, i.e. I am forced to wipe it all and reload from the repo as I am getting syntax errors. The device trees are still in my archives though.

Also, would it matter if the manifest used is for CM12.1 even if the Epic is currently running off Kitkat?
[Android General] blakegriplingph:
I hope [MENTION=7237874]NepoRood[/MENTION] doesn't mind, but any news on building the recovery? Would like to try it out myself but I'd be forced to download gigabytes of code for my build environment. :/
[Android General] NepoRood:
Recovery runs in it's own environment, so it doesn't really matter which source you use to compile it.

I haven't had a chance to try your tree, been working on my ROM for Quark (Droid Turbo) as well as working on adding OMS Rootless commits to AOKP repos. I also don't mind being reminded, I'm forgetful, :silly:

I'll try to get to it today, or Monday though

Regards,

Nepo
[Android General] blakegriplingph:
Lol so I'm in the clear with it then? Assuming that the tablet would actually boot up a custom recovery image that is.
[Android General] blakegriplingph:
Still struggling to get Google Play to work on this tablet. I could just get away with rooting it, but that isn't an option as parents aren't up to voiding the warranty off their kids' devices anyway. The most I could end up with is with Cobalt's modded Play Store coupled with microG, but the latter needs a faked signature for apps to be downloaded properly. Can anyone please help me out?

EDIT: I got the unmodded Play Store to work as well, albeit with the following error upon trying to download apps:

E/AndroidRuntime( 3623): FATAL EXCEPTION: download-manager-thread
E/AndroidRuntime( 3623): Process: com.android.vending, PID: 3623
E/AndroidRuntime( 3623): java.lang.SecurityException: Invalid value for is_public_api: null
E/AndroidRuntime( 3623):	at android.os.Parcel.readException(Parcel.java:1472)
E/AndroidRuntime( 3623):	at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:185)
E/AndroidRuntime( 3623):	at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:137)
E/AndroidRuntime( 3623):	at android.content.ContentProviderProxy.insert(ContentProviderNative.java:468)
E/AndroidRuntime( 3623):	at android.content.ContentResolver.insert(ContentResolver.java:1217)
E/AndroidRuntime( 3623):	at com.google.android.finsky.download.m.run(SourceFile:1039)
E/AndroidRuntime( 3623):	at android.os.Handler.handleCallback(Handler.java:808)
E/AndroidRuntime( 3623):	at android.os.Handler.dispatchMessage(Handler.java:103)
E/AndroidRuntime( 3623):	at android.os.Looper.loop(Looper.java:193)
E/AndroidRuntime( 3623):	at android.os.HandlerThread.run(HandlerThread.java:61)
W/ActivityManager( 630): Force finishing activity com.android.vending/com.google.android.finsky.activities.MainActivity

From what I read moving the app to /system would do the trick, but ideally it would be better for Play Store to run as a user app.
[Android General] blakegriplingph:
Looks like getting third-party homescreens to work is just the matter of editing tablet_core_hardware.xml in /system/etc/permissions. Also, apparently LeapFrog or Quanta codenamed this device as "Narnia" as references to the name can be found in a number of places.

And be careful when rooting the Epic using one-click utilities, as some of them have been found to be messing with the home screen/login screen.

EDIT: Here's a video of the Epic running off Nova Launcher and some Xposed tweaks:

[YOUTUBE]1leOobI2csY[/YOUTUBE]
[Android General] blakegriplingph:
Sorry for the bump, but I just want to let you guys know that if anyone has a spare working Epic motherboard that they're willing to part with, preferably from a retail unit, please let me know.
[Android General] blakegriplingph:
Oh and here's the modded demo ROM since a number of parents have been asking me for this lately:

https://mega.nz/#!cuhHFYTC!GC6wU1MxDybNX_tU50aMpHbFnb3TjAh5dVaWn_cNj8Y

As a bonus I included a minimal Google Play store installation in it with the required framework APKs and Phonesky itself. That way, you can install YouTube Kids on your former demo unit without a hassle.

Major props to Amber Curington for helping me test this on her son's device. :D
[Android General] bovirus:
Which part of the ROM did you mod?

How can flash this ROM in the device?
[Android General] bpivk:
Hey. OT but I can't find a Leap Epic topic anywhere else...

Does anyone know where to find a replacement stylus from my daughters Leap? I have checked Ebay, Amazon, Aliexpres, Google and I don't get any hist apart from some Australian which doesn't ship to Slovenia (EU).
[Android General] NepoRood:
Just Curious...

Has anyone tried porting one of the MT8127 Recoveries that are available? I posted a TWRP or 3 and Tony built a CWM non-touch...
[Android General] blakegriplingph:
I plan on doing so, though I am not sure if it would boot due to the locked preloader. It might work if the existing kernel is used, but that's something I'm yet to find out.

As for the modded ROM I posted earlier, that one can be flashed through SP Flash Tool's hidden Write Memory feature. I wrote a guide on it somewhere in this thread.

Oh and can anyone help me with getting Bluetooth HID support to work on this thing? As [MENTION=543591]RAMChYLD[/MENTION] pointed out in page 1, input device support is nulled out if not neutered, and I was wondering if this is at a kernel level or simply a matter of modding the framework or settings APKs to bring it back.
[Android General] blakegriplingph:
Is anyone interested in testing a Google Apps installer package for the Epic? I am contemplating on making a (semi- ) automated tool for that, in lieu of being able to flash stuff through recovery.
[Android General] bovirus:
I'm very interested.....

Thanks.
[Android General] Hitek146:
OK, not done yet... :)

I'm an ex-hardware engineer that now drives an 18 wheeler around the country. I found a demo unit at a Walmart for $15 yesterday, and would enjoy hacking this unit, just for the challenge(I have 8 Galaxy devices and 8 other android devices, all rooted and most bootloader unlocked). Software is not my strong suit, but I will contribute in any way I can. Being on the road, though, I have no build environment with me, as my linux machine is back at home. I could throw something together, though. If anyone is still watching this thread, I am willing to do anything I can to help....
[Android General] blakegriplingph:
That would be very much appreciated, mate. I did some initial work for the Epic since February, but there are still a number of things in need of poking and prodding into. Heh, ever since I worked on this thing a number of parents have been messaging me on Facebook asking if I could unlock their kids' devices for them. :D
[Android General] Hitek146:
Great! Having read through the thread, I noticed that you were cautious in suggesting courses of action because a child's toy may be damaged. This is not a problem for me, as the unit I bought is destined for experimentation. I will need to re-read this entire thread again, in order to duplicate the success you have had, as it seems the process is quite intricate. Before I proceed, is there anything I should save or backup(for community purposes; I have no need, personally) before I move forward?
[Android General] blakegriplingph:
Nice, and yeah, the bootloader hasn't been unlocked yet which is a pain as I wanted to try out the kernel sources LeapFrog sent to a friend of mine. I've wrote a long-winded post on my blog detailing what I pretty much did, and while it isn't exactly the most elegant solution ever, it worked. That being said a more reliable solution would be to unlock the boot loader and be able to flash unsigned images to the device in a conventional fashion, not just /system.

You thinking of getting your hands on a second unit, or perhaps a retail motherboard?
[Android General] blakegriplingph:
Also, does anyone by any chance have the Academy Edition variant of the Epic? I'd like to see how different the firmware is compared to the original. At worst this would still be running off Kitkat but who knows?
[Android General] Mithil Majumder:
Have anyone tried to unlock the bootloader via Miracle Box Flashing Software. I cant flash these roms via SPFT because the bootloader is dead, and my epic tab is fully bricked. Please do anything to unlock the bootloader or sign the preloader.
[Android General] blakegriplingph:
Have you tried using the Write Memory option? I also have a bricked Epic in need of TLC as I flashed a retail ROM by accident.

I don't have an actual Miracle Box or anything else of that sort with me, but I do want to give that one a shot as I've heard of no one else try using any of those tools on a LeapFrog yet.
[Android General] Mithil Majumder:
Try to flash the file with other softwares. I think that one of that may help to unbrick the tab and forcedly download the preloader without signature.

I HAVE TRIED TO WRITE MEMORY. MEMORY WRITE DONE BUT NO SIGN OF ANY LIFE

Reply me as soon as possible. I am busy right now.
[Android General] blakegriplingph:
Yeah but as I said before I don't have access to a flasher box right now. I do plan on buying one soon but for one I would be more than glad to have another Epic for testing, or someone to donate a Miracle Box since I don't have the budget tbh.
[Android General] blakegriplingph:
Seems like LeapFrog rolled out a new build last March (KOT49H.user.1.7.18.2017327.110821). Doubt it's Lollipop, let alone Marshmallow (oh brother!) but I got this off a friend who was asking as to how he can bypass the activation lock present on new smart devices called DiSA by Digital Safety USA. It appears to be some deterrent against shoplifters where in the device has to be activated prior to leaving the store, and if you don't have a valid activation key, you're SOL.

I don't think I'd be publicly disclosing any way of bypassing this due to legal concerns, but I hope the protection doesn't extend to the bootloader itself.
[Android General] og style:
I bought a epic and I just found out it is a demo unit with KOT49H.user.1.1.99.20150807.173011. Has anyone figured out how to get it running the normal rom?

Thanks
[Android General] blakegriplingph:
Yup, I did. I made a guide on my blog showing how to convert a demo unit into a fully functional one, in case you're interested:

https://huckleberrypie57.blogspot.com/2017/05/may-i-interest-you-in-yet-another.html
[Android General] og style:
Thanks a lot. I'll give that a try.
[Android General] blakegriplingph:
Let me know if you need help with the conversion though. ;)
[Android General] og style:
I will. Do you know why there are so many demo units floating around.

---------- Post added at 02:03 PM ---------- Previous post was at 01:55 PM ----------

Is this the image that I need to download?

stock ROM dump courtesy of [MENTION=543591]RAMChYLD[/MENTION]. As with epic__fail's ROM this one won't work with a locked bootloader.
[Android General] blakegriplingph:
That, and the modded demo ROM. You'll need RAMChYLD's dump so you can load the scatter file for readback and write memory to work.
[Android General] og style:
Is that the one that is labled "Kernel source ISO:"?
[Android General] blakegriplingph:
Of course not. That one is the source code by LeapFrog themselves.
[Android General] og style:
Can you provide me to a link for the download?

Thank You
[Android General] blakegriplingph:
Alright mate, you asked for this. :P

ROM dump with scatter file:

https://mega.nz/#!Jg1hSRSJ!xRoup9kZ1sSEiTwV5Fw_Jb5dgxBoXlSoxcaOvU1d6CM
PASS: epic

Pre-modified ROM:

https://mega.nz/#!cuhHFYTC!GC6wU1MxDybNX_tU50aMpHbFnb3TjAh5dVaWn_cNj8Y
[Android General] Mithil Majumder:
These two ROMS can't be flashed I've tried to flash with different types of powerful flashing softwares. I've also tried the partial flashing but every time I failed. So I am requesting the expert users to upload a fresh ROM again. So that I will be able to flash my dead epic tab. Please try to modify the "sec.ro" or something related in the ROM. That contains the digital signature for the rom. As the ROM is not signed it fails again and again to flash. Or please contact the leapfrog team for a pure official ROM or for the digital signature image. Otherwise try to upload a fresh epic tab's ROM. So that we can solve the problem and close these boring chattings.
[Android General] blakegriplingph:
The problem is every time we back up the ROM, the digital signature is lost and thus any dump we make is unsigned. There's little we could do atm other than to use the Write Memory feature or contact LeapFrog about it.
[Android General] Mithil Majumder:
I have tried to write the memory. Memory write done but why the tab is not flashing. I mean I have finished the process but my tab is still dead because of bootloader dead. Are there any successfull user who was able to flash the rom via write memory. Please try to backup the rom via Miracle Box. Or try to install ROM Backup, Or Titanium Backup to backup apk to fully backup the rom and upload the rom
[Android General] blakegriplingph:
I don't have a Miracle Box ATM.
[Android General] pperezbarrios:
How can I put it in Spanish?
[Android General] blakegriplingph:
I'm afraid there's no Spanish-language option for the Epic as of now. You can work around this by rooting the tablet and installing Locale More or a similar tool, but not all apps would have their UI in Spanish. Tis understandable though as the cost of localising games and other apps to other languages (e.g. voice acting or separate SKUs for different regions) would drive up the device's already expensive price.
[Android General] blakegriplingph:
Bumping in case anyone is still interested.
[Android General] Mithil Majumder:
Post fresh digitally signed rom for leapfrog epic tab

Hey there i have requested many times to post a fress digitally signed rom for leapfrog epic tab. But no one can't do that. So why the post is for. Delete this post if you can't. You have told to flash the uploaded rom by many theories. But all of those tricks didn't worked.

I have tried writing the rom (write memory) option via sp flash tool. Downloaded all of the roms. And tried flashing. But every time it called for a thing is the digital signature is not present in the "sec.ro" file. So that the rom can't be flashed. On the other hand the rom is not writing via memory writing. It told that it has sucessfully write the rom but nothing is showing in my tab screen. Such as charging, light beeping, logo etc. So it means that the rom hasn't flashed ptoperly. For this i am requesting all of you that if any of you has a alive leapfrog epic tab running properly please try to post a fress rom from your leapfrog epic tab. So that i can flash my tab and can make it alive. Thank you.
[Android General] blakegriplingph:
Here's the problem: I can't extract the digital signature off the device regardless of how I rip it. And the reason why your tablet's bricked is that the preloader's hosed, plain and simple. I honestly don't know of anyone else who is willing to devote his time in reverse-engineering the Epic, as this is a niche device for children. Your best bet is to wait and pray that some kind chap would come in and help open the doors to custom ROM development for this thing.

Why don't you try probing ground and KCOLO to see if you can force it out of limbo? There's a guide somewhere on the web about finding those testpoints especially if they're not silkscreened on the motherboard.
[Android General] blakegriplingph:
[MENTION=6791201]Warrior1988[/MENTION] mentions that SP Flash Tool v5.1532 works on the device, which is corroborated by a FAQ on Hovatek telling people to use that exact version should they encounter such an error. Problem is even if you do manage to flash it, the device stays dead especially if you previously bricked it before.
[Android General] blakegriplingph:
There, just posted a link to a working Academy Edition ROM on my original post, version KOT49H.user.1.1.95.20171215.140555. LeapFrog released said firmware last December, though I find it a bit strange that they still stuck to Kitkat even if the MT8127 is perfectly capable of running Lollipop and later. Should also work on the regular edition too, btw. :P

Special thanks to [MENTION=8132642]diplomatic[/MENTION] for schooling me about MTK internals e.g. the bootloader and signed firmware. ;)
[Android General] blakegriplingph:
And here's a video tutorial on how to fix LeapSearch/YouTube on certain Epic SKUs:

[YOUTUBE]OpUgI8ZSkP4[/YOUTUBE]
[Android General] Tickbaby:
Will this revive it if it's completely dead?
[Android General] blakegriplingph:
Assuming you have a complete backup of the previous ROM that is. How did you brick it if you don't mind telling?
[Android General] blakegriplingph:
Unofficial TWRP 3.0.2-0 for Academy Edition

Can be flashed through SP Flash Tool v5.1744 or later using the stock 1.1.95 ROM. Usual precautions of course.

Basic functionality works, e.g. backup, ZIP flash, ADB/MTP and so on. This is by and large a better alternative than using Kingoroot or any of those shady root utilities, not to mention it allows users especially parents to back up stuff from their kids' Epics prior to a factory reset or some other repair job.

Screenshots

More screenshots can be found here: https://imgur.com/a/xgicM

Device tree: https://github.com/huckleberrypie/device_quanta_narnia/
Recovery image: https://github.com/huckleberrypie/device_quanta_narnia/releases

Again special thanks to [MENTION=8132642]diplomatic[/MENTION], [MENTION=543591]RAMChYLD[/MENTION] and some of my other buddies for making this possible, and of course the TeamWin team. ;)
[Android General] gerryl432:
Is there a key combo to get out of fastboot mode? Let battery drain? My daughter did something to get into fastboot lol

Edit: I opened it up and disconnected the battery for a few seconds. Booted right up.
[Android General] blakegriplingph:
Yup, that's what I did as well. Fastboot mode is strangely nerfed on this thing I'm afraid.
[Fire Q&A, Help & Troubleshooting] drillster:
Hey everybody!

This is my first time posting something on XDA. This is really cool.

So I just bricked my fire, hard. Let's start from the top:

- I used the super tools rootjunkysdl.com/?device=Amazon%20Fire%205th%20gen&folder=SuperTool to get the google play store.

- Using the google play store, I got flashfire.

- Using flashfire, I flashed SlimLP onto my tablet successfully and quickly.

- I got a little cocky, and based on the comments on the youtube.com/watch?v=NaCBSuUuhRE video that I used to flash SlimLP I decided to try the flashfire technique with CM since it is my favorite ROM.

- I did everything properly and the same, but... it got stuck here... for about an hour...

imgur.com/QJvmRz3

So I decided to do the smartest thing ever and cancel it myself by turning it off, I wasn't able to do anything else anyway. Either way, my tablet is now stuck in the cyanogen 12 boot load animation, the one of the cute blue head with the radar effect.

I would of fixed this a long time ago, but for some reason I'm not able to adb sideload.

I go into fastboot, I can detect the device, but not adb sideload.

I go into adb sideload mode, I can't detect the device, so definitely not sideload. :/

I've tried updating my drivers, I don't know if I'm doing it right, but while it was in fastboot mode, I changed it to Android Composite ADB Interface, and that didn't change anything.

No matter what I'm doing, whenever I do adb devices, I always get:

List of devices attached

Blank. Nothing. Only when I'm in fastboot mode do I get:

fastboot devices

G0K0H40454261ARU fastboot

Something, but still no ADB. I can't even load TWRP here, tried that, I just install it and it just sits there dumbly saying it's installed.

I'm bricked just like my tablet. Could I please get some help here? I'm very desperate to get this tablet back up and running, and I feel so stupid for not having stuck with Slim and trying to install CM. I really don't want it to stay bricked like this. :(

Thank you, XDA!
[Fire Q&A, Help & Troubleshooting] blueberry.sky:
Do you know if you had amazon FireOS version 5.0.1 or 5.1.1?

Just to be clear, you have actually selected the adb sideload option on your Fire when you try to connect with adb on you pc, correct? ADB is not even active until the adb sideload option has been selected.

We can not "install" twrp. The bootloader is locked & won't allow it. We can only temporarily load twrp into memory. Each time we want to use twrp, we must connect usb to a pc, enter fastboot mode & load twrp. But this can only been done on 5.0.1 Fires. It's been blocked on 5.1.1. No way to load twrp at all on 5.1.1.
[Fire Q&A, Help & Troubleshooting] hAtE NeVeR dIeS:
Just use this method: http://xdaforums.com/amazon-fire/orig-development/howto-how-to-restore-frimware-device-t3238740
[Fire Q&A, Help & Troubleshooting] blueberry.sky:
Do not follow the instructions in that thread! It will permanently brick you if you're have the FireOS 5.1.1 bootloader. The OP of that thread finds it too hard to add a note that it's outdated. See the page 4, post #36
[Fire Q&A, Help & Troubleshooting] drillster:
I have 5.1.1... yeah, thanks.
[Fire Q&A, Help & Troubleshooting] drillster:
I have 5.1.1.

Yeah I selected apply update from adb, adb devices was blank, didn't work.

I went into fastboot mode, installed twrp, and nothing happened because yes, its 5.1.1.
[Fire Q&A, Help & Troubleshooting] blueberry.sky:
I've seen some other people who also have been unable to get adb to work (in custom recovery). I don't recall a solution.

There is an option in fastboot to flash firmware, I haven't seen anyone try that yet..
[Fire Q&A, Help & Troubleshooting] drillster:
Do you have any ideas on how to do this? I would greatly appreciate it.

Thank you!
[Fire Q&A, Help & Troubleshooting] blueberry.sky:
Since I haven't read anyone try it before, there would be some risk. I suppose you are already bricked, seemingly without a way to fix it, but you could brick it harder. You might be able to get adb working. I may not have any ideas on how to get adb working for you, but someone else might know. If you try flashing the stock OS via fastboot, there is a chance you could brick it in a different way.

The command would be

fastboot update <filename-of-stock-firmware.zip>

But we don't have a .zip stock firmware file. In twrp recovery you can just rename the .bin file to .zip & it works. Not sure if that will also work for fastboot. My guess is it won't work & might brick you.

Also be aware, on Fires that self-updated to FireOS 5.1.1 (or came with 5.1.1 new) you must only flash 5.1.1. Attempting to flash 5.0.1 will brick it 100% of the time & it's unrecoverable.
[Fire Q&A, Help & Troubleshooting] DoLooper:
Just a shot in the dark here, but have you gone into device manager while in sideload mode and updated drivers for KFFOWI under Other devices? Windows needs drivers for every mode.