Database Users

Radio Flashing on Incredible

Can I flash a radio.img in a update.zip from clockwork mod recovery with hboot s-on ? I saw a radio.img in the 8/01 leaked rom and my question was never answered in that thread.

Yes you can, don't see no reason why you should not be able to flash the radio in CWMR....

jahnile said:
don't see no reason why you should not be able to flash the radio in CWMR....
Click to expand...
Click to collapse
have you ever done it?
OP, until you can get a definite answer on this, dont try it

Noted was waiting for answer from unrevoked preferably.

drellisdee said:
Noted was waiting for answer from unrevoked preferably.
Click to expand...
Click to collapse
that's wise
there's a ton of misinformation about flashing radios going around. I don't really know, I updated my radio from stock hboot, but the last I heard, clockwork isn't enabled to access that partition yet.

I didn't think it was possible from CW but I think I read a post where it was being worked on. My belief at this point is that it can only be done from stock.

I'm pretty sure you are gonna have to wait for s-off and fastboot

Visionary G2 bricks - unite here

UPDATE 2: [TEST TIME]. New 2.3 rom, confirmed twice to revive soft bricks.
Link to download: http://forum.xda-developers.com/showthread.php?t=1074391 md5 fb58e249988e0fa2f50c78ce1122ffba
thanks to ilostchild for testing: http://forum.xda-developers.com/showthread.php?t=1074799
______________________________________________________________________________________________________
UPDATE: [UNITY POSTPONED] - sorry guys, I was overexited when I heard about the leak and presumed it was a signed flashable rom that can update SHIP S-ON 1.22 phones with corrupted system partitions from bad visionary permroot attempts. It turned out what we have is partition dumps, so again we are back to waiting for the official rom.
___________
There is a flashable non-signed gingerbread rom from HTC: - unfortunately not good for reviving bricks.
http://forum.xda-developers.com/showthread.php?t=1054198
Check sha1 after you download.
Need bricked testers to try to revive your phones. - already confirmed to not work once
___________

People still use Visionary?

it happens from time to time - people who don't want to install SDK and are OTA 1.22.
and there are tons of visionary guides spread all around too. people bump into them and attempt rooting.

in the minds of lazy/newer members, they think visionary is easier and never read the warnings of "Don't use it to root your [email protected]#@!#[email protected][email protected]!" =D

Used it 4 times to temp root never had a problem. Perma root I used the gfree via term emulator method. Adb I cannot get to work.
Nonsense!

I hope you all realize that there's a sticky in the General section that covers this.
Sent from my HTC Vision using XDA App

Yup I see some people still recommending the "one click" Visionary root in some forums. Ouch. I will say though that it seems fine for temprooting. I used it for that, and like some other people on this thread, proceeded to use Gfree to gain permroot. I think many uninformed may be tempted by that pretty little box on Visionary that says "Attempt Permroot Now" though.....

I tried last night to revive a g2 brick and I got sign errors

ilostchild said:
I tried last night to revive a g2 brick and I got sign errors
Click to expand...
Click to collapse
you used the leaked tmous ginger rom, renamed it to PC10IMG.zip, put it in the root of sdcard and powered up while pressing volume down?

I did oem ruu and did fastboot flash.zip and 12 signature errors

ah, i see - did some digging and found out that the leak is partitions dumps, not official rom. Already changed the first post.
Too bad we still have no remedy for those bricks.
Let's allow this thread to sink until the right time comes.

update 2 on page 1, post 1

Yup glad to see this up and hope see lot of re living g2's and bad part no root for new leak

ilostchild said:
Yup glad to see this up and hope see lot of re living g2's and bad part no root for new leak
Click to expand...
Click to collapse
thank you again for testing both the previous and the current leak.

Anytime welcome, now lets see new root

a second confirmation: http://forum.xda-developers.com/showthread.php?t=1025135&page=4

killswitch11 said:
I will say though that it seems fine for temprooting.
Click to expand...
Click to collapse
Thanks for this information! I don't really have the need to root my phone, and temproot is convenient when I need it.

Confirmed working.
Thanks.
Got this link from irc #G2ROOT. Very helpful guys there.

[Q] Unrevoked 3.32 and HTC Wildfire

Hey. Well searching on the forums or at all I just can't find a straight answer.
I have HTC Wildfire with Android 2.2.1. Can I use the newest Unrevoked 3.32 now to root this device?
I went through all the posts in this thread and the last person on page 47 mentioned he was able to do so: http://forum.xda-developers.com/showthread.php?t=788776&page=47
I want to be sure before I attempt to do this and possibly brick it

