Develop Bugs

[Q] Defy T-Mobile boot loop how do I fix

I've reviewed some solutions on here regarding the UK rom version and loading it to the device. My concern is for the warranty on the device does anyone have the T-Mobile rom available to load on the defy? I'd assume that'd fix my issue where the phone has a boot loop and a wipe is not fixing it. I tried talking to motorola and that was a complete fail (see conversation below).
Reymer: Hi, my name is Reymer. How may I help you?
James: i am using a motorola defy. all of sudden today it stopped working. it boot loops showing the motorola boot screen and tmobile screen but then keeps doing this over and over again. i tried to do a factory reset but still failed. is there anyway for me to manually update with the original rom again with an update.zip similar to the motorola cliq?
Reymer: I am sorry to know that.
Reymer: Are you referring to a bootloader screen?
James: not exactly. it acts like it's booting up as normal but keeps repeating the process. i help down the volume and pwr button to get to the other screen can't remember what it's called so i can attempt a factory wipe on the device.
Reymer: Can you please take out the battery, return it after a few seconds and turn the phone back on? Let's try to see then if the phone is still doing the same thing.
James: i tried that already. still the same thing.
Reymer: Were you able to use a different battery?
James : why would a different battery change anything if it's software related? i know from all the research i've done so far it's needs to software reloaded to it however i cannot find the software for this device on the motorola website. it's a tmobile usa phone.
Reymer: We need to determine first if it's a phone or battery issue.
James : okay but explain to me what the battery has to do with the phone software? that's like telling me to put gas in my car to fix a flat tire they have nothing to do with each other.
Reymer: How did you know if that's a software issue?
Reymer: We are doing every means to isolate the case.
James : because it powers on and starts to boot up but just boot loops it doesn't power off. the battery is brand new and has a full charge i got the battery today so i know it has nothing to do with the battery. i've also worked with android development and understand isolating the issue checking for hardware concerns first which i did prior to getting on this chat.
Reymer: I suggest that you send in your phone at our repair facility and have it evaluated by our repair technicians. If proven that it did not suffer physical or liquid damage, that will be repaired for free.
Let me just inform you of the repair time frame, it will be 5-7 business days from the date we receive your item before it will be sent back to you.
Reymer: All Motorola phones and accessories have a standard one year warranty barring physical or liquid damage from the date of purchase.
I ended the conversation after that

Use my debranding/debricking guide in the dev section. If you are a US customer you will lose 3g and wifi calling as the US firmware is not available at present so you have to use UK - there are fixes for this about.
Sent from my Defy using XDA App

My first response to your phone call is... well, when I'm asked to do something absurd with my gear (and why would you have an exta battery anyway?) I always say, "yes, done that." "Have you tried jumping out the window with the phone up your ass singing "God Save the Queen?" "Yes, twice. No go." However... there do seem to be some whacko battery issues related to rebooting issues on Motorola phones. Example:
"I just got a new battery for my Droid, and the battery came 60% charged. So I did the battery drain until it powered off. I then put it on the dock to do a full charge, and now the phone is in a constant boot loop."
Same guy then:
"I just tried the old battery, and it does not go into the loop with the old one."
So..?

scrannel said:
My first response to your phone call is... well, when I'm asked to do something absurd with my gear (and why would you have an exta battery anyway?) I always say, "yes, done that." "Have you tried jumping out the window with the phone up your ass singing "God Save the Queen?" "Yes, twice. No go." However... there do seem to be some whacko battery issues related to rebooting issues on Motorola phones. Example:
"I just got a new battery for my Droid, and the battery came 60% charged. So I did the battery drain until it powered off. I then put it on the dock to do a full charge, and now the phone is in a constant boot loop."
Same guy then:
"I just tried the old battery, and it does not go into the loop with the old one."
So..?
Click to expand...
Click to collapse
As far as I know, Li-ion batteries hate depletion, they shouldn't be totally depleted.
"Depletion below the low-voltage threshold (2.4 to 2.8 V/cell, depending on chemistry) results in a dead battery which does not even appear to charge because the protection circuit (a type of electronic fuse) disables it." -
en.wikipedia.org/wiki/Lithium-ion_battery#Prolonging_battery_pack_life

TPGamer said:
As far as I know, Li-ion batteries hate depletion, they shouldn't be totally depleted.
"Depletion below the low-voltage threshold (2.4 to 2.8 V/cell, depending on chemistry) results in a dead battery which does not even appear to charge because the protection circuit (a type of electronic fuse) disables it." -
en.wikipedia.org/wiki/Lithium-ion_battery#Prolonging_battery_pack_life
Click to expand...
Click to collapse
Not sure what you mean. That a bad battery can cause problems? That IS the point, even if it's something produced by the user. It's probably not the cause, but it might be worth a try? This rebooting issue, though not tiny, does seem to be limited to some Euro (UK?) phones. Maybe a release of a bad batch of batteries? I realize that that poster probably should not have depleted his battery (though... don't we all once in a while?) maybe by crapping out his battery he induced his re-booting issue. But that still could be the cause of others' problems.

Hi !
I have this problem too.
My Defy always reboot in loop
This is a french Vodafone branded phone with Blur_Version.2.21.0.MB525Blur.Vodafone.FR
The only thing I see is when I received the phone I started it without charging the battery.
I know that was noticed in big font but i was hurried and didn't think that can be a problem for the battery

every body i need help.
i have somthing wrong with my cell phone motorola defy
my cell phone do not turn on, but when i conected to computer i could install new rom ,
and again do not work with new cell phone and do not turn on again

Hi.
I have a Blur_Version.2.51.1.MB525,T-Mobile.en.GB is it rootable and is there a stable UK based custom rom?
Oyeah any Cynogen Mod 7 for the future?

Skillganon said:
Hi.
I have a Blur_Version.2.51.1.MB525,T-Mobile.en.GB is it rootable and is there a stable UK based custom rom?
Oyeah any Cynogen Mod 7 for the future?
Click to expand...
Click to collapse
I would love to see that also.

i have the same problem and tmobile is pretty much like screw you ive tried rsdlite and nothing all to no avail i think im just chalking 399.99$ and i promise im never buying another motorola product again

scrannel said:
"I just got a new battery for my Droid, and the battery came 60% charged. So I did the battery drain until it powered off. I then put it on the dock to do a full charge, and now the phone is in a constant boot loop."
Click to expand...
Click to collapse
that actually happened to me and i dont know what to do its really annoying.

Is it possible to recover data from a truly bricked phone?

I used these searches before compiling this thread;
"how to recover data from a bricked SGN"
"data extraction from a SGN that will not boot"
"removing the HD from samsung galaxy nexus"
These searches did not yield results that replicate my situation. The only search that resulted in many entries were for people with "bricked phones" that (at least somewhat) responded to input. I associate the term "bricked" with a phone that does not respond to input, or show any indication of getting power.
My phone is a Samsung Galaxy Nexus on verizon wireless. It has been rooted and is running a custom ROM by...AOKP i think. I had some assistance each time I rooted and updated my ROM.
Here is my problem, what caused it,my troubleshooting steps, and what I'm trying to do. My phone was partially submerged in water for an unknown amount of time. The battery and SIM were removed and kept in a water proof container within an hour of submersion. The water damage indicator stickers (on both the battery and the phone have not been triggered). About 24hrs later, the phone was placed in a zip lock bag with 4 desiccant silica gel packs where it will remain for the next 24. Per vzw's tech support, I tried to power the phone on using the charger and the battery removed. No change. Verizon was not advised of the partial submersion, only the non triggered water damage stickers. This phone is under warranty and a replacement has been shipped. I confirmed that my contacts are backed up to google.
The reason for this post is, I have close to 30GB of pictures and videos that I stored on this device's "internal SD" that I want to recover. Looking through the searches I mentioned above, it sounds like this isn't so much a separate card, but more of a partition on the phone's HD. I have been told by vzw that neither their branch office tech support, nor their recovery/diagnostic team that analyzes returned phones has the capability to remove and return this data.
If someone here has hardware experience with cracking open a SGN and swapping the "internal SD card" I would greatly appreciate any information available for this task.

if it cant turn on, you cant retrieve data.

Zepius said:
if it cant turn on, you cant retrieve data.
Click to expand...
Click to collapse
Well..OK. I'm not ready to give up just yet. When my desktop PC's power supply failed, the PC was unusable, and didn't indicate power. I swapped that out and it now it works fine. This seems like it could be a similar situation. I at least want to exhaust every option I have before throwing in the towel.
Those 30GB contain hundreds of pictures of the first 2 years of my kid's life.
It seems to me that data recovery should still be possible if an replacement power source is utilized. Maybe more than just the power source has failed. Maybe every other hardware component in my wet phone has failed. But maybe, that "internal SD" is recoverable.
If anyone here knows what the "internal SD" looks like, and has successfully swapped one, I'll risk it. I know I can't trust vzw with such a task.
I realize this is a developers forum, and I'm asking for hardware failure advice. If anyone can refer me to a different forum that is more specialized to my specific task, I'll gladly take my trouble there.
Thanks for reading,
Jef

you're assuming 1 thing. the nand that houses the storage is in good health. When water is introduced, you have the unknown factors of what it does to circuitry.
im sure there is a ifixit teardown showing where the nand is. The problem is its soldered to the mainboard of the phone. You might be able to unsolder it, but thats a stretch.

Zepius said:
you're assuming 1 thing. the nand that houses the storage is in good health. When water is introduced, you have the unknown factors of what it does to circuitry.
im sure there is a ifixit teardown showing where the nand is. The problem is its soldered to the mainboard of the phone. You might be able to unsolder it, but thats a stretch.
Click to expand...
Click to collapse
Thank you very much Zepius. I googled "ifixit teardown samsung galaxy nexus" which lead me to a page (that I'm not able to paste here as a new user).
which is exactly what I was looking for. I wouldn't go so far as to say that I'm assuming the nand is in good health, just wishful thinking.

Anncoco - sorry, I don't remember what I did with this. It's been about 4 years, and this was 3 phones ago. I think I had some of the photos backed up somewhere else, enough that I never went to the trouble to disassemble the Nexus. From my notes - I remember the phone did not indicate it was getting power when plugged in.

[Q] Huge Battery Drain but no wakelocks

How is that even possible?
I have attached 2 screnshoot of a Galaxy Nexus battery drain.
My phone is 100% stock, I just restored the nexus official image. The battery should be new, I already sent the phone to the manufacter last month and I think they changed the battery.
I didn't even setup a google account, no app installed, wifi off and there is good signal.
There are no wakelocks. Screen was off all the time. The battery just go down.
(Some translation. Segnale rete mobile = mobile network signal, Attivo = active, Schermo Acceso = Screen on)
What should I do? Call samsung again and stay another month without my phone? Is there any other solution?

Well, for starters you could let it charge for another cycle or two to be sure about.Also I see the Network reception is not so good.That may be responsible for the drain, though I highly doubt it !

dhruv52004 said:
Well, for starters you could let it charge for another cycle or two to be sure about.Also I see the Network reception is not so good.That may be responsible for the drain, though I highly doubt it !
Click to expand...
Click to collapse
Yes, I'm trying to do some complete charge/discharge.
I have similar result in Airplane mode, network reception is not the problem.
Thanks for the answer. :good:
Anyone else with some advices?

No one?
I don't want to spend another month without my phone because of RMA :crying:

supermario3 said:
No one?
I don't want to spend another month without my phone because of RMA :crying:
Click to expand...
Click to collapse
I have the *exact* problem (or at least, similar).
I have RMA'ed my phone 2 times, teling me they had done a "mechanical repair" (in Italian, as per repair center label, "riparazione meccanica").
Don't ask me about the meaning of this. It could be everything, but one thing is certain: serial number of the phone is the same, so they did not change the motherboard at all.
Back to topic, I'm experiencing serious issues:
1) huge battery drain in airplane mode, even after complete stock and several ROMs (the service center restored 4.0.4 on it, funny)
How did I test: the day I received back my phone, I have simply fully charged it, switched to airplane mode overnight and I have lost more than 30% battery with NOTHING at all installed, I even left the wrong date/time !!
2) before RMA'ing it, it did not matter if I used 3G / WiFi or nothing at all: I always got a similar battery discharge curve.
BUT today I noticed something odd:
while testing for the (1) issue above, I noticed that the "Awake" (aka "Attivo") bar under the battery graph was pretty full blue colored, which is NOT normal actually. How can it be after a full wipe (or so, as per after sale service) ????
Let's try to troubleshoot this problem guys, because I'm really fed up
...and I don't want to sell this Nexus, I simply love it hehe
TODO:
1) Wipe and test again -> charging the phone right now
2) analyze dmseg (maybe there is an hardware issue that keeps interrupting the CPU) -> after a quick look it seems that actually my interrupt idea could be true ( "Resume caused by IRQ 39, TWL6030-PIH". This is the power management unit) but I have to see during the airplane mode test, not while charging (that might be correct)
3) measure the current and compare results against a nice study of another guy (that reported power consumption on different scenarios)
4) ??

LorenzNexus said:
I have the *exact* problem (or at least, similar).
teling me they had done a "mechanical repair" (in Italian, as per repair center label, "riparazione meccanica").
Click to expand...
Click to collapse
The same. They changed the battery in my case. I did a mark with a marker pen on the battery before sending it and the mark is not there after RMA, so they changed it. Phone serial is the same.
They also put 4.04 on my nexus, what a shame!
I did not experienced the "active" thing on the battery statistics. I had several wakelock from "RILJ" but after a full restore the disappeared.
I restored (again) the phone with nexus image, and even locked the bootloader, removed the sim card and disabled wifi, gps and everything. It always discharge by itself in a too short period of time.
Is there something I can tell to RMA to make them change my phone? I don't think it's a software problem.

supermario3 said:
The same. They changed the battery in my case. I did a mark with a marker pen on the battery before sending it and the mark is not there after RMA, so they changed it. Phone serial is the same.
They also put 4.04 on my nexus, what a shame!
I did not experienced the "active" thing on the battery statistics. I had several wakelock from "RILJ" but after a full restore the disappeared.
I restored (again) the phone with nexus image, and even locked the bootloader, removed the sim card and disabled wifi, gps and everything. It always discharge by itself in a too short period of time.
Is there something I can tell to RMA to make them change my phone? I don't think it's a software problem.
Click to expand...
Click to collapse
I agree, this must be an hardware problem.
To say, I have tried a long list of ROMs and kernels, as well as updating radio and all other sort of stuff.
Now the awake "problem" has gone, so today I'm gonna retry the (1)st experiment.
Let's see...
In any case tomorrow I'm going to go to the shop and ask them if they could be so gentle lending me a fresh battery to test out.

