Database Info

[ROM][STOCK]ReRFS Format Stock ROM EC05 v1.01 w/ CWM3.1.0.1

NOTICE: If you have flashed any ROM, including CyanogenMod, that has converted the phone to MTD (yaffs2 filesystem), then this will not work. I abandoned ReRFS when MTD became the standard for CyanogenMod for the Epic. Only ODIN can be used to restore the phone to RFS from MTD.
The purpose of this ROM is to format the Epic 4G back to RFS, and give a stock EC05 system. Most current ROMs format ext4, and this will bring it back to RFS. This flashes a stock odexed EC05 system, stock EC05 kernel, and ClockworkMod 3.1.0.1 Purple Edition. This can be flashed from either cwm2 for cwm3, and can even be used as a stock ROM on phones already formatted as RFS.
Updated to cwm 3.1.0.1, and as long as your current reboot recovery boots to cwm 3.0.2.5 or 3.1.0.1, ReRFS can be flashed using ROM Manager.
Todo: I'd like to kang chris41g's autoconvert scripts for an automatic backup portion before flashing... I haven't been able to reach him lately, and I'd like his permission before using his script.
This does not touch the modem... use odin to flash the EC05 modem, or use the zip library of tools for ClockworkMod for the epic below, including modem flashes for oder stock modems, stock kernels, and stock recoveries.
IMPORTANT: Make a backup before flashing this- it will format everything on the phone, and destroy all data. It does not touch the sdcard. As with any tool here, I can't be held responsible for any trainwreck that happens to your phone.
I would highly recommend powering off the phone, and booting into cwm with vol down, camera, and power button combo. In recent testing, I've successfully been able to flash ReRFS with ROM Manager with Clean Kernel, as long as reboot recovery brings you to cwm 3.0.2.5 or greater, ROM Manager shouldn't pose any troubles. In the event of flash failure, read the next paragraph.
If for some reason the flash doesn't take, and the phone will not boot afterwards, then perform a 4 finger boot (Vol up + Vol down + camera + power), and flash the ROM again. I haven't needed to do this in my testing, but formatting RFS can be buggy at times, and a reflash of the ROM should take care of it.
If you need to turn in the phone for service or exchange, then flash the ReRFS ROM, and make sure the phone boots. Then go back to ClockworkMod with the 3 finger boot, and flash the Samsung stock recovery, to uninstall ClockworkMod. Only flash the Samsung stock recovery if you need to turn in the phone.
I extend a very special thanks to supercurio- without his voodoo lagfix source, I wouldn't have known the proper fat.format usage, and a trick to write zeros to the system partition before formatting. The exact source is here:
https://github.com/project-voodoo/lagfix/blob/stable/voodoo_initramfs_parts/scripts/rfs_formatter.sh
Thanks to: bikcmp for fossnet server space, and Shabbypenguin for graciously hosting files as mirrors.
Link:
ReRFS Format Stock ROM EC05 v1.01
Tools:
epic4g.stock.recovery.ec05.zip
The Samsung stock recovery, for uninstalling ClockworkMod, useful for turning in the phone to Sprint.
Do not flash the stock recovery unless your phone boots into system, and you need to turn the phone in.
modem.DI18toEC05.zip
update modem from DI18 to EC05, particularly important, coming from DI18
modem.EB13toEC05.zip
modem from EB13 to EC05
modem.DI07toDI18.zip
modem from DI07 to DI18
kernel.stock.EC05.epic4g.zip
Just the stock EC05 kernel by itself, if it's ever needed
DRockstar.Clean.Kernel.EC05.v1.05.zip
Flash this kernel to have root and busybox, this kernel has reboot recovery to cwm 3.1.0.1, and is ROM Manager compatible.
Support:
Either here in the forum, or live at irc.fossnet.info channel #epic
Weblink: http://webchat.fossnet.info/?channels=epic

I support this post! This is incredibly useful if you don't have USB access and need to stock your device before sending it in.

good work man, this is very nice for people looking to replace odin
Edit: omg it sexs me up

To you, sir, I give thanks. You have done a great service to this community.

Awesome work bro. I'm having g some trouble with my phone connecting to any usb. Even to charge. I think its going bad and this I'd awesome if it completely goes out I can still get to stock. Awesome work
Sent From My Evo Killer!!!

musclehead84 said:
Awesome work bro. I'm having g some trouble with my phone connecting to any usb. Even to charge. I think its going bad and this I'd awesome if it completely goes out I can still get to stock. Awesome work
Sent From My Evo Killer!!!
Click to expand...
Click to collapse
I posted a thread about this in General, give a search and try my 'fix'. It might work for you.

k0nane said:
I support this post! This is incredibly useful if you don't have USB access and need to stock your device before sending it in.
Click to expand...
Click to collapse
shabbypenguin said:
good work man, this is very nice for people looking to replace odin
Click to expand...
Click to collapse
You are both so correct on those comments.
I know there will be many happy users once they find this. Going to put this on my card for safe keeping just incase, you know.. The USB takes a dump which at some point it seems to happen to all frequent flashers...

Wow good stuff Rockstar. Great alternative to Odin if you want to restore to stock EC05.

Put the Samsung stock recovery in the tools section of the post...
Flash this with ClockworkMod, to uninstall ClockworkMod, in case the phone needs to be turned in with factory recovery.
If you need to turn in the phone, then flash the ReRFS ROM, and make sure the phone boots. Then go back to ClockworkMod with the 3 finger boot, and flash the Samsung stock recovery, to uninstall ClockworkMod.

Thank u thank u thank u. This made my day as i just started today updating my wife's epic from dk28. I used the ec05 and the kernel and her phone finally is nice to use. No matter how clean of an install it always had some issue. I loathed it, but now she and I am very happy w a 100% functioning phone w 0 problems.

How about a stock ec05 kernal for folks that have a custom kernel, but not a custom rom. That way I don't have to lose all my settings with a complete wipe and I will still be able to take my phone into Sprint.
Thanks for a great job.
Sent from my SPH-D700 using XDA Premium App

sonjohn1 said:
How about a stock ec05 kernal for folks that have a custom kernel, but not a custom rom. That way I don't have to lose all my settings with a complete wipe and I will still be able to take my phone into Sprint.
Thanks for a great job.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
You should be able to perform a backup with ClockworkMod before performing this flash. Reboot into android, and check to see that the backup is there in /sdcard/clockworkmod/backup.
After the ReRFS ROM is performed, reboot, and then shut down. 3 finger boot into ClockworkMod 2.5.1.0. Choose mounts and storage > advanced > {select backup} > restore data.
Alternatively, you can use MyBackup Root, available free from the market, and use that. My rooted kernel is also posted in this thread, that you can flash for that purpose.
I will also post the stock kernel by itself for you, and that will be part of my ClockworkMod tools release, with all of the flashes I've made and collected.
Hope this helps!

sonjohn1 said:
How about a stock ec05 kernal for folks that have a custom kernel, but not a custom rom. That way I don't have to lose all my settings with a complete wipe and I will still be able to take my phone into Sprint.
Thanks for a great job.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
For a stock kernel check out this thread post#8.
http://forum.xda-developers.com/showthread.php?t=1006894&highlight=dangdang

DRockstar, you da man! Many thanks.
Sent from my SPH-D700 using XDA Premium App

sonjohn1 said:
How about a stock ec05 kernal for folks that have a custom kernel, but not a custom rom. That way I don't have to lose all my settings with a complete wipe and I will still be able to take my phone into Sprint.
Thanks for a great job.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Just so you know, most custom kernels currently published (if not all) still make changes to the system files that would prevent OTA updates, and leave tell tale signs of rooting in the system.
In the event that you really needed to turn in the phone, I would do the following:
* Perform a backup with both ClockworkMod and MyBackup Root (just in case)
* Flash ReRFS ROM
* Boot into cwm > backup and restore > advanced restore > {choose backup} > restore data (optional, may work well, may cause force closes)
* From cwm, flash the Samsung stock recovery, in Tools section of this post, to uninstall cwm, and eliminate all signs of tampering
Just wanted to make that clear... Even the cleanest of custom kernels still leave traces when flashing the stock kernel. Even though my Clean Kernel should allow OTA updates to occur once the stock kernel is flashed again, if I really needed to turn in the phone for some reason, I would do the steps I just laid out.
Hope that clarifies some things.

This helps tremendously. Thanks again.
Sent from my SPH-D700 using XDA Premium App

Xda app thanks button!
Drockstar, you should put the md5 of the file in the OP. Well cuz you know downlaods get messed up at times and seeing how this is a "fix it kind of tool/rom" so to say
Sent from my ComBadge..

This is exactly what I was hoping to find. I had no problems with flashing this and so far it works perfectly. I am really stoked because I recently broke my usb cable and haven't picked up another yet. Thank You!!

Unreal...we have been around wifi mostly but for 6 hours on 3g. This makes me very happy. Battery is at 53% and this is an ec05 epic 4g
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Links dont work for any of the downloads... says there has been too much traffic, or something along those lines.

[Q]Where do I find a full stock rom of 2.3.3 for my i9023, xxxKB3, GRI54?

Hi guys,
Anyone could guide me to where can I find the source to download the full stock rom for the I9023, xxxKB3, GRI54 so that I can flash this into my phone and overwrite my current CM7 before manually flashing to 2.3.4's stock rom and then reroot it again. Will really appreciate it.
Stan.

There is a full 2.3.4 rom available for your phone.

the "released" link under I9023 has a full rom file in this thread.

Issue is I'm currently rooted and on CM7's rom which means I can't just apply the 2.3.4 full rom over it, it won't work this way. Thus I need to flash my phone back to the stock 2.3.3 rom but I can't seem to find one for my phone
Sent from my Nexus S using XDA App

Stanlehh said:
Issue is I'm currently rooted and on CM7's rom which means I can't just apply the 2.3.4 full rom over it, it won't work this way. Thus I need to flash my phone back to the stock 2.3.3 rom but I can't seem to find one for my phone
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
hmm.. i think a full rom is a stock rom.. it will prolly wipe everything, but bring you to stock 2.3.4.
i only read about needing a stock rom when _updating_ with an update file, which is way smaller..
i poested that in the sticky for the otas.. maybe wait, if someone else confirmes that =)
edit: i don't think rooted is a problem, i was rooted myself. it just was gone when i applied the full rom.

so I should try getting the full rom for my 9023, gri54 and just apply update from sdcard at recovery?
After apply CM7'S rom, I noticed my build changed to gri40, will it affect? The available rom for the 9023 is meant for gri54 only
Sent from my Nexus S using XDA App

Stanlehh said:
so I should try getting the full rom for my 9023, gri54 and just apply update from sdcard at recovery?
After apply CM7'S rom, I noticed my build changed to gri40, will it affect? The available rom for the 9023 is meant for gri54 only
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
well, i think it doesn't matter what you have right now, since it's a full rom, not an update. so cm7 well be gone after install and you have a pure android rom.
so either if you are on gri40 or gri54 it doenst matter, cause you will be grj22 afterwards, as long you have an i9023.
before this full rom came up, some ppl downgraded to gri40, in order to use the update grj22-from-gri40. an update requires the correct version installed, but not when using a full rom.
and yeah, just use recovery and install from sd-card. root will be gone and you be having stock recovery again.
hope that helps..

This definitely helped alot.! So I just format /data and /cache and I'm good to go ahead and flash?
Sent from my Nexus S using XDA App

Stanlehh said:
This definitely helped alot.! So I just format /data and /cache and I'm good to go ahead and flash?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
i don't think u even need to do that.. flashing that rom should wipe everything..
at least i think so.. anyway, since u are going from cm7 to stock rom, ur system is gonna be new..
let me know if it worked!
don't forget, if wann root again afterwards, u need to flash a custom recovery again!

eGozelle said:
i don't think u even need to do that.. flashing that rom should wipe everything..
at least i think so.. anyway, since u are going from cm7 to stock rom, ur system is gonna be new..
let me know if it worked!
don't forget, if wann root again afterwards, u need to flash a custom recovery again!
Click to expand...
Click to collapse
my only worry is that after reading about in the forums. After flashing the full 2.3.4's rom onto my phone and thereafter flashing CWM into it again, it won't stay permanently. Any ideas how to go about solving this?

Locking and unlocking the bootloader again should reset the phone to stock rom and factory defaults, wouldn't it?

MrNago said:
Locking and unlocking the bootloader again should reset the phone to stock rom and factory defaults, wouldn't it?
Click to expand...
Click to collapse
not sure, need someone to clarify this.

Stanlehh said:
my only worry is that after reading about in the forums. After flashing the full 2.3.4's rom onto my phone and thereafter flashing CWM into it again, it won't stay permanently. Any ideas how to go about solving this?
Click to expand...
Click to collapse
didn't realise that cwm recovery will be gone afterwards, since i still was able to flash superuser file with cwm. just saw i'm back to stock recovery ;b
found the same as u did in the guide sticky thread to work around that
so did flash the full rom already?

MrNago said:
Locking and unlocking the bootloader again should reset the phone to stock rom and factory defaults, wouldn't it?
Click to expand...
Click to collapse
If you are running CM7 at the moment, stock ROM won't magically appear just because you did lock/unlock.
It will sure wipe data/SD clean, but stock ROM can't just pop up out of no where
Stanlehh said:
not sure, need someone to clarify this.
Click to expand...
Click to collapse
Just format your /system partition, wipe data/factory reset, wipe dalvik, then install 2.3.4 full ROM. To make CWM stick, you have 2 options
1) Without rebooting after you flashed 2.3.4, stay in CWM, use adb
Code:
adb remount
adb root
adb shell mv /system/etc/install-recovery.sh{,.bak}
or you can delete it if you want...I did
adb shell rm /system/etc/install-recovery.sh
2) Root -> reboot -> install ROM Manager -> install CWM -> delete/move /system/etc/install-recovery.sh

ClockRecovery version5

I updated to Clockwork Recovery. Now my phone is stuck on HTC boot screen. I cant even recover my back up's. it keeps getting stuck on boot screen. Nothing is working. What can I do? Is it bricked? Can someone hook me up? thanks

I don't know if I'm replying too late, but here's what I did.
Hold volume button down while turning the phone on. You'll get the white bootloader screen w/ skating androids and then just scroll til you see the "Recovery" option. Highlight and push the power button.
Reinstall your nandroid backup.
Once you can, double check RomManager to see if it's actually upgraded.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The version numbers should match this image. Clockworkmod RECOVERY 5.0.1.0.

reynaldorivera said:
I updated to Clockwork Recovery. Now my phone is stuck on HTC boot screen. I cant even recover my back up's. it keeps getting stuck on boot screen. Nothing is working. What can I do? Is it bricked? Can someone hook me up? thanks
Click to expand...
Click to collapse
Did you try holding volume down and the power button when powering on the phone? You can get to recovery from the bootloader. If that doesn't work, I think your only opton would be reflashing recovery via fastboot.

You may have an older version of rom manager. To get clockwork 5 to work when I flashed it I had to update my rom manager. This happened today I tried to flash miui to review it and it told me I needed new rom manager. But since your stuck on boot screen your other options would be flash a recovery via fastboot OR run a flash with Cmd prompt (assuming you are on windows)
Sent from my Nexus S 4G using Tapatalk

I just installed CM7RC1.7 and now my phone won't boot nothing but the CM7 rom. I keep getting hung up in the white boot screen. I was trying to use a nandroid of sense to get the GPS working with CM7. So have i punched a one way ticket to CM7 or what? How do get my sense nandroid to load? Im on the most current CWR, so im baffled now. I even tried to just install a sense rom instead of going back to an nandroid. Same result, stuck at boot screen, unless i restore that nandroid of CM7 i just installed.

bamaredwingsfan said:
I just installed CM7RC1.7 and now my phone won't boot nothing but the CM7 rom. I keep getting hung up in the white boot screen. I was trying to use a nandroid of sense to get the GPS working with CM7. So have i punched a one way ticket to CM7 or what? How do get my sense nandroid to load? Im on the most current CWR, so im baffled now. I even tried to just install a sense rom instead of going back to an nandroid. Same result, stuck at boot screen, unless i restore that nandroid of CM7 i just installed.
Click to expand...
Click to collapse
If clockwork is your recovery than you can try to install a backup straight from your recovery in bootloader instead of running your phone. Can you get into your recovery
Sent from my Nexus S 4G using Tapatalk

bamaredwingsfan said:
I just installed CM7RC1.7 and now my phone won't boot nothing but the CM7 rom. I keep getting hung up in the white boot screen. I was trying to use a nandroid of sense to get the GPS working with CM7. So have i punched a one way ticket to CM7 or what? How do get my sense nandroid to load? Im on the most current CWR, so im baffled now. I even tried to just install a sense rom instead of going back to an nandroid. Same result, stuck at boot screen, unless i restore that nandroid of CM7 i just installed.
Click to expand...
Click to collapse
I can't get any sense rom to work but all AOSP ones do so I think we are in the same boat... I get bootloops on all sense roms...

bamaredwingsfan said:
Im on the most current CWR, so im baffled now.
Click to expand...
Click to collapse
Some people were having trouble getting the CWR to stick yesterday. Are you certain it updated properly to the new blue 5.0.1.0? If you think the CWR is the problem, you could try to downgrade it before flashing the Sense Rom. Try this link

perhaps the sense roms are not compatiable yet with the latest recovery. that would be my guess.

