Database Info

[q] need opinion!!

Hey guys
I gave my cousin my infuse 4g, which was running gtg's Infused latest ROM.
According to her, she was at the mall and she pulled out the phone from her pocket and all she saw was infinite logo bootloop.
At first to me it seemed like a soft brick but it's not recoverable.
When I put the battery in, it goes into infinite samsung logo bootloop.
Three button combo to CWM doesn't work, the download mode jig also does not work.
when i put the download jig in, the yellow downloading mode logo shows up for 2 seconds and then the phone turns off. and the process repeats.
When i put the charging cable in, it infinitely loops the "battery picture", turning off 1 second later everytime and turning back on...
I plan on taking it back to the AT&T Service Shop for a chance at claiming a replacement device.
So here's my question.
I've tried everything I can to get this thing back to a working state, but to no avail.
Does this mean that the engineers at the service center will also not be able to get it back up (meaning that they won't be able to tell that i've voided the warranty)?
I mean, something is seriously wrong with this infuse. it won't even go to download mode.
I bought this device back in July 2011, so I'm still under that 1 year manufacturer's warranty.
Do you guys think I will be able to get a replacement device?
Thanks guys!
EDIT: here are the visual descriptions of what i'm talking about.
http://www.youtube.com/watch?v=bYiZbgI3rnk&feature=channel&list=UL
http://www.youtube.com/watch?v=ZxvIj76MkjA&feature=channel&list=UL

jhong91 said:
Hey guys
I gave my cousin my infuse 4g, which was running gtg's Infused latest ROM.
According to her, she was at the mall and she pulled out the phone from her pocket and all she saw was infinite logo bootloop.
At first to me it seemed like a soft brick but it's not recoverable.
When I put the battery in, it goes into infinite samsung logo bootloop.
Three button combo to CWM doesn't work, the download mode jig also does not work.
when i put the download jig in, the yellow downloading mode logo shows up for 2 seconds and then the phone turns off. and the process repeats.
When i put the charging cable in, it infinitely loops the "battery picture", turning off 1 second later everytime and turning back on...
I plan on taking it back to the AT&T Service Shop for a chance at claiming a replacement device.
So here's my question.
I've tried everything I can to get this thing back to a working state, but to no avail.
Does this mean that the engineers at the service center will also not be able to get it back up (meaning that they won't be able to tell that i've voided the warranty)?
I mean, something is seriously wrong with this infuse. it won't even go to download mode.
I bought this device back in July 2011, so I'm still under that 1 year manufacturer's warranty.
Do you guys think I will be able to get a replacement device?
Thanks guys!
EDIT: here are the visual descriptions of what i'm talking about.
http://www.youtube.com/watch?v=bYiZbgI3rnk&feature=channel&list=UL
http://www.youtube.com/watch?v=ZxvIj76MkjA&feature=channel&list=UL
Click to expand...
Click to collapse
jhong91,
It is not often but several other users have reported similar hard power loops that you're describing.
If you go back through the Q/A thread, there are a few with this.
Some users have succeeded in restoring their device via jtag method - by mobiletech or something like that.
Others opted for the replacement and was successful too.
Look through the last 20-40 pages...(garen21, brazcub may have similar situation ) Others have been told that it was due to corrosion of the battery terminal or bad circuit board.

qkster said:
jhong91,
It is not often but several other users have reported similar hard power loops that you're describing.
If you go back through the Q/A thread, there are a few with this.
Some users have succeeded in restoring their device via jtag method - by mobiletech or something like that.
Others opted for the replacement and was successful too.
Look through the last 20-40 pages...(garen21, brazcub may have similar situation ) Others have been told that it was due to corrosion of the battery terminal or bad circuit board.
Click to expand...
Click to collapse
Hello,
thanks for the reply!
if the problem really is, as you may have kindly pointed out, with the circuit board or bad battery terminal, do you think it's unrecoverable even by the AT&T technicians (or mobiletechvideo's jtag service)?
Also, this is my first time dealing with warranties on smartphone.
If they happen to find out that I have voided the warranty by rooting the phone, the worst thing that could happen is not getting a replacement device right? they can't charge me or penalize me right?
Thanks in advance!

