Database Users

DPI change black screen of death

unlocked, installed recovery, rooted, all good
changed dpi using an app (I know, idiot) to 160, rebooted
stuck at black screen of death, cant get into CWR, same black screen of death
BUGGER!
anyone got any ideas?

Managed to get into clockwork, by attempting to boot with the easy fastboot rooting boot.img, for some reason after I did that, recovery worked from that point onwards, so YAAAAAAAAAY :victory:

I changed the dpi to 160 with root explorer and haven't had a problem. What app have you used?

I did something similar and nothing bad happened. Rebooted and it was all good. Accidentally did a few screen presses and pulled up a DPI changing app (it was a recently used app), changed the DPI and uninstalled the program. All was good until just now when I restarted the device and it won't go past the Google screen.
Arrrrgggg. It sucks that I'm at work and the computers are locked down tight. Can't get the drivers installed on here to get into custom recovery. Staring at a lovely soft brick that's killing me! lol

I used this app
https://play.google.com/store/apps/details?id=com.innodroid.dpichanger&hl=en
input 160, rebooted, bricked

and now i find myself stuck in the same problem... what do i do?

I've heard bad things about some of those DPI changing apps. But never heard a complaints about ROM Toolbox Lite though and that's what I've used many times to change my DPI.
There is a guide for returning to stock and unbricking, might be worth a look for those that got stuck.
http://forum.xda-developers.com/showthread.php?t=1781250

I used ROM toolbox pro to change to 160 and it worked fine
Sent from my Nexus 7 using xda app-developers app

I'm kinda stuck without recovery and just seeing black screen on my Xperia Z.
Any input would be greatly appreciated.
EDIT:
Just so people know, I fixed it by flashing stock firmware via Flashtool.
Sorry for posting over in this forum, I was really getting worried as I was finding no answers. I appreciate that the devs might want to delete the post, feel free. I just thought I'd post my solution in the meantime.

Nexus 7 Wont Boot

Ok, so everything was going fine and dandy so i decided to root my nexus 7. it was amazing, i was able to over/underclock. Then i remembered an app that i had called chainfire3d that allows you to force certain things on the gpu such as anti aliasing and full 32 bit color on some things. anyways after an install it needed to reboot. once rebooted, it just sits at the google screen with the little lock thats open at the bottom. going into bootloader by holding down all the buttons gets me to the screen but then it freezes. cant boot, cant get into bootloader. any help?
Thanks in advance.

jombo2323 said:
Ok, so everything was going fine and dandy so i decided to root my nexus 7. it was amazing, i was able to over/underclock. Then i remembered an app that i had called chainfire3d that allows you to force certain things on the gpu such as anti aliasing and full 32 bit color on some things. anyways after an install it needed to reboot. once rebooted, it just sits at the google screen with the little lock thats open at the bottom. going into bootloader by holding down all the buttons gets me to the screen but then it freezes. cant boot, cant get into bootloader. any help?
Thanks in advance.
Click to expand...
Click to collapse
sounds like you need to go to the android development list and look for the unbrick thread that has directions to put the original os back on. Then reflash your favorite recovery/rom..etc.

jinside said:
sounds like you need to go to the android development list and look for the unbrick thread that has directions to put the original os back on. Then reflash your favorite recovery/rom..etc.
Click to expand...
Click to collapse
ok, but. im no android fixing expert, but i know my way around it really well. anyways, cant you do nothing if you cant at least get to the recovery screen?!
i have no idea.\
*EDIT
Finally got recovery to work by lots of reboots and was able to reflash the whole thing. i guess let this be a lesson to people trying chainfire.

[Q] Nexus 7 wifi

Im new to Android world, so please help me.
Now, my Nexus 7 Wifi is now unlocked and rooted by your tutorial, and
flashed Xenon HD Custom Rom.
I was in Jelly Bean 4.2.2 before. And i found some site that says
XenonHD is updated to 4.2.2 version, so i try to get it, and installed it to
my device. But after evrything done, i checked my device's version and it
says 4.2.1, but im sure i downloaded the right one, dated April 2013, as
far as i know. So, my device was downgraded to 4.2.1
Question:
a) Is it just that easy for downgrading an Android device? Because on
iOS, there are lots of concerns first before you can actually do
downgrading..
b) After installing apps, i made a backup with Nexus Root Toolkit, and
after the backup process, it reboots, and i notice that something is
wrong, the X animation logo goes somewhere at the lower right, and
when it goes to lockscreen, since im locked on landscape orientation,
half right side shows first then the half left side, youll really say that, it is
not okay. I tried rebooting by XenonHD settings, i tried to turn off and turn
it on again, same thing happens, what should i do?
c) About XenonHD, is it just one theme available? or i can download more
themes elsewhere? can somebody point me to where can i do that?
d) should i be re-flashing for XenonHD 4.2.2? How would i do that?
e) And what more can i do to my device to achieve it AWESOMENESS
Thanks in advance..

