So my phone has developed a problem with the touchscreen shortly after I first flashed a custom ROM.
The phone will work fine for about 20 seconds, then it starts glitching up, things open and close as if I've tapped buttons even though I haven't and it doesn't respond when I do tap buttons and icons.
If you've ever tried to use the touchscreen outside when rain has got on the screen, the effect is similar to that. Also the power button often doesn't respond, and I have to press it 2 or 3 times to get the phone to come on or go off.
I'm inclined to think it's not a problem that was caused by the ROMs, firstly because it happens even when I'm at the bootloader screen or in CWM, and also because before I flashed any ROM, the power button had started to become unresponsive although the touchscreen never glitched up like this.
So unless there's some fix that someone knows about (I've tried clearing cache & restoring to factory settings, made no difference), I'm thinking I'm going to have to return the phone to HTC.
I'm worried about this because I've put custom ROMs on - are HTC going to say I've voided my warranty? How can I restore the phone to its original state - ie remove CWM, re-lock the bootloader?
If anyone has returned their WFS after installing ROMs (or tried to!) I'd be really glad to hear whether HTC did the right thing and honoured the warranty or not.
Thanks!
You just Re-Flash the STOCK ROM and Re-Lock the boot Loader. That's enough!!!
You can sent it to HTC. Surely they will do it....(You have this option only now as I know)
If you have Nandroid Backup, can restore the Stock Rom.
or refer this thread:
http://androidforums.com/wildfire-s...ock-rom-ruu-after-bricking-rooted-device.html
_________________________________________
Hope this may be useful. (If really press 'Thanks')
Senthamil said:
You just Re-Flash the STOCK ROM and Re-Lock the boot Loader. That's enough!!!
You can sent it to HTC. Surely they will do it....(You have this option only now as I know)
If you have Nandroid Backup, can restore the Stock Rom.
or refer this thread:
http://androidforums.com/wildfire-s...ock-rom-ruu-after-bricking-rooted-device.html
_________________________________________
Hope this may be useful. (If really press 'Thanks')
Click to expand...
Click to collapse
Thanks buddy.
Before I installed any ROMs, I made a backup with CWM, is that the same as a nandroid backup?
Related
This just crossed my mind; so IF my HTC Desire's screen would break and i would want to send it back for repair, how could i unroot it without being able to use the screen (let's assume the screen is totally f'd up)?
Thanks in advance!
If your device does power on, but you just can't see the screen, you can go into fastboot (power on whilst holding Volume-Down, wait 15 seconds for the sd card to "initialize" and press power) and run an RUU. You won't see whats going on but you can watch your computer for info on the restore process.
I hope this didn't happen to you, because that would really suck. Let's keep it a thought, shall we?
No worries, it hasn't happened to me, i just dreamt of that scenario
Thanks for the reply!
It happened to me... got the dreaded SLCD brick
made a mistake with framework-res.
device stuck in boot screen
Clockworkmod refused to restore the backup it created. Stuck with no other backup
Clockworkmod refused to flash any custom rom. Dont know why but always said signature verification failed.
Downloaded a RUU and flashed it... but turned out it bricked the LCD.
Then Downloaded another RUU and thankfully it restored the device to stock state.
Moral of the story: If you root, always have nandroid backup. If nandroid restore fails and you dont have any other backup, it will be a tough time ahead....atleast till you learn lessons like me..
Hello,
I've installed MildWild CM-4.6 on my HTC Desire and it was running perfectly until yesterday, when I have installed a Camera patch.
Now the phone won't start up (freezes on the first white screen with the green HTC logo).
What should I do to solve this problem?
Thanks a lot!
boot back in to recovery (pull the battery then put it back, vol down+power, select recovery)
then try flashing the original rom.zip straight over the top without wiping anything. you shouldn't lose any data by doing this.
if that doesn't work, you'll probably have to full wipe and flash again.
in future, get into the habit of making a nandroid backup before flashing anything. it avoids situations like this, as you can just a backup if you can't get it to boot. i don't know which camera patch you are referring to, but is it even compatible?
Thanks a lot for your help!
I was missing the "vol down+power" part...
It worked just ok! Had to reinstall de ROM again and the phone come back to life!
The camera patch I used was not the right one, so I guess it caused the crash...
Cheers!
I've recently sold my rooted HTC Desire with MIUI installed.
However the buyer contacted me today saying the phone is not working.
It was working fine when I sold it to him, but now has the following problems:
- It normally loads the boot screen instead of the ROM.
- In the boot screen everything is frozen ( I know you need to wait 10 sec). It takes a few minutes until it actually registers that you pressed something.
- If you actually do get to go to the recovery screen, it is very buggy - it mostly doesn't respond to pressing the optical button, and sometimes it selects something without you pressing anything.
- If you do get to load the ROM (I've managed to install GingerBurst Sense 2.1 ROM. So I've tried this with this and MIUI), it loads in safe mode, and whenever you lock the screen and try to open it again, the phone resets to the boot screen, which again is frozen...
I've managed to wipe the phone and install the gingerbread rom mentioned above, but the problems still persist.
Does anyone have any idea what's wrong with my phone all of the sudden, and how it can be fixed?
Could it finally have died and there's nothing else I can do?
If it helps, the phone is a HTC Desire Bravo S-ON with ClockWorkMod Recovery v2.5.0.7
Thanks for reading!
Liran
liranh said:
I've recently sold my rooted HTC Desire with MIUI installed.
However the buyer contacted me today saying the phone is not working.
It was working fine when I sold it to him, but now has the following problems:
- It normally loads the boot screen instead of the ROM.
- In the boot screen everything is frozen ( I know you need to wait 10 sec). It takes a few minutes until it actually registers that you pressed something.
- If you actually do get to go to the recovery screen, it is very buggy - it mostly doesn't respond to pressing the optical button, and sometimes it selects something without you pressing anything.
- If you do get to load the ROM (I've managed to install GingerBurst Sense 2.1 ROM. So I've tried this with this and MIUI), it loads in safe mode, and whenever you lock the screen and try to open it again, the phone resets to the boot screen, which again is frozen...
I've managed to wipe the phone and install the gingerbread rom mentioned above, but the problems still persist.
Does anyone have any idea what's wrong with my phone all of the sudden, and how it can be fixed?
Could it finally have died and there's nothing else I can do?
If it helps, the phone is a HTC Desire Bravo S-ON with ClockWorkMod Recovery v2.5.0.7
Thanks for reading!
Liran
Click to expand...
Click to collapse
It all looks like it was dropped or moisture got inside of it. I would try with 2.3 ruu, to get it back to fully stock on all partitions and try it there. If problem continues it's a hardware failure, and if everything works great, then Revolutionary (s-off and root) and a choice of custom rom. However I would stick to stock for selling, unless the buyer requests different.
nlooooo said:
It all looks like it was dropped or moisture got inside of it. I would try with 2.3 ruu, to get it back to fully stock on all partitions and try it there. If problem continues it's a hardware failure, and if everything works great, then Revolutionary (s-off and root) and a choice of custom rom. However I would stick to stock for selling, unless the buyer requests different.
Click to expand...
Click to collapse
You are quite right, I have dropped it hard and got it wet several times, so it probably is indeed a hardware fault.
I'll try your suggestions, but it seems to me like I will probably have to refund the buyer.
Thanks for your help.
Liran
Try with disassembling and cleaning of all connectors.
I've just refunded the buyer.
Thank you both for your help
I have read several other threads but no one ever quite seemed to resolve the problem. Shortly after i unlocked my phone (freegee method) i decided to switch back from aosp to stock. after it connected to wifi or data network my phone reboots every time it connects. i tried using a teeny bin but it changes my bootloader and i think thats whats causing my bootloops when i try to provision it. flashing a full stock bin isnt helping either because my phone refuses to fully boot up its just hanging at the bootanimation.
so essentially i can flash myself into a stock based rom but i cant provision anything or switch roms because ill have to repeat the whole process.
oliverpuczyk2 said:
I have read several other threads but no one ever quite seemed to resolve the problem. Shortly after i unlocked my phone (freegee method) i decided to switch back from aosp to stock. after it connected to wifi or data network my phone reboots every time it connects. i tried using a teeny bin but it changes my bootloader and i think thats whats causing my bootloops when i try to provision it. flashing a full stock bin isnt helping either because my phone refuses to fully boot up its just hanging at the bootanimation.
so essentially i can flash myself into a stock based rom but i cant provision anything or switch roms because ill have to repeat the whole process.
Click to expand...
Click to collapse
you need to do a full wipe. This happened to me as well before. This is how I fixed it
in TWRP, go to advance wipe, and wipe system along with data, davilk, an cache. This will fully wipe your rom so be prepared to install a rom afterwards. It will not wipe your sdcard.
Th a t was the first thing i tried. I would like to just be able to flash a full bin at this point. Im really not sure why its not booting fully after flashing and i havent even been able to get a bugreport. If anyone knows how to pull apart one of the bins and all the partitions of this phone ill just do everything 1 by 1
Lngpst to stock (unrooted and locked), root it, use the freegee special sbl unlock method, then flash. I have the sane thing happen every time I try to come back to a stock based ROM after going aosp based. Reboots on any data connectivity.
Sent from my LG-LS970 using xda app-developers app
Every time I try to restore with lgnpst it'll hang up at the boot animation and refuse to fully boot. I used the full zvb to try it. Ive already downloaded it twice in case I had a bad file. Right now I kinda want to know why our phone s do this.
oliverpuczyk2 said:
I have read several other threads but no one ever quite seemed to resolve the problem. Shortly after i unlocked my phone (freegee method) i decided to switch back from aosp to stock. after it connected to wifi or data network my phone reboots every time it connects. i tried using a teeny bin but it changes my bootloader and i think thats whats causing my bootloops when i try to provision it. flashing a full stock bin isnt helping either because my phone refuses to fully boot up its just hanging at the bootanimation.
so essentially i can flash myself into a stock based rom but i cant provision anything or switch roms because ill have to repeat the whole process.
Click to expand...
Click to collapse
1. How and/or what is being changed on the bootloader? Do you mean recovery?
2. When you flash back to stock from ASOP, is it hanging at the 4GLTE screen? If that's what you mean then:
3. If you're stuck at the 4glte screen: To get to stock recovery - Power off phone. You need to hold power button for about 20 sec to get it to turn off. Then press and hold vol down+power - The LG logo will come on, then the capacitive lights. Immediatly let go when the capacitive lights turn on. It takes a few seconds to work. Data wipe/Factory reset. Reboot.
Long story short, I had recently installed the cyanogenmod to my phone, don't like it, tried to flash it back to the stock rom and the rom couldn't install. The installation wizard restarted the phone, now it's stuck on the cyanogenmod boot screen and the notification light lit as if im charging the phone, but it's not plugged up. The bad part about all of this is that the battery isn't removable so now I have to wait for phone to die I guess but is my phone now bricked? Once it dies can I recover from this by booting it up thru recovery mode?
atlJE said:
Long story short, I had recently installed the cyanogenmod to my phone, don't like it, tried to flash it back to the stock rom and the rom couldn't install. The installation wizard restarted the phone, now it's stuck on the cyanogenmod boot screen and the notification light lit as if im charging the phone, but it's not plugged up. The bad part about all of this is that the battery isn't removable so now I have to wait for phone to die I guess but is my phone now bricked? Once it dies can I recover from this by booting it up thru recovery mode?
Click to expand...
Click to collapse
I have the same issue. I suspect the person I let use it tried to use the options menu to reset the phone back to factory specs, which I was warned on here that would brick it, so mine is stuck in the round and round boot screen for CM. I think you're supposed to use the factory reset in CWM to delete personal stuff. I'm trying to figure out how to fix it and if I come up with something I'll let you know.
flash back to stock rom
atlJE said:
Long story short, I had recently installed the cyanogenmod to my phone, don't like it, tried to flash it back to the stock rom and the rom couldn't install. The installation wizard restarted the phone, now it's stuck on the cyanogenmod boot screen and the notification light lit as if im charging the phone, but it's not plugged up. The bad part about all of this is that the battery isn't removable so now I have to wait for phone to die I guess but is my phone now bricked? Once it dies can I recover from this by booting it up thru recovery mode?
Click to expand...
Click to collapse
Good thing is you are not "hard bricked" just "soft bricked." Press the power button and volume up and hold till your phone reboots then immediately press the volume button and power down button to enter recovery.Then do a complete wipe, factory reset, then and only then reflash your stock CWM backup of your stock Rom . Just guessing mind you ,because I do not know every single thing you did before trying to return to stock but you should always do a full Wipe or factory reset before flashing between different roms. If your trying to flash a stock image, not a CWM backup, of your firmware you'll need to first reflash your stock recovery and relock your boot loader.
Is your phone a single SIM or dual SIM? Dual SIM phones have allot more issues on Cyanogenmod . If yours is dual SIM I'd stick to stock Rom or sense based custom roms made for our device. By the way what didn't you like about CM if your on a single SIM phone? It had a few issues but with a few tweaks you can get it working great and it's alot less bloated than stock lollipop. I'm on unofficial 12.1 CM with the a5_chl single SIM and it's fine. Having said that I had to tweak several things and I exempt dual SIM versions from my reasons for me liking this Rom. I get that it's sadly alot buggier for those phones . Let me know how things go in fixing your issue and best of luck.
---------- Post added at 10:43 PM ---------- Previous post was at 10:02 PM ----------
Ddreth said:
I have the same issue. I suspect the person I let use it tried to use the options menu to reset the phone back to factory specs, which I was warned on here that would brick it, so mine is stuck in the round and round boot screen for CM. I think you're supposed to use the factory reset in CWM to delete personal stuff. I'm trying to figure out how to fix it and if I come up with something I'll let you know.
Click to expand...
Click to collapse
First thing, some friendly advice and I truly do mean friendly, not accusing, but you should never let anyone else touch your device when it's in custom recovery. They can seriously mess it up not just"soft brick" it like yours is now.
2nd thing is the factory reset in your custom recovery doesn't have anything to do with your personal files. It's to clean your system and its data so that you can do a fresh install of a different Rom. It's called a "clean flash." A dirty flash is when your upgrading the same custom Rom and you just flash it over the previous version without wiping then clear your Dalvik cache and reboot. These wipes leave your personal files on your internal and external SD card intact unless you specifically wipe then in your custom recovery . They just call it factory reset to make it familiar to the stock Roms use of the term in my opinion. When you have this"soft brick" you can press your power button and volume up to reboot then quickly press power button and volume down to enter recovery. Then factory reset or wipe Dalvik cache if not wanting to reset and reboot one or the other should get you back into your rom.
Hope this helps and good luck plus let me know if this works to resolve your issue. Be happy to help in any way because I have been there myself in the past. Bootloops, soft bricks,etc etc................... If you can name it, I've messed it up.