Database Users

[Solved] T-Mobile OTA My touch 3G Update Files 1, 2 and 3 (?).

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!

s-on and just update to new ota.

so now, how can you do s-off cause unrevoked does not work and ive tried a couple manual pb31img and im so lost.

dadsterflip said:
so now, how can you do s-off cause unrevoked does not work and ive tried a couple manual pb31img and im so lost.
Click to expand...
Click to collapse
in your case you have to wait for the updated Unrevoked since you didnt have previous root nor clockwork mod installed prior to getting your replacement unit. so it is jsut a waiting game at this point

Use that image you downloaded. You can point to it in File>custom in the unrevoked utility. Worked fine for me with an lcd.

ptsmith24 said:
Use that image you downloaded. You can point to it in File>custom in the unrevoked utility. Worked fine for me with an lcd.
Click to expand...
Click to collapse
So do I just open the folder or exact the unrevoked file and replace it with that image or? I mean I am still s-on because of the replacement phone. Does this turn the s-on to off?

Yes, it should. AFAIK, It's the same rooting and s off process but just with an lcd compatible recovery image. There should also be a checkmark checked by default next to security in the file menu. I can get on my laptop and take some screenshots for you if that would help.

ptsmith24 said:
Yes, it should. AFAIK, It's the same rooting and s off process but just with an lcd compatible recovery image. There should also be a checkmark checked by default next to security in the file menu. I can get on my laptop and take some screenshots for you if that would help.
Click to expand...
Click to collapse
Screen shot be nice if its not too much to ask. I have the file recovery image from some thread or so I need something different for the lcd one? Thx for your responses and all.
Also it does turn it to s-off also if im understanding this right.

dadsterflip said:
Screen shot be nice if its not too much to ask. I have the file recovery image from some thread or so I need something different for the lcd one? Thx for your responses and all.
Also it does turn it to s-off also if im understanding this right.
Click to expand...
Click to collapse
Sure...the screenshot is attached. As you can see, "Disable Security on Phone" is checked (which turns S-OFF). When you click "Custom Recovery..." (in the screenshot), it brings up a file dialog. Just navigate to your "recovery.img" and hit okay. I forgot to mention that you need to unzip the PB31IMG.zip so that you can see "recovery.img". I hope I clarified. Let me know how it goes (it took me about 10 minutes once it starts). I am running all of this in Linux (Ubuntu 10.04), so there may be some tweaking you have to do with USB drivers and uninstalling HTC Sync (IIRC, from what I've read if you're running Windows), but it sounds like you're past that.

Hmmm. Ok I did that and unzip the the recovery image to desktop. Set unrevoked to it and set custom and ran it. No luck. Grrrrr. Stupid replacement phone.

Unrevoked will not work on the new OTA. Not yet atleast.

Is your replacement hardware version 3? Settings, about phone, hardware information. I still have the recovery image I used but I don't remember where I got it.

doug piston said:
Unrevoked will not work on the new OTA. Not yet atleast.
Click to expand...
Click to collapse
Thanks, Doug. I didn't even think about that since I rooted pre-ota.

hardware version 0002. wish i could downgrade to stock 2.2 but when i do it. it says pb31img is old and it forces me just to restart. no bypass to that im guessing to go back to stock?

What file are you using to downgrade?

ruu 3.21.605.1 version of the pb31img.

dadsterflip said:
Hmmm. Ok I did that and unzip the the recovery image to desktop. Set unrevoked to it and set custom and ran it. No luck. Grrrrr. Stupid replacement phone.
Click to expand...
Click to collapse
your replacement phone came with the new update already installed on it?

Yes. Unfortunately

fender Splash Image Thanks to K'tag

credits to K'tag
http://forum.xda-developers.com/showpost.php?p=11205300&postcount=284
i tried to flash it and wow it worked but its a wrong dimension it has a black bar on both sides.. so i tried the other one you post.
but a little blury... so i did some adjustments and now its kinda more like the default splash... thanks bro....
newei
heres the file
http://www.mediafire.com/?urkjhzcugs0wex8
thank you so much bro

