Database Develop

[Q] Flashing always stops at data.img/datafs

I made a wipe data/factory reset while on CWM Touch (I didn't know about the issues yet) and, of course, it didn't work. So now, everytime I try and flash an Odin ROM (because it doesn't work with the recovery), it gets stuck at data.img/datafs so there's no way I can boot my phone although it does have recovery, download and it gets to the Samsung bootscreen (I flashed a stock ROM).
Has anyone got any ideas on how to fix this? Thanks

Tried clearing cache and data while on recovery? Which rom/kernel are you on?
Sent from my GT-N7000 using XDA

praetorius said:
Tried clearing cache and data while on recovery? Which rom/kernel are you on?
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
I was on AOSP ICS v04 with the infamous AbyssNote 1.2 kernel (but I don't have the same factoryfs problem as the others) with Touch CWM (that's where the problem comes from I believe) and the only problem is that neither Odin nor CWM can access the /data partition. So a wipe doesn't work.

I fear the nearest Samsung service is the way to go for you, mate. Your data partition is corrupted beyond repair.
Believe me, the guys affected with Angelom 1.2 had tried everything, including jigging, jtagging and nothing helped unbrick their phones. It looks like replacing the motherboard is the only solution.
Sorry to have to tell you this.

chasmodo said:
I fear the nearest Samsung service is the way to go for you, mate. Your data partition is corrupted beyond repair.
Believe me, the guys affected with Angelom 1.2 had tried everything, including jigging, jtagging and nothing helped unbrick their phones. It looks like replacing the motherboard is the only solution.
Sorry to have to tell you this.
Click to expand...
Click to collapse
Are you sure? Even though it's never stuck at factoryfs and it only bootloops? Because the problem is I have no service center I can go to so sending it via La Poste (in France) isn't exactly what I'd call safe... Or is there a way to send iut directly to Samsung and get a new one?

Up.............

Since it looks like a partition problem - have you tried using stock .pit file and repartition with ODIN ?

Akiainavas said:
Since it looks like a partition problem - have you tried using stock .pit file and repartition with ODIN ?
Click to expand...
Click to collapse
Yes I did. Well I think imma have to send it to a samsung repair center. How long does it take to get a new Note?

Hi, I had a similar problem and here's what I did. I flashed a stock rom (doesn't have datafs so it worked fine) then it rebooted into recovery which complained about /data partition. So I did wipe data and rebooted.
Hope this helps.

nico53laval said:
Yes I did. Well I think imma have to send it to a samsung repair center. How long does it take to get a new Note?
Click to expand...
Click to collapse
According to warranty agreement:
"Repairs are done as fast as possible, but within 14 days time."

no id agree with what the guys have told you, looks like a service center job, did you just flash this recently or were you one of the users who flashed it weeks back, and youve only just attempted a wipe now??
Just out of curiosity, if people have this kernel installed, can they flash to a diff kernel b4 trying a wipe, or will that not work.

graemeg said:
Just out of curiosity, if people have this kernel installed, can they flash to a diff kernel b4 trying a wipe, or will that not work.
Click to expand...
Click to collapse
You're fine if you don't do any wipes prior to flashing another kernel. However, wipe anything and it's curtains.

chasmodo said:
You're fine if you don't do any wipes prior to flashing another kernel. However, wipe anything and it's curtains.
Click to expand...
Click to collapse
Exactly :/ I was fine for weeks then I wiped before installign another ROM and boom...

dirk271 said:
Hi, I had a similar problem and here's what I did. I flashed a stock rom (doesn't have datafs so it worked fine) then it rebooted into recovery which complained about /data partition. So I did wipe data and rebooted.
Hope this helps.
Click to expand...
Click to collapse
Too late ^^ I sent it to a repair center.. But I don't think it would have worked. I already did a wipe on a tock rom with stock recovery and it worked but the phone still couldn't boot.

Akiainavas said:
According to warranty agreement:
"Repairs are done as fast as possible, but within 14 days time."
Click to expand...
Click to collapse
The problem is that in France the repair centers have an agreement with Samsung but they're not directly related to Samsung so do you think it'll only be 14 days (even though I might neeed a new mobo or a new phone)?

Not sure how youre postal system works there but make sure you get recorded delivery or france similar so you have proof of posting etc.
Also considering the issue ive read most times lads have had a quick turn around, but who knows, depends how fast samsung receive it, i would suggest UP TO 2 weeks, more likely a week, but then it me be 2 week, depends what they have to do to repair it.
I recently took a phone to the o2 shop to be repaired, i received it back via post 4 days later, that was really fast, and im quite lucky here that theres an abundance of walk in repair centres around the uk, it just made me wonder if there one close to you and would it be economical to take it in person, samsung repair shop where i live if ya take your phone in by hand theyll usually say come back in a couple of hours and then they fix it there and then, that would be better for you because you arent messing around with posting then, i know a lot of countries guys dont have that option but i would have thought france and germany would be similar to the uk as they are both quite large mobile manufacturing countries so my fingers are crossed for you that you can find a quick solution.

No idea mate, but you shouldn't wait more than 2 weeks. The repair will take one hour probably, the rest is testing, posting, filling papers etc.
You'll probably have it back after 1 week or so. So let's hope you'll received it fixed as soon as possible.

nico53laval said:
Exactly :/ I was fine for weeks then I wiped before installign another ROM and boom...
Click to expand...
Click to collapse
Oh, I see. Should've read angelom 1.2 thread first.... sorry
Good luck with service.

dirk271 said:
Hi, I had a similar problem and here's what I did. I flashed a stock rom (doesn't have datafs so it worked fine) then it rebooted into recovery which complained about /data partition. So I did wipe data and rebooted.
Hope this helps.
Click to expand...
Click to collapse
what stock rom? which version you used?

Lost storage space on phone 64gb

My 64GB Nexus is now saying it has 23gb of total storage and 21gb available. I had to reflash the stock ROM after a failed twrp flash. Is there anyway to fix this? I have already tried reflashing and wiping the phone 2 times but the storage decreases each time.

Use a factory image and start over.

ericsignals said:
Use a factory image and start over.
Click to expand...
Click to collapse
I've already done that twice

Pilz said:
I've already done that twice
Click to expand...
Click to collapse
Double check and make sure you have the latest SDK and/or just download the latest regardless. N5 folks have been having similar issues since the Lollipop release.

jhax01 said:
Double check and make sure you have the latest SDK and/or just download the latest regardless. N5 folks have been having similar issues since the Lollipop release.
Click to expand...
Click to collapse
I can try to redownload the SDK, but my question is what does the SDK have to do with losing space on my phone?

I don't pretend to know what the cause is behind it but when the 5.0 factory images were released, people who flashed it with an older version of fastboot were losing storage on the Nexus 5.
Sent from my Nexus 5 using Tapatalk

I fixed it after doing a factory reset then flashing it again. I double checked and I already had the latest SDK. Its really weird how it took flashing 3 times to work.

Pilz said:
I fixed it after doing a factory reset then flashing it again. I double checked and I already had the latest SDK. Its really weird how it took flashing 3 times to work.
Click to expand...
Click to collapse
I am in the same boat. Even did a factory reset and flashed the factory image but still stuck with 23GB on my 64GB. What exactly did you do to fix this?

the.emilio said:
I am in the same boat. Even did a factory reset and flashed the factory image but still stuck with 23GB on my 64GB. What exactly did you do to fix this?
Click to expand...
Click to collapse
I re-downloaded the latest SDK and then reflashed the images again. It took a few times before it reset. I also used fastboot erase system if I remember correctly.

Pilz said:
I re-downloaded the latest SDK and then reflashed the images again. It took a few times before it reset. I also used fastboot erase system if I remember correctly.
Click to expand...
Click to collapse
Did you flash each image individually since the flash all gives that no system.img error? Just want to make sure I can duplicate what you did.

the.emilio said:
Did you flash each image individually since the flash all gives that no system.img error? Just want to make sure I can duplicate what you did.
Click to expand...
Click to collapse
I flashed each one manually. The bat file doesn't work so that's the only way to do it. I don't remember the order I flashed everything in, but I remember that I used fastboot to wipe the phone before flashing. I kept trying different things until it showed the right storage then I decrypted it and flashed TWRP and used CF auto root. One of my mistakes was rooting before checking because it was a waste of time if I had to flash it again.
I may have done a factory reset st one point but I don't remember because it was late and I was watching TV with my wife whole doing this.

Pilz said:
I flashed each one manually. The bat file doesn't work so that's the only way to do it. I don't remember the order I flashed everything in, but I remember that I used fastboot to wipe the phone before flashing. I kept trying different things until it showed the right storage then I decrypted it and flashed TWRP and used CF auto root. One of my mistakes was rooting before checking because it was a waste of time if I had to flash it again.
I may have done a factory reset st one point but I don't remember because it was late and I was watching TV with my wife whole doing this.
Click to expand...
Click to collapse
Figured. I will keep trying. Thanks!
---------- Post added at 11:56 PM ---------- Previous post was at 11:08 PM ----------
After about 10 attempts it turns out all i had to do was fastboot format cache then fastboot format userdata. Reboot and boom restored to normal. LMAO! Wasted 4 hours tonight just for that. Live and learn!

Just do a factory reset in recovery WITHOUT reflashing and the problem is taken care of.
Seems a like a bug in the factory images that can cause of wrong partition sizes.
Worked on my N9 (which I already sent back to Google due to excessive lightbleed lol)

I had the same issue after trying to root the phone showed 23 GB.
I was able to get back to 53 GB after wipine cache and formatting user data, but that still seems like I'm missing something . I did not check how much storage was available before I started.
Can any one tell me what the storage numbers should be on like on a stock device with nothing installed please?

I remember hearing about this same issue with the Nexus 5. Don't recall the cause though. Sorry folks I know this post is useless I'm just excited to be getting my Nexus 6 so I perusing the forums.

[Q] Stuck in Bootloop after fixing permissions in TWRP

Hey All,
Finally got my nexus 6 and I'm pumped to have a developer phone again. Haven't done anything since I got rid of my galaxy nexus a year or so ago, so I'm a bit rusty. Sorry if this has been posted before, I searched but couldn't find anything related to this. Long story short, I had my phone unlocked and rooted and have TWRP installed fine. I just went in and cleared the cache, dalvik cache, and fixed permissions... and now I'm stuck in a bootloop. After researching I'm pretty sure it was the fixed permissions that messed it up, I didn't know that it didn't work on lollipop at the time. I've come to the conclusion I need to reflash the stock images and start from scratch. The only problem is I'm currently stuck at work for another 4 hours and can't use adb at all on this computer. So I'm wondering if anyone knew of another way to fix from just the phone. Thanks in advanced guys!

rev89 said:
Hey All,
Finally got my nexus 6 and I'm pumped to have a developer phone again. Haven't done anything since I got rid of my galaxy nexus a year or so ago, so I'm a bit rusty. Sorry if this has been posted before, I searched but couldn't find anything related to this. Long story short, I had my phone unlocked and rooted and have TWRP installed fine. I just went in and cleared the cache, dalvik cache, and fixed permissions... and now I'm stuck in a bootloop. After researching I'm pretty sure it was the fixed permissions that messed it up, I didn't know that it didn't work on lollipop at the time. I've come to the conclusion I need to reflash the stock images and start from scratch. The only problem is I'm currently stuck at work for another 4 hours and can't use adb at all on this computer. So I'm wondering if anyone knew of another way to fix from just the phone. Thanks in advanced guys!
Click to expand...
Click to collapse
you can try flashing any rom, since you have twrp installed, or you can try wiping data(factory reset).

simms22 said:
you can try flashing any rom, since you have twrp installed, or you can try wiping data(factory reset).
Click to expand...
Click to collapse
Unfortunately, I do not have any ROMs saved on my phone yet. I just got it last night with only maybe an hour or two of playing time. I also tried factory reset through TWRP and am still experiencing the bootloop. Would formatting data help? I feel like it would, but like I said, I'm rusty.

rev89 said:
Unfortunately, I do not have any ROMs saved on my phone yet. I just got it last night with only maybe an hour or two of playing time. I also tried factory reset through TWRP and am still experiencing the bootloop. Would formatting data help? I feel like it would, but like I said, I'm rusty.
Click to expand...
Click to collapse
you can try, i dont think itll help. all you got to do is download any rom/gapps/supersu to your phone then flash it. i use rastapop.

simms22 said:
you can try, i dont think itll help. all you got to do is download any rom/gapps/supersu to your phone then flash it. i use rastapop.
Click to expand...
Click to collapse
I know, but I can't boot my phone to download it. Hence, why I'm going to have to flash the stock images when I get home. How is rastapop? I need to find something since the big names aren't out yet. I'll try it out later once everything is fixed. I'm mad I ran into this boot loop because custom rom was next on my list of things to do haha

rev89 said:
I know, but I can't boot my phone to download it. Hence, why I'm going to have to flash the stock images when I get home. How is rastapop? I need to find something since the big names aren't out yet. I'll try it out later once everything is fixed. I'm mad I ran into this boot loop because custom rom was next on my list of things to do haha
Click to expand...
Click to collapse
you didnt happen to make a backup in recovery, did you? if you did, just restore it.

simms22 said:
you didnt happen to make a backup in recovery, did you? if you did, just restore it.
Click to expand...
Click to collapse
Nope, would have made life a lot easier if I did. I was just kicking myself in the ass for that earlier.

Edit: nvm, forgot you don't have adb access
Sent from my Nexus 6 using XDA Free mobile app

Thanks for the help guys. I'm just gonna start from scratch when I get home... god I hate not having a phone.

Yah I realized fixing permissions messes it up. And also if u wipe internal storage the phone looses the system ui and the back home menu buttons as well

well thats good to know. Will it still do that if I'm not encrypted?

rev89 said:
Unfortunately, I do not have any ROMs saved on my phone yet. I just got it last night with only maybe an hour or two of playing time. I also tried factory reset through TWRP and am still experiencing the bootloop. Would formatting data help? I feel like it would, but like I said, I'm rusty.
Click to expand...
Click to collapse
Probably too late to do, but USB-OTG cable and a jump drive. I have downloaded stuff on work PC, copied to jump drive and flashed it on phone with TWRP from the jump drive.

I can personally confirm the permission fix in TWRP recovery breaks the stock L5.0.0 and 5.0.1 and I assume probably most ROMs? There seems to be several threads about this.

githyanki said:
Probably too late to do, but USB-OTG cable and a jump drive. I have downloaded stuff on work PC, copied to jump drive and flashed it on phone with TWRP from the jump drive.
Click to expand...
Click to collapse
you can flash from a jump drive? I didn't know that

Need to send my Nexus in

I just got my Nexus 6 about a week ago, (on verizon), and I got the right screen freeze issue. Which by the way, I got only when I was using chroma. I haven't gotten it yet on stock. But I already started the return process with verizon.
Now, I want to make sure I get everything stock before I send it in, so I was wondering a few things. I have Android 5.1, and I know the issue with it bootlooping, so what exact steps should I take between these 2 guides? I think during STEP 5 of the first guide, I install the factory image which is detailed in the 2nd guide correct?
http://forum.xda-developers.com/nexus-6/general/guide-safely-lock-bootloader-android-5-1-t3067302
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Also, if I make a nandroid backup using twm from my original phone, can I restore it on my other phone? Will I have any issues with that?
Thanks a lot guys.

codersanchez said:
I just got my Nexus 6 about a week ago, (on verizon), and I got the right screen freeze issue. Which by the way, I got only when I was using chroma. I haven't gotten it yet on stock. But I already started the return process with verizon.
Now, I want to make sure I get everything stock before I send it in, so I was wondering a few things. I have Android 5.1, and I know the issue with it bootlooping, so what exact steps should I take between these 2 guides? I think during STEP 5 of the first guide, I install the factory image which is detailed in the 2nd guide correct?
http://forum.xda-developers.com/nexus-6/general/guide-safely-lock-bootloader-android-5-1-t3067302
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Also, if I make a nandroid backup using twm from my original phone, can I restore it on my other phone? Will I have any issues with that?
Thanks a lot guys.
Click to expand...
Click to collapse
Yes, sounds like you've got it straight. Also, yes you can restore to your new device but don't restore the EFS backup or you'll be borked.

Evolution_Freak said:
Yes, sounds like you've got it straight. Also, yes you can restore to your new device but don't restore the EFS backup or you'll be borked.
Click to expand...
Click to collapse
Alright, thanks a lot man.

codersanchez said:
Alright, thanks a lot man.
Click to expand...
Click to collapse
No problem at all. If you get stuck, just ask for help. Good luck!

Evolution_Freak said:
No problem at all. If you get stuck, just ask for help. Good luck!
Click to expand...
Click to collapse
I got everything done
I couldn't use flash-all because for some reason it didn't flash my recovery, so I had to manually flash basically everything. Other than that it was pretty easy.

[Q] Nexus 6 screen won't work! Please help with RMA questions.

So I recently got my Nexus 6 before I left the U.S. After about 3 days of use after I got it, right in front of me the screen just died, and now doesn't work at all. I managed to unroot the phone using a tutorial at androidrootz.
Now I am done with most of the process, but can't factory reset. Do I need to factory reset if I have already flashed the stock images? And if I do, how can I with a broken screen? Help would be really appreciated.

Darthicus said:
So I recently got my Nexus 6 before I left the U.S. After about 3 days of use after I got it, right in front of me the screen just died, and now doesn't work at all. I managed to unroot the phone using a tutorial at androidrootz.
Now I am done with most of the process, but can't factory reset. Do I need to factory reset if I have already flashed the stock images? And if I do, how can I with a broken screen? Help would be really appreciated.
Click to expand...
Click to collapse
No reset needed if you flashed the whole factory image. You're good to go.

Evolution_Tech said:
No reset needed if you flashed the whole factory image. You're good to go.
Click to expand...
Click to collapse
Thanks for the help. Once I get back I'll start my RMA process.