I just entered the world of a rooted phone, all exciting and new. I used triangle away, and everything is well. I even turned off the debugging mode as i thought i was all done with things rooting and didn't need it.
The next day I realize there is update for supersu, so i accept, if gives me two choices in the update, i choose one, and now my phone is the in GTN7100 loop non stop. Seems of the two options, I choose wrongly. I can put it into download mode. I think I can put it into recovery mode too.
I used this method to boot.
galaxy-note2.wonderhowto.com/how-to/root-your-samsung-galaxy-note-2-using-odin-for-windows-so-easy-your-grandma-can-do-it-0146884
I did perform some basic backups with kies and i believe an app called my backup, so in the worst case, I believe i can recover everything if had to do some kind of reset that would erase all the data. (I am hoping to avoid that, as the recovery may be a learning process if any challenges with it)
its with 4.1.2 and I am not sure if any other details I should provide. so i feel proud i got this far, sad the supersu update made some kind of corruption. i know you guys may be extremely busy and i thank you so much in advance.
Try getting into recovery (CMW or Philz touch) and re-flash a ROM?
thank you bunglebp
bunglebp said:
Try getting into recovery (CMW or Philz touch) and re-flash a ROM?
Click to expand...
Click to collapse
Thank you so much for your reply bunglebp.
I believe I had the CMW when i rooted. Reflashing the ROM won't lose the data, or will? This is new territory for me, so I am going step be step.
Volume up - home - power, i think i understand this far. I just don't want to make any mistakes and follow to a T to bring the phone back up with least work at it if possible.
Macguyer2000 said:
Thank you so much for your reply bunglebp.
I believe I had the CMW when i rooted. Reflashing the ROM won't lose the data, or will? This is new territory for me, so I am going step be step.
Volume up - home - power, i think i understand this far. I just don't want to make any mistakes and follow to a T to bring the phone back up with least work at it if possible.
Click to expand...
Click to collapse
Yes your description of how to get into recovery is correct. But your description of your situation is light on details, hard to get a clear picture, but I feel your pain!
If you have a ROM sitting on your phone that you can reflash in recovery, do it. You won't lose any media on your internal memory e.g. pictured, movies. All your app settings will remain if you don't wipe anything in recovery prior to flashing - but in your situation I suggest a full wipe & reset to (hopefully) clear out any problems.
As for upgrading SU, I'm wondering what you mean by two options? Let us know how you get on. Also feel free to PM me if you're truly stuck, I've been there myself and received help that saved me untold stress.
tweeny80 said:
Yes your description of how to get into recovery is correct. But your description of your situation is light on details, hard to get a clear picture, but I feel your pain!
If you have a ROM sitting on your phone that you can reflash in recovery, do it. You won't lose any media on your internal memory e.g. pictured, movies. All your app settings will remain if you don't wipe anything in recovery prior to flashing - but in your situation I suggest a full wipe & reset to (hopefully) clear out any problems.
As for upgrading SU, I'm wondering what you mean by two options? Let us know how you get on. Also feel free to PM me if you're truly stuck, I've been there myself and received help that saved me untold stress.
Click to expand...
Click to collapse
When I was welcomed to update supersu, it had a left choice (normal) and a right side choice cwm/twrp (not sure the spelling) I choose the right.
I really want to first thank you so so much.
Which options within the recovery should i choose?
When I did try to repeat the original root process, I got a PIT message that just stayed and did not change. I was on slow machine, but I think it was because the debug usb was off or as i was starting to hear, the partition might be changed in the rooting process? Not sure how that would relate. likely because the debug was off
The pain and fear that broke the phone is really intense. Plus, I use it all the time, before this happened. what information do you need?
Macguyer2000 said:
When I was welcomed to update supersu, it had a left choice (normal) and a right side choice cwm/twrp (not sure the spelling) I choose the right.
I really want to first thank you so so much.
Which options within the recovery should i choose?
When I did try to repeat the original root process, I got a PIT message that just stayed and did not change. I was on slow machine, but I think it was because the debug usb was off or as i was starting to hear, the partition might be changed in the rooting process? Not sure how that would relate. likely because the debug was off
The pain and fear that broke the phone is really intense. Plus, I use it all the time, before this happened. what information do you need?
Click to expand...
Click to collapse
My assumptions are you were successfully rooted, I'm unsure if you are on stock ROM or custom ROM, you updated SU and ended up in bootloop. You are able to get into recovery - do you have a ROM already sitting on your phone, that you can flash/install? If yes, do that. But first, in recovery look for options named factory reset, do that. You suggested you have CWM recovery - there is option to wipe cache, then under advanced option, is wipe dalvik cache, do those. I hope I adequately described the menu structure, my phone is not with me right now to check.
Really, we just want to get you back into a functioning ROM, and stop the bootloops. As for updating SU, I assume you tried updating from recovery? If so, stick to the Play Store updates only.
Again lemme know how you get on, and confirm my assumptions so I can help further if needed.
tweeny80 said:
My assumptions are you were successfully rooted, I'm unsure if you are on stock ROM or custom ROM, you updated SU and ended up in bootloop. You are able to get into recovery - do you have a ROM already sitting on your phone, that you can flash/install? If yes, do that. But first, in recovery look for options named factory reset, do that. You suggested you have CWM recovery - there is option to wipe cache, then under advanced option, is wipe dalvik cache, do those. I hope I adequately described the menu structure, my phone is not with me right now to check.
Really, we just want to get you back into a functioning ROM, and stop the bootloops. As for updating SU, I assume you tried updating from recovery? If so, stick to the Play Store updates only.
Again lemme know how you get on, and confirm my assumptions so I can help further if needed.
Click to expand...
Click to collapse
[If you don't already have it, download and install the Samsung USB Drivers. Now, download and unzip the GalaxyNote2Root.zip file. Open the ODIN program by double-clicking the odin3 v1.85.exe application file.] from the website i followed. with this catchy title:
How to Root Your Samsung Galaxy Note 2 Using ODIN for Windows (So Easy Your Grandma Can Do It)
and it rooted with no problem...just that boot loop the next day when updating supersu...and using the google only site is a good idea.
I am having trouble to get the recovery mode on. I can go into download mode easily, but to go into recovery appears to be a trickier issue. I just can't get it. Can you guide me on this....
Simply reflash rom and reroot again.
Flashing stock rom won't erase data. So if after flashing rom device boot up normally, tour data will be there intact, incase it doesn't boot normally after flashing rom then you may need to wipe it.
Sent from my GT-N7100 using xda premium
Macguyer2000 said:
I just entered the world of a rooted phone, all exciting and new. I used triangle away, and everything is well. I even turned off the debugging mode as i thought i was all done with things rooting and didn't need it.
The next day I realize there is update for supersu, so i accept, if gives me two choices in the update, i choose one, and now my phone is the in GTN7100 loop non stop. Seems of the two options, I choose wrongly. I can put it into download mode. I think I can put it into recovery mode too.
I used this method to boot.
galaxy-note2.wonderhowto.com/how-to/root-your-samsung-galaxy-note-2-using-odin-for-windows-so-easy-your-grandma-can-do-it-0146884
I did perform some basic backups with kies and i believe an app called my backup, so in the worst case, I believe i can recover everything if had to do some kind of reset that would erase all the data. (I am hoping to avoid that, as the recovery may be a learning process if any challenges with it)
its with 4.1.2 and I am not sure if any other details I should provide. so i feel proud i got this far, sad the supersu update made some kind of corruption. i know you guys may be extremely busy and i thank you so much in advance.
Click to expand...
Click to collapse
Just to let you know I have used both sources of available update for super su.
And have never had any problems, I highly doubt your boot loop is anything todo with the su update. The guus on here at xda are superb and will have you back up and running no problem.
GT N7105 with XDA Premium......that is all......
bearusa said:
Just to let you know I have used both sources of available update for super su.
And have never had any problems, I highly doubt your boot loop is anything todo with the su update. The guus on here at xda are superb and will have you back up and running no problem.
GT N7105 with XDA Premium......that is all......
Click to expand...
Click to collapse
thank you for the positive thinking. but I think I have a serious problem here.
I can not get into recovery, as much as i try.
Before all this happened, i unticked usb debug.
I can however get into download mode.
I really feel that i have critically wounded my phone.
Macguyer2000 said:
thank you for the positive thinking. but I think I have a serious problem here.
I can not get into recovery, as much as i try.
Before all this happened, i unticked usb debug.
I can however get into download mode.
I really feel that i have critically wounded my phone.
Click to expand...
Click to collapse
Enter download mode and reflash the recovery using odin. Unticking debug should not put your phone into bootloop neither. . You have to make sure your flashing the correct recovery or rom for your phone model. Depending if you have n7100 or n7105..
GT N7105 with XDA Premium......that is all......
bearusa said:
Enter download mode and reflash the recovery using odin. Unticking debug should not put your phone into bootloop neither. . You have to make sure your flashing the correct recovery or rom for your phone model. Depending if you have n7100 or n7105..
GT N7105 with XDA Premium......that is all......
Click to expand...
Click to collapse
OK, let me make sure I understand correctly..I can put some of my fears/worries to rest.
Let me restate
My situation is a bootloop.
My usb debugging is off. (the day after the rooting, I didn't think I needed it on anymore, as I completed the root)
Later that day, just moment before the loop happened, I was updating SuperSu. (something the phone didn't like)
I found: I can go into download mode. I can not go into recovery mode.
(a phone with a bootloop, usb debugging is off, and download mode is accessible)
So:
(When rooting, I opened Odin, I selected the PDA option, choose the proper file, and pressed start. Yellow changed to Green and we were done)
So Now, I open Odin, select the PDA option, choose the correct file for my phone (GT N7100) from likely the samsung website, I see the Yellow, hit start, yellow turns to green, and we're ok?
That simple thing I said 24 hr ago, still you are here.
It has nothing to do with usb debugging.
If you keep it enable /disable, it won't make any difference in flashing.
Sent from my GT-N7100 using xda premium
Phone is OK now!
dr.ketan said:
That simple thing I said 24 hr ago, still you are here.
It has nothing to do with usb debugging.
If you keep it enable /disable, it won't make any difference in flashing.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
I want to say thank you to everyone. I flashed recovery and it told of bad install. I rebooted and everything is FINE!
Thank you so much!
Related
I attempted to restore my fiance's S3 to full factory stock about a month ago now, after I received a prompt for the ~82MB OTA update, and she didn't... She was tired of me taking her phone and keeping it out of her hot little hands whilst I made nandroids and flashed the latest updates to BlazerROM, and she didn't have a problem with stock ROM, so I figured I'd put it back for her.
Well, I did, and I KNOW I left CWRecovery in, and not sure if I left root or not, but she STILL has not received the OTA update which still bugs me... So I need to know what is the BEST method for FULL STOCK RECOVERY? I don't want her missing out when the Jelly Bean official drops, and I may flash mine back when it hits just to test it out...
I found this: http://forum.xda-developers.com/showthread.php?t=1935973
Which directed me to QBKing's site, but also warned that the video was now somewhat dated...
Am I assume that by saving her text messages and contacts, and flashing the ODIN .tar listed on this page: http://forum.xda-developers.com/showthread.php?t=1919919 and just letting her re-install her apps, is an effective way to return to FULL and UNMODIFIED stock? Should I run Triangle-Away before proceeding? Will this return the device status to Unmodified (or whatever it says) as opposed to "Custom" in the Status page, as it currently shows for her, in case of warranty needs?
Sorry to be "That Guy", but some of the other topics where a bit vague and lacked details, so I figure if we can get something Semi-Detailed and answering most of the big/general questions, perhaps this could serve as a Go-To thread for others who wish to do this...
http://forum.xda-developers.com/showthread.php?t=1904099
Thread youve mentioned above also works fine. If using odin method, run triangle away beforehand. Neither method will wipe data. Depending on the rom you're coming from, it may not be necessary. If you flash without wiping and the rom fails to boot(hangs on glowing samsung logo), go back to recovery and factory reset. Itll boot right up
billard412 said:
http://forum.xda-developers.com/showthread.php?t=1904099
Thread youve mentioned above also works fine. If using odin method, run triangle away beforehand. Neither method will wipe data. Depending on the rom you're coming from, it may not be necessary. If you flash without wiping and the rom fails to boot(hangs on glowing samsung logo), go back to recovery and factory reset. Itll boot right up
Click to expand...
Click to collapse
i cant thumbs-up you hard enough.... thanks for that awesome pile of resources
JUST TO CLARIFY!
On your thread you updated just this morning with the flash-counter reset included, just run in CWR, and all is good, if not, then factory reset, and all is good? Or factory reset, reflash, all is good?
EDIT: FLashed
In download mode;
ODIN MODE
PRODUCT NAME: SPH-L710
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE (not sure what that one is haven't done more than root with oden and flash)
System status troubles me... ODEN flash, or let it full reboot? I went into download to check before first initial boot after flash. will allow full boot and see what happens...
EDIT 2: Well, android system status shows Normal... Girl woke up and took her phone back, so will check oden later.
Yup the one updated today is just that. Flash and reboot. Youll be 100% stock
The system status in odin will probably fix itself after booting. If not a factory reset should do it
billard412 said:
Yup the one updated today is just that. Flash and reboot. Youll be 100% stock
The system status in odin will probably fix itself after booting. If not a factory reset should do it
Click to expand...
Click to collapse
Seems to have worked. I wish I had money to donate to your wonderful work. Hopefully she'll be receiving prompts for OTA updates for JellyBean shortly... Thanks for also having it up to date. At least I gather it DOES include the ~82MB update she's been missing... Keep up the wonderful work friend!
Glad to hear it. Much appriciated. Now if only the damn thing would be stickied...XD
billard412 said:
Yup the one updated today is just that. Flash and reboot. Youll be 100% stock
The system status in odin will probably fix itself after booting. If not a factory reset should do it
Click to expand...
Click to collapse
billard412 said:
Glad to hear it. Much appriciated. Now if only the damn thing would be stickied...XD
Click to expand...
Click to collapse
Whoever I need to tell, I support sticky'ing the thread.
AT&T Galaxy S3
Mac OSX 10.8
I know I can get my device back, I'm just not sure how. I successfully rooted using CASUAL, no problems there. Got the normal root applications installed, did the Clockwork backup, everything was great.
I then decided to try a custom ROM - the Cyanogen 10.1. It downloaded fine, and I selected to also install Google Apps, then it rebooted and the Cyanogen boot screen with the spinning circle came up. However, this lasted way longer than I thought it should, so I looked it up, and what I got from the research is that I had the wrong gapps on there.
So, I followed the instructions in this thread (same problem as me), and wiped the system. However, I believe I used the wrong list item, and now everything I had is gone. I can't boot from recovery because it doesn't exist, and when booting into CM I just get the same error message that setup has stopped working. I thought maybe I could put a new ROM on the sd card or phone harddrive and boot from that, but both are inaccessible through USB on my Mac.
I can get it into ODIN mode (where it says "Downloading... Do not turn off target!"), which I'm thinking is what I want, and I have Heimdall installed and it runs and recognizes my device, but I cannot for the life of me find a tar.gz file to use.
If anyone can offer any sort of help, I would super appreciate it.
chazbot7 said:
AT&T Galaxy S3
Mac OSX 10.8
I know I can get my device back, I'm just not sure how. I successfully rooted using CASUAL, no problems there. Got the normal root applications installed, did the Clockwork backup, everything was great.
I then decided to try a custom ROM - the Cyanogen 10.1. It downloaded fine, and I selected to also install Google Apps, then it rebooted and the Cyanogen boot screen with the spinning circle came up. However, this lasted way longer than I thought it should, so I looked it up, and what I got from the research is that I had the wrong gapps on there.
So, I followed the instructions in this thread (same problem as me), and wiped the system. However, I believe I used the wrong list item, and now everything I had is gone. I can't boot from recovery because it doesn't exist, and when booting into CM I just get the same error message that setup has stopped working. I thought maybe I could put a new ROM on the sd card or phone harddrive and boot from that, but both are inaccessible through USB on my Mac.
I can get it into ODIN mode (where it says "Downloading... Do not turn off target!"), which I'm thinking is what I want, and I have Heimdall installed and it runs and recognizes my device, but I cannot for the life of me find a tar.gz file to use.
If anyone can offer any sort of help, I would super appreciate it.
Click to expand...
Click to collapse
Your recovery shouldn't be affected by a wipe (unless you flashed something over it) as ROMs don't flash recovery, therefor vol up + home + power should get you in it. If you success to, You should be able to mount through recovery.
As for Heimdall, it just got S3 support (last week I believe), therefor it might not be easy to find a stock file for it. That being said, if you have access to any Windows pc, that'd be the easiest solution here (using Odin).
Yes, I can still get into the recovery menu, but when I use "backup and restore>restore" it says No files found. Is there anything I can do to just get a working OS running? Or am I just doing it totally wrong, I'm new to the rooting stuff. The Windows computer will be my last resort haha.
BWolf56 said:
Your recovery shouldn't be affected by a wipe (unless you flashed something over it) as ROMs don't flash recovery, therefor vol up + home + power should get you in it. If you success to, You should be able to mount through recovery.
As for Heimdall, it just got S3 support (last week I believe), therefor it might not be easy to find a stock file for it. That being said, if you have access to any Windows pc, that'd be the easiest solution here (using Odin).
Click to expand...
Click to collapse
Yes, I can still get into the recovery menu, but when I use "backup and restore>restore" it says No files found. Is there anything I can do to just get a working OS running? Or am I just doing it totally wrong, I'm new to the rooting stuff. The Windows computer will be my last resort haha.
chazbot7 said:
Yes, I can still get into the recovery menu, but when I use "backup and restore>restore" it says No files found. Is there anything I can do to just get a working OS running? Or am I just doing it totally wrong, I'm new to the rooting stuff. The Windows computer will be my last resort haha.
Click to expand...
Click to collapse
Windows pc is definitely the easiest option here but you try mounting your SD from recovery, redownload the ROM and Gapps you wanna use, put them on your device and flash them after a factory reset.
If you wiped your SD card, it's normal that you don't have a backup anymore.
BWolf56 said:
Windows pc is definitely the easiest option here but you try mounting your SD from recovery, redownload the ROM and Gapps you wanna use, put them on your device and flash them after a factory reset.
If you wiped your SD card, it's normal that you don't have a backup anymore.
Click to expand...
Click to collapse
It's aaaliiiiiiive! Grabbed an extra micro SD I had, threw Cyanogen 10.1.0 RC4 on it, and installed it just fine. Now updating to RC5. My only question now is how to get Google Apps on there. Does this need to be done beforehand, or can it be done after?
chazbot7 said:
It's aaaliiiiiiive! Grabbed an extra micro SD I had, threw Cyanogen 10.1.0 RC4 on it, and installed it just fine. Now updating to RC5. My only question now is how to get Google Apps on there. Does this need to be done beforehand, or can it be done after?
Click to expand...
Click to collapse
You usually flash the Gapps right after flashing the ROM, before rebooting.
P.S.: fully reading the instructions helps before flashing
Sent from my SGH-I747 using xda app-developers app
BWolf56 said:
You usually flash the Gapps right after flashing the ROM, before rebooting.
P.S.: fully reading the instructions helps before flashing
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Gotcha, sorry about that. Thanks for all the help good sir. This is actually way faster than my stock ROM, I'm pretty stoked on it, Google Apps or not.
chazbot7 said:
Gotcha, sorry about that. Thanks for all the help good sir. This is actually way faster than my stock ROM, I'm pretty stoked on it, Google Apps or not.
Click to expand...
Click to collapse
No need to apologize. Glad you got it back up! And it was mostly to keep you from making similar mistakes in the future
Sent from my SGH-I747 using xda app-developers app
also one thing you need to know
First boot after you flash will always take longer than normal. After that, it's fine
THIS THREAD IS ONLY FOR THE SGH-730G VARIANT OF THE SAMSUNG DISCOVER. USE OF ANY OF THESE GUIDES AND METHODS FOR ANY OTHER VARIANT OF THE PHONE IS AT THE RISK OF THE USER
This thread is a guide on how to root and install CWM recovery on the Samsung Galaxy Discover (SGH-730G) which is the Tracfone (Net10, Straight Talk) variant of the device. These instructions are for Windows users only. If someone knows how to do it through Linux distro or Mac, please let me know and we will add those instructions to this post.
IMPORTANT: THIS GUIDE ASSUMES THAT YOU HAVE A PRIOR KNOWLEDGE OF THE TOOLS AND TERMS USED. ROOTING YOUR DEVICE WILL VOID YOUR WARRANTY! STOP NOW IF THIS IS SOMETHING YOU ARE CONCERNED ABOUT! IF YOU PROCEED, FOLLOW ALL THE DIRECTIONS CAREFULLY. USE OF THIS GUIDE AND THESE TOOLS IS AT THE RISK OF THE USER! I AM NOT RESPONSIBLE FOR ANY DAMAGE OR NEGATIVE OUTCOMES INCLUDING BUT NOT LIMITED TO SOFT BRICK, HARD BRICK, EXPLODING BATTERIES, NUCLEAR WAR, GIANT SQUID PEOPLE, OR SPONTANEOUS JUSTIN BIEBER CONCERTS IN YOUR LIVING ROOM
***First let's get all the tools and files you will need to complete this process***
Samsung USB Drivers: Click HERE to download the USB drivers for the SGH-730G.
UnlockRoot Pro (Free Download) - Click HERE and scroll down to "UnlockRoot Pro" and click the "Free Download" button. *Note*: Your computer may tell you that this program is malicious. You may have to disable antivirus in order to download.
Odin3 v3.07 - Click HERE to download Odin. This program will be used to flash CWM recovery to your phone.
CWM Recovery (thanks to JohnnyGalto) - Click HERE to download CWM recovery for your phone.
***Now that you have all the tools downloaded let's get them installed and ready for use.***
1) Install the USB drivers (should be self-explanatory).
2) Click on UnlockRoot_downloader_by_UnlockRoot.exe to start the installation. You may have to grant it administrator privileges. I DO NOT RECOMMEND INSTALLING ANY OF THE SPECIAL OFFERS THAT FIRST COME UP WHEN YOU OPEN THE FILE. CLICK SKIP until the automatic download begins. This is the download for the program itself. Once that is finished, follow the instructions to install the program on your computer.
3) Extract Odin Files: I recommend creating a folder on the desktop named "Odin" simply for easy access. However, feel free to choose whatever directory you want. Simply extract all the files to a designated folder.
4) CWM Revovery Tar: Move this file into the same folder where you extracted Odin. This will make it easier to access in a little while.
***If you have followed all the instructions correctly, you are now ready to install CWM recovery and root your device! You will periodically see a yellow triangle on the Samsung boot logo screen throughout this process. But have no fear, we will take care of this later on.***
1) Put your phone into download mode by holding VOLUME DOWN + POWER. A warning screen about custom OS will appear. Press VOLUME UP to confirm this is what you want to do. You should then be showing a screen with the Android logo and the "Downloading... Do not turn off target!!" text.
2) Now connect your phone to the computer using the USB cable, and open Odin from the folder you extracted it to. If your phone is connected properly you should see something similar to "0:[COM10]" in the box under ID:COM in the upper left of the window.
**VERY IMPORTANT** MAKE SURE THE ONLY TWO BOXES CHECKED UNDER "OPTIONS" ARE AUTO REBOOT AND F. RESET TIME!! NO OTHER BOXES SHOULD BE CHECKED
3) Under "Files [Download]" click the PDA button. Navigate to where you placed the CWM tar file and click okay.It is important that you ONLY click "PDA" for this. If you have followed the directions carefully, Odin should check the MD5 sum of the file to verify validity. If the file comes back invalid or you get any errors, STOP, and report them in the thread.
4) Click "Start". DO NOT TURN OFF OR DISCONNECT YOUR PHONE DURING THIS PROCESS. If everything goes well, your phone will reboot automatically after install. To check if your install worked properly, follow the next instructions to boot into recovery and make a stock backup.
OPTIONAL BUT RECOMMENDED SAFETY STEP BEFORE PROCEEDING WITH ROOT (REQUIRES AN EXTERNAL MICRO SD CARD) - CWM recovery works without root permission. It is HIGHLY recommended that you make a complete backup of your stock image before proceeding. This will make it easier to recover from a soft brick, or to return your phone to stock in the future should you choose to do so. A)Power off your phone. To boot into recovery, hold VOLUME UP+POWER until the Samsung logo is displayed. After the logo displays, release the POWER button. Keep holding the VOLUME UP button until your phone boots into the CWM recovery screen. B) Using the volume keys to navigate the menu, scroll down to "backup and restore". Use the power button to select. C) Select backup using the power button. D) After your backup is complete, go back to the main menu and select "reboot system now".
5) Before using UnlockRoot Pro, go to your Settings menu and scroll down to "Developer Options". Be sure to select "USB debugging", "Allow mock locations", and just to avoid potential disaster, choose "Stay awake". After this is all done, you can go back and unselect these.
6) With USB debugging enabled on your phone, launch UnlockRoot (not the UnlockRoot PRO shortcut the program installs on the desktop). Click the big green "Root" button. **NOTE** During the process it will ask you if you want to install other apps. DO NOT INSTALL THEM. Once the program is finished, if all went well, you now have a rooted SGH-730G!
7) There are a number of apps available in the Play Store that check to see if you are rooted. Alternatively, this is how I check my devices. A) Download and install "Terminal Emulator" from the Play Store. This app is like using ADB on your phone. B) Once it is installed, open the app. Type in the command "su" (without the quotes) and hit enter. If rooting was successful, your phone should show a pop-up message asking you to grant it root privileges. Go ahead and say yes and rejoice in the fact you were successful. If you receive the error "permission denied", then the root was unsuccessful.
**Dealing with the pesky yellow triangle on the Samsung boot screen**
The yellow triangle on the Samsung boot screen is a visual warning that you are running custom software. To get rid of it, click the following thread link. "Triangle Away" is a paid app in the Play Store, but the awesome Chainfire has made it available in the forums. Read the thread carefully and follow all the instructions for using the app. Neither I, nor him, nor your pet are responsible for the misuse of the app. - http://forum.xda-developers.com/member.php?u=631273
THAT'S IT!!! If you followed all the directions carefully, you now have a rooted SGH-730G and the sky is the limit now. Currently there is no known custom roms for this device. However I am working on building a Stock+Root Deodexed version of the factory firmware, and will upload it when I can verify it is stable to be released. Following that, I will be developing a custom rom based on the stock firmware. But of course, if you have the experience and know-how, feel free to start developing your own roms for this phone. The more the merrier.
And as always, if you were successful using this guide, or it helped you in any way, please inflate my ego by clicking that thanks button.
I will try to answer as many questions as possible if you run into problems during the process, or if you have other questions about what you can do with this device now that it is rooted.
I CURRENTLY DO NOT KNOW OF A WAY TO MANUALLY UNLOCK THE PHONE. IT'S A LITTLE BIT BEYOND MY SKILLS. I HAVE HOWEVER SEEN PEOPLE IN OTHER FORUMS GETTING PEOPLE TO DO IT USING REMOTE ACCESS TO THEIR COMPUTERS WITH THE PHONE PLUGGED IN TO IT. I DON'T KNOW ALL THE DETAILS ABOUT HOW IT WORKS, BUT COMMON SENSE TELLS ME THIS ISN'T A VERY TRUSTWORTHY THING TO BE DOING. IT'S TOTALLY UP TO YOU IF YOU REALLY TRUST A COMPLETE STRANGER TO HAVE VIRTUAL ACCESS TO YOUR COMPUTER AND YOUR PHONE. BE I'D BE WEARY.
:good: Thanks (in no particular order) to andronald for the original thread about the 730M variant of this device, Without that thread, this thread would not be possible. FitAmp for his contributions to the project over there, JohnnyGalto for the CWM recovery image, cshmitt for his help in getting me started working on a custom rom for this device. :good:
Soft Brick Recovery
SOFT BRICK RECOVERY FOR SGH-730G
Right now, I am working on a tar Odin flashable system image to make it easier to recover from a soft brick of the device. Once it is completed and tested, I will update this post to include a download of it.
***This post will help you recover from a soft brick or bootloop error on your SGH-730G after rooting. This quick guide assumes that you still have access to CWM recovery and/or are able to boot into download mode. (See OP for instructions on how to boot into recovery and download mode.)***
If you followed the instructions and recommendations in the previous post, then you should have made a backup of the stock image using CWM recovery. This is what you will use to help recover your phone so you can start the process again, or not, depending on how gutsy you feel.
IF YOU ARE STILL ABLE TO BOOT INTO CWM RECOVERY
1) Power off your device. You may have to pull the battery to do this if you are stuck with a bootloop or other booting issues.
2) Boot into CWM recovery (see OP for instructions)
3) Scroll down to "backup and restore"
4) Select restore
5) You should then see a restore point to select. The format is usually "YYYY-MM-DD.HOUR". The hour is usually in 24h format.
6) Select the file then select "Yes".
7) If everything works correctly, your stock backup should be restored and you should be able to boot your phone again.
**Note** If you lose root while restoring your stock backup, just use the guide in the OP to try again.
**If you cannot boot into CWM recovery after installation and making a backup.**
Try to reinstall the CWM recovery image using the instructions in the OP.
Again, as soon as it is ready, I will upload a tar that can be flashed through Odin to restore the factory image to your phone, and instructions on recovering and returning to stock will be posted here.
As always, if this helps you in any way, inflate my ego by clicking that thanks button.
Fun with the SGH-730G
So far there are a few fun things I have found work for this phone so far.
For those who may want overclock features, check out this thread. The reason I didn't include it in the OP is because I didn't have success in changing the max value for CPU speed. It stayed constant at 1000 and produced a little too much battery drain for my taste.
SetCPU - This app only works to change the minimum allowed CPU speed of the stock kernel. I run the "ondemand" settings with a minimum of 600MHz and max of 800Mhz. This has helped to reduce some lag from the stock speeds the kernel likes to run and doesn't produce a noticeable battery drain.
Seeder - The seeder lag reduction app makes a huge difference in smoothness of the device.
Xposed Framework: If you don't know what this is, search the XDA forums and you will be able to learn just about everything you want about it. So far I have tested features of the XBlast module and Xposed Additions. Center clock and clock color change, 4-way reboot menu with screenshot, Volume button tweaks, all from Xblast. Xposed Additions can be used to remap the buttons for different functions. I was able to remap the back key to kill the foreground app on long-press. Very useful to limit the amount of running apps in the background.
Notification Toggle - This nifty little app allows you to place toggles for wifi, mobile data, brightness, etc, in the notification dropdown screen. Saves a little time from having to navigate through the settings on the phone, and saves home screen space by not having to use the power widget.
Rom Toolbox - Some features may work, but it is better to have the rom deodexed to take full advantage. (A deodexed version of the stock rom will be available soon).
Auto Killer Memory Optimizer: This is a personal favorite of mine. I own the pro version which is well worth the money. It allows custom settings to optimize RAM usage and free up memory. Makes the phone so much smoother.
If you find any other fun mods that work with this phone, pleas share!
Thank you very much. Been waiting for this for a while. Again thanks.
Nomad692000 said:
Thank you very much. Been waiting for this for a while. Again thanks.
Click to expand...
Click to collapse
My pleasure. I felt it was necessary to separate this phone version from the other versions to avoid confusion. I'll be (hopefully) updating the soft brick recovery in just a moment. Currently testing a new method. Glad you liked the thread. Stick around, things may start to get interesting soon
So far I haven't had any luck creating an Odin package of the factory system image. I have written to Tracfone to see if they could provide me with the factory image but I'm not going to have high hopes it will happen.
Hopefully this week I will be able to provide a deodexed and debloated version of the stock rom that will run a little faster and take up a little less space on the device.
A custom kernel is in the works for those interested in overclocking, though I think anything past the stock max speed will cause a good amount of battery drain.
Sent from my SGH-S730G
So you building a custom rom for the tracfone version (730G)?
(Dominix) said:
So you building a custom rom for the tracfone version (730G)?
Click to expand...
Click to collapse
Slowly but surely yes. Haven't gotten as much done this week as I had hoped but it is in the works.
Sent from my SGH-S730G
i need stock rom please
TheGeekyNimrod said:
Slowly but surely yes. Haven't gotten as much done this week as I had hoped but it is in the works.
Sent from my SGH-S730G
Click to expand...
Click to collapse
i mistakingly picked up the wrong phone..the discover and the centura are very similar....i accidently installed custom rom for the centura onto the discover...it is the 730g. i did not make a back up...do you have the stock rom and can you post or email it to me?? [email protected]
:crying:
j.nunez123 said:
i mistakingly picked up the wrong phone..the discover and the centura are very similar....i accidently installed custom rom for the centura onto the discover...it is the 730g. i did not make a back up...do you have the stock rom and can you post or email it to me?? [email protected]
:crying:
Click to expand...
Click to collapse
Right now I do not have a copy of the stock rom. I'm still trying to create an Odin flashable of the basic system partition files, recovery, and boot. Wish I could help you. This is why it's always important to make a backup. You might can try one of the 730M Discover threads and see if someone can send you a back up of theirs, but keep in mind that is the Canadian version of the phone. I'm not quite sure what all of the differences in them are.
Based on what I have been able to find out, other than the tracfone custom boot screen and sound, the android on this phone is just stock android 4. No touchwiz (thank God and all that it holy) no bloatware extras, no nothing. So you could probably take the stock Android 4.0.4 I think it is and work from that.
Sent from my SGH-S730G using xda app-developers app
little trouble
Ive downloaded everyting just fine, but when I try and install the unlockroot it keeps telling me Better installer host has stopped working. Is that something on my end or something on theirs? because i cant seem to figure anything out about better installer and have never seen it before downloading this. You have any suggestions on what is causing this problem?
[sgh-s730g] Discover Straight talk PR Rooted
I will reccomend you to start over as it is in [Root] [CWM] Samgsung Galaxy Discover (SGH-730G) Tracfone Variant ONLYthread, which is in the first page. Do a factory reset if it can be done, and wipe all the catches. format your sd card and be patient, because i followed all the instructions and mine works fine. the only thing i haven't done is get rid of the yellow triangle but I'll doit later on because I'm Working to find the unlocking code for mine. Wish you luck and do be afraid. Just be Patient :good:
Cristiandando said:
I will reccomend you to start over as it is in [Root] [CWM] Samgsung Galaxy Discover (SGH-730G) Tracfone Variant ONLYthread, which is in the first page. Do a factory reset if it can be done, and wipe all the catches. format your sd card and be patient, because i followed all the instructions and mine works fine. the only thing i haven't done is get rid of the yellow triangle but I'll doit later on because I'm Working to find the unlocking code for mine. Wish you luck and do be afraid. Just be Patient :good:
Click to expand...
Click to collapse
I am getting this error on my computer not on my cell phone, My cell is a discover from straight talk. when i downloaded unlockroot from their website onto my computer and go to run it it wont even install. just keeps saying better installer stopped working. Again this is on my computer not on my cell phone.
Uninstall then re-download UnlockRoot .. I had that problem first time I tried to run it. Also, there is the actual free program, amd another program file that pulls up an order and download program for the pro version. Maybe you clicked that one instead?
Sent from my SGH-S730G
I have a debloated, deodexed, zip aligned, rooted version of the stock rom completed. Working on the updater script which is being a pain in my ass. Soon as it is done and tested I'll post it.
I've been behind on it as my volunteer work and family obligations have been my primary focus. But it is something I still try to work on to give this phone a little boost.
Sent from my SGH-S730G
Here it's what you're looking for my Friend
pokesmot88 said:
I am getting this error on my computer not on my cell phone, My cell is a discover from straight talk. when i downloaded unlockroot from their website onto my computer and go to run it it wont even install. just keeps saying better installer stopped working. Again this is on my computer not on my cell phone.
Click to expand...
Click to collapse
Il' PM you the unlock root pro with the serial because I can't post it until I make 10 or more post. Download both items, install the software and then copy > paste the serial and start rooting your phone. Don't forguet to make a back up of your original not rooted rom and save it in your computer and sd card in case something goes wrong just restore it to it's original state.
TheGeekyNimrod said:
I have a debloated, deodexed, zip aligned, rooted version of the stock rom completed. Working on the updater script which is being a pain in my ass. Soon as it is done and tested I'll post it.
I've been behind on it as my volunteer work and family obligations have been my primary focus. But it is something I still try to work on to give this phone a little boost.
Sent from my SGH-S730G
Click to expand...
Click to collapse
I have a SGH-S730M that I bought unlocked off of ebay, and wound up giving it to my wife. After looking at the specs for the SGH-S730G it sounds like they are identical other than one being sold by Telus and the other being sold by net10. Is the SGH-730G unlocked by default? I'm interested in getting one to try my hand at modifying. One of my few key complaints about the SGH-S730M was that even though it didn't have the touchwiz launcher it still had the samsung style lock screen instead of the stock ICS lock screen. Would xposed or any of the other stuff you mentioned allow me to change that back to stock?
Also the battery issue you mentioned also seems to affect the S730M as well, it is more than a little annoying.
doctor_evil said:
I have a SGH-S730M that I bought unlocked off of ebay, and wound up giving it to my wife. After looking at the specs for the SGH-S730G it sounds like they are identical other than one being sold by Telus and the other being sold by net10. Is the SGH-730G unlocked by default? I'm interested in getting one to try my hand at modifying. One of my few key complaints about the SGH-S730M was that even though it didn't have the touchwiz launcher it still had the samsung style lock screen instead of the stock ICS lock screen. Would xposed or any of the other stuff you mentioned allow me to change that back to stock?
Also the battery issue you mentioned also seems to affect the S730M as well, it is more than a little annoying.
Click to expand...
Click to collapse
They are pretty much the same device yes. The 730G I bought was through StraightTalk so it wasn't unlocked. I'm sure you could find one unlocked on Ebay or maybe Swappa or something similar. I do hate the Samsung stock lockscreen too. Stock, Xposed won't do the AOSP lockscreen style. Once I have the deodexed working and ready it should. There is another way to bring it up, but it's a little beyond my experience, but also requires a deodexed system.
TheGeekyNimrod said:
They are pretty much the same device yes. The 730G I bought was through StraightTalk so it wasn't unlocked. I'm sure you could find one unlocked on Ebay or maybe Swappa or something similar. I do hate the Samsung stock lockscreen too. Stock, Xposed won't do the AOSP lockscreen style. Once I have the deodexed working and ready it should. There is another way to bring it up, but it's a little beyond my experience, but also requires a deodexed system.
Click to expand...
Click to collapse
Cool I will be watching this thread for updates. I just bought a used SGH-730G that I am willing to do test flashes on the rom if you need a tester. I got it for a super super cheap price so I won't get upset if it gets bricked.
So basically I did this:
http://forum.xda-developers.com/showthread.php?t=2538991
But unfortunately, I hadn't realized that the mobile hotspot was sealed up in that update. So I looked it up, and saw that someone had recommended this:
http://forum.xda-developers.com/showthread.php?p=48326067
So I went into TWRP and installed it. But that didn't work. When I booted back up EVERY app was crashing immediately except the stock Samsung apps (Messaging, Email, etc.). I tried to reverse it with the original framework-res.apk but when I did, the phone would get stuck at the AT&T logo (which was silent). I went back and forth a few times (when I applied that tethering mod, the phone would boot; when I tried to reverse it, it wouldn't), then did a factory reset in TWRP. After that, the phone booted, but the Setup Wizard would crash. So I did a Nandroid restore in TWRP and now the phone hangs at the AT&T logo no matter what I do.
My question is, what can I do now? I have a replacement device coming through warranty just in case, but it would be much better to just fix this one. However, I want to be certain and not HARD brick the phone...
I have never been able to restore a stock 4.3 nandroid without everything crashing. I have always had to go back into recovery and wipe data/factory reset and wipe cache and dalvik cache then reboot and go through the whole setup process again. If that doesn't work you could try installing the stock debloat ROM from this thread. That's what I am running and it works great. http://forum.xda-developers.com/showthread.php?t=2540998
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Iantuition said:
So basically I did this:
http://forum.xda-developers.com/showthread.php?t=2538991
But unfortunately, I hadn't realized that the mobile hotspot was sealed up in that update. So I looked it up, and saw that someone had recommended this:
http://forum.xda-developers.com/showthread.php?p=48326067
So I went into TWRP and installed it. But that didn't work. When I booted back up EVERY app was crashing immediately except the stock Samsung apps (Messaging, Email, etc.). I tried to reverse it with the original framework-res.apk but when I did, the phone would get stuck at the AT&T logo (which was silent). I went back and forth a few times (when I applied that tethering mod, the phone would boot; when I tried to reverse it, it wouldn't), then did a factory reset in TWRP. After that, the phone booted, but the Setup Wizard would crash. So I did a Nandroid restore in TWRP and now the phone hangs at the AT&T logo no matter what I do.
My question is, what can I do now? I have a replacement device coming through warranty just in case, but it would be much better to just fix this one. However, I want to be certain and not HARD brick the phone...
Click to expand...
Click to collapse
if you can get back to twrp , clear everything then flash the official correct file that yu want then see if that works...restore your apps/data after a clean refresh for your phone
remember panicking and being paranoid with flashing/rooting is not a a good idea, always rethink what you did wrong, let the phone cool down, research know what you re doing then fix it
dont rush, cuz rushing leads to bricks (learned from experience from day 1 with root)
bellifritz said:
I have never been able to restore a stock 4.3 nandroid without everything crashing. I have always had to go back into recovery and wipe data/factory reset and wipe cache and dalvik cache then reboot and go through the whole setup process again. If that doesn't work you could try installing the stock debloat ROM from this thread. That's what I am running and it works great. http://forum.xda-developers.com/showthread.php?t=2540998
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
How'd you do that? Just the regular factory reset? Cause the setup wizard wouldn't even run after that.
winosxbuntu said:
if you can get back to twrp , clear everything then flash the official correct file that yu want then see if that works...restore your apps/data after a clean refresh for your phone
remember panicking and being paranoid with flashing/rooting is not a a good idea, always rethink what you did wrong, let the phone cool down, research know what you re doing then fix it
dont rush, cuz rushing leads to bricks (learned from experience from day 1 with root)
Click to expand...
Click to collapse
Okay. Which official file though? and should I clear the system and boot partitions too?
Iantuition said:
How'd you do that? Just the regular factory reset? Cause the setup wizard wouldn't even run after that.
Okay. Which official file though? and should I clear the system and boot partitions too?
Click to expand...
Click to collapse
try this two links, everything on flashing 4.3 stock/rooting and fix http://forum.xda-developers.com/showthread.php?t=2540998
http://forum.xda-developers.com/showpost.php?p=46804338
either one will work
AND dont clear everything just cache/dalvik/format system/ factory reset BUT follow the instructions given for that rom to avoid any problems
winosxbuntu said:
try this two links, everything on flashing 4.3 stock/rooting and fix http://forum.xda-developers.com/showthread.php?t=2540998
http://forum.xda-developers.com/showpost.php?p=46804338
either one will work
AND dont clear everything just cache/dalvik/format system/ factory reset BUT follow the instructions given for that rom to avoid any problems
Click to expand...
Click to collapse
Okay so I just leave boot alone. Let us pray, LOL. And sorry if I've sounded like a supernoob but I'm trying to be REALLY careful.
Iantuition said:
How'd you do that? Just the regular factory reset? Cause the setup wizard wouldn't even run after that.
Hit the power button to make the screen go to sleep. Hit the power button again to wake it up. Nothing should be crashing while you are on the lock screen so just hold the power button until the power menu appears and select power off. Once it powers off hold the volume up, home button and power button until you see the blue words in the upper left corner of the screen I believe it says loading recovery. Release the power button but continue holding the other 2 buttons until recovery loads. Now wipe data, cache and under advanced wipe dalvik cache. Reboot and everything should quit crashing but you will have to setup your account and apps again. That is the only way that I can get stock touchwiz 4.3 nandroids to work.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Iantuition said:
Okay so I just leave boot alone. Let us pray, LOL. And sorry if I've sounded like a supernoob but I'm trying to be REALLY careful.
Click to expand...
Click to collapse
it will work, i agree with what bell said. unless its hard bricked then no worries just keep calm and fix the damn phone
Hi folks, long time reader, first time noob answer seeker.
I'm no stranger to rooting, flashing, hacking about and such - I even spend most of my day as a software engineer, and I've finally given up on this one - so here I am (rock me like a hurricane), please be kind.
SM-900T - It was rocking pretty darn well on Jedi Elite which I had flashed over rooted stock 4.3 MI7 - then (probably after one too many XPosed modules) it just kept rebooting randomly. Thinking it was no biggie, I thought I could just reflash to stock and call it a day. Thirteen or so flashes later, I gave up on 4.3 and figured I'd just take the thing up to 4.4.2 NB4 by upgrading everything to 4.4.2 via Kies.
That's when I first ran into the bootloop issue, read a lot about it, and managed to get it up(ish) on stock, rooted, with Philz 6.X... Couldn't flash a ROM to save myself and wound up with another soft brick.
Flash forward to Friday - decided to start from scratch again - attempted to flash stock 4.4.2 from Kies, from Odin, From Heimdall... Nothing seems to be able to get me out of the current state it's in:
Only boots to download mode. Flashes seem to work fine, but on that first reboot where it tries to go to stock recovery to finish up on the device itself, it never gets there - boot loops trying to load recovery no matter how it wants to get there. If I pull the battery and start up (either straight to system or by cancelling out of download mode), it boot loops trying to load system. Boots fine to download mode, where I attempt to flash again with the same results.
Yes, I've tried Odin 3.0.9, 3.0.7, 1.8.5, Heimdall on Mac, Heimdall on Windows, Kies on Mac, Kies on Windows - repartition via PIT and not. Installed, uninstalled, and reinstalled all software and drivers multiple times, tried multiple cables on multiple USB ports.... Most of the time it looks like it's going to be fine (sometimes the flash fails, usually through Kies), but never surivives that first reboot after the flash.
Every answer I've seen says to do the things I've already done or cannot do (flash stock via Odin, pull the battery and boot to stock recovery and do a factory reset - which I'd LOVE to do, but can't). No problem recognizing the sucker on the PC/Mac
Next step: try flashing a N9005 ROM...
Any other thoughts? I do have another N900T that's working but has a blacklisted IMEI, and I've been tempted to swap the IMEIs a last resort (although either I'm too dumb to make it stick, EFS pro says it succeeds in writing the IMEI after I do a EFS format, but it doesn't stick.... Either I'm missing something, or I need a UART cable) - is there a way of swapping just the radio hardware or just the internal storage? OR, is there a way of taking a full system image of my working phone and making an Odin-flashable tar from that?
Failing any of these options, perhaps I'll wait for an Odin-flashable 4.4.3 if such a thing exists - or, hope to get lucky and swap it out at a store praying they don't see I've tripped Knox.
Looks like you've tried almost everything. Take it in and have them swap it.
Sent from my SM-G900T using Tapatalk
Coming from you...
noobtoob said:
Looks like you've tried almost everything. Take it in and have them swap it.
Click to expand...
Click to collapse
Coming from you (I have read, and am quite thankful for, many of your posts), sounds like that might be the best option, however disconcerting.
bondidave said:
Coming from you (I have read, and am quite thankful for, many of your posts), sounds like that might be the best option, however disconcerting.
Click to expand...
Click to collapse
Well, I do have a few ideas... Got done questions though.
1. Do you have an external SD card?
2. It goes all the way through flash on 4.4 even with heimdall?
3. Is there anything you have left out? Even the smallest detail can help, and by the op you are detail oriented, so I just need to know.
Sent from my SM-G900T using Tapatalk
... is there a way of taking a full system image of my working phone and making an Odin-flashable tar from that?
Click to expand...
Click to collapse
Yes, but I don't have the details handy.
All your attempts suggest to me that you might have some damaged hardware which is causing data corruption during transfer. Open the back and take a good look at the USB port. Tighten the screws and try a transfer while firmly holding the cable in place -- don't move it while transferring.
If that doesn't work then let 'noobtoob' walk you through booting with the removable sdcard. Your second N900T will be needed to write the data to the sdcard. If this works then you can 'dd' write stock partitions to an sd card with #2 then 'dd' write them in #1.
If either of those works then unroot and take it in for warrenty exchange.
Frank
bondidave said:
... then (probably after one too many XPosed modules) it just kept rebooting randomly.
Click to expand...
Click to collapse
This also indicates data corruption, and this is what started it all. Since you have tried various cables and computers that leaves the device, probably the USB port.
Frank
probably the USB port.
Click to expand...
Click to collapse
Swapped the main board with the working phone to rule out the USB port - still no luck.
Definitely interested in trying the boot from external SD, I'll do my own search for it, unless you can quickly provide me with a link - but if it's as easy as it sounds (booting off of an SD in order to be able to send ADB commands to dd copy the partitions from the good phone to SD then from the booted SD back to internal) - I'm happy to give it a shot.
Tempted just to swing by TMO just to see if they'll swap it "under warranty" (despite picking it up from a private sale) - the only way they would notice it's been "tampered" with would be to check the knox counter by attempting to run download mode.
Oh, and yes, it does go all the way through with the flash (at least in Odin - I haven't tried a full flash through heimdall, just boot and recovery, Kies occasionally goes through to the end, but sometimes craps out at the same 57% point at which point the emergency restore screen shows up)
Thanks again guys
bondidave said:
Swapped the main board with the working phone to rule out the USB port - still no luck.
Click to expand...
Click to collapse
OK, but I still think the problem was initially caused by corruption. Maybe the files you have been flashing are corrupt.
Definitely interested in trying the boot from external SD, I'll do my own search for it, unless you can quickly provide me with a link - but if it's as easy as it sounds (booting off of an SD in order to be able to send ADB commands to dd copy the partitions from the good phone to SD then from the booted SD back to internal) - I'm happy to give it a shot.
Click to expand...
Click to collapse
This is the thread, it would be good to read the whole thing but if you need to save time begin at this message: http://forum.xda-developers.com/showpost.php?p=48685247&postcount=158
I have not tried this procedure yet but @noobtoob was actively involved in it.
Tempted just to swing by TMO just to see if they'll swap it "under warranty" (despite picking it up from a private sale) - the only way they would notice it's been "tampered" with would be to check the knox counter by attempting to run download mode.
Click to expand...
Click to collapse
Please try the SD-boot first so that we can add that experience to this newly developed procedure.
Oh, and yes, it does go all the way through with the flash (at least in Odin - I haven't tried a full flash through heimdall, just boot and recovery, Kies occasionally goes through to the end, but sometimes craps out at the same 57% point at which point the emergency restore screen shows up)
Click to expand...
Click to collapse
You have probably tried it, but if not, download fresh copies of everything and check the MD5 values.
Frank
Frank Westlake said:
OK, but I still think the problem was initially caused by corruption. Maybe the files you have been flashing are corrupt.
This is the thread, it would be good to read the whole thing but if you need to save time begin at this message: http://forum.xda-developers.com/showpost.php?p=48685247&postcount=158
I have not tried this procedure yet but @noobtoob was actively involved in it.
Please try the SD-boot first so that we can add that experience to this newly developed procedure.
You have probably tried it, but if not, download fresh copies of everything and check the MD5 values.
Frank
Click to expand...
Click to collapse
This was for hard brick method and no one has verified it works on 4.4 KK yet. There is an image in there though. My mediafire shows it was downloaded 11 times, but yet not a single "this works on KitKat" response. Located here you will find the kkunbrick.img. There is still a problem flashing anything through heimdall after updating to the 4.4 bootloader, so there is no way to tell if the phone actually took the recovery. I have had to switch to Odin for everything afterwards, and in personal experience 3.07 works best with my phone.
@bondidave I was thinking skipping the sd-card trick for now, and trying just a few other things first. Do you have a nandroid of any 4.4 ROMS saved anywhere? I was going to say try and flash the stock image. After it gets through flash and tries to boot into recovery, go back directly to download mode. Flash philz or twrp, whatever you need to. Try and perform a recovery boot, wipe everything, and nandroid restore of a 4.4 if you have one.
Also if you have an external find the efs fix zip and have handy on an sd-card, do the same steps above except the nandroid restore. Basically if we can get into a recovery we should be ok. I had a similar issue when it was just booting over and over into download mode and this was how I fixed it. I have never used the efs fix zip, but many others swear by it. I was able to recover fortunately enough.
Last resort try the sd-card boot. I don't necessarily think it will work with this particular case as you do not have the dreaded QHUSB_MODE and your phone is still recognized by the computer(s) you have been using.
As far as making a complete system backup of your current phone, I highly recommend against it, unless you just want to extract information from it and not re-write it. This could definitely cause some system corruption on a new device.
If none of these methods work, then try and have them swap it under warranty.
Frank Westlake said:
You have probably tried it, but if not, download fresh copies of everything and check the MD5 values
Click to expand...
Click to collapse
Yessirreeebobbyjimmy, tried several copies from several different places - that and Kies is a moron and redownloads it every time anyways.
noobtoob said:
My mediafire shows it was downloaded 11 times, but yet not a single "this works on KitKat" response.
Click to expand...
Click to collapse
I download these things just to have them handy if something fails.
Do you have a nandroid of any 4.4 ROMS saved anywhere? I was going to say try and flash the stock image. After it gets through flash and tries to boot into recovery, go back directly to download mode. Flash philz or twrp, whatever you need to. Try and perform a recovery boot, wipe everything, and nandroid restore of a 4.4 if you have one.
Click to expand...
Click to collapse
I don't think he got that far into installing 4.4, but I recommend not using anything that was saved after this problem began. If the problem was caused by corruption then the restore will reinstall the corruption.
Last resort try the sd-card boot. I don't necessarily think it will work with this particular case as you do not have the dreaded QHUSB_MODE and your phone is still recognized by the computer(s) you have been using.
Click to expand...
Click to collapse
If the problem is bad USB or other bad hardware causing corruption during transfer then the SD-card boot will get past that, then transferring the rest of the partitions by SD-card will continue to be corruption-free. He could then trade-in the phone.
But you are right -- he should try everything else before the SD-card boot. Because if something else succeeds then maybe the hardware is fine, and if he went immediately to SD-card boot he wouldn't know that.
Frank
Thanks for the advice guys - I'm going to try the backup from my other phone, then the efs fix, then the sd-card boot... I'll report back, wish me luck.
A nandroid previous failure, or a ROM install from external SD card was all I meant.
Sent from my SM-G900T using Tapatalk
I got some answers I was looking for here. Glad I read this thread.
Lorettaa said:
I got some answers I was looking for here. Glad I read this thread.
Click to expand...
Click to collapse
Glad something good came out of my frustration!
Here's a quick update: I've done everything but the boot from SD card with no luck (and actually thought I had hard(er?) bricked it for a while after trying to copy over a few images from the other phone - turns out it needed to stay with the battery out for at least 20 minutes).
Good news - walked into a TMO brick-and-mortar last night, showed the guy my endless bootloop, and a replacement is on its way to my house for an affordable $20 warranty service fee.
At this point, I'm thinking the internal flash memory is just bad - as a software engineer, I'm ok with chalking this one up to a hardware issue (as much as I was hoping that my first post on XDA would result in some new profound solution to a longstanding issue common to a few folks).
Oh well - new Note 3 on it's way, and a new S5 shortly behind it (didn't hold out much hope on TMO hooking me up, so I ordered an S5)... let the battle of the Samsungs begin!
Thanks again to you guys who helped out - and the whole XDA community in general, I am very grateful.
Finally you made it fix and enjoy the battle between your phones
Well, sucks it couldn't be fixed, but glad you got a replacement on the way. It pretty much sounded like the partitions were well over written before we attempted anything, but always worth a shot.
Sent from my SM-G900T using Tapatalk
Yes, but I don't have the details handy.
All your attempts suggest to me that you might have some damaged hardware which is causing data corruption during transfer. Open the back and take a good look at the USB port. Tighten the screws and try a transfer while firmly holding the cable in place -- don't move it while transferring. :good: