Related
Requirements:
1. Android 2.1
2. Root privileges
3. Compare version information in post #4
Note: This replaces framework-res.apk, i.e. will remove all previously installed themes.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Installation:
1. Unrar archive.
2. Copy extracted files to /sdcard, and
3. In command prompt:
a) adb shell
b) su
c) remount /system partition as read-write (mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system)
d) replace framework.jar (busybox cp /sdcard/framework.jar /system/framework/framework.jar)
e) replace android.policy.jar (busybox cp /sdcard/android.policy.jar /system/framework/android.policy.jar)
f) replace framework-res.apk (busybox cp /sdcard/framework-res.apk /system/framework/framework-res.apk)
Credits:
MrRusch
untermensch
[20/11/2010]Bugs fixed
[22/11/2010]Added Reboot + Battery Only
[01/12/2010]Fixed Org. Framework + Reboot
**Guys If u like this Mod thank me by donating me .**
shivenjuneja said:
Requirements:
1. Android 2.1
2. Root privileges
3. Compare version information in post #4
Note: This replaces framework-res.apk, i.e. will remove all previously installed themes.
Installation:
1. Unrar archive.
2. Copy extracted files to /sdcard, and
3. In command prompt:
a) adbshell
b) su
c) remount /system partition as read-write (mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system)
d) replace framework.jar (busybox cp /sdcard/framework.jar /system/framework/framework.jar)
e) replace android.policy.jar (busybox cp /sdcard/android.policy.jar /system/framework/android.policy.jar)
f) replace framework-res.apk (busybox cp /sdcard/framework-res.apk /system/framework/framework-res.apk)
Credits:
MrRusch
untermensch
Click to expand...
Click to collapse
HI shivenjuneja
What clock widget are you using?
beautiful widgets
shivenjuneja said:
beautiful widgets
Click to expand...
Click to collapse
Thank you
Hi. can you do this for the mini, not the pro?
thanks
it is for x10 mini & mini pro bt i have tested on x10 mini pro thats y m sure.... u can try on your mini if it is not working i'll make 1 for mini..... and ya dnt forget to backup ur original apps.....
ok thanks. i will give it a try and will lwt you know! cheers m8
Can I perform the operation of replacing the three files through "Root Explorer"? If yes, then what permissions shall I have to give all the three files before copying them to /system/framework? Is it "644"?
if u wanna do with root explorer do in the same order as given in the post 1 .... 1st framework.jar,2nd android.policy.jar,3rd framework-res.apk permissions are same as before...
i like this mod quite a bit
If I only want to get the reboot function, do I just replace the 2 files below?
/system/framework/framework.jar
/system/framework/android.policy.jar
This is really cool!
Can you tell me which XML files i have to edit/replace in framework-res to get the reboot option in my own theme?
we have to edit framework-res,framework,android.policy to get it into our theme
@ strykme no u have to replace all the things ..... if u dnt want my firmware you can download the original 1 attached in the downloads in 1st post.....
I really dony understand this. I have x10 mini pro 2.1 rooted, have installed lots of other stuff, app2sd, market patch etc.
But when doing the last
busybox cp /sdcard/framework-res.apk /system/framework/framework-res.apk
The phone restarts and dont want to boot anymore.
Have to restore with SEUS
What is going wrong here?
people who dont know how to replace framework with adb use this methode http://forum.xda-developers.com/showthread.php?t=837470
this is the safe methode and easy one
u have to wait more after the copy of new framework and android.policy then the normal boot....and when u boot do u see the boot animation??
it would be really nice if you would give us some instructions how to add the reboot option by ourself
I just installed the black HTC Theme by Draco and dont want to change but the reboot option would be nice
u can add my theme @My Theme
okey thanks to the link i got it installed.
permissons was not set now it boots and looking good.
But bot the shutdown and reboot button reboots. i cant turn off the phone it reboots no matter what i do.
Update: And the one with original framework does not show the menu at all it just reboots
This is a custom recovery for Xperia X10 based on ClockworkMod recovery source.
Credits and special thanks to Koush and everyone else involved in Cyanogenmod project!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How?
Press BACK button few times right after white SE label appears.
Controls:
Use VOLUME-UP and VOLUME-DOWN to browse, HOME to select, BACK to go back.
Features:
ADB root shell
Reboot
Install update.zip from SD Card
Factory reset (full wipe)
Wipe cache partition
Install custom zip
Backup and Restore
Partition tools
Mount/unmount partitions
Format partitions
Mount as USB Storage
Advanced options
Wipe Dalvik cache
Wipe battery stats
Fix permissions for apps (FC fix)
Installation:
A: Install the zip package via your current recovery
1. boot into recovery
2. connect with adb (adb shell)
3.
Code:
rm -r /sdcard
mkdir sdcard
chmod 777 sdcard
4. Now you will be able to see your SD Card and install fixed xRecovery
or
B: unpack all of the files to the relevant folders on your mobile
or
C: ask your ROM provider to include it
I am not responsible for any damage this software may cause to your phone.
Use it at your own risk!
Requirements:
1. 2.3 STOCK ROM
2. Phone must be rooted
3. Busybox from the market installed
Changelog:
0.3-release-GB: fixed Mass Storage mounting issues
0.3-release-GB: fixed SD Card mounting issues
0.3-release: unified version for all X10 variants and partition layouts
0.2-release: fixed installation issues for those with trashed mtd0 partition
0.1-release: xRecovery installer app - thanks zoz33!
0.0.1-beta: Initial release (for testers)
Download:
For now please use xRecovery 0.3: xRecovery_0.3_GBready.zip
snapshot_13-01-2011_xRecovery.tar.bz2 - source code
Q&A:
Q: How to use "boot custom ROM/kernel" option?
A: this is designed for ROM developers. This option executes a custom script (/system/kernel/boot.sh), which may be used for multiple puproses like:
- boot custom kernel
- boot custom ROM from SD Card
- dual-boot
- etc
Q: can you give an example?
A: Sure. Here's the simple boot.sh script to boot the custom kernel:
Code:
#!/sbin/sh
# zdzihu: boot custom kernel
insmod /system/kernel/splboot.ko
sync
cat /system/kernel/miniloader > /proc/splboot/image
cat /system/kernel/boot.img > /proc/splboot/boot_img
sleep 3
echo > /proc/splboot/boot
Q: What's edify scripting?
A: http://forum.xda-developers.com/showthread.php?t=936175
Q: Will it work with X8/X10mini/X100/T1000?
A: Yes and no. Yes, because it's compiled in compatibility mode (armv6).
But not this particular release. The init files must be changed by X8/X10mini/X100/T1000 devs first. Please check in the relevant threads.
you are a machine sir!!
Zdzihu and Jerpelea will go down in history as Gods of the X10
Thanks so much guys!!!!
You are the greatest!
Trying this out NOW!
thanks you
Thanks a lot for your efforts!
Which update.zip could we applied with this Recovery mode ? Eclair or Froyo custom Rom ?
chandyperry said:
Thanks a lot for your efforts!
Which update.zip could we applied with this Recovery mode ? Eclair or Froyo custom Rom ?
Click to expand...
Click to collapse
Wondering the exact same thing....
Nice work and congrats.
Looks hot, NO offence, but will wait until v0.1 is out. Cause 0.0.1 gives me a little worries xD
chandyperry said:
Which update.zip could we applied with this Recovery mode ? Eclair or Froyo custom Rom ?
Click to expand...
Click to collapse
It will be announced. For now, we don't have such update.zip ready.
assangflexx said:
Looks hot, NO offence, but will wait until v0.1 is out. Cause 0.0.1 gives me a little worries xD
Click to expand...
Click to collapse
As soon as it's tested by more users it will be 0.1
Can anyone confirm installation process works? I did it on a clean system but my mtd0 partition was already modified.
Cheers!
Great hope to see the bootloader Crack asap we will enjoy more X10
Thanks Zdzihu & Jerpelea for your fantastic job
Testing (nandroid?) backup now.
works well.Thanks dude.Good work buddy
Great job.
You're the best.
Thanks to J & Z the X10 is going back to track!!!! I'll give a try once I'm out of office...
Cheers
Sent from my X10i using XDA App
OMFG does this mean what i think it means ????
Another step closer to that golden path ?
HunteronX said:
Testing (nandroid?) backup now.
Click to expand...
Click to collapse
Great job!!!
I keep pressing F5 to read news about the nandroid backup!!
Made a backup, so I'm going to restore it now.
Sorry it's taking so long - didn't have enough space (took up about 562MB for me).
you're simply the best!!great job!i'll try as soon as i get back home from work
Seems to create backups fine.... haven't tested a restore yet
apk manager (backup, install, delete apks on phone )--- link: soon
custom boot image toolkit
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
azuzu kitchen --- link: soon
nandroid2pc ( xrecovery backup copier / unpacker to pc) --- link: soon
aZuZu amend syntax update-script to edify syntax updater-script converter
RamDisk Packer for Windows
Small Library Dependency Scanner - Alpha
Direct SIN & YAFFS UnPacker
Old version of SIN2IMG UnPacker
how to use this?
you place init files in some folder for example ramdisk
then
aSmallPacker ramdisk.tar [folder name]
and you will get packed init files in ramdisk.tar with linux perms as normal user.
it is for users not having linux and wanna normal ramdisk.
Thanks mate, my linux drive got damaged, and I was searching a tool like this!, you really saved my ass
EDIT: Wrong file?, can't unzip
EDIT2: Forget it unzip with 7zip
EDIT3: Made a little .bat to make it easier download here
i've got this..please see my attach...is it i'm wrong?. i allready have ramdisk folder(include all thing from extracting ramdisk.tar) in the azuzu small packer folder..
sorry if i asking this cuz i'm noob
cruizz said:
i've got this..please see my attach...is it i'm wrong?. i allready have ramdisk folder in the azuzu small packer folder..
sorry if i asking this cuz i'm noob
Click to expand...
Click to collapse
Is not aSmallPacker [forder name] ramdisk.tar
it's aSmallPacker ramdisk.tar [forder name]
Also i made a .bat to make it easier for noobs, you can download post #4
i wanna ask bout how to add the ramdisk into system after we've moded and pack it?thanks before
cruizz said:
i wanna ask bout how to add the ramdisk into system after we've moded and pack it?thanks before
Click to expand...
Click to collapse
remount system rw and copy ramdisk.tar in /system/bin
thanks for the fast response mate ...what i mean is the set permission on it
cruizz said:
thanks for the fast response mate ...what i mean is the set permission on it
Click to expand...
Click to collapse
i use chmod 0755 w/o any problems
updated / fixed
nice mate . wondering if those tools repackage into one tool...your tools is very helpfull
RAMDisk Tool Final Added. Enjoy!
new version of custom boot image toolkit is up!
minor fixes ...
added image to android logo & android logo to image ( external tools ) ( cygwin again! god damn! )
working on new ramdisk handle procedure ... soon will be fixed
thanks DooMLoRD for finding tools
Can't unpack system.sin from WT19i_4.0.1.A.0.283_(1254-1854).ftf.
In cmd everything is ok, but after unpacking winrar can't read .img file.
.: SID :. said:
Can't unpack system.sin from WT19i_4.0.1.A.0.283_(1254-1854).ftf.
In cmd everything is ok, but after unpacking winrar can't read .img file.
Click to expand...
Click to collapse
did you use upgraded version from today or older one?
With Direct SIN & YAFFS UnPacker everything works fine! Grand merci!
hi...
how do u cpio.gz the ramdisk?
I get the 'afct is nt recognised as internel or external comand, operable program or batch file'
How do I .gz the ramdisk folder?
hi azuzu and thx but how to use custom boot image toolkit is ther any tuto ??
thx in advance
Not works the download links the firs post.....
Hi,
here comes Recovery for Play of Team FreeXperia.
Download here: (Beta1 - Update 20.06.2011 - 18:28h GMT+1)
http://www.multiupload.com/VC3JRZ74H0
Broken:
Cannot backup&restore boot partition (kernel related)
To test use this command:
fastboot boot recoveryPLAY.img
Button mapping: (thanks Logseman)
Back- Back
Home/Vol UP - Up
Menu/Vol DOWN - Down
Search - OK
Please DO NOT FLASH! This recovery is designed to work just as recovery, if you flash it to your device it will NOT boot system anymore!
Please test and report functions. If there are errors please include EXACT outpot of errormessage.
Thanks to Blagus for his Xperia Play Kernel!
To gain root on every ROM (Stock ones too) just flash the attached RootXperia.zip via Recovery
Regards
Bin4ry & Team FreeXperia
I assume we need to install the custom kernel first?
No! You have NOT to install custom kernel to use this.
Just issue the command i wrote on your windows console. Then phone boots into recovery!
Regards
Logseman said:
I assume we need to install the custom kernel first?
Click to expand...
Click to collapse
The recovery image is structured exatcly as boot.img, with the difference in executable files - regular boot.img boots Android system from /system partition, while recovery boots into... well, recovery
So, since it's structured just as boot.img, you have to pack kernel inside as well. That's where, in this case mine, zImage comes in handy instead of unpacking SE's special boot.img structure, it was easier to take zImage from standard boot.img.
ive just tried it now, boots into CWM fine, im going to try a nandroid and report back
It looks weird in this DDMS capture, but in the phone it looks all right (black background, orange text). I've had no error messages of any kind.
Button mapping:
Back- Back
Home/Vol UP - Up
Menu/Vol DOWN - Down
Search/Power - OK
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This capture looks funny
But important is how it looks on device. I doubt that ddms cannot capture 32bit framebuffers
Regards
Bin4ry
Ok, i did a nandroid, rebooted, booted back into bootloader and fastboot erased /system/, pushed the recovery back and tried to restore /system/ but i get the error " Error formatting system " i also get the same error in the mounts & storage menu can i flash the nandroid image from fastboot?
*edit* no it wont let me flash it from fastboot, it tells me the image is too large lol probably because i moved some widgets and lwp's to /system/, no worries i'll flash the image in the development section.
Recovery booted fine, did a nandroid backup worked fine, not sure i want to follow suit and delete a load of stuff and try restore. will wait to see what androhero and bin4ry can figure out first with andro's issue
mehmehmen said:
Recovery booted fine, did a nandroid backup worked fine, not sure i want to follow suit and delete a load of stuff and try restore. will wait to see what androhero and bin4ry can figure out first with andro's issue
Click to expand...
Click to collapse
try and clear cache, see if you get the same error? if the action works it wont matter if cache gets formatted
I hope you can help me figure this out, because right now I am astonished at least.
I've been poking around with ClockworkMod, and getting a couple of errors. I know there is an error reporting utility inside CWM, "Report Error" in "advanced" so I made use of it. However, the log would save to "/sdcard/clockworkmod/recovery.log".
Since I'm using the custom kernel, I'm not able to use the sdcard as it seems to be improperly mounted. It shows as mounted in CWM, I unmounted it and remounted it again to no avail... though it can be mounted on the computer properly.
However, that's not the point. I thought I'd do a search on "recovery" with Root Explorer, wanting to find the Recovery.log somewhere else. And boy, did I find it. I found the two recovery logs I saved inside the folder /data/system/dropbox . I happen to have DB installed in my Android. But not only that, I found my kmsg logs, and boot logs, registered there as well.
Hereby I attach the two recovery logs. Does it make sense that these kinds of logs are saved in such a folder? Am I worrying unnecessarily?
this is one of the reaons why google take root access off us in the first place isnt it?
Thanks for the logs.Dunno why they was stored in DB folder
@AndroHero:
Yes just restore the img files from backup via fastboot flash.
Regards
Bin4ry
where excatly do i put the play recovery.img?
crispyduckling said:
where excatly do i put the play recovery.img?
Click to expand...
Click to collapse
just put it in the same folder as fastboot.exe
When backing up the progress bar doesn't work and it can take some minutes, so just be patient when doing a back-up.
Are their any specific options you like us to play with?
AndroHero said:
just put it in the same folder as fastboot.exe
Click to expand...
Click to collapse
cheers mate
okay so i formatted the cache and it comes back
Cach wipe complete.
E:Can't Mount /cache/recovery/log
E:Can't Open /cache/recovery/log
E:Cant mount /cache/recovery/last_log
E:Cant Open /cache/recovery/last_log
it wiped cache ok but is this error something i need to be worried about in away before attempt wipe and restore of system with my nandroid?
Do not bother trying to restore a nandroid backup: the /system partition won't get formatted and the operation will be cancelled.
The back-up made a cache.img, data.img, system.img and a .android_secure.img
I assume I can flash the system.img with fastboot like I used to do when rooting through fastboot? Could safe me the bloatware removal trouble after I get into a bootloop (yet again ).
Hello,
I need help for TWRP on my Samsung Galaxy A20e. My device is rooted for a while and TWRP is newly installed. But the problem is when I try to backup something, I got an error while creating the folder TWRP with the mension of operation not permited. I also have a problem when I touch the Install button, I see a list of folders with random generated names like in the photo. Can anybody help me to solve this problem? I can give more informations if needed.
Thanks for helping !
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
your device is encrypted. you must disable encryption and factory reset device in order to become TWRP functional, as TWRP cannot handle samsung encryption. or use other backup method such as Migrate.
Ok I tried what you wrote but it works only while I don't boot my device after factory reset it. If it happens, the encryption enables automatically and I can't backup anymore. Do you have a solution for this ?
you must disable encryption in /vendor/etc/fstab.samsungexynos7884
(can maybe done with zip)
https://forum.xda-developers.com/t/recovery-unofficial-twrp-3-4-0-0-for-galaxy-a20e-a202f.4141767
How am I supposed to do that ? I tried everything with this file. There is a mount option for /data "filencryption=ice". I tried to delete this with a file editor in the stock system but when I reboot my phone it reappears. When I this this in TWRP the system can't boot.
https://forum.xda-developers.com/t/recovery-unofficial-twrp-3-4-0-0-for-galaxy-a20e-a202f.4141767
Click to expand...
Click to collapse
This link cannot help me because it is just a tutorial and when I do exactly like in i get the same results. I don't unerstand why my phone has this problem and not others. If you have other ideas i would be good
there is download for Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip flashable zip which is supposed to patch fstab (last step in tutorial). you must mount system/vendor writeable (checkbox in TWRP)
aIecxs said:
there is download for Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip flashable zip which is supposed to patch fstab (last step in tutorial). you must mount system/vendor writeable (checkbox in TWRP)
Click to expand...
Click to collapse
I tried installing this zip file from the SD card but it didn't boot (locked on samsung logo) so I did a factory reset with TWRP and after configuring, I got the same results than before.
- in TWRP double check your vendor partition is separate partition (or directory inside system partition)
- in TWRP terminal make sure partition is mounted rw
Code:
mount /system w
mount /vendor w
mount
- install Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
- in TWRP terminal double check fstab.samsungexynos7884 file fileencryption= flag is gone
Code:
cat /vendor/etc/fstab.*
- in TWRP - wipe - format data - type yes
Thanks for the instructions. It works perfectly ! I am just an idiot because I didn't wipe /data in TWRP but I just swiped to factory reset. Thank you a lot !
maybe I was misleading you with factory reset. might be that TWRP factory reset just behaves like simple wipe, where only files are deleted excluding /data/media
formatting whole partition is required for removing encryption.
edit: Please note if you're interested in undo the patch, you must restore vendor partition. you can of course add the fileencryption= flag back with text editor yourself. However that requires linux line endings (LF) so you can't use Windows text editor (CRLF) that's why you should use Notepad++ and enable view for invisible chars with (π) button. Do not simply copy file back into /vendor you will lose file permissions. Do not use sed you still would lose secontext. only copy content of file into old existing file like this.
Code:
cat /tmp/fstab.new > /vendor/etc/fstab.samsungexynos7884
Btw if you're running custom ROM (such as LineageOS) it's possible to break samsung encryption and use AOSP encryption as fallback by deleting keystore.mdfpp.so and keystore.msm8953.so from /vendor/lib/hw. This way you can use TWRP on encrypted device.