yashsingh1/xdaforums huggingface dataset:
[MeMO Pad 7 General] lambdadroid:
Alright, the new files look fine. I need a while to fix the configs, and I'll be away for an hour or so I'll send you a potentially fixed partition in a few hours.

You may want to edit your two previous posts and remove the attachments because the partition can potentially contain sensible data (the serial number of the device, mac addresses etc) that may be abused. I've downloaded them so you can safely remove them now.
[MeMO Pad 7 General] pojeck:
Hi

Thank you very much for your kindly notice :)

I deleted last img files and some pictures.

I'll wait for fixed files, Thanks again.
[MeMO Pad 7 General] lambdadroid:
I've sent you a PM with a link to a potentially fixed version. Please reply here for reference (maybe someone else has a similar problem and finds this helpful).

You need to download it, unpack it and copy the new file on your external SD card. Then start TWRP again and type the following command carefully (you don't want to overwrite any other partition than the broken one):

dd if=/external_sd/oemcfg.img of=/dev/block/by-name/config

Reboot into TWRP again (Reboot -> Recovery). If it was successful "Config" should be already ticked in the Mount menu.

If that worked, do a factory reset and try booting normally again. Just make sure you don't let it running for an hour this time. :)
[MeMO Pad 7 General] pojeck:
Dear lambdadroid :)

I'll not say anythink :)

I'll just sharing some photos :P

You are the best.

Thank you very very very very much.

Now I'll test new OS.
[MeMO Pad 7 General] lambdadroid:
Awesome. The Nougat ROM works pretty well, but currently there are two problems with it:

Tablet suspend doesn't work properly yet, so keeping the tablet on the whole day won't work. I usually use my tablet only from time to time to watch a YouTube video and keep it powered off otherwise and the ROM works well for that.

The tablet seems to heat up quite quickly with graphic-intensive games, which causes temporary sound issues because it will throttle the device performance to absolute minimum.

If these two things are a problem for you or if you love the ASUS UI for some reason (is that even possible? It's horrible in my opinion), you can probably switch back to the original system now that the partition is fixed. Let me know and I'll post the instructions here.
[MeMO Pad 7 General] pojeck:
Hi Again

I used the lineageOs in my s3mini phone, it's drained and killed my battery :) I get new one :)

This tablet is for my son and my doughter, they are playing hill climb racing and some other games.

For me it's not problem but for them it's huge problem i think :)

I really dont like asus UI, they have lots of program and etc.

in my opinion KitKat is better for this tablet, better and faster than Lolipop.

Which one is good for my kids?

PS: Camera error: Can not connect to camera.
[MeMO Pad 7 General] lambdadroid:
Camera is not supported on my ROM. If you need it, you definitely need to switch back to the ASUS system.

It's hard to tell what's best. The ROM would be probably fine for simple games like hill climb racing. If you like KitKat, there is a guide somewhere here on XDA to restore it. I've never done it though, so I can't say how well that is working. Otherwise there is of course also Lollipop again, with all its bloat etc.
[MeMO Pad 7 General] pojeck:
I'll try this rom for a while. 'll observer batery status. I think i can install GAPPS right?

If i need the lolipop again how can i install the original rom?

Can i install with same steps. Any other special thinks? (TWRP Recovery Mode and Install ZIP)

Thanks alot.
[MeMO Pad 7 General] lambdadroid:
Yes, you can install Google Apps using http://opengapps.org/. You need x86, Android 7.1 and then choose one of the packages. I usually use Pico and then install all applications I need from the Play Store but it's up to you of course. To flash you just need to boot into TWRP again, flash the opengapps package additionally and do a factory reset again.

I'm not sure if you can install the ASUS system with the new version of TWRP (haven't tested), but you can flash UL-K013-WW-12.10.1.36-user.zip using the temporary recovery session like before. To enter droidboot, press Volume Down + Power but then select Volume Up instead of Volume Down.
[MeMO Pad 7 General] pojeck:
Thanks for all lambdadroid.

I2m a little familiar for lineage :) Just batery status is boring. But i'll test for a while.

If i dont like (or my kids dont like) I'll change the system to lolipop :(

I really appreciate to you. Now my tablet is not brick :)

