samsung replenish emergency!!

[jesuspantaleon1993]

ok so i accidently downloaded a rooted app nd well its called "galaxy s tweakers"
i tried to change the battery icon..but that didnt worked obviously
so now it can start but it stay on the samsung logo that glows before the lock screen
but it stays there and vibrates only..

any help!!
please i need to fix this phone because this phone is goin to be my gps navigation for out of state wednesday...so any one help me.
and does this phone have a doctor ?
like webos doctors..??

 

[firehak]

Take a look at the LeafRom thread here: http://forums.androidcentral.com/samsung-replenish/99919-acs-rom-leaf-rom-0-2-a.html

Turn your phone off, and then power it on holding the "u" key. You'll see the recovery menu from here. Download LeafRom 0.2 and run the script following the simple directions shown to you before it runs. If all goes well, you will be running again. If it fails, grab the 0.1 version instead. I had the same problem for different reasons. (I love to tinker, what can I say?). LeafRom is a "glorified stock" with a few improvements such as speeding up media scanner, faster gps location, extended battery life, etc. Custom roms void carrier warranties, but we have tricks to fake stock if you need to return your phone. Shabbypenguin is still working on a way to return to stock.

If you want a custom battery icon, take a look at the UOT theme kitchen. You can mod your theme to show a custom battery icon and then send it over. If you need further help, I'll be happy to help, or you can post in the LeafRom thread.

 

[anon(335536)]

Can you connect to the phone via ADB? Did you have usb debug enabled prior to getting to this point? Is your phone rooted?

 

[anon(335536)]

Take a look at the LeafRom thread here: http://forums.androidcentral.com/samsung-replenish/99919-acs-rom-leaf-rom-0-2-a.html

Turn your phone off, and then power it on holding the "u" key. You'll see the recovery menu from here. Download LeafRom 0.2 and run the script following the simple directions shown to you before it runs. If all goes well, you will be running again. If it fails, grab the 0.1 version instead. I had the same problem for different reasons. (I love to tinker, what can I say?). LeafRom is a "glorified stock" with a few improvements such as speeding up media scanner, faster gps location, extended battery life, etc. Custom roms void carrier warranties, but we have tricks to fake stock if you need to return your phone. Shabbypenguin is still working on a way to return to stock.

My thoughts exactly, except if he can not connect via ADB, then he may be dead it the water...

 

[firehak]

My thoughts exactly, except if he can not connect via ADB, then he may be dead it the water...

He/She's not stuck. Recovery has adb connectivity. I screwed up making my custom "flasher" and ended up here as well. I recovered from a "brick" with 0.1 right before 0.2 was released, but 0.2 has a reboot command before anything starts. If he can't modify the script, 0.1 will be a good place to start and then upgrade to 0.2.

 

[jesuspantaleon1993]

ima try firehak's idea ..i can get to the recovery mode by th u button so maybe theres luck

 

[firehak]

Best of luck. If neither solution works, there is an odin release coming out for us sometime soon. It may not meet your deadline, but you could then flash new ROM that way and recover your phone.

 

[jesuspantaleon1993]

Best of luck. If neither solution works, there is an odin release coming out for us sometime soon. It may not meet your deadline, but you could then flash new ROM that way and recover your phone.

yeah i hope so..if not my sister is goin to be so mad..she owns the account.
and well i hope it does cause im to use this phone for navigation ...if not then im dead..

 

[firehak]

I'm pretty confident that at least 0.1 will work for you as it did for me. If there adb.exe is able to see your phone when plugged into usb while the recovery menu is open, you're in luck. If you want to check before you start, you can open cmd.exe and switch to the directory that you extracted LeafRom to and then try typing "adb.exe devices" If your phone shows up, you're good to go.

 

[jesuspantaleon1993]

I'm pretty confident that at least 0.1 will work for you as it did for me. If there adb.exe is able to see your phone when plugged into usb while the recovery menu is open, you're in luck. If you want to check before you start, you can open cmd.exe and switch to the directory that you extracted LeafRom to and then try typing "adb.exe devices" If your phone shows up, you're good to go.

i cant do it..its not workin..
what to do
what to do?

 

[firehak]

What did you try, and what steps did you take? I'll explain everything as detailed as I can.

 

[jesuspantaleon1993]

i ntook out the battery nd reinserted
then i pressed u nd started the menu for recovery..it had a android icon
then ran leaf rom 0.2
didnt work it said device not found
so then i tried version 0.1'
still doesnt work either..say do a factory reset nd also said device not found..
i cant since the replenish cant get out of the boot loop on the glowing samsung logo

 

[firehak]

Try this. In your Windows start menu, search for "cmd.exe" and type "cd path\to\LeafRom\"

Then type "adb.exe kill-server" "adb.exe start-server" and "adb.exe devices"
What do you see? I'll attach a sample screenshot. Please ignore everything above the white line. It's just my attempts for the custom boot screen. I ran the command twice to show no device, and a second time for it finding my Replenish. Which do you see?

 

[jesuspantaleon1993]

Try this. In your Windows start menu, search for "cmd.exe" and type "cd path\to\LeafRom\"

Then type "adb.exe kill-server" "adb.exe start-server" and "adb.exe devices"
What do you see? I'll attach a sample screenshot. Please ignore everything above the white line. It's just my attempts for the custom boot screen. I ran the command twice to show no device, and a second time for it finding my Replenish. Which do you see?

still nothin on cd path
it says the system cannot find the path specified

 

[firehak]

See how my command prompt says "C:\Users\FirehaK\Documents\LeafRom 0.2>"? You type "cd " and the full path to where you extracted LeafRom. I'm guessing this is why you get your error? I'm sorry if I'm wrong about it, but I can't think of another reason you would get that. If command prompt isn't inside the LeafRom directory where all the files are, it won't see adb.exe.

Open up notepad and save it as "help.bat." Save this where you extracted the rom and run it. It will save you from typing stuff out. When saving it, change file type from text files to all files so Windows doesn't save it as help.bat.txt. Here is what the file should look like:

adb.exe kill-server
adb.exe start-server
adb.exe devices
adb.exe kill-server
pause​

 

[anon(335536)]

I'm still thinking that if usb debug is not enabled then leaf rom can not be installed. Did adb devices work?

 

[firehak]

That's why I'm trying to get this to work before we go out of the way and just frustrate hithereawesomeness. Debugging was enabled before I bricked. I also had drivers installed. I don't have the link to the driver anymore though if he/she hasn't installed them for debugging to work in the first place.

 

[jesuspantaleon1993]

That's why I'm trying to get this to work before we go out of the way and just frustrate hithereawesomeness. Debugging was enabled before I bricked. I also had drivers installed. I don't have the link to the driver anymore though if he/she hasn't installed them for debugging to work in the first place.

so firehak i have a question
to run cd path do u have to have the android sdk?

 

[firehak]

No. The files needed from the SDK are inluded when you download LeafRom (adb.exe and some dll's). When you run cd, you would type something like this, "cd C:\Users\FirehaK\Documents\LeafRom 0.2" That being the location of my directory for LeafRom. If you just place the .bat file I mentioned above in that directory, you won't have to do this. You'd simply double click it and wait for it to tell you.

 

[Shabbypenguin]

ok sorry i didnt spot this earlier.. if usb debugging is off then your going to get error device not found...

i have a possible solution for you.. you have a 50-50 shot right now (well actually tbh odds are a little bit better then that) of restoreing your phone or completly destroying it.. i was hoping to ask for someone.. but as your phone doesnt already boot would you be willing to test it out?

if it works then there is a way to recover back to stock (ew) and flash kernels