Develop Bugs

Optical Trackball not working in recovery and stuck in the HTC boot logo

I don't know what to do because my device is currently not booting. The device is stuck at the HTC logo for a very long time (both when booting normaly or going in to revovery). The device finaly is finished booting in like 10 min. , but when it is finnished booting the touch on the screen doesn't work, it keeps a black background and it says no service. In revovery on the otherhand the optical trackball doesn't work anymore, the hardware button does tho because the first option "Reboot system now" does work.
What should I Do???

Milioo said:
I don't know what to do because my device is currently not booting. The device is stuck at the HTC logo for a very long time (both when booting normaly or going in to revovery). The device finaly is finished booting in like 10 min. , but when it is finnished booting the touch on the screen doesn't work, it keeps a black background and it says no service. In revovery on the otherhand the optical trackball doesn't work anymore, the hardware button does tho because the first option "Reboot system now" does work.
What should I Do???
Click to expand...
Click to collapse
Have you tried using the volume up / down buttons for moving around the menus and power button for select in recovery?

sbdags said:
Have you tried using the volume up / down buttons for moving around the menus and power button for select in recovery?
Click to expand...
Click to collapse
The volume up/down buttons dont work in recovery

Now its just stuck in a bootloop .
And there is no way of wiping the device, because the trackball isn't working.
hep would be greatly appreciated

The first thing I would try is to remove the SD card and see if your phone boots.
If that doesn't work. Have you tried putting fake flash on your SD and booting into recovery on that to test your trackpad?
Why has it started playing up in the first place? Did you have a bad flash? A wee bit of the history of your device might help to find out what's going on.

socktug said:
The first thing I would try is to remove the SD card and see if your phone boots.
If that doesn't work. Have you tried putting fake flash on your SD and booting into recovery on that to test your trackpad?
Why has it started playing up in the first place? Did you have a bad flash? A wee bit of the history of your device might help to find out what's going on.
Click to expand...
Click to collapse
the trackball isn't working in the fakeflash. The whole problem didn't happen after a bad flash, but it just went in a bootloop when i tried to put it on this morning. I was running Defrost 1.4

You don't need trackball in the fakeflash. You navigate there using volume up and down. It should work. Try .

How about resetting it by doing the following.
Switch it off, or remove battery > Hold volume down and power button > wait a few seconds > use volume to go to clear storage > power button to select. This doesn't involve going into recovery so your buttons might work there.

Can't you get into the bootloader mode with vol. down + power and wipe it there?
Edit: Few secs too late heh

Sareas said:
You don't need trackball in the fakeflash. You navigate there using volume up and down. It should work. Try .
Click to expand...
Click to collapse
You need the trackpad to select the option after choosing it with volume up/down.

socktug said:
How about resetting it by doing the following.
Switch it off, or remove battery > Hold volume down and power button > wait a few seconds > use volume to go to clear storage > power button to select. This doesn't involve going into recovery so your buttons might work there.
Click to expand...
Click to collapse
No, it says clear...... and then it just restarts the bootloop

The fake-flash worked!!!!!!!
I deleted everthing there but now, when I boot up the device it boot up straight into fastboot

You could try now using an ruu to flash. Or try getting into recovery and see if you can use the buttons now.

I'll try a ruu, but the recovery still wont work

socktug said:
You could try now using an ruu to flash. Or try getting into recovery and see if you can use the buttons now.
Click to expand...
Click to collapse
The Ruu doesn't boot past the quietly brilliant signiture.

Now the official RUU is doing a bootloop...

Warning: you triple posted

dario3040 said:
Warning: you triple posted
Click to expand...
Click to collapse
Not the greatest most useful first post I've seen.

Im having the same issue. Phone locked up pulled the battery and phone stuck on HTC boot logo. Can get into recovery but no buttons are working so i cant recover. That actually happened before but i could get it sorted by flashing using rom manager as i could boot the rom.... Where can you get fake flash?

theloother said:
Im having the same issue. Phone locked up pulled the battery and phone stuck on HTC boot logo. Can get into recovery but no buttons are working so i cant recover. That actually happened before but i could get it sorted by flashing using rom manager as i could boot the rom.... Where can you get fake flash?
Click to expand...
Click to collapse
http://www.mediafire.com/?i2cy2p04tjbizn0
version I currently have, maybe not the newest (0.14), but works just fine.

[Q] Alternative methods of accessing Recovery?

My Xperia Play has had a few problems out of the box, mainly that when I switch it on there is no boot animation, just a black screen. This means I can't access Recovery through the normal method of holding down on the volume or the back button etc. I've installed CWM through the CWM Xperia installer so I know it's there. I also ran the Auto-Magic Nandroid through that app, which caused my screen to go black (as it does whenever I choose to reboot through an app). When I looked on my SD card though there is now a Nandroid folder, so it's probable that the device does go into Recovery; I just can't see it.
So my question is this; is there any other way of getting my phone into Recovery so I can install some sweet, delicious custom ROMs? Maybe through ADB or similar? Or is it possible to install a ROM via another method?
Any help at all would be appreciated!!

If it wasn't working right right out of the box, I would have sent it back.
Can't you boot into recovery from the CWM-installer app?

Solar.Plexus said:
If it wasn't working right right out of the box, I would have sent it back.
Can't you boot into recovery from the CWM-installer app?
Click to expand...
Click to collapse
Sadly that wasn't an option, it was the only one they had and I wasn't about to send it back for another type of phone, I've wanted this thing for ages
I've just clicked that option in the app and it's just rebooted the phone normally.

Trism said:
Sadly that wasn't an option, it was the only one they had and I wasn't about to send it back for another type of phone, I've wanted this thing for ages
I've just clicked that option in the app and it's just rebooted the phone normally.
Click to expand...
Click to collapse
Turn on the phone, and when you see the notification light turn blue, press volume down for the locked bootloader cwm, or the back button for the one in DooMKernel.
Sent from a Galaxy far, far away

I've not yet tried installing DooMKernel, I'm worried that if I can't get into the normal recovery in won't be able to get into that one, then I'll be stuck with a boot looping phone.
Pressing down on volume on the blue led comes on doesn't seem to do much, simply stops the boot process from completing fully. I left the phone for 5 mins and got nothing. Pressing the power button again started the boot process again and it loaded up normally (minus any animations of ciurse)
It seems like stuff is happening, but I just can't see it. I doubt this is a hardware fault as the screen works perfectly all other times, so what the heck could it be!?

The recovery in DooMKernel is already built in, so it's different than using the Xperia CWM installer. By the way, the back button will get you into DooMKernel's recovery.

I'll give it a try and see what happens. Thanks for the advice guys!

Unusual/Possible Brick?

Ok.. So, the phone is rooted with stock rom. It decided to just shut off today and continuously vibrate while off, even while the battery is out and the phone is plugged into the usb cable it vibrates.. So, when I put the battery back in it starts to boot with the Sammy logo then the TMO part comes up where its trying to load and the progress bar gets to like 30% then it shuts off again and vibrates. So I figured Id just try to get into download mode and re-flash the stock rom but no go.. I plug the phone into the usb and hold the volumes and then insert the battery and the download screen comes up but it doesnt stay, the phone goes blank and keeps vibrating again?? I also want to add that the phone wont completely turn off, even after taking the battery out.. When I put the battery back in, it boots right up everytime without me even pressing anything so I cant even get into recovery if I wanted.
So bottom line is.. Phone is rooted with stock rom.. Phone stays blank and vibrates, even when battery is out and plugged into the usb cable.. When inserting the battery and holding volumes, the warning screen comes up but only for a second then the phone shuts down and continuously vibrates?? So it wont stay on the warning screen so I can flash another rom or I cant get into recovery cause it keeps trying to boot as soon as I put the battery in and then shuts down and vibrates when it gets to the TMO screen??
I did do some searching on this particular problem and found nothing. Any help is appreciated. Thanks.

maybe power button is stuck? u cant get into dl or recovery at all?

minlo said:
maybe power button is stuck? u cant get into dl or recovery at all?
Click to expand...
Click to collapse
I can get into download mode but as soon as it gets to it, the phone just shuts off and keeps vibrating.. Recovery is a no go.

After messing around with it a little I got it to go into download mode by unplugging the usb right when the warning screen pops up, for some reason it stayed on and i was able to plug back in and flash the stock rom but once I did I got nothing but errors/force closes on my apps as soon as it booted. Now I cant get it to stay on long enough again to flash the rom again, its doing the same thing.

R u wiping properly? data, cache, system, dalvik, permissions? what recovery r u on? if u can get back in dl mode u should reflash ur recovery n see if somehow ur recovery became corrupt

minlo said:
R u wiping properly? data, cache, system, dalvik, permissions? what recovery r u on? if u can get back in dl mode u should reflash ur recovery n see if somehow ur recovery became corrupt
Click to expand...
Click to collapse
I was able to get back into download mode and I flashed the stock gingerbread rom but the phone doesnt stay on for more then 5min.. it either reboots or shuts down and vibrates till I take out battery and reboot again or boot into the stock recovery and empty cache... its stock now and not rooted so I only have the stock recovery that just list the data or cache clearing.
After a few hours of messing with it, it still does the same thing, no change, I have no idea how to fix it or what the problem is..

ykman1 said:
I was able to get back into download mode and I flashed the stock gingerbread rom but the phone doesnt stay on for more then 5min.. it either reboots or shuts down and vibrates till I take out battery and reboot again or boot into the stock recovery and empty cache... its stock now and not rooted so I only have the stock recovery that just list the data or cache clearing.
After a few hours of messing with it, it still does the same thing, no change, I have no idea how to fix it or what the problem is..
Click to expand...
Click to collapse
I'll give it a shot....You have to keep trying to get into CWM long enough to wipe cache partition, wipe dalvik cache and fix permissions.
That should help clear any anomalies.
***Something I learned by trial and error. When you say your flashing to stock try to flash android 2.3.6 stock. That should clear most problems over ICS***

minlo said:
maybe power button is stuck? u cant get into dl or recovery at all?
Click to expand...
Click to collapse
Im starting to think its a power button issue but how do I fix it? Do I have to take the phone apart and clean it out or something?

If you think its the power button issue check out this thread http://forum.xda-developers.com/showthread.php?t=1931310 posted by evilmika.
I think it’s a bad flash of course I can be wrong.

Bandaid_nyc said:
I'll give it a shot....You have to keep trying to get into CWM long enough to wipe cache partition, wipe dalvik cache and fix permissions.
That should help clear any anomalies.
***Something I learned by trial and error. When you say your flashing to stock try to flash android 2.3.6 stock. That should clear most problems over ICS***
Click to expand...
Click to collapse
I was able to install 2.3.6 and it gave me no errors/force closes on boot but its still doing the original problem.. Also, its stock rom so there is no CWM, just the stock recovery where you can clear cache only. Should I try and get it to stay on long enough to root so I can install CWM and try to clear everything else or does it not matter at this point?
The weirdest thing to me about all this is why would it still vibrate when the usb is in but the battery is out? I mean.. dont you have to have the battery in for the phone to get proper connection to even have any juice flowing through it? Idk.. just dont make sense to me lol

I understand your not rooted yet which is fine. Can you try to clear cache?
If that doesn’t work, I would like to power off, remove the battery, remove the sim card for 30 seconds. Once you have everything placed back together reboot and hopefully we can celebrate. lol

Bandaid_nyc said:
I understand your not rooted yet which is fine. Can you try to clear cache?
If that doesn’t work, I would like to power off, remove the battery, remove the sim card for 30 seconds. Once you have everything placed back together reboot and hopefully we can celebrate. lol
Click to expand...
Click to collapse
lol I wish.. I did that a bunch of times and no go, I also tried taking it a part and messing with the power button cause one thing I do notice is when I do get it to boot the power button is flaky, like when I do press it it will act as if im holding it in and bring up the power off menu, then sometimes it will just do nothing, so Im thinking it is a power button issue.. I followed the guide and I do get a click when I push it internally but I think its just shot and I need to get that replaced.

well darn lol I wonder if a pc repair shop can fix the power button versus sending the phone to samsung for repairs. I only mention pc repair shop as it is a very small fix and good possibility they can repair a silly button contact.

Bandaid_nyc said:
well darn lol I wonder if a pc repair shop can fix the power button versus sending the phone to samsung for repairs. I only mention pc repair shop as it is a very small fix and good possibility they can repair a silly button contact.
Click to expand...
Click to collapse
Yea that is worth a shot.. I did a bunch of google-in this mourning and seen that the symptoms im having are caused by either a bad flash or battery issue and im pretty certain that its not a bad flash since i flashed it back to stock several times and its still having the same problems... Regardless i appreciate your help. Thank You.

