Rogers Dream Slow Mobile Data Need Your help - G1 Q&A, Help & Troubleshooting

Hello i have a Rogers dream rooted. I used speedtest.net application here are my last 10 test result in kbps...
I have a clue can it be that is lsow my connection because it always roaming?
D/U
202/1553
5/1531
2/1605
24/1697
235/533
3/7
8/-0
561/1664
19/1806
Note:those numbers are not backward!
you get the picture the download speed is very very bad upload is good.
i tryed many differents roms and kernel mix.
here is my setup for those test above
radio: 3.22.26.17
spl: dangerspl
recovery: RA-dream-v1.7.0R
rom: MT3G-test2_S + MT3G-test2-market-fix_S
kernel: ez-BiffTest2Kern_ebi1_S
i dont know how can i fix my trouble i use this phone on telus network ans tested my sim in a telus htc desire and speed is fantastic!
if you have any idea to fix my trouble it would be very very appreciated since i need some internet for my work and if i cant fic it i need a new phone and its not a good option for me now!
thank for your help.

Look up ro.rill settings, the ota being a T-Mobile stock Tom is not optimized to other networks.
But you can from recovery modify your ro.ril settings to speed things up..
(Or copy the out of the desires build.prop)

thx for the info i will try the file from my firend desire he is on telus. i edited mine but im not sure if it worked yet!

pr0cess0r said:
thx for the info i will try the file from my firend desire he is on telus. i edited mine but im not sure if it worked yet!
Click to expand...
Click to collapse
You just want the ril settings, since the rest will impact the operation of the rom. Also not all settings will work so keep a backup.
Also in other threads it's noted it may take a few restarts for it to work.

Im not able to write to system i tryed some guide in terminal and one apllication from the marking but im notable to copy prop.buil to system.

Boot into recovery, atatch your USB wire and run the following adb comands from your computer:
To pull build.prop to your computer:
Code:
adb shell mount /system
adb pull /system/build.prop build.prop
Edit the file
Then to push back:
Code:
adb push build.prop /tmp/build.prop
adb shell dos2unix /tmp/build.prop
adb shell cat /tmp/build.prop /system/build.prop
adb shell sync
adb shell um
adb shell reboot

I finally managed to change the setting from 10 to 12 and its faster but not like the desire. i get 1000 kbps somes times and upload is still faster. Thx for the help whit this !! im still wondering if roaming can make the connection slower.

pr0cess0r said:
I finally managed to change the setting from 10 to 12 and its faster but not like the desire. i get 1000 kbps somes times and upload is still faster. Thx for the help whit this !! im still wondering if roaming can make the connection slower.
Click to expand...
Click to collapse
You have a telus sim on the telus network correct? [That combo is not roaming]
There are many factors in network speed. Personally for most things I use phone data for latency is more of a problem than speed.
One other note: if you are no longer with rogers you might try changing 3.22.26.17 -> 3.22.20.17 by fastboot. (not sure it will help speed but is know to solve some other gotchas without impacting the current rom)

do i need to flash a new recovery at the same time?

pr0cess0r said:
do i need to flash a new recovery at the same time?
Click to expand...
Click to collapse
No .. if you are just going between 3.22.* radios using fastboot to flash:
The current system (including recovery, boot, system, and userdata) ought to work without any modification..
In case of problems however: so long as you flash the radio via fastboot [AND NOT recovery] you can use fastboot to restore a -R recovery and wipe the rest of the system if something goes wrong.

ezterry said:
No .. if you are just going between 3.22.* radios using fastboot to flash:
The current system (including recovery, boot, system, and userdata) ought to work without any modification..
In case of problems however: so long as you flash the radio via fastboot [AND NOT recovery] you can use fastboot to restore a -R recovery and wipe the rest of the system if something goes wrong.
Click to expand...
Click to collapse
ok i flashed this older radio but i think froyo rom wont work whit it im not 100% sure about this.

i got good spped then checked 2g only by mistake and whas not able to change it back i wiped and now im not able to get good speed again

Finally i got some speed one of my trouble is that i cant test iut at home the signal is bad just here.I listened to internet radio for 100 KM today whit no trouble.Little cut when i whas changing tower i think!

Related

superuser help?

im having some serious issues with my SU.
i tried temporizer's fix with no help.
it started a while ago when i flashed a theme and i could never get it back.
Ive tried EVERYTHING (to my knowledge which is definitely not vast lol) to no avail. and from what temp and a couple others have told me its a problem with cyan recovery 1.3, but now i cant flash to 1.4. im stuck with no SU, no way to flash a new recovery and pretty much half ass phone. ive never had this type of problem since i rooted back in januaryish. any help would be much appreciated.
anon1ski said:
im having some serious issues with my SU.
i tried temporizer's fix with no help.
it started a while ago when i flashed a theme and i could never get it back.
Ive tried EVERYTHING (to my knowledge which is definitely not vast lol) to no avail. and from what temp and a couple others have told me its a problem with cyan recovery 1.3, but now i cant flash to 1.4. im stuck with no SU, no way to flash a new recovery and pretty much half ass phone. ive never had this type of problem since i rooted back in januaryish. any help would be much appreciated.
Click to expand...
Click to collapse
Download cyan's recovery 1.4 to your sdk tools folder, start the phone in fastboot mode [back+power] folder and run:
Code:
fastboot boot cm-recovery-1.4.img
That should boot the recovery image and you can work from there to reflash whatever you want.
sdk tools folder? and that would beeeeeeee?
apparently im not as savvy as i once thought..... lol
anon1ski said:
sdk tools folder? and that would beeeeeeee?
apparently im not as savvy as i once thought..... lol
Click to expand...
Click to collapse
Errr... you don't have the sdk?
You don't use adb...?!
That's like trying to play football with no limbs..
Get yourself rigged up with this:
http://developer.android.com/sdk/1.5_r3/installing.html
btw.. you won't need to set up eclipse or the adt plugin for this, just make sure your environment variables and java paths are set up as per the guide.
well while football WITH limbs does sound much less entertaining, i am normally no where near a computer, and do almost everything right from my phone.... and i mean everything..... i download all my roms, themes, etc. right to my download folder, find em', rename em' flash em' and im good to go. i went on a computer to get the recovery simply because it downloads wrong on my phone and saves as a text file, seems like it does the same on mozilla for some people but i got it in .img form and its on the root of my card, and nothing.
anon1ski said:
well while football WITH limbs does sound much less entertaining, i am normally no where near a computer, and do almost everything right from my phone.... and i mean everything..... i download all my roms, themes, etc. right to my download folder, find em', rename em' flash em' and im good to go. i went on a computer to get the recovery simply because it downloads wrong on my phone and saves as a text file, seems like it does the same on mozilla for some people but i got it in .img form and its on the root of my card, and nothing.
Click to expand...
Click to collapse
I do a lot of stuff from my phone too tbh, Somehow it satisfies my geek cravings more fully.. But adb is massively useful when you're on the pc.. saves a lot of cramped typing on the device keyboard.
Fastboot will be your saviour in this case though, and you're gonna need a proper box to run that on.
i have NO idea what im doing with adb, i just downloaded it and im just starign at my screen like it tried to feed me a cheeseburger.....
anon1ski said:
i have NO idea what im doing with adb, i just downloaded it and im just starign at my screen like it tried to feed me a cheeseburger.....
Click to expand...
Click to collapse
lol.. adb is pretty simple.. a few examples:
Code:
adb push localpath devicepath # push files to your phone eg: adb push c:\update.zip /sdcard
adb pull devicepath localpath # pull files from device
adb shell # basically a terminal running on your device that you control from your pc.. im sure you can figure this out if you do everything from your phone.
adb shell reboot # guess?
adb shell reboot recovery # go straight to recovery without holding any buttons
fastboot should be in the same folder as adb.. you can use it to flash .img files from the pc or just boot the images without flashing them.
how do i run fastboot, adb, etc. in relation to them running processes on my phone.
i downloaded everything. i just dont know how to run it or if i have to run a couple things, have my phone in recovery or fastboot(im guessing).
god. i feel like a moron.
anon1ski said:
how do i run fastboot, adb, etc. in relation to them running processes on my phone.
i downloaded everything. i just dont know how to run it or if i have to run a couple things, have my phone in recovery or fastboot(im guessing).
god. i feel like a moron.
Click to expand...
Click to collapse
Assuming you're on windows, you'll have to install the adb driver first (not the standard android that windows installs automatically, theres a seperate driver in the usb_driver folder of the sdk). You also need to enable usb debugging on your phone.
Follow this guide if you need to:
http://forum.xda-developers.com/showthread.php?t=532719
You can use adb whatever mode your phone is in.. even when its stuck in a bootloop usually. You don't need to be running anything on the phone, the drivers are switched on by init.rc.
Fastboot can only be run with the phone in fastboot mode (surpisingly).
thanka alot man. im gonna give this all a try.
Good luck
ok. got adb running. ran the command you gave me. it brings up 1.4 but doesnt push it to my phone...... can i actually INSTALL 1.4 from fastboot/adb?
nevermind. figured it out. used common sense and just ran fastboot flash recovery recovery.img and it worked. thanks for everything
my super user still wont work.; so apparently it had nothing to do with the recovery..... im going to wipe, reflash cyan 3.9.1. and see if that works.

[Newbie Guide] adb/fastboot/bootloader/android 101

The purpose of this document is to clarify a few basics about HTC Android Phones and basic commands to interface with the phones. Think of this as a beginner's guides to the Android device from a non-traditional user's point of view. I'll keep it simple and plain as much as I can for the new users. I'll also try to keep all the technical aspects true as much as I can while keeping it simple.
Before you go on, please read this and understand the basic concepts and how and why following commands are being used. Do not follow anyone's instructions/tutorials/guides without prior basic understanding of what each command do. I do want to believe it's humans visiting this forum and not lemmings. If you do not understand, feel free to ask here. I will or someone else also knowledgeable will answer your questions. DO NOT QUOTE THIS AS A WHOLE. My pet peeves and a complete waste of screen space.
Sometime, depending on your OS, command names may change (e.g: mouse / mouse.exe / mouse-linux / mouse-mac). For general purpose, we'll use mouse instead of an OS specific commands in this instructions.
So to repeat myself, if you understood the concepts of the commands, and you are on a linux system and someone's guide says touch index.php, you will automatically type touch-linux or whatever the name of your executable is on your system.
​
We shall assume you know how to install needed drivers and where to get android sdk and put the sdk binaries (executables) in the system path. If we need to expend this let me know and I'll expend this here.
Further, if I get any parts wrong, PM me and I'll get those parts corrected.
Android Partition, SPL etc.
Partitions:
Followings are a list of partitions on your android phone.
misc - misc partition -
recovery - Recovery Partition - This is where the original HTC recovery or Amon Ra's recovery or any other Recovery would go. Basically if you reboot into recovery it'll boot from here.
boot - This is your boot partition
system - This is where all your system information (ROM resides)
cache - cache (When you factory reset the phone, this area is wiped)
userdata - user data (like your login, your user settings etc) When you factory reset the phone, this area is wiped)
So, if you replace the recovery image, you are pretty much set for updates provided here at XDA. Note: By replacing your recovery image, you may not be able to have OTA updates.
ROM images will normally replace boot and system images at the same time and often time, userdata and cache too; reseting the phone completely.
SPL/Bootloader/Radio/Bricking Phones:
SPL / Bootloader is like BIOS on a computer. At least I think of it that way. SPL can be updated! SPL comes as either Security-On of Security-Off (S-ON/S-OFF).
Note: It is my understanding that radio will boot first, followed by other systems. So it is IMPORTANT that your radio image/version will work with your SPL image/version. This is the one and only reason for phones being bricked. You can not brick your phone by flashing a ROM or Boot image or recovery image. Once you flash the wrong radio for the SPL, the only known method of recovery is to send the phone back into HTC for repair.
How do I know the phone is bricked? A bricked phone can not boot into bootloader, recovery, or into normal operation modes. You can not connect to a bricked phone via adb or fastboot. You can only see one screen on the phone and it will be the first splash screen.
Commands:
adb - Android Debug Bridge - One of the two things you'll need to know if you ever want to do anything non-conventional on your android based phone.
List of commands that can be used by adb can be prompted by typing adb at the system shell (command prompt or terminal)
Notable adb commands:
adb devices - If you don't know anything, this is the ONE thing you have to know.
adb devices will give you a list of devices connected to the computer. This is also a good way to make sure that your phone is actually connected to the computer.
adb reboot (bootloader|recovery)
adb reboot - this will reboot your phone normally.
adb reboot bootloader - this will reboot your phone back into the bootloader (white screen with the android on wheels)
adb reboot recovery - this will reboot your phone back into recovery console (either default or amon_ra's recovery).
adb shell - this will shell into the phone and you can now explore the phone. Remember phone's native backend os is linux so know your linux commands.
adb remount - remounts the system partition on the phone so you can you read/write to it.
adb push xxx yyy - will push xxx file from computer into yyy location/file on phone (needs rooted access)
adb pull xxx yyy - will pull xxx file from phone into yyy location/file on computer (needs rooted access)
Fastboot is protocol used to update the flash filesystem in Android devices from a host over USB. It allows flashing of unsigned partition images.
Notable fastboot commands:
fastboot devices - If you don't know anything, this is the ONE thing you have to know.
fastboot devices will give you a list of devices connected to the computer. This is also a good way to make sure that your phone is actually connected to the computer.
fastboot reboot - this will reboot your phone normally
fastboot oem unlock - this will unlock your bootloader - NOTE THIS WILL VOID YOUR NEXUS ONE WARRANTY
fastboot erase XXX - Will erase the partition XXX (such as userdata, cache) - mainly used for resetting phone and clearing userdata / factory settings.
fastboot flash XXX YYY - This will flash XXX partitionn with YYY image.
e.g: fastboot flash system system_update.img will flash/update your system partition with an image called system_update
If anyone needs me to dig deep into using anything else, please PM me. I'll add it on here. Hopefully this will help all newbies about the basic commands and what they do.
FAQs (UPDATED Feb 09, 2010)
Q: One question about the Android SDK. Do I need it to flash my N1 or just to program new apps? Where can I get it?
A: Android SDK is not entirely needed to flash the N1. However, there are tools in there that you need. Adb / Fastboot etc. Although they can be downloaded by themselves, the windows version of the SDK also have the Drivers that are needed for android devices for USB connection. So, it is recommended to get it. You can get it from developer.android.com
Q:I have never experienced anything like this when I did a hard-spl on my winmo phone. Radio versions are included with SPL's, right?
A: Official packages from HTC did come with nbh packaging, meaning it is a all in one upgrader that will update Radio, ROM, System etc, it is very much common for active development area here at XDA to get the radio or SPL or ROM separately and independently of one another. And as such, you will most likely flash them seperately (who wants to wait 6-8 months). Also, since this phone is released by google, HTC will most likely not update any major Radios. However, it is very likely that we will be hacking in Radio updates or any other "updates" from HTC from their new device - HTC Bravo.
Q: Is there a guide for snow leopard? I'm kind of stuck.
A: I personally ran android SDK and aforementioned executable on both MAC OS 10.5 and 10.6. Like I posted, the commands and the executable names may be slightly different. I may call adb and you may find it as adb-mac. I am not going to write 3 separate documents for 3 separate OSes. You have to know that adb=adb-mac (on your mac), adb-linux (for linux) etc. And yes the above guide will work universally.
Q: Can i replace the splash image..?? (unlocking related)
A: As of the above date (next to the FAQ) no you can not. Issue is probably a few folds. One of them is that splash1.img is not going in due to security lock. Remember, you unlocked the phone. HTC will not like it. Anyhow, I like the current quad color X. If you are thinking of getting rid of the lock logo, good luck. Even if you can get rid of it, you will still have to overcome the pink text that says ***UNLOCKED*** on your bootloader.
Q: Can you run Windows Mobile on Android Phones?
A: With enough resources given, sure. Will it ever happen? No. Why? Windows mobile compiler and builder cost $. As a matter of fact, as of version 5, it was going to cost me $75 per device. That's one of the reasons why handset makers went to Android open platform. Android is free and universal so as long as you use certain chipsets and certain items, you are good to go. Can it ever be ported? Sure. With right amount of time and money anything can be done. But at this point, it's cheaper for you to go buy a windows mobile smartphone.
Q: How do I know the phone is bricked?
A: You can not brick a phone unless you are flashing Radio/SPL packages. Make sure if you are doing that, you follow directions VERY CAREFULLY. A bricked phone can not boot into bootloader, recovery, or into normal operation modes. You can not connect to a bricked phone via adb or fastboot. You can only see one screen on the phone and it will be the first splash screen.
Q: I have installed the Android SDK however, i cannot seem to get the laptop to detect the nexus. What have i left out?
A: Most common item that people forget to enable is USB Debugging. Settings => Applications => Development => USB debugging [checked]
Q: I have rooted n1. when I go to recovery to do backup, I get the triangle with the little green android guy, but phone is stuck there. I have to remove battery to reboot phone. What have I done wrong?
A: You still have the stock (shipping) recovery. If you want a different recovery (Amon RA's), download it, the from fastboot, run fastboot flash recovery downloaded_recovery.img
Q: Which step of the rooting / recovery procedure does it give root?
A: Root and Recovery are two totally different things. Recovery is a partition that contain recovery information. Stock recovery is what allows OTA updates etc. Normally it will search for update.zip in the root folder of the SD card. Amon_RA's Recovery or any other recovery images are there to enhance the traditional stock recovery. Amon Ra's Recovery for example, contains thing such as ability to update from different zip files, and backup/restore of your data/system.
Rooting is not done by recovery but is a kernel level access (simply put) that will give root or "SU". It is done by patching the boot partition of the your android device.
Q: What are the differences, advantages, disadvantages of the different ROM's?
A: They are all different. Some have some features, some are plain stock, some are made for bleeding edge kernel etc. You'll have to try them out and figure out yourself. I may make a chart of what they are (see the bottom at my signature - wiki) but with too many android devices, I will need some major help. One person alone will not have total knowledge of all the ROM releases. There are just way too many devices and ROMs.
Q: Which ROM will allow OTA updates?
A: Stock ROM WITH Stock Recovery.
Q: If the phone is SIM/carrier unlocked and you root do you have to SIM unlock again?
A: SIM/Carrier unlock has nothing to do with rooting your phone. You can still have root and still be carrier locked. Nexus One comes carrier unlocked from factory.
Q: How much space is there for apps? is using the sd card really necessary? (on Nexus One)
A: Search google? The phone has 512MB or space. That SHOULD be more than enough for you. If not, you have some serious issues. I do not believe you will not App2SD for Nexus One. Google did say during the release conference that they will update Android/N1 so that apps can be run/installed to SD but that requires some system and security changes (mainly to prevent pirated software - Yes if I write something, I deserve to get paid for it).
Q: When you do "flash zip from sdcard" or "fastboot flash image" does this merge and overwrite the files in to the partition?
A: When you update a software (via recovery), software my be merged. However, if you fastboot flash, just like the word flash says, it will flash and overwrite the partition.
Q: Which partition does "flash zip from sdcard" affect?
A: Depends on what you are flashing. It could be any or all of the partitions such as SPL, Boot, System, Recovery, Radio. You should study first before randomly flashing things.
sorry, got it!
blakestimac said:
i apologize if this is the wrong place for this but, but i have adb setup perfectly, but fastboot is not recognized at all. could i have missed something?
Click to expand...
Click to collapse
I need your system info.
What os are you running? where did you get fastboot? what are you trying to do?
Don't forget fastboot boot for testing images. My most used command
I still have no idea how to use or setup adb i have downloaded the sdk and used fastboot and superboot to root my phone and am currently running the cm 5.0 beta 2 rom and want to learn how to use adb so i can enable the ram. Thanks, Joe
really a noob question here.....it wa easier with Hero.
i have installed the Android SDK
however, i cannot seem to get the laptop to detect the nexus.
what have i left out?
wishmaker738 said:
really a noob question here.....it wa easier with Hero.
i have installed the Android SDK
however, i cannot seem to get the laptop to detect the nexus.
what have i left out?
Click to expand...
Click to collapse
Check the FAQ.
dylanfan424 said:
I still have no idea how to use or setup adb i have downloaded the sdk and used fastboot and superboot to root my phone and am currently running the cm 5.0 beta 2 rom and want to learn how to use adb so i can enable the ram. Thanks, Joe
Click to expand...
Click to collapse
Ok. I need to know what you actually did. I am not understanding what you are trying to do.
Can't run adb commands - device not found
Thanks for the info. I am having an issue with running adb commands. My phone is rooted via superboot and I tested it with Nexus Torch which works. Now I am trying to install the new kernel so I can run the wireless tether app... but I can't get any of the adb commands to recognize the phone. I boot the phone by holding the trackball and power button. I am in USB debugging mode. When I run fastboot devices, the phone serial number shows up. When I run adb devices, it says no device detected. And when I try to run any other adb commands they do not work, even though fastboot commands work. Any ideas? Thanks.
Sorry i was pretty vague before i down loaded the sdk and also installed the adb setup file included with the superboot pack but just have no idea how to get it to work and add things through adb. I tried typing adb commands into comand line with the phone connected to the computer but nothing happend. just said not recognised command so i just basically need a rundown of how to setup adb.
dylanfan424 said:
Sorry i was pretty vague before i down loaded the sdk and also installed the adb setup file included with the superboot pack but just have no idea how to get it to work and add things through adb. I tried typing adb commands into comand line with the phone connected to the computer but nothing happend. just said not recognised command so i just basically need a rundown of how to setup adb.
Click to expand...
Click to collapse
I'm a noob so can't offer much help...but I would make sure the usb drivers are installed if you're using windows....this probably should have happened when you installed the sdk, but you can also install it through the device manager and point it to the folder where the usb drivers are located. Also make sure the phone is in USB debugging mode. also you may need to reboot your pc. Make sure you have setup running when you run the adb commands. you need to be in the same directory as the adb file, or in the case of the superboot pack you need to type "adb-windows" not just "adb". you may also need to put .exe, ie adb-windows.exe.
pwnvds said:
Thanks for the info. I am having an issue with running adb commands. My phone is rooted via superboot and I tested it with Nexus Torch which works. Now I am trying to install the new kernel so I can run the wireless tether app... but I can't get any of the adb commands to recognize the phone. I boot the phone by holding the trackball and power button. I am in USB debugging mode. When I run fastboot devices, the phone serial number shows up. When I run adb devices, it says no device detected. And when I try to run any other adb commands they do not work, even though fastboot commands work. Any ideas? Thanks.
Click to expand...
Click to collapse
You run fastboot from the white screen. Android on non-white screen. It's one or the other. It's ADB or Fastboot (depending on the mode of the phone).
dylanfan424 said:
Sorry i was pretty vague before i down loaded the sdk and also installed the adb setup file included with the superboot pack but just have no idea how to get it to work and add things through adb. I tried typing adb commands into comand line with the phone connected to the computer but nothing happend. just said not recognised command so i just basically need a rundown of how to setup adb.
Click to expand...
Click to collapse
Is the directory where ADB/fastboot (SDK) is installled in your system path?
I am guessing it's not. If it was, just by typing adb alone (without commands), it'll give you a list of commands. Click here if you want to know how to change your system path to include a particular folder.
We're now in the age of nintendo pilots and point and click OS that no one knows how to use command lines and system paths anymore.
recovery
I have rooted n1. when I go to recovery to do backup, I get the triangle with the little green android guy, but phone is stuck there. I have to remove battery to reboot phone. What have I done wrong?
umplarry said:
I have rooted n1. when I go to recovery to do backup, I get the triangle with the little green android guy, but phone is stuck there. I have to remove battery to reboot phone. What have I done wrong?
Click to expand...
Click to collapse
Answered in FAQ area.
seraph1024 said:
Answered in FAQ area.
Click to expand...
Click to collapse
I tried that before I posted. I searched the FAQ again. Maybe I am a complete DA, but still can't find answer. I don't mind searching, it will help me to learn, but could you point me in the right direction in FAQ?
umplarry said:
I tried that before I posted. I searched the FAQ again. Maybe I am a complete DA, but still can't find answer. I don't mind searching, it will help me to learn, but could you point me in the right direction in FAQ?
Click to expand...
Click to collapse
Q: I have rooted n1. when I go to recovery to do backup, I get the triangle with the little green android guy, but phone is stuck there. I have to remove battery to reboot phone. What have I done wrong?
A: You still have the stock (shipping) recovery. If you want a different recovery (Amon RA's), download it, the from fastboot, run fastboot flash recovery downloaded_recovery.img
Click to expand...
Click to collapse
There you go.
seraph1024 said:
There you go.
[/B]
Click to expand...
Click to collapse
Thanks for your help
seraph1024 said:
There you go.
[/B]
Click to expand...
Click to collapse
I had it downloaded, just had not flashed it
I've been looking all over, but I probably need to check the HTC Dream forum or something.
How do I install a custom ROM? I know you have to adb push update.zip somewhere, but I can't find any info about this. Please help.

[FIXES] Milestone Latest WIFI Module for 02_36 kernel

Latest and stable Wifi Driver for Android 2.1, Build SHOLS_U2_02.36.0
Build for the kernel "2.6.29-omap1"
** Stable and without any Wifi drop problem, which is compiled from the latest source from Google Android Repository. **
I recently found out that the Wifi driver of the latest Froyo 2.2.1 of Milestone that released by G.O.T. team is a new build and very stable. Therefore, I tried to pull the latest TIWLAN Wifi driver source code from the Google Android Source Repository (http://android.git.kernel.org/?p=platform/hardware/ti/wlan.git;a=summary), and compile it for the ROM build "SHOLS_U2_02.36.0", kernel "2.6.29-omap1".
I succeeded to compile as "tiwlan_drv.ko", and use it with the latest firmware "fw_wlan1271.bin" from the Froyo 2.2.1 build, and finally uses on the "SHOLS_U2_02.36.0", and the result is very stable wifi connection with the proprietary power saving feature .
I am using the ROM South Asia SHOLS_U2_02.36.0, I am not sure if it can be used with any other ROM, but normally should work on any kernel which have the version "2.6.29-omap1".
I did it because that the latest Froyo 2.2.1 beta ROM is not stable enough and the battery drain fast, but it have the stable wifi connection, so I compiled it for 2.1.
Enhancement:
Much more stable WIFI connection, no more connection drop within good signal environment.
No more WIFI freeze occur, will auto re-connect to AP if back to the signaled environment.
Much much much more battery saving (IT IS THE MOST IMPORTANT), can also feel that impressively in using "android-wireless-tether".
!!! Use it at YOUR OWN RISK !!!
Make a backup of "/system/lib/modules/tiwlan_drv.ko" and "/system/etc/wifi/fw_wl1271.bin".
Copy the file "tiwlan_drv.ko" to "/system/lib/modules/", and copy the file "fw_wl1271.bin" to "/system/etc/wifi/".
** WARNING **
Normally should work on any ROM which have the kernel version "2.6.29-omap1", BUT I didn't test it for any ROM other than SHOLS_U2.02.36.0, so USE IT AT YOUR OWN RISK!!!
It may result in bootloop in case if you did something wrong or not compatible with your ROM (need to revert back to the old driver with OpenRecovery + adb).
Therefore, it is only for advanced users, and ALWAYS MAKE FULL BACKUP of your milestone.
Download link:
http://www.sendspace.com/file/ln3xm7
Ooooo nice! The leaked rom did have superb wifi performance...
I'll give this a try on Telus' U2_03.11.0
[EDIT]What does fw_tiwlan_ap.bin do?
And the instruction for fw_wlan1271.bin is just a bit wrong... it's adb push fw_wlan1271.bin /system/etc/wifi/
[EDIT2]Woo! Works!
Lollipop_Lawlipop said:
Ooooo nice! The leaked rom did have superb wifi performance...
I'll give this a try on Telus' U2_03.11.0
[Edit]What does fw_tiwlan_ap.bin do?
And the instruction for fw_wlan1271.bin is just a bit wrong... it's adb push fw_wlan1271.bin /system/etc/wifi/
Click to expand...
Click to collapse
"fw_tiwlan_ap.bin" is the firmware required for the Froyo 2.2.1 to use Wifi Hotspot, it did nothing on Android 2.1, so just simply ignore it.
and Thanks for pointing out the location of placing the "fw_wlan1271.bin" file, I will modify it.
Lollipop_Lawlipop said:
Ooooo nice! The leaked rom did have superb
[EDIT2]Woo! Works!
Click to expand...
Click to collapse
Congratulation !!
You can use "dmesg" to see the new TIWLAN driver version
How can I copy and paste to the system?
Thanks!
royshum said:
Congratulation !!
You can use "dmesg" to see the new TIWLAN driver version
Click to expand...
Click to collapse
Thanks for your work!
I'll be putting it to the test on Monday when I get to my school campus. Stock 2.1 drivers never worked there and only 2.2.1 drivers work. Fingers crossed! Thanks for the info about the hotspot. Guess it's not very useful for 2.1 users...
How can I copy and paste to the system?
Thanks!
Click to expand...
Click to collapse
As long as you have adb setup, it's an easy task.
First, restart to recovery and do a backup:
Code:
adb pull /system/lib/modules/tiwlan_drv.ko tiwlan_drv.ko.bak
adb pull /system/etc/wifi/fw_wlan1271.bin fw_wlan1271.bin.bak
Then, unzip the files into your AndroidSDK/tools/ folder and push:
Code:
adb push fw_wlan1271.bin /system/etc/wifi/fw_wlan1271.bin
adb push tiwlan_drv.ko /system/lib/modules/tiwlan_drv.ko
adb shell reboot
Lollipop_Lawlipop said:
Thanks for your work!
I'll be putting it to the test on Monday when I get to my school campus. Stock 2.1 drivers never worked there and only 2.2.1 drivers work. Fingers crossed! Thanks for the info about the hotspot. Guess it's not very useful for 2.1 users...
As long as you have adb setup, it's an easy task.
First, restart to recovery and do a backup:
Code:
adb pull /system/lib/modules/tiwlan_drv.ko tiwlan_drv.ko.bak
adb pull /system/etc/wifi/fw_wlan1271.bin fw_wlan1271.bin.bak
Then, unzip the files into your AndroidSDK/tools/ folder and push:
Code:
adb push fw_wlan1271.bin /system/etc/wifi/fw_wlan1271.bin
adb push tiwlan_drv.ko /system/lib/modules/tiwlan_drv.ko
adb shell reboot
Click to expand...
Click to collapse
failed to copy - read only!
chungtau said:
failed to copy - read only!
Click to expand...
Click to collapse
You must have a rooted milestone in order to process.
Before you using adb push, try to remount your /system partition first.
Or you can try the following commands.
Ensure your wifi is turned off first.
*** Remember to make FULL BACKUP for your milestone before proceeding the following commands. ***
Code:
C:\android-sdk-windows\tools>adb push tiwlan_drv.ko /sdcard/tiwlan_drv.ko
C:\android-sdk-windows\tools>adb push fw_wl1271.bin /sdcard/fw_wl1271.bin
C:\android-sdk-windows\tools>adb shell
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock6 /system
# cd /system/lib/modules
# mv tiwlan_drv.ko tiwlan_drv.ko.bak
# cp /sdcard/tiwlan_drv.ko ./tiwlan_drv.ko
# chmod 644 tiwlan_drv.ko
# cd /system/etc/wifi
# mv fw_wl1271.bin fw_wl1271.bin.bak
# cp /sdcard/fw_wl1271.bin ./fw_wl1271.bin
# chmod 644 fw_wl1271.bin
# mount -o ro,remount -t yaffs2 /dev/block/mtdblock6 /system
And now, you can try turning on your wifi.
In case if there is any problem occurred, you may reboot into OpenRecovery, revert the drivers from "tiwlan_drv.ko.bak" and "fw_wl1271.bin.bak".
I want to make a quick update and say that this indeed solves my campus wifi issues I have had with 2.1-based drivers.
I'm not 100% sure about the stability of the drivers though - I'm having a little trouble with maintaining a steady connection with SwiFTP.
[EDIT]I must stress, however, that in no way does this mean the new drivers are of any blame. Until I have the time to investigate deeply into this issue, it is an isolated incident that is only occurring within my network and is of no indication of the fault of the new drivers.
I have 2.2.1 milestone but it didnt work with me proper, I installed everything properly but i got error when i try to open wifi. then i restore my back up files but it still gives me eeror
Lollipop_Lawlipop said:
I want to make a quick update and say that this indeed solves my campus wifi issues I have had with 2.1-based drivers.
I'm not 100% sure about the stability of the drivers though - I'm having a little trouble with maintaining a steady connection with SwiFTP.
[EDIT]I must stress, however, that in no way does this mean the new drivers are of any blame. Until I have the time to investigate deeply into this issue, it is an isolated incident that is only occurring within my network and is of no indication of the fault of the new drivers.
Click to expand...
Click to collapse
It is glad to hear that the new driver solved your wifi issues .
Besides, are you still having the problem even after setting the "Wifi Sleep Policy" to "Never"?
In my experience, although the new driver is much more stable, but due to the highly power saving, it may still become instable (just in weak signal, not freeze nor wifi hang) if the AP have far distance to your mobile. In this case, you may try "WifiPowerSavingOff" from market to turn off the power saving feature.
But if you turned off the power saving feature for this connection session, it may drain your battery much much faster, so just use it in some trouble network .
hagizma said:
I have 2.2.1 milestone but it didnt work with me proper, I installed everything properly but i got error when i try to open wifi. then i restore my back up files but it still gives me eeror
Click to expand...
Click to collapse
You haven't read the instructions carefully. It is the latest wifi driver for "2.1", not "2.2.1", as it is supposed to compile the driver from "2.2.1" down to "2.1".
So for 2.2.1, by default, you are already have the latest wifi driver (at least a stable wifi driver), it is no clue for using it.
royshum said:
It is glad to hear that the new driver solved your wifi issues .
Besides, are you still having the problem even after setting the "Wifi Sleep Policy" to "Never"?
In my experience, although the new driver is much more stable, but due to the highly power saving, it may still become instable (just in weak signal, not freeze nor wifi hang) if the AP have far distance to your mobile. In this case, you may try "WifiPowerSavingOff" from market to turn off the power saving feature.
But if you turned off the power saving feature for this connection session, it may drain your battery much much faster, so just use it in some trouble network :
Click to expand...
Click to collapse
Yeah, it's always set to never ever ever turn off wifi unless I explicitly shut it off. For me, it seems like wifi is transferring in bursts or in intervals. After a while (roughly 5 minutes of heavy wifi activity like FTPing stuff), the phone will freeze up and it won't even automatically reboot. Of course, a quick battery pull and the problem is solved, but nonetheless the issue is still here. It *may* be my sdcard, since I've made a swap from a class 6 4GB to a class 2 16GB, but I'm not going to jump to conclusions just yet until I do some testing here and there.
Btw, CM6 uses the file name fw_wlan1271.bin. I'm guessing stock Android from Moto looks for fw_wl1271.bin (just guessing... can't exactly prove it since I'm not running stock Android), which was why I was trying to correct you (although it seems to me both of us are right).
hagizma said:
I have 2.2.1 milestone but it didnt work with me proper, I installed everything properly but i got error when i try to open wifi. then i restore my back up files but it still gives me eeror
Click to expand...
Click to collapse
If you're running 2.2.1-CM6 you can extract the files from the update zip and adb push them into the phone. That is, if you're on CM6. If not, well... you can either upgrade to CM6 or go into fastboot and restore the sbf again.
Lollipop_Lawlipop said:
Yeah, it's always set to never ever ever turn off wifi unless I explicitly shut it off. For me, it seems like wifi is transferring in bursts or in intervals. After a while (roughly 5 minutes of heavy wifi activity like FTPing stuff), the phone will freeze up and it won't even automatically reboot. Of course, a quick battery pull and the problem is solved, but nonetheless the issue is still here. It *may* be my sdcard, since I've made a swap from a class 6 4GB to a class 2 16GB, but I'm not going to jump to conclusions just yet until I do some testing here and there.
Click to expand...
Click to collapse
Very interesting what you are saying. I had the same suspicion due the fact that the sdcard is often not accessible, this again causes multiple attempts to write and fills the buffer.
Concerning the battery pull, you can reboot and wipe the protected storage area with a script, so that you don't need to pull out the battery (which at the end does nothing else but losing voltage, resulting in loss of temp data
MenoDev said:
Very interesting what you are saying. I had the same suspicion due the fact that the sdcard is often not accessible, this again causes multiple attempts to write and fills the buffer.
Click to expand...
Click to collapse
Yes, I have the same suspicion as well.
MenoDev said:
Concerning the battery pull, you can reboot and wipe the protected storage area with a script, so that you don't need to pull out the battery (which at the end does nothing else but losing voltage, resulting in loss of temp data
Click to expand...
Click to collapse
Can you go into a bit of detail on that? I'm interested
I've also had problems with the cell signal for 2.2-CM6. Again, I'm not sure the cause of it, but it's a very very serious issue that strikes at the wrong time. It seems like the cell radio freezes up even after a reboot with zero prior warning. So when I try to make a call, it doesn't go through. It's super frustrating, especially when there's really no good alternative to 2.2-CM6 right now. The only way to resolve this issue is to push the Telus baseband files again, but after a while it'll freeze up again. Ugh.
At least the Wifi works.
[EDIT]It seems like the cell problem is at least reported in the thread and acknowledge by other users. It seems to be fixed on 2.2.1-CM6, but since that's a little meh right now I'll have to dig around and see just what's causing the freeze.
[EDIT2]In fact, it seems like the problem is pretty widespread. Anything 2.2-CM6 based (that includes MotoFrenzy, Cronos...) has this problem.
works flawless, extreme improvement, thank you very much!
Lollipop_Lawlipop said:
Yes, I have the same suspicion as well.
Can you go into a bit of detail on that? I'm interested
Well, I use to code similar stuff but I am complete new to android so i have to read the dev guide, if I had no guide I'd probably create a dump, see according the file descriptor where the tables and storage are are located, then set a "write" flag on the file system and flush it to avoid a manual battery pull. but i'm sure there's more elegant ways.
I've also had problems with the cell signal for 2.2-CM6. Again, I'm not sure the cause of it, but it's a very very serious issue that strikes at the wrong time. It seems like the cell radio freezes up even after a reboot with zero prior warning. So when I try to make a call, it doesn't go through. It's super frustrating, especially when there's really no good alternative to 2.2-CM6 right now. The only way to resolve this issue is to push the Telus baseband files again, but after a while it'll freeze up again. Ugh.
At least the Wifi works.
[EDIT]It seems like the cell problem is at least reported in the thread and acknowledge by other users. It seems to be fixed on 2.2.1-CM6, but since that's a little meh right now I'll have to dig around and see just what's causing the freeze.
[EDIT2]In fact, it seems like the problem is pretty widespread. Anything 2.2-CM6 based (that includes MotoFrenzy, Cronos...) has this problem.
Click to expand...
Click to collapse
I made a little research and found a working solution, tested it myself.
Apparently it can happen that the resolved DNS can not be stored under certain circumstances, (in order to trace those, i try to avoid the "out of the box" mods, even though the guys make a tremendous job, but i feel more secure and have a higher learning curve by doing stuff myself).
In order to avoid random disconnects from network or wifi, or worst case both, add the following lines of code to /system/default.prop
net.dns1=8.8.8.8
net.dns2=8.8.4.4
net.rmnet0.dns1=8.8.8.8
net.rmnet0.dns2=8.8.4.4
These are the google dns, most probably the best choice. You can find this out if you fire up the "getprop" command.
I've seen that most Recovery tools such as the G.O.T one, have implemented the DNS fix, but personally I prefer to just fire up a terminal from the phone and add these lines manually with some comment, so i know what and why I'm doing stuff.
Hope this helps, let me know.
Please help! I succesfully copied both files using root explorer, but now I can't turn on wifi. Then I have restored the original files but it didn'tsolve the issue. I could do a nandroid restore but I really don't want to (last backup is quite old). I have a german milestone running 2.1 build SHOLS_U2_02.36.0
b787 said:
Please help! I succesfully copied both files using root explorer, but now I can't turn on wifi. Then I have restored the original files but it solve the issue. I could do a nandroid restore but I really don't want to (last backup is quite old). I have a german milestone running 2.1 build SHOLS_U2_02.36.0
Click to expand...
Click to collapse
If you followed the instruction you should have to *.bak files that you previously pulled, so no need to do a "panic rollback".
Did you turn of wifi before copying the kernel objects and made a reboot before turning on wifi as described in the howto ?
MenoDev said:
If you followed the instruction you should have to *.bak files that you previously pulled, so no need to do a "panic rollback".
Did you turn of wifi before copying the kernel objects and made a reboot before turning on wifi as described in the howto ?
Click to expand...
Click to collapse
I did turn off wifi before copying any files. However, I didn't rebooted before I tried to start wifi, only after I noticed it doesn't work.
Fix for 2.2.1 Possible?
I have the same issue with my home WIFI network on 2.1 and 2.2.1: namely the connection drops during large transfers (such as a Market app download) and I have to turn WIFI off and on again to have connectivity again.
I wonder if 2.2.1 really has the latest firmware baked in...how would I compile the TI firmware for 2.2.1?

[Q] NO 3G after UNBRICKING... :(

being stupid and messing around with rom manager somehow i had deleted my
stock flash of the 1.6... so it installed a rom that worked but when i went to connect to the cricket network with the *228 it gave me verizon wirless.... then i tried to install my backup flash...thats when i bricked the phone... after a few hours i was able to get froyo back on my phone and the only thing that doesnt work is the 3G!!! my download speed is only around 130kb or so.....!!!!!!! anyway her are my network settings. if anyone knows how to fix or change these settings it would be greatly appreciated!!!
FIXD UNROOT B 4 programming!!!
alot of people seem to get there zio's bricked unbricking was easy after figuring it out unstead of the hard reset i got the phone into the modem update mode by holding down both volume buttons and the end or some combination from there was able to use my pc to do the froyo update via usb....
Dial *228
Sent from my Zio using XDA Premium App
yeah i tried that first off dialing the *228 it gives me an error..... the phone works but the signal is extremely worse than usual..... after restoring the phone my number works from the phone just a horrible signal and no 3G! i just bought the phone hopefully cricket will help me out if not TIME for a real droid!!!
Since you altered recovery, you voided and warranty / liability with cricket.
Expect to pay for them to service your phone.
Depending on the intelligence of the Rep examining ur phone, you may be able to get away with it. Just don't mention anything about altering ur phone in any way.
fc3snstl said:
yeah i tried that first off dialing the *228 it gives me an error..... the phone works but the signal is extremely worse than usual..... after restoring the phone my number works from the phone just a horrible signal and no 3G! i just bought the phone hopefully cricket will help me out if not TIME for a real droid!!!
Click to expand...
Click to collapse
Sent from my Zio using XDA App
Yeah don't say crap. I jacked my phone due to not listening to spz0 but fix what I screwed up. I'm still having a signal problem though.
ZIO 2.2 ROOTED
ADW Launcher EX
Gingerbread Theme
Stop by openzio today and I'll see if we can get ur data working well again.
z3r0t0l0rEnCe said:
Yeah don't say crap. I jacked my phone due to not listening to spz0 but fix what I screwed up. I'm still having a signal problem though.
ZIO 2.2 ROOTED
ADW Launcher EX
Gingerbread Theme
Click to expand...
Click to collapse
Sent from my Zio using XDA App
as far as the data goes.... after the unroot and reprogramming my 3g came back and all seems well....except for the download speed is slim to none on any download over 600kb or so....html or browsing the internet no problem on 3g...streaming youtube on 3g is pointless... does youtube load quickly for anyone? or even load a 2 min video without pausing? on wifi no problem works great....
There is obviously something wrong with phone's 3G reception. Hopefully that spz0 can figure out a perm fix or otherwise take it to cricket rep. Play dumb and blame the brick on the OTA froyo update and don't mention anything about rooting.
Sent from my Zio using XDA Premium App
K. I'm going to give some instructions here. Very Clear. Follow them to the letter and you shouldn't have any problems or have to ask any questions.
**note: You'll need ADB on your PC for this.
I _think_ if you download and install the M6000 Drivers provided by the tethered update process, it may install ADB.
Try that method first, reboot your PC, connect your phone and you should be able to open up a command prompt and type:
Code:
adb devices
Your phone should list under devices as a bunch of numbers/letters.
If that doesnt work, follow Androids instructions to install the Android SDK and continue these instructions.
**remember to ad the adk path to your environment variables path section (as described in the setup of SDK on the Android site). This will allow you to run ADB without having to navigate to the folder it is installed in.**
YOUR PHONE NEEDS TO BE ROOTED FOR THIS PROCESS.
1)Download the following files:
Stock 2.2 Recovery Image
http://www.mediafire.com/?9zqvczb92r22qg1
flash_image (needed to flash recovery)
http://www.mediafire.com/?pc52nfnb185m768
2) Copy those files to the ROOT of your SDCard.
3) Connect your phone to your PC
4) Open up a command prompt and type the following:
Code:
adb devices
Your phone should be listed as a connected device (bunch of numbers/letters)
Code:
adb shell
su
**make sure your phones display is turned on and you accept the superuser request on your phone.
5) Once you obtain root (your "$" changes to "#"), type the following:
Code:
cat /sdard/flash_image > /system/bin/flash_image
chmod 0755 /system/bin/flash_image
6) Next, type the following:
Code:
cd system/bin
flash_image recovery /sdcard/recovery.img
This will flash the stock recovery to your recovery partition.
7) Next, type:
Code:
exit
exit
**yes, thats exit twice. This will get you out of the phones shell
8) Next, factory reset your phone. Type the following:
Code:
adb reboot recovery
Your phone should reboot, wipe data/cache and reboot into a stock image.
9) Dial *228
10) Profit.
**if you are still roaming after reboot, you will have to perform a factory reset (menu->settings->privacy->factory data reset) to revert to crickets APN.
I can't make it any more clear than this, so if this does not work for you, then I suggest re-installing the tethered upgrade to reflash all your partitions to stock.
ALTERNATE METHOD
You may also do this from fastboot.
Instead of using "flash_image" provided above, just download the stock 2.2 recovery image, put it in your SDK "/tools" directory (where your fastboot exe is located). Power on into fastboot (end and send keys simultaneously), open a command prompt and navigate to your SDK/tools/ directory then type:
Code:
fastboot flash recovery recovery.img
fastboot reboot
Once your phone reboots to your OS, perform a factory data reset (menu->settings->privacy->factory data reset) to revert to crickets APN.
Worked very easy even with windows 7 have had no problems doing any droid related tasks with this os...the reflash worked still network problem went to the cricket store after unrooting phone these guys didn't notice anything out of the ordinary couldn't believe it anyways he said 20 bux for a new one...
Sent from my MB860 using XDA App

