Phone is stuck in airplane mode. Long story short used abd to install stock mbr and kernal. phone is all good now only problem is i cant connect to verizon. when i try to make a call it says i need to take it out of airplane mode. when i uncheck this box, it says "enabling network connection" but never connects to verizon. any ideas?
Did you program it after restoring everything? (*22899)
Boushh said:
Did you program it after restoring everything? (*22899)
Click to expand...
Click to collapse
when i do this is tell me that i am in airplane mode and i cant get out of airplane mode
Realized that when i flashed back to stock with oden i flashed over using "phone" and not "pda". i will paypal someone $$ for a fix to this.
have you tried again using pda?
bomber889 said:
have you tried again using pda?
Click to expand...
Click to collapse
yes and with no luck....i think i need a file to reload using "phone" in odin
hey, i did the exact same thing. I was told by numerous forum veterans that it could not be undone since nobody has a modem.rar for our phone (which would be what you needed to overflash using the phone button). Basically, take it to verizon and get a warranty replacement, don't tell them about odin.
andrewblanejr said:
hey, i did the exact same thing. I was told by numerous forum veterans that it could not be undone since nobody has a modem.rar for our phone (which would be what you needed to overflash using the phone button). Basically, take it to verizon and get a warranty replacement, don't tell them about odin.
Click to expand...
Click to collapse
I found the full modem.bin here: http://www.multiupload.com/81369CIB0A
Have not tried to flash it but at this point it may be your best bet.
I too have the same issue. I have downloaded the 189meg image file and it is asking for a password Can not unzip. Do you have the pass?
There is a fix in this here forum the only problem is you will not have the ability to send text. Pick your poison, have a nice PDA, or a phone that can't send text, but it can be fixed
Sent from my SCH-I500 using XDA App
nitroxeno said:
I found the full modem.bin here: http://www.multiupload.com/81369CIB0A
Have not tried to flash it but at this point it may be your best bet.
Click to expand...
Click to collapse
That looks like a us cellular file. Bad idea
Sent from my SCH-I500 using XDA App
I was thinking there is a fix in this forum. Could be wrong however. Good luck.
Sent from my SCH-I500 using XDA App
ksizzle9 said:
There is a fix in this here forum the only problem is you will not have the ability to send text. Pick your poison, have a nice PDA, or a phone that can't send text, but it can be fixed
Click to expand...
Click to collapse
Or, uh, update to fixed GPS and calls with regular headphones...
There's a solution on IRC.
Sent from my Voodoo-powered Fascinate via XDA
So how does one recover from this?
We have a Fascinate here that's stuck in airplane mode and won't register. This is after trying to apply Clockwork and then putting on a ROM called Super Clean.
WIFI works, but all cellular seems not to work.
clickwir said:
So how does one recover from this?
We have a Fascinate here that's stuck in airplane mode and won't register. This is after trying to apply Clockwork and then putting on a ROM called Super Clean.
WIFI works, but all cellular seems not to work.
Click to expand...
Click to collapse
Some say a reboot fixes it...in my case however I had to wipe and reflash
Mine was stuck in airplane mode at one point. I think I traced mine back to reseating the SD card. It started working after I powered it off, removed battery and SD card, replaced SD card, replaced battery, and then powered on the phone.
grrrr : /
Arixsin said:
Mine was stuck in airplane mode at one point. I think I traced mine back to reseating the SD card. It started working after I powered it off, removed battery and SD card, replaced SD card, replaced battery, and then powered on the phone.
Click to expand...
Click to collapse
this just solved my problem with the epic running Frankenstein
Well, A) read the instructions next time.
B) You're boned.
Samsung Fascinate, Verizon
EB01 Superclean 2.4
Kenesis' TransMyst GBKB (EPIIIIIC)
Mob87's Honeycomb Theme
Stock Kernel
My fix for stuck airplane mode
I had same problem with phone in airplane mode. Galaxy S been rooted a month now. Left phone on desk and when came back in about an hour, it was in airplane mode. Bluetooth and wifi worked, but not cellular. Tried everything - reboot, pull battery, sd card. Did not want to reflash. Finally tried wiping cashe partition from recovery mode. It fixed the problem! Hope this helps some of you.
Flight Mode FIX
Reboot cwm recovery go to advanced permissions then wip delvik cache then wipe cache partition.. You will not lose anything on phone an dont get scared reboot will take a min like when you reflash. hope this helps you!
Related
I did all that rooting crap. Now when I press the power putton, it flashes the "Samsung Vibrant" Image, then plays the tmobile tone, but no "S" image appears. And it stays black. How do I fix this?
define "all the rooting crap"? Did you flash a Voodoo Rom and try to flash something else on top of it?
There is NO way to tell you what you need to do unless you tell us what you did.
But based on what you have described.. Gonna say u are SOL.
Use odin to flash stock rom then start over. I have been stuck on that screen a couple times. Lol
Sent from my SGH-T959 using XDA App
Truth be told
Anthony is right. i had this issue earlier this week when trying to flash a mod to my phone. Odin is the only choice at this point.
This has happened to me twice, most recently after "fixing permissions" in the oclf market program. Both times I've rectified by booting into recovery and "reinstall packages". Both times I also removed sim and sd and after a couple repetitions of package reinstall it comes back to life. Maybe dumb luck, maybe not, worked twice...
Sent from my SGH-T959 using XDA App
Correction, fixing permissions in Rom Manager...
Sent from my SGH-T959 using XDA App
Also...My Vibrant Wont Turn On
Dear All
I am new to this forum and need some assistance. I recently bought a T-Mobile Vibrant from a friend who had brought it with him for the US. I am using it in the Middle East where I live at the moment.
I have been reading a lot in the past few weeks about the Vibrant and almost everything there is to know. It seems there is always more to discover.
Back to the issue at hand. I had been having problems with getting my phone to reboot into recovery mode but I finally managed to do so last night. I wanted to flash my phone with Axura 2.1E, Nero V2 or the Macnut v14, so I can use the the Black Froyo theme on it.
First, I flashed the original firmware (T959...JDF) which I got off your site, using Odin v1.3. That worked as it should. Then I proceeded to follow instructions to download the ClockworkMod from this thread: [RECOVERY] ClockworkMod Recovery for Vibrant (FINAL! SAFE!)
After I copied the CWM file to the Internal sd card, I downloaded Rom Manager, rooted the phone with Z4root, chose the Samsung Vibrant in Rom manager and clicked install ROM from sd card. it rebooted into recover mode (blue writting), I clicked 'reinstall packages', which it did and it rebooted into the ROM recovery mode (green writting). I chose the option to install zip file from sd card, then chose Axura 2.1E and it installed until it said complete.
So far everything was working as it should, or at least that was the impression I got. I am not sure of this next step. It said installation complete, so i chose 'go back', then 'reboot device'. When it went into reboot, nothing happened...just a black screen. It wont start, neither normally, not into any other mode (recovery or download). i plugged it into the charger and not even the battery icon would come up. i assume that it is...'dead' and I just did the impossible. I tried several ways and combinations to get it back to life somehow, but I have a feeling that's it.
Any suggestions, advice, remedies, whatever help...even condolences would be much appreciated..
Much appreciated and all the best to all.
Cheers
What the heck is up with all these HARD BRICKs?
Past few days, I keep reading people who have appeared to truely HARD BRICK their phone.
Meaning they can not get into download mode, they can not use odin, they are truely hard bricked.
What is up with the sudden surge of hard bricks.
This guy sounds like he did everything correct.
Scary.
Ya I've seen a lot of those also... could it be a newer version of the Vibrant? Yes he did everything correctly... he could try a jig.. its only maybe 10 bucks? worth a try at least...
My Vibrant wont turn on
Thanks guys for the reply to my post. I was thinking today that even though I did follow instructions correctly, that I might have missed a step at the end.
My thoughts went to the fact that after the installation of my chosen ROM (Axura 2.1E) was complete, I was given the choice of installing update.zip again, along with some other ones which I forgot what they were and the option to 'go back'. I went 'back' and pressed reboot device.
If the installation was fully complete, would not the phone go into automatic reboot?
Anyways seem like the boot is screwed and I am getting help from a friend to get it back to life again.
Anyone can confirm what to do after I install a 'ROM' successfully. Is there another step afterwards which I must be aware of to fully complete the flash?
Cheers again
Hey I got a old stock rom from off one of these forms off xda... for my samsung vibrant... After i flash the rom odin said reset and the vibrant never turned on.... its been like this for a day now... the battery sign dosent even turn on... what can i do..
hellobitchdog said:
Hey I got a old stock rom from off one of these forms off xda... for my samsung vibrant... After i flash the rom odin said reset and the vibrant never turned on.... its been like this for a day now... the battery sign dosent even turn on... what can i do..
Click to expand...
Click to collapse
Get into download mode try again,
if not try getting the files from a different source
Sent from my SGH-T959 using XDA App
Sent from my SGH-T959 using XDA App
Hey everyone...
I need help.. And its not my phone nor do i have it in my possession... Kinda troubleshooting over the phone... My nephew got a samsung vibrant... Got his phone rooted and had Darky's v7.7 Gingerbread Edition rom running... It booted up ran for a bit had a LOGSPROVIDER error stopped unexeptedly message....
He shut the phone off then rebooted and it wont boot past the first boot screen... HE also cant get into recovery but download mode works fine..
Possible solutions..?
Well if he can get into download mode the he should just odin back to stock and reinstall the rom!
Sent from my SGH-T959 using XDA App
Thats what I was thinking... Im not familiar with samsung phones.. Whats the purpose of download mode?
Safety feature? I presume..
I find it odd though that it booted fine and was ok until he rebooted and it wouldnt load... Any specific reason that could happen
Nah if you read the disclaimers devs put up it clearly says "i am not responsible for bricking, etc."
So no, there should be no specific reason why your nephews phone won't boot, more unless he was running a lag fix and flashed the wrong zip or whatever then yeah...
But download mode is I guess a fail-safe for samsung if the phone bricks or anything, afterall the vibrant is nearly impossible to fully brick
Sent from my SGH-T959 using XDA App
Thank You for the help...
He opted to call tmo and there sending a replacement.. Then asked him if he bricked the phone... He played dumb.. and said he rebooted the phone and it wouldnt load...
And yes i know about the devs disclosure... Got myself a mytouch slide which just finally got s-off courtesy of ALPHAREV woohoo.. Also have a G1 from back when it first came out.. SO i got plenty of rom downloading under my belt
hellobitchdog said:
Hey I got a old stock rom from off one of these forms off xda... for my samsung vibrant... After i flash the rom odin said reset and the vibrant never turned on.... its been like this for a day now... the battery sign dosent even turn on... what can i do..
Click to expand...
Click to collapse
This same thing happened to me. I read about making a jig, yeah right. So I continued for the better part of three hours plugged into my computer with data cable continuing the same motion that I would to get into download mode. And finally I got the download dude. I used the s1.odin somthing .pit file I think it was the first .pit to come out. Not the 512.pit Along with the first .jar. Anyway keep trying to get into download mode even with a black screen, can be done.
Sent from my SGH-T959 using XDA App
Installed the DoW kernel over Bionix-v and wound up in a boot loop, unable to get into recovery, but I was able to get into download mode. Tried using ODIN to flash back to stock, but it won't boot past the 1st Vibrant splash screen.
The ONLY rom I've been able to boot is Eugene's JK2+2e Froyo ROM, but it's not recognizing both the internal and external storage (shows unavailable). I'm assuming this is due to ODINing with voodoo enabled, so I tried flashing one of SuperCurio's voodoo kernels on top, but that seemed to have no effect.
I've tried using Eugene's Froyo that doesnt brick and then downgrading to stock JFD, but it still refuses to boot, same as if I negated the Froyo step. I'm fairly lost as to what my next step should be besides randomly changing settings, but I dont want to get to a state where I can't enter download mode.
ANY help anyone can provide would be amazing and greatly appreciated, and I can of course provide any additional information that would be helpful.
Odin needs time. Odin is your solution.
Sent from my SGH-T959 using XDA App
Thanks for the response, but could you be more specific? I'm aware that ODIN is the solution, because I'm unable to flash anything in recovery.
torturedsoul802 said:
Thanks for the response, but could you be more specific? I'm aware that ODIN is the solution, because I'm unable to flash anything in recovery.
Click to expand...
Click to collapse
Sure. If it was me id download an older odin version. Just try it. Id also go back to stock.
Remember to back up a program to root.
I still use odin 1.3 myself. Works every single time.
Let me know.
Sent from my SGH-T959 using XDA App
Using Odin 1.7 now, I'll try 1.3 and report back on that. The problem is, every time I attempt to revert back to stock (JFD or JI6), the phone refuses to boot, shows Vibrant splashscreen for ~1.5 sec and then shuts off. No boot animations.
torturedsoul802 said:
Using Odin 1.7 now, I'll try 1.3 and report back on that. The problem is, every time I attempt to revert back to stock (JFD or JI6), the phone refuses to boot, shows Vibrant splashscreen for ~1.5 sec and then shuts off. No boot animations.
Click to expand...
Click to collapse
Keep trying. It will work eventually for no reason.
Sent from my SGH-T959 using XDA App
Leave it alone for at least 5 to 10 min on splash screen. Sometimes that takes a while.
Sent from my SGH-T959 using XDA App
mr.orange303 said:
Leave it alone for at least 5 to 10 min on splash screen. Sometimes that takes a while.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
15 max
Sent from my SGH-T959 using XDA App
Would you recommend flashing Eugene's Froyo that does not brick first and then flashing stock on top? Or straight to flash? And should "re-partition" be checked at any point, since the ext4 system needs to be rebuilt to RFS.
torturedsoul802 said:
Would you recommend flashing Eugene's Froyo that does not brick first and then flashing stock on top? Or straight to flash? And should "re-partition" be checked at any point, since the ext4 system needs to be rebuilt to RFS.
Click to expand...
Click to collapse
No to repartition on my end. But u may want to ask about the ext4 going back to rfs. Ive always done it in cwm honestly.
Someone else with more expirience will have to answer that.
But I have never and read it doesnt need to be done.
Sent from my SGH-T959 using XDA App
Tried, still wont turn on on stock, just vibrant screen.
torturedsoul802 said:
Tried, still wont turn on on stock, just vibrant screen.
Click to expand...
Click to collapse
Its not bricked. Keep trying.
Sent from my SGH-T959 using XDA App
mr.orange303 said:
Its not bricked. Keep trying.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
+1. If your phone boots at all it's in my experience 100% recoverable. I own a RIFF box as well so if you brick it dead then I can still fix it... . I'll be getting a video up on ODIN usage for Vibrant/i9000 owners tomorrow. Check out my Boot Logo video on my website for a little bit of ODIN usage to give you an idea. You just need to open ODIN. The put the phone in download mode and plug in via USB. Then select your PIT and PDA file and click start. Then you can reflash stock firmware. PM me as I offer this as a service as well.
Thanks for the reply. Usage of ODIN is not my problem, the problem is that flashing to JFD (whether I use Eugene's Froyo 1st or not) results in a failed boot. The phone shows the 1st Vibrant splash screen for ~2 sec and then shuts off. No process I have tried results in a successful stock boot.
Thinking about trying both of these:
http://forum.xda-developers.com/showthread.php?t=823300
http://forum.xda-developers.com/showthread.php?t=940671
HOPEFULLY, one of these will let me get into CWM or access the filesystem in order to disable Voodoo.
Once again, if anyone knows of a way to revert EXT4 -> RFS through ADB or download mode, please let me know!
Well I have been working on it for a day straight and no luck. I have talked to several people and the phone has readonly partition now so it is ****ed! Nand death! I called T-Mobile yesterday and told them I have know idea why but my phone won't turn on, blah, blah, blah. So they are going to replace it under warranty and it will be here in a few days.
torturedsoul802 said:
Thinking about trying both of these:
http://forum.xda-developers.com/showthread.php?t=823300
http://forum.xda-developers.com/showthread.php?t=940671
HOPEFULLY, one of these will let me get into CWM or access the filesystem in order to disable Voodoo.
Once again, if anyone knows of a way to revert EXT4 -> RFS through ADB or download mode, please let me know!
Click to expand...
Click to collapse
Hey, thank you so much for posting this up. These are great finds. I'd be more inclined though, to just call Tmobile and get another phone. I'm really tired of messing with the phone. I don't have time to be messing with this anymore.
The fact that I can get into download mode may be good news, but it does nothing for me right now. With what we know about bricking and unbricking phones, I've thrown every trick I know at it already. I hope you get it fixed, but I"m not messing with it anymore.
drewdude007 said:
Well I have been working on it for a day straight and no luck. I have talked to several people and the phone has readonly partition now so it is ****ed! Nand death! I called T-Mobile yesterday and told them I have know idea why but my phone won't turn on, blah, blah, blah. So they are going to replace it under warranty and it will be here in a few days.
Click to expand...
Click to collapse
Yeah man, me too. I'm getting this thing exchanged. It's a paperweight right now. My phone is doing exactly the same thing.
Can you recap one more time? You are only having problems flashing a custom ROM? You said ODIN is not the problem so I'm taking it you could flash back to stock if you wanted to?
Size matters.
Hey, I haven't posted in here before, I've been a member for a while, just never had anything to contribute. So I got the whole soft brick problem. I spent countless hours trying to get into download mode. The size of the usb cable matters, I was using an LG Optimus cord, and my buddy tried his blackberry cord which had much more gerth, and BAM download mode everytime no problem. Maybe this might help some of you out there.
Also I would like to say, thank you for everyones hard work. I had to roll back to stock roms, and just got the Froyo.UVKA7 to work. I love it, it's quick, it's got color in the settings menu. I wanted to cry... Everyone that has ever had anything to do with the developement to make Android better. THANK YOU!
Absolutely,
I am having problems with the phone starting up and loading what I flashed.
I flashed JI5 Ji6, and Eugene's non bricking Froyo Rom
These 3 are the only ones I was able to find that is ODIN flashable
Why you ask?
I cannot get into Recovery, but I can get into Download mode. I can't get into any recovery at all. NOTHING. This is why ODIN seems to be my only option.
But regardless of any ROM i flash, my phone shuts off right after the Vibrant screen. No splash screen, no loading, no booting. .Nothing. It just shuts off.
I can't charge it either.
i get a Charging bootloop. HOurglass - battery shows up for a bit, then restarts over and over.
So in other words. it's ****ed.
Hope that explains it sufficiently. if you have any more questions or suggestions, Im open man, Im open.
Help me
connexion2005 said:
Can you recap one more time? You are only having problems flashing a custom ROM? You said ODIN is not the problem so I'm taking it you could flash back to stock if you wanted to?
Click to expand...
Click to collapse
Well, my phone is non responsive to anything I do and I am unable to get into download mode. I rooted the phone using this guide from creepyncrawley (http://forum.xda-developers.com/showthread.php?t=1311081).
For a complete device history:
I later installed a nightly of CM9. Everything worked great for the most part with the various nightly builds. I changed to the UCLD3 leak for awhile without hitch.
I needed something off of my stock rooted rom from the thread above so I did a restore...again no problems with the switch. I did have to fix permissions to open some apps.
I switched back to the UCLD3 leak to test data speeds with plans on switch to the new CM 9 nighlty. I booted into recovery and wiped data, cache, and dalvik. I went to install the CM 9 4/17 rom and it checked the rom and started the install. The progress bar never moved at all and after awhile the screen/phone turned off. Since then, the phone is completely unresponsive. I am unable to get into download mode, the cap lights do not turn on...nothing.
What happened...I have no clue. Is there any way I can fix this with the tools here?
avus_m3 said:
Well, my phone is non responsive to anything I do and I am unable to get into download mode. I rooted the phone using this guide from creepyncrawley (http://forum.xda-developers.com/showthread.php?t=1311081).
For a complete device history:
I later installed a nightly of CM9. Everything worked great for the most part with the various nightly builds. I changed to the UCLD3 leak for awhile without hitch.
I needed something off of my stock rooted rom from the thread above so I did a restore...again no problems with the switch. I did have to fix permissions to open some apps.
I switched back to the UCLD3 leak to test data speeds with plans on switch to the new CM 9 nighlty. I booted into recovery and wiped data, cache, and dalvik. I went to install the CM 9 4/17 rom and it checked the rom and started the install. The progress bar never moved at all and after awhile the screen/phone turned off. Since then, the phone is completely unresponsive. I am unable to get into download mode, the cap lights do not turn on...nothing.
What happened...I have no clue. Is there any way I can fix this with the tools here?
Click to expand...
Click to collapse
This might be a stupid question, but... Dead battery?
Sent from my SGH-I777 using Tapatalk 2 Beta-6
avus_m3 said:
Well, my phone is non responsive to anything I do and I am unable to get into download mode. I rooted the phone using this guide from creepyncrawley (http://forum.xda-developers.com/showthread.php?t=1311081).
For a complete device history:
I later installed a nightly of CM9. Everything worked great for the most part with the various nightly builds. I changed to the UCLD3 leak for awhile without hitch.
I needed something off of my stock rooted rom from the thread above so I did a restore...again no problems with the switch. I did have to fix permissions to open some apps.
I switched back to the UCLD3 leak to test data speeds with plans on switch to the new CM 9 nighlty. I booted into recovery and wiped data, cache, and dalvik. I went to install the CM 9 4/17 rom and it checked the rom and started the install. The progress bar never moved at all and after awhile the screen/phone turned off. Since then, the phone is completely unresponsive. I am unable to get into download mode, the cap lights do not turn on...nothing.
What happened...I have no clue. Is there any way I can fix this with the tools here?
Click to expand...
Click to collapse
You may want to try a jig, if you haven't updated the bootloaders.
Were you switching between these using nandroid backups?
dandrumheller said:
This might be a stupid question, but... Dead battery?
Sent from my SGH-I777 using Tapatalk 2 Beta-6
Click to expand...
Click to collapse
Phone has been plugged in the charger for awhile now...nothing.
AJ Newkirk said:
You may want to try a jig, if you haven't updated the bootloaders.
Were you switching between these using nandroid backups?
Click to expand...
Click to collapse
I only used a nandroid backup for restoring back to the stock rom. For everything else, I used CWM and a zip install.
I'd try pulling the battery and leaving it out for 10-15 mins.
I find it hard to believe that you would brick your phone using a known good .zip file in CWM.
The bootloaders should be intact - so it should be recoverable.
Something else is at play here. Either it is hard locked-up or you have a hardware issue.
I'd also suspect battery or hardware.
Try to get into download mode with the battery out. Use the same sequence, vol+ and vol- then plug in the usb cable. The usb will supply the power. If it won't go into download mode that way then I would suspect hardware rather than battery.
Did you flash ld3 using the one click odin or thru a cwm file?
If a jig doesn't work than the bootloader is most likely corrupted.
10 char this
AJ Newkirk said:
I'd try pulling the battery and leaving it out for 10-15 mins.
I find it hard to believe that you would brick your phone using a known good .zip file in CWM.
The bootloaders should be intact - so it should be recoverable.
Something else is at play here. Either it is hard locked-up or you have a hardware issue.
Click to expand...
Click to collapse
That's what I thought. Like I said, it started the flash but then look like it hung. The progress bar did not move at all. After a bit the phone turned off. What is hard locked-up? I do remember when I first plugged the charger in after the phone died/suspended it did vibrate.
creepyncrawly said:
I'd also suspect battery or hardware.
Try to get into download mode with the battery out. Use the same sequence, vol+ and vol- then plug in the usb cable. The usb will supply the power. If it won't go into download mode that way then I would suspect hardware rather than battery.
Click to expand...
Click to collapse
Phone is basically new. I tried leaving the battery out and holding down the vol keys and plugging into USB. Screen does nothing.
c0ldburn3r said:
Did you flash ld3 using the one click odin or thru a cwm file?
If a jig doesn't work than the bootloader is most likely corrupted.
10 char this
Click to expand...
Click to collapse
As I posted above I only used Odin from the original rooting. Everything else was CWM.
I guess I need to find out how to make a jig and try that as my only remaining option??
Same thing happened to me earlier today when flashing the latest MIUI V4 from UCLD3 in CWM. It flashed without any errors, but upon hitting reboot the device shut off and would not respond to anything. Tried leaving battery out for an hour, tried USB jig, and several other tricks to try to boot into download. Sent the phone off to Mobile Tech Videos for repair
avus_m3 I think your bootloader is corrupt just like mine.... but how?!?
w1209 said:
Same thing happened to me earlier today when flashing the latest MIUI V4 from UCLD3 in CWM. It flashed without any errors, but upon hitting reboot the device shut off and would not respond to anything. Tried leaving battery out for an hour, tried USB jig, and several other tricks to try to boot into download. Sent the phone off to Mobile Tech Videos for repair
avus_m3 I think your bootloader is corrupt just like mine.... but how?!?
Click to expand...
Click to collapse
That's not what I want to hear
I just don't understand how this can happen. Even if lets say worse case scenario the rom is screwed, my battery dies during the update or whatever...I should still be able to get into CWM or at least download mode right?
It's very odd indeed considering MIUI doesn't have a bootloader included either, and according to CWM it flashed without any problems. The only other possibility I could think of is that the ROM got corrupted while copying onto the phone. I checked MD5 checksum after downloading onto my computer but not on my phone before flashing. Still, could a corrupt ROM without bootloader hardbrick the phone? I thought the SGS2 was supposed to be very hard to brick when not flashing something like a bootloader
If the boot loaders and param.lfs are intact you should be able to get download mode (as long as there are no hardware problems).
Recovery on the other hand is in the kernel on our phones so if the kernel did not flash properly it could cause recovery not to work.
I have read somewhere a while back where someone had their battery die during a flash and they had to get different battery altogether to get the phones to power back on - don't know if that is the case here. It was as though their battery would not charge in their phone after it died during the flash. But if you guys know someone close to you that have the same phone I would try their battery just to see. There could be some other hardware malfunction also.
I don't know if cwm recovery touches any of the boot loaders or the param.lfs in the nandroid backup/restore process. As far as flashing a cwm zip one needs to check the zip to make sure the zip dies not contain boot loaders or param.lfs - as long as the zip being flashed does not contain those then it should be pretty safe to flash.
Sent from my SGH-I777 using XDA Premium HD app
If a USB jig doesn't work, I guess call up Samsung and play dumb? Worst thing that will happen is they'll send your phone back to you. Sorry to hear about your bad luck :/
Here's an odd idea... you didn't happen to get water in it, did you?
I hard brick too! I can't get jig to work at all and can't connect to download mode. I was at ~40% battery and flashed AOKP coming from ld3. I hit reboot in recovery and the screen went black.
If I can't get it working tonight I going to AT&T in the morning
---------- Post added at 11:19 PM ---------- Previous post was at 11:16 PM ----------
dayv said:
If the boot loaders and param.lfs are intact you should be able to get download mode (as long as there are no hardware problems).
Recovery on the other hand is in the kernel on our phones so if the kernel did not flash properly it could cause recovery not to work.
I have read somewhere a while back where someone had their battery die during a flash and they had to get different battery altogether to get the phones to power back on - don't know if that is the case here. It was as though their battery would not charge in their phone after it died during the flash. But if you guys know someone close to you that have the same phone I would try their battery just to see. There could be some other hardware malfunction also.
I don't know if cwm recovery touches any of the boot loaders or the param.lfs in the nandroid backup/restore process. As far as flashing a cwm zip one needs to check the zip to make sure the zip dies not contain boot loaders or param.lfs - as long as the zip being flashed does not contain those then it should be pretty safe to flash.
Sent from my SGH-I777 using XDA Premium HD app
Click to expand...
Click to collapse
Using the odin one-click I tried to flash using Mobile ODIN, it only flashed the param.lfs (this was before the helpful instructions from entropy on how to extract properly). Don't know if that has any effect on my problem.
nakedninja42 said:
I hard brick too! I can't get jig to work at all and can't connect to download mode. I was at ~40% battery and flashed AOKP coming from ld3. I hit reboot in recovery and the screen went black.
If I can't get it working tonight I going to AT&T in the morning
---------- Post added at 11:19 PM ---------- Previous post was at 11:16 PM ----------
Using the odin one-click I tried to flash using Mobile ODIN, it only flashed the param.lfs (this was before the helpful instructions from entropy on how to extract properly). Don't know if that has any effect on my problem.
Click to expand...
Click to collapse
Not sure, but if your param.lfs got corrupted that could be your problem.
Sent from my SGH-I777 using XDA Premium HD app
Same exact thing happened to me as dayv, except I was flashing to MIUI. Coincidence between the three of us that we were flashing FROM LD3 or not? Sorry to hear about your phone as well. Lesson learned is to wait for other to flash before you?
w1209 said:
Same exact thing happened to me as dayv, except I was flashing to MIUI. Coincidence between the three of us that we were flashing FROM LD3 or not? Sorry to hear about your phone as well. Lesson learned is to wait for other to flash before you?
Click to expand...
Click to collapse
Yes....coincidence. I have flashed form UCLD3 to AOKP (and CM9) & back more than a few times without issue.
@avus_m3, w1209, and nakedninja42:
With three similar hard bricks, there is a patern. We should gather as much information as possible. What package did you use to put UCLD3 on the phone immediately before the bad flash? Also, exactly what parts did the AOKP or MIUI package that resulted in the bad flash contain?
I used the latest version posted in the thread (I think there is only one LD3 package?): hxxp://goo.im/devs/task650/SGH-I777/Task650_I777_UCLD3_signed.zip
(not allowed to post links yet)
Same for MIUI: hxxp://goo.im/devs/ktoonsez/downloads/miuiandroid_I777-2.4.13b.zip
(not allowed to post links yet)
I know for sure that the MIUI MD5 checksum matched after downloading to my computer. Will see what the MD5 checksum is of the file on my phone after I get it back from MTV. If it is the same there is a definite pattern. If not it was just bad luck and my fault for not verifying it on phone before flashing
w1209 said:
Same exact thing happened to me as dayv, except I was flashing to MIUI. Coincidence between the three of us that we were flashing FROM LD3 or not? Sorry to hear about your phone as well. Lesson learned is to wait for other to flash before you?
Click to expand...
Click to collapse
Just to be clear this did not happen to me directly - just responded as I remember reading somewhere about a battery dying during a flash and that person needing to get another battery to get their phone back to life - again the battery may not have anything to do with what happened hear.
But it does look like this happened to two people after flashing away from ld3 leak - though it just may be coincidental hardware issues. we will see if there are more people who have trouble after flashing the leak.
Sent from my SGH-I777 using XDA Premium HD app
This is the second phone this has happened to, so I'm inclined to believe the problem resides in either the recovery package or there is no way to go from ICS to stock. Here's what I did and what the result was.
1. Initial phone was having hardware issues. I needed to return it to the warranty exchange depot, so I went to flash the no BL file that you can download from the recovery thread. Everything indicated that it flashed just fine. Phone reboots after the process and it gets the the "rethink Everything" splash screen and just sits there. After a minute, it reboots the phone again. Does the same thing. I take the phone in and get it swapped out under warranty.
2. Load CM9 on new phone and notice that GPS doesn't work. Everyone else says theirs works for the same nightly (5/22), so obviously it's my phone that's the problem or a bad flash. Flash a new nightly (5/29) and GPS still doesn't work. I want to flash back to stock to ensure that it's the hardware that's the problem, not the software. I download the most current recovery NO BL file from the recovery thread to ensure I have a good one. Flash it and the exact same thing happens. I get the splash screen then a reboot.
So now the question is, does flashing ICS permanently make it so you can't flash back? Does ICS work fine, but for some reason CM9 doesnt? Has anyone else done this without a problem? If so, what did you do because 2 phones 'bricking' like this isn't convinsing me that it can be done.
stalked_r/t said:
This is the second phone this has happened to, so I'm inclined to believe the problem resides in either the recovery package or there is no way to go from ICS to stock. Here's what I did and what the result was.
1. Initial phone was having hardware issues. I needed to return it to the warranty exchange depot, so I went to flash the no BL file that you can download from the recovery thread. Everything indicated that it flashed just fine. Phone reboots after the process and it gets the the "rethink Everything" splash screen and just sits there. After a minute, it reboots the phone again. Does the same thing. I take the phone in and get it swapped out under warranty.
2. Load CM9 on new phone and notice that GPS doesn't work. Everyone else says theirs works for the same nightly (5/22), so obviously it's my phone that's the problem or a bad flash. Flash a new nightly (5/29) and GPS still doesn't work. I want to flash back to stock to ensure that it's the hardware that's the problem, not the software. I download the most current recovery NO BL file from the recovery thread to ensure I have a good one. Flash it and the exact same thing happens. I get the splash screen then a reboot.
So now the question is, does flashing ICS permanently make it so you can't flash back? Does ICS work fine, but for some reason CM9 doesnt? Has anyone else done this without a problem? If so, what did you do because 2 phones 'bricking' like this isn't convinsing me that it can be done.
Click to expand...
Click to collapse
I know it works, I just used it the other day to go from ics to gb. Did you do a factory reset after flashing? Make sure you have your sdcard backed up before you use stock recovery.
Sent from my SGH-I777 using xda premium
nakedninja42 said:
I know it works, I just used it the other day to go from ics to gb. Did you do a factory reset after flashing? Make sure you have your sdcard backed up before you use stock recovery.
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
by factory reset, you mean from the recovery console?
nakedninja42 said:
I know it works, I just used it the other day to go from ics to gb. Did you do a factory reset after flashing? Make sure you have your sdcard backed up before you use stock recovery.
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Ok. You may now mock me. I did a factory reset and it worked. Feel like such a noob.
nothing to see here folks. Move along. Red, you can shut 'er down.
stalked_r/t said:
Ok. You may now mock me. I did a factory reset and it worked. Feel like such a noob.
nothing to see here folks. Move along. Red, you can shut 'er down.
Click to expand...
Click to collapse
No one would mock you over this. It is your experience.
Next time, when somebody hit the same or similar problem, do help them.
Friendly reminder.. If you can start your title with [q], it probably belongs in QA...
Mock mock mock!
Great to know, this may not be posted and is only available as "common knowledge". You sir have made this solution available to anyone searching for it. Thank you!
Clay
Sent from my SGH-I777 using XDA
I have a T-Mobile Galaxy Vibrant that was running Android 2.1. I rooted the phone (successfully), and installed Slim Bean 4.2.2 plus Google apps. Everything was going smoothly and I was reinstalling apps and data when I noticed that I had no network phone connection. Slim Beam did not seem to recognize the sim, and I came up empty searching for networks. I removed the sim and put it in another phone, and everything was fine.
I decided to restore the previous android 2.1 (which I had backed up) using ClockWorkMod Recovery. I did restore, then reboot. Now the only thing I get is the initial screen ... Vibrant and Samsung in bold white letters. I have tried repeatedly to launch CWM Recovery, without success.
Is it time for a new phone?
Thanks!
MaydayMalone said:
I have a T-Mobile Galaxy Vibrant that was running Android 2.1. I rooted the phone (successfully), and installed Slim Bean 4.2.2 plus Google apps. Everything was going smoothly and I was reinstalling apps and data when I noticed that I had no network phone connection. Slim Beam did not seem to recognize the sim, and I came up empty searching for networks. I removed the sim and put it in another phone, and everything was fine.
I decided to restore the previous android 2.1 (which I had backed up) using ClockWorkMod Recovery. I did restore, then reboot. Now the only thing I get is the initial screen ... Vibrant and Samsung in bold white letters. I have tried repeatedly to launch CWM Recovery, without success.
Is it time for a new phone?
Thanks!
Click to expand...
Click to collapse
If you can't go to cwm menu as well than I guess a jtag is needed. Or there may be some other solution, try digging through the net... or the experts in here can help u as well
Sent from my Micromax A87 using xda premium
MaydayMalone said:
Is it time for a new phone?
Thanks!
Click to expand...
Click to collapse
Are you able to get into download mode? I would recommend taking a look at this video if your unsure how to get into download mode https://www.google.com/url?sa=t&sou...f1zo4TtaBqqpMHcnw&sig2=u29A32xeMmrpJpMo2hwuxA.
Sent from my SCH-I535 using xda premium
Thanks for the suggestions
Thanks for the suggestions, but my phone is somewhat "challenged." I got it for free (that's the good news). The previous owner gave it to me after the power port/usb connector got damaged (that's the bad news). As I understand it, all the suggestions require a usb connection ... something I've been able to live without for the last year. Maybe I should give it a shot and get the usb port repaired, or maybe it would be cheaper/smarter to go shopping. I'm going to need time to think about that.
Thanks again to both of you.
MM
MaydayMalone said:
Thanks for the suggestions, but my phone is somewhat "challenged." I got it for free (that's the good news). The previous owner gave it to me after the power port/usb connector got damaged (that's the bad news). As I understand it, all the suggestions require a usb connection ... something I've been able to live without for the last year. Maybe I should give it a shot and get the usb port repaired, or maybe it would be cheaper/smarter to go shopping. I'm going to need time to think about that.
Thanks again to both of you.
MM
Click to expand...
Click to collapse
If there's any way you can get into cwm mode then you can first add the zip file of the custom rom from your pc to your sd card via a card reader and then try to flash a new rom. I think the problem you are getting at the moment is because you did not format dalvik cache and some other things before flashing
Sent from my Micromax A87 using xda premium
RazaVakil7995 said:
If there's any way you can get into cwm mode then you can first add the zip file of the custom rom from your pc to your sd card via a card reader and then try to flash a new rom. I think the problem you are getting at the moment is because you did not format dalvik cache and some other things before flashing
Sent from my Micromax A87 using xda premium
Click to expand...
Click to collapse
I keep trying to launch CWM Recovery, but no such luck. The initial screen with Samsung and Vibrant appears, then nothing. I have to pull the battery to turn the phone off. I did wipe the dalvik cache before installing Slim Bean, but not before the reboot. Thanks for following up, but I've got a bad feeling about this.
MM
MaydayMalone said:
I keep trying to launch CWM Recovery, but no such luck. The initial screen with Samsung and Vibrant appears, then nothing. I have to pull the battery to turn the phone off. I did wipe the dalvik cache before installing Slim Bean, but not before the reboot. Thanks for following up, but I've got a bad feeling about this.
MM
Click to expand...
Click to collapse
The last resort is probably the samsung service center. They'll repair it for a hefty price but that'll be less than the price of a whole new phone..... sorry about your loss
Sent from my Micromax A87 using xda premium