So I decided to start with fresh ICS install coming from leak 1. I didn't care if I ever was able to flash back to 2.3 so I used the FXZ files found in this thread http://forum.xda-developers.com/showthread.php?t=1961310
It started the flash and seemed to be working properly. Seemed to flash the MBM. Then erase the firmware and as It was writing the new It said flash failure. 18/1 or 1/18. After letting it sit for awhile and looking up some stuff I tried again and it keeps getting stuck at flashing MBM. So now what? I thought about trying the 2.3.6 FXZ but if it updated the MBM the first time that's probably not an option..What about just flashing the firmware? Anyway I'm hoping someone can help me out.
Edit:
Well I'm not sure what happened but I have managed to boot into Android. It was a fresh install and had me setup my phone again. When I enter fast boot I haven't seen the phone show up, as I wanted to try and flash again.
I don't know if I have a partial/buggy install or if it's perfectly fine. So far it seems to run alright, it did seem a little buggy when I was first setting it up though. I took some screen shots of the about phone area. Maybe someone can tell me if all the numbers are the same as what's in the FXZ.
http://forum.xda-developers.com/attachment.php?attachmentid=1804995&stc=1&d=1363284886
The kernel is the ICS one. I guess you're good. :thumbup:
Related
Background. Was using 2.2 for the longest time, loved Firefly. Went ahead and bit the bullet and decided to go to 2.3 and use Gingerbread. Solid week of great success. However I started notcing my antenna saying no signal. Several Reboots and still nothing worked. Decided I would One-Click Back to 2.1 and start fresh. Well I never had issues with Odin 1 Click before, but now I get in a boot loop (ATT SPlash Screen) I have noticed when its unloading the package after , the last thing i see is CSC and that it boots into the loop. Would love to get my phone back to stock so i can see if its a hardware or software issue with my antenna. I have looked at this link, http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36 but was afraid I possibly might still have GB bootloaders on my phone. I would think not if Odin finished, but I just want to double check with the community so I dont brick.
Thanks guys.
Can you get into DL mode? IF so, i would try and Odin again. ALthough I looked at the link in your OP, unless your heart is set on 2.1JH7, i would use the Odin3 one click downloader. That will restore your phone to 2.1JF6 as well as flash the correct bootloaders. I have gone back and forth from continuum to cm7 a few times now using that method.
Thanks for the quick reply. however this is the 3rd time trying Odin-1 Click tonight and I still end up in a boot loop. I have redownloaded the file just to make sure I didnt have a corrupt one. I just want a stock system and see if the constant antenna issues continue. (Trust me Ive tried different modems and all those possibilities.) Is it safe with that link? I noticed when i do Odin they flash a sbin and bootloader. I am assuming that puts it back on 2.1
which Odin are you using? Are you using the one click program that gives you stock firmware... JF6 firmware?
It is here:
http://www.megaupload.com/?d=SBSMALFJ
Yup thats what I have. It looks like it doesn't load the android system. Soon as it says installing Multi-CSC its done and rebooting. It would seem like its not unpacking the files. I have no status bar at the bottom. I have no idea why its doing this. Here is the crazy part. If i go back to the ginberbread stock, its not a problem to get to boot.
while I'm no expert.. seems like a bootloader thing. Try downloading it again from the link i put up and see if it was maybe a corrupted download.
The bootloaders are the first thing flashed in odin. It stopped after that then you have stock bootloaders. Also if all you see is the white AT&T screen and then it reboots, that indicates stock bootloaders as well. The gb bootloaders have a black galaxy s I9000 screen as the param.lfs image.
I would bet money you have stock bootloaders, use that link you posted that work be perfect. If you go back to gingerbread and want to return to stock bootloaders you'll have to use one click again even though you got a problem from it this time, if you get the same problem you know this worked to fix it.
And lastly usually problems with cell signal are modem related ... Which one were you using, did you even try another one? That would've been my first move instead of going all the way back to stock.
Hey studacris,
I have been using Mosaic (Love the work you guys do over there). I did try and use the other method to get back to Stock Last night and it did the same thing. Just a bootloop. If its plugged into the USB cable it goes directly to the Battery Symbol, if its not the Att 3G bars loop. I can flash to Gingerbread stock and then apply Other Roms. I tried GR-2 and Mosaic again, but still nothing with the signals. I just dont like the fact I cant get back to Stock with those 2 different methods. What I think is odd is when I load Gingerbread, it seems like items are being unpacked and loaded. When i try to go to Stock, everything happens super quick, making me believe nothing ever gets installed on the Internal Card during the unpacking sequence. I am no pro, but thats just something i noticed. Here was my original post on the Mosaic board. http://forum.xda-developers.com/showthread.php?p=14043766&highlight=Rizz67#post14043766
I've downloaded the stock image directly from the Motodev site for my MZ604. It successfully flashes boot.img. When I try to flash system.img, it just hangs. I thought maybe I was rushing it before giving up but I left it going for a couple of hours this morning with no luck. I'm happy with cwm and running ics roms but this is puzzling me as to why I can't get back to stock. My stock recovery img got trashed last month so recovering back to stock isn't an option. Any suggestions?
More specifically, I get a successful send of system.img, the hang up happens while writing.
I know this may not help you but have u tried downloading the file another time and compare the md5 between the file.. If they are the same then i have no idea mine was able to write correctly.. If they are different download it a 3rd time and see which one is truly correct.?
Sent from my mind control device
Downloaded from another site and got the same results. I kept rebooting the xoom and repeatedly tried flashing and it finally went through. For some reason, I had to do the same thing for recovery and userdata. It's back to stock and working normally now.
ps now i'm about to root again and flash a nightly lol. I just couldn't understand why it did the same thing last month when i tried to revert to stock and gave up. I was determined to figure it out today.
Awesome to hear! Flash away lol
Sent from my mind control device
Hi all,
As the title says I am currently unable to boot past (red) CWM recovery on my Infuse. I figure it might be easier to get help if I explain everything I've done:
The other day I tried to flash Uniporn build 37 only to soft-brick my phone because I didn't have the GB bootloaders installed (I had previously been on CM7). I managed to nandroid back to CM7 and decided I'd give it another go today.
Since I was told that flashing bootloaders is very risky I decided to flash something easier first with Heimdall to make sure everything was working right. I ended up flashing the ICS kernel in qkster's thread (one-click)... mistake #1. That bricked my phone once again and gave me rainbows in recovery.
So then I decided to try a Heimdall flash to stock 2.3.6 UCLB3 (once again, the one-click Heimdall from qkster's thread), which did give me a bootable OS despite some rainbows while booting up. However, here I made mistake #2 and tried to recover from the CM7 backup I made earlier today with the Infuse Toolkit. This completely soft-bricked my phone; I couldn't even get into recovery at this point.
So, I tried to reflash the stock 2.3.6 with bootloaders this time, only (and this may be important, not sure) it tried and failed to flash a PIT. At this point I flipped because I thought I had hard-bricked the phone. After I calmed down and came back a while later, I discovered the phone wasn't hard-bricked at all and I was able to get it into download mode after all!
I then flashed stock Froyo (I'd had enough of that rainbow ****) and it seemed to go fine... only now it wouldn't boot past 3e recovery, despite me wiping data and cache multiple times. So I flashed the community kernel... same problem, only now with red CWM instead of 3e.
So... what can I do now? I'm relieved I don't have a hard-brick on my hands, but this isn't that much better... could that PIT be the problem? I hope the info I gave is enough to help (and isn't too much either!)
Screw ICS, now I just want my CM7 back
EDIT: I should also probably note that after I managed to get CWM back I tried to flash the UCLB3 ROM in the Infuse toolkit; it said it installed but when I rebooted the phone still went straight to CWM.
EDIT 2: Another weird thing I just noticed: the phone apparently refuses to stay turned off while it's plugged into the wall to charge. If I plug it in, it turns on and goes into recovery mode. This also can't be good, since IIRC the battery won't charge while in recovery.
Just heimdall or Odin again...I've had this happen soo many time when I had my infuse...I just simply run heimdall again and its good...if you ever get recovery after heimdal or Odin...do not hit reboot...wipe everything then hit reboot...
And gingerbread bootloaders are not required for ics...I keep hearing people say they brick there phones because they don't have gb bootloaders...that is not the reason...yes with out the bootloaders you get rainbow recovery and boot up but that is it!!!
Remember if you are going to ics from gingerbread...YOU HAVE TO double flash...the first flash will not work...just three finger back to recovery and flash again from.blue/rainbow recovery depending whether or not you have.bootloaders...
Look at my infinitum port thread...it has great instructions on how to flash ics roms...as well as how I flashed gingerbread bootloaders when I had my infuse
Sent from my HTC PH39100 using XDA
Nah, I've tried that, it's more broken than that. I think I need to reflash the PIT, which Heimdall doesn't like for some reason. I followed qkster's advice in another thread but still no dice. I might have to try using a different computer.
All fixed now, I used the Heimdall one-click on a Windows machine; the PIT and everything else flashed without a hitch and I'm up and running again.
just keep trying flash different stable stock roms thru odin until u can boot..i had it happen twice nd even couldn't get computer recognize my phone for a bit thru odin but it finaly workd now I'm back on cm9
Samsung Infuse ICS 4.0.1(cm9)
So I had a completely stock Galaxy s 4g, on gingerbread. I had the bright idea of rooting to try out different builds. I was in the middle of flashing when I noticed that what I was flashing was for the Vibrant. Well, it was either let it flash with that or stop the flash, so I stopped it. After searching for hours, I couldn't find a working link for a download to flash a custom build. I was able to find a "stock" flash, but for some reason I don't think it's right. I have problems with low call volume now and have to power the phone off and on to fix it temporarily. Everything else works fine, so far. Another thing I noticed is everyone shows firmware of 2.3.6, mine says 2.3.4????? Here's my info: sigh-t959v, baseband T959VUVKG4, kernel 2.6.35.7-t959vuvkg4-cl385158, build gingerbread.vuvkg4.
Any thoughts on what I should do?
Thanks in advance
This thread has heimdall one clicks that will get you back to stock kj6. Remember to flash once then after booting until you hear the t-mo jingle pull battery and put it back in download mode and check the flash bootloaders and flash it again.
http://forum.xda-developers.com/showthread.php?t=1358498
If you want root in the second post is a one click created by me. You can flash it instead of the plain stock one by bhundeven. But you need to flash the bootloaders to make sure you get rid of all the vibrant stuff.
Ok, thanks a lot. I will flash your build tomorrow when I get home from work. I'll let you know how it goes. Thanks again.
So I flashed your build and everythingis working great, even seems to be running faster. However, the wifi says "error" when I try and activate it. Is that a rom problem? Should I start over and try again?
It is because the kernel uses a different module then what is in the rom itself. That is why it is suppose to be used as a stepping stone to flash to a different rom.
Gotcha.
Okay.
So, I have tried to UTSE on this and found a thread that directed me to flash a new radio (http://forum.xda-developers.com/showthread.php?t=1116884) which I have done but the fastboot is still not letting my phone respond.
So...
My phone is a GT 19023.
I'd updated to jelly bean awhile ago but was having some serious performance problems and wanted to flash back down to ICS or GB. Of course, the recovery wasn't working so I went to Nexus Hacks and downloaded his recovery files, stupidly I didnt notice it was 4G specific (crespo4g), just that it was for ICS and JB. The recovery seemed to work ok, had the new touchscreen version, but then I tried to install a stock GB ROM from my SD card. At the end it seemed stuck on writing radio. Wasnt doing anything so assumed it was ok to reboot. When it rebooted every process was failing so I tried to do the fastboot flash recovery again and the phone just wouldnt respond.
Tht's where I am at now.
Saw another thread and got directed to the link above to flash the radio.
Did that, used the UCKF1 radio, no problems installed fine but the phone still won't respond to fastboot flash recovery using recovery-clockwork-3.0.2.4-crespo.
Can anyone point me in the right direction PRETTY PLEASE! I'm not a techie guy and its my only phone :crying:
You did a lot wrong here. NEVER DO SOMETHING UNTIL YOU HAVE COMPLETE KNOWLEDGE OF IT
Also you flashed the wrong radio. I would suggest you to stop as where you are right now.
You need to go complete stock first, by flashing the factory image.