Regards.
[MeMO Pad 7 General] pojeck:
I added some comments to here

https://xdaforums.com/memo-pad-7/or...s-14-1-asus-memo-t3633341/page16#post73711336

Thanks for all.
[MeMO Pad 7 General] martyfender:
[MENTION=8529099]pojeck[/MENTION]

I am the creator of a thread for rooting a Nextbook Ares 8A, Intel x86, Android 6.0.1, Intel Atom x5-z8350 Cherry Trail.

There are many build version of this tablet with different IFWI versions.

They all appear, though to have the same kernel version and hardware.

I have put the newer tablets versions roms on the older version with a TWRP backup, but have not found a way to dump the IFWI from the newer tablet and flash it to the older tablet. I have V1.1.1, V1.2.0, V2.1.5 and V3.0.4 tablet versions.

IFWI versions range from M882_JJ.018 to MM882_JJ.023_JJ.

Do you know of a way to pull the IFWI and flash it to the older tablet.

The older tablet has some issues which I may be able to fix with a IFWI bios update. I am willing to risk bricking that one older device if there is a way to do it.

Under:

/dev/block/platform/pci0000:00/80860F14:00/by-name I see:

android_boot mmcblk0p3 30MB

android_bootloader mmcblk0p1 60MB

android_bootloader2 mmcblk0p2 60MB

android_cache mmcblk0p8 600MB

android_config mmcblk0p11 8MB

android_data mmcblk0p9 10.6GB

android_metadata mmcblk0p6 16MB

android_misc mmcblk0p5 1MB

android_persistent mmcblk0p10 1MB

android_recovery mmcblk0p4 30MB

android_system mmcblk0p7 3GB

I have successfully pulled the partitions using dd.

I believe I successfully flashed the newer tablets 2 bootloader partitions using fastboot, but not sure if I used the proper fastboot flash command, though.

Is the IFWI actually flashed to an Intel chipset instead of MMC?

In addition, in Diskinfo Pro, I see three additional partitions:

mmcblk0rpmb 512KB

mmcblk0boot1 4MB

mmcblk0boot1 4MB

I'm not sure about what these are other than the obvious, "boot"

or how to pull them.

If you have any info about this or know a better place on xda to ask this question, it would be appreciated, as I am lost otherwise.

Thank You
[MeMO Pad 7 General] lambdadroid:
Intels official tool to flash the IFWI/BIOS/whatever is the Intel platform flash tool: https://01.org/android-ia/downloads/intel-platform-flash-tool-lite

However, I don't think it will allow pulling it from another device.

You can read/write to all partitions using dd, so you can try reading mmcblk0boot1 and then look at the result with an hex editor. If it looks mostly like what you're looking for you can flash it the same way on the other tablet.

I'd be extremely careful with this, though. You can mess up your tablet more than easily by messing with the BIOS.
[MeMO Pad 7 General] martyfender:
[MENTION=6833678]lambdadroid[/MENTION]

Thank You, that confirms what I suspected, that mmcblk0boot1 and mmcblk0, are the two bios partitions. I can only see them in diskinfo app. They don't show up in a root file explorer because, (I'm guessing), that they aren't currently mounted. I found info on the net to back up the other partitions at: /dev/block/platform/pci0000:00/80860F14:00/by-name. Do you know how to determine the dd command to backup the 2 bios boot partitions mentioned?

If I am able to successfully back up those two can they be flashed to the other tablet in fastboot/bootloader mode? If so what would the command be?

fastboot flash ? mmcblk0boot1.img ?

Yes, I realize I could mess it up but it is the oldest version of 4 of these tablets I own so I don't really have much to loose. That tablet is V1.1.1. I also have V1.2.0, V2.1.5 and V3.0.4. Those two newer tablets appear to have most, if not all of the bugs fixed from previous versions and my guess is that many of those fixes were actually done, more so in the IFWI bios than the rom itself, based partitially on the fact that flashing the newer rom alone onto an older tablet version does not solve all of the problems.

In the case of my SD card reader problem, though, it could really be a failed, intermittent, hardware problem. Hence, my willingness to take a risk with it.

