Develop Bugs

[GUIDE] Rooting and Unbricking p930/p935/p936

EDIT: I no longer support this guide, as I've not owned a nitro for at least 2 years now. It is all still accurate however, just make sure to follow the steps.
The package is hosted on my google drive, and I have no plans to remove it, so if this thread is still up, so are the files.
Good luck!
--------------------
This guide will work for P930, P935, and P936 users.
I have merely put all the pieces together to have a concise all-in-one solution for rooting/unbricking the LGE-IPROJ. Credit is given to original contributors at the bottom of the guide.
As always, I am not responsible for any damage done to your phone by following this guide. Follow at your own risk.
I strongly suggest removing your SDCARD from the phone until step 18 since it causes the phone to boot slower and makes this process take longer.
Ensure that you have the LG USB drivers installed on your computer. If you don't they can be downloaded Here.
Foreword - This guide allows the phone to keep its correct build ID, so it hasn't got leftover data from the SU640 kdz which is flashed using the other method. We flash the experimental ICS build, root it, run keeproot, flash the p936 kdz, then run keeproot to restore root access. We then install CWM, and then we can flash ROMs to our heart's desire.
The reason we have to flash the p936 KDZ is that it overwrites the v18f secure bootloader, allowing us to flash CWM and not brick the phone.
1 - Download this package
2 - Backup your phone if you want.
3 - Extract the Unbrick Package
4 - Place phone in Download Mode (Turn off phone, then hold volume up while plugging in USB cable)
5 - Run the file - P930_UDT_v18f_04112012
6 - Set your phone to allow installation from unknown sources, and enable USB debugging.
7 - Run TPSparkyRoot.bat, following the instructions in the window.
8 - Perform a factory reset of the phone. This is done by shutting off the phone, then holding VOL DOWN + Power until the phone says FACTORY HARD RESET, then following the prompt (pressing power twice)
9 - Allow USB Debugging on the phone.
10 - Run Before.bat contained in the KeepRoot folder.
11 - In the KDZ tools folder, install msxml and run B2CAppSetup (Close the application after it has installed)
12 - Run Windows Enabler as Administrator, and press the icon in the system tray to activate it. (Windows enabler allows you to click on grayed out options to unlock them in programs. You can then set the option as you normally would.)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
13 - Place the phone in Download Mode (Turn off phone, then hold volume up while plugging in USB cable)
14 - Run KDZ_FW_UPD.exe. You need to set Type to 3GQCT, PhoneMode to CS_EMERGENCY, and point the KDZ file field to V10F_00.kdz
(SOME PEOPLE HAVE REPORTED HAVING TO PRESS "Read Phone Info" FOR THIS STEP TO WORK!)
Once these settings are enabled, hit the "Launch Software Update" button.
15 - After the update has run, the phone should bootloop on the second logo screen. While it does this, run AfterROOT.bat from the KeepRoot folder.
16 - Perform factory reset. This is done by pulling the battery, then holding VOL DOWN + Power until the phone says FACTORY HARD RESET, then following the prompt (pressing power twice)
17 - Set phone's language to english, then enable usb debugging.
NOTE: The following steps are optional. Downloading Rom Manager from the Play Store and installing CWM from there will do the same thing.
18 - Place the recovery.img file in the root directory of your phone's SD card
19 - Open cmd in KeepRoot\adb
20 - Run the following commands, while the phone is plugged in and has USB Debugging enabled
adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
Click to expand...
Click to collapse
21 - Accessing CWM - This is done by shutting off the phone, then holding VOL DOWN + Power until the phone says FACTORY HARD RESET, then following the prompt (pressing power twice)
Congratulations. Your phone now has CWM 6.0.1.5 installed, and you can flash any of the CWM flashable zips available for the P930 on XDA.
Edited: Added images, included more information, took corrections from posters.

Credit
- TPSparky for his root method
- alexw88 for This Post
- usercim for This Post
- Drumist, for helping me figure out how to use this method

It work for SU640? I want to downgrade ICS to GB.

I would use mazchalets or drumists, stickied guide for su640. If you replace the KDZ file in this method with a SU640 kdz, I see no reason why it wouldn't work. Even with the files included it will work, but you will have a P930 build ID.
Sent from my LG-P930 using XDA Premium HD app

I tried that guide but not success. However, thank for your advise.
Sent from my LG-SU640 using xda app-developers app

Work for anyone yet.....? and whats wrong with the one that exists that covers it all cuz all this does is diminish other guides that others have used, just trying to understand WHY sooooo many guides and no wonder many are confused??

I'm missing something. What benefit is there to keeping the build id?
Sent from my LG-P930 using xda premium

X0dus said:
I'm missing something. What benefit is there to keeping the build id?
Click to expand...
Click to collapse
Unsure. However, that is not the only difference. Another one I have noticed is that when turning on your phone, it will vibrate to indicate you've held the button long enough. This is something that never works after using the standard unbricking method. A Korean KDZ also means you will have a Korean baseband installed which doesn't work on the P93x devices, and you'll have to flash a new baseband at some point.
All in all, these are minor things though. I don't know if there is any major difference. This method does not require modifying your hosts file OR configuring the https.exe program, which makes it a little bit easier in my opinion.

drumist said:
Unsure. However, that is not the only difference. Another one I have noticed is that when turning on your phone, it will vibrate to indicate you've held the button long enough. This is something that never works after using the standard unbricking method. A Korean KDZ also means you will have a Korean baseband installed which doesn't work on the P93x devices, and you'll have to flash a new baseband at some point.
All in all, these are minor things though. I don't know if there is any major difference. This method does not require modifying your hosts file OR configuring the https.exe program, which makes it a little bit easier in my opinion.
Click to expand...
Click to collapse
Thanks. Clears up things a bit for people that haven't used a guide yet.

