yashsingh1/xdaforums huggingface dataset:
[Nexus S Q&A, Help & Troubleshooting] Cyrille28410:
your nexsus ha been identified :

ro.product.device=crespo

and when the install script start, it compare its own value :

ro.product.device=crespo4G

to the one above

and there an error

The problem is why we have ro.product.device=crespo at the beginning of the log ?

For me the problem is : your nexus is identified as a Crespo and you try to install a Crespo4G

Very strange !

If this function "ro.product.device" is used by recovery, maybe you could try to reinstall the recovery ?
[Nexus S Q&A, Help & Troubleshooting] anglergab:
You should flash a custom recovery and ROM corresponding to your hardware version. The version can be found beneath your battery on a sticker.
[Nexus S Q&A, Help & Troubleshooting] warriorforgod:
That is what is weird. I have had a custom recovery and roms since I bought my phone last year. This just started happening yesterday. Haven't flashed a recovery or new from for a couple if weeks.
[Nexus S Q&A, Help & Troubleshooting] warriorforgod:
Update

Reflashed my recovery and now I can flash rooms just fine. Strange.
[Samsung Galaxy Mini] xenv1:
I am using CM7 rc5.7 of squad!

Anybody tell me is it have bootsoud? Firt flash=>no sound, then the second, the 3rd...boot no sound too!

In my exam, i bring it to rom, put in silent mode, but i think it no safe, i turn off it:)

unfortunately for me, when i doing exam, the ringtone rang, i see the boot amition, phone starting...and i can't turn off it :(

Now, i delete poweron.ogg, but i want to know, why it work (bootsound) in my exam ? how to enable/disable it without delete file?:confused:
[Samsung Galaxy Mini] dheeraj (dhlalit11):
silent boot and app can low the volume while booting and will restore volume setting after boot
[Samsung Galaxy Mini] killar_aka_arabu:
settings -> cm settings -> performance and scroll down.
[Motorola Droid 4] kwyrt:
Has anyone tried this yet? http://www.gottabemobile.com/2012/04/18/droid-4-update-brings-better-battery-life-backlight-fixes/

I downloaded last night, installed Voodoo Rootkeeper, unfroze any apps that I had frozen, and then chickened out. LOL! I'm not sure what this will do with safestrap installed. Makes me a little nervous with no fastboot files.

I'm thinking it might be best to uninstall safestrap first and then apply the update. Any thoughts anyone?
[Motorola Droid 4] duffman452001:
On the D3, I would switch to non-safe system, apply the update in recovery, reboot, re-root, reinstall safestrap recovery from the safestrap app, reboot into safestrap, switch back to safe and everything was peachy. No need to even reinstall safe system as everything was still there. Did it twice for the 905 and 906 updates, dont see why it would be any different for the D4

EDIT: the only difference I may have is that I keep my non-safe system stock, I dont freeze/remove bloat, just root.
[Motorola Droid 4] podspi:
Glad to see wifi is on the list of bug fixes. I haven't been able to connect to my work wick, and my home wifi drops all the time (tethering from phone works perfectly though,go figure).

I probably will wait until this officially drops, though. Bleh, why no fastboot files yet?!
[Motorola Droid 4] swjpilot:
The download has been pulled anyone have this file they can upload elsewhere?
[Motorola Droid 4] kwyrt:
http://db.tt/YIiI5SU3
[Motorola Droid 4] swjpilot:
Thanks!!! Got it!
[Motorola Droid 4] teookie:
Just rebooted after applying the update. I'm running stock ROM. I unfroze everything I had frozen, hid root w/ Voodoo OTA, rebooted, did a backup (just in case), applied the update, restored root with Voodoo OTA and everything appears to be working.

Hope this really does fix the wifi problem. Been having some problems with the wifi here at work.
[Motorola Droid 4] kwyrt:
Took the plunge. I was running stock rooted with voodoo rootkeeper and safestrap recovery installed. Here are the steps I took:

1. Unfroze apps I had frozen in Titanium Backup.

