So I flashed a JB backup and then the kernel with fastboot, and the screen would shake from side to side nonstop whenever I wasn't touching it. So I pick up my laptop to flash a new kernel (old one must of been corrupted, I assumed) and I drop the damn thing when it's turned on. I'm pretty sure that it messed up the HD files to where fastboot was messed up (it would force close when I tried a command) So I found another application to flash a kernel, but it said I wasn't rooted. So I, desperate, hit the delete kernel button. When I tried booting, sometimes the red light would flash three times,other times nothing.
I have since gotten a new phone (was already due for an upgrade) but as a hobbyist, I'd like to try to fix my old phone to maybe give it to someone else.
Related
I am running the RENOVATE 4.1.2 ROM (ICS) on my One X with CWMR 5.4.0.8. Had a weird problem today. I accidentally dropped my phone while rushing to pick up a call. When I picked it back up again, its screen was frozen at whatever it was displaying whatever was on it before I dropped it. When I tried to navigate, nothing worked and no buttons were responding.
It eventually self rebooted itself and got stuck at the HTC logo. I tried rebooting it via the bootloader three times and it never progressed beyond the HTC logo screen. Thankfully, the recovery was still accessible and I figured that maybe the boot was corrupted and not the ROM itself. I immediately reflashed the boot.img for the ROM and waited for it to reboot.
VOILA! It did. Rebooted normally and came to the home screen. NO changes. No damages. Its all working fine now.
The reason for creating this thread is to know if this is normal? I mean, dropping the phone SHOULD NOT corrupt the boot! I was on a custom ROM and I knew how to flash the boot.img again so I recovered from the issue quite easily but if its was a stock phone, then what? I dont think users will be able to figure it out.
SO, is this supposed to happen?
RipperNash said:
I am running the RENOVATE 4.1.2 ROM (ICS) on my One X with CWMR 5.4.0.8. Had a weird problem today. I accidentally dropped my phone while rushing to pick up a call. When I picked it back up again, its screen was frozen at whatever it was displaying whatever was on it before I dropped it. When I tried to navigate, nothing worked and no buttons were responding.
It eventually self rebooted itself and got stuck at the HTC logo. I tried rebooting it via the bootloader three times and it never progressed beyond the HTC logo screen. Thankfully, the recovery was still accessible and I figured that maybe the boot was corrupted and not the ROM itself. I immediately reflashed the boot.img for the ROM and waited for it to reboot.
VOILA! It did. Rebooted normally and came to the home screen. NO changes. No damages. Its all working fine now.
The reason for creating this thread is to know if this is normal? I mean, dropping the phone SHOULD NOT corrupt the boot! I was on a custom ROM and I knew how to flash the boot.img again so I recovered from the issue quite easily but if its was a stock phone, then what? I dont think users will be able to figure it out.
SO, is this supposed to happen?
Click to expand...
Click to collapse
don't think so mate. maybe the fall has shaken the electronics and did that...weird indeed.
i dropped my wallet on to my phone the other night it froze and turned off, slightly strange if you ask me.
Sent from my Transformer TF101 using xda app-developers app
No it is not supposed to happen. The only reason I can think of is the impact somehow causing an electrical spike due to some internal contacts short circuiting. Probably some files in the system partition got corrupted. But that is a very unlikely scenario.
Alright so I'm guessing i might have a broken flex cable, i don't know because of what is happening.
Don't even know where a good place to buy one.
But; first off, I don't use the phone anymore, it just its on my desk, sometimes I touch it, sometimes I don't.
When I was first getting the blank screen issue, the phone just had been sitting on my desk with the screen on (stay awake), several days later, the screen would be off and refused to come on.
Back then I was using a JB rom. Which I was told JB kernels had problems.
I can boot into fastboot and flash a new kernel and it doesn't change anything.
But now if I load up Flashtool, and boot the phone into flashmode, it will reset itself while flashtool is trying to read from it, then boot itself back into flashmode, then a few seconds later reboot itself again.
Last time I got the phone's display to come on, it was because I was able to use flashmode to flash to it before it rebooted itself.
If I try to boot the device, it will display a white LED for several seconds, then flash a few colors before going back to white and the phone resetting again.
Are these all symptoms of a broken flex cable? It makes no sense to me why fastboot mode is fine, but everything else constantly reboots.
I've tried different kernels and roms to make sure there wasn't a problem in that area.
Ellises said:
Alright so I'm guessing i might have a broken flex cable, i don't know because of what is happening.
Don't even know where a good place to buy one.
But; first off, I don't use the phone anymore, it just its on my desk, sometimes I touch it, sometimes I don't.
When I was first getting the blank screen issue, the phone just had been sitting on my desk with the screen on (stay awake), several days later, the screen would be off and refused to come on.
Back then I was using a JB rom. Which I was told JB kernels had problems.
I can boot into fastboot and flash a new kernel and it doesn't change anything.
But now if I load up Flashtool, and boot the phone into flashmode, it will reset itself while flashtool is trying to read from it, then boot itself back into flashmode, then a few seconds later reboot itself again.
Last time I got the phone's display to come on, it was because I was able to use flashmode to flash to it before it rebooted itself.
If I try to boot the device, it will display a white LED for several seconds, then flash a few colors before going back to white and the phone resetting again.
Are these all symptoms of a broken flex cable? It makes no sense to me why fastboot mode is fine, but everything else constantly reboots.
I've tried different kernels and roms to make sure there wasn't a problem in that area.
Click to expand...
Click to collapse
had that problem too. you have to enter CWM and flash any room that you can
I'm using a Verizon R800x with TurboKernel and (previously) TurboUI.
I wiped TurboUI to install a different ROM which turned out to be GSM, meaning I couldn't get signal, so I went to wipe that, as well. However, afterwards my phone would boot to 'SONY', then get a blank screen, before going black and rebooting again. It didn't respond to anything, until eventually I managed to get it into recovery mode. In TWRP recovery mode I wiped the cache, dalvik cache, etc. to clean up the messed up ROM.
Then, I went into the bootloader. However, this is where the real problem started. I can't stop getting the bootloader. I can't boot into flashmode to install different firmware, I can't boot into fastboot to install a different kernel, and installing a compatible ROM with the kernel just results in the same thing: it just goes into the bootloader.
Every boot, regardless of what I do, what I wipe, what I install, what I hold as I plug in the USB cable or whatever, I get the Turbo Kernel menu. Strangely enough, it consistently gives me the 'first time startup' message everytime it boots into it.
Worst of all is that Cosmic Dan has disabled PMs, closed the threads for all of his projects, deleted the mediafire links, and hasn't posted in over a month. I'm at a total loss; I can't flashmode or fastboot to change anything and I can't install a rom to just get my damn phone working again. I've never felt so clueless and helpless, I've been at this for hours.
EDIT: Just got Slimbean to install by going in via CWM and wiping/installing rather than TWRP; the system, yet again, reset TWRP settings and gave me the 'first time startup' message, but then booted into SlimBean no problem. My phone is working, but I want it back on Gingerbread, so not being able to fastboot/flashmode is still sort of a big problem.
EDIT 2: Tertiary problem, SlimBean has my phone recognized as an R800i rather than an R800x and as a result, most play store apps refuse to download as they're 'not supported on my phone', and the button configurations are messed up, so I can't even use the gamepad for emulators. In the event of never being able to solve this inability to flashmode/fastboot, is there a way to force it to recognize the phone as an R800x, perhaps by editing files in the root directory?
Check your build prop.... Change the model from r800i to r800x. That should help with that.
The phone does not need to be running in order to be put into fastboot/flashmode. Turn it off, hold the Back button (flashmode) or the Search button (fastboot) when plugging it into the USB cable. If you go into fastboot, the notification LED will be blue, for flashmode it will go green.
I actually have this same SlimBean setup (complete with the phone appearing as a r800i on the Play Store), but never had any problem reinstalling any of the apps I had on the phone previously. And this even includes the My Verizon Mobile app (which I have installed so I can find out the amount of data I've used as far as Verizon is concerned, since what they think is what affects the final phone bill in terms of whether I've gone over my limit or not ). Which apps are actually complaining about being incompatible that you had before?
I was messing around with my phone and entered recovery mode (PhilZ Touch) and I kept tapping the empty part of the screen. Then the screen turned off, but on again after a few seconds. Then the phone wouldn't boot past recovery mode. I was stuck!
I researched the problem online and found another forum that posted a flashable "fix". So, I flashed it and then to my horror, realized that the zip was meant for a completely different phone!
Now my phone won't display anything on the screen, won't enter into Bootloader/Download Mode nor Recovery. I can't even do a Cold Reboot!
When I plug the phone into my computer though, Windows makes the USB connected dinging sound and attempts to install drivers but fails. In Device Manager, there is now a QHSUSB_DLOAD entry that appears and disappears depending on whether my phone is plugged in or not.
Does anyone know how to fix this and get the phone up and running again?
Preferably ASAP!? I literally have no phone... not even a landline!
Bro am in tha same boat...am about to send mines off to mobiletechvideos and they'll fix it for 50$ thats the only option ppl been saying...i tried the other way but its a headace and it dosent work for me ...
I ended up solving my problem, but not in the way I wanted. Since my phone was 100% dead, I went back to ATT since it was still under warranty. I told them a story about how the phone had been malfunctioning lately and then just completely died. They replaced the phone under warranty, so now I have a brand new one.
There definitely doesn't seem to be any easy way out of this problem once it strikes. I still don't know what happened to make the phone unable to boot out of recovery, even after wiping stuff, factory reseting, and reflashing roms. All I do know is that I have never had a problem with PhilZ until I started to rapidly tap the blank part of the screen (I like how it vibrates... I'm weird like that). This caused the recovery to never want to exit. Every time I reboot the phone, it automatically went to recovery, even after a full power off or battery pull.
Nevertheless, I am still going to root and mod my phone... just carefully.
You have a hard brick, which is nearly impossible to fix.
Sent from my LG-E980 using Tapatalk
My daughter has this phone and she gave it to me to fix it was doing the same thing as stated in op kept rebooting on its own and would vibrae over an over , playing with the power button it would try to reboot sometimes it would get to the home screen but would rebot again i took the back piece off and cleaned around the power button and i would try to go into recovery but it kept rebooting, i kept trying and messing around with it and i got it to go into recovery and just enough time to clear cache brfote it robboted angian by itself still same thing, kept at it and got it to go into recovery again but i accidentally push update adb and it started to do what it does when you pushed that but i kept pressing power from a panic then i finally rebooted successful now im currently got it working its plugged into my computer it installed successfully but i don't see the storage on my computer, it does not have a sd card in it tho i have one to put in it and it does not have a sim card it it either tho i have the one my daughter gave me that she had to to her phone, i quickly turned on usb debuugging incase i need to odin firmware or something im not sure what do do from here so im asking any one that might know what i should do? If it was the power button i clean it as best as i can and aired it out too, im thinking this might tho do it again since im not sure what fixed it to this point except from what i did to it from what i wrote here. Please if anyone has any ideas out there so i can keep this thing fixed let me know in your replys TY!
mrdreamers said:
My daughter has this phone and she gave it to me to fix it was doing the same thing as stated in op kept rebooting on its own and would vibrae over an over , playing with the power button it would try to reboot sometimes it would get to the home screen but would rebot again i took the back piece off and cleaned around the power button and i would try to go into recovery but it kept rebooting, i kept trying and messing around with it and i got it to go into recovery and just enough time to clear cache brfote it robboted angian by itself still same thing, kept at it and got it to go into recovery again but i accidentally push update adb and it started to do what it does when you pushed that but i kept pressing power from a panic then i finally rebooted successful now im currently got it working its plugged into my computer it installed successfully but i don't see the storage on my computer, it does not have a sd card in it tho i have one to put in it and it does not have a sim card it it either tho i have the one my daughter gave me that she had to to her phone, i quickly turned on usb debuugging incase i need to odin firmware or something im not sure what do do from here so im asking any one that might know what i should do? If it was the power button i clean it as best as i can and aired it out too, im thinking this might tho do it again since im not sure what fixed it to this point except from what i did to it from what i wrote here. Please if anyone has any ideas out there so i can keep this thing fixed let me know in your replys TY!
Click to expand...
Click to collapse
First off, that's one hell of a long sentence!
Had you (or your daughter) recently installed a ROM and forgot to factory reset (clear all caches) the phone after doing so? Many at times, this is what causes boot loops. And you cleared cache, which I think has resolved the problem. However, MAKE A BACKUP on your phone (and onto your computer, just in case the phone hard-bricks) using your Recovery right away! Once you make the backup, there's no need to worry about whether you soft-brick your phone again; you can simply restore that backup. It's also highly possible that it was your power button, but since you said you did clean it up thoroughly, it might just be the cache preventing you from rebooting normally.
Either way, it's good to hear you got your phone working now. I would highly recommend that you make a backup before doing anything else with the phone - just to be on the safe side. Good luck!