Hello all!
I just updated now to rc33 and I knew my themes wouldn't work but I am ok with that. I do use phone as modem pretty frequently but now when I try to setup tether 1.6 it don't work. I am wondering if anyone has been able to get it working yet.
Stuck at the part where I type xf /sdcard/tether-1.6.tar
term says xf not found. Any ideas? Thanks
Oh wow, I totally forgot about tethering, Ill give it a try, I am running 1.3JF kernel running rc33 firmware (thanks to quietlurker). Ill tell you how it goes.
I just set it up and it works for me. Did it to show up a cocky iphone friend and let him connect his iphone wifi to me hehe.
Stuck at the part where I type xf /sdcard/tether-1.6.tar
Click to expand...
Click to collapse
Not sure if its a typo but you forgot the tar it should be
tar xf /sdcard/tether-1.6.tar
Hope that helps.
M9x3mos said:
Hello all!
I just updated now to rc33 and I knew my themes wouldn't work but I am ok with that. I do use phone as modem pretty frequently but now when I try to setup tether 1.6 it don't work. I am wondering if anyone has been able to get it working yet.
Stuck at the part where I type xf /sdcard/tether-1.6.tar
term says xf not found. Any ideas? Thanks
Click to expand...
Click to collapse
are you typing "xf" or "tar xf"?
You only need to tar once.
From then on, just make sure you 'su' and then 'tether start'.
But yes, worked fine for me. Once I turned my wifi back off. doh!
Anyone seen this?
http://forum.xda-developers.com/showthread.php?t=480067
Worked fine for me
Worked here without any problem.
I wiped my phone before RC33, and I did have problems getting it to work. The solution was very simple--the tar command was extracting to the SD card rather than root, so I just did:
tar -xf /sdcard/tether-1.6.tar -C /
This put it in root where it belonged. Then I removed the folder on my SD card.
wow, that tetherWifi app is great. 40 seconds after seeing the link i was tethered up and getting 350kbps speeds to my laptop. this alone makes the rooting essential.
thanks the first thing worked. I went back and tried cupcake but am going back to rc33 might take a little while to reroot and everything. will stay with engineering bootloader though.
esnapz said:
Not sure if its a typo but you forgot the tar it should be
tar xf /sdcard/tether-1.6.tar
Hope that helps.
Click to expand...
Click to collapse
I wiped my phone also for rc33 and when i type everything it works in terminal BUT my macbook isnt detecting the G1 like it used too..
You only need to issue the above command only once to get the file setup and in the phone. After that you will need to type:
su (to get super user press enter)
tether start (this command will actually start the program)
tether stop (when you are done to stop the service and not completly kill your battery)
so again to try at first just type in command as follows:
$su
#tether start
#
if done correctly and would that is what you should see. If that does not fix try typing this into your phone and download the application for it. Haven't tried it myself but have heard it works.
www.tauruspc.net/tetherWifi.apk
Related
Here are some instructions for installing JesusFreke's modified recovery image. You have to install the modified recovery image before you can install modified firmwares. These instructions are simpler than the existing ones because they don't require the use of adb or telnet.
Firstly, you need to already have firmware version RC29 or RC7. To check which version you have go to "Settings" and then "About phone". At the bottom you will see a "Build number" which will include "RC" and then a number. If you have RC30 or RC8 then you need to downgrade. THAT WILL WIPE ALL THE DATA/APPLICATIONS ON YOUR PHONE. Instructions for downgrading are here.
Now that you have RC29/RC7:
Download 'AndroidMod.zip' from one of the links in JesusFreke's post
Extract 'recovery_testkeys.img' from that zip and copy it to your SD card.
Download 'install.zip' which is attached to this post below.
Extract 'install' from that zip and copy it to your SD card.
Put the SD card in the phone or disconnect the phone if it is attached by USB.
Reboot the phone (switch it off and then on again).
When it has finished booting type the following at the home screen. It will start searching your contacts, but don't worry about that. Also, you won't see any visible sign that the first command worked. Just go ahead and type the second command straight afterwards:
cd sdcard<press enter>
sh install<press enter>
After a moment your phone should reboot itself. To check that the flashing worked, switch off the phone and then hold down the home key while you switch it on again. Keep the home key held down until you see the recovery screen (with the "!" triangle and the picture of the phone). Then press Alt+L on the keyboard and if you see "Using test keys" on the second line of text then the modified recovery image is installed and you can now install a modified firmware.
Cool! Thanks for that... much simpler... anyone else tried this yet?
I'm going to attempt all this later.
Phil
i just tried it and it works. confirmed.
great for beginners!
Hey tried it and it works!! Now how about one on restoring data after backup.
thanks for this just tryed it and worked first time.
First off thanks for all information here. Am I correct that after I downgrade to rc29 I then follow the instructions in this thread and then I can install jf 1.3 rc30. Or do I have this all wrong?
gottifour said:
First off thanks for all information here. Am I correct that after I downgrade to rc29 I then follow the instructions in this thread and then I can install jf 1.3 rc30. Or do I have this all wrong?
Click to expand...
Click to collapse
you are correct. once you have the modded recovery image, you can use jfs update zips.
korndub said:
you are correct. once you have the modded recovery image, you can use jfs update zips.
Click to expand...
Click to collapse
Sweet! Thanks for the reply. I will attempt this real soon. Do you have any suggestions before I begin? After I modify the firmware I will not get ota updates anymore right? Lets say the cupcake update, or any other for that matter, does come out. I would just have to wait untill a smarter person then me converts it to a new modified image to flash to my phone? Is that right? Thanks for any help. I'm sure this is probably the worng place to ask all of these questions. d
gottifour said:
Sweet! Thanks for the reply. I will attempt this real soon. Do you have any suggestions before I begin? After I modify the firmware I will not get ota updates anymore right? Lets say the cupcake update, or any other for that matter, does come out. I would just have to wait untill a smarter person then me converts it to a new modified image to flash to my phone? Is that right? Thanks for any help. I'm sure this is probably the worng place to ask all of these questions. d
Click to expand...
Click to collapse
in one of the zips from JF is an app that will REsign any update.zip, so when an ota comes you just have to wait for the update.zip to show up then you could REsign it with the dev keys, pretty easy, but it will probably show up pretty fast now that almost every G1 is probably running that keyset.
bhang
UPDATE..
Its working now...I wasn't doing it in the telnet client. I was just typing it in randomly and it didnt work that way for some reason.
Ok. I have downgraded to rc29 and copied the two images two my sd card. but I'm not sure if I even have root. When I try to change directory it doesnt happen. I have to have root by installing the modified rc29 right? I did type telnetd at the home screen and pushed enter. nothing happened. I know I'm missing something just not sure what yet? I did install the telnet client from the market as well. I'm not understanding something it appears. Anyone?
gottifour said:
UPDATE..
Its working now...I wasn't doing it in the telnet client. I was just typing it in randomly and it didnt work that way for some reason.
Ok. I have downgraded to rc29 and copied the two images two my sd card. but I'm not sure if I even have root. When I try to change directory it doesnt happen. I have to have root by installing the modified rc29 right? I did type telnetd at the home screen and pushed enter. nothing happened. I know I'm missing something just not sure what yet? I did install the telnet client from the market as well. I'm not understanding something it appears. Anyone?
Click to expand...
Click to collapse
use the telnet client to telnet to localhost. *then* you will have root. (note: that's only applicable for RC29. to get root on JFv1.3, just type su in terminal emulator).
To know if you have root access, check the prompt you get. if you get #, then you have root access. if you get $, you don't have root access.
JJC1138 said:
Here are some instructions for installing JesusFreke's modified recovery image.
Click to expand...
Click to collapse
well this is a big help for many people thank you for your addition
JesusFreke said:
use the telnet client to telnet to localhost. *then* you will have root. (note: that's only applicable for RC29. to get root on JFv1.3, just type su in terminal emulator).
To know if you have root access, check the prompt you get. if you get #, then you have root access. if you get $, you don't have root access.
Click to expand...
Click to collapse
I got the #
Thanks so much for everything so far..This is really awesome!!
gottifour said:
UPDATE..
Its working now...I wasn't doing it in the telnet client. I was just typing it in randomly and it didnt work that way for some reason.
Click to expand...
Click to collapse
Hi there. I just wanted to clarify that if you're following the instructions I posted then you don't need telnet.
gottifour said:
Ok. I have downgraded to rc29 and copied the two images two my sd card. but I'm not sure if I even have root. When I try to change directory it doesnt happen. I have to have root by installing the modified rc29 right?
Click to expand...
Click to collapse
No, you don't need the modified RC29 to do this. After you type the "cd sdcard<enter>" command nothing visible should happen. It works because the bug in RC29 which we are exploiting executes everything you type on a hidden root console, so the cd command works, but it just doesn't show you anything. Then you enter the second "sh install<enter>" command and that runs a script that does all the good stuff and then reboots.
JJC1138 said:
Hi there. I just wanted to clarify that if you're following the instructions I posted then you don't need telnet.
No, you don't need the modified RC29 to do this. After you type the "cd sdcard<enter>" command nothing visible should happen. It works because the bug in RC29 which we are exploiting executes everything you type on a hidden root console, so the cd command works, but it just doesn't show you anything. Then you enter the second "sh install<enter>" command and that runs a script that does all the good stuff and then reboots.
Click to expand...
Click to collapse
Thanks for the reply and for simplifying this for everyone. I was confused at first but now I understand better. I have the modified RC30 working now with the dev boot loader as well. Oh and a new theme too. Thanks again!!!
JJC1138 said:
Hi there. I just wanted to clarify that if you're following the instructions I posted then you don't need telnet.
No, you don't need the modified RC29 to do this. After you type the "cd sdcard<enter>" command nothing visible should happen. It works because the bug in RC29 which we are exploiting executes everything you type on a hidden root console, so the cd command works, but it just doesn't show you anything. Then you enter the second "sh install<enter>" command and that runs a script that does all the good stuff and then reboots.
Click to expand...
Click to collapse
Correct, this is a really good idea! Instead of typeing telnetd to start it as root, you are typing in and running the script that will root your phone-- as root! I'll update my sticky post shortly.
worked for me now do i delete the install file, DREAIMG file and Recovery test keys files or do i have to keep em?
l0uisz said:
worked for me now do i delete the install file, DREAIMG file and Recovery test keys files or do i have to keep em?
Click to expand...
Click to collapse
You can delete them off your SD card after they're installed.
I will be accepting donations if you like my work. After contacting HTC, they informed me that my device is not under warranty, as a technician determined it to be "user related" damage and that all repairs will be at owner expense.
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=8141983
If you follow my twitter, you know I bricked my G1. I am trying to get it repaired, but due to the long response time I had to buy a mytouch (no point having two G1s IF the other one gets repaired). Using this bad luck to my advantage, I scripted a way for hero to run on both with two simple commands.
How I rooted a brand new "perfected SPL" MT3G and installed Hero in 15 min:
http://forum.xda-developers.com/show...&postcount=154
Link to original thread: http://forum.xda-developers.com/showthread.php?p=4365404#post4365404
Updated, but still feeling slow? Back up. Try rm system/sd/app_s then reboot to recovery and wipe data. then install fresh. Before restoring your data, open the backup folder on your sd card and remove the subfolders for programs you no longer have or need to have backed up.
I noticed a 10% increase in speed and my phone was far from lagging to begin with.
Losing messages? Make sure that system/sd/app/com.android.mms.apk does NOT exist, as this was an old release. Go into settings for messaging (from the conversation list panel) and set priority to "High"
Most Recent:
G1 / MT3G: http://twistedumbrella.slackdev.com/ZeroXd-6.0.zip
Now includes dynamic swap. Rewrote the method of apps to sd for myTouch.
Build will move system apps, user apps, and dalvik to sd on a g1 device.
Build will ONLY move user apps to the sd when using a myTouch.
This will allow the system apps and dalvik to remain on internal device.
This is a completely new method of doing a merge build so bear with me.
I am going to be rewriting things for users without a lot of user apps, like myself.
This will allow the entire build to be placed onto internal for mytouch users.
Once you have updated and are ready to use the phone, execute Terminal and enter the following commands:
su
magic
This configures the system to the specific device. This is until I finish automation.
LEDs have been restored to 93%
Bluetooth restored in MT3G
Porting my own boots for MT3G
Based on the System Image from Haykuro
Using the Kernel and Boot.img from JAC
Extensive system script edits were done
SwitchROM installs itself to system/sd/
LEDs are at about 90-100% brightness
CPU Optimization turned off by default
Enhanced Terminal included
Fixed My Account included
G1 / MT3G: http://twistedumbrella.slackdev.com/ZeroXd-5.2r5.zip
http://twistedumbrella.slackdev.com/Resources.zip
twistedumbrella said:
MultiTouch for MT3G being patched NOW
Click to expand...
Click to collapse
Does that mean multitouch doesn't work and one more unanswered questio IS it from the latest release that modaco did, i asked it since 5.0 so please answer
White Rosie doesn't work i tried it but i doesn't show up and it doesn't even install shows parse error, can you do something about that. Really appreciate your work. Will donate as soon i finish with my exams, I came to US for a holiday for 3 months and as i came back i have exams, only 3 left, have to finish 6 books per subject (thats f*****ng 3 months syllabus) and i have exams after 2 day holidays , thats why i have been a bit inactive in the community, will be active on 24 and will provide a special version of HERO based on my favourite ZEROXD.
Installed JACHeroSki 2.0 and i get stuck on a boot loop. i've tried wiping and re-flashing and same thing.
mgorman said:
Installed JACHeroSki 2.0 and i get stuck on a boot loop. i've tried wiping and re-flashing and same thing.
Click to expand...
Click to collapse
For me 2.0 working fine,but cannot install ZeroXd-5.2r4-installation aborted:/
In v2.0 cannot run wifi:/somebody else?
Had to fix scripts. Check the link on original thread for download. They are the same files. The verification fail happens when your downloading as I upload. It was a last minute fix on the way to work. Sorry for the issues.
hey twisted...great work on the roms...
couple issues with me...
auto-rotate doesn't work...
auto correct and dictionary doesn't work also...
is there any way we can correct this?
tq745 said:
hey twisted...great work on the roms...
couple issues with me...
auto-rotate doesn't work...
auto correct and dictionary doesn't work also...
is there any way we can correct this?
Click to expand...
Click to collapse
What device are you using? MyTouch? Did you run the terminal command?
BTW, for everyone else: http://twistedumbrella.slackdev.com/user.conf
Did some testing, seems to run a little smoother
tq745 said:
hey twisted...great work on the roms...
couple issues with me...
auto-rotate doesn't work...
auto correct and dictionary doesn't work also...
is there any way we can correct this?
Click to expand...
Click to collapse
Thank you... h.nocturna for the fix, and nacron for the heads up...
Here is the fix for auto-complete... Worked for me on 5.1r2
Everything in
open dos prompt.
adb remount
(***back up the original***)
adb pull /system/sd/app_s/HTC_IME.apk c:\(*your directory*)\HTC_IME.apk
(***install the new one***)
adb push c:\(*your directory*)\HTC_IME.apk /system/sd/app_s/HTC_IME.apk
start your Messaging it will crash the first time you want to use the keyboard... restart Messaging and it should work...
HTC_IME.apk here: http://www.mediafire.com/?te0symyx4yz
Mms auto-rotate works for me in 5.1r2 so I dont know. But possibly you still have the old Mms.apk. Try pushing the new one from 5.0 or later rom...
Twisted are you using BFS in your new builds??? Post 5.1 that is....
twistedumbrella said:
What device are you using? MyTouch? Did you run the terminal command?
BTW, for everyone else: http://twistedumbrella.slackdev.com/user.conf
Did some testing, seems to run a little smoother
Click to expand...
Click to collapse
so i opened up better terminal and when i entered su it says
/system/xbin/su: not found
help?
in the meantime i'll try zambesey's way
twistedumbrella said:
What device are you using? MyTouch? Did you run the terminal command?
BTW, for everyone else: http://twistedumbrella.slackdev.com/user.conf
Did some testing, seems to run a little smoother
Click to expand...
Click to collapse
so i opened up better terminal and when i entered su it says
/system/xbin/su: not found
help?
in the meantime i'll try zambezy's way
same issue as above :-(
1.8 is running pretty awesome.
i guess its safe to assume that i shouldn't try 2.0 yet? lol
zeroxd 5.2r4 seems to be faster than jacs 2.0 but i cant get auto rotate to work or multitouch and when i try the commands in first post i get "/system/xbin/su: not found''
did you try running the commands via adb ?
im not familiar with doing it that way i dnt even know wat adb is
just connect your phone to the pc
install the drivers from android SDK
start > run > cmd
cd to the android tools directory
and adb shell
that's how i did with my phone and works perfectly
im not gona risk any damage ill deal without the rotate for a day till its fixed
tq745 said:
so i opened up better terminal and when i entered su it says
/system/xbin/su: not found
help?
in the meantime i'll try zambezy's way
Click to expand...
Click to collapse
should be under /system/bin not xbin
Hello,
This is a dead easy fix to get tethering working completely with android-wifi-tether (http://code.google.com/p/android-wifi-tether/):
UPDATE
New development version has support for this rolled in, instructions are no longer necessary:
http://code.google.com/p/android-wi...name=wireless_tether_2_0_2-pre14.apk&can=2&q=
Steps:
1. Open adb shell (start cmd.exe, run "adb shell")
2. Issue the following commands:
- "mkdir /sdcard/android.tether"
- "cat /etc/firmware/fw_bcm4329_ap.bin > /sdcard/android.tether/fw_bcm4329.bin"
3. Download and install the android-wifi-tether application, start tethering.
Your log from android-wifi-tether should look like the attached image.
Happy configuration free tethering!
NOTE: This works because of the two separate firmwares that HTC has included in /etc/firmware. One is specific for AP-mode and must be more open to this kind of stuff. The original bug stemmed from the usual firmware dropping ARP requests pretty consistently, possibly as a powersaving measure.
The second firmware is loaded using the firmware_path option when loading the bcm4329.ko kernel module.
anyone else confirm this working please.
I confirm this working...
You will need to have root to run the app of course but 2 or 3 people have confirmed it on bug 362 already on the google project.
Not working for me
AWESOME!!!
actually i ever use wifi tether but this is pretty cool because it actually worked. i know on the heroC we had issues with wifi tether all of a sudden not wrking after 2.1. nice to see that its been fixed. good work spreading the word
ya. it will get SU permissions,
i can find the connection.
i connect to it. but no data transmitting.
would be cool if someone can confirm 4g is able to be tethered.
fdot said:
ya. it will get SU permissions,
i can find the connection.
i connect to it. but no data transmitting.
Click to expand...
Click to collapse
same here. any ideas?
toastcfh said:
would be cool if someone can confirm 4g is able to be tethered.
Click to expand...
Click to collapse
Not confirming but based on what I read harry_m stated the wifi tether app uses the current connection, so in theory if you switch between 3g and 4g the app will switch accordingly.
i can confirm
I originally flashed with toast's rom. Used the recovery .bat to install Flipz's stock root rom.
I then flashed toast's radio rom.
wifi tether did NOT work.
I then performed the above instructions, and viola, it works fine. (i am posting via wifi tether)
I want to thank everyone who is hard at work on these projects, you guys are awesome.
fdot said:
ya. it will get SU permissions,
i can find the connection.
i connect to it. but no data transmitting.
Click to expand...
Click to collapse
Check that the log screen looks exactly like mine does. Did you get any errors when you issued the adb commands?
Look on your sdcard for the android.tether folder and see if fw_bcm4329.bin file exists there.
toastcfh said:
would be cool if someone can confirm 4g is able to be tethered.
Click to expand...
Click to collapse
dcmtnbkr said:
same here. any ideas?
Click to expand...
Click to collapse
It should work according to one of the comments given about the issue. http://code.google.com/p/android-wifi-tether/issues/detail?id=362#c36
Because I am weary of rooting my phone not being able to return it to stock, I am gonna try it with the unrevoked root first.
goodfellaslxa said:
I originally flashed with toast's rom. Used the recovery .bat to install Flipz's stock root rom.
I then flashed toast's radio rom.
wifi tether did NOT work.
I then performed the above instructions, and viola, it works fine. (i am posting via wifi tether)
I want to thank everyone who is hard at work on these projects, you guys are awesome.
Click to expand...
Click to collapse
i followed this same exactly.
andrew500 said:
Check that the log screen looks exactly like mine does. Did you get any errors when you issued the adb commands?
Look on your sdcard for the android.tether folder and see if fw_bcm4329.bin file exists there.
Click to expand...
Click to collapse
no errors in adb.
and the .bin file is sitting in the directory.
and the log looks like yours.
running toasts ROM
can't get this to work
followed instructions, and when i click on the tether button it instantly says: unable to start tethering, please try again!
log screen is completely blank
any ideas?
fdot said:
i followed this same exactly.
no errors in adb.
and the .bin file is sitting in the directory.
Click to expand...
Click to collapse
I meant the screen in android-wifi-tether, does it look like the screen cap I included? It should have a debug line about the loaded firmware on the first item.
- Didn't see the edit you made with that screen:
Have you done the OTA update? Could be the SD card bug possibly. The log screen shows it didn't load the external firmware.
"Unable to start teterhing try again"
I skimmed this thread, I am using toast's rom.
I have just applied the Unrevoked root. I cannot access the sdcard via adb shell. Any ideas?
When i send command
"cat /etc/firmware/fw_bcm4329_ap.bin > /sdcard/android.tether/fw_bcm4329.bin"
it gives me error msg
"cannot creat /sdcard/android.tether/fw_bcm4329.bin: directory nonexistent"
i followed this same exactly.
no errors in adb.
and the .bin file is sitting in the directory.
Click to expand...
Click to collapse
I meant the screen in android-wifi-tether, does it look like the screen cap I included? It should have a debug line about the loaded firmware on the first item.
- Didn't see the edit you made with that screen:
Have you done the OTA update? Could be the SD card bug possibly. The log screen shows it didn't load the external firmware.
Click to expand...
Click to collapse
I have not done the ota.
-------------------------------------
Sent via the XDA Tapatalk App
THIS IS FOR ECLAIR 2.1 DO NOT USE THIS IN A FROYO 2.2 ROM. SINCE THE 2.2 UPDATE WIRELESS N IS SUPPORTED OUT THE BOX. NO NEED FOR THIS HACK IN FROYO 2.2
edited by toastcfh to avoid mishaps
Update: Thanks to Calkulin there are now flashable zips on my blog post as well as just the driver. Just flash them like any other update.zip file.
So the Evo's WiFi chip supports Wireless N technology, which allows for faster throughput on your WiFi connection. To use this you obviously need a Wireless N capable AP or router. Basically, for some reason (I am going to assume battery life?), HTC decided to disable the wireless n capability of this chip but this can be fixed. Since we don't have the source for the driver we need to use a hex editor. Note, if using AOSP wireless n will already be enabled using the AOSP driver. But if you are using a Sense rom then you will need to do the following. Also I am including a download link with the driver that you can just push if you don't want to get dirty with a hex editor. Anyway, here we go:
1. Download a hex editor (I just googled hex editor and downloaded this one: http://www.chmaas.handshake.de/delphi/freeware/xvi32/xvi32.htm)
2. Go into a command prompt or shell and perform:
Code:
adb pull /system/lib/modules/bcm4329.ko ./bcm4329.ko.old
adb pull /system/lib/modules/bcm4329.ko ./bcm4329.ko
This will pull the file and make a backup in case you need to replace the backup.
3. In your hex editor open the file you just pulled. Now, in two spots HTC added 'nmode' in here to disable Wireless N. All we have to do is modify this string to be any other 5 character string and wireless N will be enabled. I did a search and replace and replaced 'nmode' with '-----' (Note: Do not include the single quotes).
4. Save the file.
5. Perform the following in a command prompt or shell:
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
adb push bcm4329.ko /system/lib/modules/bcm4329.ko
Now wireless N should be enabled on your device. If not, restart it and try. If you ever want to restore your original just perform the following:
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
adb push bcm4329.ko.old /system/lib/modules/bcm4329.ko
.
Below is the download link for the already modified wireless driver.
http://objectunoriented.com/android/?p=35
I downloaded the file and pushed it to my phone. I restarted the phone and once it came back up it connected on 802.11n. So far been working perfectly.
Sounds good, will try when I get home. But I have to say I was expecting this after I heard that the incredible is getting a patch to enable wireless n.
wow. clever little patch. im excited to try this! hopefully will at least allow better throughput if not also better signal with wireless n! thanks!!
on a technical side note, any reason why your /system is mtdblock3 while mine is mtdblock4?
cant wait to try this.... thanks
good stuff! gonna try this.
joeykrim said:
wow. clever little patch. im excited to try this! hopefully will at least allow better throughput if not also better signal with wireless n! thanks!!
on a technical side note, any reason why your /system is mtdblock3 while mine is mtdblock4?
Click to expand...
Click to collapse
That's just the command I used when I mounted the system directory as writeable when I had my Hero. Should it be 4 instead of 3?
liquidhaste said:
Sounds good, will try when I get home. But I have to say I was expecting this after I heard that the incredible is getting a patch to enable wireless n.
Click to expand...
Click to collapse
I have actually had this working for maybe a week now in my latest Superersonic rom but since I haven't had time to fix the root problem with that rom I just decided to post this seperately.
most of the power issues/concerns with wireless-n are targetted at the AP/Router i think... wondering if anyone has been seeing a drop in battery power though.
poporo said:
most of the power issues/concerns with wireless-n are targetted at the AP/Router i think... wondering if anyone has been seeing a drop in battery power though.
Click to expand...
Click to collapse
That was just an assumption. I had nothing to back that up lol
Here is the mod in zip format to make it easier, restore is also attached
Calkulin said:
Here is the mod in zip format to make it easier, restore is also attached
Click to expand...
Click to collapse
Hey thanks for doing this for me. I completely forgot to do this lol
Updated blog post with these update zips btw. Thanks again.
Probably a dumb question but im guessing since you have provided us with a zip file we can just flash it now??? And even dumber question this will still work with wireless g routers right?
awesome bro. Thanks.
rustyman14 said:
Probably a dumb question but im guessing since you have provided us with a zip file we can just flash it now??? And even dumber question this will still work with wireless g routers right?
Click to expand...
Click to collapse
Correct. Thanks to Calkulin you can now use the zips he provided (downloadable here or on my blog post) to flash instead of using adb.
And yes this will still work with a/b/g routers.
chuckhriczko said:
That's just the command I used when I mounted the system directory as writeable when I had my Hero. Should it be 4 instead of 3?
Click to expand...
Click to collapse
never used the hero, but this makes sense. on the EVO, pretty sure its mtdblock4.
would you be okay if i add this to the update.zip builder im putting together with credit going to you and a link to this thread?
joeykrim said:
never used the hero, but this makes sense. on the EVO, pretty sure its mtdblock4.
would you be okay if i add this to the update.zip builder im putting together with credit going to you and a link to this thread?
Click to expand...
Click to collapse
No problem bro. I'd be honored. My work is your work. Anything any of us do on here should be freely used by anyone else assuming proper credit is given.
Should have brought my laptop to work today, oh well will give it a go tonight. Can't wait!
jwhitney83 said:
Should have brought my laptop to work today, oh well will give it a go tonight. Can't wait!
Click to expand...
Click to collapse
You can download the files through your phone's browser and flash through that as long as you NAND unlocked everything. Just make sure you copy Calkulin's update.zip files to the root of the sd card after downloading.
Calkulin said:
Here is the mod in zip format to make it easier, restore is also attached
Click to expand...
Click to collapse
You are freakin awesome!
I have a WiFi only Xoom and it is unlocked/rooted.
I decided to use the hack on the stock browser which enables fulltime desktop mode. I downloaded the apk, renamed it to framework-res.apk and dropped in system/framework and overwrote the existing file. I dl the file from http://forum.androidcentral.com/xoom-rooting-roms-hacks/75616-full-browser.html
I've since discovered that had I read further into the thread, I would have known not to use the file on a WiFi Xoom.
The gist of my problem is I have managed to finally get the Xoom to boot to the homescreen but It's force close city. As soon as I force close one app, others come up (FC) too. The one FC that will not go away is Launcher. it will FC loop forever. The Google/Mic in the top left corner is missing but the bottom bar has the normal icons, but I can't use them because I am stuck in a FC loop. I also get stuck/locked up while rebooting using the power button and volume down and have to use the power/volume up to restart.
I'm wondering if I use the the same one click root file (with kernel) that I still have and root again if this may fix the issue?
Perhaps their may be an easier method if I am only missing the one (framework-res.apk) file I overwrote?
Any help would be most appreciated.
You wanted a new theme right?
http://forum.xda-developers.com/showthread.php?t=1015434
This theme has the framework you are looking for.
Or.. this is the original Wifi Xoom system dump. It may be in there. (I'm at work so i cant check myself)
http://forum.xda-developers.com/showthread.php?t=1011484
Just got home and read your post and do appreciate it.
I was going to begin but just discovered that my Xoom will no longer mount on my pc. Not sure what to do....
yooper said:
I have a WiFi only Xoom and it is unlocked/rooted.
I decided to use the hack on the stock browser which enables fulltime desktop mode. I downloaded the apk, renamed it to framework-res.apk and dropped in system/framework and overwrote the existing file. I dl the file from
I've since discovered that had I read further into the thread, I would have known not to use the file on a WiFi Xoom.
The gist of my problem is I have managed to finally get the Xoom to boot to the homescreen but It's force close city. As soon as I force close one app, others come up (FC) too. The one FC that will not go away is Launcher. it will FC loop forever. The Google/Mic in the top left corner is missing but the bottom bar has the normal icons, but I can't use them because I am stuck in a FC loop. I also get stuck/locked up while rebooting using the power button and volume down and have to use the power/volume up to restart.
I'm wondering if I use the the same one click root file (with kernel) that I still have and root again if this may fix the issue?
Perhaps their may be an easier method if I am only missing the one (framework-res.apk) file I overwrote?
Any help would be most appreciated.
Click to expand...
Click to collapse
I did the same thing my friend, twice in fact. Actually it was likely my post you are referencing above Second time around I still had USB debugging turned on so I didn't have to reload the images.
Do you have the original .apk backed up? If not, i'm attaching it. What I did to fix this was using the adb shell, I remounted the file system as rw and adb pushed the original .apk. You're good to go after that. Hope you have your USB Debugging still turned on
Hope this helps.
yooper said:
Just got home and read your post and do appreciate it.
I was going to begin but just discovered that my Xoom will no longer mount on my pc. Not sure what to do....
Click to expand...
Click to collapse
Are you stuck at the dual core screen? If so can you get into fastboot? You would have to flash the system and boot .img I believe. This is what I had to do when i bricked my wifi without having the USB Debugging turned on. Don't lose hope, you likely do not have a $600 paperweight on your hands.
joen1ce,
I cant thank you enough for your help and time as well as uploading the file for me. Thank you.
I do have dubugging turned on and can boot to the home screen. Actually I have gotten a bit further. I found that if I hit "ok" and force close and quickly continued to hit the time on the lower right corner, I could eventually get into the setting menu. Takes a lot of "tapping" to get it to work, but it did. I am able to get into the reset option but it simply wont work. I push the button and nothing happens. I even tried using bluetooth via my Fascinate and Xoom to see what I could do with the apk you uploaded within the xoom since I could get into the bluetooth downloads, but no worky.
Upon startup, I find that I can get into "Starting fastboot protocol support" as well as well as RSD - Fastboot and NvFlash. Although, I still cant get the Xoom to talk with the computer. I have a Mac with Windows installed and have neither will communicate with the Xoom.
I'm not overly savy with ADB and am not sure if I would know what to do with a boot.img nor where to put it let alone the commands needed to make it work with no communication between devices.
I do have SDK/ADB and the Fastboot (.exe) both on the Mac and Windows side.
I can do an exchange on the Xoom but would rather fix it myself and consider it a valuable learning experience, but I'm at my wit's end.
yooper said:
joen1ce,
I cant thank you enough for your help and time as well as uploading the file for me. Thank you.
I do have dubugging turned on and can boot to the home screen. Actually I have gotten a bit further. I found that if I hit "ok" and force close and quickly continued to hit the time on the lower right corner, I could eventually get into the setting menu. Takes a lot of "tapping" to get it to work, but it did. I am able to get into the reset option but it simply wont work. I push the button and nothing happens. I even tried using bluetooth via my Fascinate and Xoom to see what I could do with the apk you uploaded within the xoom since I could get into the bluetooth downloads, but no worky.
Upon startup, I find that I can get into "Starting fastboot protocol support" as well as well as RSD - Fastboot and NvFlash. Although, I still cant get the Xoom to talk with the computer. I have a Mac with Windows installed and have neither will communicate with the Xoom.
I'm not overly savy with ADB and am not sure if I would know what to do with a boot.img nor where to put it let alone the commands needed to make it work with no communication between devices.
I do have SDK/ADB and the Fastboot (.exe) both on the Mac and Windows side.
I can do an exchange on the Xoom but would rather fix it myself and consider it a valuable learning experience, but I'm at my wit's end.
Click to expand...
Click to collapse
Copy the apk file I uploaded to the directory where you have the adb files. Go to the command line and switch to that same directory.
Let the device reboot to the point where you get those damn force close messages.
at the command line type:
adb devices
you should see your device listed there. If so, do the following:
adb shell
mount
You should see all the mounts on your device listed. Copy the path for system you will need it for this next part. It may be exactly like mine. So next you will type in:
mount -o rw,remount /dev/block/platform/sdhci-tegra.3/by-name/system /system
the "/dev/block/platform/sdhci-tegra.3/by-name/system" above is the true path
to my /system mount. Use whatever the path yours is mounted to from the previous command.
Next hit ctrl + c to exit out of the shell and at the command line type this:
adb push framework-res.apk /system/framework/framework-res.apk
If the above was successful you should be able to reboot the device and be back in business.
You fixed it!!
joen1ce, I can't begin to thank you enough for your help Took me a couple tries as well as rebooting the Xoom for it to take but by god it worked!!!
I'm sure your post will help others out out in future too. As the WiFi Xoom becomes more popular, I'm sure this will happen again to more people looking to modify their Xoom stock browser to desktop mode.
I'm thinking their should be a sticky on bricking with possible fixes and your post should be noted for sure.
People like you really help make this site the cat's a**.
Thanks again,
Mark
yooper said:
joen1ce, I can't begin to thank you enough for your help Took me a couple tries as well as rebooting the Xoom for it to take but by god it worked!!!
I'm sure your post will help others out out in future too. As the WiFi Xoom becomes more popular, I'm sure this will happen again to more people looking to modify their Xoom stock browser to desktop mode.
I'm thinking their should be a sticky on bricking with possible fixes and your post should be noted for sure.
People like you really help make this site the cat's a**.
Thanks again,
Mark
Click to expand...
Click to collapse
No problem, glad I could help. I bricked my Xoom basically within an hour of buying it and I know how it feels, especially when trying to be moral and not return it! Had it about a week now and it's my first Android device so I'm new to these forums. But the helpfulness of the community is very impressive indeed.
Regards,
Joe
joen1ce said:
Are you stuck at the dual core screen? If so can you get into fastboot? You would have to flash the system and boot .img I believe. This is what I had to do when i bricked my wifi without having the USB Debugging turned on. Don't lose hope, you likely do not have a $600 paperweight on your hands.
Click to expand...
Click to collapse
joen1ce. Could you please help? I am stuck at the Dual Core Screen and cannot get my computer to recognize my device in adb. I am trying to return to stock 3.2.1.