Database Users

[TUT] Guide for newbies installing: [ROM] CM 6.1.3 V054 720p by WolfBreak

Click here for WolfBreak his original thread. All credits for this GREAT ROM to WolfBreak!
A picture of his ROM:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To get that awsome digital clock widget, take a look here.
Now let's get to installing WolfBreak his ROM.
---------------------------------------------------------------------
First of get your x10 rooted with xRecovery installed. (To root and install xRecovery very easy just use FlashTool)
You will also need baseband .54 or .58 for the best stability! I'm using after a long while baseband .58. It gives me a better battery life and performance!
Now download WolfBreak his ROM from here.
After downloading it, put the zip file on your SD-card.
Boot into xRecovery (Turn your phone of, then turn it on and on white S.E. logo press the back buttong a few times)
Now make sure you do the following to prevent battery drain and force closes:
1. Factory Reset (Full Wipe)
2. Wipe Cache
3. Wipe Dalvik Cache
4. Wipe Battery Stats
Make sure you do it in this order! Doing not can cause battery drain and force closes.
Go to install custom zip and choose the zip file you just put on your SD-card.
Let it copy the files, when it's done press on reboot phone and you're good to go!
Don't forget to say thanks!
Succes & Regards,
PlayGunsta

i love wolbreaks rom been using it for ages now. the only problem is occasionally the top half of the screen stops responding and requires reboot. the other is that the location of the hold button during a call it keeps getting pressed by my ear!
great work any way

rojdag said:
i love wolbreaks rom been using it for ages now. the only problem is occasionally the top half of the screen stops responding and requires reboot. the other is that the location of the hold button during a call it keeps getting pressed by my ear!
great work any way
Click to expand...
Click to collapse
I think that not responding touchscreen is fixed in v06! Not having this problem anymore. Only bug i've found on v06 is a very annoying wi-fi bug.

PlayGunsta said:
Click here for WolfBreak his original thread. All credits for this GREAT ROM to WolfBreak!
A picture of his ROM:
To get that awsome digital clock widget, take a look here.
Now let's get to installing WolfBreak his ROM.
---------------------------------------------------------------------
First of get your x10 rooted with xRecovery installed. (To root and install xRecovery very easy just use FlashTool)
You will also need baseband .54 or .58 for the best stability! I'm using after a long while baseband .58. It gives me a better battery life and performance!
Now download WolfBreak his ROM from here.
After downloading it, put the zip file on your SD-card.
Boot into xRecovery (Turn your phone of, then turn it on and on white S.E. logo press the back buttong a few times)
Now make sure you do the following to prevent battery drain and force closes:
1. Factory Reset (Full Wipe)
2. Wipe Cache
3. Wipe Dalvik Cache
4. Wipe Battery Stats
Make sure you do it in this order! Doing not can cause battery drain and force closes.
Go to install custom zip and choose the zip file you just put on your SD-card.
Let it copy the files, when it's done press on reboot phone and you're good to go!
Don't forget to say thanks!
Succes & Regards,
PlayGunsta
Click to expand...
Click to collapse
What is the baseband? and how do i get that in my phone? And does the wi fi work well?

My 3g is not working.I am not getting 3g signal on my phone.
3g activated
bb54
wolfrom v054

Brunop10 said:
What is the baseband? and how do i get that in my phone? And does the wi fi work well?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=960527 there you can find baseband

Ankit Tulsian said:
My 3g is not working.I am not getting 3g signal on my phone.
3g activated
bb54
wolfrom v054
Click to expand...
Click to collapse
you've to put your apn settings in your phone. look in the general section for global settings.

rojdag said:
i love wolbreaks rom been using it for ages now. the only problem is occasionally the top half of the screen stops responding and requires reboot. the other is that the location of the hold button during a call it keeps getting pressed by my ear!
great work any way
Click to expand...
Click to collapse
What do you mean by pressing the hold button with your ear?
I can't seem to finish a phone call with this phone. It always ends up with the other side saying "hello hello, I can't hear you anymore" and then they hang up. You got the same thing?
Is there any way the proximity sensor is not 'sensitive' enough?

I think it's much easier to flash the Baseband patch included in the original thread, than changing your baseband
At least that's what I did

Maybe I'm being completely stupid here, I've had a look around and have now reflashed my x10 several times. I'm wanting to install Wolfbreaks ROM
Currently
Xperia x10i 2.1-update1
Baseband 2.0.49
Build 2.0.2.A.0.24
I've grabbed the 58 baseband linked above, no matter what I try though I get unknown and no radio
I am using the firmware linked from reindiero, then after flashing that then reflashing the 58 update, but cannot get it to work
Should I start with a different firmware?
Can I recompile the ftf file with the added parts from the 58 baseband update?
Any help appreciated
cheers

latino147 said:
What do you mean by pressing the hold button with your ear?
I can't seem to finish a phone call with this phone. It always ends up with the other side saying "hello hello, I can't hear you anymore" and then they hang up. You got the same thing?
Is there any way the proximity sensor is not 'sensitive' enough?
Click to expand...
Click to collapse
the problem is because the "Hold" button is right where my ear is and thus it always gets pressed. I went into call settings and checked "always use prox sensor" (or smthing to that effect) and that seemed to help a bit

Ignore me guys, I found a few other guides and have been able to get myself up and running. Not yet sure how much I'm loving this Rom, but I'm sure it'll grow on me, a couple of teething issues and a big world to explore
As a complete noob I found it helpful to read a lot of this post, it's basically a complete index of how tos for the x10. It allowed me to see hoe certain things gelled together

I've install it work greets but only 1bug if wifi on it goes reboot and reboot and reboot ect.
Why do it do this....or what i did wrong.

V06 soon wolfbreak is working on custom kernel and adding some nice tweaks!!! Good job wolfbreak for this beautiful rom awesome!
Sent from my X10i using XDA App

I wanted to post in the dev thread but I don't have the rep. Any way... I tried install on .58 base brand and after a few minutes my phone SIM pin locked. after fumbling around I gave up and flashed stock 2.1 upped to BB .55. first day crazy battery drain. Left it charging for awhile. next day zero issues so far. ATT in Michigan. much love xda much live devs. Will buy beers soon
Edit,
little unclear that after I flashed stock (using windows and flashtool) I reflashed cm 6.1.3 v054 720p using xrecovery.
Edit
Sorry watching wings distracted.... the sim pin lock survived a xrecovery restore of my back up. Prob due to .58 BB so in short I don't suggest .58 to Michigan ATT users. which may be a DUH NOOB suggestion idk

Hi guys im all new to android and on a xperia x10i. i installed this ROM yesterday and it works mush faster than the 2.1 provided by SE.
There were a few issues with the proximity sensor and stuff which i managed to over. All though there is an issue with the contacts. i cannot click on any contact it force closes.
any tip on this?
thanks

Anyone cal help me please?

breakneck001 said:
Hi guys im all new to android and on a xperia x10i. i installed this ROM yesterday and it works mush faster than the 2.1 provided by SE.
There were a few issues with the proximity sensor and stuff which i managed to over. All though there is an issue with the contacts. i cannot click on any contact it force closes.
any tip on this?
thanks
Click to expand...
Click to collapse
I had that problem too, it was the 'infinitiview' that FC'ed. I couldn't uninstall it, so I installed another dialer and when I chose a contact it asked to use the dialer OR the infinityview. Offcourse you DON't choose infinity
What where the issues you were having with the proximity sensor?

latino147 said:
I had that problem too, it was the 'infinitiview' that FC'ed. I couldn't uninstall it, so I installed another dialer and when I chose a contact it asked to use the dialer OR the infinityview. Offcourse you DON't choose infinity
What where the issues you were having with the proximity sensor?
Click to expand...
Click to collapse
Thanks for your reply. so whats is the solution that you would recommend for the contacts issue?
As for the proximity sensor, is didnt respond at times. so the display was on while i was on a call. for that i just installed a app from the market which fixed it.
So now im back on 2.1 because of the contacts issue i had. too bad coz the rom was super fast than the stock 2.1

from several posts i have read i understand its the kernel file which holds the screen sensitivity and other operations speeds right. I'm sorry im kinda new to the whole things so please bare with me.
Is there a way that i can overwrite or mod the existing kernel of 2.1 stock?

CM7 Wifi Error

My post count is low or I would be posting this in the CM7 thread.
I upgraded from Alien, and wifi worked then, but it now gives me an error in CM7(as in it doesn't work, and just says "error"). It does the same with bluetooth. The cell data connection works.
To fix this, would I need to reinstall CM7 or the radio or what? Thanks!

Did you follow instructions and clear everything before installing CM7? (Like the cache and dalvik cache?)

Yes, I have wiped everything, before and after the installation(I've tried reinstalling several times since, with no change). I'm also curious about which kernel to use... Does it come with it's own..?

jefesaurus said:
Yes, I have wiped everything, before and after the installation(I've tried reinstalling several times since, with no change). I'm also curious about which kernel to use... Does it come with it's own..?
Click to expand...
Click to collapse
it comes with its own

I had this issue as well. It is not a good sign that the bluetooth is not turning on either. For me, it was a hardware issue and I had to get a replacement. Try reinstalling kernel/wiping dalvik cache. If that doesn't work, try a fresh install of stock 1.8.3 or alien. If that doesn't work, you are SOL.

I've had this a couple times. It seems to be related to something with ext4 and the kernel. Try downloading the faux 1.9 kernel and re-installing that, if not, you could try re-installing the rom. If all that still doesn't work, try wiping everything from fastboot, and do a re-install from scratch. I really doubt it's hardware related. I"ve had this error twice and each time it was related to the kernel.
Make sure you have the right recovery installed too. I'm just thinking as I type this that that may be related. You can use the version from rom manager if you want.
Fastboot commands to wipe everything so you can start from scratch.
fastboot erase system
fastboot erase userdata
fastboot erase boot
fastboot erase cache
fastboot erase preinstall
fastboot erase webtop
Good luck!
Edit, you didn't say which version of the atrix you have, but It might be an idea to download the corresponding radio for your phone.
For example, I have a bell atrix, and my install would go as follows:
I would wipe the phone using fastboot, then install the cm7 zip file, then install the faux 1.9 kernel, and then install the latest bell radio.

Anamnesis said:
I've had this a couple times. It seems to be related to something with ext4 and the kernel. Try downloading the faux 1.9 kernel and re-installing that, if not, you could try re-installing the rom. If all that still doesn't work, try wiping everything from fastboot, and do a re-install from scratch. I really doubt it's hardware related. I"ve had this error twice and each time it was related to the kernel.
Make sure you have the right recovery installed too. I'm just thinking as I type this that that may be related. You can use the version from rom manager if you want.
Fastboot commands to wipe everything so you can start from scratch.
fastboot erase system
fastboot erase userdata
fastboot erase boot
fastboot erase cache
fastboot erase preinstall
fastboot erase webtop
Good luck!
Edit, you didn't say which version of the atrix you have, but It might be an idea to download the corresponding radio for your phone.
For example, I have a bell atrix, and my install would go as follows:
I would wipe the phone using fastboot, then install the cm7 zip file, then install the faux 1.9 kernel, and then install the latest bell radio.
Click to expand...
Click to collapse
I agree with everything except installing faux's 1.9 kernel. It's not optimized for the CM7 beta, so I would recommend against that.

So are you trying to say I didn't have a hardware problem? Re-installing stock 9 times (using the fastboot erase commands) and even flashing back to 1.8.3 did not solve my bluetooth/wifi issue. I've heard of people having the wifi error, but no trouble with bluetooth. The OP is having both, which is what I had. The only way I could get it to work (for 10/15 minutes) was to rub the back of the phone under the cover. It would work, connect, and then the wifi module would crap out.

I didn't realize that, sorry. I'm running it with no issues, but if your having issues then I would listen to Kraise.
---------- Post added at 03:48 AM ---------- Previous post was at 03:44 AM ----------
jiggytom said:
So are you trying to say I didn't have a hardware problem? Re-installing stock 9 times (using the fastboot erase commands) and even flashing back to 1.8.3 did not solve my bluetooth/wifi issue. I've heard of people having the wifi error, but no trouble with bluetooth. The OP is having both, which is what I had. The only way I could get it to work (for 10/15 minutes) was to rub the back of the phone under the cover. It would work, connect, and then the wifi module would crap out.
Click to expand...
Click to collapse
I'm not sure if my Bluetooth was or wasn't working when I had the issue. I have horrible reception in my condo so when I have issues with wifi I try to fix it immediately. Yours sounds like hardware.
To be honest though, my suggestions were directed at the OP. He JUST installed a new rom, and it was all working previously. The bluetooth, wifi, 3g, ect are all part of the radio. It seems much more likely to be related to software than hardware, as others have had the same problems. You really seem to take what I said personally, like it was an attack on you or something, but I was honestly just trying to help out and contribute in a positive fashion. My comments could not have been directed at you, as you didn't even post what your experiences were in the thread. Try to chill out a bit.

I was having issues with my wifi and bluetooth out of nowhere before I ever unlocked or rooted my phone. It was a little over a month after AT&T/Motorola released the Gingerblur(2.3.4) update to my phone which I had to download using a wifi connection. Out of nowhere, it stopped working... Bluetooth would not turn on, and Wifi always says "error" underneath it. I believe mine may actually be a hardware related issue.

DAMN! I just started experiencing this. Bluetooth won't turn on and Wifi "ERROR." This came out of no where. Actually, thinking back, I dropped my phone this AM, but I am almost 100% sure it was working after that.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Kraize said:
I agree with everything except installing faux's 1.9 kernel. It's not optimized for the CM7 beta, so I would recommend against that.
Click to expand...
Click to collapse
Try the Faux 1.0GHz stopgap kernel. I use that and it works better for me with CM7 than the packaged kernel because you can UV.

J-man67 said:
DAMN! I just started experiencing this. Bluetooth won't turn on and Wifi "ERROR." This came out of no where. Actually, thinking back, I dropped my phone this AM, but I am almost 100% sure it was working after that.
Click to expand...
Click to collapse
check if you have the correct permissions for /data/misc/wifi/wpa_supplicant.conf. Try fixing permissions first through ROM Manager. Hope it helps.

Yeah, I was looking into that and modified/changed some settings around to no avail. I am going to try wiping and re-flashing and starting from scratch. It may be related to me dropping it this am. Wasn't a big fall, but that it the only thing I can think of at this point.

PHUCK!!! Just completed a COMPLETE wipe and re-install and same thing. Looks I am picking up a set of tools to crack this baby open. Maybe the lead from the radio to the board became disconnected when I dropped it. Worth a shot before I rely on Best Buy to warranty exchange it.

J-man67 said:
PHUCK!!! Just completed a COMPLETE wipe and re-install and same thing. Looks I am picking up a set of tools to crack this baby open. Maybe the lead from the radio to the board became disconnected when I dropped it. Worth a shot before I rely on Best Buy to warranty exchange it.
Click to expand...
Click to collapse
I have the same error - as I imported the phone, I don't have much in the way of warranty.
This guide shows there's no direct lead from the radio to phone - http://www.ifixit.com/Teardown/Motorola-Atrix-4G-Teardown/4964/2

Thanks! I am going to open her up and make sure that chip is still intact. Might be soldering it back in if need be. Seems that it will be the issue as Bluetooth does not turn on either.

While I haven't had the problem, I have a friend who from what he's telling me has the same WI-Fi error problem ever since updating to the AT&T 2.3.4. He has never rooted or unlocked and wants to update to the new 2.3.6 OTA, but can't due to the Wi-Fi error. Anyone make any headway on a solution?

It's a hardware issue.

Hi,
i experience the same problem with my friend's htc mytouch 3g, when i tried to install cm7 on it,
after that i tried fastboot erase system -w, then installed another ROM to be sure, i found that the WiFi now working fine,
so before opening her up try to install another rom like Dark-Side 2.3.5 or GingerMod 2.3.6, if the problem go away then it's cm related not hardware,

[WIFI Only] [How-to] GT-P1010 Gingerbread Update

I know a lot of people are going to have problems updating to the latest gingerbread build.
PLEASE NOTE: This update will remove root but you can root again with CF-Root from second post.
ALSO, THIS PROCESS WILL WIPE DEVICE!
1) Put your P1010 into download mode (by holding POWER and VOL-DOWN):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2)I went ahead and used ODIN tool to downgrade/upgrade to the latest FROYO firmware before Gingerbread:
P1010XWKC1_OXX
(OEM Flash Guide here)
You should have the same tick marks and files loaded as in my screenshot. Be sure that the box is yellow on the right and you can initiate the firmware install by clicking 'Start'.
3) (VARIES) From there, after restart some people will experience a force close followed by a reboot loop. You will need to flash this kernel via ODIN:
P1010ZHKF1-kernel
(Flash this the same way as above but UNCHECK Re-Partition and CSC!)
4) You will then be able to boot into Froyo.
5) You will use ODIN again to install the Gingerbread update and flash just the PDA (leave CSC blank and leave Re-partition unchecked this time).
P1010XEUKPG
(Flash this the same way you flashed the Kernel in step #2)
6) After it reboots, you will have 2.3.6
7) (Optional) steps in post #2 to install CWM Recovery and Root.

I recommend installing CWM Recovery and CFRoot in the thread below:
ClockWorkMod Recovery for P1010
After you install CWM Recovery, you can do a nandroid backup and never worry about brick again! (=
Also, you can use ES Explorer to mount root and get rid of the Samsung bloatware (AT YOUR OWN RISK!!!)

For those wanting to remove the bloatware (AT YOUR OWN RISK!!!):
You can remove the bloatware with ES Explorer, there's an option to enable 'Root Explorer'. Download the latest version from the Market.
See below:
screenshots are from my Galaxy Nexus but it's the same for any Android 2.2+.
1) Go to the 'Settings' screen
2) Change home directory to '/'
3) Tick the 2 marks on the bottom
4) Browse to /system/app
5) Delete whichever app you don't want, but do it with caution (I usually move these files to /sdcard and move back if it causes any type of force close)
If you totally borked out the system in such a way that you can't boot, you can always move it back in recovery via ADB (much more complicated process but it's possible).
Also, why not do a nandroid backup before messing with deep system files?

Nice! Great topic.

Updated op! =)

this is the best christmas present so far.
edit: worked, almost. thanks ! rooted flashing Skin1980-CF-ROOT-P1010-BETA.tar .
skype isn't using the front camera. =s

Is this for any p1010? Will this work for us models?
Sent from my HTC Flyer P510e using XDA App

r_3 said:
Is this for any p1010? Will this work for us models?
Sent from my HTC Flyer P510e using XDA App
Click to expand...
Click to collapse
It's THE EU ROM but it works with my US P1010.

No restart issues?

r_3 said:
No restart issues?
Click to expand...
Click to collapse
If you followed those steps, the ROM runs stable without any FC's or reboots. I even have setCPU installed on mine.
Also, it's good to note that I'm running CF-Root kernel from the thread in 2nd post.
Plus, you could always downgrade if you run into issues. Just remember to always BACKUP YOUR DATA!

nice!
wow this is good news! does this modded skype work on this: http://forum.xda-developers.com/showpost.php?p=16889575&postcount=1262
or
http://forum.xda-developers.com/showpost.php?p=20697907&postcount=1640
?
I cant try it now as I'm not home. I hope someone could try as so I won't have to think about it until I get home..

@blue_algae: neither the front or the back camera works. tried v11 and v12. so far no luck

densets said:
@blue_algae: neither the front or the back camera works. tried v11 and v12. so far no luck
Click to expand...
Click to collapse
Could you attach the logcat here? or if you could send it directly to theos0o, that'll be great. he's the modder of the skype apps I pasted above.
could you also try this: http://forum.xda-developers.com/showthread.php?t=1153285 this works for me using froyo.

im getting excited about this.. is it really for the p1010 wifi only device? because from what i can see in this subforum is the devs working on the p1000 only. another thing, please don't tell me this is an official update. i don't think the bad sammy will update this little tab.

Depending on where you are freon yes it its the official ireland uk update and makes massive difference as well
Much better tab.
Sent from my GT-P1010 using Tapatalk

skype is working
@densets, skype is working for both skype mods I posted earlier. you just need to enable 'use valid preview'. for droidrx's version, set the app to 'crop' so your video is centered.

phew.. relieved by this news, nevermind if it is not going to be released here in malaysia, at least i can still skype with my family w/o much trouble into getting the ffc to work.

urra901109 said:
phew.. relieved by this news, nevermind if it is not going to be released here in malaysia, at least i can still skype with my family w/o much trouble into getting the ffc to work.
Click to expand...
Click to collapse
hmm, if you are still in froyo, you can use ffc on skype: http://forum.xda-developers.com/showthread.php?t=1153285
just rotate the camera and try out different settings.

sorry for the newbie question, but what's the password for the 2.3.3 file from sammobile?
edit: already found it, my bad

Interestingly, I've followed the guide exactly as mentioned above (had KC1 and the HK kernel from previous flashing) and flashed the PDA for XEU 2.3 from Sammobile, and I'm now stuck in an eternal bootloop. I like the new samsung boot music though, better than the previous one
Any suggestions?
Edit: I wiped data and cache from recovery, flashed KC1 and the Kernel and it boots fine. Checked Kies to be sure and it's offering me FW upgrade to KM2. Should I accept this FW upgrade or just persevere with flashing the new 2.3 firmware?

[Solved] Encryption Unsuccessful error for samsung vibrant.

Ok, Tonight i tried to install ICS Passion rom on my old samsung vibrant( is running bionix 2.2 rom). Following the instruction from ICS Passion rom thread , - First i tried to install CW7 gingerbread rom ( got some boot loop, ..)
- Then i boot to recovery mode again , install ICS passion rom, screen flashed like crazy and got boot loop one more time.
- Reboot to recovery again, reinstall ICS passion , everything went though perfectly this time.
- Finally, my phone booted up and show me this screen ( WTF***** )
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- I tried to press the reset button , phone turned off/on and showed me this screen again. Tried this 3-4 time but nothing changed .
How i solve this problem ?
- I tried to search google to get more information about what is going with my phone. Basically, there are alot of people have exactly same problem as mine.
- I found one instruction that told me to fixed the problem, i need to flash 2.1 stock rom by using ODIN ( download everything from this link: http://androidspin.com/2010/08/09/how-to-restore-or-recover-your-samsung-vibrant/.)
1st Attempt: :
- Open ODIN, load file, put my phone into download mode..Hit start.Nothing happened. ODIN recognized my phone but the process stopped
2nd Attempt: :
- Changed usb port, did exactly same thing , the process now stopped at "analysis file" ..step
3rd Attempt: :
- Looked up google again, someone suggested that using Eugene_2E_JK2_Froyo.tar.md5 instead the stock 2.1 firmware might help. So i downloaded Eugene file, ran ODIN again. Still out of luck, process stopped at "leave CS.." step. At this point, i thought i bricked my phone already. So i unplugged usb cable from my phone. Tried to turn off, turn on my phone again, and it show me this screen (
4th Attempt: :
- I took the battery off, put it in, put my phone into download mode one last time. Open ODIN, load 2.1 stock file this time, hit start button and then BUMP..ODIN started to re-flash the firmware..And now my phone back to stock 2.1 .
P/s:
- sorry for my English, but hope this might help other people who get this error when trying to install ICS on their Vibrant.
- Any suggestion for me to install ICS again in correct way ? Thank in advance!

Does your internal sd card mount and can you access it? If yes, then you probably are the first one to get through this error. Congrats! Eugene's froyo has saved many many phones.
Edit: Strike that, it was a silly question.

No no really, do you have access to everything?? Cause i havent heard of a single person yet that got thru this bug with their sd card intact
Sent from a cell tower to the XDA server to you.

Finally, I successfully installed ICS on my vibrant. When i open setting, storage, it show my internal internal storage(about 2GB) - usb storage (about 14GB) - and my 8GB external sdcard. When i connect my phone to my computer, turn on usb storage, i can acces internal SD and external SD card ( can copy, paste, transfer files..) The gallery is able to show/view/play both video and image i have on my internal-external SD card but i can only access the internal one. I tried to find the external SD card but don't know where is it located. Is it mount as folder external_sd ?
****************
Ok, i found it. On ICS, the external sd card is mount as /emmc. Now i am able to access both of them. Nothing is broken in here.

In Passion your external is now EMMC.
So you can get to your internal just fine? When you pull up settings->storage you get readings for internal AND external.

Woodrube said:
In Passion your external is now EMMC.
So you can get to your internal just fine? When you pull up settings->storage you get readings for internal AND external.
Click to expand...
Click to collapse
Yes, it show me both internal and external.

tritran18518 said:
Yes, it show me both internal and external.
Click to expand...
Click to collapse
Now the question is...were you able to recover all your data from your internal storage? Or did it get wiped out in the process?
I wouldn't necessarily say you have solved the bug. I would rather say...you are extremely lucky sir The reason why i say that is because i could flash back to 2.1 as you did in your 4th attempt and would still get the same results (bootloop). I would really like to know what it was that you did...i have tried everything you've mentioned in your post numerous times in the past and still haven't found a proper fix for this bug. From your post it appears to be more like trial and error...in other words you just got lucky and somehow fixed your phone. Can you please elaborate and be more specific as to what you did. I and the many other people affected by this bug could really use your help since you are probably the only person who has successfully squashed the bug so to speak.
Good to hear your phone is functioning properly. This could only be good news.
Sent from my Galaxy Nexus using XDA

Merio90 said:
Now the question is...were you able to recover all your data from your internal storage? Or did it get wiped out in the process?
I wouldn't necessarily say you have solved the bug. I would rather say...you are extremely lucky sir The reason why i say that is because i could flash back to 2.1 as you did in your 4th attempt and would still get the same results (bootloop). I would really like to know what it was that you did...i have tried everything you've mentioned in your post numerous times in the past and still haven't found a proper fix for this bug. From your post it appears to be more like trial and error...in other words you just got lucky and somehow fixed your phone. Can you please elaborate and be more specific as to what you did. I and the many other people affected by this bug could really use your help since you are probably the only person who has successfully squashed the bug so to speak.
Good to hear your phone is functioning properly. This could only be good news.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
- Because i did a factory reset so all kind of system data is clear, but photo, video, music...other files in both external and internal sd card still there and accessable. Just like you wipe your phone when you install a new rom.
- I think the key in here is :
+ i got the error message, and i tried to press the reset button 3-4 times without take off my sd-card from my phone. And it's still give the error message
+ I odin to stock 2.1 . fail - tried 2 time
+ change usb port, flash 2.1 again. fail - tried 2 time
+ flash eugene 2.2 ...fail. And while my phone still show me the downloading screen , i just took battery off, put it on, turned on and it show me the new screen ( computer-phone)
+ turn off, put to download mode, flash 2.1 again and success.
==> that is pretty much everything i remember. And i'm sure i remember it right.

Passion is based on an early cm9 base. Until they update I feel you would be better off flashing cm9 since it has nightly updates now.(nightlies)

ferhanmm said:
Passion is based on an early cm9 base. Until they update I feel you would be better off flashing cm9 since it has nightly updates now.(nightlies)
Click to expand...
Click to collapse
i always pick rom base on the view of rom's thread. roms updated daily doesn't mean it is more stable than other roms ( this is what i learn from XDA)

This bug seems to happen with several diff ics roms, not just passions....
If i may venture my uneducated guess as to what happened to you:
As your odin was writing something on your phone and you pulled the batt, you corrupted the data... that means that the encrypted data and all that stuff got wiped on the next attempt and its like you had a new phone..
Prob wrong tho
Sent from a cell tower to the XDA server to you.

tritran18518 said:
i always pick rom base on the view of rom's thread. roms updated daily doesn't mean it is more stable than other roms ( this is what i learn from XDA)
Click to expand...
Click to collapse
Best ics roms out IMO are br1ck'd and team DD's ICZenwich or Team Kangs AOKP build 31, both with MP's sub zero build 61 kernal.
Sent from my SGH-T959 using xda premium

You are a very lucky man. I got mine working with cm7 after bricking it like that just enough to sell to someone as "a portable wifi hotspot for whatever plan you want." For $50
Sent from my SAMSUNG-SGH-T989 using XDA

YESSS!
I had this issue today october/31/2012, i followed OP instructions and it works! Thank you very much. The only difference is that i pressed the reset phone button and when i realized that was a mistake ( you know, when installing something and you just click and say:yeah, yeah, whats next?) i pulled out the battery as soon as i can, i searched on the web, found this thread and instead of flashing stock firmware (eclair) i flashed froyo straight.
I hope this helps somebody like it help me.

So you have access to your internal SD?
Also what ROM were you running?
Did it happen after flashing or was it random?
Please give as much info as possible as this issue (EU) is still, for the most part, a bit of an enigma.
I approve this message.

Hello there
Yes, i have access to internal and external sd card
Before the issue I was running chimera v2.2 and chimera kernel but i wanted to flash aokp lastest releases so i used odin to stock, then flashed cm7 (here it give me bootloops but i just went to next step) then chimera 2.2 (here was when EU appears, my intention was after flashing chimera 2.2 flash aokp )
If you need more details just ask me.

You're actually very fortunate to still have Int SD access esp. after pressing the EU reset button. Since EU has been primarily associated with ICS for our Vibes (and theoretically wiping /data with CWM5), you can just skip Chimera altogether. After restocking and flashing CM7 (vibrantmtd), either go straight to AOKP JB or use a recent CM10 as an interim flash.

I know im fortunate, the reason i pulled out the battery after pressing the reset button is because i knew about the EU issue.
About flashing CM7 and then AOKP JB i did not know that i can do it that way, thank you.

Hard bricked 7.7

Hi guys
I've just bricked my tab. I flashed ICS to try it then I did a Factory reset and the tab was bricked.
I can access the Download mode, but when I put any firmware into Odin PDA the flashing process get stuck shortly after " NAND Write Start!! " at the beganing of "factoryfs.img" !
Long story short, my tab is totally bricked is there anything I can do ?? Please help me as this tab is imported and I have no warranty.
Thank you very much, really appreciate the community here.

Coolman4now said:
Hi guys
I've just bricked my tab. I flashed ICS to try it then I did a Factory reset and the tab was bricked.
I can access the Download mode, but when I put any firmware into Odin PDA the flashing process get stuck shortly after " NAND Write Start!! " at the beganing of "factoryfs.img" !
Long story short, my tab is totally bricked is there anything I can do ?? Please help me as this tab is imported and I have no warranty.
Thank you very much, really appreciate the community here.
Click to expand...
Click to collapse
As long as you can access the Download mode, you are not hard bricked, just download the rom that your device came with and install through odin, this will be the only image that your tab will accept.

The problem is, the flashing starts normally and as soon as it starts to write the NAND the progress stops then a big red fail appears after a long time.
Thank you for your reply, I'm so desperate right now.

Can you tell us what model and firmware, etc you used to flash? I think you are the first case

maybe ur firmware is corrupt?try downloading a new one...as long u can acces download mode it is softbrick

Luckily I have a screenshot of the previous firmware
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I downloaded lots of firmware an none gets past the factoryFS

Did you do the factory reset while you were on ICS? Did you have CWM or root at all previously and/or after installation of ICS?

Hmmm...Curious. Any flashing program to be tried, other than Odin? If everything else fails, probably the flash ROM chip has gone bad like it did on my Xperia x10. Send it in for warranty, if possible, and tell them.you left it charging.overnight and it didn't wake in the morning...
Sent from my LG-P920 using xda app-developers app

I had root before on HC but I did a factory reset before installing ICS, then I flased the Austria ICS build. Then I did a factory reset from recovery and boom the tab can't boot nor can it be flashed ! always gets stuck at Writing NAND.

GRudolf94 said:
Hmmm...Curious. Any flashing program to be tried, other than Odin? If everything else fails, probably the flash ROM chip has gone bad like it did on my Xperia x10. Send it in for warranty, if possible, and tell them.you left it charging.overnight and it didn't wake in the morning...
Sent from my LG-P920 using xda app-developers app
Click to expand...
Click to collapse
To add insult to the injury, it's imported and I have no warranty. :good:

what you need to do is
You have super brick and not hard brick.what you need to do re partition using .pit file and then flash the room again. I had thus same issue and repartition worked for m e. How it helps

Well, you should contact service support anyway. Samsung generally doesn't care too much if the product was bought in another country...And a friend of had his Brazilian Tab 10.1 repaired in the UK, touchscreen problem, replaced by new unit free of charge... But, try another flashing solution first.
Sent from my LG-P920 using xda app-developers app

This looks like it is probably the super brick that people experienced on the note. We are luckier than the note because we have a dedicated recovery partition, so you can avoid the super brick by using a different recovery (such as the honeycomb recovery or CWM) and still use stock ICS as your rom.
As long as you don't use the stock ICS recovery for wiping/factory reset, you will be fine.

om0 said:
You have super brick and not hard brick.what you need to do re partition using .pit file and then flash the room again. I had thus same issue and repartition worked for m e. How it helps
Click to expand...
Click to collapse
How did you flash the pit file? Do you still have it?
Instructions please!
My battery actually died too - how can you charge it? D=

locerra said:
This looks like it is probably the super brick that people experienced on the note. We are luckier than the note because we have a dedicated recovery partition, so you can avoid the super brick by using a different recovery (such as the honeycomb recovery or CWM) and still use stock ICS as your rom.
As long as you don't use the stock ICS recovery for wiping/factory reset, you will be fine.
Click to expand...
Click to collapse
I guess that's not the case. Odin would overwrite all the partitions, including recovery...So device should act like factory new. However, flashing programs are often troublesome...
Sent from my LG-P920 using xda app-developers app

why not trying to let the battery run out first?

GRudolf94 said:
I guess that's not the case. Odin would overwrite all the partitions, including recovery...So device should act like factory new. However, flashing programs are often troublesome...
Click to expand...
Click to collapse
The initial post said that he did a factory reset, and then used Odin. The super brick is caused by using factory reset/wiping on recovery's built on un-safegarded kernels (the bug is actually in the firmware, but you can work around the bug by disabling a setting in the kernel). My guess is that the stock recovery with the ICS is built on an un-safegarded kernel.
I would seriously recommend that people go read up on the super brick, it affects our many (most?) of the Tab 7.7s out there. If you experience it, you better hope that Samsung support likes you.

I have tried the pit file lots of times, the flashing stops as soon as writing NAND starts.

Coolman4now said:
I have tried the pit file lots of times, the flashing stops as soon as writing NAND starts.
Click to expand...
Click to collapse
It looks like your NAND is cooked.
Have a look at ths http://forum.xda-developers.com/showthread.php?t=1682444

So Im blessed with a fried NAND Nice
Does anyone have the correct PIT file please ?