Hello xda,
I tried rooting my SGH-T999 and it took a while so I unplugged the USB and restarted the phone. Phone keeps saying it has encountered a problem with the current firmware, connect to KIES and select recovery. Kies does not connect to the device. I read on xda to reflash using ODIN. I have ODIN v1.85 from trying to root, is this the right version to use because I also found the ODIN3_v3.07? As far as USB driver, is there separate drivers for ODIN or are people referring to the Samsung Kies drivers (I just installed KIES). I read to do it on this screen and I also read to try to go into the recovery mode (holding vol down, home, power) and then reflashing; which should I do?
Also, I found this link on xda for the T-mobile firmware ( http://forum.xda-developers.com/showthread.php?t=1949687 ). No idea which one to choose, why are there so many, I am currently downloading the latest one
"UVDLJA
PDA: T999UVDLJA
CSC: T999TMBDLJA
Version: 4.1.1 JB
Date: Nov. 14, 2012
Sammobile Link
Samsung-Updates Link"
If I want to use the pre rooted file do I need to fix my problem first and try flashing with stock firmware or can I try to fix the issue directly with the pre rooted firmware?
Re: [Q] SGH-T999 Rooted bad, phone stuck on start screen
Use the Odin from my signature.
You can probably just flash mrRobinson's stock rooted rom to fix it. And Kies is garbage. Uninstall it.
I would like to see the root guide you used as well.
Aerowinder said:
Use the Odin from my signature.
You can probably just flash mrRobinson's stock rooted rom to fix it. And Kies is garbage. Uninstall it.
I would like to see the root guide you used as well.
Click to expand...
Click to collapse
I used this guide to root.
http://galaxys3root.com/galaxy-s3-r...gh-t999sgh-i747sph-l710-fail-proofnoob-proof/
Before I try to flash with mrRobinson's stock rooted rom which I just finished downloading, I will uninstall Kies and install the USB drivers first?
Thanks for your response Aerowinder.
I got USB drivers earlier today that was a newer version but I will be using the files from your sig since it works :good:
Another question I had was, does the phone need to be in download mode or can I do it in the screen where it says "encountered problem with current firmware. Connect to KIES and select recovery" screen when I flash with Odin? I know normally I would have to be in the download mode but I'm wondering if it is the same when I am getting this error.
Re: [Q] SGH-T999 Rooted bad, phone stuck on start screen
Phone must be in download mode to use Odin.
The drivers in my signature are not the newest, you are correct. They are the last version I found that work without any issues. The newer ones pretty much suck. Constant disconnects mainly.
Aerowinder said:
Phone must be in download mode to use Odin.
The drivers in my signature are not the newest, you are correct. They are the last version I found that work without any issues. The newer ones pretty much suck. Constant disconnects mainly.
Click to expand...
Click to collapse
Awesome thanks!
So I am watching the root video on your sig, so in my case I would choose the rom I want for the PDA instead of the cwm-touch-6.0.2.3-d2tmo right? Should I extract the rooted firmware or just load the zipped file onto ODIN PDA?
Re: [Q] SGH-T999 Rooted bad, phone stuck on start screen
Root66 does not contain a recovery so you still need to flash one of those but don't use my link. Get ROM Manager once you're up and running.
If you don't care about the flash counter you can flash the tar in my signature.
Sorry to interject here but you can get an Odin flashable recovery from here.
You can flash one of these and then flash Root66 right after and you'll have stock Rooted ROM with stock or custom recovery (your choice).
Not to be a buzzkill or anything but you are probably the 5th or 6th person in the past 2 weeks that have encountered the "encountered problem with current firmware. Connect to KIES and select recovery" error. Only a few of them have been able to pull out of it. The ones that have, have had to flash Root66 (or their device respective FW) multiple times.
I hope that you can get out of it and please post here if you do. Aerowinder knows what he is doing. Follow his lead.
Aerowinder said:
Root66 does not contain a recovery so you still need to flash one of those but don't use my link. Get ROM Manager once you're up and running.
If you don't care about the flash counter you can flash the tar in my signature.
Click to expand...
Click to collapse
Okay I don't care about the counter, I just want my phone to work and I'll be happy.
But now I'm getting a little confused about the cwm recovery.
So just to be clear, you are saying I need to flash a recovery (cwm-touch-6.0.2.3-d2tmo in my case since I don't care about the counter), BUT do I flash the recovery before or after I flash with Root66 firmware? That part I am confused about. And do I flash one right after another or do I need to restart my phone or ODIN first?
Thank you so much for helping me out. I was freaking out this morning and I am very grateful for your help and knowledge. I hope I am not being too much of a pain or hassle with these questions. Sorry that I am quite new to this
Woody said:
Sorry to interject here but you can get an Odin flashable recovery from here.
You can flash one of these and then flash Root66 right after and you'll have stock Rooted ROM with stock or custom recovery (your choice).
Not to be a buzzkill or anything but you are probably the 5th or 6th person in the past 2 weeks that have encountered the "encountered problem with current firmware. Connect to KIES and select recovery" error. Only a few of them have been able to pull out of it. The ones that have, have had to flash Root66 (or their device respective FW) multiple times.
I hope that you can get out of it and please post here if you do. Aerowinder knows what he is doing. Follow his lead.
Click to expand...
Click to collapse
Woody, I went to the link you posted. What are the 4 files for?
Don't use those - they are older versions.
If you don't care about the counter, then flash the CWM in my signature using Odin (can provide TWRP tar link if that's your thing), then flash root66 using Odin. You can reboot in between... but no real reason to do so.
If you are still having issues after you flash these, drop into recovery (vol up + home) and reset factory defaults. If still having problems, only thing left to do is flash a full stock image, link also in my signature. The page you linked to does not contain the newest version because DocHolliday hasn't been around here much lately.
buzzking00 said:
Woody, I went to the link you posted. What are the 4 files for?
Click to expand...
Click to collapse
Top one is TWRP version 2.3.0.0
Second is 6.0.1.2 CWR touch version
Third is TWRP version 2.3.1.0
Fourth is Stock recovery.
Do not flash all of them. Are you a TWRP or CWR kind of person? Instead of re-typing it out, go here and I come in on post #20 on the 2nd page. Read that to the end and let us know if you understand it. Pretty easy to follow but I understand your Panic Mode, so take your time.
Aerowinder said:
If still having problems, only thing left to do is flash a full stock image, link also in my signature.
Click to expand...
Click to collapse
^^ This is what I see in his future.
Like I said above, I haven't seen too many people get out of that "Encountered..." error without some real technical expertise.
Aerowinder said:
Don't use those - they are older versions.
If you don't care about the counter, then flash the CWM in my signature using Odin (can provide TWRP tar link if that's your thing), then flash root66 using Odin. You can reboot in between... but no real reason to do so.
If you are still having issues after you flash these, drop into recovery (vol up + home) and reset factory defaults. If still having problems, only thing left to do is flash a full stock image, link also in my signature. The page you linked to does not contain the newest version because DocHolliday hasn't been around here much lately.
Click to expand...
Click to collapse
Awesome. Thanks Aerowinder!
I will try this when I get home (assuming I can go into download mode...) and post what happened
Woody said:
^^ This is what I see in his future.
Like I said above, I haven't seen too many people get out of that "Encountered..." error without some real technical expertise.
Click to expand...
Click to collapse
I will take a look at the link Woody.
I am really hoping this will work on the first try!
Okay so from reading your post Woody I can use EITHER the TWRP and CWR, but I want to use the one that is easiest to use. Which one do you guys think is easier to use?
Also, SU3.3 or SU1.04 which one should I use? Aerowinder, your sig shows both now but earlier I didn't notice the SU1.04. I just realized I only need the SU file IF the prerooted file doesn't work but just in case it doesn't I guess it is better to know.
Draw straws. I use CWM/Superuser. I use Superuser because CM comes with it. AOKP comes with SuperSU... both work fine. Just make sure you use the ones from my signature, as they are newer versions. You won't need su if you get a prerooted rom, only for stock.
Aerowinder said:
Draw straws. I use CWM/Superuser. I use Superuser because CM comes with it. AOKP comes with SuperSU... both work fine. Just make sure you use the ones from my signature, as they are newer versions. You won't need su if you get a prerooted rom, only for stock.
Click to expand...
Click to collapse
I am going to try it in an hour.
Wish me luck!
1. Download mode
2. Flash CWM
3. Flash Root66
4. Hopefully no problems
:good:
Aerowinder said:
Don't use those - they are older versions.
If you don't care about the counter, then flash the CWM in my signature using Odin (can provide TWRP tar link if that's your thing), then flash root66 using Odin. You can reboot in between... but no real reason to do so.
If you are still having issues after you flash these, drop into recovery (vol up + home) and reset factory defaults. If still having problems, only thing left to do is flash a full stock image, link also in my signature. The page you linked to does not contain the newest version because DocHolliday hasn't been around here much lately.
Click to expand...
Click to collapse
OMFG OMFG OMFG
OMFG OMFG OMFG
OOOOOOH MYYYYYY FOOOOOOOOKIN GOOOOOOOOOOOOSH
AEROWINDER AND WOODY
I LOVE YOU SO MUCH
IT WORKED AND NOTHING GOT ERASED. I THOUGHT PUTTING THE NEW FIRMWARE WOULD'VE ERASED EVERYTHING WITH THE NEW ROM BUT NOPE.
Uninstalled KIES and USB drivers.
Installed USB drivers from Aerowinders sig
So the Odin 3.07 didn't work either so I ended up using ODIN 1.85
Turned off auto reboot and left f reset on (no idea what f reset does lol)
Flashed CWM
Flashed root66 rom
Restarted phone and it was back to normal with all the data saved, but no SU (wasn't unlocked)
So reflashed CWM
Then restarted in clockwork recovery and ran super user and now the phone is rooted
Thanks for your helpful knowledge and now I am going to learn everything about android so I too can help another new android user in the (hopefully near) future.
:good::good::good: 3 thumbs up to the knowledge members above Aerowinder and Woody!
THANK YOU!
Panic mode TRANSFORMMMMM! *Panic mode has now transformed into excitement mode*
buzzking00 said:
Thanks for your helpful knowledge and now I am going to learn everything about android so I too can help another new android user in the (hopefully near) future.
Click to expand...
Click to collapse
So, ahh, are you excited? Haha. Great. Glad you got it up and running.
I hope that you do learn more about Android and share it with someone who needs help someday. When I first came, that is what someone did for me and I have tried to do it ever since. We are all still learning, including Aero and myself, so there will never be an end but rather more.
Good job and now you should make a Nandroid backup just in case you ever get in a bind again.
Well now I gotta learn how to make back-ups and what a Nandroid backup is lol.
Time to search the forums
buzzking00 said:
Well now I gotta learn how to make back-ups and what a Nandroid backup is lol.
Time to search the forums
Click to expand...
Click to collapse
That's the attitude, with Android you have to be a sponge and try to learn as much as you can. A single Google search will give you the answers you seek and making a backup is pretty much universal no matter what Rom, phone you have. Good luck
Sent from my SGH-T999 using xda app-developers app
Related
I need to return this phone back to Samsung to repair my broken USB. But I need to flash it back to unroot it and flash it back to stock.
I have no USB capabilities whatsoever.
I have tried Mobile ODIN but this phone model is not currently supported or it doesn't detect the model.
I have been reading for hours now and I have not found a definitive solution that works for this phone.
Does anyone have any advice?
Does anyone know where I can find this?
http://forum.xda-developers.com/showpost.php?p=19746620&postcount=35
He was linking to a flashable stock rom, kernel and recovery. The link is now gone... But this is what I need. something flashable since USB is gone.
Maybe someone knows how to make stock flashable? Or if anyone has a backup that is fully stock everything and is willing to help me out that would also be awesome.
Please please please please please!!! I need help!
MystikMajik said:
Does anyone know where I can find this?
http://forum.xda-developers.com/showpost.php?p=19746620&postcount=35
He was linking to a flashable stock rom, kernel and recovery. The link is now gone... But this is what I need. something flashable since USB is gone.
Maybe someone knows how to make stock flashable? Or if anyone has a backup that is fully stock everything and is willing to help me out that would also be awesome.
Please please please please please!!! I need help!
Click to expand...
Click to collapse
You can use FUS Downloader to get the odin flashable tars or use the links provided below. I recommend you use fus downloader if you can, as it has faster download speeds though.
http://www.hotfile.com/dl/159042353/c56b0ab/T989DTLLE4_T989DTLLE4_TLS.zip.html - Telus ICS
http://www.hotfile.com/dl/159504252/d690f93/T989UVLE1_T989TMBLE1_TMB.zip.html - T-Mobile ICS
http://fus.nanzen.se/ - Check Fus Downloader
namanjr said:
You can use FUS Downloader to get the odin flashable tars or use the links provided below. I recommend you use fus downloader if you can, as it has faster download speeds though.
http://www.hotfile.com/dl/159042353/c56b0ab/T989DTLLE4_T989DTLLE4_TLS.zip.html - Telus ICS
http://www.hotfile.com/dl/159504252/d690f93/T989UVLE1_T989TMBLE1_TMB.zip.html - T-Mobile ICS
http://fus.nanzen.se/ - Check Fus Downloader
Click to expand...
Click to collapse
Thanks for the response! I feel like I'm on my own here...
Is this flashable with CWM? I have no ODIN capabilities. No USB. And Mobile ODIN doesn't work for this phone...
MystikMajik said:
Thanks for the response! I feel like I'm on my own here...
Is this flashable with CWM? I have no ODIN capabilities. No USB. And Mobile ODIN doesn't work for this phone...
Click to expand...
Click to collapse
It's odin only, but i can convert it for CWM if you like. Did you buy it from Telus, Koodo, or T-Mobile?
namanjr said:
It's odin only, but i can convert it for CWM if you like. Did you buy it from Telus, Koodo, or T-Mobile?
Click to expand...
Click to collapse
Its Telus! If you can do that it would be awesome... I'm at my wits end... You'd be helping me a lot!
MystikMajik said:
Its Telus! If you can do that it would be awesome... I'm at my wits end... You'd be helping me a lot!
Click to expand...
Click to collapse
I should have it ready to download soon, I'm just adding the stock recovery and then i should be able to upload. I'll update this post when it's up and tested.
EDIT : It flashed me completely to stock without error, but it came out as 351MB so i need to find a new place to upload. Shouldn't be too much longer.
EDIT 2 : I have it uploading to Dev-Host now and should be up in about 30mins.
EDIT 3 : Uploaded here.
Well this has been quite the horrible week. I want to thank you for your work... Unfortunately it seems that I have lost root. In one of my previous attempts to go back to stock I flashed an unroot tmobile rom and it seems I'm now stuck with that and now unrooted. I'm guessing I'm screwed since there is no way to root without usb...
I want to shoot myself in the face...
Samsung is going to get a Telus S2 back with a Tmobile rom on it. There's no way they'll fix it now right?
Sent from my SGH-I897 using xda premium
MystikMajik said:
Well this has been quite the horrible week. I want to thank you for your work... Unfortunately it seems that I have lost root. In one of my previous attempts to go back to stock I flashed an unroot tmobile rom and it seems I'm now stuck with that and now unrooted. I'm guessing I'm screwed since there is no way to root without usb...
I want to shoot myself in the face...
Samsung is going to get a Telus S2 back with a Tmobile rom on it. There's no way they'll fix it now right?
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
It depends, do you still have a custom recovery? Also I know one-click root worked on Telus's Gingerbread rom so maybe a tool like that might work.
Well it's stock recovery now... And would one click work without usb?
Sent from my SGH-I897 using xda premium
have you tried to download su to see if maybe you just need to load that back up on your phone. If not there are programs like adbd Insecure adb wifi and goo manager that may somehow be able to get you back.
adbd Insecure - will allow you to push files over to your system even without root access
adb wifi - incase you need to send a recovery over to your sdcard and then use the proper commands to install
goo manager - has twrp 2.2.2.0 in it so if you install that program you flash their recovery through the app.
put the factory zip on your sdcard and hopefully voila!
Just some choices - hope one works and good luck
playya said:
have you tried to download su to see if maybe you just need to load that back up on your phone. If not there are programs like adbd Insecure adb wifi and goo manager that may somehow be able to get you back.
adbd Insecure - will allow you to push files over to your system even without root access
adb wifi - incase you need to send a recovery over to your sdcard and then use the proper commands to install
goo manager - has twrp 2.2.2.0 in it so if you install that program you flash their recovery through the app.
put the factory zip on your sdcard and hopefully voila!
Just some choices - hope one works and good luck
Click to expand...
Click to collapse
i just tried adbd on my own phone(since i never flashed back cm10 yet) and unfortunately when i start the app it asks for superuser.
Thanks for the replies! I'm gonna try goo manager right now...
But would something like this work?
http://forum.xda-developers.com/showthread.php?t=1501719
Update: Goo Manager isn't really doing anything unfortunately... It won't install anything I download. Seems simple enough so I'm sure I'm not doing anything wrong there...
Update #2: Yes. All of the above seem to need root, and since I don't have root...
Thank you playya for the sugesstions!
Thank you namanjr for doing that work... I wish I had waited longer to flash the rom I did!
I think its game over. I've been trying for a week and there's not a lot of options to flash stock, root/unroot if your USB is broken... which seems ridiculous to me but it is what it is...
namanjr said:
i just tried adbd on my own phone(since i never flashed back cm10 yet) and unfortunately when i start the app it asks for superuser.
Click to expand...
Click to collapse
My bad you do need root but damn goo won't let you flash recovery without root huh. Are you sure you can't put recovery image on sdcard and use adb wifi to send command to install recovery? Just thinking out loud
playya said:
My bad you do need root but damn goo won't let you flash recovery without root huh. Are you sure you can't put recovery image on sdcard and use adb wifi to send command to install recovery? Just thinking out loud
Click to expand...
Click to collapse
I don't think that will work, i used normal ADB to reinstall TWRP and it wouldn't flash until i used su.
What about this? http://www.xoomforums.com/forum/mot...a-update-zip-flash-through-recovery-wifi.html
Not our phone obviously... but with stock recovery shouldn't I be able to flash the official ota update? what is the stock recovery for?
EDIT: Sorry I'm just realizing the use of USB in that method... but still what is the stock recovery used for?
MystikMajik said:
What about this? http://www.xoomforums.com/forum/mot...a-update-zip-flash-through-recovery-wifi.html
Not our phone obviously... but with stock recovery shouldn't I be able to flash the official ota update? what is the stock recovery for?
EDIT: Sorry I'm just realizing the use of USB in that method... but still what is the stock recovery used for?
Click to expand...
Click to collapse
It can flashed OTA updates, signed zips/md5s, wipes cache partition, and factory restore. I tried the ODIN md5 file for stock and it never worked so unless someone cracks/or knows Samsungs signature i don't think it's much use. Also if you flash a rom for anything other then phones that are compatible with ours(I727, I717, etc), you will brick.
Hmmm... and I'm assuming there isn't somewhere you can download the official samsung OTA updates?
MystikMajik said:
Hmmm... and I'm assuming there isn't somewhere you can download the official samsung OTA updates?
Click to expand...
Click to collapse
I seen a link somewhere back when 2.3.6 came out for T-Mobile but it was only an incremental update and Telus doesn't have any OTA updates.
I've been reading these forums in my spare time for the last week or so but I'm still a bit confused or just overlooking something. According to the CM 10.1 thread install instructions are
Install instructions:
1. Install ClockworkMod Recovery for "I927". Sorry, CM cannot provide support for other recoveries, although they may work fine.
3. Reboot into recovery and install
Click to expand...
Click to collapse
and a few people in some of the guide threads have basically stated the same. Is it really this simple now or do I still need to follow the guide from a year ago or the one in this thread http://forum.xda-developers.com/showthread.php?t=1962633 ?
So far all I have done is install CWMR Touch 6.0.1.2 Recovery and run backup in both blob and tar formats. Actually does this even work properly without rooting first?
You don't need root, but you can't quite go straight either. The current SOP is:
Flash TW-ICS, meaning UCLG9 or UCLH2 or UCLJ3, using the respective OneClick
Flash CWMR using Odin (the previous step overwrites recovery so you will have to do this again even if you flashed CWM previously)
Boot into CWM
Flash your AOSP-JB ROM of choice
Flash the correct gapps for your ROM
Format /data (aka factory reset)
Reboot into ROM and enjoy
Step 1 may or may not be necessary -- nobody's tried going from TW-GB straight to AOSP-JB yet. If you're feeling adventurous, try it and let us know how it goes.
Once you've flashed a TW-ICS once, you won't need to do it again -- at that point flashing a new TW-ICS or AOSP-JB ROM is as simple as flash-format-boot.
Thanks for the updated info, I didn't think it would be that simple.
Not sure what TW stands for since I haven't seen that abbreviation yet.
But basically for step one I can grab the UCLG9 from this thread http://forum.xda-developers.com/showthread.php?t=1841502
and flash it with CWM and then follow on from step 2? Or would I be better off grabbing the newer UCLJ3 from SamMobile and using Odin?
Bram Skull said:
Thanks for the updated info, I didn't think it would be that simple.
Not sure what TW stands for since I haven't seen that abbreviation yet.
But basically for step one I can grab the UCLG9 from this thread http://forum.xda-developers.com/showthread.php?t=1841502
and flash it with CWM and then follow on from step 2? Or would I be better off grabbing the newer UCLJ3 from SamMobile and using Odin?
Click to expand...
Click to collapse
Nope no zips or Odin just use one click the first time. So for step 1 above follow this http://www.theandroidsoul.com/android-4-0-4-ice-cream-sandwich-update-for-att-captivate-glide-i927uclg9/. Can't get easier then this.
Bram Skull said:
Thanks for the updated info, I didn't think it would be that simple.
Not sure what TW stands for since I haven't seen that abbreviation yet.
Click to expand...
Click to collapse
TW == TouchWiz. Basically official Samsung stuff and ROMs based directly on such.
But basically for step one I can grab the UCLG9 from this thread http://forum.xda-developers.com/showthread.php?t=1841502
and flash it with CWM and then follow on from step 2? Or would I be better off grabbing the newer UCLJ3 from SamMobile and using Odin?
Click to expand...
Click to collapse
I would get the full EXE, just to be sure. The CWM zips generally don't include bootloader or baseband and that's the important stuff.
I would get the full EXE, just to be sure. The CWM zips generally don't include bootloader or baseband and that's the important stuff.
Click to expand...
Click to collapse
I used the CWM flash and can confirm the no updated baseband since it still had the stock Rogers one on AT&T-ICS and in CM-10.1. Not sure about ICS but in CM-10.1 I could get voice but no data and haven't tested txt.
Going to flash back to stock with the backup I made for now while I research solutions to a few personal gripes I have with CM-10.1.
And would the UCLJ3 from SamMobile with odin or kies be as effective as the EXE version since I already have it downloaded?
Thanks for helping a total noob and to be honest this is my first Android phone.
Bram Skull said:
I used the CWM flash and can confirm the no updated baseband since it still had the stock Rogers one on AT&T-ICS and in CM-10.1. Not sure about ICS but in CM-10.1 I could get voice but no data and haven't tested txt.
Going to flash back to stock with the backup I made for now while I research solutions to a few personal gripes I have with CM-10.1.
And would the UCLJ3 from SamMobile with odin or kies be as effective as the EXE version since I already have it downloaded?
Thanks for helping a total noob and to be honest this is my first Android phone.
Click to expand...
Click to collapse
I just took a peek... ooh. Looks like pretty much everything is in there. You should be good.
It's been a long bloody time since I fiddled around with stuff on this phone. So I'm still on a rooted 4.1.2.
My questions are is it worth the upgrade to KitKat? And if so, what's the easiest way for me to do so? Hopefully retaining root, but not too necessary.
Help would be appreciated. For dummies.
Hey there.
I've gone through the process myself recently. Here is what you should do :
1. Download a custom rom from the Android Development forum. For example I downloaded the DN3 v5.2, but whatever catches your eye is fine.
2. Just follow the instructions the rom' s topic states.
3. If you have trouble getting to the recovery mode, you should flash with Odin some custom recovery. I like the cwm recovery.
4. Most guides provide info how to root your phone but if not then there is a topic in the Android Development forum about it.
I suggest backing up everything you can before- copy the phone contents to your pc, run the efs professional program to backup your efs.
Cheers
Rizaria said:
It's been a long bloody time since I fiddled around with stuff on this phone. So I'm still on a rooted 4.1.2.
My questions are is it worth the upgrade to KitKat? And if so, what's the easiest way for me to do so? Hopefully retaining root, but not too necessary.
Help would be appreciated. For dummies.
Click to expand...
Click to collapse
Hi there. I'm using n7100. N7105 is not far different to n7100. I've recently upgraded my phone from 4.3 to 4.4. I can't see a big difference from the 2 version except 4.4 consumes more battery than 4.3. I think you should consider 4.3 first before going straight to 4.4.
Just to inform you. What I know is...4.3 and 4.4 Official Rom already have Knox. So maybe you should read about them first. And Flashing Custom Recovery like PhilzTouchRecovery may trigger your Knox and increase your Binary Counter. And you may loose your warranty.
Flashing and rooting stock ROM is easy. But you have to do it right. What I did:
1. Download Odin
2. Download Samsung USB Drivers
3 Download 4.4 Firmware for my phone at sammobile.com
4. Install Samsung USB Driver
5. Run Odin
6. Put phone in Download Mode. Check if Odin successfully detected my phone
7. Once success, load the firmware to PDA Tab/Button. Don't touch anything
8. Press start. Wait till done. Wait till your phone reboot on it's own.
9. Once rebooted, check "About Device".
10. Done!
11. Download PhilzTouchRecovery 6.26
12. Put device into Download Mode again.
13. Run Odin again
14. Connect device again
15. Load PhilzTouchRecovery.tar.md5 to PDA Tab/Button
16. Uncheck Auto Reboot from Odin
17. Click start. Once Pass! Disconnect device.
18. Hold Power Button, DON'T RELEASE till you boot into your new recovery.
19. Once booted to PhilzRecovery, select reboot system now, but make sure not to overwrite with stock recovery or else you're PhilzRecovery will be reverted back to your stock recovery and you have to flash again your PhilzRecovery.
20. Once successfully flashed PhilzRecovery. Make all necessary backups (Full backup) you can't make EFS/MODEM backup yet because your not yet Rooted. You just installed Custom Recovery.
21. Once fully backed up. Copy backup files to your PC.
22. If you want to root again. Use CF-ROOT on 4.4.2 or use Dr.Ketan's Multi-Tool-Advance-V6 in 4.3. And follow their instructions.
Good Luck. HTH.
PoOoZaQ said:
Hey there.
I've gone through the process myself recently. Here is what you should do :
1. Download a custom rom from the Android Development forum. For example I downloaded the DN3 v5.2, but whatever catches your eye is fine.
2. Just follow the instructions the rom' s topic states.
3. If you have trouble getting to the recovery mode, you should flash with Odin some custom recovery. I like the cwm recovery.
4. Most guides provide info how to root your phone but if not then there is a topic in the Android Development forum about it.
I suggest backing up everything you can before- copy the phone contents to your pc, run the efs professional program to backup your efs.
Cheers
Click to expand...
Click to collapse
Thanks for that. Still wondering which one I should try all this Knox stuff is puzzling. Seems a lot of things have happened since I last had a fiddle.
asin_punk said:
Hi there. I'm using n7100. N7105 is not far different to n7100. I've recently upgraded my phone from 4.3 to 4.4. I can't see a big difference from the 2 version except 4.4 consumes more battery than 4.3. I think you should consider 4.3 first before going straight to 4.4.
Just to inform you. What I know is...4.3 and 4.4 Official Rom already have Knox. So maybe you should read about them first. And Flashing Custom Recovery like PhilzTouchRecovery may trigger your Knox and increase your Binary Counter. And you may loose your warranty.
Flashing and rooting stock ROM is easy. But you have to do it right. What I did:
1. Download Odin
2. Download Samsung USB Drivers
3 Download 4.4 Firmware for my phone at sammobile.com
4. Install Samsung USB Driver
5. Run Odin
6. Put phone in Download Mode. Check if Odin successfully detected my phone
7. Once success, load the firmware to PDA Tab/Button. Don't touch anything
8. Press start. Wait till done. Wait till your phone reboot on it's own.
9. Once rebooted, check "About Device".
10. Done!
11. Download PhilzTouchRecovery 6.26
12. Put device into Download Mode again.
13. Run Odin again
14. Connect device again
15. Load PhilzTouchRecovery.tar.md5 to PDA Tab/Button
16. Uncheck Auto Reboot from Odin
17. Click start. Once Pass! Disconnect device.
18. Hold Power Button, DON'T RELEASE till you boot into your new recovery.
19. Once booted to PhilzRecovery, select reboot system now, but make sure not to overwrite with stock recovery or else you're PhilzRecovery will be reverted back to your stock recovery and you have to flash again your PhilzRecovery.
20. Once successfully flashed PhilzRecovery. Make all necessary backups (Full backup) you can't make EFS/MODEM backup yet because your not yet Rooted. You just installed Custom Recovery.
21. Once fully backed up. Copy backup files to your PC.
22. If you want to root again. Use CF-ROOT on 4.4.2 or use Dr.Ketan's Multi-Tool-Advance-V6 in 4.3. And follow their instructions.
Good Luck. HTH.
Click to expand...
Click to collapse
Very concise steps, cheers for that. Might give all that a try. Just need a safe rom. Not sure what. Is there anything else that needs flashing, like modem files or anything?
Thanks for both your comments.
Only the rom is necessary. Shouldn't flash modem and kernel etc unless something doesn't work.
All the roms published in xda are fine and safe. I just went for the topic with the most views.
If you want you can also download stock 4.3 from www.sammobile.com
Just choose your device and you get a file flashable with odin. About 1.9 giga download.
Rizaria said:
Thanks for that. Still wondering which one I should try all this Knox stuff is puzzling. Seems a lot of things have happened since I last had a fiddle.
Very concise steps, cheers for that. Might give all that a try. Just need a safe rom. Not sure what. Is there anything else that needs flashing, like modem files or anything?
Thanks for both your comments.
Click to expand...
Click to collapse
Your current Bootloader doesn't have Knox. So you better search for a 4.3 or 4.4 rom that doesn't flash new bootloader. I think i saw it somewhere in the development.If I were not mistaken, it should be flashed thru custom recovery. Coz it's a zip file.
All I know is all rom files from sammobile.com includes new kernel, bootloader and modem. So if you flash this roms from sammobile, you will have a new kernel, bootloader and modem. It's all up to you. If I were you, I'll stay away from Knox. So find a rom that supports your current bootloader. Maybe a custom one.
Maybe this will help...
http://forum.xda-developers.com/showthread.php?t=2747963
asin_punk said:
Your current Bootloader doesn't have Knox. So you better search for a 4.3 or 4.4 rom that doesn't flash new bootloader. I think i saw it somewhere in the development.If I were not mistaken, it should be flashed thru custom recovery. Coz it's a zip file.
All I know is all rom files from sammobile.com includes new kernel, bootloader and modem. So if you flash this roms from sammobile, you will have a new kernel, bootloader and modem. It's all up to you. If I were you, I'll stay away from Knox. So find a rom that supports your current bootloader. Maybe a custom one.
Maybe this will help...
http://forum.xda-developers.com/showthread.php?t=2747963
Click to expand...
Click to collapse
Fair enough, thanks.
If I try the one below, think that'd work out alright? And which to use, deoxed or not?
http://forum.xda-developers.com/showthread.php?t=2588787
Sent from my GT-N7105 using XDA Free mobile app
Rizaria said:
Fair enough, thanks.
If I try the one below, think that'd work out alright? And which to use, deoxed or not?
http://forum.xda-developers.com/showthread.php?t=2588787
Sent from my GT-N7105 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah nice find... It should work fine... you're on the 3rd status "For those are on the 4.1.2 bootloader the rom could work normally with AGNi Kernel include in rom". I think you should go for DEODEXED for more customization and etc. Read here: http://codeversed.com/deodexed-vs-odexed-rom/.
Make sure to follow instruction precisely and strictly. And make sure to copy your Backup to your PC right after you created it. Coz if you do a Full Wipe, Reset and Clean Install, it will also delete the backup that you made. Read the instructions multiple times carefully to avoid mislead. Once you done it successfully, you will be on Custom Rom and Custom Kernel. Sounds very techie. Hahaha. Good Luck!
asin_punk said:
Yeah nice find... It should work fine... you're on the 3rd status "For those are on the 4.1.2 bootloader the rom could work normally with AGNi Kernel include in rom". I think you should go for DEODEXED for more customization and etc. Read here: http://codeversed.com/deodexed-vs-odexed-rom/.
Make sure to follow instruction precisely and strictly. And make sure to copy your Backup to your PC right after you created it. Coz if you do a Full Wipe, Reset and Clean Install, it will also delete the backup that you made. Read the instructions multiple times carefully to avoid mislead. Once you done it successfully, you will be on Custom Rom and Custom Kernel. Sounds very techie. Hahaha. Good Luck!
Click to expand...
Click to collapse
Thanks for the advice.
Really, I wanted to upgrade to Android L but then I saw it wasn't out yet so I was like...huh, KitKat time?
I'm not even sure if it'll be any better than what I have! Mostly just want something with better battery life. Even though I just bought a new battery that lets me use my phone for 3 days and a half hour. I have noticed that Screen/Android seem to be bleeding power a lot more these days, so figured it might be worth a wipe and an upgrade.
In any case, whenever I do, I have some handy guides now. Cheers~
Hello, I used to be rooted with custom ROMs ect but went back to stock I317ATTALJ2 so I can give the phone to my daughter. Well everything went smooth until an update from AT&T came through and she ran it when the battery was at 21% but I'm not sure it that matter but didn't help in matters... Anyhow it ran the upgrade and on reboot it stayed on the Galaxy Note II screen and wont do anything but sit there. I let it sit for a long time before pulling the battery and booting but it goes to same screen and same thing. I can not get into recovery (Volume Up, Home, Pwr) but I can go into download mode. With the battery being so low I read that it charges while in download mode so for the remainder of the day I put the phone in download mode and plugged into charger.
Suggestions?
After you get it charged up some and you're in download mode. Just Odin back to stock Att firmware should fix the problem hopefully...
You can find the stock firmware here>> http://bit.ly/1HNVFVJ
Guess the phone didn't like that update ?.
Bajanman said:
After you get it charged up some and you're in download mode. Just Odin back to stock Att firmware should fix the problem hopefully...
You can find the stock firmware here>> http://bit.ly/1HNVFVJ
Guess the phone didn't like that update .
Click to expand...
Click to collapse
Ok, Ill give the stock firmware (At&t Firmware I317UCALJ2 Uploaded By-Bajanman) that Bajanman supplys ill let you guys know in an hour or two its downloading now. I did try re installing the stock firmware I had that worked the first time and it was from SamMobile and it too sent me to the Galaxy Note II screen and froze so its not looking good.....
Thanks!
Oxicottin said:
Ok, Ill give the stock firmware (At&t Firmware I317UCALJ2 Uploaded By-Bajanman) that Bajanman supplys ill let you guys know in an hour or two its downloading now. I did try re installing the stock firmware I had that worked the first time and it was from SamMobile and it too sent me to the Galaxy Note II screen and froze so its not looking good.....
Thanks!
Click to expand...
Click to collapse
Ok.
Hopefully everything works out next time around.
Another thing you could try is flashing which ever recovery you previously had installed. Last time I was having issues with something similar, after re flashing my recovery everything started working again. Just just a thought that might work.
I'm monitoring this thread too see what happens ok.
Bajanman said:
Ok.
Hopefully everything works out next time around.
Another thing you could try is flashing which ever recovery you previously had installed. Last time I was having issues with something similar, after re flashing my recovery everything started working again. Just just a thought that might work.
I'm monitoring this thread too see what happens ok.
Click to expand...
Click to collapse
Recovery? can I flash the stock recovery using ODIN? If so where do I get it.... I always have used TWRP I wanted to use custom ROMs never really experimented with anything else.
Oxicottin said:
Recovery? can I flash the stock recovery using ODIN? If so where do I get it.... I always have used TWRP I wanted to use custom ROMs never really experimented with anything else.
Click to expand...
Click to collapse
Yes you can flash a custom recovery from Odin. You just have to use the (Twrp) tar file found here>>>
http://bit.ly/1y0Tyg7
Find your device model and download the tar. And make sure you're downloading the correct file for your device ok!
I to use Twrp and luv it.?
OK, well its not looking good....
1) Flashed the stock firmware suggested...... Still get same results!
2) Flashed TWRP through ODIN and it made it to the same screen and froze. Did a battery pull and button combo and it wont go into recovery.
Is there a application that will force your phone into recovery and download modes? I remember back when I messed with the captivate there was a application someone built that did such a thing.
Any suggestions?
Oxicottin said:
OK, well its not looking good....
1) Flashed the stock firmware suggested...... Still get same results!
2) Flashed TWRP through ODIN and it made it to the same screen and froze. Did a battery pull and button combo and it wont go into recovery.
Is there a application that will force your phone into recovery and download modes? I remember back when I messed with the captivate there was a application someone built that did such a thing.
Any suggestions?
Click to expand...
Click to collapse
Not sure you were on the newer 4.4.2 bootloader or not. If it was on a newer bootloader then you won't be able to downgrade.. This might help you get the phone working again since you just flashed the original firmware.
Go to this thread here>>http://forum.xda-developers.com/showthread.php?t=2502464.
Download
4.3 Param.bin and Tz.img
http://d-h.st/OYC
Step 2 (no bootloader in here)
flash this to bring wifi back
but keep your knox free 4.1.2 bootloader.
Allowing you to freely flash between 4.1.2 roms and the latest 4.3 leak
Without having to one click,Keeping Wifi Throughout and removing Knox
Click to expand...
Click to collapse
Unzip, Boot into Download mode, Open ODIN, put tar file in PDS slot, click Start.
Then you can go here for the latest stock Att firmware. If the above steps don't help you, then you could try flashing one one the rooted stock packages from this thread.
Bajanman said:
Not sure you were on the newer 4.4.2 bootloader or not. If it was on a newer bootloader then you won't be able to downgrade.. This might help you get the phone working again since you just flashed the original firmware.
Go to this thread here>>http://forum.xda-developers.com/showthread.php?t=2502464.
Download
4.3 Param.bin and Tz.img
http://d-h.st/OYC
Unzip, Boot into Download mode, Open ODIN, put tar file in PDS slot, click Start.
Then you can go here for the latest stock Att firmware. If the above steps don't help you, then you could try flashing one one the rooted stock packages from this thread.
Click to expand...
Click to collapse
Ok that worked and it booted!!!! Now im on 4.1.1 with TWRP
Not really sure what I just did? Did I downgrade my bootloader? Also, now how do I get it to the most up to date version without this again?
I downloaded an app and it says im on.....
Bootloader Version: 1317UCUBMK6
Thanks!
Oxicottin said:
Ok that worked and it booted!!!! Now im on 4.1.1 with TWRP
Not really sure what I just did? Did I downgrade my bootloader? Also, now how do I get it to the most up to date version without this again?
Thanks!
Click to expand...
Click to collapse
Ok not is back working again, which is great news ?. Go to the link I posted for the stock firmware, and use the rooted one.
But first make a backup of your working system first ok.
Bajanman said:
Ok not is back working again, which is great news . Go to the link I posted for the stock firmware, and use the rooted one.
But first make a backup of your working system first ok.
Click to expand...
Click to collapse
Ok, Im On 4.3 now and its working great.... Thank You!
Oxicottin said:
Ok, Im On 4.3 now and its working great.... Thank You!
Click to expand...
Click to collapse
You're very welcome glad I could help fix it.
Have a good day...
Ok problem solved so unsubscribing from this thread. If you run into any other problems you can always hit me up thru pm ?.
I have spent days looking, turn on goes to kies firmware screen yet when i put in the model and s/n it shuts and the new samsung app to replace kies is of no help. I can get to the download screen and odin shows it up but no ATT 10.5 Tab S Sm-T807A firmware ANYWHERE.
Please help this is a very very expensive paperweight and im not affiliated with ATT so them helping me is out of the question.
Samobile.com
info.sven said:
Samobile.com
Click to expand...
Click to collapse
They dont have it for the SM-T807A
0 Results found
You searched for "sm-t807a"
It would better if you just explain what state the tablet is in and how it got to that state.
There is no official software for the t807a.
OK here how it goes,
The tablet was completely fine.
The original owner ( a family member) tried to root it and didnt accomplish it, somehow through his process it ended up softbricked.
I can enter he download mode for odin but no firmware for this LTE model.
When I turn it on it goes to the kies screen but kies doesnt recognize it, and when I enter the serial it buffers for 2 seconds then closes the process of kies.
Also it says device isnt supported and yes I have installed the right drivers and uninstalled kies numerous times.
The new replacement prog for Kies (forgot the name) is no help either.
Im terrified of what to do next as it does go to the odin screen just no firmware as I stated.
Any update, or could someone upload the stock firmware so i can use Odin on it.
Samsung told me ATT can flash it for free onto it so its deff a possibility however I do not have a ATT account so they cant help me.
It doesn't boot because the stock recovery has been wiped/replaced.
Thats assuming you have tried to boot recovery?
The att models are all bootloader locked.
I'm surprised a bootloader locked device even allowed an unsigned image to flash or did they use something like flashify?
The stock ota update was posted by someone here a while back. Your only chance is to pull the recovery from it and try and flash it in download mode. However odin may refuse to flash it.
If I can find it I can pull out the recovery.img and post a modified cf_autoroot which will try and flash the original recovery, that's if odin will even accept the image.
I was used with something like kingroot.
"The stock ota update was posted by someone here a while back. Your only chance is to pull the recovery from it and try and flash it in download mode. However odin may refuse to flash it.
If I can find it I can pull out the recovery.img and post a modified cf_autoroot which will try and flash the original recovery, that's if odin will even accept the image."
this i would highly appreciate as the firmwares not deleted just corrupted.
i have searched the whole web.
here is the link to the pulled stock sm-t807a files from a xda member
https://drive.google.com/folderview?id=0B7ndOWpeCEJ4NFVHZmtvTFN0UFU&usp=sharing
PowerfulJY, any successfull update with your SM-T807A journey?
I have the same problem as you, and Odin refuses to flash your firmware files
synphonica said:
PowerfulJY, any successfull update with your SM-T807A journey?
I have the same problem as you, and Odin refuses to flash your firmware files
Click to expand...
Click to collapse
The images won't flash as they are raw unsigned images.
The update should contain a signed recovery image, but may still not flash with odin as the tar package you make will not be signed either and odin may refuse to flash
There may be a way though, another member managed to brick their device by flashing twrp using Heimdall, but couldn't then flash back the stock recovery with Heimdall.
If somehow the stock recovery can be forced to flash with Heimdall then there's a chance of unbricking the device.
I worked just flashed the FW part through AP did it on a friends pc all is back to new.
if you need a link for the ripped files just pm me.
also odin was used.
ashyx said:
The images won't flash as they are raw unsigned images.
The update should contain a signed recovery image, but may still not flash with odin as the tar package you make will not be signed either and odin may refuse to flash
There may be a way though, another member managed to brick their device by flashing twrp using Heimdall, but couldn't then flash back the stock recovery with Heimdall.
If somehow the stock recovery can be forced to flash with Heimdall then there's a chance of unbricking the device.
Click to expand...
Click to collapse
Unfortunately, Heimdall shows the same behaviour as Odin has.
AFAIK they are using the same protocol and seems that recovery CRC/sign check done via device internally, not via flashing tool.
PowerfulJY said:
I worked just flashed the FW part through AP did it on a friends pc all is back to new.
if you need a link for the ripped files just pm me.
Click to expand...
Click to collapse
Please explain in more detail what you have done for the benefit of others.
---------- Post added at 03:22 PM ---------- Previous post was at 03:22 PM ----------
synphonica said:
Unfortunately, Heimdall shows the same behaviour as Odin has.
AFAIK they are using the same protocol and seems that recovery CRC/sign check done via device internally, not via flashing tool.
Click to expand...
Click to collapse
Did you use command line or gui?
I used GUI, i didnt do the bootloader or choose any special clickies, I simply tried another pc with the same FW and it flashed in a hearbeast with PASS.
USB hubs are the devil, TRY EVERY USB PORT YOU HAVE
Kies sucks so does the new one.
any issues PM me and ill set you straightm any public questions ask away.
You have to download the IMG files and use the IMG to TAR app, I will provide a ZIP with all tars included but I assure you dont start ****ing around with bootloader images stick to AP.
AT&T is he devil.
The new Rockstar Whipped Strawberry OWNS, Oraneg Creme is Meh.
PowerfulJY said:
I used GUI, i didnt do the bootloader or choose any special clickies, I simply tried another pc with the same FW and it flashed in a hearbeast with PASS.
USB hubs are the devil, TRY EVERY USB PORT YOU HAVE
Kies sucks so does the new one.
any issues PM me and ill set you straightm any public questions ask away.
You have to download the IMG files and use the IMG to TAR app, I will provide a ZIP with all tars included but I assure you dont start ****ing around with bootloader images stick to AP.
AT&T is he devil.
The new Rockstar Whipped Strawberry OWNS, Oraneg Creme is Meh.
Click to expand...
Click to collapse
The gui question was for synphonica about Heimdall.
Are you saying you flashed the images with odin? Which version and which images?
This has been tried before and failed.
Also what do you mean you tried a pc with the same firmware, same firmware as what?
I'm new to rooting so be gentle, I just bought a Galaxy Tab S 10.5 sm-t807a (AT&T) with Android 5.0.2 Lollipop. I want to backup the stock ROM (firmware) so I can go back just in case I bricked it when rooting or installing custom ROM. I searched the web but there are no clear instruction on how to do it for an unrooted sm-t807a. Can someone provide me with a step-by-step instruction? I can share my backup of the stock ROM afterward since there does not seem to be one on the web. Thank you in advance for your help.
cluver53 said:
I'm new to rooting so be gentle, I just bought a Galaxy Tab S 10.5 sm-t807a (AT&T) with Android 5.0.2 Lollipop. I want to backup the stock ROM (firmware) so I can go back just in case I bricked it when rooting or installing custom ROM. I searched the web but there are no clear instruction on how to do it for an unrooted sm-t807a. Can someone provide me with a step-by-step instruction? I can share my backup of the stock ROM afterward since there does not seem to be one on the web. Thank you in advance for your help.
Click to expand...
Click to collapse
You can only root with Kingroot, don't try any other method or you'll brick it nor can you install a custom kernel or recovery.
Once you have root you can pull the partition images with EFS PRO or PARTITION BACKUP.
The best way to have a back up is to catch the stock Firmware update.
This is tricky so research how to do it.
There is one backup I know of:
https://drive.google.com/folderview?id=0B7ndOWpeCEJ4NFVHZmtvTFN0UFU&usp=sharing