People that can't get the roms beyond stock to work, are your phones activated?
Is it possible to use the Pac Man Rom or CM10 on an unactivated phone?
I'm having similar issues to others trying to flash Pac Man and CM10.2. The first boot was fine and I can access everything on the phone fine, including settings. I rebooted and the activation screen (which I skipped as this phone doesn't have service) always pops up but I would like to use it without putting it on a cell network. I can skip the screen fine (until I decide to disable it) but then have issues like the keyboard (physical and touch), systemUI or NAV Bar crashing with a constant message pop up telling me it has crashed. I have returned to stock using RSD and reflashed Pac Man and CM10.2 MANY (15+?) times, doing a clean install 99% of the time but also trying a couple dirty installs to cover my bases. I should also note that I flashed the phone to Cricket but have no plans to activate it anytime soon.
Another thing to note is that I had issues getting the custom roms to boot at all as the initial setup would take hours. One time I though it was a boot loop but I left it on all night and it had booted in the morning. I believe it has something to do with the file check at boot (with my 32GB low speed class SD card) but that seems to be resolved and I can get the custom roms to boot fine (on the first boot) even with my 32GB (witch is fine and has no errors nor is generic, before you ask.) I also have tried 2 4GB cards and a 2GB card, all different brands, with no change in behavior.
I have done everything below multiple times and in different orders.(If needed I can give a direct breakdown step by step but if you could do it with the files below, I have probably tried it)
Wipe the phone (including all storage internal and external SDs included)
Using RDS v6.15
RDS asanti_c_sprint-user-4.1.2-9.8.2Q-122_XT897_FFW-5-6-release-keys-cid9.xml.zip (Works 100% of the time and never has issues. I keep reverting back to this if I actually need to use the phone)
RDS ClockworkMod, TWRP, and Open Recovery without TWRP (Tried different versions when available)
Then used each recovery to install Pac Man or CM10.2 (tried 10.1 once but had the same issues and I didn't see the need to troubleshoot a rom people seemed to not want to develop for. So 10.1 was only tried once but has the same issues)
Installed GApps at this point but I also tried alternate versions of GApps and not installing it at all. All have the same effect and don't seem to be contributing to the problems at all.
A few installed I tried wiping the phone again or installing each zip multiple times. I also verified the zips were good when on the device to make sure there was no corruption at transfer.
I also tried multiple (confirmed working) SD cards and installing from the internal storage.
I have tried installing arrrghhh's Kernel too.
The issue ether seems to be boot loop (if it's doing a file check) or more often it works until I get one of the said crashes after a reboot.(blame Tyler message is getting SO old...) The time I see the errors seems to be accelerated if I mess with the settings a lot but I don't believe it is directly related to the settings.
My next recourse is to try and flash it back to Sprint (maybe check my Cricket settings) and see if that helps, without it being activated.
On a separate note.
If people need help I can help get you back to stock easily. The instructions/guides on here are all but useless if you don't know what you are doing already. I have seen down to "USE RDS" or "DELETE LINE MD5" like people would just know what that means. I understand RDS Lite is a standard tool for flashing phones but it's nigh impossible to find real explanations on what stuff does in context. I understand the basics though, so if anyone has any questions I can walk you through it.
To start with if you are stuck in a loop at the start of a new rom and it loops between the 'Welcome' Screen (Select your Language) and Activation screen just skip the initial setup by tapping the corners on your screen in a clockwise manor when on the 'Welcome' screen to skip the setup there is a video to explain it here
pocketnow(can't post links )com/how-to/android-quick-tip-how-to-bypass-touch-the-android-to-begin-video
Without doing this or activating the phone it seems to loop between those 2 screens forever (might indicate part of the problem with customs roms....)
I hope this is enough info to go off of I can give you a play by play with the actual files if you need. Maybe a video if needed and I'm feeling extra fancy.
Thanks for your time.
Hey buddy,
If you're trying to make a guide, make sure you call it what it is properly - RSD Lite.
Also, maybe clean up your post a bit so it's a proper guide (as you point out, it's needed) and make a separate thread for your question.
To answer your question, the unactivated phone shouldn't be an issue in of itself - you'll just get the nag screen like you were talking about.
I know there is an issue some are having with rebooting the 4.3 ROM's. Have you tried any 4.2.2 versions of anything? Carbon, CM10.1?
I wonder if your "flash" to Cricket is causing issue, I'm not sure. Let me know about 4.2.
Edit - I missed this part on my first read of your PM. Taking hours to boot is NOT normal. Perhaps remove the SD card entirely, flash using the internal SD... I've never heard of that. Anything over say 20 minutes is probably cause for concern.
Thanks for taking time to answer me.
In no way was I trying to make a guide yet but I guess I could. I just hate posting stuff without useful content so I figured throwing that in was better than nothing. I'll clean it up and set up some links later today. It's frustrating to try and make a full guide before I can post links that would be needed for it. You are totally right though! (complain about crappy guides and kind of make one... )
Part of my point there was that I can't post out of Q and A and this wasn't really a question so I made a question out of it and that's how my post ended up.
I have flashed many phones before but like I said I'll try and put it back on Sprint later today (probably will be a few hours) as I backed up the settings the phone came with. I know it was a wall of text and not the easiest to read so you probably missed it but I also said in my first post that I tried the internal SD card many times and the taking hours to boot isn't the standard and doesn't seem to happen at 99% of the time. It seems to be related to the recovery software I use as it happened a lot more when I was testing TWRP and none when I use clockwork.
What Recovery do you recommend? I swear they aren't made equal...
I tested CM10.1 once and it had the exact same issues as CM10.2 and Pac Man so I didn't test it further but if you want me to test it I can. I just didn't want the Rom.
I don't want Carbon either but I'll test that and AOKP next. It's just annoying that the stock rom works perfect but I can't get these to function at all. I almost wish I didn't get Pac Man to work at all. I'm very particular about my settings and NEED these features after I tried them Pac Man is AMAZING.
Thank you for the help and I hope I can get this worked out.
PS I saw that you were frustrated about working on a rom you don't have a device for. I hope you don't let a little thing like that stop you as, for the little time I have used it, it's all I want. Thanks again.
Blasz said:
What Recovery do you recommend? I swear they aren't made equal...
Click to expand...
Click to collapse
Well, OpenRecovery has probably the most work done for this device specifically. I liked TWRP, but it seems lately it has been unstable - you're not the first who has reported issues lately. I don't think CWM has been updated, unfortunately - but perhaps that's a good thing, it's stable that's for sure.
Blasz- I was just about to start a thread when I found yours, and it very accurately describes the issues I've been having. Here's my progress so far.
I got my Photon Q with Sprint and used it for a few months before Sprint started finding creative ways to take my "$79.99" bill and make it more like $140 a month. Naturally, I refused to pay. So I had a Photon Q with no cell service. This is fine, as I only need it to work on WiFi, not 2G/3G and there is no 4G in the area. Anyway.
At the time, I had Ice Cream Sandwich on it, using the (latest?) ICS firmware from Motorola. This worked very well, but I later tried to use a newer firmware, and all the custom ROMs had shown up while I hadn't been looking. All of these seemed to be based on JellyBean. First off, I tried CyanogenMod 10.2. Worked amazing well! I had literally no problems at all. However, while I was experimenting with different software for the phone, and wanted to see if "Arrrgghh"(sp?)'s kernels would give me some decent overclocking capability. Turns out, the kernel I picked wasn't compatible with the JB firmwares (I probably picked an older one by mistake.) Needless to say, it now wouldn't boot. It'd go to the "Unlocked bootloader" screen and stay there all night (literally, I tried that.)
So, I went back into CWM, which is the recovery I have installed. I erased /data, /cache and /system, and also the dalvik cache and battery stats for good measure. I also formatted /pds and /modem, I believe, which was probably dumb of me since I'm not sure what those do. Then I tried re-installing CM 10.2 from CWM. The installation went fine, and it works gorgeously. However, there's two weird issues:
1) WiFi and Bluetooth don't even BEGIN to work! Neither does Cell, as far as I can tell, because where CM used to be unable to make calls or access the internet (of course, I've not been paying my bill), it now shows an empty signal bar or "No Signal" (the little red X) in the notification bar ... When I try to turn on WiFi using the slider in Settings, it moves to "ON" (stays gray) and pauses for a few secs, then goes back to OFF. Same thing for BT. If I open the WiFi menu where you select an AP, it tells me to turn on WiFi. I do, using the slider up top, and the same thing happens. WiFi and BT simply won't turn on. Tried fiddling with every setting I can find.
Before this misadventure with the kernel/reinstall, WiFi worked great. I connected to a local AP and was surfing the net and downloading apps.
2) The system takes a VERY long time to boot up. It sits at the "Unlocked Bootloader" screen for up to a whole minute. Then it goes to the Cyanogen screen for about 30 seconds. Then it gets to the homescreen. It's fine so long as you let it boot up, but this doesn't seem normal.
Next I tried other ROMs thinking that might help. I installed AOKP, PacMan, CM1.0, Carbon, SlimBean, and I think a few others without results-- they all work but WiFi and BlueTooth are dead. PacMan is the only exception-- it boots up and then endlessly gives me "Blame Tyler" errors until I force the machine to shut off.
I also tried an older ROM, since these are all JellyBean ROMs and I wanted to get back to ICS (I'm not that fond of JB's interface) anyway. I was unable to find any ZIPs I could install through CWM of the stock firmware. I found some IMGs that it looks like I could install via Fastboot, but I don't currently have a PC with admin priveleges (it's not mine) so I can't install the drivers to use Fastboot or any part of the SDK. (I can, however, put files on my SD card, that doesn't require privleges.) The closest ROM I found to stock was "TwistedAsanti" beta-1 or whatever it's called. That installs fine, but again, it takes about 2 straight minutes to boot and it's useless after that:
It gets stuck at "Starting Services..." and will sit there forever, even left there all night. Behind this, a dialog pops up saying no cell networks were found and asking if I want to switch to GSM. (i've been trying GSM and CDMA ROMs all this time, I don't need cell access so I doubt it matters which I use. I'm in the USA.) You can pull down the notification bar and get into the Settings, and even launch a couple programs, but I can't find ANY way to get to a homescreen. Task manager shows Circles is running, which is a widget on the homescreen, so where the heck is that screen? .. I try, again, to turn on WiFi or BT without success. The friggin thing just won't turn on.
Did I eff it up by erasing the "PDS" or "modem" partition? Am I missing something obvious or is my phone just possessed?
In a few days I should have access to a computer where I can hopefully use Fastboot and see about installing a stock firmware (wish me luck). Until then, does anyone have a ZIP file I can flash from CWM to get back to an ICS firmware? I managed to find a copy of the stock firmware, in the form of a dump done from TWRP (in .win files). But as far as I know the only way to install TWRP is using Fastboot, and I've explained why I can't do that. I don't know a way to install TWRP from CWM. Maybe I can do it from CM10.2, if I can put APKs or something on my SD card. I can't get it on the network, so I have to copy all the files manually. Needless to say, it's a pain.
After my frenzy of ROM installing, I got frustrated and decided to see if TwistedAsanti would do SOMETHING if I let it sit at "Starting Services" overnight. To my mistake, I left it under my pillow and the system was quite toasty, and the battery had run dead. Plugging it back into the charger, it made a few worrying clicking noises from the speaker, then the green LED came on. This LED seems to mean "I'm charging, but the battery is too dead to turn on for a while." After it sits there a while, the green LED turns off and it just goes black. Or it goes to BOOTLOADER UNLOCKED and bootloops, or goes to black untilyou fiddle with the power button some more. I can once in a blue moon get to CWM. Sometimes it gets to the homescreen. It will charge up to about 4-7% and no further (battery got damaged by the heat?) It doesn't reliably work when plugged in, it likes to shut off at random anyway.
So now I'm stuck with a phone I can't seem to charge, or turn on reliably, and if I *do* get it to boot up, there's no way to connect it to a network.
Needless to say I'm pretty darn frustrated..
Thanks for any advice.
Epicenter714 said:
So now I'm stuck with a phone I can't seem to charge, or turn on reliably, and if I *do* get it to boot up, there's no way to connect it to a network.
Needless to say I'm pretty darn frustrated..
Thanks for any advice.
Click to expand...
Click to collapse
Did you try to use RSD Lite and flash the device back to stock?
arrrghhh said:
Did you try to use RSD Lite and flash the device back to stock?
Click to expand...
Click to collapse
Currently, I have no PC to use that has Admin priveleges, so I can't install the USB drivers or RSDLite. I also can't use fastboot to install TWRP to use the TWRP .win backups I found.
I did get a roommate to let me use his laptop for 10 minutes to try RSD Lite, but I had this result: Loaded the ".xml.zip" file for the 4.0.4 and 4.1.2 firmwares (after removing the 'getvar' line that causes problems) and it says the phone reported "FAIL". No further details. MiniRSD gives no info from the phone other than the model (it all stays blank), is that supposed to happen? I have the phone in "AP Fastboot" mode so I don't see the problem.
The guy who let me use his PC momentarily is computer-illiterate and thinks anything will break it, so he only let me use it momentarily, and won't let me touch it because I accidentally left an icon on his desktop. I'll have to ask someone else, I think I may know somone..
If I do, how do I get around this error in RSD Lite? Will keep doing research on my own .. thanks!
Epicenter714 said:
Currently, I have no PC to use that has Admin priveleges, so I can't install the USB drivers or RSDLite. I also can't use fastboot to install TWRP to use the TWRP .win backups I found.
I did get a roommate to let me use his laptop for 10 minutes to try RSD Lite, but I had this result: Loaded the ".xml.zip" file for the 4.0.4 and 4.1.2 firmwares (after removing the 'getvar' line that causes problems) and it says the phone reported "FAIL". No further details. MiniRSD gives no info from the phone other than the model (it all stays blank), is that supposed to happen? I have the phone in "AP Fastboot" mode so I don't see the problem.
The guy who let me use his PC momentarily is computer-illiterate and thinks anything will break it, so he only let me use it momentarily, and won't let me touch it because I accidentally left an icon on his desktop. I'll have to ask someone else, I think I may know somone..
If I do, how do I get around this error in RSD Lite? Will keep doing research on my own .. thanks!
Click to expand...
Click to collapse
Well remember - if you are on JB and you are downgrading to ICS, there are additional lines to remove.
Other than that, not sure why it would fail. Make sure 'fastboot devices' works in the command line before doing RSD perhaps.
arrrghhh said:
Well remember - if you are on JB and you are downgrading to ICS, there are additional lines to remove.
Other than that, not sure why it would fail. Make sure 'fastboot devices' works in the command line before doing RSD perhaps.
Click to expand...
Click to collapse
I'm trying to wipe the device clean and install ICS. Are there any other lines I need to remove? ..
As for Fastboot.. I did 'Fastboot Devices' and got no devices listed. How come it shows up in MiniRSD? .. I have the drivers installed, Windows says it installed an ADB device successfully. What are some reasons that might not work? Is there any sort of guide for this? Thank you
---------- Post added at 05:51 PM ---------- Previous post was at 05:29 PM ----------
Oh, as far as the weird booting problem, it seems the battery is fine and the charger died coincidentally at the same time as the overheating did. So my only problem is software now.. thanks.
Epicenter714 said:
I'm trying to wipe the device clean and install ICS. Are there any other lines I need to remove? ..
As for Fastboot.. I did 'Fastboot Devices' and got no devices listed. How come it shows up in MiniRSD? .. I have the drivers installed, Windows says it installed an ADB device successfully. What are some reasons that might not work? Is there any sort of guide for this? Thank you
---------- Post added at 05:51 PM ---------- Previous post was at 05:29 PM ----------
Oh, as far as the weird booting problem, it seems the battery is fine and the charger died coincidentally at the same time as the overheating did. So my only problem is software now.. thanks.
Click to expand...
Click to collapse
I have no clue what MiniRSD is - you mean RSD Lite?
If it doesn't show up in fastboot devices, sort that out before trying to use RSD.
As I stated previously, if you were on JB and going down to ICS you have additional lines which are needed to remove.
Yes, RSD Lite. I don't know where I got MiniRSD from.
I got it to show up in fastboot devices, but adb devices doesn't show it. Weird. Is that OK?
I was able to flash TWRP to the phone with Fastboot. RSD Lite was unable to find the phone. However, I opened the XML file and was able to figure out the flash commands to enter from a command prompt, so I did that:
I got these results... all of the files flashed successfully to stock, except for two. I forget the first, haven't got it in front of me, but here's the big one: SYSTEM! (Important, no?) Here's the error from fastboot:
>> fastboot flash system system.img.ext4
fastboot said:
target reports max download size 31457280 bytes
Invalid sparse file format at header magi
Click to expand...
Click to collapse
(then, Fastboot crashes.)
Does anyone know how to fix that? Also, the system image is way bigger than 31.4 MB. What is it talking about?
Thanks!
Epicenter714 said:
Yes, RSD Lite. I don't know where I got MiniRSD from.
I got it to show up in fastboot devices, but adb devices doesn't show it. Weird. Is that OK?
I was able to flash TWRP to the phone with Fastboot. RSD Lite was unable to find the phone. However, I opened the XML file and was able to figure out the flash commands to enter from a command prompt, so I did that:
I got these results... all of the files flashed successfully to stock, except for two. I forget the first, haven't got it in front of me, but here's the big one: SYSTEM! (Important, no?) Here's the error from fastboot:
>> fastboot flash system system.img.ext4
(then, Fastboot crashes.)
Does anyone know how to fix that? Also, the system image is way bigger than 31.4 MB. What is it talking about?
Thanks!
Click to expand...
Click to collapse
I would NOT recommend entering those fastboot commands in the XML file manually unless you KNOW what you are doing.
Sort out why RSD isn't working. adb and fastboot are two different things. If fastboot devices shows the device, RSD Lite should work fine. Try again.
Related
Following various threads here how to successfully unlocking and rooting their device, I've failed on so many levels.
At the moment I think my xoom is semi-bricked because its just stuck on the M screen. I've think I got the recovery screen working last night as I was able to go into recover mode but after updates through wifi I think it possibly stopped it.
So when i reboot and go into recovery mode, I get an exclamation mark over an android. I've tried rebooting and just got it to mount back on Fastboot but when I've tried to wipe it and reflesh it to (recovery-Tiamat-R4c-100611-1150-cwm.img) its not doing what its suppose to do and giving me "unknown partition, Failed to process command error (0x300003)
Any ideas what I need to do?
Btw, I can reboot, voldown and then volup to choose the 3 options but like I said I can't get into the recovery mode properly.
Schizophonic said:
Following various threads here how to successfully unlocking and rooting their device, I've failed on so many levels.
At the moment I think my xoom is semi-bricked because its just stuck on the M screen. I've think I got the recovery screen working last night as I was able to go into recover mode but after updates through wifi I think it possibly stopped it.
So when i reboot and go into recovery mode, I get an exclamation mark over an android. I've tried rebooting and just got it to mount back on Fastboot but when I've tried to wipe it and reflesh it to (recovery-Tiamat-R4c-100611-1150-cwm.img) its not doing what its suppose to do and giving me "unknown partition, Failed to process command error (0x300003)
Any ideas what I need to do?
Btw, I can reboot, voldown and then volup to choose the 3 options but like I said I can't get into the recovery mode properly.
Click to expand...
Click to collapse
Could I ask what steps in rooting you completed successfully and where exactly it went wrong?
Then, what exactly have you done to try to move forward?
Also, which guide did you use?
Don't worry, you're not bricked if you can get to fastboot.
okantomi said:
Could I ask what steps in rooting you completed successfully and where exactly it went wrong?
Then, what exactly have you done to try to move forward?
Also, which guide did you use?
Don't worry, you're not bricked if you can get to fastboot.
Click to expand...
Click to collapse
Last night I followed this videolinked in http://www.youtube.com/watch?v=OYc1lVWm7ks to Unlock OEM my device
I think that worked fine because it didn't throw up any hiccups.
I then followed this http://forum.xda-developers.com/showthread.php?t=1242241 to root it. It didn't have superuser so I downloaded it and installed it and then tried Terminal on the "SU" command. Said I did not have 'permissions'
This morning, I then followed this Youtbue link http://www.youtube.com/watch?v=ZsVpY0PDwtQ and after the first reboot of puting the new .img, it failed to reboot. Now I'm stuck on the M screen.
I think I managed to get my computer to pick up the device in adb fastboot because it responds to that. However when I type in adb devices it doesn't pick up anything...
Next after messing around I managed to flash it to the boot.img on this, http://forum.xda-developers.com/showthread.php?t=1049901
It flashed it ( I think) and worked without errors unlike the other flash I tried today, and its still stuck in M screen.
BTW, this is a UK Wifi Zoom.
Little update - I've downloaded and flash this boot: boot_3.1_insecure.zip from http://forum.xda-developers.com/showthread.php?t=1049901 and now boots up. However my Wifi has now disappeared. I'm in the process of doing a factory reset but will this work?
Still no avail - need to get this wifi working again soon. Think I've finally got access to superuser
Schizophonic said:
Little update - I've downloaded and flash this boot: boot_3.1_insecure.zip from http://forum.xda-developers.com/showthread.php?t=1049901 and now boots up. However my Wifi has now disappeared. I'm in the process of doing a factory reset but will this work?
Still no avail - need to get this wifi working again soon. Think I've finally got access to superuser
Click to expand...
Click to collapse
It sounds like you are on the right track. Hang in there, you'll make it!
Do you have access to an Ubuntu OS? when you connect an android device to a PC running Ubuntu it will mount the internal memory to the PC which makes it much easier to browse the partitions. Also, Go ahead and reflash the CWM recovery through Rom manager (if thats available to UK users) so that hopefully youll get a fresh recovery.img to work with. As far as ADB not noticing the xoom, you probably erased the adb drivers, and is the usb cord youre using 100% data transferable type? I about pulled my hair out a few times because adb wouldnt recognize my phone but realised I was using an older micro usb cable that only allowed electrical current for charging, not data transfer capable. You might also be able to find a clean nandroid backup file from a fellow UK xoom owner, that you trust, and see if they dont mind sending you their backed up boot-img and system-img. Just some guesses, but sounds like you got it pretty well figured out
Hello all, after a bit of self taught ADB and etc and understanding the mechanics how to successfully flash a Xoom, I managed to follow another guide from stratch (unlock oem, etc) and flashes it to the US stock 3.2.2 rom. It picked up wifi but couldn't connect for some reason - maybe different frequency?
Anyway since then I've installed one of the custom Roms here Team Tiamat Xoom Rom 2.2.2 and all is well now Got my Xoom back up and running with superaccess.
Thanks for all the info on this forum, great place for resource
Mind you, coming from a background with no experience with ADB, it was a bit mind boggling but I managed to get there in the end. Just a bit of feedback for those authors with the guides - maybe put a little subsection on the basics of how to get things prepared and up and running. This I think will help a lot of people who cannot sit for hours on end to trouble shoot something if it goes wrong. Most of the guides here are very useful and handy but at time I just kept saying to myself "wtf, what, where, huh?"
Schizophonic said:
Hello all, after a bit of self taught ADB and etc and understanding the mechanics how to successfully flash a Xoom, I managed to follow another guide from stratch (unlock oem, etc) and flashes it to the US stock 3.2.2 rom. It picked up wifi but couldn't connect for some reason - maybe different frequency?
Anyway since then I've installed one of the custom Roms here Team Tiamat Xoom Rom 2.2.2 and all is well now Got my Xoom back up and running with superaccess.
Thanks for all the info on this forum, great place for resource
Mind you, coming from a background with no experience with ADB, it was a bit mind boggling but I managed to get there in the end. Just a bit of feedback for those authors with the guides - maybe put a little subsection on the basics of how to get things prepared and up and running. This I think will help a lot of people who cannot sit for hours on end to trouble shoot something if it goes wrong. Most of the guides here are very useful and handy but at time I just kept saying to myself "wtf, what, where, huh?"
Click to expand...
Click to collapse
My guide, which is highlighted in the Xoom Heaven thread has a large section on setting up your adb files etc.
http://forum.xda-developers.com/showthread.php?t=1249798
Rooted 3.2 Xoom FAIL
Hi All,
Not the best way to join the boards but I am in deep....
I have a canadian wifi xoom on 3.2. I followed these instructions (How to root 3.2 on US WiFi & Verizon 3G XOOM! (Windows and Mac)) to root my xoom and was having issues with a wifi error.
I decided to use the Canadian boot.img file and when I rebooted the xoom got stuck on the moto logo and is no longer recognized by my computer.
I have tried resetting through the android recovery (I dont have anything 3rd party installed) but no luck. I am afraid that this thing is a total write off.
Any thoughts? Thanks
Blair
My phone did not want to boot this morning after swapping SIM-cards twice. Tried many things, including a hard reset, but nothing worked; the phone kept getting stuck in the second boot menu (with the fancy coloured X). When I tried to leave it it took a few minutes but the phone finally booted.
But I lost all settings (not files luckily) and came into an unknown screen. Had to setup a Google account but could not do that before accessing for internet. All these things work again, but when I reboot the phone it seems to reset again and I have to start from this unknown screen again.
Does this sound familiar and what can I do about it?
By the way, the phone currently runs Android 2.3.6 so there are no official updates (right?).
I've been messing around a bit and the "unknown screen" seems to be the new initial Android screen, in which you can setup the phone (Google account etc.). Strangely enough the phone keeps resetting and I cannot change anything. Even formatting, either through Windows or the boot/root menu doesn't help: all files that are on the phone right now are kept. I cannot add new files either.
Liquid_Metal said:
I've been messing around a bit and the "unknown screen" seems to be the new initial Android screen, in which you can setup the phone (Google account etc.). Strangely enough the phone keeps resetting and I cannot change anything. Even formatting, either through Windows or the boot/root menu doesn't help: all files that are on the phone right now are kept. I cannot add new files either.
Click to expand...
Click to collapse
First of all, do you have a Nexus S, or Nexus S 4G? Is your bootloader unlocked? If not then I suggest you follow the guides in the development section. I can't put links due to still being 'new' on here. Find a recovery, flash via fastboot, boot into recovery and flash a rom to your liking. Or you can find some system images and flash via fastboot. I hope this helps. If not, then you can pm me and then I will show you how.
mabry said:
First of all, do you have a Nexus S, or Nexus S 4G? Is your bootloader unlocked? If not then I suggest you follow the guides in the development section. I can't put links due to still being 'new' on here. Find a recovery, flash via fastboot, boot into recovery and flash a rom to your liking. Or you can find some system images and flash via fastboot. I hope this helps. If not, then you can pm me and then I will show you how.
Click to expand...
Click to collapse
Thanks for your reply. I did not unlock the bootloader. I've seen many difficult topics and don't really know where to start.
I just found out that the phone not necessarily resets to a previous state (this morning) but seems unable to write anymore. I just hooked it on to my PC, removed a file, disconnected, and upon reconnection the file was there again (whereas Windows really removed it).
Liquid_Metal said:
Thanks for your reply. I did not unlock the bootloader. I've seen many difficult topics and don't really know where to start.
I just found out that the phone not necessarily resets to a previous state (this morning) but seems unable to write anymore. I just hooked it on to my PC, removed a file, disconnected, and upon reconnection the file was there again (whereas Windows really removed it).
Click to expand...
Click to collapse
I am uploading some files to Dropbox now. Its gonna take a bit. Then I will guide you through, step by step. Sorry for the wait. I know you want to get your phone back up and running. In the meantime, I recommend doing some reasearch here on xda. Don't be afraid of Google, either. Google can be your best friend.
---------- Post added at 02:42 PM ---------- Previous post was at 02:18 PM ----------
Read this. This should help you out.
http://forum.xda-developers.com/showthread.php?t=935819
Read it first. It might come across tricky or hard, but its not... Once you do that to unlock bootloader and root, I would advise you to download either a stock rom, or any others you may feel comfortable with. Look around. There are plenty here on xda.
mabry said:
I am uploading some files to Dropbox now. Its gonna take a bit. Then I will guide you through, step by step. Sorry for the wait. I know you want to get your phone back up and running. In the meantime, I recommend doing some reasearch here on xda. Don't be afraid of Google, either. Google can be your best friend.
---------- Post added at 02:42 PM ---------- Previous post was at 02:18 PM ----------
Read this. This should help you out.
http://forum.xda-developers.com/showthread.php?t=935819
Read it first. It might come across tricky or hard, but its not... Once you do that to unlock bootloader and root, I would advise you to download either a stock rom, or any others you may feel comfortable with. Look around. There are plenty here on xda.
Click to expand...
Click to collapse
Thanks again . A friend of mine was trying to help with bootloading and stuff, but it's somewhat obscure. He said that chances that it's software or hardware are just 50:50.
Got me kinda frustrated yesterday evening but I still have warranty on the phone (have it for half a year now). Problem is that it might be a hassle, because of a conflict between the shop and the provider. But that should work out.
In the meantime it would be nice to try and get it running again.
Strangely enough, the phone drained itself this night. I made a basic install yesterday and left it in standby. This morning, when I checked the phone, it didn't do anything so I thought it finally passed away. Now that it's hooked to my computer it's charging, and it seems to start from 0 (starting with 0 bars of the battery).
Via your link I came to the following guide, which worked partially (cannot link it here).
age tee tee pee ://jaxov.com/2011/02/how-to-root-android-2-3-3-gingerbread-on-nexus-s/
I got up to step 13, where it seems that I cannot find the .zip-file because the phone doesn't store new files...
You can wait for warranty, or you can follow this guide:
http://forum.xda-developers.com/showthread.php?t=947950&highlight=odin
Odin will flash it back to stock without the need to put files on your sd card. Just download the odin files, open up odin, put phone in download mode, and happy flashing. You have to be careful with odin, though. Follow the guide. If you need help, then let me know. I can probably do it remotely for you.
Thanks, I'll try that tomorrow (topic doesn't seem so clear at first glance).
According to this guide, I have to start in Download Mode. I can access this by holding Volume Up + Volume Down and then plugging in the USB cable. It works, but the phone will not be updated and I'm stuck with the "Downloading..." message. Also, Windows Device Manager sees a Gadget Serial, which I cannot update. Google didn't allow for a clear answer (Samsung PC Studio 7 didn't work).
I also think I have an i9023, because it's the European version (which SHOULD be with an LCD screen).
By the way, I just tried formatting through Windows (FAT32) and if still connected the phone indeed seems to be empty. But as soon as I disconnect USB storage all files (on the phone) are back. Nothing special because the problem is very consistent.
Update
Alright, I finally got the drivers properly installed (also to work in Download Mode) and found proper Bootloader/PDA/CSC files (i9023EUR) for Odin and managed to do the flash update (however Odin I used is called I9003_Odin3 v1.82, don't know if that is a problem).
Then I should do a factory wipe, which works (Bootloader -> Recovery -> Wipe), but if I explore the phone I can see that all data is still present (all images, music, etc). So the hard drive still seems fixed.
Please help me out, guys...
Suggestions? Or unfixable and should I send it to be repaired?
I found out that I did not post my last update. I managed to flash with Odin, and I can get into the Bootloader menu to wipe the phone's data. I can, in Recovery Mode, also see the hard drive and it seems to be empty. That is, the phone fails to see it.
When I reboot out of Recovery Mode the phone gets stuck at the Google logo and that's it..
Ok, I will send the phone to be repaired. The phone is now unrooted and does not go further than the Google load screen.
Do you have fastboot? If not then download below.
http://dl.dropbox.com/u/64632729/platform-tools.zip
Extract contents to desktop. Open up a command prompt:
cd Desktop/platform-tools
Put phone in bootloader mode. In command prompt type:
fastboot oem unlock (only if your bootloader is still locked). If its unlocked then download this
http://dl.dropbox.com/u/64632729/recovery-clockwork-5.0.2.0-crespo.img
Put in the platform-tools folder you extracted earlier. Then type in command prompt:
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
Sometimes the flash might say 'fail' if that is the case then just boot the recovery image by typing:
fastboot boot recovery-clockwork-5.0.2.0-crespo.img
Now boot into recovery and flash either a stock rom, stock rooted rom, or whatever your desire is.
This should work. If not, then there has to be a hardware issue with phone and go ahead and send it in for warranty. Let me know if this helps.
Flashing Clockwork did work, but if I understand correctly I have to copy the stock rom to the phone and load it in Recovery Mode? When I connect the phone to my PC it is recognized as an Android Phone (and even as a Nexus S) but the drive it shows up as seems to be recognized as empty ("Please insert a disk into Removable Disk (E.").
So what do I do?
What is sort of promising is that it indeed was capable to flash Clockwork. So the memory is not completely stuck. However, when I do a format, still nothing happens (phone isn't formatted).
Update: I am able to mount the phone to USB and I can access the phone via Windows. However, I can still not format the SD Card (which is of course internal) or put files (stock rom) on it. Are there other tricks to flash a stock rom? If not, it does indeed seem to be that I cannot flash a custom/stock rom because the drive of the Nexus is frozen/broken/whatever.
Hello all, this is my first real post here,
and I hate to say that I have a problem! First off let me say, I have trolled(and found MANY fixes here) and never had to sign up, because anything I needed was in the search menu!! which let me say is Awesome...
However i have a different problem this time, lol
I recieved my OTA of JB, I was rooted, after following a few steps, I unrooted and was able to update to JB, I rooted again, and somehow or another, I ended up back on ICS,(I found this VERY VERY weird) didn't think this was possible, but it happened after a few flashes.
Anyways today, I plug my phone into my pc,(after a few weeks of it working properly) to upload some pictures, it automatically started to flash, I unplug, reboot(which works most of the time) however NOT this time,
I have the following on my screen
AP Fastboot Flash Mode(S)
10.98(*)(sha-56608bc, 2012-11-23 and time)
eMMC Info:size 16gb
Device is LOCKED, Status Code:0
Battery Low
Transfer Mode: USB Connected
Partition(boot) Security Version Downgraded
Fastboot Reason : Boot Failure
usb connected
I have tried to load a 3rd party xml file aquired from this site, when loading I can get into the other screen which allows me to wipe data etc. but still nothing, Also tried to just let it run its course and nothing..
Officially I am a N00b and I would like some help
The third party file, gives me the error(rsd lite 6.1.4) flash fail
Now I cannot find much info on this, and am Kinda in a bind. Any help is appreciated and I will gladly take the n00b comments with it as I realize this is my own fault..lol
update: when I boot my phone OFF of usb cord, I get fastboot reason: sticky bit factory_fastboot at the bottom now, wtf is this? lol
waynold78 said:
Hello all, this is my first real post here,
and I hate to say that I have a problem! First off let me say, I have trolled(and found MANY fixes here) and never had to sign up, because anything I needed was in the search menu!! which let me say is Awesome...
However i have a different problem this time, lol
I recieved my OTA of JB, I was rooted, after following a few steps, I unrooted and was able to update to JB, I rooted again, and somehow or another, I ended up back on ICS,(I found this VERY VERY weird) didn't think this was possible, but it happened after a few flashes.
Anyways today, I plug my phone into my pc,(after a few weeks of it working properly) to upload some pictures, it automatically started to flash, I unplug, reboot(which works most of the time) however NOT this time,
I have the following on my screen
AP Fastboot Flash Mode(S)
10.98(*)(sha-56608bc, 2012-11-23 and time)
eMMC Info:size 16gb
Device is LOCKED, Status Code:0
Battery Low
Transfer Mode: USB Connected
Partition(boot) Security Version Downgraded
Fastboot Reason : Boot Failure
usb connected
I have tried to load a 3rd party xml file aquired from this site, when loading I can get into the other screen which allows me to wipe data etc. but still nothing, Also tried to just let it run its course and nothing..
Officially I am a N00b and I would like some help
The third party file, gives me the error(rsd lite 6.1.4) flash fail
Now I cannot find much info on this, and am Kinda in a bind. Any help is appreciated and I will gladly take the n00b comments with it as I realize this is my own fault..lol
update: when I boot my phone OFF of usb cord, I get fastboot reason: sticky bit factory_fastboot at the bottom now, wtf is this? lol
Click to expand...
Click to collapse
1) Don't use the fastboot files from here just yet... they are unofficial right now. I'm working on something better.
2) Your battery is low, you should get a factory cable or factory adapter. Look it up...
danifunker said:
1) Don't use the fastboot files from here just yet... they are unofficial right now. I'm working on something better.
2) Your battery is low, you should get a factory cable or factory adapter. Look it up...
Click to expand...
Click to collapse
I seen that it was low, switched back to my wall plug and I don't know if its charging or what, but now battery is OK, weird.
Ok, I will hold off, but from what you see , does this seem fixable? I love the phone, and if its a brick, then I may be a lil heart broken but lesson learned for sure. lol
I am on a Verizon Razr Maxx HD (xt926). This all started when I decided to cleanly flash the newest version of CM10.2. I had been running it before. I wanted to start from a blank slate, so I went into TWRP and did the format wipe. Installed the newest CM10.2 nightly and gapps. This went fine and I booted into the ROM and started recovering all of my stuff. I installed F-droid and AdAway, and rebooted for that. The phone never got past the Bootloader Unlocked warning screen. I turned it off and went into TWRP to try some things. I tried to fix permissions, but it failed, referencing something to do with fdroid. I wiped again and reinstalled CM, but I still couldn't get past the Bootloader Unlocked warning.
I booted into TWRP again and wiped what I could, and accidentally wiped my external SD, and I had no card readers lying around to get the ROM zips back onto it. I downloaded the Razr HD utility, used the batch file, and tried to flash the stock rom through fastboot, but it got stuck in some kind of loop and would not flash correctly. I then tried to do it manually, but got some sort of buffer error. I tried again, and it started ok but I never saw it actually finish flashing.
By this time I finagled the ROM zips onto the SD card and stopped the fastboot and booted into TWRP. I did another set of wipes, and rebooted into TWRP again. I flashed the CM and Gapps. The ROM booted fine from TWRP and I was able to start setting up my account again. I tried rebooting after the initial setup just to see if it was working correctly, and was met with the fastboot screen with fastboot reason: Flash failed. I rebooted into TWRP from there, and tried to boot normally, but it still brought me to the fastboot. I went to the boot menu and tried the normal boot selection, and now my phone is stuck on the Bootloader Warning screen and now it won't even turn off when I hold the power button.
I have no idea what is going on, or why I could get to the working ROM once but not again. Does anyone know anything that could help me?
Kopiok said:
I am on a Verizon Razr Maxx HD (xt926). This all started when I decided to cleanly flash the newest version of CM10.2. I had been running it before. I wanted to start from a blank slate, so I went into TWRP and did the format wipe. Installed the newest CM10.2 nightly and gapps. This went fine and I booted into the ROM and started recovering all of my stuff. I installed F-droid and AdAway, and rebooted for that. The phone never got past the Bootloader Unlocked warning screen. I turned it off and went into TWRP to try some things. I tried to fix permissions, but it failed, referencing something to do with fdroid. I wiped again and reinstalled CM, but I still couldn't get past the Bootloader Unlocked warning.
I booted into TWRP again and wiped what I could, and accidentally wiped my external SD, and I had no card readers lying around to get the ROM zips back onto it. I downloaded the Razr HD utility, used the batch file, and tried to flash the stock rom through fastboot, but it got stuck in some kind of loop and would not flash correctly. I then tried to do it manually, but got some sort of buffer error. I tried again, and it started ok but I never saw it actually finish flashing.
By this time I finagled the ROM zips onto the SD card and stopped the fastboot and booted into TWRP. I did another set of wipes, and rebooted into TWRP again. I flashed the CM and Gapps. The ROM booted fine from TWRP and I was able to start setting up my account again. I tried rebooting after the initial setup just to see if it was working correctly, and was met with the fastboot screen with fastboot reason: Flash failed. I rebooted into TWRP from there, and tried to boot normally, but it still brought me to the fastboot. I went to the boot menu and tried the normal boot selection, and now my phone is stuck on the Bootloader Warning screen and now it won't even turn off when I hold the power button.
I have no idea what is going on, or why I could get to the working ROM once but not again. Does anyone know anything that could help me?
Click to expand...
Click to collapse
Try the solution in the last few posts on this thread. http://forum.xda-developers.com/showthread.php?t=2465695
I hope you get more knowledgeable advice than mine but, were I in your situation, my primary goal would be to get back to STOCK. Forget CM and modding for now. Either through TWRP or through the recovery settings on the phone itself I'd get to where I could do a factory reset. If you're continuously able to boot into TWRP I don't see how your phone could be bricked. My experience is, if I can get a phone to do ANYTHING I've got a shot at figuring out how to get out of whatever mess I've created. I don't know if this could be a factor but I'd put in a different micro SD card too, in case there's something on the card you've got in there.
Just an update. So, I got it to go back to fastboot this morning and I tried using the Razr Utility to flash back stock and stock recovery, but I got a "Failed" line with the reason "Remote Failure". Not sure what that's about. When it reset it got back to the Cyanogenmod boot graphic, but it never started. I left it there for a good 12 minutes.
Right now it's sitting in TWRP. I'm going to let it charge to 100% (it was a little less when I tried all of this) and attempt it again at 100% battery. Thanks for the help so far!
So, I tried using the Razr Utility to flash the system, kernel, radio and for system it was unsuccessful (something about too many threads or strings, something to that effect), but the rest said OK. Now my phone doesn't seem to turn on. My computer still makes the device plugged in sound when it's plugged/unplugged, but I cannot get the screen to show anything or seem to turn on the phone.
Is this it? Is it... bricked!? ;-;
Edit: I ordered the Factory Adapter as a last resort sort of thing. This is lame.
Edit Edit: I've seen the boot logo since my last edit! But... it's not coming back and I still can't even bring up the bootloader. I don't know why it will sometimes turn on or sometimes not. In any case, I'm now hopeful that not ALL is lost.
Bottom line, the adapter will allow you to fix your phone and flash the stock FXZ in RSD Lite or fastboot and get back to a clean slate and start over.
That's why we went to the trouble of making them!
cellzealot said:
Bottom line, the adapter will allow you to fix your phone and flash the stock FXZ in RSD Lite or fastboot and get back to a clean slate and start over.
That's why we went to the trouble of making them!
Click to expand...
Click to collapse
That's the plan! One odd thing happening now... My phone's screen isn't showing anything, so I assumed it was off. I left it unplugged and went to see a movie..... and the phone is still warm. This leads me to believe the phone is still drawing power, for some reason... God this is weird. I'll wait for the adapter and try again. Thanks for the help!
cellzealot said:
Bottom line, the adapter will allow you to fix your phone and flash the stock FXZ in RSD Lite or fastboot and get back to a clean slate and start over.
That's why we went to the trouble of making them!
Click to expand...
Click to collapse
according to the packaging on mine from tbh a chinaman made it, just sayin
Yes, we designed them and contracted through our US supplier who produced all of our cables who, in turn, had them produced in China according to our specifications. There is no longer any injection molded plastic production done in the US that can work at this small scale for affordable rates.
Sorry...that's the way the world works these days.
cellzealot said:
Yes, we designed them and contracted through our US supplier who produced all of our cables who, in turn, had them produced in China according to our specifications. There is no longer any injection molded plastic production done in the US that can work at this small scale for affordable rates.
Sorry...that's the way the world works these days.
Click to expand...
Click to collapse
thanks for making it either way, better to have and not need.
havent had to use it so far
bweN diorD said:
thanks for making it either way, better to have and not need.
havent had to use it so far
Click to expand...
Click to collapse
You're welcome! They are definitely the best $10 investment you can make in any Motorola phone.
Next time you want to invest many thousands of dollars of your own money in a wild, hairbrained scheme to help a bunch of anonymous people on the internet fix their phones that they recently finished destroying themselves, let us know...we have just the plan!
cellzealot said:
You're welcome! They are definitely the best $10 investment you can make in any Motorola phone.
Next time you want to invest many thousands of dollars of your own money in a wild, hairbrained scheme to help a bunch of anonymous people on the internet fix their phones that they recently finished destroying themselves, let us know...we have just the plan!
Click to expand...
Click to collapse
how many thousands, and whats the plan?
I got the Factory Adapter and used RSD Lite to flash stock. And it works! Yay! It's starting up reliably and everything.
Except... it won't start up without the cable attached, and the battery icon has a big question mark on it. It also won't connect to the cell network (but does connect to WiFi). What do I do now?
Edit: So I noticed that while the battery status said "Unknown", it did go from 2% to 3% charge level when I plugged it in normally for a little. My plan at the moment is to try leaving it plugged in for a while and then try taking the OTA update to see if that fixes everything. Good plan?
Edit Edit: Never mind! I just had to let it charge for a bit. It seems to be back in working order, now! Thank you so much for all the help everyone!
That is exactly what is supposed to happen. Congrats on fixing your phone!
The factory cable/adapter does not charge the device but powers it directly, allowing it to boot no matter what state the battery is in or even without a battery at all.
You cannot charge in bootloader, which is why the cable/adapter is so valuable. Once the device can boot/charge normally then you are all set.
Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!
kyle313 said:
Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!
Click to expand...
Click to collapse
Did you try flashing factory images?
ryukiri said:
Did you try flashing factory images?
Click to expand...
Click to collapse
Yeah, that was what I flashed :/
If you can get into fastboot you "should" be able to flash stock images... Obviously this will revert any root and you will need to flash TWRP/CWM recovery after.
I assume you have a Windows PC with fastboot/adb setup and all drivers etc..
- Download latest "stock" hammerhead images (I cannot post links due to XDA rules... so: "developers.google.com/android/nexus/images#hammerhead"
- Extract the .tgz archive contents on your PC into a folder
- Boot the N5 into fastboot and plug USB cable from phone into your PC
- Go to the folder with the extracted files and run the "flash-all.bat" script on Windows
**Hopefully at this point your device will start to respond.. I.e, on fastboot screen, at the bottom you will see "writing" or something, as the script runs on the command window on your PC.**
If this works, you should be able to reboot once complete and then wait to see if you can get back into your phone.. then you can fastboot again and flash custom recovery, and then whatever rom.
If however you have a hardware issue (i.e, even after the above process it fails) then I am not sure what you could do... I guess ensure it has a complete charge. If you can get into fastboot and the buttons are responsive then it should not be a faulty power button.
Hope this helps :good:
Have you tried a simple factory reset? Reason I ask is it was working fine so sounds like something needs "flushing out" clear cache etc.
kyle313 said:
Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!
Click to expand...
Click to collapse
Did you choose the right model and firmware before you flash in WugFresh NRT?
The above could be right, however when I've used it, it's pointed out if I made that mistake. Having used his software dozens of times I've found it will bring any Nexus 5 back to life.
howard bamber said:
The above could be right, however when I've used it, it's pointed out if I made that mistake. Having used his software dozens of times I've found it will bring any Nexus 5 back to life.
Click to expand...
Click to collapse
Hello! I am apologize for that I didn't read the OP carefully. This happened to me once in that particulary way, but it was immediately after flashing. OP says that it happened suddenly, without reason. So now I am the one, who doesn't read, right? Sorry for that.
Regards, Zagor
Thanks for the responses, but I'm still having trouble.
I have been able to successfully write the newest stock android 3 times (1 without full wipe, 2 with) and the phone still can't boot up and goes through one of the three issues above.
I've also been able to get to the system recovery from the bootloader and I've tried wiping the cache and doing a factory reset from there and the problem remains.
I'd contact google, but I bought it at launch so I don't think they'll do anything for me since it's been 1+ years.
kyle313 said:
Thanks for the responses, but I'm still having trouble.
I have been able to successfully write the newest stock android 3 times (1 without full wipe, 2 with) and the phone still can't boot up and goes through one of the three issues above.
I've also been able to get to the system recovery from the bootloader and I've tried wiping the cache and doing a factory reset from there and the problem remains.
I'd contact google, but I bought it at launch so I don't think they'll do anything for me since it's been 1+ years.
Click to expand...
Click to collapse
Sounds like you have a bad nand sector. From fastboot try:
Code:
fastboot oem lock
Then reboot into fastboot and check if it's locked or not. If the device isn't locked your emmc is corrupt and there is nothing you can do. If that is the case call Google and they will most likely help you out with a RMA.
theesotericone said:
Sounds like you have a bad nand sector. From fastboot try:
Code:
fastboot oem lock
Then reboot into fastboot and check if it's locked or not. If the device isn't locked your emmc is corrupt and there is nothing you can do. If that is the case call Google and they will most likely help you out with a RMA.
Click to expand...
Click to collapse
I was actually able to relock the phone.
Luckily I called google and they're going to send me a replacement.
If anyone else has any other ideas, I'll still take them...I'd rather not be without a phone for the next week!
You won't be without a phone - they are sending a refurbish unit to you , putting a block on your credit card and waiting for you phone to arive at them. Once that happens they will release the funds.