Voodoo Lagfix on 2.3.6 (XXJVU) - Galaxy S I9000 Q&A, Help & Troubleshooting

Hello all,
I just got my Galaxy S (i9000) which was running on stock 2.3.3. It was very laggy... I thought to update its firmware through Kies but there was no update available through it.
So I searched a bit and found the official leaked Value Pack firmware XXJVU. I downloaded it from samfirmwares and flashed it according to this guide.
The same website had a Root guide for this firmware which is actually CF-Root specific for this firmware. I done that too. Phone was very smooth now.. but then when I restored my ~200 apps through Titanium Backup.. it again started to lag.
I had heard about Voodoo lagfix before so thought to try it.. I searched but could not get a proper answer if I can (and how) do it to my current firmware.
I also saw somewhere that CF-Root (kernal) do the same thing as Voodoo do (RFS > Ext4) apart from rooting your device. But when I checked my filesystem.. it was still RFS.
So my question is
1. Can I do the Voodoo lagfix on my device or not? and how?
2. Will it revert my root? If yes then how will I able to root it again?
3. If Voodoo lagfix is not available for this firmware then which other lagfix can I apply? I heard that some lagfixes (don't know about Voodoo) may speed up the device initially but then with installation of more application, the lag comes back.
Is Voodoo lagfix the same?
4. If other lagfixes are not as good (or permanent) as Voodoo lagfix, then which is the latest firmware I can use with Voodoo lagfix?
XXJVS from here?
Sorry, I am new to these things.. and I have searched a lot to figure it out myself without asking here.. but I just could not.
So any help would greatly be appreciated.
EDIT: Sorry, forgot to check the "Question" mark while posting. Any mod please do it for me..

Flash cf root or better still semaphore kernel which is based on chainfires. Use ext4 app to convert rfs to ext4, root will remain, it simply backs up file systems, creates new ext4 file systems and restores. Search for ext4, lots of info available. You will need to free up some space by deleting some standard bloatware
Sent using TCP/IP

gsw5700 said:
Flash cf root or better still semaphore kernel which is based on chainfires. Use ext4 app to convert rfs to ext4, root will remain, it simply backs up file systems, creates new ext4 file systems and restores. Search for ext4, lots of info available. You will need to free up some space by deleting some standard bloatware
Sent using TCP/IP
Click to expand...
Click to collapse
Thanks for your reply.
I already had CF-Root flashed at the time of posting this thread. I tried ext4 CF tool to convert the partitions from RFS to ext4 but the CWM recovery would give error:
"Finding update package...
Opening update package...
E:can't open /sdcard/tmp_ext4_tools.zip (bad)
Installation aborted."
I tried to download the CF ext4 tool from other source and tried but same problem. I tried to copy the "tmp_ext4_tools.zip" generator by CF ext4 manager to external sd instead of internal and then tried manual installation through CWM's "install zip from SD Card" but no avail (same problem).
Then I downloaded and flashed Semaphore kernal v2.5.0 for XXJVU. Root done by CF-Root Kernal was preserved (thank God). Installed the CF-ext4 manager again.. and booted in to CWM. And this time, the convertion process occured without any errors
Now I am on ext4 finally ! (spent the whole day on this)
Don't know why CF-ext4 Manager won't work with CF-Root kernal but with Semaphore.
Anyways, my Quadrant scores with about 200+ apps installed in both scenarios:
On RFS (CF-Root Kernal): 1243
On ext4 (Semaphore): 1892
My phone run better now.. but still not as much as the number shows. Anyways I am happy and can't spend anymore time messing with it.

Hi. I also want to get lag fix and ext>4. how did u do this for xxjvu?

Related

[PRJ] Vibrant Voodo Lag-fix w/OC-Optimized 2.6.29 Kernel - Beta4 9/19/2010

This is Voodoo LagFix beta4 for the Vibrant. It does not include color adjustment just the /data as ext4. This has been tested by many users and is confirmed working, including GPS WiFi BT etc. There is also the performance increase of course as well due to the Voodoo lagfix and the optimized Kernel with OC option.
WARNING BEFORE FLASHING:DISBALE ANY LAGFIX'S YOU MAY ALREADY BE USING BEFORE APPLYING THIS FIX - IS NOT COMPATIBLE WITH THE LATEST LEAK JI2
Samsung has not provided us with the kernel sources that were used in the latest leak (which are different) so until they do we cannot support it.
To enable simply flash the kernel. It will automatically backup your existing /Data partition and create the /data as ext4 and restore so you dont lose your data of course.
To disable simply place a file/folder in the "Voodoo" folder on your SDcard (the internal one) called "disable lagfix" (e.g /sdcard/Voodoo/disable lagfix") no extention just that exact name and reboot. After your phone boots and you check that your /data partition is again RFS you can re-apply any other kernel you were using.
Upon enabling or disabling your phone will sit on the Vibrant screen. This can take 5-10 minutes depending on how much data you have (don't panic). "Linda" the robotic voice should let you know where in the process you are. After its done and your phone boots you should be able to run "mount" in terminal or adb shell and see your data is now EXT4 at
Code:
/dev/block/mmcblk0p4
Disabling by placing the "disable-lagfix" file in the "Voodoo" folder in your sdcard and that simply undoes what the enable did and returns your /data to the RFS setup at its original location.
PLEASE READ
The kernel boots to stock clocks but CAN be OC'd to 1.2Ghz via setupCPU or a user script. If you want to keep the phone OC'd just use setCPU and check apply on boot or use a user script that launches from /system/etc/init.d. If you want to run stock clocks just boot and don't do anything
NOTE This kernel does not need the init.d folder to be present to flash but will parse it if it is there. Also this kernel includes almost all the optimizations my OCv4 kernel so you get the best of both worlds if you want. Voodoo plus OC!
So a simple install routine through recovery would go like this
1.Flash a ROM and root it or flash one that is already ROOTED
2.Download beta4 Voodoo .zip file
3.Reboot into Stock recovery and flash the update.zip made for STOCK recovery.
4.Listen to "Linda" the robot tell you the progress as Voodoo does its thing.
RECOVERY UPDATE
Voodoo Beta4 UPDATE.ZIP
EDIT:Voodoo Beta4 Update zip you can install through STOCK recovery
http://project-voodoo.org/downloads/Voodoo-lagfix-3.0-SGH-T959-update.zip
Clockwork Version by request
www.justanotherdev.slackdev.com/Vibrant-Voodoo_beta4.zip
ODIN UPDATE
Vibrant Voodoo Lag-Fix Beta4
http://project-voodoo.org/downloads/Voodoo-lagfix-3.0-SGH-T959-odin-pda.tar
KNOWN ISSUE:To perform NANDroid backups or restores through clockworkmod recovery please disable the lagfix before either operation otherwise it will not work.
Big Thanks to supercurio for the Voodoo project and for letting me share it with all the Vibrant users out there.
reserved for future use...
I love you.
Going to test in a few. Do you know where we can get the disable-lagfix file? Your OP doesn't include it. =)
EDIT: Nevermind. I should have read more carefully. THANKS AGAIN JAC!
I just flashed the Leaked TMO Kernel with the GPS Fix... can I flash this Lag FIx?
Thanks a lot man! Really appreciate you giving us something to tinker with, been dying to try this out
Will users who already are using 1-click lagfix need to do anything differently in order to use this?
Goog1e Phone said:
I love you.
Going to test in a few. Do you know where we can get the disable-lagfix file? Your OP doesn't include it. =)
Click to expand...
Click to collapse
You just have to name a file "disable-lagfix" and throw it on you sd card. It shouldn't actually have any data in it.
acis said:
Will users who already are using 1-click lagfix need to do anything differently in order to use this?
Click to expand...
Click to collapse
Ya, restoring back to stock or removing the lagfix if its possible. You cannot apply this if you already have a lagfix. Remove it or restore to a previous backup before you were using the lagfix (you made one, right )
just installed on Eugene's r3 rom, and it feels very snappy, can't wait for beta 3, thanks!
Edit: just did a second reboot, and I'm getting an error about a blank internal SD card, and all my data is missing. Any ideas on what I did wrong? I had a lagfix previously installed but had reflashed r3 and didn't redo the fix(not a nandroid just a new flash)
Sent from my SGH-T959 using XDA App
zimphishmonger said:
Ya, restoring back to stock or removing the lagfix if its possible. You cannot apply this if you already have a lagfix. Remove it or restore to a previous backup before you were using the lagfix (you made one, right )
Click to expand...
Click to collapse
Yes. I didn't want to go that far back but meh. 1 click doesn't seem to be working very well tbh.
Appreciate all the hard work that goes in to making the phone actually operate as it should have on day 1. This community is amazing.
It does NOT work on the new leaked rom, fyi :O)
If you are using the leaked rom and you flash this you will need to flash the original rom and check repartition to restore your phone.
Do you need to flash the init.d update before flashing this kernel as with your previous kernels?
Dude this is fast... thank you def. worth the wait so far. the lag is gone! i cant wait to see what you guys come up with next.. its like christmas every few weeks
Eugenes Hybrid r2
Babyface1249 said:
Do you need to flash the init.d update before flashing this kernel as with your previous kernels?
Click to expand...
Click to collapse
No. Just flash the kernal through clockwork. No other steps are needed, unless you already had a lagfix prior.
Goog1e Phone said:
No. Just flash the kernal through clockwork. No other steps are needed, unless you already had a lagfix prior.
Click to expand...
Click to collapse
Giddy up. Flashing now before I get my second replacement vibrant tomorrow lol
HELP!!
i just flashed this through recovery and now my phone wont boot up... just stays at vibrant screen.
when i try to get back to go through "reinstall packages" to get back to nandroid i get stopped. it says...
--install from sdcard...
finding update package...
E:cant mount /dev/block/mmcblk0p1 (or /dev/bloc/mmcblk0)
(device or resouce busy)
E: cant mount SDCARD :update.zip
Installation aborted.
AHHH! what do i do?
Man this thing is FAST! I say we start calling this fix the doodoo lag fix instead because this thing is the SH*T!
itsjusttim said:
HELP!!
i just flashed this through recovery and now my phone wont boot up... just stays at vibrant screen.
when i try to get back to go through "reinstall packages" to get back to nandroid i get stopped. it says...
--install from sdcard...
finding update package...
E:cant mount /dev/block/mmcblk0p1 (or /dev/bloc/mmcblk0)
(device or resouce busy)
E: cant mount SDCARD :update.zip
Installation aborted.
AHHH! what do i do?
Click to expand...
Click to collapse
How long did you wait when it was on the Vibrant screen? The OP says it will usually stay on the VIBRANT screen for 5-10 min before it boots up depending on how data you have.
Goog1e Phone said:
How long did you wait when it was on the Vibrant screen? The OP says it will usually take 5-10 min on the Vibrant screen before it boots up depending on how data you have.
Click to expand...
Click to collapse
waited 20+.. nothing!
is there anything i can do? SH*T, i need this phone for work...
itsjusttim said:
HELP!!
i just flashed this through recovery and now my phone wont boot up... just stays at vibrant screen.
when i try to get back to go through "reinstall packages" to get back to nandroid i get stopped. it says...
--install from sdcard...
finding update package...
E:cant mount /dev/block/mmcblk0p1 (or /dev/bloc/mmcblk0)
(device or resouce busy)
E: cant mount SDCARD :update.zip
Installation aborted.
AHHH! what do i do?
Click to expand...
Click to collapse
Did you install the leaked rom? You will need to go back to the stock rom in ODIN and check the repartition box. Follow my instructions here: http://forum.xda-developers.com/showthread.php?t=780935 but use the original rom

[Q] Problems with Froyo, Speedmod k13e tweaks and root

Hi,
I cannot get root access on my terminal. The following is my configuration:
Froyo 2.2
PC: GT-I9000HKYTIM
PDA: GT-I9000AIJP6
PHONE: GT-I9000XXJPP
CSC: GT-I9000TIMJP4
Recovery : 3e
I installed speedmod k13e, but i cannot enable tweaks, bln and root.
Whenever i enter recovery mod i try to install root (simple) from the speedmod/ulk menu, at the end of the process it says "Done!" but when i reboot titanium backup complains that i do not have root privilegies.
Furthermore when i try to enable tweaks, every tweak i choose prompts "disabled". The same thing happend when i try to turn on BLN.
Any idea?
Thank you for you help.
Mattia.
Check if you actually have the Super User app on your phone.
If you don't have it download busybox from TitaniumBackup.
The Froyo Speedmod is ultrastable so this is quite odd to me.
If neither of this works I think you might have to reflash the kernel.
Hi,
thank you for your reply.
I did not have the superuser app installed and i did not find a way to download busybox from TitaniumBackup.
So i installed both superuser and busybox from the market.
I run superuser, then TitaniumBackup, but it does not start and it does not ask for root privileges.
In the same way i run superuser, then the BusyBox installer, but it does not start and it does not ask for root privileges.
I reflashed SpeedMod, but nothing has changed.
I forgot to say taht my sgs is branded and i did not unbrand it. Other things i should try?
Mattia.
I also tried with SpeedMod k12u and CFRoot 1.2 for JP6.
No progress made: no root privilegies.
I did one small step forward: i managed to correctly install busybox with CFRoot. I've never been able to do it with SpeedMod.
Could it be because the system ROM is full?
Mattia.
aittam said:
I also tried with SpeedMod k12u and CFRoot 1.2 for JP6.
No progress made: no root privilegies.
I did one small step forward: i managed to correctly install busybox with CFRoot. I've never been able to do it with SpeedMod.
Could it be because the system ROM is full?
Mattia.
Click to expand...
Click to collapse
yea I guess your /system probably is full. to change that delete for example google maps (you can just download and install it from the market) from /system/app with root explorer or go into recovery and convert the filesystem the conversion will give you some more free space even if you change back to rfs afterwards
I did it using ADB Shell.
From the shell both su and busybox worked like a charm.
So eventually i managed to do my backups!
Mattia.

[Q] Issue with ext4

I'm facing an issue that I've been able to narrow down to this :
- I install stock JVT (odin with re-partition)
-> no issues
- I then install Semaphore 1.8.0 kernel using odin
-> no issues
- I install and run ext4 1.3 from cf-root
-> install seems ok, I launch it, no issue, tell it to conver to ext4, the process starts, the phone reboots, the conversion processe takes a minute or two and the phones reboot.
-> at first, all seems ok, the phone operates as i should, BUT it looks like I've lost root :
- semaphore apps cannot be run because of permission issues
- same goes for ext4, cwm,...
I've tried to reflash semaphore in a hope for a fix, but it did not help.
Any guess ?
Thanks in advance, jc
the ext4 tool has several different versions: step 1 is to use a different version. The tool itself can by a bit buggy.
You can also look at other ways to convert your file system using another kernel.
Was you using the ext4 app 1.3?
If you run it now does it say your file systems are rfs or ext4?
Sent using TCP/IP
Yes, I'm using ext app 1.3.
The first time I run it, jus after semaphore install, it says my files are rfs.
I launch the conversion process, it reboots as normal, does the conversion, phone seems ok, but you cannot relaunch it to check because it wont recognize the kernel and fail (I believe it is permission issues, as my phone seem to have lost it's root in the process).
Good idea about trying another kernel jus for the ext4 migration, now I need o find one that does not leave anything behind when I move back to Semephore
jc
Yeah, You can use chainfires kernel to get root back and convert file systems to ext4.
Then use SGS flasher to flash semaphore.
yes, but I'm wondering if the issue is not somewhere else. I believe I might not have enough space on /system to do the conversion.
What is the required free space ? Arround 6 Mb ?
jc
Yes, that was the issue, not enough space on /system, which made the convert fail, and all my problems where comming from that.
Remove some apps with nitrality, got 7 mb free, and it worked !
jc

[SOLVED] EU GT-P1000 w/ CM9 RC0: "Signature verification failed"

Dear valued Android and Samsung experts,
it is my first post in this forum. I waited until the flashable ROM etc. was released, so today I tried humbertOS' CM9 (RC0) from 02.02.2012. It is only my second time doing this, after initially upgrading von Android 2.0 or so to 2.3.3.
My Device Info (after wiping, while stuck now)
European SAMSUNG GALAXY TAB (GT-P1000)
Android 2.3.3
Current baseband version: P1000XXJPZ
Current kernel version: [email protected]#2
Build No : GINGERBREAD.XXJQ1
Rooted with Super One Click (Maybe. Can't remember anymore, but it is rooted.)
Installed ROM Manager Pro.
Backed up with TitaniumBackup (Premium I think) to my Dropbox (via Wifi). I hope that is correct this way.
I get the following error:
Finding update package...
Opening update package...
Verifying update package...
E: Signature verification failed
Installation aborted.
Click to expand...
Click to collapse
What did I try to solve the issue?
I redownloaded the ROM.zip, but it didn't help. As there are no md5 hashes available (why?) for the online files, I couldn't compare if there is a problem on my download side. But I used Google Chrome, Internet Explorer 9 and jDownloader now, they can't all be faulty. Of course I re-wiped the cache every time after I had to start the phone or transfer the files!
I read 3+ threads that I found via search, but there was no solution. By the way I was unable to find this forum (Samsung Galaxy Tab) in the forum scroll-down list? Am I blind? I triple-checked! ... In one of the threads I read there I should go go back to the stock version (2.1 or so), is that true? How do I force my Tab to do so?
Now what I think could be the problem source is that I'm wondering why the path /sdcard is showing all the other folders and stuff and why before I put the files on the flash partition of the Galaxy Tab it didn't initially show up! What I try to say is: It seems to me the bootloader accesses NOT the SD-card, but the Tab's flash (all while calling it /sdcard), how can that be!
My SD card is basically empty asides of the ROM, kernel and GApps, but (how) can it even happen that the bootloader choses the internal flash over the SD card?
The last time (2.1 to 2.33) I upgraded I used Odin. This time this is not an option? I only follow the procedure you outlined and ask no questions. I mean in the other thread I read "you will need to flash via odin first because stock rom of gtp1000 have limited options in the recovery mode." (source) - well why is this then not mentioned in this thread or on humberos website? As said, I just followed the directions, thus avoided Odin this time!
And here I read a lot about "Clockwork Recovery", do I really need it? *confused* I mean I already own and payed for ROM Manager and Titanium Backup, should be fine right? I mean it is almost absurd how much I read about it...I can assure you I bought the above tools because back then those were the ones in the talk!
I also heard about "disabling of signature verification", but as it involves a lot of steps, is it really necessary?
I also read about "3e Recovery" but what is that? I would be happy if everyone could stop throwing around with abbreviations that yield no helpful Google results and instead write out and describe what tool or method they use exactly. For the above example my open question is obviously if this recovery method also applies to me with a different brand (Samsung) and model (Galaxy Tab "classic") compared to where I found this method....
Finally do I need to / should I replace my bootloader / recovery menu with another one maybe? ... In conclusion I hope you see I did my research, but there are so many ways to get a solution, so right now I simply need a hint from more experienced pro's about in which direction I have to go!
Thank you for your help in advance!
ClockworkMod Recovery
Ok, I noticed now my mistake probably is that I was missing an installed "ClockworkMod Recovery".
But: When I try to install CWM from within the ROM Manager (v.5.0.0.6, Premium) it only displays a choice of two models - "Samsung Epic4G" and "Samsung GalaxyS i9000" - in the list and not my model (Galaxy Tab EU) or any other model! What is going on there, why does ROM Manager Premium not display an array of other devices?
And is there any alternative way to download and install CWM on my Tab?
PS: The "Euro bootstrap recovery" app mentioned in other threads is not available anymore in the market either.
PPS: I also found this directory full of clockwork builds: http*//download.clockworkmod*com/recoveries/, which one of those would be right for the GT-P1000? The "recovery-clockwork-tab.img" & "*.zip" from 04-Jun-2011 17:37?
The commonly known method is to restock according to Overcome 4.1 rom thread
Then install overcome kernel.
That gives you cwm recovery and it also converts your filesystem to ext4.
Then flash the cm9.
Sent from my GT-P1000 using XDA App
Thanks priyana
Thanks priyana, that hint really made it for me!
Successfully made it through!
Now only the GApps don't show up even though I installed them.
Will browse the forum here and Google for solutions...
reset to factory default and re-install gapps once more?
seems to happen now and then to some flashes
Hey priyana, I didn't update the thread, yes I'm done with that already!
A question though: Is it normal that the internal + external storage show "as one" drive or is the SD card actually not mounting on my Windows laptop? (I assume.)
The problem is, even though I activated UMS with the toggle, I can only put the data on the "12,8 GB" drive, from which I also installed GApps.
But it seems I can't install *.apk files from this location and I also have difficulties restoring my Titanium backup files from there (I put them in the TB subfolder).
So far my progress. I only want my backup back and mount my SD card, then I'm done.
can't help you there yet. I am not yet on ICS
But in slimdizzy's latest built he confirms that both cards visible from windows.
remember one is on /sdcard (internal) and the other is /mnt/emmc (external) because that is CM standard.
One of these days I will follow you guys into ICS.
Tried once earlier before the wifi speed was fixed and didn't like it.
I mean looking from the Windows / PC perspective.
There, I have neither of those paths. I hope that is not unusual.
Another point maybe: As I can't use Kies now, how to manage music? I succeeded in putting videos into the "video" folder, but the same doesn't work for music files (in "Music" as *.mp3 files). Probably I'm lacking the basics (I self-teach them to myself ), so a link to a tutorial about all this is more than welcome. But as said, asides from restoring my backup (I'm still looking for a solution...) and the music issue, all is fine. I even managed to install the apps from within the internal storage with the pre-installed file-manager.
Dont know much about the kies and music.
For TB, there is a setting in there for backup folder.
Have you explore the options?
I can put my my backups anywhere and point TB to it and restore.
Sent from my GT-P1000 using XDA App
Actually, now after another restart it did recognize both the music and the missing TB backup files! I'm really a bit sloppy. Now I'm actually restoring successfully.
Now I will only try to find how to remove a few apps (not selected for restore!) from the backup (job). Apps that I actually don't ever want to see on my tablet again.
I'm sure I'll be able to find out myself...
same problem
priyana said:
The commonly known method is to restock according to Overcome 4.1 rom thread
Then install overcome kernel.
That gives you cwm recovery and it also converts your filesystem to ext4.
Then flash the cm9.
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
please help .... im new to this but having the same problem .n i didnt understand what is overcome n how will it solve this issue..please reply
I have replied the same way many times in this forum too
Here goes again:
Overcome ROM is a GB 2.3.6 custom ROM based on Samsung ROM.
We use it a lot because:
1) it has very clear step by step fool proof way to "re-stock" your TAB in a good clean stock condition, upon which you can then install most ROM
2) its kernel, Overcome Kernel 4.0 comes in ODIN flashable and gives you a CWM Recovery 5.x, which is needed to flash other ROMs
3) When flashed, the kernel performs conversion(and support) of RFS filesystem to EXT4 which is better and faster filesystem. This is sometimes desirable.
Go to overcome site
http://www.teamovercome.net/p1000/
Read the guide,
Missing pictures can be seen here.
http://forum.xda-developers.com/showthread.php?p=20974872
Follow the picture step by step.
But please read it many times until you get what it is saying.
Basically to restock:
Download GB-stock-safe-v5.zip, unzip it and and flash with ODIN according to the guide.
Stop there and you will have Gingerbread JQ1
Next step if you want, just continue following the guide.
Basically flash Overcome Kernel tar using ODIN, and it will reboot and converts your filesystem (you hear female robotic voice).
At the end of it, you get CWM recovery (access it while off : press volume-up and power button)
From CWM recovery you can flash any custom ROM you want.
You will find most of them ask you to flash from CWM.