2. Uninstalled safestrap recovery via the safestrap app (Shouldn't need to uninstall the app itself).

3. Backed up Superuser using Voodoo then selected "temp. un-root".

4. Rebooted and installed the update via the instructions from the link (FYI: You will need to have the update zip in /sdcard-ext, not /sdcard).

5. Rebooted and the phone shows the updated software version.

6. Restored root via Voodoo.

7. Reinstalled safestrap recovery using the safestrap app.

Success!
[Motorola Droid 4] teookie:
Wifi still dropping off randomly. I don't think this phone likes the 802.1xEAP security they are using here. Droid incredible worked just fine on it though.
[Motorola Droid 4] redddog:
Do you have to remove root to apply this?

I wonder why it was posted and then removed? Anyone?
[Motorola Droid 4] DmdStar:
Cuz it is still in soak test, which is confidential. Motorola doesn't want it out there in the wild yet.
[Motorola Droid 4] papi92:
You have to use voodoo root keeper. If you flash the update without voodoo root keeper you will lose root. But motofail still works so you can always reroot
[Motorola Droid 4] DevilDaHusky:
i just got an update today but it downloads 215 not 219.

Sent from my DRIOD 4 Husky Edition
[Motorola Droid 4] The Magician Type 0:
Question:

I updated my original, non-safe system just fine. Kept root, reinstalled safestrap no problems. However, upon switching back to my safe-system it loads the safe-system before the update. I don't know how to reset my 2nd system to match the non-safe system, and I don't dare trying to install the update while using safestrap. Is there anyway to get this updated system to carry over to my safe-system? Or do I need to wait until someone makes a ROM to flash?

Thanks in advance!

Sent from my DROID4 using telepathy
[Motorola Droid 4] kwyrt:
I assume you are running stock GB on your non-safe system then? If that is the case the easiest way I could see to update it to the new software version would be to make a backup of your non-safe system, then flash that to your safe system, just don't wipe data and it shouldn't mess up your current configuration.
[Motorola Droid 4] The Magician Type 0:
Yeah, stock Motoblur on the latest update. I had considered that, but wasn't sure I could flash a non-safe backup to the safe system. I'll give it a try and hope for the best.

Thanks!

Sent from my DROID4 using Carrier Pigeons
[Motorola Droid 4] The Magician Type 0:
So I tried just that, restoring the non-safe backup to the safe system. Everything transfered over, apps, data, etc. Except, the safe system is still on the original .215, not .219...
[Motorola Droid 4] kwyrt:
I don't know then. That was my best guess. Not sure why it wouldn't work. You made a fresh backup of your non-safe system after the update and flashed that, right?
[Motorola Droid 4] The Magician Type 0:
Yes, and I'm confused as well. One would think the ability to transition between ROMs switching GB and ICS, a simple little upgrade would work as well. I guess I'll wait for a ROM version or something, not that I really need this update, I just like being on top of things.
[Motorola Droid 4] redddog:
Does anyone have the 6.13.219.XT894 patch instead of the 6.13.215.XT894 patch that is floating around?

Thanks!
[Motorola Droid 4] The Magician Type 0:
I'm fairly certain the one floating around is the one you're looking for. The instructions from the motorola pdf showing how to update list the .zip as the .215 one. I tried it and now I'm on .219

I think the file name describes the version we're currently on, or the one it is being applied to, NOT the version it actually contains. There is a big misconception going around, please help spread the word.
[Motorola Droid 4] redddog:
OK. I'll give it a whirl.

Thanks, dude.
[Motorola Droid 4] papi92:
That's how it should show. Moto names it that way and you got that by clicking check for update not cheesecake?
[Motorola Droid 4] kwyrt:
The file is named 215 but it is the correct file. For some reason Motorola names their update files according to version you are updating from rather than what version you are updating to.
[Motorola Droid 4] silberware:
I can't get into recovery to install from sd card. When I boot into recovery I just see the exclamation point in the triangle and it stays there. Sorry for being a noob.
[Motorola Droid 4] papi92:
Hold both volume keys in when in recovery to show options.
[Motorola Droid 4] papi92:
If anyone use cheesecake and see if 220 pops up for you. And pull it for me
[Motorola Droid 4] redddog:
Hey guys. Any need for wiping?
[Motorola Droid 4] The Magician Type 0:
I got away without wiping

Sent from my DROID4 using Carrier Pigeons
[Motorola Droid 4] silberware:
verifying update package...

E:signature verification failed

Installation aborted

FML
[Motorola Droid 4] The Magician Type 0:
Do you have frozen bloatware? Or is this a different error?

Sent from my DROID4 using Carrier Pigeons
[Motorola Droid 4] silberware:
Unfroze everything, re-downloaded the file multiple times, same error every time. The OTA fails also and reminds me to install it every hour. Lame.
[Motorola Droid 4] The Magician Type 0:
You followed the directions completely, stock recovery, external sd card, everything?

Sent from my DROID4 using Carrier Pigeons
[Motorola Droid 4] silberware:
Yup, followed the directions to a t. Used voodoo, unfroze apps, stock recovery.
[Motorola Droid 4] vprasad1:
Just a quick confirmation request from those that have applied the 18meg update-- is it a non-destructive update? Or did it wipe your apps and settings?
[Motorola Droid 4] kwyrt:
It won't affect your apps or settings. It's a pretty minor update really.
[Motorola Droid 4] redddog:
Wouldn't deleting certain apps cause a failure?

Make sure you have all the stock apps.

Thanks all for the help. Anyone seen any improvements that the patch addressed?
[Motorola Droid 4] teookie:
NOPE.
[Motorola Droid 4] myfishbear:
i got more stable 4g in nj and fater ui. thits what i noticed
[Motorola Droid 4] The Magician Type 0:
There's a few threads over at Droid Forums about problems with the update. The post in particular at

http://www.droidforums.net/forum/dr...18-cant-install-new-update-4.html#post2087566

Might be of interest. The solution was copying and replacing some stock apks and odexes. If you've followed the directions completely then it must be a system problem and not the installation process.

Sent from my DROID4 using Carrier Pigeons
[Motorola Droid 4] PyroHoltz:
I was new to TB Pro prior to applying this update. I had many apps frozen but did NOT unfreeze them before applying the update. The update went 100% smooth and no issues.

Are we sure that unfreezing is necessary? Maybe only if the update is OTA initialized and not updating manually using recover?

Anyone, feel free to chime in and give your thoughts.
[Motorola Droid 4] Malnodnarb:
I followed the instructions in the Development Thread by Omniuni and it worked like a charm. I was rooted with Safestrap installed. Backed up Root with Voodoo, unfroze my apps. Installed update from SD and voila. Restored my root with voodoo.
[Motorola Droid 4] bdsullivan:
Edit. Wrong place.
[Motorola Droid 4] Montecarlo97z:
i still cant get this to work, can u not instal this while safestrap is enabled and a rom loaded? it fails during verification, nothing removed or frozen...
[Motorola Droid 4] The Magician Type 0:
I don't believe this can be applied to your safe-system. I'm fairly certain it has to be applied to your primary system. I asked earlier if the update could be carried over, my primary is on .219 but my safe-system is on .215 and I don't have a solution.

Sent from my DROID4 using Carrier Pigeons
[Motorola Droid 4] rumgool:
Lost root after OTA update

Hey guys,

I downloaded the OTA (yes OTA not manual) update last week for the soak test. I accepted the OTA update while rooted (and I had safestrap).

My problem is that now my device is not rooted (although i still have superuser.apk). Also, mattlgroff's droid 4 utility will not grant me root either even though it says root successful. Here is what the utility displays.

Motorola universal root script

by Dan Rosenberg (@djrbliss)

Tested on Droid 3, Droid Bionic, Droid RAZR, and Droid 4

Before continuing, ensure USB debugging is enabled, that your

device is in charge only mode, and your phone is connected via USB.

Press any key to continue . . .

Waiting for device...

* daemon not running. starting it now *

* daemon started successfully *

Device found.

Deploying payload...

2101 KB/s (359392 bytes in 0.166s)

Owning phone...

Waiting for phone to reboot.

* daemon not running. starting it now *

* daemon started successfully *

Root successful! Persisting...

remount succeeded

1242 KB/s (22364 bytes in 0.017s)

link failed File exists

4273 KB/s (1867568 bytes in 0.426s)

4686 KB/s (843503 bytes in 0.175s)

Cleaning up...

Rebooting...

* daemon not running. starting it now *

* daemon started successfully *

Exploit complete!
[Motorola Droid 4] papi92:
Wipe data and cache and reroot.
[Motorola Droid 4] rumgool:
Safestrap does not work either... so just do a factory reset?

---------- Post added at 06:19 PM ---------- Previous post was at 05:47 PM ----------

This did not work. I did a factory reset and re-ran the exploit with no luck. I still have superuser.apk in my system/app folder which is read only with a modified date of 2-10-2012 (when i originally rooted my phone). So, I did a factory reset and still no root? Any other ideas?
[Motorola Droid 4] papi92:
Adb push the su binary
[Motorola Droid 4] rumgool:
When I try this:

adb push su /system/bin

I get failed to copy 'su' to '/system/bin/su' : Read-only file system

So, the exploit is not working. So, does this mean Motorola updated something to prevent our root method from working in this latest release, or is this a result of me updating while rooted? I want to say the former, since the exploit is unable to get write access (my superuser.apk modified date is 2-10-2012)
[Motorola Droid 4] papi92:
Adb remount system needs to be put in first before you push
[Motorola Droid 4] rumgool:
Well, I tried running through that process and adb pushing the motofail files and trying to run them that way, but couldnt get write access to remount or /system/bin but then after resetting data/cache I got the root to fail with errors of read only access. I then ran the unroot process and was able to remove my superuser.apk and su binary. I reset data/cache again, and got the exploit to work.

I haz root! Thanks for the help
[Motorola Droid 4] jy3ng4:
Having the same problem. I backed up root with Voodoo, unfroze bloatware, and have stock recovery. The update stops at about 25% then reboots and says "The software update failed!"

No idea what the problem is :/
[Motorola Droid 4] svrnmnd:
I got this update automaticly too, I just clicked install , it didn't work. I have my phone rooted and safestrap installed (although I havent installed a second system yet) Where is the update downloaded to so I can unfreeze my frozen apps and try again? also how would I remove safestrap??
[Motorola Droid 4] The Magician Type 0:
If these work like the Cheesecake app, i think they're stored in your /cache. If nothing else you can just downloaded it to your sd-card from one of the many many topics from here or Droid Forums, Rootzwiki, etc. To unistall safestrap make sure you're on your non-safe system, open the app, and uninstall the recovery.

Sent from my DROID4 using Carrier Pigeons
[Motorola Droid 4] Fuddster:
I received the update OTA about an hour ago.

I have a stock, rooted D4, so I hit the button to update later, ran a TB backup, performed a temp unroot with Voodoo OTA Rootkeeper, then triggered the OTA update manually.

Once the phone booted back up, I went in the settings to verify the system version number, then I opened Voodoo OTA again and restored root.

Thanks to everyone for the easy steps to follow.
[Motorola Droid 4] svrnmnd:
Which one is the non-safe system? I never installed a second system, so if I reboot into safestrap is that how I in install it? Or do I just uninstall by opening the safestrap app on my menu? I have never dealt with safestrap on previous phones sorry
[Motorola Droid 4] kwyrt:
Did you actually install safestrap recovery or just the safestrap app? The whole purpose of the safestrap app is just to install safestrap recovery. So, if you installed safestrap recovery via the safestrap app, you will open the safestrap app on and uninstall safestrap recovery. If you never installed the recovery than you don't need to worry about it. As for manually installing the update that would need to be done through stock recovery.
[Motorola Droid 4] azrael293:
Does anyone have the stock apk files for backup assistant?

I keep failing the update because I had deleted the backupassistantclient.apk file. I assume I'll likely need all of the original stock apps but I figure I'll go step by step. I am attempting to unzip them from the stock rom that is in the dev forum. If anyone has any other ideas please let me know.
[Motorola Droid 4] tpjets62:
Same here....I let my phone download the file, then I postponed the install. Did a temp. unroot with Voodoo then let the update run. Restored root and all is well. So far no problems but I'll have push it a few days to see what happens.
[Motorola Droid 4] bdsullivan:
If you apply the update in stock recovery it will state where the update is getting an error. Example: error sideload. Build.prop/bunchofnumbers,bunchofnumbers.

That was the error i was getting until rumgoul posted an un-modified build.prop then i switched it with mine and update went perfectly. There are instructions in the developer section on how to update via stock recovery as well as an un-modified build.prop.
[Motorola Droid 4] wabyrd:
How can I reset the data/cache if I can't get into Moto Recovery using the tool?

I'm kind of in a state between root and unroot. Here's the whole story. I had a rooted device, but it failed to check for the updates. I did a factory reset and was able to OTA the update. I tried to use Rootkeeper, but it didn't work. I tried to use the Droid 4 utility. It says that root worked, but when I try to use a "root" app, it doesn't work. Rootkeeper shows a checkmark in "Device rooted", but no checkmark in "root permission granted". When I look at the superuser log, it shows all requests denied except for "shell" was approved 3 times.

I've tried to boot into the Moto Recovery using the Droid 4 Utility, but after it reboots, it comes up to an error screen with a triangle and exclamation point.

Any tips?

I've already done a system reset, so I'm ok with wiping the device again.

Thanks!
[Motorola Droid 4] rumgool:
Fastboot/Stock Recovery

To reset the data/cache you need to load into fastboot recovery. To do so:

1. Turn off your Droid 4

2. Power on your Droid 4 while holding both volume keys in

3. Your Droid 4 will boot into Fastboot (black and whit menu)

4. It sounds funny, but press volume down, and then volume up and the screen will change to the motorola dual core logo(like 30 seconds), then load the android with a caution sign.

5. At the android caution screen, simultaneously press the volume up and down buttons.

6. Voila, you are in stock recovery, and you can wipe data/cache, or apply OTA updates manually. The volume keys control "UP" and "DOWN", whereas the power button acts as "ENTER"

---------- Post added at 04:54 PM ---------- Previous post was at 04:52 PM ----------

Basically what I did though, was mess around until I got the unroot exploit to make my superuser.apk dissappear. That is the key, once you are completely unrooted with no superuser.apk, you should be able to run the root exploit again.
[Motorola Droid 4] wabyrd:
Thanks for the fast response. That seems to have fixed it. Waiting for the wipes now.

I had a hard time getting into fastboot...maybe it's just my fat fingers...
[Motorola Droid 4] rumgool:
LOL

Yea, I'm sure there is another way to get into fastboot using the physical keyboard like on the Droid 2, but I am not aware of the key combos.
[Motorola Droid 4] hockeygod6:
Can anybody give me a copy of the preloaded.apk? Something is wrong with mine and I think its preventing me from installing the update successfully.
[Motorola Droid 4] rumgool:
LOL maybe I should just upload my whole system folder

Here ya go preloaded.apk attached

This is post update though.... so be weary... the last modified date was after the update too
[Motorola Droid 4] Montecarlo97z:
mine failed because of my build.prop file so maybe everyone that is failing the update should replace their build.prop file
[Motorola Droid 4] jy3ng4:
How did you modify your build.prop file? How/when did it notify you that the build.prop file was the culprit? Mine isn't giving me any message like that...it just reboots after 25% and then gives me the "update failed" message.

The only thing I can think of that may be causing mine to fail was that I ran the V6 Supercharger script about a month ago...no idea how to reverse it though :/
[Motorola Droid 4] Montecarlo97z:
use root explorer or another file explorer and allow root access than mount system as rw, find system folder and scroll down till u see build.prop and replace it with this file found at the bottom of the page http://xdaforums.com/showthread.php?t=1608866&page=3
[Motorola Droid 4] rumgool:
I wonder.... when you run the exploits, are you making sure your phone is in charge-only mode, and the screen is unlocked and on. Also, when it reboots, make sure to unlock your screen as well. I know it sounds silly, but hey, I felt it was hopeless in your situation and got root back, so GOOD LUCK!
[Motorola Droid 4] wabyrd:
Yeah, I've double checked that it's in charge only and I unlock as soon as it reboots. I'm still working at it. I'm determined to get this done tonight!

Thanks for the pointers.

---------- Post added at 06:24 PM ---------- Previous post was at 05:30 PM ----------

I GOT IT!!!

It took a while, but I finally got the Superuser off of the phone! Rerooting now!

I got into ADB and finally didn't get rejected for file permissions. Then did the usual

su

mount -o rw,remount /dev/block/system /system

rm /system/app/Superuser.apk

rm /system/xbin/su

rm /system/bin/su
[Motorola Droid 4] Stensin:
Hi, I'm having problems getting the update on my rooted Droid 4. I'm pretty sure it's because I screwed with my build.prop file though. I wanted to get the Order and Chaos app and disguised my phone as a Droid 3 so I'd be able to download it. Now I could care less about it..

I first factory resetted my phone and on-board system memory, in hopes that this would restore the original build.prop file. (I'm a bit of a novice.) When this didn't work, I re-rooted my phone.

I went and replaced my current build.prop with rumgool's build.prop (in the Motoblur Update 219 thread.) (i.e. I carfeully copied their build.prop and pasted it directly into mine with no changes to [the stock].)

I then used the VooDoo OTA app to back up my root and temporarily un-root my phone.

Next I downloaded and saved Blur_Version.6.13.215.XT894.Verizon.en.US.zip to my micro-SD card.

I restarted my phone, and booted into recovery mode.

When I select the option to apply the update from sdcard, and select the file, I get this error message:

I assume I need to change the ro.build.fingerprint value in my build.prop file, but I could be wrong.

Thanks for any help in advance!
[Motorola Droid 4] jy3ng4:
Did you fix the permissions?
[Motorola Droid 4] Stensin:
I'm new to this, what do you mean "fix the permissions?" My phone is rooted, so is this something that has to do with Superuser, or the build.prop itself?