I have read around and I have seen some that still have the normal Bootloader when starting their device. Mine however does not. Mine simply says Samsung with an unlocked padlock. Why? Since I ordered mine later then others does that mean mine is different? It does seem to do things the others can't. And I'm not sure they are related but some examples are no issues with twrp, generally takes flashing "better". It also doesn't seem to have as many issues backing up or restoring, etc. I'm just guessing. Anyone know the truth of it? Why does mine say unlocked when so many others don't? And IS it unlocked, or just saying it is? Ideas?
You have a custom recovery. It is normal behavior.
Sent from my Nexus 7 using Tapatalk HD
I have a custom recovery installed and mine does not show the unlocked symbol. I think it has to do with the ROM you are running as well.
Sent from my SCH-I545 using Tapatalk 4 Beta
A custom recovery or kernel is supposed to trigger it. The behavior isn't entirely consistent, however.
Sent from my SCH-I545 using Tapatalk 4 Beta
Yep...sometimes it comes back and I have no idea why. Before scrosler posted the optical reader fix, I was pushing files trying to get it to work and boom...I suddenly had it again after maybe two weeks of not having it. I then changed ROMs and kernels again, and a reboot later it was gone again.
Sounds weird, but try reflashing your recovery IN your recovery. Get a flashable zip image of the recovery and flash it. If you are a TWRP user there is a .2 flashable zip in the thread. The first time I got rid of it was when I switched to CWM when .3 TWRP was acting up.
I've had this 4-5 times now, with various ROMs, tried CM10.1, 10.2 most recently. Basically the phone randomly stops booting, I can get to the recovery fine, but booting to system gets stuck on the Galaxy S4 Logo screen. Tried dalvik / cache wipes, permission fix, nothing helps.
Firstly, unless I completely wipe data (full wipe including /data/media), I can't seem to be able to install a new ROM. If I dirty flash everything works fine, but if I do a factory reset, I will get stuck on the logo at boot. Then even after I have successfully installed a ROM, I will sometimes randomly get stuck on reboots, and nothing but another full wipe will fix this. Is this an issue with the TWRP recovery? or is my internal memory fudged and getting corrupt ?
edit: See my post here for details on what I've found so far, I may have fixed the problem but needs more testing http://forum.xda-developers.com/showthread.php?t=2397438&page=2
TWRP!!!!
SellswordShev said:
I've had this 4-5 times now, with various ROMs, tried CM10.1, 10.2 most recently. Basically the phone randomly stops booting, I can get to the recovery fine, but booting to system gets stuck on the Galaxy S4 Logo screen. Tried dalvik / cache wipes, permission fix, nothing helps.
Firstly, unless I completely wipe data (full wipe including /data/media), I can't seem to be able to install a new ROM. If I dirty flash everything works fine, but if I do a factory reset, I will get stuck on the logo at boot. Then even after I have successfully installed a ROM, I will sometimes randomly get stuck on reboots, and nothing but another full wipe will fix this. Is this an issue with the TWRP recovery? or is my internal memory fudged and getting corrupt ?
Click to expand...
Click to collapse
I'm having the same [email protected]#$%^& problem!!!! you're using TWRP aren't you?
i finished reading your post after I was done and saw that you ARE using TWRP...
thepianoman77 said:
I'm having the same [email protected]#$%^& problem!!!! you're using TWRP aren't you?
i finished reading your post after I was done and saw that you ARE using TWRP...
Click to expand...
Click to collapse
yep I was on TWRP 2.5.0.2, I just read that its got some stability problems with /data, just flashed v2.6 hopefully this fixes it
SellswordShev said:
yep I was on TWRP 2.5.0.2, I just read that its got some stability problems with /data, just flashed v2.6 hopefully this fixes it
Click to expand...
Click to collapse
oh dude.... I was on v2.6... I think we have an issue.
That is why I use cwm. Been using it for 3+ years on 4 different devices. Never have I had one problem with it.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
That is why I use cwm. Been using it for 3+ years on 4 different devices. Never have I had one problem with it.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
i had a very bad experience with CWM... never using it again man.... no way.
thepianoman77 said:
i had a very bad experience with CWM... never using it again man.... no way.
Click to expand...
Click to collapse
Lol ok :thumbup:
Sent from my SCH-I545 using Tapatalk 2
I've been using TWRP too. I panicked last night when I couldn't boot at all. I couldn't even get to recovery. I then tried the no wipe odin without luck. I finally got the stock odin image to work but I've been having serious issues with booting on this phone since I got it this weekend and it could be TWRP I suppose. I was using it on my note 2 with no issues. Very strange. I'm back to stock and running fine now.
Sent from my SCH-I545 using xda premium
Still having odd issues with TWRP after updating to 2.6, getting stuck on boot as before, and sometimes flashing a ROM will just fail and the data partition becomes read only, and I can't push anything to it till I reformat /data.
Going to try CWM today, really hope this is just a recovery issue. Are there any tests to check the health of on board memory? I am really hoping I don't have bad hardware here.
Im having the same issue just made a thread fir it guess I will delete since I found this. Hope someone figures it out. What root/ recovery method did you all use. Was it the auto script?
Sent from my SCH-I545 using xda premium
ruffneckZeVo said:
Im having the same issue just made a thread fir it guess I will delete since I found this. Hope someone figures it out. What root/ recovery method did you all use. Was it the auto script?
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
Root / recovery methods will be the same for everyone, regardless of what guide / thread you followed, in the end you will have a loki-patched recovery and kernel, as thats the only way to run unsigned images on these phones. Whats relevant here is which recovery and kernel you are using, as these are the only 2 things that could effect errors in the boot logo state (aka freezes before the ROM boot animations kick in). Ive been looking through various ROM threads of people reporting this issue and its pretty widespread, and usually is linked to recoveries rather than ROMs. If you can post your recovery + ROM here that would be helpful. Here is what I've done so far:
I was initially on TWRP 2.5.0.2, which had possible bugs that could corrupt /data, leading to failed flashes, and being unable to read/write from /data entirely (including /sdcard). After switching to 2.6.0.0 I was still getting stuck on the boot animation. (All of this running the CM10.2 ROM with the stock kernel here http://forum.xda-developers.com/showthread.php?t=2384470). Note I did not do a full wipe after switching to 2.6.0.0, so that recovery MAY still be ok if someone wants to test it out.
I am now running CWM (official installed off ROM Manager). After flashing this I did a full re-format (/system, /data (including /data/media), etc.). And so far I haven't had any problems, going to do some more fiddling / flashing tonight to try and see if its really fixed, but I know for sure that atleast the reboot bug is gone.
So my advice is to flash the official CWM recovery, do a full re-format using that recovery, and then re-install your ROM.
I had that same /data issue with TWRP. It worked perfect for a few months and then suddenly it happened. I enjoyed TWRP for the 10 minute backups and restores, but i'd rather put up with CWM's 30 minute backup and restores if that will mean it wont happen again. Currently running PhilZ Touch Recovery and its been perfect so far!
Monkz said:
I had that same /data issue with TWRP. It worked perfect for a few months and then suddenly it happened. I enjoyed TWRP for the 10 minute backups and restores, but i'd rather put up with CWM's 30 minute backup and restores if that will mean it wont happen again. Currently running PhilZ Touch Recovery and its been perfect so far!
Click to expand...
Click to collapse
Have you tried any 4.3 ROMs with the PhilZ recovery? There seem to be some issues there. Still that recovery may be a good solution for those on 4.2 having this problem. I'm gonna try and loki patch the official CWM touch tonight if I don't run into this bug again, using the volume buttons is so bloody painful lol.
SellswordShev said:
Have you tried any 4.3 ROMs with the PhilZ recovery? There seem to be some issues there. Still that recovery may be a good solution for those on 4.2 having this problem. I'm gonna try and loki patch the official CWM touch tonight if I don't run into this bug again, using the volume buttons is so bloody painful lol.
Click to expand...
Click to collapse
None of my ROMs are 4.3, but i know the one i'm using is soon to be updated, so i will know if it works or not when it gets updated to 4.3. But no issues on 4.2.2 ROMS as of yet with PhilZ.
Monkz said:
None of my ROMs are 4.3, but i know the one i'm using is soon to be updated, so i will know if it works or not when it gets updated to 4.3. But no issues on 4.2.2 ROMS as of yet with PhilZ.
Click to expand...
Click to collapse
is PhilZ a recovery?
thepianoman77 said:
is PhilZ a recovery?
Click to expand...
Click to collapse
Yes its a custom build of CWM maintained by an xda dev here http://forum.xda-developers.com/showthread.php?t=2322675
Im still having the issue with philz. Everything was fine for the first 4-5 weeks. Now about every 3rd reboot or if battery dies I have to wipe data and nandroid. Im running stock with several tweaks. Going to try and odin restore to stock re root snd install cwm tonight and see if that helps will report back
Sent from my SCH-I545 using xda premium
Alright, I'm almost 99% sure this problem is gone after I switched to the official CWM. I've tried everything from restoring nandroids to flashing TWiz / AOSP 4.2 and 4.3 ROMs, everything boots and reboots and /data is no longer getting corrupt. I also loki patched the official CWM touch recovery (the one on their site is not patched), and flashed + used it successfully. Its pretty simple to do this, just follow the guide here: https://github.com/djrbliss/loki and use this recovery: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.3.2-jfltevzw.img
The only issue I've been having is that when I reboot to recovery, it sometimes gets stuck and I have to do a battery pull and go back into recovery.
Sent from my SCH-I545 using Tapatalk 4
I'm having the same issue on TWRP 2.6. Tried with multiple ROMs. Everytime I reboot I have to format /Data. So frustrating. I will try CWM now.
After installing the unofficial CyanogenMod 11 build, whenever I try to boot into TWRP it hangs at the logo.
I've went back to stock and reflashed the latest TWRP via Odin but it refused to go past the "teamwin" screen.
I tried different versions of TWRP and nothing works. My SD Card is not detected either; I don't know if that's related.
I'm not sure where else to go from here.
You can try the version of TWRP before the current one, read somewhere that a few people where having problems with latest version. Might help.
Sent from my SM-N900P using XDA Premium 4 mobile app
tonyevo52 said:
You can try the version of TWRP before the current one, read somewhere that a few people where having problems with latest version. Might help.
Click to expand...
Click to collapse
I'll give it a try and update with results.
EDIT: Didn't work. Got stuck on the "RECOVERY BOOTING....." screen with nothing coming up.
Just flashed 2.6.3.0 and got stuck at the splash screen again.
Read through the TWRP feed, might something, or someone who can help.. http://forum.xda-developers.com/showthread.php?t=2471564
Sent from my SM-N900P using XDA Premium 4 mobile app
Not sure what happened but my after my Note 3 detected my SD Card, recovery started working again.
So I've tried researching this slight issue and I have seen a lot of different solutions but none of them apply to my particular problem. My phone works just fine when booted regularly and charges just fine. The only time I'm having an issue is if I boot into recovery. I just installed twrp 2.7.0.3 and tried to reboot in order to flash supersu. No dice. I've tried rebooting into fastboot and reflashing and I've tried the M8 toolkit. Reflashing works, but still won't boot to recovery and the toolkit just hangs trying to flash the file. I think that's where my issue lies. I waited 19 minutes and eventually closed the program and just rebooted. I'm thinking this caused an issue and corrupted my recovery but i figured reflashing would solve this.
I was wondering if someone could clarify this for me, in which i'll just sit tight and wait until an ruu releases and stick with stock sense. The phone works perfectly so I can deal for a little while. I was just hoping to move to the GPe rom and get xposed running on it.
Thanks yall. I'll keep searching until I have to go to work and if I find a solution before anyone responds I'll update this post so it can be locked.
I would make sure you adb files are up to date, and try flashing philz recovery instead.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
HolyAngel said:
I would make sure you adb files are up to date, and try flashing philz recovery instead.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Are you using philz instead? I flashed twrp and it's very buggy. Did you fastboot flash recovery etc...? How can I install philz over twrp?
Thanks
Sent from my HTC One_M8
yeah im using philz, have been since it came out as i thought the same about twrp, tons of issues.
definitely 'fastboot flash recovery philz_touch_6.25.5-m8.img'
It'll apply itself right over your current recovery no problem :good:
pokedroid said:
So I've tried researching this slight issue and I have seen a lot of different solutions but none of them apply to my particular problem. My phone works just fine when booted regularly and charges just fine. The only time I'm having an issue is if I boot into recovery. I just installed twrp 2.7.0.3 and tried to reboot in order to flash supersu. No dice. I've tried rebooting into fastboot and reflashing and I've tried the M8 toolkit. Reflashing works, but still won't boot to recovery and the toolkit just hangs trying to flash the file. I think that's where my issue lies. I waited 19 minutes and eventually closed the program and just rebooted. I'm thinking this caused an issue and corrupted my recovery but i figured reflashing would solve this.
I was wondering if someone could clarify this for me, in which i'll just sit tight and wait until an ruu releases and stick with stock sense. The phone works perfectly so I can deal for a little while. I was just hoping to move to the GPe rom and get xposed running on it.
Thanks yall. I'll keep searching until I have to go to work and if I find a solution before anyone responds I'll update this post so it can be locked.
Click to expand...
Click to collapse
Seems like every problem in here is when someone uses a toolkit. IMO it is easier just to use the commands. There is nothing wrong with twrp as most people including myself are using it flawlessly. Download fresh copy of twrp. Make sure you get .img file, not .zip. Boot your phone, plug in and type "adb reboot bootloader" it will reboot to fastboot, if not, you do not have newest adb drivers, get this fixed before moving on. once in bootloader type "fastboot reboot-bootloader" this will just reboot your boot loader and let you know fastboot is working. If not fix this. next move to your directory with twrp and type "fastboot flash recovery twrp***.img" should only take 5 seconds. next type fastboot reboot to make sure system is still booting. Then type "adb reboot recovery" and it should go to twrp. Make sure you are getting the UL_CA twrp and not the whl. whl is for sprint and will not work. let me know. UL_CA is not available on official site. search the xda forums for it.
I actually tried the commands first and couldn't get it that's why I tried the toolkit. That's actually what ended up working for me though, but at least I'm good to go! I should have updated this a few days ago but forgot lol this thread can be locked if a mod wants to. Thanks all
Sent from my HTC One_M8 using Tapatalk
HolyAngel said:
yeah im using philz, have been since it came out as i thought the same about twrp, tons of issues.
definitely 'fastboot flash recovery philz_touch_6.25.5-m8.img'
It'll apply itself right over your current recovery no problem :good:
Click to expand...
Click to collapse
Which version of the recovery did you download? I can't find an AT&T version . Just regular M8 version. Just wanna make sure
Sent from my HTC One_M8 using Tapatalk
Z51 said:
Which version of the recovery did you download? I can't find an AT&T version . Just regular M8 version. Just wanna make sure
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
The regular m8 version in original android development ^^
Sent from my HTC One_M8 using XDA Premium 4 mobile app
I'm trying to use TWRP to update to a new cm12 nightly, but every time I select the zip and try to flash it, TWRP crashes and reboots. Is there something I'm missing? It's probably just a noob mistake... For example I only today figured out how to get TWRP to cooperate with encryption and my pattern lock on boot up, hah. I thought it wasn't mounting storage because something was corrupted. Anyways, thanks for any suggestions you can give.
What version of twrp are you using?
Sent from my Nexus 5 using XDA Free mobile app
I have the same issue. It is only with 5.1 Android and I am using 2.8.5 TWRP
Sent from my VS985 4G using Tapatalk 2
I had the problem this afternoon. I just tried it again and it worked. Didn't change anything.. never had problems like this on any other Nexus device. Creepy.
jd1639 said:
What version of twrp are you using?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
2.8.5.0. But I did some more tinkering today and eventually solved my problem. Here's to help you others who saw the same thing: I tried using progressively older versions of TWRP to see if they're used work, until version 2.8.2.1 I think. At that version, instead of crashing, it gave me an error that my zip file was corrupted. I deleted the zip and downloaded it again, switched back to version 2.8.5.0, and everything worked. (except for the Rom, which had bugs that made it unusable, but at least it flashed successfully and booted lol). Hopefully my experience can help someone else now.
I'm having issues with twrp hopefully I found the right thread. It shows no storage available? I'm trying to flash CM. Thanks