Develop Bugs

Off + plugged into ac charger = recovery?

Been having this problem since I rooted and installed the latest CWM recovery via rom manager. I'm currently on cm 7 rc1 if that helps
Sent from my HTC Vision using XDA Premium App

It's more of a "feature" than an issue I believe. Could be wrong.
I don't prefer it either, I would try another rom to see if it happens on there as well.

Yes this happens all the time it is known.. I hate it too I like to do a full charge while phone is off... not much can do except try to talk to dev...

IIRC, the image icon for when the phone is charging while its off is stored in the stock recovery. Since we flashed cwm over it, everytime we plug our phones in to charge while its off, the phone will call for it, make it go into recovery, and then we get cwm.

Get the same thing with CWM on gingervillain 1.5
A Gingervillain-ized G2

eioous said:
Get the same thing with CWM on gingervillain 1.5
A Gingervillain-ized G2
Click to expand...
Click to collapse
The rom has nothing to do with it. Its all with us flashing CWM over our stock recovery.
Working as intended.

Clockwork cycled from 3.1.0.1 (Purple) to 3.0.2.5 (Orange)

I just got a little bug from trying to undervolt/clock my phone. It froze on the spot so I pulled the battery. Restarted, then started getting Google Framework FCs. Rebooted into CWM (I currently sport purple) and fixed permissions. When I hit reboot system, my phone went dark and then booted into Orange clockwork. I hit reboot system on that, phone kept FC Launcher Pro and Google Framework. Rebooted again into purple CWM, fix permissions again, and now phone seems to be fine again.
I currently run SyndicateROM Frozen 1.2 with the Twilight Zone Kernel v1.1.1. I noticed within the Twilight Kernel's thread that it mentions having CWM 3.0.2.5 built in. Prior to installing this Kernel I have been running CWM 3.1.0.1 and the Genocide 1.2 Kernel. Before installing Twilight Zone I asked around, and was lead to believe from others I could install the kernel and have my CWM remain purple. Up to now it's been fine. I do wonder, however, is this supposed to happen? Does having CWM run in 2 different versions simultaneously pose a threat to my phone? Should I install another Kernel? Any help would be appreciated.
PS: I tried to search but only found "[Q] Phone stuck in CWM" and "Help! Bricked my phone" threads. Sorry in advanced if this has been posted before.
Edit: Rebooted again from a widget to see what's up ... booted into Orange, and when trying to boot from there, phone freezes. Managed to fix it by pulling battery and manually (Vol Down, Power, Cam buttons) entering CWM. Doing so boots me into Purple, and from there I can reboot my phone. This is making me nervous :3

Still would like help with this

Odin and start from scratch... i assume u have some weird corrupted/stale data...

There is a known issue with Clockwork Mod on some Epic 4G kernel setups, if you update your Clockwork Mod from the Redirector App, it will only update the one produced by "reboot into recovery" I don't know too many details about it, but you can look it up online if you are interesting. The best workarround is to always update clockwork mod by booting into recovery mode by shutting down, and booting it into the recovery. This only affects redirector.
You should be able to just update your Clockwork Mod from recovery mode. If it doesn't update properly, use Odin to do the update to Clockwork Recovery.

I don't know the tech terms but I am sure someone will post em lol. What it is... your phone has 2 recoverys. The kernel one and one you boot with 3 fingers. That's why its always said to boot with 3 fingers and not off of rom manager. It just simply boot looped off your kernel... there are real terms for these I just don't know em
Sent from my SPH-D700 using Tapatalk

slightly.stoopid said:
I don't know the tech terms but I am sure someone will post em lol. What it is... your phone has 2 recoverys. The kernel one and one you boot with 3 fingers. That's why its always said to boot with 3 fingers and not off of rom manager. It just simply boot looped off your kernel... there are real terms for these I just don't know em
Exactly right... I had this happening also and it never messed anything up. Just remeber to always use the 3 finger salute and everything will be fine
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Sent from my SPH-D700 using XDA App

