Database Info

[Q] Samsung Galaxy S HardReset

Hi,
I upgraded my Samsung I9000, from Éclair 2.1 to Froyo 2.2, with Odin, (everything is working fine), but...
My question is;
If I do a Hardware Reset does the phone downgrades to is factory default, in this case "Éclair 2.1", or it stays with the last OS installed?
Does anyone knows what happens??
Cheers,
Striken

A hard reset is different than a master reset. Hard reset only entails removing the battery from the device.
To answer your question, once flashed with a ROM, performing a MASTER reset, will bring the phone back to "factory" defaults, i.e. just like it was the very first time you booted it AFTER installing the custom ROM.
Hope that helps.

SeaborneClink said:
A hard reset is different than a master reset. Hard reset only entails removing the battery from the device.
To answer your question, once flashed with a ROM, performing a MASTER reset, will bring the phone back to "factory" defaults, i.e. just like it was the very first time you booted it AFTER installing the custom ROM.
Hope that helps.
Click to expand...
Click to collapse
Thanks Man,
You are talking in a Master Reset, how exactly do you do that?
When I did a software reset it erases everything on the phone, contacts, apps I installed, everything except what belongs to the Rom I installed. Also the phone stayed like when was installed for the first time...
From what I've read an Hard reset puts the phone to is factory defaults, but when I did a soft reset it also stayed "brand new", like factory default.
My question is: does a hard reset erases the rom I installed and puts my phone like it was before I upgraded with Froyo 2.2?
I never heard anything regarding a "Master Reset", can you explain me more?
Thanks,
Striken

Also interested in learning how to Master Reset before playing with ROMs.
Bookmarked for later, thanks!

Hi Kops,
If you also learn anything about it please post it here ok?
Thanks

I believe you can find the stock firmware for your phone (2.1 or 2.2) and use ODIN to flash to that. By doing so, you will revert to 100% stock settings, no root, and no proof that you've flashed your phone at all.
In my opinion, this is your best bet for a "full reset".

When you flash a new firmware, the firmware is permanently installed. Performing a factory reset will NOT revert your phone to its older version. Only a reflash will do this.
Factory reset only resets things that are stored in user data space. Such as your contacts, custom settings and any apps that you have installed (not counting those that Samsung/Google have put into the system)
So there you have it. You can safely perform that reset if you want.

deliberate187 said:
When you flash a new firmware, the firmware is permanently installed. Performing a factory reset will NOT revert your phone to its older version. Only a reflash will do this.
Factory reset only resets things that are stored in user data space. Such as your contacts, custom settings and any apps that you have installed (not counting those that Samsung/Google have put into the system)
So there you have it. You can safely perform that reset if you want.
Click to expand...
Click to collapse
Thanks for the help guys,
So, there's no difference between a soft and hard reset? Or is the factory reset an hard reset?
When I did a factory reset it erases everything and restored the phone to is default settings.
So, the only way to put the phone back like it was when I purchased is installing Eclair 2.1 again...
Thanks,

The only way to get 2.1 back is by reinstalling an official samsung firmware. Yes. If you have an official samsung firmware though, the phone is as it should be.
A soft boot is generally where you send the device a reboot command or turn it off and back on. A hard boot to reiterate generally happens after the battery is removed and reinstalled. This is not what is known as a factory reset and will not modify anything.
A factory reset formats the userdata and cache partitions and resets all settings to default including deleting any apps that were not installed on the factory firmware.
I hope this has answered your question.
Sent from my T-Mobile G2 using XDA App

It did, thanks.
The only problem is that I never found an official Samsung firmware, in this case the Eclair 2.1 from Vodafone.
If you know any site that have that Rom please share it
I would like to have it so I can restore the phone in an urgency...
Cheers,

Try samfirmwares.com

architectniharshah said:
Try samfirmwares.com
Click to expand...
Click to collapse
Already try that. They don't have it.

Or www.samsungfirmwares.com. they have an extensive collection of i9000 roms. Vodaphone is on the 3rd I9000 page.
Sent from my T-Mobile G2 using XDA App

deliberate187 said:
Or www.samsungfirmwares.com. they have an extensive collection of i9000 roms. Vodaphone is on the 3rd I9000 page.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Thanks man,
Don't want to be a pain, but just one more thing if you or anybody knows...
When I both my phone it came with Eclair 2.1 from Vodafone like I said.
You presented me with a page that have the 2.1 stock Rom from Vodafone, but, originally the phone had a Vodafone startup animated logo.
Do you know if the rom in that page has that animation startup?
Thanks,
P.S. One more thing, when I said that I didn't find anything in that site I was mistaken, it was not that website but samfirmware.com website.
Thanks again,

Its a stock rom. Just like the one that shipped inside your phone. It will have all of the features of the ROM you started out with.
Sent from my T-Mobile G2 using XDA App

You can remove all user data that is located on internal memory by typing *2767*3855# in dial pad and NO it won't downgrade to previous firmware.

deliberate187 said:
Its a stock rom. Just like the one that shipped inside your phone. It will have all of the features of the ROM you started out with.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Mangoli said:
You can remove all user data that is located on internal memory by typing *2767*3855# in dial pad and NO it won't downgrade to previous firmware.
Click to expand...
Click to collapse
Thanks for all the help guys!
Just one thing all of the firmware in samsungfirmwares.com have a download option but without any link...
How can I download?

You have to register to download if I remember correctly.
Sent from my T-Mobile G2 using XDA App

deliberate187 said:
You have to register to download if I remember correctly.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Hi,
I've try that but theres no option for register a new user there.
I manage to download else where.
Many thanks!

[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

[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.

Factory Reset 6210

Looking to gift my 7+ to my sister by doing a factory reset to return to unrooted stock. Flashed the European ICS a while back from HC via Mobile ODIN, Been reading about the Superbrick Bug on some Samsung devices has me a tad leery.
Probably know the answer but thought I'd ask regardless. Any instances of problems with reset given the above 7+ profile? Now that US ICS is out would quite probably update to US ICS afterwards.
Suggestions? Thoughts? Idle ramblings?
thanks

skeeterpro said:
Looking to gift my 7+ to my sister by doing a factory reset to return to unrooted stock. Flashed the European ICS a while back from HC via Mobile ODIN, Been reading about the Superbrick Bug on some Samsung devices has me a tad leery.
Probably know the answer but thought I'd ask regardless. Any instances of problems with reset given the above 7+ profile? Now that US ICS is out would quite probably update to US ICS afterwards.
Suggestions? Thoughts? Idle ramblings?
thanks
Click to expand...
Click to collapse
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.
For those of you who insist on upgrading to ICS, 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.
My personal experience is positive, from honeycomb , i am past to CM9 , then with ODIN to flashing ICS , I do not have locked the device , there were problems with bootloop ,but solved by using a wipe data , factory reset from the recovery..

skeeterpro said:
Looking to gift my 7+ to my sister by doing a factory reset to return to unrooted stock. Flashed the European ICS a while back from HC via Mobile ODIN, Been reading about the Superbrick Bug on some Samsung devices has me a tad leery.
Probably know the answer but thought I'd ask regardless. Any instances of problems with reset given the above 7+ profile? Now that US ICS is out would quite probably update to US ICS afterwards.
Suggestions? Thoughts? Idle ramblings?
thanks
Click to expand...
Click to collapse
If you need to reset it, DO NOT FACTORY RESET FROM ICS RECOVERY. Flash back to hc with Odin, then do a factory reset there, or install cwm recovery and reset it from there (probably the route I would take, as it is far easier)
Sent from my myTouch 4g via Tapatalk

as per what i did, i have done factory reset from within the settings menu, which rebooted my device to stock recovery.
the initial reset was fine, but when i flashed the new asian ICS firmware, i did a reset from the stock recovery itself, which have bricked my tab.
so, be careful with factory reset, as it also uses the default recovery (correct me if i understand it wrong).

[Q] Will I be able to get my Bluetooth back ?

Hello there !
I can't toggle on Bluetooth in my GT-P3110 recently.. I'm not on airplane mode.. but WiFi works though...
I even flashed a CM ROM(10.1.3 right now) to see if it works.(may be an silly deed.. I'm just new to these android things)
I have uploaded two videos which shows what really happens when trying to turn on bluetooth...
When I was using the stock rom
After flashing CM
I think that I'm having some hardware failure (i.e. dropping the unit - I never dropped myself.. idk if it happened actually as I share this tablet with my family )
I want to know whether this can be repaired ?.
Is there a seperate accessory inside for Bluetooth which can be replaced ?
Thanks in advance !

Were you on stock firmware when you noticed your bluetooth is not turning on? Was it from the start of your new tablet? Take a look at this thread, someone has the same problem with you and solved it but his problem was caused of inproper flashing http://forum.xda-developers.com/showthread.php?t=2447156
You could also try to reinstall using wipe data/factory reset, wipe cache, wipe dalvik cache from clockwork mod and reinstalling cyanogen again to see if that fixes it.
As your last resort you could flash your tab back to stock recovery and fw (and use TriangleAway to reset your flash counter) and send it to Samsung for repair, especially if it still has warranty.
some other threads with your problem: http://forums.androidcentral.com/go...s/225585-4-2-upgrade-cant-turn-bluetooth.html

katsika said:
Were you on stock firmware when you noticed your bluetooth is not turning on? Was it from the start of your new tablet? Take a look at this thread, someone has the same problem with you and solved it but his problem was caused of inproper flashing http://forum.xda-developers.com/showthread.php?t=2447156
You could also try to reinstall using wipe data/factory reset, wipe cache, wipe dalvik cache from clockwork mod and reinstalling cyanogen again to see if that fixes it.
As your last resort you could flash your tab back to stock recovery and fw (and use TriangleAway to reset your flash counter) and send it to Samsung for repair, especially if it still has warranty.
some other threads with your problem: http://forums.androidcentral.com/go...s/225585-4-2-upgrade-cant-turn-bluetooth.html
Click to expand...
Click to collapse
Thanks for the reply... I noticed the issue when I was on stock stock ROM. I may have to send it to Samsung.
Thanks for the support :highfive:

Is it possible you have another kernel other than stock?
Sent from my XT907 using xda app-developers app