I recently updated to a complete EL26 system with matching ROM kernel and modem...I've noticed when I run speedtest to test my WIFI speed my results are consistantly low getting on average .76 Mbps down where as my EG30 setup got consistantly 15Mbps down...as fast as my comupter...
I was wondering if anybody knew what factors contributed to this descrepency and if anybody had any suggestions on how to fix this problem.
thanks in advance
please keep in mind this is for WIFI ONLY
Just go back to EG30 then. There is no "fix". Certain modems are good in certain areas. Have you tried EL13?
yes i tried EL13 and EK02...at first with EK02 it was as fast as EG30...but soon slowed to .76Mbps
Then stick with EG30 or investigate whether there are conditions other than the modem that might be causing the speed change. Is there intermittent interference from neighbors?
I have noticed that undervolting too much will impact data speed on my device. Just something to look into.
no just two other laptops on this connection...when i run a speedtest on my computer and speedtest on my phone... like one right after the other i get 15 on my comp and less than 1 on my phone...if i go back to EG30...which AIO do i use...can i still use Roms based on EL26...and will i b ok with rogues desperado kernel?
Drumrocker said:
I have noticed that undervolting too much will impact data speed on my device. Just something to look into.
Click to expand...
Click to collapse
thanks...but i havent gotten in to undervolting yet...that was going to b my next venture...actually something i planned on getting into today...so i will keep ur advice in mind...any other advice for undervolting is welcomed
lunchboxVA said:
if i go back to EG30...which AIO do i use...can i still use Roms based on EL26...and will i b ok with rogues desperado kernel?
Click to expand...
Click to collapse
You said EL26 modem is worse than EG30 modem, so that assumes you tested them in isolation, but the statment you made above makes it seem like you are not clear on the differences between Modem, Kernel, and ROM.
To go back to EG30 modem, just use CWM and flash the EG30 modem only with your existing setup (kernel/ROM/AIO/etc). You can find the EG30 modem in my signature. Make sure your CWM is packed with EK02/newer-based kernel.
o no sorry for the confusion i know the difference between the three...i was asking because i have read that wen u have all three matching u get the best results...i do get confused when a rom says its based on for instance el26...i would assume that it means its packaged with the el26 modem...i just dont know what based on means...
and i asked about which aio do i use because when i was on the eko2 setup i flashed aio for eg30 and my phone would get past the bootscreen the screen went black and i had to reflash eko2 and then wen i flashed the matching aio it went through fine
samething with el26...i had an el26 setup and flashed an aio for el13...and it caused the same black screen issue which was only resolved after i installed matching aio
ROM could either refer to the entire Modem/Kernel/ROM set or just the ROM portion, depending on context.
Usually EL26-based ROM is only referring to the ROM portion. It may or may not come bundled with a Kernel and normally isn't bundled with a Modem.
You can tell which modem/baseband you are running by going to menu->settings->about phone->baseband and seeing what it says
AIO is implemented in the ROM portion. It usually is not a good idea to mix/match ROM components.
In theory it is best to have Modem/Kernel/ROM versions to match as that is what was tested together, but in reality people have found you can mix/match the 3 components w/o issues.
sfhub said:
ROM could either refer to the entire Modem/Kernel/ROM set or just the ROM portion, depending on context.
Usually EL26-based ROM is only referring to the ROM portion. It may or may not come bundled with a Kernel and normally isn't bundled with a Modem.
You can tell which modem/baseband you are running by going to menu->settings->about phone->baseband and seeing what it says
AIO is implemented in the ROM portion. It usually is not a good idea to mix/match ROM components.
In theory it is best to have Modem/Kernel/ROM versions to match as that is what was tested together, but in reality people have found you can mix/match the 3 components w/o issues.
Click to expand...
Click to collapse
do you know anything about modifying the sys directory or adding folders to it...im trying to get the enable touchscreen 1 script to work...but it cannot modify the sys directory so it errors out
lunchboxVA said:
do you know anything about modifying the sys directory or adding folders to it...im trying to get the enable touchscreen 1 script to work...but it cannot modify the sys directory so it errors out
Click to expand...
Click to collapse
Not familiar with that script, but /system is mounted read-only, so you need to use your root privileges to remount /system to be read/write
I mean this with all the best intentions, but it sounds like you probably should do some more reading before making too many changes in /system
thanks...all i do is read...but as i said i gave it all the permissions and i did run in root explorer with root access...the folders i create dont stick...and then when i try to use the root explorer included with rom toolbox..it says it cannot create the file even tho it has root access
You've verified you still have root? How did you verify?
sfhub said:
You've verified you still have root? How did you verify?
Click to expand...
Click to collapse
in root explorer in the top is says ro or rw plus there super user is installed...and in system tools which i also have i am required to tick the su box
What happens when you type "su" in adb shell?
The reason I'm asking is you are describing actions that should be working if you have root, but saying they aren't working.
Superuser showing up in the app drawer doesn't actually mean you still have root. It is a database of who gets root permissions. The actual command that gives you root is /system/bin/su or /system/xbin/su
i was doing some readying and it seems like modifying sys folder is more complicated than any other folder including the system folder...but i will try what you just recommended to ensure i have root
so i was messing with adb on the computer I wanted to see what happened if i tried to pull the sys directory to alter it...i made sure i had root access and remounted the system...when i typed in adb pull /sys it caused my cmd to freak out it started scrolling through a million files...i assume it was going through all the files in the directory but each line said special file when it finally stopped it rebooted my phone and kicked me out
lunchboxVA said:
so i was messing with adb on the computer I wanted to see what happened if i tried to pull the sys directory to alter it...i made sure i had root access and remounted the system...when i typed in adb pull /sys it caused my cmd to freak out it started scrolling through a million files...i assume it was going through all the files in the directory but each line said special file when it finally stopped it rebooted my phone and kicked me out
Click to expand...
Click to collapse
So you really wanted to edit /sys rather than /system. I actually thought you were substituting /sys for /system.
/sys aren't real "files". They are mappings to kernel internals that are represented as files. Normal file "operations" may not have the same meaning as you are used to.
Ran Speedtest from about 30 ft away from my router the other night on both my netbook and my phone.. Netbook got somewhere around 12 Mbps and EL26 got around 6.5 Mbps. When you take other factors into account (size of WIFI antenna in a laptop/netbook vs a phone) it isn't that big of a difference.
Related
I am just about to release my new barebones build with a lot of new features but one thing is killing me. I cannot get superuser to work anymore with the latest build and the latest kernel. Rogue tools won't overclock without SU working and that just totall kills the speed of my build =(. The build is based off scoot's release 5 and I am using the latest kernel with and without the module update SU is unaffected. Everything else works though.
What have you changed from the build i sent you that might effect it? Does it work for you with the original build? Things to check are the sysinit.rc, make sure it calls userinit.sh on startup, and also check your userinit.sh in the /bin directory and make sure the su fix is still present in the file Otherwise, try opening the super user app and downloading the latest su binary file, if it fails to install then you most likely have partition permission issues.
I did edit userinit to enable the odex script. I am gonna check that now.
Ok I am pretty sure that was it. how do I add this line to userinit to have it be proper then? /system/bin/odex.sh
aceoyame said:
Ok I am pretty sure that was it. how do I add this line to userinit to have it be proper then? /system/bin/odex.sh
Click to expand...
Click to collapse
You'd need to put it in sysinit.rc like this :
service odex /system/bin/odex.sh
So put that line right at the end then? Or is there a special format it has to go in. Sorry, I have just never had to edit this particular file before lol.
aceoyame said:
So put that line right at the end then? Or is there a special format it has to go in. Sorry, I have just never had to edit this particular file before lol.
Click to expand...
Click to collapse
At the end is fine, you will see some similar lines in there, you may want to add some options such as :
console
user root
oneshot
I don't know what the structure of the odex script is so i don't know which options you will need to get it to run properly but these are the most likely, just experiment and see
I've always put it at the end, after the su fix just as "/system/bin/odex.sh" and nothing else. What does service do? will it run it continuously or just with different permissions?
I would say its more likely that something's gone wrong while you edited userinit.sh, and now it can't be executed.
did you edit it in windows? you may have /n/r line endings now instead of /n
if you did it in linux it may be a permissions problem
fixed! I used the userinit from my old barebones. Something changed in the update. The two looked totally different.
how does one go about accessing these?
Easily customizable if you use a text editor(scripts located in /system/etc/init.d)
I have no idea how to do this, but I do have a text editor
there is a java script in the folder /system/etc/init.d/ that conrols the profiles and screen off battery saver. if you dont know how to find it on your own, you wont be able to edit the java probably.
dkdude36 said:
there is a java script in the folder /system/etc/init.d/ that conrols the profiles and screen off battery saver. if you dont know how to find it on your own, you wont be able to edit the java probably.
Click to expand...
Click to collapse
have to start somewhere, and seems like a reasonable place. How do i find that /system folder?
alaman68 said:
have to start somewhere, and seems like a reasonable place. How do i find that /system folder?
Click to expand...
Click to collapse
Hah I like your attitude. So, do you have adb set up, or would you prefer to use root explorer?
Would like to follow this as well
Lurker for a long time...
just rooted and am using this rom as well.
would like to follow along if you dont mind.
I myself do not know what 'dab' is so root explorer would probably be my way to go.
My bad adb not dab. Stupid iPad spell check.
Adb is a command system through which your phone communicates to the computer through USB. It is very useful for hacking especially in recovery mode. It's not that hard to set up, but you can always just use root explorer and make your life easier.
adb
Ok, is see what you mean.
I was looking for the adb_shell.zip or whatever was needed to get that setup last night but couldnt find it (now i didnt look probably everywhere).
some more information about how i am set up now is:
kernel version: 2.6.32.17-gee557fd [email protected] #15
build: calkulin's evio 2 rom v1.8
software: 3.70.651.1
pri: 1.90_003
hardware version: 3
I used unrevoked to root. I have nand back up transfered to pc, retrieved my MSL, I tried the undervolt to 150 with no success(maybe did it wrong).
I also flashed to Ava_Froyo just to have a look see and then cam back to Calkulin.
dkdude36 said:
Adb is a command system through which your phone communicates to the computer through USB. It is very useful for hacking especially in recovery mode. It's not that hard to set up, but you can always just use root explorer and make your life easier.
Click to expand...
Click to collapse
After reading your thread on rooting, I will go with whatever method you recommend, so I will get root explorer if think that is the easiest way. Totally agree with you about learning as much as possible.
i don't have adb set up
don't worry I haven't forgot about you guys! I'm busy right now but I'll post tomorrow.
abdabbs said:
Ok, is see what you mean.
I was looking for the adb_shell.zip or whatever was needed to get that setup last night but couldnt find it (now i didnt look probably everywhere).
some more information about how i am set up now is:
kernel version: 2.6.32.17-gee557fd [email protected] #15
build: calkulin's evio 2 rom v1.8
software: 3.70.651.1
pri: 1.90_003
hardware version: 3
I used unrevoked to root. I have nand back up transfered to pc, retrieved my MSL, I tried the undervolt to 150 with no success(maybe did it wrong).
I also flashed to Ava_Froyo just to have a look see and then cam back to Calkulin.
Click to expand...
Click to collapse
By what measure are you determining success? Specifically what happened or didn't happen after you flashed that file.
I will say this, if your experience is anything like mine with #15 kernel, good luck getting anything to be executed from the init.d folder. Changing kernels fixed this for me - well, actually i reverted to the an older version of the rom which i had flashed with a diff kernel. But alas, a diff kernel in 1.80 will also fix the problem (or did for me when testing the update)
To the OP, what are you trying to accomplish?
gpz1100 said:
By what measure are you determining success? Specifically what happened or didn't happen after you flashed that file.
I will say this, if your experience is anything like mine with #15 kernel, good luck getting anything to be executed from the init.d folder. Changing kernels fixed this for me - well, actually i reverted to the an older version of the rom which i had flashed with a diff kernel. But alas, a diff kernel in 1.80 will also fix the problem (or did for me when testing the update)
To the OP, what are you trying to accomplish?
Click to expand...
Click to collapse
1. learn how to get to the script
2. Change overclocking without setcpu
I use an NA kernel.
thought this would be a fun project instead of another download / copy / wipe / flash / restore
ok, so baisically, go to root explorer. go to the folder system, in that the folder etc, and in that the folder init.d. init.d holds all the clock and volt hacks calkulin has implimented. hit mount r/w (top right) and then long press on 01cpufreq_screenstate_scaling in init.d. choose edit text or something like that. all of the changable values are at the top. calkulin did that on purpose to make it easy to edit. change some values, and reboot. good luck.
dkdude36 said:
ok, so baisically, go to root explorer. go to the folder system, in that the folder etc, and in that the folder init.d. init.d holds all the clock and volt hacks calkulin has implimented. hit mount r/w (top right) and then long press on 01cpufreq_screenstate_scaling in init.d. choose edit text or something like that. all of the changable values are at the top. calkulin did that on purpose to make it easy to edit. change some values, and reboot. good luck.
Click to expand...
Click to collapse
Dumb question, but if I botch this (failed C++ in college) and it doesn't work, I can wipe / reflash and try again?
The script is already established. You're simply changing the contents of several key variables.
alaman68 said:
Dumb question, but if I botch this (failed C++ in college) and it doesn't work, I can wipe / reflash and try again?
Click to expand...
Click to collapse
yep. root explorer is even smart enough to create a .bak backup file in the same directory for you.
I was looking at the auto root for FB15 and was wanting to know if it would work for my phone, Android version: 2.3.6, Baseband: S:R760.01 K.FB14. Any help is greatly appreciated.
Sent from my SCH-R760 using Tapatalk
^^ Second this. Just got SCH-R760 (SGS II) from USCC, there is currently ZERO support. Thanks!
I've tried the ek02 autoroot three times and it's not able to push the files. SuperOneClick didn't work either.
Sent from my SCH-R760 using xda premium
themac79 said:
I was looking at the auto root for FB15 and was wanting to know if it would work for my phone, Android version: 2.3.6, Baseband: S:R760.01 K.FB14. Any help is greatly appreciated.
Sent from my SCH-R760 using Tapatalk
Click to expand...
Click to collapse
The fb15 on this phone is ics so not going to work on your GB ROM .....maybe steady Hawkin can make you a kernel to root it with Odin ....all you have to do is ask him he may do it
He may port cwm for you too don't hurt to ask
Sent from my SPH-D710 using xda premium
Epix4G said:
The fb15 on this phone is ics so not going to work on your GB ROM .....maybe steady Hawkin can make you a kernel to root it with Odin ....all you have to do is ask him he may do it
He may port cwm for you too don't hurt to ask
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
That would be great! Thanks for the advice, really appreciate it.
not working
from what I hear zergrush no longer works in 2.3.6. I tried manually installing but it fails on the USCC GS2 (SCH-R760)
[+] Found a GingerBread ! 0x00000118
[+] Found a Samsung, running Samsung mode
[*] Scooting ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 149 zerglings ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
mostly working
So I tried it with my SCH-R760 SGS2 I was able to get root boot recovery. Having the FB14 kernel would make this a snap however the Epic 4g Touch is so close it mostly worked. I seem to have intermittent wifi problems but everything else appears to work without issue.
I got the kernel from step two WISHLINK:wiki.rootzwiki.com/index.php/Samsung_Epic_4G_Touch or directly WISHLINK:goo-inside.me/epic4gtouch/kernel/acs-eb30-clockwork-epic-touch-4g-sep-20-4-00-pm.tar
I tried sweet talking USCC, evidently I'm not as charming as I think I am they told me I'm screwed and don't yet have the re-image. However, the above has the phone working and rooted minus a few problems with wifi.
Good luck.
Margey said:
So I tried it with my SCH-R760 SGS2 I was able to get root boot recovery. Having the FB14 kernel would make this a snap however the Epic 4g Touch is so close it mostly worked. I seem to have intermittent wifi problems but everything else appears to work without issue.
I got the kernel from step two WISHLINK:wiki.rootzwiki.com/index.php/Samsung_Epic_4G_Touch or directly WISHLINK:goo-inside.me/epic4gtouch/kernel/acs-eb30-clockwork-epic-touch-4g-sep-20-4-00-pm.tar
I tried sweet talking USCC, evidently I'm not as charming as I think I am they told me I'm screwed and don't yet have the re-image. However, the above has the phone working and rooted minus a few problems with wifi.
Good luck.
Click to expand...
Click to collapse
If you can get the E4GT kernel to boot on your phone then just use it to install su onto your ROM (/system), then put back your original USCC kernel and you'll be rooted with everything working.
So basically if your adb shell has a "#" prompt, you can just use Auto Root Option A on your phone and install root onto your phone's ROM. Just ignore the zergrush status, even though it fails, the script is still smart enough to install root onto your rom in your situation.
Then to get your original kernel back, figure out which partition has the recovery.bin, which is an unused mirror of your original kernel/zImage.
In the case of E4GT, this is partition /dev/block/mmcblk0p6
To get the mirror of your zImage type the following in adb shell
Code:
cd /sdcard
dd if=/dev/block/mmcblk0p6 of=zImage bs=256 count=32765
Now it is very important that the partition you chose above is really the recovery.bin partition, otherwise the file you just created will essentially be junk and won't allow you to boot your phone (ie *IF* you installed it, your phone *would not boot*)
Assuming you had the correct partition, to install it as your running kernel, you can do
Code:
cd /sdcard
dd if=zImage of=/dev/block/mmcblk0p5 bs=256 count=32765
Please don't go jumping into this unless you fully understand what I suggested.
YOU CAN MAKE YOUR PHONE UNBOOTABLE IF YOU DO THINGS WRONG.
I don't have your phone and the partitions could be different, so I'm depending on you to figure out if things don't make sense.
If you are unsure, ask questions before doing anything.
While I'm just understanding partitions and the like I'm able to follow your instructions but the *IF* parts I'd like to question.
I have:
/dev/block/mmcblk0p6
and
/dev/block/mmcblk0p5
I'm not sure how this correlates to the recovery.bin unless it is apart of one of those files. So for the SCH-R760 with FB14 I'd be looking for how to verify this. I can easily run the suggested lines and looks like everything is there. However to get this far it's been several hours and I'm a bit gun shy as I have to work tomorrow and actually need my phone. Again thank you for the suggestions and help. I'm very close. Everything but wifi is working and very well.
did anyone try flashing the cwm from the touch. it should work because the mount points line up the same. if so i can finish the ics rom and give it to who ever is willing to try
---------- Post added at 09:13 PM ---------- Previous post was at 08:56 PM ----------
sfhub said:
If you can get the E4GT kernel to boot on your phone then just use it to install su onto your ROM (/system), then put back your original USCC kernel and you'll be rooted with everything working.
So basically if your adb shell has a "#" prompt, you can just use Auto Root Option A on your phone and install root onto your phone's ROM. Just ignore the zergrush status, even though it fails, the script is still smart enough to install root onto your rom in your situation.
Then to get your original kernel back, figure out which partition has the recovery.bin, which is an unused mirror of your original kernel/zImage.
In the case of E4GT, this is partition /dev/block/mmcblk0p6
To get the mirror of your zImage type the following in adb shell
Code:
cd /sdcard
dd if=/dev/block/mmcblk0p6 of=zImage bs=256 count=32765
Now it is very important that the partition you chose above is really the recovery.bin partition, otherwise the file you just created will essentially be junk and won't allow you to boot your phone (ie *IF* you installed it, your phone *would not boot*)
Assuming you had the correct partition, to install it as your running kernel, you can do
Code:
cd /sdcard
dd if=zImage of=/dev/block/mmcblk0p5 bs=256 count=32765
Please don't go jumping into this unless you fully understand what I suggested.
YOU CAN MAKE YOUR PHONE UNBOOTABLE IF YOU DO THINGS WRONG.
I don't have your phone and the partitions could be different, so I'm depending on you to figure out if things don't make sense.
If you are unsure, ask questions before doing anything.
Click to expand...
Click to collapse
Here is a mount print out of the sgs2 from uscc that i had someone give me.
http://pastebin.com/k0nXEcKt
---------- Post added at 09:19 PM ---------- Previous post was at 09:13 PM ----------
Can't they just odin flash or heimdall flash the kernel/recovery in, that would be easier, then they truly don't have to root the rom first.
ironfisted said:
Can't they just odin flash or heimdall flash the kernel/recovery in, that would be easier, then they truly don't have to root the rom first.
Click to expand...
Click to collapse
They already did that. That is why they have rooted adb through the kernel. The issue is they are using an Epic 4G Touch kernel which causes some things to not work on their phone. I am suggesting they install their root functionality in the ROM and restore their original USCC kernel/zImage.
Since (according to them) they don't have a package to return to stock, basically they don't have a kernel/zImage to flash in ODIN because it was never provided to them.
Their original kernel/zImage is gone because they flashed over it (presumably before backing it up). That is why I gave them instructions to pull the backup kernel/zImage. Once they do that, whether they install that zImage within Android or through ODIN is not really important. The important part is they get the correct partition to use to pull the backup from so that they have a valid kernel/zImage to flash.
---------- Post added at 09:55 PM ---------- Previous post was at 09:42 PM ----------
Margey said:
While I'm just understanding partitions and the like I'm able to follow your instructions but the *IF* parts I'd like to question.
I have:
/dev/block/mmcblk0p6
and
/dev/block/mmcblk0p5
I'm not sure how this correlates to the recovery.bin unless it is apart of one of those files. So for the SCH-R760 with FB14 I'd be looking for how to verify this. I can easily run the suggested lines and looks like everything is there. However to get this far it's been several hours and I'm a bit gun shy as I have to work tomorrow and actually need my phone. Again thank you for the suggestions and help. I'm very close. Everything but wifi is working and very well.
Click to expand...
Click to collapse
Based on the previous pastebin that was posted it looks like the partitions on the USCC GS2 line up with the Sprint E4GT so it should be safe to run what I suggested.
Both /dev/block/mmcblk0p5 and /dev/block/mmcblk0p6 are linux device files that map to partitions in your phone's EMMC memory.
mmcblk0p5 is labeled zImage (on Sprint) and mmcblk0p6 is labeled recovery.bin (on Sprint). They have the exact same contents. zImage is the kernel and recovery for your phone.
recovery.bin is not being used (on Sprint) so it basically ends up being a backup of your zImage/kernel. Since you overwrote your USCC zImage with the Sprint E4GT zImage (presumably before backing it up) you cannot recover the original from your phone using the partition assigned to zImage.
I am suggesting you retrieve your original zImage from what is essentially a backup in the partition labeled recovery.bin (mmcblk0p6). This can then be installed in your zImage partition (mmcblk0p5) either directly through Android or through ODIN.
Once you create the zImage file as above, keep a copy off your phone on your PC just in case.
The whole purpose of putting back your original USCC zImage/kernel is so all the features work again, but since your root was achieved through the kernel, putting back the original zImage/kernel would cause you to lose root. That is why I suggested, prior to putting back the original USCC kernel, you install persistent root inside your ROM (ie /system)
You can do that by running Auto Root - Option A and ignoring the Blue Hellions error. If your adb is rooted as you described above, Auto Root will still install persistent root in your ROM despite the failure of the zergrush exploit. Once you install the persistent root in your ROM, you can restore the original USCC kernel/zImage and still have root for your applications. You can confirm that Auto Root - Option A did its job by typing:
Code:
ls -l /system/xbin/su
and verifying su is there and it has the proper permissions. If you are unsure, post the output and I can confirm.
What didn't work? maybe its a matter of the rom difference that makes stuff not work. Just an idea. I was thinking of porting the ics rom over to the sgs2 for them.
ironfisted said:
What didn't work? maybe its a matter of the rom difference that makes stuff not work. Just an idea. I was thinking of porting the ics rom over to the sgs2 for them.
Click to expand...
Click to collapse
As mentioned by Margey's post, the wifi wasn't working well. wifi drivers are in the kernel. Margey installed just the kernel/recovery, not the ROM.
sfhub said:
As mentioned by Margey's post, the wifi wasn't working well. wifi drivers are in the kernel.
Click to expand...
Click to collapse
hmmm, so ics is still doable then. hmmmmmm
I just wanted to thank everyone for their help it is very much appreciated. I'm going to try what sfhub posted. I still have my stock kernel since I've been working and haven't had time to do anything. I will try and make a copy of my stock kernel. Can I push superuser into my rom using adb or do I need to flash the Epic 4G's kernel then push superuser and then flash my stock kernel back.
Sent from my SCH-R760 using xda premium
eureka
sfhub said:
They already did that. That is why they have rooted adb through the kernel. The issue is they are using an Epic 4G Touch kernel which causes some things to not work on their phone. I am suggesting they install their root functionality in the ROM and restore their original USCC kernel/zImage.
Since (according to them) they don't have a package to return to stock, basically they don't have a kernel/zImage to flash in ODIN because it was never provided to them.
Their original kernel/zImage is gone because they flashed over it (presumably before backing it up). That is why I gave them instructions to pull the backup kernel/zImage. Once they do that, whether they install that zImage within Android or through ODIN is not really important. The important part is they get the correct partition to use to pull the backup from so that they have a valid kernel/zImage to flash.
---------- Post added at 09:55 PM ---------- Previous post was at 09:42 PM ----------
Based on the previous pastebin that was posted it looks like the partitions on the USCC GS2 line up with the Sprint E4GT so it should be safe to run what I suggested.
Both /dev/block/mmcblk0p5 and /dev/block/mmcblk0p6 are linux device files that map to partitions in your phone's EMMC memory.
mmcblk0p5 is labeled zImage (on Sprint) and mmcblk0p6 is labeled recovery.bin (on Sprint). They have the exact same contents. zImage is the kernel and recovery for your phone.
recovery.bin is not being used (on Sprint) so it basically ends up being a backup of your zImage/kernel. Since you overwrote your USCC zImage with the Sprint E4GT zImage (presumably before backing it up) you cannot recover the original from your phone using the partition assigned to zImage.
I am suggesting you retrieve your original zImage from what is essentially a backup in the partition labeled recovery.bin (mmcblk0p6). This can then be installed in your zImage partition (mmcblk0p5) either directly through Android or through ODIN.
Once you create the zImage file as above, keep a copy off your phone on your PC just in case.
The whole purpose of putting back your original USCC zImage/kernel is so all the features work again, but since your root was achieved through the kernel, putting back the original zImage/kernel would cause you to lose root. That is why I suggested, prior to putting back the original USCC kernel, you install persistent root inside your ROM (ie /system)
You can do that by running Auto Root - Option A and ignoring the Blue Hellions error. If your adb is rooted as you described above, Auto Root will still install persistent root in your ROM despite the failure of the zergrush exploit. Once you install the persistent root in your ROM, you can restore the original USCC kernel/zImage and still have root for your applications. You can confirm that Auto Root - Option A did its job by typing:
Code:
ls -l /system/xbin/su
and verifying su is there and it has the proper permissions. If you are unsure, post the output and I can confirm.
Click to expand...
Click to collapse
I doubled checked su, good. Re-ran the image per your suggestion, all good. I have wifi, I have 3G, I have phone and I have root and CWM.
Thank you.
I have been trying to use the auto-root method after installing the recovery kernel and it keeps saying waiting for device to connect? How can I get it to see my device?
themac79 said:
I have been trying to use the auto-root method after installing the recovery kernel and it keeps saying waiting for device to connect? How can I get it to see my device?
Click to expand...
Click to collapse
You can actually just copy the files to your sdcard and run the script by hand, but the specific reason it is waiting for your phone is because ADB cannot see your phone.
That might be because you haven't enabled USB debugging. It might be because of driver problem. It could be because your ##8778# setting is incorrect.
Have you ever been able to use "adb" with your phone?
sfhub said:
You can actually just copy the files to your sdcard and run the script by hand, but the specific reason it is waiting for your phone is because ADB cannot see your phone.
That might be because you haven't enabled USB debugging. It might be because of driver problem. It could be because your ##8778# setting is incorrect.
Have you ever been able to use "adb" with your phone?
Click to expand...
Click to collapse
I finally got it, the problem was I was missing a driver for my phone. Now I'm trying to make a copy of my stock kernel using your instructions but for some reason when I type cd /sdcard it says it can't find the path specified. It shows my device listed, I don't know what I'm doing wrong? Wait..do you mean to use my phone to make a copy?
themac79 said:
I finally got it, the problem was I was missing a driver for my phone. Now I'm trying to make a copy of my stock kernel using your instructions but for some reason when I type cd /sdcard it says it can't find the path specified. It shows my device listed, I don't know what I'm doing wrong?
Click to expand...
Click to collapse
Are you doing that from an "adb shell"?
You can replace with "cd /data/local/tmp", it can really be any directory where you have write permissions.
If you want to be more bold, you can skip the step of creating a zImage file and write directly from the recovery.bin partition into the zImage partition. The zImage file is nice because if you screw things up and your phone won't boot, you can still use ODIN to flash the zImage (assuming you moved it to your PC)
Code:
dd if=/dev/block/mmcblk0p6 of=/dev/block/mmcblk0p5 bs=256 count=32765
NOTE: Due to the fact that the Jellybean build went smoother and we all want the latest candy anyway, I've scrapped this effort. Get your candy at: http://forum.xda-developers.com/showthread.php?t=1867579
DISCLAIMER: This is a test build. It works for me, and I spent a good bit of time cleaning up the rough edges and fixing a few silly things, but for all I know it will make zombie worms run out of your tab resulting in your untimely death without warning. If you're not comfortable hacking a Galaxy-series android, probably best to wait for the official update from Samsung and be a good compliant end user and update with Kies... If the death star ever lets the ICS update out, that is.
As Cyanogen likes to say on his work in progress repos: MAY EAT YOUR CAT
ALSO: This is wholly unsupported and I have no affiliation with the Cyanogenmod team. If you bug them for help with this, they will send a laser-equipped triangle-shaped monolith of a hovercraft to your location and decimate anything in your general vicinity with insane force and completely reckless abandon. Well, maybe not, but you get the idea. Don't piss off superman.
First, the bad.. I'm going to start a list of what seems broken:
- Camera. Tablet reboots on snapping photo, preview is 90 degrees off.. weird.
- Google Talk: Looks related to the camera problem. All seems to center around some camera effects issue. Talk.apk from the original honeycomb image does work, so if you need google talk, just swap it out.
Taking what I learned from building CM10 for this device, I grabbed the CM9 tree, which is supposedly final now, and built that too. This time, I'm dropping a flashable .zip, since CM9 is "solid" and won't be updated any more. That doesn't mean this is perfect, as Cyanogenmod is only the android framwork -- The dirty low level bits still come from the OEM, and samsung hasn't released those yet, but.. It's good enough for me, so... Maybe it is for you too!
Since AT&T is still jerking around with the official ICS update, worried about their pathetic "value added" software instead of dropping a clean build, there's no official, fully regression tested radio/RIL combo... So I've yanked the RIL from the Note, a very similar device. It seems to work, but may or may not get LTE at first -- Might stick in HSPA mode a bit, might get LTE, it's a little flaky. May work better in your area, may also depend on network conditions. I'm not completely up to speed on cellular tech so the cryptic debug output doesn't say much to me. However, unlike my work with Jellybean, at least the stock radio works on ICS... For me. If you flash this, please share your 3G/4G experience, and be sure to indicate which carrier and area you are in, if you don't mind.
In Settings, Wireless/Network, More..., Mobile Networks... There is a network mode option. Be sure that is set to LTE/GSM, not GSM. In ICS, this setting actually seems to work - In Jellybean, it does nothing.
WiFi should work without any effort, bluetooth too, and it has the phone app, so you can voice call. Video playback works, audio works, GPS works, and I didn't run into troubles with about 10-15 of the more popular apps from the market.
Tether works, and I changed the tether service to hand out the google DNS server (8.8.8.8/8.8.4.4) to clients, because AT&T's DNS tends to be annoyingly slow.
I also noticed stagefright (a video rendering library, among other things) refused to play anything besides the base-quality x264 videos, so I commented out the retarded bailout (return with unspecified error) in stagefright.so, because all the better-quality youtube videos just refused to play with no reason, just a generic error (what a POS) - So have fun watching HD videos on youtube, although some of the top-quality ones (1080) are a bit on the tough side for the GPU to render. Ah well, beats a non-sensical error.
Samsung did already release the 3.0.8 ICS kernel, for the SHV-140, which is the same hardware with a different radio.. That kernel, in it's .config, has an option for the SGH-i957, so I built that and stuffed resulting kernel binary into boot.img, and packed that into the zip. boot.img also enables early ADB, so you can adb shell into it even if the framework completely shats itself, which it sure did before I got the proper production-level Adreno 220 drivers straight from qualcomm into the build. So the main advantage of this build over jellybean right now is an official Samsung kernel built from their unmodified source code and official release Qualcomm GPU driver binaries.
I also changed apns-conf.xml to use the proper "Broadband" APN for AT&T LTE data-only, as is usually sold with these tablets.
To get this going, start with TWRP recovery -- if you don't have it already, visit that thread in this forum and get yourself hooked up, drop the zip in /sdcard, boot into recovery and..
1) Make a complete TWRP backup before you do anything further! (of course)
2) Wipe -> Factory Reset
3) Wipe -> System
4) Install the .zip I'm about to link you to
5) Reboot, receive bacon.
http://d-h.st/W3X
I've not tested everything and anything, and some things may not be fixable until we get the binary bits from Samsung when they drop ICS officially for this device. However, please report any problems you have here. If I can find time to reproduce and fix, you might get lucky
Enjoy! Honeycomb got boring long ago!
Appreciate all the work. I'll hopefully have time to flash tomorrow. Looking forward to dumping honeycomb.
really glad to see developement picking up for this tab!
I never use the camera or the 4G. I'm gonna flash this in the am. Thanks!
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Flashed and currently running this build. Looks stable enough so far, a couple of FC's but definitely manageable. I know this far fetched but once CM9 gets more stable, will we be able to start porting cm9 based roms? Or can we only port roms created for devices with similar CPU/structures/etc?
Sent from my SAMSUNG-SGH-I957 using xda premium
This is great, thanks for the build. Working great for a 1st edition. From a few minutes playing with it, I noticed that vibrate doesn't work nor does MTP (drivers refuse to install). Not deal breakers and I'm going to use this as my main OS - much better than honeycomb.
I can confirm that this is working very well on rogers, havent tested all functions but my tablet is now 10 times better, currently running Apex launcher. Dont forget to flash gapps for ics....
Something is up with package manager, can't install xda app
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Confirming difficulty with package manager, for both side loading and loading from the Google Play App. However, if I load from the Google Play website the installation works.
Other than that I'm very impressed by the quality and stability of what you've built here - many thanks.
My package installer seems to work just fine.
70ish apps from the play store installed fine, and a dozen or so non market apps.
Ive had some good success with this rom and my apps are installing as well. I do have a situation where I tried using an update to rom manager and it seemed to have broke my recovery and I cant get it back! I would like to try using twrp and how do I install it? I would flash through odin but I don't have the file :crying:
cottageboy said:
Ive had some good success with this rom and my apps are installing as well. I do have a situation where I tried using an update to rom manager and it seemed to have broke my recovery and I cant get it back! I would like to try using twrp and how do I install it? I would flash through odin but I don't have the file :crying:
Click to expand...
Click to collapse
Yikes! Never good when you lose recovery, that's a bad place to be. I'm assuming you have a working image on the device that isn't locked down? IE the CM9 image and/or a rooted honeycomb image is still functional?
Recovery image at:
https://dl.dropbox.com/u/69488769/twrp_recovery_SGHI957_2.2.1.5.img
From a shell, either via adb or via the terminal, just dd (block copy) the image to the recovery partition
dd if=twrp_recovery_SGHI957_2.2.1.5.img of=/dev/block/mmcblk0p22
That should solve that
dan-htc-touch said:
Something is up with package manager, can't install xda app
Click to expand...
Click to collapse
I'm getting an "Error Processing Purchase" on the xda FREE app?? logcat shows google's server returns HTTP/500
Code:
E/Volley ( 8075): [386] BasicNetwork.performRequest: Unexpected response code 500 for https://android.clients.google.com/fdfe/purchase
HTTP 500 = Server Error
Looks like a problem others have had and may relate to the app caching information it shouldnt?
http://code.google.com/p/android/issues/detail?id=30039
also,
http://forum.xda-developers.com/showthread.php?t=1695519
After clearing the play store's DB, the google services framework database, and removing/readding my google account, the error went away.
Then I got another vague error, which the following text from logcat explained:
I/PackageHelper( 3428): Size of container 5 MB
E/PackageHelper( 3428): Failed to create secure container smdl2tmp1
D/VoldCmdListener( 157): asec create smdl2tmp1 5 fat {} 10012
E/Vold ( 157): Error creating imagefile (Read-only file system)
E/Vold ( 157): ASEC image file creation failed (Read-only file system)
W/Vold ( 157): Returning OperationFailed - no handler for errno 30
E/DefContainer( 3428): Failed to create container smdl2tmp1
Click to expand...
Click to collapse
Anyone know anything about how to configure the ASEC location? I've never delved into ASEC and probably need to configure something in the image to account for handling ASEC transactions.
... Looks like I'll need to tweak a few things in the initial ramdisk to get the asec mountpoint correctly set. Good grief, the freaking thing wants to set up a loopback block device on a tmpfs partition to install an application. That's pretty sad... /hacking it
I'm confused. How do I log into my Google account? Where's "my files" folder?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
ZX6Chris said:
I'm confused. How do I log into my Google account? Where's "my files" folder?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
You need to flash gapps for ICS for your Google account and apps.
The "my files" app does not exist on AOSP. You will need to download another file explorer.
Excellent work so far!
Snappy and mostly stable it seems.
Clicking on storage under settings causes a FC, the camera is derpy as stated in the op, and an occasional YouTube derp as stated in the op.
No hapatic at all either.
3g/hspa+/4g lte all working perfectly here.
Thanks!!
neubauej said:
Clicking on storage under settings causes a FC
No hapatic at all either.
Click to expand...
Click to collapse
Interesting, I'll check into that, thanks for that!
It Appears haptic feedback works with the keyboard, and on the home screen softbuttons. immvibed is running and doesn't register any complaints -- atleast that's how it is on my tab. does it not work at all for you?
storage FC: It's looking for /storage/sdcard1, the secondary SD card, which doesn't exist, and it has no error handling for this condition, so it explodes with java exception and the Settings process thus dies.. I believe I just need to yank that definition (for non-existent sdcard1) out of the xml for this package and rebuild, will try that next build!
Figured out the package manager issues, needed to mount tmpfs on both /mnt/secure and /mnt/asec and open up the permissions. That's unfortunately an initial ramdisk (root filesystem) hack, which means a new boot image.
attached. if you're not sure what to do with this, probably best to wait until i roll a few more fixes into a fresh flashable zip.. Otherwise, block copy to mmcblk0p8, reboot.
Been fighting with the camera issue, not having much progress there.
Thanks for the feedback, folks!
when im in my file explorer, where do I find the recovery portion?
im assuming that I put the img file there and using terminal emulator run your commands (do i have to type su first)?
nrvate said:
Yikes! Never good when you lose recovery, that's a bad place to be. I'm assuming you have a working image on the device that isn't locked down? IE the CM9 image and/or a rooted honeycomb image is still functional?
Recovery image at:
https://dl.dropbox.com/u/69488769/twrp_recovery_SGHI957_2.2.1.5.img
From a shell, either via adb or via the terminal, just dd (block copy) the image to the recovery partition
dd if=twrp_recovery_SGHI957_2.2.1.5.img of=/dev/block/mmcblk0p22
That should solve that
Click to expand...
Click to collapse
cottageboy said:
when im in my file explorer, where do I find the recovery portion?
im assuming that I put the img file there and using terminal emulator run your commands (do i have to type su first)?
Click to expand...
Click to collapse
There is no recovery partition to find in root explorer.
Just put the image file in your root directory (/sdcard).
Type "su" enter then the command.
I don't remember if you need to do it as a superuser, but it will certainly work if you are.
cottageboy said:
when im in my file explorer, where do I find the recovery portion?
im assuming that I put the img file there and using terminal emulator run your commands (do i have to type su first)?
Click to expand...
Click to collapse
The recovery emmc partition is /dev/block/mmcblk0p22. The dd command block copies the recovery image (twrp_recovery_SGHI957_2.2.1.5.img) from the filesystem to the emmc partition. if= specifies the image to read from, of= specifies the device to write the image to.
The recovery image is a raw partition image.
You will need to be root to do this.
If you're not comfortable operating on the command line, dan offered a apk to do this: http://db.tt/DXtF5iB6 -- from his TWRP thread @ http://forum.xda-developers.com/showthread.php?t=1697610
Finally got time to flash cm9. Block copied the fixed boot image. Running great. Amazing for a first build. Like a new tablet. Thanks!
i have a few apps that can disable them but the changes are reset every reboot none of them can make changes stick. i've heard of a few file editing ways to make it stick but most of those say they only work for specific phones and haven't found one for lg nitro yet. my problem is i had to replace a digitizer and the new lights on the new one are too bright and offcentered so i just want the lights off because everything else is working and i dont need the lights anyways. Thanks for any help.
if you're using stock ICS rom, there is an option to disable it in settings and it stays on reboot.
for other roms, try this app, not sure if it works.
https://play.google.com/store/apps/details?id=com.deskangel.kblight&hl=en
ightsrti purpose
arda99 said:
if you're using stock ICS rom, there is an option to disable it in settings and it stays on reboot.
for other roms, try this app, not sure if it works.
https://play.google.com/store/apps/details?id=com.deskangel.kblight&hl=en
Click to expand...
Click to collapse
i have that app its one of the only ones that will turn the lights off, but it doens't stick on boot and after boot i have uncheck recheck the option every time, it is right not he only solution but its not convenient, looking for something more perm. i'm running CM10.0.0 with apex launcher.
by the way thanks for the fast response, it's ironic because i lost my stock rom because of a faulty flash of CWM recovery, my backup rom is the stock AT&T ROM, do you know if this rom has the option? it's gingerbread i think. I'm also wondering if flashing to that rom, disabling the lights, then flashing CM10 again would solve the problem. but i asume when flashing cm10 i would lose the solution and the lights would come back on after booting into cm10 the first time. Any more help on a perm solution would be appreciated. i know there are perm soltuions for other phones but i hvaen't found one that works with p930 yet, i've even seen some for optimus 2x and G but they won't work on LTE, even rootdim doesn't work i've already contacted the developer and told him i can help him with compatibily if he needs anything from my phone to help update rootdim for p930 incase other people are having this problem as well., the problem is mostly that LTE screen is incredibly good and bright, and i dont want to wreck the clarity with my aftermarket digitizers overlight bright cap button lights blaring into my eyes and ruining the beauty of the HD screen on this thing. I mean after all how many of us need lights to tell us where our back/home/menu buttons are... i mean i googled this problem and there are hundreds of people trying to disable them on almost any phone you can think of, with varying success.
KronicSkillz said:
i have that app its one of the only ones that will turn the lights off, but it doens't stick on boot and after boot i have uncheck recheck the option every time, it is right not he only solution but its not convenient, looking for something more perm. i'm running CM10.0.0 with apex launcher.
by the way thanks for the fast response, it's ironic because i lost my stock rom because of a faulty flash of CWM recovery, my backup rom is the stock AT&T ROM, do you know if this rom has the option? it's gingerbread i think. I'm also wondering if flashing to that rom, disabling the lights, then flashing CM10 again would solve the problem. but i asume when flashing cm10 i would lose the solution and the lights would come back on after booting into cm10 the first time. Any more help on a perm solution would be appreciated. i know there are perm soltuions for other phones but i hvaen't found one that works with p930 yet, i've even seen some for optimus 2x and G but they won't work on LTE, even rootdim doesn't work i've already contacted the developer and told him i can help him with compatibily if he needs anything from my phone to help update rootdim for p930 incase other people are having this problem as well., the problem is mostly that LTE screen is incredibly good and bright, and i dont want to wreck the clarity with my aftermarket digitizers overlight bright cap button lights blaring into my eyes and ruining the beauty of the HD screen on this thing. I mean after all how many of us need lights to tell us where our back/home/menu buttons are... i mean i googled this problem and there are hundreds of people trying to disable them on almost any phone you can think of, with varying success.
Click to expand...
Click to collapse
and im not as stupid as i might sound by my rambling way of speaking lol. i was able to get all the mods onto my phone and repair a smashed digitizer by myself (which requires taking the entire phone about and motherboard out of the phone and putting it back together) i just hated english class and it now shows
you can try this one:
http://forum.xda-developers.com/showpost.php?p=30698163&postcount=2
Code:
echo 0 > /sys/class/leds/button-backlight/max_brightness
the exact path of "max_brightness" might vary and if so,
Code:
find /sys -name max_brightness
Try these commands via rooted adb shell or terminal emulator, if it works then modify init.d to set it on every reboot.
arda99 said:
you can try this one:
http://forum.xda-developers.com/showpost.php?p=30698163&postcount=2
Code:
echo 0 > /sys/class/leds/button-backlight/max_brightness
the exact path of "max_brightness" might vary and if so,
Code:
find /sys -name max_brightness
Try these commands via rooted adb shell or terminal emulator, if it works then modify init.d to set it on every reboot.
Click to expand...
Click to collapse
how would i go about modifying the init.d to add this, when i executed the command line the lights turn off as desired =P thanks for your help thus far i just haven't modify'd that file before and it's a system file i can see so i'd rather not go trial and error, thanks again so far if you could give me a step by step to add the modifications that would be optimal.
*edit* i gave u a thanks for atleast teaching me where the file is
is it just a text file i open and add the code to? if so does it matter where i add the code (top/bottom)
ok nevermind, i navigated to it out of curiousity and i see that its a folder and obviously not a text file... however im still not sure what to do from here do i drop a text file with that code in it or something ? if so what do i name the file ? if not do i add the code to one of the two files here? the two files i see here are 00banner and 90userinit
after stopping to think i would assume that the userinit file would make most sense, if i remember correctly i actually think i can put it anywhere im just being careful and double checking. two things i'm a little hazy on, can i just add it to the end of the userinit file, if so do those commands require ; at the end of them? because everything else in this file except the loop counter has ;
thanks in advance, i also have another question, i read somewhere on these forums that the system/ folder gets reflashed at every boot, if this is true wont that overwrite this file? if that is true if i was to create a custom file and add it, would that get deleted whent he system is reflashed? does it delete the entire directory and rewrite it or just readd the files because if it was copying over the old files i think that would mean i should actually create a new file called something like dislights. just to verify if this is the case would a file with this text in it suffice.
chmod 666 /sys/class/leds/button-backlight/max_brightness
echo 0 > /sys/class/leds/button-backlight/max_brightness
chmod 444 /sys/class/leds/button-backlight/max_brightness
or do i need some type of header and footer or semicolons at the end like this
{
chmod 666 /sys/class/leds/button-backlight/max_brightness;
echo 0 > /sys/class/leds/button-backlight/max_brightness;
chmod 444 /sys/class/leds/button-backlight/max_brightness;
}
sorry for all the questions im just paranoid about altering system dir when im not 100% sure what im doing.
Download and extract the attachment, put it in /system/etc/init.d, and set permission to rwxr-xr-x, you might need es explorer(enable root options) or root explorer to do so.
thanks for reply, just performed that operation, rebooting fingers crossed.
confirmed works. !!!! yay thanks man i'm going to give you another official forum thank you after im done writing this.
*note* from what i have been reading over the passed few hours, some phones my need to have the init.d activated to work on bootup automatically. the following link will provide a solution for almost all phones (even unrooted) to apply this solution. Although you need root permission to actually write files to the init.d and change permissions. thanks to everyone who contributed to this solution.
edit : adding link i forgot lol
http://forum.xda-developers.com/showthread.php?t=1710980
glad to know it works for you.
init.d is usually missing on stock roms but available on most, if not all 3rd party roms.