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.
Related
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.
How would I go from s-off back to s-on?
Sent from my FroyoEris using XDA App
api1996 said:
How would I go from s-off back to s-on?
Sent from my FroyoEris using XDA App
Click to expand...
Click to collapse
Using fastboot from the PC, as in
Code:
fastboot flash hboot name-of-hboot-image.nb0
(The phone needs to be in FASTBOOT USB mode (coldstart with Send+End), and an acceptable USB driver needs to be installed on a Windows PC)
The S-OFF bootloader is happy to let you replace itself - it is running in memory when you interact with it, not directly from the NAND flash memory.
You can find the .nb0 files inside any of the HTC leak PB00IMG.ZIP ROMs, or the "rom.zip" files embedded within the RUUs. (Note that the built-in Windows "compressed folder" methods for extracting a zip file will not work with these HTC .zip files because of the way that HTC "signs" these zip files, but the 7zip Utiltity for Windows will work).
The 1.47.0000 S-ON bootloaders are only found in the MR1 and MR2 RUUs; all of the "Leak" PB00IMG.ZIP files from HTC (Leak-V1,-V2, and -V3) contain the 1.49.0000 S-ON bootloader.
[SIZE=+1]Please be aware that flashing the bootloader is the single most dangerous thing you can do to your phone, and that if you flash a corrupted file to the bootloader you will certainly hard-brick the device. You absolutely must VERIFY THE MD5 SIGNATURE of the bootloader .nb0 image file before using it with fastboot! Fastboot provides you absolutely no protection from errors! YOU HAVE BEEN WARNED! You can find checksums listed in this reference post[/SIZE]
For clarity, I will repeat them here:
Code:
RUU___MR1 38899da4e5e002e3be22900f5f4eb6f7 hboot_7501a_1.47.0000_091023.nb0
RUU___MR2 38899da4e5e002e3be22900f5f4eb6f7 hboot_7501a_1.47.0000_091023.nb0
Leak___V1 0717a252deb8eed89f33bf277959b91c hboot_7501a_1.49.0000_100124.nb0
Root_Leak 22d3c7082811170e70f308e3213b5d1f hboot_7501a_1.49.2000_100124.nb0
Leak___V2 0717a252deb8eed89f33bf277959b91c hboot_7501a_1.49.0000_100124.nb0
Leak___V3 0717a252deb8eed89f33bf277959b91c hboot_7501a_1.49.0000_100124.nb0
bftb0
PS I could swear I wrote a post essentially identical to this one within the last week
Can you please post a download link for either the MR2 or MR1 PB00IMG.zip files? I can't seem to find them.
api1996 said:
Can you please post a download link for either the MR2 or MR1 PB00IMG.zip files? I can't seem to find them.
Click to expand...
Click to collapse
[ Edit ] Updated - check Consolidated HTC Eris RUU/OTA/ROM URLs for the MR1 or MR2 PB00IMG.ZIP files - if you haven't already done the steps below. cheers! bftb0
I don't have a download link right now. If you want to wait a couple days, maybe I'll have something more convenient. In the meantime, the way to get these files is to run the associated RUU utility - but not all the way through. More on that in a second.
You can get the MR2 (1.17.605.1) RUU utility from this folder at shipped-roms.com - the MR2 link is the RUU_Desire_C_Verizon_WWE_1.17.605.1_release_signed_with_driver.exe link.
OK, now how do you "get" the PB00IMG.zip file out of the RUU?
Simple. You run the RUU right up to the point where you would normally be starting the install to the phone - but you don't do that. Leave the RUU running, don't terminate it yet. The point of doing this is so that the RUU unpacks all the temporary files it is going to use - including the "rom.zip" file. It puts all this unpacked junk in two temporary folders underneath your Windows user area, perhaps at
C:\Documents and Settings\<your_windows_user_name_here>\Local Settings\Temp
use your windows search capability to look for a big "rom.zip" file underneath there. (The two top-level folders will have long names that look like Windows registry keys). Note that you may have to diddle with your Windows Explorer folder settings to "Display Hidden Files".
Now copy the "rom.zip" file to some other location on your hard drive, and when the copy is complete, exit the RUU utility. (You can't do this until you have copied the file someplace else first, because all the temporary files get wiped when you exit the RUU).
You can then rename the "rom.zip" file to PB00IMG.ZIP. If I am not mistaken, the MD5 checksum of that particular (1.17.605.1) "rom.zip" file will be 9e9ad31f01bbcb05157443287f4f38dd
bftb0
PS. Note the "_with_driver.exe" part of the RUU file name. All the RUUs attempt to install a USB driver for the Eris on to your PC. Since MR1 and MR2 came out one year ago - a couple months after the consumer release of Windows 7, the drivers might not be the same quality as whatever you have on your machine now (if it in fact installs the driver despite the presence of an existing driver). Just a heads up in case it tries to kang a crappy driver into your Windoze box. You might want to take a restore point just before running the RUU in case you find you need to un-kang the driver from your PC.
Thanks for the download links. I had just extracted the rom.zip and found the bootloader and figgured that I should check the tread one more time. That's when I saw the edit! I guess I just have bad timing . Anyway, I went ahead and extracted the bootloader, here's a download link for the 1.47 S-ON bootloader from the MR2 update for anyone who wants it: http://www.multiupload.com/9300LRSFZP
Thanks
I just noticed that I forgot to mention that the way that HTC "signs" those "rom.zip" / "PB00IMG.ZIP" files makes the "compressed folder" handling in Windows unhappy, so you need to use some other tool on windows to unpack those .zip files. 7-Zip will do the job, though.
You obviously got past that, though.
bftb0
bftb0 said:
I just noticed that I forgot to mention that the way that HTC "signs" those "rom.zip" / "PB00IMG.ZIP" files makes the "compressed folder" handling in Windows unhappy, so you need to use some other tool on windows to unpack those .zip files. 7-Zip will do the job, though.
You obviously got past that, though.
bftb0
Click to expand...
Click to collapse
I used 7 zip. You mentioned it in your first response.
Sent from my FroyoEris using XDA App
api1996 said:
I used 7 zip. You mentioned it in your first response.
Sent from my FroyoEris using XDA App
Click to expand...
Click to collapse
. I thought I had read that someplace recently! LOL
Worked like a charm, thanks bftb0. BTW I'm getting my fifth Eris tomorrow, I got so tired of this I tried to get a different phone, they refused, so I went to best buy added a line and got a free DINC, more or less, I just have to pay an extra $10/month, I'm throwing my old Dare on that line so I don't have to pay for data. Now I can play with my Eris all I want and don't have to worry ruining my only phone
USSENTERNCC1701E said:
Worked like a charm, thanks bftb0. BTW I'm getting my fifth Eris tomorrow, I got so tired of this I tried to get a different phone, they refused, so I went to best buy added a line and got a free DINC, more or less, I just have to pay an extra $10/month, I'm throwing my old Dare on that line so I don't have to pay for data. Now I can play with my Eris all I want and don't have to worry ruining my only phone
Click to expand...
Click to collapse
I'm glad people are getting some use out of this stuff. 5th Eris? Holy crap, I guess I should feel lucky that the phone I got on drop day (Nov '09) is still hanging tough.
bftb0 said:
I'm glad people are getting some use out of this stuff. 5th Eris? Holy crap, I guess I should feel lucky that the phone I got on drop day (Nov '09) is still hanging tough.
Click to expand...
Click to collapse
No kidding, my first one was amazing, ran stable and cool, no trackball issues. I got some dirt in the speaker, when it blew out completely I just got it replaced. If I'd have know all the issues I'd be having with these refurbs I'd have just bought a bluetooth and called it good.
bftb0 said:
I'm glad people are getting some use out of this stuff. 5th Eris? Holy crap, I guess I should feel lucky that the phone I got on drop day (Nov '09) is still hanging tough.
Click to expand...
Click to collapse
Not for a lack of trying, though.
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).
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.
Having trouble booting into Cynogen. As far as I can tell, everything is flashedd correctly. I got the initramfs and zimage from here. They flashed fine and the system boots into the multi boot screen.
Then I copied the openaos-gingerbread-anoa-gen8_113301.img.gz from here to my device through the USB MSC renaming it to openaos-gingerbread.img.gz
I believe that the menu.lst file should update itself so there should be no need to edit the file. I had to edit the file anyway, not sure why. Tried editing it through np++ and got Ginger-Bread listed in the boot menu. Tried to boot into it but it just sat at the OpenAOS screen and did nothing. I left it on that screen for close to half an hour.
I then tried the menu.lst file that is linked to the post by gbohm but the same thing happened.
When I access recovery and start USB MSC again it shows a ~525MB file called openaos-gingerbread.img and it has a folder called openaos which has a subfolder called disabled. Nothing else.
I tried this off the back of a full wipe so there is nothing on the device at all. No archos FW or anything. Coming from UD 1.5
Any idea what might be going on?
Edit: one last note. This was all done on my Windows machine. Will try it on my ubuntu server tomorrow. That machine is just a little more awkwardly placed
Maybe be you edited the menu.let wrong
Lokk in my "OpenAOS Full Instructions Thread" for tips;-) here in general section
Lenn said:
Maybe be you edited the menu.let wrong
Lokk in my "OpenAOS Full Instructions Thread" for tips;-) here in general section
Click to expand...
Click to collapse
No. Like I already said lenn update your guide or mention that it is outdated and point to the wiki.
This is what I was afraid off, giving people wrong instructions and make it worse for them.
---------
d31b0y you did it correct. Just copy openaos-gingerbread-anoa-gen8_113301.img.gz and rename it to openaos-gingerbread.img.gz
The menu.lst should update itself and create an extra Gingerbread entry in the bootmenu.
Some things that could go wrong is that you didn't safely umount or remove the drive. So the image got corrupted.
Another thing is that you maybe didn't rename it correctly using capital letters perhaps.
However my best guess is that the image got corrupted during download or during copy renaming and not safely remove the drive.
This http://dev.openaos.org/wiki/AndroidInstall_CM7_Gingerbread is the guide to follow and no other.
We from openaos recommend using linux to do the procedure, it is also much easier for us to support when coming for questions on irc http://www.openaos.org/chat
Maurice
Sorry, but stil >> 90% of users have a windows maschine.
Maybee you should also think about your target audience.
fzelle said:
Sorry, but stil >> 90% of users have a windows maschine.
Maybee you should also think about your target audience.
Click to expand...
Click to collapse
Yes, I know. Windows shouldn't be a problem for the procedure. It is only easier for us when answering questions, because we are almost all on linux machines. That is why I said we recommend it, not that we say you must use it.
Some issues for windows users. It hides known file extensions by default which could be a problem when renaming files. Windows doesn't care about cap letters, Linux does. A file named foo.img.gz is different from Foo.img.gz .
Maurice
divx118 said:
No. Like I already said lenn update your guide or mention that it is outdated and point to the wiki.
Click to expand...
Click to collapse
Sorry divx i really respct your works, but i know it.
I work at the momet on a honeycomb theme, and i said he should look there because of the menu.lst (the most makd faults, ...) and this part isnt outdated.
I will update the tutorial when i have enough time
Greets
Lenn
I know all that, as my first Unix was Minix followed by SCO and Eurix and then Linux 0.14 yggdrasil.
But if i see the questions postet here and elsewhere in android forums,
most of the people barely get their TV switched on, and to tell them that Linux is prefered might set back a few so much that they don't do anything.
On the other side, might be a good idea ;-)
Thanks for getting back to me. For some reason when I copy the file to the archos and reboot, it doesn't show up in the menu.lst
I decided to gunzip first and moved the file openaos-gingerbread.img to the archos. This showed in the list but when I tried to boot from it, the same thing as before happened. Hopefully I am just doing something silly. I'll try jump on the irc channel tomorrow. My main "comfy" computer was taken up by the oh this evening.
A couple more points.
My external SD slot is broken so I have no external SD. Although it installs onto the internal right? So that shouldn't make a difference.
I don't have stock fw installed at all. Just the SDE.
Edit: oh by the way, when I tried to move the .img file I got the following error:
mv : failed to preserve ownership for '/media/A101IT/openaos-gingerbread.img': Operation not permitted
It was moved with root privelages in terminal.
Edit2: I even did a sync before my umount to make sure everything was hunky dorey.
Sent from my R800i using Tapatalk
You need the stock to be installed, as during boot they extract some things.
I could be wrong but none of the above post seem to have noticed you haven't extracted the .gz img file. If you put that on you device it will do nothing as its the wrong file format and still compressed. You need to extract it using winrar or similar then rename that file to openaos-gingerbread.img and that should do it. nothing to do with capital letter you just missed a small but crucial step in the instructions.
ben.cordy said:
I could be wrong but none of the above post seem to have noticed you haven't extracted the .gz img file. If you put that on you device it will do nothing as its the wrong file format and still compressed. You need to extract it using winrar or similar then rename that file to openaos-gingerbread.img and that should do it. nothing to do with capital letter you just missed a small but crucial step in the instructions.
Click to expand...
Click to collapse
I'm pretty sure you don't and I have tried that anyway as per my second post...
Sent from my R800i using Tapatalk
fzelle said:
You need the stock to be installed, as during boot they extract some things.
Click to expand...
Click to collapse
That'll do it I'm sure. Will try to tonight.
Sent from my R800i using Tapatalk
Like fzelle said you need stock firmware, that is why it hangs. It needs to copy some libs and drivers over from stock. We can't include them in the release, because of license issues.
I don't think we check in the script if the original firmware isn't there. Another todo ...
I will update the wiki about having original firmware installed is essential.
@ben.cordy: The initramfs will gunzip the image when it is not done already, so no need to gunzip or unrar it yourself.
Still strange why it wouldn't show up in menu.lst while gzipped... I will check the script in initramfs.
Maurice
---------- Post added at 09:05 PM ---------- Previous post was at 08:47 PM ----------
fzelle said:
I know all that, as my first Unix was Minix followed by SCO and Eurix and then Linux 0.14 yggdrasil.
But if i see the questions postet here and elsewhere in android forums,
most of the people barely get their TV switched on, and to tell them that Linux is prefered might set back a few so much that they don't do anything.
On the other side, might be a good idea ;-)
Click to expand...
Click to collapse
At the moment, our target is the more advanced user, so we can get some good bug reports. That is why we have that big red warning on the wiki. So might be a good idea --> It is one .
Maurice