Thank you for this! Can any of the people who used this confirm whether or not this has an impact on the camera reboot bug in CM10?
Also wondering if it would be OK to follow this and then restore a full nandroid backup.
Sent from my LG-P930 using Tapatalk 2

Also wondering if it would be OK to follow this and then restore a full nandroid backup.
Click to expand...
Click to collapse
Yes, that's safe to do.

Not sure if it's due to aokp or having used this guide, but I haven't had a random reboot or bsod since. I also don't have the camera reboot issue.
EDIT: Screen not waking from sleep has happened once now, and I have started getting random reboots again. The camera reboot issue is still eliminated though. Probably going to switch to HO!NO!'s Full Throttle 9 and see if that improves my reboot situation.
Sent from my LG-P930 using XDA Premium HD app

hereric said:
Not sure if it's due to aokp or having used this guide, but I haven't had a random reboot or bsod since. I also don't have the camera reboot issue.
Sent from my LG-P930 using XDA Premium HD app
Click to expand...
Click to collapse
I will probably give this a try later on today. Thanks for making this write-up!

Was on Liquid Nitro, made a CWM full backup and did the new unbrick process this afternoon.
its easier than the su640 one.
Two little problems:
1. on step 12, after running windows enabler, have to left-click the icon on system tray to active it.
2. all prompts in bat files are in Chinese...need to change to English.
After that, I restored my backup over the GB ROM and it seemed to work fine. But I later learned that CWM didn't backup baseband, so I reflashed Liquid Nitro again then did another restore over the Liquid Nitro just to be safe.

If I have the P930, and I've successfully flashed and rooted the ICS build, is there really any need for me to continue further with the guide? What's preventing me from just flashing recovery right now and being on my way?

LiquidSolstice said:
If I have the P930, and I've successfully flashed and rooted the ICS build, is there really any need for me to continue further with the guide? What's preventing me from just flashing recovery right now and being on my way?
Click to expand...
Click to collapse
ICS bootloader doesn't work with CWM so we need to do the unbrick to back to GB bootloader.

Every time I open the KDZ fw update, all the options are greyed out. I'm stuck there. Ideas?

arda99 said:
ICS bootloader doesn't work with CWM so we need to do the unbrick to back to GB bootloader.
Click to expand...
Click to collapse
Thanks. Indeed, I was dumb and flashed recovery and got the secure boot issue. Now that I have that, should I redo the whole process?

I've done the whole thing over twice now, I simply cannot get the KDZ firmware updater to do anything. If I try "Read Device Information" it always freezes and exits.
EDIT: No matter what I do, even going so far as to try this on a computer with freshly installed Windows 7 on it (and of course, installing the provided LG driver), I keep getting stuck at this infernal screen:
http://db.tt/Ro57bvLc
MSXML is installed, the Window Enabler is started as Admin, but the damn thing just won't let me use any of its options .

LiquidSolstice said:
I've done the whole thing over twice now, I simply cannot get the KDZ firmware updater to do anything. If I try "Read Device Information" it always freezes and exits.
EDIT: No matter what I do, even going so far as to try this on a computer with freshly installed Windows 7 on it (and of course, installing the provided LG driver), I keep getting stuck at this infernal screen:
http://db.tt/Ro57bvLc
MSXML is installed, the Window Enabler is started as Admin, but the damn thing just won't let me use any of its options .
Click to expand...
Click to collapse
After running windows enabler, left click the icon on the system tray, you'll see an "ON" shown on the icon. Then the grayed area will be enabled.

Tutorial: How to use KIES Emergency Firmware Recovery (EFR)

Edit Nov 28 2013: GN3 Owners PLEASE READ!
As of the new update the ATT Galaxy note 3(possibly all carriers) IS NOT compatable with KIES EFR!
This includes KIES 2.XX and KIES 3! What does this mean?
If you took the MJ5 update you will no longer be able to use the KIES Emergency Firmware Updater.
Please complain to Samsung, locking the bootloader is one thing but no EFR??
Would you get on ship with no life boats or life preservers??
Seriously uncool of Samsung to do this.
-end of edit
/rant
So its come to my attention a lot of new guys are getting stuck soft brick, bootloop, borked recovery etc.
So .... I made this tutorial for everyone.
Please: dont flame or post useless comments.
Its great for you Odin is easy, but I made this for people who want a hassle free easy way to recover their phone.
This is also imo the fastest and easiest way back to true stock w/o a "modified"
Some people have reported a flash count of 1 but idk I always went back to 0.
If you are new, have no rooting, rom flashing or w/e experience, imo you should NOT be using odin until you have completely read up on it. I mean hey some of you super geniuses have no probs but when I see posters who have no clue about usb drivers or even how to use kies, im confused why you would want to venture to odin? 500 $ is a very expensive brick.
Ok so unsure about odin or just new and now you just borked your brand new phone?
First things first:
Can you get into dl mode.
Dont worry about recovery mode because it doesnt matter for this. This works with corrupted recovery as well.
For now lets just say download mode is achieved one way only:
Press : vol down power and home key all at the same time. Release quickly when you see the screen come up. Takes practice some times.
:thumbup: This method will remove "modified" status from your phone! :thumbup:
:beer:
Ok ready? You want step by step you got it.
If this doesnt work you are doing it wrong, so try again. Even with Odin you may have to try several times, its the nature of android.
If you can get into DL mode you CAN 100% recover your device.
If it doesnt work or you get an error, you are doing this wrong. I am pretty sure this is for ALL Samsung phones but I can only confirm this for my gs3 and note2.
Keep in mind: I corrupted my recovery on my gs3 several times and this still worked. I will assume the same for my note 2.
Download kies from samsung.com
Follow the prompts but no need to install the stupid codecs.
When you are done, (dont forget hit "yes" to dl current usb drivers)
ON your computer "run as administrator" the kies icon.
make sure you are connected to the internet.
Kies will automatically check for updates and proper usb drivers.
No need to install "myfree codecs" hit no on that.
every thing else hit yes
Step one:
Run kies as administrator as I said And do all the usb updates, kies updates
but leave the codec thing alone.
Step by step instructions just follow the pics in order:
1.Kies opens asks about update
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2.
3.Dont worry about this
4. Now in top left corner hit "tools" tab. Ignore everything else
5. After clicking tools tab click the emergency fimrware recover choice as described below
6. For now ignore this button. YOu might need it later but ignore it for now
7.
8.Well last step. Hit emergency recovery ( the "ok" button wont be there )
this will probably take 20 to 30 min total. The EFR will let you know if its succesfull or fail.
IF it fails try using the method I said to ignore. Its the same thing just an extra step of in putting your phones exact model number.
Heres some xtra links: (Thanks to Bajanman for finding these btw!)
http://www.sammobile.com/firmwares/1/
http://www.sammobile.com/kies/
http://m.samsung.com/us/support/

Nice help guide for noobs.
Good guide freak :thumbup:
Might want to go back and check some of your words tho. Lot of them misspelled... lol
Side note: All my years with Sammy I've never used Kies with any of my phone's!!
Sent from my SAMSUNG-SGH-I317 using Xparent SkyBlue Tapatalk 2

yeah yeah yeah

Nice tut freakboy i just hope I dont need to use it someday I subscribed anyways who know flashing games always full of surprises.
Sent from my SAMSUNG-SGH-I317 using xda premium

Please HELP
i have an at&t galaxy note 2 was rooted got OTA update now no signal and when i go to mobile networks (under settings) it says insert sim card so i am trying to do it your way and i have updated everything (drivers and kies) and when i try to connect to kies it says my device isn't supported by kies and there is no phone model in the white box to use the "emergency recovery using recovery code" is there a place to get this code?
Please help

Well first off there shouldnt be a need to use the kies efr with just an ota.
You can select your phone model manually.
Can I ask...did you install a recovery and make a bu after you rooted ?
im not familiar with these newer ota probs, I remember on my dx ota was no biggie due to rootkeeper. Its strange that a stock rooted phone gets borked with an ota.
Can you get into recovery?
Can you get into dl mode?
Im subscribed to this thread so ill try n help out
Edit: are you using this method because you are unfamiliar with odin?

i did install CWM recovery
i don't remember making a back up but i am sure i did
i can NOT get to recovery
i can get to dl mode
i am familiar with odin but i am on my work computer as i don't have internet at home at the moment so i cant run searches as it trips the big brother software here and i would get in trouble the phone seems to work fine other then it doesn't recognize the sim card and no recovery mode
but if i could find a stock rom i could just flash with odin

That may also be your problem.
Are you running kies as admin?
Sorry if these sound like stupid questions.
But 8f you dont have admin privies kies may not work.
Regardless there is a drop down for you to manually choose your phone.
You do have usb debugging?
A corrupted recovery should not affect your ability to use kies.
Your jobs software could be blocking it.

Also you do realise you cannot take ota with custom recovery?
Thats why your phone is borked.

i do realize it now lol but i didnt even think about it when it happened
yes running kies as admin
no to usb debugging don't event remember how to get to usb debugging but if it is in settings under mobile networks i cant get there it just says insert sim card

Justvto be sure this is an sgh-i317 correct?
Try doing the upgrade first that may give you the code.
First make sure you have usb debugging
Home>Settings> developers options> make sure usb debugging is checked.
Also since it sounds like your recovery is corrupted do not do a factory reset.

Ok so try this:
Make sure you have latest drivers from samsung for YOUR device.
Make sure kies is the latest version.
Make sure antivirus is off orvput kies in the whitelist/allowed.
Turning off is better.
Go to dl mode on phone .
Sincevkies is already running go to thetop menu :
tools> emergency firmware recovery
You should get a drop down list of devices. If this is an att phone and not another carrier model ported to att, you should choose sgh-i317 (att galaxy note 2). You shouldnt need a number thats only if you try to upgrade and it fails ( as I mentioned you may want to try upgrade first to trick the que to give you a number)
Post back.

+1
Sent from my SGH-I317M using xda premium

freakboy13 said:
Ok so try this:
Make sure you have latest drivers from samsung for YOUR device.
Make sure kies is the latest version.
Make sure antivirus is off orvput kies in the whitelist/allowed.
Turning off is better.
Go to dl mode on phone .
Sincevkies is already running go to thetop menu :
tools> emergency firmware recovery
You should get a drop down list of devices. If this is an att phone and not another carrier model ported to att, you should choose sgh-i317 (att galaxy note 2). You shouldnt need a number thats only if you try to upgrade and it fails ( as I mentioned you may want to try upgrade first to trick the que to give you a number)
Post back.
Click to expand...
Click to collapse
thanks so much for all your help there is no drop down box on my version of kies however i found stock firmware some where else and it is working now again thanks so much

mrnewspaper said:
thanks so much for all your help there is no drop down box on my version of kies however i found stock firmware some where else and it is working now again thanks so much
Click to expand...
Click to collapse
Nice job! Isnt it great figuring things out yourself?
Love hearing happy endings!
Now... go into recovery and :
Make a backup/boot img .
:thumbup:

Hello,
I am trying to fix my Korean Note 1. It is not being listed in the list of devices. I have it in D/L mode but it isn't listed. Can I use the code and, if so, what is the right code?

activepassive said:
Hello,
I am trying to fix my Korean Note 1. It is not being listed in the list of devices. I have it in D/L mode but it isn't listed. Can I use the code and, if so, what is the right code?
Click to expand...
Click to collapse
Hmmm not that familiar with note 1 or international version but ill assume its the same?
If you are not listed in the database you may want to try using odin.
The code needs to be generated by kies.
Is kies recognizing your phone?
I may be mistakwn but isnt their a kies for your country or some thing like that?
Have you submited this question in your forum?
Edit: I found this I hope it helps you!
http://forum.xda-developers.com/showthread.php?t=1740367
sent from my T.A.R.T.I.S
(Time And Relative Tarts In Space)

so this will restore my phone to stock and will instal stock recovery and reset my flash counter and modified status? no need for tiangle away and unroot??

i tried doing exactly what was in the OP and it's now stuck at 0% at restoring. It's given me an error message a few times before and i tried again but it still stays at 0%. I tried doing it with the button you said not to click and running as admin.
Now i've got two problems, one is the phone not getting out of this mode and 2 is it not even giving me an error message meaning i can't try again since it's still busy restoring.
What can i do now? Should i just pull the plug out of it and try again? Will this not break anything?
What should i do now OP?
further info:
model: galaxy S3 GT-19300
i've had it rooted using CF-root and i did a firmware update to trigger emergency recovery mode.
I got into emergency recovery mode on purpose but expected to get out of it...
---------- Post added at 08:03 PM ---------- Previous post was at 07:10 PM ----------
Hooray! it's now actually installing it and i didn't mistake it for downloading this time. I switched USB ports and now it works apparently.
Also something people that do this in the future should know: if you unplug the cable, it just gives you the error message saying that it couldn't find it which shouldn't cause any trouble. BUT only do this once it is stuck at 0%.

Possibly stupid question..
Having rooted the Note 2 att with mr skips toolbox, I then noticed a few days later the modified status.. So due to concern for warranty being voided, I'd like to return to stock: ( Heres the stupid question part).. I did install stock recovery via same toolbox, But How do I tell if it is stock vs twrp? I dont see where/how to check if it succeeded. Next- Why wont factory reset work to clear the flash counter, modified status to normal with full wipe? and as much as I admire mr Cortex method to full wipe ( 10 min process..) is that repetitive process of wiping, triangle away,unroot, reroot etc..necessary? I had a rooted samsung epic 4g touch before this note 2 and All I did to return phone to stock firmware for trade in was factory reset! yes- it was Not jellybean, was Gingerbread android.
Perhaps someone or some devs can explain this bit of mystery to me, and perhaps others... who are in search of a more direct and straightforward reset without complicating the steps. I will probably reroot and run a custom rom after warranty runs out.. but for now..stock again.

Cannot do anything with Galaxy S3

I cannot root it, I cannot install any recovery besides the stock one that comes with it, I cannot get it to connect to the computer as mass storage, only as a media device.
Im thinking I just blew $215 on a paperweight.
I CANNOT EVEN INSTALL TITANIUM BACKUP TO GET RID OF THE FREAKING ATT CRAP!
What have I did wrong?
I have CWM v5.5.0.3!
Ive tried countless number of rooting programs including some poplular ones:
1. Casual - http://forum.xda-developers.com/showthread.php?t=2189536
2. Kingo Android ROOT - http://www.kingoapp.com/android-root.htm
3. Towelroot - https://towelroot.com/
4. CF Root (Flashed SU but does not work) - http://download.chainfire.eu/269/CF-Root/CF-Auto-Root/CF-Auto-Root-d2can-d2vl-sghi747m.zip
CF Root flashed Superuser but it says unfortunately Superuser has stopped.
Im about to take this back to the store I got it from....

Tell us your phone's specifics (firmware, modem, bootloader, is it AT&T or some other carrier). Does the phone work OK otherwise?
Do you have a ROM you want to try?

How are you flashing the recovery? Do you have Knox on your phone?

Model Number: Samsung-SGH-I747
OKAstro said:
Tell us your phone's specifics (firmware, modem, bootloader, is it AT&T or some other carrier). Does the phone work OK otherwise?
Do you have a ROM you want to try?
Click to expand...
Click to collapse
Its an [email protected] Phone with a new [email protected] sim card in it. The phone works on stock stuff. It will boot up just fine with CWM installed but I cannot actually go into CWM. It just gives me a black screen.
Android Version: 4.4.2
Baseband Version: I747UCUFNE4
Kernel Version
3.4.0-1514807
[email protected] #1
Mon May 19 21:00:05 KST 2014
Build number: KOT49H.I747UCUFNE4
SE for Android Status:
Enforcing
SEPF_SAMSUNG-SGH-I747_4.4.2_0016
Mon May 19 20:59:50 2014
It doesn't matter if I got a ROM or not. I cannot install a custom recovery.
audit13 said:
How are you flashing the recovery? Do you have Knox on your phone?
Click to expand...
Click to collapse
I am flashing Recovery thru Odin. Ive even tried different versions of Odin from 1.7 to 3.09. I prefer to use Odin 1.85.
And I have no clue what knox is or even if its installed.

Have you tried this thread?
http://forum.xda-developers.com/showthread.php?t=2789917

OKAstro said:
Have you tried this thread?
http://forum.xda-developers.com/showthread.php?t=2789917
Click to expand...
Click to collapse
Im not able to flash a working custom recovery.

mrnapolean1 said:
Im not able to flash a working custom recovery.
Click to expand...
Click to collapse
Well - maybe try flashing the stock 4.42 ROM again through Odin and then if that sticks, try the steps in the thread I linked
Good luck

OKAstro said:
Well - maybe try flashing the stock 4.42 ROM again through Odin and then if that sticks, try the steps in the thread I linked
Good luck
Click to expand...
Click to collapse
I had booted into download mode being about to flash CWM to my phone via Odin (Again) and I noticed this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(If you cannot see it it says):
Factory Mode
Product Name: SGH-I727
Current Binary: Custom
System Status: Custom
Qualcomm Secureboot: Enable
Warranty Bit 1
Bootloader AP Swrev: 3
Is this bad?
Am I still able to root?
Am I able to install custom Recovery?
Am I able to install ROMS like CM 11?

mrnapolean1 said:
I had booted into download mode being about to flash CWM to my phone via Odin (Again) and I noticed this:
(If you cannot see it it says):
Factory Mode
Product Name: SGH-I727
Current Binary: Custom
System Status: Custom
Qualcomm Secureboot: Enable
Warranty Bit 1
Bootloader AP Swrev: 3
Is this bad?
Am I still able to root?
Am I able to install custom Recovery?
Am I able to install ROMS like CM 11?
Click to expand...
Click to collapse
The fact that you can get to download mode is good. But sorry, what this means is out of my league. Try PM'ing "DocHoliday77". He seems to be a great resource for all things SGS3. He's in numerous threads in the Development forum
EDIT: I booted into download and mine says the exact same thing

You have Knox on your phone. You tripped the knox counter and changed the warranty bit to 1 which means the warranty on your phone has been voided.
When flashing a custom recovery phone in Odin, do not check auto reboot. When you see the word reset appear in the status window, remove the usb cable, pull the battery, and use the button combo to boot inter recovery.

audit13 said:
You have Knox on your phone. You tripped the knox counter and changed the warranty bit to 1 which means the warranty on your phone has been voided.
When flashing a custom recovery phone in Odin, do not check auto reboot. When you see the word reset appear in the status window, remove the usb cable, pull the battery, and use the button combo to boot inter recovery.
Click to expand...
Click to collapse
No still nothing.
It vibrates when you first start it up and then the Samsung logo comes up with Recovery is starting in blue at the top for about a second and then goes to a black screen and nothing never happens afterwards.
What is Knox by the way? Is this keeping my phone from being rooted?

Figured id post here now rather than having two threads going for the same problem.
The more this goes on though, the more i am suspecting some sort of hardware problem.
I want to suggest using the PIT file to repartition the device, but theres no firmware to use along side it. Theres a program here on xda called PIT Magic i think. I dont know much about it, but maybe it could help you to somehow repartition....?
As for knox, there is tons of info out there on it already,so i wont get into it here. It wont block you from rooting, but it can deny root access when an app requests it.

Will the pit wipe it?
Will installing cm 11 using the installer work? Does it work?

Yes, repartitioning will wipe your data.
I dont use CM roms so im not familiar with the installer. Sorry.

DocHoliday77 said:
Yes, repartitioning will wipe your data.
I dont use CM roms so im not familiar with the installer. Sorry.
Click to expand...
Click to collapse
My main thing is I want to root my unrootable SGS3 so I can remove the ATT crap.

Im out of ideas for you...sorry. I kinda think its probably a hardware issue. It sounds like youve done everything you can to get root or recovery. Might be wise to start looking into a motherboard replacement...and keep your backups up to date!

DocHoliday77 said:
Im out of ideas for you...sorry. I kinda think its probably a hardware issue. It sounds like youve done everything you can to get root or recovery. Might be wise to start looking into a motherboard replacement...and keep your backups up to date!
Click to expand...
Click to collapse
I just spent $215 on this. I don't think the place where I bought it from will ever take it back.

I wish i had something better for you to try. Sorry.
If you are willing and able to consider it, i saw several motherboards and devices with broken screens (but otherwise functional) go for less than $65 today. Its the best option i can think of now.

Where at?

Sorry. It was on ebay. They often will go for a bit more than that, but if you are patient you should be able to get one relatively cheap.
Just do not buy any that say no power. Just look at ones that are a good motherboard, or a device with a broken screen where they say it powers on, just with no display. Also make sure the IMEI is clean.
Good luck!

Firmware for SM-T807P

Would anyone happen to know where I can get the firmware for the Sprint variant of the Galaxy tab S 10.5? I have the "Firmware Upgrade Encountered an Error issue" after attempting to root with CF Auto Root. Kies 3 says it doesn't support the tablet, Sammobile doesn't have it and im pretty sure I don't want to contact Samsung quite yet. Thanks in advance.

Yes sammobile doesnt have firmware yet for snapdragon version

I just found out this tablet just came out to sprint. Which caused cf auto root to fail. Which could also mean it isn't on Sam mobile yet.

Is this a common thing? Does sammobile rarely get them for the Snapdragon variants?

Not sure, when the tab s wifi one came out there was already roms for them.

BDA_Rival said:
Would anyone happen to know where I can get the firmware for the Sprint variant of the Galaxy tab S 10.5? I have the "Firmware Upgrade Encountered an Error issue" after attempting to root with CF Auto Root. Kies 3 says it doesn't support the tablet, Sammobile doesn't have it and im pretty sure I don't want to contact Samsung quite yet. Thanks in advance.
Click to expand...
Click to collapse
well...since u have already tried the worse thing possible which is to flash a fule meant for an exynos device on a qualcom chipset then u might as well try this suggestion since it cant really make things worse at this point & just MIGHT actually work. Instead of using the our cfautoroot attempt to use the tab pro SM-T525 cfautoroot (link below)...i just saw that someone suggested that in another thread but dont know if u have had chance to try it yet. Also....as @edan1979 suggested chainfire is pretty good about creating new root packages if u can get him the files that he requests. If u do get this thing rooted with the file below then please pos back because i have a few files i need from your device if its not too much trouble...thx in advacnce
http://download.chainfire.eu/393/CF-Root/CF-Auto-Root/CF-Auto-Root-picassolte-picassoltexx-smt525.zip
^TAB 10.1 LTE SM-T525 CFAUTOROOT (same chipset except for screen...just might be the magic fix)
on a related note....i have aso been searching for the new qualcom/carrier branded firmware files & culdnt find them on sammobile either so if someone finds the one for sprint or the att/verizon version (SM-T707) then please let me know.
@DUHAsianSKILLZ
Just to be clear...i saw in the other thread that u said the wifi root method worked so i'm wondering what version of the device do u actually own?
@BDA_Rival
Thats actually why i suggested trying the other method...at this point your tablet could POTENTIALLY already be bricked & flashing the file i suggested is not only harmless but COULD even bring your tab back from the dead because theres no telling how long it will be before the firmware files are available. Worse case u can return it to sprint & say it failed during an over the air upgrade...i would definitely try the link i added NOT for the root but as an attempt to revive the tablet

I dont even care about root at this point, id rather have my tablet boot up to the stock OS. And I'd rather not fully brick it.

@THEDEVIOUS1 in the other thread I didn't know he had a sprint LTE tab s. I own a WiFi version of the tab s 10.5 inch. Sorry for any confusion.

THEDEVIOUS1 said:
Thats actually why i suggested trying the other method...at this point your tablet could POTENTIALLY already be bricked & flashing the file i suggested is not only harmless but COULD even bring your tab back from the dead because theres no telling how long it will be before the firmware files are available. Worse case u can return it to sprint & say it failed during an over the air upgrade...i would definitely try the link i added NOT for the root but as an attempt to revive the tablet
Click to expand...
Click to collapse
so i tried this because why not, already went to a service center and they acted like theyve never seen my issue. before i tried this, i had the binary status saying custom and the kox counter said 0. i flashed this, it was successful finally and my knox counter is at 1 which is fine. it tries to boot up unlike before but restarts saying "Could not normal boot" but i atleast see the splash screen. one question i guess i have is what would happen if i flashed the firmware for th the sm-t525? not that im seriously contemplating but if its the closest, chipset wise, would it work? i dont really care about cellular signal and if i brick it, im probably better off calling sprint with a completely bricked tablet that they wouldnt know was once rooted than one that says custom binary and the knox counter set off.

Well at least that's an improvement...the Odin firmware file will most likely NOT flash due to security checks so the only real hope u have right now is to try the 525 cwm or twrp and & see if it will boot into recovery. If it actually works then u could attempt one of their custom roms (would probably remove the boot.mg first) or maybe even cm11 for the tab pro (would have to delete the assert lines in the updater script so it would even flash). U can also try the a qualcom note 3 custom recovery (if they work will probably have resolution issues) or the 10.1 note 2014 ones which has the same chipset and resolution also

THEDEVIOUS1 said:
Well at least that's an improvement...the Odin firmware file will most likely NOT flash due to security checks so the only real hope u have right now is to try the 525 cwm or twrp and & see if it will boot into recovery. If it actually works then u could attempt one of their custom roms (would probably remove the boot.mg first) or maybe even cm11 for the tab pro (would have to delete the assert lines in the updater script so it would even flash). U can also try the a qualcom note 3 custom recovery (if they work will probably have resolution issues) or the 10.1 note 2014 ones which has the same chipset and resolution also
Click to expand...
Click to collapse
do radios matter though? would it brick because im flashing a verizon rom and those use different radios, or would it be better to flash a wifi rom? i dont really care if i have mobile data, i only use wifi. if i flash a 525 twrp, it wouldnt disable odin mode, would it?

BDA_Rival said:
do radios matter though? would it brick because im flashing a verizon rom and those use different radios, or would it be better to flash a wifi rom? i dont really care if i have mobile data, i only use wifi. if i flash a 525 twrp, it wouldnt disable odin mode, would it?
Click to expand...
Click to collapse
I'm assuming Odin mode & download mode are the same thing so the answer is yes IF it works u would be able to do the key combination and boot directly into recovery from Odin mode...I would NOT flash the radio although it shouldn't harm anything but what we really want right now is to leave as much of the original file system in place as possible & the only thing that technically should be different at this point is the recovery partition. The wifi versions are exynos devices so NO do NOT flash those because that's how we ended up here in the first place...just follow my last reply & since I don't like to waste posts if u respond needing more help just check back here for a mention of your username

THEDEVIOUS1 said:
I'm assuming Odin mode & download mode are the same thing so the answer is yes IF it works u would be able to do the key combination and boot directly into recovery from Odin mode...I would NOT flash the radio although it shouldn't harm anything but what we really want right now is to leave as much of the original file system in place as possible & the only thing that technically should be different at this point is the recovery partition. The wifi versions are exynos devices so NO do NOT flash those because that's how we ended up here in the first place...just follow my last reply & since I don't like to waste posts if u respond needing more help just check back here for a mention of your username
Click to expand...
Click to collapse
so im not sure i understood the last part of your message about wasting posts but i figured youd want to hear this. So i download the TWRP for the SM-P905 (note pro 12.2) and after i flashed it through odin, the tablet restarted and booted all the way up. I dont get how the hell this worked but flashing TWRP fixed my OS not booting. I also went to settings to check my device status and it says custom. i want to install super su but i dont know if TWRP stuck for sure or not and i cant get TWRP to boot, it keeps taking me to download mode. any ideas? id like to make a back up in case something dumb happens.
Edit: Got into recovery by holding home button, volume up button, and power but it says "Recovery booting, Recovery is not SEANDROID ENFORCING", not too sure what that means. heres the weird part. after it shows that, the screen starts turning gold within a matter of 15 seconds.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ever seen that before?

BDA_Rival said:
so im not sure i understood the last part of your message about wasting posts but i figured youd want to hear this. So i download the TWRP for the SM-P905 (note pro 12.2) and after i flashed it through odin, the tablet restarted and booted all the way up. I dont get how the hell this worked but flashing TWRP fixed my OS not booting. I also went to settings to check my device status and it says custom. i want to install super su but i dont know if TWRP stuck for sure or not and i cant get TWRP to boot, it keeps taking me to download mode. any ideas? id like to make a back up in case something dumb happens.
Click to expand...
Click to collapse
Sorry but the last part wasn't that serious...I just don't like to run my post count up. ok...that's great news which confirms what I thought since all the cf root really does is flash an altered stock recovery, install root then flash stock back. So...what I would try at this point is to go ahead & install supersu & hope that it detects the su file (it technically should) & if/when it requests u to upgrade the file choose NORMAL method NOT twrp/cwm which will attempt to finalize the root WITHOUT needing to boot into twrp. I would try to avoid that because even if it stuck there may be problems with the fact that it is from another device and will potentially screw the partitions up worse.....I know this is not the best bet for a backup but I would avoid recovery until u can find the proper Sprint Odin firmware for your device & instead just useb titanium to backup up your apps, system settings, & whatever else u can with it for the time being. At this point I would just be satisfied with the fact that u now have a working device & wait to do anything further until u get the correct software to fully fix it...well I'm glad u were able to get it going and IF u in fact have real root then can i get a HUGE favor? I need the keyguard.apk as well the framework-res.apk & twframework-res.apk with the corresponding odex files of course (i wouldn't mind having systemui & both framework jars if possible also)...if u can't do it , don't know how or it's just too much trouble then don't worry about it but i just thought I'd ask since I've been trying to find snap versions these files
@BDA_Rival
U edited your post before I could finish my reply but long story short just leave recovery alone for right now...what u are seeing is most likely due to the different types of screens between the 12.2 & 10.5 so the display driver is causing that problem. No problem on the assistance...that's were all supposed to be here for
Just thought I'd throw this out there since u seem to be able to find your way back home now but maybe if u try the cfautoroot for the P905 12.2 note pro then MAYBE that will root it...just thinking out loud though
http://forum.xda-developers.com/showthread.php?t=1980683&page=24
^NOTE PRO 12.2 LTE P905 CFAUTOROOT (see post #235...just in case u get the guts to try it again good luck)

THEDEVIOUS1 said:
Sorry but the last part wasn't that serious...I just don't like to run my post count up. ok...that's great news which confirms what I thought since all the cf root really does is flash an altered stock recovery, install root then flash stock back. So...what I would try at this point is to go ahead & install supersu & hope that it detects the su file (it technically should) & if/when it requests u to upgrade the file choose NORMAL method NOT twrp/cwm which will attempt to finalize the root WITHOUT needing to boot into twrp. I would try to avoid that because even if it stuck there may be problems with the fact that it is from another device and will potentially screw the partitions up worse.....I know this is not the best bet for a backup but I would avoid recovery until u can find the proper Sprint Odin firmware for your device & instead just useb titanium to backup up your apps, system settings, & whatever else u can with it for the time being. At this point I would just be satisfied with the fact that u now have a working device & wait to do anything further until u get the correct software to fully fix it...well I'm glad u were able to get it going and IF u in fact have real root then can i get a HUGE favor? I need the keyguard.apk as well the framework-res.apk & twframework-res.apk with the corresponding odex files of course (i wouldn't mind having systemui & both framework jars if possible also)...if u can't do it , don't know how or it's just too much trouble then don't worry about it but i just thought I'd ask since I've been trying to find snap versions these files
Click to expand...
Click to collapse
so i tried root checker, it said no root, i tried installing super su, said no root as well. i guess even though my device status says custom, im not actually rooted i went ahead and tried that CF Autoroot you suggested earlier in Odin and it gave me a boot loop so i flashed TWRP again and now its booting all the way. still says im not rooted so i just dont think its gonna work. If it did, i would have gotten that stuff for you for all your help. thanks for helping out.

Ota to won't take

I have been getting this phone up to date with out any computer at all ant have just been doing the ota updates so I can then root wit towelroot and the world I need opens from there
Look mm y phone downloads 4.3 goes to install restarts ans simply says install failed ummmmm.... what this is about I have no clue a little guidance would be great ppoint blank I will never have the option for computer for a long ass time

cmjester6421 said:
I have been getting this phone up to date with out any computer at all ant have just been doing the ota updates so I can then root wit towelroot and the world I need opens from there
Look mm y phone downloads 4.3 goes to install restarts ans simply says install failed ummmmm.... what this is about I have no clue a little guidance would be great ppoint blank I will never have the option for computer for a long ass time
Click to expand...
Click to collapse
Try using FlashFire, it's basically Odin for your phone. I think you have to join the Google+ Community to download it, but it works great.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Without root or anything that will work.... I kinda feel like that may not be the case another thing at one point a long time ago I changed my modstrings would that impede on the install with ota
Edit: ya flash fire won't work need root
Edit2: nvm the modsring is stock so I'm still at a total stop here

cmjester6421 said:
Without root or anything that will work.... I kinda feel like that may not be the case another thing at one point a long time ago I changed my modstrings would that impede on the install with ota
Edit: ya flash fire won't work need root
Edit2: nvm the modsring is stock so I'm still at a total stop here
Click to expand...
Click to collapse
Modstrings? What are you talking about?

cmjester6421 said:
I have been getting this phone up to date with out any computer at all ant have just been doing the ota updates so I can then root wit towelroot and the world I need opens from there
Look mm y phone downloads 4.3 goes to install restarts ans simply says install failed ummmmm.... what this is about I have no clue a little guidance would be great ppoint blank I will never have the option for computer for a long ass time
Click to expand...
Click to collapse
Once you update to the latest firmware, towelroot will not work. The exploit towelroot uses has been patched. And no one knows what you mean by "modstrings"

Well it don't work now anyway and forget the modstrings part I just need a way at this point to root and I cab roll with what I need to do worst case I have to go buy a new computer but I would rather not

cmjester6421 said:
I have been getting this phone up to date with out any computer at all ant have just been doing the ota updates so I can then root wit towelroot and the world I need opens from there
Look mm y phone downloads 4.3 goes to install restarts ans simply says install failed ummmmm.... what this is about I have no clue a little guidance would be great ppoint blank I will never have the option for computer for a long ass time
Click to expand...
Click to collapse
bilgerryan said:
Modstrings? What are you talking about?
Click to expand...
Click to collapse
madbat99 said:
Once you update to the latest firmware, towelroot will not work. The exploit towelroot uses has been patched. And no one knows what you mean by "modstrings"
Click to expand...
Click to collapse
This will help everyone understand what he means by modstrings...
https://towelroot.com/modstrings.html
This would make a great t-shirt!..."Modstrings? What are you talking about?"
Yes he is right the latest update patches the towelroot exploit. But you can still use another method without computer. But basically if you want your whole world to open up then you will not need that update. For example im running 5.1 lollipop on my gs3 so that ota update is not helping me at all. Rooting your stock rom opens a couple door in an old phone. But installing a custom rom, kernel, mod, framework, etc. will open every door. My gs3 outperforms my sisters gs6 in many ways and i had 5.1 update before she did. Amd i can always put my phone back to stock rom, unroot, and make it under warranty terms again because i made backup. But if you want slight upgrade i can help you troubleshoot the ota installation. But if not its ok because my wife has same phone and didnt update and she is running same custom rom, kernel, mod, framework, etc that i am with no problems.
Check out this thread i started last night as its related and has more info...
http://forum.xda-developers.com/galaxy-s3-sprint/help/samsung-galaxy-s3-lollipop-5-1-custom-t3162496
Let me know what u decide to do

I'm doing full mods to this phone I had a s6 I really don't like it look as I said I don't have a computer I need the fastest path to getting cwm once I have the rom I want I can go fron there howevrr the fine tuning help would be a big plus from you if I evrr get this done lol the plan is to get cm 12.1 and go as far as I can to make this bettrr then the s6 please let me jnow where I need to go fron here

cmjester6421 said:
I'm doing full mods to this phone I had a s6 I really don't like it look as I said I don't have a computer I need the fastest path to getting cwm once I have the rom I want I can go fron there howevrr the fine tuning help would be a big plus from you if I evrr get this done lol the plan is to get cm 12.1 and go as far as I can to make this bettrr then the s6 please let me jnow where I need to go fron here
Click to expand...
Click to collapse
Fastest path to cwm is rooting your phone using towelroot or cf autoroot then install root checker app to verify root and then install app supersu and then install app called rommanager from app store and update the recovery in the app. Should only take a few minutes plus reboot time. No computer needed. Forget about the ota upgrade for now since you want cm12.1. Once cwm running do a nandroid backup so you have a stock rom image before doing anything else. Later you can revert back to the moment after you rooted if you run into any problems and try again, try ota update again, or unroot and get it back to warrantied state. Before updating to custom rom check out my new thread to get some ideas on what to back up to save your important data and other ideas. Yes i can help you furthur just message me anytime or ask in my thread..
http://forum.xda-developers.com/galaxy-s3-sprint/help/samsung-galaxy-s3-lollipop-5-1-custom-t3162496

Cf needs a computer right? And as for towel root I have ran it many times it says it worjed but su won't install....

cmjester6421 said:
Cf needs a computer right? And as for towel root I have ran it many times it says it worjed but su won't install....
Click to expand...
Click to collapse
My fault. I meant framaroot. Try this i think this is what i had to use from xda..
http://forum.xda-developers.com/apps/framaroot/root-framaroot-one-click-apk-to-root-t2130276
The towelroot saying success is throwing me off. I will try to find out info on that. Did you use root checker app to verify root or no root? My first root i thought nothing happened at first. Let me know

Error 7 first exploit and error 9 secong exploit.... as for towel root years ago I paid for root checker advanced I know better its not rooted I have done factory resets and tried again I'm running 4.1.2 this is stock from a ota a long time ago I know you have no reason to hekp but if you can get me in the right place to make this work you save me a grand plus if I'm getting a new pc its asus gaming level what I had was 6k I won't take much less please let me know what you find I have been reserching for the last six hours.... no luck

Thanks to zip addict he found me king root and I looked in to it the 4.5 version I git root no pc all is needed after that is super sume from what he told me so that you can install the right super user and move on to a recovery now at this time I'm trying to find a dl for super sume that is not the play store as it says not compatible