yareally said:
perhaps the sense roms are not compatiable yet with the latest recovery. that would be my guess.
Click to expand...
Click to collapse
Yea I just tried it again... :-( I miss sense...

I had to install a fresh from download ROM manager then download cwm 4.0 and recovery worked fine. Somethin is weigh with 5.xx
Sent from my thunderbolt using Forum Runner

dms76 said:
I had to install a fresh from download ROM manager then download cwm 4.0 and recovery worked fine. Somethin is weigh with 5.xx
Sent from my thunderbolt using Forum Runner
Click to expand...
Click to collapse
5.xx is working fine on my phone. Plus I like the blue color he used this time. It might be buggy for other phones but on mine it works like a charm
Sent from my Nexus S 4G using Tapatalk

Have you tried a restore yet?
Sent from my thunderbolt using Forum Runner

dms76 said:
Have you tried a restore yet?
Sent from my thunderbolt using Forum Runner
Click to expand...
Click to collapse
I've done a backup and restore. Working fine for me. I do not use ROM manager. Only do backups from cwm. Flashed 5.0.1.0 from hboot. Downloaded the zip from Absolute_Zero's thread in the development section.

yareally said:
perhaps the sense roms are not compatiable yet with the latest recovery. that would be my guess.
Click to expand...
Click to collapse
Shouldn't be the case. At the point that recovery is running, the ROM itself has NO relevance. The ROM and recovery do not run at the same time. It's like the BIOS on a PC - while it's running, Windows, Linux, etc is NOT running.

Hey all . I had the same problem the new version of clockwork will not backup or restore . I had to flash a fresh ROM also to get booted up then downgrade clockwork again. I also noticed that the backups I tried to restore the img files were turned to tars . What up with that ?
Sent from my ADR6400L using XDA App

Jorge330823 said:
If clockwork is your recovery than you can try to install a backup straight from your recovery in bootloader instead of running your phone. Can you get into your recovery
Sent from my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
Cyanogen doesn't support recovery before version 4, but I never searched for the reason. I assume the install script for it.

hallstevenson said:
Shouldn't be the case. At the point that recovery is running, the ROM itself has NO relevance. The ROM and recovery do not run at the same time. It's like the BIOS on a PC - while it's running, Windows, Linux, etc is NOT running.
Click to expand...
Click to collapse
It is the case I can confirm. Also some roms have been known in the past to not work with certain versions of recovery so this is nothing new. I went back to 4.x and sense roms work again.

Ok, managed to get back to a sense rom. I looked up the app version of CWR and it was not the most current it was 03 instead of 05. So i updated the app an had the most current recovery(blue one) and tried to restore my nandroid of sense to get out of CM7 Same result, white brick until i wipe everything an restore the CM7 nandroid. Being baffled, i tried some different combinations, but it was getting late, so i had to stay on CM7. Go to work today, and CM7 is just not cutting it, BT was all over the place. So this time i deleted my Ti backup of CWR, an installed new an fresh. Reinstalled the recovery just to make sure everything was the most current. Thank god before i went to bed last night, i copied over a zip of gingeritis3D as a just incase if all else fails. Well, all else failed, so i had to try a fresh install of a new rom instead of going to a nandroid backup. That failed too. One last try, an here is what worked. I wiped everything but dalvic an did the fresh install of gingeritis3D, an bingo, the phone booted! I was never so happy to see sense as i was at that moment. I then preceeded to delete any an everything off my phone that pertained to CM7. I never had a single problem until i installed that CM7 1.7 rom on my phone. Im not saying that is what caused my problem, but something did. Right now im mainly leaning toward the wiping of the dalvic that was causing most of the trouble. Guess we will see in a few days when i try a different sense rom.

i hope a stable build comes soon.

[HOWTO] GB to ICS OTA for Rooted Stock - Keep your data (Revolutionary hboot only)

Provided you meet the prerequisites, this is an easy way to safely update from 2.11.695.19 Gingerbread to 7.02.605.06 to 7.02.605.10 Ice Cream Sandwich via the new OTA and keep root. I have also modified the stock kernel to allow adb remount so you can push/pull files directly from the command line without needing to drop into adb shell. If you do not have the correct Revolutionary hboot or have modified your Gingerbread system files then skip this guide and flash a rooted stock build from the development forum.
ONLY for users with S-OFF revolutionary hboot and running rooted stock. DO NOT USE THIS GUIDE IF YOU ARE HTCDEV UNLOCKED OR HAVE CHANGED OR DELETED ANY OF THE STOCK SYSTEM FILES. FLASH THE RADIO AND FULL ROM INSTEAD.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
REQUIRED Prerequisites:
Revolutionary hboot with S-OFF
Rooted Stock ROM with NONE of the system files missing or changed
Get the files:
- Save the stock recovery image to your fastboot directory: Stock recovery (use the same as your ROM build, 2.11.695.19) or attached below
- Save the custom recovery image of your choice to your fastboot directory: TWRP or CWM
- Optional Superuser or SuperSU recovery flashable .zip package if OTA rootkeeper did not work
- Optional insecure boot.img attached below
Steps:
1) Set your Superuser app for OTA survival mode
2) Reboot into bootloader
If your bootloader does not have "Revolutionary" across the top, STOP immediately. If you take the OTA, you will end up with a locked bootloader.
3) Flash stock recovery
Code:
fastboot flash recovery name_of_stock_recovery.img
4) Reboot, check for the first firmware update and download.
5) Apply update. It should reboot a few times and then reboot back into system when done. Check for the second OTA and download.
6) Apply update. It should reboot a few times and then reboot back into system when done.
7) Reboot into bootloader
8) Flash TWRP or CWM recovery
Code:
fastboot flash recovery name_of_custom_recovery.img
9) Copy the superuser install .zip to the root of your sdcard
10) Reboot into recovery and flash the superuser update package
Optional for insecure boot ie: adb remount works:
1) Download mecha_insecure_boot.img to your fastboot directory
2) Reboot into bootloader
3) Flash:
Code:
fastboot flash boot mecha_insecure_boot.img
Secure boot attached if you want to go back.
Code:
fastboot flash boot mecha_secure_boot.img
Once you are done, your Thunderbolt will have the current ICS rom with data intact, the new radio, working superuser, custom recovery and insecure boot for "adb remount" if wanted.

This looks good, have people had success with it yet? I don't want to lose my data by trying to unroot, but I am already sitting with rooted stock with the 2.11.605.19 recovery installed.

I've seen posts of Hboot 6.04.1002
When I go into hboot, I see
****UNLOCKED***** (in pink back ground)
MECHA XD SHIP S-OFF
HBOOT-1.04.0000
I thought I used the Revolutionary tool a while back to get S-OFF. I know my Hboot hasn't changed as I flashed RUU's or OTA's in the past.
Does it matter than I have what appears to be a lower/older HBOOT?

Looks simple enough. I am going to try this on my wifes tbolt tonight.

Re: [HOWTO] Apply ICS OTA to Rooted Stock (Revolutionary hboot only)
Tiezane said:
This looks good, have people had success with it yet? I don't want to lose my data by trying to unroot, but I am already sitting with rooted stock with the 2.11.605.19 recovery installed.
Click to expand...
Click to collapse
So far just me that can confirm this works. I did not wipe at first but ended up doing a factory reset after everything was said and done anyway. There are always bits and pieces of old data that are not quite right going between major versions like this.
KidJoe said:
I've seen posts of Hboot 6.04.1002
When I go into hboot, I see
****UNLOCKED***** (in pink back ground)
MECHA XD SHIP S-OFF
HBOOT-1.04.0000
I thought I used the Revolutionary tool a while back to get S-OFF. I know my Hboot hasn't changed as I flashed RUU's or OTA's in the past.
Does it matter than I have what appears to be a lower/older HBOOT?
Click to expand...
Click to collapse
I can only confirm this worked for me on the Revolutionary hboot. Not going to speculate on others. If the version number in the OTA is higher, it probably will replace what you currently have.

Instructions in the OP should work just fine. Thank you kpetrie77 for providing this guide.
However for anyone timid to try this, you may wanna know that I have a stock rooted, deodexed version about to upload.

Re: [HOWTO] Apply ICS OTA to Rooted Stock (Revolutionary hboot only)
A CWM flashable zip would have been nice to have last night! This goat rope is pretty much the same process I used on the G2 and MyTouch. No patience so went with what I know and sharing how I did it.

kpetrie77 said:
A CWM flashable zip would have been nice to have last night! This goat rope is pretty much the same process I used on the G2 and MyTouch. No patience so went with what I know and sharing how I did it.
Click to expand...
Click to collapse
Haha yeah I agree, however I spent last night getting it made up.
Didn't finish till this am.
But truly thank you for sharing this alternate method of keeping root and updating.
I'm sure it's much appreciated by many.
Upload is about halfway...

santod040 said:
Instructions in the OP should work just fine. Thank you kpetrie77 for providing this guide.
However for anyone timid to try this, you may wanna know that I have a stock rooted, deodexed version about to upload.
Click to expand...
Click to collapse
Call me timid.....
Thanks in advance santid040.

santod040 said:
Instructions in the OP should work just fine. Thank you kpetrie77 for providing this guide.
However for anyone timid to try this, you may wanna know that I have a stock rooted, deodexed version about to upload.
Click to expand...
Click to collapse
At the risk of sounding like a complete n00b (which I feel like anyway)... will the version you are uploading be run as an update, and therefore maintain data on the phone, or is it going to wipe what I have there now?

Tiezane said:
At the risk of sounding like a complete n00b (which I feel like anyway)... will the version you are uploading be run as an update, and therefore maintain data on the phone, or is it going to wipe what I have there now?
Click to expand...
Click to collapse
It's a full rom install.
But I did not set it up to wipe data.
That doesn't mean it will play well if you don't format first, but you can try.
It's posted HERE

KidJoe said:
I've seen posts of Hboot 6.04.1002
When I go into hboot, I see
****UNLOCKED***** (in pink back ground)
MECHA XD SHIP S-OFF
HBOOT-1.04.0000
I thought I used the Revolutionary tool a while back to get S-OFF. I know my Hboot hasn't changed as I flashed RUU's or OTA's in the past.
Does it matter than I have what appears to be a lower/older HBOOT?
Click to expand...
Click to collapse
Apparently I had an OLD "permanent hboot with S-OFF that was made to not be overwritten.
I chickened out on trying to update. Instead, I reverted from the OLD "permanent" hboot to the old eng 1.40.2000 s-off hboot which could be over written. Then flashed with the 2.11.605.5 RUU to get back to S-ON, and Used Revolutionary to get S-OFF & Root.
So I now have the Revolutionary S-OFF hboot 6.04.1002 and will be upgrading from here.

santod040 said:
It's a full rom install.
But I did not set it up to wipe data.
That doesn't mean it will play well if you don't format first, but you can try.
It's posted HERE
Click to expand...
Click to collapse
I read this post while installing and wiped data/factory reset after installing (without booting first). Will this have the same effect as doing so before installing? Or should I wipe and install again?

Dropbox temporarily suspended... Oops.

lukesed said:
I read this post while installing and wiped data/factory reset after installing (without booting first). Will this have the same effect as doing so before installing? Or should I wipe and install again?
Click to expand...
Click to collapse
As an answer to my own question... I wasn't able to log in to my google account. I did a full wipe and installed again, and now it does work.

I have come to the conclusion that rooting is for people much smarter and with much more time than me. I'm hopelessly confused. I will never root my phone again becasue I simply don't enjoy spending my whole damn night figuring this stuff out... but since my current phone IS rooted and I want the ICS update I have to deal with this migrane.
I appreciate this OP ... but the first thing it says to do is to get the mecha android 3e recovery rom or whatever it is... and when I click that link it takes me to another forum with files all over the place, none of which are called that. What exactly am I supposed to download?
Thanks!

Re: [HOWTO] Apply ICS OTA to Rooted Stock (Revolutionary hboot only)
Good point, updated the OP. Use the stock recovery from Scotty's thread (linked) that matches the ROM version your are on.
Settings > About phone > Software
If on 2.11.605.09 then use the matching 2.11.605.09 recovery. If running 2.11.605.19 rom use 2.11.605.19 recovery.

jdport said:
I have come to the conclusion that rooting is for people much smarter and with much more time than me. I'm hopelessly confused. I will never root my phone again becasue I simply don't enjoy spending my whole damn night figuring this stuff out... but since my current phone IS rooted and I want the ICS update I have to deal with this migrane.
I appreciate this OP ... but the first thing it says to do is to get the mecha android 3e recovery rom or whatever it is... and when I click that link it takes me to another forum with files all over the place, none of which are called that. What exactly am I supposed to download?
Thanks!
Click to expand...
Click to collapse
If you are rooted, why not flash the stock rooted ICS rom?

santod040 said:
If you are rooted, why not flash the stock rooted ICS rom?
Click to expand...
Click to collapse
Because I have no idea how. I'm a complete newbie to this. I got through the rooting process because the nice scripts that were written were easy for even me to follow.... the only reason I rooted at all was so that I could get a proper backup with titanium. I wish now I had not rooted because I am absolutely clueless on how this stuff works. Of course if I unroot, it wipes my phone and I can't restore... without rooting again. lol. I just want to get the update installed without screwing up my phone.... whatever it is I have to do to do that. Unfortunately I really can't seem to find a resource that explains all of this. I've been reading all night and at this point my head is starting to hurt and i'm not much closer to the solution than when I started.

jdport said:
Because I have no idea how. I'm a complete newbie to this. I got through the rooting process because the nice scripts that were written were easy for even me to follow.... the only reason I rooted at all was so that I could get a proper backup with titanium. I wish now I had not rooted because I am absolutely clueless on how this stuff works. Of course if I unroot, it wipes my phone and I can't restore... without rooting again. lol. I just want to get the update installed without screwing up my phone.... whatever it is I have to do to do that. Unfortunately I really can't seem to find a resource that explains all of this. I've been reading all night and at this point my head is starting to hurt and i'm not much closer to the solution than when I started.
Click to expand...
Click to collapse
If you are already rooted, go to my thread, click the link.
Sign into the InfectedROM forums, and grab the stock rom, full or debloated, your choice.
Flash it in Recovery like any other custom rom and reboot.
DONE! Stock ICS rooted... :good:

Hard brick? Soft brick? I need help

Please treat a newb gently...
I rooted my phone earlier tonight, followed all the instructions here, and everything went well. I flashed cwm recovery (I was most comfortable with it from an old phone.)
The first thing I did was back up my stock configuration for future use.
I then rebooted and started removing some bloatware. (The real reason I wanted to root.) I got a little overanxious and removed one app I decided I wanted back, so I rebooted to recovery and restored my backup with no problem.
Then, my phone wouldn't boot up out of recovery. So, I removed the battery and tried a simple boot - no luck. To make a long story short, I've booted to recovery multiple times. I've wiped and restored multiple times. No matter what I do though, the phone will not boot to anything but recovery.
Help!

Sounds a bit like the bootloader didn't unlock.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/url]

How can I fix it?

butch50 said:
How can I fix it?
Click to expand...
Click to collapse
Ezunlock 1.2... Do you still have root?
Sent from my SCH-I535 using xda premium

Correct me if I'm wrong, but Ezunlock requires me to boot to the ROM. I can only boot to cwm recovery.
And yes, I rooted before trying to unlock the bootloader.

Sounds to me like you need to odin back to stock and start over. Guessing you didn't get the bootloader unlocked.

blackwolf77 said:
Sounds to me like you need to odin back to stock and start over. Guessing you didn't get the bootloader unlocked.
Click to expand...
Click to collapse
I've been away from a computer for a couple of days, but that's what I did. Worked like a charm, thanks.

Followed [GUIDE] Root for Jelly Bean 4.1.1 or 4.1.2, cannot mount sdcard to get .tar
blackwolf77 said:
Sounds to me like you need to odin back to stock and start over. Guessing you didn't get the bootloader unlocked.
Click to expand...
Click to collapse
I followed the directions exactly on this excellent xda site's "[GUIDE] Root for Jelly Bean 4.1.1 or 4.1.2" with all the correctly downloaded and installed files but when I get to "Step 4 - Rooting Your Device and Unlocking Your Bootloader Quote: Using your custom recovery flash the download you chose above from Step 1 (#3)"
I go to "install zip from sdcard" and I select it, and go to "choose zip from sdcard" I get "E: Can't mount / sdcard/".
So what does one do to "odin back to stock and start over"? Are the sequences of the steps in that guide in correct order? Thanks.

boldred said:
I followed the directions exactly on this excellent xda site's "[GUIDE] Root for Jelly Bean 4.1.1 or 4.1.2" with all the correctly downloaded and installed files but when I get to "Step 4 - Rooting Your Device and Unlocking Your Bootloader Quote: Using your custom recovery flash the download you chose above from Step 1 (#3)"
I go to "install zip from sdcard" and I select it, and go to "choose zip from sdcard" I get "E: Can't mount / sdcard/".
So what does one do to "odin back to stock and start over"? Are the sequences of the steps in that guide in correct order? Thanks.
Click to expand...
Click to collapse
To clarify after you flashed the bootchain through Odin did you then proceed to the step to flash a custom recovery? If you did, at the end of the custom recovery step did you wind up in recovery and do you have the SuperSU .zip on your phone? Keep in mind those instructions in that thread and the recovery image should work but are outdated. If things still don't work for you I would Odin back to stock to give yourself a fresh slate and then check out beanstown106's 1-click CASUAL package that will painlessly root, unlock your bootloader, and flash custom recovery for you.

blackwolf77 said:
Sounds to me like you need to odin back to stock and start over. Guessing you didn't get the bootloader unlocked.
Click to expand...
Click to collapse
shimp208 said:
To clarify after you flashed the bootchain through Odin did you then proceed to the step to flash a custom recovery? If you did, at the end of the custom recovery step did you wind up in recovery and do you have the SuperSU .zip on your phone? Keep in mind those instructions in that thread and the recovery image should work but are outdated. If things still don't work for you I would Odin back to stock to give yourself a fresh slate and then check out beanstown106's 1-click CASUAL package that will painlessly root, unlock your bootloader, and flash custom recovery for you.
Click to expand...
Click to collapse
Thank you for your reply.
Yes, I did have the SuperSU zip on the sdcard in the phone but I got the error message and continue to do so even after formatting two different sdcards, using the CWM that was installed. The sdcards won't mount in the phone. I can still use the phone (it's one week-old now) but the "custom" screen now appears when turning it on. I'd just like to get the stuff off of the phone that I put on there during this botched process. Apparently, after reading about this situation, this problem appears to be that the CWM corrupts itself and has to be uninstalled, re-installed, uninstalled and etc. until it finally correctly does it what it was supposed to do. This seems too risky now. This is an expensive phone and I thought that I had selected the best option for rooting, unlocking the bootloader and installing a ROM after searching for a week, so I was prepared for problems. I've rooted/unrooted devices before. But I wasn't prepared for this kind of error at this level. I still may try it using TWRP Recovery 2.4.3.0 rather than the ClockworkMod Touch Recovery 6.0.2.3. But, first, I need to know how to get back "to stock" -- the way it was before I tried this. The firmware of my phone is VRBMF1 and I do have a "d2vzw_VRBMF1_firmware.zip". I would deeply appreciate tips on how to use Odin to undo the changes made to my phone and restore it back to where it was before I tried this.
Thank you for your reply.

boldred said:
Thank you for your reply.
Yes, I did have the SuperSU zip on the sdcard in the phone but I got the error message and continue to do so even after formatting two different sdcards, using the CWM that was installed. The sdcards won't mount in the phone. I can still use the phone (it's one week-old now) but the "custom" screen now appears when turning it on. I'd just like to get the stuff off of the phone that I put on there during this botched process. Apparently, after reading about this situation, this problem appears to be that the CWM corrupts itself and has to be uninstalled, re-installed, uninstalled and etc. until it finally correctly does it what it was supposed to do. This seems too risky now. This is an expensive phone and I thought that I had selected the best option for rooting, unlocking the bootloader and installing a ROM after searching for a week, so I was prepared for problems. I've rooted/unrooted devices before. But I wasn't prepared for this kind of error at this level. I still may try it using TWRP Recovery 2.4.3.0 rather than the ClockworkMod Touch Recovery 6.0.2.3. But, first, I need to know how to get back "to stock" -- the way it was before I tried this. The firmware of my phone is VRBMF1 and I do have a "d2vzw_VRBMF1_firmware.zip". I would deeply appreciate tips on how to use Odin to undo the changes made to my phone and restore it back to where it was before I tried this.
Thank you for your reply.
Click to expand...
Click to collapse
To use Odin I would first download the latest version of Odin from here. Then I would extract the contents of the .zip file that contains Odin to a folder on your computer. Also I would recommend downloading the I535VRBMF1 firmware from here. Once you have done this click on the Odin .exe file. Now that you have launched Odin I would recommend taking a look at this guide on how to flash the firmware. After you have flashed the firmware to your device and have a clean slate then I would go ahead and use the 1-click by beanstown106 to root, unlock bootloader, and install custom recovery. Feel free to keep asking questions if you need as I'll be happy to answer them.