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.

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.

[Q] Error Wifi,. after Kernel failure

hi guys
ok, so I have a Sensation XE. I had the stock ROM, then added Fast Boot.
I wanted USB OTG support, so tried to [KERNEL] Overclocked kernel v1.5.2, not sure why, but it failed.
after that my phone was buggy. slow and the Wifi unhappy.
I thought ill just put a new kernel in, I ran [Aroma] Sultan kernel [r21 3/2/2013]
a bit better but not great.
I figured Ill start from scratch then:
So I flashed Darkforest Sensation XE 7.3.0 with Kernal:XxXPachaXxX_Custom_Kernel_stable3.1. this includes a COMPLETE wipe of the system using Aroma.
I thought this would fix the issue...
it didn't... the ROM is nice n slick, but Wifi - Error on the quick setting screen. cant be turned on.
whats gone wrong, and can I fix it?
I've tried http://forum.xda-developers.com/showthread.php?t=1456700 delete the "wifi_supplicant.conf" file.
Wold flashing a different Kernel fix this like http://forum.xda-developers.com/showthread.php?t=1230687 did.
if so, which Kernel, as with my noobness I'm not sure which ones would work or are fully compatible
Cheers for your help

Try ARHD. Then flash Sultan's r15. If problem still persists, use R15 with the BCMXXXXX thingy. It worked for me.

KiD3991 said:
Try ARHD. Then flash Sultan's r15. If problem still persists, use R15 with the BCMXXXXX thingy. It worked for me.
Click to expand...
Click to collapse
I've just tried the Sultan-kernel-r14-Aroma-BCM4329.zip, still the same wifi error.
I've also noticed that in Advanced Wifi, MAC Address: unavailable, IP Address: Unavailable

i was going through my boot loader. and when it checks itself it has image errors
see image
{
"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"
}
https://www.dropbox.com/s/vkhw9s0qamionws/BootImageIssues.jpg

grymcent said:
i was going through my boot loader. and when it checks itself it has image errors
see image
https://www.dropbox.com/s/vkhw9s0qamionws/BootImageIssues.jpg
Click to expand...
Click to collapse
don't care about that.it is nothing
when you boot into bootloader it reads every time the sdcard and searching for pg58img.zip or pg58diag.zip
ignore it
now about your wifi issue
i saw that you are S-ON
i suggest to have 4ext recovery for flashing kernels and roms
and before flashing any rom or kernel enable smartflash from recovery
now try this way
flash the boot.img of the rom manually.if don't know how see here
http://forum.xda-developers.com/showthread.php?t=1631861 (only extra 1 step)
then check your wifi
also can you tell me what error did you have with overclocked kernel 1.5.2?

rzr86 said:
don't care about that.it is nothing
when you boot into bootloader it reads every time the sdcard and searching for pg58img.zip or pg58diag.zip
ignore it
now about your wifi issue
i saw that you are S-ON
i suggest to have 4ext recovery for flashing kernels and roms
and before flashing any rom or kernel enable smartflash from recovery
now try this way
flash the boot.img of the rom manually.if don't know how see here
http://forum.xda-developers.com/showthread.php?t=1631861 (only extra 1 step)
then check your wifi
also can you tell me what error did you have with overclocked kernel 1.5.2?
Click to expand...
Click to collapse
Sorry, I cant recall the error from flashing the Kernel.
I have tried to flash Recover.img and add 4Ext, however it seems I have TWRP 2.3.x
i did also flash the Boot.img for the DarkForest ROM to see if that made a difference..
nope nothing
also was directed to the PG58IMG.zip to fix firmware, but that didnt seem work according to their instructions either.

grymcent said:
Sorry, I cant recall the error from flashing the Kernel.
I have tried to flash Recover.img and add 4Ext, however it seems I have TWRP 2.3.x
i did also flash the Boot.img for the DarkForest ROM to see if that made a difference..
nope nothing
also was directed to the PG58IMG.zip to fix firmware, but that didnt seem work according to their instructions either.
Click to expand...
Click to collapse
after much searching and trying a few other ROM, I found a comment about other ppl having issues with ROM. but fine with the Stock ROM.
I have just put the Stock rROM on, its connected to wifi straight away.
hope it lasts!

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.

Cannot flash system with odin after twrp Galaxy Note 9

Hi
I install twrp on my note 9 exynos. Then flashed no-verity-opt-encrypt-6.1.zip onto it. Phone will not flash stock firmware now with odin. I managed to remove twrp but when I flash stock firmware with odin everything flashes but the system part,it just hangs there doing nothing. It wont boot into stock recovery, I jst get the samsung screen. It will boot into download mode. Any suggestions please or have i got an expensive paper weight.
Thanks

manimaluk said:
Hi
I install twrp on my note 9 exynos. Then flashed no-verity-opt-encrypt-6.1.zip onto it. Phone will not flash stock firmware now with odin. I managed to remove twrp but when I flash stock firmware with odin everything flashes but the system part,it just hangs there doing nothing. It wont boot into stock recovery, I jst get the samsung screen. It will boot into download mode. Any suggestions please or have i got an expensive paper weight.
Thanks
Click to expand...
Click to collapse
If there is a multiple file stock ROM existing for it, did you try that?

bmwdroid said:
If there is a multiple file stock ROM existing for it, did you try that?
Click to expand...
Click to collapse
I'll have a look. thanks

I have managed to bring my phone back to life with a stock based rom (Thank God).
I cannot flash stock rom with odin though after twrp. It just hangs.
Can anyone tell me how to get odin to flash genuine firmware after twrp please.
How do I remove twrp & get stock recovery back ?
Thanks in advance.

manimaluk said:
I have managed to bring my phone back to life with a stock based rom (Thank God).
I cannot flash stock rom with odin though after twrp. It just hangs.
Can anyone tell me how to get odin to flash genuine firmware after twrp please.
How do I remove twrp & get stock recovery back ?
Thanks in advance.
Click to expand...
Click to collapse
So with which stock is it working right now?
Was it the multiple one?
and:
Why do you want to flash stock (if it's working already as you quoted) after TWRP as this should restore the stock recovery?
I don't really get what you're intending to do as what you wrote in the 1. sentence doesn't make sense with what you wrote afterwards.

bmwdroid said:
So with which stock is it working right now?
Was it the multiple one?
and:
Why do you want to flash stock (if it's working already as you quoted) after TWRP as this should restore the stock recovery?
I don't really get what you're intending to do as what you wrote in the 1. sentence doesn't make sense with what you wrote afterwards.
Click to expand...
Click to collapse
Thanks for your reply, I managed to flash N960X Superstable V14 rom & it is working fine. I just needed to know how to get back to stock if i wanted to sell it. I thought twrp restored the stock recovery but when i reboot it just hangs on the first samsung logo screen. Could it be a kernel problem. ?

I did flash no-verity-opt-encrypt-6.1.zip. Would this stop odin from flashing. If so, is there a way to reverse it with a stock boot file or something ?

manimaluk said:
I did flash no-verity-opt-encrypt-6.1.zip. Would this stop odin from flashing. If so, is there a way to reverse it with a stock boot file or something ?
Click to expand...
Click to collapse
TWRP is in no way able to let you return to stock.
Only Odin (or Heimdall) or fastboot can do that.
Don't understand how you've flashed stock recovery with TWRP.
Never used this file so can't tell.
Which Odin version?
Didn't answer question about multiple part stock ROM.

[ROM] [10] [RC] [SecureFolder]Galaxy Note9 [N960F/DS/N] SUPERSTABLE ROM UI2.5 V15 (02/04/2021) is the rom I used.​It works fine just google pay & samsung pay doesn't work which I expected anyway.
I didn't flash stock with twrp. I tried to flash with odin 3..14.1. But it just hangs on the recovery part. Won't complete.

Didn't answer question about multiple part stock ROM.

how do i find out if it is a multiple part stock rom

{
"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"
}
View attachment 5292385
The second shot is in the image folder.

These are not a stock ROM files.
They either has one AP.....tar.md5
or consists of four to five files (AP, BL, Home-CSC, CSC, CP).tar.md5.
Idk if all Samsung stock ROMs can have multiple parts but all of mine do but I gotta admit they are much older than yours.
These files are imo the safest way to return to stock as single file stock ROMs didn't work always.

bmwdroid said:
These are not a stock ROM files.
They either has one AP.....tar.md5
or consists of four to five files (AP, BL, Home-CSC, CSC, CP).tar.md5.
Idk if all Samsung stock ROMs can have multiple parts but all of mine do but I gotta admit they are much older than yours.
These files are imo the safest way to return to stock as single file stock ROMs didn't work always.
Click to expand...
Click to collapse
yes i have the same files for my phone downloaded from sammobile but odin won't flash them. I seemed to have lost my recovery partition i think. When i press the 3 buttons to boot into recovery it just stays on the samsung boot screen. If i install twrp it will boot into that ok. It goes into download mode ok. Never had this problem with my previous samsungs in the past. Wish i hadn't bothered now. :-(

Sorted it ! I deleted my google account, did a wipe with twrp then installed the latest firmware with Odin3_v3.14.4. Back on stock for now. Thanks for your interest.