yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy A50 ROMs, Kernels, Recoveries, & Ot] explay999:
Great kernel! I would love if you could update magisk to the newest version.
[Samsung Galaxy A50 ROMs, Kernels, Recoveries, & Ot] rezabahramnezhad:
Can we install on oneui4?
[Samsung Galaxy A50 ROMs, Kernels, Recoveries, & Ot] Suryadip___:
Can you give me kernel new link or file v 2.0 one ui 3.1 because link not working.
[Samsung Galaxy A50 ROMs, Kernels, Recoveries, & Ot] Suryadip___:
Bro you have file of this kernel because links not working now
[Realme 7 Questions & Answers] R.2.:
is there is any custom recovery available for realme 7 ?
[Xiaomi Mi A2 / 6X Questions & Answers] Corburry:
I recently purchased a refurbished Mi A2. Today i tried to connect the phone via USB to my PC (tried Win10, Manjaro & Ubuntu) which did not work. While I can charge the phone it is not recognized as a storage device. When looking at the USB configuration in the developer options all the "use usb for" options are greyed out.

It runs Android 10 with the Dec 2020 security update. Since I already tried pretty much every solution recommended in other threads I was wondering if it is an issue with the current android version or if the charging port (which should be new after refurbishment) has to be replaced.

I would appreciate any input or help. Many thanks!
[Touch Diamond, MDA Compact IV General] doopsie:
Hi guys,

