Related
Hi,
I need help guys.
I have S4 and I was trying to mess with it and now I don't have it at all. (pic 1)
the Samsung logo and unlock lock icon are as far as my phone goes now, and after that u cant even power it off u have get battery out. (pic 2)
I am able to go to download mode (pic 3)
and I was able to get to there (up+menu+power key), but now I cant even go there. I get black screen when I am trying to do it. (pic 4)
Thanks for your time,
Ps. Help me
Did you flash a ROM? In you pictures it appears that you can still get to recovery, is that true? What steps did you take for root? We need more information.
answer
Eeiden said:
Did you flash a ROM? In you pictures it appears that you can still get to recovery, is that true? What steps did you take for root? We need more information.
Click to expand...
Click to collapse
I was trying to flash rom, I was trying to make in international phone so it could work in Europe with out any Verizon build in stuff, just pure Samsung.
I can go do download mode, I was able to go for recovery before. That why there is the 4th picture, in stead of regular recovery a had that "teamwin" screen. Now when I press up menu and power is saying its going to recovery boot but then it resets it self and going back to Samsung unlock icon screen and just stays there...
You hold volume down + power to get to download mode. Then connect to a pc and download the all in one tool found in the development thread. Ignore the messages about having your phone in USB debugging and tell it to flash twrp 2.6.0.0. If it doesn't take In download mode, try rebooting your phone while it tries to flash twrp.
If that doesn't work flash stock with Odin and re-root and unlock the phone.
Sent from my SCH-I545 using xda app-developers app
I'm having the exact same problems right now. I tried flashing a 4.3 i9505 rom and now I can't get back into recovery and I can't boot into the OS. I can get into download mode and use ODIN, but I don't know what to do from there. I tried using the All-In-One tool to install TWRP, but it just says Device Not Found. I also tried flashing the stock sch-i545 kernel in ODIN, and it completed successfully, rebooted, and its still doing the same thing. Is there some other way that I've missed to return to stock? I'm kinda bummin here.. but thats what comes with the territory I suppose. Any help you can offer would be greatly appreciated. Thanks.
Found the factory image thread. Going to follow instructions. Will report back.
it works but not completly
So guys going back to my problem I was trying to do everything like lahma69 was trying too...
in odin was error that device not found, all off that...
but what I did, I look more online and I found this one guy...
and what I did in download mode I use odin, and in PDA selection I use this file stockroms(dot)net/file/GalaxyS4/SCH-i545/VRUAMDK_NoWipe.tar.zip
now boom... its kinda works... I am back with my os, I got the android root.
but some things are not right... my phone is very hot, maybe because its charging its self for the first time in weeks.
more important is Whats is happening right now, in boot menu I get errors, no commands, it was not able to do factory reset until I went into os and did it over there... and I cant do software update from Verizon... it goes to root and its trying but then gets error and going back to os...
and I am worry about that file that I download...
so we got little progress and lahma69 I can at least operate os and I have back stock root...
but until we will not going to make it 100% hold on with what I did...
U cant flash a rom thats not made specifically for the verizon variant (i545). The i9505 is the international version of the phone. Hence your phone not booting. Youre going to have to flash the stock mdk firmware through odin and start over (reroot, etc).
SCH-I545 using Tapatalk 2
sannek, I actually got it back up and running doing the same thing you did. I flashed the factory image in this thread: http://forum.xda-developers.com/showthread.php?t=2301259
I haven't noticed any problems yet. I'm fixing to reroot and flash my nandroid. I will let you know if I run into any problems.
I know you can't typically flash a i9505 rom on a verizon gs4, but the author of a i9505 4.3 rom gave me some instructions to try in order to get it working. I'm inserting a 4.3 ramdisk into a 4.2 AOSP ktoonsez verizon gs4 kernel, and replacing the boot.img in the 4.3 i9505 rom. I now know that I had accidentally inserted the wrong version kernel, and thats what caused my problems.
lahma69 said:
sannek, I actually got it back up and running doing the same thing you did. I flashed the factory image in this thread: http://forum.xda-developers.com/showthread.php?t=2301259
I haven't noticed any problems yet. I'm fixing to reroot and flash my nandroid. I will let you know if I run into any problems.
I know you can't typically flash a i9505 rom on a verizon gs4, but the author of a i9505 4.3 rom gave me some instructions to try in order to get it working. I'm inserting a 4.3 ramdisk into a 4.2 AOSP ktoonsez verizon gs4 kernel, and replacing the boot.img in the 4.3 i9505 rom. I now know that I had accidentally inserted the wrong version kernel, and thats what caused my problems.
Click to expand...
Click to collapse
lahma69 were u able to do software upgrade on your phone?
and I am happy for you, mine still have same problems like I mentions up there, I still get error and no command in root and I cant get software update... as soon I will be able to figure this out that will mean that my phone is 100% able to go back to Verizon that's one thing but then I will now for future because really want to make this phone a Europe compatible phone...
SaNNeK said:
lahma69 were u able to do software upgrade on your phone?
and I am happy for you, mine still have same problems like I mentions up there, I still get error and no command in root and I cant get software update... as soon I will be able to figure this out that will mean that my phone is 100% able to go back to Verizon that's one thing but then I will now for future because really want to make this phone a Europe compatible phone...
Click to expand...
Click to collapse
My phone seems to be at 100%. I never do software updates through Verizon so I would not know if thats working or not. After I flashed the stock image in ODIN and rerooted my device, I immediately flashed TWRP through Goomanager and reflashed my nandroid (Eclipse TW rom.) Everything is running well and my phone isn't warm. Why are you trying to do a software update? I think there is an update now that can't be rooted, so you definitely don't want to do that...
I tried several things to get the i9505 4.3 rom running on my device. You can get an idea of what I did by reading this thread: http://forum.xda-developers.com/showthread.php?t=2253528&page=779 Scroll down to post #7785 and that is mine. I never did get it to boot... Let me know if you need anything else.
root problem and upgrate
So I did exactly how xda web site was saying about going back to stock and all of that.
It worked, I can run to os and I have original root.
Still have couple of problems,
1.when u in recovery I see error and no command right below android guy. also I see new info in yellow color, below regular blue recovery screen option. (pic1)
2. information in yellow color is follow: (pic 2)
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the csc-code:VZN
successfully applied multi-CSC.
never see in before, don't know what to do..
3. I cant do regular Verizon software update. S4 resets it self and goes to recovery where is trying to do update but ends um saying error and then is going back to os and its saying that update was not that and that there were no changes applied...(pic 3)
I still need your help guys...
SaNNeK said:
So I did exactly how xda web site was saying about going back to stock and all of that.
It worked, I can run to os and I have original root.
Still have couple of problems,
1.when u in recovery I see error and no command right below android guy. also I see new info in yellow color, below regular blue recovery screen option. (pic1)
2. information in yellow color is follow: (pic 2)
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the csc-code:VZN
successfully applied multi-CSC.
never see in before, don't know what to do..
3. I cant do regular Verizon software update. S4 resets it self and goes to recovery where is trying to do update but ends um saying error and then is going back to os and its saying that update was not that and that there were no changes applied...(pic 3)
I still need your help guys...
Click to expand...
Click to collapse
Did you see what I said about doing Samsung software updates? The rooting threads for the Verizon GS4 say that the new VRUAME7 OTA update can't be rooted. After flashing the stock image from oden, why don't you reroot your device according to http://forum.xda-developers.com/showthread.php?t=2290798 and then install Goomanager, click the menu key, click "Install open recovery script" and that will install TWRP recovery. From there, flash a verizon rom of your choice and all should be well, no? I only use TWRP so I can't give you any input on other recoveries. Make sure you didn't somehow get updated to VRUAME7.
township japinove
lahma69 said:
My phone seems to be at 100%. I never do software updates through Verizon so I would not know if thats working or not. After I flashed the stock image in ODIN and rerooted my device, I immediately flashed TWRP through Goomanager and reflashed my nandroid (Eclipse TW rom.) Everything is running well and my phone isn't warm. Why are you trying to do a software update? I think there is an update now that can't be rooted, so you definitely don't want to do that...
I tried several things to get the i9505 4.3 rom running on my device. You can get an idea of what I did by reading this thread: http://forum.xda-developers.com/showthread.php?t=2253528&page=779 Scroll down to post #7785 and that is mine. I never did get it to boot... Let me know if you need anything else.
Click to expand...
Click to collapse
Well I am not that good with all of it... I don't know a lot of meanings of all this like TWRP, Eclipse TW rom, or what you said u did on post #7785
so I am just trying to be able to make it run like new, and then if I do that I will try to work on my s3 and practice on that...
I am beginner in it... plus my English abilities are not that great, so I really don't know which root is the best or how to do it with out messing up entire phone. I love to dig into it, and my s4 was just laying broken for past month and I worked on in today with you guys and its almost working... I almost made claim from insurance for new phone but this one starts working today..
and looks like everything is fine with it
except root errors and no commands ,I cant wipe cash because its crashing and restarting and I cant do that software update, and I have that manual multi csc note in recovery system like I mention just on top with pictures...
SaNNeK said:
Well I am not that good with all of it... I don't know a lot of meanings of all this like TWRP, Eclipse TW rom, or what you said u did on post #7785
so I am just trying to be able to make it run like new, and then if I do that I will try to work on my s3 and practice on that...
I am beginner in it... plus my English abilities are not that great, so I really don't know which root is the best or how to do it with out messing up entire phone. I love to dig into it, and my s4 was just laying broken for past month and I worked on in today with you guys and its almost working... I almost made claim from insurance for new phone but this one starts working today..
and looks like everything is fine with it
except root errors and no commands ,I cant wipe cash because its crashing and restarting and I cant do that software update, and I have that manual multi csc note in recovery system like I mention just on top with pictures...
Click to expand...
Click to collapse
Whats your build number in Settings -> About Phone ?
lahma69 said:
whats your build number in settings -> about phone ?
Click to expand...
Click to collapse
jdq39.i545vruamdk
Working progress
SaNNeK said:
jdq39.i545vruamdk
Click to expand...
Click to collapse
so when I will learn how to fix my phone to 100%.
Then I will experiment with it and try to learn and install more roots if I will learn how to fix first... so I will not panic like I did this time... I was just completely lost, and I need to take is step by step... don't get me wrong... I love doing that kinda stuff I build my first pc when I was 10 years old... back on old good windows 95
SaNNeK said:
so when I will learn how to fix my phone to 100%.
Then I will experiment with it and try to learn and install more roots if I will learn how to fix first... so I will not panic like I did this time... I was just completely lost, and I need to take is step by step... don't get me wrong... I love doing that kinda stuff I build my first pc when I was 10 years old... back on old good windows 95
Click to expand...
Click to collapse
Do you currently have root? To check, you can run the "SuperUser" app. If you don't have it, download it from the Play store. After installing it, run it, and a box should pop up asking you for superuser permissions. Click "Grant." If a message pops up that says something like "Superuser has been granted superuser permissions," then you have root. If you don't have root, you need to get it. Follow the instructions at http://forum.xda-developers.com/showthread.php?t=2290798 . After performing those instructions, and verifying you have root, you need to download an application called "Goomanager" from the play store. After installing and opening it, click your "Menu" key (bottom left hand corner of your phone.) A menu will pop up. Click "Install open recovery script." Click Yes or Ok to all the pop up messages. After that completes, you will have TWRP recovery installed. Your recovery is what you boot your phone to in order to flash new roms, kernels, etc. In order to boot into recovery, turn off your phone completely, click and hold your volume up button, and power on your phone (while still holding volume up.) You should see some tiny blue text pop up in the top left hand corner of your screen that saying "Opening recovery" (or something to that effect.) Once you see that text, you can let go of volume up, and you will boot into TWRP. Let me know if you get this far...
And by the way, for the love of God, do not do any Samsung system updates.
lahma69 said:
And by the way,for the love of God, do not do any Samsung system updates.
Click to expand...
Click to collapse
And thats the most important part, because if you do you will lose root and your ability to customize your phone. In layman's terms? You will be re-VZ-navigated.
I am having a similar issue. Got the "Samsung Custom" boot screen with no boot to the OS after clean wipe and install of Hyperdrive 7. Since then I have been troubleshooting the issue and have tried many things including the "No-Wipe Factory Image". Once complete I am still getting the Samsung Custom boot screen and no loading of the OS.
Any ideas as to what I can try.
Thanks in advance,
Tony
lahma69 said:
Do you currently have root? To check, you can run the "SuperUser" app. If you don't have it, download it from the Play store. After installing it, run it, and a box should pop up asking you for superuser permissions. Click "Grant." If a message pops up that says something like "Superuser has been granted superuser permissions," then you have root. If you don't have root, you need to get it. Follow the instructions at http://forum.xda-developers.com/showthread.php?t=2290798 . After performing those instructions, and verifying you have root, you need to download an application called "Goomanager" from the play store. After installing and opening it, click your "Menu" key (bottom left hand corner of your phone.) A menu will pop up. Click "Install open recovery script." Click Yes or Ok to all the pop up messages. After that completes, you will have TWRP recovery installed. Your recovery is what you boot your phone to in order to flash new roms, kernels, etc. In order to boot into recovery, turn off your phone completely, click and hold your volume up button, and power on your phone (while still holding volume up.) You should see some tiny blue text pop up in the top left hand corner of your screen that saying "Opening recovery" (or something to that effect.) Once you see that text, you can let go of volume up, and you will boot into TWRP. Let me know if you get this far...
And by the way, for the love of God, do not do any Samsung system updates.
Click to expand...
Click to collapse
as my understanding its not.. I just did that no wipe recovery...
sorry I was out of town today... so I assume I will have to do root but which one is the best? there is so many different ones...
I recently installed the update 4.3 for my phone, which blocked the only thing I use the phone for free HOTSPOT. I tried to go back to 4.1.2 and obviously messed up somewhere along the way. Presently I can boot to download screen and recovery, but NOTHING works. Anything I try to install I get an error message. Currently, when I try to boot I get "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help." Don't want to do that, since they already told me they will not revert back to previous software version.
I have Odin 3.09 installed, USB driver for my phone installed and downloaded multiple tar and md5 files that are the correct ones for my phone. When I try to install I get FAILED! every time. I am putting it in the PDA slot, with proper check marks.
Please help me, I will give additional details as you see fit, don't want to clog up the thread with everything I tried, like unlocking bootloader, installing custom recovery, etc.
I'll be here all day, hopefully I can get some quick responses.
duffycoug said:
I recently installed the update 4.3 for my phone, which blocked the only thing I use the phone for free HOTSPOT. I tried to go back to 4.1.2 and obviously messed up somewhere along the way. Presently I can boot to download screen and recovery, but NOTHING works. Anything I try to install I get an error message. Currently, when I try to boot I get "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help." Don't want to do that, since they already told me they will not revert back to previous software version.
I have Odin 3.09 installed, USB driver for my phone installed and downloaded multiple tar and md5 files that are the correct ones for my phone. When I try to install I get FAILED! every time. I am putting it in the PDA slot, with proper check marks.
Please help me, I will give additional details as you see fit, don't want to clog up the thread with everything I tried, like unlocking bootloader, installing custom recovery, etc.
I'll be here all day, hopefully I can get some quick responses.
Click to expand...
Click to collapse
63 views but no replies? Maybe I'm in the wrong place? Is there anyone here who can help or point me to another forum?
duffycoug said:
63 views but no replies? Maybe I'm in the wrong place? Is there anyone here who can help or point me to another forum?
Click to expand...
Click to collapse
This is a GS3 correct? Did you unlock the bootloader? if you didn't unlock the bootloader then you will get this message. I had the same issue with my girlfriends SGS3 on verizon.
I followed the EXACT directions that were posted...if flashing VRALEC bootchain unlocks the bootloader than yes. I followed them step by step.
The good news is though, I finally gave up and hit accept on the software update and figured I'd just pay the extra $20 for the hotspot that was free on 4.1.2, but to my surprise the update failed. I still have my 4.1.2, my free hotspot and everything functions. Whatever I did messed up my phone enough to block the update, so I'm happy. Pretty crazy though that the methods followed to the T didn't work over and over again. I simply cannot root my phone no matter what I try. I'd love for someone to physically have my phone and try it with me present.
duffycoug said:
I recently installed the update 4.3 for my phone, which blocked the only thing I use the phone for free HOTSPOT. I tried to go back to 4.1.2 and obviously messed up somewhere along the way. Presently I can boot to download screen and recovery, but NOTHING works. Anything I try to install I get an error message. Currently, when I try to boot I get "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help." Don't want to do that, since they already told me they will not revert back to previous software version.
I have Odin 3.09 installed, USB driver for my phone installed and downloaded multiple tar and md5 files that are the correct ones for my phone. When I try to install I get FAILED! every time. I am putting it in the PDA slot, with proper check marks.
Please help me, I will give additional details as you see fit, don't want to clog up the thread with everything I tried, like unlocking bootloader, installing custom recovery, etc.
I'll be here all day, hopefully I can get some quick responses.
Click to expand...
Click to collapse
give this a shot for verizon s3: http://forum.xda-developers.com/showthread.php?t=2581166. It will provide you with directions on how to flash the stock recovery and bootloader. My S3 would not turn on at all until I tried this method.
Hi all,
I'm having trouble getting Safestrap to install and work properly on my VerizonSG4. Phone is rooted with stock ROM and still on 4.3 with updates and notifications blocked.(SDM frozen with TB) Other mods include Exposed Framework using 2 modules,Greenify, Busybox, and a couple other root dependent apps that are not likely to be the issue. The problem I'm having is that upon getting Safestrap to install (which took multiple attempts) it will open to the screen where you can choose to install or uninstall recovery and when I hit install it does its thing but shows "State: Not Installed". However, I DO get a little pop up at the bottom of the screen that says" Installation Complete". Safe System says " Not Active" and " Reboot to Recovery" is grayed out so that I can't select it. Manual reboot into recovery brings up stock recovery so I'm not sure what's going on. I've tried everything I can think of to make it work including defrosting SDM, disabling my antivirus, verifying that USB debugging is enabled, etc. So I'm frustrated and could use some insight. I'm obviously missing something or doing something wrong so any help would be greatly appreciated. Oh, and the apk that I downloaded was Safestrap-JFLTEVZW-3.71which is supposed to be the correct on for Verizon MK2.
Thanks in advance
markctco said:
Hi all,
I'm having trouble getting Safestrap to install and work properly on my VerizonSG4. Phone is rooted with stock ROM and still on 4.3 with updates and notifications blocked.(SDM frozen with TB) Other mods include Exposed Framework using 2 modules,Greenify, Busybox, and a couple other root dependent apps that are not likely to be the issue. The problem I'm having is that upon getting Safestrap to install (which took multiple attempts) it will open to the screen where you can choose to install or uninstall recovery and when I hit install it does its thing but shows "State: Not Installed". However, I DO get a little pop up at the bottom of the screen that says" Installation Complete". Safe System says " Not Active" and " Reboot to Recovery" is grayed out so that I can't select it. Manual reboot into recovery brings up stock recovery so I'm not sure what's going on. I've tried everything I can think of to make it work including defrosting SDM, disabling my antivirus, verifying that USB debugging is enabled, etc. So I'm frustrated and could use some insight. I'm obviously missing something or doing something wrong so any help would be greatly appreciated. Oh, and the apk that I downloaded was Safestrap-JFLTEVZW-3.71which is supposed to be the correct on for Verizon MK2.
Thanks in advance
Click to expand...
Click to collapse
After rooting your phone with presumably saferoot did you open up SuperSu and update it's binary?
Sounds like a Superuser problem. Either open up SuperSu and update binary the " normal" way or run saferoot again if that doesn't work and then update binary. Then you should be OK to install SafeStrap.
Sent from my SCH-I545 using Tapatalk
Solved it!
Mistertac said:
After rooting your phone with presumably saferoot did you open up SuperSu and update it's binary?
Sounds like a Superuser problem. Either open up SuperSu and update binary the " normal" way or run saferoot again if that doesn't work and then update binary. Then you should be OK to install SafeStrap.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Thanks for the response, and I actually figured it out last night. But you were on the right track. After trying a download from a different source the apk installed, opened up and showed that I wasn't rooted! Surprised me because the app itself needed super user rights itself so I knew I was rooted. Turns out I needed to have the paid/full version of SuperSU! Bought it and I now have Safestrap. I know I should probably always purchase the full versions of such high tech apps but damn it would have been nice if someone...anyone would have said that. I'm guessing there are other versions of SuperUser that may work differently right out of the box? IDK but I'm up and running and grateful that I didn't brick my phone. Been down that road before and know that it doesn't take much to mess things up.
Anyway, thanks to all that read and maybe this will help someone else
markctco said:
Thanks for the response, and I actually figured it out last night. But you were on the right track. After trying a download from a different source the apk installed, opened up and showed that I wasn't rooted! Surprised me because the app itself needed super user rights itself so I knew I was rooted. Turns out I needed to have the paid/full version of SuperSU! Bought it and I now have Safestrap. I know I should probably always purchase the full versions of such high tech apps but damn it would have been nice if someone...anyone would have said that. I'm guessing there are other versions of SuperUser that may work differently right out of the box? IDK but I'm up and running and grateful that I didn't brick my phone. Been down that road before and know that it doesn't take much to mess things up.
Anyway, thanks to all that read and maybe this will help someone else
Click to expand...
Click to collapse
I'm not sure why you had to get a paid version of su. I had the SU zip and installed it as part of the upgrade/downgrade method
sent by baja kitkat S4
Definitely shouldn't need the paid version but hey good to support Chainfire anyways.
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Definitely shouldn't need the paid version but hey good to support Chainfire anyways.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Yes, I found that odd also. When I switched to the other apk download it installed but said I did not have root, so I backed out one step and under the apk download that I selected was text in red that said "full version of SuperSu is required to complete this operation." So I paid for the full version, rebooted and everything worked fine from there. At that point the price was worth it, plus I typically use free versions of apps if I can get away with it so by supporting the Dev, as stated, perhaps I made a small deposit in the karma bank
Now I'm just trying to figure out if I need to do a factory reset before installing Hyperdrive. This is not my first ROM install but is under this format, so i want to take every precaution. Any suggestions? Leaning towards doing it except for concern about my phone downloading KitKat before I can reinstall TB and block it. Maybe I just need to be quick fingered. Again, open for suggestions.
Thanks in advance
markctco said:
Yes, I found that odd also. When I switched to the other apk download it installed but said I did not have root, so I backed out one step and under the apk download that I selected was text in red that said "full version of SuperSu is required to complete this operation." So I paid for the full version, rebooted and everything worked fine from there. At that point the price was worth it, plus I typically use free versions of apps if I can get away with it so by supporting the Dev, as stated, perhaps I made a small deposit in the karma bank
Now I'm just trying to figure out if I need to do a factory reset before installing Hyperdrive. This is not my first ROM install but is under this format, so i want to take every precaution. Any suggestions? Leaning towards doing it except for concern about my phone downloading KitKat before I can reinstall TB and block it. Maybe I just need to be quick fingered. Again, open for suggestions.
Thanks in advance
Click to expand...
Click to collapse
You should have plenty of time. I've flashed back to stock so many times and never had that update pop up before I could freeze SDM
I have an MDK phone so I'm not 100% up to speed on what you should do... @decaturbob has done it all and I'm sure would help send you down the right path
Sent from my SCH-I545 using Tapatalk
markctco said:
Yes, I found that odd also. When I switched to the other apk download it installed but said I did not have root, so I backed out one step and under the apk download that I selected was text in red that said "full version of SuperSu is required to complete this operation." So I paid for the full version, rebooted and everything worked fine from there. At that point the price was worth it, plus I typically use free versions of apps if I can get away with it so by supporting the Dev, as stated, perhaps I made a small deposit in the karma bank
Now I'm just trying to figure out if I need to do a factory reset before installing Hyperdrive. This is not my first ROM install but is under this format, so i want to take every precaution. Any suggestions? Leaning towards doing it except for concern about my phone downloading KitKat before I can reinstall TB and block it. Maybe I just need to be quick fingered. Again, open for suggestions.
Thanks in advance
Click to expand...
Click to collapse
the steps listed in surge's method are pretty easy and there is a video. Once you have rooted NC5 deox rom installed, then you can flash another rom right over the top as you would normally do. I installed Bajarom.
- roms go in stock slot
- be sure to flash SU update.zip (a step in safestrap right after you flash hyperdrive)
decaturbob said:
the steps listed in surge's method are pretty easy and there is a video. Once you have rooted NC5 deox rom installed, then you can flash another rom right over the top as you would normally do. I installed Bajarom.
- roms go in stock slot
- be sure to flash SU update.zip (a step in safestrap right after you flash hyperdrive)
Click to expand...
Click to collapse
Ok, thanks, but now I'm hung up again. But first of all let me say that there are numerous methods to be found online and I'm not familiar with surge's method, plus I'm not sure exactly how or when to flash the SU update .zip you mention. With that being said, after getting Safestrap to run I decided to flash a Hyperdrive ROM. Following several a combination of instructions and videos, I settled on Hyperdrive RLS12 as it claims to work with 4.3/MK2. But I've also seen that I need to flash the correct module, in this case JFLTEVZW-MK2-modules.zip file. There are conflicting instructions as to whether to flash both zips together or to flash the ROM and then the module just before rebooting. I've also read that I need to wipe cache etc. before rebooting.
Long story short, no matter what I try, I always get the same results...I see the Verizon Galaxy S4 logo followed by a black screen followed by a new boot audio? followed by over 30 minutes of black screen and a very hot battery. I have wiped rom slots between flashes, tried different ROM slots, just about everything I can think of besides the SU update. So perhaps someone can provide some detail on that step and some clarity on the other steps that vary from source to source.
I'm sure I'm doing something wrong but have gotten to a point where I'm just going to leave it alone for a while and use my stock ROM until I can get some help UGHHH
Thanks in advance
markctco said:
Ok, thanks, but now I'm hung up again. But first of all let me say that there are numerous methods to be found online and I'm not familiar with surge's method, plus I'm not sure exactly how or when to flash the SU update .zip you mention. With that being said, after getting Safestrap to run I decided to flash a Hyperdrive ROM. Following several a combination of instructions and videos, I settled on Hyperdrive RLS12 as it claims to work with 4.3/MK2. But I've also seen that I need to flash the correct module, in this case JFLTEVZW-MK2-modules.zip file. There are conflicting instructions as to whether to flash both zips together or to flash the ROM and then the module just before rebooting. I've also read that I need to wipe cache etc. before rebooting.
Long story short, no matter what I try, I always get the same results...I see the Verizon Galaxy S4 logo followed by a black screen followed by a new boot audio? followed by over 30 minutes of black screen and a very hot battery. I have wiped rom slots between flashes, tried different ROM slots, just about everything I can think of besides the SU update. So perhaps someone can provide some detail on that step and some clarity on the other steps that vary from source to source.
I'm sure I'm doing something wrong but have gotten to a point where I'm just going to leave it alone for a while and use my stock ROM until I can get some help UGHHH
Thanks in advance
Click to expand...
Click to collapse
have you looked at any youtube videos concerning S4 and safestrap?
decaturbob said:
have you looked at any youtube videos concerning S4 and safestrap?
Click to expand...
Click to collapse
Absolutely! But good news, phone is now booting! I tried flashing both zips together and it's working...at least I think it is. Displaying what I think is Google Play Edition boot image, 4 dots, yellow green red and blue zooming in and out. Not sure how long this is supposed to go on but I'm further along than previously. Any suggestions in case I end up in a boot loop or how long to wait to decide?
markctco said:
Absolutely! But good news, phone is now booting! I tried flashing both zips together and it's working...at least I think it is. Displaying what I think is Google Play Edition boot image, 4 dots, yellow green red and blue zooming in and out. Not sure how long this is supposed to go on but I'm further along than previously. Any suggestions in case I end up in a boot loop or how long to wait to decide?
Click to expand...
Click to collapse
Did you check the thread for compatibility of roms with ss?
sent by baja kitkat S4
decaturbob said:
Did you check the thread for compatibility of roms with ss?
sent by baja kitkat S4
Click to expand...
Click to collapse
Yup! As a matter of fact this is the video I watched that shows Hyperdrive RSL12 on the exact same phone as mine with 4.3 MK2 build.I think this is also the one that suggests flashing the module at the end. I've watched so many videos I can't remember which ones say what.
Am I missing something? I've made sure that I have USB debugging checked as well as unknown sources before flashing, I've tried flashing both zips at the same time and individually, even tried again without selecting any music players besides the Samsung one and not picking any audio mods when setting up the rom as per someones post on some blog somewhere. I've changed boot image, keyboards...I'm just about over this ROM. It can clearly be used with 4.3 but just not for me I quess? I've even considered backing up my stock rom and doing a factory reset on my phone and then starting from scratch. I'm just hoping I don't have to update to KitKat, which by the way is what Hyperdrive's website states you have to do, but this video contradicts that. UGHHH AGAIN!
http://www.youtube.com/watch?v=pA8cV3-r3oU
Wow, really? Nothing? No one? I thought this was where all the Android Root and Rom specialist hung out? Am I posting in the wrong thread or something? I cannot be the only one with this problem, can I?
markctco said:
Wow, really? Nothing? No one? I thought this was where all the Android Root and Rom specialist hung out? Am I posting in the wrong thread or something? I cannot be the only one with this problem, can I?
Click to expand...
Click to collapse
Alright since your trying Rls12 this should be easy since that's for Mk2.. Which your on.
Hop into SafeStrap and create a ROM slot. After its created activate that ROM slot. Then for good measure once your on that ROM slot wipe it.. Factory data reset. Then proceed to flash the Hyperdrive zip. Once that's finished don't leave SafeStrap until you'll flash those modules.
Then you can wipe cache and Dalvic again before rebooting.
If that's still not working for you I'm not sure where the problem lies. You're using SafeStrap v3.71 right?? Not version 3.72..
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Alright since your trying Rls12 this should be easy since that's for Mk2.. Which your on.
Hop into SafeStrap and create a ROM slot. After its created activate that ROM slot. Then for good measure once your on that ROM slot wipe it.. Factory data reset. Then proceed to flash the Hyperdrive zip. Once that's finished don't leave SafeStrap until you'll flash those modules.
Then you can wipe cache and Dalvic again before rebooting.
If that's still not working for you I'm not sure where the problem lies. You're using SafeStrap v3.71 right?? Not version 3.72..
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Thanks for responding! And yes I'm using that version of Safestrap and did everything you mentioned as per this video:
http://www.youtube.com/watch?v=l4F5UYDcQ5A
The only thing I can think of comes from something someone else mentioned about updating superuser binaries which made me realize that SuperSu, which is what I have doesn't appear to have that option. I checked the Play Store and there is the original Super User apk that I've used before to root other versions before all this bootloader crap started. I remember updating binaries in that version...I think. It may have been an option in CWM which I've also used. Could that be the issue? SuperSu acts just like Super User, asking for permissions and whatnot, but maybe Safestrap needs the other version. I think I'm going to uninstall or freeze (better idea) SuperSu and install the regular SuperUser. What gets me thought is that they are both developed by Chainfire, so I'm not sure what the difference would be. I do know that something is not right because I'm confident I'm doing everything as instructed.
HOT DAMN! I got it! It was a SuperSu issue, just took me a bit to figure out how to update binaries. It doesn't just have a button for that, had to uninstall and reinstall newest version.
Wow, what a trip that was! And I love the ROM.Gotta go and play now though
Thanks for everyones help and patience!
markctco said:
Hi all,
I'm having trouble getting Safestrap to install and work properly on my VerizonSG4. Phone is rooted with stock ROM and still on 4.3 with updates and notifications blocked.(SDM frozen with TB) Other mods include Exposed Framework using 2 modules,Greenify, Busybox, and a couple other root dependent apps that are not likely to be the issue. The problem I'm having is that upon getting Safestrap to install (which took multiple attempts) it will open to the screen where you can choose to install or uninstall recovery and when I hit install it does its thing but shows "State: Not Installed". However, I DO get a little pop up at the bottom of the screen that says" Installation Complete". Safe System says " Not Active" and " Reboot to Recovery" is grayed out so that I can't select it. Manual reboot into recovery brings up stock recovery so I'm not sure what's going on. I've tried everything I can think of to make it work including defrosting SDM, disabling my antivirus, verifying that USB debugging is enabled, etc. So I'm frustrated and could use some insight. I'm obviously missing something or doing something wrong so any help would be greatly appreciated. Oh, and the apk that I downloaded was Safestrap-JFLTEVZW-3.71which is supposed to be the correct on for Verizon MK2.
Thanks in advance
Click to expand...
Click to collapse
Edited
---------- Post added at 10:01 PM ---------- Previous post was at 09:57 PM ----------
Install Terminal Emulator. Type su and press enter. Then type setenforce 0 with a space after setenforce. Then press enter and reopen SafeStrap and all is well. The reboot recovery button will not be greyed out no more.
James- tech for a site dealing with Android day and night!
Hey guys... So I'm REALLY new at this whole rooting thing, so please forgive me if I am not aware of any terms related to rooting and such.
So basically what happened was this:
I decided to root my Galaxy S4 (sgh-i337 --- AT&T) using the towelroot method. I had to use this method because my phone is currently running Android 4.4.4 KitKat (TouchWiz) and it worked fine. SuperSU was installed, Root Checker said my phone was rooted, it was good. I tried to install CWM using Odin, and I got the "RESET" or "PASS" from Odin, which I thought that it meant that it worked. However, when I tried to go into Recovery Mode, it went into Stock Recovery Mode. I started to look at other tutorials, and I came across another one that involved flashing your phone's respective CWM .img file from your phone itself (transfer the .img to your phone's SD, and then flash it from your phone using the app, Flashify). But when I tried to go into Recovery mode to see if it worked, it gave me the yellow triangle with an error message, "System software is unauthorized by AT&T" or something like that. I tried to look at other posts, and there was a general idea that I needed to flash the stock Kernel. Now, the way I rooted the phone in the first place, I already had two different ones downloaded. One was flashed, towelroot was used, and then the second kernel (which was the one that originally on my phone before rooting) was flashed. After that, it was rooted. So me, being the complete noob I am at rooting, decided to re-flash both, in order, to see if that cleared up the error message when trying to get into Recovery Mode. This did not solve the problem either.
Again, I would like to apologize for my lack of knowledge on rooting and such, so please forgive me for my incompetence. And yes, I know that there are other threads on topics like this, but I have tried several things and it has not worked. Any help on how to fix this problem (and how to install CWM properly on my phone - since it is updated to 4.4.4 TouchWiz - or if I should use TWRP instead, because I intend on downloading the Kangapop GPE ROM(and how to install that for my specific model/software version)) is greatly appreciated, thanks!
Have a Verizon SCH-I535 running android 4.4.2 I have been trying in vain for two days now to root this phone and replace the stock recovery. I'm aiming for running clockworkmod recovery and cyanogenmod. I've followed their instructions using terminal and heimdall which DOES WORK and communicate with device.
Problem is EVERY TIME I boot to recovery and try to run anything...a stock zip to downgrade it says "failed to verify whole-file signature" and "signature verification failed."
The only thing I can do is run towelroot.apk, install superSU.apk, and use the stock ROM. Using ODIN is a waste of time and fails every file every time. At this point I'm honestly kinda amazed I don't have a brick I've done so many transfers! I also always wipe data/cache before I install zips off SDcard.
I'm out of answers. Oh! At one point my counter was too high and it was also saying, "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help. " I downloaded TriangleAway and it reset the counter back to zero and the error went away, but there for a while I couldn't even get to recovery (take battery out and cancel out of download mode FYI to boot back into device).
Samsung Kies is the closest glimmer of hope I've gotten. Twice now it has returned my phone back to stock; so I don't think its a hardware issue ie. bad ram or ROM memory...
I've rooted a couple older Galaxy S3's running 4.3 with no issue. It's been a couple years but that was a simple ODIN flash and I kept standard ROM/recovery as I was flashing carriers and didn't want to risk breaking anything.
I'd like to think I'm not an idiot, but what the hell am I missing. I've watched dozens of youtube videos and read hundreds of guides that all seem to work. It's something with this phone and kies or some type of heightened security...
Thanks in advance! You can also email me at [email protected]
Anyone? Even a, "Yeah, that's weird man! Sounds like you did everything right!" Would make me feel better...
Yes I've tried it and it worked make sure u have the unofficial safestrap the one for your phone and do the busy box and terminal emulator thing and it works if you try to install safestrap without the other things you will brick I did it twice but it very easy to unbrick so download busybox terminal emulator and the correct safestrap for you device and also I'm on 4.4.2 also and there is only one rom i have found that works and its called superliter there ya go hope I help would provide download links but I'm not home
Also I forgot to mention your bootloader won't be unlocked it'll be bypassed and you will have a custom recovery
androidforums.com/threads/verizon-verizon-bootloader-unlock.856221/page-2[/url]
forum.xda-developers.com/showthread.php?t=2605648
device specific safestrap recovery and image
4.4.2 has a 'locked bootloader' courtesy of Verizon! This is what has been giving me fits... Going to try to go back to totally stock 4.4.2 (right not my bootloader is the international version and locked out), then towelroot to root, then install root explorer/supersu, then I'll try safestrap and hopefully its the miracle cure!
schmitey said:
Have a Verizon SCH-I535 running android 4.4.2 I have been trying in vain for two days now to root this phone and replace the stock recovery. I'm aiming for running clockworkmod recovery and cyanogenmod. I've followed their instructions using terminal and heimdall which DOES WORK and communicate with device.
Problem is EVERY TIME I boot to recovery and try to run anything...a stock zip to downgrade it says "failed to verify whole-file signature" and "signature verification failed."
The only thing I can do is run towelroot.apk, install superSU.apk, and use the stock ROM. Using ODIN is a waste of time and fails every file every time. At this point I'm honestly kinda amazed I don't have a brick I've done so many transfers! I also always wipe data/cache before I install zips off SDcard.
I'm out of answers. Oh! At one point my counter was too high and it was also saying, "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help. " I downloaded TriangleAway and it reset the counter back to zero and the error went away, but there for a while I couldn't even get to recovery (take battery out and cancel out of download mode FYI to boot back into device).
Samsung Kies is the closest glimmer of hope I've gotten. Twice now it has returned my phone back to stock; so I don't think its a hardware issue ie. bad ram or ROM memory...
I've rooted a couple older Galaxy S3's running 4.3 with no issue. It's been a couple years but that was a simple ODIN flash and I kept standard ROM/recovery as I was flashing carriers and didn't want to risk breaking anything.
I'd like to think I'm not an idiot, but what the hell am I missing. I've watched dozens of youtube videos and read hundreds of guides that all seem to work. It's something with this phone and kies or some type of heightened security...
Thanks in advance! You can also email me at [email protected]
Click to expand...
Click to collapse
Verizon spends a pretty penny when it comes to making sure their devices................. stay theirs i guess you can say when it comes to the boot-loader! To my knowledge their isn't a way of getting around that with a permanent recovery flash that completely replaces Verizon's stock recovery. I can almost guaranteeing you that your problem is Verizon locked boot loader. Stock recoveries are solely only their for their technicians, so unless someone somehow has leaked a program that they use to get around that stuff without screwing it up, we the general public will never be able to flash anything permanent with any phones stock recovery unless we have their "secret" software! Every once in a while you do find a leaked one. I got lucky and found one for the T-mobile galaxy S6 Edge. As far as Odin I've noticed that the new versions seem to be very particular. Meaning if a dot or a space is misplaced anywhere in the zip or what not it will always fail. With my t-mobile S6 I spent two days figuring out I had to take a letter out of the name of the file i was trying to Odin. One letter that was it and once I did that it went flawlessly. Otherwise man i really don't know what to tell you, seems like ya followed the lines as described. Just remember its a Samsung Galaxy in my opinion Galaxies are unbrickable. Ive even pulled the cord in the middle of a Odin flash to see if i could brick it for good and was still able to go right into download mode and flash stock back onto it and everything working. So don't be afraid of bricking it. It will be way easier (sorry to say) for you to re-flash stock right now! Good luck bro wish you the best!
---------- Post added at 08:25 PM ---------- Previous post was at 08:18 PM ----------
schmitey said:
4.4.2 has a 'locked bootloader' courtesy of Verizon! This is what has been giving me fits... Going to try to go back to totally stock 4.4.2 (right not my bootloader is the international version and locked out), then towelroot to root, then install root explorer/supersu, then I'll try safestrap and hopefully its the miracle cure!
Click to expand...
Click to collapse
Are you able to disable Signature verification in the recovery?
Are you able to disable Signature verification in the recovery?
You can once I flash to say clockworkmod recovery. Stock I don't know of a way to...hence the Catch 22 there's no going forward and no going back...you're stuck with stock ROM/recovery but at least its rooted.
Well ****. Take my word for it you CAN brick a galaxy s3.
I used KIES to restore back to factory stock recovery etc etc.
I then used towelroot to root phone and install supersu. I then installed safestrap which totally worked! I was able to bypass the stock recovery and everything was running smoothly...I got overzealous and tried to install the cyanogenmod vrale6 bootloader zip through safestrap. I currently have a brick. It won't boot, no led's, no screen, no vibrate. I have another galaxy s3 charging batteries and swapped it out...removed sim and micro sd. I should have just installed the cyanogenmod app and done it that way...
So close and now I bricked it...
OK got my brick back by writing image to microSD card...pretty happy about that little trick. And that's utter nonsense about needing the same size card as your internal memory! I used a 32gig card on a 16gig phone...
Still trying but this locked 4.4.2 bootloader is BULL****. Going to try to downgrade but I'm not sure I'm going to end up with anything but a rooted stock rom...
So does anyone know of a way to downgrade or change recovery on Verizon 4.4.2?
I have s3 Verizon I-535 & clockworkmod recovery is not gonna work cuz of the locked bootloader, I used safestrap that's the only recovery for 4.4.2
slimcyril said:
I have s3 Verizon I-535 & clockworkmod recovery is not gonna work cuz of the locked bootloader, I used safestrap that's the only recovery for 4.4.2
Click to expand...
Click to collapse
Thanks for the reply. But with safestrap its a step in the right direction but every zip fails...so I don't see what it really does for us. Don't see myself ever running cyanogenmod at this rate unless you know something I don't...
schmitey said:
Thanks for the reply. But with safestrap its a step in the right direction but every zip fails...so I don't see what it really does for us. Don't see myself ever running cyanogenmod at this rate unless you know something I don't...
Click to expand...
Click to collapse
Well no zip has ever failed on my end using safestrap, does your device have init.d support?
No point me to it! I'm basically stock rom running safestrap atm. If you can walk me through this I'd be grateful.. Just remember I'm locked Verizon bootloader...
And may I say I finally got the I535 switched to selectel (was on a flashed sprint L710) and holy cow 4G LTE is fast...faster than my home internet!
schmitey said:
No point me to it! I'm basically stock rom running safestrap atm. If you can walk me through this I'd be grateful.. Just remember I'm locked Verizon bootloader...
And may I say I finally got the I535 switched to selectel (was on a flashed sprint L710) and holy cow 4G LTE is fast...faster than my home internet!
Click to expand...
Click to collapse
Go to mount on safestrap & see if your system partition is checked(mounted) e.t.c & go to playstore install universal init.d app
Note; uncheck verify signature checks if you're trying flash anything via recovery or else it will definitely fail
slimcyril said:
Go to mount on safestrap & see if your system partition is checked(mounted) e.t.c & go to playstore install universal init.d app
Note; uncheck verify signature checks if you're trying flash anything via recovery or else it will definitely fail
Click to expand...
Click to collapse
system partition is NOT checked within safestrap. Installed universal init.d but I'm out of my league on it... Init.d says stock kernel does not have support...