Safestrap/not active?? - AT&T Samsung Galaxy S 5

Safestrap will not activate safe mode on my G900A anymore. Was working fine and then all the sudden I get the disable screen on reboot.
Sent from my SAMSUNG-SM-G900A using XDA-FORUM, powered by appyet.com

m4tchb0x87 said:
Safestrap will not activate safe mode on my G900A anymore. Was working fine and then all the sudden I get the disable screen on reboot.
Sent from my SAMSUNG-SM-G900A using XDA-FORUM, powered by appyet.com
Click to expand...
Click to collapse
same thing with mine. when i install safestrap the recovery installs fine but the safe mode says inactive. would that be the reason why i cant mount system in twrp?

Same here. I can check the system mount box but when I reboot same thing... inactive safe system. This all happened after I did a mod on TouchWiz. Apk. I restored to backup but still same results. I even reinstalled busybox and safestrap, still won't activate safe system.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app

Related

Phone boots straight into CW Recovery?

When I restart my phone it boots right into CW recovery. I tried to deodex but it didn't go through. Once in CW recovery I can hit restart and it loads up fine. Any reason this is happening or how to fix it?
Sent from my DROIDX using XDA App
DrewDanger said:
When I restart my phone it boots right into CW recovery. I tried to deodex but it didn't go through. Once in CW recovery I can hit restart and it loads up fine. Any reason this is happening or how to fix it?
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Try following this thread and see if it helps:
http://forum.xda-developers.com/showthread.php?t=805031
DrewDanger said:
When I restart my phone it boots right into CW recovery. I tried to deodex but it didn't go through. Once in CW recovery I can hit restart and it loads up fine. Any reason this is happening or how to fix it?
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Do this happen everytime... or just that one time when you tried to deodex??
I'm asking because the modded recovery is made so that if your phone never COMPLETELY boots... it will reboot to recovery the next time your phone restarts.
When it does restart COMPLETELY, it will restart as normal.. until it fails to boot again. (Which no one ever wishes to happen lol)

Is my Nexus completely dead?

