Hey Folks,
So I've noticed on several ROMs I've tried as of late that I seem to be randomly losing internet connection. Basically, everything will be fine, phone goes to sleep. When I turn it back on the WiFi signal is full but grey as though it has no internet. Generally, if I turn it off and back on it works, sometimes I need to reboot my phone entirely if it doesn't come back up. I've searched through all the Power Management settings, and I think I have them all set to not manage wifi, or turn it off, or use it in low power mode, etc. But there has to be either something I am missing or a real issue with WiFi drivers or something. has anyone else seen this kind of behavior?
~RickoT
Almost 300 views and no responses? Is no one else experiencing this kind of behavior?
What ROM are your using? R u s-off and what kernel u had. without those it's hard to pin point and maybe that's y u have no reply.
cat2115 said:
What ROM are your using? R u s-off and what kernel u had. without those it's hard to pin point and maybe that's y u have no reply.
Click to expand...
Click to collapse
I am having an issue with my mobile internet. Everything will be fine on wifi, but when I leave the wifi area I will have full bars and say I am connect to mobile internet, but I will get no connection error in every app. I have noticed sometimes that if I get an edge signal and try go back to H H+ it happen. It is sporadic and hard to pin point when it happens and what is causing it.
I am s off h boot 1.06 on pacman. Now this has only happened in the last few updates of pacman, and i have been talking to the developer, but it seems like i am the only one having the problem. Any help is greatly appreciated.
Note: Doing this delete everything on your phone, So backup
oh sorry i can't help cuz i;m not on PAC MAN. Maybe try to re-flash the ROM with a full wipe in twrp-->wipe cache, wipe dalvik cache, wipe system, & wipe factory reset. Maybe do it 3x. But as u know, this will erase all ur apps. If that still not working, it's better to run US T-Mob JB RUU. This will fix all your issue. Don't worry, u will still be S-off and BL unlock.
If u plan to run RUU, this is what i do and always success:
1. Make sure phone is on USB debugging
2. On cmd, type adb reboot-bootloader
3. Run RUU
4. When finish, do your normal phone setup, then go into Setting-->restore&backup-->Reset Phone and put check mark on Erase Everything
5 when done, do your normal phone setup and turn ON USB debugging
6. On cmd, type adb reboot-bootloader
7. on cmd type: fastboot flash recovery TWRP.img I use twrp v2.3.3.0
8. on cmd tyoe fastboot flash recovery TWRP.img again
9. Your done and flash any ROM u wish and see if the issue go aways.
Hey folks,
So I've noticed this on several roms, Currently I am using LiquidSmooth 2.3.1. But I have noticed it with the last 5 or 6 roms I've tried. I also tried restoring to the latest RUU, flashing the latest TWRP and going from there. I've even gone as far as getting the latest mutli-radio installer and trying several different radios, but in the end I experience the same kind of issue.
~Rick
i though it was just me that had this problem
Im on t mobile and since the firmware update I started having this problem no matter what Rom I tried sence and cm, my signal would disappear completly at times and the settings would show service is unavailable next to the radio at times when it was bad even in good coverage areas, any way this is what worked for me
1.- I changed the svn value on the bulid prop from 19 to 1, left the other ones alone (24,6,4)
2.- I made sure the build prop had the fallowing propperty "ro.ril.disable.power.collapse" and the value set to 0
3.-when I see service unavailable I swith airplane mode on and than off
4.-don't forget to thank me if I helped u even just a bit
cat2115 said:
Note: Doing this delete everything on your phone, So backup
oh sorry i can't help cuz i;m not on PAC MAN. Maybe try to re-flash the ROM with a full wipe in twrp-->wipe cache, wipe dalvik cache, wipe system, & wipe factory reset. Maybe do it 3x. But as u know, this will erase all ur apps. If that still not working, it's better to run US T-Mob JB RUU. This will fix all your issue. Don't worry, u will still be S-off and BL unlock.
If u plan to run RUU, this is what i do and always success:
1. Make sure phone is on USB debugging
2. On cmd, type adb reboot-bootloader
3. Run RUU
4. When finish, do your normal phone setup, then go into Setting-->restore&backup-->Reset Phone and put check mark on Erase Everything
5 when done, do your normal phone setup and turn ON USB debugging
6. On cmd, type adb reboot-bootloader
7. on cmd type: fastboot flash recovery TWRP.img I use twrp v2.3.3.0
8. on cmd tyoe fastboot flash recovery TWRP.img again
9. Your done and flash any ROM u wish and see if the issue go aways.
Click to expand...
Click to collapse
thanks I think i will try this, but i am noobish and never dealt with a ruu, and don't really know what it is. Is it a file I need? if so where can i dl it?thanks again.
Well its good to see that other people are having this issue ( I thought for a while it was just an issue with my phone ), I wonder if there is something wrong with the base image that people are using to create these ROMS
If the problem happens between midnight and 7 a.m., it's normal. The connection (both 3g and wifi) gets cut after 20 minutes.
nor-ric said:
If the problem happens between midnight and 7 a.m., it's normal. The connection (both 3g and wifi) gets cut after 20 minutes.
Click to expand...
Click to collapse
I have never had this happen before on any other phone. Is this something exclusive to the One S? Is there anywhere to disable this?
Also, it happens during the day as well, just not as frequently
?
I have never had that problem either in fact its past midnite and check out the screen capture
Search for htc smartsync and you'll find what I'm tallking about. The connection (3g and wifi) gets cut with the screen off for 20 minutes during night time (midnight - 7 a.m.). This can be disabled but it needs root.
If your problem is not related to night time, forget about this.
ok ill check it out
Now check outy latest screen capture
Actually I had already checked that screenshot but I couldn't get the meaning. lol The connection gets cut only with the screen off. As soon as you turn the screen on it reengages both 3g and wifi connection. You can see this happen because as soon as you turn the screen on (after 20 minutes off) there will be no 3g and wifi icon: after 1-2 seconds they'll pop up again.
Am I missing something with your speedtest? Of course it works, you are with the screen on! lol
o
Damn your right I can't prove the internet stays on with this, it does stay on do I now this because I have downloaded large files recently like TD10 and some others and the progress doesn't slowdown when the screen is off, how can I prove this?
Ice Master Ben said:
Damn your right I can't prove the internet stays on with this, it does stay on do I now this because I have downloaded large files recently like TD10 and some others and the progress doesn't slowdown when the screen is off, how can I prove this?
Click to expand...
Click to collapse
Wait for midnight, enable push mail (if not already enabled), wait 20-25 minutes (with screen off) and send an email to yourself from the pc.
If you receive a call or if the screen turns on for any other reason during the 20-25 minutes, start all over again! lol
Related
Ok be prepared, this post may be rather long winded however I will try my best to prevent that. I have a Tmobile G2x I purchased on launch date. Ive not attempted to Root, change roms, or anything of the sort. (as much as I always wanted to, I always felt that my skills were not good enough to attempt these ideas no matter how easy they may seem. I just did not want to be the cause of screwing up my phone that I paid dearly for)
So I have a friend who claims to be the master (of disaster so it turns out) of rooting androids and such. He stops by my house just to hang out and eventualy convinces me to let him root my phone and install CM7. Within a few minutes the phone was rooted (super1click) and was running CM7 release candidate. (I really dont know what all these things truly are but I drilled him for answers once he jacked up my phone and left me with a half-bricked phone) So he installed Rom manager and convinced me to upgrade to the premium version via marketplace so I did. He was then showing me how easy it was to flash new roms at the touch of a few buttons. He put on some other rom which looked like CM7 but claimed to have extra tweaks. It worked fine. A few minutes later he put on some Faux Rom which gave a boot up screen like my old Nexus One did. (Multicolored X) It seemed to work fine as well. Then he said lets check out the nightly CM7 Rom so he put it on. (however I dont think it ever actually put CM7 back on.-still on Faux?) Thats when things got crazy.
Now I get the com.google.process.gapps force close message all the time. He tried to fix it for 4 hours and finally gave up. Here is what I know he/we tried: After searching the internet for hours we tried everyone elses ideas. Clearing calenders cashes, un syncing, etc. We did about 40 factory resets. We have tried to install my backup (which was from BEFORE he even touched my phone) and upon holding both volume rockers and plugging in USB (no battery installed) and it still does nothing. Windows recognizes device but phone screen stays black. Tried Debug mode while doing this as well. If we hold the volume down button and power the little install bar comes on the screen and it does its thing (whatever that is) and goes right back to the way it was. I keep getting the gapps message all the time. After factory reset I cant even type in my gmail address to start the initial setup of the phone. The force close keeps cutting me off. If I type fast, I can sync the account but I cant use market whatsoever. Tried installing Rom manager to re-flash but just sticks at starting download and gapps pops up again.
My son is starting school tomorrow and he has a medical condition. I NEED this phone to communicate with the school nurse via emails and such. As of now I can only text, call, or surf web all while dodging force closes. If ANYONE out there can please help me get my phone back to normal Id greatly appreciate it. Im sure its something easy but as I said before, Im not good at this thing and thats why I never attempted it myself. Your welcome to submit answers here or PM me your phone # if you want to walk me through it on the phone. (I have a landline phone to talk to you on) Thanks in advance for everyones time and Im sorry this ended up being so long.
Download latest Gapps.zip from Cyanogen site to your phone's SD card, boot into recovery, wipe data and cache then flash the Gapps.zip file. Let me know if this helps.
I will try this now. Thank you
Im unable to get anywhere. It still has stock recovery and I cannot get to the screen where I can wipe. Im not great at this sort of thing but Im trying.
Omnichron said:
Download latest Gapps.zip from Cyanogen site to your phone's SD card, boot into recovery, wipe data and cache then flash the Gapps.zip file. Let me know if this helps.
Click to expand...
Click to collapse
i think you would be better off starting from scratch
1. remove your sd card from your phone and plug it in your computer
2. download the latest rom here
3. download gapps from the download links at the bottom of this page
4. transfer both files onto the sd card and put it back into your phone.
5. with your phone off, boot your phone into recovery by holding vol down+power
6. wipe data, cache, and dalvik cache
7. flash only the cm7 file
8. reboot normally
9. reboot into recovery
10. flash gapps
11. reboot normally
after you flash one file, it is highly recommended that you reboot before you flash another file (if your friend didnt do this, this may have been the problem)
HurtsBad said:
Im unable to get anywhere. It still has stock recovery and I cannot get to the screen where I can wipe. Im not great at this sort of thing but Im trying.
Click to expand...
Click to collapse
to flash custom recovery, use this (method two on the page)
EDIT: original post (http://forum.xda-developers.com/showthread.php?t=1056847)
Thank you guys for all your help. The instructions helped me out. Im very thankful. I can now rest better knowing that my sons school nurse can contact me if needed. Have a great night.
no more force closes? sounds good
feel free to post again if you have any more problems
sweetnsour said:
i think you would be better off starting from scratch
1. remove your sd card from your phone and plug it in your computer
2. download the latest rom here
3. download gapps from the download links at the bottom of this page
4. transfer both files onto the sd card and put it back into your phone.
5. with your phone off, boot your phone into recovery by holding vol down+power
6. wipe data, cache, and dalvik cache
7. flash only the cm7 file
8. reboot normally
9. reboot into recovery
10. flash gapps
11. reboot normally
after you flash one file, it is highly recommended that you reboot before you flash another file (if your friend didnt do this, this may have been the problem)
Click to expand...
Click to collapse
....touché
A long time ago I rooted my phone and put CM9 on it. I decided I wanted to go back and try Jelly Bean (from factory then go outwards).
I had a difficult time with the CM flash and found one that worked, and thought I was good to go.
My phone: gt-i9020a nexus s
Product name: Herring
HW version 16
boot loader: i 9020xxkl
carrier att
fastboot enabled
unlocked state.
I can launch the official 2.3.6 (Build GRK39F), from google
then the OTA updated kicks in and the phone is stuck at 'boot' Google logo on the screen.
I have done the information below and the same keeps happening...
link: http://forum.xda-developers.com/showthread.php?t=1586845
first of all, the VQ8PQk is a patch file, not a full rom. So flashing that on something else than 2.3.6 will never work. Get into clockworkmod recovery wipe wverything from the mounts and storage menu, and then flash this file : http://android.clients.google.com/pa...o/ZD3PyN0t.zip and THEN this : http://android.clients.google.com/pa...o/hR7QFEtn.zip
and other steps I could try to work around, none of them seem to work.
Am I missing anything?
Thanks!
Use the full factory rom images (sojuaxxxx) from Google.
https://developers.google.com/android/nexus/images#sojua
Follow the instruction on that page (scroll up). If using Windows, use 7zip (or similar util) to expand the .tgz file, open content of "flashall.sh" and execute the commands one at a time.
Code:
fastboot flash bootloader bootloader-crespo-i9020xxlc2.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020uckj1.img
fastboot reboot-bootloader
fastboot -w update image-sojua-jro03e.zip
The last command will wipe all data and install new 4.1.1 rom.
Edit: install CYGWIN to have linux-like commands (works with tar, adb, fastboot) in windows.
Do you have a backup (preferrably CWM backup) that you have prior to trying to get JB working? If so keep that handy, and preferrably store it on the PC. Titanium backup can ease migrating apps after a wipe and is highly recommended, so do one of these too if you havn't already.
After you make sure you have a solid backup with the information that you want/need on the phone, i would just start fresh. The best way to do this is to do a factory image flash (note: you want sojua if you have the 850MHz variant which is from AT&T). Flashing these will wipe all user data and the /system partition, the sdcard won't be touched. Basically you download it, extract it, then hook up your phone in fastboot mode and do the commands as written in the text file (or run it as a script if you know how). I've described it in more detail elsewhere as have others, doing a search should give results pretty quickly
This will become a factory install of android as given by google, in your chosen version. I'd go straight ot JB and then you can see how much you like it. CWM backup data can be extracted if you lost some crucial information in the flashing and all your apps and their data can be easily restored with titanium backup.
morning update
_android_ said:
Use the full factory rom images (sojuaxxxx) from Google.
Follow the instruction on that page (scroll up). If using Windows, use 7zip (or similar util) to expand the .tgz file, open content of "flashall.sh" and execute the commands one at a time.
Code:
fastboot flash bootloader bootloader-crespo-i9020xxlc2.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020uckj1.img
fastboot reboot-bootloader
fastboot -w update image-sojua-jro03e.zip
The last command will wipe all data and install new 4.1.1 rom.
Click to expand...
Click to collapse
running linux, no cygwin needed
did this again this morning..and i'm stuck on the google boot screen with the unlocked padlock on the bottom.
how long should this run (20 minutes now)
I have tried the roms from that page, the 2.3.6 is the only rom that I was able to get working..
lost_man said:
running linux, no cygwin needed
did this again this morning..and i'm stuck on the google boot screen with the unlocked padlock on the bottom.
how long should this run (20 minutes now)
I have tried the roms from that page, the 2.3.6 is the only rom that I was able to get working..
Click to expand...
Click to collapse
Make sure you use the sojua versions.
Do you mean you finish all the steps and upon reboot, it's stuck on Google boot screen?
What do you mean by you can only get 2.3.6 working? It went past Google boot screen?
** ran 'flash-all.sh" see if that changes anything, nothing like a script to rule out human error.***
**** that was a mistake...now phone is not turning on, the screen is dead...when i plug in USB chord, nothing is detected no state change on the phone. When I press buttons no state change nothing changes on the screen. I actually think my phone is a true brick, not a software glitch that is fixable....any suggestions now? ****
lost_man said:
** ran 'flash-all.sh" see if that changes anything, nothing like a script to rule out human error.***
**** that was a mistake...now phone is not turning on, the screen is dead...when i plug in USB chord, nothing is detected no state change on the phone. When I press buttons no state change nothing changes on the screen. I actually think my phone is a true brick, not a software glitch that is fixable....any suggestions now? ****
Click to expand...
Click to collapse
Some (quite a few) Nexus S seemed to be vulnerable to Jelly Bean/CM10 update in that the mainboard is toast. I think the only option is to send back for warranty repair. There are some threads on rigging some kind of adapter cable but that will definitely void your warranty (physical mod).
Doesn't sound good, there have been instances where the flash storage has given up and ends up needing a new SoC (the whole mainboard) and similar issues. Some more information would be good to diagnose this better though.
-Take the battery out for 5 minutes, place back in, can you get into fastboot?
-Can you flash recovery and radio? Can you enter recovery?
-After the "fastboot -w update ...." command, what messages do you see on the phone (at the bottom)?
If you can't get the phone to turn on at all after a good 5 minutes without the battery inserted, give AdamOutlers resurrector a shot. A nice phone call to samsung might be a good idea if you're still within 12 months of purchasing. Hopefully it all turns out okay.
-Take the battery out for 5 minutes, place back in, can you get into fastboot?
-Can you flash recovery and radio? Can you enter recovery?
-After the "fastboot -w update ...." command, what messages do you see on the phone (at the bottom)?
If you can't get the phone to turn on at all after a good 5 minutes without the battery inserted, give AdamOutlers resurrector a shot. A nice phone call to samsung might be a good idea if you're still within 12 months of purchasing. Hopefully it all turns out okay.
Click to expand...
Click to collapse
Did all of the above, nothing. adamoutliers does not see a device connected.
lsusb shows nothing
dmesg shows my device disconnect, after the failed boot, no reconnect.
I'm headed out for a few hours, I will leave battery out, and phone disconnected but i'm thinking it's toast. Att will send an RMA phone to me, they gave me a choice of samsung focus (I asked how a windows phone was similar to an android?) or a samsung galaxcy II skyrocket...I'll try samsung next..
Thanks for all the help!
lost_man said:
Did all of the above, nothing. adamoutliers does not see a device connected.
lsusb shows nothing
dmesg shows my device disconnect, after the failed boot, no reconnect.
I'm headed out for a few hours, I will leave battery out, and phone disconnected but i'm thinking it's toast. Att will send an RMA phone to me, they gave me a choice of samsung focus (I asked how a windows phone was similar to an android?) or a samsung galaxcy II skyrocket...I'll try samsung next..
Thanks for all the help!
Click to expand...
Click to collapse
How do i close this thread? It's done, the phone is dead...rma...
My nexus s keeps booting up like normal but then once it gets to my lock screen it shuts off by itself within 5 seconds. Sometimes I manage to put my password in and get onto my main screen but that's as far as I can get before it shuts off again. This continues repeatedly till the battery dies, turning on and shutting off by itself. This has been going on for 2 days now, since my phone died while at work and got home and charged it. When I took it off the charger when it showed a full charge it started happening, turning on and shutting off by itself and when the phone would turn on it would show low battery. As you may know this phone only has internal memory (no memory card slot). So what I'm trying to do is get my pictures and videos off of the internal memory before I do a hard reset which is what the sprint repair store told me was my only option to fix the phone but I would lose everything on there and there's absolutely no way to recover my pics and videos cuz the phone doesn't stay on long enough. Does anyone have any suggestions at all on how I could fix my phone WITHOUT doing a hard reset? I'm hoping to not lose these precious memories so I'd like to keep that as a very, very last resort. Any suggestions would be helpful and very much appreciated...
diamondrl1 said:
My nexus s keeps booting up like normal but then once it gets to my lock screen it shuts off by itself within 5 seconds. Sometimes I manage to put my password in and get onto my main screen but that's as far as I can get before it shuts off again. This continues repeatedly till the battery dies, turning on and shutting off by itself. This has been going on for 2 days now, since my phone died while at work and got home and charged it. When I took it off the charger when it showed a full charge it started happening, turning on and shutting off by itself and when the phone would turn on it would show low battery. As you may know this phone only has internal memory (no memory card slot). So what I'm trying to do is get my pictures and videos off of the internal memory before I do a hard reset which is what the sprint repair store told me was my only option to fix the phone but I would lose everything on there and there's absolutely no way to recover my pics and videos cuz the phone doesn't stay on long enough. Does anyone have any suggestions at all on how I could fix my phone WITHOUT doing a hard reset? I'm hoping to not lose these precious memories so I'd like to keep that as a very, very last resort. Any suggestions would be helpful and very much appreciated...
Click to expand...
Click to collapse
Bootloop... You flashed something wrong, modded/tweaked something wrong or overclocked and it wasn't stable... You need to go into recovery and do a CLEAN install of your rom and/or kernel.. if you used a mod/tweak this could have caused it... If overclocking DO NOT check to keep the settings after a reboot unless you are sure that these settings are stable..
Setting.Out said:
Bootloop... You flashed something wrong, modded/tweaked something wrong or overclocked and it wasn't stable... You need to go into recovery and do a CLEAN install of your rom and/or kernel.. if you used a mod/tweak this could have caused it... If overclocking DO NOT check to keep the settings after a reboot unless you are sure that these settings are stable..
Click to expand...
Click to collapse
im not sure what exactly i did but i havent changed anything from what originally came with the phone. (im still running on gingerbread) i had my phone on airplane mode so my battery wouldnt die while i was at work and somehow my phone died anyway then i put it on the charger when i got home and let it charge fully then turned it on and from the time i turned it on till now its been shutting off and turning on by itself. i guess the repair store told me its recycling itself?
diamondrl1 said:
im not sure what exactly i did but i havent changed anything from what originally came with the phone. (im still running on gingerbread) i had my phone on airplane mode so my battery wouldnt die while i was at work and somehow my phone died anyway then i put it on the charger when i got home and let it charge fully then turned it on and from the time i turned it on till now its been shutting off and turning on by itself. i guess the repair store told me its recycling itself?
Click to expand...
Click to collapse
Try booting into recovery.. Volume + and Power.. use the volume keys to scroll and power to enter.. the menu has an option for recovery (this does not do anything to your phone).. You may see a dead android,.. DON'T PANIC.. this is perfectly normal, you didn't break anything.. try pressing the volume up, then power, wait a sec and do it again.. (I always had an issue with the "stock recovery") the phone may power off or try to reboot.. (been a while, kinda fuzzy on this).. be persistent and keep retrying the fore mentioned steps and you should get a recovery menu.. Phew... Now the sad bit, you don't have any files you need on your phone.. I don't know if the stock recovery works with usb mounting, but it might.. try it.. if it does then download a custom recovery, I suggest the one in my signature, and copy from computer to phone using the usb.. in the recovery menu, after the transfer is complete, go to install / install from sd / choose the zip that you just put on your sd card / accept / and if you get this far then.. Reboot recovery, don't worry, nothing broken (yet).. lol.. In your new recovery, assuming it's the one I said, go to the advanced menu, (this is a touch version, so you don't need to use the volume keys) and select "fix permissions".. ... .. and reboot.. WORKED???
All is not lost (yet).. try wiping (ONLY) cache and dalvik(under advanced menu).. and reboot.. WORKED??
Okay, so if you are reading down here, either you are bored, or the above steps failed..
Use this program, read the forum as well..
http://forum.xda-developers.com/showthread.php?t=1766475
You can keep your phone 100% stock, but you'll need to unlock it to fix it, then you can lock it back up if you'd like.. Not necessary though.. You might think about just installing a custom rom or upgrading to jb.. OOooh the possibilities..
But here's the problem, remember the (yet).. if you have come this far down in steps to restore your phone..
ALL YOUR DATA WILL BE LOST!!!
was sianlog
Setting.Out said:
Try booting into recovery.. Volume + and Power.. use the volume keys to scroll and power to enter.. the menu has an option for recovery (this does not do anything to your phone).. You may see a dead android,.. DON'T PANIC.. this is perfectly normal, you didn't break anything.. try pressing the volume up, then power, wait a sec and do it again.. (I always had an issue with the "stock recovery") the phone may power off or try to reboot.. (been a while, kinda fuzzy on this).. be persistent and keep retrying the fore mentioned steps and you should get a recovery menu.. Phew... Now the sad bit, you don't have any files you need on your phone.. I don't know if the stock recovery works with usb mounting, but it might.. try it.. if it does then download a custom recovery, I suggest the one in my signature, and copy from computer to phone using the usb.. in the recovery menu, after the transfer is complete, go to install / install from sd / choose the zip that you just put on your sd card / accept / and if you get this far then.. Reboot recovery, don't worry, nothing broken (yet).. lol.. In your new recovery, assuming it's the one I said, go to the advanced menu, (this is a touch version, so you don't need to use the volume keys) and select "fix permissions".. ... .. and reboot.. WORKED???
All is not lost (yet).. try wiping (ONLY) cache and dalvik(under advanced menu).. and reboot.. WORKED??
Okay, so if you are reading down here, either you are bored, or the above steps failed..
Use this program, read the forum as well..
http://forum.xda-developers.com/showthread.php?t=1766475
You can keep your phone 100% stock, but you'll need to unlock it to fix it, then you can lock it back up if you'd like.. Not necessary though.. You might think about just installing a custom rom or upgrading to jb.. OOooh the possibilities..
But here's the problem, remember the (yet).. if you have come this far down in steps to restore your phone..
ALL YOUR DATA WILL BE LOST!!!
Click to expand...
Click to collapse
mentioning unlocking my phone... i did come across a menu that was a "unlock bootloader". but it said i would have to do a factory data reset...wouldnt that wipe my memory completely?
diamondrl1 said:
mentioning unlocking my phone... i did come across a menu that was a "unlock bootloader". but it said i would have to do a factory data reset...wouldnt that wipe my memory completely?
Click to expand...
Click to collapse
The first steps won't.. if you get to the unlock stage then yes.. As long as you keep it locked, you'll be fine.. If it won't let you flash a custom recovery, you can try the above steps in the stock...
Setting.Out said:
The first steps won't.. if you get to the unlock stage then yes.. As long as you keep it locked, you'll be fine.. If it won't let you flash a custom recovery, you can try the above steps in the stock...
Click to expand...
Click to collapse
sorry to keep bugging you... so i downloaded your recovery file... im not really sure what to do next since my phone doesnt stay on long enough to transfer the file from my comp to my phone.. apologizes again.. im not really tech savvy as you might have figured out :laugh:
diamondrl1 said:
sorry to keep bugging you... so i downloaded your recovery file... im not really sure what to do next since my phone doesnt stay on long enough to transfer the file from my comp to my phone.. apologizes again.. im not really tech savvy as you might have figured out :laugh:
Click to expand...
Click to collapse
Won't stay on, or the screen turns off.. ?? does the computer give a pop-up message saying that you had an issue when copy/pasting the file to the phone..??
Remember that we are working from recovery, not with the phone fully booted into your android os..
Setting.Out said:
Won't stay on, or the screen turns off.. ?? does the computer give a pop-up message saying that you had an issue when copy/pasting the file to the phone..??
Remember that we are working from recovery, not with the phone fully booted into your android os..
Click to expand...
Click to collapse
my comp isnt picking up my phone via usb...
update: now my phone isnt turning on at all, even when plugged in to charge or via usb... so does that mean im out of luck now..?
My nexus s has the same issue
brethren, I am sorry to drop in on the discussion like this but I don’t know where to get an answer from. My Nexus S (phone) has had a problem recently, it just keeps on turning on and off and mentions the “type password to decrypt storage”, if it remains on. I tried to factory reset the phone through the steps mentioned in the blog here:
1. Power off
2. Hold Volume + , volume - and power
You should get a green android image with the body opened with "Start" on the screen
3. Press Down till you get to recovery mode
4. Press power
Phone will reboot. You will then get same image of android (smaller) with red warning triangle
5. Wait a minute or two and then press volume + and power (not sure exactly what I did for this maybe it's just waiting)
6. Use volume down to select wipe data/factory reset and hit power
Select Yes - delete all user data and hit power
7. Once done select reboot system now and hit power
You are now back to zero and can start again
But it does not work. I will be obliged if someone helps me out
Thanks
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.
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.