a) Yes, on many android devices it's that easy to downgrade. You don't need to jump through all the hoops like iOS requires you to.
b) Sounds like something may have gone wrong during the install process. Perhaps you could post a picture of what it looks like.
c) not sure, never used it.
d) Guess that's up to you. If it's an upgrade then it could fix the screen issue you're having. You'd flash it the same way you flashed the 4.2.1 version.

I'm sorry for spoonfeeding.
zeneleven said:
a) Is it just that easy for downgrading an Android device? Because on
iOS, there are lots of concerns first before you can actually do
downgrading..
Click to expand...
Click to collapse
Yes. XenonHD says it's 4.2.2 though, so I'm pretty sure you flashed an old build or the dev forgot to edit some text to make it say 4.2.2.
zeneleven said:
b) After installing apps, i made a backup with Nexus Root Toolkit, and
after the backup process, it reboots, and i notice that something is
wrong, the X animation logo goes somewhere at the lower right, and
when it goes to lockscreen, since im locked on landscape orientation,
half right side shows first then the half left side, youll really say that, it is
not okay. I tried rebooting by XenonHD settings, i tried to turn off and turn
it on again, same thing happens, what should i do?
Click to expand...
Click to collapse
Flash a different ROM or reflash your current one. Backups shouldn't have any effect on the ROM; if the backup app you're using negatively impacts your experience, switch it (I use titanium backup). TWRP recovery also supports nandroid backups.
zeneleven said:
c) About XenonHD, is it just one theme available? or i can download more
themes elsewhere? can somebody point me to where can i do that?
Click to expand...
Click to collapse
From the ROM thread, it says it supports CM10.1 themes (theme chooser). Search "CM10 themes" on Google Play to find them, then go to your settings to apply.
zeneleven said:
d) should i be re-flashing for XenonHD 4.2.2? How would i do that?
Click to expand...
Click to collapse
First, download the ROM to your device (if you haven't already), and google apps.
Make a backup of your data (nandroid or Titanium backup or some other backup app).
Then hold the power button, and select either "reboot"/"restart" or "recovery".
If you select "reboot" and no option for "recovery" comes up, hold down the volume down key while the device is restarting, then navigate using the volume buttons once the bootloader pops up, to the "recovery" tab.
Verify that the recovery installed is indeed TWRP (TeamWin recovery). If it isn't stop, and get TWRP before continuing.
Once your recovery pops up, select "factory reset", and swipe.
Then, select "install" from the menu that pops up, navigate to the folder labeled "downloads" and select the ROM file, and then select "add more zips", then select the gapps (google apps) file.
After that, swipe the little bar to start flashing, then after it's finished, select "reboot system".
Once the thing has properly booted into the setup screen, set it up, and restore your data.
zeneleven said:
e) And what more can i do to my device to achieve it AWESOMENESS
Click to expand...
Click to collapse
Install M-Kernel and Trickster Mod (app).
Install Nova launcher.
Install fdroid (for freedoms).
Install MX Player.

Ive already re-flashed with XenonHD's latest update i think, and yeah its on 4.2.2. and still, got the lockscreen problem which i solved by changing the lockscreen orientation, locking it to portrait.. and got more error like "Apollo" and its launcher "has stopped" something.. and the voice dictation, exits when being used, wherever im in..
Now, im planning to switch to Cyanogenmod for 4.2.2, since it has few themes available.
About Kernel? Can someone help me how to do that? a great guide will be greatly appreciated, done searching and cant find it, i swear.
Thank you so much in advance

[SOLVED] HELP! Phone stuck in odd loop after boot

