Database Info

Nexus S storage corrupt

Hi, I'm having a lot of issue with my Nexus S so I want to reflash with full 2.3.3 image... The thing is when I mount the phone and copy the file, after I reboot the Nexus S to go in recovery... The update.zip is not there. I tried to create a folder and put some files on it... When I unmount the phone and remount it ... everything is gone except "LOST.DIR | .android_secure | Android | DCIM. The rest is gone .... Looks like the phone memory is corrupt ...
Looks like everytime the phone use the memory everything begins to crash (force close of all application) and even the phone just freeze and I need to remove the battery.
Is there any way I can save my phone? Probably a bad flash or something cause this issue (I flashed to gingerbread 2.3.3 from the file found on this forum)
If anyone is able to help.... it will be appreciate.
Thanks.

Here's something to add:
Looks like the whole storage is read-only (at some point) I'm changing some settings and after a reboot it's not kept ... backgroung is default, google account is not configured .... Even tried to factory-default again and it gives me a unable to format /system or /data I don't remember the whole line ... I was kinda stuck in the custom recovery where you can flash from /sdcard/update.zip ... I look at the mount with "adb shell" and it looks OK.
I can provide adb logcat if needed ... But any help will be appreciate ...
Thanks!

Put the phone in download mode then reflash using Odin after it boots go into settings and wipe your SD and then do a hard reset. That should fix any problems.
Sent from my Nexus S

if you have CW recovery installed, you can use it to fix the permissions issues

Hi,
I tried the odin flash and no good... now I installed the CW recovery and tried the fix permissions... looks like it's hang... is this procedure long?? I'll leave the phone like this...
Tried to wipe to factory default and reflash... same issue has before, update.zip is not staying on the usb storage... Is there another way to fix this issue...
Thanks for your help, appreciate!
Sent from my Nexus One

Ok, fix permissions done, still not working... tried to factory default... No good.... Any ideas?
Sent from my Nexus One

SpOuK-3- said:
Here's something to add:
Looks like the whole storage is read-only (at some point) I'm changing some settings and after a reboot it's not kept ... backgroung is default, google account is not configured .... Even tried to factory-default again and it gives me a unable to format /system or /data I don't remember the whole line ... I was kinda stuck in the custom recovery where you can flash from /sdcard/update.zip ... I look at the mount with "adb shell" and it looks OK.
I can provide adb logcat if needed ... But any help will be appreciate ...
Thanks!
Click to expand...
Click to collapse
I have the exact same issue... were you able to fix it?

in the worse case scenario, in CWR advanced menu you can format the internal SD card

I'm very interested to hear how you get on with this, sounds like the infamous freezing problem that the Nexus S seems to suffer from.
Please let us know how you get on and if the suggestion above to format the internal SD with cwm works.

xspyda said:
I'm very interested to hear how you get on with this, sounds like the infamous freezing problem that the Nexus S seems to suffer from.
Please let us know how you get on and if the suggestion above to format the internal SD with cwm works.
Click to expand...
Click to collapse
Tried it... it doesn't work ... SpOuK-3- said he sent his phone to samsung

legojj said:
Tried it... it doesn't work ... SpOuK-3- said he sent his phone to samsung
Click to expand...
Click to collapse
Bugger! I was hoping there would be another way. Out of interest, had either of you recently performed an update either ota or manual?

try fastboot oem lock and then fastboot oem unlock.
unlocking the bootloader will wipe and format ur sd card

deeren said:
try fastboot oem lock and then fastboot oem unlock.
unlocking the bootloader will wipe and format ur sd card
Click to expand...
Click to collapse
Yea i have tried that, no success.
And yes I did a nightly update (build 39)

legojj - as above had you recently performed an update when you ran into this problem?

xspyda said:
legojj - as above had you recently performed an update when you ran into this problem?
Click to expand...
Click to collapse
Yes, i went from cyanogens nightly build 38 to nightly build 39.

legojj said:
Yes, i went from cyanogens nightly build 38 to nightly build 39.
Click to expand...
Click to collapse
I figured that would be the case (though not necessarily cyanogenmod related). This seems to be the common factor with all Nexus S phones suffering from the freezing issue - the problem always starts pretty soon after an update.

xspyda said:
I figured that would be the case (though not necessarily cyanogenmod related). This seems to be the common factor with all Nexus S phones suffering from the freezing issue - the problem always starts pretty soon after an update.
Click to expand...
Click to collapse
Do you know if there is any way of fixing it, cause I have even used odin and still nothing. Do you know what the re partition check box in odin does?

As far as I can tell there is no way to fix it, not for us users. Not even sure Samsung fix the issue, seems they just give replacements which is quite worrying.
I started a thread about the freezing issue to gather info and hopefully to find a pattern / solution to the problem. Apart from establishing that the problem seems to occur after an update in.every case, so far no dice.
I'd be delighted to hear of a fix as I feel like I'm waiting for a time bomb to go off with my Nexus S!

Ok... so after doing some reserch i decided to use adb shell to delete the sdcard partition and remake it inorder to hopefully find the error. Everytime i tried deleteing the partition, nothing happened. So i tried resizing it and then i got the error that saying
" /.../clockworkmod/backup/.../data.img is corrupt run scandisk or chkdisk. "
Two things that dont exisist or i dont know how to use on adb shell. Anyways, it seems the corrupt file was created by my clockworkmod before i updated to the new cyanogen.

That's interesting although from my own research I'm not convinced cwm is the cause of the freezing issue as there are many reports of people running into problems without having ever flashed a custom rom or recovery.
I'm glad you're trying to get to the bottom of this though, it wiuld be great for us to be able to find a solution.
I refuse to believe the only sulolution is to replace the phone - can't see this being anything but software related.
Please keep us posted.

[Q] Resetting device encryption

Hello, I am in a bit of a jam and am trying to find the best way out.
My device is encrypted using the native Android feature. I have Lean Kernel and CleanROM on the device. So it is rooted/unlocked. I was trying to clean the device further by uninstalling some useless apps with Titanium Backup. Turns out I messed up on something..
When the phone boots to the encrypted device screen, the keyboard doesn't show up! I am not able to get into the phone to do anything!
I have the latest CWM recovery installed. I tried a factory reset and such, but it says it fails to mount the internal SD card. /:
Anyone know how I can fix this and flash a new CleanROM? Data wiping is not a problem for me, but CWM refuses to mount the SD card to do it..
Any advice? I am relatively new to the Android scene, so try not to make things too complicated.

Odin?
EatonZ said:
Hello, I am in a bit of a jam and am trying to find the best way out.
My device is encrypted using the native Android feature. I have Lean Kernel and CleanROM on the device. So it is rooted/unlocked. I was trying to clean the device further by uninstalling some useless apps with Titanium Backup. Turns out I messed up on something..
When the phone boots to the encrypted device screen, the keyboard doesn't show up! I am not able to get into the phone to do anything!
I have the latest CWM recovery installed. I tried a factory reset and such, but it says it fails to mount the internal SD card. /:
Anyone know how I can fix this and flash a new CleanROM? Data wiping is not a problem for me, but CWM refuses to mount the SD card to do it..
Any advice? I am relatively new to the Android scene, so try not to make things too complicated.
Click to expand...
Click to collapse
This probably wouldn't work, but have you tried reflashing with Odin?

budzylikessoup said:
This probably wouldn't work, but have you tried reflashing with Odin?
Click to expand...
Click to collapse
I am looking at this thread:
http://forum.xda-developers.com/showthread.php?t=1984436
I am downloading the very first package. Since that seems to wipe everything, which is what I want at this point.
Will flashing that work?

I'm not sure if it will work, as I don't encrypt my device. What it will do is wipe your system, data, etc. partitions, but it won't touch your internal SD. This will probably be fine; it will install a keyboard and you should be able to enter your password, that is, if it can flash the ROM properly.

flanks vidsguir
budzylikessoup said:
I'm not sure if it will work, as I don't encrypt my device. What it will do is wipe your system, data, etc. partitions, but it won't touch your internal SD. This will probably be fine; it will install a keyboard and you should be able to enter your password, that is, if it can flash the ROM properly.
Click to expand...
Click to collapse
I'm still trying to understand how Android storage works, so I may sound like a noob here haha..
All I have is an internal SD card. I don't have an external one or anything. Are system, data located on another internal flash chip or something? If they are on the internal SD, I would imagine everything would be formatted and reset once this is flashed.

