• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Bricked after clockwork 2.2 Root

Penny_Man

Penny_Man

Newbie
I can only get to the clockwork 3.0.0.6 Recovery screen. I have the Default Stock Dual FS kernel For EB13 installed on my sd card.

http://efragtv.com/android/EB13-DUALFS-KERNEL.zip

When I go to "install zip from sdcard" it installs correctly and I reboot the phone. It just goes black after the samsung logo and vibrates a couple times, it eventually restarts and does the same thing.

I tried doing the recovery that was made, but it does the same thing.

I tried a factory restore and it has the same effect.

I installed Android 2.2 from Samsung's Zip.

I dont' mind taking it back to the factory settings because I'll try to root again...

Any suggestions?
 
Penny_Man said:
I can only get to the clockwork 3.0.0.6 Recovery screen. I have the Default Stock Dual FS kernel For EB13 installed on my sd card.

http://efragtv.com/android/EB13-DUALFS-KERNEL.zip

When I go to "install zip from sdcard" it installs correctly and I reboot the phone. It just goes black after the samsung logo and vibrates a couple times, it eventually restarts and does the same thing.

I tried doing the recovery that was made, but it does the same thing.

I tried a factory restore and it has the same effect.

I installed Android 2.2 from Samsung's Zip.

I dont' mind taking it back to the factory settings because I'll try to root again...

Any suggestions?
Click to expand...

I tried the deodexed e13 rom but now it is stuck at the Samsung screen...
 
First of all its not bricked. Now far as the kernel goes this is very common as all chips are not same so based on voltage which can be low or stock for better power consumption which can cause problem and not even boot as it gets stuck on the logo.

I hope you had backed up using nandroid or have default kernel in SD so you can flash it over the current one. If not well then go download it hopefully someone has it posted in XDA which I am sure they do as you can't transfer it from phone you need to do it via USB card reader.

When you are testing do as I always do I never backup myself. But I keep rom.zip, kernel.zip, cwm.img in SDCard as I flash 2-3times a day and if something goes wrong takes 2min for me to get back.
 
HKM said:
First of all its not bricked. Now far as the kernel goes this is very common as all chips are not same so based on voltage which can be low or stock for better power consumption which can cause problem and not even boot as it gets stuck on the logo.

I hope you had backed up using nandroid or have default kernel in SD so you can flash it over the current one. If not well then go download it hopefully someone has it posted in XDA which I am sure they do as you can't transfer it from phone you need to do it via USB card reader.

When you are testing do as I always do I never backup myself. But I keep rom.zip, kernel.zip, cwm.img in SDCard as I flash 2-3times a day and if something goes wrong takes 2min for me to get back.
Click to expand...

Thanks for the clarification. I did a backup before I rooted, but restoring the backup gives me the same problem.

So I'm stuck at the samsung screen because the kernel is corrupted? What is the best way to restore functionality to this phone?

I see this thread when searching for an Epic Kernel:
http://forum.xda-developers.com/showthread.php?t=915344

I'm going to try one of these Kernels:
http://forum.xda-developers.com/showthread.php?t=967014

Should I restore this this phone to a custom rom or 2.1 and then retry the update to root? I'm not clear on how to restore the kernel. I've flashed several ROMS (DK28 and the EB13 deodexed) but everything just hangs on the Samsung screen.
 
Do you have any current rom.zip available in SDCard? If so do full wipe for data, cache, davlik. Then flash the rom.zip and get back to normal world and then from there go in to stable testing.

As I said if you don't have it then you have to download it and transfer it to SDCard via card reader. But this should take care of it as if it doesn't then you can revert back to the stock rom/radio using stock.img which is last resort which I don't recommend as it can revert the bootloader and root itself which should be your last resort if everything fails.

Clean wipe and reflashing the rom would take care of it. Been there so many times its not even funny :P believe it or not I flashed 20+ times in single day like just 3-4days ago as I was testing new kernel.
 
HKM said:
Do you have any current rom.zip available in SDCard? If so do full wipe for data, cache, davlik. Then flash the rom.zip and get back to normal world and then from there go in to stable testing.

As I said if you don't have it then you have to download it and transfer it to SDCard via card reader. But this should take care of it as if it doesn't then you can revert back to the stock rom/radio using stock.img which is last resort which I don't recommend as it can revert the bootloader and root itself which should be your last resort if everything fails.

Clean wipe and reflashing the rom would take care of it. Been there so many times its not even funny :P believe it or not I flashed 20+ times in single day like just 3-4days ago as I was testing new kernel.
Click to expand...

I installed the genocide Kernel and then tried to flash the Stock eb13 deodexed. Before I installed the stockeb13 I cleared the data, cache and dalvik twice. The Kernel seems to be installed fine it says it was successful and has the dev team logo. When I flash the eb13 deodex rom it still just stops on the samsung screen.

I tried installing the kernel and then rebooting. I tried installing the rom without rebooting. I'm getting the same effect each time. I don't know what I'm doing wrong and I'm going insane. :eek:

I just tried the same thing with the stock dual ssytem eb13 kernel and it still hangs on the samsung screen.

http://forum.xda-developers.com/showthread.php?t=964142%22


I'm using this page to get the Kernels.

Thanks for your help!
 
Penny_Man said:
I installed the genocide Kernel and then tried to flash the Stock eb13 deodexed. Before I installed the stockeb13 I cleared the data, cache and dalvik twice. The Kernel seems to be installed fine it says it was successful and has the dev team logo. When I flash the eb13 deodex rom it still just stops on the samsung screen.

I tried installing the kernel and then rebooting. I tried installing the rom without rebooting. I'm getting the same effect each time. I don't know what I'm doing wrong and I'm going insane. :eek:

I just tried the same thing with the stock dual ssytem eb13 kernel and it still hangs on the samsung screen.

[KERNEL] Stock EB13 Dual Filesystem [EXT4/RFS] Kernel! - xda-developers


I'm using this page to get the Kernels.

Thanks for your help!
Click to expand...

I'm going to try this:

[Stock Flash][CWM]ReRFS.Format.ROM.DK28 to revert back to RFS from ext4 - xda-developers

If that doesn't work I guess I'll have to use Odin to restore the stock images.

How come nothing ever goes smooth?????
 
Glad to see you are back on track and it all worked out in the end. I myself lol fall asleep so couldn't reply as I was up drinking and watching sopranos online.
 
Penny_Man said:
I can only get to the clockwork 3.0.0.6 Recovery screen. I have the Default Stock Dual FS kernel For EB13 installed on my sd card.

http://efragtv.com/android/EB13-DUALFS-KERNEL.zip

When I go to "install zip from sdcard" it installs correctly and I reboot the phone. It just goes black after the samsung logo and vibrates a couple times, it eventually restarts and does the same thing.

I tried doing the recovery that was made, but it does the same thing.

I tried a factory restore and it has the same effect.

I installed Android 2.2 from Samsung's Zip.

I dont' mind taking it back to the factory settings because I'll try to root again...

Any suggestions?
Click to expand...

I don't have the Epic, but it really doesn't sound like you're bricked.

I got the Evo and last week I ran into a similar problem like yours. If you can get into Recovery or do just about anything else on your phone, 99.9% sure that you are not bricked and it is a fixable issue. Most of the time now, it seems harder and harder to get into a straight brick that will completely ruin your device beyond repair. Anyway...last week I accidentally uploaded Amon-Ra Recovery but forgot to backup before flashing a ROM and coincidentally, the ROM I was using didn't want to load, so I was stuck either going into Recovery or HBOOT.

What I did was take out the SD card and put it into a USB adapter and connect it to my computer and put on ClockWork Recovery onto the card then go back into HBOOT and install CWM and BAM!...I was back into my original state.

I don't know about Epics, but people with Evos told me that ClockWork is terrible and if I was to use any version, not to use 3.0.0.0.

Anyway, moral of the story, keep backups handy and if you have a backup anyway or can only get into Recovery or HBOOT, it's a fixable problem. Hopefully some Epic expert can help.
 
You must log in or register to reply here.
Back
Top Bottom