Develop Bugs

[SPH-L900] CF-Auto-Root

Check your device model ! Settings -> About device -> Model number. This stuff is made for the SPH-L900, if your model number has a suffix, it may not work, or if it is a totally different model, it will not work (may even brick) !
CF-Root is the root for "rooting beginners" and those who want to keep as close to stock as possible. CF-Root is meant to be used in combination with stock Samsung firmwares, and be the quickest and easiest way for your first root.
Donate
CF-Root has been available for many device (Galaxy S1, Galaxy Tab 7", Galaxy S2, Galaxy Note, Galaxy Nexus, Galaxy S3) and has clocked over 8 million downloads. This is not even counting custom ROMs that already include it. Don't be a leech, buy me a beer (and use the "Thanks" button!). Imagine if every CF-Root user has donated me $1...
What's installed
- SuperSU binary and APK
- Stock recovery
Installation and usage
Flash the CF-Auto-Root package as PDA in ODIN (details on how to do that are in next post), and your device should reboot into a modified recovery (signified by a large red Android logo) and it will install SuperSU for you and restore the stock recovery, and reboot back into Android.
If you don't get to the red Android logo, boot into recovery manually ("adb reboot recovery", or boot while holding Power+VolUp+Home).
Using this root increases your flash counter. You should run Triangle Away (see below) after rooting to reset the counter. Note that if you want to run custom kernels or custom recoveries, your flash counter will be set to 1 at every boot. Either configure Triangle Away to reset the counter at every boot (Play version only) or only reset the counter when you need to go into warranty.
Did you see the red Android logo during rooting, but SuperSU does not appear? This may sometimes occur due to left-over files and settings, however, you can usually install SuperSU from Google Play at this stage and it'll just work.
Not included - Triangle Away
Triangle Away can be used to reset the flash counter after installing CF-Root. The flash counter keeps track of how many custom firmwares you have flashed, as this voids warranty. (No idea what this about ? Read up on it, you will want to use this !)
Not included - adbd Insecure
As this CF-Root does not include a custom kernel, adb shell does not have root access by default (you can still get it by typing su inside the shell), nor is adb remount supported, nor will adb push and adb pull work on system files. adbd Insecure can be used to remedy this situation. (No idea what this is about ? Don't worry about it !)
CF-Auto-Root homepage
http://autoroot.chainfire.eu/
CF-Auto-Root main thread
[CENTRAL] CF-Auto-Root
For requests for new roots and generic discussion - please keep device specific discussion in the thread you are viewing now.

ODIN Installation (detailed)
- Follow these instructions to the letter. Do not touch any buttons or checkboxes that are not listed below to touch!
- Unzip the attached Odin3-vX.X.zip file
- Download and unzip the CF-Auto-Root-....zip file (see posts below this one)
- If you end up with a recovery.img and cache.img file, you've extracted twice. You need to end up with a .tar.md5 file - don't extract that one
- (USB) Disconnect your phone from your computer
- Start Odin3-vX.X.exe
- Click the PDA button, and select CF-Auto-Root-....tar.md5
- Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue, press the listed button, or run adb reboot download command)
- (USB) Connect the phone to your computer
- Make sure Repartition is NOT checked
- Click the Start button
- Wait for Android to boot
- Done (if it took you more than 30 seconds, you need practise!)
- NOTE: Sometimes the device does *not* boot into recovery mode and root your device. Just do the entire procedure again if this happens. If it still will not install root and such, make sure that in Odin "Auto Reboot" is not checked. Then after flashing, pull the battery, and boot with VolUp+Home+Power button to boot into recovery manually. This will start the install process.
New to Samsung? Unfamiliar with Odin? Think all the above is a hassle? Get used to it. It's very simple, and us Samsung folk use Odin (or Mobile ODIN ) for everything! It's so very very convenient once you get used to it. Notice the 30 second comment above? For experienced users, the entire process indeed takes only 30 seconds!
You may now optionally want to install and run Triangle Away to reset the flash counter.

Download
2013.05.20 --- CF-Auto-Root
SuperSU: v1.30
Download: CF-Auto-Root-t0ltespr-t0ltespr-sphl900.zip
--- History ---
2013.05.20: SuperSU v1.30
2013.02.20: SuperSU v1.05
2012.12.02: SuperSU v0.98
2012.10.31: SuperSU v0.96

Thanks for ALL you do!
Imagine if every CF-Root user has donated me $1...
Click to expand...
Click to collapse
I just made up for myself and a couple of others.

Thanks much

rooted. awesome. thanks

Thanks Chainfire! You are God!
Conf: 3GC122393T563813M

Rooted here as well!
Thanks!

So, how long should it take to reboot? Last message I see in Odin is all threads completed. (succeed 0 / failed 0) and phone is still in downloading... Been 15 minutes now.

Should take seconds.
Did it boot into recovery?
With 0 succeed, something went wrong

rwright64 said:
Should take seconds.
Did it boot into recovery?
Click to expand...
Click to collapse
It just sits at Downloading the whole time. Phone is in Odin mode.

Flak said:
It just sits at Downloading the whole time. Phone is in Odin mode.
Click to expand...
Click to collapse
Start from the beginning and do it exactly as it says. Maybe you missed something?
Did odin show that you were connected?

scrosler said:
Thanks Chainfire! You are God!
Click to expand...
Click to collapse
Ohh ****, we getting some cleanrom love?
---------- Post added at 02:16 AM ---------- Previous post was at 02:06 AM ----------
So, note to myself and anyone else. If you use the universal driver package for everything, they no workie for the Note 2 (though they do install successfully). Grabbed the driver package from Samsung and root went fine.
Thanks and sorry for causing a stir.

Flak said:
Ohh ****, we getting some cleanrom love?
---------- Post added at 02:16 AM ---------- Previous post was at 02:06 AM ----------
So, note to myself and anyone else. If you use the universal driver package for everything, they no workie for the Note 2 (though they do install successfully). Grabbed the driver package from Samsung and root went fine.
Thanks and sorry for causing a stir.
Click to expand...
Click to collapse
Glad everything went okay!
Sent from my SPH-L900 using xda premium

Took 30 secs just like Chainfire said!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

OMG! Thank you! Took about the 30 seconds as advertised. I did have Samsung drivers already installed and this is coming from an 8 year HTC user.

@chains anything you need?
Sent from my SPH-D710 using Tapatalk 2

def DID NOT WORK until i installed samsung drivers from their site..then everything went smooth
heres the direct link for those who need it
http://downloadcenter.samsung.com/c..._L900_Note_II_Samsung_USB_Driver_v1_4_6_0.exe

yeah you need samsung drivers. if youre coming from a previous samsung phone like me they should already be installed if not you need to go download them

sextape said:
@chains anything you need?
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Whatever latest tar you have would be great. When we were working on root, I know he mentioned he would like a stock recovery.img from the software the device launched on. Not to bother you further about releasing the tar, but it really is essential for people that screw something up. I made a system dump of my phone and tar'd it for use with Odin, but I didn't get to test it.
Sent from my SPH-L900 using Tapatalk 2

[URGENT] Stuck on "Firmware Upgrade Encountered an Issue"

Hello XDA, haven't been on these forums for a while.
I have a slight issue with a Galaxy SIII I just picked up off a friend.
The S3 goes to this screen every time I try to boot it with the power button:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And I AM able to get to the download mode screen:
I've tried to flash a Stock Rooted Firmware onto the phone using Odin 3.07, and all it does is say it failed.
Another thing to note is that I CAN'T boot into recovery, and that I do not have Clockworkmod installed.
Also, I am not sure if my device is rooted as it was given to me by someone else..
Any help on trying to solve this issue will be much appreciated!! Thank you! ��
EDIT: if you can't see the images for some reason, it is just a photo of the "Firmware Upgrade Encountered an Issue" screen and a photo of the download mode screen.
More info:
ODIN MODE
PRODUCT NAME: SGH-T999
CUSTOM BINARY DOWNLOAD: Yes (4 counts)
CURRENT BINARY: custom
SYSTEM STATUS: official
QUALCOMM SECURE BOOT ENABLE

When you try to flash with Odin, what does it say in the message box after it fails?
Also, what firmware are you trying to flash?

DocHoliday77 said:
When you try to flash with Odin, what does it say in the message box after it fails?
Also, what firmware are you trying to flash?
Click to expand...
Click to collapse
This is the firmware I am trying to flash: root66_TMO_T999UVDLJA.tar.md5
It's basically a rooted stock ROM for the SIII T-Mobile.
And this is the message I receive when trying to flash:
Please note I have tried to flash other firmwares as well, getting the same message.
One thing that DID work was flashing a custom recovery through odin.
Thanks for the reply!

UPDATE:
I've now gotten the phone to get stuck at the Samsung boot logo (the one where it glows blue) instead of giving me the firmware issue message.
I did this by flashing CWM through odin. In Odin, it said the flash was successful but when I boot into recovery on my phone, it just goes to the stock Samsung recovery.
One thing I did notice was that when I try to factory reset the phone, it gives me a BUNCH of errors in red text.. doesn't seem normal.
Thanks again!

Yeah. Im afraid that doesn't sound good. But before getting too negative, try flashing the firmware again, but this time use the PIT file as well. In case the local one on your device is corrupted, use one from our thread in the General section.
http://forum.xda-developers.com/showthread.php?t=1848267
Download the correct one for your device. If the link in the op isn't working check my last few posts for a mirror.
Now in Odin do exactly as before, but also click the PIT button and select the file you just downloaded. Then make sure that re-partition is checked. Click start.
If something corrupted your partition layout, theres a chance this will fix it. If it doesn't work, theres a good possibility the memory is going bad....

DocHoliday77 said:
Yeah. Im afraid that doesn't sound good. But before getting too negative, try flashing the firmware again, but this time use the PIT file as well. In case the local one on your device is corrupted, use one from our thread in the General section.
http://forum.xda-developers.com/showthread.php?t=1848267
Download the correct one for your device. If the link in the op isn't working check my last few posts for a mirror.
Now in Odin do exactly as before, but also click the PIT button and select the file you just downloaded. Then make sure that re-partition is checked. Click start.
If something corrupted your partition layout, theres a chance this will fix it. If it doesn't work, theres a good possibility the memory is going bad....
Click to expand...
Click to collapse
Same thing happens this time, same error message. It seemed like the PIT file did not make a difference at all..
BUT! Now, I went into the stock recovery and tried to do a factory reset. NO ERRORS!
And when it began to boot, it made the little ringtone "jingle" and FINALLY BOOTED UP TO THE SETUP SCREEN!!
YOU, MY FRIEND, ARE AMAZING. THANK YOU SO MUCH!!
So for all future references: the PIT file may seem to do nothing at all, but once you do a factory reset it will work like a charm.
Once again, thanks! Bought the phone for $20, now I can sell it for around $100, lol.

Glad i could help!

[GUIDE] How to Update Bootloader & Modem

I've seen this asked a lot. People try and flash the new modem and/or bootloader on their rooted devices, and neither stick. Why?
The Note 3 bootloader is programmed in such a way that it will refuse to accept a new modem if the binary is marked as CUSTOM instead of SAMSUNG OFFICIAL in the bootloader. The thing that the bootloader checks for is the kernel. Meaning the kernel you have to have in order to flash the modem is the stock one. However, we're all pretty much already on custom ROMs with custom kernels, so it says custom even if you flash back the stock kernel.
How to flash a new modem and/or bootloader:
1. Flash the stock kernel via ODIN or some other method
2. Download and run Triangle Away
3. The phone will shut off after running the app. Reboot into Recovery mode normally (Hold Volume Up + Home after you feel the initial vibration)
4. When the Triangle Away menu comes up, hit Volume Up to reset the phone to "OFFICIAL" (nothing is erased or modified except for that, don't worry).
5. Press Volume Down to go straight to Download mode. You'll see it says SAMSUNG OFFICIAL next to System Binary.
6. You can ODIN over the modem.bin and/or the bootloader file (both in one shot works) now, or you can use Mobile Odin just for the modem file if you have it/want to. ODIN's easier.
I just did this. It's my second time updating a modem on this phone. It worked the last time and it worked this time.
Proof (the last two are my custom ROM, which is NF1 based. So ignore those):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Product F(RED) said:
I've seen this asked a lot. People try and flash the new modem and/or bootloader on their rooted devices, and neither stick. Why?
The Note 3 bootloader is programmed in such a way that it will refuse to accept a new modem if the binary is marked as CUSTOM instead of SAMSUNG OFFICIAL in the bootloader. The thing that the bootloader checks for is the kernel. Meaning the kernel you have to have in order to flash the modem is the stock one. However, we're all pretty much already on custom ROMs with custom kernels, so it says custom even if you flash back the stock kernel.
How to flash a new modem and/or bootloader:
1. Flash the stock kernel via ODIN or some other method
2. Download and run Triangle Away
3. The phone will shut off after running the app. Reboot into Recovery mode normally (Volume Up + Home after you feel the initial vibration)
4. When the Triangle Away menu comes up, hit Volume Up to reset the phone to "OFFICIAL" (nothing is erased or modified except for that, don't worry).
5. Press Volume Down to go straight to Download mode. You'll see it says SAMSUNG OFFICIAL next to System Binary.
6. You can ODIN over the modem.bin and/or the bootloader file (both in one shot works) now, or you can use Mobile Odin just for the modem file if you have it/want to. ODIN's easier.
I just did this. It's my second time updating a modem on this phone. It worked the last time and it worked this time.
Proof (the last two are my custom ROM, which is NF1 based. So ignore those):
Click to expand...
Click to collapse
So what you are saying is that what I have done with my phone for the last 3 new firmwares shouldn't be possible.
I have been on CM11(temasek's version) for about 8 months, and I have upgraded my modem and bootloader only, never flashing the full firmware, and never using Triangle away.
I always turn my phone completely off, take battery out, put battery in, use three button combo to enter download mode, plug phone into computer and odin flash JUST the modem and bootloader, reboot my phone, and BOOM, profit!
You can't odin flash the modem and bootloader and get them to stick if you use the OS or a reboot application to enter download mode. Theory has been proven, and it is this way on the S5 also.
Your theory is just that...a theory.

idtheftvictim said:
So what you are saying is that what I have done with my phone for the last 3 new firmwares shouldn't be possible.
I have been on CM11(temasek's version) for about 8 months, and I have upgraded my modem and bootloader only, never flashing the full firmware, and never using Triangle away.
I always turn my phone completely off, take battery out, put battery in, use three button combo to enter download mode, plug phone into computer and odin flash JUST the modem and bootloader, reboot my phone, and BOOM, profit!
You can't odin flash the modem and bootloader and get them to stick if you use the OS or a reboot application to enter download mode. Theory has been proven, and it is this way on the S5 also.
Your theory is just that...a theory.
Click to expand...
Click to collapse
Enough people have had trouble updating their Note 3's after flashing a custom ROM that my theory holds true. Your situation, while interesting, is an outlier.
Also I never said you had to flash the full firmware...
Sent from my SM-N900T using Tapatalk

Product F(RED) said:
Enough people have had trouble updating their Note 3's after flashing a custom ROM that my theory holds true. Your situation, while interesting, is an outlier.
Also I never said you had to flash the full firmware...
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Flashing the full firmware should still work right?
Only when flashing a new modem and/or bootloader is when it may not always stick, right?

Thugnificent69 said:
Flashing the full firmware should still work right?
Only when flashing a new modem and/or bootloader is when it may not always stick, right?
Click to expand...
Click to collapse
If the system binary says "CUSTOM", I believe it's permanent unless you use Triangle Away. So you would need to flash a stock kernel, use Triangle Away, and then flash the full firmware. If you were to just flash the full firmware, the firmware would update, but the bootloader and modem would not.
I believe (emphasis on believe) the reason is that the bootloader flag (CUSTOM when you flash a custom kernel/ROM) is there for security. Meaning, if someone tampered with the phone, there's a good chance something was compromised (in say, a business situation). So Samsung programmed the phone to restrict updating the modem and bootloader (which may have been modified maliciously) in order to preserve any evidence. Again, it seems like a totally farfetched theory, I know. But that's what I think.

Different Software, Baseband, Bootloader After Flashing ROM

I just checked my phone with Galaxy Tools and it's showing a different version for the software, baseband, and bootloader.
The ROM is the Sprint Hybrid-X 3.0 COG5...could this cause a problem with the phone not running right?
Software version is COG5
Baseband version is COK1
Bootloader version is COJ6
I need to get everything the same but I can't flash any firmware tar files in ODIN, they all fail.
In recovery my "/system" won't stay mounted.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I can help you with this. You definitely need to update your bootloader. I'm not sure how you managed to update the kernel to OK1 and not the bootloader. The modem is OK1 and that's fine. It will work on all roms. If you want to continue running my Hybrid-X 3.0 rom you should go ahead start fresh by downloading the latest official samsung OK1 rom tar package. Search the general threads here in the sprint N4 forum to find a link. Once you have that downloaded you need to extract it with 7zip. Inside the extracted folder will be the actual tar file that u will flash in odin. But first you will need to backup anything you need to back up from you sd-card and internal storage. Next, reboot to TWRP recovery and do factory reset a few times then press "advanced wipe options" and wipe all of the partitions except internal storage and micro-sd card. do this two or three times repeatedly. You must do this BEFORE you odin the OK1 tar or else you will have left over data and it will cause problems. So wipe everything FIRST. Once you do this, while you're still in recover, go back to reover home screen and then select reboot and reboot to Download mode. Then launch odin and then connect your phone to your pc & usb cable. Use the AP button and select the tar you extracted earlier. It will verify the md5. Once that finishes then you can start the flash process. When it finishes you will be fully updated to OK1. At that point you should be able to odin TWRP again then the rom of your choice.
Edit: If you can't odin the OK1 tar and it fails then you will need to do this... download the OJ6 tar ball. extract it like usual. Then flash it in odin. If it fails then do this... Open odin. Don't connect your phone yet! click on the "options" tab and check the "re-partition", "auto reboot" and "reset time" options. then flash OJ6 and watch it work. Let you phone boot up completely! Then do the device activation, prl and profile updates in settings BEFORE you flash any other custom rom. This will set you straight.

tx_dbs_tx said:
I can help you with this. You definitely need to update your bootloader. I'm not sure how you managed to update the kernel to OK1 and not the bootloader. The modem is OK1 and that's fine. It will work on all roms. If you want to continue running my Hybrid-X 3.0 rom you should go ahead start fresh by downloading the latest official samsung OK1 rom tar package. Search the general threads here in the sprint N4 forum to find a link. Once you have that downloaded you need to extract it with 7zip. Inside the extracted folder will be the actual tar file that u will flash in odin. But first you will need to backup anything you need to back up from you sd-card and internal storage. Next, reboot to TWRP recovery and do factory reset a few times then press "advanced wipe options" and wipe all of the partitions except internal storage and micro-sd card. do this two or three times repeatedly. You must do this BEFORE you odin the OK1 tar or else you will have left over data and it will cause problems. So wipe everything FIRST. Once you do this, while you're still in recover, go back to reover home screen and then select reboot and reboot to Download mode. Then launch odin and then connect your phone to your pc & usb cable. Use the AP button and select the tar you extracted earlier. It will verify the md5. Once that finishes then you can start the flash process. When it finishes you will be fully updated to OK1. At that point you should be able to odin TWRP again then the rom of your choice.
Edit: If you can't odin the OK1 tar and it fails then you will need to do this... download the OJ6 tar ball. extract it like usual. Then flash it in odin. If it fails then do this... Open odin. Don't connect your phone yet! click on the "options" tab and check the "re-partition", "auto reboot" and "reset time" options. then flash OJ6 and watch it work. Let you phone boot up completely! Then do the device activation, prl and profile updates in settings BEFORE you flash any other custom rom. This will set you straight.
Click to expand...
Click to collapse
lemme explain the whole "situation" real quick---
I flashed the stock rooted deodexed rom a while back, soon as it was posted and it ran perfectly, no reboots, no freezing, not a problem ever.
Last Monday I was charging the phone, it fully charged and I hit the home button and the screen wouldn't lightup/open...first time I ever had this happen on this phone. I yanked the battery, put it back in and it wouldn't boot.
tried to re-flash the rom after factory reset and when it booted i got the MMC Failed/can't do normal boot error.
reflashed the stock frmware in odin and that failed, odin said I need a PIT file...found the PIT file to flash with the unrooted stock firmware, failed in odin.
I managed to restore from TWRP, which worked until I rebooted then got the same "can't do regular boot" error after it booted ...I checked TWRP and the "/system" is unticked and even when I check it to boot it doen't boot and always go back to unticked.
I finally re-installed this rom and it's working now but as you saw above everything is different (firmware, etc.)
I want to get it to where I can at least use it again and at the best revert to unrooted stock to send to samsung for repairs of whatever caused the initial problem since the phone is only 3 months old.
Thanks for the response btw:good:

broad_st_bully said:
lemme explain the whole "situation" real quick---
I flashed the stock rooted deodexed rom a while back, soon as it was posted and it ran perfectly, no reboots, no freezing, not a problem ever.
Last Monday I was charging the phone, it fully charged and I hit the home button and the screen wouldn't lightup/open...first time I ever had this happen on this phone. I yanked the battery, put it back in and it wouldn't boot.
tried to re-flash the rom after factory reset and when it booted i got the MMC Failed/can't do normal boot error.
reflashed the stock frmware in odin and that failed, odin said I need a PIT file...found the PIT file to flash with the unrooted stock firmware, failed in odin.
I managed to restore from TWRP, which worked until I rebooted then got the same "can't do regular boot" error after it booted ...I checked TWRP and the "/system" is unticked and even when I check it to boot it doen't boot and always go back to unticked.
I finally re-installed this rom and it's working now but as you saw above everything is different (firmware, etc.)
I want to get it to where I can at least use it again and at the best revert to unrooted stock to send to samsung for repairs of whatever caused the initial problem since the phone is only 3 months old.
Thanks for the response btw:good:
Click to expand...
Click to collapse
Your phone has a hardware failure. If you have insurance through Sprint, take it in to a Sprint owned store. They won't be able to fix it, and will offer to replace it.
Sent from my SM-N920P using Tapatalk

followed the first set of instructions and it failed, on the phone screen under the odin info it said write fail, no pit file,read fail

LMMT said:
Your phone has a hardware failure. If you have insurance through Sprint, take it in to a Sprint owned store. They won't be able to fix it, and will offer to replace it.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
I have full insurance but when i brought it to the store the "tech specialist" saw the "SEANDROIDENFORCING" at the top of the screen and saw it was rooted and blamed the root

broad_st_bully said:
I have full insurance but when i brought it to the store the "tech specialist" saw the "SEANDROIDENFORCING" at the top of the screen and saw it was rooted and blamed the root
Click to expand...
Click to collapse
tinker with the phone and try to get it back to a regular stock firmware. even if it won't boot up. that will get rid of the red and yellow text at boot screen. formatting System may also clear the red and yellow text.
it will still show when booting twrp though.
never take a rooted phone to Sprint lol 98% of their employees either think it's witchcraft or are too afraid of repercussions for servicing a rooted device. the warrantee void the phone refers to is manufacturer warrantee though and has nothing to do with Sprint. it's aggravating.

I agree. it definetely sounds like hardware failure. Do like the previous poster said. Odin the stock OJ6 or OK1 rom and then go back to the sprint store and see what they can do for you. If it's hardware related and you do have TEP "Total Equipment Protection" on your line then they will order you a free replacement. Don't let them bully you into filing an insurance claim. this is not physical damage therefore you DO NOT have to file an insurance claim. They will tell you to file insurance but you have to explain to them that it is not physical damage to the phone and let them know you are a little wiser than that.

Accidentally flashed Note 4 Edge recovery image to Note 4 Official app, need help..

Hi, so today I rooted my Note 4 and installed the official TWRP app, I made the mistake of flashing the Note 4 Edge recovery firmware directly from the TWRP app and when I rebooted my phone updated and now the touch screen heavily distorts where I touch the screen in order to compensate for the edge that is not there. My phone is basically unusable but with some effort I can get into TWRP to try to restore to the back up I made before doing this but it doesn't fix the problem. The phone will also not boot into any sort of recovery mode and is not recognized by odin anymore. I don't know what to do here.. if anyone has any tips for me I'd be very appreciative. Thank you so much.

slothandtorpor said:
Hi, so today I rooted my Note 4 and installed the official TWRP app, I made the mistake of flashing the Note 4 Edge recovery firmware directly from the TWRP app and when I rebooted my phone updated and now the touch screen heavily distorts where I touch the screen in order to compensate for the edge that is not there. My phone is basically unusable but with some effort I can get into TWRP to try to restore to the back up I made before doing this but it doesn't fix the problem. The phone will also not boot into any sort of recovery mode and is not recognized by odin anymore. I don't know what to do here.. if anyone has any tips for me I'd be very appreciative. Thank you so much.
Click to expand...
Click to collapse
Try pulling the battery at least one minute, reinstall battery and boot directly to recovery or download mode. But if you can boot to system, you could install the Official TWRP Manager from Google Play and download the right TWRP image and flash it with the same app.
In the app, search "Samsung Galaxy Note 4" and scroll to bottom and select "...Qualcomm -- trlte", then "...Americas...". The file you need is twrp-3.1.1-0-trlte.img to flash with TWRP or the the recovery flash option in the app.
I've read many posters have flashed wrong recovery (Note Edge) but not corrupted partitions. But you may need to flash the stock tar if getting right TWRP recovery flashed, boot and opening dialer and dialing *#2663# and pressing the top left update button doesn't work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Alternately, you can download this app and use the left tab to select secret codes and select code 2663 (if the dialer code doesn't work).
http://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
The 2663 secret code is to correct the touch screen calibration. You need to use your S-pen to open dialer or navigate until touch is restored.
Sent from my SM-N920P using Tapatalk

Thank you so much man I had done everything up to entering that last secret code and that did it for me. It's a damn shame I already have a new phone coming in the mail but thank you so so much.

wow, spoke a little too soon on this one. Now normal booting is failing and it goes straight to recovery, that and I can't get my computer to detect it in Odin

slothandtorpor said:
wow, spoke a little too soon on this one. Now normal booting is failing and it goes straight to recovery, that and I can't get my computer to detect it in Odin
Click to expand...
Click to collapse
When boot fails, do you see eMMC read or write failure (component failure)? If you see that, Samsung Support may offer to repair it for $75 USD and a week or more turnaround. Unless you have a warranty...
Your phone not detecting on PC could be a bad Samsung USB driver. Try reinstalling it; download it from Samsung Support for your model number. But give Odin and PC time if you're trying to install stock tar; it takes a minute or longer to verify the md5, then it may add your phone in COM tab on Odin as highlighted. You may see a comment in Odin log (view log while running), like please wait during this verification. Don't try to proceed without md5 verification and COM added.
Sent from my SM-N920P using Tapatalk

Tried again today and after a few restarts I got my phone to read in odin and wrote a stock tar.gz to it. I'm still updating as we speak but it looks like it's gonna work out thanks a bunch man.
samep said:
When boot fails, do you see eMMC read or write failure (component failure)? If you see that, Samsung Support may offer to repair it for $75 USD and a week or more turnaround. Unless you have a warranty...
Your phone not detecting on PC could be a bad Samsung USB driver. Try reinstalling it; download it from Samsung Support for your model number. But give Odin and PC time if you're trying to install stock tar; it takes a minute or longer to verify the md5, then it may add your phone in COM tab on Odin as highlighted. You may see a comment in Odin log (view log while running), like please wait during this verification. Don't try to proceed without md5 verification and COM added.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse