I had my Verizon Galaxy S4 rooted. I am looking to turn my phone in today for the Note 3. I went into SU and checked I wanted to unroot my phone. My phone is unrooted now, but I can't get the Custom Lock that appears when you first boot the phone. I can't upgrade the phone either. I did a hard reset and that didn't work. I tried everything, and I can't get rid of that Custom Lock that appears, and I am afraid that I won't be able to turn my phone it. Can anyone help me?
Thank you,
Al Metta
You need to Odin it back to stock. I'll get you the link
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
am2354 said:
I had my Verizon Galaxy S4 rooted. I am looking to turn my phone in today for the Note 3. I went into SU and checked I wanted to unroot my phone. My phone is unrooted now, but I can't get the Custom Lock that appears when you first boot the phone. I can't upgrade the phone either. I did a hard reset and that didn't work. I tried everything, and I can't get rid of that Custom Lock that appears, and I am afraid that I won't be able to turn my phone it. Can anyone help me?
Thank you,
Al Metta
Click to expand...
Click to collapse
Flash the MK2 ODIN tar
http://forum.xda-developers.com/showthread.php?t=2578209
am2354 said:
I had my Verizon Galaxy S4 rooted. I am looking to turn my phone in today for the Note 3. I went into SU and checked I wanted to unroot my phone. My phone is unrooted now, but I can't get the Custom Lock that appears when you first boot the phone. I can't upgrade the phone either. I did a hard reset and that didn't work. I tried everything, and I can't get rid of that Custom Lock that appears, and I am afraid that I won't be able to turn my phone it. Can anyone help me?
Thank you,
Al Metta
Click to expand...
Click to collapse
To remove the "Custom" flag, you've got to return the phone to stock. If you haven't done anything but rooted it, then run the "unroot" script in the Saferoot thread (which means you'll need to re-root, unfortunately). After a reboot, the custom flag will reset.
However, many people have reported that having Custom hasn't caused them to have warranty claims denied.
Related
Upgraded from my Rooted Galaxy S1 to a shiny new S3 and rooted because it did improve the performance of the S1.
Since doing so my phone intermittently turns off and restarts.
Its a UK phone on Tmobile. Will some kind soul point me in the right direction on how to get my phone back to stock.
I rooted the phone using Odin. I have deleted most of the rooted apps the exceptions being cwm manager, root checker, super user and voodoo ota rootkeeper.
Any help appreciated
Thanks
Steve
Factory reset
Sent from my GT-I9300 using xda app-developers app
stevegold6 said:
Upgraded from my Rooted Galaxy S1 to a shiny new S3 and rooted because it did improve the performance of the S1.
Since doing so my phone intermittently turns off and restarts.
Its a UK phone on Tmobile. Will some kind soul point me in the right direction on how to get my phone back to stock.
I rooted the phone using Odin. I have deleted most of the rooted apps the exceptions being cwm manager, root checker, super user and voodoo ota rootkeeper.
Any help appreciated
Thanks
Steve
Click to expand...
Click to collapse
Google for Branded ROMs and reflash through Odin the original ROM if you "wish you hadnt rooted" your phone...there could be many reasons that cause such issues...such as the phone hardware itself which in your case regardless of rooted or not will still present such issues...if it was a software issue, either you have selected the incorrect insecure kernel or...your phone has no love for you.
Factory reset will solve ur problem
Sent from my GT-I9300 using Tapatalk 2
Go into recovery and fix permissions. If that fails, like the other person stated, factory reset. If that doesn't work. The rooting process must have messed up when you did it. Use Odin and factory firmware to go back to stock. Then try the root process again. But look for another method to do so. I am not on TMobil so I don't know how that works with that phone. But there are a ton of posts here that explain everything in detail going forward and backwards. Good luck. Let us know how it turns out.
stevegold6 said:
Upgraded from my Rooted Galaxy S1 to a shiny new S3 and rooted because it did improve the performance of the S1.
>>> Root cannot improve performance by itself .
Since doing so my phone intermittently turns off and restarts.
..>>>>Possible bad flash
Run Triangle away to reset rom counter to zero .
Download your firmware via CHECKFUS flash via Odin boot then factory reset .
jje
Click to expand...
Click to collapse
Really new to this. I did the verizon root methed for ME7. It says can't complete upgrade. Do I need to unroot in order to upgrade to MI1? If so, how do I do that?
bbroydri said:
Really new to this. I did the verizon root methed for ME7. It says can't complete upgrade. Do I need to unroot in order to upgrade to MI1? If so, how do I do that?
Click to expand...
Click to collapse
You don't need to unroot, but you do need to have the device in a stock condition. If you've debloated and removed stuff, or frozen apps, then the upgrade will likely fail.
I wouldn't be in any rush to install MI1.
Had same problem, now soft bricke my phone and need help
k1mu said:
You don't need to unroot, but you do need to have the device in a stock condition. If you've debloated and removed stuff, or frozen apps, then the upgrade will likely fail.
I wouldn't be in any rush to install MI1.
Click to expand...
Click to collapse
I was in the same position trying to accept the update from ME7. I had re-downloaded the stock apps and was in the process of converting them to system apps when my phone froze. When I tried to reboot I could not get passed the Verizon screen. I have been trying to read about how to fix this but I am unable to get odin to recognize my phone. I have downloaded the Samsung drivers and tried every version of odin but nothing happens when I put my phone into download (odin) mode and connect it with odin open. The rest of the steps seem easy if I could just get it to see my phone. Any thoughts, going on 3 days with no phone.
I've been trying to get my phone back on stock rom for hours or at least to the point where I can use it. Ive tried several methods in the past day. However, I have not been able to do it without success. This was all for the purpose of updating to 4.3 since I hadn't updated since I rooted my phone. First I unrooted it through Supersu and tried to apply the update but it wouldnt work so then I factory reset it. I applied the update again but it didnt seem to want to update to 4.3 . So then I went to TWRP and cleaned out the files, but I never checked to it to the system. After that It was stuck into a boot loop. It never got past the Galaxy s4 boot image. I still have a back up of everything after I rooted my phone, but after applying the following system recovery
stockroms.net/file/GalaxyS4/SPH-L720/L720VPUAMDC_L720SPTAMDC_SPR.zip
I am no longer able to use TWRP and my phone is still in the same situation. All I know about my phone without acess to the information in the about phone section is that it is a Verison Galaxy S4 and before I did anything it was on an android 4.2.2 rooted stock. On the box it say its a SPHl720BKK. If anyone could help me that would be greatly appreciated before I hard brick my phone with the little experiance i have.
santiagorook said:
I've been trying to get my phone back on stock rom for hours or at least to the point where I can use it. Ive tried several methods in the past day. However, I have not been able to do it without success. This was all for the purpose of updating to 4.3 since I hadn't updated since I rooted my phone. First I unrooted it through Supersu and tried to apply the update but it wouldnt work so then I factory reset it. I applied the update again but it didnt seem to want to update to 4.3 . So then I went to TWRP and cleaned out the files, but I never checked to it to the system. After that It was stuck into a boot loop. It never got past the Galaxy s4 boot image. I still have a back up of everything after I rooted my phone, but after applying the following system recovery
stockroms.net/file/GalaxyS4/SPH-L720/L720VPUAMDC_L720SPTAMDC_SPR.zip
I am no longer able to use TWRP and my phone is still in the same situation. All I know about my phone without acess to the information in the about phone section is that it is a Verison Galaxy S4 and before I did anything it was on an android 4.2.2 rooted stock. On the box it say its a SPHl720BKK. If anyone could help me that would be greatly appreciated before I hard brick my phone with the little experiance i have.
Click to expand...
Click to collapse
You're posting in a forum for the SCH-I545. That's a Verizon Galaxy S4.
The SPH-L720 is an international phone, You'll need to post on a forum for that particular variant of the GS4 if you expect any help.
Hi all,
I need help badly. I recently bought a Samsung galaxy s4, rooted it on the mj7 build, there was an ota mk2 I did. After I was done updating root was broken. I am sending the phone back and needed to remove root and the custom boot logo. I did a factory reset on the device, I downloaded Odin and tried numerous m5 files to flash back to stock. It keeps failing. Now the phone won't boot normally. Someone please help
chudze said:
Hi all,
I need help badly. I recently bought a Samsung galaxy s4, rooted it on the mj7 build, there was an ota mk2 I did. After I was done updating root was broken. I am sending the phone back and needed to remove root and the custom boot logo. I did a factory reset on the device, I downloaded Odin and tried numerous m5 files to flash back to stock. It keeps failing. Now the phone won't boot normally. Someone please help
Click to expand...
Click to collapse
If you're going to return the phone, flash the emergency recovery MJ7 ROM in the Android Development thread.
Hopefully you didn't trip the Knox Warranty Void flag with your serial flashing.
k1mu said:
If you're going to return the phone, flash the emergency recovery MJ7 ROM in the Android Development thread.
Hopefully you didn't trip the Knox Warranty Void flag with your serial flashing.
Click to expand...
Click to collapse
Hi, thanks for replying. I was able to successfully restore to mk2, I don't see the boot screen that says Samsung custom, and I don't see supersu either. I don't know what knox is, and how would I check to see if something happened to that?
chudze said:
Hi, thanks for replying. I was able to successfully restore to mk2, I don't see the boot screen that says Samsung custom, and I don't see supersu either. I don't know what knox is, and how would I check to see if something happened to that?
Click to expand...
Click to collapse
Boot your phone into bootloader mode and read the REALLY TINY text. One line will read "Knox Warranty Void" and either 0x0 (warranty OK) or 0x1 (warranty void).
Get into bootloader mode by powering off, then holding volume down, home, then power. Release when the phone vibrates.
k1mu said:
Boot your phone into bootloader mode and read the REALLY TINY text. One line will read "Knox Warranty Void" and either 0x0 (warranty OK) or 0x1 (warranty void).
Get into bootloader mode by powering off, then holding volume down, home, then power. Release when the phone vibrates.
Click to expand...
Click to collapse
OK, I followed your instructions and it says 0x0, so everything should be OK. Thank you
Has anyone tried Towelroot on the S4 NC5 build?
Is this going to unlock the bootloader?
Sent from my SCH-I545 using Tapatalk
This is root method....no it will NOT unlock boot loader
And yes I have used it on my wife's phone it works great..
There is a thepread on it in general section...
sambrooke said:
Has anyone tried Towelroot on the S4 NC5 build?
Is this going to unlock the bootloader?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Works perfectly.
sambrooke said:
Has anyone tried Towelroot on the S4 NC5 build?
Is this going to unlock the bootloader?
Click to expand...
Click to collapse
We really seem to have failed in helping people to understand this, as Towelroot users are now bricking phones right and left by people who root bootloader locked phones then use Goo Manager and the like to try to flash custom recovery and fail.
If your bootloader is locked, you can't flash custom recovery or custom kernel. It doesn't matter if you're rooted or not.
"CUSTOM" Software
Does anyone know if the triggers the "Custom" and the unlocked padlock when rebooting?
seadooman said:
Does anyone know if the triggers the "Custom" and the unlocked padlock when rebooting?
Click to expand...
Click to collapse
It DOES trigger the Custom padlock. With root access you can install Xposed Framework and one of modules allows you to reset that back to Original boot screen.
I think triangle away will work also. I haven't tried yet, but removed the custom screen with the mk2 build after that was rooted with saferoot.
http://forum.xda-developers.com/galaxy-s2/orig-development/2014-01-15-triangleaway-v3-26-t1494114
Sent from my IdeaPad U410 using Tapatalk
Lost "HI Galaxy Funtion"
Not sure if its related but I lost the handsfree "HI Galaxy" , Get the cannot connect to servers error. Anyone experience this?
seadooman said:
Not sure if its related but I lost the handsfree "HI Galaxy" , Get the cannot connect to servers error. Anyone experience this?
Click to expand...
Click to collapse
If it really happened out of the blue, without installing or reconfiguring anything, your issue will probably be fixed with a power cycle. I would try a battery pull, holding down the power button for a couple seconds without the battery in place (to drain remnants of electricity), replace the battery, boot, reboot, soft/hotboot. If that doesn't fix it, you must have done something to stop it from functioning in the first place.
Yes that also happened to me.. Not sure if it was related to towel root or something I froze. I unfroze everything and uninstalled towel root still had issue..ended up reinstalling oem firmware and everything works normal now. Wondering if the samsung servers know the phone is rooted and refuse connection?
seadooman said:
Yes that also happened to me.. Not sure if it was related to towel root or something I froze. I unfroze everything and uninstalled towel root still had issue..ended up reinstalling oem firmware and everything works normal now. Wondering if the samsung servers know the phone is rooted and refuse connection?
Click to expand...
Click to collapse
Doubtful; people saying "Hi Galaxy" is free advertising for them. If it occured after freezing tasks I'm sure that was the source of the problem. Must be SELinux related. Next time, just redo your root; you probably didn't need to forfeit data.
I unfroze everything and it was hit and miss if it connected or not. Reinstalled android problem was gone. Just thought I would offer my experience on this..
On NC5 it was the fastest and easiest root ever.
One of my phone's is a Galaxy S3 using NE1 and since i couldn't unlock the bootloader but, i had successfully rooted it using towelroot.
It has been about 6 months and i never had issues.
Not everyone with a matching phone has the same issues when it comes to Rooting as well as Bootloader Unlocking.
One's bad experience doesn't always mean another will have the same. This all depends on the expertise and know-how of the user as well as the reliability of an individual who provides the information and/or files accomplishing a Root and/or Bootloader Unlocking.
Just my opinion :fingers-crossed: