Related
Well again.... Im about to lose my minda because of this damn thing! Now I'm getting a fc every 5 sec... Process acore? My tab is essentially dead? Can't do anything author a fc, can't go into settings our anything... I want to smash this thing! I just got it working well and now this? Anyone know what that process is? I cam do anything with it now, cant load a new rom because I can't get into settings. Its just in an intimate loop of fc. The real disaster is im in idaho, where I got it as a gift, and I'm flying back to nc in the morning.. Can't take out back before I leave..
Anyone know anything about the fc?
Sent from my SAMSUNG-SGH-I897 using XDA App
Setting---appliction----Clear the contacts and ContactsProvider data .
I can't get into settings... It fc's every time I try to go into settings. Any other way to do it?
Sent from my SAMSUNG-SGH-I897 using XDA App
I think I need to do a reset, but if I can't open settings I'm lost? Not sure how it happened, it just started doing it.
Sent from my SAMSUNG-SGH-I897 using XDA App
pqrs said:
I think I need to do a reset, but if I can't open settings I'm lost? Not sure how it happened, it just started doing it.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
If you can get ClockWork to run on boot .You might need to wipe data and reinstall the rom..Not much you can do when it is constantly Fc'ing
Well I don't have cw on the tab, its still stock.. I'm hoping I can plug into a pc, download it and get root that way? Then possibly load a new rom... Otherwise I'm screwed.
Think that will work?
Sent from my SAMSUNG-SGH-I897 using XDA App
Maybe you should restore it back to factory settings...
http://forum.xda-developers.com/showthread.php?t=861950
That will bring it back to how it was out of the box, then start over.
If there are still issues then possible hardware problems?
Had this issue, even after NV flash. I was able to get CW (even with the fc) on and wipe, and partition the sd to 2gb. That seems to have cleaned it up.
This forum is the greatest on the entire internet!
Glad to hear you got it working. Imo, your issue is probably the worst thing about running stock - if you get these FC's, there's really no fix unless you take the risk of using a mod.
I believe it's the same reason why Staples pulled the devices - too many returns due to FC's OOTB.
Yes, it's too bad they did not include the "easy" button to reset to stock. Even with the upgrade, it may be enough to ultimately kill off the device. With all of the recovery images on my laptop now, I can put humpty dumpty back with ease. It's good for me, I plan to watch for returns. I could use a couple more of these.
I got cw installed and vegan, the table works like I'd expect now! This thing is awesome! Thanks for the help.
A resolution
I had this same issue happen to me on a new ROM not factory. I couldn't get into settings either to do the contact wipe. But Titanium was installed on it and I was able to wipe the contact data through there. Just an FYI if anyone else runs across the same problem.
Thanks to you Snyper....I just picked up my tab after placing it down for 10 mins and saw this error. Just a quick search in the thread and there is the answer. Man this forum rocks!!!
Just happened to me running vegan 3
clearing contact info worked like a champ!
thanks guys
I have the same issue. But, I don't have CW installed, Titanium won't load up. How can I manually get the clockword APK file on there to attempt to install it?
Any other ideas?
Gravislord said:
I have the same issue. But, I don't have CW installed, Titanium won't load up. How can I manually get the clockword APK file on there to attempt to install it?
Any other ideas?
Click to expand...
Click to collapse
Clockwork is not an apk. Read this
Post 1
http://forum.xda-developers.com/showthread.php?t=865245
Post 1
http://forum.xda-developers.com/showthread.php?t=892090
roebeet said:
Glad to hear you got it working. Imo, your issue is probably the worst thing about running stock - if you get these FC's, there's really no fix unless you take the risk of using a mod.
I believe it's the same reason why Staples pulled the devices - too many returns due to FC's OOTB.
Click to expand...
Click to collapse
Hi,
Having had this acore FC problem last night, I have a couple of questions:
1) In your post above, you seem to have thought that this only happens with stock TNT. But, in this thread, it seems like others that are not running stock TNT also encounter this problem. So, it this a potential problem with all ROMs, or just with stock TNT?
2) From reading through and other threads, one fix when it happens is to clear the Contacts and ContactsProvider data, either using Settings, if you can get to it, or using Titanium, if you have it. I'm assuming that what both of those steps do is to clear out the tables in SQLlite for the Contacts and ContactsProvider apps. Is that right? If it is, do you, or does anyone know the command lines that would do the same thing?
The reason for the latter question is that when I had the problem, I could still do adb shell. If there was an sqllite command I could have used to clear the problem, I definitely would have done that, instead of having to install CWM, re-partition, and re-flash stock 3452!
Thanks,
Jim
Alright folks, my phone appears to have gone off the deep end.
A few weeks back, I was changing over to the new Eclipse ROM, and at first everything was going fine and dandy. However, I soon began experiencing a few force closes. I restarted the phone, and then everything went to hell. So many force closes I couldn't operate the phone, inability to make calls, unable to open apps, unable to install apps, basically all I can do is text, receive calls, and browse the web (although after enough time the phone crashes anyway). I have tried everything I know of to fix it: new ROMs via recovery, new ROMs via Odin, deleting caches, deleting personal data, using the .pit file and factory stock in Odin, the works. I even found the Samsung PST and used that, but for naught. The weird thing is that even after using the .pit file (which is supposed to delete EVERYTHING), my phone "remembers" old applications that were installed on it. In fact, it seems like there is some sort of ghost image on my phone, and whenever I restart it the phone returns to that state (any applications I tried to uninstall are back, all contact data is deleted, etc.). This ghost image hangs around no matter what I do.
Any suggestions?
Sounds to me that you obviously are not getting a true "PASS" with pit file. If you had you would have no files saved on phone. But if you followed the instructions to a "t" like you allude to...
Sent from my SCH-I510 using xda premium
I have followed the instructions fully (and multiple times to boot), and I have always gotten a PASS.
This is sounding regrettably similar to the issues reported in this thread - try looking at post numbers in the mid 300s - I think they are centered around late September/early October (there are more than this, but I'm pretty sure that timeframe has the highest density of discussion on this). If it's what it sounds like, the /data partition is no longer in a state that can be written over (the "ghost image" you were referring to) - and truth be told I don't know if anyone has come up with a "free" solution to the problem.
dwitherell said:
This is sounding regrettably similar to the issues reported in this thread - try looking at post numbers in the mid 300s - I think they are centered around late September/early October (there are more than this, but I'm pretty sure that timeframe has the highest density of discussion on this). If it's what it sounds like, the /data partition is no longer in a state that can be written over (the "ghost image" you were referring to) - and truth be told I don't know if anyone has come up with a "free" solution to the problem.
Click to expand...
Click to collapse
I had read through those posts before, and was not very happy to see the conclusion. As those posts were from a few months ago, I was hoping that perhaps someone had some new ideas. Oh well, I guess I'll be trying my luck with Verizon. Thanks for trying, folks!
jderig said:
I had read through those posts before, and was not very happy to see the conclusion. As those posts were from a few months ago, I was hoping that perhaps someone had some new ideas. Oh well, I guess I'll be trying my luck with Verizon. Thanks for trying, folks!
Click to expand...
Click to collapse
Thinking... What recovery does your phone have on it now- stock or clockwork? Are you on rfs file system- did you revert back or can you flash a diff kernel using cwr?
These are just some thoughts that came to mind. If dwith can't help you I can't do much more. Good luck with Verizon offering any help
Sent from my SCH-I510 using xda premium
Corrupted NAND, but still returns a pass.
I had this once, I spammed with the PIT and it somehow worked
Sent from my SCH-I510 using xda premium
Hindle1225 said:
Thinking... What recovery does your phone have on it now- stock or clockwork? Are you on rfs file system- did you revert back or can you flash a diff kernel using cwr?
These are just some thoughts that came to mind. If dwith can't help you I can't do much more. Good luck with Verizon offering any help
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
I currently have Clockwork. I am unable to tell at this moment what my file system is, as I can't install Voodoo, and the method of adding/deleting folders on my SD card doesn't work. However, I do recall during one of my many attempts at using different kernels/radios/roms I did get the creepy female Voodoo bootup voice, but even though that said it was a success I was never able to tell whether it actually worked.
As of right now I am capable of ODIN and Clockworking any Rom/kernel/etc., but they all bring along the Ghost Image.
kvswim said:
Corrupted NAND, but still returns a pass.
I had this once, I spammed with the PIT and it somehow worked
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
What is NAND, if you don't mind me asking? Also, I suspect by now I've run ODIN with the PIT 10+ times with no success
jderig said:
What is NAND, if you don't mind me asking? Also, I suspect by now I've run ODIN with the PIT 10+ times with no success
Click to expand...
Click to collapse
NAND is just a type of flash memory. If you recognize the word nand then you should have an idea. If not, it's not really important.
jderig said:
Alright folks, my phone appears to have gone off the deep end.
A few weeks back, I was changing over to the new Eclipse ROM, and at first everything was going fine and dandy. However, I soon began experiencing a few force closes. I restarted the phone, and then everything went to hell. So many force closes I couldn't operate the phone, inability to make calls, unable to open apps, unable to install apps, basically all I can do is text, receive calls, and browse the web (although after enough time the phone crashes anyway). I have tried everything I know of to fix it: new ROMs via recovery, new ROMs via Odin, deleting caches, deleting personal data, using the .pit file and factory stock in Odin, the works. I even found the Samsung PST and used that, but for naught. The weird thing is that even after using the .pit file (which is supposed to delete EVERYTHING), my phone "remembers" old applications that were installed on it. In fact, it seems like there is some sort of ghost image on my phone, and whenever I restart it the phone returns to that state (any applications I tried to uninstall are back, all contact data is deleted, etc.). This ghost image hangs around no matter what I do.
Any suggestions?
Click to expand...
Click to collapse
just covering bases by asking, did you go ALL the way back to ed1 with that pit file or a more recent version (gb or something along those lines)
From what I understand, the phone is still working, but is very unstable. The PBJ kernel does NOT support Voodoo Lagfix (but still supports EXT4). Can you try flashing imoseyon's kernel (which supports it) and enabling/disabling Voodoo? It can be found at RootzWiki. Also, when you get into CWM, it says the version at the top.
Sent from my SCH-I510 using xda premium
Here you go....i have been here.
Get into clockwork(CWM) - mount everything via usb and backup what you need to backup.
Perform a quick format of your sdcard so that when you see your phone on the pc, its blank.
Go back to stock odin and boot up, report any issues.
Sent from my SCH-I510 using XDA
What happened next
I tried what you said because I'm in the same boat. I still get the FCs and it tries to walk me through the setup. It gets stuck at the Checking Account step in the setup wizard. I let it sit there for about an hour while I went to lunch to no avail.
I'm not a dev, but it's obvious to me something is wrong.
I re-flashed the eaglesblood ICS rom using clockworkmod recovery v.5.8.1.3 (touch version)
everything seemed okay.
until i started putting apps back on my phone with app backup and restore.
I was getting "process syystem has stopped responding" all over the place.
Then the phone crashed.
it keeps booting, only three apps seem to be running that show themselves in the taskbar, Groove IP, GV SMS integration, and Battery Notifier (Big Text)
It sits there, one one of the home screens, LW animating slowly as it will.. then the phone reboots for no reason.
I installed 4 or 5 different logcat apps but i can't make heads or tails of them
and adb logcat > logcat.txt just spits out this :
/sbin/sh: exec: line 1: logcat: not found
dmesg spits out the log i'm attaching.
Can anyone help me? If i can save the log from one of the logcat apps, will that help?
I'd rather not have to reflash and re-install apps AGAIN.
Where you flashing EB 4.0.4 from gingerbread ?
In any case a full wipe and reflash of the ROMs would work fine. Then reflash the appropriate gapps, But when restoring the apps using TB just restore at apps and not their data. They sometimes don't play well.
I had a similar issue when I tried flashing the 4.2 gapps on 4.1.2 keyboard would crash everytime and any app that uses even one of the google services would crash right away.
I cleared dalvic cache did a dirty flash over my existing 4.1.2 , reflashed the 4.1.2 gapps then I fixed permissions and in was good to go.
Sent from my LG-P999 using xda app-developers app
Barracuda1101 said:
Where you flashing EB 4.0.4 from gingerbread ?
In any case a full wipe and reflash of the ROMs would work fine. Then reflash the appropriate gapps, But when restoring the apps using TB just restore at apps and not their data. They sometimes don't play well.
I had a similar issue when I tried flashing the 4.2 gapps on 4.1.2 keyboard would crash everytime and any app that uses even one of the google services would crash right away.
I cleared dalvic cache did a dirty flash over my existing 4.1.2 , reflashed the 4.1.2 gapps then I fixed permissions and in was good to go.
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
so a dirty reflash and fix permissions might help?
Funny enough, after posting that, and hitting reboot on CWM recovery.. the phone came up with the cord plugged in, and seems to be stable for now.
Uhm. i was flashing from.... heck if i know, i've tried a bunch of roms.
the phone INITIALLY was 2.3.4
back when i started.. months ago.
Eve_brea said:
so a dirty reflash and fix permissions might help?
Funny enough, after posting that, and hitting reboot on CWM recovery.. the phone came up with the cord plugged in, and seems to be stable for now.
Uhm. i was flashing from.... heck if i know, i've tried a bunch of roms.
the phone INITIALLY was 2.3.4
back when i started.. months ago.
Click to expand...
Click to collapse
grrrrrrrrrr. i'm back at the crashing behavior
I see "equalizer activated " then the phone gets stuck... that same "equalizer activated" thing came up when i added speakerboost... wonder if it's the cause..
Eve_brea said:
grrrrrrrrrr. i'm back at the crashing behavior
I see "equalizer activated " then the phone gets stuck... that same "equalizer activated" thing came up when i added speakerboost... wonder if it's the cause..
Click to expand...
Click to collapse
*grumble* damn sun-downer phone. SO all night it was crashing.. So i finally got irritated when i went to bed, yanked the battery out and plopped it on my night-stand by my fan.
This morning i put the battery in, turn it on, and it seems stable.
What the heck?!
logs.
So... between all the log apps i've played with i have a bunch of logs.. if anyone could look them over and tell me if they see a problem, i'd appreciate it.
Re-download Rom+Gapps
Place on SD card
Re-nvflash cwm recovery 5.0.2.0
Wipe data/cache/davlk/battstats/format system
Install rom+gapps
Wipe cache/davlk/battstats
Fix permissions
Reboot
Using touch is sometimes buggy, 5.0.2.0 is most stable. Restoring apps/data is sometimes a messes things up.
Sent from my LG-P999 using xda app-developers app
I have a possibly simple yes or no question in the case there is no alternative. So, I am currently running 4.2.2 PAC-Man Rom and I want to update to the 4.3 version of it. Technically, speaking, I have no issues in updating the ROM itself. The problem is when I try to keep my app data moving from 4.2.2 to 4.3. Whenever I try to restore data via Titanium Backup, the phone will allow it, but upon the next shutdown, will not boot again. Likewise, I have also tried to flash 4.3 and then do an advanced restore via CWM and only restore data. This has the same results as the previous option in that I can boot the phone, but if I shut it off, it won't restart. Basically, I can keep and install the original app apks, but the moment I try to restore any form of app data from the previous iteration of the ROM, my phone will refuse to restart. This predicament is met on any 4.3 ROM I have tried. I have never had this problem before, as I have been able to move from 4.1.2 to 4.2.1 to 4.2.2 (I suppose 4.3 is different?). This brings me to my question, is it possible to keep app data moving from 4.2 to 4.3? I fear I already know the answer. In any case, thank you for your time.
Tl;DR
When moving to 4.3, restoring app data from previous rom (PAC-man 4.2.2) causes the phone to lose the inability to boot. Is there any way to keep app data, or is it a lost cause? Thank you for your time.
One thing that comes to mind is are you restoring any system data? That causes problems.
Other than that I would download and install all my apps through the app store and reboot.
Then make a restore image to fall back on so you don't have to repeat these steps.
Now start restoring you app data SELECTIVELY. And restore app data ONLY. And do it one by one and reboot. This is the only way I know that can pin point the problem or the one restore data piece causing you problem.
Identifying it is the hardest part, any better ideas are welcomed.
Once identified just avoid that one app as your migration casualty.
Good luck,
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
verissimus said:
I have a possibly simple yes or no question in the case there is no alternative. So, I am currently running 4.2.2 PAC-Man Rom and I want to update to the 4.3 version of it. Technically, speaking, I have no issues in updating the ROM itself. The problem is when I try to keep my app data moving from 4.2.2 to 4.3. Whenever I try to restore data via Titanium Backup, the phone will allow it, but upon the next shutdown, will not boot again. Likewise, I have also tried to flash 4.3 and then do an advanced restore via CWM and only restore data. This has the same results as the previous option in that I can boot the phone, but if I shut it off, it won't restart. Basically, I can keep and install the original app apks, but the moment I try to restore any form of app data from the previous iteration of the ROM, my phone will refuse to restart. This predicament is met on any 4.3 ROM I have tried. I have never had this problem before, as I have been able to move from 4.1.2 to 4.2.1 to 4.2.2 (I suppose 4.3 is different?). This brings me to my question, is it possible to keep app data moving from 4.2 to 4.3? I fear I already know the answer. In any case, thank you for your time.
Tl;DR
When moving to 4.3, restoring app data from previous rom (PAC-man 4.2.2) causes the phone to lose the inability to boot. Is there any way to keep app data, or is it a lost cause? Thank you for your time.
Click to expand...
Click to collapse
What recovery are you using? If it's not TWRP 2.6.0.3 or newer, or the custom CWM provided by Team Chopsticks, you will continue to have this problem. Also, it has absolutely nothing to do with restoring data.
Fixed XD
Okay, so I have been doing nandroid backups the whole time, so I haven't really lost anything. I did try to install apps using Google Play and it would cause the same problem that restoring data only via cwm would. That said, I got bored and just left the phone boot looping and slept for 5 hours. Interestingly enough, upon checking on it later, it had in fact booted and it did function. Naturally, I reverted back to 4.2 and tried to upgrade again, this time timing it. Over all, it took about 1 hour for the phone to stop bootlooping and actually boot up. I don't really know what is wrong, but hey, it works. Nevertheless, I would like to thank you guys for your input. Sorry that my problem wasn't actually what I thought it was. :/ Good day.
verissimus said:
Okay, so I have been doing nandroid backups the whole time, so I haven't really lost anything. I did try to install apps using Google Play and it would cause the same problem that restoring data only via cwm would. That said, I got bored and just left the phone boot looping and slept for 5 hours. Interestingly enough, upon checking on it later, it had in fact booted and it did function. Naturally, I reverted back to 4.2 and tried to upgrade again, this time timing it. Over all, it took about 1 hour for the phone to stop bootlooping and actually boot up. I don't really know what is wrong, but hey, it works. Nevertheless, I would like to thank you guys for your input. Sorry that my problem wasn't actually what I thought it was. :/ Good day.
Click to expand...
Click to collapse
This is due to the recovery version you are on as the guy before your last post indicated. It has nothing to do with your restoration of data, but rather the recovery used to flash the rom and the way it's handling the partitions.
Long story short, update your recovery to one of the ones indicated two posts above mine and you should be good to go.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
bps119 said:
This is due to the recovery version you are on as the guy before your last post indicated. It has nothing to do with your restoration of data, but rather the recovery used to flash the rom and the way it's handling the partitions.
Long story short, update your recovery to one of the ones indicated two posts above mine and you should be good to go.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Ah, okay, that makes a great deal of sense. Thank you for elucidating, I shall do just that.
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