Does anyone have the Stock Rom 3.2.2 for the Xoom, post 4G LTE update?
My Xoom was being worked on at a Verizon retailer for connectivity issues and somehow managed to be rolled back to 3.2
I Have now completely lost the ability to connect to 3G as well and was given a new SIM card to help remedy the problem so now my Xoom will not activate since the 4G modem is no longer detected. I have put a call into Motorola and I'm supposedly getting a call back next week so they can schedule another RMA for me to send in my tablet. My theory is if I can get 3.2.2 back on the 4G modem will become available and my tablet will be able to re-activate it self.
If anyone can provide me with a stock 3.2.2 Rom something that can be flashed via fastboot would be great.
Thank you for any assistance you can provide.
FYI, I do not want the 3.2.2 rooted Rom that is out there. I want a stock unmodified version.
Dude just root it! Your gonna have to change the LCD density anyway cuz Google changed it on us when they installed 3.2.2. I have been back and fourth with them on the fact that they did it. I can't download apps that I paid for now! They keep trying to tell me to ask the developers for a refund. I have asked motor for the stock imgs, but they said it can't be released right now. They also said they are trying to find out why Google changed the density when it has nothing to do with the 4g upgrade. You have to either send it in which the Verizon idiots downgraded you for what who knows. This could cause an issue for your warranty. Or just root it and save having to ship it out. Right now that is the only 2 options we have.
Sent from my Xoom using xda premium
Just an FYI that if you use the rooted 3.2.2 image you will lose wifi. Its prevalent now in that thread.
So as it stands now I have applied 3.2.2 + Root. It does not appear to be the same Rom that my Xoom shipped with there are a few menus that are either different or missing. I also now have a Xoom that has no 3G, 4G, or WiFi connectivity. I'm on the phone now with Motorola trying to get them to do an RMA on it. I will roll it back to 3.2 before shipping because I can find that posted on Motorola's dev site. That's also the version of ROM my Xoom was showing when I called my case into Motorola.
Let's see how this goes.
AceXMachine has loaded files that can be flashed straight from fastboot without issues.
Sent from my ADR6400L using xda premium
Here ya go!
http://forum.xda-developers.com/showthread.php?t=1269957
Sent from my ADR6400L using xda premium
This did not work either. It looked promising because there was a update that it downloaded after I applied the Rom but then it came back with no 3G/4G and the menu options still look different. The one good thing is that I have WiFi back.
FYI, I went to a Verizon store just a few moments ago and they are stumped as to why my 3G/4G hasn't returned so they are going to warranty replace it. I also have noticed that now when I remove the SIM card it does not do anything. When I first got the Xoom back with the 4G chip if the SIM card was removed it would complain saying no card detected, now it's as if there is no detection happening. Not sure if that piece of information may be significant for someone else having the same problem as me.
Thanks for all your help everyone.
The loaded HLK75C instead of HLK75D at the upgrade depot. What idiots!
Sent from my Xoom using xda premium
gordon12393 said:
This did not work either. It looked promising because there was a update that it downloaded after I applied the Rom but then it came back with no 3G/4G and the menu options still look different. The one good thing is that I have WiFi back.
FYI, I went to a Verizon store just a few moments ago and they are stumped as to why my 3G/4G hasn't returned so they are going to warranty replace it. I also have noticed that now when I remove the SIM card it does not do anything. When I first got the Xoom back with the 4G chip if the SIM card was removed it would complain saying no card detected, now it's as if there is no detection happening. Not sure if that piece of information may be significant for someone else having the same problem as me.
Thanks for all your help everyone.
Click to expand...
Click to collapse
That's exactly what's happening to me.... have you figured anything out since?
so basically they sent my xoom into Motorola for repair. When I got it back all was good man and its been working fine ever since. Sorry I can't tell you what the root cause of the problem was.
can't root my honeycomb 4g verizon Xoom tablet
ok so followed these instructions exactly but still says my sd card is not mounted. This is a brand new Verizon 4g honeycomb 3.2.2.
Downloaded the ROM Android-HC-3.2.2-Stock+Rooted-1.1-SOLARNZ.zip and saved to my desktop. connected to computer, copied the downloaded Zip file to SD Card. Did the rest of the instructions, no option to do a backup or nandroid backup it just has 4 options: reboot system now, apply update from usb drive, wipe data/factory rest, and wipe cache partition. i did the factory rest then reboot and attempted to install zip but had no install zip option so i tried selecting 'apply update from usb drive' and that's where i get the error "E:failed to mount /sdcard (no such file or directory)." now people have said to make sure the zip file is on the root of the sd, what does that mean actually? when i opened the sd folder on my pc i copied zip to the sd folder, do i need to create a folder to put the zip in your do i need to unzip the file first. I've tried several times and same result, please help.
I had a similar issue, I had to format my SD card in my PC before my table would see it
Hi so I have been dreading bothering anyone and I have tried many things but no success.
The issue: My phone all of a sudden gets super super slow during the day. Happens with or without my apps i like on my phone. If it happens while I am not using the phone I will not get any texts or any phone calls. I can sometimes unlock the screen but clicking on things it just lags to the max. Nothing Force Closes or anything but its just super slow. It gets so slow I have to hold the power button to shut it off and then restart it. This happens at least 2 times a day.
What I have: I have a stock Rom that was rooted using the easy root command on a Windows 7 Machine. I also have CWM installed and the features all work.
What I have tried: I have tried a few different things including using odin to root the phone. I have restored the stock recovery using odin and also wiped and re installed stock Rom with odin. the same thing is happening after all of that work. Its not an app that is doing it because I used a os monitor app and nothing is using the CPU 100% or anything.
I need help otherwise I am going to see if I can exchange it with AT&T but unfortunately trying to repair this thing I had to set off the counter 2 times so I don't know if that will prevent me from being able to do a exchange under warranty.
Freeze the bloatware. If that does not help flash a custom rom
Thank you for the quick response. I did freeze the bloatware and I did try TPC rom and the same exact thing happens.
Then i would exchange it if i was you.
Yea I think i am going to just worried about the flash counter being at 2 now. Right now there is still no way to reset it correct?
No no way to reset. But odin the stock tar. They wont even check the flash counter anyway. Atleast thats been the case for most people.
Carlobravo said:
Yea I think i am going to just worried about the flash counter being at 2 now. Right now there is still no way to reset it correct?
Click to expand...
Click to collapse
Go on eBay and purchase a USB JIG and it would reset it. It only cost about $2.00 USD but you would have to wait about a week since it ships from China...
That what happend to my phone too. I install CWM and root then phone get verry slow. I think there was bloatware so i install custom rom, but then bluetooth stop working and have some more issue with phone not responding. So i install stock and want to start from scrach, but after this i steel had some problem with bluetooth and incoming calls ( phone not pick them up ). I go to ATT store and replace for new one and with orginal software no problem at all for last 45 days. No root no CWM and no problem.. . I use samsung infuse 4G for all software games and works exelent on custom roms and all..
Above&Beyond™ said:
Go on eBay and purchase a USB JIG and it would reset it. It only cost about $2.00 USD but you would have to wait about a week since it ships from China...
Click to expand...
Click to collapse
how to I use that to reset it I thought the jig just puts it in download mode?
Carlobravo said:
how to I use that to reset it I thought the jig just puts it in download mode?
Click to expand...
Click to collapse
Apparently they aren't working at the moment with 2.3.5, you might want to look more into it.
To start, I have never had problems flashing Skyrocket ROMs before. I flashed the ICS leak with Odin when I first got the phone, then CWM, then Cyanogeonmod when that came out, and some other things. But recently I decided to flash SlimBean which suggested TWRP so I flashed that and I had it working well for awhile.
After Google I/O I decided to f;ash the weekly build, SlimBean 5.5. The flash went OK but the ROM was glitchy and crashed a lot. So I decided yesterday to go back to the release channel of SlimBean. So I downloaded SlimBean 5.0 and AIO Addons 5.x and I moved them to my SD card. However before I did that I noticed I already had a 5.x from my last flash that would turn out to be the Aroma installer that i didn't want. But anyways, after wiping the cache, Dalvik cache, system, and data, I flashed the 5.0 ROM then the 5.x aroma aio addons, and then it sent me into the Aroma installer which I figured out that I used the wrong addons aio package. So then I hit next all the way through the installer without changing anything and didn't hit reboot device. Then, still in the TWRP menu, I wiped the same sections I did last time, mounted the SD card through TWRP, moved the AIO Addons 5.x on, and deleted the AIO Aroma 5.x. Then I flashed SlimBean 5.0 from before with the AIO Addons 5.x.
When I hit reboot, my phones screen was off and it never went on again. I took out the battery, had it hooked to the charger, and tried everything and it wouldn't even vibrate. So I knew pretty fast that I had hard bricked it. I Google'd a little bit and read about the jig, but I have a feeling that wouldn't work with this low level of a brick. So I guess what I want to know is what actually happened, and I just want to get this story out there because I have no idea how I got such a low level brick from just flashing ROMs like usual.
Also, I'm planning on making a trip to the AT&T store with hopes of getting a replacement. I don't know if I will because it is refurbished and I bought it online over a year ago. (the warranty being 90 days) Does anyone have experience getting replacements out of warranty?
First off if it's bricked it's bricked it's not about low level or whatever.
Second a jig does nothing for this phone that can't be done manually, don't waste your time or money on it.
Third you can have it jtag'd for $50 by some dudes if you search tons of people have done it.
You left out an astounding amount of detail for an extremely long post so no one can tell you exactly where you went wrong.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Yea, way too many words. But to your last paragraph, good f'n luck. You're way out of warranty.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
You will get no warranty. Send it away for jtag if you want it fixed, you can't fix it if it's hard bricked.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
I sent the phone to be jtag'd and they sent it back saying they couldn't fix it. What could have gone so wrong in the flashing process that it is bricked so badly?
TankTan38 said:
I sent the phone to be jtag'd and they sent it back saying they couldn't fix it. What could have gone so wrong in the flashing process that it is bricked so badly?
Click to expand...
Click to collapse
probably wasnt the flash but bad hardware, most likely mobo/memory, jtag can only write to the mem chip if its corrupted or a incompatible rom was trying to write to it but it wont/cant fix a hw failure of chip
So I decided to go ahead and put my findings of this issue that several of us have had with our phones getting the dreaded "Battery Disconnect" after upgrading from stock ICS to stock JB. I cannot guarantee that this will work for everyone but it did work for me.
Here are the different solutions I have come across in my research on this issue.
1: Battery corruption: get new battery
2: Gold prongs are dirty on phone and battery: clean them
3: Bad charger: get new charger
4: Dirt or dust in USB port: clean with compressed air
Now I tried each of these and unfortunately none worked for me. It has for some that I have read on different sites, so if you don't want to try and re-flash everything try those above.
For those that have tried each of above 4 and still have the issue, like myself, you can try the following. This worked for me, but you have to have patience. Read entire post before trying, check MD5 sums before any flashing and the typical disclaimer, I AM NOT RESPONSIBLE FOR YOU PHONE, TRY AT OWN RISK. Sorry, had to put that in.
1. Have your battery charged to 100%. You need to go back to ICS if you aren't already. If you are on JB right now, wipe your system clean (factory reset) that's including formatting system, data, cache, dalvic, etc. using CWM (that's just what I prefer for this part and what I used). Do a backup first of anything you don't want to lose. I used Titanium Backup Pro myself but pick your own poison. If already on ICS, proceed to step 4.
2: Using ODIN, flash ICS back on to your phone. If you haven't already looked at Vincom's guides, here you go. http://forum.xda-developers.com/showthread.php?t=1652398 and http://forum.xda-developers.com/showthread.php?t=1785999. Keep it plugged into the computer while it reboots. Should show battery charging. If not, do it over. DO NOT ADD CUSTOM RECOVERY AND ROOT.
3: Test all your chargers. Generic and OEM and any additional batteries you may have. Make sure they all work. If so, let it settle for about 10 minutes and then on to the next step.
4: Power off the device and boot into the stock recovery. Do a factory reset, choose reboot and when the phone powers off, take out your battery.
5: Now using ODIN, flash stock JB. Again, leave the phone plugged into the computer until it boots completely. As long as it is charging and not "Battery Disconnect" you're on the right track. If it does not boot, basically just sits on the AT&T symbol for an extended period of time which can happen, remove battery, reboot into stock recovery, factory reset and re-flash JB again. If it says "Battery Disconnect" after it boots, wipe, and re-flash JB again. DO NOT INSTALL CUSTOM RECOVERY OR ROOT YET. I did on my first attempt of these steps and immediately got the "Battery Disconnect". If you succeeded, on to the next step.
6: This is when your patience comes to affect. You need to let the phone settle. I gave mine 2 days of using and charging when dead without getting the "Battery Disconnect". It happened once after a full charge, but only once. I plugged it in while half charged to see what happened and it popped up. Later when it died and I plugged it in, it charged with no problems. Patience. Something about the drivers taking time to settle either in the rom itself or in the kernel for certain devices. Not sure which. I did re-install my apps but I did with using the Play Store and not with my backup. Make sure you are on Wi-Fi so you don't jack up your data usage.
7: Now that you have had two days of using and charging with no issues, fingers crossed, go ahead and install TWRP using ODIN (no wipes needed). After it reboots, again keep it plugged into the computer and if it is charging after boot without the dreaded phrase, CONGRATULATIONS! BUT, I would wait for at least one day before you try any custom roms on it. Again, let it settle first.
I know this is a lot. But again, this is what worked for me after trying for almost two weeks now to find a solution. Good luck everyone, I hope this works for you as well. And thank you Vincom for the guidance.
Thanks! I will try this perhaps if my attempts to return the device fail...
The other thing I am wondering is if anyone that has had this issue has tried going "the long way around" to upgrade... be on ICS, flash TWRP/CWM, then (assuming everything is OK), flash just the JB radios and a custom JB based AOSP ROM and ignore the full ODIN of official JellyBean if the result would be better?
acejavelin said:
Thanks! I will try this perhaps if my attempts to return the device fail...
The other thing I am wondering is if anyone that has had this issue has tried going "the long way around" to upgrade... be on ICS, flash TWRP/CWM, then (assuming everything is OK), flash just the JB radios and a custom JB based AOSP ROM and ignore the full ODIN of official JellyBean if the result would be better?
Click to expand...
Click to collapse
I still had issues with doing that as well. Try though. If it works then let me know and I'll put as another solution in the OP.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
I will let you know, will probably be next week before I get a chance to look at it again.
BTW, I sent an email to tech support, explaining that I used nothing but the stock firmware images and the issues I had... here is there "official" response:
Dear Steve ,
Thank you for contacting Samsung Telecommunications America.
After reviewing your e-mail we understand that, you have updated the device to Jelly Bean and the battery was not charging and you have installed stock ROM of Ice Cream Sandwich.
As we see that, you have rooted the device, we would like to inform you that, rooting the phone will void the warranty. We also would like to inform you that, as the phone is not taking a charge, the device need to be physically examined by the service technicians to reflash the software on the phone. Hence, we request you to contact our voice team, they will assist you further regarding the query.
You can contact our voice support at 1-888-987-4357, Mon-Fri: 7 AM - 9 PM (CST), Sat: 9 AM - 6 PM (CST).
If you have a minute, please click on the “Start survey here” link at the bottom of this email to fill out a brief survey to help us serve you better. Kindly note that you can access the survey page only when the pop-up blocker is disabled on the browser. Have a wonderful day!
Should you have more questions regarding your Samsung Mobile Phone, you can reach out to our chat support team by accessing the following link. Live Chat is available 24 hours a day 7 days a week. Have a wonderful day!
Link: http://www.samsung.com/us/support/contact
Thank you for your continued interest in Samsung products.
Sincerely,
Michelle
Technical Support
Click to expand...
Click to collapse
Basically, it's "Well, too bad... Send it in and we will fix it, for a price!" Thanks Samsung!!!
Yep, that sounds about right.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Changing radios to UCMC1 and installing TWRP recovery and rooting had no effect, with an ICS ROM the battery charges properly.
So this clearly seems to be kernel related with the JellyBean code of the kernel and how it is talking to the hardware, the stock kernel and Marla kernel have the same result... I tried Beanstalk 1.300.3 (Wrap-up 3) and the battery would not charge, in the *#*# menu under battery it showed the exact same thing, "Unknown error" and would not charge. Restore back to ICS from TWRP and everything was OK again. Think I will wait to see how it goes after I get an real Samsung battery, about 95% sure this battery is a fake, but in reading similar discussions on this with SGS2 models, the battery doesn't seem to be the issue but it's worth a shot. I might try a few ICS ROMs and see what happens and report back now that I know restoring back to stock ICS via TWRP is a fix for the problem.
UPDATE EDIT: Well, the seller who sold me this phone, phonesandparts.com on eBay has agreed to take back the device and give me a full refund. Guess I will just do that and now that the Nexus 4 has dropped a $100 on price I can get a Nexus 4. I am tired of messing around with this, I love the device but not being able to flash anything is annoying as all get out, it might be fake, defective, or whatever, but guess I am moving on, just waiting for the RMA then I will have to move back to my old HTC Aria for a while and just deal with it for now and once my refund comes through grab a Nexus.
I flashed my i727 with JB rom, and after do that i recive that message when i tried charge my cell phone, so the sollution was install a Stock rom with odin and go back to ICS every time i try ti update my cellphone with any rom i get that message... but at least i can charge my cellphone again... i write this reply this post because it works for me, and if you had the same problem maybe this can be the solution...
---------- Post added at 11:07 AM ---------- Previous post was at 10:41 AM ----------
acejavelin said:
Changing radios to UCMC1 and installing TWRP recovery and rooting had no effect, with an ICS ROM the battery charges properly.
So this clearly seems to be kernel related with the JellyBean code of the kernel and how it is talking to the hardware, the stock kernel and Marla kernel have the same result... I tried Beanstalk 1.300.3 (Wrap-up 3) and the battery would not charge, in the *#*# menu under battery it showed the exact same thing, "Unknown error" and would not charge. Restore back to ICS from TWRP and everything was OK again. Think I will wait to see how it goes after I get an real Samsung battery, about 95% sure this battery is a fake, but in reading similar discussions on this with SGS2 models, the battery doesn't seem to be the issue but it's worth a shot. I might try a few ICS ROMs and see what happens and report back now that I know restoring back to stock ICS via TWRP is a fix for the problem.
UPDATE EDIT: Well, the seller who sold me this phone, phonesandparts.com on eBay has agreed to take back the device and give me a full refund. Guess I will just do that and now that the Nexus 4 has dropped a $100 on price I can get a Nexus 4. I am tired of messing around with this, I love the device but not being able to flash anything is annoying as all get out, it might be fake, defective, or whatever, but guess I am moving on, just waiting for the RMA then I will have to move back to my old HTC Aria for a while and just deal with it for now and once my refund comes through grab a Nexus.
Click to expand...
Click to collapse
I bought the same cellphone at the same seller and i have problems with the imei: null/null and i search here and maybe they flashed the cellphone with a new rom and lose the files of the EFS folder, so i cant unlock and use with my service network.. i will ask for a return item.
That's rotten luck for both of you.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Well, the seller took back the phone, and issued me a full refund, so this is probably going to be one of my last posts in the Skyrocket forums since I am using those funds and ordered a LG/Google Nexus 4 16GB phone. I really liked the SR and would have kept it had it worked as I had hoped, but with all the issues I had I just figured this was a better way go than fighting with another one since Google dropped the price a $100 on the Nexus. Thanks for the help to everyone, enjoy your Skyrocket.
dgoby said:
So I decided to go ahead and put my findings of this issue that several of us have had with our phones getting the dreaded "Battery Disconnect" after upgrading from stock ICS to stock JB. I cannot guarantee that this will work for everyone but it did work for me.
Here are the different solutions I have come across in my research on this issue.
1: Battery corruption: get new battery
2: Gold prongs are dirty on phone and battery: clean them
3: Bad charger: get new charger
4: Dirt or dust in USB port: clean with compressed air
Now I tried each of these and unfortunately none worked for me. It has for some that I have read on different sites, so if you don't want to try and re-flash everything try those above.
For those that have tried each of above 4 and still have the issue, like myself, you can try the following. This worked for me, but you have to have patience. Read entire post before trying, check MD5 sums before any flashing and the typical disclaimer, I AM NOT RESPONSIBLE FOR YOU PHONE, TRY AT OWN RISK. Sorry, had to put that in.
1. Have your battery charged to 100%. You need to go back to ICS if you aren't already. If you are on JB right now, wipe your system clean (factory reset) that's including formatting system, data, cache, dalvic, etc. using CWM (that's just what I prefer for this part and what I used). Do a backup first of anything you don't want to lose. I used Titanium Backup Pro myself but pick your own poison. If already on ICS, proceed to step 4.
2: Using ODIN, flash ICS back on to your phone. If you haven't already looked at Vincom's guides, here you go. http://forum.xda-developers.com/showthread.php?t=1652398 and http://forum.xda-developers.com/showthread.php?t=1785999. Keep it plugged into the computer while it reboots. Should show battery charging. If not, do it over. DO NOT ADD CUSTOM RECOVERY AND ROOT.
3: Test all your chargers. Generic and OEM and any additional batteries you may have. Make sure they all work. If so, let it settle for about 10 minutes and then on to the next step.
4: Power off the device and boot into the stock recovery. Do a factory reset, choose reboot and when the phone powers off, take out your battery.
5: Now using ODIN, flash stock JB. Again, leave the phone plugged into the computer until it boots completely. As long as it is charging and not "Battery Disconnect" you're on the right track. If it does not boot, basically just sits on the AT&T symbol for an extended period of time which can happen, remove battery, reboot into stock recovery, factory reset and re-flash JB again. If it says "Battery Disconnect" after it boots, wipe, and re-flash JB again. DO NOT INSTALL CUSTOM RECOVERY OR ROOT YET. I did on my first attempt of these steps and immediately got the "Battery Disconnect". If you succeeded, on to the next step.
6: This is when your patience comes to affect. You need to let the phone settle. I gave mine 2 days of using and charging when dead without getting the "Battery Disconnect". It happened once after a full charge, but only once. I plugged it in while half charged to see what happened and it popped up. Later when it died and I plugged it in, it charged with no problems. Patience. Something about the drivers taking time to settle either in the rom itself or in the kernel for certain devices. Not sure which. I did re-install my apps but I did with using the Play Store and not with my backup. Make sure you are on Wi-Fi so you don't jack up your data usage.
7: Now that you have had two days of using and charging with no issues, fingers crossed, go ahead and install TWRP using ODIN (no wipes needed). After it reboots, again keep it plugged into the computer and if it is charging after boot without the dreaded phrase, CONGRATULATIONS! BUT, I would wait for at least one day before you try any custom roms on it. Again, let it settle first.
I know this is a lot. But again, this is what worked for me after trying for almost two weeks now to find a solution. Good luck everyone, I hope this works for you as well. And thank you Vincom for the guidance.
Click to expand...
Click to collapse
After step 4 I guess I need to put the battery back in before proceeding with 5 and ODIN right?
djandreski said:
After step 4 I guess I need to put the battery back in before proceeding with 5 and ODIN right?
Click to expand...
Click to collapse
Follow Vincom's steps to use Odin. Step 2. It will tell you when to put the battery back in.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
So have you tried installing custom ROM like CM 10.2 or 10.1?
Does it charges properly?
djandreski said:
So have you tried installing custom ROM like CM 10.2 or 10.1?
Does it charges properly?
Click to expand...
Click to collapse
Until I did the novel I wrote above, nothing worked. Either it was an immediate disappointment or wouldn't work after the first charge. Since then the phone has worked perfectly with any rom. Even an aftermarket battery. I don't want to put "solved" in the OP until I get feedback from others that it worked for them as well.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
I repeated the step 5 three times and every time the same. Right after reboot I get "Battery disconnected" error message. I re-flashed JB, as I said 3 times but every time i see that error.
So I don't know if I can continue and use my phone until full discharge, I am afraid that I can't charge the battery back, and revert to ICS.
djandreski said:
I repeated the step 5 three times and every time the same. Right after reboot I get "Battery disconnected" error message. I re-flashed JB, as I said 3 times but every time i see that error.
So I don't know if I can continue and use my phone until full discharge, I am afraid that I can't charge the battery back, and revert to ICS.
Click to expand...
Click to collapse
I have to ask of course, did you follow everything exactly? I.e. not rooting or installing custom recovery
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
dgoby said:
I have to ask of course, did you follow everything exactly? I.e. not rooting or installing custom recovery
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Of course, just plain stock JB ROM.
UPDATE:
Here is what I did. I used stock ICS for about a day, then I updated it with Kies, just to try my luck, and as you guess that stupid error poped up.
I continued from step 5 , so I reboot in recovery, did factory reset and install stock JB ROM with ODIN
djandreski said:
Of course, just plain stock JB ROM.
UPDATE:
Here is what I did. I used stock ICS for about a day, then I updated it with Kies, just to try my luck, and as you guess that stupid error poped up.
I continued from step 5 , so I reboot in recovery, did factory reset and install stock JB ROM with ODIN
Click to expand...
Click to collapse
Instead of using Kies I would use only Odin. I know you're running low on battery but I would start over but charge it up while on ICS. I was only successful using Odin in this process.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Out of the blue my Nexus 5 totally flipped out. It only recognizes 215MB of 16GB internal storage, the rest is missing. It's also not getting service. Also, every time I reboot the phone, it goes back to totally factory stock. So I tried unlocking it, successfully, but then on reboot it was locked again. Need to unlock and install custom recovery so I can flash a new ROM, but I can't because of the reset thing. Any ideas?
Rma the device. It sounds like your emmc flash memory is bad. You have the symptoms
Sent from my Nexus 5 using XDA Free mobile app
Log please. Perhaps you messed up with partitions just like me yesterday
GR0S said:
Log please. Perhaps you messed up with partitions just like me yesterday
Click to expand...
Click to collapse
What logs? There's basically no storage on the device, and when I plug it into my computer, it sees the phone but it's totally empty. I did nothing to any partitions. This is my wife's phone, and she's been using it bone stock since she got it a few months ago. She wouldn't let me do anything to it, no rooting, no unlocking, and she doesn't do anything to it herself except use basic apps. It just started doing this on its own. I think we'll RMA it.
RemeCA said:
What logs? There's basically no storage on the device, and when I plug it into my computer, it sees the phone but it's totally empty. I did nothing to any partitions. This is my wife's phone, and she's been using it bone stock since she got it a few months ago. She wouldn't let me do anything to it, no rooting, no unlocking, and she doesn't do anything to it herself except use basic apps. It just started doing this on its own. I think we'll RMA it.
Click to expand...
Click to collapse
go RMA then. Just thought you messed up like me yesterday (no radio, no modem).