Database Info

Post Root Thread

I'm going to start compiling a list of instructions all in one place for our new rooters out there who have questions. After surfing through tons of forum posts on the bamf roms and questions in Q&A there are a lot of people who still don't know how to necessarily wipe there devices correctly, install radios, the difference between .apk's being installed on your phone, versus a ROM or a patch to a rom that has to be installed in recovery. I think in the end this will make all our lives easier and when someone has a question about how do I install this radio or what is hboot we can just point them here. I'll probably start compiling instructions (and videos) during my morning break at work.
Im posting this here
1. as a place holder
2. do you think this should go into android development once it is completed and up and going. I think it should because that is where most people will look for it, but just want to get feedback from the community.
To all the developers out there thank you for your had work. I wish I understood the code writing so I could help you, so this is the best way I can think of giving back.
Disclaimer: This is here as a guide, I am not responsible for any damage that happens to your phone. If you have questions or run into any problems feel free to post in this thread of contact me. Thank you.
So Your Rooted, What do yo do next?
First if your TBOLT isn't rooted yet please go here (http://forum.xda-developers.com/showthread.php?t=996616) and follow Jcases great instructions on how to get your device rooted.
Definition of Terms
Stock: When people referring going back to stock, they are referring to the default android operating system that is being pushed by Verizon and HTC. Think of stock as Verizon and HTC's ROM for the Thunderbolt.
Recovery: This is where you go to back up and install roms, as well as wipe your data.
Bloatware: Extra software that HTC and/or Verizon puts on your phone that slows it down, drains battery, and just overall makes your device not as good as it should be.
ROM: A custom version of android that our awesome developers have made for you. Roms have a number of benefits besides just looking pretty. Some of the major benefits of flashing a custom ROM include, no bloatware, faster processing, better reception (with custom radios) and most importantly better battery life.
Super User: An application that allows you to grant other applications access to the system properties on your phone.
HBoot: This is the white screen you boot your phone into when powering your phone on using the power and volume down combination. From here you can flash leaked radios, as well as enter CWR manually.
Radio: This is the software on your phone that tells your phone how to communicate with Verizon.
Files on the "root" of your sd card: These files need to be placed directly on your sd card, and not in a folder in your sd card.
Rom Manager/Clockwork Recovery
So the first thing I would highly recommend after rooting your device is go and download Rom Manager (https://market.android.com/details?id=com.koushikdutta.rommanager&feature=search_result). Rom Manager is going to allow you the easiest way to flash clockwork recovery on your device. Clockwork recovery is the most essential component you will need in order to backup your current ROM and install a new one.
In order to install Rom Manager follow the link above or just search for it from the android market from your phone and download it. After it installs and opens your going to get a pop up that says Super User at the top informing you that Rom Manager is asking for permissions. When this happens click on remember (if its not already checked) and allow. At this point you you will see a number of different options, but for now the top one will be the most important. The very first box will say "Flash Clockwork Recovery" check this box and if it asks for any confirmation or permissions say yes.
After this completes congratulations you now have recovery on your device.
Once Rom Manager is done flashing the first thing you will want to do is back up your current stock OS. One mistake I've noticed many people do is immediately wipe their data and flash a custom ROM. If for some reason the install is bad, its makes life a lot easier to know you have a backup you can restore, versus HAVING to get that install you just tried to work.
Backing up with Rom Manager/Clockwork Recovery
Ok so we are still sitting at our Rom Manager screen with a ton of different options (I have the paid donated version so the screens may appear some what differently if you don't.) The very first box is the "Flash ClockworkMod Recovery" that we already did, right under that is the "reboot into recovery" option. This will be the method I will recommend but for now lets look at our other options.
The next section is titled Rom Management and for now we can skip that one and head towards backup and restore. Now Backing up and restoring your current ROM is as easy as as pressing one of those two options. When using these two options CWR (clock work recovery) runs a script that will do the following:
Auto(scripted) backup
If backing up your current ROM, CWR will turn your phone off and reboot it into a recovery screen. Once in the recovery screen the backup will automatically start, and once it finishes, it will once again turn your phone off and reboot it all the way back to your load screen, and just like that you have your first backup.
This method does work, and (if after I go through the steps to do the backup manually) you don't feel comfortable doing it manually this is a solid way to backup your OS. I personally, however, prefer to do all my backup and recoveries manually in CWR versus running the script.
Manual backup (through CWR)
Ok now to talk you through how to do your backup's manually (which is my preferred method). In Rom Manager the second option from the top of the screen is reboot into recovery. Press that and a pop up box will appear asking if you are sure you want to reboot into CWR, press ok.
If it is the first time doing this you may get another superuser prompt, once again click allow and remember. Your phone will now begin rebooting and you will end up with a orange screen that says ClockworkMod Revocery and then the version number.
Now if it is your first time in here take a minute to look at the number of options, for the most part your options are self explanitory
1. reboot system now
2. apply sdcard:update.zip
3. wipe data/factory reset
4. wipe cache partition
5. install zip from sdcard
6. backup and restore
7. mounts and storage
8. advanced
If when you start looking at these options and you see the wipe/data, don't freak out. It is nearly (if not impossible) to do a data wipe accidentally which you will see why later in the tutorial. For right now lets focus on the sixth option listed which is backup and restore. To maneuver around the options is fairly simple you do this by pressing your volume buttons. Volume up goes up and volume down well goes down. If you are at option number 1 you can press volume up to go all the way to the bottom. Using your volume keys go and highlight backup and restore. Once there you will select it by either pressing the "home" key.
After you select it you will see "nandroid" in white letters at the top left of the screen and only three options.
1. Backup
2. Restore
3. Advanced restore
All you need to do now is select backup (it should be selected by default) and press your home key, and the backup process will start. This can take a while depending on the number of apps that you have on your phone. During the process you will see 6 categories that have been backup-ed or or are in the process of. The categories are:
Boot image
recovery image
system
data
.android-secure
cache
During each section being backup-ed you will see a yellow status bar showing the percentage of the backup that has been completed. Realize that this is for each section, not for the entire backup. After the "backing up cache" completes you will see a message "no sd-ext found. skipping backup of sd-ext" this is normal don't freak out. Next you will see a "generating md5 sum" followed by backup complete. Once the backup completes you will be at the initial screen of CWR, reboot system now is selected by default, for now press the home key and let your phone reboot.
Renaming backups
After it reboots I would recommend going to your app tray and opening up Rom Manager one more time. Under the section "Backup and restore" click on the manage and restore backups button. In here you will find all the backups that you have on your phone. If you just did your first backup you will see it listed as a time stamp (yyyy-mm-dd.xx.xx.xx.xx) if you press this once a window will appear with three options:
restore, rename and delete. If you accidentally press restore or delete dont panic, a second pop up window will appear asking you to confirm the operation, just hit cancel and all is good with the world again. If you press the rename button, however, a pop up box will appear and you have the option of renaming the backup from the time stamp name to whatever you would like it. My first backup on my phone is simply called stock_no_bloat. Rename them whatever you would like, but I would advise changing them from the time stamp format.
Congratulations your first CWR backup is complete.
Restoring a backup
Warnings
First and foremost before you go any further in this guide MAKE sure you have a CWR backup on your phone. Any steps you follow from this point on without one, will make it a lot more difficult to get your phone working again then it has to be.
Also never leave a PG05IMG.zip file on the root of your sd card (we will go over what this file is and does later in the guide). If this file is on the root of your sdcard you will need to either have a sd card reader, or another phone you can use to move the file if your phone is not booting.
Manually booting into CWR
So before I go into how to install a custom ROM, I want to first address how easy it is to restore a backup. Many people will freak out because they get stuck into some sort of boot loop or their phone will freeze after a bad install. This is EXTREMELY easy to remedy if you just have some patience.
So for the sake of a hypothetical lets say you just installed your first custom ROM, and something has gone screwy on your phone. You turn it on it starts to boot and either restarts or just hangs. Don't freak out that handy backup you have sitting in your phone is about to save the day.
I would like to point out that you could also restore a backup just because you like an old rom better, or the current one you have is just to buggy for you. If you have a working phone that boots you can enter recovery as we did earlier by using Rom Manager and selecting "reboot into recovery" However, If you are reading this guide for instructional purposes I would recommend you read the following instructions as well,so you know what to do in a worst case situation.
1. if you are stuck in a boot loop or your phone is frozen, pop the back off of the phone and pull the battery.
2. put the battery back in your phone and turn your phone on by holding the power key and volume down button.
3. if for some reason you had a PG05IMG.zip file on the root of your sdcard, your phone will automatically begin loading this file. Eventually
it will give you the option of (volume up installing update) (volume down canceling update) press your volume down key and after that
do a battery pull (once again assuming you cannot get your phone to boot). Once your battery is pulled you will either need a sd card
reader or another phone you can put your sd card in and move the PG05IMG.zip file of of your root directory.
4. If you didn't have a PG05IMG.zip file on the root of your sd card HBOOT will load as normal, and you will see the following options
Fastboot
Recovery
Factory Reset
Simlock
Hboot USB
System INFO
Image CRC
5. using your volume down button select recovery, press power, and then your phone will booth into CWR.
Do not proceed with the actual steps unless you have a current working backup. The following steps will delete all the data from your phone
6. Once in CWR the first thing we are going to want to do is wipe all the data off your phone, so we can do a clean restore. Using the vol keys highlight wipe data/factory reset and press the home key. On the next screen use the vol keys again and select Yes and press home, CWR will no begin to wipe all the data on your phone.
7. Do this 2 more times for a total of 3 data wipes.
8 (I prefer to do this also) Now manually go to wipe cache partition (it is wiped during the factory reset but it wont hurt) verify you want to wipe the data and do this three times as well.
9. After you are done wiping the cache go down to advance and select it. Then highlight and select wipe davlik cache and do that three times.
10. Once all your data wipes are complete go to backup and restore and select it. Next select restore (not advanced restore) and on the next screen select the backup you want to restore. At this point your phone will begin restoring your backup and it will take roughly the same amount of time it took to do the backup initially. After the backup is complete reboot your phone and all should be well with the world again.

an decent introductory to terms with corrisponding directory/path placement, would be welcome.
I've been working compuers since the commodore, but with this as my first android, I found myself straining under the wieght of Full threads I had to read to get an idea of what is really going on.

get the how to backup with CWR complete would like feedback thanks.

[Q] Recovery Reboot problems

Hi, All,
Sorry if this has been answered before, I could not find it through search.
Whenever I reboot my Droid 2 Global, it goes straight into recovery (ClockWorkMod). I press the camera button and it reboots into the OS just fine. I tried uninstalling Clockwork, reinstalling ClockWork but that does not help.
Tried flashing but the regular firmware that I found did not work for my D2G phone.
Anyone has any clue on how to fix this?
Thanks,
shadov

Try actually removing CWM hijack files, and then reinstalling it.
Go to /system/bin, find logwrapper.bin; if it's there, delete logwrapper and rename logwrapper.bin to logwrapper. Check if the problem persists (I highly doubt it), then try reinstalling CWM.

Worked
That worked, thanks, man!
Are there any resources that explain how ClockworkMod (or any recovery hijacking) works? Wanted to understand better what actually happens on the system level.
Thanks

The false logwrapper CWM installs starts the CWM binary when there's a certain file present in a certain directory. If there's no such file, it just starts logwrapper.bin and startup continues as usual. That's about it.

I tried installing ginerbread update abd it fails. That's why I am trying to solve this problem in the first place.
When I tried installing the update today, it downloaded the update, rebooted and went into recovery partition and started extracting it (progress bar was moving for about 5 seconds), then I saw droid with exclamation point, phone rebooted again and said "Update failed"
Any tips?
Sent from my DROID2 GLOBAL using XDA App

I'm a bit tired of explaining this all over again.
Download the standalone update file from somewhere, or fetch it from your phone's /cache directory with Root Explorer once the download completes (do not confirm installation, just fetch the zip file). Place it into the root directory (/) of your SD card. Rename it to update.zip. Reboot into stock recovery. Choose install sdcard:update.zip. Check the error messages it displays.
For 99% of the cases the problem is CWM's logwrapper.

[Q] Fuhu Nabi 2 - Root and Removing Monarch

I have managed to follow the instruction to root and install the google play store from this http://forum.xda-developers.com/showthread.php?t=1905674 but it also mentions the ability to remove the Monarch kids interface and make it a regular ICS tablet. I am unable to find the system/vendor files to remove them. I have root permissions since it allowed me to run Titanium Backup.
I used ES File Explorer and wasn't able to find the necessary folders to remove Monarch. Any advice?

theonyxphoenix said:
I have managed to follow the instruction to root and install the google play store from this http://forum.xda-developers.com/showthread.php?t=1905674 but it also mentions the ability to remove the Monarch kids interface and make it a regular ICS tablet. I am unable to find the system/vendor files to remove them. I have root permissions since it allowed me to run Titanium Backup.
I used ES File Explorer and wasn't able to find the necessary folders to remove Monarch. Any advice?
Click to expand...
Click to collapse
Go into the settings of ES file explorer and check everything under root settings. The only folder you want to get rid of is the Apps in the vendor folder. Anything else can harm the system. I just used the cut feature on the apps folder and pasted it to my sd card to make sure it worked first. Good Luck!

That worked great, thanks. I had to make sure to change it to always boot in parent mode or else it tried to boot the monarch interface on a cold start and, not having the necessary files any longer, just ended up with a blank screen. I had to restore a unit to factory and then switch to boot in parent mode, then remove the apps folder. Works like a charm now.

theonyxphoenix said:
. then switch to boot in parent mode, .
Click to expand...
Click to collapse
how ?

theonyxphoenix said:
That worked great, thanks. I had to make sure to change it to always boot in parent mode or else it tried to boot the monarch interface on a cold start and, not having the necessary files any longer, just ended up with a blank screen. I had to restore a unit to factory and then switch to boot in parent mode, then remove the apps folder. Works like a charm now.
Click to expand...
Click to collapse
Guess I missed something and should've read better, how did you set it to boot only into parent mode.
Sent from my SAMSUNG-SGH-I957 using xda premium

theonyxphoenix said:
That worked great, thanks. I had to make sure to change it to always boot in parent mode or else it tried to boot the monarch interface on a cold start and, not having the necessary files any longer, just ended up with a blank screen. I had to restore a unit to factory and then switch to boot in parent mode, then remove the apps folder. Works like a charm now.
Click to expand...
Click to collapse
How do you set it to boot into parent mode?

byohaserd said:
How do you set it to boot into parent mode?
Click to expand...
Click to collapse
Did you try going to settings -Security - put a TIC in " Set Parent Mode as default mode " ?
---------- Post added at 07:15 AM ---------- Previous post was at 07:07 AM ----------
ALSO
I found no need to delete the vender/apps folder as it can be used to help get rid of "Android is upgrading ' message after each boot up that seem to come when you install apps from play store
---------- Post added at 07:28 AM ---------- Previous post was at 07:15 AM ----------
theonyxphoenix said:
I have managed to follow the instruction to root and install the google play store from this http://forum.xda-developers.com/showthread.php?t=1905674 but it also mentions the ability to remove the Monarch kids interface and make it a regular ICS tablet. I am unable to find the system/vendor files to remove them. I have root permissions since it allowed me to run Titanium Backup.
I used ES File Explorer and wasn't able to find the necessary folders to remove Monarch. Any advice?
Click to expand...
Click to collapse
I used TWRP to do anything - rooted or unrooted you can make change as you wish .
when you are in TWRP mount system then use advanced and file manager
hope this helps

I did not see that until you mentioned it...thanks
I was able to get it to work by going into a startup manager and freezing kidsmode2 and nabimode. I erased the apps folder though cause I wanted the space freed up.
Sent from my NABI2-NV7A using xda app-developers app

I deleted some files I shouldn't have. My nabi 2 keeps rebooting. It goes from the start up screen to "Android is upgrading..." Then back to the start up screen, then again. When I try to go to "Recovery Kernel" I get the Android laying down with the Red triangle over his chest..any suggestions?

Rest to Factory setting
mikewhit001 said:
I deleted some files I shouldn't have. My nabi 2 keeps rebooting. It goes from the start up screen to "Android is upgrading..." Then back to the start up screen, then again. When I try to go to "Recovery Kernel" I get the Android laying down with the Red triangle over his chest..any suggestions?
Click to expand...
Click to collapse
1-switch off.
2-press power button & vol + together.
3-press vol - to go to recovery kernel and press vol + to select it.
3-android model should come lying down with red triangle!.
4-press vol - & vol + together.
5-select the system reset and press power button.
6-after that switch off and on with all new factory settings.
Best Regards.

Eric Karz said:
ALSO
I found no need to delete the vender/apps folder as it can be used to help get rid of "Android is upgrading ' message after each boot up that seem to come when you install apps from play store
Click to expand...
Click to collapse
I created a new gapps package that does away with the upgrading message on every boot.
http://forum.xda-developers.com/showpost.php?p=35887804&postcount=1

Nabi 2 Charge/Reboot problem
t499user said:
I created a new gapps package that does away with the upgrading message on every boot.
http://forum.xda-developers.com/showpost.php?p=35887804&postcount=1
Click to expand...
Click to collapse
Completed the OTA to 1.9.37, root, and gapps install - had the upgrading message on every boot but fixed that with the new gapps package (thanks a lot to all the great developers on this forum!)
However I still have a problem since the root process that I haven't seen addressed so far after searching the forums.
After my putting the Nabi 2 to sleep and plugging in the charger, it will fully charge and turn the battery light green as it should, shortly after that the device then powers off and requires a reboot/cold start vs. just a quick click of the power button to return from sleep mode. It does reboot fine and has a full charge - all other operations are normal.
Any suggestions on how to eliminate this power down/reboot after charging?
Thanks!

I flashed your package but the android upgrading still shows up for me,only for a few secs and it seems as if no programs get upgraded...what are your thoughts on this? How can I find the stray files that are causeing this?
Sent from my NABI2-NV7A using xda app-developers app

stuck in TWRP
My tablet only boots in TWRP v2.2.2.1
I've flashed at least 5 different images in fastboot using at least 5 different methods. Every time I think I make any progress, I reboot my nabi2 and it reboots directly to TWRP. Any advice would be greatly appreciated.

mikewhit001 said:
My tablet only boots in TWRP v2.2.2.1
I've flashed at least 5 different images in fastboot using at least 5 different methods. Every time I think I make any progress, I reboot my nabi2 and it reboots directly to TWRP. Any advice would be greatly appreciated.
Click to expand...
Click to collapse
Are you trying to flash a backup of 1.9.37 or just a program thru install? I know that if you wipe system and then flash another backup, if the backup is no good, twrp will not boot system but go right back to twrp. That is a safety setting, cause if it booted with no system installed you would most likely have a bricked device. That happened in the early days of Twrp, so they added the safety setting. If you flashed a backup, how long did it take, a good backup or image will take 10+ minutes, a bad 1 will say done in 1-2 minutes or less.
Might help if we had a little information about what you where doing.

ALD3 said:
Are you trying to flash a backup of 1.9.37 or just a program thru install? I know that if you wipe system and then flash another backup, if the backup is no good, twrp will not boot system but go right back to twrp. That is a safety setting, cause if it booted with no system installed you would most likely have a bricked device. That happened in the early days of Twrp, so they added the safety setting. If you flashed a backup, how long did it take, a good backup or image will take 10+ minutes, a bad 1 will say done in 1-2 minutes or less.
Might help if we had a little information about what you where doing.
Click to expand...
Click to collapse
I tried flashing multiple backups and they all go to twrp. The backups only took a minute or 2.

mikewhit001 said:
I tried flashing multiple backups and they all go to twrp. The backups only took a minute or 2.
Click to expand...
Click to collapse
Ok your backups are all bad, that's why it finishes so quick and won't boot out of TWRP recovery. You will have to download a image file and get it into the TWRP folder on your sdcard. You will have to download it on your computer unrar it and name the folder something like unrooted 1.9.37 and transfer it to your micro sdcard. Then put micro sdcard back in tablet. In TWRP recovery, you will have to go into Advanced>File Manager. In file Manager, you will have to click on external sdcard and copy the file from there back to sdcard>TWRP>backups>serial#>unrooted 1.9.37 it doesn't matter what the folder name is that you put in the serial# folder but the all the others are as named and your new folder HAS TO BE IN THE SERIAL# FOLDER, or Restore will not see it. When that is done go back to main menu and Restore, you should see your new folder, choose it and swipe to restore. This should take 10+ minutes. You should be able to reboot to system then.
Unrooted1.9.37 file to download
https://www.box.com/shared/ew0jcmch2ohvr43ubjqe
This thread can help you a lot quicker.
http://forum.xda-developers.com/showthread.php?t=1905674
If you have problems, PM me and I will send you my email so we can work quicker and won't trash up this thread.

I'm having the same issue since the gapps update, where the Nabi shuts itself down while charging. Sometimes it can be a real pain to reboot after it does this.
Funhog51 said:
Completed the OTA to 1.9.37, root, and gapps install - had the upgrading message on every boot but fixed that with the new gapps package (thanks a lot to all the great developers on this forum!)
However I still have a problem since the root process that I haven't seen addressed so far after searching the forums.
After my putting the Nabi 2 to sleep and plugging in the charger, it will fully charge and turn the battery light green as it should, shortly after that the device then powers off and requires a reboot/cold start vs. just a quick click of the power button to return from sleep mode. It does reboot fine and has a full charge - all other operations are normal.
Any suggestions on how to eliminate this power down/reboot after charging?
Thanks!
Click to expand...
Click to collapse

i cant delete /vendor/apps always tells me (app can not be deleted) thats in es file explorer the others say its deleted but its still there???

streetglide13 said:
i cant delete /vendor/apps always tells me (app can not be deleted) thats in es file explorer the others say its deleted but its still there???
Click to expand...
Click to collapse
In es go to the menu where you turn on root explorer and tap the words 'root explorer' then a menu will pop up, tap mount r/w and then set /system to rw. You then should be able to delete the files. After you're done deleting set system back to read-only.

Titanium Backup has memory issues?

Ok, so I flashed Scott's 12/19 CM build and everything is booted up, nothing is wrong, or at least not horribly wrong. Here are the events as they occurred in great detail: Open up Titanium Backup- it asks for SU permissions, select ok and remember forever. Pops back up with the same message about 4 times, then finally accepts that it has permission to work. Go through and select an app to restore, it decides to forget that it has permission and asks a couple more times. It again is allowed to work. During the process it pops up again. Same procedure. Finally installs the app, and pauses on the screen where it says the app is being restored (I am only restoring the app, no data) Then asks for SU permission.
I then exit out and re-open TB, and the process starts over. I decide to uninstall and install, same thing. Then out of the blue it tells me I'm not rooted, I immediately put the ORLY face on and go to Root Checker, I am indeed rooted.
I'm not really worried about this, as the apps I'm trying to restore aren't like, need right now or I die, but I'm too lazy to go onto 4shared and re download them. I would just like to know why it's doing this, and how to fix it.
TL;DR Titanium Backup has Alzheimer's.

I have the same issue; look at the Q&A thread for the ROM.
FlyingIsFun1217

Simple fix, just updated the Super SU binaries and everything is fine.
Sent from my SGH-I997 using xda premium

cwm nanodroid backup

1. So i made a backup using cwm recovery and everything was successful but on the second last line it said "no android_secure found.moving applications to (i cant remember where)".did it really back my stuff?
2.where did it create the folder.i cant find it using file manager.
3.and when i go to cwm recovery and go to "reboot system now".on the top it say" root access possibly lost.fix?This cant be undone"....i got three options.1 no.2 yes-fix root(system/xbin/su/) and 3 go back...i have been choosing go back and it reboot the phone normally....is my phone still rooted.which option should i choose from now on?thank

00MATRIX00 said:
1. So i made a backup using cwm recovery and everything was successful but on the second last line it said "no android_secure found.moving applications to (i cant remember where)".did it really back my stuff?
2.where did it create the folder.i cant find it using file manager.
3.and when i go to cwm recovery and go to "reboot system now".on the top it say" root access possibly lost.fix?This cant be undone"....i got three options.1 no.2 yes-fix root(system/xbin/su/) and 3 go back...i have been choosing go back and it reboot the phone normally....is my phone still rooted.which option should i choose from now on?thank
Click to expand...
Click to collapse
The android.secure thing is not an issue. It means you did not encrypt the file system.
The constant root nagging is a 4.4 bug, I think.
You should use TWRP instead.

Or use philz....
Sent from my Nexus 5 using Tapatalk

Backup should be in /data/media/clockworkmod/backups
You can use a file explorer, like root explorer, to find it.