Guys please help i want my NTFS USB drive to work with S3
Root and use a custom kernel.
SiyahKernel has fixed NTFS mounting and will auto root with CWM Recovery (if you don't already have). Flash via Odin or CWM zip.
http://gokhanmoral.com/
Sent from my GT-I9300T using xda premium
UpInTheAir said:
Root and use a custom kernel.
SiyahKernel has fixed NTFS mounting and will auto root with CWM Recovery (if you don't already have). Flash via Odin or CWM zip.
http://gokhanmoral.com/
Sent from my GT-I9300T using xda premium
Click to expand...
Click to collapse
is it possible without installing a custom ROM.. i mean any mod or procedure
That's not a custom rom. All you do is replace the kernel.
The ROM itself (everything you see and care about, including the Touchwiz) is not being touched. (also including all your data, they remain intact)
It would be possible to compile ntfs-3g drivers for S3 but frankly what is the point if there are kernels which already include these features?
You'd need root anyway so you won't be on stock either way round.
Flash the kernel (never mentioned ROM) with Odin and you're auto rooted, CWM recovery, and NTFS mounting.
Then, download Chainfire Triangle Away app to remove the binary flash counter.
Important, whenever rooting, make sure you backup your EFS folder! SiyahKernel will do this automatically (saved to internal sdcard) when flashing. Do not delete this, but keep in a safe place copied to your PC.
Sent from my GT-I9300T using xda premium
Is SiyahKernel still considered the best for this job? I have a relatively standard S3 rooted with CF root already, I'd like to keep it more or less the same. Would SiyahKernel be the simplest, least intrusive way to do this? What changes will I notice?
danben7 said:
Is SiyahKernel still considered the best for this job? I have a relatively standard S3 rooted with CF root already, I'd like to keep it more or less the same. Would SiyahKernel be the simplest, least intrusive way to do this? What changes will I notice?
Click to expand...
Click to collapse
There are other custom kernels that probably will do the job. I just recommend siyah, as no issues with it.
Just take note of your current stock kernel version before flash, so you know what stock to flash if siyah is not for you.
This is the only path. Flash via Odin or cwm recovery (if your rooted and have it).
Sent from my GT-P6810 using xda premium
er_026 said:
Guys please help i want my NTFS USB drive to work with S3
Click to expand...
Click to collapse
If you want to keep the stock kernel, use Paragon NTFS&HFS+ from Play Store. It's free.
I've tested with a NTFS USB Stick and the Stock XXBLG8 kernel and worked fine
rafaelpernil said:
If you want to keep the stock kernel, use Paragon NTFS&HFS+ from Play Store. It's free.
I've tested with a NTFS USB Stick and the Stock XXBLG8 kernel and worked fine
Click to expand...
Click to collapse
Phone needs to be rooted though.
Try paragon. Works for me on my 32gb rooted sgs3 with too much pimped out accessories and features to list.
FYI: it will mount it deep in the Android file system
in a folder. What i do is unmount, then mount, choose
destination folder of my choosing.
Sent from Pimped out sgs3!!!
Try formatting to exfat or smaller partitions. Never tried an external hdd, only usb sticks.
I dont think android can use ntfs naturally because microshaft put a flag on it and claimed it.
I wish I stole my HTC M9.
Related
I modified the official 1.2 update to allow CWM to flash them. You can use these to upgrade to 1.2 or to return to stock.
There are two files. One replaces CWM with the stock recovery (good for going back to stock). The other doesn't replace CWM (but will replace uboot).
Other than that they are identical to the update from B&N.
update-nc-stock-1.2-keepcwm-signed.zip
update-nc-stock-1.2-signed.zip
Please note neither one of these are rooted yet.
Just curious as to if this is rooted or just fixed to allow use of CWM?
Nevermind just read the full post!!
So just to make sure, I could use the one zip to return to full stock but with the 1.2 update? Also will this work if I have CM7 and CWM on my emmc? So reboot into CW, format \system and \data then flash the update-nc-stock-1.2-signed.zip, then Reboot. At that point, I should be 100% 1.2 stock, sound about right?
I thinking about returning to stock and just run CM7 for my SD if this is an options.
Thanks,
Derek.
DGarmon said:
So just to make sure, I could use the one zip to return to full stock but with the 1.2 update? Also will this work if I have CM7 and CWM on my emmc? So reboot into CW, format \system and \data then flash the update-nc-stock-1.2-signed.zip, then Reboot. At that point, I should be 100% 1.2 stock, sound about right?
I thinking about returning to stock and just run CM7 for my SD if this is an options.
Thanks,
Derek.
Click to expand...
Click to collapse
Assuming you haven't fooked up any paritioning by using the "dual-boot" stuff you can return to 100% stock by doing the folllowing:
Download the update-nc-stock-1.2-signed.zip above
Flash the zip with CWM (either from emmc or sdcard)
Use CWM to factory reset the device (wipe /data and /cache)
Reboot into 100% stock froyo
If you have modified your partitions this will not work.
This won't work off of an sd right?
I'd like to modify this so it just installs to my dual boot partition.
I've done this before with flashing kernels, but there are more partitions here to take care of.
I figure if I'm going to change the updater script to mount the correct block partitions then I should also have it wipe /data and /cache on the secondary partition.
Any ideas on syntax?
sassafras
Thanks
Once we have a rooted version I'll probably check it out for fun.
nemith said:
Assuming you haven't fooked up any paritioning by using the "dual-boot" stuff you can return to 100% stock by doing the folllowing:
Download the update-nc-stock-1.2-signed.zip above
Flash the zip with CWM (either from emmc or sdcard)
Use CWM to factory reset the device (wipe /data and /cache)
Reboot into 100% stock froyo
If you have modified your partitions this will not work.
Click to expand...
Click to collapse
But then I'm stuck with stock froyo - I can't go back to CM7 after I've satisfied my curiosity, right?
Hmmm, have to think about that......then, again, maybe not.
nemith said:
There are two files.
Click to expand...
Click to collapse
Many thanks for these.
Please post MD5's of these so that we can be sure that the download was successful (some may want to store the file for later use).
BTW, free MD5checker can be found at getmd5checker.com
HarleyChick said:
But then I'm stuck with stock froyo - I can't go back to CM7 after I've satisfied my curiosity, right?
Hmmm, have to think about that......then, again, maybe not.
Click to expand...
Click to collapse
Create a backup first.
Thanks for the files nemith. Much appreciated.
Sent from my NookColor using Tapatalk
Hey nemith, would it be okay if I used this as a base for a rooted version? Give you full credit of course, just dont feel like going through the hassle of the updater script and what not.
msgnyc said:
Create a backup first.
Thanks for the files nemith. Much appreciated.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
I guess I wasn't clear the first time: if I use this method, am I stuck with B&N's version of Froyo until someone figures out how to root this one, or can I just reflash CM7? And I'm not sure I understand the difference between both of the zips that nemith has produced.
In any case, thanks nemith - I always appreciate the work that the devs do!
HarleyChick said:
I guess I wasn't clear the first time: if I use this method, am I stuck with B&N's version of Froyo until someone figures out how to root this one, or can I just reflash CM7? And I'm not sure I understand the difference between both of the zips that nemith has produced.
In any case, thanks nemith - I always appreciate the work that the devs do!
Click to expand...
Click to collapse
If you dont like this, just boot into a bootable clockwork recovery and flash cm7 or whatever you want. You wont be stuck on this.
One zip removes Clockwork Recovery and puts the stock recovery back. The other leaves Clockwork Recovery intact.
I'd assume, leaving it intact allows you to flash back to any backups or any other Rom if incase you do not like the official build.
I'm at work so I'm unable to test it out.
Or you can always just use a bootsble SD with clockwork on it to reflash whatever ron or backup you have.
Sent from my NookColor using Tapatalk
nemith said:
I modified the official 1.2 update to allow CWM to flash them. You can use these to upgrade to 1.2 or to return to stock.
There are two files. One replaces CWM with the stock recovery (good for going back to stock). The other doesn't replace CWM (but will replace uboot).
Other than that they are identical to the update from B&N.
update-nc-stock-1.2-keepcwm-signed.zip
update-nc-stock-1.2-signed.zip
Please note neither one of these are rooted yet.
Click to expand...
Click to collapse
My rooted BN1.1 with auto-nooter 3.0 does NOT have CWM in emmc. Can I use update-nc-stock-1.2-signed.zip to go to 1.2 unrooted?
nemith said:
I modified the official 1.2 update to allow CWM to flash them. You can use these to upgrade to 1.2 or to return to stock.
Please note neither one of these are rooted yet.
Click to expand...
Click to collapse
Any way you could make something would allow you to flash 1.2 onto a secondary parttion for those of us who are dual booters?
So Ive got this thing rooted but I for the life of me cannot get the market to work. I have the vending.apk and googleservicesframework.apk under /system/app but market will not show up in my app drawer on the stock or adw launcher. Under manage applications, market or googleservicesframework arent there either. Does the nook have other dependencies? If anyone with some experience could throw some suggestions my way. ADB isnt currently working without the driver. Ive added other apps that are showing up and working perfectly.
Did you modify the build.prop?
Sent from my Nook Color using XDA App
scoutcamper said:
Did you modify the build.prop?
Sent from my Nook Color using XDA App
Click to expand...
Click to collapse
Nope didnt touch it, im usually devving for the evo, so modding that isnt normally needed for gapps. What would need to be modified in the build.prop?
The device code will have changed and prevent market access. Try pulling the device code from a froyo device with market access like Droid X.
Sent from my Nook Color using the XDA App
Hi, anyone now if rom manager working on rooted galaxy s2? Do a backup, restore, install new rom from sd card, etc. Thanks in advance
078gregory said:
Hi, anyone now if rom manager working on rooted galaxy s2? Do a backup, restore, install new rom from sd card, etc. Thanks in advance
Click to expand...
Click to collapse
It isnt fully compatible. Use the cwm that is in chanfires root thread in dev.
Sent from my GT-P1000 using XDA Premium App
Delete
078gregory said:
I'm using cwm, but I did one time backup with cwm and then I tried a restore, I can not because a received a error:MS5 Mismatch. Before sgs2 I had a optimus 2x and worked perfect on 2x. Hope will fixed to work on sgs2, coz is easy to use.
Click to expand...
Click to collapse
Anyone????
what version of CF root are you using?
Delete
MD5 = file signature does not match probable corruption or different file .
jje
JJEgan said:
MD5 = file signature does not match probable corruption or different file .
jje
Click to expand...
Click to collapse
It`s another way to make a restore if I did a backup with CWM?
What did you backup ???
On what phone and what app to backup .
What CWM recovery are you using .
or are you trying to restore a backup from a different phone ??
Post is rather confusing .
jje
Delete
MD5 is a way to control a TAR file.
It will missmath as well if you try to access the file via 7-Zip for instance.
Try to find same file elseware from the web, or excrtact end rebuild a direct tar file.
Good luck
I don't like CWM4 on CF-root
The reason i don't like it is: It makes the recovery disappear after about a day of use, Then i have to reflash, i don't want to do that.
CWM removes it's self for me
The thing i don't like about CF-Root, is and this may be my fault, It freezes some of my rooted apps that freeze bloatware (Easy Freezy) and it also removes the custom recovery by it's self
When i go into the app and click reboot recovery, it boot into Android system recovery.
I then have to reflash in order to get ClockworkMod back.
This other Root meathord: http://forum.xda-developers.com/showthread.php?t=1125414
Does NOT freeze some rooted apps like Easy Freezy and Adfree like CF root does for some reason.
Help would be appreciated,
Thanks.
Is anybody else unable to back up ROM successfully on Omega v13?
I thout I'd backed up my beloved ROM and settings last night before full wipe testing the latest JB Odin ROM. That ROM was not good with regards to wifi intermittently toggling on and off so restore the previous ROM time thought I.
Wrong!
The CWM file wouldn't restore and when I looked at the files the Backup file was 16.8mb bit the Blob files were over a gig. There was no md5sum.
The situation then got worse as my phone entered a black screen bootloop for a while and wouldn't connect to the pc to flash an old backup ROM.
3 hrs of sweating and various wipes, odin flashes, downloads and not much sleep later and I'm back on Omega v13 again (minus all of my SD card files). But, I've just tried to back up my current ROM and still the same problem.
ROM manager is 6.0.1.2 if that helps.
Sent from my GT-I9300 using xda app-developers app
Dont use Rom Manager is the simple answer especially if you used CF root .
jje
JJEgan said:
Dont use Rom Manager is the simple answer especially if you used CF root .
jje
Click to expand...
Click to collapse
Thanks for the reply but how do I backup my ROM without using ROM manager? Also why is the function not working anymore as it's been fine for 23 different ROMs?
Do cf root and ROM Manager conflict with each other?
It's doing my head in
Sent from my GT-I9300 using xda app-developers app
Just back up with cwm and forget about Rom manager
slaphead20 said:
Just back up with cwm and forget about Rom manager
Click to expand...
Click to collapse
Alright cheers gents.
Have duly uninstalled ROM Manager and will stick with CWM.
I think the problem was that the way a backup is now saved has changed - previously each dated backup file would be circa 1.8 gb in size but now when you back up it doesnt duplicate all of the files, instead it has a file hub in the BLOBS folder and just captures an image of the remaining files and md5sum.
It will save a lot of space this way at least...
As for CF Root however it wont let me do a NAND backup as it loses connection to the device as soon as it starts...?
Maybe because Omega v13 doesnt meet the criteria of insecure kernal??
I dunno.
Root with.
http://forum.xda-developers.com/showthread.php?t=1695238
jje
JJEgan said:
Root with.
http://forum.xda-developers.com/showthread.php?t=1695238
jje
Click to expand...
Click to collapse
Yep done it, cheers mate.
Was being a kn*b and getting confused with mskips all in one toolkit because, er, I'm a kn*b
Sent from my GT-I9300 using xda app-developers app
I am trying to root my s2, and using this method
http://forum.xda-developers.com/showthread.php?t=1501719&page=56
I install cwm and then when i go to install busy box, I need to click on install from internal sd card even though its my external. When I go to the top option which should give me external. it gives me internal and even has a folder called ext-sd, when I click on it, Im at the same place. So without root how can I change them back? or get root with out changing them? I tried cf root and don't know how to download a firmware from chainfire(which I just got was why it was CF... CF=ChainFire) because when i extract, i only get zImage. Any help is fine
joeym11 said:
I am trying to root my s2, and using this method
http://forum.xda-developers.com/showthread.php?t=1501719&page=56
I install cwm and then when i go to install busy box, I need to click on install from internal sd card even though its my external. When I go to the top option which should give me external. it gives me internal and even has a folder called ext-sd, when I click on it, Im at the same place. So without root how can I change them back? or get root with out changing them? I tried cf root and don't know how to download a firmware from chainfire(which I just got was why it was CF... CF=ChainFire) because when i extract, i only get zImage. Any help is fine
Click to expand...
Click to collapse
Don't worry, that's the limitation/bug in the CWM recovery version used for that rooting guide.
Once you know that, then you will not have problem to root your phone.
Once your phone is rooted with that method, flash either Siyah or Speedmod kernel.
Visit the thread of those kernels in the original development section, download .zip version and not .tar
CWM recovery only recognises zip files.
Those kernels, have fixed version of CWM recovery and will drain keeps battery than stock kernel
Good luck.
Swyped from my Samsung Galaxy SII
Jokesy said:
Don't worry, that's the limitation/bug in the CWM recovery version used for that rooting guide.
Once you know that, then you will not have problem to root your phone.
Once your phone is rooted with that method, flash either Siyah or Speedmod kernel.
Visit the thread of those kernels in the original development section, download .zip version and not .tar
CWM recovery only recognises zip files.
Those kernels, have fixed version of CWM recovery and will drain keeps battery than stock kernel
Good luck.
Swyped from my Samsung Galaxy SII
Click to expand...
Click to collapse
I actually ended up getting through and immediatly after flashing busybox, I just installed Siyah and I am all good. Ext and int sd card now are even in the right places and I am preparing to install para if my cwm is working correctly.
I did the ExynosAbuse-v1.40 exploit, install Mobile Odin Lite, SiyahKernel v2.6.14, ClockworkMod Recovery, and install CM 10.1.3.
My first root and rom install and everything works great! Battery life went from one day to three and operating quickly.
Do I keep the files on my sd card or can i delete them?
For future installs and upgrades, is CWM recovery my primary means of install?
Thanks guys for your hard work. I really appreciate all you do and plan on donating to the cause.
Dave
dave042 said:
I did the ExynosAbuse-v1.40 exploit, install Mobile Odin Lite, SiyahKernel v2.6.14, ClockworkMod Recovery, and install CM 10.1.3.
My first root and rom install and everything works great! Battery life went from one day to three and operating quickly.
Do I keep the files on my sd card or can i delete them?
For future installs and upgrades, is CWM recovery my primary means of install?
Thanks guys for your hard work. I really appreciate all you do and plan on donating to the cause.
Dave
Click to expand...
Click to collapse
"on my sd card"? You meant external uSD card or internal memory?
Either way, you can delete them if you won't ever need them again.
From this point on, any flashable zip file will be run using CwMR
Welcome @dave042,
-and congrats on a successful first root/ROM experience.
regarding the "files on the sd card", If we're ignoring the expansion slot, then there are files that apps use on the internal SD, so I wouldn't go deleting them at random. I'm sure that a google search will help you with which folders are needed, and which are not.
All future firmware installs should indeed happen from CWM recovery. Once you're rooted and kernel'd, there isn't any need for mobile ODIN. The options offered in CWM recovery are superior.
As you try new things, I do advise that you do some cleanup inbetween ROMS. Dirty flashes often lead to issues that people blame on the rom or kernel. factory resets only catch a portion of the critters. @mrcook has a few rom wipe scripts specifically for the i777 that have helped multiple people (myself included) out of weird phone issues that were the result of old-rom-junk not playing well with new-rom-junk.
Happy flashing
-Cyril
thanks votinh and Cyril for the quick response.
the SD card i was referring to was the external SD. i don't plan on installing too many roms but will make sure to do a complete wipe prior to any install.
was this process of installing ExynosAbuse-v1.40 exploit, install Mobile Odin Lite, SiyahKernel v2.6.14, ClockworkMod Recovery, to get me to root? and once to root, to install a rom?
another question, kernal and rom updates, are they independent of each other? can i update one without the other?
i understand roms are numerous and customized, what about the kernal? does changing the kernal make any significant changes to the operating system?
Gneerally on this device ROMS will come packaged with their own kernel. The kernel will be flashed when the rom is flashed. I do believe however that most install AJK after they flash their roms.
You can delete everything off your sd card. I do keep a known good rom as well as a copy of Siyah 4.3.3 kernel on my card at all times. You never know when something is going to mess with your phone, and you may have to re install a rom in order to make you phone function again. I would hate to be somewhere, my phone start a boot loop, and I am stuck without a phone. The Siyah 4.3.3 kernel comes in handy for me. Some roms will give you an error 7 when flashing. Rather than messing with editing the build prop I just flash Siyah, and try my rom again.
If you go flashing kernels make sure you have the proper kernel for your ROM.
@dave042: "was this process of installing ExynosAbuse-v1.40 exploit, install Mobile Odin Lite, SiyahKernel v2.6.14, ClockworkMod Recovery, to get me to root? and once to root, to install a rom?"
Click to expand...
Click to collapse
ExynosAbuse-v1.40 exploit <-- tool to establish root-access to the device (framaroot is another useful, easy rooting tool for the i777)
Mobile Odin Lite <-- tool that uses root-access to install...
SiyahKernel vX.X.X <-- a custom kernel (one of many) installed primarily to provide cwm recovery, but are also commonly used to:
-provide additional functionality to the existing ROM
-backup your ROM install
-install a different ROM
-install a different kernel
-flash cleanup scripts
-and many many other things
As Butchr stated, the ROMs are usually packaged with their own kernels, so the kernel used above only remains in place until another ROM is flashed, which will overwrite the existing recovery with one specifically designed for the ROM flashed.