Alright so I flashed rubiX, but it started going haywire. Volume started flipping balls, then it kept going in and out of honeycomb (when you press home and it zooms out). Also my home and menu button lights were really dim and flickering. So I SBF'd it back to stock, so I was then running a completely stock, new, fresh droid x. I began to root via z4 and since my battery door was off it accidentally came off. Now I m stuck on the motoroala M bootscreen. I can get into bootloader, i can SBF, but even after SBF flashing, nothing. Holding Home+Power button does nothing. Help me out fellows! I shouldn't be rooted at this point since the battery came out during rooting. Ideas? I need my phone for tomorrow, I will be up all night.
Should I take it back to Verizon? I need to know before I get off work. It never rooted, but the z4 root app is on there. Will the void because of that?
LET ME KNOW!
If it doesn't boot they wont be able to tell. I would recommend taking it to Verizon
Thank you sir. I mean it is literally completely stock, bootstrapper and z4 apps are on it, but i sdf'd it 5 or 6 times. Just going to cross my fingers and bring it to verizon
Yes I have gotten my phone to a point like that in the past. I took it to Verizon, and they didn't even ask what happened they just gave me a new one
You sir are a scholarly gentleman. Leaving work now.
Thank you very much. I do try
Isnt it "a gentleman and a scholar"? Lol
Sent from my DROIDX using XDA App
haha I guess. So I will be taking it back to Verizon tomorrow. If they ask if i rooted ill be like wtf is that?
THe sbf should have cleared everything, right?
Yes the sbf should clear everything. And if the employee knows enough to ask about rooting, they are usually sympathetic as they probably do it themselves. So you are all set
Sounds good. Leaving for verizon store right now, ill tell you whats up when i get home
Got it coach! They're overnighting it, will be here monday!
Related
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.
.. after foolishly trying to apply a Metamorph theme that was meant for the Motorola Defy. It was the Gingerbread theme for the Defy that did it. I was rooted and de-crapified of AT&T bloatware and loving life until this happened.
I am coming from A Samsung Captivate and thats why I had the balls to try it in the first place. I know the theme wasn't made for the Bravo but there are alot of themes that aren't meant for the Captivate that work flawlessly.
I saw similar specs in the Bravo and the Defy (processor, screen resolution, Android build, Motoblur, ect..) and took the risk
NOW I HAVE AN ENDLESS BOOTLOOP!!!!
I know we don't have a custom recovery yet, but is there any way I can get this thing running again?
Mine is in the same state!
I tried instilling an app meant for the Motorola Droid that allows custom recoverys, and now I'm also in boot loops. Good news though, a friend of mine works at Motorola and signed me up to receive Motorola prototype phones, (that's how I got the bravo) and when my trial was over a new trial started with 2.2 Bravos, I didn't get on it though. But usually they work on the phone, and after the project starts about 2 to 4 months later the finished product comes out.
I'm thinking that the 2.2 update will be released probably the first month of 2011, just my guess, pretty sure sometime around there though. When it's released then that 2.2 sbf will be released also. Someone will take that in, post it on a website like always, then all you have to do is flash it with RSD. But don't you have warranty? If you do, don't wait like me, turn it in and get it fixed! You see, I can't do that because I have the prototype phone, and that thing has no warranty.
But yea thats 2 options for you,
Good luck!
Thanks. I still have the Captivate so I just started using it again. But the Moto just feels better in the pocket to me tho. I guess I can wait a few weeks to see if the 2.2 rolls out. But the warranty part is a no go for me because I bought the phone off EBAY and I don't have the original store/dealer reciept... At least that's the excuse that AT&T are giving me. Motorola doesn't deal with the Bravoo warranty wise because its AT&T labeled. Anyways, someone here at XDA will discover some kinda breakthrough...
Quick question for you... If you boot into recovery, and do the clear user data/factory reset can your Bravo make it to the Moto Setup screen? Mine can for some reason! But just when I am clicking next to set up the wi-fi connections it starts the whole bootlooping again, until I reboot into recovery and clear user data/factory reset all over again..ect.
jreal said:
Thanks. I still have the Captivate so I just started using it again. But the Moto just feels better in the pocket to me tho. I guess I can wait a few weeks to see if the 2.2 rolls out. But the warranty part is a no go for me because I bought the phone off EBAY and I don't have the original store/dealer reciept... At least that's the excuse that AT&T are giving me. Motorola doesn't deal with the Bravoo warranty wise because its AT&T labeled. Anyways, someone here at XDA will discover some kinda breakthrough...
Quick question for you... If you boot into recovery, and do the clear user data/factory reset can your Bravo make it to the Moto Setup screen? Mine can for some reason! But just when I am clicking next to set up the wi-fi connections it starts the whole bootlooping again, until I reboot into recovery and clear user data/factory reset all over again..ect.
Click to expand...
Click to collapse
How are you getting the wipe/reset options to show in recovery? every time I boot into recovery I just get the little tri-angle and andy. No matter what buttons I push, the options will not show. On my Droid X, you have to push the search button. but those are physical buttons not capacitive like the Bravo.
well, i don't know what i pushed, but the options showed up.
Your smoking crack if you like the bravo over captivate...
Just press the lower right part of the screen when you see the exclamation triangle.
Anyone know if there is a way to change permissions on the framework from recovery?
Did you ever get your Bravo up and running again? I just rooted mine with SuperOneClick v. 1.5.5. The new one v. 1.6.3 kept hanging at "Reading OS Version Properties..." Your initial post sent a chill down my spine.
Yeah, I got it up and running again... by warranty exchange! lol. Luckily I have a few phones to fall back on. Otherwise I would have been stuck for a month because thats how long AT&T makes you wait if your handset wasn't purchased at an official retal store.
I have a brand new one in my possession but I am a "flash freak" and if someone doesn't find a method for us to fully take advantage of this phones hardware then i'm gonna sell it and wait for the Atrix 4G
jreal said:
Yeah, I got it up and running again... by warranty exchange! lol. Luckily I have a few phones to fall back on. Otherwise I would have been stuck for a month because thats how long AT&T makes you wait if your handset wasn't purchased at an official retal store.
I have a brand new one in my possession but I am a "flash freak" and if someone doesn't find a method for us to fully take advantage of this phones hardware then i'm gonna sell it and wait for the Atrix 4G
Click to expand...
Click to collapse
Good to know you got your replacement.
I would like to try flash "defy" firmware, as soon as, bravo sbf file become available.
BTW, knowing how att/moto operate, I would think skip Atrix's 2.2 and straight to Nexus S with 2.3?
I need help before I go to my last resort of taking my phone to Verizon to be replaced. I have rooted my droid 2 and was running and old version of fission 2.1 I think. Tried flashing the new version of fission after wiping data, cache, dalvik, battery status etc. I followed the directions perfectly and when it was done it was stuck on Moto logo. Tried a few things like pulling battery etc and decided I needed to resort to SBF. I have SBFed this phone before with no problems but this time I think I may have pulled the USB cable out at the very end of the SBF process without realizing it. The screen went black and no longer had the transferring info on it so I thought it was done. When I tried to boot it up the screen will flash on for a second or so with no text and then shut off. I tried holding the UP key while booting to get back to SBF again and the screen just shuts off...
Is there ANYTHING else I can try or might work before I take this back to verizon? I really dont want to resort to that and dont want them to think I have been rooted and deny me a new device... PLEASE HELP....
RammiKan said:
I need help before I go to my last resort of taking my phone to Verizon to be replaced. I have rooted my droid 2 and was running and old version of fission 2.1 I think. Tried flashing the new version of fission after wiping data, cache, dalvik, battery status etc. I followed the directions perfectly and when it was done it was stuck on Moto logo. Tried a few things like pulling battery etc and decided I needed to resort to SBF. I have SBFed this phone before with no problems but this time I think I may have pulled the USB cable out at the very end of the SBF process without realizing it. The screen went black and no longer had the transferring info on it so I thought it was done. When I tried to boot it up the screen will flash on for a second or so with no text and then shut off. I tried holding the UP key while booting to get back to SBF again and the screen just shuts off...
Is there ANYTHING else I can try or might work before I take this back to verizon? I really dont want to resort to that and dont want them to think I have been rooted and deny me a new device... PLEASE HELP....
Click to expand...
Click to collapse
Thats really bad, i think at the end SBF flashs the bootloader and the recovery modules and such. i cant think any other ways of recovering, if im wrong, someone please correct me
Ouch... never even heard of that happening. My D2 fell off my desk a few weeks back, while I was in the middle of an sbf, and it was fine afterwards. The sbf failed but I ran rsd lite again and it was good. Guess I got lucky.
Instead of going to the store, you can call to try and get a replacement. I called after the incident above, and told them my micro usb port wasn't working anymore. They overnighted me a replacement with no questions asked...
Sent from my DROID2 using Tapatalk
YOU DONE GOOFED.
No but seriously, this doesn't sound too good. Hopefully someone knows how to get you out of it. Good luck.
Hold down x+power on.
Sent from my Squidlied Droid 2 using Tapatalk Pro
What kind of backup are you running. Can you absolutely rule out a dead battery at this point, I don't know how long you've been messing with it. I've heard of some d2 users using charge only instead of pcmode. What mode were you in. What does it do when you plug it in to a wall charger. Sorry if this is redundant just trying to get a good feel for your problem and rule a few things out till maybe somebody more of a help than me comes along.
Sent from my Squidlied Droid 2 using Tapatalk Pro
lizard1 said:
What kind of backup are you running. Can you absolutely rule out a dead battery at this point, I don't know how long you've been messing with it. I've heard of some d2 users using charge only instead of pcmode. What mode were you in. What does it do when you plug it in to a wall charger. Sorry if this is redundant just trying to get a good feel for your problem and rule a few things out till maybe somebody more of a help than me comes along.
Sent from my Squidlied Droid 2 using Tapatalk Pro
Click to expand...
Click to collapse
You are a genius. My battery must have died in the middle of the SBF. I swapped out the battery with a charged one and it booted to the bootloader. The SBF said that it was corrupt but I plugged it back in and ran it again and it worked. Thanks for saving my droid!
Even a blind squirrel finds a nut every now and then!
Glad I could help out. Best of luck with the phone.
Sent from my Squidlied Droid 2 using Tapatalk Pro
I have just switched over to verizon from AT&T a couple of days ago. It was an impulse decision as I was only in the Verizon store with my girlfriend to get a her a new phone. I was showing the sales guy my pimped out Samsung Captivate and explaining to him him how easily these things can be manipulated and how much I loved my Cappy. Thats the last thing I remember. I woke up to find I had switched my service (3 lines) over to Verizon and I was now the owner of a Droid X.
I loved my Captivate and had no thoughts of ever switching but they had a promotion going on that blew my AT&T plan out of the water so financially it was a good decision. But I am beginning to wonder if I haven't made a mistake.
Out of the box, the DX is rebooting pretty often. I had planned on getting on here when I got home to find the latest and greatest ROM anyway so I didn't worry about it too much.
I am currently running Liberty 1.0 as my first flash. That is of course after flashing .340 which I read may or may not fix the rebooting issue. I am liking the ROM but the random reboots still persist. Its beginning to get too much to bare as I have yet to have one phone conversation that isn't interrupted by the phone powering down by itself.
I have searched for any word of a fix for this but I haven't found any definitive answers other than to do a factory reset. I have done that several times, as well as reflashing .340 and Liberty to no avail.
Before I take 3 phones back to Verizon and crawl back to AT&T and beg for forgiveness does anyone have a definitive solution for this?
Its worth mentioning that I bought my daughter a DX as well to replace her Cappy (she is NOT happy BTW), and it does the same thing. It is still stock out of the box.
Thanks in advance for any replies.
I have a Dx and haven't had this reboot issue, however, my sister traded in her iPhone for an x on my advice and now she's having the same issue you are. I was going to have her flash to liberty and do a system restore but obviously that hasn't worked for you. Hopefully someone will have an answer to this problem
Sent from my DROIDX using XDA App
Send the phones back to Verizon, that is not normal.
In my opinion, not to say you don't know what you are doing which I am sure you are, I know you are well aware of the risks of flashing roms.
I hear more people having issues with Droid Xs that have been re-ROMed, flashed, themed, etc, then I do people with stock DXs that are rooted and cleaned up of bloat.
While my DX might not be clean out the box, it's still in prestine shape, rooted and even flashed to Cricket. I have never had a single issue with it unless I am bricking it or messing with it myself.
A lot of times, people mistake the phone as the issue. These were $600 phones when released, still are (give and take a few bucks lol). I doubt the issue is hardware. Send it back to VZW or try the Full SBF 320 using RSD Lite. It's been the talk of the town.
Could be that there's a bad batch of DXs going around that have just been released? None the less, VZW can get you replacement DXs over night practially.
Sbf to stock and reflash liberty. Or take it back a get a new phone.
Sent from my DROIDX using XDA App
Ben's said:
In my opinion, not to say you don't know what you are doing which I am sure you are, I know you are well aware of the risks of flashing roms.
I hear more people having issues with Droid Xs that have been re-ROMed, flashed, themed, etc, then I do people with stock DXs that are rooted and cleaned up of bloat.
While my DX might not be clean out the box, it's still in prestine shape, rooted and even flashed to Cricket. I have never had a single issue with it unless I am bricking it or messing with it myself.
A lot of times, people mistake the phone as the issue. These were $600 phones when released, still are (give and take a few bucks lol). I doubt the issue is hardware. Send it back to VZW or try the Full SBF 320 using RSD Lite. It's been the talk of the town.
Could be that there's a bad batch of DXs going around that have just been released? None the less, VZW can get you replacement DXs over night practially.
Click to expand...
Click to collapse
Ben you are right about people messing up phones by flashing. But generally taking them back to stock will fix any issues that have risen from tinkering.
My issue is that mine did it out of the box. My daughters did as well.
Funny thing is just this morning I updated my daughters with the .340 update and it seems to have stopped. Its been quiet now for about the last 30 minutes. I reflashed .340 on mine at the same time and it has rebooted about 4 times while I type this message. Maybe my daughters is fixed, but mine is definitely not right.
Thanks for the comments.
My sisters phone is also doing this bone stock. It doesn't always reboot sometimes it locks up and she has to pull the battery. She's taken it into the Verizon store and they reset it to stock (not sure exactly what they did). That didn't fix it so she took it back to exchange it and they told her " that's normal, sometimes you have to pull the battery." So they wouldn't exchange it.
Sent from my DROIDX using XDA App
Sadly this is has been a small issue with the DX, it's been posted many times. Mine did it when I first got it back in August and at first I was blaming Handcent on the reboots. Then for some reason it just stopped and I have never seen it reboot on it's own. Was it the update to 2.2 or removing Handcent? I've reinstall Handcent since so I honestly I don't know. Side note I still blame Handcent on the phones lag because when I uninstall it the screen redraws and the lag goes away.
Anyway there is a great big long thread on this at the Moto DX forums and Matt's (forum admin) advice was to return the phone for a new one. I would arm myself with a printed copy of the thread in case Verizon wants to throw a fit.
For the record I just dig this phone. I'm stock, rooted with just bloat frozen. It's been a great phone after the teething problems were solved.
fasthair
boot phone, screen is on, hit power button or just let screen go off and then it won't come back on with the power button, phone is working, everything is working but screen won't come back on, on froyo it works fine, on gingerbread, won't work, this is wifes phone completely stock.
I odined to stock froyo, works fine, did the update on the phone, then it doesn't work, tried the rooted ei22 on here, odined it and screen won't come back on. has anyone else had this problem?
i put her back to froyo for the time being, but really need to fix this for her.
Did u try changing the cpu settings to were it won't go into 100
Sent from my SPH-D700 using XDA App
its the wifes phone, its completely stock, no root, nothing. was working fine for the past month or so with the gingerbread update from samsung/sprint, now won't work with ei22. i'd like to just take it back to sprint and say fix it. but i don't know if its hardware or software, can't understand how it would be hardware if its working with froyo, but doesn't make sense that it could be software since it works on everyone elses phone.
Its more than likely a bad update id say take to sprint after you odin back to stock and install the update in front of them and show them the screen won't come on they will more than likely help you and if they can't fix it they'll give you a new phone free since its their fault.
Sent from my OG Epic
Even with phone out of warranty? And do I tell them I odined back after it happened the first time?
I wouldn't tell them that you've odined back.. When I went in to get my phone fixed I just acted dumb. Tell them you just updated it, and the screen won't turn back on..
Not sure about the out of warranty bit though. I have insurance on mine
But all phones were updated a month ago or so, so i'm not sure playing dumb would work
Just take it in on gb and tell them you decided to update that day and that's what happend
Sent from my SPH-D700 using XDA App
i know, but my point is, since the update went out like a month ago, doesnt it force you at some point to update? wouldn't she have had to update already? We got the phones right when they came out and mine has been rooted since day 2, so I really don't know. just don't want to go look like a moron.
robl45 said:
i know, but my point is, since the update went out like a month ago, doesnt it force you at some point to update? wouldn't she have had to update already? We got the phones right when they came out and mine has been rooted since day 2, so I really don't know. just don't want to go look like a moron.
Click to expand...
Click to collapse
No they'll believe you if you just recently "decided" to update. Its an error on their part and are forced to fix it or replace it.
Sent from my OG Epic
took it back today, they wanted to charge me 37.10 to warranty the phone. I asked if we could get sprint to waive it as it was their software update that botched the phone. The guy said he would do it since he is in a good mood. but really I left feeling that sprint might as well close up shop, everything is all about the insurance, insurance insurance. why would I need insurance to cover them bricking my wifes phone??
funny thing is, it was working on gingerbread just fine for a month or so until it didn't. now I just odined the phone back to stock froyo and its working fine again until she gets the new phone.