Database Users

Defy-semi bricked

Was running an ICS rom for about 2-3 weeks. Can't remember which 1 but I do remember that it was a Defy+ (port ?, 4.0.3). It changed my phone description to (MB526). Ran pretty good but would randomly freeze and not move. Decided to re-flash. Went to clockwork to run a backup, not sure/don't remember what I did after that as it's been a week since I'm trying to get Defy back up and running. got stuck in a boot loop. Now it's not even looping, just freezes on google splash screen.
My problem: I can get into boot loader fine but phone is not recognized/won't connect with RSD Lite. Tried a couple different versions including v4.9. If I could connect I'd just re-flash an sbf. Drivers are fine. I have other Motorola Apps such as Flash&Backup3, P2K, Motorola Phone Tools for a couple other phones I have so I should have any drivers I need, Also phone was flashed prior to this with these drivers installed.
I cannot get into fastboot, stock or CWM recovery. I did notice "all" of the zip files on the SD card were gone. Roms, Apps, etc. Everything else was still there. When phone is off and I plug into the computer, the white led lights for a bit, then the blue, then the google splash screen and that's it. Won't move after that. So I'm guessing my recovery is still there but I can't access it. Tried connecting with/without SD in the phone. No luck.
I cannot connect with ADB either. Says no device found.
I've downloaded and re installed everything I could but still no luck.
I am at a loss as to what to try next. This is not my 1st flash so I like to think I know what I'm doing. Flashed 11 different phones, 5 different OS's. So I'm not a noob. But now I need some help from you guys/gals.
Anyone with any suggestions would be welcome.
From my limited knowledge I understand that if you can get into the boot loader your not bricked ?
So what do I do next ? HELP. Questions ? Ask away. This is starting to piss me off.
Bootloader 09.10
Battery OK
OK to Program
Connect USB Data Cable
After pluging in usb, phones says:
Transfer Mode: USB
Did all this on Vista Desktop. Should I try my Windows 7 Ultimite laptop ?
Mods: apologize if it's been covered but I didn't see my problem in the threads, not that I looked at all of them.
Thanks

crz6662 said:
When phone is off and I plug into the computer, the white led lights for a bit, then the blue, then the google splash screen and that's it.
Click to expand...
Click to collapse
When the indicator is lit in blue, press the volume down. It should boot recovery.
crz6662 said:
Should I try my Windows 7 Ultimite laptop ?
Click to expand...
Click to collapse
Yes.
Also you could try to connect your phone to another USB port.

Try that when I get home from work. Let you know if either worked.

Ant-ON said:
When the indicator is lit in blue, press the volume down. It should boot recovery.
Solved. Ya know, I thought I there was something I was missing. That's what happens when you own 9 different phones and play with them all. I had just finished flashing an old Motorola RAZR V3re.
Appreciate the heads up.
Up and running in 5 minutes. Thanks
Click to expand...
Click to collapse

Any help fixing my Nvidia shield software brick

Right first of all I know I've been stupid..... It's just one of those days.
Okay I want to test, [ROM][Full Android 5.1 for Shield TV][v.2.2]
Got it installed and it was working perfect, but as I said before I only wanted to test, but then I decided I want to switch back to stock.
so I download the stock firmware from Nvidia, next I try to get into fast-boot by holding the power button down for 3 seconds, but for some reason this feature is disabled on [ROM][Full Android 5.1 for Shield TV][v.2.2]
what I thought was weird, but oh well I can just do it through cmd on the computer, i got in fine, but then unluckily for me I had a power cut.
Why it was doing the new process of copying over the new stock ROM.
Now I'm stuck on the Nvidia boot screen.
And my boot button still doesn't work, if I hold it down for 3 seconds, so my question is have I bricked the device, is it now an expensive paperweight.
Is there any tutorial where I can solder leads to the motherboard, so I can get fast boot working, so I can continue with the installation of the ROM.

Managed to fix it myself, issue resolved

ultimate_spy_binns said:
Managed to fix it myself, issue resolved
Click to expand...
Click to collapse
Please can you explain how you resolved this for anyone else with similar problems?

he used the "Search" on XDA

alsheron said:
Please can you explain how you resolved this for anyone else with similar problems?
Click to expand...
Click to collapse
I held the button down for 10 seconds.
Then I pulled the power cable out, then quickly pressed the power button again for three seconds and this time it worked, got into recovery.

Phone still gets stuck in boot loop after flashing stock firmware

I have a TMobile/MetroPCS GS4 model SGH-M919N that got stuck in a boot loop last week. I was finally able to find working firmware last night and used Odin to flash. Once it got to PASS my phone automatically rebooted with the blue recovery boot text in the top left, but then it just went back into a boot loop. I tried all other firmwares and none of them got to 100% so now I don't know what else I can do.

I have the same issue on a GT-i9505. I was using my phone this evening when it randomly rebooted and just keep rebooting until I removed my battery. After that, it was dead . Flashing stock firmwares like shooting a minigun and nothing works. Smells like a hard brick?

