Database Users

brick?

i was running fission rc1 on my d2g, used frm to download stock d2g deodexed blah blsh, flashed it, stuck on motorola m screen. cant get it to boot to bootstrap recovery for ****. only regular recovery...i could cry
edit: omg im gonna throw up. please tell me theres something i can do.
EDIT: ok...so if it is bricked and i have the $1.99 or $2.99 insurance, whatever....can i get it replaced...and if not, what if hypothetically speaking...it was smashed by a car...could i then get it replaced?

I am no expert, but lets try this, start the phone and as soon as the M appears, immediately pull the battery, and the put back in and start the phone. Lets see if the phone goes into ClockworkMod, and if it does, you can do a restore. Let me know how you make out.
MICP1480

no luck dude. thanks tho
EDIT: just got off the phone with verizon, theyre sending me a new one. wasnt hard at all, i played dumb and acted like bootloader mode was a whole new world to me, she had me wipe the data and reboot, of course i had already done that to no avail so of course it didnt work this time either, she put me on hold and talked to a tech and then came back and said they'd send out a new one.

botnryan said:
no luck dude. thanks tho
EDIT: just got off the phone with verizon, theyre sending me a new one. wasnt hard at all, i played dumb and acted like bootloader mode was a whole new world to me, she had me wipe the data and reboot, of course i had already done that to no avail so of course it didnt work this time either, she put me on hold and talked to a tech and then came back and said they'd send out a new one.
Click to expand...
Click to collapse
They will check your phone to make sure there is no ROM's and that it is not rooted as that voids the warranty.

This just means moto needs to release the sbf for the D2G so we can fix them instead of moto/verizon getting a bunch of returned devices.
Sent from my DROID2 using XDA App

miketoasty said:
They will check your phone to make sure there is no ROM's and that it is not rooted as that voids the warranty.
Click to expand...
Click to collapse
really? and how will they know if its all messed up and wont even boot? plus i did a data and cache wipe of the phone thru the regular recovery, will that not kinda wipe away anything incriminating? Not to mention the last rom i flashed was the stock d2g rom, just deodexed and such

When you flash a custom ROM or root the phone, evidences remain in /system which survives data wipe.
It is another question how would they see that if phone is not booting.
If you sent it in already and you do not receive a nasty 600 dollar invoice in the following days/billing cycle stating you have voided the warranty, then they really do not check.
I guess all they do is to flash the oh-so-desired-by-everyone stock SBF and sell it as refurb or give it as replacement phone.

leobg said:
When you flash a custom ROM or root the phone, evidences remain in /system which survives data wipe.
It is another question how would they see that if phone is not booting.
If you sent it in already and you do not receive a nasty 600 dollar invoice in the following days/billing cycle stating you have voided the warranty, then they really do not check.
I guess all they do is to flash the oh-so-desired-by-everyone stock SBF and sell it as refurb or give it as replacement phone.
Click to expand...
Click to collapse
i havent sent it in yet as ill be recieving the replacement tomorrow...any ideas on how to prevent this? could a good strong magnet wipe the memory completely?

