Just rooted and s-off a replacement one S. Everything went fine until i got to the point i was going to flash a rom. Ive been using the viper rom. after starting the installer it seemed out that all it did was format the memory. After it finished it rebooted and stayed on the HTC splash screen for probably twenty minutes before i did a hard boot. after getting back into recovery and trying again it did the same thing. i decided to just start over and do reboot from recovery but it is saying there is no OS. so i went back to view my card from recovery and everything on it was erased. Now im trying to copy the viper rom back over via recovery but the transfer speed is down to about 50kbps and keeps saying its timing out. any ideas
What recovery are u using? I read several times, that ViperRom and the latest twrp don't fit. In case of using twrp u should try an older version.
Sent from my HTC One S using xda app-developers app
customromfan said:
What recovery are u using? I read several times, that ViperRom and the latest twrp don't fit. In case of using twrp u should try an older version.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
I guess i was using the twrp with that all in one toolkit i would switch to cwm but i cant get my computer now to reconigze the phone. i keep getting the htc mtp driver issue and haven't been able to figure it out. I figured if i can get the other recovery installed i should be able to flash a os
Jayster06 said:
I guess i was using the twrp with that all in one toolkit i would switch to cwm but i cant get my computer now to reconigze the phone. i keep getting the htc mtp driver issue and haven't been able to figure it out. I figured if i can get the other recovery installed i should be able to flash a os
Click to expand...
Click to collapse
go into bootloader, then fastboot usb mode.
the flash the new recovery via fastboot command, or with the all in one toolkit (chose custom, then locate your file)
i switched over to cwm and tried copying a viper rom to my phone but it keeps erroring out during the transfer. I tried a smaller rom and it copied over but all its doing with i click install is going to a black screen then back to cwm
i also tried several other roms that were smaller in size and it was doing the same thing
Related
Went to flash an updated Rom on my ATT One X. Been using CWM recovery.
Reboot into recovery, wipe/factory reset.
Go to find the file, SDCard is almost completely gone/items deleted.
I load up TWRP, mount the SDCard, nothing, all gone. So I just format the SDCard, copy the new Rom over to the SDCard root.
Reboot into recovery. Try to install, when I select it in TWRP, swipe, it sits, then just reboots the app and goes back to the main screen.
At a loss right now, phone apparently soft bricked. Maybe bad Rom zip?
Rooted/Unlocked of course, been working fine the past week. Only had the phone 1 week.
Ideas? Help..haha...
Easy, except you gonna have to reunlock boot loader.you can't boot into fast boot OEM relock bootloader and run ruu. You could also try using fast boot to flash something.
Sent from my HTC One X using xda app-developers app
Or it might be a case of twrp going bad. Fast boot flash recovery img and boot back into recovery.
Sent from my HTC One X using xda app-developers app
ethantarheels123 said:
Or it might be a case of twrp going bad. Fast boot flash recovery img and boot back into recovery.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
It was clockwork I was using at the time.
Everytime I rebooted into recovery and selected the file to install, more stuff was missing.
I'm wondering if the SDCard got corrupt, recovery went crazy and wiped etc...or bad Rom.
Redownloaded Rom.
Reformatted SDCard for good measure since it was all pretty much gone.
Flashed TWRP back as the recovery.
Installing the Rom now. CleanRom 4.1SE.
But...all my Sh&t is gone off the SDCard. Backups, photos etc...buh-bye forever.
Side note, my camera lens area on the phone has been getting hot. Not sure where the processor is located on this phone, maybe it is just doing that while trying to install Rom and CPU is running a little hot and normal?
techlogik said:
It was clockwork I was using at the time.
Everytime I rebooted into recovery and selected the file to install, more stuff was missing.
I'm wondering if the SDCard got corrupt, recovery went crazy and wiped etc...or bad Rom.
Redownloaded Rom.
Reformatted SDCard.
Flashed TWRP back as the recovery.
Installing the Rom now.
But...all my Sh&t is gone off the SDCard. Backups, photos etc...buh-bye forever.
Click to expand...
Click to collapse
Cwm has been known to have instability which is why almost everyone suggests using twrp, which is officially supported.
Sent from my HTC One X using xda app-developers app
ethantarheels123 said:
Cwm has been known to have instability which is why almost everyone suggests using twrp, which is officially supported.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Ok. I noticed it was nowhere near as complete and slick at say 4EXT recovery on my Inspire and suspected some weirdness was going on.
Back on TWRP now and seems to be installing the new Rom I just downloaded again.
Rebooting now...guess I should start copying my SDCard to my computer
Go to cnet.com and download recuva. Do a deep scam and it will recover most of your stuff.. worked for me.. do it on your computer.
Sent from my HTC One X using xda app-developers app
rpomponio said:
Go to cnet.com and download recuva. Do a deep scam and it will recover most of your stuff.. worked for me.. do it on your computer.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Ok, cool, will give it a look.
The CleanRom thread blew up, apparently me and bunch of others had this happen using CWM and the latest build....
All working again, now if I can recovery some stuff, like the photos I had, that would be nice.
Appreciate the replies and help.
Edit: recuva didn't find anything useful. SDCard was blasted for good somehow.
techlogik said:
The CleanRom thread blew up, apparently me and bunch of others had this happen using CWM and the latest build....
Click to expand...
Click to collapse
scrosler warned very clearly (even before the latest 4.1 build) not to use CWM. Why so many people chose to ignore him, I have no idea. For some reason the SD card wipe issue was much worse on CleanROM 4.1 than previous versions (and other ROMs).
Take note that the SD wipe issue has also happened on TWRP. Safest approach is to backup SD data to your desktop computer before flashing anything. In particular, your Titanium folder and anything not easily replaceable (photos, etc.). Its a bit of an annoyance to have to do this whenever you want to flash something. But until the cause of the issue is found and fixed, this is the safest way.
Not sure why everyone is blaming the Recovery's for loosing pictures and stuff from there internal SD card. Same thing happened to me with my HTC Touch Diamond, We all came to the conclusion it was from so much flashing. I have used both recovery's and lost pictures and My Documents. Just my 2cents worth.
Is there a tutorial somewhere showing how to switch from CWM to TWRP?
bTrizzy said:
Is there a tutorial somewhere showing how to switch from CWM to TWRP?
Click to expand...
Click to collapse
Doload goo manager and use it to install recovery. Or you can go to twrp dev thread directions are there.
Sent from my HTC One X
Hi all,
Got mine today, tried to install a ROM and it got stuck in bootloop.
I did a number of stupid things not to mention wiping the SD and im in serious trouble.
I can get into bootloader and CWM but thats it.
Ive heard restoring a RUU can cure it but I have a MAC and cant find anything to help.
Can anyone help? Im gutted....and fell like an idiot.
Ive got an S4 on the three network.
Thanks
Hold down the power button for 10 seconds then after the touch buttons stop flashing, just hold the volume button and see if ot enters the bootloader.
Sent from my HTC One S using xda app-developers app
blackcell1 said:
Hold down the power button for 10 seconds then after the touch buttons stop flashing, just hold the volume button and see if ot enters the bootloader.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Hi,
It enters into bootloader but then what?
Follow the guide here from how to flash custom rom
http://forum.xda-developers.com/showthread.php?p=24478083
Sent from my HTC One S using xda app-developers app
blackcell1 said:
Follow the guide here from how to flash custom rom
http://forum.xda-developers.com/showthread.php?p=24478083
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Its sent and wrote the recovery file but what now?
mikejasonsmith said:
Its sent and wrote the recovery file but what now?
Click to expand...
Click to collapse
Specifically you'll have to flash the ROM zip file from the recovery and then use fastboot flash boot boot.img.
You can find boot.img inside the ROM zip file
Tried flashing ROM zip but no joy...when should i flash boot img? before or after recovery?
mikejasonsmith said:
Tried flashing ROM zip but no joy...when should i flash boot img? before or after recovery?
Click to expand...
Click to collapse
ok managed to get the sd mounted...phew...but how do i get a rom on when it wont boot?
mikejasonsmith said:
ok managed to get the sd mounted...phew...but how do i get a rom on when it wont boot?
Click to expand...
Click to collapse
Ive used TRW to get the sd mounted but it wont boot beyond that. i restored the stock recovery but what do i do next?
At the moment i have a phone which has CWM working but nothing else?
Thanks for your help
mikejasonsmith said:
Ive used TRW to get the sd mounted but it wont boot beyond that. i restored the stock recovery but what do i do next?
At the moment i have a phone which has CWM working but nothing else?
Thanks for your help
Click to expand...
Click to collapse
ok so ive tried flashing ruu and keep getting error 155 which is a cid issue i believe - which RUU do i use for a device locked to '3'?
Thanks
oh and can you point me in the direction of it...thanks
mikejasonsmith said:
ok so ive tried flashing ruu and keep getting error 155 which is a cid issue i believe - which RUU do i use for a device locked to '3'?
Thanks
oh and can you point me in the direction of it...thanks
Click to expand...
Click to collapse
so ive managed to get the h3g rom and flashed rom and boot.img.
locked bootloader and run RUU but i keep getting error 155???
Somebody please help me before this thing goes out of the window.....:crying:
Search adb push
Sent from my HTC One S using Tapatalk 2
danevianta said:
Search adb push
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
Finally seem to have done it and managed to RUU
The phone is locked to 3 but as a noob I spent 2 days flashing a generic euro ROM.
When i realised i need a ROM to match CID i downloaded 1.53. Tried this a number of times with no joy.
Just tried 1.78 and it seems to be working
Thanks to everyone for your help - us noobs must be sooooooo annoying.
Htc One S bricked
Hi im relatively new at rooting and am currently experiencing issues with a bricked device.
i have two htc one s devices
my personal one is running cm10 ville with clockwork touch recovery and is working perfectly
however the second one i was using the same exact files.
this one is bricked
its in a constant bootloop.
i can get back to my recovery just fine and get to the fastboot in the phone fine
i cleared my cache
wiped my data and wiped the dalvik cache all perfectly fine when i try to flash the cm10 official rom back on it cannot mount the sd card
i would try to install a different recovery and try again maybe using viper one s
but i cannot get the phone to power on
it doesnt showup on the computer when it is plugged in while in fastboot
when i try the cmd fastboot flash recovery it says waiting for device
any advice. this is not my own phone so i need it repaired pretty quickly.
any helpful information would be much appreciated.
FaLLeN_BtB said:
Hi im relatively new at rooting and am currently experiencing issues with a bricked device.
i have two htc one s devices
my personal one is running cm10 ville with clockwork touch recovery and is working perfectly
however the second one i was using the same exact files.
this one is bricked
its in a constant bootloop.
i can get back to my recovery just fine and get to the fastboot in the phone fine
i cleared my cache
wiped my data and wiped the dalvik cache all perfectly fine when i try to flash the cm10 official rom back on it cannot mount the sd card
i would try to install a different recovery and try again maybe using viper one s
but i cannot get the phone to power on
it doesnt showup on the computer when it is plugged in while in fastboot
when i try the cmd fastboot flash recovery it says waiting for device
any advice. this is not my own phone so i need it repaired pretty quickly.
any helpful information would be much appreciated.
Click to expand...
Click to collapse
Bootloop does not mean your bricked...means you need to fastboot flash boot.img
Sent from my HTC One S using xda premium
blackcell1 said:
Hold down the power button for 10 seconds then after the touch buttons stop flashing, just hold the volume button and see if ot enters the bootloader.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
This little post just pulled me out of missery. Love ya man!
all you guys getting sorted
make a nandroid and sdcard bu NOW and put them on pc,
obviously leave a copy of nandroid on phone also
makes it a lot easier if you get in trouble again
and you/we will
Mounts and Storage --> Format everything --> Now Mount USB Drive --> Put Gapps and ROM
Flash it, erase cache & and Dalvik...Blah blah blah. Flash boot.img in fastboot, and there you go.
Everybody, please remember this and there won't be noob q&a anymore...
TWRP v 2.2.2.1 I can't flash Jelly Bean 4.2.2 .zip on HTC one s (s3)
HI, my device is an HTC ONE S (s3)... I've already unlocked the bootloader and rooted it... it's ok... For recovery mode I installed TWRP v 2.2.2.1.... I've wiped the cache and made a factory reset... BUT when I try to flash the zip which contains the jelly bean 4.2.2 I get a message saying: FAILED when i was trying to install it... PLEASE I NEED YOUR HELP CUZ I THINK I CAN'T DO TOO MUCH WITHOUT AN OS ON MY DEVICE... I'M NOW JUST IN TWRP... HELP PLEASE........
mikebryant2807 said:
HI, my device is an HTC ONE S (s3)... I've already unlocked the bootloader and rooted it... it's ok... For recovery mode I installed TWRP v 2.2.2.1.... I've wiped the cache and made a factory reset... BUT when I try to flash the zip which contains the jelly bean 4.2.2 I get a message saying: FAILED when i was trying to install it... PLEASE I NEED YOUR HELP CUZ I THINK I CAN'T DO TOO MUCH WITHOUT AN OS ON MY DEVICE... I'M NOW JUST IN TWRP... HELP PLEASE........
Click to expand...
Click to collapse
See other reply.
I have an HTC One S and recently tried putting a newer rom on my phone. That process has made my phone a paperweight.
I was using a really old ROM from my rooted HTC One and decided it was time to update as I was having a lot of issues with outdated software. Since i've tried installing several versions of TrickDroid onto my phone and all them failed me. I'm currently running S-off HTC One S with TWRP and I'm stuck in a vicious cycle of bootcycling from either the recovery, bootloader, or the logo. Whenever I leave TWRP it says that I don't have an OS installed, which is most likely why I hang at the logo and cycle through restarts. However, I'm adb pushing roms onto the phone and using the recovery install from zip to run the installers. I've followed that up with variations of flashing the boot in the bootloader with Fastboot flash boot boot.img or just trying to restart straight into my OS, but I can't.
I'm not really sure where to go from here.
khaele said:
I have an HTC One S and recently tried putting a newer rom on my phone. That process has made my phone a paperweight.
I was using a really old ROM from my rooted HTC One and decided it was time to update as I was having a lot of issues with outdated software. Since i've tried installing several versions of TrickDroid onto my phone and all them failed me. I'm currently running S-off HTC One S with TWRP and I'm stuck in a vicious cycle of bootcycling from either the recovery, bootloader, or the logo. Whenever I leave TWRP it says that I don't have an OS installed, which is most likely why I hang at the logo and cycle through restarts. However, I'm adb pushing roms onto the phone and using the recovery install from zip to run the installers. I've followed that up with variations of flashing the boot in the bootloader with Fastboot flash boot boot.img or just trying to restart straight into my OS, but I can't.
I'm not really sure where to go from here.
Click to expand...
Click to collapse
So what happens when you try to install an OS via recovery?
Also what TWRP version do you use?
Sent from my Nexus 7 using Tapatalk HD
khan.orak said:
So what happens when you try to install an OS via recovery?
Also what TWRP version do you use?
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I use TWRP 2.6.0.0
When I try to use TWRP to recovery install I can successfully complete the installation, but once I leave recovery to restart I'm stuck in bootcycles.
khaele said:
I use TWRP 2.6.0.0
When I try to use TWRP to recovery install I can successfully complete the installation, but once I leave recovery to restart I'm stuck in bootcycles.
Click to expand...
Click to collapse
Wipe data/factory reset, cache, dalvik and flashing boot.img before flashing ROM all good??
I see no other reason why it shouldn't boot up.
Sent from my HTC One S using Tapatalk 4 Beta
khan.orak said:
Wipe data/factory reset, cache, dalvik and flashing boot.img before flashing ROM all good??
I see no other reason why it shouldn't boot up.
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yes, I can do all of those things. I eventually got back to an OS by using an RUU from my carrier. It could just be the trickydroid rom I'm trying to use or ALORA. I have no idea.
ive tried twrp and cwm, and both seem to have extremely bad problems on my phone. i haven't seen others have problem with their phones but mine has gone full retard. with twrp, wiping takes a super really long time and most of the time it does not wipe anything even though its says completed. it cant flash any rom either. it just immediately says failed. so i tried cwm thinking it was a twrp thing, but ive ran into the same issues. i flashed a rom thinking it had wiped (it said it had wiped) but id didnt, it just dirty flashed the rom over stock. can someone suggest what can be going wrong? :crying::crying:
Have you tried using the newest twrp?
Sent from my Nexus 5 using XDA Premium 4 mobile app
JCreazy said:
Have you tried using the newest twrp?
i have a mac and no access to a pc, so installing it has been manually through adb commands has been a real headache for me. i first installed it through a tool someone made in the forums for mac but i don't think they have updated it ever since the first release. then i tried using goo manager but it appears the servers are still down.ccc
Sent from my Nexus 5 using XDA Premium 4 mobile app[/QUmasmasclmlklcmxzklckxlzmcxlkmczklmczlkxcmklxzmcOTE]
Click to expand...
Click to collapse
In TWRP you can check -rom option in Settings menu to wipe the partitions instead of formatting them. The process will take less time.
To flash a rom try to boot into the bootloader then select Recovery mode and flash.
If you are rooted you can install TWRP via Flashify app or even with Terminal commands.
I ran the causal root applet on a new SG3 on 4.1.2. Ran root, the unlock script and installed TWRP. Booted into recovery and I got the error for a locked bootloader. I used download mode to get back to the stock rom and then used E-Z unlock to unlock the bootloader. Was able to boot into recovery this time but TWRP read internal and external memory as 0mb, unable to make a backup, and gave a no OS error when went to reboot. I updated TWRP with TWRP manager but the problems are still persistent. Phone boots fine and reboots fine at the moment.
I'm not sure what to do now though. I'm at the point were I don't care if I get stuck with the OTA update but I'm afraid that will brick the phone. I'm not sure what went wrong with TWRP, since this is the second S3 I've rooted.
Any sugestions? I'm afraid to use odin or try anything else since the phone currently works fine. But I'd prefer to not have to sleep in fear it might force the OTA update while I'm asleep and wake up to a bricked phone.
I tried searching, the best I could find is that newer versions of TWRP can't read the memory on a 4.1.2 rom, but the problems were there when I originally started with the recommended version.
Thanks for any help anyone can give.
Try to use cwm or philz and see if you have the same issue.
Sent from my SCH-I535 using Tapatalk 2
Xx
BadUsername said:
Try to use cwm or philz and see if you have the same issue.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Can you install a different custom recovery over one using the causal applet? I was planning on trying to reinstall TWRP but I wasn't sure if I had to do it a certain way like through odin or Using the unified tool kit?
Thanks for the help so far!
Smogon said:
Can you install a different custom recovery over one using the causal applet? I was planning on trying to reinstall TWRP but I wasn't sure if I had to do it a certain way like through odin or Using the unified tool kit?
Thanks for the help so far!
Click to expand...
Click to collapse
No.
Download latest philz touch recovery d2lte zip, then flash it in recovery, then reboot recovery.
Then check and see if you're getting a similar error message.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
No.
Download latest philz touch recovery d2lte zip, then flash it in recovery, then reboot recovery.
Click to expand...
Click to collapse
I can't, recovery doesn't detect my internal or external memory. That's my main issue.
Smogon said:
I can't, recovery doesn't detect my internal or external memory. That's my main issue.
Click to expand...
Click to collapse
OK.
Then download the Odin version and flash through that. Then boot the phone into recovery.
Or download ez recovery, and the latest cwm image file, and flash through that from your rom.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
OK.
Then download the Odin version and flash through that. Then boot the phone into recovery.
Or download ez recovery, and the latest cwm image file, and flash through that from your rom.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I'll try the second option, Thanks!
BadUsername said:
OK.
Or download ez recovery, and the latest cwm image file, and flash through that from your rom.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I tried CWM and the stock recovery through EZ, both gave the same error as TWRP, unable to mount /
I'm really confused as to whats wrong. At this point I don't care if I get stuck with the OTA 4.3, but I don't want to try to update it with the recovery still not reading either my SD cards.
Any Ideas?
Are you sure of your phone model? I believe it puts it on the screen in download mode and also on a sticker under the battery. I'm mostly curious because you mention that this is a new phone with 4.1.2. Are you trying older versions of cwm as well?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Smogon said:
I ran the causal root applet on a new SG3 on 4.1.2. Ran root, the unlock script and installed TWRP. Booted into recovery and I got the error for a locked bootloader. I used download mode to get back to the stock rom and then used E-Z unlock to unlock the bootloader. Was able to boot into recovery this time but TWRP read internal and external memory as 0mb, unable to make a backup, and gave a no OS error when went to reboot. I updated TWRP with TWRP manager but the problems are still persistent. Phone boots fine and reboots fine at the moment.
I'm not sure what to do now though. I'm at the point were I don't care if I get stuck with the OTA update but I'm afraid that will brick the phone. I'm not sure what went wrong with TWRP, since this is the second S3 I've rooted.
Any sugestions? I'm afraid to use odin or try anything else since the phone currently works fine. But I'd prefer to not have to sleep in fear it might force the OTA update while I'm asleep and wake up to a bricked phone.
I tried searching, the best I could find is that newer versions of TWRP can't read the memory on a 4.1.2 rom, but the problems were there when I originally started with the recommended version.
Thanks for any help anyone can give.
Click to expand...
Click to collapse
by any chance did u try to setup dualboot? I have a similar issue where nothing gets mounted and o mb for storage, .only receovery i get to work is cwm. im pretty sure its a partition issue but idk. i tried flashing pit files for my phone but so far the issue remains.
xevildoerxx said:
by any chance did u try to setup dualboot? I have a similar issue where nothing gets mounted and o mb for storage, .only receovery i get to work is cwm. im pretty sure its a partition issue but idk. i tried flashing pit files for my phone but so far the issue remains.
Click to expand...
Click to collapse
No I just used the causal tool.
dpeeps74 said:
Are you sure of your phone model? I believe it puts it on the screen in download mode and also on a sticker under the battery. I'm mostly curious because you mention that this is a new phone with 4.1.2. Are you trying older versions of cwm as well?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm pretty sure, has all the verizon bloat and logos, also I'm pretty sure the causal applet bricks the international ones. I don't remember the version of twrp that the causal script flashed, but I tried that one, the most recent one, and 2.5 i think from EZ recovery. The stock recovery from EZ has the same issue now though which is what really confuses me. at the moment I have root dissabled and the bootloader is locked and its back with the stock recovery, it still says custom when i reboot the phone though.