Database Users

Full Downgrade from 2.1root (any) to 1.5 stock - FULLY WORKING

Download removed, go ahead and thank user nimdae for pointing out the wrongness of my work. I am done with Eris dev work because of people like him.
nimdae <-- that user right there.
THIS IS NOT FOR LEAK USERS SO DON'T ASK
*start rant* THIS MEANS DON'T MESSAGE ME ASKING HOW TO USE IT ON 2.1LEAK, ITS NOT CURRENTLY POSSIBLE TO DOWNGRADE FROM LEAK. PLEASE STOP SENDING ME MESSAGES ASKING HOW.*end rant*
If it bricks your phone, not my fault (it shouldn't and I hope it doesn't).
Please read and follow the directions included in this thread.
unzipme.zip md5sum: 0ed3c91d7574367d65428b3bc230f217
This is fully working, I just did a full reflash to 1.5, including the kernel, the system software, the radio firmware, recovery image and the bootloader.
This must be done from a PC with Fastboot, which comes with windows. Linux/Mac users will have to find it and compile it. You will need to have Amon's recovery image installed to use this downgrade, at the end we will overwrite his image with the stock one.
Inside unzipme.zip are three files
downgrade.zip md5sum: c440c87f1e67f4b62e05da0d255e80e9
-Do not unzip/open/alter this file
--Contains your kernel, radio firmware, and system.
recovery.img md5sum: 71a4b633bdb32de9dcdd8953fef43cdc
--stock recovery image
hboot.nb0 md5sum: 38899da4e5e002e3be22900f5f4eb6f7
--Original bootloader
Step one:
Put hboot.nb0 and recovery.img in the tools dir of your sdk.
Put downgrade.zip on the sdcard of your phone
Step two:
Turn your phone off, then turn it back on holding the power button (red) and send button (green). Once in the boot loader press volume down, then volume up to get to Amon's recovery image. Go to wipe, wipe dalvik cache, and do a factory reset (aka wipe data). Then choose flash zip from sdcard, and flash downgrade.zip. The phone will flash the kernel, and system softare, then ask you to reboot. Let it reboot so it can flash the radio, it will restart back in the recovery image. You can power down your phone now.
Once the phone says "Formatting CACHE:" wait 30seconds and your done. This is an minor error in the update-config on my part, but it is not harmful and I won't be fixing it.
At this point if your just wanted 1.5 back, you are done.
If you want the original bootloader and recovery image, (ie 100% stock) continue on.
Step three:
Plug your phone into your PC. Power your phone on using the power button (red) and send button (green). Your phone should now be sitting back at the bootloader screen and say FASTBOOT USB. Now on your PC, go to the sdk tools dir in command line. Issue this command.
Code:
fastboot flash recovery recovery.img
Let it flash, when done wait a minute (just to make sure).
Then issue this command
Code:
fastboot flash hboot hboot.nb0
Once this is done, wait a minute then pull your battery and restart your phone.
You are now back at factory stock.
Thank you ivanmmj for showing me how to do this crud, and zifnab06 for telling me the right way to flash hboot.
...
..
.
jcase

Risk of losing root permanently? I could be up to test, but I won't be home til after 5 pst. I'll hit you up on irc later to check if you're still looking for someone.

This is not the droid your looking for......

move along move along.

What are the risks / requirements?

Darn, if this was a 2.1leak to 1.5 test, I would so be your guinea pig, since I'm getting a new phone tomorrow anyway. lol

Ruh17 said:
Risk of losing root permanently? I could be up to test, but I won't be home til after 5 pst. I'll hit you up on irc later to check if you're still looking for someone.
Click to expand...
Click to collapse
no you could just root again by loading the rooted 2.1 rom

Thanks jamezelle. Good job devs. Don't know how you find the time to work your magic every day.

I have 2 eris's here. Ones an extra. Let me know..

This kind of gets me excited being on 2.1 leak atm but I guess I should not bother to get hopes up doing things while rooted is a lot easier than when not so Im guessing I am going to be stuck.

OH DANG!!!!!
i am so excited!!! if you're like 90% seure it will work i volunteer!!!
i love 2.1 but i WANT to root SO BAD

Too bad its not for 2.1 leakers huh?

Has anyone tried this? I have an extra eris sitting around running the 2.1 root. If it has not been tried i will test it on the extra one (warranty have to send it back in a few days)

morbidpete said:
Has anyone tried this? I have an extra eris sitting around running the 2.1 root. If it has not been tried i will test it on the extra one (warranty have to send it back in a few days)
Click to expand...
Click to collapse
Please try it! I want to have a sure downgrade after root.

no links :-/

Apparently I need to fix it, and i dont have time right now.

jcase said:
Apparently I need to fix it, and i dont have time right now.
Click to expand...
Click to collapse
ohh ok. NP

where is the link to download
?

bah never mind shouldhave read the last post.... =X

Now, if I root and go stock, the engineering bootloader stays correct? Would they notice that the engineering bootloader was there if I turned it in for warranty? What's the difference in appearance on the engineering bootloader?

Anyone know how to downgrade roms?

I have the updates installed but the unlock and selection sounds don't work. They were for a bit but then stopped. I tried to rename the rom update.zip but the phone stated it was an older version and could not flash it. It then forced me to reboot, end of story.
I want to reboot back to OG rom and then apply the updates over it.
Can anyone help me out.

Do it with paulobrian's method.

~~Tito~~ said:
Do it with paulobrian's method.
Click to expand...
Click to collapse
Assuming he knows what that is. OP, were you doing the fastboot flash method using the command prompt on Windows?

~~Tito~~ said:
Do it with paulobrian's method.
Click to expand...
Click to collapse
Now if i only knew what this really meant.
* Download the 1.19 stock ROM from here
* Download fastboot from here
* Extract the fastboot zip to the same directory as the ROM
* Turn your G2 on with the action button held (fastboot mode) I've never heard of an action button
* Type 'fastboot-windows oem rebootRUU' (case sensitive, replace windows with mac or linux as required) No where does it give me the option to type anything in.
* Type 'fastboot-windows flash zip PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459
signed.zip'
* Let this finish, then type 'fastboot reboot' and apply the OTA
P

EfemaN said:
Assuming he knows what that is. OP, were you doing the fastboot flash method using the command prompt on Windows?
Click to expand...
Click to collapse
I used this method to revert back to stock cuz i deleted the goggles. But, the click sounds only worked for an hours then stopped.
-------------------------------------------------------
Download PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b _26.02.01.15_M2_release_149459_signed
(the link is somewere in this thread)
*then read name it to PC10IMG.zip
*Put it on the root of your sd card.
*Power down phone
*Power up phone holding Vol Down and Power button.
*Phone will boot into fastboot i believe and then it will look for PC10IMG
*It will ask to flash it you use the vol key and power buttons to do that.
*Once it done it will reboot the phone and all your data will be gone and your be back at factory setting.
Then just rename the ota to update.zip and flash via recovery.
*remover the PC10IMG.zip from root of sd card
* Get back into the fastboot on the phone (setups up there^)
*this time use the vol button to go down to recovery.
*Once at recovery hold vol up and hit the power button.
*then vol down to flash update.zip

ddgarcia05 said:
I have the updates installed but the unlock and selection sounds don't work. They were for a bit but then stopped. I tried to rename the rom update.zip but the phone stated it was an older version and could not flash it. It then forced me to reboot, end of story.
I want to reboot back to OG rom and then apply the updates over it.
Can anyone help me out.
Click to expand...
Click to collapse
First make sure you media vol is on and up. If its not then u wont be able to hear it. And second you can downgrade the phone. All andiords are downgrade block unless we have custom bootloader. And the steps poste above are mines I orignaly posted them so I know it wont work after u applyed the ota
Sent from my T-Mobile G2 using XDA App

You cannot downgrade using either of the fastboot methods (fastboot-windows or fastboot on your phone) listed above after you have applied the OTA. It checks the version and then tells you that the downgrade version is old.
So far, I have not seen a solution to downgrade.

cparekh said:
You cannot downgrade using either of the fastboot methods (fastboot-windows or fastboot on your phone) listed above after you have applied the OTA. It checks the version and then tells you that the downgrade version is old.
So far, I have not seen a solution to downgrade.
Click to expand...
Click to collapse
This is correct, verified live in IRC by people in #g2root

Just call tmob and tell them your hinge is loose! Exchange phone, don't apply OTA.

All the sounds stopped working on my phone a day ago, had to do a hard reboot to get them working again.
OTA was applied.

Well, I called tmobile and told them my issue. I also told them I had already tried to reset my phone in attempts to fix the sound issue to no avail. I've got a new or like new G2 on it's way.
I'm going to be kinda bummed if it's a like new (refurbished) model, but then again it can't be older than the one I got now.

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?

HTC ARIA 2.2.2 downgraded and rooted

