Database Develop

[Discontinued] [HOW TO] Root, Stock, ODIN For P3113UECLK7

This is nothing more than a pre-rooted completely stock image that you would flash in Odin.
It is based off of this stock image: P3113UECLK7_P3113XACCLK7_HOME.tar.md5
Simply adds the SuperSU apk v0.99 and su binary.
From there you can chose to install busybox, flash a non-stock recovery, etc.
It DOES NOT wipe any data. So if you are coming from a completely different rom base then you will want to boot to recovery and factory reset.
This is good for getting back to known good state after you may have flashed something and now have weird behavior going on. Also good if you want to run stock but just have root for a few apps like adaway or tibu.
Instructions:
Extract the root66_xxx_.tar.md5 from the .7z file you downloaded.
Use Odin, put device into download mode, connect to computer and open Odin.
once in odin click the PDA field and select the root66_xxx_.tar.md5 you downloaded.
Leave Auto Reboot and F. Reset Time checked.
click start and
when done let device reboot.
If you have issues flashing with Odin please ensure you are using the microusb cable that came with the device, users have had issues using other cables.
Choose One:
Download: root66_XAC_P3113UECLK7.7z - JellyBean 4.1.1
Download: root66_XAR_P3113UECLK7.7z - JellyBean 4.1.1

{
"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"
}
ty for this trying it out now
Update: installed via odin now its in recover loop. Just stuck with the lil android guy with his spinning cube in his chest. Progress bar at the bottom isn't moving at all.

F3AR420 said:
ty for this trying it out now
Update: installed via odin now its in recover loop. Just stuck with the lil android guy with his spinning cube in his chest. Progress bar at the bottom isn't moving at all.
Click to expand...
Click to collapse
Few questions....
I see in your signature you had AOKP. Did you flash this direct from AOKP? This doesn't wipe data and since it goes back to stock its still trying to use all your /data from aokp. You'd want to boot into recovery and do a factory reset coming from a different rom base than stock.
Also I use the Region XAC stock file. There is also an XAR. Does anyone know the difference? Samsung-updates seems to list XAC as N/A for region while XAR as Cellular South but I think I read the opposite from someone on the forum here.

Nah haven't updated my profile in a while. I had actually come from stock 4.0.4 i believe in my case atleast that my battery simply wasn't charged well enough.
Sent from my HTCEVODesign4G using Tapatalk 2

I would very politely like to point out that this has already been posted [13 Jan 2013] in this thread: http://forum.xda-developers.com/showthread.php?t=2098085 -- UECLK7

metalchef said:
I would very politely like to point out that this has already been posted [13 Jan 2013] in this thread: http://forum.xda-developers.com/showthread.php?t=2098085 -- UECLK7
Click to expand...
Click to collapse
Close. That thread shows you step by step how to do it yourself using mobile Odin lite using original official unmodified update files. This thread seems to give you one file to flash with Odin. Haven't tried this file yet...yet.

metalchef said:
I would very politely like to point out that this has already been posted [13 Jan 2013] in this thread: http://forum.xda-developers.com/showthread.php?t=2098085 -- UECLK7
Click to expand...
Click to collapse
There are a few differences. To use that thread your device has to be rooted. Here it does not.
In that thread you are using mobile odin to flash the stock file, then using recovery to flash root. Here root is pre-injected into the stock firmware. You can use mobile odin to flash this and be done. (unless you want a non-stock recovery etc).

LeftyGR said:
Close. That thread shows you step by step how to do it yourself using mobile Odin lite using original official unmodified update files. This thread seems to give you one file to flash with Odin. Haven't tried this file yet...yet.
Click to expand...
Click to collapse
Yes though you mention to use the XAR file and I've pre-injected the XAC. Outside of what you've said I can't find what region would be for what tablets. I'll post up the XAR as well and let the user pick.

XAR region uploaded..

mrRobinson said:
Few questions....
I see in your signature you had AOKP. Did you flash this direct from AOKP? This doesn't wipe data and since it goes back to stock its still trying to use all your /data from aokp. You'd want to boot into recovery and do a factory reset coming from a different rom base than stock.
Also I use the Region XAC stock file. There is also an XAR. Does anyone know the difference? Samsung-updates seems to list XAC as N/A for region while XAR as Cellular South but I think I read the opposite from someone on the forum here.
Click to expand...
Click to collapse
I found this suggestion to be quite helpful. I was coming from Tsunami and found if it would not boot to go back and factory reset. Thanks!
---------- Post added at 11:25 AM ---------- Previous post was at 11:21 AM ----------
Interestingly I am having a problem using TWRP to backup this ROM. TWRP FCs and the Tab reboots before any data is written to the SD card. It does create the named backup folder but dies early on in the backup process. Going to try CWM next but the backups created by CWM and TWRP are not compatible. TWRP has worked fine on all the other ROMs I tried. I need to perform more testing.

archcantor said:
I found this suggestion to be quite helpful. I was coming from Tsunami and found if it would not boot to go back and factory reset. Thanks!
---------- Post added at 11:25 AM ---------- Previous post was at 11:21 AM ----------
Interestingly I am having a problem using TWRP to backup this ROM. TWRP FCs and the Tab reboots before any data is written to the SD card. It does create the named backup folder but dies early on in the backup process. Going to try CWM next but the backups created by CWM and TWRP are not compatible. TWRP has worked fine on all the other ROMs I tried. I need to perform more testing.
Click to expand...
Click to collapse
yea try cwm. this is just stock maybe twrp is having some issue.

F3AR420 said:
ty for this trying it out now
Update: installed via odin now its in recover loop. Just stuck with the lil android guy with his spinning cube in his chest. Progress bar at the bottom isn't moving at all.
Click to expand...
Click to collapse
I have got exactly the same issue like this one when I was trying
root66_XAR_P3113UECLK7.7z - JellyBean 4.1.1
on my P3113. The tablet seems frozen at this stage and if I hold the power botton and let it reset, it will come back at the same screen with the progress bar unchanged.
My P3113 is with stock ICS ROM and rooted.
I cant do factory reset because when I trying to go to recovery mode, this screen shows up...

spunky2008 said:
I have got exactly the same issue like this one when I was trying
root66_XAR_P3113UECLK7.7z - JellyBean 4.1.1
on my P3113. The tablet seems frozen at this stage and if I hold the power botton and let it reset, it will come back at the same screen with the progress bar unchanged.
My P3113 is with stock ICS ROM and rooted.
I cant do factory reset because when I trying to go to recovery mode, this screen shows up...
Click to expand...
Click to collapse
I got the same result as well, eventhough Odin said pass. Funny thing is I put in download mode again and flash this official firmware from France. The Odin said failed, but after I reboot all good.

droidnext said:
I got the same result as well, eventhough Odin said pass. Funny thing is I put in download mode again and flash this official firmware from France. The Odin said failed, but after I reboot all good.
Click to expand...
Click to collapse
You must have lost the root by flashing the official stock rom, right?
I was thinking to flash the stock ICS rom for P3113 someone post on this board also but don't want to go through the hustles to root it again

spunky2008 said:
You must have lost the root by flashing the official stock rom, right?
I was thinking to flash the stock ICS rom for P3113 someone post on this board also but don't want to go through the hustles to root it again
Click to expand...
Click to collapse
Yes, I lost root. But I end up flash USA official firmware again and used this root method . It's very easy, took 15 sec. I came from CM10.1 nightly, but want to try official JB from Samsung. Actually, it's smooth and fast. Maybe I stick to it, I am tired of update everyday for CM10.1.

Removed post.

i tried this from a corrupted cm10.1 nighlty custom kernel which is stuck on the samsung galaxy tab 2 logo. odin was successful, i got pass the android screen shown in the previous post but now im stuck on the samsung logo with the blue orb. help

Re: [HOW TO] Root, Stock, ODIN For P3113UECLK7
jonahmt21 said:
i tried this from a corrupted cm10.1 nighlty custom kernel which is stuck on the samsung galaxy tab 2 logo. odin was successful, i got pass the android screen shown in the previous post but now im stuck on the samsung logo with the blue orb. help
Click to expand...
Click to collapse
Boot to recovery and factory wipe.

Removing the my external SD card did the trick for me.

Thanks cumanzor. One small comment like yours and it relieves a major headache for me, thanks again.

[Q] can't flash rom?

hi im trying to flash jelly bean but after flashing through cwm it just charges at the cyanogenmod logo endlessly

and now im just stuck, the backup says md5 mismatch?

ShadowsDie said:
and now im just stuck, the backup says md5 mismatch?
Click to expand...
Click to collapse
try flashing the ROM, twice
Check this out! You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, click on their Thanks button
{
"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"
}
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.​

xsenman said:
try flashing the ROM, twice
Check this out! You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, click on their Thanks button
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.​
Click to expand...
Click to collapse
ok, i made a big mistake now... plz help me now i really need your help.
because of the backup didn't work i tried flashing stock but odin stucks at adsp.mbn (right after step 1/7)
NOW I CANT ACCES RECOVERY, JUST DOWNLOAD MODE...
PLZ HELP.. idk i managed to solve another problem with amss.mbn where it got stuck but i tried different rom and this one stucks here
plz... the phone is not mine.... i dont want to go to a service to repair it and im pretty sure i can do it from my pc but idk what to do now

ShadowsDie said:
ok, i made a big mistake now... plz help me now i really need your help.
because of the backup didn't work i tried flashing stock but odin stucks at adsp.mbn (right after step 1/7)
NOW I CANT ACCES RECOVERY, JUST DOWNLOAD MODE...
PLZ HELP.. idk i managed to solve another problem with amss.mbn where it got stuck but i tried different rom and this one stucks here
plz... the phone is not mine.... i dont want to go to a service to repair it and im pretty sure i can do it from my pc but idk what to do now
Click to expand...
Click to collapse
It looks like you are talking about i9001 or is it i9000?, so if you do not indicate what model you have from the beginning, you will get wrong directions
Check this out! You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, click on their Thanks button
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.​

Reflash
1. You have to Install back the cwm by odin. Go to i9000 forum if your phone is i9000. If your phone is i9001 then go to i9001 android development.
2. Then search the ROM that you want (the best is cyanogenmod). Then im pretty sure the cyanogenmod from the development team got state the type of CWM use to flash the ROM.
Example, for this ROM: http://forum.xda-developers.com/showthread.php?t=2436670
The CWM used is v6.0.2.8
3. Download the CWM and ROM
4. Follow the instruction on how to install the CWM through odin step by step (must be patient)
5. Then follow the instruction on how to install the ROM (step by step)
6. You should be able to enjoy your phone like a new one.
:good:

