Related
DO NOT FLASH THIS UPDATE UNTIL YOU HEAR FROM THE BIG GUNS OR RISK LOSING YOUR ROOT!
Please Be Patient!!!!
Sprint is pushing out a system update this morning with a size 21.43mb
Update Download Links:
http://www.mediafire.com/file/2myavzqygir/OTA_Supersonic_1.47.651.1-1.32.651.6_releaseq2wpcb5jl7uowah9.zip Thanks Calkulin!
http://www.sdx-downloads.com/sdx/evo/stock/OTA_Supersonic_1.47.651.1-1.32.651.6_release.zip Thanks Joeykrim!
Firmware Version
2.1-update1
Baseband Version
2.05.00.06.10
Kernel Version
2.6.29-789bf291
[email protected] #1
PRI Version 1.40_003
PRL Version 60667
Thank you joeykrim for the following:
RADIO - the radio is updated through a radio.diff.
SYSTEM - no system/app files are changed
it appears this OTA is much more extensive than the previous OTA.
this one appears to apply small patches to every application in /system/app. a few are large in size, but most are very small.
it also appears to patch:
16 files in system/bin
etc/wimax/
etc/firmware/fw_bcm4329.bin and (ap)
31 files in framework
28 files in lib
2 files in lib/modules - bcm4329.ko and sequans_sdio.ko
SYSTEM updated files (might be more, researching now):
wifi module - BCM4329B1_002.002.023.0396.0402.hcd
android.hardware.camera.flash-autofocus.xml
android.hardware.telephony.cdma.xml
ton of framework files
libCamera_donut.so
libCamera_eclair.so
Fixes & Bugs:
From user npace: (I extracted and fastboot flashed the kernel zImage. Here's a rundown of the issues that I tested for fixes
1. Touch input lag -- fixed -- tried with multitouch visualizer 2
2. Improperly grounded touchscreen -- fixed -- tried on multiple surfaces
3. 30 fps cap -- still there
same radio by your title?
Appears to be. I am waiting for it to finish downloading and I will attempt to upload.
This thread will probably be moved / deleted but I was just letting everyone know. Personally I am going to wait to hear from the Dev's on this download before even touching it.
is this breaking root access.. some unrevoked users via face book saying unrevoked is no longer working.. i guess they should have went all out and did the full root
danon.brown said:
is this breaking root access.. some unrevoked users via face book saying unrevoked is no longer working.. i guess they should have went all out and did the full root
Click to expand...
Click to collapse
Even if you rooted via toasts method, i would not update until a custom ROM is put out with the update included. You could lose root ability forever.
Anyone know the location of system updates are stored on the phone? I am trying to locate using the adb shell but have had no luck finding the download yet.
huoter said:
Appears to be. I am waiting for it to finish downloading and I will attempt to upload.
This thread will probably be moved / deleted but I was just letting everyone know. Personally I am going to wait to hear from the Dev's on this download before even touching it.
Click to expand...
Click to collapse
can you post this OTA .zip?
joeykrim said:
can you post this OTA .zip?
Click to expand...
Click to collapse
Its done downloading, just trying to find the darn file right now. Any ideas?
Awaiting an update zip
Here's the untouched update zip for those that want it. If you want to put it in the OP, feel free to
OTA_Supersonic_1.47.651.1-1.32.651.6_releaseq2wpcb5jl7uowah9.zip
huoter said:
Its done downloading, just trying to find the darn file right now. Any ideas?
Click to expand...
Click to collapse
i didn't look into the last one and this is my first HTC phone so im not familiar with their OTA process.
perhaps try /cache? or any type of temp directory on /data or /sdcard?
we know it won't be on /system.
We install this from recovery, right?
herzzreh said:
We install this from recovery, right?
Click to expand...
Click to collapse
Don't install anything until some devs have had a look around--they'll make a package to flash when it's safe.
herzzreh said:
We install this from recovery, right?
Click to expand...
Click to collapse
I'd recommend not installing it at all until the devs here have had a chance to go through it and release it themselves. You risk loosing your root if you don't. Then follow their release instructions to apply it.
Btw the radio is 2.05.00.06.10 with this update.
Sent from my EVO using Tapatalk
Shidell said:
Don't install anything until some devs have had a look around--they'll make a package to flash when it's safe.
Click to expand...
Click to collapse
I don't care if I lose root. I assume this update doesn't reinstall Sprint junk, so I'm good to go. That was the only reason why I wanted root access...
donatom3 said:
Btw the radio is 2.05.00.06.10 with this update.
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
if you've applied this, can you take a screenshot of the about phone -> software versions or manually type all the info up on here?
im wondering about the PRI ...
herzzreh said:
I don't care if I lose root. I assume this update doesn't reinstall Sprint junk, so I'm good to go. That was the only reason why I wanted root access...
Click to expand...
Click to collapse
No, looks like just about all the preloaded APK's are in there, including the Sprint crap. I assume if you apply it as stock you'll get them back, but I could be wrong.
herzzreh said:
I don't care if I lose root. I assume this update doesn't reinstall Sprint junk, so I'm good to go. That was the only reason why I wanted root access...
Click to expand...
Click to collapse
The official froyo release from HTC / Sprint will definitely contain all the "Sprint Junk" and if you've given up root to one of these updates and go to apply that it will all come back. You may never get root again in order to re - clean it up once you apply froyo.
Be patient. It won't take the devs here long to cook up an update for us. Flipz had the rooted .6 update rom out in 24 hours or so...
.....
Just took a look inside the zip file. All the apk files are there, including the sprint junk...
Just installed....all is well with root...
Just like our USCC friends, I'm currently working on several mods for Cellular South's release of the Desire. I'll keep this post updated with new developments.
Linked is a custom boot.img from our stock ROM with apps2sd support. You will still need to download and flash the latest Darktremor apps2sd release and format your SD card accordingly.
How to flash?
Place the dphase-apps2sd-signed.zip file on the root of your sdcard and flash it as a zipped update.
Download Link (Cellular South, also confirmed working with Alaska Communications):
http://dphase.net/desire/dphase-apps2sd-signed.zip (2.3 MB)
MD5 checksum: 70df556ceb6891cbdcc3801d807d58af
US Cellular stock boot.img with apps2sd support
http://dphase.net/desire/dphase-USCC-apps2sd-signed.zip (2.3 MB)
MD5 checksum: e11b6f40b26811e252f0579f0ed5861c
Latest Darktremor apps2sd:
http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.1-adv-signed.zip
------------------------------------------------------------------------------------------
Zipaligned and PNG optimized system apps:
Code:
% du -sh original optimized
62M original
42M optimized
As you can see above, I've zipaligned and optimized the images in the system apps, which shaved off 20MB from total files size. This should lead to faster load times.
To install, untar the optimized archive to the directory of choice and boot to recovery. Mount the /system partition then do the following command with adb from within the directory holding the apk's (adb should be in your binary path, if not, fix that to make life easier in the future):
Code:
adb push . /system/app
You'll then see, for example:
Code:
push: ./DCSImpl.apk -> /system/app/DCSImpl.apk
push: ./HtcDialer.apk -> /system/app/HtcDialer.apk
push: ./EnhancedGoogleSearchProvider.apk -> /system/app/EnhancedGoogleSearchProvider.apk
... (etc)
Link:
http://dphase.net/desire/system_app_optimized.tar.gz (40MB compressed)
MD5 checksum:
2dc5fe2683e657006d2a8026c4ac32dc
reserved for later use
So what exactly does this accomplish? Is it basically adding apps 2 sd to the stock 2.1 rom? Any chance it will run on my US Cell desire?
Yes, adds apps2sd support to the stock rom. The latest a2sd will automagically move portions of /data over once it sees a properly formatted card.
In theory, this should work on USCC, but ymmv.
It is likely I won't get time tonight, but if I do, I'll be sure to give it a shot. I would like to get a2sd without a full reflash
con247 said:
It is likely I won't get time tonight, but if I do, I'll be sure to give it a shot. I would like to get a2sd without a full reflash
Click to expand...
Click to collapse
If it doesn't work, we'll grab your existing boot.img and I can tweak it.
Updates posted, please test and enjoy.
dphase said:
If it doesn't work, we'll grab your existing boot.img and I can tweak it.
Click to expand...
Click to collapse
That is the link to my boot.img
If you have time, if you could tweak that one, it would be great. If not, I'll give yours a shot tonight.
con247 said:
That is the link to my boot.img
If you have time, if you could tweak that one, it would be great. If not, I'll give yours a shot tonight.
Click to expand...
Click to collapse
I've modified your boot.img and placed a link in the first post.
dphase said:
I've modified your boot.img and placed a link in the first post.
Click to expand...
Click to collapse
A Big Thanks I am testing it now. I had to remember to change the MD5 information otherwise you get a fail.
Also You have to remember to run the apps2sd after the restore otherwise you will not boot!
Just booted and WOW look at all that new Space!!! Time to get more apps
seesser said:
A Big Thanks I am testing it now. I had to remember to change the MD5 information otherwise you get a fail.
Also You have to remember to run the apps2sd after the restore otherwise you will not boot!
Click to expand...
Click to collapse
Yes, I recommend installing apps2sd, formatting card, then applying new boot image.
How do you change the MD5 of the file
dphase said:
Yes, I recommend installing apps2sd, formatting card, then applying new boot image.
Click to expand...
Click to collapse
I guess I did it a little differently. I already had the sd card partitioned so I just took a backup swapped the boot.img and edited the MD5 with note++. Restored the modified backup and then ran the apps2sd.zip and rebooted.
I did it this way just in case something went wrong I could restore the backup that I didn't modify.
Going to try out that app optimize next.
Thank again.
This might be a noobish ?
but couldnt I just use a custom recovery and flash this as a rom?
or do I still have to push stuff?
im a lil confused coming from winmo
Right now im running blitz's apps2sd 2.1 sense rom
but not sure im seeing any benifit from the apps2sd....although I do see somethings being moved...wondering if seesser had tried blitz's rom...
are u seeing more space with the above method?
and what do I change the md5 to?
thanks
byte
bytethegroove said:
This might be a noobish ?
but couldnt I just use a custom recovery and flash this as a rom?
or do I still have to push stuff?
im a lil confused coming from winmo
Right now im running blitz's apps2sd 2.1 sense rom
but not sure im seeing any benifit from the apps2sd....although I do see somethings being moved...wondering if seesser had tried blitz's rom...
are u seeing more space with the above method?
and what do I change the md5 to?
thanks
byte
Click to expand...
Click to collapse
Hello and yes I was running that rom but did not like that friend Stream did not have twitter. with that rom you still had to tell the phone to move the files (a little bit of command line codding). With this boot.img and apps2sd on my stock rom backup I went from 15mb to 71mb so this one works great right out of the box.
I Explained how I did it from a backup of my stock rom up a few lines hope this helps.
I too am a little lost on this push of the app optimize. Could you explain it a little more? I have done a little adb shell programming but am lost with your directions.
Thanks,
bytethegroove said:
This might be a noobish ?
but couldnt I just use a custom recovery and flash this as a rom?
or do I still have to push stuff?
im a lil confused coming from winmo
Right now im running blitz's apps2sd 2.1 sense rom
but not sure im seeing any benifit from the apps2sd....although I do see somethings being moved...wondering if seesser had tried blitz's rom...
are u seeing more space with the above method?
and what do I change the md5 to?
thanks
byte
Click to expand...
Click to collapse
No, none of this can be flashed as a rom.
I'm not sure why anyone is changing MD5's, I included those so one could verify there was no data corruption during the download.
fixed. no worries..
con247 said:
I keep getting an MD5 mismatch after I edited the nandroid.md5 to the one in the original post
Click to expand...
Click to collapse
There is zero reason to edit that. Are you trying to use nandroid to flash the image? If so, that's the wrong answer.
con247 said:
fixed. no worries..
Click to expand...
Click to collapse
Did you restart the phone after you modified the MD5? I had that problem also until I restarted the phone and It worked after that.
I tried to update my rooted TF using a repacked 8.4.4.11 update.zip file (the one with all the patch files in it), but it kept failing on checking of the existing APK hashes. Not sure why, but I got around it by doing a clean install of 8.4.4.5, manually applying the 8.4.4.11 patch, then taking all of the changed (between 8.4.4.5 and .11) files and packing them up in a zip file with an updater-script file.
You should be able to apply this to any US version TF (rooted or stock as long as you have CWR) and bring everything up-to-date without losing root or any of your other install modules, system APKs, etc.
Make sure you back up first, as this is something I quickly threw together and has not been properly vetted. If you find a problem, let me know and I'll try to get it fixed and updated ASAP.
You can also download this ZIP and just take out any APKs you are interested in (the google video apk seems to be popular for example).
Link: http://blog.ryantadams.com/2011/07/...4-5-to-8-4-4-11-changed-files-rom-update-zip/
good work dude! i know a bunch of guys here need this. Now Im assuming this has SU installed
The only thing is you should label this Thread correctly with a [ROM] tag so others will know
nicknowsky said:
good work dude! i know a bunch of guys here need this. Now Im assuming this has SU installed
The only thing is you should label this Thread correctly with a [ROM] tag so others will know
Click to expand...
Click to collapse
Unless I misread this is just an update script and not a full ROM. So this would only work for people on 3.1 though right? You shouldn't flash this from 8.2.X.X for example?
Edit: Thanks this is a great idea, and I was just ready to try this when I saw Prime 1.6 out. Keep it up, I wonder if something like this would work when the 3.2 update comes out.
ToyTank said:
Unless I misread this is just an update script and not a full ROM. So this would only work for people on 3.1 though right? You shouldn't flash this from 8.2.X.X for example?
Click to expand...
Click to collapse
...Not sure why, but I got around it by doing a clean install of 8.4.4.5, manually applying the 8.4.4.11 patch, then taking all of the changed (between 8.4.4.5 and .11) files and packing them up in a zip file with an updater-script file....
Click to expand...
Click to collapse
Looks like so; zip should be run on-top of 8.4.4.5.
thank you worked for me
This does not have SU in it (or anyhtign else "custom"), but when applied to a ROM that already has SU/busybox/anyhting else in it, those files will be retained.
This is an "update" in the sense that it only contains files changed between 8.4.4.5 and 8.4.4.11, so you will need to be coming from 8.4.4.5 (or perhaps anyhtign 3.1, not sure). It is nto really an "update" though, as all of the patch files (blahblahblah.apk.p) and the patch script have been replaced with full 8.4.4.11 version of the files and the script has been udpated to simply copy these over into the appropriate folders on yoru TF.
I see this being most useful for people who have modified their 8.4.4.5 install such that in will no longer be patachable using a script that pataches the existing files.
I just used this to update from 8.4.4.5_US and it seems to have worked just fine! I kept my superuser app, and nothing was touched. My apps, widgets, and settings are all in the right places. I've now got 8.4.4.11! Thank you very much rtadams89!
Thank you for this!! I've been racking my brain trying to get to a rooted 8.4.4.11 with a good CWM recovery and this did it!
thanks.
Can anyone check to see if their BT is able to turn on....?
After doing this...my BT won't turn on.
rpavich said:
Can anyone check to see if their BT is able to turn on....?
After doing this...my BT won't turn on.
Click to expand...
Click to collapse
My bluetooth works fine, using it right now. Did you tweak anyhting else on your TF?
Well done!
I still have the update notification, but "About" shows x.11.
Screen seems both brighter & to have smoother transitions.
-bZj
Does this also give you the Nvidia boot animation?
Is it possible to get a .zip for the WW version?
down8 said:
Well done!
I still have the update notification, but "About" shows x.11.
Screen seems both brighter & to have smoother transitions.
-bZj
Click to expand...
Click to collapse
Try clearing data for the "dmclient" app.
AllTheWay said:
Does this also give you the Nvidia boot animation?
Click to expand...
Click to collapse
Yes. Anything new or updated is included.
rtadams89 said:
Try clearing data for the "dmclient" app.
Click to expand...
Click to collapse
Thanks!
rtadams89 said:
Yes. Anything new or updated is included.
Click to expand...
Click to collapse
My transformer still has the "Transformer" boot animation I added - wasn't replaced when using this file to update.
-bZj
[email protected] said:
Is it possible to get a .zip for the WW version?
Click to expand...
Click to collapse
+1, also interested on this
down8 said:
Thanks!My transformer still has the "Transformer" boot animation I added - wasn't replaced when using this file to update.
-bZj
Click to expand...
Click to collapse
That is the boot animation I use, and I may have accidentally included this in the zip. If you want the real 8.4.4.11 animation, you can download the "update" 8.4.4.11 zip file that has been posted on xda and inside you will find that boot animation.
[email protected] said:
Is it possible to get a .zip for the WW version?
Click to expand...
Click to collapse
Since I don't have a WW version myself, I don't have a need to do this and quite frankly because I don't have much free time, I don't want to say I'll do something and then not follow through. Further, I'm not sure I can install the WW versions on my US transformer. That said, I will see if I can whip one together. If you get impatient waiting, you can follow the same process I did and make one yourself:
Backup your current ROM/setup
Wipe your device (leaving CWR in place)
Install the stock 8.4.4.5 WW with the ZIP found on XDA
"Update" to 8.4.4.11 using the update zip found on XDA
Backup this new 8.4.4.11 ROM
Restore to your first backup
Take the backup of the 8.4.4.11 ROM you made last, and use your computer to "unyaffs" it
You will now have 8.4.4.11 versions of all the system files; Look at the updater-script file in the 8.4.4.11 update zip and remove any files you just "unyaffs"ed that aren't mentioned in there
Put all of the remaining files (in their folder structure) into a zip file
Copy the updater-script (and it's folder structure) from my download to your zip file
Verify that your final zip looks like the one I posted
You should then have a ZIP file that will bring all the files on your device up to 8.4.4.11 WW without touching any of your other files (like su).
My BT doesn't turn on either.
I went to this as a stepping stone while recovering from a failed root. Went to an older stock than this update. I notice a few slow downs here and there and BT not working, but that's about it.
What I would really love is an image of 8.4.4.11 stock/rooted. I like having it rooted for things like Titanium, but I still like having the stock image. I can't seem to get back to that now.
Link is down, Dropbox says too much traffic. Rapidshare/MUpload?
This is a general CWM question but I could not find any place better to post on XDA, so excuse this if incorrect location.
I have flashed all the Skyrocket ICS roms in the past few days to see which I liked best. Before I flashed a new one, I would make a CWM backup of the current one. Wanting to easily be able to identify the files, I appended the rom name to the end of the CWM filenames after deleting all the characters after the date, which appeared to be a GMT time stamp. Now, when I try to restore any of those files, I get an MD5 checksum error. I am only assuming that this is due to changing the filename and not some other problem. Anyone have any ideas on how to fix this? TIA.
phoneturf said:
This is a general CWM question but I could not find any place better to post on XDA, so excuse this if incorrect location.
I have flashed all the Skyrocket ICS roms in the past few days to see which I liked best. Before I flashed a new one, I would make a CWM backup of the current one. Wanting to easily be able to identify the files, I appended the rom name to the end of the CWM filenames after deleting all the characters after the date, which appeared to be a GMT time stamp. Now, when I try to restore any of those files, I get an MD5 checksum error. I am only assuming that this is due to changing the filename and not some other problem. Anyone have any ideas on how to fix this? TIA.
Click to expand...
Click to collapse
Are you talking about the folder name? Because that shouldnt affect it. Inside the folder that is created for each backup, there are backup files which dont have any dates/times in the filename itself.
I vaguely remember reading about this, but I can't recall how it was resolved. Try updating your can to 5.5.0.4 Touch or 5.8.1.3 (?? something along those lines) and seeing if that resolves it. Outside if that I must ask the obvious, did u Google "md5 checksum error cwm"?
Are you using the same CWM version as you did when you backed up? If you didnt, then thats one reason. You have to stay on the same CWM version, many of these CWM versions floating around have different fixes in there.
One way around this is to go to Advanced Restore and restore all the IMG files from there.
Dixit
ihtfp69 said:
I figured I would post this fix here in case anyone else ran into this problem. This is assuming you did not change the folder names and let Clockworkmod create them. I haven't had it happen until today, but it's not a nice message to see when you are trying to do a restore.
Code:
Checking MD5 sums...
MD5 mismatch!
Do this to fix:
To fix this problem use the code below. Substitute the final folder name for the backup you need to fix.
Code:
adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
When that finishes, re-run the restore and everything should be fine.
NOTE: As rpearl stated, there could be something really wrong with your nandroid, so use this tutorial as a learning experience and not a fix-all. In my case, everything was fine after restoring. However, that may not always be the case. Do this with caution.
Click to expand...
Click to collapse
Use this method to potentially fix.
dixit said:
Are you using the same CWM version as you did when you backed up?
Dixit
Click to expand...
Click to collapse
That is correct on most of them. I updated to CWM Touch for the last one, but it did not restore either. To check this out, I just did a backup and without changing the name did a restore and it worked fine. The thing that was odd in the backups that would not restore was that it immediately bombed out of the checksum each time as if it was checking the name itself first.
That is brilliant. I did not realize you could generate the MD5 from ADB and stick it right into the folder. Thanks!
The few times this md5 mis-match has happened to me was because (a) the backup was actually messed up (check folder size) probably due to corruption or (b) my SD card was out of space. I've always renamed my backup set similar to yours (I append the ROM name) and it never affects the restore.
bdbx18 said:
The few times this md5 mis-match has happened to me was because (a) the backup was actually messed up (check folder size) probably due to corruption or (b) my SD card was out of space. I've always renamed my backup set similar to yours (I append the ROM name) and it never affects the restore.
Click to expand...
Click to collapse
Are you using touch or standard CWM? I wonder if this only happens in touch version. I will try this in the next few days.
I changed the name of one of the backups I created with CWM touch and it restored fine using touch. I suppose my earlier problem may have been trying to restore a backup created with old CWM using touch version.
well since you are on the subject cwm touch im making a nanadroid backup of my current ics rom right now as i speak. i started about an hour ago and its still on the backing up data part. when i used the older version to make backups i dont remember it taking this long. have any of you had cwm touch take well its been a little over an hour now? i do have more apps on my phone now than i did the last time i made a backup would that matter? should i just jerk the battery out and go back to the older version of cwm i was using? thanks ahead of time for any advice / help you may give i would appreciate it. im trying to backup this rom cause i want to flash a different modem cause the ics modem form the leak is crap and need a backup in case it dont work..
garydv2002 said:
well since you are on the subject cwm touch im making a nanadroid backup of my current ics rom right now as i speak. i started about an hour ago and its still on the backing up data part. when i used the older version to make backups i dont remember it taking this long. have any of you had cwm touch take well its been a little over an hour now? i do have more apps on my phone now than i did the last time i made a backup would that matter? should i just jerk the battery out and go back to the older version of cwm i was using? thanks ahead of time for any advice / help you may give i would appreciate it. im trying to backup this rom cause i want to flash a different modem cause the ics modem form the leak is crap and need a backup in case it dont work..
Click to expand...
Click to collapse
If you are using sk8erwitskil version of the CWM touch (ClockworkMod TOUCH 5.5.0.4 v3.5) then most likely you didnt follow one of the directions on the front page. This is a known issue. Here it is again. You need to create that file on the location you backing upto.
For CWM to recognize the .hidenandroidprogress file you need to boot into CWM and go to mounts and storage>>mount /sdcard then go back to backup & restore and make a restore and it should work everytime (as long as you do the steps in that order and you have the .hidenandroidprogress file in /sdcard/clockworkmod & /sdcard/external_sd/clockworkmod folders)
There is a known bug in ClockworkMod 5.5.0.4 that long file names can POSSIBLY cause backups to hang. There is a solution/workaround:
•boot into recovery
•try to make a backup (no matter if it passes or fails proceed to next step)
•either through terminal emulator or through adb run the following command EXACTLY:
Code:
touch /sdcard/clockworkmod/.hidenandroidprogress
•if you are backing up to external sdcard then run the following:
Code:
touch /sdcard/external_sd/clockworkmod/.hidenandroidprogress
im using 5.8.1.3 hercules that i got from the dev section. is this a known issue with it to?
garydv2002 said:
im using 5.8.1.3 hercules that i got from the dev section. is this a known issue with it to?
Click to expand...
Click to collapse
Not sure, I used that for awhile but then went back to the other touch and Ive had those two files still in my directories.
I would go ahead and create those two files (one for internal SD and one for external SD if you got one you are using that is) and try it again. Make sure you call that file exactly the way it is, or copy/paste the code identically if you do it through ADB.
Dixit
garydv2002 said:
im using 5.8.1.3 hercules that i got from the dev section. is this a known issue with it to?
Click to expand...
Click to collapse
I use that one, takes less than 5 minutes on my class 10 sd.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Well the crazy thing is after sitting there over an hour waiting I finally took out the battery and even though it never said complete all the files are there but I still don't trust that it made a good backup so I deleted those files tried putting in the code above and it still would not work so I flashed back to version 5.0.2.0 thats not touch and it made a perfect backup in under 2 minutes. Might be one of those it just ain't gonna work right on this specific phone thing or it could be the little green gremlins at it again lol... who knows.. I'll just wait for new version of touch to come along and try it. It won't be long till a newer greater version comes along as fast as technology is going today.. thanks for the help. I'm learning more and more each day from you guys on xda.....
Sent from my SAMSUNG-SGH-I727 using XDA
Not sure if this is the cause of the issue but for nandroid backups you can't make a folder name with spaces otherwise you will get an md5 sum error. Try renaming the folder with underscores instead of spaces
Initial phone stats: DS Mod 1.55.531.3, hboot 1.45.0013, s-on/unlocked via HTC unlocker.
I'm trying to update my own phone to 1.63.531.2 via the PG59IMG.zip file found here, http://forum.xda-developers.com/showpost.php?p=17424340&postcount=24 , but I'm running into problems applying this update and keeping it after restoring a Nandroid backup. It would be a huge amount of work to set up my phone from square one, and I'd like to avoid the process if at all possible.
The steps I've followed (twice, now, with no joy) are the following:
* apply the update through the PG59IMG.zip
* flash CWM 5.0.2.7
* flash Superuser
* restore most recent Nandroid backup
* flash 1.63.531.2 boot image (for wi-fi fix)
And this puts me back at my starting point, with the 1.63.531.2 update not applied.
I know I'm going about this the wrong way, but I can't figure out the correct method to make this work. The fact that I flashed the DS Mod 1.55.531.3 ROM back after unlocking might have something to do with this, however, I just can't nail down why. Really could some help to make this work.
TIA for any suggestions --
--
KingCheetah
hey, real quick, after flashing the 1.63.531.2 update, instead of restoring your full nandoid of 1.55.531.3, go to 'advanced restore', choose that nandroid, and choose only 'restore data'. that will put all your apps and data onto the new update, rather than flashing you all the way back to what you had before.
you could also backup and restore your data with an app called Mybackup Root, or some people use Titanium Backup. I personally like using the advanced data restore in CWM, or else Mybackup.
Yogi, I thought your suggestion would be a smoking gun. However, I'm having the same problem as described in this thread: http://forum.xda-developers.com/showthread.php?p=25431819#post25431819
Might you have any suggestions for addressing the md5 problem? I'm coming up empty...
Thanks for your help --
--
KingChetah
yeah, come to think of it, I've had that problem before as well. did you try what xmc suggested? also, perhaps try the Modaco 4.0.0.9 version of CWM to do the advanced data restore... if my memory serves me, I have had more success overall with that version. unfortunately that's about all I got!
the other sugestion would be to flash your full nandroid, then use Mybackup Root to back everything up. then after updating, DL the app again and restore.
good luck and keep us posted!
yogi2010 said:
yeah, come to think of it, I've had that problem before as well. did you try what xmc suggested?
Click to expand...
Click to collapse
Yes, and for the backup I want to restore, all the md5s are the same between the files and what is listed in the nandroid.md5 file. So, the method XMC suggested really doesn't do anything.
yogi2010 said:
also, perhaps try the Modaco 4.0.0.9 version of CWM to do the advanced data restore... if my memory serves me, I have had more success overall with that version. unfortunately that's about all I got!
Click to expand...
Click to collapse
Hmm, okay, I'll give that a try. Weird that CWM 5.0.2.7 has this problem. Also frustrating.
yogi2010 said:
the other sugestion would be to flash your full nandroid, then use Mybackup Root to back everything up. then after updating, DL the app again and restore.
Click to expand...
Click to collapse
I'll keep this as the last resort, because I'd rather not have to download an app for just this purpose. Nandroid backups have served me fine so far. Call me a minimalist.
I'll try Modaco and see what happens. Thanks much for the idea to try.
--
King Cheetah
Sadness
Using Modaco didn't work. Although the Advanced Restore sees the file and appears to run successfully, it says it can't find a data.img file and an Android.img file, so it doesn't restore the info.
So, I guess it's down to trying Mybackup Root and see what happens. Getting tired of redoing this process over and over.
Why can't things "just work" in these situations?
--
KingCheetah
check the other thread....problems with restoring backup
---------- Post added at 05:11 PM ---------- Previous post was at 05:08 PM ----------
or actually...just flash the data.img through fastboot....its ten times easier
but the data.img in the same directory as adb and fastboot....then run the two commands with your phone in the bootloader
fastboot erase data
fastboot flash data data.img
xmc wildchild22 said:
or actually...just flash the data.img through fastboot....its ten times easier
but the data.img in the same directory as adb and fastboot....then run the two commands with your phone in the bootloader
fastboot erase data
fastboot flash data data.img
Click to expand...
Click to collapse
The problem with this is the file "data.img" doesn't exist in a Nandroid backup. As I stated in my previous message, the Advanced Restore process tossed up a message that the file didn't exist (which is correct).
The files within a given Nandroid backup folder are the following:
.android_secure.vfat.tar
boot.img
cache.ext4.tar
data.ext4.tar
nandroid.md5
recovery.img
system.ext4.tar
From the Advanced Restore problem thread (http://forum.xda-developers.com/showthread.php?t=1624319):
xmc wildchild22 said:
then take the system.img from the 1.63 update and put in replace of the nandroids one....then redo the md5 checksum for the system.img like i had showed before
Click to expand...
Click to collapse
I would love to try this, but since the 1.63 update is a PM59IMG.zip, I can't open it with a zip file manager--it throws up a "central directory not found" error. Unless there's another program besides 7zip that's needed to handle this type of zip file...
Edit: I just realized that, as you can see from the file list above, a Nandroid backup also doesn't have a "system.img" file--it has a "system.ext4.tar," but not "system.img." So being able to pull anything from a PM59IMG.zip file is a moot point at this juncture.
Banging one's head against the keyboard does little constructive good, but it's really tempting at this point --
--
KingCheetah
just try opening it with a plain windows explorer
xmc wildchild22 said:
just try opening it with a plain windows explorer
Click to expand...
Click to collapse
Using the "Explore" option from the right-click context menu in Windows Explorer gives the following error: "The Compressed (zipped) Folder is invalid or corrupted." (Since archive files on my laptop are associated with 7zip, this is the only method by which I can access Win XP's native archive file handling.)
This has been the case with all PM59IMG.zip files--they don't register as normal zip files.
Thanks for the suggestion, though --
--
KingCheetah
hmm...maybe tht zip is corrupted because it works for me....DL this --> http://tinyw.in/Mzg2
Nope, not corrupted because it works just fine to update my phone to 1.63 (as stated before, I've done this twice now). Also, that's the exact same source from whence I downloaded my copy of the file. The PM59MG.zip for 1.55.531.3 gives exactly the same error, and I used that without difficulty as well.
KingCheetah said:
Nope, not corrupted because it works just fine to update my phone to 1.63 (as stated before, I've done this twice now). Also, that's the exact same source from whence I downloaded my copy of the file. The PM59MG.zip for 1.55.531.3 gives exactly the same error, and I used that without difficulty as well.
Click to expand...
Click to collapse
Use winrar to open the PG59IMG.zip files - that's what I used to make all the custom ones with, and also what I used to open the leaked ones we started from.
You won't be able to edit existing leaked ones, because they are locked and have an HTC signature.
Sent from a digital distance.
Thanks for the pointer, Blue, and I'll keep this in mind. But as I added to my previous post (#8), I realized that a Nandroid backup doesn't have a "system.img" file--it has a "system.ext4.tar," but not "system.img." So being able to pull anything from a PM59IMG.zip file is a moot point at this juncture.
I think I'm going to have to wait for a 1.63 ROM that can be installed through CWM rather than the PM59IMG.zip method. The DS Mod 1.55.531.3 worked well for me, and all apps/data were just there after I flashed it. Maybe I just got lucky with the process I followed previously, who knows? (http://forum.xda-developers.com/showthread.php?t=1508406&page=4 post #39)
At any rate, I've got a truly mean headache from working on this all day. Time for a break with a bit of ice on ye old cervical vertebrae.
Thanks again for chiming in --
--
KingCheetah
No prob, didn't read through and shot from the hip on the last post I saw, out at dinner and skimming the forums on smoke breaks
Sent from a digital distance.
does anyone know the deal with the implementation of tar backups? I think that came into play at some point, and I wonder if that has anything to do with anything.
I just checked a backup I made with the Modaco CWM, and the files in it are all .img files, including data. and I know for a fact I have done backups and advanced data restores with that recovery. it would be a hassle, but if you get re-energized you might make the backup and do the restore with Modaco. definitely would be a hassle if it didn't work, but you could also make a backup with Mybackup, and have that ready too, as well as probably have a data.img to try and flash thru fastboot like xmc suggested.
anyway, hopefully we'll get this all sorted out. take it easy!
well .tar are used ever since cwm started working with ext4....maybe imgs are only ext3 or lower or its just inefficient
On that note, I did use the modaco 4.0.0.9 recovery to make the nandroids I pulled the system images from to get the bases from which I de-odexed, and when finished I uploaded to my host and they are the de-odexed bases I posted in dev.
I am pretty sure I went with modaco recovery for that because cwm 5.0.2.7 output tar files and it just saved a step in the process.
If you are working with the .tar files then jump on linux to unarchive them if that's what you are trying to do.
I just ran the deodex process using windows, because the first working deodex tool I found was a windows tool.
Generally I use modaco .9 for nandroids I want to work with in windows, and cwm 5 for nandroids I want to work with in linux.
We're probably leaving the restaurant soon, if we split up I'll actually read back through the thread when I get home and see if I have anything else to add.
Sent from a digital distance.
Yogi, you're brilliant!
yogi2010 said:
I just checked a backup I made with the Modaco CWM, and the files in it are all .img files, including data. and I know for a fact I have done backups and advanced data restores with that recovery.
Click to expand...
Click to collapse
[facepalm] Of course! This is why my Advanced Restore attempt with Modaco failed--because I used the CWM 5.0.2.7 backup, which did not have the files Modaco would have referenced. Duh! I wasn't even thinking along the lines of a file type mismatch between the two recoveries. Baka baka baka...
yogi2010 said:
it would be a hassle, but if you get re-energized you might make the backup and do the restore with Modaco. definitely would be a hassle if it didn't work, but you could also make a backup with Mybackup, and have that ready too, as well as probably have a data.img to try and flash thru fastboot like xmc suggested.
Click to expand...
Click to collapse
At this point, not a hassle, but the best chance to accomplish this thing with a minimum of fuss and bother. I'll give this a shot right after a bit 'o java. Thank you, Yogi, for highlighting something that should have been obvious to me when Modaco gave the error message that "data.img" didn't exist. Oy!
However, this still leaves unanswered the question of why CWM 5.0.2.7 is tossing up the md5 mismatch error when one tries to use Advance Restore, and that files aren't seen by CWM via Advance Restore until one accesses regular Restore. Paperskye is having the exact same problem in this thread: http://forum.xda-developers.com/showthread.php?t=1624319 . Should this be brought to the attention of the CWM devs? It really seems like a rather show-stopping error for CWM...unless Advanced Restore isn't really used with 5.0.2.7 and the MT4GS. There just doesn't seem to be a good reason for the observed behavior.
Many thanks for your encouragement. I'll report back with results on the next try with Modaco --
--
KingCheetah
It's a beautiful thing!
Using Modaco for my backup prior to the update, then Advanced Restore of data afterward = perfect restore of my phone environment with 1.63 on board. Done with as little fuss as I was hoping to encounter. Yogi, you get the prize. The only thing I had to manually put back was my custom boot animation, but that's trivial.
I think I'll just leave Modaco on as my recovery for now, since AR is functional with it and CWM 5.0.2.7 is not. Makes me wonder, from just an everyday backup standpoint, is there any real advantage of CWM over Modaco? I wish there was more information on how the recovery module functions on the CWM website--I'd like to read up on it for educational purposes. Guess I'll do a Google to find more.
So ridiculously happy right now. In a stew of things going wrong, at least something went right.
Big rumbling purr of gratitude --
--
KingCheetah