Database Develop

[Q] Not sure if hard bricked

Hey everyone - I've got an interesting one I think.
I had just gotten everything working with CM11 when I got ambitious and went to replace the logo.bin to remove the 'unlocked bootloader' warning that shows up every boot. I realized too late that the logo.bin I used was for a Moto G. Now you'd think that this would just affect the boot logo and I'd be able to try again with the right logo.bin... nope.
On boot all I see is colorful snow. I hear the startup sounds, and I can access the files on my computer when connected via USB. After the screen goes to sleep it shows a flashing white light. Same response with each different startup button combo.
Any ideas? I've tried using adb and fastboot manually, as well as Myth Tools. 'fastboot devices' shows up blank, and adb finds no devices either. I've installed RSDLite but can't find a file to use (lots of broken download links), and I'm not sure that would even solve my problem.
Thanks for any help!

The phone woke me up with it's alarm this morning. That was unexpected. It's also ringing when I call it - CM is running, just the screen is messed up.
How can I get into fastboot in this state? I've never had much success getting the key combos to work on this phone. Adb reboot commands were my most reliable way, but adb isn't detecting a device. If I installed CM11 and have not installed google apps yet, should adb be working?

dta5003 said:
The phone woke me up with it's alarm this morning. That was unexpected. It's also ringing when I call it - CM is running, just the screen is messed up.
How can I get into fastboot in this state? I've never had much success getting the key combos to work on this phone. Adb reboot commands were my most reliable way, but adb isn't detecting a device. If I installed CM11 and have not installed google apps yet, should adb be working?
Click to expand...
Click to collapse
Nope. Not until adb is enabled by going into the developer options or tweaking the build.prop before install.
Just hold down all three buttons when you are booting up and you'll access the boot menu, from there you can select recovery or fastboot or whatever (for me it's easier than using the other key combos as I too have a hard time with them).

skeevydude said:
Just hold down all three buttons when you are booting up and you'll access the boot menu
Click to expand...
Click to collapse
Maybe it's the way you described it, but I was actually able to get into the boot menu this time! I've fixed the logo, and the phone boots normally now.
For anyone else with similar issues, getting the boot menu requires doing a simulated battery pull (vol down + power) followed by booting with all 3 buttons pressed. I think my error was attempting to hold all 3 buttons when the phone was still on and expecting to get the boot menu.
Hooray, my wife has a phone again! And I won't have to worry about touching it ever again because I won't be allowed to. :victory:
Thanks!

Hi, I am having some problem with my Atrix HD. I was doing some rom update and after reboot all I can see is colored snow (not sure whats the technical name for this, as it will help to search better) and goes to nowhere from there. I tried rebooting few times, but nothing except the snow. Its summer now, so How can get rid of this snow and see my normal phone ?

manugoenka said:
Hi, I am having some problem with my Atrix HD. I was doing some rom update and after reboot all I can see is colored snow (not sure whats the technical name for this, as it will help to search better) and goes to nowhere from there. I tried rebooting few times, but nothing except the snow. Its summer now, so How can get rid of this snow and see my normal phone ?
Click to expand...
Click to collapse
What exactly were you doing? Taking the new AT&T OTA or was it something on the custom side?
I know that flashing the wrong sized bootlogo can do this. I actually flashed a bad one I made the other day that turns my screen red and the actual image is all jacked up. The Moto G logo I flashed left it snowing just like you're experiencing. I've also had random bad flashes do this too.
All you can do is fastboot/myth/rsd back to stock and start over. Hopefully you have backups.

Thank you, I managed to fix my phone, it was something related to battery. I simple pressed all three buttons and connected to charger to get to fastboot menu, which also rebooted few times as phone did not had enough battery to run fastboot. Repeated the process few time to get it working. Thanks

[Q] LG Optimus L90[LG DG415] stuck on logo

So I was just screwing around with my fonts folder(under system) and I replaced my custom font file for Roboto-Normal.ttf with the original Roboto font and when I rebooted my phone it got stuck on the LG logo and wouldn't advance after that. I also noticed while it was stuck on the LG logo if I hit any buttons in any combinations the phone would vibrate randomly. My phone is rooted with debugging on.

MrKidQuisine said:
So I was just screwing around with my fonts folder(under system) and I replaced my custom font file for Roboto-Normal.ttf with the original Roboto font and when I rebooted my phone it got stuck on the LG logo and wouldn't advance after that. I also noticed while it was stuck on the LG logo if I hit any buttons in any combinations the phone would vibrate randomly. My phone is rooted with debugging on.
Click to expand...
Click to collapse
Maybe the font was not compatible for your phone,If it was compatible for you it should apply and you should see it immeadiately,Rebooting is not required.
Try to connect the computer and Use the LG R&D Tool to flash the ROM.

androidvillage said:
Maybe the font was not compatible for your phone,If it was compatible for you it should apply and you should see it immeadiately,Rebooting is not required.
Try to connect the computer and Use the LG R&D Tool to flash the ROM.
Click to expand...
Click to collapse
No I wasn't using a custom font installer I was just putting a different font into the system root fonts folder and that ended up slowing down the phone so I restarted it and now its bootlooping.

MrKidQuisine said:
No I wasn't using a custom font installer I was just putting a different font into the system root fonts folder and that ended up slowing down the phone so I restarted it and now its bootlooping.
Click to expand...
Click to collapse
That's Because the font was written bad or the system cant render it because wrong format,that's why ended up slowing.
Turn off your phone,Hold Volume + And Plug it into USB.AndUse the LG Mobile Support Tool,Select CS_Emergency Mode and Flash...
Or if you could get into the phone into safemode,Fix it by replacing other font into the file.
That's only 2 way to fix your phone.

androidvillage said:
That's Because the font was written bad or the system cant render it because wrong format,that's why ended up slowing.
Turn off your phone,Hold Volume + And Plug it into USB.AndUse the LG Mobile Support Tool,Select CS_Emergency Mode and Flash...
Or if you could get into the phone into safemode,Fix it by replacing other font into the file.
That's only 2 way to fix your phone.
Click to expand...
Click to collapse
When I hold down volume up and power it just goes into the logo and if I continue to hold it it vibrates then immediately shuts off. Ive tried before to enter recovery mode on this phone but I think LG blocked it.

MrKidQuisine said:
When I hold down volume up and power it just goes into the logo and if I continue to hold it it vibrates then immediately shuts off. Ive tried before to enter recovery mode on this phone but I think LG blocked it.
Click to expand...
Click to collapse
Perform a factory reset. See this thread Q14.

I had a very similar problem that stemmed from trying to install a new font. When I tried a hard key factory reset, it did nothing to fix the bootloop. Rather, I think it made the phone impossible to reach with ADB by resetting the "debugging mode" setting along with everything else. My advice to you, though I haven't actually tried this because of the above problem, is to try to access your phone through ADB.
If that doesn't work, what I ended up doing was sending my phone to an LG service facility with a note attached detailing the problem and cause. They were able to restore it, despite it being rooted.

Update
Ok so I left my phone out unplugged for about and hour on the logo and it popped on so Im trying the same thing again but with the sim card in and if it works Im going to see if I can make the thing load faster by updating the permissions on the font file or using a font installer all together.

MrKidQuisine said:
Ok so I left my phone out unplugged for about and hour on the logo and it popped on so Im trying the same thing again but with the sim card in and if it works Im going to see if I can make the thing load faster by updating the permissions on the font file or using a font installer all together.
Click to expand...
Click to collapse
Still stuck in bootloop no other activity since restarting and puting in sim, I also about two hours ago took out the sim and restarted

similar problem
i was messing with the app chainfire 3d was prompted to install a graphics driver which and gave me a warning that it might brick my phone if it was not compatible so i said what the hell and proceeded now im stuck at lg logo with no clue on how to get it back to normal i am currently trying lg mobile support tool which seems to only stay at 10% been at it for about 15 min now not sure if just copying files or what im clueless on what to do im running rooted d415 stock rom my phone is on download mode right now

Same problem, different cause
I was installing an update to CM. In the recovery it said something about symlinks failed. I restarted, and now phone will get past the LG logo, but black screen. I can't access recovery either. In adb, I see the device, but it is unauthorized, and I obviously have no way to authorize it. Any way to fix this without sending it back?
Thanks in advance

Fixed it
I found a way to recover, but you must have a custom recovery.
Use the button shortcut for force reset. It will take you to recovery. From there you can restore or reinstall a rom.

Soft-Bricked Moto G (2014) won't move beyond Fastboot

Hey guys!
So I've got an issue I'm struggling with on the Moto G (2014). First I'll tell you as much as I can about the phone: I bought it from the Motorola website, so I think it's running whatever the stock firmware is. Also, it's the 8 GB US model and isn't tied to any carrier. (I have it on T-Mobile, but got it directly from Motorola. I was trying to figure out what the firmware is but the closest I've been able to get is by running the Motorola Device Manager app while the phone is in fastboot mode. It says there are no available updates for: 21.11.17.titan_retuaws.retuaws.en.us The bootloader is locked and the phone is not rooted. It's pure stock, though it might have automatically gotten an OTA update to the latest official release, I can't be sure because I bought it for someone else.
Okay, so the problem. I'd bought the phone for my dad and set it up and it worked fine for about two months. Yesterday, he came by my place and asked if I could take a look at it because it was stuck on one screen and since there was no removable battery, he didn't know how to reset it. The screen it was stuck on is the boot screen where the Motorola logo is supposed to come up. It was up, but the bottom half of the logo was stretched to the side and pixelated so my first reaction was "crap, he hit it against something and there's damage to the screen." But there was no visible damage to the screen anywhere (neither from a hard hit or from pressure) and he's got the flip case for it and he said it hadn't been hit or anything.
I tried to power it down by holding down the power button, but as soon as it went off, it tried to start up again. A bootloop that always froze on that messed up Motorola boot screen. I set it on the charger for a bit and let it run through the loop a few times and at one point it got as far as the "world" screen where it shows a cartoon planet. This extended down past where the weird stretch happened on the motorola graphic and it was perfectly clear so I realized there was no damage to the screen, just some sort of boot error.
So then I tried booting into fastboot (hold both volume buttons down along with the power button for a few seconds, release) and I was able to get into fastboot. I tried scrolling down to recovery and then hitting the volume up key to select it but the second I hit the volume up key (the selection key in this mode) it reboots the phone. It doesn't go into the recovery screen, just turns off the phone. I tried this for the "Factory" (reset) option, for the "Normal Powerup" option, and the others. Instead of getting anything different, selecting any of them turns the phone off and nothing happens. The computer is recognizing that there's a device connected to it when I have the phone plugged in via usb in fastboot to my Windows 8 laptop. It also appears that I can enter commands in fastboot. (Though I'm not sure what to put in to fix this so I'm turning to you guys.)
So I can't figure out what's wrong. I've got some experience in flashing roms, both manually and with some of the tools, but haven't had to deal with what I'm assuming is a soft brick before.
Can anyone offer any help?
Thanks very much.

Watch this video and try again
https://www.youtube.com/watch?v=vf2sOPoE2b4

Roldorf said:
Watch this video and try again
https://www.youtube.com/watch?v=vf2sOPoE2b4
Click to expand...
Click to collapse
Unfortunately that didn't work. I was able to click the "restore to factory" part and it seemed to do that but I tried it again with the "wipe cache partition" and it just reset. I tried to restart normally and nothing happened. I will start boot and go to the Motorola logo but will always fail there, no matter what I try.

I'm still stuck with the soft-bricked phone. Any help going from Fastboot to somehow getting it to work?
(As I stated in the OP, the recovery options don't work. It seems only the Fastboot area is working.)

try to reflash the rom via fastboot, using the commands on 4.2 on this thread
if you have fastboot working they must work and re-flash the stock rom and everything back to stock...
to have the XML zip of yours rom search in here and download the file regards yours model and OS version that you wanna...
download, very slow download, unzip, to the some folder of mfastboot and give the commands a try... :good:

This is how to solve *ANY* softbrick on the Moto G 2014 (2nd Gen Moto G)
Try unlocking your bootloader with the given instructions on Motorola's website. You can flash a recovery like TWRP or CWM using mfastboot-v2. After flashing the recovery you can reinstall a custom ROM or stock ROM to fix the soft brick. ADB is only available if you enabled USB debugging although it will allow few commands. Using mfastboot-v2 after unlocking the bootloader will play the main factor in resolving the soft brick.:laugh::good:

eyhajee said:
Try unlocking your bootloader with the given instructions on Motorola's website. You can flash a recovery like TWRP or CWM using mfastboot-v2. After flashing the recovery you can reinstall a custom ROM or stock ROM to fix the soft brick. ADB is only available if you enabled USB debugging although it will allow few commands. Using mfastboot-v2 after unlocking the bootloader will play the main factor in resolving the soft brick.:laugh::good:
Click to expand...
Click to collapse
hello eyhajee.
My Moto G 2014 xt1068, running on Android 5.0.2 has some softbrick issue.
I have unlocked its bootloader, rooted it, unrooted it and while I was trying to lock its bootoader, I forgot to enable USB debugging and now it's stuck on fastboot mode.
So I wanna ask that can flashing a custom ROM turn my phone on??

I think so. If you are able to run some basic commands you should be able to flash it to emergency mode.

HTC Desire 510 stuck on logo and won't factory reset

Last nite all my apps including stock/system apps started crashing back to back and my cell locked up so I restarted it, it ran fine for a cpl min then did it again. I tried rebooting and noticed there was no sound when tha orange logo came up next. I knew I was in trouble. It then got stuck on tha white logo.
So I pulled up fastboot and tried factory reset. It will go to tha screen wit 2 arrows in a circle wit tha loading bar underneath, tha loading bar does not show a single bit of progress and it only stays on that screen b4 rebooting and getting stuck on white logo again. So no luck wit factory reset.
My cell is NOT rooted and my pc is NOT recognizing it when plugged in via usb.
I am wondering if there is a chance I can dl tha stock rom onto my sd and from fastboot screen get it to read and install that stock rom tho it's not even rooted, or am I completely screwed?
I appreciate ne help I can get.
I am tech smart and have rooted a cpl androids b4 via odin app and cwm/kouma. So I am familiar wit these processes tho it's been a while.
Thanx, Kari

Kari13electra84 said:
Last nite all my apps including stock/system apps started crashing back to back and my cell locked up so I restarted it, it ran fine for a cpl min then did it again. I tried rebooting and noticed there was no sound when tha orange logo came up next. I knew I was in trouble. It then got stuck on tha white logo.
So I pulled up fastboot and tried factory reset. It will go to tha screen wit 2 arrows in a circle wit tha loading bar underneath, tha loading bar does not show a single bit of progress and it only stays on that screen b4 rebooting and getting stuck on white logo again. So no luck wit factory reset.
My cell is NOT rooted and my pc is NOT recognizing it when plugged in via usb.
I am wondering if there is a chance I can dl tha stock rom onto my sd and from fastboot screen get it to read and install that stock rom tho it's not even rooted, or am I completely screwed?
I appreciate ne help I can get.
I am tech smart and have rooted a cpl androids b4 via odin app and cwm/kouma. So I am familiar wit these processes tho it's been a while.
Thanx, Kari
Click to expand...
Click to collapse
Please tell us what what version is your phone (32 bit or 64 bit), so that we could point you in the right direction.

denny.hell said:
Please tell us what what version is your phone (32 bit or 64 bit), so that we could point you in the right direction.
Click to expand...
Click to collapse
I'm not sure. I can tell u it's a 4gb, 4g boost mobile htc desire 510. How can I find out since it's stuck?
Thanx, Kari
btw, it's tha white one wit no rear facing flash for camera.

Kari13electra84 said:
I'm not sure. I can tell u it's a 4gb, 4g boost mobile htc desire 510. How can I find out since it's stuck?
Thanx, Kari
btw, it's tha white one wit no rear facing flash for camera.
Click to expand...
Click to collapse
Since it's from boost mobile that means that it is the 32 bit version. Now, If you'd like the pure stock back you can get it here: http://dl3.htc.com/application/RUU_A11_CHL_K44_DESIRE_SENSE60_Sprint_WWE_VM_1.49.652.3_Radio_1.47.40.0224_NV_SPCS_1.08_003_release_448617_signed_2.exe
Also here are some instructions on how to proceed with the install:
Performing the ROM Update:
1. Download and save the HTC Desire™ ROM update to your PC.
2. Connect your device to your PC via the supplied USB cable.
3. If the device is not recognized by the PC, ensure you have HTC Sync Manager installed and then disconnect and reconnect the device from the USB cable.
4. Once the device is properly recognized on the PC, locate the HTC Desire 510 ROM Update that you downloaded. Double-click on the file to launch the system update wizard.
5. Follow all of the system update wizard instructions shown on your PC.
6. Once the update is complete, click Finish in the Wizard and the device will reboot.
7. Once the device reboots, the initial setup wizard will appear.
8. Once the initial setup process is complete, open Play Store, tap the Menu icon, then select My apps and ensure all installed apps are updated.
9. After initial setup and updating all apps, the device is ready for use.
Note: If the ROM update wizard fails to recognize the device, close the wizard and then follow the steps below:
· From a powered off state, hold VOLUME DOWN while powering on the device.
· Use the volume buttons to scroll to FASTBOOT and then press the POWER button to select it.
· Connect the device to the PC while in this state and attempt the ROM update again.
To exit FASTBOOT manually, use the volume keys to navigate to REBOOT and press the POWER button to select it.
But if you'd like to try out some other ROM's there are a couple of good ones here on this site along with great tutorials about rooting and other stuff. Just make sure you pick the ones that are for the 32 bit version.

Please help me to unbrick my G5S Plus

Hi guys,
I got a G5S+, which got stuck the other day.
It was booting, showing the blue Motorola screen but ended up with a lying down android with a red questionmark and saying 'no command'.
I read through a couple of threads and finally decided, I need to flash stock again.
I did not have switched on USB debugging and so on, as the phone was quite new to me.
I decided to run with that tutorial here:
https://forum.xda-developers.com/g5-plus/how-to/solution-to-flash-stock-romfactory-t3691396
Which seemed to be the right one.
Said so, booted into bootloader, installed the driver on my Win10 PC and ran through the steps.
I gut stuck on 'fastboot flash system system.img_sparsechunk.3' (15mins waiting..... after the steps before required about 12 Sec each) and needed to disconnect and connect the phone again.
Started with the same command and it worked.
Anyway when I got to the command 'fastboot flash system system.img_sparsechunk.5' I realized in the Potter Retail, there is no such file (neither there is 6 or 7).
I skipped the commands and continued.
When it came to rebooting the phone disconnected and thats it.
Since then I am not able to turn my phone back on.
Sometimes there seems to be a small notofication led showing up when trying to turn on the phone.
And you can hear the USB connect sound when I connect it to my computer.
Did anyone of you guys experience the same issue or has an idea what to do?
I have no idea what I shall so.
Best regards,
Matt

Which stock ROM did you flash? I'm hoping that following that guide, you flashed a stock ROM for sanders (i.e. the codename for Moto G5S Plus) and not for potter (codename for G5 Plus), which appear to be not compatible with each other.
Your original issue appears to be your device is booting into the stock recovery (which the start of is the 'no recovery' screen).
Do you know what model number or retail software channel, or the software build you had on your device before it failed? If so, we may be able to flash the correct sanders stock ROM to your device and get it going again. Another user appears to have gotten their device working when they incorrectly flashed the potter stock ROM and not sanders. https://forum.xda-developers.com/moto-g5s-plus/help/bricked-moto-g5s-plus-t3747064 Ideally you will want to flash the correct stock ROM for your device.

Oha damn you are right.
I am an idiot and tried to flash Potter to a G5S Plus.
Oh boy. I should not flash a cellphone after a long day at work.
I had the latest safety update installed and the latest release.
I am not sure though which software that used to be.
Unbelievable.....
Anyway, so my screen does not show anything anymore.
I guess the display driver dows not work or something like that.
The cellphone is still working I think, as the USB sound still appears.
Does anyone have an idea what to do if the screen stays black.
I still cannot believe it.....
Thanks though for your help!
EDIT: fastboot still reckognizes the phone. I guess this is good.
But the command 'fastboot oem fb_mode_set' runs into an error.
Edit2:
I skipped the first command and everything ran through (with some error messages though).
I hope it works now.
Device is currently rebooting and showing the blue motorola screen.
Lucky me.....

Okay, at least your device is booting now (ish)... I saw your other post and was wondering if you were able to boot from the bootloader.
1)Boot to fastboot (probably easiest by powering off your device, then hold down power and volume down keys until your device boots).
2)Once in the fastboot menu (with details about your device, like bootloader version), check that 'Start' is selected, and press the Power button to select. If 'Start' is not showing, use the volume keys to scroll through the options until 'Start' appears. Sometimes, this booting via fastboot bypasses an auto-boot to recovery mode.
Failing that, if you're on the 'no command' screen, then hold down the power button and tap the volume up key. Release both and it should let you into the recovery menu. Then, you can try to reboot to system.

Hi there,
I ran through all the steps you said.
But I ended up having the same issue. I always get back to the broken droid.
Is there a way to flash a completely new ROM to the device in its current condition?
I don't mind having a customrom, but I want to get it working again.
Thanks!
Matt

I solved my problem:
It was the SD card. I cannot believe it.
I got myself another G5S Plus and swapped everything:
Same issue.
So I removed the memory card and all good again.
I am quite sad though not having figured that out earlier, becoz all my data is lost now....
Thanks for your help though!