Database Info

[Q] reboot loop

My g2x keeps rebooting over and over again! This happened after i mounted it to my pc. it tries to read my sd card then just reboots over and over again. I have nv flash and tried to restore old back up but still does it. can any one help im thinking i need to flash stock.

you need to do a factory reset if your nandroid backup doesn't work. if that doesn't work reflash the rom.

I already did a factory reset and wipe and tried to re install the rom. it just continues to reboot. It starts up and if quick i can get into my lock screen and access things but within seconds it reboots and continues to do that

What rom are you using?

jcbofkc said:
What rom are you using?[/QUOTE
I was on a stock rooted rom when the problem happened. so i then i did a restore. when that didnt work i reflashed the stock rom that was posted on forum. i think it has something to do with my internal memory which i cannot access. this all happened when i was trying to back up my sd card while in usb and it just got an error when i unplugged it enless reboot.
Click to expand...
Click to collapse

I was hoping it was something simple like undervolting with a custom rom. I wish I could help. It sounds like you tried everything I would recomend. Maybe one of the real Android techie type guys can help you. I am still learning myself.

jcbofkc said:
I was hoping it was something simple like undervolting with a custom rom. I wish I could help. It sounds like you tried everything I would recomend. Maybe one of the real Android techie type guys can help you. I am still learning myself.
Click to expand...
Click to collapse
Thanks anyway! I even when as far as to re-flash stock recovery and then try to factory reset it but still did not work. I just dont know what the heck happened. So today I went to t-mobile and they r sending me a new phone and for know I have a loaner 10 days until I get the new phone they said it was backordered. oh well

[Q] Boot loop or Brick? HELP?

GOT IT FIXED
Thanks to fabricatedhero for the brain pulse to try and just root it!
First this isnt my G2X, I am trying to help a co-worker. She isnt Tech-savy by any means... lol... any way here is her story:
She got the OTA pop-up and thought it was a virus (yeah shes that smart) then she said she accepted the update as it kept asking. She started the update and it took hours over night and it never finished she said so she pulled the battery durring the s/w update screen. Then it started the boot loop.
Now my story:
The G2x is bone-stock
I did the NVflash successfully... Flashed the stock recovery via:http://forum.xda-developers.com/showthread.php?t=1056847 ... Still have the boot loop issue and wont boot into recovery. I searched and even Googled and everything is the same, and of which nothign is working for me.
I tried to maybe catch something from the boop loop and also from the S/W update screen... NOTHING... Clearly this is software issue; The only thing I have yet to confirm is if I place the stock update on sd card and see if itll pick that up.
The issue I see there is I cant google for the life of me what the "special" name of the update would be called. Nor do I have a clue what to really call it. I know for most phones its NOT "update.zip" more like "espring13" or somethign like that...
Can any Jedi MAster help me? Thanks!
ok found the file name:
LG-P999-V10f.zip
Still boot-looping and that didnt work...

resources
http://theunlockr.com/2011/05/23/how-to-unroot-the-t-mobile-g2x/

Use. The nvflasher to put Cwm on it and go under restore and re-format sd, cache, and etc
Then go and do gummans froyo 2.2 stock rooted rom
Also there's a post about how to do the GB update on here as well.
Sent from my LG-P999 using XDA Premium App

Did you try a simple factory reset? If you still have stock recovery and rom try holding volume up + power until the reset process begins.
G2X CM7

So I will have to root the device? I guess that makes sense...
Keep in mind I cant get into stock recovery period...
cwm worked! wipped everything, still nothing, gonna flash a new rom
update:
ok SDcard doesnt show have to mount internal storage to apply update... *crosses fingers*
**worked running newest nightly of CM7 with CWM recovery

[Q] Unrooted stock bootloop - need help

Recently my Nexus s started bootlooping.
First it was happening if the phone was powered off due to finished battery, now it happens every time i power it off.
What happens is, it bootloop on the google logo. In order to over come that i pull the battery out and turn it back on. After a few time (3-10) it would start up normally and not bootlooping.
I run stock 4.0.3, not rooted.
Anyone has a clue ?

iglu said:
Recently my Nexus s started bootlooping.
First it was happening if the phone was powered off due to finished battery, now it happens every time i power it off.
What happens is, it bootloop on the google logo. In order to over come that i pull the battery out and turn it back on. After a few time (3-10) it would start up normally and not bootlooping.
I run stock 4.0.3, not rooted.
Anyone has a clue ?
Click to expand...
Click to collapse
my only suggestion is maybe a factory reset, you might have some corrupted files somewhere. but, my fear/concern is that your internal sd storage card might be going.

And if a factory reset didn't work, I think you'll have to use ODIN to flash stock 2.3.6 ...

simms22 said:
my only suggestion is maybe a factory reset, you might have some corrupted files somewhere. but, my fear/concern is that your internal sd storage card might be going.
Click to expand...
Click to collapse
What is lost on factory reset ? only the OS and installed apps, no SD data right ?
TheMatrix246 said:
And if a factory reset didn't work, I think you'll have to use ODIN to flash stock 2.3.6 ...
Click to expand...
Click to collapse
You think it might be a result of ICS upgrade ?

iglu said:
What is lost on factory reset ? only the OS and installed apps, no SD data right ?
You think it might be a result of ICS upgrade ?
Click to expand...
Click to collapse
Yes factory data reset only deletes all data on your phone not the SD card.
Sent from my Galaxy Nexus using xda premium

simms22 said:
my only suggestion is maybe a factory reset, you might have some corrupted files somewhere. but, my fear/concern is that your internal sd storage card might be going.
Click to expand...
Click to collapse
TheMatrix246 said:
And if a factory reset didn't work, I think you'll have to use ODIN to flash stock 2.3.6 ...
Click to expand...
Click to collapse
Okay, so i did factory reset and i'm still stuck on the bootloop. Need to remove the battery and turn back on until it doesn't bootloop.
Actually what happens is the google logo appear, then for a moment it turned off and comes back again.
simms22, why do you think it's internal sd damage ?
TheMatrix246, what's ODIN ?

Guys, you think if i root and switch ROM it could be fixed ?
I would appreciate some help here a bit lost.

One last thing before you contact Samsung:
Download Nexus S [i9020T/i9023] 4.0.3 Full ROM and copy to sdcard as update.zip
Go into bootloader
Recovery
Data/factory reset
Install update.zip (reflash all files of ICS)
Reboot and hope it works out fine
If this doesn't work for you i highly doubt rooting and changing ROMs will. This will reinstall the entire OS (format and install /system), bootloader, radio, kernel and recovery.

Do i need to be root user in order to do that ?
And just to make sure, this Full ROM is for i9020T ? correct ?
(mine says only GT-i9020 on the back, bought in Carphone Warehouse in England).

Yes, i9020T. If you get 3G with Orange, and you have the SAMOLED screen, you have the i9020T (and to my knowledge, 9020 on the back signifies i9020T).
Also, i don't believe you need to be root to do that. I'm pretty sure you can flash the same version ROM from stock recovery as long as it is signed, just not older versions.

First, thanks guys for the help.
After first doing the factory reset, it seemed the bootloop happens less often. At first i tought it was solved but then it rarely (1 to 5 reboots) yet happened.
Today i installed the Full ROM Harbb suggested and so far i have no reboot issues.
But i after the installation i saw OS wasn't reset. Does it suppose to (not) happen ?

iglu said:
First, thanks guys for the help.
...
...
...
But i after the installation i saw OS wasn't reset. Does it suppose to (not) happen ?
Click to expand...
Click to collapse
You're welcome. Also, all that file does is replace everything in the /system partition (OS). All apps besides the defaults that come from the factory are not in that partition so are not affected. Hopefully your problem is fixed permanently

But it's generally recommended to do a full wipe when switching ROMs. It could be that you encounter other problems because of the ROM change without wipe. But you could also be lucky to have no problems. Just to remind you, when you encounter something wierd.

Problem is still there ....
Hi guys,
First thanks for all the help, but the problem still there.
I did the upgrade using the Full ROM as Harbb suggested. For the first 10-12 times i rebooted (i rebooted again and again) it was alright, booting successfully ... but then it stated occasionally to bootloop and now it does it almost everytime. usually takes up to 10 times i remove the battery and start the phone so it will start up and not bootloop.
Also, I'm sorry the taking so long to respond, the nature of the problem compelling me to test it for a few days so i will know if it works or not.
Should i root the device ?
If so , how do i replace / rewrite the boot program ?
I would much appreciate any suggestion.

I had a similar problem, bootlooping, stuck on Google logo when running 4.0.3 in the end I took it back to carphone warehouse who repaired it and now it's ok. I found that heating it with a hair-dryer made it stop bootlooping (but that's what worked for me). However the repair seems to have fixed any issues and its all OK now.

BlatDinger said:
I had a similar problem, bootlooping, stuck on Google logo when running 4.0.3 in the end I took it back to carphone warehouse who repaired it and now it's ok. I found that heating it with a hair-dryer made it stop bootlooping (but that's what worked for me). However the repair seems to have fixed any issues and its all OK now.
Click to expand...
Click to collapse
My problem is i bought the device also in carphone warehouse in the UK, but i live in Israel. Meaning i will have to send it to them by air-mail.
By any chance they mentioned what was the problem ?
also did they give you a refurbished device or a new one ?

iglu said:
My problem is i bought the device also in carphone warehouse in the UK, but i live in Israel. Meaning i will have to send it to them by air-mail.
By any chance they mentioned what was the problem ?
also did they give you a refurbished device or a new one ?
Click to expand...
Click to collapse
Most likely its a refurbished one, as is the way of sending devices for warranty
Sent from my ice cream powered Nexus S

Sorry for slow reply - they said they 'flashed it' and it came back unlocked but I believe its still the same handset and I've no idea how they did it soz.
Sent from my Nexus S using xda premium

BlatDinger said:
Sorry for slow reply - they said they 'flashed it' and it came back unlocked but I believe its still the same handset and I've no idea how they did it soz.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Hey, thanks for the replay.
What does is mean to flash it ?
How do i do that ?
You noted it was returned unrooted, was it rooted before ?
Again thank you all for the help.

To be honest I'm a novice to these terms but know that they unlocked it(it was not unlocked when sent off) and reinstalled os 2.3.3 after a complete wipe. Details of how to unlock and flash (install a different os) are on the forums. If you follow the forum advice precisely the instructions work. I am now running a CyberGR rom of ics 4.0.3 that runs smoother than stock ics . Again found on these forums. Hope this helps.
Sent from my Nexus S using xda premium

Bootloops with any Rom, PLEASE HELP..!!

guys I have a serious problem..!!
I was in 5.1.8 everything was fine non a problem and when 5.5 came out I installed it, super wipe script, and install the Rom; I was getting a lot of boot loops. Reinstall the ROM again full wiping, ans still the same. I came back to 5.1.8 and I'm still having boot loops but not that often like it was in 5.5, now I have boot loops when turn on the data or when I try to make a call... I really don't know what could be the problem because I have installed hundreds of roms with the same steps and everything was fine,.I don't know what could be the problem...
I hope someone could help me thanks a lot
from my HTC Sensation XE with Beats Audio using xda premium

renehd2 said:
guys I have a serious problem..!!
I was in 5.1.8 everything was fine non a problem and when 5.5 came out I installed it, super wipe script, and install the Rom; I was getting a lot of boot loops. Reinstall the ROM again full wiping, ans still the same. I came back to 5.1.8 and I'm still having boot loops but not that often like it was in 5.5, now I have boot loops when turn on the data or when I try to make a call... I really don't know what could be the problem because I have installed hundreds of roms with the same steps and everything was fine,.I don't know what could be the problem...
I hope someone could help me thanks a lot
from my HTC Sensation XE with Beats Audio using xda premium
Click to expand...
Click to collapse
Hi... I once had a similar problem late last year. My phone kept rebooting randomly, sometimes as soon I switch the phone on, or data like yourself. What I did was.... Installed the official RUU that came on my phone (O2) and the rebooting stopped. But I felt the need to send it back anyway, so I did and just as well, because HTC replaced the mainboard and a few other things. I hadn't overclocked or anything either so it was a strange one.
This way worked for me, so give it a go.