Aylwinchai said:
1. You have to Install back the cwm by odin. Go to i9000 forum if your phone is i9000. If your phone is i9001 then go to i9001 android development.
2. Then search the ROM that you want (the best is cyanogenmod). Then im pretty sure the cyanogenmod from the development team got state the type of CWM use to flash the ROM.
Example, for this ROM: http://forum.xda-developers.com/showthread.php?t=2436670
The CWM used is v6.0.2.8
3. Download the CWM and ROM
4. Follow the instruction on how to install the CWM through odin step by step (must be patient)
5. Then follow the instruction on how to install the ROM (step by step)
6. You should be able to enjoy your phone like a new one.
:good:
Click to expand...
Click to collapse
ok let me tell you from the start, YES my phone is i9001 because i put the cwm for it and it worked (yes, 6.0.2.x , i dont remember that x but i know its name was patched or something like that)
so, i had cwm, root, and flashed a cyanogen mod 10.2 (alpha 2 i think) but i because i used a broken cable, i think the rom got corrupted
so i made a backup, wipe data/cache ,and i couldn't wipe dalvik i dont remember why.
so i flashed the rom and spent like 20 min on the cyanogenmod charging screen and i took the battery.
i tried liek 4-5 times and no change
so i tried to restore but i had the md5 error, because i dont have the adb thing to repair it i tried to flash stock.
so flashing it got stuck at amss.mbn (downloading)
so i tried changing the stock rom and now it got stuck at adsp.mbn (WHY?)
but now i have better news, i flashed a cwm recovery and it enters, but the same problem, when i flash cyanogenmod it charges endlessly and i dont want to flash stock firmware again... so?
INCREDIBLE EDIT: when i was writing it was just charging at the logo, NOW IT WORKS!!!!!!!!!!, i think it was a CWM problem? because i flashed through odin a different version (6.0.x)
anyway thanks guys

Aylwinchai said:
1. You have to Install back the cwm by odin. Go to i9000 forum if your phone is i9000. If your phone is i9001 then go to i9001 android development.
2. Then search the ROM that you want (the best is cyanogenmod). Then im pretty sure the cyanogenmod from the development team got state the type of CWM use to flash the ROM.
Example, for this ROM: http://forum.xda-developers.com/showthread.php?t=2436670
The CWM used is v6.0.2.8
3. Download the CWM and ROM
4. Follow the instruction on how to install the CWM through odin step by step (must be patient)
5. Then follow the instruction on how to install the ROM (step by step)
6. You should be able to enjoy your phone like a new one.
:good:
Click to expand...
Click to collapse
yea.. as i said before now it works but i had another recovery , (newer and with the patch thing)

SO now everything okay? Good for you.. as i said, you have to follow the instruction very carefully. It includes all the version that they state. Matching the version of the software before start or else everything will become a mess. I experience that before.
:thumbup:
Sent from my GT-I9001 using xda app-developers app

Aylwinchai said:
SO now everything okay? Good for you.. as i said, you have to follow the instruction very carefully. It includes all the version that they state. Matching the version of the software before start or else everything will become a mess. I experience that before.
:thumbup:
Sent from my GT-I9001 using xda app-developers app
Click to expand...
Click to collapse
sry i didn't replied sooner. as i see it wasn't my fault, someone posted a fix for the recoveries but.... almost bricked the phone.
i mean with the backup having that md5 mismatch error and the odin not working i couldn't do nothing. thanks god i managed to flash a strange cwm version,
i dont own this phone now and as i see i like the cm support, maybe i will buy it someday

[Q] Problem with my p880 after installing android.

Hey guys, I'm new here..idk if this is the right category but here we go: I tried to upgrade the software from the phone and after reboot just went in recovery mode and I found out I have no android. After that I copied stable cm 10.1 gapps on my sd card then I tried to install the zips, everything seemed ok..I restarted the phone and it went straight to recovery mode. I did the same thing with the android 4.4.2 MoKee and happend the same thing. What should i do?

kanaal said:
Hey guys, I'm new here..idk if this is the right category but here we go: I tried to upgrade the software from the phone and after reboot just went in recovery mode and I found out I have no android. After that I copied stable cm 10.1 gapps on my sd card then I tried to install the zips, everything seemed ok..I restarted the phone and it went straight to recovery mode. I did the same thing with the android 4.4.2 MoKee and happend the same thing. What should i do?
Click to expand...
Click to collapse
Try installing Symbian , just kidding.
Did you unlock the bootloader of the phone while you were on stock rom?

fuathan said:
yeah guys I ask anything ?
Click to expand...
Click to collapse
Apparently you do.

Coolneng said:
Try installing Symbian , just kidding.
Did you unlock the bootloader of the phone while you were on stock rom?
Click to expand...
Click to collapse
Yes, I unlocked the bootloader

kanaal said:
Hey guys, I'm new here..idk if this is the right category but here we go: I tried to upgrade the software from the phone and after reboot just went in recovery mode and I found out I have no android. After that I copied stable cm 10.1 gapps on my sd card then I tried to install the zips, everything seemed ok..I restarted the phone and it went straight to recovery mode. I did the same thing with the android 4.4.2 MoKee and happend the same thing. What should i do?
Click to expand...
Click to collapse
Can you little better describe how did you upgrade the software. Recovery, rom etc. Did you start at stock ICS or JB?

LGaljo said:
Can you little better describe how did you upgrade the software. Recovery, rom etc. Did you start at stock ICS or JB?
Click to expand...
Click to collapse
I had stock JB and I had this program in menu "Software update" and it was an 19-25 mb update..I downloaded and I installed the update then the phone rebooted and it went in cwm recovery. If I install a custom rom everything seems ok, after reboot it enter straight to recovery and I don't know why.

kanaal said:
I had stock JB and I had this program in menu "Software update" and it was an 19-25 mb update..I downloaded and I installed the update then the phone rebooted and it went in cwm recovery. If I install a custom rom everything seems ok, after reboot it enter straight to recovery and I don't know why.
Click to expand...
Click to collapse
If you set up working stock JB follow this:
*prepare custom ROM, kernel and Gapps then copy to SD
*if you want CWM download this: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.5-p880.img, then copy *.img file to a folder where adb is installed and rename it to recovery.img
*boot to fastboot mode (adb reboot oem-unlock)
*install recovery in fastboot mode (fastboot flash recovery recovery.img)
*power off, then boot to recovery
*flash ROM, Gapps and kernel

LGaljo said:
If you set up working stock JB follow this:
*prepare custom ROM, kernel and Gapps then copy to SD
*if you want CWM download this: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.5-p880.img, then copy *.img file to a folder where adb is installed and rename it to recovery.img
*boot to fastboot mode (adb reboot oem-unlock)
*install recovery in fastboot mode (fastboot flash recovery recovery.img)
*power off, then boot to recovery
*flash ROM, Gapps and kernel
Click to expand...
Click to collapse
Ok, I will try this but can you suggest me a good custom ROM and kernel? I never installed a kernel before and i don't know what to look for

kanaal said:
Ok, I will try this but can you suggest me a good custom ROM and kernel? I never installed a kernel before and i don't know what to look for
Click to expand...
Click to collapse
You don't really need different kernel, for first start I suggest you official CM11 nightly
Hit thanks if it helps

LGaljo said:
You don't really need different kernel, for first start I suggest you official CM11 nightly
Hit thanks if it helps
Click to expand...
Click to collapse
While I try to install the cwm I get this error http://i.imgur.com/d9nPSeI.jpg I installed with my cwm 6.0.4.4 the CM11 gapps and this kernel http://forum.xda-developers.com/showthread.php?t=2241474 all of these installed with no problems, after that i reboot and the cwm recovery appears w/o pressing the volume button.

kanaal said:
While I try to install the cwm I get this error
{
"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"
}
I installed with my cwm 6.0.4.4 the CM11 gapps and this kernel http://forum.xda-developers.com/showthread.php?t=2241474 all of these installed with no problems, after that i reboot and the cwm recovery appears w/o pressing the volume button.
Click to expand...
Click to collapse
I recommend you not to use this kernel, it is deprecated. Try without flashing different kernel first. Which CWM did you download? From link I gave?
EDIT: Have you done formats of /system, /data, /cache ?

You bugged out your device. OTA doesnt work properly with custom recovery installed. Reflash kdz to fix the issue,but try grabbing everything you need from via adb from recovery first as you may have to do hard reset from stock recovery which will format your internal sd (in case you dont know how to flash custom recovery via fastboot)

LGaljo said:
I recommend you not to use this kernel, it is deprecated. Try without flashing different kernel first. Which CWM did you download? From link I gave?
EDIT: Have you done formats of /system, /data, /cache ?
Click to expand...
Click to collapse
Yes, from the link you gave me and I did formated the /system, /data and /cache
Flying_Bear said:
You bugged out your device. OTA doesnt work properly with custom recovery installed. Reflash kdz to fix the issue,but try grabbing everything you need from via adb from recovery first as you may have to do hard reset from stock recovery which will format your internal sd (in case you dont know how to flash custom recovery via fastboot)
Click to expand...
Click to collapse
What kdz is? Sorry, but i'm new in this thing.

kanaal said:
Yes, from the link you gave me and I did formated the /system, /data and /cache
What kdz is? Sorry, but i'm new in this thing.
Click to expand...
Click to collapse
You can reflash or put phone to stock state with using lgmobile support tool. Just put phone in S/W mode (volume down and USB cable plug in) and in dropdown menu select update recovery

LGaljo said:
You can reflash or put phone to stock state with using lgmobile support tool. Just put phone in S/W mode (volume down and USB cable plug in) and in dropdown menu select update recovery
Click to expand...
Click to collapse
Ok, so i was following this tutorial http://forum.xda-developers.com/showthread.php?t=2069723 and on LG Mobile Support when I press install usb driver I can't find LGP880, why? maybe something is missing from pc like drivers or something like that?
EDIT: I did it, my phone works fine thank you very much! one more thing..can i install CM11 w/o problems now? i mean while i'm on 4.1.2

kanaal said:
Ok, so i was following this tutorial http://forum.xda-developers.com/showthread.php?t=2069723 and on LG Mobile Support when I press install usb driver I can't find LGP880, why? maybe something is missing from pc like drivers or something like that?
EDIT: I did it, my phone works fine thank you very much! one more thing..can i install CM11 w/o problems now? i mean while i'm on 4.1.2
Click to expand...
Click to collapse
yes, you can. the bug you encountered only happens when you use OTA with modified stock firmware.
good luck :good:

Flying_Bear said:
yes, you can. the bug you encountered only happens when you use OTA with modified stock firmware.
good luck :good:
Click to expand...
Click to collapse
Ok, I got it. Thank you! One more thing, I swear it! When I try to root my phone (I follow this guide http://forum.xda-developers.com/showthread.php?t=1818502 ), the SystemBackupTest doesn't work, I googled the problem and I found nothing.

kanaal said:
Ok, I got it. Thank you! One more thing, I swear it! When I try to root my phone (I follow this guide http://forum.xda-developers.com/showthread.php?t=1818502 ), the SystemBackupTest doesn't work, I googled the problem and I found nothing.
Click to expand...
Click to collapse
you are using deprecated method. that's method for ics. search for a way to root jellybean 20a.

Back to stock please

Hello all
I have an old Samsung Captivate, my kids were using it. Now they've new phones, so they left this aside.
Anyway, my son put cyanogen mod on this phone. But I want to put this back to stock. I tried the methods at http://forum.xda-developers.com/showthread.php?t=731989, but that didnot help, as I cannot yet go into download mode, as well as Odin or Samsung Kies does not recognize this device. It goes into recovery mode and shows CVM-based Recovery v6.0.3.1. There is no download link on this. I've tried vol down+power, then vol up+vol down+power, then just both volume buttons, but nothing helps.
The device is reconized by my laptop, and it is there under android devices in device manager, just doesnt get recognized by either samsung kies or odin.):
My all other samsung devices are working fine with the drivers I have.
I'm on Windows 10.
So please help me get this phone back to stock.
thanks

tahrang said:
Hello all
I have an old Samsung Captivate, my kids were using it. Now they've new phones, so they left this aside.
Anyway, my son put cyanogen mod on this phone. But I want to put this back to stock. I tried the methods at http://forum.xda-developers.com/showthread.php?t=731989, but that didnot help, as I cannot yet go into download mode, as well as Odin or Samsung Kies does not recognize this device. It goes into recovery mode and shows CVM-based Recovery v6.0.3.1. There is no download link on this. I've tried vol down+power, then vol up+vol down+power, then just both volume buttons, but nothing helps.
The device is reconized by my laptop, and it is there under android devices in device manager, just doesnt get recognized by either samsung kies or odin.):
My all other samsung devices are working fine with the drivers I have.
I'm on Windows 10.
So please help me get this phone back to stock.
thanks
Click to expand...
Click to collapse
Did you pull the battery before attempting the button combinations for getting into download mode?
If you did that, this thread may provide another way for you to get to download mode.
Is there a specific reason you are going back to stock Eclair, android 2.1, instead of using one of the newer one-click stock roms?
Others are available here. But then, that may be where you found the link to the rom you tried.
Which bootloader and modem were on the phone while it was in use? Which version of CM?

I've not used CM on any of my devices, I always use stock rom, even after I root.
Secondly, I am loaning this phone out to my friend, and she's not very digital savvy. I want to give her the phone with as little customization done as possible, because that's what she'll be most comfortable with.
I'll try the methods on the thread you posted above.
thanks

Hello
Nope, nothing helped, the phone just booted into the home page.
thanks

tahrang said:
I've not used CM on any of my devices, I always use stock rom, even after I root.
Secondly, I am loaning this phone out to my friend, and she's not very digital savvy. I want to give her the phone with as little customization done as possible, because that's what she'll be most comfortable with.
I'll try the methods on the thread you posted above.
thanks
Click to expand...
Click to collapse
I must have misunderstood what you said in the original post.
I thought you stated that the phone in question had cyanogenmod rom on it at one time, installed by your son. I also thought you said it currently had CWM Recovery, v6.0.3.1, installed. This could be important because some versions of CM ROM would require an update in the bootloader from the Eclair bootloader. Those versions would require an upgrade to the Gingerbread bootloader. This includes a re-partitioning of the internal harddrive. Supposedly the GB bootloaders will work with the Eclair roms
So far AT&T GB bootloaders have been backward compatible with all I897 (even I9000) Froyo/Eclairs ROMs. I have used I9000 based ROMs with AT&T GB BLs. Someone in CM7 thread claimed to use AT&T GB bootloaders with CM7 without any problem.
Click to expand...
Click to collapse
but if you are on the GB bootloader, why not try the GB stock rom, android 2.3.5?
Since you can get to the home screen, is the current rom fully functional?
What rom, and version, is it that you can boot into?
If it is CM, there should be an app named Terminal Emulator installed. If it is present you can run these two commands to determine the bootloader and modem that are on your phone:
Code:
getprop ro.bootloader
getprop | grep version.baseband

dawgdoc said:
I must have misunderstood what you said in the original post.
I thought you stated that the phone in question had cyanogenmod rom on it at one time, installed by your son. I also thought you said it currently had CWM Recovery, v6.0.3.1, installed. This could be important because some versions of CM ROM would require an update in the bootloader from the Eclair bootloader. Those versions would require an upgrade to the Gingerbread bootloader. This includes a re-partitioning of the internal harddrive. Supposedly the GB bootloaders will work with the Eclair roms
but if you are on the GB bootloader, why not try the GB stock rom, android 2.3.5?
Since you can get to the home screen, is the current rom fully functional?
What rom, and version, is it that you can boot into?
If it is CM, there should be an app named Terminal Emulator installed. If it is present you can run these two commands to determine the bootloader and modem that are on your phone:
Code:
getprop ro.bootloader
getprop | grep version.baseband
Click to expand...
Click to collapse
for bootloader, it says unknown.
for version.baseband it says [gsm.version.baseband]: [T959TLJL3]
When the phone bootsup, it shows cyanogen mod, then when I boot into recovery, it shows CVM Recovery, v6.0.3.1(and it says CVM, not CWM). So now I am confused what do I have on the phone?

tahrang said:
for bootloader, it says unknown.
for version.baseband it says [gsm.version.baseband]: [T959TLJL3]
When the phone bootsup, it shows cyanogen mod, then when I boot into recovery, it shows CVM Recovery, v6.0.3.1(and it says CVM, not CWM). So now I am confused what do I have on the phone?
Click to expand...
Click to collapse
You may have just given a valuable clue.
That baseband is from the Samsung Galaxy S Vibrant, a T-Mobile device, not the Samsung Galaxy S Captivate, an AT&T device.
Either someone flashed T-Mobile software on your Captivate. Or, you are trying to flash AT&T software on your Vibrant. I don't know if these devices and their software are cross compatible.
Could you remove the battery and check on the underlying label the model of the phone?

sgh 1897

tahrang said:
sgh 1897
Click to expand...
Click to collapse
It appears that a search of this forum has provided the solution.

