Greenify used to work perfectly for me, phone had to be reflashed with stock on the day before. (I was on stock before, and stock now)
I've tried both, the play store and the apk file, both just load a black screen and don't respond later.
I have not rooted since the reflash, if that is of any importance.
Galaxy Note 2, n7100. Stock 4.4.2
I have searched, and found 2 people with the same issue, but no solution.
Related
I recently rooted the note 3 vzw i chose to go with jasmine 1.9 which was pretty great but i just couldnt help but wonder what 2.3.4 looked like so when I entered safestrap to flash it I decided what the heck I'll just flash it to the stock delete the 1.9 slot and use the phones entire memory. I didnt even think to do a backup in safestrap. well I did that and now when I restart. I notice firts that safestrap now says disabled. the samsung note 3 screen comes up then its a black screen and the blue led stays on. i dont get any other activity from the phone. this is the first unit I have rooted since the thunderbolt so I'm a bit out of the loop. any advice would be greatly appreciated.
Note. I did make a back up in titanium before [email protected] fell apart and saved the file on my laptop. not sure if thats of much use as I believe its just data right?
poop
Ok so i may have jumped the gun a bit looks to me like i must install. 2.3.2 first as the other two files are quite small in comparison. anyone confirm this?
So, gave the screen mirroring a try today in the car (Appradio) connected to (Microsoft wireless display adaptor) got video, touch even worked, but the sound came out through the phone. Tried for a while, different apps, nothing, still through phone (Sound)
So tried my old lg g3 worked perfect first time, sound and full mirroring worked.
LEads me to believe its the phone.
Now the s6 is rooted, using unikernel atm.
ive tried using different roms, but they are all linked to samsung ones (Other phones you could have completely custom roms, samsung though apparently not) but the roms where the samsung mirroring is not present, theres no mirroring, tried a google search of an apk to add the lollipop native mirroring, couldnt find it.
So yeah, my last resort, help!! Been at this for five hours now and bricked my phone 3 times, someone please help, i just want to achieve mirroring with sound, i know its samsungs tech i should be going to but lets face it, you guys are armore useful than they are, plus the first person to solve it gets a few beers!!!
rgray99c said:
So, gave the screen mirroring a try today in the car (Appradio) connected to (Microsoft wireless display adaptor) got video, touch even worked, but the sound came out through the phone. Tried for a while, different apps, nothing, still through phone (Sound)
So tried my old lg g3 worked perfect first time, sound and full mirroring worked.
LEads me to believe its the phone.
Now the s6 is rooted, using unikernel atm.
ive tried using different roms, but they are all linked to samsung ones (Other phones you could have completely custom roms, samsung though apparently not) but the roms where the samsung mirroring is not present, theres no mirroring, tried a google search of an apk to add the lollipop native mirroring, couldnt find it.
So yeah, my last resort, help!! Been at this for five hours now and bricked my phone 3 times, someone please help, i just want to achieve mirroring with sound, i know its samsungs tech i should be going to but lets face it, you guys are armore useful than they are, plus the first person to solve it gets a few beers!!!
Click to expand...
Click to collapse
You're lucky you're able to mirror even video because when you have a modified kernel, it breaks screen mirroring. Every Samsung i've had I had to stay away from custom kernels because I mirror my screen often enough that i rather stay stock then lose that. Sometimes I could use wanam to fake system status but even then, the mirroring wasnt as smooth as it were on a stock kernel
So if I put the stock kernel back on it then it will work again?? Will I loose root if I do so?
If so is there anyway of keeping root when going back to stock kernel?
rgray99c said:
So if I put the stock kernel back on it then it will work again?? Will I loose root if I do so?
If so is there anyway of keeping root when going back to stock kernel?
Click to expand...
Click to collapse
Kernel and root and 2 different things. One is dependent on the other but the other is not. You can have stock kernel while rooted without a problem. Thats what I do.
You can flash stock kernel in recovery and you will stay rooted.
Well I managed to get screen mirroring to work. Stumbled across a rom called echorom. That appears to work whilst keeping both gear manager and root. So happy days. Figured I'd post the solution as not many do.
http://forum.xda-developers.com/showthread.php?p=62005518
A while back I rooted my Samsung Galaxy S4 GT-i9506, I didn't modify it other than that, I just rooted so I could hack games, install snapchat addons, etc. No Custom Roms/Kernels, none of that. Then my phone smashed and the screen stopped working, it took me about 2 months to get it fixed so when I got it back it was being really slow, all it needed was time but then the Samsung Sync was not working, so I tried to update, it said that I couldn't because my device was modified, so I eventually after doing a couple things, got my device to Android 5.0.1 Lolipop by Flashing with Odin and TWRP. When I first got onto 5.0.1 my wifi didn't work, my data does but not the wifi, I have been looking for at least a week for a fix for this, but nothing seems to work. I'm not sure if i'm missing something but i'm tired of this, i've been using a very smashed s3 and I want to use my S4 quite badly, If anyone got point me in the right direction or even help me out on this one, I would appreciate it heaps! When I hit the wifi button it doesn't get stuck on that grey/green or anything, it just doesn't turn on, it goes straight back to grey. I assume this is the modem but I have tried getting a newer modem and it hasn't worked, i'll be checking this for a while until this problem is resolved, any help would be very appreciated!
Alright guys, so I rooted 2 days ago. Easily one of the worst decisions i've made. I've rooted my s4 mini, and it's perfect. I love it. But, my s4 gave me a migraine. I couldn't handle it. Anytime I solved as problem, 2 more popped up. Today, I couldn't get in google play (connection error) and decided to unroot (through supersu) and factory reset. I still don't have access to google play, and my battery charges SUPER slow. 15% every 30 minutes or so (it happened after the root). So now, I have a factory reset, slow charging, no access to google play S4. Needless to say, I messed up. I decided to save myself another headache and just ask you guys for your opinions. What should I do?
CF-Auto-Root-jfltespr-jfltespr-sphl720.tar.md5 <----- What i used (after extract)
I have two Galaxy S2's; an everyday one and a spare. Both were stock ROMs and generally do everything I want a phone to do.
Recently, however, I needed to install an app (Mi Fit) that needs Android 4.4 upwards so I tried installing a new ROM on my spare S2. I should say that this was an unused, out of the box phone and everything worked fine with the stock ROM.
Initially, I tried to install a custom 7.1 ROM and it worked fine except that Mi Fit crashed every time I tried to pair the Mi Band. Also, TomTom would not work and several other apps failed to work. So, I tried another 7.1 ROM and then several 6 ROMs all to no avail. I had several boot loop issues during this and an "almost bricked" phone that would only go into Download mode but got over all of them. I then tried several 4.4 ROM's but Mi Fit crashes still when trying to pair the band. Also, the camera crashes when trying to load and all other camera apps that I have tried crash as well. One camera app says that the external SD card is not allowing third-party apps to access it. However, I have tried a couple of patches to cure this and they say the card is fine.
I have successfully loaded custom ROM's on other devices and think I (more or less) know what I am doing but am really stuck on this one.
Any help gratefully accepted.
Coaster750 said:
I have two Galaxy S2's; an everyday one and a spare. Both were stock ROMs and generally do everything I want a phone to do.
Recently, however, I needed to install an app (Mi Fit) that needs Android 4.4 upwards so I tried installing a new ROM on my spare S2. I should say that this was an unused, out of the box phone and everything worked fine with the stock ROM.
Initially, I tried to install a custom 7.1 ROM and it worked fine except that Mi Fit crashed every time I tried to pair the Mi Band. Also, TomTom would not work and several other apps failed to work. So, I tried another 7.1 ROM and then several 6 ROMs all to no avail. I had several boot loop issues during this and an "almost bricked" phone that would only go into Download mode but got over all of them. I then tried several 4.4 ROM's but Mi Fit crashes still when trying to pair the band. Also, the camera crashes when trying to load and all other camera apps that I have tried crash as well. One camera app says that the external SD card is not allowing third-party apps to access it. However, I have tried a couple of patches to cure this and they say the card is fine.
I have successfully loaded custom ROM's on other devices and think I (more or less) know what I am doing but am really stuck on this one.
Any help gratefully accepted.
Click to expand...
Click to collapse
This should be posted in Q&A and troubleshooting but no one seems to care about this.
Anyway, I got mi fit working fine until now. Last time i used mifit on los14.1 where quite long ago but i remember that it still work. I'm on 8.1.0 now amd mi fit still working fine
Disappointed no-one came to my aid but just to let you know I fixed the problem(s).
Coaster750 said:
Disappointed no-one came to my aid but just to let you know I fixed the problem(s).
Click to expand...
Click to collapse
It's not ideal you were not offered any assistance but sometimes the issue is too niche or obscure for anyone to have any advice.
What I think would be nice is instead of just saying "I fixed the problem", you detail exactly HOW you fixed it so in future someone with a similar issue searching for help can benefit from your success. What do you think?
As you say, very niche problem so I didn't elaborate. All I did was went back to basics, read the "Android Hacker's Toolkit" book from Jason Tyler and worked through everything until the problem went away. Oh, and reading loads of stuff on here and elsewhere. Not all of it is true (shock horror) but all is now well - and I am not 100% sure what the problem was so won't add to the pool of less than accurate information caught in the web.