[Q] Unrooted, partially rooted purgatory? Please help!!! - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

Background:
I had my Galaxy S3 rooted on 4.0.4 ICS with no problems for several months, however when I wanted to upgrade to 4.1 Jellybean via OTA I quickly learned that the OTA update won't work on a rooted OS. I installed an called Voodoo OTA which claimed to be able to temporarily unroot you device so you can get the OTA Jellybean update. It failed, did not accomplish what it claimed to be able to do, however what it did do was patially unroot my phone to a state that it can neither be unrooted fully or re-rooted back to a full rooted state. I did a full clean wipe and factory reset and I am still in the same position. I have used the Android Toolkit for S3 to flash it back to factory state it just hangs in ODIN at the boot.img, I have attempted to root and un-root with the Android Toolkit multiple methods and .tar files, nothing, just hangs when it gets to the imaging part.
The phone is fully functional, but I feel imprisoned by the phone now as it operates like an unrooted phone, but I can't upgrade it.
Can anyone help me out of this, even to just get back to a rooted phone.
Thank you to anyone and everyone for your advice!

I will donate to any developer that can get my phone back to working order!
bigmtnskier said:
Background:
I had my Galaxy S3 rooted on 4.0.4 ICS with no problems for several months, however when I wanted to upgrade to 4.1 Jellybean via OTA I quickly learned that the OTA update won't work on a rooted OS. I installed an called Voodoo OTA which claimed to be able to temporarily unroot you device so you can get the OTA Jellybean update. It failed, did not accomplish what it claimed to be able to do, however what it did do was patially unroot my phone to a state that it can neither be unrooted fully or re-rooted back to a full rooted state. I did a full clean wipe and factory reset and I am still in the same position. I have used the Android Toolkit for S3 to flash it back to factory state it just hangs in ODIN at the boot.img, I have attempted to root and un-root with the Android Toolkit multiple methods and .tar files, nothing, just hangs when it gets to the imaging part.
The phone is fully functional, but I feel imprisoned by the phone now as it operates like an unrooted phone, but I can't upgrade it.
Can anyone help me out of this, even to just get back to a rooted phone.
Thank you to anyone and everyone for your advice!
Click to expand...
Click to collapse
I am desperate at this point , I have spent 2 almost 3 days trying to get my phone back to stock or rooted state. I have scoured Google, XDA and other Android phones. If anyone wants to volunteer and help me on or offline I will gladly donate generously.

I'd recommend forgetting about that tool kit for now. You should download the latest version of Odin v3.07, twrp recovery (tar file), and supersu.zip, and try doing everything manually; flash twrp through PDA from Odin, and supersu.zip through Twrp recovery if you get that far. The files are easy to find, so I'm not going to post links just yet.
Sent from my SAMSUNG-SGH-I747 using xda premium

shortydoggg said:
I'd recommend forgetting about that tool kit for now. You should download the latest version of Odin v3.07, twrp recovery (tar file), and supersu.zip, and try doing everything manually; flash twrp through PDA from Odin, and supersu.zip through Twrp recovery if you get that far. The files are easy to find, so I'm not going to post links just yet.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
:good:thank you, I will give it a go and try it as you describe.

Fixed after almost 3 days!!!!
shortydoggg said:
I'd recommend forgetting about that tool kit for now. You should download the latest version of Odin v3.07, twrp recovery (tar file), and supersu.zip, and try doing everything manually; flash twrp through PDA from Odin, and supersu.zip through Twrp recovery if you get that far. The files are easy to find, so I'm not going to post links just yet.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
:laugh:FIXED!!!!!!!!!!!!!!!!!!!!!!!
I did what you said, but only after I figured out that I was using the wrong driver, correct device, wrong model. I used a USB driver cleaner, cleaned them all off, wiped the device, installed the driver and reconnected then I followed your instructions!:good:
I found these instructions on the AT&T Samsung forum for how to clean your drivers:
http://forums.att.com/t5/Android-Di...ix-for-Windows-7-at-least-for-me/td-p/3369515
Samsung Galaxy S3 MTP USB Fix for Windows 7(at least for me)!!
Post Options
‎11-30-2012 02:55:21 PM
Here's what worked for me after literally trying everything under the sun (compiled steps from various sources):
Steps to Safely Cleanup and Remove old USB Mass Storage Drivers on your PC
Shut down your computer. Unplug your USB storage devices: USB Disks, flash, cams, CD/DVD, etc.
==> Other USB devices like keyboards, mice and LAN adapters can stay plugged in
Boot computer back up. Click for how to determine whether you are running 32 or 64 bit Windows
Download drivecleanup.zip, unzip and save to your desktop. Move the 32 or 64 bit version of DriveCleanup.exe toC:\Windows\System32
Open a command prompt window as follows:
==> For XP only: You must have Admin privileges. Click Start->Run, enter cmd
==> For Vista and Windows 7: You must open an elevated command prompt window!
After the command prompt enter: drivecleanup.exe
==> Your command prompt window should be similar to my example below.
==> If, instead, you get an error message like Command not recognized it means you didn't move Drivecleanup.exe to the right directory
Reboot.
Download the latest USB drivers here:http://www.samsung.com/us/support/owners/product/SGH-I747MBBATT Click the tab at the bottom that says "Manuals & Downloads" then Software then the link for the Device(Install),USB Driver (Software) (ver.v1.5.14.0)
Intstall Drivers
Reboot
Unplugged or disable your internet connection ***CRITICAL***
On your S3 go to Settings>About device>Check for updates and install the update (eventhough we next do a hard reset the new firmware is worth it if only for the brightness feature added to the notification drop down).
Do a hard reset on your Galaxy S3 instructions for that here: http://www.hard-reset.com/samsung-galaxy-s3-hard-reset.html
Turn on S3 (without USB plugged in) and don't login to your Android account ***CRITICAL***
Plug in USB and it should install all the drivers at long last ***SIGH***
Login to your Android account with the USB plugged in and you should be good to go!
Thanks again for helping me out!

my android is partially rooted or partially unrooted
Before three days I was think to update my android.so I done to unroot my android.after update my device is not root again.it says failed again and again.i also try to unroot again but this is also says that root required first.how can I do.i want to root again.please help me.:crying:

Related

[Q] Root Galaxy Note 2 N7100 Running Android 4.3 Jelly Bean [How to]