didnt help, it just went to recovery mode.

tahrang said:
didnt help, it just went to recovery mode.
Click to expand...
Click to collapse
Without more details and answers to previous questions I am out of ideas.

just want to go into download mode.
thanks

dawgdoc said:
Without more details and answers to previous questions I am out of ideas.
Click to expand...
Click to collapse
Maybe these would help?
{
"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"
}
I tried out the samsung kies(old one) to see if that would connect. didnt connect.
Sent from my SM-P600 using Tapatalk

Hello
I found I had GooManager installed. will that be of any help here?

You said odin didnt recognized the phone right? I ll recommend uninstall the kies, that thing is always in the way and mess up the connection in odin

dennisbarcelonaflyman said:
You said odin didnt recognized the phone right? I ll recommend uninstall the kies, that thing is always in the way and mess up the connection in odin
Click to expand...
Click to collapse
Thanks for chiming in. That sounds vaguely familiar, but I have had no experience with Kies in years. I use Linux and Kies will not work on Linux based computers. (I think I used Kies for my first upgrade on my Captivate, back when I was still dual booting Linux and WinXP. That was the upgrade from Eclair to Froyo.)
Yes, @tahrang those pics help answer some of the other questions I asked. They show that you have the a Jellybean ROM installed using a Gingerbread kernel (GB). I think it is the PACman ROM. Hopefully removing Kies, as Dennis suggests, allows you to get to download with one of the many methods suggested in the thread I linked to works, then you can flash a stock rom. I would suggest one of the Odin-One-Click methods that installs a stock Gingerbread ROM. I think they final three identifiers begin with K, ones like KH3, KK4, etc. Use a one-click that does not install bootloaders, it is not needed at this time.

still not going into download mode. always goes into recovery ):
I can access the phone via my laptop. From recovery, if I have a rom zip file on the sd card, can I flash it that way? Where would I find such rom(stock) zip file?
thanks

tahrang said:
still not going into download mode. always goes into recovery ):
I can access the phone via my laptop. From recovery, if I have a rom zip file on the sd card, can I flash it that way? Where would I find such rom(stock) zip file?
thanks
Click to expand...
Click to collapse
Yes, you can flash roms from CWM recovery. The One-Click files will not work for this. You will need to use a recovery flashable zip. You can find stock and custom roms in the Development sub-forum. With the Captivate and CWM recovery you need to put the flashable zip on the root of the internal sdcard, IIRC. I don't think it will flash the rom from the external sdcard.
Since your laptop will access the phone, did you use either of the adb methods to boot into download mode? They are described in one of the other threads I linked.
Also, you could use adb to flash the portions of a rom, whichever type it is - recovery flashable or Odin one-click. But you would need the adb/flashboot tutorial threads to understand that process and the commands involved.

can you send the link to the flashable zip files?
thanks

tahrang said:
can you send the link to the flashable zip files?
thanks
Click to expand...
Click to collapse
The link in the previous post will lead to them. The early posts in that sub-forum are to the one-clicks. The custom roms on the first page are flashable zips. It may take going through several pages to find a stock rom that is a flashable zip with a valid download link. I am on a slow connection with limited data, I can't test the downloads for you.

[ROOT GUIDE] SamPWNED32 - Samsung J3 prime SM-J327T/SM-J327T1

