Database Users

[Q] Shot self in foot, edited build.prop now N7 won't boot

I was testing tablet UI mode by editing the /system/build.prop file. The N7 went into Tablet UI mode OK but I didn't like it so I reedited the /system/build.prop file to undo my edits, and now the N7 doesn't boot properly. It goes to a black screen and just sit there.
I can boot into recovery and I can get adb to work. I used the pull command to get a copy of the build.prop file and it seems OK but I'm not 100% sure if I made any other edits by mistake. Of course like a fool I didn't make a backup of the original.
Can anyone make some suggestions on how to fix my N7?
Thanks.

lbloo said:
I was testing tablet UI mode by editing the /system/build.prop file. The N7 went into Tablet UI mode OK but I didn't like it so I reedited the /system/build.prop file to undo my edits, and now the N7 doesn't boot properly. It goes to a black screen and just sit there.
I can boot into recovery and I can get adb to work. I used the pull command to get a copy of the build.prop file and it seems OK but I'm not 100% sure if I made any other edits by mistake. Of course like a fool I didn't make a backup of the original.
Can anyone make some suggestions on how to fix my N7?
Thanks.
Click to expand...
Click to collapse
reflash your ROM. it'll replace your build.prop with a good copy. don't wipe a thing, just reflash.

I'm rooted but on stock. Can I just download a copy of the stock rom and flash that with CWM?

lbloo said:
I'm rooted but on stock. Can I just download a copy of the stock rom and flash that with CWM?
Click to expand...
Click to collapse
rooted stock ROM yea. I've also flashed a pure aosp ROM over stock without any reprocussions.

Before I go ahead and reflash I just want to make sure I'm getting it right. I've downloaded the stock rom, extracted image-nakasi-jro03d.zip. I should push this file to my internal storage, then use CWM to flash? Or should I just find a pure aosp ROM and flash that?
Sorry for all the questions, I just don't want to make things worse.

lbloo said:
Before I go ahead and reflash I just want to make sure I'm getting it right. I've downloaded the stock rom, extracted image-nakasi-jro03d.zip. I should push this file to my internal storage, then use CWM to flash? Or should I just find a pure aosp ROM and flash that?
Sorry for all the questions, I just don't want to make things worse.
Click to expand...
Click to collapse
I don't know what you picked up, but here's a stock/rooted ROM that you can flash in your cwm recovery http://forum.xda-developers.com/showthread.php?t=1776330
Aosp works too, its your choice

if you know how to use adb you can just boot to recovery and push the stock build.prop to your tab

I downloaded a stock copy of the stock build.prop, used the adb push command to push it into /system rebooted and nothing. Still hangs on black screen upon boot.
I then downloaded the stock ROM which simms22 kindly pointed me to, used the adb push command to copy the zip file into /data/media/Firmware, used CWM v6.0.1.0 to "install zip file from sdcard" and I got an error, here is the output:
Installing:/sdcard/Firmware/Nexus7 - JRo03d-Odexed-ROOT_4.1.1_signed.zip
Finding update package...
Opening update package...
Installing update package...
E:Error in /sdcard/Firmware/Nexus7 - JRo03d-Odexed-ROOT_4.1.1_signed.zip
(Status 0)
Installation aborted.
I tried both the Odexed and Deodexed files, both gave same results.
Am I missing a step in the process?

It's working now!
I was afraid I was messing up some of the adb commands so I downloaded the Nexus 7 Toolkit 2.0 (Great tool for someone like me)
- via Toolkit re-transferred the odexed and deodexed ROM files, reflashed, same errors as above
- via Toolkit re-installed CWM Recovery 6.0.1.0, reflashed, same errors as above
- via ADB Shell used CHMOD to modify file rights of the ROM files (stab in the dark), same errors as above
- downloaded stock image from CWM site (JRO03D_grouper.zip), pushed via tool kit, flashed via CWM....WORKED!!!
Everything is as it was before, no need for a full wipe! I'm going to do a backup right now!
Not sure why the other ROMS would not flash, but at this point I'm not going to mess around to try to figure it out.
Many thanks to simms22 and PhxkinMassacre for getting me pointed in the right direction.

prly a bad download.
after pushing the file you need to set the correct mode:
Code:
adb shell chmod 644 /system/build.prop

Me too - also hosed my own build.prop
lbloo said:
- downloaded stock image from CWM site (JRO03D_grouper.zip), pushed via tool kit, flashed via CWM....WORKED!!!
Everything is as it was before, no need for a full wipe! I'm going to do a backup right now!
Click to expand...
Click to collapse
Ok, I did the exact same thing and followed these instructions but haven't had any luck.
First, thanks lbloo and the folks who have responded for all the info here. I have downloaded JRO03D_grouper.zip and I am grateful for the tip to the toolkit.
When I have pushed JRO03D_grouper.zip to the N7, it appears to have worked, but I can't find it on the sdcard. I am pushing from the default location to /sdcard/. I then select "install zip from sdcard" and "choose zip from sdcard" but the only zip there is supersu (from Day 1).
For reference, this is CWM Recovery v 6.0.0.6.
Thanks in advance for any help anyone can offer.
Jack

Looking back I don't recall resetting the file rights after modifying the file and that was likely the root cause of my problems.
You should try the chmod command a couple of posts back.

JackinNC said:
Ok, I did the exact same thing and followed these instructions but haven't had any luck.
First, thanks lbloo and the folks who have responded for all the info here. I have downloaded JRO03D_grouper.zip and I am grateful for the tip to the toolkit.
When I have pushed JRO03D_grouper.zip to the N7, it appears to have worked, but I can't find it on the sdcard. I am pushing from the default location to /sdcard/. I then select "install zip from sdcard" and "choose zip from sdcard" but the only zip there is supersu (from Day 1).
For reference, this is CWM Recovery v 6.0.0.6.
Thanks in advance for any help anyone can offer.
Jack
Click to expand...
Click to collapse
What location did you push it to? /sdcard/?
Sent from my Nexus 7 using xda app-developers app

mvmacd said:
What location did you push it to? /sdcard/?
Click to expand...
Click to collapse
Yes. And, to further test, I created a little zip file called test.zip and pushed it to the tablet. I can see it just fine. It's just the grouper zip that I can't find.
Thanks
Jack

I just noticed a diff in filesize between the JRO03D_grouper.zip file I am using and one shown in a Youtube video entitled "how to put a rom to flash on a semi-bricked nexus 7 with recovery" by Youtube user metroid031993. (I'm too green to post outside links on XDA)
Mine is 261814702 bytes, the one shown in the video is 32650144 bytes.
Perhaps this is my problem, an invalid zip file. What do you think? And, can someone please tell me the correct size of JRO03D_grouper.zip?
Thanks
Jack
[Note to moderator(s): If I am heading off track in this thread, please don't hesitate to move it or to instruct me to create a new thread. I think the issue may have changed, but I have stayed here since this is where the conversation is for my root issue. Thx!]

JackinNC said:
can someone please tell me the correct size of JRO03D_grouper.zip?
Click to expand...
Click to collapse
Not sure what's up with the youtube video you're using, but 261814702 bytes is the correct size.

Visa Declined said:
Not sure what's up with the youtube video you're using, but 261814702 bytes is the correct size.
Click to expand...
Click to collapse
Thanks for the confirmation.
Ok, back to trying to figure out why it doesn't appear in CWM Recovery after I've pushed it...
---------- Post added at 11:19 AM ---------- Previous post was at 10:51 AM ----------
JackinNC said:
Ok, back to trying to figure out why it doesn't appear in CWM Recovery after I've pushed it...
Click to expand...
Click to collapse
Well, I got the grouper zip into /sdcard/ and was able to upgrade without losing anything. w00t!
Theory:
I was in the same adb "session" this time since I was using adb from the command line. Meaning, the daemon was still running from the first push I did. So, while I couldn't see the grouper zip after the first push (consistent with your experience, dark_samus), I could see it and upgrade with it after second push (also consistent). And, perhaps my previous attempts didn't work before because I was closing and opening the Nexus 7 Toolkit each time, therefore stopping and restarting the daemon, which meant that each push attempt was the first attempt for that "session."
I don't have any solid technical basis to support or refute that theory, it's just one possible theory that, if true, would result in the experience I had.
My problem is resolved. Thanks to everyone who contributed to this, I truly appreciate your help!
Jack

simms22 said:
reflash your ROM. it'll replace your build.prop with a good copy. don't wipe a thing, just reflash.
Click to expand...
Click to collapse
how to put the stock image if my n7 doesnt boot to android? pls help
i have CWM already

Either replace the complete system partition using 'fastboot flash',
or, probably less intrusive, boot into recovery mount system partition writeable and push build.prop manually using 'adb push'.
Sent from my Nexus 7 using xda app-developers app

AndDiSa said:
Either replace the complete system partition using 'fastboot flash',
or, probably less intrusive, boot into recovery mount system partition writeable and push build.prop manually using 'adb push'.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
my bad i already flash a fresh stock rom again, but thanks anyways...

Soft Bricked- Still have CWM and by bootloader up, but can't mountSD to put a ROM on!

I'm just trouble today.... So how might I get the rom onto the SD or just pushed to be able to give this another go! I've got one downloaded, but if I a need stock tgz file, please do guide me through!
#help.
Thanks everyone!

You can push files using adb push rom.zip /sdcard/ otherwise flash a stock image with fastboot.

peachpuff said:
You can push files using adb push rom.zip /sdcard/ otherwise flash a stock image with fastboot.
Click to expand...
Click to collapse
Great, will check back if needed! Thanks!

[Q] Need unmodified JWR66Y build.prop file

Hello,
I kind of messed up with my nexus 4's build.prop file and forgot to back up
Will someone be kind enough and upload their unmodified build.prop file (JWR66Y).
Thanks.

avi619 said:
Hello,
I kind of messed up with my nexus 4's build.prop file and forgot to back up
Will someone be kind enough and upload their unmodified build.prop file (JWR66Y).
Thanks.
Click to expand...
Click to collapse
Go to https://developers.google.com/android/nexus/images and download the 4.3 factory image, then extract the build.prop file

Desno365 said:
Go to https://developers.google.com/android/nexus/images and download the 4.3 factory image, then extract the build.prop file
Click to expand...
Click to collapse
How do I extract the .img file? 7zip does not seem to work.

avi619 said:
How do I extract the .img file? 7zip does not seem to work.
Click to expand...
Click to collapse
I forgot the img file sorry.
I will upload it for you, wait a moment

Desno365 said:
Go to https://developers.google.com/android/nexus/images and download the 4.3 factory image, then extract the build.prop file
Click to expand...
Click to collapse
Desno365 said:
I forgot the img file sorry.
I will upload it for you, wait a moment
Click to expand...
Click to collapse
I found a tool here and extracted the image via linux reader. Replaced the build.prop file and when I restarted my phone it went completely blank.
The google logo also did not show. I think I bricked it

avi619 said:
I found a tool here and extracted the image via linux reader. Replaced the build.prop file and when I restarted my phone it went completely blank.
The google logo also did not show. I think I bricked it
Click to expand...
Click to collapse
Don't worry you didn't brick it, how do you replace the build.prop file?

Desno365 said:
Don't worry you didn't brick it, how do you replace the build.prop file?
Click to expand...
Click to collapse
ES File Manager. My phone is rooted.

avi619 said:
ES File Manager. My phone is rooted.
Click to expand...
Click to collapse
Did you set the correct permissions (rw-r--r--)? Maybe this is the problem.
If your phone doesn't boot, restore a nandroid backup or flash a ROM

Desno365 said:
Did you set the correct permissions (rw-r--r--)? Maybe this is the problem.
If your phone doesn't boot, restore a nandroid backup or flash a ROM
Click to expand...
Click to collapse
No I did not set those permissions. Just replaced the build.prop file. I don't know what nandroid backup is but I have TWRP installed.
PS: The phone is still on the blank screen.

avi619 said:
No I did not set those permissions. Just replaced the build.prop file. I don't know what nandroid backup is but I have TWRP installed.
PS: The phone is still on the blank screen.
Click to expand...
Click to collapse
If you have a ROM in sdcard flash it, if you haven't you have to flash a ROM with adb sideload or a factory image with fastboot (the factory image will erase your data!)

Desno365 said:
If you have a ROM in sdcard flash it, if you haven't you have to flash a ROM with adb sideload or a factory image with fastboot (the factory image will erase your data!)
Click to expand...
Click to collapse
Thanks, I m going to flash 4.4 stock rom from http://forum.xda-developers.com/showthread.php?t=2535728

Alright, quick update:
I used adb sideload to flash the rom from my above post. Worked like a charm, and I have Kitkat running with root. Also, no data was lost.
First thing I am gonna do now is backup my build.prop and data
Thanks for the help.
Cheers.

avi619 said:
Alright, quick update:
I used adb sideload to flash the rom from my above post. Worked like a charm, and I have Kitkat running with root. Also, no data was lost.
First thing I am gonna do now is backup my build.prop and data
Thanks for the help.
Cheers.
Click to expand...
Click to collapse
Great!

I made the same mistake before, when I hide the softkeys
just for reference, you could have fixed it easily, just by using TWRP's File manager:
1. Mount System
2. Replace with the original Build.prop inside the system directory
3. Click the file -> Change file permissions chmod 775

[Q] No TWRP folder.

Hello guys.
I want to flash 5.0.1 on my Nexus 4 and I did a TWRP backup for my data, however, I don't see the TWRP folder anywhere.
I tried to pull the file with adb but I get permission denied error (I do have root permission).
I tried to go into recovery and see if I can get the file this way, no success.
Please help me.

https://www.google.com/search?q=mis...obile&sourceid=chrome-mobile&espvd=1&ie=UTF-8

Wassupdog said:
Hello guys.
I want to flash 5.0.1 on my Nexus 4 and I did a TWRP backup for my data, however, I don't see the TWRP folder anywhere.
I tried to pull the file with adb but I get permission denied error (I do have root permission).
I tried to go into recovery and see if I can get the file this way, no success.
Please help me.
Click to expand...
Click to collapse
TWRP/ mount/enable MTP and everything will return to the place of sdcard/twrp/backup

Berrydroidcafe said:
https://www.google.com/search?q=mis...obile&sourceid=chrome-mobile&espvd=1&ie=UTF-8
Click to expand...
Click to collapse
pincher65 said:
TWRP/ mount/enable MTP and everything will return to the place of sdcard/twrp/backup
Click to expand...
Click to collapse
Thank you both!

Help. Soft bricked my 6p.

I was restoring a twrp backup and when it reaches "flashing system image" in the restore process it just reboots. Ive tried a few things but cant get it going. It just bootloops.

dontbeweakvato said:
I was restoring a twrp backup and when it reaches "flashing system image" in the restore process it just reboots. Ive tried a few things but cant get it going. It just bootloops.
Click to expand...
Click to collapse
Flash the factory images with fastboot, see section 9 of my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Did you actually backup "system image" or just "system"? It should be only system, not the system image.

Heisenberg said:
Flash the factory images with fastboot, see section 9 of my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Did you actually backup "system image" or just "system"? It should be only system, not the system image.
Click to expand...
Click to collapse
That was my first rooted twrp backup on 6p. I checked everything under what to backup. It has a system and system image to backup along with everything else. I thought it was weird to have both of them because I've never seen that before in twrp.

Well im back to normal. I must of screwed up the restore with the "system" and "system image" business. What's the difference in twrp restore between the two?

dontbeweakvato said:
Well im back to normal. I must of screwed up the restore with the "system" and "system image" business. What's the difference in twrp restore between the two?
Click to expand...
Click to collapse
Honestly, I don't know. I only know that you only need to backup system, boot, and data (if you want your apps and settings).

Heisenberg said:
Flash the factory images with fastboot, see section 9 of my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Did you actually backup "system image" or just "system"? It should be only system, not the system image.
Click to expand...
Click to collapse
I have a soft bricked phone... I have done everything in your thread and flashing all the files worked except i get an error when flashing the system.img
it says error unable to allocate xxxxxxx bytes...? i really want my phone back to normal.. PLEAS HELP

taylorleach said:
I have a soft bricked phone... I have done everything in your thread and flashing all the files worked except i get an error when flashing the system.img
it says error unable to allocate xxxxxxx bytes...? i really want my phone back to normal.. PLEAS HELP
Click to expand...
Click to collapse
Try to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files.

indian84 said:
Try to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files.
Click to expand...
Click to collapse
I am sorry what do you mean?? what commands should I try?

taylorleach said:
I am sorry what do you mean?? what commands should I try?
Click to expand...
Click to collapse
Try this.
Reboot Bootloader again
1. fastboot erase userdata
And then follow the guide. Hopefully this will help.

indian84 said:
Try this.
Reboot Bootloader again
1. fastboot erase userdata
And then follow the guide. Hopefully this will help.
Click to expand...
Click to collapse
so, just to clarify... run the command "fastboot erase userdata" then run all of the IMG files?

taylorleach said:
so, just to clarify... run the command "fastboot erase userdata" then run all of the IMG files?
Click to expand...
Click to collapse
My bad.
use command fastboot format userdata
This will erase everything on your phone. Including photos and all the media.
After this use below command
fastboot reboot bootloader
And then follow guide and flash all IMG files.

indian84 said:
My bad.
use command fastboot format userdata
This will erase everything on your phone. Including photos and all the media.
After this use below command
fastboot reboot bootloader
And then follow guide and flash all IMG files.
Click to expand...
Click to collapse
that did not work same problem
"load_file: could not allocate 2014315040 bytes
error: cannot load 'C:\angler\images\system.img"
all other .img files i get OKAY except for system.img
PLEASE HELP ME UGG I REALLY NEED MY PHONE TO WORK AGAIN. I even tried re downloading the 6.0.1 again and also tried rebooting PC and multiple USB ports...

taylorleach said:
that did not work same problem
"load_file: could not allocate 2014315040 bytes
error: cannot load 'C:\angler\images\system.img"
all other .img files i get OKAY except for system.img
PLEASE HELP ME UGG I REALLY NEED MY PHONE TO WORK AGAIN. I even tried re downloading the 6.0.1 again and also tried rebooting PC and multiple USB ports...
Click to expand...
Click to collapse
You need to update your fastboot on your PC update everything in Android SDK or install latest minimal adb and fastboot. The system needs to be sent/flashed in parts as it's a big file. That will/should fix your issue.

matt1515 said:
You need to update your fastboot on your PC update everything in Android SDK or install latest minimal adb and fastboot. The system needs to be sent/flashed in parts as it's a big file. That will/should fix your issue.
Click to expand...
Click to collapse
I really appreciate your reply.. But i am a bit new to the Nexus and fastboot (sdk) environment. How do I update fastboot? I believe I have updated my Android Studio properly already. Is there a way to flash that system.img in stages then? I am so confused. Thanks again in advance!!!

taylorleach said:
I really appreciate your reply.. But i am a bit new to the Nexus and fastboot (sdk) environment. How do I update fastboot? I believe I have updated my Android Studio properly already. Is there a way to flash that system.img in stages then? I am so confused. Thanks again in advance!!!
Click to expand...
Click to collapse
Assuming you have Windows go to this site and download latest version(1.31) https://androidmtk.com/download-minimal-adb-and-fastboot-tool
Read Heisenberg's thread on how to flash everything but put all your files(system, boot, bootloader, radio, boot, vendor, cache, userdata in the minimal adb and fastboot folder hold shift right click and open cmd window and flash away it will work follow Heisenberg's thread and you should be good! Good luck!

taylorleach said:
I really appreciate your reply.. But i am a bit new to the Nexus and fastboot (sdk) environment. How do I update fastboot? I believe I have updated my Android Studio properly already. Is there a way to flash that system.img in stages then? I am so confused. Thanks again in advance!!!
Click to expand...
Click to collapse
matt1515 said:
Assuming you have Windows go to this site and download latest version(1.31) https://androidmtk.com/download-minimal-adb-and-fastboot-tool
Read Heisenberg's thread on how to flash everything but put all your files(system, boot, bootloader, radio, boot, vendor, cache, userdata in the minimal adb and fastboot folder hold shift right click and open cmd window and flash away it will work follow Heisenberg's thread and you should be good! Good luck!
Click to expand...
Click to collapse
If you already have the Android SDK it probably isn't a good idea to start installing other versions. Just go to where you installed the SDK on your PC, open SDK Manager, and update the platform-tools package.

matt1515 said:
Assuming you have Windows go to this site and download latest version(1.31) https://androidmtk.com/download-minimal-adb-and-fastboot-tool
Read Heisenberg's thread on how to flash everything but put all your files(system, boot, bootloader, radio, boot, vendor, cache, userdata in the minimal adb and fastboot folder hold shift right click and open cmd window and flash away it will work follow Heisenberg's thread and you should be good! Good luck!
Click to expand...
Click to collapse
YOUR ARE MY BEST FRIEND THANK YOU SO MUCH!! I knew I was close to figuring it out but I seriously appreciate your help good sir.
So, to ask one more question. I flashed TWRP totally fine, but when I when to reboot after failing to find my SU.zip in my phones directory (due to 0MB detected.. i don't know why) it asked me if I wanted to root because I was currently not rooted and I just said yes.. was that why it got stuck in a bootloop? I never actually directed it at my specific SU.zip file because it wouldn't appear in the phones files?

taylorleach said:
YOUR ARE MY BEST FRIEND THANK YOU SO MUCH!! I knew I was close to figuring it out but I seriously appreciate your help good sir.
So, to ask one more question. I flashed TWRP totally fine, but when I when to reboot after failing to find my SU.zip in my phones directory (due to 0MB detected.. i don't know why) it asked me if I wanted to root because I was currently not rooted and I just said yes.. was that why it got stuck in a bootloop? I never actually directed it at my specific SU.zip file because it wouldn't appear in the phones files?
Click to expand...
Click to collapse
Yes that's why it was stuck in a boot loop, the version of SuperSU that's included in TWRP is incompatible. Which version of TWRP did you flash? You need the latest in order for it to be able to successfully decrypt your storage so you can view it.

Heisenberg said:
Yes that's why it was stuck in a boot loop, the version of SuperSU that's included in TWRP is incompatible. Which version of TWRP did you flash? You need the latest in order for it to be able to successfully decrypt your storage so you can view it.
Click to expand...
Click to collapse
To be honest, I moved the file to my phones directory from my PC and did not just copy it so I lost it lol. Could you please tell me what one I should flash so I don't mess anything up. PLEASE and THANK YOU

taylorleach said:
YOUR ARE MY BEST FRIEND THANK YOU SO MUCH!! I knew I was close to figuring it out but I seriously appreciate your help good sir.
So, to ask one more question. I flashed TWRP totally fine, but when I when to reboot after failing to find my SU.zip in my phones directory (due to 0MB detected.. i don't know why) it asked me if I wanted to root because I was currently not rooted and I just said yes.. was that why it got stuck in a bootloop? I never actually directed it at my specific SU.zip file because it wouldn't appear in the phones files?
Click to expand...
Click to collapse
+1 on Heisenberg you should use Android SDK and update properly but I knew you needed to get back up and running and figured that was the fastest way to help you. Read his thread like you would a book you will learn all you need to learn! But glad to hear I was able to help! Always use latest TWRP and SuperSU and you will be fine if you can decrypt then install SuperSU that way if not just hit cancel and adb sideload it. Look in general thread for the TWRP thread. Good luck and enjoy your working phone again!