Samsung's second generation Galaxy Note has recently received latest Jelly Bean software version, Android 4.3. The update is released for both HSPA+ and LTE variants of the handset bearing model number GT-N7100 and GT-N7105.
The new stock build of Android 4.3 carries a host of new features including improved UI, new Keyboard, Samsung Knox and Samsung Wallet.
Users can grab the Android 4.3 update by connecting the Galaxy Note 2 to the computer and use Samsung KIES or use OTA (Over-The-Air) service. Navigate to Settings>> More>> About device>> Software update>> Update to download and install the official build via OTA.
Click here for our step-by-step guide to install official XXUEMK4 Android 4.3 update on Galaxy Note 2 N7100.
Those who have already installed Android 4.3 on the Galaxy Note 2 N7100 and currently looking for a root method may follow our step-by-step guide. The tutorial uses CF-Auto-Root file by recognised XDA developer, Chainfire. As the CF-Auto-Root is firmware independent, it supports Android 4.3 and future firmware as well. The root file has SuperSU binary and APK with stock recovery installed. Besides, it is for those who wish to keep as close to stock as possible. Head over to the development thread to learn more about the root file.
IBTimes UK reminds its readers that it will not be held liable for any mishap. Users area also advised to verify that their devices meet following requirements.
Pre-requisites
1) Install USB Driver for Samsung Galaxy Note 2 to transfer files between the Android device and the computer.
2) Enable USB Debugging Mode on phone to connect it with computer and use Android SDK with it. [Head over to Settings>> Developer Options]
3) As the tutorial might wipe out all data of the phone, create a backup. If the device is having any custom recoveries such as ClockworkMod/TWRP already installed, backup data using the recovery.
4) If the Android phone powers off due to lack of battery while the installation process, it could damage the device. Therefore, the Note 2 should have charge above 80% battery charge.
5) The phone should be factory unlocked and not locked to any particular carrier.
6) The device will lose manufacturer's warranty once it is rooted.
7) The CF-Auto-Root files work only on Samsung Galaxy Note 2 GT-N7100. As applying these on any incorrect variant might brick the device, verify the model number of Galaxy Note 2 by navigating to Settings>> About phone>> Model number.
Steps to root Samsung Galaxy Note 2 GT-N7100 on Android 4.3 Jelly Bean
Step-1: Download CF-Auto-Root file for Galaxy Note 2 to computer
File name: CF-Auto-Root-t03g-t03gxx-gtn7100.zip
Step-2: Extract the downloaded root zip using Winzip/7zip/winrar or any other extracting tool to get CF-Auto-Root-t03g-t03gxx-gtn7100.tar.md5 file
Step-3: Download Odin3_v3.07. Extract Odin zip to get Odin3 v3.07.exe file
Step-4: Turn off Galaxy Note 2
Step-5: Place the phone into Download Mode by pressing and holding Volume Down, Home and Power buttons together until the construction Android robot icon with a warning triangle appears on the phone's screen. Then press the Volume Up button to continue to enter Download Mode
Step-6: Run Odin3 v3.07.exe as Administrator
Step-7: Connect the phone to the computer using USB cable while it is in Download Mode. Wait for some time until Odin detects the device. When the phone is connected successfully, an Added message will appear under Odin message box. Additionally, the ID: COM box in Odin will turn blue with the COM port number indicating successful connection
Note: If the Added message does not appear then try another USB port, try the one located at the back side of the computer. In case Odin still fails to recognise the device then reinstall USB driver.
Step-8: In Odin, click the PDA button and select CF-Auto-Root-t03g-t03gxx-gtn7100.tar.md5 which was extracted earlier
Step-9: Verify Auto-Reboot and F.Reset Time checkboxes are selected in Odin
Step-10: Finally click the Start button in Odin. The installation process should begin now and take few minutes to complete
Step-11: After the installation process is completed, the phone will restart and soon a PASS message with green background in the extreme left box at the very top of Odin. Unplug the USB cable from the phone to disconnect it from computer
As the Galaxy Note 2 boots up, it should be rooted successfully on Android 4.3 firmware. You may install any app that requires root permission. To verify the root status of the device download Root Checker app from Google Play Store.
Note:
Sometimes the device does not boot into Recovery Mode and root the device. If this happens then perform the entire procedure again. If it still does not install root, ensure Auto Reboot checkbox in Odin is not checked. Then after flashing the root package, pull out the battery and boot the phone into Recovery mode by selecting Volume Up, Home and Power buttons together. This will start the install process.
The "CF-Auto-Root-t03g-t03gxx-gtn7100.zip" is corrupted. Can you upload again? TQ.
mohammedaminewardy said:
Samsung's second generation Galaxy Note has recently received latest Jelly Bean software version, Android 4.3. The update is released for both HSPA+ and LTE variants of the handset bearing model number GT-N7100 and GT-N7105.
The new stock build of Android 4.3 carries a host of new features including improved UI, new Keyboard, Samsung Knox and Samsung Wallet.
Users can grab the Android 4.3 update by connecting the Galaxy Note 2 to the computer and use Samsung KIES or use OTA (Over-The-Air) service. Navigate to Settings>> More>> About device>> Software update>> Update to download and install the official build via OTA.
Click here for our step-by-step guide to install official XXUEMK4 Android 4.3 update on Galaxy Note 2 N7100.
Those who have already installed Android 4.3 on the Galaxy Note 2 N7100 and currently looking for a root method may follow our step-by-step guide. The tutorial uses CF-Auto-Root file by recognised XDA developer, Chainfire. As the CF-Auto-Root is firmware independent, it supports Android 4.3 and future firmware as well. The root file has SuperSU binary and APK with stock recovery installed. Besides, it is for those who wish to keep as close to stock as possible. Head over to the development thread to learn more about the root file.
IBTimes UK reminds its readers that it will not be held liable for any mishap. Users area also advised to verify that their devices meet following requirements.
Pre-requisites
1) Install USB Driver for Samsung Galaxy Note 2 to transfer files between the Android device and the computer.
2) Enable USB Debugging Mode on phone to connect it with computer and use Android SDK with it. [Head over to Settings>> Developer Options]
3) As the tutorial might wipe out all data of the phone, create a backup. If the device is having any custom recoveries such as ClockworkMod/TWRP already installed, backup data using the recovery.
4) If the Android phone powers off due to lack of battery while the installation process, it could damage the device. Therefore, the Note 2 should have charge above 80% battery charge.
5) The phone should be factory unlocked and not locked to any particular carrier.
6) The device will lose manufacturer's warranty once it is rooted.
7) The CF-Auto-Root files work only on Samsung Galaxy Note 2 GT-N7100. As applying these on any incorrect variant might brick the device, verify the model number of Galaxy Note 2 by navigating to Settings>> About phone>> Model number.
Steps to root Samsung Galaxy Note 2 GT-N7100 on Android 4.3 Jelly Bean
Step-1: Download CF-Auto-Root file for Galaxy Note 2 to computer
File name: CF-Auto-Root-t03g-t03gxx-gtn7100.zip
Step-2: Extract the downloaded root zip using Winzip/7zip/winrar or any other extracting tool to get CF-Auto-Root-t03g-t03gxx-gtn7100.tar.md5 file
Step-3: Download Odin3_v3.07. Extract Odin zip to get Odin3 v3.07.exe file
Step-4: Turn off Galaxy Note 2
Step-5: Place the phone into Download Mode by pressing and holding Volume Down, Home and Power buttons together until the construction Android robot icon with a warning triangle appears on the phone's screen. Then press the Volume Up button to continue to enter Download Mode
Step-6: Run Odin3 v3.07.exe as Administrator
Step-7: Connect the phone to the computer using USB cable while it is in Download Mode. Wait for some time until Odin detects the device. When the phone is connected successfully, an Added message will appear under Odin message box. Additionally, the ID: COM box in Odin will turn blue with the COM port number indicating successful connection
Note: If the Added message does not appear then try another USB port, try the one located at the back side of the computer. In case Odin still fails to recognise the device then reinstall USB driver.
Step-8: In Odin, click the PDA button and select CF-Auto-Root-t03g-t03gxx-gtn7100.tar.md5 which was extracted earlier
Step-9: Verify Auto-Reboot and F.Reset Time checkboxes are selected in Odin
Step-10: Finally click the Start button in Odin. The installation process should begin now and take few minutes to complete
Step-11: After the installation process is completed, the phone will restart and soon a PASS message with green background in the extreme left box at the very top of Odin. Unplug the USB cable from the phone to disconnect it from computer
As the Galaxy Note 2 boots up, it should be rooted successfully on Android 4.3 firmware. You may install any app that requires root permission. To verify the root status of the device download Root Checker app from Google Play Store.
Note:
Sometimes the device does not boot into Recovery Mode and root the device. If this happens then perform the entire procedure again. If it still does not install root, ensure Auto Reboot checkbox in Odin is not checked. Then after flashing the root package, pull out the battery and boot the phone into Recovery mode by selecting Volume Up, Home and Power buttons together. This will start the install process.
Click to expand...
Click to collapse
xbean said:
The "CF-Auto-Root-t03g-t03gxx-gtn7100.zip" is corrupted. Can you upload again? TQ.
Click to expand...
Click to collapse
it is.
kindly re-upload.
link is ok
NaAZoOR said:
it is.
kindly re-upload.
Click to expand...
Click to collapse
now is ok :good:
Correct link
the correct link
http : // download.chainfire.eu/264/CF-Root/CF-Auto-Root/CF-Auto-Root-t03g-t03gxx-gtn7100.zip
:good:
Unfortunately, SuperSU has stopped
mohammedaminewardy said:
Samsung's second generation Galaxy Note has recently received latest Jelly Bean software version, Android 4.3. The update is released for both HSPA+ and LTE variants of the handset bearing model number GT-N7100 and GT-N7105.
The new stock build of Android 4.3 carries a host of new features including improved UI, new Keyboard, Samsung Knox and Samsung Wallet.
Users can grab the Android 4.3 update by connecting the Galaxy Note 2 to the computer and use Samsung KIES or use OTA (Over-The-Air) service. Navigate to Settings>> More>> About device>> Software update>> Update to download and install the official build via OTA.
Click here for our step-by-step guide to install official XXUEMK4 Android 4.3 update on Galaxy Note 2 N7100.
Those who have already installed Android 4.3 on the Galaxy Note 2 N7100 and currently looking for a root method may follow our step-by-step guide. The tutorial uses CF-Auto-Root file by recognised XDA developer, Chainfire. As the CF-Auto-Root is firmware independent, it supports Android 4.3 and future firmware as well. The root file has SuperSU binary and APK with stock recovery installed. Besides, it is for those who wish to keep as close to stock as possible. Head over to the development thread to learn more about the root file.
IBTimes UK reminds its readers that it will not be held liable for any mishap. Users area also advised to verify that their devices meet following requirements.
Pre-requisites
1) Install USB Driver for Samsung Galaxy Note 2 to transfer files between the Android device and the computer.
2) Enable USB Debugging Mode on phone to connect it with computer and use Android SDK with it. [Head over to Settings>> Developer Options]
3) As the tutorial might wipe out all data of the phone, create a backup. If the device is having any custom recoveries such as ClockworkMod/TWRP already installed, backup data using the recovery.
4) If the Android phone powers off due to lack of battery while the installation process, it could damage the device. Therefore, the Note 2 should have charge above 80% battery charge.
5) The phone should be factory unlocked and not locked to any particular carrier.
6) The device will lose manufacturer's warranty once it is rooted.
7) The CF-Auto-Root files work only on Samsung Galaxy Note 2 GT-N7100. As applying these on any incorrect variant might brick the device, verify the model number of Galaxy Note 2 by navigating to Settings>> About phone>> Model number.
Steps to root Samsung Galaxy Note 2 GT-N7100 on Android 4.3 Jelly Bean
Step-1: Download CF-Auto-Root file for Galaxy Note 2 to computer
File name: CF-Auto-Root-t03g-t03gxx-gtn7100.zip
Step-2: Extract the downloaded root zip using Winzip/7zip/winrar or any other extracting tool to get CF-Auto-Root-t03g-t03gxx-gtn7100.tar.md5 file
Step-3: Download Odin3_v3.07. Extract Odin zip to get Odin3 v3.07.exe file
Step-4: Turn off Galaxy Note 2
Step-5: Place the phone into Download Mode by pressing and holding Volume Down, Home and Power buttons together until the construction Android robot icon with a warning triangle appears on the phone's screen. Then press the Volume Up button to continue to enter Download Mode
Step-6: Run Odin3 v3.07.exe as Administrator
Step-7: Connect the phone to the computer using USB cable while it is in Download Mode. Wait for some time until Odin detects the device. When the phone is connected successfully, an Added message will appear under Odin message box. Additionally, the ID: COM box in Odin will turn blue with the COM port number indicating successful connection
Note: If the Added message does not appear then try another USB port, try the one located at the back side of the computer. In case Odin still fails to recognise the device then reinstall USB driver.
Step-8: In Odin, click the PDA button and select CF-Auto-Root-t03g-t03gxx-gtn7100.tar.md5 which was extracted earlier
Step-9: Verify Auto-Reboot and F.Reset Time checkboxes are selected in Odin
Step-10: Finally click the Start button in Odin. The installation process should begin now and take few minutes to complete
Step-11: After the installation process is completed, the phone will restart and soon a PASS message with green background in the extreme left box at the very top of Odin. Unplug the USB cable from the phone to disconnect it from computer
As the Galaxy Note 2 boots up, it should be rooted successfully on Android 4.3 firmware. You may install any app that requires root permission. To verify the root status of the device download Root Checker app from Google Play Store.
Note:
Sometimes the device does not boot into Recovery Mode and root the device. If this happens then perform the entire procedure again. If it still does not install root, ensure Auto Reboot checkbox in Odin is not checked. Then after flashing the root package, pull out the battery and boot the phone into Recovery mode by selecting Volume Up, Home and Power buttons together. This will start the install process.
Click to expand...
Click to collapse
I succesfully rooted my mobile, it it shows this message "Unfortunately, SuperSU has stopped" every time i reboot the mobile, can u please help resolving this issue?
Though i rooted my samsung galaxy note 2 GT-7100 as you say.I keep getting a "Unfortunately, SuperSU has stopped" error. Can someone please help? also cant install rooted apps.What should i do in such case?
super user corret file
anirudh56 said:
Though i rooted my samsung galaxy note 2 GT-7100 as you say.I keep getting a "Unfortunately, SuperSU has stopped" error. Can someone please help? also cant install rooted apps.What should i do in such case?
Click to expand...
Click to collapse
Sorry you can replace it by this file in attachment
Hey can anyone using Galaxy Note 2 GT-N7100 confirm whether the procedure worked successfully?
Supersu
mohammedaminewardy said:
Sorry you can replace it by this file in attachment
Click to expand...
Click to collapse
I'm getting the same Supersu has stopped message. When I try to install with this replacement it says application not installed. Been trying to get past this error message for several days now! What else can I try?!
It worked !
Crysis32013 said:
Hey can anyone using Galaxy Note 2 GT-N7100 confirm whether the procedure worked successfully?
Click to expand...
Click to collapse
Yes it worked perfectly.. I got the SU error and knox pop ups too, but somehow Superuser updated automatically and everything works now ! (i tested root checker --> positive ) amd gamekiller works also
---------- Post added at 04:33 PM ---------- Previous post was at 04:25 PM ----------
s.rolx said:
I'm getting the same Supersu has stopped message. When I try to install with this replacement it says application not installed. Been trying to get past this error message for several days now! What else can I try?!
Click to expand...
Click to collapse
Yo bro I had the same problem.. somehow SU updated and now everything works.. (update su) hit the Tanks button plz
Mine updated but when I go to Setting>>about Device, it's still on 4.1.2
Marc_ab98 said:
Yes it worked perfectly.. I got the SU error and knox pop ups too, but somehow Superuser updated automatically and everything works now ! (i tested root checker --> positive ) amd gamekiller works also
---------- Post added at 04:33 PM ---------- Previous post was at 04:25 PM ----------
Yo bro I had the same problem.. somehow SU updated and now everything works.. (update su) hit the Tanks button plz
Click to expand...
Click to collapse
Mine updated but when I go to Setting>>about Device, it's still on 4.1.2
Perfectly worked...
mohammedaminewardy said:
Sorry you can replace it by this file in attachment
Click to expand...
Click to collapse
I have the same problem. But Root Checker also says my phone is not rooted?
I get a Security Notice, saying Unauthorized access to a secured area has been blocked. - Help?
same problem
rossfen said:
I have the same problem. But Root Checker also says my phone is not rooted?
I get a Security Notice, saying Unauthorized access to a secured area has been blocked. - Help?
Click to expand...
Click to collapse
+1 same problem!!!!!
thank u
Don't worry guys i face the same problem at first"super has stopped". What you have to do is go to PLAY STORE and search SuperSU and not super user. when u see superSU then press update,then after updating it will ask you to grant permission to superSU press GRANT, and also when it ask you to stop samsung knox press OK,congrats your phone is rooted
Hey guys Why isn't freedom apk and gamekiller Working anymore? Im rooted
Sent from my GT-N7100 using Tapatalk
s.rolx said:
I'm getting the same Supersu has stopped message. When I try to install with this replacement it says application not installed. Been trying to get past this error message for several days now! What else can I try?!
Click to expand...
Click to collapse
Even i was not able to root my GN2 through cf auto root on 4.3..so i flashed philz recovery..then through that i installed Dr. ketan multitool..there are option in steps to root..and after that reboot your phone..go to SuperSU app in app drawer..install custom binaries..it worked for me..do try..!!
Sorry if this was asked before guys, but im totally new whit this phone.
My question is ¿what happend if i follow this method if mi N7100 its not unlocked?
My carrier its Telcel
And really sorry for my english, i know isnt good
My Root Problem Solve
I can confirm that this way able to root my N7100. I'm using latest official stock rom so Knox disable SuperSu. To be clear, here's step that I do.
1. Using N7100XXUENB2_N7100OLBENB1_THL (country Thailand)
2. At first, flash cf auto root - after reboot, SuperSu fail to load (disable by Knox)
3. Flash philz recovery - auto reboot
4. Power off then enter philz recovery back
5. From there, install Dr.Ketan multitool - it will auto running then...
6. Choose "Root Inject"
7. Choose "Busybox Inject"
8. For all others page, I just choose "Do Not Change" until the end of page. The last one will reboot phone automatically.
9. After reboot, SuperSu will still fail to load.
10. Go to Play Store, search for SuperSu. There's an option to "Update" (before, only Open available). Update it.
11. After that, SuperSu can be open and running already through apps drawer.
I have ROM Toolbox apps, so the first thing I do is to disable Knox from App Manager option. But it's call KLMS Agent ver 1.5 (please correct me if I'm wrong).
Thanks to iprabhsingh hint... :highfive:
iprabhsingh said:
Even i was not able to root my GN2 through cf auto root on 4.3..so i flashed philz recovery..then through that i installed Dr. ketan multitool..there are option in steps to root..and after that reboot your phone..go to SuperSU app in app drawer..install custom binaries..it worked for me..do try..!!
Click to expand...
Click to collapse

[Q] Bricked Note 2?

First and foremost, thank you for any help and advise at all.
Had 4.3 ota.... Flashed cwm thru odin. Restarted the phone, it will not boot past the "samsung galaxy note 2" screen. Flashed stock rom thru odin, still stuck at the samsung note 2 screen. I can get into download mode with no issues whatsoever. I cannot get into recovery mode, whether stock or cwm. Nothing. Can I flash another 4.3 or 4.4 rom thru odin? I just need my phone working again..... thanks gentlemen
Also, I have tried flashing back to stock with odin, I have tried flashing to and earlier version with odin. Nothing. As stated above, I can get into download mode. I cannot get into recovery of any kind. Also, I have no idea how to enter emergency recovery mode to try and restore with kies...... I am lost and have a paper weight as of now thanks again guys
http://forum.xda-developers.com/showthread.php?t=2581321
This is the only known method so far and it is not working for everyone but at this point I'd say it is your best and only hope.
Did you thank your Developer today?
Thanks.... Tried that but nothing still samsung note 2 screen only...... Downloading newest odin and a 4.3 stock rom, we shall see......
solomon316 said:
Thanks.... Tried that but nothing still samsung note 2 screen only...... Downloading newest odin and a 4.3 stock rom, we shall see......
Click to expand...
Click to collapse
Where I can get those 4.3 stock and odin?
https://mega.co.nz/#!bg4QVLqI!H-nB_jZlsStgzcF4POd432atbOVHwkzrOPIeHQPOQUQ
Ok, guys, finally made some if little progress..... got the phone into kies firmware recovery mode........ now, I'm still waiting for kies to recognize my note 2 been connecting for 5 minutes now...... If it would just see the phone I could do the emergency recover (HOPEFULLY) and waiting.......
And still waiting for kies to connect to my note 2.......
solomon316 said:
And still waiting for kies to connect to my note 2.......
Click to expand...
Click to collapse
It wont connect!! Stop wasting your time.... I've been there.......................
Rooted 4.3 OTA?
solomon316 said:
First and foremost, thank you for any help and advise at all.
Had 4.3 ota.... Flashed cwm thru odin. Restarted the phone, it will not boot past the "samsung galaxy note 2" screen. Flashed stock rom thru odin, still stuck at the samsung note 2 screen. I can get into download mode with no issues whatsoever. I cannot get into recovery mode, whether stock or cwm. Nothing. Can I flash another 4.3 or 4.4 rom thru odin? I just need my phone working again..... thanks gentlemen
Click to expand...
Click to collapse
Was your 4.3 OTA rooted before you flashed CWM?
I'm having similar issues. Stuck on the Note II screen, and no recovery. I have only ever had stock recovery. I can get into download mode, but ven after using Odin to get back to stock, I have the same issue. I assume this has something to do with the boot loader. Does anyone have a fix for this?
Use Kies to emergency recover back to stock 4.1.1.
Steps. (READ ALL BEFORE STARTING)
1.) Downloads Kies onto your pc
2.) Install drivers to pic
3.) Open Kies and go to TOOLS > instal/upgrade firmware.
4.) Kies will ask you for you device model. AT&T = SHE I317. And your serial number. Located behind the battery.
5.) Hit start in Kies it will down load the stock firmware to your PC. Follow the instructions.
6.) It will eventually ask you to put your phone in download mode and connect it to the pc. Do this.
7.) Don't touch it. It is going to take about 10-20 min depending on your Internet speed and your computer.
When it is complete your phone will be back to stock. The same it was the day you pulled it out of the box.
***I would also make sure you back up any data on your phone because it will delete the sd card. It is also wise to remove any external storage sd.
****when finished you can re root using cf auto root or take the OTA update to get you back to 4.3.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
ShrekOpher said:
Use Kies to emergency recover back to stock 4.1.1.
Steps. (READ ALL BEFORE STARTING)
1.) Downloads Kies onto your pc
2.) Install drivers to pic
3.) Open Kies and go to TOOLS > instal/upgrade firmware.
4.) Kies will ask you for you device model. AT&T = SHE I317. And your serial number. Located behind the battery.
5.) Hit start in Kies it will down load the stock firmware to your PC. Follow the instructions.
6.) It will eventually ask you to put your phone in download mode and connect it to the pc. Do this.
7.) Don't touch it. It is going to take about 10-20 min depending on your Internet speed and your computer.
When it is complete your phone will be back to stock. The same it was the day you pulled it out of the box.
***I would also make sure you back up any data on your phone because it will delete the sd card. It is also wise to remove any external storage sd.
****when finished you can re root using cf auto root or take the OTA update to get you back to 4.3.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
Kies doesnt work. It does the whole process and then fails with an error message and put the phone in emergency recovery mode but does not give you a recovery code.
What is the error you get in Kies?
If you are using Kies correctly it should work. It is designed to completely restore your phone.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
ShrekOpher said:
Use Kies to emergency recover back to stock 4.1.1.
Steps. (READ ALL BEFORE STARTING)
1.) Downloads Kies onto your pc
2.) Install drivers to pic
3.) Open Kies and go to TOOLS > instal/upgrade firmware.
4.) Kies will ask you for you device model. AT&T = SHE I317. And your serial number. Located behind the battery.
5.) Hit start in Kies it will down load the stock firmware to your PC. Follow the instructions.
6.) It will eventually ask you to put your phone in download mode and connect it to the pc. Do this.
7.) Don't touch it. It is going to take about 10-20 min depending on your Internet speed and your computer.
When it is complete your phone will be back to stock. The same it was the day you pulled it out of the box.
***I would also make sure you back up any data on your phone because it will delete the sd card. It is also wise to remove any external storage sd.
****when finished you can re root using cf auto root or take the OTA update to get you back to 4.3.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
It does not take my phone model number "sgh i317".
---------- Post added at 10:29 AM ---------- Previous post was at 09:34 AM ----------
ShrekOpher said:
Use Kies to emergency recover back to stock 4.1.1.
Steps. (READ ALL BEFORE STARTING)
1.) Downloads Kies onto your pc
2.) Install drivers to pic
3.) Open Kies and go to TOOLS > instal/upgrade firmware.
4.) Kies will ask you for you device model. AT&T = SHE I317. And your serial number. Located behind the battery.
5.) Hit start in Kies it will down load the stock firmware to your PC. Follow the instructions.
6.) It will eventually ask you to put your phone in download mode and connect it to the pc. Do this.
7.) Don't touch it. It is going to take about 10-20 min depending on your Internet speed and your computer.
When it is complete your phone will be back to stock. The same it was the day you pulled it out of the box.
***I would also make sure you back up any data on your phone because it will delete the sd card. It is also wise to remove any external storage sd.
****when finished you can re root using cf auto root or take the OTA update to get you back to 4.3.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
It gives you an error! It does not say what kind of error, it said, just an error, and contact Samsung support.
Yet, on phone display I am getting : "Unsupported Version" in red message.
So, I am guessing - THIS is a good way to recover your Note2 IF, and only IF your phone is NOT bricked.
Damn, I am very close to smash that thing into the wall.................
Lets arrange the facts, BC there must be the way out................
One CAN get back from 4.3 (or even from 4.4) to 4.1.1. I know i did.
All was fine until receiving first OTA update to 4.1.2
And this is when one got stock in white letters Galaxy Note II screen............any ideas why?
fuzio1963 said:
It does not take my phone model number "sgh i317".
---------- Post added at 10:29 AM ---------- Previous post was at 09:34 AM ----------
It gives you an error! It does not say what kind of error, it said, just an error, and contact Samsung support.
Yet, on phone display I am getting : "Unsupported Version" in red message.
So, I am guessing - THIS is a good way to recover your Note2 IF, and only IF your phone is NOT bricked.
Damn, I am very close to smash that thing into the wall.................
Lets arrange the facts, BC there must be the way out................
One CAN get back from 4.3 (or even from 4.4) to 4.1.1. I know i did.
All was fine until receiving first OTA update to 4.1.2
And this is when one got stock in white letters Galaxy Note II screen............any ideas why?
Click to expand...
Click to collapse
OKAY GUYS!!!! SOLUTION FOUND!!!!
Just un-zip, and install this http://www.androidfilehost.com/?fid=23212708291677024 in ODIN 3.07
Finally, it worked for me!!!!
fuzio1963 said:
OKAY GUYS!!!! SOLUTION FOUND!!!!
Just un-zip, and install this http://www.androidfilehost.com/?fid=23212708291677024 in ODIN 3.07
Finally, it worked for me!!!!
Click to expand...
Click to collapse
I can confirm this worked. Phone is no longer bricked.
fuzio1963 said:
OKAY GUYS!!!! SOLUTION FOUND!!!!
Just un-zip, and install this http://www.androidfilehost.com/?fid=23212708291677024 in ODIN 3.07
Finally, it worked for me!!!!
Click to expand...
Click to collapse
Not sure how you came to try this but great job. I did massive testing yesterday with Zen trying to get from stock LJ2 ODIN, all the way to the 4.3 update.
I never thought it was possible, but encountered the same problem of not being able to get to recovery. Regardless of what I tried.
Luckily I remembered you and found this.
That was crazy, I thought my phone was toast. Thanks again.
Had a similar experience recently moving to jedi master x2
After reboot I was left staring at the galaxy note 2 screen for an hour.
Nothing I would typically have done worked including a restore of my nandroid.
So i went back to basics.
Used Odin 2.85
Switched to CWM from TWRP(i prefer and am back on TWRP)
From CWM I was able to finally install the rom and get to swipe screen.
I was still anxious on boot and it took a while though.
good luck
You rocked. This worked absolutely fine. Where did you find this file.
dicksteele said:
Not sure how you came to try this but great job. I did massive testing yesterday with Zen trying to get from stock LJ2 ODIN, all the way to the 4.3 update.
I never thought it was possible, but encountered the same problem of not being able to get to recovery. Regardless of what I tried.
Luckily I remembered you and found this.
That was crazy, I thought my phone was toast. Thanks again.
Click to expand...
Click to collapse
This worked absolutely fine. Even I was stuck on Samsung logo and dint know wat to do I just flashed this file via odin 3.07 and my phone started like a charm. Thanks a lot

[Q] Nexus 7 won't connect to Windows, can't root, can't flash - stuck?!

So I rooted my Nexus 7 (2013) a while back, and it was working fine. I have TWRP recovery installed, bootloader unlocked, and I thought it was rooted. Then (don't kill me, I can't remember what I did, it was so long ago - I think maybe I installed the official KitKat update, although I am pretty sure I sideloaded a rooted version of the stock KK ROM), root just stopped working. Root Checker says I'm not rooted, even though I have the SU app installed. So, I thought, I'll just flash the SU.zip from recovery. So I flash it. And literally nothing happens. It says it flashed successfully, but when I reboot, no root.
In fact, any time I flash anything, it appears to work, but doesn't actually do anything. I tried flashing a different ROM and no dice. I tried accepting the official 4.4.2 update and again, looked like it flashed, but was still 4.4 when I rebooted.
So I thought I'll just plug it into my PC and re-root and maybe flash everything if need be. Except, when I plug it in, it 1) isn't recognized by my computer at all, no matter how many times I uninstall and reinstall drivers, and 2) the ADB connected icon doesn't show up, even when I enable it in Developer Settings.
So basically I'm dead in the water: I can't do anything via recovery, and if recovery is messed up, I can't do anything because it won't connect to my computer (Windows 7, SP1, 64 bit). I have a Mac running OS X Mavericks, if anyone knows some Terminal tricks for stuff.
So…advice?
darnocs1 said:
So I rooted my Nexus 7 (2013) a while back, and it was working fine. I have TWRP recovery installed, bootloader unlocked, and I thought it was rooted. Then (don't kill me, I can't remember what I did, it was so long ago - I think maybe I installed the official KitKat update, although I am pretty sure I sideloaded a rooted version of the stock KK ROM), root just stopped working. Root Checker says I'm not rooted, even though I have the SU app installed. So, I thought, I'll just flash the SU.zip from recovery. So I flash it. And literally nothing happens. It says it flashed successfully, but when I reboot, no root.
In fact, any time I flash anything, it appears to work, but doesn't actually do anything. I tried flashing a different ROM and no dice. I tried accepting the official 4.4.2 update and again, looked like it flashed, but was still 4.4 when I rebooted.
So I thought I'll just plug it into my PC and re-root and maybe flash everything if need be. Except, when I plug it in, it 1) isn't recognized by my computer at all, no matter how many times I uninstall and reinstall drivers, and 2) the ADB connected icon doesn't show up, even when I enable it in Developer Settings.
So basically I'm dead in the water: I can't do anything via recovery, and if recovery is messed up, I can't do anything because it won't connect to my computer (Windows 7, SP1, 64 bit). I have a Mac running OS X Mavericks, if anyone knows some Terminal tricks for stuff.
So…advice?
Click to expand...
Click to collapse
Does it recognize your device when it's booted into the bootloader (aka fastboot mode)?
charesa39 said:
Does it recognize your device when it's booted into the bootloader (aka fastboot mode)?
Click to expand...
Click to collapse
It didn't, but I found I was using a bad USB cable. Swapped out, and now it works (yay). However, root still wouldn't work after I ran several rooting methods from the computer.
Finally, I went to the Play Store, downloaded Superuser from Clockworkmod, followed their link in that description to download the flashable zip, flashed that, and FINALLY got root working. So happy.
darnocs1 said:
It didn't, but I found I was using a bad USB cable. Swapped out, and now it works (yay). However, root still wouldn't work after I ran several rooting methods from the computer.
Finally, I went to the Play Store, downloaded Superuser from Clockworkmod, followed their link in that description to download the flashable zip, flashed that, and FINALLY got root working. So happy.
Click to expand...
Click to collapse
Cool. Glad it worked out for you. :good:

