So I used Oneclickroot 2.3.0 a while back, which did NOT remove asphalt or nascar or anything else that I know of and i did check the run.bat file...saw nothing regarding any removal of files.
I undid the root in order to apply the update and I still get an error...does anyone know what can be wrong? Here is the error:
Verifying current system...
assert failed: apply_patch_check ("/system/build.prop", "6d74575d0a7391c3578d907fc43f9485f8d93032", "68a96e00d1e9b40bad1491dbf63822e7be86fca6")
E:error in /sdcard/update.zip
(status 7)
Installation aborted.
Ideas, anyone?
Thanks
Try renaming the file to just "update" and not update.zip
Please update us about whether this solution works and good luck. Pretty sure I'm going to be in the same situation.
Unfortunately this did not work. It is looking for update.zip. not update.
Anyone else? Please throw some ideas!
OdIN > DI18
Odin
Odin back to stock Di18 and reapply the update zip it will work fine from there.
Top Nurse said:
OdIN > DI18
Click to expand...
Click to collapse
The oneclickroot didnt delete anything though. The error is saying that it is the update.zip...or is that normal? Is there any way to figure this out so that I do not have to start from scratch with everything on my phone?
Redownload the zip. That was a problem I had, and I rooted with cwm 2.5...
Sent from my SPH-D700 using XDA App
damicrobe said:
Redownload the zip. That was a problem I had, and I rooted with cwm 2.5...
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I did this many times, I even downloaded it straight from my phone browser to single out any problems with a usb cable...still nothing.
Anyone have an alternative link to it, besides that thread thats entitled direct google download?
Check for the existance of /system/build.prop
Lcstyle said:
Check for the existance of /system/build.prop
Click to expand...
Click to collapse
You may be on to something. I once DID modify
windowsmgr.support_rotation_270=false
to true, using root explorer. I just changed it back.
Can someone please copy/paste the contents of this file to me?
Also, if there's a build.prop.bak file in the /system directory, would that make a difference?
Elixis said:
You may be on to something. I once DID modify
windowsmgr.support_rotation_270=false
to true, using root explorer. I just changed it back.
Can someone please copy/paste the contents of this file to me?
Also, if there's a build.prop.bak file in the /system directory, would that make a difference?
Click to expand...
Click to collapse
The plot thickens! Even though I've never made such a change, I'm still interested to see how you do so I'm going to try and help you out when I get to a real computer shortly. EDIT: here it is, stock dated 9/18/10 attached.
Were you at least able to use your phone even after these failed upgrades? It'd help settle things in my mind if the answer's yes.
I did the same thing and the DI18 -> EB13 update failed on my phone 'til I reverted the build.prop file back to original ( you did save build.prop.orig didn't you )
After I restored the file ot original the update completed and now I'm on EB13 waiting for EC05.
JDotScott said:
I did the same thing and the DI18 -> EB13 update failed on my phone 'til I reverted the build.prop file back to original ( you did save build.prop.orig didn't you )
After I restored the file ot original the update completed and now I'm on EB13 waiting for EC05.
Click to expand...
Click to collapse
Excellent news! That means I hopefully stand a good chance of success. Anyway, the file's above for Elixis.
Thanks! How exactly do I apply this file and get rid of the old one? Do I need to root again?
Elixis said:
Thanks! How exactly do I apply this file and get rid of the old one? Do I need to root again?
Click to expand...
Click to collapse
I'm far from the biggest expert here but I think you probably would, yes, then do a copy/paste with the right file explorer. I use AndExplorer and it can see the root of the phone FS (that's how I got the file actually).
My questions to you and others are:
1) is the phone still OK after a failed update.zip process
and
2) is it really necessary to UN-root in order to make the update work? (whether or not you have to root again after it's done)
Yes, the phone DOES still work after a failed update process. It never started to fully undo the file....the verifications failed.
DroidApprentice, thanks so much for the build.props file...that definately helped something =]
however, I now face a NEW error when trying to install the update:
"BML:Boot: (then a bunch of random numbers and letters)
Status 7.
Any ideas on what this is?
Phone still works after this error.
I tried this both while rooted and unrooted.
Edit: I found a thread on sdx, where Firon says that you need a stock kernel to flash a stock update. The oneclickroot said something about the kernel when it installed, but doesnt it put everything back to normal when you undo it? Is there an easy fix for this, if this is the cause?
Whew, this just gets more interesting if not frustrating, but at least you're not "soft bricking" your phone.
It's funny but I never thought One Click Root did ANYTHING to the kernel. I guess my reading about it or knowledge of it isn't as comprehensive as I thought.
I'd like to continue helping you research this issue because, like you, I would prefer not to use Odin unless I have no other choice.
Elixis, I just realized! You may have been on EB13, the first "official" Froyo update, or another ROM entirely.
I am on DI18 and that's where my build.prop file came from, a rooted with OCR DI18/Eclair phone. That may matter and just wanted to make sure you were clear on that since I'm guessing other versions may have different build.prop files which could affect the update process.
I'm a noob but not that much of a noob....lol. I'm on DI18, not EB13..
Related
File 1 http://android.clients.google.com/packages/ota/tmobile_opal/894fb8631db9.hboot-1.33.0013.opal.zip
File 2 https://android.clients.google.com/...59adc603a3.signed-opal-ota-60505.e059adc6.zip
File 3 (Still Not sure what this file is)
https://android.clients.google.com/...17d.signed-opal-FRG83-from-DMD64.e3671133.zip
Here are the correct downloads. This update only works on the Original My Touch 3G. Not the My Touch 3G 3.5 or Fender Version.
I took these instructions from Smapdi's Post
Renamed 894fb8631db9.hboot-1.33.0013.opal.zip to update.zip and placed it into the root of my SD card. Rebooted into recovery and flashed it (Turn on with Home then Power Key to boot into recovery). The process restarted the phone a few times (DO NOT TOUCH THE THING ONCE YOU START THE FLASH!!!!!) and eventually booted into 1.6.
I rebooted into fastboot and saw HBOOT was now 1.33.0013 :-D
I then took e059adc603a3.signed-opal-ota-60505.e059adc6.zip and renamed it to update.zip and put it into the root of the SD card deleting the previous file. Repeated the same steps as before and the phone did the whole restart itself a few times thing and eventually booted to 2.2!!!
Great work guys!
Thanks for everyones help I hope you enjoy Froyo 2.2.
Stingerrray
Stingerrray said:
File 1 (I Think) https://android.clients.google.com/...17d.signed-opal-FRG83-from-DMD64.e3671133.zip
File 2 (I Know) https://android.clients.google.com/...59adc603a3.signed-opal-ota-60505.e059adc6.zip
The downloads worked for me can someone confirm that theses are the correct files. And maybe help with installation.
Thanks "Phateless"
Stingerrray
Click to expand...
Click to collapse
I do concur, the Philly Cheese Steak is quite delicious, however I find that nothing beats a good Cheeseburger!
Which one is which?
And do they need to be flashed in a specific order?
File one is new. File 2 is the one that has been out for a couple of days. I'm not sure on the install will test soon.
Stingerrray said:
File one is new. File 2 is the one that has been out for a couple of days. I'm not sure on the install will test soon.
Click to expand...
Click to collapse
ill go ahead and test this aswell, so tech i should flash file 2 then file 1 since that is the order they were released in?
Foo_Blyat said:
ill go ahead and test this aswell, so tech i should flash file 2 then file 1 since that is the order they were released in?
Click to expand...
Click to collapse
actually the I believe the first file is the spl and would be flashed first. Be careful.
XfooYen said:
actually the I believe the first file is the spl and would be flashed first. Be careful.
Click to expand...
Click to collapse
i thought file 1 should be flashed first aswell but to me it looked like the 2.2.1 update since theres a "FRG84-from-DMD64" line in the code.
anyone else care to maybe back that assumption up or throw in your own 2 cents, wouldnt mind a few opinions before i flash these files.
Both downloaded, both have been put onto the root of my sdcard. Just waiting on a guiding light before i boot into stock recovery and flash
I also have the files ready but I dont have the guts to flash. I barely use the MT3G lately but I dont want to risk a brick.
negative
Good news is the phone doesn't brick after trying to flash the first file. Bad news is it comes across an error. Apparently this is for a different phone. I got the error "E:Error in /sdcard/update.zip (Status 7)" with a bunch of other gibberish about buildprops before it ..
hope this helps someone ..
has anyone tested these file yet with success?
PulldOvr said:
Good news is the phone doesn't brick after trying to flash the first file. Bad news is it comes across an error. Apparently this is for a different phone. I got the error "E:Error in /sdcard/update.zip (Status 7)" with a bunch of other gibberish about buildprops before it ..
hope this helps someone ..
Click to expand...
Click to collapse
if your sig is correct, you are in the wrong forums, no **** its "apparently for a different phone"
PulldOvr said:
Good news is the phone doesn't brick after trying to flash the first file. Bad news is it comes across an error. Apparently this is for a different phone. I got the error "E:Error in /sdcard/update.zip (Status 7)" with a bunch of other gibberish about buildprops before it ..
hope this helps someone ..
Click to expand...
Click to collapse
I got the same error message and installation aborted. I tried file #2 first. Rebooted and went back to normal. Mytouch 3g stock.....
Same thing happened when I flashed #1 .....
Foo_Blyat said:
if your sig is correct, you are in the wrong forums, no **** its "apparently for a different phone"
Click to expand...
Click to collapse
Before you continue being an ass had you thought about he is someone that upgraded from a mytouch 3g to a vibrant and still has his old mytouch? That is exactly what I did and I am still trying to update my mytouch.
Foo_Blyat said:
if your sig is correct, you are in the wrong forums, no **** its "apparently for a different phone"
Click to expand...
Click to collapse
My Vibrant runs off MT3G roms ...
On a serious note .. I have an original MyTouch 3g, a Cliq, a G1, and a Vibrant ... usually just lurk around these forums and try not to intervene too much because people are quick to become trolls on this site .. then they complain when no one will help them .. gee i wonder why ... learn to be a little nicer, and maybe we can get some work accomplished as a whole ...
and just to clarify, I tested this on an original MyTouch 3g, 1.33.006 SPL, (stock) and unrooted DMD64 build.
This made me think that a "...*** from DMD646" update file would work. I'll be sure to keep my testing to myself so i can avoid trolls like you.
Don't get your panties in a bunch...
I already tried 1.5 -> 2.2.1 and both builds of 1.6 -> 2.2.1, doesn't work in any order
I've tried to update with both files no luck. They are definitly part of the update. I did notice from an earlier post with photos that one file was looking to the system cache file for the other file. So just a thought maybe both files need to be in place before the update can take place. Maybe this could be the problem. Any thoughts on this?
Stingerrray
Sent from my T-Mobile G2 using XDA App
I thought that the first update was supposed to be 300-400kb? Where did you discover this link out of curiosity?
I saw the file name in another post with a view of a botched upgrade due to root. put the file name in the url for the other update and it was a valid url.
Sting
Sent from my T-Mobile G2 using XDA App
The post was here.
http://forum.xda-developers.com/showpost.php?p=8687201&postcount=175
First off any time you want to test if a file is legit or not ( coming from htc/google ) you can just test the keystore via command prompt if the java development kit and runtime is in your system path. Don't remember the code off hand.
Second I would really suggest either using someone elses update script or at least replace/delete most of it. As well as install su and busybox. Because it won't run in a custom recovery.
Enjoy if you can!
Today I installed my first rom, it was called dl09_supah_clean_04. That worked ok but I could not receive text messages. I thought maybe I'd try another rom. So I downloaded one called hamsters rom. Once I booted the phone up with that rom I got a bunch of errors. So I restarted and now get nothing but the samsung logo flashing. I go into recovery mode, click on update.zip to load clockwork recovery and get a message saying:
e:can't mount /dev/block/vold/179:9
(no such file or directory)
e:can't mount sdcard:update.zip
Installation aborted
I'm just wondering if I am screwed here. I'm about to plug the sdcard into my computer and copy update.zip again in hopes of getting clockwork recovery to work.... just wondering if anyone has any ideas in case this doesn't work.
You need to put it on the phones internal sd card plus sometimes you need to put text message setting yourself like message centres number .
Sent from my GT-I9000 using XDA App
Is this a troll?
mdisaac said:
Today I installed my first rom, it was called dl09_supah_clean_04. That worked ok but I could not receive text messages.
Click to expand...
Click to collapse
That's because you have to install a DL09 kernel and modem as well.
I thought maybe I'd try another rom. So I downloaded one called hamsters rom.
Click to expand...
Click to collapse
How clueless are you?
That's a i9000 ROM. Or Captivate port.
Every single flashing thread warns
DO NOT FLASH ANYTHING NOT SPECIFICALLY FOR THE VERIZON FASCINATE
You flashed a GSM ROM onto a CDMA phone. That's just asking for a brick.
Now download this (and since you can't figure obvious things out, flash it into *PDA* of Odin, NOT NOT NOT NOT NOT "phone"), and pray it works.
THANK YOU, THANK YOU, THANK YOU!!
My phone is back and working on the stock rom. I am definitely clueless when it comes to this but I am not giving up. I am going to get the dl09_supah_clean_04 rom working. I'll be more careful this time though.
Thanks again!
s44 said:
Is this a troll?
That's because you have to install a DL09 kernel and modem as well.
How clueless are you?
That's a i9000 ROM. Or Captivate port.
Every single flashing thread warns
DO NOT FLASH ANYTHING NOT SPECIFICALLY FOR THE VERIZON FASCINATE
You flashed a GSM ROM onto a CDMA phone. That's just asking for a brick.
Now download this (and since you can't figure obvious things out, flash it into *PDA* of Odin, NOT NOT NOT NOT NOT "phone"), and pray it works.
Click to expand...
Click to collapse
not trying to be a d!ck but, you really need to stop before you do brick your phone. read, read, and read some more. its clear you dont understand what your doing and are going to end up screwing up even worse. read EVERYTHING dealing with ONLY the VZN fascinate. if it says anything other that VZN fascinate DO NOT READ IT. your in to big of a hurry and will brick your phone. hell, i have been hacking phones for years and am still not comfortable with android yet. i have rooted but not installed a rom because i dont want to mess it up. hell, i havent even done the new update from VZN. im waiting for more reports to come in. just take your time and read, then worry about flashing to another rom.
If you mess your phone up just use odin and the official stock DL09.md5 to return the phone to normal. Easy.
mdisaac said:
Today I installed my first rom, it was called dl09_supah_clean_04. That worked ok but I could not receive text messages. I thought maybe I'd try another rom. So I downloaded one called hamsters rom. Once I booted the phone up with that rom I got a bunch of errors. So I restarted and now get nothing but the samsung logo flashing. I go into recovery mode, click on update.zip to load clockwork recovery and get a message saying:
e:can't mount /dev/block/vold/179:9
(no such file or directory)
e:can't mount sdcard:update.zip
Installation aborted
I'm just wondering if I am screwed here. I'm about to plug the sdcard into my computer and copy update.zip again in hopes of getting clockwork recovery to work.... just wondering if anyone has any ideas in case this doesn't work.
Click to expand...
Click to collapse
You also need to odin the DL09 modem. or SMS and other things WILL be broken.
1.4hitachi said:
If you mess your phone up just use odin and the official stock DL09.md5 to return the phone to normal. Easy.
Click to expand...
Click to collapse
When people take Odin for granted, they end up with bricks.
Odin can be your friend...as long as you use PDA and not Phone...which is counter intuitive
adrynalyne said:
When people take Odin for granted, they end up with bricks.
Click to expand...
Click to collapse
Shouldn't you say, 'when people use Odin incorrectly"? I mean, as long as he follows the instructions and un-does and kernel changes beforehand the device will be returned back to stock. Also with the official DL09.md5 package it has inside all necessary operating parts. It sounds to me like all he did was attempt a rom flash twice. Odin with the "offical" DL09.md5 will return his Fascinate to stock.
Thanks everybody! I got back to stock and let phone receive the ota update of DL09. Figured that would take care of the kernel and modem and I could install dl09_supah_clean_04. Worked like a champ. I think I learned a lot in this process as well... time will tell.
Can somebody tell me how to root a my touch 4g ? I'm kinda new at this and want to learn.
chitopr said:
Can somebody tell me how to root a my touch 4g ? I'm kinda new at this and want to learn.
Click to expand...
Click to collapse
Google VISIONary (r14) place it on your device, install it then run it. Temproot is for temporary rooting your device, its gone after a reboot, permaroot is for good, unless you use the unroot option.
Its safe, fast and easy. I use temproot option so I can use some root only apps. This is the first device I have felt no need to add a custom rom to or anything so VISIONary was the choice for me. If you want the long harder way directions can be provided. I do recommand you learn the long hard way at some point, its good to know your way around just in case.
chitopr said:
Can somebody tell me how to root a my touch 4g ? I'm kinda new at this and want to learn.
Click to expand...
Click to collapse
first of all rooting is not for everyone. I can name a few people in a few forums that do not run a rooted phone for one reason or another. Rooting your phone gives you possibilities that are not even considered when you are in a stock form. But on the other hand you can seriously damage your phone, with the possibility of it ending up a 500.00 paper weight.
The safest and easiest thing to do is download VISIONary.apk and just use temp root. That will give you the ability to do everything you need to do in a root status w/o risking FUBARing anything. You can wi-fi tether, run Titanium Backup and stuff like that.
If you are wanting to go full blown and root it w/ s=off and do the
you can do it the real way and follow Cyanogen's method
Or you can do via the TheUnlockr for a simpler way.
If I temp-root it, would I have to temp-root it every time I want to run the wifi-tether program? Or just on installation?
http://forum.xda-developers.com/showthread.php?t=858996
I have been trying to get visionary r14 but i have no idea where to get it. I google visionary r14 and use the first link like many people have said but whenever i click download it says firefox can't find the page. Does anyone know of some other way to get visionary ?
Nickoro said:
I have been trying to get visionary r14 but i have no idea where to get it. I google visionary r14 and use the first link like many people have said but whenever i click download it says firefox can't find the page. Does anyone know of some other way to get visionary ?
Click to expand...
Click to collapse
There is a link in the post 4 above this one.
does anyone know if this method will work on a htc glacier thats flashed to a network other then t-mobile.
http://forum.xda-developers.com/showthread.php?t=858996
its my friends phone and he is on simple mobile. i have rooted quite a few phones and know what i am doing but wanted to make sure it wouldn't conflict with his network
mdrentz said:
does anyone know if this method will work on a htc glacier thats flashed to a network other then t-mobile.
http://forum.xda-developers.com/showthread.php?t=858996
its my friends phone and he is on simple mobile. i have rooted quite a few phones and know what i am doing but wanted to make sure it wouldn't conflict with his network
Click to expand...
Click to collapse
Any rooting method will work on any phone it was designed for.
Hi guys, I just follwed the method by the unlocker... but at the end when I go to better terminal I'm not getting the # sign... So I recon that it didn't work, right? What might the problem be?
My bad, wasn't writing SU... OPPSSS!!!
I think I screwed something. I just noticed that my CW version is 3.0.2.4 and everybody I see is talking about 3.0.0.5. Is this something bad? I'm having trouble flahing gapps and I got another strange problem, If I put a ringtone and reboot the phone it reverts to the original one, and if I copy something to the SD card it gets deleted. Strange? Please can anyone tell me if I screwed this and how can I resolve?
mindwarp1571 said:
I think I screwed something. I just noticed that my CW version is 3.0.2.4 and everybody I see is talking about 3.0.0.5. Is this something bad? I'm having trouble flahing gapps and I got another strange problem, If I put a ringtone and reboot the phone it reverts to the original one, and if I copy something to the SD card it gets deleted. Strange? Please can anyone tell me if I screwed this and how can I resolve?
Click to expand...
Click to collapse
3.0.0.5 is the older one. 3.0.2.4 is the newer one.
What error are you getting when you flashed the g/apps?
how the eff is stuff getting deleted from the SDcard. the recovery image doesn't natively delete anything from the SDcard.
neidlinger said:
3.0.0.5 is the older one. 3.0.2.4 is the newer one.
What error are you getting when you flashed the g/apps?
how the eff is stuff getting deleted from the SDcard. the recovery image doesn't natively delete anything from the SDcard.
Click to expand...
Click to collapse
I don't really know, this is a new 32 gig class 6 sandisk memory, the original 8gigs is out ot the phone. I left last night transfering from my pc 20 gigs of music and today after i disconnected it from the pc it was gone.
I'm testing the ringtones to determine what the heck is going on, more on that later....
Gapps... starts to install and...
finding update package...
opening update package...
e:cant open /sdcard/gapps-gb-20110307-signed.zip
(bad)
Installation aborted
This is the 4th time I download this... Maybe permissions?
mindwarp1571 said:
Gapps... starts to install and...
finding update package...
opening update package...
e:cant open /sdcard/gapps-gb-20110307-signed.zip
(bad)
Installation aborted
This is the 4th time I download this... Maybe permissions?
Click to expand...
Click to collapse
Their has to be something wrong with (a) the recovery image or (b) the g/apps.
Are you sure you are downloading the correct g/apps for our phone running CM7. They have their own g/apps....If you are 100% sure it's for our phone then i'd suggest .....
... is attempting to manually flash the recovery image to make sure you do not get a blip in the system. Personally, i do not trust flashing recovery images with Clockwork ROM manager. I've seen a-lot of errors come out of it. This might be one of them.
Have you tryed the 8gig sdcard to install the g-apps? the 32gig may be bad
I just removed the sd card and put it on my laptop and copied a folder with music... after taht turned on the phone and it is gone! strange!
Gonna test the 8gigs..
Put the 8 gigs, and it installed... Hmmm...
NOw, after it finishes the setup of the apps I will format the 32 and test it...
Every time I try to download the Visionary.apk from the above posts, it downloads, then tells me the file has a virus... what's going on? Are they false positives?
_Allan_ said:
Every time I try to download the Visionary.apk from the above posts, it downloads, then tells me the file has a virus... what's going on? Are they false positives?
Click to expand...
Click to collapse
Its false so don't worry about it and go with VISIONary+
I was excited that I received a message to update my firmware to 2.2 Froyo, but when I tried doing so I kept getting errors at the installation screen. It would download then go to the installation screen and give me an error.
I'm not sure if I bricked the phone without knowing or something, but I get the following error message when trying to upgrade:
E:Can't open /cache/recovery/command
I have no idea what that is/where it is. I checked my SD Card, but I didn't see anything like that there. I'm guessing I'm missing that folder/file, but I don't know where it would have went or if I can get it back.
I've tried to do the update both through my Bravo and downloading a ZIP file and trying to do it through the Recovery screen. I tried everything Motorola suggests on their website as well as searched Google a lot, but came up with nothing.
I should add that even when I click "applysdcard:update.zip" it gives me a few errors and aborts the installation.
I'm just wondering if there's any way to fix this so I can upgrade my firmware?
Thanks to anyone that can help.
GeNiO426 said:
I was excited that I received a message to update my firmware to 2.2 Froyo, but when I tried doing so I kept getting errors at the installation screen. It would download then go to the installation screen and give me an error.
I'm not sure if I bricked the phone without knowing or something, but I get the following error message when trying to upgrade:
E:Can't open /cache/recovery/command
I have no idea what that is/where it is. I checked my SD Card, but I didn't see anything like that there. I'm guessing I'm missing that folder/file, but I don't know where it would have went or if I can get it back.
I've tried to do the update both through my Bravo and downloading a ZIP file and trying to do it through the Recovery screen. I tried everything Motorola suggests on their website as well as searched Google a lot, but came up with nothing.
I should add that even when I click "applysdcard:update.zip" it gives me a few errors and aborts the installation.
I'm just wondering if there's any way to fix this so I can upgrade my firmware?
Thanks to anyone that can help.
Click to expand...
Click to collapse
Have you done any sort of modding using SQLite Editor or Root Explorer to your phone?
i have the same error, but i do have modified the bravo with sqlite editor en root explorer. Does somedoby has the original build.prop please? i cant remember what i have changed in mine so i can not update
gosunta said:
i have the same error, but i do have modified the bravo with sqlite editor en root explorer. Does somedoby has the original build.prop please? i cant remember what i have changed in mine so i can not update
Click to expand...
Click to collapse
Just emailed you the original build.prop you need in order to get the update to work. Let me know how it goes.
Finally working , i replace the file and i did upgrade my phone. Thanks a lot for all the info
I get a the update downloaded but when it restarts I am getting a white triangle with a yellow explination point.
If I pop the battery I can get past the error and back to the phone
I have it rooted with one click
Any info?
seraphielx said:
I get a the update downloaded but when it restarts I am getting a white triangle with a yellow explination point.
If I pop the battery I can get past the error and back to the phone
I have it rooted with one click
Any info?
Click to expand...
Click to collapse
touch the screen at right-bottom and you will see a list. Select update.zip and touch ok
hippyman said:
Have you done any sort of modding using SQLite Editor or Root Explorer to your phone?
Click to expand...
Click to collapse
I'm sure there is a solution, but just forget it and install 2.2 SBF.
hippyman said:
Have you done any sort of modding using SQLite Editor or Root Explorer to your phone?
Click to expand...
Click to collapse
Yes, I used Root Explorer. I'm guessing by MCFarmfresh's post that there issome sort of original build for the phone? I've looked everywhere for hours all night last night before resorting to asking somewhere, but I couldn't find anything and the "solutions" I've seen all did not work. I kept getting the same errors.
Thank you for replying. If you can help, it'll be very much appreciated.
I have a rooted Bravo and I deleted some of the bloatware, and I received the Froyo update and everytime I download and the system resets I get an error and the update stops. Selecting from memory card doesnt work for me, and I dont have a backup of the original settings to re-install (which I'm not sure how to do that either). If anyone has any suggestions I'm open.
its checking for att apps
if you renamed them name them back to apk
I didn't rename them, I deleted them off my phone.
Sent from my MB520 using XDA App
I don't know much about these things but I would think that would be a bad thing to do...
I was able to get the update to install to my phone but now it is running slow
Any more info on how to fix this issue?
OK, so I tried everything that's suggested pretty much everywhere and I'm still unable to update. I'm not sure if I'm doing something wrong or what, but I've tried resetting the phone via the phone/recovery screen, tried updating via the phone, and I also tried replacing the original build, but nothing worked so far.
I have no idea what else I can do, but any help would be appreciated.
GeNiO426 said:
OK, so I tried everything that's suggested pretty much everywhere and I'm still unable to update. I'm not sure if I'm doing something wrong or what, but I've tried resetting the phone via the phone/recovery screen, tried updating via the phone, and I also tried replacing the original build, but nothing worked so far.
I have no idea what else I can do, but any help would be appreciated.
Click to expand...
Click to collapse
If nothing else works, you can always sbf. It sounds scarier than it really is, actually it is pretty easy. Just make sure you follow the directions. I've done several sbf's and they have all turned out perfectly.
jorgonv said:
If nothing else works, you can always sbf. It sounds scarier than it really is, actually it is pretty easy. Just make sure you follow the directions. I've done several sbf's and they have all turned out perfectly.
Click to expand...
Click to collapse
Thanks. I'm not sure what it was, but I switched to my Windows XP desktop (from my Windows 7 Home 64-bit laptop) and the SBF Flash worked perfectly, thanks bandroid, yourself, and others. I really appreciate all of the help given. 2.2 looks and feels a lot better than 2.1 so I'm really happy about that.
MCFarmfresh said:
Just emailed you the original build.prop you need in order to get the update to work. Let me know how it goes.
Click to expand...
Click to collapse
please send me one too and where do i put it.????
mismisgh said:
please send me one too and where do i put it.????
Click to expand...
Click to collapse
If you will give me your email I can get it to you. For the life of me I cannot figure out hhow to attach files through pm using my phone lol. You can also use the .sbf method to upgrade but I'll definitely get the files to you if you send me your email.
SBF'in it...
Okay....so one of your gentleman above (I'm new to the forum ish) stated that he had deleted some apps off of his OS. I did the same thing with AT&T Hotspot Locator (unfortunately, AT&T was quick on merging this standalone app into MyAT&T so I couldn't get the atthotspotlocator.apk back). I fixed this using the SBF file.
I won't give you the step by step but I can tell you RSD Lite is a free program from Motorola. It's basically the program they use to flash boot SW onto an otherwise dead device.
Don't be intimidated by it because it really is rather easy to facilitate. Just do like I did and YouTube how to load an SBF into a motorola device. You can pause and replay as you go along to assure no errors. Takes like 15 minutes once you've got all the necessary files downloaded.
Well, that lasted long...
Everything was going fairly well until this morning when I clicked on the phone button (default launcher) and tried to go into the dialer, then it just closed every time I tried doing so.
To try to fix this I rebooted my phone, nothing; restored, nothing; factory reset, nothing; re-installed 2.2.1 FroYo via flashing the SBF with RSD Lite and 'apply:sdcard:update.zip' through Android's Recovery Screen, nothing.
When I tried doing the last 2, however, I received these errors (the first one I had with the first problem and the other 2 are new):
E:Can't mount CACHE: recovery/command
E:Can't mount CACHE: recovery/caller
E:Can't mount CACHE: recovery/log
Now, with the "caller" error, I did NOT touch anything having to do with the dialer and whatnot. That I know.
The last time I had problems with my laptop so I tried it on my desktop and it worked, but now I tried the desktop and it still isn't working properly. Some of the features that I had with the update are now gone such as the "third party apps" option and the sliding "lock screen" is now permanently present.
Any help with this is appreciated.
I've noticed that a lot off people get the update, try to apply it, then are disappointed when all the get on reboot is an android with an exclamation mark so I figured I would shed some light on how to minimize this and it comes down to checking the updater-script which I'll tell you how I do. First thing I do after getting the prompt for an update is let it download. After it downloads I use root explorer(since I am rooted) and copy the update from /cache to /sdcard because one thing I've noticed is that I can't get the prompt to update again if it fails so this way I've got my own backup of the update. Now, instead of accepting the update I first append .zip to the dlpkgfile in /sdcard so that I can open it. Open it and navigate to "\META-INF\com\google\android\" and open "updater-script" which should open in the text editor. This file is exactly what the update is running when it starts. First in the file is a list of asserts and these are what generally cause the update to fail. What they do is check to make sure the file it is going to patch is unmodified so that it can successfully patch it. If it detects the file it's checking is modified it kicks to the !. 8.6.5.6 initially didn't work for me but by checking the script I found the problem was my srs_processing.cfg file because I tried to fix my speaker balance and this was a file that the script asserted. After restoring the original file I was able to update with stock recovery even though I had modified other system files including kernel. As long as the specific files the update checks are ok the update will proceed. If you have never modified anything and are completely stock then you don't have to do this, it's just nice knowing what's going on.
Here is a list of everything that is checked:
Code:
system/app/AWS.odex
system/app/ApplicationsProvider.apk
system/app/ApplicationsProvider.odex
system/app/AsusReader.apk
system/app/AsusReader.odex
system/app/AsusSetupWizard.odex
system/app/Bluetooth.apk
system/app/Bluetooth.odex
system/app/BooksTablet.odex
system/app/Browser.apk
system/app/Browser.odex
system/app/CMClient.apk
system/app/CMClient.odex
system/app/Calculator.apk
system/app/Calculator.odex
system/app/Calendar.apk
system/app/Calendar.odex
system/app/CalendarProvider.apk
system/app/CalendarProvider.odex
system/app/Camera.odex
system/app/CertInstaller.apk
system/app/CertInstaller.odex
system/app/ChromeBookmarksSyncAdapter.odex
system/app/Contacts.apk
system/app/Contacts.odex
system/app/ContactsProvider.apk
system/app/ContactsProvider.odex
system/app/DLNA.apk
system/app/DLNA.odex
system/app/DMClient.apk
system/app/DMClient.odex
system/app/DefaultContainerService.apk
system/app/DefaultContainerService.odex
system/app/DeskClock.odex
system/app/Dictionary.odex
system/app/DownloadProvider.apk
system/app/DownloadProvider.odex
system/app/DownloadProviderUi.apk
system/app/DownloadProviderUi.odex
system/app/DrmProvider.apk
system/app/DrmProvider.odex
system/app/Email.odex
system/app/EmailWidget.apk
system/app/EmailWidget.odex
system/app/Exchange.odex
system/app/FacebookPoster.odex
system/app/FileManager.apk
system/app/FileManager.odex
system/app/Finsky.odex
system/app/GalleryNew3DGoogle.odex
system/app/Gmail.odex
system/app/GoogleBackupTransport.odex
system/app/GoogleCalendarSyncAdapter.odex
system/app/GoogleContactsSyncAdapter.odex
system/app/GoogleFeedback.odex
system/app/GoogleLoginService.odex
system/app/GooglePartnerSetup.odex
system/app/GoogleQuickSearchBox.odex
system/app/GoogleServicesFramework.odex
system/app/HTMLViewer.apk
system/app/HTMLViewer.odex
system/app/HoloSpiralWallpaper.apk
system/app/HoloSpiralWallpaper.odex
system/app/Keyboard.odex
system/app/Kindle-OEM.odex
system/app/LatinImeGoogle.odex
system/app/Launcher2.apk
system/app/Launcher2.odex
system/app/Layar.odex
system/app/LiveWallpapersPicker.apk
system/app/LiveWallpapersPicker.odex
system/app/MEar.odex
system/app/Maps.odex
system/app/MarketUpdater.odex
system/app/MediaProvider.apk
system/app/MediaProvider.odex
system/app/MediaUploader.odex
system/app/ModemUpdateService.odex
system/app/Music2.odex
system/app/MyCloud.odex
system/app/MyGazine.odex
system/app/MyWater.odex
system/app/NVIDIATegraZone.odex
system/app/NetworkLocation.odex
system/app/OneTimeInitializer.odex
system/app/PCSyncLauncher.odex
system/app/PRAndroid.odex
system/app/PackageInstaller.apk
system/app/PackageInstaller.odex
system/app/Phone.apk
system/app/Phone.odex
system/app/PicoTts.odex
system/app/PixWe.odex
system/app/PolarisOffice.apk
system/app/PolarisOffice.odex
system/app/Screenshot.apk
system/app/Screenshot.odex
system/app/Settings.apk
system/app/Settings.odex
system/app/SettingsProvider.apk
system/app/SettingsProvider.odex
system/app/SetupWizard.odex
system/app/SoundRecorder.apk
system/app/SoundRecorder.odex
system/app/StrAsus.odex
system/app/Street.odex
system/app/SystemUI.apk
system/app/SystemUI.odex
system/app/Talk.odex
system/app/TelephonyProvider.apk
system/app/TelephonyProvider.odex
system/app/TtsService.apk
system/app/TtsService.odex
system/app/UpdateLauncher.apk
system/app/UpdateLauncher.odex
system/app/UserDictionaryProvider.apk
system/app/UserDictionaryProvider.odex
system/app/Vending.odex
system/app/Vibe2.odex
system/app/VideoEditorGoogle.odex
system/app/Videos.odex
system/app/VoiceSearch.odex
system/app/Weather.odex
system/app/XT9IME.apk
system/app/XT9IME.odex
system/app/YouTubeTablet.odex
system/app/ZinioReader.odex
system/app/ZinioSettingsProvider.odex
system/bin/brcm_ram_plus
system/bin/debuggerd
system/bin/fu
system/bin/vold
system/bin/wpa_supplicant
system/buildrop
system/framework/am.jar
system/framework/am.odex
system/framework/androidolicy.jar
system/framework/androidolicy.odex
system/framework/android.test.runner.jar
system/framework/android.test.runner.odex
system/framework/apache-xml.jar
system/framework/apache-xml.odex
system/framework/bmgr.jar
system/framework/bmgr.odex
system/framework/bouncycastle.jar
system/framework/bouncycastle.odex
system/framework/com.android.future.usb.accessory.jar
system/framework/com.android.future.usb.accessory.odex
system/framework/com.android.locationrovider.jar
system/framework/com.android.locationrovider.odex
system/framework/core-junit.jar
system/framework/core-junit.odex
system/framework/core.jar
system/framework/core.odex
system/framework/ext.jar
system/framework/ext.odex
system/framework/framework-res.apk
system/framework/framework.jar
system/framework/framework.odex
system/framework/ime.jar
system/framework/ime.odex
system/framework/input.jar
system/framework/input.odex
system/framework/javax.obex.jar
system/framework/javax.obex.odex
system/framework/monkey.jar
system/framework/monkey.odex
system/framework/pm.jar
system/framework/pm.odex
system/framework/services.jar
system/framework/services.odex
system/framework/sqlite-jdbc.jar
system/framework/sqlite-jdbc.odex
system/framework/svc.jar
system/framework/svc.odex
system/lib/drm/libdrmwvmplugin.so
system/lib/hw/gralloc.tegra.so
system/lib/libandroid_servers.so
system/lib/libbcc.so
system/lib/libereader.so
system/lib/libinput.so
system/lib/libjSebring.so
system/lib/libnvomx.so
system/lib/libsensors.mpl.so
system/lib/libsrsprocessing.so
system/lib/libstagefright.so
system/lib/libwebcore.so
system/lib/libwvdrm.so
system/lib/libwvm.so
system/lib/modules/bcm4329.ko
system/lib/modules/scsi_wait_scan.ko
I can remember with an old 2.1 tablet we used to modify the actual update script and remove the part of the script that it checks against, so the update would go ahead without checking anything.
Guys, supposing the FOTA update has gone wrong (that's my case, and i understood why... most probably the issue is related to my modified wpa_supplicant this time) ... Is there any way to re-trigger the update procedure?
As far as I've understood the update is cached after download in the tablet, is there any way to retry in case something's gone wrong?
Otherwise, as far as I know, the only way is to bring everything to stock using Nvflash and original ROM and wait for Asus to put on their site the update. That seems to be related to the fact that Asus servers track any FOTA request for a device and let you download it only once.
If you're US you can get the update from here http://forum.xda-developers.com/showthread.php?t=1231635 rename the update to EP101_SDUPDATE.zip put it on the root of a microsd card then boot the transformer into recovery and it will update. As for the wpa_supplicant, use the stock 3.1 in the OP of this post http://forum.xda-developers.com/showthread.php?t=1093778 and you should be able to update.
alex5790 said:
If you're US you can get the update from here http://forum.xda-developers.com/showthread.php?t=1231635 rename the update to EP101_SDUPDATE.zip put it on the root of a microsd card then boot the transformer into recovery and it will update.
Click to expand...
Click to collapse
Can I use CWM recovery or stock recovery required?
rufik said:
Can I use CWM recovery or stock recovery required?
Click to expand...
Click to collapse
I'm pretty sure you have to have stock recovery. If you have CWM you could try it and the worst thing that could happen is just the update failing. Also make sure you have a U.S. transformer because that specific update is U.S.
Hmm, I dont have the compass issues so Im trying to decide here if its worth restoring my old SystemUI (I am running the stock buttons) because that is the only thing I changed when rooted in order to update or just wait for someone to put out a deodexed version.
alex5790 said:
I'm pretty sure you have to have stock recovery. If you have CWM you could try it and the worst thing that could happen is just the update failing. Also make sure you have a U.S. transformer because that specific update is U.S.
Click to expand...
Click to collapse
Is there a quick and easy way to restore/flash the stock recovery? I have CWM and want to get the stock recovery back, but so far the only ways I've found to do that require using nvflash and wiping everything. Am I wrong? It seems like there should be an easier way. On my Evo 4G I was able to flash back and forth between recoveries.
My firmware has been downloaded but is not in /cache. Is there another location where it could have downloaded to? What is the file name of the update?
kenlperry said:
Is there a quick and easy way to restore/flash the stock recovery? I have CWM and want to get the stock recovery back, but so far the only ways I've found to do that require using nvflash and wiping everything. Am I wrong? It seems like there should be an easier way. On my Evo 4G I was able to flash back and forth between recoveries.
Click to expand...
Click to collapse
For the transformer I don't know of a easy way that would be a question for a dev.
GiantSeaturtle said:
My firmware has been downloaded but is not in /cache. Is there another location where it could have downloaded to? What is the file name of the update?
Click to expand...
Click to collapse
It should be named dlpkgfile. If you are not running a file explorer as root the /cache directory will appear empty. I personally use root explorer because it runs as root by default. I'm not sure what other file explorers can run as root.
I was one of the dumb ones and ran the update while still rooted ( thought I wasn't but I guess I was). I then used the Nvflash and original ROM to get back to stock US 8.6.5.6. I then followed the direction in the post to get he dlpkgfile and renamed it EP101_SDUPDATE.zip and put it on the root of the SDcard and booted into the RCK and I am still getting the Yellow ! mark. All I did while rooted was apply the netflix patch but I was under the assumption that if I ran the NvFlash back to root that it put back the original file for libnvomx.so. Is that not the cause and has anyone been able to use this dlpkgfile to get to the updated version?
Thanks
dugout2929 said:
I was one of the dumb ones and ran the update while still rooted ( thought I wasn't but I guess I was). I then used the Nvflash and original ROM to get back to stock US 8.6.5.6. I then followed the direction in the post to get he dlpkgfile and renamed it EP101_SDUPDATE.zip and put it on the root of the SDcard and booted into the RCK and I am still getting the Yellow ! mark. All I did while rooted was apply the netflix patch but I was under the assumption that if I ran the NvFlash back to root that it put back the original file for libnvomx.so. Is that not the cause and has anyone been able to use this dlpkgfile to get to the updated version?
Thanks
Click to expand...
Click to collapse
It has to be the external microsd card, not the internal sdcard.
alex5790 said:
It has to be the external microsd card, not the internal sdcard.
Click to expand...
Click to collapse
Thanks, I went ahead and ran it from the MicroSD card and I am getting still getting the yellow !. I would have thought had I done the nflash to the current rom it would have reset all the files under system.
dugout2929 said:
Thanks, I went ahead and ran it from the MicroSD card and I am getting still getting the yellow !. I would have thought had I done the nflash to the current rom it would have reset all the files under system.
Click to expand...
Click to collapse
The only other asserts are:
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "asus/US_epad/EeePad:3.2/HTJ85B/US_epad-8.6.5.6-20110726:user/release-keys"
and
assert(getprop("ro.product.device") == "EeePad"
so unless those are different it should work especially if you nvflashed it back to stock. Does it immeadiately go to ! or does the green bar at least progress a little? Also what region eg. US,WW,TW
alex5790 said:
The only other asserts are:
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "asus/US_epad/EeePad:3.2/HTJ85B/US_epad-8.6.5.6-20110726:user/release-keys"
and
assert(getprop("ro.product.device") == "EeePad"
so unless those are different it should work especially if you nvflashed it back to stock. Does it immeadiately go to ! or does the green bar at least progress a little?
Click to expand...
Click to collapse
It does a the progress bar for about 1 sec or so. It is the US version.
kenlperry said:
Is there a quick and easy way to restore/flash the stock recovery? I have CWM and want to get the stock recovery back, but so far the only ways I've found to do that require using nvflash and wiping everything. Am I wrong? It seems like there should be an easier way. On my Evo 4G I was able to flash back and forth between recoveries.
Click to expand...
Click to collapse
You can use nvflash to "download" partition 5 which is the SOS/recovery. You can reflash the stock and apply the stock OTA. There will be no --create flag in the nvflash command.
A modded OTA won't work with the stock recovery because of signature checks.
CWM should be able to flash everything but the blob, but you have to mount system first. You can mount staging and then the blob will flash as well (after a manual reboot to recovery). I have to admit that it is a pretty convoluted process if your android-fu is weak.
sent from my cyanogen(mod) vision
dugout2929 said:
It does a the progress bar for about 1 sec or so. It is the US version.
Click to expand...
Click to collapse
Possibly there could be something wrong with the rom used to nvflash. What you could try next is go to Asus's site and get the 8.6.5.6 update, unzip it once so that it is only a single zip file, rename it to EP101_sdupdate put it on the root of the microsd and try to flash that then try to flash 8.6.5.9 again
alex5790 said:
Possibly there could be something wrong with the rom used to nvflash. What you could try next is go to Asus's site and get the 8.6.5.6 update, unzip it once so that it is only a single zip file, rename it to EP101_sdupdate put it on the root of the microsd and try to flash that then try to flash 8.6.5.9 again
Click to expand...
Click to collapse
I was able to do this and it worked perfectly, I was thinking maybe the file dlpkgfile that I got was corrupt but I am able to unzip it etc. I guess I will just need to wait for Asus to put it out on their site.
Thanks for all the help.
dugout2929 said:
I was able to do this and it worked perfectly, I was thinking maybe the file dlpkgfile that I got was corrupt but I am able to unzip it etc. I guess I will just need to wait for Asus to put it out on their site.
Thanks for all the help.
Click to expand...
Click to collapse
If you think it might be corrupt you could try the one from this post http://forum.xda-developers.com/showthread.php?t=1231635