Droid ProPlus bricked itself - Droid Pro General

After a year of playing with Galaxy S3 I got bored with constant flashing and well, I never got used to onscreen keyboard.
I wanted a phone that will just work and decided to go for a Droid Pro+. Device was form Germany as there is no official distribution in Poland. It worked like a charm for two weeks till just now.
While playing with it (changing ringtones and stuff) I got several messages about services failing - com.service.usb, com.service.google, etc.) As it happened before (but only com.service.usb) I restarted it - in a normal way - power button and then Reboot. It rebooted and after that got stuck on M logo.
The firmware was as stock as it could be. No modifications were made. What's strange, the device can't be hard resetted. I can hold the power button for several minutes and it won't turn off.
Recovery mode works, but wiping does not help. Fastboot also works, but RSD Lite shows N/A in every column of Device info. I flashed GB 2.3.6 (5.5.1Q-110_ELW-TA-36-65-release-keys-signed.Retail-en-GB.tar) found on XDA. The rom itself should be OK, as no functionality was lost (recovery and fastboot), but the device still hangs on the boot logo. Device info is still N/A.
Could it be a hardware malfunction or is there something else I could try? Warranty is probably not an option since as i mentioned there is no official distribution in Poland. Any help would be appreciated since I'm out of ideas by now... Also, does anyone know if the battery is charged when in Recovery or fastboot mode? Connecting to a charger ends up on the M logo. And because very few people in Poland have Moto devices I have no other way to recharge the battery.

Related

[Q] Need help - HK MX 030 won't boot

Hello everyone!
My brother sent me is MX 030. It is the original Meizu MX HK version with the unlocked bootloader. Two weeks ago, he found his phone had crashed. The screen was black and he powering it off and then back on would not do anything (black screen - only vibrates on power on).
I got it today and first thing I did (after charging it-the charging mode works and displays a battery logo) was boot into recovery mode (or update mode on Meizu phones) and I was able to reach the menu. It let me mount the drive onto my PC. I downloaded the latest firmware and put it on the drive. I pressed upgrade and cleared data. The software seemed to install fine, but then the phone rebooted to a black screen - again.
Then I tried installing older versions which I found on the meizu website. They all install and I can see the recovery mode is different, but they all boot into black unresponsive mode (which drains the battery).
Having had other android devices before, I feel the phone is stuck in reboot loop.. I don't know what else to try or attempt. I feel am running out of options. The fact that the phone still responds to some commands and allows me to flash firmware should indicate that the phone isn't brain dead quite yet, right? Anyone else experienced a similar situation?
Thank you,
Oli

[Q] Nexus 7(2012) stuck in fast boot mode, bricked?

Have a standard Nexus 7(2012), 18m old. OTA upped to Android 4.4.4. a month+ ago. Never rooted. From then on it has lasted a week or less before freezes/reboots while using apps or even nothing at all.
Have undertaken boots to fastboot mode (android on its back, door open but no red triangle) and then entered recovery mode to wipe system cache and then do a factory reset. This sometimes progresses thru startup restoring apps ok. Sometimes it crashes part way thru. Often get background Chrome and Maps crashes of late as it redownloads my old apps.
Google HW support line recommended this course of action until last time when desperate Indian woman out of her depth tried to say it was a hardware fault and palmed me off on Ausus(uk) saying they did a 2yr warranty... which I think they don't. Still to investigate that one.
The reboots kicked off again today. So did the usual: did a cache clear then factory reset and it restarted. Now it crashed while the Android coloured balls still rotating! And forcing into fast mode to do a 2nd factory reset failed as when I select Recovery Mode it now says "Booting failed" in small letters at the top and dumps u back in Recovery mode, though less the Android logo on its back. Cannot restart bootloader either, same error. Rebooting just freezes with "Google" displayed.
Have I "bricked it" somehow. How to I get past this?
As a novice, I have got Nexus Root Toolkit v1.8.5and tried to reflash to stock 4.4.4 rom on it. But bootloader is locked, as it is delivered, and it will not unlock it. (read from The Definitive Guide on How to Restore Your Nexus 7 Tablet (Even if You've Bricked It from nexus7 wonderhowto site)
Anyone got any info on what to do here? Better reflash tool/instructions? Is it hardware problem? Do Asus uk do a 2yr warranty that I need after 18months? Is this tablet permanently a dead parrot?
Any help, I am desperate here. Thanks

Sm-g900f (uk) galaxy s5 - arrgghhhhh

Can anyone PLEASE help??
My partner opted to do a suggested update on her S5, but didn't notice the wifi was off. The phone seemed to have done the update, but shortly after it rebooted itself, then again, then again. The frequency of reboot got quicker and quicker and now it loops between the Galaxy S5 splash screen and the SAMSUNG logo, but doesn't go any further.
I managed to boot the phone into reset mode, cleared the cache and then did a factory reset, but that did nothing to prevent the boot loop.
I then downloaded Odin (ver 10.3.7) and what I believed to be the correct firmware (G900FXXS1CPLV_G900FVFR1CPJ1_G900FXXU1CPIW_HOME.tar.md5).
Having checked the battery was charged, I followed the instructions of connecting the phone via USB, loading the md5 in the AP, checking Auto Reboot and F-Set time in the options and clicking the Odin Start button. I had removed the battery, replaced it and then booted it into the update mode (Power, Home, Volume Down, then volume up) with the screen confirming I was in the right place (....do not unplug.... etc).
The file loaded, (green bar at top of the Odin window on my PC) and Odin reported success. I then disconnected the phone, booted in recovery mode, reset the cache and then did a clear data, factory reset.
The same symptoms prevail, STUCK IN BOOT LOOP!!!!
The only thing different is that if I plug it into the USB on my PC, after a while the phone tries to turn itself on and goes into either a boot loop or freezes on the Galaxy S5 Splash screen or the SAMSUNG Logo.
I am charging another battery (just in case that is in some way to blame) and will try again to replace the firmware, but could I be missing something, do I need to do anything with PIT (I thought this was all taken care of by Odin using the MD5 file) or is there some other test I can perform that will show if the phone is fried???
MANY THANKS for looking!
ur going correct, try to reflash it again through odin and dont disconnect phone until it boots into system, it is taking some good time, so just wait and dont do anything this time like clearing anything or restoring. i hope ull get success.
THANKS - but...
Thanks Rayzen, I will try the whole thing again, but I think there is something more to this than a firmware fault!
There and gone again
OK, so on the 4th attempt I got the phone to take the firmware using Odin, it reported success and the phone rebooted itself (several times) and eventually appeared to boot to a new factory reset.
I put in a SIM card and entered my email and google account details and left it charging over night. This morning when I tried to use it, the screen froze and then it rebooted itself. Hey presto, the phone is back to square one with a boot loop.
ANYONE (please) got any suggestions?
THANKS
No one??
same here, same symptoms, same feeling.
when flash gone right... i feel lucky.. but for half hour only, rebooted and angain in boot loop.
I cannot even boot in recovery. flashed TWRP. from 5 boots in recovery only 1 success.
When trying to wipe phone in TWRP - it hangs.
still trying to install some other (custom) rom. still no success.
hope never dies
same things happened here! now cant get samsung galaxy s5 to boot...............
Are you sure your using right firmware? as it took me a few versions before it booted last time this happened?
Could any please confirm what is the right firmware for samsung galaxy s5 900F
It took another 6 or 7 attempts, left it over night and was about to trash it when it booted.
I then received a 'software update available' message and tried installing it. First attempt put the phone back into boot loop so I reflashed it again using Odin.
That worked immediately the over the network software update installed and now phone is 100%
Very frustrating but I got there!
glad you fixed it! ive tried three different firmwares and still nothing.
trying this one atm
G900FXXU1ANE2_G900FEVR1AND1_G900FXXU1ANE2_HOME.tar
oh and how long do they take to boot when there are sitting at the samsung glowing screen?>
I'm in UK and used what (I had to guess) was the best firmware.
I'll let you know which version it was when I get home tonight.
BUT I had all the problems with a single version and it eventually came good.
I read somewhere that overwriting a different core (from specific providers) with generic firmware, could lead to a world of pain until it gets full replaced... not sure if that's a good description (or has any fact to it) but it seemed to be re-loading and re-loading and re........ for ages, finally cracked it.
well mines booted now!but getting constant errors about samsung push!
If it'still booted, you'very made progress!
Push issues are mentioned elsewhere and can (eventually be sorted) but if you have a booted phone you should be able to get an over the air software update installed from the service provider....?!

s7 edge reboots in logo need help please

Hello guys i have a strange problem. i am using my s7edge for over a year (finally was in batman rom).
After updating to marshmallow i encountered this problem where sometimes rarely my phone reboots (reboot- - show samy logo - then reboot). sometimes after few reboots it will comeback and some other time. i need to wait till it discharges fully and charge it it comes back. (but its so random though. totally happened 3 - 4 times last year)
from last week it happened quite often once a day and from yesterday it keeps rebooting in logo no matter what i do. when this happens only download mode is accessible and twrp recovery is not accessable at all. so i waited till it discharges fully but that does not help.since download mode is accessible i used Odin and flashed stock firmware, still the same result(tried several times). its just keeps rebooting in logo even after flashing with stock firmware via Odin and i have no more options to go for. is my device hard bricked? any more options i can try??? my final hope is someone here will help me.:crying::crying:
Thank you
Oh! I just posted a similar question. After several tries, I sorted out a way to make it boot:
1) With the latest samsung drivers on my notebook, I've downloaded the latest Odin (Odin3_v3.12.3) with this stock rom from sammobile (G935FXXU1DQJ4_G935FUUB1DQJ4_ARO). According to this page this rom works in Argentina and the ARO means it is used on unlocked devices. Then it has no bloatware or any company logo.
2)Charged it for a few minutes until it reached 2~3%. Vol Down + Home + Power (in that order) and entered 'Download mode'. Then plugged it into the pc.
3) Opened AP, BL, CSC and CP files, then flashed it. Once it restarts, try to get it into recovery mode with volup+home+power and charge it. I used a power bank. Then wipe cache and factory reset. Then reboot to system and let it loop until it gets into the OS.
The one I've got in quarantine is working smooth.

Won't power up or boot into download/recovery after interrupted update

Please help! My S5 Neo was in a drawer for a few months after the LCD got smashed. I recently bought a new LCD assembly and connected it to make sure it worked before fitting and it was fine. However, the phone immediately started doing a software update but was interrupted after a few seconds as the battery was dead. Now the phone won't power up or boot into download mode or recovery. When I plug the phone in to its charger, the LED flashes red but nothing is displayed on the screen. I had a new battery for it and charged it in another device but still no joy. I've been messing around with old galaxy phones for a couple of years now, flashing custom ROM's etc, so I wanted to just re-flash a stock ROM into it but there's no way I know of performing this without getting the device into recovery or download mode. Does anyone have any ideas? The device is totally stock and hadn't even been rooted. I'm currently using an S4 Active running Lineage OS 17.1 so I'm not desperate for a phone, but I loved my S5 and really would like to get it up and running again. It never once had any problems.

Categories

Resources