HTC ARIA FIX FOR THOSE THAT UPGRADED TO 2.2.2
By kibby Ndemo
ALPHAREVX
Requirements:
• ADB Installed on your system. See our guide on what is ADB and how to install it.
• HTC Sync software installed in order to download necessary drivers. (Once the drivers are installed, remove HTC Sync from your system.)
• AlphaRevX.
Instructions:
1. To begin, make sure USB debugging is enabled in you device under Settings > Applications > Development.
2. Download AlphaRevX and extract the files to a folder. (A form will show up on the download page, keep it opened.)
3. Connect your device to the system and run Aplharev.exe.
4. You will be asked to enter a Beta key at this stage. Simple copy the serial number that shows up in the brackets in the prompt as shown in the screenshot above, and paste it into the form on the download page.
5. Hit the Generate Key on that form and once you have the key, enter it into the prompt to see a Beta key accepted message.
6. The application will start the S-Off procedure and should complete in around 90 seconds. Incase it does not start, wait fro around 15 minutes and re-do the whole process.
After doing the above procedure downgrade to HTC aria 2.1 then you be able to root you aria once more and flash any files. Please donate to alpharev too they made it possible.you can find the old 2.1 ruu in xda
PS I have done it and it works.

Man talk about timing. My fr008 aria bit the dust and I had to get another via ins. well it came factory with 2.2.2. I was pissed off about that and started looking for a fix and found one here. I will have to wait till tomorrow or Monday to try it because the unit they sent me has a bad ear piece and they are sending a new one but I will post my results when I get my new, new phone. Thanks for the work on this.
No link to file do I need to search XDA or did you forget to attach it.

tbone22 said:
Man talk about timing. My fr008 aria bit the dust and I had to get another via ins. well it came factory with 2.2.2. I was pissed off about that and started looking for a fix and found one here. I will have to wait till tomorrow or Monday to try it because the unit they sent me has a bad ear piece and they are sending a new one but I will post my results when I get my new, new phone. Thanks for the work on this.
No link to file do I need to search XDA or did you forget to attach it.
Click to expand...
Click to collapse
it's all over these forums
www.alpharev.nl/x/beta

ferariboy said:
HTC ARIA FIX FOR THOSE THAT UPGRADED TO 2.2.2
By kibby Ndemo
ALPHAREVX
Requirements:
• ADB Installed on your system. See our guide on what is ADB and how to install it.
• HTC Sync software installed in order to download necessary drivers. (Once the drivers are installed, remove HTC Sync from your system.)
• AlphaRevX.
Instructions:
1. To begin, make sure USB debugging is enabled in you device under Settings > Applications > Development.
2. Download AlphaRevX and extract the files to a folder. (A form will show up on the download page, keep it opened.)
3. Connect your device to the system and run Aplharev.exe.
4. You will be asked to enter a Beta key at this stage. Simple copy the serial number that shows up in the brackets in the prompt as shown in the screenshot above, and paste it into the form on the download page.
5. Hit the Generate Key on that form and once you have the key, enter it into the prompt to see a Beta key accepted message.
6. The application will start the S-Off procedure and should complete in around 90 seconds. Incase it does not start, wait fro around 15 minutes and re-do the whole process.
After doing the above procedure downgrade to HTC aria 2.1 then you be able to root you aria once more and flash any files. Please donate to alpharev too they made it possible.you can find the old 2.1 ruu in xda
PS I have done it and it works.
Click to expand...
Click to collapse
Why would anyone want to downgrade to 2.1 after having S-OFF!? (Rhetorical question). Once you have S-OFF, you can flash superuser, clockworkmod and custom roms without needing to downgrade to 2.1 then rooting again. Also attn1 already made a thread here on what to do after AlpharevX: http://forum.xda-developers.com/showthread.php?t=1122694.

HTC ARIA
He is very right i jumped the gun too soon

ferariboy said:
Try flashing the htc aria after s-off then that will answer your question please do research before bloging something you dont have an idea about
Click to expand...
Click to collapse
fastboot?
characters

ferariboy said:
Try flashing the htc aria after s-off then that will answer your question please do research before bloging something you dont have an idea about
Click to expand...
Click to collapse
Uh no, Theonew is exactly right. Not only is he right, but he gave a link showing exactly what he was talking about. In an ultimate showing of irony, you blasted someone for not doing his research when it's actually you who hasn't done his research.
Once you have S-OFF you don't need to use the 2.1 RUU or Unrevoked. It's a waste of time. You can push Clockwork recovery to your phone via fastboot, then flash whatever you want. It takes literally 2 seconds to flash Clockwork in this manner after you have S-OFF.

