After rooting, I installed safe trap on my razr 912 CDMA, (no bootstrap).
1. Went to safetrap 1.0 recovery, data wipe, safetrap ENABLED and tried installing GUMMY 1.0.0 and gapps.
Tried rebooting but, after pressing the 'search button' key to start the ROM boot, it doesnt show anything , complete blank screen. rebooted few times, factory reset ,etc, didnt help.
2. Went back and DISABLED safetrap, which restored my initial copy of the stock, rebooted and it worked fine, my intial Stock ROM was up and running.
3. I doubted that this was issue with safetrap and not gummy installation; so to check that, I went to safetrap recovery, ENABLED safetrap. DID NOT INSTALL anything else.
Simply rebooted the phone, hoping the stock ROM to boot up since I did not install anything this time.
Result was the same...nothing on the screen....blank screen.
4. I went back and DISABLED safetrap and all was fine. Now stuck with stock ROM cant install new ROMS.
(I have no intention of trying bootstrap, because i did that on earlier Razr while installing Gummy 1.0.0 and it bricked the phone)
Question: it seems enabling safetrap, i am not able to bootup , no matter what. Any solution to this?
Related
I am running Razr ICS 4.0.4 safestrap 3.11.
Problem is when i try to restore a backup that I made, could have just made it 5 minutes ago( does samething to any backups) all that happens is the M logo comes up then the safestrap screen and I hit the button to boot phone normally it just goes to a black screen. I have do the 3 button reset to get back to safestrap. I then have to switch over to the stock rom slot, and that boots fine. I then have to go back into safestrap and delete rom slot 1 and re-create it to be-able to restore any backups. What is going on, what do I have to do to just be able to restore a backup without have to delete the rom slot and recreate it everytime? I made a post on Hashcode site as well. Would love to get this resolved!
Interesting
blackops11252 said:
I am running Razr ICS 4.0.4 safestrap 3.11.
Problem is when i try to restore a backup that I made, could have just made it 5 minutes ago( does samething to any backups) all that happens is the M logo comes up then the safestrap screen and I hit the button to boot phone normally it just goes to a black screen. I have do the 3 button reset to get back to safestrap. I then have to switch over to the stock rom slot, and that boots fine. I then have to go back into safestrap and delete rom slot 1 and re-create it to be-able to restore any backups. What is going on, what do I have to do to just be able to restore a backup without have to delete the rom slot and recreate it everytime? I made a post on Hashcode site as well. Would love to get this resolved!
Click to expand...
Click to collapse
Actually, after I went from Safestrap 2.__ to 3.11, every time I create a new Rom slot and try to Install a ROM into it, I get a black screen on reboot. The only thing that works for me is the stock at this point. I'm worried to revert to the previous Safestrap and some ROM's don't work with anything but the latest Safestrap, so unsure what to do.
Cmar
I got the same problem as your when using the safestrap 3.11. But then I noticed that every developer ask us to wipe before install roms.
I followed, and I succeeded most of my installation. But I still get the black screen randomly, even when I reinstall the rom that boots normal before.
Anyway, you could try wipe all between the time of recreate the rom-slot and install roms.
Hope this will help you!
sweetmeroy said:
I got the same problem as your when using the safestrap 3.11. But then I noticed that every developer ask us to wipe before install roms.
I followed, and I succeeded most of my installation. But I still get the black screen randomly, even when I reinstall the rom that boots normal before.
Anyway, you could try wipe all between the time of recreate the rom-slot and install roms.
Hope this will help you!
Click to expand...
Click to collapse
On my first install of Safestrap 3.11 on Motorola Droid Razr HD, I made a 1gb partition in slot 1, installed Batakang rom and rebooted. Worked fine (except I could only receive, not send sms/mms). Since then nothing has worked. I have even gone as far as factory reset my phone, re-rooted (Motochopper) and Unlocked Bootloader (Motopocalypse), re-installed safestrap, created new rom slot (tried slot 1 and 3) tried installing CM10 and AOKP unofficial builds downloaded from this site, no ammount of wiping before installing works. I can boot to stock rom fine but get black screen when booting into other roms. Holding down power key forces reboot into safestrap again.
I will first delete any ROM slot i created first then Easiest way to fix black screen is to boot to stock rom and select safestrap app open and chose uninstall recovery, reboot and do same thing but this time choose install recovery then reboot, can go back into safestrap now and all will be Good
Some ROMs are messed up like that as far as messaging goes
So up until today I was running this rom: http://forum.xda-developers.com/showthread.php?t=1912596
It was getting really buggy, so I decided to update to the latest CM10.1 nightly. I updated safestrap to the latest version, and I saw that on the changelog for the CM nightlies that the rom could be installed on any slot. For some reason, there was no rom slot 1, even though that's what I had the current rom installed on. I made a backup of the stock rom slot, wiped system/cache/factory reset, and installed CM 10.1 on the stock slot. That didn't boot up. So I tried to restore my backup. My backup of my current rom didn't show up, but the initial stock rom backup that I made when I first rooted the phone showed up, so i wiped everything again and tried to boot from that. On that, the boot animation showed up and went through, but it sat there for a few minutes without booting, so I did a hard reset and went back into recovery. I then made a romslot-1, wiped for precaution, then tried to install the cm nightly. The install went fine, but when I try to boot, the phone just vibrates initially like it's going to boot up, but there is no boot animation or anything on the screen, and it just sits there. Is there anything I can do to get this thing up and running again? I am not at the least opposed to returning it to stock, but I'm not sure if I need to restore to stock ICS or JB, since I'm pretty sure the rom I had running was using the ICS kernel. Here's the link to the rom I just tried to install: http://forum.xda-developers.com/showthread.php?p=39330661&highlight=boot#post39330661
Any help on the matter would be greatly appreciated.
Been getting frustrated over the past day.
Currently am up and running on a backup of Hyperdrive RLS 8.1, but I am afraid to reboot because for all of last night, any backup or clean install of any ROM I flashed would either
1) boot up the first time, but any subsequent reboots would result in stuck at the Samsung Custom Lock screen
2) not boot up at all, stuck at the Samsung Custom Lock screen
When I get stuck at the Custom Lock screen, I do a battery pull and then attempt to reboot into recovery. However, trying to boot recovery would not work (phone reboots itself after briefly showing "booting recovery" every time) until I plugged in the charger and tried to boot recovery (not sure if just coincidence?). Currently running TWRP 2.5.0.2
At this point, the recovery asks for a password (I have never set a password, don't know why this happens?). This prevents me from factory resetting (gives me an operation failed) because I need to "decrypt data" or something along those lines, using a password which I am sure I have never set. The internal storage is apparently unable to mount without decrypting data using a password..?
I found that in the WIPE menu I can perform the FORMAT DATA action which is successful and fixes the decrypt data problem, and I am able to factory reset and then restore a working ROM or install a new one (I tried CleanROM 1.6 with patch to 1.6.5 since it was on my sdcard).
This brings me to this position at the current moment. After formatting and factory resetting, I have done the following with such results:
1) Restoring my STOCK, ROOTED TWRP backup from before my install of Hyperdrive 8.1. Booted up fine, but a reboot gave the same results of stuck at the custom lock screen
2) Installing CleanROM, booted up fine the first time, but got stuck on the first reboot at the first bootup screen (it changed it to the original
Samsung Galaxy S4" instead of the custom lock?). I went back to recovery and went through the same process (decrypt by formatting data, factory reset, restore/install new rom)
3) Restoring my Hyperdrive 8.1 TWRP backup (first backup of the ROM while it was apparently running fine, reboots were normal and no problems yet). I am currently running this right now but have not attempted a reboot because I do not have the time for the next few days to mess around with my phone.
Summary: Stuck at initial boot screen (Custom Lock or Samsung Galaxy S4), TWRP 2.5.0.2 asks for password for decrypt?? & cannot factory reset, able to format data which allows factory reset after, restored Hyperdrive 8.1 backup, currently afraid to reboot in fear of getting stuck again.
Any help or suggestions would be appreciated. I am considering ODIN a stock image and completely starting over, but that will have to wait until the weekend.
Hello all,
By using Safestrap, I wanted to flash a CM 11 Kitkat ROM to my XT912, but I ran into some complications that I will detail below. If anyone can follow what I did and tell me how to get out of this situation, I would be very appreciative.
The very first thing I did was gain root access for my phone. Using this script, http://forum.xda-developers.com/showthread.php?t=2192467, and after a few tries, I was able to root the phone and install Safestrap. But this was an earlier version of Safestrap than what the directions for installing the ROM said, so I then installed the updated version.
After installing Safestrap v 3.65 and installing the recovery, I then using Titanium backup (the free version) and made a backup of all my app data. When I booted into Safestrap, I immediately created a backup of the stock ROM. Then, using this guide: http://forum.xda-developers.com/showthread.php?t=2535920, I created a ROM slot, did the advanced wipe, flashed both the ROM and gapps .zip files, and wiped the Dalvik and the cache for the final time. This is where a problem occurred. After I tried wiping the Dalvik and the cache at the end, Satestrap said that the process had failed. Dumb me decided that it would be a good idea to then boot the phone anyway with the KK ROM selected.
In my phone's current state, it will not boot past the M logo. It can boot into fastboot, but when an option is selected, either the M logo appears again or the screen goes blank. I've tried reflashing the stock ROM using the 2nd option in the script, but every time I do that, the phone says it has a low battery. To try and solve this problem, I tried using this trick to get the phone to charge: http://forum.xda-developers.com/showthread.php?t=1549625, but it hasn't helped. Even after sitting overnight after doing this trick the phone still said low battery when I tried running the script.
Any ideas as to what I did and how I can go about solving it? Thanks for reading my post.
Does anyone know what is wrong here? I wanted to get back to stock by flashing Amazon's stock .bin (changed to .zip) in twrp. I've done this before and had no issues. In twrp I wiped everything and then flashed the .zip. Then I booted into the Amazon OS and everything appeared fine. I'm on 14.3.2.5. For one, I cannot factory reset. After trying to do so, it reboots to the Kindle logo and just permanently hangs there. If I try to update it manually to 14.4.5.5, once again, it just hangs on the Kindle logo. It appears I have no recovery or something. What I don't understand is that I've done this in the past with no issue. Where I am now is that I am able to boot without issue into 14.3.2.5, but cannot update. What can I do?
edit: http://forum.xda-developers.com/showpost.php?p=55759790&postcount=204 fixed it. It restored my stock recovery and I was able to update and factory reset after doing it.