I am a "noob" to android but have always gotten elbow deep into computers so i figured I would take a crack at it. Well it cracked me back and now I am stuck and help would be great....
I have an ascend II cricket phone, I rooted the phone using a guide foud on www,theunlockr,com and everthing was good. Iflashed a couple different roms and still no problems but I couldn't find one that had everthing I wanted so I decided to dig deeper.
I reflashed the phone back to stock with no problems and started changing little thing like sounds and the boot animation and then I went for broke and tried flashing a kernel that was supposed to enable multi-touch on the display - BRICK-!
I once again reflashed back to stock and installed the android updateds to bring my as current as the ascend to gets and re-did all my custom sounds and graphics.
This is where things go bad, I put everything back on the phone (battery, back plate, and hard plastic holster) and inadvertently put the holster on upside down so when I powered the phone on the two volume buttons where being held in by the holster and it once again started to re-flash the firmware, I didn't want to mess it up and yank the battery mid process so i let it run and it never came back .
At current the phone powers on but freezes at the oem boot logo. I have tried with no sucess to enter both fastboot and recovery, however I can still re-flash the firmware. When connected to my pc the computer recognizes that the device is plugged in only if I boot the phone while holding both volume buttons in with out an sd card inserted. This brings me to a blank pink screen. even though windows sees it there is no communication to the device.
I downloaded the stock firmware from several different source but they all produce the same result.
Also every 15 minutes or so the screen goes blank, vibrates and the boot logo comes back on, obviously the phone is trying to do something so I feel as though all is not lost, any advice or ideas as to what I can do from here would be greatly appreciated. (i tried to make sure I included all the details of my situation if there is anything else I or you need to know just ask.)
Related
I just flashed the Frankin Final rom on my vibrant and all was going well until I rebooted it and now the damn thing seems to be in a boot loop of some sort, but this is different than all others I have seen cause it goes to the samsung screen like normal and then it goes to a totally different screen that is only half size and is jumbled up and not a damn thing is readable. When I plug in my USB to the computer not only is it seen by the computer but it goes to the battery icon and then back to that screwed up - half sized screen. Please someone help.
Go back into recovery and reflash the rom you had installed previously. Or do a nand backup. You did back it all up before you flashed v4 as you should have, right?
I do have it backed up from v3 but it wont even get recognized by adb nor odin. Its the strangest friggin boot loop I have ever seen. When the vibrant screen goes blank then the strange unreadable screen comes on for about 2 seconds and then the vibrant screen comes on and thats over and over. I do have a hardware locked phone so I guess I will have to screw with it when I get home. I did have it in download mode but now I can't even get it to that. Is that USB that came with the phone the only usb that can be used when getting into download mode as I had no troubles at home but I am using my USB from my nexus one at work and its all screwed up.
Did you mean DON'T have a hardware locked vibrant?
I got it about a 2 months ago so I don't know if its locked or not.
Heres what happened in detail.
I rebooted via Rom Manager into the stock recovery.
I installed packages as I have the clockworkmod recovery as update.zip in my 14G sd
I backed up my current Frankin ver3 rom
I erased all userdata and such like I should when flashing a new rom.
I installed the Frankin Final Update
I rebooted the phone like normal and the BAM.
A never ending boot loop that wont even get recognized by my computer.
I cant even plug it into charge as it won't stop bootlooping. the
battery charging icon comes up but then it goes to that funky ass
screen and back to the charging icon. when I unplug the charger it
switches to the Vibrant screen and then the messed up screen. I
really think its bricked as its gotta be the boot image that is
screwed up.
I am very sorry if I am wasting your time on this as I do know how to
properly flash a rom on a phone but this phone is not like my G1 nor
my Nexus. Its about as flaky as a phone can get in my opinion and had
I known it was this flaky I never wouldve gotten the damn thing. I
guess I am going to Tmobile and tellin them the OTA update did this as
there is no way in hell to tell. Not even the splash screen comes up.
Its really bricked.
I just wanted to say that this website and you all developers are the BEST people I have ever followed. This is the very first post I have made and I really do think I f--ked big time. No matter, what you all have done for the G1 and Nexus blows my mind. I never owned a iphone and never will and I think I might say the same about this vibrant. Getting the Nexus bricked is nearly impossible but this Vibrant is to damn confusing and with the lag fixes and crap that I am leary about goin to the store and replacing mine with a new one. Wish me luck.
You may want to try loading Eugene's Froyo Rom that does not brick. Once that is done, try and install Frankin Twiz.
I tried and when the computer won't even read the connection all is bricked. good news though, I went to the tmobile store last night and showed the guy what happened after a OTA Update. he was totally understanding about it. He said it was the white screen of death and that I will have another shipped out the following day. Thanks again for all your help and especially the moderator for putting up with my crap. You all are the bomb-diggity.
I always just boot into recovery and flash say Vibrant7 that always seems to work for me. From there I flash whatever other rom I want.
Recovery meaning
Hold down your Vol + and -
Push Power.
Actually I get scared that I might screw things up by entering recovery through clockwork ( laugh at that now huh) so I always went to the stock recovery and updated my packages with the clockwork recovery file that was named update.zip. I think I had a issue with my phone from the get go as it never would enter download mode unless I was connected to only my samsung charger and no others. I tell ya it was a strange phone and to top it all of the tmobile dude showed me a g2 they had in stock. Nice phone I tell ya but it ain't no Nexus one. Thanks again for all your help guys. Keep the little green dude alive.
Ok, so before the general populace of the forum, looks over this post thinking it's some noob who cant read through the forums to solve there own problem, i would like to say thanks in advance to anyone who can seriously provide some help.
Problem is as follows:::
1,)Phone is working fine using mini-winmo+cyan droid
2,) -PROBLEM- My android stops working, so now im stuck using a lite version of winmo
3,) Tried formatting the sdcard with the lite version winmo built in sdcard formatter, doesnt solve anything, dont exactly know what i was trying to solve with this step.
4,) I decide to get a nice fancy version of winmo, figured it would be as easy as just flashing it once n done.
5,)Decided on going with Ozrom, looked the best at the time.
6,) Run the ruucustom as admin, everything goes fine.
7,) -PROBLEM- after flashing the first boot leaves me stuck on the bootscreen.
So after all that i took the advice and tried to get back to the stock Tmous ROM, but as im typing this im still stuck on the Stick together screen, and also just for a control group i downloaded the latest HD2 cell winmo rom release, and that left me hanging on there version of the boot screen.
Same problem, different roms.. stuck on the loading/boot screen.
But, with the stock rom after playing around with removing the battery, simcard,sdcard and what have you i got the stock rom to boot!!!! I was so excited, i skipped the "How to use the on screen keyboard" tut and was typing in my email info when the phone reset on its own and all my hopes went down the drain... hopefully i will get some help on the issue, and like i said previously in the first paragraph i appreciate any and all help.
thanks.
---UPDATE---
Phone is on and working, intermittently.
When i plug the phone into the charger and wait for the amber light, it will boot up and actually enter into windows, now heres the kicker, removing the charger and using the phone will result in the phone turning off and restarting itself, hanging on the stick together screen.
Removing the battery, and replacing the battery after i push all the buttons, the same way you would power cycle a TV remote, and then connecting it to a charger is the only way ive been able to maintain the operation of the device.
Any ideas?
Try doing task29 reinstall winmo Rom of choosing.. see if that helps.. also I flash everything from bootloader. Also check battery pins make sure they aren't bent..
Sent from my Mytouch HD2
Hello everyone.
I ran into a serious mishap with my brand new work phone. I was handed a HTC radar c110 with Windows phone 7.5 to work with, but the phone had a little issue with calls and I decided to do a factory reset to see if it would sort it out.
So I searched on how to do a factory reset, and took a quick run to the bathroom before I could complete it. But my friend decided to finish it off for me, and somehow mispressed some button I guess, because a screen saying "Omega system loader menu" came up instead, with "FFU method" and 2 options, "MTPz" and "TFTP protocol". She took a blind guess at TFTP protocol, and when I came back the phone wouldn't turn on, it keeps resetting every few seconds and only says "TFTP protocol" on the bottom of the screen. Sometimes an image asking to connect the phone to the pc comes up.
I have tried the factory reset after this a couple of times, but when the phone restarts, this TFTP protocol image still comes up and the phone won't start. My guess is I have effed up the OS. What do I do now? Any guess? I don't want to go to my new job on monday and say that I screwed up the phone they gave me yesterday :S.
Any help is very appreciated. Thank you very much.
EDIT: I can get to USB host mode screen (white screen with "enter usb host mode"), and the white screen where you can "image crc" and "factory reset", not sure if it's called bootloader screen? I'm pretty sure I can get somewhere from one of these screens, but I'm not familiar with rom flashing and bootloaders at all.
EDIT2: I have been investigating further and I can now access the bootloader mode (the factory reset one), update mode (the omega system loader one) and usb host mode. I just need to figure out how to flash a rom (preferably an official one, as it's a company phone) into it now.
EDIT3: I got it fixed, not really sure how, but trying different things ended up booting the phone as normal. I am back to having the same problem as before though, but better than having a bricked phone I guess.
any idea what the solution ended up being?
I think reverting back to my original stock rom might be the answer for me, how did you do it?
I've just managed to do the same..
Any help as to how to sort out this issue? TFTP Protocol appears at the bottom of the screen with all the other symptoms referred above.. PLEASE SOMEONE HELP.
I got a new xperia active st17i yesterday, it was on gingerbread fw.
I used flashtool to unlock the bootloader. I reset the phone but it hung on the sony logo, which was odd. (I have unlocked and flashed around a dozen xperias and this has never happened). I pulled the battery and turned it back on and it boot looped on the sony logo. (left it for several minutes to be sure). Every time it was switched on after that the screen powered on but remained blank.
I flashed the Rage kernel for GB. Turned the phone on and the sony logo came up, went bright, and I got into CWM recovery ;0) all good I thought. I rebooted the phone. It started up, the sony logo came up, went bright, the animation started but then crashed/hung. I left if for a few minutes and nothing, so I pulled the battery. After this, no screen function at all, no back light, completely dead. ;0( When I power on the phone it vibrates and after a few seconds the front led flashes blue and goes out.
Fast boot works, Flash mode works, Flash tool lets me lock and unlock the phone, flash kernels (rage/X-kernel and Lupus) and ftf firmwares ... S1 tool sees my phone, pc companion updates the phone perfectly, but still no screen.
I read the other ST17i bricked threads here and looked at trying the Wotan server method but the phones date code is not covered, its newer than the ones Wotan cover (maybe an issue?).
I have not idea right now, apart from I have hard bricked it somehow. (searching for 'st17i dead screen' gives a few results from Sony's service forum with similar sounding phone activity, with no resolutions). Searching for bricked st17i all relate to soft bricked devices.
As the phone is brand new, I am not sure about the bootloader issue, is it still covered by warranty? The phones current state is locked and fully updated via pc companion, as it was out of the box.
Any advice and help will be greatly appreciated!
Fixed!!! ... (see edit)
I started from 100% scratch. I use an old laptop with winxp to do all my phone work. I did a factory reset on it (begrudgingly) and reinstalled everything*. ADB, flashtool, drivers/kernels etc. (Its now working a lot better I have noticed).
Bear in mind my phones state was factory stock ics 4.1.B.0.587 and locked.
I unlocked the phones bootloader in flastool, it turned on?! Resurrected.
I flashed the ics rage kernel and installed a custom rom, backed up x2 ;0) I AM HAPPY :0D
I honestly tried everything methodically beforehand, hence my post!
*Is it possible to install a corrupt zip? I noticed when downloading files that some were showing as downloaded but were not the correct file size. I only noticed this when grabbing a kernel file, its size was around 6.7mb but the file I had on my desktop was 633kb, it unpacked and came up with the correct size of 6.7mb? (downloaded on my main work laptop with windows 8.1). I had so many bits and pieces on my xp laptop, swapping files from usb pens etc I will assume this could have been my issue!
lol... I must have spent near to 6+ hours reading about tespoint method flashing, TA restoring/backup up, and a whole range of other bricked device issues... I am educated a little bit more now, in more ways heheh...
Update....
The phone worked for about 30 minutes and then a blank screen again. No CWM, because of blank screen. Had fastboot and flashmode still.
So from scratch again, I relocked and flashed with original ftf CE (I have two CE ftf's of different sizes (will need to do homework on these)). The phone was still dead? When plugged into my pc (tried all three USB ports), sometimes when in fastboot/flashmode the device keeps connecting/disconnecting randomly, which is definitely wrong. Possibly my problem is a bad port or maybe the micro usb cable, or loose connection somewhere? Irdk? So now I tried a brand new sony, original, cable and all seems fine again. So, used flashtool to unlock, flash kernel, get to CWM, use my backup and the phone is working again.... but for how long? There's definitely an issue with the ftf files (mabye something to do with my corrupt file size problem? Will go to another place to grab these from and if the phone goes off again will try). odd.
**last edit**
The phone is now running okay. I had a dud battery, which I was using/swapping between several phones that I was returning to stock. It was showing 100% charged but upon disconnecting USB the phone died. Took me the best part of two days to figure that one out... I know! (I'm very busy). So it was possibly the bad battery all along!
Hi guys, sorry if I posted this at the wrong place.
I have a Lenovo s860 and it went into a bootloop. It was stock and all so I thought that I can have my files recovered if I just bring it to a service center so they can get the files first before wiping it or maybe even fixing the bootloop without wiping the device. Well, the thing is, the guy at the service center screwed up and now, when I try to turn it on, I still see the boot screen (Lenovo, powered by Android) but the next screen is like an television with bad signal.
I'm familiar with rooting and flashing ROMs, I've tried it on my Galaxy S2 (yeah I know, it was way back), but I think things are still more or less the same: I need to be able to boot into recovery mode in order to root the device. However, when I tried the Power Button + Volume Up, or any combinations of the Power Button and the Volume Buttons, it just goes straight to the dead screen, I get no response whatsoever.
I also tried to check if adb can detect it, however, it didn't seem to be able to do so. I'm using a MacBook Pro so I know I don't have to install any drivers, I also code Android Apps so I have a background on this.
I think my only option would be to flash the ROM on this dead device but I don't know how to do that. I've also seen some posts that suggest doing some things (I forgot the specifics) while the battery is drained, so what I'm doing for the mean time is to leave the phone open and let it drain which might take ~2 days.
Does anyone know how to flash a ROM on a bricked device? Thanks for any leads.