ferariboy said:
HTC ARIA FIX FOR THOSE THAT UPGRADED TO 2.2.2
By kibby Ndemo
ALPHAREVX
Requirements:
• ADB Installed on your system. See our guide on what is ADB and how to install it.
• HTC Sync software installed in order to download necessary drivers. (Once the drivers are installed, remove HTC Sync from your system.)
• AlphaRevX.
Instructions:
1. To begin, make sure USB debugging is enabled in you device under Settings > Applications > Development.
2. Download AlphaRevX and extract the files to a folder. (A form will show up on the download page, keep it opened.)
3. Connect your device to the system and run Aplharev.exe.
4. You will be asked to enter a Beta key at this stage. Simple copy the serial number that shows up in the brackets in the prompt as shown in the screenshot above, and paste it into the form on the download page.
5. Hit the Generate Key on that form and once you have the key, enter it into the prompt to see a Beta key accepted message.
6. The application will start the S-Off procedure and should complete in around 90 seconds. Incase it does not start, wait fro around 15 minutes and re-do the whole process.
After doing the above procedure downgrade to HTC aria 2.1 then you be able to root you aria once more and flash any files. Please donate to alpharev too they made it possible.you can find the old 2.1 ruu in xda
PS I have done it and it works.
Click to expand...
Click to collapse
Even though I switched to the atrix, I kept my aria just for this
Sent from my "Emo" rooted Motorola Atrix! Emo Thinks Possible™

nice share M8, even if it was copied directly from Addictivetips.com
im interested to know other peoples experience with this... all good i hope
only for curiosity, i didnt upgrade to 2.2 OTA

zedbra said:
nice share M8, even if it was copied directly from Addictivetips.com
im interested to know other peoples experience with this... all good i hope
only for curiosity, i didnt upgrade to 2.2 OTA
Click to expand...
Click to collapse
I really didn't have any need to either. I was perfectly happy with a fully rooted Aria running CM 7.0.3, but curiosity got the best of me, plus I had just ordered a HTC Incredible S, so I decided to 'practice' the AlphaRevX process on my Aria.
Installed the Froyo 2.2.2 update and then ran AlphaRevX and it went without a hitch. Got CWM reinstalled and superuser reinstalled and it was a really painless.

Nice!! thanks for the feedback M8
not to stray off topic, but now with S-Off achieved is it possible to downgrade HBoot with .zip file?? or is this sticky which can only be done using a box??
i may upgrade anyway just for kicks, but it would be great if we could downgrade HBoot again too

zedbra said:
Nice!! thanks for the feedback M8
not to stray off topic, but now with S-Off achieved is it possible to downgrade HBoot with .zip file?? or is this sticky which can only be done using a box??
i may upgrade anyway just for kicks, but it would be great if we could downgrade HBoot again too
Click to expand...
Click to collapse
AlphaRevX is able to overwrite HBOOT 1.02 and replace it with their own that has S-OFF. It looks like they set the HBOOT version very high, so that 'downgrading' with say a RUU will fail. So if you find a way to replace this special HBOOT, you will loose S-OFF.

yah after reading a bit i see the Alpharev hack is a pached HBOOT. so i believe you are correct, removing it will make it S-On again. too bad

Theonew said:
Why would anyone want to downgrade to 2.1 after having S-OFF!? (Rhetorical question). Once you have S-OFF, you can flash superuser, clockworkmod and custom roms without needing to downgrade to 2.1 then rooting again. Also attn1 already made a thread here on what to do after AlpharevX: http://forum.xda-developers.com/showthread.php?t=1122694.
Click to expand...
Click to collapse
This is what I want to do, but I need some help.
After using AlpharevX, I'll get S-OFF. Then, I just want to root the phone and be able to do a nandroid backup. I don't want to flash any ROM at this time.
The link you posted to does not have a clockworkmod listed for Aria. Which one do I use?

i would use THIS One. finally Clockwork without the recovery screen during charging
once you aquire S-off you can install Clockwork using Android Flasher

amlothi said:
This is what I want to do, but I need some help.
After using AlpharevX, I'll get S-OFF. Then, I just want to root the phone and be able to do a nandroid backup. I don't want to flash any ROM at this time.
The link you posted to does not have a clockworkmod listed for Aria. Which one do I use?
Click to expand...
Click to collapse
It does have it listed for Aria. The Aria is codenamed as Liberty. It's ClockworkMod is here: http://forum.xda-developers.com/attachment.php?attachmentid=591945&d=1305031790. You can get android flasher from here: http://forum.xda-developers.com/showthread.php?t=794638. Unzip it, run it, select recovery at the side and click begin (Your phone will go into fastboot), find recovery.img (extracted from ClockworkMod), select it, click begin, and your done. You now have ClockworkMod 2.5.0.1 installed. To root, just go here: http://forum.xda-developers.com/showthread.php?t=1122694 and follow the "To Root" steps and then you will be rooted. To do the nandroid backup, just start ClockworkMod (Instructions in the previous link - "How to start ClockworkMod") and select nandroid.

[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!