Database Info

[Q] Noob question regarding to odin and clockwork

Hi,
I am very new to android and Samsung captivate. I am thinking of installing froyo on it.
I was reading that with Odin and Clockwork, this can restore your phone to original factory state after you have rooted or do anything crazy with the phone.
My question is, with this factory state restoration through these programs, does this also "unvoid" the phone warranty? Is this method untraceable to ATT or samsung?

Good question, I'm curious about that as well. Anyone know if odin leaves a trace that AT&T can track?

Is there anyone who knows about this? I want to install the custom rom, but I want to make sure about everything first.

In my admittedly general experience, AT&T doesn't do a lot of RMA snooping beyond trying to start it up. I wouldn't take that as gospel, but I've returned two (dumb) phones to AT&T, and all they did was try to start it up, take a new phone out of a new box and do a direct swap.

I am not sure what happens when you send them in, but I have returned two Captivates back to the AT&T store. One for reception problems and the other for the random shutdown issue. Both were flashed...then reflashed with Odin and there was no issue with the return. If it has to be sent in, there may be more thorough methods they use. But in store it's start it up, they looked through a few menus, but that was about it.

[Q] com.Android.phone crashes after root Samsung Admire

Last week I rooted my primary phone, a Samsung Admire with Gingerbread 2.3.4. This was done only after successfully rooting my older LG Optimus T running Fryo. I had no trouble with either phone during the process. However, as of 2 days ago the Admire has had some troubles, namely that the phone function crashes when I press the send key. I get the error message stating “Sorry! The process com.android.phone has stopped unexpectedly. Please try again.” It will receive incoming calls but they cannot be answered and when I try, it crashes
I’ve spent much of the time since researching the problem to find the cause and it’s fix. In doing d\so I have read of multiple causes from screen resolution changes to attempted over clocking, which I have played with. I’ve read that there might be problems with the phones attempting to switch from 2g to 3g too rapidly, something this phone cannot do I believe.
I came to the conclusion, probably erroneously, that I needed to reset it back to factory and then reinstall apps and data out of the backup I made using Titanium Backup prior to the phones troubles. So I did so, doing the three button cocktail I’ve read about here on XDA Forums. After doing this, the problem persists. I’ve read some more becoming more baffled as I went along. So I tried to reroot the phone using one click root, and that was unsuccessful as well, no root. I then read that all I needed to do was to install Superuser from the Market. In attempting this I found my device was no longer recognized by Market and after going through their troubleshooting process it’s still unrecognized, Next I decided, also most likely erroneously to reset the phone again using the three button combo as before. This time I noticed at the bottom of the screen written in yellow, E: File is written: not updated
Also as a side note my phone currently says that there are 133MB available and after the reset(s) my bloat ware has not returned,
So that’s it. I seem to have deleted something that kills the phone app and prevents me from rooting. Other than those two things the phone is working well. However as it sits it’s merely a small Internet tablet with no phone capability. Can anyone help me out with this? And yes, I have read and read and read about it but clearly this is beyond my ability to fix on my own.
Thanks,
Zeke

Hey, my skill level ranges between beginner and intermediate, but honestly in a situation like that I would odin back to stock. I have an epic 4g, so I have no idea what your download mode is or if you have one or if you have to use quick boot or fast boot? Its one of those. If **** ever hits the fan on me (Thank god it hasn't yet) I would odin to an old stock rom and root it and install a recovery and wipe and flash a ROM. Good luck I hope I helped and didn't sound like too much of a scrub.

Reached said:
Hey, my skill level ranges between beginner and intermediate, but honestly in a situation like that I would odin back to stock. I have an epic 4g, so I have no idea what your download mode is or if you have one or if you have to use quick boot or fast boot? Its one of those. If **** ever hits the fan on me (Thank god it hasn't yet) I would odin to an old stock rom and root it and install a recovery and wipe and flash a ROM. Good luck I hope I helped and didn't sound like too much of a scrub.
Click to expand...
Click to collapse
I will research this Odin you mention as I have no clue as to what it is. Thanks, anyone else care to chime in?
Zeke

Noob root now slightly bricked G Flex 2

Hi all. My new phone was going greatish. It was a little laggy, so thought I would root it and remove some of the preinstalled junk. All went fine no problem.
I removed some of the vodafone (UK) stuff, and all was well. Some time later though, I get a message:
"Unfortunately, the process com.android.phone has stopped"
And now my phone won't find the network and message pops up every couple of seconds. I tried a factory reset, but I suspect this made it worse as I have now lost my backups from Titanium app. The phone is basically unusable as it is due to constant error message and no network.
I have tried to access the recovery menu, but i get an empty robot with "no command".
I have seen some mention of CIDs on other forums but haven't got a clue how to go about fixing it or even where to start.
Any help would be greatly appreciated as obviously the phone is absolutely brand new, and I'm very very upset about the whole thing! Not to mention the fact that I feel like an idiot!
Anyway, thanks in advance.

You deleted something that was not suppose to be deleted. Don't the stock tot file on this forum and follow the steps to Flash back to factory
http://forum.xda-developers.com/g-flex2/general/guide-lg-g-flex-2-stock-firmware-to-t3037593 follow the video and you should be up in running in no time . make sure this link support your version not sure which g flex2 Version you have.

Still no tot files available for the LG G Flex 2 (any variant). Sorry got to wait for some to become available.

Thanks for the input. I figured it would be something like that. Any idea when the files might be available? I don't mind being a guinea pig at this stage. My phone is LG H955 on Vodafone UK.
I am going to try and play dumb in Vodafone shop today and see if they'll replace it there and then (doubtful).
I suppose my other alternative is to return it to LG for Firmware Flash. Anyone know if this is possible and potential cost?
Strangely, I'm not so bothered about (temporarily) destroying my brand new phone too much, it's my sudden lack of connectivity that hurts the most.
Thanks guys

Further update; I have spoken to LG tech support / repair department, and I told them the phone had been rooted etc. (I didn't leave any identifying details!) They informed me that as the phone was now out of warranty, I should speak to their service partner SBE.
After calling SBE, they informed me that LG or their partner have no obligation to fix rooted phones, so apparently they just won't do it, even though I'm certain they could, which kind of sucks, as I was obviously willing to pay.
So it looks like I'm waiting for the TOT files. I hope they come along soon!
Lesson well and truly learned!

djjag1 said:
Further update; I have spoken to LG tech support / repair department, and I told them the phone had been rooted etc. (I didn't leave any identifying details!) They informed me that as the phone was now out of warranty, I should speak to their service partner SBE.
After calling SBE, they informed me that LG or their partner have no obligation to fix rooted phones, so apparently they just won't do it, even though I'm certain they could, which kind of sucks, as I was obviously willing to pay.
So it looks like I'm waiting for the TOT files. I hope they come along soon!
Lesson well and truly learned!
Click to expand...
Click to collapse
Stay positive. Hopefully those tot files come soon. I on the other hand what to experiment with my phone but need a tot file just in case I mess anything up.
If it's just your dialer that's acting up, have you tried a third party dialer to make phone calls?

djjag1 said:
Further update; I have spoken to LG tech support / repair department, and I told them the phone had been rooted etc. (I didn't leave any identifying details!) They informed me that as the phone was now out of warranty, I should speak to their service partner SBE.
After calling SBE, they informed me that LG or their partner have no obligation to fix rooted phones, so apparently they just won't do it, even though I'm certain they could, which kind of sucks, as I was obviously willing to pay.
So it looks like I'm waiting for the TOT files. I hope they come along soon!
Lesson well and truly learned!
Click to expand...
Click to collapse
Lets see if we can work on this.
Is it working ok, just not picking up the network?
How long exactly have you had it?

If you put what you all deleted meaning what folders they were in i could make a copy of that folder or apps you deleted and upload them on dropbox for you that might help get you going worth a shot
Be better if someone had the same variant as you i have the Sprint model.

Thanks again for input. I have hopefully managed to sort this with my provider. I was just within the 14 day cancellation period, so I have arranged for a brand new handset. I know its a little bit naughty but if the phone wasnt so laggy to begin with, I would never have rooted it.
I'm guessing it makes no difference to them as the phone will go back to lg for wipe and reflash as a matter of course once returned.
Thanks folks, I will remain on this forum and hopefully not do anything quite so stupid again!

Unfortunately this is my last day with this device . Great phone but i was wrong the 810 processor is dangerously hot to the point it felt like my pockets were on fire. This my second g flex2 and I'm moving on to something more reliable. Love this phone but this heat issue i can't risk. After 14 days i would be stuck with this phone and i can't take the risk of hoping of getting a device that function fine bye everyone.

:victory::victory::victory:

Today, I've gotten myself in a similar pickle after applying noob root.. Data OK but no phonecalls and no txts. When I tried to make a call, the thing said the phone is not activated. Sprint tech supp was of course no help, so after some digging I found this: ##72786#
Factory reset, keep the data (and all apps).
That solved it.
I guess I'm old enough to know that being lazy doesn't pay.

Stank0 said:
Today, I've gotten myself in a similar pickle after applying noob root.. Data OK but no phonecalls and no txts. When I tried to make a call, the thing said the phone is not activated. Sprint tech supp was of course no help, so after some digging I found this: ##72786#
Factory reset, keep the data (and all apps).
That solved it.
I guess I'm old enough to know that being lazy doesn't pay.
Click to expand...
Click to collapse
so you had root, and while doing this factory reset you were able to go back to full stock unrooted rom? if so, were you able to install updates? i too have a sprint version and i was rooted and tried installing an update but failed, i then unrooted my phone tried the update again and still got an error. im just wondering if this method would actually help people who have the same problem as i do.

gothikzoul said:
so you had root, and while doing this factory reset you were able to go back to full stock unrooted rom? if so, were you able to install updates? i too have a sprint version and i was rooted and tried installing an update but failed, i then unrooted my phone tried the update again and still got an error. im just wondering if this method would actually help people who have the same problem as i do.
Click to expand...
Click to collapse
Unfortunately, that wasn't the case.
I tried every possible way to install this damn update. Rooted, unrooted, factory reset 4 times, tried to install from the system update in settings, from recovery (which is, at least for me, very tricky to get into) all efforts errored out.
I posted a link to the update.zip in other thread.
So then I gave up and used this noob root which killed voice calls and text.
This code I posted says it does a factory reset but is resetting something else than other factory resets because almost all my settings, passwords and all apps remained intact.. Then I used the original root method and everything works like it's supposed to.
I guess we'll have to wait until someone finally starts developing for our phone.

So after a few days I just received a notification for the update for the third time. Any suggestions as to how I should proceed? I've tried it while being rooted and failed, also tried it the second time after unrooting and failed too. Also, what is the default location where the update is downloaded to, so I can back it up.

So far nothing has worked. The update should be in the cache folder. There is also a link to download the update that someone posted in another thread here about the update.

FYI - I forced the update through recovery over root and bricked my phone. Like all the way bricked. I can get to recovery and download mode, but no fastboot even. Luckily I was within my 14 days and there is no way to tell it is rooted... because it doesn't even get that far, so I got a replacement. My sincere advice would be to wait to root until we have custom recovery and stock firmware available, and if you have root now, wait to update until a dev can release a "root safe" version.
I'm not an expert but I'm not new either. I got the original Evo on launch day and have done all kinds of dumb stuff to every phone since. This is the first time I haven't been able to recover it.

austontatious said:
FYI - I forced the update through recovery over root and bricked my phone. Like all the way bricked. I can get to recovery and download mode, but no fastboot even. Luckily I was within my 14 days and there is no way to tell it is rooted... because it doesn't even get that far, so I got a replacement. My sincere advice would be to wait to root until we have custom recovery and stock firmware available, and if you have root now, wait to update until a dev can release a "root safe" version.
I'm not an expert but I'm not new either. I got the original Evo on launch day and have done all kinds of dumb stuff to every phone since. This is the first time I haven't been able to recover it.
Click to expand...
Click to collapse
=( *hug. That sucks man, thankfully you were able to get it replaced. *pfew I dodged a bullet there. I was actually thinking about doing the same thing getting home from work. Yeah its best we don't mess with the phone any longer those that have root at the moment. Until custom recovery and stock rom is out like he says.

Wow. How did you manage to "force" the update through recovery? I tried it through recovery but it would error out. (Error 7)

I will tell you, as a cautionary tale.
The error when you flash from recovery references a specific file that is incompatible with the update. I used root explorer to investigate further and found that the root script had overwritten a system file. The original was saved as "original" so I deleted the file causing the error and renamed the original one. After that, the update went through and I thought I was golden... Only now nothing else works.

Please help with my Samsung galaxy 6 edge (sm-g925A)

So, about a month ago I decided to factory reset my phone. I got it to factory binary mode, that was what I wanted to do because the phone kept messing up, getting hot, etc. I figured I’d reset it, download my apps back that I used a lot and everything else would be erased so I could start fresh, rather than going through every single thing in my phone and deciding what to get rid of, and what to keep.
Of corse, I have a AT&T phone that apparently makes this complicated with the Samsung factory reset protection. I got this phone from someone I used to have a relationship type of connection with, and I did ask for the help from them, they couldn’t remember the login info for their old phone.
Basically what I’m asking here is when in factory binary mode, with FRP on, can I get back to the phones regular system? I’ve never done this before, and now I regret it more than anything. I didn’t backup my phone or anything, I’ve tried several times reading countless thin about flashing a phone and blah blah, so, does ANYONE know what I should do? I recently lost my job and buying anything isn’t an option, espicaly those websites that say you have to pay to get the FRP deleted.
Is there ANYTHING I can do a thing this point? I’ve heard with the FRP still on, that I can’t download the stock rom back or really do anything, is this true? Can anybody please help! This is my last resort, I’ve spent countless hours trying to google and read articles and this forum was the only place I saw people actually getting help and getting their problems resolved.
Thanks for your time, and the replies. Sorry if this is the wrong sub forum, I’m new here.

Bringing up my post, still no replies yet.

Question OTA Updates failing with, "partition superReason SUPER: Build-id does not match with the reference"

**Solved posting update in thread.
Purchased S21+ from Samsung online for Verizon Network, every OTA update since purchase results in it failing to the downloading screen with "
partition super Reason SUPER: Build-id does not match with the reference" I have been able to resurrect it successfully by entering the recovery mode and performing a factory reset. But each OTA update push results in the same issue.
Samsung wants me to either send them the phone or take to a repair location for a software refresh as they called it. Problem is nearest repair center is 3+ hours away from me or 5-7 day turn around on the mailed device with no backup phone.
Has anyone else encountered this and does anyone here have a solution to fix this myself? I am comfortable using Odin and flashing roms but not sure if this will fix it.

have you talked to verizon?

Post Nine said:
have you talked to verizon?
Click to expand...
Click to collapse
Yes, Spoke with their Tier 2 support. Tier 2 discussed the issue and implied a change of information for the phone would fix it. They transferred me to Samsung due to the phone being purchased direct from Samsung.

Ok so the problem seems to have been resolved. Here's what I did to fix it.
Downloaded the current firmware I had before the update from Sammobile.com. Using Odin I installed the firmware I was currently on. I had done this before on the last update that failed. But this time I gave it the user data info and did use the Home CSC in an effort to reset everything.
Phone came back online functioning normally with everything wiped. I connected to WiFi and let the first of 2 updates download then run. Success . First OTA that's been successful on the phone. Then went for update #2. Failed, but rebooted this time and gave me an Error 402. Tried again a little later, same WiFi. It redownloaded the update and success again.
So it seems it needs a very very stable internet connection and the full wipe fixed the build id mismatch.
Also before attempting updates highly recommend having all your 2FA accounts either backed up, a second authenticator on another device or turned off. Its a real PITA to get back into all your accounts when your authenticator app gets wiped unexpectedly.
Hope this helps someone else!

CBH60 said:
Hope this helps someone else
Click to expand...
Click to collapse
Thank you!!! I was stuck on this screen all day!
I had restored my S22 Ultra, as a last resort to troubleshoot the shut down/reboot issue I, like many others, have been experiencing. When my phone then updated itself afterward, the install failed and I was stuck. I just happened to find this post of yours, while I was researching some info someone at the Geek Squad gave me, and told me to try it when I got home. The print out he gave me was a word for word copy of your solution! It totally worked, and I am back in. Now to see if the shut down/reboot issue recurs..... I suspect it will, I'm thinking it has something to do with my battery, which I can't remove.

Ardera_Sempre said:
Thank you!!! I was stuck on this screen all day!
I had restored my S22 Ultra, as a last resort to troubleshoot the shut down/reboot issue I, like many others, have been experiencing. When my phone then updated itself afterward, the install failed and I was stuck. I just happened to find this post of yours, while I was researching some info someone at the Geek Squad gave me, and told me to try it when I got home. The print out he gave me was a word for word copy of your solution! It totally worked, and I am back in. Now to see if the shut down/reboot issue recurs..... I suspect it will, I'm thinking it has something to do with my battery, which I can't remove.
Click to expand...
Click to collapse
Hey did you ever get this screen again? And were OTA updates normal after you flashed?
OTA updates keep failing for me on my S22+, either at 25% causing it to go back to the old firmware with an error message, or getting bricked showing that screen. I've tried to reflash and then update and so far only solution is flashing the update through Odin every time. I have had only 2 successful OTA updates since I got this phone in April

AliRAS said:
Hey did you ever get this screen again? And were OTA updates normal after you flashed?
OTA updates keep failing for me on my S22+, either at 25% causing it to go back to the old firmware with an error message, or getting bricked showing that screen. I've tried to reflash and then update and so far only solution is flashing the update through Odin every time. I have had only 2 successful OTA updates since I got this phone in April
Click to expand...
Click to collapse
I did not have any further issues with updates failing, and getting this screen again. I DID have to send my phone back to Samsung twice though for repair, because of the constant rebooting issue. They could NOT repair that issue, so I ended up getting a refund for the phone. Due to their p**s poor customer service (more than a month later I'm still trying to get them to return the charger for the phone, that they said I HAD to send back with the phone for testing), I will (very unhappy) be purchasing an iPhone. Never buying Samsung again.

Ardera_Sempre said:
I did not have any further issues with updates failing, and getting this screen again. I DID have to send my phone back to Samsung twice though for repair, because of the constant rebooting issue. They could NOT repair that issue, so I ended up getting a refund for the phone. Due to their p**s poor customer service (more than a month later I'm still trying to get them to return the charger for the phone, that they said I HAD to send back with the phone for testing), I will (very unhappy) be purchasing an iPhone. Never buying Samsung again.
Click to expand...
Click to collapse
Damn that sucks never heard of them needing the charger as well for tests, that is a bit odd. The reflash seems to have fixed the rebooting issue I had when I first got my S22+ not sure if I should gamble with trying to update again after the last one failed. Might just wait for One UI 5 and do a dirty flash through Odin and if it doesn't give any problems I'll just flash the security updates every so often I guess. Saves me the stress haha.