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.
Related
I tried to update my brothers phone to 4.4 from 12B because he kept saying that it would try to update but would fail which I didn't understand why because he only had root but that's not the problem. I installed TWRP and made a backup right away. I then installed the boot stack from this thread http://forum.xda-developers.com/showthread.php?t=2715408 then rebooted and was bootlooping. So, I put it in recovery mode and think I probably messed something up so I'll just restore the backup I made. I restore it and everything is looking good no errors or anything until I go to reboot it and it's still bootlooping. I'm stuck here because everything I've tried has failed.
I recommend following the restore to stock instructions (the tot method going to 11a then OTA to 12b) in the general section. Then use Cloudy's Malidus 2.0.2 files to update to 4.4.2.
Sent from my VS980 4G using Tapatalk
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!
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
Hello, I'm terribly sorry if this is the incorrect place to put this; but I'm desperate. I flashed hyperdrive on my galaxy s4 active NH3, and it booted the rom before I could flash the master patch, and the su update zips. So now im stuck with an unrootable nh3 galaxy s4 active that runs hyperdrive rom fine, but my wifi doesn't work, and I can't get into safestrap to flash the modules, because I can't root to install safestrap. Someone please help me, I can't reinstall my stock rom with Odin right now because my computer isn't working. Please help and thank you so much
The safe strap splash screen doesn't show up at boot? A safe strap ROM should not uninstall safe strap iirc.
Just because the app isn't in your app drawer, doesn't necessarily mean safe strap is gone. Reboot and check if it's still there, it should be.
The splash screen doent come up at all. It just says "samsung galaxy s4 active" and where the ss screen should come up, it automatically boots into the rom, displaying the rom boot animation and booting into the rom
thisisapoorusernamechoice said:
The safe strap splash screen doesn't show up at boot? A safe strap ROM should not uninstall safe strap iirc.
Just because the app isn't in your app drawer, doesn't necessarily mean safe strap is gone. Reboot and check if it's still there, it should be.
Click to expand...
Click to collapse
Could it be that when I flashed the rom in ss I wasnt able to flash the su update, and the rom took away my root? Idk im desperate
Lane5SOS said:
Could it be that when I flashed the rom in ss I wasnt able to flash the su update, and the rom took away my root? Idk im desperate
Click to expand...
Click to collapse
Every single solution I can think of either requires root (lol hardly a solution, huh?) or consists of, "Odin back to stock." Are you able to use Odin at all?
Even if you don't want to Odin back to stock NE3, I think the W0lfdroid method should still be able to root your phone while on hyperdrive, just like on stock NH3. I.e. flash the root kernel to your phone via Odin, boot and run towelroot, Odin flash the NH3 kernel, boot and install/run superSU.
I'm inclined to think that method will still work because for any rom to work on the i537, it automatically has to be compatible with our stock kernel.
thisisapoorusernamechoice said:
Every single solution I can think of either requires root (lol hardly a solution, huh?) or consists of, "Odin back to stock." Are you able to use Odin at all?
Even if you don't want to Odin back to stock NE3, I think the W0lfdroid method should still be able to root your phone while on hyperdrive, just like on stock NH3. I.e. flash the root kernel to your phone via Odin, boot and run towelroot, Odin flash the NH3 kernel, boot and install/run superSU.
I'm inclined to think that method will still work because for any rom to work on the i537, it automatically has to be compatible with our stock kernel.
Click to expand...
Click to collapse
Thank you, ill try that method. I wont be able to get my computer fixed until the weekend so im suck with no wifi or camera until then. Im still very confused as to why it did all of this. When I flashed the rom in ss, the aroma installer launched, and at the end I pressed next and it froze, so I had to take my battery out a place it back in. When I rebooted I expected to see the ss splachscreen so I could proceed to flash the masterpatch and the camera and wifi fix but it just booted right into the rom boot animation and then loads the rom. It continues to do this, so I have no safestrap now. However I do have the safestrap apk saved on my sd card along with the towlroot apk incase I ever lose root while flashing a rom and my wifi doesn't work such as the fist time I flashed hyperdrive with my NE3.
Anyways thanks a bundle
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.