frozen on bootloader screen - 8125, K-JAM, P4300, MDA Vario General

ok here's what's going on perhaps someone can figure out what's wrong. Last night I had placed my mda on its charger like usual b4 bed. well sonce my battery cover is slightly broken I had placed a some cardboard within the battery door due to the fact that it would "white screen" then rest and get stuck at the loading screen and drain my battery, anyhoo.... well it whitescreened cause my dresser rocked due to my cat stepping on my phone. so I reset it as usual and the splash screen would load then fade to white. after several attempts it finally started to load as usual but then it went to the boot loaderscreen. I had reset it several more times but no luck. I took out the mobo to see if something was stuck and again nope. luckly I had an older mobo that wouldent charge so I had replaced the mobo but does anyone know why it would randomly get stuck on the boot loader screen? I had even did a hard reset in the device and still no luck. if it was a normal computer I would say that it had lost it's OS any ideas on how to fix it so I can get back my phone the way it should be?
-rastlin

update on bootloader
well I was able to aquire tmobiles flasher utility and I attemted to flash the unit to no luck. I went through all the steps and it gave me an error that it cannot retreive data from the device. ok now I am totally stumped. I am open to any and all suggestions
-rastlin

Related

[Q] Hardware Failure? or Something else

Phone - I400 (Continuum)
So I turned my phone on and it got stuck in a boot up, samsung logo then the verizon would come up and the phone would get stuck there. After i went through the typical remove battery, wait a while turn on again, I still couldnt get it to load. On my last attempt at this instead of any logos, I got a completely white screen with a black bar. I had done no flashing prior to this point. All that will load is the android digging screen. It is detected by odin but nothing will work on it. I have a picture that I will load up when I get back home.
If you have any ideas how to fix this, it would be greatly appreciated.
thebod15 said:
Phone - I400 (Continuum)
So I turned my phone on and it got stuck in a boot up, samsung logo then the verizon would come up and the phone would get stuck there. After i went through the typical remove battery, wait a while turn on again, I still couldnt get it to load. On my last attempt at this instead of any logos, I got a completely white screen with a black bar. I had done no flashing prior to this point. All that will load is the android digging screen. It is detected by odin but nothing will work on it. I have a picture that I will load up when I get back home.
If you have any ideas how to fix this, it would be greatly appreciated.
Click to expand...
Click to collapse
If you have not flashed the phone, I would call Verizon and have them send out a replacement. My very first Continuum did that to me. After I received the replacement, I started flashing it, and haven't had issues with flashing. I have had a total of 4 Continuums. The first one did something like yours. The next two have/had critical memory errors, and this one has a broken camera. I think I am getting lemons... But, when you get refurbished items, one never knows what to expect...

Dead Lumia 520, screen is damaged, help needed.

I have obtained a water damaged Lumia 520. I opened it up and dried it while also clearing any oxidation from the various contact points. The phone displayed the bolt+gear icon on screen but the screen kept flashing and fading. I figured the phone needed the firmware to be reflashed so I downloaded the software recovery tool and it detected the phone and flashed the firmware without error. Then the phone actually worked albeit with a black screen, I could hear the little noises and stuff so it was working under the black screen. I figured that maybe the screen could be salvaged by cleaning the contacts and letting it dry up completely, but after I put the phone together it wouldn't work anymore at all, it basically turns on for a few seconds and turns itself off. The software recovery finds it and I can reflash the firmware but it still doesn't work. I tried checking all the internal connectors but now there doesn't seem to be any way to make it work even with the dead screen.
Is there something I need to touch on screen to make it work? I never had a Windows Phone so I don't really know and I can't see the screen. And do you geniuses know what might be wrong with it and how can I tell if it's just the LCD that has been killed by the water or if the motherboad might be FUBAR as well? What could be causing it to turn off after a few seconds? The battery is definitely not dead as I left it to charge for a long time.
Actually I just managed to "fix" it. The screen comes on after I cleaned the contacts and messed with it a bit, it just looks really bad and it's full of line but I can see what's on screen and use the phone. My issue now is that the bolt+gear icon appears at every reboot and doesn't go away. The only way I have to boot the phone normally is to hold camera and volume down after I reboot it. What does this mean? Other than that the phone seems to be working perfectly once it actually boots.
I just managed to bring it back to life completely. Screen contacts were water damaged but I managed to get them working again and now the screen is perfect. It kept getting stuck on the bolt+gear icon after every reboot because the volume+ button was stuck but I managed to unstuck it and now the phone is perfect. So yeah if you have a flashing screen after water damage check the contacts, if your phone doesn't boot and keeps getting stuck on that icon try to unstuck the volume+ button.

