Ok so this issue has now been fixed, download the following file and place it on your SD card, start your phone up with, volume down + power and follow the instructions.
PB99IMG.zip
Thanks to everybody who tweeted this in.
o.o adamg - not really! Why did you do that?
That could not mean the end of opendesire and your sense roms could it?
Adam you should have known better, but still look at root method now on my gf's desire will post when I get root
ohh crap i was holding out hoping you'd have an update. hope someone figures it out for your sake if any
I will still be releasing, I have people on the team who test the roms and report the bug errors for me to fix
I will still be releasing, I have people on the team who test the roms and report the bug errors for me to fix
Click to expand...
Click to collapse
If need more help testing email me I'm global mod on villainrom.co.uk
Email [email protected]
Lots of experience
Cheers
Mike
any chance of getting a full root while were at it? it would be awesome to use metamorph
i'm sorry to hear that adam,
but i seriously lol ...... so sorry.
i love your roms.
i got the same problem
http://htcpedia.com/forum/showthread.php?t=2934
Prema999 said:
http://htcpedia.com/forum/showthread.php?t=2934
Click to expand...
Click to collapse
Not possible because you need root to place the flash-executable and the img into a read only directory.
Tried it too but you definitly need a method to execute some lines of code. adb push to /data is not possible because:
- adb is not working
- you can't get root to remount /data rw instead of ro.
Before i flash anything... How did you get there?? Flashed new 2.2 ROM? Or RADIO? or????
after we upgraded the official version throw htc live update
And this?
Isn't it possible to hex edit the version string to trick it into believing it is a newer version?
Prema999 said:
http://htcpedia.com/forum/showthread.php?t=2934
Click to expand...
Click to collapse
twicejr said:
Isn't it possible to hex edit the version string to trick it into believing it is a newer version?
Click to expand...
Click to collapse
that's not so easy, i think it is nearly impossible, you can't hex edit something on a read only phone (if we could edit sth we could flash the 0.80 hboot back), and hex-editing the whole RUU is - as i think - because of encryption and checksum checks etc impossible, too. we have to inject the flash software and the image - and this is impossible without rw / root.
wiggy2k said:
that's not so easy, i think it is nearly impossible, you can't hex edit something on a read only phone (if we could edit sth we could flash the 0.80 hboot back), and hex-editing the whole RUU is - as i think - because of encryption and checksum checks etc impossible, too. we have to inject the flash software and the image - and this is impossible without rw / root.
Click to expand...
Click to collapse
damn you htc
madman_cro said:
damn you htc
Click to expand...
Click to collapse
I think there WILL be a root-hack. it is just a cat and mouse game, htc is now in front, but the dev scene will be back soon with successful rooting i think. so dont fear and be patient
the only hardware which was not exploit-hacked for now is the playstation 3. (I hate not having otherOS anymore ...)
yes should they come with a new release because all the new htc devices will come with 0.92 at least
Adam, get on Freenode IRC and query me.
There's a few things I'd like to test with you
(IRC nick = IEF)
same problem impossible to downagrad hboot or install "RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4.06.00.02_2_release_126984_signed"
Related
Hello all
I downloaded the new ROM from the TW HTC site some minutes ago and proceed with flashing some time thouought the FLASH the pfone gave an error "Checking Custom ID"
"Update Failed"
And Android Update says ERROR 131 CUSTOMER ID ERROR
Now I can do nothing! The phone goes into HBOOT 1.76.0007 and I have a big icon with a memory chip on the bottom of the screen!
Pleace help me restore the hboot and recovery roms! The rest I'll menage.
same error..
You cant flash the update, don't do it.
Eugene is having a 32B ROM done and i belive he is uploading it atm.
32A users will soon have a flashable ROM.
WebghostDK said:
You cant flash the update, don't do it.
Eugene is having a 32B ROM done and i belive he is uploading it atm.
32A users will soon have a flashable ROM.
Click to expand...
Click to collapse
And for the ones that did it?
Great, i flashed my 32A via fastboot, and now im stuck in some strange state... I think i might have gotten a corrupt radio on it somehow...
Epedemic said:
Great, i flashed my 32A via fastboot, and now im stuck in some strange state... I think i might have gotten a corrupt radio on it somehow...
Click to expand...
Click to collapse
Yup it seems that way, as it now always hangs when flashing radio (trying a official 2.17 upgrade) grr...
Epedemic said:
Yup it seems that way, as it now always hangs when flashing radio (trying a official 2.17 upgrade) grr...
Click to expand...
Click to collapse
Yes. Cause you flashed a new HBoot.
You should wait, while romcookers will find way to downgrade new hboot
or repacked rom to flash properly to all customers, not only taiwanese.
I think it is time to clear things out:
DO NOT FLASH / UPDATE THIS ROM TO YOUR DEVICES!!!! - This means: Wait for someone to release correct ROM Updates to your devices. This official update is ONLY for TW devices. When you decide to flash something to your devices you should be very sure that you are not doing a stupid move! If someone tells you not to do it then you should hear that! Flashing something isn't like dressing a tshirt, and this means that if you choose a wrong size tshirt you can always take it off and dress another that fits you right. Flashing something that doesn't fit your device can easily brick it! Be aware!
5[Strogino] said:
Yes. Cause you flashed a new HBoot.
You should wait, while romcookers will find way to downgrade new hboot
or repacked rom to flash properly to all customers, not only taiwanese.
Click to expand...
Click to collapse
Indeed. I thought i was safe cause i flashed the files (boot.img, radio.img and system.img (which failed) via fastboot... Guess not... So now im stuck at the same screen with the cross over the ram chip
joaosousa said:
I think it is time to clear things out:
DO NOT FLASH / UPDATE THIS ROM TO YOUR DEVICES!!!! - This means: Wait for someone to release correct ROM Updates to your devices. This official update is ONLY for TW devices. When you decide to flash something to your devices you should be very sure that you are not doing a stupid move! If someone tells you not to do it then you should hear that! Flashing something isn't like dressing a tshirt, and this means that if you choose a wrong size tshirt you can always take it off and dress another that fits you right. Flashing something that doesn't fit your device can easily brick it! Be aware!
Click to expand...
Click to collapse
Yes we already know this! But it is too late! So please tell us how to fix the mess we have created!
I agree don't do stupid things in excitement. If you have eng spl etc by flashing all imgs )boot, radio etc) you may brick your device, so please please be careful wait for a update.zip file from greats mods like drizzy, eugene etc.
Once again I want to point that the purpose of this thread is help theese of us that DID the flash NOT knowing that it will NOT work!
OrionBG said:
Yes we already know this! But it is too late! So please tell us how to fix the mess we have created!
Click to expand...
Click to collapse
In my understanding the only thing you can do is to wait the official htc EU flasher (HTC said around mid November) and see if it's able to replace everything loading a proper radio/spl on the bricked device, acting on a lower level.
Otherwise you would just keep that expensive plastic brick ...
I am sorry, i was also eager to upgrade, but if HTC let you download their flasher only with a proper TW serial number, and if they've already advertised that you need to wait 2 or 3 weeks more for european firmware, then there should be a reason: so I didn't.
Hope you will be able to fix, but I am not too confident: guess you will need service.
It's ALIVE!!!! I have no idea how or why, but after tons of failed attempts and failed fastboot commands i now have the 3.03 update on my scandinavian 32a which i thought was bricked!
Epedemic said:
It's ALIVE!!!! I have no idea how or why, but after tons of failed attempts and failed fastboot commands i now have the 3.03 update on my scandinavian 32a which i thought was bricked!
Click to expand...
Click to collapse
Good. Now please write everything, what you did to get device alive)
5[Strogino] said:
Good. Now please write everything, what you did to get device alive)
Click to expand...
Click to collapse
yes yes post it please
i have no idea what actually did it, but it is possible that it was because i did a adb logcat command while the 3.03 update was running..
I can see that i have the 1.76 spl, and the new radio (which kept failing on me before)
i have try now to do adb logcat while update is running, but adb continuos stay in waiting for device, or say adb server is out to date ecc
Epedemic said:
i have no idea what actually did it, but it is possible that it was because i did a adb logcat command while the 3.03 update was running..
I can see that i have the 1.76 spl, and the new radio (which kept failing on me before)
Click to expand...
Click to collapse
Strange thing... adb logcat simply outputs log into console... How outputing logs can affect to flashing properly?
p.s. please post your full SPL-info too.
p.p.s. I think we need get right order to flashing this update. You tried to flash images via fastboot. What order do you have at first (boot - 1, radio - 2, system -3)?
What did you do at last?
i can't accesso to fastboot mode beacuse the phone stay in RUU USB ..
I AM NOT RESPONSIBLE FOR THE "BRICKING" OF YOUR DEVICE. FLASHING A RADIO IS DANGEROUS, DO NOT PULL THE BATTERY OR STOP THE UPDATE AT ANY TIME. FOLLOW ON SCREEN INSTRUCTIONS AND BE PATIENT.
That said... let the fun begin!!!
Anyhow this is the latest radio from:
RUU_Supersonic_1.32.651.6_Radio_1.39.00.05.31_release_171253_signed
INSTRUCTIONS FOR FLASHING:
- Download the EVO-1.39.00.05.31-radio-signed.zip from below
- Put it on the root of your sdcard (top level)
- Reboot to recovery and run .sh or .bat file to gain custom recovery
- Select "Flash zip from sdcard" in recovery
- Select "EVO-1.39.00.05.31-radio-signed.zip" and confirm the flash
- Ath the bottom it will say "Reboot via menu to complete installation" do as it says and select reboot in the menu
- it will then say "writing image" then reboot to a screen with a phone and a green arrow
- then it will reboot again showing the same screen with the arrow but have a little status bar.
- after that it will reboot into android and prompt u with a congrats on flashing the new radio. press ok ansd cancel the firmware update (its useless )
- navigate to settings>About phone>Software information
- under Baseband u will see "1.39.00.05.31"
- your done now. enjoy the awesome new radio <~~~ congrats its not a brick!!!
DOWNLOAD LINK
Thanks toast!
Sweet thanks
Wait where's the link lol
Download Link
Download Link PLZ
is this the radio extracted from football's RUU_Supersonic_1.32.651.6 and packaged into a custom update.zip for recovery?
change log? any idea what it updates/fixes/improves?
thanks!!
toast your a monster
Man what a good job your doing toast I can hardly keep up I am loving my rooted Evo I/O Phone tho thanks to you I am even sending someone my Incredible to see about root cuz I sill never use it again lol
joeykrim said:
is this the radio extracted from football's RUU_Supersonic_1.32.651.6 and packaged into a custom update.zip for recovery?
change log? any idea what it updates/fixes/improves?
Click to expand...
Click to collapse
htc doesnt do chage logs in their ruus anymore. ur guess is as good as mine as to whats changed. they obviously want u to use this radio for a reasion or else they wouldve just left the old one.
What is the md5sum of EVO-1.39.00.05.31-radio-signed.zip?
could this be a fix for the weak Wifi radio?
which radio is this?
toastcfh said:
htc doesnt do chage logs in their ruus anymore. ur guess is as good as mine as to whats changed. they obviously want u to use this radio for a reasion or else they wouldve just left the old one.
Click to expand...
Click to collapse
didnt see an answer to this previously?
is EVO-1.39.00.05.31-radio-signed.zip the radio extracted from football's RUU_Supersonic_1.32.651.6 and packaged into a custom update.zip for recovery?
is there a simple way to determine this? compare radios? what partition are they kept in? mtd2?
sorry bunch of questions as my thoughts flow
ChrisDos said:
What is the md5sum of EVO-1.39.00.05.31-radio-signed.zip?
Click to expand...
Click to collapse
4d9404ebc30c32b20a7b8fa304225680
joeykrim said:
didnt see an answer to this previously?
is EVO-1.39.00.05.31-radio-signed.zip the radio extracted from football's RUU_Supersonic_1.32.651.6 and packaged into a custom update.zip for recovery?
is there a way to find this out?
Click to expand...
Click to collapse
Anyhow this is the latest radio from:
RUU_Supersonic_1.32.651.6_Radio_1.39.00.05.31_rele ase_171253_signed
So should we apply this right after we follow instructions from here? http://forum.xda-developers.com/showthread.php?t=690762
Is this supposed to replace the OTA update?
Thanks toast!
pingpongboss said:
So should we apply this right after we follow instructions from here? http://forum.xda-developers.com/showthread.php?t=690762
Is this supposed to replace the OTA update?
Thanks toast!
Click to expand...
Click to collapse
this will not replace the ota. this will only replace the radio.img and yes u must be root and have access to a custom recovery
pingpongboss said:
So should we apply this right after we follow instructions from here? http://forum.xda-developers.com/showthread.php?t=690762
Is this supposed to replace the OTA update?
Thanks toast!
Click to expand...
Click to collapse
somebody can correct me if im wrong, this is just what ive gathered from reading.
yes, apply this radio udpate.zip after rooting using's toasts method and running his recovery. when the recovery UI pops up, then load this radio update.zip file posted in the OP. that way you'll still be able to keep root and have the latest radio.
this does not replace the OTA update, this update only patches the radio, it does not patch the software.
Call me stupid, but what are the benefits of flashing the radio?
Thanks for the quick response guys. So are we free to apply the OTA ourselves after we root and use this radio upgrade? I keep remembering toast saying not to apply any RUU's (not sure if the OTA update counts as an RUU)
jigglywiggly said:
Call me stupid, but what are the benefits of flashing the radio?
Click to expand...
Click to collapse
Since they don't release the changelogs, we don't know what has changed. But as toast said, there must be a reason they updated the radio.
jigglywiggly said:
Call me stupid, but what are the benefits of flashing the radio?
Click to expand...
Click to collapse
You must not be the only stupid one, Im stupid too, what does this new radio do?
arkshel said:
You must not be the only stupid one, Im stupid too, what does this new radio do?
Click to expand...
Click to collapse
could increase signal or optimize hardware. the radio controls a lot of function of the device.
thanks. Everything went well.
!!!! ROOTING/FLASHING/DOWNGRADING IS ALWAYS ON YOUR OWN RISK !!!!
Attention: This method will completely wipe your phone!!!
You can find the reworked Tutorial here: http://android-tutorials.org/
Video of the first step is online: Step 1
Video of the 3 & 4 step is online: Step 3 & 4
Known Problems
If you have problems while re-rooting or custom recovery (unrevoke) try to downgrade again with the above procedure.
Make sure you have made a new goldcard.
If you have problems e.g. 140 ERROR please follow these instructions (thx to raz2133)
This will fix your MISC Partition so you can flash back original RUU files.
Happy re-rooting
P.S. i hope you can understand this because english is not my foreign language
Great News!
Im not Root-Bricked ^^ but someone else will be happy with it =)
Edit: Why is 1 Pic from July and one from March!? And different times.
Thank you!!!
Maybe you should add: this wipes your device...
This is great, keep up the good work! =)
Edit: Are we sure those that do not have a carrier locked/branded also needs to create a goldcard?
Nitrius said:
This is great, keep up the good work! =)
Edit: Are we sure those that do not have a carrier locked/branded also needs to create a goldcard?
Click to expand...
Click to collapse
Not sure about that. i had a branded Vodafone version and unbranded it.
If someone could try without goldcard and report here
xtcislove said:
Edit: Why is 1 Pic from July and one from March!? And different times.
Click to expand...
Click to collapse
That was when the bootloader was built, not the current time.
sorch said:
That was when the bootloader was built, not the current time.
Click to expand...
Click to collapse
Ah thanks ! Dont know this =)
I hope this will work on generic devices that are not branded...
Sammy83 said:
For everyone how was in bad luck and updated to the original OTA FroYo here is a way how you can revert it.
The User maximini1 has found a thread where they describe how you can downgrade to 0.80 again.
So i try to explain how you have to do it.
Preparation
1. Make a NEW Goldcard (here)
2. Download PB99IMG.zip (here - MIRROR - germany MIRROR2)
3. Rename the downloaded file to "PB99IMG.zip" and copy it onto your SD Card.
Flashing
1. Shutdown yor mobile
2. Hold Volume up and press power
3. wait until PB99IMG.zip was found and checked
4. Press Volume Up <yes> - PICTURE 1
5. Wait until all steps are done. DON't POWER OFF YOUR DEVICE!!! - PICTURE 2
6. After flashing press Volume Up to reboot
7. done
Happy re-rooting
Click to expand...
Click to collapse
Is it working? Did try anyone?
Sammy83 said:
Not sure about that. i had a branded Vodafone version and unbranded it.
If someone could try without goldcard and report here
Click to expand...
Click to collapse
Looks like it's possible for those with an unbranded/unlocked phone:
mbroeders said:
First of all, I have an unbranded simlock-free phone. All I did was
1. download the file to SD card.
2. rename to PB99IMG.zip
3. boot into recovery (turn phone on while holding down volume)
4. just let it load the zip file and press yes when asked to install
Easy as that!
Click to expand...
Click to collapse
SharpSA said:
Is it working? Did try anyone?
Click to expand...
Click to collapse
Yes working 100%
Ok, I never rooted my android before and I have the OTA 2.2 Froyo update on an unbranded Desire. After I complete these steps, what do I need to do to install a custom rom?
Thanks!
Wheezy_be said:
Ok, I never rooted my android before and I have the OTA 2.2 Froyo update on an unbranded Desire. After I complete these steps, what do I need to do to install a custom rom?
Thanks!
Click to expand...
Click to collapse
Root your phone with unrevoked, using on of these guides for example:
Linux:
http://myhtcdesire.com/modding/how-to-root-your-desire-easily-method-1
Windows:
http://myhtcdesire.com/modding/how-to-root-your-desire-easily-method-2
Ok for the dumb and ignorant among us (a.k.a me) what state does this leave your phone in.
I get I downgrade HBOOT to 0.80 and my phone will be wiped, but what ROM will be on the phone after the downgrade will it still be the OTA rom or will it be another one?
Or do I then need to install a ROM of my choice after the downgrade, sorry if this is a really stupid question, I haven't put any custom ROM on my Desire yet and then I got the OTA update as I was thinking about checking out some custom stuff. Not had the phone long.
Thanks.
{EDIT} someone beat me to it as I was typing this post thanks for the above!
u9dbg said:
Ok for the dumb and ignorant among us (a.k.a me) what state does this leave your phone in.
I get I downgrade HBOOT to 0.80 and my phone will be wiped, but what ROM will be on the phone after the downgrade will it still be the OTA rom or will it be another one?
Or do I then need to install a ROM of my choice after the downgrade, sorry if this is a really stupid question, I haven't put any custom ROM on my Desire yet and then I got the OTA update as I was thinking about checking out some custom stuff. Not had the phone long.
Thanks.
Click to expand...
Click to collapse
After you've done the steps above you will have the following:
Blank and wiped device
Firmware: 2.1-update1 UNROOTED!
HBOOT: 0.80
Basband(Radio): 32.36.00.28U_4.06.00.02_2
Kernel: [email protected]#1
Build: 1.21.405.2 CL174215 release-keys
With that you can root and flash anything you want
Thanks for the tuto.
Hello sweety 0.80, bye bye dirty 0.92 ^_^
Worked for me.
Btw, didn't need the gc
Well, if this works AdamG doesn't have to find a way to root hboot 0.92.
:/
Sent from my HTC Desire using XDA App
Has anyone tried this on a branded, but rooted phone?
I've got an O2 branded desire with hb00t 0.83, I can root with unrevoked, but can't boot into recovery =( Hoping this will fix it.
It's works fine! Why doesn't work the recovery bat. on my PC?
u9dbg said:
Ok for the dumb and ignorant among us (a.k.a me) what state does this leave your phone in.
I get I downgrade HBOOT to 0.80 and my phone will be wiped, but what ROM will be on the phone after the downgrade will it still be the OTA rom or will it be another one?
Click to expand...
Click to collapse
Also for me, it's Volume Down + Power
Here is the latest,
It contains a new boot.img and recovery.img
http://www.unlocksolutions.us/XDA/OTA_Supersonic_3.30.651.3-3.30.651.2.zip
Anyone have any information on it ?
well thats intresting?
bad block fix maybe?
Who knows, i'm s-off for now
Updating
ill take a shot.
Ok people,
Updated the phone. Looks like root and nand unlock still possible.
tried to update but i got an error message!
What error ?
3.30.651.3 will address issues where users are experiencing power cycling when accessing the camera through some applications.
Sent from my PC36100 using XDA App
Hmm it updates a lot of crap just for a fix for camera... Anything else ? It updates the whole framework folder, fotaboot etc.
Mine threw me an error. I did a Nandroid, then downloaded and installed the new OTA.
It says,
E:Error in /cache/Supersonic_3.30.651.3-3.30.651.2_releaseziblddc3oqo05zyk.zip
(Status 7)
Installation aborted.
Weird, so far I am thinking maybe this is only for newer Evos that came with 3.30.651.2 as the default ROM (the new hardware 0004 with the new camera chip).
Mine is a Evo version 0003 with the Epson panel. Bought in July of this year of course.
Think Sprint is trying to throw us some curveballs or put a bandaid on their newest.
Doesnt make sense,
My girlfriends evo is HW V3. I updated it.
Mine is HW V2-3 and its updated now.
ok i guess this is the .30 you were talking about..how do i apply this ...as an update.zip or PC36IMG.zip thru HBOOT?... like i said on my previous post on the other thread of HBOOT 2.02 off i dont have root anymore... please let me know so i do the right thing...thanks
eldiablito004 said:
ok i guess this is the .30 you were talking about..how do i apply this ...as an update.zip or PC36IMG.zip thru HBOOT?... like i said on my previous post on the other thread of HBOOT 2.02 off i dont have root anymore... please let me know so i do the right thing...thanks
Click to expand...
Click to collapse
You cannot just "install" the file posted. Well, at least I cannot!
Here is what happens when I try and install it (both from OTA and flashed.)
Same results, see picture.
This is not the update i was talking about. read my thread i have pointed to it so many times already.
ricsim78 said:
You cannot just "install" the file posted.
Click to expand...
Click to collapse
im sorry for the dumb question...so how do i apply this to my phone? do i have to root it first or can i just apply it....im guessing i need root and a recovery image to apply the zip isnt?
nv i just saw i need a recovery image to do it...
amoamare said:
Here is the latest,
It contains a new boot.img and recovery.img
http://www.unlocksolutions.us/XDA/OTA_Supersonic_3.30.651.3-3.30.651.2.zip
Anyone have any information on it ?
Click to expand...
Click to collapse
interesting.
definitely has a kernel (boot.img) and recovery.img
majority of patches are done to /system/framework - 44 files
including - com.sprint.hardware.twinCamDevice.jar.p
system/lib/modules are also included to go along with the kernel (boot.img)
system/etc/otacerts.zip is also present
everything else is standard for an OTA, it seems.
doesn't appear to be significantly changes...also, the OTA server isn't offering this to EVOs on 3.29...
joeykrim said:
interesting.
definitely has a kernel (boot.img) and recovery.img
majority of patches are done to /system/framework - 44 files
including - com.sprint.hardware.twinCamDevice.jar.p
system/lib/modules are also included to go along with the kernel (boot.img)
system/etc/otacerts.zip is also present
everything else is standard for an OTA, it seems.
doesn't appear to be significantly changes...also, the OTA server isn't offering this to EVOs on 3.29...
Click to expand...
Click to collapse
Right - and this won't be - Sprint reps are being told to verify the HW version and Build version before doing any camera hardware swaps, etc. as putting a 3.29 build camera in a device with 3.30 build will cause nuclear meltdown
I see this causing a lot of problems in the future for Sprint (and HTC) as new updates come out - and for ROM devs as well - we now have two different frameworks and two different Evo types.... the potential for a lot of noob issues is there....
jerdog said:
Right - and this won't be - Sprint reps are being told to verify the HW version and Build version before doing any camera hardware swaps, etc. as putting a 3.29 build camera in a device with 3.30 build will cause nuclear meltdown
I see this causing a lot of problems in the future for Sprint (and HTC) as new updates come out - and for ROM devs as well - we now have two different frameworks and two different Evo types.... the potential for a lot of noob issues is there....
Click to expand...
Click to collapse
yep...i was just thinking the same issue.
The question is all evos should be able to get this due to the fact it should be backwards compatible.
zikronix said:
yep...i was just thinking the same issue.
The question is all evos should be able to get this due to the fact it should be backwards compatible.
Click to expand...
Click to collapse
Yeah - should be. I have noticed some issues with Myn's ROM on the 3.30 build that I am not sure if they're related to 3.30 or for some reason my hw v002 phone.... (pissed that I got a v002 when I got it replaced for a 4G issue - had v003 and could OC to 1.226 but now with v002 can't get above 1.15)
3.30 isn't supposed to work on hardware 0002? Works on my phone...
AS MY EVITA IS CURRENTLY BOOTLOADER LOCKED, THIS SUPERBOOT IS FOR TEST PURPOSES ONLY. USE AT YOUR OWN RISK!
Superboot is a boot.img that when booted, will root your device the first time you boot (installing su and the superuser APK). No need to flash any partitions, no need to mess around with ADB, no messing with the contents of your data partition, no overwriting the shipped ROM on your device, just boot the boot image using the instructions below and you're done!
Download
Superboot r2 - DOWNLOAD - MD5: 39a02275706d4b034c3c185b5b9b1a82
The superboot image is also 'insecure', allowing you to use 'adb remount' as well as having full ADB root access to your device until such time as you reboot after running this process (it's a non permanent ADB root as it's a 'fastboot boot' and not a 'fastboot flash' but it IS a permanent root in all other regards!).
How to use Superboot - Windows, Linux and OSX
Ensure your bootloader is unlocked using the htcdev unlock process
Download the Superboot zip file above and extract to a directory
Put your device in bootloader mode - Turn off the phone then turn on with the 'volume down' button pressed to enter the bootloader, then press the power button again to enter fastboot.
WINDOWS - double click 'install-superboot-windows.bat'
MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-mac.sh' followed by './install-superboot-mac.sh'
LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-linux.sh' followed by './install-superboot-linux.sh'
P
PS Details on how to donate should you wish to do so are in the download topic at MoDaCo.
have a mirror? ...file not found.
JSLEnterprises said:
have a mirror? ...file not found.
Click to expand...
Click to collapse
i just tried it. works for me
edit: nope, didn't work upon actually trying to grab the file
edit: thanks Paul!
Small typo, fixed now.
P
Superboot confirmed working.
manually install superuser in /superboot/ and delete the folder afterwards and update su binary (or the toast will hang)
now care to share your repack methods?
I was just about to try using the same method xperia users were using for their ics builds... and then you posted your superboot... beaten too the punch. Cheers at getting it though.
Superboot should automatically install the Superuser APK in /system/app?
P
JSLEnterprises said:
Superboot confirmed working.
manually install superuser in /superboot/ and delete the folder afterwards and update su binary (or the toast will hang)
now care to share your repack methods?
I was just about to try using the same method xperia users were using for their ics builds... and then you posted your superboot... beaten too the punch. Cheers at getting it though.
Click to expand...
Click to collapse
The folder disappears on the next reboot.
P
paulobrien said:
Superboot should automatically install the Superuser APK in /system/app?
P
Click to expand...
Click to collapse
It did, but didnt show up on first boot. wasnt in the appdrawer, but was in the directory.
either a manual reinstall, or a hot restart fixes it. (Dont know why it didnt show up in the app drawer initially)
Just realised the SU binary is slightly out of date on this superboot, uploading new version now.
P
Updated with latest SuperSU.
P
time to start up on a rom. ;D
... hopefully we'll have a cwm port by the time I've finished v1.0
JSLEnterprises said:
time to start up on a rom. ;D
... hopefully we'll have a cwm port by the time I've finished v1.0
Click to expand...
Click to collapse
I'm working on one today...
JSLEnterprises said:
time to start up on a rom. ;D
... hopefully we'll have a cwm port by the time I've finished v1.0
Click to expand...
Click to collapse
so the 1.73 Rogers RUU is the shipping firmware for the Evita, is that everyone's understanding? The AT&T is also the same, except for branding, correct? I am going to use the boot.img from the Rogers 1.73 release in porting the recovery. Please let me know if you know there is something amiss. thanks.
Steve
sk806 said:
so the 1.73 Rogers RUU is the shipping firmware for the Evita, is that everyone's understanding? The AT&T is also the same, except for branding, correct? I am going to use the boot.img from the Rogers 1.73 release in porting the recovery. Please let me know if you know there is something amiss. thanks.
Steve
Click to expand...
Click to collapse
Yep. And a few missing apk's. Comparing the two. The proprietary carrier apps, plus amazon, boot and down annimations, security certs, gps.conf, minor variance in the build.prop, and the /cid and /mns default.xml's are pretty much the only varying things that I've noticed so far ... Also an xml in /framework/services.jar. If you replace the at&t services.jar with the one from the rogers version, you'll have the selectable 3g/hspa+ or 3g/hspa+/LTE auto options that are not available to at&t users (turn off lte use)
... These are just preliminary comparisons.
If you want to revert to stock boot and down animations just edit /system/customization/mns/default.xml amd change the file names at the bottom. Eg. Rogers_bootanimation.zip to hTC_bootup_one.zip. rogers included their own animations and left the stock ones in resource folder as well. So its pretty easy to debrand & debloat the rogers version.
sk806 said:
so the 1.73 Rogers RUU is the shipping firmware for the Evita, is that everyone's understanding? The AT&T is also the same, except for branding, correct? I am going to use the boot.img from the Rogers 1.73 release in porting the recovery. Please let me know if you know there is something amiss. thanks.
Steve
Click to expand...
Click to collapse
The 1.73 Rogers RUU is indeed the shipping firmware for Rogers phones. The AT&T version has slight differences (no LTE Toggle, tethering), though these shouldn't cause an issue.
~dan
danada said:
The 1.73 Rogers RUU is indeed the shipping firmware for Rogers phones. The AT&T version has slight differences (no LTE Toggle, tethering), though these shouldn't cause an issue.
~dan
Click to expand...
Click to collapse
Thanks. I will check the partitions info on that and use for build.
I am going to start build now. Will let you know how it goes. I should be getting my ATT One X tomorrow, so I will test (unless there are some brave souls out there...).
Steve
danada said:
The 1.73 Rogers RUU is indeed the shipping firmware for Rogers phones. The AT&T version has slight differences (no LTE Toggle, tethering), though these shouldn't cause an issue.
~dan
Click to expand...
Click to collapse
Lte toggle = services.jar (/system/framework) & settings.apk (/system/app)
also, deleting TetheringGuard.apk from the AT&T unit will enable the tethering ability.
JSLEnterprises said:
Yep. And a few missing apk's. Comparing the two. The proprietary carrier apps, plus amazon, boot and down annimations, security certs, gps.conf, minor variance in the build.prop, and the /cid and /mns default.xml's are pretty much the only varying things that I've noticed so far ... Also an xml in /framework/services.jar. If you replace the at&t services.jar with the one from the rogers version, you'll have the selectable 3g/hspa+ or 3g/hspa+/LTE auto options that are not available to at&t users (turn off lte use)
... These are just preliminary comparisons.
If you want to revert to stock boot and down animations just edit /system/customization/mns/default.xml amd change the file names at the bottom. Eg. Rogers_bootanimation.zip to hTC_bootup_one.zip. rogers included their own animations and left the stock ones in resource folder as well. So its pretty easy to debrand & debloat the rogers version.
Click to expand...
Click to collapse
Thanks. This doesn't look like anything that would affect boot.img, good to know. Hope ATT won't mind if I brick my device tomorrow, lol.
You guys are doing a fantastic job for both Rogers and AT&T users! Thanks!
Great job, guys!
I'm at work and can't install the USB drivers to operate my device in the Bootloader/Fastboot but you can be damned sure that I'm eager to go home and flash this!!! Been waiting so impatiently for root and you guys did the trick. Thanks so much