Well I was running the super dark rom + stupidfast kernal and everything was running great, until i wanted to try stupidfast 1.1.4 and i noticed that it said BLN was disabled by default and followed the link to flash a kernal (had no idea that it was a kernal and that it wasnt meant for our phone) long story short. My phone is stuck at the samsung boot screen i downloaded odin3 and downloaded all the files needed to restore, however everything i do results in the phone still being stuck at the samsung screen then rebooting over and over again
****UPDATE****
FIXED GO TO POST #12 to see how!
Well I was running the super dark rom + stupidfast kernal and everything was running great, until i wanted to try stupidfast 1.1.4 and i noticed that it said BLN was disabled by default and followed the link to flash a kernal (had no idea that it was a kernal and that it wasnt meant for our phone) long story short. My phone is stuck at the samsung boot screen i downloaded odin3 and downloaded all the files needed to restore, however everything i do results in the phone still being stuck at the samsung screen then rebooting over and over agai
Well I was running the super dark rom + stupidfast kernal and everything was running great, until i wanted to try stupidfast 1.1.4 and i noticed that it said BLN was disabled by default and followed the link to flash a kernal (had no idea that it was a kernal and that it wasnt meant for our phone) long story short. My phone is stuck at the samsung boot screen i downloaded odin3 and downloaded all the files needed to restore, however everything i do results in the phone still being stuck at the samsung screen then rebooting over and over again
The stupidfast 1.1.4 kernal was meant for our phone.
It sounds like all you need to do is cold start your phone in download mode. Make sure you have the correct (samsung galaxy s) drivers on your computer.
1) Turn off phone
2) Pull battery and USB out
3) Hold volume DOWN while reconnecting USB
4) Continue Holding volume DOWN and press the power button
(you may now put the battery back in)
You should see a big yellow triangle, this is download mode. From here you can use Odin to flash back to stock. Also, make sure you are flashing the correct image via. odin. We had a guy awhile back who accidentally flashed the stock mesmerize image and his phone really was bricked.
That last sentence brings a smirk to my face for some reason
I think someone needs to come up with a theme that makes the phone look like a brick
chrisexv6 said:
I think someone needs to come up with a theme that makes the phone look like a brick
Click to expand...
Click to collapse
or at least a boot animation of a brick being dropped by a flying android that explodes once it reaches the bottom of the screen.
Sent from my StupidFast, SuperDark Fascinate.
After i flash the stock-i500-recovery.tar.md5 through odin and go to the recovery menu and hit apply sdcard:update.zip it gives me this error message:
E: failed to verify whole-file signature
E: signature verifcation failed
Installation aborted
anyone know what this means or if im supposed to be seeing this?
sounds like you still have the update.zip that clockwork creates on your phone but your not rooted (kind of a guess here). I would flash EVERTHING back with odin, remove your SD Card (where the update.zip is) and just boot the phone to see if it gets you to a setup/home screen.
nmyeti said:
sounds like you still have the update.zip that clockwork creates on your phone but your not rooted (kind of a guess here). I would flash EVERTHING back with odin, remove your SD Card (where the update.zip is) and just boot the phone to see if it gets you to a setup/home screen.
Click to expand...
Click to collapse
tried that and the phone still continues to just hang at the samsung screen and continuously reboots over and over. and when i tried the update.zip it says there's no SD card inserted (obviously since i took it)
Try flashing the odin recovery file. It's in this thread;
http://forum.xda-developers.com/showthread.php?t=782204
It worked for me when I got that error.
GOT IT TO WORK!!!! YES ALL THE BLOOD, SWEAT, AND TEARS PAID OFF!!! If anyone EVER runs into this issue please read this thread:
http://forum.androidcentral.com/fascinate-roms-hacks/44476-bricked-phone-need-help.html
Related
I was wondering if someone can give me a hand here.
Galaxy S Fascinate, I was playing in odin and tried doing a nand dump. It just sat there for awhile and never completed. So I disconnected the cable and attempted to put in the battery and reboot normally.
However it just goes to a screen that shows a phone, a yellow warning and a computer. Assuming odin did not reboot the phone therefor did not close the connection.
Is there something simple I'm missing...
I am rooted running 2.1 update1 and also have clockwork recovery!
I got it back..
What I tried that did not work. Restoring boot through clockwork recovery and a full restore as well.
What worked. Just simply re-flashed clockwork mod through odin. I'm pretty sure I just needed that reboot command.
For future reference is there a way to send a reboot only command through odin?
This happened to me once.
To fix it, I unplugged the phone and removed the battery.
Then, I held the down volume, plugged it in, then inserted the battery.
I got the download mode screen, Odin saw it and I flashed as normal.
[tapatalk on android]
egg_head said:
This happened to me once.
To fix it, I unplugged the phone and removed the battery.
Then, I held the down volume, plugged it in, then inserted the battery.
I got the download mode screen, Odin saw it and I flashed as normal.
[tapatalk on android]
Click to expand...
Click to collapse
Thanks Guys!!!!! Back to... oops spoke too soon. Force close loop....launcher problems....Restoring backup with CW....BTW @egg_head how did you figure that out!?....still restoring backup...SCORE, GOLDEN!!!
A message popped up from Samsung to install an update (I had been pressing cancel for the past week on this update). It says click OK to reboot and apply update (something along those lines) so I do. Now I am stuck with a tablet that won't boot. If I hold the power button it says "Samsung Galaxy 10.1" after about 12 seconds, but then it goes away and back to darkness. Nothing else. Holding power and volume up does nothing.
Someone know what is going on and have any idea how to resolve?
The best way is to restore any backup you have from cwm recovery. Else grab a stock firmware and flash it with ODIN or if zip than CWM recovery. For luck, try clearing cache and data in recovery, first!Perhaps it may work saving you all fuss of flashing a firmware.
I cannot even boot that far too get into recovery. And I just noticed that although I can't boot, the backlight is on (on a solid black screen).... wtf
You can't hold volume down and power button to enter recovery?
Nope. I plugged into my computer and for some reason with the USB connectd it let me enter recovery. Flashed a backup and rebooted, but now I have no wifi... im confused.
it occured once to me when i tried to overclock, it never worked except when installing a new rom... Try to root the device and then install a new rom
OK, was a helluva night messing with ROM and kernel installs... I have yet to go back to completely stock (that's next up tonight, unfortunately), but I installed Starburst ROM and the Wifi still didn't work so I then installed pershoot's kernel and now when I boot the screen is extremely distorted kind of like this: http://t1.gstatic.com/images?q=tbn:ANd9GcTsKa5IoQxnesGdUjykWDDggoQZ38yZ2VXSgPAQ09NOCnETzl9-
As a side note, when I say the wifi is not working, it still shows all networks and allows me to connect just like normal. However when connected no apps can access the network...
Can someone point me to a thread on how to revert EVERYTHING back to stock so I can start fresh? TIA!!
http://forum.xda-developers.com/showthread.php?t=1171089
Should have all the files you need. From where you are now I would flash the stock OTA 3.1 or TW then flash the stock recovery and do a factory reset from that recovery. That should get rid of the garbled screen.
Thanks buddy. On my way to grab the files now
I heard the update was pulled as it sometimes rewrites the bootloader improperly. You might need to send it in, unfortunately.
Hello XDA-devs forums,
I'm having an issue since yesterday.
I have rooted my Huawei Ideos X5, and it ran fine for a day or so.
However, when my battery ran out it shut down into a completely blue screen.
When I tried booting it again, this just showed me a blue screen as well.
Now, I fixed this issue by connecting the phone to my PC after booting it with the Vol+ and Vol- pressed.
(So you get the pink/purple screen)
However, when I opened the phone on my PC, all I saw was a "239 MB" "empty" space, and it should have ~2GB..
I placed a backup copy I saved of my "image" folder in that 239 MB storage, and it booted.
However, today I hooked it up to my PC again to see if it magically changed..
And I couldn't access the 239 MB space anymore.
When I tried fixing the issue with a reboot of the phone, that just caused it to get stuck in a booting loop.
So now I'm stuck with a phone that keeps trying to boot itself,
and I can't access it on my windows PC.
I can, however, access 4 different folders of the phone on my linux notebook.
Now, my question is: can someone with a good understanding of problems like these please help me out?
I'm getting kind of fed up with it, as I've only got the phone for 2 days now.
Thank you in advance, and thank you for taking the time to read this.
Have you tried removing the battery for 5 minutes and then putting it back in?
After this, what happens when you press VOL+ and Power?
How about if you press VOL+, VOL- and Power, without the USB cable?
Hello Katu, thank you for posting.
Regarding your questions:
Yes, I have tried to take out the battery for 5+ minutes- it didn't change anything to the situation unfortunately..
If I press VOL+ and Power at the same time, the device boots into recovery mode.
In this I have tried to format the device in order to reset it to factory defaults, but this did not help either.
When I press VOL+, VOL- and Power, the phone boots into the pink/purple screen.
Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]
I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.
PlanDreaM said:
Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]
Click to expand...
Click to collapse
Well, I used an original ROM:
U8800 V100R001C00B136(Overseas General version)
And that resulted in the boot.img being corrupted, so I can't even overwrite that anymore.
Also, this is what I see when I hit VOL+, VOL- and Power at the same time to boot into safe mode, and connect it to my PC.
img69 [dot] imageshack [dot] us/img69/244/10101191548pm.png
julle131 said:
I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.
Click to expand...
Click to collapse
I installed the official B136 rom, and after it rebooted, it would just hang on a black screen.
(it used to show the IDEOS or Android logo when it booted)
Hmm mine came with this Rom
U8800 V100R001C00B135SP01 ( general )
Looking at your name you're from the Netherlands ( so am I )
where did you get this 136 version from ?
I would try to put this one on it
You have to put the 'dload' folder into the root of your SD Card,
then boot into boot-loader, after that it'll automatically flash back to the stock Rom.
1 Format SD card
2 On the SD card, create "dload" folder
3 Put the unzipped Rom into "dload" folder
4 Then boot to bootloader (pink screen)
Yes, mine came with that version as well.
However, I couldn't find it anymore and thus downloaded the version I said earlier.
Also, I did everything as you described, except step 4.
You have to boot to recovery instead of bootloader. (VOL+ and Power)
Anyways, I managed to get ClockworkMod's recovery.img on my phone,
and from there on install a custom ROM on the phone, which magically got it working again - even though it didn't work earlier.
Thank you for reading my thread and taking the time to reply to it.
My issue has been resolved.
just for the record, flashing a stock rom is different from flashing a custom rom..
the 4 steps described by Gman2oo6 is the correct way to flash a stock rom (and it is written clearly in the document that is in the stock rom zip file)
[edit]
step (1) is not a necessary step though..
Yeah, I noticed that.
What I did was format my SDcard with FAT32,
and put a custom rom (update.zip) on the SDcard.
I then booted ClockworksMod Recovery and installed the custom rom from the SDcard.
When I tried installing the stock rom, I just followed the PDF file's instructions that came with the stock rom.
hey i udated to GB 2.3.4 (official)and i didnt like the it cuz the wifif ddnt work and the bluetooth also the DATA so itryed to downgrade to 2.2.2 original official and it did the 2/2 steps intalled and when it restarted it did not want to turn on all that happened was it vibrated and thats all so i left it on like that and when the battery died i plugged it in to the AC and the LED turned on red and the touch kkeys also but not the screen so i really NEED help!
Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started
i tryed it
nope nothin good happened all that happens is a blank screen with nothin on ,LED is off and the touch keys are off. it justz vibrates and when i put the battery it turn the LED on to red and the touch keys turn on but then like 5 min later the LED and keys turn off
astewart said:
Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started
Click to expand...
Click to collapse
ok heres what i did i wanted to upgrade my phone to the newest version GB 2.3.4.So what i did was download the update and i followed the installation steps i successfully updated to Gb 2.3.4. so like i was checking how it look and the new feature but when i wanted to go on the android market i went to setting and turn on the wifi and it said Error and then i tried the Bluetooth and it said Error also so then i put my SIMs card in and i was like imma use DATA then and when i restarted my phone it had service but no HSPA+ or Edge or GPRS so like i just hatted my phone from their so then i was trying to root it but iddnt know how to do that so like i read this website and i got the UPDATE.APP or 2.2.2 AT&T did the same steps of the installation of BG 2.3.4 and it went to the process and 1/2 stepp good it passed and then 2/2 also passed it installed it and when it said Successively Installed it said Restarting and the scrren turn of and it vibrated and thats all that happened and i left it like that for the whole days and nothing happened
Do u got any idea?
When i connect it to my laptop it says installing drivers .then its says sucesfully installed drivers ready to use. so then i got to Device Manger and i check what has been installed and their it said USB Human interface device and HID-compliant device WHAT DOES THAT MEAN??
Not sure about the HID (human interface device) probably just the way windows sees the device for interfacing with it. With regards to the not booting I have read a lot of people saying that you need to factory reset and clear cache after the upgrade/downgrade. With the phone off, turn it on by long pressing volume+ and power on button till you get the blue recovery screen and from there you can reset factory/ data and also clear the cache. from what I see this should clear up the problem and start up. Please read this thread, it may help you somehow..... http://forum.xda-developers.com/showthread.php?t=1420728
Hope this helps a little
U mean Boot recovery and imma try it and thanks ill check it out
Sent from my MB300 using XDA App
all that i know is that if u customized your partition, it'll bootloop,
so go back to stock-partition ^^
How do I do that got like the steps or video?
Sent from my MB300 using XDA App
when i downgraded to 2.2.2 i installed this V100R001C00B138SP04CUSTC185D002
http://forum.xda-developers.com/showthread.php?t=1251250 got it from that link
Looks like you are not having much luck. Did you try to factory reset?
astewart said:
Looks like you are not having much luck. Did you try to factory reset?
Click to expand...
Click to collapse
well how do i do that do i need to got to the purple/pink screen or bot recovery cuz i cannot access that my phone doesn't do anything pretty much
Okay so I guess I didn't read something and bricked my phone ...i was trying to install clockwork recovery from here: http://wiki.cyanogenmod.com/wiki/Samsung_Vibrant:_Full_Update_Guide
Now my phone never boots. I get the regular start up jingle and boot animation, but then nothing. Sometimes the buttons light up, but the phone never starts.
I used Heimdall Frontend on unbunto32 bit to flash the zImage vibrant kernerl file for clockwork recovery installation.
Could i just install the original Vibrant kernel to restore my phone?
Thanks
I'm actually in the same boat here, don't know what went wrong, any suggestions?
Easiest solution? Go into download mode and ODIN back to stock. Instructions available in the developer section.
kaintfm said:
Easiest solution? Go into download mode and ODIN back to stock. Instructions available in the developer section.
Click to expand...
Click to collapse
Yeah i tried that with bay_wolf's AIO program. It looked like it worked, but now continues in endless boot cycle. I don't even get to the gingle anymore, it just boots to the Vibrant-Samsung logo...repeat.
http://forum.xda-developers.com/showthread.php?t=1319802
legend_jo said:
Okay so I guess I didn't read something and bricked my phone ...i was trying to install clockwork recovery from here: http://wiki.cyanogenmod.com/wiki/Samsung_Vibrant:_Full_Update_Guide
Now my phone never boots. I get the regular start up jingle and boot animation, but then nothing. Sometimes the buttons light up, but the phone never starts.
I used Heimdall Frontend on unbunto32 bit to flash the zImage vibrant kernerl file for clockwork recovery installation.
Could i just install the original Vibrant kernel to restore my phone?
Thanks
Click to expand...
Click to collapse
I hope you or the guy after you aren't the one I've been trying to help on G+.. if so I said don't use heimdall
Remove the battery, plug in usb to phone and computer, and while holding both volume keys insert battery, if it goes to download mode you're golden.
The post just above this one explains how to get into download mode and flash back to stock with ODIN.. Odin works flawlessly every time unless someone screws up, and I have seen too many issues with heimdall. If you don't have windows you can run odin in a virtual machine on mac or linux if you install the usb drivers into the directory structure.
Me, too
I also meet the same trouble with you, I don't know what's wrong and how to solve it. That really makes me crazy！
Hello there,
I'm using a vodafone bloated version of the i9505 and wanted to flash CM or a clean stock 4.3 because I don't want to wait for vodafone to release updates.
I downloaded Odin and CWM for my device and followed the instructions correctly. All went as it should. But when I tried to boot into recovery, I got the boot logo and in the upper left corner it said in small blue text "booting recovery..." but it would just give me a black screen after a while and restart into normal mode. I tried flashing different versions of CWM via Odin. My next approach was to root the phone with cf auto root which succeeded. After that, I tried all of the above again, and still didnt get any results. I even tried the Cyanogenmod desktop intsaller and after a while it said: "cant communicate with your phone"
Please help!
I believe I had the same issue once. When you flash the recovery true Odin, make sure Auto Reboot is not selected in Odin. That fixed it for me. After the flashing is done, you need to remove the battery and insert it again. Then it should probably work.
Lennyz1988 said:
I believe I had the same issue once. When you flash the recovery true Odin, make sure Auto Reboot is not selected in Odin. That fixed it for me. After the flashing is done, you need to remove the battery and insert it again. Then it should probably work.
Click to expand...
Click to collapse
I tried what you suggested, and hat the same thing as before but after the second restart I kept holding the volume up key as someone suggested on the internet and got a CM boot screen with on screen buttons like in CWM. after a brief pause I got a violet screen with nothing on it. I am now very confused and have no idea how to fix this. The phone itself can be booted normally though.
It seems to be that something remained from the failed CM installation.
Any suggestions?
What version of Odin do you use? Try version 1.85.
TWRP
Lennyz1988 said:
What version of Odin do you use? Try version 1.85.
Click to expand...
Click to collapse
Hello again, I flashed TWRP and it worked! I had to hold the volume up button even after the logo with the small blue print showed up in order to boot into recovery. Still couldnt get it to boot into CWM though. But thank God there is no need for that anymore!