I rooted my Epic 4G with the new Epic Experience Rom recently. I am going to return the phone, but they won't take it back rooted. I couldn't find anything in search. Does anyone know how to erase any trace of my phone being rooted?
Thanks everyone.
Edit: nm read his post wrong.
RootTheWorld said:
I rooted my Epic 4G with the new Epic Experience Rom recently. I am going to return the phone, but they won't take it back rooted. I couldn't find anything in search. Does anyone know how to erase any trace of my phone being rooted?
Thanks everyone.
Click to expand...
Click to collapse
ODIN, and an official release, not Froyo.. Use the DI18 Package..
Also remember to wipe your SD card too which will not be touched during install. ODIN will flash over EVERYTHING making it brand new.
Why would you want to return your Epic? I hope not to get an EVO.. The EVO is a good phone and I wanted it when it first came out, my gut kept telling me to wait and the EPIC really is a good phone.
brian_hoffman said:
ODIN, and an official release, not Froyo.. Use the DI18 Package..
Also remember to wipe your SD card too which will not be touched during install. ODIN will flash over EVERYTHING making it brand new.
Why would you want to return your Epic? I hope not to get an EVO.. The EVO is a good phone and I wanted it when it first came out, my gut kept telling me to wait and the EPIC really is a good phone.
Click to expand...
Click to collapse
Last time I had to take my phone into a sprint store, I ODIN'ed back to DI18 and thought that it removes root as I've read in multiple posts but apparently it doesn't because the technician said the phone is rooted and although they will service the phone this time, root voids warranty and they put a note on my account to check if phone is rooted if i ever take it back again. My speaker just died, so I ODIN'd and used this to remove root.
http://forum.sdx-developers.com/epi...ecovery-1-13-for-windows-intel-mac-and-linux/
When I took it in, they didn't mention anything about root. So either they didn't check or they saw phone wasn't rooted.
For you those going back to stock or are stock and u flashed 2.2 and want to downgrade or resort back to stock use this method.
Rooted/clockwork users skip the first step...
1. Do the one click root/clockwork/etc Here
2. Flash the d118 modem Here
3. Then Flash the zip file Here
4. Then flash the get rid of clockwork zip Here
5. Your are back to stock without using odin yay!!!
Now all links work!!! and added a step use this method to return to stock with out odin.
viper786 said:
Last time I had to take my phone into a sprint store, I ODIN'ed back to DI18 and thought that it removes root as I've read in multiple posts but apparently it doesn't because the technician said the phone is rooted and although they will service the phone this time, root voids warranty and they put a note on my account to check if phone is rooted if i ever take it back again. My speaker just died, so I ODIN'd and used this to remove root.
http://forum.sdx-developers.com/epi...ecovery-1-13-for-windows-intel-mac-and-linux/
When I took it in, they didn't mention anything about root. So either they didn't check or they saw phone wasn't rooted.
Click to expand...
Click to collapse
Perhaps,
If you ODIN to an offical "virgin" Rom you will lose root.. Period. If you dont believe me do it then try and run any app that requires root "like wifi tether" it will not work. There are roms that work with odin that are pre rooted.
What I got from the other thread was Sprint can tell by some method what OS version and build you have been using while connected to thier network... so if this is true they may be able to tell your running an "Epic Experience" build and put 2&2 together that you have rooted.
The fact of the matter is, if you are running software not designed for the phone or not ready to be released and things do not work then they waste countless man hours trying to figure our why things force close on a product that is no longer thiers.
So, it is not hard to see why they do not like people rooting thier devices.
If you ODIN back and still have the speaker problem then it is SAFE to assume its a hardware rather than a software problem regardless of your past programs that have run on the phone.
brian_hoffman said:
Perhaps,
If you ODIN to an offical "virgin" Rom you will lose root.. Period. If you dont believe me do it then try and run any app that requires root "like wifi tether" it will not work. There are roms that work with odin that are pre rooted.
What I got from the other thread was Sprint can tell by some method what OS version and build you have been using while connected to thier network... so if this is true they may be able to tell your running an "Epic Experience" build and put 2&2 together that you have rooted.
The fact of the matter is, if you are running software not designed for the phone or not ready to be released and things do not work then they waste countless man hours trying to figure our why things force close on a product that is no longer thiers.
So, it is not hard to see why they do not like people rooting thier devices.
If you ODIN back and still have the speaker problem then it is SAFE to assume its a hardware rather than a software problem regardless of your past programs that have run on the phone.
Click to expand...
Click to collapse
I was not aware that they can see what OS i've been using. Anyway, they are replacing the phone and said i should receive the replacement at my house tomorrow. Normally all replacements are sent to them this is the first time i'm getting a replacement sent to my house instead of the store.
Are you sure you searched? One of the very first threads in the development forum...
Sent from my SPH-D700 using Tapatalk
updated instructions to goto stock without odin, see post 5.
Related
I searched and found no answer. My Vibrant is just rooted to turn off the boot up and turn off sounds. Nothing else has done, is the OTA safe for my phone?
parahelium said:
I searched and found no answer. My Vibrant is just rooted to turn off the boot up and turn off sounds. Nothing else has done, is the OTA safe for my phone?
Click to expand...
Click to collapse
There are reports that it works with RyanZA's lag fix and root in some instances.
There are reports that the OTA update bricks even virgin stock phones, so it is a shot in a dark.
Personally I think I'm gonna wait till some one uploads the update and does some testing to see what is making the phone soft brick .
Sent from my SGH-T959 using XDA App
parahelium said:
I searched and found no answer. My Vibrant is just rooted to turn off the boot up and turn off sounds. Nothing else has done, is the OTA safe for my phone?
Click to expand...
Click to collapse
Root is ok but you will have to undo any lagfixes if you applied them.
It will most likely unroot your device but you can use the same method to root again.
dublued said:
Root is ok but you will have to undo any lagfixes if you applied them.
It will most likely unroot your device but you can use the same method to root again.
Click to expand...
Click to collapse
Not to be a downer but not necessarily. I was rooted with no lag fix (currently or prior) at all and it soft bricked my phone. I had the Samsung AP installed but that is about it, didn't remove bloatware or change the startup/shutdown sounds.
Got the phone running again with ODIN so I am back to stock now, without the update
gancho said:
Not to be a downer but not necessarily. I was rooted with no lag fix (currently or prior) at all and it soft bricked my phone. I had the Samsung AP installed but that is about it, didn't remove bloatware or change the startup/shutdown sounds.
Got the phone running again with ODIN so I am back to stock now, without the update
Click to expand...
Click to collapse
What a bummer...I'm rooted w/ Ryans LagFix....hope to hear some good news in a few on a solution...
lqaddict said:
There are reports that it works with RyanZA's lag fix and root in some instances.
There are reports that the OTA update bricks even virgin stock phones, so it is a shot in a dark.
Click to expand...
Click to collapse
does the virgin stock phones mean that it is unrooted or nothing is changed in the out of the box phone?
No Success Here
My Rooted Vibrant that also went through OCLF failed to boot and hung on the Vibrant splash screen. Had to use Odin and the stock build to get it back and running. Thankful I had made backups prior to trying the OTA.
I've since renamed /etc/system/otacerts.zip to stop the OTA update but I would love to get rid of the OTA update icon. Anyone have any ideas?
mine was rooted with just the ji6 modem flashed from odin.. and some other mods like mobile ap and metamorph..
so i got the update.. and it failed on install... ahhh.... flashed back pure stock on odin.. waaaaiiitning.. praying it comes back again!
Stock phone, rooted with no lagfix ever applied.
Phone is toast. I'm at work so waiting for Odin to download slowly so I can reflash the phone to stock.
Might just say skip it and apply one of the custom roms. It seems neither TMO or Samsung can get their **** together. I waited patiently for the OTA and got screwed.
Updated ok with root
My phone had the OCLF v 2.1 plus root installed. Yesterday I removed the lag fix since most folks recommended this prior to updating. Crossed my fingers and hoped my update would arrive soon.
Today my update arrived. It installed with no issues, after which my phone is still rooted. It did pause for several minutes at the Galaxy S screen, I was wondering if I had bricked it but I waited and it came through ok.
I'm not planning to reinstall the lag fix anytime soon as I don't notice that much of a change - except in the Quadant scores ;-)
d01100100 said:
Stock phone, rooted with no lagfix ever applied.
Phone is toast. I'm at work so waiting for Odin to download slowly so I can reflash the phone to stock.
Might just say skip it and apply one of the custom roms. It seems neither TMO or Samsung can get their **** together. I waited patiently for the OTA and got screwed.
Click to expand...
Click to collapse
That's what I ended up doing. I didn't want to potentially wait until the end of October so I just went ahead and flashed Bionix. I don't think I'm going back to stock ever.
atatistcheff said:
My phone had the OCLF v 2.1 plus root installed. Yesterday I removed the lag fix since most folks recommended this prior to updating. Crossed my fingers and hoped my update would arrive soon.
Today my update arrived. It installed with no issues, after which my phone is still rooted. It did pause for several minutes at the Galaxy S screen, I was wondering if I had bricked it but I waited and it came through ok.
I'm not planning to reinstall the lag fix anytime soon as I don't notice that much of a change - except in the Quadant scores ;-)
Click to expand...
Click to collapse
How many "minutes" did you wait? The notice before the update said it would take 10 minutes. I'm willing to wait, but not all night
The update portion with a status bar went my pretty quickly. My phone's been sitting on "Vibrant" for about 5 minutes and I'm starting to sweat.
I had been rooted and had OCLF but reversed both before applying the update. I also had the mobile AP, customized swype skin and custom battery meter but everything else was stock.
gancho said:
Not to be a downer but not necessarily. I was rooted with no lag fix (currently or prior) at all and it soft bricked my phone. I had the Samsung AP installed but that is about it, didn't remove bloatware or change the startup/shutdown sounds.
Got the phone running again with ODIN so I am back to stock now, without the update
Click to expand...
Click to collapse
i want to remove mobile AP just incase that is what is causing the soft bricks. ive noticed many people have problems have flashed the mobile ap. is there a way to remove with like uninstalling an application?
--without odin or flashing back to stock
I was rooted and removed some of the Samsung bloatware apps such as MediaHub etc...saw the update was available this morning and started it, phone was stuck on the Samsung Vibrant screen ever since. I put in for a replacement, could probably fix it with ODIN but new phone should be here tomorrow. I was actually having issues before that, so it could have been the phone itself...no way to be 100% sure.
For the people who had issues with their OTA, did you have a file named update.zip previously on the /sdcard directory? It's the only thing I can think of that might interfere with the OTA download, causing it to truncate. Phone is recovered and re-rooted, but the Update Firmware shows no update available. I'm going to Odin flash the 9-28 JI6 image.
That is what I am thinking as well. I have removed the update.zip from the internal storage now. The OTA is here and I postponed for a day just to be safe. I really need the GPS fix.
d01100100 said:
For the people who had issues with their OTA, did you have a file named update.zip previously on the /sdcard directory? It's the only thing I can think of that might interfere with the OTA download, causing it to truncate. Phone is recovered and re-rooted, but the Update Firmware shows no update available. I'm going to Odin flash the 9-28 JI6 image.
Click to expand...
Click to collapse
fine over here
My phone is rooted with RyanZA's one click lag fix and the update worked fine for me. I've never removed bloatware or anything though. Total I think it took about 8 minutes from start to finish.
I received the update this morning but my battery was below 10% and said I need more juice in order to install. I recharged and it kept saying the same thing after postponing a couple times. I restarted my phone and all works good now.
I'm noticing very good improvements in signal strength and flawless gps now. Maybe a speed increase also? I'm not sure about the speed thing just yet. Seems a bit snappier to me.
Lost Root
I updated to JI6 using odin based on the info in android development section, and I most definitely lost root.
Trying one click root/unroot to see if I can get root back
Nightfall983 said:
I updated to JI6 using odin based on the info in android development section, and I most definitely lost root.
Trying one click root/unroot to see if I can get root back
Click to expand...
Click to collapse
Using the recovery mode / update.zip (the classic root method) worked for me after Odin flashing JI6.
I'm having a problem with my wifi randomly turning itself off and customer care told me to just switch it out through the buyers remorse policy at a T-mobile store. I know you have to erase all signs of having rooted the phone before sending it to HTC under the limited warranty or else they charge you. Do I also have to set it back to stock before returning it directly to T-mobile through buyers remorse?
I'm asking because a) its a pain in the rear end to get it back to stock and b) I haven't found the stock recovery anywhere and have already flashed ClockworkMod Recovery so I'm not sure at this point I can get it back to stock.
Please post questions in Q&A section
Thanks for moving it.
Sent from my HTC Glacier using XDA App
I remember one time sending my Touch Pro 2 to T-Mobile for a new one with the HSPL on it. HSPL allows me to flash any custom ROM basically.
But I never got a call back or charged, but I only did that one time because I was being lazy.
Good question.
I have to return mine actually due to a hardware defect which I can't put up with like I thought I could but I also rooted my phone and turned S OFF but I turned the S ON the other day so I am hoping that will be enough lol. Well plus make sure none of the files I've d/l are on the sd card but I don't think I have to worry about that seeing as I'm not using the sd card that came with the phone but my own.
However, I think I might do this once I figure out if it's needed (cause I'm kind of nervous about doing it and messing it up you know) and after I do more research on this hex editor stuff. http://forum.xda-developers.com/showthread.php?t=832642
likeitnot said:
Good question.
I have to return mine actually due to a hardware defect which I can't put up with like I thought I could but I also rooted my phone and turned S OFF but I turned the S ON the other day so I am hoping that will be enough lol. Well plus make sure none of the files I've d/l are on the sd card but I don't think I have to worry about that seeing as I'm not using the sd card that came with the phone but my own.
However, I think I might do this once I figure out if it's needed (cause I'm kind of nervous about doing it and messing it up you know) and after I do more research on this hex editor stuff. http://forum.xda-developers.com/showthread.php?t=832642
Click to expand...
Click to collapse
Its very easy to do, it really is. I did it just today to switch out phones for another color. Just follow the directions carefully. They won't know because it literally puts stock right back on the phone. Just make sure that's what you want because there is no link for the 2.2.1 update right now. And people are having problems getting the updates again.
timbo1083 said:
Its very easy to do, it really is. I did it just today to switch out phones for another color. Just follow the directions carefully. They won't know because it literally puts stock right back on the phone. Just make sure that's what you want because there is no link for the 2.2.1 update right now. And people are having problems getting the updates again.
Click to expand...
Click to collapse
That's the easy part but how do you get the stock recovery back on? I haven't seen a download for it, don't think HTC has released it either.
Sent from my HTC Glacier using XDA App
If you are returning it to a store under buyer's remorse, then you don't need to unroot or do anything, as it is not a warranty exchange. You should be able to swap it out within a few minutes there, and never hear of it again.
When you follow the other post to downgrade it.puts the stock back on it. That is the point of it.
Sent from my HTC Glacier using Tapatalk
^^ I finally got it to work but I did notice that after a while superuser app and a few others I had downloaded are appearing again... uhhhhh
When I got into the terminal on the phone and type su + enter it says permission denied and another $ appears...am I safe to say its not rooted and it just put the apps back cause of the google backup?
Plus S is back to SON (it was SOFF cause of the root) & Titanium Pro will not let me upgrade the busybox always comes back with an error and then when I go back in the application it says "Error" Sorry I could not acquire root priveleges. This application will *not* work!..." Not to mention the application ShootMe no longer works cause it says I don't have root access.
OKAY *phew* I take it they only appeared again because of the google backup!
I had the exact same problem. My wifi and GSM signal would disappear. I would have to reboot the phone to get it back.
Anyway I took it back to tmo and they didn't even power it up or anything. I put everything back in like it was when I go it and no questions asked.
btmec said:
I had the exact same problem. My wifi and GSM signal would disappear. I would have to reboot the phone to get it back.
Anyway I took it back to tmo and they didn't even power it up or anything. I put everything back in like it was when I go it and no questions asked.
Click to expand...
Click to collapse
You bought your's from a Tmo store though right?
I ordered mine through add a line with 611..
I have dust under my sceen and am thinking about sending it back.
Odds are you all would be just fine, but honestly? Why take that chance...if you rooted it, you can unroot it. Just set it all back to stock and dont sign back in with the phone.
c_licious said:
I'm having a problem with my wifi randomly turning itself off and customer care told me to just switch it out through the buyers remorse policy at a T-mobile store. I know you have to erase all signs of having rooted the phone before sending it to HTC under the limited warranty or else they charge you. Do I also have to set it back to stock before returning it directly to T-mobile through buyers remorse?
I'm asking because a) its a pain in the rear end to get it back to stock and b) I haven't found the stock recovery anywhere and have already flashed ClockworkMod Recovery so I'm not sure at this point I can get it back to stock.
Click to expand...
Click to collapse
just flash the RUU from the downgrade post since you're already rooted and s-off you shouldn't need to do any of the hex editing or anything just download the RUU and put it in /sdcard/ named PD15IMG.zip and it will take care of it... and it will restore everything including recovery... the only thing that won't go back to normal is if you ran gfree for radio s-off... if you did that follow the guide in that post for restoring radio s-on then flash the RUU... http://forum.xda-developers.com/showthread.php?t=832642
slhpss said:
just flash the RUU from the downgrade post since you're already rooted and s-off you shouldn't need to do any of the hex editing or anything just download the RUU and put it in /sdcard/ named PD15IMG.zip and it will take care of it... and it will restore everything including recovery... the only thing that won't go back to normal is if you ran gfree for radio s-off... if you did that follow the guide in that post for restoring radio s-on then flash the RUU... http://forum.xda-developers.com/showthread.php?t=832642
Click to expand...
Click to collapse
Where can I get the RUU?
And the method I used was with Visionaryr11 and a download that had a script.
I just ran Visionary, used Terminal Emulator to access the script and then rebooted and I was perma rooted.
http://www.youtube.com/watch?v=eHrtVzlsA_s
nguyendqh said:
Where can I get the RUU?
And the method I used was with Visionaryr11 and a download that had a script.
I just ran Visionary, used Terminal Emulator to access the script and then rebooted and I was perma rooted.
http://www.youtube.com/watch?v=eHrtVzlsA_s
Click to expand...
Click to collapse
the download that the link I posted says to save as PD15IMG.zip on your sdcard and reboot in the boot loader is the RUU... it will put you back to stock 2.2 everything including recovery and bootloader
I accidentally deleted my part7 .bin created by gfree and could not get s=on. I exchange anyway at the tmo for a better screen. They didn't even pretend to check if it had been rooted.
Sent from my HTC Glacier using XDA App
exchanged my G1 which was rooted and had a version of android we werent supposed to have yet, I exchanged it through HTC though, my screen all out stopped working, maybe thats why they didn't notice anything, that or they just don't really care.
QUESTION - it seems that flashing PD15IMG.zip is the same process as flashing SAPPIMG.nbh for the original myTouch 3G.
1. Is the hexeditor stuff necessary or can we just copy to sdcard and flash away?
2. Can PD15IMG.zip be flashed from hboot S-OFF or do I need to turn S-ON first?
c_licious said:
That's the easy part but how do you get the stock recovery back on? I haven't seen a download for it, don't think HTC has released it either.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
The Unlockr
Has a stock ROM and a Stock Recovery Image that you can flash.
Apologies if this is a noob question. I didn't see any obvious answer to this, and I'm guessing I"m not the only one to question this.
I have a rooted stock 2.2, rooted with Unrevoked3. Now that there's a root exploit for GB, I'm trying to make sense of what I need to do to get the OTA installed.
Reading through the Unrevoked site, it looks like I need to find the appropriate .img first to restore me back to original? And Unrevoked's site directed me back here, but i didn't see where to find the correct file.
Second, I assume, and correct me if I'm wrong, that I simply copy the correct .img file back to my phone (which directory?) and boot up into recover to restore? At that point, i'll be able to get and update with the OTA?
-Brian
Why not flash a stock rooted GB ROM?
Sent from my PC36100 using XDA Premium App
That would certainly be the easiest solution, but i'd rather go OTA for a couple reasons:
1) while absolutely nothing against the great work the devs have done, I've gone back and forth on this and really end up wanting to keep mine stock (with a lot of sprint crap-ware frozen)
2) and a more direct reason for my question in the first place, this isn't just for my own phone, which i don't mind "hacking" with as much, but also for a coworker's phone I've rooted, the wife's (don't want to mess too much with hers) and even the in-law's two phones.
3) least required reason, I have very little actual use for Root, especially on the other listed phones, but the primary requirements on why i've rooted theirs is for wireless tethering and freezing of crapware.
1) while absolutely nothing against the great work the devs have done, I've gone back and forth on this and really end up wanting to keep mine stock (with a lot of sprint crap-ware frozen)
Click to expand...
Click to collapse
Umm, the stock rooted roms are exactly that: stock, but rooted. Everything is still there.
2) and a more direct reason for my question in the first place, this isn't just for my own phone, which i don't mind "hacking" with as much, but also for a coworker's phone I've rooted, the wife's (don't want to mess too much with hers) and even the in-law's two phones.
Click to expand...
Click to collapse
Again, flashing a stock rooted rom is NO different than taking the ota, except you will stay rooted and will not have to re-root.
3) least required reason, I have very little actual use for Root, especially on the other listed phones, but the primary requirements on why i've rooted theirs is for wireless tethering and freezing of crapware.
Click to expand...
Click to collapse
OK, well if you don't need root, then take the ota and you will be unrooted.
Ok, fair points. So which rom(s) would be the original stock roms with nothing but Root added?
They would be in the threads that say Stock ROMs
I accidentally deleted a few important documents led to the current system fails to boot, whenever I boot it always stays in the interface of a white background, and now I can get into odin mode but not in the recovery
My mail is [email protected]
chentongxin said:
I accidentally deleted a few important documents led to the current system fails to boot, whenever I boot it always stays in the interface of a white background, and now I can get into odin mode but not in the recovery
My mail is [email protected]
Click to expand...
Click to collapse
I might be wrong here as im not the sharpest tool in the shed, but i do believe there is a new post like this every single day and all get the same response. There is no MF3 image available for flash through odin or otherwise. Search = Friend.
If you repeat three times "owaa tagoo siam" it might magically appear.
Not happening my friend. Try going into download mode and then press down to cancel. It might boot normally then. (worked for me at one point with a similar issue)
agent929 said:
Not happening my friend. Try going into download mode and then press down to cancel. It might boot normally then. (worked for me at one point with a similar issue)
Click to expand...
Click to collapse
It seems useless
So did you try it or just say its useless? There are a couple other methods that have been shown to work as well.
Sent from my GT-I9505G using XDA Premium HD app
You are going to have to wait for Samsung to release the MF3 on kies or a leak of the tar to happen.
Sent from my GT-I9505G using Tapatalk 2
chentongxin said:
I accidentally deleted a few important documents led to the current system fails to boot, whenever I boot it always stays in the interface of a white background, and now I can get into odin mode but not in the recovery
My mail is [email protected]
Click to expand...
Click to collapse
hey buddy, im not familiar with Samsung restoring things cuz im an HTC person. but i was talking with a samsung rep and played dumb, i told him i did OTA and my phone died on me. now it booting up with emergency mode, and i told him i tried to hook it up to kies with emergency mode but no luck....
he gave me this like to remove custom OS ROM, i know its stupid but it kinda a different way to re-install the stock OS...
im sorry if being a NOOB here, cuz i said before im an HTC guy and love RUU ....
anyway if you already know that, then ignore it. otherwise try this link and let me know if this restore MF3 for you.
thanks
http://www.samsung.com/us/support/faq/FAQ00052690/61265/SGH-I337ZRAATT
salwansk said:
hey buddy, im not familiar with Samsung restoring things cuz im an HTC person. but i was talking with a samsung rep and played dumb, i told him i did OTA and my phone died on me. now it booting up with emergency mode, and i told him i tried to hook it up to kies with emergency mode but no luck....
he gave me this like to remove custom OS ROM, i know its stupid but it kinda a different way to re-install the stock OS...
im sorry if being a NOOB here, cuz i said before im an HTC guy and love RUU ....
anyway if you already know that, then ignore it. otherwise try this link and let me know if this restore MF3 for you.
thanks
http://www.samsung.com/us/support/faq/FAQ00052690/61265/SGH-I337ZRAATT
Click to expand...
Click to collapse
Its been stated 1000 times, this will not work with MF3 at this time. Using Kies to try and restore Firmware if you are on MF3 or using ODIN at best will not work and could possibly make things worse. There are a couple of exceptions using modified files (you can find them in the forum) but other than those exceptions absolutely KIES and ODIN will not help to restore Firmware if a phone is already on MF3.
scott14719 said:
Its been stated 1000 times, this will not work with MF3 at this time. Using Kies to try and restore Firmware if you are on MF3 or using ODIN at best will not work and could possibly make things worse. There are a couple of exceptions using modified files (you can find them in the forum) but other than those exceptions absolutely KIES and ODIN will not help to restore Firmware if a phone is already on MF3.
Click to expand...
Click to collapse
LOL... i think i might upset u right ? sorry bro...
i hope some one can modify the stock MF3 soon...
i had similar problem with Sprint note2 L900 4.1.2, it won't downgrade to 4.1.1 in order to get the SPC and flash it with different carrier. but one of the genius guys modify the stock 4.1.1 to let note2 accepted without error ....
its here
https://www.youtube.com/watch?v=f0d2B9lfouQ
salwansk said:
LOL... i think i might upset u right ? sorry bro...
i hope some one can modify the stock MF3 soon...
i had similar problem with Sprint note2 L900 4.1.2, it won't downgrade to 4.1.1 in order to get the SPC and flash it with different carrier. but one of the genius guys modify the stock 4.1.1 to let note2 accepted without error ....
its here
https://www.youtube.com/watch?v=f0d2B9lfouQ
Click to expand...
Click to collapse
No, definitely didn't upset me. My phone works and i know what I am doing. However, you probably would have upset the OP if he would have tried your suggestion and screwed his phone up worse. It would have been his own fault because there is always risk when it comes to doing anything to our phones, but being a bit more cautious when making suggestions to people would be a good thing also. Especially when there is already so much information about this in the AT&T S4 forums.
The video you linked to, once again, will do no good. ODIN will not work for restoring firmware on an MF3 phone at this time period.
scott14719 said:
No, definitely didn't upset me. My phone works and i know what I am doing. However, you probably would have upset the OP if he would have tried your suggestion and screwed his phone up worse. It would have been his own fault because there is always risk when it comes to doing anything to our phones, but being a bit more cautious when making suggestions to people would be a good thing also. Especially when there is already so much information about this in the AT&T S4 forums.
The video you linked to, once again, will do no good. ODIN will not work for restoring firmware on an MF3 phone at this time period.
Click to expand...
Click to collapse
i know ODIN will not work for restoring firmware on an MF3 phone at this time, but this link was just an example. maybe in the future someone can do something work with MF3....cuz at my work now we can't sim unlock or fix imei with this bulid MF3, i have tried octopus box, nspro, and setool3. non of them was able to sim unlock MF3, even the secret menu not exist in MF3....
i asked the riff jtag rep, if i can resurrection I337 MF3 and unlock the bootloader with riff box. he hasn't responded yet.
salwansk said:
i know ODIN will not work for restoring firmware on an MF3 phone at this time, but this link was just an example. maybe in the future someone can do something work with MF3....cuz at my work now we can't sim unlock or fix imei with this bulid MF3, i have tried octopus box, nspro, and setool3. non of them was able to sim unlock MF3, even the secret menu not exist in MF3....
i asked the riff jtag rep, if i can resurrection I337 MF3 and unlock the bootloader with riff box. he hasn't responded yet.
Click to expand...
Click to collapse
Many things have been tried with this already.
Look up a poster called "Aou". His posts will help shed light on the subject. Adam Outler also has worked a lot on the issue. The entire MF3 OTA was torn down and part by part tried. Once the MF3 bootloaders are applied, it simply can not be rolled back. There are software and hardware reasons for this, but it has all been tried. The result every time is Hard brick that JTAG can not fix at this time.
Once the full MF3 firmware has been released, maybe this will change, but it is doubtful. The MF3 bootloaders will still be the same. Without Samsung's signing key, the bootloader cannot be modified.
Once Samsung releases the full MF3 firmware (for ODIN and Kies) it will hopefully enable people to flash or restore back to a factory MF3 state, but we will still not be able to roll-back to AMDL. Maybe the full MF3 firmware release will include more files to work with...but again, it is doubtful.
As of now, the only way to sim unlock a phone on MF3 is to use a code (from AT&T or other). Hopefully someone will find a method that will work with MF3...but it hasn't happened yet.
You have good ideas about what should be done but it is important that you look and see what has already been tried and what is known at this point. Hopefully, people will still try to modify and work with MF3 (maybe something that hasn't been tried yet), but it will be building on what has been tried so far.
So, basically, at this time ODIN and KIES will not work with MF3, except for the modified files used without the bootloader. Neither will restore the phone to stock or can be used to roll back the firmware.
Hopefully, when Samsung releases the MF3 firmware, people will be able to restore their phones through ODIN and KIES, but will still be stuck on MF3.
In order to do any more, another work-around (such as the LOKI exploit) will need to be found or someone at Samsung is going to have to release or leak the encryption key.
That is pretty much all for now.
scott14719 said:
Many things have been tried with this already.
Look up a poster called "Aou". His posts will help shed light on the subject. Adam Outler also has worked a lot on the issue. The entire MF3 OTA was torn down and part by part tried. Once the MF3 bootloaders are applied, it simply can not be rolled back. There are software and hardware reasons for this, but it has all been tried. The result every time is Hard brick that JTAG can not fix at this time.
Once the full MF3 firmware has been released, maybe this will change, but it is doubtful. The MF3 bootloaders will still be the same. Without Samsung's signing key, the bootloader cannot be modified.
Once Samsung releases the full MF3 firmware (for ODIN and Kies) it will hopefully enable people to flash or restore back to a factory MF3 state, but we will still not be able to roll-back to AMDL. Maybe the full MF3 firmware release will include more files to work with...but again, it is doubtful.
As of now, the only way to sim unlock a phone on MF3 is to use a code (from AT&T or other). Hopefully someone will find a method that will work with MF3...but it hasn't happened yet.
You have good ideas about what should be done but it is important that you look and see what has already been tried and what is known at this point. Hopefully, people will still try to modify and work with MF3 (maybe something that hasn't been tried yet), but it will be building on what has been tried so far.
So, basically, at this time ODIN and KIES will not work with MF3, except for the modified files used without the bootloader. Neither will restore the phone to stock or can be used to roll back the firmware.
Hopefully, when Samsung releases the MF3 firmware, people will be able to restore their phones through ODIN and KIES, but will still be stuck on MF3.
In order to do any more, another work-around (such as the LOKI exploit) will need to be found or someone at Samsung is going to have to release or leak the encryption key.
That is pretty much all for now.
Click to expand...
Click to collapse
thanks bud, and yes i started read about this issue just today.
i know samsung is way easier than HTC when it comes to unlocking and flashing, thats why i didn't care at first. but what freaked me out when i tried to sim unlock galaxy s4 yesterday. today i found out about the MF3 and how is it pain in the axx :laugh: .... thanks for the info bro :good:
add myself to the thread for future fixes...
Scott that was probably the best explanation I have seen yet. You should have it pinned lol
Sent from my GT-I9505G using XDA Premium HD app
agent929 said:
Not happening my friend. Try going into download mode and then press down to cancel. It might boot normally then. (worked for me at one point with a similar issue)
Click to expand...
Click to collapse
Well Thank YOU ALOT.. you saved me TONS OF WORRIES. That trick got me out of a boot -> recovery -> odin mode loop. I thought I was going to have to confess to ATT and beg for them to fix my phone. I wont be touching my recovery again for a while. Not until a confirmed method and hugely tested recovery/custom rom method comes out.
Thank you! I knew that little bit of advice would help somebody one day.
Getting a replacement device today because mine will randomly drop 4G and revert to 3G in strong signal areas and will only come back when I put it in airplane mode and back out again. Swapped SIMs, reset to stock, even allowed the latest update with no change.
The replacement device arrives today. My phone before was rooted with Kingo, but I only used root for tethering and minor customization using Wanam, Nova, etc. No special ROMs or anything. In reading the forums it looks like accepting the KK update is NOT the way to go.
Looking at this thread http://forum.xda-developers.com/showthread.php?t=2727876, I think this is the route I want to take.Since I haven't done a whole lot since my OG Droid days besides point and click rooting solutions, if I mess something up do I always have the option of restoring my phone to stock using Kies like I did to revert to stock for my original phone's trip back to Verizon?
Thanks all.
I work for Verizon Wireless Tech Support, YOU NEED TO UNROOT AND FLASH STOCK EVERYTHING ON THE PHONE. Literally no joke, if our returns center detects even the HINT of root / non stock they WILL charge you $299 and it CAN NOT BE REVERSED, not by a supervisor, not by returning the phone, not by talking to samsung, nothing will have that removed. Just flash the phone completely stock, as for your new one that will depend on what OS it comes pre loaded with.
Xproplayer said:
I work for Verizon Wireless Tech Support, YOU NEED TO UNROOT AND FLASH STOCK EVERYTHING ON THE PHONE. Literally no joke, if our returns center detects even the HINT of root / non stock they WILL charge you $299 and it CAN NOT BE REVERSED, not by a supervisor, not by returning the phone, not by talking to samsung, nothing will have that removed. Just flash the phone completely stock, as for your new one that will depend on what OS it comes pre loaded with.
Click to expand...
Click to collapse
I did. Used Kies and restored my original phone to the stock image.
Can I always do this with this model phone? If I have a problem with rooting?
hawkeye680 said:
I did. Used Kies and restored my original phone to the stock image.
Can I always do this with this model phone? If I have a problem with rooting?
Click to expand...
Click to collapse
Do what? Root or unroot?
Xproplayer said:
Do what? Root or unroot?
Click to expand...
Click to collapse
Use Kies to restore to factory. Unrooted.
hawkeye680 said:
Use Kies to restore to factory. Unrooted.
Click to expand...
Click to collapse
Probably. If not, use odin.
<Note3>
LeftyGR said:
Probably. If not, use odin.
<Note3>
Click to expand...
Click to collapse
Kies actually uses Odin to restore the phone to stock. :good: