long story short, my phone was shipped with prerelease software. After rooting and flashing a customer recovery, my original nandroid was corrupted.
The only option for me now is custom ROMs, but unfortunately my wifi gives me an error on every single ROM available.
Anyone know of a quick fix?
The only thing i can think of that would solve the issue is to possible flash the stock US ROM once it's available, then hopefully that would fix my wifi issues and i'd be able to flash to any other ROM with no problem.
Alternatively - could someone please post a flashable ZIP of the stock ROM, or at least post a stock nandroid that i would be able to restore onto my phone to see if the wifi issue gets resolved.
Did flashing the stock img work
Sent from my PC36100 using Tapatalk 2
I have a fix for you. I'm releasing it tomorrow though.
I'm releasing a stock T-Mobile nandroid final firmware and newest software.
I'm also releasing a rooted version.
Sent from my HTC VLE_U using XDA
Full wipe on everything?
Sent from my Galaxy Nexus using Tapatalk 2
MikeyCriggz said:
Full wipe on everything?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Always
After doing a bit of reading, it seems as though some people have having similar issues. The exception is that theirs is doing this while stock, and updating their router firmware fixed the problem. My phone connected to my router perfectly fine while stock...the problem didn't occur until i flashed the first custom ROM.
Reviewers said:
I have a fix for you. I'm releasing it tomorrow though.
I'm releasing a stock T-Mobile nandroid final firmware and newest software.
I'm also releasing a rooted version.
Sent from my HTC VLE_U using XDA
Click to expand...
Click to collapse
Thanks, hoping this will solve the problem!
suhailtheboss said:
Always
After doing a bit of reading, it seems as though some people have having similar issues. The exception is that theirs is doing this while stock, and updating their router firmware fixed the problem. My phone connected to my router perfectly fine while stock...the problem didn't occur until i flashed the first custom ROM.
Click to expand...
Click to collapse
It's because all roms now are based on European firmware not T-Mobile firmware.
Tomorrow I'm uploading the first ever T-Mobile Rom and it'll fix everybodys problem.
Sent from my HTC VLE_U using XDA
suhailtheboss said:
Always
After doing a bit of reading, it seems as though some people have having similar issues. The exception is that theirs is doing this while stock, and updating their router firmware fixed the problem. My phone connected to my router perfectly fine while stock...the problem didn't occur until i flashed the first custom ROM.
Click to expand...
Click to collapse
Definitely sounds like a firmware or driver issue. Have you tried resetting your router or updating its firmware? Also, what kernel version are you running.
Sent from my Galaxy Nexus using Tapatalk 2
MikeyCriggz said:
Definitely sounds like a firmware or driver issue. Have you tried resetting your router or updating its firmware? Also, what kernel version are you running.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
tried connecting to a different router on update stock firmware and teh issue still exists.
I was hoping that with the stock TMO-US ROM the problem would be fixed, but unfortunately not.
Now i have really no idea. It's impossible for me to live without wifi on my phone for good.
suhailtheboss said:
tried connecting to a different router on update stock firmware and teh issue still exists.
I was hoping that with the stock TMO-US ROM the problem would be fixed, but unfortunately not.
Now i have really no idea. It's impossible for me to live without wifi on my phone for good.
Click to expand...
Click to collapse
Do this:
1. Delete /data/misc/wifi folder using a file browser.
2. Clear cache using recovery. Reboot. Wifi will regenerate its data.
3. Try wifi again.
Let me know if this works. It's a shot in the dark so I don't know if that's gonna work for you, since you already seem to have performed a fac reset.
nickmv said:
Do this:
1. Delete /data/misc/wifi folder using a file browser.
2. Clear cache using recovery. Reboot. Wifi will regenerate its data.
3. Try wifi again.
Let me know if this works. It's a shot in the dark so I don't know if that's gonna work for you, since you already seem to have performed a fac reset.
Click to expand...
Click to collapse
Thanks for the tip, unfortunately this didn't work either. I'm totally out of ideas at this point. Might just end up exchanging the phone and paying the out of warranty fee if they find out the boot loader was unlocked. Not really sure what's left for me to try.
Flash my T-Mobile Nandroid in recovery.
Reviewers said:
Flash my T-Mobile Nandroid in recovery.
Click to expand...
Click to collapse
I did within ten minutes of you posting it. Unfortunately it did not solve the problem. I thought that would be the fix...
One thing I didn't notice was a clear description of the problem. Please describe what your issue is. You say the wifi gives you an error. What does that mean?
Please describe everything in detail from start to finish, before trying to return it.
WiFi will turn on, display available networks, once a network is selected it will not connect and then says "error"
then after about ten seconds the phone will reboot, then reboot after it turns on. never-ending.
only way to have the phone work is to do a master reset, but the problem starts again when you attempt to.connect to WiFi.
also the phone will not stay off when stuck in the WiFi reboot loop. if i choose "power down" it will turn off, then turn back on within 10 seconds.
That sounds very very strange. Almost like a kernel error (unlikely since kernel is included w/ ROMs), a radio issue (more likely), or a hardware issue (most likely, in my opinion). If you've already done a full wipe and wiped /system and /sdcard to be sure, then it sounds like you've done your due diligence.
At this point you might want to go ahead and reflash the stock ROM (see Reviewer's post with a nandroid of the stock ROM), reflash the stock recovery, and relock the bootloader. Unless someone else can chime in here. Also, if you return it, there's no promises that they won't look for TAMPERED or anything in the bootloader, so beware. The important thing is to have the stock software and recovery loaded and it relocked. Then they can flash it in the store, and it'll probably fail, in which case they may replace it.
nickmv said:
That sounds very very strange. Almost like a kernel error (unlikely since kernel is included w/ ROMs), a radio issue (more likely), or a hardware issue (most likely, in my opinion). If you've already done a full wipe and wiped /system and /sdcard to be sure, then it sounds like you've done your due diligence.
At this point you might want to go ahead and reflash the stock ROM (see Reviewer's post with a nandroid of the stock ROM), reflash the stock recovery, and relock the bootloader. Unless someone else can chime in here. Also, if you return it, there's no promises that they won't look for TAMPERED or anything in the bootloader, so beware. The important thing is to have the stock software and recovery loaded and it relocked. Then they can flash it in the store, and it'll probably fail, in which case they may replace it.
Click to expand...
Click to collapse
Yeah i'm clueless. I've literally done absolutely EVERYTHING that i could imagine to fix the issue.
I actually work for T-Mo, we dont have any abilities to flash anything in store. Also exchanging the phone is a little bit more difficult for me, because the phone was not purchased through tmobile, it was given to me by HTC a week before launch.
Either way, I'm going to reload all the shipping stuff when i get home tonight then go ahead and try to process an exchange. Worst case scenario they will charge me ~100 bucks as an out of warranty fee. (due to having the *TAMPERED* logo on the bootloader scren. Although I'm fairly certain they don't check that, they shoudl only check for physical/liquid damage. I have processed many exchanges for rooted customers, who had manufacturer defects.
also another thing i just noticed, my baseband is: 0.15.31501S , but my friends retail version is 0.16.
any way for me to update this?
Early Adopters
I just got the One S myself and I'm a bit forlorn from the lack of available ROMS. Then again when I was in the Apple Ecosystem, there was no ROMS, just tweaks so different environment different timelines I guess.
Not sure if it can help in this case, but this solved my wifi error problem.
I had a "wifi error", my One S coudn't connect any AP.
The problem was a bad permision on the file /data/misc/wifi/wpa_supplicant.conf.
Logcat gave me that :
"Cannot set RW to /data/misc/wifi/wpa_supplicant.conf"
So, using Es Explorer (as root), i changed the chmod of this file to rw-rw-rw and wifi started to work again. (no reboot needed in my case).
Hope this help.
Related
No matter what ROM/Kernel I flash to i loose my WIFI access. When I go into settings/Wifi it just says ERROR. Anyone have any idea what I'm doing wrong?
With CM7.0.3.1, I have been using bcblends tinyrcu (available through kernel manager) and leave min/max as is (806max/245min) make sure you wipe cache/dalvik before installing the kernel...
Hope this works for you.
Sent from my PG06100 using XDA App
When it does that is your SD card not mounted anymore and requires a reboot for it to see it again? That happens to me smetimes
Sent from my NookColor using XDA Premium App
lilgrass71 said:
When it does that is your SD card not mounted anymore and requires a reboot for it to see it again? That happens to me smetimes
Sent from my NookColor using XDA Premium App
Click to expand...
Click to collapse
SD card should be mounted. It's only unmounted when I plug my phone to the computer to transfer files and such...
Same thing happens to me with kernels. Sometimes Wimax too. I'm using mik shift, works fine with stock kernel.
Sent from my Nexus S using XDA Premium App
Maybe its just my luck w cards... been running cm7 stables and had two 8 giggers die one me... one kingston class 4 and a sandisk class 6... its happening again on my last 8 gigger too!
Sent from my PG06100 using XDA Premium App
I have a regular evo with this same problem, tried 3 dif kernals, and upteen romflashes.... still have wifi error in settings
still no progress on this, i still have this problem... super gay
I too am getting an "Error" when trying to turn wifi, Logcat says " Wifi Driver missing" have tried rebooting, and flashing another rom. any help?
Well it's probably been said before, but here goes When you flash a new Rom make sure you do a FULL wipe. It's seems trivial, but not doing this can and usually does cause all kinds off issues. Also, you should check your WiFi settings, and make sure they're correct.
Full wipe has been done and what wifi settings are you talking about? phone settings can't be accessed because the phone can't turn wifi "on". is it possible to extract the wifi driver from another shift? i have another one at my disposal. BTW wifi was working a day ago no problem. i havn't flashed a new ROM in months and was on a stock rooted rom.
Have you tried to ruu back to stock to see if you have the same issue? Or nandroid back to a version where it worked?
Sent from my PG06100 using XDA App
yea ruu'd back to froyo, re-rooted and reinstalled updated radios, and am back to gb. any idea where the wifi drivers would be? thanks for the replies.
Have you just tried it from a stock froyo rom? RUU back to 2.2 and just try it from there. It should reflash all the proper radios. Maybe the wifi chip is defective in the phone too. It happened at work to a co-workers playbook.
lvpre said:
Have you just tried it from a stock froyo rom? RUU back to 2.2 and just try it from there. It should reflash all the proper radios. Maybe the wifi chip is defective in the phone.
Click to expand...
Click to collapse
+1 on that. Also if it was working then not. Something else might be up, are other devices able to connect to that WiFi spot with no issues? It is possible to extract the wifi driver from another SHift. But if you just RUU back to stock it should work. If not somethingelse is definately wrong. To get to the settings: Menu-Settings-Wireless & Networks-Wi-Fi settings-menu-Avanced.
yea went ruu'd back to stock, no dice. wifi just says "error" after "turning on", must be an internal problem. other devices work fine on this point. what would be the steps to extracting the driver from another shift, i have one ready to go.
If you RUU'd back to stock, and it's a still no good. Then you might want to consider getting a replacement if WiFi is really important to you. Especially if you know for sure that other devices can connect, and you cannot on a stock Rom. But you do risk getting an updated Shift. Not a risk worth taking in my eyes. Did you make sure and check all the settings?
Yea all the settings are good, it definitely seems to be an internal problem at this point. I'm weighing the options right now and came close to ruu'ing to gb to see if it solved the problem, but I just couldn't give up root.
only 2 things come to mind on what caused this, i attempted to update to the newest ota htc update over the stock rom, ( i know stupid, got the android + !) and i installed an app to transfer files over wifi.
Wifi isn't too important but I hate the feeling of not having my phone %100.
Same problem here. I just got a wifi-error running the latest shift-deck. The phone was brand new with a bad esn (planning to flash to a different carrier) and was first turned on 8/2/11. so basically 2 weeks turned on. This just happened 2 days ago. Cleared everything and flashed again. Don't know how to RUU or what it is. Anyone want to explain?
Ruu basically puts the phone back as if it were just out of the box. There is a thread somewhere here with the file. Just make sure you get the froyo version, otherwise you won't be able to root.
Sent from my PG06100 using XDA App
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
My One X restarts when I'm in the Google Play app and while using the built in browser. It seems to be data related... Also I get no error or anything of that nature, it just freezes (stops responding to any input whatsoever the capacitive buttons don't respond either) and it just restarts and goes through the HTC and AT&T load screens. Any ideas as to why my phone keeps restarting after a bit of use on the market, browser, etc... I've sent in my original phone thinking it might've been defective. Turns out the one they sent me did the same thing. Mind you they sent me a refurbished one. So I don't know if its a problem isolated to the original shipments of HOX's since I got mine via a pre-order and this is probably the same batch since the AT&T rep said they had no new devices to ship to me as a replacement.
Any ideas?
I've gone through a few HOXs and have never had a single reboot on any of them. My suggestion to you would be to wipe everything (data, cache, dalvik) and reflash your ROM.
_MetalHead_ said:
I've gone through a few HOXs and have never had a single reboot on any of them. My suggestion to you would be to wipe everything (data, cache, dalvik) and reflash your ROM.
Click to expand...
Click to collapse
How exactly would I go about doing that. I used the clockwork recovery mod on my Aria back when I had that. But from what I understand the HOX doesn't have that yet and attempting to use ROM Manager or anything that uses it would brick my phone.
We have clockwork mod and TWRP recoveries. I take it you are on a stock ROM then? Are you rooted?
Oh, and never use ROM Manager. Ever.
_MetalHead_ said:
We have clockwork mod and TWRP recoveries. I take it you are on a stock ROM then? Are you rooted?
Oh, and never use ROM Manager. Ever.
Click to expand...
Click to collapse
Yeah I'm rooted (on the stock ROM) and I managed to get my bootloader unlocked.
I take it you haven't flashed any mods right? I'd get clockworkmod flashed on your phone and then wipe and flash CleanROM SE. It's very close to stock, perfectly stable (I haven't had a single force close except for one youtube one a long while back right after flashing), and it has some great mods and tweaks. If you are still having reboots, then I would RUU back to stock, see if they are still there and if they are, get it replaced.
_MetalHead_ said:
I take it you haven't flashed any mods right? I'd get clockworkmod flashed on your phone and then wipe and flash CleanROM SE. It's very close to stock, perfectly stable (I haven't had a single force close except for one youtube one a long while back right after flashing), and it has some great mods and tweaks. If you are still having reboots, then I would RUU back to stock, see if they are still there and if they are, get it replaced.
Click to expand...
Click to collapse
Sorry, didn't see this (http://briefmobile.com/how-to-install-cwm-recovery-on-htc-one-x-att) on the index. Thanks for the help.
xChurchx said:
Sorry, didn't see this (http://briefmobile.com/how-to-install-cwm-recovery-on-htc-one-x-att) on the index. Thanks for the help.
Click to expand...
Click to collapse
Yep, that's the one. Happy to help.
Radio
If your issues were mostly data related its probably a radio issue. Be sure to flash a new radio. If I'm not mistaken most roms don't include the radio. I like the latest AT&T as well as 1.88. Much better than 1.73 or 1.85. you can flash it just like a rom if it's in zip format. There's a thread in development with radio In the title. Normally first page.
xChurchx said:
My One X restarts when I'm in the Google Play app and while using the built in browser. It seems to be data related... Also I get no error or anything of that nature, it just freezes (stops responding to any input whatsoever the capacitive buttons don't respond either) and it just restarts and goes through the HTC and AT&T load screens. Any ideas as to why my phone keeps restarting after a bit of use on the market, browser, etc... I've sent in my original phone thinking it might've been defective. Turns out the one they sent me did the same thing. Mind you they sent me a refurbished one. So I don't know if its a problem isolated to the original shipments of HOX's since I got mine via a pre-order and this is probably the same batch since the AT&T rep said they had no new devices to ship to me as a replacement.
Click to expand...
Click to collapse
I had this exact problem. EXACT. Does it happen on WiFi only? try turning it off.
EDIT: this happened to me on two different HOXs, one just after i updated to 1.82, and the other, stock from the store on 1.85. I was able to narrow it down to the fact that our home wifi was unprotected with a hidden SSID. as soon as we changed it to WPA it worked fine, and continues to.
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.
Recently I unlocked bootloader, installed twrp and succesfully rooted my device, but while I was tinkering with my device I accidentally wipe all data, partition, etc in TWRP now I guess I wiped out everything including OS !!!
How can I restore ? Do I need to flash new hammerhead image ?
Right now I'm following this tutorial
http://forum.xda-developers.com/showthread.php?t=2513701
It'll be great if anyone of you can point me right way.
You can just flash any custom rom using this
http://forum.xda-developers.com/showthread.php?t=2575150
Or
Follow the thread you posted to restore a factory image..
But restoring a factory image will unroot your device..
You have twrp so the first thing you did was make a nandroid, right? Live and learn.
Thanks for the help, I just flashed new image. Everything works good except wifi, random drops + slow speed.
I contacted google for replacement and they send me RMA form. Unrooted the phone, bootlocker locked + flag reset.
Thanks for the help, I just flashed new image. Everything works good except wifi, random drops + slow speed.
I contacted google for replacement and they send me RMA form. Unrooted the phone, bootlocker locked + flag reset.
Huh? You're doing an RMA why?
sent from my hammerhead
albertpaulp said:
Thanks for the help, I just flashed new image. Everything works good except wifi, random drops + slow speed.
I contacted google for replacement and they send me RMA form. Unrooted the phone, bootlocker locked + flag reset.
Click to expand...
Click to collapse
Why are you rma'ing it. Was wifi messed up before you erased everything?
jd1639 said:
Why are you rma'ing it. Was wifi messed up before you erased everything?
Click to expand...
Click to collapse
Before rooting wifi problem was rarely occur now after rooting problem arise more frequently, now even after unrooting wifi is super slow sometimes not even connecting. I hate RMAing but seems like no other way.
http://forum.xda-developers.com/showthread.php?t=2586410
jd1639 said:
You have twrp so the first thing you did was make a nandroid, right? Live and learn.
Click to expand...
Click to collapse
Awesome advice. I made a nandroid of my N5 first thing after getting all my apps straight. Playing with flashing a rom in TWRP I did a manual "wipe data" which proceded to wipe out the entire SDCARD in the process including my nandroid. Sooooo.... Yes, make a nandroid but also back it up to your computer or dropbox right away.
albertpaulp said:
Before rooting wifi problem was rarely occur now after rooting problem arise more frequently, now even after unrooting wifi is super slow sometimes not even connecting. I hate RMAing but seems like no other way.
http://forum.xda-developers.com/showthread.php?t=2586410
Click to expand...
Click to collapse
Don't RMA it, there's nothing wrong with the hardware. All you have to do is reflash the factory image. If you didn't know what you were doing, you shouldn't have been messing around with your phone in the first place. Reflash your phone back to its factory state and next time do your homework before you start tinkering. People like you are going to cause Google to change their return policy so that returns are much more heavily scrutinized.
BirchBarlow said:
Don't RMA it, there's nothing wrong with the hardware. All you have to do is reflash the factory image. If you didn't know what you were doing, you shouldn't have been messing around with your phone in the first place. Reflash your phone back to its factory state and next time do your homework before you start tinkering. People like you are going to cause Google to change their return policy so that returns are much more heavily scrutinized.
Click to expand...
Click to collapse
Before rooting wifi problem was rarely occur now after rooting problem arise more frequently, now even after unrooting wifi is super slow sometimes not even connecting. I hate RMAing but seems like no other way.
Click to expand...
Click to collapse
You know how to read right ? also I did reflashed to stock image and unrooted + locked bootloader but problem persists, what do you propose I do now ? I started loving my phone now I'm getting new one, it's hard for me too, it's like adopting a son.