Sorry, I read the linked post wrong...So this will wipe everything, system, data, and internal SD.
As for the difference, the system and data are different partitions than the internal SD.. so normally when you factory reset in CWM, it just wipes the data, not your internal SD or system. What this means is that it won't touch some files, like ones you download from the internet, but it will get rid of all of your apps and appdata, as you know, and these are stored in the data partition.

I got it sorted. Thanks for the help.

Glad I could help!

EatonZ said:
I am looking at this thread:
http://forum.xda-developers.com/showthread.php?t=1984436
I am downloading the very first package. Since that seems to wipe everything, which is what I want at this point.
Will flashing that work?
Click to expand...
Click to collapse
Just wanna say this thread was a lifesaver, and I'll just leave my experience here for fellow noobs, like myself, stumbling into this issue.
I CMod'd my S3 with Clockwork (following very detailed instructions) and tried out encryption (knowing ahead of time that a factory reset would be in order if I didn't like it). As you all know Clockwork has trouble mounting the encrypted /sdcard/ directory, and won't do the factory reset. I was afraid that since Clockwork couldn't deal with the encrypted data, so too might Odin, leading to the risk of bricking. This thread gave me enough courage to give it a go. Following the above linked instructions solved the problem. Odin had no problem wiping and writing over the encrypted data. after I was back to stock I ran through installing Clockwork and CMod again. And just like that, the problem's fixed.
Thanks a bunch everyone!
EDIT:
I just got a response on twitter from a friend who ran into the same issue with clockwork. According to him, apparently TWRP doesn't have this flaw. My phone's working now and I don't want to monkey around with it anymore, but maybe a more experienced user out there could comment on/confirm this, and maybe add the info to the tutorials (if it's correct).
Thanks again!

SpoonlessCorey said:
Just wanna say this post was a lifesaver, and I'll just leave my experience here for fellow noobs, like myself, stumbling into this issue.
I CMod'd my S3 with Clockwork (following very detailed instructions) and tried out encryption (knowing ahead of time that a factory reset would be in order if I didn't like it). As you all know Clockwork has trouble mounting the encrypted /sdcard/ directory, and won't do the factory reset. I was afraid that since Clockwork couldn't deal with the encrypted data, so too might Odin, leading to the risk of bricking. This thread gave me enough courage to give it a go. Following the above linked instructions solved the problem. Odin had no problem wiping and writing over the encrypted data. after I was back to stock I ran through installing Clockwork and CMod again. And just like that, the problem's fixed.
Thanks a bunch everyone!
Click to expand...
Click to collapse
Yeah, I was worried I might have created a $200 paper-weight!
I'm glad that my question ended up helping you as well!:good:

[Q] after installing 4.4.1 - no cellular + data - SOLVED

SOLVED! see solution in the first comment.
I really need some help...
I installed manually 4.4.1 version using this guide: http://forum.xda-developers.com/showthread.php?t=2523217
(I am having a rooted device with TWRP without any modifications or deletions - used section B)
after the install successfully worked, i chosed to wipe. it was stuck and i used the powerbutton to reload device.
when the device turned on it used emulated storage which means no imei and no efs.
using the twrp (in recovery mode) i can see my full data and efs files.
when i am trying to rewipeqinstall update i get this error: "E:/Unable to mount /cache"
please help me.

hbhc123 said:
I really need some help...
I installed manually 4.4.1 version using this guide: http://forum.xda-developers.com/showthread.php?t=2523217
(I am having a rooted device with TWRP without any modifications or deletions - used section B)
after the install successfully worked, i chosed to wipe. it was stuck and i used the powerbutton to reload device.
when the device turned on it used emulated storage which means no imei and no efs.
using the twrp (in recovery mode) i can see my full data and efs files.
when i am trying to rewipeqinstall update i get this error: "E:/Unable to mount /cache"
please help me.
Click to expand...
Click to collapse
Do not turn the device off while clearing the cache.
Reboot to recovery, go to TWRP settings and enable rm -rf option, go back and wipe the cache/dalvik. If THAT doesn't work, you will need to flash the cache.img from the factory image found here http://forum.xda-developers.com/showthread.php?t=2513701
After you do that, make sure you have the latest version of TWRP installed (2.6.3.4) If you don't you can also choose to install that via ADB before clearing the cache.

Synyster06Gates said:
Do not turn the device off while clearing the cache.
Reboot to recovery, go to TWRP settings and enable rm -rf option, go back and wipe the cache/dalvik. If THAT doesn't work, you will need to flash the cache.img from the factory image found here http://forum.xda-developers.com/showthread.php?t=2513701
After you do that, make sure you have the latest version of TWRP installed (2.6.3.4) If you don't you can also choose to install that via ADB before clearing the cache.
Click to expand...
Click to collapse
First of all - thanks for help.
already tried the rm -rf option unsuccessful.
2 question before I'm starting the flash process:
1. Is there a way dumping the efs folder to my computer before?
2. is this the command i should use: "fastboot flash cache C:/image-hammerhead-krt16m/cache.img"?
thanks a lot.

hbhc123 said:
First of all - thanks for help.
already tried the rm -rf option unsuccessful.
2 question before I'm starting the flash process:
1. Is there a way dumping the efs folder to my computer before?
2. is this the command i should use: "fastboot flash cache C:/image-hammerhead-krt16m/cache.img"?
thanks a lot.
Click to expand...
Click to collapse
1. Use TWRP to back up your EFS data if you would like. You won't lose any data by just flashing the cache though. All your apps and everything should still be there.
2. If you installed the drivers correctly and that is the correct directory for the file on your computer, that is right! I put mine on the desktop for simplicity.

clearing cache/dalvik is very slow on N5, I found, and so is resetting the phone in recovery. though the progress bar may not move the process isn't stuck, it's still going on in background.

chi_heng said:
clearing cache/dalvik is very slow on N5, I found, and so is resetting the phone in recovery. though the progress bar may not move the process isn't stuck, it's still going on in background.
Click to expand...
Click to collapse
Flash the newest version of TWRP. The issue is fixed.

Synyster06Gates said:
1. Use TWRP to back up your EFS data if you would like. You won't lose any data by just flashing the cache though. All your apps and everything should still be there.
2. If you installed the drivers correctly and that is the correct directory for the file on your computer, that is right! I put mine on the desktop for simplicity.
Click to expand...
Click to collapse
I have done what you said and it worked perfectly
many thanks!

hbhc123 said:
I have done what you said and it worked perfectly
many thanks!
Click to expand...
Click to collapse
No problem! Glad you got it taken care of.

What should one do if fastboot flash cache doesnt fix it? im having same issue and i have tried restoring stock, flashing cache, etc. still no imei showing in settings and sim doesnt get reconized. Hangouts fc, google search fc and i cant access sd card in windows or the phone.

any one else
benbailey84 said:
What should one do if fastboot flash cache doesnt fix it? im having same issue and i have tried restoring stock, flashing cache, etc. still no imei showing in settings and sim doesnt get reconized. Hangouts fc, google search fc and i cant access sd card in windows or the phone.
Click to expand...
Click to collapse
I guess me and you are screwed I tried every suggestion on the forums but nothing works I'm just gonna RMA mine and pray that Google doesn't say its my fault I wish someone could help us I gotta send mine off as fast as possible im already looking at two weeks minimum for the RMA so every day I wait is just more time I won't have a phone thanks

ddloco said:
I guess me and you are screwed I tried every suggestion on the forums but nothing works I'm just gonna RMA mine and pray that Google doesn't say its my fault I wish someone could help us I gotta send mine off as fast as possible im already looking at two weeks minimum for the RMA so every day I wait is just more time I won't have a phone thanks
Click to expand...
Click to collapse
yeah i have a rma out for mine. Luckly i have a spare phone (its a damn $15 go phone) but mine is already shipped. biggest issue is the $440 is tied up in my account until they get the bad phone back. basically i would suggest to anyone that if they are going to flash a rom first thing they should do is back up their efs to their pc and also some sort of could (dropbox, drive, mega, box, etc).

benbailey84 said:
yeah i have a rma out for mine. Luckly i have a spare phone (its a damn $15 go phone) but mine is already shipped. biggest issue is the $440 is tied up in my account until they get the bad phone back. basically i would suggest to anyone that if they are going to flash a rom first thing they should do is back up their efs to their pc and also some sort of could (dropbox, drive, mega, box, etc).
Click to expand...
Click to collapse
Well in our case I have my efs on my PC from weeks ago restoring it doesn't fix whatever the ROM changed lol

[Q] Recovery is broken??? I Don't Know.. Please Help

So I bought a Nexus 5 off of craigslist for a pretty good price about a week ago and he had already rooted and installed a custom recovery onto the phone. He had some sort of rom that I didn't like so I decided to flash my own. So I downloaded cyanogen mod (the latest nightly build at the time) and flashed it along with g apps and rebooted the phone. When I it was turning on it said "upgrading apps xxx out of xxx." I was very confused because coming from a Nexus 4 and flashing many ROMs I have never seen this before. When the phone finally powered on it started giving me errors every 5 seconds and I realized soon after that I had my previous apps from the old rom still installed and everything else was in place. I managed to get into settings after clicking ok to errors every 5 seconds and saw that my ROM did indeed change to Cyanogen Mod. I decided to try to factory reset the phone through the settings menu and that fixed the phone seemingly until today. I tried installing another rom but this one is giving me multiple errors and then rebooting my phone. I could not get into the settings to factory reset the phone through there.
I was thinking that maybe the recovery was broken but I'm not sure of how to fix it. I tried to find a flashable recovery but only found IMG versions which I don't know how to install. Is there a possibility of any other issues? I am resetting/wiping cache/wiping dalvik cache every time in that order. When I'm installing the roms it says something about e:/ volume not existing or not being found could that be the problem? I don't recall ever seeing this on my nexus 5. If anyone knows how I could fix this issue I would greatly appreciate your help.
Thanks, Alex:laugh::laugh:

alexdzk said:
So I bought a Nexus 5 off of craigslist for a pretty good price about a week ago and he had already rooted and installed a custom recovery onto the phone. He had some sort of rom that I didn't like so I decided to flash my own. So I downloaded cyanogen mod (the latest nightly build at the time) and flashed it along with g apps and rebooted the phone. When I it was turning on it said "upgrading apps xxx out of xxx." I was very confused because coming from a Nexus 4 and flashing many ROMs I have never seen this before. When the phone finally powered on it started giving me errors every 5 seconds and I realized soon after that I had my previous apps from the old rom still installed and everything else was in place. I managed to get into settings after clicking ok to errors every 5 seconds and saw that my ROM did indeed change to Cyanogen Mod. I decided to try to factory reset the phone through the settings menu and that fixed the phone seemingly until today. I tried installing another rom but this one is giving me multiple errors and then rebooting my phone. I could not get into the settings to factory reset the phone through there.
I was thinking that maybe the recovery was broken but I'm not sure of how to fix it. I tried to find a flashable recovery but only found IMG versions which I don't know how to install. Is there a possibility of any other issues? I am resetting/wiping cache/wiping dalvik cache every time in that order. When I'm installing the roms it says something about e:/ volume not existing or not being found could that be the problem? I don't recall ever seeing this on my nexus 5. If anyone knows how I could fix this issue I would greatly appreciate your help.
Thanks, Alex:laugh::laugh:
Click to expand...
Click to collapse
Did you wipe data and cache before flashing the new rom?

This happened to me loading some ROM previously. You need to make sure that you do a factory reset and wipe the cache and dalvik. I also redownloaded the ROM just to be sure but I do not think that is necessary. It sounds like you dirty flashed. Is the recovery Team win? If so there is a setting under mount that you need to uncheck and it is called system.
edit: I re-read and saw that you are wiping the cache and dalvik cache, by resetting do you mean you are factory resetting? The img files are for you to do through the command line in fast boot and you can find out more by clicking this link: http://forum.xda-developers.com/showthread.php?t=2507905 and also this link: http://forum.xda-developers.com/showthread.php?t=2513701. <--- familiarize yourself with both of those threads and you will be better off than a lot of people that come asking for help. Not saying that you are not well off just knowing is good for the soul.
2nd edit: Since it sounds like he did not wipe the SD card were there good things on there?

I see your doing a clean install. I'd return it to stock and start over, especially considering you bought the phone used. Who knows what's been on it. See this http://forum.xda-developers.com/showthread.php?p=47156064

mistahseller said:
This happened to me loading some ROM previously. You need to make sure that you do a factory reset and wipe the cache and dalvik. I also redownloaded the ROM just to be sure but I do not think that is necessary. It sounds like you dirty flashed. Is the recovery Team win? If so there is a setting under mount that you need to uncheck and it is called system.
edit: I re-read and saw that you are wiping the cache and dalvik cache, by resetting do you mean you are factory resetting? The img files are for you to do through the command line in fast boot and you can find out more by clicking this link: http://forum.xda-developers.com/showthread.php?t=2507905 and also this link: http://forum.xda-developers.com/showthread.php?t=2513701. <--- familiarize yourself with both of those threads and you will be better off than a lot of people that come asking for help. Not saying that you are not well off just knowing is good for the soul.
2nd edit: Since it sounds like he did not wipe the SD card were there good things on there?
Click to expand...
Click to collapse
jd1639 said:
I see your doing a clean install. I'd return it to stock and start over, especially considering you bought the phone used. Who knows what's been on it. See this http://forum.xda-developers.com/showthread.php?p=47156064
Click to expand...
Click to collapse
I'll try this then if it doesnt work ill try the factory reset/ relock whatever, thanks.

mistahseller said:
This happened to me loading some ROM previously. You need to make sure that you do a factory reset and wipe the cache and dalvik. I also redownloaded the ROM just to be sure but I do not think that is necessary. It sounds like you dirty flashed. Is the recovery Team win? If so there is a setting under mount that you need to uncheck and it is called system.
edit: I re-read and saw that you are wiping the cache and dalvik cache, by resetting do you mean you are factory resetting? The img files are for you to do through the command line in fast boot and you can find out more by clicking this link: http://forum.xda-developers.com/showthread.php?t=2507905 and also this link: http://forum.xda-developers.com/showthread.php?t=2513701. <--- familiarize yourself with both of those threads and you will be better off than a lot of people that come asking for help. Not saying that you are not well off just knowing is good for the soul.
2nd edit: Since it sounds like he did not wipe the SD card were there good things on there?
Click to expand...
Click to collapse
no its CWM

You didn't wipe/factory reset.
Sent from my Nexus 5 using Tapatalk

mistahseller said:
This happened to me loading some ROM previously. You need to make sure that you do a factory reset and wipe the cache and dalvik. I also redownloaded the ROM just to be sure but I do not think that is necessary. It sounds like you dirty flashed. Is the recovery Team win? If so there is a setting under mount that you need to uncheck and it is called system.
edit: I re-read and saw that you are wiping the cache and dalvik cache, by resetting do you mean you are factory resetting? The img files are for you to do through the command line in fast boot and you can find out more by clicking this link: http://forum.xda-developers.com/showthread.php?t=2507905 and also this link: http://forum.xda-developers.com/showthread.php?t=2513701. <--- familiarize yourself with both of those threads and you will be better off than a lot of people that come asking for help. Not saying that you are not well off just knowing is good for the soul.
2nd edit: Since it sounds like he did not wipe the SD card were there good things on there?
Click to expand...
Click to collapse
housry23 said:
You didn't wipe/factory reset.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes, I did. I said it in my post.

alexdzk said:
Yes, I did. I said it in my post.
Click to expand...
Click to collapse
I see. Well, if you really did do a factory reset before flashing a new Rom, then maybe you have an old version recovery, or something is borked with your phones partitions. Honestly, buying a used one like that, I would do a full factory restore by flashing the stock images(sticky in general for directions) but don't relock the bootloader. This will erase everything and repartition the phone. Then install recovery and flash away.
Sent from my Nexus 5 using Tapatalk

housry23 said:
I see. Well, if you really did do a factory reset before flashing a new Rom, then maybe you have an old version recovery, or something is borked with your phones partitions. Honestly, buying a used one like that, I would do a full factory restore by flashing the stock images(sticky in general for directions) but don't relock the bootloader. This will erase everything and repartition the phone. Then install recovery and flash away.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I fixed the issue by flashing a new recovery through adb already and it works fine now thank you. I guess it was really my recovery that was broken.

