Develop Bugs

[Q] Phone crashed and wont boot into OS

Here's whats going on:
My phone has AOKP M4 (4.0.3) with Franco r98 (with hotplug, ondemand governor and no UV). The phone had been working for about close to 200 hours with no crash until today. I was about to check my email, so i pushed the power button and slid to unlock. It opened to the homescreen and then just froze.
Pulled the battery, restarted the phone, went through the boot animation and then it just sits on a black screen. It does nothing. Fastboot and CWM still work so i wiped cache/dalvik and rebooted again; same problem. Installed Franco M2 kernel for testing but still did the same thing..
What would you guys recommend me doing? Thanks

ankushkatari said:
Here's whats going on:
My phone has AOKP M4 (4.0.3) with Franco r98 (with hotplug, ondemand governor and no UV). The phone had been working for about close to 200 hours with no crash until today. I was about to check my email, so i pushed the power button and slid to unlock. It opened to the homescreen and then just froze.
Pulled the battery, restarted the phone, went through the boot animation and then it just sits on a black screen. It does nothing. Fastboot and CWM still work so i wiped cache/dalvik and rebooted again; same problem. Installed Franco M2 kernel for testing but still did the same thing..
What would you guys recommend me doing? Thanks
Click to expand...
Click to collapse
Wipe data?
Sent from my Galaxy Nexus using xda premium

Disable hotplug after you get the restore running. Also, disable any "set on boot" kernel teaks you may have added.

I will give flashing a new rom a try.. just making up a nandroid and copying some stuff over just in case something goes wrong.
However i dont know how this happened in the first place after working for so long!

[Q] My Verizon GNex keeps turning itself off!!!!

Hey guys, so I have this big problem I have never seen before.
My Verizon Galaxy Nexus keeps turning itself off after about 1-2 minutes of turning on. The only way to turn it back on is to do a battery pull. This started when I upgraded the Franco Kernel to the latest version which I think is #350 I believe. I thought it was the kernel at first so I booted into recovery and flashed Tinys Kernel. Needless to say it turned off again. It would make a weird flash transition as the screen would shut off. I then wiped data, wiped cache, wiped dalvik, flashed Muzzys latest ROM, and booted. Then it said the process for Setup was unable to process. I booted into recovery, flashed the zip for SuperWipe, flashed Muzzy's again and it worked. But after 3 minutes right when it was logging into my Google Account through setup, it turned off again.
Does anybody know how to fix this? What a horrible way to start Christmas...ugh
Thanks everyone.

Nevermind. I found the problem. Apparently it seems that the OEM Samsung Extended 2100 mAh battery is shot. It came with my phone at Verizon when I bought it from them the day this phone launched. I put my girlfriend's GNex battery in my phone and it is running no problem. I put the OEM Extended into hers and her phone shut off after 1 minute of being powered on. The battery has about 3/4 full charge. Not sure what happened but it seems the battery is done and I got to get a new one.
Hope this helps out people who have the same issue!

[Q] Flashed Trinity 3.2 for XaS, cant charge through PC

so reflashed the Trinity 3.2 rom on my Acro S, and was surprised to see my phone not charging when connected to PC..here's what i noticed:
red led is on when connected [usually means it's charging, right?]
there's no up trend on the battery stats [it's flatlined, which i think means it's not using the battery power but using the USB power instead]
battery charging animation is there on offline charging through PC, but when i turn it on after 20 minutes or so, the battery level is the same
lockscreen says it's charging and show battery percentage but stays the same for another 20 minutes
so, i already tried changing roms to RootBox, thinking maybe it's kernel related, but its the same
this is also not my first time to reflash Trinity, i already reflashed maybe 3-4 times with no problems..
am i missing something when flashing?though i flashed it the same way i flashed before: wipe data, cache and dalvik; and never had problems till now, it's just confusing..can anybody help?
i borrowed a wall charger from a colleague that has an XneoL and it's charging right now, 1% to 14% in 15 minutes

boyheadkick said:
so reflashed the Trinity 3.2 rom on my Acro S, and was surprised to see my phone not charging when connected to PC..here's what i noticed:
red led is on when connected [usually means it's charging, right?]
there's no up trend on the battery stats [it's flatlined, which i think means it's not using the battery power but using the USB power instead]
battery charging animation is there on offline charging through PC, but when i turn it on after 20 minutes or so, the battery level is the same
lockscreen says it's charging and show battery percentage but stays the same for another 20 minutes
so, i already tried changing roms to RootBox, thinking maybe it's kernel related, but its the same
this is also not my first time to reflash Trinity, i already reflashed maybe 3-4 times with no problems..
am i missing something when flashing?though i flashed it the same way i flashed before: wipe data, cache and dalvik; and never had problems till now, it's just confusing..can anybody help?
i borrowed a wall charger from a colleague that has an XneoL and it's charging right now, 1% to 14% in 15 minutes
Click to expand...
Click to collapse
I think there was this problem with 3.2 version itself.. Lots of users complained about FC's and different sorts of bugs.. May be this was one among them too.. U can try 3.4 or just flash the original ftf itself.. Or if u have had a CWM backup of your previous ROM, you can do that too.. You know, the best thing u can do to avoid these sorts of probs in future is to make a clean install or clean flash as they say.. Wipe everything, format system,data,cache and then flash the ROM..

i do wipe everything when i update a rom
and Trinity 3.4 for Acro S hasn't been released yet
thanks anyways

[??] Recent 4.3 doesn't boot! - Help!

Hello!
Today, my bro - gnex succesfully waked me up with a new alarm sound (a really weird loop of a Timely sound)... It froze in the "snooze" screen in Timely, and it didn't do anything so I removed the battery and then I turned it on.. It passed the Google logo, but the boot animation never appeared... It didn't reboot (no boot loop), and it got quite hot in the area next to the camera... Now it doesn't start. I can get into fastboot and recovery (Twrp)
It's been like a week since I got it into ParanoidAndroid 4.3 (3.99v), and since, it rebooted a couple of times, don't know if it has something to do with the Rom or the Kernel or if it's relevant...
My gnex is rooted and unlocked (obviously), with PA 3.99 (the latest 4.3?) and franco kernel (r391 nightly).
- First, I wiped cache\dalvik - No change
- Then I did a full wipe - No change
- Tried to install stock 4.3 with the Toolkit (yep, I know that's not the best way... won't do it again) - didn't worked (It looked like it succesfully installed radio and bootloader but then an error stops everything)
I always thought I was such a badass installing things to my unbrickable gnexus, now I'm too scared to do anything else to it without any help...
I'm from Costa Rica, please excuse my English
Any help would be much appreciated!!
EDIT: Managed to install stock again, 4.3, stock recovery and radios... Got halfway of the boot animation but then boot-loop... Went to stock recovery and wiped cache, no change... Re-flashed stock android, no change... Re-locked and unlocked the bootloader so it would wipe everything... Sadly no change...

phantom16r said:
Hello!
Today, my bro - gnex succesfully waked me up with a new alarm sound (a really weird loop of a Timely sound)... It froze in the "snooze" screen in Timely, and it didn't do anything so I removed the battery and then I turned it on.. It passed the Google logo, but the boot animation never appeared... It didn't reboot (no boot loop), and it got quite hot in the area next to the camera... Now it doesn't start. I can get into fastboot and recovery (Twrp)
It's been like a week since I got it into ParanoidAndroid 4.3 (3.99v), and since, it rebooted a couple of times, don't know if it has something to do with the Rom or the Kernel or if it's relevant...
My gnex is rooted and unlocked (obviously), with PA 3.99 (the latest 4.3?) and franco kernel (r391 nightly).
- First, I wiped cache\dalvik - No change
- Then I did a full wipe - No change
- Tried to install stock 4.3 with the Toolkit (yep, I know that's not the best way... won't do it again) - didn't worked (It looked like it succesfully installed radio and bootloader but then an error stops everything)
I always thought I was such a badass installing things to my unbrickable gnexus, now I'm too scared to do anything else to it without any help...
I'm from Costa Rica, please excuse my English
Any help would be much appreciated!!
EDIT: Managed to install stock again, 4.3, stock recovery and radios... Got halfway of the boot animation but then boot-loop... Went to stock recovery and wiped cache, no change... Re-flashed stock android, no change... Re-locked and unlocked the bootloader so it would wipe everything... Sadly no change...
Click to expand...
Click to collapse
How did you flash stock? With fastboot via the flash-all.bat?
Sent from my Galaxy Nexus using XDA Premium HD app

Battery issues

Hey guys I've a problem with the battery of my mzp, the duration in this days was poor, check the images below
In the last screenshot was from 3 days ago
Stock 7.1.1 ROM by flashallthetime + substratum
Any ideas ?

I'm also having very very bad battery life after the 7.1.1!

Hi guys, you need to recalibrate the battery.
To do so (according to a Motorola official video) you have to first perform a force restart (hold power until it restarts by itself) then fully charge the phone to 100% without using it, then keep the phone for another 2 hours plugged in without using it. That will recalibrate the battery. I did this and I'm back to 6 - 7 sot with everything activated.

If you already have flashed a stock rom with twrp, try to flash the stock 6.0.1 Marshmallow rom build by flashallthetime. You should get 10-12h of screen on time.