yashsingh1/xdaforums huggingface dataset:
[MeMO Pad 7 General] Penguineh:
That is such a terrible joke! :)

Nah, I've been busy also and have taken a few days off the annoying problems of technology in general.

I was experimenting with Android x86 (The project mentions it has Baytrail Support), with the intention to load the proprietary blobs extracted, but my tablet having motherboard issues causes it to require a battery pull for a few hours every time it attempts to load.

When these issues occur, I have to disconnect the battery for an hour and pray it will work again once reconnected. The intel logo does not display and I cannot even access the UEFI GUI. This is one of the reasons my updates are irregular. Clonezilla loads fine, interestingly.

For those that are interested and to help diagnose the problem (I have heard numerous have the same issue), it can be triggered also by the issuance of the invalid command "reboot now" rather than "shutdown now". I presume it has something to do with the Bootloader Control Block and a valid command might be "reboot recovery" etc (like adb).
[MeMO Pad 7 General] social-design-concepts:
Tell me about it, lol. . .

So much drama in the Intel /x86 Android community. . . I think Intel needs to step up and do the right thing by fully releasing the open source components of their Android BSP's instead of only making them available under NDA, The IRDA program should of been the rebirth of an Intel / x86 Android Community.
[MeMO Pad 7 General] Mis012:
Yeah I hate this issue I had a tablet in this state for a month until I tried to trickle cherge the battery and then after the 30 minutes exact (15 min. each cell) I tried to power on and it worked. It was like first time I managed to solve problem which seemed unsolvable. I get it anytime I power off the tablet without android fully loaded AND responding - android handles the long power button lold before it's long enough to be recognized. But also happening when android totaly freezes, so I's not releted to UEFI which should not be in play as it gives controll to bootloader - which is not in game too - and that gives controll to OS.
[MeMO Pad 7 General] delta 084:
Hello everyone and first of all thanks for your work. I'm really hoping you can get marshmellow or CM13 to work.

I have some questions about this tablet.

1º - anyone had problems with the home button not working properly? I've already factory reset mine but still can use home button (except in some rare cases) to go to the home screen. Even with apex launcher and the home button action selected. I can only go to google now with the long press.

2º - what are the symptoms of the motherboard issues? most of the times I can't even go to the boot menu to reset or wipe cache.

I want to flash a decent rom ASAP but don't want to void warranty before making sure everything with ok with the tablet first :/

Tks
[MeMO Pad 7 General] Ruben Craveiro:
For the 1 it happend to me once when i restored a nandroid backup the way to fix was reinstalling stock rom with temp recovery session and 2 idk what ur talking about and 3 theres still no rom that works with device you still need to wait..
[MeMO Pad 7 General] Penguineh:
To my knowledge only the backlight fault is a symptom of a known motherboard issue. When started the device would only turn on to a powered backlight.

Actually [MENTION=6013061]Mis012[/MENTION], I thought the exact same thing - I thought that the battery had been exhausted and couldn't be charged because it had too low a charge... I tried trickle charging it without success before reading that you need to disconnect the battery for a while..

Want Drama? Console OS would fit the bill!
[MeMO Pad 7 General] jerbear294:
Pfft...

I was actually considering it before I found out it's literally Android-x86.
[MeMO Pad 7 General] social-design-concepts:
<!-- deleted -->
[MeMO Pad 7 General] sidane12:
There is a way to fix black screen? I tried flashing .33 through TWRP, and nothing :crying:
[MeMO Pad 7 General] MaDDaWg836:
Not sure if this has been answered,

How can i get back to i believe its .29 (the one before .33)?

My battery is draining so fast i have to charge it everyday, and some apps keeps crashing. I'm super pissed at this tablet and really want to trash it but id rather revert to a better firmware. is my only choice start from 181 and go incrementally?
[MeMO Pad 7 General] DudeyGeezer:
Hi, I'm on the latest, .33, and haven't got around to rooting yet (not sure if you can) but i tried to get into the recovery menu and all i get is the fastboot one, when i scroll through the options while in that and choose boot to recovery, it just comes up with the same fastboot menu. Am i doing something wrong?
[MeMO Pad 7 General] jerbear294:
That would happen if the recovery it's trying to boot is unsigned or is corrupt.

You'll have to flash the stock recovery via fastboot.
[MeMO Pad 7 General] DudeyGeezer:
I havent modded this one yet so i guess it must have become corrupt somehow.

