Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Nexus 7 (2013) - flo
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Click to expand...
Click to collapse
Will there be a version for deb also?
I want to test it but with the flo version this might be a bad idea while using the LTE version of the Nexus 7,
But thanks anyway for your CWM version here - I used it with N7000 and therefore didn't use TWRP.
Until now it was different here...
Thanks
Flo version is booting which is a good sign. However, you get 2 errors when you try to create a Nandroid Backup:
E:FAILED to find partition size `/recovery`
E:FAILED to find partition size `/boot`
Edit: 1 Nandroid Backup created, going to test this soon and report more Bugs after some testing.
Gorgtech said:
Flo version is booting which is a good sign. However, you get 2 errors when you try to create a Nandroid Backup:
E:FAILED to find partition size `/recovery`
E:FAILED to find partition size `/boot`
Click to expand...
Click to collapse
They are cosmetic bugs
Please provide a log on that error
I added a detection mode that seems not working on flo.
To fix it the hard way, provide me from adb shell
Code:
cat /proc/partitions
ls -l /dev/block/platform/msm_sdcc.1/by-name
In recovery, it normally tries to resolve the links when i do not know the real mmcblk name for partitions. So, in addition to above adb shell commands, if you provide a log, I can see why links are not resolved on this device
For 4.3 roms, you must enable selinux context backup/restore in misc nandroid settings by the way
Here are two screenshots: https://www.dropbox.com/sh/roo85slxi7h9l69/kjBrLNIJmC
Phil3759 said:
They are cosmetic bugs
Please provide a log on that error
I added a detection mode that seems not working on flo.
To fix it the hard way, provide me from adb shell
Code:
cat /proc/partitions
ls -l /dev/block/platform/msm_sdcc.1/by-name
In recovery, it normally tries to resolve the links when i do not know the real mmcblk name for partitions. So, in addition to above adb shell commands, if you provide a log, I can see why links are not resolved on this device
For 4.3 roms, you must enable selinux context backup/restore in misc nandroid settings by the way
Click to expand...
Click to collapse
this looks sweet. Does it have multiboot ability?
Gorgtech said:
Here are two screenshots: https://www.dropbox.com/sh/roo85slxi7h9l69/kjBrLNIJmC
Click to expand...
Click to collapse
Thank you a lot
But I really need a log. Just go into "Custom backup and restore" menu, select boot and recovery only, hit backup
In backup folder, you should have a recovery.log file. Zip and attach here
Else, after the backup, "Advanced Menu" and select report error
I need to know why the readlink function is not doing its job to get what you see with ls -l command
I´ve included the log file to the dropbox folder Just to make sure it doesn´t get lost, also as an attachment.
Phil3759 said:
Thank you a lot
But I really need a log. Just go into "Custom backup and restore" menu, select boot and recovery only, hit backup
In backup folder, you should have a recovery.log file. Zip and attach here
Else, after the backup, "Advanced Menu" and select report error
I need to know why the readlink function is not doing its job to get what you see with ls -l command
Click to expand...
Click to collapse
Gorgtech said:
I´ve included the log file to the dropbox folder Just to make sure it doesn´t get lost, also as an attachment.
Click to expand...
Click to collapse
Thank you a lot
I am fixing the silly bug I did
Will release an update when back to home
v5.18.4
http://d-h.st/users/philz_touch/?fld_id=26583#files
This fixes the boot/recovery partition size check
That bug had no effect on backup/restore. It is just for the progress bar accuracy
Phil3759 said:
v5.18.4
http://d-h.st/users/philz_touch/?fld_id=26583#files
This fixes the boot/recovery partition size check
That bug had no effect on backup/restore. It is just for the progress bar accuracy
Click to expand...
Click to collapse
This version is asking me to fix root when i reboot...every time
joeyddr said:
This version is asking me to fix root when i reboot...every time
Click to expand...
Click to collapse
Nothing to do with CWM
Only change from previous is fix to detect size of boot and recovery on backup
Is that fixed?
Phil3759 said:
Nothing to do with CWM
Only change from previous is fix to detect size of boot and recovery on backup
Is that fixed?
Click to expand...
Click to collapse
that seems to be and the version before din't ask to fix root.
joeyddr said:
that seems to be and the version before din't ask to fix root.
Click to expand...
Click to collapse
say yes and it will be happy probably
Or see if you updated your ROM SU version
Phil3759 said:
say yes and it will be happy probably
Or see if you updated your ROM SU version
Click to expand...
Click to collapse
I reflashed the supersu 1.65 and it went away thanks.
Only 12 people thanked for such a nice recovery?
Maybe because there is no (install)information whatsoever?
Sent from my GT-I9505 using xda app-developers app
Barthlon said:
Maybe because there is no (install)information whatsoever?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Should install info be in a dev thread?
Phil3759 said:
Should install info be in a dev thread?
Click to expand...
Click to collapse
Quoting your own posts there
How to Install
This will depend on your device. Please look first for help in your device specific thread.
Provided instructions here ARE NOT VALID for all phone
Click to expand...
Click to collapse
So the answer must be "yes".
ThaiDai said:
Quoting your own posts there
So the answer must be "yes".
Click to expand...
Click to collapse
No
I meant forums, not thread. Will edit it.
People should look, into their device forum, FAQ and General. Dev threads are not meant to be a how to flash tut
If someone doesn't know how to flash a recovery, he has no reason to lurk here. He should start in other general/faq forums
Related
Sorry if it is a silly question. I am new to installing new ROM and flashing stuff. I have come across the thread on TWRP recovery where it says that to install it, we have to flash it from other recoveries(i.e. CWM or AmonRA). What if I have none of these? Should I install one of them at first place and then proceed to flash TWRP or, there is some other way out? Thanks.
flash_image, Flash Image GUI, fastboot, another recovery, LGMDP.exe for unrooted phones. Read the sticky threads.
Sent from my LG-P500 using XDA App
dr.notor said:
flash_image, Flash Image GUI, fastboot, another recovery, LGMDP.exe for unrooted phones. Read the sticky threads.
Sent from my LG-P500 using XDA App
Click to expand...
Click to collapse
Thanks Sir for your quick response. Will go through it.....
developer++ said:
Sorry if it is a silly question. I am new to installing new ROM and flashing stuff. I have come across the thread on TWRP recovery where it says that to install it, we have to flash it from other recoveries(i.e. CWM or AmonRA). What if I have none of these? Should I install one of them at first place and then proceed to flash TWRP or, there is some other way out? Thanks.
Click to expand...
Click to collapse
root using gingerbreak,download latest rom manger and install clockwork recovery from there - if want to change reovery to twrp just flash from clockowrk recovery after it gets installed
this may help u http://forum.xda-developers.com/showthread.php?t=1038338
make sure usb debugging is enabled while installing custom recovery from rom manger ,make sure u download the latest rom manger from market
welcome to world of custom rom
shhbz said:
root using gingerbreak,download latest rom manger and install clockwork recovery from there - if want to change reovery to twrp just flash from clockowrk recovery after it gets installed
this may help u http://forum.xda-developers.com/showthread.php?t=1038338
make sure usb debugging is enabled while installing custom recovery from rom manger ,make sure u download the latest rom manger from market
welcome to world of custom rom
Click to expand...
Click to collapse
Thanks for the info. Was really a nice descriptive guide for newbies.
One more question. I am on stock froyo 2.2.2 and have flashed TWRP recovery which creates partition in ext4 only. Now I have also flashed Darktremor A2SD which fails to move dalvik to sd card which I assume is because of the ext4 partition that is not recognised by the stock rom. Am I correct with my assumption?
Is flashing another rom is the only way out? If yes, how should I move the existing apps from my stock rom to the new row. Thanks.
Code:
cat /proc/filesystems
will tell you what your kernel supports.
shhbz said:
root using gingerbreak,download latest rom manger and install clockwork recovery from there - if want to change reovery to twrp just flash from clockowrk recovery after it gets installed
this may help u http://forum.xda-developers.com/showthread.php?t=1038338
make sure usb debugging is enabled while installing custom recovery from rom manger ,make sure u download the latest rom manger from market
welcome to world of custom rom
Click to expand...
Click to collapse
This method is not quite OK for me. Did anyone try to actually install that recovery using "Phone Terminal Emulator method"?
I mean this.
adb shell
su (it will ask for root permission in your phone screen just allow)
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 755 /system/bin/flash_image
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak (you will get an error just proceed)
mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
flash_image recovery /sdcard/LGp500-recovery-v12.img (note just name the blue marked as the same as your custom recovery name and should end with .img)
Click to expand...
Click to collapse
Martin "skunk" Rotter said:
This method is not quite OK for me. Did anyone try to actually install that recovery using "Phone Terminal Emulator method"?
I mean this.
Click to expand...
Click to collapse
Click the link in my signature. There are 3 perfectly working methods to flash recovery. Dunno what the problem really is.
Well, if course i know these methods and i used it many times. Maybe author of this (extremely interesting and incredibly looking) recovery could mention these methods in his thread. I think that only "flash this ZIP via your CWM"-like tutorial is not enough for some users and then they are confused -> and then new threads like this are created.
Martin "skunk" Rotter said:
Well, if course i know these methods and i used it many times. Maybe author of this (extremely interesting and incredibly looking) recovery could mention these methods in his thread. I think that only "flash this ZIP via your CWM"-like tutorial is not enough for some users and then they are confused -> and then new threads like this are created.
Click to expand...
Click to collapse
That thread is a development thread for that particular recovery. There is absolutely no difference when flashing this or another recovery (like AmonRa or CWM.) So, there are enough howtos here (mentioned in the sticky thread that noone reads) to cover flashing recovery.
Development section is for development, not for repeating redundant stuff over and over again.
I get it, but obvíously developer++ doesn't.
Martin "skunk" Rotter said:
This method is not quite OK for me. Did anyone try to actually install that recovery using "Phone Terminal Emulator method"?
I mean this.
Click to expand...
Click to collapse
well that an outdated mwthod and a lengthy procedure so why not use rom manger and get the latest clockwork recovery and easily shift to whichever recovery u are wiling to use
shhbz said:
well that an outdated mwthod and a lengthy procedure so why not use rom manger and get the latest clockwork recovery and easily shift to whichever recovery u are wiling to use
Click to expand...
Click to collapse
There is nothing outdated about the method. And why not use ROM Manager? Because ROM Manager absolutely lacks any sanity checks when flashing recovery. It will happily download incomplete *.img (happens a LOT esp. on 2G/3G) and flash it, making your phone stuck with fastboot.
I have mentioned numerous times that they should distribute a signed ZIP with recovery contained and check the ZIP before flashing. (Even the ZIP format itself has a CRC checks built in if you are too lazy to bother with manifests.)
There are tons of complaints from people all over the board about ROM Manager half-bricking their phones, I am really stunned by the bad design of the feature and lack of action to fix it.
shhbz said:
well that an outdated mwthod and a lengthy procedure so why not use rom manger and get the latest clockwork recovery and easily shift to whichever recovery u are wiling to use
Click to expand...
Click to collapse
Well, but don't you see that problem?
get the latest clockwork recovery and easily shift to whichever recovery u are wiling to use
Click to expand...
Click to collapse
Why this? Some say usual recovery installation methods will work and you say to use this (weird) method. Then you can't wonder, why creator of this thread is confused.
dr.notor said:
There is nothing outdated about the method. And why not use ROM Manager? Because ROM Manager absolutely lacks any sanity checks when flashing recovery. It will happily download incomplete *.img (happens a LOT esp. on 2G/3G) and flash it, making your phone stuck with fastboot.
I have mentioned numerous times that they should distribute a signed ZIP with recovery contained and check the ZIP before flashing. (Even the ZIP format itself has a CRC checks built in if you are too lazy to bother with manifests.)
There are tons of complaints from people all over the board about ROM Manager half-bricking their phones, I am really stunned by the bad design of the feature and lack of action to fix it.
Click to expand...
Click to collapse
yes the problem was there of phone getting into fastboot mode ,but i beieve the problem was later solved and then it worked fine as many users dont follow instruction carefully which land them into probs.yes i do agree on ur internet connection part if that lacks than they need to use adb to get it done.
since,many users are not able to use adb and stuff just bcoz they cannot configure it properly.
so they have these option to do it the easiest way if they are not able to configure adb to work properly.
shhbz said:
yes the problem was there of phone getting into fastboot mode ,but i beieve the problem was later solved and then it worked fine as many users dont follow instruction carefully which land them into probs.yes i do agree on ur internet connection part if that lacks than they need to use adb to get it done.
Click to expand...
Click to collapse
I do not believe they ever changed the ROM Manager design in the way suggested. The problem is with lack of sanity checks, do not blame users for their sucky internet connection.
Martin "skunk" Rotter said:
Well, but don't you see that problem?
Why this? Some say usual recovery installation methods will work and you say to use this (weird) method. Then you can't wonder, why creator of this thread is confused.
Click to expand...
Click to collapse
It depends on the users choice what they choose as we started with thunderg recovery than came the clockwork method and now the twrp method.
there are various threads and discussion on the first two method .
go and read threads as i said is a matter of choice which way u want it to get it done.
so make ur choice in which u are comfortable and confident.
dr.notor said:
Code:
cat /proc/filesystems
will tell you what your kernel supports.
Click to expand...
Click to collapse
the above command gives me the following output:
Code:
cat /proc/filesystems
nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev tmpfs
nodev debugfs
nodev sockfs
nodev pipefs
nodev anon_inodefs
nodev rpc_pipefs
nodev inotifyfs
nodev devpts
ext3
ext2
nodev ramfs
vfat
nodev nfs
yaffs
yaffs2
as seen my kernel does not support ext4.
dr.notor said:
Click the link in my signature. There are 3 perfectly working methods to flash recovery. Dunno what the problem really is.
Click to expand...
Click to collapse
Yes, I have been following links from your signature. They are perfectly ok. But the situation I got into was that I flashed TWRP recovery and created a ext4 partition which was the only format supported by TWRP. Then I flashed Darktremor A2SD but it was unable to mount the ext4 partition as such was unable to move dalvik to sd.
Martin "skunk" Rotter said:
Well, if course i know these methods and i used it many times. Maybe author of this (extremely interesting and incredibly looking) recovery could mention these methods in his thread. I think that only "flash this ZIP via your CWM"-like tutorial is not enough for some users and then they are confused -> and then new threads like this are created.
Click to expand...
Click to collapse
Yes, I too think an additional info about the other ways to install recovery as stated by dr.notor would be very much helpful.
And as for creating new threads I sincerely apologize if I have a made a mistake here.
Flash the correct franco kernel, it supports ext4 just fine. (v1 versions are for CM7 6.6.x and stock(-based) GB ROMs only!)
Could someone please post a step by step on how to properly install the speedy Gonzales script for us less savvy people. Thanks in advance.
You have to be rooted with tenfars recovery and the init hack: http://forum.xda-developers.com/showthread.php?t=1223771
Download the .zip file that says flashable in the title, it located at the bottom of first post. Move it to sd card. This one: http://forum.xda-developers.com/attachment.php?attachmentid=704624&d=1314689490
Open the System Recovery app and select Recovery Mode (unsure plugged in).
Select choose zip from sd card. Navigate to the file and flash it.
What part is the issue, let me know where you have questions.
Ok I am rooted and have tenfars recovery. Do I still need the init hack installed or just go ahead and install new script through system recovery. Confused on first part.
Yes you need the init hack. Its the first link I posted. Its same thing. Download zip. Move to sd. Boot into recovery, flash. May be able to flash the speedy hack right after, but id reboot first just to make sure.
You need to go back into the /etc/init.d folder and delete the kickasskernel and S00tweaks once everything is successfully flashed.
One last question. I notice that there are 3 init.d hacks do you use all 3 or just one. That's the only think im not sure of.
Which ever one you want, but only one. Each is different and the description should describe that difference. I am on the first one. Battery saver or what ever its called.
So after I install the script using the flashable zip am I supposed to have the "zipalign-dataapp.log." in my /data file? Or is that only if you do it manually?
dust. said:
So after I install the script using the flashable zip am I supposed to have the "zipalign-dataapp.log." in my /data file? Or is that only if you do it manually?
Click to expand...
Click to collapse
That's what the instructions say in the original post for speedy.
You know what sucks is that the guy who made this got bashed so much he pulled the script and closed the thread...
This is supposed to be a community you ask and answer questions it gets to the point were people are afraid to ask anything without searching for 3-5 days for something i don't understand why people on these types of forums bash each others work so much its ridiculous...that sucks i feel really bad for the OP of this script he was just trying something and he got the crap kicked out of him....venting
im not gettintg the zipalign logfile he mentioned. hmmm
nitwit said:
im not gettintg the zipalign logfile he mentioned. hmmm
Click to expand...
Click to collapse
I didnt at first either, but I didnt follow directions proper and do the init.d thing first. after I did that I had the zip log thingy in /data
nitwit said:
im not gettintg the zipalign logfile he mentioned. hmmm
Click to expand...
Click to collapse
Same here.
Sandso9 said:
Same here.
Click to expand...
Click to collapse
Yeah you're not the first person to have this problem, it's because Naven's init hack uses the busybox applet run-parts which doesn't exist in all busybox releases. You definitely should have a zipalign log in /data.
I'll probably get flamed again for posting, but the following link is init-rehack, I created it for myself (original work by naven who discovered the hack!) when the initial hack from naven wasn't working.
http://www.sendspace.com/file/9g6ngz
Edit: Updated with new link.
Flash it in recovery and let me know if that works and you see the zipalign logs.
0vermind said:
Yeah you're not the first person to have this problem, it's because Naven's init hack uses the busybox applet run-parts which doesn't exist in all busybox releases. You definitely should have a zipalign log in /data.
I'll probably get flamed again for posting, but the following link is init-rehack, I created it for myself (original work by naven who discovered the hack!) when the initial hack from naven wasn't working.
http://www.sendspace.com/file/jmvpyf
Flash it in recovery and let me know if that works and you see the zipalign logs.
Click to expand...
Click to collapse
flash it over yours then? or before ?
Sandso9 said:
flash it over yours then?
Click to expand...
Click to collapse
Yeah. Let me know if it works or if it doesn't.
0vermind said:
Yeah. Let me know if it works or if it doesn't.
Click to expand...
Click to collapse
flashed this over yours and still no zip align log file in /data
Sandso9 said:
flashed this over yours and still no zip align log file in /data
Click to expand...
Click to collapse
Sorry, wrong link.
Blah blah blah blah, edit edit edit edit
http://www.sendspace.com/file/9g6ngz
Edit: Updated with new link.
Flashed the latest file and still no zipalign log in /data.
zetsumeikuro said:
Flashed the latest file and still no zipalign log in /data.
Click to expand...
Click to collapse
Lol same here
Sent from my OG Droid
Team Win Recovery Project 2.4, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s 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.
Phone look:
Tablet look:
CHANGELOG for 2.4.1.0:
-Fixed a problem with mkdosfs that formatted sdcards to 2GB
-Fixed handoff between vfat and exFAT on devices where blkid didn't detect vfat (fixes some issues with mounting sdcards)
-Fixed problems with changing working directory on MD5 creation/checking that may have prevented unmounting
-Backups will now store a copy of the backup log after the backup is completed (only if backup is successful)
CHANGELOG for 2.4.0.0:
-Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes (thanks to bigbiff)
-Support for exFAT formatted sdcards (also thanks to bigbiff)
-Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)
-Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running
-Added wipe cache and dalvik after ADB Sideload
-Replaced many system calls with their native C counterparts
-Fixed bugs in file manager where it would display an empty list after moving or deleting a folder
-Fixed AOSP recovery commands to run after decryption on encrypted devices
-Improvements for building TWRP in CM10.1
-Other minor bugfixes and improvements
NOTE: 2.4.0.0 is, as always, still compatible with your older backups!
CHANGELOG for 2.3.3.0:
-Fix renaming backups with a space in the name
-Add decrypt button to mount page if you cancel decryption during startup
-Added ignore blkid flag
-Fixed handling of MTD partitions during mount
-Fixed some keyboard mapping issues on 800x1280 layout
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Special thanks to toastcfh, the sexy, neckbearded, nice thighed, elite guy that he is, for helping to get TWRP working properly on the S3 Mini.
Reserved!
yayyyyyyyyyyyyyyyyyyyyy
AW: [RECOVERY] TWRP 2.4.1.0 touch recovery [2013-02-01]
Aaawwwwweeeeesssoommeeeeee!
Sent from my GT-I8190 using xda app-developers app
Oh yeah! Great work.
So will this work with other versions too? (Specifically the I8190L version )
And my flashable zip again.
Sv: [RECOVERY] TWRP 2.4.1.0 touch recovery [2013-02-01]
With goomanager I get "no recoveries were found for your device".
Maybe because I already done "dd",or isn't it on server yet?
Sent thru time and space from my s3mini.
tys0n said:
With goomanager I get "no recoveries were found for your device".
Maybe because I already done "dd",or isn't it on server yet?
Sent thru time and space from my s3mini.
Click to expand...
Click to collapse
Same with me. But through Rom manager there is also upgrade to recovery
Sent from my GT-I8190 using xda premium
AW: [RECOVERY] TWRP 2.4.1.0 touch recovery [2013-02-01]
Benzonat0r said:
And my flashable zip again.
Click to expand...
Click to collapse
I tried this zip.
You are the master!
ExtSd is found here.
All features works pretty cool.
Only the version inside must be upgraded.
Very good work.
Only one thing were so much fun,
Partition sd card..
Good evening
Sent from my GT-I8190 using xda app-developers app
mermigas said:
Same with me. But through Rom manager there is also upgrade to recovery
Sent from my GT-I8190 using xda premium
Click to expand...
Click to collapse
Yes, but with rom manager you won't find a recovery for our device because CWM in this forum isn't official build.
Not saying it's no good. xd.bx did a great job, it's just not official
AW: [RECOVERY] TWRP 2.4.1.0 touch recovery [2013-02-01]
In rom manager there are official cwm and twrp recoveries on ma phone.
There is listed as samsung g9190 golden.
Quiet interesting..
Sent from my GT-I8190 using xda app-developers app
Trykall8 said:
In rom manager there are official cwm and twrp recoveries on ma phone.
There is listed as samsung g9190 golden.
Quiet interesting..
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
Oh, I didn't know it was official CMW! Thats great!
Can you really install TWRP with rom manager?
Isn't it CWM touch?
No no, you got that all wrong.
First of all this is not CWM it's TWRP custom recovery.
You can't install it via ROM Manager but you can install it via GooManager.
Benzonat0r said:
No no, you got that all wrong.
First of all this is not CWM it's TWRP custom recovery.
You can't install it via ROM Manager but you can install it via GooManager.
Click to expand...
Click to collapse
Well the goomanager didn't find anything for my device, I mean didn't find no recoveries.
Sent from my GT-I8190 using Tapatalk 2
It's probably a bug, use my flashable zip.
Also does flashing this recovery increase the binary count?
Sent from my GT-I8190 using Tapatalk 2
If you flash it via CWM or via Terminal with dd if command then no, but if you flash it via Odin yes
And yes there's an official CWM recovery and also CWM touch recovery for our device.
For anyone that isn't able to have GooManager find a recovery for you, open up your /system/build.prop and find ro.product.name and give me that line.
Dees_Troy said:
For anyone that isn't able to have GooManager find a recovery for you, open up your /system/build.prop and find ro.product.name and give me that line.
Click to expand...
Click to collapse
ro.product.name=goldenxx
Hello, i think i made a big mistake, on my phone with root explorer i was unable to mount / and then i tried to mount /system into read only, i remember that i ticked "owner" "group" and "other" but only on read, and my phone just freezed and now the screen is on but it is black and the navigation buttons are on too, please help me
skip
Go to twrp, mount system, go-to inbuilt file manager and chmod 755 the system folder and reboot, or Dirty flash the firmware will do the job.
Next time, do nand-backup before perform sny changes to system. or would be better don't messed up with root partition.
R324D said:
Go to twrp, mount system, go-to inbuilt file manager and chmod 755 the system folder and reboot, or Dirty flash the firmware will do the job.
Next time, do nand-backup before perform sny changes to system. or would be better don't messed up with root partition.
Click to expand...
Click to collapse
You are sure it is going to work ?
Yakia said:
You are sure it is going to work ?
Click to expand...
Click to collapse
Lol
I don't know man, you could try. I'm not a magician...
Soooo little info you provided, I don't know what device you mentioned above? Rooted/unrooted? Custom rom/stock rom? Twrp installed/uninstalled? Almost zero info :laugh:
But basically, yes it'll work. Just do it..
R324D said:
Lol
I don't know man, you could try. I'm not a magician...
Soooo little info you provided, I don't know what device you mentioned above? Rooted/unrooted? Custom rom/stock rom? Twrp installed/uninstalled? Almost zero info :laugh:
But basically, yes it'll work. Just do it..
Click to expand...
Click to collapse
I actually have twrp installed and fully functionnal, but the phone won't boot on os, when i try to boot, it always shows me recovery, and i precise that in /system there is no file, its empty, i don't know why but when i go to storage info i see that the system partition takes 4gb why ? If in file explorer /system is empty, why system takes 4gb ? Maybe it's not really empty ? Anyway i just need help please
Yakia said:
I actually have twrp installed and fully functionnal, but the phone won't boot on os, when i try to boot, it always shows me recovery, and i precise that in /system there is no file, its empty, i don't know why but when i go to storage info i see that the system partition takes 4gb why ? If in file explorer /system is empty, why system takes 4gb ? Maybe it's not really empty ? Anyway i just need help please
Click to expand...
Click to collapse
I tried to help you here, but clearly you didn't read my previous comment.
Boot into TWRP (you said you have it installed), and you have to MOUNT SYSTEM first, or it'll just show you an empty folder without file.
R324D said:
I tried to help you here, but clearly you didn't read my previous comment.
Boot into TWRP (you said you have it installed), and you have to MOUNT SYSTEM first, or it'll just show you an empty folder without file.
Click to expand...
Click to collapse
Where do i mount system ? Sorry if i'm maybe annoying i just want to be sure that i will not fail
Yakia said:
Where do i mount system ? Sorry if i'm maybe annoying i just want to be sure that i will not fail
Click to expand...
Click to collapse
Just boot into twrp, you'll see mount menu as soon as you enter the twrp recovery. Enter mount and check system.
R324D said:
Just boot into twrp, you'll see mount menu as soon as you enter the twrp recovery. Enter mount and check system.
Click to expand...
Click to collapse
When i tick system, i have no "mount" button, i only have a "disable mtp" button, why ? I can give you screens if you want
Seeing there is no TWRP for the pixel 6 yet, was wondering if there was a way to backup my current stock rooted rom for I can flash other roms? Then flash back of I don't like it.
There's a twrp. You mind testing it for me?
enigma2446 said:
Seeing there is no TWRP for the pixel 6 yet, was wondering if there was a way to backup my current stock rooted rom for I can flash other roms? Then flash back of I don't like it.
Click to expand...
Click to collapse
An easy method of restoring to stock if you don't like a custom ROM is to use Google's recovery tool. Or you can use ADB as it has commands for backing up and - I think - restoring.
NonStickAtom785 said:
There's a twrp. You mind testing it for me?
Click to expand...
Click to collapse
Sure thanks for responding.
NonStickAtom785 said:
There's a twrp. You mind testing it for me?
Click to expand...
Click to collapse
I'm down for testing recovery for pixel 6.
NonStickAtom785 said:
There's a twrp. You mind testing it for me?
Click to expand...
Click to collapse
you have 2 users willing to twst
Flar2's AppDash works great if you have root for backing up apps and app data.
As for ROM, I haven't tried this yet, but seems quite promising:
GitHub - Magisk-Modules-Alt-Repo/backup: An android CLI partition backup tool without custom recoveries.
An android CLI partition backup tool without custom recoveries. - GitHub - Magisk-Modules-Alt-Repo/backup: An android CLI partition backup tool without custom recoveries.
github.com
@enigma2446 @shelbo The image is inside the zip archive. Tell me if anything is incorrectly working I haven't tested it yet
OK I'll give it a shot in a couple of hours and let you know
NonStickAtom785 said:
@enigma2446 @shelbo The image is inside the zip archive. Tell me if anything is incorrectly working I haven't tested it yet
Click to expand...
Click to collapse
Any special flashing instructions?
NonStickAtom785 said:
@enigma2446 @shelbo The image is inside the zip archive. Tell me if anything is incorrectly working I haven't tested it yet
Click to expand...
Click to collapse
no go.......tried booting it and flashed it....would not boot
andybones said:
Flar2's AppDash works great if you have root for backing up apps and app data.
As for ROM, I haven't tried this yet, but seems quite promising:
GitHub - Magisk-Modules-Alt-Repo/backup: An android CLI partition backup tool without custom recoveries.
An android CLI partition backup tool without custom recoveries. - GitHub - Magisk-Modules-Alt-Repo/backup: An android CLI partition backup tool without custom recoveries.
github.com
Click to expand...
Click to collapse
have no idea how to use it...tried termux but dont understand fully
enigma2446 said:
have no idea how to use it...tried termux but don;t understand fully
Click to expand...
Click to collapse
same here I may give it a go.
May need to try another terminal.. IIRC Termux can run into issues.
It seems like in terminal:
-d all
should backup all
andybones said:
same here I may give it a go.
May need to try another terminal.. IIRC Termux can run into issues.
It seems like in terminal:
-d al
Click to expand...
Click to collapse
andybones said:
same here I may give it a go.
May need to try another terminal.. IIRC Termux can run into issues.
It seems like in terminal:
-d all
should backup all
Click to expand...
Click to collapse
Yes but I'm not sure about the backup output directory ...pixel is /storage/emulated/0/
andybones said:
same here I may give it a go.
May need to try another terminal.. IIRC Termux can run into issues.
It seems like in terminal:
-d all
should backup all
Click to expand...
Click to collapse
I get this output with nothing saved due to read only file system
enigma2446 said:
Yes but I'm not sure about the backup output directory ...pixel is /storage/emulated/0/
Click to expand...
Click to collapse
This is internal.
Are you rooted? U have to be g to of installed the module
andybones said:
This is internal.
Are you rooted? U have to be g to of installed the module
Click to expand...
Click to collapse
Yes I'm rooted with the module installed.