Not sure about about the free version, but I know the paid version of Titanium Backup has the option to create an "update.zip" file which I had assumed would have been able to be flashed from recovery. I tried and it didn't worked because it complained about not being signed. I know I should have thought of that, but it occurred to me I have no idea about how to properly sign a zip file. Can anyone point me in the right direction?
check thread # 709117 on xda-developers.com
I'm new and wasn't allowed to post the link, even though it was not an "outside link"... don't know why, but anyway, its on-topic to update.zip
gospodinwizard said:
Not sure about about the free version, but I know the paid version of Titanium Backup has the option to create an "update.zip" file which I had assumed would have been able to be flashed from recovery. I tried and it didn't worked because it complained about not being signed. I know I should have thought of that, but it occurred to me I have no idea about how to properly sign a zip file. Can anyone point me in the right direction?
Click to expand...
Click to collapse
I know that the HTC android kitchen has a tool for signing. It's somewhere in the Android dev general or software thread
Sent from my Eris Lightning 3.02
As previous Title says...
Did you check thread # 709117 on xda-developers.com?
Thanks for the tip about the thread. No, I had not seen it but have already pretty much got the info contained therein thru email I've been exchanging with the app dev. At present, it seems his update-script does not play nicely with A2SD.
Related
I have spent the better part of 3 days on these forums. Tried Super1Click to no avail then followed instructions as in the Noob Guide and everything looked good.
The phone found the update.zip file, did the whole reinstalling pkgs thing and rebooted.
But I can't find the superuser icon and when I downloaded Titanium backup it said I was not rooted.
I have the 959 UVj16 with Eclair 2.1
I would greatly appreciate some assistance. I honestly spent untold hours trying to find the answer before I asked.
Why go through all that. Just use z4root found here:
http://www.4shared.com/file/12OzPNJZ/z4root130.htm
Download from your phone.installs like a normal apk app and open and click root. Installs root and then all done.simple!
Sent from my SGH-T959 using XDA App
That link says not valid on phone but I can download to PC, where do I put it so that it will install?
1. should I remove uninstall.zip first from previous try
2. do I need to do anything with this file, ie. move from downloads to somewhere else?
nevermind, downloading from softpedia.
One click simple! Worked perfectly, thanks a million!!
did you rename the update.zip file? If you did, you shouldn't have.
You just had to place the file on your sd card.
yeah, OP PM me what didnt work on the noob guide.... please explain everything you did. There is no reason that file I uploaded should not work just fine. I need to make certain for others though (nobody else has said anything to me with an issue).
Can't post in the Dev section yet. That's what I get for trolling around since you guys showed me how to root my OG Droid. Thanks, btw.
Now, I'm trying to root my Tbolt, and when I click on the downgrade RUU file to see the contents it says the file is invalid. So, then I tried to extract it, to see what would happen, but same message.
I also downloaded the exploits.zip and the final PG05IMG.zip and was able to view both their contents. Plus, I had to extract the exploits file to the SDK directory, and it worked fine.
So, I then downloaded from all three mirrors, but same result. And then I went to the rom.galaxysense.com site and downloaded from there, but same result. Am I the only one having retarditis? Is the file jacked, or just run-of-the-mill incompetence on my part???
Thanks to whomever takes the time to help out. And thanks for all the help everyone puts out there for the rest of us.
I am confused by your massive amount of words in this post. You need to say maybe, 20 things total.
First, you don't need to open anything, you simply need to put the ZIP onto your SD card and reboot into Hboot.
The only ZIP you need to unzip is the exploit.zip.
I don't need to extract them, I get that. I was looking in the zip files out of curiosity, but when the one file said it was an invalid file type I didn't want to put it on my SD card. That's closer to 20 words, hope that makes sense.
drweltman said:
I don't need to extract them, I get that. I was looking in the zip files out of curiosity, but when the one file said it was an invalid file type I didn't want to put it on my SD card. That's closer to 20 words, hope that makes sense.
Click to expand...
Click to collapse
haha, I was feeling like being a smart ass. The RUU needs to be renamed to PG05IMG.ZIP and put on the sd card, then you need to reboot into bootloader.
Also to add, I came into the problem where I renamed to PG05IMG.zip It was already zipped so just had to name it PG05IMG Then it worked for me.
Thanks for the help. I guess no one understood what I was saying, but since no one else has mentioned the file being corrupted I guess I'll use it and hope for the best.
That's why I mentioned that the other two zip files would let me look at their contents, but the third one said invalid file type. I thought it was clear, but my bad...
Either way, here's another post towards getting out of noob post restrictions!
drweltman said:
Thanks for the help. I guess no one understood what I was saying, but since no one else has mentioned the file being corrupted I guess I'll use it and hope for the best.
That's why I mentioned that the other two zip files would let me look at their contents, but the third one said invalid file type. I thought it was clear, but my bad...
Either way, here's another post towards getting out of noob post restrictions!
Click to expand...
Click to collapse
I'm pretty sure that the RUU downgrade is not something you can open. Just make sure the checksum is valid and you're good to go.
I had tried to flash the RUU after I first rooted becuase I was having location issues. It would check the PG05IMG.ZIP and go back to the Hboot screen. I had flashed another rom so I didn't mess with it any further.
drweltman said:
Thanks for the help. I guess no one understood what I was saying, but since no one else has mentioned the file being corrupted I guess I'll use it and hope for the best.
That's why I mentioned that the other two zip files would let me look at their contents, but the third one said invalid file type. I thought it was clear, but my bad...
Either way, here's another post towards getting out of noob post restrictions!
Click to expand...
Click to collapse
Finally! I've been looking through threads forever in search of this very issue. I was all set on rooting last night, and just like you, the Mecha_RUU file wouldn't unzip, said it was invalid, etc. I stopped right there out of fear that I'd get burned pressing on with one of the key files "broken." Have you rooted since with no trouble?
The best thing to always do is get an MD5 sum for the file and compare it to the root post. I have rooted my thunderbolt twice now and never had a problem.
If the md5sum is correct then you should be fine. Also remember in Windows, it hides the extensions. So when you rename your files do not add the extension as it is already there.
You can show the extensions by changing the folder settings.
Downgrade wont flash
1) Power down phone
2) Power up phone holding volume down
3)No option to upgrade just starts checking files
4) Third check is the downgrade file, starts loading
5) Fails because the file is Older than the main
Ive seen other threads touch on this but no one answer it. Any help with this would be greatly appreciated. Also I have already updated to the 7/8/11 OTA.
Thanks,
JDBSC1 said:
1) Power down phone
2) Power up phone holding volume down
3)No option to upgrade just starts checking files
4) Third check is the downgrade file, starts loading
5) Fails because the file is Older than the main
Ive seen other threads touch on this but no one answer it. Any help with this would be greatly appreciated. Also I have already updated to the 7/8/11 OTA.
Thanks,
Click to expand...
Click to collapse
as in "MAIN VERSION HIGHER" error while flashing?
Not sure what exactly you are trying to do but read this post where it discusses about getting that error.
http://forum.xda-developers.com/showthread.php?t=1008824
Absolute_Zero said:
as in "MAIN VERSION HIGHER" error while flashing?
Not sure what exactly you are trying to do but read this post where it discusses about getting that error.
http://forum.xda-developers.com/showthread.php?t=1008824
Click to expand...
Click to collapse
I appreciate the thread link. That's exactly the error I'm getting. Problem is I'm supposed to downgrade to obtain root ( or at least that's one of the steps). I have downloaded this downgrade file from multiple links and verified its the correct one to use in this step and I always receive the "main version higher" issue. Should I be using a different file to downgrade or is this no longer an option for root since the 7/8/11 ota?
Sent from my ADR6400L using Tapatalk
Interesting..
I wiped everything ADB and Thunderbolt related from my PC.
Then I downloaded the easy root from this link
http://forum.xda-developers.com/showthread.php?t=1005292&highlight=easyroot
Then I downloaded and opened the pdf instructions on the same page.
Then I followed the written directions to a T!
Worked like a charm. Steps 1, 2, and 3 hung up and had to be done multiple times but I finally got through it. Some other links if found with this same method were misleading as to doing the steps over again but he accounted for this in his pdf instructions and if you follow it to the letter you should be good.
I keep reading in threads to check md5sums before doing anything. Would someone care to explain why and how to go about doing so? Is this to be done prior to installing a ROM?
Just trying to get a better understanding of things.
Figured it out before someone gave me the old spoon fed line.
Anyway for those of you that might be a bit confused like myself here is a link to a md5 checker.
http://www.softpedia.com/get/System/File-Management/MD5-Checker.shtml
Run exe. after unzipping.
search for file you want checked
Good to go
Guess i've been fairly lucky up till now considering i have never performed this step prior to installing anything.
you can also go to the market and download an app called ManD5....it is also a md5sum checker...
hogowner said:
you can also go to the market and download an app called ManD5....it is also a md5sum checker...
Click to expand...
Click to collapse
This is what I use - works great.
hogowner said:
you can also go to the market and download an app called ManD5....it is also a md5sum checker...
Click to expand...
Click to collapse
I thought the idea was to check the file prior to putting it on your phone?
EDIT: Just tried that app and it works great. Thanks
Dxun said:
I thought the idea was to check the file prior to putting it on your phone?
EDIT: Just tried that app and it works great. Thanks
Click to expand...
Click to collapse
The idea is to check it prior to actually installing it on the phone, not just before it is copied to the storage card. Theoretically, it could get corrupted at any point it is copied/moved/etc, so the ideal time to check is just prior to the step where you flash/install/reboot/whatever.
I actually just use Astro file explorer on my phone. You can look at the details of a file, and it will compute the md5 for it.
My favorite free shell extension for MDS - HashTab
Win & Mac versions.
Thanks for all this info peeps. Many people, including myself, are afraid to ask a stupid question at times.
Dxun said:
Thanks for all this info peeps. Many people, including myself, are afraid to ask a stupid question at times.
Click to expand...
Click to collapse
I have asked plenty of stupid questions in the past...and I EXPECT to ask some in the future LOL
You can also do it in a command line (Terminal) just type
Code:
md5sum <path-to-file>/<file-name>
FreemanB said:
The idea is to check it prior to actually installing it on the phone, not just before it is copied to the storage card. Theoretically, it could get corrupted at any point it is copied/moved/etc, so the ideal time to check is just prior to the step where you flash/install/reboot/whatever.
I actually just use Astro file explorer on my phone. You can look at the details of a file, and it will compute the md5 for it.
Click to expand...
Click to collapse
I find it's easier to check on my PC after I D/l so I use TeraCopy when copying files. Copies then goes back and checks them.
Hey everyone, i am running CM10 and going to use Cyandelta but when i tried it, it reinstalled all the files i removed and changed my su binary(which freaked me out), so after i installed the cyandelta update, i would like to run the update.zip to remove the things i dont' want. I am sure that something is wrong with this script and just want someone to double check it for me, thanks in advanced P.S. i am aware that it is not signed
i think i have the copy su incorrect can someone confirm?
Moved by request of OP
prbassplayer said:
Moved by request of OP
Click to expand...
Click to collapse
Thank you
Ok, this may be answered elsewhere, I don't know. "Search is temporarily unavailable" I am trying to understand how I am supposed to work with the backup from CWM. I understand that I should have a System image that I can work in, but what I have is 3 files in its place. System.ext4.tar, System.ext4.tar.a, and System.ext4.tar.b. All three files are broken to some degree.
System.ext4.tar is a zero byte file.
System.ext4.tar.a appears to be a spanned tar file that 7ZIP/WinRAR simply think was cut-off (never asks for the second file, and complains of unexpected End of Archive)
System.ext.4.tar.b appears to be the second part of the archive, but nothing will open it.
So, how do I get to a point I have a complete archive that I can edit? Or do I need to use different software than CWM to back up the phone?
Thanks for the help guys.
waldojim said:
Ok, this may be answered elsewhere, I don't know. "Search is temporarily unavailable" I am trying to understand how I am supposed to work with the backup from CWM. I understand that I should have a System image that I can work in, but what I have is 3 files in its place. System.ext4.tar, System.ext4.tar.a, and System.ext4.tar.b. All three files are broken to some degree.
System.ext4.tar is a zero byte file.
System.ext4.tar.a appears to be a spanned tar file that 7ZIP/WinRAR simply think was cut-off (never asks for the second file, and complains of unexpected End of Archive)
System.ext.4.tar.b appears to be the second part of the archive, but nothing will open it.
So, how do I get to a point I have a complete archive that I can edit? Or do I need to use different software than CWM to back up the phone?
Thanks for the help guys.
Click to expand...
Click to collapse
Well, I found a solution for now. Fire up Linux, use cat to combine all three files, then use tar to extract the contents. Not sure why this needed split in the first place, but at least the files can be extracted.
I have managed to remove the APKs I do not want, and made a new system.ext4.tar file (all in Linux), but need to know what else I have to do to make the system image usable.
I found several guides on making a ZIP file, but I didn't want to necessarily go through all that. I backed up everything, so what I would like to know, is what all needs to change so that I can use the separate files as they are, and simply do a CWM "restore" function?
I know I sound like a complete noob at this point, and will deal with the related comments. However, please understand, I don't want the heavily modified rom packs. I simply wanted a rom VOID of all the Verizon bloatware, and have the Verizon tethering restraints removed. I have them all disabled now, and 3rd party tethering is working quite well. So I would rather not have that garbage wasting space. Right now, it looks like I may save 250MB or so.
Any help would be appreciated. Thanks.
waldojim said:
I have managed to remove the APKs I do not want, and made a new system.ext4.tar file (all in Linux), but need to know what else I have to do to make the system image usable.
I found several guides on making a ZIP file, but I didn't want to necessarily go through all that. I backed up everything, so what I would like to know, is what all needs to change so that I can use the separate files as they are, and simply do a CWM "restore" function?
I know I sound like a complete noob at this point, and will deal with the related comments. However, please understand, I don't want the heavily modified rom packs. I simply wanted a rom VOID of all the Verizon bloatware, and have the Verizon tethering restraints removed. I have them all disabled now, and 3rd party tethering is working quite well. So I would rather not have that garbage wasting space. Right now, it looks like I may save 250MB or so.
Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
Backups really aren't meant to be unzipped and played with. Usually bloat removal is done while booted into the system or you can unpackage a Rom and remove the bloat there and then repackage it and flash it then make your backup that doesn't contain any bloat. Using the xda kitchen tools from dsxda I believe is the name
Sent from my HTC6435LVW using XDA Premium HD app
.torrented said:
Backups really aren't meant to be unzipped and played with. Usually bloat removal is done while booted into the system or you can unpackage a Rom and remove the bloat there and then repackage it and flash it then make your backup that doesn't contain any bloat. Using the xda kitchen tools from dsxda I believe is the name
Sent from my HTC6435LVW using XDA Premium HD app
Click to expand...
Click to collapse
I think this is where some of my confusion comes from - it was never zipped. There was a group of tarred files, an MD5sum and a few other items. But nothing there was zipped.
waldojim said:
I think this is where some of my confusion comes from - it was never zipped. There was a group of tarred files, an MD5sum and a few other items. But nothing there was zipped.
Click to expand...
Click to collapse
I guess what I meant to say by "zipped" was just in general they are compressed by the recovery in a way that it knows how to go and use them to restore data to the device.