Is the stock recovery for this available somewhere or is it an asus website thing?

Also, will flashing the stock recovery mess with the data on the tablet at the moment? Im under the impression that it will just flash a different area without effecting whats already on the tablet.

Is this device actually rootable on .33?
[MeMO Pad 7 General] jerbear294:
Yes, the device is rootable on .33.

I might have a backup of the stock recovery somewhere (I'm on TWRP right now) so if I can find it I'll link it later.

Right, it won't mess with any data, only the recovery partition.
[MeMO Pad 7 General] social-design-concepts:
[MENTION=7057426]Penguineh[/MENTION] any progress on your android-6.x.x build?
[MeMO Pad 7 General] jerbear294:
I was about to come on and ask that, but I figured if he had anything to report he'd report it.
[MeMO Pad 7 General] social-design-concepts:
good point.

i'm back to cm-12.1 again. lol. but finally got all the media components to build completely from source (if the actually work properly is another story) but they were the last thing on my list of things i would like to build from source. so now that that is complete, today i start actually working on making it boot.

i know it wont boot in it's current form as my device tree is currently heavily based on android-ia and some dummy .rc files to simply get through the build. so it's off to clean up all that and make it more aosp than android-ia and then hopefully will attempting to boot on device tonight.

as most intel android baytrail devices will see little if any active development the goal is still to make this work against the stock 3.10.xx kernel that ships on the device and have installer that generates a compatibility pack from the device basically the idea is to do the proprietary.txt part of the android build during the install instead of during the build and generate a new boot.img.

but also have a device tree easy enough to hook into that most devices would only need a cm.targetdevice.mk and proprietary.txt file. in the device tree's current state should be everything that is common between all baytrail devices with the exception of the common proprietary files i'll be adding these during the clean up.
[MeMO Pad 7 General] Penguineh:
I'll get back to you guys with a more detailed report in the next few days or so, but essentially because my device is somewhat faulty I cannot safely work with boot.img's that are crazy experimental - that is why I was first attempting to use the stock ramdisk/kernel to get things moving. Seems social-design-concepts is attempting the same sort of thing.. except with a modified ramdisk.

That is actually a really smart idea. The kernel is aware of the proprietary blobs and should only need them in the original folder structure they where originally placed in. I might give something like this a go. :)

With Android 6.0, (this is some half-baked conclusion I came to) wouldn't new features like dm-verity cause incompatibilities with the stock kernel. I am aware some sort of implementation existed in 4.4, but would Android be relying on features that don't exist in the kernel?
[MeMO Pad 7 General] social-design-concepts:
we probably couldn't support dm-verity with out changes to the bootloader but i think this can be turned off? need to check. the android-ia base currently use dm-verity which is why i'm not booting yet once i finish the clean up and build a standard basic android boot.img and get cm-12.1 booting i'll probably turn my attention on to android-6.x.x / cm-13 and go from there.
[MeMO Pad 7 General] daspex:
[MENTION=7057426]Penguineh[/MENTION]

hi maybe this tool i found on xda could help you with the blobs?

http://xdaforums.com/showthread.php?t=2794413&page=1 and a question; could you built your rom so to make it possible to install it over the kk stock rom?

best regards
[MeMO Pad 7 General] Penguineh:
Looks awesome, here is a compiled version for OS X if anyone is interested. Same license as source code.
[MeMO Pad 7 General] social-design-concepts:
that's nifty should come in real handy. thanks
[MeMO Pad 7 General] daspex:
[MENTION=7057426]Penguineh[/MENTION]

l'm still on kk and can't obviously upgrade to LL without sending my device to asus.is there a chance to get the uefi partition over another way or does the ll update patch the firmware in the chipset?

thanks in advance
[MeMO Pad 7 General] Penguineh:
I have absolutely no idea. social-design-concepts or jerbear are way more qualified to answer that :).

It would most likely require an update as it probably flashes an updated image to the chipset.

If someone was able to extract the uefi firmware image, the question remains - would you be willing to risk permanently bricking your tablet? There is a lot you can do safely, more so than a standard arm tablet because you can boot a live os off a usb device, but if you brick the bios/uefi that may not be possible.
[MeMO Pad 7 General] daspex:
[MENTION=4821597]social-design-concepts[/MENTION]

