I have Safestrap 3.7.2 and Lollipop rooted installed. I've googled and googled and can't find an answer to this. I booted into Safestrap to try to figure out how to delete an old NC1 backup I made. I hit the reboot/recovery button once. What a mistake. The phone booted into stock recovery. Now when the phone boots, I get a message saying Safestrap is disabled with the options of recovery or continue. Continue does nothing but gives me a blank screen. Recovery takes me into Safestrap, and I can't get the phone to boot back into Lollipop. If I hit reboot/system, I get the same Safestrap disabled screen. If I hit reboot/recovery, I end up in the stock recovery. It says to wait 10 seconds and it will boot, but all I get is a blank screen. I have Lollipop in the stock ROM slot with no other ROMs loaded. HELP!
Well the only thing I could figure to do was to ODIN back to NC2, use Towelroot to get root, install Busybox and Safestrap 3.75, install the OC1 rooted ROM, and reinstall everything via Titanium Backup. This time once I get the phone set up the way I want I will make sure to make a Safestrap backup. What a pain.
Unbelievable. After restoring everything via Titanium Backup, and then booting back into Safestrap to make a backup, I decided to wait and the only thing I did was to power the phone off. I'm getting the same Safestrap disabled message again. I'm not even sure how this is possible.
voigts said:
Unbelievable. After restoring everything via Titanium Backup, and then booting back into Safestrap to make a backup, I decided to wait and the only thing I did was to power the phone off. I'm getting the same Safestrap disabled message again. I'm not even sure how this is possible.
Click to expand...
Click to collapse
Since you're on Lollipop did you flash the OC1 kernel before leaving Safestrap? http://forum.xda-developers.com/showpost.php?p=59666958&postcount=2
Yes. What I have been finding after flashing/reflashing about 10 times today is that if I boot into Safestrap (v. 3.75) even once after flashing the rooted Lollipop Zip (OC1 that you linked to), Safestrap gets disabled. As long as I do not boot into Safestrap, the phone boots fine. Once Safestrap disables, I am dead in the water and can't get back into Lollipop at all. I then have to ODIN back to NC2, root with Towelroot, install Busybox, and then Safestrap to flash back to OC1.
I spent all day on and off messing with this. I'd really be in a fix without Titanium Backup.
voigts said:
Yes. What I have been finding after flashing/reflashing about 10 times today is that if I boot into Safestrap (v. 3.75) even once after flashing the rooted Lollipop Zip (OC1 that you linked to), Safestrap gets disabled. As long as I do not boot into Safestrap, the phone boots fine. Once Safestrap disables, I am dead in the water and can't get back into Lollipop at all. I then have to ODIN back to NC2, root with Towelroot, install Busybox, and then Safestrap to flash back to OC1.
I spent all day on and off messing with this. I'd really be in a fix without Titanium Backup.
Click to expand...
Click to collapse
Only thing I can think of is something in your Titanium backup is messing things up. If you happen to flash all that again (not saying to do) but if you do, I would boot into Safestrap (once you install Lollipop) and flash the OC1 kernel to see if it boots ok. (Before you do the Titanium Backup).
Thank you for the replies. I failed to realize that I needed to extract the lollipop file and then flash the SM-N900A_OC1_Kernel_Safestrap_Installer.zip file contained within AFTER flashing the lollipop file. Yes, I get the stupid award for the day. Duh....
I extracted the file, copied to MicroSD card, and then booted into Safestrap and flashed it. Hopefully things will work correctly now. I feel pretty stupid.
I need help myself.. Every time I try to flash any type of zip I get stuck in safestrap disabled
Related
I've been modding androids, iphones, and windows phones for years now but I somehow ended up to finally brick a phone.
So I was running stock 4.3 rooted on my N900A and decided to install SafeStrap 3.71 in order to upgrade to Knoxraid. I followed this guide (kind of):
http://galaxynote3root.com/att-galaxy-note-3-roms/knoxraid-kitkat-rom-for-att-galaxy-note-3/
Everything went well and I got SafeStrap but I installed the rom to Rom Slot 1 instead of the Stock Rom slot., I rebooted into the regular download mode. Everything went okay with the install but after flashing the ODIN files I noticed that SafeStrap no longer booted to the recovery menu (of course). Knoxraid installed just fine but after booting into the rom I noticed that it would soft-reboot every 20-30 seconds. I couldn't get into Settings>General>Security. I couldn't load any apps because it rebooted too fast. It was basically useless. I booted into recovery mode to try and reload the rom there. Now I just get a black screen on bootup.
I think my saving grace might be that I took a backup of my phone using SafeStrap before I made any changes. However, how can I apply that backup without SafeStrap?
HELP!!
I've done this before and I'm wondering if I can do it again
http://forum.xda-developers.com/showthread.php?t=2559715
Okay I've made some progress. After restoring the original MJ5 ODIN files in the above link, SafeStrap came up after the reboot!!!!!! Now I'm doing a restore.in SafeStrap. I should be all set but I'll update in case anyone else has the same issue in the future.
It worked flawlessly after that. I followed the instructions to the letter and now everything is working perfectly!
Ok, so I tried following the method described here:
http://forum.xda-developers.com/showthread.php?t=2712039
I was on JB. Installed SS 3.71, downloaded the odexed version of UrDroid and odin files.
Procedure I followed:
Booted into SS
Factory reset
Install urdroid - deodexed
Installation failed, zip wouldn't open
Booted back up, downloaded urdroid again - odexed version this time
pulled battery, booted to safestrap
factory reset
install new zip, worked this time
tried booting to download mode with vol down key, didn't work for some reason. just went to SS splash screen then tried to boot
pulled battery, booted SS again, used the reboot menu to get to download mode
followed steps to set up partitions in ODIN, seemed to work fine
Now when I try to boot it just shows me the SS splash screen, then when I let it boot it just goes to a black screen with a solid blue indicator LED.
Next, I tried to verify the MD5 on the UrDroid zip and it didn't match. I downloaded it again, copied it to my external SD, and it then checked out.
Wiped, installed, ran the odin stuff again. Same problem.
I'm guessing the next step is to restore it back to MJ5 using this method: http://forum.xda-developers.com/showthread.php?t=2559715&page=118
Except several of the files linked there are no longer available....
I'm feeling a little panicked now, this is my only phone lol. Can anyone give me a hand?
If you're on MJ5 and If you can access Safestrap recovery, this should work : http://forum.xda-developers.com/showthread.php?t=2619005
andygev35 said:
If you're on MJ5 and If you can access Safestrap recovery, this should work : http://forum.xda-developers.com/showthread.php?t=2619005
Click to expand...
Click to collapse
I thought that once you update to KK, you can't go back to JB... except I don't know if I ever completed the update. I'm not entirely sure how this process even works.
Do you flash the rom, and then the ODIN portion of it prepares your phone for KK?
Boot into safestrap recovery, click reboot, click reboot to recovery (which will boot you into system recovery). Near the top of the system recovery screen it will show you what version of firmware you have. If it's MJ5, then just do a restore within safestrap recovery to the restore files you get from the link I posted earlier.
andygev35 said:
Boot into safestrap recovery, click reboot, click reboot to recovery (which will boot you into system recovery). Near the top of the system recovery screen it will show you what version of firmware you have. If it's MJ5, then just do a restore within safestrap recovery to the restore files you get from the link I posted earlier.
Click to expand...
Click to collapse
First of all, thank you for your help.
In recovery, it just says "Android system recovery <3e>". Then goes down to the options you can select.
Before you posted, I tried installing a MJ5 custom rom (FireNote) in the stock slot and now it successfully boots. Which is certainly an improvement. I tried the same process again with UrDroid and had the same result as before - no boot. Now I'm back on FireNote again.
Since FireNote works fine, is it safe to conclude that the Odin process did not properly prepare my boot system for KitKat, and that is why the KK rom isn't working at all?
Have I stumped XDA?? Haha.
I went over the guide again and can't see anything that I've done wrong, but I certainly could have. Are there glitches in Odin3 with Windows 7 that I should be looking out for or anything?
Another thought: I was attempting to do this with SafeStrap 3.71 installed. I thought that 3.72 should be sideloaded after I had switched to KitKat. Was this incorrect? Should I have started by installing 3.72 in my JB rom?
Well, I just let out a string of bad words.
When I ran Odin it defaulted to my 'return to stock' files even though I ran it from a completely different folder... and I didn't realize it.
I'm guessing using the right files will resolve this problem.
Wow, I'm an idiot.
steveh_131 said:
Well, I just let out a string of bad words.
When I ran Odin it defaulted to my 'return to stock' files even though I ran it from a completely different folder... and I didn't realize it.
I'm guessing using the right files will resolve this problem.
Wow, I'm an idiot.
Click to expand...
Click to collapse
I wouldn't say you're an idiot. You're human!
TWRP Recovery
Rooted
Xposed framework installed
Been getting bugged for the 4.4.4 update, and I wanted to open and look at the ZIP out of curiosity, so I hit install now, thinking it still needed to download... but turns out it didn't, and rebooted right away.
So now I'm stuck in a boot loop of sorts.... it boots, and loads up Android, and I can use the phone, but after about 20-30 seconds it reboots into recovery.
Is there an easy way out of this without wiping everything? Preferably a modded OTA that I can install for the 4.4.4 update.
Check out the thread under general tab to use RSD Flasher or House of Moto to install the 4.4.4 FXZ
DB's Moto X
coreno said:
TWRP Recovery
Rooted
Xposed framework installed
Been getting bugged for the 4.4.4 update, and I wanted to open and look at the ZIP out of curiosity, so I hit install now, thinking it still needed to download... but turns out it didn't, and rebooted right away.
So now I'm stuck in a boot loop of sorts.... it boots, and loads up Android, and I can use the phone, but after about 20-30 seconds it reboots into recovery.
Is there an easy way out of this without wiping everything? Preferably a modded OTA that I can install for the 4.4.4 update.
Click to expand...
Click to collapse
The above post is good advice. If you use House of Moto with the full 4.4.4 FXZ, you can choose to "KEEP DATA".
You will need to flash TWRP back on and re-root afterwards AND re-install Xposed, but all of your apps and settings will remain intact.
The reason this happened is because you have TWRP installed - taking OTAs *always* requires you to have STOCK recovery - not custom.
Good Luck :good:
samwathegreat said:
The above post is good advice. If you use House of Moto with the full 4.4.4 FXZ, you can choose to "KEEP DATA".
You will need to flash TWRP back on and re-root afterwards AND re-install Xposed, but all of your apps and settings will remain intact.
The reason this happened is because you have TWRP installed - taking OTAs *always* requires you to have STOCK recovery - not custom.
Good Luck :good:
Click to expand...
Click to collapse
Thanks for the replies. Thanks for the reply... the phone eventually decided the update failed and gave up. Apparently clearing the cache would've also probably worked.
But, now I've reflashed stock recovery, removed xposed, and unrooted. I should be safe to just take the OTA now, right?
I would've done the FXZ earlier, but didn't realize there was a keep data option.
coreno said:
Thanks for the replies. Thanks for the reply... the phone eventually decided the update failed and gave up. Apparently clearing the cache would've also probably worked.
But, now I've reflashed stock recovery, removed xposed, and unrooted. I should be safe to just take the OTA now, right?
I would've done the FXZ earlier, but didn't realize there was a keep data option.
Click to expand...
Click to collapse
You can try, and it will probably work....but if it were me, I'd still use the FXZ and keep data option. It's cleaner and no chance of something going wrong. Afterwards, just do like I said -- re-flash TWRP, re-root, then reinstall Xposed.
samwathegreat said:
You can try, and it will probably work....but if it were me, I'd still use the FXZ and keep data option. It's cleaner and no chance of something going wrong. Afterwards, just do like I said -- re-flash TWRP, re-root, then reinstall Xposed.
Click to expand...
Click to collapse
Thanks for you help! I am all upgraded and got everything back going to the way it was!
coreno said:
Thanks for you help! I am all upgraded and got everything back going to the way it was!
Click to expand...
Click to collapse
Great!! Glad to hear everything worked out. I sent you a Private message - check your PMs
Just to add my experience: I too tried to apply the update (rooted, 4.4.2, xposed, stock recovery, locked boot loader).
Got the boot loop you mentioned.
Only remedy was for me to quickly go into root explorer and rename the 3c.ota.apk and 3c.ota.odex files. Now I no longer get the notifications (unless I reboot my phone).
jco23 said:
Just to add my experience: I too tried to apply the update (rooted, 4.4.2, xposed, stock recovery, locked boot loader).
Got the boot loop you mentioned.
Only remedy was for me to quickly go into root explorer and rename the 3c.ota.apk and 3c.ota.odex files. Now I no longer get the notifications (unless I reboot my phone).
Click to expand...
Click to collapse
And in your case, it was Xposed.
There are several threads (and posts) discussing conditions for taking an OTA. You need stock recovery, have to disable Xposed, and you need to be close enough to stock so the pre-flash verification will pass. Otherwise, the OTA will fail, and/or you'll get stuck in a boot loop.
There is a little more to it as well, but I'll ask you to see the other threads.
Thought I disabled xposed. But perhaps not. I've read other threads. From my understanding, I won't be able to root (or even the quasi-root) on 4.4.4 with a locked boot loader.
Thx for the reply.
I was originally on lollipop, downgraded to nc2, rooted, then got the oc1 lollipop root. I then installed all my apps, and restarted the phone. When the safestrap menu comes up i click continue to boot, but theres just a black screen for 30 seconds until it opens up the normal android recovery menu. What should i do? Can i configure something in safestrap to let it boot?
This might be important but I think this was caused by me holding the power button, clicking on reboot device and selecting a safestrap recovery boot. Not sure how to fix this because I heard safestrap won't work on oc1.
Zenoah said:
I was originally on lollipop, downgraded to nc2, rooted, then got the oc1 lollipop root. I then installed all my apps, and restarted the phone. When the safestrap menu comes up i click continue to boot, but theres just a black screen for 30 seconds until it opens up the normal android recovery menu. What should i do? Can i configure something in safestrap to let it boot?
Click to expand...
Click to collapse
You need to flash the SM-N900A_OC1_Kernel_Safestrap_Installer.zip in Safestrap which should be on your internal storage, ("5. Flash the file called "SM-N900A_OC1_Kernel_Safestrap_Installer.zip" which is located under /sdcard/OC1_Kernel/") http://forum.xda-developers.com/showpost.php?p=59666958&postcount=2 If you can't find the OC1 Kernel folder, then you can flash this http://forum.xda-developers.com/attachment.php?attachmentid=3231668&stc=1&d=1427464619 from here http://forum.xda-developers.com/note-3-att/general/att-nj5-safestrap-t2957471 Anytime you are done with Safestrap you need to flash the OC1 Kernel in Safestrap before leaving Safestrap.
So I had root on 4.4.2 with busybox and safestrap. I attempted to flash the OC1 file which is the stock 5.0 rooted lollipop, but it failed. Now my phone boots and shows the paddle lock boot screen, but bypasses safe strap and goes into an Android system recovery withe the android guy. Ive tried to target my original backup, but it fails. I'm going into the twrp directory on my external storage that has the stock backup, but when i click it, it opens and shows 4 md5 files.
data.ext4.win000.md5
data.ext4.win001.md5
system.ext4.win000.md5
system.ext4.win001.md5
Is there a way to get the phone to boot? I've just tried to wipe data as well but it connects to odin for a few seconds, then goes into removed status when it goes into Android System Recovery <3e>.
Have u flashed the twrp recovery?
Sent from my A0001 using XDA Free mobile app
i was able to get it to boot to ODIN and i just put it back to 4.4.2. After root, I'll dig into the forums to see what i did wrong. I'd like to use the stock lollipop rooted but safestrap kept failing when it was verifying the partition.
lesd777 said:
i was able to get it to boot to ODIN and i just put it back to 4.4.2. After root, I'll dig into the forums to see what i did wrong. I'd like to use the stock lollipop rooted but safestrap kept failing when it was verifying the partition.
Click to expand...
Click to collapse
Did you make sure to flash the lollipop kernel in safestrap before rebooting? You can't use regular twrp on our locked bootloader, so safestrap and flashfire are the only options. But safestrap doesn't work out the door with L, so you have to use flashfire or the safestrap workaround. Make sure you read, read, and read some more to get where you're trying to go. Good luck.