yashsingh1/xdaforums huggingface dataset:
[MeMO Pad 7 Q&A, Help & Troubleshooting] RaiKov:
Fastboot commands:

fastboot oem start_partitioning
fastboot oem partition /system/etc/partition.tbl

View attachment 5153065

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash osloader efilinux
.efi
target didn't report max-download-size
sending 'osloader' (2009 KB)...
OKAY [ 0.104s]
writing 'osloader'...
OKAY [ 0.045s]
finished. total time: 0.153s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot droidboot.img
downloading 'boot.img'...
OKAY [ 0.537s]
booting...
OKAY [ 0.002s]
finished. total time: 0.540s

C:\Program Files (x86)\Minimal ADB and Fastboot>
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem start_partitioning
...
(bootloader) Start partitioning

OKAY [ 0.046s]
finished. total time: 0.048s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem partition /system/e
tc/partition.tbl
...
FAILED (remote: GPT command failed
)
finished. total time: 0.103s

C:\Program Files (x86)\Minimal ADB and Fastboot>
[MeMO Pad 7 Q&A, Help & Troubleshooting] RaiKov:
Patch Micro SD, trying to run OS on it.

View attachment 5153197

View attachment 5153281

View attachment 5153283

View attachment 5153749

View attachment 5154997

View attachment 5154999
[MeMO Pad 7 Q&A, Help & Troubleshooting] RaiKov:
Power Y USB Hub connected. Have access to UEFI settings.

View attachment 5160277

View attachment 5160279

View attachment 5160281

View attachment 5160287
[MeMO Pad 7 Q&A, Help & Troubleshooting] Ruben Craveiro:
If im not wrong its due to bad partition table, you should try to format everything first, before flashing, on after new year I can give more detailed help, I dont have access to the device at the moment.
[MeMO Pad 7 Q&A, Help & Troubleshooting] RaiKov:
Hi, i appreciate if you can help me further. Yes, the main problem is Internal memory is somehow disappeared after i tried to format all memory on WIPE menu in TWRP. Now Tablet went into read-only mode, no access to flash something. Only MicroSD storage is visible on MTP device on Windows PC. It was both visible(Internal storage and MicroSD) before formatting data in TWRP. Looks like all partitions are erased, unable to mount data due to Internal Storage(0 MB) problem. I guess i may need a full memory dump of any of working 176CX 8GB tablet to restore my tablet. Looking forward to your reply. Merry Christmas and happy holidays.

Raiko.
[MeMO Pad 7 Q&A, Help & Troubleshooting] lambdadroid:
The partition table looks pretty good in this screenshot:

Spoiler content hidden.

The sizes seem to mostly match mine (I have the 16 GB variant though).

In general, as long as you can still access the UEFI setup or even boot (temporary?) TWRP your tablet seems in pretty good shape.

I would try flashing e.g. me176c-boot from the "FASTBOOT MODE" (Droidboot) screen (see https://xdaforums.com/t/bootloader-0-3-0-me176c-boot-for-asus-memo-pad-7-me176c-x.3780225/) and then check if it shows the boot menu if you keep "Volume Down" pressed while turning the tablet on.
[MeMO Pad 7 Q&A, Help & Troubleshooting] RaiKov:
Hi, yes i have access to Fastboot mode and then TWRP, but not directly(first i need to flash efilinux from DNX mode Fastboot starting...#1#2#3 https://xdaforums.com/t/unbrick-asus-memopad-7-me176c-cx.2970049/post-72963836) I flashed ESP.img successfully. When i press Volume down button. These options are available:

*Recovery mode

*Restart bootloader

*Normal boot

*Power off

View attachment 5183689

(This is an old image for e.g., there was no error in this session.)

C:\Users\RaiKo\Desktop\asus recovery project\rollback\WW_ME176C_V12.10.1.17-user
debug-201505051557-rawdata>fastboot flash osloader efilinux-userdebug.efi
sending 'osloader' (2023 KB)...
OKAY [ 0.105s]
writing 'osloader'...
OKAY [ 0.007s]
finished. total time: 0.115s

C:\Users\RaiKo\Desktop\asus recovery project\rollback\WW_ME176C_V12.10.1.17-user
debug-201505051557-rawdata>fastboot boot droidboot.img
downloading 'boot.img'...
OKAY [ 0.536s]
booting...
OKAY [ 0.002s]
finished. total time: 0.541s

C:\Users\RaiKo\Desktop\asus recovery project\rollback\WW_ME176C_V12.10.1.17-user
debug-201505051557-rawdata>fastboot flash ESP esp.img
target reported max download size of 536870912 bytes
sending 'ESP' (33792 KB)...
OKAY [ 1.169s]
writing 'ESP'...
OKAY [ 0.616s]
finished. total time: 1.788s

C:\Users\RaiKo\Desktop\asus recovery project\rollback\WW_ME176C_V12.10.1.17-user
debug-201505051557-rawdata>

When i select boot or recovery it directly goes into UEFI bios screen. Is there any solution to format or recover Internal Storage(0 Mb) of the tablet?
[MeMO Pad 7 Q&A, Help & Troubleshooting] lambdadroid:
That does not sound like it really flashed it successfully. If you install me176c-boot, the boot menu should look like

View attachment 5185301

It does kind of sound like your eMMC has magically become read-only, although I don't know how this is possible.
[MeMO Pad 7 Q&A, Help & Troubleshooting] RaiKov:
Exactly yes! This read-only memory mode what i'm facing now. As i said above, i didn't change too many things. When i was trying to solve "unable to mount" error, once i tried to format internal memory on TWRP wipe menu. I saw this advice in main topic, it was explaining in guide how to solve Internal Memory(0 Mb) problem with TWRP formatting, wipe, repairing partitions, change type of format from ext4 to ext2 and rechange it to ext4 etc. I'm very sure Internal memory was visible both TWRP and MTP device on Windows PC before formatting.

Maybe i need to give permissions or enter password(seen it in many Youtube tutorials for Asus Phone) to unlock Internal Memory, but i don't know how to solve this problem without running Android.

Do you have any suggestion to me, what i supposed to do?
[MeMO Pad 7 Q&A, Help & Troubleshooting] lambdadroid:
It's a very strange problem and to be honest I don't really know what to do either.

I guess in your situation I would put some Linux distribution on a USB flash drive (e.g. Arch Linux), boot it through the UEFI menu (use the "Boot Override" option). And then try to investigate from there using some proper Linux command line tools or by looking at the kernel log. But I can't give you exact steps because I don't know how the eMMC could magically become read-only or how to get it out of this mode.
[MeMO Pad 7 Q&A, Help & Troubleshooting] RaiKov:
Thanks for the answer. Not sure we are talking about similar things. I downloaded gparted live on Linux OS.(My dev specialist friend had advised me). Created a bootable disk by rufus, but if i knew it i could tell you the result. :(

View attachment 5185957

And then do you know any person in the forum who can help me in this case? i believe this eMMC issue is weird, but not magical imho, it must have happened and affected to more users.
[MeMO Pad 7 Q&A, Help & Troubleshooting] lambdadroid:
So, did you find anything interesting?

I don't really know any other person who has worked on this device in the last few years so I'm afraid I don't know anyone either.
[MeMO Pad 7 Q&A, Help & Troubleshooting] RaiKov:
No, actually i haven't tried it yet. Because i dunno how to recognise it.(not familiar with Linux) Another reason i know this is one of the last thing i can try to bring the tablet back life. 😕 I was searching other possible solutions before this step.

What do you think about if i got a full memory dump.img.gz(including all 15 partitions) of a working 176CX 8GB tablet? Would that help me in some way?
[MeMO Pad 7 Q&A, Help & Troubleshooting] lambdadroid:
This will probably be helpful at some point, but I would recommend against randomly overwriting all partitions from some memory dump. This might do more harm than good. From what I could tell, your partition table for example seems fine.

You can try booting the following image. This is me176c-boot packaged for USB. It also contains a bootable version of my TWRP build (https://xdaforums.com/t/recovery-20...p-3-3-1-for-asus-memo-pad-7-me176c-x.3745190/).

Flash it to an USB flash drive using Rufus.

Boot it on your tablet. A menu like I showed above should show up.

You can try the other boot options but I added a special "Recovery (USB)" one. This should boot TWRP from the USB flash drive. (Note: use ↓ to switch options, ↑ or Enter to select an option)

When the TWRP splash screen shows up you can disconnect USB.

Post the output of "dmesg" in the terminal emulator here. You can get it via adb shell (tablet connected via USB to your PC) or write to to an external SD card e.g. with "dmesg > /external_sd/dmesg.txt".

Perhaps that (dmesg = kernel log) contains something useful.
[MeMO Pad 7 Q&A, Help & Troubleshooting] RaiKov:
Thank you for taking your time! i will try it asap.
[MeMO Pad 7 Q&A, Help & Troubleshooting] RaiKov:
Here's the result. i hope it will be helpful.

View attachment 5187457

Also, is there a solution to charge the tablet properly? After the battery capacity goes under 50%(only i can monitor it in TWRP) and then try to connect a power source (AC charger, PC USB cable or USB HUB), Tablet screen is immediately opened in UEFI bios menu by itself. No matter of using power off button. During a cable is connected, tablet goes on again(with release of power off button). Only way i find is opening back cover of tablet and disconnecting power supply terminal of battery for a while. Tablet is charging well via AC charger while screen is completely off(No backlight.) i hope you understand it.
[MeMO Pad 7 Q&A, Help & Troubleshooting] lambdadroid:
Hmm. There are lots of I/O errors that shouldn't be there.

[ 8.008459] print_req_error: I/O error, dev mmcblk2, sector 589864
[ 8.008492] Buffer I/O error on dev mmcblk2p9, logical block 0, lost sync page write
[ 8.008641] EXT4-fs (mmcblk2p9): I/O error while writing superblock
[ 8.008692] EXT4-fs (mmcblk2p9): mount failed
[ 8.030538] print_req_error: I/O error, dev mmcblk2, sector 589864
[ 8.030571] Buffer I/O error on dev mmcblk2p9, logical block 0, lost sync page write
[ 8.030868] EXT4-fs (mmcblk2p9): I/O error while writing superblock
[ 8.030919] EXT4-fs (mmcblk2p9): mount failed

This could be caused by this "eMMC has magically become read-only" problem. But I have absolutely no idea how this could happen, it seems almost impossible.

Sadly, another possible explanation for those I/O errors would be that your eMMC is just broken. :(

Can you try flashing me176c-boot to the internal storage from that TWRP build? Download https://github.com/me176c-dev/me176c-boot/releases/download/0.3.0/esp-0.3.0.zip and unpack it to external SD card.

From TWRP terminal do dd if=/external_sd/esp.img of=/dev/block/by-name/ESP (make sure to type it correctly). Before rebooting, copy the dmesg again to see if there are new I/O errors. (You can post it here if you are not sure how to read it...)
[MeMO Pad 7 Q&A, Help & Troubleshooting] RaiKov:
Here's the result after it. Looks like a lot of changes.

Btw On your information, Once your bootable disk is initialized, i've seen some errors or fails to load kernel.
[MeMO Pad 7 Q&A, Help & Troubleshooting] lambdadroid:
And I assume it still doesn't boot into me176c-boot, i.e. it did not successfully write anything?

There are still tons of I/O errors. I'm afraid my only plausible explanation for this is:

I'm not sure if there is any magic you can do if the eMMC doesn't let you write anything anymore. At least I don't have any suggestions. Perhaps someone else here can help you but I wouldn't necessarily count on it. Sorry :(

You could, theoretically, with some work use the tablet through a micro SD card. But unfortunately I'm not aware of a way to make UEFI boot directly from micro SD. So you would always need to connect USB temporarily for booting.
[MeMO Pad 7 Q&A, Help & Troubleshooting] RaiKov:
How do you understand it doesn't boot into me176c-boot? As following your guide, i run unofficial(permanent build) TWRP with selecting USB option on my tablet.

Well, this is a really frustrating situation for me. :mad: it's very hard for me to understand and accept how can a software/firmware error cause to eMMC has fallen into absolute disrepair and cannot be reverted back? My experience and learnings say it could be fixed somehow unless there isn't any damage on IC hardware. What's your thoughts about it?

i tried to run OS through microSD, but it's hard task and UEFI didn't recognise SD card yet. What would you suggest me the least painful way of booting the tablet via USB stick? I mean, can you explain it in more details like cable/setup/hardware configuration, which OS could be useful for 1 GB tablet(android x86, debian etc). I've also been struggling with charging my tablet properly.

And the last thing, i'm thinking of contacting with ASUS global RMA. Maybe they won't help me, I would still ask about the dead eMMC of the tablet. What i supposed to show them like screenshots or files to explain the problem? What should I ask/request them? Thank you.
[MeMO Pad 7 Q&A, Help & Troubleshooting] lambdadroid:
If the dd if=/external_sd/esp.img of=/dev/block/by-name/ESP was successful you would not need to boot via USB anymore, then it should boot to me176c-boot directly (without USB).

I don't know much about the hardware, so this is just my humble opinion based on what I know from the software side. Trust me, I'm at least as confused as you are.

I just cannot imagine any reason why something in software/firmware would purposefully make your eMMC read-only with seemingly no way to recover. And I don't even see any way how this could be done using software. Therefore I can also not imagine any software that would reverse this condition.

I would be very happy if you can prove otherwise. So perhaps there is some magic recovery tool that can fix this. But I cannot point you to it, and it would need to be very low-level (not something like TWRP).

Someone experienced with hardware would probably try to read/write to the eMMC directly using external tools, but this would require some seriously advanced soldering as far as I understand.

Unfortunately I'm not aware of any way to make UEFI boot from the micro SD card. :(

Effort for the software configuration is really the main obstacle here. Theoretically you could configure any OS to treat the micro SD card just like your eMMC. Then you just need something like the USB me176c-boot that I posted to workaround the limitation that UEFI cannot boot from the micro SD.

I could imagine how to set this up using my LineageOS ROM (Android) or postmarketOS (Linux). But especially for Android it would likely require changes in quite some places to make this work properly.

This tablet is really old, sadly I doubt they are still able to help you. And even if they are willing to help you, it would likely be as expensive as a new, much more modern tablet. If you are interested in this tablet specifically, it's likely cheaper to look if someone is selling it used somewhere.
[MeMO Pad 7 Q&A, Help & Troubleshooting] RaiKov:
Thanks for the detailed answer. I'm aware of that tablet is old fashion and it's not good idea to spend a penny for it anymore. I'm keen on my patience and tryings for 2 reasons; one is for it was used by Mom and the other was completely turned into a challenge for me to fix it. Other users were able to recover their tablets easily from UEFI screen, whereas i've faced with difficulties every day harder than before. idk what was wrong with my luck.

I'm still thinking how it'll be ended up or looking for new help might be come. :)
[MeMO Pad 7 Q&A, Help & Troubleshooting] mesutsenol:
Hi I have the same tablet in the same situation. Although I know the tablet is very old,just to improve myself I want to work on it. Did you fix the problem? If so,would you pleaase tell me the steps? Thank you
[OnePlus 8 Pro  Guides, News, & Discussion] p96xl:
I am on the OnePlus 8 Pro with OOS 11. Two apps you need.

SetEdit and FNG (or any other gestures app you want)

Steps:

Go to settings and turn on "Navigation Gestures"

Open SetEdit and find "op_gesture_button_side_enabled" and set that to "0" instead of "1"

Open up FNG and set it up with all the permissions that are needed

Disable "bottom edge" in FNG and only use "left edge" and "right edge" since there is conflict when "bottom edge" is used

Set them up the way you want, and now you can use hamburger menus again!

This should work for any OnePlus, and any version since this tutorial is from the OnePlus 5 and 5t

You can disable the activation of Google assistant by going into Settings > apps and notifications > see all apps > Google > disable
[OnePlus 8 Pro  Guides, News, & Discussion] dlads:
Can't believe no one gave you a thumbs up for this.

Nice one.
[OnePlus 8 Pro  Guides, News, & Discussion] ps000000:
Very nice guide.

Now I can use LMT Launcher with Stock OOS Android11.
[OnePlus 8 Pro  Guides, News, & Discussion] galaxys:
Great guide! Kudos
[OnePlus 8 Pro  Guides, News, & Discussion] ProAm500:
Is there a way to get this to work on AOSP roms?
[OnePlus 8 Pro  Guides, News, & Discussion] smartymcfly:
I never used the gestures from prior versions. What is the difference between the standard android 10-11 gestures and the one you describe?
[OnePlus 8 Pro  Guides, News, & Discussion] p96xl:
The old OnePlus gestures were a simple two button operation, from the middle of the bottom, it was either home or multi task. And the side of the bottom was back. Now the new ones change position when you flip your screen, so when watching a YouTube video, you have to swipe up twice from the bottom. The old ones you just had to swipe towards the camera from the charging port. The new gestures also have a really ****ty back button, the entire edges of the screen are back buttons now, which means no hamburger menus will work anymore. I am very frustrated by this change, so i hacked up a little solution.
[OnePlus 8 Pro  Guides, News, & Discussion] p96xl:
I never used custom roms before, I have no idea if this works or not.
[Touch Diamond, MDA Compact IV General] Unemo:
Hey! Just wanna have a simple app that calculates your distance...?? Anything avalible? Using tom tom 7 now but can´t figure out how to measure your distance travelled...?
[Touch Diamond, MDA Compact IV General] laser21:
Trackme from Louis Espinosa or Tracky, which is more complex.

There is an older version or Trackme, which is in my opinion better for your purpose. See attached file.

:)
[Android Q&A, Help & Troubleshooting] Snayps:
Root working?
[Android Q&A, Help & Troubleshooting] Deleted member 1890170:
Do you mean Inovu A7i?
[Android Q&A, Help & Troubleshooting] Snayps:
Reeder a7i
[Android Q&A, Help & Troubleshooting] Snayps:
https://xdaforums.com/t/tool-kit-mykit_batchv1-1-x.2681783/

not working
[Android Q&A, Help & Troubleshooting] CXZa:
Should work according to this:

Reeder A8i 4.4.2 Kitkat Root // Araçlar // Resimli Anlatım

Sevindim.Bu bence bütün intelli tabletlerde çalışır.

forum.donanimhaber.com

If "adb root" works you can try that package on google drive...

Reeder A8i 4.4.2 Kitkat Root // Araçlar // Resimli Anlatım

Tabletten usb hata ayıklamayı aktif edip pcye bağlayın.Driverlar vs yüklenip tableti tanıdıktan sonra verdiğim rarın içindeki programı rardan çıkarıp çalıştırın. Program açılınca 'Y' harfine basın ve 10-20 saniye arası bekleyin.Tablet kapanıp açılacak ve açıldığında cihaz rootlanmış olacak.

forum.donanimhaber.com
[Android Q&A, Help & Troubleshooting] Snayps:
Not working
[Android Q&A, Help & Troubleshooting] CXZa:
Have you installed both driver packages as said?

Basically a non secure adbd is installed using fastboot and then su using adb.
[OnePlus 8T Questions & Answers] Smallsmx3:
Double post... Please delete
[General Topics] BLL1989:
Hello,

I am searching a program for my raphael or any windows mobile based phone. I have to use it to control the mediaplayer on my notebook. I know sony ericsson has something like that built/in, but I need it for windows mobile.

Thanks!!!
[General Topics] misioooo:
I think it is rather related to your notebook software...

Last time i did this i just paired handheld (some older Nokia iirc) with Bluetooth in PC. Then i installed some software on PC and voila - i could even move mouse pointer using phone.

Start by pairing your WM device with laptop. Then search for some program for notebook to use BT signal to control mouse/imitate key presses. And you are good to go.
[General Topics] Menneisyys:
readmy Multimedia Remote Control Bible in the Wiki
[LG G5 Themes, Apps, and Mods] tremalnaik:
Hi everybody,

while there are already some good ADB debloaters on XDA, this moring was cold and rainy, and I had nothing better to do than writing my own debloater.

I wanted to keep it as simple as possible, so it's a bare batch script for Windows (I hear you Linux geeks praying for my soul's redemption).

View attachment 5150147

The script requires adb installed (and the phone connected to the pc, although this should be quite obvious). Just double click on the script and you will be prompted with the choices for uninstalling different sets of useless software:

Third party bloatware: things that you probably want to remove like a bee from an helmet you're wearing. The list includes the phone carriers promotional softwares, Facebook, Instagram and Evernote

Google heavyweight suite: a whole bunch of software that is either necessary, if you have a Google account, or totally useless in the opposite case. The list includes Duo, Google App, Ok Google, Docs and more.

LG's useless software: I find most of the LG apps useful, so this list is currently empty.

Play Services: if you are really masochist, you can erase from your life Play Services and Play Store too with a single keystroke.

App removal is done using --user 0 parameter, so root is not needed.

Spoiler content hidden.

This specific version of the script targets the LG G5 H850 with the latest (Oreo v30f) OPEN EU rom.

Feel free to edit and repost my script, adapting it to other phones or with other apps to be removed from the same phone.
[LG G5 Themes, Apps, and Mods] yken:
need root?
[LG G5 Themes, Apps, and Mods] tremalnaik:
No, it doesn't, apps removal is done with --user 0 parameter, so the apps are removed only for the current user without needing root premissions.
[General Questions and Answers] PanosT:
I have flashed a new rom on my phone with twrp 3.4.0.0

When I got to the new UI I had no free space (both internal and sdcard)

Back to twrp I took these steps:

1. Boot into TWRP recovery.

2. Select Wipe » Advanced Wipe.

3. Tick/check the Data partition.

4. Select Repair or Change File System button.

5. And lastly select Resize File System button.

that solved the internal storage size, but the storage of sdcard shows 80MB when it should read 128GB.

I tryed the same method for sdcard but it cant be done on sdcard selection.

Is there any solution without formating sdcard?

if not please provide a solution with formating on twrp.

I have searched for a solution but no result...

Please help! i have no time to search right now!
[General Questions and Answers] PanosT:
Problem solved by replacing twrp with pitchblack ver.3 and repeating the procedure mentioned.
[Realme 5 Pro Questions & Answers] Jamensolasco:
Hello guys i really need some help i dont know what to do in my realme 5 pro i try to root my phone using twrp and magisk but somethings happen i think i broke it and when i try to put custom rom using flashing tool that i found in google my phone cannot read the tool and i cant even open custom recovery mode please help me this phone is really important to me its a gift from my mother someone help me View attachment 5150277
[Realme 5 Pro Questions & Answers] jijojamie:
Hi,

Fixed the issue?
[Realme X2 Pro Questions & Answers] rpfe26:
Hello everybody !

I need to understand something !

When i use corvus rom fingerprint works perfectly and when i use the other the fingerprint is really difficult to use. registration works but recognition is really hard !

in the engineer mode my value of finger print test is around 16 !

it's possible to export corvus configuration in the other ?
[Redmi Note 8 Questions & Answers] Antar122:
Please recommend me some of the best redmi note 8 gaming kernels. I am running evolution x5.1 gkingo