Update 03/28: Problem resolved with assistance from BadaB!ng developer of collective rom. Thank you for the help. Will post reference link.
Update 03/27: Problem not resolved. 4.04 system was some factory test image and everything I tried to flash or update caused the problem to repeat.
Problem resolved: tried the 4.04 image odin flashed
Model: GT-N8013
User Level: Idiot (Me)
I was playing with the pimp my rom app believing that it was a part of the Collective 5.1 rom, which is 100% my fault. Rebooting is a part of the completion of those tweaks and upon reboot, I could not get passed the samsung galaxy note 10.1 screen. I tried a restore and still stuck. I decided to odin flash back to stock and I am still stuck. I then went into recovery and did a factory wipe and reset. Still stuck. It did say that it could not mount /efs during the process [Invalid Argument]. I am in passed my knowledge base and am hoping another knows what to do.
Thank you for your time.
fftlambet said:
Problem resolved: tried the 4.04 image odin flashed
Model: GT-N8013
User Level: Idiot (Me)
I was playing with the pimp my rom app believing that it was a part of the Collective 5.1 rom, which is 100% my fault. Rebooting is a part of the completion of those tweaks and upon reboot, I could not get passed the samsung galaxy note 10.1 screen. I tried a restore and still stuck. I decided to odin flash back to stock and I am still stuck. I then went into recovery and did a factory wipe and reset. Still stuck. It did say that it could not mount /efs during the process [Invalid Argument]. I am in passed my knowledge base and am hoping another knows what to do.
Thank you for your time.
Click to expand...
Click to collapse
This happened from pimp my rom?
Sent from my GT-N8013 using XDA Premium HD app
seshaz said:
This happened from pimp my rom?
Sent from my GT-N8013 using XDA Premium HD app
Click to expand...
Click to collapse
I have no way to confirm that, however, that is where I made the last change that required root and reboot occurred. From that reboot, I could only get to the Samsung Galaxy Note 10.1 screen. I need to make an update...I was mistaken when I said it was fixed. The 4.04 image that I flashed worked but was not complete...no lock screen, had some factory test program on it, and anything new I flashed or updated to resulted in getting the screen stuck on Samsung Galaxy Note 10.1 again. I am trying to find other images to odin flash or another instance of this issue.
Related
Hi, I rooted my S2 6 months or so ago, and haven't had any issues, but last night, I changed my font, and rebooted, ans since then it won't boot past the logo screen.
I can't remember which software i have used to flash the phone, other than I used odin, and in the PDA section the file is called CF - Root _XX_XEO_LPQ-v5.3-CWM.
I have tried to restore factory settings, and also going through Odin again, but still won't work.
Any ideas??
You could try flashing your stock Rom again. Usually when I get stuck in boot loop that is always worked for me. Its nothing to worry about. Go to settings- about phone and that will tell you everything you need to regarding Rom, kernel etc
Sent from my GT-I9300 using xda app-developers app
t_appletart said:
Hi, I rooted my S2 6 months or so ago, and haven't had any issues, but last night, I changed my font, and rebooted, ans since then it won't boot past the logo screen.
I can't remember which software i have used to flash the phone, other than I used odin, and in the PDA section the file is called CF - Root _XX_XEO_LPQ-v5.3-CWM.
I have tried to restore factory settings, and also going through Odin again, but still won't work.
Any ideas??
Click to expand...
Click to collapse
If it still shows the logo, your phone is safe. Don't send it for repair. You could fix it by yourself
Download a firmware from sammobile.com. Flash it through odin
And btw you'll get more and quicker helps if you post this thread in the sgs2 section.
Sent from my GT-I9100 using xda premium
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.
Hey everyone, I've done some searching but I can't seem to find what I'm looking for. I was having a problem with my CM10 installations so I decided to revert back to a stock rom and start fresh.
I used odin to flash "I727UCLF6_I727ATTLF6_I727UCLF6_HOME.tar.md5" (which is supposed to be the stock ICS rom for at&t) and everything goes great, but the phone now hangs on the "Rethink Possible" AT&T logo. I've let it sit for about an hour so I'm pretty certain that nothing is going to happen.
I tried doing the same thing over hoping that maybe it was a bad flash or some kind of fluke, but came back to the exact same problem.
Any suggestions here would be phenomenal! :silly:
Factory reset
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mmerlina said:
Hey everyone, I've done some searching but I can't seem to find what I'm looking for. I was having a problem with my CM10 installations so I decided to revert back to a stock rom and start fresh.
I used odin to flash "I727UCLF6_I727ATTLF6_I727UCLF6_HOME.tar.md5" (which is supposed to be the stock ICS rom for at&t) and everything goes great, but the phone now hangs on the "Rethink Possible" AT&T logo. I've let it sit for about an hour so I'm pretty certain that nothing is going to happen.
I tried doing the same thing over hoping that maybe it was a bad flash or some kind of fluke, but came back to the exact same problem.
Any suggestions here would be phenomenal! :silly:
Click to expand...
Click to collapse
Reboot into recovery which will be stock recovery factory reset 3x and wipe cache 3x reboot and it will come up.
Yep you guys were right that did the trick! I didn't even think of it. I meant to post this last night when I actually did it but I fell asleep.
Do you know what exactly the phone is doing (or trying to do) when this actually happens to cause it? Just out of curiosity.
Thanks again!
Only way to find out is connect a debugger. Android SDK, ddms.bat
I'm not sure exactly but I have had similar issues with getting stuck in a boot loop. Usually formating and factory reset and a fresh flash did the trick.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
This is my first post and I'm not sure where to put it but I hope this is right.
I'm kinda new to flashing ROMs and was trying to flash one using safestrap on my GS3. I couldn't find one that worked and went back to my stock ROM. In the stock ROM cell service completely died and wouldn't work, to combat this problem I removed all ROMs, ROM slots, and wiped the stock ROM cache. Nothing. So then I restored to my nandroid backup I made yesterday and that deleted my OS. Now when I boot it just gets stuck at the second Samsung boot logo (there the first one that just says "Samsung" and "unlocked", then the second on says "Galaxy SIII" or something) now I have no OS and I'm not sure how to fix this, can I get some help please?
Okay, I got the stock firmware installed but I still have no service anywhere. Any ideas?
apcake said:
This is my first post and I'm not sure where to put it but I hope this is right.
I'm kinda new to flashing ROMs and was trying to flash one using safestrap on my GS3. I couldn't find one that worked and went back to my stock ROM. In the stock ROM cell service completely died and wouldn't work, to combat this problem I removed all ROMs, ROM slots, and wiped the stock ROM cache. Nothing. So then I restored to my nandroid backup I made yesterday and that deleted my OS. Now when I boot it just gets stuck at the second Samsung boot logo (there the first one that just says "Samsung" and "unlocked", then the second on says "Galaxy SIII" or something) now I have no OS and I'm not sure how to fix this, can I get some help please?
Okay, I got the stock firmware installed but I still have no service anywhere. Any ideas?
Click to expand...
Click to collapse
Uhhhmmmm would flashing the modems help? (directed towards the more knowledged users)
Sent from my SCH-I535 using XDA Free mobile app
poppers162 said:
Uhhhmmmm would flashing the modems help? (directed towards the more knowledged users)
Sent from my SCH-I535 using XDA Free mobile app
Click to expand...
Click to collapse
It might. It depends on what modem they are currently on
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
apcake said:
This is my first post and I'm not sure where to put it but I hope this is right.
I'm kinda new to flashing ROMs and was trying to flash one using safestrap on my GS3. I couldn't find one that worked and went back to my stock ROM. In the stock ROM cell service completely died and wouldn't work, to combat this problem I removed all ROMs, ROM slots, and wiped the stock ROM cache. Nothing. So then I restored to my nandroid backup I made yesterday and that deleted my OS. Now when I boot it just gets stuck at the second Samsung boot logo (there the first one that just says "Samsung" and "unlocked", then the second on says "Galaxy SIII" or something) now I have no OS and I'm not sure how to fix this, can I get some help please?
Okay, I got the stock firmware installed but I still have no service anywhere. Any ideas?
Click to expand...
Click to collapse
First thing I would do is make sure your imei is still present in the about phone section. If it is, move on to the next step.
I would go completely back to stock, Odin flash either the stock 4.3 or 4.4 image depending on which you were on. If you're unsure, post what it says in download mode.
If you do that and you still have no service, then go to verizon and get a new sim card. Flashing a new modem wouldn't fix this situation.
BadUsername said:
First thing I would do is make sure your imei is still present in the about phone section. If it is, move on to the next step.
I would go completely back to stock, Odin flash either the stock 4.3 or 4.4 image depending on which you were on. If you're unsure, post what it says in download mode.
If you do that and you still have no service, then go to verizon and get a new sim card. Flashing a new modem wouldn't fix this situation.
Click to expand...
Click to collapse
it appears as though the sim was wiped
apcake said:
it appears as though the sim was wiped
Click to expand...
Click to collapse
Grab a new sim card.
So I know there's not much support for this device anymore but I'm stuck in the water with my Galaxy S6 wondering if anybody can help here's my situation:
I have a SM-G920V on firmware OE2 as of yesterday. I have been rooted running the revolution 1.0 ROM for about year now with no problems. Yesterday I was doing some things in titanium backup and I tried to move a system app over to a user app. Well things got hairy and it ended up soft bricking my phone. I was stuck in a boot loop at the main splash screen with no way around it. I tried everything at that point that I know of. I put it into recovery mode, tried to boot in safe mode, wiped cache via recovery, did a factory reset via recovery . Still just a boot loop.
So then I came across the Stock Odin thread and I have tried OE2 f and then OC3 with the same outcome on both for . The FW flashes but when I boot up the phone and start the setup wizard I get stuck at the first step of it trying to activate the phone/ phone number . The System even becomes a bit glitchy and starts not responding at this point and will reboot randomly . This happens on both firmwares that I tried from that thread ....I can't get it past the activation. I did try a factory reset on OE2 after I Odin the tar to see if that helped but still got stuck at activation
I actually took the phone in to Verizon last night and it's sad because the customer service rep only tried about 5% of the things(5 min) that I tried before saying that the phone was "toast". All he did was go to recovery mode and tried to factory data reset ,which I had told him I tried many times and did not work. Fortunately or unfortunately enough my work replaced the phone with a brand new Galaxy S7 which I am using now. I still have the S6 though and I'm just determined not to give up yet because I don't think this phone is "toast" . If anyone can shed some light or has had the same problem and knows a fix I would love to know. I would absolutely love to be able to get this thing fixed and be able to give it to my daughter for Christmas.
Thanks in advanced!
Sent from my SM-G930V using Tapatalk
Sent from my SM-G930V using Tapatalk
It maybe worth noting that while I'm in download mode or Odin mode on the phone it does say the reactivation lock is on. I know I've read this is cause some problems for people later on in the process so I thought I would mention it
Sent from my SM-G930V using Tapatalk
Bump. Anyone have any suggestions or input?
Sent from my SM-G930V using Tapatalk
Problem resolved thread can be closed. I flashed FM PI2 and it seemed to fix my issues. Something with root and the bootloader were conflicting.
Sent from my SM-G930V using Tapatalk
Hello,
what is FM PI2? thanks.
Dayd said:
Hello,
what is FM PI2? thanks.
Click to expand...
Click to collapse
The latest firmware release from Samsung. Can be found HERE
Sent from my SM-G930V using Tapatalk