you are welcome.you guy's on this device thread do a hard work and spent your rare free time to make this device cool and work well and you make a lot of people happy so you have to get every information which could be usefull.i'm not a dev and was looking on what the hell are blobs?so i found this util and thougt maybe it could be usefull to you.:)
[MeMO Pad 7 General] jerbear294:
[MENTION=7057426]Penguineh[/MENTION] is right, it's not possible. You'd have to upgrade to Lollipop, as when Lollipop rolled out ASUS replaced the bootloader with a UEFI instead. The UEFI is what's making all of this possible, and is actually better than a bootloader unlock as it allows for booting other operating systems as well.

Why can't you upgrade to Lollipop?

The utility looks nice, looking into it.

Blobs, in layman's terms, are like drivers for Windows. They control portions of the hardware and allow for communication between the hardware and software.
[MeMO Pad 7 General] daspex:
[MENTION=3474936]jearbear[/MENTION]294

yes i know now a lot more about blobs and stuff while reading in the wiki,thanks.

if i do an update i have no issues and every thing looks ok,i've been waiting about 20-30 minutes and it bootloops i have no device version conflicts as other users had it seems to be that the ll installs fine but the bootloader is not changed or the uefi is not present so i thougt i could make all the new partitions from hand with a partition tool but that would'nt work if the firmware of the chipset is changed during stock ll update so i don't know what i could do further.:(
[MeMO Pad 7 General] social-design-concepts:
it's going to come in quite handy for the installer for sure. it doesn't seem to allow you to specify a custom sdk version i'll look into that because it be nice to be able to feed it the file list of the built rom and a file list of know proprietary blobs , but it is a good find for sure.
[MeMO Pad 7 General] Mis012:
UEFI isnot on a partition it is on the mainboard. Sending to Asus is eisiest but if you can access DNX mode you may be able to flash capsule.bin and if it is UEFI then hooray. But you would have no nvram entries so you would have to do some other things but that are definitely possible. Or maybe JTAG or so if someone had it too and sent the dump to you. But I sent my tablet to Asus just to have UEFI, so if you have even better motivation..
[MeMO Pad 7 General] vesko2000:
Since I erased my storage :crying:, which was about two months ago, I've been trying to get completely working a few OSes. The first one was Fedora ( GNOME, KDE, MATE, Xfce - all of them) , as I presumed it has nice support for Bay Trail Chipsets. This wasn't the case. Turns out you can't get sensors, Wi-Fi, Battery, Sound working. The thing that amazed me was that the Goodix touchscreen panel was working and backlight was somewhat working, too. Windows 10 was no different - no support, even with Windows settings on in OS Selection and IGD. But in Windows even the touch doesn't work as there are only 32-bit drivers. I also tried Android-IA - couldn't boot. Android-x86 work partially well - no Wi-Fi, bluetooth, rotation. I also had constant networking enabled through USB and was searching for drivers - no luck :mad:. So now that I've checked every option I'm ready to head back to Asus' ROM. Turns out I can't flash it as I have no recovery. The only way to fix my tablet I could think of is to flash someone else's EMMC dd backup, made through live Linux and flash it. Could someone provide the backup, please :fingers-crossed:? Does anyone have any other ideas how to get out of this situation :confused:?
[MeMO Pad 7 General] Ruben Craveiro:
i could make emmc backup of some partitions

EDIT: Boot-Recovery-fastboot partitions backed up with dd:

Boot.img: https://drive.google.com/file/d/0BxzG5iupOOSKaElKbHlweEFPXzQ/view?usp=sharing

Recovery.img: https://drive.google.com/file/d/0BxzG5iupOOSKLWpIOWpRSnc0VVk/view?usp=sharing

Fastboot.img: https://drive.google.com/file/d/0BxzG5iupOOSKUXV1Zll0UmxVczA/view?usp=sharing

if you need any other backup tell me.
[MeMO Pad 7 General] vesko2000:
That's great. Thanks!!! But How should I partition my drive in GParted and flash them?
[MeMO Pad 7 General] daspex:
[MENTION=6013061]Mis012[/MENTION]

thanks for this information,i've tried to boot into dnx mode but no menu comes up to boot into savemode so no chance at all.....i have to send it to asus but i'll wait until the custom rom is ready to go...
[MeMO Pad 7 General] Ruben Craveiro:
load a linux distro and dd the images to the device?

if u need this:

boot -> /dev/block/mmcblk0p4

fastboot -> /dev/block/mmcblk0p6

recovery -> /dev/block/mmcblk0p5
[MeMO Pad 7 General] vesko2000:
I meant how should I partition the drive. When I deleted it it was left empty. Then Windows 10 created it's partition table. So what size and how many should the partitions be? What's the partition table type? Thanks in advance! :)
[MeMO Pad 7 General] social-design-concepts:
whats the issue with updating from kitkat?
[MeMO Pad 7 General] Mis012:
You need to back up whole disk with dd if="dev/block/mmcblk0" of="Removable/(something)/emmc.img" to an external disk connected over otg with 16 gb + (16 gb flash drive is not enough)

For dnx, power off the tablet, andnwhile powering on, hold both volume buttons. When the backlight goes on, release the power button and still hold volume. You should get some 1, 2, 3 message. If you search this thread you can find my zip folder to get to droidboot. Now place kk to lp update package on sdcard and use temporary twrp to start it. Then hope it will work. It may scan for system info so you may need to delete some lines in update script. But some partitions aren't included in the updates, so who knows if it will work.. But everything you try and post results may help us to understand this device. To get faster results, try to search internet before posting here (but still post what you found even if it works) AND good luck. PS I am trying to dual boot linux live cd - http://unix.stackexchange.com/quest...ind-a-medium-containing-a-live-file-system,so if you found out something while trying to boot other systems, please let me know.

---------- Post added at 07:28 PM ---------- Previous post was at 07:22 PM ----------

Ot doesn't flash UEFI and stuck at bootloader splash until kitkat update is flashed with twrp, then it works even with new partition table.
[MeMO Pad 7 General] daspex:
[MENTION=4821597]social-design-concepts[/MENTION]

that's the point if i flash any ll version there is no issue it say's system update complete and bootloops no device version conflict and the bootloader is still .201 version after the update is installed

---------- Post added at 20:48 ---------- Previous post was at 20:44 ----------

.i have already tried to flash it with twrp,same thing...
[MeMO Pad 7 General] thebulletfromhell:
Open up the kitkat to LP update file and have a look at the partition.tbl file. It has the partition offset down to the bytes so you can repartition with gdisk
[MeMO Pad 7 General] Ruwin:
The best way is to flash a dd of the complete mmc. This would also include the partition table. You shouldn't have to partition the memory by hand. I will try to reset my tablet and make a dd but I can try this only tomorrow, when I have my USB hub back from a friend. If I'll have it...
[MeMO Pad 7 General] social-design-concepts:
Do the fastboot commands for partitioning not work on this device?
[MeMO Pad 7 General] jerbear294:
Isn't that what the temporary CWM uses?

The post says it uses an alternate oem stop_partitioning
[MeMO Pad 7 General] social-design-concepts:
derp. . . hand to face.

repartition using fastboot commands :

# start partitioning utility
fastboot oem start_partitioning

# droidboot stashes a copy of the partition table here
fastboot oem partition /system/etc/partition.tbl

# some devices this will generate error msgs / some device need to use oem format
fastboot oem erase cache
fastboot oem erase system
fastboot oem erase config
fastboot oem erase logs
fastboot oem erase misc
fastboot oem erase data

# stop partitioning utility
fastboot oem stop_partitioning

there are actually a few commands used to trigger the temp recovery session.
[MeMO Pad 7 General] DudeyGeezer:
What launcher do you guys "choose" to use?

I'm sat here thinking ZenUI isnt half bad but i see most people hate it?
[MeMO Pad 7 General] sidane12:
There is a way to fix black screen? I tried to flash .33 through TWRP, and nothing. Also I can't mount /factory for unknown reasons
[MeMO Pad 7 General] jerbear294:
The reasons I hate ZenUI-

It can't manage memory at all. It's worse than TouchWiz. This is why applications slow to a crawl and freeze all the time. There's not enough RAM for it to work with.

It comes about as bloated, if not more bloated than TouchWiz.

Every update has had an issue. It feels like a nightly ROM, not a stable one.

As for the launcher, I use Google Now Launcher coupled with Xposed GEL Settings, then use the Glim icon pack on top of it.
[MeMO Pad 7 General] Ruben Craveiro:
do you experience any lag with xposed? or delay? ive installed xposed on the me173x and me176cx but it allways seems to make device slower (just by installing the framework)
[MeMO Pad 7 General] kitsunezero:
Help with this, i have the same problem :crying:
[MeMO Pad 7 General] DudeyGeezer:
and running all that instead of zenui is less laggier?

I've just put xposed on but have not installed any modules yet, any other recommendations from the massive module list?

(thanks for the input by the way, really appreciate it)
[MeMO Pad 7 General] jerbear294:
I only use some modules I see as essential- Xposed GEL Settings, GravityBox, YouTube AdAway and Xprivacy.
[MeMO Pad 7 General] daspex:
i use go launcher with xposed installed and the modules are xprivacy,phab7,android theme engine and hktheme manager,preference injector,icon set is win7
[MeMO Pad 7 General] social-design-concepts:
UGH!!! The fan in my PSU on my build box died last night can't build anything until Saturday now. :(
[MeMO Pad 7 General] jerbear294:
That's annoying.

I'd send you the extra power supply I have lying around but it's a crappy Logisys, and those PSU's are notorious for blowing out and frying components. I haven't even used it, for that reason- I'll stick with my EVGA.
[MeMO Pad 7 General] social-design-concepts:
I just cant make it to Micro Center until Saturday morning. I'm not paying $20 more to get it from bestbuy today.
[MeMO Pad 7 General] Mis012:
Hello everyone! Any progress? I've managed to boot something with grub2 - unpacked droidboot. Now we only need a grub2 module to unpack it from partition, and make the timer persistent so you can select boot option. Still works quiet well though.
[MeMO Pad 7 General] dennissingh99:
Hi guys I'm new to this thread but I thought you may be able to help me with this problem. I have a hudl2 which I would like to root but I can't. I've tried all of the software root methods out for android 5.1 suck as kingsroot but none of them worked. Whenever I try to flash anything with the fastboot/droidboot I get an error saying that I don't have any permission. I also can't use the OEM bootloader unlock command as that gets to the same error. There is nothing in the developer options either which would allow me to unlock the fastboot. Please could you guys help me with this.
[MeMO Pad 7 General] social-design-concepts:
I never understood why no one built a module for grub2 for handling android boot images yet.

Timer? With gummiboot I'm using long key press events vol up / vol down for navigation, long press vol down for enter and long press vol up for esc
[MeMO Pad 7 General] NahuelMS:
Question!

I really not an expert in this programming think you are doing. I just want to have an idea how long we have to wait for a room/kernell for this tablet for dummies because stock work like chinese cheap ****. Battery sucks, freeze, restart, 0 ram managing, mi father samsung with 256mb and ****_ui works better. b

Bougth a gpad for a friend with same battery and with lg bloatware and sp 400 and it ****ing beat 176cx in all aspects exept screen quality. He is getting 8 hours SOT of mixed usage an idlee tablet for days. With this asusmemocrap if i can get more than 3 hours Sot with low britgh i am lucky and it drain battery in sleep like no other device. Even can't sell it on internet because it freezes and restart... For me this tablet was the worst purchase! It work good with KK for 3 months (Sot alway suck but i was able to get 4hs 30 min). After that time they ruined it with they monkey software "ingeniers".

For peole thinking that this tablet has good hardware, i think this intel processors eats battery like hell and Sp 400 beats them for me (based on KK usage). Anyways i will love to see how this intel processor works with a custom rom/kernell properly optimicided. Why Asus didn't unlock the bootloader? For me it's like a trap, don't even think in buy asus **** again, don't even a mouse or a sdcard or a toilet paper on discount.

Thanks a lot for your work, like me there is a lot of people around the world with this memocrap thats enter this forum to see if there is any update.
[MeMO Pad 7 General] Beaver_XT:
Guys! Problem! It's .33 update, root and freeze some system apps.

I don't know which apps or services I froze that make iGO app not receiving GPS signal. I haven't tried Gmaps yet but presumably it's the same.

Do you have any idea about which system (or maybe not) apps might operate GPS?

update:

gmaps seems to be working. now i want to try another offline gps (sat-nav) app but i don't know anything except igo. if anyone got other favorite app, may be the one you're using please let me know.
[MeMO Pad 7 General] Mis012:
This tablet is AMAZING and without lollipop update we wouldn't have UEFI. As now we have it, noone really cares if ASUS will give us bootloader unlock as we don't need it. We can make our own or just use grub2. Any your problems are becouse of the ZenUI and I even don't have some of them. What really helped me was using their tool to deny apps from autostarting, and turning synchronization off also helped. Now I can get two school days with moderate using.