I created this thread to help people who are having issues getting their Rogers Captivate running Froyo.
I just recently got a Samsung Captivate (locked to Rogers).
The guy i bought it from had rooted it and installed the AT&T 2.2 Froyo ROM but he didn't unlock the phone
I tried to unlock it while running Froyo, but had no luck.
In the end I rolled the ROM back to the stock 2.1 Eclaire ROM; from there I could unlock the phone and then upgrade to the leaked 2.2 Froyo ROM and remove all of the AT&T bloatware
I hope this guide can help others unlock the true potential of their phone too
Disclaimer
I am only giving this information as a guideline.
I take no responsibility if you brick your phone and can't recover it.
I followed the below steps and got my phone working really well, but I don't know enough about this to give a guarantee.
Resources
Helpful Guide
File Patching Site
Samsung Windows Drivers
Captivate Windows Drivers (32-bit)
Captivate Windows Drivers (64-bit)
Stock AT&T 2.1 Eclair ROM
Leaked AT&T 2.2 Froyo ROM
Rooting Tool (works with 2.1 Eclair ROM)
Rooting Tool (works with 2.2 Froyo ROM)
Phone Unlocker
Note:
If you've already installed Froyo, your nv_data.bin file is likely gone (it gets deleted by the updater). This sucks because this file has your unlock code in it.
Determine if it's Locked
To determine if you phone is locked, go to your dialer (on your phone) and enter *#7465625#
If Network Lock is [ON] then your phone is locked.
In this case, you should perform all of the below steps (at your own risk).If Network Lock is [OFF] then your phone is NOT locked .
In this case you can either walk away happy or just do steps 6-9 listed below (at your own risk).I don't know what the other locks refer to.
Unlocking your Phone
flash back to a 2.1 Eclair ROM
I chose to use the Stock AT&T 2.1 Eclair ROM because I heard that the Rogers 2.1 Eclair ROM doesn't have the nv_data.bin file.
download and extract the Stock AT&T 2.1 Eclair ROM
download and install the Samsung Windows Drivers
download and extract the Captivate Windows Drivers (*-bit) (use the 32 or 64 bit depending on your version of Windows)
run the Stock AT&T 2.1 Eclair ROM program (it's a Windows program)
put your phone into Debug Mode*
plug your USB cable into your PC.
connect your phone to the PC in Download Mode**.
if Windows says that if failed to install the drivers for your phone, update the drivers by telling Windows to look inside the directory where you extracted the Captivate Windows Drivers (*-bit).
Once your phone is installed properly, the Stock AT&T 2.1 Eclair ROM program should have detected it. Once detected, press the Start button and just wait. (this process can take a little while, your phone will also load slowly the 1st time)
when it's done, your phone will be booted back into Android and the Stock AT&T 2.1 Eclair ROM program should say that it was successful.
root it
download and extract the Rooting Tool (works with 2.1 Eclair ROM)
put your phone into Debug Mode*
plug your USB cable into your PC.
connect your phone to the PC in Download Mode**.
run the Rooting Tool (works with 2.1 Eclair ROM) program and click the One-Click Root button.
when it's done, your phone will be rooted and you'll be able to grant superuser access.
extract and patch the nv_data.bin file
go to the File Patching Site and follow the instructions.
flash to the 2.2 Froyo ROM
download and extract the Leaked AT&T 2.2 Froyo ROM
run the Leaked AT&T 2.2 Froyo ROM program (it's a Windows program)
put your phone into Debug Mode*
plug your USB cable into your PC.
connect your phone to the PC in Download Mode**.
Once your phone is installed properly, the Leaked AT&T 2.2 Froyo ROM program should have detected it. Once detected, press the Start button and just wait. (this process can take a little while, your phone will also load slowly the 1st time)
when it's done, your phone will be booted back into Android and the Leaked AT&T 2.2 Froyo ROM program should say that it was successful.
root the phone again
download and extract the Rooting Tool (works with 2.2 Froyo ROM)
put your phone into Debug Mode*
plug your USB cable into your PC.
connect your phone to the PC in Download Mode**.
run the Rooting Tool (works with 2.2 Froyo ROM) program SuperOneClick.exe and click the Root button.
when it's done, your phone will be rooted and you'll be able to grant superuser access.
enable side-loading of apps
to do this, you must have done the previous step root the phone again
download and extract the Rooting Tool (works with 2.2 Froyo ROM)
put your phone into Debug Mode*
plug your USB cable into your PC.
connect your phone to the PC in Download Mode**.
run the Rooting Tool (works with 2.2 Froyo ROM) program SuperOneClick.exe and click the Allow Non Market Apps (requires root) button.
when it's done, your phone will be able to accept side-loaded apps to be installed on it.
get your phone working properly with Rogers
The phone will come back up with voice services working, but no MMS or data. In order to make data and MMS work, you need to set the Access Point Name (APN) settings in the phone’s config. APN Settings can be found under Settings > Wireless > Mobile Networks >Access Points. Set the following:
Name: Rogers
APN: rogers-core-appl1.apn
MMSC:http ://mms.gprs.rogers.com
MMS Proxy: 10.128.1.69
MMS Port: 80
MCC: 302
MNC: 720
Everything else blank.
You should now have a working data connection!
remove all AT&T bloatware
just follow the instructions at the bottom of the Helpful Guide.
install your favorite apps via the Android Market
* Debug Mode is when you put your phone in a mode which enables shell (scripting-level) access to the Android operating system. This is needed to perform many tasks when it comes to rooting, unlocking, side-loading apps, etc...
In your phones main menu, go to Applications ==> Development ==> USB Debugging
** Download Mode basically tells the phone to allow an external program to update it's ROM (operating system).
Hold-down both volume buttons on your phone and then plug the USB cable into your phone.
My Resources
http://forum.xda-developers.com/showthread.php?t=831569
http://www.communityhosting.net/sgsunlock/
http://www.mmacleod.ca/blog/2010/10/updating-the-rogers-samsung-galaxy-s-captivate-to-android-2-2-froyo/
This is nice and all, but why not just root the phone install CWM and flash a nicer rom and not worry about ATT bloatware have a better kernal HUSPA better battery life BLN and the best lagfixes?
slayp00n said:
This is nice and all, but why not just root the phone install CWM and flash a nicer rom and not worry about ATT bloatware have a better kernal HUSPA better battery life BLN and the best lagfixes?
Click to expand...
Click to collapse
Thanks for the info, I'm still really new to this; i'll probably give your recomendation a try soon
I just want to be sure that everything works fine... My friend who knows a lot more about this is currently on vacation, i'll see which rom he installed as his captivate is running really well too.
Nice guide, with this I got Froyo running on my phone. However, when I went to the market to download apps I bought back when I had stock firmware, they weren't there anymore. I was just wondering if you had the same problem and a possible solution.
I've been going through many pages of different forums and none of the methods are working. Many of the guides required me to download apps from the market to assist me in uploading a new build.prop file to /system/ but I cant see any of them since my market is screwed up.
Is your android market working fine ?
I managed to get a new build.prop uploaded with different fingerprint codes:
ro.build.fingerprint=verizon/voles/sholes/sholes:2.1-update1/ESE81/29593:user/release-keys
ro.build.fingerprint=verizon_wwe/inc/inc/inc:2.2/FRF91/231334:user/release-keys
both didn't work.
I then reflashed using the 2.2 froyo that you have linked at the top, and now my market app is the same as before. When I first flashed it I could see all the apps but I am having the same issues as before. I was about to try a rom called Cognition but seeing as how reflashing didn't work I am running out of ways of fixing this :S
This is the stock APN from my Rogers Captivate
FROYO lag fix help
Hey guys.
Kind of a noob here. I was wondering if someone can help me fix the lag problem i have with my captivate running on froyo 2.2 that i upgraded through Keis. I had the 2.1 lag fixed before i upgraded to froyo and it was amazingly fast! i want the same speed now if someone can give me a link or explain to me the easiest way to go about this, that would be awesome! thank you!!
Related
I am posting this message in the developer section because I thought the developers of the various ROMs might want to know of problems that at least one user is experiencing.
The problems I have noticed include the loss of ADB access to the phone, Market freezing and doing reboots during updates and installs, and apps installed via Zips not showing in Market Downloads for updates.
It appears that the problem with the Market freezing during updates may have been caused by me doing multiple zips when in clockwork, for these tests I only did one zip each time and that corrected the problem.
I was experiencing a problem where ODIN would not recognize the phone after the DK17 ROM was loaded but I suspect that was due to going from one DK17 ROM to another because the process I followed below ODIN saw the phone each time.
The ADB not working and the zip apps not showing persist. My test plan and results for multiple ROMs are below...
My process...
- Use 3 finger salute to enter Clockwork Recovery
- Wipe 3 times
- Install from zip to [ACS] SyndicateROM 1.0.2 (Shuriken)
This ROM works well for me and does not experience any of the problems I have been having with DK15
- Reboot system and confirm proper operation
- Able to use ADB
- WiFi, 3G, and 4G working
- All Apps installed via Zip detected by Market
- Update of App (Using Google Maps) not hanging system
- Power down system
- Reboot phone into Download Mode
- Confirm Odin3 v1.61 sees the phone
- Remove battery for cold restart
- Use 3 finger salute to enter Clockwork Recovery
- Wipe 3 times
- Install from zip to desired ROM
- Reboot System
- Test ADB
- Test 4G
- Sign into Google
- Test Update of App (Google Search & Maps)
- Power down system
- Use 3 finger salute to enter Clockwork Recovery
- Install Zip of preferred apps
- Reboot System
- Check Market for Apps
- Attempt Update again
- Retest ADB
- Connect WiFi
- Test Wireless ADB
- Reboot phone into Download Mode
- Confirm Odin3 v1.61 sees the phone
- Rinse & Repeat for next ROM
The results:
[Stock Flash][Odin]Dk17 Extended 11/27/2010
-------------------------------------------------
Filename: DK17-Extended.rar
Note: Installed via ODIN and not using Clockwork
ADB - Device not found
4G - Worked (Fell asleep during download - Continued after waking back up)
Market Update - Installs worked with no problems
Zipped Apps - Not listed in market
Market Update x2 - Worked
ADB x2 - Device not found
WiFi - Worked
adbWireless - Worked
ODIN - Detected (Retest?)
[ACS] Froyo Build DK17 - Deodexed/Zipaligned/Rooted - No FC - 11/23
-------------------------------------------------
Filename: acs-dk17-signed.zip
ADB - Device not found
4G - Worked
Market Update - Worked
Zipped Apps - Not showing
Market Update x2 - Worked
ADB x2 - Device not found
WiFi - Worked
adbWireless - Worked
ODIN - Detected
Froyo Beta V1.0.2 Devsforandroid
-------------------------------------------------
Filename: Mammon_Froyo_Beta_V1.0.2.zip
ADB - Works!
4G - Works
Market Update - Worked
Zipped Apps - Did not show
Market Update x2 - Worked
ADB x2 - Worked
WiFi - Workd
adbWireless - Worked
ODIN - Detected
Froyo Beta V1.0.3 - Devsforandroid 11-27-2010
-------------------------------------------------
Filename: Mammon_Froyo_Beta_V1.0.3.zip
ADB - Device not found
4G - Works (but sleeps easy)
Market Update - Worked
Zipped Apps - Not shown in market
Market Update 2 - Worked
ADB x2 - No
WiFi - Started Freezing - Restart Cycle
adbWireless - Unable to test
ODIN - Worked
Quantum Rom v1.4 DK17
-------------------------------------------------
Filename: QuantumRomv1.4_signed.zip
ADB - Device not found
4G - Worked
Market Update - Worked
Zipped Apps - Not detected
Market Update 2 - Worked
ADB x2 - Device not found
WiFi - Worked
adbWireless - Worked
ODIN - Worked
Quantum Rom v1.5 DK17 [WarpSpeed Edition] [Updated 11/27]
-------------------------------------------------
Filename: QuantumRomv1.5.zip
ADB - Device not detected
4G - Worked
Market Update - Worked
Zipped Apps - Not listed in market
Market Update 2 - Worked
ADB x2 - Device not detected
WiFi - Worked
adbWireless - Worked
ODIN - Worked
VIPERrom [IMPact] (DK17 Kernel) 2.2
-------------------------------------------------
Filename: VIPERrom [IMPact] DK17 2.2.zip
ADB - Device not detected
4G - Worked
Market Update - Worked
Zipped Apps - Not listed in market
Market Update 2 - Worked
ADB x2 - Device not detected
WiFi - Worked
adbWireless - Worked
ODIN - Worked
This is extremely helpful.
I've experienced the Sleep issue mentioned with the two ROMs mentioned above as well the ziped apps update issue.
Thanks for putting the time in to compile this
PokrTom said:
[Stock Flash][Odin]Dk17 Extended 11/27/2010
-------------------------------------------------
Filename: DK17-Extended.rar
Note: Installed via ODIN and not using Clockwork
ADB - Device not found
4G - Worked (Fell asleep during download - Continued after waking back up)
Market Update - Installs worked with no problems
Zipped Apps - Not listed in market
Market Update x2 - Worked
ADB x2 - Device not found
WiFi - Worked
adbWireless - Worked
ODIN - Detected (Retest?)
Click to expand...
Click to collapse
Well first thing wrong is that this isn't a rom by normal standards, its an Odin flash sort like the official Releases and what you get on your phone natively.
Secondarly it's also using the same "rom" flashable as the ACS dk17 that k0nane made. Second thing wrong is there is no way to install this via clockwork.
Therefore it's not a rom, it's a stock as sprint wouldnt have given it to you more or less and shouldn't be treated as a rom but as a recovery point.
Nothing overtly special has been done with this Flash or with the ACS k0nane flashable. so therefore there is nothing to fix.
Figured i'd make this point as everyone seems to see something new on the forums and go ooo new wrong works great except....
Perhaps understanding what they are would be a touch more helpful than a biased self comparision, seeing as how i could do the exact same test and get different results because my phones is different(ie it doesnt suffer the gps bug a fair amount do)
but it is what it is....
Take it with a grain of salt and understand that your mileage may very.
PS: the market not seeing apps is a simple fixable thing that's searchable in the forum, while it can be corrected quite easily, it's not a flaw that it's missing, these are BETA not for public distro leaks.
art3mis-nyc said:
but it is what it is....
Take it with a grain of salt and understand that your mileage may very.
PS: the market not seeing apps is a simple fixable thing that's searchable in the forum, while it can be corrected quite easily, it's not a flaw that it's missing, these are BETA not for public distro leaks.
Click to expand...
Click to collapse
This.
And keep in mind that stock builds don't turn USB Debugging on by default.
Tabulating the results would get you an A+; it's kind of hard to make any sense of it right now.
...but I also strongly agree that all of this is very circumstantial. The mere fact that some people have _____ working and others do not means that whatever results you get will not always be repeatable.
Yeah... Why would you list adb device not found when you forgot to turn on usb debugging? lmao.
art3mis-nyc said:
Well first thing wrong is that this isn't a rom by normal standards, its an Odin flash sort like the official Releases and what you get on your phone natively.
Click to expand...
Click to collapse
I understood this. I included it in my testing in part, as a baseline, and also because if I had not, then if someone had been interested in the results they may have asked how it behaved for me.
Forgive me for being a Noob and providing the information I did. I thought that this was a development forum, where developer might be interested in what results some people were getting. It appears that if you are not part of the developing community then input providing results is not wanted. I will just keep my mouth shut and enjoy the fruits of their labor.
On that point, to all the developers out there who have put forth the great effort they have, I give my thanks.
PokrTom said:
I understood this. I included it in my testing in part, as a baseline, and also because if I had not, then if someone had been interested in the results they may have asked how it behaved for me.
Forgive me for being a Noob and providing the information I did. I thought that this was a development forum, where developer might be interested in what results some people were getting. It appears that if you are not part of the developing community then input providing results is not wanted. I will just keep my mouth shut and enjoy the fruits of their labor.
On that point, to all the developers out there who have put forth the great effort they have, I give my thanks.
Click to expand...
Click to collapse
It is not that "We developers are better than you." It is the fact that the tests you performed were not done properly.
For one; For adb to work, USB Debugging must be turned on. (And no it is not on in every ROM by default)
What the hell are zipped apps?
PokrTom said:
I am posting this message in the developer section because I thought the developers of the various ROMs might want to know of problems that at least one user is experiencing.
The problems I have noticed include the loss of ADB access to the phone, Market freezing and doing reboots during updates and installs, and apps installed via Zips not showing in Market Downloads for updates.
It appears that the problem with the Market freezing during updates may have been caused by me doing multiple zips when in clockwork, for these tests I only did one zip each time and that corrected the problem.
I was experiencing a problem where ODIN would not recognize the phone after the DK17 ROM was loaded but I suspect that was due to going from one DK17 ROM to another because the process I followed below ODIN saw the phone each time.
The ADB not working and the zip apps not showing persist. My test plan and results for multiple ROMs are below...
My process...
- Use 3 finger salute to enter Clockwork Recovery
- Wipe 3 times
- Install from zip to [ACS] SyndicateROM 1.0.2 (Shuriken)
This ROM works well for me and does not experience any of the problems I have been having with DK15
- Reboot system and confirm proper operation
- Able to use ADB
- WiFi, 3G, and 4G working
- All Apps installed via Zip detected by Market
- Update of App (Using Google Maps) not hanging system
- Power down system
- Reboot phone into Download Mode
- Confirm Odin3 v1.61 sees the phone
- Remove battery for cold restart
- Use 3 finger salute to enter Clockwork Recovery
- Wipe 3 times
- Install from zip to desired ROM
- Reboot System
- Test ADB
- Test 4G
- Sign into Google
- Test Update of App (Google Search & Maps)
- Power down system
- Use 3 finger salute to enter Clockwork Recovery
- Install Zip of preferred apps
- Reboot System
- Check Market for Apps
- Attempt Update again
- Retest ADB
- Connect WiFi
- Test Wireless ADB
- Reboot phone into Download Mode
- Confirm Odin3 v1.61 sees the phone
- Rinse & Repeat for next ROM
The results:
[Stock Flash][Odin]Dk17 Extended 11/27/2010
-------------------------------------------------
Filename: DK17-Extended.rar
Note: Installed via ODIN and not using Clockwork
ADB - Device not found
4G - Worked (Fell asleep during download - Continued after waking back up)
Market Update - Installs worked with no problems
Zipped Apps - Not listed in market
Market Update x2 - Worked
ADB x2 - Device not found
WiFi - Worked
adbWireless - Worked
ODIN - Detected (Retest?)
[ACS] Froyo Build DK17 - Deodexed/Zipaligned/Rooted - No FC - 11/23
-------------------------------------------------
Filename: acs-dk17-signed.zip
ADB - Device not found
4G - Worked
Market Update - Worked
Zipped Apps - Not showing
Market Update x2 - Worked
ADB x2 - Device not found
WiFi - Worked
adbWireless - Worked
ODIN - Detected
Froyo Beta V1.0.2 Devsforandroid
-------------------------------------------------
Filename: Mammon_Froyo_Beta_V1.0.2.zip
ADB - Works!
4G - Works
Market Update - Worked
Zipped Apps - Did not show
Market Update x2 - Worked
ADB x2 - Worked
WiFi - Workd
adbWireless - Worked
ODIN - Detected
Froyo Beta V1.0.3 - Devsforandroid 11-27-2010
-------------------------------------------------
Filename: Mammon_Froyo_Beta_V1.0.3.zip
ADB - Device not found
4G - Works (but sleeps easy)
Market Update - Worked
Zipped Apps - Not shown in market
Market Update 2 - Worked
ADB x2 - No
WiFi - Started Freezing - Restart Cycle
adbWireless - Unable to test
ODIN - Worked
Quantum Rom v1.4 DK17
-------------------------------------------------
Filename: QuantumRomv1.4_signed.zip
ADB - Device not found
4G - Worked
Market Update - Worked
Zipped Apps - Not detected
Market Update 2 - Worked
ADB x2 - Device not found
WiFi - Worked
adbWireless - Worked
ODIN - Worked
Quantum Rom v1.5 DK17 [WarpSpeed Edition] [Updated 11/27]
-------------------------------------------------
Filename: QuantumRomv1.5.zip
ADB - Device not detected
4G - Worked
Market Update - Worked
Zipped Apps - Not listed in market
Market Update 2 - Worked
ADB x2 - Device not detected
WiFi - Worked
adbWireless - Worked
ODIN - Worked
VIPERrom [IMPact] (DK17 Kernel) 2.2
-------------------------------------------------
Filename: VIPERrom [IMPact] DK17 2.2.zip
ADB - Device not detected
4G - Worked
Market Update - Worked
Zipped Apps - Not listed in market
Market Update 2 - Worked
ADB x2 - Device not detected
WiFi - Worked
adbWireless - Worked
ODIN - Worked
Click to expand...
Click to collapse
Your kidding right? Well for starters, if you want a Froyo build/ROM to work right, first thing you gotta do is flash DI18 FULL ROM using Odin, then re-install clockworkmod, then flash (if your goin to a DK17 ROM ) the DK17 modem, and pit. Then you boot into cwm and wipe/factory reset 3 times, then wipe cache 3 times, then factory reset once more, then wipe Dalvik, then flash DK17 ROM, let phone boot all the way until your media scanner stopes (usually about a minute or two ). Then power back off, then boot back into clockworkmod, and wipe data 3 times, then wipe cache 3 times, then wipe data once more, but this time, dont wipe Dalvik. Then re-flash DK17 ROM and let it boot all the way. And ONLY then, will you have a fully working phone with DK17. If your not wiping cache before every MOD you install, you got problems. If you restore data after install of DK17 ROM, you will prolly get problems.
Im not saying that this will GUARENTEE that you will not have any problems, but I am saying that THIS method has treated me WELL over the past year or so. If you are doing ANYTHING differently, then how do I, or any of the DEV's here, take what your saying, to be fact, meaning that their ROM's are defective? Or somethings wrong with their ROM??? Im not saying your lying, all im saying is perhaps you did/doing something wrong.... you can chew on that a while, lol..
Dameon87 said:
For one; For adb to work, USB Debugging must be turned on. (And no it is not on in every ROM by default)
Click to expand...
Click to collapse
We learn something new everyday. This was something I did not know/realize. My guess is that up until now the ROMs I had downloaded had USB Debugging on my default and so I had not connected those dots.
I had posted earlier that ADB had not been working for me with the DK17 ROMs and no one had responded that I needed to check if USB Debugging was turned on.
I now know that and will act accordingly.
Dameon87 said:
What the hell are zipped apps?
Click to expand...
Click to collapse
I placed a number of apps that I prefer to use into a Zip file, similar to the ROM files being provided, but only apps. Signed the zip, and then used clockwork to install those apps, saving me the time of downloading and installing all of them.
art3mis-nyc said:
Well first thing wrong is that this isn't a rom by normal standards, its an Odin flash sort like the official Releases and what you get on your phone natively.
Secondarly it's also using the same "rom" flashable as the ACS dk17 that k0nane made. Second thing wrong is there is no way to install this via clockwork.
Therefore it's not a rom, it's a stock as sprint wouldnt have given it to you more or less and shouldn't be treated as a rom but as a recovery point.
Nothing overtly special has been done with this Flash or with the ACS k0nane flashable. so therefore there is nothing to fix.
Figured i'd make this point as everyone seems to see something new on the forums and go ooo new wrong works great except....
Perhaps understanding what they are would be a touch more helpful than a biased self comparision, seeing as how i could do the exact same test and get different results because my phones is different(ie it doesnt suffer the gps bug a fair amount do)
but it is what it is....
Take it with a grain of salt and understand that your mileage may very.
PS: the market not seeing apps is a simple fixable thing that's searchable in the forum, while it can be corrected quite easily, it's not a flaw that it's missing, these are BETA not for public distro leaks.
Click to expand...
Click to collapse
True that!!!
PokrTom said:
We learn something new everyday. This was something I did not know/realize. My guess is that up until now the ROMs I had downloaded had USB Debugging on my default and so I had not connected those dots.
I had posted earlier that ADB had not been working for me with the DK17 ROMs and no one had responded that I needed to check if USB Debugging was turned on.
I now know that and will act accordingly.
I placed a number of apps that I prefer to use into a Zip file, similar to the ROM files being provided, but only apps. Signed the zip, and then used clockwork to install those apps, saving me the time of downloading and installing all of them.
Click to expand...
Click to collapse
If those aren't working; then you likely didn't make the zip properly. You have to have an update-script add the files either to /data/app or system/app respectively.
They also have to be in a proper format: example:
./
./META-INF
./META-INF/folders under it
./system
./system/app
./data
./data/app
And of course a properly made update-script (Copying the files to the proper directories.)
sniperkill said:
Your kidding right? Well for starters, if you want a Froyo build/ROM to work right, first thing you gotta do is flash DI18 FULL ROM using Odin, then re-install clockworkmod, then flash (if your goin to a DK17 ROM ) the DK17 modem, and pit. Then you boot into cwm and wipe/factory reset 3 times, then wipe cache 3 times, then factory reset once more, then wipe Dalvik, then flash DK17 ROM, let phone boot all the way until your media scanner stopes (usually about a minute or two ). Then power back off, then boot back into clockworkmod, and wipe data 3 times, then wipe cache 3 times, then wipe data once more, but this time, dont wipe Dalvik. Then re-flash DK17 ROM and let it boot all the way. And ONLY then, will you have a fully working phone with DK17. If your not wiping cache before every MOD you install, you got problems. If you restore data after install of DK17 ROM, you will prolly get problems.
Click to expand...
Click to collapse
Live and learn. I did post the process that I used, which did not involve all of the steps you listed above. I will follw what you recommend in the future.
sniperkill said:
Im not saying that this will GUARENTEE that you will not have any problems, but I am saying that THIS method has treated me WELL over the past year or so. If you are doing ANYTHING differently, then how do I, or any of the DEV's here, take what your saying, to be fact, meaning that their ROM's are defective? Or somethings wrong with their ROM??? Im not saying your lying, all im saying is perhaps you did/doing something wrong.... you can chew on that a while, lol..
Click to expand...
Click to collapse
Understood, which was why I listed the process I followed, that way some of what I did was there and may have shown where I may have made a mistake. Which has been pointed out to me earlier regarding turning on USB debugging. I do not expect any developer to take what I post to be a statement that their ROM is broken. I never said that anyones ROM was broken, I started the post saying that I thought the developers might want to know what one user was experiencing. I know that it could be something I did.
Dameon87 said:
If those aren't working; then you likely didn't make the zip properly. You have to have an update-script add the files either to /data/app or system/app respectively.
Click to expand...
Click to collapse
I am using an update-script and the applications themselves are being installed and are working, they just don't show up in the market as installed. Something that there must be a fix for since sniperkill referenced searching the forums for the fix, so I will do that and will hopefully find it.
PokrTom said:
Live and learn. I did post the process that I used, which did not involve all of the steps you listed above. I will follw what you recommend in the future.
Understood, which was why I listed the process I followed, that way some of what I did was there and may have shown where I may have made a mistake. Which has been pointed out to me earlier regarding turning on USB debugging. I do not expect any developer to take what I post to be a statement that their ROM is broken. I never said that anyones ROM was broken, I started the post saying that I thought the developers might want to know what one user was experiencing. I know that it could be something I did.
I am using an update-script and the applications themselves are being installed and are working, they just don't show up in the market as installed. Something that there must be a fix for since sniperkill referenced searching the forums for the fix, so I will do that and will hopefully find it.
Click to expand...
Click to collapse
Oh. That is because when installed from the market, the market sets information in the database that says it is installed. This likely will not be fixable by using a zip to flash a bunch of apps. I believe what sniper was referring to was market apps now showing up because of the fingerprint in the build.prop.
Dameon87 said:
Oh. That is because when installed from the market, the market sets information in the database that says it is installed. This likely will not be fixable by using a zip to flash a bunch of apps.
Click to expand...
Click to collapse
I looked for the apps installed via the ZIP because when I did the same think using the Syndicate ROM on 2.1 all of the apps installed via the zip file did show up in the market, so I had been looking for the same thing.
It was worth a try, I have 4 Android phones in the household (My Epic & 3 Heroes) and so I was looking for any way to make reinstalling apps easier.
Thanks to all who answered questions or pointed out where I made mistakes.
k0nane said:
This.
And keep in mind that stock builds don't turn USB Debugging on by default.
Click to expand...
Click to collapse
I'm runing the ACS buildand USB debugging is definitely not on by default. After I enabled it ADB works fine.
Good stuff though! Thanks for the useful info!
Sent from my SPH-D700 using Tapatalk
it will be in next build
pokrtom, thanks for the informative post its always good to see people giving feedback that isnt "zomg dis is teh suxz you broke wifis!!!" 950 times over.
This is the first time Ive seen someone else notice the 4g sleeping issue. I thought I was imagining it.
Any clues on what could cause it?
sniperkill said:
Your kidding right? Well for starters, if you want a Froyo build/ROM to work right, first thing you gotta do is flash DI18 FULL ROM using Odin, then re-install clockworkmod, then flash (if your goin to a DK17 ROM ) the DK17 modem, and pit.
Click to expand...
Click to collapse
If you're going to try and bash someone atleast do it right. If you're going to be flashing the dk17 modem then why the hell would you flash the di18 first? All the dk17 modem does is overwrite... so ummm nothing stays behind which means.. un-needed step. Anyways..
Why don't you people stop being assholes. He's merely trying to help out the community with his testing efforts.. yea maybe he did a few things wrong but he's new.. we all were in the same boat.
Give the new people a chance; the ones who arnt meant to be fall through the cracks.. whilst the others stand by and prosper..
agreed. although i might also say that going from rom to rom, i have noticed that i have needed to uninstall the epic drivers and reinstall them to get them to notice my phone. this is on my win7 bootcamp on my mac.
that being said, you might also do a little bit of searching and throw some other general errors in the mix, that way we can be sure and document what is a "rom" bug or a "froyo" bug. that way some of the developers will ease off your back a little bit.
for example, i havent been using sniperkills 30 step "getcha rom runnin right" method, just a simple 3f salute, wipex3, install zip, restore apps from mybackup pro (still have never gotten titanium backup working correctly on my epic) and voila call it quits. but i have noticed a constant keyboard wake every 5-10 seconds with the keyboard slid out. this is on every rom ive tried so im thinking its a froyo problem and less of a specific problem.
just saying, lets make this a project and not a "dear developer. your rom blows. love the community."
Hi fellow streak users. Hopefully I'm asking questions in the right place.
Background:
I have read a fair amount of threads on upgrading the streak. I had 1.6, GUASBA111100 (build 6267? from memory), and received the dell 2.2 update notification. Downloaded the update and selected it when it downloaded. The phone re-booted, then sat at a black screen. There it sat for many hours. I tried re-downloading the update many times, but it does the same thing.
I got sick of this and started digging on the web. A simple method seemed to be to rename the file Update.pkg and put it on the root of the sdcard. It then sits at the dell logo. Forever. I have downloaded more images, roms, recoveries than I want to admit. I have attempted following fastboot instructions. They all fail on the reboot.
Currently the phone will not start up at all. Is it really possible to brick the phone?
What I'm trying to do.
Given all the bad publicity I have read about the current 2.2 from dell, I am hoping to install steve's latest version. I am hoping someone has some time and patience to explain how to do this. (commands and which files to use) (as the phone does not seem to respond to all the methods flooding multiple forums).
If you need further information, please ask.
Try flashing the stock recovery for the 1.6 build you have then it should boot as normal. Make sure all the other versions you have are not in the "fastboot" c:/ folder.
OK, here's the update. It's a bit jumbled and random, but I have been up for at least 18 hours fiddling...
I was unable to find the stock recovery for the 1.6 build I had. Probably lots of mismatched files were flashed unnecessarily. Nothing would touch the 'carrier unlocked US version' I had. That is until I tried QDL tool upgrade M 2.7.4.8 Now I suspect it is a beta version of 2.2 that it puts on the phone. It's slow and featureless. But it was the only thing that worked. From there I managed to make clockwork recovery work, and worked my way from steve's 1.4.6 to 1.5.1 to 1.5.2 Somewhere here the phone chucked a spaz and I discovered my phone had been booted off the network (showed no signal coverage). I began to suspect something to do with the imei being blocked (Another streak I was playing with is locked to O2, but came with a rebelsim installed - apparently illegal in australia). I checked the IMEI and it had mysteriously changed. (I suspect it had somehow been put to all zeroes, and something somewhere had given it a 'different' one.) Anyway, I used the QDL tool again, and the original one came back.
Finally what worked for me: QDL tool to flash 2.2, flashthe new amss.mbn, flash clockwork recovery, put steves 1.4.6 on SDcard and flash, then flash 1.5.3
(I couldn't tell you where I downloaded the files that worked. Your results (people who are still seeking action to try and upgrade their software) may vary. All I can say is that now I have downloaded half the internet and installed all the computer drivers, I have hit on a combination that works for me on this computer).
Steve, Thankyou! It's fast, snappy. It has those settings I love to twiddle.
Thank you to everyone else that has either directly or indirectly helped me with your description of how you got yours working.
Thank you for the hosting of the ROMS. I like that you don't have to wait 45 seconds and/or join to download.
A few comments:
I downloaded so many roms and files that it wasn't funny. The problem is that they are all named Update.zip, amss.mbn etc. When they are all in the download folder... Some people just provided the files, others packaged them with a batch file to automate the process. If I was to download them all again, I would download them into folders labelling them...
There seems to be a wide variety of situations/variables that dictate 'what you need to do and how you need to do it' to change roms in the phone. There are half a dozen comprehensive guides on the net, yet all different. I was quite confused. It almost needs some sort of chart where you can pick where you are at the moment, where you want to be, then follow those instructions.
I was also bamboozled with the different tools. QDL, flashboot, ADB etc. I have a bit of an idea, but I'm sure others are equally confused. I know the information is 'out there' but to have it all in one place. What do some of the files do. Why might you need to flash them. Which files are erased by the stock ROM if you don't do anything with them. What does it do when you flash a recovery? How long does it stay on the phone?
There are several parts of the phone that get upgraded. Not sure I have it right, but QDLtool upgrades the modem software (amongst other things) Other things you change is the baseband, SDcard contents etc. (Trying to connect what software files go to what places to what hardware in the phone.)
I do have several questions that have arisen.
1. Am I right in thinking you must flash steves 1.4.6 before you can flash the latest 1.5.3?
2. QDLtools: In theory is it possible to replace the files somehow so it puts steve's latest ROM straight on?
3. Rebelsim: (The small amount of information I have suggests it is illegal in australia) Does it block or change the imei? Can the carrier tell if you are using one?? (not that I use one, apparently they don't work on 2.2)
(that's all for the moment.)
i have been having problems with doing my streak aswell and still am but
ato answer one of your questions that i found out while downloading the whole internet is that the QDL tool can be used to put steves on
here is the instructions i just copied off the qdl page i would of posted a link but i am a new member so i cant post inks yet
Beyond QDLTool
Using QDLTool will get you to a pre-release of v2.2. From here, you’ll want to upgrade to a newer release. The two options that people tend to choose from are to either go up to the official v2.2 ROM from Dell, or install DJ_Steve’s latest ROM.
Official ROM
If you want to go to the latest official ROM from Dell, simply set up your wifi connection, then go to Settings -> About Phone -> System updates. The latest update can then be downloaded and installed, updating your Streak.
Latest Streakdroid ROM
If you want to upgrade to the latest Streakdroid ROM (1.5.3), either from the QDLTool install or from the latest official build, you can follow these steps:
1.Go to the downloads section and grab StreakMod Recovery, the latest 1.5.3 Update and the AMSS for 1.5.1+ (the update and amss are under Roms, StreakMod Recovery is under Recovery)
2.Copy the update-1.5.3.zip file onto the root of your SD card.
3.Extract recovery.img from the StreakMod recovery and place it, along with amss.mbn, into the same directory as QDLTool (QDLTool has a copy of fastboot)
4.Shut down your Streak, then hold down the camera button (all the way) as you turn it back on.
5.The screen should turn white; press ‘Fastboot’ in the top right hand of the screen.
6.Plug in the USB cable – the Streak should now display ‘FASTBOOT_MODE’ at the bottom of the screen.
7.Open a command window and use ‘cd’ to change to the same directory as qdltool.
8.Run: fastboot -i 0x413c flash recovery recovery.img
9.Run: fastboot -i 0x413c flash amss amss.mbn
10.Run: fastboot -i 0x413c reboot
11.As the Streak starts to reboot, hold down both volume buttons.
12.The recovery menu should come up; select option 2 (Upgrade)
13.A Dell logo and an exclamation mark should appear; press power or menu to open StreakMod’s main menu
14.Select ‘apply sdcard:update.zip’ then ‘chose zip on sd card’
15.Find the update-1.5.3.zip file, select it and apply the zip.
16.When the update finishes, press back a couple of times then select the option to reboot your Streak.
17.The Streak will restart. It will take about 5 minutes to complete, but you are now on the latest v1.5.3
at moment i am following the qdl guide to getting the steve rom on my phone so will let you know how it has gone but with that guide the installation at moment seemed seemless now got to see if it goes off the dell logo after a while if not got to recovery but lets hope
no luck so far
stuck on the logo screen but asked for help now its a waiting game
Cheers for that!
Sent from my Dell Streak using XDA App
Is it necessary to use QDLTool to get to the pre-release 2.2 if I am on 1.6 or can I just follow steps 1-17?
The reason I ask is that QDLTool for me just stops at "Check version ... " so I have not been able to complete running it.
i dont know if it is necessary
are all the drivers installed?
i used to have a prob where it kept failing me but all i had to do was change usb port
and got it working but i was running 2.1 stock at the time but that was buggy and crap UI
have you tried just puting 2.1 or 2.2 on your SD card and updating that way
i finally got my streak sorted
i started from scratch
first i installed clockwork mod using fastboot
then installed very version of steves roms in order starting with 1.1.1
and worked my way down and when i installed 1.5.0 i then ran flashed the amss that is required if you want to get the newer versions then installed the rest of the updates and when i got to 1.5.3 i also installed the camera fix
i found it best to put all steves rom zip files onto your SD card at once then it saves having to keep putting one of after another
also after every update leave the phone for a few mins because it does take a lil time to sort the updates out
THE ROM UPDATES (at top also has the AMSS that need flashing)
http://streakdroid.com/?page_id=15&category=1
Camera fix and the comandlines for the AMSS update
http://forum.xda-developers.com/showthread.php?t=802405
clockwork
http://streakdroid.com/?page_id=15&did=9
I don't know if all the drivers are installed. Is there a way to check? I cannot even get into FASTBOOT (POWER + CAMERA) mode and the Streak is just in an infinite reset loop.
Just a note, the older StreakFlash QDLTool completes completely but the newer one in Repairtool just sits infinitely at "Check Version ... "
what operating system you using on your computer
rahbone said:
what operating system you using on your computer
Click to expand...
Click to collapse
Nice of you to ask, as indirectly that was the issue. I outlined it over at the forum mydellmini dot com. Sorry, cannot post hyperlinks as yet. Issue has been resolved. Looking now to load 1.5.3
why not spam a few more posts on here then u can do links when u want 2 in future
you just need 3 more posts i believe the you can do links
- I have a r800i on 2.3.2 rooted and some bloatware removed.
- My goal is to update to 2.3.3 (which i am having problems).
- I dont care if i lose root access or not.
1) I tried an OTA update but after downloading everything, the phone rebooted and simply displayed a message "Cant update".
2) Then i tried flashing to a uk generic firmware following the instructions from this thread http://forum.xda-developers.com/showthread.php?t=1116090
However when i try to flash i get told to turn the phone off, turn it back on holding the back button. However this doesnt work as i get an error message telling me to install the correct s1boot driver.
3) Then i tried downloading PC Companion and updating this way. When i am in mass storage mode the installed proceeds to update, but then it tells me to go into media storage mode, at which point the software fails to recognised my phone and stops the update.
I cant update to 2.3.3 at this point and dont know how to proceed.
Any ideas would be appreciated.
Found solution -
I found the best way to overide all settings, root, PC Companion etc and just get a complete fresh 2.3.3 install.
SE provide the tools for this here -
http://www.sonyericsson.com/cws/sup...etailed/updateservice/xperia-play?cc=gb&lc=en
It provides a direct way to update your phone and reset to factoy settings if you wish. Also installs all bloatware etc too btw.
You do lose root access though, but not your user settings (unless you want a factory reset).
I doubt i will bother to root the phone for a while, not much benefit imho. Hopefully the dev scene isnt dead for the Play and we will have some proper custom roms released soon.
Hi,
Even if you are 2.3.3 now.
Use the latest version of flash tool. Open the drivers folder and install the only executable there. Download 2.3.2 UK generic .184. Save it to the firmwares folder.
Click root, unplug usb, press and hold back button, reinsert the usb.
When it starts flashing remove hold on back button.
Then gingerbreak. Then update your apn setting. (can useally be sent by your provder from their website) Then over the air update. Job done.
Sent from my R800i using XDA Premium App
nelly_boy said:
Hi,
Even if you are 2.3.3 now.
Use the latest version of flash tool. Open the drivers folder and install the only executable there. Download 2.3.2 UK generic .184. Save it to the firmwares folder.
Click root, unplug usb, press and hold back button, reinsert the usb.
When it starts flashing remove hold on back button.
Then gingerbreak. Then update your apn setting. (can useally be sent by your provder from their website) Then over the air update. Job done.
Sent from my R800i using XDA Premium App
Click to expand...
Click to collapse
Im going to leave it unrooted for a while, phone runs great with 2.3.3 for me even with bloatware.
Ill root and upgrade to custom rom when and if there is a decent release.
Just wanted to say thanks for the instructions though.
Do you have an unlocked bootloader? If so NEVER do an ota update, it has bricked quite some phones!
svenk919 said:
Do you have an unlocked bootloader? If so NEVER do an ota update, it has bricked quite some phones!
Click to expand...
Click to collapse
No. Thanks for pointing this out though. My first and only root was done with gingerbreak.
I had a similar problem in W7 - turns out I had to download the SE Update utility (NOT the PC Companion Utility) and install it. Then, once I set my phone into update mode (hold Back button and plug in USB cable) it properly installed the drivers.
Once I'd done that, I could then use Flashtool to flash the UK firmware to my Canadian Rogers Xperia.
So if you plug in and have the green light, but get a driver error from windows, try finding the update utility on the Sony Ericsson website and installing it. Good luck!
Hey guys, first I want to gives props to those of you who have posted tutorials on tweaking/modding this phone. I am an AT&T customer so I have an X10a, but with your help I successfully flashed my phone to 2.1, debranded it and rooted it. Of course AT&T released their official 2.1 update just a week later but like now, I was tired of waiting. So I now have an X10i, debranded and rooted, running customization# 1232-9897, for which there is no official GB release for just yet.
I want GB now! So am I right in assuming that my only option at this point is to flash a custom rom (WB)? I have been reading up on how to do so and it doesn't look nearly as easy as it was to flash to 2.1 from 1.6, debrand and root. Not only that but the tutorials on how to do so aren't exactly noob friendly. So this is what I've gotten so far.
1. In order to install WB 2.3.3 I need to be on a stock 2.1 rom, rooted w/xRecovery.
a.) I'm good on the first 2 but don't have xRecovery (I don't see an icon for it, at least, in my apps menu). Do I need to flash the rom again or can I just install it as shown in this video?....sorry, can't post the video, not enough posts yet. I'll update it shortly.....the video was made by username BluechipJ on youtube.
2. When making a backup of my apps/data, I use MyBackup Root, and for backup type I chose APK. Is that ok?
3. agentJBM wrote the tutorial I followed to upgrade to 2.1/debrand and root my phone, his guide was super detailed for noobs like me. Is there a guide out there that walks noobs through the process of going from 2.1 to 2.3?
Download flashtool 0.2.9. from there you can root and install xrecovery but just make sure you have unknown sources and usb debugging checked in phone settings
You don't access xRecovery from your app drawer (your "apps menu"). You can check if you have it by turning off your phone, turning it back on again, then when you see the white "Sony Ericsson" text repeatedly hit the 'Back' button on your phone (the right most button from the 3 at the bottom of your phone). If you come to a menu which says up the top "xRecovery" with Zdzihu's infamous android-troll face picture, then you have it. If not, then you can easily install it via FlashTool.
From then on, just follow the guides, they are actually pretty simple.
Simply use one of the 2.3.3 stock ftf files and flash it the same way you would a regular 2.1 file unless you want a modded rom like that of WB.
Im on at and t also and I know it sucks. But yeah just use flashtool and flash one of the firmwares. Should be just as easy as 2.1
Sent from my x10 on official gingerbread http://www.youtube.com/watch?v=mh19PLNTWwk&feature=youtube_gdata_player
JohnShade123 said:
Download flashtool 0.2.9. from there you can root and install xrecovery but just make sure you have unknown sources and usb debugging checked in phone settings
Click to expand...
Click to collapse
I downloaded it and unzipped it to my desktop thinking it would just be a single file, turned out to be a few folders and what not....I'm assuming I should unzip it to it's own folder??? Since i'm already rooted, can I just install xRecovery from it? Unknown sources and usb debugging are checked.
Mayazcherquoi said:
You don't access xRecovery from your app drawer (your "apps menu"). You can check if you have it by turning off your phone, turning it back on again, then when you see the white "Sony Ericsson" text repeatedly hit the 'Back' button on your phone (the right most button from the 3 at the bottom of your phone). If you come to a menu which says up the top "xRecovery" with Zdzihu's infamous android-troll face picture, then you have it. If not, then you can easily install it via FlashTool.
From then on, just follow the guides, they are actually pretty simple.
Click to expand...
Click to collapse
Durr....So glad I made this thread I tried that, didn't get that menu or picture, it just booted up as normal and I kept pressing the back button repeatedly from the time the white SE logo came up until my homescreen came on. How do I install it from FlashTool?
Dark Nightmare said:
Simply use one of the 2.3.3 stock ftf files and flash it the same way you would a regular 2.1 file unless you want a modded rom like that of WB.
Click to expand...
Click to collapse
So I could use any one of the stock 2.3.3 roms? Even though they were for other countries? I'd actually prefer a WB 2.3.3 since it's tweaked and what not already.
Lion3494 said:
Im on at and t also and I know it sucks. But yeah just use flashtool and flash one of the firmwares. Should be just as easy as 2.1
Sent from my x10 on official gingerbread
Click to expand...
Click to collapse
Is that what you did? Which firmware did you use?
916x10 said:
I downloaded it and unzipped it to my desktop thinking it would just be a single file, turned out to be a few folders and what not....I'm assuming I should unzip it to it's own folder??? Since i'm already rooted, can I just install xRecovery from it? Unknown sources and usb debugging are checked.
Durr....So glad I made this thread I tried that, didn't get that menu or picture, it just booted up as normal and I kept pressing the back button repeatedly from the time the white SE logo came up until my homescreen came on. How do I install it from FlashTool?
So I could use any one of the stock 2.3.3 roms? Even though they were for other countries? I'd actually prefer a WB 2.3.3 since it's tweaked and what not already.
Is that what you did? Which firmware did you use?
Click to expand...
Click to collapse
I just used the 1237 update. But all of the firmwares work fine for me. I tried 3 so far
Sent from my x10 on official gingerbread http://www.youtube.com/watch?v=mh19PLNTWwk&feature=youtube_gdata_player
916x10 said:
I downloaded it and unzipped it to my desktop thinking it would just be a single file, turned out to be a few folders and what not....I'm assuming I should unzip it to it's own folder??? Since i'm already rooted, can I just install xRecovery from it? Unknown sources and usb debugging are checked.
Durr....So glad I made this thread I tried that, didn't get that menu or picture, it just booted up as normal and I kept pressing the back button repeatedly from the time the white SE logo came up until my homescreen came on. How do I install it from FlashTool?
So I could use any one of the stock 2.3.3 roms? Even though they were for other countries? I'd actually prefer a WB 2.3.3 since it's tweaked and what not already.
Is that what you did? Which firmware did you use?
Click to expand...
Click to collapse
Once you unzip flashtool to your computer
*Run the flashbat to start flashtool
*Then plug in your phone to the computer and click on "charge phone" (on phone)
*then click on "ask permission" at top of flashtool window
*on your phone click on "allow" (once superuser asks you for permission)
*then you'll be able to click on "xrecovery" at top of flashtool window
that will install xrecovery
Then if you want to install Ericks 2.3.3 custom ROM you can follow this guide
links to Ericks ROM is here http://forum.xda-developers.com/showthread.php?t=1192326
or you can install Wolfs custom ROM basically the same way but with his links instead of Ericks
It's very easy once your phone is rooted and has busybox/xrecovery
Hello guys.
I have purchased U8800 pro two days ago and decided to do some modding here
The phone came with 2.2.2. I managed to root it with SuperOneClick 2.3.
After that I installed CWM 5.0.27 and tried some ICS roms.I liked aurora but I had one problem.When the screen switched off,the phone would reboot after 2,3 seconds....
I recovered via CWM to 2.2.2 and installed the official 2.3.5 rom (build 540g).
I installed 2.3.5 because I have read here in the forums that this rebooting was done because I went straight from 2.2.2 to 4.0.3(don't know if it's true,i'm completely noob).
Anyway,I tried rooting my phone now with 2.3.5 but I can't.
I tried with SuperOneClick(2.2 and 2.3,setted the exploited both to auto and zergRush),with doomlord tool but yet no success.SuperOneClick gets stuck at step 7 and then is says not responding.DoomLord Tool outputs a lot of errors that I don't have permission to write in the filesystem and stuff.
I run both programs with Windows 7 64bit and by right click and run as admin.
Still no success.Tried to restore to factory defaults (with 2.3.5 still there) but yet again the programs don't work).
Of course i have enabled usb debugging,turned log switch one,dump & log turned all on options,enabled non market applications to install....the usual stuff I found in the guides here but still I can't root it.
Also the pink screen no longer works.With 2.2.2 I was able to replace the recovery img and get CWM,but after 2.3.5 the computer no longer finds the phone when in pink screen mode.I also tried all of the above in a laptop with windows 7 64bit.
All drivers installed and updated according to device manager.
Well guys? What can I do? Is is a good idea to try to revert back to 2.2.2 and root from there? I really want my U8800 Pro to have an ICS
Anyway,sorry for the long post.
Hope you can help me.Thanks in advance!
Hi,
I think you flashed the B540 ROM. Flash B512 (yes, you can downgrade; there's no block) and you'll be able to use the pink screen mode (and zergRush will also work)
EDIT: Glad to hear it worked!
Do I follow the same procedure as the one I followed to upgrade to 2.3 from 2.2?
(the step 1,step 2 folders ->dload folder in internal sd with update.app and update_g.app etc etc)?
edit: it seems that the procedure is the same.downgrading right now and I will post the results
edit2: You are the best qwerty12!!!
Thank you very very very much sir!!!!!!!!!!!!! You are awesome! I finally rooted my phone with superoneclick 2.3 and zergRush exploit selected.
Thanks again!