I tried to change the shape of a clock with software. Now hung up in
"Vbrant samsung"
What can be done?
Odin back to stock.
Related
My Note 3 was bricked in the process of rooting. I can get to the Downloading screen on my phone, but I always get a "Failed" Message on Odin after NAND files are being written. The blue progress bar never goes past 10%. Any help would be awesome as I need to use this phone tomorrow! Many thanks!
Go here http://forum.xda-developers.com/showthread.php?t=2630669 this fixed it for the same situation as yours. Go into recovery mode as explained in the post and clear cache and then factory reset. If that doesn't work you will need to Odin back to stock. You will most likely have to use Vroot to root your phone.
Hello all,
I have a Samsung Galxy S5 with AT&T model SM-G900A. Any time the phone reboots, on the "Samsung Galaxy S5" boot screen, it says "Custom" and has an "Unlocked Padlock" logo as if the phone were rooted or something. A while back, I was trying to do a basic root to allow use of Titanium Backup using the Towelroot app, which failed because it said my phone was not supported. I'm not sure if this has caused it, or if, as I read elsewhere, it was caused by my once changing from Dalvik to ART. However, I have since switched back to Dalvik, I know its not rooted because SU and other such apps wont work, and I have even Factory Reset the device but I can not get rid of this. I would like to return my phone to its default state. How can I get rid of this "Custom" and Lock Logo? Your help is greatly appreciated! Thanks so much!
-Noomrise
It won't hurt anything as long as Knox isn't tripped but you can download the full stock retail ROM and flash it in Odin or Kies 3.
Update: Phone thinks its rooted?
Noomrise said:
Hello all,
I have a Samsung Galxy S5 with AT&T model SM-G900A. Any time the phone reboots, on the "Samsung Galaxy S5" boot screen, it says "Custom" and has an "Unlocked Padlock" logo as if the phone were rooted or something. A while back, I was trying to do a basic root to allow use of Titanium Backup using the Towelroot app, which failed because it said my phone was not supported. I'm not sure if this has caused it, or if, as I read elsewhere, it was caused by my once changing from Dalvik to ART. However, I have since switched back to Dalvik, I know its not rooted because SU and other such apps wont work, and I have even Factory Reset the device but I can not get rid of this. I would like to return my phone to its default state. How can I get rid of this "Custom" and Lock Logo? Your help is greatly appreciated! Thanks so much!
-Noomrise
Click to expand...
Click to collapse
Okay, so here is an update. After performing a factory reset in order to try and fix this issue, I was playing around and opened the "Softcard" app and received the message that it doesn't work on rooted phones. Since the Towelroot app did not work, I don't understand this. I have also been unable to get SuperUser to install binaries, saying the phone is not rooted. Don't know what this means or if it helps, but thought id give an update. Thanks again!
Would you be so kind as to provide me with a link to the retail ROM and instructions on flashing it through Kies 3? THANKS!
I'd have to do a search. .. or you could. ?
Rapunzl said:
I'd have to do a search. .. or you could.
Click to expand...
Click to collapse
Thanks, I found the file (I hope) and downloaded odin, and it is currently flashing. I will let you know if it a) removes the custom lock and b) fixes the softcard app thinking the phone is rooted. Thanks for your help!
It Worked!!!!!
Rapunzl said:
It won't hurt anything as long as Knox isn't tripped but you can download the full stock retail ROM and flash it in Odin or Kies 3.
Click to expand...
Click to collapse
I would like to report that flashing the stock ROM has fixed both the Custom Lock boot screen as well as SoftCard thinking my phone was rooted. Thank you Rapunzl for your help, you are awesome!
I successfully rooted my Samsung Galaxy A8(Indian variant A800F). While experimenting withe the DPI values by ROM Manager's build.prop editor I made the mistake of changing it to 160. So all the UI elements were gone(Icons, Notification Bar, etc).
Then I had the bright Idea of resetting the phone which somehow did not revert to the original DPI settings. This in turn disabled USB Debugging and now I'm unable to use ADB. Moreover the FRP Lock is turned on too so I guess Download Mode won't work either.
The only thing I can do right now is taking screen shots and turning the phone off(Shutdown Dialogue Box is visible too). I did not take a backup at the time nor did I flash any recovery.
Hope I made my issue clear.
Now what options do I have left?
Can re-flashing the firmware do the trick?
Would the Samsung service centre guys re-flash the firmware even after the KNOX getting tripped off. Or I'll have to do that myself?
Any sort of help is highly appreciated. Thanks!
Yes you should be able to flash stock firmware again but no guarantee it'll work. All you need to do is get the original firmware from sammobile and Odin, downloaded both, extract all the Odin files to your PC, also extract the md5.tar file from the firmware zip, boot to download and connect, if it connects then that's a start, once connected click "ap" box and choose the firmware you just downloaded, wait a couple of mins for Odin to check the md5 is correct then hit start.
Sent from my SM-A500FU using XDA-Developers mobile app
Great. Will try that and post the results.
Just wanted to ask if this manual procedure may somehow make my situation even worse. Or is it completely safe to flash?
Really don't want to get into a deeper mess.
And thanks for the quick response
sanu23kumar said:
Great. Will try that and post the results.
Just wanted to ask if this manual procedure may somehow make my situation even worse. Or is it completely safe to flash?
Really don't want to get into a deeper mess.
And thanks for the quick response
Click to expand...
Click to collapse
Completely safe, that's the beauty of ODIN.
sanu23kumar said:
I successfully rooted my Samsung Galaxy A8(Indian variant A800F). While experimenting withe the DPI values by ROM Manager's build.prop editor I made the mistake of changing it to 160. So all the UI elements were gone(Icons, Notification Bar, etc).
Then I had the bright Idea of resetting the phone which somehow did not revert to the original DPI settings. This in turn disabled USB Debugging and now I'm unable to use ADB. Moreover the FRP Lock is turned on too so I guess Download Mode won't work either.
The only thing I can do right now is taking screen shots and turning the phone off(Shutdown Dialogue Box is visible too). I did not take a backup at the time nor did I flash any recovery.
Hope I made my issue clear.
Now what options do I have left?
Can re-flashing the firmware do the trick?
Would the Samsung service centre guys re-flash the firmware even after the KNOX getting tripped off. Or I'll have to do that myself?
Any sort of help is highly appreciated. Thanks!
Click to expand...
Click to collapse
you can flash it with service firmware (that means the firmware that one have all the file separately,pda csc cp bl pit) from,joomla or any other forum. it will reset the phone to its factory state.in ksa knox counter tripping not void the warranty.you can take the phone to any customer care without any problem.
How did you rooted it?
sanu23kumar said:
I successfully rooted my Samsung Galaxy A8(Indian variant A800F). While experimenting withe the DPI values by ROM Manager's build.prop editor I made the mistake of changing it to 160. So all the UI elements were gone(Icons, Notification Bar, etc).
Then I had the bright Idea of resetting the phone which somehow did not revert to the original DPI settings. This in turn disabled USB Debugging and now I'm unable to use ADB. Moreover the FRP Lock is turned on too so I guess Download Mode won't work either.
The only thing I can do right now is taking screen shots and turning the phone off(Shutdown Dialogue Box is visible too). I did not take a backup at the time nor did I flash any recovery.
Hope I made my issue clear.
Now what options do I have left?
Can re-flashing the firmware do the trick?
Would the Samsung service centre guys re-flash the firmware even after the KNOX getting tripped off. Or I'll have to do that myself?
Any sort of help is highly appreciated. Thanks!
Click to expand...
Click to collapse
How did you rooted it?
I used Smart Switch to unbrick after a having a FRP lock bootloop
Hi, im selling my S5 so wanted to unroot it and put the stock Rom back on it.
So using Odin 3.12 I have put the phone into download mode, added the .tar file to the AP part of Odin and hit start. I get a pass and the phone reboots, then states it is sorting out the App's, then it reboots again and just sits on the Samsung screen.
Can anyone help me? I've obviously gone wrong some where.
Opened Odin as Admin, think that may have been the issue as all working fine now, or 3rd time a treat, whop knows!!
Hello there,
i need help with fixing my phone, i tried to change the model of the phone by changing the build.prop file, like everyone else who does something like this for the first time. i bricked my phone and it went into a bootloop.
after ton of research on multiple websites and especially xda-developers, i managed to flash the phone with a suitable frameware form the galalxy S5, the first time i did it i accidently put the firmware into the BL position into ODIN. then i put it into AP and reset the device.
the download was succesfull, but the phone didnt start up. the next day i turned the phone on, and after 5 mins being stuck on the Samsung logo, it finally booted up and i managed to get inside the phone. i thought it has been fixed, the device asked if i wanted to apply updates, which i said yes to. It updated and tried to restart itself.
now it wont turn on, everytime i try restarting it it is just shutting itself again animated samsung logo fades.
i don´t know what i should do right now, i tried looking for similar situations to mine but i couldn´t find anything similar.
Can someone tell me what i should do in oder to get it fixed pls.
model: SM-g900f
thanks in advance.
edit: it is working again, but it has been completely reset. for now it worked. going to update it again, i will put if the same problem accours again.
bayar16 said:
i tried to change the model of the phone by changing the build.prop file, like everyone else who does something like this for the first time. i bricked my phone and it went into a bootloop.
Click to expand...
Click to collapse
Most likely you forgot to set permissions 0x644 for this file after editing it.
It's a common mistake.