Ever since the Jelly bean update my battery life has been awful. This issue isn't happening all the time however, a restart seems to resolve the issue. When my battery drains really fast Android OS is using anywhere from 30%-50%.
Anyone else having this?
richport29 said:
Ever since the Jelly bean update my battery life has been awful. This issue isn't happening all the time however, a restart seems to resolve the issue. When my battery drains really fast Android OS is using anywhere from 30%-50%.
Anyone else having this?
Click to expand...
Click to collapse
Have you tried to Wipe Data and Cache???? (Not through configuration, inside android. Wipe data and cache turning your phone on with 'vol +' and 'vol -' pressed.) When you see the black screen with white letters, scrool down using 'vol -' to 'RECOVERY' and press 'vol +' to select. When the green android appears, press 'vol +' and 'vol -' at the same time and you will have the option to wipe data and cache.
Then, reboot your phone and it will start as a new phone with jelly bean.
I saw a significant difference on my phone after this.
=p
zilian28 said:
Have you tried to Wipe Data and Cache???? (Not through configuration, inside android. Wipe data and cache turning your phone on with 'vol +' and 'vol -' pressed.) When you see the black screen with white letters, scrool down using 'vol -' to 'RECOVERY' and press 'vol +' to select. When the green android appears, press 'vol +' and 'vol -' at the same time and you will have the option to wipe data and cache.
Then, reboot your phone and it will start as a new phone with jelly bean.
I saw a significant difference on my phone after this.
=p
Click to expand...
Click to collapse
Are you rooted, and if so, did you maintain root? I was looking at the build.prop file and noticed a comment that one of the props is to allow the mounting of /system on the data partition which implies that it could be an image on the data partition or block of the data partition. I would like to wipe my data and cache so long as it didn't reinstall the entire OS causing me to lose root.
PantsDownJedi said:
Are you rooted, and if so, did you maintain root? I was looking at the build.prop file and noticed a comment that one of the props is to allow the mounting of /system on the data partition which implies that it could be an image on the data partition or block of the data partition. I would like to wipe my data and cache so long as it didn't reinstall the entire OS causing me to lose root.
Click to expand...
Click to collapse
Actually I'm on ICS rooted. But I know that if you wipe data and cache on JB, unfortunately ur gonna loose root. =/
I read people saying that there is a file that if you clear its data, everything gets back to normal and the battery drain stops. I just don't remember which one is. Do a little search here at the forum that you will find. =]
Thanks for both replies; the answer and the instructions.
I'm about to take the leap into the uncertainties surrounding an unlocked boot-loader, I think. Its been inevitable at some point, I guess...
It turns out that I'm one of the incredibly lucky ones. It wiped my internal sd but su was unaffected. All my rooted apps, except for a modifiaction to build.prop, a backup of build prop, and the su binary, were simlinked into root from a folder in data which I can restore from the tarball I'de made. The symlinks are still there, as was the modification to build.prop which meant I had no buttons at the bottom of the screen to start with. Perhaps because of this; no extra apks detected or something, and with the supersu.apk on data. I don't know if having the reinject root option of supersu previously checked mattered or not. In any case, bootloader still locked and everything wiped. Now I have to put it all back to how it was but that was a given, either way.
This had nothing to do with the rootkeeper app btw. When I installed it, it still had the same settings as prior; didn't have re-insert root or anything.
Sorry for posting a useless comment since I don't know what made my situation differant than what other people have had happen, keeping the binary but losing proper file permissions on it from what I had read last night, but I'm happy that it worked out for me and telling my wife would be futile.
Also, I cleared cache and did a wipe data/system restore... twice. The first time, I made it most of the way through the initial Android setup and it popped me back a few selections; opting not to enable to turn on Google+ and then the screen flickered and it pulled me back to entering my Google account again so I powered off and did the clear cache and wipe again. What luck!
Bringing this thread back. Lately I've been getting some poor battery life on my maxx HD. I used to be able to get through the day with around 50% battery left at the end of the night. Now that number has been steadily decreasing over time. Does the recovery method mentioned also wipe my apps? I would love to finally root the phone to remove all the crapware but everything seems to be for the 925 and not the 926.
Sent from my DROID RAZR HD using Tapatalk 2
Related
Sorry if this is the wrong place to post this. I had to unroot my work phone because my firm said the servers identified my phone as having an operating system not supported by our security system and they suspended my server access.
So I uninstalled most of the "root" apps, thawed all the bloatware I froze in Titanium, disabled all the crap in Startup Auditor and then unrooted with Z4root. It literally took a minute for Z4root to unroot the phone.
I then brought my phone to IT to do a factory reset/wipe with one of our IT people so they can put me back on the server and I took my phone back.
The problem is whenever I start my phone, I get the Clockwork Mod screen (see attached). FYI I did not delete Bootstrap just in case I needed to restore for some reason.
BTW I did wipe data/factory reset in Bootstrap and when I rebooted the screen still came up and I'm definitely not rooted since immediately after unrooting with Z4root, Superuser was gone and Titanium said I didn't have root.
Any thoughts how to get rid of Bootstrap?
Thx!
The easy way is to flash SBF. The hard way is to root again and manually remove the bootsrap point. Then unroot again. SBF is much faster and convenient. Edit: much faster no - but much more convenient yes
Edit: if you want to go the long way, once you rooted again from PC mount system in RW mode, delete /system/bin/logwrapper then rename /system/bin/logwrapper.bin to /system/bin/logwrapper. Reboot and custom recovery should be gone. Unroot with Z4root and you are done.
leobg said:
The easy way is to flash SBF. The hard way is to root again and manually remove the bootsrap point. Then unroot again. SBF is much faster and convenient.
Click to expand...
Click to collapse
Thanks. I was afraid someone was going to say that. Is SBFing n00b-proof like z4root was with rooting my phone?
Edit: if you want to go the long way, once you rooted again from PC mount system in RW mode, delete /system/bin/logwrapper then rename /system/bin/logwrapper.bin to /system/bin/logwrapper. Reboot and custom recovery should be gone. Unroot with Z4root and you are done.
Click to expand...
Click to collapse
What does that mean??
jjdavola said:
Thanks. I was afraid someone was going to say that. Is SBFing n00b-proof like z4root was with rooting my phone?
What does that mean??
Click to expand...
Click to collapse
Huh, I was afraid you would say that Edit - I am sorry - I was about to put the commands you need to type using ADB from PC, but decided it will be confusing. ('from PC' to be scratched)
Well - SBF-ing is the easier way for you then. Simply make sure all pre-requirements are fulfilled (proper drivers installed, software loaded) and it is as easy as the Z4root. Read these instructions and follow them carefully and you will be set in no time
leobg said:
Huh, I was afraid you would say that Edit - I am sorry - I was about to put the commands you need to type using ADB from PC, but decided it will be confusing. ('from PC' to be scratched)
Well - SBF-ing is the easier way for you then. Simply make sure all pre-requirements are fulfilled (proper drivers installed, software loaded) and it is as easy as the Z4root. Read these instructions and follow them carefully and you will be set in no time
Click to expand...
Click to collapse
Thanks again!
OK. I flashed the SBF , it said PASS so I unplugged the phone and rebooted and Bootstrap didn't appear when I booted back up. What I believe to be a problem is that everything appears to be exactly the same as it just was (e.g. no apps were deleted, LauncherPro and my settings were still there etc.). Plus the System Updates option is not clickable anymore and my phone number was changed.
FYI I was thinking that the SBF would have just totally erased everything and I'd have to start from scratch installing apps etc.
Any thoughts?? Should I do another factory reset?
Yes - SBF will not erase data partition (user data). It is recommended you do factory reset once SBF is complete to clear up all the stuff that customizations before might have caused. At least you should clear cache partition to avoid wired behaviour from the phone. To delete cache - boot phone in stock recovery (power up while pressing X button - when you get the triangle with the android guy - press the magnifying glass button on the keyboard - menu will show up. Use the arrows and OK button to navigate. Options in menu are self explanatory I believe. Deleting cache will not delete your data, but deleting cache & data will delete data (factory reset)
To fix the phone programming (CDMA Verizon) - dial *228 option 1
leobg said:
Yes - SBF will not erase data partition (user data). It is recommended you do factory reset once SBF is complete to clear up all the stuff that customizations before might have caused. At least you should clear cache partition to avoid wired behaviour from the phone. To delete cache - boot phone in stock recovery (power up while pressing X button - when you get the triangle with the android guy - press the magnifying glass button on the keyboard - menu will show up. Use the arrows and OK button to navigate. Options in menu are self explanatory I believe. Deleting cache will not delete your data, but deleting cache & data will delete data (factory reset)
To fix the phone programming (CDMA Verizon) - dial *228 option 1
Click to expand...
Click to collapse
I cleared the cache and did the activation earlier. If I really need to, I'll do another factory reset some other day since unrooting, reseting and flashing wore me out for today.
Thanks again for your patience and assistance. I greatly appreciate your help.
i had the same problem and i figured out why it does it generally. Though it is weird for your case. When you have anything that requires root set to launch at boot (e.x SetCPU for me) for some reason it boots into the recovery. But when you disable these things it boots regularly.
Thanks to imnuts and wynalazca for all this info. I just collected it up into a how to video. Hope this helps as I am an visual learn and I know many others are. Complete at your own risk. If this helped please follow me @kraisydave on twitter, subscribe to youtube.com/kraisydave and visit www.KDtech.org. (A work in progress).
http://www.youtube.com/watch?v=IAKDeFIIM2c
1. Open ODIN.
2. Put the phone into download mode. Do this by powering off your phone, pulling out the battery, and then holding volume down while connecting it to your pc. A giant yellow triangle should be on the phone's screen and it should say 'Downloading...' ODIN should say 'Added!!' and one of the boxes will be yellow and say '0:[COM#]'
3. Click the button labeled 'PDA' and locate the file you are wanting to flash. For emphasis: YOU MUST USE THE PDA BUTTON!
4. Click start. Do not disconnect the phone while it is flashing, it can cause some serious damage.
5. Wait.
6. When finished, unplug the phone, put the battery back in and power up the phone.
Every time I've flashed this, the phone booted straight into recovery. Just select reboot (press home) and it boots up normally. It should probably be recommended to wipe data and cache afterwards, but I didn't and all of my data stayed in tact.
Multiple people have reported that this works. Use at your own risk. I am not responsible for anything that happens to your phone if this doesn't work.
Just wanted to know if you have any second thoughts about wiping data and cache?
When I used HTC phones, I always was warned to wipe data and cache.
Just asking.
kubla1,
Since rooting a week ago or so I have had no problems minus the updater sneaking up here and there. It is generally recommended to wipe the cache and data, but I still have not. When I move to other versions of android I do wipe everything just to avoid issues. But really it cannot hurt, so if you fell the need I say go for it.
Dave
I installed a update.zip(Acer_AV043_A701_0.006.00_WW_GEN1.zip).
then,My A701 restarted, but it's stuck at the ACER logo.
I hook up this device to the PC ,but not go to fastboot mode , "MTB drivers" is no found.
I pressed the "volume up"- and the "power"-button at the same time, released the power-button when the screen turns on and switched the lock switch on and off and on and off: top left corner of the screen says "Erasing Userdata... Unrecoverable bootloader error (0x19000008).
Who can help me? thks.
fishwood said:
I installed a update.zip(Acer_AV043_A701_0.006.00_WW_GEN1.zip).
then,My A701 restarted, but it's stuck at the ACER logo.
I hook up this device to the PC ,but not go to fastboot mode , "MTB drivers" is no found.
I pressed the "volume up"- and the "power"-button at the same time, released the power-button when the screen turns on and switched the lock switch on and off and on and off: top left corner of the screen says "Erasing Userdata... Unrecoverable bootloader error (0x19000008).
Who can help me? thks.
Click to expand...
Click to collapse
Unfortunately, as the 701 is new, there are not a lot of options at this time.
You can try downloading a full stock rom, renaming it to "update.zip", copy it to SD card, and boot your tab holding Vol + and PWR.
See it it installs the rom. You may have to try a couple. Hopefully 1 will work.
I am going to assume the update really wasn't meant for your version (WW_COM_GEN1 build) ?
Other than that, we do not have a service rom (EUU) available for the 701.
The only other option would be Acer Repair.
MD
thank a lot.
Hi Fishwood,
To get into a workable bootloader mode, try this:
Power button and volume DOWN at the same time, while flicking rotation lock on and off
When the tablet vibrates, let go of the power button, but KEEP pressing volume down and KEEP flicking rotation lock
The tablet should get to the bootloader.
Earlier I managed to put my tablet into an unusable state, but this method got me to the bootloader and I was able to continue working.
I'll tell you what I did, but I do not recommend this particular course of action - there is a chance you will completely ruin your tablet. Moscow Desire has warned in no uncertain terms to stay away from Clockwork Mod Recovery and I trust his judgement. I chose to go against his advice to do the following, but I was fully aware that I was running the risk of bricking my tablet.
I checked that the tablet was rooted
I installed CWM 6.0.1.1
I wiped the cache, wiped the user data (factory reset) and wiped the Dalvik
I then installed a stock ROM from the SD card
I then carried on messing around in the way I have been for a few days now.
If you are interested in doing this, I can provide the links for the various posts that I got my information/downloads from.
Seriously though, you do this at your own risk. If you're not sure about what you're doing, or you're not prepared to accept that you might brick your tablet, it's better to follow an alternative course of action.
misteral1970 said:
Hi Fishwood,
To get into a workable bootloader mode, try this:
Power button and volume DOWN at the same time, while flicking rotation lock on and off
When the tablet vibrates, let go of the power button, but KEEP pressing volume down and KEEP flicking rotation lock
The tablet should get to the bootloader.
Earlier I managed to put my tablet into an unusable state, but this method got me to the bootloader and I was able to continue working.
I'll tell you what I did, but I do not recommend this particular course of action - there is a chance you will completely ruin your tablet. Moscow Desire has warned in no uncertain terms to stay away from Clockwork Mod Recovery and I trust his judgement. I chose to go against his advice to do the following, but I was fully aware that I was running the risk of bricking my tablet.
I checked that the tablet was rooted
I installed CWM 6.0.1.1
I wiped the cache, wiped the user data (factory reset) and wiped the Dalvik
I then installed a stock ROM from the SD card
I then carried on messing around in the way I have been for a few days now.
If you are interested in doing this, I can provide the links for the various posts that I got my information/downloads from.
Seriously though, you do this at your own risk. If you're not sure about what you're doing, or you're not prepared to accept that you might brick your tablet, it's better to follow an alternative course of action.
Click to expand...
Click to collapse
thks.
Pls give me the all links.
thank you so much!
I checked that the tablet was rooted I do
I installed CWM 6.0.1.1 I do
I wiped the cache, wiped the user data (factory reset) and wiped the Dalvik I do,but "Error mounting /data!"
Pls help me!
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
*D821 (E) - hammerhead
*KTU84M
*HW version: rev_11
*bootloader version: HHZ11k
*baseband version: M8974A-2.0.50.1.13
*carrier info: NONE (is this wrong?)
*signing: production
*secure boot: enabled
*lock state: locked
#I didn't touch this phone's system, still original.
my story:
so it's been 3 weeks since I bought my phone. I was happy with it, nothing was wrong.
a week later, the 4.4.3 came out, I updated it, and nothing was wrong too.
until last night, I turned off my phone, curious to see how the Nexus 5's recovery look like,
I pressed (volume down + power), and I noticed that it enters FASTBOOT mode. and I just learned, navigate with the volume buttons and select with power button.
NOTICE: I'm already familiar with things like this, I was in the Galaxy W forum and Galaxy SIII mini forum. *yes lol I came from Samsuck
so I selected recovery mode and enter it.. I saw the android logo there, the healthy one, not the murdered robot with a red triangle on it.
I saw nothing but that logo, I pressed volume up button and the text showed up. I navigate down with volume down button, until it was down at the "wipe cache partition", I wanted to go up to reboot my phone, but I realized, the up button just a switch to hide or show the recovery text, so there's only one choice, press the power button, *if I press the power button, I wipe the cache because it selects "wipe cache partition"*.
and then it writes "wiping the cache", I was confused why it was so long, until I decided to reboot with holding the power button.
NOTICE: it is strange to wait sooooo long for cache wiping. I know this.
the system turned on. I'm not sure if the cache wiped cleanly, I'm afraid it will make the system error. so I decided to change my runtime from ART to Dalvik, so the cache wiped out and built again, strange process that took only 64 apps to optimize, that before it was around 110 apps. and then after reboot, I decided to go ART again to saw how many apps that optimized, LOL it was again, 64.
I reboot my phone again, and wait the reception, LOL strange I got no signal in my home *usually full*.
NOTICE: the signal has already gone after first cache wipe.
somehow I go to About Phone, Status on the Settings, and I found out the IMEI is UNKNOWN. I tried to check it with *#06# and it shows nothing.
I repeat the process how I get to the recovery and try to wipe cache, and it said, "error: can't mount /cache".
so I think the cache was gone?? I look to the "Explorer" app *the one who makes the root version too (Root Explorer)*, well the cache partition still there.. LOL
MY QUESTION:
1. am I having a defective Nexus 5? or there is a bug?
2. my IMEI lost, I have 2 expectations: my EFS/IMEI is truly lost, or the system just can't detect it? how can I know?
3. I saw a thread that tells me Nexus 5 doesn't have EFS partition backup, so where does the EFS located?
4. if I follow you guys, unlocking bootloader, rooting and etc. can I make my phone's state default again? *I don't mean fix this thing, just go default*
5. most important thing, HOW CAN I GET MY PHONE BACK TO NORMAL?? *peace bro
please help, right now I'm trying to reset my phone as soon as my backup finishes.
thx
I think people have remedied this problem by flashing the factory image. If that doesn't work then it is probably a hardware defect and will have to be replaced.
There's an option in the stock recovery which reads "Reboot System Now". You could have selected that if you didn't want to do anything.
1. No, the cache partition got messed up and hence the unknown IMEI and signal loss.
2. The system just can't detect it because of the reason mentioned above.
3. EFS is located on the /efs partition but you need root to back it up or restore it.
4. No need to root the phone to fix this. Go back to the stock recovery and wipe cache partition again and this time around WAIT PATIENTLY for it to complete. This should fix it.
5. ^^^^^^
vin4yak said:
There's an option in the stock recovery which reads "Reboot System Now". You could have selected that if you didn't want to do anything.
1. No, the cache partition got messed up and hence the unknown IMEI and signal loss.
2. The system just can't detect it because of the reason mentioned above.
3. EFS is located on the /efs partition but you need root to back it up or restore it.
4. No need to root the phone to fix this. Go back to the stock recovery and wipe cache partition again and this time around WAIT PATIENTLY for it to complete. This should fix it.
5. ^^^^^^
Click to expand...
Click to collapse
as I told you before, I can't select "reboot system now" because the volume up button strangely working as show/hide text. wipe cache partition, the /cache can't be mounted.
BirchBarlow said:
I think people have remedied this problem by flashing the factory image. If that doesn't work then it is probably a hardware defect and will have to be replaced.
Click to expand...
Click to collapse
well, my phone still original untouched.. what if you were me, having an untouched phone and it has already been like this? I don't think I would touch it ._.
anyway, @BirchBarlow @vin4yak , I can go adb and fastboot without root or unlock bootloader right? thx anyway
IvanKurnia said:
as I told you before, I can't select "reboot system now" because the volume up button strangely working as show/hide text. wipe cache partition, the /cache can't be mounted.
Click to expand...
Click to collapse
Strange indeed. Yeah, those errors are common. Just try wiping cache multiple times. If not, factory reset the device.
IvanKurnia said:
well, my phone still original untouched.. what if you were me, having an untouched phone and it has already been like this? I don't think I would touch it ._.
Click to expand...
Click to collapse
Since you're responsible for this mishap, I would certainly try to fix it myself if I were you. Wiping cache/factory reset is the only thing you can do with a locked bootloader. If that doesn't fix it, the phone's hosed!
IvanKurnia said:
anyway, @BirchBarlow @vin4yak , I can go adb and fastboot without root or unlock bootloader right? thx anyway
Click to expand...
Click to collapse
ADB is used whilst you're in Android OS/custom recovery. You first need to unlock the bootloader, flash/boot a custom recovery and then flash the supersu.zip to gain root. I'm not sure what purpose it will serve in your situation though??
this happened to me too. and I waited for the the wipe cache operation for 15 minutes. After a forced reboot the phone was not connecting to the cell network, had a 1970 date and gave various google errors. I went back to recovery, noticed the comatose android and the missing cache partition messages but again I selected wipe cache and this fixed it. It took just a minute or so to create and format it. After the reboot the phone was fine. phew...
This problem happens when the cache partion is not formated properly. You can't take screenshots either, right? You should try to format the cache partition again, and again until your phone becomes normal, or unlock bootloader and flash the cache.img from the stock images. You can find all the instructions about unlocking bl and flashing cache image in the sticky posts of the general forum.
Tapatalk-kal küldve az én Nexus 5-el