I need to send in my MDK S4 for screen repair to Samsung, and I'm worried about them flashing the update killing access to loki. Is there any way to to prevent flashing of ME7 / retain loki exploit post-flash, or am I doomed?
SellswordShev said:
I need to send in my MDK S4 for screen repair to Samsung, and I'm worried about them flashing the update killing access to loki. Is there any way to to prevent flashing of ME7 / retain loki exploit post-flash, or am I doomed?
Click to expand...
Click to collapse
Kinda screwed because you have to root it to do so they could check, see it was rooted and then deny warranty claims. I would call ahead and make sure they know you dont want it updated or include a note that states you dont want it updated.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
hexitnow said:
Kinda screwed because you have to root it to do so they could check, see it was rooted and then deny warranty claims. I would call ahead and make sure they know you dont want it updated or include a note that states you dont want it updated.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Click to expand...
Click to collapse
Its an out of warranty repair (cracked screen), so the rooting doesnt matter. I know OTA can be blocked via root, but doesnt prevent from them just flashing it via ODIN/Other firmware software. I was hoping there was some way to dupe the firmware updaters but couldnt find any from my search. I guess I just have to leave a note and hope they dont flash the update.
SellswordShev said:
Its an out of warranty repair (cracked screen), so the rooting doesnt matter. I know OTA can be blocked via root, but doesnt prevent from them just flashing it via ODIN/Other firmware software. I was hoping there was some way to dupe the firmware updaters but couldnt find any from my search. I guess I just have to leave a note and hope they dont flash the update.
Click to expand...
Click to collapse
A kind note is probably your best way to not have them update, because if they wanted to I'm sure there's nothing you could do to block it... but my question is why would they need to update your device if they're just replacing the screen? Seems like that would just be a waste of their time
Crawshayi said:
A kind note is probably your best way to not have them update, because if they wanted to I'm sure there's nothing you could do to block it... but my question is why would they need to update your device if they're just replacing the screen? Seems like that would just be a waste of their time
Click to expand...
Click to collapse
When my brother sent his HP computer into repair for a broken fan they reimaged it for no reason...
Related
I hear conflicting views in the threads:
Some say that the phone should be on stock JI6 for the supposed Froyo OTA update to kick in, some say it is not required.
I am confused - who is right?
If you want OTA then yes you need to be back on stock.
The others are probably telling you to not bother because you are most likely better off on the build you already have
guruchimi said:
I hear conflicting views in the threads:
Some say that the phone should be on stock JI6 for the supposed Froyo OTA update to kick in, some say it is not required.
I am confused - who is right?
Click to expand...
Click to collapse
If you want to get the update, yes you should go back to stock. There is always the potential of the update bricking your phone. Or maybe not, but do you want to take the chance
Will someone have a flashable ready lol... Im more scared of ota then flashing
I think I will stick to KA5. The last JI6 OTA update bricked my phone.
cjggilbert said:
If you want to get the update, yes you should go back to stock. There is always the potential of the update bricking your phone. Or maybe not, but do you want to take the chance
Click to expand...
Click to collapse
Why would the update brick his phone, I mean sure updates can do that if something goes wrong, but are you suggesting because he has installed custom roms in the past, this puts him at a greater risk for bricking a phone via OTA?
SamsungVibrant said:
Why would the update brick his phone, I mean sure updates can do that if something goes wrong, but are you suggesting because he has installed custom roms in the past, this puts him at a greater risk for bricking a phone via OTA?
Click to expand...
Click to collapse
actually it does.
A LOT of people including me were bricked with the last update JL6 or something.
Flashing is easier because you can see whats happening, and its pretty easy as well...
OTA, it comes through the air, which is... hard espically if you live in a low signal area you ota can get interrupted and then just stop.
So I got careless while prepping my phone for warranty return, unrooted and wiped, and then discovered that the su binary was baked into the ROM. I'd re-root the phone, but the problem is, the reason I'm returning it is the USB port is screwed up. I can't get a reliable connection with a computer to root. Is there a way to root wirelessly, or via download?
EDIT: I'm still running 2.3.4 (UCKH7)...could I just do an OTA update? That would basically flash new firmware on the phone, right?
Check 3A in this thread, or check out this thread. Mobile Odin should be able to do what you want to do.
Red5 said:
Check 3A in this thread, or check out this thread. Mobile Odin should be able to do what you want to do.
Click to expand...
Click to collapse
So I kinda feel like an idiot...I didn't actually think the Superuser app was still usable (I assumed my previous kernel flash somehow wiped root...not sure what I was thinking), so I didn't try Mobile Odin. After your suggestion, I went ahead and tried it...and it prompted for authorization. If the app is there, it should work...duh.
I was able to do a full update via Mobile Odin, which appears to have flashed a completely stock kernel, rom, etc. I then did a factory reset. Everything appears to be stock. Thanks!
nd_geek said:
So I got careless while prepping my phone for warranty return, unrooted and wiped, and then discovered that the su binary was baked into the ROM. I'd re-root the phone, but the problem is, the reason I'm returning it is the USB port is screwed up. I can't get a reliable connection with a computer to root. Is there a way to root wirelessly, or via download?
EDIT: I'm still running 2.3.4 (UCKH7)...could I just do an OTA update? That would basically flash new firmware on the phone, right?
Click to expand...
Click to collapse
I can't thinik of any way to root the phone without usb. Mobile Odin requires the phone already be rooted.
I believe the OTA update in incremental, so I don't think it will touch the su binary.
Are you sending it back to Samsung, or taking it to AT&T? What is the chance that anyone is going to look in the file system? Probably non existant with AT&T. Don't know with Samsung.
creepyncrawly: looks like I posted after you started to but before you finished...you're probably right on AT&T not noticing, but they already almost wouldn't take a warranty exchange via the phone support due to the USB port issue (they wanted to call it "physical damage"), so I figured I'd better do everything I could to make it look stock.
nd_geek said:
So I kinda feel like an idiot...
Click to expand...
Click to collapse
You should. Everything you've posted today could have been dealt with in 1 thread instead of 3.
I apologize in advance if I waste anyones time with this, Im not even sure how I would look it up.
My knowledge on this subject is very limited but im wondering if this idea holds water at all. Could anything be done along the lines of faking an ota update? Why could someone not break open an ota update, say an older version that is rootable, change what ever would be needed to make the tablet think its a newer version than whats installed. Then using like on my linux box changing the hosts file so that when the tablet goes what it thinks is "out" to check for updates, it gets sent to a local computer and finds the modified update, boom I get back to a rootable version. I know its probably not that simple I was just hoping to learn.
Thanks a bunch for your time.
Sean
gundark2 said:
I apologize in advance if I waste anyones time with this, Im not even sure how I would look it up.
My knowledge on this subject is very limited but im wondering if this idea holds water at all. Could anything be done along the lines of faking an ota update? Why could someone not break open an ota update, say an older version that is rootable, change what ever would be needed to make the tablet think its a newer version than whats installed. Then using like on my linux box changing the hosts file so that when the tablet goes what it thinks is "out" to check for updates, it gets sent to a local computer and finds the modified update, boom I get back to a rootable version. I know its probably not that simple I was just hoping to learn.
Thanks a bunch for your time.
Sean
Click to expand...
Click to collapse
Nice thinking but SONY has screwed us on this. We can decrypt the OTA zip files but can not fully sign them with SONY's special key. The only way to do anything is with root. I.e. lower incremental and get an ota. Or install a modified OTA using a temp recovery with disabled signature check. Pretty much if you get root then don't accept any OTA's. I have had root with HC and had to wait for ICS exploit, then sat on R5 (still rootable) and then pre-rooted to R5A. Tablet then got messed up and Sony repaired but was stuck on R5A no root. We will have to wait once again and hope we get JB and hope it has an exploit.
Stifilz
Ive had the 16gb Tablet S since xmas 2011. Ive never really had a reason to root it. I have rooted numerous phones and tablets for the wife and friends. I now would like to root but I am currently on FW R5A. Is there anything I can do to root it? Ive looked through some of Condis AiO tool thread, but with a 1yr old, its kinda hard to look through the entire thread. Would I have to use a prerooted R5A in AiO tool or am I just SOL right now? Thanks for any help:good:
you have 2 ways
*wait r5a tobe root,this may take looong time
*ask the sony service flash back to old FW,need much lucky
<robin> said:
you have 2 ways
*wait r5a tobe root,this may take looong time
*ask the sony service flash back to old FW,need much lucky
Click to expand...
Click to collapse
Would a factory reset go back to old FW?
VoltronMaximus said:
Would a factory reset go back to old FW?
Click to expand...
Click to collapse
No. Just lose data
Sent from my WT19i using xda app-developers app
hi,
just got my GS4 today and, very stupidly, agreed to let the phone update to the new firmware via verizon's OTA update to VRUDMI1. realizing i had already made a mistake, i used ODIN to try and flash it back to the stock firmware, which failed. i tried a couple packages for the stock VZ image, but both have failed. also, apparently the VZ GS4 does not give you a serial number, so Samsung's KIES is not an option, unless i am mistaken. i tried downloading that and using my IMEI as the serial but it says the serial is incorrect.
am i completely screwed? or maybe just for the time being until a new image for flashing back to stock from the new firmware is released? the phone boots into ODIN but gives the message that there was an error while updating the firmware, and to try the software repair assistant. based on what i've been reading, it seems that this is sometimes fixable, but perhaps it is just too early for this firmware at this point? ugh.
long shot: the phone was not rooted at the time, locked bootloader, running the fully stock VZ image and new firmware -- perhaps they would provide assistance? i wouldn't hold my breath though!
androidy_guy said:
hi,
just got my GS4 today and, very stupidly, agreed to let the phone update to the new firmware via verizon's OTA update to VRUDMI1. realizing i had already made a mistake, i used ODIN to try and flash it back to the stock firmware, which failed. i tried a couple packages for the stock VZ image, but both have failed. also, apparently the VZ GS4 does not give you a serial number, so Samsung's KIES is not an option, unless i am mistaken. i tried downloading that and using my IMEI as the serial but it says the serial is incorrect.
am i completely screwed? or maybe just for the time being until a new image for flashing back to stock from the new firmware is released? the phone boots into ODIN but gives the message that there was an error while updating the firmware, and to try the software repair assistant. based on what i've been reading, it seems that this is sometimes fixable, but perhaps it is just too early for this firmware at this point? ugh.
long shot: the phone was not rooted at the time, locked bootloader, running the fully stock VZ image and new firmware -- perhaps they would provide assistance? i wouldn't hold my breath though!
Click to expand...
Click to collapse
Yeah once you go to ME7 or MI1, there is no going back. You can only stay where you are, or go forward. You'll need to use Odin again and this time flash the MI1 file.
Which can be found here thanks to Surge1223
http://forum.xda-developers.com/showthread.php?t=2484726
spc_hicks09 said:
Yeah once you go to ME7 or MI1, there is no going back. You can only stay where you are, or go forward. You'll need to use Odin again and this time flash the MI1 file.
Which can be found here thanks to Surge1223
http://forum.xda-developers.com/showthread.php?t=2484726
Click to expand...
Click to collapse
Chances are it will also flip the knox warranty to void because knox status/warranty is now included in the new firmware.
tech_head said:
Chances are it will also flip the knox warranty to void because knox status/warranty is now included in the new firmware.
Click to expand...
Click to collapse
hmm, interesting. perhaps i should try my luck with VZ first? i guess it can't do any harm. currently when it turns on it shows knox status 0x0, which is apparently good. perhaps VZ can flash it somehow? i have no idea what kind of support they provide for this kind of thing.
edit: also it seems this KNOX is mainly relevant for creating a secure zone for corporate applications? i am not using it in that setting. perhaps it would just reduce the resale value somewhat? or is there something i'm not understanding about it.
That flag if set will have Samsung trying to deny any warranty.
They are not going to flash it for you.
Not advocating fraud or anything., but you have only had it one day.......
Sent from my SCH-I545 using Tapatalk
tech_head said:
That flag if set will have Samsung trying to deny any warranty.
They are not going to flash it for you.
Not advocating fraud or anything., but you have only had it one day.......
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
yea, i figured as much. it does say "system status: custom" though - maybe that alone will screw me? not sure how VZ will see that. if they refuse is it worth contacting samsung directly?
also, bought the phone used from a friend, so that prob eliminates any hope from VZ to begin with.
Flash the Odin posted in post 2. Then you can root and use safestrap the same as it being on me7 like it was.
androidy_guy said:
yea, i figured as much. it does say "system status: custom" though - maybe that alone will screw me? not sure how VZ will see that. if they refuse is it worth contacting samsung directly?
also, bought the phone used from a friend, so that prob eliminates any hope from VZ to begin with.
Click to expand...
Click to collapse
Okay, bought from friend not Verizon.
So back to ODIN it is.
You just need the latest firmware to flash. You can't use ME7 but you can use the latest one.
The file is in this thread -> http://forum.xda-developers.com/showthread.php?t=2484726 like one of the previous people posted.
You already know how to use ODIN and this should work. Just remember PDA mode.
Once you flash Me7 there was no going back and MI1 is the same. No going backward.
You should be fine if you can get into download.
^^^^^^^^^ what he said
tech_head said:
Okay, bought from friend not Verizon.
So back to ODIN it is.
You just need the latest firmware to flash. You can't use ME7 but you can use the latest one.
The file is in this thread -> http://forum.xda-developers.com/showthread.php?t=2484726 like one of the previous people posted.
You already know how to use ODIN and this should work. Just remember PDA mode.
Once you flash Me7 there was no going back and MI1 is the same. No going backward.
You should be fine if you can get into download.
Click to expand...
Click to collapse
will do - downloading the package now. should be able to fool around with it after work today. i feel like a real idiot for rushing into this without knowing enough about the OTA firmware that i ignorantly accepted.
at this point i don't really care if the KNOX is triggered or whatever - i always purchase my devices out of warranty and activate them so i can keep my grandfathered unlimited. it's the risk i run for wanting stock android on verizon with unlimited data
ooooook, the package in that thread worked. thanks a lot guys! i was really kicking myself all day over this one, and really had only myself to blame. my only questions now are:
how can i check my KNOX status?
is it likely that there will be a root/CM version for this phone, post UMI1?
Reboot into download and read the tiny text with a magnifying glass
Sent from my SCH-I545 using Tapatalk
Im glad the odin image worked...pulling that thing was kinda difficult lol.
ok i booted into ODIN again and KNOX comes up 0x0, so it looks like i came out unscathed all around. too bad i inadvertently locked my phone down with this update. i got the GS4 so i could upgrade from my GN, in hopes of flashing the latest CM10 on a phone with some nicer hardware.
So my VWZ S4 crapped out on me. About 2 weeks ago, the USB port died completely. I bought some replacement batteries and and external charger and figured I would just swap out the battery every day. Last week, the microphone seemed to go too. On every call, my voice sounded "tinny" and robotic. I brought it to a Verizon store and the rep offered to send me a warranty replacement (I only had 3 days left before the 1 year warranty expired!).
The problem I have is that I had the MDK bootloader unlocked and had a custom ROM install. When I get the replacement phone in a few days, I will have to send my old one back to Verizon. The guy at the store told me I had to unroot and get the phone back to stock, otherwise Verizon charges a $300 penalty (ouch!).
My main problem it that I don't have USB access. It's completely dead. I was wondering if these steps would work:
(I'm currently running Vanir ROM and latest CWM)
1.) Flash TW 4.4.2 Stock Verizon I545VRUFNC5 (found here http://forum.xda-developers.com/showthread.php?t=2721118)
2.) Download/run Triangle Away to reset the Flash Counter.
3.) Use the SuperSU settings to "Full Unroot"
4.) OTA update that will lock bootloader???? (I think this is where I am screwed)
Any other thoughts or suggestions?
to me that sounds legit on how it should be done. or even doing the Kies way of update after you put stock (any bl version) or buy a usb charging port and microphone and fix the phone. couple bucks on ebay or amazon n an easy fix
FordNate, I wish I had the technical skills to replace both. Unfortunately, I do not!
I wonder if this method will be good enough for Verizon. I don't know that this will re-lock the bootloader if I do the steps above?
double zero said:
FordNate, I wish I had the technical skills to replace both. Unfortunately, I do not!
I wonder if this method will be good enough for Verizon. I don't know that this will re-lock the bootloader if I do the steps above?
Click to expand...
Click to collapse
It should, since the bootloader was never unlocked anyway. Loki was a convenient workaround.
wtherrell said:
It should, since the bootloader was never unlocked anyway. Loki was a convenient workaround.
Click to expand...
Click to collapse
Thanks. Sounds good. Do you know for a fact that there will be an OTA update to take if I flash the TW 4.4.2 Stock Verizon I545VRUFNC5. Should I flash something else instead?
double zero said:
Thanks. Sounds good. Do you know for a fact that there will be an OTA update to take if I flash the TW 4.4.2 Stock Verizon I545VRUFNC5. Should I flash something else instead?
Click to expand...
Click to collapse
Idk.
wtherrell said:
Idk.
Click to expand...
Click to collapse
Me neither. I'm not sure what the final step should be. However, I feel like if I flash a stock ROM and unroot, I should be good enough for Verizon.
I don't know if they ever turn them on once they get them.
I recently sent a Galaxy S3 in with full root and the "Custom" text on the screen for replacement.
The only email I ever got was that the phone had been received. YMMV.
tech_head said:
I don't know if they ever turn them on once they get them.
I recently sent a Galaxy S3 in with full root and the "Custom" text on the screen for replacement.
The only email I ever got was that the phone had been received. YMMV.
Click to expand...
Click to collapse
Interesting. When I was at the Verizon store, the guy at the customer service area told me to return it to stock, because they would definitely check to see if the software was modified. That's why I'm worried about trying to return to stock (or as close to possible) before sending it in.
It seems like if I do the steps I suggested above, it would "appear" to be stock, but it would still have CWM installed. Maybe that will be good enough? I don't think I have any other choice.
@Surge1223 Unique situation I think I remember you having a solution for awhile back. Any advice on this OP?
double zero said:
Interesting. When I was at the Verizon store, the guy at the customer service area told me to return it to stock, because they would definitely check to see if the software was modified. That's why I'm worried about trying to return to stock (or as close to possible) before sending it in.
It seems like if I do the steps I suggested above, it would "appear" to be stock, but it would still have CWM installed. Maybe that will be good enough? I don't think I have any other choice.
Click to expand...
Click to collapse
Easiest method would be to find an me7 ota zip and stock mdk recovery.img and boot.img, if you have a stock mdk back up. Otherwise id suggest going to mk2 instead of nc5 that way you would get an ota notification...although I think flashing a stock rom, recovery and kernel then using supersus full unroot method should do the trick.
Surge1223 said:
Easiest method would be to find an me7 ota zip and stock mdk recovery.img and boot.img, if you have a stock mdk back up. Otherwise id suggest going to mk2 instead of nc5 that way you would get an ota notification...although I think flashing a stock rom, recovery and kernel then using supersus full unroot method should do the trick.
Click to expand...
Click to collapse
Surge, I don't have a stock mdk back up, unfortunately. I went through the forums and found this MK2 Rom (http://forum.xda-developers.com/showthread.php?t=2581072). Do you think that would work?
1.) Flash the http://forum.xda-developers.com/showthread.php?t=2581072 ROM
2.) Download/run Triangle Away
3.) SuperSU (Full Unroot)
4.) OTA update to NC5 (lock bootloader)?