I want say thanks to all they great people on this forums out who help us in our times of needs.
Here is my story:
In preparation to the upcoming gingerbread update for my i9000m I decided to disable my lagfix and revert back to an RFS filesystem. I had installed a new kernel. I had replaced my stock kernel with a Kernel switcher app because I did not want to use Odin. Having an i9000m that was plagued with a failed motherboard back in December, I did not want to have another brick in my hand.
So Friday night, I went in the recovery boot. Disabled Ext4 in favour of RFS. Rebooted to convert the filesystem. Went I went from RFS to EXT4 the whole thing took approximately 20 minutes. After an hour of converting, it was stuck on one file for about 45 minutes that is when I should I ask instead of act. I pulled the battery and hoped for the best. It restarted. The filesystem seemed to have been converted and it booted into android without an itch. I decided then to revert back to the stock kernel which is when I brick my phone. It did not reboot. After the animation screen it never loaded into Android. After wiping out and trying for format my SD card, I got over my fear of Odin and decided to flash the custom kernel once again, however, instead of flashing it through PDA, I flashed it through CSC. My bad… At this point I was able to see the Galaxy S I9000m screen but never loaded the animation. I thought I was screwed badly. I tried to find over the forum the darn CSC tar file for the KC1 update but couldn’t find it all by it self. After reading a few post I registered myself over at samfirmware, downloaded the whole update, flash it through Odin again because at least I was able to load into download mode. Now, I was able to see the animation screen once more but nothing after that. I loaded into recovery mode; saw the notice that it cannot mount the E:something, which I suspect was there all along. I search over the forum for the solution. Found it, applied the missing file through Odin. Phone booted into android perfectly.
I made every the mistakes that I should not have done, primarily not searching for a solution first before acting. I acted before reading and I screw up my phone and lost all my data because of that. If I had read the error that my phone was giving me and applied the patch, I would still have all of my information and all my apps, but this is the price I accept to pay for my mistakes. I have learned my lesson but also have learned that Odin is very easy to use.
Thanks again to all the people who keep this forum alive with solutions and great apps, ROMs and kernel.
Related
I did this about 4 days ago and have since done sooo much reading and researching, I am having trouble with my specific issue though.
I was basically just rooted/unlocked on ji6 with some cosmetics and decided I wanted to play around with some features as I am fairly new to Android. So the kid in me decided to pull the ol' "what's this button do" so I got what I deserved.
1st, at reboot the tmo screen and the galaxy screen boot up but then it goes to the black screen and only the bottom buttons light up.
Researching I Odin a stock JFD as per the many threads on here but it gave me the same end result.
Continuing my research I found on here many have had success with Odin to Eugenes 2.2 then back to JFD. I HAD success with getting 2.2 to boot up but I would then go to JFD and be back at square one.
Something I am noticing is that once in 2.2 I cannot install apps, the application space reads as 0.00 so it's telling me to remove some apps which I also cannot. I was going to try to install clockwork mod and see if I could get to the recovery console but I cannot.
Please advise, I am not sure what other info is needed as I am still a little green in the Android field and learning. The plus to this is Tmo accidentally sent me another phone so I am basically just using the bricked phone for all my newbie mistakes.
Blizzard1017
Are flashing eugene's unofficial froyo or eugene's froyo that doesnt brick? Never done the repartition personally but I've read others posts who have. I think you use the froyo that doesn't brick, without checking repartition in odin, then flash the stock jfd with checking repartition in odin. Good luck hope you get it back up and running.
Sent from my Vibrant running Macnut R10
Load Odin with the 512.pit file along with JFD.tar and check the repartition box. This should get your phone back to working properly.
There is a thread here that I thought I saved but did not that have instructions and links to the proper froyo and jfd. Says something to the fact of dl 512 and jfd then dl links in eugenes thread, use froyo 1st THEN reflash to jfd. I will try to search it back, I am sorry for being vague on this part.
EDIT: found it:
forum.xda-developers.com/showthread.php?t=745547
I have flashed with partition, without partition. With card in phone, without card in phone. With sim in without sim in. Combinations of all three.... this has become quite the taxing experience. Only saving grace is I have a working spare Vibrant with Axura on it running oh so smooth.
BTW, when in Eugenes froyo, I also cannot log into google to get to the market. I can get online through the web wirelessly but logging into google says try later. weird? related?
Another issue I have, as I was just going to send it back in and hope they thought it was a software issue, I cannot lock the phone back. I enter in the code and it pauses about 10 seconds and rejects it. I can successfully re-write the lock code but it still rejects it in the phone. I am curious if this has to do with the partition not working.
Ugh, this is driving me insane now. Is there a way to force this phone backed to locked? I am just going to send it in flashed to the JFD stock and play stupid if I can lock it back up.
Unless someone has some more solutions for the above issues lol. I would of course LOVE to be able to "fix" if just for the learning experience.
what is exactly are you trying to do? you want to lock the phone?
The phone is sim unlocked, I want to lock it back so I can just send it in if I cannot fix this partition issue. The problem I am having is that it will not accept the lock code I give it.
To unlock it I used the adb method of "repairing" the nv_data.bin file allowing me to make a custom lock/unlock code which worked to unlock it. It will now not allow me to lock it back, it rejects the code.
I'm sure there is another post about this but I don't know where it is, have looked, a little, but, just want my specifi ? answered. So, have Epic and went to flash from CWM2.5 to 3. Followed all instructions and 1st time didn't flash right, so, reflashed, again, sidenote, I followed all instructions correctly. Anyways, seemed like everything was fine until it rebooted after switching all to Ex4 and from that point only Samung bootup screen appears and nothing else. In addition, have been unable to do 3 finger startup since the reboot. Help, esn swapped to my POS Hero that's slower than slow until I get some advice. Thanks.
S-
I did the samething when I installed cwm 3. U gotta take ur microsd card out and insert it into a computer using an adapter. From there dl a rom of your choice, place it on the sd card, and then flash with cwm.
smathias503 said:
I'm sure there is another post about this but I don't know where it is, have looked, a little, but, just want my specifi ? answered. So, have Epic and went to flash from CWM2.5 to 3. Followed all instructions and 1st time didn't flash right, so, reflashed, again, sidenote, I followed all instructions correctly. Anyways, seemed like everything was fine until it rebooted after switching all to Ex4 and from that point only Samung bootup screen appears and nothing else. In addition, have been unable to do 3 finger startup since the reboot. Help, esn swapped to my POS Hero that's slower than slow until I get some advice. Thanks.
S-
Click to expand...
Click to collapse
Yeah, it sounds like the rom flash after the ext4 upgrade didn't "take". Try what the previous poster suggested and if that doesn't help, look up the Odin posts on this forum. Even if you can't "3-finger" into some form of recovery - as long as you can put the phone into download mode (holding down the "1" key while you power the phone on), you can use odin with 99% success.
If you have any questions, feel free to PM me and maybe I can try to walk you through it without you getting bashed on here! LOL
cjobanion said:
Yeah, it sounds like the rom flash after the ext4 upgrade didn't "take". Try what the previous poster suggested and if that doesn't help, look up the Odin posts on this forum. Even if you can't "3-finger" into some form of recovery - as long as you can put the phone into download mode (holding down the "1" key while you power the phone on), you can use odin with 99% success.
If you have any questions, feel free to PM me and maybe I can try to walk you through it without you getting bashed on here! LOL
Click to expand...
Click to collapse
He doesn't need odin. The CWM3 flash he did was successful. He just needed to flash an ext4 ROM to get past the Samsung Boot screen.
mattallica76 said:
He doesn't need odin. The CWM3 flash he did was successful. He just needed to flash an ext4 ROM to get past the Samsung Boot screen.
Click to expand...
Click to collapse
That's my thought as well. What rom is the OP trying to use? Is it ext4 compatible? Using a rom that isn't compatible with your file system is one way to get stuck at the Samsung screen.
Although, if ext4 didn't "take" or was partially completed, it could result in something like this. Reflashing with cwm3 might fix this if it notices a problem and tries to redo the conversion.
If flashing a good ext4 compatible rom doesn't fix it, then using Odin and starting over quickly becomes the best option. Though there is a reRFS dk28 rom that the OP could try to flash from his current situation.
Ok flashed Midnight Standard and goes straight to CWM3 startup screen & that's it. So, am I gonna have to do the whole Odin thing? I really hope not. Oh, and fyi I'm a SHE not a HE, lol!
Sent from my HERO200 using XDA App
There's a girl on our website! OMG!
Look for the reRFS dk28 rom. It will try to reformat your phone back to rfs. Then try again. Or just go ahead and jump straight to Odin. Some people seem have a hard time with Odin, but it really isn't that hard.
Ok, thanks for the input. Screw it, just going to do Odin and not mess around anymore. Not having a phone the last day in a half is driving me nuts! Can you point me to a link that has all the stuff I need to do this. I've surfed a couple links and some lead to dead link for Odin. Besides, I want to make sure I've got all the right "ish" to do this. Thanks, so much!
S-
I've been scared to make a thread for my problem cause I know how much you all hate that when there's another thread with the answer. However, I've been getting lost in links and threads for hours with now results and no actual help. If there's a thread for my exact problem please post the link or redirect me.
What I did:
I had a STOCK EC05 on my Epic. I had rooted it about a week ago using the method presented here:http://forum.xda-developers.com/showthread.php?t=808103
I had to use MAC method, cause my laptop won't charge so I had no other choice. It worked, except I had no CWM. Then today, I wanted the CWM so I repeated what I did and I finally got CWM, it was CWM 2.X. After that I decided to take it a step further and tried flashing Syndicate 1.1 Frozen ROM. It looked like it worked, I wiped everything beforehand like I'm supposed to.
Ok, now my problem is, it's stuck on the Samsung boot screen after it rebooted itself. I can't do anything with it. It only responds to the power button and a charger.I can't get into CWM, it'll turn on with the power button but can only turn it off by pulling the battery. Also, When I plug in the cord it tries to bring up the battery picture but just freezes with the little circling circles in the middle of the battery, and it won't recognize on my computer.
I can't find any links or threads that have the answer I'm searching for, especially since I'm on a MAC OSX 10.6.7. If It's best I use a PC then I could gain access to one. Any help is appreciated. and like I said, if there's already an answer posted then I probably missed it, and I apologize.
What you did wrong was root with 2.x, which kept you with an rfs filesystem and then you flashed an ext4 filesystem rom. To flash an ext4 rom you need to root with 3.x. if you can't get back to stock, and you're on mac you'll probably need to use heimdall since I don't think odin works with mac. Hopefully somone can give u more info on heimdall cuz I'm not familiar with it.
Sent from my SPH-D700 using XDA App
Try turning on your phone by holding the 1 key on the keyboard and the power button. If that brings you to the download screen you can use hemidal on mac or odin on pc to restore your phone.
Sent from my SPH-D700 using XDA App
Use the TAR located here to fix your phone. Download the CMW 3.0.0.6 version.
---> http://forum.xda-developers.com/showthread.php?t=1061912
I'm assuming Hemidal is the same as ODIN but MAC version.
So just Flash that tar with hemidal. (make sure to boot phone while holding "1" on slideout keyboard.)
Then after you let it boot, you can go into CMW, (let it EXT4 itself) then you can install SRF 1.1 =D )
The "1" on the keyboard...OMFG, Thank you!!! I'm so happy to see something else other than that Samsung screen, YES! Ok, my hope has been renewed. Thanks to all of you. I never even heard of Heimdall till now...I'll get to work on it now
EDIT:Ok, I had spent 12 hours straight figuring everything out. Finally, as I was LITERALLY about to give up hope, I had used Odin on my on my Laptop. I found a PIT and used the TAR that Shoulon suggested. Finally worked. It's miraculous that I had just so happened to receive my new charger for my laptop, because nothing was working for me on my Mac. Thanks to you all for the assistance.
Excuse the long thread title lol..
I've been gently lowering myself into all this tampering with my phone as I've always been a bit of a tinkerer with everything i've ever owned.
So back in march my phone, an unbranded handset on o2 uk was on 2.2.1. My first foray into modifying my handset was to flash the jvk gb firmware. I then rooted it using cf root. All very simple. I then flashed it using cwm with Simply honey 3.2 and then the latest 3.5. No issue.
So this afternoon, I flashed it with the "unspoken ones" kernel just cos I could lol. Something didnt seem right though. There was a bit of lag and I got one or two forced closures so I decided to restore one of the cwm backups I had. Thing is, it hung upon reboot at the i9000 screen, for about 10 minutes so I pulled the battery. Now I couldnt get it restarted. Panic set in. This was my first proper issue and I just wished I was back in march on 2.2.1 again.
As said, couldnt get it started so went hunting some advice. Install a base stock rom with 3 files and a 512 pit. I struggled. Could I find 3 files ? Nope. Not on samfirmware. Every file I downloaded was one file. JP1 JPU JPY. All 1 file. So. As JPY was the firmware I was on originally, I chose the 1 file version, put the phone in download mode and flashed it via odin. It worked !!! And then I plugged it into kies and up popped the box, I have an firmware update ! JPO GB! So i installed that. I'm quite surprised that I got the update because you always see lots of threads regarding people being unable to update by kies once they have modified their phones. Why did mine work? Because the handset in unbranded perhaps ?
Anyway, I wanted to get back to the Simply Honey rom because it ran really well and the battery life is fantastic but Simone hasnt done a version based on JVO yet as far as I could tell so I thought, I know, I'll root with cf root, again and try that backup again using cwm. And it worked, and here I am back where I was earlier today ! Ace ! lol
Sorry about the essay but I'm sure that there are some questions in there worth answering.. ?...and also to serve as a bit of help to those that find themselves in a dodgy situation. Just calm down, search for the advice, it is out there and do as it says and everything will be cool
Posted from my restored and working handset...
the files you download from samfirmware are rar files (have a .rar extention). This means you need to decompress them into a folder and the "three files" will be in there. You need a rar extractor app. You can use 7-zip which is free.
You need odin (or ezodin or heimdal) to flash the stock rom but I am sure you know that already. There are a few guides around for all tools.
There is a lot of information here, especially in the "sticky" posts. If you feel like learning what you are doing rather than copy instructions (as I think you do), it may be a good idea to go through them.
Anyway you got your phone working in the end so that's good!
simple solution when an install hangs is only to reflash the kernel in odin: that restarts the phone.
cwm is not invincible and the restored rom is there but the phone hangs on the boot because of the kernel hiccup. Reflashing the kernel to the one you now want will allow the phone to boot and access the rom that matches -- you do have to ensure the recovery version rom and the kernel you are flashing are in sync.
Persist. You only really panic the first time this happens -- after that you know it is a possibility and how to fix it.
Worst case scenario: pull the battery, reinsert, go to download mode and reflash the kernel and base rom of your choice. At least now you have a clean phone!
Two things are important to remember: (1) always do a backup before installing a new rom or kernel and (2) use titanium backup for all applications -- easy to restore everything.
Also I find it easier to use google calender and my internet email as bases for dates, appointments and contacts -- that way if I loose everything on the phone I can quickly reload my data by sync with online accounts once I have the phone "rebuilt".
So, I was at work today, and a customer came and asked if I can recover her deleted picture on her GS4 I337. I thought, OK, I've never played with S4, this is a good chance. So I took the phone and started mess around with it.
As Usual, before any recovery, you need to do a 1:1 backup of the device. so I was thinking, android's file system is basically ext4, if I could install a busybox, I can then make a clone of the internal storage with dd or whatever; before I can install busybox, I need to root the phone.
so without carefully reading I just downloaded kingo android root I found in GS4 forum. and it worked out pretty well.
then, maybe because I haven't had any breakfast, or something....my mind wasn't thinking stuff right.....I told myself that I need to find a busybox flashable and flash it into the phone. so I found the busybox flashable zip. but for obvious reason the stock recovery didn't take it lol. at that point I was like, ok let's try something else....because I need a custom recovery to flash anything other than stock auth ....
and I found CASUAL....again, without reading the manual, I just plugged in the phone and clicked go...
after CASUAL finished its job, it reboot the phone, and I found myself in deep****.....
the phone is stocked in download/odin mode.....
I was scared ****less...after search and read like a crazy, I found out that 1, there's no custom recovery for MF3 and, 2, CASUAL doesn't work for MF3 phones (before soft-brick I don't even know what's MF3 lol)...and, 3, people with similar issue sent their phone over to a ebay seller who offers jtag unbricking service for $30...
after reading CASUAL log, I noticed that CASUAL didn't successfully flash the recovery(of course) but it just went ahead with the progress anyways...so, I think there's something wrong with the boot env or bootstrap it mess up to cause the phone not able to boot up.
so I thought, if I can find the stock rom and flash boot.img, maybe it will unbrick the phone.
because it was a HUGE responsibility, it's not my own phone. it's a customer's, and may or may not contain life and death information in there that was probably why the owner was willing to pay for recovery service at the first place... and I mess it up for her...it was so much pressure.....
thank god it was not the end of my life....
I downloaded and extracted I337UCUAMDL_I337ATTAMDL_ATT.zip, and tried to flash the boot.img with Heimdall .
heimdall flash --BOOT boot.img
heimdall failed with a message like "there's no partition name boot" or something, BUT it DID successfully update the PIT, and rebooted the phone. Magically, the phone came back alive. PIT corrected the partition problem so phone will boot normally??? I was SO HAPPY!!!!
I stopped there and put the phone aside, I don't wanna touch it anymore LOL
I actually posted a small guide about how to get it back up and working again, but you nuked her recovery. She'll have to get it fixed at a Samsung experience shop. They do it for free.
Sent from my SAMSUNG-SM-N900A using Tapatalk 5
If only I found your guide at my 3-hour panichour lol
I am not sure if the stock recovery is still there. do you think technically I can use heimdall flash --RECOVERY recovery.img to reflash the recovery if it was nuked?
crumpz said:
If only I found your guide at my 3-hour panichour lol
I am not sure if the stock recovery is still there. do you think technically I can use heimdall flash --RECOVERY recovery.img to reflash the recovery if it was nuked?
Click to expand...
Click to collapse
It's been posted in many threads about manually putting the phone into ODIN (download) mode and then manually cancelling out to usually boot the phone. However, as mentioned, the stock recovery probably no longer works. It seems to me, and you mentioned it a couple of times yourself that your biggest issue is not reading about what it is you are doing. Hopefully, you learned a lesson about that.