[Q] HELP!!! I am soooo [email protected]#ked!! - Nexus 6 Q&A, Help & Troubleshooting

So...I'm an idiot.
I rooted my phone sometime last week and installed Chroma...its awesome, but thats not the problem
The problem is that when Chroma reset my DPI, a lot of the original stuff that comes in the phone didn't scale properly. I use a pattern password at boot to start because my college has an serious issue with stolen phones...the problem is...my 9 dots are sitting in the corner like a little cue instead of how they usually are and I can't unlock my phone -_-
Is there anyway to reset the DPI without having to get into the phone, bc I've tried and its not happening.
Thanks in advance.

Manny910 said:
So...I'm an idiot.
I rooted my phone sometime last week and installed Chroma...its awesome, but thats not the problem
The problem is that when Chroma reset my DPI, a lot of the original stuff that comes in the phone didn't scale properly. I use a pattern password at boot to start because my college has an serious issue with stolen phones...the problem is...my 9 dots are sitting in the corner like a little cue instead of how they usually are and I can't unlock my phone -_-
Is there anyway to reset the DPI without having to get into the phone, bc I've tried and its not happening.
Thanks in advance.
Click to expand...
Click to collapse
could you not dirty flash the rom? im not sure where the dpi settings are stored. if it is in the system file somewhere it would get overwritten

...and of course I got a unable to mount storage error. Great. But thanks anyways!

All I can really say is... LOL.
Use recovery to access and edit the file /system/build.prop and change the dpi line to correctly match the screen.

Manny910 said:
...and of course I got a unable to mount storage error. Great. But thanks anyways!
Click to expand...
Click to collapse
A factory reset through recovery wont work? i

If your device is detected by fastboot command it's better backup your data via titanium and do all the things over again following http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 and follow the second step.
I had the same dpi issue and this is the best solution and you have chance to go back stock rooted unencrypted. the boot img in that thread may be force encrypt you have to download noforce encrypt boot.img
good luck.

Related

Tilt Stuck on Boot Screen

I apologize first off for another boot problem thread.
First, I have never messed with my rom. I never flashed it or anything. The most I have done is load KaiserTweak and TomTom. Basic stuff.
I went to turn on my phone this morning and it stayed on the AT&T boot screen. It just freezes. I kept trying to soft reset the phone and at one point it loaded with like the default settings but nothing worked. The start menu only had the Today listed. The phone wouldn't work either. From then on, it always sticks on the AT&T boot screen.
I tried removing the battery and the sim card for a few hours and that didn't help. I tried turning on without the sim.
I am hoping to fix without a hard reset. I don't want to lose all of my contacts and all the data saved on the phone. Is there any way to save this stuff?
That's why you should always have scheduled backups at least once a week. I don't see this being fixed without a hard reset. You did everything that i would have personally suggested (taking out battery and everything for a few minutes). If all fails, you can always go into bootloader mode and reflash the ROM.
Is there no safe mode way to access the device? How about any work around so the computer can access the flash data without the device being in active sync mode?
Highly doubt it and i've never read anything about accessing the device when it's not on. It seems so sporadic and from the looks of it, only a reflash will get you going again.
This reminds me of back when I was trying to flash my Kaiser to 6.1... had exactly the same issues. Even worse actually since the problem started when I flashed a ROM wrongly, also without having an original to fall back to. Cue a night of trying to flash over my mistakes!!
I recall having some success with some specific mtty commands... argh, I'd bookmarked hundreds of threads on it back then but have since lost them all. All I know is there are a few commands you can type which may just get the phone booting again. Bit useless of me but it's a start!!
Ah, check these threads:
http://forum.xda-developers.com/showthread.php?t=371154 This one will erase all data
And post #2 demonstrates use of using the mtty boot command here:
http://forum.xda-developers.com/showpost.php?p=1765045&postcount=2
Those kinds of commands I managed to get my phone working with.
I figured out how to boot to the tri-color boot screen. The computer regonizes it and the boot command in mtty just does the same thing as turning it on.
Since my computer is now linked to the phone, isn't there some way to access files? Any commands in mtty that will work? Any other program out there that might help access the memory?
No one has any ideas about how to access the memory?
Did you manage to fix this in the end?
Got the very same problem with mine which hasn't been flashed in any way.
vigilante_xix said:
Did you manage to fix this in the end?
Got the very same problem with mine which hasn't been flashed in any way.
Click to expand...
Click to collapse
Never was able to figure it out. I had to reload from scratch.
Good luck with your issue. Hopefully some of the suggestions around here and elsewhere will get you back up and running.

Any way to recover from boot loop?

Ok, first of all I know it's been said not to mess with Framework. I read that too late =/
I was trying to install a status bar replacement, which overrides framework-res.apk. It sent it into reboot loop. I can get to recovery screen, but factory reset doesn't do anything of course.
I also can get to bootloader. It gives me the following:
===
Bootloader
29.01
Battery OK
OK to program
Transfer mode:
USB
===
It's connected through USB and bootloader recognizes that. My question - is there a way to push original framework-res.apk back to the phone or is it completely bricked?
I posted in an existing thread about this already, but figured I might have more luck with a new thread.
If you
Code:
adb devices
does it show up? I'm unfamiliar with this type of situation. =p
Oh sorry, forgot to mention that. adb devices doesn't show anything in either recovery nor bootloader.
When connecting through USB and starting bootloader, I can hear the sound of device found on my PC, but it doesn't get found and is listed as "S Flash OMAP3630 MI" with a ? mark in device manager.
Yikes, can't help you with the obvious then (just pushing framework-res.apk again).
Yeah, I was really hoping to somehow get in there with adb
As suggested in another thread, I tried applying .604 update, but it aborts when verifying current system with CityID.apk as a reason. I removed it along with other bloat from the phone.
Also when trying to remove app files I don't have on the phone from update.zip, it fails when verifying the update file.
hey its me again, take a look at this!
http://www.droidxforums.com/forum/d...your-x-stuck-bootloop-you-want-look-here.html
Thanks for the link!
That guy got lucky cause it bricked after he put all the bloatware back on the phone lol. So he had all the default apps. Mine gets stuck when verifying my system and complains about CityID.apk missing. And as we figured out, your previous suggestion with removing files from the zip messes up its integrity.
So I went to a Verizon store and got a replacement ordered. I was afraid they'd start asking if I'd rooted it, but apparently the guy helping me didn't even know what that is He tried a factory reset and then just ordered a new phone.
Thanks for your suggestions, guys!
He may not of known that the x has been rooted yet lol. Or you can just find something small and miniscule to complain about on you phone to get a new one. When the dare first came out I had a new one at the end of every month just for the fun of it. And they where always replaced with a brand new phone. Did that for atleast 5 months before getting a cheap wm phone because they felt bad about all the hassles I had.
Sent from my DROIDX using XDA App
Did the same thing with mine, except my framework file is there, just renamed. I tried last night to figure out how to change the name back with adb but never could.
to the OP, how did you get to that Bootloader? The only thing I have been able to do is get into "Android System Recovery (2e)", which is done by holding Home while powering up the phone. If you hold Home, you'll get a screen with Android next to an exclamation point sign. At that screen you can press Search to open up the menu system, and then you have the ability to reboot, apply update.zip from microSD, wipe data/factory reset, and wipe cache partition.
I am trying to get into ADB so I can potentially work on this phone and fix it. At the moment I am boot looping like nobody's business
-EDIT-
Found the answer myself on this forum: "Hold down the power+vol down+camera button."
This works, but from what I can tell, it puts the phone into a basic USB flashing mode that is useful if you wanna reflash the ROM. At the moment there isn't anything available which could be flashed onto the phone (need to wait for an SFP file?), so I'm stuck waiting.
If/ when the 2.2 update leaks, I believe I can at least try to install that via MicroSD while in System Recovery Mode. I already unbricked my phone once by doing that, but then removed exactly the wrong APKs so now I cannot use that trick a second time
Yep, that was exactly my experience. If I didn't remove bloat apk's, I'd be able to apply .604 update, but...
And yeah, bootloader doesn't do much at this point since we have no way/no ROM's to load.
As far as I remember, Verizon have one month return policy, so I'd suggest just taking it to them. I had my replacement ordered with no questions asked. I just said I was installing an app and it rebooted and went into a loop.

[Q] Really annoying issue with Google account sign in.