Welcome to the root guide thread for the SAMSUNG J327T/T1 GALAXY J3 PRIME
This guide will show you how to root the J3 prime 2017, Exynos 7570 released by Tmobile and MetroPCS.
If you choose to follow the steps below, you should be aware of the risks.
While minimal, neither myself or thepcwiz101 accept any responsibily for broken devices.
Unfortunately this device has a locked bootloader and root so far has been elusive for this device. Many have tried different methods to no avail.
Finally it is here.
Through much research by @thepcwiz101 we came by a method that uses an ENG firmware to gain root. Basically this firmware is an engineering firmware with the su binary already installed which can be used to leverage some scripts to gain proper root with Supersu.
I went on the hunt for this firmware and found it.
Then we needed a method to push Supersu to the ENG firmware.
The Samsung S8/S8+ already used a similar method to root that device, so I took the script they used called SamPWNED and modified it to work for this device. We'll call this SamPWNED32.
Please see credits below for more info.
@thepcwiz101 did most of the testing along with a few others and finally we had success.
To see how we got here you can refer to the thread below:
https://forum.xda-developers.com/galaxy-j3-2017/help/samsung-galaxy-j3-prime-sm-j327t1-t3604860
Follow the steps below and at the end of it you should have a rooted device.
I strongly advise backing up all your settings and personal data before continuing. YOU HAVE BEEN WARNED!
Smartswitchmobile can be used to back up apps and settings to an SDCARD.
https://play.google.com/store/apps/details?id=com.sec.android.easyMover&hl=en_GB
************** INSTALLATION STEPS **************
Step 1.
Download the required files:
http://www.mediafire.com/file/s6hn38hb5wkiqsw/J327T_J327T_J327TUVU1AQC3_ROOT.zip
Step 2.
Unpack the package you downloaded above.
Put your device in DOWNLOAD mode (POWER + HOME + VOL DOWN)
Run Prince Comsey ODIN
Click the AP button then locate the ODIN flashable file you downloaded in the package named:
J327T_J327T1_J327TUVU1AQC3-eng.tar
Tick NAND Erase All
Leave all other ODIN options at default then click START.
Wait for the files to finish flashing and your device reboots. Disconnect the USB cable then remove the battery.
Force boot to recovery by holding POWER + HOME + VOL UP.
In recovery select Factory Reset then reboot the device.
Put the device to one side, have a coffee and wait a good ten minutes or so for the device to boot.
Step 3.
Once your device has fully rebooted you will be running the engineering firmware. This firmware isn't really good for a daily driver, so we're only using it to gain root.
Plug in the USB cable.
Your device should have USB debugging already enabled and a pop up should ask you to accept the connection to your PC. Accept the pop up to enable USB debugging for your PC.
Step 4.
Now to begin the root process.
Locate the root.bat file in the SamPWND32_Root folder and double click it to run it.
You should see a bunch of stuff on the screen as it does it thing and then your device should reboot.
When your device reboots you should now be rooted with SuperSU!
Step 5.
As mentioned in Step 3, this firmware isn't really good as a daily driver, so we're going to replace it with the stock firmware using Flashfire.
Download the stock firmware for your device from https://updato.com
Download Flashfire from the Play store: https://play.google.com/store/apps/details?id=eu.chainfire.flash&hl=en_GB
Download the Supersu system mode root package: https://forum.xda-developers.com/attachment.php?attachmentid=4289379&d=1506893064
Step 6.
Run Flashfire and agree when it asks for root permission.
In the main screen tap the + button then select Flash firmware Package and locate the stock firmware package you downloaded.
IMPORTANT: Uncheck the BOOT partition. Leave the rest enabled. Tap the tick top right when done. in the next screen tap EverRoot and uncheck Inject SuperSU and Preserve recovery. Tap the tick top right when done.
In the main screen again tap the + and then select Flash zip or OTA and locate the SR5-SuperSU-v2.82-SYSTEMMODE.zip
Check Mount /system read/write and leave everything else unchecked and then tap the tick when done.
Check you have the following selected on the main screen:
Flash Firmware package - The stock firmware with BOOT disabled.
Flash zip or OTA - System mode Supersu
EverRoot - disabled
Reboot - Normal
Ensure that System mode supersu is last on the list after the firmware or it won't root the new firmware.
Now tap FLASH and let Flashfire do it's thing.
When your device reboots you should be rooted and running the stock firmware.
If your devices suffers a kernel panic at any point take the battery out and reboot. Give it time and your device should stabilise.
I suggest factory resetting after performing the above procedure as this may make your device more stable if it's clean and fresh.
There is also an updated eng boot binary posted below which may help.
Hopefully you now have a fully rooted device.
{
"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"
}
IMPORTANT NOTE:
THE DEVICE STILL HAS A LOCKED BOOTLOADER. DO NOT ATTEMPT TO FLASH A CUSTOM RECOVERY OR ANYTHING THAT MODIFIES THE BOOT PARTITION. DO NOT REPLACE THE BOOT IMAGE EITHER.
DOING ANY OF THE ABOVE WILL SOFT BRICK THE DEVICE.
CREDITS:
ME(ashyx)
@thepcwiz101
@elliwigy and the SamPWNED devs (To donate or see who was involved in creating SamPWNED see this link, they deserve the credit for creating it.)
https://forum.xda-developers.com/ga...root-g955u-g955u1-snapdragon-sampwnd-t3658911
@Chainfire
@mauam for System mode Supersu
Anyone that tested.
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
DONATE ME HERE IF YOU WANT TO BUY ME A BEER/COFFEE OR HIT THE THANKS BUTTON IF I HELPED YOU

UPDATE 15/3/2018
Below is an updated eng binary(boot image) which may help with instability problems and kernel panics
This can be flashed with ODIN or Flashfire.
https://www.mediafire.com/file/q8j4b4ozvmwfrz7/J327TUVU1AQI1_eng_boot.tar
.

Just wanna say thanks to all that have put in the countless hours and hard work to finally give this device a root method. Will be testing this out as soon as I get home. Will post any issues or recommendations after flashing. Great work guys.

Samsung FAILS again!

ashyx said:
Please note this thread is still under construction and subject to change.
Click to expand...
Click to collapse
I think you hit the thread spot on. Also for anyone who would like to do further testing. here is my build.prop i edited. All it does is disable samsung's security features which i think is still enabled even when making supersu disable knox. Feel free to test out my build.prop. Warning do not use adb to transfer it. for some reason even when system is R/W it doesnt transfer and overwrite the original file it. when i did this i tried to transfer it using a root file manager and i was too late and a kernel panic caught me at the wrong time and when it rebooted it refused to load as build.prop was missing. After this (the 5th time rooting) i decided just to go back to stock as my phone is the only internet source i got.

thepcwiz101 said:
I think you hit the thread spot on. Also for anyone who would like to do further testing. here is my build.prop i edited. All it does is disable samsung's security features which i think is still enabled even when making supersu disable knox. Feel free to test out my build.prop. Warning do not use adb to transfer it. for some reason even when system is R/W it doesnt transfer and overwrite the original file it. when i did this i tried to transfer it using a root file manager and i was too late and a kernel panic caught me at the wrong time and when it rebooted it refused to load as build.prop was missing. After this (the 5th time rooting) i decided just to go back to stock as my phone is the only internet source i got.
Click to expand...
Click to collapse
Knox was already disabled on the firmware I've provided in the other thread, just saying.

MiiJack said:
Knox was already disabled on the firmware I've provided in the other thread, just saying.
Click to expand...
Click to collapse
Knox isn't just one thing, it's a number of services running in the background.

So got a noob question. Since we don't have the ability to have a custom recovery cuz of the locked bootloader any zips that we want to flash have to be done using abd correct? Or would it be possible to use the stock recovery using the install update from sd card option?

hatchet13rydin69 said:
So got a noob question. Since we don't have the ability to have a custom recovery cuz of the locked bootloader any zips that we want to flash have to be done using abd correct? Or would it be possible to use the stock recovery using the install update from sd card option?
Click to expand...
Click to collapse
the update from sd card option doesnt work. all it does is check signatures and anything that doesnt got samsungs signature will fail to flash.
---------- Post added at 12:32 PM ---------- Previous post was at 12:32 PM ----------
ashyx said:
Knox isn't just one thing, it's a number of services running in the background.
Click to expand...
Click to collapse
i know.

thepcwiz101 said:
the update from sd card option doesnt work. all it does is check signatures and anything that doesnt got samsungs signature will fail to flash.
That's what I thought. So basically I'll have to use adb to install any zips correct?
Edit.. nevermind my smart self forgot all about flashfire as the guide tells me to use for the root method.
Click to expand...
Click to collapse

hatchet13rydin69 said:
That's what I thought. So basically I'll have to use adb to install any zips correct?
Click to expand...
Click to collapse
No, you use Flashfire which pretty much does the same as any custom recovery and then some.

ashyx said:
hatchet13rydin69 said:
No, you use Flashfire which is pretty much does the same as any custom recovery and then some.
Click to expand...
Click to collapse
I feel like a complete noob right now. It's been a long day lol
Click to expand...
Click to collapse

thepcwiz101 said:
i know.
Click to expand...
Click to collapse
That was in response to MiiJack.

ashyx said:
That was in response to MiiJack.
Click to expand...
Click to collapse
my bad i must have misread your post.

Hey everyone i literally found a way to make a custom rom for this device. Take a look on the tmobile s8 thread. They have a locked bootloader just like us and yet they got a custom stock rom that has alot of optimizations they use flashfire to flash the rom. If anyone knows enough to build a heavily modified stock rom please start a thread. I can provide the kernel files if needed as samsung released the kernel soon after releasing this phone. We need a more stable kernel to stop these kernel panics.

thepcwiz101 said:
Hey everyone i literally found a way to make a custom rom for this device. Take a look on the tmobile s8 thread. They have a locked bootloader just like us and yet they got a custom stock rom that has alot of optimizations they use flashfire to flash the rom. If anyone knows enough to build a heavily modified stock rom please start a thread. I can provide the kernel files if needed as samsung released the kernel soon after releasing this phone. We need a more stable kernel to stop these kernel panics.
Click to expand...
Click to collapse
Modified ROM is no problem to flash, it's no different to the stock rom after rooting/installing xposed etc, but a custom kernel is a no go I'm afraid.

ashyx said:
Modified ROM is no problem to flash, it's no different to the stock rom after rooting/installing xposed etc, but a custom kernel is a no go I'm afraid.
Click to expand...
Click to collapse
Well i think we could flash the updated kernel that is stock as its more stable. It shouldnt be blocked by the bootloader. And also the kernel is inside of fota.zip but im afraid it may cause root to be lost. Only testing will show for sure. I would only flash the stock kernel after reflashing the stock system.img using flashfire. Then attempt to obtain root with supersu and try to use terminal emulator. If you get root attempt to run the root script again to repatch the kernel if at all possible. As the root script patches uevent_helper inside /sys/kernel

thepcwiz101 said:
Well i think we could flash the updated kernel that is stock as its more stable. It shouldnt be blocked by the bootloader. And also the kernel is inside of fota.zip but im afraid it may cause root to be lost. Only testing will show for sure. I would only flash the stock kernel after reflashing the stock system.img using flashfire. Then attempt to obtain root with supersu and try to use terminal emulator. If you get root attempt to run the root script again to repatch the kernel if at all possible. As the root script patches uevent_helper inside /sys/kernel
Click to expand...
Click to collapse
You can't use a stock kernel nor can it be patched. We don't need to go down this road again here. It's all been covered in the previous thread.
To gain root an eng boot image is needed otherwise the device will simply soft brick due to integrity check failure.
The images I have provided here contain the latest eng boot from the combo firmware which should in theory be more compatible with later stock firmwares.
On another note, no info whatsoever in the form of logs has been provided regarding the kernel panics.

ashyx said:
You can't use a stock kernel nor can it be patched. We don't need to go down this road again here. It's all been covered in the previous thread.
To gain root an eng boot image is needed otherwise the device will simply soft brick due to integrity check failure.
The images I have provided here contains the latest eng boot from the combo firmware which should in theory be more compatible with later stock firmwares.
On another note, no info whatsoever in the form of logs has been provided regarding the kernel panics.
Click to expand...
Click to collapse
Ok i must have had a brain fart there. Well and thats because i have been literally unable to get them as the crashes happen before i can get a logcat going. I personally wouldnt do anything unless the crashes havent happend after 30 mins of the phone being on bc if your in a file transfer or changing a system file like build.prop you would go into a soft brick if you get a kernel panic during it. It happend to me and i wasnt happy about it which made me decide to go back to full stock. But just saying as soon as i am able to start a catlog the panics stop.

thepcwiz101 said:
Ok i must have had a brain fart there. Well and thats because i have been literally unable to get them as the crashes happen before i can get a logcat going. I personally wouldnt do anything unless the crashes havent happend after 30 mins of the phone being on bc if your in a file transfer or changing a system file like build.prop you would go into a soft brick if you get a kernel panic during it. It happend to me and i wasnt happy about it which made me decide to go back to full stock. But just saying as soon as i am able to start a catlog the panics stop.
Click to expand...
Click to collapse
Logging starts as soon as the device is booted, so last_kmsg should contain info up to the crash.
Logcat won't be of any use as it'll only be for the currently booted system.
However it can be piped to a file or via adb to windows up until it crashes.