Database Users

Oops! I changed LCD Density and now will not boot up.

Hey Everyone,
So I was being impatient and wanted to change the Density of my LCD on my Nexus 7. I changed it from the stock DPI to 170 using LCD Density Modder on the Market. Ever since reboot I have not been able to get past the google screen when you first turn on device. I can get into bootloader as well. My bootloader is unlocked and device is rooted if that helps.
Is there any easy way to recover the device besides a adb, or fastboot method? If not, what are the adb, fastboot commands to flash the OTA image to device from my PC?
Thanks

Download the nexus root toolkit, it can turn everything stock.
Sent from my LG-P999 using xda app-developers app

I have the nexus root toolkit, but don't you need the device powered on to put in usb debugging mode, etc? All I can do is hit google splash screen and get into bootloader, recovery.

There's buttons that say revert to stock, I believe those work in recovery.
Sent from my LG-P999 using xda app-developers app

redmonke255 said:
Download the nexus root toolkit, it can turn everything stock.
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
+1 just unlock and reflash
Sent from my i777 using xda app-developers app

Whenever I try to flash stock + unroot I get error message, "Windows cannot find 'C:\\data\gnexwug_DLnX.exe'. Make sure you typed the name correctly, and then try again."
Im not trying to type in anything, all I am doing is trying to restore to stock.

did you make a nandroid backup?" i am goign through the same thing right now. I am goign to restore from backup.
To change the desinty, it must be manually done in build.prod i assume. LCD Density modder might not be compatible, yet.
edit: Crap, i cant boot to recovery for some reason :/
edit2: it seems the only way to boot into recovery now is from a ROM manager application. Ijust finished restoring using the Nexus Toolkit.

I finally figured how to get SDK going and restored via nexus root toolkit. Thanks guys!
Sent from my Nexus 7 using xda app-developers app

mheller91 said:
I finally figured how to get SDK going and restored via nexus root toolkit. Thanks guys!
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Hi,
I stupidly did the same thing and am now in the same situation. :crying:
Can you tell me how you finally got it sorted?
Cheers

damienleetobin1976 said:
Hi,
I stupidly did the same thing and am now in the same situation. :crying:
Can you tell me how you finally got it sorted?
Cheers
Click to expand...
Click to collapse
Personally,
i booted into fastboot (all buttons if i remember correctly), then hit up the Tool Kit, go to advanced > temporary recovery, From there, i just restored my nandroid backup, or if you have any roms on there, just flash that.
You could do that, or once in fastboot and connected, you could just unlock, which will wipe everything.

tremblingwater said:
Personally,
i booted into fastboot (all buttons if i remember correctly), then hit up the Tool Kit, go to advanced > temporary recovery, From there, i just restored my nandroid backup, or if you have any roms on there, just flash that.
You could do that, or once in fastboot and connected, you could just unlock, which will wipe everything.
Click to expand...
Click to collapse
Hi,
I tried this and went for the Unlock route but after a restart it now just seems to be stuck at the google splash screen.
Is it usual to take this long?
Cheers

So what program is everyone using to change the DPI without getting a black screen?
Sent from my Nexus 7 using xda premium

theusername said:
So what program is everyone using to change the DPI without getting a black screen?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Just using a file explorer (specifically, solid explorer but root explorer should also work), navigating to /system/build.prop, and changing the number ro.sf.lcd_density.
changing that particular number's easy, and the last app I tried somehow managed to make a second build.prop inside the same file. So yeah.
Don't forget to backup your build.prop (preferably externally as well, in case you need to flash it) before trying this. And/or make a nandroid.

damienleetobin1976 said:
Hi,
I tried this and went for the Unlock route but after a restart it now just seems to be stuck at the google splash screen.
Is it usual to take this long?
Cheers
Click to expand...
Click to collapse
Im not sure, i dont want to advise something that is wrong, but, no, it doesn't take extraordinarily long. How long has it been?
I would boot into fastboot again and try the other route (provided you have a rom on the device or hopefully, better yet, a nandroid)

If you're using the cwm recovery from the toolkit you must be plugged in to usb to access cwm from the bootloader menu. From there you can reflash whatever you want to fix it.

jamesbra said:
If you're using the cwm recovery from the toolkit you must be plugged in to usb to access cwm from the bootloader menu. From there you can reflash whatever you want to fix it.
Click to expand...
Click to collapse
Yep, this is how it got it back and running last night.
I then used root explorer to edit build.prop and it worked like a charm.
Thanks all

In Recovery, wiped probably too much - no ROM

Like the title says.
I'm in recovery, I wiped it all (unfortunately even the ROM as zip I put on it) and now I don't have no ROM on it and no zip to flash a ROM.
Thought this was no problem, knowing from smartphone recoveries to mount sdcard and copying the file on it. But Nexus 7, well, has no sdcard.
What can I do?
As it is now, I don't have nothing on it and rebooting it wouldn't lead to anything useful.
I need help.
What can I do?
Thanks in advance.

l33ch0r said:
Like the title says.
I'm in recovery, I wiped it all (unfortunately even the ROM as zip I put on it) and now I don't have no ROM on it and no zip to flash a ROM.
Thought this was no problem, knowing from smartphone recoveries to mount sdcard and copying the file on it. But Nexus 7, well, has no sdcard.
What can I do?
As it is now, I don't have nothing on it and rebooting it wouldn't lead to anything useful.
I need help.
What can I do?
Thanks in advance.
Click to expand...
Click to collapse
If you have Android SDK installed, you can use adb push to push the zip file to your internal storage. Put the ROM zip file in your Android SDK - Platform Tools folder on your computer, reboot the N7 into Recovery (connected to computer of course!), open Command Prompt window and change directories to where ever you keep your Android SDK (for me, it's: cd sdk/platform-tools). Then type:
Code:
adb push <name of ROM zip file> /sdcard
Wait, and after about 20 - 60 seconds it'll complete, then you can flash the ROM. It'll be on the root of your internal sdcard (/sdcard).

Sounds difficult for a bloody rookie like me - is there really no easier way? Like transfering via recovery by just telling recovery to mound internal-sd so that it'll pop up on my pc? (know that from CWM and 4Ext on my smartphone)
Or could you explain the steps so that even the bloodiest rookie of them all could understand it properly :-/
aaaw **** -.-
by the way, device is still in recovery

l33ch0r said:
Sounds difficult for a bloody rookie like me - is there really no easier way? Like transfering via recovery by just telling recovery to mound internal-sd so that it'll pop up on my pc? (know that from CWM and 4Ext on my smartphone)
Click to expand...
Click to collapse
Maybe, I don't know. Have you tried it? What recovery are you using? I use TWRP.

RMarkwald said:
Maybe, I don't know. Have you tried it? What recovery are you using? I use TWRP.
Click to expand...
Click to collapse
TWRP as well. Just unlocked, rooted and flashed recovery and now I wanted to have a custom rom.
I tried to mount data and what else there was in "advanced" - my PC doesn't show me anything
Edit: not in advanced, it's the point "mount"

Restock and reroot.You can use Wugfresh toolkit for this. You just install the toolkit and if you can boot in bootloader mode you're saved. That's what I did and it solved my problem.
Sent from my Nexus 7 using xda premium

l33ch0r said:
TWRP as well. Just unlocked, rooted and flashed recovery and now I wanted to have a custom rom.
I tried to mount data and what else there was in "advanced" - my PC doesn't show me anything
Edit: not in advanced, it's the point "mount"
Click to expand...
Click to collapse
How'd you root/unlock, toolkit of some type?
Using the adb command mentioned is the only way that I know of to push a file to your N7. It's not as difficult to do as it sounds.

RMarkwald said:
How'd you root/unlock, toolkit of some type?
Using the adb command mentioned is the only way that I know of to push a file to your N7. It's not as difficult to do as it sounds.
Click to expand...
Click to collapse
Toolkit by WugFresh - I may try to get into bootloader and get back to stock - hopefully it works...

l33ch0r said:
Toolkit by WugFresh - I may try to get into bootloader and get back to stock - hopefully it works...
Click to expand...
Click to collapse
Yeah that would work, as long as you don't re-lock via fastboot. That's what probably wiped out your sdcard, was the fastboot unlock of your device, as it wipes your sdcard.

andymihail said:
Restock and reroot.You can use Wugfresh toolkit for this. You just install the toolkit and if you can boot in bootloader mode you're saved. That's what I did and it solved my problem.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Is it important which current status I choose?
There are 2 to be chosen: Soft-Bricked/Bootloop and Device is on/Normal
If "Device is on" means, that it's turned on, then this'll be my choice, right?
Totally shocked right now
This ain't even my device :-/

RMarkwald said:
Yeah that would work, as long as you don't re-lock via fastboot. That's what probably wiped out your sdcard, was the fastboot unlock of your device, as it wipes your sdcard.
Click to expand...
Click to collapse
No, wiping of my /sdcard was all my fault. I guess I have to take all credit for that
Well downloading the Stock with the toolkit takes quite some time...
foolish me -.-
Thanks for your help so far.
I'll definetely report whether it worked or not

I've never used any of the toolkits out there, I've done it using adb/fastboot commands in a Command Prompt window.

l33ch0r said:
Is it important which current status I choose?
There are 2 to be chosen: Soft-Bricked/Bootloop and Device is on/Normal
If "Device is on" means, that it's turned on, then this'll be my choice, right?
Totally shocked right now
This ain't even my device :-/
Click to expand...
Click to collapse
I can't remember my choice, was a few months ago.
Don't think you can go wrong with either.
I would try device is on.
Sent from my Nexus 7 using xda premium

RMarkwald said:
I've never used any of the toolkits out there, I've done it using adb/fastboot commands in a Command Prompt window.
Click to expand...
Click to collapse
I would've used your solution immediately but I'm just too unfamiliar with this method
Toolkits are probably the easiest way - and it was pretty easy - who could expect me to wipe the zip, I just moved to the storage before flashing it?...

Why does this file has to be hosted on goo.im?
Goo.im gives me roundabout 120kb/s...

It took a while for me also, but in the end everything worked well.
Sent from my GT-I9100 using xda premium

andymihail said:
It took a while for me also, but in the end everything worked well.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I desperately hope to have the same luck...will the bootloader still be unlocked after that procedure? I understand that root definetely is gone, but that shouldn't be a problem at all.

l33ch0r said:
I desperately hope to have the same luck...will the bootloader still be unlocked after that procedure? I understand that root definetely is gone, but that shouldn't be a problem at all.
Click to expand...
Click to collapse
It will remain unlocked until/unless you run the fastboot command: fastboot oem lock
If you don't run this, it will remain unlocked.

Whoaaaa I could scream!
Now that I downloaded the right one and try to flash it through the toolkit, it tells me, that there's no adb to be found. He doesn't recognize the device in bootloader.
What should I do?
OH THANK GOD! Tried it via recovery, he found it and restarted into bootloader

First of all: thank you so much guys - I was really shocked, but it all worked out
One more question before I make the same mistake again. Where should I put the zip which I wanna flash? When I have it connected to the pc, it shows me a portable device where the folders of the internal storage are (like Alarms, Android, DCIM, Download etc pp) - that's where I put the ZIP before.
Shall I keep it there?
And another question: what should I wipe in order to get it done properly?
Edit: Figured it out - got me CWM, much more familiar with that one
but thanks again for all your help guys

A solution for all those affected by the ,,forgot pattern'' bug

Finally, i have solved it !!! A couple of days ago, i forgot my pattern and clicked on forgot pattern, but i didn't get a prompt to turn on wifi. So basically, i was stuck, unless i wanted to do a factory reset and lose all of my data. Here's my unique solution to this problem, :
First of all, you need to be rooted and to have usb debugging ON. Otherwise, it won't work.
Second, you need to install wug's nexus toolkit, because it gives you an option to boot with a modified boot.img which has root privileges, go to advanced, you'll see it (if you know of any other way to boot up such an image, use it, because when you get locked out with the ,,forgot pattern'', your root won't work, that's why you need this boot image).
Here's what i did:
First, i booted the modified boot image and by using either adb or the toolkit, i pulled /data/data and /data/app to my pc.
Second, I made a full wipe and set up my N7 as usual. At this point, you need a good root file explorer in order to get to the /data folder. I installed colornote (from the app backup i made, because i wan't sure that there was a new version and,if there was, it could be a possible failure, because i wasn't sure how it would behave with the last version's data) and rebooted (in order for colornote to get into the dalvik cache).
Third, i opened up colornote's folder in /data/data and just replaced the databases folder with the one from my backup and i went to /data/dalvik-cache and deleted the corresponding color note dalvik file. Afterwards, i just rebooted and voila, all my stuff that i had written in color note was staring at me.
Now, i want to mention that i've only tried this with colornote (as it was my foremost priority to get to the essays that were stored there) and i've tried this on only 4.1.2. I can't guarantee that it will work on other apps or that you won't get damage to your precious Nexus 7, so please, proceed with caution, and don't blame me if something unexpected comes up. Good luck !!!
P.S. If you get more than one device or emulator, it's because you have bluestacks, disable or uninstall it, and you're good to go !!!

Did you try any of the suggestions offered to you in the other thread you started on this topic?
They seem like way less effort and some of them don't involve any wiping.
BTW when you do an adb pull you lose all file ownership and mode information; it is important to restore those correctly.
iAndroidOS said:
Second, you need to install wug's nexus toolkit, because it gives you an option to boot with a modified boot.img which has root privileges, go to advanced, you'll see it (if you know of any other way to boot up such an image, use it, because when you get locked out with the ,,forgot pattern'', your root won't work, that's why you need this boot image).
Click to expand...
Click to collapse
You can do whatever you want with the custom recovery - it is unaffected by the lock condition. You are complicating things by using a toolkit.
good luck

If you have USB debugging enabled you can just use adb to delete the pattern file and then unlock the tab.
Sent from my GT-I9000 using xda premium

NIMBAH said:
If you have USB debugging enabled you can just use adb to delete the pattern file and then unlock the tab.
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
I tried that and it didn't work

bftb0 said:
Did you try any of the suggestions offered to you in the other thread you started on this topic?
They seem like way less effort and some of them don't involve any wiping.
BTW when you do an adb pull you lose all file ownership and mode information; it is important to restore those correctly.
You can do whatever you want with the custom recovery - it is unaffected by the lock condition. You are complicating things by using a toolkit.
good luck
Click to expand...
Click to collapse
Thank you for reminding me, it is imperative to restore the permissions

iAndroidOS said:
I tried that and it didn't work
Click to expand...
Click to collapse
Weird I've done it a few times and its always worked. How did you do it ?
Sent from my GT-I9000 using xda premium

NIMBAH said:
Weird I've done it a few times and its always worked. How did you do it ?
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
I dunno, i went into adb and used the adb shell rm /data/system/gesture.key
command and as soon as it finished, i unplugged my N7 and rebooted it, and the login prompt was still there.

Bricked Nexus 7

Hey guys,
a few hours ago I tried flashing the new Ldroid Rom onto my Nexus 7. After flashing the rom my tablet took ages to boot up and after the bootup it said i had to enter a password to encrypt the data (i never set encryption). after entering a random password android reported that the password was right but the data corrupt and i'd have to do a factory reset. after entering twrp i realized that the device couldn't mount anything except system. i wiped/formated everything except system and tried booting into android. this time i was stuck at the google logo. after entering recovery mode again now twrp couldn't mount system and sdcard. so i formated both and now i'm here with an absolutely empty nexus 7. i tried to use adb sideload to flash a new rom but my pc doesn't recognize the device and neither does fastboot. i tried reinstalling adb and fastboot drivers, i used universal drivers, i used drivers from toolkits, i did many many pc and tablet restarts, i reinstalled android sdk several times, i used different adb/fastboot locations, i even tried using a different pc trying the same steps. no change, only thing i get is that the tablet gets recognized by the device manager as an adb/fastboot device, nothing more.
Does anyone of you know a possible sollution for my issue?
Thanks in advance
P.S.: i've been researching the internet for this issue for the past hours and couldn't find any sollutions, so please don't say stuff like "use search function"
P.P.S.: My other devices get recognized without any issues with the same cable.

I would suggest using wugs awesome software you need to make sure all partitions are wiped and repaired to which ever format you are trying to use ext4 or f2fs and through wugs you can flash new ROM through fastboot wigs has save my ass a few times one should not try to do tedious tasks after a long night of drinking hope this helps let me know if ya need more
Sent from my d2lte using XDA Free mobile app

Masterloki666 said:
I would suggest using wugs awesome software you need to make sure all partitions are wiped and repaired to which ever format you are trying to use ext4 or f2fs and through wugs you can flash new ROM through fastboot wigs has save my ass a few times one should not try to do tedious tasks after a long night of drinking hope this helps let me know if ya need more
Sent from my d2lte using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the reply.
The thing is that the device doesn't get recognized in fastboot mode by the fastboot interface. But I'll try anyways as soon as I'm at home again...

Wugss also has a option to restore soft bricked devices that should do the trick for ya if all else fails
Sent from my d2lte using XDA Free mobile app

Masterloki666 said:
Wugss also has a option to restore soft bricked devices that should do the trick for ya if all else fails
Sent from my d2lte using XDA Free mobile app
Click to expand...
Click to collapse
didn't work :/ device doesn't get recognized by fastboot but it's shown as fastboot device in the device manager

OK check verify all partitions are set and you can try to use adb and you can push a new os I believe that should work
Sent from my AOSP on Grouper using XDA Free mobile app

Masterloki666 said:
OK check verify all partitions are set and you can try to use adb and you can push a new os I believe that should work
Sent from my AOSP on Grouper using XDA Free mobile app
Click to expand...
Click to collapse
how can i do that?

http://forum.xda-developers.com/showthread.php?p=56749959 here's a post with syteps to fix and get you set up
Sent from my AOSP on Grouper using XDA Free mobile app

Masterloki666 said:
http://forum.xda-developers.com/showthread.php?p=56749959 here's a post with syteps to fix and get you set up
Sent from my AOSP on Grouper using XDA Free mobile app
Click to expand...
Click to collapse
Will not work as my device doesn't get recognized by fastboot.

OK are you on the latest twrp recovery if so you can go into that and enable mtp get the ROM and gapps and all other files you want to flash and drop them onto your device the only thing is it for some reason won't let you transfer zip files that's fine just rename from zip to txt
And it should work sorry for the delay in response hope that works for you lol
Sent from my d2lte using XDA Free mobile app

Excuse me I do not write good English. Today I had a similar problem. Tablet remained in bootloader and laptop does not see it
I used NRT function Back to Stock and click on Soft-Bricked / Bootloop.
Tablet runs on Lolipop
wwarrel: Dobrý:

Masterloki666 said:
OK are you on the latest twrp recovery if so you can go into that and enable mtp get the ROM and gapps and all other files you want to flash and drop them onto your device the only thing is it for some reason won't let you transfer zip files that's fine just rename from zip to txt
And it should work sorry for the delay in response hope that works for you lol
Sent from my d2lte using XDA Free mobile app
Click to expand...
Click to collapse
no I don't even if I had, it wouldn't work because I have no system on the tablet...
wwarrel said:
Excuse me I do not write good English. Today I had a similar problem. Tablet remained in bootloader and laptop does not see it
I used NRT function Back to Stock and click on Soft-Bricked / Bootloop.
Tablet runs on Lolipop
wwarrel: Dobrý:
Click to expand...
Click to collapse
Will not work because you need fastboot for it which is not working for me...

Alright I used my macbook for adb/fastboot and there it somehow recognized my device and I could use fastboot to do a factory reset. I still don't know why two independent windows systems did not recognize my Nexus 7 but I got it fixed. Anyways thanks to everyone who tried to help me in this thread!

[Q] broken N4

phone got wiped, os and all. can only get into team win recovery (no android with !). in recovery file manager there is NOTHING on the phone. can not get phone to be recognized by computer. used sdk to install drivers still nothing. can not activate usb debugging as there is no os. reboot in recovery gives warning no os on phone. there is nothing to restore, all folders in install tab are completely empty. is there anyway to save my phone? there is nothing on it...just enough for safe mode and recovery.

You need to get the computer to recognize your device. When booted into recovery and the device connected to your pc go to device manager and see what the issue is.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
You need to get the computer to recognize your device. When booted into recovery and the device connected to your pc go to device manager and see what the issue is.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
got drivers installed sees the device as "android bootloader interface...a link to what to do from this point would work or step by step instruction on how to get os on phone would be great.

Paltirian said:
got drivers installed sees the device as "android bootloader interface...a link to what to do from this point would work or step by step instruction on how to get os on phone would be great.
Click to expand...
Click to collapse
You've got two options
1. Flash the factory image.with fastboot. You'll then have to re-install twrp amrd root
2. Push a rom onto your device using adb in recovery. Then flash that in twrp
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
You've got two options
1. Flash the factory image.with fastboot. You'll then have to re-install twrp amrd root
2. Push a rom onto your device using adb in recovery. Then flash that in twrp
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
ok...it is recognized in fast boot but not in recovery. as far as i knew i only need the usb drivers that come from sdk as it is a google device. is there another driver set i need from recovery. where could i find super simple instructions of how to flash image? and if i didnt care about re rooting could i just use fast boot to flash iamge and run with that?

Paltirian said:
ok...it is recognized in fast boot but not in recovery. as far as i knew i only need the usb drivers that come from sdk as it is a google device. is there another driver set i need from recovery. where could i find super simple instructions of how to flash image? and if i didnt care about re rooting could i just use fast boot to flash iamge and run with that?
Click to expand...
Click to collapse
Simplest way is to download the factory image. Google nexus factory image. It's a .tgz file. Extract it using 7-zip. There's a flash-all.bat file in there. Boot into the bootloader and with your device connected to the pc just double click the flash-all.bat. It will wipe your device so if you can, backup first.
Sent from my Nexus 5 using XDA Free mobile app

You are my freaking hero. I'd give you a hug if i could. Will root tomorrow or so... Have you tried lollipop and would you recommend it over KitKat? Again ty so much

Paltirian said:
You are my freaking hero. I'd give you a hug if i could. Will root tomorrow or so... Have you tried lollipop and would you recommend it over KitKat? Again ty so much
Click to expand...
Click to collapse
No problem, glad you got it working. I like lollipop. It looks different but once you get over the difference you like it. I'm running 5.0.1
Sent from my Nexus 9 using XDA Free mobile app