Well, thus far, that is the only post that has show unrEVOked to work on 2.2 ota.
May I suggest to you my way?
http://forum.xda-developers.com/showpost.php?p=14855147&postcount=1
(No reports of any brickings thus far.)

Kulverstukass said:
I went through all the posts in this thread and the last person on page 47 mentioned he was able to do so: http://forum.xda-developers.com/showthread.php?t=788776&page=47
Click to expand...
Click to collapse
He (post #461) didn't clearly say that he used unrevoked.
Posting in that related thread doesn't mean using the process right.
And if u can see his previous post (#460), it gives the link to this process
http://joel5121.blogspot.com/2011/06/wildfire-22-root-tutorial.html
So, don't use unrevoked for wildfire alpharev hboot. Ofcourse we should't forget unrevoked .

bharatgaddameedi said:
He (post #461) didn't clearly say that he used unrevoked.
Posting in that related thread doesn't mean using the process right.
And if u can see his previous post (#460), it gives the link to this process
http://joel5121.blogspot.com/2011/06/wildfire-22-root-tutorial.html
So, don't use unrevoked for wildfire alpharev hboot. Ofcourse we should't forget unrevoked .
Click to expand...
Click to collapse
I s-off my wildfire with ApharevX and I root with SuperOneClickRoot to get Superuser and I Flash custom recovery (Clockworkmod 2.xxx or 3.xxx) with PC49IMG.ZIP

Bbuummpp

Kulverstukass said:
Bbuummpp
Click to expand...
Click to collapse
Your question was answered. Why bump needlessly? No you can NOT use Unrevoked to root your device. You will have to get S-OFF first via AlphaRev X, then, use SuperOneClick v1.9.5 to get root, and, if you are interested in getting a Custom Recovery to flash Custom ROMs and stuff, you can follow nejc's post.
Unrevoked does not come into the picture at all if you are on official 2.2.1.
One more thing, there is no way to remove S-OFF once you perform it. (yet) So, if warranty is essential for you, keep this in mind.
EDIT: Read the Post before the post on Page 47 of the thread you posted (Last Post of Page 46). Then you will see the continuity. He did NOT use Unrevoked to root his phone.

This http://forum.xda-developers.com/showthread.php?t=788776&page=47 (same as the link above) is also the method I used and I must say it worked like a charm!

3xeno said:
Your question was answered. Why bump needlessly? No you can NOT use Unrevoked to root your device. You will have to get S-OFF first via AlphaRev X, then, use SuperOneClick v1.9.5 to get root, and, if you are interested in getting a Custom Recovery to flash Custom ROMs and stuff, you can follow nejc's post.
Unrevoked does not come into the picture at all if you are on official 2.2.1
Click to expand...
Click to collapse
Well, 3xeno, you CAN use Unrevoked to root the device. I did, worked flawlessly.
1.) S-OFFed with AlphaRev X.
2.) Installed 2.1 RUU.
3.) Used Unrevoked to root and flash recovery.
4.) Happily using CyanogenMod 7.

smokzye said:
Well, 3xeno, you CAN use Unrevoked to root the device. I did, worked flawlessly.
1.) S-OFFed with AlphaRev X.
2.) Installed 2.1 RUU.
3.) Used Unrevoked to root and flash recovery.
4.) Happily using CyanogenMod 7.
Click to expand...
Click to collapse
It may be working. But it shouldn't be recommended buddy.
After s-off, ruu + unrevoked is completely unnecessary process and a risky process which includes possibility of errors. And moreover a lot lengthier process.
I think these are some disadvantages of it...
-- it includes flashing of radio and an attempt to overwrite hboot both of which are sensitive process. Ofcourse RUU generally will not brick the phone. But when phone is S-OFF, it skips the signature check which means AFAIK it cannot differentiate a bad file and a good file.
-- there will be two eclair RUUs present. And flashing the oldest eclair RUU will mostly result in touch screen failure. This should be fixed by flashing the newest eclair or froyo ruu again.
-- I think the unrevoked version installs the 2.x recovery for wildfire. Since unrevoked is not released for a while for wildfire I think so. If yes, it means cannot install 2.3 roms unless using rom manager or by reflashing recovery with regular processes. And ofcourse the offline charging bug.
Unrevoked software hacks the greatest security so as to install the custom recovery. And what if there is no security at all. Even simplest methods can do the job.
Sent from my HTC Wildfire using XDA App

smokzye said:
Well, 3xeno, you CAN use Unrevoked to root the device. I did, worked flawlessly.
1.) S-OFFed with AlphaRev X.
2.) Installed 2.1 RUU.
3.) Used Unrevoked to root and flash recovery.
4.) Happily using CyanogenMod 7.
Click to expand...
Click to collapse
Sure, but, I wont recommend it. Also, because it seems that this method is widely recommended, the forums are full of "Touchscreen Fail" after flashing the Eclair RUU.
Besides, I don't get what's the issue with using Fastboot, where just 1 line in Command Prompt will do it, but, whatever suits people............ Fastboot is supposed to be a breakthrough feature when you get S-OFF using AlphaRev X, and, it's sort of an "insult" to not use it.

Well, it worked for me. I guess I'm lucky.
Sent from my HTC Wildfire using XDA App

[WIP]Temp-root Gingerbread EVOs

my evo is rooted already and i havent paid much atention since i got my 3d but was there an HBOOT update in the GB OTA as compared to the last Froyo 3.70?
If there wasnt, anyone should be able to a simple downgrade with a previous RUU and then use any of the working root methods for froyo.
just a thought i had while being bored.

Nope, new bootloader is locked. Cant downgrade.

EVOlvedAndroid said:
Nope, new bootloader is locked. Cant downgrade.
Click to expand...
Click to collapse
so there was a bootloader update?

I really don't even know what to say anymore. I give up. Someone else can do it.

github said:
I really don't even know what to say anymore. I give up. Someone else can do it.
Click to expand...
Click to collapse
+1 thats all i have to say about that

what about replacing the system.img in in the latest pc36img with one from the last froyo? if the bootloader stays intact it should flash the froyo sys image and then you could at lease have temp root

t3project said:
what about replacing the system.img in in the latest pc36img with one from the last froyo? if the bootloader stays intact it should flash the froyo sys image and then you could at lease have temp root
Click to expand...
Click to collapse
The short version is there is no way around or tricking the bootloader. Pretty much every way imaginable to do this has been tried a bunch of times. We need to find a new exploit to get in. Several devs are working on it and itay happen soon. Seems to be more problematic than any one expected.

firket2000 said:
The short version is there is no way around or tricking the bootloader. Pretty much every way imaginable to do this has been tried a bunch of times. We need to find a new exploit to get in. Several devs are working on it and itay happen soon. Seems to be more problematic than any one expected.
Click to expand...
Click to collapse
yes, but you're not tricking the bootloader. the bootloader remains the same. the sys image is all you are changing and the signatures should remain intact if it is pulled out of a froyo ruu. for that matter even try placing a rooted OTA sys image in it. this would not gain s-off but you could run a shell root and su if it would work.

t3project said:
what about replacing the system.img in in the latest pc36img with one from the last froyo? if the bootloader stays intact it should flash the froyo sys image and then you could at lease have temp root
Click to expand...
Click to collapse
As far as I understand, the new bootloader won't allow for downgrading or flashing anything that doesn't match HTCs signature....so modifying files is out of the question....
Sent from my PC36100 using XDA App

t3project said:
what about replacing the system.img in in the latest pc36img with one from the last froyo? if the bootloader stays intact it should flash the froyo sys image and then you could at lease have temp root
Click to expand...
Click to collapse
Can't do that, it would break HTC's signature and the bootloader would not accept it

I need to save this response in a text file so I can just copy and paste it every day.
You can't modify the contents of a RUU provided by HTC on an S-ON HBOOT. The zip is signed by HTC with their private key. The HBOOT has the public key. Changing just 1 bit on the zip will invalidate the private key and HBOOT won't allow it to flash. This is the reason for wanting S-OFF, so you can flash anything via HBOOT (Recovery, for example) without any signature checks.
You also can't downgrade the HBOOT, as it will give you an error about an earlier version.
All the obvious ideas have been tried, over and over again over the past few months since the new update hit.
If you are still confused, please see this article on Wikipedia about Public Key Cryptography.

Don't forget to add that goldcards and battery pull microsd swaps do not work either.

Well, eff. I switched back to Sprint and back to the EVO today after a (very unpleasant) experience with T-MO and the G2X, only to find out my brand new EVO is already on Gingerbread and can't be rooted, ruling out the best part about owning an EVO... all the awesome custom ROMs. Lovely.

There's been all types of shenanigans occurring trying to root this thing. Including physically planting in the ground. No root from that either. Appreciate where you're coming from and trying to help and all though

jjones1983 said:
Well, eff. I switched back to Sprint and back to the EVO today after a (very unpleasant) experience with T-MO and the G2X, only to find out my brand new EVO is already on Gingerbread and can't be rooted, ruling out the best part about owning an EVO... all the awesome custom ROMs. Lovely.
Click to expand...
Click to collapse
Its being worked on right now so no worries
Sent from my PC36100 using XDA App

I'm rooted but jw is there any news on when that source will be out?
My stupid friends at work wouldn't let me root their froyo and now want to pay me to root their gb I don't even want $ .
Sent from my PC36100 using XDA App

Do not S-ON your edited HBOOT!

As there are more and more firmware coming, people will be installing them more and more... Same thing about people that wants to go back to stock. This thread could be considered useless and will make people say "yeah man, I knew it I'm not so stupid" that's OK! You're right.
I just wanted to remember that you shouldn't ever ever ever S-ON your HBOOT if it is edited by someone else! This will immediately brick your device, if you want to check do it. You need first to replace your current HBOOT with a stock one and then you'll be good to go.
@Sneakyghost:
* Before resetting Security to ON (S-ON) you MUST flash a stock/unchanged HBOOT! Your device will brick instantly if you set Security ON and reboot on a modified HBOOT!
Click to expand...
Click to collapse

In all the hboot threads it clearly states this
And it's not locking your bootloader that bricks it, it's s-on that does it
Sent from my HTC One using Tapatalk

superchilpil said:
In all the hboot threads it clearly states this
And it's not locking your bootloader that bricks it, it's s-on that does it
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I thought it was if you: fastboot oem writesecureflag -3 it will check if it's a modified hboot.
Sent from my HTC One using Tapatalk

I knew That simply locking the hboot would have bricked the device
Sent from my HTC One using XDA Premium 4 mobile app

@superchilpil you were right, I've edited the OP now and it should be ok now... :good:

matt95 said:
@superchilpil you were right, I've edited the OP now and it should be ok now... :good:
Click to expand...
Click to collapse
Wow, I think I've read about 20 threads so far about this, and this is the first time I've seen this corrected... Lots of threads always mentioned locking the bootloader as the issue if you don't have stock hboot.
I actually had a few questions about this,
1. Does the hboot version have to match that of the firmware ? ( 1.54 for 2.24.x.x for example ?) or does it simply have to be any stock hboot ?
2. Are there any differences between hboot for various carriers ?
3. I've read multiple times that running an RUU will not allow you to downgrade unless you have superCID, I don't understand this. I thought the RUU wouldn't run if the CID didn't match. From what I had understood previous to reading that is simply that an RUU cannot be used to downgrade the firmware or the hboot version, that can only be done manually with S-off
Thank you for your time and for the clarification!

ieldra said:
Wow, I think I've read about 20 threads so far about this, and this is the first time I've seen this corrected... Lots of threads always mentioned locking the bootloader as the issue if you don't have stock hboot.
I actually had a few questions about this,
1. Does the hboot version have to match that of the firmware ? ( 1.54 for 2.24.x.x for example ?) or does it simply have to be any stock hboot ?
2. Are there any differences between hboot for various carriers ?
3. I've read multiple times that running an RUU will not allow you to downgrade unless you have superCID, I don't understand this. I thought the RUU wouldn't run if the CID didn't match. From what I had understood previous to reading that is simply that an RUU cannot be used to downgrade the firmware or the hboot version, that can only be done manually with S-off
Thank you for your time and for the clarification!
Click to expand...
Click to collapse
1. Matching firmware/hboot is always the best route possible as it can minimize any issues that may arise, so I suggest it.
2.As far as compatibility issues there aren't any, the hardware on all these devices are almost exactly alike so running another hboot is quite possible. Although I suggest keeping to your carriers hboot to minimize issues. Or atleast keep a backup of yours
3.You can downgrade only if you are S-OFF, otherwise you can only upgrade or flash the corresponding firmware you're currently on. SuperCID only allows you to flash RUUs/firmware from other carriers or regions. CID stands for Carrier Identification. So even with supercid you can't downgrade, there are security measures in place to stop you from downgrading you hboot without s-off, it either won't write or you will end up with a brick.
Sent from my HTC One using Tapatalk