I'm new to Xposed but I've tried to read everything I can about it before posting.
I've Installed the Framework, hard reboot, installed Modules and hard reboot.
Yet Still nothing happens.
I've tried XPrivacy and GravityBox. XPrivacy Will tell me that the module isn't activated when it is. Gravity Box will tell me the frameworkit's self isn't installed.
I'm at a loss of what to do. Thanks to anyone in advance for any and all help.
When you install the frame work do a soft reboot instead of a regular reboot it will work then.
Sent from my XT1058 using Tapatalk 4
Install and activate in the recovery system write mode. Then it should stick
Keller_psycho said:
When you install the frame work do a soft reboot instead of a regular reboot it will work then.
Sent from my XT1058 using Tapatalk 4
Click to expand...
Click to collapse
Thanks this worked. But now I have this strange Icon in the top right hand corner that looks like an SD card with a red circle with a line through it and it over lapse my Wifi icon in the notification bar.
Also do you know how to reorder things in quicksettings with gravitybox?
Icon000 said:
Thanks this worked. But now I have this strange Icon in the top right hand corner that looks like an SD card with a red circle with a line through it and it over lapse my Wifi icon in the notification bar.
Also do you know how to reorder things in quicksettings with gravitybox?
Click to expand...
Click to collapse
If you installed the MotoXposed app and activated it, it defaults to having the gap between the WiFi icon and the Provider network icons, but unfortunately, it doesn't fix the gap, but instead overlaps them. The icon that looks like an sd card with a red circle is your sim card saying it isn't working. The phone seems to boot faster than the sim card can initialize and shows the sim not working for a moment, then finds the signal.
Xposed isn't Holding After Reboot
I know I was told earlier that I should be doing a soft boot but does that mean that I will have to reinstall Xposed every time I do a reboot?
Also it seem since I have installed Xposed that I've had a few apps consistently go non responsive at same point in using them. Example: I have the premium app for these forums but when ever I try to view any particular thread the app will go non responsive and need to restart.
Icon000 said:
I know I was told earlier that I should be doing a soft boot but does that mean that I will have to reinstall Xposed every time I do a reboot?
Also it seem since I have installed Xposed that I've had a few apps consistently go non responsive at same point in using them. Example: I have the premium app for these forums but when ever I try to view any particular thread the app will go non responsive and need to restart.
Click to expand...
Click to collapse
The soft reboot was mentioned as it allows you to stay booted with the root privileges, Once you have everything set the way you would like it, then just do a normal reboot. If for some reason you want to make a change or try a new module you will have to reboot to recovery to use root. I have not had any apps have issues with being non responsive. You can try uninstall/reinstall of the app, clearing it's data/cache, or going and seeing what is all running at the time on your phone, then disable or uninstall programs you don't want running all the time.
When you say rebooting to recovery odd that an option in the Xposed framework installer or am I doing this during the boot process?
Sent from my XT1058 using XDA Premium 4 mobile app
Icon000 said:
When you say rebooting to recovery odd that an option in the Xposed framework installer or am I doing this during the boot process?
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You would just turn off the phone, then hold Power+Vol down then press Vol down to get to recovery, then press Vol up to select it. This will boot your phone with root.
stillthisguy said:
You would just turn off the phone, then hold Power+Vol down then press Vol down to get to recovery, then press Vol up to select it. This will boot your phone with root.
Click to expand...
Click to collapse
Thanks
stillthisguy said:
You would just turn off the phone, then hold Power+Vol down then press Vol down to get to recovery, then press Vol up to select it. This will boot your phone with root.
Click to expand...
Click to collapse
I know this seems obvious but I wasn't quite getting how the X works. Thanks for the comment. Makes sense now
So I have it working while in recovery but if I reboot, everything goes away. From reading, this should not be the case. Am I reading the comments incorrectly?
sankyou said:
I know this seems obvious but I wasn't quite getting how the X works. Thanks for the comment. Makes sense now
So I have it working while in recovery but if I reboot, everything goes away. From reading, this should not be the case. Am I reading the comments incorrectly?
Click to expand...
Click to collapse
When setup xposed, any time I make a change, I reboot with write protection off and make sure everything is still working, then boot normally. Never had any issues when doing it that way.
stillthisguy said:
When setup xposed, any time I make a change, I reboot with write protection off and make sure everything is still working, then boot normally. Never had any issues when doing it that way.
Click to expand...
Click to collapse
Yes I redid everything and did that and it stuck. Thanks for the advice - it worked perfectly! Man this phone rocks now and I don't even have to mess with roms....
Related
Bit of a conundrum here - About an hour and a half ago my phone was working ok, albeit a bit slow.
I tried opening GoSMS, and it kept FCing. Didn't think anything of it, as I had a few memory hungry apps open as well (Angry Birds/Firefox), but rather than mess around with a task manager to kill the offending apps, opted for a soft boot using the power switch.
Upon rebooting the phone completes the boot animation, then at the point it would normally present me with a lockscreen and SIM unlock prompt, the screen goes black. Every 10-15 secs or so the familiar buzz, buzz-buzz-buzz of an app FCing can be felt. The power button is effective only to hold for a soft reboot, and the 3 buttons at the bottom (2 soft, 1 physical) have no effect other than to permanently illuminate the soft keys.
I've tried rebooting with every combination of the SIM card/external SD card removed, with no change.
Any suggestions?
Just remove battery from the phone. Reinsert it after 15 min and boot your device.
I wish you Good Luck !
Sent from my GT-I9003 using XDA App
rex4u said:
Just remove battery from the phone. Reinsert it after 15 min and boot your device.
Click to expand...
Click to collapse
No luck unfortunately - left it out for half an hour or so, and still nothing (
boot into recovery and do a reset, if that fails, flash thru odin
Boot into recovery and tell us the error you are getting.....sounds like the partition is F'd!
azzledazzle said:
boot into recovery and do a reset, if that fails, flash thru odin
Click to expand...
Click to collapse
Yup, a factory reset finally worked. I just need to remember to keep a copy of the Titanium Backup apk on the SD card. Install, then restore the TB Pro apk, reset and leave TBP restoring all the apps!
Thanks for your help guys, if someone can mark this as solved, then brilliant )
Roll on CM7!
how to catch the error?
Hi all,
same problem here (when switching the phone on this mornig).
I've already experienced this once and solved via reset, as mentioned before.
I think maybe it's something related to an app (installed some new yesterday evening), and it vould be interesting to understand the reason of this behaviour, so I was wondering how I can get the error (or read a log) to get what's not working properly.
I will have time to investigate in the afternoon, so can you give me any suggestion on how I can look after this (I'm relatively new to android)?
thank you
I've tried many different things in alot of the threads I've read on this forum and nothing is working. I tried using the One-Click root on my Droid and it didn't work, come to find out, it was an outdated method for the Droid 3. It messed up my phone. My apps constantly crash. My texts disappear, then sometimes reappear switching the place of the texts randomly. When I reset from settings, it restarts phone, but nothing is reset. It won't let me check my e-mails(G-mail). I can hardly do anything. I've tried flashing back using the AP Fastboot method from psouza(spelling?). On my phone it says Battery OK/Program OK/USB Connected. So I run the "CLICK HERE - Flash Verizon DROID 3 OTA 5.6.890 to phone.bat". It failed.
Then I tried ovelayers method. Everything seems to go good. And I was happy! But when it rebooted, it took me to the android triangle screen. SO I selcected reboot. And absolutely nothing changed. Am I Missing a step? I also tried doing it again, but after it went to traingle android screen, I selected the update from the SD card, installed it, rebooted, and STILL nothing. Nothing changes. Ever. Nothing is working. Please help. I tried being as descriptive as possible so that it answers most potential questions.
*Edit* I've also tried the RDS Lite method. Crashes on step 3.
Phone specs: Version: 5.7.906.XT862.Verizon.en.US
Kernel: 2.6.35.7-g5fa4155
Android 2.3.4
download full system file
http://dev-host.org/uEA
put it on your sdcard, and if you are on "android triangle screen" go to menu
pickup update, select the downloaded file and install it.
After will all done push reboot from menu
thats all
Make sure you use the sbf for. 906 and not the one for. 890
http://d-h.st/mvX
niko99 said:
download full system file
put it on your sdcard, and if you are on "android triangle screen" go to menu
pickup update, select the downloaded file and install it.
After will all done push reboot from menu
thats all
Click to expand...
Click to collapse
I have the full system file already. That's what I tried using to update. The problem doesn't lie there though. The problem is that no matter what I do, the phone never resets. It's on right now. If I uninstall apps right now and restart my phone, they'll still be there. Likewise with installing them. If I text anyone, when I restart my phone, that conversation will be gone. Likewise with call logs and everything else. The phone literally after every restart goes back to the same position it was when I badly rooted the first time. No resets, recoveries, hard resets, flashes, etc have worked thus far. I've used ALL the one click SBF versions also, just to be thorough. The phone literally will not change. What I need is something similar to a computer. I need to completely wipe it. Then I need to completely reinstall it from scratch. Just like reformatting your hard drive. I've heard that there has really been no case of an unbrickable phone, that there is always a way to fix it; but this far, I haven't found anybody that hasn't had their phone fixed. Even those that have had similar issues fixed it, and I've tried the methods they've provided to no avail.
xJolly said:
I have the full system file already. That's what I tried using to update. The problem doesn't lie there though. The problem is that no matter what I do, the phone never resets. It's on right now. If I uninstall apps right now and restart my phone, they'll still be there. Likewise with installing them. If I text anyone, when I restart my phone, that conversation will be gone. Likewise with call logs and everything else. The phone literally after every restart goes back to the same position it was when I badly rooted the first time. No resets, recoveries, hard resets, flashes, etc have worked thus far. I've used ALL the one click SBF versions also, just to be thorough. The phone literally will not change. What I need is something similar to a computer. I need to completely wipe it. Then I need to completely reinstall it from scratch. Just like reformatting your hard drive. I've heard that there has really been no case of an unbrickable phone, that there is always a way to fix it; but this far, I haven't found anybody that hasn't had their phone fixed. Even those that have had similar issues fixed it, and I've tried the methods they've provided to no avail.
Click to expand...
Click to collapse
Can you install bootstrap? That way you can wipe data, and there should be no way it boots back like nothing has changed
http://db.tt/pi5c484a
Edit: or, boot into recovery with x+power (or m+power i always forget) and wipe/factory from there
DoubleYouPee said:
Can you install bootstrap? That way you can wipe data, and there should be no way it boots back like nothing has changed.
Edit: or, boot into recovery with x+power (or m+power i always forget) and wipe/factory from there
Click to expand...
Click to collapse
I will attempt that now. How is it used? I can build pc's and am rather intelligent in the IT of macs and pc's. But haven't had to do much with Androids till now. Lol. I've tried the wipe/factory method already. I understand that .apk is the file extension for Google Play apps, and I can install it via the SD card, but what do I do from then?
*EDIT* It's installed, it has bootstrap recovery and reboot recovery. Reboot does nothing. Bootstrap says there's an error running a command. Looks like a directory about files and hashcodes. "Working Directory: null/Environment: null".
xJolly said:
I will attempt that now. How is it used? I can build pc's and am rather intelligent in the IT of macs and pc's. But haven't had to do much with Androids till now. Lol. I've tried the wipe/factory method already. I understand that .apk is the file extension for Google Play apps, and I can install it via the SD card, but what do I do from then?
*EDIT* It's installed, it has bootstrap recovery and reboot recovery. Reboot does nothing. Bootstrap says there's an error running a command. Looks like a directory about files and hashcodes. "Working Directory: null/Environment: null".
Click to expand...
Click to collapse
First you need root access. Use Motofail if you haven't:
https://www.dropbox.com/s/wpl88mwm6eilhe6/motofail.exe
Open bootstrap, press bootstrap recovery, afterwards press reboot recovery.
If it doesn't work, shutdown your phone, hold X and press power and do it from there
DoubleYouPee said:
First you need root access. Use Motofail if you haven't:
Open bootstrap, press bootstrap recovery, afterwards press reboot recovery.
If it doesn't work, shutdown your phone, hold X and press power and do it from there
Click to expand...
Click to collapse
Figured. My phone won't root. Like I said, nothing will change about it.
xJolly said:
Figured. My phone won't root. Like I said, nothing will change about it.
Click to expand...
Click to collapse
Ok so what about x+power?
DoubleYouPee said:
Ok so what about x+power?
Click to expand...
Click to collapse
No. It doesn't work. I've tried that.
xJolly said:
No. It doesn't work. I've tried that.
Click to expand...
Click to collapse
So you did wipe/factory reset from recovery and it still boots like nothing happened? I'm not sure how thats possible.. stock recovery shouldnt have anything to do with what you messed up in your rom. Maybe for some reason your phone is unable to write data anymore
DoubleYouPee said:
So you did wipe/factory reset from recovery and it still boots like nothing happened? I'm not sure how thats possible.. stock recovery shouldnt have anything to do with what you messed up in your rom. Maybe for some reason your phone is unable to write data anymore
Click to expand...
Click to collapse
I'm going to record a video. And show you the multiple things that happens. I'll have to PM it to you though, and anyone who wants to see it.
I remember someone else having a similar issue on their device. Since I'm home sick today I'll see if I can find the thread and if it ever got solved
Sent from my XT860 using xda premium
Just saw your vid and its exactly as you say. I don't know whats going wrong..
Writing yo your internal might not be the same as writing to your data partition.. I don't see why else wiping from recovery would fail since that part should be unaffected.
You said sbf says its succesful however on your screenshot i see errors.
DoubleYouPee said:
Just saw your vid and its exactly as you say. I don't know whats going wrong..
Writing yo your internal might not be the same as writing to your data partition.. I don't see why else wiping from recovery would fail since that part should be unaffected.
You said sbf says its succesful however on your screenshot i see errors.
Click to expand...
Click to collapse
There's only errors for the click here to flash method, however, the ovelayer method screenshot says there are no errors, unless I am missing something there.
xJolly said:
There's only errors for the click here to flash method, however, the ovelayer method screenshot says there are no errors, unless I am missing something there.
Click to expand...
Click to collapse
You're right. No way you can send it back for replacement? Your phone seems stock
DoubleYouPee said:
You're right. No way you can send it back for replacement? Your phone seems stock
Click to expand...
Click to collapse
Well, I don't have insurance on it, as I had gotten it from a friend. So, no. Not without paying an arm and a leg, at which point I'd pay for a new phone instead. I just really wish this could be fixed. I've heard no phone was unbrickable. AM I THE PRODIGY?!
I tried searching the threads but couldn't find one with a problem like exactly mine. Sorry if I was a lousy searcher, but here goes:
1 I had TWRP and TrickDroid 5.5.1 installed. Working fine.
2 Downloaded TrickDroid 6.0.1, went into recovery, wiped everything/factory reset etc. and installed the new ROM, rebooted
3 Working fine but there is no root
4 Tried wiping everything again and reflashing the same ROM. Rebooted. Same thing: ROM is working but there's no root
5 Read somewhere that flashing a different kernel might work, so I flashed Bulletproof 1.10 through TWRP. At the end of the installation of the kernel, right before reboot, TWRP said that my root seemed to be broken and asked me if I wanted to fix it. I said yes. As soon as I said yes (by swiping), phone shut off. Now it won't even start so I can't get into recovery. Pressing Volume-down+Power won't get me into fastboot either.
—The only sign of life is this: when I long press the power button, the home and back buttons will blink as long as I continue pressing it. When I release, nothing happens.
—When I plug the phone to PC, it sees it as a "HTC MTP device" and looks for the drivers but fails to find them.
I had never any trouble with flashing ROMs before so I got lazy with time, I don't have any nandroid backup, though since I can't get even into fastboot I guess that's the least of my problems?
Please help; did I really just brick my phone?
Just happened to me too man, I'm not sure what to do! Sorry to hijack your thread, just looking for answers too.
---------- Post added at 10:10 PM ---------- Previous post was at 10:03 PM ----------
kuboa said:
I tried searching the threads but couldn't find one with a problem like exactly mine. Sorry if I was a lousy searcher, but here goes:
1 I had TWRP and TrickDroid 5.5.1 installed. Working fine.
2 Downloaded TrickDroid 6.0.1, went into recovery, wiped everything/factory reset etc. and installed the new ROM, rebooted
3 Working fine but there is no root
4 Tried wiping everything again and reflashing the same ROM. Rebooted. Same thing: ROM is working but there's no root
5 Read somewhere that flashing a different kernel might work, so I flashed Bulletproof 1.10 through TWRP. At the end of the installation of the kernel, right before reboot, TWRP said that my root seemed to be broken and asked me if I wanted to fix it. I said yes. As soon as I said yes (by swiping), phone shut off. Now it won't even start so I can't get into recovery. Pressing Volume-down+Power won't get me into fastboot either.
—The only sign of life is this: when I long press the power button, the home and back buttons will blink as long as I continue pressing it. When I release, nothing happens.
—When I plug the phone to PC, it sees it as a "HTC MTP device" and looks for the drivers but fails to find them.
I had never any trouble with flashing ROMs before so I got lazy with time, I don't have any nandroid backup, though since I can't get even into fastboot I guess that's the least of my problems?
Please help; did I really just brick my phone?
Click to expand...
Click to collapse
Dude, just hold the volume down button and then press the power button...the back and home button will keep flashing and then it will stop...should take you into fastboot..navigate to recovery and try to load a rom up using the SD card mount method...hope it works out for you man!
DarknessTM said:
Just happened to me too man, I'm not sure what to do! Sorry to hijack your thread, just looking for answers too.
Click to expand...
Click to collapse
No need to apologize, that's why we're here. Please report back if you can find a solution.
Google told me that HTC's RUU tool could possibly help unbrick it, so I've downloaded the European variant ("RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4"). I fiddled a bit in the Device Manager in my PC and somehow got it to recognize the phone as "My HTC" under "Android ...", then ran the program. HTC logo appeared on the phone's screen so I got excited but after 10 minutes of waiting RUU told me it was the wrong variant and exited. Back to nil. I'm now downloading another variant of the RUU. We'll see if it helps. (I can't for the life of me figure out how to make my PC recognize the phone again though; I'm back to "MTP device, failed to install drivers" phase. Frustrating.)
kuboa said:
No need to apologize, that's why we're here. Please report back if you can find a solution.
Google told me that HTC's RUU tool could possibly help unbrick it, so I've downloaded the European variant ("RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4"). I fiddled a bit in the Device Manager in my PC and somehow got it to recognize the phone as "My HTC" under "Android ...", then ran the program. HTC logo appeared on the phone's screen so I got excited but after 10 minutes of waiting RUU told me it was the wrong variant and exited. Back to nil. I'm now downloading another variant of the RUU. We'll see if it helps. (I can't for the life of me figure out how to make my PC recognize the phone again though; I'm back to "MTP device, failed to install drivers" phase. Frustrating.)
Click to expand...
Click to collapse
Dude, just hold the volume down button and then press the power button...the back and home button will keep flashing and then it will stop...should take you into fastboot..navigate to recovery and try to load a rom up using the SD card mount method...hope it works out for you man!
DarknessTM said:
Dude, just hold the volume down button and then press the power button...the back and home button will keep flashing and then it will stop...should take you into fastboot..navigate to recovery and try to load a rom up using the SD card mount method...hope it works out for you man!
Click to expand...
Click to collapse
That doesn't work for me unfortunately, the capacitive buttons just keep on flashing. I can get my PC to recognize it as "HTC Android Interface" but the second RUU failed, too. Glad yours got fixed, though.
kuboa said:
That doesn't work for me unfortunately, the capacitive buttons just keep on flashing. I can get my PC to recognize it as "HTC Android Interface" but the second RUU failed, too. Glad yours got fixed, though.
Click to expand...
Click to collapse
hold it under a bright light and try again
kuboa said:
That doesn't work for me unfortunately, the capacitive buttons just keep on flashing. I can get my PC to recognize it as "HTC Android Interface" but the second RUU failed, too. Glad yours got fixed, though.
Click to expand...
Click to collapse
if you can get still have adb access use Hasoon's AIO Toolkit to reboot to bootloader/recovery and go from there. otherwise hold power and volume down button with the screen facing a very bright light.
Aldo101t said:
hold it under a bright light and try again
Click to expand...
Click to collapse
Whoa! That really did it. Excuse me for swearing but what the f* a bright light has to do with anything?
Thanks, anyways! Phew.
(Now I should figure out why I'm losing my root when flashing this ROM)
kuboa said:
Whoa! That really did it. Excuse me for swearing but what the f* a bright light has to do with anything?
Thanks, anyways! Phew.
(Now I should figure out why I'm losing my root when flashing this ROM)
Click to expand...
Click to collapse
just reflash superuser, i think it was left out by mistake
Aldo101t said:
just reflash superuser, i think it was left out by mistake
Click to expand...
Click to collapse
I tried that but didn't work. Anyways, that's a far less scary problem than a bricked phone, I'll figure it out. Thanks again.
Aldo101t said:
hold it under a bright light and try again
Click to expand...
Click to collapse
hi there.. im having the same problems. i cant access recovery and my computer wont let me access the files on my phone neither. when i boot on the phone it goes right into the bootloader and won't go anywhere else. please help! many many thanks
Bricked after attempted TrickDroid update
I’m having the same problem.
Attempted to update Trickdroid 6.0.1 to 7.0 last night.
My phone now constantly hangs on the boot screen.
I can get to the fastboot and bootloader menus via long press volume down and power but anything from here simply reboots the phone back to the boot screen.
I’ve tried connecting the phone to the PC and using Fastboot and the One all in one kit but the device is never recognised.
Basically I’ve bricked my phone and need help!!
kuboa said:
I tried searching the threads but couldn't find one with a problem like exactly mine. Sorry if I was a lousy searcher, but here goes:
1 I had TWRP and TrickDroid 5.5.1 installed. Working fine.
2 Downloaded TrickDroid 6.0.1, went into recovery, wiped everything/factory reset etc. and installed the new ROM, rebooted
3 Working fine but there is no root
4 Tried wiping everything again and reflashing the same ROM. Rebooted. Same thing: ROM is working but there's no root
5 Read somewhere that flashing a different kernel might work, so I flashed Bulletproof 1.10 through TWRP. At the end of the installation of the kernel, right before reboot, TWRP said that my root seemed to be broken and asked me if I wanted to fix it. I said yes. As soon as I said yes (by swiping), phone shut off. Now it won't even start so I can't get into recovery. Pressing Volume-down+Power won't get me into fastboot either.
—The only sign of life is this: when I long press the power button, the home and back buttons will blink as long as I continue pressing it. When I release, nothing happens.
—When I plug the phone to PC, it sees it as a "HTC MTP device" and looks for the drivers but fails to find them.
I had never any trouble with flashing ROMs before so I got lazy with time, I don't have any nandroid backup, though since I can't get even into fastboot I guess that's the least of my problems?
Please help; did I really just brick my phone?
Click to expand...
Click to collapse
Deano1889 said:
I’m having the same problem.
Attempted to update Trickdroid 6.0.1 to 7.0 last night.
My phone now constantly hangs on the boot screen.
I can get to the fastboot and bootloader menus via long press volume down and power but anything from here simply reboots the phone back to the boot screen.
I’ve tried connecting the phone to the PC and using Fastboot and the One all in one kit but the device is never recognised.
Basically I’ve bricked my phone and need help!!
Click to expand...
Click to collapse
go to fastboot, use HTC all in one kit by hasoon to flash TWRP, go in twrp, Wipe everything including data, system, cache, dalvik cache, again go on HTC kit and put command of adb sideload, go on TWRP advanced menu and sideload roam. once sideload gets transferred, it will start installing and try different rom like ARHD 10.1
I can't belive it, but the bright light thing actually worked for me!
Thanks!
I was in the same situation with an HTC logo and flashing back and home keys. When I tried volume down + power under a bright light, it came back to life in bootloader. Not sure what the bright light has to do with it but glad it worked.
Bright light solution is from twrp sleep bug.. I read it before.. Good luck
Sent from my HTC One using xda app-developers app
ayan15 said:
Bright light solution is from twrp sleep bug.. I read it before.. Good luck
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
The bright light trick is not a bug, and it has nothing to do with TWRP. It happens because HTC built in a "pocket protection" so that the phone will not reboot on its own in your pocket. The proximity sensor needs light shining on it for a hard reboot to work. (Sometime they're not sensitive enough and it takes a brighter light than you would expect)
Sent from my HTC One using XDA Premium 4 mobile app
Just installed the latest update (0621), and now when I try to do anything to open the UI from the booted splash screen (lock image) I get the message above.
I cannot shutdown or reboot to go back to an earlier version, I can only power off with the power switch.
If I try to use the reboot option from the splash screen, the recovery option has disappeared.
Starting the unit again produces the same result.
My latest boot got me the animated logo then presented a solid light blue screen.
How do I get it back so I can install the earlier build that was working while you fix this problem.
Right now the unit is useless, absent making up a new SD card. I have lots of stuff on the current card so would prefer not to do this.
This is somewhat similar to the clock has stopped warning on some earlier builds, but these did not render the unit inert.
exfed2002 said:
Just installed the latest update (0621), and now when I try to do anything to open the UI from the booted splash screen (lock image) I get the message above.
I cannot shutdown or reboot to go back to an earlier version, I can only power off with the power switch.
If I try to use the reboot option from the splash screen, the recovery option has disappeared.
Starting the unit again produces the same result.
My latest boot got me the animated logo then presented a solid light blue screen.
How do I get it back so I can install the earlier build that was working while you fix this problem.
Right now the unit is useless, absent making up a new SD card. I have lots of stuff on the current card so would prefer not to do this.
This is somewhat similar to the clock has stopped warning on some earlier builds, but these did not render the unit inert.
Click to expand...
Click to collapse
Developer has said he will fix this in next build. Look at his thread.
Sent from my Galaxy Tab 2 using XDA Premium
leapinlar said:
Developer has said he will fix this in next build. Look at his thread.
Sent from my Galaxy Tab 2 using XDA Premium
Click to expand...
Click to collapse
And that is going to help how?
Did you read my post?
The unit is unable to get past the splash screen with the lock icon. I can't even regress to a working build.
exfed2002 said:
And that is going to help how?
Did you read my post?
The unit is unable to get past the splash screen with the lock icon. I can't even regress to a working build.
Click to expand...
Click to collapse
Just boot to recovery, wipe data and reflash. But you will lose apps and settings, not much you can do about that.
Sent from my Galaxy Tab 2 using XDA Premium
leapinlar said:
Just boot to recovery, wipe data and reflash. But you will lose apps and settings, not much you can do about that.
Sent from my Galaxy Tab 2 using XDA Premium
Click to expand...
Click to collapse
I wasn't able to do that as I had to shutdown, that was the only option.
In some way, punching the power key and home key in some sequence, suddenly the recovery menu appeared. Don't ask me how.
I was able to go back to the 0615 build, and from there do the upgrade to the 0623 build and now it's working.
But I have no idea how I got the revery menu to come up when all else failed.
exfed2002 said:
I wasn't able to do that as I had to shutdown, that was the only option.
In some way, punching the power key and home key in some sequence, suddenly the recovery menu appeared. Don't ask me how.
I was able to go back to the 0615 build, and from there do the upgrade to the 0623 build and now it's working.
But I have no idea how I got the revery menu to come up when all else failed.
Click to expand...
Click to collapse
Holding power + n key on boot takes you to recovery.
Sent from my Nook HD+ running CM10.1 on emmc.
System ui stopped Nook
I encountered this problem as well. Thanks to your posts, I started trying things before the flash screen locked. I downloaded a Nook app and the error message and display screen errors went away. I hope this works for someone else also..
I need help as I locked myself out of the phone somehow!
I have xposed installed, and I have gravitybox and wanam installed (as well as sense toolbox)
i check the feature that does crt animation for screen off and also fade on screen on, however I think I have some conflicting settings I may not be aware of as when I try to turn on my screen I get both animations at once it seems. I can't access anything at all and if I swipe up from the bottom of the screen I get a vibration.
I have TWRP installed so I can probably disable one of the mods if I only knew in which directory it was and what it was called :crying:
Please help I don't want to re-install all my apps
And it would be nice to use my phone again lol
RAMBOcoder said:
I need help as I locked myself out of the phone somehow!
I have xposed installed, and I have gravitybox and wanam installed (as well as sense toolbox)
i check the feature that does crt animation for screen off and also fade on screen on, however I think I have some conflicting settings I may not be aware of as when I try to turn on my screen I get both animations at once it seems. I can't access anything at all and if I swipe up from the bottom of the screen I get a vibration.
I have TWRP installed so I can probably disable one of the mods if I only knew in which directory it was and what it was called :crying:
Please help I don't want to re-install all my apps
And it would be nice to use my phone again lol
Click to expand...
Click to collapse
have you tried disabling xposed from recovery? Select ''install'' from recovery then choose Xposed-Disabler-Recovery.zip
alray said:
have you tried disabling xposed from recovery? Select ''install'' from recovery then choose Xposed-Disabler-Recovery.zip
Click to expand...
Click to collapse
Thanks for the info I didn't have the file but I should keep it handy.
I actually solved the problem I just restarted and was able to use the phone as long as the screen didn't shut off. So I just turned off the offending feature.