So I've been having this strange problem and I am convinced there is no simple solution. Every time I wipe date and install a rom, I try to sign in to the Google account during setup, and I keep getting an error saying that there was a problem communicating with Google servers. I've done a factory reset, formatted everything, tried different RUUs, and nothing seems to work. I just can't sign in on a Sense 5.5 rom. So now I want to clear the phone completely, because there must be something that no form of wiping is touching. A stock RUU can't solve the problem and I don't know what can. I even tried using LTE instead of WiFi and still no luck. Does anyone have any clue about this?
Prophet16 said:
So I've been having this strange problem and I am convinced there is no simple solution. Every time I wipe date and install a rom, I try to sign in to the Google account during setup, and I keep getting an error saying that there was a problem communicating with Google servers. I've done a factory reset, formatted everything, tried different RUUs, and nothing seems to work. I just can't sign in on a Sense 5.5 rom. So now I want to clear the phone completely, because there must be something that no form of wiping is touching. A stock RUU can't solve the problem and I don't know what can. I even tried using LTE instead of WiFi and still no luck. Does anyone have any clue about this?
Click to expand...
Click to collapse
I had the same thing. My solution was wipe everyithing except data and internal memory. After that no more errors
donkeykong1 said:
I had the same thing. My solution was wipe everyithing except data and internal memory. After that no more errors
Click to expand...
Click to collapse
But I have wiped everything including internal storage and used usb-otg to install roms. Nothing works. Are you sure that will fix this?
EDIT: Can confirm that your recommendation doesn't work for me. I decided to flash a different rom (InsertCoin) and in this one I can sign in, but it won't sync, it just keeps saying "Google Sync error."
Prophet16 said:
But I have wiped everything including internal storage and used usb-otg to install roms. Nothing works. Are you sure that will fix this?
Click to expand...
Click to collapse
It did the trick for me. Also, I mount system in recovery before doing anything. I'm pretty new to this phone and never used any recovery except 4ext on my Desire and Evo so I can't be 100% sure, leaving data did the trick for me
I've tried a few new things so far. I used the mkfs.ext4 file to format the data partition as I think that's where the source of the issue lies. But I also used fastboot to format system. If this doesn't work then I don't know what else to to. I might be forced to run a GPe rom or some other android rom. I just strongly prefer sense.
Prophet16 said:
I've tried a few new things so far. I used the mkfs.ext4 file to format the data partition as I think that's where the source of the issue lies. But I also used fastboot to format system. If this doesn't work then I don't know what else to to. I might be forced to run a GPe rom or some other android rom. I just strongly prefer sense.
Click to expand...
Click to collapse
whats happens if you start a new account
It won't work. I tried typing in random letters in to the user name and password box but it doesn't even try to connect.
Well I've got bad news. I managed to hard brick my device, so this issues I was having is not an issue for me anymore. But if anyone can help find a solution that would be appreciated as I'm sure someone else might be facing the same problem.
Define hard brick
SaHiLzZ said:
Define hard brick
Click to expand...
Click to collapse
Hard Brick = Phone that has been thrown on the floor and crushed with a very large rock.
SaHiLzZ said:
Define hard brick
Click to expand...
Click to collapse
That's when you can't enter the bootloader anymore. You hold the power button and the lights on the bottom don't flash and it'll just vibrate a bit. But it's all good I got the phone replaced today. So then I installed the rom I was trying to install earlier (the one where I couldn't sign in to google) and I ended up having the same issue. So I think I'm gonna just use ARHD or something.

[Q] Bricked Xperia Z

