yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy J2 Guides, News, & Discussion] Badger50:
Perfect. Thank you. (y) (y)
[Touch Pro, Fuze General] Antzor:
I've followed just about EVERY guide to get gps to work on these forums and so far absolutely nothing works. I simply cannot get an accurate lock in google maps at all. Whenever I select "Use GPS" it says "seeking gps satellites" and never appears to find any.

My radio version is 1.02.25.19

Has anyone had this problem or knows how to fix it?
[Samsung Galaxy S21 FE] afaneh92:
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.

* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.

Supported Models:

Galaxy S21 FE 5G G9900 and G990B.

Download & Guide:

1. Unlock your bootloader.

2. Download S21 FE 5G: r9q.

3. Reboot to download mode

4. Put the TWRP TAR for your device with Odin in the AP slot, vbmeta_disabled_R.tar in USERDATA slot and click start.

5. Reboot to recovery via recovery key combo (Vol up + power + USB connected).

6. Disable encryption:

- Go to Advanced > Terminal, type: multidisabler.​

If vendor complain about free space left on device, will attempt to resize vendor. and it ask to - Run multidisabler again!.​

- Type: multidisabler again. will see - Finished. when done.​

- Go back to Wipe > Format Data > type yes.​

- Reboot to recovery.​

7. Flash magisk apk in twrp.

8. Reboot to system, Enjoy.

Bugs:

- Encryption not fully working.

- Haptic feedback is currently not working.

Thanks:

TWRP team

@ianmacd for multidisabler

@Dan_FFM (David Dean) for testing and fix touch

Sources:

Kernel tree

Device tree
[Samsung Galaxy S21 FE] afaneh92:
Changelog:

01.05.2022 - Initial Release.
[Samsung Galaxy S21 FE] Doghan13:
Tested on BVB3 and CVC6 roms, both are working perfect.

On CVC6, wiping data worked and multidisabler seems to be working too. My phone is rebooting and after all data recover I can tell if it done well completely.

Edit : backup is working, install zip is working, to me there is no bug. Just one weird thing, after the update I directly installed TWRP, it worked fine. Then decrypted data and reboot. When finished, I wanted to reboot recovery via Vol Up and power, it always boot up to system, I née needed to reflash TWRP to access it again.

Except this little thing, it works great.

Many many thanks !!
[Samsung Galaxy S21 FE] wazer1337:
Great cant wait to test whenever I got some time to clear it all and start over :/
[Samsung Galaxy S21 FE] wazer1337:
Any1 who tested yet?
[Samsung Galaxy S21 FE] Mr NI:
How do I unlock my bootloader?
[Samsung Galaxy S21 FE] Dr.Lost:
If you bought a US Version, i.e. Carrier brands, you cannot do so, even if you have an unlocked. All US Snapdragon device after like S6 they've kicked us out. If you have a Exnos.

1. Open Settings scroll to about device

2. Tap on Software Information tap build number 5 times to show hidden developer settings.

3. Scroll to you see OEM Unlock.

4. Refer to guides online after step 3
[Samsung Galaxy S21 FE] Mr NI:
well isnt that ass
[Samsung Galaxy S21 FE] icalgoos:
I am considering buying the smartphone. But the root access ist important for me.

Need you to enter twrp again to have root access after a restart and a connection to pc to enter twrp? I ask because my Galaxy A50 loose after every restart the root access and I need to enter the twrp with a connection to pc to fix it.
[Samsung Galaxy S21 FE] joke19:
When you make all right, unlock bootloader, twrp, vb_disabler and then magisk. Then you have a rooted phone with advantages and disadvantages. No loosing after reboot. But no OTA too
[Samsung Galaxy S21 FE] Discorly:
Does nandroid backups work with this version and android 12?
[Samsung Galaxy S21 FE] stuntora:
how can we update the phone say to OneUI 5.0 in the future and keep root.
[Samsung Galaxy S21 FE] ShaDisNX255:
Patch the fw with Magisk, use Magisk install instructions and possibly replace recovery.img with TWRP so that you keep it and flash any multi disabler again that you may have already flashed.
[Samsung Galaxy S21 FE] Benjamin2557:
Is it mandatory to format data when we already have Magisk installed ?
[Samsung Galaxy S21 FE] afaneh92:
If you are full stock, then disabling vbmeta will trigger a wipe
[Samsung Galaxy S21 FE] Benjamin2557:
Just a thought, I have stock ROM october patch and I have Magisk installed properly with Zygisk activated.