Long post but can't really shorten it.
32GB wifi Nexus, rooted and was running Liquid Smooth ROM and Motley kernel, went to update the ROM to rc9 version ,anytime I updated previously I never done full wipe unless using different ROM, anyway flashed the ROM and the gaaps with it and rebooted, immediately and prompted to me to use either apex or Holo HD I choose Holo HD got error saying system ui not responding, tried apex and got the same.
I was on the main screen but couldn't access it, yet I could pull down and enter into settings, everything else looked to be ok, so rebooted back to recovery and tried fixing permission, rebooted and got the same so I though I'll be just restore my nandroid backup, to my astonishment all the data had been wiped, I didn't do a wipe at all so I'm baffled how this happened.
Anyway I done a factory reset and rebooted and went through the setup, got the same system ui not responding, went to settings which could still access, apps and un installed both Apex and Holo HD noticed that Liquid Smooth rc9 had installed but instead of showing the cm kernel it still showed motley kernel.
Back to recovery, factory reset twice, wiped cache and dalvik, rebooted, went through set up process, same system ui error again, went to settings, erased all data, tablet rebooted, set up process same again, system ui, so I'm getting worried so back to recovery and this time I selected format system, data and sd, card and now I think I've completely fuc#ed it up as it just hangs at the Google screen and has stayed like that for over 30 minutes.
Previously asides from the occasional force close issue in the 2 months I've had the Nexus not really had a problem with it and whilst I'm no developer or techy geek I'm certainly no noob when it comes to this type of thing but I'm very concerned now and hoping someone can be of assistance as I sold laptop and primary just use my Nexus (and Galaxy S3)
Thanks
Sent from my GT-I9300 using xda app-developers app
Strange.. But I didn't understand well, after wiping /system, did you flash the ROM back ?
I think you should flash 4.2.1 factory image using toolkit or whatever, then root etc..again
No all the data had been wiped this is what is baffling me, I didn't do a factory reset I just flashed the ROM and gaaps, as I said initially it was the system ui error I was getting but I think I've fucjed it up by formatting the system, data and sd card as all I can see now is the Google screen at boot, I can still get into clock work mod recovery but I've exhausted all avenues as it were, is there any hope I can get it back working again?
Sent from my GT-I9300 using xda app-developers app
j3r3myp said:
Strange.. But I didn't understand well, after wiping /system, did you flash the ROM back ?
I think you should flash 4.2.1 factory image using toolkit or whatever, then root etc..again
Click to expand...
Click to collapse
Is that Mr skips Nexus 7 toolkit?
Sent from my GT-I9300 using xda app-developers app
Download Google Stock Image and Flash the System.img File ...Tablet will be fine after that.
manasgirdhar said:
Download Google Stock Image and Flash the System.img File ...Tablet will be fine after that.
Click to expand...
Click to collapse
Thanks can you give me more instructions how I go about doing that, any links, etc
Sent from my GT-I9300 using xda app-developers app
jonny68 said:
Is that Mr skips Nexus 7 toolkit?
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Yes ! Really easy to use. You'll just have to put the tab into fastboot mode give it a try I'm pretty sure it will solve everything and you'll start back with good bases as it is full stock !
Sent from my Nexus 7 using Tapatalk HD
Cheers but I don't see anything in clockwork mod recovery for fastboot mode, I'll go to an Internet cafe tomorrow and do it if I could just get specific instructions.
Thanks again folks for your assistance
Sent from my GT-I9300 using xda app-developers app
jonny68 said:
Cheers but I don't see anything in clockwork mod recovery for fastboot mode, I'll go to an Internet cafe tomorrow and do it if I could just get specific instructions.
Thanks again folks for your assistance
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Hold power and volume up and down all for like 10-15 seconds. Tablet will boot into bootloader/fastboot mode
Sent from my Nexus 7 using xda app-developers app
malikadnanm said:
Hold power and volume up and down all for like 10-15 seconds. Tablet will boot into bootloader/fastboot mode
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
That is what I've always done but all I can see is - start - restart bootloader - recovery mode - power off, and I cannot see anything for fastboot mode (unless I'm going blind)
Sent from my GT-I9300 using xda app-developers app
jonny68 said:
Thanks can you give me more instructions how I go about doing that, any links, etc
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
First Download and install the fastboot drivers...Download the stock Image here:-
https://developers.google.com/android/nexus/images
then hold volume-(Down) Button and while holding the Button power on the device..it will take you into the bootloader. Now conne4ct the nexus to your PC...Now extract the file you downloaded (the Stock image)..keep extracting the files till you get the system.img file.Use fastboot to flash that(the command):
fastboot flash system system.img
Boot into fast boot, push a stock image. Ta da. Easy stuff. The basics.
Sent from my A100 using xda app-developers app
manasgirdhar said:
First Download and install the fastboot drivers...Download the stock Image here:-
https://developers.google.com/android/nexus/images
then hold volume-(Down) Button and while holding the Button power on the device..it will take you into the bootloader. Now conne4ct the nexus to your PC...Now extract the file you downloaded (the Stock image)..keep extracting the files till you get the system.img file.Use fastboot to flash that(the command):
fastboot flash system system.img
Click to expand...
Click to collapse
Right cheers ill give this a go tomorrow pretty new to the Nexus used to Samsung
Sent from my GT-I9300 using xda app-developers app
jonny68 said:
Right cheers ill give this a go tomorrow pretty new to the Nexus used to Samsung
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Ah..We were all new to this once..you will get the Hang of it..If you need further help please do let me know.Always happy to help.

[Q] Unable to make changes

I am unable to make permanent changes to my T679 Exhibit II and need some help. Here are the symptoms.
1. Any changes in Settings go back to previous settings after a power on/off cycle.
2. When attempting Factory Data Reset, the phone just turns off or seems like it's off (display is black).
3. Attempting to enter Stock Recovery results in the same black screen after the Samsung logo is displayed.
4. Tried flashing CWM 6.0.1.2 with ODIN. Although I get a Pass indication, I can't get into any recovery mode.
5. Tried flashing stock UVLG3 with ODIN. Although I get a Pass indication, The old Rom remains unchanged.
Otherwise, the phone seems to operate normally. I can make and receive calls, gps, bluetooth, and wifi works. Files written to an external SD card are okay. Files written to the internal SD disappear after a power on/off cycle.
Any ideas?
Hmm Odin is hit and miss, sometimes I have no problems other times it won't work at all
Sent from my SGH-T679 using xda app-developers app
Tried ODIN again
Thanks for looking into the problem.
I tried UVLG3 with Odin again. Although, it says Passed, I'm not sure anything is getting written. Everything is finished writing at about 20 seconds after starting and then the phone is reset. At this time the phone's screen goes black. I'm not sure if the phone is off or what's happening. If I press the power switch, I'll get the Samsung logo and a normal boot up after about 13-14 seconds. On a regular power on sequence, I get the Samsung logo after about 5 seconds.
Keep trying cwm via Odin, I know I only had to do cwm once and it worked fine. Also make sure you have the proper drivers installed, a quick search of Google will help with that.
Sent from my SGH-T679 using xda app-developers app
Odin again
I tried Odin again (many times) with a different tar file. With the new file, the time to complete all the writing takes approximately 4.5 minutes vice 20 seconds with the old file. There must be a glitch with the original tar or ops file. The file sizes are about the same, 600MB. The results are the same also... no change to the ROM. It's like the ROM is write protected. Even the clock starts off at the same time every time I power up the phone. Anyone have any ideas?
I would just do cwm the Odin stock is possible corrupt.
Sent from my SGH-T679 using xda app-developers app
Odin/cwm
tazmaniondvl said:
I would just do cwm the Odin stock is possible corrupt.
Sent from my SGH-T679 using xda app-developers app
Click to expand...
Click to collapse
Do you mean flashing CWM with Odin? I've tried many different combinations but nothing works so far. The main rom doesn't change and I get a black screen when I go into recovery. Funny thing... when I'm in the black recovery screen, my computer will sense that the phone is there if I plug in the USB cable. Also, when I tried ADB, reboot or reboot recovery takes me to the black screen.
The only screens I get are download, memory dump, and the normal 2.3.6 operating system. No permanent changes can be made to the operating system and I can't get into recovery. When I write the CWM zip file to the internal SD, I can see it with my laptop and also with the Files app on the phone. However, the file disappears when I power the phone off and then back on. Like I said before, it's like everything is write protected.
When you are doing cwm via Odin it has nothing to do with your internal SD, you should save the Odin file to your computer, if you follow the instructions on the page you get cwm Odin file, you should have no problem, I just did cwm from Odin and it worked just fine. But if you miss a step you will still get a pass but in reality it failed. If it does not work for you then there is a problem on your device I have never ran into.
Sent from my SGH-T679 using xda app-developers app
Odin
tazmaniondvl said:
When you are doing cwm via Odin it has nothing to do with your internal SD, you should save the Odin file to your computer, if you follow the instructions on the page you get cwm Odin file, you should have no problem, I just did cwm from Odin and it worked just fine. But if you miss a step you will still get a pass but in reality it failed. If it does not work for you then there is a problem on your device I have never ran into.
Sent from my SGH-T679 using xda app-developers app
Click to expand...
Click to collapse
Sorry, I did not mean to say that I was trying Odin by copying the file to the internal SD. I was just trying to illustrate the read only characteristics of the phone. I've done Odin downloads before but the first thing that I tried to revive this phone was to copy the CWM zip over to the phone thinking that I would flash CWM and then reset/reflash the phone with CWM.
Since you can't do cwm flash. That's why I recommend you try cwm via Odin.
Sent from my SGH-T679 using xda app-developers app
Odin/cwm
tazmaniondvl said:
Since you can't do cwm flash. That's why I recommend you try cwm via Odin.
Sent from my SGH-T679 using xda app-developers app
Click to expand...
Click to collapse
I did try it. I thought I mentioned that CWM via Odin only took about 4 seconds to do the write (I didn't).
I would like to mention that one thing does change... the clock/calendar does update (I thought it didn't). It doesn't keep any changes that were made to the phone (manually or automatically via network) before turning it off. I just noticed that when I turned it on today, the date was Aug 17, 2012. Yesterday it was Aug 16. So some changes are being kept.
There is a cwm flashable zip for stock recovery. Why not just use that? After the 2.3.6 update there is really no need for Odin with this phone.
Sent from my SGH-T679 using xda app-developers app
He can't get to recovery at all
Sent from my SGH-T679 using xda app-developers app
Tried something different
I tried to gain root via ADB. I pushed and executed psneuter and also gingerbreak. The two programs seemed to execute (get several lines of messages for each program before stalling), though not to completion. Each one hung after executing partially. The funny thing is after a power off/on cycle, when I use adb again and navigate to the directory that I pushed psneuter and gingerbreak to (/data/local/tmp), the directory is empty. I don't quite understand why all changes made to this phone are just temporary. Any change stays only until the next power off/on cycle. Any ideas?
tazmaniondvl said:
He can't get to recovery at all
Sent from my SGH-T679 using xda app-developers app
Click to expand...
Click to collapse
Just reread thread, my bad. I didn't catch that. Sorry.
Sent from my SGH-T679 using xda app-developers app

[PROBLEM=SOLVED] Unable to flash ROM in CWM

Here is the problem: the phone is only able to boot in to cwm. I dont know what happened, but the system got wiped. The process of flashing a ROM goes well but when i reboot the system is wiped again and it boots into cwm.
Is there a way to solve this problem with the phone only, because i dont have the necessary programs on my laptop to solve this problem in a different way, and i wont be able to download them for another week. I do have adb on laptop but i dont know if it could help the situation.
Sent from my GT-I9070 using xda app-developers app
Try removing the battery then put it back in. Turn it on pressing power and volume up. In recovery choose reboot system.
Sent from my LG-P880 using Tapatalk 4
MilkyJoePD said:
Try removing the battery then put it back in. Turn it on pressing power and volume up. In recovery choose reboot system.
Sent from my LG-P880 using Tapatalk 4
Click to expand...
Click to collapse
Already did that, but the problem is that after reboot there isnt a system to boot into. So it boots in cwm.
Sent from my GT-I9070 using xda app-developers app
It might be different with this phone, but the phones I've had with a blank system didn't boot into recovery, you'd either get a boot loop or just a blank screen.
I've had the recovery boot loop before and the only way to get out of it was to boot into recovery manually (rather than let it boot into it itself). Which meant removing the battery for about 10 seconds, then making sure when you boot into recovery you initiate it before it does itself.
If it is a blank system then I'd suggest just trying to somehow get a ROM on your phone to flash.
Did you not make a nandroid?
Sent from my LG-P880 using Tapatalk 4
I tried to boot into recovery manually, but instead it booted into OS
Sent from my GT-I9070 using xda app-developers app
Recovery limbo solution should be stickied.
How many times will an unnecessary full wipe etc. be advised?
Sent from my LG-P880 using Tapatalk 4

big problem help :(

helly today i installed mclaws cm10.2 rom i is cool but i want to restore to my old rom and i cant gett in to the recovery i tried with quickboot with rom manager with rom toolbox but when i press reboot to recovery the phone just restarts and dont want to boot in to the recovery why is that and how can i fix it
Sent from my GT-I8190 using xda app-developers app
allso i tried trough terminal emulator but same phone reboots only ans starts again normaly and does want to boot in to recovery pls help
Sent from my GT-I8190 using xda app-developers app
Have you tried three button combo? From power off, press Vol+/home/power at the same time, keep pressing untill you're in recovery.
yes i tried it but i get some wierd pixels and phone shuts of and when i want to start i get the same pixels and phone starts normaly and i cant turn of the phone when i hint turn of it self starts again with the same pixels and starts again normaly and works
Sent from my GT-I8190 using xda app-developers app
How did you try with terminal emulator?
su
reboot recovery
Like that?
Why don't you just flash a stock rom with Odin and do the whole thing again (root, etc...)
Enviado desde mi GT-I8190L usando Tapatalk
is there another way to gett in the recovery
Sent from my GT-I8190 using xda app-developers app
HTC-DeSiRe-S-S510e said:
is there another way to gett in the recovery
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
To me it starts to feel like your recovery partition is messed up in some way. Have you tried to reflash recovery?
via odin or is there another way
Sent from my GT-I8190 using xda app-developers app
HTC-DeSiRe-S-S510e said:
via odin or is there another way
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
You can get it through rom manager.
fixed recovery and restorednto my old rom but when i turn off my phone and turn it on again i get the same strange pixels on scrren and than goes samsung logo and phone turns on everithing is ok phone works but what is that and how to fix it
Sent from my GT-I8190 using xda app-developers app
HTC-DeSiRe-S-S510e said:
fixed recovery and restorednto my old rom but when i turn off my phone and turn it on again i get the same strange pixels on scrren and than goes samsung logo and phone turns on everithing is ok phone works but what is that and how to fix it
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
Flash in odin as pda. View attachment i8190-param.tar
I have the same. Only Shotdown and Volume_up+Home+Power get me acces to recovery
Restart to Recovery from system doesn't run recovery
I installed some recoverys few times and again rom (Maclaws CM10.2 from 20131021) and it is still the same.
tomaasz

Categories

Resources