Hey guys, hoping you can offer me some fairly urgent help.
Basically, I was running ViperOne v7.0.0 on my M7, great ROM, never had any major problems with it. Recently, it started crashing a lot, so figured it was high time i reflashed it. Thought i'd give the Lollipop ROM's a try, so downloaded a couple, transferred them to my handset, and went ahead to wipe and reflash. However, due to having a lot of stuff in my "sdcard", I had to remove the ViperOne installer in order to get the two new ROM installers on the phone. It now transpires that one of the ROM's doesnt actually install an OS, and the second installs, but upon rebooting, just boots back into recovery.
At this point, i decided not to bother going for lollipop, and to stick with ViperOne, but upgrade to v7.0.1. Issue im having is that without an OS on the handset, I can't seem to get it to connect to the PC so i can transfer the ViperOne installer.
Anyone got any suggestions? Kinda stuck with an ornate paperweight at the moment! :laugh:
wingnutz said:
Hey guys, hoping you can offer me some fairly urgent help.
Basically, I was running ViperOne v7.0.0 on my M7, great ROM, never had any major problems with it. Recently, it started crashing a lot, so figured it was high time i reflashed it. Thought i'd give the Lollipop ROM's a try, so downloaded a couple, transferred them to my handset, and went ahead to wipe and reflash. However, due to having a lot of stuff in my "sdcard", I had to remove the ViperOne installer in order to get the two new ROM installers on the phone. It now transpires that one of the ROM's doesnt actually install an OS, and the second installs, but upon rebooting, just boots back into recovery.
At this point, i decided not to bother going for lollipop, and to stick with ViperOne, but upgrade to v7.0.1. Issue im having is that without an OS on the handset, I can't seem to get it to connect to the PC so i can transfer the ViperOne installer.
Anyone got any suggestions? Kinda stuck with an ornate paperweight at the moment! :laugh:
Click to expand...
Click to collapse
use adb to push the rom to your phone when booted in recovery.
Code:
adb push your_rom.zip /sdcard
then wait a few minutes (the command window will be unresponsive during the transfer.
Btw what recovery version are you using?
alray said:
use adb to push the rom to your phone when booted in recovery.
Code:
adb push your_rom.zip /sdcard
then wait a few minutes (the command window will be unresponsive during the transfer.
Btw what recovery version are you using?
Click to expand...
Click to collapse
Yeah, that's just dawned on me! :laugh:
I'm using TWRP 2.6.3.3. Thanks for your input though!
Related
Been searching for over a day but no real luck so far.
Currently S-Off, TWRP running Bareback for the last couple months with absolutely zero issues. Saw we got an update so I figured I work try stock out again for a couple of days until I wanted to try something else.
Everytime I put the odexed stock rom on my phone (.zip) either on the root of SD card or in a folder, twrp doesn't seem to have any type of knowledge that the .zip in there. Went through everything I could think of to try and make it show while in twrp to still having the issue. I upgraded to twrp 2.6.3 yesterday only to go back to 2.5 to see if that was possibly an issue.
Anyone know of anything to get zip's to show while in twrp? I'm getting close to just RUUing just to save myself any more headache over something that seems so simple.
Well I still have no idea on why I could never get TWRP to see the zip's but after relocking, RUU and unlock, everything is back to normal.
Does anyone have an issue with the MTP driver never installing? My continually failed this morning even though fastboot and adb all work.
I think it's something quite simple, you have to change your sd card dir on twrp settings since 4.3 adds a 0 folder and puts all data in there.
Sent from my HTCONE using xda app-developers app
That's the weird part, I was still on 4.1 trying to flash 4.3.
With the new 4.3 OTA I thought I might be good to delve into updating my phone today. That was around Noon, it's now 9PM, and I just don't know where else to turn. I know where I screwed up a few things and I feel like I've tried everything. Hopefully you guys will have some helpful suggestions, if not I guess I'll have to bite the bullet.
I'm a noob at rooting. I did root my HTC Evo Shift a year or two ago. Put CM 7.something on it, but I really wasn't happy with the performance so I just RUU'd back to stock and haven't messed with it since. I did leave it rooted for some root required apps though.
I rooted my HTC One a couple months ago using this method:
On gizmodo how-to-root-your-nexus-htc-one-or-samsung-galaxy-s4-990847878 (can't link it because I just signed up)
With 4.3 out I thought I would be able to find a modified update and keep my phone Stock rooted or try InsertCoin or something. My first mistake, I believe, was thinking that root was fine without S-Off.
I've got Drivers and Android SDK on my Win7 machine (I have a Mac and Fedora box if anyone knows any solutions using those OS's). I have on the phone TWRP 2.5.0.0, root, S-On. I try to upgrade to TWRP 2.6.0.0 and that doesn't work so well. I read somewhere that the M7WLS doesn't like that build, and I should try 2.6.0.1, I just strait to 2.6.3.0.
Read some articles on TWRP, watched some videos, so I go to do factory data wipe, cache wipe, dalvik cache wipe, and I do system wipe thinking I need to do that too. Whenever I reboot I basically stop at the HTC splash screen. Mistake number two, I have no OS now.
I hunt down a recovery.img from a site that is supposedly offical Sprint, flash it, try to do a factory restore, no good.
I try getting it back to stock with this:
How to Unroot / Unbrick the HTC One M7: Back to Stock by C4Etech
youtube.com C0G0hKY4P9Y
fastboot oem rebootRUU
fastboot flash zip <rom>.zip
I get errors whether locked or unlocked. I still have S-On and I'm guessing that's why I'm getting signature validation errors.
I try TWRP and ClockworkMod 6.0.4.3 to see if I can mount to my PC, no go.
Fastboot devices recognizes the M7WLS so after more reading I'm going to try ADB sideload. ADB devices does not see my phone. HT Sync is already installed, I remove it and try HTCDriver_4.2.0.001, no go. I remove it and try Universal_Naked_Driver_0.73, still nothing on adb devices. Whether TWRP or ClockworkMod Recovery I can't side seem to sideload.
I go to the store and pick up a cable:
Staples.com Belkin-4-Ports-USB-20-External-Flex-Hub product_IM1QZ5590 (Can't link)
Put
insertcoin-m7-4.0-4.zip AND
Guru_Reset_M7_Sprint_1.29.651.10.zip
on a USB stick, but the phone doesn't recognize it so I can load from either recovery.
I'm sure I've missed a few things in there. Right now I'm sunk, I'm tired, and suggestions are appreciated.
Try buy a USB to go and put a Rom on a Memory stick them using TWRecovery flash the Rom if you have any questions feel free to ask
Demo3827 said:
Try buy a USB to go and put a Rom on a Memory stick them using TWRecovery flash the Rom if you have any questions feel free to ask
Click to expand...
Click to collapse
Thanks for the input Demo. I actually connected it to OSX and the adb devices came right up so I was able to do a rom side load. Thanks again though.
your welcome
pwjohnston79 said:
Thanks for the input Demo. I actually connected it to OSX and the adb devices came right up so I was able to do a rom side load. Thanks again though.
Click to expand...
Click to collapse
your welcome =] anytime :good:
Hi all,
So I wanted to flash ViperOne and saw that it requires 2.6.3.3 for TWRP, so I went and found 2.6.3.4, and went through a big excursion trying to get that to work with ViperOne 5.0.0, and it turns out doing all that somehow really messed my phone up. I don't get service, I can't set the phone up, it has a bunch of problems. I managed to get TWRP 2.6.3.0 working for my phone, and flashed ViperOne 3.5.0 but do not get any service on it, same with just about every ROM I run now. It can't even get to the setup screen, which is a big problem as well.
Any idea what I may have done to mess my phone up so badly? I'm really starting to freak out over here.
Thanks in advance.
Edit: Managed to get a backupe restored from a while ago of ViperOne 3.5.0, but it constantly restarts on me, as well as my data doesn't work. When I turn Mobile Data on it immediately says "Disconnected" and will not find a data network. Any ideas?
BlackHayze said:
Hi all,
So I wanted to flash ViperOne and saw that it requires 2.6.3.3 for TWRP, so I went and found 2.6.3.4, and went through a big excursion trying to get that to work with ViperOne 5.0.0, and it turns out doing all that somehow really messed my phone up. I don't get service, I can't set the phone up, it has a bunch of problems. I managed to get TWRP 2.6.3.0 working for my phone, and flashed ViperOne 3.5.0 but do not get any service on it, same with just about every ROM I run now. It can't even get to the setup screen, which is a big problem as well.
Any idea what I may have done to mess my phone up so badly? I'm really starting to freak out over here.
Thanks in advance.
Edit: Managed to get a backupe restored from a while ago of ViperOne 3.5.0, but it constantly restarts on me, as well as my data doesn't work. When I turn Mobile Data on it immediately says "Disconnected" and will not find a data network. Any ideas?
Click to expand...
Click to collapse
Look here to get it fixed up
http://forum.xda-developers.com/showthread.php?t=2503646
Also the latest version of twrp is 2.6.3.0 that's why everything is messed up you flashed a version from a GSM device
BD619 said:
Look here to get it fixed up
http://forum.xda-developers.com/showthread.php?t=2503646
Also the latest version of twrp is 2.6.3.0 that's why everything is messed up you flashed a version from a GSM device
Click to expand...
Click to collapse
Does it matter that I never actually flashed a ROM for a GSM device? I stuck to only flashing ROMs that are compatible for my device, it was just the recovery I flashed wrongly.
BlackHayze said:
Does it matter that I never actually flashed a ROM for a GSM device? I stuck to only flashing ROMs that are compatible for my device, it was just the recovery I flashed wrongly.
Click to expand...
Click to collapse
The mount points are different on the GSM recovery
BD619 said:
The mount points are different on the GSM recovery
Click to expand...
Click to collapse
OK, awesome. That makes a lot of sense, as it was having a lot of errors involving mounting. I am downloading one of his S-ON firmwares now, and am going to go about attempting to fix it using that guide. I will update with the results.
ok, so i was trying to root my sprint htc one, and everything was going, ok. i unlocked the bootloader simple enough. then i wanted to back up the data, before i tried putting roms on it. well twrp kept saying i only had about 34 mb of space which made no sense since i had formatted it, and only brought back things like contacts and texts. when i checked my phone it said that i had 24gbs. so i couldnt find an answer to this anywhere so while looking through twrp i saw the wipe function. not having seen anything about it, i said, maybe if i reformat it again, itl clear up. so i hit wipe all. well after it was done it only said i had 1.2 gbs, so still confused i went to load my normal os, well i cant. because wiping everything meant the system data the os is on. i spend hours trying to find a fix, as im only able to go between the bootloader and twrp, and i see a sideload option, and after following the steps, i attempt to sideload. everything is going well. Viper looks like its about to install, until at the last second it says install fail. but now i cant even access the recovery menu. literally stuck in the boot loader option. all my contacts and pictures and stuff are backed up, so i have no problem formatting my phone to scratch if it means fixing this, but can anyone point me in the right direction???? i cant find anything on this, ive been searching through this site, and some people with similar issues solve it by sheer luck, but i have no rom back up(since i was trying to do that when i got into this problem) please please help!!!
**edit** i was able to get into twrp by using the recovery steps, though im just back to square 1. is there a guarenteed reliable sideloader that can work?
Look HERE
Try the latest RUU first if it does not work follow the guide from the beginning it will get you fixed up.
raynefr said:
ok, so i was trying to root my sprint htc one, and everything was going, ok. i unlocked the bootloader simple enough. then i wanted to back up the data, before i tried putting roms on it. well twrp kept saying i only had about 34 mb of space which made no sense since i had formatted it, and only brought back things like contacts and texts. when i checked my phone it said that i had 24gbs. so i couldnt find an answer to this anywhere so while looking through twrp i saw the wipe function. not having seen anything about it, i said, maybe if i reformat it again, itl clear up. so i hit wipe all. well after it was done it only said i had 1.2 gbs, so still confused i went to load my normal os, well i cant. because wiping everything meant the system data the os is on. i spend hours trying to find a fix, as im only able to go between the bootloader and twrp, and i see a sideload option, and after following the steps, i attempt to sideload. everything is going well. Viper looks like its about to install, until at the last second it says install fail. but now i cant even access the recovery menu. literally stuck in the boot loader option. all my contacts and pictures and stuff are backed up, so i have no problem formatting my phone to scratch if it means fixing this, but can anyone point me in the right direction???? i cant find anything on this, ive been searching through this site, and some people with similar issues solve it by sheer luck, but i have no rom back up(since i was trying to do that when i got into this problem) please please help!!!
**edit** i was able to get into twrp by using the recovery steps, though im just back to square 1. is there a guarenteed reliable sideloader that can work?
Click to expand...
Click to collapse
Do you still have the memory issue? If so, try running a RUU, and see if that fixes your problem.
If not, just use adb sideload to sideload a ROM. Then wipe everything except internal storage and install the ROM normally.
EDIT: Looks like @BD619 ninja'd me XD
BTW sideload very rarely works when you wipe your sdcard.
BD619 said:
Look HERE
Try the latest RUU first if it does not work follow the guide from the beginning it will get you fixed up.
Click to expand...
Click to collapse
hey thanks for the reply. i followed the guide and after some effort, everything seemed good, but when i was trying to load 5.03 sense 6 rom, i got to the htc start up, then it defaulted back to the bootloader..i went with the deodex version of the download, should i try the odex? or a different version all together?
and now it doesnt want to boot into recovery mode either! going to try redoing the steps, but i just cant figure out what the problem is
**edit* i cant fix twrp. the title loads, but thats it. endless loop
ok i got it to seemingly work. restoring content now. sat in fron of my pc for 15 hours...not even sure where imat or if i got any closer to rooting..smh..thank you everyone who helped. if anyone comes across this
to get out of the endless cycle of recover/loading screen.. delete your twrp, or whatevs your using. even if you have the latest, just redownload it. worked for me. i guess there is a huge difference between the odex and the deodex.i had figured deodex was a more refined version, but maybe it had more complicated software. in any case, if you are at a point where you dont have a base os, and you make it this far, go with odex, it worked for me. htc is big on back up, so i was more worried about having to scrap my phone then i was regaining data, especially with most of my stuff backed up to google drive. hopefully you guys are careful.
now...about this backup issue i had in the first place. how can i fix the storage issue? i have a 32 gb phone minus partition leaves me with over 24gb..why is it going based off the separate phonememory slot? why cant i change it?
Hello everyone! Thank you for your time.
I have a AT&T HTC One from launch day. I recently flashed the AT&T stock ROM for 4.4.2 over an old 4.2 Google Play Edition ROM for my phone. I used ADB Sideload in TWRP 2.5 to do so. I also rooted. After flashing, I was fine for about a day, but then two issues occurred.
1) I can no longer send texts. I receive them fine and the phone works otherwise for calls, Wi-Fi, data, etc. but nobody I've texted is receiving texts. I've tried using a third-party client and the built in one.
2) If I reboot the phone, the phone will boot up normally, work for about a minute or two, then reboot again. This cycle repeats until I flash again. Clearing the caches does not help. I'm still able to access everything until it reboots and getting into the Settings menu seems to prevent this issue from occurring, but I have no idea why this is happening.
I know I can always flash another ROM and those seem to work fine, but I'd really like to stick with stock or a similar-stock experience where I can root. Anyone that can recommend a solution or a ROM that's close to stock would be greatly appreciated! Thank you!
TPMX said:
Hello everyone! Thank you for your time.
I have a AT&T HTC One from launch day. I recently flashed the AT&T stock ROM for 4.4.2 over an old 4.2 Google Play Edition ROM for my phone. I used ADB Sideload in TWRP 2.5 to do so. I also rooted. After flashing, I was fine for about a day, but then two issues occurred.
1) I can no longer send texts. I receive them fine and the phone works otherwise for calls, Wi-Fi, data, etc. but nobody I've texted is receiving texts. I've tried using a third-party client and the built in one.
2) If I reboot the phone, the phone will boot up normally, work for about a minute or two, then reboot again. This cycle repeats until I flash again. Clearing the caches does not help. I'm still able to access everything until it reboots and getting into the Settings menu seems to prevent this issue from occurring, but I have no idea why this is happening.
I know I can always flash another ROM and those seem to work fine, but I'd really like to stick with stock or a similar-stock experience where I can root. Anyone that can recommend a solution or a ROM that's close to stock would be greatly appreciated! Thank you!
Click to expand...
Click to collapse
Did you change your MID & CID back to stock? Did you flash the stock AT&T firmware? You can get the latest from this post.
TPMX said:
Hello everyone! Thank you for your time.
I have a AT&T HTC One from launch day. I recently flashed the AT&T stock ROM for 4.4.2 over an old 4.2 Google Play Edition ROM for my phone. I used ADB Sideload in TWRP 2.5 to do so. I also rooted. After flashing, I was fine for about a day, but then two issues occurred.
1) I can no longer send texts. I receive them fine and the phone works otherwise for calls, Wi-Fi, data, etc. but nobody I've texted is receiving texts. I've tried using a third-party client and the built in one.
2) If I reboot the phone, the phone will boot up normally, work for about a minute or two, then reboot again. This cycle repeats until I flash again. Clearing the caches does not help. I'm still able to access everything until it reboots and getting into the Settings menu seems to prevent this issue from occurring, but I have no idea why this is happening.
I know I can always flash another ROM and those seem to work fine, but I'd really like to stick with stock or a similar-stock experience where I can root. Anyone that can recommend a solution or a ROM that's close to stock would be greatly appreciated! Thank you!
Click to expand...
Click to collapse
Your recovery is also very old ..flash TWRP 2.6.3.3 or newer
do a full wipe when going from GPE to Sense 6
majmoz said:
Did you change your MID & CID back to stock? Did you flash the stock AT&T firmware? You can get the latest from this post.
Click to expand...
Click to collapse
I didn't, but I never changed it to begin with. When I flashed the GPE, did it change that?
clsA said:
Your recovery is also very old ..flash TWRP 2.6.3.3 or newer
do a full wipe when going from GPE to Sense 6
Click to expand...
Click to collapse
I'll flash the new recovery then. Thank you! Also I did do a full wipe, same issues occur.
TPMX said:
I didn't, but I never changed it to begin with. When I flashed the GPE, did it change that?
I'll flash the new recovery then. Thank you! Also I did do a full wipe, same issues occur.
Click to expand...
Click to collapse
You can tell the GPE firmware by the Black bootloader screen.
new recovery and reflash rom and you should be in good shape
clsA said:
You can tell the GPE firmware by the Black bootloader screen.
new recovery and reflash rom and you should be in good shape
Click to expand...
Click to collapse
Updating the recovery helped me reflash the ROM without issue and I'm up and running! Thank you very much!