Related
I'm not responsible to any damage which is caused by applying any modification listed below to your phone.
Backup
If you made mistake to this file, you phone will not boot in gui, so you should always backup the file before you make any change to it. Just use any file manager to copy the file to your sd card or your pc.
Restore
If you have a Linux machine you can mount the /system partition while plugging in with the purple screen (vol up + vol down + power).
Easiest way: get Ubuntu, put your phone in purple screen, plug in with USB, you will see the system partition at your Ubuntu desktop.
The hard way: if the /system partition is no accessible under purple screen mode (such as in the latest 528 rom), you can use adb push the backup file back, search the web for details about how to use adb.
I'm digging the build.prop, some apps can do some of these tweaks for you, but I prefer typing myself. You need to reboot the phone to take effect.
1. windowsmgr.max_events_per_sec=75
add this new line to make UI more responsive, the bigger the value the more responsive, I've tried 90, too fast, fall back to 75, still quite fast
2. ro.config.hw_menu_unlockscreen=false
change value from "false" to "true" to enable menu key unlocking screen
3. ro.sf.lcd_density=240
change to 225 to increase the resolution of display, as a result, the size of icon on home page and fonts of list (of file manager or contact) become smaller, the smaller the value the smaller size of icon and fonts
4. dalvik.vm.heapsize=24m
increase the value to 32m~48m to increase stability and performance, tested but doesn't see much effect so far
all so if you tried games like nova or brother in arms that have black screen or graphic probs do this they now all work
go to /system/build.prop and edit it to this then close and turn the phone off / on do a build.prop DO A BUILD.PROP BACKUP FIRST ALLWAYS A MUST BEFOR PLAYING AROUND.
once the phone is on go to settings about phone model number and it will say Desire HD.
Then download games for the htc desire hd and it works.
if you want it back to standed just replace it with the backup
i think the suggestions are great!
big thx!!!
thanks for the share
Do I just change the name, where it says build.prop now?
sorry there are still some games that wont work like brother in arms 2 and modern combat black pegasus but all the others work like
splinter cell
sandstorm
n.o.v.a.
and so on
your phone hast to be rooted and use root explorer and go to
/system/build.prop and open and edit the text then reboot your phone
backed up the build.prop and made the changes. On restart it hangs on boot screen (huawei name and logo) I have to remove the battery to switch off. tried connecting to the PC to restore build.prop but it doesnt load the phone memory. Only launches the mobile partner autostart. Also tried updating by adding update.zip to sd card but says signature verification failed. Tried lading general update from huaweidevice.com onto dload directory on sd card, Just shows purple screen on booting with power, vol up and down. Please advice.
adrdsouza said:
backed up the build.prop and made the changes. On restart it hangs on boot screen (huawei name and logo) I have to remove the battery to switch off. tried connecting to the PC to restore build.prop but it doesnt load the phone memory. Only launches the mobile partner autostart. Also tried updating by adding update.zip to sd card but says signature verification failed. Tried lading general update from huaweidevice.com onto dload directory on sd card, Just shows purple screen on booting with power, vol up and down. Please advice.
Click to expand...
Click to collapse
If you have a Linux machine you can mount the /system partition while plugging in with the purple screen (vol up + vol down + power).
Easiest way: get Ubuntu, put your phone in purple screen, plug in with USB, you will see the system partition at your Ubuntu desktop.
Thank you..a mate uses linux so went over and it worked like a charm. I hadn't put the 'm' at the end in 'dalvik.vm.heapsize=24m' but it is sorted now. Thanks again.
Hi there.Is there any value in build.prop file to decrease the time that the screen rotates?I measure that the default time is about 1sec.I want it 500ms or lower.
ive root and root explorer, but when i try to edit the build.prob it says that its read only rom .
whats the problem?
sry for my bad english
In the top right hand corner there is a button which says 'mount r/w' press it and your filesystem will be read/write. Then make the changes to build.prop then press the button again then reboot.
volume headphones?
Where can I find the file corresponding to the volume of the sound through headphones? A similar problem occurred on the ZTE, but was repaired in the new ROM.
Piron said:
Where can I find the file corresponding to the volume of the sound through headphones? A similar problem occurred on the ZTE, but was repaired in the new ROM.
Click to expand...
Click to collapse
/system/etc/hwVolumeFactor.cfg
iamelton said:
/system/etc/hwVolumeFactor.cfg
Click to expand...
Click to collapse
I found the compination of speaker=80 and wired_headset=80 pretty cool.Has anyone found a better setting?
headphone volume
80 is too much. For me the best settings are:
- speaker 75 (default)
- Headphones 70 (higher values will cause the overload of sound)
With this setup is really cool .
Swype
The original ROM is installed Swype keyboard, but not in the Polish language. It is not possible to uninstall Swype and you can not install a new keyboard. Despite the ROOT system does not allow the removal of the keyboard ("cust/hw/ideos_x5/app / "). Does anyone know how to remove the keyboard, or where to replace your dictionary?
adrdsouza said:
Thank you..a mate uses linux so went over and it worked like a charm. I hadn't put the 'm' at the end in 'dalvik.vm.heapsize=24m' but it is sorted now. Thanks again.
Click to expand...
Click to collapse
unfortunately I've got the same problem with you, I changed a file's name in the system/ directory now the phone bricks. I mounted it on mu ubuntu laptop and found that file but it says I have no permission to change it back...what should do now?
edit: never mind, I got it solved with sudo. I am a stupid linux noobie.
I just opened the file, but there's no "windowsmgr.max_events_per_sec" in it, i found the rest (2-4), does someone know why?
Edit: after applying the B160 ROM, i found this line, works great
HI Guys,
Maybe somewhat can help me out here, in my attempt to update my Acer A500, I may have in a kind of way bricked my phone. I attempted to replace wpa_supplicant file as per some of the instructions, needless to say the update failed and me in my pure genius figure I would simply factory reset and reboot. Which I ended up doing, the problem now is that the WIFI does not turn on and my tab has been unrooted, I no longer have any file explorer app on the phone and I can't download anything. Does anybody know how I can gain access to the root files so that I may revert back the old file, or somehow install an apk file from the mini sdcard or even get access to the internet via bluetooth or USB. Anything would be helpful.
FYI - I am trying to gain access to my root files using Android SDK, but I've always had problems getting any of my pc to find any of the android stuff when plugged in.
Ph0tin0 said:
HI Guys,
Maybe somewhat can help me out here, in my attempt to update my Acer A500, I may have in a kind of way bricked my phone. I attempted to replace wpa_supplicant file as per some of the instructions, needless to say the update failed and me in my pure genius figure I would simply factory reset and reboot. Which I ended up doing, the problem now is that the WIFI does not turn on and my tab has been unrooted, I no longer have any file explorer app on the phone and I can't download anything. Does anybody know how I can gain access to the root files so that I may revert back the old file, or somehow install an apk file from the mini sdcard or even get access to the internet via bluetooth or USB. Anything would be helpful.
FYI - I am trying to gain access to my root files using Android SDK, but I've always had problems getting any of my pc to find any of the android stuff when plugged in.
Click to expand...
Click to collapse
I was in this court just yesterday, swearing up and down for some reason.
You'll need the root explorer apk, gingerbreak apk and the original wpa_supplicant file posted all over XDA.
Download and install Android SDK. It will also make you download the Java SDK too before you install the Android one. Start installing the Android SDK. It will seem like it's going to take forever, but you really only need what's in the folders 2 minutes in.
Go into the program files folder where the SDK stuff is and rip the 3 ADB files out and place them in their own folder. Mine were in: c:\program files\android\android-sdk\platform-tools\
I took the 3 files out and placed them in c:\and\
Place the apks in the c:\and\ folder
Make sure the driver files are installed from the Acer website.
Make sure USB bugging and apps from outside sources are enabled in settings on the tab.
Plug the tab into the PC via USB.
Open up the command prompt and go to the c:\and\ folder
then type
adb install c:\and\rootexplorer.apk
ENTER
then
adb install c:\and\gingerbreak-v1.20.apk
ENTER
The apps should be now installed on the tab.
Then just transfer the wpa_supplicant file over and you're right where you need to be.
Make sure you change the permissions on the wpa_supplicant file like you did the first time (enable everything read/write/etc etc) by holding on the wpa_supplicant file that you paste.
rorytmeadows said:
Open up the command prompt and go to the c:\and\ folder
then type
adb install c:\and\rootexplorer.apk
ENTER
then
adb install c:\and\gingerbreak-v1.20.apk
ENTER
The apps should be now installed on the tab.
Then just transfer the wpa_supplicant file over and you're right where you need to be.
Make sure you change the permissions on the wpa_supplicant file like you did the first time (enable everything read/write/etc etc) by holding on the wpa_supplicant file that you paste.
Click to expand...
Click to collapse
You are my new hero, all this time I've been trying to get Android ADK to recognize my tablet, but to no success. All I had to do was run ADB, which Ironically I had done, but only to see if it recognizes my unit. I was not aware I can install apps with it.
I'm not worthy... I'm not worthy
A million thank you's, now to try and get 3.1 installed and hopefully Googel/android was smart enough to put in a stock file explorer.
Not working wifi hardware
Somewhat similar to what happened to this guy. But to be specific, I am using an acer a500 originally on a rooted ics 4.0.3, i remember using lucky patcher and using the custom patch on adobe flash player then i saw an update regarding busybox and superSU...i was able to install the busybox updater but not the superSU since i remembered i already had superuser. I opened superuser and then it updated...from then on...I lost my wifi...at start it was still there but it can't connect. also, i lost my root because i no longer am able to use titanium backup. double checking it, i downloaded a root checker and it displayed not properly rooted. seeing this, i thought it's been a long time since i've updated my rom so i might as well upgrade everything...my bootloader, kernel, rom. So i first degraded it by flashing to the full package stock HC 3.1 ROM (it had an old HC 3.1 bootloader). Then i noticed i can no longer turn on my wifi and use my old apps...I flashed it back to a NON-rooted stock ics 4.0.3 thinking it might fix it...but it did not. HELP please...
When I originally bought the Nook HD+, I made several futile attempts to get ADB working so I could sideload apps to it. I was so frustrated that I was ready to give up and return it. But I finally got it going and with the help of a few smart users here was able to get it rooted and installing apps directly on the device. So, to save some other users the same frustration I had, I thought I would outline what I did to make this device hum.
Update 12/27/2012: A lot has changed since I first created this tips thread. I am updating it to the latest information. Most of the steps below are not necessary anymore since I now have a new thread here which lets you do these things easily with a special version of ClockworkMod (CWM) recovery for the HD and HDplus. And the text here has been modified to reflect that and include the HD.
Update 11/02/2013: Since B&N has included the gapps and Play Store in version 2.1.0 and above and since verygreen developed the new boot.img that removes B&N /system file protection scheme and I updated my HD/HD+ CWM thread to account for those changes, I decided to give this thread an update. I have added comments to the sections in italics below where necessary
If you have questions or comments on this post, reply to this thread. Please do not send me private messages or emails. By posting in the forums others get a chance to help you and if I answer your question in the forum, others can see my response and it may help them too.
1. Setting up ADB
ADB is very useful for many things but you do NOT need ADB to root anymore. Look at my thread referenced above to use CWM to root.
Also, rather than use ADB via USB, it is much easier to use a Wireless ADB app available in the Play Store.
If you want to know how to set up ADB with USB, click on the "show content" button below.
The first thing you need to do is get ADB working on your PC so that it can connect with the HD+. The instructions to do that is on B&N's own site here. (But you really don't have to do all that, see below). To make it easier for XDA users, I have attached to this post the drivers downloaded from B&N site. Download and unzip that file to your PC.
To install the drivers, do the following (I tested this on Windows XP and Windows 7):
1. On your HD+ go to settings, device information, developer options, and make sure check "Enable ADB" is not checked.
2. Plug in the device to the PC with the USB cable. MTP should install.
3. Unplug the device, go to settings again and check 'Enable ADB'. Plug back in.
4. New devices will try to install. When they do, work your way through the options until you get to the choice "include this location in search" (the terminology is a little different in Win7) and browse to the location you unzipped the driver files above. Continue and the driver should install. In Windows 7 just one device will pop up. On Windows XP, two may. (Edit: If you are having trouble with this step, go to the B&N link I have above and read and follow section 4.6 of that guide. You can skip section 4.6.2 since you unzipped those drivers earlier. But do all of the remaining steps in section 4.6).
5. An "Android Composite ADB Interface" will install. If the computer says it needs to reboot to finish. Do it.
6. If, when it starts back up, and after installing ADB below, it does not work, you may need to go the Device Manager and look to see if "Android Composite ADB Interface" device has a yellow exclamation point by it. If it does, update the driver with the B&N driver again.
7. Create a file named adb_usb.ini and put 0x2080 in it with no line feed or carriage return. Go to \documents and settings\ and open your users folder and create a folder named .android and put that file in it.
8. I have attached a file named adb.rar below. Just unrar the adb.rar file. There will be three files there that you can put in a directory (any name you want).
9. Open a command prompt and cd to wherever you copied those adb files. If you set your path to that directory, you can have the prompt set for any directory, like where your apks are stored. Type 'adb devices'. It should go through some commands ending with a list of devices connected. The serial number of your HD+ should be listed. You can now run ADB commands.
2. Sideloading Apps
Once Unknown Sources is activated by my CWM zip above, you do not really need to install apps this way anymore.
Once you have ADB connected to your HD/HD+, it is very easy to sideload install apps. Just have your command prompt set to the location that you have your apk's stored and type "adb install xxx.apk", where xxx.apk is the name of your app. It is best to name the apk to something simple with no underlines or special characters in the name. It does not matter what you name it, the real name is inside the apk. The app should install. I would start with a launcher app since sideloaded apps cannot be seen in the stock launcher. Then I would install AnyCut which I have attached to this post. This app allows you to put the Home command on your launcher's home screen so that after you make your launcher default, you can get back to the B&N home page. There is a trick mentioned in the B&N guide referenced above that lets the stock app drawer see your sideloaded apps. On the Apps screen, hold the volume up button while you press the "Apps" word at the top of the screen for 2-3 seconds. An "Extras" screen will pop up showing all of the sideloaded apps. You have to do this every time you want to see it.
3. Rooting the HD/HD+
Rooting is now very easy using CWM in the referenced thread above. If you want to use the older manual method, click on the "show content" button below. But be warned these older methods no longer work on version 2.0.5 or newer.
Verygreen came up with the original scheme to root the HD+. But it had a problem. The HD+ checks on boot to see if /system has changed, and if it has, it will not boot. It tries this 8 times and on the last time the "8 failed boot" procedure kicks in and your device is wiped clean (including your storage space) and the factory ROM is re-installed. He later modified it to survive a reboot. Someone0 developed another scheme where he can root without modifying /system directly. So the next time it boots, it boots normally. See his thread here.
ONCE YOU HAVE ROOT, DO NOTHING THAT MODIFIES /SYSTEM OR IT WILL NOT BOOT AND END UP RESETING ITSELF. Also do not install anything that installs to /system, like busybox, AdFree and a few other apps. Ignore this warning with Universal Root rev3 or higher.
4. Setting OTA (Over the Air) Updates from B&N to Manual
When you first register the HD/HD+ it will automatically update itself to the latest version. To protect yourself against further updates that might jeopardize your ability to root or add other mods, you should try to block further automatic updates. But it seems that making this mod is no longer effective, B&N updates anyway.
Again, I have a CWM zip that will do this for you in the referenced thread above. If you want to see how to do it manually, click on the "show content" button below.
EDIT: (2/22/13) I have a new way to block OTA that seems to work so far. Another user (thanks greenya!) discovered this and I have come up with a way to implement it. I use the app AdAway to put my own black list of sites to not allow access to. If you want to try this, you must be rooted. Get AdAway either on the 1mobile.com market or at its developer's site (http://code.google.com/p/ad-away/). Before you do anything go to its preferences and change the target hosts file to /data/data/hosts. That way it will not reset the device. Then go to "Your Lists". Add this site to the black list: su.barnesandnoble.com. Then go to the main menu and select "Download files and apply ad blocking". It will ask you if you want to add a symlink, say yes. (If you installed the new boot.img from verygreen or flashed my latest version of Universal Root (rev3 or higher), you do not need to worry about adaway resetting your device. Just install it normally.)
It does not seem to block any B&N shopping or downloading apps or books. I installed this on my 2.0.5 and purposely tried to update and it says it needs the update but pushing download does nothing. Then I unblocked it and pushed download and it started to download immediately. So it does work.
Basically the same method used on the Nook Color and Nook Tablet should work on the HD+. It requires that you edit a database file and that requires root access. I use the paid Speed Software's SQLite Editor. You need to use the latest version (2.0.1). I could not get my older version to get root access.
So here is a description on how to do it with SQLite Editor. Open the app and it should get granted superuser access. Then browse with it to /data/data/com.bn.devicemanager/databases. There should be a file there named "devicemanager.db". Open that with SQLite Editor. There should be a list down the left side, one being "registry". Click on that. A table opens up that looks like a spread sheet. On line 6 is com.bn.device.fota.mode. Scroll across till you see the value column. It should say auto. Edit that to manual. Save the database and you are done.
This worked on the other Nooks, so should work here. See the post below for another automatic method.
5. Setting Up Installing from Unknown Sources
I also have a CWM zip that will do this for you in the referenced thread above. If you want to see how to do it manually, click on the "show content" button below.
You can toggle the unknown sources using the same method as I used for blocking OTA. Just look for the database in /data/data/com.android.providers.settings/databases. The database is settings.db. Open secure and line 4 - install_non_market_apps and change the value to 1.
6. Setting up Google Play Store and Google Apps
I also have a CWM zip that will do this for you in the referenced thread above. If you want to see how to do it manually, click on the "show content" button below. If you have stock version 2.1.0 or higher you do not need to flash my zip. Play store is included in the ROM.
Someone0 has a post on how to add Google Play Store is here. And he now has it so you can install the entire Gapps package, including Play Store. Again, you must be rooted first.
7. Setting LCD Density
If you are like me, you hate the tiny fonts on these high resolution devices. You can change the default lcd density to help with that. The default lcd density for the HD/HD+ is 240. I changed it to 300 and everything works fine on the HD+ and fonts are a little larger. But you cannot modify build.prop on /system to do that. It will cause the device to reset itself since you are modifying /system. To get around that, create a file in /data named local.prop. Add the following line to that text file:
qemu.sf.lcd_density=300
Then reboot and your new density is set. You need to be rooted to do this on the device.
I found that changing the density on the HD made the SystemUI app crash. If you want larger fonts for the HD, I recommend you use the tip in the next section.
8. Larger System Fonts
If you don't want to set your LCD density higher but you still want larger fonts, a user (Windsor1959) just passed on this tip. Go to the B&N app store and install the free app Go Read. Once that is installed, open it and use the menu to go to accessibility settings. There is an option for larger system fonts. It works great. Thanks Windsor1959.
I also just discovered that there is another hidden setting that lets you set the system fonts from small, normal, large and huge. To get to these settings you need a third party launcher like zeam or adw and the AnyCut app I attached below. On the launcher screen long press and select shortcut. Select AnyCut from the list. Within AnyCut select activity and scroll down to fonts. Select that and a fonts shortcut will appear on the launcher screen. Open that and you can select the font size.
9. Data structures on the HD/HD+
For those of you used to having two separate partitions for data and media files, B&N has used a different scheme for the HD/HD+. They make one very large /data partition ranging from 5GB to 28GB depending on which device you have. Then they create a folder in /data (/data/media) and, using the sdcard fuse feature, link it permanently to /sdcard. So that means it is one big dynamic space for both /data and /sdcard, sharing the free space. /data is considered root and /sdcard is not.
They named it /sdcard because a lot of third party apps expect there to be an sdcard on the system and won't run unless there is one. That creates a little bit of a terminology problem for us Nook Color users. We are used to having /sdcard be an external SD. And on top of that, if we do add an external SD, it is mounted as /ext_sdcard under /mnt and that is hard for some apps to see. And when you connect your device to your PC with MTP, internal media (sdcard) is called 'internal memory' and the SD (ext_sdcard) is called 'SD card'. I think B&N did this with the expectation that users would not be rooted and be able to see that stuff under the hood.
Since sdcard is really just a part of /data, it is formatted as ext4 instead of FAT32 like the Nook Color media partition was. That means you can store a single file larger than 4GB, which is the limit for FAT32. Most external SD cards are formatted FAT32 so they are also limited to a single file size of 4GB. But it makes them directly readable by your Windows based PC. When you first put a new external SD in the HD/HD+, it asks you if you want to reformat it so you can more easily store your media files. If you say yes, it will format it to ExFAT, a new flash drive format that supports larger file sizes. That's good for your media files since you can have very large files on it. But it could be bad if you want to take the card out and put it in your Windows XP PC because XP cannot read it without an update patch from Microsoft. If you have Vista or higher, ExFAT can be read natively.
When you do a factory reset (clear /data) your media directory (/sdcard) is wiped out too.
Also, the B&N media, books, magazines, etc., are stored in /data/nookmedia, which is root.
10. White on White Text for Some Apps
One of the annoying issues with using some third party apps is the HD/HD+ displays some dialogue boxes with white text on a white background so that the text is unreadable. Someone0 and I developed a patch that can repair this. I have a zip in my CWM thread referenced above to repair the HD+ and HD. (Also since stock version 2.1.0, B&N has dramatically changed the color scheme so that the white-on-white issue is no longer the problem it used to be, I have discontinued providing white-on-white mods for version 2.1.0 and above.) If you want to see how to do it manually, click on the "show content" button below.
Someone0 and I have been working on this and have found a solution. It requires a modification to the framework-res.apk on /system. And the mod works very well. The problem is that the apk is on /system and must be symlinked using our symlink trick we use on /system files when we need to modify them. That is easy to do, but this particular apk is very critical to your system. If you do not get it installed properly, it will lock up the device and you either need to reset it completely or repair with ADB.
If you are tech savvy enough you could modify your own apk and install it. In the colors.xml file in the values section of the de-compiled apk, are two settings that need to be changed, "background_light" and "background_holo_light" need to be changed to "ffcfcfcf". The color choice was a compromise between making the text dark enough to be seen against a white background and bright enough to make things like menus show in the grey backgrounds. Re-compile and put the apk in /data, delete the apk in /system and symlink to the one in /data. The problem with doing it manually while running is as soon as you delete the apk, things go bonkers. And you cannot add the new symlink until the original apk is deleted. If you start messing with this mod, be sure to have ADB enabled so if it locks up and gets stuck on booting, you can access things with ADB and hopefully repair it. When I did my system manually, I copied the modded apk to /data with root explorer, used root explorer to set /system to read/write, then used ADB to delete the apk in /system and create the symlink. If you mess up, it will boot, but get stuck at the 99% level. Hopefully if you left ADB enabled, you can use ADB to repair whatever is wrong.
11. Implementing Userinit.d
Userinit.d can be used to run specialized scripts as part of the boot process. The HD/HD+ does not implement userinit.d, but it can be modified to allow it. And these scripts can be used to customize the performance of the device, like modify fonts, change colors, add symbolic links, modify drives, set CPU speeds and tweaks, etc.
I have implemented userinit.d in the new Universal Root zip in my referenced CWM thread above. (The latest version no longer uses it).
The scripts are usually named with numbers at the beginning and no extension. Examples would be the scripts from CM7 init.d which are: 00banner, 01sysctl, 03firstboot, 05mountsd and others. They are executed in the order of the numbers. They are plain text files that have as the first line:
#!/system/bin/sh
Then they have script commands in text format.
The beauty of these scripts on the HD/HD+ is you put them in /data instead of /system which would reset your device. Put the script files in a new folder named /data/local/userinit.d. Set the script file permissions to execute.
There are examples of userinit.d scripts out there if you search for init.d scripts on XDA or the web. Some will work on the HD/HD+ and some won't. I have a great example in the next section.
12. Swapping "sdcard" and "ext_sdcard"
I now also have this modification as a flashable zip in my CWM thread linked above. No need for root with that one.
As explained in section 9 above, the internal media is named "sdcard" so that apps can store their files there. Some users would like them stored on their external SD. I have a userinit script that will swap "sdcard" and "ext_sdcard" so that apps will store their files on the external SD. The external SD will show as "sdcard" and the internal media will show as "ext_sdcard". And it shows swapped using MTP also. It can be a little confusing since we cannot control the names, but they are swapped. If you don't have an external SD plugged in, both sdcard and ext_sdcard will show the internal media.
To swap the drives, make sure userint.d is implemented, then download the attached file, 11SDswap.rar, and extract it and put the file in /data/local/userinit.d. Set the permissions of the file to execute in all three boxes. On the next reboot, they will be swapped. To return to normal, just remove the file and reboot.
13. Skipping OOBE (Out of Box Experience)
Skipping OOBE is when you want to skip the registration step when you first start your device or after a reset. Not registering means that you will not be able to buy books or apps from B&N or, if you already have an account, have access to already purchased items. Your name will show as TEST (which can't be changed). And, if you set up wifi, the device will still check for updates and if found, update.
So if you don't want to register, or that device is already registered to someone else and you can't, just skip OOBE. There are instructions for the Nook Color here. They still work for the HD/HD+.
14. Back Up Your Stock ROM Installation with CWM v6.0.2.8 for Nook HDplus and v6.0.2.7 for the HD
Now you can backup your stock installation with my bootable CWM (ClockworkMod) recovery SDs. That way you can restore if you make a mistake and change /system so the device starts to reset itself. Just catch it before the reset completes, insert the card and restore and you will be back to OK.
You can do anything with these CWM SDs you normally would do with CWM, (nandroid backup, wipe system, data, cache, dalvik-cache, fix permissions, etc).
One of the nice features is you can wipe /data without it wiping your internal media at /data/media. So, if you want to reset, just wipe /data and your media files are still left intact. And when you do a nandroid backup, it can be placed either on internal media or your external card. The nandroid backup feature backs up /boot, /system, /cache and /data (without the media folder). So if you want the media folder backed up you must do it manually from within stock. And when you restore, you can selectively restore any partition. So if you mess up /system by putting something there that causes a reset, just selectively restore /system.
EDIT (5/22/13) - There is a new procedure brought to my attention by another user (thanks fanoush) which lets you make the CWM SD without burning the image. It seems the OMAP4 devices are a little more liberal on the booting requirements than previous OMAP devices. This makes it easier to install on any size SD. Go to my HD/HD+ CWM thread linked in my signature and look at item 1a. There are instructions and files there.
The versions attached below are under 120 MB so they can be put on any size SD. It burns very quickly. But there is no room there for any backups. After burning the SD you can use partitioning software (like Mini-Tool Partition Wizard or EaseUS Partition Manager, both free) to expand it to the full size of your SD card if you want so there would be plenty of room for backups. But be sure to only expand the back end of the partition, being careful not to touch the beginning.
I also now have a 4GB versions for both the HD and HDplus attached to the CWM thread referenced above.
To make the SD, download the version for your device and extract the file. It should be a 120MB .img file. Burn (write) that image file to your SD card using Win32diskimager in Windows. In Linux or OSX (Mac) use the "dd" command.
To use Win32DiskImager, find it on the web (here, it's free) and install it on your Windows PC. Open it (be sure to run it as administrator) and select the drive (device) that has your card reader with your SD inserted. Then in the image file box put the location where you have the extracted img file. Then when everything is set right, click on the write button. A warning will pop up asking if you want to proceed. When you have verified that you are going to write to the correct device, click on Yes. (One user overwrote their external USB hard drive by not verifying first). With the small version it should burn fairly rapidly. If you get an error message about access denied, it means you are looking at the drive with Windows Explorer. Close Windows Explorer and try again. In fact, it is a good idea to close all unnecessary windows when burning, even your browser.
Insert the SD into your powered off Nook HD/HD+ and power on. It should boot to CWM with the label v6.0.2.8 for HD+ stock. The HD version just says v6.0.2.7 for Stock. You can tell it is booting properly if the cyanoboot logo shows up after the Nook logo shows for a few seconds. If the Nook logo stays there and starts changing, it means it is booting to stock. Hard power off by holding the power button for several seconds. Try again.
Manipulate the controls with volume up/down for cursor, n key to activate and power key for back.
15. Modifying System Files on the HD/HD+
Ordinarily you cannot modify system files on these devices because they will detect the change and reset themselves back to factory stock, wiping out all your data at the same time. But there is a safe way to do it if you are rooted.
If you have installed my new Universal Root rev3 or higher or installed verygreen's boot.img, the below procedure is no longer necessary, just modify the files directly.
The HD/HD+ has a manifest file included in the boot files that has a listing of each file that is supposed to be in /system and a checksum of each file. On boot, it reads the files in /system and makes sure each file that is there is on the list and matches the checksum. It ignores directories, symlinks and missing files. If one is added or has the wrong checksum, it stops and tries to boot again. If it reboots 8 times in a row without completing the boot, the automatic reset feature kicks in and your device is formatted and the factory ROM is reinstalled.
So you can see that missing files are OK and symlinks are OK. So if you want to modify a system file, first copy it to /data somewhere, delete the original, and make a symlink in /system to replace the deleted file. The symlink points to the file copied to /data. But be careful, some files, like framework-res.apk, are being used all the time and if you delete it, even temporarily, the system goes crazy.
The scheme that someone0 and I use is to mimic /system under /data/su so that the structures are the same to avoid confusion. For example, if you wanted to modify build.prop, it would be copied to /data/su/system/build.prop and the symlink would point there. Since build.prop is not used very often, it is safe to now modify it however you want. But be careful, some settings there are vital, like hardware rotation. Mess with that and things will go all wonky on the next reboot.
Here are the specific commands to make this happen using build.prop as an example:
1. Use your root file manager to copy /system/build.prop to /data/su/system/build.prop. Set the file's permissions to match the original.
2. Delete /system/build.prop also using your root file manager
3. Set up Terminal Emulator. Start the program and type su enter. After you allow superuser access, the prompt turns to #
4. Type the following command at the # prompt (without the quotes):
"mount -o remount,rw /system"
5. Then this command:
"ln -s /data/su/system/build.prop /system/build.prop"
(That first letter is a lower case L)
6. Then this command:
"mount -o remount,ro /system"
You are done. You can now modify build.prop in /data any way you want and the system will not reset.
But before you do this mod or any other system file mod, I recommend you have backed up your system using CWM as described in the previous section. That way if you did not get it right somehow and it starts to reset, you can insert your CWM card to stop the rebooting and selectively restore /system and try again.
One side benefit of doing this build.prop mod is if B&N tries to update you in the future, it will fail because it cannot verify your build.prop because it is missing. And, in my experience, it does not try again.
16. Nook HD/HD+ internal partition structure and backups
The partition structure for the HD/HD+ is the same and is as follows:
Code:
P# Name Size Type
1 xloader 128K Fastboot Image
2 bootloader 256K Fastboot Image
3 recovery 15MB Fastboot Image
4 boot 16MB Fastboot Image
5 rom 48MB vfat
6 bootdata 48MB vfat
7 factory 448MB ext4
8 system 672MB ext4
9 cache 464MB ext4
10 data varies ext4
There is a simple process to make image backups of your internal partitions. Most people will never have to use the backups, but there is one critical partition that holds vital device specific information that was created at manufacture that is probably wise for you to back up. The process requires that you have either Terminal Emulator installed or ADB set up. And it can be done either in rooted stock or CM10/CM10.1. In Terminal Emulator or ADB Shell in superuser mode, type the following command:
dd if=/dev/block/mmcblk0p7 of=/mnt/sdcard/factory.img
This will make an image of your partition 7 that has that vital information. It also has a copy of the factory.zip file used to reset your device should you need to. If you want to back up the rest of your partitions, just change the p# and file name in the above commands to match the listing above. Partition 10 is quite large so should not be backed up using this method.
To restore a partition, just reverse the information following the if= and of= statements in the command. The information stored in partitions 1, 2, 3, 4, and 8 is specific to the ROM version you were running when you made the backup, so restoring them to another version is probably not a good idea (and if you do, restore all 5 of them together). Only do it if it is a last resort. And of course you should not restore HD partitions to the HD+ and vice versa.
Enable Unknown Sources and Blocking Auto OTA made easy (updated 12/3)
Instead of making a new thread, I have decide to make the tips that already available, but hard to use and make it simple.
So, what is it? This little thing will set Enable install from Unknown Sources and change the auto update to manual update for Nook HD ROM. I keep hearing how people are saying they have hard time making these changes so, I make it pretty dead simple. It's as simple as I can make. If you are looking at the timeline, root first, then this, and then gapps after. I now make them all so simple that it take me like 15mins to do all those 3 things from scratch. Originally I grab the sqlite3 from one of the app, which I guess I shouldn't have. Now I replace it w/ the one from CM9, which I guess is okay. And smaller size too.
If you were using verygreen version of root, try running this first.
Code:
adb shell su -c "/data/su/busybox chown shell.shell /data/su"
Pre-Requisite:
ADB and root.
NEW Instruction:
download the settings_new.zip in the attachment and save it somewhere.
unzip it.
run install.bat (for windows)
OLD Instructions:
download the settings_old.zip in the attachment and save it somewhere.
unzip it.
run install.bat (it basically just upload settings.sh and sqlite3 and change their permission, if you are on linux just do that instead)
adb shell
su
/data/su/settings.sh
*** OLD TEXT ***
While it's true that we should put heavy emphasis on not touching /system and that is not just manual works, but also any app with root access. You could be installing something like busybox via goole play store and screw everything up. That said, we are not touching /system at the moment because we lack the knowledge of that the nook is doing during boot process. I have been able to get asomething like AdAway to work which actually creating a sym link from /system/etc/hosts to /data/data/hosts file. I been doing this under the assumption that mounting and sym link are ok in the /system. But I would be worried too if there is a lot of those.
Click to expand...
Click to collapse
Lost and Confused
I tried following the instructions on the B&N’s website, but I do not see ‘Android Composite ADB Interface’ or even ‘Android Phone’ within the Device Manager of Windows. I now have ‘BNTV600’ and ‘NOOK’ under Device Manager/Portable Devices. I think this is for the big leagues and I may mess something up. Probably going to wait until there is a YouTube video guide showing step by step on how to successfully root the Nook HD+.
Many thanks to ‘leapinlar’ for the help.
cybersonic_ca said:
I tried following the instructions on the B&N’s website, but I do not see ‘Android Composite ADB Interface’ or even ‘Android Phone’ within the Device Manager of Windows. I now have ‘BNTV600’ and ‘NOOK’ under Device Manager/Portable Devices. I think this is for the big leagues and I may mess something up. Probably going to wait until there is a YouTube video guide showing step by step on how to successfully root the Nook HD+.
Many thanks to ‘leapinlar’ for the help.
Click to expand...
Click to collapse
If you read my description above, it says to update the driver for BNTV600.
No longer able to access internal & external memory on the Nook
leapinlar said:
If you read my description above, it says to update the driver for BNTV600.
Click to expand...
Click to collapse
This is what I did:
1. Plugged my Nook HD+ to my computer (ADB enabled)
2. Device Manager / BNTV600 / Update Driver Software / Browse my computer for driver software / Usb_driver_r04-windows folder / OK
3. Clicked on ‘Let me pick from a list of device drivers on my computer’
4. MTP USB Device appeared so I clicked on ‘Have Disk’
5. Browsed ‘android_winsub’ and clicked Open and OK
6. Android Composite ADB Interface appeared so I clicked ‘Next’
7. Message, ‘Windows can’t verify the publisher of this driver software’
8. Install this driver software anyway
9. Rebooted my computer
10. When the Nook is connected to the computer (ADB not enabled)
a. The Nook shows up as a G: drive and ‘MyNOOK Setup’ is the only file in it
b. Clicking on the ‘MyNOOK Setup’ brings me to a message:
• Welcome to MyNOOK Setup.
• MyNOOK Setup is a one-time installation that will allow you to tranfer your personal files to your NOOK.
• Transferable files include, but are not limited to: photos, music, videos, EPUB, PDF and Microsoft Office files.
• Note: Copyright protected files are not transferable
• To install, go to .... can't post link since im a noob
• For more information, visit ..... can't post link since im a noob
c. MyNOOKSetup.dmg appears when I click on the first link
11. When the Nook is connected to the computer (ADB enabled)
a. AutoPlay ‘BNTV600’ constantly appears.
12. I cannot access the internal or external memory on the Nook for both #10 & #11,
13. Running ‘makeroot.bat’ in the cmd for both #10 & #11 does not work either.
14. Device Manager / NOOK (BNTV600 no longer exist)
Follow my instructions to install the drivers and use my driver file from my first post. Go to device manager and delete any those three drivers you installed earlier, composite, mtp, etc. Then just do the bntv600.
Sent from my Nook HD+ using Tapatalk
Cool but....
...I am having a slight problem. I can not download your attached file usb_driver_r04-windows-Modded-for-HD.zip :/ everytime I do my computer which is running windows xp is telling me there is nothing there. Can you please help me thank you
Possible driver conflict with Samsung Galaxy Tab 7 Plus
leapinlar said:
Follow my instructions to install the drivers and use my driver file from my first post. Go to device manager and delete any those three drivers you installed earlier, composite, mtp, etc. Then just do the bntv600.
Sent from my Nook HD+ using Tapatalk
Click to expand...
Click to collapse
I followed your instructions and I successfully installed the driver you provided in your zip but the following actions occur after computer reboots.
When ADB is disabled
• NOOK (G Drive appears in My Computer
When ADB is enabled
• NO NOOK (G Drive in My Computer
• BNTV600 AutoPlay windows constantly pops up
I forgot to say that I have a Samsung Galaxy Tab 7 Plus installed in this computer. The following items are what I see in Device Manager:
• Portable Devices / NOOK
• SAMSUNG Android Phone / Android Composite ADB Interface
I tried deleting all the drivers and repeat your instructions but the SAMSUNG Android Phone / Android Composite ADB Interface keeps appearing.
Dopey32 said:
...I am having a slight problem. I can not download your attached file usb_driver_r04-windows-Modded-for-HD.zip :/ everytime I do my computer which is running windows xp is telling me there is nothing there. Can you please help me thank you
Click to expand...
Click to collapse
I don't know what to tell you. I just tried again with windows XP and it downloaded fine. Just keep trying. And watch where windows puts it.
cybersonic_ca said:
I followed your instructions and I successfully installed the driver you provided in your zip but the following actions occur after computer reboots.
When ADB is disabled
•NOOK (G Drive appears in My Computer
When ADB is enabled
•NO NOOK (G Drive in My Computer
•BNTV600 AutoPlay windows constantly pops up
Click to expand...
Click to collapse
I experienced a lot of the same symptoms.
The Nook G: is for Mac users that do not have MTP. It is so they can get the drivers they need. Notice the .dmsg (sp ?) is for them. That will only go away when you get MTP working or switch to enabled adb.
I was most concerned with getting the adb interface working, so I just ignored the MTP issues until later. In fact I temporarily disabled it so it would not keep popping up during adb.
After I got everything sideloaded and rooted, I tackled the MTP issue. With adb unchecked, I went to USB devices and uninstalled the USB mass storage device (which was the Nook G). Then it recognized MTP.
Sent from my Nook HD+ using Tapatalk
I think it's safe to say that what we(me and other who got all the stuff out seperately) did so far aren't anything very dangerous. We havn't touch any other partition or boot loader. Unless you mess them up yourself since now you have root, then the worst it could happen is a full factory reset or you can force yourself to factory reset it.
okay got a little farther
I have installed the drivers and my nook is having the same symptoms as cybersonic_ca. Now I am trying to figure out how to utilize the command prompt, i type in adb devices and it responds with 'adb' is not recognized as an internal or external command, operable program or batch file.
please help, i am trying to root my nook and HD+ but i feel i must be forgetting something. I am sorry if i am very bothersome but i can not figure out what is going on
All these tips also help with the HD. Thanks so much!
Sent from my Nook HD using xda premium
Dopey32 said:
I have installed the drivers and my nook is having the same symptoms as cybersonic_ca. Now I am trying to figure out how to utilize the command prompt, i type in adb devices and it responds with 'adb' is not recognized as an internal or external command, operable program or batch file.
please help, i am trying to root my nook and HD+ but i feel i must be forgetting something. I am sorry if i am very bothersome but i can not figure out what is going on
Click to expand...
Click to collapse
Then you have either not installed the Android SDK (Software Development Kit) on your PC (which includes adb) per the B&N instructions or your path variable is not set to include where you installed it.
Sent from my Nook HD+ using Tapatalk
Dopey32 said:
I have installed the drivers and my nook is having the same symptoms as cybersonic_ca. Now I am trying to figure out how to utilize the command prompt, i type in adb devices and it responds with 'adb' is not recognized as an internal or external command, operable program or batch file.
please help, i am trying to root my nook and HD+ but i feel i must be forgetting something. I am sorry if i am very bothersome but i can not figure out what is going on
Click to expand...
Click to collapse
if you can't follow or understand the instructions about adding the path to adb in the environment path you can always just cd "/to the directory adb is installed/" and run adb directly from there. easy way is to just drag the folder into the command prompt window. it'll save a bit of typing - only works if you're not running cmd as admin.
You said you modded the drivers from B&N? What did you change? Just curious...
So, instead of making another thread, since this is a tips thread, I'll just post it here.
Just in case you are not familiar with a factory reset on the Nook HD+, there are two kind of factory resets. The one that you perform yourself, which is actually not a full factory reset and the one that Nook get pissed and do the full one.
A factory reset that you perform yourself, whether from the GUI or button combination will basically clean the partition /data while a full blown one will basically restore other partition such as /system.
Why do I bring this up, because as we know, we are not perfect. I make mistake and so do other. Sometime instead of trying to re-trace the step and fix our mistake, it's easier to just reset everything. Well, since we can't just do a full blown factory reset our self, at least not very easy, we can at least force the Nook to do it for us.
So, if you felt like I did something wrong, and I don't know which step to take next, I make a little tool for you to start over. You can see the attachment, reset.zip in there, there are 3 files. You only have to run reset.bat if you need a linux version, maybe you can beg the OP to do it for you. If you exam the package, you can see that this is very similar to the original root method which force itself to factory reset, so this is basically a modified version of that. Obviously you still required ADB. Well, on the other hand, if you never get ADB working in the first place, you probably can't mess up that bad that you need this tool in the first place.
Let me make it clear, this tool WILL RESET EVERYTHING. It also REBOOT MANY TIMES. And expect the whole process to take about 10 minutes.
dbh369 said:
You said you modded the drivers from B&N? What did you change? Just curious...
Click to expand...
Click to collapse
I actually modified a generic driver by putting the Nook HD+ device id in it. I was not able to download the B&N driver so I don't know if it needed modifying or not.
Sent from my Nook HD+ using Tapatalk
cybersonic_ca said:
I followed your instructions and I successfully installed the driver you provided in your zip but the following actions occur after computer reboots.
When ADB is disabled
• NOOK (G Drive appears in My Computer
When ADB is enabled
• NO NOOK (G Drive in My Computer
• BNTV600 AutoPlay windows constantly pops up
I forgot to say that I have a Samsung Galaxy Tab 7 Plus installed in this computer. The following items are what I see in Device Manager:
• Portable Devices / NOOK
• SAMSUNG Android Phone / Android Composite ADB Interface
I tried deleting all the drivers and repeat your instructions but the SAMSUNG Android Phone / Android Composite ADB Interface keeps appearing.
Click to expand...
Click to collapse
I am having the same problem as Cybersonc_ca. I did everything according to the nook developer website and when I enable ADB on my nook hd+, it does not show my BNTV600 under portable devices but I DO have Android Phone >> Android Composite ADB Interface.
If I go to command prompt, how can I make it so that it checks that folder as well?
I apologize for such noob questions. Thank you.
sayw0rd said:
I am having the same problem as Cybersonc_ca. I did everything according to the nook developer website and when I enable ADB on my nook hd+, it does not show my BNTV600 under portable devices but I DO have Android Phone >> Android Composite ADB Interface.
If I go to command prompt, how can I make it so that it checks that folder as well?
I apologize for such noob questions. Thank you.
Click to expand...
Click to collapse
Go to command prompt and type 'adb devices' and see if you have any. And the looking for bntv600 was for getting the composite to show. You have that.
Sent from my Nook HD+ using Tapatalk
Hi.
I have a Nexus 4 running stock Android 4.2.2. The bootloader is unlocked and it's rooted using TWRP to install Super SU.
Just recently I decided I didn't like the soft keys (navigation bar) and researched how to remove it (just it, not the notification bar). The simplest solution I found was to use ROM Toolkit Lite to add "qemu.hw.mainkeys=1" to build.prop, and rebooting.
Eventually I found too many problems with removing the soft keys and wanted them back so today I went back in to ROM Toolkit to remove that line. The problem was that I couldn't figure out how to do this. ROM Toolkit lets you add lines to build.prop by tapping "new entry" which brings up a box that had "property name" and "property value" like this:
When I went to remove the entry, I couldn't work out how to delete it (I now know you tap menu>edit and it comes up as a text file). What I ended up doing was just removing the property name and changing property value to 0. That meant that build.prop had "=0" at the end. When I rebooted, it just sits endlessly showing the Nexus logo.
My question is how do I restore build.prop? Factory resetting doesn't work because it doesn't change the Android system files. I actually have a backup of build.prop made by ROM Toolkit but how do I overwrite the broken one? All I can do is use recovery mode (TWRP).
Is there a flashable zip with the default build.prop?
Can I make my own flashable zip from the backup of build.prop?
How do I put files onto my Nexus using recovery?
I have no system backup.
Thanks,
Lachlan
Restore your Nandroid.
Edit: just saw that you said you didn't make one. Lesson learned, I guess. You can adb sideload files from within recovery. Do this, sideload a stock rom, flash it, and it will give you a normal build.prop.
Sent from my iPad 4
Use adb to push the backup build.prop and overwrite the current one.
I'm assuming that u have the backup on your PC? If not, then download the stock ROM and extract the build.prop from /system.
Use the following command to push it:
Code:
adb push /path/to/build.prop \system
Sent from my HTC Desire using xda app-developers app
megaman1574 said:
Hi.
I have a Nexus 4 running stock Android 4.2.2. The bootloader is unlocked and it's rooted using TWRP to install Super SU.
Just recently I decided I didn't like the soft keys (navigation bar) and researched how to remove it (just it, not the notification bar). The simplest solution I found was to use ROM Toolkit Lite to add "qemu.hw.mainkeys=1" to build.prop, and rebooting.
Eventually I found too many problems with removing the soft keys and wanted them back so today I went back in to ROM Toolkit to remove that line. The problem was that I couldn't figure out how to do this. ROM Toolkit lets you add lines to build.prop by tapping "new entry" which brings up a box that had "property name" and "property value" like this:
When I went to remove the entry, I couldn't work out how to delete it (I now know you tap menu>edit and it comes up as a text file). What I ended up doing was just removing the property name and changing property value to 0. That meant that build.prop had "=0" at the end. When I rebooted, it just sits endlessly showing the Nexus logo.
My question is how do I restore build.prop? Factory resetting doesn't work because it doesn't change the Android system files. I actually have a backup of build.prop made by ROM Toolkit but how do I overwrite the broken one? All I can do is use recovery mode (TWRP).
Is there a flashable zip with the default build.prop?
Can I make my own flashable zip from the backup of build.prop?
How do I put files onto my Nexus using recovery?
I have no system backup.
Thanks,
Lachlan
Click to expand...
Click to collapse
If it's stock android, you could actually just wipe /system , then using adb in recovery you can push up a zip of the stock 4.2.2 isntall, and just flash that.
If build.prop is all you changed in /system then that should be fine to do, which will be especially easy if you can just grab a pre-rooted flashable zip of 4.2.2 stock.
megaman1574 said:
Hi.
I have a Nexus 4 running stock Android 4.2.2. The bootloader is unlocked and it's rooted using TWRP to install Super SU.
Just recently I decided I didn't like the soft keys (navigation bar) and researched how to remove it (just it, not the notification bar). The simplest solution I found was to use ROM Toolkit Lite to add "qemu.hw.mainkeys=1" to build.prop, and rebooting.
Eventually I found too many problems with removing the soft keys and wanted them back so today I went back in to ROM Toolkit to remove that line. The problem was that I couldn't figure out how to do this. ROM Toolkit lets you add lines to build.prop by tapping "new entry" which brings up a box that had "property name" and "property value" like this:
When I went to remove the entry, I couldn't work out how to delete it (I now know you tap menu>edit and it comes up as a text file). What I ended up doing was just removing the property name and changing property value to 0. That meant that build.prop had "=0" at the end. When I rebooted, it just sits endlessly showing the Nexus logo.
My question is how do I restore build.prop? Factory resetting doesn't work because it doesn't change the Android system files. I actually have a backup of build.prop made by ROM Toolkit but how do I overwrite the broken one? All I can do is use recovery mode (TWRP).
Is there a flashable zip with the default build.prop?
Can I make my own flashable zip from the backup of build.prop?
How do I put files onto my Nexus using recovery?
I have no system backup.
Thanks,
Lachlan
Click to expand...
Click to collapse
Ok, I can pull the backup of build.prop from my phone using adb and I found how to make a flashable zip, pushed it back and flashed it but still no boot up. I don't understand, I've replaced the offending file, why does it still not work?
megaman1574 said:
Ok, I can pull the backup of build.prop from my phone using adb and I found how to make a flashable zip, pushed it back and flashed it but still no boot up. I don't understand, I've replaced the offending file, why does it still not work?
Click to expand...
Click to collapse
Could be permissions or a number of other things, If you can I would run adb logcat while plugged in, assuming it even gets past the point of starting the adb daemon.
The alternative if you didn't mess with much more than the build.prop (like install system apps), is to simply wipe /system and flash on the stock rom (or pre-rooted version of it).
kbeezie said:
Could be permissions or a number of other things, If you can I would run adb logcat while plugged in, assuming it even gets past the point of starting the adb daemon.
The alternative if you didn't mess with much more than the build.prop (like install system apps), is to simply wipe /system and flash on the stock rom (or pre-rooted version of it).
Click to expand...
Click to collapse
Where should I look to get a stock rom?
megaman1574 said:
Where should I look to get a stock rom?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2147281
[ROM][OTA][mako]Android 4.2.2 JDQ39: Rooted Busybox Deodexed/Odexed (2/13/13)
Sent from my iPad 4
mitchdickson said:
just saw that you said you didn't make one. Lesson learned, I guess.
Click to expand...
Click to collapse
Yes, definitely. I can't remember why I didn't make a backup...
mitchdickson said:
http://forum.xda-developers.com/showthread.php?t=2147281
[ROM][OTA][mako]Android 4.2.2 JDQ39: Rooted Busybox Deodexed/Odexed (2/13/13)
Sent from my iPad 4
Click to expand...
Click to collapse
Ok, if I can't fix it by tonight I'll download this and flash it (My download limit during the day is too small to download it. That's why I'm trying to fix it without doing that)
kbeezie said:
Could be permissions or a number of other things, If you can I would run adb logcat while plugged in, assuming it even gets past the point of starting the adb daemon.
The alternative if you didn't mess with much more than the build.prop (like install system apps), is to simply wipe /system and flash on the stock rom (or pre-rooted version of it).
Click to expand...
Click to collapse
I'm not that good with Android, how and when do use this "logcat"?
megaman1574 said:
I'm not that good with Android, how and when do use this "logcat"?
Click to expand...
Click to collapse
adb should be second nature to anyone who has rooted/unlocked their phone or flashed custom roms. (But I'm guessing you just used a toolkit).
ie: phone plugged in while it's booting, you'd type
adb logcat
and if adbd is launched on the phone you'll see the logs as they are produced which might offer some clues as to where it's failing.
kbeezie said:
adb should be second nature to anyone who has rooted/unlocked their phone or flashed custom roms. (But I'm guessing you just used a toolkit).
ie: phone plugged in while it's booting, you'd type
adb logcat
and if adbd is launched on the phone you'll see the logs as they are produced which might offer some clues as to where it's failing.
Click to expand...
Click to collapse
I actually rooted it manually because A: The toolkit I had didn't work, and B: It's more fun. But I had never used the logcat command. I figured out how to call the command but it kept saying "file not found" or something because I didn't think to have it booting. I'm trying that now. Ok, it says
C:\Users\Lachlan>adb logcat
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
- waiting for device -
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
- waiting for device -
adb server is out of date. killing...
* daemon started successfully *
And then sits there with a flashing cursor after the last line.
megaman1574 said:
I actually rooted it manually because A: The toolkit I had didn't work, and B: It's more fun. But I had never used the logcat command. I figured out how to call the command but it kept saying "file not found" or something because I didn't think to have it booting. I'm trying that now. Ok, it says
C:\Users\Lachlan>adb logcat
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
- waiting for device -
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
- waiting for device -
adb server is out of date. killing...
* daemon started successfully *
And then sits there with a flashing cursor after the last line.
Click to expand...
Click to collapse
It tells you what the problem is right here:
adb server is out of date. killing...
adb is out of date, update it. (on OSX or Linux you would just run android update adb, I assume the same probably works on windows for the SDK).
kbeezie said:
It tells you what the problem is right here:
adb server is out of date. killing...
adb is out of date, update it. (on OSX or Linux you would just run android update adb, I assume the same probably works on windows for the SDK).
Click to expand...
Click to collapse
My adb version is 1.0.31. As far as I know that is the latest version. I don't actually have the Android SDK because I had trouble installing it. I installed adb separately. Plus, with all the other commands it says it's out of date but then works anyway.
megaman1574 said:
My adb version is 1.0.31. As far as I know that is the latest version. I don't actually have the Android SDK because I had trouble installing it. I installed adb separately. Plus, with all the other commands it says it's out of date but then works anyway.
Click to expand...
Click to collapse
Weird, but far as the SDK goes, all I did was unpack the SDK onto my desktop. And just hit up the platform-tools folder, type the command android , to bring up the java app so I can choose what I want installed (updating can be done without the GUI by doing android update sdk --no-ui , or can remove the last part if you want to see the window).
So to me it wasn't much different on windows as it was on my mac (just easier to add adb/fastboot to my path variable in OSX).
PS: You're correct, the latest version does appear to be 1.0.31
kbeezie said:
Weird, but far as the SDK goes, all I did was unpack the SDK onto my desktop. And just hit up the platform-tools folder, type the command android , to bring up the java app so I can choose what I want installed (updating can be done without the GUI by doing android update sdk --no-ui , or can remove the last part if you want to see the window).
So to me it wasn't much different on windows as it was on my mac (just easier to add adb/fastboot to my path variable in OSX).
PS: You're correct, the latest version does appear to be 1.0.31
Click to expand...
Click to collapse
Ok, after much fiddling I still can't make it boot so I'll have to download the stock rom tonight. Should I get odexed or deodexed? Will I be able to restore my data backup after flashing the rom? And will OTA updates work after flashing?
megaman1574 said:
Ok, after much fiddling I still can't make it boot so I'll have to download the stock rom tonight. Should I get odexed or deodexed? Will I be able to restore my data backup after flashing the rom? And will OTA updates work after flashing?
Click to expand...
Click to collapse
I haven't done it myself, but I don't think the OTA update will work if you have a custom recovery (and if the OTA update does go thru, it can possibly unroot your install). odexed is usually the original state.
Odexed are optimized (can be faster to load etc), where as deodexed are easier to modify/theme (most are originally odex'd as they're not intended to be modified later).
If you were already on stock, and you flash a stock rom (with just rooted being the difference) then the data you already have in /data should work. You can basically wipe /system but not /data and just flash the rom and boot up. (just be sure to make a backup of the data first if you can).
Ok... I had managed to move the backup of build.prop into system using TWRP's file manager but after THAT it wouldn't even show the Nexus logo. Hence the reason I said nothing about this (I thought it to be a dead end). Just as I was about to give up, I was reading an obscure post on Androidforums.com and came across a post telling the guy to pull build.prop, edit it, push it back, and chmod it to 644. I haven't the FAINTEST clue what the hell that is, but I remembered that "chmod" and "chmod 755" were two options when you tap on a file in TWRP's file manager. So I raced back in there, deleted the broken build.prop, moved the backup into system, tapped on it and pressed "chmod 755" rebooted and it worked! Anyone have any idea what is was that I did? What is chmod? But basically:
I FIXED IT YAY!!!
Thanks everyone for your help. I've been desperate to fix it, in fact, when I broke it was an hour before I had to leave for a weekend trip, so I had no phone.
kbeezie said:
I haven't done it myself, but I don't think the OTA update will work if you have a custom recovery (and if the OTA update does go thru, it can possibly unroot your install). odexed is usually the original state.
Odexed are optimized (can be faster to load etc), where as deodexed are easier to modify/theme (most are originally odex'd as they're not intended to be modified later).
If you were already on stock, and you flash a stock rom (with just rooted being the difference) then the data you already have in /data should work. You can basically wipe /system but not /data and just flash the rom and boot up. (just be sure to make a backup of the data first if you can).
Click to expand...
Click to collapse
My Nexus 7 is rooted with TWRP and it received an OTA update. But anyway, if you refer to my last post I fixed it.
Edit: However, it did unroot it. (not hard to reroot though)
I know I shouldn't have done this. But somehow I managed to "cut" the system fonts instead of copying them. And when I realized it, I tried to put the fonts back. but everything messed up and fonts started disappearing from every app. So I restarted the phone and boom. Stuck at Samsung boot animation.
Now, I've searched for this issue and now know that I've to replace system fonts with a genuine one for my device. So do I need to replace just the Roboto-regular.ttf or every font that was present in /system/fonts?
Secondly, I'm rooted and have Philz recovery installed. But I'm not able to use adb when phone is booting in normal mode. It says device unauthorized (I believe we need to authorize a pc for the first time).
Again, I can't push files using adb in recovery to /system/fonts because su right is not available. It says access denied.
And the data is important. So any method except RESET would be welcome.
Ok, I got it working partially. I'm able to push files to system partition. I pushed roboto regular ttf file. The phone boots now but systemui keeps on crashing. So can someone just provide me the stock fonts folder dump? I will try to push every font to see if the crashes still occur or not.
Edit: Finally solved it. What I was missing was the permissions. I was just pushing the font file but never bothered to think about permissions. So it could help someone in future. Push the font file to /system/fonts and change the permission to rw-r--r-- . I used aroma file manager for this purpose in philz recovery. I think you can also change the permission using adb.