Hello,
I think I did something really wrong with my Xperia Z. I rooted it a month ago, I have the latest stock rom. Yesterday, I downloaded an app called Flashify on the play store who claimed to be able to flash recoveries and zips directly from phone, as long as it was rooted. I tried to flash the purexaudio mod to my phone, and since then it has become unusable. It first started to be very hot, then laggy, which forced me to shut it down. Now everytime I turn it on, it is usable for barely two minutes, before it becomes really laggy and nothing works or it freezes. Some actions directly crash my phone, such as opening the developers settings. I looked at the RAM usage on the phone's settings and the RAM is filling up progressively until the total 1.8GB of RAM is used and my phone freezes. I really don't know what is causing this.
It gets even worse, as I've managed to factory reset my phone with the sony PC companion, but the problem is still there. I can't access reccovery but I can access fastboot mode. However, neither Flashtool or fastboot command shell will flash a recovery for me (I get an "access denied" error). I can't flash the stock kerne with Flashtooll, I have the message : "Processing of loader.sin finished with errors." (I had this problem when I rooted it but I really can't remember how I fixed it).
I'm really anxious about what I've done with my phone, I hope someone could help me recover my phone as I honestly don't know what to do at this point...
Thank you so much in advance.
williaam said:
Hello,
I think I did something really wrong with my Xperia Z. I rooted it a month ago, I have the latest stock rom. Yesterday, I downloaded an app called Flashify on the play store who claimed to be able to flash recoveries and zips directly from phone, as long as it was rooted. I tried to flash the purexaudio mod to my phone, and since then it has become unusable. It first started to be very hot, then laggy, which forced me to shut it down. Now everytime I turn it on, it is usable for barely two minutes, before it becomes really laggy and nothing works or it freezes. Some actions directly crash my phone, such as opening the developers settings. I looked at the RAM usage on the phone's settings and the RAM is filling up progressively until the total 1.8GB of RAM is used and my phone freezes. I really don't know what is causing this.
It gets even worse, as I've managed to factory reset my phone with the sony PC companion, but the problem is still there. I can't access reccovery but I can access fastboot mode. However, neither Flashtool or fastboot command shell will flash a recovery for me (I get an "access denied" error). I can't flash the stock kerne with Flashtooll, I have the message : "Processing of loader.sin finished with errors." (I had this problem when I rooted it but I really can't remember how I fixed it).
I'm really anxious about what I've done with my phone, I hope someone could help me recover my phone as I honestly don't know what to do at this point...
Thank you so much in advance.
Click to expand...
Click to collapse
Well, that's not weird at all that you're getting "access denied" via fastboot. You said you've rooted your device, but did you unlock your phone's bootloader?
LaurynasVP said:
Well, that's not weird at all that you're getting "access denied" via fastboot. You said you've rooted your device, but did you unlock your phone's bootloader?
Click to expand...
Click to collapse
No, I guess I didn't... My bootloader status in Flashtool is : ROOTABLE I'm going to try doing that first. Thank you so much for your fast answer
I have a big problem actually now, as repairing my firmware with the sony software removed the USB debugging option. And opening the "developers settigns" to turn it back on still makes the settings crash. So I have no way of unlocking the bootloader now have I?
EDIT : Okay, nevermind. I managed to unlock the bootloader and flash a custom recovery (Cyanogen recovery). But now I'm on a boot loop (Sony message then Xperia then phone restarts)
What should I do now?
EDIT 2 : Solved the problem by simply wiping all caches/data from my recovery (ended up setting up the more traditional CW recovery) + sideloading a custom ROM (Ultimate PureZ). Now everything's working perfectly.
Thank you again for suggesting to unlock the bootloader, I couldn't have flashed the recovery otherwise. Have a nice day!
williaam said:
I have a big problem actually now, as repairing my firmware with the sony software removed the USB debugging option. And opening the "developers settigns" to turn it back on still makes the settings crash. So I have no way of unlocking the bootloader now have I?
EDIT : Okay, nevermind. I managed to unlock the bootloader and flash a custom recovery (Cyanogen recovery). But now I'm on a boot loop (Sony message then Xperia then phone restarts)
What should I do now?
EDIT 2 : Solved the problem by simply wiping all caches/data from my recovery (ended up setting up the more traditional CW recovery) + sideloading a custom ROM (Ultimate PureZ). Now everything's working perfectly.
Thank you again for suggesting to unlock the bootloader, I couldn't have flashed the recovery otherwise. Have a nice day!
Click to expand...
Click to collapse
You're welcome, but in this case you've made a major mistake - you didn't take TA Partition backup in which all DRM keys are being kept. Now you've erased them permanently, this will cause some stock applications to won't work (camera stabilization and etc.,).
Have a nice day you too
LaurynasVP said:
You're welcome, but in this case you've made a major mistake - you didn't take TA Partition backup in which all DRM keys are being kept. Now you've erased them permanently, this will cause some stock applications to won't work (camera stabilization and etc.,).
Have a nice day you too
Click to expand...
Click to collapse
Really? :/ What won't work exactly.?. I bootloaded my phone the official way though...
And BTW that's strange but when I put my SDCard back into my phone it crashed just like before? I guess I should format it?
williaam said:
Really? :/ What won't work exactly.?. I bootloaded my phone the official way though...
And BTW that's strange but when I put my SDCard back into my phone it crashed just like before? I guess I should format it?
Click to expand...
Click to collapse
Guess so. If even will update to earlier version (4.4.x) or later BE2 won't work, as well as camera stabilization (focus, well, it works, but photos are a bit like blured) and some other functions that I don't remember at the moment. It doesn't matter how did you unlock your bootloader, the fact that you've unlocked your bootloader is the most important. I'm sorry, but there's nothing we can do about it (DRM keys recover) at the moment. Maybe in a future there will be found a solution for this, but then our phone, I suppose will be like a nokia 3310 in nowadays.
Btw, you can still get some functions working, just surf this forum for unlocked bootloader functions "Get back" or sth., don't remember thread name either.. :|