I rooted my phone, then unrooted without ever installing a custom rom. I have gotten boot loops ever since and seemingly random shut downs that require me to take out the battery and put it back in before the phone will boot up again. Happens every day, several times a day.

MANTI5 said:
I rooted my phone, then unrooted without ever installing a custom rom. I have gotten boot loops ever since and seemingly random shut downs that require me to take out the battery and put it back in before the phone will boot up again. Happens every day, several times a day.
Click to expand...
Click to collapse
When you say rooted and unrooted what exactly did you do?? Meaning did you HTC unlock or use revolutionary to s-off? And what recovery did you use? Because in actuality all root is, is the su binaries and the su app, not the process of gaining the access. There are inherent problems with the htcdev unlock and using cwm as your recovery. Even if you delete su the remnants of either process could possibly cause problems. Did you return to s-on again?? Because that will cause serious issues if you don't have the correct ruu. Did you flash any newer firmwares??? The few before .32 did cause loops without the correct rom.
Also in your case it sounds like a rogue app causing loops because it boots up after a battery pull. Have you tried to factory reset and wipe your data to see if that helps??
Sent from my Sensation using xda premium

renehd2 said:
guys I have a serious problem..!!
I was in 5.1.8 everything was fine non a problem and when 5.5 came out I installed it, super wipe script, and install the Rom; I was getting a lot of boot loops. Reinstall the ROM again full wiping, ans still the same. I came back to 5.1.8 and I'm still having boot loops but not that often like it was in 5.5, now I have boot loops when turn on the data or when I try to make a call... I really don't know what could be the problem because I have installed hundreds of roms with the same steps and everything was fine,.I don't know what could be the problem...
I hope someone could help me thanks a lot
from my HTC Sensation XE with Beats Audio using xda premium
Click to expand...
Click to collapse
it's maybe hardware failure in first place but after doing battery thing it was fine
go here and try battery fix thread plzzz post back and vote in first thread
MANTI5 said:
I rooted my phone, then unrooted without ever installing a custom rom. I have gotten boot loops ever since and seemingly random shut downs that require me to take out the battery and put it back in before the phone will boot up again. Happens every day, several times a day.
Click to expand...
Click to collapse
it's a battery thing go here and try battery fix thread plzzz post back and vote in first thread

Used Revolutionary, not sure what I used to put it back as it's been a while but I followed a guide from here. I'm trying the card piece trick so we'll see if it does anything.

Pm me if your soff I can help easy
Sent from my Sensation using xda premium

Thanks but not s-off anymore and just got another reboot so I doubt it's the battery. I guess I'll try to deal with it until ICS and see if that fixes anything. If not then I guess I'll try something more drastic.

Well get soff you can't fix with out it
Sent from my Sensation using xda premium

Ok, got s-off again.

It seems to have something to do with going in and out of service or switching between wifi and cell service. But that could just be a coincidence.

Anyone have ideas on how to fix this? I got the OTA ICS and I'm still getting reboots.

MANTI5 said:
Anyone have ideas on how to fix this? I got the OTA ICS and I'm still getting reboots.
Click to expand...
Click to collapse
it's a battery thing go here and try battery fix thread plzzz post back and vote in first thread
it won't hurt ur phone u must stick a tape to close the gap between batt pins and connectors do it and see it easy but worth allot

Tried that earlier in this thread and it didn't help.

Anyone else?

Well guys after reading I fixed my problem cleaning the little panels in the battery, and also installing another rom, seems like the htc sense roms have some problems with that because since I install a senseless rom (not aosp) the problem is gone
Sent from my HTC Sensation using xda premium

I think you did not unroot properly. Can you please describe the process you used for unrooting?

Don't remember what guide I used to unroot as it was a while back. It definitely seems to have something to do with the signal. It will lose signal, reboot, get pretty warm and repeat while sometimes just shutting off and needing the battery pulled and put back before it will turn back on. My wife will have a signal just fine in the same areas mine loses them.
Very frustrating because I'm missing a lot of calls and txts because it'll just shut down.

MANTI5 said:
Don't remember what guide I used to unroot as it was a while back. It definitely seems to have something to do with the signal. It will lose signal, reboot, get pretty warm and repeat while sometimes just shutting off and needing the battery pulled and put back before it will turn back on. My wife will have a signal just fine in the same areas mine loses them.
Very frustrating because I'm missing a lot of calls and txts because it'll just shut down.
Click to expand...
Click to collapse
First make a NANDROID backup now. Then try rooting again to see if that fixes the issue.
If not, try to flash a different Radio. I would in your case also suggest wiping all partitions except SD card and re-installing the ROM, after flashing the radio.

[Warning] Ice Cream Sandwich OS Bricks

This thread is now irrelevant as Jellybean is available for the device.​
The old post can be found below:
As of right now be sure that you all are extemely cautious when trying to flash any type of ICS package (be it firmware, a ROM, or any type of system running it). Our tablet may have an issue with ICS as many other galaxy devices have. A bug currently exists that corrupts the mounting of the data partition on the device which *MAY* lead to a permanent hard bricking of your device.
This is currently a very RARE issue, however, those who are not well educated in Android development and that do not know how to 100% reset their tablet should refrain from flashing any type of ICS ROM or ODIN package.
If you have already flashed an ICS ODIN package or are running CM9 safely and have been for a good amount of time, then my guess is that this issue will not effect you, BUT it may strike you at any given time!
For those of you who insist on upgrading to ICS, *PLEASE* backup your entire ROM and make sure that you have the stock HC ODIN package. Although it probably won't help having them if you are hard bricked.​
A quote from an effected user:
ringnutz said:
I also had the can't mount data problem, I tried for 3 days to get it to work. I ended up sending it back to Samsung after reverting everything to stock. I was on cm9 though and one night it just started bootlooping while i was asleep. I.e. it would fully boot then restart after 5 seconds or so. So I tried reverting to stock and trying again, which is when I got the can't mount data issue. I literally tried every combination of wiping, recovery, Odin/heimdall, and the only thing that would get past the Samsung logo was cm9, which would just stick at the boot animation forever. I got tired of messing with it and thought it could have been a hardware problem, so I sent it back under warranty
Sent from my myTouch 4g via Tapatalk
Click to expand...
Click to collapse
A quote from an effected user:
daviddavid123 said:
i installed cm9 and ics 4 then my tab hard bricked and internal memory damaged
Click to expand...
Click to collapse
A quote from an effected user:
krbabb said:
I dont have posting privleges in the developer forums but i thought i would let you know whats up with my tab.
Rooted it, got cwm on it and flashed cm9. Worked for about a week without issue then started the bootlooping issues. I couldnt even wipe the data in recovery.
Used odin to go back to stock HC according to your instructions. Then i thought it bricked cause it just got stuck on the default screen showing galaxy tab. Tried installing HC a few more times but it never booted.
Tried one more time but now with the stock ics. Still nothing so i gave up.
Only thing is i couldnt power off. I planned to let the battery die. So it just sat on the default gakaxy tab screen and about 30 minutes later it showed the samsung boot animation.
I let it sit for another half hour with samsung pulsing. Nothing. So i reboot into recovery (stock) which i couldnt even get to before now, wipe everything like 5 times then reboot the device.
Booted up and works like a charm. I thought this thing wad gone.
Not sure if the stock ics tar file did the trick but let everyone know that mine came back to life. It possible other devices could be bricked but maybe there is a chance for some people.
Sent from my GT-P6210 using xda app-developers app
Click to expand...
Click to collapse
If you have flashed ICS and you have bricked your device I am sorry. I know there are a few people out there who have....
To conclude, everybody please be careful about tinkering with your device. I know ICS has great speed enhancements and all, but as of right now your box of ice cream sandwiches may or may not be poisoned.​
For the daredevils:
CM9 [View thread]
Guide to flashing ICS [View thread]
EDIT: Our case is not the same as the other galaxies.... Ours effects the data partition while theirs effects their emmc... I'm assuming ours may be a bug with the firmware installation / recovery as it was with theirs however I'm not sure why it is effecting users on CM9....
EDIT 2: We should all be cautious and NOT wipe at all using Samsung's ICS Recovery. I was chatting with aorth and he suggested that that may be the cause of the issue. His recovery (or the one I posted in my guide) are safe to wipe on.
EDIT 3: I guess we also have reports of the emmc being corrupted as well...

Just don't wipe data/factory reset using recovery ICS (RECOVERY 3e). Use recovery 5.5.0.4 or 6.0.x.x......only you wipe for up new rom, everything will be OK.
Sent from my GT-P6200 using Tapatalk 2

Yeah, i experienced this type of total brick. I flashed p6200 ics firmware with mobile odin and than did factory reset in ics recovery mode. I think this was the reason of hard brick. After some time tablet did shut down and didn't turn on. Service fixed the problem, they said that main board died.

Ignore this post.

StrumerJohn said:
That's not the case I afraid...
Click to expand...
Click to collapse
I really don't think it was a problem with upgrading. I had been on cm9 for over a month, then I woke up one morning and it was bootlooping. I got all the can't mount data errors afterwards, so it's either a hardware problem or cm9 is somehow magically corrupting the /data partition. I hadn't even installed anything recently
EDIT: Samsung just sent me the email that the repair is finished, they replaced the main board, so it definitely was a hardware problem.
Sent from my myTouch 4g via Tapatalk

This issue was brought up a couple months ago by aorth, I think its in his CM9 thread or in one of the rooting or CWM threads. I don't think it is an issue that will be going away any time soon as Samsung isn't in any hurry to fix it, that is if they even can or want to.

Using stock ICS for almost 3 weeks now.
I was backing up and restoring all of the partitions via CWM 6.0.1.0 two times.
Nothing weird happening for the moment.

I use the ics wipe/factory reset and I don't have any problem, I have 6210 .

Well, aorth entioned sth like this before, here his post:
aorth said:
Maybe you guys have heard, but some early ICS ROMs for Galaxy Note and other similar Galaxy S II variants have triggered hard bricks due to faulty MMC firmware handling erase commands improperly. I never bothered to read up about the issue until now, but it looks like we should also be careful.
Chainfire just released a tool to print out whether your device has a known-bad firmware revision, Got BrickBug?. As you can see, my device has firmware revision 0x19. This revision has been known to cause hard bricks on other devices using Samsung ICS ROMs.
CM9 is safe (Entropy512 haxx0red the kernel), but we should be careful.
Click to expand...
Click to collapse
I got this bad firmware revision too, but iam still safe after 2 months
Sent from my GT-P6200 using xda app-developers app

Bad2hold said:
Well, aorth entioned sth like this before, here his post:
I got this bad firmware revision too, but iam still safe after 2 months
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
I'm not sure if I had the bad one, but mine worked fine for months too. Then out of the blue it bootlooped and when I tried to fix it by reverting to stock, I got the error. Hopefully when it comes back it will have a different firmware revision (if that's what the problem was)
Sent from my myTouch 4g via Tapatalk

I flashed my tab with 'P6200OXALQ1_P6200XXLQ1_P6200XXLQ1' on 19th July - so far nothing has happened.... and it is working much faster than the 3.2 Honeycomb it came with.:fingers-crossed: Using Stock kernel/recovery... only rooted using temporary touch recovery.

02xda2 said:
I flashed my tab with 'P6200OXALQ1_P6200XXLQ1_P6200XXLQ1' on 19th July - so far nothing has happened.... and it is working much faster than the 3.2 Honeycomb it came with.:fingers-crossed: Using Stock kernel/recovery... only rooted using temporary touch recovery.
Click to expand...
Click to collapse
If you flashed it using Mobile Odin that's normal because it uses its own recovery.

Ok, so what's the verdict? This bug sounds very scary.
Given that I'm running a stock ICS flashed via ODIN, should I be running:
-Stock recovery
-CWM
-Something else
to avoid bricking while factory reset?

I also use mobile Odin to flash ics and no problem. So, could you say that with Mobile Odin are safe from this problem?

Just read this http://www.reddit.com/r/Android/comments/xj2hd/i777_superbrick/, seems some of the things said could be relevant for us.

I have a galaxy note and Entropy who is dealing directly with samsung on this issue has a thread over on the galaxy note page. Lots of information over there.
I use the free emmc bug check app by vinagre https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check&hl=en to check my samsung devices on ics. Not entirely sure that the same case applies for the note and the tab plus though but it does give me peace of mind.
Just to err on the side of caution, I always odin flash back to gingerbread to wipe cache and other stuff before upgrading. This seems to have worked for me so far. *fingers crossed*
Check out that app above, its free and have a read of entropy's thread http://forum.xda-developers.com/showthread.php?t=1698977 but beware they don't take kindly to noob questions. I just mainly read entropy's updates and replies and ignore most of the rest of the stuff there.

Is there any chance to bring my tab to life has the repair center hasen't repaired mine

hi,
i have flashed the stock ICS, the Austrian version using ODIN3. i have been running it since july 18th.
so far i dont see any problem with my tab..
just to say, i have flashed the firmware atleast 3 times, just as an exercise. and have factory reset it after ICS flash atleast like 5 times now.
everything so far works fine. i use the stock recovery for factory reset.
after the 1st flash, i had root.. then thought of unrooting, so flashed the firmware 2 more times.
and in between the flashes, i have factory reset a lot of times.
so far, the bootloop problem which i used to have when on HC, is not there. hopefully, it wont occur in ICS.
hope, this helps developers.

Zarvox said:
Is there any chance to bring my tab to life has the repair center hasen't repaired mine
Click to expand...
Click to collapse
Use pit file (tab 7.7) in topic of hg42 - galaxy note this forum.
http://forum.xda-developers.com/showthread.php?t=1667886
Or use this method:
http://forum.xda-developers.com/showthread.php?t=1661590
Sent from my GT-P6200 using Tapatalk 2

giangp1 said:
Use pit file (tab 7.7) in topic of hg42 - galaxy note this forum.
http://forum.xda-developers.com/showthread.php?t=1667886
Click to expand...
Click to collapse
Thanks with manual method described in this thread I've confirmation that my data partition became corrupted.
Yes it is alive !!!
I've deleted mmcblk0p9 (DATAFS on my P6210) and recreate one with smaller size (3 GB) than normal (15.2 GB).
When the tablet boot I realise I've 1.68 GB of storage
Now I may increase the size of data but previous tries told me if data reach 5 GB in size the creation of partition fail.