botnryan said:
i havent sent it in yet as ill be recieving the replacement tomorrow...any ideas on how to prevent this? could a good strong magnet wipe the memory completely?
Click to expand...
Click to collapse
without the sbf to get back in there isn't really much you can do. The stuff is on there and you don't have a way to get back in.
try to get into recovery by:
pulling battery (or powering down phone)
while completely off plug in to wall via charging cable
turn on phone while connected to power (if you get the battery screen press power again)
you should hopefully be in recovery (not sure if this method works on D2 G but it does wonders for the D2 but it's worth a try.)
unless you really flashed crazy and messed up recovery theoretically bootstrap should be there unless completely wiped it.

newk8600 said:
without the sbf to get back in there isn't really much you can do. The stuff is on there and you don't have a way to get back in.
try to get into recovery by:
pulling battery (or powering down phone)
while completely off plug in to wall via charging cable
turn on phone while connected to power (if you get the battery screen press power again)
you should hopefully be in recovery (not sure if this method works on D2 G but it does wonders for the D2 but it's worth a try.)
unless you really flashed crazy and messed up recovery theoretically bootstrap should be there unless completely wiped it.
Click to expand...
Click to collapse
dude i tried that with both usb and wall charger, no luck either way, i flashed stock d2g deodexed blah blah rom over fission rc1 and this happend. totally blows my mind. got my replacement today, super glad to be back away from the eris lol

botnryan said:
dude i tried that with both usb and wall charger, no luck either way, i flashed stock d2g deodexed blah blah rom over fission rc1 and this happend. totally blows my mind. got my replacement today, super glad to be back away from the eris lol
Click to expand...
Click to collapse
Just checking I didn't see you tried that specifically glad you got your replacement now you know to be very careful as the sbf isn't out yet.

sorry if that last post came off harsh lol, didnt mean it to, read it again and was like geez dude chill (at myself). So im really hoping they dont charge my ass for this, but i dont see how theyre going to know. if you flash an sbf, does it unroot it? Because, if thats what they do to phones like mine, then they wont know i had it rooted/rom'd right?

botnryan said:
sorry if that last post came off harsh lol, didnt mean it to, read it again and was like geez dude chill (at myself). So im really hoping they dont charge my ass for this, but i dont see how theyre going to know. if you flash an sbf, does it unroot it? Because, if thats what they do to phones like mine, then they wont know i had it rooted/rom'd right?
Click to expand...
Click to collapse
Yeah SBF put's it back to stock from factory software. Unless they have another way of getting in and see what was in there they won't know much unless after they SBF they can pull the residual data in data or cache but I don't think they will go to that extent only if D2 G's start dropping like flies.
If they would just release the SBF for us we could have fixed your phone in 15 minutes and it wouldn't have cost them anything at all.

newk8600 said:
Yeah SBF put's it back to stock from factory software. Unless they have another way of getting in and see what was in there they won't know much unless after they SBF they can pull the residual data in data or cache but I don't think they will go to that extent only if D2 G's start dropping like flies.
If they would just release the SBF for us we could have fixed your phone in 15 minutes and it wouldn't have cost them anything at all.
Click to expand...
Click to collapse
alrights, thanks man. i feel they probably wont be able to find anything out but im still going to use up my 10 day period i have to send the phone in just in case the sbf is magically released in that time period.

[Q] If i unlock then relock, can Moto tell that i unlocked?

I know this has been asked before but i just want to be sure, i just got the xoom and i want to know if i can send it in for repairs. I just want to kno if its like the ipod's/phones where there is a physical feature that is broken, so i can relock and my warranty will be valid.

Moto doesn't care.

K thanks
Sent from my HTC Thunderbolt running Das BAMF v1.6.1 remix.

Elysian893 said:
Moto doesn't care.
Click to expand...
Click to collapse
Wait, what makes you say that? Do you know something we don't know? As far as I've heard, they've been very specific to say that they will not support devices that have been hacked.

slack04 said:
As far as I've heard, they've been very specific to say that they will not support devices that have been hacked.
Click to expand...
Click to collapse
... yet they sold us a Google-Experience device with an unlocked bootloader.
You can't break anything seriously with software, which means any potential problems we'd have are either physical, user-abuse, or hardware defects. If you send it in and they determine that the problem is SW, they'll probably just wipe it back to stock and send it to you.

Fact does remain, however, that when you unlock that device you have to acknowledge you are voiding your warranty if you proceed. I'd like to think they would be reasonable - but at the same time, you have agreed to kiss off your warranty when you unlock.

That is why I am hesitant to unlock, on all of my Android Phones I have rooted because I know there is no hardware function that can tell it has been "Hacked" like on the iPhone. The Xoom I am unsure about because nobody has a definitive answer yet. My Eris broke 3 times while rooted and I unrooted each time and sent it in for a exchange. I just want the above situation to be equivilent to when/if (Hopefully not) my xoom has a hardware failure.

Jiv3turk3y89 said:
That is why I am hesitant to unlock, on all of my Android Phones I have rooted because I know there is no hardware function that can tell it has been "Hacked" like on the iPhone. The Xoom I am unsure about because nobody has a definitive answer yet. My Eris broke 3 times while rooted and I unrooted each time and sent it in for a exchange. I just want the above situation to be equivilent to when/if (Hopefully not) my xoom has a hardware failure.
Click to expand...
Click to collapse
Moto has released their newest UPDATE for the xoom, on their website they included instructions and software to "RE-LOCK"/"UNROOT" your device before doing update. they dont care as long as you "relock"before sending the device to them to fix or reflash stock after you BUNKED a mod or etc...i dont recommend doing a theme flash, i did a few of them and had to go back to stock after every theme i tried, they did nothing but force close and i almost wasnt able to get back into CWM because the device wasnt recognized in adb...unlocking and rooting does nothing bad to your XOOM, best thing going for it, at least til there are some ROMS that couldnt get here any sooner...just a heads up

LNKNPRKFN said:
Moto has released their newest UPDATE for the xoom, on their website they included instructions and software to "RE-LOCK"/"UNROOT" your device before doing update. they dont care as long as you "relock"before sending the device to them to fix or reflash stock after you BUNKED a mod or etc...i dont recommend doing a theme flash, i did a few of them and had to go back to stock after every theme i tried, they did nothing but force close and i almost wasnt able to get back into CWM because the device wasnt recognized in adb...unlocking and rooting does nothing bad to your XOOM, best thing going for it, at least til there are some ROMS that couldnt get here any sooner...just a heads up
Click to expand...
Click to collapse
Thanks everyone! I think im going to unlock it when I get the chance, the SD card slot is a BIG thing that I could use, also I want it overclocked just a lil (1.25 Ghz per core) so it doesn't lag much on the home screen. Also im not going to be flashing roms and stuff mainly kernels. This device is going to be used as a family computer so i can't mess with it as much as I can with my Phone . Anyways thanks guys!

What is considered a defect on this phone?

I still have my phone under the manufacturer warranty and it has been acting wonky lately. I want a new vibrant and I am just wondering what is considered a defect? Im thinking about flashing back to stock and saying my GPS doesn't work, and also I have light leakage from LED buttons. Thanks.

what is "wonky" about it?
Maybe we can fix it... I don't like the idea of helping get a new phone, just for the sake of getting a new phone.
This (and other reasons) are why phone costs so dang much.

Smh...
Sent from my ADR6300 using XDA App

s15274n said:
what is "wonky" about it?
Maybe we can fix it... I don't like the idea of helping get a new phone, just for the sake of getting a new phone.
This (and other reasons) are why phone costs so dang much.
Click to expand...
Click to collapse
Exactly, if it is indeed defective then by all means get an exchange. But if it just running slow then it can prolly get fixed with a flash. I process so many warranty exchanges that in all honesty there was nothing physically wrong with it. A simply odin to stock fixes them.
Sent from my SGH-T959 using XDA App

Marvlet said:
Exactly, if it is indeed defective then by all means get an exchange. But if it just running slow then it can prolly get fixed with a flash. I process so many warranty exchanges that in all honesty there was nothing physically wrong with it. A simply odin to stock fixes them.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
And if you are willing to try, check my signature for going back to stock... files and a guide for you.

Random restarts, GPS still doesnt work at all, light leakage on buttons and screen. Ive tried numerous ROMs and I am still having issues with GPS. Ive went to stock and while it fixed my problems with restarts, stock was just to laggy so I went back to custom ROMs, GPS still doesn't work.
I am also having signal problems. Me and my friend bought a vibrant the same day and we have tested in the same room that his gets better reception. In a room where he has H, I am only on Edge. This isn't a problem with the ROM because we are both running Bionix.
If there is any way to fix my GPS/Signal issues then by all means tell me and I wont send my phone in for a replacement.
EDIT: Thank you guys for the help. Could ROMs effect signal/GPS? Like I said above when I compared with my friends phone under the same conditions (same room, same ROM) i was only on Edge and he had H. I've tried Trigger, MIUI, and CM7 and still don't have 3G or H in places my friend does.
Se7enDayz said:
Smh...
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Thank you for the input I'm glad you gave me some good information as to fixing my phone/getting a replacement.

ROMs COULD be a reason since they have different modems... but if you guys were on the same rom and didnt change the modem, then no....
I have best luck on KB1.
I would ODIN to JFD, root, Flash Trigger and see how your signal/gps goes... if not great, flash the KB1 modem over it (dev section) and see if any better.
If you look in my tips/tricks (first link in signature) there is a fix I do for GPS. Sometimes on a new ROM when it DOES NOT work, I have to do that to make it work. Other roms, it works right after flashing... no real rhyme or reason.
If you want a new phone, i am certain you could get one based off what you said already..... but I would not be surprised if you could make it 100% right.

s15274n said:
If you want a new phone, i am certain you could get one based off what you said already..... but I would not be surprised if you could make it 100% right.
Click to expand...
Click to collapse
not to mention the refurb you get could have the same problems or worse.

Refurbished is what you will get, there are no more "new" Vibrants.
Sent from my CM7 Powered Vibrant

For gps try this http://www.intomobile.com/2010/07/21/t-mobile-samsung-vibrant-galaxy-s-gps-issues-fix-tutorial/
I am using stock KB5, it helped me get a lock in 15-30 sec.
edit: I did mess with gps.conf from hd2 forum, dont know if that helped too.

Sbf'd 2.3.4 and now stuck on bootloop

Need to take my phone back to att for a faculty gps and after reading around here i found out it might hard brick it.
Well i didn't hard brick, but i am stuck on boot loop.
Any help?
It goes to the att boot animation, then goes back to the Motorola logo one...
I used a File called 2.3.4_pudding_preroot or something like that.
I had a similar problem once and re flashing fixed it, which ill try when i get home from errands, but i wanted to post and ask for suggestions i til I get back to try it.
Im gonna stop at an att store and see if they can give me a replenished one, but i doubt that...
There is probably a thread related to this somewhere too, but im posting from Tapatalk so its hard to look around. Lol
Thanks in advance!
Sent from my Xoom using Tapatalk
Sent from my Xoom using Tapatalk

At&t will refer you to Motorola ...I had the same problem with my ATRIX gps too and actually hard bricked it in the processes if returning to stock just tell them when updating the rom your phone died ...they will overall send you a new one
Sent from my MB860 using XDA App

yokozuna82 said:
At&t will refer you to Motorola ...I had the same problem with my ATRIX gps too and actually hard bricked it in the processes if returning to stock just tell them when updating the rom your phone died ...they will overall send you a new one
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Is there a number for motorola warranty you have? How do I start the process?
Sent from my Xoom using Tapatalk

Just left the att store. There is apparently a DSC (device support center) about 10 miles from here and they'll just replace the phone on the spot. Hopefully they won't say anything about the 'unlocked' text.
Let you know what happens
Sent from my Xoom using Tapatalk

In recovery mode wipe the cache then factory reset. Don't restart the system. Pull the battery out and place it back without touching the power button, it might happen when putting the battery cover back on.
Reflash the desire. sbf file as you normally do with the latest version of MotoHelper and RsdLite program that you can find. Make sure your battery have enough charge for next flash attempt.
The above instructions are what I would do in your circumstances. Please make sure the. sbf is exactly same version as what is on your handset. If the flashing .sbf has higher version then it will be safe.
Good Luck!

CSharpHeaven said:
In recovery mode wipe the cache then factory reset. Don't restart the system. Pull the battery out and place it back without touching the power button, it might happen when putting the battery cover back on.
Reflash the desire. sbf file as you normally do with the latest version of MotoHelper and RsdLite program that you can find. Make sure your battery have enough charge for next flash attempt.
The above instructions are what I would do in your circumstances. Please make sure the. sbf is exactly same version as what is on your handset. If the flashing .sbf has higher version then it will be safe.
Good Luck!
Click to expand...
Click to collapse
Ok got it running at the att store and was able to download GPS status and i compared the performance to the xoom's GPS status. He saw how the GPS just couldn't lock on so he said hell swap it out for me. Waiting on the replacement now
Sent from my Xoom using Tapatalk

Got a new phone. GPS works. Gonna have to sbf again for Unlock and pre root now. Hopefully this one will work out. Lol...
Is there a way to Unlock and root without sbf??
Sent from my Xoom using Tapatalk

razorseal said:
Ok got it running at the att store and was able to download GPS status and i compared the performance to the xoom's GPS status. He saw how the GPS just couldn't lock on so he said hell swap it out for me. Waiting on the replacement now
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Good to hear that. Please make sure you will read the following thread once you got your new Atrix. I get GPS lock in the UK within seconds. I even managed to get GPS lock indoors. A must for every handset really.
http://forum.xda-developers.com/showthread.php?t=1239713

Did I just Hard Brick my phone?

I've had my HTC 10 about a month. I was running NuSense Marshmallow by Santod040 and I had run the "NoRedText_aboot_firmware zip" to get rid ot the red text. Still, things were running well.
I then updated to the Nougat version of NuSense and the firmware and again things were running well. But the red text was back so I decided to get rid of the red text again. That is where things went wrong.
I didn't realize that there was a "new version" of the "NoRedText_aboot_firmware zip" and I tried to flash the same one.
I got an error message about it being the version prior to the update then the phone shut down. Now it wont power up.
Am I totally screwed? Is there a way to fix this? HELP... :crying:

Are you S-Off? Does your computer see it?
@dottat

acbrocksit said:
I've had my HTC 10 about a month. I was running NuSense Marshmallow by Santod040 and I had run the "NoRedText_aboot_firmware zip" to get rid ot the red text. Still, things were running well.
I then updated to the Nougat version of NuSense and the firmware and again things were running well. But the red text was back so I decided to get rid of the red text again. That is where things went wrong.
I didn't realize that there was a "new version" of the "NoRedText_aboot_firmware zip" and I tried to flash the same one.
I got an error message about it being the version prior to the update then the phone shut down. Now it wont power up.
Am I totally screwed? Is there a way to fix this? HELP... :crying:
Click to expand...
Click to collapse
Try charging with oem stock charger and cable overnight.
If it starts to take a charge, prepare a blank SDcard with
2PS6IMG_PERFUME_WL_M60_SENSE80GP_VZW_VERIZON_WWE_1.85.605.8_Radio_1.0.C010141xxxx.zip or similar. Rename it 2PS6IMG.zip with only one .zip at end. Try and boot with volume down and power.
With any luck, you'll get enough charge on it to allow you to do this software install.

Hard Brick
I did ask Santod and he said it is hard bricked. I flashed the wrong aboot image and now the phone does nothing, no power, no response from any combination of button presses, the computer does not see it. I don't know of anything else that might work.
I'm going to try to see if HTC can fix it, if not then I may use it for parts because the phone looks great. So I may try to get a beat up phone with a busted screen and swap out the guts.

Pretty sure this is what I've been talking about folks.
Stop messing with custom aboots.
Sent from my HTC6545LVW using Tapatalk

Bricked / aboot
dottat said:
Pretty sure this is what I've been talking about folks.
Stop messing with custom aboots.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
Yeah, I read your info and warning about it after the fact.

acbrocksit said:
Yeah, I read your info and warning about it after the fact.
Click to expand...
Click to collapse
Yep...Moreso posting for anyone who sees this as further warning.
Sent from my HTC6545LVW using Tapatalk

I did the same thing trying to downgrade my firmware. Same exact thing happened. So I got it replaced by Verizon with the warranty, and they accepted it, I just said that I was trying to update it and that it won't turn on now. They haven't noticed that I did it, and I doubt they'll be able to get it to boot without flashing complete stock.

Spinkness said:
I did the same thing trying to downgrade my firmware. Same exact thing happened. So I got it replaced by Verizon with the warranty, and they accepted it, I just said that I was trying to update it and that it won't turn on now. They haven't noticed that I did it, and I doubt they'll be able to get it to boot without flashing complete stock.
Click to expand...
Click to collapse
So Verizon accepted your bricked phone? No issues?
Sent from my HTC6525LVW using Tapatalk

I sent mine to HTC to see what they would charge me (repair center in USA). I didn't say what happened, just that it wouldn't turn on. I don't think that they looked very close at it. They just sent me a refurbished phone, no charge.
But I won't mess with the red text again. It's really not worth the risk.

acbrocksit said:
I sent mine to HTC to see what they would charge me (repair center in USA). I didn't say what happened, just that it wouldn't turn on. I don't think that they looked very close at it. They just sent me a refurbished phone, no charge.
But I won't mess with the red text again. It's really not worth the risk.
Click to expand...
Click to collapse
They didn't even ask why Verizon wouldn't warranty it?
Sent from my m8wl using Tapatalk

Evocm7 said:
So Verizon accepted your bricked phone? No issues?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Sorry about the delayed response!!!
Yes they accepted it with no issues. Been a few months now and still nothing bad from them. The people at Verizon don't even have the knowledge to revive a hard bricked phone. At least not the people I've ever been able to speak to. But either way, it's not worth the hassle for them. They'll just part it, toss it, or send it back to HTC, where they will either part it or toss it. So yeah, no worries about sending Verizon a rooted/s-offed/bootloader unlocked phone. I've done it more times than I can count, and they've never found out.

Spinkness said:
Sorry about the delayed response!!!
Yes they accepted it with no issues. Been a few months now and still nothing bad from them. The people at Verizon don't even have the knowledge to revive a hard bricked phone. At least not the people I've ever been able to speak to. But either way, it's not worth the hassle for them. They'll just part it, toss it, or send it back to HTC, where they will either part it or toss it. So yeah, no worries about sending Verizon a rooted/s-offed/bootloader unlocked phone. I've done it more times than I can count, and they've never found out.
Click to expand...
Click to collapse
No problem. I called Verizon and even though it was dead, they were still able to communicate with the phone while I was talking to them on another phone. The power led was flashing red and then she said the phone wasn't under warranty because there was custom software. I ended up sending it to HTC where they sent me a refurb with a bad mic then the second one I have now is fine. So after a month and $40 worth of shipping charges, I have a working 10 again. I honestly don't think HTC cares about rooted phones and the time it would take to diagnose what actually happened in our down grade brick wouldn't be worth it for them.
Sent from my HTC6545LVW using Tapatalk

If it's under warranty, make a claim. Verizon will tell you to ship it back to another location where all they do is refurbish the phones for subsequent resale. You will likely get a replacement refurb. The refurbisher has absolutely no clue what you have done; they handle these things in bulk and I have not once ever heard of a phone under warranty being "refused" because an end user did something stupid. Which, as @dottat says, is what flashing an edited aboot to get rid of the red text is, by the way. Stupid.
I *like* the red-text, frankly. It reminds me whether I'm running pure stock boot and recovery or not while I'm flashing updates, etc.