I have been attempting to apply a work around from tjayz thread for restoring recovery. In the CWD folder we are supposed to search for 5) Navigate to clockworkmod/download/download.clockworkmod.com/recoveries/
There you will see some two files - recovery-clockwork-4.0.0.4-p7100.img and recovery-clockwork-4.0.0.3-p7100.img
I only see files with names like -2110140792 and -21108160.
Does anyone know if you can rename these files as described in his post?
Thanks
Please use the Q&A Forum for questions Thanks
Moving to Q&A
I tried to experiment with Cyanogen nightlies, but unfortunately it didn't end so well. I have used ODIN to start to restore my tablet, and I have the default rom that came with my Galaxy Tab 10.1 (wifi).
My problem however is that I don't have that zip file on my tablet and without the ability to boot it and push the file onto it, how do I flash it? I can't use clockwork, but is there a way in which I can use ODIN to push the zip file?
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
I took it from the telegram group, and I'm just posting it here.
Made for Android 11, if you use it on android 12 you will have many unexpected bugs.
Download
Important note: I didn't make this twrp, I just took it from the group and posted it here, if you and the created please create a more appropriate post here on xda and I'll delete this one.
Hi,
I changed the tag from Development to Guide, because Development tag is only for original developer (as you are the developer and you are posting it yourself).
Thanks.
Hello. I ported another twrp.
There is a bug. When restoring userdata, the system does not boot
These are the twrp sources from the telegram https://github.com/pjgowtham/recove...mmit/48560f736d92610fbc299a7d86f3f731496f9b42
And these sources are from the ported twrp that I posted
GitHub - TeamWin/android_device_oneplus_lemonadep
Contribute to TeamWin/android_device_oneplus_lemonadep development by creating an account on GitHub.
github.com
AllexBast said:
Hello. I ported another twrp.
There is a bug. When restoring userdata, the system does not boot
Click to expand...
Click to collapse
this backup bug is common, but does everything else work?
SrCDA said:
this backup bug is common, but does everything else work?
Click to expand...
Click to collapse
I solved the problem with userdata, but did not solve it. Probably you need to collect twrp from source. I added system_root symlinks to twrp, they were in the stock boot.img. You can mount all partitions in twrp that I added and see all files. They are displayed correctly.
Partition backup and restore is also correct except for userdata.
system, system_ext,product, vendor is not restored backup. write protection.
The transition between firmware can be done by restoring the super.img backup with a subsequent wipe. So I switched from Indian firmware to Kenyan
Do not try to lock the bootloader, the consequences can be irreversible
These are the latest versions of TWRP ports
You can additionally flash sections with images
system
system_ext
vendor
product
my_region - to remove programs
I can’t flash gsi.img through system_root yet because of the write protection of the partitions that I listed earlier
AllexBast said:
These are the latest versions of TWRP ports
You can additionally flash sections with images
system
system_ext
vendor
product
my_region - to remove programs
I can’t flash gsi.img through system_root yet because of the write protection of the partitions that I listed earlier
Click to expand...
Click to collapse
Allex why don't you create a post, here more detailed, and always updating and with changelogs?
SrCDA said:
Allex why don't you create a post, here more detailed, and always updating and with changelogs?
Click to expand...
Click to collapse
I won't do porting anymore. These were the latest versions. Who will collect from the source, he will lay out.
This is a ported twrp for rui3 india. It works only after the first installation of rui3. As soon as we format the data section, the section will be inaccessible.
As it turned out, with the help of TWRP, you can flash any OTA firmware, regardless of the region.
For a clean installation, flash the firmware into the slot where the system is and make the date format
To update, flash the firmware into the opposite slot where the system is without wipes and date format
How do I use the twrp i can't even access bootloader
And can anyone give me scatter file for realme 9se
How to root this device?
SrCDA said:
I took it from the telegram group, and I'm just posting it here.
Made for Android 11, if you use it on android 12 you will have many unexpected bugs.
Download
Important note: I didn't make this twrp, I just took it from the group and posted it here, if you and the created please create a more appropriate post here on xda and I'll delete this one.
Click to expand...
Click to collapse
Can anyone please tell me how to unlock bootloader of this phone??
Search telegram for realme 9 5g se. We found a way to unlock the bootloader of the Chinese and Indian versions of rmx3461 on 4pda
I just tried to add variables on Android /etc/mkshrc file but I get an error:
Read-only file system
Click to expand...
Click to collapse
Further, I have tried to use adb remount, but it says inaccessible or not found.
I tried to use the following:
mount -o remount,rw /
Click to expand...
Click to collapse
But it says '/dev/block/dm-10' not user mountable in fstab.
Phone is Pixel 6
xracerx123 said:
I just tried to add variables on Android /etc/mkshrc file but I get an error:
Further, I have tried to use adb remount, but it says inaccessible or not found.
I tried to use the following:
But it says '/dev/block/dm-10' not user mountable in fstab.
Phone is Pixel 6
Click to expand...
Click to collapse
Hello and good morning, @xracerx123
Prior to your next posting please read the guidances that are stuck on top of every forum like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
and the others. I've moved your thread to Android Q&A.
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
what was your search result for Pixel 6 mount rw Read-only file system?
https://twitter.com/i/web/status/1170404631865778177
https://blog.esper.io/android-dessert-bites-25-erofs-in-android-13-47987123
Hi everyone, I hope you're doing great
So, I'm currently trying to debloat some XOS ROMs which is Infinix's official firmware.
I have a problem repacking product.img since it doesn't have file_contexts which is required by the tools that repack .img files
IJoseph23 said:
Hi everyone, I hope you're doing great
So, I'm currently trying to debloat some XOS ROMs which is Infinix's official firmware.
I have a problem repacking product.img since it doesn't have file_contexts which is required by the tools that repack .img files
Click to expand...
Click to collapse
Hello and good afternoon, @IJoseph23
Welcome to XDA! I hope you'll always get the support you require.
However, prior to your next posting please read the guidances that are stuck on top of every forum like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
and the others. I've moved your thread to Android Q&A.
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
these kind of img files are partition images of linux file systems, sometimes sparsed with simg2img to reduce file size.
usually, partition images can mounted in linux only, same as partitions. windows is not capable of mounting linux file systems natively.
"extracting" linux images on windows is just some nasty hack and not intended for "repacking", because windows file system (NTFS) cannot handle linux file names and its metadata (like permissions, uid/gid, secontext)
the proper way is to mount (EXT4) partition image on linux, delete files, and unmount it.
additionally it might need img2simg/simg2img (not for dynamic partitions on super partition)