Upgrade to VRUFNC5 and keep root from NC2/MK2
I'm not responsible for anything negative that may come from using this method, and it should be treated as a WIP
Directions
1. Download Upgrade_I545VRUFNC5_fromNC2_with_Root.zip,, and Odin3-v3.09.zip
2. Download I545VRUFNC5-Stock-Root-Deodex.zip or I545VRUFNC5-Stock-Root-Odex.zip and put it on your external sdcard make sure you have the AT&T Safestrap 3.72 for KK installed (get it here) also download the SuperSu zip from here and put in on your External SD Card as well just in case.
3. Reboot into Safestrap and delete all rom slots (except stock) and wipe data, cache, system, and dalvik-cache via SS's wipe menu
4. Install I545VRUFNC5-Stock-Root-Deodex.zip or I545VRUFNC5-Stock-Root-Odex.zip on the stock slot and install the SuperSu zip after (optional-just incase) Once the install completes don't reboot, use SS's reboot menu and reboot into Download mode
5. Extract the contents of Upgrade_I545VRUFNC5_fromNC2_with_Root.zip into a folder of your choice then launch Odin 3.09
6. In "AP" input AP_VZW_I545VRUFNC5_I545VZWFNC5_1151670_REV06_user_low_ship_MULTI_CERT.tar.md5 and in "CP" input CP_VZW_I545VRUFNC5_I545VZWFNC5_1151670_REV06_user_low_ship_MULTI_CERT.tar.md5 then click start. Let it reboot and you should be done! ---
-Additional notes:
*If it still doesnt boot up then try flashing the CSC_VZW_I545VRUFNC5_I545VZWFNC5_1151670_REV06_user_low_ship_MULTI_CERT.tar.md5 in Odin under the "CSC" slot, I incuded this file in the zip just incase.
I545VRUFNC5-Stock-Root-Deodex.zip
MD5: c9ac7a4e62679693f43ac0c150761269
Features:
-rooted
-busybox
-deodex
-init.d
-setup wizard now completes, no force closes at boot, fixed majority of reported issues
-Knox is present (SuperSu apk will ask you to disable it when launched)
-write to external sd is enabled
-tethering is enabled
-no apks have been deleted
-no aroma installer
-extended reboot menu added
- NC5-patch1.zip- This patch will add toggles, remove the init.d toggle script so that you can save your own customized order of toggles and will fix the lock screen security types issue.
I545VRUFNC5-Stock-Root-Odex.zip
MD5: 6a4013e4e15acfc9b45e16ad7aac6ddf
Features:
-rooted
-busybox
-odex
-Knox is present (SuperSu apk will ask you to disable it when launched)
-write to external sd is NOT enabled
-tethering is NOT enabled
-no alterations have been made aside from root and busybox being added
-no aroma installer
-NC5-patch1.zip- This patch will add toggles, remove the init.d toggle script so that you can save your own customized order of toggles and will fix the lock screen security types issue.
-zip to add tethering here
-zip to add write to external sd fix here
Video of the process for MK2 to NC2 (note you don't have to flash the BL tar) video was made courtesy of @Tomsgt
VIDEO
Video - Verizon Galaxy S4**KitKat (NC5) Upgrade**With Root&Tethering thanks to @Scottchy014
How to Downgrade back to 4.2 MK2
I want to address somethings...im uploaded a new version of this zip Downgrade_I545VRUEMK2_I545VZWEMK2_1937946_REV06_us er_low_ship_MULTI_CERT.zip
that should get rid of the inital fail error and hopefully prevent some from getting the status 7 error
If your phone says and/or gives the "Kies emergency firmware" message, that doesn't mean you've bricked, it just means a flash didnt succeed all the the way through. Most of the time this is at the cache step. You might also get the "failed to mount /preload error". None of this means you're bricked. most of the time you can recover by following these steps in this order:
1. Flash I545VRUEMK2_Downgrade.tar.md5 --> Should no longer fail at cache; I accidentally included it in the first tar I uploaded but when i noticed the error I didn't think to much of it because i knew that step 3 would take care of it. Anyways no longer an issue.
2. Then reboot into download mode immediately after step one and flash flash I545VRUEMK2_System.tar.md5 --> should have no errors here, if you do try again. At this point, the phone should boot back into MK2, if it doesn't, then proceed to reboot into normal recovery and wipe data/factory reset. Next boot into download mode and go on to step 3.
3. Finally flash the I545VRUEMK2_cache.tar.md5 --> as long as you didn't deviate from the steps that I just listed then this should pass in Odin. The device should not give the /preload error after this step. If you do get an error then factory data reset in recovery then flash the zip from step 1 followed by the zip from this step (step 3) again , that is flash the cache tar.md5 again.
4. I was going to type something about Wifi...but this issue drives me crazy...(...its not a issue, learn adb) You need to use bypasslkm. Flash the NC2 hlos for sound to work and use bypasslkm for wifi
Code:
su
cd /data/local/tmp
chmod 755 bypasslkm
./bypasslkm
cd /system/lib/modules
rmmod dhd.ko
insmod dhd.ko
The status 7 failed to mount /preload error and why it happens:
Lets take a minute to go over why this happens and what it means. First what is /preload anyways? Well lets take a look at how it gets mounted, consider mount points below:
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/hidden", "/preload");
Click to expand...
Click to collapse
We can infer from the point arguements that /preload is the mount point for the "hidden" partition. Well then what is this "hidden" partition then you ask? Well hidden contains some useless crap Samsung uses to verify integrity of the system partition when in recovery
So the idea is to wipe data/factory reset in recovery followed by making sure to flash hidden.img.ext4 prior to cache.img.ext4. I think my inclusion of cache.img.ext4 on accident in the first tar is the root of the cause so ive uploaded a new one that doesnt contain it so it wont fail at step 1.
So essentially you cant flash a a full-wipe or no-wipe Odin tar to go back. You have to use a custom made Odin tar. Also for people getting the status 7 error where /preload fails to mount after flashing cache the solution is to boot into stock recovery and factory data reset followed by flashing hidden.img.ext4 via Odin or Heimdall.
Click to expand...
Click to collapse
Credits:
@Hashcode
@bajasur
@BeansTown106
@jeboo
@ted77usa
@muniz_ri
@rebel1699
@Maribou
@sextape
@Chainfire
@ryanbg
@jrkruse
@sbreen94
Changelog:
05/13/2014 - added odex stock root rom
Thanks. .. already downloaded all the files. . Will try in the morning. ..When I wake up. . And thanks again
Sent from my SCH-I545 using XDA Premium 4 mobile app
Will give this a whirl sometime after I get home at 3. Double Thanks!
Sent from my SCH-I545 using xda premium
My next phone will be whatever phone Surge goes with lol you're awesome at this stuff good work man
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
Awesome stuff man, thanks! Quick question, will this prevent me from updating to the final release, or will I be able to Odin to it?
RyaNov1333 said:
Awesome stuff man, thanks! Quick question, will this prevent me from updating to the final release, or will I be able to Odin to it?
Click to expand...
Click to collapse
Even though the leak says "noship", from looking at the files this seems like it might actually turn out to be the OTA. Even if its not, you'll still be able to take the OTA provided you flash the VRUNFC2 leak Odin tar first.
Sent from my SCH-I545 using XDA Premium 4 mobile app
So I'm taking it you have to have safestrap to do this method. No way to root without safestrap?
Sent from my SCH-I545 using xda app-developers app
this is freakin awesome! thanks man for your hard work!
i have a quick question. if the flash should happen to not work right- would i still be able to use it unrooted on the nc2 or do i have to downgrade back to mk2
Thanks for the guide! Before I do anything, as I'm carefully looking through the instructions, I seem to be missing the part where the file: jfltevzw-FN2-modules.zip is used? Can you point me to that part, I might just be stupid and overlooking it :cyclops:
Do I also install the jfltevzw-FN2-modules.zip file thru Safestrap?
You mentioned to download this file and then it is not talked about again.
blueboymj said:
Do I also install the jfltevzw-FN2-modules.zip file thru Safestrap?
You mentioned to download this file and then it is not talked about again.
Click to expand...
Click to collapse
Lol :laugh: That's the very thing I just asked in the post before yours. The file is listed in the OP but there is no mention as to when in the process to flash it
Hmm. Stuck on a Verizon splash screen.
lazer9 said:
Thanks for the guide! Before I do anything, as I'm carefully looking through the instructions, I seem to be missing the part where the file: jfltevzw-FN2-modules.zip is used? Can you point me to that part, I might just be stupid and overlooking it :cyclops:
Click to expand...
Click to collapse
blueboymj said:
Do I also install the jfltevzw-FN2-modules.zip file thru Safestrap?
You mentioned to download this file and then it is not talked about again.
Click to expand...
Click to collapse
Well I guess I didnt have to use it, but its useful to have it handy anyways
Sent from my SCH-I545 using XDA Premium 4 mobile app
Haha guess I hadn't refreshed my page and saw that Lazer
Thanks for getting back to us so quickly Surge.
Surge1223 said:
Well I guess I didnt have to use them, but its useful to have handy anyways
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the quick reply @Surge1223
So if I understand you correctly, the module mentioned would be used later once up and running if we didn't have wifi or something and could then re-enter SS and flash it once the whole process is completed? Oden, ATT SS installed, ect...
I see we have aosp browser. Is that in the leak build our was that thrown in there.
Sent from my SCH-I545 using Tapatalk
Anyone report success with this yet? While I'm confident I know what I'm doing, I'm scared to be the first, lol :laugh:
Well, crap. I'm stuck in the Verizon splash screen for the down grade as well. Safestrap is no longer showing either so I can't try to flash anything. Ideas?
I got it up and running. Is running smooth. I get an Android error on boot but that it's it
Sent from my SCH-I545 using Tapatalk
lazer9 said:
Anyone report success with this yet? While I'm confident I know what I'm doing, I'm scared to be the first, lol :laugh:
Click to expand...
Click to collapse
Looks like the post above yours might have worked.
I seem to be the first case of failure.
Related
This is something I realized when the init.d hack by naven was posted, it plain didn't work for me, and after some investigation i discovered that not all busybox versions had the run-parts applet.
It has come to my attention to that many users may not have the proper hack installed, at least the ones using my scripts, I had them check in /data for the zipaplign log and it was in fact not there.
I got it working by modding navens hack. Credit goes to him for his discovery.
Here is a link to the flashable zip. If you are using my scripts, check in /data for the zipalign log, if you don't have one, just flash this zip, reboot, and check again.
http://www.sendspace.com/file/9g6ngz
Thanks!
Edit (8/31/2011): Just so there is no confusion, this is not my new Speedy script, this is just a re-hack for init.d originally discovered by naven. This will just help those of you having problems with his hack. Obviously you need to be rooted and have recovery bootstrap.
Just flashed your zip. Log file in /data
Welcome back! Thanks for your work on the X2.
Sent from my DROID X2 using xda premium
Grapejelly!!
Sent from my DROID X2 using xda premium
Worked perfectly
Sent from my DROID X2 using XDA App
Is this a new version of your script then?
Do we have to flash this the same way with recovery (aka renaming it to update.zip) like i had to go with the manual gb update?
Nevermind, figured that out.. but why am i getting a signature verification on install? Where do i turn off sig verification?
SuBDivisions said:
Nevermind, figured that out.. but why am i getting a signature verification on install? Where do i turn off sig verification?
Click to expand...
Click to collapse
There is an option under advanced I think, in recovery, to enable/disable that.....
I dont have that option, unless now there is some other recovery peice im missing.. my recovery whichis Android System Recovery (3e) only has reboot, apply update, wipe data, wipe cache.
SuBDivisions said:
I dont have that option, unless now there is some other recovery peice im missing.. my recovery whichis Android System Recovery (3e) only has reboot, apply update, wipe data, wipe cache.
Click to expand...
Click to collapse
You need to use the modified boot -strap recovery available on this forum. D/L it & install it like any other app. When you open it, just read & follow the directions on the screen & you will get to the custom recovery where all good things flash from.
Sent from my DROID X2 using xda premium
SuBDivisions said:
I dont have that option, unless now there is some other recovery peice im missing.. my recovery whichis Android System Recovery (3e) only has reboot, apply update, wipe data, wipe cache.
Click to expand...
Click to collapse
You should be flashing this thru the Bootstrap Recovery, not the default Android Recovery.
Sent from my DROID X2 using Tapatalk
Ahh HA.. See i know i was missing something.. Thanks have been given.
Zip-align logs were not showing in /data/ for me, so I flashed this, and now they do.
I'm assuming that means the rest of the scripts weren't working either?
Cool. Going to flash this but need a quick question answered.
I have Busybox 1.19.0 installed. I downloaded "Busybox" from marketplace to install 1.18.4 but which location should I chose?
Options are /system/xbin/ or /system/bin/
Thanks
Sorry found this in original init.d hack thread:
BusyBox with run-parts binary, installed in /system/xbin - If you don't have BusyBox, you can download it from the market here.
Click to expand...
Click to collapse
hapyman said:
Cool. Going to flash this but need a quick question answered.
I have Busybox 1.19.0 installed. I downloaded "Busybox" from marketplace to install 1.18.4 but which location should I chose?
Options are /system/xbin/ or /system/bin/
Thanks
Sorry found this in original init.d hack thread:
Click to expand...
Click to collapse
You should be okay on 1.19.0 now, but busybox should always always be installed in xbin.
So which init is better or the working one?
gkitab said:
So which init is better or the working one?
Click to expand...
Click to collapse
Some people find that the re-hack (this thread) works (and the original does not), others find that the original hack works just fine. A way to test is to install my Speedy Gonzales scripts, reboot the phone, and then check in /data for a zipalign log. If not, then flash this re-hack.
I am running speedy. So should I us you init when using yours and his when trying his? How can we tell if yours is working and when using his if his is working? This is getting a bit confusing. I also noticed when I flashed speedy navens old oo got left behind. So I deleted al scripts in init folder and reflashed yours and all yours are now correct.
With his init and your script. Yours scripts are in there but no zipalign in data.
Should I start over by deleting unit folder flash your unit then speedy would that be the safe bet?
Thanks for staying.
gkitab said:
I am running speedy. So should I us you init when using yours and his when trying his? How can we tell if yours is working and when using his if his is working? This is getting a bit confusing.
Thanks for staying.
Click to expand...
Click to collapse
They are two separate things entirely. I posted the re-hack for those having troubles getting scripts to run with naven's original hack. The re-hack posted in this thread doesn't contain any init.d scripts, it's purely the hack. Like I said above, a good way to test his hack is to install my scripts (which it looks like you have), and then use a file manager like Root Explorer and navigate to /data, there should be a zipalign log, if there isn't then his hack isn't working.
Edit: Well, the biggest question is if the init hack you have installed is even working. I'm assuming you have naven's... try the above, let me know if the log is there or not.
I edited my post can you please check it and let me know what you think.
I do have his with your script.
I think I should I should delete init completely and start fresh with yours and your scripts. That sounds like safest bet. Or does naven init need to be there first then yours on top then your scripts. Thanks.
For all you Shotputterz heres the factory image we've been waiting for
assuming you have debug mode enabled, ADB and fastboot working properly
EDIT 1: REUP'D CWM mod
EDIT 2: reordered process to make more sense
Method:
1. Download the Beta CWM mod from rootzwikis credit to birdman EDIT:REUP'ED http://d-h.st/Fdp
2. Using fastboot, DO NOT FLASH Clockwork mod just use the syntax
"fastboot boot 'File path of clockwork mod image'
Note* this will boot directly into the recovery without permanently writing to the recovery and boot partition on the eMMC on the Nexus Qs board
3. Download the posted CWM factory backup posted
4. make the directory on the device and adb push the backup folder (unzipped) to /sdcard/clockworkmod/backup while in CWM recovery
*The device should show up in "adb devices" while in the CWM recovery*
5. *TEXT WILL BE REALLY SMALL! Now navigate with the Scroll wheel to backups and restore and tap the mute button to select.
*IF SOMETHING IS SELECTED IN ERROR THERE IS NO BACK BUTTON JUST REBOOT AND REDO FASTBOOT BOOT*
6. Now select restore and select the image folder
7.blah blah CWM Freaking MAGIC
8. Your Q is back to factory state
If someone wants to PM me or show me how to package this in a nicer CWM zip to install with a script let me know
http://d-h.st/yeo
*Note* I am NOT responsible if you brick your already bricked Nexus Q*
You sir get a beer, since my 2nd (dev) Q won't arrive until later this week, and mine was a shot put until this post.
If you happen to be in NYC before I move to SF, you get three beers.
Hoppy ones.
I am moving to SF
Did the reflash go smoothly?
fiveipads said:
I am moving to SF
Did the reflash go smoothly?
Click to expand...
Click to collapse
No unfortunately it didn't--I blew away all partitions other than bootloader so I can't, to my knowledge at least, push the zip since I can't adb.
I've got factory recovery, boot, system imgs but the system img won't push out because of fastboot's apparent inability to handle files that large (1GB exactly I believe).
...I guess I have to patiently await my second Q but the point of having two was to *use* one and have one for dev... rather than have one as a heavy reminder of my overzealous endeavors...
Hopefully I can give it more time while on this SF trip...
Boot into the cwm bootloader with fastboot without flashing. Adb will be enabled and you can push files the files while your in adb recovery. Try that and flash it.
Sent from my SPH-D710 using xda app-developers app
Does our Q's have internal memory.. if not wouldn't it be possible to run back up of off otg memory stick if recovery would support it
Sent from my Galaxy Nexus using xda premium
fiveipads said:
Boot into the cwm bootloader with fastboot without flashing. Adb will be enabled and you can push files the files while your in adb recovery. Try that and flash it.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
The problem I'm having is that ADB is not responding from CWM... at least not on a Windows machine. The drivers are fine as ADB was working in normal mode before my issue sprung up.
EDIT: As suspected Virtual Ubuntu on a Win host didn't see the device, Physical Ubuntu had no issue. NQ reloaded.
fiveipads said:
Boot into the cwm bootloader with fastboot without flashing. Adb will be enabled and you can push files the files while your in adb recovery. Try that and flash it.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Can we do this by say pushing the file to the download folder and then installing from zip?
And i know slightly off topic but once we've installed some apks for example, what's currently the best interface to use to navigate through the apps and use them?
How do I make a directory on Nexus Q
fiveipads said:
For all you Shotputterz heres the factory image we've been waiting for
assuming you have debug mode enabled, ADB and fastboot working properly
Method:
1. Download the posted CWM factory backup posted
2. make the directory on the device and adb push the backup folder (unzipped) to /sdcard/clockworkmod/backup
http://d-h.st/yeo
Click to expand...
Click to collapse
In step 2 you say make a directory for the file that is posted below. How do I create a directory on the Nexus Q? Currently my Q is stuck in a bootloop after trying to launch CWM from a Galaxy Nexus. If you could post command codes that would be awesome!
I figured it out. You can just follow step #4 and in CWM you can push the CWM Factory img to the /sdcard/Download/ folder and use CWM to unzip and launch.
Could someone please provide me the beta cwm image for Nexus Q? The links are all circular and point to
http://goo.im/devs/birdman/CWM-steelhead-beta.img
Which is dead...
discoltk said:
Could someone please provide me the beta cwm image for Nexus Q? The links are all circular and point to
http://goo.im/devs/birdman/CWM-steelhead-beta.img
Which is dead...
Click to expand...
Click to collapse
I've been trying to get ahold of this image too! Anyone?? anyone?? Bueller???
WildSatchmo said:
I've been trying to get ahold of this image too! Anyone?? anyone?? Bueller???
Click to expand...
Click to collapse
Me as well...not sure why I got this damn thing...lol
The edit didn't prompt an email to me even though I'm following the thread, so those of you looking for the clockworkmod beta image please take note that OP was kind enough to provide a working link to the image.
Thanks fiveipads!
Can someone post full backup please?
caioketo said:
Can someone post full backup please?
Click to expand...
Click to collapse
The link at the bottom still works for me...
http://d-h.st/yeo
..
ok this is really bothering me, i've restored with this factory image several times, and I have to do it again right now and I cannot seem to push this file folder to /sdcard/clockworkmod/backup
what am i doing wrong..
it should be:
adb push NexusQFactoryImage /sdcard/clockworkmod/backup/ (assuming the file is in same folder as adb which it is)
that's it right.... the extracted folder contents in a folder.. not the zip.. so i dont understand why this is not working. Everytime I go to CWM and try to restore it tells me nothing to restore...
what really bothers me is that i've done this a hundred times, and never had this problem..
UKROB86 said:
ok this is really bothering me, i've restored with this factory image several times, and I have to do it again right now and I cannot seem to push this file folder to /sdcard/clockworkmod/backup
what am i doing wrong..
it should be:
adb push NexusQFactoryImage /sdcard/clockworkmod/backup/ (assuming the file is in same folder as adb which it is)
that's it right.... the extracted folder contents in a folder.. not the zip.. so i dont understand why this is not working. Everytime I go to CWM and try to restore it tells me nothing to restore...
what really bothers me is that i've done this a hundred times, and never had this problem..
Click to expand...
Click to collapse
BUMP.. stuck in CWM unable to get a restorable file.. no idea why...
Download OneClickRestore (it's the factory image straight from Google with the needed fastboot files included)
Extract zip to OneClickRestore
Unplug Nexus Q
Plug in Nexus Q and place hand on it til the leds turn red then remove hand
Launch "flash-all.bat" from the OneClickRestore folder
You may need to do a full reset, it's hit or miss
Another option is push & flash (Nexus Q)uantum Singularity Project RTS ROM from CWM and again may need to hard reset.
RTS is
Based on stock 4.0.4 build IAN67K
Deodexed
Zip aligned
init.d Support
bash support
Busybox updated
Prerooted
Superuser
Updated Keymap (Home=Home, End=Back, Delete=Menu, Insert=Visualizer)
Lokifish Marz said:
Download OneClickRestore (it's the factory image straight from Google with the needed fastboot files included)
Extract zip to OneClickRestore
Unplug Nexus Q
Plug in Nexus Q and place hand on it til the leds turn red then remove hand
Launch "flash-all.bat" from the OneClickRestore folder
You may need to do a full reset, it's hit or miss
Another option is push & flash (Nexus Q)uantum Singularity Project RTS ROM from CWM and again may need to hard reset.
RTS is
Based on stock 4.0.4 build IAN67K
Deodexed
Zip aligned
init.d Support
bash support
Busybox updated
Prerooted
Superuser
Updated Keymap (Home=Home, End=Back, Delete=Menu, Insert=Visualizer)
Click to expand...
Click to collapse
The problem with putting Quantum singularity project on is that I can't turn on ADB debug, because i use a bluetooth mouse and keyboard, don't have an OTG mouse/keyboard, so somehow I need to be able to connect with adb to setup a bluetooth connected mouse/keyboard
I was thinking to install stock image, and then without wiping install Quantum SIngularity Project over top to preserve the settings for usb debug, on.
what's confusing to me is that i've restored the stock image many times before, and never had a problem.. that's why im wondering what the problem is.. if im typing something wrong.
I used the OneClickRestore as you said, and im just booting it up now
EDIT: didn't get past boot logo, i'll try again
So just to confirm this OneClickRestore is loading the stock nexus Q img right? I've never used it before I usually manually do it
EDIT: still stuck at the nexus q logo before home screen
do you see any error in my commands of trying to push the stock img folder (original post) to "/sdcard/clockworkmod/backup" ? I've done it many times before never had a problem
Hello, I have a verizon s4 and am using the safestrap method. After updating the hyperdrive rom and flashing the MK2modules.zip safestrap says the install was successfull but wifi still doesn't work. My baseband is MJ7 and my build number is MK2. Also I did a factory reset before updating.
Initially, hyperdrive was installed on the stock rom which I thought might be the problem so I installed a backup that had the original samsung rom there and installed hyperdrive to rom slot 1. I tried to flash the MK2 modules again and wifi still doesn't work. Any help would be appreciated.
You may want to try downloading the modules again. Worked like a charm for me with every rom I've installed. Did you install Hyperdrive into a rom slot other than stock? I can't flash much into the stock rom slot.
Sent from my SCH-I545 using Tapatalk
darkmagi83 said:
Hello, I have a verizon s4 and am using the safestrap method. After updating the hyperdrive rom and flashing the MK2modules.zip safestrap says the install was successfull but wifi still doesn't work. My baseband is MJ7 and my build number is MK2. Also I did a factory reset before updating.
Initially, hyperdrive was installed on the stock rom which I thought might be the problem so I installed a backup that had the original samsung rom there and installed hyperdrive to rom slot 1. I tried to flash the MK2 modules again and wifi still doesn't work. Any help would be appreciated.
Click to expand...
Click to collapse
I don't understand how you got to MJ7 baseband (radio/modem) and MK2 build. MK2 would have updated the baseband, normally.
However, there's a common problem that you may have run in to. The MK2 modules here are for the Verizon SCH-I545. There's no guarantee that those will work with any other vendor's phone.
What I'd do is to boot your stock slot, copy out the modules (/system/lib/modules), then flash them into the safestrap slot. I've posted instructions for doing this dozens of times already so I won't repeat.
k1mu said:
I don't understand how you got to MJ7 baseband (radio/modem) and MK2 build. MK2 would have updated the baseband, normally.
However, there's a common problem that you may have run in to. The MK2 modules here are for the Verizon SCH-I545. There's no guarantee that those will work with any other vendor's phone.
What I'd do is to boot your stock slot, copy out the modules (/system/lib/modules), then flash them into the safestrap slot. I've posted instructions for doing this dozens of times already so I won't repeat.
Click to expand...
Click to collapse
''
I understand the annoyance , could you please provide a link to the steps
Thanks
pbman1953 said:
I understand the annoyance , could you please provide a link to the steps
Click to expand...
Click to collapse
Here's what you do to recover your Wifi.
First, if you didn't overwrite the stock slot:
1. Boot your stock slot.
2. Copy the two files in /system/lib/modules to your EXTERNAL sdcard.
3. Boot the custom slot.
4. Use your favorite root file manager to mount /system read-write, then copy those files from the external sdcard into /system/lib/modules in your custom slot.
5. Reboot. Wifi should be back.
Second, if you flashed over the stock slot: :crying:
Well, you've written over the factory modules. You'll need to get them back.
A. Find someone with the same device as you that's unmodified and ask them for the contents of /system/lib/modules. Copy them to your /system/lib/modules.
B. Remove Safestrap and install a factory stock ROM. You can now use Safestrap to flash into a different slot and use the directions above.
If you INSIST on flashing over the factory ROM again (i.e. you haven't learned why that's a bad idea), then copy off the files to your external sdcard before you install Safestrap, then go to step 4 above after you finish flashing the custom ROM.
C. Take apart a factory ROM image and extract the contents of the /system/lib/modules directory onto your external sdcard. Go to step 4 above.
k1mu said:
Here's what you do to recover your Wifi.
First, if you didn't overwrite the stock slot:
1. Boot your stock slot.
2. Copy the two files in /system/lib/modules to your EXTERNAL sdcard.
3. Boot the custom slot.
4. Use your favorite root file manager to mount /system read-write, then copy those files from the external sdcard into /system/lib/modules in your custom slot.
5. Reboot. Wifi should be back.
Second, if you flashed over the stock slot: :crying:
Well, you've written over the factory modules. You'll need to get them back.
A. Find someone with the same device as you that's unmodified and ask them for the contents of /system/lib/modules. Copy them to your /system/lib/modules.
B. Remove Safestrap and install a factory stock ROM. You can now use Safestrap to flash into a different slot and use the directions above.
If you INSIST on flashing over the factory ROM again (i.e. you haven't learned why that's a bad idea), then copy off the files to your external sdcard before you install Safestrap, then go to step 4 above after you finish flashing the custom ROM.
C. Take apart a factory ROM image and extract the contents of the /system/lib/modules directory onto your external sdcard. Go to step 4 above.
Click to expand...
Click to collapse
I performed the first set of steps but it failed and I checked the ES program had the explorer on
pbman1953 said:
I performed the first set of steps but it failed and I checked the ES program had the explorer on
Click to expand...
Click to collapse
you flashed over your stock slot before, so you need to do the second set of steps.
edit: sorry thought u were the op
joshm.1219 said:
you flashed over your stock slot before, so you need to do the second set of steps.
edit: sorry thought u were the op
Click to expand...
Click to collapse
More of a head ache. I'll wait for kit kat 4.4 and the reinstall
Thanks for help
pbman1953 said:
I performed the first set of steps but it failed and I checked the ES program had the explorer on
Click to expand...
Click to collapse
Failed. Uh huh.
Can you possibly explain what you did and what happened?
k1mu said:
Failed. Uh huh.
Can you possibly explain what you did and what happened?
Click to expand...
Click to collapse
Copied from the stock folder to ext sd card then switched to hyperdrive rom and pasted in the folder you wrote
pbman1953 said:
Copied from the stock folder to ext sd card then switched to hyperdrive rom and pasted in the folder you wrote
Click to expand...
Click to collapse
If you just copied and pasted the permissions on the modules would have been rw-rw-rw-. The permissions on the modules need to be 0644. Copy and pasting them dooesnt change their permissions. You need to make sure the contents of the modules folder are owned by root (0) and have permissions set to rw-r--r--(0644).
Copy and paste the modules into /system/lib/modules as you did before then copy and paste the following into terminal line by line and dont modify the commands in any way:
Code:
su
mount -o remount,rw /system
cd /system/lib/modules
chmod 0644 *.ko
reboot
then hit enter to reboot.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
If you just copied and pasted the permissions on the modules would have been rw-rw-rw-. The permissions on the modules need to be 0644. Copy and pasting them dooesnt change their permissions. You need to make sure the contents of the modules folder are owned by root (0) and have permissions set to rw-r--r--(0644).
Copy and paste the modules into /system/lib/modules as you did before then copy and paste the following into terminal line by line and dont modify the commands in any way:
Code:
su
mount -o remount,rw /system
cd /system/lib/modules
chmod 0644 *.ko
reboot
then hit enter to reboot.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Just now I remembered that you have to switch on the permissions in tool area of the r/w . I did that then tried again and still failed. ES won't let me delete the old files or rename them.
I'm stuck because each time I try to copy to device/system/lib/modules it fails
pbman1953 said:
Just now I remembered that you have to switch on the permissions in tool area of the r/w . I did that then tried again and still failed. ES won't let me delete the old files or rename them.
I'm stuck because each time I try to copy to device/system/lib/modules it fails
Click to expand...
Click to collapse
Ok. Then open terminal type the following first:
Code:
su
mount -o remount, rw /system
Then copy and paste the modules In that folder and run the commands I typed in my previous post.
Surge1223 said:
Ok. Then open terminal type the following first:
Code:
su
mount -o remount, rw /system
Then copy and paste the modules In that folder and run the commands I typed in my previous post.
Click to expand...
Click to collapse
I got lucky!!
I rebooted a couple times, re-checked that the permissions in ES stuck in root explorer to all R/W's.
Then I went to device/ system/ lib/ modules and tried again to rename the existing 2 files and it worked. Then I copied in the 2 files need, rebooted for the last time and BINGO, working wifi
BIG thanks for all the time spent and help!!
I do have one weird issue.
On text receiving, I see the flash of the incoming message on the notificationbar but the response is not added to the conversation list
Files in /system/lib/modules
I've hit the same problem here- I was getting so many self-restarts and hangs from my ROM slot that I wiped it and reinstalled, and now WiFi won't turn on.
I'm running MI1 still (was happy for a long time, not not so), SafeStrapped, and have installed Hyperdrive RLS10.2 and the jfltevzw-MI1-modules. Phone works, 4G works. WiFi will not turn on.
I tried wiping Dalvik and cache, rebooting, then fixing permissions via Hyperdrive tweaks, but no luck on getting it to work.
I've read through the thread, but here's the thing: When I look through Stock device/system/lib/module, there aren't two files, but about nineteen or so in there. Which ones am I looking for?
Sorry to resurrect this, but I figure it's better than starting a whole new thread to ask the same question.
Since so many of us have to use Safestrap to use custom ROMs, thanks to Verizon, I thought that it would be reasonable to have a list of the currently compatible ROMs. I see a lot of threads and questions about ROMs "not working" with Safestrap that turn out to be people trying to flash AOSP ROMs instead of compatible TouchWiz (TW) ROMs.
I suggested this to Kennyglass123, who wisely suggested that I put one together.
I started with the official list of TW ROMs, and then added some that I found. I first communicated with most of the devs for these ROMs, and created the list based on their responses.
If you are a dev and your ROM is Safestrap-compatible, and you want your ROM added to the list, please PM me.
SO, here is the current list, with this format for each line:
ROM name [author/maintainer] (notes/link)
Safestrap-compatible ROMs
Bonestock v1.1.4 [andybones] (but only this version)
Eclipse S4 TW Edition v2.0 [nitroglycerine33] (4.2.2 version, not 4.3 yet)
Foxhound Diamond Dogs v3.6 [gigilie] (link)
Hyperdrive RLS13 [sbreen94] (link)
Jelly 'Beans' Build 7 [BeansTown106] (yes, for ME7)
Omega v19 [gigilie] (link)
Stock-Rooted-International MKF Base [jrkruse] (link)
PLEASE NOTE: I'm only reporting what people have told me. Please don't get upset with me if you're having trouble with a particular ROM.
Here is a link to the Safestrap thread (link).
Having a ROOTED phone IS A REQUIREMENT for using Safestrap.
PLEASE read the first two posts through entirely before trying it on your phone for the first time.
If you do not know what rooting is, or how to do it, please start at this thread (link).
Good luck!
I started this thread for safestrap compatible 4.3 ROMS:
http://forum.xda-developers.com/showthread.php?t=2630040
I'm loading each to verify myself.
decaturbob said:
I started this thread for safestrap compatible 4.3 ROMS:
http://forum.xda-developers.com/showthread.php?t=2630040
I'm loading each to verify myself.
Click to expand...
Click to collapse
Great minds.
Wish I'd seen this before starting my work!
I cede the ground to you sir.
jogawa said:
Great minds.
Wish I'd seen this before starting my work!
I cede the ground to you sir.
Click to expand...
Click to collapse
If you test out any Rom I haven't listed please post it...
Sent from my SCH-I545 using XDA Premium 4 mobile app
hi a small request for you need you help as can you create bootstrap for samsung galaxy grand2 SM-G7012 it also uses same 1.20GHz Qualcomm Snapdragon 400 firmware 4.3 JB
boot.img u can find here.
http://forum.xda-developers.com/show...2&postcount=10
you can find grand 2 thread here : http://forum.xda-developers.com/galaxy-grand-2
manan001 said:
hi a small request for you need you help as can you create bootstrap for samsung galaxy grand2 SM-G7012 it also uses same 1.20GHz Qualcomm Snapdragon 400 firmware 4.3 JB
boot.img u can find here.
http://forum.xda-developers.com/show...2&postcount=10
you can find grand 2 thread here : http://forum.xda-developers.com/galaxy-grand-2
Click to expand...
Click to collapse
Not understanding what you are asking or stating
Sent from my SCH-I545 using XDA Premium 4 mobile app
decaturbob said:
Not understanding what you are asking or stating
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I request can you create safestrap as custom recovery not available for samsung galaxy grand2 SM-G7102
Sent from my SM-G7102
manan001 said:
I request can you create safestrap as custom recovery not available for samsung galaxy grand2 SM-G7102
Sent from my SM-G7102
Click to expand...
Click to collapse
This thread had nothing to do with Safestrap development.
Sent from my SCH-I545 using XDA Premium 4 mobile app
vzw gs3 4.3 + morphology?
should i be able to ss flash morphology to stock 4.3? all i really want is themeing
because i understand morphology has an aroma installer and im not sure
Something I found....well didn't find...more came across is. I use hyper drive and installed it over the stock rom slot. Works wonders and haven't lost any gigs
Sent from my SCH-I545
Any 4.4 roms yet?
Sent from my SCH-I545 using xda app-developers app
peppersu812 said:
Any 4.4 roms yet?
Click to expand...
Click to collapse
Not for Safestrap. That won't happen until Verizon eventually releases Kit Kat.
Tbo I don't think they will release KitKat until s5 has been release. A marketing tool to get people to upgrade.
Sent from my SCH-I545 using Tapatalk
simple_fear85 said:
Something I found....well didn't find...more came across is. I use hyper drive and installed it over the stock rom slot. Works wonders and haven't lost any gigs
Sent from my SCH-I545
Click to expand...
Click to collapse
I tried it on stock slot and had lots of lag. It worked ok but was slow and laggy.
4.4.3 GPE ROM installed VIA Safestrap on my Verizon Samsung S4 i545 NC5.
peppersu812 said:
Any 4.4 roms yet?
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
I was able to get a fully functioning 4.4.3 GPE ROM installed VIA Safestrap on my Verizon Samsung S4 i545 NC5.
It takes a little bit of work because straight out the box there are issues with google apps and data not working. Some of my steps may not be necessary. The most important parts are the apns-conf as this made the phone and data work. Making SELinux permissive and of course the modules. Whether or not starting from stock made a difference I am not sure. I did it because I softbricked and had to restore with odin.
MAKE A BACKUP JUST IN CASE
This is how I did it.
1. I started with stock factory image of NC5. The no-wipe link http://forum.xda-developers.com/showthread.php?t=2735172 and installed with odin. I then rooted with towelroot, installed supersu, busybox from playstore and Safestrap v3.75 recovery http://forum.xda-developers.com/showthread.php?t=2793891.
2. I copied apns-conf from the etc folder on my phone to my download folder(any folder on your phone easily accessable from a computer will work).
3. Plugged phone into computer and copied apns-conf to my computer
4. Downloaded 4.4.3 zip from here http://forum.xda-developers.com/showthread.php?t=2767026 on to my computer
5. Download and install 7-zip http://www.7-zip.org/ on to my computer
6. On computer create an empty etc folder on your desktop and move apns-conf copied from phone in step 3 into this folder
7. Right click on the zip downloaded in step 4 and choose to open archive with 7-zip
8. In 7-zip open system folder. Open etc folder. Delete apns-conf.
9. Back up one directory so the system folder is open in 7-zip. Drag and drop the etc folder(from step 6 which contains the apns-conf from factory image) from your desktop into the system folder in 7-zip. This will add the apns-conf to the etc folder in the flashable zip. See http://forum.xda-developers.com/showthread.php?t=2163974 for more details
10. Copy this zip with the new apns-conf back to your external SD card on your phone
11. Reboot phone into safestrap. I used stock slot because the rom slots as the rom slots are not working. !!!WIPE!!! and flash zip copied to phone in step 10. Also be sure to flash NC5 modules for Wi-Fi http://forum.xda-developers.com/showthread.php?t=2487298
12. Reboot from safestrap and continue to boot into the newly flashed ROM.
13. I then ran the towelroot.apk found at towelroot.com. Installed SELinuxModeChanger from playstore and set to permissive (without this chrome and playstore have issues and FC)
14. Data connected but showed 3g. After a reboot this cleared up on its own. Guessing it pulled the needed information from the APN file on reboot.
I have been using it for about a day.
Phone = Working
4g Data = Working
Wi-Fi = working
External SD card = Working
I have not found anything that is not working yet. There is a 4.4.4 update in the thread where I downloaded the ROM. Have not tried the update yet. Probably will eventually when I have time. Apparently you do have to start with 4.4.3 and then do the update to 4.4.4.
RickGrimes411 said:
I was able to get a fully functioning 4.4.3 GPE ROM installed VIA Safestrap on my Verizon Samsung S4 i545 NC5.
It takes a little bit of work because straight out the box there are issues with google apps and data not working. Some of my steps may not be necessary. The most important parts are the apns-conf as this made the phone and data work. Making SELinux permissive and of course the modules. Whether or not starting from stock made a difference I am not sure. I did it because I softbricked and had to restore with odin.
MAKE A BACKUP JUST IN CASE
This is how I did it.
1. I started with stock factory image of NC5. The no-wipe link http://forum.xda-developers.com/showthread.php?t=2735172 and installed with odin. I then rooted with towelroot, installed supersu, busybox from playstore and Safestrap v3.75 recovery http://forum.xda-developers.com/showthread.php?t=2793891.
2. I copied apns-conf from the etc folder on my phone to my download folder(any folder on your phone easily accessable from a computer will work).
3. Plugged phone into computer and copied apns-conf to my computer
4. Downloaded 4.4.3 zip from here http://forum.xda-developers.com/showthread.php?t=2767026 on to my computer
5. Download and install 7-zip http://www.7-zip.org/ on to my computer
6. On computer create an empty etc folder on your desktop and move apns-conf copied from phone in step 3 into this folder
7. Right click on the zip downloaded in step 4 and choose to open archive with 7-zip
8. In 7-zip open system folder. Open etc folder. Delete apns-conf.
9. Back up one directory so the system folder is open in 7-zip. Drag and drop the etc folder(from step 6 which contains the apns-conf from factory image) from your desktop into the system folder in 7-zip. This will add the apns-conf to the etc folder in the flashable zip. See http://forum.xda-developers.com/showthread.php?t=2163974 for more details
10. Copy this zip with the new apns-conf back to your external SD card on your phone
11. Reboot phone into safestrap. I used stock slot because the rom slots as the rom slots are not working. !!!WIPE!!! and flash zip copied to phone in step 10. Also be sure to flash NC5 modules for Wi-Fi http://forum.xda-developers.com/showthread.php?t=2487298
12. Reboot from safestrap and continue to boot into the newly flashed ROM.
13. I then ran the towelroot.apk found at towelroot.com. Installed SELinuxModeChanger from playstore and set to permissive (without this chrome and playstore have issues and FC)
14. Data connected but showed 3g. After a reboot this cleared up on its own. Guessing it pulled the needed information from the APN file on reboot.
I have been using it for about a day.
Phone = Working
4g Data = Working
Wi-Fi = working
External SD card = Working
I have not found anything that is not working yet. There is a 4.4.4 update in the thread where I downloaded the ROM. Have not tried the update yet. Probably will eventually when I have time. Apparently you do have to start with 4.4.3 and then do the update to 4.4.4.
Click to expand...
Click to collapse
Man that sounds like way to much stuff. Think I'm just gonna search around for a m8 to buy.
Great instructions; thanks! I may give this a try.
Do you know of any issues with EMAIL App. using MS Exchange (corporate email)?
lambdaman said:
Great instructions; thanks! I may give this a try.
Do you know of any issues with EMAIL App. using MS Exchange (corporate email)?
Click to expand...
Click to collapse
I have not tested it. The app starts and prompts for an email address and password. From there I do not know. I don't have an account to test it out on.
Your comprehensive guide to rooting the NC5 and fixing it if/when something goes wrong
To start out I found it very time consuming to find the 'right' information on rooting the NC5 or that it wasn't possible. So I went on the mission to see if i get what was out in the wild to work.
Well I figured it out and I hope this helps!
Step One: Charge your phone! In the event we need to use Odin to fix a boot-loop/soft-brick.
Step Two: Check your version number. As the title suggests this method is only for Verizon Galaxy S4 NC5!
(ENABLE USB DEBUGGING AND UNKNOWN SOURCES IN SETTINGS BEFORE PROCEEDING)
Step Three: Time to download the tools we will need to get this done. Place these files on your SD card. This is the only time you will need your computer. CLICK IT> ONE STOP SHOP
Towel Root: Okay, this is version 1 of the app. I know there are newer versions but they don't work and this does so use it. Select and install. Open the app and select 'make it rain', your phone will reboot and base root has been achieved!
Super User: Select and install. Open the app and install the SU binary at the prompt. The app will also ask to disable KNOX, if you do the app might hang. Home button out and try again after a reboot. Eventually it will work though a bit funky at times.
Safe Strap: Select and install. Open the app and select 'install recovery'. After it installs reboot to the recovery by selecting 'reboot to recovery'. When the recovery loads select the backup option and make a backup!
This is our recovery and allows nandroid backups(you should have done this) and flashing of safestrap ROMs. The bootloader is locked on this phone so no flashing of CM11 or any custom kernels. Do some research before you start flashing things!
Well that was easy! Now you have a rooted and safestrapped NC5 S4!
FAQ\INFO
This recovery is BETA and does not support ROM slots. Everything must be done on the STOCK slot. MAKE A BACKUP!
Nandroid backup and restore is working completely with this recovery!
If you remove Samsung Hub auto rotation will break. Attached is the library file that fixes this. Extract libgnustl_shared.so from the attached zip. Copy and paste to System\Lib and change permission to rw-r--r--. I use Root Explorer, though not free is a very good file manager. There are free alternatives on Google Play.
CREDITS DUE!
HASHCODES< Safe Strap!
CHAINFIRE< Super SU!
GEOHOT< Towel Root!
Thank you for your work. But I have a few major points to address with this:
1. There is a newer, stable SAFESTRAP out (3.75), this one also supports ROM slots, and doesn't corrupt the Non-HLOS Partition.
2. Version 3 of TowelRoot is out, and alot more stable/clean than Version 1.
3. SAFESTRAP really should be installed after busybox is installed, which you did not recommend.
The Samsung Hub Auto Rotation bug is a very nice find though! Thank you for that.
Hey thank you! I will update accordingly.
However TowelRootv3 would not root my phone. I tried changing the strings, the app just states the phone isn't supported.