Good day everyone,
My problem started a month and a half ago, but in a different form. The battery of my Motorola Razr (Non-US) went too low, and it only showed the bright white light whenever I tried to charge it. This is an error code that means that the battery ran so low that it is now in a protective mode that you can only get it out with higher amounts of amperage, using a cable that I don't have myself. I returned it to the store, they sent it to the motorola factory, and I got it back yesterday. Now, it might be important for me to note that I live in the Netherlands; the nearest Motorola factory was the one in Germany. It took a solid 5 weeks for me to get my phone back.
Right, so today/yesterday I tried to turn on my phone, excited to have it back after such a long time. It got stuck in a bootloop. All it does is show the red/white M, with dual core below it. This is the first screen you normally see when you boot the phone. After a second or 5, the screen goes black, only to be replaced by the red/white M, this time without the dual core text. After a while ripples start to show around the M, but without vibrations. The menu buttons also do not light up. Normally the same happens, but it vibrates rather violently and the menu buttons do light it; it means that the phone is booting the firmware.
The phone keeps this up for a few minutes, after which it starts all over again, from the red/white M with the dual core text. It does does indefinitely, until the battery runs out. It doesn't shut down in between, so this takes quite a while. I tried forcing it to reboot with the volume down + power button (which is a hardware reboot), but that just makes the cycle start over again. Very, very rarely (usually after looping for about an hour), the phone DOES go on. However, it soon crashes again, being on between 10 seconds and 5 minutes.
Now here is what I think happened. Before I sent the phone to the factory, I was running an old version of android, still in Gingerbread. I don't know exactly what firmware it used, but it was rather old, maybe half a year at least. However, now that I have it back, I appear to have been updated to ICS 4.0.4. The firmware running on the phone is also new (obviously), version 672.180.41.XT910.NonEFIGSRetail.en.EU (EU for Europe obviously, and NonEFIGS for non English, French, Italian, German and Spanish) as I live in the Netherlands. Now what I figure has happened is that the factory tried to flash my phone to the new firmware after they had fixed the issue, and the update didn't take.
Now, I could obviously return the phone to the store again and have them repair it, but that will take another month. Also, the store is very disappointing to say the least; they will not give me a replacement phone in the meantime, which is very bothersome. So I'd rather try and solve the problem myself.
However, I don't know how to flash 672.180.41.XT910.NonEFIGSRetail.en.EU again. All the instructions or guides that I have found so far only refer to the American version of the phone, or require me to be able to access the phone (turn it on). I can however access the boot menu with volume + volume - power held together, which lets me access the AP Fastboot menu.
Could anyone give me instructions what to do from there? I already did a factory reset, which did nothing to fix the situation.
I did find this link
http://forum.xda-developers.com/showthread.php?t=1837971
But I'm not sure how to proceed with that.
Note: If I'm on the wrong path with trying to fix it all, please do say so! By no means do I want to screw up the situation any further, as I could still have it repaired for free, it just takes a long time and I'd rather not.
Note2: If I am missing any crucial info, please let me know too!
Edit/Delete Message
Alright, so maybe I should modify the title.. I tried using the method in
http://forum.xda-developers.com/showthread.php?t=1837971
But I'm afraid that only made the situation worse. My phone now automatically boots into AP Fastboot, giving the message that the flash has failed.
Now I understand that I should be able to just re-flash it, but I would be very thankful if someone could point me to the right files/procedure, as almost everything I can find is for the US version, and I'd rather keep the EU version with my language pack and all.
Thanks in advance
Resolved Bootloop problem
Hi Dazm;
I had the exactly the same problem and i resolved it yesterday. You need to flash a custom ROM for in order for it to work again, but you battery is to low to do this e.g. if you hold both volume+ - down and keep power button for 10sec and go to fastboot ap, it would indicate this.
So what i did was the extreme lol, i created my own factory cable, I bought a usb data cable cut of the one end (micro usb) stripped the red and black coded wires, removed the back cover of the Motorola Razr XT910, and you will notice at the bottom corner of the phone is a positive + negative - with screws. I connected the red wire to the positive + and the black wire to the negative - and the other end of the usb to my computer. This will charge for 1 hour 15min, once this is done, you will need to download RSD lite 5.7 and install on pc, download stock ROM and flash the ROM with RSD lite and there you go. Mine work 100%, sorry if im not to clear, was in a rush.
arendshp said:
Hi Dazm;
I had the exactly the same problem and i resolved it yesterday. You need to flash a custom ROM for in order for it to work again, but you battery is to low to do this e.g. if you hold both volume+ - down and keep power button for 10sec and go to fastboot ap, it would indicate this.
So what i did was the extreme lol, i created my own factory cable, I bought a usb data cable cut of the one end (micro usb) stripped the red and black coded wires, removed the back cover of the Motorola Razr XT910, and you will notice at the bottom corner of the phone is a positive + negative - with screws. I connected the red wire to the positive + and the black wire to the negative - and the other end of the usb to my computer. This will charge for 1 hour 15min, once this is done, you will need to download RSD lite 5.7 and install on pc, download stock ROM and flash the ROM with RSD lite and there you go. Mine work 100%, sorry if im not to clear, was in a rush.
Click to expand...
Click to collapse
Thanks for the reply! I'm not sure this is the issue though, I can still charge my phone (It's at 100% now), and it says Battery OK in the fastboot menu. However, exactly which custom ROM I need to flash is the main part of my problem, I think.
Interesting, I'm going to have to keep my eye on this thread.
I am experiencing the same thing, after an OTA update to 672.180.41.XT910.Retail.en.FR from GB. I also experiencing a rebooting loop with the occasional boot that last about 5 minutes. Clueless about what to do at this time. Maybe flashing with a fastboot file found here.
Hopefully you can resolve your problem and help me solve mine in the process. Unlike you, it's improbable at this time to have my phone service by Motorola; Moto US won't touch because it has French software, Moto FR would fix the phone (after I cover the service and postage) but will not sent it back to me because I have an American address.
Related
So I just got done configuring chompSMS. Disabled notifications on the built in SMS app. Did a battery pull and got this screen and haven't been able to get out of it. Held down home & power and got a user memory wipe screen. Figure I'd give that a shot. Still stuck on the FASTBOOT screen and now have to redo the whole thing if I manage to get out of this screen.
Anyone else see this? Not much out there about Sprint's Hero, but there's a bit about Orange's Hero, rooting, flashing rom's and all that fun stuff. Nothing about getting it back to normal though.
and to add....after letting it sit connected to usb for a bit, the screen finally went dark but now won't turn back on. Really odd.
hmm im kinda new to android, but if your stuck in fastboot cant you use the devkit to push a new recovery image like RA 1.2.3 and flash ?
i might be wrong tough
I'm brand spanking new to Android. Haven't dealt with sdk's andn loading rom's in ages and don't have the time to figure it out. Thought there might be some hard reset button combo that I was missing or something. Just heading to the Sprint store now with box in hand to have them switch it out or activate my Treo Pro again. Kinda need the phone for work and don't have a home phone so downtime is not a good thing.
darkenergy said:
hmm im kinda new to android, but if your stuck in fastboot cant you use the devkit to push a new recovery image like RA 1.2.3 and flash ?
i might be wrong tough
Click to expand...
Click to collapse
he won't be able to push that to do ADB tricks, nor do fastboot flashing with img files
Goldcard doesn't help as well
I hv got a G1 in same situation after pulling out the battery.
Stucked at first splash screen on next boot.
I assume that is a rom / system problem so I tried to boot into recovery but still freeze on 1st splash screen.
I tried to figure out the problem and I'd try to connect by usb and tried adb logcat but only waiting device return. And yep the screen goes black ( but still on ) likely in this situation.
And yea SPL enter was successful but can't connect to fastboot so no recovery can flash.
I notify the phone (seemingly) won't be able to charge as the notification do not turn on, or it does charge but problem with notification light (?), probably it is more likely a hardware problem due to removing the battery. Recently I take the G1 to a shop to figure out is that a hardware failure.
I'm all for troubleshooting and playing around with ROMs, but there's times when I just need to be up and running and have opted not to screw around with something I depend on for work. There's other toys to "play" with.
So after a way too long stay at the Sprint store I have a new Hero that's up and running just fine.
Wanted to say it was something I installed, but everything seemed to be approved by the masses as working well. Maybe it was something with the battery pull. I'm surprised no one has made a soft reset widget. Seems kinda basic coming from 13yrs of PalmOS and a bit of winMob.
dbpaddler said:
So I just got done configuring chompSMS. Disabled notifications on the built in SMS app. Did a battery pull and got this screen and haven't been able to get out of it. Held down home & power and got a user memory wipe screen. Figure I'd give that a shot. Still stuck on the FASTBOOT screen and now have to redo the whole thing if I manage to get out of this screen.
Anyone else see this? Not much out there about Sprint's Hero, but there's a bit about Orange's Hero, rooting, flashing rom's and all that fun stuff. Nothing about getting it back to normal though.
and to add....after letting it sit connected to usb for a bit, the screen finally went dark but now won't turn back on. Really odd.
Click to expand...
Click to collapse
download htc sync and install it.
http://www.htc.com/us/supportdownloadlist.aspx?p_id=300&act=sd&cat=all
download sprint RUU and run it, it will wipe your phone, but it will work agian
ftp://xda:[email protected]_Hero_C_Sprint_1.29.651.1_signed_release.exe
thanks for that. Will keep that handy for next time or if I ever play around with it. I think I'm going to the Moment though when it hits next month. Better screen, processor and keyboard will be doing it for me.
fixing any android stuck in fastboot
If your stuck in fast boot this is what you do.
1. Remove the micro sd card and somehow connect it to your computer.
2. Download a rom that is made for your phone and put it in a easily accessible folder on the micro sd.
3. Reinsert the sd card in the phone and reboot, once in fast boot go to hboot.
4. After going into hboot select recovery.
5. After this is done you must go to "install zip from sd card" and choose the rom that you have downloaded, select install and wait until the installation is complete, if unsuccessful redownload and try the whole process again, if unsuccessful the second time try downloading another rom.
If you have any questions please personal message me so i can help you.
Download: cyanogenmod.com
Btw i had a HTC hero and had this problem many times and this had worked every time.
I have a similar situation
when i power on the phone it goes straight to fastboot mode.
I Checked volume keys and are not stuck.
If I connect phone via usb and run:
fastboot reboot
the phone will load normally the android OS and will work just fine until you power it off again.
\
I dismantled the phone just to be sure there is no hardware issues, I tried to power on the phone without the home button connected to the board and the phone will load the android OS without any issue.
I dismantled the button itself, it has some sort of touch IC inside and a normal key button downside.
I could not notice any dust or water tracks in the button, so
at this point and dont know where to go...
I dont have another button just to be sure if it is the button itself or a board issue.
dbpaddler said:
So I just got done configuring chompSMS. Disabled notifications on the built in SMS app. Did a battery pull and got this screen and haven't been able to get out of it. Held down home & power and got a user memory wipe screen. Figure I'd give that a shot. Still stuck on the FASTBOOT screen and now have to redo the whole thing if I manage to get out of this screen.
Anyone else see this? Not much out there about Sprint's Hero, but there's a bit about Orange's Hero, rooting, flashing rom's and all that fun stuff. Nothing about getting it back to normal though.
and to add....after letting it sit connected to usb for a bit, the screen finally went dark but now won't turn back on. Really odd.
Click to expand...
Click to collapse
yurais said:
I have a similar situation
when i power on the phone it goes straight to fastboot mode.
I Checked volume keys and are not stuck.
If I connect phone via usb and run:
fastboot reboot
the phone will load normally the android OS and will work just fine until you power it off again.
\
I dismantled the phone just to be sure there is no hardware issues, I tried to power on the phone without the home button connected to the board and the phone will load the android OS without any issue.
I dismantled the button itself, it has some sort of touch IC inside and a normal key button downside.
I could not notice any dust or water tracks in the button, so
at this point and dont know where to go...
I dont have another button just to be sure if it is the button itself or a board issue.
Click to expand...
Click to collapse
People still use the Hero? There are so many better phones you can buy for dirt cheap. Heck, I got the Evo LTE for $80 on Craigslist. Even the Evo Shift, Design and 3D can be had cheap. I'd dump the Hero without blinking.
So I wanted CM 10 on my phone and did all the reading as was following a guide. I got as far as installing CM 10 and on the initial start-up it says it can take up to five minutes.. Well, it sits there forever and goes there every time I reboot.
Now, when I hold the volume and power buttons it goes into Android system recovery <3e> I know I had to boot into bootstrap recovery to be able to load the file off my external drive - otherwise you get the failed signature and it won't load.
Can I do anything here to fix my phone? I don't don't care what I loose, I need this working.
Thanks-
Kyle
Ok - so I'm trying to fastboot VRZ_XT912_6.5.1-73_DHD-11_TA-3_1FF_02 onto my phone bia FlashME as RSD Lite will no longer work and its telling me battery low.
I've had this plugged into a Motorola branded wall charger for nearly 4 hours and it still says battery low. Im switching to the dual usb black square charger and a Motorola branded usb cable and trying again - after this I'm not sure how I'm going to be able to charge it...
holding volume and power and going to bp tools to get the battery meter to show does nothing, sits at moto screen forever... I dont want to claim this on my insurance - but I may have to. Help?
KyleQ said:
Ok - so I'm trying to fastboot VRZ_XT912_6.5.1-73_DHD-11_TA-3_1FF_02 onto my phone bia FlashME as RSD Lite will no longer work and its telling me battery low.
I've had this plugged into a Motorola branded wall charger for nearly 4 hours and it still says battery low. Im switching to the dual usb black square charger and a Motorola branded usb cable and trying again - after this I'm not sure how I'm going to be able to charge it...
holding volume and power and going to bp tools to get the battery meter to show does nothing, sits at moto screen forever... I dont want to claim this on my insurance - but I may have to. Help?
Click to expand...
Click to collapse
To charge the phone, you will now need the Motorola factory Charging Cable that bridges pin 4 with pin 1...anyways this will allow the phone to charge now that it is stuck in bootloop. The bridging of the pins allows the phone to think it is in the factory programming mode, allowing it to charge.
I would include a link to the post, but I am a new member...can't post links...but Google the below search term, and there is a few sites on how to make the cable, or where to buy it.
Now, I believe this will solve your charging issue. I don't know about flashing back to stock or making the ROM work, and I would look around a little more on the subject of this cable because I just stumbled across a thread about this a few days ago. A quick Google/XDA search on "Motorola Factory Charge Cable Razr" Should be sufficient.
---EDIT---
After looking through the forums again, I found a thread that may help you...it is in the middle of this forum, and it is called Low Battery charge in Ap Fastboot Fix. Take a look at that and it may help you.
Its toast - wont charge. took it all apart, hacked a cable and put the leads on the battery and gave up. put it back together - calling asurian to get a replacement. **** this thing
Hey Guys, ive scoured google for 2 days now trying to find a way to fix my phone.
two days ago i was doing some work and i left my phone on the table, and later i found out that the battery was low and it had shut off. But when i looked at it, it was just flashing the "samsung galaxy s2 gt-i9100" text logo. (and not the animation circle logo.)
I tried turning it off, didnt work so i thought it had frozen which happens, so i took out the battery and put it back in again.
Then i tried to plug it into my recharger, and it was showing a grey battery icon and was frozen on that screen always, the screen doesnt turn off, the battery icon isn't showing that its charging. doesnt change, just shows the same empty battery grey icon with the refresh circle-arrow in the middle.
I tried taking the battery out leaving it out for 5 minutes, draining the battery from the phone by holding the power button for 10 seconds, then trying to charge the phone. Same issue, only showing the grey battery icon when trying to charge and it never changes or goes away.
SO i tried to boot up the phone, but it wont go past the samsung text logo.
I tried entering recovery, but it just freezes on the samsung text logo.
I can enter Odin download mode, and ive tried installing several different both stock, original and CMW roms, and nothing changes. (except if i use gingerbread, then the grey battery icon just keeps flashing off and on in 5 second intervals when plugged into the charger.)
Ive tried taking the battery out for 8 hours and try booting it, no change.
Ive tried changing the battery, no change (think it has low bat as well maybe).
Ive tried leaving it plugged in overnight, but that only drained whatever power i had left over in one of the batteries.
Ive tried some of the siyah and doriman kernels, and they add a loading bar which gets full on the samsung text screen,
but then freezes after that.
Im losing my mind here, ive tried almost everything i can think of. And would really appreciate any help on this.
UPDATE
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Ok so to keep this post updated for people experiencing the same issues.
IT seems there is a hardware failure in progress.
BUT i managed to get a temporary fix, it seems that by having the ear plugs connected into the earphone jack in the phone, the phone becomes somewhat usable. I was able to get into recovery, and able to flash a new stock, and its up and running, but as i said this is only a temporary solution as the real issue is that the phone is not conducting the electricity in a proper way that allowed me to recharge my batteries until i had added the earphones...
The phone becomes unusable for me when i remove the earphones again, as i believe its failing to conduct the electricity from the battery properly through the motherboard without something connected into the earphone jack..
SO for people having issues with their phones, it might be a possible way to get your phone temporarily operational again.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Search for Hopper8's 'Odin troubleshooting' thread, download the 3 part stock firmware linked in the thread, flash it with Odin (only if you absolutely have an I9100/I9100T though).
Edit - Doesn't sound promising though, cross your fingers doing that works.
yeah i tried hoppers guide, didnt help me.
Still stuck on the samsung screen.
Whats wierd is, if ive got the phone on charging, it wont boot to the samsung screen even, it just turns itself off
and returns to the grey battery icon again.
Hang on....Did you try flashing the 3 part firmware like I mentioned ? If you haven't, do it. If you have, it's a service centre/local mobile repair shop job.
MistahBungle said:
Hang on....Did you try flashing the 3 part firmware like I mentioned ? If you haven't, do it. If you have, it's a service centre/local mobile repair shop job.
Click to expand...
Click to collapse
Yeah, tried 3 part, even another packages with pit files bootloader and repartitioning from another guide.
still no change, still freezes at samsung text screen.
I dont want to take it to a service center, as there is none around here as far as i know. Norway.
If i can just get it into recovery mode i can prob fix it, but i cant fracking enter recovery. Its driving me insane.
Given what you've tried, no chance of fixing it yourself by the usual methods.
Either take it to a local mobile repair shop & ask them to source a 2nd hand motherboard for you & put it in, or you source one (from a 'donor' phone; a phone with a broken screen that is otherwise OK for example, search online) & either replace it yourself or pay the local mobile repair shop to do it if you're not confident enough.
have you ever flashed a rom on that before..... or is this a stock ROM phone we are talking about???
if it was a stock ROM phone....then did it receive updates over carrier network and started to install itself???
if yes then you should have not stopped it...... i have some problem with phone 3 days ago.... i downloaded latest XWMS1 released for nordic region....... phone is fixed and i am back to neatrom 5.3.1
i suggest you download XWMS1 ...and try flashing it via Odin..... might start......
keep fingers crossed
Roshan707 said:
have you ever flashed a rom on that before..... or is this a stock ROM phone we are talking about???
if it was a stock ROM phone....then did it receive updates over carrier network and started to install itself???
if yes then you should have not stopped it...... i have some problem with phone 3 days ago.... i downloaded latest XWMS1 released for nordic region....... phone is fixed and i am back to neatrom 5.3.1
i suggest you download XWMS1 ...and try flashing it via Odin..... might start......
keep fingers crossed
Click to expand...
Click to collapse
It wasn't any update or anything, it was related to the battery i think as the batt was low.
And instead of recharging the battery, it went into bootloop and started draining the battery more when it was plugged into the charger.
ive downloaded xwms1, still stuck in bootloop.
Ive even opened it up to see if it was a hardware issue, i see no flaws, all buttons work and nothing is stuck.
the phone just keeps going to the samsung logo, and wont go into recovery mode.
It can easily go into download mode, but recovery mode is just not happening.
at this point i just ordered the Xperia Z1 instead, but i still want to fix this phone and give it to my dad or something.
desidarko said:
Hey Guys, ive scoured google for 2 days now trying to find a way to fix my phone.
two days ago i was doing some work and i left my phone on the table, and later i found out that the battery was low and it had shut off. But when i looked at it, it was just flashing the "samsung galaxy s2 gt-i9100" text logo. (and not the animation circle logo.)
I tried turning it off, didnt work so i thought it had frozen which happens, so i took out the battery and put it back in again.
Then i tried to plug it into my recharger, and it was showing a grey battery icon and was frozen on that screen always, the screen doesnt turn off, the battery icon isn't showing that its charging. doesnt change, just shows the same empty battery grey icon with the refresh circle-arrow in the middle.
I tried taking the battery out leaving it out for 5 minutes, draining the battery from the phone by holding the power button for 10 seconds, then trying to charge the phone. Same issue, only showing the grey battery icon when trying to charge and it never changes or goes away.
SO i tried to boot up the phone, but it wont go past the samsung text logo.
I tried entering recovery, but it just freezes on the samsung text logo.
I can enter Odin download mode, and ive tried installing several different both stock, original and CMW roms, and nothing changes. (except if i use gingerbread, then the grey battery icon just keeps flashing off and on in 5 second intervals when plugged into the charger.)
Ive tried taking the battery out for 8 hours and try booting it, no change.
Ive tried changing the battery, no change (think it has low bat as well maybe).
Ive tried leaving it plugged in overnight, but that only drained whatever power i had left over in one of the batteries.
Ive tried some of the siyah and doriman kernels, and they add a loading bar which gets full on the samsung text screen,
but then freezes after that.
Im losing my mind here, ive tried almost everything i can think of. And would really appreciate any help on this.
Click to expand...
Click to collapse
errrrm - just a thought (and it's a real long shot) I had some strange battery drain (bootloop) issues with a brand new i9100 and it turned out that the micro sd card I was using was corrupt, took it out and it worked. Might be worth a try but like I said its a long shot. If that does not work I agree with mistahbungle and looks like you wil need to replace the mb.
Jimsilver73 said:
errrrm - just a thought (and it's a real long shot) I had some strange battery drain (bootloop) issues with a brand new i9100 and it turned out that the micro sd card I was using was corrupt, took it out and it worked. Might be worth a try but like I said its a long shot. If that does not work I agree with mistahbungle and looks like you wil need to replace the mb.
Click to expand...
Click to collapse
Yeah ive already taken out the micro sd card and sim card, didnt change anything.
Just so weird the phone is less than 2 years old. Sucks that its already llike this.
desidarko said:
Yeah ive already taken out the micro sd card and sim card, didnt change anything.
Just so weird the phone is less than 2 years old. Sucks that its already llike this.
Click to expand...
Click to collapse
I've went through this on my Hercules, T-Mobile S2. I had Android tweaker pro, removed all of the tweaks, and rebooted. It took me quite a while but I was able to get into recovery by the normal button mashing.
DO NOT HAVE THE PHONE PLUGGED INTO THE CHARGER.
PRESS THE VOLUME BUTTONS THEN THE POWER BUTTON WHILE STILL HOLDING THE VOLUME BUTTONS.
AS SOON AS YOU FEEL THE FIRST VIBRATION, LET GO OF ONLY THE POWER BUTTON!
CONTINUE TO HOLD THE VOLUME BUTTONS UNTIL YOUR RECOVERY LOADS.
THAT IS WHAT HAS WORKED FOR ME.
Sent from my Skinny Hercules
Ok so to keep this post updated for people experiencing the same issues.
IT seems there is a hardware failure in progress.
BUT i managed to get a temporary fix, it seems that by having the ear plugs connected into the earphone jack in the phone, the phone becomes somewhat usable. I was able to get into recovery, and able to flash a new stock, and its up and running, but as i said this is only a temporary solution as the real issue is that the phone is not conducting the electricity in a proper way that allowed me to recharge my batteries until i had added the earphones...
The phone becomes unusable for me when i remove the earphones again, as i believe its failing to conduct the electricity from the battery properly through the motherboard without something connected into the earphone jack..
SO for people having issues with their phones, it might be a possible way to get your phone temporarily operational again.
Please Help !!
i kinda cloned my ROM , it happened by mistake while trying to flash my kernel , now that my phone is stuck in samsung start up logo , . tried to reboot still the same result. . . :crying:
No recovery ? If that's the case, stock rom from Samfirmware, flash with Odin to get a 'clean slate' (How ? Thread stickied near top of Q&A has instructions) & re-try whatever it was you wanted to do. If you do have recovery, try a factory reset in the first instance, if that doesn't work or if you have recovery but can't do one for whatever reason, proceed with the stock flash via Odin.
Thanks
thanks a lot mate , my fone back in action. successfully flashed, now running on JB 4.3.1 on Paranoidandroid 3.99-RC2 , so far so good .:victory:
being a newbei in this field hoping for all the support
EDIT : any suggestion how to remove warning symbol (yellow triangle) while booting .
Possibly triangle away.Search to get the free version.
desidarko said:
Ok so to keep this post updated for people experiencing the same issues.
IT seems there is a hardware failure in progress.
BUT i managed to get a temporary fix, it seems that by having the ear plugs connected into the earphone jack in the phone, the phone becomes somewhat usable. I was able to get into recovery, and able to flash a new stock, and its up and running, but as i said this is only a temporary solution as the real issue is that the phone is not conducting the electricity in a proper way that allowed me to recharge my batteries until i had added the earphones...
The phone becomes unusable for me when i remove the earphones again, as i believe its failing to conduct the electricity from the battery properly through the motherboard without something connected into the earphone jack..
SO for people having issues with their phones, it might be a possible way to get your phone temporarily operational again.
Click to expand...
Click to collapse
Okay so I have managed to get it to this point after day's of grief, now please tell me I don't have to walk around with the earplugs in for ever !
RustyNail99 said:
Okay so I have managed to get it to this point after day's of grief, now please tell me I don't have to walk around with the earplugs in for ever !
Click to expand...
Click to collapse
A friend of mine had am Android phone that had a similar problem. It always showed the headphones on the status bar and Could not be heard. If you will take your phone apart then you can look for bridges in the solder points. These happen from poor construction and over heating. Fix the bridges and you should be good to go.
Sent from my Skinny Hercules
fathertomany said:
A friend of mine had am Android phone that had a similar problem. It always showed the headphones on the status bar and Could not be heard. If you will take your phone apart then you can look for bridges in the solder points. These happen from poor construction and over heating. Fix the bridges and you should be good to go.
Sent from my Skinny Hercules
Click to expand...
Click to collapse
I did take it apart and had a quick look, all seems ok. However I was not ready to junk the phone so I improvised a little, its not pretty but it works.
I had an old headphone jack which I cut down so as it would just fit into the jack point, installed Soundabout Pro app which forces the calls to come out the earpiece and not headphones voila it works. In the end it cost me a lot of time surfing countless forums, anger management control and some joy at getting it to work. Still without the help people give on this and other forums it would be a useless phone :fingers-crossed:
sweetben747 said:
thanks a lot mate , my fone back in action. successfully flashed, now running on JB 4.3.1 on Paranoidandroid 3.99-RC2 , so far so good .:victory:
being a newbei in this field hoping for all the support
EDIT : any suggestion how to remove warning symbol (yellow triangle) while booting .
Click to expand...
Click to collapse
i was also searching for the same...... since triangle did not hurt but i wanted to know if i could get rid of it......
thanks to our wonderful Dev name Phliz i could do it... i had to reflash to stock for it ofcourse but then whole effort was worthwhile .....
http://forum.xda-developers.com/showthread.php?t=1877270
this is the link.... please go through... and best of luck to remove the triangle.....
I started to restore to a back-up I made two days ago in TWRP and I think it got interrupted by my accidentally canceling it. I was on my way out the door and wasn't paying attention and must've touched the screen (phone in hand).
Now it behaves much like cadcamaro's description in his recent post about having tried to install a Z2 ROM. I can get into FastBoot, but all options simply shut down the phone. If I don't choose an option, it shuts down by itself after a a minute or so.
Power + Volume Down gets a short vibration.
When I plug it into the PC, Power + Volume Up Gets me a blue LED that stays lit, but the PC (and Flashtool) doesn't see it.
Power + Volume Down gets an orange, then green LED with vibration that repeats.
The first time I realized it was screwed up, I did get into Recovery. I tried to re-run the back-up (which is saved to external SD), and it shut down.
Thanks, all.
AddictedToGlass said:
I started to restore to a back-up I made two days ago in TWRP and I think it got interrupted by my accidentally canceling it. I was on my way out the door and wasn't paying attention and must've touched the screen (phone in hand).
Now it behaves much like cadcamaro's description in his recent post about having tried to install a Z2 ROM. I can get into FastBoot, but all options simply shut down the phone. If I don't choose an option, it shuts down by itself after a a minute or so.
Power + Volume Down gets a short vibration.
When I plug it into the PC, Power + Volume Up Gets me a blue LED that stays lit, but the PC (and Flashtool) doesn't see it.
Power + Volume Down gets an orange, then green LED with vibration that repeats.
The first time I realized it was screwed up, I did get into Recovery. I tried to re-run the back-up (which is saved to external SD), and it shut down.
Thanks, all.
Click to expand...
Click to collapse
Have you tried pressing and holding the reset button next to the SIM tray? Try holding it down for 2+ minutes and see what happens.
Have you tried pressing and holding the reset button next to the SIM tray? Try holding it down for 2+ minutes and see what happens.
Click to expand...
Click to collapse
Thanks for responding, BladeRunner.
I just tried that in a variety of ways, and got either no response or it simply did what it was doing. I'll explain;
Believing the phone to be OFF, nothing happens for 2 1/2 minutes of pressing the Reset button.
Same goes for a variety of combinations of switches also depressed, such as Volume Up/Down, Power, or any combo therof.
(At this point, I'm uncertain if I even have much of a charge in the phone.)
FastBoot is the menu that has the green Droid with a choice of 4 options, including Power Down, Continue to Power Up, Factory Reset, and something else, correct?
The one time that I did get that to appear during these last few attempts to use the Reset switch, the menu simply shut down after 15 seconds. I continued to press the reset switch, but nothing happened.
Plugged into the PC, the phone continued to cycle Power-On every 8 seconds, with the Orange LED followed by the Green, then Shut-Down. (Apparently, as without the screen on I have no idea what it's really doing....)
Plugged into PC, Power Button in and Volume Up gives me the Blue LED that stays on constantly, but depressing the Reset Switch does nothing.
As I stated earlier, I have no idea how much charge the phone has, so I'm leaving it on the PC in the Blue LED state. It may not be charging, but all it does when I try to charge it any other way is cycle through every 8 seconds with the Orange & Green LED.
Sigh... This would be the first phone I've ever bricked, and I've been messing around since Vivo on the V3m, and always very careful. Sucks since this has been my favorite of them all.
AddictedToGlass said:
Thanks for responding, BladeRunner.
I just tried that in a variety of ways, and got either no response or it simply did what it was doing. I'll explain;
Believing the phone to be OFF, nothing happens for 2 1/2 minutes of pressing the Reset button.
Same goes for a variety of combinations of switches also depressed, such as Volume Up/Down, Power, or any combo therof.
(At this point, I'm uncertain if I even have much of a charge in the phone.)
FastBoot is the menu that has the green Droid with a choice of 4 options, including Power Down, Continue to Power Up, Factory Reset, and something else, correct?
The one time that I did get that to appear during these last few attempts to use the Reset switch, the menu simply shut down after 15 seconds. I continued to press the reset switch, but nothing happened.
Plugged into the PC, the phone continued to cycle Power-On every 8 seconds, with the Orange LED followed by the Green, then Shut-Down. (Apparently, as without the screen on I have no idea what it's really doing....)
Plugged into PC, Power Button in and Volume Up gives me the Blue LED that stays on constantly, but depressing the Reset Switch does nothing.
As I stated earlier, I have no idea how much charge the phone has, so I'm leaving it on the PC in the Blue LED state. It may not be charging, but all it does when I try to charge it any other way is cycle through every 8 seconds with the Orange & Green LED.
Sigh... This would be the first phone I've ever bricked, and I've been messing around since Vivo on the V3m, and always very careful. Sucks since this has been my favorite of them all.
Click to expand...
Click to collapse
I'm not sure what fastboot mode on the z3v looks like honestly, but your description sounds about right. You could try getting into xz dual recovery again and wiping the cache maybe? The instructions to there are in the xzdr thread. If you can get there wiping, a factory reset or flashing something might work but failing that you might want to try letting the battery drain all the way down. If you just let your phone sit that can take a while ( days at least) or you use a rubber band to hold down the poet and volume down button, I believe, to drain the battery. Once its dead completely connect it to your PC and see what happens.
A failed flash on a eeprom can be a hard thing to recover from, sometimes it can ruin the eeprom preminently, depends on the state the eeprom was in in the flash process,usually in erase process it will not be recoverable. . Removing power will not reset the eeprom, eeproms are preminent memory, but it can allow the device to be discovered again hopefully.
You have to get something to erase and flash again, if the eeprom is in a failed state that may be impossible to do.
1linuxfreak said:
A failed flash on a eeprom can be a hard thing to recover from, sometimes it can ruin the eeprom preminently, depends on the state the eeprom was in in the flash process,usually in erase process it will not be recoverable. . Removing power will not reset the eeprom, eeproms are preminent memory, but it can allow the device to be discovered again hopefully.
You have to get something to erase and flash again, if the eeprom is in a failed state that may be impossible to do.
Click to expand...
Click to collapse
So I'm assuming the eeprom is like an order of operations & file allocation index or something really basic upon which everything else is built? This is an old school term for file index, right?
So even if I manage to get everything wiped, I need to start fresh by installing the stock ROM that the phone came with and progress to where I can load the saved Back-Up that's on the External SD?
If the eeprom gets wiped as it's re-written from the Back-Up, and interruption blew this process mid-wipe, will my Back-Up still be useable?
How is it that battery drain will help my device become recognized by the PC?
Thanks for all the help.
AddictedToGlass said:
So I'm assuming the eeprom is like an order of operations & file allocation index or something really basic upon which everything else is built? This is an old school term for file index, right?
So even if I manage to get everything wiped, I need to start fresh by installing the stock ROM that the phone came with and progress to where I can load the saved Back-Up that's on the External SD?
If the eeprom gets wiped as it's re-written from the Back-Up, and interruption blew this process mid-wipe, will my Back-Up still be useable?
How is it that battery drain will help my device become recognized by the PC?
Thanks for all the help.
Click to expand...
Click to collapse
Correct. Your backup is safe as long as you don't mess with sdcard storage. You have to get the eeprom healthy before you can do a recovery.
Back to working on my bricked Z3v...
Plugged into PC with Volume-Up held in yields solid Blue LED. This is the only time that in Windows 8.1 Device Manager that the phone shows up as a connected device. The name of the device is "S1 Boot Fastboot", for which there is no driver installed. When I navigate to Z3-lockeddualrecovery2.8.23-RELEASE.combined / files / adbdrivers and try to install the driver, Windows says "Windows could not find driver software for your device."
However, in the "Events" tab it shows three previous dates that the device was configured. It listed the device as such "Device USB\VID_0FCE&PID_0DDE\BH900JCL1N was configured." on those dates.
Was there something different I had to do for Windows 8? I cannot remember, but this feels familiar.
Driver Name: Google, Inc. (WinUSB)...
Status: Install failed
Meanwhile other drivers do install. What gives?
Well I was hoping for a bit more. Extremely frustrated right now as it took me about 15 minutes just to get here to see that nobody can help.
In the meantime with all the **** I've downloaded trying to fix my phone, I've completely scxrewed my computer. 4 virus scans later and I'm still f'd.
Great.
AddictedToGlass said:
Well I was hoping for a bit more. Extremely frustrated right now as it took me about 15 minutes just to get here to see that nobody can help.
In the meantime with all the **** I've downloaded trying to fix my phone, I've completely scxrewed my computer. 4 virus scans later and I'm still f'd.
Great.
Click to expand...
Click to collapse
Your phone is toast and the only way to get it back is through the Flashtool imo. It wouldn't be common for many to have your circumstances with a bricked phone so you aren't getting much feedback. See if you can follow these instructions with Flashtool that I posted. I've gone from 4.4.4 to 5.02 non-rooted and back to root on 4.4.4 and then forward again so it has worked well for me.
http://forum.xda-developers.com/showpost.php?p=63800685&postcount=8
See if you can download the 4.4.4 firmware after getting flasthool 09.18.6 installed. Granted my instructions are from Windows 10 64 bit but it should work.
Couldn't do any of it. My PC is s screwed up, but even in Safe Mode I was unable to load drivers that would recognize my z3v.
So I'm typing this on my replacement phone that came today via FedEx. I was very nervous about getting a refurb, but this one really is like new. I managed to get the glass protector of the old one, rinse it off, and apply it to the new one.
Now I'm on unrooted kitkat.
If I root and install TWRP, can I simply flash my saved lollipop backup from my SD card and make this phone exactly like the other one was before I borked it?
AddictedToGlass said:
Couldn't do any of it. My PC is s screwed up, but even in Safe Mode I was unable to load drivers that would recognize my z3v.
So I'm typing this on my replacement phone that came today via FedEx. I was very nervous about getting a refurb, but this one really is like new. I managed to get the glass protector of the old one, rinse it off, and apply it to the new one.
Now I'm on unrooted kitkat.
If I root and install TWRP, can I simply flash my saved lollipop backup from my SD card and make this phone exactly like the other one was before I borked it?
Click to expand...
Click to collapse
I wouldn't recommend that. I have used titanium backups before from one device to another and it worked. The whole system from a twrp backup really doesn't sound like a good idea.
OK. Think I'll just be patient and do it from scratch. Have to get the computer cleaned up first.
Really glad to have a clean, new z3v back again, but this ordeal has certainly impacted my confidence doing this stuff.
Thanks for your help, everyone.
Hi , I had my Motorola Droid 4 XT894 by Verizon working until last week. One of my kids threw it on the floor.
The phone got stuck on Droid logo loop.
So I tapped into recovery, made the power+volume keys combo but it never went into recovery mode.
So I tried fastboot mode (power+UP+DOWN volume keys) I get into fastboot menu and selected fastboot menu option (so I can get this
phone to flash original stock rom back (which I downloaded from one of the threads here on XDA Developers, using rds lite 4.5).
But Battery being FULLY charged before the drop, showed me it needed more energy and won´t allow the flash.
3 hours later (trying to flash many other roms for 2.3 and 4.0, 4.1 and 4.4) battery went dead.
I hard wired red cable to positive and black cable to negative connectors in the non removable battery (as shown from a cut-usb cable on youtube) and plugged the device onto the wall to feed it power.
Battery never charged up a bit. Didn´t even warmed up. The only signal that energy is going through is that when I push the power button, it shows a white screen with a lot of little color pixels randomly scattered. There´s no text to read or sound to hear.
*Phone still gets recognized by computer on fastboot before and after the "half flash".
*Device is correctly identified when adb command: "fastboot devices" is typed.
QUESTION TIME:
If I buy a brand new original motorola battery - would my phone recognize it and ignite power on? or did I just lost a phone?
If I remove the screws and get the batt out and place it on those generic rechargeable phone battery-devices with tweezers, would it correctly charge?
Thank you community.
Regards.
Thanks.
main phase 2
got a radio-electronic guy. Charged the battery up to 4.2 (battery says that´s the fullest charge on the back label). So I guess I´m ready to go and flash original ROM.
I think I got one or 2 updates (I don´t recall the 4.0 upgrade, but I´ll say the original ROM should be: VRZ_XT894_6.7.2-180_DR4-16_M2-37_1FF.xml.zip
Right?
Working - Partially until reeboot
Hi Everyone. I successfully loaded in the battery with an all-night-charge with direct connection to the wall charger. So I ran RSD Lite, and flashed original stock ROM. It flashed sucessfully.
So YES, definitely a fully charged battery (hardwired) did allow for the full process to flash the entire rom into the phone.
I waited 15 full minutes until all 1 to 18 process were done. RSD showed: Now flashing files and reeboot.
The phone took another 7 minutes to get into android (and it also showed me : updating system files 1-of-69) and so it did. System loaded in correctly and I have all my OLD desktop icons and contacts and everything back. BATTERY is FULLY CHARGED. (it is shown on the screen).
So I press the power button to turn the phone off.
I turn it on again, and all I get now is a white screen with a lot of randomly scattered color pixels. Again the phone doesn´t do anything
and there´s no MOTO logo.
I´m going nuts now....how do I fix this?