Related
I'm not sure if I'm the only one who is having this problem but I've searched around and can't fix the issue. I recently had CM9 but went back to complete stock, on 2.3.4 (which isn't up to date). When I go to update from the settings menu, I get a communication failed text box, which then in turn makes me wait 24 hours before checking again.
I've done multiple battery pulls and stopped the running process for the software update to no avail. Can anyone help me with this?
Remember, I'm on the stock AT&T rom.
Sent from my SAMSUNG-SGH-I777 using XDA
myownwitness said:
I'm not sure if I'm the only one who is having this problem but I've searched around and can't fix the issue. I recently had CM9 but went back to complete stock, on 2.3.4 (which isn't up to date). When I go to update from the settings menu, I get a communication failed text box, which then in turn makes me wait 24 hours before checking again.
I've done multiple battery pulls and stopped the running process for the software update to no avail. Can anyone help me with this?
Remember, I'm on the stock AT&T rom.
Sent from my SAMSUNG-SGH-I777 using XDA
Click to expand...
Click to collapse
Are you rooted? And why update to 2.3.6 uckk6? Its got a few really bad bugs.
Sent from my SGH-I777 using XDA App
Not rooted. I just want to get my phone up to date so when the ICS update rolls out I'll be able to get it.
Sent from my SAMSUNG-SGH-I777 using XDA
myownwitness said:
Not rooted. I just want to get my phone up to date so when the ICS update rolls out I'll be able to get it.
Sent from my SAMSUNG-SGH-I777 using XDA
Click to expand...
Click to collapse
If*
Sent from my SGH-I777 using XDA App
Thank you for your helpful information.
Sent from my SAMSUNG-SGH-I777 using XDA
I think others were having trouble updating as well... I'd suggest flashing a custom rom, or if you want to stay with stock, using Entropy's Back to Stock packages (I'm not going to link that for you cause I'm too lazy and you should be able to find it.)
jcracken said:
I think others were having trouble updating as well... I'd suggest flashing a custom rom, or if you want to stay with stock, using Entropy's Back to Stock packages (I'm not going to link that for you cause I'm too lazy and you should be able to find it.)
Click to expand...
Click to collapse
Might give it a try. Trouble is, not having a rooted phone and going back to stock means I lose all applications and data with them. Eh. Thanks
Download stock rom (if u can get a tar file it most likely has everything u need, do some Googling just make sure its for the i777). Get mobile odin pro. Use mobile odin pro to flash the .tar and it gives u the option to root right there within the app before u flash. Profit. Just giving my two cents and what worked for me . If u do this though and don't remove any system apps it should allow u to ota upgrade. Haven't tried myself but that sounds like it'd work fine.
Sent from my GT-I9100 using Tapatalk
Phalanx7621 said:
Download stock rom (if u can get a tar file it most likely has everything u need, do some Googling just make sure its for the i777). Get mobile odin pro. Use mobile odin pro to flash the .tar and it gives u the option to root right there within the app before u flash. Profit. Just giving my two cents and what worked for me . If u do this though and don't remove any system apps it should allow u to ota upgrade. Haven't tried myself but that sounds like it'd work fine.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
I already did this except for rooting about 3 weeks ago. From what you're saying, if I root my phone from its current state I should be able to receive OTA updates? I'm willing to root just to see but I don't see how that would fix the "communication failed" errors for updates.
Sent from my SAMSUNG-SGH-I777 using XDA
FYI I have a rooted stock ROM, and I'm having difficulty doing an OTA update also. Different error (mine is "interrupted" after reboot). I posted it here because it seemed more related to that thread and I had other Q's about the process.
You guys are in panic mode, wait till we actually get an ANNOUNCEMENT for ICS from AT&T, then try to go back to stock using the methods we have.
No reason to do so right now, since AT&T will probably take a long time before pushing it.
We have a possible sources dropping on March 15th from i9100 but you will be required to be rooted to flash the possible ICS Roms that will be available after that date.
LiLChris06 said:
You guys are in panic mode, wait till we actually get an ANNOUNCEMENT for ICS from AT&T, then try to go back to stock using the methods we have.
No reason to do so right now, since AT&T will probably take a long time before pushing it.
We have a possible sources dropping on March 15th from i9100 but you will be required to be rooted to flash the possible ICS Roms that will be available after that date.
Click to expand...
Click to collapse
I don't think you understand. First of all, in no way am I in panic mode. Secondly, my phone is a few updates behind since I just recently brought it back to stock from CM7. All I am trying to do is bring it up to date.
Sent from my SAMSUNG-SGH-I777 using XDA
ota issue
You might want to check the (Guide)How to flash custom binaries.....on this forum. Creepycrawly has posted a reply towards the end of the thread that might be helpful. Believe its on one of the last two pages.
As has been said many times in other threads, even on a stock ROM if you have rooted and removed even one item of bloatware or made any other mods you will not be able to download an OTA update.
I have not rooted my phone. And as I said earlier, I restored my phone to complete stock meaning no bloatware has been removed. I'm still at a loss for what to do
Sent from my SAMSUNG-SGH-I777 using XDA
You were on CM9 (in a later post you say CM7), but you went back to stock UCKH7. Now you are unable to update over the air to UCKK6. You are mainly interested in having the phone ready to receive the update over the air to ICS, whenever that occurs. You have not rooted the phone since you returned to stock but you are willing to try root if it will help the update happen. You were also concerned about loosing apps and their data since you are not rooted. I recapped all this because on stock you should be able to run the update. To help you solve the problem, need to know all the facts.
I've done the following, although it has been several months ago, about a week or two after UCKK6 first released. From running a custom rom, I did a wipe data/factory reset, flashed stock UCKH7 plus root, and ran the over the air update to UCKK6 successfully, retaining root on UCKK6. I just did this to test it out, so after completing the test, I used my nandroid backup to return to the custom rom I was on.
I would assume that you did a wipe data/factory reset either before or after you flashed back to stock? If not, there could be traces left over that could interfere with the update process. I'm not sure if there could be traces left even after a wipe data/factory reset, but the Cyanogen Mod file structure is so very different than stock that it wouldn't be inconceivable.
Next, I would wonder how soon after flashing back to stock you tried to run the update, and if not immediately, what action could have possibly placed or removed files that would intefere with the process.
I'm pretty certain that if you were to wipe data/factory reset with a format and then flash stock again, and then try to run the update immediately, it would succeed. So there has to be something in the file system preventing it. You may not find it easy to correct that something manually. You may just have to do a wipe data/factory reset, and maybe a format, and then start all over with a fresh install.
Of course, that is the reason for rooting first. Root, then back up everything with titanium backup, SMS backup, export contacts, etc. and save all that to your computer. Then you can restore stuff after.
Thanks creepy,
I'm in the process of doing what you said. I rooted my phone, backed up everything I thought needs to be backed up and flashed the stock rom (2.3.4 kernel version 2.6.35.7 baseband version I777UCKH7). I still need to do a factory format in order to see if that will fix the update problem.
Question. Is the firmware version(s) above the latest AT&T software? According to Kies, it is. But I am reading other places that the latest software is android 2.3.6.
Did exactly as creepy stated. Brought the phone back to stock software and did a factory reset. Without ANY customization and as soon as the phone booted up, I did the software update and had the same thing, "Communication failed" (says there is an update available but servers are busy).
I give up.
Well, I don't have any new ideas. Maybe if I get some time in the next few days I'll try it on my phone to see what happens. It has been a while since I tried it. Maybe the server behaves differently now?
creepyncrawly said:
Well, I don't have any new ideas. Maybe if I get some time in the next few days I'll try it on my phone to see what happens. It has been a while since I tried it. Maybe the server behaves differently now?
Click to expand...
Click to collapse
From what I've been reading on AT&T forums (http://forums.att.com/t5/Samsung/Sa...2-3-6-OTA-update-now-live/td-p/2996495/page/3) I don't think so. I've been trying every combination I can think of to make this thing work but I honestly have no idea. I was extremely surprised when I brought the phone back to complete stock and no root and still couldn't get the update.
If ICS ever comes to AT&T GS2, I'll wait a month or so to keep trying then I might resort to going to an AT&T store to get a replacement. Who knows
Hi guys,
I've had an S2 for a few months now, and although I've managed to root the phone I'm still pretty green and need help.
I've had an OTA update from Gingerbread to ICS which I only installed as it popped up when I was using the phone.
The battery died earlier than expected and now it's stuck in a bootloop.
I don't want to have to ROM it as frankly I'm still in the "full theory" stage. I've heard of Odin and SamMobile.com, I've seen hours of vids on Youtube but I'm hoping there's another way to get around it. My confidence levels are improving but not there yet.
I have a Titanium backup on the phone from 2.3.4, if I wipe the phone from recovery will it work? Is there anything I can do apart from a new ROM?
If you had my lack of experience with this, what would you do? Thanks.
Can you get into download mode?
If so, you may have to bite the bullet and use Odin to flash the original firmware. You will be able to find it on these forums.
Don't sweat it, just download the Orange ICS ROM and put it in PDA on Odin and flash it, it'll take just a couple of minutes and you are done.
Thanks guys. It sounds so simple when you don't have a bootlocked phone to panic about.
FourQ said:
Thanks guys. It sounds so simple when you don't have a bootlocked phone to panic about.
Click to expand...
Click to collapse
Thats because it is simple! Ive never rooted because it looks confusing. But I've used odin many times to flash stock firmwares.
Sent from my GT-I9100 using XDA
Warren.D said:
Thats because it is simple! Ive never rooted because it looks confusing. But I've used odin many times to flash stock firmwares.
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
Nothing confusing about rooting either.
Download one of chainfires cfroot kernels or siyah kernel and flash via Odin.
That's it you're rooted.
----------------------
GTI9100
Hydra H2O 1.2.1
fluxi xx.01_rc5
if ya have a look around the forum, theres plenty of pre-rooted roms to flash via odin that wont increase ya binary counter, nothing hard about that.
Read the links in my signature
Sent from my GT-I9100 using XDA
I'm still reletively new to it
and I've had a couple of bootloops. A bit of a panic and then I figured out what I'd done wrong. As long as you follow instructions to the letter you'll be fine.
Edit: *Relatively, damn it.
Rooting it was easy enough. I went to unlockroot.com and a download later I was rooted. It's the ROMs that terrify me.
FourQ said:
Rooting it was easy enough. I went to unlockroot.com and a download later I was rooted. It's the ROMs that terrify me.
Click to expand...
Click to collapse
getting a custom rom isn't something you should be afraid of
getting a custom rom (or kernel) can improve your battery life (some of them).. but just be sure that getting a custom rom, it should be for whatever you're running (Gingerbread or ICS) usually, roms are flashable via CWM
take a leap, when you get into bootloop or get some problems along the process, just flash a stock firmware with odin..
@saywhatt
A mate (who's been doing this for years) has installed CWM7. It's odd how the things I liked about Gingerbread were added by Samsung, not Google.
I suspect I'll run with CWM7 for a week or so and decide then. First impressions aren't always correct (especially if you saw my face!) but after a week I should have a pretty good impression of the new ROM. I'm hesitant about ICS as the official version killed the phone but ultimately I may end up there.
It's good to watch the Youtube vids on how to flash stock ROMs with Odin. It's something I may try next week if CWM7 falls from favour.
Ultimately I'm sort of glad it happened. It's given me new confidence to try these things as I know there's a good chance it can all be recovered.
Q
I've never been too afraid of rooting or flashing. My first android device was a cheap piece of rubbish (an LG GTsomething i think), so I built up confidence in rooting and flashing because I didn't care if i damaged my phone.
I would recommend anyone who's not too confident to go out and get a cheap phone, it's a pretty significant investment but if your unsure about what your doing and just want to experiment, it's definitely worth the peace of mind.
...
I'm hesitant about ICS as the official version killed the phone
Click to expand...
Click to collapse
no m8 it didn't, your battery dying while you were updating killed your phone
It had finished a while before that. I was selecting a new font when it died.
You can't stuff up your phone anymore - its already in bootloop, what do you have to lose?
Odin is indeed very easy. Just make sure F.Partition is unchecked. Put the ROM in PDA and flash! Of course, after your phone has been put into download mode and connected to pc via usb and one of the Odin blocks have turned yellow.
Your phone is already rooted? If you made a backup in CWM (NOT Titanium Backup, this won't help you right now, as it's only for apps) you should restore that in CWM. A wipe and factory reset wouldn't help you right bow.
I understand you are a bit skeptic of ICS stock ROM right now, but remember you probably got pushed an early version,.the latest versions are very stable! Though Custom ROM's are the way to go eventually. Try the latest stable Cyanogen ROM.
Sent from my GT-I9100 using Tapatalk 2
@FreeStanler
Good point.
The stock ICS ROM was 4.0.3 if memory serves. It wasn't there for long but I was curious to see which version I'd been upgraded to.
I'm planning to see how this CWM7 ROM sits with me. If I can find out which app is causing this: http://t.co/9GfdXmD I'll probably be happy with it. I need to have a good play about with it to give it a fair chance. May end up with ICS/Stock ICS but for now we'll see how it goes.
Why on earth would you use Cm7 when Cm9 is far better, plus to flash a fw & then root with SuperOneClickRoot, or use the cf root kernel. The whole process takes 5 mins. Honestly M8 there's nothing to worry about. One thing I will say tho, Google Nandroid back up & once you know how to use etc, use it & make it your best friend coz that's the only thing that will fix the bootloop in the future
Sent from my GT-I9100 using xda premium
@blade30p
I didn't. A friend who's been doing this for years did it for me. I was hoping to get something resembling the stock Gingerbread on the phone, instead I got CWM7.
Hi am obviously new to these forums but not new to Android/Samsung development so I had custom roms installed on my I777 so I needed to revert back to stock in which I flashed a leak which apparently changed the pit so I was able to download all the stock files for Odin3 for my device in the Download Repository. My question is there any reason why my device just doesn't act as accurately as I though I remembered it being when it was stock. Is there any ultimately right process for flashing because most instructions including my own are all different, some say wipe cache and data first and battery pull then download mode Creepys says its not neccessary until after the flash as does ZedoMax. I've followed all of them and haven't understood why there is no ultimately right process if there is one at all using odin3 and one-click. And if this is the case what could possibly be going on with the force closes and hangups I'm getting? If someone is willing to take the time to help me with all these questions I'd greatly appreciate it.
Dunno if it'll help, but it won't hurt..
Boot into recovery and"fix permissions". *Should* help with the FC's - oh, and delete everything from your memory that you read on galaxys2root (zedomax). Whatever you've read from creepy, COMMIT to memory. The guy is ace!
Clay
Team Pirate
Sent from my PINK SGH-I777
clay101eve said:
Dunno if it'll help, but it won't hurt..
Boot into recovery and"fix permissions". *Should* help with the FC's - oh, and delete everything from your memory that you read on galaxys2root (zedomax). Whatever you've read from creepy, COMMIT to memory. The guy is ace!
Clay
Team Pirate
Sent from my PINK SGH-I777
Click to expand...
Click to collapse
I don't see the option for fix permissions first of all is that a cwm option? Also I know creepy is one of the best but what's wrong with gs2root? And I appreciate the help but which process is the ultimate right way? Do you flash pit,PDA,modem all together or is that incorrect?
GalaxyHackster85 said:
I don't see the option for fix permissions first of all is that a cwm option? Also I know creepy is one of the best but what's wrong with gs2root? And I appreciate the help but which process is the ultimate right way? Do you flash pit,PDA,modem all together or is that incorrect?
Click to expand...
Click to collapse
I don't remember for sure, but I don't think fix permissions in available in stock 3e recovery. It should be available in just about any custom recovery.
GalaxyS2Root, and it's owner who goes by the screen name zedomax, is a strictly commercial endeavour, designed to make money but not necessarily designed to help people. I think zedomax is a developer, but I'm not sure how good he is. Many of the offerings on that web site, and presumably on his dozens of other web sites for other phones, cause problems for folks, bricking phones, and other things. Further, he takes the work of developers here and posts their work on his sites without giving any attribution or remuneration. He's spread way too thin keeping up with all his various sites, and/or he just doesn't seem to care if his offerings cause problems. We've had so many people come to this forum with various problems due to GalaxyS2Root that when the name is mentioned, everyone is on it right away.
I would only use the pit to repartition on the I777 when everything else fails. It can be a help, but you should be sure that you are going to have a successful flash before you use it, since it repartitions the memory space of the phone.
Most firmware for the I777 has everything in one .tar file, which you put into the PDA slot. If you are flashing just a param.lfs or just a sbl.bin, then that goes into the PDA slot. You can also flash a modem at the same time as the rest of the firmware, using the Modem slot, but most firmware packages have the modem in them too.
So essentially the oneclicks are absolutely the only thing I need in order to ensure a 100% successful restocking? And if so am I always suppose to factory wipe/cache then battery pull (3e recovery doesn't have a power off option)? The reason why I ask so many questions is A. A lot of peoples data isn't accurate as you've stated and its better for me to have as much data as possible when potentially getting into these things. And B. I've been flashing my S2 like a madman with OCD because as soon as I'd get a force close or any sort of hiccup happened I assumed it was because I flashed it wrong when in fact I was just following some of the directions that I've aqquired from here or GS2Root and so far everything has flashed with the same results but as its been forever since my phone was purchased so I can recall if these are just the normal hiccups that come with the inconsistancy of android. So to me I'm just trying to.make sure that I'm doing things absolutely correct.
There is lots of material here to read. You can learn a lot about your phone by spending some time reading.
creepyncrawly said:
There is lots of material here to read. You can learn a lot about your phone by spending some time reading.
Click to expand...
Click to collapse
And you are absolutely correct and I have your guide bookmarked but with so many people having different takes on how to return to stock can you point me in a direction that's the completely right way of flashing your pit and attempt software. Or is your guide with one click the most surefire way to do it? Like I said before I'm a bit OCD when it comes to my phone so whenever I get a little hiccup I can't tell if those are just normal for I777 software or is it something I've done wrong which I probably haven't but it still worries me.
If you havn't done something absolutely ignorant, i.e. flash firmware for a different phone, then you should just use my guide with the linked one-click downloader. That package does not contain bootloaders or param.lfs. Those (the bootloaders and param) will always be good, and not needing replaced, if you only flash firmware from these forums and never flash leaked firmware (which usually contains bootloaders.) There should never, ever be a reason to use a pit file. As I said before, the phone has to be pretty seriously screwed before you need to repartition, and then it should be the absolutely last thing you try.
And inform yourself before you do any actual flashing. You should know exactly what you are doing to your phone, and also know what the remedy is before you do it. That way, you can avoid doing something stupid. If you really want to learn about your phone, read at least a little bit from the forums here every day for a few months, get involved in the discussions, and before you know it, you'll be one of the helpers.
Thank you so much for all of your prompt replies, I have been using the data from this site for quite some years now but never ran into any issues which required me to create an account (although I have wanted to), but for s**ts and giggles let me just say that due to the few hiccups I encountered and not knowing what would have caused them I have already flashed the pit and repartitioned as well as flashed the oneclick w/ bootloaders and param. Now asside from the few force closes that I ran into and the one time I bricked it and brought it back to fully functional is there any harm to the flashing of those tools that I've already done so far. Is there any negative side effects of what I've done that I may not be seeing or is it a case of well "there in the repository so theyre safe as long as I've flashed them correctly". And if so are these few force closes just everyday hiccups that every version of Android experiences and that I'm just overthinking it and it's just been a case of my ocd kicking me in the ass?
The danger in using those files is in the flashing. If a flash is inadvertantly interrupted or goes bad, then it can hard brick the phone. Once the flash is complete and successful, then you're fine. There are no side effects.
Force closes, and other anomalies can be caused by conflicting data is the system and data partitions. They can also be the result of bugs in the firmware distribution or in any of the various applications. To eliminate the first cause, following all the best proceedures when flashing such as wiping first, etc eliminates the possibility that the fc's are caused by improper proceedure.
With proper installation proceedure, and with a stable firmware, and with robust applications, you should experience little to no fc's.
creepyncrawly said:
The danger in using those files is in the flashing. If a flash is inadvertantly interrupted or goes bad, then it can hard brick the phone. Once the flash is complete and successful, then you're fine. There are no side effects.
Force closes, and other anomalies can be caused by conflicting data is the system and data partitions. They can also be the result of bugs in the firmware distribution or in any of the various applications. To eliminate the first cause, following all the best proceedures when flashing such as wiping first, etc eliminates the possibility that the fc's are caused by improper proceedure.
With proper installation proceedure, and with a stable firmware, and with robust applications, you should experience little to no fc's.
Click to expand...
Click to collapse
i did zedo then s2 unlock then aokp then siyah kernal change forgot to do triangle away then tryed a ota update messed up rom cwm messed up then i just did zedo again to get cwm again then i did aokp again then ran triangle away then i return to stock backup after root then odin flash for stock non root then i took stock and did ota update to 2.3.6 i dont think we will ever get 2.3.7 because google wallet is on 2.3.7 and we cant have it correctly .....on reboot it hangs so i did 3e wipe and cache delete reboot all has been good since batt has been outragously long on uckk7 but after ota update it shows as uckk6 i used a non rooted file maybe u used a rooted return to stock file ?anyway file i used was I777UCKH7-CL503881-No-BL as stated just used pda slot .....idk after all the custom roms theres a distinct feeling in knowing your stock again but have the ability to go and do it all over again i honestly just miss the torch feature and the easy brightness slider on the pulldown
im getting h+ but it doesnt seem like true h+ speed and i also lose h+ while holding the phone im waiting for this to change with tmobile and thier 1900mhz i hope it does or ill be looking into whats going on with the modem maybe
colorsharpkid said:
i did zedo then s2 unlock then aokp then siyah kernal change forgot to do triangle away then tryed a ota update messed up rom cwm messed up then i just did zedo again to get cwm again then i did aokp again then ran triangle away then i return to stock backup after root then odin flash for stock non root then i took stock and did ota update to 2.3.6 i dont think we will ever get 2.3.7 because google wallet is on 2.3.7 and we cant have it correctly .....on reboot it hangs so i did 3e wipe and cache delete reboot all has been good since batt has been outragously long on uckk7 but after ota update it shows as uckk6 i used a non rooted file maybe u used a rooted return to stock file ?anyway file i used was I777UCKH7-CL503881-No-BL as stated just used pda slot .....idk after all the custom roms theres a distinct feeling in knowing your stock again but have the ability to go and do it all over again i honestly just miss the torch feature and the easy brightness slider on the pulldown
im getting h+ but it doesnt seem like true h+ speed and i also lose h+ while holding the phone im waiting for this to change with tmobile and thier 1900mhz i hope it does or ill be looking into whats going on with the modem maybe
Click to expand...
Click to collapse
Honestly, I have no idea what you just said, or what you're asking.
qwertyaas said:
Honestly, I have no idea what you just said, or what you're asking.
Click to expand...
Click to collapse
Me either, sometimes punctuation goes a long way
Sent from team Pirate! Using Tapatalk 2
colorsharpkid said:
i flashed zedo then used s2 unlock. then i flashed aokp and siyah kernel. I forgot to do triangle away (because I used zedo) and then tried an ota update. This messed up my rom because I couldn't access cwm. then i flashed zedo again to get cwm back. After that i flashed aokp again and ran triangle away.
I then did a return to stock backup after root and an odin flash for stock non root. While on stock i did an ota update to 2.3.6. (some nonsense about 2.3.7 and Google wallet)
.....on reboot it hangs so i did 3e recovery wipe and wiped cache. Reboot has been good since. My batt has been outragously long on uckk7!! But, after an ota update it shows as uckk6 i used a non rooted file, maybe I should have used a rooted return to stock file?
Anyway, the file i used was I777UCKH7-CL503881-No-BL as stated and i just used pda slot .....idk, after all the custom roms theres a distinct feeling in knowing your stock again but have the ability to go and flash custom ROMs all over again. i honestly just miss the torch feature and the easy brightness slider on the pulldown.
im getting h+ but it doesnt seem like true h+ speed and i also lose h+ while holding the phone. im waiting for this to change with tmobile and thier 1900mhz i hope it does or ill be looking into whats going on with the modem maybe
Click to expand...
Click to collapse
Fixed... I think. And "zedo" refers to the sh;t zedomax has on gs2root.
Clay
Team Pirate
Sent from my Buttery Pink SGH-i777
Ok thats where I'm a bit concerned because I ran into an issue before where I was going to do a flash and it choked up on me (mind you it was a pit and tar flash repartition) and it bricked on me but I was able to reflash the same process again once the pc was ok again. I also had on flash that was the 2.3.5 leak but flashed over that and it was fine. Now with that said the phone flashed well, and now it runs generally like it should have in the first place. But my question is did that fluke flash do anything negative to the device behind the scenes that will never be ok again?
creepyncrawly said:
The danger in using those files is in the flashing. If a flash is inadvertantly interrupted or goes bad, then it can hard brick the phone. Once the flash is complete and successful, then you're fine. There are no side effects.
Force closes, and other anomalies can be caused by conflicting data is the system and data partitions. They can also be the result of bugs in the firmware distribution or in any of the various applications. To eliminate the first cause, following all the best proceedures when flashing such as wiping first, etc eliminates the possibility that the fc's are caused by improper proceedure.
With proper installation proceedure, and with a stable firmware, and with robust applications, you should experience little to no fc's.
Click to expand...
Click to collapse
Ok thats where I'm a bit concerned because I ran into an issue before where I was going to do a flash and it choked up on me (mind you it was a pit and tar flash repartition) and it bricked on me but I was able to reflash the same process again once the pc was ok again. I also had on flash that was the 2.3.5 leak but flashed over that and it was fine. Now with that said the phone flashed well, and now it runs generally like it should have in the first place. But my question is did that fluke flash do anything negative to the device behind the scenes that will never be ok again?
Sorry for double post but I wanted to make sure my questions are targeting creepy seeing as this thread is getting a bit off topic.
GalaxyHackster85 said:
Ok thats where I'm a bit concerned because I ran into an issue before where I was going to do a flash and it choked up on me (mind you it was a pit and tar flash repartition) and it bricked on me but I was able to reflash the same process again once the pc was ok again.
Click to expand...
Click to collapse
As far as I know, that would be fine. Someone with dev experience could look into partition sizes on the phone, and see what actually happened. As long as the firmware is functioning correctly, then I would assume the partition sizes are correct.
I also had on flash that was the 2.3.5 leak but flashed over that and it was fine.
Click to expand...
Click to collapse
I guess you didn't get a crippled bootloader. That was the main problem with some of the leaks.
Now with that said the phone flashed well, and now it runs generally like it should have in the first place. But my question is did that fluke flash do anything negative to the device behind the scenes that will never be ok again?
Click to expand...
Click to collapse
I don't know how to look behind the scenes... but I would think your phone is fine.
creepyncrawly said:
As far as I know, that would be fine. Someone with dev experience could look into partition sizes on the phone, and see what actually happened. As long as the firmware is functioning correctly, then I would assume the partition sizes are correct.
I guess you didn't get a crippled bootloader. That was the main problem with some of the leaks.
I don't know how to look behind the scenes... but I would think your phone is fine.
Click to expand...
Click to collapse
OK great info and definitely a relief but just out.of curiousity what are the repercussions of a bad bootloader flash or an improper pit flash? And how would we know that whatever pit or bootloaders flashed weren't for our phone or are corrupted data?
creepyncrawly said:
As far as I know, that would be fine. Someone with dev experience could look into partition sizes on the phone, and see what actually happened. As long as the firmware is functioning correctly, then I would assume the partition sizes are correct.
I guess you didn't get a crippled bootloader. That was the main problem with some of the leaks.
I don't know how to look behind the scenes... but I would think your phone is fine.
Click to expand...
Click to collapse
And trust me I absolutely appreciate all the responses the answer to my last question is all I needed to know to truly understand how the i777 works and functions and I commend you for that. I felt that trying to find all these answers would have been trying to find a needle in a haystack.
Also regarding the repartioning I just wanted to make sure that everything is correct in terms of space. My device is showing only 1.89gb of "Device Memory" at the bout of the "Storage" screen is this normal I though it was higher before but I cant quite remember.
sorry, don't have an sg2, nor at&t, just trying to help a co-worker so thanks in advance
1. is the latest update only available through odin?
2. if root isn't an option (and it's not in this case) would you recommend staying at 2.3.6 over the latest update? seems this new one was to fix the sod's people were experiencing but there are some who would disagree here. would just like to get an idea of what issues to expect if going to UCLL6
i spent a few minutes sifting around the forums here but i would appreciate a few responses, so again, thank you
The Odin flashable tar is available at Sam Mobile, and in the Download Repository. The Stock plus Root package is also available. See the links in my Signature.
There were quite a few reports from people who had sod on UCLC3 and said it was fixed on UCLL6. I only remember one report from someone who said they still had sod on UCLL6. My assumption, and the reason I went to the trouble of putting together the stock plus root package, was that the sod issue was fixed in this distribution.
As I recall, 2.3.6 had a fairly large number of little problems, so who's to say which is better. I haven't run stock since the first couple weeks in October 2011.
Thanks for taking the time to reply. I saw your thread and will probably head over there. One other question... Can mobile Odin be used to update or just through a PC?
Edit: one other thing, does updating through odin wipe the phone? Text messages, app data?
damngood98 said:
Thanks for taking the time to reply. I saw your thread and will probably head over there. One other question... Can mobile Odin be used to update or just through a PC?
Edit: one other thing, does updating through odin wipe the phone? Text messages, app data?
Click to expand...
Click to collapse
To use Mobile Odin, you have to already have root access.
As for wiping the phone, yes. When moving from one base to another(like 2.3.6 to 4.0.4) you should always wipe the phone. There are apps you can use to back up stuff beforehand, and restore after the flash.
This is a Backup of the PH1 ROM's system and modem partitions. This is a Pre-Rooted ROM with the SD Card write permissions fix. This is different from my other post in those two differences.
You will need a custom recovery to install this ROM. (http://forum.xda-developers.com/note...lipop-t3089382)
Always perform the appropriate backups and other steps just in case something messes up. If you are on Lollipop, you should be able to just flash and go without any data loss (except custom system apps), but no promises.
Extract the folder (ES File Explorer or 7 Zipper) to "extsdcard/TWRP/backups/[serial number]" then boot into recovery and restore the image. The easiest way to get this folder is to simply perform a backup first, then unzip this folder next to the one for the backup you just created.
I didn't factory reset prior to this backup because it's just system partitions, so let me know if there's anything weird.
https://drive.google.com/open?id=0B2iEgzRTFjrQa2JEbE1DSE9qNHM
Here's the Odin ROM:
http://forum.xda-developers.com/note-3-sprint/general/rom-odin-ph1-update-t3463178/page1
Here's my non-rooted TWRP ROM:
http://forum.xda-developers.com/not...stom-recovery-rom-stock-rooted-t3449321/page1
Still 5.0 this is probably just a security update
RDF
http://device.sprintpcs.com/Samsung/SM-N900P-SPRINT/PH1.rdf
evilvoice said:
Still 5.0 this is probably just a security update
RDF
http://device.sprintpcs.com/Samsung/SM-N900P-SPRINT/PH1.rdf
Click to expand...
Click to collapse
Yep, just a security update most likely. Looks like some of the stock (Sprint) apps may have been updated as well . The update file was only about 190 megabytes if I remember correctly.
Quick question on updating modem & firmware.. I'm stock rooted ok2, and i dont have this update yet. I am working toward flashing the newly released and highly anticipated DL Modded N5N7 v4 which requires the PH1 updated firmware.
Do I need to ODIN flash the update files from the other PHI ROM thread or can I just do a full wipe and flash this backup with TWRP?
Thanks in advance.
Sent from my SM-N900P using XDA Labs
MeAtKeRtN said:
Quick question on updating modem & firmware.. I'm stock rooted ok2, and i dont have this update yet. I am working toward flashing the newly released and highly anticipated DL Modded N5N7 v4 which requires the PH1 updated firmware.
Do I need to ODIN flash the update files from the other PHI ROM thread or can I just do a full wipe and flash this backup with TWRP?
Thanks in advance.
Sent from my SM-N900P using XDA Labs
Click to expand...
Click to collapse
You can just flash the rom you want and keep your current bootloader/modem. But it's always suggested to keep current with any bootloader/modem, that the OP mentioned. That way if there is a issue with the install, it wouldn't be that.
Sent from my Nexus s using XDA-Developers mobile app
jhunt75 said:
You can just flash the rom you want and keep your current bootloader/modem. But it's always suggested to keep current with any bootloader/modem, that the OP mentioned. That way if there is a issue with the install, it wouldn't be that.
Sent from my Nexus s using XDA-Developers mobile app
Click to expand...
Click to collapse
The preferable answer would have been 'NO' or 'I'M NOT SURE' as a direct answer to my very specific question... as I now have a phone that doesn't make phone calls.
MeAtKeRtN said:
The preferable answer would have been 'NO' or 'I'M NOT SURE' as a direct answer to my very specific question... as I now have a phone that doesn't make phone calls.
Click to expand...
Click to collapse
Hey, I've seen you in a few threads and figured I ask before I made the same mistake. I'm looking to upgrade to DL Modded N5N7 v4 like yourself. I have a exploding Note 7 still and I'm anticipating being blacklisted at some point. As crazy as it sounds I like my Note 3's snappiness and everything else over the 7. My issue is my Note 7 radio gets 4g in my job and my Note 3 radio is 3g or spotty. I'm sure my modem and baseband is outdated and may help being updated
I'm on a older Moars Rom Baseband Nk4 android version 4.4.2. Did you figure out where things went bad. I was thinking of following these instructions http://forum.xda-developers.com/note-3-sprint/general/rom-odin-ph1-update-t3463178 don't want to mess this up.
What did you use and what should you have used?
Thanks
Lyvewire said:
Hey, I've seen you in a few threads and figured I ask before I made the same mistake. I'm looking to upgrade to DL Modded N5N7 v4 like yourself. I have a exploding Note 7 still and I'm anticipating being blacklisted at some point. As crazy as it sounds I like my Note 3's snappiness and everything else over the 7. My issue is my Note 7 radio gets 4g in my job and my Note 3 radio is 3g or spotty. I'm sure my modem and baseband is outdated and may help being updated
I'm on a older Moars Rom Baseband Nk4 android version 4.4.2. Did you figure out where things went bad. I was thinking of following these instructions http://forum.xda-developers.com/note-3-sprint/general/rom-odin-ph1-update-t3463178 don't want to mess this up.
What did you use and what should you have used?
Thanks
Click to expand...
Click to collapse
My mistake was following bad advice and flashing the TWRP Backup of PH1 in the OP of this thread instead of ODIN flashing the full ROM-ODIN-PH1- Update- t3463178.
I was able to get TWRP to restore my backup to OK2. From there I did a full wipe 3x and ODIN flashed the full PH1 update, immediately rooted with CFautoroot and reinstalled TWRP 2.8.7.0.
From there I followed the OP instructions in the DL Modded N5N7 thread which require the ROM, Kernel Cleaner, MVNO Buzbee2, Sprint VVM, and I installed the DL MM UIX Kernel.
The ROM and kernel are both really well put together except my mobile network connection to Sprint has been intermittent... the phone was stuck roaming and was connecting in spurts with Verizon, sprint, or the network was unavailable.
I just dirty flashed the Rom, Kernel, and MVNO fix an hour or so ago and the APNs seem to be sticking now. We'll see.
I have three Note 3's and each has its own quirky 'personality'- not especially playing nicely with most of the Port ROMs available these days. Hope this answers your questions and helps someone else trying to keep their Note 3 thriving.
MeAtKeRtN said:
The preferable answer would have been 'NO' or 'I'M NOT SURE' as a direct answer to my very specific question... as I now have a phone that doesn't make phone calls.
Click to expand...
Click to collapse
I am not trying to start any trouble, but from reading your comment it seems you are suggesting I gave you bad or wrong advice. So I want to explain myself just in case it was a misunderstanding. All roms are capable of being flashed with older bootloaders and modems. But the proper thing to do, is to always be up to date with all bootloader/modem files. This way you will not run into any problems. Now I didn't mention anything about flashing the OP'S twrp backup method. I figured you may have been experienced enough to flash these BL/modem files from a source like sammobile. Then proceed to flash your rom of choice. As you experienced you lost your signal. It may have been a few reasons why this happen. 1. The way the OP mentioned to flash wasn't meant for your phone. Every phone response differently. 2. The rom for whatever reason can only be used if you dirty flashed over your current system. This will not be the only time you may have to do it this way. So instead of being sarcastic with your reply, maybe try and ask the one who is helping you to explain themselves more. We are all here to help each other, and by no means was my response to your question was meant to harm your phone.
Sent from my SM-N920C using XDA-Developers mobile app
jhunt75 said:
I am not trying to start any trouble, but from reading your comment it seems you are suggesting I gave you bad or wrong advice. So I want to explain myself just in case it was a misunderstanding. All roms are capable of being flashed with older bootloaders and modems. But the proper thing to do, is to always be up to date with all bootloader/modem files. This way you will not run into any problems. Now I didn't mention anything about flashing the OP'S twrp backup method. I figured you may have been experienced enough to flash these BL/modem files from a source like sammobile. Then proceed to flash your rom of choice. As you experienced you lost your signal. It may have been a few reasons why this happen. 1. The way the OP mentioned to flash wasn't meant for your phone. Every phone response differently. 2. The rom for whatever reason can only be used if you dirty flashed over your current system. This will not be the only time you may have to do it this way. So instead of being sarcastic with your reply, maybe try and ask the one who is helping you to explain themselves more. We are all here to help each other, and by no means was my response to your question was meant to harm your phone.
Click to expand...
Click to collapse
No misunderstanding here... I asked a specific either/or question directly related to the thread topic (twrp custom recovery version) and you either misunderstood my question or decided it required an answer other than a 'yes or no' As a result of your longwinded answer, I lost several hours working through how to get a signal back on my phone. Was pretty annoying.
MeAtKeRtN said:
No misunderstanding here... I asked a specific either/or question directly related to the thread topic (twrp custom recovery version) and you either misunderstood my question or decided it required an answer other than a 'yes or no' As a result of your longwinded answer, I lost several hours working through how to get a signal back on my phone. Was pretty annoying.
Click to expand...
Click to collapse
I never knew giving someone detailed information was a problem. It's funny how I never had an issue with the install, but you did. It seems you lack enough experience to realize a few things. But I will make it a point to never help you again. Whether that's to long-winded or not for you, oh well.
Sent from my SM-N920S using XDA-Developers mobile app
MeAtKeRtN said:
No misunderstanding here... I asked a specific either/or question directly related to the thread topic (twrp custom recovery version) and you either misunderstood my question or decided it required an answer other than a 'yes or no' As a result of your longwinded answer, I lost several hours working through how to get a signal back on my phone. Was pretty annoying.
Click to expand...
Click to collapse
Did you get it all figured out?
I did get it figured out. Wasn't much more than an unnecessary inconvenience that someone else might be able to avoid.
Ok, so something weird...
Im running KK4.4.2 with the NC5 baseband on Sprint.
I upgraded my TWRP to 2.780 to flash the recovery both first time 'dirty flashing' and the 2nd time doing a facory wipe.
I removed the battery after the flash.
When I reboot, the phone stays on the Yellow Sprint screen and the LED pusles blue slowly. So far been doing it for 15 mintues.
What am I missing?
Dave
Unidave199 said:
Ok, so something weird...
Im running KK4.4.2 with the NC5 baseband on Sprint.
I upgraded my TWRP to 2.780 to flash the recovery both first time 'dirty flashing' and the 2nd time doing a facory wipe.
I removed the battery after the flash.
When I reboot, the phone stays on the Yellow Sprint screen and the LED pusles blue slowly. So far been doing it for 15 mintues.
What am I missing?
Dave
Click to expand...
Click to collapse
Give it 30 minutes? It seriously takes a long time. Are you sure you want to upgrade to lollipop? In just asking because you've been on Kit Kat long after support for lollipop or this phone has long stopped. I'd suggest downloading the latest Odin and flashing that instead, unless there is something here you wanted? I'm rooted on PL1 and have no issues other than my phone being as old as it is and how many times it's been flashed.
evilvoice said:
Give it 30 minutes? It seriously takes a long time. Are you sure you want to upgrade to lollipop? In just asking because you've been on Kit Kat long after support for lollipop or this phone has long stopped. I'd suggest downloading the latest Odin and flashing that instead, unless there is something here you wanted? I'm rooted on PL1 and have no issues other than my phone being as old as it is and how many times it's been flashed.
Click to expand...
Click to collapse
30 minutes? Woah that is a long time. Ok I will give it a try sometime when I go to bed.
I am mainly trying to get the PL1 update and not mess with Odin if I can get around it. I would like to try and port the Darklord Marshmellow ROM and take advantage of built in google assistant
So I thought I would try them. And always get back if I need to but wanted to keep the PL1 modem updates.
I only have one problem with one other phone user... She doesnt always get my texts and I dont always get hers. I dont know if others arent getting them and just dont know but my 1 friend I text a lot so she notices when there is a gap.
Anyways. Just feeling out how I can maximize this phone's performance. NO plans on changing phones anytime soon.
Unidave199 said:
30 minutes? Woah that is a long time. Ok I will give it a try sometime when I go to bed.
I am mainly trying to get the PL1 update and not mess with Odin if I can get around it. I would like to try and port the Darklord Marshmellow ROM and take advantage of built in google assistant
So I thought I would try them. And always get back if I need to but wanted to keep the PL1 modem updates.
I only have one problem with one other phone user... She doesnt always get my texts and I dont always get hers. I dont know if others arent getting them and just dont know but my 1 friend I text a lot so she notices when there is a gap.
Anyways. Just feeling out how I can maximize this phone's performance. NO plans on changing phones anytime soon.
Click to expand...
Click to collapse
I still use my note 3. Granted not for main phone as I switched to iPhone, but I use it every day. I don't really know the hesitation of using Odin, but to each their own. If you did decide to use Odin, I'd flash the ROM, boot it, go to download mode again, flash TWRP, boot recovery (so it sticks and doesn't go back to stock recovery), flash SuperSU, done. You're rooted on PL1. Hopefully you have already backed up your text messages and other various things to either SDCard or something else. I'm not sure if that survives whether you wipe and flash clean or Odin. Depending on provider, that could be your issue with text messages. If you're with Sprint, check that you are on latest PRL. If not, make sure APN settings are correct.
If you're only looking for Assistant, I had it running on stock PL1. XDA did a blog post about enabling it in Lollipop, so once you upgrade, check it out. I couldn't stay on Marshmallow. Being that these are ports and not specifically built for our phone, I ran into issue with every single ROM either not being able to place calls, text (MMS actually), or wireless/data not working. No matter what I changed APN to, I would always have issues. Some do not. I just can't recommend a port when they haven't worked for me. Some roms have been abandoned, which meant if I found one that I could at least handle, it was so outdated that it was unusable (issues had arisen and the developer had moved on so they weren't being fixed). By handling a rom, I mean that after I upgraded to iPhone, I only needed wireless to work (to connect to hotspot) and it not go into a boot loop or crash all the time (some do). Those roms I have no idea if calls or text work because I wasn't using that. A lot have issues with wireless working.
One more thing you can try is to do a flash, wait about 30 minutes. If it still doesn't boot, pull the battery and reboot into recovery. Wipe data and cache and reboot again. It should boot. It'll still take a long time. Make sure you wait the 30 minutes before pulling the battery (it should have finished upgrading your system by then). Do note that first boot from now on will take forever no matter if it's a port or stock. Lollipop and higher take a long time to upgrade. I've only had 1 or 2 roms take around 5 minutes and that's because they were minimalist and without Google apps. The phone does get a little warm and uses a lot of battery, so I'd keep it plugged in.
Please report back if you got it to work and how. Like I said, I still use mine. I still visit this forum every day even though I've had an s5 and an s7 edge. I love this phone. I need to get mine replaced because I've worn it out: broken charger port so I have to make sure the cable is plugged in a certain way and I can't touch the phone while charging, side molding is broken off in places, some of my partitions can't be changed which means the memory is failing (not even Odin flashes correctly anymore let alone custom roms). But, it still keeps on ticking.
evilvoice said:
I still use my note 3. Granted not for main phone as I switched to iPhone, but I use it every day. I don't really know the hesitation of using Odin, but to each their own. If you did decide to use Odin, I'd flash the ROM, boot it, go to download mode again, flash TWRP, boot recovery (so it sticks and doesn't go back to stock recovery), flash SuperSU, done. You're rooted on PL1. Hopefully you have already backed up your text messages and other various things to either SDCard or something else. I'm not sure if that survives whether you wipe and flash clean or Odin. Depending on provider, that could be your issue with text messages. If you're with Sprint, check that you are on latest PRL. If not, make sure APN settings are correct.
If you're only looking for Assistant, I had it running on stock PL1. XDA did a blog post about enabling it in Lollipop, so once you upgrade, check it out. I couldn't stay on Marshmallow. Being that these are ports and not specifically built for our phone, I ran into issue with every single ROM either not being able to place calls, text (MMS actually), or wireless/data not working. No matter what I changed APN to, I would always have issues. Some do not. I just can't recommend a port when they haven't worked for me. Some roms have been abandoned, which meant if I found one that I could at least handle, it was so outdated that it was unusable (issues had arisen and the developer had moved on so they weren't being fixed). By handling a rom, I mean that after I upgraded to iPhone, I only needed wireless to work (to connect to hotspot) and it not go into a boot loop or crash all the time (some do). Those roms I have no idea if calls or text work because I wasn't using that. A lot have issues with wireless working.
One more thing you can try is to do a flash, wait about 30 minutes. If it still doesn't boot, pull the battery and reboot into recovery. Wipe data and cache and reboot again. It should boot. It'll still take a long time. Make sure you wait the 30 minutes before pulling the battery (it should have finished upgrading your system by then). Do note that first boot from now on will take forever no matter if it's a port or stock. Lollipop and higher take a long time to upgrade. I've only had 1 or 2 roms take around 5 minutes and that's because they were minimalist and without Google apps. The phone does get a little warm and uses a lot of battery, so I'd keep it plugged in.
Please report back if you got it to work and how. Like I said, I still use mine. I still visit this forum every day even though I've had an s5 and an s7 edge. I love this phone. I need to get mine replaced because I've worn it out: broken charger port so I have to make sure the cable is plugged in a certain way and I can't touch the phone while charging, side molding is broken off in places, some of my partitions can't be changed which means the memory is failing (not even Odin flashes correctly anymore let alone custom roms). But, it still keeps on ticking.
Click to expand...
Click to collapse
Come back to Android! We miss you!!!!
Yes I am backed up and also have a Titanium Backup of everything so I am pretty much covered... I have even backed up the backups to my PC!
You have much wisdom in what you are saying. I thought I would play around with some other ROM's and see what the potential is.
I hear good things about the Darklord Reborn by Midevil and JCorderno so thought I would investigate.
I am not opposed to using Odin, but I was at work, and no access to a computer so wanted to see if I could do the upgrade 'on the fly' since I am already rooted and with recovery.
Man, waiting 30 minutes for a phone to boot sounds like a anxiety attack waiting to happen! But still wanna give it a try.
As to your USB port. Have you thought of going wireless charging? I did and haven't looked back! You can get a wireless charging back and a case that will fit at...
for the charging back
https://smile.amazon.com/Samsung-Ga...=8-2&keywords=samsung+note+3+wireless+charger
for the case
https://smile.amazon.com/gp/product/B00F3KP156/ref=oh_aui_search_detailpage?ie=UTF8&psc=1
Clone Wars....
Just wanted to put out a big THANKS for this.. I broke my Note 3 after 2,433 days (long story) but had bought a stock spare on Ebay last year... Making the switch now, but your PH1 Flashable update is making it super easy!
To let everyone who needs to use this nowdays... you will need to Flash an older TWRP (I used 2.7.8) in order to allow the Modem partition to be overwritten. Then you can flash up to 3.x to load a Android 10 based rom.