[RECOVERY] CWM Recovery for Galaxy Light T-399

Search This thread

smartguy044

Inactive Recognized Developer
Mar 3, 2012
2,605
3,952
North Carolina
DISCLAIMER: I take no responsibility for any bricks or other damages that may happen to your phone. You flash this knowing all the risk.





CWM Recovery for Galaxy Light


Installation:
1) Download the CWM file from here
2) Put phone in Download mode. Power off phone. Hold down 'Volume Down' button and 'Power Button'. When the warning screen comes up press 'Volume Up' button.
3) Open Odin and put cwm file in pda and flash
4) Success. Reboot and enjoy custome recovery



Bugs:
-The only weird thing I know is going on is that in order to go to internal sd card is you have to go to sdcard/0 directory




If you like my work just hit the Thanks button




Thanks to:
tazmaniondvl for doing all the testing for me
shabbypenguin for providing me with the stock recovery.img







 
Last edited:

aureljared

Senior Member
May 2, 2013
970
671
dantis.me
Redmi Note 11
DISCLAIMER: I take no responsibility for any bricks or other damages that may happen to your phone. You flash this knowing all the risk.





CWM Recovery for Galaxy Light


Installation:
1) Download the CWM file from here
2) Open Odin and put cwm file in pda and flash
3) Success. Reboot and enjoy custome recovery


Bugs:
-The only weird thing I know is going on is that in order to go to internal sd card is you have to go to sdcard/0 directory


If you like my work just hit the Thanks button

Thanks to:
tazmaniondvl for doing all the testing for me
shabbypenguin for providing me with the stock recovery.img


I own a Galaxy Express, but I just want to say that the sdcard/0 issue also occurs on mine. I think it's a kernel issue (decision?) to use mainly 0 instead of legacy when writing data to the internal sdcard.
 
  • Like
Reactions: GalaxySmokes

smartguy044

Inactive Recognized Developer
Mar 3, 2012
2,605
3,952
North Carolina
Ok I think Arco does the stuff for that phone. I will see if he has any opinions about it. The good thing is it works like it's supposed to, it's just a little hassle for users to make that extra step to get to what they want.

Sent from my HTC6500LVW using XDA Premium 4 mobile app
 
  • Like
Reactions: aureljared

mn1968

Senior Member
Nov 7, 2011
596
161
I just want to confirm that this cwm will allow me to perform nandroid backups.

Thanks
 

tazmaniondvl

Senior Member
Sep 11, 2012
1,700
565
Phoenix
Yes, I tested multiple times after flashing, even tried after flashing via cwm and odin

Sent from my SGH-T399 using XDA Premium 4 mobile app

---------- Post added at 05:20 PM ---------- Previous post was at 05:19 PM ----------

I just want to confirm that this cwm will allow me to perform nandroid backups.

Thanks

.

Sent from my SGH-T399 using XDA Premium 4 mobile app
 
  • Like
Reactions: GalaxySmokes

smartguy044

Inactive Recognized Developer
Mar 3, 2012
2,605
3,952
North Carolina
Added step to tell how to get to download mode to OP thanks for the suggestion

Sent from my HTC6500LVW using XDA Premium 4 mobile app
 

GJSmith3rd

Senior Member
May 6, 2008
429
54
Chicago
OnePlus 8
Soft Brick

Ok, today I felt brave and enthusiastic and ultimately soft bricked my SGH-T399. I can boot into CWM but my MD5 failed. Factory reset no go. I can boot into download mode. Normal boot just sits at the 4G LTE. I can connect with ODIN. Any suggestions. :confused:
 

smartguy044

Inactive Recognized Developer
Mar 3, 2012
2,605
3,952
North Carolina
What steps did you take to do whatever you did to bootloop your phone

Sent from my HTC6500LVW using XDA Premium 4 mobile app
 

GJSmith3rd

Senior Member
May 6, 2008
429
54
Chicago
OnePlus 8
What steps did you take to do whatever you did to bootloop your phone

