[Guide] How to fix black screen of death after dirty flashing lollipop - Nexus 5 General

On threads of lollipop flashing, There are quite lots of people asking about the black screen issue, but not really clear solution's out there.
These are the symptoms:
1. After booting, you get black screen with just upper notification bar and back button below
2. If you turn on the screen after a few second, you see the normal screen but only for a fraction of second.
3. You can hear some notification sound, but notification bar still says "no notification" (or something, well I'm not using english ui )
4. no response on cancel button
The reason is that, you've set a lock screen before, but your phone thinks you've never performed initial setup, so your phone gets confused and doesn't know what to do.
You can solve this by deleting /data/system/gesture.key (for gesture lock) or /data/system/password.key (for password lock) on recovery mode. Now your lock screen's gone, and you can normally boot your phone. If you're doing this on recovery, you should mount /data partition to locate the file.
There could be some other problems because your phone still thinks that you haven't initiallized it, so you should manually run initial setup by "adb shell am start -n com.google.android.setupwizard/.SetupWizardTestActivity" on normal boot.
I hope this helps!
credit : @nighthammer http://forum.xda-developers.com/showpost.php?p=56715651&postcount=7664

FreakyTux said:
On threads of lollipop flashing, There are quite lots of people asking about the black screen issue, but not really clear solution's out there.
These are the symptoms:
1. After booting, you get black screen with just upper notification bar and back button below
2. If you turn on the screen after a few second, you see the normal screen but only for a fraction of second.
3. You can hear some notification sound, but notification bar still says "no notification" (or something, well I'm not using english ui )
4. no response on cancel button
The reason is that, you've set a lock screen before, but your phone thinks you've never performed initial setup, so your phone gets confused and doesn't know what to do.
You can solve this by deleting /data/system/gesture.key (for gesture lock) or /data/system/password.key (for password lock) on recovery mode.
after that, you should manually run initial setup by "adb shell am start -n com.google.android.setupwizard/.SetupWizardTestActivity" on normal boot, to avoid several problems.
I hope this helps!
credit : @nighthammer http://forum.xda-developers.com/showpost.php?p=56715651&postcount=7664
Click to expand...
Click to collapse
This would be sweet except for some reason I hadn't accepted the adb authorization request on my device before I went all darkscreen duck.
wipe it is.

perdid0 said:
This would be sweet except for some reason I hadn't accepted the adb authorization request on my device before I went all darkscreen duck.
wipe it is.
Click to expand...
Click to collapse
You can delete the file via recovery, with file explorer or adb.
Since you have to unlock the bootloader to flash a factory image, you can flash a recovery image any time if you need one.

FreakyTux said:
You can delete the file via recovery, with file explorer or adb.
Since you have to unlock the bootloader to flash a factory image, you can flash a recovery image any time if you need one.
Click to expand...
Click to collapse
i cannot find that file in the location you specified. any other suggestions for locating it?!
---------- Post added at 09:23 AM ---------- Previous post was at 09:16 AM ----------
actually.......i found it!!!! same place you said!!! deleted both .key files and rebooted.......the screen was gone allowing me to accept the adb autorization and run the setupwizard!!! woot woot.....thanks a billion!!

perdid0 said:
i cannot find that file in the location you specified. any other suggestions for locating it?!
---------- Post added at 09:23 AM ---------- Previous post was at 09:16 AM ----------
actually.......i found it!!!! same place you said!!! deleted both .key files and rebooted.......the screen was gone allowing me to accept the adb autorization and run the setupwizard!!! woot woot.....thanks a billion!!
Click to expand...
Click to collapse
I'm glad that it helped!:highfive:

Hey man, thank you for your post !
I delated the file you said, but i didn't understand what should I do then ? Does it work if I don't do that adb setup (that I don't know what it is..)
Thank you for your help !

jordanl68 said:
Hey man, thank you for your post !
I delated the file you said, but i didn't understand what should I do then ? Does it work if I don't do that adb setup (that I don't know what it is..)
Thank you for your help !
Click to expand...
Click to collapse
Check the help threads for Nexus devices, there are "how-to" ADB & fastboot guides just everywhere. It works for all Nexus devices just the same way.
tetakpatalked from Nexus 7 flo

Please add this to your post. I had the black screen, but I never had a password set up. The black screen was happening because before I flashed an update, I had a system profile set to bypass the lockscreen. Once I put it back on the default profile (which you can do from the notification bar) everything was fine.

HELP! BLACK SCREEN ISSUE (Lollipop)
I flashed cm12 on my Galaxy Grand 2,but everytime i push the power button to unlock the screen,All i get is a black screen.I can hear touch sounds and responses and the harware buttons light up,but that's it.The black only goes on rebooting and I have to reboot my phone everytime I unlock it.Please Help?

Better Explanation
To make this guide appear better , and make it more easy doing etc etc..
Add this instead of a line method (well explained)
Download Aroma File Manager
Place it in your scdard directory
Boot in recovery
Mount Data
Go to Install and flash this zip..
Navigate to /data/system
Now delete password.key if a normal password or
gesture.key if a gesture

akastixx said:
Please add this to your post. I had the black screen, but I never had a password set up. The black screen was happening because before I flashed an update, I had a system profile set to bypass the lockscreen. Once I put it back on the default profile (which you can do from the notification bar) everything was fine.
Click to expand...
Click to collapse
I don't understand what you're saying. I've never seen "system profile set to bypass the lockscreen". could you tell me more specifically?
Aman_Arora said:
To make this guide appear better , and make it more easy doing etc etc..
Add this instead of a line method (well explained)
Download Aroma File Manager
Place it in your scdard directory
Boot in recovery
Mount Data
Go to Install and flash this zip..
Navigate to /data/system
Now delete password.key if a normal password or
gesture.key if a gesture
Click to expand...
Click to collapse
Thanks for your help. that's also a great workaround, but you know, it was nexus 5 that I was working on. If you were to place the file on the device, you would have to use adb anyway.

how can you do anything while screen is black? You just do not have any options displayed. I mean I am a layman

As everyone involved seems to be new to rooting, judging from the number of posts , tell them to READ READ READ . There is something called running before you can walk.

A clean install avoids the BS to begin with ...

Doesn't work with Nougat 7.1.1 (Dark ROM)
Does anyone know what if this solution works with Nougat 7.1.1 (Dark ROM)? I couldn't find the given files under /data/system, but I've found one as gatekeeper.password.key. However, if I delete it and reboot, I still get black screen.
Also, trying to run the setup wizard using ADB gives me a "SecurityException: Permission Denial: starting intent { ... } from null ( ... ) not exported from uid 10020".
Any ideas?

Related

"Superuser Permissions" freezing (JF 1.51)

Hi all,
Whenever I go to use a program for the first time that requires root, my screen goes black and processes start freezing. Eventually, a box comes up saying that the "Activity SU Request" process has frozen.
Any idea what's causing it (could it be the amount of apps i've installed?) and/or how to remedy it?
EDIT: found this:
@Androidandy the easiest way to get it working seems to be:
turn on your phone by holding the home+end(power) key
press alt+x to enter the recovery console and then press enter when it asks you
next type:
mount data
rm /data/data/com.koushikdutta.superuser/databases/superuser.sqlite
if you have the problem where it says this file does not exist, type:
rm /data/data/koushikdutta.superuser/databases/superuser.sqlite
Click to expand...
Click to collapse
Sorry for asking without looking completely thoroughly first, a mod can close this thread if they like.
blakew said:
Hi all,
Whenever I go to use a program for the first time that requires root, my screen goes black and processes start freezing. Eventually, a box comes up saying that the "Activity SU Request" process has frozen.
Any idea what's causing it (could it be the amount of apps i've installed?) and/or how to remedy it?
EDIT: found this:
Sorry for asking without looking completely thoroughly first, a mod can close this thread if they like.
Click to expand...
Click to collapse
Or...... dear lord, why.... you could just go to Settings>Applications>Development and enable "USB debugging". It's a known problem with the current SuperUser.apk
Usb debugging simply isn't working with my stupid windows computer, and I'm too lazy to boot it into linux. I found out the hard way that the recovery console doesn't work on my phone, I must have forgotten to update the phone somehow. I was fiddling with all the key combinations, conveniently forgetting alt + w = wipe.
Managed to get an old backup working, and the SU popup is working again.

How to root your Samsung Galaxy Gear!

How to Root the Samsung Galaxy Gear:
Firstly:
I AM IN NO WAY, SHAPE OR FORM, RESPONSIBLE FOR THE OUTCOME OF YOU FOLLOWING THESE INSTRUCTIONS! IT WORKED FOR ME, BUT THAT DOES NOT MEAN IT WILL ABSOLUTELY, POSITIVELY, WITHOUT A DOUBT, WORK FOR YOU!
Root Guide:
Preparation:
1. Install Samsung's official ADB Drivers from here.
2. Get Cydia Impactor from here.
3. Go to your Gear's settings and enable ADB​
To Root:
1. Plug in the device and let it install all the drivers it needs.
2.Unzip the Cydia Impactor folder you just downloaded
3. Open Impactor from the folder you just unzipped
4. The default "# drop SuperSU su to /system/xbin/su" is what you need
5. Click start
6. Once the process completes, the device will still look normal, but is fully rooted!​
I will have to leave it to you guys to install a utility like SuperSU or Superuser until there is a functioning recovery for the Gear.
Though this isn't necessary, however, and in some most cases doesn't work! SuperSU or Superuser just manage what apps access the SU command, so if you trust the app, it should be ok!
Enjoy your newly rooted device!​
How to restore back to stock:
Preparation:
1. Get Odin 3.07 from here.
2. Find the proper .md5 file from here.
(If you are in the US, just select the Great Britain file.)
3. Install Samsung ADB drivers from here.​
To Restore:
1. Plug in the Gear
2.From being powered on, (Bootable or not) press and hold the button of the right until the Gear shows "Samsung Galaxy Gear Rebooting" and rapidly press the button until you get to the "Select REBOOT MODE" screen.
3. Highlight "Download" in the list by pressing the button to scroll.
4. Press and hold the button for 3 seconds (and let go! The screen won't change immediately) and let it boot into download mode.
5. Unzip the .zip file you just downloaded that contains the ROM itself.
6. Select the PDA button and open the .MD5 file in the folder you just unzipped.
7. DO NOT ALTER ANYTHING ELSE!!!
8. Click the start button, and you'll be back to stock within a couple of minutes! (Most likely with any data on /data kept and all sideloaded apps remaining.)​
Any questions? Ask below! Want to help me make a ROM or Recovery? PM me!​
I tried this on OSX and now have a device that won't connect via USB anymore, even after factory reset! Proceed with caution.
EDIT : The device would still connect to adb in 64-bit Ubuntu, and and after re-running the application I have a rooted device. Busybox has been installed and all seems to be working well now.
Oops!
BUS DR1V3R said:
I tried this on OSX and now have a device that won't connect via USB anymore, even after factory reset! Proceed with caution.
EDIT : The device would still connect to adb in 64-bit Ubuntu, and and after re-running the application I have a rooted device. Busybox has been installed and all seems to be working well now.
Click to expand...
Click to collapse
I had issues with impactor crashing on my Mac, so i ran it on Windows instead as well!
photonicgeek said:
I had issues with impactor crashing on my Mac, so i ran it on Windows instead as well!
Click to expand...
Click to collapse
I'm actually not sure what's going on with this thing now. Busybox said the device was rooted, and it installed, but I can't seem to run any commands that require root.
Are you running Superuser or SuperSU, and what version?
Does this mean i will be able to use this with my HTC one? Im a newbie when it comes to this but id love to buy this watch to use with my stock 4.2 HTC One. Thanks.
Sent from ...............
Great news! :victory:
About 'UNROOT'? ... any idea? Or we just flash official rom back to GEAR?
big_pongo said:
Great news! :victory:
About 'UNROOT'? ... any idea? Or we just flash official rom back to GEAR?
Click to expand...
Click to collapse
Haven't rooted mine yet. But seems like the unroot feature in supersu should work
---------- Post added at 06:22 PM ---------- Previous post was at 06:18 PM ----------
This is great news! Thank you sir for creating an account. Just to share ur find. Who knows this might even make it to XDA wall on home page! But I do have to ask, how did you know Cydia Impactor would do the trick?
To answer some questions...
Ok, Firstly, mounting the gear should never have been possible... I know I have tried!
The entire process of rooting a device is simply getting the file "su" into /system/bin/ but the trick is getting it in there without root privileges! The truth is SuperSU or Superuser aren't ACTUALLY needed, they actually just regulate how apps access the "su" command.
To use the gear with any watch would require a new ROM which I know NOTHING about, but I am looking into modding the first one. (I recommend setting the screen DPI to 100)
And to answer @trevor7428 , I am an iPhone and Android user, and I do a lot of research into how exploits work. Saurik who does a lot of iPhone security research, mentioned the "Master Key" ("Hack 99% of Android devices") exploit, how to exploit it (Where impactor came from!), and also how to fix it. Thus, I thought that the worst that would happen is that it would fail!
photonicgeek said:
Ok, Firstly, mounting the gear should never have been possible... I know I have tried!
The entire process of rooting a device is simply getting the file "su" into /system/bin/ but the trick is getting it in there without root privileges! The truth is SuperSU or Superuser aren't ACTUALLY needed, they actually just regulate how apps access the "su" command.
To use the gear with any watch would require a new ROM which I know NOTHING about, but I am looking into modding the first one. (I recommend setting the screen DPI to 100)
And to answer @trevor7428 , I am an iPhone and Android user, and I do a lot of research into how exploits work. Saurik who does a lot of iPhone security research, mentioned the "Master Key" ("Hack 99% of Android devices") exploit, how to exploit it (Where impactor came from!), and also how to fix it. Thus, I thought that the worst that would happen is that it would fail!
Click to expand...
Click to collapse
After typing that about mounting the gear I immediately questioned whether that ever worked. :silly:
That being said, I have the su file in system/bin and system/xbin/, but anytime I try to run something that requires root it says "must be suid to work properly". After trying to find a fix for that for a few hours without luck I've run out of ideas.
Better yet, why not make a backup of the rooted rom that can be flashed via Odin now that download mode is more accessible?
Someone please sticky this so its easy to find
Sent from my SM-N900V using xda app-developers app
Minecraft on the Galaxy Gear!
BUS DR1V3R said:
After typing that about mounting the gear I immediately questioned whether that ever worked. :silly:
That being said, I have the su file in system/bin and system/xbin/, but anytime I try to run something that requires root it says "must be suid to work properly". After trying to find a fix for that for a few hours without luck I've run out of ideas.
Better yet, why not make a backup of the rooted rom that can be flashed via Odin now that download mode is more accessible?
Click to expand...
Click to collapse
I just added restore instructions to the OP!
Oh, and I found that Minecraft actually runs rather well, if not extremely cramped!
Look for my video on Youtube! Username: Photonic Boom
photonicgeek said:
I just added restore instructions to the OP!
Oh, and I found that Minecraft actually runs rather well, if not extremely cramped!
Look for my video on Youtube! Username: Photonic Boom
Click to expand...
Click to collapse
This looks to have worked fine.
However now I have a couple of "Payload" apps in my drawer...do you know what files these are so I can remove them?
codeman05 said:
This looks to have worked fine.
However now I have a couple of "Payload" apps in my drawer...do you know what files these are so I can remove them?
Click to expand...
Click to collapse
Hmmm... payload... could you possibly upload a picture? or...
1.is it a custom launcher?
2.do they have custom icons, or are they the stock "these apps have no icon" icons?
3.if it is a custom launcher, are the apps uninstallable?
photonicgeek said:
Hmmm... payload... could you possibly upload a picture? or...
1.is it a custom launcher?
2.do they have custom icons, or are they the stock "these apps have no icon" icons?
3.if it is a custom launcher, are the apps uninstallable?
Click to expand...
Click to collapse
No, no custom launcher yet.
It's in the "stock" app drawer and they do not have an icon, just the generic green android guy.
I'll see if I can get a screenshot
codeman05 said:
No, no custom launcher yet.
It's in the "stock" app drawer and they do not have an icon, just the generic green android guy.
I'll see if I can get a screenshot
Click to expand...
Click to collapse
I figure you can try restoring again!
codeman05 said:
No, no custom launcher yet.
It's in the "stock" app drawer and they do not have an icon, just the generic green android guy.
I'll see if I can get a screenshot
Click to expand...
Click to collapse
Well I loaded Nova and was able to uninstall them with that so all it well!
On a side note...I found out something you guys may have already figured out, but figured it was worth sharing just in case.
To get into download mode:
1. Hold down power until the screen says "rebooting"
2. Start tapping the power button until you get into the "Boot" menu
3. tap power to cycle to "Download"
4. long press (~3 seconds) to select Download mode
You can then odin the image referenced in the OP.
Handy if you screw up the build prop changing the DPI like I did initially
codeman05 said:
Well I loaded Nova and was able to uninstall them with that so all it well!
On a side note...I found out something you guys may have already figured out, but figured it was worth sharing just in case.
To get into download mode:
1. Hold down power until the screen says "rebooting"
2. Start tapping the power button until you get into the "Boot" menu
3. tap power to cycle to "Download"
4. long press (~3 seconds) to select Download mode
You can then odin the image referenced in the OP.
Handy if you screw up the build prop changing the DPI like I did initially
Click to expand...
Click to collapse
Actually, I'm glad you found that!! I've been using ADB all this time!
Mods,
PLEASE pin this thread!
Hey does anyone know if
a) you can get notifications from 3rd party sms apps like handcent and
b) if you can respond to sms by typing yet? its pretty annoying when you get a text on your gear and you're somewhere loud, then you gotta take out your phone and respond. please if anyone knows these answers cant wait for this to take off....pretty excited.
this looks interesting! will have to try it on my gear :laugh:

[SOLVED] [Q] ifont font change > stuck at boot logo

Phone was originally ICS, then upgraded to the official Jelly Bean, and rooted.
After selecting a font and having ifont set it, phone is stuck in the boot process (LG Logo).
Probably there is some problem with the selected font. I think ifont places the font at /system/fonts and renames it so that the device thinks it the default one.
I can put the phone in the "Recovery mode" by pressing Vol up + Power, but don't know what to do next.
Haven't tried Vol up + Vol down + Power yet. Probably it works, but I want to avoid hard reseting as I haven't got backups at a desktop computer, only in internal "/sdcard" on the phone.
I would appreciate a way to boot or access the phone's file system. Anything but a hard reset.
EPa said:
Phone was originally ICS, then upgraded to the official Jelly Bean, and rooted.
After selecting a font and having ifont set it, phone is stuck in the boot process (LG Logo).
Probably there is some problem with the selected font. I think ifont places the font at /system/fonts and renames it so that the device thinks it the default one.
I can put the phone in the "Recovery mode" by pressing Vol up + Power, but don't know what to do next.
Haven't tried Vol up + Vol down + Power yet. Probably it works, but I want to avoid hard reseting as I haven't got backups at a desktop computer, only in internal "/sdcard" on the phone.
I would appreciate a way to boot or access the phone's file system. Anything but a hard reset.
Click to expand...
Click to collapse
Stupid question time ...
I presume that you have CWM or TWRP recovery installed and took a full Nandroid backup before trying to play around with system files?
SimonTS said:
Stupid question time ...
I presume that you have CWM or TWRP recovery installed and took a full Nandroid backup before trying to play around with system files?
Click to expand...
Click to collapse
Stupid answer: No
EPa said:
Stupid answer: No
Click to expand...
Click to collapse
I'm not sure you're going to have much luck recovering the phone without a hard reset I'm afraid. I've seen quite a few threads before where people have tried to change the default fonts and it's gone wrong, but I've never tried it or wanted to so I can't offer any other advice really.
Ok, having connected usb and using Vol down + Power I get to the Android system recovery.
Options are
reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
wipe nv partition
toggle console UART log
Can I do anything from there?
EPa said:
Ok, having connected usb and using Vol down + Power I get to the Android system recovery.
Options are
reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
wipe nv partition
toggle console UART log
Can I do anything from there?
Click to expand...
Click to collapse
You could, potentially, create your own ADB update .zip file containing the original files from /system/fonts
SimonTS said:
You could, potentially, create your own ADB update .zip file containing the original files from /system/fonts
Click to expand...
Click to collapse
Sounds great. I already have adb drivers installed on my windows machine. Now where do I get adb client? Do I need the whole android SDK?
Solved.
Downloaded android SDK, then used adb shell command which gave me access to the phone's OS, remounted the file system as read-write, copied a valid font in place of Roboto-Regular.ttf (that's what ifont had replaced with my obviously problematic font), rebooted, everything fine.
Thanks a million SimonTS..
By the way if anyone could point me to / send me a copy of the original (I don't have it anymore) Roboto-Regular.ttf found in their /system/fonts? Thank you.
EPa said:
Solved.
Downloaded android SDK, then used adb shell command which gave me access to the phone's OS, remounted the file system as read-write, copied a valid font in place of Roboto-Regular.ttf (that's what ifont had replaced with my obviously problematic font), rebooted, everything fine.
Thanks a million SimonTS..
By the way if anyone could point me to / send me a copy of the original (I don't have it anymore) Roboto-Regular.ttf found in their /system/fonts? Thank you.
Click to expand...
Click to collapse
http://www.filedropper.com/roboto-regular
SimonTS said:
http://www.filedropper.com/roboto-regular
Click to expand...
Click to collapse
Got it! Thank you once more!
EPa said:
Solved.
Downloaded android SDK, then used adb shell command which gave me access to the phone's OS, remounted the file system as read-write, copied a valid font in place of Roboto-Regular.ttf (that's what ifont had replaced with my obviously problematic font), rebooted, everything fine.
Thanks a million SimonTS..
By the way if anyone could point me to / send me a copy of the original (I don't have it anymore) Roboto-Regular.ttf found in their /system/fonts? Thank you.
Click to expand...
Click to collapse
How did you get ADB control from the stock recovery?
Thanks
h078 said:
How did you get ADB control from the stock recovery?
Thanks
Click to expand...
Click to collapse
I am not sure what you mean.. isn't android sdk and its tools (like adb) supposed to give you this kind of control on normal (ie unflashed, unrooted) phones? What were someone who wanted to develop for android to do if this control didn't exist?
Anyway it just happened and I thought it was natural. It was the first time I had to deal with android at that level.
So basically my answer is: I don't know, wasn't booting my phone in (stock) recovery (by means of power+volume down), connecting it via the usb cable to the desktop and using adb (which was included in google's sdk for android) supposed to give me this kind of control?
It's little out of topic, but there is (it think so) real problem with apps which modify the fonts. I have the same problem with Font Installer. I set font, then reboot and bootIoop. I had to reflash ROM. I don't know what goes wrong. But if I copy /system/fonts and rename to roboto-regular.ttf and reboot everything is normal (font changed, everything works)
EPa said:
I am not sure what you mean.. isn't android sdk and its tools (like adb) supposed to give you this kind of control on normal (ie unflashed, unrooted) phones? What were someone who wanted to develop for android to do if this control didn't exist?
Anyway it just happened and I thought it was natural. It was the first time I had to deal with android at that level.
So basically my answer is: I don't know, wasn't booting my phone in (stock) recovery (by means of power+volume down), connecting it via the usb cable to the desktop and using adb (which was included in google's sdk for android) supposed to give me this kind of control?
Click to expand...
Click to collapse
What I meant is in my case when I boot in stock recovery and fire up ADB , ADB does not see connected device....
Maybe because I have only basic ADB not full SDK...
But when I type ADB devices it returs no device connected....
h078 said:
Maybe because I have only basic ADB not full SDK...
Click to expand...
Click to collapse
That must be the case.
Do you need to download full sdk for that ?
I did (well, I let it install just the standard stuff), but I think a slim version will do just fine.

[Q] Second Screen Simulation activated - Phone doesn't boot properly

Hi,
i just activated the "Second Screen Simulation" in the developer options on my S 3 Mini, now it won't boot again to work completely.
I got the SlimKat CustomRom and TWRP v.2.7.1.0.
After i press the Power-Button the Samsung Logo appears and then the "SlimKat" Logo appears. The SlimKat Logo pulses and then it just stops to pulse and the phone freezes.
Now i got the idea if i could just edit the settings via terminal in TWRP, is this possible? If yes, can anyone tell me where the settings-files are located?
If no, anyone got another idea to get it back to work again? I definetly don't want to reinstall it.
And YES, i searched the forum!
greetings
solved
I just fixed it myself.
And here's how you do:
backup the file "settings.db" under the path /data/data/com.android.providers.settings/databases. I accessed my phone via TWRP file manager and copied it on my computer.
open the file with a sql manager e.g. the firefox addon SQlite Manager.
browse to the key "global" and DELETE the last key with name="overlay_display_devices". I know this is risky but it worked for me.
Than simply copy the settings.db to the original path and boot your phone.

can anyone offer me some help

Background
Okay so the glass on my 2013 Moto X broke on September 27th I ordered a new one and while changing it I accidentally broke the digitizer so I disconnected the digitizer and the phone turned on while my digitizer with disconnected then i had no way of turning it off while my digitizer was disconnected the phone started to vibrate every 3 seconds until the battery died... so I was forced to switch over to my Nexus 6 because at the time that was my backup phone because I love the performance of my Moto X.. now a few months later yesterday to be exact my new digitizer arrived and I brought my Moto X back to life powers on and performs just fine
Problem
My wrist twitch to activate camera doesn't work
My dual chop to activate led doesn't work
Whenever I make a phone call or receive a phone call my screen turns off automatically but the phone call works just fine once the phone call has ended my screen does not turn back on I have to reboot the phone to turn on the display again
Phone info
2013 moto x on 5.1.1 stock rom locked bootloader rooted using crashes method with ultra slim root
any help or tip is greatly appreciated
Maybe, but it really depends what's actually wrong. The Moto has a TI MSP430 chip that handles all that 'motion, wave-to-wake, chop-chop' stuff and it's loaded from a /firmware folder or partition (have forgotten at this point). @masterifla figured out which files it was on 4.4.4 & 5.1 that got uploaded to the 430 and wrote a .zip file to change from 4.4.4's "wave to wake" to 5.1 "chop chop" or vice versa. I fixed some little bug in it, and stuck the working .zips up in this post although they may be elsewhere as well: (so :: these zips contain the firmware that actually does the wave-to-wake stuff and can be 'recovery-flashed')
http://forum.xda-developers.com/showpost.php?p=63616790&postcount=17
At least if that works, you'll know that it was the firmware for that chip, and if not, it might actually be the 430 chip(which you can see in the teardown). The post by me and anything by masterifla should be pretty well explained.
Cheers.
but have a locked bootloader I can't flash anything...but you gave hope maybe if I use rsd lite to flash stock I can fix this
BADDINOROX99 said:
but have a locked bootloader I can't flash anything...but you gave hope maybe if I use rsd lite to flash stock I can fix this
Click to expand...
Click to collapse
There still might be a way. I keep trying to have people get this to work, but I'm not sure of the outcome yet, so give it try if you like: Here's some steps:
1) Locked bootloader / no root means mostly that you can't write system, but I'm pretty sure you should be able to temporarily boot into a PC-based copy of twrp. Once in twrp (for one time say) you are root, and you have access to anything on your gizmo. In theory, you should be able to mount system read-write and change something in the file system.
2) Get the correct copy of twrp and adb (from dev forum for this box) and put it on a PC with fastboot in the same folder. To make this easy, called twrp "twrp.img" and call "fastboot" or "mfastboot" fastboot.exe (I am for some reason assuming you've got a PC, not a mac or linux, but the ideas are similar.
3) quick explain of the files in the .zip from above ^^ : 8 files prefixed by MSP that are located when on the moto in /system/etc/firmware. Unzip them and stick them in that same folder.
4) Tricky part : (I think) : reboot into the twrp.img on your PC by getting your device into fastboot / bootloader mode: (so .. volume-up&down&power keys all held down for ~10 seconds perhaps, then if you've gotten it right (it's touchy), you'll be in the bootloader where it has a small tiny text list of stuff like "continue, recovery, etc).
5) you're good with the phone if you've made it here: now on the PC from that folder, type in "fastboot boot twrp.img" and good luck. If it works, your phone will be in TWRP with root access. If not, I don't know another option at the moment.
6) Probably the rest is most easily done from the PC command (or shell) window where the files are. Since your device is in the bootloader and awaiting further instruction, you should be able to use adb to talk to recovery now. so carry on:
7) (get the files from your PC (the MSP prefixed ones) onto the device, so first remount system r/w):
Code:
a) "adb remount" // supposedly should remount system toggling the read attribute to write
b) "adb push msp* /system/etc/firmware/" // copies files to device unless I've got syntax wrong, try one at a time if doesn't work.
c) "adb shell ls -al /system/etc/firmware/" // list all files, and post them back here to see if it even worked.
d) "adb remount" // system partition back to normal ro state.
d) "adb reboot" // moment of truth, a reboot.
8) after things settle post-reboot, check out "wave-to-wake" , camera twist, etc. This works on 4.4.4 or 5.1 (if this other stuff above works).
Note: I could be way off on my idea that rebooting into recovery will give you enough functionality to do this, but I'm not sure what other choices you've got without being able to root. I guess another thing I'm wondering about is why you wouldn't be able to root the phone from recovery regardless of how you booted into it. You still can't unlock bootloader, but I'm not clear on what difference it makes at the moment.
Good luck. It's a "hail mary" pass.
thanks I got my stuff working again ? I screwed up in the file install part freaked out and reflashed stock and rerooted so everything is good now once again thanks

Categories

Resources