Just got a brand new N7100 today. Do my usual thing as with all my phones, flash CWM, root, flash custom rom (Omega v8.0). Changed kernel to Note2Core (OC, NOT EXTREME VERSION WITHOUT FSYNC), was running for a bit then it rebooted itself.
After reboot, phone won't run, so I go to do a full system wipe. Except now I can't wipe /data. Tried 3 different CWMs including TWRP (TWRP doesn't even start, just shows load screen then reboots).
Flashed stock ROM with ODIN including .PIT but the /data isn't being cleared, I can't clear it in any way. Only way to get the phone working now is stock ROM through ODIN but it boots up with a bunch of messed up stuff and I can't factory reset.
I have tried scanning for EMMC Brickbug but there are no errors. This one has got me stumped, I know my way around recoveries and android etc. but can't for the life of me figure out what I can do to fix this.
Don't really want to send in for warranty as I probably have a flashcounter (I will try to flash a rooted ROM through ODIN and triangleaway..)
Hoping since there's no EMMC brickbug triggered from the scans, that there's some way to fix this. I thought flashing PIT would wipe the /data partition but obviously not.
Any ideas? Would be most appreciated.
Thanks
I'm having the exact same issue on my N7105. It was working fine for days after flashing, then all of a sudden it rebooted and all user apps were gone. When I tried to reinstall from TB, I got an error on each app that it had stopped working.
I tried to reflash the ROM with full wipe, but CWM restarts when it tries to wipe /data.
I'm using this ROM http://forum.xda-developers.com/showthread.php?t=1985200 with Note2Core v2.10.
there is probably an issue with the internal sd card(hardware part).
or maybe you have done something wrong.
try using adb to format it.
I was finally able to format the /data folder by doing a factory reset, now it works in CWM and flashing a ROM doesn't fail when choosing the full wipe installation.
I'm not sure what the problem was. A faulty internal SD card would still be having this problem and incorrect flash method would show problems straight away, not 5 days later, right?
Hi guys,
I have the same issue, anything related to the partition /data is causing me troubles since I first tried to wipe it when I wanted to install CM9.1. (and I had stock ICS 4.0.4 at the time...)
Do you think it is the mmc bug ?
I can enter DL mode but when I try to flash stock rom, it just remains at the animated boot logo for hours...
Tried also to flash rom (with CODE, MODEM, CSC) and Odin stays stuck when starting DATA...
Any luck on your side ?
Wtf this is n7100 thread and forum. How can you get 4.0.x on it
Sent From Samsung's Galaxy Note II Using Internet
i think u guys just hardbricked ur n7100..maybe try to go samsung centre..can try ask for warranty
Related
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Did you wipe data and cache when you flashed the new rom?
nyyankees1237 said:
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Click to expand...
Click to collapse
a few questions:
and i can verify the issue is something on your end, because the ROM you tried was mine, and nobody has had that issue (not booting it)
do this...
1. make sure you have the latest version of clockwordmod, don't use twrp
2. re-download my ROM (just for sake of not adding any other variables to your issue, because mine should boot)
3. put ROM on external SD card
before continuing... take a quick look at my thread here in QA titled "flashing ROMs correctly every time" .... so you can get some instruction on verifying MD5 of the download... don't worry, the thread will explain that you...
now proceed
4. boot to recovery
5. do a factory reset - 3 times do this, just to be thorough. people will say you don't need to, but like i said, just for the sake of removing variables
6. go to mounts and storage, format system 3 times - (yes, through recovery as well)
7. flash ROM, and reboot
EDIT*** i will say this, ALWAYS format system when flashing a new ROM
cobraboy85 said:
a few questions:
and i can verify the issue is something on your end, because the ROM you tried was mine, and nobody has had that issue (not booting it)
do this...
1. make sure you have the latest version of clockwordmod, don't use twrp
2. re-download my ROM (just for sake of not adding any other variables to your issue, because mine should boot)
3. put ROM on external SD card
before continuing... take a quick look at my thread here in QA titled "flashing ROMs correctly every time" .... so you can get some instruction on verifying MD5 of the download... don't worry, the thread will explain that you...
now proceed
4. boot to recovery
5. do a factory reset - 3 times do this, just to be thorough. people will say you don't need to, but like i said, just for the sake of removing variables
6. go to mounts and storage, format system 3 times - (yes, through recovery as well)
7. flash ROM, and reboot
EDIT*** i will say this, ALWAYS format system when flashing a new ROM
Click to expand...
Click to collapse
thanks for the info, will try this all out soon. I've been flashing roms for years now and have never run into anything like this, and as previously stated, this didn't occur solely with your rom which has me thinking something has happened to the phone itself. will get back to you soon and once again thank you
chucktdriscoll said:
Did you wipe data and cache when you flashed the new rom?
Click to expand...
Click to collapse
of course, wiped data, cache, & delvik
nyyankees1237 said:
of course, wiped data, cache, & delvik
Click to expand...
Click to collapse
my point is...
coming from a cm based ROM, or aokp, whatever you said... you would want to format system as well.
nyyankees1237 said:
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Click to expand...
Click to collapse
I was having some of the same issues. I downloaded XquiziT's Superwipe and ran it by installing from external sd card. I ran it three times to clear everything out, then I wiped data, cache and the rest three times.
No probs for me after that.
Will definitely give that a try as well! Thank you! Will post my results when the holiday is over.
Happy thanksgiving
Sent from my SGH-T999 using xda app-developers app
Hey guys hopefully you can help me. I was rooted for like 3 or 4 months now and have had not many problems or not anything I couldn't fix my self. My phone gets stuck on the Samsung Galaxy s4 screen anytime I reboot. I have tried different roms, different kernels, I even odin back to stock. I was using TWRP 6.0 then reverted back to TWRP 5.2 to see if that was causing the problem. Still have problems. I am going to re download the stock tar to see if it was a bad download but Odin checks the md5 and says it was good. Odin says passed every time also. Odin version is 3.07.
I get a error before and when trying to wipe dalvic cashe. I can wipe reg cash no problem. I think my phone is not mounting the internal storage when it reboots. I could be way off but need help asap. If I format super wipe with twrp then restart twrp and then factory reset I can install or restore a rom some times but still cant restart the phone. Any hope would be greatly appreciated.
EDIT
I wanted to edit my previous commet. LiquidSmooth seems to be running fine. So TW roms and GE roms **** up on my phone when I restart. so is it the internal systems when I have TW roms. I think it has something to do with partictions messing around maybe.
I like TW roms and want to continue to use them... Thank you
Get into recovery and do a factory reset, it is a must after you odin back to stock. Make sure you are also using a tmo kernel.
Thanks you
I got this problem a few days ago and found some topic including this one. You should check it out.
Well, what worked for me was Odin to stock firmware, root again, install recovery then custom rom. Now it's working fine. Try to downloading it again to see if it works. I downloaded mine from here, rooted and recovery it using this one.
TheAxman said:
Get into recovery and do a factory reset, it is a must after you odin back to stock. Make sure you are also using a tmo kernel.
Thanks you
Click to expand...
Click to collapse
+1 to what he said. I bet if you go into the stock recovery after odin flashing it will say something like cannot mount /data partition. Factory reset there, and it should fix that and make it mountable. (Its important to use the stock recovery factory reset after the odin, don't flash a custom recovery right after flashing)
This was incredibly helpful. I had the same issue. Thank you.
This is also applicable to the Verizon Wireless model.
First Yes i have searched and i found several posts but none had enough information or ended up with directing the op to the de-brick thread I feel its not bricked and I don't want to run into more problems.
Here is how it goes down
using 4.2.1 Rom
using CWRM 6.0.3.1
I tried to encrypt my phone (don't ask me why as if i could go back in time i wouldn't have tried it)
So first it would only boot to the screen that says encryption failed factory reset and try to encrypt again and has a restart button at first nothing worked even the Rom UI would crash at this point and the restart (software button) on the screen was unresponsive. I then went into recovery and tried to load a recovery and it could not mount /data as it read as it was secured. So i went and formatted it and was successful with restoring a backup Although as soon as it booted again it brought me right to that same screen?
I am going to try to start over with a new Rom installation while i wait for a reply.
I just hope i can get it done simply without Odin or connecting it to my PC as i tend to not have good luck with that. IDK whats up with my PC.
Anyway if a simple Rom install fixes it ill be happy but something is still there saying i want to encrypt it or IDK what is causing it to go to the encryption failed page when I have formatted all but /sdcard (i was afraid to unless I'm told) I know everything else is fine /system /data /cache are all replaced by the Rom so i know its OK to format them but /sdcard is all the data on the phone so I'm not afraid of losing music ringtones pictures etc if i do need to format /sdcard but i want to be told i should first
also please ask me for any in formation you may need i want to fix this and also i need to go find a Rom so also a Rom suggestion is fine too (if its going to help otherwise I'm going to find a basic 4.2.1 Touchwiz based Rom and flash that
Please Flash UVDMD5 version of Root66 via Odin.
Perseus71 said:
Please Flash UVDMD5 version of Root66 via Odin.
Click to expand...
Click to collapse
THANKS I tried flashing a fresh ROM after formatting everything now im in a boot loop and as it not bricked (soft bricked anyway) i was hoping a new route66 via Odin would be my main option.
Now as far as it goes on updating to 4.3 what file should i flash via Odin? should i use T999_UVDMD5 to get it working again then use T999_UVUEMJC to update to 4.3 (how i went from ICS to JB so would it be the same to KK ,4.3,) or can i just do a single Odin to T99_UVUEMJC so I u can be ready to use 4.3 roms. I just want to make sure because if I don't' have to use a 4.13 route 66 ROM to com back from this boot loop can I skip the step of using Odin to UN soft brick my 4.1.2 and go straight to 4.3.
I just want to know the best way to go about eventually being able to load 4.3 roms on this phone more because they are easier to find (as in more developed at this time) and to be update
I appreciate all your help and in case any ROM devs are reading this I love your work each and every one of you make this place better i wish i had the (first smarts) and second the time to mod for myself but over the years you guys are just awesome and i wish i was at any of your levels (all who post or even mod for themselves) as if i knew what you did i would not be in the predicament either and if i can fix it i will be pleased with myself as i bet most or all devs could fix this issue in 5-10 min where you can see Ive been at it days! Thanks in advance for any future help and most of all so far thank to you Perseus71 for helping me start
Never EVER flash UVUEMJC. Let's first get you back working with UVDMD5. Once that's achieved, I will get you 4.3 by another way.
For now, If you are right now on that bootloop/softbrick with just the UVDMD5, then great. If not go back to recovery, factory reset and wipe the cache and Re-flash UVDMD5 via Odin. This time, in Odin, make sure to uncheck Auto Reboot.
Once Odin has succeeded, Flash a custom Recovery such as TWRP via Odin. After that is done, reboot to recovery. Wipe Dalvik and Cache and then reboot normal.
[Q] Encryption Unsuccessful (Android 4.1)
I have partitioned my phone incorrectly. Phone is asking for a reset..
I deleted the /data and /sdcard because I formatted the internal storage and every time I reboot, I get a Encryption Unsuccessful message and it tells me to reset phone. I did but same message. What should I do??
Here's my phone: Cherry Mobile Omega HD (IQ6A) / Xolo A1000 / Alps H100
Android JB, Custom ROM, Rooted, TWRP
5"
8Gb External
Wrong Device forum Bud.
Hi, I have been trying to flash a new ROM to my Note II.
It was on Official Stock 4.3 ROM and I flashed succesfully another 4.3 ROM based on stock with some Note 3 features using Philipz Touch.
Then I switch Philipz to TWRP in order to install DN3 V4 ROM and I made the wipes and format /data and I start flashing the ROM, and since that moment It stucks on the first screen.
When I try to flash a stock 4.3 ROM using Odin, It seems to flash correctly, but when I try to boot, it stucks again.
I can enter to recovery and download mode, I can install some ROMS using TWRP but when it finishes it shows "Unable to mount /data" and if I try to boot, It always stucks on fisrt screen.
I hope you can help me.
Do it again: format cache; davik; systems; data and install rom again. If not, flash cwm recovery via odin.
Good luck.
Sent from my Assistant
Still the same
biokiller said:
Do it again: format cache; davik; systems; data and install rom again. If not, flash cwm recovery via odin.
Good luck.
Sent from my Assistant
Click to expand...
Click to collapse
I really appreciate your help, but I can't fix the problem yet.
With CWM I can't make a factory reset, when I try to make it, it restarts the phone and it stuks on the first screen.
I have flashed stock ROMS with odin and it says PASS but when the phone boots It always stucks on the first screen.
Fear not.
I am fairly confident this will work, but read the whole post first
You tick erase all nand as well as the usual two options. Then boot into recovery (should give warnings about unmountable /data) and wipe data / factory reset. Then reboot and it should work / odin a stock rom as normal.
If that doesnt work / or instead you get the correct pit file and flash it as well as the rom and have four options ticked: pit, erase all nand + normal two.
If someone gave me their phone with the same symptoms as yours and said: fix it right now that's what I'd do. I'd also warn them I really need to do more research before doing this and using these two options in odin could brick the phone forever.
I hope this gives you lines of inquiry. I found many mixed messages with the erase nand option, most said nothing of merit except don't do it, some said you must wipe data first (which u can't), some said exactly what I've repeated, some say a pit is enough, others had many steps and files ive never heard of to solve the same issue. There is a large thread in the S3 forum about this, even got mentioned on xda proper. My brief cookie crumbs journey did not return any note 2 threads.
Remember one thing, before using odin, double check every detail. Battery, cable being used, files being used (right ones, md5s), right options ticked, computer is in good health, internet is off, Kies is not running. (I'm sure ive missed some)
Solved
I install again the stock kit Kat firmware and the problem was the same, but this time I boot stock recovery and there I made factory reset and that's it. Problem solved and Note boot normally.
Thanks for your help
With or without erase nand in odin?
No, I just flashed normally as all the stock firmwares
I see, thought you'd rule that out. Disappointing really. Glad ur sorted anyway. Remeber wiping data is important when changing roms, even if it's not always absolutely necessary.
Did you try TWRP or Philztouch ? Did you flash 4.3 stock rom?
Sent from my GT-N7100 using Tapatalk
I woke up the other day with my phone stuck at the Galaxy Note II bootup screen.
Great!
So I've been trying for days to solve this issue that's driving me insane.
I'm running TWRP 2.8.0.0
It starts and can't mount any of the partitions. Attempting to mount internal storage or SD card is impossible, it says it has 0 bytes.
Obviously something corrupted something. But now I can't get anything working.
I can't format from withing TWRP, it fails.
Tried using KIES emergency firmware update, but its supposed to show a list of devices that need emergency update, it never shows up.
I was able to flash a stock rom with Odin. Except for that it doesn't repartition the device's internal storage and it never is able to boot into the new ROM. If I check TWRP after installing with Odin, it shows that all the devices are still unmountable.
So I flashed the new TWRP 2.8.6.0 with Odin. Except when I boot back into Odin it shows 2.8.0.0 still.
Anyone have any ideas? I've been phoneless for a week now!
changoland said:
I woke up the other day with my phone stuck at the Galaxy Note II bootup screen.
Great!
So I've been trying for days to solve this issue that's driving me insane.
I'm running TWRP 2.8.0.0
It starts and can't mount any of the partitions. Attempting to mount internal storage or SD card is impossible, it says it has 0 bytes.
Obviously something corrupted something. But now I can't get anything working.
I can't format from withing TWRP, it fails.
Tried using KIES emergency firmware update, but its supposed to show a list of devices that need emergency update, it never shows up.
I was able to flash a stock rom with Odin. Except for that it doesn't repartition the device's internal storage and it never is able to boot into the new ROM. If I check TWRP after installing with Odin, it shows that all the devices are still unmountable.
So I flashed the new TWRP 2.8.6.0 with Odin. Except when I boot back into Odin it shows 2.8.0.0 still.
Anyone have any ideas? I've been phoneless for a week now!
Click to expand...
Click to collapse
Have you tried flashing a pit file along with the stock firmware in Odin? That's what I would do in your case. It'll repartition the phone and flash the firmware. Fresh as the day you bought it.
absinthesummer said:
Have you tried flashing a pit file along with the stock firmware in Odin? That's what I would do in your case. It'll repartition the phone and flash the firmware. Fresh as the day you bought it.
Click to expand...
Click to collapse
On your advice I just flashed i317.pit with Stock ROM. Succeeded in flashing in ODIN as well as looking like it rewrote the partitions. However, upon reboot to TWRP, all partitions are still unmountable. Tried flashing pit along with TWRP 2.8.6.0. It remained on 2.8.0.0 when I rebooted into TWRP. Again experienced the same issue and could not mount any partitions. Tried flashing PIT alone and then booting into TWRP. Same.
I've attached a picture too. This inability to mount also prevents me from formatting, factory resetting, loading from external microsd, so on and so forth...
http://i.imgur.com/J5ppODI.jpg
Man I really thought the pit would work! Just 2 days ago I had the unable to mount data error and flashing stock with the pit file worked for me
A few questions-
1. I wonder if that old old old issue of eMMc brick bug is present in your device. The symptoms are very similar from what I remember of it but I do highly doubt that's what's happening.
2. Do you have more info about your device prior to this breakdown? Ie what rom + kernel were you on? were there any hints of anything failing? did you flash anything and if so what was it?
I'm hoping the information might help point us in the right direction. I'll look into something a well, but I'm also hoping that someone else with more experience with this problem will come help. @sawdoctor didn't this happen to your note 2 once also? When mine refused to mount data the other day it wasn't quite as bad as this, so it was an easy fix. Hopefully we can get you sorted.
absinthesummer said:
Man I really thought the pit would work! Just 2 days ago I had the unable to mount data error and flashing stock with the pit file worked for me
A few questions-
1. I wonder if that old old old issue of eMMc brick bug is present in your device. The symptoms are very similar from what I remember of it but I do highly doubt that's what's happening.
2. Do you have more info about your device prior to this breakdown? Ie what rom + kernel were you on? were there any hints of anything failing? did you flash anything and if so what was it?
I'm hoping the information might help point us in the right direction. I'll look into something a well, but I'm also hoping that someone else with more experience with this problem will come help. @sawdoctor didn't this happen to your note 2 once also? When mine refused to mount data the other day it wasn't quite as bad as this, so it was an easy fix. Hopefully we can get you sorted.
Click to expand...
Click to collapse
I had a similar issue when porting a s3lte 4.4.4 base to the n2 I couldn't mount data even odin didn't fix it but I was able to format internal with recovery. A full wipe of everything fixed it. I'd try mskips toolkit, it has an emergency firmware rescue package that you can flash see if it helps. It maybe your internal sd has actually died which I've heard off before
Sent from my SM-N910F using Tapatalk
sawdoctor said:
I had a similar issue when porting a s3lte 4.4.4 base to the n2 I couldn't mount data even odin didn't fix it but I was able to format internal with recovery. A full wipe of everything fixed it. I'd try mskips toolkit, it has an emergency firmware rescue package that you can flash see if it helps. It maybe your internal sd has actually died which I've heard off before
Sent from my SM-N910F using Tapatalk
Click to expand...
Click to collapse
Thanks for chiming in! Hopefully that'll help him. Yeah memory failure us what I was thinking not brick bug (couldn't think of the right word, thanks)