Sent from my HTC6500LVW using XDA Premium 4 mobile app

I think I ran into the Samsung internal SD problems I've been seeing so much in the forums. I reformatted my Ext SD to include a SWAP partition. I didn't really know if the kernel would support it but I thought I'd give it a quick try. I installed Swapper 2 from the Play Store set it for SWAP partition instead of SWAP file and set it to format the SWAP. It asked what mount to format and I thought it would auto detect so I kept the prefilled mount, EFS -> /dev/block/mmcblk0p3 i think, doh! After that when I rebooted I just had 4glte screen...:confused:

EDIT:

03-09 00:03:45.185: E/android.os.Debug(3769): !@Dumpstate > dumpstate -k -t -z -d -o /data/log/dumpstate_sys_error
03-09 00:03:45.195: E/dumpstate(3816): Cannot get free space size. So, skip dumpstate.
03-09 00:03:45.315: E/connfw(2784): connect error:2
03-09 00:03:45.365: E/DTT(2783): connect error:2
03-09 00:03:45.400: E/AndroidRuntime(3769): Error reporting crash
03-09 00:03:45.400: E/AndroidRuntime(3769): java.lang.NullPointerException
03-09 00:03:45.400: E/AndroidRuntime(3769): at com.android.internal.os.RuntimeInit$UncaughtHandler.uncaughtException(RuntimeInit.java:138)
03-09 00:03:45.400: E/AndroidRuntime(3769): at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:693)
03-09 00:03:45.400: E/AndroidRuntime(3769): at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:690)
03-09 00:03:45.400: E/AndroidRuntime(3769): at dalvik.system.NativeStart.main(Native Method)
03-09 00:03:45.440: E/SMD(2781): connect error:2
03-09 00:03:45.750: E/TinyUCM(3817): 23.26: This output device support only one mic
03-09 00:03:45.750: E/TinyUCM(3817): 24.32: This output device support only one mic
03-09 00:03:45.750: E/TinyUCM(3817): 25.31: This output device support only one mic
03-09 00:03:45.750: E/TinyUCM(3817): 26.40: This output device support only one mic
03-09 00:03:45.750: E/TinyUCM(3817): 27.28: This output device support only one mic
03-09 00:03:45.750: E/TinyUCM(3817): 28.35: This output device support only one mic
03-09 00:03:45.815: E/tms_audio_hw/AudioTmsIpc(3817): AudioTmsServerListen bind error -1 Read-only file system
03-09 00:03:45.815: E/tms_audio_hw/AudioTmsIpc(3817): AudioTmsClientListen::bind error -1
03-09 00:03:46.185: E/SMD(2781): InvokeOemRequestHookRaw usbstatus true is failure 1
03-09 00:03:46.315: E/connfw(2784): connect error:2
03-09 00:03:46.365: E/DTT(2783): connect error:2
03-09 00:03:46.440: E/SMD(2781): connect error:2
03-09 00:03:46.650: E/SecBandwidthController(3818): SecBandwidthController::enableBandwidthControl
03-09 00:03:46.650: E/SecBandwidthController(3818): information file open failed (No such file or directory)
03-09 00:03:46.650: E/SecBandwidthController(3818): backup file open failed (No such file or directory)
03-09 00:03:47.315: E/connfw(2784): connect error:2
03-09 00:03:47.370: E/DTT(2783): connect error:2
03-09 00:03:47.440: E/SMD(2781): connect error:2
03-09 00:03:47.825: E/cutils(4086): Failed to read /data/.layout_version: No such file or directory
03-09 00:03:47.825: E/installd(4086): Could not create directories; exiting.
03-09 00:03:47.830: E/keystore(4087): chdir: /data/misc/keystore: No such file or directory
03-09 00:03:47.830: E/DataRouter(4088): bind error:30
03-09 00:03:47.835: E/Kies(4089): bind error
03-09 00:03:47.880: E/gpsd(4090): Process is already running, the second instance will not be started!
03-09 00:03:48.185: E/SMD(2781): InvokeOemRequestHookRaw usbstatus true is failure 1
03-09 00:03:48.315: E/connfw(2784): connect error:2
03-09 00:03:48.370: E/DTT(2783): connect error:2
03-09 00:03:48.445: E/SMD(2781): connect error:2
03-09 00:03:49.315: E/connfw(2784): connect error:2
03-09 00:03:49.370: E/DTT(2783): connect error:2
03-09 00:03:49.445: E/SMD(2781): connect error:2
03-09 00:03:49.820: E/AndroidRuntime(4098): !@*** FATAL EXCEPTION IN SYSTEM PROCESS: main
03-09 00:03:49.820: E/AndroidRuntime(4098): java.lang.NullPointerException
03-09 00:03:49.820: E/AndroidRuntime(4098): at com.android.server.pm.PackagePrefetcher.prefetchInner(PackagePrefetcher.java:166)
03-09 00:03:49.820: E/AndroidRuntime(4098): at com.android.server.pm.PackagePrefetcher.prefetchPackages(PackagePrefetcher.java:160)
03-09 00:03:49.820: E/AndroidRuntime(4098): at com.android.server.SystemServer.main(SystemServer.java:1908)
03-09 00:03:49.820: E/AndroidRuntime(4098): at java.lang.reflect.Method.invokeNative(Native Method)
03-09 00:03:49.820: E/AndroidRuntime(4098): at java.lang.reflect.Method.invoke(Method.java:511)
03-09 00:03:49.820: E/AndroidRuntime(4098): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1102)
03-09 00:03:49.820: E/AndroidRuntime(4098): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:869)
03-09 00:03:49.820: E/AndroidRuntime(4098): at dalvik.system.NativeStart.main(Native Method)
03-09 00:03:49.825: E/dumpstate(4142): Cannot get free space size. So, skip dumpstate.
03-09 00:03:50.125: E/android.os.Debug(4098): !@Dumpstate > dumpstate -k -t -z -d -o /data/log/dumpstate_sys_error

