It's been awhile since I did anything much with my phone and so I am a bit out of date on what is available these days, especially with the Bionic, I could use a little advice and some recommendations. I used to be into phone modding big "back in the day" with my DX but not so much anymore.
Firstly, I am not a nub and I spent a few hour's online reading before deciding to post anything so I am not trying to be spoon fed here, but I am a bit stuck here and I am not sure what to do. Anyway, I got the phone with 886 and rooted it, installed my stuff and have been using it since. Been having some issues with the phone (still do) so I decided to update it. I made backups via clockworkmod and did the forever root (where you edit with SQL editor) and ran the official update. The OTA said I would be getting 902 however after it installed I was on 893, so I assume I needed to be on 893 before I could go to 902, however when I try to go to 902 I get failed update.
I have tried two ways of updating.
1a. Updating to 902 from phone
2a. Updating from stock recovery using the 902 update file, named Blur_Version.5.5.893.XT875.Verizon.en.US.zip
1b. When updating from phone it downloads, "installs", phone reboots to "update failed".
2b. When installing update from stock recovery I get "package verification failed bla bla myverizon.apk".
So, I figured it was apps and such I either removed, froze, etc. I unfroze and restored any stock apps and still myverizon.apk failed. I read online about putting myverizon.apk in /system/apps however that did not work.
My goal is to keep my phone as is, I cannot really afford to reset it at this time. I feel what I need is the proper myverizon.apk file and someone with more knowledge than myself to tell me exactly what to do.
Any help is greatly appreciated and thank you in advance.
Go here and use Timmy10shoes files if needed...http://androidforums.com/bionic-all-things-root/480176-how-flash-5-5-893-5-9-902-rsdlite.html
Thank you but this does a full wipe, I am just trying to update to 902.
This will get you to 902 and Timmy10shoes file will prevent a wipe of the sd card.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
Related
Hey everyone,
Sorry to be creating a new topic on this but I have literally spent the last 3 hours trying to figure this out and have searched the entire forum looking for answers and couldn't find any.
Here's the deal. I was following this guide on rooting my phone and got all the way to the image part. I was going to install this build which mentioned I needed the DangerSPL. Went ahead and followed this guide on how to install the DangerSPL and got to the flashing DangerSPL part, where I was supposed to install the CM 5.0. (Note: When trying to install the CM 5.0 I also get the e: can't find update script as well)
There's where the problem happened. After getting that in my phone will not go any further than the T-Mobile G1 screen. It just freezes there and there it stay. I tried updating the CM 5 but it always gives me the message e:can't find update script, and that's downloading straight from the website and then renaming it to update.
So as of right now I don't know where to go, I'm pretty stuck at this point. I don't know if I should be doing something to prevent the can't find the update script message or what, or how to get past the G1 screen.
Any help will be deeply appreciated as I'm stuck without a phone at the moment.
Thanks a lot in advance.
Edit:
Update: By returning to "factory" settings I was able to at least start up the phone, so that's a positive. Negative is that it is now a 1.0 version of the droid, so I would much rather be able to install something slightly better but I still have been running into the error can't find update script on several different builds.
Ouch.... I feel your pain... 1.0 is pretty old. Few questions before troubleshooting:
1. What phone do you have: G1, Dream, Roger's Dream.. etc
2. What does it say in your H/F boot (power up using camera and power button and copy 4 lines that you will see)
3. What build are you on right now (Menu-Setting-About phone)
Once we have that - we can proceed.
Edit:
After going through the steps again as I restored factory settings the rooting and upgrading finally did work. Go figure.
Thanks for the help, it was really appreciated.
A few weeks ago I rooted my X and ran the manual deodex method posted on the site. Phone ran great, I installed clockwork recovery and made a few backups. after installing a rom and not being able to get back into the recovery, I had to flash the phone with the 2.2 full SBF. This leads to my questions
1. After I SBF'd I was able to recover my applications and my data was all on the SD card. however I have a few applications that when run will close and give me an error message stating that the "application unexpectedly quit" I can duplicate the issue most when attempting to search the a forum through the XDA application. I am sure I failed to wipe data and cache before I recovered the stock OS, could this be the cause, any ideas?
2. I have re-rooted my phone but I have a question about deodexing again. I understand that motorola is in the early stages of working on an update to fix reported issues with 2.2, I also believe that they will use this opportunity to update the bootloader version. is there a way to disable the OTA updates? I am concerned about bricking my phone if an update is release and I am deodexed, what is the worst that could happen?
Sorry for the post, I am technically inclined but am still learning the android OS, any help is very much appreciated.
If you run a rom either aosp or blur you can avoid the ota that's end only way I know to avoid it
Sent from my DROIDX using XDA App
thanks for the response, I read a few places that clockwork recovery blocks OTA updates from installing, but I am having a hard time nailing down a definitive answer.
From what I understand Droid X SBF files do not wipe data like other phones. I recently had to SBF but kept getting stuck looping at the droid eye. I booted into recovery and did a factory reset and all worked out just fine. I know it's not your exact problem but it still might be worth it to try.
As for not getting OTA updates other than doing a custom ROM I can't help you there, sorry.
I rooted, bootstrapped, and flashed clockwork with rom manager. I am currently running liberty3 v2.0 and I am on .886. Is it worth updating to .901? And if so how do I do it? Step by step instruction will help. Thanks
Read around. Just to give you a hint:
There is currently a thread on the first page of the "Droid Bionic General" section of this forum (same area as this thread) that has a list of step by step instructions. To give you an even bigger hint, it has NOOB in the title.
whoops! my bad.
Edit: Just checked out post. Its for .893, but is it basically the same way? In other words, could I just run R3l3AS3DRoot in order to restore to stock, update to .901 and then reinstall liberty. Also, is it worth updating? Thanks.
901 radio is flawless for me never dropped signal phone went from 5 starts to 10 stars however I am stock plan on rooting after I learn a bit mire
Sent from my DROID BIONIC using XDA App
I have no experience with 886 since my phone came with 893 pre installed. Here's my general advice.
1) Read more.
2) Get rid of Bootstrap and install Safestrap. Especially since you're a noob, this is like an insurance policy. Again, refer back to #1.
3) If you want to get to 901, my best guess would be to FXZ back to stock, and then get the OTA (over-the-air) update to 893. I've never done that, so I can't be more help. But there's definitely instructions somewhere. Let me know how that goes.
EDIT: Maybe try this post: http://forum.xda-developers.com/showthread.php?t=1408522 Disclaimer: I haven't tried it, have no idea what I'm talking about, but it looks promising.
EDIT2: Or maybe this could help? http://www.mydroidworld.com/forums/droid-bionic-forum/10577-bionic-path-saver-1-click-method.html
Many non Noobies seem to be running across the same problems with rooting ZV8 updates. The answers are spread across three different threads so it seemed worth putting them all in one place up front.
First, big thanks MT for putting all this up so quickly.
If you are still on ZV7, first try
http://forum.xda-developers.com/showthread.php?t=1566729
However, I and many others have not been able to get an over the air update (step 6) to succeed and/or get a lot of permission denied errors in the All in One batch processes. If you can't get an OTA update to succeed first try
Originally Posted by drt054
use a terminal emulator, type in
su <enter>
echo 'ro.kernel.qemu=1' > /data/local.prop <enter>.
OR
Use root explorer to create /data/local.prop and type ro.kernel.qemu=1 then save it.
If the OTA update works, you're good, continue with MT's instructions, but SKIP OPTION 1 "Prepare for Update"
If, like me and many others you still can't get an OTA update to succeed Alternative 2 is the LGPST method here
http://forum.xda-developers.com/showthread.php?t=1466655
Again, the key is to not loose Clockwork Recovery. As long as you have done the create local.prop step and not done the All in One Option 1 "Prepare for Update" The LGPST ZV8 push will not erase Clockwork Recovery. Then you have ZV8 with Clockwork Recovery and you can get MT"s Broken Out v 1.1 here
http://forum.xda-developers.com/showthread.php?t=1577423
Or get back to a nandroid backup or rooted ZV7 to start over
http://forum.xda-developers.com/showthread.php?t=1348637
If you loose Clockwork Recovery or otherwise run into trouble, the sure fire way to get back on track is to go back to ZV7 and start over. Personally, reading through all the forums and despite several attempts, I was never able to get an All in One batch process to root ZV8, always permissions denied. But I was just trying to ZV8 with Clockwork Recovery to get to Broken Out anyway.
UPDATE 4/3/12
Another option for regaining CWM if you use LGPST
http://forum.xda-developers.com/showpost.php?p=24411050&postcount=83
MT is looking for ZV7 testers for an easy update
http://forum.xda-developers.com/showpost.php?p=24416908&postcount=86
I'm more than a Noob, but far from an expert, so if this contains errors or doesn't deserve it's own thread, feel free to suggest removal!
Cutterstark said:
If, like me and many others you still can't get an OTA update to succeed Alternative 2 is the LGPST method here
http://forum.xda-developers.com/showthread.php?t=1466655
Again, the key is to not loose Clockwork Recovery. As long as you have done the create local.prop step and not done the All in One Option 1 "Prepare for Update" The LGPST ZV8 push will not erase Clockwork Recovery. Then you have ZV8 with Clockwork Recovery and you can get MT"s Broken Out v 1.1 here
http://forum.xda-developers.com/showthread.php?t=1577423
Click to expand...
Click to collapse
Appears that you DO lose CWM with LGNPST. I just tried your method and I no longer had CWM. Maybe you missed a step in the OP? Otherwise, I lost CWM when I pushed ZV8 TOT. Also, just so you know, I did check/test CWM just prior to pushing and it worked just fine.
-Cybie
EDIT: I wanted to clarify and emphasize "Appears" in my reply above. Your method may work perfectly fine, but I had nothing but troubles getting things to work...
is this a bad place to ask how im supposed to go back to zv7? i dont have cwm anymore....
help me out
ejammer said:
is this a bad place to ask how im supposed to go back to zv7? i dont have cwm anymore....
help me out
Click to expand...
Click to collapse
See this Link... All the tools and instructions.
http://forum.xda-developers.com/showthread.php?t=1337386
Be sure to follow the part with which LGNPST Tool Part to install first!!!
-Cybie
yes am back to zv7 now trying to figure out how to do the all in one update steps from mt. it seems in the "prepare for update" steps it fails on copying local.prop or whatev its called.
ejammer said:
yes am back to zv7 now trying to figure out how to do the all in one update steps from mt. it seems in the "prepare for update" steps it fails on copying local.prop or whatev its called.
Click to expand...
Click to collapse
That is the same problem I had. Try the copy local.prop option described above and bypassing the prepare for update.
better yet, contact MT, he is working on an easy solution and needs ZV7 testers
http://forum.xda-developers.com/showpost.php?p=24416908&postcount=86
what if I am on zv6 still?
Son's Revo asked bout v8 OTA today. Didn't want to do it as I figured it would lose root. Currently we are on v6 and rooted (via AIO). Never went to v7, and now with v8 am trying to figure out how to get to v8 and keep root.
Do I need to get to v7 first prior to trying to get to v8 while keeping root or is there a way to go directly to v8 while maintaining root?
I posted in http://forum.xda-developers.com/showthread.php?p=25188375#post25188375 about trying to get to stock v7 not working for some reason so won't go into that here, but thought I would ask about a way to get to v8 with root WITHOUT having to go to v7 first.
I have a solid nandroid (which I just had to use to get a working phone again) I can use so don't mind testing things.
Thanks for any ideas...
***EDIT***
I went ahead and went to stock v7, rooted, and followed the v7 to v8 (save root) process MT created and all is well.
Hey guys.. My System Version is listed as being 6.13.215.XT894.Verizon.en.us. (This phone is about a week or 2 old for me) I have installed safetsrap recovery just to see how it works etc and have successfully installed the Eclipse port on the non-safe system. Now that I am done having fun with that, I would like to upgrade my system to newer leaked versions. My question is this: Should I uninstall safestrap before attempting to flash any of the leaked updates? How should I go about removing safestrap the "best" way? Also could someone please enlighten me with the correct "order" of these releases? EG: 6.11.200, 6.11.202, 206 etc. I guess I'm confused bc my system version starts with 6.13 instead of 6.11. Any help much appreciated!
I'm in the same boat as you, safestrap w/eclipse setup and I think I want to just switch to ICS 211
Pretty sure there are 2 methods, one with fastboot, and one with safestrap.
Fastboot method (droidforums.net/forum/droid-4-roms/212634-simplified-211-update-guide.html) definitely requires you to uninstall safestrap, but I think that automatically happens when you flash w/stock 219.
Safestrap method (droidforums.net/forum/search.php?searchid=4780372) allows you to just use a 211 ICS rom. But, I'm not sure if you already have to have done the fastboot ICS, I think you may have to fastboot ICS then install safestrap and safestrap into 211 ICS from 206 or 208 ICS.... Anyways, that's about where I am right now, trying to figure out if I safestrap to a 211 ICS rom from my current stock 219 GB, will it brick my phone. :/
---------- Post added at 12:46 PM ---------- Previous post was at 12:38 PM ----------
Oh also (droidforums.net/forum/droid-news/212864-another-ics-leak-here-droid-4-maybe-closer-ota.html) says that "212 ICS should be leaked soon". You may want to just hold tight, lots of new leaks means that something big (and easy to install for noobs like me ) may be coming soon .
The adventure continues...
Thanks for the quick response man... I'm glad to see I'm not the only one in this situation! I've been "creeping" on this board for 2 years now, (which I can't believe how fast that time went by) and thought it was about time that I start posting etc... you know what I mean, I see that was your 4th post so, that makes 2 situations where we are in the same boat! Thanks for the links brother I have actually read those, but need to checkup on them again... ALSO, my system downloaded an update the other day, (OTA) and was automatically going to install it (I clicked on download, thinking it would just download and wait for me to do the install manually like i have been used to in the past...) So, I tried to interrupt the download by throwing my phone into airplane mode really quick and then forcing a shutdown. Next time I turned on my phone I end up seeing the "Green Android with a triangle" screen, and a progress meter.. and I KNOW what that means. Something was flashed automatically by the phone. I got nervous, but my phone booted up perfectly, and I still had root, along with safestrap intact. I'm still a bit confused by what might've happened, but am relieved that my phone is still working perfectly... strangeness. I'll update this thread w any more info I can find. Thanks again!
Time out guys! First off, you cannot flash the ICS leaks in safestrap. The leaks are updates, not full ROMs. Second, you cannot flash a ROM based off the ICS leaks in safestrap unless you update you stock system to an ICS leak first. Well, you probably could, but it wouldn't boot. If you are on GB .215 you will need to update to .219 first. If you are on GB .219, and have not installed safestrap, you should be able to flash the an ICS leak via stock recovery without fastbooting. If you have installed safestrap, I believe you have to fastboot using the .219 file since safestrap changes something in the build.prop that will cause the leak update to fail.
The Optimizer said:
Thanks for the quick response man... I'm glad to see I'm not the only one in this situation! I've been "creeping" on this board for 2 years now, (which I can't believe how fast that time went by) and thought it was about time that I start posting etc... you know what I mean, I see that was your 4th post so, that makes 2 situations where we are in the same boat! Thanks for the links brother I have actually read those, but need to checkup on them again... ALSO, my system downloaded an update the other day, (OTA) and was automatically going to install it (I clicked on download, thinking it would just download and wait for me to do the install manually like i have been used to in the past...) So, I tried to interrupt the download by throwing my phone into airplane mode really quick and then forcing a shutdown. Next time I turned on my phone I end up seeing the "Green Android with a triangle" screen, and a progress meter.. and I KNOW what that means. Something was flashed automatically by the phone. I got nervous, but my phone booted up perfectly, and I still had root, along with safestrap intact. I'm still a bit confused by what might've happened, but am relieved that my phone is still working perfectly... strangeness. I'll update this thread w any more info I can find. Thanks again!
Click to expand...
Click to collapse
Yup, same here, I'm just taking as much info in right now as possible. I think our options are eclipse, stock 219 with frozen apps, or ICS. Oh if you use stock at all, I'd recommend upgrading to 219, I think that was a major update, my battery life has just about doubled... then again I only had my phone for about a week before upgrading, and about 3 weeks total now.
kwyrt said:
Time out guys! First off, you cannot flash the ICS leaks in safestrap. The leaks are updates, not full ROMs. Second, you cannot flash a ROM based off the ICS leaks in safestrap unless you update you stock system to an ICS leak first. Well, you probably could, but it wouldn't boot. If you are on GB .215 you will need to update to .219 first. If you are on GB .219, and have not installed safestrap, you should be able to flash the an ICS leak via stock recovery without fastbooting. If you have installed safestrap, I believe you have to fastboot using the .219 file since safestrap changes something in the build.prop that will cause the leak update to fail.
Click to expand...
Click to collapse
Thanks for clarifying that ^^, kwyrt, I've read some of your other posts they are always quite informative!
Glad I could help! There are a LOT of nice, helpful people in these forums. Just keep asking questions! Doing some of this stuff can be nerve wracking even if you know what your doing. I actually, finally, got up the nerve to jump on the ICS leak train last night. If you decide to take the leap, I highly recommend using jsnweitzel's Droid 4 Utility located here: http://forum.xda-developers.com/showthread.php?t=1714596. Made the process much easier than it has any right to be.
Android 4.0.4 flash Success! =)
So I decided to take the leap last night... first thing I did was every way of factory resetting I know how to do hehe. (Privacy, factory reset under settings, then a data and dalvik clear in recovery) Downloaded the GB219 file, put it on my SD, fired up the Droid 4 Utility (thanks to everyone who contributed!) and had no problems at all upgrading. I wasn't worried about root so I skipped the OTA rootkeeper process. Next I needed to get to an ICS build. Again, I used the Droid 4 utility.... only difference being that we had to flash the boot.img file first.. (ICSFIX.img). On my first go, I successfully flashed the new boot.img (ICSFIX), but then got a sig verification error when trying to flash the OTA zip. ****. Soft brick at 2AM... heh. at least I still had plenty of time. Re-DL the OTA file, copied it over again and repeated the entire procedure, this time with success. Really Glad I decided to upgrade! Thanks guys!