I flash the stock firmware on the phone.
Installed root and safestrap recovery.
Booted into safestrap, wiped stock slot and installed Goldeneye by selecting all of the safestrap options.
Unselected reboot option and installed NB1 modules.
Rebooted into system
After this when it boots up, it shows safestrap disabled. If I wait, it goes to a black screen for a while and then reboots again into stock recovery. If I reboot again, it repeats the same thing over again. Yesterday, I got it to work using this same steps if I remember correctly, but the wifi wasn't working, so I needed to flash to stock again and try again making sure to install the modules.
UPDATE: I tried again, but with the GE-XXUGNK4-49.2 rom. I first tried to flash it to stock slot, but it didn't work. Then, I tried again by creating a new slot, flashing the rom to there. It didn't work, so I deleted it and tried the stock slot again. It worked this time. Now I'm going to try this again, but with the GE-XXUHOD7-53 rom.
UPDATE2: It didn't work. I'm not sure what's going on. It flashed just fine yesterday. I'm going to try again, but without wiping stock slot before installing.
UPDATE3: Didn't work. I'm so tired of this. Does anyone have any idea what's happening with this?
UPDATE4: I got it to work! I followed the safestrap instructions for GE EXACTLY. The thing that was throwing me off was that I thought I had to install the NB1 kernel and not the OC3 since I have NB1, but I did everything OC3. Also, I have no idea how I got it to work yesterday. I'm pretty sure all I did was just install and run.
Related
Cliff Notes
Bug during ODIN after failed flash of MDL
battery pull to reset phone after bad flash of MDL
ODIN flash MDB worked fine
Rooted/recovery TWRP worked fine
ODIN flash to MDL worked fine
Rooted/recovery TWRP worked fine
Reboot and NO custom/padlock
wiped/reset and flashed new ROM
STILL have root/recovery and custom ROM/Kernel work 100%
restored old (that had Custom/Padlock on boot) backup
STILL no custom/padlock, but everything works
Had Goldeneye ROM 1.3, Ktoosez kernel running perfectly. Went to flash Goldeneye ROM 2.0 and Ktoonsez kernel, and decided to do a clean install, so used ODIN to go back to UCUAMDB baseband. At first i tried to flash a good copy of UCUAMDL, but it kept failing, and i used ODIN to flash UCUAMDB over the *still technically part done at 'download' mode* UCUAMDL, when the UCUAMDB flash worked, I then used 3-Way tool to Root/install TRWP, ODIN flashed to UCUAMDL, used 3-Way again to Root/install TWRP, when it booted, there was no padlock screen. I had to reinstall (rerooted too, to be safe) TWRP, then wiped/reset and flashed Goldeneye 2.0 and Ktoonsez kernel.
The padlock 'custom' screen is gone. I have root. I have custom recovery. I dont know why or how. So i made a full Nandroid backup. I then wiped/reset, and restored the Goldeneye 1.3 backup i had (also TiBU with all data/apps), i STILL have root, recovery, everything back to 1.3, and NO CUSTOM/PADLOCK screen.
I have no idea why; but i know it might be useful to figure out what happened so others with custom rom/kernel can get rid of the Custom/Padlock image as well; i couldnt get rid of it via other methods, and had given up. This happened randomly. Again, i have root, recovery, and custom ROM/Kernel working perfectly, i can even reflash 2.0 via recovery and not get Custom/Padlock screen, or restore the 2.0 backup and no Custom/Padlock screen.
I am having some weird issues trying to flash a custom rom to my Verizon Galaxy Note 3. (NC4)
I was able to root with Towelroot. Able to install safestrap 3.75 and have custom recovery.
I can boot into recovery, able to wipe, create rom slot, and switch between slots fine. (stock boots, slot 1 empty)
Tried flashing custom ROM to slot 1, flashing hangs and fails.
Tried flashing NC2 kernel.tar.md5 flashes fine but stock fails to boot now.
Reflashed stock firmware everything back to normal
Tried flashing NC4 based custom rom to stock, seems to flash fine (says some issues about unable to mount) Says to wipe and reboot, wait 5-10 minutes. Nothing happens and screen stays blank.
I will try to flash Original flash rom in a little, but does anyone have any other ideas?
Thanks!
picabotwo said:
I am having some weird issues trying to flash a custom rom to my Verizon Galaxy Note 3. (NC4)
I was able to root with Towelroot. Able to install safestrap 3.75 and have custom recovery.
I can boot into recovery, able to wipe, create rom slot, and switch between slots fine. (stock boots, slot 1 empty)
Tried flashing custom ROM to slot 1, flashing hangs and fails.
Tried flashing NC2 kernel.tar.md5 flashes fine but stock fails to boot now.
Reflashed stock firmware everything back to normal
Tried flashing NC4 based custom rom to stock, seems to flash fine (says some issues about unable to mount) Says to wipe and reboot, wait 5-10 minutes. Nothing happens and screen stays blank.
I will try to flash Original flash rom in a little, but does anyone have any other ideas?
Thanks!
Click to expand...
Click to collapse
Welcome to the international Galaxy Note 3 forums. Here we have absolutely no idea what you're doing because we have no need for Safestrap. Your best bet would be to go to the Verizon Samsung Galaxy Note 3 forums here: http://forum.xda-developers.com/verizon-galaxy-note-3/help and hope that someone would be able to help you
Having some issues getting a recovery to be flashed on this new device, I am not use to a phone that when rooted doesn't have some stock recovery that actually works. And by that I mean, allows me to install zip from file. All I get is the option to reboot, flash from adb, install from external, wipe factory reset, wipe cache, and install from cache.
Sorry if this has been asked a few times before, but with my searching I didn't find any one answer that solved my problem. Tried flashing a recovery via odin but it said Auth fail for the recovery. Going to try a few other things and see what I can come up with.
Thanks in advanced!
What recovery are you trying to flash? I believe the closet thing we have to a custom recovery is safestrap. Is that what your trying to install?
Ysosrslawl said:
Having some issues getting a recovery to be flashed on this new device, I am not use to a phone that when rooted doesn't have some stock recovery that actually works. And by that I mean, allows me to install zip from file. All I get is the option to reboot, flash from adb, install from external, wipe factory reset, wipe cache, and install from cache.
Sorry if this has been asked a few times before, but with my searching I didn't find any one answer that solved my problem. Tried flashing a recovery via odin but it said Auth fail for the recovery. Going to try a few other things and see what I can come up with.
Thanks in advanced!
Click to expand...
Click to collapse
It sounds like you flashed philz touch recovery witch will not work with the VZW S5 you need to flash SafeStrap Recovery. You might need to Odin back to stock and re root your device to get it back to normal first.
chrisbass said:
What recovery are you trying to flash? I believe the closet thing we have to a custom recovery is safestrap. Is that what your trying to install?
Click to expand...
Click to collapse
I didn't flash anything when I first started rooting the phone I just used towelroot, then when the OTA messed it up I went and did the NCG to NE9 method using odin and towelroot. But every time I went into recovery, it has been the same. It wasn't until I used the toolkit from the forums that installed safestrap and busybox did I actually get a different recovery, but even if I reboot into recovery it still takes me to the stock one first and then on reboot i can access safestrap.
Yes, that's how safestrap works, through a process called "bootstrapping". It never replaces your stock recovery so when you boot into recovery it'll always be stock but upon boot you'll be presented with the safestrap option.....totally normal
On another note, my Supersu binaries wont update so I'm going back to stock anyway. I think I may leave it at stock for a while until I see some more ROMs come out.
Ysosrslawl said:
On another note, my Supersu binaries wont update so I'm going back to stock anyway. I think I may leave it at stock for a while until I see some more ROMs come out.
Click to expand...
Click to collapse
Your other option is what I have done. I first went the safestrap route but installed rom on rom slot before finding out about the bugz in safestrap. So I odined back to stock. Instead of installing something with bugz in it I rooted, installed supersu and Xposed framework with some modules. Wanam module gives you most of the customizations found in custom roms. Tons of other modules for pretty much anything you want to tweak. Works like a champ on stock system.
Hi all,
So - I followed this post - http://forum.xda-developers.com/ver...-to-downgrade-lollipop-5-0-to-kitkat-t3088571
I downgraded from Android 5.0
Now it shows Android 4.4.4
Build ANI2
Kernal 3.4.0
Everything went to plan. Towelroot worked, installed and ran supersu, busybox and safestrap 3.75.
I booted into safestrap - backed up my stock slot, created slot1 and tried to restore my backup to slot1. - after a fair amount of time and normal looking prompts it looks like it is finishing and then says - failed.
Boot it to slot1 just to confirm... it times out and boots to android recovery.
Well - deleted slot, created slot, downloaded Eclipse Rom http://forum.xda-developers.com/ver.../rom-eclipse-s5-tw-v1-0-12-8-14-real-t2967151
Flashed to slot 1
boot fails
Backedup sdcard to my pc
formated sdcard
Uninstalled/reinstalled busybox and safestrap
created backup and tried to restore to slot1...
Still fails.
Not sure what I am doing wrong. Seems like I am missing something easy... Any help would be appreciated.
Regards,
wantpizza said:
Hi all,
So - I followed this post - http://forum.xda-developers.com/ver...-to-downgrade-lollipop-5-0-to-kitkat-t3088571
I downgraded from Android 5.0
Now it shows Android 4.4.4
Build ANI2
Kernal 3.4.0
Everything went to plan. Towelroot worked, installed and ran supersu, busybox and safestrap 3.75.
I booted into safestrap - backed up my stock slot, created slot1 and tried to restore my backup to slot1. - after a fair amount of time and normal looking prompts it looks like it is finishing and then says - failed.
Boot it to slot1 just to confirm... it times out and boots to android recovery.
Well - deleted slot, created slot, downloaded Eclipse Rom http://forum.xda-developers.com/ver.../rom-eclipse-s5-tw-v1-0-12-8-14-real-t2967151
Flashed to slot 1
boot fails
Backedup sdcard to my pc
formated sdcard
Uninstalled/reinstalled busybox and safestrap
created backup and tried to restore to slot1...
Still fails.
Not sure what I am doing wrong. Seems like I am missing something easy... Any help would be appreciated.
Regards,
Click to expand...
Click to collapse
No need to restore your stock slot to one of your slots,the slot is safe. Just flash away.
It has been a while since I used a slot (Roms seem to work better on stock slot) but make sure you are creating a large enough slot to accomadate your ROM. Also, make sure you are using the slot compatible safestrap. If you aren't you will need to go into safestrap, uninstall recovery, go into settings, uninstall safestrap. Go into SuperSU, tell it to forget safestrap. Then install the correct safestrap.
Thanks Tulsadiver.
That is the same safestrap that I used but I will double check it.
I know I don't have to restore stock to slot1 but it would sure give me a warm and fuzzy feeling that things were working if that worked. I guess I am a little scared that something isn't right and flashing a rom to my stock slot could leave me without a phone for a bit if things don't go right.
Do I need to be on a newer firmware? Is the standard slot too small to even fit my stock backup? When I flash a rom to the slot - it completes without errors. But backing up my stock to slot1 trips an error just before completing...
I followed the instructions here http://forum.xda-developers.com/verizon-galaxy-s5/development/safestrap-odin-safestrap-flashable-t3161043 to install Safestrap on my phone with rooted BOE1, my phone rebooted, and I'm looking at a screen that say Android System Recovery <3e> LRX21T.G900VVRU2BOE1
I was trying to install the MOAR rom, but I fear that now I'm stuck in this strange recovery with no way out. Could someone please tell me exactly what I will need to do to get out, and possibly how to actually boot to Safestrap?
Not to leave anything out, though I'll look the fool if I don't, while in this recovery I wiped Data+Cache and attempted to install the ROM, got some sort of error about footers and signature verification (it happened pretty quick then rebooted) and wound up back in recovery, so I tried flashing the BOE1 kernel, same problem, back to recovery.
PhreeqQitsikk said:
I followed the instructions here http://forum.xda-developers.com/ver...t/safestrap-odin-safestrap-flashable-t3161043 to install Safestrap on my phone with rooted BOE1, my phone rebooted, and I'm looking at a screen that say Android System Recovery LRX21T.G900VVRU2BOE1
I was trying to install the MOAR rom, but I fear that now I'm stuck in this strange recovery with no way out. Could someone please tell me exactly what I will need to do to get out, and possibly how to actually boot to Safestrap?
Not to leave anything out, though I'll look the fool if I don't, while in this recovery I wiped Data+Cache and attempted to install the ROM, got some sort of error about footers and signature verification (it happened pretty quick then rebooted) and wound up back in recovery, so I tried flashing the BOE1 kernel, same problem, back to recovery.
Click to expand...
Click to collapse
S5 doesn't have a custom recovery per se, so any app that "reboots to recovery" will go to the Android stock recovery which your in. You can't flash anything of value in there, and can't install a custom recovery. You should just be able to turn the phone off then on again to get back to the stock rom, right?
It's been so long since I've done it, but won't safestrap only install on kitkat? Doors it even work in lollipop? Must people use flashfire I think
I should probably mention now that I got it fixed. Following more instructions in that thread, I did everything in the order of the first step again, using ODIN, flashed back to NC2 (I think? Going off memory) rooted, installed Safestrap, flashed MOAR, and the OC4 firmware, and here I am.