Note 2 stuck at Start Up screen. Please help

My Galaxy Note 2 is stuck at the Start up screen screen. Where its an all black bg and simply says Samsung Galaxy Note II
I have tried using recovery mode, cleared cache, and reset to factory. Neither troubleshoot method worked.
I have tried numerous Odin autoroots. none work. Whenever I try to root it fails. Im guessing it might be because I dont have Dev Debug enable and I cant get into my phone to enable it. because of this issue
I have tried looking for TWRP .tar but every file I download the file is always a .img
The Model of the phone is a SGH-T889 (T-mobile Note II)
I am all out of ideas, and I dont know what to do. I have been search for answers for hours and everytime I think I found a solution it doesnt work.
What ROM was your phone on when this happened ?
Can you get int to download mode ? If yes try flashing stock ROM and see if it helps.
ciphercodes said:
What ROM was your phone on when this happened ?
Can you get int to download mode ? If yes try flashing stock ROM and see if it helps.
Click to expand...
Click to collapse
It was on the offical default rom. the phone was never modded, or rooted.
My niece downloads a bunch of kiddie games onto the phone, we constantly have to uninstall them. My thoughts and the T-mobile tech suspects that it the crash may have been caused my too many updates or a bad updated file most likely due to the games or game.
I can get the phone into download mode, and recovery mode.
In reovery mode I have 6 options
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cashe partition
apply update from cache
I have tried Apply update from cache, Wipe cache partition, then Wipe data.factory reset. I also attempted to put a CF auto root .md5 file and a KIES .md5 file which I believe is a stock firmware file on a SD card. to try to use the apply update from external storage option, but neither file showed up when I went into the option. So I guess I didnt have the right sort of file.
So recovery didnt work so I tried using Odin v3.07 and Odin v3.09 with CF auto root files for the SGH-T889, that didnt work, ecerytime I tried to apply it, It was always Fail within seconds. I tried other root files that are made for other versions of the Galaxt Note 2 like the GT-N1700 but those also simply failed.
I tried using what I believe to be stock frimware files with Odin. and those also Failed.
Im not exactly the best person with these. I learn mostly what I know from the internet and reading various forums, youtube videos, and other people experiences. I cannot find anyone who's problem has not yet been fixed through the above methods. so I really dont know where to go from here.
I think the reason I cant Flash from PC is because it might be possible USB Debugging is not enabled. Not sure if this is what is causing all the Fails in odin
BramaKnox said:
It was on the offical default rom. the phone was never modded, or rooted.
My niece downloads a bunch of kiddie games onto the phone, we constantly have to uninstall them. My thoughts and the T-mobile tech suspects that it the crash may have been caused my too many updates or a bad updated file most likely due to the games or game.
I can get the phone into download mode, and recovery mode.
In reovery mode I have 6 options
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cashe partition
apply update from cache
I have tried Apply update from cache, Wipe cache partition, then Wipe data.factory reset. I also attempted to put a CF auto root .md5 file and a KIES .md5 file which I believe is a stock firmware file on a SD card. to try to use the apply update from external storage option, but neither file showed up when I went into the option. So I guess I didnt have the right sort of file.
So recovery didnt work so I tried using Odin v3.07 and Odin v3.09 with CF auto root files for the SGH-T889, that didnt work, ecerytime I tried to apply it, It was always Fail within seconds. I tried other root files that are made for other versions of the Galaxt Note 2 like the GT-N1700 but those also simply failed.
I tried using what I believe to be stock frimware files with Odin. and those also Failed.
Im not exactly the best person with these. I learn mostly what I know from the internet and reading various forums, youtube videos, and other people experiences. I cannot find anyone who's problem has not yet been fixed through the above methods. so I really dont know where to go from here.
I think the reason I cant Flash from PC is because it might be possible USB Debugging is not enabled. Not sure if this is what is causing all the Fails in odin
Click to expand...
Click to collapse
Lets see if we can get this resolved.
1) Do you remember what version of Android the phone was on 4.3 or 4.1.2 ?
2) Put your phone in download mode then connect to your computer via usb. Start Odin in admin mode (right click and run as admin).
3) Now do you see ID:COM section turn blue ? Under message you can see "Added!". If you see this then phone is recognized by Odin.
4) If your phone was on 4.3 then download this most up to date firmware - from here http://www.sammobile.com/firmwares/download/22863/T889UVUCMK7_T889TMBCMK7_TMB/
5) Once downloaded, extract the file(use 7zip or winrar), once extracted you will see a file with .md5 extension.
6) Now going back to ODIN, click on PDA and then browse to this file which you just extracted.
7) This takes some time, once done you should see a message like "Checking MD5 finished successfully", "Leave CS".
8) You can leave Auto reboot and F-reset time checked.
9) Now click Start and let the process finish.
10) If everything goes fine you should see a green message "Pass"
Let me know how it goes.
I have the same problem as the OP (boots only up to Samsung logo with black bg) but it was not caused by niece downloading games but instead from trying to install jedi masterx2 rom.
I did what ciphercodes recommended and put phone in download mode and odin went through the motions of installing the stock os (in my case version 4.3) but after apparently installing the rom it again booted up to Samsung note II logo in black bg.
luckily I can install either Clockword mod recovery v6.0.4.3 or teamwin v2.8.6.0
The clockword mod recovery can read the external sd card (whereas funnily enough the teamwin can't) and I can attempt recovery from previous backups on cmr or to install a rom from zip file but neither of these work - reboots again to Samsung logo in black background after apparently installing the rom.
both teamwin and cwr mention that they can't mount system and that's probably why no rom is install either using cwr or odin so my guess is that I have to reformat the partitions cause probably efs file is corrupt but I don't know how to do that and I have done extensive search in google but have not found a solution
so ciphercodes if you or anyone reading this can help please reply to this message
ciphercodes said:
Lets see if we can get this resolved.
1) Do you remember what version of Android the phone was on 4.3 or 4.1.2 ?
2) Put your phone in download mode then connect to your computer via usb. Start Odin in admin mode (right click and run as admin).
3) Now do you see ID:COM section turn blue ? Under message you can see "Added!". If you see this then phone is recognized by Odin.
4) If your phone was on 4.3 then download this most up to date firmware - from here
5) Once downloaded, extract the file(use 7zip or winrar), once extracted you will see a file with .md5 extension.
6) Now going back to ODIN, click on PDA and then browse to this file which you just extracted.
7) This takes some time, once done you should see a message like "Checking MD5 finished successfully", "Leave CS".
8) You can leave Auto reboot and F-reset time checked.
9) Now click Start and let the process finish.
10) If everything goes fine you should see a green message "Pass"
Let me know how it goes.
Click to expand...
Click to collapse
I am uncertain of which version the phone was on. If you need I can call t-mobile and have them tell me which version it was on.
I did these steps. the file took a hour to download. and It still didn't work. I follow all steps down to the exact. and when I pressed start. within one second it said FAIL. just the other attempts I made.
BramaKnox said:
I am uncertain of which version the phone was on. If you need I can call t-mobile and have them tell me which version it was on.
I did these steps. the file took a hour to download. and It still didn't work. I follow all steps down to the exact. and when I pressed start. within one second it said FAIL. just the other attempts I made.
Click to expand...
Click to collapse
Unless your t889 Note II was sitting in a drawer and not being updated for the last year or so you probably have 4.3
When you go to download mode do you see "custom binary download: yes ..."
and do you see "knox warranty void:" ?
if so, your phone has been rooted.
but unlike your case, when I try to install stock rom through Odin, it goes through the motions of installing and gives message pass - that is that the stock rom has been installed, but unfortunately it has not installed any rom that my phone can read.
koyanishi said:
Unless your t889 Note II was sitting in a drawer and not being updated for the last year or so you probably have 4.3
When you go to download mode do you see "custom binary download: yes ..."
and do you see "knox warranty void:" ?
if so, your phone has been rooted.
but unlike your case, when I try to install stock rom through Odin, it goes through the motions of installing and gives message pass - that is that the stock rom has been installed, but unfortunately it has not installed any rom that my phone can read.
Click to expand...
Click to collapse
No it says
Product Name: SGH-T889
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Official
Knox Warranty Void: 0
RP SWAEV: A2
BramaKnox said:
No it says
Product Name: SGH-T889
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Official
Knox Warranty Void: 0
RP SWAEV: A2
Click to expand...
Click to collapse
Then you have an un rooted 4.3 rom because the 4.1.2 did not have knox
koyanishi said:
Then you have an un rooted 4.3 rom because the 4.1.2 did not have knox
Click to expand...
Click to collapse
Okay thank you, well then link ciphercodes gave me for the firmware was the right one. But still Failed. *Sigh*
BramaKnox said:
Okay thank you, well then link ciphercodes gave me for the firmware was the right one. But still Failed. *Sigh*
Click to expand...
Click to collapse
Since your phone is not rooted then I think that ciphercodes advice will not work as you can only install a stock rom that way only if your phone is first rooted.
Probably you should try to root your phone using instructions from this thread
http://forum.xda-developers.com/showthread.php?t=2562994
But this might not work for you as it could be that efs file is corrupted or something else as we both boot up to a black screen that only has Samsung logo
koyanishi said:
Since your phone is not rooted then I think that ciphercodes advice will not work as you can only install a stock rom that way only if your phone is first rooted.
Probably you should try to root your phone using instructions from this thread
http://forum.xda-developers.com/showthread.php?t=2562994
But this might not work for you as it could be that efs file is corrupted or something else as we both boot up to a black screen that only has Samsung logo
Click to expand...
Click to collapse
Yeah the chainfire root fail as well. I have tried every file for all the Galaxy II's including mines. none work. Always FAIL in Odin. I'm guessing there is just nothing I can do
BramaKnox said:
Yeah the chainfire root fail as well. I have tried every file for all the Galaxy II's including mines. none work. Always FAIL in Odin. I'm guessing there is just nothing I can do
Click to expand...
Click to collapse
Since your phone is not rooted you may be able to get it repaired under warranty. I think that Samsung warranty is only good for a year, but if you purchased your phone with a American Express gold card (I think other gold cards will also apply) your warranty is extended to double what the original was. So perhaps you have a chance to have your credit card pay for the repair.
Otherwise:
I am no expert but if you want to continue playing with your phone before you get expert advice you may want to play with the recovery mode. To enter recovery mode press volume up and home and power buttons at the same time. once you feel vibrate or after a while release the power button but continue to hold volume up and home buttons and then you will enter recovery mode. you may want to go to menu that says wipe data/factory reset and see if that works. It may be that it is like my phone and the system cannot be mounted in which case you will get that message. After you are through to get out of this menu remove the battery.
But please be aware that I am no expert and you are using this info at your own risk
but I think of doing something catastrophic using this advice in my non expert opinion is small.
koyanishi said:
Since your phone is not rooted you may be able to get it repaired under warranty. I think that Samsung warranty is only good for a year, but if you purchased your phone with a American Express gold card (I think other gold cards will also apply) your warranty is extended to double what the original was. So perhaps you have a chance to have your credit card pay for the repair.
Otherwise:
I am no expert but if you want to continue playing with your phone before you get expert advice you may want to play with the recovery mode. To enter recovery mode press volume up and home and power buttons at the same time. once you feel vibrate or after a while release the power button but continue to hold volume up and home buttons and then you will enter recovery mode. you may want to go to menu that says wipe data/factory reset and see if that works. It may be that it is like my phone and the system cannot be mounted in which case you will get that message. After you are through to get out of this menu remove the battery.
But please be aware that I am no expert and you are using this info at your own risk
but I think of doing something catastrophic using this advice in my non expert opinion is small.
Click to expand...
Click to collapse
Yeah the warranty is expired. and I have tried recovery mode. thats actually the first step before trying to apply a firmware. So recovery hasnt worked either. Guess I will just have to get a new phone. thank you all for oyu help tho. I apperciate it
I was just reading through the thread.. It doesnt seem like you tried flashing Tmobiles Stock 4.3 Firmware in download mode. If you tried to flash a 4.1.2 Firmware when the phone was already updated then I think thats where it failed. Try again but with the 4.3 Firmware through ODIN. After it finishes try rebooting it manually and/or if it doesnt boot again then go back into recovery and factory/data reset again...shouldnt hurt to try..
Double0EK said:
I was just reading through the thread.. It doesnt seem like you tried flashing Tmobiles Stock 4.3 Firmware in download mode. If you tried to flash a 4.1.2 Firmware when the phone was already updated then I think thats where it failed. Try again but with the 4.3 Firmware through ODIN. After it finishes try rebooting it manually and/or if it doesnt boot again then go back into recovery and factory/data reset again...shouldnt hurt to try..
Click to expand...
Click to collapse
From my knowledge the other person who first replied gave me 4.3 firmeware fild link. But in the chances of it could u provide me with a link to a 4.3 firmware u believe will work, because all the ones I found have not worked

