In terminal emulator to fix wifi I get, unable to chmod bypasslkm: no such file or directory. Any ideas?
We all appreciate all the hard work you and the team did for us here in maintaining a root while updating to 4.4. Trust me you devlopers are greatly appreciated amount this community. I hate to be the one to ask really. But did this move us any where towards an unlocked bootloader? Did this leak provide any information that's going to help us in the long hall or are we still just as stuck with a lock down as we were on MJ7?
Sent from my SCH-I545 using xda app-developers app
Same here, I'm having the exact problem as you. Odin won't even recognize my device anymore.
WiFi is really important to you huh? Here is the bypasslkm thread http://xdaforums.com/showthread.php?t=2578566 and here ive uploaded the binary for you https://www.dropbox.com/s/9rdz9ff6x5foech/bypasslkm.
To tell you the truth I havent even examined the partitons from VRUFNC2 other than checking if the counter in aboot was incremented. Havent had time and didnt anticipate people having all these questions related to the upgrade/downgrade to/from VRUFNC2! ??
But with the qcom leak, n3 KK leak, our KK leak and having to find/come up with a method to upgrade with root, I havent much time for anything lately ?
Sent from my SCH-I545 using XDA Premium 4 mobile app
What do you mean? can you elaborate? what were you doing that caused this?
What were you doing that caused this?
Did you install the zadig.exe driver? if so then switch usb ports and try.
Sent from my SCH-I545 using XDA Premium 4 mobile app
What do you mean? can you elaborate? what were you doing that caused this?
Yes I can. When I enter Download mode and open Odin on my PC, the phone does not come up. I followed everything in the guide, and when it got to the last step, the stock recovery failed at trying to mount something. I then went and followed the "In case the last step above fails" section, and when it got back to the stock recovery and the blue progress bar, it failed with the same error. Now Odin will not recognize my device is connected.
Try using another USB port as Surge1223 mentioned for me. It got things going again for me.
What do you mean? can you elaborate? what were you doing that caused this?
Yes I can. When I enter Download mode and open Odin on my PC, the phone does not come up. I followed everything in the guide, and when it got to the last step, the stock recovery failed at trying to mount something. I then went and followed the "In case the last step above fails" section, and when it got back to the stock recovery and the blue progress bar, it failed with the same error. Now Odin will not recognize my device is connected.
K open device manager and plug then phone into a different USB port. See if Odin recognizes it then. If not uninstall the zadig drivers and reinstall the samsung drivers then reboot your PC.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Changing USB ports worked. Thank you. Downgrading to MK2 again. Did you see my earlier question in regards to using a stock MK2 cache.img in heimdall?
---------- Post added at 01:58 PM ---------- Previous post was at 01:56 PM ----------
Yeah when I downgraded to MK2 I still had the /cache issue so after flashing the mk2 downgrade tar i flashed the mk2 cache.img.ext4 in heimdall. What version of Odin are you using? it might be worthwhile to reflash the mk2 recovery.img and cache.img.ext4 along with the pit when downgrading to see if it fixes this issue.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Uhm, I have an issue here. During the first Oden 3 step flash, it ended with 0 succeeded 1 failed and my phone is still stuck in "Downloading.. Do not turn off target" with the progress bar most of the way filled but still solid. I don't know if "WonderShare" on my computer interfered with the process or what as I heard some USB type connect/re-connect beeps and WonderShare tried to load into Manage device...
What to do? I'm still connected via USB to the computer with the phone in above mentioned state.
---------- Post added at 03:00 PM ---------- Previous post was at 02:29 PM ----------
Ok got past that problem by disabling wonder share on the PC and forcing phone back into download mode and was able to proceed through ALL odin steps including the final one and I'm booted into the ROM fine. Other than all the force closes, things seem proper so far.
Now my problems. I can't seem to get into STOCK recovery to do the factory reset to get rid of the force closes as when I hold down Vol Up, Power, and home, it flashes back n forth from a battery symbol to SS recovery.
2nd, I of course no longer see V3.71 or ANY SS recovery in the app drawer so I'm confused when it says first uninstall the old SS before installing the AT&T 3.72.
Thanks
I re installed 3.71 then uninstalled the recovery. Then installed 3.72
Sent from my SCH-I545 using Tapatalk
I said to uninstall 3.71 then install 3.72 so people would uninstall SS 3.71 in case they had already downladed and installed it prior to that step. But at least people will check what version of SS they are installing, and hopefully install 3.72.
You don't need to do a factory reset via recovery, you can do that in SS 3.72 once you install it. If you want to restore stock recovery you can try flashing the NC2 recovery.img in Odin/Heimdall, though it should have installed by default..strange.
Sent from my SCH-I545 using XDA Premium 4 mobile app
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:
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 recoverymount("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");
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.
So is this the official rom from VZW or some other version. I want the stock rom that is rooted with no mods so I can chose what I want myself. I don't like it when people debloat my phone and dcecide what stays and what goes, as well as adding "helpful" things to my phone. I like complete control.