yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] ADDICT.ANK:
no u can flash rom and kernel both with cwm..

No issues with that..

Do one thing via rom manager flash the boot.img from cm10.1 zip u extracted earlier.

And turn the signature verification off from cwm advanced tab..

And post

---------- Post added at 12:14 PM ---------- Previous post was at 12:12 PM ----------
[General Questions and Answers] angello2299:
i have done a fresh rom install and it still the same problem
[General Questions and Answers] MCSH:
When you use 'Back up', it'll store the data on internal storage (i.e: on your phone's internal storage, not external (removable) SD card) but when you use Back Up to External SD card, it'll be stored on your removable sd card.

There can be plenty of different reasons for the speed... (which depends on your device, ROM... etc)

I suggest you to back up to your sd, specially if you want to install a new ROM or if you want to play with system files and applications.
[General Questions and Answers] karlkurtis:
Lost icon images

I have recently installed a app but a week later all my icons next to my links have disappeared ( telephone icon next to tel no..etc) any clue why this would happen..had to install all applications again quite annoying
[General Questions and Answers] Peachstateboi:
---------- Post added at 12:25 PM ---------- Previous post was at 12:23 PM ----------

[/COLOR]

CHECK THE LINKS

http://xdaforums.com/showthread.php?t=2130276

http://xdaforums.com/showthread.php?t=1886460[/QUOTE]

I check these links but they do not have my tablets listed just phones
[General Questions and Answers] akins47:
10x. Bt hw wil i turn it off, d device is already S-OFF in boot menu. Besides, i use TWRP. d device is htc droid incredible 2
[General Questions and Answers] Erisii:
Posting issue

I haven't been able to find anything on this issue so far. Then again it might not be an "issue" and just a built in thing. I can't post to the "Windows RT Hacking/Development" section, which is expected because I have less than 10 posts (This is my first, hello all!). I figured I'd try to get my 10 posts by helping people out in the regular "Windows RT" section, answering questions about ARM CPUs and the inevitable threads about "Why doesn't ____ work on Windows RT?", but I can't post there either. Please let me know if I need to do something special to post, and if this is in the wrong spot. Also, if I fail at searching, and there is a topic about this, could someone be so kind as to link it?

Yes, I know I probably look like mega-noob right now. :silly:
[General Questions and Answers] ADDICT.ANK:
Which app u install'd.

A launcher or what?

---------- Post added at 10:27 PM ---------- Previous post was at 10:19 PM ----------

Dont wipe the data yet.

Post the device model and kernel info pls.

Also check the motochopper and easy root.

And does the device have stock recovery?

And dont worry. It'll be done and make a backup pls.
[General Questions and Answers] shifau00:
Yea you need to get 10 posts before you can post in a dev thread.. I'm also working my way up hehe .. u can post in general discussion
[General Questions and Answers] Erisii:
General Discussion

I guess that's really my question. I thought the "Windows RT" section WAS a general discussion. If it is not a general discussion, then why in the world do we have a "Windows RT Development/Hacking" section?

I don't know, I guess it just kinda sucks that I have to post 10 times in the ANDROID Forums so that I can go help out in the WINDOWS sections, but I'm apt enough to contribute to some android stuff, I suppose :P
[General Questions and Answers] ADDICT.ANK:
increase to 10 posts..

so post in off topic and increase the posts.
[General Questions and Answers] nbaqir:
LG LU6200 went dead after flashing wrong ROM

Hello everybody,

i erroneously flashed wrong ROM [of Vega Racer II SKY IM-A830/A840L/S/K)/IM-a800-- (viethoajb830lmadetungkick777)] on my LG LU6200, it installed in about 40 seconds (may be just boot file) and completed then i rebooted the phone but it never turned on nor it is detectable on PC via USB cable, completeeeeeely dead.

pl see if anybody can advise on it
[General Questions and Answers] tom353:
I tried erasing the userdata partition, and indeed it seems to be where the issue comes from.

Basically, after trying all combinations, my device boots (to a fresh state) when userdata is erased, with either my set of partitions or the set I got from the stock ROM. And when I restore userdata, the device goes back to a boot loop with either set of partitions.

So I guess I don't need to fix the ROM, I need to fix my userdata partition.

Any idea what type of problem could have occurred on that partition that stops the device from booting? Maybe if there's no space left (are there no safeguards from this situation in Android?)

I understand this partition is encrypted, but file-based. Does that mean the filesystem itself is not encrypted and there is a way to mount it on a PC and, for example, delete a few files, selected based on their size or their modification date, or even selected randomly if the metadata is encrypted as well?
[General Questions and Answers] tom353:
Yes, the bootloader is locked, and mtkclient can't unlock it (I tried).

I would try to boot to it without flashing, but apparently there isn't yet a TWRP image available for my device model (Moto E7).

But I like the suggestion! I understand that TWRP has a file manager, so I could potentially recover files or free up space in userdata if I could boot it.
[General Questions and Answers] DiamondJohn:
As for not having a TWRP, just for comparison, I have a Google Pixel 4a (ie what I would of thought would be a pretty main stream phone), and we still do not have a fully functioning TWRP. However, it is a great utility to fix some things that cant be fixed in the running OS. Just not all the old features I have become accustomed to having, and hence, I dont flash it, just run it as boot. It would be interesting to know if one could run TWRP (possibly crippled) without flashing it, on a locked bootloader?
[General Questions and Answers] SubwayChamp:
I don't think so, erasing the userdata partition can fix some bootloop issues, instead. The files within the userdata are recreated on the first boot, at least, with the minimum set of them.

The userdata partition doesn´t need any fix.

From my previous post:

"- If your model allowed (allows) being unlockable, then you can consider by unlocking it, a locked device doesn't admit some modifications, so maybe your device doesn't allow restoring some partitions this way."

This is the issue now, the userdata partition itself, doesn't have any issue, but a locked bootloader doesn't allow booting a device that was, in some way, modified. Check if your device can be unlocked officially, then try to restore this piece.

In the meantime, you can try to mount the image in some Linux distro, or unpacking it with some tool, and extracting what you need, part of that back up can be restored through some apps from the Play Store, you should install some of them, then take a look at the extension, they use for backing up, and compare with your back-up, This will be possible, only once you can open/unpack/extract it.

As per the mtk client, did you try to unlock it, also erasing the partition they recommend? And which size took your userdata backed up?

Remember that you have to target to the A or B slot, using nameofpartition_a, or _b. It´s probable too, that the OTA update was directed to the B partition, assuming that this was the first update you received, usually, devices start with the A partition running.
[General Questions and Answers] Renate:
I think that you're misreading what Tom is saying?

He's saying erasing userdata makes it functional, therefore the backedup userdata is the problem and needs fixing.

The biggest thing is getting ADB working. Sometimes you can hack the boot image to make that possible.

Then you can fix the broken details in the userdata.
[General Questions and Answers] Droidriven:
As far as I know, fastboot booting TWRP(booting temporary recovery session) doesn't require an unlocked bootloader. I've used TWRP on locked bootloader devices in order to root them.
[General Questions and Answers] Droidriven:
I think you may be right about the backup being the issue.

They might be able to follow your suggestion about hacking the boot.img, provided that the bootloader is unlocked/unlockable or if they can manage to gain temp root via ADB, if the necessary partition is accessible via temp root.

Or, if they can figure out what data is corrupted in the backup and just remove that data then restore the edited backup. Maybe.
[General Questions and Answers] Droidriven:
When you backed up your data, what partitions/data were included in the backup?

Can you extract the data from the backup? If so, you can, by trial and error, create a copy of the unextracted backup then extract the copy. Remove one of the backed up partitions, such as system/data or data/data, etc.. Save the edited backup with the partition or folder removed then try restoring it on the device, if it doesn't work, reset the device then repeat the process of creating a copy of the original backup and removing a portion of data from the backup then restoring it with that part of the data removed, rinse, repeat.
[General Questions and Answers] Kabir498:
I have a pixel 3 with a fairly small battery capacity of about 2900mah, and I want to try adding a new battery with a larger capacity (8000mah) I want to know how to change the settings in the sys/class/power_supply/bms/charge_full section so that it can be increased from 2900mah to 8000mah so that when charging the 8000mah battery capacity can be fully charged. or will even if I don't change the charge_full setting the battery will still be fully charged?
[General Questions and Answers] tom353:
I tried, but no luck on my Moto E7 with a locked bootloader. This device has 2 options to run fastboot and they tend to behave differently in terms of permitted operations, and error messages. This in itself is weird, but anyway, I tried both with a TWRP image for a relatively similar device:

$ ./fastboot boot twrp-3.5.2_10-0-ginna.img

Sending 'boot.img' (26560 KB) OKAY [ 0.692s]

Booting FAILED (remote: 'unknown command')

fastboot: error: Command failed

$

$ ./fastboot boot twrp-3.5.2_10-0-ginna.img

Sending 'boot.img' (26560 KB) FAILED (remote: 'Download is not allowed on locked devices')

fastboot: error: Command failed

$
[General Questions and Answers] Droidriven:
Adding incompatible hardware and getting that hardware functioning like you want would require compiling/building a custom kernel with support for the new hardware built into the new kernel.
[General Questions and Answers] Renate:
I edited the quote to change kernel to kernel module.

Ok, that's still a bit of an undertaking building mymodule.ko

I've never sorted out how to build a kernel module using just kallsyms.

Also, if you want to add something USB, I²C, GPIO or UART you could do it just adding user code.
[General Questions and Answers] tom353:
Thanks for the suggestion!

I haven't tried to get ADB working, but I managed to mount the userdata.img I had extracted with mtk client on my laptop.

I can see the file system structure, only the names and contents are encrypted. I will try removing part of it and flashing it to see if I can get the phone to boot. I'll also try copying part of the data to a fresh userdata.img recreated by my device, to see if the partition remains valid and if the phone will decrypt the copied content.

If that fails, I'll see if I have any luck with ADB.
[General Questions and Answers] tom353:
That second option is my hope at the moment. I'm lucky that's it's Android 10, and metadata encryption is only mandatory from Android 11, so the img I retrieved is only file based encrypted. I hope this means I can modify it by trial and error and maybe remove the problem this way (assuming the problem is indeed from this file system).
[General Questions and Answers] tom353:
Thanks for the detailed answer! Sorry if my post wasn't clear.

That's what I meant, erasing it did fix the bootloop, so I suppose something in that partition was causing it, and hopefully I can find a way to fix it without losing data.

My backup is from mtk client. I can mount it, no proprietary format or apps needed, but its content are encrypted and can only be read by the device. What I'll try to do next is to remove parts of the encrypted files and see if I can get the device to boot with the resulting userdata partition.

No, i skipped the erase step. The unlock command said it was done, but it wasn't. But i can read and write partitions with my locked bootloader, so for the moment I'm focusing on this, and I gave up trying to unlock for now. I don't want to unlock officially, as I understand this would reset the encryption keys, and there would be no hope to restore my data.

It wasn't the first OTA update, but the active slot was A. I switched slots with fastboot, but was still getting a boot loop, and the device switched back to slot A during the boot loop.
[General Questions and Answers] tom353:
Many thanks @SubwayChamp , @Droidriven , @Renate , @DiamondJohn ! With your comments and guidance, I feel I made some progress today.

I could mount userdata.bin extracted with mtk client on linux. It's an F2FS image, files are encrypted, name included, but the structure (with dates and sizes) isn't (it would if it was Android 11 or above).

As a bonus, top level directory names are not encrypted.

I could rule out a 'disk full" issue, df reports 90%.

I did a fsck.f2fs and almost everything seems normal, except maybe:

Info: checkpoint state = 44 : crc compacted_summary sudden-power-off

However when i did du -sh * , I got around 100 errors, all of them in the /data/ directory, all of this type:

du: cannot access '/phone/data/R3o2MwAAAAAIoyi1oUQx-q1M6CbyyFzjx0x1vg/jYwuXQAAAADFeCpgtX0Mm3fpQaZew24b': Invalid argument

At the same time, dmesg was reporting this type of errors:

[199881.286386] fscrypt (loop8, inode 34534): Unsupported encryption modes (contents 127, filenames 4)

[199881.286452] fscrypt (loop8, inode 34534): Unsupported encryption modes (contents 127, filenames 4)

[199881.286522] fscrypt (loop8, inode 34534): Unsupported encryption modes (contents 127, filenames 4)

[199881.286592] fscrypt (loop8, inode 34534): Unsupported encryption modes (contents 127, filenames 4)

[199881.286658] fscrypt (loop8, inode 34534): Unsupported encryption modes (contents 127, filenames 4)

[199881.286738] fscrypt (loop8, inode 34534): Unsupported encryption modes (contents 127, filenames 4)

[199884.719497] fscrypt_msg: 13548 callbacks suppressed

[199884.719508] fscrypt (loop8, inode 15553): Unsupported encryption modes (contents 127, filenames 4)

[199884.719841] fscrypt (loop8, inode 15553): Unsupported encryption modes (contents 127, filenames 4)

[199884.727157] fscrypt (loop8, inode 15553): Unsupported encryption modes (contents 127, filenames 4)

[199884.727384] fscrypt (loop8, inode 15553): Unsupported encryption modes (contents 127, filenames 4)

[199884.727658] fscrypt (loop8, inode 15553): Unsupported encryption modes (contents 127, filenames 4)

[199884.727736] fscrypt (loop8, inode 15553): Unsupported encryption modes (contents 127, filenames 4)

[199884.727822] fscrypt (loop8, inode 15553): Unsupported encryption modes (contents 127, filenames 4)

[199884.727890] fscrypt (loop8, inode 15553): Unsupported encryption modes (contents 127, filenames 4)

[199884.728083] fscrypt (loop8, inode 15553): Unsupported encryption modes (contents 127, filenames 4)

[199884.729384] fscrypt (loop8, inode 15553): Unsupported encryption modes (contents 127, filenames 4)

[199889.729296] fscrypt_msg: 1238 callbacks suppressed

[199889.729306] fscrypt (loop8, inode 15553): Unsupported encryption modes (contents 127, filenames 4)

I will try a few more things tonight (see if my device accepts partitions that I modified on linux), but I'm running out of time to do much more just now, as I'll be travelling for the next couple of weeks, so I'll get back to it when I'm back!
[General Questions and Answers] Ducky187u:
I need help .dont know hiw i did this but i do know it can be fix .with a lil help

Im pretty sure im the one who coused it so i need to be able to fix it.

Its crazzy the way this all came about so heres a brief explinatiin

Work for several motels and they allow us to take phones that have been in lost and found after a waiting period so i have a few phones to play with .ive been able to bypass frp and unlock the phones in doing so thought it might be easy to root one of them so i picked the only one that might be rootable a025qs android 11 .but after reading several difrent websights .that it cant be done. Cant unlock bootloader ? Hmm

Ive gotten this far only to run acrooss a mistake that i made but dont know how i did it . Ithink i know how but i stuck . Ive some how have hiden the baseband version and bootlader info off of thefastboot mode. So device isnt able to flash any thing help
[General Questions and Answers] Droidriven:
Adding external hardware is one thing, but, when you change internal hardware components, a completely new custom kernel(the whole kernel, not just a module) must be built with support for the new hardware added during the build process because the kernel is what tells your software how to use all of the internal components. Android kernels are streamlined, they do not have support for internal components that are not installed from the factory, there is no extra "driver support for non OEM components or generic support for other hardware" built in like with Linux or Windows. If a specific internal component isn't factory installed, there is nothing in the kernel to support it unless you build a new kernel with support for the new hardware built in. I've seen scenarios where a user would replace a broken screen with a non OEM replacement that wasn't exactly like the one they had and then they would have to build a modified kernel to make the kernel and the new screen compatible, not as simple as adding/pushing/editing a piece of code within the device. I've never tried any kernel dev either, but, I have some understanding of the process and how the kernel does what it does.

A Windows kernel is an enigma compared to Linux/android kernels, Linux kernel is a bit more of an enigma than android kernels but not as much of an enigma as a Windows kernel. Windows kernels have too much going on with having support for a plethora of "potential" components and chipsets where android only has to support a specific chipset and a more limited number of external components.
[General Questions and Answers] Renate:
Maybe I missed the context of this response.

If you're replacing some essential component with something incompatible, yeah, you might need to rebuild the whole kernel.

OTOH, you might get away with only writing a kernel module.

If this was about installing a bigger battery (I wouldn't) and the BMS didn't have a data interface you might get away with just fine-tuning some parameters.
[General Questions and Answers] Droidriven:
I guess it is like everything else Android, YMMV.
[General Questions and Answers] RickyBoby:
Hello XDA,

New in the flashing and rooting game. Learnt a couple of days ago. I use Kali on a daily basis and I wanted to try and go mobile. Finally, found a phone I could root, but it seems I also need a custom Kernel. I couldn't find one, so I tried building one myself but to no avail. V3rb0se helped me out with a thread and his custom Kernel, However, it isn't built on the same firmware.

Me: A515F UI3.1 Android 11

Custom Kernel: A51 Alynx Nethunter Kernel - Stock - Android 12 - UI 4.0

My question is, can I still flash the kernel with TWRP and my phone will update? If not, what steps should I take to get this running properly?
[General Questions and Answers] Droidriven:
It doesn't need to be built for the firmware, it just needs to be built to work on your specific hardware architecture.
[General Questions and Answers] SubwayChamp:
It`s probable that the userdata image got corrupted in the process itself or trying to transfer the file to a different location, in some way, but, assuming that the tool did the job well, then I can`t assume that the userdata image it`s corrupted and it needs some kind of fixing, the whole issue, is that a locked bootloader doesn`t admit a different image than the stock, the image that the user want to re-write to their device, it`s not necessarily corrupted, to my point-of-view.

Using mtk-client they can, arbitrarily, flash anything they want, but of course, the device unlikely will boot.
[General Questions and Answers] shamsaboubkr:
I messed up build.prop file located in vendor folder(using build prop editor from playstore)

Now my device gets stuck at Infinix logo

But i can enter Recovery, Bootloader and fastboot

So my question is can I flash the Vendor.img alone from my device stock firmware via fastboot using SDK platform tools to fix the issue?
[General Questions and Answers] Droidriven:
Yes, or, if you have access to adb, you can use adb push to push a copy of your unmodified build.prop to replace the corrupted build.prop.
[General Questions and Answers] ChenataBaby:
Hello everyone,

I'm really a novice in Android so I'm not quite sure how to synthesize the question but here it is:

I accidentally cleared the App Data of Instagram on my Xiaomi Redmi Note 10 Lite, and I thought it would only clear the cache but it deleted the folders in the gallery where I downloaded photos and videos from the app which were shared from me or other people in chats. Now I'm unable to revert this and they're all gone. I also haven't done a backup from Mi Cloud or any other backup that can be used.

Is there a way to restore these photos and videos by rooting the phone and using a third-party restore software or by any other way?

The phone is not rooted and is using Android 12 SKQ1.210908.001 on MIUI version 13.0.2.

Any advice would be really helpful!

Thanks in advance!
[General Questions and Answers] SubwayChamp:
I don`t really know, for sure, if this can work, but as your Android device can be mounted, and read, natively in Linux, I feel that can be done through it, read this https://www.systranbox.com/how-to-recover-deleted-files-in-android-phone-using-linux/

Also, you should take a look, in the Gallery file manager, in case it has a trash bin, and as a consolation, probably you can find many images in the folder Pictures or in the folder DCIM, as thumbnails.

Of course, you can wait, in the meantime, a more exact, or better targeted answer.
[General Questions and Answers] Markix_:
In 2022, is there any purpose to rooting your phone?

Sure I'd very much like to get rid of bloatware I don't use but other than that, I can't think of anything else...
[General Questions and Answers] Droidriven:
It depends on the user, some use root in order to add/enable/setup features and mods that did not come on the device natively. Some use root because they are power users and root is required for some apps to function. There are lots and lots of uses, it just depends on how deep you go and whether you as the user need to go that deep or use things that require going that deep.
[General Questions and Answers] Fytdyh:
1. Privacy concerns can be alleviated with root. Flashing a privacy inclined custom rom, degooglied.

2. Getting a custom launcher to work with gesture navigation and recents.

3. Certain apps, like Viper audio, in order to enhance audio output.

4. Certain apps for gaming, in order to maximize your performance and turn a rather mediocre smartphone experience into a decent one.

5. Getting a feeling of a pixel smartphone in a budget, like the nexus series used to be.

6. Certain apps for media consumption, if you are looking to set up a server on your phone. Given that some smartphones have even 12 gigs of ram, that makes sense.

7. Buying a Chinese phone for cheap and flashing a global custom rom.

8. Hiding bootloader status from banking apps, netflix or Amazon.