So, last night, I was silly, tried flashing the ICS port on low battery...the install rebooted in the middle of an operation, and I had this nice Att logo/Google logo reboot loop. If I plug the phone in with the battery installed, the battery charging animation appears for a moment, then I get a flash of some text(similar to text you see when a rom is installing in CWM) and then it reboots to the battery logo, and this repeats forever.
I can force the phone into download mode, but when i attempt to use Odin, the process freezes at the zImage or rfs install. I'm trying Heimdall now, and for the first two tries it stopped at 4 and 10% of the flashing kernel step. This most recent try it stopped at 76%...so I don't know what to do.
I've tried rebooting the computer, a different cable, different ports, running Odin as admin and in compatibility mode, and it still freezes.
Any ideas?
use my Heimdall One-Click UCKB2. flash it once, then flash again with Flash Bootloaders checked.
Related
I have a little problem and could use some help. I was running superclean 2.9.2 and attempted to switch over to the community rom. Before flashing the rom I downloaded the stock CI500_VZW_DL09_ECLAIR.tar.md5 file and attempted to load that with Odin(yes i chose pda). I have used Odin multiple times in the past w/out issues. Well this time my screen went blank on the Odin was stuck on param.lfs. When i disconnected my phone it now boots to the screen with a phone, exclamation point and a computer. I closed Odin restarted my computer and tried again with the same result. I can still access the download mode and CWM. When I try to complete a nandroid restore the phone goes through the whole process and then when I click to reboot I get the same screen as above. My next step was to download DI01package3.tar.md5. I tried pushing this with Odin and it got stuck on sbl.bin. Please help me get my phone back.
I flashed Bionix-v on my phone the other day, it is a vibrant rom, and I flashed it on my i9000M without knowing this. I liked bionix, but I wanted my old configuration instead, so I restored from my back up with Nandroid. It would work fine until I plug it into either a computer or an outlet, it would immediately power off and have a battery that appears for a split second, then a loading circle, preventing me from connecting to the computer to transfer any type of file. It would continue this cycle until I powered my phone back on again which would say "Vibrant" (I'm using the GT-i9000) then my usual Galaxy S logo. It resumed working.
I decided that I needed a NORMAL charging process so I followed the guides and used Odin to flash my phone back to stock firmware. Odin told me everything succeeded and a giant "PASS" was lit up in green at the top of the window. However my phone no longer had a battery flashing, it was instead just a loading circle that would flash without stop. I unplugged my phone, and was greeted by a "Galaxy S" logo that would flash instead. I have also tried Heimdall by following TubeShaped's : http://forum.xda-developers.com/showpost.php?p=11257871&postcount=154
And tried to flash a custom rom directly from Odin: http://forum.xda-developers.com/showthread.php?t=940671
None of these methods have worked. If any of you have any idea of whats going on, I'd appreciate the help. My hunch is that by loading a custom Vibrant rom onto a GT-i9000, something went amiss, but have no idea what it could be.
This morning, I was on the current CM experimental build. I decided to flash the latest nightly. It flashed normally. It got about halfway through the "Android is optimizing applications" screen. Then, it shut off. It now boots to the point where the CM guy is on the screen with the spinning arrow and then it hangs for a few seconds and reboots. I figured something went wrong, so I decided to wipe it and re-flash the experimental build. When I tried to boot to recovery it gets to the point right before the buttons appear, then it reboots. (CWM Touch 6.0.4.5) I then decided to try download mode. Download mode appears to work fine, except that nothing recognizes the phone. I tried Heimdall, Odin, and even this weird Verizon Tool http://forum.xda-developers.com/showthread.php?t=2586319 (I know that it's for a different version, I just wanted to see if it would show up). I tried under Window and Linux, uninstalled and re-installed drivers, swapped USB ports and cables. It has no listing whatsoever in Device Manager. Custom binary download is off, the current binary is Samsung Official, the system status reads custom, and secure boot says that it is enabled.
Any help or advice would be much appreciated. Thanks.
my nexus 4 was on temasek's unofficial cm12 build ver 6.1
recovery in use was recovery-philz_touch_6.59.0-mako
i decided to update the rom to build 6.5, so i downloaded the zip to my sdcard,
i had not made a nandroid bkp
after flashing the rom/gapps/superuser, wiping dalvik and cache, things went wrong
after that the phone would only show 'google', then freeze, then go blank, then again show 'google'. this is the first Loop i have encountered where the boot animation never even showed up.
after that in about 8 hrs, i tried all of the foll-
installing the stock images: my phone booted up the first few times i flashed stock images using fastboot, but after three times (because each time it successfully booted i would go back to recovery to try flashing the customromzip) my phone stopped booting up for stock.
it resolutely stayed stuck on the boot ani.
recovery: flashed many times, via sdcard and also via fastboot. no problem with the recovery
zips. absolute fail. nothing can get me past the 'google'
now there's another peculiarity, which makes me wonder if there is hardware damage involved in this softbrick story
after all this flashing my charge came down to 20%, so i tried to charge it (switched off, obviously, since it isn't booting up)
but every time i connect my charger, it boots up,and then shows me google, and freeze and restart..same old cycle
in a last ditch attempt to somehow charge my phone i have brought it to fastboot, and left it connected to my laptop. i don't know if this will work.
please help, also i am now considering using a toolkit, unified android or wugfresh (the latter, i have a previous bad experience with) to get my phone to atleast switch on with something.
should i use the toolkit or just take my brick to the servicecenter to check for damage to hardware
Last night I tried to flash TWRP just because I wanted to go to a custom ROM- alas, the phone now will not go past the google logo. It usually hangs there for 10-ish seconds and then reboots. Occasionally hangs there indefinitely. It's not a power button issue- the button worked just fine before flashing and I've confirmed it still works normally with a multimeter.
I tried to reflash stock using the Google images and "flashall.bat", which says it succeeded- but the phone still loops. I can get into fastboot, but I get the bootloop even in recovery. Running the similar script through Nexus Root Toolkit always fails on flashing the system partition- usually a buffer error due to a sparse header. Can't even seem to get it to do the "fastboot boot TWRP.img" or whatnot. I've flashed KitKat, Lollipop, and MM stock roms to no avail- they all say they succeed, then continue to bootloop.
I've tried just about everything I've seen on here- but not being able to get into recovery hampers efforts like repairing the persist partition.
Help?
When you boot into recovery, the phone reboots itself? If it does, it could be a sign of a failing power button.
When flashing a stock ROM, are you flashing userdata.img and then performing a factory reset/wipe before booting the phone with a stock ROM for the first time?
When I can get into recovery (without a restart), the phone is totally fine.
I think part of the issue is that the battery ran down while I was trying to do the repair- hence it trying to restart and failing. Power button still seems fine (again, confirmed with a multimeter). I left it plugged in to my iPad charger (since that's a 2A charger) overnight and it was still blinking red in the morning. I moved it upstairs and now I can't even make it that far.
Perhaps the battery was just shot by the time I got the "repair" done, hence the boot loops. Is there any way to revive it shy of cutting open the battery + charging manually (with a bench supply) or just replacing the battery altogether? I may try doing a motherboard swap with my working Nexus 5 just to see if it is in fact the battery.
When the phone is powered off and connected to a power source, do you ever see a flashing red LED? You flashed the correct twrp for the hammerhead?
I would try a new battery because it seems like everything is working.