Froyo EB13 Pre-Rooted, Deodexed, with Clockwork - RFS & EXT4

[Tahe]

Ok. I got a Green Pass in Odin for the Stock EB13 flash. Just put the battery and sd card back it just rebooted. I think I'm in good shape now. Thanks a bunch Paul627g!

I will play with EB stock for a while and when my heart comes back up out of my stomach I'll consider rooting and flashing the kernels for those fixes (camera, keyboard, video lag). Thanks, again!

Alright.. At this point you need to try the following.


- Turn off any and all virus scanners/spy ware detectors.

- Try removing your battery completely and plug your device into your computer with the cable. You may have to try different ports or cable.

- Next with the battery out and the device plugged into your computer try and boot into Download mode.

If you can get into Download mode then I would recommend at this point doing a factory restore to either Froyo EB13 or back to Eclair 2.1. This way your phone will be back to a functioning state again before reattempting the conversion to Froyo Prerooted/Deodexed with CWM.

You can download the files needed here and follow the steps.. Procedure #1 is for Froyo EB13, procedure #2 is for Eclair 2.1

[How to] Factory Restore (or Fix a Bricked Phone)

Not sure if you followed the OP instructions, but the post I did on page #3 was referring to someone that was checking/ticking F Reset Time and other boxes.. I believe it says to have the Repartitioning checked for the CWM3/EXT4 version, but that shouldn't of affected things immediately when starting Odin like it did in your case.

 

[Paul627g]

Tahe, yes if you got the green light and passed then you can unplug and replace your battery and boot up.

 

[Tahe]

Awesome, ok thanks. Please read my "re-edited" last post. In short - a heartfelt THANKS!

Tahe, yes if you got the green light and passed then you can unplug and replace your battery and boot up.

 

[Paul627g]

No problem.... Sounds like you just had one of those flukes that happen... You had a soft brick, hard brick (time to worry) is when your phone is completely unresponsive and you can't get back into download mode.

 

[Tahe]

shrew! (forehead wipe)

No problem.... Sounds like you just had one of those flukes that happen... You had a soft brick, hard brick (time to worry) is when your phone is completely unresponsive and you can't get back into download mode.

 

[leftkidney]

No problem.... Sounds like you just had one of those flukes that happen... You had a soft brick, hard brick (time to worry) is when your phone is completely unresponsive and you can't get back into download mode.

after looking into this for about 2 days so far I have talked to many people that know there stuff - I work for IBM and so does my dad so I have access to some really smart people - I have been told that the Epic and other SGS phones cant be "bricked" in the sense that it can never be returned to a working unit as long as there is no physical damage, there are some cases where if overclocked and/or overheated it could cause problems - internal components could be damaged but thats far off

what I was told is that these phones use a type of chip that doesent allow for this type of problem, the EVO on the other hand can have this problem if flashed with a incorect file system there can never be fixed

 

[Paul627g]

after looking into this for about 2 days so far I have talked to many people that know there stuff - I work for IBM and so does my dad so I have access to some really smart people - I have been told that the Epic and other SGS phones cant be "bricked" in the sense that it can never be returned to a working unit as long as there is no physical damage, there are some cases where if overclocked and/or overheated it could cause problems - internal components could be damaged but thats far off

what I was told is that these phones use a type of chip that doesent allow for this type of problem, the EVO on the other hand can have this problem if flashed with a incorect file system there can never be fixed

Hate to correct your sources but it can be hard bricked. We have had a few incidences where people have completely bricked their phones where they would not respond to anything. They wouldn't turn on, they wouldn't give an error, no download mode, nothing. OS completely corrupted. Most recent was someone accidently pulled the usb cable during the Odin process while Odin was "working" on screen and it completely bricked it beyond return. The user took it to the local Sprint rep and they couldn't get it to do anything either, complete loss..

While a true hard brick is rare, it can happen given the right situation. I find though if we can get it to boot into download mode it can be restored. No download mode, your true bricked because that is the only way to restore the OS image to the phone using Odin (which is what Samsung uses).

 

[Tahe]

Ok so, just so i have this straight for my next attempt to flash the Pre-rooted EB13, CWM3, etc., I should click Repartion and keep Auto Reboot checked. Does the F.Reset Time need to be kept checked as well?

 

[Paul627g]

Ok so, just so i have this straight for my next attempt to flash the Pre-rooted EB13, CWM3, etc., I should click Repartion and keep Auto Reboot checked. Does the F.Reset Time need to be kept checked as well?

Okay if your going prerooted/cww3.0.0.6/EXT4 then yes, tick the repartition and auto reboot.

F. Reset Time does NOT need to be tick/selected.

 

[Tahe]

Okay if your going prerooted/cww3.0.0.6/EXT4 then yes, tick the repartition and auto reboot.

F. Reset Time does NOT need to be tick/selected.

Ok, sweet. Thanks! Greatly appreciated!

 

[leftkidney]

Hate to correct your sources but it can be hard bricked. We have had a few incidences where people have completely bricked their phones where they would not respond to anything. They wouldn't turn on, they wouldn't give an error, no download mode, nothing. OS completely corrupted. Most recent was someone accidently pulled the usb cable during the Odin process while Odin was "working" on screen and it completely bricked it beyond return. The user took it to the local Sprint rep and they couldn't get it to do anything either, complete loss..

While a true hard brick is rare, it can happen given the right situation. I find though if we can get it to boot into download mode it can be restored. No download mode, your true bricked because that is the only way to restore the OS image to the phone using Odin (which is what Samsung uses).

I thought that the only problems came if someone tried to flash the wrong carrier info into the phone - as in cdma to gsm or whatever

I thought that there was a way to pull the battery and plug it into odin with no battery in it and recover it that way - but I guess that if odin is working

but I was told that the Evo uses NAND and the Epic uses OneNAND with package-on-package which prevents a bad flash from sticking because you can use the "charge pump" built into the chip to flash it, where as with normal NAND you have to use an external device to flash it

 

[robyn25]

Thankyou , Thankyou , Thankyou!!!! I haven't tested it out much, but I know my phone made it through it alive and workin! Just installed syndicate on there too! About to check it out, yay!

 

[Paul627g]

I thought that the only problems came if someone tried to flash the wrong carrier info into the phone - as in cdma to gsm or whatever

I thought that there was a way to pull the battery and plug it into odin with no battery in it and recover it that way - but I guess that if odin is working

but I was told that the Evo uses NAND and the Epic uses OneNAND with package-on-package which prevents a bad flash from sticking because you can use the "charge pump" built into the chip to flash it, where as with normal NAND you have to use an external device to flash it

I may not know the exacts of the terminology you used here but I do know we have had a few true hard bricks. From what I understand they are the fault of user error and not Odin. Yes the problems happened during the Odin process but it was due to something the user did while performing the processes. I know the last one we had a month or so back was completely bricked, he had nothing.. Completely bricked due to pulling the cord at the wrong time and corrupted everything from being unrecoverable.

The end result he was very lucky and went to Sprint the next day and they replaced the phone free of charge and no hit on his Sprint insurance replacement plan.

 

[leftkidney]

I may not know the exacts of the terminology you used here but I do know we have had a few true hard bricks. From what I understand they are the fault of user error and not Odin. Yes the problems happened during the Odin process but it was due to something the user did while performing the processes. I know the last one we had a month or so back was completely bricked, he had nothing.. Completely bricked due to pulling the cord at the wrong time and corrupted everything from being unrecoverable.

The end result he was very lucky and went to Sprint the next day and they replaced the phone free of charge and no hit on his Sprint insurance replacement plan.

I bet that did happen, however according to what I have been told using the correct software the chip can be forced to flash the chip by using the "charge pump" which is a feature on the chip that when given the correct code it will release high power and erase the chip

that being said this "software" might be something that isnt available to anyone outside of certain departments in certain companies so in that case it is "hard bricked" I have asked people I know and was told that it is just like the ultraviolet erasing method used with EPROM chips but a software code - they werent sure but it was suspected that if the phone was sent into Samsung it could have been fixed by there software, unlike HTC if the same thing happened to the Evo because it is using the normal NAND not OneNAND


so I guess the only way to prevent this would be to just not unplug your phone while odin is running or anything else like that - but I bet that someone knows how to fix that if they looked into the technology - I was told that the OneNAND is brand new so its likely that its not understood properly outside of labs and such

 

[DroidXcon]

Im pretty sure that it will only brick if you pull in the middle of boot.bin or sbl.bin

other than that it will just be a soft brick. so the best way to safegaurd this is to remove boot and sbl and repackage it

 

[Paul627g]

I bet that did happen, however according to what I have been told using the correct software the chip can be forced to flash the chip by using the "charge pump" which is a feature on the chip that when given the correct code it will release high power and erase the chip

that being said this "software" might be something that isnt available to anyone outside of certain departments in certain companies so in that case it is "hard bricked" I have asked people I know and was told that it is just like the ultraviolet erasing method used with EPROM chips but a software code - they werent sure but it was suspected that if the phone was sent into Samsung it could have been fixed by there software, unlike HTC if the same thing happened to the Evo because it is using the normal NAND not OneNAND


so I guess the only way to prevent this would be to just not unplug your phone while odin is running or anything else like that - but I bet that someone knows how to fix that if they looked into the technology - I was told that the OneNAND is brand new so its likely that its not understood properly outside of labs and such

Yes I agree with what your saying. You and I know in the real world, if a phone comes in "bricked" to Sprint or Sammy I bet if they take the time to actually attempt using Odin to recover the device and it doesn't work it hits the trash bin... A few written off devices here and there will not make a dent or be worth their time to mess around with recovering using methods you describe to make into a refurb..

Thanks for the "advanced" look into this situation.

 

[Eatsleepdrivesc]

Hey guys,

I Odin my phone back to factory with the EXT4.

I went and got the Terminal Emulator to see if it was EXT4.

I type in "mount" and under System it says EXT4 but under Cache and Data it says RFS.

Is this correct? my benchmark was at a 1220 ish area If not how do I correct it to be right?


Thanks!

 

[leftkidney]

Hey guys,

I Odin my phone back to factory with the EXT4.

I went and got the Terminal Emulator to see if it was EXT4.

I type in "mount" and under System it says EXT4 but under Cache and Data it says RFS.

Is this correct? my benchmark was at a 1220 ish area If not how do I correct it to be right?


Thanks!

I dont think so, I have the midnight rom the EXT4 version so it will only run with EXT4 (I think) and there is nothing about RFS anywhere in there when I look

you might not have wiped the cache 3x like its sugested and it is showing that from before the conversion

also when I did the test I was at 1033 before with RFS EB13 and after I was at 1540 or so - now after midnight rom I am at 1847 so I know its not RFS


try the wipe cache 3 times and the davlik cache also, that could be what it is

 

[Paul627g]

I dont think so, I have the midnight rom the EXT4 version so it will only run with EXT4 (I think) and there is nothing about RFS anywhere in there when I look

you might not have wiped the cache 3x like its sugested and it is showing that from before the conversion

also when I did the test I was at 1033 before with RFS EB13 and after I was at 1540 or so - now after midnight rom I am at 1847 so I know its not RFS


try the wipe cache 3 times and the davlik cache also, that could be what it is

The user resolved it. They didn't reboot into CWM to finalize the conversion.

 

[robomav]

i always forget about the reboot to finish the conversion. luckily it will happen anyways if you are going to flash a rom