Related
I am having lots of issues with my phone, touchscreen going crazy, touchscreen locking up until I turn the screen off and back on, phone randomly rebooting and then locking during reboot requiring battery pull, etc, etc. I have tried wiping everything, even using superwipe and tried several different roms and stock and still having issues. I am going to take it to Sprint but I am sure the first thing they are going to do is to apply the latest updates, but I don't want that because I don't want HBOOT 1.5. Any way around this?
I was having a similar issue and i installed a new kernel with a new ROM that works great together. I'm not having any more issues. Try a kernel that marries your ROM.
My money making shooter in 3D.
Just tell then not to apply the updates.
aFoodStampBaby said:
I was having a similar issue and i installed a new kernel with a new ROM that works great together. I'm not having any more issues. Try a kernel that marries your ROM.
My money making shooter in 3D.
Click to expand...
Click to collapse
I don't think that is the issue. I have tried many different kernels and ROMs and even completely stock and still having issues.
Sent from my PG86100 using xda premium
I'm probably screwed regardless as they will probably want to replace the device. If a full wipe and return to stock didn't fix it I don't know what else they can do. I see that you can now flash Roms with hboot 1.5. Is there any reason I should be trying to avoid it anyway?
Sent from my PG86100 using xda premium
i have hboot 1.5 and avoided rooting for a long time after i got my refurb that was shipped with it. I haven't had any problems the only thing that is different is you can't currently gain s-off so you will need img gui from market to flash kernels with out having to plug your phone up to a computer and booting into recovery through command but i haven't had any issues. just a small annoiance of having the plug the phone o a pc when i want to flash a new ROM
I have a friend with a non rooted phone and his digitizer went nuts after the most recent update(VOICEMAIL) sound like the same issue. He took his into Sprint and they confrirmed it was the update that fried his digitizer. He asked me about it and I said never heard of that issue, I told him I will check. Looked on XDA and here it is. Unroot and take it back to sprint. He is receving a new 3vo tommorow.
Sent from my PG86100 using xda premium
Mine does this same thing .. no matter which ROM setup I use. However it only does it when I have bad service, like the radios are causing it idk its driving nuts at times LOL
Sent from my PG86100 using XDA App
bnl552 said:
I am having lots of issues with my phone, touchscreen going crazy, touchscreen locking up until I turn the screen off and back on, phone randomly rebooting and then locking during reboot requiring battery pull, etc, etc. I have tried wiping everything, even using superwipe and tried several different roms and stock and still having issues. I am going to take it to Sprint but I am sure the first thing they are going to do is to apply the latest updates, but I don't want that because I don't want HBOOT 1.5. Any way around this?
Click to expand...
Click to collapse
Doubtful you won't get the HBOOT update if you take it in; try one last thing: Wipe everything and reformat your SD card, there's another thread somewhere around here that was talking about the SD card being a culprit for those type of issues.
If you're STILL having problems, then bite the bullet, you can ask for them to not update your phone but most of the time (read: not all of the time) they'll either refuse to troubleshoot your phone or will update it anyway.
Hope for the best, prepare for the worst.
Bondue said:
i have hboot 1.5 and avoided rooting for a long time after i got my refurb that was shipped with it. I haven't had any problems the only thing that is different is you can't currently gain s-off so you will need img gui from market to flash kernels with out having to plug your phone up to a computer and booting into recovery through command but i haven't had any issues. just a small annoiance of having the plug the phone o a pc when i want to flash a new ROM
Click to expand...
Click to collapse
You don't need to plug in to the pc to flash a new rom. You can do everything with hboot 1.50 except change kernel. And as you mentioned you can use flash image GUI. I never connect to pc anymore.
Sent from my PG86100 using XDA App
JayDaKissEP said:
You don't need to plug in to the pc to flash a new rom. You can do everything with hboot 1.50 except change kernel. And as you mentioned you can use flash image GUI. I never connect to pc anymore.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
agree, no need for a pc anymore, kernal is changeable too,
http://forum.xda-developers.com/showthread.php?t=1192527
lchupacabras said:
Doubtful you won't get the HBOOT update if you take it in; try one last thing: Wipe everything and reformat your SD card, there's another thread somewhere around here that was talking about the SD card being a culprit for those type of issues.
If you're STILL having problems, then bite the bullet, you can ask for them to not update your phone but most of the time (read: not all of the time) they'll either refuse to troubleshoot your phone or will update it anyway.
Hope for the best, prepare for the worst.
Click to expand...
Click to collapse
SD card may have been the issue. I haven't had access to a computer to backup and format the card so i just removed it. So far its working fine, but its only been an hour or so.
Sent from my PG86100 using xda premium
OK so I did the HTCDev unlock perfectly fine, then flashed the Leedroid rom (using cwm) and the kernel (using fastboot), it loaded up and was working great until I made a phone call! Within about 2 minutes of the call it cut out completely (had about 70-75% battery), and I mean it literally just completely shut off and now it won't turn back on. I have done battery pulls, tried a different battery, plugging into charger (but light doesn't even come on!). What is going on?
Sounds like leedroid is your problem
Sent from my PG86100 using XDA
fpineda101 said:
Sounds like leedroid is your problem
Sent from my PG86100 using XDA
Click to expand...
Click to collapse
Yeah I guessed that problem is I can't boot the phone at all, so can't get into fastboot or recovery to get rid of it
Atomix86 said:
Yeah I guessed that problem is I can't boot the phone at all, so can't get into fastboot or recovery to get rid of it
Click to expand...
Click to collapse
Weird... Have u tried vol down+power?
What you could try, take the SD card out and use either another phone or sd adaptor and place on it the PG86IMG.zip file (you can find this in one of the root threads)..........try the volume-down, power button method to see if it boots into recovery.........if this works, then it will read the .zip file.
---------- Post added at 08:34 AM ---------- Previous post was at 08:33 AM ----------
of course, after placing the .zip file on the card, put back into your phone before trying to boot into recovery.
wikdNoob said:
Weird... Have u tried vol down+power?
Click to expand...
Click to collapse
Yes it was one of the first things I tried.
ycats said:
What you could try, take the SD card out and use either another phone or sd adaptor and place on it the PG86IMG.zip file (you can find this in one of the root threads)..........try the volume-down, power button method to see if it boots into recovery.........if this works, then it will read the .zip file.
of course, after placing the .zip file on the card, put back into your phone before trying to boot into recovery.
Click to expand...
Click to collapse
I wish I could do that but I can't boot using any button combination at all
the volume-down/power button method, hold them both down simultaneously for awhile................in the past I've had to do this for about a minute to get it to work.............you may have tried that already but doesn't hurt to try again.
ycats said:
the volume-down/power button method, hold them both down simultaneously for awhile................in the past I've had to do this for about a minute to get it to work.............you may have tried that already but doesn't hurt to try again.
Click to expand...
Click to collapse
Counted two whole minutes while holding them down, nothing :/ beginning to regret buying this now.
that sucks.........did you try finding that .zip file, put on the sdcard, then hold down those buttons for awhile? bTW, when you plug in the charger, do you get a red light?
ycats said:
that sucks.........did you try finding that .zip file, put on the sdcard, then hold down those buttons for awhile? bTW, when you plug in the charger, do you get a red light?
Click to expand...
Click to collapse
Yes I tried placing the file on the memory card, no dice. And no I don't get a red light when plugging into charger. It's as if the ROM or whatever the issue is, has completely destroyed it.
Atomix86 said:
Counted two whole minutes while holding them down, nothing :/ beginning to regret buying this now.
Click to expand...
Click to collapse
Sounds like a hardware issue. How long did you have it before unlocking it? Did you even make sure that the phone ran a few days before screwing around with installing a ROM and Kernel?
Would you buy a new car and not break it in before replacing the factory parts with aftermarket parts?
tgruendler said:
Sounds like a hardware issue. How long did you have it before unlocking it? Did you even make sure that the phone ran a few days before screwing around with installing a ROM and Kernel?
Would you buy a new car and not break it in before replacing the factory parts with aftermarket parts?
Click to expand...
Click to collapse
Used it for about an hour as stock, but that is irrelevant. I wasn't "screwing around" either, I have flashed many phones in my time and always follow the guides provided to completion. The car analogy isn't anything like this, rooting or installing a ROM wouldn't cause a hardware issue any different to a stock ROM would.
Atomix86 said:
The car analogy isn't anything like this, rooting or installing a ROM wouldn't cause a hardware issue any different to a stock ROM would.
Click to expand...
Click to collapse
That is halfway correct. But you said in your original post that you installed a kernel. The kernel is what runs the hardware. If the kernel is set to run the phone out of spec, this could cause hardware issues.
Did you change the max CPU? What about undervolting?
tgruendler said:
That is halfway correct. But you said in your original post that you installed a kernel. The kernel is what runs the hardware. If the kernel is set to run the phone out of spec, this could cause hardware issues.
Click to expand...
Click to collapse
The kernel was the leedroid one, but I thought it only started running that if you booted regularly eg not into fastboot?
Atomix86 said:
The kernel was the leedroid one, but I thought it only started running that if you booted regularly eg not into fastboot?
Click to expand...
Click to collapse
If you installed the ROM and Kernel, you were running it when you made the phone call and the phone went dead. Leeroids kernel, even though he is an excellent developer and I am not saying anything bad about him or his work, changes cpu and undervolting settings which could cause issues with the phone. I am not saying that that is what caused your issue, but it could have been your phone not playing nice with the kernel.
only other thing I would try is leave the battery out for an hour and try again...........but you've probably been down that road.
Yep... sounds to me like a hardware failure. Shiat! :-/
tgruendler said:
If you installed the ROM and Kernel, you were running it when you made the phone call and the phone went dead. Leeroids kernel, even though he is an excellent developer and I am not saying anything bad about him or his work, changes cpu and undervolting settings which could cause issues with the phone. I am not saying that that is what caused your issue, but it could have been your phone not playing nice with the kernel.
Click to expand...
Click to collapse
That is very true, I was just hoping that the kernel "boot up" so to speak could be avoided by opening fastboot and flashing a stock rom back. But as you stated perhaps the undervolting has messed something up. Thank you very much for your insight and help.
ycats said:
only other thing I would try is leave the battery out for an hour and try again...........but you've probably been down that road.
Click to expand...
Click to collapse
Funnily enough this is what i'm going to do now, having a quick google search shows a few people suggesting to do this (im not quite sure what it does, something to do with the phone dispersing the charge it has inside it or some such?), so thanks for the suggestion!
Jakedude2011 said:
Yep... sounds to me like a hardware failure. Shiat! :-/
Click to expand...
Click to collapse
Indeed
ycats said:
only other thing I would try is leave the battery out for an hour and try again...........but you've probably been down that road.
Click to expand...
Click to collapse
Holy crap, this actually worked! Now I just have to find a way of removing that nasty kernel xD
AWESOME! I believe the stock kernel would be in that .zip file if it flashed from recovery.
So, long story short, took the Phone into Sprint so they could look at my headphone jack (was cracked and left ear bud would constantly cut in and out) because its acting up.
Gave the Tech the phone without the battery in it (since he didn’t need to power up the device to clearly see the headphone jack has a huge crack in it) but I left my SD card installed. As he was walking away, I asked him if I could remove my SD card and he let me, then seen that I gave him the phone without a battery. So, I ended up giving it to him (praying he didn’t turn it on and see ViperBoys sick ass ROM booting up) and he accidently pressed the power button turning the phone on. Promptly short after, he removed the battery when the phone was on the HTC screen, didn’t even get the boot animation. I was like OHH $h!t, that gonna mess up my phone & sure as $h!t, it did… Just loops in and out of that screen resetting each time with a little vibrate then looping.
I can get into Fastboot and use ADB, I’ve flashed RUU’s, put Stock image on root of SD and let recovery restore (losing my CWM & my HBOOT 1.400), unlocked, relocked, wiped, thrown, and screamed at it with no luck.
I did do a CWM backup before even setting foot in the Store, so I do have a backup. The 1st thing I tried was restoring it through CWM recovery and that didn’t stop the looping. I can still get into fastboot via power + vol down and adb functionality is still there.
HBOOT is 1.50 and s-on is enabled..
Been reading through threads since lunch and tried many different solutions without success. It seems once a phone is this far gone, people stop responding.
Anyone have any ideas?
New phone will be here tomorrow (free of coarse courtesy of Sprint insurance) but I’ve been without a phone all day and most of yesterday. I’d like to get this one back to stock and booting before I trade it in for the replacement tomorrow
So you ran an RUU and it still didnt work? And you're sure the RUU SUCCESSFULLY ran without any parts of it failing right?
If that's true, there's no hope AFAIK. Try to get it not to show the bootanimation by bricking it further.
yousefak said:
So you ran an RUU and it still didnt work? And you're sure the RUU SUCCESSFULLY ran without any parts of it failing right?
If that's true, there's no hope AFAIK. Try to get it not to show the bootanimation by bricking it further.
Click to expand...
Click to collapse
Yup, RUU ran though fine and finished without error. Thing has been rooted since Revolutionary came out with the 1st rooting scheme for the 3D.. Flashed tons of ROM's never had this problem.
lessegr said:
Yup, RUU ran though fine and finished without error. Thing has been rooted since Revolutionary came out with the 1st rooting scheme for the 3D.. Flashed tons of ROM's never had this problem.
Click to expand...
Click to collapse
My only explanation is that while he removed the battery some of your hardware got borked. This can't possibly be a software issue.
yousefak said:
My only explanation is that while he removed the battery some of your hardware got borked. This can't possibly be a software issue.
Click to expand...
Click to collapse
BUMMER! In case the question comes up I ran "RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed" and it ran just fine.
Hmm, hardware issue. Dont see how I can check for that if it doesnt boot.
Guess I'll just have to wait for the new Phone
try to fastboot oem lock it from fastboot. Then RUU, see if that works.
Why even get this one to work if you are getting a replacement?
Sprint is just going to put the phone back to stock....
jdeoxys said:
try to fastboot oem lock it from fastboot. Then RUU, see if that works.
Click to expand...
Click to collapse
The HTC unlock went as expected. Followed the directions to the "T", then relocked, checked in fastboot (not that I could check anywhere else, LOL) and the phone says "*** RELOCKED***". Ran 2.17.651.5 RUU successfully to the finish. Still looping
WEIRD!
DarkManX4lf said:
Why even get this one to work if you are getting a replacement?
Sprint is just going to put the phone back to stock....
Click to expand...
Click to collapse
Because I just want to know WTF happened!!! Had this Phone since release, abused\used the hell out of it by flashing ROMs constantly, restoring backups, tethering like crazy, emailing, texting, FBing...
No reason for it to crap out on me from a simple mistake, not even of my responsibility, lol!
The only issue I've had with this Phone is that damn headphone jack 1/2 way failing..
Got new phone, terrified to even think about trying to flash new ROM though
lessegr said:
Got new phone, terrified to even think about trying to flash new ROM though
Click to expand...
Click to collapse
LULZ
Same problem with me happened.. Except I had hboot 1.5 and I went one month or two without rooting because I was scared to brick it. I ended up rooting it with desperation and I found my one true love ZR3D rom.
BEAUTIFUL, FAST, plus 4.0 skins ;D. Do it man
Sent from my PG86100 using XDA
Threevo said:
LULZ
Same problem with me happened.. Except I had hboot 1.5 and I went one month or two without rooting because I was scared to brick it. I ended up rooting it with desperation and I found my one true love ZR3D rom.
BEAUTIFUL, FAST, plus 4.0 skins ;D. Do it man
Sent from my PG86100 using XDA
Click to expand...
Click to collapse
DONT TEMPT ME DAMMIT! lol! Just been without a phone for almost 3 days. I'm also seeing a lot of new threads about people experiencing what I've gone through.
Woops, sprint\HTC! once again rooted, and running viperROM.... SWWWWWET!
HBOOT 1.5 and s-on is a *****!
Not to mention... But in Linux, I never got revo recovery to flash... You can do it in windows just do it via fastboot.
Took my Orig cwm bsckup "recovery" & "boot" .img and threw them @ the phone via command prompt.
After cwm was restored, I restored my 4\29\2012 backup that I made before I entered the Sprint store, now my phone is back to the exact same way
It was. Pretty Damn sweet!
So much info here!! I'm truly thankful!!!
Sent from my PG86100 using xda premium
Is anybody having problems getting clockwordmod to work. After I flashed it, it loads, but none of the options take me anywhere. All the options on the recovery take me to a black screen with a hat. Let me know if you've gotten clockmod recover to work, and how you did it? Thanks
i am stuck too, cannot get out of black screen with hat
Not sure which version you're using. But the one on the development section had issues.
Sent from my EVO using XDA
shook187 said:
Not sure which version you're using. But the one on the development section had issues.
Sent from my EVO using XDA
Click to expand...
Click to collapse
I simply downloaded rom manager and told it to flash clockworkmod. So I'm not sure why I'm experiencing this problem. I even re-flashed it several times.
Use the Camera Button!!
mark22179 said:
Use the Camera Button!!
Click to expand...
Click to collapse
Lmao, took me five minutes to figure thus out. Now I don't feel so dumb
Sent from my ltEVO using Tapatalk 2
last i heared CWM was still broken. make sure it has been fixed before you use it. it would corrupt the /misc partition and it takes a few steps to get it fixed when you flash out of CWM into TWRP
Spyderekz said:
last i heared CWM was still broken. make sure it has been fixed before you use it. it would corrupt the /misc partition and it takes a few steps to get it fixed when you flash out of CWM into TWRP
Click to expand...
Click to collapse
Sorry I never came back to the thread, but I believe you are correct. I don't believe CWM works on the EVO LTE yet of what I've heard. As a result I'm just using TWRP which works great.
if you guys get stuck in clockwordmod, simply go to the main menu of it but hitting power button, then HOLD power button... capac lights will blink a couple times, and the device will reboot.
had this same issue.
also, use twrp for now. instruction to flashing it via terminal emulator is on their site! very useful and straight forward method! good luck
Use TWRP and for gods sake done use ROM manager.
Learn how to do things in recovery. Its painfully easy and work 100% of the time. Unlike ROM Manager.
Rom Manager cant save you when it causes a problem and the phone bootloops.
You can also install it via the goo inside app
sent from my EVO LTE
all you guys that are trying to use clockwork are not doing enough research or something because i have seen it over and over a thousand times that its not working for this phone. you have to use TWRP!!! dont ya think something is wrong when everyone thats trying to use it is having problems? lol
I've been running CM as my recovery for a couple weeks now. Sometimes in ClockworkMod, repeated use of the volume up/down buttons can trigger a 'back button disabled' message. When this happens, it becomes unable to select any of the menu options, leaving you with just the logo until you hit power again. For the CM version on the LTEvo, for some reason, the 'back button disabled' mode is the default starting point.
To overcome this, simply repeatedly press volume up &/or down in rapid succession; it usually takes me less than 10 seconds of pressing them. You will know that it worked when you see a message at the bottom stating 'back button enabled'. At this time, you can navigate and select menu items as normal.
Its still not 100% functional as a recovery, however, as USB storage does not work yet.
I've also been using ROM Manager to facilitate my back ups and restores with no problem.
So why would you use a non functional recovery over one that works 100%
Rxpert said:
So why would you use a non functional recovery over one that works 100%
Click to expand...
Click to collapse
For me, its just a matter of personal preference. TWRP is cool, and I used it initially when brought my LTEvo home and rooted it. However, I've used CM since my OG Evo, and I like it. Its simple, fast, and does what I need (except for the storage part, but then I only use that when I forget something).
geniustheanimal said:
I've used CM since my OG Evo, and I like it.
Click to expand...
Click to collapse
Strike 2
I understand that you want choice, but recoveries are probably the most important part of the phone for a rooted user.
Rxpert said:
Strike 2
I understand that you want choice, but recoveries are probably the most important part of the phone for a rooted user.
Click to expand...
Click to collapse
I don't disagree with you here. Nevertheless, I've been able to use CM for all the essentials I've required of it (namely wiping, flashing, backup, & restore) with zero issue. I may revert back to TWRP for the USB mounting, as it saves me restoring, loading, adding something, and then re-wiping again if I forget something when flashing, but I have no qualms hanging with CM for the time being.
Sent from my EVO using xda app-developers app
geniustheanimal said:
For me, its just a matter of personal preference. TWRP is cool, and I used it initially when brought my LTEvo home and rooted it. However, I've used CM since my OG Evo, and I like it. Its simple, fast, and does what I need (except for the storage part, but then I only use that when I forget something).
Click to expand...
Click to collapse
Yeah, I've been using CM for the same reason, I already know it and trust it. But I already switched to TWRP, and I figured it all out now, so it works.
Not trying to troll or anything, but the majority is correct. Clockwork is down and there is no telling when it will get fixed to work with our Evos. TWRP has been around for quite some time now and is trusted, so why not just stick with what's working? Especially when it comes to the important functionality like recovery.
XDA Premium
TWRP is superior: you can queue up files to flash. Plus, its touch interface is about a million times better than CWM's.
I recommend switching. If you're familiar with CWM, you might be wary (I was at first too), but you'll never look back.
So, I stupidly allowed ROM Manager to install an update for me, including updating my TWRP recovery...and now MoBoot is borked. Nothing will boot except WebOS Recovery (just a USB icon) and everything else fails to boot.
Is there a quick way to fix this? I mean, I could wipe the TP and try a fresh MoBoot etc. but I'd rather not if I can save all my data etc.
Thanks all.
Sent from my Desire HD using xda app-developers app
tedrogers61 said:
So, I stupidly allowed ROM Manager to install an update for me, including updating my TWRP recovery...and now MoBoot is borked. Nothing will boot except WebOS Recovery (just a USB icon) and everything else fails to boot.
Is there a quick way to fix this? I mean, I could wipe the TP and try a fresh MoBoot etc. but I'd rather not if I can save all my data etc.
Thanks all.
Sent from my Desire HD using xda app-developers app
Click to expand...
Click to collapse
You could try running ACMEInstaller3 without running ACMEUninstaller. I believe I did that once and nothing got wiped.
That's a good suggestion. Well, it's a suggestion and I like options that make sense, so thank you.
But, before I go for this...any other possibilities?
Sent from my Desire HD using xda app-developers app
If you cant boot anything, I would think AcmeInstaller is your best bet. And if that doesnt work. Use the webOS doctor and start all over.
jsgraphicart said:
If you cant boot anything, I would think AcmeInstaller is your best bet. And if that doesnt work. Use the webOS doctor and start all over.
Click to expand...
Click to collapse
I'm going through ACMEInstaller3 now...did the old "novacom boot mem:// < ACMEInstaller3" line in CMD, and I'm getting scary amounts of linux verbose output pouring down the screen. It's been over 10 minutes now of what looks like error messages. I'm not hopeful!!
Frankly I'll be amased if this works! Right now I'm thinking WebOS Doctor is the way to go.
===
Update: It didn't work. I'm just back at the same point. Nothing will boot beyond MoBoot. Just hangs. I could reinstall a different recovery, but I can't mount the SD in the TP. Maybe I can adb push it???? Any ideas?
I would use Acmeuninstaller first then ACMEInstaller 3 with a regular nightly. Then if that goes to plan use one of your CWM/TWRP backups to restore your settings as they won't be deleted.
Yeah I've got plenty of backups in Ti and CM/TWRP. Hassle though eh!
Still, I'm bored unless I can fiddle.
Sent from my Desire HD using xda app-developers app
tedrogers61 said:
I'm going through ACMEInstaller3 now...did the old "novacom boot mem:// < ACMEInstaller3" line in CMD, and I'm getting scary amounts of linux verbose output pouring down the screen. It's been over 10 minutes now of what looks like error messages. I'm not hopeful!!
Frankly I'll be amased if this works! Right now I'm thinking WebOS Doctor is the way to go.
===
Update: It didn't work. I'm just back at the same point. Nothing will boot beyond MoBoot. Just hangs. I could reinstall a different recovery, but I can't mount the SD in the TP. Maybe I can adb push it???? Any ideas?
Click to expand...
Click to collapse
Can you get into webOS recovery? If it was my TouchPad, I would just go with the webOS doctor. You dont want to lose webOS or its recovery or else you have really bricked your Touchpad.
jsgraphicart said:
Can you get into webOS recovery? If it was my TouchPad, I would just go with the webOS doctor. You dont want to lose webOS or its recovery or else you have really bricked your Touchpad.
Click to expand...
Click to collapse
I can get into recovery from MOBOOT. I get the usual USB icon on the screen. I can't get into anything else though...not recovery, webos or android.
Sent from my Desire HD using xda app-developers app
tedrogers61 said:
I can get into recovery from MOBOOT. I get the usual USB icon on the screen. I can't get into anything else though...not recovery, webos or android.
Sent from my Desire HD using xda app-developers app
Click to expand...
Click to collapse
I would use the webOS Doctor then. As long as you have backups of everything, you don't have to worry about losing your stuff.
jsgraphicart said:
I would use the webOS Doctor then. As long as you have backups of everything, you don't have to worry about losing your stuff.
Click to expand...
Click to collapse
So I decided that WebOS Doctor is my only option now...but when I come to try this tonight, the TP is dead (battery) and charging doesn't seem to be happening.
I've got the large battery icon with red bar across the bottom, so it seems to be getting power. I've checked the twist off part on the charger assembly, that's all okay, but it's just taking an age to charge up. I would have thought that after an hour it would be near complete, and well easily over 30% which WebOs Doctor needs to run.
I've reset it loads of times too (Centre Button and power for 15 seconds)...I read this is supposed to help in CM forums, but I don't think it's making any difference at all.
I can't see how swapping the USB lead will help...I've never had a broken USB lead in my life! This seems like a really daft (clutching at straws) option that is banded about the forums.
Any ideas? How long should this take to charge? Will it ever charge? Does it need a working WebOS to gain access to it's own battery stats? This seems crazy if it's not built into firmware!!
Thanks for your help so far guys.
==
EDIT / UPDATE: So, eventually after near 2 hours the TP sprung into life. The battery must have been severly drained. After that I was able to run WebOS Doctor. The TP has just finished it's reboot sequence, which also took a disturbingly long amount of time, but looks like I'm home free! Now just to re-do the Android install procedure.
I've read people saying they had to leave it charging overnight before seeing signs of life. Just leave it charging for a long while.
jsgraphicart said:
I've read people saying they had to leave it charging overnight before seeing signs of life. Just leave it charging for a long while.
Click to expand...
Click to collapse
it also helps to use the charger/wire that came with it...and to not use that wire for other devices. Messed up my one s port.
Sent from my HTC VLE_U using xda app-developers app
havikx said:
it also helps to use the charger/wire that came with it...and to not use that wire for other devices. Messed up my one s port.
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Well, swapping the cables made no difference for me...and anyway, I'm happy to report that I'm back up and running.
I'm putting FatnCreamy on right now.
Thanks for all your help peeps!
tedrogers61 said:
Well, swapping the cables made no difference for me...and anyway, I'm happy to report that I'm back up and running.
I'm putting FatnCreamy on right now.
Thanks for all your help peeps!
Click to expand...
Click to collapse
I have come across another really odd issue. For some reason I can't put TWRP on now (latest version 2.3.10). It installs fine through Goo.im Manager, but when you try and run it you get an "invalid magic" message and it fails to boot. That then makes it impossible to boot any other mode except recovery without doing a reset first (centre button and power).
I had to go back to non touch CWM 1012 via ACMEInstaller and it works fine.
Any ideas why TWRP would be not working all of a sudden? It all worked fine before this caper when I allower the ROM Manager to do some updates for me. *slaps own forehead*.