Sure that's no prollem. Ill take a look later this evening. Also can you get me an md5 of your file?
Need to be as cautious as possible when flashing bootloaderz.
Where could i get the md5 file from?
And if its from the phone how do i copy it?
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root thunderbolt rooting methods(updated 8-24-2011)
- Thread starter scotty85
- Start date
-
- Tags
- htc thunderbolt
Where could i get the md5 file from?
And if its from the phone how do i copy it?
If the file is on your phone use AFV (market link) to get the md5, if it is on your CPU google search for md5summer and install it to take the MD5
Thanks for the answer.
Il just presume its on my phone because the only thing i downloaded was the RUU. Il try the app from market
Okej so i might have done this completely wrong but first i tried using the phone but that was no good. DIdent understand anything.
Then i tried it on the cumputer and i was abel to creat a md5 file from the ruu.
uploaded the file here: 2shared - Upload complete
Did i do it right or did i mess up completely?
I compared the checksum (hex) numbers and they were identical on both the phone after verification and on the computer after the creation.
oh btw, sry about my bad gramar but im not from an english speaking country
Then i tried it on the cumputer and i was abel to creat a md5 file from the ruu.
uploaded the file here: 2shared - Upload complete
Did i do it right or did i mess up completely?
I compared the checksum (hex) numbers and they were identical on both the phone after verification and on the computer after the creation.
oh btw, sry about my bad gramar but im not from an english speaking country
Did i do it right or did i mess up completely?
I compared the checksum (hex) numbers and they were identical on both the phone after verification and on the computer after the creation.
oh btw, sry about my bad gramar but im not from an english speaking country
Normally you don't get a file from generating a MD5 sum, it is a hex # that allows you to verify the file was downloaded with no issues if it matches the original file you should be okay.
I wouldn't have known you weren't from an English speaking country if you didn't tell me so no need to be sorry
I haven't used revolutionary myself but from what you posted about your hboot it looks like you have s-off so you should be able to flash a recovery and rom I would think. I don't believe the thunderbolt and desire. Scotty will be able to look into it further for you if needed, I am at work currently and my time to devote to forums can get limited
Normally you don't get a file from generating a MD5 sum, it is a hex # that allows you to verify the file was downloaded with no issues if it matches the original file you should be okay.
I wouldn't have known you weren't from an English speaking country if you didn't tell me so no need to be sorry
I haven't used revolutionary myself but from what you posted about your hboot it looks like you have s-off so you should be able to flash a recovery and rom I would think. I don't believe the thunderbolt and desire. Scotty will be able to look into it further for you if needed, I am at work currently and my time to devote to forums can get limited
Najs but just said so in case you wondered about wrong spelling
i cant spel most things right tbh.And every other thing you just said about verifying and stuff was like pure hebrew to me
Hoping for him to find something that even a four years old kid would understand
Loved his previously post, never seen anything that easy! Thanks for your help though. Hope it saves him alot of time =)
scotty85
Extreme Android User
yeahha,he is trying to unroot,so we need to get him a desire bootloader. very luckily for him,the image was the wrong type and it didnt flash hbooteng.nb0.
aasterix im not sure if you realize how very close you were to having a certified brick on your hands if your phone had replaced its bootloader with this one
im not sure how someone could direct you here without realizing that some very important files were different. not pickin on you by any means,as you were told this would work.
at any rate,your RUU is in .exe format,and luckily the ruu let me get all the way to where i needed to be to extract the rom from the .exe with my eris plugged in instead of a desire
all i need to do is change some commands and maybe upload a new miniadb file with your hboot enclosed,and put you togerther a new guide.
but first,we need to verify the integrity of this file. we need to be 100% sure that i have the exact same file that you have flashed to your phone. when i check the md5 sum on my pc of the file you uploaded,heres what i get:
Unroot-Desire-Froyo-2.10.exe ec4251cf5458f4b5807fa695714253e4
did you get an md5 sum program installed on your computer? if you can check the file you downloaded and flashed,and its the same,then im pretty comfortable doing this for you.
if its different,then we cant risk that the part of the file that has become corrupt or contaminated might be the bootloader.
yeahha,you arent able to download and verify until later,are you?
aasterix im not sure if you realize how very close you were to having a certified brick on your hands if your phone had replaced its bootloader with this one
im not sure how someone could direct you here without realizing that some very important files were different. not pickin on you by any means,as you were told this would work.
at any rate,your RUU is in .exe format,and luckily the ruu let me get all the way to where i needed to be to extract the rom from the .exe with my eris plugged in instead of a desire
all i need to do is change some commands and maybe upload a new miniadb file with your hboot enclosed,and put you togerther a new guide.
but first,we need to verify the integrity of this file. we need to be 100% sure that i have the exact same file that you have flashed to your phone. when i check the md5 sum on my pc of the file you uploaded,heres what i get:
Unroot-Desire-Froyo-2.10.exe ec4251cf5458f4b5807fa695714253e4
did you get an md5 sum program installed on your computer? if you can check the file you downloaded and flashed,and its the same,then im pretty comfortable doing this for you.
if its different,then we cant risk that the part of the file that has become corrupt or contaminated might be the bootloader.
yeahha,you arent able to download and verify until later,are you?
scotty85
Extreme Android User
cool if you could verify the ruu he linked,that would be great. theres an md5 on the multiupload page,and it doesnt match what i have,so it makes me a lil nervous.
ive got everything uploaded and ready to go for him if we can just verify this file as a good,working copy,im pretty comfortable releasing it
scotty85
Extreme Android User
looking back thru things,i caught this statement.
so do you mean that after running the RUU,the phone OTAed to newer firmware than what this ruu is? if the answer is yes,i believe you should run this ruu again before changing the hboot. the bootloader may be different in the OTA,and if we replace revolutionary with this one it may cause prollems(i dont think it will but i dont know for sure)
that way we will be placing an hboot with matching firmware when we change it.
that is the safest way to do this IMO.
after the operation is complete, you can allow the phone to OTA to current firmware
Hi and sorry for late reply.
Were sleeping and im at GMT+1
Nah no offens taken, just good that your honest how els can i learn
Im just glad i dident reck my phone, phew.
Yes i did the OTA updating to the newest version, but if you want me to reflash with this ruu befor i do anything to hboot then il do it.
ec4251cf5458f4b5807fa695714253e4 was the sum i got when doing it on the computer.
Were sleeping and im at GMT+1
Nah no offens taken, just good that your honest how els can i learn
Im just glad i dident reck my phone, phew.
Yes i did the OTA updating to the newest version, but if you want me to reflash with this ruu befor i do anything to hboot then il do it.
ec4251cf5458f4b5807fa695714253e4 was the sum i got when doing it on the computer.
scotty85
Extreme Android User
excellent
i will pm you the new guide with links,just delete the entire "tbolt" file from your c: drive,and use the new one.i defintely dont have a prollem with you sharing it if it helps other desire folks,just make sure you provide a link to the ruu you used,as i dont know what would happen if you installed an older hboot with newer firmware.prolly nothing,but im not in the habit of reccomending things i dont know 100% and have tested,so if youre going to use this,have people run the ruu first,flash the hboot second
also,i just have to add the usual disclaimer: i dont have a desire,so i cant test this,and im not obliated in any way to anyone that uses this,screws it up somehow,and bricks their device
so,run your ruu again,then try the procedure again with the file and commands in the pm. let me know how it goes
scotty85
Extreme Android User
thanks for verifying. since we all got the same # it should be OK.
aasterix,PM sent... please pm or post after you do this,so i know its ok. it is my nature to be nervous until i hear from yuo,since i dont have one of these phones to test on first
Im just followed by bad luck it seems.
The ruu flashing process is taking alot longer then its ever taken befor.
So long so im starting to wonder if something has gone wrong.
Its stuck at 45% in the room utility at windows and the statusbar is not moving anymore on the phone.
What would happen if i took out the usb and restarted the phone to try and restart the process?
The ruu flashing process is taking alot longer then its ever taken befor.
So long so im starting to wonder if something has gone wrong.
Its stuck at 45% in the room utility at windows and the statusbar is not moving anymore on the phone.
What would happen if i took out the usb and restarted the phone to try and restart the process?
scotty85
Extreme Android User
sounds good
just to verify... this is the exact same file you ran before,correct? you didnt delete it after,and have to re-download it did you?
sounds good
just to verify... this is the exact same file you ran before,correct? you didnt delete it after,and have to re-download it did you?
nop its the same file that i downloaded the first time.
If anything i just copyed it to a new folder befor i did the checksum because if anything was to happend with the file i still would have the oroginal untampered.
But now im starting to realise that the flash wont work =/
Bahh, well il let it be pluged in untill i return from work.
Im off to work now, hope you have a nice day and ty for all the help =)
Il reply later on when im off work.
scotty85
Extreme Android User
from the android info doccument,this is for firmware 2.10.405.2. i found another ruu for it,downloaded it,and it does have a different md5 than the other one we used. this doesnt neccessarily mean the one we used is bad,just that there is something different about it.
this is the link to is,just in case we need it later.
RUU_Bravo_Froyo_HTC_WWE_2.10.405.2_R_Radio_32.44.00.32U_5.09.05.30_2_release_142828_signed.exe
when i get home later,ill extract rom.zip from this one,and make sure its the same as whats in your download,and make sure the hboot is the same as i uploaded for you.
if this is the same file you used the first time,it should still work. if its different,might want to redownload and try again.
if you get it flashed,dont do the hboot update until ive had a chance to check the 2nd ruu
this is the link to is,just in case we need it later.
RUU_Bravo_Froyo_HTC_WWE_2.10.405.2_R_Radio_32.44.00.32U_5.09.05.30_2_release_142828_signed.exe
when i get home later,ill extract rom.zip from this one,and make sure its the same as whats in your download,and make sure the hboot is the same as i uploaded for you.
if this is the same file you used the first time,it should still work. if its different,might want to redownload and try again.
if you get it flashed,dont do the hboot update until ive had a chance to check the 2nd ruu
scotty85
Extreme Android User
cool,im not sure what you should do. hopefully it will fail with an error message at some point,so the battery doesnt just run down with it pulgged in.
let me know what you find when you get home. its goot to know that this same file worked for you before.
off to work myself