It worked great for me. I just tested it with a back up and restore from internal as well as an OTG cable.
http://teamw.in/project/twrp2
http://teamw.in/project/twrp2
Updated TWRP 2.7.0.0 for Ville
- Thread starter BullSpit
- Start date
Here you can find a modified version of the latest TWRP that works correctly on hboot 2.16, which have the data/media storage partition in the same system partition.
The version for hboot 2.16:
/data/media storage partition (HBOOT 2.16.0000 only)
twrp-2.7.0.5-ville-dm.img (9 MB)
There are a lot of issue with this recovery because since /sdcard is on /data/media and there is no symlink to /sdcard, than a lot of installer and aroma installer will fail during zip flashing...
also it would be nice if backup is done like 2.6.1.0 (accessible from sdcard/TWRP/backups)
and also it would be nice if the default directory points to /sdcard and not /
Did you flash the correct version for your boot? Also note that no recovery for 2.16 will be able to mount as usb due to new partition layout which is not fat32 anymore. You can mount a usb otg or otherwise use adb sideload feature (google it). This is not the fault of the dev.
Sent from my KFAPWI using Tapatalk
---------- Post added at 10:14 PM ---------- Previous post was at 10:11 PM ----------
Your latest unofficial twrp is working great for me on the 2.16 hboot. Stable so far and when I reboot to system there are no multiple reboots or other issues.
Have you thought about posting the link in the htc one s development forum? A lot of folks who may be interested tend to view that subforum more than this one. Also I had a bit of trouble downloading the link. I had to tell my browser to download the target and had to rename to .img as it was originally trying to download and open as a webpage.
Sent from my KFAPWI using Tapatalk
T-Mobile HTC One S won't enter recovery
I flashed openrecovery-twrp-2.7.1.0-ville.img onto my t-mobile htc one s (i wish i knew the model number i think it may be the pj40100 or the z520e or both, the z520e pj40100 and i'm running hboot 2.15.0 with bootloader unlocked s-on After flashing i rebooted the bootloader and then tried to go into recovery but the phone just goes into a loop of failed system boot attemps and the white htc quietly brilliant screen just goes on and off over and over until i hold down the power button long enough to power down the phone Phone has a brand new battery that I used another phone to fully charge What could be the problem?
I flashed openrecovery-twrp-2.7.1.0-ville.img onto my t-mobile htc one s (i wish i knew the model number i think it may be the pj40100 or the z520e or both, the z520e pj40100 and i'm running hboot 2.15.0 with bootloader unlocked s-on After flashing i rebooted the bootloader and then tried to go into recovery but the phone just goes into a loop of failed system boot attemps and the white htc quietly brilliant screen just goes on and off over and over until i hold down the power button long enough to power down the phone Phone has a brand new battery that I used another phone to fully charge What could be the problem?
Unable to boot or enter recovery
fastboot flash recovery openrecovery-twrp-2.7.0.0-ville
---------- Post added at 07:52 PM ---------- Previous post was at 07:45 PM ----------
There's no sd card present and I tried clear storage from bootloader didn't help the phone doesn't boot to system or recovery i'm running mainver 3.14 installed via ruu hboot 2.15 I'm thinking i need to flash boot.img maybe i dunno
fastboot flash recovery openrecovery-twrp-2.7.0.0-ville
---------- Post added at 07:52 PM ---------- Previous post was at 07:45 PM ----------
There's no sd card present and I tried clear storage from bootloader didn't help the phone doesn't boot to system or recovery i'm running mainver 3.14 installed via ruu hboot 2.15 I'm thinking i need to flash boot.img maybe i dunno
I've got exactly the same problem with my HTC ONE S ville. Cannot get TWRP 2.7.1.2 or any newer version to work, only bootloop. Just wanted to install cm11 on H-Boot 2.15 unlocked, S-OFF :crying::crying:
Use unofficial TWRP v2.8.5.5, -> LOOK HERE <-. From me recommend CyanogenMod 12 or other ROM's on this base (Candy5, Resurrection Remix, PAC-MAN)
Unfortunately no luck at all. The only Recovery I got to work is "openrecovery-twrp-2.6.3.0-ville-selinux.img" but this one is to old to flash new roms. I can flash CM10 with it, but it is also not booting. Here are the details of my phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.09.0000
(bootloader) version-baseband: 0.16.31501S.17_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.77.111.5
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: T-MOB101
(bootloader) battery-status: good
(bootloader) battery-voltage: 3870mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: e964c535
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I send it to a specialist (someone with a Riff Box xD), because I bricked the bootloader (QHUSB_DLOAD). I got the phone back with unlocked super cid hboot 2.15. That are very good prerequisites, but as I said no Recovery works for me. No Philz, no offical or inoffical twrp. This device is the first one in my "carrier" that is really frustrating me...
Last edited:
First: Please delete your serial number and your imei. Just for your own safety.
And second: As your "fastboot getvar all" output states your phone is on hboot 1.09 and not 2.15. So that's the culprit for your problems.
Just flash a RUU that corresponds to your CID and update your phone to the latest firmware version using the OTA function of the stock rom. If you can't find a suitable RUU get S-OFF by flashing a Sense based rom and using either rumrunner or facepalm. After that you will be able to use every RUU you want. If you use facepalm just be careful not to install OTAs before you undo SuperCID or you will brick your phone.
P.S.: Maybe there's a faster method to solve your problems but that's actually what I would do.
And second: As your "fastboot getvar all" output states your phone is on hboot 1.09 and not 2.15. So that's the culprit for your problems.
Just flash a RUU that corresponds to your CID and update your phone to the latest firmware version using the OTA function of the stock rom. If you can't find a suitable RUU get S-OFF by flashing a Sense based rom and using either rumrunner or facepalm. After that you will be able to use every RUU you want. If you use facepalm just be careful not to install OTAs before you undo SuperCID or you will brick your phone.
P.S.: Maybe there's a faster method to solve your problems but that's actually what I would do.
Thank you for the advice, normally I delete those data but it was to late for thinking clearly xD
The vars I posted were the ones before I bricked the phone. I got it back with the values I described after that. But I was not able to update TWRP and in general not able to boot any ROM flashed with old TWRP. But after one week of pain I found this awesome Thread http://xdaforums.com/showthread.php?t=2751518 the RUU updated the whole phone to Hboot 2.16 and suddenly I was able to install TWRP 2.8.5.5-ville and flash the special Hboot 2.16 version of cm11. I had to flash boot.img manually, because S-OFF was gone after RUU update, no big deal. I'm happy now =)
The vars I posted were the ones before I bricked the phone. I got it back with the values I described after that. But I was not able to update TWRP and in general not able to boot any ROM flashed with old TWRP. But after one week of pain I found this awesome Thread http://xdaforums.com/showthread.php?t=2751518 the RUU updated the whole phone to Hboot 2.16 and suddenly I was able to install TWRP 2.8.5.5-ville and flash the special Hboot 2.16 version of cm11. I had to flash boot.img manually, because S-OFF was gone after RUU update, no big deal. I'm happy now =)
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
1It worked great for me. I just tested it with a back up and restore from internal as well as an OTG cable.
http://teamw.in/project/twrp2