Oh right, I posted this Yeah it is as everyone says, kernel uses Purple CWM and phone has Orange. Now orange is replaced with the new ACS Blue CWM. Same thing but no issues. I asked because it seemed that having 2 CWM on the phone was bound to mess things up. Not the case. At any rate thanks for the replies.

I am using ACS recovery too
Sent from my SPH-D700 using Tapatalk

[Q] GPS Fix and other stuff..

So I tried both the vision_wipe_efs and the manual dd command in terminal. Both didn't fix my GPS issues. I'm running a variant of CM7, but even on CM7 and IWLT CM7 I couldn't get a GPS fix.
I opened my phone to fix my hinge a while ago, could I have hit something that affected the GPS?
Also, when I turn off my phone, and plug it in, it boots up Clockwork.. Why?
Thanks for any help guys!

gaarry said:
So I tried both the vision_wipe_efs and the manual dd command in terminal. Both didn't fix my GPS issues. I'm running a variant of CM7, but even on CM7 and IWLT CM7 I couldn't get a GPS fix.
I opened my phone to fix my hinge a while ago, could I have hit something that affected the GPS?
Also, when I turn off my phone, and plug it in, it boots up Clockwork.. Why?
Thanks for any help guys!
Click to expand...
Click to collapse
Well, the GPS issue could be the issue I had. Have you tried replacing the gps_vision.so file from a stock ROM?
The clockworkmod issue is more than likely the a common issue with the recovery version you are using. What cwm version are you using? You might want to try 4ext recovery.
Sent from my HTC Vision using Tapatalk

tronmech said:
Well, the GPS issue could be the issue I had. Have you tried replacing the gps_vision.so file from a stock ROM?
The clockworkmod issue is more than likely the a common issue with the recovery version you are using. What cwm version are you using? You might want to try 4ext recovery.
Sent from my HTC Vision using Tapatalk
Click to expand...
Click to collapse
Also, the initial GPS fix after wiping efs takes several minutes but is faster after that.
Sent from my HTC Vision using XDA App

I'm using 5.0.2.7 cwm iirc. How do I replace the file?
I'll try the gps fix again, didn't know it took a while the first time. Thanks!

[Q] Black screen and no boot after flashing PA/CM10.1

Hi, this morning I encountered something which I haven't seen before in my 3 years or so of flashing roms on Android phones. The scenario was the standard process: Root with Odin > Install CWM with Odin > Copy Rom / gapps package to sdcard > Wipe & Install rom with CWM.
I rooted my Note II using CF Auto Root, all went fine, I flashed the latest Phil's touch CWM recovery using Odin which was also successful.
I had root access and was able to do a titanium backup of apps and messages/call logs. I successfully did a Nandroid backup of the stock rom.
After wiping data through CWM as per normal, I flashed the latest Utacka ParanoidAndroid and gapps. The flash was successful, but after rebooting, the 'Samsung Note II' splash screen only appeared briefly, then the image sheared and distorted and the screen went black, in less than three seconds.
I restored my nandroid backup and repeated the process, this time also formatting system, and installing CM10.1 nightly instead of PA. Again, I got a distorted splash screen then a black screen when trying to boot.
Can anyone think of a reason why my phone does not seem to be able to boot a custom rom?
Many thanks

I read on the forum someone else had a similar issue with cm as well
Sent from my GT-N7100 using xda app-developers app

koalauk said:
I read on the forum someone else had a similar issue with cm as well
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Really? I've tried searching xda, google and the CM forums and havent found anything relevant.

I had this problem recently and after some nice guys helping me out we conclude that the solution is to flash RedPill kernel as the culprit for this glitch is the stock kernel you previously had.

I had such issue with my Note2 too. I was advised to flash Thor kernel 0.15 too after flashing cm10.1 and gapps. And problem was solved. Now cm10.1 boots normal on my Note2.
Sent from my GT-N7100 using xda premium

Did you do a factor reset.
Sent from my GT-N7100 using xda app-developers app

[Easy Fix] Is TWRP asking for a password? Heres the fix