I'm on NCG odexed stock, rooted with nova launcher + xposed framework/wanam
Today, I rebooted my phone and was presented with an odd scenario: The phone was looping between my homescreen (black background) and the Galaxy S5 blue geometrical wallpaper (I think I left the TW launcher with the default grassy picture). That's all the phone does - cycle between the two - and I cannot get a screen to stay up long enough to do anything. Of course, I don't have ADB authorized for any of my machines (haven't had the chance to use it yet) and I can't do much of anything. I tried safe mode, emergency call, camera, clear cache via stock recovery, and adb sideload to try and get SOMETHING to run. Unfortunately it seems I'm locked out of my device...does anybody have a suggestion that would allow me to get the data off the internal storage before wiping? >.<
Added video of issue:
https://www.youtube.com/watch?v=M_mncUueCJ8
Edit: Solved the issue through the most scientific methods; insanity and brute force! The phone would boot sometimes with the lock screen in the rotation, and those boots allowed me a brief window of touch interaction which I used to enable emergency mode, which fixed my immediate problem of being locked out and allowed me into an adb root shell. Hurrah.
Thanks all,
Overkill

OverkillSD said:
I'm on NCG odexed stock, rooted with nova launcher + xposed framework/wanam
Today, I rebooted my phone and was presented with an odd scenario: The phone was looping between my homescreen (black background) and the Galaxy S5 blue geometrical wallpaper (I think I left the TW launcher with the default grassy picture). That's all the phone does - cycle between the two - and I cannot get a screen to stay up long enough to do anything. Of course, I don't have ADB authorized for any of my machines (haven't had the chance to use it yet) and I can't do much of anything. I tried safe mode, emergency call, camera, clear cache via stock recovery, and adb sideload to try and get SOMETHING to run. Unfortunately it seems I'm locked out of my device...does anybody have a suggestion that would allow me to get the data off the internal storage before wiping? >.<
Click to expand...
Click to collapse
I would suggest you download the stock tar and odin, pull the battery and put it in download mode and odin back to stock. So long as you can get to download mode you should be fine.
Everything you need can be found here ==> http://forum.xda-developers.com/showthread.php?t=2784880

Chopstix9 said:
I would suggest you download the stock tar and odin, pull the battery and put it in download mode and odin back to stock. So long as you can get to download mode you should be fine.
Everything you need can be found here ==> http://forum.xda-developers.com/showthread.php?t=2784880
Click to expand...
Click to collapse
Already in progress But the stock tar also flashes over any user data, correct?

OverkillSD said:
Already in progress But the stock tar also flashes over any user data, correct?
Click to expand...
Click to collapse
Absolutely you will be returning to out of the box stock. But it's a good failsafe. Then you can start to play with it all over again

Chopstix9 said:
Absolutely you will be returning to out of the box stock. But it's a good failsafe. Then you can start to play with it all over again
Click to expand...
Click to collapse
Right The problem is, there are files I need to get from the device before I do that!
OverkillSD said:
does anybody have a suggestion that would allow me to get the data off the internal storage before wiping?
Click to expand...
Click to collapse

OverkillSD said:
Right The problem is, there are files I need to get from the device before I do that!
Click to expand...
Click to collapse
If the files are on the external sd card you are golden. That doesn't get formatted. If not ... It will take someonen with more expertise than me on the issue.

Chopstix9 said:
If the files are on the external sd card you are golden. That doesn't get formatted. If not ... It will take someonen with more expertise than me on the issue.
Click to expand...
Click to collapse
Well, I let the phone run for the last 45 minutes and eventually the phone rebooted itself and the system UI immediately crashed. I'm going to wait for the next crash and see if I have any luck with not pressing ok when this happens, and using that opportunity to allow ADB, which would solve my problem In the meantime, assuming that my hopes and dreams will be crushed, if anybody with ninja hacker skills has any suggestions, I'm all ears (or is it eyes?)

OverkillSD said:
Well, I let the phone run for the last 45 minutes and eventually the phone rebooted itself and the system UI immediately crashed. I'm going to wait for the next crash and see if I have any luck with not pressing ok when this happens, and using that opportunity to allow ADB, which would solve my problem In the meantime, assuming that my hopes and dreams will be crushed, if anybody with ninja hacker skills has any suggestions, I'm all ears (or is it eyes?)
Click to expand...
Click to collapse
I wasn't able to do this, presumably because com.android.systemui is responsible for this dialog and when it restarts, the problem restarts with it.
what's strange is that i can see my device on windows but the internal storage doesn't mount when the device shows up >.<
would i be able to flash just the systemui.apk and framwork.res files to stock using odin?
EDIT: Was able to get the device into emergency mode after much spamming of buttons and trial/error; this stops the problem I'm having, and I was able to get into ADB. The problem is most likely with Xposed, I'll be able to troubleshoot from here =) Basically, I had a brief window of laggy but responsive touchscreen interaction once out of every 10 boots which I used to get emergency mode enabled (lots of checkboxes) and this worked. It was either xposed or nova or a combination of the two, but it appears that I'm able to hack at it from here xD

[Q] CM11 much slower than CM7.2, normal?

Hey,
I just flashed the latest Quark's KitKat nightly (20141007), was on CM7.2 previously, is it supposed to be so much slower/more sluggish or did I do something wrong?
Any action takes at least a second (opening the menu, going into any submenu in the settings, ...), the keyboard takes 5s to popup when I tap an input field, call screen takes a few seconds too, if I tap the Google Now search bar I can only start typing 10s later, ...
The display and touch seem responsive, scrolling between my home screens is fluid and doesn't lag behind, but opening anything is slow.
Any idea?
It's a red lens MB525 Defy.
I went straight from CM7.2 to CM11, installed using the guide at quarx2k.ru, didn't install the 2.2.2 sbf (or any sbf).
Edit: Actually, just realised I installed new_boostrap.zip from recovery (as seen in another guide here) instead of doing the terminal part. Is that a problem?

Flash 08/10 nightly with the steps in the first post of kitkat thread, I don't know what you mean with "the terminal part"

DiegoxG said:
Flash 08/10 nightly with the steps in the first post of kitkat thread, I don't know what you mean with "the terminal part"
Click to expand...
Click to collapse
(The tutorial on quarx website makes you install the bootstrap manually via shell or terminal instead of recovery but I guess that's the same)
This KitKat thread right ? http://forum.xda-developers.com/showthread.php?t=2515036
That's how I did it actually. Install TWRP, install new_bootstrap, reboot, install resize, reboot, install CM11. Then I also installed the minimal gapps, and did a Factory Reset in android settings (to get the google first boot set-up).
Edit : Lock screen is super slow and if I check cpu usage after unlocking, Lock Screen is using over 50%...

DinoD2 said:
(The tutorial on quarx website makes you install the bootstrap manually via shell or terminal instead of recovery but I guess that's the same)
This KitKat thread right ? http://forum.xda-developers.com/showthread.php?t=2515036
That's how I did it actually. Install TWRP, install new_bootstrap, reboot, install resize, reboot, install CM11. Then I also installed the minimal gapps, and did a Factory Reset in android settings (to get the google first boot set-up).
Edit : Lock screen is super slow and if I check cpu usage after unlocking, Lock Screen is using over 50%...
Click to expand...
Click to collapse
You don't need to do a factory reset in order to get the wizard setup.
That's strange, those issues shouldn't occur. Try with 09/23 build

DiegoxG said:
You don't need to do a factory reset in order to get the wizard setup.
Click to expand...
Click to collapse
Yeah I knew there was probably a better way but I hadn't installed anything yet anyway.
DiegoxG said:
That's strange, those issues shouldn't occur. Try with 09/23 build
Click to expand...
Click to collapse
Hmm, where can I find older builds? There's only the latest 7 on quarx2k.ru and quarx.cm-for.us
Edit: I installed the 10/12 nightly, still laggy (maybe a tiny bit better, not sure). Also, the phone seems to reboot by itself from time to time.

DiegoxG said:
Try with 09/23 build
Click to expand...
Click to collapse
Hm. I got cm-11-20140923-NIGHTLY-mb526.zip, tried installing it from recovery, got the following error : "E:Error executing updater binary in zip '/sdcard/cm-11-20140923-NIGHTLY-mb526.zip".
Then I had no boot anymore (TWRP was saying I had no OS installed).
I got a newer (october) nightly and install worked for this one.
Am I not compatible with the older releases becuase I installed the new bootstrap and the partition resizing?
Is there a way to undo it or do I have to install an SBF?
Edit: Yep, installed an SBF, rooted, installed september CM11 and it worked. It seems faster too, no more big lags, but still slower than CM7.2 imo, I think I'm gonna downgrade.

DinoD2 said:
Hey,
I just flashed the latest Quark's KitKat nightly (20141007), was on CM7.2 previously, is it supposed to be so much slower/more sluggish or did I do something wrong?
Any action takes at least a second (opening the menu, going into any submenu in the settings, ...), the keyboard takes 5s to popup when I tap an input field, call screen takes a few seconds too, if I tap the Google Now search bar I can only start typing 10s later, ...
The display and touch seem responsive, scrolling between my home screens is fluid and doesn't lag behind, but opening anything is slow.
Click to expand...
Click to collapse
For keyboard remove if u don't use it swipe and suggestions