So, I have copied my backups from my device to computer using adb pull /sdcard/clockworkmod/backup/ .
but I have deleted the backups on my device. so i wanted to restore my backups to my device. but I came with no success when using adb push /sdcard/clockworkmod/backup/. the process can be done, but I don't find my backups in my CWM.
so, I tried another directory to /mnt/shell/emulated/clockworkmod/backup/. but the adb push process can not be done.
please, help me out. I want to get my data back
thelasthonor said:
So, I have copied my backups from my device to computer using adb pull /sdcard/clockworkmod/backup/ .
but I have deleted the backups on my device. so i wanted to restore my backups to my device. but I came with no success when using adb push /sdcard/clockworkmod/backup/. the process can be done, but I don't find my backups in my CWM.
so, I tried another directory to /mnt/shell/emulated/clockworkmod/backup/. but the adb push process can not be done.
please, help me out. I want to get my data back
Click to expand...
Click to collapse
Is it official CWM? If so, you need to push them whilst in recovery to /sdcard/clockworkmod/backup. If you do it in Android, CWM will not see them.
This is because since android 4.2, /sdcard is actually mounted on /data/media/0 however CWM never updated code so in CWM /sdcard is mounted to /data/media instead.
So boot into recovery and push to /sdcard/clockworkmod/backup or /data/media/clockworkmod/backup
Then do yourself a favour and stop using Official CWM
rootSU said:
Is it official CWM? If so, you need to push them whilst in recovery to /sdcard/clockworkmod/backup. If you do it in Android, CWM will not see them.
This is because since android 4.2, /sdcard is actually mounted on /data/media/0 however CWM never updated code so in CWM /sdcard is mounted to /data/media instead.
So boot into recovery and push to /sdcard/clockworkmod/backup or /data/media/clockworkmod/backup
Click to expand...
Click to collapse
I recently pushed to /data/media/clockworkmod/backup/ and still no success. I pushed the folder but the only ones copied is the files (like system4.ext4.tar.a) in the /mnt/shell/emulated/clockworkmod/backup/
but for now my problem is solved by manually copy it to my storage and using Root Explorer to copy it to /mnt/shell/emulated/clockworkmod/backup/
Then do yourself a favour and stop using Official CWM
Click to expand...
Click to collapse
LOL. what about that? official Official CWM is s*ck?
Its a piece of sh*t. Its no longer managed by the original dev. Just a messy community of people...
The features are poor, the code is ancient and the support is null.
If you trust your device with that, more fool you.
Sent from my Nexus 5 using Tapatalk
rootSU said:
Its a piece of sh*t. Its no longer managed by the original dev. Just a messy community of people...
The features are poor, the code is ancient and the support is null.
If you trust your device with that, more fool you.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
LOL. And the rant of the day award goes to rootSU.
That should send people flocking to Philz.
theesotericone said:
LOL. And the rant of the day award goes to rootSU.
That should send people flocking to Philz.
Click to expand...
Click to collapse
Philz, TWRP, some other new recovery... It doesn't matter. CWM is terrible and no one should use it.
Sent from my Nexus 5 using Tapatalk
rootSU said:
Philz, TWRP, some other new recovery... It doesn't matter. CWM is terrible and no one should use it.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Guess now's not the time to tell you I still use it. I've been on Playfulgods unofficial swipeable builds since I've had this device. I've had zero issues with it and I flash quite a bit. TWRP is historically buggier than CWM imo. I like Philz and will move onto that when CWM starts to present problems. Old habits die hard or so they say.:laugh:
rootSU said:
Its a piece of sh*t. Its no longer managed by the original dev. Just a messy community of people...
The features are poor, the code is ancient and the support is null.
If you trust your device with that, more fool you.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
yeah, on my way flashing another recovery.
but, can you tell me where is the directory of Philz or TWRP backups, cause I need to immediately sent the backups to my computer since my nexus' storage is only 12GB
rootSU said:
Official CWM
Click to expand...
Click to collapse
rootSU said:
Its a piece of sh*t
Click to expand...
Click to collapse
theesotericone said:
Guess now's not the time to tell you I still use it.
Click to expand...
Click to collapse
theesotericone said:
Playfulgods unofficial
Click to expand...
Click to collapse
Not quite the same.
thelasthonor said:
yeah, on my way flashing another recovery.
but, can you tell me where is the directory of Philz or TWRP backups, cause I need to immediately sent the backups to my computer since my nexus' storage is only 12GB
Click to expand...
Click to collapse
I don't know much about TWRP. Philz is /sdcard/clockworkmod/backup
Sent from my Nexus 5 using Tapatalk
rootSU said:
Not quite the same.
I don't know much about TWRP. Philz is /sdcard/clockworkmod/backup
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
hey thanks, now I am using philz as my recovery.
but there is a minor problem for me. the name of the backups. precisely the time of the backups. the names of the backups should be yyyy-mm-dd.hh.mm.ss. I have recently backed up my N5, but instead of named 2014-09-09.20.40.00, it was named 1970-09-01.20.00.17_blablabla.
so, how can I changed the time or the name of the backups to the normal time? It's not a big problem, but it annoyed me. thanks before
thelasthonor said:
hey thanks, now I am using philz as my recovery.
but there is a minor problem for me. the name of the backups. precisely the time of the backups. the names of the backups should be yyyy-mm-dd.hh.mm.ss. I have recently backed up my N5, but instead of named 2014-09-09.20.40.00, it was named 1970-09-01.20.00.17_blablabla.
so, how can I changed the time or the name of the backups to the normal time? It's not a big problem, but it annoyed me. thanks before
Click to expand...
Click to collapse
Use the time settings mentioned in the nexus 5 philz thread
Sent from my Nexus 5 using Tapatalk
Related
Hey all,
Recently, I had an issue with the SD card in my skyrocket. Phone will get stuck at custom boot screen for a while. After finally booting, I noticed I had to reinstall some apps...not all.
Anyways,
Right after this happened, I noticed that I could no longer perform a clockwork mod backup as I have done with no issues. It gets stuck randomly during the system files backup state. What can I do to fix this?
I have tried many things, including fix per, flash new cwm version and format new card and copy over all files previously other. Nothing seems to work.
Any help is appreciated...
Thanks
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
I would flash back to stock reload the whole initial bootloader and stock recovery then go and redo the actual superuser then put on the custom recovery try TWRP or you can try cwm again nothing against skaters CWM twrp is just easier for me
Ahh, was not familiar with twrp and have always used cwm. However, after your reply and downloading and flashing it, I must say I love the GUI and ease of use.
Anyways,
I flashed it and did perform a backup. While I did get two errors, it did actually complete and I believe it did save data to this SD card. Should I worry about the errors though?
What's the difference between this from recovery tool and cwm? Still can't get cwm to backup after that SD card issue.
Thank you much for quick reply
--mike
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
pookieguy said:
Ahh, was not familiar with twrp and have always used cwm. However, after your reply and downloading and flashing it, I must say I love the GUI and ease of use.
Anyways,
I flashed it and did perform a backup. While I did get two errors, it did actually complete and I believe it did save data to this SD card. Should I worry about the errors though?
What's the difference between this from recovery tool and cwm? Still can't get cwm to backup after that SD card issue.
Thank you much for quick reply
--mike
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
if your not having issue with twrp then i wouldnt worry there has been alot people that said thta sk8ters recovery was giving issues never personally had any trouble when i used maybe just bad recovery.. sometimes thing act wonkie for no reason
Thanks...
Should I worry about the two errors even if it did complete?
Also, how do you restore?
I tested by booting to twrp and hit the restore button. I browsed to directory on SD card where backup is but not sure what file to chose?
Thanks again...
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
pookieguy said:
Thanks...
Should I worry about the two errors even if it did complete?
Also, how do you restore?
I tested by booting to twrp and hit the restore button. I browsed to directory on SD card where backup is but not sure what file to chose?
Thanks again...
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I don't use twrp but shouldn't the backup be named after the time/date it was created. If that's true then you should know which backup to choose by looking at the time/date.
I'm thinking the folders for the failed backups are also there..
This is just the Grouper KRT16S OTA package from Google. Bugfixes, 1.4Mb in size. ZIP file attached. I am not your tech support to get ADB working on you laptop or why your Nexus 7 does weird things after installing so don't be surprised if I ignore questions that can be answered by searching.
Original file name:
3aad414bf97cede8ecbc2027597e7f01bfe1ce47.signed-nakasi-KRT16S-from-KRT16O.3aad414b.zip
If you are stock and want to update from KRT16O then just drop the zip into your adb folder and sideload it in recovery:
Code:
adb sideload signed-nakasi-KRT16S-from-KRT16O-3aad414b.zip
Help this helps someone.
kpetrie77 said:
This is just the Grouper KRT16S OTA package from Google. Bugfixes, 1.4Mb in size. ZIP file attached. I am not your tech support to get ADB working on you laptop or why your Nexus 7 does weird things after installing so don't be surprised if I ignore questions that can be answered by searching.
Original file name:
3aad414bf97cede8ecbc2027597e7f01bfe1ce47.signed-nakasi-KRT16S-from-KRT16O.3aad414b.zip
If you are stock and want to update from KRT16O then just drop the zip into your adb folder and sideload it in recovery:
Code:
adb sideload signed-nakasi-KRT16S-from-KRT16O-3aad414b.zip
Help this helps someone.
Click to expand...
Click to collapse
I have a question. If this can be side loaded to recovery and I assume you mean twrp or cwm why can't it just be down loaded to device and flashed through recovery? Maybe I just don't understand what you mean by sideloaded. Thanks if you reply and if not I read the op and thanks for this
Sent from my HTCONE using Xparent Blue Tapatalk 2
Also with unlocked Bootloader and TWRP I get this update OTA and installation went fine.
ml_taz said:
Also with unlocked Bootloader and TWRP I get this update OTA and installation went fine.
Click to expand...
Click to collapse
Same for me, OTA went fine with TWRP
Received tonight at 02.30 cet!!! :good:
ml_taz said:
Also with unlocked Bootloader and TWRP I get this update OTA and installation went fine.
Click to expand...
Click to collapse
How did you update via twrp? I'm having bluetooth.apk error. It always fail. =(
Sent from my Nexus 7 using xda app-developers app
ianmedina said:
How did you update via twrp? I'm having bluetooth.apk error. It always fail. =(
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
use adb sideload command, read the OP
ianmedina said:
How did you update via twrp?
Click to expand...
Click to collapse
I didn't update via TWRP! I get the update OTA! Also I have unlocked BL, Root and TWRP.
If you didn't get it via OTA you can sideload the Zip from Post #1.
ml_taz said:
I didn't update via TWRP! I get the update OTA! Also I have unlocked BL, Root and TWRP.
If you didn't get it via OTA you can sideload the Zip from Post #1.
Click to expand...
Click to collapse
Whefe can i find the adb folder? Sorry about the question..
Hopefully you can walkthrough me or tell me the step by step.
Sent from my Nexus 7 using xda app-developers app
ianmedina said:
Whefe can i find the adb folder? Sorry about the question..
Hopefully you can walkthrough me or tell me the step by step.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
platform-tools, SDK
View attachment 2404062
treIII said:
I have a question. If this can be side loaded to recovery and I assume you mean twrp or cwm why can't it just be down loaded to device and flashed through recovery? Maybe I just don't understand what you mean by sideloaded. Thanks if you reply and if not I read the op and thanks for this
Sent from my HTCONE using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
The stock recovery does not look for a zip on the device without a command file telling it there is one present to flash.
ivn888 said:
platform-tools, SDK
View attachment 2404062
Click to expand...
Click to collapse
Thanks... But i think i'm gonna lose root?
Sent from my Nexus 7 using xda app-developers app
ianmedina said:
Thanks... But i think i'm gonna lose root?
Click to expand...
Click to collapse
No, doesn't touch su.
Sent from my HTC6500LVW using Tapatalk
kpetrie77 said:
No, doesn't touch su.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
How about my twrp? I might lose it.
Sent from my Nexus 7 using xda app-developers app
ianmedina said:
How about my twrp? I might lose it.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I believe the stock recovery will be installed with the update? but you can always reinstall TWRP with flashify......
What folder was this update downloaded too?
Re: OTA
bonzer2u said:
I believe the stock recovery will be installed with the update? but you can always reinstall TWRP with flashify......
Click to expand...
Click to collapse
The OTA process works with TWRP but reloads stock recovery AND removes root. No problem getting both back through the usual methods.
ianmedina said:
How about my twrp? I might lose it.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
It's a nexus. Its not hard to get back recovery and root.
Sent from my Nexus 7 using XDA Premium HD app
ianmedina said:
How did you update via twrp? I'm having bluetooth.apk error. It always fail. =(
Click to expand...
Click to collapse
ianmedina said:
Whefe can i find the adb folder? Sorry about the question..
Hopefully you can walkthrough me or tell me the step by step.
Click to expand...
Click to collapse
ianmedina said:
Thanks... But i think i'm gonna lose root?
Click to expand...
Click to collapse
ianmedina said:
How about my twrp? I might lose it.
Click to expand...
Click to collapse
I'm going to say some things not to be mean or rude but to keep you out of trouble. It is not installing because you do not know what you are doing and have not taken the initiative to learn some basics for yourself. Except for the fact you are not on the correct ROM to install this update in the first place, I would say losing root and TWRP would be the best thing for now.
You are going screw up your device and have no idea how to fix it yourself or even what information to provide for others to help you fix it. Your best bet would to be restoring to stock with a factory image and not screw around until you are up to speed.
There are ton of FAQ's and guides on this site in the general sections. Learn how to install and use ADB and fastboot. Read up on the different types up zip files and how they are installed. If you are using a one click, understand what ADB or fastboot commands are going on behind the scenes and exactly what it is pushing to your device.
Once you have a general understanding of things, please come and play around as much as you want. If you do something that causes a bootloop you will at least know how to recover your device.
bonzer2u said:
I believe the stock recovery will be installed with the update? but you can always reinstall TWRP with flashify......
Click to expand...
Click to collapse
ChauncyG said:
The OTA process works with TWRP but reloads stock recovery AND removes root. No problem getting both back through the usual methods.
Click to expand...
Click to collapse
A 5.4Mb recovery is not going to fit in a 1.4Mb zip file. Also see post 3, 4 and 8. Root and TWRP or CWM will remain intact. Bad information is worse than no information.
"Once you have a general understanding of things, please come and play around as much as you want. If you do something that causes a bootloop you will at least know how to recover your device.A 5.4Mb recovery is not going to fit in a 1.4Mb zip file. Also see post 3, 4 and 8. Root and TWRP or CWM will remain intact. Bad information is worse than no information."
Not trying to give bad info just relating my personal experience. You are correct that a full recovery image file at 5.4mb could not fit, even zipped, in a 1.4mb update, however, a full recovery image file is not needed to change the behavior of things. Root and the ability to boot back into TWRP were lost during my update process. It was easily corrected but it did happen. Others have reported a different experience. That was mine.
A good scientist reports ALL observations and reserves judgement until a complete data set is established.
OK yesterday I rooted my nexus 5 using chain fire. I then installed the ROM manger app to install CWM. Does this mean I can now flash ROMs or zip files (eg. Beats audio) straight away or am I missing steps.
Sorry and thank you in advanced
Sent from my Nexus 5 using xda app-developers app
You need to head to CWM recovery and then flash the rom.zip files...
Make sure you do a complete wipe before installing a new rom...
dec1153 said:
OK yesterday I rooted my nexus 5 using chain fire. I then installed the ROM manger app to install CWM. Does this mean I can now flash ROMs or zip files (eg. Beats audio) straight away or am I missing steps.
Sorry and thank you in advanced
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Dude, uninstall Rom Manager asap and never use it again, this has always been a terrible app and now its real terrible. Flash a custom recovery with Flashify (Play) or in fastboot (fastboot flash recovery namerecovery.img). Rom Manger is not a solution but a problem.
Sorry I don't understand!!! I have been using CWM for a very long time. I am just asking now that I am able to flash ROMs?
Sent from my Nexus 5 using xda app-developers app
dec1153 said:
Sorry I don't understand!!! I have been using CWM for a very long time. I am just asking now that I am able to flash ROMs?
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Rom Manager is unstable and buggy mate, if you have a working recovery then you`re lucky. Make sure to backup your current rom before you start flashing and backup your EFS folder and store it on the PC to be sure.
gee2012 said:
Rom Manager is unstable and buggy mate, if you have a working recovery then you`re lucky. Make sure to backup your current rom before you start flashing and backup your EFS folder and store it on the PC to be sure.
Click to expand...
Click to collapse
I have done a nandroid backup through CWM which functiond fine. Thanks anyways. One question, after root my nexus 5 is a tad slower. Is it possible to turn ART on while rooted because I heard people are getting bootloops when they do this.
Thanks
dec1153 said:
I have done a nandroid backup through CWM which functiond fine. Thanks anyways. One question, after root my nexus 5 is a tad slower. Is it possible to turn ART on while rooted because I heard people are getting bootloops when they do this.
Thanks
Click to expand...
Click to collapse
ART is still experimental atm and some apps are not optimized for it yet. That can cause bootloops in some cases. If that should happen restore the backup.
dec1153 said:
... Thanks anyways...
Click to expand...
Click to collapse
Dude, @gee2012 is just trying to help, and is right about RM. I used it back in the day on my Nexus One running CM before there were any alternatives. Over time, RM got wonkier and wonkier, ending up an app that is best avoided. I recommend that you take the advice of a recognized contributer, and don't continue to be loyal to a has-been app that could bork your system.
PS. Welcome to the forum!
PhilipTD said:
Dude, @gee2012 is just trying to help, and is right about RM. I used it back in the day on my Nexus One running CM before there were any alternatives. Over time, RM got wonkier and wonkier, ending up an app that is best avoided. I recommend that you take the advice of a recognized contributer, and don't continue to be loyal to a has-been app that could bork your system.
PS. Welcome to the forum!
Click to expand...
Click to collapse
Hi I only used ROM manger to install CWM. I don't plan to use it for anything else. I plan to boot into CWM and flash a .zip from there. Is this not safe?
dec1153 said:
Hi I only used ROM manger to install CWM. I don't plan to use it for anything else. I plan to boot into CWM and flash a .zip from there. Is this not safe?
Click to expand...
Click to collapse
Sure it is. I was talking about Rom Manager, please don`t ever use it again. Just for your sake mate.
Everything said about Rom Manager is 100% correct; it's long been known to brick some phones, due to the recovery files it lists not being compatible with a lot of devices (and poorly defined).
Great advice, @PhilipTD and @gee2012.
Haha OK. I just like CWM so I used it to install it. How do I boot into CWM without using the app? So I can delete ROM manger after
dec1153 said:
... my nexus 5 is a tad slower. Is it possible to turn ART on...
Click to expand...
Click to collapse
Further to @gee2012's response, rather than switch to ART, and thereby forego the use of Xposed, check out the optimized Dalvik library.
dec1153 said:
Haha OK. I just like CWM so I used it to install it. How do I boot into CWM without using the app? So I can delete ROM manger after
Click to expand...
Click to collapse
Download it from here https://www.clockworkmod.com/rommanager and flash in fastboot or with Flashify (Google Play.)
PhilipTD said:
Further to @gee2012's response, rather than switch to ART, and thereby forego the use of Xposed, check out the optimized Dalvik library.
Click to expand...
Click to collapse
I don't need closed framework. So uninstalling and then switching ART should work? I'm scared it will go into a bootloop!
You might like Philz, btw. (With a nod to @rootSU)
dec1153 said:
I don't need closed framework. So uninstalling and then switching ART should work? I'm scared it will go into a bootloop!
Click to expand...
Click to collapse
You might want to read the first 5 threads in the General section well, this will give you the basics knowledge you need to not to brick your phone
gee2012 said:
Download it from here https://www.clockworkmod.com/rommanager and flash in fastboot or with Flashify (Google Play.)
Click to expand...
Click to collapse
I already have CWM installed? Do I have to install it again? If so can you take me on a step by step guide, I'm a utter noon! Thanks
So step 1) download ROM manger
Then.....
dec1153 said:
... can you take me on a step by step guide...
Click to expand...
Click to collapse
Wouldn't you rather learn it yourself? It's so much more rewarding.
dec1153 said:
I already have CWM installed? Do I have to install it again? If so can you take me on a step by step guide, I'm a utter noon! Thanks
So step 1) download ROM manger
Then.....
Click to expand...
Click to collapse
If it works for you, it works. Don`t have to flash it twice. Look above @PhilipTD`s post for Philz Touch CWM, which is even better and has more options than CWM. Its a zip and you can flash it in CWM.
And its noob, not noon
USE THIS INSTEAD: http://forum.xda-developers.com/showthread.php?t=2711051
============================================================================================
Now that s-off has been released, here's a working TWRP for the Verizon M8.
FYI: Because I'm lazy I did not build this from source. I simply ported the GSM twrp and replaced the variant specific bits with our stuff. I have also not extensively tested this, so beware!
Pre-Requisites:
- s-off (I'm sure you can use the search button and figure out how to do this)
- fastboot and adb binaries (I'm sure you can use the search button and figure out how to do this)
- download this: deleted
Boot into fastboot mode:
Code:
adb reboot bootloader
Install the img downloaded from above:
Code:
fastboot flash recovery openrecovery-twrp-2.7.0.3-m8vzw-UNOFFICIAL.img
You may then either boot back into your rom using: fastboot reboot
or
Use the menu in the bootloader to reboot or (via the HBOOT menu) reboot into recovery
Sweet. Thanks
Sent from my HTC6525LVW using Tapatalk
Do I need glasses to use ?
HTC ONE (M8)
sorry for broken links, etc
all should be well now, please check your md5sum
no, you don't need glasses for this one =P
invisiblek said:
sorry for broken links, etc
all should be well now, please check your md5sum
no, you don't need glasses for this one =P
Click to expand...
Click to collapse
Flashify works great for flashing this too...
Sent from my Nexus 7 using Tapatalk
Nice looks great awesome work
Thanks, cool to,have both custom recovery options. Anyone do a backup yet ?
Sent from my VS980 4G using Tapatalk
krazie1 said:
Thanks, cool to,have both custom recovery options. Anyone do a backup yet ?
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
I did a backup with TWRP. Everything went smooth for me.
Sent from my Insane powered M8 using Tapatalk
awesome I've been waiting for a usable TWRP. Does it actually mount external SD card so we can backup to there?
Works awesome! Thanks.
Flashed and booted fine. Did not try it out yet. Thanks for updating.
krazie1 said:
Thanks, cool to,have both custom recovery options. Anyone do a backup yet ?
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
Backs up to the internal card fine but reboots into TWRP for me when I try to send a backup to the external SD.
Can't flash it with flashify
Sent from my HTC One VZW using Tapatalk 4
coldconfession13 said:
Can't flash it with flashify
Sent from my HTC One VZW using Tapatalk 4
Click to expand...
Click to collapse
Just used flashify, worked fine.
ocman40 said:
Just used flashify, worked fine.
Click to expand...
Click to collapse
Me too. No issues.
ocman40 said:
Just used flashify, worked fine.
Click to expand...
Click to collapse
Mike02z said:
Me too. No issues.
Click to expand...
Click to collapse
Worked fine for me as well.
Flashed via ADB. Can backup on SD Card! Thanks InvisibleK! :good:
Reflashed using ADB this time and still just restarts TWRP when trying to backup to my external SD card. There is plenty of room before someone asks
Mike02z said:
Reflashed using ADB this time and still just restarts TWRP when trying to backup to my external SD card. There is plenty of room before someone asks
Click to expand...
Click to collapse
Yea, it may help if there is room lolol!
Mike02z said:
Reflashed using ADB this time and still just restarts TWRP when trying to backup to my external SD card. There is plenty of room before someone asks
Click to expand...
Click to collapse
It restarted for me when I tried to backup to SD too. Then when I enabled compression it allowed me to make a backup to my SD card no problem.
Mods feel free to move if this is in the wrong section.
This is an unofficial build of TWRP RECOVERY built from the latest twrp sources
I just compiled this out and it fixes the new fstab layout starting from tonight's Cyanogenmod build
Credit: Mdmower --> https://github.com/mdmower/twrp/tree/twrp-2.7.0.8
Download: http://d-h.st/kgR
Note: If after installing the recovery, it will not pass the screen TWRP:
Restart and boot normally (system), then with any file manager to delete this "/sdcard/TWRP/.twrps
Click to expand...
Click to collapse
Sorry, this thread isn't pretty, but whatever
Mdmower also compiled his...didn't notice lol
feel free to take either one, won't hurt my feelings, as long as it gets the job done
http://mdmower.cmphys.com/download/267/?version=2.7.0.8
How did this recovery pan out? What's diff of this one and 2.7. Just wondering
Sent from my Desire HD using Tapatalk
chrisb906 said:
How did this recovery pan out? What's diff of this one and 2.7. Just wondering
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
CM is having a new fstab layout for a number of devices. One of these changes include a by-name partition support (instead of say mmcblk0p33 called as "system"). you need this recovery to flash CM from today, and probably all 4.4.2 ROMs soon
That's the major change...other than that: adb fixes (big issue for me while trying to pull kmesg logs for Sense 6 building :fingers-crossed, LED fixes, dual core support, fix of backup and restoration of encrypted backups
Is the mounting to pc issue solved?
Sent from my HTC One XL using xda premium
paras33 said:
Is the mounting to pc issue solved?
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
I haven't tried. I know adb works now though so I can guess that mass storage will too
Sent from my HTC One XL using Tapatalk
Tried flashing, then tried booting both versions directly from fastboot and neither will completely boot for me. All I get is a flashing TWRP splash.
jacobas92 said:
Tried flashing, then tried booting both versions directly from fastboot and neither will completely boot for me. All I get is a flashing TWRP splash.
Click to expand...
Click to collapse
Is anyone else having this issue? because its working for me fine. Maybe an ruu will fix it
Sent from my HTC One XL using Tapatalk
pandasa123 said:
Is anyone else having this issue? because its working for me fine. Maybe an ruu will fix it
Sent from my HTC One XL using Tapatalk
Click to expand...
Click to collapse
I guess I could try that. I'm fairly certain I've got the latest firmware and hboot, but its worth a shot
Sent from my Wabbajack using Tapatalk Classic
jacobas92 said:
Tried flashing, then tried booting both versions directly from fastboot and neither will completely boot for me. All I get is a flashing TWRP splash.
Click to expand...
Click to collapse
I did what Jose mentioned in the Pacman Kitkat thread as the fix to this--"Note: If after installing the recovery, it will not pass the screen TWRP
Restart and boot normally (system), then with any file manager to delete this "/sdcard/TWRP/.twrps"
It worked for me, and I had the same flashing TWRP screen issue as you.
Rayvin56 said:
I did what Jose mentioned in the Pacman Kitkat thread as the fix to this--"Note: If after installing the recovery, it will not pass the screen TWRP
Restart and boot normally (system), then with any file manager to delete this "/sdcard/TWRP/.twrps"
It worked for me, and I had the same flashing TWRP screen issue as you.
Click to expand...
Click to collapse
Ahh. Thanks bud, I'll get right on that.
Mounting to PC is not working in this version of TWRP
sathish804 said:
Mounting to PC is not working in this version of TWRP
Click to expand...
Click to collapse
It is for me, you could try uninstalling the currently installed driver on windows and reinstall it.
jacobas92 said:
It is for me, you could try uninstalling the currently installed driver on windows and reinstall it.
Click to expand...
Click to collapse
I tried to uninstall and re-install the drivers but no luck for me to enable USB mounting in TWRP 2.7.0.8
I just flashed this via fastboot and when I go into recovery, it gets stock on the teamwin logo forever?? md5 checks out?
Lunatic00 said:
I just flashed this via fastboot and when I go into recovery, it gets stock on the teamwin logo forever?? md5 checks out?
Click to expand...
Click to collapse
Go back, one page.
I flashed this today and now my internal SD card doesn't mount. I'd be grateful for any assistance.
[email protected] said:
I flashed this today and now my internal SD card doesn't mount. I'd be grateful for any assistance.
Click to expand...
Click to collapse
All you needed to do was read the last few posts in this thread for suggestions on what to do.
Sent from my Evita
I flashed mine with Flash GUI Image. It worked flawlessly and TWRP is super smooth and stable. I couldn't use fastboot because my phone can't be recognized by my PC.
timmaaa said:
All you needed to do was read the last few posts in this thread for suggestions on what to do.
Sent from my Evita
Click to expand...
Click to collapse
I'm sorry timmaaa, I'm not sure what you mean. When I use a file explorer on my phone, it says my internal storage sd card is unmounted.