alexdzk said:
I fixed the issue by flashing a new recovery through adb already and it works fine now thank you. I guess it was really my recovery that was broken.
Click to expand...
Click to collapse
Good. Glad you got it worked out. Was probably an old build of whatever recovery and because of the way KitKat changed things, there were a lot of problems wiping when the phone first came out. If you find any more good deals on your local Craigslist, PM me. I want a black n5 instead of my white one.
Sent from my Nexus 5 using Tapatalk

[HUGE BUG] Partitions disappeared!

Hello everyone. Wanted to share an experience with my OPO,.
Today i rebooted the phone, and when it booted up it presented me the first configuration wizard. I thought, "ok this is strange" but after i completed again the configuration everything was still there.
Tonight I tried to install the XNPH33R update via TWRP, i loaded the file into the sdcard and rebooted into TWRP.
I thought "let's make a nandroid before, in case of problems", and i saw it could not mount the /system partition. The backup failed and then i tried to reboot. The phone does now not start and when i try to boot into TWRP, it reports that now ALL the partitions are borked and can't be mounted, reporting them 0MB, except for the boot one.
My question is, am i the only one that experienced something similar?!
I'm goin on to flash factory image but this seems a big problem!

Little hint: try to install another recovery (e.g. CWM, Philz...) before returning to stock

I doubt OnePlus (or any other mfg) would count this sort of thing a bug if your phone is running anything other than 100% stock.

CafeKampuchia said:
I doubt OnePlus (or any other mfg) would count this sort of thing a bug if your phone is running anything other than 100% stock.
Click to expand...
Click to collapse
Obviously i don't want to report a "bug" that i want oneplus to fix
I just wanted to know what happened, my partitions corrupted themselves by... rebooting?
since i saw that many users reported being stuck at the oneplus logo after updating to XNPH33R i wanted to know if this is related to their experience :silly:
dreamerguy00 said:
Little hint: try to install another recovery (e.g. CWM, Philz...) before returning to stock
Click to expand...
Click to collapse
I flashed the factory image except for recovery and everything works, same old TWRP now reports everything as ok and running.. it's just strange! i flashed countless devices and i own a Nexus 4 and a Nexus 5!

blackbird5308 said:
Obviously i don't want to report a "bug" that i want oneplus to fix
I just wanted to know what happened, my partitions corrupted themselves by... rebooting?
since i saw that many users reported being stuck at the oneplus logo after updating to XNPH33R i wanted to know if this is related to their experience :silly:
I flashed the factory image except for recovery and everything works, same old TWRP now reports everything as ok and running.. it's just strange! i flashed countless devices and i own a Nexus 4 and a Nexus 5!
Click to expand...
Click to collapse
Sorry wrong thread
Sent from E.P.D.Center

I had the same weird problem last night.....
Except my recovery was also reverted to stock.
it happened after i got notifed about an update available couple days in a row which i canceled.
I even have Droidwall and everything but a few apps are blocked from data usage.
What i would suggest is to freeze the ""system update" system app.
I kinda have a feeling the OTA updates have something to do with it.
This happend to me 1 other time a while back with an HTC One X device. Same pattern, System update notifications then couple days of ignoring .... then pooffff...
blackbird5308 said:
Hello everyone. Wanted to share an experience with my OPO,.
Today i rebooted the phone, and when it booted up it presented me the first configuration wizard. I thought, "ok this is strange" but after i completed again the configuration everything was still there.
Tonight I tried to install the XNPH33R update via TWRP, i loaded the file into the sdcard and rebooted into TWRP.
I thought "let's make a nandroid before, in case of problems", and i saw it could not mount the /system partition. The backup failed and then i tried to reboot. The phone does now not start and when i try to boot into TWRP, it reports that now ALL the partitions are borked and can't be mounted, reporting them 0MB, except for the boot one.
My question is, am i the only one that experienced something similar?!
I'm goin on to flash factory image but this seems a big problem!
Click to expand...
Click to collapse