Develop Bugs

[ROM][ODIN][TAR]SPH-D710 FH23 (FH23 Modem/Kernel/ROM - Full Restore - Rooted)

Note: This is cross-posted from SXTP-Developers so please click the link and give him the hits when possible.
Credits
Thanks go to the following:
- sfhub for many hints on how to do this - I'm just trying to help fill in while he's away.
- sextape for FH23 leak
- Chainsdd for superuser/su
- rwilco12 for advice and hosting
- rainmotorsports, dev-host for hosting
- XDA Members for their support and hopefully feedback on these builds!
Make sure you give them any thanks for this build - they did far more than I on this! :highfive:
sfhub said:
You may have heard... the zerglings fought a noble battle against the samdroids and held their own for many battles, but were finally defeated on the EL13 battleground. Starting with EL13 the zergrush exploit is plugged. Do not fear, as the zerglings have enlisted their old ally Odin to fight the next battle for them.
Click to expand...
Click to collapse
This is a match of sextape's FH23 leak with only root added.
This means it should behave completely as it is stock or released by either OTA/Kies.
Since most people are familiar with sfhub's format I'm going to include it here.
Again thank him for the LARGE amounts of time that he put into these posts.
-----------------------------------------------------------------------------------------------------------------------------------
This will NOT trigger the Yellow Triangle NOR will it increment the ODIN flash count.
This does NOT have the issue with the USB jig being disabled.
There are two versions provided, a FULL Restore that resets your whole phone, similar to a factory restore, and a No Data Restore, which is the same, except it preserves your User Data. The NoData version is only suggested if you are upgrading or remaining at the same version.
{
"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"
}
Instructions - (No Video Yet)
0) Backup anything important and Disable any PINs
This process will restore you to factory software. All your Android data will be reset.
To be safe, it is best to archive your backup off your phone, ie on your PC or dropbox.
Note #1: Please DISABLE any PIN code you may have created to protect your phone. As a security measure, after the flash, Android will ask you for your PIN, if you have one enabled. It is simpler to have no PIN active. If you forgot your PIN then, after the factory restore, just enter the wrong PIN a few times and it will warn you. Enter the wrong PIN again and it will reset the filesystem.
1) Install Samsung USB/Android drivers (if necessary) [USB/Android]
2) Download the FF18 full restore One-Click self-extractor
SPH-D710_FH23_CL1057614_Rooted_Restore_OC.exe [Mirror1|Mirror2] (RESET user data) (md5: 63388c019efa0e5d9896e0254c3d3ea9)
SPH-D710_FH23_CL1057614_Rooted_NODATA_OC.exe [Mirror1|Mirror2] (PRESERVE user data - do NOT use if downgrading versions) (md5: b0499d6fcc6bf0092e2ef0e1d7e01f1c)
Mac/Linux - Install 7-zip, then use it to unpack the individual ODIN components in Reference Section B (below). If Heimdall fails flashing all 3 files together, try doing them individually. Skip the remaining instructions that are windows specific (steps 3, 4, 6).
Android - Install ZArchiver, then use it to unpack the ODIN OneClick 7zip self-extractor file in this section (long press *-oc-sfx.exe, Open as archive, Odin-OC, select *-OneClick.exe, Extract). Use Mobile ODIN to Open File the resulting *-OneClick.exe file. Mobile ODIN issue - modem might not flash consistently. Skip the remaining instructions that are windows ODIN specific (steps 3, 4, 5, 6).
3) Extract the package
double-click on the self-extractor file, specify the directory to extract to (instructions assume C:\)
4) Start ODIN One-Click
Full: Double-click on SPH-D710_FH23_CL1057614_Rooted_Restore.exe in Odin-OC folder created.
NoData: Double-click on SPH-D710_FH23_CL1057614_Rooted_NODATA.exe in Odin-OC folder created
Note #1: On Vista or newer, you may need to right-click on the file and Run as Administrator.
5) Place phone in ODIN download mode
Code:
[B][U]Method #1[/U][/B]
Power down phone
Wait for capacitative button [B]lights to turn off[/B]
Simultaneously [b]Press and Hold [Power] [VolDn][/b] until confirmation screen appears
Press [B][VolUp][/B] to enter Download mode
Code:
[B][U]Method #2[/U][/B]
adb reboot download
Code:
Connect USB cable to PC if not already connected
ODIN should show yellow COM port in 2nd column
Note #2: If you do not see a yellow COM port, you may need to run the ODIN One-Click as Administrator and/or unplug/plugin the USB cable after starting ODIN One-Click.
6) Start ODIN flash process
Press [Start]
7) Complete - PASS!
When complete you should see a screen similar to what is shown at top of post
Phone will automatically reboot
Status should change to green PASS!
Boot process will be slightly longer than usual during which time you'll see the 4G logo screen.
If you want CWM use Option D in the Auto Root Package to install FF18+CWM-agat-src (you are already rooted so Option A is not necessary). You will lose the FG31 kernel in the process.
If you need to clear NVRAM/Sprint data login info, perform a ##72786# reset from the Dialer and enter MSL.
Type getprop ril.MSL in adb shell or terminal to retrieve your MSL.
For NoData install:
- If you are getting random force closes, wipe cache/dalvik-cache
- If you have troubles with Android Market, clear data from
menu->applications->all->market->clear data
- If you have troubles booting into Android, perform factory reset in ICS using the ODIN OneClick Factory Reset tool. Do NOT perform factory resets using stock recovery or privacy->reset, at least until you read about the EMMC superbrick/lockup bug and understand what the trigger points are and what you are exposing yourself to.
---------------------------------------------------------------------------------------------------------------

Reference Section
FH23 Leak (SXTP-Developers Forum)
(Link to leak here, no mirrors allowed)
FH23 One-Click (Unrooted, Full Restore) - Thanks to rwilco12!
FH23 One-Click (Unrooted, Preserve User Data) - Coming Soon
CWM Zips (Odexed/Deodexed, Rooted) - Thanks to crawj!
FH23 Modem - Links thanks to rwilco12:
[OC] FH23 Modem One-Click.exe
[ODIN] FH23 Modem TAR.MD5 *Flash with Odin in PDA Slot or through Mobile Odin.
[CWM] FH23 Modem ZIP
FH23 Kernel - Links thanks to rwilco12:
[OC] FH23 Kernel One-Click.exe
[ODIN] FH23 Kernel TAR.MD5 *Flash with Odin in PDA Slot or through Mobile Odin.
[CWM] FH23 Kernel ZIP
FH23 ROM Only - Unrooted (tar.md5) - Coming Soon
FH23 ROM Only - Rooted (tar.md5) - Coming Soon

Known Issues and Other Items
Wi-Fi: No issues so far.
Task Manager (Bottom is not opaque) Still there...
Freezing/Partial Reboot (Sprint Screen): I'm noticing this but normally it also is when the signal is wonky. Might be the cause.
It also caused a few times where I rebooted the phone to get it to come back.
In the end I can't say for sure what this is.
Su notifications for shell: There seem to be a few things going on here.
First, a long known issue is ##DATA# will act up after going in once. Better to reboot and then go back in.
But I think there are some viruses out there also trying to dig in - for example, I had a fake email from a "bank" today.
The email didn't load and it started giving this notification - so I rebooted.
Because of that and the known fact that Android is now being targeted for malware, please consider getting a product to monitor or an AV solution.
It's the least you can do if you're going to keep root.
Potential Issue with NODATA versions
It seems that the NODATA versions are not behaving as previously expected.
This does not appear to be a problem with the build itself but rather the data in the apps.
For example, I did a test NODATA update on a FF18 phone to FH23. This froze constantly.
I wiped dalvik, cache and did NODATA FH13. Finished and wasn't locking up as much but still froze constantly.
Took back down to FF18 and Sprint ID kept FC'ing... cleared that data and all was right again in the world.
Moral of the story - I'm happy to put up a NODATA version but please realize you flash at your own risk! When in doubt, save yourself a headache and get TB, backup apps/data and do the full restore version.

Hey thanks for this. Is there a no root, NO DATA wipe, one click?
And the SOD issue with the FF13 one click has been resolved and shouldn't be present in this one? Kinda lost track of the leak vs Kies discussion thread and what the final determination was as to why they behaved differently.

First page awesome.can't wait to try this out.

tpapa said:
Hey thanks for this. Is there a no root, NO DATA wipe, one click?
And the SOD issue with the FF13 one click has been resolved and shouldn't be present in this one? Kinda lost track of the leak vs Kies discussion thread and what the final determination was as to why they behaved differently.
Click to expand...
Click to collapse
There is a no root no data coming soon.
I'm uploading the full restore now and will have the other uploaded hopefully by the end of today.
EDIT: Unrooted thread now up http://forum.xda-developers.com/showthread.php?t=1859771. Still uploading the No Data version but Full Restore is in there.

Thanks Garwynn!

Nice, will try this out today!

Thanks bro! I think today I'm gonna load a stocker for the weekend...

I have been having the freezing / partial reboots on all stock versions of ICS so far, so I don't think it is specific to this build... Roam control causes it just about every time I switch...

CyberpodS2 said:
Thanks bro! I think today I'm gonna load a stocker for the weekend...
Click to expand...
Click to collapse
Running the OneClick NODATA over a totally clean rebuild of FF18 from last night, I'm stuck in the same boot hang situation I was before when I tried it yesterday with the version that "wasn't ready for prime-time" and was posted by another user without garwynn's permission. Basically, it boots up, and I can do things for a few seconds, but inevitably the phone locks up and reboots itself within about 10-20 seconds every time.
I'm thinking that it might be tied to the fact that I'm running Nova Launcher 1.3 beta 6 as my default launcher (has "Jelly Bean enhancements"). Worked fine with FF18 and FH13, but something must've changed in FH23 that doesn't play nicely with this version. The problem is that I can't have the phone interface up long enough to get Nova Launcher cleared out as the default launcher. Trying to go into SprintID to reset the pack to the default Android Launcher that way doesn't seem feasible either.
Any ideas?
But yeah, note to anyone else flashing... be sure to switch back to either Touchwiz or the stock launcher before flashing this one. It's finicky.

tmeader said:
Running the OneClick NODATA over a totally clean rebuild of FF18 from last night, I'm stuck in the same boot hang situation I was before when I tried it yesterday with the version that "wasn't ready for prime-time" and was posted by another user without garwynn's permission. Basically, it boots up, and I can do things for a few seconds, but inevitably the phone locks up and reboots itself within about 10-20 seconds every time.
I'm thinking that it might be tied to the fact that I'm running Nova Launcher 1.3 beta 6 as my default launcher (has "Jelly Bean enhancements"). Worked fine with FF18 and FH13, but something must've changed in FH23 that doesn't play nicely with this version. The problem is that I can't have the phone interface up long enough to get Nova Launcher cleared out as the default launcher. Trying to go into SprintID to reset the pack to the default Android Launcher that way doesn't seem feasible either.
Any ideas?
But yeah, note to anyone else flashing... be sure to switch back to either Touchwiz or the stock launcher before flashing this one. It's finicky.
Click to expand...
Click to collapse
It's not - and I was having this issue with other builds. I have a co-workers phone here at the moment that is suffering the same thing. I'm going to *try* and flash FF18 nodata and see if I can get it back to stable for now. (Note: This coworker was 100% stock so whatever this is may not be launcher related.)
One thing I noticed - I could get to Task manager and last active app I saw was Gapps. Unfortunately I can't even get to clear the data and see if that would fix it. If you can, try a custom recovery and see if clearing dalvik-cache helps.
*Edit* Got a logcat of it.... And I'll recommend that people highly consider doing the full wipe until I have a better handle on what's going on. (FWIW this seems to be happening with OTAs as well, so may not be just this particular build...)

garwynn said:
It's not - and I was having this issue with other builds. I have a co-workers phone here at the moment that is suffering the same thing. I'm going to *try* and flash FF18 nodata and see if I can get it back to stable for now. (Note: This coworker was 100% stock so whatever this is may not be launcher related.)
One thing I noticed - I could get to Task manager and last active app I saw was Gapps. Unfortunately I can't even get to clear the data and see if that would fix it. If you can, try a custom recovery and see if clearing dalvik-cache helps.
Click to expand...
Click to collapse
I'm actually in the process of the same thing, FF18 NODATA OneClick to see if I can at least get it back up and running. Will let you know how it goes. If I can get it stable, I'm going to just clear dalvik, and then stick with the FH13 NODATA for now. Don't really feel like redoing everything again on FH23 RESTORE.
----
OneClick FF18 NODATA over the FH23 seems stable. Gonna wipe dalvik and cache, and just go with FH13 for now. THanks for investigating.

tmeader said:
I'm actually in the process of the same thing, FF18 NODATA OneClick to see if I can at least get it back up and running. Will let you know how it goes. If I can get it stable, I'm going to just clear dalvik, and then stick with the FH13 NODATA for now. Don't really feel like redoing everything again on FH23 RESTORE.
----
OneClick FF18 NODATA over the FH23 seems stable. Gonna wipe dalvik and cache, and just go with FH13 for now. THanks for investigating.
Click to expand...
Click to collapse
Just an update - wiping cache, dalvik and then flashing FH13 nodata worked. *Phew!* Now to figure out what didn't change between FF18/FH13 but did with FH23...
Will update Post #3 to note this incident.
*Edit (again!)* Going to FH13 was no good... person had me come get their phone and asked me to fix it because it was freezing again..

I flashed the no data version and have the exact same issue...
---------- Post added at 12:17 PM ---------- Previous post was at 11:46 AM ----------
Interesting... I flashed back to FH13 no data, and everything was working fine again. Then updated several google apps... now I have the same boot loop with FH13... Ugh...

Sideman7 said:
I flashed the no data version and have the exact same issue...
---------- Post added at 12:17 PM ---------- Previous post was at 11:46 AM ----------
Interesting... I flashed back to FH13 no data, and everything was working fine again. Then updated several google apps... now I have the same boot loop with FH13... Ugh...
Click to expand...
Click to collapse
Hmm... I flashed back to FF18 NODATA, updated all the apps, then cleared dalvik and rebooted. Updated to FH13 NODATA and seems to be running fine so far.
I'll report back if there's an issue though.
If so, looks like I'll just do FH23 RESTORE tonight. Ugh.

Sideman7 said:
I flashed the no data version and have the exact same issue...
---------- Post added at 12:17 PM ---------- Previous post was at 11:46 AM ----------
Interesting... I flashed back to FH13 no data, and everything was working fine again. Then updated several google apps... now I have the same boot loop with FH13... Ugh...
Click to expand...
Click to collapse
That seems to be the key - apparently some of the data in these apps doesn't behave well with a NODATA flash. I know they're convenient but I found early on in ICS that I had more problems with them usually than it took to just keep a regular backup of necessary data and just do the full restore.
In the end I was able to apply the modem and kernel for the person. As long as it runs that's all I'm sure they care about.

Just a reminder for everyone, this is a Development Build that wasn't ever supposed to see the light of day. Without the changelog we can't know for certain what is going on behind the scenes that could be creating those additional issues. I believe the issues people are experiencing are probably related to that.

rwilco12 said:
Just a reminder for everyone, this is a Development Build that wasn't ever supposed to see the light of day. Without the changelog we can't know for certain what is going on behind the scenes that could be creating those additional issues. I believe the issues people are experiencing are probably related to that.
Click to expand...
Click to collapse
That's true as well.. They may have logic that ports older data into the newer formats so that it behaves right during an OTA (and could be missing from this build.) In either case I'm happy to work on this!
And I guess I should drop a bomb now and say that FH28 rdf dropped this afternoon...

Well, for now I'm just flashing the FH23 full restore. I had to wipe my FF18 install not long ago, so I have my rebuild process fresh in my mind...

Need to flash my phone, but have a question...

So here's the scenario. Hopefully I don't leave anything pertinent out...
Galaxy S3 w/Sprint. Phone is rooted but has the stock ROM on it. The phone doesn't need to be rooted, but I figured something like wifi tether might come in handy at some point. I rooted it such a long time ago I honestly don't remember how I did it. However, the screenshots of the Odin program look somewhat familiar so I'm guessing it was something with that.
When I boot into recovery mode, it says CWM-based recovery v5.5.0.4 and has the standard CWM menu.
This, of course, means I can't get the OTA update that came out a few months back.
So, in order to get the stupid prompt to stop bugging me to update, I need to flash the phone with something. I'd be fine using an updated version of the Stock ROM, or would be happy to put something like CM10 on there. I don't want anything experimental so I'd go with the stable version.
This leads me to three questions.
1) What would you recommend as far as a ROM to flash when comparing stock vs CM vs whatever else. I'm fine with the stock feature set and stability is the top priority.
2) When I flash whatever ROM I flash, how much of the phone needs to be wiped? All the apps will have to be reinstalled, but does it also have to wipe things like photos and such?
3) How do I do the flash? All of the tutorials I see assume you're starting with an unrooted phone, which I'm not. Do I just copy the ROM Zip file over, do one of the wipes and then do the install from zip? I'm just looking for the basic steps to follow since I"m already rooted and have a recovery already there.
THANKS for any help so I can finally get this straightened out!!!

1.It depends on your likings. Play with different ROMs.
2.Just a wipe before to flash the ROM.No need to wipe photos and videos.
3.Yep.Put the ROM on your SD card,wipe your phone and then flash it.
Hope that helps
Sent from my GT-I9300 using xda app-developers app

