as i mentioned a few days ago, i recently rooted some vibrants for a few of my friends.
one of them decided to switch me phones for a few days just to see if he liked my phone (g2) since he wants to upgrade anyways.
so i unlocked his vibrant using this hex editor method. worked like a charm. popped in my sim and at&t came up, all was well with the world.
i was going to do a nandroid backup of his phone so i used rommanager to boot into recovery.
that didn't happen.
his phone hung at the samsung vibrant screen. i figured no big deal, maybe just a hiccup. pulled the battery and attempted to start the phone again normally, but still stuck on vibrant. tried a few more reboots with no new results. next i booted the phone into download mode which worked just fine. dl mode came up normally and was recognized by odin. still feeling creative, i decided to pull the battery while it was in dl mode then undo the usb cable. put the battery back in, turned it on and voila! phone booted like normal!
i was pretty damn confused. i could get it to boot this way about 1 out of every 3 tries. i thought perhaps changing the nv_data.bin file was what screwed it up so i replaced the modified one with the original and re-locked his phone.
so the phone boots up normally, i go to rommanager, tell it to install clockwork recovery, wait for it to finish and attempt to reboot into recovery mode, this time through adb. the phone still got stuck on the vibrant screen BUT adb still recognized that the phone was attached AND in recovery mode.
still confused. i'm assuming perhaps the adb functionality was due to restoring the original nv_data.bin?
so i rebooted his phone via adb and it turned on like normal, told him not to turn the phone off. i was going to take it with me to work today, but we're generally busy on saturdays and i won't have time to mess with it. gonna take it monday and try some more stuff.
so long story short; unlocked phone, wouldn't reboot into recovery, just hung on vibrant screen. put phone in dl mode, pulled battery, attempted boot and it worked. relocked phone, reflashed cwm in rommanager, rebooted via adb, still hung on vibrant screen but recognized by adb.
anyone ever had anything similar to this happen?
This actually happened to me once. Bit once i odin'ed back to stock it fixed it and it never happened again.
Related
Alright, I was having problems with my CyanogenMod, and I went to restart my phone because it kept force closing all my apps (including system processes) and it got stuck on the Vibrant screen and never started up.
I went to Nandroid to restore my backup I made before CM7, and it must be corrupted, because it refused to restore, so I said to hell with it and decided to start from scratch.
Long story short, I ended up flashing the wrong ROM by accident because I got confused between the Samsung Vibrant and the Samsung Galaxy S 4G, and somehow I got my phone stuck at an AT&T World Phone logo, and it won't do anything else. I've tried entering recovery AND download mode, and neither will work. Also, when I plug my phone into the USB port, the charging indicator gets stuck at the very beginning, showing a pinwheel and a greyed out battery.
I ordered a USB jig, hoping this would help send my phone into DL mode, but I'm still open to any ideas anyone has until then. I haven't had a phone for a couple days and its killing me!
itsjuztin said:
Alright, I was having problems with my CyanogenMod, and I went to restart my phone because it kept force closing all my apps (including system processes) and it got stuck on the Vibrant screen and never started up.
I went to Nandroid to restore my backup I made before CM7, and it must be corrupted, because it refused to restore, so I said to hell with it and decided to start from scratch.
Long story short, I ended up flashing the wrong ROM by accident because I got confused between the Samsung Vibrant and the Samsung Galaxy S 4G, and somehow I got my phone stuck at an AT&T World Phone logo, and it won't do anything else. I've tried entering recovery AND download mode, and neither will work. Also, when I plug my phone into the USB port, the charging indicator gets stuck at the very beginning, showing a pinwheel and a greyed out battery.
I ordered a USB jig, hoping this would help send my phone into DL mode, but I'm still open to any ideas anyone has until then. I haven't had a phone for a couple days and its killing me!
Click to expand...
Click to collapse
Here's some tips:
1. NEVER restore non-cm7 nandroid backups on a cm7 based rom.
2. Flash stock JFD with repartitioning checked to go back to stock.
3. Reflash vibrant bootloaders. You may have some captivate bootloaders or a mismatched param.lfs that's causing the AT&T bootsplash. It could be one or the other and mismatching captivate and vibrant bootloaders or params could lead to a brick so just flash the vibrant bootloaders since it contains both bootloaders and param.lfs.
4. DL mode depends on the bootloaders you run.
Froyo bootloaders-------------
1. Volume up and down with USB inserted and with battery disconnected
2. Insert battery without letting go of buttons
Gingerbread bootloaders-------
1. hold power and volume up with the battery inserted and with the phone powered off
2. connect USB to pc when booted into DL mode.
P.S. Can you take a picture of the front and the back of the phone so I can identify the kind of phone you are using at this moment?
The name you are using for the device you have is kinda confusing me.
I believe I'm running ICS Passion, I'm not sure what version
Last night I turned my Vibrant off. It wasn't anything special, just a boot because my messenger app wouldn't open. However, when I got home and tried to turn my phone back on the phone will take an unusually long time to get past the loader, and then the boot animation seems to run forever. I left it on overnight and my phone was not booted in the morning. The process seems to take up a lot of battery as well. I'd like to avoid flashing another rom because I haven't had preparation, but I need to update soon anyway so it's not completely out of the question. How can I attempt to fix this?
Odin back to stock
djquick said:
Odin back to stock
Click to expand...
Click to collapse
I figured I'd have to do this.
I used my home made jig to get into download mode (because the three button combo isn't working) however my computer is refusing to recognize the device when I open Odin. I'll try on my desktop when I get home, but for now I'm just going to let the phone boot and see what happens.
I'll post back if I still can't odin to stock.
Hey guys, Today I just finished downgrading to HBOOT 1.4 and got up and running fine on TWRP 1.1.1 and ViperRom's new ICS build. I wasn't having any issues at all. I started reading about TWRP2 though, and felt like checking it out. So I downloaded GooManager and searched for TWRP and got openrecovery-twrp-2.1.3.blob. I touched it to download and it immediately went into recovery to install. However, as soon as it rebooted, it came up with TWRP 1.1.1's logo and a scrolling status bar. This lasted about 2 seconds and then the phone shut off. I left it as is hoping it would come back for about 10 min but nothing. I removed the battery and put it back in and tried to reboot. Booting to system and booting to recovery give zero response and ADB controls don't seem to recognize the device when plugged into USB. Can anybody help? TWRP2 doesn't seem to have a thread here and their site has limited resources for help.
thanks.
Can you boot into the bootloader (hold power and down on startup)?
no I cannot. Phone is completely unresponsive. I didn't think trying to flash a recovery would cause complete system failure.. wth
Just to be clear, before you call it a brick, did you remover battery for 10 seconds and then try to get to the bootloader. Hold down the volume first then the power button and keep holding both until the bootloader pops up. Just making sure...
yeah I did. Pulled the battery, left it out while I went and ate something, then plugged in the HTC charger and tried to reboot and nothing. Tried putting the battery back in and doing the same thing. I guess It's time to go to sprint and beg for mercy
Same thing happened to me. My phone is completely unresponsive after I tried to update to TWRP 2.1. I was on AOKP milestone 5a. The computer responds when I connect the USB, but the phone will not boot at all.
EDIT: Computer doesn't respond either. Think I'm headed to the nearest Sprint store ASAP.
Connect your device to your computer then go into your adb directory in cmd and type. "adb reboot-bootloader" (without the quotation marks)
Are you s-off ? And does the phone show up as qhusb_dload in device manager ? If it does it is bricked. If you still have s-on it can be fixed if you are s-off i am sorry to say you have to get a new phone. I have a phone now that is s-off and bricked and i cant recover it as of now but i am working on it, if i succeed i will post how to do it.
I would recommend trying to keep the bricked phone in case there is a way to unbrick eventually then you have another phone to play with. I just claimed my insurance and told them i dropped the phone in a porta-john at work and i wasn't about to fish it out. So they told me dont worry about sending the bricked phone in and i got my new one next day.
A couple days ago, within an hour of using my phone and everything seeming to be fine, my phone got stuck at the Galaxy Note II logo. Thinking that it locked up and reset itself or something like that while in my pocket, I pulled the battery because it didn't respond to the power button. after I replaced the battery and turned it on, it stopped at the same screen. After a few attempts, I tried to get into recovery mode and it only got to the download screen. After some research, it sounded like I could maybe flash the stock rom onto the phone and get back up and running. so I downloaded ODIN and found what I thought was the correct ROM and tried to flash it. ODIN gave an error about unable to find a PIT file, so more googleing later, I found a PIT file and tried again. ODIN tried for about 10 minutes and then failed. My phone was still on the download screen so I thought to just try the process completely from the start again. I unplugged my phone from the computer and tried to restart it, I think by holding the power button down but I may have just pulled the battery. once my phone turned off it hasn't turned back on again. It wont even attempt to charge when I plug it into the wall.
So I ask the people who are far more experienced with this kind of thing, did I unrecoverably mess up my phone, or is there something I can still do?
Soo... I have a S2 and S3. I use the S2, today I woke up for my phone freezing on Samsung Logo. I tried booting Recovery, froze on Team Win logo, so I guessed that something is the software went wrong. I decided to flash some Recovery from Odin and boot into Recovery. I Googled, downloaded one recovery, flashed it via Odin, didn't work, tried another one, didn't work, I would put out the battery every time between tries. And boom it wont turn on, only gets warm in the camera region. So I tried all the combinations of putting it the power with and without battery, pushing all the button combinations etc. I told myself I'll deal with it later, need a phone right now. So I used a spare phone my brother game me, an S3. It had a stock ROM and I wanted to flash JB on it. I rooted the S3, downloaded TWRP for Odin, flashed it with Odin, it didn't work, it booted me to a stock recovery, so I rebooted the phone, it went to Samsung logo, I removed the battery to go faster to Download Mode and try something else, and it wont turn on. What happened and what can I do to fix that? I really need a phone for tomorrow. Please help.