Related
After ROM upload my HTC Hero show only some logo like device out of box. Nothing else is going. Button combinations for bootloader access is not working. Any ideas?
I managed to skilfully brick mine too, is a there a way to get it to boot up via key combination or using USB from a computer?
We are three now.
I know (presumably) my error: I flashed an SPL zip package that could be of the wrong type (Dream).
The boot shows the phone logo (mine says G2 T-Mobile).
The home keydown at boot doesn't work.
Is there a possibility to unbrick it?
Hope someone tells you how to unbrick it as I was about to do the update the ROM, not sure I want to do it now.
Right this is very weird as i had the same picture on my phone and thought it was bricked too..
BUT i just did a soft reset call menu end together. Then i did a hard reset as i wasnt sure if the soft one had done anything. Battery out then in and start up phone whilst holding down house and back key and then it started to boot up. So not sure if this helps anyone i doubt it as its very random but i thought id share just in case!!!
I had just flashed my radio when mine did this..
friend of mine had tha problem too, he had to send his device to htc.. 50 bucks ;-)
hmmm ... i am one of u guys now ...
no matter what key-combo i press, it just show a BOX and an arrow and a phone ... 3 sec later, phone turns off, no matter hwat key u press, it is not doing anything until u unplug the batery ... then when u turn it on, it repeat the same thing again
check if you can access fastboot via back+power when the phone is off. if so install recovery image and then install correct rom. if not i guess you're screwed, not sure though.
This guy
http://forum.xda-developers.com/showthread.php?t=556038
seemed to have the same issue and resolved it.
Hope it helps/good luck!
sonatbey said:
i bricked very bad no screen no logo not booting. anyway any helps
Click to expand...
Click to collapse
Please be more explicit as to what exactly you did.
(for someone to help you)
Soooo ....I tried to install the update from OTA and my phone is now stuck in a failed to boot mode /starting rsd services screen......anyone help me out real quick? This is my first MOTO since the star tac , ive been strictly htc since the mogul....im rooted other than that ive done nothing else to the phone.....
If it is "Starting RSD Services" then your phone is not bricked. Assuming you can't make it boot any other way, you can load up RSD Lite on your pc, connect the phone via usb, and flash the latest SBF which will completely reload your OS. Granted you are going to need the correct drivers to do this.
Now, I'm wondering if you've done anything to this phone prior to applying the OTA update or was the phone completely stock? If it was stock and you did not unlock the bootloader then I'd just return it to Sprint and let them take responsibility for it. Otherwise you can do the repair yourself but only at your own risk...
I've posted the basics below but feel free to click here to go to the actual thread which explains this. I recommend you make sure your phone is charged before doing this.:
RSD Lite and 32 Bit Drivers (Install the 32bit drivers if you are running a 32bit Windows OS)
64 Bit Drivers (use these instead are running a 64 bit version of Windows.)
Latest SBF
1. DL and install RSDLite and Driver package from link above
2. Power down your phone
3. On your phone hold vol up and power till you see RSD at the top of the screen
4. Launch RSDLite from your program menu on your pc/laptop
5. Press the “. . .” button next to the box labeled “Filename”
6. Load up the SBF file you extracted from the MR download
7. Plug your device into your computer RSDLite should recognize your phone right away if you installed the drivers from this link i provided
8. Press the “Start” button
9. Be patient...takes a while...will reboot a couple times so grab a beverage of choice...use the restroom...take out the dogs...whatever...
10. may require activation again...mine did so be sure you have a means in which to do so...web...phone to call sprint for programming...OTA...
11. Enjoy and hit thanks!!!
Don't thank me, thank Yay 4 Juggs, I took this from his thread. If you have further issues you should post them there.
yeahried to flash the newest update, but now all it says is failed to boot 2 at the top of the moto screen...... Idk what now...???
make sure you have insurance
why would i need insurance? this phone is less than a month old, and the thing dumped on me while flashing Sprints OTA system update.....pretty sure it is thier fault.......lol......
The sbf update failed? Pull the battery for a few minutes then put it back and press and hold volume down while holding the power button. Does it say fastboot?
Also, you are within your return period so they will probably take it back unless you unlocked the bootloader. I don't think they'll take it back if it says unlocked at the top when you boot it, if it doesnt say that it should be fine because Sprint is okay with rooting. I wouldn't tell them you attempted the SBF though, just that the OTA update borked your phone.
ok I got it thanks everyone.......rsd failed to flash because my battery was lower than 50% .......i charged it and it flashed the first time with no problems......i dont understand why you have to re register your phone after the rsd flash though.....Motorola Android phones are wierd
I'm glad to hear your phone survived. Yeah you definitely want to make sure your phone is charged whenever you do any sort of modifications to the system/bootloader/recovery partitions. As for the reactivation, its not bad once you learn your MSL number you can do it yourself without needing to call Sprint. I'm thankful your phone didn't brick. lol
My phone also was recovered after doing as outlined by Yayy . Don't go into RSD with a low battery or you WILL pay the consequences.
I tried doing this and my battery died... Now I'm not sure where to go from here. I either charge it from the computer and ONLY the green led lights up and then like 10 minutes later the phone automatically comes on and says failed to boot 2, starting rsd, battery too low to flash. Or I can plug it into my wall and the phone automatically comes on and says the same thing immediately. Which way should I do this?
Nickdroid86 said:
I tried doing this and my battery died... Now I'm not sure where to go from here. I either charge it from the computer and ONLY the green led lights up and then like 10 minutes later the phone automatically comes on and says failed to boot 2, starting rsd, battery too low to flash. Or I can plug it into my wall and the phone automatically comes on and says the same thing immediately. Which way should I do this?
Click to expand...
Click to collapse
You may want to look on ebay for a Motorola Photon 4G / Droid 3 Battery Charger for a few bucks/no shipping cost. Order the charger, rush shipping if you feel you need to, open the package, take the battery out of your phone, plug the battery in the wall with the charger, and wait until the light changes from red to blue/green and continue from there.
Sent from my MB855 using xda premium
deedscreen said:
You may want to look on ebay for a Motorola Photon 4G / Droid 3 Battery Charger for a few bucks/no shipping cost. Order the charger, rush shipping if you feel you need to, open the package, take the battery out of your phone, plug the battery in the wall with the charger, and wait until the light changes from red to blue/green and continue from there.
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
no other ways to get it to charge? tried to relock and ended up with this problem didnt realize mt phone was so low and now all i get is the failure to boot 4 starting rsd battery too low..... sucks to be me just got this phone through ebay so would have to pay the fee to get new one from insurance if i cant fnd a way to charge this thing really dont want to have to buy another battery or charger old lady already mad i got such a picey phone and screwed with it and screwed it up...ha ha oh well
I cut the end off of a charger stripped the red&black wires placed red on pos blk on neg of battery and plug into wall for about 20 min the battery started getting warm but this worked for me
Sent from my MB855 using XDA App
In rsdlite uncheck the delete on exit box. It will save your battery
Sent from my MB855 using XDA App
I thought if it was semi-bricked you could still charge it?
sbf update-failed to boot 2
Hey after doing OTA for latest sbf im getting error
failed to boot 2
starting RSD mode
and when i srestart my mopho is runs normally but after some time it restarts on its own and goes to above error message again
my battery is showing at 50% is that the reason
is there any other way to fix it??
Flash 154 then 198
dilkush said:
Hey after doing OTA for latest sbf im getting error
failed to boot 2
starting RSD mode
and when i srestart my mopho is runs normally but after some time it restarts on its own and goes to above error message again
my battery is showing at 50% is that the reason
is there any other way to fix it??
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
still no luck
jokersax11 said:
Flash 154 then 198
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
Hey it's showing that my version is 154 only....
also when i tries to connect to rsd lite it's showing unable to initialize from .INI file
can you post link for 198 update on xda forum link is not working
Loki is making a new guide thread with everything in it, ill oil the whip
dilkush said:
Hey it's showing that my version is 154 only....
also when i tries to connect to rsd lite it's showing unable to initialize from .INI file
can you post link for 198 update on xda forum link is not working
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
Looks like it started working fine once i wiped my cache but at the same it it showed notification that update failed.....not worried about update failure as finally my mopho started working!!!!!!!!!!!!
Heeeeere we go.
long story short I messed up, here are the symptoms(spent 2 hours scouring the internet and XDA BTW)
SVF:108:1:2
Failed To Boot 3
Entering NvFlash Recovery Mode
thats after trying to enter recovery (vol-/pwr), alternatively I recieve a "Starting RSD mode" if I try to boot normally or try to plug phone in to charge.
Also, just tried (vol+/vol-/Pwr) received "Starting Fastboot Protocol support"
battery too low to flash...this presents a problem as I am unable to plug the phone in without it coming on....
All tutorials Ive found involve failed to flash 0x1000 or something of that nature, I am not receiving that message.
It never progresses past that. If anyone could point me in the direction of a good tutorial or even the thread that Im apparently missing it would be greatly appreciated.
Thanks!
Have you tried this thread?
[How To] Recover from a soft brick
giqbal said:
Have you tried this thread?
[How To] Recover from a soft brick
Click to expand...
Click to collapse
Thats the one I was referring to that flashed that lil red light. My atrix isnt displaying either of those problems and I cannot get to fast boot.
gorealmighty said:
Thats the one I was referring to that flashed that lil red light. My atrix isnt displaying either of those problems and I cannot get to fast boot.
Click to expand...
Click to collapse
Can you get to your recovery? If you can get to rsd you might be able to recover by flashing sbf
giqbal said:
Can you get to your recovery? If you can get to rsd you might be able to recover by flashing sbf
Click to expand...
Click to collapse
Unfortunately the process as I described it above is how it happens. I dont get to choose which "mode" it goes to. It just depends on the action/button combination. It never progresses past that.
gorealmighty said:
Unfortunately the process as I described it above is how it happens. I dont get to choose which "mode" it goes to. It just depends on the action/button combination. It never progresses past that.
Click to expand...
Click to collapse
Well i think you need to flash sbf file in rsd mode. The sbf should be on the version you had originally or higher (if you were on 2.3.4 so don't flash 2.2.2 otherwise you'll hard brick). I might be wrong so someone else should confirm me before you proceed with it.
Not to sound like a broken record...but I'm not sure that that's possible. I don't have the option to choose. Unless you ate suggesting that from the available options I listed above I make an attempt.
Sent from my Inspire 4G using XDA
gorealmighty said:
Heeeeere we go.
long story short I messed up, here are the symptoms(spent 2 hours scouring the internet and XDA BTW)
SVF:108:1:2
Failed To Boot 3
Entering NvFlash Recovery Mode
thats after trying to enter recovery (vol-/pwr), alternatively I recieve a "Starting RSD mode" if I try to boot normally or try to plug phone in to charge.
Also, just tried (vol+/vol-/Pwr) received "Starting Fastboot Protocol support"
battery too low to flash...this presents a problem as I am unable to plug the phone in without it coming on....
All tutorials Ive found involve failed to flash 0x1000 or something of that nature, I am not receiving that message.
It never progresses past that. If anyone could point me in the direction of a good tutorial or even the thread that Im apparently missing it would be greatly appreciated.
Thanks!
Click to expand...
Click to collapse
You say in this post that when you boot normally the phone says "Starting RSD Mode". Im talking about using this mode to flash sbf…you can search the forums on how to flash sbf in RSD mode.
Also you'll need to charge your battery some way(battery can't charge without going into OS) before you flash.
gorealmighty said:
Not to sound like a broken record...but I'm not sure that that's possible. I don't have the option to choose. Unless you ate suggesting that from the available options I listed above I make an attempt.
Sent from my Inspire 4G using XDA
Click to expand...
Click to collapse
I'll give it a try, thanks
Sent from my Inspire 4G using XDA
FAIL any more suggestions?
Sent from my Inspire 4G using XDA
umm...
thats after trying to enter recovery (vol-/pwr), alternatively I recieve a "Starting RSD mode" if I try to boot normally or try to plug phone in to charge.
Also, just tried (vol+/vol-/Pwr) received "Starting Fastboot Protocol support"
battery too low to flash...this presents a problem as I am unable to plug the phone in without it coming on....
Click to expand...
Click to collapse
if you can get to working fastboot support you can probably recover.
http://forum.xda-developers.com/showthread.php?t=1501532
follow Alaq/ Uncle Cemka's method of flashing pudding via fast boot, I have recovered more than one phone this way, your going to need a way to charge your battery though, might have to buy an external battery charger, build a powered usb cable or cutup a cable and apply the + and - straight to your battery....you can search and find ways to charge your battery.
Also a little more info than just "Fail" would be helpful, did the RSD flash fail, is the phone just boot looping and going straight to RSD support or fastboot support? Error messages? it may not seem relevant but many of us have seen similar error messages and know different ways to get back to a working phone but we need more information from you to be able to help.
Also I have seen phones with the SVF:105.1:2 failed to boot error actually be accessible by RSD even when the screen did not mention RSD support was up...
You might need to strip the end of a USB cable and charge the battery directly. Another user posted instructions somewhere. I'm sure a quick google will reveal all.
Sent from my MB860 using Tapatalk 2
Wreaks, thanks much I'll look into it.
Consolation thank you as well.
I'm not giving up I'm still working on the beast.
Sent from my Inspire 4G using XDA
Hey, to make a long story shorter i tried to root it but did not succeed.. fully.. haha, well it all went smooth until i wanted to go in to recovery first time
after unlocking bootloader, i couldnt get in there, so i erased cache and tried again, and different methods then i started to try to flash another recovery img, didnt want to work and still i could not get in to recovery.... tried to lock and unlock bootloader and other things and nothing....
So i did it from scratch,. but i couldnt even do factory reset from bootloader, couldnt do anything from there really... and then it didnt want to boot normally for some reason, i might just have been impatient but... so i started flashing in another boot.img.... dont ask me why but in the end when i felt there was no more hope i started flashing in everything i had, more or less.. what i think got f'ked up is the Kernel.
i used this guide http://forum.xda-developers.com/showthread.php?t=2069904 and used that all in 1 tool most of the time, but also tried manual commandands via fastboot..
.
when it locked up totally, it didnt want to boot normally after that i could just get in to bootloader, so i sat all day yesterday putting posts in different threads in several forums so dont say i havent looked ^^
i didnt get any answer anywhere in time and it got uncharched, and was dead since yesterday so i gave up, until today, i couldnt charge it.. but i tried now and from nowhere i could get into bootloader again but this time with too low battery to flash!!
and i dont think its charging properly, dont know why exactly.. so im just sticking the usb cable in and out while its powered off since the red Led just light up for a sec when inserted then nothing, just to maybe get some power in there...
so im kind of at a cricis here, and would need help since i dont have anymore time to try to fix it
dont know exaclty what info you need, dont want to boot in unneccesary right now so just ask if u need any numbers or whatever..
i bought it very recently here in sweden.. dont rly know what more information i can give
Would surely appreciate some solid help!
Sincerely, jeff
VivaSativa said:
Hey, to make a long story shorter i tried to root it but did not succeed.. fully.. haha, well it all went smooth until i wanted to go in to recovery first time
after unlocking bootloader, i couldnt get in there, so i erased cache and tried again, and different methods then i started to try to flash another recovery img, didnt want to work and still i could not get in to recovery.... tried to lock and unlock bootloader and other things and nothing....
So i did it from scratch,. but i couldnt even do factory reset from bootloader, couldnt do anything from there really... and then it didnt want to boot normally for some reason, i might just have been impatient but... so i started flashing in another boot.img.... dont ask me why but in the end when i felt there was no more hope i started flashing in everything i had, more or less.. what i think got f'ked up is the Kernel.
i used this guide http://forum.xda-developers.com/showthread.php?t=2069904 and used that all in 1 tool most of the time, but also tried manual commandands via fastboot..
.
when it locked up totally, it didnt want to boot normally after that i could just get in to bootloader, so i sat all day yesterday putting posts in different threads in several forums so dont say i havent looked ^^
i didnt get any answer anywhere in time and it got uncharched, and was dead since yesterday so i gave up, until today, i couldnt charge it.. but i tried now and from nowhere i could get into bootloader again but this time with too low battery to flash!!
and i dont think its charging properly, dont know why exactly.. so im just sticking the usb cable in and out while its powered off since the red Led just light up for a sec when inserted then nothing, just to maybe get some power in there...
so im kind of at a cricis here, and would need help since i dont have anymore time to try to fix it
dont know exaclty what info you need, dont want to boot in unneccesary right now so just ask if u need any numbers or whatever..
i bought it very recently here in sweden.. dont rly know what more information i can give
Would surely appreciate some solid help!
Sincerely, jeff
Click to expand...
Click to collapse
Dude I just googled ur problem......
found a possible solution from HTC One X forum http://forum.xda-developers.com/showthread.php?t=2148689
refer Post #4 the bat file might solve ur problem
Anyways I would like u to confirm it with some senior developers(PM them)
I'm sure they ll help u out.....
Good luck
Danny Samuel said:
Dude I just googled ur problem......
found a possible solution from HTC One X forum http://forum.xda-developers.com/showthread.php?t=2148689
refer Post #4 the bat file might solve ur problem
Anyways I would like u to confirm it with some senior developers(PM them)
I'm sure they ll help u out.....
Good luck
Click to expand...
Click to collapse
it aint that easy.. ive been to several threads that were it was similiar problems, tried all those similiar solutions aswell.. this one was nowhere close to my solution
i tried it but now again its stone dead cant even get in to bootloader so computor just says waiting for device.
who are these senior developers and where do i find them??...
what recovery are you using
Lloir said:
what recovery are you using
Click to expand...
Click to collapse
i was trying to use the TWRP 2.4.1.0 at first, then tried clockworks with no success..
now i think i want to download some fresh ones... again
VivaSativa said:
i was trying to use the TWRP 2.4.1.0 at first, then tried clockworks with no success..
now i think i want to download some fresh ones... again
Click to expand...
Click to collapse
just plug the phone into the wall, leave it for a day or so.
Lloir said:
just plug the phone into the wall, leave it for a day or so.
Click to expand...
Click to collapse
alright, that might solve my battery problem... but then what? my problem still consists...
then flash a correct twrp\boot.img\rom
Lloir said:
then flash a correct twrp\boot.img\rom
Click to expand...
Click to collapse
that is what ive been trying all along, tried to clear cache.. but it seems like the first one i got in there wont go away and is priotized or something..
it was this morning i tried for fun to press power and it started i was like wtf because it wasnt plugged in.. then i plugged it in to start this thread its been shut down and plugged in the wall since i put this thread, around 12.. and i cannot start in into bootloader again, completely dead for now..
if i insert it in to my pc the red LED flashes 3 times if i put it in the wall it flashes steady 1 time. but does not seem to get any charge from either
VivaSativa said:
it was this morning i tried for fun to press power and it started i was like wtf because it wasnt plugged in.. then i plugged it in to start this thread its been shut down and plugged in the wall since i put this thread, around 12.. and i cannot start in into bootloader again, completely dead for now..
if i insert it in to my pc the red LED flashes 3 times if i put it in the wall it flashes steady 1 time. but does not seem to get any charge from either
Click to expand...
Click to collapse
Your battery is critically low.
As already advised by lloir... Just plug it in to the charger, and may forget for a good 24 hours so that the phone exists....
Addicted2xda said:
Your battery is critically low.
As already advised by lloir... Just plug it in to the charger, and may forget for a good 24 hours so that the phone exists....
Click to expand...
Click to collapse
i will do that, its still in the wall and shut off, and try some solution tomorrow, but i still dont quite have that solution ^^
Once charged, you could download the correct RUU, flash that, and restart from scratch. You may have to relock the bootloader using Hasoon's toolkit. After that, its not complicated - use Hasoon's kit to unlock again, flash the correct recovery, sideload a ROM and boot up your phone.
surfatwork said:
Once charged, you could download the correct RUU, flash that, and restart from scratch. You may have to relock the bootloader using Hasoon's toolkit. After that, its not complicated - use Hasoon's kit to unlock again, flash the correct recovery, sideload a ROM and boot up your phone.
Click to expand...
Click to collapse
i have the correct RUU on my desktop, i searched for ages before i found it, but this is an .exe and starts a program for me and have failed at the last part.. i cant try it now so i can see what it said and i cant remember exactly at what step it failed.. i came like halfway in to it
or do you mean the ruu.zip version? to flash it manually into the device?
did you relock the bootloader? the error message might help
surfatwork said:
did you relock the bootloader? the error message might help
Click to expand...
Click to collapse
relock it for what step, i tried to lock and and unlock it several times
seriously, you need to read atleast a little bit - a million people before have posted exactly the same questions, have had answers posted umpteen times. you need to relock the bootloader before you run the RUU.
surfatwork said:
seriously, you need to read atleast a little bit - a million people before have posted exactly the same questions, have had answers posted umpteen times. you need to relock the bootloader before you run the RUU.
Click to expand...
Click to collapse
well sorry for acting Stupid but i just want to be completely sure since ive been at it since friday now
if i get it to start tomorrow, i think ill start with the .bat file to get it to charge some more, then relocking the bootloader, then flashing a proper ruu..
is these steps somewhat correct??
no one??? i got it to boot a short time today then stone dead again so there is some hope
Hi there!
This thread is my last hope, so please dont let me down folks...:cyclops:
The story short - one sunny morning i turned on my HTC Nexus One and it got stuck with te X on the screen for about 15 minutes, non of the buttons responded, so i did the first thing that came in my mind - i pulled out the battery. After inserting the battery the phone went full brick, i mean literally, no reaction on anything, even conected to the wall charger, there is no sign of life, no charging LED, nothing. Connected to the PC, it says USB device not recognised.
I dont think this is a hardware proble, the phone workwd fine until this interrupted power on. Phone runned on stock Androud, i have not played aroun with it - no bootloader unlock, no rooting.
I searched the internet for a solution, tried a lot of button combinations like in this thread:
http://forum.xda-developers.com/showthread.php?t=1069032
but still no luck, i cannot restore or flash it while my PC does not recognise the phone.
Found some info about those Usb Jig things, but they work only on Samsung phones, so, is there a way to force the phone to go in recovery mode, or give any sign of life so i can try to recover it or flash a diferent ROM?
The warranty has ended, so no hope there.
Hope there is a way out of this, and, sory for my bad english. :good:
Veesais said:
Hi there!
This thread is my last hope, so please dont let me down folks...:cyclops:
The story short - one sunny morning i turned on my HTC Nexus One and it got stuck with te X on the screen for about 15 minutes, non of the buttons responded, so i did the first thing that came in my mind - i pulled out the battery. After inserting the battery the phone went full brick, i mean literally, no reaction on anything, even conected to the wall charger, there is no sign of life, no charging LED, nothing. Connected to the PC, it says USB device not recognised.
I dont think this is a hardware proble, the phone workwd fine until this interrupted power on. Phone runned on stock Androud, i have not played aroun with it - no bootloader unlock, no rooting.
I searched the internet for a solution, tried a lot of button combinations like in this thread:
http://forum.xda-developers.com/showthread.php?t=1069032
but still no luck, i cannot restore or flash it while my PC does not recognise the phone.
Found some info about those Usb Jig things, but they work only on Samsung phones, so, is there a way to force the phone to go in recovery mode, or give any sign of life so i can try to recover it or flash a diferent ROM?
The warranty has ended, so no hope there.
Hope there is a way out of this, and, sory for my bad english. :good:
Click to expand...
Click to collapse
Well no, bricked is a term used when you are rooted and flash a bad rom,kernel,etc. You have no root, so you cannot be "bricked". Just a software failure, you cannot flash another rom because, again, you have no root or custom recovery. Your best bet is trying to send it back to your carrier and get it replaced
ParanoidKang said:
Well no, bricked is a term used when you are rooted and flash a bad rom,kernel,etc. You have no root, so you cannot be "bricked". Just a software failure, you cannot flash another rom because, again, you have no root or custom recovery. Your best bet is trying to send it back to your carrier and get it replaced
Click to expand...
Click to collapse
The warranty time is out, so there is no help from the carrier, unless for cash...
But there must be a way to bring it back to life.
Veesais said:
The warranty time is out, so there is no help from the carrier, unless for cash...
But there must be a way to bring it back to life.
Click to expand...
Click to collapse
Now the screen may not show, but try booting into fastboot mode by press and hold the Trackball+Power buttons together.
I'm not sure about the nexus one, but newer nexus devices have factory images, supplied by Google. If they exist for the nexus one, you should be able to save your device by flashing them through fastboot. That is if the images exist and you can get to fastboot.
Sent from my Nexus 4 using XDA Premium 4 mobile app