I started having this problem after rooting and installing custom rom. It does not matter which rom you install. The only fix I have found is to unroot and return to stock..
Once you root and install your rom the phone works fine, until you reboot. Then it just hangs at the padlock screen. You have to pull the battery and reboot into recovery, format, and reinstall the rom, or go back to stock... HELP!!!!!!
When originally rooting did you let supersu update and select normal?
Sent from my SCH-I545 using xda app-developers app
I did update, not sure about selecting normal. I don't remember seeing that option. What does the normal do?
You need to select normal when updating supersu when you open the app. And what recovery are you using? Have you tried installing goo manager and installing the script which is twrp that has auto loki.
Sent from my SCH-I545 using xda app-developers app
Yea, I installed TWRP from goo.. I will root again and make sure I check normal.
I don't see the Normal setting. Could you point it out..
Ok... I'm a D.A. Both times I rooted, I missed the step of downloading SuperSU and updating it during the Root process. Thanks Black Hat.. Everything should be good now.
You're welcome. Let me know how you turn out!
Sent from my SCH-I545 using xda app-developers app
I spoke to soon.. No Joy.. I managed to get it to reboot one time. Now stuck at Custom Padlock, again.
i'm actually having the same issue. i followed the directions to root using the pre-release kernel and odin. i updated the SU binaries and selected Normal when it asked me. after that i installed the custom recovery using GooManager. now when i install a ROM and reboot it hangs. wonder whats going on. hopefully someone can help us out
trbman said:
i'm actually having the same issue. i followed the directions to root using the pre-release kernel and odin. i updated the SU binaries and selected Normal when it asked me. after that i installed the custom recovery using GooManager. now when i install a ROM and reboot it hangs. wonder whats going on. hopefully someone can help us out
Click to expand...
Click to collapse
You shoul be able to return to stock with one of the methods in the developers forum.
i'm going to try returning to stock than trying everything all over again. i'll report back on how it goes
I've seen another person reporting this issue in the hyper thread. I installed the hyper rom last night and rebooted fine like three to four times no issues but now I'm scared to reboot lol
Sent from my SCH-I545 using xda app-developers app
imablackhat said:
I've seen another person reporting this issue in the hyper thread. I installed the hyper rom last night and rebooted fine like three to four times no issues but now I'm scared to reboot lol
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
that other person was me. haha
I wonder what's going on. If you're missing a step or something. Idk I've installed last night upon release. Rebooted a couple times. Didn't have an issue. When I wiped. I wiped data system cache and dalvik twice. Then installed the rom and rebooted. Restored my apps and settings. Let it settle for a sec and rebooted again. Didn't have any issues.
People that are stuck at padlock screen. You're using the latest twrp autoloki? Can you get back into recovery even though you can't get past padlock. And how long do you wait at the padlock?
Sent from my SCH-I545 using xda app-developers app
---------- Post added at 09:45 PM ---------- Previous post was at 09:43 PM ----------
After rooting and updating supersu and hitting normal. you guys are going back and flashing the normal kernel not prerelease right through Odin?
Sent from my SCH-I545 using xda app-developers app
imablackhat said:
I wonder what's going on. If you're missing a step or something. Idk I've installed last night upon release. Rebooted a couple times. Didn't have an issue. When I wiped. I wiped data system cache and dalvik twice. Then installed the rom and rebooted. Restored my apps and settings. Let it settle for a sec and rebooted again. Didn't have any issues.
People that are stuck at padlock screen. You're using the latest twrp autoloki? Can you get back into recovery even though you can't get past padlock. And how long do you wait at the padlock?
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
i installed TWRP using GooManager. it said it was version 2.5.0.2. yes, i can get back into recovery. and the padlock screen stays there indefinitely. i am in the process of odin-ing back to stock so i'm gonna start over and we'll see how it goes. hopefully this resolves it. can't live with Stock TouchWiz.
EDIT---
yes, i hit normal and flashed back to stock kernel from the pre-release.
So it booted fine once. How long were you in it? Did you install anything or configure anything or did you install boot it up. And reboot and notice it won't come back up and hangs?
Because I've been told X posed doesn't work yet even though it's in the rom and if you install it. It'll soft brick and you'll need to dirty flash or reinstall.
Sent from my SCH-I545 using xda app-developers app
trbman said:
i'm going to try returning to stock than trying everything all over again. i'll report back on how it goes
Click to expand...
Click to collapse
Already done that.. No help.. Maybe you will have better luck.
Two people so far with the same issue. Doesn't matter whatever rom?.. ;/
Sent from my SCH-I545 using xda app-developers app
imablackhat said:
I wonder what's going on. If you're missing a step or something. Idk I've installed last night upon release. Rebooted a couple times. Didn't have an issue. When I wiped. I wiped data system cache and dalvik twice. Then installed the rom and rebooted. Restored my apps and settings. Let it settle for a sec and rebooted again. Didn't have any issues.
People that are stuck at padlock screen. You're using the latest twrp autoloki? Can you get back into recovery even though you can't get past padlock. And how long do you wait at the padlock?
Sent from my SCH-I545 using xda app-developers app
---------- Post added at 09:45 PM ---------- Previous post was at 09:43 PM ----------
After rooting and updating supersu and hitting normal. you guys are going back and flashing the normal kernel not prerelease right through Odin?
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Done all of that. Rerooted twice! I'm getting frustrated with it. I am now back to stock with no problems.. But yea, I was able to get into recovery after pulling the battery. :crying:
Related
the other day i tried restoring a back up via TWRP but it didnt work until i fastboot flashed boot.img...Alright so i updated my TWRP via goomanager app to the latest version (whatever is on there via goomanager) as in the TWRP forum discussions it was stated that previous versions were not working properly wihen restoring. So today i flashed a new ROM (NOS ROM) but that didnt work so i decided what better time than now to try restoring again, no dice didnt work and i had to fastboot flash the boot img for the restore file to take and boot up just fine again...ok peeps what am doing wrong??? again im fairly new at this flashing ROMS scene but i thought witht he TWRP update i would be good to go. Am i missing some settings ticks/options/checks? i saw a check box that said "recovery" i think in the restore or back up process dont remember which process. i tried going onto the TWRP discussion but it is locked down and states that there will no longer be any support for it...should i just switch to CWM?? thanks in advance to whom ever replies
twrp recovery..
kenohki88 said:
the other day i tried restoring a back up via TWRP but it didnt work until i fastboot flashed boot.img...Alright so i updated my TWRP via goomanager app to the latest version (whatever is on there via goomanager) as in the TWRP forum discussions it was stated that previous versions were not working properly wihen restoring. So today i flashed a new ROM (NOS ROM) but that didnt work so i decided what better time than now to try restoring again, no dice didnt work and i had to fastboot flash the boot img for the restore file to take and boot up just fine again...ok peeps what am doing wrong??? again im fairly new at this flashing ROMS scene but i thought witht he TWRP update i would be good to go. Am i missing some settings ticks/options/checks? i saw a check box that said "recovery" i think in the restore or back up process dont remember which process. i tried going onto the TWRP discussion but it is locked down and states that there will no longer be any support for it...should i just switch to CWM?? thanks in advance to whom ever replies
Click to expand...
Click to collapse
What did you have checked while making the backup? data? recovery? cache? system? and did you rename the back up?
System, data and boot are checked...I didn't mess with the options just hit restore and let it do it's thing...should I change something or check the other 2 boxes (one of them being "recovery" forgot what the other option was)?
Sent from my HTC6435LVW using xda app-developers app
kenohki88 said:
System, data and boot are checked...I didn't mess with the options just hit restore and let it do it's thing...should I change something or check the other 2 boxes (one of them being "recovery" forgot what the other option was)?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I would check recovery as well and try again.....also make sure to wipe everything before flashing anything
---------- Post added at 12:42 PM ---------- Previous post was at 12:34 PM ----------
canemaxx said:
I would check recovery as well and try again.....also make sure to wipe everything before flashing anything
Click to expand...
Click to collapse
also some roms are picky about which recovery is used to install/backup. I can say I have had no issues backing up stock or custom roms with twrp on my DNA
Alright sounds good maybe later on tonight when I'm at my computer just in case thank you for the tips I as well haven't had much trouble flashing ROMS with TWRP, albeit I've only tried flashing 2 or 3 been very happy with ViperDNA just wanted to check out different ones and easily restore back to viper
Sent from my HTC6435LVW using xda app-developers app
kenohki88 said:
Alright sounds good maybe later on tonight when I'm at my computer just in case thank you for the tips I as well haven't had much trouble flashing ROMS with TWRP, albeit I've only tried flashing 2 or 3 been very happy with ViperDNA just wanted to check out different ones and easily restore back to viper
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Check out NOS its a great rom
canemaxx said:
Check out NOS its a great rom
Click to expand...
Click to collapse
That's exactly what I was trying when all this happened...I flashed it via flash gui app like I've been doing but for some reason it didn't work...when I went to unlock screen it would pull up HTC splash screen and just stay stuck there... I'm not S-off yet so would that have something to do with NOS ROM not functioning?
Sent from my HTC6435LVW using xda app-developers app
kenohki88 said:
That's exactly what I was trying when all this happened...I flashed it via flash gui app like I've been doing but for some reason it didn't work...when I went to unlock screen it would pull up HTC splash screen and just stay stuck there... I'm not S-off yet so would that have something to do with NOS ROM not functioning?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
no thats how that rom boots....leave it alone for about 5-10 minutes youlll see the notificatiion light come on and your =e good to go
Let me rephrase that...it boots up, screen comes on silver background from butterfly then I go pull ring to unlock and it pulls up the HTC splash screen once I unlock and will not move from there...so that's when I reset and went back to viper...???
Sent from my HTC6435LVW using xda app-developers app
kenohki88 said:
Let me rephrase that...it boots up, screen comes on silver background from butterfly then I go pull ring to unlock and it pulls up the HTC splash screen once I unlock and will not move from there...so that's when I reset and went back to viper...???
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Flash the new Nos build, and flash cpalmers kernel after the Rom install and then reboot.
Sent from my ADR6425LVW using Xparent Red Tapatalk 2
Haven't tried it since I posted this, but ok I'll give it another spin/attempt this weekend thanks for the tip
Sent from my HTC6435LVW using xda app-developers app
kenohki88 said:
Haven't tried it since I posted this, but ok I'll give it another spin/attempt this weekend thanks for the tip
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I may have misread but did you wipe everything before loading nos? I saw what was checked for backup but not about wiping. You should wipe everything-system, then cache, then delvik cache-not exactly in that order (make SURE there IS a backup just in case). Load the rom AND flash the correct image file with adb. Also, many roms when FIRST loading up sit a long time before they start up, not sure if nos does this or not-I have been jumpy about the time sitting with a few roms when waiting was all I needed to do. I have had different Viper versions on a few times and moving to another rom was quirky each time I did so, not sure why.
NOS did that to me too. Just wait....it will load into the setup wizard. I think being s-on, which I still am...twrp isn't able to back up and restore your roms boot.img. just a guess but I to failed to restore a backup when an install went awry. Makes sense to be being that you can't install a kernel from recovery either.
Sent from my HTC6435LVW using xda app-developers app
Ajj915 said:
NOS did that to me too. Just wait....it will load into the setup wizard. I think being s-on, which I still am...twrp isn't able to back up and restore your roms boot.img. just a guess but I to failed to restore a backup when an install went awry. Makes sense to be being that you can't install a kernel from recovery either.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I looked at the install instructions for nos, if you are s-on you need to do one extra step. You have to extract the rom into a folder somewhere to get the image file, copy the image file from it. Flash that image file using adb on your pc and THEN install the rom from your phone with goomanager. Without the image file loaded, I don't think it would work. If you are s-off this step is not needed.
rootntootn said:
I looked at the install instructions for nos, if you are s-on you need to do one extra step. You have to extract the rom into a folder somewhere to get the image file, copy the image file from it. Flash that image file using adb on your pc and THEN install the rom from your phone with goomanager. Without the image file loaded, I don't think it would work. If you are s-off this step is not needed.
Click to expand...
Click to collapse
I get that. I'm purely talking about after a full while that I'm not sure if twrp will restore the boot.img from a nandroid. S-On of course.
Sent from my HTC6435LVW using xda app-developers app
Ajj915 said:
I get that. I'm purely talking about after a full while that I'm not sure if twrp will restore the boot.img from a nandroid. S-On of course.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I believe it will, if it had the image from the get go. I believe that the back up has everything it needs. At least my back ups have never needed an image file. I decided I should try NOS myself and must say it would not go for me (S-off) it kept rebooting into recovery. I was going to try and also flash the boot image but have not done so yet.
---------- Post added at 10:10 AM ---------- Previous post was at 10:08 AM ----------
rootntootn said:
I believe it will, if it had the image from the get go. I believe that the back up has everything it needs. At least my back ups have never needed an image file. I decided I should try NOS myself and must say it would not go for me (S-off) it kept rebooting into recovery. I was going to try and also flash the boot image but have not done so yet.
Click to expand...
Click to collapse
Oh yeah, and I restored my back up and that works just fine
rootntootn said:
I believe it will, if it had the image from the get go. I believe that the back up has everything it needs. At least my back ups have never needed an image file. I decided I should try NOS myself and must say it would not go for me (S-off) it kept rebooting into recovery. I was going to try and also flash the boot image but have not done so yet.
---------- Post added at 10:10 AM ---------- Previous post was at 10:08 AM ----------
Oh yeah, and I restored my back up and that works just fine
Click to expand...
Click to collapse
Its the kernel in NOS. Flash NOS and then flash cpalmers kernel. Then reboot and do the setup and if you want to change to the zarboz kernel you need to delete system/bin/thermald or rename it to thermald_old.bak
Sent from my HTC6435LVW using Xparent Red Tapatalk 2
Hmmm well I did everything via my cell (been the way I've been flashing ROMS unless something goes wrong then I use ADB on computer) and everything when properly done works fine using Flash GUI APP love that app! I've flashed super charged hatka 320 (used that for a couple weeks) then switched over to viper...both using Flash GUI I tried using NOS but yes no dice loaded up but when I pull the unlock ring for whatever reason the splash screen comes up and it won't budge from there....and as for my original question haha TWRP did not work for me when restoring it tripped out like if it was missing the boot image (done that before so I'm familiar with that behavior haha)
Oh and I'm still S-on
Sent from my HTC6435LVW using xda app-developers app
CharliesTheMan said:
Flash the new Nos build, and flash cpalmers kernel after the Rom install and then reboot.
Sent from my ADR6425LVW using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
That's what mine does too......just wait til the notification light turns orange and you will be all set......be patient.
canemaxx said:
That's what mine does too......just wait til the notification light turns orange and you will be all set......be patient.
Click to expand...
Click to collapse
Really? After it boots up? That's odd but ok I'll give it a shot again but probably tomorrow will post here again if it doesn't work....thanks everyone for responding. I'm out at the moment and need cell to be functioning hahaha just in case
Sent from my HTC6435LVW using xda app-developers app
I've been running Hyperdrive rom on CWM, and decided I wanted to try Illusion. So I rebooted into recovery, deleted cache and data, then installed the Illusion rom. At the end a yellow triangle popped up telling me that the software was insecure or something, and told me to go to a Verizon store.
I read that this was due to the kernel not being loki'd, so like an idiot I went back to Odin and flashed a kernel.
Soon after my screen went black, but I could hear the sounds of me raising/lowering the volume and turning the screen on and off.
I took the battery out and put it back in, and now all I see is an empty battery imposed on a black background with a frozen loading-circle int he middle.
Have I bricked my phone?
Edit:
When I unplug the phone from my computer and turn it on I see the Samsung boot-up along with the word Custom and unlocked icon above it. From there all I get is a black screen.
I can hold the lock+home+lower volume keys and I get the "Press volume up key if you want to download a custom OS" and "Volume down to cancel (restart phone)" screen, then the little green android shows up. Is there anything I can do from here?
You likely have "soft bricked" it, as long as you can still access it with odin or push files to it with adb you are not hard bricked... if you can, get the current verizon firmware from Sammobile.com and flash that with odin. This or fastboot are your best options. Take your time. Dont make things worse by trying things without reading completely. As long as you can flash and see it from adb or odin you can get it fixed up. Good luck
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
SmartAs$Phone said:
You likely have "soft bricked" it, as long as you can still access it with odin or push files to it with adb you are not hard bricked... if you can, get the current verizon firmware from Sammobile.com and flash that with odin. This or fastboot are your best options. Take your time. Dont make things worse by trying things without reading completely. As long as you can flash and see it from adb or odin you can get it fixed up. Good luck
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the response!
1. "USA" isn't listed in both "Galaxy S 4" or "Galaxy S 4 LTE" on Sammobile
2. So I reboot into download mode, connect phone to pc, run odin, and flash PDA?
http://forum.xda-developers.com/showthread.php?t=2301259
Read that and use the file in the thread.
Ryno77 said:
http://forum.xda-developers.com/showthread.php?t=2301259
Read that and use the file in the thread.
Click to expand...
Click to collapse
Thank you, I'm currently downloading the file. Will give it a shot.
dabs delicious said:
Thank you, I'm currently downloading the file. Will give it a shot.
Click to expand...
Click to collapse
No problem. I don't know how familiar you are with Odin but reading the original post closely and following any guides posted would be a good idea. Once you've used Odin once it's very easy....scary the first time.
Ryno77 said:
No problem. I don't know how familiar you are with Odin but reading the original post closely and following any guides posted would be a good idea. Once you've used Odin once it's very easy....scary the first time.
Click to expand...
Click to collapse
I followed the guide and successfully flashed the file, but now my screen is stuck on the "Verizon" logo page..
dabs delicious said:
I followed the guide and successfully flashed the file, but now my screen is stuck on the "Verizon" logo page..
Click to expand...
Click to collapse
Try booting into recovery and wiping data. You may have to pull the battery to get it into recovery.
Sent from my SCH-I545 using xda premium
Ryno77 said:
Try booting into recovery and wiping data. You may have to pull the battery to get it into recovery.
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
By this do you mean I should go into Odin and tick Nand Erase All? Sorry, I'm a complete noob at this and none of the threads I looked up really provided solid answers..
No, just boot into stock Android recovery and wipe data. Not Odin.
Sent from my SCH-I545 using xda premium
---------- Post added at 10:25 PM ---------- Previous post was at 10:20 PM ----------
dabs delicious said:
By this do you mean I should go into Odin and tick Nand Erase All? Sorry, I'm a complete noob at this and none of the threads I looked up really provided solid answers..
Click to expand...
Click to collapse
Sorry, I don't know if your subscribed to this or not but hopefully the quote notification gets to you...try stock recovery not Odin at this point.
Sent from my SCH-I545 using xda premium
Ryno77 said:
No, just boot into stock Android recovery and wipe data. Not Odin.
Sent from my SCH-I545 using xda premium
---------- Post added at 10:25 PM ---------- Previous post was at 10:20 PM ----------
Sorry, I don't know if your subscribed to this or not but hopefully the quote notification gets to you...try stock recovery not Odin at this point.
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
Yes, I'm watching this thread eagerly haha, I would like to fix my phone
So I held power+volume up+home and entered stock recovery. I chose the option "wipe data/factory reset" and afterwards rebooted the system, but to no avail. I'm going to try again right now, wiping the cache partition as well.
Edit: Ah! After I wiped the cache my system auto-rebooted and it successfully booted up. Factory settings!
dabs delicious said:
Yes, I'm watching this thread eagerly haha, I would like to fix my phone
So I held power+volume up+home and entered stock recovery. I chose the option "wipe data/factory reset" and afterwards rebooted the system, but to no avail. I'm going to try again right now, wiping the cache partition as well.
Edit: Ah! After I wiped the cache my system auto-rebooted and it successfully booted up. Factory settings!
Click to expand...
Click to collapse
There you go! You have to be careful with Odin because if you do something incorrectly you can totally brick your phone.
Sent from my SCH-I545 using xda premium
Ryno77 said:
There you go! You have to be careful with Odin because if you do something incorrectly you can totally brick your phone.
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
Thanks so much!
help
i tried installing omega 4.3 using twrp it failed, then i couldn't restore my back up. i can get into download mode and try to flash stock rom with odin but it fail's every time and a msg with su rev check fail fused 2 binary 1 appears on the hand set. it also won't even try and boot it just says fw encountered an issue any help would be much appreciated thanks kyle
I used an app suggestion from the guy that wants to get paid for everything to install TWRP on my ATT i527. It installed just fine and ROM Manger shows TWRP as being my recovery system. Only problem is, ATT blocks the recovery and now I can't get to stock recovery.
My biggest problem is I don't know how to to uninstall the TWRP and get back to stock recovery. Any suggestions? Do I unroot and do a factory reset?
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
Ugh. That is a tough one. Know who you are talking about too. Nothing is for sure without a recovery rom. Would hate to see you get caught in a bootloop. That's a pain. Still waiting on my phone. Good luck and let us know how it goes.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Think I may just unroot and hit the factory reset option in the Backup menu.
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
Good luck
2SHAYNEZ
dparrothead1 said:
Think I may just unroot and hit the factory reset option in the Backup menu.
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
Click to expand...
Click to collapse
AFAIK factory reset won't bring back the stock recovery.
Download your device's Rom, flash it, and you'll have your stock recovery back.
unclefab said:
AFAIK factory reset won't bring back the stock recovery.
Download your device's Rom, flash it, and you'll have your stock recovery back.
Click to expand...
Click to collapse
I know you mean well but laughed when I read this. There is no rom for att mega. Hope you figured something out dparrothead1. Worst case is keep twrp, as long as phone is okay, it shouldn't hurt anything. At least, until we get a rom for this thing.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
I would guess you could flash twrp through Odin with the att version but don't mark my words
2SHAYNEZ
azpatterson3 said:
I know you mean well but laughed when I read this. There is no rom for att mega. Hope you figured something out dparrothead1. Worst case is keep twrp, as long as phone is okay, it shouldn't hurt anything. At least, until we get a rom for this thing.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
Yeah az, I had second thoughts about doing the factory reset. I will just keep the TWRP until someone breaks out the bootloader.
The only reason I wanted the stock recovery was to see what this update is all about. The update d/l'ed fine and was going to install but it need stock recovery....I keep hitting the "unauthorized software has been detected... .turn off your phone and take to nearest store". I don't think being rooted has anything to do with it.
I think that sooner or later our phone will be figured out. But I have to tell you. With being rooted and being able to get rid of some bloatware, and with Nova Launcher, I'm really happy with this big assed phone! Sure, I miss some of the customization, but I hated PA and some of the other overloaded roms.
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
Maybe you could find stock recovery to reflashing it back... I'm not sure though if stock recovery from i.e. I9205 ROM couldn't brick your phone...
Dparrothead1 I received the update message yesterday but clicked out of it in error. I don't know what its for either. Suppose I'll google it in a few. I tried updating from settings and get an error saying update was interrupted.
D's Mega 6.3 ♥★♥ sgh-i527
I tried updating my rom and my phone will not boot. I cannot get past the samsung splash screen showing me the unlock icon. I have tried installing a different recovery, wiping everything, restoring from a backup from my SD card... no luck. I have been reading on here, http://forum.xda-developers.com/showthread.php?p=30386309 and it kind of sounds like my issue. sometimes when I try wiping and installing a rom, the phone reboots when it has to write data, eg. installing gapps. no matter the gapps package im installing, kit kat or jellybean, the phone will reboot in the middle of the install. it is almost like the R/W is now corrupt. Anyone have any idea?
We need more info than that etc build you are on, and what build you were trying to update to.
Sent from my SCH-I545 using XDA Premium 4 mobile app
same problem !!PLEASE HELP!!
I have the same problem. I upgraded my S4 to kikat a week ago using this method http://forum.xda-developers.com/showthread.php?t=2726868 worked fine. then i lost my phone at the park after about a couple hours trying to call it and find it a kid answered the phone. he wouldn't help me get it back and said he was gonna keep it and wipe it. i filed a police report and a few days later they got my phon back. but now its stuck in a boot loop on the unlock custom splash screen. the kid that took had my phone was only 8 years old. is there anything i can do to get my phone working again?
Blaymon said:
I have the same problem. I upgraded my S4 to kikat a week ago using this method http://forum.xda-developers.com/showthread.php?t=2726868 worked fine. then i lost my phone at the park after about a couple hours trying to call it and find it a kid answered the phone. he wouldn't help me get it back and said he was gonna keep it and wipe it. i filed a police report and a few days later they got my phon back. but now its stuck in a boot loop on the unlock custom splash screen. the kid that took had my phone was only 8 years old. is there anything i can do to get my phone working again?
Click to expand...
Click to collapse
Your best bet is to just Odin the NC5 stock firmware back on there then. You can try the no wipe first.
Sent from my SCH-I545 using Tapatalk
---------- Post added at 11:55 AM ---------- Previous post was at 11:53 AM ----------
Here
http://forum.xda-developers.com/showthread.php?t=2735172
Sent from my SCH-I545 using Tapatalk
thanks
Mistertac said:
Your best bet is to just Odin the NC5 stock firmware back on there then. You can try the no wipe first.
Sent from my SCH-I545 using Tapatalk
---------- Post added at 11:55 AM ---------- Previous post was at 11:53 AM ----------
Here
http://forum.xda-developers.com/showthread.php?t=2735172
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Thank you so much my phone works again. By any chance do you know if there is a way i can get rooted again if not that's OK i am happy my phone works
Blaymon said:
Thank you so much my phone works again. By any chance do you know if there is a way i can get rooted again if not that's OK i am happy my phone works
Click to expand...
Click to collapse
Well there are some partial downgrade methods on here which require a few files and Odin again. I haven't done it myself and I've seen some have no issues at all with it and some have had nothing but issues.
Sent from my SCH-I545 using Tapatalk
ugh. im having the same issue. Installed NC5 today from a clean install on my MK7 phone that was running NC2.
It installed and booted up fine. I installed some apps and rebooted. Now stuck on the Samsung logo with blinking blue led light. Can't get into recovery.
I have a note 2 that I kept stock for a long time. And decided to root it about a week ago. I used the latest casual one click root. And it seemed all dandy initially until i went between a few different roms and it decided it wanted to shut off randomly and not boot back up past the note 2 screen on its own. But the odd part was it booted while connected to the wall or to the computer. So I flashed to 4.1.2 stock via odin and the issue still remains. I can only use it fine on charger. Is there something else im missing on flashing back to stock?
Sent from my SCH-I605 using XDA Free mobile app
Hmm when you installed 4.3 did you do so wiping everything could be an app causing the problem. Try it from brand new with no apps installed and see if that helps. Could be also a radio issue as well.
Sent from my XT1060 using Tapatalk
Yeah I wiped everything. Actually used odin twice to revert to stock 4.1.2. I tried a few cm nightlies before it began. Is there anything else I should flash on top of whats already been done?
Sent from my SCH-I605 using XDA Free mobile app
mddcflimsreal said:
Yeah I wiped everything. Actually used odin twice to revert to stock 4.1.2. I tried a few cm nightlies before it began. Is there anything else I should flash on top of whats already been done?
Sent from my SCH-I605 using XDA Free mobile app
Click to expand...
Click to collapse
I've found that even after using ODIN to go back to stock 4.1.2, that there's still leftover data on the phone from custom ROM's. I've read where others had the same issue. I don't know why Odin doesn't seem to fully wipe everything ... but this has been my personal experience.
The way I've fixed this (and all this may not be necessary).. . is that after Odin'ing back to stock 4.1.2, I boot into stock recovery, then do a full factory reset and wipe cache. Then I booted into the stock Rom and used the bypass setup trick (touch the left side of the screen right above Emergency... then right side, then left, then right again, and then volume up... this should bypass setup to save time).
Then went into phone's settings and performed a factory reset from within the stock Rom too...
Finally... (because I'm a bit OCD... so this is probably not necessary), but I ODIN'd back to stock 4.1.2 one more time and then proceeded with using CASUAL again to root /unlock the bootloader).
I know this is a pain in the butt... but this has worked for me. Maybe others will have some better suggestions.
(Edit : Forgot to mention that if you're not wanting to return to stock to start over again... check out this thread (http://forum.xda-developers.com/showthread.php?p=53624921) on how to flash a stock recovery for the purposes of doing a proper data wipe... then can you odin your custom recovery back to the device without having to fully restore to stock... this can be a real time saver. Please make sure to thank the OP for the helpful info).
So in the end I tried to reset from stock recovery and wipe cache. Than do a reset from the settings and the issue presisted. But now I have root and recovery as well. So I may give a rom a try.
Sent from my SCH-I605 using XDA Free mobile app
mddcflimsreal said:
So in the end I tried to reset from stock recovery and wipe cache. Than do a reset from the settings and the issue presisted. But now I have root and recovery as well. So I may give a rom a try.
Sent from my SCH-I605 using XDA Free mobile app
Click to expand...
Click to collapse
This is totally a guess, but I'm thinking that you may have a battery problem... and it's just a coincidence that these problems started happening around the same time that you rooted. You may try replacing the battery to see if that fixes things.... (you can get one pretty cheap off ebay or Amazon).
Yeah thats odd. I had bought another battery from a phone store I use to work at and have no issues now, back on 4.1.1 rooted.
Sent from my SCH-I605 using XDA Free mobile app
mddcflimsreal said:
Yeah thats odd. I had bought another battery from a phone store I use to work at and have no issues now, back on 4.1.1 rooted.
Sent from my SCH-I605 using XDA Free mobile app
Click to expand...
Click to collapse
Cool. Hopefully you'll have no more problems with it for a while.
:thumbup: