Related
I have franco kernel and i tried to go to faux kernel but i know you have to reset franco kernel so i downloaded the reset zip from faux thread and i flashed it but its stuck with the black google screen..I need help kinda scared. is it bricked??
Cjshino said:
I have franco kernel and i tried to go to faux kernel but i know you have to reset franco kernel so i downloaded the reset zip from faux thread and i flashed it but its stuck with the black google screen..I need help kinda scared. is it bricked??
Click to expand...
Click to collapse
i tried getting into bootloader by holding down all the buttons but im in download mode and nothing happens...
No, your phone is not bricked.
ziddey said:
Because you don't hit "all the buttons" to get to fastboot.
No, your phone is not bricked.
Click to expand...
Click to collapse
im holding the power button and the up and down volume buttons..nothings happening
Cjshino said:
im holding the power button and the up and down volume buttons..nothings happening
Click to expand...
Click to collapse
wait nvm im in
Im in recovery but I dont know what to do next
Cjshino said:
Im in recovery but I dont know what to do next
Click to expand...
Click to collapse
Easiest method would be to dirty flash whatever rom you're running.
Edit: also, only need power + volume down to boot into bootloader. Holding the power button for 10 seconds will hard reboot your phone.
Truth be told, I just hold power for 10 seconds, then just hold volume down before it gets to the Google logo.
Sent from my Nexus 4 using Tapatalk 4 Beta
DontPushButtons said:
Easiest method would be to dirty flash whatever rom you're running.
Edit: also, only need power + volume down to boot into bootloader. Holding the power button for 10 seconds will hard reboot your phone.
Truth be told, I just hold power for 10 seconds, then just hold volume down before it gets to the Google logo.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
im on stock rom.
Cjshino said:
im on stock rom.
Click to expand...
Click to collapse
Then find a windows machine and download the Occam stock image from Google and flash it via fast boot
Sent from my Nexus 4 using xda app-developers app
http://forum.xda-developers.com/showthread.php?p=40859201 motley has a stock kernel and components link in the OP. Don't forget to thank him if it helps.
That's for 4.2.2, so if you're on 4.3 it may not help. Failing that, try reflashing Franco's kernel?
Sent from my Nexus 4 using Tapatalk 4 Beta
Harry GT-S5830 said:
Then find a windows machine and download the Occam stock image from Google and flash it via fast boot
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
but how do I get the file in my phone?
sigh im getting overwhelmed on what to do. I've searched many methods and I dont know where to start. im gonna be up all night and I need my phone tomorrow
Just try reflashing Franco?
Sent from my Nexus 4 using Tapatalk 4 Beta
by reflashing I just go to recovery and go to the install tab ?
DontPushButtons said:
Just try reflashing Franco?
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
omg that was all I needed to do! Thank you!!
Hi guys, I recently installed CM on my N4 and at some point on day one the vibration got completely disabled. No haptic feedback, no vibration when my alarm goes off etc.
Obviously I double checked all options already. Rebooting doesn't help either.
What could the reason be and how to fix it?
I don't think it would be a hardware failure, but to be sure you can try dirty flashing your ROM and that would also reflash the ROM's stock kernel, and if there is still a problem, try flashing a custom kernel. If all fails, flash back to stock.
Sent from my Nexus 4 using XDA Free mobile app
I installed loillipop 5.1, from scratch using the factory image. All went smooth and the performance was much better than with 5.0.2 (which was my previous version), but I have random reboots unless I stay connected to the wall. This can be easily reproduced by putting the tablet to sleep (i.e., I pressing power button). Immediately my nexus reboots (99% of times).
I tried everything possible. Factory reset. Reistalled after formatting every possible partition. Reistalled starting from scratch without using my google backups. Nothing helps.
The only solution was to come back to 5.0.2 (again through the factory images, flashing and formatting everything).
Last test I am going to do is to use the OTA to go from 5.0.2 to 5.1 but I do not have much hope.
Anyone else experiencing similar problems?
It looks like an hardware issue put in evidence by the new kernel that is part of 5.1, but it could eb enything else.
Greetings.
Have you tried using any other kernel, eg. franco kernel?
Fobos531 said:
Greetings.
Have you tried using any other kernel, eg. franco kernel?
Click to expand...
Click to collapse
Thanks for the suggestion, I didn't know Franco had released a version of his kernel for 5.1. I tried latest M-Kernel but it is not working with 5.1. Now I am sideloading the OTA from a stable 5..0.2, just to see if going to 5.1 using OTA helps. Will report if I succeed and in case I didn't will try with FK (and report).
Meanwhile, any other suggestion is welcome
Fobos531 said:
Greetings.
Have you tried using any other kernel, eg. franco kernel?
Click to expand...
Click to collapse
Current situation after some more tests:
5.0.2 from factory image (full wipe): works
5.0.2 -> 5.1 via OTA: reboot each time goes to sleep (unless wall powered or attached to PC USB)
5.1 from factory image (full wipe): same as above
rastapop 5.1 (full wipe): same as above
5.1 + franco kernel R82: same as above
I would try to increase CPU voltage: any suggestion how to do? Which kernel to use? Which app to adjust voltages? I am going to try with franco kernel and trickstermod (which I already bought) but I am not sure this combination will allow me to adjust voltages.
EDIT: no way to adjust voltages with FK for 5.1. Reverting back to 5.0.2 and waiting someone gives suggestions or has similar issues (or releases new kernels)
Sideload 5.1, same issue. Even worse than 5.0.2.
Sent from my Nexus 7 using XDA Free mobile app
killerfrank said:
Sideload 5.1, same issue. Even worse than 5.0.2.
Click to expand...
Click to collapse
Even in your case the device reboots just after entering sleep mode? Please confirm, I thought I was the only one, but if this happens to others then it must be a software issue, not hardware.
This does not happen at all to me(using stock 5.1 with Franco Kernel).
This is indeed happening to me as well with the factory 5.1 image. Also thought Franco Kernel could possibly be a solution but didn't work. I had F2FS previously but reverted to install stock 5.1.
_Hobbz said:
This is indeed happening to me as well with the factory 5.1 image. Also thought Franco Kernel could possibly be a solution but didn't work. I had F2FS previously but reverted to install stock 5.1.
Click to expand...
Click to collapse
It looks like a mixed hw/sw problem. It is indeed clear that 5.1 works on most N7, either being installed from factory images or after an OTA upgrade, but for some of us it results in rebooting when the machine goes to sleep.
I attached last_kmsg (/proc/last_kmsg) just after the problem manifested. This is exactly what happens every time I put the device to sleep (pressing the power button or leaving it alone for a couple of minutes) and it repeats always the same (with the same kmsg).
Anyone knows how to extract other information that could be useful to isolate the source of the problem? Notice that I cannot do a catlog since the device doesn't go to sleep if it is connected to a PC (so I cannot recreate the problem).
Your battery is dying, I've been getting the same problem until I replaced the battery today.
richarddwyer10 said:
Your battery is dying, I've been getting the same problem until I replaced the battery today.
Click to expand...
Click to collapse
A hardware problem related with the power unit of the device was also my first hypothesis, but under 5.0.2 i everything works perfectly and the battery has the original duration. Under 5.1 also everything works... until the device goes to sleep. Only then it reboots.
Was this the behavior in your case?
I've been getting the same issues on my N7 since updating.
regret to disappoint you people, but i have not a single reboot in my nexus 7 since doing a clean install from cm12. two days being unrooted, no reboots; now running three days rooted, still no reboot. could be due to the clean install i did. lol.....
ondoy1943 said:
regret to disappoint you people, but i have not a single reboot in my nexus 7 since doing a clean install from cm12. two days being unrooted, no reboots; now running three days rooted, still no reboot. could be due to the clean install i did. lol.....
Click to expand...
Click to collapse
I also made a clean install of 5.1 using the factory image and formatting everything (from system to data and cache). Still I have the reboots. I come back to 5.0.2 (same procedure: clean install from factory image) and had no reboots in four days of use. Clean install of rastapop (5.1 based) or 5.0.2 -> 5.1 via OTA resulted in the same situation: The device reboots as soon as it goes to sleep.
I know several users installed 5.1 and have no issues, this is why I think this is a hardware problem put in evidence from the new software.
I hope someone find a way to deliver a 5.1 version that do not present the problem (I like how smoother 5.1 is w.r.t. 5.0.2). Perhaps a new kernel or a new rom as a whole.
gianpaoloc said:
I also made a clean install of 5.1 using the factory image and formatting everything (from system to data and cache). Still I have the reboots. I come back to 5.0.2 (same procedure: clean install from factory image) and had no reboots in four days of use. Clean install of rastapop (5.1 based) or 5.0.2 -> 5.1 via OTA resulted in the same situation: The device reboots as soon as it goes to sleep.
I know several users installed 5.1 and have no issues, this is why I think this is a hardware problem put in evidence from the new software.
I hope someone find a way to deliver a 5.1 version that do not present the problem (I like how smoother 5.1 is w.r.t. 5.0.2). Perhaps a new kernel or a new rom as a whole.
Click to expand...
Click to collapse
I've seen other people reporting the same issue on the nexus help forums too so hopefully Google will be looking in to this.
_Hobbz said:
I've seen other people reporting the same issue on the nexus help forums too so hopefully Google will be looking in to this.
Click to expand...
Click to collapse
Sorry, which forums do you exactly mean? Something here on XDA or something managed by Google directly? If you could forward us to the right place we could add our report. The more we are the easier it is that Google takes the issue into consideration (I hope
Thanks
I've given up on LP for the N7. I've gone back to KK. Stability is awesome, performance is great. LP was a disaster on the N7. Performance issues, lock ups, etc. No matter how many times I clean installed it, etc, it just wasn't good.
I'm now officially calling it Lollipoop (at least for the 2012 N7). But, it is an old device. I'm still waiting to see how it turns out on my LG G3 phone. I'm sticking with KK on that phone as well for now until I know for sure it runs well on it.
Stability over bleeding edge.
Hi
JFYI, I have just updated my 2 sons' N7 2012 (coming from Omnirom) to Lollipop 5.1 (with Nexus Root Toolkit v2.0.4, meaning following the same procedure)
- 1 of them fine
- 2nd one with the issue reported here; which is why I'm on this thread now
updated kernel to franco r82
the issue remains...
will keep checking this thread
thansk
beng
gianpaoloc said:
Sorry, which forums do you exactly mean? Something here on XDA or something managed by Google directly? If you could forward us to the right place we could add our report. The more we are the easier it is that Google takes the issue into consideration (I hope
Thanks
Click to expand...
Click to collapse
So I can't post links yet because of my low number of forum posts but if you google 'nexus help after update to 5.1, it won't wake up after in sleep mode, please help' then it should be the first result that shows up.
Things were running fairly well for me with the slimkat 5.0.2 rom on F2FS so I'll likely switch back to that while this gets sorted out.
I've had my n7 for 2 years now, flashed all kinds of custom Roms, bricked it, fixed it, encrypted it, unencrypted it several times, and It has never ran as slow as it did on lollipop. I tried, 5.0, 5.0.2, and 5.1 I even reset kk to stock and let the ota's do the job and no matter what, LP is still not usable in my opinion. I feel sorry for the people that take the ota and do not know how to revert back to kk.
Sent from my Nexus 7 using Tapatalk
On Pure Nexus rom with EX kernel, my battery indicator drops 2% at a time.. Is there any fix for this?
I'm getting this too. Its annoying find any fix ?
I'm having this with PureNexus and Franco. So is it kernel or ROM related?
I'm not 100% sure but I think I heard about this in a different thread, try to dirty flash ROM + Kernel and wipe dalvik + cache before reboot.
Regards,
I'll give this a go and let you know
Not seeing this with Pure Nexus 2/3 build & Franco r9 kernel. Clean flashed tonight
Sent from my Nexus 6P using Tapatalk
I was having the same issue after flashing PureNexus + ElementalX Kernel, then I thought going back to stock (completely unrooted) would fix this issue entirely, but unfortunately the problem still persists. The fellows at Google suggested me to wipe the device cache which supposedly would fix it, will see how that goes.
I'm actually seeing this now and have tried wiping cache. Not really concerning for me since it's just a reporting issue (battery life isn't affected)
Sent from my Nexus 6P using Tapatalk
Bump this tread i have same useuses i factory rest the latest 6.0.1 and android N W firmware all stock same hapend first 100%-90% ok 1% drop the after that its 1% drop then in 5 seconds andother % drop i thoth its a N devoloper bug but its not have same on stable M build shood i wory about?
I also have this issue with the latest Pure Nexus and ElementalX. Battery life does not seem very good but perhaps it's just something wrong with the battery indicator?
nds850 said:
I also have this issue with the latest Pure Nexus and ElementalX. Battery life does not seem very good but perhaps it's just something wrong with the battery indicator?
Click to expand...
Click to collapse
does its was ok before i just bought used nexus 6p week ago so i very nevous about it i was thinking its N preview doing this but its not
Seems to be a Google bug that happens to some users. Haven't found a solution yet but we´re not alone.
Happening here too on stock latest 6.0.1 firmware
Enviado desde mi Nexus 6P mediante Tapatalk
It's a 6p bug
Sorry for necroposting. Same problem here with N5X all stock, MM 6.0.1
I'm having the same problem here, started while using stock then I tried to flash CM but it didn't fix it, flashed stock again today, still happening
But the problem here also is that it's greatly affecting my battery life
I have the same priblem Pure nexus EX kernel twice clean flashing and the same.
It had been reported many times
Its a 6p bug
Even i have faced it
Some users have claimed that N had fixed that
I'm still on DU and have this since day 1 i had this device
Cheers
I have this problem on my 5X too, like i said.
I have this issue but I take it I just a software issue, if it was fixed the battery life wouldnt be any different
It stays at a number for a long time then it drops by two
Hi,
using French device DS with build 23.118-10. Lollipop 5.1.1. Rooted with SuperSU 2.46 and using latest v79 xposed.
All smooth except for this:
Phone calls work until - randomly - the mike does not work anymore. Switching to hands free and back remedies the situation. Still, this being a phone, I would like rock solid calls.
Was using Amplify before and turned it off to make sure this wasn't the culprit. Still hard to diagnose.
Any ideas?
dreinulldrei said:
Hi,
using French device DS with build 23.118-10. Lollipop 5.1.1. Rooted with SuperSU 2.46 and using latest v79 xposed.
All smooth except for this:
Phone calls work until - randomly - the mike does not work anymore. Switching to hands free and back remedies the situation. Still, this being a phone, I would like rock solid calls.
Was using Amplify before and turned it off to make sure this wasn't the culprit. Still hard to diagnose.
Any ideas?
Click to expand...
Click to collapse
Issues maybe with xposed. Try uninstalling that.
Sent from my XT1562 using Tapatalk
Possible but doubt it. Also too many people using xposed. I already uninstalled Amplify to make sure its not some wakelock that is blocked or delayed...
dreinulldrei said:
Hi,
using French device DS with build 23.118-10. Lollipop 5.1.1. Rooted with SuperSU 2.46 and using latest v79 xposed.
All smooth except for this:
Phone calls work until - randomly - the mike does not work anymore. Switching to hands free and back remedies the situation. Still, this being a phone, I would like rock solid calls.
Was using Amplify before and turned it off to make sure this wasn't the culprit. Still hard to diagnose.
Any ideas?
Click to expand...
Click to collapse
I'm on Lollipop 5.1.1 as well (Canadian stock Rom). My Xposed setup is v79 sdk22 arm with SuperSU 2.62 and I haven't had any of the problems that you are having. I'm using the stock dialer. Do you have any Xposed modules that might be acting up.
Sent from my XT1563 using Tapatalk
None. Just True Silent Mode, Gravity Box and Greenify. Already tried with experimental features off etc. Anyway. Restored to stock 23.118-12 and will see if the fresh re-install fixes things. Noticed that the phone likes to fall asleep when in a call and holding against my ear... Need to press unlock button sporadically.
Hi, I've the same problem in STOCK reteu 6.0 without root, did you solve the problem???
One problem I have been having, and its extremely random (never been able to duplicate, has happened twice now) is the phone just goes completely silent on a call over Bluetooth. I switch to speaker and it works, then back to Bluetooth and it stays silent. I have to reboot the phone to get phone audio back over Bluetooth. I wonder if the issues are related, it happened once on 5.1.1 and once on 6.0.
@eloyo: Did not happen again, but might have happened once when someone dropped the call and re-called before I could switch on speakerphone.
Might have helped I reflashed the modem when installing the -32 Retasia release.