your very welcome. I hope you get this fixed quickly and come to flash haven.

is there any app the op could use to disable the power button and/or use another button to boot?
i know noLED will while the phone is running but can u remap thru recov on the fly?

[Q] htc incredible loop at boot up

hey xda
my droid incredible won't start up.. it keeps looping on the boot up ... what can I do to solve this problem ?

try a factory reset.
hold down -volume and hit power button. a menu should pop up and factory reset should be one of the choices

Same problem
tekweezle said:
try a factory reset.
hold down -volume and hit power button. a menu should pop up and factory reset should be one of the choices
Click to expand...
Click to collapse
My incredible started doing this yesterday, Ive tried this option it doesn't work for me. I can get the menu but it when I choose factory reset or any of the other options it flashes the htc incredible screen and starts the loop again, any more suggestions would be appreciated.

Is your phone unlocked and rooted/s-off?
It will say so on that menu screen.
Sent from my SCH-I500 using Tapatalk 2

Htc loop
wanted167 said:
hey xda
my droid incredible won't start up.. it keeps looping on the boot up ... what can I do to solve this problem ?
Click to expand...
Click to collapse
tekweezle said:
Is your phone unlocked and rooted/s-off?
It will say so on that menu screen.
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
No I was getting ready to root it the day this started. Will rooting help this problem?

having CWM recovery on the device would help you clear the memory and load the OS easily. but that requires your device to be rooted.
whats strange about this case is that my understanding is that the OS is read only and the only thing that changes is data and user data held in a separate partition. so the 2 possibilities is that your user data is corrupted(probably due the space getting exhausted-were you getting a low space warning?) or less likely but possible-the OS corrupted in some way-perhaps from repeated reboots and phone use.
i guess if a factory reset isn't helping there is little i can suggest. that should do the trick if the OS isn;t corrupt because all it does is wipe away the user data so you can resetup the device as if you bought it brand new.
if you have an micro sd card in the device, try removing it. if that doesn;t work, try reformatting it and putting it back in.

Htc loop
tekweezle said:
having CWM recovery on the device would help you clear the memory and load the OS easily. but that requires your device to be rooted.
whats strange about this case is that my understanding is that the OS is read only and the only thing that changes is data and user data held in a separate partition. so the 2 possibilities is that your user data is corrupted(probably due the space getting exhausted-were you getting a low space warning?) or less likely but possible-the OS corrupted in some way-perhaps from repeated reboots and phone use.
i guess if a factory reset isn't helping there is little i can suggest. that should do the trick if the OS isn;t corrupt because all it does is wipe away the user data so you can resetup the device as if you bought it brand new.
if you have an micro sd card in the device, try removing it. if that doesn;t work, try reformatting it and putting it back in.
Click to expand...
Click to collapse
I tried all that and nothing seems to work can I root it like this? Ive tried taking the sd out and putting it back in reformatting it still it just loops and I get the boot menu but it wont do anything in the boot menu only the power down option everything else when highlight it and hit the power button to select it just goes right back to the loop Im ready to throw it out the window lol

SuzyQangel said:
I tried all that and nothing seems to work can I root it like this? Ive tried taking the sd out and putting it back in reformatting it still it just loops and I get the boot menu but it wont do anything in the boot menu only the power down option everything else when highlight it and hit the power button to select it just goes right back to the loop Im ready to throw it out the window lol
Click to expand...
Click to collapse
This sounds quite a bit like an Inc I have lying on my shelf. It was a friend's and he gave it to me to see if I could fix it. As far as I can tell, the phone's emmc storage simply failed. These phones are aging and that happens sometimes. Anyway, I tried all the usual stuff, including running RUU's (flashing signed PB31IMG.zip's since the thing had never been rooted and was still s-on), and yeah, just boot looped.
I did get the phone working, but it was complicated and messy. Here's more or less what I did: I was able to successfully run the RUU that updates HBOOT to 1.02 (or 1.07, either one works), which allowed me to unlock the bootloader via HTCdev. (see one of the root / s-off guides if this doesn't make sense.) This made it possible to flash ClockworkMod recovery using fastboot, and boot into recovery. From there, I was able to get to a root shell through adb (plugged into my computer) and proceeded to downgrade and get s-off, following the guide. It now works, though it's running Froyo and there is hardly any space for apps due to the messed up storage. I've been wanting to try this hack on it but I haven't gotten around to it yet.

stuck in boot loop, keys dead
I have an HTC incredible. One day the power button decided to quit working. Everything else worked fine, except when the phone went to sleep, the only way to wake it up was to plug in the charger. That was all fine and dandy til I was using it one night to listen to TuneIn and forgot to shut it off. When I plugged in the charger the next morning, it went into boot loop. I can get it out of boot loop by holding the power and/or volume down buttons, but when the hboot (?) screen comes up, I am helpless to do anything, as the power and volume buttons are unresponsive. It is not recognized when I plug it into my laptop, either. For whatever it's worth, it does say "S-on" on the hboot screen, if that helps. Is it junk or fixable?

spappy said:
I have an HTC incredible. One day the power button decided to quit working. Everything else worked fine, except when the phone went to sleep, the only way to wake it up was to plug in the charger. That was all fine and dandy til I was using it one night to listen to TuneIn and forgot to shut it off. When I plugged in the charger the next morning, it went into boot loop. I can get it out of boot loop by holding the power and/or volume down buttons, but when the hboot (?) screen comes up, I am helpless to do anything, as the power and volume buttons are unresponsive. It is not recognized when I plug it into my laptop, either. For whatever it's worth, it does say "S-on" on the hboot screen, if that helps. Is it junk or fixable?
Click to expand...
Click to collapse
Sounds hosed to me. You could try to flash an RUU zip but that'd require use of the keys in HBOOT. If there is an RUU option that does not involve touching the phone, it's possible. Otherwise, no. I guess you could open the phone and check the button connections are there but it may be locking up at the HBOOT screen. Give it a chance to charge up a bit. However, I believe this phone is a lost cause. I seem to be seeing more frequent bootloop phone reports lately.

[Q] Tried downloading cyanogenmod and messed up

So I rooted my LG Optimus G and wanted to download a new rom to try it out and heard that Cyanogenmod was pretty good. So I downloaded it and extracted it and tried to boot it from recovery on my phone. The problem though is that when it goes to boot up it just shows the cyanogenmod logo and the blue circle spinning. From what I understand it's most likely because I didn't restore to factory settings before hand. So I was wondering whether there's anything that I can do to try and fix it or whether I just got a new paperweight?

justsomedude23 said:
So I rooted my LG Optimus G and wanted to download a new rom to try it out and heard that Cyanogenmod was pretty good. So I downloaded it and extracted it and tried to boot it from recovery on my phone. The problem though is that when it goes to boot up it just shows the cyanogenmod logo and the blue circle spinning. From what I understand it's most likely because I didn't restore to factory settings before hand. So I was wondering whether there's anything that I can do to try and fix it or whether I just got a new paperweight?
Click to expand...
Click to collapse
Did you wipe data, system, dalvik and cache? Actually what recovery are you using? If it's TWRP, go to wipe and then advanced and wipe everything EXCEPT internal storage(data, system, dalvik, cache) then reinstall the rom and gapps. CWM(clockworkmod) is different and I haven't used it in awhile, but usually bootloops are because you didnt wipe atleast dalvik and cache(the factory reset in TWRP), but I usually wipe everything. Just not internal because that is where your files(and rom) reside.
If that doesnt work, you can try a different rom and use adb sideload from a pc. There are plenty of tutorials for that here on xda if you do a search.
But if its loading to the CM logo, it is not a paperweight. Worst case scenario you can use LGNPST and a stock bin file to go completely back to stock. But as long as you can get into recovery you shouldn't have to go to those lengths.
Hope this helps.
EDIT: I know it's your phone and if you are like me, it's probably your only phone. But don't panic, real bricks are rare and if you can get back into recovery you are usually fine!

HPTesla said:
Did you wipe data, system, dalvik and cache? Actually what recovery are you using? If it's TWRP, go to wipe and then advanced and wipe everything EXCEPT internal storage(data, system, dalvik, cache) then reinstall the rom and gapps. CWM is different and I haven't used it in awhile, but usually bootloops are because you didnt wipe atleast dalvik and cache, but I usually wipe everything. Just not internal because that is where your files(and rom) reside.
If that doesnt work, you can try a different rom and use adb sideload from a pc. There are plenty of tutorials for that here on xda if you do a search. Hope this helps.
Click to expand...
Click to collapse
No I did not, at the time apparently I wasn't thinking. I was using clockworkmod, but whenever I try and use adb on my pc it doesn't detect my phone anymore either. Rebooting it manually also doesn't work either since it just goes back to the loop cycle, I'll definitely look into sideloading though.

justsomedude23 said:
No I did not, at the time apparently I wasn't thinking. I was using clockworkmod, but whenever I try and use adb on my pc it doesn't detect my phone anymore either. Rebooting it manually also doesn't work either since it just goes back to the loop cycle, I'll definitely look into sideloading though.
Click to expand...
Click to collapse
Power your phone off completely, then hold the volume up button while you power it on. Once it loads, hit volume down twice then the power button to get back into recovery. Wipe dalvik and cache and reinstall cm and gapps. You should be ok after that.
I also added some edits to my first post. Again I use TWRP which has an adb sideload option under advanced settings......not sure about CWM. But this guide here is a great resource for our phone and has a lot of helpful links.

HPTesla said:
Power your phone off completely, then hold the volume up button while you power it on. Once it loads, hit volume down twice then the power button to get back into recovery. Wipe dalvik and cache and reinstall cm and gapps. You should be ok after that.
I also added some edits to my first post. Again I use TWRP which has an adb sideload option under advanced settings......not sure about CWM. But this guide here is a great resource for our phone and has a lot of helpful links.
Click to expand...
Click to collapse
Whenever I try and turn the power off, it automatically reboots itself back into the loop. That also happens whenever I try and put it into recovery mode so I can't delete anything. Would going through the annoying process of removing my battery potentially help with that?
I also don't know whether LNGPST would be able to help because if the normal manual commands such as the power down function don't work, then I probably won't be able to enter into download mode to use LGNPST.
On a side note, I really appreciate your help, but even if all else fails, I do have another phone I could use but it's old so I'd rather avoid that.

justsomedude23 said:
Whenever I try and turn the power off, it automatically reboots itself back into the loop. That also happens whenever I try and put it into recovery mode so I can't delete anything. Would going through the annoying process of removing my battery potentially help with that?
I also don't know whether LNGPST would be able to help because if the normal manual commands such as the power down function don't work, then I probably won't be able to enter into download mode to use LGNPST.
On a side note, I really appreciate your help, but even if all else fails, I do have another phone I could use but it's old so I'd rather avoid that.
Click to expand...
Click to collapse
How long have you held the power button in? For me sometimes its 20 seconds but Ive heard as long as a full minute. If you hold the power button down until the screen turns off, and it comes right back on try holding it for a minute straight and let it go. If not, you may have to do the battery pull which is a pain in the a**. But Ive had that power down, turn right back on and into the bootloop myself, holding the power button for a solid 20 count solved it - but again it may be longer. And you're welcome, Im here to help - one thing you will learn about fellow lgog users if you get that phone working again - lots of support!
EDIT: Also, if you do get it to power down and then are able to get into recovery - plug it into the wall. Wait until you get into recovery to do it - but if its been on this whole time your battery might be low and you dont want lithium batteries to drain completely. It shortens their lifespans.

HPTesla said:
How long have you held the power button in? For me sometimes its 20 seconds but Ive heard as long as a full minute. If you hold the power button down until the screen turns off, and it comes right back on try holding it for a minute straight and let it go. If not, you may have to do the battery pull which is a pain in the a**. But Ive had that power down, turn right back on and into the bootloop myself, holding the power button for a solid 20 count solved it - but again it may be longer. And you're welcome, Im here to help - one thing you will learn about fellow lgog users if you get that phone working again - lots of support!
EDIT: Also, if you do get it to power down and then are able to get into recovery - plug it into the wall. Wait until you get into recovery to do it - but if its been on this whole time your battery might be low and you dont want lithium batteries to drain completely. It shortens their lifespans.
Click to expand...
Click to collapse
Holding it for 20 seconds worked and from there I was able to put it into recovery. Thank you for all the help, if not for you I probably would've tried to remove the back and probably just break it even worse

justsomedude23 said:
Holding it for 20 seconds worked and from there I was able to put it into recovery. Thank you for all the help, if not for you I probably would've tried to remove the back and probably just break it even worse
Click to expand...
Click to collapse
Good stuff man, glad to hear it and you're welcome!