Some clues here?
http://androidforums.com/samsung-ga...drain-since-i-started-using-wifi-hotspot.html
I don't know if it might be related or not, did you ever use tethering?
Pernsonally speaking, yes I did.
Today I try to wipe radio and flash another one...

LorenzNexus said:
Some clues here?
http://androidforums.com/samsung-ga...drain-since-i-started-using-wifi-hotspot.html
I don't know if it might be related or not, did you ever use tethering?
Pernsonally speaking, yes I did.
Today I try to wipe radio and flash another one...
Click to expand...
Click to collapse
No, I never used tethering.
My phone is at RMA again, I asked to fix it FOR REAL, I'm just hoping.

I've had a similar experience since first getting the phone. While with light usage, I used to get anywhere between 16 hours to a full day of battery life, I'll only get between 4 and 6 hours of screen-on time. Whether full stock or ROMs, it's always been the same. I've eventually just chalked it up to hardware being the issue and made sure to always have a spare battery and charger with me at all times.

I got my phone back.
They said that they changed the motherboard. On the package the note is "sostituzione board unit".
In the next few days I am gonna do some test to see if they really solved the problem, I really hope so.

supermario3 said:
I got my phone back.
They said that they changed the motherboard. On the package the note is "sostituzione board unit".
In the next few days I am gonna do some test to see if they really solved the problem, I really hope so.
Click to expand...
Click to collapse
Nice to hear
Today I was suprised of my phone's duration (still no serviced again): more than 1 day (of course without doing much) and only 10% drain during the night.
I don't know what happened BUT i can say also that I'm experiencing now a problem with the network (GSM, 3G): the network crashes sometime also while calling or while idling.
Today it did not crash in a > 10min call, so let's see also the battery drain during this night
...because strange stuff happens!

try update to the latest new radio.. flash radio.img
galaxy nexus i9250

I think that the problem is solved.
It was a hardware problem.
I'm on CM10.2stable now.
Latest radio and bootloader.
Now my phone last enough .
I called Samsung a lot of times to urge them to fix my phone.
EDIT: I'm now on 20h20m on battery with 3h23m screen on and 4% left. Goood
Inviato dal mio Galaxy Nexus utilizzando Tapatalk

Mysterious i9190

Hello everyone! This is my first thread and I know it's the right site to ask this. (sorry for my english)
I bought this "suspicious" i9190 in Budapest 2 years ago. Since then it has been impossible to use it regulary.
Constant rebooting and freezes are part of its daily routine. As well as stopped apps and processes messages in a ridiculous way.
I have tried millions of ROMs, officials and customs, all kind of wipes and restores. I have even tried the eMMC brickbug apps looking for damaged chips or internal memory: Nothing, the phone is perfectly fine.
But here are some facts that may be relevant to find the problem:
- The phone came with the IMEI number scrached in the back of the battery.
- I've been using the phone for hours and hours perfectly fine as long as no update is performed and the Sync option is off.
- Doing the above I have even downloaded and used some little apps with no problems.
- When the major apps are installed, like Facebook and Instagram the phone begins to die, popping more and more "stoppped working" errors.
- The processes that fail the most are the google type but, in general, every single existing process has failed in this 2 years.
- I have noticed that when you start the phone for the first time after a wipe or a new ROM, it is better to create a new google account than using an existing one because the existing one, I think, will start updating everything while the new one will not. Anyway, using a new google account collapses the phone sooner or later.
Sorry for the long post, fellas. But I wanted to give you all the possible info I have about this phone.
Hoping for you can help me fix this issue... Have a good day.
Galaxy S4 mini GT-I9190

I'd guess at a hardware issue in the radio and related circuitry as you seem to get the issues when apps that send/receive data frequently are in use. Though it could be anything. You probably need to get it checked by an authorised Samsung repair centre ......... if your phone is not too "suspicious!"

IronRoo said:
I'd guess at a hardware issue in the radio and related circuitry as you seem to get the issues when apps that send/receive data frequently are in use. Though it could be anything. You probably need to get it checked by an authorised Samsung repair centre ......... if your phone is not too "suspicious!"
Click to expand...
Click to collapse
Thanks for your reply! Do you have an idea why they scratched the IMEI number? Maybe that could take me to where the exact problem is. Here is a photo of the back
http :// imgur. com/Sa0ptSm
Sorry for the link, my account still cannot post outside links

I was going to say they scratched the IMEI number probably because it was stolen so that it could not be tracked, but it is quite easy to see the number so that is probably not the reason. One place I used to work at the test department used to scratch the bar codes on faulty PCB's so that they cannot be scanned back into the system by mistake (if the fault tag comes off, etc) as that computer system did not prevent scrapped boards from being re-entered. So I would guess this may be the case with your phone, but of course we can't know for certain! But based on this and all tests of different ROMs etc you did I suspect it is quite likely the explanation.
What I would do is look for the same model that has a cracked screen on ebay etc so it's cheap to buy then swap the PCB's from the cracked phone to your good screen (swap everything to prevent the possibility of the boards not working due to different revision numbers, as has been reported when replacing the power boards on our phone). You can also buy a repair kit for a few dollars on ebay with screwdrivers, pry tool etc
http://www.ebay.com/itm/10-In1-Repa...et-for-Mobile-Phone-iPhone-6-5s-/281869038536
If the PCB on your phone was scratched to show it was faulty then taking to a repair shop is probably a waste of money, unless then run an assessment for free before they repair it.
Hope you can fix it for a few dollars!

not sure if this helps but that I actually managed read off the IMEI code correctly and it turns out its a turkish registered phone, I can PM you IMEI code if you want, also its not reported stolen (but i am guessing its most likely is), anyways thats all I was here to say, good luck.

XIAOMI MI A1; Just turned off by itself randomly when i was using it. Cant turn it on

Ive only had this phone for 1 month and while I was on my bed using the phone when suddenly my phone just powered off by itself and it wouldn't turn back on. Ive tried plugging in the charger but it didnt do anything. I tried to force it on but it didnt do anything. Also, it wouldnt turn on in any way possible.. I suspect that my battery is damaged but im not too sure since I do not know much about smartphone technology and i think its also because that i used the bluetooth function with my car and i noticed that the phone was slightly hotter than usual, maybe this was the case but i dont know. Please help me out here.
Thanks for your time.

Go to the repair shop official if theirs one, unofficial if their isn't. Or contact those you got it from & let them hassle with it. It could be many things from simple battery ribbon to fried SoC... Anyhow even if you got it on wild still in most countries who ever sold it to you must provide one year warranty by the law.

Zola III said:
Go to the repair shop official if theirs one, unofficial if their isn't. Or contact those you got it from & let them hassle with it. It could be many things from simple battery ribbon to fried SoC... Anyhow even if you got it on wild still in most countries who ever sold it to you must provide one year warranty by the law.
Click to expand...
Click to collapse
Got it, and mines official so yeah but I had apps such as Blackboard, Chrome and Google Drive on to check on my assignment work and details. SO if I were to get my phone fixed would they still appear in the background to continue the process?

42_Gummy said:
Got it, and mines official so yeah but I had apps such as Blackboard, Chrome and Google Drive on to check on my assignment work and details. SO if I were to get my phone fixed would they still appear in the background to continue the process?
Click to expand...
Click to collapse
What's cloud synced is recoverable regardless. As stated before it depends on what is the case of the problem. Could be a power stripe from battery which is easy & you don't lose any data or in the worst case it could be a main bord socket in which case you do as everything is on it (SoC, RAM, NAND...)...