Hello folks,
i got hold of a HTC Flyer which is tmobile branded(-> i cant flash WWE Roms).
When I tried to root it, it was possible to do by flashing superuser.zip and installing a new recovery (via ADB), but I could not get any rom working.
Most of them require S-OFF.
And here is the problem: I can't turn it S-OFF, because I am not able to flash a Gingerbread RUU (which is required to get revolutionary working. it requires hboot version 1.11.003, I have 1.11.011)
When trying to downgrade with the WWE RUU I either get the error 131 or 155 (either wrong image or consumer failure).
So I read a lot and eventually found out, that I need a goldcard to flash any RUU (because I have a tmobile branded device) - it didnt work out either.
After reading more, I found SuperCID (which basically let me install through any RUU i want) - but I did not work - it didnt change the CID.
So my main problem is - how can I get the GB WWE RUU working, in order to S-OFF the device (it is already unlocked via HTCunlock)
I hope you get my point I would be very happy for any tips.
I need help with this too. Please let me know if you are able to find the ROM. Thanks
Downgrade RUU
I too am having trouble will putting on ROMs and downgrading the RUU to GB.
I downloaded from here
The GB RUU - RUU_Flyer_HTC_WWE_2.23.405.3_R_Radio_20.3504.30.089BU_3809.07.04.06_M_release_204108_signed.exe
as my current RUU was - RUU_Flyer_HC_S_HTC_WWE_3.55.405.1_Radio_20.4801.30.0822U_3822.10.08.07_M_release_226690_signed.exe
The followed the instructions on the there here but the RUU exe fails to install. it semi bricks the device and stalls the RUU installation at 16%
Related
Currently I am Hboot 1.5 S-ON and trying to downgrade to HBoot 1.4 S-OFF. When trying to brick my phone on the PG86IMG.zip update it doesn't brick, at least I don't think so. I can enter HBoot, flash a rom, and all that stuff. I believe my problem is because I am presently on RUU 2.17 flashing a 2.17 update and I need to downgrade to RUU 1.13. However, when I try to run RUU 1.13 EXE with a relocked HBoot I get an error message part way through the utility.
ERROR [140]: BOOTLOADER VERSION ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
First of all, do I need to downgrade to RUU 1.13 to brick my phone on the PG86IMG update? And second, if that being so, how do I downgrade?
IXKastling said:
Currently I am Hboot 1.5 S-ON and trying to downgrade to HBoot 1.4 S-OFF. When trying to brick my phone on the PG86IMG.zip update it doesn't brick, at least I don't think so. I can enter HBoot, flash a rom, and all that stuff. I believe my problem is because I am presently on RUU 2.17 flashing a 2.17 update and I need to downgrade to RUU 1.13. However, when I try to run RUU 1.13 EXE with a relocked HBoot I get an error message part way through the utility.
ERROR [140]: BOOTLOADER VERSION ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
First of all, do I need to downgrade to RUU 1.13 to brick my phone on the PG86IMG update? And second, if that being so, how do I downgrade?
Click to expand...
Click to collapse
You need to be relocked/have 2.17 firmware on your phone.
Once you press (UP) to update does your device turn off right away?
I am relocked and have 2.17 firmware. When I press (UP) for the update it updates with a series of purple and black updating sequences. But I am trying to brick it and I can't seem to do so cause I am pulling out the power cord with no battery but I see no dim red light on the top of the phone. Like I said, everything boots as normal and I even can run the 2.17 RUU EXE and boot up that. I saw that the "HBoot downgrade tutorial" said...
If you're already S-OFF, but on 1.50, you can do one of two things... I have attached the PG86IMG.zip with the 1.40 bootloader on it, download it copy to sd card and flash via bootloader.
The other option is to simply re-run 1.13 RUU, this will downgrade it as well, but this will also erase all data in the process.
Now I assume that means if I am 2.17 and S-ON, which I am, I need to downgrade to 1.13 to have the 2.17 PG86IMG.zip update properly so I can pull the plug and brick it. Do I need to do that or am I just needing to repeat the bricking process until it works?
IXKastling said:
Currently I am Hboot 1.5 S-ON and trying to downgrade to HBoot 1.4 S-OFF. When trying to brick my phone on the PG86IMG.zip update it doesn't brick, at least I don't think so. I can enter HBoot, flash a rom, and all that stuff. I believe my problem is because I am presently on RUU 2.17 flashing a 2.17 update and I need to downgrade to RUU 1.13. However, when I try to run RUU 1.13 EXE with a relocked HBoot I get an error message part way through the utility.
ERROR [140]: BOOTLOADER VERSION ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
First of all, do I need to downgrade to RUU 1.13 to brick my phone on the PG86IMG update? And second, if that being so, how do I downgrade?
Click to expand...
Click to collapse
I downgraded yesterday. This is what I did. I downloaded this hbootdowngrade217.zip along with another download zip file that contained the 1.13 ruu and I downloaded a 2.08.zip file as well. I relocked my phone and ran the 2.17 ruu thats in that hbootdowngrade217.zip file. Then I rename the 2.08.zip file to PG86IMG.zip onto the root on my sd card. Booted into bootloader let it read the file. Once it read n I had to update. I plugged in the charger from the laptop to the phone then took the battery out. let it sit for a min then hit up on sp it can begin the update n right after it said UNZIPPING n said Updating I counted to 5 n took the charger out on 5. If u did this before it went to the next step you have bricked your device correctly. You can check this by going into the control panel>view devices<manage devices n u put the battery back in hold down the down volume button then plug your phone back up n u will see something saying: Qualcomm MMC Storage but it should change to QSUSB_ (something) that means have bricked it correctly. If u didnt then its gone read unknown device. Just continue trying to brick it. Hope this works for you.
I just bought this flyer 3G version It was working with 2.3.4 when i bought it.
I've searched the entire XDA forum ,modaco and loads of the other sites. Been attempting this for 4 hours straight x 3nights in a row.
I've managed to get Bootloader unlock via HTCdev but still on S-ON because my hboot is 1.11.011 Flashed the Paul obriens modified HC boot 11.11.0011 image. I got revolution CWM and i can get into it but now suddenly fail to adb into it.
FLYER PVT SHI{P
S-ON RL
HBOOT - 1.11.0011
MICROP=0950
RADIO-3822.10.08.07_M
eMMC-boot Oct 25 2011,16:55:07
I think my flyer is in limbo.
CID=044 which is the HTC Asia WWE one.
I tried: Installing some custom ROM's as soon as i achieved bootloader unlocked. Tried the latest LOeeDroid etc. BUT they all fail at the HTC boot screen. Even after waiting for 10 mins. Yes I did extract the boot.img and flashed via fastboot due to s-on but still stuck at HTC boot logo.
Ran the RUU's directly from fastboot mode (i just double clicked on the exe from my PC) -HTC Asia WWE . but they all fail on installtion/ signature. RUU_Flyer_hTC_Asia_WWE_1.48.707.4_Radio_20.3501.30 .089BU_3809.05.04.10_M_release_193927_signed RUU_Flyer_hTC_Asia_WWE_2.27.707.1_Radio_20.3504.30 .089BU_3809.07.04.06_M_release_204905_signed RUU_Flyer_hTC_Asia_WWE_2.27.707.2_Radio_20.3504.30 .089BU_3809.07.04.06_M_release_219276_signed
i tried the rom.zip extraction and renamed it to PG411MG.zip with the hope of the bootloader detecting and running it - it tried to install but failed -signature. I created a goldcard but not used this method yet as i had to format it and now i cant even connect to the PC -its as if it cant detect the device. I will try a ROM that is similar to my radio . But i cant connect to the Flyer -(adb- device not found)
Please help - ill gladly donate to a working solution. I dont know what else to do. I just want to get android working again passing the horrid HTC boot logo. i dont mind stock etc just need my flyer to work.
Been ROMing since HD2
UPDATE: SOLVED
none of the stock RUU I tried installing was successful because I had Unlocked the Bootloader.
All I needed to do was' fastboot oem lock' and it relocked. RUU will only install on locked bootloaders.
While still in fastboot I ran the RUU from my PC and it worked. Installing while tears of joy rolled down my tired eyes.
So I'm now on an older hboot and achieved S-off,rooted and made my flyer into a phone + Bluetooth.
Flash the stock rom
Get a guide on xda about it... Urs any flashing software and u will b alr9
Click THANKS button if I helped, or u liked my post.
Will be honored.
I updated my phone using the latest 4.03.605.2 and the latest firmware.zip (am S-ON). Now I got my replacement phone, and got it all set up and working fine. Now I can't seem to get the original phone (has a bad touch screen) to restore... every time I try to run the RUU (PH98IMP.zip, 4.03.605.2), it says bad mainver, which I found a mainvir patch and flashed it.
Now it says the HBOOT is newer and won't flash. My HBOOT is on 2.28. The 4.03.605.2 apparently is 2.27, and the latest firmware zip I flashed updated it.
I have both zips still... obviously firmware.zip doesn't include the whole OS... is there a 4.03.605.2 ruu with the updated 2.28 and 2.23 radios already in it?
Help?
Thanks!
Apparently the firmware.zip file was from the global .14 update. Am I stuck until an RUU is released?
Phew... took me a couple hours but got a rom running again, tracked down a download of the s-off windows files, went s-off, ruu'ed, then s-on.
Stock-Rooted 4.05.605.14 rom, loadable from recovery (post #3): http://forum.xda-developers.com/showthread.php?t=2288479
Windows S-Off files (post 361): http://forum.xda-developers.com/showthread.php?p=40950251#post40950251
Followed this guide to reset my locked flag (since I unlocked after going S-Off /facepalm): http://androidforums.com/rezound-all-things-root/659453-how-reset-your-lock-status-flag.html
Then followed this guide to go back to S-ON (after running the RUU): http://androidforums.com/rezound-al...-off-guide-info-return-stock.html#post4394129
Result: Fully stock, locked, and S-ON, to send back to VZW
Hey all,
so I've been running ARHD on firmware 127.538.8 for awhile. I saw the RUU come out for 4.3 on Tmob, so obviously I was all like, **** yeah! So I flashed a stock ROM (based on 127.538.11) and then tried to run the RUU. Unlocked, S-OFF. For some reason, the RUU flashed Hboot (I'm currently stuck at 1.55.00) and then decided to throw an error 155 at me. So I tried relocking the bootloader, with a command I found browsing the forums that sets the status to Locked. Flashing the RUU here didn't work either. Re-unlocked the bootloader (I have no user data at all... it's sad). I realized, okay, I'm Unlocked and have a custom recovery installed (TWRP). Even if I relock, the RUU doesn't flash. My idea right now is to flash the 127.538.11 RUU to get Hboot 1.44, as well as a working non-hacked firmware. I'm not sure if that RUU will work, though I'm hoping it does. If it does, then I can OTA update without a problem.
Do any of you have any ideas as to how to do this? I can RUU to 127.538.11, then downgrade to x.8 and use revone to lock my bootloader and attempt an OTA. I'm not sure what to do here... I can also reflash ARHD 30 and stick with that for awhile. I can do basically anything recommended, as I have S-OFF and TWRP.
Thanks!
I don't mind being stuck on stock, however I do want to be able to warranty my phone in the future -- will having hboot 1.55.00 with 127.538.8 firmware be a problem? Can I downgrade my hboot since I'm S-Off? Any help here would be absolutely wonderful...
Hi,
I have HTC One International Version (O2 Germany) I have S-Off it and rooted it, Now I want to revert it and want OTA to work. I am unable to get any OTA notification as it always says there is no update for your phone even though its on 4.3. Due to S-Off it always says that you are having a test device. Resetting it didn't help. I don't have RUU for CID O2___102. Now should I flash a boot file on it to gain S-On, if yes then which one. The Hboot is 2.46.00. Will after getting S-On the OTA will be available to get installed?
PS: The bootloader is Relocked. I guess the right Stock Recovery is installed. Although I think the kernel is messed up as it is showing 3.4.10 on v4.3 (image attached)
This is Bootloader info:
-OS-1.23.1540.1
radio -4T.21.3218.04
CID O2___102
-T6UL PVT SHIP S-OFF RH
-hboot-2.46.0000
Thanks
-------
Edit:
Although I have been searching for it for many days, the only option I think I am coming across is getting boot.img from virtuous rom and update my boot which will also update the hboot. Although I am not sure if this is possible solution. Just want an opinion before updating the hboot as it wont be downgraded later.
Edit 2: Installing boot for 1.54 (stock and also from Stock Nandroid) or from virtuous rom with S-Off *Unlocked* is not making any difference or update to the boot. Its still the same.
i have t6ul cid htc_001 uk international
it's soff
it took the ota no problems. and its still soff
soff will not stop you from getting update ota.
so stop trying to gain son when so many people have trouble getting soff! lol
japodude said:
i have t6ul cid htc_001 uk international
it's soff
it took the ota no problems. and its still soff
soff will not stop you from getting update ota.
so stop trying to gain son when so many people have trouble getting soff! lol
Click to expand...
Click to collapse
S On is not a problem for me the now reverting to stoack while having OTA is a main pain. I am not getting OTA while having soff and all the info provided above.
I started getting OTA 4.4.2 when I made Super CID and installed RUU_T6_UL_JB43_SENSE55_BrightstarUS_WWE_1.23.1540.1_Radio_4T.21.3218.04_10.15.1718.01_release_337609_signed_2.exe
The problem was when the OTA gets downloaded and then it varify the system update conditions before installing, it give back error of some manipulated system etc.
why did you super cid? what cid is it now. can you put back to original cid?
device has to be completely stock to run ota.
unrooted. (only way i could get unrooted was to format system then restore my 4.3 backup, and flash stock recovery and lockbootloader.
only then would ota work.
restore your original cid, get a backup from your region and restore.
if your cid was o2_102 then can you change it to htc_102. then it may run ota fine.
i have a cwm backup of my t6ul international from vodafone uk if you want it to try.
instal latest cwm recovery. think its 6.0.4.7
make a backup of you current rom first. then download my backup here and uncompress to external sdcard https://www.dropbox.com/s/pj9mds5lalg84lu/clockworkmodbackup.rar
format your system, data, and restore my cwm backup.
boot device once and run setup wizard.
flash stock recovery and lock bootloader by scotty123's method (NOT RE-LOCK, ota will not work)
now ota should work.
this has helped many others
I got OTA. Restoring the cwm backup as I already have this file with me through cwm recovery then installed stcok recovery, relocked and it worked while having Super CID. the only thing is even after update and hboot update it remained S Off. The S On I want to have because IF I need to return it for warranty issues, how I will be able to get S On again.
PS: I had to change CID to make it Super CID to get the cwm backup installed and OTA working. Which I reverted back after installation.
aaho said:
I got OTA. Restoring the cwm backup as I already have this file with me through cwm recovery then installed stcok recovery, relocked and it worked while having Super CID. the only thing is even after update and hboot update it remained S Off. The S On I want to have because IF I need to return it for warranty issues, how I will be able to get S On again.
PS: I had to change CID to make it Super CID to get the cwm backup installed and OTA working. Which I reverted back after installation.
Click to expand...
Click to collapse
i have hboot 2.49 t6ul modded to show son even though it's soff. also removes the red text