Related
[UPDATE] Fixed using method 2 in the link in post #4. Thanks a lot!!
Hi everyone, new to the forum and in need of some help please
I have a new Desire from T-Mobile UK. Branded and I assume locked, not rooted.
I attempted to debrand my phone by doing the following.
1. I already had Android SDK and HTC Sync.
2. I made a GoldCard following the unlockr instructions "how-to-create-a-goldcard" (not allowed to post link as am new forum user).
3. I ran an RRU from the pinned ROMS topic in this forum, which was RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4.06.00.02_2_release_126984_signed.exe
The flash completed with no errors.
Afterwards, the phone appears to boot up but the screen remains completely black at all times. I have tried everything I can think of, and have seen absolutely nothing on the screen at all since flashing. Pure black not even backlight.
What I have observed is:
1. On power-up, the vibration and welcome sound.
2. The hardware buttons illuminate. They time out and go off, and they illuminate again when pressed.
3. On inserting a freshly formatted SD card and turning on, waiting ages, turning off (remove battery), removing card, then viewing in a card reader, Android has added some folders to the card (.footprints, LOST.DIR, rssreader) so obviously it is booting up to some degree.
4. On attempting to flash another ROM, the tool reports the "From image version" to be 1.21.405.2 which is the one I flashed earlier, not the phone's original version.
5. Phone no longer shows up in "adb devices" when connected, although this may be simply because USB debugging isn't enabled, or because the phone will be at its start-up introduction screens.
6. There is network activity after a while, indicated by the interference on my PC's speakers.
What I have tried to do to fix:
1. Numerous reboots removing battery, SD, SIM etc.
2. Flashed the WWE 1.21 ROM again, which succeeded, but didn't fix the problem.
3. Attempted to flash the WWE 1.15 ROM RUU_Bravo_HTC_WWE_1.15.405.4_Radio_32.30.00.28U_4.05.00.11_release_122704.exe which failed with "ERROR [140]: BOOTLOADER VERSION ERROR. The ROM Update Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again."
4. Attempted to flash the T-Mobile 1.5 ROM RUU_Bravo_TMO_UK_1.15.110.11_Radio_32.30.00.28U_4.05.00.11_release_122755.exe which failed with the same error.
5. Flashed the T-mobile 1.21 ROM, which succeeded, but didn't fix the problem, and has made it slightly worse in that I don't get the welcome sound at power-on any more. I still get the vibration, the lights, the network activity, and the black screen.
6. Tried with another SD card, no difference.
Before I started debranding at all, I took a photo of the software versions screen as supplied by t-mobile, which showed as follows.
Firmware version: 2.1-update1
Baseband version: 32.41.00.32U_4.08.00.09
Kernel version
2.6.29-3cb3dfbf
htc-kernel{at}and18-2 #1
Build number 1.15.110.11 CL155070 release-keys
Software number: 1.15.110.11
Browser version: WebKit 3.1
(replace {at} with the email at symbol, new forum members aren't allowed to post these)
So in summary, I probably have the WWE 1.21 ROM working on my phone, but the screen doesn't work so I can't see it, and re-flashing doesn't work so I can't try a different ROM.
I'm a noob to debranding but am a programmer and Android app developer so feel free to get a little bit technical
Any help you can give is greatly appreciated! Hopefully I won't have to explain this to the T-Mobile support people!
Thanks!
Hi. Sorry to hear you having trouble, I'm not too sure. But sounds to me like its a display issue? You may have a Desire with the new cheaper display, not a amoled.screen? Think I remember reading in the forums blank screens and issues with roms. (please check other treads)
The good news is I think its recoverable. Sorry. I can't be of mote help.
Sent from my HTC Desire using XDA App
Thanks for the reply,
I had a better search around and found showthread.php?t=747393 which describes apparently the same problem, although I haven't messed with bootloaders. It was fixed by installing the OTA update blind by pressing buttons in the right order.
It is indeed possible I have a different screen type, or perhaps a different model of AMOLED, does anyone know how to tell the difference? I do notice the screen is more reflective than my G1, which I think is associated with AMOLEDs, but that might just be down to 2 yrs of wear and tear.
Anyway, I will try it now let you know how I get on!
Thanks!
As above you have a Desire with an SLCD screen.
You will have a HBOOT of 0.83 or 0.92 - You need a rooting and/or debranding guide for those HBOOTs. The current guides only work for HBOOT 0.80 and lower.
Here is your fix for your current problem: http://forum.xda-developers.com/showthread.php?t=748498&highlight=brick+fix+SLCD
I couldn't get the pressing buttons blindly method to work, but method 2 from dickenz's link worked a treat.
It gave me WWE Android 2.1, and I immediately got the OTA update to Froyo, WOOHOO!
Can I suggest we create a section in the pinned ROM topic listing RRUs and OTAs compatible with the new screens? That'll make it more obvious to new visitors.
Thanks for your help both of you, I'll stay around the forums!
Hi all, would like to know if, after installing a custom ROM, if i use a RUU will the recovery image be restored to default?
Thanks in advance!
Yes it Will
Yay! thank you! so just using the RUUs i will totally reset my desire, so HTC won't be able to tell if it's been rooted before?
Don't know whether they can't tell, whether they look if they've no need to I don't know...so long as it's on a stock ROM I don't think they'd check
lambdafreak said:
Hi all, would like to know if, after installing a custom ROM, if i use a RUU will the recovery image be restored to default?
Thanks in advance!
Click to expand...
Click to collapse
What is a RUU and how can I do it, as I'm having the same problem.
I rooted to allow Titanium Backup to have root after using unrevoked but wasn’t aware that meant I also had a custom rom installed now.
I’ve been told I need to RUU as well.
RUU = ROM Upgrade Utility
It's the official way of flashing a ROM. Each phone has a software version running on it when you first get it and you should make a note of the one on yours before doing anything root-related for the very reason that if something goes wrong you can revert back to stock. Not all versions are available, e.g. there are no Orange RUUs about, but the ones that are can be found here:
http://shipped-roms.com/index.php?category=android&model=Bravo
If you didn't happen to make a note of yours then it's hard to say what it came with. If you've only rooted and NOT flashed a new ROM yet then if you go to Settings>About phone>Software information and post the software version we might be able to help
Thanks for all the information it helps fill in some blanks.
I dont think I have put a different rom on it, I only rooted using revoked- does that mean it has a different rom now?
and my settings show
Android 2.2
Baseband version 32.46.00.32U_5.10.05.17_2
Kernel version 2.6.32.15-gd96f2c0 [email protected] #1
Build number 2.12.110.2 CL232610 release-keys
Software number 2.12.110.2
on a side note the link you posted - what do the numbers correspond to, my Kernel or build
Right you're on a T-Mobile FroYo ROM but the issue is there isn't that versions RUU available...how long have you had your Desire?
Damm.
I got mine in April this year, why do you ask.
Can I not use RUU_Bravo_Froyo_TMO_AT_2.12.112.1_Radio_32.46.00.32U_5.10.05.17_2_release_143754_signed.exe?
You CAN use that but it's the Austrian one...the reason I ask is to find out the screen type, you should be on an AMOLED screen so you can flash the older 1.21.110.4 RUU if you need to - you'll need a gold card to do it, though, I believe
http://shipped-roms.com/download.ph...00.28U_4.06.00.02_2_release_127570_signed.exe
If I do flash the older 1.21.110.4 version, are there any drawbacks, or will I just be able to update through OTA updates that will then be available to me through T-mobile to get me back to normal?
Also is there a best way to do this RUU as I have seen a few guides, can you recommend any to follow.
The way I'd do it is:
1. Download that RUU
2. Have gold card in your phone and HTC Sync installed on your PC
3. Connect phone to PC and select 'HTC Sync' from the options on the phone
4. Once HTC Sync on the PC shows connected, run the RUU
5. All being correct it'll flash the ROM
6. Assuming it's worked, you should get the OTA updates again as you did before
Replying on here and androidforums is getting confusing!!!
Thanks for all the help and I hope those instructions were meant for me and not some one else
Maybe you have to downgrade your hboot to 0.75.
Sent from my HTC Desire using newest version of swype and the XDA App
digo21 said:
Thanks for all the help and I hope those instructions were meant for me and not some one else
Click to expand...
Click to collapse
Yes they're for you but there's someone on androidforums with EXACTLY the same issue - you sure you're not the same person??
Nope thats not me
I followed all the procedures. But the RUU gave me an error after a few minutes saying 'Error 140 Bootloader version error'.
What does that mean and how can I fix it.
Which RUU are you trying to use? And which HBOOT are you on now?
Im trying to use the one you recommended above RUU_Bravo_TMO_UK_1.21.110.4_Radio_32.36.00.28U_4.06.00.02_2_release_127570_signed.exe
Bootloader version I found out by holding the back key and power button to swithc on, it says HBOOT - 0.93.0001
Im going to be sending my Desire to HTC after experiencing the reboot issue , at the moment i have a rooted phone running a custom rom and want to go back to an official UK T-Mobile (non rooted) rom
on the official ROMS page there are two:
RUU_Bravo_TMO_UK_1.15.110.11_Radio_32.30.00.28U_4. 05.00.11_release_122755.exe
RUU_Bravo_TMO_UK_1.21.110.4_Radio_32.36.00.28U_4.0 6.00.02_2_release_127570_signed.exe
does anyone know what the differences are and which one i should go back to?
Cheers
What software version are you on now?
What HBOOT are you on?
when i power on and volume down i get
BRAVO PVT1 SHIP S-ON
HBOOT-0-80-0000
MICROP-031d
TOUCH PANEL SYNT0101
RADIO-5.09.05.30_2
not sure what you mean by software version
Im running the latest OpenDesire ROM at the moment : http://forum.xda-developers.com/showthread.php?t=768624
Get 1.21.110.4, it'll flash fine
k cool ,can you tell me what the differences are?
i also noticed one has signed at the end, is that significant?
1.15 - old
1.21 - new
Pretty simple really!! The higher the numbers, the newer the build
As for signed, probably just means it's actually a released ROM - I've never took any notice before. They're both official T-Mobile RUUs so it shouldn't matter
couple more questions
does anyone know if the newest TMobile ROM is Froyo
and
Do i need a gold card to run these RUU roms
1. No it's not, it would be 2.x.xxx.x if it was. The T-Mobile one isn't available yet BUT you can then flash the OTA update to get to FroYo once you've used 1.21.110.4
2. If you phone came with a T-Mobile ROM on it then no, a gold card is only needed to flash a ROM which is a different version to the original
I flashed one of the tmobile roms off the rom page and it was no good with my slcd screen.
Just something to consider if you have an slcd screen.
He's not on an SLCD screen as he's on HBOOT 0.80 so it'll be AMOLED
thanks for your help, appreciated
yeah i have an amoled screen (i checked the sticker on the side of the box )
on the Official RUU page it has these two OTA updates
OTA_Bravo_TMO_UK_1.15.110.11-1.15.110.10_releasez3xlhzglzlds8gg2.zip
OTA_Bravo_TMO_UK_1.21.110.4-1.15.110.11_release0grz58nlwns0d5mw.zip
would the 2nd one include froyo? the reason for asking is i really need the Portable Hotspot feature in a couple of weeks and unrooted 2.1 doesnt have this
Neither are the FroYo OTA, you need this one:
http://fotadl.htc.com/2.12.110.2-1.21.110.4_release3uop1mw9unpc376h.zip
First, flash the 1.21.110.4 RUU, then download that file and do the following:
1. Rename it update.zip (not update.zip.zip)
2. Copy it to your SD card
3. Turn the phone on holding volume down to get into HBOOT and then select recovery
4. At the red !, hold volume up and press power
5. On the menu, select 'apply sd:update.zip'
6. Follow the instructions
superb mate, thanks!
just tried to run teh OTA_Bravo_TMO_UK_1.21.110.4-1.15.110.11_release0grz58nlwns0d5mw.zip
and went through all the prompts and then it told me
ERROR[131]: CUSTOMER ID ERROR
now my phone is tmobile but im 90% sure when i got it (when the desire came out, bought it from mobilephonesdirect) it was customised with Virgin Mobile icons, would that make a difference?
Yes, chance are you're on generic FW (x.xx.405.x)...having said that, is your sd card a gold card?
i still have my goldcard
i just checked back on an old thread and a few people also got tmobile desires with Virgin media icons on the homescreen
Either way, if you're now on 1.21.110.4 then that OTA file should have no issues. Obviously use your gold card as if you're not chances are you weren't on a T-Mobile ROM originally - in which case get the latest FroYo RUU by clicking on my Signature and use that instead!!
ok
i didnt manage to get as far as flashing 1.21.110.4 as i got there ERROR 131.
so , i need to use my goldcard to flash 2.29.405.2 WWE (FRF91). and if so i take it all i need to do is flash the rom with the gold card in instead of my normal sd card.
if i install 2.29.405.2 will that be ok to send back to HTC (reboot problem)
No
If you tried the T-Mobile RUU without your gold card and got that error then chances are you're on a generic Desire. So download the 2.29.405.2 from my sig and try again without your gold card. If it works then you have an unbranded Desire
ey mate
cheers for all yor help
i managed to flash the rom in your sig without a goldcard and all is fine!
i can now send them phone to HTC to be repaired! thanks again
Hello:
I have a rooted InC2 , Android 2.3.4
Hboot 6.13.1002 (not sure how I went from 0.98 to this version after S-OFF)
I need to return the phone because the earpiece does not work
Need back to stock (Android 2.3.4 Hboot 0.98)
I have the zip file for v2.3.4 but it is bypassing flashing the Bootloader.
My question is where can I get the Hboot 0.98 for INC2 and remove revolutionary?
I found a procedure for HTC Desire S where someone created a an EngBoot.img loader that you flash by using
" fastboot flash hboot engHBOOToverARX.img "and this version allows you to upgrade the next version
using the same command for the Hboot you want.
Then, I assume you can flash stock with the zip file
Has anyone done this ?
Is the hboot for HTC Desire the same as INC2? Can I use these files?
I know there some dd commands that can be used (I understand the risk) but I don't have Hboot 0.98 for INC2 , if the procedure above does not work for INC2, where can I find Hboot 0.98 and the dd procedure to flash it?
Can some one help me ?
thank you very much
vlsi99 said:
Hello:
I have a rooted InC2 , Android 2.3.4
Hboot 6.13.1002 (not sure how I went from 0.98 to this version after S-OFF)
I need to return the phone because the earpiece does not work
Need back to stock (Android 2.3.4 Hboot 0.98)
I have the zip file for v2.3.4 but it is bypassing flashing the Bootloader.
My question is where can I get the Hboot 0.98 for INC2 and remove revolutionary?
I found a procedure for HTC Desire S where someone created a an EngBoot.img loader that you flash by using
" fastboot flash hboot engHBOOToverARX.img "and this version allows you to upgrade the next version
using the same command for the Hboot you want.
Then, I assume you can flash stock with the zip file
Has anyone done this ?
Is the hboot for HTC Desire the same as INC2? Can I use these files?
I know there some dd commands that can be used (I understand the risk) but I don't have Hboot 0.98 for INC2 , if the procedure above does not work for INC2, where can I find Hboot 0.98 and the dd procedure to flash it?
Can some one help me ?
thank you very much
Click to expand...
Click to collapse
My educated guess is that you're flashing one of the newer custom DI2 Rom here (ported from 2.3.6 or 2.3.7 or based on the Chinese Rom) and it changed your HB too. As I recall when this sub-forum was very active then, WiFi and 3G data also become unresponsive or "buggy" at times. In any event, you should read this link carefully & follow the steps -
http://forum.xda-developers.com/showthread.php?t=1298990
The reference RUU file, if you cannot find it on VZW's linked website as it is a discontinued model, here is a working link that you can follow, housed on one of my Dropbox account, it is the original untouched one, clean & all. - skip to post #7 - http://forum.xda-developers.com/showthread.php?t=2427581
I do not recall whether it specifically restore the HB to the earlier one, but everything else will be OEM/stock fresh, ready to activate - as if it's just unboxed. Besides, techs will most likely not be checking yours for HB verison as long as it boot up normally and appeared working, assuming that you are returning it for repairs/exchange and within the warranty coverage period.
Good luck !
Letitride said:
My educated guess is that you're flashing one of the newer custom DI2 Rom here (ported from 2.3.6 or 2.3.7 or based on the Chinese Rom) and it changed your HB too. As I recall when this sub-forum was very active then, WiFi and 3G data also become unresponsive or "buggy" at times. In any event, you should read this link carefully & follow the steps -
http://forum.xda-developers.com/showthread.php?t=1298990
The reference RUU file, if you cannot find it on VZW's linked website as it is a discontinued model, here is a working link that you can follow, housed on one of my Dropbox account, it is the original untouched one, clean & all. - skip to post #7 - http://forum.xda-developers.com/showthread.php?t=2427581
I do not recall whether it specifically restore the HB to the earlier one, but everything else will be OEM/stock fresh, ready to activate - as if it's just unboxed. Besides, techs will most likely not be checking yours for HB verison as long as it boot up normally and appeared working, assuming that you are returning it for repairs/exchange and within the warranty coverage period.
Good luck !
Click to expand...
Click to collapse
I want to be sure I understand you instructions, I will perform these commands below . Should I flash the zip indicated or are you saying the last step "fastboot flash zip " I should replace the zip file for another from one of your links??
In post #7 there are 2 links :
To this file which is an executable
RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_5.10.605.9_Radio_1.09.01.1111_NV_VZW1.92_release_225831_signed
Will this executable generate a zip file?
the other link :
is a zip file All_Stock_PG32IMG.zip Or should I use this zip
adb shell rm -r /data/local/tmp/*
adb push zergRush /data/local/tmp/zergRush
adb push misc_version /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/zergRush
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/zergRush
adb shell /data/local/tmp/sh -c '/data/local/tmp/misc_version -s 2.18.605.3'
adb reboot bootloader
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.09.01.0622_NV_VZW1.92_release_199487_signed.zip
fastboot reboot
Will this reflash Hboot to 0.98
and basically remove S-OFF correct?
thank you
vlsi99 said:
I want to be sure I understand you instructions, I will perform these commands below . Should I flash the zip indicated or are you saying the last step "fastboot flash zip " I should replace the zip file for another from one of your links??
In post #7 there are 2 links :
To this file which is an executable
RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_5.10.605.9_Radio_1.09.01.1111_NV_VZW1.92_release_225831_signed
Will this executable generate a zip file?
the other link :
is a zip file All_Stock_PG32IMG.zip Or should I use this zip
...
Click to expand...
Click to collapse
Ok, the RUU...signed file that is in one of my Dropbox account now (next 72 hours or so) is the *.exe file from VZW, it will NOT generate a Zip file and it does NOT run inside ADB. Just download it to your preferred drive/subfolder. Connect your DI2 and assuming the HTC drivers were installed and it recognized yours (as it should) - click on the RUU file name and it should launch, with VZW's disclaimers and warnings, etc. - read & click thru it, and proceed - AT YOUR OWN RISK, of course. It will take 5 to 10 minutes to flash, when it's done - follow the prompts & reboot the phone. EVERYTHING, everything will be wiped clean & sysem reset, UNrooted - back in stock form as shipped.
If there are errors for whatever reasons, it might failed and stop proceeding with the flashing.
THE PG32IMG.zip file from Condemned will NOT change/restore your bootloader to HB98 or HB97, it will only restore the ROM portion to factory stock conditions and is for rooted devices with working CWM/TWRP recoveries installed - since it is in ZIP file format.
So, backup & save your settings with TB and CWM Backup first, save them to a safe location (i.e. USB or standalone external drive, etc.) before proceeding with the more basic PG*.zip file if you just wanted to get a feel for restoring it to stock looking rom. Running the RUU file in *.exe format will reset and wipe everything completely - you will lose ROOT and custom recovery will be gone too, and you should also see HB9x restored as part of the process - I just don't recall, but it will otherwise be 99%+ stock in general. The outsourced tech geeks at VZW's service counter will most likely not be looking to see if you've "messed" with the bootloader to disallow your repair claims or warranty coverage.
Good luck & please post your outcome/results - and/or if you run into other problems in the process.
Letitride said:
Ok, the RUU...signed file that is in one of my Dropbox account now (next 72 hours or so) is the *.exe file from VZW, it will NOT generate a Zip file and it does NOT run inside ADB. Just download it to your preferred drive/subfolder. Connect your DI2 and assuming the HTC drivers were installed and it recognized yours (as it should) - click on the RUU file name and it should launch, with VZW's disclaimers and warnings, etc. - read & click thru it, and proceed - AT YOUR OWN RISK, of course. It will take 5 to 10 minutes to flash, when it's done - follow the prompts & reboot the phone. EVERYTHING, everything will be wiped clean & sysem reset, UNrooted - back in stock form as shipped.
If there are errors for whatever reasons, it might failed and stop proceeding with the flashing.
THE PG32IMG.zip file from Condemned will NOT change/restore your bootloader to HB98 or HB97, it will only restore the ROM portion to factory stock conditions and is for rooted devices with working CWM/TWRP recoveries installed - since it is in ZIP file format.
So, backup & save your settings with TB and CWM Backup first, save them to a safe location (i.e. USB or standalone external drive, etc.) before proceeding with the more basic PG*.zip file if you just wanted to get a feel for restoring it to stock looking rom. Running the RUU file in *.exe format will reset and wipe everything completely - you will lose ROOT and custom recovery will be gone too, and you should also see HB9x restored as part of the process - I just don't recall, but it will otherwise be 99%+ stock in general. The outsourced tech geeks at VZW's service counter will most likely not be looking to see if you've "messed" with the bootloader to disallow your repair claims or warranty coverage.
Good luck & please post your outcome/results - and/or if you run into other problems in the process.
Click to expand...
Click to collapse
Sorry, I got confused because this link http://forum.xda-developers.com/show....php?t=1298990 has the instructions I posted and I thought I needed to execute. However, it seems all I have to do is run the executable to be stock.
I am just curious what are those commands for in the above link?
thank you very much
vlsi99 said:
Sorry, I got confused because this link http://forum.xda-developers.com/show....php?t=1298990 has the instructions I posted and I thought I needed to execute. However, it seems all I have to do is run the executable to be stock.
I am just curious what are those commands for in the above link?
thank you very much
Click to expand...
Click to collapse
I may have misunderstood you.. running the executable just re-flashed ROM still S-OFF and @ hboot 6.13.1002
I though I saw the message flashing Hboot and it completed successfully. Did I miss a step?
thanks
vlsi99 said:
I may have misunderstood you.. running the executable just re-flashed ROM still S-OFF and @ hboot 6.13.1002
I though I saw the message flashing Hboot and it completed successfully. Did I miss a step?
Click to expand...
Click to collapse
I see, okay - so you have the stock ROM on the device but it's still S-OFF with HB 6.13.1002 .... I went back to the older posts as it's been a while.
Well, if you feel you must get it to stock conditions, then I would say you need to run the ADB scripts as some users did have problems and it took more than one attempt to get it to work - http://forum.xda-developers.com/showthread.php?t=1298990&page=17
Check that you have only HTC drivers installed and other USB device drivers uninstalled from the PC (running Vista or Win7, correct - or XP ??)
reboot the computer and connect DI2 with the micro-USB cable, and make sure that all the files needed are in the same sub-folder, including the RUU file as you've downloaded. Turn off your anti-virus & firewall temporary - restore them/ON afterward.
Log into command prompt as administrator on the PC, run the adb scripts - and as it continued, you should see the progress and/or error messages across the screen.
Let's try that - also look at, starting from post #161 from the linked post above.
Please advise as to your results afterward or whether you are still S-OFF with the same HB. Thanks.
fortified wardaid
Letitride said:
I see, okay - so you have the stock ROM on the device but it's still S-OFF with HB 6.13.1002 .... I went back to the older posts as it's been a while.
Well, if you feel you must get it to stock conditions, then I would say you need to run the ADB scripts as some users did have problems and it took more than one attempt to get it to work - http://forum.xda-developers.com/showthread.php?t=1298990&page=17
Check that you have only HTC drivers installed and other USB device drivers uninstalled from the PC (running Vista or Win7, correct - or XP ??)
reboot the computer and connect DI2 with the micro-USB cable, and make sure that all the files needed are in the same sub-folder, including the RUU file as you've downloaded. Turn off your anti-virus & firewall temporary - restore them/ON afterward.
Log into command prompt as administrator on the PC, run the adb scripts - and as it continued, you should see the progress and/or error messages across the screen.
Let's try that - also look at, starting from post #161 from the linked post above.
Please advise as to your results afterward or whether you are still S-OFF with the same HB. Thanks.
Click to expand...
Click to collapse
Android 2.3.3 S-OFF same boot 6.13.1002 :crying:
One concern, if I do something else where S-OFF is removed and it does not leave me at Stock 2.3.4 , will still be able to use the executable to get back to Android 2.3.4 (with S-ON this time)?
Another comment that may or may not be related , through all these flashing sequences that I have tried , if a new radio is re-flashed, I get into the loop reboot mode and I need to reflash version
1.09.01.0312_vivow_Radio_PG32IMG.zip to stop it.
Any other ideas to remove S-off?
thank you
vlsi99 said:
Android 2.3.3 S-OFF same boot 6.13.1002 :crying:
One concern, if I do something else where S-OFF is removed and it does not leave me at Stock 2.3.4 , will still be able to use the executable to get back to Android 2.3.4 (with S-ON this time)?
Another comment that may or may not be related , through all these flashing sequences that I have tried , if a new radio is re-flashed, I get into the loop reboot mode and I need to reflash version
1.09.01.0312_vivow_Radio_PG32IMG.zip to stop it.
Any other ideas to remove S-off? ...
Click to expand...
Click to collapse
See this hosted link to a full collection of RUU / roms for the DI2, including those outside US and overseas - please only consider using the last 7 at the bottom as you scroll down, the final 3 might be the older ones (2.3.3 ??) - I've never used this link's files to reflash our DI2, but the download links are working and MD5's provided to verify its integrity upon d/l completion. Use at your own risks & discretion. http://www.androidruu.com/index.php?developer=Vivo_VivoW
The x.0312 radio isn't the newest one, if I am not mistaken - the x.0320 radio is the newest official VZW release for the DI2 & compatible with Gingerbread roms. The older ones x.0622 or x.0722 and there was another one in between 0.1111 radio - these might be causing problems with the newer Roms. Most of the custom Rom offered here usually (but not always) as a matter of practice, does not change or re-flash to a newer radio unless it specifically stated so in the instructions - so I would just keep extra copies named with its version available, and rename it to PG32IMG.ZIP before moving it onto the mSD card to flash from the Bootloader in case of boot-looping. Just be careful as flashing a non DI2 radio will permanently brick your device.
Our DI2 are on SkyRaider (2.3.4) and runs great with the .0320 radio (the 0.312 radio was used earlier.)
More reading for you - http://forum.xda-developers.com/showthread.php?t=1751796 - with the TACOROOT method, it will downgrade and result in S-ON, prior to running Revolutionary to get S-OFF again with additional steps. Consider this as it sounded like you are comfortable with using ADB.
If you manage to get S-ON somehow via other discovered means, flashing the *.exe again should not affect S-ON/OFF setting.
Generally speaking, if you managed to get the device back to 99% stock look & functioning, and there is no water damage or physical breakage due to accidental dropping, etc. - you shouldn't have any problems with warranty repair or exchange at VZW - I have yet to come across hearing/reading about anyone being denied a claim for updating the radio, HB or kernel, etc. Just bring/send it back to nearly as stock as possible, move/delete anything "unusual" that might be on your mSD card (i.e. empty subdirectory of CWM or Titanium Backup, etc.) and I think you will be fine.
Letitride said:
See this hosted link to a full collection of RUU / roms for the DI2, including those outside US and overseas - please only consider using the last 7 at the bottom as you scroll down, the final 3 might be the older ones (2.3.3 ??) - I've never used this link's files to reflash our DI2, but the download links are working and MD5's provided to verify its integrity upon d/l completion. Use at your own risks & discretion. http://www.androidruu.com/index.php?developer=Vivo_VivoW
The x.0312 radio isn't the newest one, if I am not mistaken - the x.0320 radio is the newest official VZW release for the DI2 & compatible with Gingerbread roms. The older ones x.0622 or x.0722 and there was another one in between 0.1111 radio - these might be causing problems with the newer Roms. Most of the custom Rom offered here usually (but not always) as a matter of practice, does not change or re-flash to a newer radio unless it specifically stated so in the instructions - so I would just keep extra copies named with its version available, and rename it to PG32IMG.ZIP before moving it onto the mSD card to flash from the Bootloader in case of boot-looping. Just be careful as flashing a non DI2 radio will permanently brick your device.
Our DI2 are on SkyRaider (2.3.4) and runs great with the .0320 radio (the 0.312 radio was used earlier.)
More reading for you - http://forum.xda-developers.com/showthread.php?t=1751796 - with the TACOROOT method, it will downgrade and result in S-ON, prior to running Revolutionary to get S-OFF again with additional steps. Consider this as it sounded like you are comfortable with using ADB.
If you manage to get S-ON somehow via other discovered means, flashing the *.exe again should not affect S-ON/OFF setting.
Generally speaking, if you managed to get the device back to 99% stock look & functioning, and there is no water damage or physical breakage due to accidental dropping, etc. - you shouldn't have any problems with warranty repair or exchange at VZW - I have yet to come across hearing/reading about anyone being denied a claim for updating the radio, HB or kernel, etc. Just bring/send it back to nearly as stock as possible, move/delete anything "unusual" that might be on your mSD card (i.e. empty subdirectory of CWM or Titanium Backup, etc.) and I think you will be fine.
Click to expand...
Click to collapse
One question, the *exe you first gave me had a radio 1111 with 2.3.4 , however it had the bootloop problem. The last downgrade to 2.3.3 that I did had another radio that also caused the bootloop problem. My fear is that if I accomplish S-ON and use any *exe to go back to stock 2.3.4 , I will have the bootproble without a way to reflash the radio 302 since I am S-ON at that point.
Is there a way to fix the bootloop problem with S-ON?
Is this make sense to you?
Just to be sure , doing this below, downgrades only the Hboot or also does S-ON, Reading the post is a procedure for phones that S-ON with a particular Hboot and FW version below certain number. Are you recommending this just to downgrade Hboot?
DOWNGRADE TOOL
Versions: HBOOT .98, firmware below 6.01.605.05
This will not work with firmware version 6.01.605.05! Use the tacoroot method!
This tool will downgrade you to 2.3.3, which will allow you to use Revolutionary to gain S-OFF.
Download the tool here, and extract it to a folder where you can easily get to it in a command prompt/terminal.
Now, connect your device to your computer with a USB cable, and turn on USB Debugging in settings. To ensure you are connected, open a command prompt/terminal and type "adb devices". If you see a bunch of letters and numbers followed by "device," you're good to go.
It is more like a challenge now..but may be I should send the phone back with 2.3.4 and S-OFF. I will appreciate if you can answer my questions above.
thanks again
vlsi99 said:
One question, the *exe you first gave me had a radio 1111 with 2.3.4 , however it had the bootloop problem. The last downgrade to 2.3.3 that I did had another radio that also caused the bootloop problem. My fear is that if I accomplish S-ON and use any *exe to go back to stock 2.3.4 , I will have the bootproble without a way to reflash the radio 302 since I am S-ON at that point.
Is there a way to fix the bootloop problem with S-ON? Is this make sense to you?
Just to be sure , doing this below, downgrades only the Hboot or also does S-ON, Reading the post is a procedure for phones that S-ON with a particular Hboot and FW version below certain number. Are you recommending this just to downgrade Hboot?
DOWNGRADE TOOL
Versions: HBOOT .98, firmware below 6.01.605.05
This will not work with firmware version 6.01.605.05! Use the tacoroot method!
This tool will downgrade you to 2.3.3, which will allow you to use Revolutionary to gain S-OFF.
Download the tool here, and extract it to a folder where you can easily get to it in a command prompt/terminal.
Now, connect your device to your computer with a USB cable, and turn on USB Debugging in settings. To ensure you are connected, open a command prompt/terminal and type "adb devices". If you see a bunch of letters and numbers followed by "device," you're good to go.
It is more like a challenge now..but may be I should send the phone back with 2.3.4 and S-OFF ...
Click to expand...
Click to collapse
I have been searching other related Android sources for answers in addition to what's been discussed & shared here - some of the older "tools" or linked files are no longer available (due to various file hosting sites being offline, etc.) so practical options are limited.
A number of older radios apparently bootlooped with 2.3.4 roms (including 622, 722 and 1111 radios) 312 radio works fine and we have them on 2 of our DI2's, the 320 radio is for ICS roms and newer without bootloop issues. If you managed to find a way to lock up the bootloader and S-ON again, and reflashing a stock ROM - it is possible you will experience continuous looping - or, worst, end up bricking the device for good.
Other users have noted that with the newer bootloader that you are on - that downgrading or going back to HB98 or HB97 has been a challenge, if not impossible. Additional attempts could cause more harm than good, bricking the phone - maybe it's time to just leave it alone & send it back for repair/exchange as IS - due to earpiece/volumne issue. If the phone boot & behave normally, have no water damage and other physical breakage, your warranty should be honored.
At this moment, just to be clear - do you still have CWM or custom recovery on the DI2, what kernel & radio are you using?
Letitride said:
I have been searching other related Android sources for answers in addition to what's been discussed & shared here - some of the older "tools" or linked files are no longer available (due to various file hosting sites being offline, etc.) so practical options are limited.
A number of older radios apparently bootlooped with 2.3.4 roms (including 622, 722 and 1111 radios) 312 radio works fine and we have them on 2 of our DI2's, the 320 radio is for ICS roms and newer without bootloop issues. If you managed to find a way to lock up the bootloader and S-ON again, and reflashing a stock ROM - it is possible you will experience continuous looping - or, worst, end up bricking the device for good.
Other users have noted that with the newer bootloader that you are on - that downgrading or going back to HB98 or HB97 has been a challenge, if not impossible. Additional attempts could cause more harm than good, bricking the phone - maybe it's time to just leave it alone & send it back for repair/exchange as IS - due to earpiece/volumne issue. If the phone boot & behave normally, have no water damage and other physical breakage, your warranty should be honored.
At this moment, just to be clear - do you still have CWM or custom recovery on the DI2, what kernel & radio are you using?
Click to expand...
Click to collapse
I am at 2.3.3 ,radio 302 , K 2.6.35.9 (from my last downgrade attempt). Since your *.exe brought me to 2.3.4 (with 1111 radio) , I will re-flash this and put radio 302 back. I have already done this so it is pretty safe. I did not find a *exe RRU with 5.10.605.9 with radio 302.
I have CSW
Doe sit make sense?
thank you so much for all your help
vlsi99 said:
I am at 2.3.3 ,radio 302 , K 2.6.35.9 (from my last downgrade attempt). Since your *.exe brought me to 2.3.4 (with 1111 radio) , I will re-flash this and put radio 302 back. I have already done this so it is pretty safe. I did not find a *exe RRU with 5.10.605.9 with radio 302. ... I have CSW ... Doe sit make sense? /QUOTE]
Hmm, interesting - the 302 radio was only for 2.3.3 Froyo - the earliest batch of DI2 and mostdefinitely had HB.97 bootloader.
Our black DI2 had HB.97 bootloader but was already on GingerBread ROM when unboxed (back in Oct. 2011) and DW's red DI2 had HB.98 bootloader w. GB - we had 622, 722 and 1111 radio - both running .0312 radios now (320 for ICS didn't do anything for us running 2.3.4 Sense-based SkyRaider)
CondemnedSoul isn't active these days (great developer to the HTC Eris days) - has a Return to Stock PG32IMG zip file, that is based on 5.10.605 RUU that you can flash from Custom Recovery (CWM) after downloading, verifying MD5 and moving to mSD card. He does good stuff and everything should be self-contained and should not result in bootlooping, regardless of the radio that is being used.
Here is the link again - http://forum.xda-developers.com/showthread.php?t=1599767
Link to various DI2 radios - http://forum.xda-developers.com/showthread.php?t=1134451
For comparison, I'm @ 2.3.4 with SkyRaider Zeus v1.3 - Kernel 2.6.35. and .0312 radio (Hardware ver is 0001) Since you still have Custom Recovery with S-OFF, you knew already how to fix or stop the bootloop by reflashing the radio - you might want to try the Return to stock PG32IMG zip from CS (link is good & valid) and see what happened then - not sure if it is going to help downgrade the Bootloader. The worst is that you will run the RUU again - how's that sound to you?
From the AndroidRUU host site - the last one on the bottom is the Froyo-based RUU file for the DI2 - http://www.androidruu.com/getdownlo...1.0225_2_NV_VZW1.92_release_182876_signed.exe
D/L it first if you are daring enough to flash it - proceed at your OWN RISKS - to see whether it can downgrade the bootloader as well. http://rootzwiki.com/topic/1579-how-to-restore-to-stock-from-alpharevx-incredible-2-vivow-only/
Click to expand...
Click to collapse
curti was
Letitride said:
I have been searching other related Android sources for answers in addition to what's been discussed & shared here - some of the older "tools" or linked files are no longer available (due to various file hosting sites being offline, etc.) so practical options are limited.
A number of older radios apparently bootlooped with 2.3.4 roms (including 622, 722 and 1111 radios) 312 radio works fine and we have them on 2 of our DI2's, the 320 radio is for ICS roms and newer without bootloop issues. If you managed to find a way to lock up the bootloader and S-ON again, and reflashing a stock ROM - it is possible you will experience continuous looping - or, worst, end up bricking the device for good.
Other users have noted that with the newer bootloader that you are on - that downgrading or going back to HB98 or HB97 has been a challenge, if not impossible. Additional attempts could cause more harm than good, bricking the phone - maybe it's time to just leave it alone & send it back for repair/exchange as IS - due to earpiece/volumne issue. If the phone boot & behave normally, have no water damage and other physical breakage, your warranty should be honored.
At this moment, just to be clear - do you still have CWM or custom recovery on the DI2, what kernel & radio are you using?
Click to expand...
Click to collapse
Ok here is how to S-ON and go back to v2,3,4 only if your phone works with radio 1111, IMPORTANT ---< You need to try this version with S-OFF first in case you get into booloop and can re-flash the radio 312
Follow this link
http://www.iball99.com/2013/04/htc-incredible-2-gingerbread-rooted-stock/
Revert to Stock Froyo
Re-flash Hboot 0.97 ---<At this point you are S-off but the next stock flash will take you back to S-ON
Update back to Gingerbread ----< WARNING assuming you don't get into booloop with radio 1111
Otherwise, I assume you can't recover from with S-ON and bootloop mode?? Is this true??
I did not try to reflash stock because my phone gets into bootloop with radio 1111.
But I was able to downgrade and re-flash Hboot 0.97 . I only need a to find a zip or ^exe with radio 312
I really appreciate your help!!
vlsi99 said:
Ok here is how to S-ON and go back to v2,3,4 only if your phone works with radio 1111, IMPORTANT ---< You need to try this version with S-OFF first in case you get into booloop and can re-flash the radio 312
Follow this link http://www.iball99.com/2013/04/htc-incredible-2-gingerbread-rooted-stock/
Revert to Stock Froyo
Re-flash Hboot 0.97 ---<At this point you are S-off but the next stock flash will take you back to S-ON
Update back to Gingerbread ----< WARNING assuming you don't get into booloop with radio 1111
Otherwise, I assume you can't recover from with S-ON and bootloop mode?? Is this true??
I did not try to reflash stock because my phone gets into bootloop with radio 1111.
But I was able to downgrade and re-flash Hboot 0.97 . I only need a to find a zip or ^exe with radio 312
Click to expand...
Click to collapse
Thanks for the info - for the time being, my motto is "if it ain't broke, don't mess with it or change it" but I'm downloading those patches via my Linux server to offline storage, just in case that I want to or need it later on, once I'm done with using the DI2 as my daily device, LOL - less than 2 months left on my contract & seriously considering Nexus 4 now the price drop - whether there's a Gen II or now, just to team up with the beloved Nexus 7 running JB 4.3
If I am going to play - and mine doesn't bootloop with the 1111 radio (nor the 722 or 622 radios based on Froyos) - flash the stock RUU files - it's been a while in dealing with those *.nb0 - once it's back to S-ON and locked bootloader with stock recovery, it's much harder to recover if the Rom run into a continuous looping. Our warranty has expired long ago and I don't plan on selling these on *Bay with its low resale/market value, so just going to keep it as a backup even if I'm going to switch to GSM services - 3G CDMA coverage is barely working inside our house but thankfully for Fios, I have ultra fast broadband coverage 85% to 90% of the time that smoked the best 4G LTE out there today.
I dont' recall either, whether one of the GB RUU from VZW has the 312 radio included in the *.exe download, it could've been an OTA file on a stock Rom, but the 1111 radio was definitely in one of the stock RUU in the link - the discussions on where the developers (AndyBone, CS or Nit's) pulled the 312 radio were "buried" in their development Rom's, if only I have time to dig thru them.
Sounds like your DI2 is where you wanted it to be in restoring to stock form, good luck in getting the warranty exchange or repair done. Regards !
Dear XDA developers, professionals and programmers:
Recently I came across a good deal (HTC M8 in mint condition) and bought it. It was running Android 4.4.4 and I was happy with it till I read that it could be updated to Marshmallow. I followed a few links and after some time discovered that it was originally bought from the USA and locked to AT&T even though the installed rom was WWE. Stupidly I downloaded Marshmallow update for AT&T (RUU) from the HTC website and ran the installer. The installer completed successfully and the phone now runs Marshmallow with Sense7.
Since the rom was filled to brim with useless AT&T crap that does not work outside AT&T network I decided to switch to developer WWE rom but the RUU refused to install on the phone (I have S-Off)
After doing a bit more reading I discovered it was because my new rom has a software number 6.20.502.5 while the RUU I would like to install has a software number of 6.12.1540.4
I googled and googled and searched and searched but could not find a single tutorial to explain how I can replace my current rom with the WWE version which has less bloatware and takes it easy on the RAM.
Can someone kindly explain (or redirect me to a link) of how to downgrade HTC M8 from image version 6.20.502.5 to image version 6.12.1540.4 or in layman's terms how to replace AT&T rom with Developer rom? BTW both roms are Marshmallow. I do not wish to install TWRP or CM so if there is a way besides this I'd be grateful. If not then I don't see any other options and I'd still be grateful
Awaiting your generous replies
What you want is not really a "downgrade" per se. While the AT&T version number is "larger" than the Dev Ed (6.20 versus 6.12), that is mostly just because it came later due to AT&T's slowness in approving the software. I don't think there is much (if anything) that is actually "newer" or "updated" in the AT&T stock ROM (versus Dev Ed). It just has (as you know) all the AT&T branding and bloatware crap.
What is keeping you from flashing the Dev Ed RUU 6.12.1540 is that your carrier ID (CID) needs to match the RUU (even with s-off). Therefore, you need to change your CID to that of the Dev Edition (or alternately SuperCID), which is easy since you already have s-off. You will however need root to do this, so either flash TWRP and SuperSU/Magisk to root, or you can run adb shell with run while booted to TWRP. Either way, you will need to install TWRP: https://forum.xda-developers.com/htc-one-m8/general/change-wwe-m8-to-dev-edition-ota-t2826567
No need to change the Model ID (MID) since the AT&T version and Dev Edition have the same MID.
After that, you should be able to run the Dev Ed RUU.
Sorry .. correction. No need root/twrp to change CID, only change MID need these.
Simply reboot to bootloader/fastboot then run command
To Dev Ed CID
fastboot oem writecid BS_US001
To SuperCID
fastboot oem writecid 11111111
Can't remember if this only can be done on unlocked bootloader. If can't, try this command first
fastboot oem rebootRUU
the follow by the above.
If still can't then need a unlocked bootloader to proceed.
ckpv5 said:
Sorry .. correction. No need root/twrp to change CID, only change MID need these.
Click to expand...
Click to collapse
Ah yes, obviously I was mixing up my methods to change CID versus MID.
Thanks for clarifying, yet again.
Thank you
Many thanks to you gentlemen for your generous assistance and helpful instructions. I really appreciate it. All the best
Update
Good day all:
Sorry to bother again but it failed again! I downloaded fastboot adb and followed the procedure, put the phone in fastboot mode and the CID was already 11111111 and still it refused to accept the RUU. Please find attached a photo of my fastboot screen, hope it can help determine where the problem is on my phone. [ The following errors occurred with your submission:
To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!] Site refused to allow me to attach the photo link so I'll just write everything here
*****Software Status - Official******
******LOCKED******** (Even though I can use a non AT&T sim normally)
MS_UL_CA PVT SHIP S-OFF
CID~11111111
HBOOT - 3.19.0.0000
Radio - [email protected](long number)
OPENDSP - v56.2.2. (loooooooong number)
OS-6.20.502.5
eMMC Boot - 2048MB
*end of pic*
On the official HTC site in the support section where they post the RUUs it states the following.
"Before you proceed, please confirm that this software upgrade to 6.12.1540.4 is a newer version than what is currently loaded on your device. If it is the same version, there is no need to reload the software. Navigate to the Home screen then tap All apps > Settings > About and locate the Software information . If your Software number is less than 6.12.1540.4 , you should proceed with the upgrade." end of quote
This paragraph is what let me to believe it is the software version that is stopping me from changing RUUs and why I called this post a downgrade (even though I know it's not)
Can any of you good gentlemen help me out a bit more? I'm willing to answer any questions to further clear the picture of my predicament.
Thank you again
Bootloader is fine, still ATT.
Explain more on the error that you have when you tried installing RUU.
Do note - to run RUU you need PC with USB 2.0;
Latest htc usb drivers which you'll get when you installed latesr htc sync manager (uninstall sync manager but leave all drivers to proceed RUU installation)
ckpv5 said:
Bootloader is fine, still ATT.
Explain more on the error that you have when you tried installing RUU.
Do note - to run RUU you need PC with USB 2.0;
Latest htc usb drivers which you'll get when you installed latesr htc sync manager (uninstall sync manager but leave all drivers to proceed RUU installation)
Click to expand...
Click to collapse
Thank you for your reply:
the RUU I'm trying to install is the developer RUU that I downloaded off the HTC official website. It is the same website I downloaded the AT&T RUU from which installed fine, upgrading the phone's OS from Android 4.4.4 to Android 6.0.
I have several laptops each running a different OS (Windows 7 which I use mostly and have been using for this process) Windows 10, Linux and Solaris.
I did download and install HTC Sync but disabled it's auto run when I noticed every time I plug my phone in it pops up. So that's disabled not uninstalled, but it didn't interfere in the RUU installation of the ATT update and it doesn't pop up when I try to install the developer update.
The Error get is as follows:
Upon running the RUU it does all the necessary checks and then asks me if I would like to install the update, I click on "I Agree" and next, then it puts the phone in boot mode (black screen with HTC written in grey) and after it begins the process by popping up a screen that says: Current info about your Android phone: Image Version: 6.20.502.5 select one below and the update button. After I click on it another screen pops up: Verify that you want to update the Rom version from image version 6.20.502.5 to image version 6.12.1540.4 Clicking on Next another windows shows explaining what happens when I click on Next. When I click next it puts the phone in boot mode and begins by Reading header, sending............................................. then it pops another screen that says update failed and I have to click on recovery and press the power button on my phone for 10 seconds to turn it off
Sir Lucifer said:
On the official HTC site in the support section where they post the RUUs it states the following.
"Before you proceed, please confirm that this software upgrade to 6.12.1540.4 is a newer version than what is currently loaded on your device. If it is the same version, there is no need to reload the software. Navigate to the Home screen then tap All apps > Settings > About and locate the Software information . If your Software number is less than 6.12.1540.4 , you should proceed with the upgrade." end of quote
This paragraph is what let me to believe it is the software version that is stopping me from changing RUUs and why I called this post a downgrade (even though I know it's not)
Click to expand...
Click to collapse
You can't really take the "official" HTC info literally, anymore. By having s-off and SuperCID, you are so far off the "official" path, that most of the rules no longer apply.
S-off bypasses version check (flashing older RUUs is allowed). In fact, you can RUU all the way back to Kitkat if you wanted with s-off (not recommended - just making a point).
---------- Post added at 09:56 AM ---------- Previous post was at 09:52 AM ----------
Sir Lucifer said:
The Error get is as follows:
Upon running the RUU it does all the necessary checks and then asks me if I would like to install the update, I click on "I Agree" and next, then it puts the phone in boot mode (black screen with HTC written in grey) and after it begins the process by popping up a screen that says: Current info about your Android phone: Image Version: 6.20.502.5 select one below and the update button. After I click on it another screen pops up: Verify that you want to update the Rom version from image version 6.20.502.5 to image version 6.12.1540.4 Clicking on Next another windows shows explaining what happens when I click on Next. When I click next it puts the phone in boot mode and begins by Reading header, sending............................................. then it pops another screen that says update failed and I have to click on recovery and press the power button on my phone for 10 seconds to turn it off
Click to expand...
Click to collapse
The RUU stalling out while "sending" is a common bug. Did you simply try running the RUU again? A lot of times, it will work on subsequent attempts.
The fact it got that far, means to me that it passed (or bypassed) any version or CID checks. Otherwise, it never would have gotten to the point of "sending". Instead, it would have told you something like "Error 140" with a description of what the problem was, and aborted the install before ever "sending".
redpoint73 said:
You can't really take the "official" HTC info literally, anymore. By having s-off and SuperCID, you are so far off the "official" path, that most of the rules no longer apply.
S-off bypasses version check (flashing older RUUs is allowed). In fact, you can RUU all the way back to Kitkat if you wanted with s-off (not recommended - just making a point).
---------- Post added at 09:56 AM ---------- Previous post was at 09:52 AM ----------
The RUU stalling out while "sending" is a common bug. Did you simply try running the RUU again? A lot of times, it will work on subsequent attempts.
The fact it got that far, means to me that it passed (or bypassed) any version or CID checks. Otherwise, it never would have gotten to the point of "sending". Instead, it would have told you something like "Error 140" with a description of what the problem was, and aborted the install before ever "sending".
Click to expand...
Click to collapse
Have tried it 5 times already, results are the same. I'm downloading the RUU again, maybe my download was corrupt. Will get back to you later with any results. Thank you for your patience and time. Much appreciated
redpoint73 said:
You can't really take the "official" HTC info literally, anymore. By having s-off and SuperCID, you are so far off the "official" path, that most of the rules no longer apply.
S-off bypasses version check (flashing older RUUs is allowed). In fact, you can RUU all the way back to Kitkat if you wanted with s-off (not recommended - just making a point).
---------- Post added at 09:56 AM ---------- Previous post was at 09:52 AM ----------
The RUU stalling out while "sending" is a common bug. Did you simply try running the RUU again? A lot of times, it will work on subsequent attempts.
The fact it got that far, means to me that it passed (or bypassed) any version or CID checks. Otherwise, it never would have gotten to the point of "sending". Instead, it would have told you something like "Error 140" with a description of what the problem was, and aborted the install before ever "sending".
Click to expand...
Click to collapse
Maybe my downloaded RUU is corrupt, I'll download another time and if it gives me the same problem I'll look for another source. I will keep you posted, thank you very much good man.
RUU Broken on HTC's website
Dear all:
After downloading the developer RUU for the second time and trying to install it again (Marshmallow for those of you who have just joined us) off the HTC support site I failed miserably at changing my firmware using that RUU. After a series of searches on the internet and darknet I came across a post on reddit dot com titled M8 marshmallow RUU from HTC is broken and the article was dated last year. Searching further I found a similar post on a Chinese website that stated the same thing. So in conclusion the developer RUU on HTC's site is damaged as confirmed by a few users/developers on both reddit and the Chinese website.
Sorry for wasting all your time gentlemen. I am very grateful (and very lucky) having assistance from good people like yourselves who have taken from their time to help a complete stranger. Much obliged gentlemen. And thank you all again
Cannot be the RUU is broken.
Another way to do this :
1. Install Dev Edition firmware. You can get the fw_6.12.1540.4.zip from - https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
2. Instead of using RUU exe, you can use RUU zip (rom.zip) to install RUU. I remember long time ago someone had same problem like you. Asked him to use zip format RUU and it was successful.
I believe there is RUU.zip somewhere on XDA. Can't search now as I'm on mobile.
You can get your own RUU.zip which is actually rom.zip yourself. Just run RUU.exe (no need to connect phone). Once it opens the agreement page, go to %temp% thru your search/run windows menu.
It's better to clear your temp directory first so easy to find 2 newly created folder when you run RUU.exe
The rom.zip is inside one of the folder. Copy that to your desktop.
Then follow this on how to install - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
There are 3 methods but I prefer the htc_fastboot because easily can see any error if any.
So step 1 firmware & step 2 RUU (rom.zip)
Sir Lucifer said:
Dear all:
After a series of searches on the internet and darknet I came across a post on reddit dot com titled M8 marshmallow RUU from HTC is broken and the article was dated last year. Searching further I found a similar post on a Chinese website that stated the same thing. So in conclusion the developer RUU on HTC's site is damaged as confirmed by a few users/developers on both reddit and the Chinese website.
Click to expand...
Click to collapse
Did those threads specifically mention RUU 6.12.1540.4? If not, then you realize this device has dozens of RUUs for the M8? Most of which have been confirmed many times over to work properly.
My experience, is that 95% of the time, the problem with RUU running is with the PC. Try re-installing HTC drivers, different USB port, turn off USB 3.0. Also try a different USB cable, or if possible another PC.
Downloading the RUU again (as you tried) is not a bad idea. They do sometimes get corrupted while downloading. But if you download another time, and it still fails, the problem is probably not the RUU.
You should also verify your PC has Visual C++ installed, as the RUU exe requires it. The error your are encountering doesn't sound like the C++ problem. But it won't hurt to verify, anyway. Link here, but confirm it's the right install for your Windows version: https://forum.xda-developers.com/showpost.php?p=60021580&postcount=4
Or of course, you can use the RUU.zip method stated by ckpv5, which avoids all the of the above possible pitfalls. You'll need to search for the 6.12.1540.4 zip, as I don't know where it is off hand, either.
Downloaded Again
redpoint73 said:
Did those threads specifically mention RUU 6.12.1540.4? If not, then you realize this device has dozens of RUUs for the M8? Most of which have been confirmed many times over to work properly.
My experience, is that 95% of the time, the problem with RUU running is with the PC. Try re-installing HTC drivers, different USB port, turn off USB 3.0. Also try a different USB cable, or if possible another PC.
Downloading the RUU again (as you tried) is not a bad idea. They do sometimes get corrupted while downloading. But if you download another time, and it still fails, the problem is probably not the RUU.
You should also verify your PC has Visual C++ installed, as the RUU exe requires it. The error your are encountering doesn't sound like the C++ problem. But it won't hurt to verify, anyway. Link here, but confirm it's the right install for your Windows version: https://forum.xda-developers.com/showpost.php?p=60021580&postcount=4
Or of course, you can use the RUU.zip method stated by ckpv5, which avoids all the of the above possible pitfalls. You'll need to search for the 6.12.1540.4 zip, as I don't know where it is off hand, either.
Click to expand...
Click to collapse
I did download the developer RUU again, I also downloaded the Metro PCS RUU which has a software number of 6.20.531.5 and it installed just fine but refused to see the sim card so I reinstalled AT&T
I am an electronics engineer so yes my laptops are always up to date on flash, oracle, C++, Perl, Java, etc
ckpv5 said:
I believe there is RUU.zip somewhere on XDA. Can't search now as I'm on mobile.
Click to expand...
Click to collapse
redpoint73 said:
You'll need to search for the 6.12.1540.4 zip, as I don't know where it is off hand, either.
Click to expand...
Click to collapse
Sir Lucifer said:
I did download the developer RUU again, I also downloaded the Metro PCS RUU which has a software number of 6.20.531.5 and it installed just fine but refused to see the sim card so I reinstalled AT&T
I am an electronics engineer so yes my laptops are always up to date on flash, oracle, C++, Perl, Java, etc
Click to expand...
Click to collapse
I have the RUU.zip
You can download it from here :good:
Sir Lucifer said:
I also downloaded the Metro PCS RUU which has a software number of 6.20.531.5 and it installed just fine but refused to see the sim card so I reinstalled AT&T
Click to expand...
Click to collapse
That is the T-Mobile RUU. MetroPCS merged with T-Mobile, so it's a bit one and the same. But most everyone will call that RUU/version T-Mobile. It will change band support (as flashing any other RUU will). So if it was working before on the AT&T RUU(or Dev ED will support the same bands) I would not mess with random RUUs, unless we suggest them specifically.