I recently installed Dirty Unicorns along with JBX 0.8 Hybrid kernel in system 2 using BMM on a GSM XT910. I've installed the kernel before, but I've never had it replace the motorola boot image before getting to recovery with the JBX logo. Can anybody tell me why that boot logo before recovery would have changed and how I'd go about changing it back?
Furthermore, there seems to be a discrepancy between battery stats on DU and the stock rom. For example, today the stock rom says the battery is at 30 % which is consistent to what the battery level was according to BMM (3%). When I booted into DU it said it was at 49%. I've tried wiping the battery stats, but I imagine it'll be a while before I know if this solves the problem. Has anyone else experienced this before?
Lastly, my phone doesn't seem to go into deep sleep. I'm new to trickster mod and don't have much experience with fiddling around with the kernel. My phone seemed to be doing very well, it was at 100% charge for five hours but then it rebooted itself and the cpu was constantly running at 1000 MHz which is the max value I set. At the time I was using Performance Control, and thought that might be the issue. I performed a wipe, reflashed, installed trickster mod and set up battery friend but my phone hasn't gone into deep sleep at all. What might I be doing wrong?
Edit: I probably should have added that the boot image is a problem to the thread title. If any mod wants to do that, I'd be grateful.
Just an update, the battery issues seem to be resolved with the battery friend majigger and wiping the battery stats. Although, I have the orange led for full battery but the level is at 76%. :/
Still don't understand the boot image, if anyone can explain.
I did the same thing and it freaked me out for a bit After searching I found the logo for the new Moto/Google logo and it also included the Original Logo. Downloaded the newer logo and the old logo, and I replaced the new logo with the old/original logo in the setup folder on my computer. Let the program do its thing, and I now have the original Moto logo back.
This is all explained at http://forum.xda-developers.com/showthread.php?t=2340961
Good Luck. I just followed the directions there. The Original logo download is just below the RSD lite screenshot.
Related
Installed Cyanogen 6.1.1 and GApps yesterday (wiped cache partition, Dalvik cache and battery stats before installing). Was working great all night and most of today. Much faster, not crashing like the JIT was causing my phone to do.
This afternoon the battery seemed to be charging slowly so I restarted the phone. The phone kept getting stuck in the boot screen (with the blue android on a skateboard). I took the battery out and tried again. Same thing happened about 4 times, then finally it went through and started the phone. However, everything started crashing one by one when i got into my phone (force close) and I wasn't able to do anything. I had to pull the battery out again to restart.
It seems to be a toss up now, it either gets stuck in a boot loop or it starts up and everything crashes. I can't even get into XRecovery for some reason so I can't wipe to factory defaults. Seems like the phone is wrote off.
Is there anything I can do? Any help would be appreciated as I am lost without this phone.
I flashed the latest builds from both Coffebeans - http://forum.xda-developers.com/showthread.php?t=1547778 and Pershoot - http://droidbasement.com/galaxy/roms/cm9/p4wifi/ and I'm having the same issue with both of them. The problem is my Tab will randomly reboot then get stuck on the boot animation and just sit there forever. It's already happened twice now where my Tab rebooted sometime at night and sat at the boot animation until the battery was dead. I did do a full wipe before flashing.
Does anyone else have this issue?
Thanks.
i've ran both of those without any problems. did you come from another custom rom or from stock firmware?
foliage green said:
i've ran both of those without any problems. did you come from another custom rom or from stock firmware?
Click to expand...
Click to collapse
I came from Task650's version 14, but I've been flashing the CM9 KANGs for a while and haven't had this issue.
i have had some strange reboots...but never gotten stuck on the boot animation like that..thats the bad part about not having a battery to yank unfortunately
Sent from a Gtab 10.1 running Build 30
Well whenever I can't get something to work right, I Odin stock firmware on it and restart the custom rom process from scratch. Having a clean slate is time consuming and might not even be necessary but it's the only full proof way I can get things to work.
I wiped everything and also formatted /system in CWM and then flashed Coffeebeans latest build from 4/8. I haven't had the reboot and stuck boot animation issue, but now I'm having an issue where every time I charge the tab fully it won't wake up. I have to hold the power button to reboot it. It seems like it's the deep sleep issue, but it's been fine leaving it overnight as long as it's not connected to the charger.
Let me first explain what I did.
1. From stock rom, after doing the root (TWRP recovery), i flashed JellyDaemon v 2.0 listed here http://forum.xda-developers.com/showthread.php?t=2307247 . Used CPU control inbuilt in app to set CPU governer to OnDemand
Fantastic ROM with no problems.
2. After the news of 4.2.1 release came, I started looking for 4.2.1 based roms. I went with StarkHD listed here http://forum.xda-developers.com/showthread.php?t=2212028 . I think my download went wrong and file wasn't downloaded cleanly. I flashed with it. Flash went on successful. Phone got hung at the boot animation. Tried multiple methods to start the ROM. No success. Phone not booting into any ROM.
3. I had stock rom v 0.16 available with so flashed it with SP flash tools. Flash was successful.
4. Downloaded Naturewiz HD listed here http://forum.xda-developers.com/showthread.php?t=2319288 . ROM flashed and phone booted. Restored the apps. Used battery calibration app to calibrate the battery. After this, noticed that every time phone went into standby, it won't wake after that and needed reboot. I thought it to be bug in the rom.
5. Downloaded 4.2.1 based rom listed here http://forum.xda-developers.com/showthread.php?t=2306461 and flashed it. Flash was successful followed by successful TP upgrade. Installed everything. Same problem noticed. Phone won't wake from standby. Needed to be rebooted.
6. I figured it to be a CPU governer problem left over from JellyDaemon v. 2.0. So installed juice defender and set the CPU governer to OnDemand. Frequency of reboots has reduced but the problem still persists.
Problem: The phone does not wake up when put to standby for a duration of 2-3 hours.
Any solutions to this? There are no other problems I am facing.
"I figured it to be a CPU governer problem left over from JellyDaemon v. 2.0. So installed juice defender and set the CPU governer to OnDemand. Frequency of reboots has reduced but the problem still persists.
Problem: The phone does not wake up when put to standby for a duration of 2-3 hours.
Click to expand...
Click to collapse
Looks like you yourself gave an answer to your problem. Don't enable Ondemand. if you still getting the problem. take a video of your problem and try posting along with a link to the video (I am not sure whether it is allowed). this way it will be easy to know what the problem is... hope i helped..
Sent from my CaNvAs HD using xda-developer app.
adizrox said:
Looks like you yourself gave an answer to your problem. Don't enable Ondemand. if you still getting the problem. take a video of your problem and try posting along with a link to the video (I am not sure whether it is allowed). this way it will be easy to know what the problem is... hope i helped..
Click to expand...
Click to collapse
Thanks for your reply. I will try your suggestion and see. In the meanwhile, I removed TWRP and flashed CWM 6.0.3.0 and fixed permissions with that. The phone did not reboot on its own for close to eight hours (which it was doing earlier at random). I thought problem was solved. But trying to go through contacts list (DW Contacts), phone rebooted on its own.
Can anyone tell me a method where you do a clean install and bring the phone to a factory fresh state. Something similar to tutorial by team overcome for galaxy tab. Frankly, that seems to be the only possible solution: Get the phone in a completely formatted factory fresh state and then install any other ROM.
SP flash tools
To get your phone to a default factory status. you have to flash the original rom using SP tools. Links to both can be found in the forum.
Finally, tired after numerous attempts, decided to take it to the service center. Asked them to update to 4.2.1. They had the same problem. After flashing, the phone just wouldn't boot past the boot animation.
They kept trying. After two hours, they gave it back to me saying there is a hardware problem which requires a main board change.
I had suspected all along and now I know I was right. I asked them about the time line. The answer I got was even more shocking. Minimum two weeks, but there are lots of hand sets awaiting main board since more than a month
I guess I am better off with current status (Ver .20 installed and rooted).
Seriously, this episode has seriously dented my faith in micromax as a brand. One can buy there phones and be happy with whatever has been packaged. Trying anything new can be dangerous.
Hi guys, I was using my phone messaging my friends. I put the phone down for about half an hour. When I pick it up again it is hot and will boot to the glowing slimbean logo (boot animation). I assume the phone ran out of battery, but even when I plug it in it will not boot past the logo. Do you guys have any idea as to what is going on, and how I can get my phone working again?
Try booting to recovery and wiping dalvik (hold both volume keys, plus power at the same time - release all after the Samsung logo appears). Phones don't usually freak out like this unless there's something the user either did or installed, especially those running stable slim roms.
On another note, the version you're running is very outdated; have you considered installing the last i777 slim rom, based on 4.2.2 (8.1)?
SteveMurphy said:
Try booting to recovery and wiping dalvik (hold both volume keys, plus power at the same time - release all after the Samsung logo appears). Phones don't usually freak out like this unless there's something the user either did or installed, especially those running stable slim roms.
On another note, the version you're running is very outdated; have you considered installing the last i777 slim rom, based on 4.2.2 (8.1)?
Click to expand...
Click to collapse
Thanks for your reply Steve!!
The reason why I'm still using 7.1 is because I was having battery problems on 8.0. I wasn't sure if the bug I had was fixed so I decided to stay behind. This was probably not the best choice but convenience and stability were something I wanted. I will try 8.1 after I backup my current setup if it works.
I believe its Google Now that has been causing me problems. Ever since I started using it my battery drains much faster, and the phone is hotter than usual. If wiping the cache works then I will delete it , otherwise I will probably have to wipe to factory which I really don't want to do.
OK so wiping the dalvik cache has allowed my phone to get past the bootloop. I get this message "Android is Upgrading.. starting apps" and its been stuck on it for a while. Any ideas?
This is weird, don't really know why - out of nowhere - your rom just all of a sudden won't boot.
And yes Google Now will kill ANY battery!
One other method would be to dirty flash 7.1 without doing any more wiping, if you want to keep it. If that doesn't work, full wipe/format system and start over.
Hope you get it working again!
Hi guys,
I was using Miui in mi pad 1 but it was really laggy IN VIDEOS and many apps including netflix wont even load in 4.4.4.
I moved to lineage 14.1 shield and apart from camera all were good.
i thought of upgrading to oreo and in middle i broke the device.
I went back to stock rom but i choose latest Chinese build 9.2.4.0 and use mi flash tool to boot it up. I was able to boot fine.
Again i went to custom rom dotos 2.5 and could see on locksreen showing phone charging slowly.
I kept for 3 hours and still same. I thought issue with the rom. WIPE EVERYTHING and again install lineage 15.1. It was able to boot fine but still no charging.
I kept my pad for hours to charge but still red light blinking, not booting up.
I removed the backpanel to remove battery (connector) and insert it again but still same.
I am not sure what to do now. If it will boot up i can go back to stock but it is not even booting to fastboot.
PLEASE HELP.
THANKS
Mont1jack said:
I removed the backpanel to remove battery (connector) and insert it again but still same.
Click to expand...
Click to collapse
Hello Is your problem fixed as I'm also experiencing the same
This also happened to me too in the past, my MiPad 2 is just in storage, still don't know how to fix it. Anyone here fixed this problem?