You will be OK.
I bricked mine and sent it in, they didn't even realize it was rooted and sent me a new one. Just don't mention it man. Also its better if you take it to a smaller att store, they seem to be a bit cooler then the big corporate stores
Sent from dr0id using Tapatalk 2 beta 5

eZdubzitmk4 said:
You will be OK.
I bricked mine and sent it in, they didn't even realize it was rooted and sent me a new one. Just don't mention it man. Also its better if you take it to a smaller att store, they seem to be a bit cooler then the big corporate stores
Sent from dr0id using Tapatalk 2 beta 5
Click to expand...
Click to collapse
did you go to a retail store? or an official device support center?
thanks!

A retail store
Sent from dr0id using Tapatalk 2 beta 5

eZdubzitmk4 said:
A retail store
Sent from dr0id using Tapatalk 2 beta 5
Click to expand...
Click to collapse
ok, i thought I was supposed to go to device support center..
i guess i'll go to retail first and then device support center if they should redirect me there..
anyways,
thanks man!

Yeah it all depends on the person, most are pretty cool and try to help.
But others just send you away to support
Sent from dr0id using Tapatalk 2 beta 5

[Q] Static from headphone jack (questions about Moto service)

Hi, my headphone jack has always been pick about having things plugged in just right, usually the slightest bit of ling screws it up. Finally today, it just started giving serious static in right side. when music or any sound starts it goes away, but the volume is very low on that side. It only does it when there is power (battery is in), so I think it is a bad connection in there. I have some questions regarding this.
1. How horrible is the Motorola service? they say 5-7 days, but is that really the case (In the U.S.). My warranty is still good, I'll just flash back to stock.
2. will opening the phone up void my warranty? I am somewhat experienced with electronics, so I could probably fix it, but I don't wantt to void the warranty in case it doesn't work.
3. I also have a stuck pixel on my screen that has been there since I got the phone (New). Will they fix that as well even though I can only select one problem on the application form? Should I mention it as well so that they might fix it?
Thank you,
-lkrasner
P.S. Unfortunately this means that I might be unable to do much for a while when I send my phone away. I hope you guys get ICS without me, and I will be waiting to try it out myself.

lkrasner said:
Hi, my headphone jack has always been pick about having things plugged in just right, usually the slightest bit of ling screws it up. Finally today, it just started giving serious static in right side. when music or any sound starts it goes away, but the volume is very low on that side. It only does it when there is power (battery is in), so I think it is a bad connection in there. I have some questions regarding this.
1. How horrible is the Motorola service? they say 5-7 days, but is that really the case (In the U.S.). My warranty is still good, I'll just flash back to stock.
2. will opening the phone up void my warranty? I am somewhat experienced with electronics, so I could probably fix it, but I don't wantt to void the warranty in case it doesn't work.
3. I also have a stuck pixel on my screen that has been there since I got the phone (New). Will they fix that as well even though I can only select one problem on the application form? Should I mention it as well so that they might fix it?
Thank you,
-lkrasner
P.S. Unfortunately this means that I might be unable to do much for a while when I send my phone away. I hope you guys get ICS without me, and I will be waiting to try it out myself.
Click to expand...
Click to collapse
Just do a mis-flash or delete the system partition and take it into a store and tell/show them it does not boot, that you picked it up off the charger and it was like that, and you need a replacement. They will send you a replacement and you have 30 days to return your "broken" phone. I have done this 4 times with my A2s.

jimbridgman said:
Just do a mis-flash or delete the system partition and take it into a store and tell/show them it does not boot, that you picked it up off the charger and it was like that, and you need a replacement. They will send you a replacement and you have 30 days to return your "broken" phone. I have done this 4 times with my A2s.
Click to expand...
Click to collapse
But my AT&T warranty is up?!?! will it still work? I still have my 1 year moto warranty.
Edit: If this does work I owe you something huge, plus I would get my screen problem fixed
EDIT 2: would I be better off just deleting something that would just stop if from booting past the boot logo (big M) so it wouldn't be so obvious that I just killed it with is basically sayins so on the fastboot screen. If so what could I delete that wouldn't prove I had rooted, probably nothing now that I say that.

lkrasner said:
But my AT&T warranty is up?!?! will it still work? I still have my 1 year moto warranty.
Click to expand...
Click to collapse
That is the Moto warranty, AT&T will just help you "file" it since it is done through them anyhow.
Just don't call moto yourself.

jimbridgman said:
That is the Moto warranty, AT&T will just help you "file" it since it is done through them anyhow.
Just don't call moto yourself.
Click to expand...
Click to collapse
sweet, I will try that, what should I do to brick just erase system with fastboot? isn't that really obvious? or are all the employees just stupid. Obviously I need to do something recoverable so that i can get it back if it doesn't work.

lkrasner said:
sweet, I will try that, what should I do to brick just erase system with fastboot? isn't that really obvious? or are all the employees just stupid. Obviously I need to do something recoverable so that i can get it back if it doesn't work.
Click to expand...
Click to collapse
Do anything that will make it either boot loop or stick on the dual core/moto boot screen. Whacking system/boot should do that, and you can still flash it back to stock before you send it back if you really want to.... they are just going to fully refurb it and re-sell it...
The secret is to act dumb, pretend like you know nothing bout flashing and this site... just act like it just went nuts and started this, and it will not boot.
Ask for the advanced replacement.

jimbridgman said:
Do anything that will make it either boot loop or stick on the dual core/moto boot screen. Whacking system/boot should do that, and you can still flash it back to stock before you send it back if you really want to.... they are just going to fully refurb it and re-sell it...
Click to expand...
Click to collapse
OK, and they will not be able to see root then, and if they flash it back to stock it will no longer be rooted, so I should be fine. I opened a service request with Moto earlier, do you think that will be a problem? Should I wait until it expires so they don't get suspicious that I bricked it on purpose.

lkrasner said:
OK, and they will not be able to see root then, and if they flash it back to stock it will no longer be rooted, so I should be fine. I opened a service request with Moto earlier, do you think that will be a problem? Should I wait until it expires so they don't get suspicious that I bricked it on purpose.
Click to expand...
Click to collapse
if it is borked when you take it to the store they can't see that it is rooted cause it won't boot... all they are going to do it call their 1-800 number and help you file a support request... then the person the phone will let you know of the "requirements" and ask if the phone has any visible water damage, yadda yadda...
Then they will send you a new phone and you should get it in 3 or so days and you are supposed to send the old one back in the SAME box... so you will already have flashed the fxz and been using the phone the whole time you waited for the new one to show up... just don't forget to send it back... I did and waited until 25 days later, and I was bugged mercillessly by att...
Just make sure you factory wipe and take out your sim and SDcard, and battery door... they do not send anything but the core of the phone, no batt or batt door or anything.

lkrasner said:
OK, and they will not be able to see root then, and if they flash it back to stock it will no longer be rooted, so I should be fine. I opened a service request with Moto earlier, do you think that will be a problem? Should I wait until it expires so they don't get suspicious that I bricked it on purpose.
Click to expand...
Click to collapse
@jim on playing dumb,hilarious ..i do that when i upgrade my phone.im such an ass when i upgraded to a2 from xperia x10 that i didnt even bother restoring it to stock, i left cm7 on it,custom bootlogo ,said "free xperia team" on boot.i just pretended i didnt know what happend. it was so enjoyable.
service rep - "it appears to be rooted"
My response - "What do you mean rooted? It has roots like a plant?".
@krasner
You worry to much,they cant prove anything.just brick it and youll be fine.u could even play dumb as u crack a smile while doing so and they still really cant do anything to prove u did it and have to exchange it.
Sent from my MB865 using xda premium

worked beautifully! I deleted build.prop and default.prop, so it just went to a black screen after the moto logo. when the guy called the warranty center he said it was "extremely defective and clearly in need of replacement."
After I walked out, I went home, booted into bp tools, taking me to cwm and used adb to push the two files back. The phone already shipped.
However I am thinking of selling it BNIB and getting something else, any ideas what I could get for it

lkrasner said:
worked beautifully! I deleted build.prop and default.prop, so it just went to a black screen after the moto logo. when the guy called the warranty center he said it was "extremely defective and clearly in need of replacement."
After I walked out, I went home, booted into bp tools, taking me to cwm and used adb to push the two files back. The phone already shipped.
However I am thinking of selling it BNIB and getting something else, any ideas what I could get for it
Click to expand...
Click to collapse
Maybe 150. It wont be "NIB" you will not get a box, batt, back cover, etc. With the replacement.
Sent from my SAMSUNG-SGH-I747, running CM9, using xda premium

Nexus 5 randomly shutting down

Rooted (with WugFresh) and running stock. Have switched between Dalvik and ART, problem happens on both. My phone will randomly turn off while I am not using it. Sometimes i just need to hit power and it turns back on, other times i need to plug it in to get it going again. I'm fairly new to Android and Nexus... not sure if this is a hardware or software issue.
I was afraid this was caused by me rooting it, but that doesn't make much sense as I have done the exact same things to my wife's phone and hers is fine. Is there any way I can access logs to see what happened to cause it to shut down?
It seems to be getting worse now, shut down last night (while plugged in) and missed my alarm. Then couldn't get it back on, had to hold volume up+down + power button. I am going to try a wipe to stock and if that doesn't work, i'll RMA it
Any help is appreciated!

You're on the right track flash back to stock and see if you still have a problem. If you do then it's an issue with your device.
Edit, this might help. http://forum.xda-developers.com/showthread.php?p=47156064

Returned everything back to stock and still having the issue... time to RMA?

adil_93 said:
Returned everything back to stock and still having the issue... time to RMA?
Click to expand...
Click to collapse
I would, you don't want your device randomly shutting down
Sent from my Nexus 5 using xda app-developers app

Unfortunatly, I have the same issue with my 32GB white D820 US version, which arrived yesterday here in Germany. Almost all system and user apps keep FCing (but most re) and random hot reboots after kernel panics (mainly oups 80d). It makes the phone unusable. And to be said: When I received the phone yesterday it was factory sealed and I didn't tampered with the phone in any way (though I was just about to do so ). Anyway, the issues started with the very first system boot.
A bug report has been filed in the Android bug tracker andseveral similar discussions are going on in the Google product forums.
I doubt this is a software (ie OS) related bug leading to the kernel panics, looking at last_kmsg and asort and there would be much more issue reports. It looks more like defective RAM.
I'm a professional developer since 10 years and fell in love with Android a few years ago (just to say I know what I'm doing). I did all things possible to troubleshoot. No way.
I spoke to Google's tech support and they recommended to RMA too. Here's the email I received after that call:
Hello Stephan,
Thank you for contacting Google! My name is XXX and I'll be happy to assist in this matter.
If you have already performed the steps we talked about (factory data reset and/or reflashing a factory image on your device 1 or multiple times) and yielded no results, I would advise a replacement device. From our system, however, it doesn't look like you purchased your Nexus 5 from the Google Play Store. Therefore I wouldn't be able to process that device exchange for you.
If your device wasn't purchased from the Google Play and you're looking for warranty repair service, please contact the manufacturer of your device directly.
If you'd like to return a device that wasn't purchased from Google Play for a refund, please contact the retailer from which you purchased the device for more information.
If there is anything further I can assist you with, please feel free to reply directly to this email or visit our help center at
http://support.google.com/googleplay/bin/request.py?contact_type=contact_policy&policy=hardware
Sincerely,
XXX
The Google Team
Click to expand...
Click to collapse
So, if you ordered from Google Play Store, here are the relevant links:
General return, refund and replacement instructions: https://support.google.com/googleplay/answer/2411741?hl=en
Contact form to request an RMA form (for US purchases only!): https://support.google.com/googleplay/contact/c2c_hardware_ordering
List of Google Play hardware support team phone numbers by country: https://support.google.com/googleplay/answer/3053039?hl=en
Otherwise contact your local LG support here https://www.lg.com/
Because I did not purchased mine via Google Play they won't replace mine (as you've read in their mail). But I also spoke to LG already today and they'll replace mine. Gonna send it back tomorrow. (so saaad. won't let it go again... )

[Q] Odd Phone Behavior after flashing H810PR10 (Lost 30GB of memory?)

It would appear that, in my habit of ruining everything, I failed the low effort boot and bricked my new LG G4. Thankfully, I remembered that in this instance you can flash the stock firmware to return to default. Unfortunately, the US firmware wasn't available, but apparently the Puerto Rico one was. I flashed that and got my phone back working just fine, kind of.
First, it doesn't lock normally. Usually, I set it to the 10 minute lock delay, where I just have to swipe unless 10 minutes have passed, then it requires the password. Instead of going to a lock screen, it skips that and just goes right into the phone. It's probably a settings thing, but it's weird.
The worst thing is that I have apparently lost 30GB of storage to "miscellaneous". When I plug it into my computer, it says that I only have 1GB of storage on the whole phone. What is going on here?

Same thing happened to me. Your not gonna be able to flash anything else because of the space on the phone, and can't get the System Image onto a MicroSD card to try and fix it either. I tried both then I just called up AT&T and told them about a problem which I did encounter with the flash making noise when turned on. They replaced the phone
Not sure if there is an actual work around to get the space back but what happened was you flashed it to the wrong partition.

I have the same issue. No one has figured it out yet

TheProblemCauser said:
Same thing happened to me. Your not gonna be able to flash anything else because of the space on the phone, and can't get the System Image onto a MicroSD card to try and fix it either. I tried both then I just called up AT&T and told them about a problem which I did encounter with the flash making noise when turned on. They replaced the phone
Not sure if there is an actual work around to get the space back but what happened was you flashed it to the wrong partition.
Click to expand...
Click to collapse
The problem is that I'm not encountering any issues like that so far. I doubt that they'd replace an issue caused by failed root.

Sorry for the double post, but is there any way that I can create a situation where I could get my phone replaced? I just got it, so it still is under warranty.

Flash the ATT system image back on to it and brick it is about your only option.
Sent from my LG-H810 using Tapatalk

Nynten said:
Sorry for the double post, but is there any way that I can create a situation where I could get my phone replaced? I just got it, so it still is under warranty.
Click to expand...
Click to collapse
Best case scenario would be to call them up and tell them your phone got bricked due to an update. Then let them know that you needed the said phone in a working condition until you can get a replacement.
Or tell them a bull**** problem, normally they send you the replacement then you ship yours out to them. Done this twice already I'm on my 3rd G4

TheProblemCauser said:
Best case scenario would be to call them up and tell them your phone got bricked due to an update. Then let them know that you needed the said phone in a working condition until you can get a replacement.
Or tell them a bull**** problem, normally they send you the replacement then you ship yours out to them. Done this twice already I'm on my 3rd G4
Click to expand...
Click to collapse
Can I just take it to the shop bricked "from an update" and get a new one there or do I have to mail it in?

How do I flash the stock att .Img with a full system data. Sorry of this is a noob question

Nynten said:
Can I just take it to the shop bricked "from an update" and get a new one there or do I have to mail it in?
Click to expand...
Click to collapse
You probably can. Its still under warranty so you should still get it replaced

TheProblemCauser said:
You probably can. Its still under warranty so you should still get it replaced
Click to expand...
Click to collapse
You can take it to a shop, but they will still call customer service and you will have to mail it in still. I paid extra to have a next day replacement.
Was told they don't switch phones in store anymore. Had a few local friends confirm their warranty replacements were done the same way from in store. I'm not sure if that is a national policy, regional, or local. I can say I did like it better when they could switch out in store.

Anybody come up with another solution besides sending the phone back??? I won my phone off a att contest. So I doubt if att will do anything about it. Plus I can't install the stock Img and re soft brick the phone because I don't have anymore space

Question OTA Updates failing with, "partition superReason SUPER: Build-id does not match with the reference"

**Solved posting update in thread.
Purchased S21+ from Samsung online for Verizon Network, every OTA update since purchase results in it failing to the downloading screen with "
partition super Reason SUPER: Build-id does not match with the reference" I have been able to resurrect it successfully by entering the recovery mode and performing a factory reset. But each OTA update push results in the same issue.
Samsung wants me to either send them the phone or take to a repair location for a software refresh as they called it. Problem is nearest repair center is 3+ hours away from me or 5-7 day turn around on the mailed device with no backup phone.
Has anyone else encountered this and does anyone here have a solution to fix this myself? I am comfortable using Odin and flashing roms but not sure if this will fix it.

have you talked to verizon?

Post Nine said:
have you talked to verizon?
Click to expand...
Click to collapse
Yes, Spoke with their Tier 2 support. Tier 2 discussed the issue and implied a change of information for the phone would fix it. They transferred me to Samsung due to the phone being purchased direct from Samsung.

Ok so the problem seems to have been resolved. Here's what I did to fix it.
Downloaded the current firmware I had before the update from Sammobile.com. Using Odin I installed the firmware I was currently on. I had done this before on the last update that failed. But this time I gave it the user data info and did use the Home CSC in an effort to reset everything.
Phone came back online functioning normally with everything wiped. I connected to WiFi and let the first of 2 updates download then run. Success . First OTA that's been successful on the phone. Then went for update #2. Failed, but rebooted this time and gave me an Error 402. Tried again a little later, same WiFi. It redownloaded the update and success again.
So it seems it needs a very very stable internet connection and the full wipe fixed the build id mismatch.
Also before attempting updates highly recommend having all your 2FA accounts either backed up, a second authenticator on another device or turned off. Its a real PITA to get back into all your accounts when your authenticator app gets wiped unexpectedly.
Hope this helps someone else!

CBH60 said:
Hope this helps someone else
Click to expand...
Click to collapse
Thank you!!! I was stuck on this screen all day!
I had restored my S22 Ultra, as a last resort to troubleshoot the shut down/reboot issue I, like many others, have been experiencing. When my phone then updated itself afterward, the install failed and I was stuck. I just happened to find this post of yours, while I was researching some info someone at the Geek Squad gave me, and told me to try it when I got home. The print out he gave me was a word for word copy of your solution! It totally worked, and I am back in. Now to see if the shut down/reboot issue recurs..... I suspect it will, I'm thinking it has something to do with my battery, which I can't remove.

Ardera_Sempre said:
Thank you!!! I was stuck on this screen all day!
I had restored my S22 Ultra, as a last resort to troubleshoot the shut down/reboot issue I, like many others, have been experiencing. When my phone then updated itself afterward, the install failed and I was stuck. I just happened to find this post of yours, while I was researching some info someone at the Geek Squad gave me, and told me to try it when I got home. The print out he gave me was a word for word copy of your solution! It totally worked, and I am back in. Now to see if the shut down/reboot issue recurs..... I suspect it will, I'm thinking it has something to do with my battery, which I can't remove.
Click to expand...
Click to collapse
Hey did you ever get this screen again? And were OTA updates normal after you flashed?
OTA updates keep failing for me on my S22+, either at 25% causing it to go back to the old firmware with an error message, or getting bricked showing that screen. I've tried to reflash and then update and so far only solution is flashing the update through Odin every time. I have had only 2 successful OTA updates since I got this phone in April

AliRAS said:
Hey did you ever get this screen again? And were OTA updates normal after you flashed?
OTA updates keep failing for me on my S22+, either at 25% causing it to go back to the old firmware with an error message, or getting bricked showing that screen. I've tried to reflash and then update and so far only solution is flashing the update through Odin every time. I have had only 2 successful OTA updates since I got this phone in April
Click to expand...
Click to collapse
I did not have any further issues with updates failing, and getting this screen again. I DID have to send my phone back to Samsung twice though for repair, because of the constant rebooting issue. They could NOT repair that issue, so I ended up getting a refund for the phone. Due to their p**s poor customer service (more than a month later I'm still trying to get them to return the charger for the phone, that they said I HAD to send back with the phone for testing), I will (very unhappy) be purchasing an iPhone. Never buying Samsung again.

Ardera_Sempre said:
I did not have any further issues with updates failing, and getting this screen again. I DID have to send my phone back to Samsung twice though for repair, because of the constant rebooting issue. They could NOT repair that issue, so I ended up getting a refund for the phone. Due to their p**s poor customer service (more than a month later I'm still trying to get them to return the charger for the phone, that they said I HAD to send back with the phone for testing), I will (very unhappy) be purchasing an iPhone. Never buying Samsung again.
Click to expand...
Click to collapse
Damn that sucks never heard of them needing the charger as well for tests, that is a bit odd. The reflash seems to have fixed the rebooting issue I had when I first got my S22+ not sure if I should gamble with trying to update again after the last one failed. Might just wait for One UI 5 and do a dirty flash through Odin and if it doesn't give any problems I'll just flash the security updates every so often I guess. Saves me the stress haha.