Related
I flashed a non-US rom on my Vibrant and now my volume buttons are backwards and my power button isn't recognized in recovery mode. The funny thing is, I am stuck in recovery mode. I can't get out of it. I pulled the battery and turn on the phone and it automatically goes to the recovery. I tried to go into download mode as well, but no luck. Hmmmm what to do now? Any advice would be appreciated!
i hope someone helps you out. If someone else was in trouble with their phone, they would want help. Wish I could help. Im sure someone will get to U
this just did it to me i need help also anyone got any idea how to fix it
Wow, that really sux. I honestly do not know what to do at this point, I am only replying to give my sympathy and a bump.
I am quite experienced in AmonRa Recovery, but new to clockwork (I am assuming that you are using clockwork). Is it possible to connect to adb while in clockwork, without the use of an "action" key?
Very sorry this happened to you guys, hope someone figures it out soon!
I would read this thread and follow it:
http://forum.xda-developers.com/showthread.php?t=738085
It looks as though others are in the same boat as you are after flashing non US roms.
If you have ADB working I typed "adb reboot clockwork recover" and it rebooted me back up $hit scared the hell out of me now im scared to flash my nandroid
Don't know if this helps, but eugene373 said he used the back soft-key to act as an action key in clockwork recovery
http://forum.xda-developers.com/showthread.php?t=740077
I am new to the android world, I have a vibrant that I rooted using the update.zip method. Then I went to apply the LAG FIX using the same method from the RyanZA thread. Now all I get is a boot sound and a black screen along with the buttons on the bottom glowing. I have no Idea where to even begin to recover this. I have a mac, any suggestions would be helpful. Thank you in advance!
Fathom0195 said:
I am new to the android world, I have a vibrant that I rooted using the update.zip method. Then I went to apply the LAG FIX using the same method from the RyanZA thread. Now all I get is a boot sound and a black screen along with the buttons on the bottom glowing. I have no Idea where to even begin to recover this. I have a mac, any suggestions would be helpful. Thank you in advance!
Click to expand...
Click to collapse
That's a boot loop. In your case, being new and all, it might be better to re-install the ROM and try again. You might need to give it a while as well, I don't know the details of the zip you used, but it might be copying large amounts of data, which will look like a stall in the boot process.
Get ADB and open a terminal window and do "adb logcat" it should let you know where you are stuck in the boot. Post the log and someone here should be able to help you.
Also, get boot camp and/or Virtualbox going so you can use Odin, which requires Windows. If you mess something up, you can use Odin to get back to a stock setup. Sucks that it requires Windows, but that's just how it is for now.
Oppps mis-read this phone is complete black no noise just heat
Moved your thread to general section.
Had the same problem when I tried to install that FixLag update.zip. Lucky for me, I did an Anroid Backup before I attempt it.
Hold down Vol+ & Vol- and power it up, do a Wipe.. when its done, restart your phone. When its booting up, its gonna act the same without the Tmobile Flash and still missing the Samsung Galaxy S logo. Just wait for your phone to VIBRATE. Then your phone should be working. I dont know what happen in that update.zip but it deleted the Graphic at the beginning when you first boot up your phone. After that I went back and did a Recovery and got everything back too normal.
kiddiosky said:
Had the same problem when I tried to install that FixLag update.zip. Lucky for me, I did an Anroid Backup before I attempt it.
Hold down Vol+ & Vol- and power it up, do a Wipe.. when its done, restart your phone. When its booting up, its gonna act the same without the Tmobile Flash and still missing the Samsung Galaxy S logo. Just wait for your phone to VIBRATE. Then your phone should be working. I dont know what happen in that update.zip but it deleted the Graphic at the beginning when you first boot up your phone. After that I went back and did a Recovery and got everything back too normal.
Click to expand...
Click to collapse
It worked!! Thank you so much! I am back up and running. No boot screens, however funtional and root maintained. Is there a way to recover the boot screens?
I was just searching through the forums for the answer to the last post in this thread - "is there a way to reinstall the boot animation? Well, is there? Mind, I DO NOT want the horrible tmo portion, just the S.
Thought?
Droidicus said:
I was just searching through the forums for the answer to the last post in this thread - "is there a way to reinstall the boot animation? Well, is there? Mind, I DO NOT want the horrible tmo portion, just the S.
Thought?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=7663822&postcount=38
I just did this to my phone like the ones stated above..... Blank screen then vibrate and im in the Android OS and it changed the Audio but still no graphics....... Kinda disapointing but until someone finds hwo to actually finx this I'm stuck.
So I just rooted my device and then tried to install a lag fix... when I rebooted my phone after the script, I heard the T-Mobile jingle and then it came to a blank screen. When I pressed the power button there was no response. If I press any of the white keys at the bottom, they just light up. I CAN turn my phone off and go into recovery mode.
This thing has kind of shaken me up so I am willing to go back to an unrooted phone.
PLEASE HELP!
Nandroid, my friend.
Since you are able to boot into recovery, do a nandroid restore.
If you do not have your own nandroid backup There is a thread in the Dev forum you can dowload one from. Just search "[ROM] OFFICIAL T-Mo Vibrant JFD ODIN/Nandroid Backup Images 7/29/10 (Tested/Working)" (I can't hotlink yet. sorry)
This is all assuming you have installed clockwork recovery, which you should have done before you attempted any modding of any sort. Also always remember to create a nandroid of your current system before trying something that is still in beta.
i got same problem here and a don't have clockwork recovery :-(
Then you have to use odin if you don't have clockwork...
My phones have been flashed more than Girls Gone Wild..
[email protected]
I think I found a fix that works...
I just went to recovery mode, and deleted all user data.
I then rebooted and still had a blank screen for about 10 seconds, and then my lock screen came up.
Worked for me! Thanks everyone.
nearblack said:
So I just rooted my device and then tried to install a lag fix... when I rebooted my phone after the script, I heard the T-Mobile jingle and then it came to a blank screen. When I pressed the power button there was no response. If I press any of the white keys at the bottom, they just light up. I CAN turn my phone off and go into recovery mode.
This thing has kind of shaken me up so I am willing to go back to an unrooted phone.
PLEASE HELP!
Click to expand...
Click to collapse
Sorry to resurrect old posts, but I would like to know If after rooting and lag fixing it, it didn't show ABSOLUTELY NOTHING on boot screen and you were only able to hear the sounds and the buttons lit up...
I have a Vibrant on this situation and would like to know I this procedure can fix it.
Best Regards.
Just wait 10 mins if nothing do a battery pull...boot...wait another 10. It will boot after that. Had same issue on two vibrants.
Sent from my SGH-T959 using XDA App
Happendd to me. Just let it sit there. It'll boot.
Sent from my SGH-T959 using XDA App
This happen to me I tired volume up+down+ power nothing happen...... here's what I found...Unplug ur battery n plug it back in with ur usb n when it turns on use adb on ur computer..... adb reboot recovery n do a data wipe
Hope this helps
Sent from my SGH-T959 using XDA App
Thanks for your answers, will try them all and report results.
Best Regards.
Got a replacement Vibrant today and it will not boot into recovery with vol up/dwn/power buttons, any ideas? I booted my first Vibrant daily into recovery, this one won't do it.
Have you tried Quick Boot in the market?
SugarMouth said:
Got a replacement Vibrant today and it will not boot into recovery with vol up/dwn/power buttons, any ideas? I booted my first Vibrant daily into recovery, this one won't do it.
Click to expand...
Click to collapse
The thing with these Vibrants is that some of them have that problem where the phone doesn't register that your pushing the volume buttons at boot up...only the power button, which is why it just turns on and nothing else. This is a known issue that was found out by another canadian phone company(Bell)
I just bought a Vibrant and I could not boot into recovery from day one...after a week I took it back 'today' and got a replacement and now it works. I guess me and you were the unlucky ones.
If you really want it to work I would take it back somehow because this isn't fixable, its a hardware issue on boot.
-By the way, you can still boot to recovery from adb or rom manager, anything like that, just not physically. The down side of this is that if your in a boot loop and your computer doesn't recognize your phone your screwed. It also doesn't recognize Download Mode either to restore.
Hope it works out for you.
Wow so I'm screwed? Hard to call up T-Mobile and say "hey my phone won't boot into recovery, I need to switch it."
s15274n said:
Have you tried Quick Boot in the market?
Click to expand...
Click to collapse
I need root for that and I can't boot into recovery to get root.
SugarMouth said:
Wow so I'm screwed? Hard to call up T-Mobile and say "hey my phone won't boot into recovery, I need to switch it."
Click to expand...
Click to collapse
Actually thats exactly what I did...I told them I like to have control over my phone and that I use the recovery to "clean up" my phone every month or so and I like to use the recovery to do it. I also told them in the past i've used the recovery to install OTA updates that simply did not want to install over the air, so I would download it myself and install manually. The T-mo rep didn't seem to care.
So why not root this way then, and use quick boot once you have root
http://forum.xda-developers.com/showthread.php?t=739300
s15274n said:
So why not root this way then, and use quick boot once you have root
http://forum.xda-developers.com/showthread.php?t=739300
Click to expand...
Click to collapse
Exactly...do that. Like I said in my first post, you can still do everything thru Quickboot, Rom Manager, etc and ADB. You just won't be able to get to recovery that way if your phone won't boot or is stuck in a boot loop..that would suck.
As I mentioned in your other thead on this subject, I have the same problem with a brand-new Vibrant, and I don't want to root it yet. Only way I was able to get into clockwork recovery was via 'adb reboot recovery' method. Once I'd done that, I was able to install and run wirelessap tethering without rooting, infrastructure mode and all. Still not rooted, but I never did get my intended 'factory-fresh' nandroid backup, I gave up and popped in my SIM and installed a few things before I got adb talking to the phone. (running adb on ubuntu box, hadda kill and restart server as root to fix permissions issue)
j
I got my replacement vibrant, after bricking the first one, and I can confirm that I am not able to boot into recovery by holding the volume buttons. I hope samsung hasn't changed something...
But thankfully I was able to finally get into recovery using ADB...
I hope someone can help me. I've been scouring the blogs but couldn't find anything that could help me and I'm stuck. I have a mytouch 3g slide and all of a sudden it keeps rebooting and won't turn completely on...it just keeps rebooting non-stop. I tried taking out the battery overnight and putting it back in, held the volume down button + power button which brought me to the HBOOT screen and only showed FASTBOOT, RECOVERY, CLEAR STORAGE & SIMLOCK. When I tried clicking on RECOVERY it just reboots my phone and does it over and over again, same thing when I do CLEAR STORAGE. I've tried this both with the SD card in and out and it would still not take me to where there's the red triangle...just keeps rebooting. Everything else I've seen on forums tells me to unroot/reroot, reformat, flash etc but since whatever I do it just reboots I can't do it. Other details of my phone are the following:
EXPRESSO PVT SHIP S-ON
HBOOT-1.02.0000
MICROP-0620
TOUCH PANEL-SYNT0102
RADIO-7.07.35.02S
Nov 26 2010, 20:43:01
CM7
I'm sorry but I'm pretty new to this and I get lost with the terms so I'm trying to be as detailed as I can. I really do hope someone can help me
ka-dork said:
I hope someone can help me. I've been scouring the blogs but couldn't find anything that could help me and I'm stuck. I have a mytouch 3g slide and all of a sudden it keeps rebooting and won't turn completely on...it just keeps rebooting non-stop. I tried taking out the battery overnight and putting it back in, held the volume down button + power button which brought me to the HBOOT screen and only showed FASTBOOT, RECOVERY, CLEAR STORAGE & SIMLOCK. When I tried clicking on RECOVERY it just reboots my phone and does it over and over again, same thing when I do CLEAR STORAGE. I've tried this both with the SD card in and out and it would still not take me to where there's the red triangle...just keeps rebooting. Everything else I've seen on forums tells me to unroot/reroot, reformat, flash etc but since whatever I do it just reboots I can't do it. Other details of my phone are the following:
EXPRESSO PVT SHIP S-ON
HBOOT-1.02.0000
MICROP-0620
TOUCH PANEL-SYNT0102
RADIO-7.07.35.02S
Nov 26 2010, 20:43:01
CM7
I'm sorry but I'm pretty new to this and I get lost with the terms so I'm trying to be as detailed as I can. I really do hope someone can help me
Click to expand...
Click to collapse
It sounds as if your phone is toast... however, you could try going to the HTCdev.com site and doing the unlock procedure (which is going to require you to enter fastboot, so if that's not working, you're truly toast).
Once you've got that done, you can then flash a new recovery, like clockworkmod, and see if you can then use that to clear storage, or flash a new ROM.
Alternatively, you could try to just reinstall the froyo update from T-Mobile/HTC.
Thanks
jonnycat26 said:
It sounds as if your phone is toast... however, you could try going to the HTCdev.com site and doing the unlock procedure (which is going to require you to enter fastboot, so if that's not working, you're truly toast).
Once you've got that done, you can then flash a new recovery, like clockworkmod, and see if you can then use that to clear storage, or flash a new ROM.
Alternatively, you could try to just reinstall the froyo update from T-Mobile/HTC.
Click to expand...
Click to collapse
Thanks for the help, jonnycat26. I really appreciate it. It does seem my phone is pretty much toast I tried unlocking it as you said but you're right, it won't let me enter fastboot and my PC couldn't detect the phone since it won't turn on.
I was wondering though, would you happen to have any idea what caused this? It would be good to know so I don't make the same mistake next time around. Thanks again!
Wait! Your phone isn't toast! Download the RUU from the htc website, run it on windows, take the rom.zip from %TEMP%, rename it to ESPRIMG.zip and put it on your sdcard, then boot into Hboot, and it'll reflash the system.
Hitorijanae said:
Wait! Your phone isn't toast! Download the RUU from the htc website, run it on windows, take the rom.zip from %TEMP%, rename it to ESPRIMG.zip and put it on your sdcard, then boot into Hboot, and it'll reflash the system.
Click to expand...
Click to collapse
Thanks, Hitorijanae! I'll try that and let you know how it goes.
Hi Hitorijanae,
Okay I'm not sure if I did it right. I saved it to my sdcard as ESPRIMG.zip as you said and then did the volume down + power thing and it brought me to the screen with the 3 androids (sorry not quite sure if that's the HBOOT page that you were talking about). Anyway it did the SD checking. Does it make a difference if it says [ESPRDIAG.zip] no image or wrong image? Anyway it loaded up the ESPRIMG.zip and then asked me if I wanted to update it and I said yes. After that it asked if I wanted to reboot and when I said yes it just rebooted over and over again like my previous problem. I tried also choosing no and it brought me back to HBOOT and my only options were FASTBOOT, RECOVERY, CLEAR STORAGE & SIMLOCK. Choosing FASTBOOT just brings me to reload bootloader, etc.; choosing RECOVERY my phone just reboot loops again and same if I choose CLEAR STORAGE.
I'm not sure if I'm doing it wrong or just screwing it up even more. Sorry for all the questions but I keep getting stuck. I would appreciate all the help I can get.
ka-dork said:
Hi Hitorijanae,
Okay I'm not sure if I did it right. I saved it to my sdcard as ESPRIMG.zip as you said and then did the volume down + power thing and it brought me to the screen with the 3 androids (sorry not quite sure if that's the HBOOT page that you were talking about). Anyway it did the SD checking. Does it make a difference if it says [ESPRDIAG.zip] no image or wrong image? Anyway it loaded up the ESPRIMG.zip and then asked me if I wanted to update it and I said yes. After that it asked if I wanted to reboot and when I said yes it just rebooted over and over again like my previous problem. I tried also choosing no and it brought me back to HBOOT and my only options were FASTBOOT, RECOVERY, CLEAR STORAGE & SIMLOCK. Choosing FASTBOOT just brings me to reload bootloader, etc.; choosing RECOVERY my phone just reboot loops again and same if I choose CLEAR STORAGE.
I'm not sure if I'm doing it wrong or just screwing it up even more. Sorry for all the questions but I keep getting stuck. I would appreciate all the help I can get.
Click to expand...
Click to collapse
When it's booting up, go into the command prompt, cd to the directory with adb and then do adb logcat.
Hitorijanae said:
When it's booting up, go into the command prompt, cd to the directory with adb and then do adb logcat.
Click to expand...
Click to collapse
When I do that it only says -waiting on device- and nothing else. I tried doing the unlock bootloader thing but when it comes to the part after I type in fastboot oem get_identifier_token it just says waiting on device as well. Any other suggestions? I'm not really a dev so I'm not very confident if what I'm doing is right and I get lost sometimes with what you ask me to do but I try to look it up online to get a better understanding of it and then try it before I ask too many questions. I appreciate your patience with me though and for all your help, Hitorijanae and jonnycat26. I'd like to go on if there's still hope for my phone :crying:
ka-dork said:
When I do that it only says -waiting on device- and nothing else. I tried doing the unlock bootloader thing but when it comes to the part after I type in fastboot oem get_identifier_token it just says waiting on device as well. Any other suggestions? I'm not really a dev so I'm not very confident if what I'm doing is right and I get lost sometimes with what you ask me to do but I try to look it up online to get a better understanding of it and then try it before I ask too many questions. I appreciate your patience with me though and for all your help, Hitorijanae and jonnycat26. I'd like to go on if there's still hope for my phone :crying:
Click to expand...
Click to collapse
Alright, go into HBOOT, then hit power button to go into fastboot. Plug it up, and type fastboot devices in the command prompt.
Thanks!
Hitorijanae said:
Alright, go into HBOOT, then hit power button to go into fastboot. Plug it up, and type fastboot devices in the command prompt.
Click to expand...
Click to collapse
Hi, Hitorijanae!
Sorry for the late reply and things got a bit crazy over here. I had my phone checked and it was a hardware problem so they had to open it up and stuff and now it's all good but I have to be extra careful not to drop or accidentally hit my phone or else it's screwed again. I just wanted to thank you for all your help though
Do you know what was the issue? (Loose cable, failed component, etc)
GoPadge said:
Do you know what was the issue? (Loose cable, failed component, etc)
Click to expand...
Click to collapse
The guy said it was a hardware issue. Something broke off inside and damaged the memory (I accidentally dropped my phone a few days before my phone went bonkers on me). I wish I could explain it better but for the life of me I can't remember the things the guy said right now but he had to open it up and weld the broken bit back together.
ka-dork said:
The guy said it was a hardware issue. Something broke off inside and damaged the memory (I accidentally dropped my phone a few days before my phone went bonkers on me). I wish I could explain it better but for the life of me I can't remember the things the guy said right now but he had to open it up and weld the broken bit back together.
Click to expand...
Click to collapse
Solder, not weld, but I understand completely. I had to replace the power button and digitizer on mine.
GoPadge said:
Solder, not weld, but I understand completely. I had to replace the power button and digitizer on mine.
Click to expand...
Click to collapse
LOL! Yeah, goes to show you how much I know about this stuff I just have to be extra careful with my phone...I hope it holds up for a bit longer.