Database Info

[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

wifi error on every ROM

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.

A Tale of Two Skyrockets - Are either of them susceptible to the bricking bug in FL6?

So, I have 2 Skyrockets, both of them on Gingerbread, but the similarities end just about there.
Phone 1 is my phone, running stock UCJK2 (2.3.5), rooted using SuperOneClick (so, I suppose it's only soft-rooted), running CWM 5.0.2.7, and the stock kernel.
Phone 2 is my mother's, running UCLA3 (2.3.6), entirely stock.
I'd like to upgrade both to UCFL6 through Kies so that no data is lost. In addition, I'd like to be able to get the first phone rooted with CWM on it. However, I kind of got scared away by news of a supposed bricking bug that affected those upgrading to UCFL6. The forum posts I read about it (yes, I did search beforehand) show quite a bit of discussion, but nothing really nailing down the cause of the bug.
My question is: can both of these phones be upgraded to UCFL6 through Kies without any* risk of bricking either of them?
* Of course there's going to be a small risk whenever one upgrades, but I mean encountering the bricking bug.

hmmwhatsthisdo said:
* Of course there's going to be a small risk whenever one upgrades, but I mean encountering the bricking bug.
Click to expand...
Click to collapse
Your final paragraph sums it up
Sent from my SAMSUNG-SGH-I727R running SKY-ICS 4.2F6-2.7

mymusicathome said:
Your final paragraph sums it up
Sent from my SAMSUNG-SGH-I727R running SKY-ICS 4.2F6-2.7
Click to expand...
Click to collapse
I mean the bricking bug that had something to do with UCFL6, recoveries, and wiping the phone, not the general small amount of risk that comes with flashing any ROM. It sounded like there was a huge bug that made upgrading to UCFL6 extremely dangerous (moreso than any other ROM flash).

it was doing a reset within the os not recovery with the ics leaks, bricks are caused by user error 99% of the time, there are some links to the bug in my 1st link in my sig, its under the info section
one guy that had the problem in uclf6 rebooted into android after a reset within ics, but not after the 1st boot, it was suspected of hardware failure since he was having problems b4 he did the reset and it did bootup after the reset

vincom said:
it was doing a reset within the os not recovery with the ics leaks, bricks are caused by user error 99% of the time, there are some links to the bug in my 1st link in my sig, its under the info section
one guy that had the problem in uclf6 rebooted into android after a reset within ics, but not after the 1st boot, it was suspected of hardware failure since he was having problems b4 he did the reset and it did bootup after the reset
Click to expand...
Click to collapse
And, is it recommended/required to do a reset after flashing with Kies?

hmmwhatsthisdo said:
And, is it recommended/required to do a reset after flashing with Kies?
Click to expand...
Click to collapse
No solid evidence on importance .. But if you wanna do it do it from the stock recovery , benefit is questionable .. If you're just ODINed or Kies'ed , why reset ?

mahanddeem said:
No solid evidence on importance .. But do if you wanna do it do it from the stock recovery , benefit is questionable .. If you're just ODINed or Kies'ed , why reset ?
Click to expand...
Click to collapse
Well, I didn't want to have to reset (since I wouldn't be able to save everything in /data), but I'd thought I'd check in case not doing so caused major stability issues.

[Q] Hard Bricked Skyrocket from Bad Flash

To start, I have never had problems flashing Skyrocket ROMs before. I flashed the ICS leak with Odin when I first got the phone, then CWM, then Cyanogeonmod when that came out, and some other things. But recently I decided to flash SlimBean which suggested TWRP so I flashed that and I had it working well for awhile.
After Google I/O I decided to f;ash the weekly build, SlimBean 5.5. The flash went OK but the ROM was glitchy and crashed a lot. So I decided yesterday to go back to the release channel of SlimBean. So I downloaded SlimBean 5.0 and AIO Addons 5.x and I moved them to my SD card. However before I did that I noticed I already had a 5.x from my last flash that would turn out to be the Aroma installer that i didn't want. But anyways, after wiping the cache, Dalvik cache, system, and data, I flashed the 5.0 ROM then the 5.x aroma aio addons, and then it sent me into the Aroma installer which I figured out that I used the wrong addons aio package. So then I hit next all the way through the installer without changing anything and didn't hit reboot device. Then, still in the TWRP menu, I wiped the same sections I did last time, mounted the SD card through TWRP, moved the AIO Addons 5.x on, and deleted the AIO Aroma 5.x. Then I flashed SlimBean 5.0 from before with the AIO Addons 5.x.
When I hit reboot, my phones screen was off and it never went on again. I took out the battery, had it hooked to the charger, and tried everything and it wouldn't even vibrate. So I knew pretty fast that I had hard bricked it. I Google'd a little bit and read about the jig, but I have a feeling that wouldn't work with this low level of a brick. So I guess what I want to know is what actually happened, and I just want to get this story out there because I have no idea how I got such a low level brick from just flashing ROMs like usual.
Also, I'm planning on making a trip to the AT&T store with hopes of getting a replacement. I don't know if I will because it is refurbished and I bought it online over a year ago. (the warranty being 90 days) Does anyone have experience getting replacements out of warranty?

First off if it's bricked it's bricked it's not about low level or whatever.
Second a jig does nothing for this phone that can't be done manually, don't waste your time or money on it.
Third you can have it jtag'd for $50 by some dudes if you search tons of people have done it.
You left out an astounding amount of detail for an extremely long post so no one can tell you exactly where you went wrong.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Yea, way too many words. But to your last paragraph, good f'n luck. You're way out of warranty.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app

You will get no warranty. Send it away for jtag if you want it fixed, you can't fix it if it's hard bricked.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

I sent the phone to be jtag'd and they sent it back saying they couldn't fix it. What could have gone so wrong in the flashing process that it is bricked so badly?

TankTan38 said:
I sent the phone to be jtag'd and they sent it back saying they couldn't fix it. What could have gone so wrong in the flashing process that it is bricked so badly?
Click to expand...
Click to collapse
probably wasnt the flash but bad hardware, most likely mobo/memory, jtag can only write to the mem chip if its corrupted or a incompatible rom was trying to write to it but it wont/cant fix a hw failure of chip

[Q] Flashing no longer possible: Flash successful but system does not change

Hello!
I can no longer flash anything to my GT-P5110, even factory reset has no effect. The internal storage seems to be read-only.
I think this is a longer story: About one year ago the stock firmware became incredibly slow, to the point that processes started to force close, then my user data was lost, and after factory reset the tablet went into endless boot loop.
So I decided to give CM10 a try and it worked flawlessly. The tablet was fast again. I even could upgrade to CM11 later. But around 2 month ago, only sometimes processes started to force-close or the tablet randomly rebooted itself - mostly during charging. I left it that way in the charger for some days because I had no time to bother with that issue. Then, I tried to factory reset my device only to find out that this has absolutely no effect. Installing app updates: No effect. Changing system settings: No effect. And apps start to force-close at an insane rate short after boot. The device is unusable. My could only shut down and reboot into recovery. I left the tablet lying around, turned off, out of charger, for 2 months. Now I tried to investigate:
When I "adb shell" into recovery and call dmesg, I see lots of these lines:
Code:
mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
I think something is really broken with the internal storage. I tried to flash a newer recovery but it has no effect, even when done from download mode.
Factory reset sometimes fails with an error. Reinstalling CM fails with an error. Wiping cache seemingly succeeds but I'm sure it has no effect. I tried installing SlimRom instead which seemingly succeeds, too - but after reboot I'm greeted with the CM boot logo again.
I tried to flash stock firmware with Odin. It is very very slow, runs for about 15 minutes, then fails at around 50%. Of course: That "half flashed firmware" does in no way affect the device: It still boots CM11 "without problems", then a few seconds after finishing boot (showing home screen), force-closes start to pop-up.
What should I do? I suppose the device is out of warranty for a few weeks or months, now. And even when not: It has been flashed with CM, the triangle counter is not zero. I suppose that combination of problems (read-only/failing storage, non-stock firmware) voids warranty in a way that Samsung will deny any repair. If at least I could return the device to stock firmware things would be different maybe.
Any ideas what I could try? Is it possible that the internal storage is simply fried? fsck'ing the partitions shows no errors, just the data partition is unclean with unwritten journal data but all data is readable. So the internal storage has probably not died. It just sticks to read-only mode for whatever reason.
I've found some posts with similar problems but those seem to be about older Galaxy Tab 1 devices built 2011 or before.

Just reading over this and it sounds very similar to what I'm currently facing, which is doubly annoying as no one else has chipped in a solution
I had reboot issues with my Tab2 10.1 (GT-P5110) on stock so after realizing I'd need to factory reset bite the bullet and rooted so I could use CM10.
Had occasional reboots but nothing I couldn't live with however from yesterday evening the tablet is seemingly stuck in a boot loop. It comes on, some apps fire up and an update starts. Sometimes apps force close then BOOM I get the boot splash screen.
I've tried factory reset in recovery (CWM 6.0.2.7) to no avail and wiping just about everything which also had no noticeable effect as all my settings and the rom are still the same when I get back in (albeit briefly!).
I've tried flashing new recovery via ODIN which reported a success however that also didn't appear to take. I'm beginning to think it some serious file system or storage corruption ;(

Same problem here...
Hopefully someone can come up with a solution or at least a cause. I've tried to Odin every recovery available for my 5113 and nothing has taken. I'm currently on Omni with cwm and tried to update to the latest cwm and twrp and aroma installer yet nothing takes. I too rooted because of the incessant bootloops about 3 months ago.

bigg fella said:
Hopefully someone can come up with a solution or at least a cause. I've tried to Odin every recovery available for my 5113 and nothing has taken. I'm currently on Omni with cwm and tried to update to the latest cwm and twrp and aroma installer yet nothing takes. I too rooted because of the incessant bootloops about 3 months ago.
Click to expand...
Click to collapse
For what I can tell, my device is effectively read-only. Even in download mode (Odin) I cannot even flash a different recovery (tried to flash TWRP, still boots CWM).

hurikhan77 said:
For what I can tell, my device is effectively read-only. Even in download mode (Odin) I cannot even flash a different recovery (tried to flash TWRP, still boots CWM).
Click to expand...
Click to collapse
exactly, can't even uninstall an app. It's as if it boots from a permanent back up because even deleting pictures or files isn't permanently successful. You can uninstall and delete to your hearts content, get false hope, and get crushed after it reboots and everything is unchanged

Not looking very optimistic for this I was getting a similar inkling that it's gone into a permanent RO mode as not even the wipes from recovery have an effect. I'd also tried un-installing apps as I noticed one updating and thought it was crashing it however even when it did fire up and I disabled WLAN to stop Play Store auto-updating and removed the app on the next reboot cycle the app was back:crying::crying:
I fear I may have a big white paperweight....

Sounds like the internal partitions might need to be completely reformatted. This CAN be done through recovery, but is tricky... However without actually having your device in my hand I'm not sure 100 what the best course of action would be. Try searching for the commands to format (or maybe someone else will post them) or maybe PM me for them but no promises. I won't post them publicly on XDA because honestly there are too many users who do stuff like one-click root and don't actually know what they're doing and I don't want to be in some way responsible for someone following the command wrong and bricking their device for good. I don't need that on my conscience. Personal choice.
Sent from my Nexus 4 using XDA Premium HD app

shakatu said:
Sounds like the internal partitions might need to be completely reformatted. This CAN be done through recovery, but is tricky... However without actually having your device in my hand I'm not sure 100 what the best course of action would be. Try searching for the commands to format (or maybe someone else will post them) or maybe PM me for them but no promises. I won't post them publicly on XDA because honestly there are too many users who do stuff like one-click root and don't actually know what they're doing and I don't want to be in some way responsible for someone following the command wrong and bricking their device for good. I don't need that on my conscience. Personal choice.
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
Would this method be any different to the way it attempts to reformat the internal partitions when you select to format the various mounts from CWM? If so I'm more then willing to give it a go as I really have nothing to lose as the damn thing is useless atm!

shakatu said:
Sounds like the internal partitions might need to be completely reformatted. This CAN be done through recovery, but is tricky... However without actually having your device in my hand I'm not sure 100 what the best course of action would be. Try searching for the commands to format (or maybe someone else will post them) or maybe PM me for them but no promises. I won't post them publicly on XDA because honestly there are too many users who do stuff like one-click root and don't actually know what they're doing and I don't want to be in some way responsible for someone following the command wrong and bricking their device for good. I don't need that on my conscience. Personal choice.
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
Good call......Smart move?

help!!
same issue here , sort of .. i have stock rom and stock recovery and i cannot flash CWM .. no matter how many times i try through ODIN or hemidal nothing changes.. any idea what is going on here?

PMs have been sent. Hopefully it works.
Sent from my Nexus 4 using XDA Premium HD app

im also having this issue with my galaxy tab2 7".. help is badly needed

Well, the proposed fix I had didn't help. Was worth a shot...
Sent from my Nexus 4 using XDA Premium HD app

hope someone finds a solution for this.

No Access to ADB
shakatu said:
PMs have been sent. Hopefully it works.
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
Hi Shakatu,thanks for the PM, however, my device in ADB is unauthorised, so wont let me get into shell. Is there a way around this please?

sunnytimes said:
same issue here , sort of .. i have stock rom and stock recovery and i cannot flash CWM .. no matter how many times i try through ODIN or hemidal nothing changes.. any idea what is going on here?
Click to expand...
Click to collapse
Unmark "Auto Reboot" in Odin when CWM is flashed... Stock room overwrites it during start.
After flashed CWM start in Recovery mode and flash new ROM.
this is offtopic in this tread

same problem please help me... :crying:

seagman said:
Unmark "Auto Reboot" in Odin when CWM is flashed... Stock room overwrites it during start.
After flashed CWM start in Recovery mode and flash new ROM.
this is offtopic in this tread
Click to expand...
Click to collapse
i have tried that 100 times .. its also exactlly what this thread is about , not being able to flash because nothing changes..

sunnytimes said:
i have tried that 100 times .. its also exactlly what this thread is about , not being able to flash because nothing changes..
Click to expand...
Click to collapse
same here too, i have same issue.. unable to flash or do anything to my phone....

Probably this is the end for our tab. As off now the tab is useless.
Sent from my GT-N7000 using XDA Free mobile app