Water Damage - Restarts, Stuck on "Powered by Android" screen

Hello i have a question regarding my recently water damaged galaxy grand prime (rather not discuss how it got wet) but the top portion of my phone got submerged. I immediately removed the battery and vacuumed out water for a few minutes, tested it to see if it would power on (i know, too soon. So stupid) and to my dismay the camera flashed upon the battery touching the connectors inside the phone so im guessing something shorted there. I proceeded to let it sit in rice for the day but i dont have much patience and was missing using my device with cm12.1 flashed and kept checking it every 4-5 hours or so. So at the end of the day i took it out the bag of rice, powered it on, and everything was functioning as it should, besides a little screen flickering which has disappeared entirely now. But here and there and random times im not using my phone, it will restart and get stuck on the "Samsung Galaxy Grand Prime Powered By Android" screen. It wont make it to the boot animation or even go into recovery, but it will boot download mode. So after pulling the battery a dozen times i finally get it to boot again and i go into recovery and try repairing the system with TWRP repair or replace file system option thinking it could probably help. But to this point my phone still restarts by itself and gets stuck on the logo screen here and there and i have to fight it to boot system. Could somebody please help me out here? I hope it isnt a hardware failure and just some software corruption i can fix by factory resetting and re-flashing the rom. Any help is highly appreciated. Oh and i forgot to mention my camera definitely shorted somewhere only the rear works and if i try to switch to front it cant connect. This happens in snapchat and the cameranextmod cyanogen camera. My stock one stopped entirely.
If your phone got submerged, i'm afraid it'll damage the hardware, sorry bro, you'll have to let it go

heat and boot loop

so i have bought a brand new OP 5. did the latest update to O2 os 4.5.5 and considered doing a hard reset as i have spent a good amount of time with windows phone and a reset was just another ritual there after a ota update.
so i set the device to do a clean reset with wiping of all the data. the device rebooted to the red dot and 2 with dots revolving around it and then after a few seconds rebooted again . as it was late night already i decided to leave it resetting and will set it up later in the morning.
for my surprise when i woke a hour or 2 later i saw the phone is still in the same condition with the two dots revolving around in circles. and the device was super hot around the camera lens region. i didn't wanted to disturb the process so i kept the phone upside down to get it to cool down and went back to bed once again.
when i woke up in the morning and tried switching on my phone it showed a warning sign which read " low battery cannot boot" for a sec and died again. so i connected the charger and the phone booted up with the normal setup screen.
so what just happened? i thought of recreating the issue and i was able to reproduce it again when i charged the phone back to 90% i again set it to factory reset and alas again the thing got stuck in a loop where the two white dots kept circling around. this time i held the power button and the phone switched off but when i turned it on it went straight to the setup screen.
i can still recreate this issue and is seriously bothering me as what is the issue, my knowledge tells me this must be a software bug but is anyone else facing it? though a proper reset happens once in a while where the phone itself boots up to the setup screen but most of the times the device will be stuck on the rotating dots screen.
any help / suggestions / explanations will be much appreciated .
I had the same issue when i reset my phone
Oops Reseting leads to bootloop ??
Same thing happened to me as well. Stuck on bootloop

Damaged screen causes reboot, eventually gets stuck in boot loop

Hello, so I have a J7 2017 (SM-J730GM/DS) 32 GB Unlocked Dual SIM which has served me well for a while. I ended up dropping the phone at some point in a sliver of time without a case and the screen cracked. After replacing the screen I noticed if the screen was pressed in a certain area it would go crazy and reboot the phone (crazy as in the pixels would do weird things like dimming, going grainy, like the display shorted in some area, then the phone would reboot itself), probably some error on my installation of the screen and the ribbon cables (I can see an area where it looks creased, it never sat flush with the body of the phone as the OEM screen did). I was able to just be careful and not trigger the reboot for some good time until it happened again and the phone would continuously reboot, allowing me to only get back to the OS through the boot menu, selecting "reboot now". That worked for a while until it would never boot into the OS, just looping at the screen where it says the phone name, where it would vibrate, go black, and go back to the phone name screen. I gave up trying to fix it, as I had a backup phone, and just now had some ideas. I figure the OS is corrupted in some way, I am no master in knowing the details on how phone boots up and such, so I did some research and successfully flashed the most recent ROM onto the phone using Odin 3.14. It still doesn't stop the looping, unfortunately.
Any ideas? I hear people talking about using TWRP or something to do things boot related, but I don't want to possibly mess anything up further nor do I know what they were talking about.
Thanks,
Stella

Categories

Resources