I backup my mails and pim using sprite backup, and restored them after a hard reset. The thing is, my mail shows up in manila.exe but i cannot find it in messaging. Is there a way to delete it while retaining my smses or restore the account? I tried creating the account before restoring but it just deletes the account i created. And if i try creating an account under the same name it does not let me do so. Please help. :(
[Touch Diamond, MDA Compact IV General] DeepDay:
This is exactly my problem too.

Pls advise!
[Touch Diamond, MDA Compact IV General] Epioneer:
I have the same problem. Any one can help?
[Moto G5 Questions & Answers] Dislekzi4:
Hi, I used Carbon ROM on XT1670, when I wanted to change ROM I ran:

fastboot -w

And i got this:

View attachment 5174151

I also tried to remove them:

View attachment 5174155

In TWRP I tried to do something but all I get is something similar to this:

View attachment 5174161

Am I missing something? Thanks for your help.
[Moto G5 Questions & Answers] Dislekzi4:
I've been reading the question and answer forum, apparently it's a problem with the encryption.

I don't have the Moto G5 right now, I can try it in a couple of hours, what other solution could I have anyway?
[Moto G5 Questions & Answers] TheFixItMan:
In twrp go to wipe

Then press the option on the right to format data

Reboot to recovery

Note this is different from wipe data from the advanced wipe menu.

The fastboot command would be

fastboot erase userdata
[Moto G5 Questions & Answers] Dislekzi4:
Hello, good (and bad) news

I did and now I have MTP for TWRP.

But still CMD says "Bootloader is logical @@@ not found"

"@@@" is depending on what you are trying to flash, be it system or recovery.

I was also able to change the filesystem I did it for DATA / CACHE / SYSTEM I went from FAT and then to EXT4 again.

Insert a ROM and it flashed without problems but it starts again in fastboot, the same if I do it with ADB Sideload.

I also tried flashing Stock ROM, everything seems to be written without problem but with the first line of "Bootloader logical ... not found" and again start in fastboot.

It makes me believe that something is still encrypted.

I mean this.

View attachment 5174881
[Moto G5 Questions & Answers] Dislekzi4:
I also tried

fastboot format:ext4 userdata

But I have this:
[Moto G5 Questions & Answers] TheFixItMan:
Bootloader is logical not found - this is normal output

Why are you trying to change formats? You are going to have issues especially with encryption. Use twrp to format not fastboot if you are messing with formatting but make sure you know what you are doing!
[Moto G5 Questions & Answers] Dislekzi4:
I flash a rom (no apparent problem, even Stock ROM) but it only boots to fastboot or the robot with an open belly.

What exactly should I do, I will follow step by step, I really need to get it back. Thank you very much for your help.
[Moto G5 Questions & Answers] Dislekzi4:
Hello again, I saw you in another post that apparently has the same problem as me, it is this:

https://xdaforums.com/t/decryption-unsuccessfull.3713556/#post-74722860
[Moto G5 Questions & Answers] Dislekzi4:
I have the same bugs, do you think I should run the command to decrypt?
[Moto G5 Questions & Answers] TheFixItMan:
In twrp format data

That is by selecting wipe

Then the option on the right to format data

Reboot to recovery

Everything should now be mountable

Make sure you are flashing stock rom correctly

fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot

Making sure you are flashing the same or newer firmware version than already on your phone

If your phone keeps booting to recovery (android with an open stomach or twrp) then do this

Boot into twrp then connect phone to PC and in cmd/terminal type

adb shell dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc

Reboot and your device will boot normally (assuming you have a working rom)
[Moto G5 Questions & Answers] Dislekzi4:
Hi, it work!

Thank you very much for your time and help, I am very grateful, for a moment I thought it was really a hardware problem.
[Moto G5 Questions & Answers] Rod_Ems:
I get device unauthorized. Please check the confirmation dialog on your device. and it won't let me do anything :(
[Moto G5 Questions & Answers] TheFixItMan:
Enable adb debugging on your device in dev options

Make sure you are using the latest platform tools

https://dl.google.com/android/repository/platform-tools-latest-windows.zip

Unzip

Navigate your cmd window to to the platform tools directory

In cmd type

adb devices

Look on your phone and a window will pop up asking you to confirm authorisation - tick the box to allow always if you want to

Then type

adb devices

And your device is authorised
[Moto G5 Questions & Answers] danniel_sx:
mine show the following error message: device '(null)' not found
[Moto G5 Questions & Answers] TheFixItMan:
Either

Your phone is not connected to pc

Faulty cable

You haven't installed Motorola USB drivers

You are using the wrong commands

If in fastboot mode type

fastboot devices

If in recovery mode type

adb devices

Your device should be listed if correctly connected
[Moto G5 Questions & Answers] Cristiansitow:
I found a solution, i'm argentinian so sorry if my english is bad

the fastboot menu of the combination power + volume down have no permissions to all modifications

You have to acces to the recovery fastboot menu, to do this, move to "recovery mode" enter here with power

Now if in the screen appears "No command" you have to press power + volume down for 3 sec and press vol up without press the another 2, then release the 3 buttons

Now go to "fastboot" in the recobery mode, and ta daaa. You have permissions
[Moto G5 Questions & Answers] Kireej:
dont have recovery partition is the problem only fastboot
[G4 Q&A, Help & Troubleshooting] steadfasterX:
Sounds like the ilapo. Is the battery charged now? I don't know which LOS version you have installed but if you use mine:

follow FAQ #7 of my LOS thread
[G4 Q&A, Help & Troubleshooting] electricfield:
Thank you for your reply. You seem to know more about G4 issues than anyone. I really appreciate your help.

The battery is charged now.

Unfortunately, I am using the microg version of LOS 14.1, rather than your 16.0.

I tried following the instructions in your FAQ #7, but I can't do step 1 (boot android). The only way for me to exit the bootloop is by removing the battery. There is no "debug" in /cache after I mount cache in TWRP.

I also looked at FAQ #1. ADB never finishes waiting for the device. In fact "lsusb" doesn't show the phone during OS boot (ADB is fine when TWRP is loaded).

Any other ideas?
[G4 Q&A, Help & Troubleshooting] steadfasterX:
As written in my mentioned FAQ taken battery out is needed in your case. Step 2 iirc.

If you dont use my LOS then no way. The cache/debug is something I've added and no one else has.

Option1:

You can just flash my LOS 16 or /e/ ROM (take a full backup before in TWRP) and use that for debugging your current issue. Why using microg btw? /e/ is great ;)

Option2:

The other option would be pulling the boot img of your current LOS (in TWRP: adb pull /dev/block/bootdevice/by-name/boot ) and rebuilding it as insecure (i.e. usb debug on and adb root ) but if you never did that before it it will be hard i guess. AiK might work here or using mAid which includes bootimgtool.

Option3:

Also you can attach that boot img here and if i ever find the time i can do option2 for you but don't expext that this happens soon .
[G4 Q&A, Help & Troubleshooting] electricfield:
Thank you again for your help.

I'm a little afraid that installing a new & different ROM will increase the level of complexity. I'll do it if I must, though.

I started looking at option #2. Retrieving the boot image was fine, but unpacking presents a problem.

$ ./unpack-bootimg.sh boot.img.original

Found a secondary file after the ramdisk image. According to the spec (mkbootimg.h) this file can exist, but this script is not designed to deal with this scenario.

Is there a guide anywhere?
[G4 Q&A, Help & Troubleshooting] steadfasterX:
thousands.. But the problem is that our device is sensitive when it comes to packaging the boot.img again. Bootimgtool is working in 9 of 10 times though.

Boot mAid . Open a terminal. Type bootimgtool --help .important is to use "-v qcom". Then extract the ramdisk with gzip and cpio, then modding the default.prop to make it insecure , then using gzip and cpio again to rebuild the ramdisk, finally using bootimgtool to construct the boot.img again. Sounds harder than it is but i have no access to my pc until monday so i cannot give all the needed cmds atm. There are plenty of guides out there and tools ofc which allow unpack,repack etc. That's why i mentioned AIK which does exactly the above but it fails sometimes to build a correct working boot.img.

So my suggestion is try your luck with one of the tools or wait until I've access to my pc. Consider joining my TG group then for easier support (see my sig)
[G4 Q&A, Help & Troubleshooting] electricfield:
Thank you once again. I'm really impressed by how much help you have been able to give so far.

Unfortunately, I have no phone with which to join the Telegram group.

I made the modified boot image, but adb is still unable to speak to the phone during boot. I note that lsusb does not show the phone during boot -- maybe the system hangs before USB is activated. However, I could have made the boot image incorrectly.

Here is what I did:

[android@fwul extract]$ bootimgtool -i boot

Image size: 41943040

Page size: 4096

Kernel size: 22456976

Ramdisk size: 1672742

Second stage size: 0

Device tree size: 0

Kernel load address: 0x00008000

Ramdisk load address: 0x01000000

Second stage load address: 0x00f00000

Device tree load address: 0x00000000

Tags load address: 0x00000100

Product name:

Command line: maxcpus=4 boot_cpus=0-1 console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 msm_rtb.filter=0x37 boot_cpus=0-1 buildvariant=userdebug

[android@fwul extract]$ bootimgtool -x boot -v qcom

[android@fwul extract]$ gunzip ramdisk

[android@fwul ex]$ cpio -i < ../ramdisk

In default.prop, I changed:

ro.adb.secure=0

ro.secure=0

security.perf_harden=0

ro.debuggable=0

persist.sys.usb.config=mtp,adb

In default.prop, I added:

persist.service.adb.enable=1

persist.service.debuggable=1

[android@fwul ex]$ find > /tmp/filelist

[android@fwul ex]$ cpio -o < /tmp/filelist > ../ramdisk.modified

This produces

-rw-r--r-- 1 android users 4166400 Jan 2 17:29 ramdisk.gunzip.original

-rw-r--r-- 1 android users 4162048 Jan 2 17:31 ramdisk.modified

-rw-r--r-- 1 android users 1672742 Jan 2 17:16 ramdisk.img.original