kelemvor33 said:
This leads me to three questions.
1) What would you recommend as far as a ROM to flash when comparing stock vs CM vs whatever else. I'm fine with the stock feature set and stability is the top priority.
2) When I flash whatever ROM I flash, how much of the phone needs to be wiped? All the apps will have to be reinstalled, but does it also have to wipe things like photos and such?
3) How do I do the flash? All of the tutorials I see assume you're starting with an unrooted phone, which I'm not. Do I just copy the ROM Zip file over, do one of the wipes and then do the install from zip? I'm just looking for the basic steps to follow since I"m already rooted and have a recovery already there.
THANKS for any help so I can finally get this straightened out!!!
Click to expand...
Click to collapse
1) The standard answer is: try them all out and see if you like one or the other. But I'll be nice and also say that if you're looking for something stable, I'd recommend The People's ROM. It's a TW-based ROM with a lot of customization, but it's very stable and has a large user base. They're always willing to help someone out (as long as you search before asking).
2) It really depends what you're flashing. I always recommend what I call a "so fresh, so clean-clean flash," which means wiping /data, wiping /system, and cache and dalvik cache. You won't lose your photos, but you will lose all apps and their associated data (save games, etc). The reason I recommend wiping system (which others might not suggest), is that different ROMs have different mods associated with them, and as an end-user of the ROM, you have no idea if your previous ROM is leaving behind files in /system that won't play nicely with your new ROM. So I typically wipe system as well as data and the caches.
3) You're in luck. I have a previous post that explains #3 is pretty good detail. Since you have verified that you have CWM, you can skip the first section where I talk about that. I have quoted it below:
kay131108 said:
ok..can u pls be a little more specific..i if i press the three buttons with volume down is just an android in download mode..so what do i do next?...clockworkmodrecovery
Click to expand...
Click to collapse
Ok, let's start at the very beginning (it's a very good place to start).
Before we get started, I'm going to make the following assumptions:
You successfully rooted your phone through Odin.
You currently have a custom recovery (either TWRP or CWM).
You have a Rom you'd like to flash on either your internal storage or your SDcard (I'd recommend the SDcard, but that's your prerogative).
If either of the first two is not true, I'd recommend going back to qbking77's thread and check out the videos on how to use Odin to gain root and a custom recovery.
If number 3 above is not true, download a ROM (nor someone new to flashing/custom Roms, I'd recommend Freeza's stock rooted Rom, as it's identical to stock TW, but just with Root). Once you download a Rom, check it's md5sum to verify that it's a good download. Copy the file to your SD card and get ready to flash (make sure you have decent battery life left, I try to keep at least 50% or more when flashing Roms, although it shouldn't take too long.
I'll give directions on how to flash a Rom below. The instructions will be for TWRP, but CWM has similar options/settings
Turn your phone completely off (hold down power for 3-5 seconds)
Boot your phone into recovery. Hold Up, Menu, and Power for a few seconds (until SAMSUNG appears on your screen and the phone vibrates)
Make a Nandroid backup. I can't emphasize this enough. In flashing, it's almost a certainty that one time, something will mess up. When that happens, you want to be able to restore a backup. In TWRP, just go into Backup Menu and choose where you want it (internal vs. External storage). It takes my phone a few (5-10) minutes to completely backup my data.
In TWRP, click the wipe button, then system. This will completely wipe the Rom from your phone. Doing this will allow you to get a "clean" install, without any settings or leftover files from your old Rom getting in the way. Instead, you could only wipe data (factory reset), which is good enough for most Roms. I'd still recommend a system wipe, though.
Also while in the Wipe menu, wipe Cache and Dalvik Cache.
Go back to the TWRP main menu.
Click Install, then find your Rom zip file (may have to switch from internal to external storage).
Let TWRP do it's thing.
If you're installing a TW-based Rom, chances are it had gapps already installed. If not, you should now flash the correct gapps package from goo.im. Make sure you're flashing the correct one, as if you don't, your google apps will force close upon use.
Reboot into system and give it time to boot (first boot sometimes takes a couple of minutes).
Set up your phone the way you like.
These should be the directions to follow whenever you flash a new Rom. Some Roms have the Aroma installer, so you'll have more options once you choose to flash the Rom zip, but those are typically easy to follow (and vary from Rom to Rom, so I won't be able to give you a good guide on that).
Hope this helps!
Click to expand...
Click to collapse
And lastly, you don't have to lose all your apps. You can use Titanium Backup (TiBu) to restore your apps. You just have to be careful not to restore any system apps, as they tend to not play well between Roms. I have quoted my previous post about TiBu down below so you can review some features/warning about TiBu.
Ok, first I'll describe what you did and how that (most likely) messed up your phone. Then I'll describe what you can do to fix it.
Problem
It seems like your original flash of CM10.1 went smoothly. It must have been something to do with your Titanium Backup (TiBu) restores. More than likely, you tried to restore too much. In TiBu, the different apps have different colors: Red, Yellow, Green, and White. In the menu, you can see the following Legend:
{
"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"
}
White: User Application. These are apps that you installed from the Play Store or sideloaded by directly installing an apk. These are safe to restore.
Red: System Application. These are system files that heavily rely on which Android version (4.1.x vs. 4.2.x) and whether you're on TW or AOSP. I always try to avoid restoring these backups (even when just upgrading to a newer version of the same Rom). Some people will say that you can restore the Data only for these, but my motto is: caution will help prevent mistakes (ground-shaking, I know).
Green: System Service with Useful Data: These are system apps that have useful information (such as User Accounts, etc.). I treat these the same as Red Backups, but am a bit more likely to restore the data of them (green means go, right?).
Yellow: These backups are system data that can be restored as an xml file. These are inherently safer than the red and green ones, and I say restore away (I always restore my Call Log, Messages, and Wi-Fi Access Points).
The reason you were getting FCs was restoring a red or green backup. This can sometimes work, but has a lot of potential for issues when switching between TW and AOSP Roms. Most likely something in your /system folder is messed up due to restoring an app. Even when you flash a new Rom, it just overwrites items in your System folder, it doesn't wipe /System. So whatever is wrong in your /System folder is still there, regardless of what you flash.
Click to expand...
Click to collapse

Twrp says it installs, but doesn't

{
"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"
}
***EDIT: Just decided to install cwm and flash me a new rom and now I cant even do that just gives me a message saying unable to install recovery...Wtf? So now I'm stuck without any recovery options. Any ides other than firing u Odin?***
Never had any problems before but after flashing the return to stock unroot ma7 zip (with flashing the root zip immediately afterwards) all the sudden Twrp won't install. I go to the goo.im app. Go to install openscript recovery. it goes to the download and starts. Here's where it gey weird. It sits there with the download bar thinking for a while. Then sits with it at 0% and then eventually the toast message saying my recovery has been installed pops up. I reboot...and I'm still here with the 3e stock recovery. Thought it may be a goo server issue but it's been going on foe more than a few days now. I should also add thay since originally flashing the mc2 return to stock unroot zip I've been having data hangup issues and posted there got a response to jist reflash. Since the rom I decided to go to was ma7 I decided to just flash that one. Same thing, issues with loosing 4g all the time and intermittent periods wjere daya just stops working and I need to reboot. Was going to try flashing the ma7 zip again as per the suggestion yhat was made to me, but I now can not get twrp to install (this particular zip needs twrp and can not be used with cwm). Anyone else have this issue or know how to overcome this obstacle? Any and all help will be greatly appreciated!
Sent from inside your head

You need to flash it in odin or mobile odin at this point. In odin uncheck auto reboot, once the flash passes then unplug the device from PC, pull the battery for a second then boot straight into recovery via vol- & home & power. Reboot from recovery selecting yes for fix recovery and fix root. There's a recovery install script that will reflash stock recovery upon reboot if you don't disable the script first, booting to recovery will remove or disable the script so that doesn't happen. In order for recovery to install from an app like goomanager or rom manager you need to be rooted first, unless you just used CF-autoroot you should have had a recovery after rooting, if you're rooted properly anyways.
°•○●¤◇★S☆A: Son's of Android★◇¤●○•°
I like to break stuff! :flipoff2:
Sign up for copy using this link and get us both and extra 5gb of free storage https://copy.com?r=b8U0ED

Yeah that's what I figured after I found out I was totally unable to install a recovery. Was just thinking maybe someone knew of some awesome work around I was unaware of. But alas my fears rang true. Was trying to hold out until the labrats update was out. Oh well, have already pulled out the pc and ran through Odin just hadn't had a chance to update the post. Thanks for the reply though. Very appreciative as always for the advice of someone infinitely more knowledgeable than myself!

Psychotic-Cerebellum said:
Yeah that's what I figured after I found out I was totally unable to install a recovery. Was just thinking maybe someone knew of some awesome work around I was unaware of. But alas my fears rang true. Was trying to hold out until the labrats update was out. Oh well, have already pulled out the pc and ran through Odin just hadn't had a chance to update the post. Thanks for the reply though. Very appreciative as always for the advice of someone infinitely more knowledgeable than myself!
Click to expand...
Click to collapse
You need full root access to install recovery straight from the device itself. From your post I assumed your root didn't fully take and was causing the issues. Probably outdated or corrupted su.bin causing su to not properly gain root access. Oh well, at least odin only takes a second to get done, and it's much less likely to end up with a corrupted recovery img that way. A lot of people don't know about, forget about or don't understand the recovery install script that replaces a custom recovery with <3e> on boot which ends up confusing them even more when the recovery flashes right but won't stick.
°•○●¤◇★S☆A: Son's of Android★◇¤●○•°
I like to break stuff! :flipoff2:
Sign up for copy using this link and get us both and extra 5gb of free storage https://copy.com?r=b8U0ED

That was my assumption too. Not having proper root access even though I was able to run root only apps and super su said everything was dandy. I was just unsure because with the aforementioned data issues was thinking it could possibly be related to that. And yes luckily Odin is easy peezy especially with the Odin one click

Psychotic-Cerebellum said:
That was my assumption too. Not having proper root access even though I was able to run root only apps and super su said everything was dandy. I was just unsure because with the aforementioned data issues was thinking it could possibly be related to that. And yes luckily Odin is easy peezy especially with the Odin one click
Click to expand...
Click to collapse
Yeah it could have been bad downloads as well. I usually like to take the safest route when fixing someone else's phone tho, even if it does require more steps and some extra work. The one thing we could have tried if root was actually working was Mobile Odin, it works very similar to regular odin and flashes the same files bin, tar, img, etc. (can even flash one clicks if you extract them properly)
°•○●¤◇★S☆A: Son's of Android★◇¤●○•°
I like to break stuff! :flipoff2:
Sign up for copy using this link and get us both and extra 5gb of free storage https://copy.com?r=b8U0ED

[Q] Any idea how to fix this issue? I'm a noobie who has been trying to trouble shoot

I have a Sph-L900 Sprint Galaxy Note 2. About a month ago the device started acting up Saying it couldn't connect to my Samsung Account, and the only way I was able to fix it was a factory reset. That soon turned into not being able to connect to my Google account and knox issues where something was trying to access my device administrator, and the only fix was to keep updating the samsung security police. The device began shutting off and restarting about two to three times a day with the same error notifications popping up on start up. I kept doing a factory reset in order to get ride of the issues but would reappear shortly after.
I have never tried to root my phone because I wanted to wait for my contract to be up before messing around with it.The most I have done is install a few 3rd party apps and use the google launcher apk as my everyday launcher. Eventually because it keep restarting so often I thought I would try to put cyanogenmod on it using the installer app.Unfortunately it kept saying it couldn't communicate with my device and had to abandon that option. A few hours later the phone restarted again but this time became stuck on the Samsung Galaxy Note 2 logo on start up. I tried to another factory reset hoping that would fix it but this is what happened
View attachment 2714455
The whole thing is in red and keeps saying error and fail.
I have no idea what the issue being a noob, but started looking through forums and posts hoping to get an answer. I thought trying to reload the stock rom might be my best bet and started looking into how to unbrick the phone on youtube and forums.
I downloaded Odin and tried [ROM][ODIN]SPH-L900 MK4 (MK4 Modem/Kernel/Bootloader/ROM - Full Restore - Unrooted), Galaxynote2root.com, and QBking77 methods and files for putting factory stock rom back on the phone. I spent all day trying each one only to get "nand write start fail" when trying each tar file on odin.
I wanted to see if someone might actually be able to explain to me the exact issue and hopefully a possible solution.

Surgemidnight13 said:
I have a Sph-L900 Sprint Galaxy Note 2. About a month ago the device started acting up Saying it couldn't connect to my Samsung Account, and the only way I was able to fix it was a factory reset. That soon turned into not being able to connect to my Google account and knox issues where something was trying to access my device administrator, and the only fix was to keep updating the samsung security police. The device began shutting off and restarting about two to three times a day with the same error notifications popping up on start up. I kept doing a factory reset in order to get ride of the issues but would reappear shortly after.
I have never tried to root my phone because I wanted to wait for my contract to be up before messing around with it.The most I have done is install a few 3rd party apps and use the google launcher apk as my everyday launcher. Eventually because it keep restarting so often I thought I would try to put cyanogenmod on it using the installer app.Unfortunately it kept saying it couldn't communicate with my device and had to abandon that option. A few hours later the phone restarted again but this time became stuck on the Samsung Galaxy Note 2 logo on start up. I tried to another factory reset hoping that would fix it but this is what happened
View attachment 2714455
The whole thing is in red and keeps saying error and fail.
I have no idea what the issue being a noob, but started looking through forums and posts hoping to get an answer. I thought trying to reload the stock rom might be my best bet and started looking into how to unbrick the phone on youtube and forums.
I downloaded Odin and tried [ROM][ODIN]SPH-L900 MK4 (MK4 Modem/Kernel/Bootloader/ROM - Full Restore - Unrooted), Galaxynote2root.com, and QBking77 methods and files for putting factory stock rom back on the phone. I spent all day trying each one only to get "nand write start fail" when trying each tar file on odin.
I wanted to see if someone might actually be able to explain to me the exact issue and hopefully a possible solution.
Click to expand...
Click to collapse
Not sure what the issue is, but if your not rooted you can not use method you tried.. If you can get back into your phone, root it using the toolkit found here. http://forum.xda-developers.com/showthread.php?t=1957155 it will install a custom recovery for you during the process. once done you can us the restore method you tried.. You might want to also, uninstall all the apps you have installed one at a time, until you find the one, that might be given you the problem..

doubledragon5 said:
Not sure what the issue is, but if your not rooted you can not use method you tried.. If you can get back into your phone, root it using the toolkit found here. http://forum.xda-developers.com/showthread.php?t=1957155 it will install a custom recovery for you during the process. once done you can us the restore method you tried.. You might want to also, uninstall all the apps you have installed one at a time, until you find the one, that might be given you the problem..
Click to expand...
Click to collapse
Thanks for replying, unfortunately I'm not able to get into my phone as it is just stuck on the Galaxy note 2 logo image on start up. Someone on the google+ community said that it could of happened from the 4.1 to 4.3 update. I guess my best bet is to go to the Samsung kios at Best Buy and see if they can reflash my phone. If I do get it up and running I will install a custom recovery like you mentioned.

Can you reboot and hold the power, home button, & up arrow to get into download mode?
If you can, flash things from there. Odin. I would do the billiard back to stock. Or possibly try the philz recovery.
Please let us know what happens.

ColeTrain! said:
Can you reboot and hold the power, home button, & up arrow to get into download mode?
If you can, flash things from there. Odin. I would do the billiard back to stock. Or possibly try the philz recovery.
Please let us know what happens.
Click to expand...
Click to collapse
{
"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"
}
This is the best I can do with what I have to show you the process. I'm using this download SPH-L900_MK4_Full Restore_UNROOTED one click process as an example. It happens when I use the regular versions of oden and add the tar. files where it says PDA. I have used several versions like Sammobile that people have recommended, but In the end it always says Fail
I tried using the billiard one but since it's set up for twrp I'm not sure how to istall it with odin on the PC

I don't know. I'm just guessing. I'm not an expert. Post in the billiards forum.
I guess i would go to my "prepatory" thread and try flashing a new recovery. I guess try TWRP first. Then try the billiard back to stock. If still no. Try philz and then back to stock. I can't promise anything, but that is my advice.

Surgemidnight13 said:
View attachment 2718005
View attachment 2718006
View attachment 2718007
This is the best I can do with what I have to show you the process. I'm using this download SPH-L900_MK4_Full Restore_UNROOTED one click process as an example. It happens when I use the regular versions of oden and add the tar. files where it says PDA. I have used several versions like Sammobile that people have recommended, but In the end it always says Fail
I tried using the billiard one but since it's set up for twrp I'm not sure how to istall it with odin on the PC
Click to expand...
Click to collapse
That is a very old version of Odin I might add. Download and use Odin 3.07. When using make sure you right click and choose run as administrator. Flash philz 6.0.7.9 do a full wipe reboot into recovery then flash billards return to full stock with counter reset, you should not have any issues..

Hey. If i knew the answer i would tell you. Lol. I'm sorry that i don't. But you need to get something going through odin. Something is messed up on your phone and you need to replace it with something works. If you can't get Anything to flash from odin.... Well i can't imagine what else there would be to do. Except take it in for a replacement.

Sorry to hear this. I remember bricking my phone and was really scared as I did not want to go to the sprint store and go through all that nonsense. I hope you get it up and running. I know someone in this awesome community will help u out.
Wish I could help.
What version of odin are you using?

Let's see if this helps.
First download this Toolkit. It's an awesome tool. http://forum.xda-developers.com/showthread.php?t=1957155
(you will need to read those instructions for drivers install etc)
There really should be no reason why you can't simply reboot your phone into download mode and flash it back to stock. Just make sure you enable usb debugging mode within developer options BEFOREyou begin.
If you want a custom ROM right away, use the toolkit to root and install custom bootloader and recovery, then flash the ROM from recovery per usual.
From that point you can either flash a stock unrooted MK4 ROM or a stock rooted ROM or you can go with a custom rooted ROM. You will need to decide what you want right now.
If you want to stay on a stock unrooted MK4 ROM then you can go ahead and download this stock MC2 with flash count reset. http://forum.xda-developers.com/showthread.php?t=2086769 then once that completes you can simply let the OTA update your phone to MK4 and that will put you back at stock MK4.
You can also just flash the stock MK4 ROM via this page. Follow the instructions. http://forum.xda-developers.com/showthread.php?t=2591898

[Q] [Hard Resetting] Help for T999

Hello XDA members.
I am having an issue.
I came across an S3, I see it was previously rooted, with vroot, and it wont remove easily.
I'm also only getting EDGE speeds, but that's another story.
I've tried the usual Hard Reset through the phone. Didn't work properly. I've booted into recovery and erased cache and done a wipe from there. Still not properly cleansed. Does that mean its missing a file or a certain file has been changed?
Im trying to go back pure stock and also remove the 'modified' from the status.
I'm not too hip to all the specifics and whatnot, just mainly basics with ROMs and rooting.
My only other thought would be Odin. But if I flash the stock through Odin, will it go back to 100% stock? No 'modified'?
I've rooted and Odin'd before, but I never was concerned about it being pure stock or saying modified, cause I was modifying it lol
And, as a bonus, has anyone been able to find a working solution to only getting EDGE speeds? I've read around about changing the Network Mode, and that doesn't seem to work. Seen another post saying that TMO would have to reset the tower connections, or something relative...basically saying the phone could still be locked into a certain area.. I dunno.
That's one reason I'm trying to get the phone back to 100% stock; that's another step in my trial-and-error to get back to '4G' speeds (plus to see the logo)
I sincerely thank you for your help in advance.

What model S3 do you have? Download the one for your model and use Odin to flash back to stock, after that, reboot to recovery and perform a factory reset. It should now say official instead of modified

Yup. Need to know the model. Never heard of vroot so I suspect its different than ours. Factory resetting only wipes data, so it won't remove root since that is on the system partition. You need to find and flash the correct firmware for your device using Odin. Factory reset after that.

serio22 said:
What model S3 do you have? Download the one for your model and use Odin to flash back to stock, after that, reboot to recovery and perform a factory reset. It should now say official instead of modified
Click to expand...
Click to collapse
DocHoliday77 said:
Yup. Need to know the model. Never heard of vroot so I suspect its different than ours. Factory resetting only wipes data, so it won't remove root since that is on the system partition. You need to find and flash the correct firmware for your device using Odin. Factory reset after that.
Click to expand...
Click to collapse
its the standard T999 version..
I, too have never heard of vroot. It's like in 2% english and 98% chinese I suspect. Seems to be flashed into the phone.
{
"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"
}
thats the logo of it.
I will go that route [Odin] and give it a go.
And you mean once the Stock is flashed, Hard Reset from within the OS?
& Thanks for your responses.

Yup. Or from recovery. Same thing either way.

DocHoliday77 said:
Yup. Or from recovery. Same thing either way.
Click to expand...
Click to collapse
Just wanted to say thank you for your help.
The phone has a fresh system on it..not modified anymore, along with no more vroot.
Other than that:
Now im just dealing with only getting EDGE.

Check to make sure the imei matches the sticker under the battery.