Database Develop

[Q] Stuck in recovery mode

So as the title says i am stuck in recovery mode, Heres the story.
Got a new Samsing Galaxy S Rooted it installed lagfix all went with out a hitch. Started to install patch to allow me to connect to adhoc networks before hand I backed up my system folder using adb pull. I copied the files for the crack to get adhoc working. My wireless on my phone stops working, I restore the back up I made using adb push and restarted the phone now it boots into recovery mode everytime.
The PC still connects to my phone and I can still use adb. Now how can I undo my stupidity or atleast fix my phone?
Cheers guys
</Noob>

that's a good sign at least
see if you can get into the Download Mode with the 3 button
then Flash it with Odin back to a stock ROM

Ok i am not sure what you are refering to by download mode what 3 button combo do i use to get into it? I was just looking at the Odin software and it sounds like it might do the job but where can could i get a stock ROM? My phone is running Android 2.1 would it hurt to try installing the leaked copy of 2.2 using Odin?

wiki my friend wiki
links to sams firmware are in the wiki
odin is also on sams firmware
also how to get into the Download mode
click my wiki link

Odin successful, but still stuck in boot loop

TL;DR - Stuck in boot loop, can't enter recovery mode, but can enter download mode. Odin says it is successful, but the phone is still in the boot loop.
I've had Cognition 2.3 for a few months now and decided to update to Cognition 4.3. I used the AIO toolbox 2.5 to Odin one-click back to stock, rooted, and flashed to 4.3. Everything went well and I restored all my apps with Titanium and loaded some music.
At some point later the screen was completely blank and the only way I could get any response out of it was to hold the volume buttons and power buttons. Instead of going into recovery, though, it would boot to the Cognition boot screen and hang indefinitely.
I was able to get it into download mode by removing the sim and battery and holding the volume buttons while plugging it into USB and replacing the battery. I ran Odin one-click again, it said it was successful, but the phone was stuck in either a battery screen or AT&T screen boot loop (depending on whether or not it was plugged into USB).
I've tried using regular Odin with both the ROM included with AIO 2.5 (JF6*) and JH2 (from http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36) to no avail. Every time Odin shows that it is successful, but it always ends up in a boot loop with no ability to enter recovery mode.
What can I do? Will getting a jig help me in any way?
*Edited for correct ROM

Use the normal ODIN (v1.7 or v1.8), a full stock JF6 ROM and PIT file. Make sure "repartition" is selected and if possible, do a master clear with ODIN first (though shouldn't be critical.........then start over with Cog 4.3 if that's your ROM of choice (good choice by the way).

I tried the JF6 ROM again with the same results (using http://forum.xda-developers.com/showthread.php?t=818439#8802897). It looks like AIO 2.5 used this ROM all along.
I can't master clear because I can't boot past the AT&T screen. The only way for me to get Odin (or Windows for that matter) to recognize the phone is by putting it in download mode. From what I understand you don't master clear from download mode.

bharden said:
I tried the JF6 ROM again with the same results (using http://forum.xda-developers.com/showthread.php?t=818439#8802897). It looks like AIO 2.5 used this ROM all along.
I can't master clear because I can't boot past the AT&T screen. The only way for me to get Odin (or Windows for that matter) to recognize the phone is by putting it in download mode. From what I understand you don't master clear from download mode.
Click to expand...
Click to collapse
Are you using the PIT file and selecting repartition?
When I get home today, I will upload the ROM and PIT that I use to flash to stock and see if that helps but you do need to use the PIT and repartion which will only help if you have a FULL copy of JF6 that reloads the bootloaders.

Just out of curiosity, what is your build number?

I am using the PIT and selecting repartition. I've done this every time I've tried Odin (besides when using one-click of course) Is the PDA.tar listed in that link not a full copy of JF6?
My build number is 1008.

May sound crazy, but you could try using a different computer. I ran into a lot of problems using odin on my pc. Switched to laptop (more ram and windows 7 64 bit ) with great success. Also make sure you have the right drivers. Your build# should allow you to use odin one click.
Sent from my GT-I9000 using XDA App

I've actually already tried it from both my PC (Windows 7 x64, 4 GB ram) and my laptop (Windows Vista x86, 2 GB ram). In both cases I used the drivers in the AIO toolbox 2.5 (http://forum.xda-developers.com/showthread.php?t=944418)
Are those the correct ones? If not, could you point me to a resource with the latest drivers? There are quite a few versions floating around and I'm not sure which ones I should be using.
Any other suggestions?

Those should be the correct drivers
Also, make sure odin is completely open before connecting your phone.
That'd all I can think of.
Sent from my GT-I9000 using XDA App

I definitely did that.
Since I'm able to get into download mode, I should be able to un-brick it right? I can't figure out why Odin says it's successful but I still can't boot.
Does anyone else have any ideas?

You may have to give it a few minutes or so as I am uploading now but the link for the PDA and PIT is:
http://dl.dropbox.com/u/24576569/ATT%20ROM%202.1.rar
Try using this version of ODIN:
http://dl.dropbox.com/u/24576569/Odin3%20v1.7.rar
Hope this helps otherwise I am out of ideas except flashing a kernel with a recovery included through ODIN, going into the recovery and formatting and wiping absolutely everything and then reflashing JF6. But try the files I linked first.
Good luck.

It's been 30 minutes and the ROM link still isn't up. Is it working?
Also, I'd like to change what I said slightly. When using regular Odin 1.81 it says PASS when it's finished. When using Odin one-click it gets to the point of cache.rfs and then says removed. The box turns blue and says Reset. Meanwhile, the phone is busy rebooting indefinitely on the battery screen.
I'll try your ROM and Odin version as soon as the link works. Also, do you have a ROM with built in recovery that you would suggest? Thanks!

bharden said:
It's been 30 minutes and the ROM link still isn't up. Is it working?
Also, I'd like to change what I said slightly. When using regular Odin 1.81 it says PASS when it's finished. When using Odin one-click it gets to the point of cache.rfs and then says removed. The box turns blue and says Reset. Meanwhile, the phone is busy rebooting indefinitely on the battery screen.
I'll try your ROM and Odin version as soon as the link works. Also, do you have a ROM with built in recovery that you would suggest? Thanks!
Click to expand...
Click to collapse
Drop box seems to be running slow. So the JF6 that I am uploading may take a bit. The version of ODIN that You are running should be fine.
Try this Kernel. It's not a complete ROM just the kernel. If it works, you will have to flash a ROM too. Cognition is a good start. You can find it in the Dev section and actually, even if it's not the recommended way of flashing, I moght try flashing a custom ROM anyway just to rule out ODIN and your phone. If you can successfully flash a custom ROM then it's probably the version of JF6 that you are using.
Anyway, let's start with the kernel first:
Onix by existz:http://forum.xda-developers.com/showthread.php?t=930679
make sure you download 2.0.3 "tar" file for ODIN
you know how to get into recovery after you flash right? From powered off, hold the up and down volume buttons and then power all at the same time for about 5 second......

Ok, so there seems to be some progress. I flashed the kernel and the phone rebooted to what I'm assuming is the Onix splash screen and hangs. The power button won't turn the phone off, but at least the softkeys do seem to respond, even if they don't do anything.
Odin now recognizes the phone in both download mode and at the splash screen. Although, to reach download mode I now have to take the battery out, whereas I did not have to before.
I'm still unable to enter recovery. The only way to get any response out of the phone at the splash screen is to hold both volumes and the power button, but the phone just reboots back to the splash. It also does this when attempting to enter recovery from a power off state.

bharden said:
Ok, so there seems to be some progress. I flashed the kernel and the phone rebooted to what I'm assuming is the Onix splash screen and hangs. The power button won't turn the phone off, but at least the softkeys do seem to respond, even if they don't do anything.
Odin now recognizes the phone in both download mode and at the splash screen. Although, to reach download mode I now have to take the battery out, whereas I did not have to before.
I'm still unable to enter recovery. The only way to get any response out of the phone at the splash screen is to hold both volumes and the power button, but the phone just reboots back to the splash. It also does this when attempting to enter recovery from a power off state.
Click to expand...
Click to collapse
The three button combo should work to reset the phone when it's stuck as well as getting into recovery. It sounds like you aren't holding the buttons for long enough. If the phone is frozen, you have to hold the button combo for quite a while to get the phone to reset. Weh trying to get into recovery, push both volume buttons and then hold down the power button and don't let go till yoiu get past the AT&T screen.
If that still doesn't work, then try and load up the ROM and see if at least you can get a working phone back in the meantime. Like I said, I recommend Cog 4.3 but serendipity is a good choice too.

Awesome. I must have been holding the buttons for half a second too little. Now I can get into the Onix Recovery, but I'm getting:
"E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory)"
when trying to mount the SD card.
Searching around I've found these two threads:
http://forum.xda-developers.com/showthread.php?t=563298
http://forum.xda-developers.com/showthread.php?t=792708
but I'm not exactly sure what to do with the information. I don't particularly want to go guessing at what to do next and ruin my progress. Could you give me a little guidance on what steps to take next?
From "adb shell mount /sdcard" I'm getting:
mount: can't find /sdcard in /etc/fstab

bharden said:
Awesome. I must have been holding the buttons for half a second too little. Now I can get into the Onix Recovery, but I'm getting:
"E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory)"
when trying to mount the SD card.
Searching around I've found these two threads:
http://forum.xda-developers.com/showthread.php?t=563298
http://forum.xda-developers.com/showthread.php?t=792708
but I'm not exactly sure what to do with the information. I don't particularly want to go guessing at what to do next and ruin my progress. Could you give me a little guidance on what steps to take next?
From "adb shell mount /sdcard" I'm getting:
mount: can't find /sdcard in /etc/fstab
Click to expand...
Click to collapse
OK, so I've never had to mount SD from those options so not too familiar with this problem but, i am going to guess that we shouldn't have to play with this right now. Onix will let you install a zip from your external SD, so i recomend finding a recovery flashable ROM (almost all custom ROMs come this way....it'll be a ZIP file) Again I recomend using Cog 4.3 or serendipity (both of these may change your kernel but it's ok because they will both have a custom recovery).
Follow these steps:
1. Remove your external SD and insert it into your computer.
2. Remove any files you want to keep and place them somewhere on your computer for future recovery (Titanium backups, music, pics, etc....)
3. Format your sd (FAT32 should be default)
4. Download the ROM of your choice, copy it to the root of your external SD using your computer
5. Replace the SD into your phone power up into recovery
6. From the Onix recovery menu select "advanced options"
7. Pick wipe dalvik/cache and confirm
8. Select go back untill you get to the first recovery menu
9. Select install zip from SD and NOT "install update.zip"
10. Navigate to your external SD (it should look something like "/extsd" in the file menu
11. Pick the zip you put on the external SD and confirm
12. Wait till the recovery indicates instalation done
13. Navigate back to the first recovery menu and select reboot phone
14. Sit back and relax, your phone will likely take 3-5 min to boot up the first time
If after 10 min of waiting you get no response from your phone, use the 3 button reset to get into the custom recovery and select advanced features again, format absolutely everything you can format (you'll have to do it one at a time) and do that. Then repeat the steps above.
Installing a custom ROM isn't normally this complicated but I am trying to eliminate as many variables as possible here that might cause complications with instalation.
Let me know how it turns out.

FYI: Continuum v4 has the Onix kernel in it (recovery is a blue color)

ROM Files
This is the link to the good JF6 stock ROM. You will have to download it and the ODIN version. All you need is the PDA.tar and the PIT that comes with the ODIN package in the thread. You can still use ODIN 1.8 once you get the PIT file out of the ODIN ZIP.
So, after all is said and done. When you feel like trying this:
1. Open ODIN
2. Phone into download mode (with phone off hold down both volume buttons and plug in USB)
3. Make sure phone is recognised by ODIN
4. Select PIT file that you downloaded
5. Select PDA file that you downloaded
6. Make sure "repartition" IS selected
7. Hit start and sit back and relax
http://forum.xda-developers.com/showthread.php?t=818439
Again, let me know how it all works out.......

Ok, I'll try flashing Cog 4.3 after I get off this afternoon. I'll have to buy an external SD, but that's better than buying a new phone.
I skimmed those threads on the internal SD problem and it looks like there's either some corruption on the SD or it's not formatted correctly or something. How can I fix this problem? Doesn't the ROM need that internal SD card space? Or can it use the external SD card as a replacement? If it does need the internal SD card then won't the ROM fail to install if that SD is corrupted?
Thanks for all your help by the way. When Odin wasn't fixing the problem I was afraid it was completely bricked.

[Q] install continium V5 with 3 button combo not working

Hi.Currently i am running continium V4 Android 2.2 .If i want to install another Foroyo rom it can be done via rom manager without 3 button combo.
Now i want to install gingerbread but i cant find any way to do it as all methods require 3 button combo to go to Download mode & recovery mode.
Actually i can go to download mode by a JIG.But recovery mode??????
Any alternate methods to update to gingerbread(continium V5)

I don't know how it does it, but I had a usb cable that had some bad terminals and when I plugged it into the phone when the phone was turned off, it went into recovery mode every time. I'm no electrical engineer so my theory had no basis but my thought is that the usb cable when coming from a charge dock has 2 pins for dc current, 1 positive and one negative. The 3 left (I think it's 5, not sure, not looking at one) must be for data transfer. Maybe 2 for synchronous travel and one for data corruption testing, not sure. Out of these pins, the only thing that makes sense to me that made it go into recovery was that one of the charge pins were not making contact, the positive or negative. I dont think any of the transfer pins would make a difference in this. Again, not sure if this is how it worked or not, just a theory. Maybe it can be replicated if recovery will help you, don't have any knowledge of CM.
Sent from my GT-I9000 using XDA App

Only rom in rom manager is cm7.
If you want to make the jump to gingerbread all you need is the jig one time to get into download mode and flash the gingerbread bootloaders, from there you will have a new working combo because the button combos are in the secondary bootloader.
Once on the gingerbread bootloaders
Vol up + power = recovery
Vol down + power = download
Thats it, one jig use...bootloader flash...working combo. easy.
You're welcome

http://www.youtube.com/watch?v=UOyx5JQ_8_I&feature=youtube_gdata_player

Just to inform you, but after you flash the GB bootloaders, you cannot flash Cognition. It has a secondary bootloader in its flash package that will cause your your phone to turn into a paperweight. Why? Because you can't mix bootloaders. A Gingerbread Primary bootloader must have a Gingerbread secondary. The secondary in Cog isn't a GB bootloader. For that reason, you also can't flash the Odin w/3button fix until AFTER you have flashed eclair/froyo bootloaders with Odin. So, if you do go to GB, ask more questions before you flash back to JF6 stock. It could be the difference in a working phone and a brick.

studacris said:
Only rom in rom manager is cm7.
If you want to make the jump to gingerbread all you need is the jig one time to get into download mode and flash the gingerbread bootloaders, from there you will have a new working combo because the button combos are in the secondary bootloader.
Once on the gingerbread bootloaders
Vol up + power = recovery
Vol down + power = download
Thats it, one jig use...bootloader flash...working combo. easy.
You're welcome [/Last night i again tried to flash gingerbread boot loaders.Here are the steps i followed.
1)Went back to stock(JF6) by ODIN.Initially i was running Continuum V4(Themed).Actually i did'nt perform a full wipe.
2)Went into DOWNLOAD MODE through ADB.
3)followed instructions given on ""[Rom][2.3.3] « GR-12 » **5/4"" in first post
Instruction i followed were
Installation Instructions:
1. Download this package.
2. Open Odin3 1.7
3. Select the PDA, PHONE, CSC, and PIT files in their correct spots
4. Connect phone in download mode
5. Ensure that Auto-reboot and Re-Partition are both checked. These have a tendency to change after plugging the phone in, so double check before you hit start.
6. This is where the bootloader will be flashed, along with stock Gingerbread. Hit Start.
7. Allow the phone to boot.
After hitting the START BUTTON,It got stuck on ""DO NOT TURN OFF TARGET.And my cappy is soft bricked again.
Any help is highly appreciated if i am doing anything wrong.]
Click to expand...
Click to collapse

You have a wonky connection. Make sure your chord is good. Plug into the back of the pc, no front ports, if its in a back port already go ahead and switch it to another one on the back. Restart your computer and try again. No need to return to stock first you can flash gb from where you are ... If you get a good connection...

studacris said:
You have a wonky connection. Make sure your chord is good. Plug into the back of the pc, no front ports, if its in a back port already go ahead and switch it to another one on the back. Restart your computer and try again. No need to return to stock first you can flash gb from where you are ... If you get a good connection...
[May be ur rite.I'll buy a new cord.
Another reason may be that i am going to download mode by ADB.Next time i will go to download mode by JIG.
One more thing i am using same cord for installing Foroyo roms and there is no problem.I'll post if i get it rite.Thanks
EDIT:SOLVED:
Hi all i just installed gingerbread.Now all of you installing gingerbreadWith 3 button combo not working here is what i did different.
1)Main point is i was going into DOWNLOAD mode by ADB.After that i was installing gingerbread bootloaders n boom mobile is SOFT BRICKED.
This happened atleast five times.
Today i prepared the jig with 3 100K resistors(Search XDA forum).Got my cappy into DOWNLOAD mode by jig and unbricked it.
Now note my cappy is in stock JF6.Again with jig got cappy into download mode and followed method posted on UTUBE by CONNECTION2005 and installed bootloaders which i did like a piece of cake.
then i installed kernal and....................
So main thing is DO NOT USE ADB TO GO TO DOWNLOAD MODE
THANKS FOR EVERY ONE FOR HELPING]
Click to expand...
Click to collapse

[Q] Restore from CyanogenMod

Hello,
I installed the CyanogemMod 7.1 on a SGS. Before install, I made a backup of the stock ROM using CWM. But now I want to come back to the Stock ROM, but when I restore the backup, is always giving me error when flashing the boot.img. Could be problems with the filesystems?
Thanks

To move from CM7 to another Samsung rom you have to use odin.
you need to flash a stock rom with 512pit file and tick repartition.

But I cant get to download mode. I used the three finger combination (volumedown+home+power) or the adb reboot-bootloader command and nothing.
If a use the three finger combination, the galaxy-s i9000 first screen appears but it flash and reboot again, and if I continue to press the buttons, it will enter in loop until I release the buttons and cyanogemmod opens normally.
How I restore the download mode screen?
Thanks

Try to pull battery off battery a few seconds
Sent from my GT-I9000 using XDA App

Hi, mate.
It's sad but you lost the three keys combo.
Now, if i don't say wrong, the only method to launch the download mode is to use a usb dongle.
Search the forum with the word "dongle usb galaxy s" and you should find what i'm talking about.
Normally the combo (notice that you can't access to recovery too) lost it self during a downgrade from ginger bootloader to froyo or eclaire bootloader.
Wich means that your bootloader is corrupted.

Hi people,
I bought a USB dongle and now the download mode is working again.
Thanks

[Q] galaxy ace s5830D in BOOT LOOP, no access to 'RECOVERY'

Hi gals and guys, I bought a new galaxy ace s5830D (gingerbread) from Telus and decided to unlock it the following way:
1. root using Universal_GB_ROOT_v10.zip
2. installed SuperOneClickv2.1.1-ShortFuse.zip on PC
3. installed Root Explorer (File Manager) v2.19.apk
4. used ADB shell on PC to read ST5L for unlock code
here is where the problem begins:
-- upon reboot phone goes in a bootloop (screen lights for a sec without Samsung logo)
-- I CANNOT put phone in recovery via home + power
--I CAN put phone in 'download' via power + home + vol dwn; or to RamDump with vol Up; or to Emergency Dload Mode by holding both up and dwn
I have tried the following:
-- flash stock telus rom S5830DTLKI4_S5830DTLSKI4_S5830DTLKI4_HOME.tar using ODIN. The flash goes successful but upon reboot goes back to bootloop? And still cannot enter 'recovery'
-- tried to flash cwm-recovery-ace.tar.md5 using ODIN. The flash is successful but on reboot goes to bootloop. Still no acess to 'recovery'
-- tried QtADB but cannot connect to phone
-- tried OneClickUnbrick but it will not recognize connection to phone either
-- tried AndroidSDK however cannot get to recognize device
So any ideas considering the main thing is I cannot get to 'recovery' and flashing with ODIN still results in bootloop.
Thanks for any advice

tedxdadevelopers said:
Hi gals and guys, I bought a new galaxy ace s5830D (gingerbread) from Telus and decided to unlock it the following way:
1. root using Universal_GB_ROOT_v10.zip
2. installed SuperOneClickv2.1.1-ShortFuse.zip on PC
3. installed Root Explorer (File Manager) v2.19.apk
4. used ADB shell on PC to read ST5L for unlock code
here is where the problem begins:
-- upon reboot phone goes in a bootloop (screen lights for a sec without Samsung logo)
-- I CANNOT put phone in recovery via home + power
--I CAN put phone in 'download' via power + home + vol dwn; or to RamDump with vol Up; or to Emergency Dload Mode by holding both up and dwn
I have tried the following:
-- flash stock telus rom S5830DTLKI4_S5830DTLSKI4_S5830DTLKI4_HOME.tar using ODIN. The flash goes successful but upon reboot goes back to bootloop? And still cannot enter 'recovery'
-- tried to flash cwm-recovery-ace.tar.md5 using ODIN. The flash is successful but on reboot goes to bootloop. Still no acess to 'recovery'
-- tried QtADB but cannot connect to phone
-- tried OneClickUnbrick but it will not recognize connection to phone either
-- tried AndroidSDK however cannot get to recognize device
So any ideas considering the main thing is I cannot get to 'recovery' and flashing with ODIN still results in bootloop.
Thanks for any advice
Click to expand...
Click to collapse
What ROM are you trying to flash with ODIN, because I couldn't find any on SamFirmware. Also in order to use ADB, you need the drivers, make sure you have them installed (they automatically install when you install Kies).

tedxdadevelopers said:
Hi gals and guys, I bought a new galaxy ace s5830D (gingerbread) from Telus and decided to unlock it the following way:
1. root using Universal_GB_ROOT_v10.zip
2. installed SuperOneClickv2.1.1-ShortFuse.zip on PC
3. installed Root Explorer (File Manager) v2.19.apk
4. used ADB shell on PC to read ST5L for unlock code
here is where the problem begins:
Click to expand...
Click to collapse
The stl5 method might damage the efs partition. It's a coinflip, with 3 outcomes:
-all goes well and you get an unlocked ace.
-your imei becomes 00000000000000 in which case you get aa working ace, but many carriers deny service to that imei, so no calls, no sms, no movile data.
-completely f****d up efs partition. You loose your imei. That's it, you're toast. No amount of flashing fixes this, it's not a hardbrick, but no rom will boot appropriately.
Try and flash a full package with odin. Make sure you use the correct odin version for your model and have the correct firmware. Then go into recovery and wipe everything, see if it boots. If it boots, open up your call app and dial *#06#* to see your imei (to make sure its still there).
If you have successfully flashed with odin before, and still won't boot or go into recovery, then maybe your efs partition got messed up.

Return the phone to telus, just don't tell them what you did.

thanks for the suggestions.. few more questions
-- any suggestions as to what to tell telus that is believable that happened? (phone is 3 days old and i bought it outright)
-- also re Efs partition damage, is there any way to repartition the phone and rewrite imei (isn't it on the stickers behind the battery)?
with ODIN i flashed (several times - all successfully) the stock rom made for the TELUS D version on the Ace. Its someone that build it from a stock Ace. Its available if u google it and many ppl have returned their Telus phones to stock telus\koodoo status via that rom with proprtietary carrier startup screen and all. The Model D of the Ace is not at all available on the SamFirmware site.
I also flashed only the CWM Recovery - sucessfully and still no access to 'recovery' menu.
ODIN i am using is the right version according to all i have read (4.42); and the .ops file is made, as I understand it, for partitions of the D version of the Ace. (odin + ops + rom was all one package that many ppl from telus have said to have used sucesfully to return their phones to stock.)
-- should i try to flash with odin a cyannogen mode 7.2.0; could that make a difference vs stock rom, or does the cyannogen just go on top of the stock rom; ie will not function without a proper stock rom? (i guess what i am asking is cyannogen a complete self contained os?)
--If the efs partition is damaged does it make sense then, that the ADB, oneclick unblock etc.., will not recognize the phone? Am i supposed to be able to even connect to ADB when phone is in 'download mode'? or its made to work only when phone is already booted up?
thanks guys again.. T

tedxdadevelopers said:
thanks for the suggestions.. few more questions
-- any suggestions as to what to tell telus that is believable that happened? (phone is 3 days old and i bought it outright)
-- also re Efs partition damage, is there any way to repartition the phone and rewrite imei (isn't it on the stickers behind the battery)?
with ODIN i flashed (several times - all successfully) the stock rom made for the TELUS D version on the Ace. Its someone that build it from a stock Ace. Its available if u google it and many ppl have returned their Telus phones to stock telus\koodoo status via that rom with proprtietary carrier startup screen and all. The Model D of the Ace is not at all available on the SamFirmware site.
I also flashed only the CWM Recovery - sucessfully and still no access to 'recovery' menu.
ODIN i am using is the right version according to all i have read (4.42); and the .ops file is made, as I understand it, for partitions of the D version of the Ace. (odin + ops + rom was all one package that many ppl from telus have said to have used sucesfully to return their phones to stock.)
-- should i try to flash with odin a cyannogen mode 7.2.0; could that make a difference vs stock rom, or does the cyannogen just go on top of the stock rom; ie will not function without a proper stock rom? (i guess what i am asking is cyannogen a complete self contained os?)
--If the efs partition is damaged does it make sense then, that the ADB, oneclick unblock etc.., will not recognize the phone? Am i supposed to be able to even connect to ADB when phone is in 'download mode'? or its made to work only when phone is already booted up?
thanks guys again.. T
Click to expand...
Click to collapse
Hey again, changing IMEI is illegal in some countries:
Here is a link on how to change it though.
when I go to repair my phone, they normally don't ask why does this happen, they just ask what's the problem. ALso, you have to pretend you are really angry, because the phone broke just 3 days after buying it. That's all. Just be sure that the boot animation is from the stock ROM, as well as the currently installed ROM.

Good deal, had phone exchanged for a new one. That should serve as a lesson to those trying to screw with their efs/ that sometimes it may actually NOT work!!
Thanks guys Cheers!