I don't understand why the "modified" gunzipped file is slightly smaller than the original.

[android@fwul extract]$ mv ramdisk.modified.gz ramdisk.img

[android@fwul extract]$ cp boot boot.original

[android@fwul extract]$ bootimgtool -v qcom -c boot

Overwrite 'boot'? [y/N] y

-rw-r--r-- 1 android users 25370624 Jan 2 17:38 boot

-rw-r--r-- 1 android users 41943040 Jan 2 17:37 boot.original

I am wary because I don't understand why the new file is so much smaller than the original. However, I decided to proceed. Uploaded modified boot to /sdcard/boot.modified

Inside adb:

/dev/block/platform/soc.0/f9824900.sdhci/by-name # ls -al boot

lrwxrwxrwx 1 root root 21 Jan 1 04:16 boot -> /dev/block/mmcblk0p38

/dev/block/platform/soc.0/f9824900.sdhci/by-name # cp /sdcard/boot.modified /dev/block/mmcblk0p38

Plugged in device. On computer "adb wait-for-device". Reboot device.

Unfortunately, no action from adb.
[G4 Q&A, Help & Troubleshooting] steadfasterX:
Ok i haven't followed every step bc I'm in half sleep mode already but you did one step wrong : you cant use cp like you did to copy the boot img. Either use the IMG button within TWRP flash menu or use fastboot flash boot boot.img to actually flash the modded boot img
[G4 Q&A, Help & Troubleshooting] electricfield:
Thank you, once again.

I think that something must be wrong with the boot image.

After "fastboot flash boot boot.modified", I get a blue light. The screen is blank with a cursor in the upper-left hand corner.

"fastboot flash boot boot.original" restores it to its previous state. i.e., it gets to the first lineageos splash screen bubble.

I'm suspicious of the difference between the file sizes of the original and modified boot images.
[G4 Q&A, Help & Troubleshooting] steadfasterX:
Ignore the size diff. That's bc of diff compressing tools but does not matter. Your cpio cmd is unusual . Cpio has switches to create directories and that is not used in yours above . Thats likely the reason why it does not boot at all. Again sorry that i can't help better atm but without my pc..
[G4 Q&A, Help & Troubleshooting] electricfield:
Thanks.

I changed the ramdisk extraction command to:

gzip -dc ../ramdisk.img | cpio -imd

and the creation command to:

find . ! -name . | LC_ALL=C sort | cpio -o -H newc -R root:root | gzip > ../new-boot.img-ramdisk.gz

Bootimgtool then produced a boot image that booted. After fastboot flash, the device is in the same state as before (splash screen).

Unfortunately, "adb wait-for-device" produces nothing. "lsusb" does not show the phone.

Can you confirm the lines to change in default.prop?

In default.prop, I changed:

ro.adb.secure=0

ro.secure=0

security.perf_harden=0

ro.debuggable=0

persist.sys.usb.config=mtp,adb

I added:

persist.service.adb.enable=1

persist.service.debuggable=1
[G4 Q&A, Help & Troubleshooting] steadfasterX:
ro.debuggable=1 is better (allows adb root)

security.perf_harden shouldn't be added (or.changed if it was there)

Rest looks ok. At least as long as you really changed these values directly or added them at the top (ro. values can be set only once)

Otherwise you should wait until tomorrow then i can share a 100% working way
[G4 Q&A, Help & Troubleshooting] steadfasterX:
Oh wait! Pls share the bootimgtool command you are using to create the new boot.img
[G4 Q&A, Help & Troubleshooting] electricfield:
Thank you, again.

The bootimgtool command is the same one as I used before (no change). Before running it, I renamed the new ramdisk to ramdisk.img.

bootimgtool -v qcom -c boot.modified3

Followed by bringing the phone into fastboot mode and running

fastboot flash boot boot.modified3

The phone boots to the lineageos splash screen but no response to "adb wait-for-device".

I'll try ro.debuggable=1 and get rid of security.perf_harden in a few minutes, but I wonder if they are unlikely to change anything given that the device does not show up in (linux) lsusb.
[G4 Q&A, Help & Troubleshooting] steadfasterX:
That wont change anything if adb does not come up. Just for completeness.

Ok so if you renamed it to ramdisk.img then all.good that was the thing i had in mind (that you didn't and not.used the -r switch). Well ok then without my pc the only thing i can think of might be the USB cable but thats very unlikely
[G4 Q&A, Help & Troubleshooting] electricfield:
Thanks again for your help.

The boot image that was flashed is definitely the correct one. I extracted it to another folder and checked it before flashing.

I re-made the boot image, but the result is the same (no adb, no device in lsusb).

What "-r switch" are you referring to in your previous message?

The USB cable works fine for ADB in TWRP, so I doubt it is the problem.
[G4 Q&A, Help & Troubleshooting] steadfasterX:
The -r (iirc) switch was related to bootimgtool. That way you can choose your newly created ramdisk.img ;) but when you renamed it to ramdisk.img it works without.
[G4 Q&A, Help & Troubleshooting] electricfield:
Thanks.

I would deeply appreciate if you were able to guide me in making the boot image correctly when you have your computer on Monday.

On the other hand, if this method won't work, its best if I know that so that I can try the next thing....
[G4 Q&A, Help & Troubleshooting] steadfasterX:
ok here you go, this must be added /changed in default.prop:

ro.adb.secure=0
ro.secure=0
ro.debuggable=1
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=adb

thumbs pressed ;)
[G4 Q&A, Help & Troubleshooting] electricfield:
Thank you.

I rebuilt the boot image with these entries, but "adb wait-for-device" still does not work during boot.