[Q] Odin bricked. Can get to DL but Kies won't identify my phone?

I am something of a long time XDA user, having been flashing since the time of the HTC Wizard. But I had never bothered rooting my S3 until I decided I need to install music on the SD card using doubletwist.​
I installed the toolkit and the drivers properly but SuperSU 2.48 doesn't download (yes, I paid a donation), -error messages such as 'couldn't resolve host skipsoft.net' or 'HTTP doesn't seem to support byte ranges'
Option 1 loads what seemed to be an old (2.42?) version of the Odin flash tool: if I follow the instructions, the S3 does to into Download mode (with a message 'do not turn off target) and after about five minutes Odin shows FAIL on the TWRP recovery operation it seems to be executing. It then tells me to be patient while (I assume) rebooting but after about 30 minutes of waiting, the phone doesn't come out of download mode.​
I then rebooted and tried to flash again and again, the flash failed completely, and the phone seems bricked, giving the error message 'firmware upgrade failed, use KIES recovery.
It does go into download mode but when connecting to (newly updated) KIES, the model isn't detected in the recovery procedure so it won't either recover itself or give me a code to do the KIES emergency recovery.
Currently showing in DL is:
ODIN MODE
custom binary downloads YES (1 counts)
curent binary: Custom
system status: Official
qualcomm secureboot:enable
warranty bit:0
bootloader AP SWREV:1​
What is a recovery procedure please? KIES? Some other flasher? Some newer version of Odin?
Oh, and when I plug the phone into the computer, it suddenly recognizes it as an MSM8960, whatever that is?? Before the computer recognised it as the more normal SGT999. Also (this is obvious), the device is no longer recognized in Explorer once the device is connected if you connect it in DL.
Is an MSM8960 the same as a SGT999 in DL mode?
Sorry no one posted any tips or tricks on this request! In default, I ploughed ahead with the normal instructions, remembering that often when flashing doesn't work for no apparent reason, trying again does get everything to work
Re-flashed stock with Odin from download mode, which worked fine and unbricked phone. Then tried TWRP again, which worked fine as well, always providing instructions are followed.
Eventually found myself back at what looked like stock, but with message that I haven't rooted but would i like to do so now using the SuperSU that the toolkit said it was using? If so, down load it from the Playstore, which I didn't understand at all. I thought the playstore was against things like rooting?
Anyway, everything ran to completion, though I am still working on how to use DoubleTwist to transfer albums to the SD card on the Galaxy. (error message, apparently from SGS3 Easy UMS: 'You Do Not Appear to Have Busybox Installed', followed by loop of preparing SD card for mounting, mounting Then nothing by way of D card shows up in DoubleTwist)
Don't use toolkits, they are not updated and have caused many issues. To root, use towelroot
serio22 said:
Don't use toolkits, they are not updated and have caused many issues. To root, use towelroot
Click to expand...
Click to collapse
is there a list anywhere of devices which work with towelrroot please or is it only flavours of s3? i have a curious MK 6571 S6 which seems to defy identification because it isn't an iPhone knockoff and it is having the hardest of times addressing its hard drive. Whatever i try to install on it results in the error message that there isn't enough hard drive space to install. Towelroot also gives this error message which i believe to be entirely spurious, and it is a really tiny!! something appears to be preventing it installing any app on it which can read or influence any hardware on it?
(I also tried installing framarooot 193 but it gave me the same out of space error message)
licensedtoquill said:
is there a list anywhere of devices which work with towelrroot please or is it only flavours of s3? i have a curious MK 6571 S6 which seems to defy identification because it isn't an iPhone knockoff and it is having the hardest of times addressing its hard drive. Whatever i try to install on it results in the error message that there isn't enough hard drive space to install. Towelroot also gives this error message which i believe to be entirely spurious, and it is a really tiny!! something appears to be preventing it installing any app on it which can read or influence any hardware on it?
(I also tried installing framarooot 193 but it gave me the same out of space error message)
Click to expand...
Click to collapse
So it is an S6 knockoff? I'm not sure if there is a list but the s6 definitely is not compatible
Sent from my SM-G920T using Tapatalk
s3 recovery my testimony
licensedtoquill said:
I am something of a long time XDA user, having been flashing since the time of the HTC Wizard. But I had never bothered rooting my S3 until I decided I need to install music on the SD card using doubletwist.​
I installed the toolkit and the drivers properly but SuperSU 2.48 doesn't download (yes, I paid a donation), -error messages such as 'couldn't resolve host skipsoft.net' or 'HTTP doesn't seem to support byte ranges'
Option 1 loads what seemed to be an old (2.42?) version of the Odin flash tool: if I follow the instructions, the S3 does to into Download mode (with a message 'do not turn off target) and after about five minutes Odin shows FAIL on the TWRP recovery operation it seems to be executing. It then tells me to be patient while (I assume) rebooting but after about 30 minutes of waiting, the phone doesn't come out of download mode.​
I then rebooted and tried to flash again and again, the flash failed completely, and the phone seems bricked, giving the error message 'firmware upgrade failed, use KIES recovery.
It does go into download mode but when connecting to (newly updated) KIES, the model isn't detected in the recovery procedure so it won't either recover itself or give me a code to do the KIES emergency recovery.
Currently showing in DL is:
ODIN MODE
custom binary downloads YES (1 counts)
curent binary: Custom
system status: Official
qualcomm secureboot:enable
warranty bit:0
bootloader AP SWREV:1​
What is a recovery procedure please? KIES? Some other flasher? Some newer version of Odin?
Click to expand...
Click to collapse
hey friend, your woes sound alarmingly familiar to my own not so long ago. I will start this post by saying I am not going to come out and declare myself as anything but what I am, an average guy with an interest and at one time identical dilemma as yourself.
that being said what exactly are you trying to achieve an are you willing to start from scratch? are you backed up? these are my questions. in answering or perhaps confirming what you may know is that once rooted and subsequently bricked kies ceases to be a friend to your device and it is with odin that your phones future if is to have one lies. I personally have enjoyed much success with the program but at this point ive only done a handful of operations with it.
If what ive written has given you any encouragement please feel free to respond and I'll gladly explain what i did to restore my s3 because i wouldnt want to advise outside of something I have tried myself and know to be safe and conclude with a desirable result for you

Categories

Resources