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."
[TELUS FASCINATE USERS] Hello XDA and community. I've compiled a complete walkthrough to install either i9000 or vibrant custom roms onto a telus T959D fascinate. Follow these instructions to have relatively the same STABLE setup im using at the moment
I AM NOT ACCOUNTABLE IF U BRICK YOUR PHONE!!! PLEASE FOLLOW CAREFULLY!! I MADE SURE I MENTIONED EVERY SINGLE BIT OF INFORMATION SO YOU COULD FOLLOW ALONG, NOT THINK YOU KNOW WHAT YOUR DOING THEN TRY WITHOUT FOLLOWING THE INSTRUCTIONS LIKE MY DAD PUTTING TOGETHER A COMPUTER DESK!!! THIS IS A EXPENSIVE PIECE OF HARDWARE SO FOLLOW MY EXACT STEPS!!!!!
The only 2 known issues ive had personally were
-no home button just 2 back buttons for the time being
-phone model specific apps for the T959D wont download from the market because you will be using a i9000 kernel to mimic the i9000 system
THE ONLY REQUIREMENTS ARE TO MAKE SURE YOUR BATTERY IS FULLY CHARGED AND YOU HAVE DOWNLOADED AND INSTALLED THE SAMSUNG USB DRIVERS
http://www.samsung.com/ca/consumer/...TLS/index.idx?pagetype=prd_detail&tab=support
I've Added a video of my current setup.. i was going to do a video showcasing the installation but i really dont want to redownload all my apps. far too time consuming.
STEP ONE - Download and reflash froyo 2.2 1st thing were gonna do is reflash stock 2.2. i know most of u r already on stock 2.2 but a fellow tester by the name of roccos_van said he was having market issues. So i wanna be 100% careful. So lets flash to stock. TO start, download the omega 2.2 leak here: http://www.megaupload.com/?d=C3DQ1LZF
the leak comes with odin and all files needed to flash back to 2.2 stock. Once the download is complete, unzip the file to somewhere your familiar with ie. desktop or my documents. The files name will b T959TJL3. inside this file, youll find odin and 3 files. Right click odin and click start as administrator. Odin has a fairly simple setup. the thing u wanna do in odin is place the files from the
T959TJL3 folder into the proper catagories. Heres a screenshot of what it should look like when its properly setup
once your odin looks EXACTLY THE SAME, its time to put your phone into download mode.
Turn off your phone and wait for it too completely power down. once its completely off, pull your battery. SGS phones come with a hidden mode called download mode which is what the phone goes into when you recieve a OTA update. to manually put your phone into download mode, follow these instructions
MAKE SURE YOU USE THE SAMSUNG CABLE THAT CAME WITH YOUR PHONE!!
make sure u have your samsung usb cable plugged into the pc but not into the phone (not yet at least) and make sure u remove your battery.
step 1. hold down the volume down button and continue holding
step 2. whille still holding down the volume down button, plug your phone into the usb cable
step 3. while still holding down the volume down button, pop your battery in.
Your phone should show this screen
Now if u look at odin you will have a yellow stripe on the top left area as seen in this picture
Now your ready to flash to stock 2.2. In odin, click start. It will then begin flashing the stock firmware into the phone.
It will look something like this
After afew minutes, it will reset your phone and odin will look like this but will say reset instead of pass
let your phone sit for while untill odin looks like this
once it says pass, your officially back to stock 2.2. CONGRATZ!!! step1 complete!
Now onto the i9000 kernel
STEP 2 - DOWNLOAD AND INSTALL CUSTOM VOODOO i9000 KERNEL
1st off, download the custom kernel here
http://rapidshare.com/#!download|30...stable-5.0.1-Froyo-GT-I9000-odin-pda.tar|6461
This kernel has clockwork recovery enabled which allows you to flash new roms, make backups, etc.
once the file is done downloading, reopen odin and place the file in to PDA section and do nothing else!!
Put your phone back into download mode following the steps above until your ready to flash. Once your ready to go, click start. It will only take like 10 seconds this time around since your only flashing a kernel.
When your phone resets, it will say 959d then quickly change to i9000 and then it will begin to talk to you! lmao. dont fret, its supposed todo this. its installing the voodoo lagfix in your phone. this will take approx 5-10 minutes. once your phone is up and running, let it sit for about 5 minutes so it can finish installing the lagfix. Once your phone is up and running again, power it down. Wait for it to be completely off, then we are going to get into recovery mode.
To get into recovery mode, hold down both volume buttons and hold power. Continue holding these 3 buttons until your phone loads the i9000 bootscreen for the 2nd time then release.
You should b in a screen resembling this but yours will be red
To navigate recovery, you must use the volume buttons for up and down and power for enter.
From the main menu, go down to lagfix and click enter.
in this menu, u can enable or diasble the voodoo lagfix. Since we want to flash a new rom, WE MUST TURN OFF VOODOO!!!
YOU MUST ALWAYS TURN OFF VOODOO BEFORE FLASHING ANYTHING OR YOU CAN POTENTIALLY BRICK YOUR PHONE!!!
once youve clicked disable lagfix, disable system lagfix and disable debug lagfix, go back to the main menu then click reboot.Againm, it will take like 5-10 minutes to completely disable the lagfix. Once its completely done disabling the lagfix, your phone will load. You wont have signal to telus quite yet, but we will get to that. From this point, u can choose what u want to do.
U have 3 options
1. Install a vibrant rom
2. Install a i9000 rom or
3. Flash The telus modem and stay stock
But since this is a tutorial on how to get a custom rom up and running, ill choose a rom. On to step 3!
STEP 3 - CHOOSING AND FLASHING A CUSTOM ROM
If u want my opinion, if u choose vibrant rom, choose Nero v5
Nero v.5: http://www.teamwhiskey.com/DownVibrant.html
If u choose a i9000 rom, id say darkys v8.1.
Darkys v8.1: http://www.multiupload.com/SHPR3TXLYB
Either choice you make, download the file to a familiar place on your computer.
On your phone, goto Settings > Applications > Development and turn on USB debugging.
Once the download is complete, connect your phone to your computer. Once your phones signals it knows its connected to the computer, pull down your notification bar and click USB CONNECTED. This will open up the Mass storage. Then click enable usb storage.
Now your computer and phone are able to communicate and share files. click my computer then you should see your phone named removable storage. Open the device. Now you want to drag and drop the custom rom zip into the root of your internal storage. once its finished copying the zip, click close usb storage on your phone then unplug it once it says its ok. Now you have the custom rom on your phone but its not installed quite yet.
IF U CHOSE NERO v.5: NERO HAS A VIBRANT KERNEL PREINSTALLED WHICH WILL NOT ALLOW A TELUS FASCINATE TO CHARGE! IT WILL BOOTLOOP UNTIL U UNPLUG YOUR CHARGER. WE WILL B OVERWRITING THE VIBRANT KERNEL WITH A I9000 KERNEL FURTHER INTO THE TUTORIAL SO DONT START THINKING NEGATIVE! IT IS A SIDEAFFECT OF PORTING A VIBRANT KERNEL. ONCE WE HAVE THE ROM WORKING, WE WILL BE RE-ADDING ANOTHER I9000 CUSTOM KERNEL TO FIX THIS ISSUE. SO JUST CONTINUE WITH THE INSTALLATION
IF U CHOOSE DARKYS: NO ISSUES HERE BECAUSE IT IS A I9000 KERNEL. BUT I PERFER THE LOOK OF NERO V5 SO THE ADDED BULLS**T TO GET IT WORKING PROPERLY IS DEFINATELY WORTH IT!!
To install the custom rom you chose, follow these instructions:
1. Turn off phone and wait till its completely shutdown
2. Use the above mentioned 3 button combo to get into recovery
3. Once in recovery, click wipe data/factory reset. once it finshes, click wipe cache partition. Once it finishes, goto advanced then wipe dalvik cache.
4. After youve wiped everything, go back to the main menu and click install zip from SDcard. Then click choose zip. u should see your nero 5 - voodoo file. click it. it will ask if your sure. click yes. your rom will then proceed to install. you will see some wierd stuff but it will load perfectly. once its done, click reboot.
Because both Roms come with Voodoo enabled, you will have to sit and wait while voodoo reenables itself. once your rom is up and running, you probably still dont have a signal from telus and depending on which type of rom u chose, u may not be able to charge your battery. This is exactly y i said make sure your battery was fully charged. Im quite sure both of these roms come with enter recovery mode by holding your power button and it will say recovery. click that.
Once in recovery, your going to want to disable the lagfix, system lagfix and debuglagfix. Once youve disabled all of them, reboot. Again, it will take like 5 minutes to disable the lagfix. Once its done, shut down your phone entirely.
Now that the rom is installed, Step 3 is complete! Congratz! We are almost done!!
STEP 4 - OVERCLOCKED KERNEL & TELUS MODEM
The final steps to have your phone up and running is to flash a new advanced voodoo kernel that is overclocked and allows undervolting for better battery life (as well as fixes the charging bootloop issue on a vibrant rom) and reflashing the telus modem file so you can get signal again.
Click the following link and download this file:
voodoo.advanced.v666.2-20110111-21.53.tar
http://kernel.1ug.org/
Once the download is complete, reopen odin and place the voodoo.advanced.v666.2-20110111-21.53.tar in the pda file and thats it!!
get your phone into download mode and click start in odin. This will flash the stable kernel to your phone and allow you to overclock and undervolt. If u chose Nero v.5, plug your phone in for a charge, it deserves it Finally to get your telus signal back up and running.
Shut down your phone completely. Open odin (for the final time :0). You remember the T959TJL3 folder we used to first restore to stock froyo 2.2 in step 1 (also the folder odin is in)? Well what we want to do is take the file with the word "phone" in it and place it in the phone section and thats it thats all!! Get your phone back into download mode and click start in odin. this shouldnt take very long as your just exchaging the nero modem for the telus.
Once the flash is complete, BAAAMMMMMM BABYYYY!!!! custom roms!!!!! WITH WORKING DATA!!! ON A TELUS FASCINATE!!!
Now that your successfully running a custom rom, i suggest going back into recovery and re-enabling lagfix, system lagfix and debug lagfix then rebooting. After the reboot, i suggest re-opening recovery then going to backup and restore then clicking backup. This will create a system image of your freshly loaded rom so if u have issues down the line, u can easily restore back to your freshly loaded rom problem free. I THINK THIS IS DEFINATELTY A NECCESITY!!! BETTER SAFE THEN SORRY!!! IF NOT YOULL HAVE TO START FROM STOCK 2.2 ALL OVER AGAIN!!!
(OPTIONAL): HOW TO OVERCLOCK AND UNDERVOLT
Overclocking your phone is super easy considering once youve added the advanced voodoo kernel its automatically overclocked but you cant control it. I suggest going onto the market and purchasing SETCPU. Its pritty cheap, comes with a widget, and allows you to choose the max cpu speed (overclocked its 1.28ghz) and the minimum. I only overclock when im playing psx4droid v1.7 (final fantasy 9 runs mint) but usually keep my cpu set at 600mhz max 200mhz min while im doing my day to day to preserve battery life but also keep the speed.
SETCPU HAS ISSUES ON GALAXY S PHONES WITH THE SET TO BOOT OPTION AND SAVING PROFILES. DO NOT USE SET TO BOOT OR PROFILES!!! JUST CHANGE THE CPU SPEED MANUALLY WHEN YOU WANT TO CHANGE IT OR YOU COULD SERIOUSLY MESSUP YOUR PHONE
Undervolting is pritty easy also. just go checkout Xan`s app: voltage control v.3.
Heres a link to his thread and the the download link for the apk is at the bottom of his post:
http://forum.xda-developers.com/showthread.php?t=829731
Either download this file directly to your phone or download it to your computer then use usb storage to drag and drop the apk into the root of your internal sdcard. Close your usb storage and unplug phone. Open your custom roms file manager and find the apk. Click it. Use program installer to install it.
Once its installed open the app. Superuser will ask you if its allowed to allow voltage control to work. Click yes. You will then see a list of voltages etc.
1st thing you should do is change your scheduler to noop. Its the best scheduler in the app and easiest on your phone.
I`m going to paste stable undervolting values you should copy into your voltage control.
1280 = -25
1200 = -25
1120 = -25
1000 = -50
900 = -50
800 = -50
600 = -50
400 = -75
200 = -75
100 = -75
These settings have worked perfectly for me although you could try different settings. Once youve added the above values into voltage control, click the menu button and click apply now. then click menu again then apply now again (i heard it takes 2 times to actually go through). The values i put there are safe so if you followed those, open menu and click apply to boot, then menu then apply to boot. Your phone is now undervolted.
I just spent roughly 9 hours creating this post so if it has helped you in anyway possible, plz click thank you. I'd like to thank supercurio for creating voodoo, omega1 for creating my interest in custom roms with faded froyo, and roccos_van for testing what everyone else was afraid to test. Id also like to thank everyone reading this post. Plz click the thank you button
The market issue is fixed, it had nothing to do with your instructions, I have a bad imei and simply had to force stop a few market related apps, clear data and cache then reboot.
You should also update your post as user supercurio released a custom t959d kernel today with clockwork and voodoo.
Now we can flash roms for i9000 or t959 with no issues.
just my luck. spend 9 hours posting then supercurio posts a kernel.. lmao. o well. if your looking for a overclocked undervolted phone, follow this post
roccos_van said:
The market issue is fixed, it had nothing to do with your instructions, I have a bad imei and simply had to force stop a few market related apps, clear data and cache then reboot.
You should also update your post as user supercurio released a custom t959d kernel today with clockwork and voodoo.
Now we can flash roms for i9000 or t959 with no issues.
Click to expand...
Click to collapse
ill b updating my post to include instructions on flashing stock 2morop morning when i got some free time
EDIT: so i think my battery is finally syncedup properly. i have no task killers with the above setup. Charged my phone yesterday at 1pm. Its now 7:30am the next day and i have 51 percent left
You did a good job with the post.
I think when you add the supercurio modded stock kernel it will be fairly complete.
roccos_van said:
You did a good job with the post.
I think when you add the supercurio modded stock kernel it will be faily complete.
Click to expand...
Click to collapse
i was just in the shower with my phone playing music on the counter and it stopped playing. i jumpedout to see wtf was going on. the lockscreen just magically appeared saying sim card removed reboot phone. seems to be working now but fuk it. thats too messed up 4 me. imma re edit this thread to include the telus voodoo stock so no1 gets the same issues im hjaving. overclock undervolt or not, i hate glitches.
Im thinking ill return to stock and start from scratch. Should i make a video showing complete installation? i think so
LINKSLOVESANDROID said:
i was just in the shower with my phone playing music on the counter and it stopped playing. i jumpedout to see wtf was going on. the lockscreen just magically appeared saying sim card removed reboot phone. seems to be working now but fuk it. thats too messed up 4 me. imma re edit this thread to include the telus voodoo stock so no1 gets the same issues im hjaving. overclock undervolt or not, i hate glitches.
Im thinking ill return to stock and start from scratch. Should i make a video showing complete installation? i think so
Click to expand...
Click to collapse
Try the stock voodoo kernel first...i don't know if you should disable lag fix first but I would just in case.
roccos_van said:
The market issue is fixed, it had nothing to do with your instructions, I have a bad imei and simply had to force stop a few market related apps, clear data and cache then reboot.
You should also update your post as user supercurio released a custom t959d kernel today with clockwork and voodoo.
Now we can flash roms for i9000 or t959 with no issues.
Click to expand...
Click to collapse
Thanks for the tip, my market stopped working today, cleared data and cache, rebooted and now I'm back in action!
well headsup telus users. i flashed axura on my fascinate and it completely bricked my phone. wont turn on. no recovery no download mode. i tihnk im screwed
LINKSLOVESANDROID said:
well headsup telus users. i flashed axura on my fascinate and it completely bricked my phone. wont turn on. no recovery no download mode. i tihnk im screwed
Click to expand...
Click to collapse
Oh man...that sucks...did you disable voodoo before flashing? You have a one year warranty take it back.
LINKSLOVESANDROID said:
i was just in the shower with my phone playing music on the counter and it stopped playing. i jumpedout to see wtf was going on. the lockscreen just magically appeared saying sim card removed reboot phone. seems to be working now but fuk it. thats too messed up 4 me. imma re edit this thread to include the telus voodoo stock so no1 gets the same issues im hjaving. overclock undervolt or not, i hate glitches.
Im thinking ill return to stock and start from scratch. Should i make a video showing complete installation? i think so
Click to expand...
Click to collapse
roccos_van said:
Oh man...that sucks...did you disable voodoo before flashing? You have a one year warranty take it back.
Click to expand...
Click to collapse
i did disable voodoo. dunno y it bricked. i went to the future shop i got it from, lied and said i flashed official froyo from kies and it wouldnt start afterward. They checked my account. turns out i was 3 days late on my replacement policy fee so i have 2 wait 3 business days with a paper weight phone until it goes through b4 they can replace it for me. but on the brightside, my buddy who works the cell area said when i get my replacement, if the same thing happens he has to give me the telus phone of my choice. SOO. if the htc desire hd does come to telus, i can purposely brick my phone, say froyo did it, and get the desire hd for free. although i dont know much about htc, ive heard they r the best android brand around. u got any info on htc at all rocco? all i know is sense looks sexier then any rom ive seen thus far including every differenty model rom ive seen on youtube. imma post a new thread warning t959d users to beware on flashing roms until there propp[erly ported to our phone. cause as u can see in the above post, i know what i was doing. wasnt like i just fukedup and forgot something. i had nero v5 running with the supercurio stock voodoo kernel last night but it felt like it was hiccuping after i enabled the lagfix so i decided to go back to stock and try other roms. from what i heard, axura is the best of the best for vibrant roms. so i flashed to stock with odin. added the new kerne; thru odin, let the lagfix install, rebooted into recovery, disabled the lagifx, system lagfix and debug. rebooted. let the lagfix uninstall. copied the zip to my interna; sdcard, rebooted into recovery, wipe data, cache and dalvik then chose the zip. it installed properly. i clicked reboot phone then it turned off. and that was that. question is is there anyway to use slp to open your phone and try and reset it or is it bricked and am i without a phohe till next wednesday?
LINKSLOVESANDROID said:
i did disable voodoo. dunno y it bricked. i went to the future shop i got it from, lied and said i flashed official froyo from kies and it wouldnt start afterward. They checked my account. turns out i was 3 days late on my replacement policy fee so i have 2 wait 3 business days with a paper weight phone until it goes through b4 they can replace it for me. but on the brightside, my buddy who works the cell area said when i get my replacement, if the same thing happens he has to give me the telus phone of my choice. SOO. if the htc desire hd does come to telus, i can purposely brick my phone, say froyo did it, and get the desire hd for free. although i dont know much about htc, ive heard they r the best android brand around. u got any info on htc at all rocco? all i know is sense looks sexier then any rom ive seen thus far including every differenty model rom ive seen on youtube. imma post a new thread warning t959d users to beware on flashing roms until there propp[erly ported to our phone. cause as u can see in the above post, i know what i was doing. wasnt like i just fukedup and forgot something. i had nero v5 running with the supercurio stock voodoo kernel last night but it felt like it was hiccuping after i enabled the lagfix so i decided to go back to stock and try other roms. from what i heard, axura is the best of the best for vibrant roms. so i flashed to stock with odin. added the new kerne; thru odin, let the lagfix install, rebooted into recovery, disabled the lagifx, system lagfix and debug. rebooted. let the lagfix uninstall. copied the zip to my interna; sdcard, rebooted into recovery, wipe data, cache and dalvik then chose the zip. it installed properly. i clicked reboot phone then it turned off. and that was that. question is is there anyway to use slp to open your phone and try and reset it or is it bricked and am i without a phohe till next wednesday?
Click to expand...
Click to collapse
The only thing I can say is keep trying to get it into download mode? I had an HTC desire, I just sold it on ebay, and have the cash waiting for the Desire HD...so yeah, the HTC stuff is real nice. It's being released at TELUS on feb 10, for $499.
LINKSLOVESANDROID said:
i did disable voodoo. dunno y it bricked. i went to the future shop i got it from, lied and said i flashed official froyo from kies and it wouldnt start afterward. They checked my account. turns out i was 3 days late on my replacement policy fee so i have 2 wait 3 business days with a paper weight phone until it goes through b4 they can replace it for me. but on the brightside, my buddy who works the cell area said when i get my replacement, if the same thing happens he has to give me the telus phone of my choice. SOO. if the htc desire hd does come to telus, i can purposely brick my phone, say froyo did it, and get the desire hd for free. although i dont know much about htc, ive heard they r the best android brand around. u got any info on htc at all rocco? all i know is sense looks sexier then any rom ive seen thus far including every differenty model rom ive seen on youtube. imma post a new thread warning t959d users to beware on flashing roms until there propp[erly ported to our phone. cause as u can see in the above post, i know what i was doing. wasnt like i just fukedup and forgot something. i had nero v5 running with the supercurio stock voodoo kernel last night but it felt like it was hiccuping after i enabled the lagfix so i decided to go back to stock and try other roms. from what i heard, axura is the best of the best for vibrant roms. so i flashed to stock with odin. added the new kerne; thru odin, let the lagfix install, rebooted into recovery, disabled the lagifx, system lagfix and debug. rebooted. let the lagfix uninstall. copied the zip to my interna; sdcard, rebooted into recovery, wipe data, cache and dalvik then chose the zip. it installed properly. i clicked reboot phone then it turned off. and that was that. question is is there anyway to use slp to open your phone and try and reset it or is it bricked and am i without a phohe till next wednesday?
Click to expand...
Click to collapse
Best way I've found to avoid this is to unzip the ROM and take a look at the update script to see exactly what it's flashing. Some custom ROMs flash more then just the kernel and modem and modify things like the boot.bin, which is almost sure to brick your phone if it's not compatible.
To all Telus Fascinate T959D users, I have posted a complete guide to installing custom Vibrant ROM's.
The guide shows you how to install any ROM for the T-Mobile Vibrant (I prefer Team Whiskey's Nero 5), then flash a custom Telus Fascinate kernel with Voodoo and CWR built-in, and then finally flashing the stock Telus Fascinate JL3 modem.
This will leave you with a 100% functioning (yes, flawless) custom ROM on your Fascinate.
The reason I posted the guide, despite this one already existing, is that it doesn't require you to sacrifice certain functionality. The guide I have posted is only for flashing Vibrant ROMs, and uses supercurio's newly released T959D Stock+Voodoo kernel that is built on the Telus one, so everything works.
Themes
So I just followed samperlmutar's guide and installed the nero v5 rom. My question is now I'm having problems applying themes for Nero v5. I followed instructions to the T on the theme pages in the Vibrant section but it says it is not compatible. Anyone know if Vibrant Nero v5 themes will work on a Telus Fascinate?
This is a very informative post - thank you.
im very new to this my phone will not turn on completely i can get into download mode still but phone isnt functioning. I'm just trying to install 2.2 OS on it. Is anyone online that can help
crap
I have an issue. Everything was going great Step 1 complete. Step 2 the download was deleted from rapidshare. so I googled and downloaded the file from dl.project-voodoo.org
It failed. now the phone boots but only to a screen with a phone icon and a computer icon with a warning icon. so it wont boot, it wont connect to the pc and wont hard reset.
Any suggestions? Thanks.
Rick
still failing
merganser said:
I have an issue. Everything was going great Step 1 complete. Step 2 the download was deleted from rapidshare. so I googled and downloaded the file from dl.project-voodoo.org
It failed. now the phone boots but only to a screen with a phone icon and a computer icon with a warning icon. so it wont boot, it wont connect to the pc and wont hard reset.
Any suggestions? Thanks.
Rick
Click to expand...
Click to collapse
k well I got it back in download mode and odin 3 recognizes it but step 2 is still failing. any chance I can get that step 2 download?
Yeah it's pretty annoying how every guide I've tried to go through so far has broken links.
Hi to all,
I created this thread here is for existing users, potential users, interested users and experienced users or any casual visitors who wants to know more about the rom. Well, SGS users will ask why create a thread just for this, when there is another one over at the development section. The answers are listed as follows:
To reduce the number of posts in the other thread (reduce spamming) thereby not bogging down the developers with issues that can be solved by the users. And they can spend their time to concentrate what they do best, which is improving the MIUI Rom.
To consolidate questions, problems, bug reports, comments in one place. As you can see from the other thread, many a times, some of the posts which benefits the users were consumed by newer posts. While there is a SEARCH function, I can understand it can sometimes be a challenging task just to sieve through the searched posts results. I know we can't eliminate users posting repeated issues, but at least this will attempt to reduce those posts.
To allow new xda members who are on MIUI but unable to post their ideas, comments, etc. This is also an important avenue to allow new xda members to have a voice. While they may be new, they might have tips, tricks and also can help to resolve issues. Issues brought up can be shared by everyone too.
To allow the developers concentrate on improving the MIUI rom. Who doesn't want a better MIUI? Of course the developers doors will always be open, and will help out whenever they can, but wouldn't it be better for us to let them concentrate on what they do best, and what we want best?
So, to make it successful, I need you guys to help one another out, like what I have seen over the other thread.
This thread belongs to all of you, and I am sure that there is active participations in here.
MIUI has a pretty long history. However, for our device, MIUI has just evolved. Likewise, the user base has just started to grow. There will be times when even the most experienced user or developer will get stumped too, and not able to come up with a solution to resolve. We can see from the other thread that there are diverse views regarding battery life, sdcard issue, etc etc. We will not know since the usage pattern of each individual is as good as your fingerprint. No one is alike. Therefore we seek your understanding that issues not solved immediately will be looked into seriously by the team. There will always be limitations for every rom, regardless what base they come from.
All we ask is whether this rom fits your usage or not. And the only way for you is to try it out. Feel it, experience it, and judge for yourself if this rom fits you, can you live with the shortcomings of the rom. If you decide that this rom doesn't fit your daily needs, you can just simply flash to another rom that fit your needs better. And you can at least tell yourself that I have tried but it is not suitable.
Is this thread some form of advertising? Well, again different interpretations for different people. We will not go into that as we believe the QUALITY OF THE ROM WILL SPEAK FOR ITSELF.
One thing that can be said though, credits goes to the cm7 team, the official MIUI developers too. And each day, we can see breakthroughs. I do foresee a bright future for this rom here.
FAQ Section
[Written by Galnet, g00ndu and me]
Before asking for help, please read through post 1 to post 4. Most of the issues have been addressed in this 4 posts. By doing so, you are helping to keep this thread clean.
1. APP RELATED:
1.1 Apps crashing all the time!
Simply enter recovery mode and do a Format on Data, System, Cache
1.2.1 Apps restored from backup not working
I would always flash from clean and redownload all your apps from market. I know you can backup and restore, but to me this causes alot of issues which people bring up all the time. If you want a clean install and avoid any issues in the long run, then 15 - 20 minutes of redownloading isn't as bad as hours of issues!
Also, if you want to try to restores apps using Titanium Backup, restore "APP ONLY," restoring data causes problems.
1.2.2 3rd party apps force closing
Turn off compatibility mode. Settings > Programs Tab > Manage Applications > All Tab > Select app > Turn off OR IF IT STILL FORCE CLOSES Settings > Programs Tab > Manage Applications > All Tab *again* > Select app > Clear Data > Uninstall and then reinstall using Market.
1.3 Apps not installing
Clear market cache and try again.
1.4 Can't See Paid Apps in Market
Download SGS-Tools and select Market Fix and apply then reboot.
1.5 Downloading from Market Not working
Goto Downloads Press Menu Key and switch Settings to WiFi or Mobile network.
1.6 Searching not working
Simply enter search advanced settings and turn off searching within SMS (Mentioned on Original Post)
2. HARDWARE RELATED:
2.1 SD-CARD Not working or other issues with Camera or Sensors
When flashing if you don't see the Cyanogen Logo after the Samsung one when turning the phone on to enter recovery (After flashing cm7-galaxys-initial-kernel.tar) , then STOP flashing process as you have done something wrong or are trying to install coming from a JVK rom. Downgrade to Froyo or if need be JM1 and start the process over.
Also, camera is not working properly (known bug) – poor saturation and multiple lines running through image.
2.2 External SD card not detected
If your external sd card is not detected even when the kernel had corrected the issue, you most likely has the 2.3.3 bootloaders. You may flash the bootloader (definitely not recommended) or you can restart using EZBase rom or follow galnet's guide in his site.
2.3 Auto rotation/accelerometer not working
If your auto rotation/acceleromter is not working (despite having it enabled in Settings > Common Tab > Display Settings > Auto-rotate screen) then hard reboot (completely switch off device, wait 10+ seconds, and then switch device back on)
2.4 High Battery Drain
Known CM7 bug that is not fixed yet.
2.5 Battery only reports ~96% on full charge
This is a function implemented on ALL 2.2.1+ ROMS (including MIUI, which is based off CM7 2.3.3) so that the battery of the devices do not overcharge. Samsung ROMS falsely report 100% charge, but in actual fact, it also charges to ~96% and that if you watch closely, after a few minutes, the battery will rapidly drop back down to ~96% and stablise.
http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
2.5 Battery has stopped charging
Battery is known to stop charging when it gets too hot. This is to protect the battery and phone from exploding.
2.6 Phone turns on when I insert charger
This is a known bug (or function LOLS) which is present in the Nexus S ROMS and because the SGS MIUI ROM is a derived from the MIUI Nexus S ROM, SGS will also have this bug/function.
3. ETC:
3.1 Where do I start?
Have a look at Galnet's MIUI Guide and note that you can start from ANY Froyo ROM (Stock and Custom) as long as your device has a Froyo Bootloader.
3.2 Flashing from JVK to MIUI
You must first downgrade the firmware to Froyo (which MUST include a Froyo Bootloader - check in zip via WinRar for boot.bin and sbl.bin) It has been found that the Gingerbread bootloader has caused major problems. It is recommended that you downgrade to Eclair JM1 then upgrade to JS5 (files are avaliable on Galnet's Website) and then follow Galnet's MIUI guide to flash MIUI.
Note that flashing/using any Gingerbread modems such as JVK will not cause problems, it is only the Gingerbread bootloader that is causing problems.
3.3 IMEI SCREWED!
Flash back to JS5 or another Official Rom and it will be restored!
3.4 FLASH AT OWN RISK
If you don't have a clue what you are doing or ODIN is a strange word, then please go over to Galnet's MIUI guide and read it before flashing, make sure you understand the risks and note that the developers are not always available to answer your questions instantly!
3.5 Applying a downloaded theme:
Move theme file anywhere onto your phone's memory (should have a .mtz file extension) > Open Theme Manager > Press on Capacitive Menu Button > Import Theme > Locate and Select the theme you added onto your phone's memory
Alternatively, you can directly move the theme (.mtz) file to sdcard/MIUI/theme/
3.6 (SOME) Themes not changing lockscreen
Check that the theme supports MIUI Gingerbread 1.4.8, older MIUI FROYO themes will not work.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
COPY AND PASTE:
(Insert FAQ here)
In the future, please refer to the MIUI FAQ Section[/URL ] before posting.
TIPS AND TRICKS
1. Download seems to get stuck forever. Download only works with wifi.
To fix, open up the Download App, click menu, select toggle 3g /wif. This normally will work. If it doesn't work, try for 2 or 3 times. Remember to cancel the download from the app. If it still doesn't work, reboot and try again. The best fix will be to boot into recovery, and do a wipe / factory reset and reboot. Before downloading, go to the download app to activate the 3g / wifi toggle.
2. Speaker phone is too loud (Thanks to Ekin)
Goto DSPManager > Phone Speaker > Enable equalizer
Then drag all the zeros on the graph down to about -3.0 but keep them all roughly the same. This will lower the volume on the loudspeaker for everything, fixing your problem. When you want to watch a movie and want to make it louder, go back here and just swipe it to disable. So its only one swipe to get it on/off. In order to keep the settings, you need to hit the Back button for it to register correctly.
Raising it/enabling bass boost seems to kill the quality a little bit, so I recommend not to do those.
I have a Nokia headset that I use, and its a little quite so I do the same trick (except I raise the "headset" equalizer) and this nifty trick is basically the same as the voodoo sound hack which takes proper use of the high-quality sound card inside the Hummingbird.
3. Choppy / Laggy graphics and interface (Thanks to whitesox311)
In the settings under battery options....it has " power saving mode" on automatically....if you disable this it gets rid of all the issues. Also, if you leave "Hi-res graphics" turned off in the launcher settings it vastly improves smoothness.
4a. How to get Swype to work (Thanks to Prototype159)
Download the swype installer.
Follow the directions all the way til the end.
Hit the finish button. Reboot.
If it didn't work, clear data and uninstall swype and the swype installer. Try again.
If you change the kernel, you will have to redo it again.
4b. How to get Swype to work (Thanks to agha123)
Follow the instructions to the tee on this web page ,
http://www.androidpeek.com/2010/12/get-swype-keyboard-working-on-miui-rom/
5. Screenshot (Thanks to hacksome)
Pressing Menu + Volume DOWN -->> Screenshot!
reserved
Sent from my GT-I9000
Hmm...good timing. I have some questions on my own.
I have been reading the installation procedures for a while. This particular line intrigues me
6: Pull out the USB cable and start (in download mode) with 3-button-combo in recovery mode (waiting until samsung logo appears)
How do I start recovery mode within download mode? I don't want to take any risks but wish to understand fully on what I will be doing before I commit.
Another question: Assuming that later I decided MIUI is too buggy, is there a backtrack procedure? Usually I will just reflash with ODIN to a stock rom(eg: JPY) to rid of all the lagfixes etc then to maybe Doc's rom for example.
Since this is a ASOP sort of ROM in GB. how do I go about it?
Noob questions I know but I rather be noob now then to beg for help around later
i dont have the maps application in my rom. After installation i dont see any maps app.
mystifiyer said:
Hmm...good timing. I have some questions on my own.
I have been reading the installation procedures for a while. This particular line intrigues me
6: Pull out the USB cable and start (in download mode) with 3-button-combo in recovery mode (waiting until samsung logo appears)
How do I start recovery mode within download mode? I don't want to take any risks but wish to understand fully on what I will be doing before I commit.
Another question: Assuming that later I decided MIUI is too buggy, is there a backtrack procedure? Usually I will just reflash with ODIN to a stock rom(eg: JPY) to rid of all the lagfixes etc then to maybe Doc's rom for example.
Since this is a ASOP sort of ROM in GB. how do I go about it?
Noob questions I know but I rather be noob now then to beg for help around later
Click to expand...
Click to collapse
It means exactly that. In download mode hold the 3 buttons (vol up, power & home) and release all keys when the Samsung logo appears. After about 5 seconds you will see recovery mode.
You can easily backtrack. In Odin use a fw that has all three files and tick repartition. I use jpu.
Sent from my GT-I9000 using XDA App
sxi200 said:
It means exactly that. In download mode hold the 3 buttons (vol up, power & home) and release all keys when the Samsung logo appears. After about 5 seconds you will see recovery mode.
You can easily backtrack. In Odin use a fw that has all three files and tick repartition. I use jpu.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
@mystifyer,
this is the same answer i will give. it is correct.
thanks sxi200.
Sent from my GT-I9000
vivekrk44 said:
i dont have the maps application in my rom. After installation i dont see any maps app.
Click to expand...
Click to collapse
maps can be downloaded from market.
Sent from my GT-I9000
This is new! I didn't know we can do that!
Shall give it a try this Friday Thanks for the explanation
Another question:
I understand also that ASOP roms don't have the very good codec support. Fair enough. Some threads I seen has mentioned of Moboplayer. I gave it a try. Works well enough in hardware acceleration mode but software decoding mode looks really slow.
Now my question is: Does software decoding mode works better in ASOP roms than say a generic lagfixed rom?
vivekrk44 said:
i dont have the maps application in my rom. After installation i dont see any maps app.
Click to expand...
Click to collapse
Download from Market.
mystifiyer said:
This is new! I didn't know we can do that!
Shall give it a try this Friday Thanks for the explanation
Another question:
I understand also that ASOP roms don't have the very good codec support. Fair enough. Some threads I seen has mentioned of Moboplayer. I gave it a try. Works well enough in hardware acceleration mode but software decoding mode looks really slow.
Now my question is: Does software decoding mode works better in ASOP roms than say a generic lagfixed rom?
Click to expand...
Click to collapse
wow, this one i dont really know. i am not sure if there were bemchmarks being made on that or not.
not a good comparison, but still say this. i ran quadrant for this two roms, and the framerate for samsung is better in 3D, and not much different on 2D.
dont forget samsung did not release the sourcecode, and cyanogenmod do it from scratch. but nevertheless it is still good in aosp.
Sent from my GT-I9000
Prasad007 said:
Download from Market.
Click to expand...
Click to collapse
tks buddy, glad you are here too.
Sent from my GT-I9000
g00ndu said:
tks buddy, glad you are here too.
Sent from my GT-I9000
Click to expand...
Click to collapse
Likewise.
No problem. I will know it after I try this Friday. I can share it then, provided nothing goes wrong.
Quite a fair bit of adventurous users tend to dive in straight without checking the cons of a ASOP rom, only to regret and then flash back. I don't really want to fall in this category.
Multimedia is big for me as I watch alot of animes. This codec problem might give me abit of a headache with the software decoding and probably missing code support.
I think I asked enough. Shall camp here and explore other users' problems.
Thanks for the feedback. Appreciate it.
Did the galnet's instructions and the result is the same. so tired by the way
dr.bahaeddin said:
Did the galnet's instructions and the result is the same. so tired by the way
Click to expand...
Click to collapse
I've PM'ed you, I advise you do a 3 file install of JP2 via ODIN to make sure all your files on the phone aren't corrupted.
Once you have got Froyo installed then please get back to us. (Boot into Froyo and make sure it's all working correctly)
galnet said:
I've PM'ed you, I advise you do a 3 file install of JP2 via ODIN to make sure all your files on the phone aren't corrupted.
Once you have got Froyo installed then please get back to us. (Boot into Froyo and make sure it's all working correctly)
Click to expand...
Click to collapse
got your message man downloading right now. maybe my internal sd makes files corrupted?
dr.bahaeddin said:
got your message man downloading right now. maybe my internal sd makes files corrupted?
Click to expand...
Click to collapse
Pass mate, but if you have a felling this could be the case then format the internal sd, after installing Froyo and then copy the required MIUI files back across to your internal sd and then try to proceed in flashing MIUI again.
galnet said:
Pass mate, but if you have a felling this could be the case then format the internal sd, after installing Froyo and then copy the required MIUI files back across to your internal sd and then try to proceed in flashing MIUI again.
Click to expand...
Click to collapse
ok now i'm on JP2 everything works fine.
Hi everybody! I'm Dr...
Nah nm. Anyways well the past 2 days I have been working on switching from FXP CM7 to CM9. Needless to say, the process was abit confusing and did run across some snags along the way. So now that I figured it out with some help. I am returning the favor to the community and putting up this guide. (Also this guide is for users who already have an unlocked bootloader and so. So if you are a new R800x user who JUST unlocked their bootloader using testpoint or so, you too can use this guide)
Keep in mind this guide is based on the changes and tweaks from FXP 125!
So for those who are using a R800x CDMA Xperia play, this is for you.
-= The Prep =-
1: You will need the Flashtool to flash the latest ftf from Verizon. agraceful was nice enough to put it on his cloud storage here. http://www.mediafire.com/?yas7dola6dgd8 (You may wanna disable your AV for this as Kaspersky for me, didnt like the file since it uses exploits to do the stuff to your phone) if the cloud storage is down, this is the thread for the flashtool. http://forum.xda-developers.com/showthread.php?t=1351299
2: The latest Verizon ftf file here. http://forum.xda-developers.com/showthread.php?t=1696233
3: The latest FXP CM9 (remember its zeusc that you are downloading for!) AND the gapps for ICS! (Very important you use the right gapps here), http://forum.xda-developers.com/showthread.php?t=1447542
*OPTIONAL* 4: Mjolnir Kernel (boot.img) - http://forum.xda-developers.com/showthread.php?t=1708459 (Rename that img file to boot.img) (This is a diff kernel which may have some different features and abilities compared to fxp 125, so take a look and choose, atm it has zRam support (compcache) )
*OPTIONAL* 5: Cdma Carrier Name Fix - https://dl.dropbox.com/u/21955004/Carrier Fix.zip (This can either let you use a custom carrier name or least fix it from saying T-Cdma 64)
6: Of course, fastboot, drivers, and drivers for the flashtool which come with flashtool for flash drivers. (Not covered in this guide, cause if you already have CM7 on CDMA.. I am assuming you already have an unlocked bootloader, drivers etc already installed)
Now once you have everything. Time to do some EXTRA note prep work:
1: Make note of your MDN/MSID numbers. (The phone number and 2nd set of number incase you need to manually program your phone if OTA programming doesnt work)
2: Titanium Backup of your apps/data
3: Put the CM9 zip, cdma mega fix, and gapps ics into the memory card root folder. You will need this here to flash in a bit.
4: Kiss your phone bye bye and tell it you love it and that it will be back online soon if you dont mess it up!
Now you are ready to get started!
-= The Upgrade Install Process! =-
1: Turn your phone off, hold the back button and plug in the usb, You should be in the flash mode. Load up flashtool. (Your PC will install the drivers now if it needs to or the flashtool will error and tell you where the drivers are located to install and run its exe file to install)
2: With drivers ready, phone ready, you can drag the verizon ftf file to the main screen of flashtool. It should start up, give you some notes, tell you what you need to do if needed and just start flashing. Wait till its done fully, then you can close out of it, reboot your phone, if it boots up to Verizon screen setup, you have done the job correctly! Grats!
3: Unplug USB, Turn off phone, hold the search button, then plug in the usb again. You will see a blue light on the power button to tell you that you are fastboot mode.
4: Make sure the boot.img (Either the boot.img from FXP 125 zip file or the downloaded one) is in the same folder as your fastboot command! From cmd prompt, be in the directory of your fastboot and type fastboot -i 0xfce flash boot boot.img this should be a quick process and will put the new kernel you need with its cwm recovery built in needed for CM9. After thats done, type fastboot -i 0xfce reboot
5: During the reboot phase, LOOK at the power button. The MOMENT you see it light up "blue" hold the back button. This will load you into CWM where you can get started!
6: Now you SHOULD have your files on your SD card ready to be flashed! If you dont and you forgot. Just go to "mount" and mount the usb storage and then put your files on the sd card. (Silly person forgetting! Remember, its the cm9 zip, cdma fix, and the gapps ics)
7: Now flash the fxp 125 cm9 zip. Will take a min or 2. Once that is done. Do the 4x wipe. Wipe/Factory reset, Wipe Cache, Then goto Advanced, Wipe Devlik, Wipe Battery Stats.
8: Now flash gapps ics
9: (Optional) Flash the Cdma Carrier name fix.
10: Reboot into your phone.
If you see the cool transwarp sliders style android logo. Go WOOT!
-= The Inital Setup =-
Now that you are staring at the new android setup wizard here are my "personal" tips
1: From the setup wizard. I just did the basic, and SKIPPED the sign in part. Get your wifi running once inside if you want. Then load up "Play Market" and sign into google from there.
Why did I do this? Well.. I did it the other way 1st time signed in during the setup process.. and well.. I left the option "Restore phone from google" enabled.. yea.. not smart, next I know its installing EVERY app I had from Google. (Which I guess it was basing it on the google history or using my G1s installed stuff to restore from) By doing it the way above, it doesnt try to start restoring everything. Which is good.
2: Now to program your phone number and so again. Now I did this using pageplus, which is still verizon. For me, the OTA to get my number back in was *228 send. Wait wait wait, and it should program and be done with. Alt numbers are *22890 and *22891 which some update the roaming towers or just an alt form of OTA. Now if none of that works, then do the manual programming.
3: In the market, get titanium backup (and your pro key) and install.
4: The rest you should be able to do yourself as far as restoring goes using titanium backup.
Congrats you are now running ICS CM9 FXP!
Hope this guide helps people who maybe confused and would like a lil thread with something to look over to help them get it going. =)
Reserved..For..Stuff..
-=Tweaks=-
V6 Supercharger - http://forum.xda-developers.com/showthread.php?t=991276 (This is being used to help increase performance of CM9 on our xperia as well as some games that started sluggishing up after the change to ICS)
Volume+ - https://play.google.com/store/apps/details?id=com.TEST.android.lvh&hl=en Well worth the money.. otherwise my emulators sounded too quiet lol. Not to mention Youtube. Now at work, I use Speaker setting 8.
Hey,
You can make the update, as of FXP125 you don't need a separate kernel to get CWM. It's baked in again. Volume keys get you into it.
Mogul345 said:
Hey,
You can make the update, as of FXP125 you don't need a separate kernel to get CWM. It's baked in again. Volume keys get you into it.
Click to expand...
Click to collapse
Done. I left it optional for now. =) Also the only thing I need to confirm on is if we need that cdma mega fix file still... I forgot my XP at home.. (Go figure) so I wont be able to test the update out till tm. Heh.
Mysticales said:
Done. I left it optional for now. =) Also the only thing I need to confirm on is if we need that cdma mega fix file still... I forgot my XP at home.. (Go figure) so I wont be able to test the update out till tm. Heh.
Click to expand...
Click to collapse
I did not have to flash the megafix. All I did was the following (w/ FXP125):
1)Use flashtool to flash new baseband from 2.3.4 FTF (when selecting what to flash, I excluded everything but baseband).
2)Use fastboot to flash the FXP125 kernel.
3)Booted into CWM, wiped data/cache/dalvik cache/battery stats, then flashed FXP125 and the 4/29 Gapps.
Only thing I think needs flashed is the carrier name fix. My phone says T-CDMA 64 again.
Ok thanks. Yea, according to lightningdude the only things in the cdma mega fix was just the gamepad fix (dont know what that is yet) and the cdma carrier name. Gonna try to see about those. While its minor, still good info to have.
Also its being said that we should use V6 Supercharger on the CM9 to improve some games again for XP users.
Ok thanks to lightningdude, I put the cdma carrier name fix in the guide. =)
Mysticales said:
Ok thanks. Yea, according to lightningdude the only things in the cdma mega fix was just the gamepad fix (dont know what that is yet) and the cdma carrier name. Gonna try to see about those. While its minor, still good info to have.
Click to expand...
Click to collapse
Ahh OK. That gamepad fix is the patch to the .idc file changing the button map so circle isn't back in some games.
Sounds like the megafix is just all the preferred patches that were applied to paxChristos' CDMA builds.
Yea, just made life easier. Also I excluded the gamepad fix as thats a personal pref.. cause BUTTON_B vs BACK_ALT mapping can break some apps which devs code for one or the other. Normally everyone is using BACK_ALT. Then emulators which can remap it all anyways works fine with it.
Edit: Ok just updated to 125 myself without the CDMA carrier name thing. My Pageplus comes up as Verizon Wireless, so not sure if the patch was needed, but still its in guide as optional, case you want a custom name or you do get that t-cdma 64 issue.
Mogul345 said:
Hey,
You can make the update, as of FXP125 you don't need a separate kernel to get CWM. It's baked in again. Volume keys get you into it.
Click to expand...
Click to collapse
are you saying that steps 3-5 of the install process is not required since its baked in? Sorry, just getting into the more advanced rooting/customization with the r800x. I'm going to unlock the bootloader (put this off for way to long but with the latest "No ICS from Sony/Verizon" i'm just going to move ahead with my own upgrades, then ftf the verizon 2.3.4, and then hopefully be getting ICS.
blkwhk said:
are you saying that steps 3-5 of the install process is not required since its baked in? Sorry, just getting into the more advanced rooting/customization with the r800x. I'm going to unlock the bootloader (put this off for way to long but with the latest "No ICS from Sony/Verizon" i'm just going to move ahead with my own upgrades, then ftf the verizon 2.3.4, and then hopefully be getting ICS.
Click to expand...
Click to collapse
Looks like the original instructions have been updated. You should follow the instructions as directed in the OP. Steps 3-5 currently are where you flash the boot.img (kernel) you wish to use. It's either FXP's (which would be extracted from the ROM .zip), or Moljnir's or the other one listed. All three have working Clockworkmod recoveries now. At the time these instructions were originally written the recovery in FXP's kernel was busted, the next FXP build fixed it, and that's when I wrote the post you're referring to.
I'm stuck on some developer ROM.. Was trying to follow instructions to get passed the activation lock. So I currently have a barely working ROM installed (as it seems it's for developers). I don't care what version of android I get installed at this point.. Looking for some help. I've been trying to fix it for days now. I don't have access to the icloud email I used to set up the samsung account, that's what started all of this *cries*
FancyPantsu said:
I'm stuck on some developer ROM.. Was trying to follow instructions to get passed the activation lock. So I currently have a barely working ROM installed (as it seems it's for developers). I don't care what version of android I get installed at this point.. Looking for some help. I've been trying to fix it for days now. I don't have access to the icloud email I used to set up the samsung account, that's what started all of this *cries*
Click to expand...
Click to collapse
You could try using Odin to flash the appropriate firmware though I'm not sure if it would wipe the reactivation lock
FancyPantsu said:
I'm stuck on some developer ROM.. Was trying to follow instructions to get passed the activation lock. So I currently have a barely working ROM installed (as it seems it's for developers). I don't care what version of android I get installed at this point.. Looking for some help. I've been trying to fix it for days now. I don't have access to the icloud email I used to set up the samsung account, that's what started all of this *cries*
Click to expand...
Click to collapse
Which/what instructions were you going by....?
Deleted
FancyPantsu said:
I'm stuck on some developer ROM.. Was trying to follow instructions to get passed the activation lock. So I currently have a barely working ROM installed (as it seems it's for developers). I don't care what version of android I get installed at this point.. Looking for some help. I've been trying to fix it for days now. I don't have access to the icloud email I used to set up the samsung account, that's what started all of this *cries*
Click to expand...
Click to collapse
@FancyPantsu, do you know what OS version you were running before you had done what, IMHO, you shouldn't have unless you know exactly what you are doing. You didn't actually flash a ROM persay, you flashed, i believe, the engineering ROM or something like that.....let me/us know EXACTLY what Android version you were running before you ODIN'd the factory Tar file. By that I mean OG5, OK3, PB1, PD1, etc. But need that to possibly get you out of your predicament....
al50 said:
@FancyPantsu, do you know what OS version you were running before you had done what, IMHO, you shouldn't have unless you know exactly what you are doing. You didn't actually flash a ROM persay, you flashed, i believe, the engineering ROM or something like that.....let me/us know EXACTLY what Android version you were running before you ODIN'd the factory Tar file. By that I mean OG5, OK3, PB1, PD1, etc. But need that to possibly get you out of your predicament....
Click to expand...
Click to collapse
Honestly this would be the first time anything like this has happened, haha.. I've flashed many devices with custom roms and never seemed to have this much of a problem. Basically the whole situation was I got the phone from my cousin who didn't need it anymore, she doesn't know her google info (no way of finding out now), so I figured what the hell and started screwing with the phone. Samsung being Samsung.. This happened. I seem to have flashed a dev rom or as you said an engineering rom (which I'm pretty sure it is). If I can remember correctly it was running.. 6.0.1.
If it helps any, I'm up for trying anything I've got plenty of phones laying around at this point, would be nice to have the s5 again though.
**Sorry for the very, very, very late reply!
-Thanks.
... del ...
bbsc said:
All you need is:
1. Install a 4.4.2 with working Samsung Account. It's a little tricky because you cannot downgrade your phone via Odin to 4.4.2. Root that "developer ROM" you have, install Safestrap Recovery and use it to flash a custom stock-near 4.4.2.
2. Boot it and bypass Setup Wizard. It's a little tricky too but is easily done with an OTG cable and a USB stick. There are other methods but I like this one .
3. Create a new Samsung account (or login to your existing Samsung account) from the phone and turn Reactivation Lock off.
After this you'll be able to flash any firmware.
Click to expand...
Click to collapse
Is it possible to message you directly in case I need any help or have questions? @bbsc
... del ...
bbsc said:
Please, ask questions and I'll answer if I can.
Have a look at the first and the third post in this thread: https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
It will give you directions how to root your current rom and to install Safestrap Recovery.
This will be the first step
P.S. Nothing more. Just G900VVRU2APA1, Apex launcher, BusyBox, Towelroot, Safestrap Recovery.
Click to expand...
Click to collapse
Oh jeez. That's confusing already.. Lol. I've got G900VVRU1ANCG downloaded \, Towelroot v3, Safestrap KLTEVZ
I'm currently booted into the current engineering rom. Next step?
(Sorry if I'm not catching it the first time)
... del ...
bbsc said:
The next step is to read the thread I've given you link to, download files, install Apex launcher, BusyBox, Towelroot, Safestrap recovery. To root engineering ROM.
You'll need some 4.4.2 stock-like ROM to install via Safestrap Recovery. Odin won't work. This ROM will do. You can download it here.
After this you need to reboot to Safestrap Recovery and install kltevzw_NCG_eLLiKat1_0.zip
Click to expand...
Click to collapse
Alright. Currently I have the files downloaded, moving them over to the sd card now. EMMC_15_VZW_QB2_STOCK_MAGISK_ROOT.zip, EMMC_15_Root_Bootloader_Unlock+S5_QB2_PB1.zip, Towelroot.apk, Safestrap.apk. Missing anything that you can notice? I'll continue to follow the steps and see where it lands me
... del ...
bbsc said:
Supersu.apk missing. My fault, sorry.
1. Copy apk files and kltevzw_NCG_eLLiKat1_0.zip into the phone's memory.
2. Install Apex_Launcher.apk (you'll need to turn Unknown Sources ON) but do not run it.
3. Install BusyBox.apk but don not run it.
4. Install Safestrap_KK.apk but do not run it.
5. Install tr_v2.apk - Open - make it rain (a message "You should have root, no reboot required" should appear) - Back.
6. Install Superuser.apk - Open - Continue - Normal - Reboot.
7. After reboot, in the pop-up window - Apex Launcher - Always - Ok.
8. Menu (dotted button) - BusyBox Free - Grant - close balloon - Install - close balloon - Back.
9. Safestrap - Grant - Agree - Install Recovery - Reboot to recovery. Wait patiently for SafeStrap Recovery to boot.
10. Swipe to Allow modifications - Wipe - Advanced Wipe - Dalvik/Data/Cache - Swipe to Wipe.
22. Back - Back - Back - Install, install kltevzw_NCG_eLLiKat1_0.zip.
Reboot system and now you must have a 4.4.2 phone with Samsung account locked. Next step will be to bypass Setup Wizard.
Click to expand...
Click to collapse
Got into recovery once. Followed the wrong directions- off the link you gave me. Wasn't supposed to do anything else from there I suppose. Now I reboot to custom binary blocked by reactivation lock. Solution? Gotta redo everything again?
... del ...
bbsc said:
Sorry.
You have to begin again from the start and flash COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_257265 6_REV00_user_mid_noship_MULTI_CERT.tar.md5 with Odin.
I'll prepare a detailed guide with files if needed but a bit later.
Click to expand...
Click to collapse
No need- I redid everything already. About to boot into safestrap.
... del ...
bbsc said:
I'll leave it here to edit and add links later.
1. Charge the battery to more than 50%.
2. Download Odin and COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_257265 6_REV00_user_mid_noship_MULTI_CERT.tar.md5.
3. Download applications files - apks.zip.
4. Download ROM file - kltevzw_NCG_eLLiKat1_0.zip.
5. Run Odin.exe.
6. Select COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_257265 6_REV00_user_mid_noship_MULTI_CERT.tar.md5 in Odin's AP slot, boot the phone into the download (Odin) mode, connect with USB cable to the computer, press Start, wait till the flash process is finished. Press Exit and wait for the phone to complete reboot.
7. Disconnect USB cable from the phone and connect again.
8. Unzip apks.zip into the apks forlder on the Desktop.
9. Copy everything from apks folder to the root of phone's internal memory.
10. Copy ROM file kltevzw_NCG_eLLiKat1_0.zip to the root of phone's internal memory.
11. Disconnect the cable from the phone.
12. Press Menu (dotted button) - My Files - All - RootS5.
13. Apex_Launcher.apk - Settings - Unknown Sources - Ok - Back - Apex_Launcher.apk - Next - Install - Done.
14. BusyBox.apk - Install - Done.
15. Safestrap_KK.apk - Install - Done.
16. tr_v2.apk - Install - Open - make it rain (a message "You should have root, no reboot required" should appear) - Back.
17. Superuser.apk - Install - Open - Continue - Normal - Reboot.
18. After reboot, in the pop-up window - Apex Launcher - Always - Ok.
19. Menu (dotted button) - BusyBox Free - Grant - close balloon - Install - close balloon - Back.
20. Safestrap - Grant - Agree - Install Recovery - Reboot to recovery. Wait patiently for SafeStrap Recovery to boot.
21. Swipe to Allow modifications - Wipe - Advanced Wipe - Dalvik/Data/Cache - Swipe to Wipe.
22. Back - Back - Back - Install, install kltevzw_NCG_eLLiKat1_0.zip.
23. Reboot System - Do not install. After reboot you should see 4.4.2 Setup Wizard (dark background).
24. Connect to Wi-Fi AP.
25. Get a FAT-formatted USB stick of any size and a USB-OTG cable. Throw any apk file on the USB stick and connect it to the phone.
26. When the phone recognizes the storage it will pop-up an Explorer window. Navigate to your apk file and tap it once. You should see a security warning with link to Settings.
27. Press "Settings", navigate to Reactivation Lock and disable it. The phone will ask you to enter login/password from your Samsung account or to register a new one. Do it.
28. After logging into the Samsung account you should be able to disable Reactivation Lock.
29. Flash any firmware on your choice. The current firmware is outdated and may be non-operational in some points.
Click to expand...
Click to collapse
Thank you very much kind sir Restored, up and running again.
FancyPantsu said:
Thank you very much kind sir Restored, up and running again.
Click to expand...
Click to collapse
~~ Now if I want to flash a custom rom from 4.4.2 up to 7.0 how can I do that..? Currently trying multiple roms, none of them will boot correctly. Get's stuck in a boot loop
FancyPantsu said:
~~ Now if I want to flash a custom rom from 4.4.2 up to 7.0 how can I do that..? Currently trying multiple roms, none of them will boot correctly. Get's stuck in a boot loop
Click to expand...
Click to collapse
This question does not concern this discussion.
Your phone is now "clean" and if you flash a factory firmware with Odin and perform a factory reset it will be in a "like new" state.
You'd better begin with these threads:
One
Two
Personally I and my family and my friends use this ROM with the latest firmware for SM-G900V.