Keep getting partial root... (I've tried at least)

stupid stupid question, but I keep getting partial root (adb su shows # but cannot write to /system)
Root Explorer as well as mount system rw app both cannot mount system as rw
SuperSU binary updates fine
However, what is odd is that I have sucessfully deleted system apps (eg phone.apk), via TIB and they do not run on the phone anymore. I have also occasionally been able to restore them via TIB
I have tried flashing CF-Root LRB via odin, same result.
I have tried flashing Abyssnote42 and then flashing the ROM via abyssnote, but still get partial root.
I don't get it- according to the post in this forum, all I needed to do was flash CF-Root and that should have done it.
I have Mobile Odin Pro, but there are no .tar files which I can find for ICS (everyone is doing CWM releases).
Also, AdAway does not seem to be able to write to the hosts file, which imo seems like it is unable to write to /system.
The very few times TIB has been able to mount /system/app as rw and I have overwritten files, nothing has changed (so it looks like they were never overwritten in the first place).
I want root to be able to write to /system, not use 'kewl root appz'. (Trying to overwrite phone.apk and contacts.apk)... i've also tried making CWM flashable zips but CWM won't flash them...
I have been able to get GB full root by flashing pre-rooted stock, this is all for Kingdroid ICS 4.0.4
Am I missing something? Can CWM install a rooted kernel? Should an Odin flash of a rooted kernel get full root? Sorry for the dumb question, but I really tried
I had same problem tried almost everything and in the last had to flash stock GB to start over again.
guitarplayerone said:
stupid stupid question, but I keep getting partial root (adb su shows # but cannot write to /system)
Root Explorer as well as mount system rw app both cannot mount system as rw
SuperSU binary updates fine
However, what is odd is that I have sucessfully deleted system apps (eg phone.apk), via TIB and they do not run on the phone anymore. I have also occasionally been able to restore them via TIB
I have tried flashing CF-Root LRB via odin, same result.
I have tried flashing Abyssnote42 and then flashing the ROM via abyssnote, but still get partial root.
I don't get it- according to the post in this forum, all I needed to do was flash CF-Root and that should have done it.
I have Mobile Odin Pro, but there are no .tar files which I can find for ICS (everyone is doing CWM releases).
Also, AdAway does not seem to be able to write to the hosts file, which imo seems like it is unable to write to /system.
The very few times TIB has been able to mount /system/app as rw and I have overwritten files, nothing has changed (so it looks like they were never overwritten in the first place).
I want root to be able to write to /system, not use 'kewl root appz'. (Trying to overwrite phone.apk and contacts.apk)... i've also tried making CWM flashable zips but CWM won't flash them...
I have been able to get GB full root by flashing pre-rooted stock, this is all for Kingdroid ICS 4.0.4
Am I missing something? Can CWM install a rooted kernel? Should an Odin flash of a rooted kernel get full root? Sorry for the dumb question, but I really tried
Click to expand...
Click to collapse
Flash back to GB and root and then come to CM9 or CM10.
guitarplayerone said:
stupid stupid question, but I keep getting partial root (adb su shows # but cannot write to /system)
Root Explorer as well as mount system rw app both cannot mount system as rw
SuperSU binary updates fine
However, what is odd is that I have sucessfully deleted system apps (eg phone.apk), via TIB and they do not run on the phone anymore. I have also occasionally been able to restore them via TIB
I have tried flashing CF-Root LRB via odin, same result.
I have tried flashing Abyssnote42 and then flashing the ROM via abyssnote, but still get partial root.
I don't get it- according to the post in this forum, all I needed to do was flash CF-Root and that should have done it.
I have Mobile Odin Pro, but there are no .tar files which I can find for ICS (everyone is doing CWM releases).
Also, AdAway does not seem to be able to write to the hosts file, which imo seems like it is unable to write to /system.
The very few times TIB has been able to mount /system/app as rw and I have overwritten files, nothing has changed (so it looks like they were never overwritten in the first place).
I want root to be able to write to /system, not use 'kewl root appz'. (Trying to overwrite phone.apk and contacts.apk)... i've also tried making CWM flashable zips but CWM won't flash them...
I have been able to get GB full root by flashing pre-rooted stock, this is all for Kingdroid ICS 4.0.4
Am I missing something? Can CWM install a rooted kernel? Should an Odin flash of a rooted kernel get full root? Sorry for the dumb question, but I really tried
Click to expand...
Click to collapse
Had you tried the rooting method of dr ketan. http://forum.xda-developers.com/showthread.php?t=1329360
guitarplayerone said:
stupid stupid question, but I keep getting partial root (adb su shows # but cannot write to /system)
Root Explorer as well as mount system rw app both cannot mount system as rw
SuperSU binary updates fine
However, what is odd is that I have sucessfully deleted system apps (eg phone.apk), via TIB and they do not run on the phone anymore. I have also occasionally been able to restore them via TIB
I have tried flashing CF-Root LRB via odin, same result.
I have tried flashing Abyssnote42 and then flashing the ROM via abyssnote, but still get partial root.
I don't get it- according to the post in this forum, all I needed to do was flash CF-Root and that should have done it.
I have Mobile Odin Pro, but there are no .tar files which I can find for ICS (everyone is doing CWM releases).
Also, AdAway does not seem to be able to write to the hosts file, which imo seems like it is unable to write to /system.
The very few times TIB has been able to mount /system/app as rw and I have overwritten files, nothing has changed (so it looks like they were never overwritten in the first place).
I want root to be able to write to /system, not use 'kewl root appz'. (Trying to overwrite phone.apk and contacts.apk)... i've also tried making CWM flashable zips but CWM won't flash them...
I have been able to get GB full root by flashing pre-rooted stock, this is all for Kingdroid ICS 4.0.4
Am I missing something? Can CWM install a rooted kernel? Should an Odin flash of a rooted kernel get full root? Sorry for the dumb question, but I really tried
Click to expand...
Click to collapse
Last few months ago im also having the same problem. No matter which method i had try..dr.ketan...start from gb...no luck at all. The partial root problem still remain.
Luckily i met someone to gv me help. And his method 100% works.
Please report back if u able obtain full root. Other wise i will gv u the proper step to obtain full root.
Good luck
Sent from my GT-N7000 using xda premium
Maybe the problem lies with busybox. Try getting busybox binary updated. I've read some people can do it by installing busybox from Google Play. For my case usually I inject busybox directly via CWM, but it is potentially dangerous so I won't share it here.
When I had this prob, I tried everything bo no luck, so flashed gb again.
Sent from my GT-N7000
lee yun khong said:
Last few months ago im also having the same problem. No matter which method i had try..dr.ketan...start from gb...no luck at all. The partial root problem still remain.
Luckily i met someone to gv me help. And his method 100% works.
Please report back if u able obtain full root. Other wise i will gv u the proper step to obtain full root.
Good luck
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I am having exactly this problem.
I have tried everything over and over and still partial root.
I would REALLY appreciate your help with getting full root on my note.
u need to give more details. what rom are u on?

Categories

Resources