Thanks again
[MeMO Pad 7 General] lambdadroid:
On my tablet those partitions are at /dev/block/mmcblk0boot0 and /dev/block/mmcblk0boot1. With a root terminal, you should be able to dump them like. Make sure you don't confuse if and of, otherwise you will write to the partitions:

dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0.img

... will write the contents of mmcblk0boot0 to /sdcard/boot0.img. Writing works the same way, just the other way around.

I'm not sure if you can actually read/write from these partitions from Android/Fastboot. Normally, BIOS updates were either made in DNX mode or using a specifically prepared BIOS update file that was put somewhere where the BIOS implementation picks it up and installs it. It would be much easier if you had a flashable firmware ZIP from your vendor. For my tablet these are available and include the BIOS updates (which are flashed automatically when installing the ZIP).
[MeMO Pad 7 General] martyfender:
[MENTION=6833678]lambdadroid[/MENTION] Yes, that is probably true. This tablet does have DNX mode which I know nothing about and couldn't find much info about in previous searches, months ago.

So do you think I will be able to read/write to these boot partitions in the terminal with dd, or can they be locked, also?

I could risk bricking, but I would have to think about it, as the device is functional in every way with the exception of an intermittent, external SD card problem. It could be a controller failure of some type.

using TWRP, I reflashed the original V1.1.1 backup I had and with the original, the external will not even show up through multiple removal and insertions.

I have tried other cards also and checked them for integrity on both Linux and Windows.

I use Apps2sd which, in Android 6 and beyond creates two, guid (GPT) partitions on the cards, the first, fat32 and the second ext2, ext3, or ext4.

Also, standard, MBR formatted, fat32 cards are not showing up, also on this older rom. The external SD was showing up intermittently on V3.0.4 rom, but only bluetooth sound works on V3.0.4 and not the external speakers or headphones.

Hence my thought that it could be bios related. There could be different hardware revisions on the newer tablet to explain that though.

The only two apps I have used to see hardware is AIDA64 and CPUz.

Thanks for your help.

I just checked in Total Commander and mmcblk0boot0 and mmcblk0boot1 does show up at /dev/block/ instead of under /dev/block/platform/pci0000:00/80860F14:00/by-name, where I was seeing the other partitions. Permisssions show root as owner, read and write (600). Mixplorer shows brw____
[MeMO Pad 7 General] lambdadroid:
I never tried so I don't know if those are readable/writable. You will need to test it and hope for the best :)

You might want to test reading on the broken tablet first so you don't risk breaking the working one. It seems like you will be able to read but not write directly, at least according to https://www.kernel.org/doc/Documentation/mmc/mmc-dev-parts.txt
[MeMO Pad 7 General] Lamacik:
Same problem

hi guys!!so good to see people helping each other here ....

i messed up my tablet..asus me 176cx

İm trying to get it working for two days but nothing happens i followed every step in here since i had the same problem at first

AFU:TESt IFWI bios update fv filesize is somethin cause i couldnt read

now im in recovery team win recovery project but cant wipe factory reset because it says

failed to mount /factory (invalid argument) i could flash the lineage os but it doesnt open it shows some blue linegae thing moving logo what im a supposed to do now? if i cant do factrory reset?this is my first:o post icould use some help here especially from lambdadroid but other guys with knowledge can help too ..sorry my knowledge about tech poor but i have some basic understanding what u guys saying im noob at this :)
[MeMO Pad 7 General] lambdadroid:
That doesn't sound good, but it might be possible to fix it. Do you only get this error for /factory or also for /oemcfg? If you send me a copy of your partitions I can take a look. https://xdaforums.com/showpost.php?p=73685118&postcount=15 explains how you get them from your device. Make sure to type the commands carefully (check before you press enter), or you might make things even worse :)
[MeMO Pad 7 General] Lamacik:
thanky you your interest lamdadroid :) your an awesome guy i love techguys :) but i guess my tablet hardbricked now nothing show ups after power button not even asus logo nor recovery menu.. i guess my journey with me 176cx come to an end :) sorry and btw i didnt do anything related to your suggestions...yesterday was working today not :) and thank you again :good:
[MeMO Pad 7 General] lambdadroid:
To be honest, the tablet is pretty hard to brick entirely. I managed to mess up things several times, but was able to fix all of them. One of the biggest problems can be the battery, one time I managed to drain it pretty much to zero, and first it didn't even manage to boot into the charger screen anymore.

If you want to try to get it working again: Have you tried charging it? Does it turn on the screen backlight when you turn it on and/or plug in the charger? If you press Volume Up and Volume Down while booting, does it display "Fastboot starting..."?
[MeMO Pad 7 General] 9rpp:
my me176c can boot into UEFI just fine but I am unable to boot into DNX, holding vol up + vol down + power doesn't do anything. Any hints? I would really like to bring this tablet back to life for my 6 yo son to use.

One thing though, when in UEFI, goes to the Recovery tab, with the following message

"ROM Image update denied

EFI_NOT_FOUND! ROM Image is not loaded"
[MeMO Pad 7 General] lambdadroid:
What does "Recovery tab" mean? There isn't anything related to "Recovery" in the UEFI setup, maybe you are in the Fastboot mode? Can you make a picture of the screen?
[MeMO Pad 7 General] 9rpp:
Here's a screenshot of my uefi screen.

https://photos.app.goo.gl/Ksf5eVZ3DL2rSuq58
[MeMO Pad 7 General] 9rpp:
stumbled upon this post again. Anyone has any ideas?
[Xperia Z5 Compact Android Development] Phoenix Wright:
Nice work! Just to let you know, I made some final changes to the patch before submitting it to SultanXDA there: https://xdaforums.com/showpost.php?p=64784909&postcount=8403 (I think there was an issue with kernel panics in certain circumstances which was fixed by a msleep(), maybe something else too).
[Xperia Z5 Compact Android Development] nlra:
Thanks! My version of the patch was based off of the final post you made to sollapse's thread, which I'll call your patch #1. I just downloaded the version of the patch you linked to (#2), and diff'd a copy of the Sultan dwc3_otg.c patched with #1 against a copy patched with #2, and this is the only difference I found:

@@ -1048,6 +1044,11 @@
phy->state = OTG_STATE_A_HOST;
/* Wait, as host must be enabled after power */
if (ID_MODE == ID_A) {
acaenabled = 0;
+	/* If B_SESS_VLD went off already, proceed to enable host */
+	if (test_bit(B_SESS_VLD, &dotg->inputs)) {
+	work = 1;
+	break;
+	}
/* Ensure there's no charger before suspending */
msleep(200);
if (!dotg->ext_xceiv->bsv)
pm_runtime_put_sync(phy->dev);
} else {

...and I had actually added a single line to that 'if' block already that set work=1 indiscriminately (which you can see in my patch). (As I recall, more often than not after hitting the A_IDLE case, there would be no additional external event to trigger the workqueue again after state was set to A_HOST, which meant that OTG_STATE_A_HOST case block would never actually get executed.) It probably would be more correct for me to test for BSV before forcing another workqueue loop, so I'll try making that change and re-testing. I haven't experienced any ill effects in day-to-day use, though.

Is there a reason why you are checking BSV state twice and in two different ways here (checking the B_SESS_VLD bit in dotg.inputs, and also directly checking dotg.ext_xceiv.bsv)? Are you checking dotg.ext_xceiv.bsv directly because there is a chance that dwc3_ext_event_notify() hasn't been called by the transceiver driver yet for some reason to update the state machine inputs? What about simplifying things here down to a single test, like so?:

phy->state = OTG_STATE_A_HOST;
/* Wait, as host must be enabled after power */
if (ID_MODE == ID_A) {
acaenabled = 0;
/* If B_SESS_VLD went off already, proceed to enable host */
if (test_bit(B_SESS_VLD, &dotg->inputs)) {
work = 1;
break;
} else {
/* Ensure there's no charger before suspending */
msleep(200);
pm_runtime_put_sync(phy->dev);
}
} else {

(or substitute in "if (dotg->ext_xceiv->bsv)" for the call to test_bit() if you think that is more appropriate for some reason?)

Thanks again,

-- Nathan
[Xperia Z5 Compact Android Development] Phoenix Wright:
A lot of time has passed, but if I'm not mistaken, on the OPO, in some circumstances (II think if you removed the otg-y cable quickly or something like that), dwc3_ext_event_notify() would be called (to signal that power was removed) after the device was suspended leading to a kernel panic (I did a lot of tests with the "extreme" cases, like removing the cables quickly). So the msleep is to make sure that it didn't happen (in such cases, the device is then suspended by the next invocation of that state machine if I'm not mistaken, in the "case OTG_STATE_A_HOST:", in the part below the "/* Charger has been removed */" comment). So the changes you proposed wouldn't work, as the msleep + direct check are there to tell if the state machine is going to be called again just after that.
[Xperia Z5 Compact Android Development] nlra:
Gotcha, thanks; makes perfect sense. I'm not sure that the same thing is necessarily happening on the Z5...it uses a different battery charge controller than the 1+1 and in fact I ripped out a lot of the 1+1-specific workarounds when preparing my version of the patch. (I still need to do more testing, but in fact I'd say there are some instances where BSV is actually not being detected properly on this platform, which could explain my initial findings...there is a debugfs file exposed where you can check current BSV detection state, but even when phone is getting power it almost always shows "0".)

Nevertheless, I ran some tests:

1. With work=1 set explicitly every time (my addition to your code for my original version of the path), everything with a powered OTG cable and aca_enable=Y worked fine for me.

2. With that removed, it almost never engaged the battery charger, though host mode almost always kicked in.

3. After adding work=1 only if B_SESS_VLD bit was set, working functionality for powered OTG cables was restored (again, as long as my new prop_chg_aca_enable=N).

So I have updated the patch to check for that bit before forcing another workqueue loop, which I believe is "more correct".

Thanks again,

-- Nathan
[Xperia Z5 Compact Android Development] tarsonis666:
Hm sorry I gonna sound like a total noob but everyone starts out somewhere. The *.diff file is for a ROM to be compiled? Its not supposed to be flashed with TWRP or such? Or is it just a file to be overwritten in the system files?

Just today I made myself an OTG cable with charging function and was scratching my head why it's not charging.
[Xperia Z5 Compact Android Development] DevelLevel:
You are correct, this file is used to patch the kernel (not the ROM) source and then compile the kernel binaries.

Files you flash in TWRP usually end in ".zip" or ".img".

// DevelLevel
[Xperia Z5 Compact Android Development] Adamell0:
Hey. Has anyone compiled a kernel with this patch applied? I'm a total noob when it comes to Linux and I'm really struggling with compiling a kernel, let alone applying patches to it :( . I would be really grateful if someone could attach a ready kernel image.
[Xperia Z5 Compact Android Development] nlra:
Sorry, haven't hung out around here in a while...

What specific phone model do you have, and what firmware version are you using? If it is something in the Z5 family (regular/Compact/Premium) and otherwise stock Sony firmware, let me know which model and f/w version and I can probably whip something up.

If it's some other phone model, no guarantees. If Z5 with third-party AOSP-based firmware, also no guarantees but more likely than not may be possible.
[Xperia Z5 Compact Android Development] Adamell0:
Thanks for your response. I have Sony Xperia Z5 Compact model E5823 with Android 7.1.1., kernel version is 3.10.84-perf-g99119bc.
[Xperia Z5 Compact Android Development] nlra:
Gotcha; I should be able to help with this, but what I need is the Sony ROM version, not the kernel version. Can I assume that you're running the latest (last) version of 7.1.1 released for the Z5c, 32.4.A.1.54? (At this point I'd be surprised if you were running anything older, but I'm going to be pulling the kernel sources direct from Sony for the firmware version that matches what you're running, which is why I need to be sure. In all likelihood, though, even if you are running slightly older ROM, since you're already on 7.1.1, the odds of a kernel built from the latest sources not working with your ROM are likely slim-to-none.)

And you already have the bootloader unlocked on your Z5c, yes?

EDIT: -g99119bc is what is shown as the suffix on the kernel version from 32.4.A.1.54 in screenshots of "About phone" all over the internet for the Z5 series, so I'm moving forward with this assumption.
[Xperia Z5 Compact Android Development] Adamell0:
I'm running exactly the version you mentioned: 32.4.A.1.54. As far as unlocking bootloader goes it is still on my "to do" list, but for that I assume that the tutorial on Sony website will suffice.