Any other ideas?
[G4 Q&A, Help & Troubleshooting] steadfasterX:
share the untouched boot.img and the one you modded pls
[G4 Q&A, Help & Troubleshooting] electricfield:
Thanks -- here they are.
[G4 Q&A, Help & Troubleshooting] steadfasterX:
ok lets try that one
[G4 Q&A, Help & Troubleshooting] electricfield:
Thanks. Unfortunately, the result is the same :( No response from "adb wait-for-device" and the phone does not show up in lsusb.
[G4 Q&A, Help & Troubleshooting] steadfasterX:
well that is weird then.

u can either flash one of my ROMs or adding debug code into the init script within the boot image.

if you wanna add my debug patch here the required lines:

https://github.com/Suicide-Squirrel/android_device_lge_g4-common/blob/lineage-16.0/rootdir/etc/init.qcom.rc#L86-L90
https://github.com/Suicide-Squirrel/android_device_lge_g4-common/blob/lineage-16.0/rootdir/etc/init.qcom.rc#L469-L472
https://github.com/Suicide-Squirrel/android_device_lge_g4-common/blob/lineage-16.0/rootdir/etc/init.qcom.rc#L1094-L1110
https://github.com/Suicide-Squirrel/android_device_lge_g4-common/blob/lineage-16.0/rootdir/etc/init.qcom.rc#L1125-L1127
https://github.com/Suicide-Squirrel/android_device_lge_g4-common/blob/lineage-16.0/rootdir/etc/init.qcom.rc#L1139-L1141

or as patches:

https://github.com/Suicide-Squirrel/android_device_lge_g4-common/commit/f94cb6dd4ffaa7c60741c9bae12aa06030ccc1d4.patch
https://github.com/Suicide-Squirrel/android_device_lge_g4-common/commit/3d72007ff701fc26a4e3979662bd35b9f8da8742.patch
https://github.com/Suicide-Squirrel/android_device_lge_g4-common/commit/706cd0a8a78e5bf610299d26d2b4d66707fd314f.patch
[G4 Q&A, Help & Troubleshooting] electricfield:
Thanks again for your help.

I ended up installing your lineage 16.0 from Dec 21, 2020 (already had it on hand). I let the phone boot for 20 minutes under a fan to minimize heating.

Here are my logs -- it looks like all of the action takes place in the first 32.5 seconds.

The lc_crash file seems to point to a problem that occurs when loading the fingerprint service. I don't care if the fingerprint reader works -- do you think that this is a fingerprint device problem or that the real trouble is something else entirely and the failure just happens to occur when the fingerprint device is initialized?
[G4 Q&A, Help & Troubleshooting] electricfield:
Hmm... are all of these empty XML files normal?

/data/system # ls -las *xml

100 -rw------- 1 system system 98378 Dec 31 2020 appops.xml

20 -rw------- 1 system system 18568 Feb 8 2015 batterystats-daily.xml

4 -rw------- 1 system system 392 Dec 30 2020 device_policies.xml

4 -rw------- 1 system system 272 Dec 25 2020 deviceidle.xml

4 -rw------- 1 system system 369 Jan 1 00:57 display-manager-state.xml

4 -rw------- 1 system system 339 Dec 30 2020 install_sessions.xml

0 -rw------- 1 system system 0 Dec 31 2020 log-files.xml

0 -rw------- 1 system system 0 Feb 8 2015 netpolicy.xml

0 -rw------- 1 system system 0 Feb 8 2015 notification_policy.xml

0 -rw-rw---- 1 system system 0 Feb 8 2015 packages.xml

0 -rw------- 1 system system 0 Feb 8 2015 profiles.xml
[G4 Q&A, Help & Troubleshooting] electricfield:
(If you're wondering, I did clean

So, I backed up /data/system. I then deleted the following empty files, hoping that android would re-generate them:

packages.list

packages.xml

profiles.xml

netpolicy.xml

notification_policy.xml

Now, it boots!
[G4 Q&A, Help & Troubleshooting] steadfasterX:
glad you solved it!

yes the crash indicates an issue with parsing these XMLs (as they are empty). That kind of data corruption has been fixed long time ago but as you were on a non-suicide ROM you didn't had that fix .. ;)

anyways I am just curious: you have used the microg version of LOS and now switched to our LOS - why not using /e/ OS ? :)

.-
[G4 Q&A, Help & Troubleshooting] electricfield:
Thank you for the help! You're awesome!

Soon, I'll write up a summary for people who come upon this problem in the future.
[G4 Q&A, Help & Troubleshooting] steadfasterX:
summary: use a current ROM ;) haha jk.
[G4 Q&A, Help & Troubleshooting] Bcoates84:
I Think you for got to remount the dir in twrp. Try to type adb devices ; adb usb. If you can get into twrp. Look at my photo on the Mount make sure you have the little check boxes checked.

Also pull the battery out look at the sticker

Please fill this out on what the sticker says >>>

FCC ID:

IC ID:

M/N:
[Android Q&A, Help & Troubleshooting] diegocapassi:
First one, wish you and your family a safe and great new year.

Second,I need help to unban my account.

Used for 5 years angry birds 2 and after switched to another phone I've been banned.

The ban cannot be lifted.

I've send many tickets but nothing happens.

The game was important for me cause I use it to distract from my parents brain problem with cancer and Alzheimer too.

Please,if someone could help I need an help.

Have just a phone not rooted,any help would be appreciated.

Ty all

diego.capassi@gmail.com
[Android Q&A, Help & Troubleshooting] Raiz:
Welll unfortunately we can't do much for you. If you can't get in contact with the angry bird's mod team, who have control over their servers and game policy, try to post a message on the game's forum for help contacting them (unofficial forum), maybe you'll get some help.

Here's the game's website and why they don't answer you rn
[Android Q&A, Help & Troubleshooting] Deleted member 1890170:
To get temporarily unbanned from Angry Birds 2 ( account ) turn Wi-Fi off before opening app.