Related
It is what it says on the box....
I accidentally flashed an updated 4.2.2 rom onto my rooted Nexus 4 that was only running 4.2.1
Now, I can't get by the repeated error messages.
In recovery mode have tried to wipe the cache, the dalvik... even tried a full new install of the SU binary.... but can't seem to recover from this error.
Any insight?
I'm only asking this because it's on the script us tech support people have to follow. Did you make a backup?
wipe data(factory reset), then reflash your 4.2.2 nexus 4 rom(and gapps if needed). just flashing the su binaries does nothing for you. i do stuff like this for fun sometimes, its neat seeing all those errors
benderunit9000 said:
I'm only asking this because it's on the script us tech support people have to follow. Did you make a backup?
Click to expand...
Click to collapse
Fair question -
I backed up all my data, yes.
And I had just done a fresh unlocking so I didn't think I needed to - I still had the SU binary in the root directory.
I tried to reflash, still won't boot up in a way I can get at the root directory to put new .zip ROMs on the root, etc.
simms22 said:
wipe data(factory reset), then reflash your 4.2.2 nexus 4 rom(and gapps if needed). just flashing the su binaries does nothing for you. i do stuff like this for fun sometimes, its neat seeing all those errors
Click to expand...
Click to collapse
Did the factory reset. But I don't know how to re-flash with 4.2.2 since it was 4.2.1 originally.
I've downloaded the binary... do I use a similar command ./fastboot .... etc. like I used for flashing the other things?
Robworldwide said:
Fair question -
I backed up all my data, yes.
And I had just done a fresh unlocking so I didn't think I needed to - I still had the SU binary in the root directory.
I tried to reflash, still won't boot up in a way I can get at the root directory to put new .zip ROMs on the root, etc.
Click to expand...
Click to collapse
there should be an adb sideload option in your custom recovery, you can push a rom to your phone from your computer using adb. you can also reflash the stock image via fastboot. then youll just have to reflash a recovery, then your su binaries or custom rom.
---------- Post added at 09:46 PM ---------- Previous post was at 09:42 PM ----------
Robworldwide said:
Did the factory reset. But I don't know how to re-flash with 4.2.2 since it was 4.2.1 originally.
I've downloaded the binary... do I use a similar command ./fastboot .... etc. like I used for flashing the other things?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2010312
simms22 said:
there should be an adb sideload option in your custom recovery, you can push a rom to your phone from your computer using adb. you can also reflash the stock image via fastboot. then youll just have to reflash a recovery, then your su binaries or custom rom.
Click to expand...
Click to collapse
Hmmm.
Okay. I'm using clockworkMod Recov 5.8.3.1
I don't see the sideload option, but I'll keep looking.
Robworldwide said:
Hmmm.
Okay. I'm using clockworkMod Recov 5.8.3.1
I don't see the sideload option, but I'll keep looking.
Click to expand...
Click to collapse
cwm should have it, twrp has it for sure.
simms22 said:
there should be an adb sideload option in your custom recovery, you can push a rom to your phone from your computer using adb. you can also reflash the stock image via fastboot. then youll just have to reflash a recovery, then your su binaries or custom rom.
---------- Post added at 09:46 PM ---------- Previous post was at 09:42 PM ----------
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
I've been trying for hours. NO IDEA how to do any of this with a MAC computer.
I at least get to my CDW recovery screen, but I don't have a clue what to do next.
1. Go back to 100% stock using efrant's guide on here
2. Read up on everything so you know what you're doing
3. Try again
EddyOS said:
1. Go back to 100% stock using efrant's guide on here
2. Read up on everything so you know what you're doing
3. Try again
Click to expand...
Click to collapse
For the benefit of those coming after me, who may run into the same problem I did:
I can attest to the wisdom of the above 3 simple steps. It took me several hours to *finally* get this right, but the ABSOLUTE SLAM-DUNK I'VE FINALLY GOT THIS SUSSED PROCESS happened start-to-finish in 20 minutes.
The key step: METICULOUS FOLLOWING EFRANT'S GUIDE.
Do not get sidetracked by other boards or 'short-cuts'.
Just do this... it works, and obviously I learned a lot along the way.
I'm now back to stock, and happily unlocking and rooting, installing custom ROMs just being cognizant of the difficulty if I flash a 4.2.2 ROM on a device that is currently 4.2.1 (which, I believe, is the stock Sprint even now as of April 23).
Thank you to EddyOS and Simms.
what you actually have to do when flashing a ROM with a higher android version than the one you are running? for example I am now on CM10.1, and when Android 5.0 comes out, I need to flash new bootloader and baseband to update to a 5.0 ROM and it will work? Or what?
Thanks in advance!
Sent from my Nexus 4 using xda app-developers app
Thibaultvw said:
what you actually have to do when flashing a ROM with a higher android version than the one you are running? for example I am now on CM10.1, and when Android 5.0 comes out, I need to flash new bootloader and baseband to update to a 5.0 ROM and it will work? Or what?
Thanks in advance!
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
The key for me was that in addition to flashing the new ROM (I was running 4.2.1 and wanted to put on a custom 4.2.2 ROM) I had to sequentially install the custom ROM then the gapps file while in the same session in recovery mode. Do NOT install just the ROM and then exit recovery mode and reboot! That is how mine got hung up and I had to do a full stock re-install (see Efrant's guide).
As I understand it, this was an issue due to the a change in directory structure or something, so YMMV - this may not apply to future versions of Android.
Robworldwide said:
The key for me was that in addition to flashing the new ROM (I was running 4.2.1 and wanted to put on a custom 4.2.2 ROM) I had to sequentially install the custom ROM then the gapps file while in the same session in recovery mode. Do NOT install just the ROM and then exit recovery mode and reboot! That is how mine got hung up and I had to do a full stock re-install (see Efrant's guide).
As I understand it, this was an issue due to the a change in directory structure or something, so YMMV - this may not apply to future versions of Android.
Click to expand...
Click to collapse
So you didnt actually have to do something special cause I always flash gapps in same session.
And baseband and bootloader, how did you do that? Just flash before installing ROM?
Sent from my Nexus 4 using xda app-developers app
When KLP finally comes out the first thing I will be doing is flashing the complete factory image when released from Google. This will update everything and then using a custom KLP ROM will be a sinch. This is my personal opinion and others may say otherwise but for me it works
EddyOS said:
When KLP finally comes out the first thing I will be doing is flashing the complete factory image when released from Google. This will update everything and then using a custom KLP ROM will be a sinch. This is my personal opinion and others may say otherwise but for me it works
Click to expand...
Click to collapse
Yeah but cant you just install new bootloader and baseband, and then flash a ROM? Much easier imo
Sent from my Nexus 4 using xda app-developers app
I, personally, prefer to flash everything first and then go custom. Dunno why, just do!
EddyOS said:
I, personally, prefer to flash everything first and then go custom. Dunno why, just do!
Click to expand...
Click to collapse
Meh, easier if you just flash stock ROM in CWM first if you want to...
But could someone please answer my question?
Sent from my Nexus 4 using xda app-developers app
Anyone figure out how to root the new OTA? It wont allow root with the old flash way since its new OTA
timenewton said:
Anyone figure out how to root the new OTA? It wont allow root with the old flash way since its new OTA
Click to expand...
Click to collapse
Yes use the new IOROOT15 to root the device. But I have been unsuccessful in flashing any roms, however I did get twrp to work with FreeGee app in the android market.
I appreciate your help very much, thank you
jea508 said:
Yes use the new IOROOT15 to root the device. But I have been unsuccessful in flashing any roms, however I did get twrp to work with FreeGee app in the android market.
Click to expand...
Click to collapse
What version of twrp? Sounds like you may need to update.
Sent from my LG-D800
btm fdr said:
What version of twrp? Sounds like you may need to update.
Sent from my LG-D800
Click to expand...
Click to collapse
Im still using the twrp that was flashed with freegee. i'm a newb to all this. Maybe i should flash new version of twrp and try. I was trying to install the mal 4.2.2 rom and just got lg screen, then black.
jea508 said:
Im still using the twrp that was flashed with freegee. i'm a newb to all this. Maybe i should flash new version of twrp and try. I was trying to install the mal 4.2.2 rom and just got lg screen, then black.
Click to expand...
Click to collapse
I've been unsuccessful in getting any roms to work. I tried 4.2.2 rom and got lg screen then black, had to restore nand backup from twrp recovery but it was hellish to get into, had to do the hold vol+pwr precisely, almost gave up. So, reverted to a backup just fine.
Next tried to loki_flash recovery 2.6.3.1 (then was going to do them in order-2.6.3.2>2.6.3.3 [have not tried going directly to 2.6.3.3) and was hit with an unsupported aboot error (device mismatch).
So now i'm going to try and use flash tool to revert back to 11A, root, install twrp (I hope this is possible and I don't brick my phone [i'm new to all of this])
Anyone tell me if this is an acceptable option to proceed? Thank's in advance.
Acceptable. KDZ to 11A.
Just wanted to post I was successful using lg flash tool to revert to 11A, rooted, freegee twrp, flashed 2.6.3.3, flashed OSE ROM. Everything is well ATM!
Sent from my LG-VS980 using Tapatalk
Hey guys, somehow I managed to do something unexpected to my N3 and It stops at the Samsung Note 3 screen right after startup. I can access stock recovery but it wont hit safestrap. Anyhow, I was going to odin flash a stock .tar file and start over. However, I'm a bit confused on what file to flash and how to proceed from there. Can I flash a KK .tar file or do I have to flash a JB based .tar file and then root and upgrade. Either way, what is the prefered .tar file(s)? I've looked around a bit and I'm thuroughly confused! Any help would be greatly appreciated.
scheirere said:
Hey guys, somehow I managed to do something unexpected to my N3 and It stops at the Samsung Note 3 screen right after startup. I can access stock recovery but it wont hit safestrap. Anyhow, I was going to odin flash a stock .tar file and start over. However, I'm a bit confused on what file to flash and how to proceed from there. Can I flash a KK .tar file or do I have to flash a JB based .tar file and then root and upgrade. Either way, what is the prefered .tar file(s)? I've looked around a bit and I'm thuroughly confused! Any help would be greatly appreciated.
Click to expand...
Click to collapse
Were you initally on MJE then upgraded to NC2 then a NC4 ROM? If not did you take the NC4 OTA or flash the NC4 .tar file to get on KK?
airmaxx23 said:
Were you initally on MJE then upgraded to NC2 then a NC4 ROM? If not did you take the NC4 OTA or flash the NC4 .tar file to get on KK?
Click to expand...
Click to collapse
Yep, I came from MJE and then up to NC2/NC4 KK. I was running BajaROM at the time and was trying to do a wipe for a clean install of the latest version. Again, I have no idea what I did to screw this up.
scheirere said:
Yep, I came from MJE and then up to NC2/NC4 KK. I was running BajaROM at the time and was trying to do a wipe for a clean install of the latest version. Again, I have no idea what I did to screw this up.
Click to expand...
Click to collapse
Do not flash the NC4 tar, you will be stuck on it with no way to downgrade. Flash the MJE full tar file in Odin, root it with TowelRoot, Install SU, and BusyBox (make sure to open the app and do the actual install) then install SS 3.65. After you're done install the ROM of your choice through SafeStrap 3.65, once it's done installing reboot to download mode and flash the file in the link below through Odin. Once you boot up to the ROM install the newest version of SS.
http://forum.xda-developers.com/devdb/project/dl/?id=6366
airmaxx23 said:
Do not flash the NC4 tar, you will be stuck on it with no way to downgrade. Flash the MJE full tar file in Odin, root it with TowelRoot, Install SU, and BusyBox (make sure to open the app and do the actual install) then install SS 3.65. After you're done install the ROM of your choice through SafeStrap 3.65, once it's done installing reboot to download mode and flash the file in the link below through Odin. Once you boot up to the ROM install the newest version of SS.
http://forum.xda-developers.com/devdb/project/dl/?id=6366
Click to expand...
Click to collapse
Cool, Cool! Downloading all the files as I type this. I can just download and install BusyBox from Google Play, right? Or is their a different .apk or flashable file I need to use?
scheirere said:
Cool, Cool! Downloading all the files as I type this. I can just download and install BusyBox from Google Play, right? Or is their a different .apk or flashable file I need to use?
Click to expand...
Click to collapse
The one from Google Play is the one you want.
soft Brick Safestrap 3.65 issues
I'm in the same boat did the first steps down graded to MJE rootedd installed SU Busy safestrap 3.65 but I have root but won't boot into safe strap so I can't install a Custom Rom. Says Safe Strap is not Active again I just installed 3.65 am I supposed to follow that up with installing 3.75 over it before using it?
pospower said:
I'm in the same boat did the first steps down graded to MJE rootedd installed SU Busy safestrap 3.65 but I have root but won't boot into safe strap so I can't install a Custom Rom. Says Safe Strap is not Active again I just installed 3.65 am I supposed to follow that up with installing 3.75 over it before using it?
Click to expand...
Click to collapse
Safe Strap should say "not active" unless you're booted into a ROM slot other than stock. Did you try rebooting and hitting "recovery" when the SS screen comes up? You can not hit "boot to recovery" in SS.
No option to hit safe strap.?
airmaxx23 said:
Safe Strap should say "not active" unless you're booted into a ROM slot other than stock. Did you try rebooting and hitting "recovery" when the SS screen comes up? You can not hit "boot to recovery" in SS.
Click to expand...
Click to collapse
I'm familiar it just goes right to the stock rooted rom. No option to hit safestrap.
pospower said:
I'm familiar it just goes right to the stock rooted rom. No option to hit safestrap.
Click to expand...
Click to collapse
Did you hit "install recovery" in SS?
airmaxx23 said:
Did you hit "install recovery" in SS?
Click to expand...
Click to collapse
Yes was I not supposed too? Then I just rebooted. and looked for the boot into safe strap option on the screen and it went right into the rom.
pospower said:
Yes was I not supposed too? Then I just rebooted. and looked for the boot into safe strap option on the screen and it went right into the rom.
Click to expand...
Click to collapse
Yes, you were supposed to install it. I'd try opening SS, hit uninstall, then uninstall the app and try installing the app and recovery again. Did you grant it SU permissions?
airmaxx23 said:
Yes, you were supposed to install it. I'd try opening SS, hit uninstall, then uninstall the app and try installing the app and recovery again. Did you grant it SU permissions?
Click to expand...
Click to collapse
yes to SU now once I install recovery do i boot into recovery or just reboot. ? I have been just rebooting.
pospower said:
yes to SU now once I install recovery do i boot into recovery or just reboot. ? I have been just rebooting.
Click to expand...
Click to collapse
You just do a normal reboot (phone completely off then on) and you should see the SS screen.
airmaxx23 said:
You just do a normal reboot (phone completely off then on) and you should see the SS screen.
Click to expand...
Click to collapse
yup nothing just back to stock. I"m stuck. I think I'm going to start over with odin MJE.
Once there root using TR Then down load SU run it. then Safe strap 3.65.
correct?
pospower said:
yup nothing just back to stock. I"m stuck. I think I'm going to start over with odin MJE.
Once there root using TR Then down load SU run it. then Safe strap 3.65.
correct?
Click to expand...
Click to collapse
Did you install the busybox app then open it and install busy box?
airmaxx23 said:
Did you install the busybox app then open it and install busy box?
Click to expand...
Click to collapse
Honestly not sure at this point. I might have just installed SU then Safestrap 3.65 doesn't that install busybox?
pospower said:
Honestly not sure at this point. I might have just installed SU then Safestrap 3.65 doesn't that install busybox?
Click to expand...
Click to collapse
No, you need to download busybox from the Play Store, open it and then install busybox through the app. That's why SS isn't working. After you root you need SU, busybox, and SS.
airmaxx23 said:
No, you need to download busybox from the Play Store, open it and then install busybox through the app. That's why SS isn't working. After you root you need SU, busybox, and SS.
Click to expand...
Click to collapse
got it ill let you know
---------- Post added at 09:33 PM ---------- Previous post was at 09:24 PM ----------
pospower said:
got it ill let you know
Click to expand...
Click to collapse
Ok reodined MJE ran TR then installed Busy Box Then SU rebooted then installed SS 3.65 rebooted and NOTHING still goes right back into stock MJE Rooted Rom.
pospower said:
got it ill let you know
---------- Post added at 09:33 PM ---------- Previous post was at 09:24 PM ----------
Ok reodined MJE ran TR then installed Busy Box Then SU rebooted then installed SS 3.65 rebooted and NOTHING still goes right back into stock MJE Rooted Rom.
Click to expand...
Click to collapse
Did you open the busybox app and install busybox?
I had rooted my phone using the downgrade method a while back (MK2 -> NB1?) For whatever reason, I decided I wanted to flash a clean ROM. I went ahead and flashed I337UCUFNB1_Rootable_Full_Odin and rooted with Towelroot (I never wiped cache or data with Safestrap before...completely forgot about it). I am now on rooted NB1 with superuser installed, however Safestrap refuses to install. After I install the recovery, even though it states the installation was complete, the status of Safestrap is still "Not Installed".
Did I make a booboo by not wiping/uninstall safestrap beforehand? Is the old version and the new conflicting? halp
Unistall the recovery using the previous version of the app and then install the new version
jmjoyas said:
Unistall the recovery using the previous version of the app and then install the new version
Click to expand...
Click to collapse
Meaning install 3.71, uninstalling, rebooting, installing 3.72, then installing again? That didn't do anything for me
Outta the loop
Possibly stupid question, but what is Safestrap? I haven't been around here in a year or so
FlashThisB said:
Possibly stupid question, but what is Safestrap? I haven't been around here in a year or so
Click to expand...
Click to collapse
What seems to be a very simple and on the surface recovery mode for phones with locked bootloaders.
SELinux Mode Changer solved my problem.
FlashThisB said:
Possibly stupid question, but what is Safestrap? I haven't been around here in a year or so
Click to expand...
Click to collapse
If you are on MDL build, you don't need it. You can read up on it in Development, HashCode has a thread there--
Q&A for [RECOVERY LOCKED/NCG] Safestrap Recovery v3.75 [2014-06-26 B03]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Safestrap does not work
Hi, this is my first time ask for help. I have verizon samsung galaxy s4 and currently with hyperdrive 18.1 and safestrap 3.75. For some reason, I found my safesrtrap does not work. I touch the screen, nothing happened. I lock screen and swip to unlock, nothing happened. Feel like touch screen does not work. Could anybody help me? Thanks
doubletong said:
Hi, this is my first time ask for help. I have verizon samsung galaxy s4 and currently with hyperdrive 18.1 and safestrap 3.75. For some reason, I found my safesrtrap does not work. I touch the screen, nothing happened. I lock screen and swip to unlock, nothing happened. Feel like touch screen does not work. Could anybody help me? Thanks
Click to expand...
Click to collapse
are you using the safestrap from the s4 or from the s5 thread? if so, try using the s4 ss apk
Sent from my SM-G900V using XDA Free mobile app
Splash screen shows after apk removal of SS 3.75
I have read numerous threads and can not find a clearly define method for removing all traces of safe strap 3.75 if there is one kindly point me to it.
device VZW Note 3, running Kit kat, rooted via geohot towelroot method, Su pro version 1.99
1. I have removed SS by uninstalling recovery then uninstalling the app.
2. On initial start up no safe strap screen.
3. On reboots "custom "pad lock shows as if Safe Strap is still installed.
4.After Safe Strap apk removal SU binaries wont update either even after the 5 reboots attempts
I have seen the manual remove method for SafeStrap versions 3.62 and lower:
su
mount -o remount,rw /system
mv /system/etc/init.qcom.modem_links.sh.bin /system/etc/init.qcom.modem_links.sh
rm -rf /system/etc/safestrap
rm /system/etc/firmware/q6.mdt
ln -s /firmware/image/q6.mdt /system/etc/firmware/q6.mdt
mount -o remount,ro /system
Can I do this manually for the 3.75 version of safe strap? I just want to remove all traces of safe strap (all splash screens ) and update SU binaries post its removal.
Thanks!
Backups being removed
I installed SafeStrap 3.75 on my s5 and it runs, and says it backs up properly to the sd card, but when I reboot back into Android, the backup file is no where to be found. The TWRP folder on the sdcard is empty. Does anyone know why the file would that it exists inside safestrap, but disappear after reboot?
I've got NCG installed, I've rooted, installed SuperSU, Installed the latest busybox and I've installed and run sdfix to fix the permissions on the SD Card, yet every backup I make is removed from the sd card.
It DOES backup successfully to the internal device storage, thoughts?
did not find delete option for posts...
ahbeeneverywhereman said:
did not find delete option for posts...
Click to expand...
Click to collapse
You can not remove your own posts. It has to be deleted by someone with the authority to do so.
Verizon Galaxy S5 Safestrap and NI2 ROMS
Hello everyone,
First time poster, long time lurker.
I usually just lurk until I find the answers to my questions. I figured I can become an active member of the community now.
I have a rooted Galaxy S5 running on the NCG build. I want to install a custom ROM using Safestrap 3.75. Then I want to install Optimal ROM which is running on NI2. For which I believe I will have to install the NI2 firmware tar.
What exactly is the NI2 firmware tar (is this the kernal)? And if I install it, will it remove root (I'm logically assuming no but I need some confidence on the quesion)?
Much appreciated!
safestrap help!
i have a verizon galaxy s5, model number sm-g900v, android version 4.4.4, baseband version ending in ank2, kernel version 3.4.0, build number ending in ank2. i have flashed back to baseband NCG via odin v3.09, rooted via towelroot, verified root via root check lite, flashed back to baseband version ending in ANK2 via odin v3.09, verified root via root check lite, installed superSU by chainfire, installed busybox by jrummy apps inc, installed titanium backup and performed backup.... so my question is, will the current safestrap for verizon gs5 work with my phone? the thing that kinda worries me is the link >> Safestrap-KLTEVZW-NCG-3.75-B03.apk<< shows "NCG". does this mean NCG and up or NCG only? if it means NCG only, where is the ANK2 safestrap? what are my options for a recovery?
LLG BAD HABIT CC said:
i have a verizon galaxy s5, model number sm-g900v, android version 4.4.4, baseband version ending in ank2, kernel version 3.4.0, build number ending in ank2. i have flashed back to baseband NCG via odin v3.09, rooted via towelroot, verified root via root check lite, flashed back to baseband version ending in ANK2 via odin v3.09, verified root via root check lite, installed superSU by chainfire, installed busybox by jrummy apps inc, installed titanium backup and performed backup.... so my question is, will the current safestrap for verizon gs5 work with my phone? the thing that kinda worries me is the link >> Safestrap-KLTEVZW-NCG-3.75-B03.apk<< shows "NCG". does this mean NCG and up or NCG only? if it means NCG only, where is the ANK2 safestrap? what are my options for a recovery?
Click to expand...
Click to collapse
No worries SafeStrap works fine with all the kernels so far. Just use the updated one here.
thanks!
Misterxtc said:
No worries SafeStrap works fine with all the kernels so far. Just use the updated one here.
Click to expand...
Click to collapse
thats what i assumed but didnt want to try until i got a confidence boost (its my only phone at the moment). i tried downloading your beta but got a 404 not found error. again, i assume thats because its out of beta with known issues having been fixed as its kind of an old post. the one i downloaded (from the same thread) seems to be working just fine (have yet to flash a rom... that will come tomorrow). thanks for the quick response; thats part of what makes great communities. BTW i hit that thanks button.
LLG BAD HABIT CC said:
thats what i assumed but didnt want to try until i got a confidence boost (its my only phone at the moment). i tried downloading your beta but got a 404 not found error. again, i assume thats because its out of beta with known issues having been fixed as its kind of an old post. the one i downloaded (from the same thread) seems to be working just fine (have yet to flash a rom... that will come tomorrow). thanks for the quick response; thats part of what makes great communities. BTW i hit that thanks button.[/QUOT
Did you try SS on ANK2? did it work? I just got the phone back from Samsung, don't wanna mess it up Thanks!
Click to expand...
Click to collapse
dj_ox said:
LLG BAD HABIT CC said:
thats what i assumed but didnt want to try until i got a confidence boost (its my only phone at the moment). i tried downloading your beta but got a 404 not found error. again, i assume thats because its out of beta with known issues having been fixed as its kind of an old post. the one i downloaded (from the same thread) seems to be working just fine (have yet to flash a rom... that will come tomorrow). thanks for the quick response; thats part of what makes great communities. BTW i hit that thanks button.[/QUOT
Did you try SS on ANK2? did it work? I just got the phone back from Samsung, don't wanna mess it up Thanks!
Click to expand...
Click to collapse
Yes sir. Worked fine. NK2 baseband, android version 4.4.4
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
outpost785
Sorry if this has been asked already ,safestrap for s5 on rooted stock 5.0 .Safestrap says its installed but will not work.Thanks inadvance.
outpost785 said:
Sorry if this has been asked already ,safestrap for s5 on rooted stock 5.0 .Safestrap says its installed but will not work.Thanks inadvance.
Click to expand...
Click to collapse
I had to run the SS and SuperSu step again.
Rapunzl said:
I had to run the SS and SuperSu step again.
Click to expand...
Click to collapse
Are you saying that you are able to access the safestrap recovery while running the 5.0 kernel? All reports state that ss will no longer work on the 5.0 kernel.
That's what I have found myself that ss is a no go on 5.0 hopefully someone finds a work around, I can't boot into stock recovery
outpost785 said:
That's what I have found myself that ss is a no go on 5.0 hopefully someone finds a work around, I can't boot into stock recovery
Click to expand...
Click to collapse
The ss recovery will work on a 5.0 build by downgrading the kernel back to nk2.
But can/can't run 5.0 on nk2 kernel?
outpost785 said:
But can/can't run 5.0 on nk2 kernel?
Click to expand...
Click to collapse
5.0 will not boot on the NK2 kernel.