alesu69 said:
I have the same issue on a GT-i9505. I was using my phone this evening when it randomly rebooted and just keep rebooting until I removed my battery. After that, it was dead . Flashing stock firmwares like shooting a minigun and nothing works. Smells like a hard brick?
Click to expand...
Click to collapse
Have you tried replacing the battery? I figured I would try that but I havent gotten around to it yet

Not yet, i have no spare battery. Looks like when i plug the charger my phone just vibrates, like it's rebooting, and it's not showing anything. I found a similar issue here: http://forum.xda-developers.com/showthread.php?t=2532447
Looks like one guy did solve his problem.
*need to mention that by dead I mean it shows the "Samsung Galaxy S4 GT-I9505" logo and also shows "RECOVERY BOOTING", even though I didn't enter in recovery mode. Looks like now it doesn't shows anymore "RECOVERY BOOTING", but still, it doesn't boot. I was able to flash firmwares via odin and kies, but still no luck.
LE: It start booting by.. magic, i got to samsung boot logo, but that's all, crashed again.

After flash with Odin, immediately boot into recovery, perform a factory wipe, and reboot.

The problem is it doesn't boot into recovery.
LE: I managed to flash twrp via odin and boot into recovery, but i have an error:
"Unable to mount /data"
Any ideas?
LE2: Everything is useless, i managed to flash the rom, manage to boot into the rom, but then it will still reboot (which it did). Next step will be maybe to disassemble and clean all contacts.

alesu69 said:
The problem is it doesn't boot into recovery.
LE: I managed to flash twrp via odin and boot into recovery, but i have an error:
"Unable to mount /data"
Any ideas?
LE2: Everything is useless, i managed to flash the rom, manage to boot into the rom, but then it will still reboot (which it did). Next step will be maybe to disassemble and clean all contacts.
Click to expand...
Click to collapse
How did you manage to get into recovery?

harary said:
How did you manage to get into recovery?
Click to expand...
Click to collapse
Yes, but if I leave my phone in recovery (stock or custom), it just either freezes, either reboots, even though i don't do anything, just let it idle.
I can't manage to boot into the ROM 'cause eventually it will reboot. I couldn't finish the setup wizard.

OK so I don't know if this helps, but I managed to at least get past the "blue recovery boot" part. When the phone vibrated I let go of the power while still holding home + vol up, and I managed to get to the android guy with a blue progress bar below him. My phone shut off as the progress bar got 80-90% but now I know it's not impossible to start recovery.

Well, nothing works. After flashing pit file, an 4.4.2 odin prerooted image from here, cf auto root and then twrp, it will still randomly reboot. I manage to get past the boot logo into setup wizard, but phone just freezes after a couple of minutes, can't finish the setup wizard. Also, if i idle in twrp it will reboot sooner or later, tested already.I left my phone idling in twrp just to recharge my battery.
At least i have no more "unable to mount /data" errors.

I finally got it to work, all I had to do is keep flashing twrp and stock firmware back and forth. But it is just one problem after another with this thing, the problem now is every 5 minutes it will freeze and restart, also it tells me there is no sim even though it worked the first time i put it back in.

Operation Ivy said:
I finally got it to work, all I had to do is keep flashing twrp and stock firmware back and forth. But it is just one problem after another with this thing, the problem now is every 5 minutes it will freeze and restart, also it tells me there is no sim even though it worked the first time i put it back in.
Click to expand...
Click to collapse
What do you mean with back and forth?

harary said:
What do you mean with back and forth?
Click to expand...
Click to collapse
It means he flahsed and reflashed many times until he got lucky and it worked. That's what happened to me also. But i have the same issue, phone reboots or freezez after a couple of minutes, even though everything else is installed properly.
Dude, we have the same issue. Btw, is this happening to you too? Like, now and then when the phone freezes, that the screen is turning to a bright yellowish green?
I know a friend who repairs phone hardwares for a living, i gave it to him, i'll let you know how this went.

alesu69 said:
It means he flahsed and reflashed many times until he got lucky and it worked. That's what happened to me also. But i have the same issue, phone reboots or freezez after a couple of minutes, even though everything else is installed properly.
Dude, we have the same issue. Btw, is this happening to you too? Like, now and then when the phone freezes, that the screen is turning to a bright yellowish green?
I know a friend which repairs phone hardwares for a living, i gave it to him, i'll let you know how this went.
Click to expand...
Click to collapse
I got several times into Recovery Mode now, flashed several ROMs. I had no issues with freezing, especially not in TWRP Recovery Mode. But sometimes if i am trying to go into Recovery Mode or i just want to start ROMs, the screen turns into yellow behind the Samsung logo. If i dont take out the battery this wents into a complete white, but nothing happens.
Yes please tell if you got some news..

guys its not hard bricked its a problem wiht your power button
my friend had the same issue and then i killed the battery by letting it keeep bootlooping
then plugged it in and let it charge to around 10% and booted it
just try to press the power button slowly

Joashrox said:
guys its not hard bricked its a problem wiht your power button
my friend had the same issue and then i killed the battery by letting it keeep bootlooping
then plugged it in and let it charge to around 10% and booted it
just try to press the power button slowly
Click to expand...
Click to collapse
But it is sure that the power button is working because i get this blue "recovery booting". Or am i wrong?

So.... bad news, the guy whom i gave the phone to said that it's a short on the motherboard and there's nothing he can't do other than changing the motherboard. If you guys found another solution and that guy is mistaking, let me know.

alesu69 said:
So.... bad news, the guy whom i gave the phone to said that it's a short on the motherboard and there's nothing he can't do other than changing the motherboard. If you guys found another solution and that guy is mistaking, let me know.
Click to expand...
Click to collapse
Replace power button to new one. I have the same problems with s3 and this works. Try it.
Sent from my GT-I9300 using XDA-Developers mobile app

My phone is dead, it's not even charging anymore. The guy whom I give it to said it's a short on the motherboard. You guys managed to solve something with your phones? Or still a dead end?

alesu69 said:
My phone is dead, it's not even charging anymore. The guy whom I give it to said it's a short on the motherboard. You guys managed to solve something with your phones? Or still a dead end?
Click to expand...
Click to collapse
If You can't charge phone... Yup, motherboard is died. If You plug the charger and see something this have to be button but if You plug charger and don't see anything this is motherboard.

How to recover from bootloop after Shield 2017 8.0.1 Experience update?

Hi, hoping for some advice, I have three shield 2017's, updated 2 of 3 to 8.0.1 without issue, last one went into bootloop after the update.
The problematic one had the update pending for a long time, just never rebooted to install it, until now.
I followed the nvidia KB, and tried the the fast boot menu, recovery kernel, factory reset, still bootloop.
I contacted support over chat, they had me boot without HDMI, press A, reconnect HDMI, no difference, shield keeps rebooting even without HDMI.
Support then had me change power plugs, since I have three shields, I tested using another working shield PSU, same problem.
Support then had me boot, wait 2 mins, press home and left on dpad, wait for blue flashing, no difference, as shield keeps rebooting, waiting for anything is really pointless.
Out of frustration, and not knowing what I'm doing, I did a factory reset directly from fastboot menu, now I get a can't verify firmware, lock firmware, press A message, and then it just sits at the nvidia menu, not good.
(Btw, it took many tries to get the fastboot menu to launch, first time was lucky, but it continued rebooting before I had a chance to move the menu, then it seemed impossible to get again.
Is there a reliable way to get the fastboot menu up using the controller A+B or other method?
Given the state of the shield, can I recover the device, any advice on how, please?

if you are able to access fastboot menu everything is possible if it's not a hardware problem, grab one of the recovery images for your device and use one of the many tutorials available to recovery your device

zecabra said:
if you are able to access fastboot menu everything is possible if it's not a hardware problem, grab one of the recovery images for your device and use one of the many tutorials available to recovery your device
Click to expand...
Click to collapse
Ok, that's good news then, I'll order and A-A cable and try one of the tutorials (I was pointed to one on reddit).
Any advice on how to reliably launch the fastboot menu using the controller, I do the A+B button, power on, and it only occasionally works?

Nexus 10 bricked, bootloader possibly corrupted: fix?

I just aquired a used Nexus 10 that I wanted to flash with Lineage. Before that, I had successfully flashed every android device I have ever owned, so I thought there'd be no problem. After unlocking the bootloader I tried flashing TWRP recovery (on Linux using fastboot in the terminal), but it took several minutes and when suddenly the sreen started flickering and the flash still wasn't done, I tried to CTRL+C to no avail. I figured that I'd at most corrupt the recovery which would be quite fixable, so I unplugged the cable and tried restarting the tablet. I could still select the options in the bootloader, but when I selected anything, it didn't work (not even shutdown).
Whenever I try to start the tablet now, nothing happens. When it is plugged in to the wall, it shortly shows the "full battery" symbol and the goes black again. No combinations for bootloader or recovery work anymore. I suspect that the unsuccessful flash corrupted the bootloader, so how could I fix that. I do have FTDI and STM32 flashing devices, if that is any help.
P.S.: I already tried removing the battery in case there was anything in volatile memory preventing the boot.

I kind of jumped the gun on this one. As I had suspected, aborting the recovery flash did not corrupt the bootloader. The solution was simply an empty battery. I didn't notice, because it showed me a full 100% when I initially tested it, so it might be a broken battery, after all.
But still, got it to work now. Thanks for this great community, I could not have learned all the android stuff without it.

Atreus said:
I kind of jumped the gun on this one. As I had suspected, aborting the recovery flash did not corrupt the bootloader. The solution was simply an empty battery. I didn't notice, because it showed me a full 100% when I initially tested it, so it might be a broken battery, after all.
But still, got it to work now. Thanks for this great community, I could not have learned all the android stuff without it.
Click to expand...
Click to collapse
Good to hear:good:
Please mark your thread as [SOLVED] if it is, or give us an update on how did you go about the battery perhaps?
Cheers