Related
Well, since no one has mentioned this yet, hope has returned for the quick computerless root, via apk!
This is not my work, it is Chainfire's apk, with Android Exploid Crew's gingerbreak binary inside... brought to you by the makers of rageagainstthecage-arm5.bin... anyways, here's the xda post:
http://forum.xda-developers.com/showthread.php?t=1044765
Note: this only installs su with superuser.apk, and not busybox, from what I've seen, I tested this with stock EC05. I'm glad busybox is not included, since it would be broken, due to the limited space of the stock EC05 system. So for most using this, the first steps, after rooting with this, would be the following:
Edit: new instructions, for installing rooted kernel, and Clockworkmod 2.5.1.0, all without a computer:
* on the phone, goto menu > settings > applications. Make sure Unknown sources is checked. Goto Development, and make sure USB debugging is checked.
* Install the following apps from the market: SGS Kernel Flasher, ROM Manager, Astro File Manager, and Dolphin Browser HD, all available free from the market, the names here are market links, for your convenience. If opening the links on the phone, make sure to choose the market, when opening them.
Note: Astro File Manager is for ease of locating and installing the gingerbreak.apk on your sdcard. Dolphin Browser HD is recommended, so that downloads don't get the names truncated... The stock browser has been known to do this, especially on my kernel zip downloads.
* Grab the gingerbreak.apk from here (I used the 1.2 version of the apk). either tap the apk download from the dropdown menu, or use astro file manager to locate the apk, and install it. Now close astro file manager, and any other apps that may be using the sdcard.
Now it's time to open gingerbreak from your applications, and choose, "Root Device". It may take up to several minutes, before the phone reboots itself. If all has gone according to plan, you will now have a very basic root, with the Superuser app, so that you can control what apps have root permissions. If for some reason you don't have superuser in your apps, or the gingerbreak has frozen past 10 minutes, reboot the phone, and run the gingerbreak app again.
Note: I am not directly linking the apk here, out of respect for Chainfire, who developed this apk... I wouldn't do it without his permission anyways.
* download DRockstar.Clean.Kernel.EC05.v1.02.zip and put on your sdcard
Original kernel post with sources: http://forum.xda-developers.com/showthread.php?t=1053252
* Open SGS kernel flasher, and be sure to give permission when the superuser prompt appears. Tap "choose kernel", tap .. , locate DRockstar.Clean.Kernel.EC05.v1.02.zip on your sdcard, and flash the kernel. It should reboot the phone when done. You'll now be running a rooted stock kernel, with some nice added features.
* download cwm2.5.1.0.zip.
Original ReRFS Stock ROM and tools: http://forum.xda-developers.com/showthread.php?t=1027904
Note: It's a really good idea to download ReRFS Stock ROM, in case you need to stock the phone, in a jam.
* open ROM Manager app, and Tap "Flash ClockworkMod Recovery". Choose the Epic 4G.
The following message will appear:
"Epic4G does not have an officially supported ClockworkMod Recovery yet. Have you installed a ClockworkMod recovery manually?"
choose yes, and select ClockworkMod 2.x.
Next, tap "Install ROM from SD Card". Browse to, and choose the cwm2.5.1.0.zip on your sdcard.
Tap OK at "Reboot and Install", and be sure to give permission, when the superuser prompt appears.
Presto... rooted kernel with full busybox, and Clockworkmod, with no computer needed, for the epic!
Note: Here's cwm3.0.0.6.zip, if you're ready to plunge into ext4. Make sure you have an ext4 compatible ROM ready to flash, on your you sdcard, before converting to ext4. The stock EC05 system will not boot after converting to ext4. Also, be warned, that as of yet, no posted Epic kernels are ROM Manager compatible with ext4, though I am quite certain that tanimn is very hard at work, doing his best to make this happen.
Anyways, I figured all this would be welcome news, and gives me hope again, that an all in one apk can be mustered for the Epic.
I know some are you are saying, "But this is all so complicated, can't you make this any easier?" Well, I say, having dealt with driver and cable issues galore for months, supporting one click root adb scripts... that this is, in fact, no more complicated at all. It may even be easier.
Maybe with some luck and a little skill, I can do a custom apk for us in the future, but for now, this *will* work.
Sent from my SPH-D700 using Tapatalk
It's been mentioned in "themes and apps" where it belongs not here in development.
OK, I did look there first (in the Epic section, anyways), but I must have missed it...
Some of the devs in the irc channel didn't even know, so I thought it was worthy of mention here, as much as a one click root is stickied in this very section.
If this thread needs to be deleted, so be it, I thought I was doing a service, calling people's attention to it, and outlining what steps should be taken, after using it.
Edit: now I see a post in the apps section, but my notes here are still very pertinent, to anyone relying on the gingerbreak.apk
theimpaler747: do what you will on this thread, it was intended as a public service announcement, and just might affect the development of the epic, especially since it'll most likely become the new root for gingerbread. I leave it up to you and your judgement.
Sent from my SPH-D700 using Tapatalk
If we rooted with this method then how do we push custom recovery?
Sent From My Evo Killer!!
musclehead84 said:
If we rooted with this method then how do we push custom recovery?
Sent From My Evo Killer!!
Click to expand...
Click to collapse
Ask damean
Sent from my Samsung-SPH-D700 using XDA App
musclehead84 said:
If we rooted with this method then how do we push custom recovery?
Sent From My Evo Killer!!
Click to expand...
Click to collapse
First off, I suspect any one click scripts for gingerbread, would have to use the gingerbreak binary, also listed and linked in the Chainfire post.
Hopefully, before GB is released (and hopefully a patch hasn't been, for rooter's sake), we can make an apk that flashes a proper recovery in bml8. (Preferably, in my opinion, to cwm 2.5.1.0, until the user decides to convert to ext4, which can be done with a subsequent cwm zip, like the cwm3.0.0.6.zip in my ReRFS Stock ROM post.)
joeykrim has made a kernel flashing apk (FlashImage GUI, in market), but at my behest, left out the ability to flash bml8, due to the fact that if a corrupt kernel is flashed there, odin or heimdall is required to fix it, once a 3 button boot is attempted to a corrupt bml8 flash.
For now, I would recommend a manual bmlwrite bml8 flash for a known good recovery kernel, for anyone using the gingerbreak method.
Also, some kernels, like my Clean Kernel, have reboot recovery to cwm 2.5.1.0 if RFS, and, can be flashed with the free SGS Kernel Flasher apk from the market. Once reboot recovery is achieved, cwm can be flashed to bml8, using the zip tools in the ReRFS post.
Sent from my SPH-D700 using Tapatalk
Just modded the original post, with instructions on getting full rooted kernel, and Clockworkmod, without needing a computer... how about that?
Sent from my SPH-D700 using Tapatalk
DRockstar said:
Just modded the original post, with instructions on getting full rooted kernel, and Clockworkmod, without needing a computer... how about that?
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Haha calm down sir, calm down
Sent from my SPH-D700 using XDA Premium App
Wow good work guys. That's awesome.
Sent From My Evo Killer!!
Woot, woot!! Now my wife can stop climbing down my throat about always being on the computer!! Gimme a woot!!
Sent from my SPH-D700 using XDA App
If only it converted your files to ext4..
Sent from my Samsung Epic
DRockstar said:
Just modded the original post, with instructions on getting full rooted kernel, and Clockworkmod, without needing a computer... how about that?
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Good stuff DRockstar, I'm glad you posted this up for us!
Nice! Very handy indeed.
Sent from my SPH-D700 using XDA App
acer1096xxx said:
If only it converted your files to ext4..
Sent from my Samsung Epic
Click to expand...
Click to collapse
Actually, you can convert to ext4 too, with the cwm3.0.0.6.zip posted in the ReRFS ROM thread... just flash it through cwm 3 button boot, or from reboot recovery with the kernel... keep in mind, that reboot recovery won't work for ext4 with the Clean Kernel, at this point in time.
but anyway, there's still nothing you can't do without a computer!
DRockstar said:
Actually, you can convert to ext4 too, with the cwm3.0.0.6.zip posted in the ReRFS ROM thread... just flash it through cwm 3 button boot, or from reboot recovery with the kernel... keep in mind, that reboot recovery won't work for ext4 with the Clean Kernel, at this point in time.
but anyway, there's still nothing you can't do without a computer!
Click to expand...
Click to collapse
Eh, sounds complex lol. I'll either wait for a video or just do it on a pc, no biggy
Sent from my Samsung Epic
I remember when installing Samsung Drivers, finding a good cord, using Odin, rooting, wiping system/data, Cache Partition, Dalvik, installing zip from SD, choosing zip from SD,etc. sounded like another language to me! If this works, congratulations. It may save many headaches.
Sent from my SPH-D700 using XDA Premium App
Subscribed, for future reference.
Sent from my SPH-D700 using XDA App
zanderman112 said:
Subscribed, for future reference.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Did the exact same thing...
Sent from my SPH-D700 using XDA Premium App
acer1096xxx said:
Eh, sounds complex lol. I'll either wait for a video or just do it on a pc, no biggy
Sent from my Samsung Epic
Click to expand...
Click to collapse
It was actually very simple I just did it not hard at all
Sent from my SPH-D700 using XDA Premium App
Updated, with instructions for ROM Manager zip flashing... muahahahahaha
Also, almost all the links are phone friendly now, especially if you use the Dolphin HD Browser to download files, and the app names, are now market links, in the hopes that will make installing them even easier from the phone.
The only link that is not a direct link, is to the actual gingerbreak.apk itself, which is contained in an xda post, that requires xda registration to see. I respect that and the original dev, and will not give a direct download link, without Chainfire's expressed permission. I do think others will understand this.
Anyways,
Hope you all dig it!
http://forum.xda-developers.com/showthread.php?t=1170232
Someone needs to port this for our LG Optimus One P500.
We all know that Adhoc doesn't work on Android. I've also seen a few thread recommending the use of alternative software on the PC. But one must understand that these software do not support all WiFi adapters and/or need specific OS in order to operate.
If one of our dev can port or make a fresh one, we could vote to make it a "Sticky".
I request you comment your opinion about this.
--------------------------------------------------------------------------
Download the "wpa_supplicant" from the link below and replace it with the one in your rom. It should work.
www.mediafire.com/?939dy6dzmmc2vkp
[Thanks to seriousia for the link]
--------------------------------------------------------------------------
Please click "Thanks" if it works for you.
Use connectify, i am using it
Sent from my LG-P500 using xda premium
DJoptimus-One said:
Use connectify, i am using it
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
Connectify requires Win7, I'm running WinXP. Also, connectify does not support all adapters.
You can checkout the list of adapters which supports connectify:
http://support.connectify.me/home?page=2
Also, was referring to Ad-Hoc, not "Access Point".
Maybe this can help you as it is xp compatible.
http://www.virtual-ap.com/
ashishv said:
Maybe this can help you as it is xp compatible.
http://www.virtual-ap.com/
Click to expand...
Click to collapse
Will definitely give it a try . Anyway, about the "G3 AdHoc Wifi Thread" by "jinxskore", it supports even old onboard laptop adapters which is why we definitely need this. You don't need to download any additional application/software....it will detect the AdHoc like an access point which is absolutely cool. Google could have added that with their updates but God knows why not.
I still think one of our dev should make one. I would if I could but I just started using android a month back and rooted yesterday.
Ad-hoc support for Android
Flash this
www.mediafire.com/?939dy6dzmmc2vkp
M using it
N It works perfectly
Sent from my LG-P500 using XDA App
What is adhoc?
Sent from my LG-P500 using xda premium
seriousia said:
Ad-hoc support for Android
Flash this
www.mediafire.com/?939dy6dzmmc2vkp
M using it
N It works perfectly
Sent from my LG-P500 using XDA App
Click to expand...
Click to collapse
Thanks a ton. Before I proceed, is it possible to just copy it through "Root Explorer" instead of flashing it? This is because I'm on stock 2.2.2 rooted and planning to stick with it for a while.
Also, is there a post dedicated to this particular "supplicant"? Would be really handy if there is one. If not, you could make a sticky
Okay, replaced the wpa_supplicant using "Root Explorer" and YES I can confirm it is working. Thanks a ton.
virusshah1997 said:
What is adhoc?
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
http://en.wikipedia.org/wiki/Wireless_ad_hoc_network
Here, I was referring to "PC-to-Phone" wireless connection which allows internet sharing from the PC to the Phone (not Phone-to-PC) without using any particular OS (eg. Win7) or PC Software (eg. Connectify).
Take a look at the link in the original thread and you'll get the idea of what the post is all about.
novas242001 said:
Thanks a ton. Before I proceed, is it possible to just copy it through "Root Explorer" instead of flashing it? This is because I'm on stock 2.2.2 rooted and planning to stick with it for a while.
Also, is there a post dedicated to this particular "supplicant"? Would be really handy if there is one. If not, you could make a sticky
Okay, replaced the wpa_supplicant using "Root Explorer" and YES I can confirm it is working. Thanks a ton.
Click to expand...
Click to collapse
Wlcm bro
Sent from my LG-P500
Sonygenmod 1.2 Final
problem
so i am able to see the adhoc network i have at home, but now my issue is i am apparently unable to connect to said network. i click connect and it just dismisses the prompt, but with no change to my connection state. ive rebooted the phone many times, disabled data to ensure nothing is coming from 3g, and tried multiple times, so now im at a loss. im also unaware if this has affected my ability to connect to regular networks as i have none available to test right now. any help would be great tho, im still learning my way around adb but these are the commands i used.
adb remount
adb push system/bin/wpa_supplicant /system/bin/wpa_supplicant
adb shell chmod 755 /system/bin/wpa_supplicant
and i was instructed to use this as well but it came with an error
adb shell chown system.wifi /data/misc/wifi/wpa_supplicant.conf
---------- Post added at 09:03 PM ---------- Previous post was at 08:57 PM ----------
so i tried again with that chown command after a restart and it went through, and now it still sees the adhoc network, but once i try to connect it just adds it to the bottom of the list saying out of range, and i try again with no results..
---------- Post added at 09:05 PM ---------- Previous post was at 09:03 PM ----------
maybe someone could provide me with this as an edify ready zip? i couldnt use the other because my recovery doesnt support amend anymore. that would be awesome
Where I can download connectify ....
Mahesh....Android Freek...
mvgadagi said:
Where I can download connectify ....
Mahesh....Android Freek...
Click to expand...
Click to collapse
Google it my friend.
I have a Vista machine.
1) First of all I enabled sharing of LAN card
2) Wifi & LAN were not getting enabled at same time (LAN was given auto precedence), issue was resolved by disabling switching of LAN/WLAN in BIOS
3) Installed Connectify
4) configured it to share my LAN connection over WIFI
Simple!
---------- Post added at 07:14 PM ---------- Previous post was at 06:54 PM ----------
For setting up proxy in my optimus, I used ProxyDroid.
[/COLOR]maybe someone could provide me with this as an edify ready zip? i couldnt use the other because my recovery doesnt support amend anymore. that would be awesome
Click to expand...
Click to collapse
i have attached the edify ready zip of wpa adhoc
and if u need to convert amend script to edify use the other attachment found via googling
i have flashed this but unfortunately i could connect to ad hoc(of my laptop) only once and that too couldnt access the internet.
Now whenever i make ad hoc from my lappy the option of 'share your internet connection' is not present at all!
My phone is a LG p500 rooted, android 2.3.3 original LG ROM, and my sdcard is partioned, I've not updated the kernel yet... I have used ES File Explorer since Root Explorer is now paid and I have no credit card.
I've tried a wpa_supplicant from another forum and now my android just keeps rebooting.
I set the airplane mode and could use ES File Explorer again to restore original file, but, anyway, my phone just works in 3G networks... whenever I turn on the wifi, the phone reboots....
What exactly is this wpa_supplicant, what it does? in linux terms?
Anyway, I'm gonna give a try in this one in this thread...
---------
Update:
Meanwhile, i found out why my original wpa_supplicant was not working... it seems it is not a file, as i was wondering, it is a program... and when i gave it permissions to override, i set wr-wr-wr... but as a program, it must have the EXECUTION permission: wrx-wrx-wrx ... now my wi-fi is working again... but, still, not detecting ad-hoc ...
anyway, i can try again with differente version i backed up my original, and now i know how to fix it...
in case of success, i post here!
---------
Update:
ad-hoc now working! \o/
there are many threads about this subject, so, to help others noobs like me, some notes:
1) root your phone
2) download ES File Explorer on market. it's a free (and very good) alternative to Root Explorer
3) its a good idea to turn off wifi now. better, set airplane mode.
4) in the configs of ES File Explorer, if your phone is rooted, there is an option to mount the /system directory with permissions to write/read and another option to see hidden files. check them on.
5) now, you should navigate to /system/bin/wpa_supplicant and save a copy of this file in a secure location.
6) back to system/bin/wpa_supplicant, press long and in its properties, you can change the permissions of the file to rwx-rwx-rwx
7) now you can copy the wpa_supplicant you found in this forum, to that location, and override the original (dont worry, if you have a backup, its reversible)
8) again, check the permissions of the new wpa_supplicant. it must be rwx-rwx-rwx too. (it's a program, the "x" is needed to execute)
9) that all. it now should work. ad-hoc networks are marked with a (*)... in my case, worked perfectly. My phone is a LG P500 android 2.3.3 original rom.
10) in case of any errors, just try another version of wpa_supplicant, there are some versions here. or, just restore your original wpa_supplicant. remember the permissions.
11) if you have the android sdk in your pc, you can run adb shell wpa_supplicant -v and find out your version... v5 or v6 ... in this forum there are modified wpa_supplicant in versions 5 and 6 ... use the correct according to your rom...
no ta transferring
pfrolim said:
My phone is a LG p500 rooted, android 2.3.3 original LG ROM, and my sdcard is partioned, I've not updated the kernel yet... I have used ES File Explorer since Root Explorer is now paid and I have no credit card.
I've tried a wpa_supplicant from another forum and now my android just keeps rebooting.
I set the airplane mode and could use ES File Explorer again to restore original file, but, anyway, my phone just works in 3G networks... whenever I turn on the wifi, the phone reboots....
What exactly is this wpa_supplicant, what it does? in linux terms?
Anyway, I'm gonna give a try in this one in this thread...
---------
Update:
Meanwhile, i found out why my original wpa_supplicant was not working... it seems it is not a file, as i was wondering, it is a program... and when i gave it permissions to override, i set wr-wr-wr... but as a program, it must have the EXECUTION permission: wrx-wrx-wrx ... now my wi-fi is working again... but, still, not detecting ad-hoc ...
anyway, i can try again with differente version i backed up my original, and now i know how to fix it...
in case of success, i post here!
---------
Update:
ad-hoc now working! \o/
there are many threads about this subject, so, to help others noobs like me, some notes:
1) root your phone
2) download ES File Explorer on market. it's a free (and very good) alternative to Root Explorer
3) its a good idea to turn off wifi now. better, set airplane mode.
4) in the configs of ES File Explorer, if your phone is rooted, there is an option to mount the /system directory with permissions to write/read and another option to see hidden files. check them on.
5) now, you should navigate to /system/bin/wpa_supplicant and save a copy of this file in a secure location.
6) back to system/bin/wpa_supplicant, press long and in its properties, you can change the permissions of the file to rwx-rwx-rwx
7) now you can copy the wpa_supplicant you found in this forum, to that location, and override the original (dont worry, if you have a backup, its reversible)
8) again, check the permissions of the new wpa_supplicant. it must be rwx-rwx-rwx too. (it's a program, the "x" is needed to execute)
9) that all. it now should work. ad-hoc networks are marked with a (*)... in my case, worked perfectly. My phone is a LG P500 android 2.3.3 original rom.
10) in case of any errors, just try another version of wpa_supplicant, there are some versions here. or, just restore your original wpa_supplicant. remember the permissions.
11) if you have the android sdk in your pc, you can run adb shell wpa_supplicant -v and find out your version... v5 or v6 ... in this forum there are modified wpa_supplicant in versions 5 and 6 ... use the correct according to your rom...
Click to expand...
Click to collapse
only it is connecting but no data transferring i am using connectify 3.3 pro to establish ad hoc connection
and running on gb stock and window xp home edition sp3
what I am missing
Install the wifiadhocenabler app from market, this perfectly works on my O1
Sent from my LG-P500 using Tapatalk 2 Beta-5
ramblaklash said:
Install the wifiadhocenabler app from market, this perfectly works on my O1
Sent from my LG-P500 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
apk removed from play store. can u upload it ???
You find the answer with google. It works for me
Long time user of XDA, first time poster! This website has been a constant help and friend through all of the Flashing, Modding and Fixing I've done through my many Smart-phones (All the way back to the HTC StarTrek flip phone).
I have a question about the removal of 3e Recovery on the Samsung Infuse.
-I recently bought it broken and have since repaired the LCD. First thing I
wanted to do was load it up with some Cyanogenmod or the equivalent, and
that's when I Discovered a potentially NEW problem regarding the replacement
of the Recovery file.
-As it is a general rule, to check other threads before making a new one, I have
spent the last week scouring the Infuse page to try and find an answer to my
specific issue, and since none of the fixes posted work, I was wondering if y'all
could help.
-First of all, the Recovery file is not under the System/Bin folder like many of the
walk through videos and Threads mention, it is instead in the root of the phone.
-Secondly, When using Root Explorer to mount the root folder as R/W, I was able
to replace the "Recovery" file with the modified variation. However, whenever I
restart the phone, go into recovery via the 3 button hold, It still gives me the
unsigned error. I exit the Recovery and let it boot up normally, only to find that
the "Recovery" file has been replaced with the original.
-I figured maybe there was a backup on the phone that is auto-subbed in for the
modified file. I do a search for "recovery" via root explorer and find a few more
"Recovery" files. No matter which one I replace, upon reboot, they have been
swapped out for the original "recovery".
I am at a loss... Any help would be greatly appreciated, as I have tried the Odin Methods to a T as well as the Heimdall method for recovery.
Thanks in Advance!
Corey Krattli
P.s. I know Im not the only one with this issue, as Ive seen it posted, but never
responded to. I think it may be a new issue with the 2.3.6
Im new so probably way off, bit when you replaced the recovery file and rebooted into recovery, have you tried to select reinstall packages twice? I just started doing this kind of stuff the last few days, but I know when I pit in 3e I had to reinstall packages twice, then got the green recovery.
Sent from my Infuse 4g running MIUI v1.12.23
Replacing the 3e recovery was on froyo roms you are on gingerbread so you will need to odin the infused kernal to get your moddified recovery just follow the instruction to root rogers infuse even though you may have att its just for gingerbread let the robotic woman voice get done then boot into recovery and flash whichever rom with the instructions from that thread
http://forum.xda-developers.com/showthread.php?t=1197248
its not an issue, its an international change. I've been telling people not to bother with green cwm and 3e since the first voodoo kernels came available. heimdall flash a voodoo gingerbread kernel to the phone and keep it there or keep a backup of both the stock kernel and a voodoo kernel with sgs kernel flasher and swap back and forth. remember you may need to incorperate some fixes for the Rogers based kernels because some wifi stuff and video playback stuff has changed.
"-Secondly, When using Root Explorer to mount the root folder as R/W, I was able
to replace the "Recovery" file with the modified variation. However, whenever I
restart the phone, go into recovery via the 3 button hold, It still gives me the
unsigned error. I exit the Recovery and let it boot up normally, only to find that
the "Recovery" file has been replaced with the original.
After you paste or copied in the new recovery file, did you also change the permissions of the new file?
the other option would be to download sgs kernel flasher from market and flash gtg's CWM-infused-v2.0.1-kernel.zip (for GB) found on his installation page to get red recovery.
I did edit the permission on the alternate recovery file, but to no avail. Every time I reset the phone, The original file is back.
I have not tried the kernel flash, So ill give it a go
Dani897 said:
its not an issue, its an international change. I've been telling people not to bother with green cwm and 3e since the first voodoo kernels came available. heimdall flash a voodoo gingerbread kernel to the phone and keep it there or keep a backup of both the stock kernel and a voodoo kernel with sgs kernel flasher and swap back and forth. remember you may need to incorperate some fixes for the Rogers based kernels because some wifi stuff and video playback stuff has changed.
Click to expand...
Click to collapse
I'm with him on this. There is no need with messing with the 3e recovery or green cwm. Do what he says with using sgs kernel flasher. I have had this phone for a few months and have never messed with the 3e recovery. I keep entropys kernel and KL2 stock kernel in the sgs kernel flasher files on my sd card and flash back and forth. It's a hell of a lot easier this way.
Sent from my SGH-I997 using xda premium
aluthier said:
I did edit the permission on the alternate recovery file, but to no avail. Every time I reset the phone, The original file is back.
I have not tried the kernel flash, So ill give it a go
Click to expand...
Click to collapse
make sure its a gingerbread kernel and pre-disable lagfix if you intend to use the stock everything working including HDMI kernel. its a pain letting the conversion run back and forth.
to do this, open root explorer and navigate to /sdcard and see if there is a "Voodoo" folder. if not then create one making sure only the letter v is capital. then, in the voodoo folder, create a "disable-lagfix" folder all lowercase. this prevents the file system conversion from running. the quote are to represent the exact spelling and case, don't create the folders with quotes in the name. the path should be
/sdcard/Voodoo/disable-lagfix
make sure it matches exactly...
I know that Android cannot connect to ad-hoc wireless AP and there are hacks that replace wpa_supplicant module with a modified one after root. However I am new to Android and also my P6800 (Galaxy tab 7.7) is also relatively new, I don't know which wpa_supplicant version it uses and where the modified version is? Is there anyone who modified P6800 successfully and can connect to adhoc AP?
I also appriciate a detailed instruction from how to root till replacing this module as I am not familiar with these operations.
By the way after root can I upgrade firmware when it is released?
Thank you all for the help!
Push up for more attention
push push!
this forum is so quiet?
push....
olivex said:
push....
Click to expand...
Click to collapse
Well idk, just wanted to help you push! Push! LMAO.
Sent from my E15i using xda premium
Shimizux said:
Well idk, just wanted to help you push! Push! LMAO.
Sent from my E15i using xda premium
Click to expand...
Click to collapse
Yeah, push! push! PYAU.
pump!!
Bump bump bump
Nobody has answer?
Galaxy Tab 7.7 Ad-Hoc enablement in progress
I've rooted my 7.7 tab using the instructions from Pocketnow (very easy and quick). They are specific to the 7.7 tab. I would post the link but I'm not allowed as a new poster!
I'm about to manually copy a new wpa_supplicant file using Root Browser (free from Google Play).
I'll let you know what happens!
Edit:
Managed to copy over the original file but the one I used is obviously not compatible as I couldn't enable WiFi afterwards. It's probably to do with the versions. I'll have to do some more research!
jonnynorris said:
I've rooted my 7.7 tab using the instructions from Pocketnow (very easy and quick). They are specific to the 7.7 tab. I would post the link but I'm not allowed as a new poster!
I'm about to manually copy a new wpa_supplicant file using Root Browser (free from Google Play).
I'll let you know what happens!
Click to expand...
Click to collapse
That's great! I will be right here waiting!
jonnynorris said:
Managed to copy over the original file but the one I used is obviously not compatible as I couldn't enable WiFi afterwards. It's probably to do with the versions. I'll have to do some more research!
Click to expand...
Click to collapse
OK, thanks, this is what I worried, I don't know which one is the good version for 7.7. But have you backed up the original one and restored it?
I also want to know which root you used, if you cannot post link can you remove 'http://www' so it will not be regarded as a link (like I do below)?
There is one worry about root, some people said after root, if you uninstall busybox, wifi will not work:
thegalaxytabforum.com/index.php?/topic/9039-galaxy-tab-gt-p6800/
This is the root I used:
pocketnow.com/android/how-to-root-the-samsung-galaxy-tab-77-without-kies-or-odin
I installed superuser as suggested and WiFi still worked ok (not ad-hoc yet though, obviously!).
It didn't take long at all for the root to be applied.
I'm just attepting a wpa_supplicant that is confirmed working on the 10.1 tab so will let you know...
Edit:
Just tried this:
androidtablethacks.com/android-tablet-hacks/how-to-enable-adhoc-wifi-on-android-tablets/
but no joy for the 7.7.
I now have two alternative versions of the wpa_supplicant file and neither allows Wifi to re-enable after reboot. Restoring to the original file has worked no problem so I haven't needed to re-flash my tab.
I will try to get hold of a 7.7 specific version.
I'm thinking that the only solution may be to get a MiFi unit that will run an infrastructure network that can be detected by the SGT7.7.
I will keep investigating a wpa_supplicant solution.
jonnynorris said:
This is the root I used:
pocketnow.com/android/how-to-root-the-samsung-galaxy-tab-77-without-kies-or-odin
I installed superuser as suggested and WiFi still worked ok (not ad-hoc yet though, obviously!).
It didn't take long at all for the root to be applied.
I'm just attepting a wpa_supplicant that is confirmed working on the 10.1 tab so will let you know...
Edit:
Just tried this:
androidtablethacks.com/android-tablet-hacks/how-to-enable-adhoc-wifi-on-android-tablets/
but no joy for the 7.7.
I now have two alternative versions of the wpa_supplicant file and neither allows Wifi to re-enable after reboot. Restoring to the original file has worked no problem so I haven't needed to re-flash my tab.
I will try to get hold of a 7.7 specific version.
Click to expand...
Click to collapse
Thank you. So there is no good version for 7.7 yet?
As for root, superuser is OK, but the problem is on busybox. I also saw some different versions of root packages, some of which claims to not have busybox inside.
olivex said:
Thank you. So there is no good version for 7.7 yet?
As for root, superuser is OK, but the problem is on busybox. I also saw some different versions of root packages, some of which claims to not have busybox inside.
Click to expand...
Click to collapse
I have come across multiple versions of the wpa_supplicant file but I have not found one that enables ad-hoc on the 7.7 yet. As someone else posted elsewhere, they are a much smaller file size than the stock one (>500kb).
I have not used busybox at all. Once I rooted my device I installed Superuser from the marketplace. This manages all my root permissions.
I have also installed Root Browser to allow file and permissions manipulation of wpa_supplicant.
jonnynorris said:
I have come across multiple versions of the wpa_supplicant file but I have not found one that enables ad-hoc on the 7.7 yet. As someone else posted elsewhere, they are a much smaller file size than the stock one (>500kb).
I have not used busybox at all. Once I rooted my device I installed Superuser from the marketplace. This manages all my root permissions.
I have also installed Root Browser to allow file and permissions manipulation of wpa_supplicant.
Click to expand...
Click to collapse
When I used ipad, it was so convenient to connect to the ad-hoc wifi spot that my Nokia E72 shared. Now with 7.7 I am totally blocked on the way. I can put my IM card into 7.7 to get Internet, but 7.7 is not a convenient phone...
Maybe we have to wait...
Edit: It seems your root.zip (614kb) already includes superuser and busybox.
Hey all! Glad to be apart of the sidekick 4g xda community. i just recently got a SK4G from ebay for 45.99. Works flawlessly. (after a return of a 70$ one that wi-fi didn't work - which ima use groove ip lite to call for free w/my GV number, text with GV app)
So I'm trying to flash CWM recovery to flash custom roms. Here is where I am stuck at:
I'm on the Kv1 stock firmware
I am also rooted
I moved the recovery file to system/bin
i am in a pickle trying to figure out how to install the recovery.zip within the 400mb-ish all-in-one pack i got from an awesome member who compiled it and uploaded it through dropbox
do i flash with odin? does mobile odin work for this device?
i'm trying to navigate it /internal_sd/ the root file so that when i reboot to the system recovery it will flash the voodoo CWM.
but i cant find /internal_sd/ with root explorer. should try es strongs? or just regular odin?
tl;dr - this is exactly where i am stuck
whats the best recovery without having to deal with the mounts?
kinda annoying but after i find a rom i like i dont plan to flash a lot, but would like to try a few roms to find my liking.
what is your fav set up? as in
-whats your fav rom?
-whats your fav kernel?
-whats your fav modem?
any extra advice and everything will be appeciated
ckrummi said:
Hey all! Glad to be apart of the sidekick 4g xda community. i just recently got a SK4G from ebay for 45.99. Works flawlessly. (after a return of a 70$ one that wi-fi didn't work - which ima use groove ip lite to call for free w/my GV number, text with GV app)
So I'm trying to flash CWM recovery to flash custom roms. Here is where I am stuck at:
I'm on the Kv1 stock firmware
I am also rooted
I moved the recovery file to system/bin
i am in a pickle trying to figure out how to install the recovery.zip within the 400mb-ish all-in-one pack i got from an awesome member who compiled it and uploaded it through dropbox
do i flash with odin? does mobile odin work for this device?
i'm trying to navigate it /internal_sd/ the root file so that when i reboot to the system recovery it will flash the voodoo CWM.
but i cant find /internal_sd/ with root explorer. should try es strongs? or just regular odin?
tl;dr - this is exactly where i am stuck
whats the best recovery without having to deal with the mounts?
kinda annoying but after i find a rom i like i dont plan to flash a lot, but would like to try a few roms to find my liking.
what is your fav set up? as in
-whats your fav rom?
-whats your fav kernel?
-whats your fav modem?
any extra advice and everything will be appeciated
Click to expand...
Click to collapse
Welcome. I personally use the red CWM recovery and the Glorious Overdose series of ROMs. I had been using TLS' G.O. v3.2 Bulky until I recently decided to go back to G.O. v1 and flash a few newer things onto it. So, my phone is a franken-phone right now, but it works well.
awesome thanks! currently i am having trouble getting into CWM recovery - orange text. i mount system, backed up recovery, overwrote recovery, placed update.zip at the root of microSD, then used quick reboot to go into recover and i get a csc error thing. something about e signature verification failed. i am rooted, usb debugging, and using a 32microHCSD. heard that i might have to use a non - HDSD? i have a normal 2gb one to try. any ideas on what i may be doing wrong?
ckrummi said:
awesome thanks! currently i am having trouble getting into CWM recovery - orange text. i mount system, backed up recovery, overwrote recovery, placed update.zip at the root of microSD, then used quick reboot to go into recover and i get a csc error thing. something about e signature verification failed. i am rooted, usb debugging, and using a 32microHCSD. heard that i might have to use a non - HDSD? i have a normal 2gb one to try. any ideas on what i may be doing wrong?
Click to expand...
Click to collapse
How are you going about overwriting the recovery file? One thing that took me a while to do on mine was that I had to mount the internal storage as read/write in order for the recovery file to be really overwritten. You'll need a file explorer such as ghost commander (free on Google Play) that can do that. The other thing is maybe the recovery file you have is bad. I don't think so, but you never know. You could also try holding down the volume buttons and the power key when the phone is off to get into recovery.
ged92781 said:
How are you going about overwriting the recovery file? One thing that took me a while to do on mine was that I had to mount the internal storage as read/write in order for the recovery file to be really overwritten. You'll need a file explorer such as ghost commander (free on Google Play) that can do that. The other thing is maybe the recovery file you have is bad. I don't think so, but you never know. You could also try holding down the volume buttons and the power key when the phone is off to get into recovery.
Click to expand...
Click to collapse
i'll try uploading a video of me trying. then at each minute section or second section you could help me. i;ll try the ghost commander app. how do you make a seperate sdcard directory for internal memory? so basically get the recovery file to stick, then restart into recovery and itll work if it sticks?
def gonna hit up gloriousoverdose after
ckrummi said:
i'll try uploading a video of me trying. then at each minute section or second section you could help me. i;ll try the ghost commander app. how do you make a seperate sdcard directory for internal memory? so basically get the recovery file to stick, then restart into recovery and itll work if it sticks?
def gonna hit up gloriousoverdose after
Click to expand...
Click to collapse
I could not for the life of me get Ghost Commander to overwrite the recovery file, although it otherwise looks like a solid, clean app. I tried Root Browser and it worked perfectly. Most likely it was user error, whatever the issue with GC was but in case it does that to you there's another app that might do the job.
ckrummi said:
Hey all! Glad to be apart of the sidekick 4g xda community. i just recently got a SK4G from ebay for 45.99. Works flawlessly. (after a return of a 70$ one that wi-fi didn't work - which ima use groove ip lite to call for free w/my GV number, text with GV app)
So I'm trying to flash CWM recovery to flash custom roms. Here is where I am stuck at:
I'm on the Kv1 stock firmware
I am also rooted
I moved the recovery file to system/bin
i am in a pickle trying to figure out how to install the recovery.zip within the 400mb-ish all-in-one pack i got from an awesome member who compiled it and uploaded it through dropbox
do i flash with odin? does mobile odin work for this device?
i'm trying to navigate it /internal_sd/ the root file so that when i reboot to the system recovery it will flash the voodoo CWM.
but i cant find /internal_sd/ with root explorer. should try es strongs? or just regular odin?
tl;dr - this is exactly where i am stuck
whats the best recovery without having to deal with the mounts?
kinda annoying but after i find a rom i like i dont plan to flash a lot, but would like to try a few roms to find my liking.
what is your fav set up? as in
-whats your fav rom?
-whats your fav kernel?
-whats your fav modem?
any extra advice and everything will be appeciated
Click to expand...
Click to collapse
Going off first post
Please remember this phone has issues with rooting (may be a problem with flashing new roms
The locations
/system/bin
/sdcard/
I stick with ric's nexus jb rom for many reasons it runs smoother then glorious overdose v5 an v4 (v5 is great an v4 is great as well but not for me personally)
Cwm red voodoo is stock with most roms but you need yellow to flash
Kj2 newer is ussually better
(Gb kills keyboard right now so if you want gb you give up keyboard for awhile)
If you have issues you should go stright into them (I don't like reading >.< ill try to help like I have been an I'm sure any user will be glad to help (we need the community strength)
P.s. root browser works flawlessly
Most explores need you to be rooted ill post another file explorer in a bit
If you need the file ill upload each one with a readme txt file (if that's allowed) doubt its not c:
if I can't upload the files you can go into android development an go to sticks or you can go to the ref of mine on buttom of the page
Sent from my SGH-T839 using xda app-developers app
---------- Post added at 04:04 PM ---------- Previous post was at 03:56 PM ----------
immorality said:
Going off first post
Please remember this phone has issues with rooting (may be a problem with flashing new roms
The locations
/system/bin
/sdcard/
I stick with ric's nexus jb rom for many reasons it runs smoother then glorious overdose v5 an v4 (v5 is great an v4 is great as well but not for me personally)
Cwm red voodoo is stock with most roms but you need yellow to flash
Kj2 newer is ussually better
(Gb kills keyboard right now so if you want gb you give up keyboard for awhile)
If you have issues you should go stright into them (I don't like reading >.< ill try to help like I have been an I'm sure any user will be glad to help (we need the community strength)
P.s. root browser works flawlessly
Most explores need you to be rooted ill post another file explorer in a bit
If you need the file ill upload each one with a readme txt file (if that's allowed) doubt its not c:
if I can't upload the files you can go into android development an go to sticks or you can go to the ref of mine on buttom of the page
Sent from my SGH-T839 using xda app-developers app
Click to expand...
Click to collapse
... edit: read 3rd-5th reply
If you get error the best thing to do is odin to kg2 or kd1 (recommend kg2 as its simple [r] to use )
Then re root an it should fix issues overwrite the recovery in system bin .. then you can pull battery put back in hold volume an power for 4-5 secounds should boot into recover (download mode pull batter hold track pad an power for 4-5 sec)
Sent from my SGH-T839 using xda app-developers app