Access Device Storage via Bootloader/Recovery? Phone Wont Boot Past AndroidOne Screen

TL : DR - My phone won't boot because of low disk space, how can I free up memory?
Greetings,
Project FI purchased Moto X4 running BONE STOCK and absolutely ZERO CUSTOMIZATION. If I can get access to my pics taken via the camera I'm ok with wiping the phone and starting over. Screenshots folder access would be cool too but not life necessary... Wait there has to be a way to make a dump of all this data somehow, somewhere right?
Last night I was on 15% or less battery life and less than 100mb's of disk space left. (i know, i know, i'm a dummy head)
I heard about PLEX running no problem on mobile Browser and decided to test it out and sure enough it worked fine. Was test streaming a few movies out when my PHONE DIED. I thought, oh man, thats probably not the best since it died and it was low on space but yeah I threw it on the charger and went to bed....
This morning, I confirmed it was charged 100% but when I turn it on, the phone will not boot past the AndroidOne screen. Left it there for 40mins and no change, AndroidOne displays and the rainbow colored bars at bottom are frozen(don't scroll) and screen flashes off/on every 30 secs to that same AndroidOne screen.
However I can boot into Bootloader with no issues, and into Recovery mode as well, but there is not a WIPE CACHE option on this device... Obviously the Wipe data/factory reset option is there...
BUT BEFORE WE GET TO THAT POINT, WHaT GIVES? Anyone have any ideas?
few ?'s
#1 - In the Bootloader menu, What is this RESTART BOOTLOADER option for, what does it do?
#2 - Is there any way I can free up some space from Bootloader/Recovery as I'm pretty sure thats the cause of this problem I'm having. I was intending to do that today actually, was going to dump all my pics from the phone to a computer. ..
#3 - Is there any way I can see if my pic's backed up somewhere? New to the Google ecosystem...
#4 - Is there any way I can read or access the phones data via a computer, then perhaps I can delete a few pics to free up memory or better yet, wipe app caches to clear up memory instantly? PERHAPS even command line ????
Any and all other inputs and suggestions greatly appreciated before I take that step of wiping the device(which assumes I can start over with a working phone by doing that but not a guarantee).
Please ADVISE
much appreciated!
oNe
@Sean Price
Go to photos.google.com with the account you signed into your phone to see if they were backed-up.
jhedfors said:
@Sean Price
Go to photos.google.com with the account you signed into your phone to see if they were backed-up.
Click to expand...
Click to collapse
Thanks for the reply, so Google says I have backup turned off but my photos are in the timeline.. SO I just manually downloaded them all as a backup/pre-caution.
any other suggestions before I attempt the WIPE data/factory reset option from Bootloader > Recovery?
I can boot up fine into Bootloader and Recovery.
I can access the logs via . Bootloader > Recovery > View Recovery Logs
last line states the following: I:[libfs_mgr]fs_mgr_read_fstab_dt(): failed to read fstab from dt
please advise,
oNe
the internet failed, I found nothing on this issue and since I got 90% of my photos recovered via Google photos..
long story short, from Bootloader/Recovery I did the WIPE data/factory reset and i'm good to go now.
even updated my phone to all the latest android and moto updates, feels and seems like a totally new phone.. at a cost of 15gbs!! 15/32gbs used jus for the AndroidONE o/s, am I missing something?
oNe
Sean Price said:
the internet failed, I found nothing on this issue and since I got 90% of my photos recovered via Google photos..
long story short, from Bootloader/Recovery I did the WIPE data/factory reset and i'm good to go now.
even updated my phone to all the latest android and moto updates, feels and seems like a totally new phone.. at a cost of 15gbs!! 15/32gbs used jus for the AndroidONE o/s, am I missing something?
oNe
Click to expand...
Click to collapse
Not missing anything the OS takes up a lot of space. I am using a Pie ROM right now and system takes up 12GB.
johnjingle said:
Not missing anything the OS takes up a lot of space. I am using a Pie ROM right now and system takes up 12GB.
Click to expand...
Click to collapse
gotcha.. so basically 32gb's is the new 8gb
moving forward I'll try to stick to 64gb phone's and up..
oNe

Categories

Resources