2014-05-23 -- These builds are no longer being maintained.
This is TWRP touch recovery for m7 (m7_u and m7_ul) GSM versions only.
Credits:
TeamWin http://teamw.in/project/twrp2 - goes without saying, without them we wouldn't be doing this.
Dees_Troy - continued development work on TWRP.
Flyhalf205 - the original port of TWRP to m7.
tdhite - some of the latest goodies (performance mode, charging led, etc.)
GadgetFreak - updated curtain image.
My contribution is putting all the pieces together and providing regular builds for the community.
Change log:
build 2.7 4.05.05
- This release addresses wipe/mount issues in 05.01 and 05.02 builds.
- Switched to msm8960 kernel with this commit to disable secure discards for ext4 wipes.
- With this release, versions are simply 2.7 + build Y-MM-DD (i.e. 2.7 4.05.01)
- Fix for block by-name support change in CM11 as noted here
build 2.7 4.05.02
- Updated charger icons restored (missing in 4.05.01 build)
build 2.7 4.05.01
- With this release, versions are simply 2.7 + build Y-MM-DD (i.e. 2.7 4.05.01)
- Fix for block by-name support change in CM11 as noted here
build 2.7.0.4b 2014-04-21
- Maintenance release with latest TWRP commits from ominirom and tdhite.
build 2.7.0.4b 2014-04-08
- Fix for missing brightness control in settings.
build 2.7.0.4b 2014-04-07
- Switched to CM11 m7 kernel to address performance issues - change log
build 2.7.0.4 2014-04-06
- Initial build release
- Building from tdhite/android_bootable_recovery - change log
- Kernel: CM11 msm8960 - change log
- Updated curtain image
- Updated charger icons from here
Downloads:
Fastboot images and flashable zips: here
Versioning:
My builds are marked with build date in the .img and .zip (i.e. yyyymmdd) as well as the TWRP version number (i.e. 2.7.0.x mmdd), where yyyy is the build year, mm is the build month and dd is the build day. This should help reduce confusion on determining if you have the latest build, etc.
Installation:
Fastboot Method
Unlock bootloader at http://www.htcdev.com/bootloader/
Make sure fastboot is unchecked in power options and turn phone completely off
Reboot into bootloader (fastboot USB mode)
Issue commands:
Code:
fastboot flash recovery recovery.img
fastboot erase cache
Note: fastboot erase cache is only required when coming from stock recovery, otherwise skip this step. If you receive 'unable to mount /cache' error in recovery, use Advance Wipe menu to wipe (i.e. format) the cache partition.
Select reboot recovery.
Recovery Method
Simply flash the flashable zip in your existing custom recovery (TWRP/CWM)
Or better yet, grab Flashify from the Play store and flash the recovery.img directly from within your current ROM (root required.)
Reporting bugs:
Report bugs on the latest version only (posted in this thread) and give details such as hboot version, rom name/version, custom kernel, recovery log from /cache/recovery/last_log, really as much detail as possible. Without details I won't investigate.
Reserved
Thank you very much for posting this. Used the flashable zip and it worked like a charm.
hi, first thank you and wanted to ask if you have solved the problem of the block to run the wipe-factory reset.
ok, I just tried doing a factory reset, but the problem persists.
Thanks, twrp-recovery-2.7.0.4-m7-20140406.img is working fine for me. I did the following after flashing it
- Backup
- Wipe Boot, System, Data
- Reboot (TWRP warned that there was no system, but I rebooted anyway without installing SU)
- After 2 minutes of hanging on the splash screen, Power + Volume Down to get back to bootloader and then into recovery
- Restored the backup I made in the first step
- Flashed a new ROM that I just built
- Rebooted
- Everything was fine and the date in Settings/About matched my new ROM
Great thanks, can we have changelog? plzzzz
stempox said:
ok, I just tried doing a factory reset, but the problem persists.
Click to expand...
Click to collapse
Is the problem that it's slow or doesn't work at all? They are fixing a slow format issue in the m7wls version, which might be the same issue here?
Edit: try checking 'use rm - f' in settings and see if that helps.
cschmitt said:
Is the problem that it's slow or doesn't work at all? They are fixing a slow format issue in the m7wls version, which might be the same issue here?
Click to expand...
Click to collapse
In my case, the bar never advances and after several minutes it freezes everything and I have to restart with the power button. but in this I am looking for support from other users if they have the same or different about reports.
thanks.
regarding use rm - f 'do a test and report the outcome.
---------- Post added at 07:41 PM ---------- Previous post was at 07:30 PM ----------
Chezbel said:
Thanks, twrp-recovery-2.7.0.4-m7-20140406.img is working fine for me. I did the following after flashing it
- Backup
- Wipe Boot, System, Data
- Reboot (TWRP warned that there was no system, but I rebooted anyway without installing SU)
- After 2 minutes of hanging on the splash screen, Power + Volume Down to get back to bootloader and then into recovery
- Restored the backup I made in the first step
- Flashed a new ROM that I just built
- Rebooted
- Everything was fine and the date in Settings/About matched my new ROM
Click to expand...
Click to collapse
cschmitt said:
Is the problem that it's slow or doesn't work at all? They are fixing a slow format issue in the m7wls version, which might be the same issue here?
Edit: try checking 'use rm - f' in settings and see if that helps.
Click to expand...
Click to collapse
I went to the settings, I have selected (use rm-rf) as you told me and now works fine. thanks:good:
stempox said:
In my case, the bar never advances and after several minutes it freezes everything and I have to restart with the power button. but in this I am looking for support from other users if they have the same or different about reports.
thanks.
regarding use rm - f 'do a test and report the outcome.
Click to expand...
Click to collapse
I have never had this issue... just to be clear, you mean factory reset or advanced reset, right?
stempox said:
I went to the settings, I have selected (use rm-rf) as you told me and now works fine. thanks:good:
Click to expand...
Click to collapse
So appears to be problem with format command, will see if we can fix it in a later build.
pottyvick said:
I have never had this issue... just to be clear, you mean factory reset or advanced reset, right?
Click to expand...
Click to collapse
Basically, commands that format a partition, factory reset or advanced wipe.
I've noticed the issue with wiping cache, it starts but doesn't do anything. Has this been solved yet?
Sent from my HTC One using Tapatalk
Is there a changelog? There is none on the teamw.in site. I'm currently running 2.7.0.0 and would like to know what differs from it and 2.7.0.4.
chrisrj28 said:
I've noticed the issue with wiping cache, it starts but doesn't do anything. Has this been solved yet?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Sounds like I can flash the updated Recovery without losing any data Nice
Theshawty said:
Is there a changelog? There is none on the teamw.in site. I'm currently running 2.7.0.0 and would like to know what differs from it and 2.7.0.4.
Click to expand...
Click to collapse
If you go to the Sprint HTC one forum there is a changelog posted in the twrp thread
Sent from my HTC One using Tapatalk
pottyvick said:
I have never had this issue... just to be clear, you mean factory reset or advanced reset, right?
Click to expand...
Click to collapse
is just that, strange because I read in the TWRP thread, other users have had the same problem with this version.
---------- Post added at 08:26 PM ---------- Previous post was at 08:23 PM ----------
chrisrj28 said:
I've noticed the issue with wiping cache, it starts but doesn't do anything. Has this been solved yet?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
just read back a page and you found the solution, however restarts in recovery, go to Settings and select (use rm-rf), and solve the problem.
stempox said:
is just that, strange because I read in the TWRP thread, other users have had the same problem with this version.
---------- Post added at 08:26 PM ---------- Previous post was at 08:23 PM ----------
just read back a page and you found the solution, however restarts in recovery, go to Settings and select (use rm-rf), and solve the problem.
Click to expand...
Click to collapse
Yeah I saw that but didn't know it was related to that issue too. Thanks
Sent from my HTC One using Tapatalk
Theshawty said:
Is there a changelog? There is none on the teamw.in site. I'm currently running 2.7.0.0 and would like to know what differs from it and 2.7.0.4.
Click to expand...
Click to collapse
Just added to OP.
2.7.0.4 04.06 wipe problematic
HTC One cihazımdan Tapatalk kullanılarak gönderildi
For those having issues with format / wipe / factory reset, please try this test build: twrp-recovery-2.7.0.4-m7-20140406b.img It's built using the CM11 m7 kernel (vs. msm8960) and possibly does not suffer from the format performance issue. Interested in your feedback.
If you give me the necessary files İ want to translate about Turkish language support
Sent from my HTC One using XDA Premium 4 mobile app
Related
Q&A for [ROM][5.0]+[4.4.4][Official][Nighties]VanirAOSP Lollipop Alpha 3
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][5.0]+[4.4.4][Official][Nighties]VanirAOSP Lollipop Alpha 3. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
help
I dont have root. To take this one i have to?
Sorry, have been busy lately.
As of today, you will have two options:
You can use the version vanir_bacon_5.0.0.120214.zip that will have working root buildin but a permissive SELinux (and therefore there is some risk of something invading your system) or you can use the version vanir_bacon_5.0.0.120214.enforced.zip and install SuperSU afterwards...
I am totally stock ROM and recovery.
Can I just download Vanir Rom and Gapps to phone and then:
1: wolume+ and powerbotton
2: wipe data
3: install Vanir zip
4: install Gapps zip
Finished......
Or I am totally on the wrong way ?
Printet on OnePlus One
ZoNe_dk said:
I am totally stock ROM and recovery.
Can I just download Vanir Rom and Gapps to phone and then:
1: wolume+ and powerbotton
2: wipe data
3: install Vanir zip
4: install Gapps zip
Finished......
Or I am totally on the wrong way ?
Printet on OnePlus One
Click to expand...
Click to collapse
you need to install custom recovery first
http://forum.xda-developers.com/showthread.php?t=2788632
There is no face unlock feature in smart lock menu. Someone told me to flash a different version of gapps to fix it. Can I dirty flash a different version or should I do it after wiping data?
Thanks.
Sent from my A0001 using XDA Free mobile app
agentinani047 said:
There is no face unlock feature in smart lock menu. Someone told me to flash a different version of gapps to fix it. Can I dirty flash a different version or should I do it after wiping data?
Thanks.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
You can try without wiping data: just wipe system, dalvik and cache partitions, flash your ROM, flash gapps, reboot.
for everyone who wants to change the settings for the notification bar weather: just add a "cLock" widget and set everything up there. :good:
i'm on vanir 5.0.2 (problem with xpose mod)
I just wanted to know why xpose module is not working on this rom.
whenever i run xpose mod it says ur version of android is not suported.
wat to do??
deb1806 said:
I just wanted to know why xpose module is not working on this rom.
whenever i run xpose mod it says ur version of android is not suported.
wat to do??
Click to expand...
Click to collapse
Xposed does not work with ART. You'll have to go back to a 4.4.4 ROM, where dalvik cache is enabled.
cam30era said:
Xposed does not work with ART. You'll have to go back to a 4.4.4 ROM, where dalvik cache is enabled.
Click to expand...
Click to collapse
sorry for being a noob.. i jst forgot dat 5.o is ART .
any alternative of xpose for 5.0
deb1806 said:
sorry for being a noob.. i jst forgot dat 5.o is ART .
any alternative of xpose for 5.0
Click to expand...
Click to collapse
No need to apologize. Everyone was a noob once. I think you'll have to wait until the developer updates xposed to work with ART. I can't imagine it'll be long. If you search XDA you might even find a thread.
You can get the buildprop editor from the play store too. I use 401 dpi
so I had this rom and worked perfectly and almost without bugs (version 122914) and now in the last version the wifi is working very badly and does not connect correctly, gives authentication error. Anyone knows how to fix it? thanks in advance
joseka22 said:
so I had this rom and worked perfectly and almost without bugs (version 122914) and now in the last version the wifi is working very badly and does not connect correctly, gives authentication error. Anyone knows how to fix it? thanks in advance
Click to expand...
Click to collapse
Upon further research, it is confirmed that Vanir ROM does NOT include any modem files. Sorry for the previous misinformation.
I just flashed it and got caught in a bootloop I turned it off but it finally booted because (and I dont know the reasoning behind how it works, I just know it worked) I booted into fastboot and then reboot it that way and it works.
EDIT: It only works when you have a usb plugged and when you unplug it it reboots.
Will flashing a new kernel like AK fix this problem?
elpiggo said:
I just flashed it and got caught in a bootloop I turned it off but it finally booted because (and I dont know the reasoning behind how it works, I just know it worked) I booted into fastboot and then reboot it that way and it works.
EDIT: It only works when you have a usb plugged and when you unplug it it reboots.
Will flashing a new kernel like AK fix this problem?
Click to expand...
Click to collapse
That's an odd problem... Did you clean flash?
rudi_j7 said:
That's an odd problem... Did you clean flash?
Click to expand...
Click to collapse
Yeah I came from stock and wiped everything. The Rom would only run if usb debugging was enabled and when I tried to reboot into recovery, it wouldnt let me unless i selected recovery from the power menu, then waited until the twrp logo showed up, then unplugged it. Otherwise it would just reboot into the rom
Latest vanir has a kernel that needs latest firmware to work.
Our Exodus has a kernel that works with normal firmware so you might want to use this.
And you should maybe stay away from CM's new firmware as we got informed that at least find7 seems to hardbrick with the newest firmware and find7 is very close to bacon...
Martin_Ro said:
Latest vanir has a kernel that needs latest firmware to work.
Our Exodus has a kernel that works with normal firmware so you might want to use this.
And you should maybe stay away from CM's new firmware as we got informed that at least find7 seems to hardbrick with the newest firmware and find7 is very close to bacon...
Click to expand...
Click to collapse
I have insalled 13.01 nightly CM12 and I don't have any problems. No bootlops, no brick. Not tried today nightly yet.
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
DOWNLOAD : https://dl.twrp.me/thea/
BUGS:
If you have found a bug, please consider posting it to our github issues log and then I'll report to Dess_Troy. If you have a significant problem that cannot be answered in this thread, your best bet is to PM Dees_Troy 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.
XDA:DevDB Information
[RECOVERY][THEA] TWRP 3.2.3-0 Touch Recovery [OFFICIAL], ROM for the Moto G 2014 LTE
Contributors
luca020400, LuK1337
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Created 2016-02-07
Last Updated 2018-08-07
Reserved
Reserved
Source code : motog2014devteam
Source code : CyanogenMod
ok and how can we install it?
javierutxo said:
ok and how can we install it?
Click to expand...
Click to collapse
fastboot flash recovery file.img
LuK1337 said:
fastboot flash recovery file.img
Click to expand...
Click to collapse
aja, and what about unlock bootloader and rooting? the same process than moto g 2014?
javierutxo said:
aja, and what about unlock bootloader and rooting? the same process than moto g 2014?
Click to expand...
Click to collapse
Yes
javierutxo said:
ok and how can we install it?
Click to expand...
Click to collapse
Take the steps from here http://forum.xda-developers.com/moto-g-2015/general/rooting-moto-g-2015-lte-xt1078-t3086069
Just change the twrp.mg for the one in this post.
Good Luck!
Thank you!! Its worked for me on XT1072
Hello, It worked just fine on my XT1078
Thanks!
Is it possible to make this an "official" release ?
551790 said:
Is it possible to make this an "official" release ?
Click to expand...
Click to collapse
Yes , but I'm not going to do that
luca020400 said:
Yes , but I'm not going to do that
Click to expand...
Click to collapse
Hi Luca! Can you explain shortly how you built this image? Any manual that you can point me to?
I'm asking because I'd like to build it also for peregrine...
New build up
Download
idk whats happening. i unlocked my phone and installed this recovery and when i try to enter in recovery mode it shows and android with the exclamation sign and never continues to the actual recovery. it just stays there forever and then reboots by itself. can anyone tell me what is wrong?
Maledroid said:
idk whats happening. i unlocked my phone and installed this recovery and when i try to enter in recovery mode it shows and android with the exclamation sign and never continues to the actual recovery. it just stays there forever and then reboots by itself. can anyone tell me what is wrong?
Click to expand...
Click to collapse
You haven't flashed twrp
Reboot to bootloader
By pc
fastboot flash recovery twrp-thea.img
( with admin/sudo )
Then reboot to recovery
luca020400 said:
New build up
Download
Click to expand...
Click to collapse
Hi Luca, thank you very much for your hard work on this device.
About this new release of TWRP, I'd like to know, if possible, what are the main differences with the previuos one.
cgb.spender said:
Hi Luca, thank you very much for your hard work on this device.
About this new release of TWRP, I'd like to know, if possible, what are the main differences with the previuos one.
Click to expand...
Click to collapse
TWRP fixes
The TWRP version still 2.8.6 but it's 2.8.7
My encrypted TWRP nandroid backups fail with the following error message:
E:createTarFork() process ended with ERROR=255
Click to expand...
Click to collapse
This only happens when I use encryption, and it always happens right near the end of backing up the Data partition (the System partition backup completes successfully).
N.B. The percentage of files and MB processed do not increase in-step, like with an unencrypted backup. The MB percentage increases to 90%+ far quicker than the percentage of files processed. When the percentages come in-line with each other near the end of the Data partition backup, it fails, and the above error message is given.
I was using a Titan build of TWRP to create nandroid backups on my Thea device previously, and had no issues with encrypted backups.
This is an issue, as there are sensitive security details stored in the backup, which must be encrypted with a strong password.
Internal Storage failure?
sunka1 said:
My encrypted TWRP nandroid backups fail with the following error message:
....
Click to expand...
Click to collapse
This happens to me all the time all of a sudden. I did not change anything at all, except for flashing a new CM version.
I also get a strange stat error, something with google.photo cache.
Yesterday, I have then flashed the new 2.8.6(7). from a few posts above and that gave my phone the rest. It might be because I flashed through TWRP itself into the recovery partition, but now additional to the backup error above when I want to erase dalvik cache, the recovery just hangs. I also can't restore a backup atm.
Now I have reflashed the real 2.8.6.0 recovery and it still hangs when I want to wipe dalvik... wtf is going on here?
And oh yea, my phone does not boot anymore either, it just loops at the flash screen...
UPDATE:
After I found some info on this thread about similar issues, I factory reset my phone with stock recovery (TWRP was not reliable anymore, even the 2.8.6.0 version that was running perfectly before) and then reflashed the latest CM on a wiped internal storage. Now I am up and running again with minimal loss of data due to my TB backups that are scheduled and save to the SD.
But this leaves a very weird feeling back, basically my phone was rendered useless out of nowhere (I was running the previous CM for 2 weeks already), making TWRP backups impossible and forcing me to wipe the internal storage with all media on it without giving me the chance to back it up (MTP in TWPR was also very flaky and died several times half in copy operations). Something is going very wrong with this phone, never ever had that on any of my 5 previous htc devices and the fact that the OnePlusOne users are among the main ones that reported similar issues, I have a feeling it is linked to cheap storage quality. Motorola is a Chinese company now after all... :-/
i try flash on custom recovery a rom using my otg storege on the note 5 . someone can help me.
Otg is not working on twrp yet, you would have to use philz cwm recovery.
I don't have a nice otg yet, and I have not tried to do it... maybe someone else can explain the process... I just know as of today, you would have to use Philz recovery.
dandroid7 said:
Otg is not working on twrp yet, you would have to use philz cwm recovery.
I don't have a nice otg yet, and I have not tried to do it... maybe someone else can explain the process... I just know as of today, you would have to use Philz recovery.
Click to expand...
Click to collapse
Philz is needed and same steps. Put on otg. Click install select ur drive and flash.
thanks
raynol said:
thanks
Click to expand...
Click to collapse
@bigbiff is working on getting OTG working on N920T - he needs a DMESG.txt file from TWRP after attempting to use OTG in recovery. I have tried to do it for him but am having difficulties pulling the file via ADB - hopefully I (or someone) will figure it out and get him that file - once he has it - he should be able to fix OTG pretty quickly.
mocsab said:
@bigbiff is working on getting OTG working on N920T - he needs a DMESG.txt file from TWRP after attempting to use OTG in recovery. I have tried to do it for him but am having difficulties pulling the file via ADB - hopefully I (or someone) will figure it out and get him that file - once he has it - he should be able to fix OTG pretty quickly.
Click to expand...
Click to collapse
It was my understanding since it is not responding it would be unable to pull. Can he provide the instructions. I will flash twrp and try it.
I.D.F.W.Y.
BACARDILIMON said:
It was my understanding since it is not responding it would be unable to pull. Can he provide the instructions. I will flash twrp and try it.
I.D.F.W.Y.
Click to expand...
Click to collapse
I just finished testing a new TWRP Recovery for @bigbiff and he got OTG working. I made a backup using OTG and everything went fine. You will either need to download the TWRP he posted (last page of the TWRP Thread) or wait until it is officially released - your call - but it is working.
mocsab said:
I just finished testing a new TWRP Recovery for @bigbiff and he got OTG working. I made a backup using OTG and everything went fine. You will either need to download the TWRP he posted (last page of the TWRP Thread) or wait until it is officially released - your call - but it is working.
Click to expand...
Click to collapse
Nice.
I.D.F.W.Y.
mocsab said:
I just finished testing a new TWRP Recovery for @bigbiff and he got OTG working. I made a backup using OTG and everything went fine. You will either need to download the TWRP he posted (last page of the TWRP Thread) or wait until it is officially released - your call - but it is working.
Click to expand...
Click to collapse
Link.
Nevermind found it lol. Everything I searched it showed everything but what I needed Google found it tho lol
I.D.F.W.Y.
BACARDILIMON said:
Link.
Nevermind found it lol. Everything I searched it showed everything but what I needed Google found it tho lol
I.D.F.W.Y.
Click to expand...
Click to collapse
Glad you found it - it is also on the Twrp site - just search Twrp devices for the Samssung Note 5.
By the way - what does I.D.F.W.Y. mean?
mocsab said:
Glad you found it - it is also on the Twrp site - just search Twrp devices for the Samssung Note 5.
By the way - what does I.D.F.W.Y. mean?
Click to expand...
Click to collapse
Thanks man
It means
I dont fuc* with you.
---------- Post added at 11:22 AM ---------- Previous post was at 10:58 AM ----------
mocsab said:
Glad you found it - it is also on the Twrp site - just search Twrp devices for the Samssung Note 5.
By the way - what does I.D.F.W.Y. mean?
Click to expand...
Click to collapse
i did a test back up and when i went to restore it said it restored but when i went to reboot it went into download mode. it never restored my system.
BACARDILIMON said:
Thanks man
It means
I dont fuc* with you.
---------- Post added at 11:22 AM ---------- Previous post was at 10:58 AM ----------
i did a test back up and when i went to restore it said it restored but when i went to reboot it went into download mode. it never restored my system.
Click to expand...
Click to collapse
i did a test earlier and it worked for me - I also just did another back up and am in the process of restoring - so I will confirm it works again shortly - my file sizes seem right - close to 7gb - which is about what most of my Nandroids have been - without system, it would be much smaller - But I will knwo for sure when this finishes the restore.
I wonder if you accidentally did not check the 'system' toggle in twrp when you backed up and or restored the rom you were on?
EDIT - CONFIRMED. Backup from OTG was successful - RESTORE from OTG of that same backup was successful.
YOu must have accidentially toggled off system when you did the restore in the first place.
mocsab said:
i did a test earlier and it worked for me - I also just did another back up and am in the process of restoring - so I will confirm it works again shortly - my file sizes seem right - close to 7gb - which is about what most of my Nandroids have been - without system, it would be much smaller - But I will knwo for sure when this finishes the restore.
I wonder if you accidentally did not check the 'system' toggle in twrp when you backed up and or restored the rom you were on?
EDIT - CONFIRMED. Backup from OTG was successful - RESTORE from OTG of that same backup was successful.
YOu must have accidentially toggled off system when you did the restore in the first place.
Click to expand...
Click to collapse
i finally got it to odin back to stock. will mess with this when i get home from work.
BACARDILIMON said:
i finally got it to odin back to stock. will mess with this when i get home from work.
Click to expand...
Click to collapse
Just make sure everything you want backed up is checked when oyu do the backup - and same when you do the restore - should work
(I figure you know this already so I really don't need to remind you ....) good luck -
TWRP
2.8.7.0
UNOFFICIAL
Just as the title says this is an unofficial build of TWRP recovery v2.8.7.0 for the HTC DESIRE S (Saga).
*** I DO NOT OWN A DESIRE S*** This has been tested on by numerous users previously and I test all my releases on the nearly identical Desire HD. It has been tested with both Sense roms and current KK/LP AOSP roms. I have put it to the test and not found any issues so far. If you find any bugs please report with an attached recovery log.
DOWNLOAD
Current Version for ODP Saga builds
<<HERE>>
Current Version for ODP Saga-opt builds
<<TWRP for SAGA-OPT>>
For more info on SAGA-OPT see the original release notes for ace-opt cm-12.1 HERE
Special thanks to @Mustaavalkosta & @kylon for all his work keeping this device alive for so long.
SOURCES
Recovery built in a CM-12.1 environment using device trees/kernel
from Mustaavalkosta's OpenDesireProject github
My modified trees/kernel are HERE and HERE
TWRP source from Omnirom
Code:
Changelog:
7/30/15
-2.8.7.0
4/14/15
- 2.8.6.0
2/28/15
- fix reboots
2/27/15
- 2.8.5 release
- LP cm-12.0 based
- updated offmode blobs
1/10/2015
- 2.8.1.2 release
- MTP support is back on, no more USB mount. CM-12.0 went this direction and so shall recovery
- by-name partition mount support. Needed for 1/10 nightly and beyond.
1/5/2015
- 2.8.1.1 release (i know i'm falling behind)
- /sd-ext support
- f2fs support
11/15/2014
- 2.8.1 release
- Performance profiles in recovery, should speed up backup/restore just a bit
- Offmode charging images are back!!! Thanks to @mdmower for the guidance from 8960 series HTC's
6/13/2014
- fixed adb in recovery
6/12/2014
- fixed ability to use encryption
6/11/2014
- initial release
XDA:DevDB Information
TWRP-Desire S, Tool/Utility for the HTC Desire S
Contributors
jrior001, jrior001
Source Code: https://github.com/OpenDesireProject
Version Information
Status: Stable
Created 2015-11-23
Last Updated 2015-11-22
I've been requested to create my own thread since i sort of took over maintaining TWRP builds for the time being. These are the same builds I've been providing in the older TWRP thread.
jrior001 said:
I've been requested to create my own thread since i sort of took over maintaining TWRP builds for the time being. These are the same builds I've been providing in the older TWRP thread.
Click to expand...
Click to collapse
Thank you very much for your kind contribution to the community. I am very appreciated.
Thank you for keeping this device alive for all these years!!!
Having a problem lately though. When I try to connect my phone via fastboot, I just get a USB device not recognized. I have tried to install HTC USB drivers (official and forum downloads) and on my other android devices I have no issues to use fastboot or adb (meaning that it's set up correctly?). Any ideas on how to use fastboot on Windows 10?
Thanks for any help!
moesus said:
Thank you for keeping this device alive for all these years!!!
Having a problem lately though. When I try to connect my phone via fastboot, I just get a USB device not recognized. I have tried to install HTC USB drivers (official and forum downloads) and on my other android devices I have no issues to use fastboot or adb (meaning that it's set up correctly?). Any ideas on how to use fastboot on Windows 10?
Thanks for any help!
Click to expand...
Click to collapse
It might be possible by using Fastboot.reg method as it is working for me.
Hi,
I've recently found my ds and i thought i'd try out CM12.1 or even CM13. however i'm stuck at installing TWRP-saga-2.8.7.0-unofficial.img.
I can get twrp-2.6.3.0-saga.img to work OK.
Basically, after flashing the latest recovery via fastboot (looks to work OK) and then reboot into recovery, it just hangs on the startup flash screen. I have to pull the battery to get back into the bootloader again.
i have
HBOOT 2.00.2002
S-OFF (unlocked)
RADIO 3822.10.08.04_M
thanks
stehaworth said:
I've recently found my ds and i thought i'd try out CM12.1 or even CM13. however i'm stuck at installing TWRP-saga-2.8.7.0-unofficial.img.
Click to expand...
Click to collapse
CM13 uses the opt version, for 12.1 you might also want to go for the opt version. It will mean that you have to format your sd-card as ext4... If you go that way, you need 2.8.7.1.
stehaworth said:
Basically, after flashing the latest recovery via fastboot (looks to work OK) and then reboot into recovery, it just hangs on the startup flash screen. I have to pull the battery to get back into the bootloader again.
Click to expand...
Click to collapse
Maybe there was an error downloading the file? Check the file size just to see if it's offside...
TWRP-saga-2.8.7.0-unofficial.img - 7.4 MB
TWRP-recovery-sagaopt-2.8.7.1.img - 7.3 MB
i23098 said:
CM13 uses the opt version, for 12.1 you might also want to go for the opt version. It will mean that you have to format your sd-card as ext4... If you go that way, you need 2.8.7.1.
Maybe there was an error downloading the file? Check the file size just to see if it's offside...
TWRP-saga-2.8.7.0-unofficial.img - 7.4 MB
TWRP-recovery-sagaopt-2.8.7.1.img - 7.3 MB
Click to expand...
Click to collapse
i think i might have remembered something from when i originally was playing with this phone. it has a screen by Hitachi..... i think this stops me from doing anything CM12.1 +...
stehaworth said:
i think i might have remembered something from when i originally was playing with this phone. it has a screen by Hitachi..... i think this stops me from doing anything CM12.1 +...
Click to expand...
Click to collapse
Yeah, if you have an Hitachi panel you can't run a recent CM... It shouldn't affect the recovery, though... I think
lool, I flashed TWRP-recovery-sagaopt-2.8.7.1.img and issued factory reset... and it formatted my SD card (coz it takes it as internal memory)... I already recovered files most of files, but was "a bit" surprised... was it also like that in previous versions?
Unauthorized
i recently got to stupid situation - i wanted to try cm13 so i used tweaked twrp 2.8.7.1 for saopt sm13 and formated my sd card, loosing everything - i had to load the rom to the phone by using ./adb push. the rom was not stable enough to be used, so i wanted to go back - flashed back twrp 2.8.7.0 formated again my card and finding that i cannot mount phone to my macbook (dunno why?) and that ./adb push returns with info that device is unauthorized. i had to use different phone to put rom on sd card to be able to install it.
tweaked version or older version of twrp did not have this problem.
Hi, where can I read Step by Step instalation proces of TWRP
Hi,
how can i change from v2.8.7.0-saga to 2.8.7.1-sagaopt? every try within twrp quits with [IMAGE FLASH COMPLETED], but after reboot to recovery i'm still on v2.8.7.0-saga???
c_kay
c_kay said:
Hi,
how can i change from v2.8.7.0-saga to 2.8.7.1-sagaopt? every try within twrp quits with [IMAGE FLASH COMPLETED], but after reboot to recovery i'm still on v2.8.7.0-saga???
c_kay
Click to expand...
Click to collapse
Same problem
mentodsman said:
Same problem
Click to expand...
Click to collapse
use Rashr - Flash Tool apk to flash the img
Flash using TWRP. This will flash all files in the MCG24.251-5 update except for recovery.
New features in this update that I've noticed:
-Marshmallow, aged to perfection in Verizon's own servers. Only one major release version obsolete, and with outdated security patches!
-WiFi calling (woooooo! Those custom roms just got another carrier-specific, unportable feature to compete with)
-The command center widget has been replaced with the Droid Turbo 2 version
Get it here: https://mega.nz/#!G1xg1aYa!fm2hUL7hDDVaxTAj_iPbtY61P-8VrQEvoOJiVsDtdho
Here's the stock recovery image if you want it: https://mega.nz/#!r1wDQRCJ!KHbo_Q6L-WE_VyB1x8W4FbT6PrerPEyn9H1C6VUAyf8
Flashing this rom updates the bootloader to a version that can communicate with the kernel to tell SafetyNet that it is unlocked, causing it to fail. Fret not, however, as there are two options to fix this:
OPTION 1: Flash the SU4TL-49 bootloader using the following TWRP package: https://mega.nz/#!6logEaIQ!q8qPJw65Upt38Hxiu1JyxErmwbgL7CBzuGzzPC0C9pQ
OPTION 2: Flash this patch made by @bhb27: https://www.androidfilehost.com/?fid=745425885120696423
Wipe cache and dalvik/art cache after either of these options.
NOTE that these options only fix failures due to SafetyNet checking the bootloader status. It will still fail due to root, xposed and the like. There are no known consequences or side effects to either of these options, so just pick whichever one you feel like.
If you notice weird things after you flash this rom (long boots other than the first one which is supposed to be long, random reboots, etc.) try flashing the stock recovery image and factory resetting.
If you want root, flash this version of SuperSU first, then flash whatever newer version you want: https://download.chainfire.eu/751/SuperSU/
If you have trouble flashing this, try TWRP Mod 3 instead of Mod 4.
Ouch, you have almost full flash inside archive, with bootloader too... Who is the most brave, introduce yourself ))
+ mirror
I can confirm that it works on old bootloader.
I had SULT-49 5.1 installed before and I just flashed this via TWRP. I haven't taken the OTA. It works perfectly. Thank you.
PS: My bootloader now is moto-apq8084-70.95 (2016-06-29). Do you have same version after taking OTA?
Did you have to wipe the system, data and cache first like you would with a new ROM or just dirty flash it?
Sent from my XT1254 using Tapatalk
Thanks OP
rickyblaze13 said:
Did you have to wipe the system, data and cache first like you would with a new ROM or just dirty flash it?
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
When in doubt, always wipe.
Hey everyone, what is your safetynet status with this rom? It's failing for me, and I can't figure out why.
rickyblaze13 said:
have to wipe the system, data and cache first
Click to expand...
Click to collapse
It works w/o, but, IMO, better wipe, than not. You don't need extra bugs, right )
It's completing setup now, I did a wipe after I backed up my phone. It's unlocked and rooted before I flashed the zip
Sent from my QMV7A using Tapatalk
Can we get this ULed to Dropbox or Google Drive? The Mega link and the mirror are taking forever...
Crowick said:
Can we get this ULed to Dropbox or Google Drive? The Mega link and the mirror are taking forever...
Click to expand...
Click to collapse
My google drive is full and I don't have Dropbox. But if you wanted to mirror it, I will gladly add the link to the OP.
Sure, I'll throw it up on Google Drive. Do you have just the MM stock recovery kicking around?
---------- Post added at 04:08 AM ---------- Previous post was at 03:50 AM ----------
Google Drive link to the TWRP Flashable version in your OP hosted on Mega.
https://drive.google.com/open?id=0BzQJqGBWW9ViQzFjTWJVUVZNazg
Crowick said:
Sure, I'll throw it up on Google Drive. Do you have just the MM stock recovery kicking around?
---------- Post added at 04:08 AM ---------- Previous post was at 03:50 AM ----------
Google Drive link to the TWRP Flashable version in your OP hosted on Mega.
https://drive.google.com/open?id=0BzQJqGBWW9ViQzFjTWJVUVZNazg
Click to expand...
Click to collapse
thanks for gdrive mirror
Crowick said:
Sure, I'll throw it up on Google Drive. Do you have just the MM stock recovery kicking around?
---------- Post added at 04:08 AM ---------- Previous post was at 03:50 AM ----------
Google Drive link to the TWRP Flashable version in your OP hosted on Mega.
https://drive.google.com/open?id=0BzQJqGBWW9ViQzFjTWJVUVZNazg
Click to expand...
Click to collapse
I don't. I don't know how I would get it since I need root access to get it, and I can't get root access without TWRP, and I have to overwrite the stock recovery to get TWRP.
TheSt33v said:
I have to overwrite the stock recovery to get TWRP.
Click to expand...
Click to collapse
fastboot boot TWRP.img
s5610 said:
fastboot boot TWRP.img
Click to expand...
Click to collapse
Nice! Good call.
https://mega.nz/#!r1wDQRCJ!KHbo_Q6L-WE_VyB1x8W4FbT6PrerPEyn9H1C6VUAyf8
Is anyone else having exceptionally long reboot/start times for their phone after flashing this rom?
Just the first boot after flashing
Sent from my XT1254 using Tapatalk
Thanks for that! Did anybody try to install it right over SU4TL-44? Just in case, I'm rooted, using xposed and twrp.
TheSt33v said:
Hey everyone, what is your safetynet status with this rom? It's failing for me, and I can't figure out why.
Click to expand...
Click to collapse
Perhaps this:
https://www.xda-developers.com/android-safetynet-now-reportedly-tripped-by-unlocked-bootloaders/
I just tried using AP a few hours ago and it failed with the screen in the article. OTA with unlocked bootloader.