I obviously already done a full wipe for this.

If one day I would like to install TWRP, a full wipe will be mandatory ?

I'm asking since I understand that full stock means no Magik installed, which is not my case.
[Samsung Galaxy S21 FE] afaneh92:
Yes its mandatory
[Samsung Galaxy S21 FE] R0298:
does smali patcher work on rooted galaxy s21 fe?
[Samsung Galaxy S21 FE] MoveToZero:
Hello Mohammad,

After rooting I keep getting "ERR_INTEGRITY" errors in logcat, so some apps (especially Samsung ones) don't work properly. Is it normal since you wrote "Encryption not fully working", or am I doing something wrong?

Thank you!
[Samsung Galaxy S21 FE] afaneh92:
Usually because bootloader unlocked, use safetynet fix module.
[Samsung Galaxy S21 FE] kufysk:
[deleted]
[Samsung Galaxy S21 FE] MoveToZero:
Yeah it is for sure a Bootloader / tripped Knox issue, but I just cannot fix it no matter which Safetynet fix I flash. I pass Safetynet every time, but still get when trying to use Samsung Health Monitor.

E/S HealthMonitor - WsmController: WsmSession.connect(). fail : ERR_INTEGRITY
[Samsung Galaxy S21 FE] Brea-flee:
It's because of the tripped knox. Just look for knox patch github. It's an Lsposed module. I've been using it for secure folder and S.Health.
[Samsung Galaxy S21 FE] Wera2:
Is this work on g990u1/DS
[Samsung Galaxy S21 FE] afaneh92:
Bootloader must be unlocked and not supported yet
[Samsung Galaxy S21 FE] Wera2:
Ok thnx bro but alert us if it supported on snapdragon
[Samsung Galaxy S21 FE] afaneh92:
Read the thread title and supported list in op
[Samsung Galaxy S21 FE] BABYFACE10:
Work perfect, little work with safetynet but now google wallet and everthing runs perfect.
[Samsung Galaxy S21 FE] navi7512:
Whats happen if encryption is not disabled??

Ask because some apps require device encryption to work ...
[Samsung Galaxy S21 FE] afaneh92:
You can skip the encryption disable but data will be unusable in twrp
[Samsung Galaxy S21 FE] Gueste4555:
will this tutorial work with a Samsung Galaxy S21 FE 5g SM-G990B2/DS?

So is it necessary to also flash the ''Samsung multidisabler.zip'' and ''DM Verity Force Disabler.zip'' files?
[Samsung Galaxy S21 FE] afaneh92:
Read the instructions and supported list in OP
[Samsung Galaxy S21 FE] Gueste4555:
Is TWRP able to decrypt data?

Does encryption work fully?
[Samsung Galaxy S21 FE] afaneh92:
no
[Samsung Galaxy S21 FE] appu1993:
Is there any way to update stock rom after installing twrp..?
[Samsung Galaxy S21 FE] applekid2016:
How do you unlock the bootloader for this device? i went into developer mode and oem unlocking is not there.
[TCL 10L Questions & Answers] exsheal:
Hello XDA forum members. I'm Turkish so my english might be bad, sorry about that.

Today I was formatting my "TCL 10L T770H" phone with the "TCL Mobile Upgrade 0.1.6" program. But it gave such an error while formatting and the phone started to reboot itself constantly. What do you think could be the problem?

I tried 3 more times but it still gave the same error.

View attachment 5603703

Normally, the phone was working fine, I just wanted to format it.
[TCL 10L Questions & Answers] ibramreda:
same problem with me
[TCL 10L Questions & Answers] loonbgg:
don't use that software it can kill your phone os instead flash it .. its due Data formation error
[Android TV General] GoldenJet:
Hi would like to know I have a hisense 55A6G with Vidaa. Is there a custom firmware or better firmware version I can download I can't find anywhere on the TV a app store or Google playstore or a way to access my USB stick to install apk files. Just looking for a better firmware or OS to access files and download apps etc.
[Android TV General] nxb:
You have to access ADB and you can then put mostly whatever apps you want:

https://xdaforums.com/t/rooting-hacking-hisense-a6g-m7322-based-android-tv.4451587/
[Android TV General] Akash420:
Hisense when came new update on 55A6u . Model . ?
[Android TV General] TMHAKIM:
Bruh VIDAA and Android are a whole different operating systems. you can't install APK files on it. Also VIDAA is hot garbage
[Vivo X70 Pro+] fabrixx:
- If I plug my USB-C lavalier and record a video with the camera app, now I hear only a rustle.

- If I use it in the Logitech Mevo or Logitech Mevo Multicam application connected to the external camera, (it has worked for months) plugged mic no longer works.

I'm going crazy and as I need urgently it to get my channel going for the outdoor streamings I'm really thinking of selling it and going back to the Pixels.

I can only use the recorder application whith my mic it works correctly so the microphone is not broken but there is something in external mic recognitions with other apps (like camera and others)

There is no technical support
[Coolpad Cool1 Questions & Answers] Lord87:
I am trying to flash TRWP onto Coolpad Cool 1. I am mainly following this manual https://xdaforums.com/t/guide-eui-c...ot-easy-twrp-root-using-qfil-for-eui.3781171/ but tried a couple of others as well (e.g. https://xdaforums.com/t/guide-9-0-r...-to-android-9-from-jui-or-nougat-rom.3954064/).

I was able to get to a point when everything behaves as expected (devices/drives/ports/etc). After pressing Download in QFil, the whole process runs without any errors (attached log). But when I reboot to recovery, the TRWP is not there. Stock recovery is still installed. I've been stuck with this issue for a few hours now.
[G1 Android Development] jriley60:
hooray! you're awesome:D
[G1 Android Development] Dimath:
Where does boot.img flash? What is the corresponding part of the system?
[G1 Android Development] alansj:
I'm not sure what exactly you mean, but when you do flash_image boot imagefile.img it will write imagefile.img to /dev/mtd/mtd2, which is where your phone looks for the boot files. Did that answer your question?
[G1 Android Development] eckzow:
For your command...

cat /dev/zero >> /dev/mtd/mtd2

Do you mean

cat /dev/zero > /dev/mtd/mtd2

?

The idea being that you erase flash in the version with one '>', whereas you... append to the end of a device in the version with two '>'s? I can see the utility of erasing flash with one '>' but appending seems... odd. Am I missing something?
[G1 Android Development] andonnguyen:
Is this any different than using the Dalvik Debug Monitor (DDMS) file manager found the the Android SDK? I'm able to push, pull, and delete files on my G1 with no problem.
[G1 Android Development] jnasti1:
Would this be the only way to rebuild a system app (i.e. Settings.apk) with more debug (Log. to extract via adb logcat over usb), then rebuild the entire system.img, then flash into the G1?
[G1 Android Development] alansj:
I think you're right. I copied that from somebody else's instructions and it certainly seems to make more sense with one '>'. Anybody know for sure?

