Related
This is all thanks to the awesome threads on this website.. No credit of programming will be claimed by me.
*warning* this can be done only if you have a device that forces the samsung galaxy s g or gt i9000 to go in to download mode.
Ok so here is the story, when the samsung galaxy S froyo beta was out I kind of editted the regedit of samsung to be able to install it...
What I didn't know and wasn't noticed by anyone as I've surfed down google to the 200th pages... was that after the reg edit update the Volume down + home button + off switch combination falls of and will not work anymore.
So I waited untill it was out officially in the Netherlands (eindhoven)
What I did was the folowing:
I went to vodafone and they tried to update it. with the force device (big blue box with 12 buttons on it with the buttons 2 and 6 were clicked down).
When they tried to update the phone went off and it lost it's complete firmware. aka PHONE - ! - COMPUTER.. I went home and searched of the web and found here that there was a kind off update.zip. (when I find it I will edit this post and upload it) I downloaded the file and extracted the contents on a SD card. I went back to vodafone and let them force the phone in to download mode again. after that odin instantly recognized and updated the phone to Android 2.2 Froyo update for Galaxy S.
So here are the simple steps.
1. Don't panic.
2. Surf this forum for the update.zip if I still haven't uploaded it. and mainly search for the tag: black screen of death. or phone + ! + computer.
When you have the file. follow step 3.
3. Extract the contents of the update.zip file to the removable SD card of your phone with another device note like root:Sd/update/(files) but like root:sd/(files) the files must be directly available to the phone without having to be searching in to another folder. and plug the sd-card back in the phone.
4. If you have such blue device to force in to download mode then just use odin and update phone. if not, then go to the nearest and trustworthy phone store and make them force it into the download mode... and follow the rest of the steps.
5. step 5 is the most attention worthy part there is: Either bring your own laptop with the correct odin and the correct files and USB cable for when it's in download mode to update it. or either give it to the person behind the counter and let him update it.
6. When froyo is installed give it time to run and scan all it needs to do, otherwise it will lagg and only frustrate you.
7. after couple of minutes froyo is ready for use. after this.look for a reliable lagg fixer because froyo laggs the same way the mind of your mother-in-law does when you're trying to talk sense in to her mind...
If I'm correct after these steps you should be able to use your phone again and have froyo installed and working.
If this hasn't worked, then I advice to either repeat these steps (hence the bring your own laptop) or let the phone-store guy do his thing and force the install. REMEMBER these people usually give up after 1 or 2 try's but it's your phone and they don't care.. so just stand firm and say, I would like you to give it another try..and if he refuses. you can just tell him you won't leave untill he has done it over and over untill it's done or let you self try it and crawl behind the counter.
ALL CREDITS GO TO THE PEOPLE THAT HAVE WRITTEN THE PROGRAMS AND GIVEN ME THE OPPORTUNITY TO COMBINE THE STEPS AND FIX THIS.
But hey if you think the credits belong to me since I wrote this guide. then by all means
I can't access the recovery mode, but I can access the download mode. I also used the Kies registry hack to upgrade to 2.2.
Which update.zip file you are talking about? There are a million different ones!
I do not have an external SD card. Is it still possible to fix the phone? No offense but your solution doesn't really offer a solution at all. It only tells us to go somewhere else to get it fixed!
What is the correct Odin, what are the correct files? PIT, PDA, PHONE, CSC, update.zip? Links?
Here are the files and instructions to get root and CWM on a Samsung Conquer 4G with the FC17 update. To enter Download Mode on the phone, make sure the phone is turned off and plugged into the wall charging. You should also make sure the phone has a good charge on it. Then turn the phone on by pressing the volume down and camera button and holding them while pressing the power button for a few seconds.
Here are the files you will need -
CONQUER-ROOT.zip
Unzip all the files on your computer and follow these steps.
1) Enter download mode on the phone and plug it into your computer. Open up the Odin program. Then press the OPS button and select the SPH-D600_FC17_CWM.ops file. Then press the PDA button and select the SPH-D600_FC17_CWM.tar.md5 file. The press the Start button, the images should install and the phone reboot. Congrats, your phone now has a stock FC17 image with a CWM Recovery.
2) Next, copy the Superuser-3.0.7-efghi-signed.zip and su-bin-3.0.3.2-efghi-signed.zip files to the root of your SD Card after booting up.
3) Once the phone boots up, go into settings, select Applications, then Development, then turn on USB debugging. Now you can restart the phone into recovery mode with adb. If you don't want to use adb, you can plug the phone into the wall and turn it on while holding the volume down and power button. Either way is fine, as long as you now get the phone into recovery mode.
4) The phone should now go into CWM recovery. Go to install zip from sdcard and select the Superuser-3.0.7-efghi-signed.zip file you put on the sdcard and install that. Next select the su-bin-3.0.3.2-efghi-signed.zip file from your sdcard and install that.
5) Congratulations, you now have a rooted phone with the FC17 update. If you had CWM installed before, you can now do an advanced back-up, and just restore the data from your most recent backup and get all your data back.
I've created a new custom ROM here - http://forum.xda-developers.com/showthread.php?p=29369141
You can just download the new files and follow those instructions if you haven't installed this yet.
it work like charm thank you very much sir very good job done..........
---------- Post added at 04:47 AM ---------- Previous post was at 04:38 AM ----------
there is any custom rom kool one ...
I know on the E4GT, sfhub is able to make tar's that do not wipe user data. The file difference between the 2 images are
removed: boot.bin, sbl.bin, param.lfs, cache.img, data.img
intact: recovery.bin, hidden.img, factoryfs.img(largest file) modem.bin and zImage(contains the kernel)
The Question I'm posing to you is which of the files in the conquer tar.md5 might be the counterparts to the above files, making them the ones to strip out in order to make it not wipe data?
My wife never wanted me to root her phone until recently, so no cwm backup that's pre-OTA, and there are some apps that don't work when re-installed (a security key-gen app)
Any help would be much appreciated.
AestenD said:
I know on the E4GT, sfhub is able to make tar's that do not wipe user data. The file difference between the 2 images are
removed: boot.bin, sbl.bin, param.lfs, cache.img, data.img
intact: recovery.bin, hidden.img, factoryfs.img(largest file) modem.bin and zImage(contains the kernel)
The Question I'm posing to you is which of the files in the conquer tar.md5 might be the counterparts to the above files, making them the ones to strip out in order to make it not wipe data?
My wife never wanted me to root her phone until recently, so no cwm backup that's pre-OTA, and there are some apps that don't work when re-installed (a security key-gen app)
Any help would be much appreciated.
Click to expand...
Click to collapse
Take out userdata.yaffs to retain your data, BUT you will have to rebuild the tar file and remake the OPS file by removing the line that reads -
Code:
9,userdata
If you need the Linux commands to rebuild the image, let me know.
brienj said:
Take out userdata.yaffs to retain your data, BUT you will have to rebuild the tar file and remake the OPS file by removing the line that reads -
Code:
9,userdata
If you need the Linux commands to rebuild the image, let me know.
Click to expand...
Click to collapse
Crap, and me with no Linux box lol
I'll figure something out, I have a live CD around here somewhere.
AestenD said:
Crap, and me with no Linux box lol
I'll figure something out, I have a live CD around here somewhere.
Click to expand...
Click to collapse
Just install Cygwin and use that and then extract all the files out of the .md5 file, it's just a regular tar file with md5 sums in it. WinZip, WinRAR, etc. will easily extract the files from it. Then use these commands to rebuild the image without the userdata.yaffs file.
tar -H ustar -c adsp.mbn amss.mbn appsboot.mbn boot.img cache.yaffs mibib osbl recovery.img system.yaffs > package_name.tar
md5sum -t package_name.tar >> package_name.tar
mv package_name.tar package_name.tar.md5
Click to expand...
Click to collapse
You can replace each package_name with whatever you want it called.
brienj said:
Just install Cygwin and use that and then extract all the files out of the .md5 file, it's just a regular tar file with md5 sums in it. WinZip, WinRAR, etc. will easily extract the files from it. Then use these commands to rebuild the image without the userdata.yaffs file.
You can replace each package_name with whatever you want it called.
Click to expand...
Click to collapse
Thanks for your help, took me a bit, because I mistakenly flashed the non-CWM image first, and the bootloader version just wasn't letting me in. Luckily I have a jig for my SGS2, and I'm up and running now. Hopefully just the fact that it's the full image, rather than OTA upgraded will fix some of the issues she's been having. If not, then having root gives me so many more troubleshooting options.
give me an error says the SPH-D600_FC17_CWM.tar.md5 is invalid image type please help
sromero619 said:
give me an error says the SPH-D600_FC17_CWM.tar.md5 is invalid image type please help
Click to expand...
Click to collapse
"known issue" just keep going, it'll work just fine.
Sent from my SPH-D710 using Tapatalk
sromero619 said:
give me an error says the SPH-D600_FC17_CWM.tar.md5 is invalid image type please help
Click to expand...
Click to collapse
It says this, even with an official Sprint Odin image. It will still work, like AestenD mentioned.
i did all the step but when i hit start on the odin it says please connect phones what can else can i do. loaded the drive from super one click because my laptop running windows seven wasn't reading my phone. Its reading my phone I downloaded the usb driver from this link http://r2doesinc.bitsurge.net/leaked/
now when i run odin now it say """an unnamed file was not found""" whats to do please help
brienj said:
It says this, even with an official Sprint Odin image. It will still work, like AestenD mentioned.
Click to expand...
Click to collapse
i got the phone to be read but now when i hit the start button a window pops out says "unnamed file is not found"
It worked for me.
Question
I have been reading up on this phone since I ordered it from my new provider. I should get the phone sometime later today and wanted to get everything ready to root it as soon as I get it. I've read JWhip804's tutorial on how to root the Conquer. I've also been keeping up with chrystal0925's efforts at making a working themed ROM.
My question is, if I want to have a recovery of my stock phone just in case I have to send it back to my carrier, should I use the method described in this thread or use JWhip804's thread?
I have a brand new Samsung Conquer SPHD600BKS on the Sprint network using a new provider to my area called Ting.
Android Version: 2.3.4
Baseband Version: S: D600.12 x.EG15
Kernel Version: 2.6.35.7-perf
Build Number: GINGERBREAD.EG15
Hardware Version: D600.12
Thanks.
roofus1812 said:
I have been reading up on this phone since I ordered it from my new provider. I should get the phone sometime later today and wanted to get everything ready to root it as soon as I get it. I've read JWhip804's tutorial on how to root the Conquer. I've also been keeping up with chrystal0925's efforts at making a working themed ROM.
My question is, if I want to have a recovery of my stock phone just in case I have to send it back to my carrier, should I use the method described in this thread or use JWhip804's thread?
I have a brand new Samsung Conquer SPHD600BKS on the Sprint network using a new provider to my area called Ting.
Android Version: 2.3.4
Baseband Version: S: D600.12 x.EG15
Kernel Version: 2.6.35.7-perf
Build Number: GINGERBREAD.EG15
Hardware Version: D600.12
Thanks.
Click to expand...
Click to collapse
Super-One-Click only works on EC15, and you can not do an OTA update to FC17 with root, and once you do update to FC17, Super-One-Click will no longer work to root your phone, so you must use the method I have made in this thread, or a similar one to it. You MUST get a stock FC17 image with the CWM recovery to push root onto your phone, as the OTA update has recovery updating scripts, etc. in it, and it's just easier to use the FC17 image and not bother with making the OTA able to be rooted. In order to get the phone back to a stock image, you can easily find the stock Odin image that is floating around, or change the recovery image in the Odin file I have in this thread, with a stock recovery image.
Finished
brienj said:
Super-One-Click only works on EC15, and you can not do an OTA update to FC17 with root, and once you do update to FC17, Super-One-Click will no longer work to root your phone, so you must use the method I have made in this thread, or a similar one to it. You MUST get a stock FC17 image with the CWM recovery to push root onto your phone, as the OTA update has recovery updating scripts, etc. in it, and it's just easier to use the FC17 image and not bother with making the OTA able to be rooted. In order to get the phone back to a stock image, you can easily find the stock Odin image that is floating around, or change the recovery image in the Odin file I have in this thread, with a stock recovery image.
Click to expand...
Click to collapse
I just finished backing up my Conquer using this guide. It was really easy. Thanks.
Hi guys. Anyone use tethering with this? I had tethering working on the old rom fine and another unrooted phone with the ota update. I got a replacement phone and tethering does not work. It only works for google sites - with any tethering app i tried. Is it the hardware or maybe its the stock fc17? I tried reflashing and clearing everything and the problem persists.
I tried using Odin today to root my Samsung Conquer and had a bit of trouble. When I attached the .tar file it gave me an error but as I read this thread I just kept going as if there was no issue. About half way through the Odin installation my phone just rebooted, I tried again and it rebooted it the same spot. I tried putting my phone back into download mode and continue the process, which it did, and I got a "Pass" message at the end. But I don't have CWM and I'm almost positive its still not rooted. Any suggestions?
Any chance of an update with the new OTA included?
Sent from my SPH-D710 using xda premium
There is a new ota fe17. Does anyone know if it will break root? Will it install?
Sent from my SPH-D600 using XDA
I can't really take credit for this, but I just restored my IMEI without a backup of the efs folder. Keep in mind that I actually deleted my efs folder by accident, so I didn't even have the original efs folder.
The original thread I referenced is here:
http://forum.xda-developers.com/showthread.php?p=31771228#post31771228
FYI, this method will restore your phone to stock Gingerbread.
Here is what you do:
1.)
A) Download and unzip the Gingerbread unbrick package here from (http://forum.xda-developers.com/showthread.php?p=27286083#post27286083):
w/ root - http://d-h.st/ewu
w/o root - http://d-h.st/G6g
B)
Download and unzip the efs zip here:
http://forum.xda-developers.com/attachment.php?attachmentid=1152914&d=1340558510
2.) Place phone in download mode.
3.) If needed, install latest Samsung USB drivers by installing Samsung Kies from HERE.
4.) Open the included Odin exe.
5.) If phone is detected, the window under ID:COM will turn yellow.
6.) Click on "PIT" to browse to and select infuse_gb.pit. Make sure that Re-Partition is selected.
7.) Click on "PDA" to browse to and select PDA_UCLB3.tar.md5.
8.) Click on "PHONE" to browse to and select PHONE_UCLB3.tar.md5.
9.) Click on "CSC" to browse to the efs.tar
10.) Click the Phone EFS Clear checkbox
11.) Click on "Start", and allow Odin to flash the phone. Do not unplug or power off the phone until Odin is finished.
12.) When the Odin dialogue reads "PASS!", the phone should reboot into the stock UCLB3 Setup Wizard. For me this step just proceeded to install an update and the reboot the phone.
Once the phone reboots, if your SIM card is installed you should be good to go, otherwise you will get an alert about your SIM card which means you need to power off and pop in the SIM card.
Thanks to the original thread author for this one.
It works perfect for me even without the .nv_data file. Before this i only get simbols instead the imei number. You save my phone!
recovered IMEI by just flashing the CM10 base
I dunno if it's just me or what. I lost my IMEI on Slim Bean.. so I had this thought. I hadn't had this issue with the CM10 rom, so I decided to do the standard flashing procedure. Once CM10 was installed my IMEI came back. I had full signal and all is good. I decided to go back to Slim Bean to see if it would fix the IMEI issue. I flashed it just like the OP stated and walah! I had my IMEI back and everything worked without having to go back to GB, ICS and then JB again. I don't know if this will help anyone, but just wanted to note other people about it. Why did this work for me?
will this mess up my phone more?
I am running froyo 2.2.1 ,I guess it is stock, as I pick this phone up in pawn shop, and it was already rooted. I was doing the command line argument dd and a bunch of stuff, to get some file to get my unlock code. I didn't get no bak file copy, gave up put my sim card back in and that's when I noticed my imei was gone, then I had go launcher installed, so my screen goes blank I end up having to do the three finger data wipe, then I see I got no wifi either. Then I get this phone, DL some apk files, try to reinstall busy box, no go, teller me it don't think it has su permission after I gave it through that super user program, then it say it cant install into /dev/sh/ what ever, so all I got is a really nice looking video player.
So now that I got all that out of me.
2 questions, will flashing gingerbread overtop of froyo, will not make it worse?
Why do one have to flash in the first place, why can't one just copy over the old-time files, or someone find which file goods the imei number then just to in isinglass a file manager open that file, as it should be just what is caller a flat file, meaning no special formating like a Word file.
Then just save it. I am not an expert at android wse (whatsoever) but I have played with copying over top of files, or deleting the old-time one then replacing it with a new one. Why Doesn't that work, has anyone player around just opening there files to see what they look like and figure out where they stick the imei number?
Seems to me should be an easy manner of doing, but now that I don't have an individual showing I am not even sure which file I should try to type that number in to to see what will happen as I don't want to make this phone completely useless.
Any commentary, ideas, anything?
Thanks
MikieD
mikied12 said:
I am running froyo 2.2.1 ,I guess it is stock, as I pick this phone up in pawn shop, and it was already rooted. I was doing the command line argument dd and a bunch of stuff, to get some file to get my unlock code. I didn't get no bak file copy, gave up put my sim card back in and that's when I noticed my imei was gone, then I had go launcher installed, so my screen goes blank I end up having to do the three finger data wipe, then I see I got no wifi either. Then I get this phone, DL some apk files, try to reinstall busy box, no go, teller me it don't think it has su permission after I gave it through that super user program, then it say it cant install into /dev/sh/ what ever, so all I got is a really nice looking video player.
So now that I got all that out of me.
2 questions, will flashing gingerbread overtop of froyo, will not make it worse?
Why do one have to flash in the first place, why can't one just copy over the old-time files, or someone find which file goods the imei number then just to in isinglass a file manager open that file, as it should be just what is caller a flat file, meaning no special formating like a Word file.
Then just save it. I am not an expert at android wse (whatsoever) but I have played with copying over top of files, or deleting the old-time one then replacing it with a new one. Why Doesn't that work, has anyone player around just opening there files to see what they look like and figure out where they stick the imei number?
Seems to me should be an easy manner of doing, but now that I don't have an individual showing I am not even sure which file I should try to type that number in to to see what will happen as I don't want to make this phone completely useless.
Any commentary, ideas, anything?
Thanks
MikieD
Click to expand...
Click to collapse
This is either a joke or a joke.
Many Thanks
zackdjones said:
I can't really take credit for this, but I just restored my IMEI without a backup of the efs folder. Keep in mind that I actually deleted my efs folder by accident, so I didn't even have the original efs folder.
The original thread I referenced is here:
http://forum.xda-developers.com/showthread.php?p=31771228#post31771228
FYI, this method will restore your phone to stock Gingerbread.
Here is what you do:
1.)
A) Download and unzip the Gingerbread unbrick package here from (http://forum.xda-developers.com/showthread.php?p=27286083#post27286083):
w/ root - http://d-h.st/ewu
w/o root - http://d-h.st/G6g
B)
Download and unzip the efs zip here:
http://forum.xda-developers.com/attachment.php?attachmentid=1152914&d=1340558510
2.) Place phone in download mode.
3.) If needed, install latest Samsung USB drivers by installing Samsung Kies from HERE.
4.) Open the included Odin exe.
5.) If phone is detected, the window under ID:COM will turn yellow.
6.) Click on "PIT" to browse to and select infuse_gb.pit. Make sure that Re-Partition is selected.
7.) Click on "PDA" to browse to and select PDA_UCLB3.tar.md5.
8.) Click on "PHONE" to browse to and select PHONE_UCLB3.tar.md5.
9.) Click on "CSC" to browse to the efs.tar
10.) Click the Phone EFS Clear checkbox
11.) Click on "Start", and allow Odin to flash the phone. Do not unplug or power off the phone until Odin is finished.
12.) When the Odin dialogue reads "PASS!", the phone should reboot into the stock UCLB3 Setup Wizard. For me this step just proceeded to install an update and the reboot the phone.
Once the phone reboots, if your SIM card is installed you should be good to go, otherwise you will get an alert about your SIM card which means you need to power off and pop in the SIM card.
Thanks to the original thread author for this one.
Click to expand...
Click to collapse
I just wanted to thank all of you who have contributed your brain power to the xda forums. This advise worked great and after a lot of self doubt I now consider myself a semi-noob. Thanks again.
A J
Thanks on this. I had a backup of my EFS folder, but the tool I used to create it made a .img file and once I got it into JB, the tool didnt work. UGH.
Just want to say thank you for posting this. I have a friend who had her Infuse stop getting calls, texts, etc. Turns out her IMEI was all question marks and other invalid characters. ATT wouldn't help her at all and either did a full reset.
thank you, this method really works!! finally my imei is back...no more symbols, now is time for a efs back up
Since when do phones lose their imei's? That's a new one on me.
sholsten said:
Since when do phones lose their imei's? That's a new one on me.
Click to expand...
Click to collapse
It happened for me twice on two separate phones when using MIUI. Basically the ROM managed to corrupt the system partition, specifically the efs folder.
I don't know the specifics of why, but it happens to a lot of people. That's why I always now make sure I have a backup of the efs just in case.
Sent from my SAMSUNG-SGH-I717 using xda premium
zackdjones said:
It happened for me twice on two separate phones when using MIUI. Basically the ROM managed to corrupt the system partition, specifically the efs folder.
I don't know the specifics of why, but it happens to a lot of people. That's why I always now make sure I have a backup of the efs just in case.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
This method didn't work for me :\ Any other ways to solve this issue?
can i use this Efs on galaxy R to repair unknown baseband & Blank imei????
Thank you very much. This is what I need
worked great. thank you.
zackdjones said:
I can't really take credit for this, but I just restored my IMEI without a backup of the efs folder. Keep in mind that I actually deleted my efs folder by accident, so I didn't even have the original efs folder.
The original thread I referenced is here:
http://forum.xda-developers.com/showthread.php?p=31771228#post31771228
FYI, this method will restore your phone to stock Gingerbread.
Here is what you do:
1.)
A) Download and unzip the Gingerbread unbrick package here from (http://forum.xda-developers.com/showthread.php?p=27286083#post27286083):
w/ root - http://d-h.st/ewu
w/o root - http://d-h.st/G6g
B)
Download and unzip the efs zip here:
http://forum.xda-developers.com/attachment.php?attachmentid=1152914&d=1340558510
2.) Place phone in download mode.
3.) If needed, install latest Samsung USB drivers by installing Samsung Kies from HERE.
4.) Open the included Odin exe.
5.) If phone is detected, the window under ID:COM will turn yellow.
6.) Click on "PIT" to browse to and select infuse_gb.pit. Make sure that Re-Partition is selected.
7.) Click on "PDA" to browse to and select PDA_UCLB3.tar.md5.
8.) Click on "PHONE" to browse to and select PHONE_UCLB3.tar.md5.
9.) Click on "CSC" to browse to the efs.tar
10.) Click the Phone EFS Clear checkbox
11.) Click on "Start", and allow Odin to flash the phone. Do not unplug or power off the phone until Odin is finished.
12.) When the Odin dialogue reads "PASS!", the phone should reboot into the stock UCLB3 Setup Wizard. For me this step just proceeded to install an update and the reboot the phone.
Once the phone reboots, if your SIM card is installed you should be good to go, otherwise you will get an alert about your SIM card which means you need to power off and pop in the SIM card.
Thanks to the original thread author for this one.
Click to expand...
Click to collapse
1stly thanks a lot for this thread. Really millions of thanks.
Now one silly question:- I unzipped the efs file attached and it says "efs.rfs" but your instructions above says "efs.tar" needs to be selected under CSC option. Am I missing something?
Punnyabrata said:
1stly thanks a lot for this thread. Really millions of thanks.
Now one silly question:- I unzipped the efs file attached and it says "efs.rfs" but your instructions above says "efs.tar" needs to be selected under CSC option. Am I missing something?
Click to expand...
Click to collapse
Strange things are happening to me.
About 2 weeks back this problem started and today when I reconnected the SIM and restarted the phone everything was back to normal. Phone is picking up signal/3G etc.
Surprised is the word. Leads me to believe some app must be responsible for all of this.
Thanks,
PC
It is showing invalid mds sum...what I do?
At the end of the task odin shows blue screen and show fail.
Now my phone doesnt get start..what I do?
sachinppatel16 said:
At the end of the task odin shows blue screen and show fail.
Now my phone doesnt get start..what I do?
Click to expand...
Click to collapse
Have you tried Odin as administrator ? that's might be the problem
Solved: stuck at "Firmware upgrade encountered an issue. Please select recovery mode
So you are stuck on the dreaded " Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" screen and there is nothing you can do to get your phone to start normally or even get to the download screen?
Fret not lads & ladies, I've already gone thru the pain and suffering and have come out new man, and I'll tell you how I did it. Also im starting all the way at linux/mac so everyones included.
First things first, you are going to have to get your computer ready with the right software for it to work.
You will need to make sure you get an original stock rom, make sure your source forwhere you download it is credible, this was my first mistake and why evidently I got myself into this mess.
I'm sure other roms might work that are modified for your device, but I suggest stock, and starting fresh just to make sure everything is up and running.
I am not responsible for your device, it may get bricked if done wrong.
Linux & Mac users first.
1. You will need to downloadable a program called Hiemdall, its a program similar to Odin3 (windows program).
2. You will need to extract the stock rom you downloaded earlier, I suggest to a folder in your desktop, wd will call it "folder1".
3. Now open up Hiemdall in root, (sudo Hiemdall-frontend for terminal) and then make sure device is on and stuck on the " Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" screen, plug it in, then press the utilities tab and detect. ($ Heimdall detect)(terminal users). Make sure you do all this fast because the tablets are kinda funny when they stay connected.
4. Now clickthe Utilities tab then the "save as..." button and save the destination for the .pit file in the same location as the extracted stock rom folder (folder1).
5. Next click the Flash tab, and click browse and locate your .pit file, the one you just downloaded. Next click add under Partition (files), and then change the partion name (On the left hand under patition details) to recovery and browse to the extracted folder (folder1) and click and add the recovery.img and press start.
Now if all went well your tablet will have restarted itself and you have seen the logo (Samsung). but the chances are it wont load past that screen, but thats ok because now you can get your device into download mode and re-flash the whole rom. Do this the same way you did the recovery.img, but make sure you add each new one to the correct name in the partitions details section.
Now if this didnt work, then dont worry you can still join the windows crew and do it hat way. Simple download a program called virtualbox and get a windows xp iso, thats up to you to figure out as I deal with open source only O.S
So aftr you do that just load up the virtualbox with windows xp and follow below. I found it a bit easier as well.
Windows users....
I found this way to be pretty simple and straight forward,
1. Download Odin 1.3 (1.85 wasn't working for me)
2. Download the clockworkrecoveryMod
3. Open up Odin and browse in the PDA section for the CWM you downloaded and add it, next plug in your device and the box should turn yellow on the top left.
4. Press start and let it finish and reboot your device and you should now be able to boot into CWM and re flash a rom, or if you were smart just restore from a previous backup and get all the apps and stuff back too.
I dont know why cwm worked but it did so no complaints, just make sure you go into cwm and backup your device and with titanium (google play app) before you start playing with the root.
I did this and it worked for me, so hopefully it did for you. Im sorry if it didnt but dont get down, j6st be patient and ask and someone will help.
The key is getting the recovery.img to flash on I believe and maybe the cwm has it built in the package, im sure someone can shed some light on it.
"Im tired, cranky and hungry, but I got my baby back, no not you hunny, my GT2...":beer:
JLloydMedia said:
So you are stuck on the dreaded " Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" screen and there is nothing you can do to get your phone to start normally or even get to the download screen?
Fret not lads & ladies, I've already gone thru the pain and suffering and have come out new man, and I'll tell you how I did it. Also im starting all the way at linux/mac so everyones included.
First things first, you are going to have to get your computer ready with the right software for it to work.
You will need to make sure you get an original stock rom, make sure your source forwhere you download it is credible, this was my first mistake and why evidently I got myself into this mess.
I'm sure other roms might work that are modified for your device, but I suggest stock, and starting fresh just to make sure everything is up and running.
I am not responsible for your device, it may get bricked if done wrong.
Linux & Mac users first.
1. You will need to downloadable a program called Hiemdall, its a program similar to Odin3 (windows program).
2. You will need to extract the stock rom you downloaded earlier, I suggest to a folder in your desktop, wd will call it "folder1".
3. Now open up Hiemdall in root, (sudo Hiemdall-frontend for terminal) and then make sure device is on and stuck on the " Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" screen, plug it in, then press the utilities tab and detect. ($ Heimdall detect)(terminal users). Make sure you do all this fast because the tablets are kinda funny when they stay connected.
4. Now clickthe Utilities tab then the "save as..." button and save the destination for the .pit file in the same location as the extracted stock rom folder (folder1).
5. Next click the Flash tab, and click browse and locate your .pit file, the one you just downloaded. Next click add under Partition (files), and then change the partion name (On the left hand under patition details) to recovery and browse to the extracted folder (folder1) and click and add the recovery.img and press start.
Now if all went well your tablet will have restarted itself and you have seen the logo (Samsung). but the chances are it wont load past that screen, but thats ok because now you can get your device into download mode and re-flash the whole rom. Do this the same way you did the recovery.img, but make sure you add each new one to the correct name in the partitions details section.
Now if this didnt work, then dont worry you can still join the windows crew and do it hat way. Simple download a program called virtualbox and get a windows xp iso, thats up to you to figure out as I deal with open source only O.S
So aftr you do that just load up the virtualbox with windows xp and follow below. I found it a bit easier as well.
Windows users....
I found this way to be pretty simple and straight forward,
1. Download Odin 1.3 (1.85 wasn't working for me)
2. Download the clockworkrecoveryMod
3. Open up Odin and browse in the PDA section for the CWM you downloaded and add it, next plug in your device and the box should turn yellow on the top left.
4. Press start and let it finish and reboot your device and you should now be able to boot into CWM and re flash a rom, or if you were smart just restore from a previous backup and get all the apps and stuff back too.
I dont know why cwm worked but it did so no complaints, just make sure you go into cwm and backup your device and with titanium (google play app) before you start playing with the root.
I did this and it worked for me, so hopefully it did for you. Im sorry if it didnt but dont get down, j6st be patient and ask and someone will help.
The key is getting the recovery.img to flash on I believe and maybe the cwm has it built in the package, im sure someone can shed some light on it.
"Im tired, cranky and hungry, but I got my baby back, no not you hunny, my GT2...":beer:
Click to expand...
Click to collapse
Hi. Tried your method and it worked on windows. I tried 2 different ODIN softwares before it worked. Thanks for your help and information.
can't enter download mode
thanks for the notes. i tried to update to 4.2.2 from 4.1.2. the upgrade was unsucessfull. now i did whatever u have told. now i got the recovery but i can't enter download mode. now the tab 2(p3100) is just restarting. please help me as soon as possible
JLloydMedia said:
So you are stuck on the dreaded " Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" screen and there is nothing you can do to get your phone to start normally or even get to the download screen?
Fret not lads & ladies, I've already gone thru the pain and suffering and have come out new man, and I'll tell you how I did it. Also im starting all the way at linux/mac so everyones included.
First things first, you are going to have to get your computer ready with the right software for it to work.
You will need to make sure you get an original stock rom, make sure your source forwhere you download it is credible, this was my first mistake and why evidently I got myself into this mess.
I'm sure other roms might work that are modified for your device, but I suggest stock, and starting fresh just to make sure everything is up and running.
I am not responsible for your device, it may get bricked if done wrong.
Linux & Mac users first.
1. You will need to downloadable a program called Hiemdall, its a program similar to Odin3 (windows program).
2. You will need to extract the stock rom you downloaded earlier, I suggest to a folder in your desktop, wd will call it "folder1".
3. Now open up Hiemdall in root, (sudo Hiemdall-frontend for terminal) and then make sure device is on and stuck on the " Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" screen, plug it in, then press the utilities tab and detect. ($ Heimdall detect)(terminal users). Make sure you do all this fast because the tablets are kinda funny when they stay connected.
4. Now clickthe Utilities tab then the "save as..." button and save the destination for the .pit file in the same location as the extracted stock rom folder (folder1).
5. Next click the Flash tab, and click browse and locate your .pit file, the one you just downloaded. Next click add under Partition (files), and then change the partion name (On the left hand under patition details) to recovery and browse to the extracted folder (folder1) and click and add the recovery.img and press start.
Now if all went well your tablet will have restarted itself and you have seen the logo (Samsung). but the chances are it wont load past that screen, but thats ok because now you can get your device into download mode and re-flash the whole rom. Do this the same way you did the recovery.img, but make sure you add each new one to the correct name in the partitions details section.
Now if this didnt work, then dont worry you can still join the windows crew and do it hat way. Simple download a program called virtualbox and get a windows xp iso, thats up to you to figure out as I deal with open source only O.S
So aftr you do that just load up the virtualbox with windows xp and follow below. I found it a bit easier as well.
Windows users....
I found this way to be pretty simple and straight forward,
1. Download Odin 1.3 (1.85 wasn't working for me)
2. Download the clockworkrecoveryMod
3. Open up Odin and browse in the PDA section for the CWM you downloaded and add it, next plug in your device and the box should turn yellow on the top left.
4. Press start and let it finish and reboot your device and you should now be able to boot into CWM and re flash a rom, or if you were smart just restore from a previous backup and get all the apps and stuff back too.
I dont know why cwm worked but it did so no complaints, just make sure you go into cwm and backup your device and with titanium (google play app) before you start playing with the root.
I did this and it worked for me, so hopefully it did for you. Im sorry if it didnt but dont get down, j6st be patient and ask and someone will help.
The key is getting the recovery.img to flash on I believe and maybe the cwm has it built in the package, im sure someone can shed some light on it.
"Im tired, cranky and hungry, but I got my baby back, no not you hunny, my GT2...":beer:
Click to expand...
Click to collapse
pls help..
I m faceting same problem on my galaxy tab 2 7.1 gtp3100..but my tab is not detecting by odin ..n tell me is
kies are necessary or not? pls help me..
shubham.butle said:
I m faceting same problem on my galaxy tab 2 7.1 gtp3100..but my tab is not detecting by odin ..n tell me is
kies are necessary or not? pls help me..
Click to expand...
Click to collapse
kies is not nesccearlly needed we need the usb drivers make sure you installed them and you are using stock samsung usb cable or else IT WON"T WORK !!!
shubham.butle said:
I m faceting same problem on my galaxy tab 2 7.1 gtp3100..but my tab is not detecting by odin ..n tell me is
kies are necessary or not? pls help me..
Click to expand...
Click to collapse
If you can reach to the CWM recovery mode: Download firmware in zip form, you can get it from the below link. if you have a zip file leave it.
After obtaining the firmware copy to your external sdcard using a card reader or any other method
In recovery mode select "Instal zip from sdcard" then select "choose zip from external sdcard" then select the copied firmware zip file from the list and wait for completion
After completion go back and select "wipe data/factory reset" and "wipe cache partition" reboot . it will take some time for reboot atleat 15min. it worked for me. hope it will work for you. good luck
http://forum.xda-developers.com/showthread.php?t=2054901
Thanx...
thanx.. @Jeevan I flashed cwm successfully..(I don't know how..!)n in ur link there are many roms ,when this problem was created my os was ICS..now tell me if I flash 4.2.2 directly..then it will create problem or not..n in 4.2.2 there are two files so which will better..thanx once again u saved me!!pls reply
shubham.butle said:
thanx.. @Jeevan I flashed cwm successfully..(I don't know how..!)n in ur link there are many roms ,when this problem was created my os was ICS..now tell me if I flash 4.2.2 directly..then it will create problem or not..n in 4.2.2 there are two files so which will better..thanx once again u saved me!!pls reply
Click to expand...
Click to collapse
You can choose any of the roms, deodexed will be better. And there won't be any problem flashing 4.2.2
You should install latest kies version
Sent from my GT-P3100 using xda premium
sukkukikku said:
You should install latest kies version
Sent from my GT-P3100 using xda premium
Click to expand...
Click to collapse
Thanx yr..bt today I just install stock rom 4.2.2,so no problem just tell me these stock roms are exactly original or change some thing I mean in future updates can I use normal method ie directly
update from tab?
---------- Post added at 02:05 AM ---------- Previous post was at 02:01 AM ----------
shubham.butle said:
Thanx yr..bt today I just install stock rom 4.2.2,so no problem just tell me these stock roms are exactly original or change some thing I mean in future updates can I use normal method ie directly
update from tab?
Click to expand...
Click to collapse
I update rom by cwm..
would you like to give me clear solution? i have same problem here with P3100, already tried many CWM but none of them fixed it, flashing directly through odin with this file (DBT-P3100XWDMI1-20140113101559) and still no luck. Any link to download correct CWM please... Thanks
Awesome post
Dears
please follow blindly in this post,
because i have tried to install , 4.2.2 Bg to my samsung tab 2, got error firmware upgrade issue, and now i followed the steps here. got installed on 4..2.2
who would required , please go for XDA instruction
realy awesome, life saver, :good:
ragujay said:
Dears
please follow blindly in this post,
because i have tried to install , 4.2.2 Bg to my samsung tab 2, got error firmware upgrade issue, and now i followed the steps here. got installed on 4..2.2
who would required , please go for XDA instruction
realy awesome, life saver, :good:
Click to expand...
Click to collapse
Hi! Do you still having the CWM and Odin 1.3?
Hi.. I was experiencing this problem. Then without even thinking deeply, I try google any solution regarding this matter without referring to this thread first. I found this guys solution as he said it is for all samsung model.
https://www.youtube.com/watch?v=Jfgq6bYfKLg
After done flashing, my tab giving a samsung logo and went off until now. I was unable to enter the recovery and download mode. I try to connect the tab with PC but it kept reconnecting repetitively although universal samsung usb driver has been installed. Any idea how to solve this?
I managed to pull some files together including the .pit file from my now working tablet and make a fully working 4 file firmware and combo (all in one) firmware that CAN be flashed with Odin. I have tested it on my device and it does work. Since I know people are searching EVERYWHERE for this, I have released a download link for these files below.
Please, feel free to re-post this anywhere, just be sure to credit me.
DISCLAIMER (Obviously): I WILL NOT BE HELD RESPONSIBLE FOR ANY DAMAGE DONE TO YOUR DEVICE AFTER FLASHING. KEEP IN MIND THAT ANYTHING CAN GO WRONG, EVEN IF YOU'RE FLASHING FIRMWARE THAT IS MADE FOR YOUR DEVICE. THE FIRMWARE AVAILABLE BELOW HAS NOT BEEN MODIFIED, ENGINEERED, OR EDITED IN ANY WAY TO CHANGE THE FUNCTIONALITY OF YOUR DEVICE. IF YOUR DEVICE BRICKS AFTER FLASHING, IT'S ALL ON YOU.
Flashing instructions:
But first, the requirements:
1) SM-T337A, Obviously, but seriously, I can't stress how important it is that you check that your model number is matched with the model number in this thread before flashing anything.
2) A Windows pc (NOT A VIRTUAL MACHINE! Using a VM to flash your device has a high chance to hard-brick your tab, and make sure your computer is running Windows XP or newer.)
3) Your device's USB transfer/charging cable
4) A Brain (Obviously)
Now then, the actual steps (4 File Firmware):
1) Boot your tab into download mode (Shut the device down completely, then hold down the power, volume down, and home button at the same time until a warning message appears)
2) Download and open Odin on your pc
3) Grab the USB charging cable and plug your tab into your pc
4) If Odin does not show your device in the list (It will display an "Added" message if the device is detected) download the Samsung USB Drivers for Mobile Phones and install it to your pc. You may need to/and it is recommended to restart your computer after installing the drivers.
5) Extract the zip file you downloaded containing the firmware to your desktop or a memorable place on your computer.
6) If you wish to wipe your data and start from scratch, click on the 'PIT' tab and select the .pit file in the extracted folder. Then, click the 'OPTIONS' tab and select 'Re-Partition' and 'NAND Erase All'.
7) Insert the firmware files into Odin. Within Odin, for instance, Click on the 'BL' button, which is where the bootloader file goes. Select the extracted package that has 'BL' at the beginning, and vice versa.
Example:
BL: *directory*/BL_T337AUCU2BOH4...
AP: *directory*/AP_T337AUCU2BOH4...
CP: *directory*/CP_T337AUCU2BOH4...
CSC: *directory*/CSC_ ATT_T337AUCU2BOH4...
8) Once done, verify that you have correctly done all the steps above, click 'Start' in Odin and wait for Odin to output a "PASS" message before unplugging anything.
9) If you wish to flash the firmware, but keep your data, make sure that there is no .pit file in Odin, make sure that 'Re-Partition' and 'NAND Erase All' are unchecked, and make sure that there is no file inserted under the 'CSC' row.
Tutorial (Combo Firmware)
1) Boot your tab into download mode (Shut the device down completely, then hold down the power, volume down, and home button at the same time until a warning message appears)
2) Download and open Odin on your pc
3) Grab the USB charging cable and plug your tab into your pc
4) If Odin does not show your device in the list (It will display an "Added" message if the device is detected) download the Samsung USB Drivers for Mobile Phones and install it to your pc. You may need to/and it is recommended to restart your computer after installing the drivers.
5) Extract the zip file you downloaded containing the firmware to your desktop or a memorable place on your computer.
6) Within Odin, Select 'AP' and browse to the directory where you extracted the firmware, and select the .tar package in the directory. There should be nothing else under the other tabs, only 'AP' should have a firmware package in it.
7) Flashing this package (unless you perform the "Developers Tip" at the end of this thread) will wipe all of your data, so be sure that the proper .pit file that came with the firmware package is selected under the 'PIT' tab in Odin and make sure that 'Re-Partition' and 'NAND Erase All' are checked in Odin to ensure a complete wipe of all personal data on the device. If you perform the developers tip at the end of the thread, simply insert the new package you created under 'AP', make sure there is no .pit file under the PIT slot, and make sure that 'Re-Partition' and 'NAND Erase All' are unchecked in Odin.
8) Once done, verify that everything is set and ready-to-go, then click 'Start' and wait for Odin to output a "PASS" message before unplugging anything.
9) Enjoy!
WARNING: If you are seeing sites that charge you money for the files, DO NOT BUY IT. They are scams and I HIGHLY SUGGEST AVOIDING THESE SITES. I didn't have to buy anything. If you do buy the firmware from these scam sites, and your device becomes bricked or messed up in some way, don't say I didn't warn you.
4 File Firmware Download: https://mega.nz/#!n8Q3VIIS!OComhygeI5SL5R6n0EXEfiYMBtVn_aOAIcUuLgmYs-k
Combo Firmware Download: https://mega.nz/#!69oEwbBR!vBtHQnrdwAfdZB3iPeGb99Yp7W79efTQr7t6FZXrzIo
Odin 3.12 Download: https://mega.nz/#!KsZiHKTb!aEHdQgO7JAQeUwdJWqS0xoR3lyJH4ieJ6qTbVKce8Zk
If the link doesn't work or goes down for some reason or if you were confused by my instructions in any way, please let me know.
Developers Tip: If you want to flash firmware without wiping your data, make sure there is no pit file selected under the PIT tab in Odin, then extract your firmware package (extract everything into a separate folder for combo firmware, extract the CSC package for 4 file downloads) and remove cache.img.ext4 then repack as a .tar file. Applies to both combo and 4 file firmware packages. In 4 file packages, cache.img.ext4 is in the CSC file. However, in some cases this may put your device in a bootloop. If you wish to do this on an older device and the cache file doesn't have the .ext4 extension at the end, don't worry, it'll work the same way.
Now that you have the firmware, WHY NOT ROOT IT? Check out my thread on how to do so here: https://forum.xda-developers.com/tab-4/general/root-how-to-root-sm-t337a-supersu-t3553848
Cheers!
Does anyone know the process for extracting the files like this from an OTA update? I have some files I would like to extract from another OTA. Thank you
Sent from my SAMSUNG-SM-N910A using XDA-Developers Legacy app
dkmac said:
Does anyone know the process for extracting the files like this from an OTA update? I have some files I would like to extract from another OTA. Thank you
Sent from my SAMSUNG-SM-N910A using XDA-Developers Legacy app
Click to expand...
Click to collapse
I'll be honest and say its not easy. Making this firmware took me about 3 months. OTA update files are very different from actual Odin firmware files. If you want to extract the files from an OTA update, I just used 7Zip and went from there.
Lollipop 5.1.1 Root for SM-T337A
@KingOfTheNet - Great stuff. There are definitely some shady sites out there offering firmware for the T337A so thank you.
Not to be greedy but any recommendations on rooting 5.1.1 on SM-T337A. I am trying to remove all of the Samsung and AT&T bloatware and get my Tab 4 running lean and mean. I am pretty sure I went with your firmware - my build number is listed as LMY47X.T337AUC2BOH4.
Appreciate the support.
18Echo said:
@KingOfTheNet - Great stuff. There are definitely some shady sites out there offering firmware for the T337A so thank you.
Not to be greedy but any recommendations on rooting 5.1.1 on SM-T337A. I am trying to remove all of the Samsung and AT&T bloatware and get my Tab 4 running lean and mean. I am pretty sure I went with your firmware - my build number is listed as LMY47X.T337AUC2BOH4.
Appreciate the support.
Click to expand...
Click to collapse
Your welcome bro, happy to help! I have actually rooted my tab with SuperSU, fully working. The only thing is its temporary, and I avoid rebooting or shutting the device down at all because it's a system-less SuperSU (meaning temporary). I'll make a thread on how to achieve root on this tab later tomorrow when I get home from work, unless someone replies to this before I do (It's late where I'm at).
Cheers!
18Echo said:
@KingOfTheNet - Great stuff. There are definitely some shady sites out there offering firmware for the T337A so thank you.
Not to be greedy but any recommendations on rooting 5.1.1 on SM-T337A. I am trying to remove all of the Samsung and AT&T bloatware and get my Tab 4 running lean and mean. I am pretty sure I went with your firmware - my build number is listed as LMY47X.T337AUC2BOH4.
Appreciate the support.
Click to expand...
Click to collapse
Just made a thread for it here: https://forum.xda-developers.com/tab-4/general/root-how-to-root-sm-t337a-supersu-t3553848
Cheers!
Hello! ... First of all, thank you for all your hard work! But unfortunately that firmware does not seem to work for me. I'm a little newbie, so I'd appreciate if someone could explain the steps to follow specifically with Odin, as a tutorial or something ... so that I can distinguish what I'm doing wrong.
I uploaded a short video so you can see what I mean... If you could take the time to watch it and tell me what I'm doing wrong, that would be awesome.
Here it is: youtu.be/9JsLVJ-xHMA (I cannot post direct link since I'm new user)
I've downloaded some files with name ATT_T337AUCU2BOH4_T337AATT2BOH4.zip (1.19gb) put by poorusernamebychoice and their tar.md5 file is gone 404.
Now i need some help here, this zip contains:
AP_T337AUCU2BOH4_T337AATT2BOH4_HOME.tar
BL_T337AUCU2BOH4_T337AATT2BOH4_HOME.tar
CP_T337AUCU2BOH4_T337AATT2BOH4_HOME.tar
CSC_T337AUCU2BOH4_T337AATT2BOH4_HOME.tar
MILLETLTE_USA_ATT.pit
This is big file so now I'm stuck what to do or i start a fresh download from above links.
Sent from my SAMSUNG-SM-T337A using Tapatalk
darkcrazy75 said:
Hello! ... First of all, thank you for all your hard work! But unfortunately that firmware does not seem to work for me. I'm a little newbie, so I'd appreciate if someone could explain the steps to follow specifically with Odin, as a tutorial or something ... so that I can distinguish what I'm doing wrong.
I uploaded a short video so you can see what I mean... If you could take the time to watch it and tell me what I'm doing wrong, that would be awesome.
Here it is: youtu.be/9JsLVJ-xHMA (I cannot post direct link since I'm new user)
Click to expand...
Click to collapse
Sorry for the late responce, my internet has been down for a while now (2 weeks). I'll watch the video later today and edit this post with an explainatio n.
_SAM11_ said:
I've downloaded some files with name ATT_T337AUCU2BOH4_T337AATT2BOH4.zip (1.19gb) put by poorusernamebychoice and their tar.md5 file is gone 404.
Now i need some help here, this zip contains:
AP_T337AUCU2BOH4_T337AATT2BOH4_HOME.tar
BL_T337AUCU2BOH4_T337AATT2BOH4_HOME.tar
CP_T337AUCU2BOH4_T337AATT2BOH4_HOME.tar
CSC_T337AUCU2BOH4_T337AATT2BOH4_HOME.tar
MILLETLTE_USA_ATT.pit
This is big file so now I'm stuck what to do or i start a fresh download from above links.
Click to expand...
Click to collapse
Do you mean you need to re-download the files or you need help with flashing them? Dl links are at the middle of the thread.
KingOfTheNet said:
Do you mean you need to re-download the files or you need help with flashing them? Dl links are at the middle of the thread.
Click to expand...
Click to collapse
I hve these files i wrote above. So if they're working, i just need procedure
Sent from my SAMSUNG-SM-T337A using Tapatalk
_SAM11_ said:
I hve these files i wrote above. So if they're working, i just need procedure
Sent from my SAMSUNG-SM-T337A using Tapatalk
Click to expand...
Click to collapse
It's actually very easy, that's why I didn't put any instructions in the thread, I just assumed people knew how to do it by now. But I'm happy to provide instructions to those people who don't know how. Instead of posting said instructions right here, I'll update the thread with instructions.
Cheers!
KingOfTheNet said:
It's actually very easy, that's why I didn't put any instructions in the thread, I just assumed people knew how to do it by now. But I'm happy to provide instructions to those people who don't know how. Instead of posting said instructions right here, I'll update the thread with instructions.
Cheers!
Click to expand...
Click to collapse
That means alot after my last reply, i had been trying to flash with odin but i dnt kno why tablet isn't connecting laptop while other phones are. Not evn on media mode. So I'm downloading ota update.zip
Sent from my SAMSUNG-SM-T337A using Tapatalk
_SAM11_ said:
That means alot after my last reply, i had been trying to flash with odin but i dnt kno why tablet isn't connecting laptop while other phones are. Not evn on media mode. So I'm downloading ota update.zip
Sent from my SAMSUNG-SM-T337A using Tapatalk
Click to expand...
Click to collapse
This might take me a while, I can't edit the thread (kinda odd). I've gotta talk to admin about it but I'll try to get instructions up for ya asap (unless someone replies to you with instructions before I do).
Update: I managed updating to 5.1.1 update. Now i just need January update and root the device. I just need January zip update ota if u can manage me getting that please
Sent from my SAMSUNG-SM-T337A using Tapatalk
_SAM11_ said:
Update: I managed updating to 5.1.1 update. Now i just need January update and root the device. I just need January zip update ota if u can manage me getting that please
Sent from my SAMSUNG-SM-T337A using Tapatalk
Click to expand...
Click to collapse
I believe I have the file stored somewhere on my hard drive, I'll look and pm you a link if I can find it.
Cheers!
KingOfTheNet said:
I believe I have the file stored somewhere on my hard drive, I'll look and pm you a link if I can find it.
Cheers!
Click to expand...
Click to collapse
Sure Thanks for much help
Sent from my SAMSUNG-SM-T337A using Tapatalk
Guys no lollipop update for tab4 t230 ?
tab4map4 said:
Guys no lollipop update for tab4 t230 ?
Click to expand...
Click to collapse
No, this thread is for the Tab 4 8.0 AT&T. Please make sure you consult the relevant forums for your device model as doing anything meant to be done on different devices can be catastrophic.
Cheers!
_SAM11_ said:
Sure Thanks for much help
Sent from my SAMSUNG-SM-T337A using Tapatalk
Click to expand...
Click to collapse
Finally got the instructions up. You can check the very beginning of the thread for instructions on flashing. Just remember, I will not be held responsible if your device is bricked after the matter.
Cheers!