Yep, boot loop...
http://code.stypi.com/gjsmith3rd/sgh-t399_bootloop.txt
 
Last edited:

GJSmith3rd

Senior Member
May 6, 2008
429
54
Chicago
OnePlus 8
CWM Restored Boot and System

Ok, I was able to restore both Boot and System nandroid by manipulating MD5

rm nandroid.md5
md5sum *img>nandroid.md5

Then using CWM advanced restore from extsd but still no luck. I still think it's my EFS partition.

Here are some efs theads maybe someone can use to help out.

[APP][4.0+][ROOT] SA Manager (EFS, MODE, MODEMST, TA backup & restore)

[EFS][APP][15/01/14] Samsung Tool 2.0 [BACKUP/RESTORE ON DEVICE]

[IMEI][efs] SAMSUNG NOTE 3 EFS BACKUP/RESTORE

---------- Post added at 09:02 PM ---------- Previous post was at 08:45 PM ----------

Ok, here's an interesting thread about restoring EFS partition by modifing EFS backup and making a CWM zip. I think this will if someone will help by backing up EFS.img and making it available for me to download. Then I can include it in the EFS-cwm-flasher.zip and restore with CWM.

[EFS-cwm-Restore] Restore zip for your EFS
 

smartguy044

Inactive Recognized Developer
Mar 3, 2012
2,605
3,952
North Carolina
Ok glad you got it fixed. Guess someone needs to set y'all up with stock Rom zip or Odin flashable incase something like this happens again.

Sent from my HTC6500LVW using XDA Premium 4 mobile app
 

Top Liked Posts

  • There are no posts matching your filters.
  • 14
    DISCLAIMER: I take no responsibility for any bricks or other damages that may happen to your phone. You flash this knowing all the risk.





    CWM Recovery for Galaxy Light


    Installation:
    1) Download the CWM file from here
    2) Put phone in Download mode. Power off phone. Hold down 'Volume Down' button and 'Power Button'. When the warning screen comes up press 'Volume Up' button.
    3) Open Odin and put cwm file in pda and flash
    4) Success. Reboot and enjoy custome recovery



    Bugs:
    -The only weird thing I know is going on is that in order to go to internal sd card is you have to go to sdcard/0 directory




    If you like my work just hit the Thanks button




    Thanks to:
    tazmaniondvl for doing all the testing for me
    shabbypenguin for providing me with the stock recovery.img







    3
    I'll just go ahead and say this here, i hope no one sends this file on any phone at any time. nothing personal by any means, but your efs partition contains your devices IMEI. early on in android devices people would get ahold of someone elses efs partition and it would mess up both devices, nowadays on devices like the s4 it actually just corrupts the image when it reads the hardware values and compares to the image. but still having the image given freely is a fairly large security risk (with someones IMEI you can clone their device and report it lost/stolen blacklisting the device for the true owner and much more.)

    if it truly is your efs partition there have been several tools which claim they can repair it, this is my second GSM device and ive made sure to backup EFS on both as soon as i got root so ive no idea if they work or not. seems kind of odd though that EFS would prevent you from booting, in all other cases i know about it just blanks out your cell signal stuff.

    Just so they know you dont need someone elses efs file.. You can restore it from the nvdata and the nvdata backup.. you could completly wipe the efs folder it will remake it on boot and restore it from any backup of nvdata you had... Why people still ask for someone elses efs folder escapes me thanks for putting the warning out there.

    also helpfull if theres a stock odin... Humm going to have to check my source on getting the stock odin image.. You can completly hose it 9 times out of 10 if u can get to a stock recovery from factory it will re provision your first boot might be 00000s but it will correct..


    NEVER EVER EVER GIVE YOUR EFS OR NVDATA FILES TO ANYONE ASKING TO RECOVER THERE DEVICE... EVER.


    Off chance that a developer asks for it make sure you know what your getting into.. Sometimes we do use them for hex editing unlockers. But we will a ask for your permission first second Tell you what were doing with it and thirdly. Give you the unlock code if successful. Thats only if we wanna test it on a device we dont own and or we already unlocked our device and want to say make sure it unlocks on someone elses.
    Most the time we wont ask for it...
    2
    Ok somehow I missed important comments from smartguy and shabbypenguin but I understand now. Since using someone elses efs could cause problems and not having efs backup looks like I'm toast. The efs partition won't even mount so its worse than corrupt or incorrect. This is my first brick. I wish I could recreate own efs from data on the box or something.

    Sent from my U8150 using Tapatalk 2

    efs wont mount on anyone's device, its not a file system. just one giant file. as i mentioned i dont think you overwrote your efs though, perhaps something more useless like param or hidden and its causing the bootloop. we know its not the bootloaders and we know its not system/data/boot/recovery/cache.
    2
    CWM installed just fine. Some may need to know that you need to put the phone into download mode before trying to install CWM . I just use ADB command "adb reboot download" while the phone is connected to computer.
    1
    DISCLAIMER: I take no responsibility for any bricks or other damages that may happen to your phone. You flash this knowing all the risk.





    CWM Recovery for Galaxy Light


    Installation:
    1) Download the CWM file from here
    2) Open Odin and put cwm file in pda and flash
    3) Success. Reboot and enjoy custome recovery


    Bugs:
    -The only weird thing I know is going on is that in order to go to internal sd card is you have to go to sdcard/0 directory


    If you like my work just hit the Thanks button

    Thanks to:
    tazmaniondvl for doing all the testing for me
    shabbypenguin for providing me with the stock recovery.img


    I own a Galaxy Express, but I just want to say that the sdcard/0 issue also occurs on mine. I think it's a kernel issue (decision?) to use mainly 0 instead of legacy when writing data to the internal sdcard.