In any event, this is unnecessary in most cases because flash_image should overwrite the whole thing. The only exception is when you have an identical header on your image to the one that is already on the device. This shouldn't happen in my instructions (mkbootimg creates a header that includes the build timestamp) but I kept the instruction there just for good measure.
[G1 Android Development] alansj:
The adb push command I gave is no different, but you would still have to unpack/repack and flash_image according to my instructions.
[G1 Android Development] Koush:
I've tried these instructions on RC30 1.3. Basically I extracted, unpacked, and repacked, just to see if it would work. The resultant file is too large; it fails when you run flash_image.
[G1 Android Development] [RiS]:
I'm trying to modify my boot image of my ADP1 using the perl scripts, but I receive the following warning while decompressing the ramdisk:

$ unpack-bootimg.pl mtd2.img

kernel written to mtd2.img-kernel.gz
ramdisk written to mtd2.img-ramdisk.cpio.gz

removed old directory mtd2.img-ramdisk

[B]gzip: ../mtd2.img-ramdisk.cpio.gz: decompression OK, trailing garbage ignored
462 blocks[/B]

extracted ramdisk contents to directory mtd2.img-ramdisk/

Is this warning expected? Is safe to continue?

Also, I've found that the size of the modified packed image is far smaller than the original one :confused:

$ ll mtd2.img mtd2-modified.img
-rwx------ 1 ris ris 2621440 2009-01-07 19:19 mtd2.img
-rw-r--r-- 1 ris ris 1533952 2009-01-07 20:49 mtd2-modified.img

Update: I've tried anyway.

For the record, I've obtained the boot.img using cat, uncompressed with the perl script, modified default.prop, repacked with the perl script.

As you see from the code above, the img file is much smaller (Opening with a hex editor you can see that the end of the original image is full of 0xFF, so I believe it's ok, both the gzip warning and the different file sizes).

Reflashed it from recovery mode, using

fastboot flash boot mt2-modified.img

fastboot reboot

... and worked flawlessly :D

I'm leaving the coment for future references.

Thanks for the tutorial :)
[G1 Android Development] alansj:
Yes, you would expect trailing zeroes, which would give you that error. The trailing zeroes exist in order to pad the image size to the nearest page boundary. They are added by mkbootimg.

Yep, that's exactly why. Nothing to worry about.

Thanks for the informative clarification.
[G1 Android Development] [RiS]:
I'm using an stock ADP1, and the file /system/recovery.img does not exist. Is this expected?

Also, I've found out in JFv.1.31 that the recovery image is in /data/recovery.img (although there is no /data/recovery.img in my ADP1 neither..)
[G1 Android Development] JesusFreke:
It deletes it after it flashes on the first bootup after you apply the update.
[G1 Android Development] [RiS]:
Are you refering to /data/recovery.img or /system/recovery.img? or both? :)
[G1 Android Development] JesusFreke:
I'm referring to /data/recovery.img in JFv1.2 and up (although there was a bug in the RC8 version of JFv1.2 that prevented it from being deleted)
[G1 Android Development] [RiS]:
So is there any reason why there is no /system/recovery.img on my ADP1?
[G1 Android Development] slevin.yu:
When I use the unpack script on JF1.31 boot.img, it prints out like this:

"Could not find any embedded ramdisk images. Are you sure this is a full boot image?"

Any help?
[G1 Android Development] JesusFreke:
Stock or JFv1.3?
[G1 Android Development] [RiS]:
"Stock". I've just modified boot img to change default.prop
[G1 Android Development] JesusFreke:
Then you don't have /system/recovery.img for the simple fact that it's not included on the stock ADP1 build. (iirc)
[G1 Android Development] [RiS]:
That's a bit weird, isn't it? if I put a recovery image on /system/recovery.img it flashes it. Do you think of any reason why that file is not there?

The only one that comes to my mind is to let the developers to play around the system partition and don't loss the changes after a reboot, but for me this is more a dangerous thing than a "feature"..:confused:
[G1 Android Development] JesusFreke:
It doesn't need to be there. As far as I can tell, the "flash /system/recovery.img on boot" feature is there so that you don't have to flash the recovery image while actually in recovery mode. This helps protect against bricked phones. If it replaced both the boot and recovery images while performing an update, there's a possibility that both could be corrupted, and thus the phone wouldn't boot. But by pushing the recovery image to /system/recovery.img, the new recovery image is only flashed once the phone has booted into normal mode - thus guaranteeing that it can still at least boot into normal mode, before it flashes the new recovery.

But on a new phone, there's no need for /system/recovery.img - it already has the correct recovery partition.
[G1 Android Development] alansj:
Also, from G1-Hackers list:

http://www.telesphoreo.org/pipermail/g1-hackers/2009-January/000462.html

Xiangfeng wrote:

Will wrote:

Donnie Smith wrote:

The split_bootimg.pl approach appears to be smarter and cleaner than my approach, because mine doesn't remove the trailing zeroes in the kernel. Ultimately, I don't know that it matters because I've never had a problem with using the padded kernel as an input, but it's probably a good idea to use the cleaner method.
[G1 Android Development] Plastriq:
How do you compile the mkbootimg tool? It's complaining about how it can't find sha.h, but I can't find it anywhere in the repos :(
[G1 Android Development] zabouth:
I compiled mkbootimg for linux x86 32bit.

Hope it helps.
[G1 Android Development] cpedia:
Any one can help me to repack the boot.img for adp1 with fireware 1.1

I don't have the mac os enviroment, so I can not repack the boot.img of adp1.1.

Any one can help me to do that?

I just want to change the /init.rc in the boot.img.

I want to add follwe two lines after line "chmod 0771 /data"

import /data/init.rc
trigger userdata

The result will looks like:

# We chown/chmod /data again so because mount is run as root + defaults
mount yaffs2 mtd@userdata /data nosuid nodev
chown system system /data
chmod 0771 /data

[COLOR="Red"]
import /data/init.rc
trigger userdata
[/COLOR]

# Same reason as /data above
mount yaffs2 mtd@cache /cache nosuid nodev
chown system cache /cache
chmod 0770 /cache

The original boot.img is the attached.

Please help me, great thanks in advance!
[G1 Android Development] blackgin:
I tried to unpack boot.img of android.. The guide says to execute this command

gunzip -c name.img | cpio -i

But executing this command fromthe terminal the result is:

gzip: name.img: not in gzip format
cpio: premature end of archive

What am I doing wrong?
[G1 Android Development] dbhatesyou:
odd question, i grabbed the linux mkbootimg did the command posted, and i end up getting permission denied. thus tried with sudo mkbootimg then get command not found.
[G1 Android Development] dbhatesyou:
guess no one has any ideas
[G1 Android Development] hercule18:
Same error for me!!

please help.

Bye

Herc.8)
[G1 Android Development] yukkio:
Hi, I'm trying to port last cyanogen rom and I cant. I've ported old cyanogen roms without problems using unpack and repack scripts but with the last rom I get this error:

./unpack-bootimg.pl boot.img
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.

I dont know what it's happening with this boot.img. I did md5sum and it's ok.

Thank you.

BR.
[G1 Android Development] dazcox5181:
I've got this too :( also had it on the first fatal1ty hero rom, never solved it yet
[G1 Android Development] yukkio:
I solved it.

Just add # to the lines in conflict (search into the script the print out).

BR.
[G1 Android Development] mistadman:
Elaborate

Elaborating on yukkio's comment:

if ($numfiles == 0) {
die "Could not find any embedded ramdisk images. Are you sure this is a full boot image?\n";
-} elsif ($numfiles > 1) {
-	die "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.\n";
-}
+}
+
+#elsif ($numfiles > 1) {
+#	die "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.\n";
+#}

