I'm having a problem getting my phone to connect to my pc, I was able to connect to it about a week ago and transfer a few files(movies) over. But now when I plug it in all it dose is charge, no notification bar, no pop-up asking what I want to do, windows wont chime and detect it either, rebooted both phone and pc, and still nothing. I tried using all the ports on my pc front and back, and a different cable. However my friend can connect his phone to my pc(same port I always used for my phone) just fine, so I plugged my phone into a different computer and it just charges. I even checked to make sure it's still set to ask me on connection and default is to mount as well as debugging is on.
I went into the bootloader to see if I could mount through "fastboot USB" but it wasn't an option, when "adb devices" is used the list is blank, and HTC Sync show's no devices(installed sync to see if the drivers it had would fix things...it did not). I'm on 1.85 rooted but not unlocked and have tried just about everything short of doing a factory restore or running the 1.85 ruu which I'm holding out for last as I don't want to lose my files or root in case doing either doesn't work lol, so any help or advice is greatly appreciated. thanks in advance guys!
Did you check main settings, connect to pc an select your USB option?
WR
Edit to add, I misread your post, it seems you did that already, my bad.
Sent from a CleanRom-V OneX
My HTC Flyer used to do that every once in a while (actually has not done it in a while) and its annoying as hell. Wiping cache and Dalvik cleared it right up. I do it from custom recovery, but if you don't have one installed, Market apps should let you clear the caches as long as you have root (which you mentioned you did). ROM Toolbox is one app that states it has this feature (but I haven't personally used it).
Otherwise, a factor reset should fix the issue.
What ROM are you running? I had this issue when I switched to a JB ROM that wasn't very far into development. It could be the ROM. Try entering recovery and mounting it through there.
Sent from my HTC One XL using xda premium
I tried Rom Toolbox but it tries to boot into recovery, and from there I get a picture of a phone with arrows, and then it becomes a red ! and then I have to reboot, so Im looking for any other app that may let me wipe the caches and will let y'all know when/if I find one that works. As for my rom, I'm running stock 1.85 as I never unlocked the bl, just gained root using the 1.85 method (did it all manually) but that a few months ago lol
>Edit
I ended up using an app called System Tuner to wipe my caches which did not fix my problem so I guess I'll have to try a factory reset *sigh*
Azure_Nall said:
I tried Rom Toolbox but it tries to boot into recovery, and from there I get a picture of a phone with arrows, and then it becomes a red ! and then I have to reboot, so Im looking for any other app that may let me wipe the caches and will let y'all know when/if I find one that works. As for my rom, I'm running stock 1.85 as I never unlocked the bl, just gained root using the 1.85 method (did it all manually) but that a few months ago lol
Click to expand...
Click to collapse
The screen with the phone with arrows is the stock recovery. Its lame if the advertised feature of wiping cache and Dalvik in ROM Toolbox simply boots into recovery (and requires custom recovery), since custom recovery has these features anyway.
Here are a couple more apps that advertise the feature:
https://play.google.com/store/apps/details?id=com.fm.kk&feature=search_result
https://play.google.com/store/apps/details?id=com.j.y.daddy.customizer&feature=search_result
Again, can't vouch for any of them, and haven't used them (since I wipe cache & Dalvik from custom recovery).
BTW, if you do find an app or other method to wipe cache and Dalvik, be sure to reboot, if the method does not already force a reboot.
Are you rooted with a custom recovery flashed. If not rom toolbox will be of no help. The fact that you got the stock recovery tells me you have not yet flashed one. Maybe, if ur rooted download goomanager and install a recovery from there
---------- Post added at 07:57 PM ---------- Previous post was at 07:56 PM ----------
Re-read. Your rooted so just dload goomanager and install twrp recovery. No need to unlock bootloader if you do not feel comfortable unlocking
redpoint73 said:
The screen with the phone with arrows is the stock recovery. Its lame if the advertised feature of wiping cache and Dalvik in ROM Toolbox simply boots into recovery (and requires custom recovery), since custom recovery has these features anyway.
Here are a couple more apps that advertise the feature:
https://play.google.com/store/apps/details?id=com.fm.kk&feature=search_result
https://play.google.com/store/apps/details?id=com.j.y.daddy.customizer&feature=search_result
Again, can't vouch for any of them, and haven't used them (since I wipe cache & Dalvik from custom recovery).
BTW, if you do find an app or other method to wipe cache and Dalvik, be sure to reboot, if the method does not already force a reboot.
Click to expand...
Click to collapse
Thanks for the links, unfortunately when I cleared both cache and Dalvik and rebooted and connected my phone it still only charges so I'm working on using drop box to pull a few backups I made before doing a factory reset or even using a ruu
18th.abn said:
Are you rooted with a custom recovery flashed. If not rom toolbox will be of no help. The fact that you got the stock recovery tells me you have not yet flashed one. Maybe, if ur rooted download goomanager and install a recovery from there
---------- Post added at 07:57 PM ---------- Previous post was at 07:56 PM ----------
Re-read. Your rooted so just dload goomanager and install twrp recovery. No need to unlock bootloader if you do not feel comfortable unlocking
Click to expand...
Click to collapse
I was under the impression I needed my bootloader unlocked to flash a new recovery. The only reason why I never unlocked mine was if something happened I could use my warranty until we got s-off, but at this point if I ever get this problemo fixed I'll just unlock it (might save me from a good bit of head aches later on lol)
Azure_Nall said:
Thanks for the links, unfortunately when I cleared both cache and Dalvik and rebooted and connected my phone it still only charges so I'm working on using drop box to pull a few backups I made before doing a factory reset or even using a ruu
Click to expand...
Click to collapse
Too bad, it was worth a shot. Sorry for the wild goose chase.
Did you try to re-install the HTC drivers (which come with HTC Sync)?
---------- Post added at 03:19 PM ---------- Previous post was at 03:15 PM ----------
18th.abn said:
Are you rooted with a custom recovery flashed. If not rom toolbox will be of no help.
Click to expand...
Click to collapse
What a stupid "feature"! If ROM Toolbox requires custom recovery to wipe cache and Dalvik, then its not a "feature" at all, since all custom recoveries can already do it!
---------- Post added at 03:22 PM ---------- Previous post was at 03:19 PM ----------
Azure_Nall said:
I was under the impression I needed my bootloader unlocked to flash a new recovery.
Click to expand...
Click to collapse
That's what I thought, as well. 18th.abn has written this elsewhere, but I haven't seen it confirmed. If you feel comfortable, give it a try, and let us know. Especially if you are going to run the RUU anyway. Running the RUU will revert recovery back to stock.
If you can flash a custom recovery without bootloader unlock, what's to stop you from flashing custom ROMs?
yeah I had HTC Driver 3.0.0.007 installed before this problem, tried to reinstall them and tried to connect again and nothing, so I removed them again and installed HTC Sync to get the drivers from that and still nothing =\
If I don't need an unlocked bootloader to flash a recovery then really theres nothing stopping me now, albeit there's really nothing stopping me now in any case if I manage to fix the usb mounting problem haha
wellp...I did a factory reset and it still wont connect to my computer, so I'm now at a complete loss at what to do
-Edit
I downloaded goomanager and installed twrp but it shunts me back to the bootloader / fastboot and has a tag *** Security Warning ***
Azure_Nall said:
wellp...I did a factory reset and it still wont connect to my computer, so I'm now at a complete loss at what to do
Click to expand...
Click to collapse
I'm at a loss as well. Seems like it might not be the software issue that has plagued my Flyer, and some other users. Does it look like anything in the USB port is damaged or bent?
Azure_Nall said:
-Edit
I downloaded goomanager and installed twrp but it shunts me back to the bootloader / fastboot and has a tag *** Security Warning ***
Click to expand...
Click to collapse
That's what I thought. If you can install custom recovery without unlocking the bootloader, there is no purpose to unlocking the bootloader, as I think getting custom recovery on the device is the main obstacle to flashing ROMs. Thanks for checking.
well I took it to an at&t store yesterday and they couldn't even get it to connect to their device, so they gave me a number for phone warranty and told me they'll have me do a few trouble shooting steps and then when they realize it's the phone itself send me a new one. My main fear about this is once they get my current phone and they see it's got the security warning and tampered label in the bl will they claim I'm responsible?
Azure_Nall said:
My main fear about this is once they get my current phone and they see it's got the security warning and tampered label in the bl will they claim I'm responsible?
Click to expand...
Click to collapse
Report on here so far, is that AT&T doesn't care about the BL being unlocked, and have given warranty replacements for BL unlocked phones.
redpoint73 said:
Report on here so far, is that AT&T doesn't care about the BL being unlocked, and have given warranty replacements for BL unlocked phones.
Click to expand...
Click to collapse
sweet! best news Iv heard since this problem started (well as best as it gets in any case lol) I also took a look at the port itself on the phone and it dose not seem like anything is bent and/or damaged so I'm not sure exactly where the hell the problem is.
**Update** I got my replacement phone in, and unfortunately it's on the latest firmware =\ on the up-ish side I think I found out why my old oneX stopped reading...a friend of mine built a pc but his USB ports weren't working, turned out he had the usb lead plugged into a firewire header lol
Big thanks to everyone who helped out trying to find out what the heck happened to my phone!
Wait, so you are you saying their was nothing wrong with your phone?
redpoint73 said:
Wait, so you are you saying their was nothing wrong with your phone?
Click to expand...
Click to collapse
to be honest, I'm not sure. A few days after I last had my phone hooked into my pc I plugged it into his and it never connected (which was normal at the time since nothing but his mouse/keyboard was able to connect) he had his plugged into the same port as well most the time but his was still able to connect to other computers. In short, it's just my guess that it's a possibility that my plugging it into his computer might have damaged it as we just found out last night he had the front panel usb lead plugged into a firewire header
Ahh, I see what you're saying. Maybe having the Firewire lead connected to the USB port shorted out the port on your One X?
Related
As the title suggests I am stock gingerbread (the one pushed then oulled back). I would like to remain this way until cm7 has become official for the thunderbolt or at least until it has a few of the bugs ironed out in the rom so we don't have to flash fixes.
Anyway I am familiar with the method of renaming otacerts.zip to otacerts.zip.bak and I have done that.
I wonder if others have had success blocking ota's with that method?
Is anyone familiar with a better method?
recDNA said:
As the title suggests I am stock gingerbread (the one pushed then oulled back). I would like to remain this way until cm7 has become official for the thunderbolt or at least until it has a few of the bugs ironed out in the rom so we don't have to flash fixes.
Anyway I am familiar with the method of renaming otacerts.zip to otacerts.zip.bak and I have done that.
I wonder if others have had success blocking ota's with that method?
Is anyone familiar with a better method?
Click to expand...
Click to collapse
well, renaming files at least works for boot animations & such, so i don't see why it wouldn't work for that ota file. normally, if it's something i don't want/need, i'll either freeze it or remove it entirely. try 'Anttek App Manager'(it's free).
additionally, i wouldn't wait around on an "official" CM7 for the Thunderbolt as that may never happen. i find at least that the latest 'SHIFTAO5P" roms that dhacker is now working on are the most stable ones and seem to have everything working ok.
recDNA said:
As the title suggests I am stock gingerbread (the one pushed then oulled back). I would like to remain this way until cm7 has become official for the thunderbolt or at least until it has a few of the bugs ironed out in the rom so we don't have to flash fixes.
Anyway I am familiar with the method of renaming otacerts.zip to otacerts.zip.bak and I have done that.
I wonder if others have had success blocking ota's with that method?
Is anyone familiar with a better method?
Click to expand...
Click to collapse
Has anyone actually tried the method I mentioned
Did it work
Now that an ota IS being pushed I guess i'll find out the hard way unless someone can help me out?
I got a OTA request right before I updated from Stock Rooted Gingerbread to the current stock rooted.
Now I'm on the current version same as OTA but rooted, renamed otacert.zip.bak but still had in the software update "deferred update pending".
Not sure how to stop this. Any help appreciated.
Can't u accept the OTA n just reinstall Superuser as long as ur S-Off? Been awhile so I can't remember.
Sent from my ADR6400L using xda premium
I accepted the OTA this evening & now I'm stuck. It shut down to then reboot & I ended up stuck at the triangle ! screen for over an hour.
Removing the battery & turning it on allows me to get it back, but as soon as the system is loaded it powers down again to complete the update...
Rooted via Revolutionary method & I'm stuck until someone with more xp comes along & can point me in the correct direction.
My bad.
Tantalin said:
I accepted the OTA this evening & now I'm stuck. It shut down to then reboot & I ended up stuck at the triangle ! screen for over an hour.
Removing the battery & turning it on allows me to get it back, but as soon as the system is loaded it powers down again to complete the update...
Rooted via Revolutionary method & I'm stuck until someone with more xp comes along & can point me in the correct direction.
My bad.
Click to expand...
Click to collapse
Rev method copies its own version of hboot and does not allow an OTA to copy over its own version. I could be completely wrong since i didnt use Revo to root my phone but you may want to try powering to hboot menu if you can power on you can get there, and try flashing the rooted version after full system wipe.
If I helped you in any way please use the thank you button
Could you just restore a nandroid?
I noticed when I updated manually (with help from mike and grlantern) that the file I had renamed otacerts.zip.bak is now back to otacerts.zip. I don't know if the update process created a new version or what but the date next to the zip folder is August, not October.
Is it possible for you to get to hboot by holding volume down as you push power key, then choose recovery, then restore to a nandroid (assuming you ever backed up your rooted rom).
I'm not sure if recovery will still be available though if the update made you s-on.
I'm no expert so perhaps you may want to wait for grlantern to chime in.
recDNA said:
I noticed when I updated manually (with help from mike and grlantern) that the file I had renamed otacerts.zip.bak is now back to otacerts.zip. I don't know if the update process created a new version or what but the date next to the zip folder is August, not October.
Is it possible for you to get to hboot by holding volume down as you push power key, then choose recovery, then restore to a nandroid (assuming you ever backed up your rooted rom).
I'm not sure if recovery will still be available though if the update made you s-on.
I'm no expert so perhaps you may want to wait for grlantern to chime in.
Click to expand...
Click to collapse
1. Have you ever looked at other files in there or files in windows. They don't update files that don't need updates so some files could be from launch of Thunderbolt if the file did not need an update.
2. Revo protects you from an RUU gaining S-On with its version of Hboot. I think the process of returning to stock by flashing an RUU is just for the ADB method which is what I used. I think Revo has to use a different method to regain stock.
If I helped you in any way please use the thank you button
You realize I was trying to give tanalin an idea of how to get his phone working again right?
I just thought he might be able to get into recovery and restore a nandroid or even wipe everything and install a custom rom? Of course I don't know if he can get into cwm.
recDNA said:
You realize I was trying to give tanalin an idea of how to get his phone working again right?
I just thought he might be able to get into recovery and restore a nandroid or even wipe everything and install a custom rom? Of course I don't know if he can get into cwm.
Click to expand...
Click to collapse
I was answering your file question while telling him why his OTA didn't work cause of the hboot problem
If I helped you in any way please use the thank you button
Grnlantern79 said:
1. Have you ever looked at other files in there or files in windows. They don't update files that don't need updates so some files could be from launch of Thunderbolt if the file did not need an update.
2. Revo protects you from an RUU gaining S-On with its version of Hboot. I think the process of returning to stock by flashing an RUU is just for the ADB method which is what I used. I think Revo has to use a different method to regain stock.
If I helped you in any way please use the thank you button
Click to expand...
Click to collapse
I'm in the same pickle as tantalin. Let me ask some dumb questions:
- I can get to the CWM recovery screen. Are you saying I could do a factory re-set, then restore the ROM pre-update? Would I have to have backed up before the OTA (which I didn't, as I only rooted yesterday...argh).
Thanks for your help.
Keep in mind Im a beginner too so you may want to wait for someone with more experience.
CHECK WITH AN EXPERIENCED USER BEFORE FOLLOWING MY DIRECTIONSDIRECTIONS
Yes, you would have had to have a rom to restore to. You could try wiping data, cache, and dalvik cache but I don't know whether phone would boot.
Another alternative would be to shut off phone, take out flash card, copy a custom rom like bamf forever 1.0.8 or the rooted version of the update on the sdcard. Put sdcard back in phone, turn on phone whole holding volume key down. Go to recovery. Wipe data, wipe cache, wipe dalvik cache (under advanced choices)Choose instal from sdcard. Browse to custom rom you put on sdcard. Choose it and install.
Keep in mind Im a beginner too so you may want to wait for someone with more experience.
TOTALLY INADVERTENT SUCCESS!!
I booted into clockworkmod recovery, deleted the cache partition, then under "advanced", I deleted the dalvik cache. I have literally no idea what either of these two things are, but since a factory reset was my worst case scenario, jimmy cracked corn and I didn't care.
Rebooted recovery (accidentally), then rebooted the phone. An error message saying the update failed! Happy day!
Now I can back the phone up properly, and go forward. So worried I'd lose all my apps and information not backed up to my Exchange server! Phew!!!!
If you have a rooted stock phone, and then you accept an OTA or load an RUU, you WILL lose root and the custom recovery program. But you SHOULD still be S-Off. If you are in that position right now, you need to re-flash the custom recovery to be able reload the SU app to regain root.
If you are actually back in S-on, you need to restart the root process from the beginning.
THEN BACK UP IMMEDIATELY BEFORE YOU DO ANYTHING ELSE....
---------- Post added at 03:57 PM ---------- Previous post was at 03:55 PM ----------
Fastlivin said:
TOTALLY INADVERTENT SUCCESS!!
Click to expand...
Click to collapse
Good job.
Fastlivin said:
TOTALLY INADVERTENT SUCCESS!!
I booted into clockworkmod recovery, deleted the cache partition, then under "advanced", I deleted the dalvik cache. I have literally no idea what either of these two things are, but since a factory reset was my worst case scenario, jimmy cracked corn and I didn't care.
Rebooted recovery (accidentally), then rebooted the phone. An error message saying the update failed! Happy day!
Now I can back the phone up properly, and go forward. So worried I'd lose all my apps and information not backed up to my Exchange server! Phew!!!!
Click to expand...
Click to collapse
Excellent! I know that phew feeling all to well!
Now please, PLEASE READ THIS THREAD (You'll be glad you did!)
http://forums.androidcentral.com/showthread.php?p=829066
Grnlantern79 said:
Rev method copies its own version of hboot and does not allow an OTA to copy over its own version. I could be completely wrong since i didnt use Revo to root my phone but you may want to try powering to hboot menu if you can power on you can get there, and try flashing the rooted version after full system wipe.
If I helped you in any way please use the thank you button
Click to expand...
Click to collapse
I was able to get to HBOOT & I followed the steps in the 3rd post of this thread starting at step 5.
I didn't wipe anything (Wipe data, cache, and dalvik), so I don't know what the short term or long term effects are.
I used TiBup & My Backup Pro to restore my SMS/MMS...I don't really want to go any further until I know if I should go back & wipe those things & then do it over...anyone?
I ended up in the exact situation as the op. I went back to stock rooted with perm S-Off and the update got pushed to my phone.
When I noticed the phone trying to update but stuck at the screen you are describing I pulled the battery and went into recovery from hboot. In recovery under mounts there is an option to turn on sd storage or something like that. I've used it before so I knew it would allow me to access the sd card from pc. I then downloaded the rooted rom of the ota. Then I unmounted the phone from pc, rebooted recovery, and went through the normal rom installation.
Sent from my ADR6400L using xda premium
The only issue to me seems if you have something on the phone not backed up you want to keep. Even if the update installs and it updates the bootloader back to s-on, revolutionary root still works so you cam just re-root.
Edit: I recommend you head over to thunderboltforums to at least restore the bootloader to stock s-off if you want to accept the update and re-root.
Sent from my ADR6400L using Tapatalk
Hey All,
First time poster, long time lurker! i have learned so much from this community. thank you all for what you do. anywho lets get on with the show.
Having an issue with my SD. I cannot mount it all of a sudden in CWM. if i /mount/sdcard the error message i receive is something along the lines of error mounting sdcard.
if i try to mount USB storage i receive the error "E: unable to write ums lunfile (no such file or directory exists).
i cannot for the life of me figure out why.
I am Unlocked, rooted, S-on, running Pyro-ice 1.1.3
i have even tried to flash the stock recovery, flash stock rom, but it wouldnt even take that. through bootloader it would recognize the PG59IMG and get to the point where it would be checking the .zip and it would fail about 75% of the way through. i am at a complete loss guys. any help would be greatly appreciated! thanks!
sd issue
sounds like a problem with your sd card. you should format your sd card to fat32. if that doesn't work, go to settings>sd & phone storage>factory data reset and make sure the 'erase sd card' option is checked (assuming you're still on the stock rom).
not on the stock rom. still on pyro-ice 1.1.3.
i have backed up my sdcard and reformatted to fat32 two times now. that doesnt seem to be the issue.
have tried a different sd card as well to no avail. how would i be able to get it to stock if i cant get my phone to read a sdcard? im assuming the answer is YOU CANT... ugh.
EDIT- i have just flashed stock recovery via fastboot and relocked bootloader. PG59IMG was found in bootloader during the scan and it has finally asked me to update. Going through the process now. WIll report back. Hope this short lived thread will hopefully be able to help at least someone in a predicament similiar to mine.
WELLLLLLL. i managed to get back to the stock rom. I unlocked bootloader once again and flashed cwm. once again. no sdcard can be mounted. i was able to mount the sd card with a mounting app in the market before i went stock. but CWM will not recognize the sd whatsoever. i need to flas su to get root so i can finally get s-off.
this is killing me. ugh.
cwm
try to re-flash/upgrade cwm recovery. it could be that your current cwm recovery is corrupted. xmc wildchild22 posted his cwm 5.5.0.4 in the dev section and it has worked well for me.
So here is where I am at now.
Managed to get stock rom installed and running with stock recovery and a relock of the bootloader. After that I was able to use the sd card normally while the phone was on, and in bootloader.
CWM will not mount the sd, nor will it mount usb storage. That being said, I can't install su via cwm to root, which I would then run JB to gain s-off. I flashed and reflashed all available versions of cwm, new and old with the same result.
Its certainly not a hardware issue seeing as I can use the sd normally while its on, and it even scans during bootloader. But cwm just will not take... I'm officially out of ideas... Help????
ota zip
if it's not a hardware issue, there might be an issue with your internal memory. i've seen instances where the recovery mmcblkxxx on internal memory can get corrupted.
so if you have an htcdev unlocked bootloader and jb s-off, you can flash zip's and ruu's now. try to flash the latest ota 1.63.531.2 PG59IMG.zip and see if it fixes the internal memory partition. i did this last week and although i had to re-unlock bootloader, the device kept s-off so you don't have to do jb all over again.
if this doesn't work, i would pm blue or another dev to find out how to actually format and restore the internal memory.
EDIT: have you always had this problem with all recoveries
I'm having this same issue, I can't even mount my SD while on a ROM. This happened after I flashed CWM 6.
Edit: Also the LED is ALWAYS orange now. Even in recovery.
AgentCherryColla said:
I'm having this same issue, I can't even mount my SD while on a ROM. This happened after I flashed CWM 6.
Edit: Also the LED is ALWAYS orange now. Even in recovery.
Click to expand...
Click to collapse
try flashing back to a stable version of cwm...never had these problems :/
---------- Post added at 08:46 PM ---------- Previous post was at 08:43 PM ----------
This problem is also in the not working list in CWM 6....thats why its still an alpha....just flash back to a stable version
AgentCherryColla said:
I'm having this same issue, I can't even mount my SD while on a ROM. This happened after I flashed CWM 6.
Edit: Also the LED is ALWAYS orange now. Even in recovery.
Click to expand...
Click to collapse
That's the very same way mine was reacting as far as the orange light goes after a CWM 6 flash. But I COULD mount my sd card from there. It, for me, ended up being a corrupted user data partition that I couldn't get around for the life of me. I'm now waiting on a replacement phone. Should be here tomorrow.
IMHO, there's something about CWM 6 that isn't playing nicely with SEVERAL of the DS's partitions. That seemed to be indicated when it gave me errors on partitions 31 & 24 in particular when trying to do a test restore after my install.
XMC has added to the top of his OP under the header to not use CWM 6 until some of these issues can be addressed & resolved. I would heed that warning!
---------- Post added at 10:16 PM ---------- Previous post was at 10:15 PM ----------
xmc wildchild22 said:
try flashing back to a stable version of cwm...never had these problems :/
---------- Post added at 08:46 PM ---------- Previous post was at 08:43 PM ----------
This problem is also in the not working list in CWM 6....thats why its still an alpha....just flash back to a stable version
Click to expand...
Click to collapse
Opps. Sorry XMC. I didn't realize you'd responded to this.
WeekendsR2Short said:
That's the very same way mine was reacting as far as the orange light goes after a CWM 6 flash. But I COULD mount my sd card from there. It, for me, ended up being a corrupted user data partition that I couldn't get around for the life of me. I'm now waiting on a replacement phone. Should be here tomorrow.
IMHO, there's something about CWM 6 that isn't playing nicely with SEVERAL of the DS's partitions. That seemed to be indicated when it gave me errors on partitions 31 & 24 in particular when trying to do a test restore after my install.
XMC has added to the top of his OP under the header to not use CWM 6 until some of these issues can be addressed & resolved. I would heed that warning!
---------- Post added at 10:16 PM ---------- Previous post was at 10:15 PM ----------
Opps. Sorry XMC. I didn't realize you'd responded to this.
Click to expand...
Click to collapse
Well I'm currently out a myTouch 4G Slide, can't afford to get it repaired. :Y Was a nice run while it lasted. Hopefully I can figure out how to get it working. I need to get ADB working on my Laptop.
AgentCherryColla said:
Well I'm currently out a myTouch 4G Slide, can't afford to get it repaired. :Y Was a nice run while it lasted. Hopefully I can figure out how to get it working. I need to get ADB working on my Laptop.
Click to expand...
Click to collapse
If you're not getting any partition error messages you MIGHT be able the use jonnycat's method pinned to the top of the developer's section to 'go back'. Mine seemed to be doing great until HBoot got to the user data partition and just hung there. It DID replace my boot & system files that CWM 5 OR 6 wouldn't touch. That is if you can't get ADB running to try what you may have in mind. I wish you ALL the luck in the world my friend!
I take it you're no longer under warranty?
WeekendsR2Short said:
If you're not getting any partition error messages you MIGHT be able the use jonnycat's method pinned to the top of the developer's section to 'go back'. Mine seemed to be doing great until HBoot got to the user data partition and just hung there. It DID replace my boot & system files that CWM 5 OR 6 wouldn't touch. That is if you can't get ADB running to try what you may have in mind. I wish you ALL the luck in the world my friend!
I take it you're no longer under warranty?
Click to expand...
Click to collapse
I have my Deadma5 going, and some coffee brewing. I'm game mode right now.
Sent from my MIUI V4
AgentCherryColla said:
I have my Deadma5 going, and some coffee brewing. I'm game mode right now.
Sent from my MIUI V4
Click to expand...
Click to collapse
I hope they inspire you....the coffee recharges you and it delivers you an epiphany that helps you save your phone. I'm sorry to hear about your's & other's predicament. I was "lucky" I suppose.
AgentCherryColla said:
I have my Deadma5 going, and some coffee brewing. I'm game mode right now.
Sent from my MIUI V4
Click to expand...
Click to collapse
Love deadmau5.
+1 for warranty.
As long as your void sticker is still intact and no water damage, it should be ok.
You should call up htc asap, and figure it out. You may be in the last month or so, but a very good chance (90%+) you're still covered...
Do it! Do it now!!
I'd hate to see you go like this
Sent from my myTouch_4G_Slide using xda app-developers app
That's true! HTC's warranty is for 1 year whether you took TMobile's insurance or not. I didn't have it but was covered by the manufacturer's warranty.
Ok so here is whats up. 1, my SD was fried. Put in a new one, still did not work. Flashed official CWM, then wiped data/cache/dalvik. Phone booted, and SD is working fine. I can mount via CWM.
Thank goodness!!!!
WeekendsR2Short said:
Thank goodness!!!!
Click to expand...
Click to collapse
I'm glad, I can't use my work phone for anything but calls. I used my doublshot as a PMP.
I had my phone rooted and unlocked and was also using CleanROM 4.1 before I decided today to change to CleanROM 4.5.
So, I downloaded the file and went to Recovery and flashed it (it did take very little time with flashing which I found rather strange.) When I rebooted, the phone was stuck at the HTC screen. I figured that I MIGHT have had CWM installed and I didn't know it (I can't be quite 100% sure of this as I thought I DID have TWRP since it was a touch recovery that I had.) Since I was able to boot back up to Fastboot, I said "Let me flash the TWRP recovery file and try again".....Well, I did that and according to the Command Prompt it was successful (showed sending, writing, finished etc....) Once finished, I rebooted back and all I see now is the TeamWin logo in Recovery and THAT'S IT. It won't give me any menu options. If I let it sit, it will reboot back to the HTC screen.
What are my options right now? Is there a specific file I can flash through Fastboot that will allow me to proceed?
I would appreciate the help and I'll be sure to come back and let you know how successful I was. :fingers-crossed:
****BTW, I want to point out that my phone has had this strange message everytime it reboots (over the past few months since unlocked) stating: "This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission....etc..." What does that mean? I don't like that message to appear everytime I reboot my phone. Thanks again!
reflash
Try flashing the boot.IMG from the the zipped ROM you were trying to flash to boot partition through the bootloader (cmd in windows: fastboot flash boot boot.img[enter] after you put The boot.img in the same folder as the adb & cd to that folder) and flash cwm for recovery, then you can reflash twrp
thesm4rt1 said:
Try flashing the boot.IMG from the the zipped ROM you were trying to flash to boot partition through the bootloader (cmd in windows: fastboot flash boot boot.img[enter] after you put The boot.img in the same folder as the adb & cd to that folder) and flash cwm for recovery, then you can reflash twrp
Click to expand...
Click to collapse
I will definitely be trying that. Will be back in a couple of hours and let you know how it went. Thank you!
bbonline said:
I had my phone rooted and unlocked and was also using CleanROM 4.1 before I decided today to change to CleanROM 4.5.
So, I downloaded the file and went to Recovery and flashed it (it did take very little time with flashing which I found rather strange.) When I rebooted, the phone was stuck at the HTC screen. I figured that I MIGHT have had CWM installed and I didn't know it (I can't be quite 100% sure of this as I thought I DID have TWRP since it was a touch recovery that I had.) Since I was able to boot back up to Fastboot, I said "Let me flash the TWRP recovery file and try again".....Well, I did that and according to the Command Prompt it was successful (showed sending, writing, finished etc....) Once finished, I rebooted back and all I see now is the TeamWin logo in Recovery and THAT'S IT. It won't give me any menu options. If I let it sit, it will reboot back to the HTC screen.
What are my options right now? Is there a specific file I can flash through Fastboot that will allow me to proceed?
I would appreciate the help and I'll be sure to come back and let you know how successful I was. :fingers-crossed:
****BTW, I want to point out that my phone has had this strange message everytime it reboots (over the past few months since unlocked) stating: "This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission....etc..." What does that mean? I don't like that message to appear everytime I reboot my phone. Thanks again!
Click to expand...
Click to collapse
In the future I suggest factory wipe even if going from CR to CR. Also, make sure to check the MD5 once you move the file on to your storage.
Butters619 said:
In the future I suggest factory wipe even if going from CR to CR. Also, make sure to check the MD5 once you move the file on to your storage.
Click to expand...
Click to collapse
I did do the factory wipe.
By the way, I tried what I was told to do and nothing happened. It successfully flashes the boot image and recovery, but when it tries to boot into the recovery, it just freezes in the recovery with the word TEAMWIN and a blue background....No menu or options.... I did try several different ways by downloading and installing several versions of the CWM and TWRP, but no success. Any other suggestions? Will I be stuck with this piece of brick now? Please help.
bbonline said:
****BTW, I want to point out that my phone has had this strange message everytime it reboots (over the past few months since unlocked) stating: "This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission....etc..." What does that mean? I don't like that message to appear everytime I reboot my phone. Thanks again!
Click to expand...
Click to collapse
^That right there is normal by the way and will always be there.
Looks like it's time for you to relock your bootloader (don't worry you can unlock it again), download an RUU, and try again.
Butters619 said:
^That right there is normal by the way and will always be there.
Looks like it's time for you to relock your bootloader (don't worry you can unlock it again), download an RUU, and try again.
Click to expand...
Click to collapse
Ughh! Do you know if I will lose any documents/pictures that are in my USB storage? Which RUU do you think is the best in my case? Thanks!
bbonline said:
Ughh! Do you know if I will lose any documents/pictures that are in my USB storage? Which RUU do you think is the best in my case? Thanks!
Click to expand...
Click to collapse
You will lose the contents of your SD card, which is why you should back that up before flashing. Since you were on CR 4.1, I would go with the 1.85 RUU. If you use 2.20, you will add an extra step or two in when it comes to flashing ROMs. But hey, your phone should work again!
Butters619 said:
You will lose the contents of your SD card, which is why you should back that up before flashing. Since you were on CR 4.1, I would go with the 1.85 RUU. If you use 2.20, you will add an extra step or two in when it comes to flashing ROMs. But hey, your phone should work again!
Click to expand...
Click to collapse
I know, silly me. Usually I backup the data and everything goes well and when I don't, there goes my luck! I really appreciate the suggestion.
One quick question, if in the future I need to have the phone sent in for warranty, is this the same procedure I need to follow? Relock and flash an RUU? Will they not know it had been unlocked before?
bbonline said:
I know, silly me. Usually I backup the data and everything goes well and when I don't, there goes my luck! I really appreciate the suggestion.
One quick question, if in the future I need to have the phone sent in for warranty, is this the same procedure I need to follow? Relock and flash an RUU? Will they not know it had been unlocked before?
Click to expand...
Click to collapse
Exact same procedure, but yes they will know. The giant RELOCKED gives it away lol.
Butters619 said:
Exact same procedure, but yes they will know. The giant RELOCKED gives it away lol.
Click to expand...
Click to collapse
Darn.... I just hope I don't have to deal with sending it for any repair. Gave you thanks!
Butters619 said:
Exact same procedure, but yes they will know. The giant RELOCKED gives it away lol.
Click to expand...
Click to collapse
But only if they reboot and look, which from what I've seen here, they never seem to do.
iElvis said:
But only if they reboot and look, which from what I've seen here, they never seem to do.
Click to expand...
Click to collapse
I took my One X back to Best Buy to swap it out just before the return policy expired because my gf dropped it and put a small dent in the casing and I didn't even bother to relock or even RUU my device. I said I had a software issue and couldn't get the OTA. They turned it on and played with it and it had a custom boot animation and a ROM on it lol. They also couldn't get the OTA so they approved the return.
Butters619 said:
Exact same procedure, but yes they will know. The giant RELOCKED gives it away lol.
Click to expand...
Click to collapse
it doesn't say RELOCKED when you run an RUU. It gets rid of everything like Tampered and Unlocked and returns the phone to LOCKED. like it came
---------- Post added at 08:34 PM ---------- Previous post was at 08:31 PM ----------
Butters619 said:
I took my One X back to Best Buy to swap it out just before the return policy expired because my gf dropped it and put a small dent in the casing and I didn't even bother to relock or even RUU my device. I said I had a software issue and couldn't get the OTA. They turned it on and played with it and it had a custom boot animation and a ROM on it lol. They also couldn't get the OTA so they approved the return.
Click to expand...
Click to collapse
hahaha, thank god for company cutbacks sometimes... it makes the employees not give a ****. and rightfully so too!!
the fact that companies cut back to make a few more billion dollars makes me sick anyways. but this is not the place for this conversation. carry-on
trichrome1 said:
it doesn't say RELOCKED when you run an RUU. It gets rid of everything like Tampered and Unlocked and returns the phone to LOCKED. like it came
---------- Post added at 08:34 PM ---------- Previous post was at 08:31 PM ----------
hahaha, thank god for company cutbacks sometimes... it makes the employees not give a ****. and rightfully so too!!
the fact that companies cut back to make a few more billion dollars makes me sick anyways. but this is not the place for this conversation. carry-on
Click to expand...
Click to collapse
Nope once you unlocked it won't ever say locked again. Just re-locked
gunnyman said:
Nope once you unlocked it won't ever say locked again. Just re-locked
Click to expand...
Click to collapse
not true, mine said LOCKED after running the att 1.85 RUU.. I had SUPERcid though if that makes any difference.
trichrome1 said:
not true, mine said LOCKED after running the att 1.85 RUU.. I had SUPERcid though if that makes any difference.
Click to expand...
Click to collapse
You should probably double check that. Anybody with an AT&T One X had to have SuperCID to unlock their bootloader so that wouldn't matter. I have unlocked two AT&T One Xs and run the 1.85 RUU on both (one of them a couple times) and I have run the 2.20 RUU on one. every time it says RELOCKED.
Mine did this to when going to 4.5.
I did the following to get back into Recovery.
Use fastboot to flash the boot.img from the cleanrom 4.5 zip.
"fastboot flash boot boot.img"
I then flashed the recovery (TWRP 2.2.1.4 at the moment) again to the phone.
next I erased Cache.
"fastboot erase cache"
I then used the phone itself to reboot the bootloader and went into recovery. It took about 10 minutes but recovery finally booted.
At this point I had no access to anything on the SD card. so I selected mount and mounted the sd card as disk drive to access it through my PC. I was forced to format the drive at this point and loaded a fresh copy of the ROM onto the drive for flashing.
You probably just got a wrong recovery. The recovery on twrp website didn't work for me. The one I downloaded from the development section works fine.
Sent from my One X using xda app-developers app
trichrome1 said:
not true, mine said LOCKED after running the att 1.85 RUU.. I had SUPERcid though if that makes any difference.
Click to expand...
Click to collapse
Screenshots PLS
Help needed,
Got a brand new HOXL, unlocked yesterday and from AT&T shipped to me in the carribeans. So shipping back is not an option.
Android 4.1.1
software version 3.18
Hboot 2.14
S-On
Boot loader Locked
Two windows 7 laptops
Two usb cables, one official from HTC and another that I had lying around at home
The phone doesn't connects to a Pc and it charges. However the PC does not recognize the device. And usually says something about unidentified usb device.
- I have gone into device manager and tried different things (uninstalling device/leaving device plugged in while reboting the PC...etc) to get it to work.
- And I have the latest drivers installed via HTC sync.
- Tried installing only the drivers and then also tried installing all of HTC sync.
- I can get into fastboot and while there phone is still undetected by the laptop.
- If i try and open recovery I get a screen with a phone picture on it and a caution sign and after a while phone reboots. Don't know if thats normal or if its cause my bootloader is still locked.
Any assistance will be greatly apprecuated. thanks.
Do you have the latest version of HTC Sync Manager? The connection protocol changed from usb mass storage to MTP so I believe you need the latest version. I'd advise uninstalling HTC Sync and all drivers and downloading HTC Sync Manager from HTC again. The caution sign when entering recovery is normal, that's normal for stock recovery. Are the usb ports on your laptop 2.0 or 3.0?
Sent from my Evita
Thanks. I was able to sort the problem and I've gone on to unlock bootloader, flash twrp and root. Haven't done s-off yet or tried any new Rom. Wanna get a feel of the stock Rom first that way I have a better handle on what I Want or dont want.
My fix was kinda strange. Previously had HTC sync manager fully installed and then only the drivers of HTC sync installed. Didn't uninstall anything. Put my phone into hboot and then went into fastboot then plugged it in. The laptop discovered the phone and stayed downloading a "android 1.0" driver. My hox could now be recognized as a usb device only in fastboot. Test the phone, and this time around windows downloaded and installed all the necessary drivers.
Strange.
Any Rom recommendations? Looking for something as close to stock as close to stock as possible. Currently leaning towards the viper x sense5 Rom.
Sent from my HTC One X using xda app-developers app
I won't say any recommendations, but make sure that everything you flash is from this device forum ONLY.
Sent from my One X using Tapatalk
Lol.... of course. That goes without saying. I've been around for quite a bit.
Anyways, S-offed and all that. Gonna let the phone run as stock for a week or two while I explore my rom options.
Lorddeff07 said:
Lol.... of course. That goes without saying. I've been around for quite a bit.
Click to expand...
Click to collapse
Nothing here "goes without saying". Its far better for folks to point out the seemingly "obvious"; instead of folks bricking due to something that went unsaid. Aside from your post count and join date, we know nothing of your experience. And even so, just because you know it, does not mean that everyone reading this thread will also know it. So its just good all around to point out even the simple things.
---------- Post added at 11:31 AM ---------- Previous post was at 11:29 AM ----------
Lorddeff07 said:
Any Rom recommendations? Looking for something as close to stock as close to stock as possible. Currently leaning towards the viper x sense5 Rom.
Click to expand...
Click to collapse
Since you've been around for a while, you should know that asking for ROM recommendations is a no-no on XDA. Just look through the ROMs and see what fits your needs and wants. And its not hard to figure out which ROMs are well liked without asking.
---------- Post added at 11:33 AM ---------- Previous post was at 11:31 AM ----------
Lorddeff07 said:
- If i try and open recovery I get a screen with a phone picture on it and a caution sign and after a while phone reboots. Don't know if thats normal or if its cause my bootloader is still locked.
Click to expand...
Click to collapse
Its normal, as that is the stock recovery. You won't have a custom recovery until you unlock the bootloader and flash a custom recovery.
Get what u mean Redpoint.
And to everyone else this problem has been resolved. I have done everything including using a custom Rom. For those that may have a similar problem this was my fix.
- make sure usb debug is on. put ur phone in hboot and plug to computer. Windows should detect the phone and install one driver "android 1.0
- with phone still plugged to computer, reboot phone. Windows should detect device and install all other drivers.
- done.
Sent from my HTC One XL
I know this isn't technically the right section for this but I put it here in hopes more people would see it. This is very important for anyone rooting using the dirtysanta method and perhaps other methods as well. It would be nice if this could get a sticky because people need to see this or this problem is going to keep occurring. I'm seeing it all over the threads.
DO NOT FACTORY RESET FROM INSIDE THE ROM. DO NOT USE LG's BUILT IN FACTORY RESET IN THE PHONE OR YOU WILL GET STUCK IN RECOVERY. Use the factory reset option inside of TWRP if you want to do a factory reset.
There have been many people (myself included even though I knew better and told myself not to do it before I did) who have got stuck in recovery because of this and it's not common sense to get out of it. I've been rooting and messing with this stuff for over 5 years and for 2 hours tried every trick I knew and nothing worked. What did finally end up working for me personally is this:
*restore your full stock backup (if you have one)
*after the backup is restored, in TWRP, go to mount, and mount the system. Check the box and press the mount USB storage button
*power off device
*use the button combo to boot into TWRP. It's volume down + power (hold them down), as soon as you see the LG logo let go of power for a brief moment and continue to press and hold both buttons until a white screen comes up. Choose yes for the next two options. This will bring you back into TWRP.
*now go back to mount and check system, and press the mount storage button, and reboot system.
lol this is only because it give you your stock boot.img. So if you factory reset, you have to flash SuperSU, no need to freak out.
If you format /system, you will need to flash a ROM, if the ROM does not flash SuperSU, you will h ave to flash it.
That's all folks!
That said, who wants a VZW Custom ROM and Kernel? Making the thread now. Identical to my H918 5.1 MOD ROM
Tilde88 said:
lol this is only because it give you your stock boot.img. So if you factory reset, you have to flash SuperSU, no need to freak out.
If you format /system, you will need to flash a ROM, if the ROM does not flash SuperSU, you will h ave to flash it.
That's all folks!
That said, who wants a VZW Custom ROM and Kernel? Making the thread now. Identical to my H918 5.1 MOD ROM
Click to expand...
Click to collapse
I tried flashing supersu.zip but that wouldn't work either. I challenge you to factory reset in the rom and then once stuck in recovery flash a new rom and the supersu zip and see if that works. I did this several times and it wouldn't work. I tried it with flashing a rom, and after restoring a backup. What appears to be happening is the system isn't mounting and it doesn't recognise that you have a ROM installed.
Not freaking out either, just trying to let people know not to factory reset inside the rom but use TWRP. There have been many people with this issue.
imucarmen said:
I tried flashing supersu.zip but that wouldn't work either. I challenge you to factory reset in the rom and then once stuck in recovery flash a new rom and the supersu zip and see if that works. I did this several times and it wouldn't work. I tried it with flashing a rom, and after restoring a backup. What appears to be happening is the system isn't mounting and it doesn't recognise that you have a ROM installed.
Not freaking out either, just trying to let people know not to factory reset inside the rom but use TWRP. There have been many people with this issue.
Click to expand...
Click to collapse
Oh, sorry. I overlooked something. That you had in huge bold caps the words IN THE ROM lol, my bad. I've never factory reset from within the ROM.
But my post stands when factory resetting from TWRP.
Tilde88 said:
Oh, sorry. I overlooked something. That you had in huge bold caps the words IN THE ROM lol, my bad. I've never factory reset from within the ROM.
But my post stands when factory resetting from TWRP.
Click to expand...
Click to collapse
Yea I knew better too, that's the bad part. In 5+ years I've never factory reset while in a rom when I have root and TWRP installed. Before I did it I even told myself it was probably a bad idea and I should just use TWRP. But my lazy conscience said "ahhh what the heck! just do it, it's too much trouble to boot into TWRP and besides, it might work ok" I hate my lazy consicence :'(
Exactly what I did and exactly what happened.
Gonna try this in the AM. One question...
If I'm able to flash back to "stock" using a deoxed stock rom, how can I then get rid of the boot warning so I can return this device to T-Mobile?
mrbigdrawsz said:
Exactly what I did and exactly what happened.
Gonna try this in the AM. One question...
If I'm able to flash back to "stock" using a deoxed stock rom, how can I then get rid of the boot warning so I can return this device to T-Mobile?
Click to expand...
Click to collapse
You'll need to return to full stock. I can't verify it works but this thread here claims to have a method for returning to stock.
imucarmen said:
You'll need to return to full stock. I can't verify it works but this thread here claims to have a method for returning to stock.
Click to expand...
Click to collapse
Well pray for me. Downloading now and will try first thing tomorrow.
mrbigdrawsz said:
Well pray for me. Downloading now and will try first thing tomorrow.
Click to expand...
Click to collapse
Did it work for you? Also since there is no t mobile rom there what did you use?
thegameksk said:
Did it work for you? Also since there is no t mobile rom there what did you use?
Click to expand...
Click to collapse
I used this guide https://goo.gl/ZHZPfO and it worked perfectly. Had a little stress when attempting to flash the stock recovery, but after installing two again, I was able to revert back to stock. Locked bootloader and it's as if I never did anything but boot up the stock OS.
Returning to T-Mobile today and just waiting on my Oneplus 3T to ship (granted I'm pissed off because the 128gb version is out of stock).
mrbigdrawsz said:
I used this guide https://goo.gl/ZHZPfO and it worked perfectly. Had a little stress when attempting to flash the stock recovery, but after installing two again, I was able to revert back to stock. Locked bootloader and it's as if I never did anything but boot up the stock OS.
Returning to T-Mobile today and just waiting on my Oneplus 3T to ship (granted I'm pissed off because the 128gb version is out of stock).
Click to expand...
Click to collapse
Glad you got it fixed.
Just for the record, this thread isn't for helping people get back to stock, its main focus is to warn people not to factory reset inside the rom. Then I just shared the method that worked for me to get out of being stuck in TWRP. Not saying you implied any different, I'm just clarifying for anyone that may read in the future. It's awesome return to stock methods are now popping up which are usually good for fixing all sorts of issues.
Enjoy your OnePlus 3T