Database Develop

[Fix] Droid3 Boot looping because you messed with /System Apps after upgrade?

I did not find a complete solution to this while cruising through the forums but found a partial solution in 2 Posts that when combined helped me fix my issue. I'm not sure if me being a noob I should have known 1 part before starting another but for others who know less or about the same as me here's the solution I had.
MY problem was I deleted some System Apps (also deleted Yahoo apk which messes with the contacts). If you read everything here they will tell you not to delete, but rename. Which some might ignore like I did. I was in a rush and not on my computer (at work; restricted computers) so I could not use Pete's (psouza) Root Tools to restore my apps and instead tried to copy and paste the APK's which mess up my Droid and caused it to constantly boot loop.
When i got home I had no success trying to Run Temp ADB Root Procedure in the Tools while it was boot looping to restore the apps so I was trying Krazykrivda's post to attempt to fix my boot looping which didn't fully correct itself because i never got root until I combined both solutions.
Step 1 I did what KrazyKrivda said in his post http://forum.xda-developers.com/showthread.php?t=1236465
Directions:
1. Battery Pull
2. Put Battery Back
3. Hold M button on keyboard then power
4. Use vol - button to go to BP TOOLS (don't select yet)
5. Connect via USB to computer with ADB
6. In terminal on computer...
Code:
adb wait-for-device shell
7. On phone use vol + button to select BP Tools.. then wait for your terminal to get you into shell (this will happen while the phone is continuously bootlooping)
Click to expand...
Click to collapse
After getting the prompt that the adb shell was successful I opened Pete's Root Tools clicked on Run Temp Adb Procedure then Clicked on Restore My /System/Apps
While the Tool does the restoring the phone will restart so you will have to be quick and repeat steps 3 through 7 so the Root Tools can automatically restore the Apps. Make sure you catch the opportunity to do 3 right before it restarts.
After it restores the apps the phone will reboot itself for one last time and you should be good. It'll take a while to fully boot that 1st time.
I hope this helps at least one person solve their problems.

[HELP!] Half-bricked my Droid 3

I've had a Droid 3 for a little under a year now. For the past few months I was having an 'issue' where the phone would not vibrate when I got an SMS message. Apparently this is a known issue caused by installing a non-stock SMS app from the app-store. I took it to the Verizon store and the guy put in a request for a replacement phone. He knew I'd rooted it and just said to make sure I unroot it, uninstall the bootloader, and factory reset before sending it in. I did all 3 things however the reset didn't reset my custom boot animation so I figured I'd activate the phone real quick, reroot, change that, and unroot. I started the activation process and I get to the "Add Accounts" screen, added my Google account, and hit Done. It asks about location services, I hit "Next" and then com.motorola.setup crashes and I have to force close. If I hit the Home button it takes me right back to the "add accounts" screen and I'm stuck in that infinite loop. I can still receive texts and reply to them from the notifications menu, I can send and receive phone calls with voice commands, I can access the browser, but that's about it. I cannot get to the home screen and I cannot open the settings 'app'.
I brought it back to the Verizon store and they were baffled, told me that Verizon would probably charge me full retail for the replacement if I sent this once back, so I sent back the replacement phone and am stuck with this one now.
I think what caused this is that I had the 'Bloat Freezer' app installed and I had frozen a bunch of the default Verizon apps. I didn't unfreeze them before the factory reset and I have a feeling that's what's causing the issue. I had the idea to re-root the phone and install Bloat Freezer again from the Play store but the Play store isn't recognizing my Droid 3 anymore.
Any suggestions?

Factory reset is a deceiving term. It resets it to factory user data (none) and settings. It doesn't restore the system. What you need is an SBF to flash the entire phone to factory software, overwriting all partitions. First though, you must find which system you had. Since you didn't recently get this phone, did you accept an OTA update within the last month or so? If so, head over to the Dev area and download the stickied SBF file to return you from .906 to .890. If not, there is an SBF in the General area called Quick Unbrick or something like that.
http://www.youtube.com/watch?v=pcne9tFtBxY

Awesome! Thanks for the info. I'll give this a try when I get home from work tonight. Do you know if there's any way to tell what version I need without the settings app? Or perhaps if there's a way to forcibly open the Settings app?

If you've had your D3 for over a year and have not updated to .906, then you'll need .890. The .906 update is fairly recent (a couple months old I think?) so if you don't explicitly remember taking it, use .890.
Side note, check the rom you used before this happened. Check if it's based on .906 or .890.
Sent from my DROID3 using xda premium

JDiPierro said:
Awesome! Thanks for the info. I'll give this a try when I get home from work tonight. Do you know if there's any way to tell what version I need without the settings app? Or perhaps if there's a way to forcibly open the Settings app?
Click to expand...
Click to collapse
Do you know if you enabled USB debugging? (from settings->applictaions->development - check "USB debugging" on.) Many root apps require that.
Anyway, if you did, you can install the Android SDK's adb app and, from a command prompt, you can try to type the following command (with the phone on and cabled to the computer)
adb shell cat /system/build.prop | grep "version"
This should show you a bunch of lines, one of which will be "ro.build.version.full". The system version follows that text on the line - I have last month's OTA, so mine is Blur_Version.5.7.906.XT862.Verizon.en.US (so I have 5.7.906).
You can most easily get adb (for Windows) with instructions from here: http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/
After you get those files unzipped in c:\android, you can start a command prompt by hitting start, type "cmd" and enter in the search box - this will start a black command prompt window. From there, enter the command cd \android and then enter the adb command I put up above.
I'm not sure it will work, but it should.

You can bypass the activation. Starting with the top left corner, press each corner in a clockwise rotation. This will bring your phone to the home screen so you can then find which version it's on.

doogald said:
Do you know if you enabled USB debugging? (from settings->applictaions->development - check "USB debugging" on.) Many root apps require that.
...
adb shell cat /system/build.prop | grep "version"
Click to expand...
Click to collapse
What USB mode should the phone be in for this to work? I definitely had USB Debugging on before I did the factory reset; would that reset it though? When I try the command (minus grep, i'm in Windows unfortunately) I get 'error: device not found'
eww245 said:
You can bypass the activation. Starting with the top left corner, press each corner in a clockwise rotation. This will bring your phone to the home screen so you can then find which version it's on.
Click to expand...
Click to collapse
I had tried this but it still brought me straight to the "Add Accounts" screen, not to the home screen.

JDiPierro said:
What USB mode should the phone be in for this to work? I definitely had USB Debugging on before I did the factory reset; would that reset it though? When I try the command (minus grep, i'm in Windows unfortunately) I get 'error: device not found'
I had tried this but it still brought me straight to the "Add Accounts" screen, not to the home screen.
Click to expand...
Click to collapse
Needs to be I. Charge only mode. On stock rom I believe its called none
Sent from my XT860 using xda premium

JDiPierro said:
What USB mode should the phone be in for this to work? I definitely had USB Debugging on before I did the factory reset; would that reset it though? When I try the command (minus grep, i'm in Windows unfortunately) I get 'error: device not found'
Click to expand...
Click to collapse
You can grep: because you are running a shell command, I believe it is running on the phone, not on the windows computer.
(The grep is not all that critical, though, as I believe the version number line is one of the last lines displayed by that command.)
You can do an:
adb devices
before you run the shell command to verify that the computer and phone are communicating; it should return a line of characters that represents your phone, if it is connected.

Root guide with lots of pictures and instructions [AndroidNZ]

Hi everyone,
I see more people than usual having issues with Rooting their Nexus 7 because of problems with booting into CWM recovery post flash - thought I would do a nice plain and easy to follow guide including instructions for booting into CWM recovery from a command point (thanks to Wugfresh for his Toolkit which is used in the guide).
http://www.androidnz.net/2012/07/how-to-root-your-nexus-7.html
Porting the full guide here, first the text because that is a simple cut n paste job, images to follow soon:
Before we get down into the nitty-gritty of the guide itself you should familiarise yourself with our usual disclaimers at the beginning of this post. I say this not because we don't care if you have problems, it's just that our capacity to trouble shoot is limited, and you shouldn't have embarked on an adventure to Root your device unless you did your due diligence first and had some understanding of what you were up to. One final disclaimer weasel-word at the off: the CWM recovery ports for the N7 are still a little iffy at this stage and even when taking appropriate steps to make it permanent you may only be able to boot into it via a command prompt window. Expect updates once fixes are available.
Disclaimers out of the way, here are the things you will need:
A Nexus 7, fully charged
A windows PC (the guide may work on macs via Windows virtual environments, but that isn't confirmed by us and is outside the scope of this guide)
The appropriate Nexus 7 USB drivers, there are several ways to get these:
Preferred method - Go to this thread at XDA-Developers and download and install the Root Toolkit there, which has an automated drivers installation included (this is preferred because it is what the guide that follows is based on because the Toolkit is probably going to be the most straightforward for the majority to use, and even if it fails and they have to resort to using command prompts that is more easily done from the Toolkit). Many many thanks to WugFresh at XDA for producing such a noob-friendly Rooting application - please consider making a donation to him here.
Install the Android SDK from here. Please note if you are already an SDK user that the Google USB drivers in the SDK have updated with the release of the Nexus 7 and Jelly Bean and you should update your drivers from within the SDK itself
Install the universal drivers from this post at XDA-Developers, but please make note of how you will need to adjust fastboot commands if you are using these drivers
Go to this post at XDA-Developers and install the USB drivers from there if you have no luck whatsover with any of the other methods
OK, now that you've got the Root Toolkit let's proceed (if you plan to do this with the SDK and command prompts then you should be advanced enough to follow the guide here, I did the first time and if you've done this stuff before the process is trivial).
Open the Root Toolkit, at the prompt to select your device scroll down to the bottom and select the Nexus 7 and the version number that corresponds to the firmware installed on your Nexus 7 (you can find this out in Settings --> About tablet --> Android version)
You'll be greeted with a screen that looks like this:
Click on Initial Setup and use the automatic driver installation facility from here to install USB drivers, it will check that ADB and Fastboot commands are working before dropping you back to the install window.
Turn on USB Debugging in the Nexus 7 by navigating to Settings --> Developer options. Turn on Developer options using the toggle in the top right hand corner, and then turn on USB debugging
Connect your Nexus 7 to your computer with the micro USB cable that came in the box. At this point it is vital that your computer recognises the Nexus 7 as a connected device, you will know if it has because a Nexus 7 "AutoPlay" window should pop up and ask you what action you want to take. If it doesn't show up, pull down the notification tray and press on the notification that says "Connected as a media device". A new menu will open and select the "Camera (PTP)" option. You should now get the AutoPlay window.
Head back to the Toolkit, and select "Unlock" from here, be aware that this will wipe your device (you might want to take a backup if you've already installed a lot of stuff on the device, that's just a button click away also in the Toolkit)
This will boot the device up to a screen giving you the option to unlock the bootloader, with "Yes" selected hit the power button. You'll see some text in the top left corner telling you it is unlocking the device, and then you will see the red "Locked" text toward the bottom of the screen change to "Unlocked". Moments later the device will reboot, and because it will have been wiped you will need to either set it up again or just skip past set-up and get back to the homescreen.
Once you're back onto the home screen, connect as you did before and take the same steps to turn on USB debugging and get the AutoPlay prompt to appear. Then go back to the Toolkit and select the Root option with permanent CWM recovery. All things going well the process will be fully automated from here, it will check that ADB and Fastboot are working, push the SU and CWM files to the device, boot the Nexus 7 into it's bootloader, flash CWM recovery to the device, and then reboot with Root privileges and a fresh new recovery permanently installed.
...or so the theory goes. Using this method I get Root, but CWM recovery is only accessible via command prompt, and I see others having the same problem. So...
Accessing CWM recovery:
In the Root toolkit go to Advanced Utilities by launching it here:
On the next screen select Launch CMD Prompt:
Once the command prompt appears type: ADB reboot recovery - the phone will boot into CWM recovery for you, so you can do things like make Nandroid backups, install zip files and so forth
Installing the 4.1.1 update post-Root and installation of CWM recovery:
Install OTA Rootkeeper by Supercurio from the Play Store here
Open the app once installed and grant it SuperUser privileges
In the app select "Protect Root", and then "temp unroot" the device
Download a zip of the 4.1.1 update here.
Copy it to the internal SD of the Nexus 7
Access CWM recovery as per the instructions above. In this version of CWM recovery you will navigate the options with the volume keys and press the power button to select an option - do that to navigate to "Install zip from SD card" and press the home button
On the next screen go to down "Toggle signature verification" and toggle it until it says "disabled" at the bottom of the screen (it should be set to default to disabled, but you lose like 5s making sure)
Go up to install zip, navigate to the zip file you downloaded in step one and install it
When the device reboots go to OTA Rootkeeper and restore Root, viola! You're done!
So, after all is said and done you should have a Rooted Nexus 7, running the 4.1.1 update, and with a custom recovery that can only be accessed via command prompt. Don't forget to shout WugFresh, the Toolkits developer, a coffee - make a donation here.

Would be nice if you posted that guide on this forum too.
Thanks for the guide.

Oooohh pictures

Caliyork said:
Oooohh pictures
Click to expand...
Click to collapse
You know, for the totally acopic

Will this work on the new Build number JRO03D? Or should I wait until he updates the toolkit?

Dillon610 said:
Will this work on the new Build number JRO03D? Or should I wait until he updates the toolkit?
Click to expand...
Click to collapse
No idea. You can simply downgrade to an older stock image using his Toolkit though and then follow the same process used in the guide to update to the latest build.

"Meh" at requirement #2:
A windows PC
Click to expand...
Click to collapse
I haven't ran Windows for years. I hope there's a way to do this with Linux (assuming a computer is even needed?)
I remember rooting my Optimus T with Z4 root... one click, bingo bango, done.

JaSauders said:
"Meh" at requirement #2:
I haven't ran Windows for years. I hope there's a way to do this with Linux (assuming a computer is even needed?)
I remember rooting my Optimus T with Z4 root... one click, bingo bango, done.
Click to expand...
Click to collapse
"Windblows"

Any way to do on Mac? Also I'm new but what will root do that out of box won't? Any guides that help explain this? Thanks!

mario24601 said:
Any way to do on Mac? Also I'm new but what will root do that out of box won't? Any guides that help explain this? Thanks!
Click to expand...
Click to collapse
There's a wiki on cyanogenmod.com that explains root.

mario24601 said:
Any way to do on Mac? Also I'm new but what will root do that out of box won't? Any guides that help explain this? Thanks!
Click to expand...
Click to collapse
Should be doable on mac in a windows virtual environment, which seems to be how most mac users are doing things here at XDA.
Actually looking for someone to write "for mac" guides, if anyone is up for that!

[ROOT]Help with 7.3.1 KFHD 7"

So I have run into several problems using several different methods, none of which have worked properly and I really need some help. Now, I am by no means stupid when it comes to computer stuff but I am not a programmer nor any sort of software engineer. I understand much of the command line stuff and some simple code but I don't understand why nothing I have tried is working. So let me list the problems I've run into in my attempts to root my KFHD 7":
Root Many Android:
I am using v28 (which I believe is the latest and is reported to work on my device hardware and software).
I am unable to run the batch file as an administrator which I believe is the problem that results in the "permission denied" errors when trying to push the packages like superuser and busybox.
I am certain I have followed the tutorial to the letter so I don't know where I am going wrong. I can open the command window as an admin and cd to the C:\Root and run the batch but that doesn't fix the permissions errors.
Qemu:
I am using the latest version.
I select option 1 to root and it runs through the processes but nothing works and it just goes through several reboots so I am assuming it is running into the same issues as RMA, above.
KFFirstAide:
I am using the 64 bit as per my system. I run through option 21 to root my device using method 2 (Preferred).
It shows some success in that I can see the apps BusyBox Installer and Root Checker, however it does not push the rest of the packages necessary and this is evident by when it says I should receive a SuperSU or SuperUser popup, nothing happens and so the rest fails, though it says the root check passes in the final step.
So now I ask, is there a better way or something I am doing wrong with my Kindle Fire HD 7" 7.3.1?
Thanks in advance.

Softbricked after 5.1.1 sideload - HELP!

Last night I sideloaded the 5.1.1 update to my Droid Turbo. While playing around with it this morning, I accidentally clicked the 'Force RTL' option under accessories. Immediately after, my phone crashed, and on boot would display 'system ui has stopped working' indefinitely. The wallpaper would load, and the alert modal would appear, but clearing it just kicked up another 'system ui has stopped working' modal a few seconds later.
I cleared the cache, and now when I reboot the device, it comes up with the Recovery Andy image with 'no command' below. I don't mind doing a factory reset, but I have a LOT of data I'd lose in the process. All of my pictures are backed up to Dropbox/G+, but I have a lot of other files and backups that I neglected to save externally prior to the update ... because I'm a genius.
When I try to reapply the update, I get a message indicating "/system/app/3c_main.apk" has unexpected contents. I've tried to push from SD and from ADB, both with no luck. At this point I'm happy to just reset the device, but I want my data off first. All ADB commands with the exception of SIDELOAD return 'error: closed', so I can't even backup my files.
Ideas? Help?! ANYTHING?!

spikejnz said:
Last night I sideloaded the 5.1.1 update to my Droid Turbo. While playing around with it this morning, I accidentally clicked the 'Force RTL' option under accessories. Immediately after, my phone crashed, and on boot would display 'system ui has stopped working' indefinitely. The wallpaper would load, and the alert modal would appear, but clearing it just kicked up another 'system ui has stopped working' modal a few seconds later.
I cleared the cache, and now when I reboot the device, it comes up with the Recovery Andy image with 'no command' below. I don't mind doing a factory reset, but I have a LOT of data I'd lose in the process. All of my pictures are backed up to Dropbox/G+, but I have a lot of other files and backups that I neglected to save externally prior to the update ... because I'm a genius.
When I try to reapply the update, I get a message indicating "/system/app/3c_main.apk" has unexpected contents. I've tried to push from SD and from ADB, both with no luck. At this point I'm happy to just reset the device, but I want my data off first. All ADB commands with the exception of SIDELOAD return 'error: closed', so I can't even backup my files.
Ideas? Help?! ANYTHING?!
Click to expand...
Click to collapse
Did you use the zip from Rootjunky?
Sent from my Droid Turbo using Tapatalk

zefir738 said:
Did you use the zip from Rootjunky?
Sent from my Droid Turbo using Tapatalk
Click to expand...
Click to collapse
Yes

spikejnz said:
Yes
Click to expand...
Click to collapse
You might have to wait until the OTA is available for manual download and then flash it via RSD Lite. The way the zip works is it'll only install if you have version 21.44.12.en.us installed. You have 23.11.38 so it won't install now.
Sent from my Droid Turbo using Tapatalk

zefir738 said:
You might have to wait until the OTA is available for manual download and then flash it via RSD Lite. The way the zip works is it'll only install if you have version 21.44.12.en.us installed. You have 23.11.38 so it won't install now.
Sent from my Droid Turbo using Tapatalk
Click to expand...
Click to collapse
Yikes. OTA is supposed to drop today, so hopefully that becomes available soon thereafter. Not sure how long I can survive without my phone.

spikejnz said:
Last night I sideloaded the 5.1.1 update to my Droid Turbo. !
Click to expand...
Click to collapse
I assume you mean the 5.1 update? or did you try to use a 5.1.1 update for some other phone by mistake? if so there may be no easy solution.

I don't accept defeat. Everyone said my data was a lost cause, and that Factory Reset was my only hope. Yeah, well who's copying data off his device right now?
THIS GUY.
I downloaded the firmware, removed the "erase userdata" line from the batch file, and ran it to restore the images and partitions.
I then cleared the cache (again) and rebooted my device.
Back to the 'System UI has stopped' loop
Tried unsuccessfully to send ADB commands to the device
Opened and ADB Shell in Cerberus Dashboard, but kept getting disconnected
Sent an Unlock command in Cerberus Dashboard to my device ... voilla!
UI is still crashing, but Windows is now attempting to install drivers
After trying to manually install drivers for an extended period of time, decided to attempt it on my Mac
BOOM, FS mounts and Android File Transfer is now accessing all the files, even if my display is all jacked!
Next comes the factory reset. I knew there was a reason I installed Cerberus on my non-rooted device.

Fix RTL via ADB
I had this problem on my turbo after reading about a possible fix for snapchat image problems.
After a bit of googling, I came up with this simple fix.
This will only work if ADB Debugging is enabled and your PC is already authorized.
No need for root.
Code:
adb devices
adb shell
settings put global debug.force_rtl 0
reboot

And I suppose if you do NOT already have ADB enabled et al, you're SOL?

AnoraxAudio said:
And I suppose if you do NOT already have ADB enabled et al, you're SOL?
Click to expand...
Click to collapse
If your phone has a secure lock screen, it will not recognize a usb port for file transfer or ADB mode until the password/pin/pattern/etc. has been entered. The Cerberus method described above worked because it was able to meet this requirement. With this in mind, you have the following options depending on your lock screen situation:
1. Insecure lock screen, ADB previously enabled: use the ADB method described above.
2. Insecure lock screen, ADB disabled: Plug in the USB, transfer over your important files, reboot the phone in bootloader mode, select recovery mode, perform a factory reset.
3. Secure lock screen (all cases, assuming you can't unlock it with Cerberus or something similar): Wipe cache through recovery to see if that helps anything. If it doesn't, you can try reflashing the system image via mofo or fastboot to see if that helps anything. If not, bite the bullet and perform a factory reset. You will lose your data.
Now if you have mofo, you might be able to flash a rooted rom that can perform the adb method using a su.d script, but I'm not entirely sure about that.