$bootimg =~ /(.*\x00\x00\x00\x00)(\x1F\x8B.*)/s;
[G1 Android Development] zaff00:
Does Anyone have a Windows version of the mkbootimg tool?:confused:
[G1 Android Development] shafty023:
No b/c unlike Linux, Windows doesn't have a rich tool set. The script relies on binaries such as gzip & cpio which are not available in Windows.
[G1 Android Development] zaff00:
I managed to get a windows version of gzip & cpio, just need the mkbootimg or a windows compiler for it. Windows is real crapy in cutting down on the command line.
[G1 Android Development] uansari1:
Is there an easy way (i.e. via terminal or recovery console) to replace an existing 2nd splash screen with the animated HTC gif that has the Android peeking out from behind the HTC text?
[G1 Android Development] karan09:
android rom boot logo

i want to know how to change android logo the one after splash screen ? i want one like on hero .. i looked it in to files this is in cyangenmod 4.0.4 /system/bin/bootanimation . i dont know how to edit this file ..... and i looked it in hero and i find diff files

system/media/boot,boot2,boot.mp3,boot_animation.xml . Anyone.....??????

i see this in xml file

<?xml version="1.0" encoding="utf-8" ?>
- <!--
* Copyright (C) 2008 HTC Inc.
*

-->
- <!-- For new bootup animation
<BootConfiguration>
<BootAnimation
image="/system/media/boot.gif"
audio="/system/media/boot.mp3"
image2="/system/media/boot2.gif" (optional)
image3="/system/media/boot3.gif" (optional)
screenX="100" (optional)
screenY="130" (optional)
image_bg = "/system/media/boot_bg.gif" (optional)
useAudio="0" // 1: true ; 0:false (optional)
/>
</BootConfiguration>

-->
- <!-- For cropped version
-->
- <BootConfiguration>
<BootAnimation image="/system/media/boot.gif" image2="/system/media/boot2.gif" image3="/system/media/boot2.gif" loopimage="/system/media/boot2.gif" image_bg="/system/media/boot_bg.gif" audio="/system/media/boot.mp3" screenX="10" screenY="180" useAudio="1" />
</BootConfiguration>
- <!-- For full screen version
-->
- <!-- BootConfiguration>
<BootAnimation
image="/system/media/boot.gif"
audio="/system/media/boot.mp3"
useAudio="1"
/>
</BootConfiguration
-->
[G1 Android Development] ycrdml:
has anyone successful unpack-and-repack the nandroid boot.img without any changes? My boot.img is hang after the logo screen. mkbootimg without any problem :mad: please help
[G1 Android Development] erikwt:
Yes, this is unnecessary, and yes, I know for sure that it should be one '>'

:)
[G1 Android Development] thebalkanking:
Im currently using the newest Amon_Ra ROM,.took a copy of the boot image and edited init.rc and repacked, flashed, wont work..tried flashing from adb and thru fastboot

anyone successfully edited init.rc and flashed the new boot image?

all I added was a single line that mounts the ext2 on my sdcard on boot.
[G1 Android Development] chertykov:
I have a problem with unpack and repack because mkbootimg require --base option for 32a.

Try to using "--base 0x19200000".

Also you can try to compile the dumpbootimg program and compare the output of the original boot.img and created by youself.

Especially, compare the 'kernel_addr' fields.
[G1 Android Development] thebalkanking:
I took a different approach, and did a how to on it,

http://xdaforums.com/showthread.php?t=575144
[G1 Android Development] sandis84:
There is some great info in this thread, big thanks!

However, I have run into a problem: When I follow these instructions with my G1, it works perfectly. But when I do it with my magic, it hangs at the splash screen. Still, it feels as if this should work for any ROM, no? Anyone else tried with a phone other then the G1? Since I am doing the same thing with both phones, what could possibly be wrong? ._.

edit: Just to clarify, I did not use the same ROM for both phones... but I got the ROMs from each phones with adb.
[G1 Android Development] bonesy:
my repacked boot.img just makes it goto boot then restart,go to boot then restart?