If TWRP is asking for a password and not booting do this: Re odin recovery twrp 2.4.4.0, wipe ALL data, odin twrp 2.6.1.0 back on to the device, reboot recovery, re-wipe data, flash desired COMPATIBLE rom.
To sum up what I found, new encryption added to 4.0+ of android encrypts user and important file partitions, updating recovery basically screws that all up. Your device has no way of accessing those files without the encryption key which was never explicitly made, its just a background feature to help protect your data.
I know this isnt much but atleast some people wont have to search around as much.
Now I cant take any credit for this, I also couldnt really find any user that took credit for it either.
Update: Something about gapps is the catalyst for this issue. After I flash gapps i get 15 mins of solid system performance, after that I start to get app download errors. The device will continue to function normally with snag and hiccups but after rebooting it goes right back to bootlock and asking for a P/W in TWRP. And of course I find a couple thread talking about this fix after, sorry for the redundancy I guess.
Can any confirm that Gapps may be causing this? Or better yet, what is actually causing this?

Jataadroid said:
If TWRP is asking for a password and not booting do this: Re odin recovery twrp 2.4.4.0, wipe ALL data, odin twrp 2.6.1.0 back on to the device, reboot recovery, re-wipe data, flash desired COMPATIBLE rom.
To sum up what I found, new encryption added to 4.0+ of android encrypts user and important file partitions, updating recovery basically screws that all up. Your device has no way of accessing those files without the encryption key which was never explicitly made, its just a background feature to help protect your data.
I know this isnt much but atleast some people wont have to search around as much.
Now I cant take any credit for this, I also couldnt really find any user that took credit for it either.
Update: Something about gapps is the catalyst for this issue. After I flash gapps i get 15 mins of solid system performance, after that I start to get app download errors. The device will continue to function normally with snag and hiccups but after rebooting it goes right back to bootlock and asking for a P/W in TWRP. And of course I find a couple thread talking about this fix after, sorry for the redundancy I guess.
Can any confirm that Gapps may be causing this? Or better yet, what is actually causing this?
Click to expand...
Click to collapse
im seeing people popping on on my phones forums (note 2) getting this message....and def not gapps...i have latest 4.3 gapps for weeks now and never seen this message
What rom you using?

PA 3.99 I have been running solid for 12 hrs now but I haven't rebooted since the last time I had to redo this process. It does fix it though.
All my apps have been installing and functioning fine. One thing I did different is I didn't flash BMS kernel. I havent checked the other threads reporting this issue but does any one know if they were using BMS?
Sent from my SPH-L710 using xda app-developers app

Jataadroid said:
PA 3.99 I have been running solid for 12 hrs now but I haven't rebooted since the last time I had to redo this process. It does fix it though.
All my apps have been installing and functioning fine. One thing I did different is I didn't flash BMS kernel. I havent checked the other threads reporting this issue but does any one know if they were using BMS?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Now I dont have TWRP asking for a password but PA_3.99 is stuck at the splash screen with the yellow sub. No longer an encryption issue it seems but now a new one entirely. At this point it exceeds my nooby knowledge of android and im stuck waiting for a kind soul to assist.
So please anybody have any idea? Or any idea how to define the issue better so i can get some help, it seems kernel or recovery related.
Is there a bootloader Im supposed to flash for 4.3? Im at a loss entirely.
Pls&thx

Just flash clockwork. Done
Sent from my SPH-L710 using xda app-developers app

I had the same problem, just once though. I booted into my ROM and all I needed to do was reinstall TWRP through Goomanager, then everything worked out fine. I updated from 2.6.0 to 2.6.1 at that point, so maybe that fixed my TWRP password problem. I did it about two weeks ago, so far no recovery issues. I used TWRP pretty intensely about a week ago to update to 4.3 and all went according to plan.

Shoot...I odin'd twrp 2.6.1.0 so many times I thought my phone would literally die. I didn't come from 2.6.0.1 ( not sure if that's the right) but instead several versions back.
Sent from my SPH-L710 using xda app-developers app

It wouldn't be a bad idea to implement a recovery password
Sent from my Nexus 5 using Tapatalk

alvintimothyjr said:
It wouldn't be a bad idea to implement a recovery password
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It's kind of already been done.

Really...info?
Sent from my Nexus 5 using Tapatalk