If I flash my phone using odin and screw up. Will tmobile replace it? I want to flash the hardware locked fix for my phone because I can't get it to download mode without using adb. But what if my phone gets bricked by that fix, the only solution is to replace the phone right?
iynfynity said:
If I flash my phone using odin and screw up. Will tmobile replace it? I want to flash the hardware locked fix for my phone because I can't get it to download mode without using adb. But what if my phone gets bricked by that fix, the only solution is to replace the phone right?
Click to expand...
Click to collapse
If you brick your phone with Odin it does void the warrantee. We all like to mod our phones but if we mess it up it is our fault. Besides these phones are really hard to brick. My opinion to you is if you dont feel comfortable doing something you may not want to do it. My opinion is if you brick your phone you are s#@^ out of luck as far as returning it. This forum is really good at helping though. Im sure if you do brick it someone can help you
iynfynity said:
If I flash my phone using odin and screw up. Will tmobile replace it? I want to flash the hardware locked fix for my phone because I can't get it to download mode without using adb. But what if my phone gets bricked by that fix, the only solution is to replace the phone right?
Click to expand...
Click to collapse
saying things like that will just get people yelling at you.
if you need help with fixing it i can do my best to help you but i need to know what state your phone is in.
does the phone turn on?
when you turn it on what does it do?
does it hang at the vibrant screen but still make the start up noise?
Will they replace it? Yeah probably. Are they liable to replace it? No. However if the phone is bricked sending it in for a replacement is not as bad as people may want you to think.
When someone sends in a phone for replacement,
T-Mobile sends it to Samsung who then send out a used replacement. The only costs incurred to either party are shipping and labor costs which are minute compared to the goodwill they just built with a customer. Neither Tmo or Samsung are out of a phone because they simply fix your bricked phone and send it as a replacement to someone else.
ipeench said:
saying things like that will just get people yelling at you.
if you need help with fixing it i can do my best to help you but i need to know what state your phone is in.
does the phone turn on?
when you turn it on what does it do?
does it hang at the vibrant screen but still make the start up noise?
Click to expand...
Click to collapse
I still haven't done anything to my phone because I'm really scared I might brick it. my phone is a hardware locked, so what I really want to do is flash the fix for the hardware locked phones. But what If it bricks my phone? Then there's no way i could go to download mode because I can't use adb anymore. What will I do if that possibility happen?
geocepe said:
If you brick your phone with Odin it does void the warrantee. We all like to mod our phones but if we mess it up it is our fault. Besides these phones are really hard to brick. My opinion to you is if you dont feel comfortable doing something you may not want to do it. My opinion is if you brick your phone you are s#@^ out of luck as far as returning it. This forum is really good at helping though. Im sure if you do brick it someone can help you
Click to expand...
Click to collapse
Yes I'm not comfortable in flashing my phone, that's why I haven't done the update yet. But I really want the update that's why I'm asking if I can get a new phone. If only my phone is not a hardware locked I already flashed the JI6
iynfynity said:
Yes I'm not comfortable in flashing my phone, that's why I haven't done the update yet. But I really want the update that's why I'm asking if I can get a new phone. If only my phone is not a hardware locked I already flashed the JI6
Click to expand...
Click to collapse
What have you done to your phone so far? Root? Flash a rom? anything?
geocepe said:
What have you done to your phone so far? Root? Flash a rom? anything?
Click to expand...
Click to collapse
none. all stock. I'm really afraid because there's a possibility that flashing the hardware fix might brick my phone.
if a phone gets bricked, can i still use the adb? That's the only way I can go to download mode.
iynfynity said:
none. all stock. I'm really afraid because there's a possibility that flashing the hardware fix might brick my phone.
if a phone gets bricked, can i still use the adb? That's the only way I can go to download mode.
Click to expand...
Click to collapse
I have heard that some people after the OTA are no longer hardware locked. I cannot confirm or deny this as mine is not locked. I myself am not comfortable with Odin so I wont do anything with it. I have heard to many people bricking phones using it. There are some other links in the forums on how to get into download mode on a locked phone. If I were you I would try those ways first to see if you can get into download mode before trying the upgrade.
geocepe said:
I have heard that some people after the OTA are no longer hardware locked. I cannot confirm or deny this as mine is not locked. I myself am not comfortable with Odin so I wont do anything with it. I have heard to many people bricking phones using it. There are some other links in the forums on how to get into download mode on a locked phone. If I were you I would try those ways first to see if you can get into download mode before trying the upgrade.
Click to expand...
Click to collapse
I really have tried going to download mode and the only way that works for me is by adb. anyway, thanks for the reply. I'll just give up and will not update. I really don't want to risk my phone.
I dont blame you.
I did the bootloader fix on my hardware locked phone (wife's). I figured this OTA may brick it and Im screwed, but the next update, and the next may also brick it.
Figure 2.2 is somewhere down the road. That may brick it too.
Thats why I took the chance on flashed the fix. Just my .02
Moped_Ryder said:
I dont blame you.
I did the bootloader fix on my hardware locked phone (wife's). I figured this OTA may brick it and Im screwed, but the next update, and the next may also brick it.
Figure 2.2 is somewhere down the road. That may brick it too.
Thats why I took the chance on flashed the fix. Just my .02
Click to expand...
Click to collapse
Good for you, so your locked phone is now working great?
And yeah I've thought of that one, the froyo. What if that one comes and it needs a JI6 ROM. if that happens i'll contact t-mobile.
Yeap HW locked phone good to go now.
I did the "test" file first. That worked fine through odin, so I went back into download mode via adb and flashed the fix.
Moped_Ryder said:
Yeap HW locked phone good to go now.
I did the "test" file first. That worked fine through odin, so I went back into download mode via adb and flashed the fix.
Click to expand...
Click to collapse
What test file? I didn't see that one.
Related
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.
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.
Hello guys,please make sure you activate OEM UNLOCK in the developer options before you root your Android device with FRP installed. otherwise you risk to get into a bootloop after trying to boot into recovery due to FRP blocks custom binaries
have u tried using kies and using tools/firmware upgrade and putting your model number in and flashing with stock ? have you tried using odin and doin the same ?
jo01 said:
have u tried using kies and using tools/firmware upgrade and putting your model number in and flashing with stock ? have you tried using odin and doin the same ?
Click to expand...
Click to collapse
I am downloading the stock ROM now it takes a while. But how the hell can google tell me what i have to install and wehat not when i paid the phone? I am so pissed, its unbelievable. **** google and **** Samsung for letting this assholes do this.
Ok KIES does not even recognize my phone. The mworse is, it would start if it would not try to start into recovery. is there any option to remove the "recovery bit" or something like that and make the phone start normal and not into the recovery? That is my problem.
k now it is definately bricked, after i triedto flash a stock rom it says an error ocurred while recovery an i shall use smart switch but smart switch says unsupported device, i can not believe thishappened because of a google feature which no one asked for and they brick a device i bought for 800 bucks
OK FIXED, i had to flash via ODIN the Origin ROM, in my case the phone came from Italy and the Provider was TIM, it took me 7 Euro to download at Sammobile full speed and got it in 5 minutes.
Can be closed
I am in the same situation. I tried using the Recovery method with smart switcher or ODIN to flash the stock firmware but I am still stuck in a boot loop. I cannot access recovery at all and cannot install as the lock protection is on. Any other suggestions? I wasn't trying to root my phone it just decided to shut off and not boot up again.
this is quite concerning as i purchased my phone from Amazon Italy as it was cheaper than anywhere else but i was unable to root despite following the steps but i discovered it was because of the FRP, but i don't want a situation like this to happen, any more tips would be good, preferably without having to spend money from sam mobile too.
Brunkhorse said:
I am in the same situation. I tried using the Recovery method with smart switcher or ODIN to flash the stock firmware but I am still stuck in a boot loop. I cannot access recovery at all and cannot install as the lock protection is on. Any other suggestions? I wasn't trying to root my phone it just decided to shut off and not boot up again.
Click to expand...
Click to collapse
Im having the same problem. I can only access the download menu on the phone and all of my many attempts to flash or recover it failing with the phone saying "custom binary (recovery) blocked by FRP lock". I only know a limited amount about the rooting scene but if anyone could post a rom or something that would fix this or a method to remove the lock even with the smallest chance of success I definitately would give it a try(maybe a step by step as well please ) . Again there is no way i can see how to access anything on the device. My phone is the SM-G928W8 from Canada with Telus. Anything is worth a shot so if you have any ideas id love to hear them, thank you everyone :fingers-crossed:
ibstickboy said:
Im having the same problem. I can only access the download menu on the phone and all of my many attempts to flash or recover it failing with the phone saying "custom binary (recovery) blocked by FRP lock". I only know a limited amount about the rooting scene but if anyone could post a rom or something that would fix this or a method to remove the lock even with the smallest chance of success I definitately would give it a try(maybe a step by step as well please ) . Again there is no way i can see how to access anything on the device. My phone is the SM-G928W8 from Canada with Telus. Anything is worth a shot so if you have any ideas id love to hear them, thank you everyone :fingers-crossed:
Click to expand...
Click to collapse
YOu need to find a stock ROM, this will be the hardest part. AFter you have it, flash via ODin and the problem will be solved, i had the same problem. But you have to hurry because FRP also locks the charging of the battery so once you run out of battery you need to bring it to a technician.
jonny68 said:
this is quite concerning as i purchased my phone from Amazon Italy as it was cheaper than anywhere else but i was unable to root despite following the steps but i discovered it was because of the FRP, but i don't want a situation like this to happen, any more tips would be good, preferably without having to spend money from sam mobile too.
Click to expand...
Click to collapse
I spent the money because i needed it quick, if you download a stock ROM and have it left you can go ahead. YOu can download at SLOW MODE for free at sam
Brunkhorse said:
I am in the same situation. I tried using the Recovery method with smart switcher or ODIN to flash the stock firmware but I am still stuck in a boot loop. I cannot access recovery at all and cannot install as the lock protection is on. Any other suggestions? I wasn't trying to root my phone it just decided to shut off and not boot up again.
Click to expand...
Click to collapse
Check if you have the right stock ROm, it needs to be exactly the same country and provider. There is unfortunally no other way to remove FRP but booting the phone and remove the google account
can be deleted, i thought it works like on other subforums that new posting willl be added
please delete
Is it true that the battery doesn't charge after it's FRP locked? So the missing W8 firmware even if it comes eventually when the battery is dead the phone is dead? How in the hell are we supposed to fix this with no firmware available on sammobile?! Is there really no other way? Who has the firmware? Do the carriers have it?
thismonk said:
Is it true that the battery doesn't charge after it's FRP locked? So the missing W8 firmware even if it comes eventually when the battery is dead the phone is dead? How in the hell are we supposed to fix this with no firmware available on sammobile?! Is there really no other way? Who has the firmware? Do the carriers have it?
Click to expand...
Click to collapse
The battery is not locked (as far as I can tell), my phone got the lock when it was fully dead and while I was charging it and it seemed to have a charged battery after I unplugged from charging for awhile but there was no actual way to check. As for the firmware you will just have to wait for it my friend, that is the same firmware I needed and as of just now they still don't have it available on sammobile. Sorry man and best of luck
Needed? Did you end up getting the phone fixed by someone or send it back in to Samsung?
No I didn't get it fixed I sent it back to the phone company and paid a small fee rather than waiting for the firmware to be released.
Who was your phone company? I'm wondering because I can't seem to find anyone to help. I even contacted the local Samsung service center who deals with Telus and they told me that they could replace the mainboard but woudlnt flash the firmware or otherwise fix it. So that was rather useless I'm essentially buying a new phone.
thismonk said:
Is it true that the battery doesn't charge after it's FRP locked? So the missing W8 firmware even if it comes eventually when the battery is dead the phone is dead? How in the hell are we supposed to fix this with no firmware available on sammobile?! Is there really no other way? Who has the firmware? Do the carriers have it?
Click to expand...
Click to collapse
Absolutely right, if the battery runs out, you are lost. Then you have to bring it to the Samsung Service, they will fix it for you, if you pay of course..because KNOX will be void. The only way to avoid this is to remove your google account from the phone or enable under Developer Settings the OEM UNLOCK. Then FRP is disabled. But if you forgot and are now in a bootloop you have a real problem because as i have seen the W8 Firmware is not available on sammobile.
deepphrozen said:
Absolutely right, if the battery runs out, you are lost. Then you have to bring it to the Samsung Service, they will fix it for you, if you pay of course..because KNOX will be void. The only way to avoid this is to remove your google account from the phone or enable under Developer Settings the OEM UNLOCK. Then FRP is disabled. But if you forgot and are now in a bootloop you have a real problem because as i have seen the W8 Firmware is not available on sammobile.
Click to expand...
Click to collapse
My battery ran out but the phone is actually still working. When I plug it in via USB it powers up. It doesnt' actually charge the battery, but this will work for Odin. Now I just need to find someone to dump the stock firmware for me...
Any updates on a firmware?
If you need to go to stock then have you tried to boot I to download mode and use smartswitch reinstall feature?
thismonk said:
My battery ran out but the phone is actually still working. When I plug it in via USB it powers up. It doesnt' actually charge the battery, but this will work for Odin. Now I just need to find someone to dump the stock firmware for me...
Click to expand...
Click to collapse
I have same Problem as all of you but haven't fixed it yet because I still haven't found right ROM but if you have wireless charger it will force charge!! ??
This morning my phone notified me that there was an update available. I ran the update, and now my phone is pretty much completely unusable. If I try to make a call the phone app closes. If I try to text the messaging app closes. The phone also reboots every few minutes on its own.
I did the samsung support chat, they had me put the phone in safemode which didn't help at all. They suggested I do a factory reset, but I haven't been able to backup my phone without it restarting.
I'm skeptical the factory reset would help, anyway.
I'm thinking about just taking it into the verizon store and having them replace it (it's still under warranty), but I'm wondering if I could get an upgrade for the inconvenience.
Any ideas? Thoughts?
Thanks!
JMBush1007 said:
This morning my phone notified me that there was an update available. I ran the update, and now my phone is pretty much completely unusable. If I try to make a call the phone app closes. If I try to text the messaging app closes. The phone also reboots every few minutes on its own.
I did the samsung support chat, they had me put the phone in safemode which didn't help at all. They suggested I do a factory reset, but I haven't been able to backup my phone without it restarting.
I'm skeptical the factory reset would help, anyway.
I'm thinking about just taking it into the verizon store and having them replace it (it's still under warranty), but I'm wondering if I could get an upgrade for the inconvenience.
Any ideas? Thoughts?
Thanks!
Click to expand...
Click to collapse
I would Odin using home_csc to avoid wiping all data and either use qc5 or qa4 depending on which is available. Doubtful they'd offer an upgrade over a replacement
gunz.jones said:
I would Odin using home_csc to avoid wiping all data and either use qc5 or qa4 depending on which is available. Doubtful they'd offer an upgrade over a replacement
Click to expand...
Click to collapse
Okay, thanks. I did some rooting and ROMing back when I had a rezound, but haven't done anything of the sort on my S7. This method won't void my warranty, will it?
I know it's probably wishful thinking for the upgrade, but dang. Having to go a day without a phone and then through the trouble of replacing it seems like it should be worth something!
JMBush1007 said:
Okay, thanks. I did some rooting and ROMing back when I had a rezound, but haven't done anything of the sort on my S7. This method won't void my warranty, will it?
I know it's probably wishful thinking for the upgrade, but dang. Having to go a day without a phone and then through the trouble of replacing it seems like it should be worth something!
Click to expand...
Click to collapse
The rezound was a beast for this process. Like Simon says to get soff. But, know won't trip with Odin at all if you are using.stock fw
gunz.jones said:
The rezound was a beast for this process. Like Simon says to get soff. But, know won't trip with Odin at all if you are using.stock fw
Click to expand...
Click to collapse
I would think having s-off or root would be grounds for not covering on warranty, no? Or you're just saying that it's easy to get off on this device, not that I should?
I just got back from the Verizon store and the guy helping me saw the SuperSU app, which was there simply from being transferred over from google automatically from my last phone, and warned me that I may have tripped Knox and may not be covered by warranty if I had. He tried to look on the phone to see if it had, and he thought it was but said he wasn't sure because he hadn't done it in a while.
Like I said, I haven't done any thing like that, except today I did press pwr dwn + pwr + home, then I hit continue, so maybe that did it?
Anyway, if I can fix this myself I would like to just for times sake. However, since (presumably) it's under warranty still I don't want to do anything to it that will void that.
We got it to do a factory reset with much effort, finally having to copy paste my pin after typing it into the calculator and pasting it in the pin screen for the reset. Now it is stuck in the initialization mode, of the reset process and rebooting.
So, sorry to press further, but if you're sure this will not void my warranty, I will try the odin tool. I'm getting conflicting information on the interwebs about this. I want to make sure I get the right files and do it right, so do you mind linking? I've seen some stock flashes say they void the warranty. Although maybe I have already anyway?
Thanks again.
JMBush1007 said:
I would think having s-off or root would be grounds for not covering on warranty, no? Or you're just saying that it's easy to get off on this device, not that I should?
I just got back from the Verizon store and the guy helping me saw the SuperSU app, which was there simply from being transferred over from google automatically from my last phone, and warned me that I may have tripped Knox and may not be covered by warranty if I had. He tried to look on the phone to see if it had, and he thought it was but said he wasn't sure because he hadn't done it in a while.
Like I said, I haven't done any thing like that, except today I did press pwr dwn + pwr + home, then I hit continue, so maybe that did it?
Anyway, if I can fix this myself I would like to just for times sake. However, since (presumably) it's under warranty still I don't want to do anything to it that will void that.
We got it to do a factory reset with much effort, finally having to copy paste my pin after typing it into the calculator and pasting it in the pin screen for the reset. Now it is stuck in the initialization mode, of the reset process and rebooting.
So, sorry to press further, but if you're sure this will not void my warranty, I will try the odin tool. I'm getting conflicting information on the interwebs about this. I want to make sure I get the right files and do it right, so do you mind linking? I've seen some stock flashes say they void the warranty. Although maybe I have already anyway?
Thanks again.
Click to expand...
Click to collapse
It will not trip knox. So far the only thing that would trip knox is flashing a custom recovery, which we can't do. I have used the eng boot kernel a few times and still haven't tripped knox. What you're doing is flashing stock firmware back to the device in the same manner that they would at any phone shop to repair it.
gunz.jones said:
It will not trip knox. So far the only thing that would trip knox is flashing a custom recovery, which we can't do. I have used the eng boot kernel a few times and still haven't tripped knox. What you're doing is flashing stock firmware back to the device in the same manner that they would at any phone shop to repair it.
Click to expand...
Click to collapse
Alright, thanks for the reassurance.
Unfortunately, after apparent successful attempts using odin, the phone is still exhibiting the same behavior with closed app notifications, not showing the keyboard at times, and restarting. Guess I will be make a service request tomorrow, unless you have any other ideas?
Odin is a factory Samsung tool and will not flash anything to your phone that isn't allowed, due to the locked bootloader. What is your full build number? I can walk you through the steps of reflashing with Odin.
CVertigo1 said:
Odin is a factory Samsung tool and will not flash anything to your phone that isn't allowed, due to the locked bootloader. What is your full build number? I can walk you through the steps of reflashing with Odin.
Click to expand...
Click to collapse
I tried flashing QC5 a few different times, and also QA4 after that, and it just kept rebooting after the initialization screen. I loaded all 4 files, and got (1 succeeded / 0 failed) message from odin each time.
However, just now I went on Verizon's support chat to get a warranty replacement issued. I entertained Jennifer, the tier two from the windy city, and booted up in safemode. Everything seems to be working fine now! Although I did get a few close app notifications after changing from high performance mode to optimized.. but the phone is still up and running fine since then. I've been able to text and make calls for the first time since running the update yesterday morning. I'm hoping everything stays stable.
Also, I'm wondering whether it makes sense to try running the update again through the phones system update mechanism.
Thanks for the help!
The only option now is to force factory reset and clean out everything after flashing
From what I gather, you have already done a factory reset, haven't you? When you flashed with Odin, did you use HOME_CSC or CSC_VZW?
CVertigo1 said:
From what I gather, you have already done a factory reset, haven't you? When you flashed with Odin, did you use HOME_CSC or CSC_VZW?
Click to expand...
Click to collapse
Yes, yes, and yes. I did a factory reset and everything has been erased. I tried using both at different times. My last one was with QA4, and I used CSC_VZW iirc.
My phone is still going strong with no reboots since I started it up this morning!
Welp, things still seem to be running smoothly.
I do keep getting update notifications though. I'm tempted to press my luck and install the update.
Opinions? I'd be a lot more confident had it started working immediately after I flashed with Odin. The fact that I finally turned it off for the night after it cycled through several boot loops with different installs makes me wonder what the problem/solution actually was.
I guess I'll try it. It is still under warranty, and would probably be best to find out if there's an issue with it now rather than later.
I have the latest update and never exhibited the issues you have. Since you've done the factory reset, it probably wouldn't hurt to do the update. I have a feeling it should be good now. If not, then you know the update is bad. Only way to know is to try. Hoefully, it should work for you. It's been excellent for myself and many others.
iBolski said:
I have the latest update and never exhibited the issues you have. Since you've done the factory reset, it probably wouldn't hurt to do the update. I have a feeling it should be good now. If not, then you know the update is bad. Only way to know is to try. Hoefully, it should work for you. It's been excellent for myself and many others.
Click to expand...
Click to collapse
Yup, ran the update and everything is good!
Thanks for all the help, everyone.
Hey, is it possible to get rid of this message when booting?
Would be nice
Sure, just re-lock your bootloader. Presto. ?
thedrizzle said:
Sure, just re-lock your bootloader. Presto. ?
Click to expand...
Click to collapse
Probably a stupid question but im rooted, will it still boot up?
Macblack1991 said:
Probably a stupid question but im rooted, will it still boot up?
Click to expand...
Click to collapse
No, it's likely that your device will brick. Please don't do so
veatesia said:
No, it's likely that your device will brick. Please don't do so
Click to expand...
Click to collapse
Okay thanks for the reply
Dead end thread, there have been many many many many many posts about that since oneplus introduced that a couple of years ago
THERE IS NO WAY TO GET RID OF THAT WHILE UNLOCKED
period
and there's a thread about it here. been following this from the start and apparently it's next to impossible to achieve.
https://forum.xda-developers.com/oneplus-6t/development/wip-dissecting-bootloader-aka-rid-t3878470
veatesia said:
No, it's likely that your device will brick. Please don't do so
Click to expand...
Click to collapse
I have experience doing that. Yes your device will definitely get BRICKED!!! Just ignore that boot screen, do not attempt to do anything to get rid of it. It just takes time to accept it. I use to think about getting rid of it as well when i was using my Oneplus 3. I re-locked the bootloader and got bricked. I couldn't do anything and had to send it back to Oneplus to fix it.
There have been other devices where they are able to replace the image with another, such as a blank image to hide the warning. I've also seen people load custom ROMs signed with their own signature so they can relock their bootloader after loading a custom OS. So there are things that can be done, but it's not something to just play around with, as mentioned, mess it up, and you'll brick something.
Thanks for the replies. Well I guess its just how it is, nit a big issue, was just wondering because most videos of custom roms I saw this part was cut out lol.