So as stated in the title, I'm on ATT KK OTA, rooted and installed TWRP successfully. I can get in with ADB and FreeGee reboot to recovery, but I can't with hardware buttons.
Also a couple more questions:
Above your light sensor on the top of your phone do you have a hole that looks filled in?
And my notification LED keeps cycling between green and blue and won't stop. I'm assuming this would be a problem with the kernel since it's custom because installing TWRP requires a custom kernel. Any help with this?
One more: Is anyone able to view the ATT G2 section in the tapatalk app? It says there are no topics. I can see all the others fine, but not ATT although I can see the threads if I use a browser.
Sent from my LG-D800 using Tapatalk
EDIT: LED stopped flashing after installing an app, came back after reboot.
Tried installing another app, it didn't stop flashing.
EDIT: Using knock-on stopped it, not downloading the app.
Related
Whenever I install a new rom, whether its cm10.2, GE 4.3, etc, the screen off animation stops working after I reboot the phone. It just turns off normally. Not a big deal, but I couldnt find any info on this. Was wondering if anyone else has experienced this or even have the issue solved.. I clean install everytime I flash any rom. So im not sure whats causing this. Iniitially I thought i was freezing a wrong app or something, but I tried rebooting the phone without making any changes and it stops working. This has been happening for the past 10 or so flashes and I believe it started when i started flashing 4.3 roms.
You have to be in latest CWM or TWRP in order to flash Android 4.3 ROMs.
Update the recovery and you'll be ready to flash again.
Search for the recoveries in official websites.
Cheers.
Sent from my GT-I9505 using Tapatalk 4
I upgraded my phone from 4.3 MJE to 4.4.2 today with the instructions here http://youtu.be/tickH7zTEXQ and everything seemed to be working fine until i realised i have no play store app. So i went to the internet and downloaded an apk. When trying to sign in i get a message saying there is a problem communicating with the Google servers. I tried a few different apks but all were giving me the same message. Ive been searching for a fix for the past few hours to my own chagrin. The guy at the top of this page http://forum.xda-developers.com/showthread.php?t=2553357&page=802 seems to be having the same issue but i can not understand how to fix it like he did. If somebody could help that would be awesome.
I also realise i am not getting the safestrap splash screen on boot where i can choose to go into recovery. When i try to boot into recovery from the safestrap app itself or my power menu neither work. All the options on my power menu just turn the screen black and leave the sensor lights on which i find weird. Maybe if i can get into recovery and flash the de-odex rom first i can fix my problems? sorry i am not very experienced with this so i do not know much about it.
Fixed it by reverting back to stock MJE. I used odin to flash the Pit file and stock md5 for MJE. followed instructions by rob here http://forum.xda-developers.com/showthread.php?t=2790728& . It will unroot your device.
TL;DR - Installed bean's rooted kit kat, new safestrap, and Eclipse ROM 2.0.1. Phone essentially freezes when prompted to shut off or reboot and gets stuck there indefinitely. I also cannot install any apps via the play store reliably from Eclipse.
Hello everyone! I'm fairly new to rooting/flashing roms, and last night I used Bean's rooted kit kat to upgrade my N3 from 4.3 to 4.4. I went with de-odexed because from what I understood it was easier to change themes and whatnot that way (again, forgive me if I'm wrong, still new to all of this). Everything went great, I installed to stock rom slot, Odin detected my phone in DL mode, I installed the new firmware, it updated and loaded all the apps just fine, and I installed the new safestrap.
There was a problem however... Whenever I go to turn off or reboot the phone, the "shutting down" dialogue box comes up and it just gets stuck there. I timed it for about 20 minutes before finally just pulling the battery. It does this everytime I need to reboot the phone and I always have to end up pulling the battery.
EDIT: As of this morning the stock rom appears to no longer be having the reboot issue. My guess is that is just a bug in a Eclipse at this point.
Thinking it might be just a weird bug, I made a partition in ROM slot 2 (ROM slot 1 was where my 4.3 was and I hadn't deleted it yet) and installed Eclipse 2.0.1. When I booted into it and logged into my Google account to recover all my apps like I did just did with the stock rom slot, all the apps que'd up, but nothing showed as installing. I thought that maybe I had kinda just overwhelmed the phone with downloads and went into the play store to stop the que. I started installing about 3 apps at a time to see if it worked better, and I ran into the same issue. Usually when you click "install" on an app, it will show the download process and then start installing to your phone. Mine goes straight to install and gets stuck on an endless loading bar, with no way to cancel or stop it without a reboot.
Rebooting is also having the same issue as before. I cannot shut off or restart the device without it locking into the shutting down dialogue box.
1. Did installing a de-odexed version cause any problems that I wouldn't have had with an odexed?
2. If so, I can follow the same methods I did to install bean's kit kat and reinstall the odexed version? Or would I have to somehow go back to 4.3 first?
3. Are there any other known fixes I should try?
C3PH0 said:
TL;DR - Installed bean's rooted kit kat, new safestrap, and Eclipse ROM 2.0.1. Phone essentially freezes when prompted to shut off or reboot and gets stuck there indefinitely. I also cannot install any apps via the play store reliably from Eclipse.
Hello everyone! I'm fairly new to rooting/flashing roms, and last night I used Bean's rooted kit kat to upgrade my N3 from 4.3 to 4.4. I went with de-odexed because from what I understood it was easier to change themes and whatnot that way (again, forgive me if I'm wrong, still new to all of this). Everything went great, I installed to stock rom slot, Odin detected my phone in DL mode, I installed the new firmware, it updated and loaded all the apps just fine, and I installed the new safestrap.
There was a problem however... Whenever I go to turn off or reboot the phone, the "shutting down" dialogue box comes up and it just gets stuck there. I timed it for about 20 minutes before finally just pulling the battery. It does this everytime I need to reboot the phone and I always have to end up pulling the battery.
EDIT: As of this morning the stock rom appears to no longer be having the reboot issue. My guess is that is just a bug in a Eclipse at this point.
Thinking it might be just a weird bug, I made a partition in ROM slot 2 (ROM slot 1 was where my 4.3 was and I hadn't deleted it yet) and installed Eclipse 2.0.1. When I booted into it and logged into my Google account to recover all my apps like I did just did with the stock rom slot, all the apps que'd up, but nothing showed as installing. I thought that maybe I had kinda just overwhelmed the phone with downloads and went into the play store to stop the que. I started installing about 3 apps at a time to see if it worked better, and I ran into the same issue. Usually when you click "install" on an app, it will show the download process and then start installing to your phone. Mine goes straight to install and gets stuck on an endless loading bar, with no way to cancel or stop it without a reboot.
Rebooting is also having the same issue as before. I cannot shut off or restart the device without it locking into the shutting down dialogue box.
1. Did installing a de-odexed version cause any problems that I wouldn't have had with an odexed?
2. If so, I can follow the same methods I did to install bean's kit kat and reinstall the odexed version? Or would I have to somehow go back to 4.3 first?
3. Are there any other known fixes I should try?
Click to expand...
Click to collapse
I read your post a couple times and I think you may be using the wrong Safestrap. I could be wrong.
Use stable Safestrap 3.65 for jellybean roms and Safestrap 3.72 or 3.75 for nc2/nc4 roms.
I'm running Eclipse 2.0.1 on Safestrap 3.75 right now and have zero reboot problems.
Sent from my Eclipsed Note 3 using XDA Premium
Harleydroid said:
I read your post a couple times and I think you may be using the wrong Safestrap. I could be wrong.
Use stable Safestrap 3.65 for jellybean roms and Safestrap 3.72 or 3.75 for nc2/nc4 roms.
I'm running Eclipse 2.0.1 on Safestrap 3.75 right now and have zero reboot problems.
Sent from my Eclipsed Note 3 using XDA Premium
Click to expand...
Click to collapse
Yup! This was it. I installed 3.75 and re-flashed. I feel slightly dumb for not thinking of that but I'm so happy to have a functional phone again. Thank you very much!
C3PH0 said:
Yup! This was it. I installed 3.75 and re-flashed. I feel slightly dumb for not thinking of that but I'm so happy to have a functional phone again. Thank you very much!
Click to expand...
Click to collapse
You bet bud
Sent from my Eclipsed Note 3 using XDA Premium
Last night I got a Galaxy S5 as an anniversary gift and successfully rooted and installed TWRP and Alliance Rom 4.4.2 and everything is going smooth for the most part except for fingerprint scanning.
When going to define a new fingerprint or access fingerprint options it gives an error: "An error has occurred with the fingerprint sensor...".
The process I took to mod it was use Odin to downgrade the kernel back to a towelroot friendly one, use towelroot to gain root, install busybox, flash previous kernel back using Odin, installed Safestrap (nandroid backed up), installed Alliance Rom via Safestrap recovery, installed SuperSU (disabled KNOX) and here I am. Does disabling KNOX cause the issue?
Any advice would be greatly appreciated! Thanks XDA
Yes I have searched forums and google before posting. Yes I wiped prior to installing the rom.
Unrelated problem: the phone also does not shut down. When going to shut down the samsung shut down animation plays then the screen goes black and just hangs there. The LED shows a blue light and the bottom soft keys are lit up and it will stay that way until I pull the battery. Any advice?
Hey guys,
So I've got a problem. When I had originally rooted my phone in the beginning, I hadn't installed safestrap; I installed everything else: busybox, superuser, etc. So I kept on regularly using my phone and what not, updating and making sure I kept root. I was able to follow muniz_ri's tutorials to stay up to date and keep root. So eventually I was on OE1 stock rooted rom and had stopped there (accidentally accepted an OTA update after OE1 so I quickly froze the update thing [forget what it's called] through TiBU, hence not being on the most current firmware).
I wanted Snapprefs but needed Xposed. And to get Xposed, you need safestrap (from my understanding). I followed this to get safestrap (I think that's what the overall goal of the tutorial was for) and got safestrap working. Then, tried to install xposed using this and this. Successfully got the app, but then it said something along the lines of "you have not installed the framework" or something like that (that would be the zip file that I had to download right? The file that came from following the flow chart?). Used safestrap to install the framework (aforementioned zip file), then rebooted. However, after the Samsung Galaxy S5 menu and the safestrap menu, the screen just stays black. There is nothing. When I have my phone connected to the computer, the computer makes its jingle like it recognizes it (however, nothing comes up on the computer), the phone stays black for 2-3 minutes maybe, then boots into recovery mode (not safestrap recovery but stock recovery, where you use the volume buttons). I did a wipe data/factory reset (or whatever the option is called) in the stock recovery menu hoping it would fix something but it didn't. Just trying to include as much info as possible. Would flashing with this in Odin help? Read somewhere that it would put me back at square one so I could do everything over again, which I am not opposed to. However, I thought you couldn't downgrade from OE1 or anything higher?
I'm at a loss as to what to do next. Searched everywhere but couldn't find anyone with the same problem as me. Any help would be appreciated.
Thanks guys!
P.S. Sorry for going parentheses crazy
Found out what to do right after posting. Had to flash the BOE1 factory tar image in ODIN so back to stock, unrooted with all this bloat
Will be checking back periodically in hopes of a root method for latest firmware.