[GUIDE] [froyo] Downgrade to 1.36

How to downgrade to 1.36 (release ruu)
This only works on froyo based roms, gingerbread radio won't downgrade
About:
Currently it is not necessary to downgrade since no exploits have been found. But for the case we have to downgrade, we have it. It is currently only tested on the leaked ASIA rom, but cannot imagine it is not working on later/other ROMs.
I have nothing to do with this method, i only wrote the guide.
This guide is based on the DHD downgrade (so many similarities will be found)
Anyhow keep in mind that:
You will lose all data on your phone (not from your sd-card)
First boot after downgrade can take pretty long (a few minutes) so dont be scared it didn't work and absolutly DON'T pull your battery out. Just wait a while, if its beyond 15min and still not working. Come here and ask. And DONT PULL THE BATTERY unless you are told to.
Thanks:
Scotty2, rhcp and Guhl for development of this method
jkoljo for putting up the DHD guide
bippolinno for the ruu mirror
lge73 for testing and getting it done
If i miss someone, please tell me and i add u
System requirements:
HTC Sync (or ADB drivers)
Incredible S with build number higher than 1.36
A working ADB setup (ADB is included in the downgrade package though)
Howto downgrade:
If you have a branded device, Goldcard is required (have not tested it if its required for a non-branded device EDIT: unbranded seems to work without goldcard)
The PG32IMG.zip (if the download is not working extract it from the RUU, can be done by yourself (see below))
Connect Incredible S to a computer. Charge only, USB Debugging enabled!
Open up cmd/terminal and go to downgrade folder
Code:
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
adb shell
If you got "#" in the result, you have temproot! Proceed:
Code:
cd /data/local/tmp
./misc_version -s 1.31.405.1
Put the PG32IMG.zip on the root of your SD Card (trough adb push or just connect it as a disk drive)
Reboot into bootloader (adb reboot-bootloader or hold volume down while rebooting)
Follow the instructions
Ready, you have downgraded your Incredible S to release ROM
Extracting rom.zip from RUU.exe
Ruu can be found here
Make sure your INC s is connected
Start installer
Click next
Click next
Goto your temp folder (open the start menu, type %tmp% and press enter, ty l0st.prophet)
Sort folders on date
Pick the most recend and look inside one of that folders for rom.zip
Copy it to downgrade folder (or anywhere else) and rename to PG32IMG.zip
Disclaimer:
I am not responsible for bricks
Thanks to all involved!
I would recommend that you mention all data on the device will be wiped by this downgrade and that the reboot after downgrade will take a little while and not to get scared or do silly things like pull the battery out!
Thank you for this very clear guide !
Now, I just need to know where to get the European rom ! (i will install the european rom instead of the asian)
Someone can give me the link ? Please ?
It is in the guide (RUU.exe). Just download and install. Just received message from the tester that it is also possible with just the misc_version hack and use the RUU.exe
It is the oldest currently available. But i'm not 100% sure if its the same as the old European Rom, but it has the same number as mine (Netherlands) so i quite sure its the same.
I can not extract with ruu...
Cause i have an asian version. I didn't upgraded it...
I just need to install the european Rom.
If someone can share this for me, it will be great !
Thank you guys
Like i said: download the ruu from this topic it is the european. Than follow the guide. I don't know how I can be any clearer.
Don't know what the problem is since all you say that you want the European ROM. Btw if you have preinstalled Asian ROM, there is a possibility that there are minor differences. But you can always flash the Asian ROM back.
Thank you again...
Sorry but my English and android's knowledge are not so good
That's no problem. I advice to get a little basic knowledge about Android, since this process on the IS is still in its early stage a lot can go wrong and currently there are not many methods available for fixing it. Not that a lot can go wrong here, but if it does you are screwed.
So if you don't know what is going on, I advice to stay at the default stock ROM.
Extracting rom.zip from RUU.exe
Ruu can be found here
Make sure your INC s is connected
Start installer
Click next
Click next
Goto your temp folder
Sort folders on date
Pick the most recend and look inside one of that folders for rom.zip
Copy it to downgrade folder (or anywhere else) and rename to PG32IMG.zip
Oh hell 2 nights I used to figure it out were that temp folder could be.
First I had to turn on the option see hidden files.
C:/Users/%user%/Appdata/Local/Temp
Windows is so frustrating wen your used to a Mac.
ab65 said:
Extracting rom.zip from RUU.exe
Ruu can be found here
Make sure your INC s is connected
Start installer
Click next
Click next
Goto your temp folder
Sort folders on date
Pick the most recend and look inside one of that folders for rom.zip
Copy it to downgrade folder (or anywhere else) and rename to PG32IMG.zip
Oh hell 2 nights I used to figure it out were that temp folder could be.
First I had to turn on the option see hidden files.
C:/Users/%user%/Appdata/Local/Temp
Windows is so frustrating wen your used to a Mac.
Click to expand...
Click to collapse
It's alot simpler than that, just open the start menu, type %tmp% and press enter. Voila!
thanks l0st.prophet
that information comes in handy. it's so easy if you know
don't ask how long I used to get a working ADB setup, and that is also a piece of cake wen you figured it out.
( I'm still on PPC Mac and muss use the Pc of my son, and he is enjoying it seeing me so helpless on windows system)
But it's a great tutorial and in the end all went fine.
Thank you xda comunity.
thanks for share
this is very helpful
does this work for s-on devices?
shiftyllama said:
does this work for s-on devices?
Click to expand...
Click to collapse
Yes, although it's untested on the new GB ROMs.
I get an error when running the adb command:
adb shell /data/local/tmp/psneuter
reading:
Failed to set prot mask <Inappropriate ioctl for device>
I'm trying to downgrade from Vivo_Gingerbread_S_Virgin_Mobile_AU_2.12.981.2
Any ideas. Does the psneuter exploit no longer work with gingerbread?
doctorsax said:
Yes, although it's untested on the new GB ROMs.
Click to expand...
Click to collapse
Tested on Gingerbread 2.3.3 but, the radio will not downgrade so the OS does not load.
The "How to" is a little different tho.
Note: Do not update to GB if you want to downgrade back to froyo anytime soon.
I'll attach this here for safe keeping.
touchpro247 said:
Tested on Gingerbread 2.3.3 but, the radio will not downgrade so the OS does not load.
The "How to" is a little different tho.
Note: Do not update to GB if you want to downgrade back to froyo anytime soon.
I'll attach this here for safe keeping.
Click to expand...
Click to collapse
so am i stuck with the aussie virgin ROM untill an RUU for europe is released?
shiftyllama said:
so am i stuck with the aussie virgin ROM untill an RUU for europe is released?
Click to expand...
Click to collapse
Yes or until a full root method is released.
I am trying to downgrade now tho and then force the ota.
Wish me luck...
touchpro247 said:
Yes or until a full root method is released.
I am trying to downgrade now tho and then force the ota.
Wish me luck...
Click to expand...
Click to collapse
good luck.....
and let us know if you manage it and how!!

Categories

Resources