ardeldotcom said:
credits to K'tag
http://forum.xda-developers.com/showpost.php?p=11205300&postcount=284
i tried to flash it and wow it worked but its a wrong dimension it has a black bar on both sides.. so i tried the other one you post.
but a little blury... so i did some adjustments and now its kinda more like the default splash... thanks bro....
newei
heres the file
http://www.mediafire.com/?urkjhzcugs0wex8
thank you so much bro
Click to expand...
Click to collapse
how do i get this on my phone?

Nice work aldeldotcom!
Of course, before I saw this, I cleaned up the resized image a bit, so I may as well link to it.
http://www.mediafire.com/?ts7q2t2q7bovao1
I actually haven't gotten it onto my phone yet. I lost root with the OTA and haven't managed to get it back yet, (I haven't tried too hard either... yet) but it should look pretty good.
Of course, the REAL file would still be better...

"Fender" splash screen AND stock recovery
So I made it work.... I have this splash screen, root, AND stock recovery. (Ya know, in case I want more OTAs...)
Here's my story. And I'm stickin' to it.
You will need root. SuperOneClick worked for me. I did have to follow his instructions about toggling USB debugging on and off when it went into a loop. I also had a snag in that SuperUser.apk didn't actually load onto the phone, even though it was rooted. Apparently it's a lack of memory problem. There's a simple fix though; after rooting, copy the superuser.apk file from the SuperOneClick folder onto you SD card. Open it with ASTRO and install it like any other non-market app. You're good to go.
After getting root, here's what I did.
I flashed the 2010 SPL from the thread below by putting the zip on my sdcard and flashing it from Amon's recovery. There were some nervous moments, but it worked fine for me.
BE CAREFUL!!!! THIS IS WHERE YOU CAN BRICK YOUR PHONE. BE CAREFUL! (did I say to be careful?)
http://forum.xda-developers.com/showthread.php?t=794447
This is the link to the actual SPL I used: http://rapidshare.com/files/267475618/update.Engineering-SPL-HBOOT-1.33.2010-signed.zip
Next, I renamed the splash screen splash.rgb565 and put it in the same folder as my fastboot tool and followed the unlockrs instructions here:
http://theunlockr.com/2010/04/15/ho...for-all-320-x-480-resolution-android-devices/
Read their directions throughly, but here are the commands you need from fastboot:
fastboot flash splash1 splash.rgb565
fastboot reboot
Click to expand...
Click to collapse
And finally I reflashed the stock SPL through fastboot as instructed here:
http://forum.cyanogenmod.com/index.php?/topic/644-mytouch-12-tutorial/
This link: http://www.megaupload.com/?d=9Z7K1PAL
has the stock radio and SPL. I just put the SPL in the folder with fastboot and followed their instructions
AGAIN, BE CAREFUL!!! FLASHING SPLs CAN BE DANGEROUS.
PLEASE, read the instructions carefully and multiple times, but, here are the commands you'll need:
fastboot flash hboot hboot.nb0 (that's a zero at the end)
fastboot reboot-bootloader
Click to expand...
Click to collapse
Then I finally reflashed the stock recovery from a terminal emulator on the phone using DonJaun's instructions from here:
http://forum.xda-developers.com/showpost.php?p=11136815&postcount=266
The recovery file is here: http://forum.xda-developers.com/attachment.php?attachmentid=509115&d=1296862264
Here's his quote:
DonJuan692006 said:
Download the attached "Flash_image.zip", unzip the file, and put in on the root of your SD card. Then open up terminal on the phone and type the following hitting enter at the end of each line:
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 755 /system/bin/flash_image
mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
flash_image recovery /sdcard/*name of recovery*.img
reboot recovery
Click to expand...
Click to collapse
So that's where I'm at. As close to stock as I'm probably going to get, but still with root!
KT
BTW: I had the OTA on my phone before I did all this, but if I were still on 1.6, I would go in the same order and not try and apply the OTA first, if for no other reason than getting root on 1.6 is easy. Use UniversalAndRoot. Done. Then:
flash engineering SPL from recovery,
flash splash screen and original SPL from fastboot (in that order), and finally
flash stock recovery from terminal.
Then I would probably UNROOT before applying the OTA. I was unrooted when I got it, and I think I might be the only person not having trouble with it. Just my 2 cents..

I updated my post to include the actual flash_image command argument needed for my little guide.
As for applying the update. I would do it manually. You can download the update file from here, rename it to update.zip, put it on your SD card, and flash it from recovery. Before flashing it, make sure you do a "Wipe data/factory reset". For my myTouch 1.2 the update ran like crap, until I went it and did a wipe. It seems the update doesn't do a very good job of cleaning up the system cache before updating, which leads to ridiculous lag. A full wipe will help it run a million times better.

on the last part when you re-flash the stock hboot and recovery..
i flashed the hboot first according the guide then when i tried to flash the recovery it failed.. so i reflash the eng spl again then flash the stock recovery after that i re-reflashed the stock spl.. and it works... iam now left with "close to stock" fender??
about the stock recovery, is it the one when it onl shows you triangle with exclamation mark?

yes thats stock recovery. anywei
if you like you can do manual update if you want to update to froyo thats what i did.. after doing what i stated above.. now im on my stock froyo fender running smooth..
Sent from my T-Mobile myTouch 3G my fender using Tapatalk

ardeldotcom said:
yes thats stock recovery. anywei
if you like you can do manual update if you want to update to froyo thats what i did.. after doing what i stated above.. now im on my stock froyo fender running smooth..
Sent from my T-Mobile myTouch 3G my fender using Tapatalk
Click to expand...
Click to collapse
yes but i after that i put the update.zip in the MMC but it did not read it.

Just putting the word out...
There are people who have the original image who have visited the forum and are willing to donate their original Splash image if there is someone who can post direction on how to get it off the phone.

did you check if its update.zip ( no wrong spelling) and if your pc showing file extension because if not maybe you have it spelled as update.zip.zip...
Sent from my T-Mobile myTouch 3G using Tapatalk

i hope someone can post it on how to. but for now maybe you could try the splash imges we posted.. its almost close to the origial..
Sent from my T-Mobile myTouch 3G using Tapatalk

I'm fine, thanks.
I don't really need to change my splash screen. People are certainly welcome to use the one that's been synthesized. I'm just hoping for about as complete a restore for the Fender as we can get and that image would really seal the deal. Getting it off just seems to be the challenge.
Also working on a clean and usable 2.2.1 image in the event one should want to go there if they happen to release this rumoured fix or try it with an overclocked kernel. Hopefully we will see some targeted at the 1.2/Fender owners with some encouragement. Work so far impressed a T-Mobile rep who was a fan of the phone when I went in to pay for a data plan. It's getting pretty clean and snappy as is.

In the efforts of bringing this to a successful close I have created the following thread. http://forum.xda-developers.com/showthread.php?p=11341358
Seems the splash image and the entire original ROM can be fetched and reconstructed.

update stuck
so i did the whole process and i ended up with "stock" Fender Edition, i did a system update, it downloaded the update so i installed it but after it's done reseting it's just stuck at the splash screen, and now i cant boot to the system anymore...
help please?

Questions...
Can you boot your phone into Recovery, Fastboot/HBoot? Have you tried asking for help in the OTA thread? http://forum.xda-developers.com/showthread.php?t=906006 More super smart android people seem to be watching that one and may be able to help.

WoefulDerelict said:
Can you boot your phone into Recovery, Fastboot/HBoot? Have you tried asking for help in the OTA thread? http://forum.xda-developers.com/showthread.php?t=906006 More super smart android people seem to be watching that one and may be able to help.
Click to expand...
Click to collapse
i can boot into fast/h-boot and i am able to boot to the recovery screen(the one with the ! mark, and also the 2e)
but i cannot do anything, fastboot gets remote not allow, tried to flash the eng SPL is also failed

danxtian said:
i can boot into fast/h-boot and i am able to boot to the recovery screen(the one with the ! mark, and also the 2e)
but i cannot do anything, fastboot gets remote not allow, tried to flash the eng SPL is also failed
Click to expand...
Click to collapse
Going to have to goldcard root. There's a guide in my sig.
Sent from my LG-P500 using Tapatalk

DonJuan692006 said:
Going to have to goldcard root. There's a guide in my sig.
Sent from my LG-P500 using Tapatalk
Click to expand...
Click to collapse
but i can't access my phone to turn the USB debugging on, is there anyway to make the goldcard?

danxtian said:
but i can't access my phone to turn the USB debugging on, is there anyway to make the goldcard?
Click to expand...
Click to collapse
Use a friends phone that has Android on it.
Sent from my LG-P500 using Tapatalk

DonJuan692006 said:
Use a friends phone that has Android on it.
Sent from my LG-P500 using Tapatalk
Click to expand...
Click to collapse
hmm... will it work if i use HD2 running android on it?

Trying to root - problems [SOLVED]

Hey guys.
I've been attempting this all morning and so far I've had no luck. I have a VodafoneAU Legend which I updated to the official 2.2 yesterday. But now I want to try root.
I've been trying to follow the HBOOT 1.01 guide but there's a few problems. First, I cannot connect to the phone with adb unless it's in htc sync mode. No other mode will work. So when it's time to copy testimage.zip to the card I have to change from sync mode to disk mode, whereby adb loses it's connection. What do I do about this? Is it a driver problem (in Win7 here) or something else?
Thanks,
Dave.

Ok, the first problem were drivers.
Now I can't finish the second guide. When I try using clockwork to install the firmware.zip, the phone just boots to the red triangle. What do I have to do?
Dave.

So I pressed the up button/power combo at the red triangle and get the Android system recovery. Selecting "apply update.zip" says it can't verify. What do I do? Is this guide for my phone or do I need to follow something else?

I don't understand this guys. Anyone help? I'm thinking since this is a step to root the phone, I'm not actually rooted yet so I can't use the clockworkmod? Then what is the guide for? The guides at unlockr don't mention what firmware/hboot they work for so I'm not keen to try them yet.

Read the guide on fake flash. You need the recovery file named "update.zip" in the root of your sd to proceed..
Sent from my Legend using XDA App

whitetigerdk said:
Read the guide on fake flash. You need the recovery file named "update.zip" in the root of your sd to proceed..
Sent from my Legend using XDA App
Click to expand...
Click to collapse
But isn't that what Rom Manager does? Download the update.zip then run it? Man this is getting even harder to understand.
Edit: And this is left out of the HBOOT 1.01 guide because.....????? When I work this out I'll write a PROPPER guide, lol.

Just checked and update.zip is on the card.
So which part of the guide am I getting wrong?

Decided to reinstall phone with the official froyo release and am now ready to try this again. Is there anyone that will walk me through the process? I will write a complete guide if the "gotchas" are still there.

i feel for you ... hope you get it fixed... thats one of the reason i havent dared messing with the phone because i've seen a few post like yours where something didnt go quite as described... for whatever reason... and im sure the answer is out there but just not within the guide instructions... i guess there is no way to gather all gotchas because there are so many environment variables...
good luck
and please share your technique

Just saw gobczak's thread in the developer forum having similar troubles with Vodafone UK phone, getting the red triangle at reboot. I'll keep an eye on his thread and see how he goes with it.

Did you run the stage1 and stage2 bats while in recovery?

dezzadk said:
Did you run the stage1 and stage2 bats while in recovery?
Click to expand...
Click to collapse
No because the guide didn't say to.
The thing is it seems I'm only stuck on the part where the firmware.zip file has to be flashed. The guide says to use clockworkmod for this. But when I try installing the clockworkmod recovery it gives some file verification error. Isn't there ways to do this via the pc, either through those batch files, adb etc? Or will that fake-flash update.zip file work?

jabbado said:
No because the guide didn't say to.
Click to expand...
Click to collapse
As I just posted on the other forum, I think you need to skip that step in guide 2 and go straight onto guide 3 after you have flashed the LEGEIMG.zip, rebooted, and then removed LEGEIMG.zip from the SD card.

Guys I've got to the point of downgrading to 1.31. But when I run the first batch file it just hangs at the "Writing zip" part, with the htc logo on the screen. Is there any way to fix this?

Can someone please explain this part of the guide:
Phone will reboot and find LEGEIMG.zip on your sdcard, copy it into RAM and check it. If you get CID error at this point, then you don't have goldcard.
Click to expand...
Click to collapse
Ok, so I don't get an error. I get nothing. The phone just boots to the fastboot screen. If I press the power button it goes to the hboot screen and I can see the messages of loading LEGEIMG.zip. But the guide doesn't say to press anything.
So should I or shouldn't I press the power button? Also, if I try making the goldcard again, at which point in the guide do I start from again? The entire process or just copying LEGEIMG.zip to card then rebooting phone? I mean, will all the other things like flashing misc1-2.img still be there?

Guys I finally got this working.
The first problem was with the goldcards. For whatever reason formatting them with the win7 format tool just wouldn't work. I had to use the command-line format tool, setting the block size etc manually.
The second problem was the unnecessary steps in the guide. A few people helped me out with this (namely blackbart at the Aus Whirlpool forum), but basically in the second step you can stop after flashing the LEGEIMG.zip. The updating froyo part isn't needed - for my phone anyway.
Then when running the batch files in the third part, for whatever reason the first batch would keep hanging at 'writing zip...' and I needed to remove the battery to unfreeze the phone. flannigan, also from the Aus Whirlpool forums suggested to just go on to the second batch file. This worked!
So my Legend is now finally a true Legend
Anyway, thanks for the help everyone - couldn't have done this by myself.
Dave

Great news, I think we need a new guide focused on rooting for HBOOT 1.01 / Stock Froyo to clear up the inconsistencies in the existing one. It's a minefield for a noob (or a rite of passage!), a revised guide will certainly save a lot of time and frustration for those taking this road in the future.
Sent from my HTC Legend using XDA App

EpicSauce said:
Great news, I think we need a new guide focused on rooting for HBOOT 1.01 to clear up the inconsistencies in the existing one. It's a minefield for a noob (or a rite of passage!), a revised guide will certainly save a lot of time and frustration for those taking this road in the future.
Click to expand...
Click to collapse
I'll write one if ya's want. I wanted to include little tidbits like downloading the apps required (visionary, rom manager etc) from the market then backing them up to the card with Astro so if it goes all wrong and you have to start again, you can just install them all from the card Also on using adb to push the files (roms, img's etc) when the guides say "copy this blah blah". Much quicker than changing to disk mode and back. Sound good?

Sounds good! Happy to help and add my 20c worth along the way. The existing guide has got the meaty bits, a new guide would cull the stuff not relevant, help fill in the gaps and alert to the pitfalls we've fallen into.

jabbado said:
I'll write one if ya's want. I wanted to include little tidbits like downloading the apps required (visionary, rom manager etc) from the market then backing them up to the card with Astro so if it goes all wrong and you have to start again, you can just install them all from the card Also on using adb to push the files (roms, img's etc) when the guides say "copy this blah blah". Much quicker than changing to disk mode and back. Sound good?
Click to expand...
Click to collapse
I agree... i've done my reading since june of last year but then didnt check for another 4 months... and so many how to's pop up with various ways of doing it depeding on the situation... a lot of those howtos were consolidated howtos which sometimes make intermediate steps unenecessary (may be in some cases causes more head aches since it didnt take into considerations on newer version of hboots...etc)... an updated how to will be much appreciated...
And you're right the most important pre requirement is to have a safety net ... so starting with how to create a back up in case you screw it up is a must!
but im glad it worked out for you!

[Q] another noob with a rooting issue

sprint evo 4g, updated to the newest version before deciding to root. yes i now know that was my biggest mistake!
ok so i used this: themikmik dot com/showthread.php?11114-GUIDE-WIP-How-to-achieve-S-OFF-after-unlocking-2-18-HBOOT-with-HTCDev-com-No-More-Watermark
after using the HTCDEV to unlock.
basic info:
says unlocked at top of screen
hboot 2.18.0001
radio 2.15.00.12.19
s-on
version 2.3.5
kernel 2.6.35.10 g4b48446
software 4.67.651.3
pri2.33_003
prl 60683
hardware 0003
i am stuck in between step 10 and 11.
problem i am having is the pc36img.zip. i tried both that are listed and tried both from different computers to make sure it wasn't a pc issue. i get a message that says "no or wrong zip image" it never gives me the option to update in fastboot. and never goes to saying locked again as described in the tutorial.
i downloaded su, root checker,and busy box. root checker says the phone is rooted. i know i need to get the h boot to a lower level inorder to do the unrevoked3 program.
tried flashing the recovery and says "cant open /sdcard/pc36img.zip (bad)"
made sure it wasn't zip.zip and it was so i fixed that and still wouldn't work.
the only thing i am not sure of is step 10 and wether i did it right :Once the misc partition has been updated, you can downgrade your Bootloader and HBOOT to a non-watermarked version rootable with unrevoked.
does the partition auto update or do i need to do something to make it update? i didn't see any option for this. eveything up to this point went exacty liek it should have so now i am lost. i have searched numerous forums and found similar problems but none that were exactly the same. and none of the solutions worked for me. i tried all the basics rebooting, etc and nothing. any info would be greatly appriciated.
the only other thing that i may have done wrong that i can tell is what file i am trying to make the pc36img. at the bottom of post # 1 it has 2 attachments listed as pc36img files those are the ones i am trying to use. when i try to click the hyperlinks thru the rest of the post i get an error message from that site thats says " This account's public links are generating too much traffic and have been temporarily disabled! " so i dont know if that site has the same zip files or i am completely using the wrong zip file.
sorry for the long winded post i know the noob video says make it brief but i figured the more info the better.
thank you.

sprint evo 4g, updated to the newest version before deciding to root. yes i now know that was my biggest mistake!
Click to expand...
Click to collapse
Oh brother was it!
basic info:
says unlocked at top of screen
hboot 2.18.0001
radio 2.15.00.12.19
s-on
version 2.3.5
kernel 2.6.35.10 g4b48446
software 4.67.651.3
pri2.33_003
prl 60683
hardware 0003
Click to expand...
Click to collapse
Your S-On,so your not rooted.
problem i am having is the pc36img.zip. i tried both that are listed and tried both from different computers to make sure it wasn't a pc issue. i get a message that says "no or wrong zip image" it never gives me the option to update in fastboot. and never goes to saying locked again as described in the tutorial.
Click to expand...
Click to collapse
Make sure the PC36IMG is all in CAPS.
Sent from my Dell PC.

Diablo67 said:
Oh brother was it!
Your S-On,so your not rooted.
Make sure the PC36IMG is all in CAPS.
Sent from my Dell PC.
Click to expand...
Click to collapse
Actually s-on or s-off status doesn't determine if your rooted or not. That indicates wether your NAND unlocked or not. To be rooted is to have busybox and superuser permissions
Sent from my PC36100 using XDA App

when i check with root checker it says i am rooted and have su. maybe it just means unlocked? busy box also says rooted?
pc36img is in all caps.
thanks for the quick response!

evo4gnoob said:
Actually s-on or s-off status doesn't determine if your rooted or not. That indicates wether your NAND unlocked or not. To be rooted is to have busybox and superuser permissions
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
This. S-Off/S-On is basically root for bootloader only has no bearing on root of phone itself you can be s-on and still root your phone you just wont have or be able to have a custom recovery or flash unsigned zips thru bootloader so romming is almost impossible but root is completely possible

evo4gnoob said:
Actually s-on or s-off status doesn't determine if your rooted or not. That indicates wether your NAND unlocked or not. To be rooted is to have busybox and superuser permissions
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
This. S-Off/S-On is basically root for bootloader only has no bearing on root of phone itself you can be s-on and still root your phone you just wont have or be able to have a custom recovery or flash unsigned zips thru bootloader so romming is almost impossible but root is completely possible
Click to expand...
Click to collapse
Ok,thanks for clearing that up,serious dudes i hate giving the wrong info when trying to help someone and i don't mind admitting when i'm wrong,lol.Your never to smart or old to learn something new.
Sent from my Dell computer.

I can probably help here.
If all you want is to be rooted, then you are. There's no reason to do the rest, especially if you're out of warranty. Since you already have a custom recovery installed, you can feel free to flash a custom ROM, and not even worry about the rest of the process.
The Dropbox links thing should be fixed now. I had to move them all to 4shared.
As far as the misc partition flashing, as long as you didn't get any errors when in the command prompt/adb shell, then I'm sure it flashed successfully. The only way to tell is if the Froyo PC36IMG.zip flashes successfully without a "main version fail."
I can assure you the PC36IMG works, as I've used it many times myself. Did you confirm the md5? Is it possible your SD card got corrupted somehow? Those are the only reasons it wouldn't pick it up.

thanks for coming in here i really appriciate it.
i still pay for the extended warranty if thats what you are asking for my phone.
my hboot is still 2.18 and because of that i can not run the unrevoked software either.
as far as the pc36img, i am just not sure if i am changing the name on the correct file. in your first post you have 2 attachments, those are the ones i tried to use to rename, was i correct in doing that? if i go back to where you say to use the 3.70 Froyo ROM with 2.10 HBOOT - md5: 7056D42812AA5DF03FCC8DDDC2B64E85
it goes to a dead site, so thats what makes me think i did something wrong. no main version ail messages and the top of my fastboot screen still says unlocked, not locked and not missing.
thank you again for your help and imput
how do i confirm if the md5 number is correct?

98tib said:
thanks for coming in here i really appriciate it.
i still pay for the extended warranty if thats what you are asking for my phone.
my hboot is still 2.18 and because of that i can not run the unrevoked software either.
as far as the pc36img, i am just not sure if i am changing the name on the correct file. in your first post you have 2 attachments, those are the ones i tried to use to rename, was i correct in doing that? if i go back to where you say to use the 3.70 Froyo ROM with 2.10 HBOOT - md5: 7056D42812AA5DF03FCC8DDDC2B64E85
it goes to a dead site, so thats what makes me think i did something wrong. no main version ail messages and the top of my fastboot screen still says unlocked, not locked and not missing.
thank you again for your help and imput
how do i confirm if the md5 number is correct?
Click to expand...
Click to collapse
The two files attached to the first post are both recoveries. You only needed one of them, and I assume you were okay with that part. The link you speak of should be working now, and that file gets renamed the same way the recovery zip did. As far as checking the md5, you just need to find a program that will do that. I use HashTab.
Like I said before, the dead link has nothing to do with you; Dropbox just canned my account because of too many downloads. The link should now be pointing to 4shared if the md5 doesn't match and you need to redownload.
You don't necessarily need to worry about the watermark issue now; just wait until you need repairs, and then you can use that process to remove it. You'll probably know a lot more if/when that happens, and the process will be easy as pie .

Captain_Throwback said:
The two files attached to the first post are both recoveries. You only needed one of them, and I assume you were okay with that part. The link you speak of should be working now, and that file gets renamed the same way the recovery zip did. As far as checking the md5, you just need to find a program that will do that. I use HashTab.
Like I said before, the dead link has nothing to do with you; Dropbox just canned my account because of too many downloads. The link should now be pointing to 4shared if the md5 doesn't match and you need to redownload.
You don't necessarily need to worry about the watermark issue now; just wait until you need repairs, and then you can use that process to remove it. You'll probably know a lot more if/when that happens, and the process will be easy as pie .
Click to expand...
Click to collapse
i used only one and that was fine.
here is the link i am talking about, when i click on the hyperlink for pc36img.zip it still leads to drop box.and not a file i can download to drop/drag to the root of the sd card
PC36IMG.zip - 3.70 Froyo ROM with 2.10 HBOOT - md5: 7056D42812AA5DF03FCC8DDDC2B64E85
both attachments at the bottom of post # 1 start with pc36img, i am using one of them as the renamed file, i am sure if i am wrong in doing that at this point.
i understand about the water mark. thank you.

98tib said:
i used only one and that was fine.
here is the link i am talking about, when i click on the hyperlink for pc36img.zip it still leads to drop box.and not a file i can download to drop/drag to the root of the sd card
PC36IMG.zip - 3.70 Froyo ROM with 2.10 HBOOT - md5: 7056D42812AA5DF03FCC8DDDC2B64E85
both attachments at the bottom of post # 1 start with pc36img, i am using one of them as the renamed file, i am sure if i am wrong in doing that at this point.
i understand about the water mark. thank you.
Click to expand...
Click to collapse
Thanks, you were right, that link wasn't updated. It is now .
You can remove the renamed recovery PC36IMG from your card and replace it with the Froyo PC36IMG, if you're going to continue trying to flash and NAND unlock with unrevoked.

This is what's cool about this forum a noob asking a question and you get 4 big time contributors helping out!
Sent from my PC36100 using xda premium

Captain_Throwback said:
Thanks, you were right, that link wasn't updated. It is now .
You can remove the renamed recovery PC36IMG from your card and replace it with the Froyo PC36IMG, if you're going to continue trying to flash and NAND unlock with unrevoked.
Click to expand...
Click to collapse
thank you.
i downloaded the correct file, renamed, and moved to the sd card and i'm still having the same problem. never asks to update. still says unlocked and still can't run unrevoked.
i really do appriciate all your help and imput with solving my problem

98tib said:
thank you.
i downloaded the correct file, renamed, and moved to the sd card and i'm still having the same problem. never asks to update. still says unlocked and still can't run unrevoked.
i really do appriciate all your help and imput with solving my problem
Click to expand...
Click to collapse
What kind of sd card are you using? You might want to try a different card, or reformat the stock card, if that's what you're using. That's the only other reason it wouldn't pick up the file, provided it's named correctly. And I assume you verified the md5 and it's good? And you're certain the file is on the root of the sd card as well? I cant think of anything else that could be causing the problem. Let me make sure my bootloader reads the file just to make sure.
EDIT: Scratch everything I said above. If your phone still says "unlocked" at the top of the bootloader, the misc partition wasn't updated successfully. Did you already complete that part, with no errors? You need to reconnect the device while booted up, with USB Debugging enabled, and run those commands from the command prompt from the folder with adb in it. Make sure you have the files "flash_image" (extracted from zip file) and "mtd-eng.img" (extracted from zip file) on the root of your sd card. If you're using Windows 7, run Command Prompt as an administrator. Let me know the output of those commands before continuing. If you got any errors on that part, that would be why you can't flash the Froyo ROM.
I saw you mentioned that in your OP, but I guess I didn't realize you skipped that part. That'a really the most important part of the process. It's the part right before the sentence you mention about the misc partition being downgraded. That last command flashes the mtd-eng.img file to the misc partition.

both files are unziped and on the sd card, running windows vista. ran the cmd and it looked like just like it did in your post but now that i am thinking about it i dont remember the phone doing anything. i also have the zip file for both on the sd card, should i remove them? but then again it didn't give me any errors either.
using the stock sd card. sandisc 8gb class 4.
i will redo the cmd portion again when i get home, limited here at work.
i thank you again for your help.

98tib said:
both files are unziped and on the sd card, running windows vista. ran the cmd and it looked like just like it did in your post but now that i am thinking about it i dont remember the phone doing anything. i also have the zip file for both on the sd card, should i remove them? but then again it didn't give me any errors either.
using the stock sd card. sandisc 8gb class 4.
i will redo the cmd portion again when i get home, limited here at work.
i thank you again for your help.
Click to expand...
Click to collapse
It does sound like it worked okay. The phone isn't supposed to do anything. But there is a way to verify that it flashed successfully. And yes, you should delete the zip files for those off of the root of your sd, to be safe.
Before you re-run those commands, open a command prompt and navigate to the location of fastboot. Put your phone into fastboot mode, connect to the the computer, and run this command:
Code:
fastboot getvar mainver
and report back what it says. My guess will be it'll report "4.67.651.3". That means the main version hasn't been downgraded. Then, reboot the device and run the commands as listed in the guide to gain superuser access & flash the downgrade to the misc partition. Then reboot into the bootloader, and you'll know it worked if it now says "LOCKED (OOW)" at the top. If it doesn't, then I'm not really sure what to do next. But definitely do a screenshot of the command prompt commands and output, starting with "adb shell".

Captain_Throwback said:
It does sound like it worked okay. The phone isn't supposed to do anything. But there is a way to verify that it flashed successfully. And yes, you should delete the zip files for those off of the root of your sd, to be safe.
Before you re-run those commands, open a command prompt and navigate to the location of fastboot. Put your phone into fastboot mode, connect to the the computer, and run this command:
Code:
fastboot getvar mainver
and report back what it says. My guess will be it'll report "4.67.651.3". That means the main version hasn't been downgraded. Then, reboot the device and run the commands as listed in the guide to gain superuser access & flash the downgrade to the misc partition. Then reboot into the bootloader, and you'll know it worked if it now says "LOCKED (OOW)" at the top. If it doesn't, then I'm not really sure what to do next. But definitely do a screenshot of the command prompt commands and output, starting with "adb shell".
Click to expand...
Click to collapse
thank you, you are my savior! its always the dumb things that you think you did right that you did wrong! lol. thank you again!

now i'm off to screw something else up!