I flashed the factory images onto the device since I'm going to RMA it. Now it only shows up as a 8gb version.
I just tweeted at jbq about this.
Google can't seem to do anything right with this device.
nakasi-jro03d from developers-dot-google-dot-com?
I just flashed this today and it shows as 16gb (13.5gb usable).
Verixx said:
nakasi-jro03d from developers-dot-google-dot-com?
I just flashed this today and it shows as 16gb (13.5gb usable).
Click to expand...
Click to collapse
Yeah. The normal amount of storage was there prior to flashing the images. Now its not. I am going to try a regular factory reset from the device and see if that changes the outcome. If nothing changes I will flash the images again since you reported you had no issue.
Edit. Normal factory reset from inside the OS has it reporting the correct amount of data.
albundy2010 said:
Yeah. The normal amount of storage was there prior to flashing the images. Now its not. I am going to try a regular factory reset from the device and see if that changes the outcome. If nothing changes I will flash the images again since you reported you had no issue.
Click to expand...
Click to collapse
Good luck, let us know how it works out. If it matters, I flashed it by using fastboot -w update image-nakasi-jro03d.zip in Windows.
I have the same problem. Anxiously awaiting any details about how you resolve this.
Yeah I know exactly how to use fastboot. I notified jbq about it fixing itself with a factory reset on twitter. I am most likely going to reflash the factory images again to see if If the result is the same. That should not have happened.
.
Azimuth0r said:
I have the same problem. Anxiously awaiting any details about how you resolve this.
Click to expand...
Click to collapse
Try a factory reset from device. That wipes all your data off which should be obvious but eh. Don't want to blamed for you or anybody else loosing their data. That has it working normally again for me
Update. Reflashing the the factory images caused the device to never make it out of the boot animation.
So I re downloaded the factory images and checked the md5 check sum. Flashed them and the device boots up normally. It goes to the wifi network screen but will not connect to any network. Just gets stuck at obtaining IP address.
Conclusion is my device is piece of crap hardware wise and far as the factory images and flashing them goes that's a piece of a crap as well.
Update, decided lets try and flash it again one more time. This time everything works software wise as it should.
My outgoing tablet is possessed by gremlins as simms22 would say. Makes no damn sense.
To the other user who reported the same storage issue, let me know if you get it straightened out.
Try a different wifi network mine did that as well tried another network was fine.
+1 for the issue here as well.
Related
Weirdest thing happens, I'll boot my DS7 and it's like if I just did a factory reset...every time. I'll customize my homescreens/gmail and what not, and do a normal reboot and it does a factory reset every time. I've read a few threads about similar topics and no one seems to know what's going on.
I've wiped data/cache/dalvik and fixed permissions, doesn't help. Re-install ROM, doesn't help.
I tried reflashing superuser.zip says installation aborted (bad). Same when I try to flash HC (yes, I'm still on Froyo).
Any clues ladies and genitals? Any help would be appreciated.
Sounds like you are experiencing the READ-ONLY bug that plagues this device. Hopefully it is still under warranty so that you can send it to Dell. Last summer I sent my Streak 7 to Dell. They repaired the read-only bug and had it back to my house in about 2 weeks.
Basically, what happens when your tablet goes into read-only mode... any updates, installs, customizing you do will be lost upon a reset... even though it appears like things are updating, they simply are not saved to the internal flash drive. Also, when it gets really bad some of the apps (along with the web browser) will start to get fatal errors.
That sounds about right, especially since even when I try to move a file from my netbook to the device (such as a new ROM to try to flash in CWM) it wont show up after I reboot either.
Don't think its under warranty anymore, dang.
Yes this is what happened to the one I got off Craigslist too the person I bought it from also changed his phone number instantly, so I got screwed but I'm in the process of getting a replacement or getting an extended warranty on it.
Sent from my Galaxy Nexus using XDA App
Ive searched and havent been able to find a solution to this, although Ive seen it asked before.
Galaxy Tab P100 bought from a pawn shop. It still has the prior owners (unknown) gmail info minus p/w. I cannot remove the account, or access market because of this. Everytime I tried to data reset (both via Privacy settings and also CWM), add a new rom, or add apps - after I reboot it goes back to the prior owner settings and apks.
I have Odin'd/Heimdall with different roms but they dont stick. Different kernels install though. Ive added two different CWMs. Superuser breaks after every reset - I gain, then lose, root. Ive rooted/added root explorer and deleted accounts.db and user.db - they go back after. Ive spoken with Sprint and we tried everything they had, as well as a ##786# and MSL number (resetting phone activation I think?). Their response was take it in to send back. I want to fix it myself.
It seems to me that this prior info is overriding and reinstalling every reboot, preventing any new flashing/etc from taking place.
Here is my question. I took it apart this morning and disconnected the battery (thinking maybe it will wipe any memory). But does it have a CMOS-type battery? I noticed there is a small round battery-looking connection soldered into the mainboard (see here - step 7/8 http://www.ifixit.com/Teardown/Samsung-Galaxy-Tab-Teardown/4103/1)
Does anyone know what this is? I dont really have anything to lose, but Im not great with a soldering iron, but will try. Im thinking this might be for the memory, and disconnecting/reconnecting this would erase any permanent user information, freeing it up for me to add mine.
Or if anyone has any new ideas I would appreciate it.
Thanks for the time. Ed
Sent from my rooted/rom'd PG86100 using XDA Premium App
It is not a battery backed memory, it is a NAND chip.
Sounds like the chip gone bad.
Sent from my GT-P1000 using XDA
Just an update.
I did not do anything with the round battery thing, as priyana stated the memory is stored on a nand chip. I put the tab back together.
I rooted again, and found the ea24 firmware and loaded it via odin. It took, but the prior user info was still there, and everything (I mean a crapload of apps) began force closing. I did confirm that ea24 was on it. I then flashed back to ef17.
I contacted Sprint repair store again, and they told me that they probably cant fix it, and its something they have to send back. They said that I have done all that they would do in-store.
I dont understand what could be wrong, as I found the prior owner and spoke with her. She had no issues with it. It worked fine prior to her getting rid of it. And it works fine, I just cant get rid of any prior info. I googled it and it seems like there are people out there who have the same problem, but no one has an answer, including sprint or samsung.
So much for my venting. Ill keep trying to find an answer.
roninep said:
I have Odin'd/Heimdall with different roms but they dont stick. Different kernels install though. Ive added two different CWMs. Superuser breaks after every reset - I gain, then lose, root.
Click to expand...
Click to collapse
First of all, I'd like to apologize for posting something that won't really help, but I recognize this from somewhere else. On some devices, there's some kind of file (that you can delete via the adb prompt when you're root) that on every bootup checks to see if the installed ROM matches stock, and if not, restores to stock. This sounds exactly what you're experiencing when you mention that no ROMs "stick".
I think you should try to look into if there's some files that need to be erased in order for a ROM to be cleanly installed that you haven't gotten rid of. It might also be some kind of feature that the previous user enabled, so maybe it's somewhere around in the settings that you can disable it, who knows.
It definitely does not sound like a memory issue because I don't see how a memory issue could make the stock ROM suddenly appear again after you've installed a custom ROM through CWM (assuming CWM gives no errors or anything and the custom ROM has actually been wiped).
Maybe you can do a more thorough wipe of the device memory manually with some guidance from someone who knows more about how these tablets work :fingers-crossed:
I agree with you about some type of file and bootup. Thats why I went with maybe it being a cmos/nand issue. I couldnt understand that I wiped everything, and information was still coming back. It makes me think that somewhere, something is being stored separate from the main drive.
Ive used the factory restore, CWM (2 different versions - 3 and 5 I believe), and wiped data (factory reset), cache and Davlik three times each before I flashed the CM ROMs. And I have not had any errors or problems installing any of the CWMs.
I spoke with the previous user, and she did nothing above turning it on/off, and using it. I am not on the Sprint network with it, and the wi-fi doesnt turn on until I set it up, so I cant see it being something that contacts Sprint and OTAs from them.
Can anyone tell me if, using ADB, there is a more thorough wipe I can perform ? More than the normal one done through CWM or Android factory restore?
Something similar to the reformatting of a hard drive?
Thanks
Ed
I have the same problem. Did you find any solution?
I believe the previous owner info is stored on sprint servers. When you reboot, it downloads all the crap.
The long time required to reboot explains the slow transfer of data - wireless.
These wireless service providers are pretty sneaky.
Thanks
Hi,
Have you tried formatting both internal and external Sd via Windows? (connecting via USB)
You can also try CM10, it has a different memory map which will write your device completely.
Regards
Sent from my GT-P1000 using Tapatalk 2
I have this same problem with a tab. Its not connected to sprint,has not been on the internet at all. Was there ever a fix for this?? Please let me know its a christmas present and i need to fix this issue. Thank you
So I've been having this strange problem and I am convinced there is no simple solution. Every time I wipe date and install a rom, I try to sign in to the Google account during setup, and I keep getting an error saying that there was a problem communicating with Google servers. I've done a factory reset, formatted everything, tried different RUUs, and nothing seems to work. I just can't sign in on a Sense 5.5 rom. So now I want to clear the phone completely, because there must be something that no form of wiping is touching. A stock RUU can't solve the problem and I don't know what can. I even tried using LTE instead of WiFi and still no luck. Does anyone have any clue about this?
Prophet16 said:
So I've been having this strange problem and I am convinced there is no simple solution. Every time I wipe date and install a rom, I try to sign in to the Google account during setup, and I keep getting an error saying that there was a problem communicating with Google servers. I've done a factory reset, formatted everything, tried different RUUs, and nothing seems to work. I just can't sign in on a Sense 5.5 rom. So now I want to clear the phone completely, because there must be something that no form of wiping is touching. A stock RUU can't solve the problem and I don't know what can. I even tried using LTE instead of WiFi and still no luck. Does anyone have any clue about this?
Click to expand...
Click to collapse
I had the same thing. My solution was wipe everyithing except data and internal memory. After that no more errors
donkeykong1 said:
I had the same thing. My solution was wipe everyithing except data and internal memory. After that no more errors
Click to expand...
Click to collapse
But I have wiped everything including internal storage and used usb-otg to install roms. Nothing works. Are you sure that will fix this?
EDIT: Can confirm that your recommendation doesn't work for me. I decided to flash a different rom (InsertCoin) and in this one I can sign in, but it won't sync, it just keeps saying "Google Sync error."
Prophet16 said:
But I have wiped everything including internal storage and used usb-otg to install roms. Nothing works. Are you sure that will fix this?
Click to expand...
Click to collapse
It did the trick for me. Also, I mount system in recovery before doing anything. I'm pretty new to this phone and never used any recovery except 4ext on my Desire and Evo so I can't be 100% sure, leaving data did the trick for me
I've tried a few new things so far. I used the mkfs.ext4 file to format the data partition as I think that's where the source of the issue lies. But I also used fastboot to format system. If this doesn't work then I don't know what else to to. I might be forced to run a GPe rom or some other android rom. I just strongly prefer sense.
Prophet16 said:
I've tried a few new things so far. I used the mkfs.ext4 file to format the data partition as I think that's where the source of the issue lies. But I also used fastboot to format system. If this doesn't work then I don't know what else to to. I might be forced to run a GPe rom or some other android rom. I just strongly prefer sense.
Click to expand...
Click to collapse
whats happens if you start a new account
It won't work. I tried typing in random letters in to the user name and password box but it doesn't even try to connect.
Well I've got bad news. I managed to hard brick my device, so this issues I was having is not an issue for me anymore. But if anyone can help find a solution that would be appreciated as I'm sure someone else might be facing the same problem.
Define hard brick
SaHiLzZ said:
Define hard brick
Click to expand...
Click to collapse
Hard Brick = Phone that has been thrown on the floor and crushed with a very large rock.
SaHiLzZ said:
Define hard brick
Click to expand...
Click to collapse
That's when you can't enter the bootloader anymore. You hold the power button and the lights on the bottom don't flash and it'll just vibrate a bit. But it's all good I got the phone replaced today. So then I installed the rom I was trying to install earlier (the one where I couldn't sign in to google) and I ended up having the same issue. So I think I'm gonna just use ARHD or something.
Hello, I have searched for a solution and found some that worked, My WIFI on my moto x will not connect to any network.
it just started a few weeks ago, But going to in to recovery mode and wiping the cache was working it would connect again.
Thing is it's not only on my home network if i go to any place with WIFI it shows the network, I try to connect and it disappears.
I had the kitkat update I tried to factory reset that did not work also reflashed to jelly bean to see if that would fix the problem. I did not restore any back ups of my device since it could have been a corrupt setting or file that was messing it up. Still no luck I tried some of the router options found on the web about changing the channels. Just to be clear it will not connect to any WIFI not just the one at my house.
I spoke with Fido tech support and after explaining everything i tried they said i was out of options and since I bought the phone right out, I would have to call Motorola and see if they can fix it, thing is i unlocked the bootloader when I rooted it when i first had it with it's stock jelly bean.
I know this is a on going issue for many other moto x, could it just be a hardware issue now my phone has been in a otter box defender since the day i bought it, it has no damage or ever been dropped in water.
it's frustrating, my data works perfect and every thing else on phone works great. I really like the phone but since the bootloader is unlocked the warranty is now void and I only had the phone since dec 2013.
does any one have any last options I could possibly try thanks in advance.
xsnyper said:
Hello, I have searched for a solution and found some that worked, My WIFI on my moto x will not connect to any network.
it just started a few weeks ago, But going to in to recovery mode and wiping the cache was working it would connect again.
Thing is it's not only on my home network if i go to any place with WIFI it shows the network, I try to connect and it disappears.
I had the kitkat update I tried to factory reset that did not work also reflashed to jelly bean to see if that would fix the problem. I did not restore any back ups of my device since it could have been a corrupt setting or file that was messing it up. Still no luck I tried some of the router options found on the web about changing the channels. Just to be clear it will not connect to any WIFI not just the one at my house.
I spoke with Fido tech support and after explaining everything i tried they said i was out of options and since I bought the phone right out, I would have to call Motorola and see if they can fix it, thing is i unlocked the bootloader when I rooted it when i first had it with it's stock jelly bean.
I know this is a on going issue for many other moto x, could it just be a hardware issue now my phone has been in a otter box defender since the day i bought it, it has no damage or ever been dropped in water.
it's frustrating, my data works perfect and every thing else on phone works great. I really like the phone but since the bootloader is unlocked the warranty is now void and I only had the phone since dec 2013.
does any one have any last options I could possibly try thanks in advance.
Click to expand...
Click to collapse
Hi,
I suggest you do a full SBF restore. Don't confuse this with a factory reset....SBFing can actually repair a corrupted filesystem, while a factory reset does not.
You can find a great guide here:
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
There are 2 methods. RSD Lite and manual method. Either will work, but pay very close attention to the instructions.
You will find the SBF file for your particular carrier/version here:
http://sbf.droid-developers.org/phone.php?device=0
Good Luck
P.S. I too was having strange WIFI issues. The SBF back to stock fixed it 100%. Hope it works for you.
no luck
samwathegreat said:
Hi,
I suggest you do a full SBF restore. Don't confuse this with a factory reset....SBFing can actually repair a corrupted filesystem, while a factory reset does not.
You can find a great guide here:
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
There are 2 methods. RSD Lite and manual method. Either will work, but pay very close attention to the instructions.
You will find the SBF file for your particular carrier/version here:
http://sbf.droid-developers.org/phone.php?device=0
Good Luck
P.S. I too was having strange WIFI issues. The SBF back to stock fixed it 100%. Hope it works for you.
Click to expand...
Click to collapse
I followed the guide step by step, Still no luck.
shows the wifi connections, saves them and shows that it is connecting and just goes back to saved, or disabled. Sometimes even just disappears took it in to have it looked at and the guys at the fido store had the same issue trying to connect to their network.
They keep saying it is a software issue but i'm starting to think it might be hardware. I even tried some fixes with Root to get access to the persist folder to change a file. Tried booting in safe mode to see if it would connect and just does the same thing, I might just be buying a new device just got one of those unlucky ones thanks again tho.
xsnyper said:
I followed the guide step by step, Still no luck.
shows the wifi connections, saves them and shows that it is connecting and just goes back to saved, or disabled. Sometimes even just disappears took it in to have it looked at and the guys at the fido store had the same issue trying to connect to their network.
They keep saying it is a software issue but i'm starting to think it might be hardware. I even tried some fixes with Root to get access to the persist folder to change a file. Tried booting in safe mode to see if it would connect and just does the same thing, I might just be buying a new device just got one of those unlucky ones thanks again tho.
Click to expand...
Click to collapse
I would suspect a hardware issue since you have doctored your persist partition, and you have restored the others via SBF. Bummer :/ Maybe someone else will have another suggestion for you.
Good Luck
Thank you
Thank you Very Much
Working again!
I did not give up and it's working again thanks to samwathegreat, I dont mean to bump my old post but I just want to share with other xt 1058 users that may have been having this issue.
I had mentioned before I used some one else's persist files to try and fix mine and thought it was a hardware problem, Well turns out it was not.
I used the files samwathegreat posted in this post
http://forum.xda-developers.com/showpost.php?p=54089540&postcount=7
I also made a back up of mine, the files in that folder are for a xt 1060 but corrected my problem now I can connect every where again including my house and any other place that offer WIFI.
I was not able to send it to Motorala since I had unlocked the boot loader and warranty was void. All I could do was wait, I even flashed a tmobile 4.4.3 to see if that would fix it with no luck. Any ways just want to say thanks again samwathegreat!!! :good::good:
xsnyper said:
I did not give up and it's working again thanks to samwathegreat, I dont mean to bump my old post but I just want to share with other xt 1058 users that may have been having this issue.
Click to expand...
Click to collapse
Congrats bud!!! Don't worry about the files being from an XT1060 - they are the same on all Moto X variants.
Glad to hear it is all sorted out!!! Enjoy.
I don't see EQC1 on sammobile, anyone else see the 127 MB update?
I'm on EQB1.
Yup, I see it, 127.53mb on both of mine SM-N910T3 and
SM-N910T
I have it as well. Have you flashed yet?
I have it too. I'm not sure I want to flash, especially if it patches the ability to root my phone.
My phone also suffers from the SD card / reboot issue (the phone constantly boot loops when both an SD card and SIM card are in the phone). I wonder if this update will fix that?
I tried flashing it and it failed, I'm running a stock highly modified rom. I'll try reflashing the original stock unmodified rom when I get a chance tomorrow and apply the update. It looks like it's just security updates
Says "Various system improvements" for the QC1 update.
https://support.t-mobile.com/docs/DOC-28899
I updated to this version the other day, now I'm looking to root. Anyone know if the old root method still works? I may try myself in the next few days myself and find out.
I upgraded to it yesterday. Took about 30 minutes from start of install to finish. It updates the security to March 2017, has the new Google Play Store. Other than that I do not notice any other differences
Can i root after upgrade?
Does anyone know if this fixes the mmc_read failed issue along with its constant lagging/freezing problem?
febzz88 said:
Does anyone know if this fixes the mmc_read failed issue along with its constant lagging/freezing problem?
Click to expand...
Click to collapse
I'm pretty sure the mmc_read failure issue is failing hardware and no firmware release can fix this. My understanding is some Note4's had dodgy flash memory and will eventually fail. I had this happen to my note4 last year and got it changed out under warranty at a tmobile store. My phone had the constant lagging/freezing for about a month before it would just no longer boot, it wouldn't do anything other than a quick vibrate on power up, no boot screen of any type.
If you are getting mmc_read I would suggest you get the phone replaced ASAP, and make backups of everything you have on it that you want to keep. At some point it probably just wont power back on again. Hopefully you are still under a warranty and can get it swapped out.
d0ug said:
I'm pretty sure the mmc_read failure issue is failing hardware and no firmware release can fix this. My understanding is some Note4's had dodgy flash memory and will eventually fail. I had this happen to my note4 last year and got it changed out under warranty at a tmobile store. My phone had the constant lagging/freezing for about a month before it would just no longer boot, it wouldn't do anything other than a quick vibrate on power up, no boot screen of any type.
If you are getting mmc_read I would suggest you get the phone replaced ASAP, and make backups of everything you have on it that you want to keep. At some point it probably just wont power back on again. Hopefully you are still under a warranty and can get it swapped out.
Click to expand...
Click to collapse
Hi,
That's certainly is one possible scenario (hardware failing). But based on my extensive research too, many have said that this could be faulty firmware. I went to a Samsung Experience Center and talked with a guy there and he said that it's a known issue affecting many Galaxy Note 4 Sprint users a few months ago. Samsung in the end replaced/repaired the affected units free of charge.
In the past 2 months or so, more and more Galaxy Note 4 users started experiencing this issue. And so it could be that the firmware triggered the issue, and eventually damaged the hardware.
Since we don't really have a 100% certain answer (of course, Samsung will never tell us), I'm just trying to see if anyone has updated the phone to the latest firmware and could tell us if it fixed the issue.
Soooo..... Is this rootable or not?
sino8r said:
Soooo..... Is this rootable or not?
Click to expand...
Click to collapse
Try this https://forum.xda-developers.com/no...rom-n910t3uvu3eqc1-stock-rooted-odex-t3592242
I can't seem to get TWRP to work on this. I've tried several times with Odin, it appears to be successful, phone reboots, but then when I try to reboot into recovery there's no TWRP, only stock. Anyone else have this issue or any suggestions?
Edit: Tried something I remembered reading in another thread. I pulled the battery immediately after Odin successfully finished and the booted directly into recovery. It worked. I'm flashing pvsgh's rooted EQC1 and will report back if TWRP sticks
Edit 2: Success. Seems like pulling the battery after Odin/TWRP before the phone reboots did the trick
ok, thanks for the suggestion.
Anybody have a link for the firmware?
thecrunked said:
Anybody have a link for the firmware?
Click to expand...
Click to collapse
https://forum.xda-developers.com/no...firmware-galaxy-note-4-n910tuvs2eqb1-t3569911
Can I autoroot with EQC1?
I tried auto root and got
RECORVERY IS NOT SEANDROID ENFORCING,
AM I screwed? I assume there's some way to get back to EQC1 and boot the phone. There has to be. But could I do it and keep the data. I was trying to get deleted photos back.