Related
I have been running the newest release of the sprint rom since it came out a few weeks back. I today loaded the HTC Home app and my phone wanted to reboot and when I did, it comes back up locked up every time.
1. Screen still reacts to touch as far as backlight turning on
2. Somtimes the power button puts it to sleep and wakes it back up
3. Have performed multiple resets (using the sytlus in the reset button), anyway to do a hard reset?
4. Active sync wont connect
5. Never have custom rom'd this before, always have used the sprint roms. Just activesync'd and ran their installer.
Any ideas how to jumpstart a reload of the sprint rom??
Ok first of all...your phone is NOT bricked.
A "bricked phone" is exactly that...bricked. As in it doesn't do ANYTHING and can be used only as a paperweight (i.e. like a brick). People always post that their phone is bricked when it isn't even anywhere close to being bricked. In fact, it is VERY difficult to brick the Titan.
In your case, all you need to do is hard reset. If it locks up right at boot and won't even allow you to hard reset, just reflash the rom. Very simple.
wacktool said:
I have been running the newest release of the sprint rom since it came out a few weeks back. I today loaded the HTC Home app and my phone wanted to reboot and when I did, it comes back up locked up every time. I have pulled the batter, and the data card. Multiple resets (using the stylus to press the reset button). Any way to jumpstart the rom installation to reinstall it? Any suggestions?
Click to expand...
Click to collapse
Sounds like you need a hard reset. It will take you back to your default Sprint ROM without the Home app. You will lose all data though.
See here:
http://wiki.xda-developers.com/index.php?pagename=TitanForBeginners
wacktool said:
I have been running the newest release of the sprint rom since it came out a few weeks back. I today loaded the HTC Home app and my phone wanted to reboot and when I did, it comes back up locked up every time. I have pulled the batter, and the data card. Multiple resets (using the stylus to press the reset button). Any way to jumpstart the rom installation to reinstall it? Any suggestions?
Click to expand...
Click to collapse
When you indicate that "it comes back up locked up every time" can you elaborate on the exact symptoms? Does the phone boot and when the home screen attempts to load, the phone freezes/locks and stops responding?
If this is the case, the phone is far from bricked. What you can do is hard-reset which will reset it to the way the rom comes.
Best regards,
-boggsie
wacktool said:
I have been running the newest release of the sprint rom since it came out a few weeks back. I today loaded the HTC Home app and my phone wanted to reboot and when I did, it comes back up locked up every time. I have pulled the batter, and the data card. Multiple resets (using the stylus to press the reset button). Any way to jumpstart the rom installation to reinstall it? Any suggestions?
Click to expand...
Click to collapse
If you don't have safe mode (through PocketPlus or other), or through a SPB Backup (or similar) there are very few ways to get this back safely. Hard reset is probably the way to go if you can't get around in the OS. I love PocketPlus safe mode, it has saved me many, many times.
Edit: I agree with the "bricked" comment, it is an attention grabber if anything but almost always inaccurate. Can people say stuck instead please?
ande8150 said:
Sounds like you need a hard reset. It will take you back to your default Sprint ROM without the Home app. You will lose all data though.
See here:
http://wiki.xda-developers.com/index.php?pagename=TitanForBeginners
Click to expand...
Click to collapse
Lol I LOVE your avatar... how fitting for a thread such as this
Oh, and on topic... I didn't see anyone actually posting HOW to hard reset without flashing... this is obviously an easy first step. If you don't intend on changing your ROM, you should be fine doing the following:
hold down the 2 softkeys (the ones with Dots on em) and press reset with stylus... follow instructions on screen
EDIT: Oh, I guess that's in the Wiki! Good stuff those wiki's
gc14 said:
A "bricked phone" is exactly that...bricked. As in it doesn't do ANYTHING and can be used only as a paperweight (i.e. like a brick). People always post that their phone is bricked when it isn't even anywhere close to being bricked. In fact, it is VERY difficult to brick the Titan.
Click to expand...
Click to collapse
serfboreds said:
Edit: I agree with the "bricked" comment, it is an attention grabber if anything but almost always inaccurate. Can people say stuck instead please?
Click to expand...
Click to collapse
Just changed my avatar to make you smile....
That avatar is badass lol
I'm smiling
ande8150 said:
Just changed my avatar to make you smile....
Click to expand...
Click to collapse
That is awesome, don't change it.
serfboreds said:
That avatar is badass lol
Click to expand...
Click to collapse
gc14 said:
That is awesome, don't change it.
Click to expand...
Click to collapse
Yup, it's here to stay.
I am trying to unlock my bootloader so im using the automatic thing..
My phone says failed to boot 0x1000. it warned me that this might happen and that i can use the volume keys to select fastboot but the volume keys arent doing anything..
help!
when youre phone is first booting, the very first thing you have to do is hold the down volume key (instantly after boot starts) and then press the up volume key to select it
ok so i did that and now at the bottom it says
"current choice is mode:
fastboot
starting fastboot protocall support"
the next step it tells me to do is turn off the phone while i press and hold volume down
but it wont let me turn it off.. the power button isnt doing anything
please if somoene could help mee
skip that step. You already did that step (what I just told you to do). You now have to run the fastboot protocols that they tell you to use in the "pudding" thread
edit: don't worry man. I'm here to help. Just keep telling me whats going on
i THINK i MAY have figured it out!!!
the phone now has the big Motorola sign with dualcore technology under it and it says
unlocked at the top right.
ill let you know if it eventually finished turning on..
EDIT:
does it usually take this long??????
sounds like you took care of it. If it says unlocked, youre good!
Good job man
does it ever boot? does it take a long time the first boot?
its still at that screen. -- never done this before if you cant tell.
no worries man. Give it a couple minutes!
You'll learn a lot as you keep doing more and more. In case your contacts get deleted, be sure to check out an app called "contact restoration" in the app market from moto. Works great. And be sure to check out faux123's 1.3 OC kernel (most stable I've seen so far) and either the Alien 4 rom or CyanogenMod7 pre-beta 3 (what I run and I love it)
okay ill give it a couple more minutes hopefully itll do somtehing
and yeah I want to put the alien rom on here.. is cm7 pre beta 3 better working than alien?
what do you think
EDIT:
its still at that same screen.. should i be worried yet?
well, for you, I'd suggest running alien build 4 with the alien 4 theme. It runs really smooth and has very few issues. You should do some research into CM7 though...I can do lots of cool **** with my phone that I never knew was even possible with a cellphone
The only problem is it's not a very good "all day, everyday" rom. Some things dont work and there are some quirks but all basic functions work well
stillllll..
man...that's a little unusual. I've never heard of it doing that. Let me ask a buddy real quick
okay because its still doing it haha gt back to me soon !!
That happened to me, just pull battery and reset
Sent from my Atrix 4G
andrewxu said:
That happened to me, just pull battery and reset
Sent from my Atrix 4G
Click to expand...
Click to collapse
YESS YOU SAVED MY LIFEEE
i dont know why i didnt try that in the first place but THANK YOU SO MUCH !!!!!!!!
lol took the words right out of my mouth. I just wanted to be sure it wouldn't brick your phone before I told you to do it!
Good luck with roms and kernels and such
spitefulcheerio said:
lol took the words right out of my mouth. I just wanted to be sure it wouldn't brick your phone before I told you to do it!
Good luck with roms and kernels and such
Click to expand...
Click to collapse
thank you so much for all of your help
one more question -- which rom do you think is best?
Alien 4 (or any build) for a standard, everyday rom for sure.
yeah thats the one i am downloading right now.
I rooted the phone now and installed superuser.
once i download the rom and put it in my phones storage do i get intwo cwm by holding power and volume down ?
and then do i just flash it
If I power down it boots, starts loading, then reboots. not sure if that counts as a soft brick or not, but I've discovered a work around, if I re-root it using roloracer's instructions, and let it boot a few more times while plugged in, I can get it back, then I dare not cycle power. It's almost like a tethered jailbreak on the old iphone.
Anyway, I've been unsuccessful in finding anyone else mentioning this type of issue, so obviously it's never happened to anyone on the face of the planet before.
Does anyone have any links, search terms i may know have thought of, solutions?
I rooted a couple of weeks ago. Nothing is frozen, what I did freeze was on the list of thinks that were ok, and i un-froze it with TB.
Sorry, this is the AT&T Galaxy Note i717.
Thanks.
Do u have cwm? ? If so get into recovery and wipe cache see if that works post back ill help as much.as i can
Sent from my SAMSUNG-SGH-I717 using xda premium
I haven't installed cwm, nor anything beyond the rooting. I presume I should, then wipe the cache?
Install and flash clockwork mod recovery and then do a wipe BUT PLEASE make sure u have a back up before u do any wipes and changing Roms and such
Sent from my SAMSUNG-SGH-I717 using xda premium
Do you have any backups?
Sent from my SAMSUNG-SGH-I717 using xda premium
armyboy11b said:
Do you have any backups?
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
yes. I've now installed CWM and did a backup there, a rather lengthy one, as far as time goes.
I wiped the cache, with no positive effect. I ultimately wiped the dalvik cache, and now i simply get the AT&T boot screen. So I am now restoring my cwm backup, hoping at least I'll be back where I was.
As it stands now, or before I wiped the dalvik cache, which you did not mention so that may well be my error, I was in a loop. unable to connect via USB for any length of time. BUT I additionally have everything backed up, as far as apps, settings and my data seperately of the cwm backup.
I am considering trying the odin unroot process.
later that day:
I had to get some sleep I was falling asleep at my laptop. I reinstalled cwm, using the touch one here earlier this morning, I again wiped the cache, it still looped, I did another backup in cwm, then went to bed with it plugged in beside me after about 30 minutes I saw it was done, and I rebooted it, and left it, it rebooted once maybe more, but when I got up later it was up.
I'd intended to do all this today, but I accidentally had the power button resting on my finger and that began this early morning session. I have a phone back, but will wait before I intentionally cycle power again. I do have a number of flashes counted today that weren't there yesterday. i'll see about zeroing those out later.
In download mode it doesn't boot loop, so I do not think it's a hardware issue. But at least now it's up long enough to back it all up to my PC.
Thanks very much
that is cool
Man, being over 50 I can barely make out those image verifications!
So no one else has run across this with mashi/roloracer root? I did it exactly as it said to to a stock i717.
I'm going to wait to cycle power again, to test if it's fixed, when I know I will have a few hours to dedicate to trying to get it all back. I'd rather have it rooted and when an ICS ROM is out try that. Like I said I'm a complete android noob, but not to Unix/AIX/Linux, PC's or Macs. I had to do macs because no one else wanted to back in the `90's when apple was failing.
So is this a "soft brick" this boot looping?
Thanks again.
bigbuc said:
Man, being over 50 I can barely make out those image verifications!
So no one else has run across this with mashi/roloracer root? I did it exactly as it said to to a stock i717.
I'm going to wait to cycle power again, to test if it's fixed, when I know I will have a few hours to dedicate to trying to get it all back. I'd rather have it rooted and when an ICS ROM is out try that. Like I said I'm a complete android noob, but not to Unix/AIX/Linux, PC's or Macs. I had to do macs because no one else wanted to back in the `90's when apple was failing.
So is this a "soft brick" this boot looping?
Thanks again.
Click to expand...
Click to collapse
hey buddy sorry been realllll busy with work and such how did everything go are u all set? is it working let me know if u need help!!! as i said before sorry i didnt reply back man been very busy but please feel free to ask for help if u still need it
armyboy11b said:
hey buddy sorry been realllll busy with work and such how did everything go are u all set? is it working let me know if u need help!!! as i said before sorry i didnt reply back man been very busy but please feel free to ask for help if u still need it
Click to expand...
Click to collapse
Well, it's still acting kind of like a tethered boot. It takes a few hours of it cycling power, plugging in/ unplugging and suddenly it 'decides' to stay up. No one else has reported this issue that I have found. I've uninstalled several apps I suspected, like 'The Weather Channel', and anything else I can find that runs in the background by itself, that I don't need... It does it everytime I power down... so I never let it get below 5% before I run to plug it in... Battery life is kind of sucky anyway.
My PC healed itself regarding seeing the phone MTP style.
I wipe the cache, re-root it ala mashi/roloracer then it'll start to settle down some. Curious about UNrooting it, but not real clear on how that's done, as most instructions are in shorthand leaving out (to me) an obvious step here and there.
I'd rather have it rooted, I've bought titanium backup, and use a few others utils that require root.
If I installed a different ROM that might help... or might not... I'm fairly certain it's not the phone, at least not a 'short' type thing where it reboots on it's own... I SAY reboot, it's actually not rebooting since it doesn't show the samsung and at&t logo, it just reloads the UI.
Point me anywhere and thanks again. I clicked the 'thanky' button.
bigbuc said:
Well, it's still acting kind of like a tethered boot. It takes a few hours of it cycling power, plugging in/ unplugging and suddenly it 'decides' to stay up. No one else has reported this issue that I have found. I've uninstalled several apps I suspected, like 'The Weather Channel', and anything else I can find that runs in the background by itself, that I don't need... It does it everytime I power down... so I never let it get below 5% before I run to plug it in... Battery life is kind of sucky anyway.
My PC healed itself regarding seeing the phone MTP style.
I wipe the cache, re-root it ala mashi/roloracer then it'll start to settle down some. Curious about UNrooting it, but not real clear on how that's done, as most instructions are in shorthand leaving out (to me) an obvious step here and there.
I'd rather have it rooted, I've bought titanium backup, and use a few others utils that require root.
If I installed a different ROM that might help... or might not... I'm fairly certain it's not the phone, at least not a 'short' type thing where it reboots on it's own... I SAY reboot, it's actually not rebooting since it doesn't show the samsung and at&t logo, it just reloads the UI.
Point me anywhere and thanks again. I clicked the 'thanky' button.
Click to expand...
Click to collapse
Have u done a factory reset before flashing to ur back up?? If not it will cuase serious issues factory reset/wipe cache/wipe dalvik cache
Sent from my SAMSUNG-SGH-I717 using Xparent ICS Blue Tapatalk 2
Do all three wipes like I said earlier then flash a fresh rom and u should be fine man hope that works for u pm me if need better instructions or help
Sent from my SAMSUNG-SGH-I717 using Xparent ICS Blue Tapatalk 2
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 have an AT&T LG Optimus G (E970). However, I found out that it's pre-release hardware (yes, it says "nOt foR sale***" on the side of the phone, but it was in a case), and I've bricked it trying to root it the standard way (using LGNPST), and it now boot loops 3 times before displaying "Security Error" under the LG logo. I can't get it back into download mode, nor does a factory hard reset (the only mode I can get it into) work.
A bit of background info:
The original firmware was E97009j. It was unable to download the OTA JB update. I tried to install that stock update through LGNPST since the phone couldn't be seen through ADB. From there I planned on rooting and everything else. Yes, I should have never tried messing with pre-release hardware, but in theory, since it was a review unit, the hardware itself should've been identical to what is sold in stores. Also, and more importantly, I didn't realize it was pre-release until after I bricked it.
Luckily this isn't my daily phone, but I'd like to get it fixed...
Possible way to get back into download mode.
Start with phone unplugged, and when it gets stuck on security error hold power button for 10 seconds to force reboot.
Then at very instant it powers off, but before it powers on hold volume up + volume down + power and plug in USB.
If you are able to get into download flash the teenybin alt. with lgnpst.
adfurgerson said:
Possible way to get back into download mode.
Start with phone unplugged, and when it gets stuck on security error hold power button for 10 seconds to force reboot.
Then at very instant it powers off, but before it powers on hold volume up + volume down + power and plug in USB.
If you are able to get into download flash the teenybin alt. with lgnpst.
Click to expand...
Click to collapse
So that partially got me fixed. I was able to finally get it into download mode after trying your method about 4 times, and I did the teenybin deal. The "regular" teenybin didn't fix it, though it allowed it into download mode the proper way without trying more than once. I then did the alt teenybin, and when it rebooted, it showed a Google logo (instead of LG) with an unlocked icon at the bottom of the screen for about a second before the screen went black. Now I can't get it to turn on at all, though it could just need to be charged. When I plug it in, it shows a white battery icon with a lightning bolt for about 4 seconds before turning back off. I'll let it sit on the charger undisturbed for an hour or so and see what I can do then. As it stands right now, it won't go back into download mode or factory hard reset mode.
Out of curiosity, since I've flashed teenybin, my bootloader should be unlocked and I should have a recovery I can flash zips from now, right? I shouldn't have to jump through any more hoops with LGNPST or anything?
EDIT:
Um, this phone will charge even in this state, right? The LED on the power button isn't lighting up, and I can only sometimes get it to show that battery icon...
YES!!!
I'm into recovery now! I'm going to flash CM10.1 and report back!
EDIT:
I'm up and running now, though WiFi isn't working, nor is my earpiece on the phone. Though, the earpiece was an issue before I borked everything, so I'm pretty sure that's a broken bit of hardware there.
THANK YOU SO MUCH!
chrisliphart said:
I'm into recovery now! I'm going to flash CM10.1 and report back!
EDIT:
I'm up and running now, though WiFi isn't working, nor is my earpiece on the phone. Though, the earpiece was an issue before I borked everything, so I'm pretty sure that's a broken bit of hardware there.
THANK YOU SO MUCH!
Click to expand...
Click to collapse
I am glad you got it fixed! Setting WiFi to 2.4 GHz only may work.
adfurgerson said:
I am glad you got it fixed! Setting WiFi to 2.4 GHz only may work.
Click to expand...
Click to collapse
Wifi works under the stock AT&T JB firmware. Not sure why it didn't work under CM10.1 (it couldn't initialize it), but I'm good now. Thanks!
It may have been a radio issue, ROM zips don't include them. Teenybin would not have changed radio either, so you would still have had ICS radio.
adfurgerson said:
It may have been a radio issue, ROM zips don't include them. Teenybin would not have changed radio either, so you would still have had ICS radio.
Click to expand...
Click to collapse
Ah, that makes total sense. I just got everything setup and signed in on this ROM, so I'm running a Titanium Backup now. I'll switch ROMs and see what happens. Thanks so much for your help.
EDIT:
Yep, that did it. I didn't think to update the radios. I can't thank you enough, man. Aside from the earpiece issue (and I can just use a BT headset to get around it until I decide to pay to get it fixed), it's purring along now.
Sent from my LG-E970 using xda premium
chrisliphart said:
Ah, that makes total sense. I just got everything setup and signed in on this ROM, so I'm running a Titanium Backup now. I'll switch ROMs and see what happens. Thanks so much for your help.
EDIT:
Yep, that did it. I didn't think to update the radios. I can't thank you enough, man. Aside from the earpiece issue (and I can just use a BT headset to get around it until I decide to pay to get it fixed), it's purring along now.
Sent from my LG-E970 using xda premium
Click to expand...
Click to collapse
Nice, glad you got it fixed. And thanks to adfurgerson for the assist.
Sent from my Nexus 7 using xda app-developers app
TangoXray said:
Nice, glad you got it fixed. And thanks to adfurgerson for the assist.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Autoprime explained how to get into download to me on irc, I just relayed the answer. I was glad to help after having a hand in bricking it.
adfurgerson said:
Autoprime explained how to get into download to me on irc, I just relayed the answer. I was glad to help after having a hand in bricking it.
Click to expand...
Click to collapse
Haha, it wasn't you who bricked it; it was me. Really, I should've just done TeenyBin when I first got it into download mode through LGNPST instead of trying to install a stock ROM to root. It really was a backwards way for me to accomplish what I wanted. You'd think that since I've had like 10 Android devices, all rooted and modded, I'd know better. lol
http://forum.xda-developers.com/showpost.php?p=41415103&postcount=248 It all worked out in the end.
chrisliphart said:
Haha, it wasn't you who bricked it; it was me. Really, I should've just done TeenyBin when I first got it into download mode through LGNPST instead of trying to install a stock ROM to root. It really was a backwards way for me to accomplish what I wanted. You'd think that since I've had like 10 Android devices, all rooted and modded, I'd know better. lol
Click to expand...
Click to collapse