Develop Bugs

Can't even downgrade - error 140

Hello all,
Played around with unrevoked 1, loved it, did the OTA update once and obviously my (soft) root ability has been lost.
Problem is I can't even restore DOWN to the stock firmware. I get Error 140 - bootloader version error.
If I try doing any custom flashing, I get an error about flashing to an older version.
I've done a ton of reading and searching, it would seem I'm "stucK' at the moment correct? Can't downgrade, and can't flash my way to a rooted/free bootloader?
Thanks in advance guys! looking forward to spending some serious time here to learn!
Jeff

It's my understanding that if you installed the ota update you are going to have to wait for a new root method. Nothing can be done as of yet. It just takes time, it's only been a couple of days.

Thanks, that's what I figured. What had me scared is the fact that I can't even use HTC's own software, or firmware to take an HTC device back to the "out of the box" state.
Love the HTC hardware, however their software and general approach to patching sucks.

[Q] Getting rid of Vodafone AU ROM to 'stock'?

Hi,
I've had my DHD for 6 months now, and I love it, but after seeing this thread...
http://forum.xda-developers.com/showthread.php?t=1056329
I've finally decided I want to get rid of the Vodafone crap on my phone. It takes way longer to boot than it should, I have stupid apps on there, and I'm generally sick of seeing the Vodafone symbol every time I boot my phone, especially as I bought the phone from them and am not even contracted to them.
Is there an easy way to rid myself of this Vodafone branded ROM? I know next to nothing about rooting or anything, however.
After seeing the link above, I realised that I'll probably be waiting ages for Vodafone to send the update OTA, and I would really like some Gingerbread around about now. Hopefully the process will speed up my phone.
But, is there anyway I can do this without losing everything on my phone? My messages, apps, settings?
A lot of questions there - thanks in advance.

Hi, you will lose everything you don't backup.
Apps will need to be reinstalled, and settings will be lost.
If your firmware version is greater than 1.3x.xxx.x then you will need to downgrade to 1.32
Follow THIS thread to downgrade.
Once downgraded simply download & run the RUU~.exe file and it will take care of the rest.

How could I backup my apps (and settings) and restore them once updated?
My 'software version' is 1.32.178.5
Looking at the link you provided, it says...
System requirements:
Desire HD with build number 1.72 or higher
My DHD's build number is 1.32.xxx.x... Do I...not have to downgrade? Or what?
Also, since I'm running on an Australian network (Virgin), will I need to incorporate that somehow into the software I put onto the phone or something..?

You can root your phone and use clockwork to remove data/cache to go back to factory settings
as for the virgin thing, just make sure your APNs are correct and you should be fine

So I could root it and use Clockwork and my phone would basically be like a standard Desire HD that I bought new, unbranded in a shop?

yeah but you will also lose all your contacts and messages etc
i think you can use titaniumbackup to save those kind of things .. but done quote me because ive never done this, ive only rooted and cleared then flashed a new rom on

actually look up a stock RUU guide
EDIT: Just Root your phone and flash a custom rom imo
I did it .. never going back

Hmm, okay.
What about if I wanted to put something on my phone like the link I posted up top, the 2.3 'release'?

well click the ROOTED link in my sig
and do all the steps with the exception of the flashing of the MIUI.zip ... just replace it with the custom rom of your choice and bobs your uncle
i advice to back up your apps and anything else you want to keep

Wildfire S ota update issue.

I got myself a wildfire s a short while ago, so I could teather my galaxy tab 10.1 (my S2 was stolen). It seemed a good idea at the time, to get a cheap, small Android phone, for this purpose and just making phonecalls.
I knew the phone had limited storage, but at the time wasn't really an issue.
I unboxed it, started it up, put my sim card in, and away I went. ( I bought it sim - free brand new from carphone warehouse )
once set up, it informed me there was an ota update, which went fine, no problem. I continued to set the phone up with my favorite softwares, and everything was great.
This is where the problem started.
A few weeks later, It told me there was new update, so update i _TRIED_ . And failed. It told me that the firmware on the phone was not HTC, and would not be updated.
Not a problem, I dont care, i thought. It does all i need to do, and I didnt really want to do a full reset on it, so I didnt bother for a couple of months, it was fine.
Eventually, I started to find the tiny storage quite irritating, so got myself a class 10 8GB SD card, and looked into using somthing like Data2SD.
No problem, Iv rooted a few phones, so did the required reading into getting root and s-off. Easy ( I thought ).
I took myself off the htc dev, to download the unlocked bootloader today, and attempted to install. UH-OH.. Error 190 .. Wrong firmware version.
I decided now was as good a time as any to hard reset, as it would happen anyway, and retry the ota update..... FAIL!
I contacted HTC, and they said I would have to send off for repair ( I guess I could, its stock, unmodded in any way yet ) but that would mean I would be without my phone.
then I tried this : http://forum.xda-developers.com/showthread.php?t=1445867&page=1
didnt work. I need the new 2.33.401.3 software, but im stuck on 1.33.401.3 (Android 2.3.3)
Is there a way to root and s-off the older firmware as HTC DEV now require you to have the newer firmware to unlock the bootloader, or atleast manually flash the newer firmware??
Plz help me, before i chuck my phone in the sink!
Thanks,
Dave

Get the RUU of 2.13.401.whatever from somewhere (You'll find it in the 'Shipped marvel rom collection' at the top of the dev section) and run that first before you you run the unlockable bootloader one and tell us what happens

This worked perfectly. Thankyou. I downloaded the HTC EU rom, for 2.13.401.3, Flashed it in, and the rest worked.
Thanks again,
Dave

Hi, digitalwarfare
you flashed this
RUU_Marvel_S_HTC_Europe_2.13.401.3_Radio_47.23c.35.3037_7.54.39.28M_release_236989_signed.exe
or this
Marvel_S_HTC_Europe_2.13.401.3_Radio_47.23c.35.3037_7.54.39.28M_release_236989_signed_ROM.zip
What are the differences, please?

[Q] Confused...

So i'm confused about this whole thing with ROMs and firmware and the Viper One 3.0.0 that was just released.
I've been playing it safe with ROMs, being outdated regularly because "it worked". Probably not the best choice for security reasons, but wiping my phone and reinstalling the OS, restoring all the apps, is time consuming and something I try to avoid doing as much as possible.
So Saturday I upgraded my phone from 1.9.1 of Viper One M9 to 2.3.0, then took the OTA to 2.3.1. Previously I installed 1.9.1 and a week later 2.0.0 came out. So I waited until this weekend to finally go to 2.x.x. In a mean twist of fate, less than 24 hours later I'd find that Viper One M9 3.0.0 is out. So no matter what I try to do it seems I'm in for perpetual upgrades, wiping and reinstalling the OS, restoring apps, etc.
So here's my questions:
1. Do I actually need to install any firmwares for this? I see dottat's thread http://forum.xda-developers.com/verizon-one-m9/general/official-ruu-1-33-605-15-t3137397 and I'm not sure if I'm supposed to install that first. My instinct is "no" but I would like to verify that before I try to go to 3.0.0.
2. If it's not required, is it at least optional? If so, what benefits are we aware of that the new firmware will fix? I get the impression that the firmware update isn't truly supported with Viper One M9 since the firmware hasn't been officially released, nor was it unofficially released before the compiled 3.0.0 build was released.
3. How "official" is the 1.33.605.15 that I just linked above? Is it 100% for sure going to be the next release and we're just waiting for it to be pushed out as an OTA update? When I had my Droid Bionic we had something like 20+ "unofficial" builds of ICS that were leaked early, and ultimately the one that was released OTA was 3 or 4 versions behind what was the 'latest'. Definitely created problems for some people and not looking to see that happen to me.
4. When I do an upgrade of Viper One, I normally do the full wipe and then have to restore the apps with titanium backup, then the SMS messages that I have with another app, resetup the icons on my screens, resetup the viper settings, etc. Takes me basically a full day to re-test and re-setup everything how I like it. Is there a better way that doesn't take all day? I'd prefer to be on the latest, but with the constant restoring I'm pretty much always behind because I don't have the 8+ hours it takes to resetup my phone exactly how I want it every time an update comes out. I've heard the non-wiping is not recommended, so I've never tried that. Is it actually safe and effective?
5. Anyone using 3.0.0 and having any problems or comments?
In case anyone asks, the phone is s-off, rooted, etc by the mighty dottat with his Java card.
Thanks,
-Josh

Joshy8 said:
So i'm confused about this whole thing with ROMs and firmware and the Viper One 3.0.0 that was just released.
I've been playing it safe with ROMs, being outdated regularly because "it worked". Probably not the best choice for security reasons, but wiping my phone and reinstalling the OS, restoring all the apps, is time consuming and something I try to avoid doing as much as possible.
So Saturday I upgraded my phone from 1.9.1 of Viper One M9 to 2.3.0, then took the OTA to 2.3.1. Previously I installed 1.9.1 and a week later 2.0.0 came out. So I waited until this weekend to finally go to 2.x.x. In a mean twist of fate, less than 24 hours later I'd find that Viper One M9 3.0.0 is out. So no matter what I try to do it seems I'm in for perpetual upgrades, wiping and reinstalling the OS, restoring apps, etc. [emoji14]
So here's my questions:
1. Do I actually need to install any firmwares for this? I see dottat's thread http://forum.xda-developers.com/verizon-one-m9/general/official-ruu-1-33-605-15-t3137397 and I'm not sure if I'm supposed to install that first. My instinct is "no" but I would like to verify that before I try to go to 3.0.0.
2. If it's not required, is it at least optional? If so, what benefits are we aware of that the new firmware will fix? I get the impression that the firmware update isn't truly supported with Viper One M9 since the firmware hasn't been officially released, nor was it unofficially released before the compiled 3.0.0 build was released.
3. How "official" is the 1.33.605.15 that I just linked above? Is it 100% for sure going to be the next release and we're just waiting for it to be pushed out as an OTA update? When I had my Droid Bionic we had something like 20+ "unofficial" builds of ICS that were leaked early, and ultimately the one that was released OTA was 3 or 4 versions behind what was the 'latest'. Definitely created problems for some people and not looking to see that happen to me.
4. When I do an upgrade of Viper One, I normally do the full wipe and then have to restore the apps with titanium backup, then the SMS messages that I have with another app, resetup the icons on my screens, resetup the viper settings, etc. Takes me basically a full day to re-test and re-setup everything how I like it. Is there a better way that doesn't take all day? I'd prefer to be on the latest, but with the constant restoring I'm pretty much always behind because I don't have the 8+ hours it takes to resetup my phone exactly how I want it every time an update comes out. I've heard the non-wiping is not recommended, so I've never tried that. Is it actually safe and effective?
5. Anyone using 3.0.0 and having any problems or comments?
In case anyone asks, the phone is s-off, rooted, etc by the mighty dottat with his Java card.
Thanks,
-Josh
Click to expand...
Click to collapse
There's newer firmware out. Look in neo's 5.1 deodex thread. That os is also 5.1 (rom).
Sent from my HTC6535LVW using Tapatalk

LOL! So it is! I saw it last night and somehow I screwed up and linked to your thread. Hooray for tired long days.

1. You do need to update your firmware to 2.6.605.10 before installing ViperOneM9 3.0.0, or you will most likely see a bootloop or have other issues.
2. ViperOneM9 3.0.0 was based on the 2.6.605.10 firmware that is posted in NEO's thread. Bottom line is that you should be on that firmware before flashing viper.
3. The 2.6.605.10 firmware is official, but prerelease, and it is very likely not the final version that will be released when the FOTA is pushed out to the public. You can just flash the firmware of the final release version when that is released, so you don't need to worry about being ahead/behind the release version.
4. On ViperOneM9, there is no reason to do a full wipe unless you are coming from another ROM. If you read the thread, you will see that the developers and most of the people around there haven't done a clean flash since their first flash of viper. Make a backup before flashing, and you can always revert to that if you have an issue when you dirty flash.
5. 3.0.0 is working great. No reason not to update.

Thanks for the response bschram. It is appreciated.
I actually wiped my phone and installed 3.0.0 without updating the firmware. Phone still works fine, but I will be updating the firmware as soon as I am confident I know what I'm doing with firmware upgrades. I'm a bit more nervous about updating firmware as I don't want to break the phone.
I'm glad to hear that I don't have to do a full wipe, and I'll definitely be doing that going forward. I will say that 3.0.0 is way more reliable than 1.9.1 was.

Just to make sure I am doing things correctly.... I am not totally new to this. Coming from stock 5.0.2... with S-off/Bootloader Unlocked. Flash firmware from NEO's deodexed rom in fastboot, advanced wipe in TWRP, then flash any 5.1 rom that is compatible IC, Viper, ect.... Then we should be good to go?
Then when offical OTA arrives, wait until firmware is pulled then flash the same way? Just making sure I will doing things right..... Thanks in advance

bschram said:
1. You do need to update your firmware to 2.6.605.10 before installing ViperOneM9 3.0.0, or you will most likely see a bootloop or have other issues.
2. ViperOneM9 3.0.0 was based on the 2.6.605.10 firmware that is posted in NEO's thread. Bottom line is that you should be on that firmware before flashing viper.
3. The 2.6.605.10 firmware is official, but prerelease, and it is very likely not the final version that will be released when the FOTA is pushed out to the public. You can just flash the firmware of the final release version when that is released, so you don't need to worry about being ahead/behind the release version.
4. On ViperOneM9, there is no reason to do a full wipe unless you are coming from another ROM. If you read the thread, you will see that the developers and most of the people around there haven't done a clean flash since their first flash of viper. Make a backup before flashing, and you can always revert to that if you have an issue when you dirty flash.
5. 3.0.0 is working great. No reason not to update.
Click to expand...
Click to collapse
Came in a bit late to the m9 threads. Is the losing VOLTE thing still a thing or was that earlier builds and firmwares? My phone is attached to my work account so it's big pain to talk with actual verizon and i've been hesitant on flashing roms. Not asking for gaurantees, i get the risk, just wondering if that is still going on.

teckels said:
Came in a bit late to the m9 threads. Is the losing VOLTE thing still a thing or was that earlier builds and firmwares? My phone is attached to my work account so it's big pain to talk with actual verizon and i've been hesitant on flashing roms. Not asking for gaurantees, i get the risk, just wondering if that is still going on.
Click to expand...
Click to collapse
It's never been 100% understood why this has happened. It isn't specific to any ROM, I think someone on stock rooted ROM had this issue happen. Once you S-OFF you will be at risk, as far I am aware.

andybones said:
It's never been 100% understood why this has happened. It isn't specific to any ROM, I think someone on stock rooted ROM had this issue happen. Once you S-OFF you will be at risk, as far I am aware.
Click to expand...
Click to collapse
Is it a common thing or has it only happened to one or two people.

Tommydorns said:
Is it a common thing or has it only happened to one or two people.
Click to expand...
Click to collapse
I
Thiss I am not too sure of, but I don't think too many.

Tommydorns said:
Is it a common thing or has it only happened to one or two people.
Click to expand...
Click to collapse
Me and one or two others. I have my suspicions as to what caused it and the casual crack rom flasher likely won't fall victim to it.
Sent from my HTC6535LVW using Tapatalk

What are my options on a 2PS6400 with Android versions Rooting and S-OFF

I bought this new off eBay for development only. I have no plans to Activate it.
I would love to just run RUU for Android 6, 7, or 8 as needed.
Which RUU's do I need for a 2PS6400
I'm confuse what this phone is. It was advertised as "Sprint Unlocked". It was brand new sealed.
I put an old Sprint SIM in it, just to get rid of some warnings and wasn't sure if it would help GPS quality by pinging towers. GPS is running pretty poorly. Runs fine on Deactivated M9.
It doesn't have any Sprint Crap on it, which is really nice.
I would like to avoid S-OFF and rooting if possible. But I don't mind using the ZIP RUU on the SD Card to switch.
I just noticed this thread of someone switching from Nougat to Marshmallow but he was S_OFF, Rooted, TWRP etc.
But based on the Video he posted to finally make it work, if he put the ZIP on the SD Card my recollection is S-OFF wouldn't matter.
Anything other than RUU makes me nervous trying to go backwards manually flashing old firmware with S-OFF (with partition changes etc.).
I've also lost S-OFF that I paid for in the M9. I don't mind at all in paying once, but I'm not paying multiple times.
Also it shows 2.42.651.66 Are their Android 7 updates I can apply?
If I check for software updates, it might kick off the Android 8 update and I may not be able to stop it. What are my options there?

boot into download mode. If it was a true brand new sprint phone that was unlocked it would still have sprint apps. People on ebay are either buying new phones and flashing new roms themselves or buying new phones thatve been flashed by some other company.
Hold vol down and power button until the htc logo lights up and it should boot into download mode. Take note of the red colored data up top and write down the radio and os. Also do a imei and serial number check. If its anything other than an htc 10 send it back

mswlogo said:
I bought this new off eBay for development only. I have no plans to Activate it.
I would love to just run RUU for Android 6, 7, or 8 as needed.
Which RUU's do I need for a 2PS6400
I'm confuse what this phone is. It was advertised as "Sprint Unlocked". It was brand new sealed.
I put an old Sprint SIM in it, just to get rid of some warnings and wasn't sure if it would help GPS quality by pinging towers. GPS is running pretty poorly. Runs fine on Deactivated M9.
It doesn't have any Sprint Crap on it, which is really nice.
I would like to avoid S-OFF and rooting if possible. But I don't mind using the ZIP RUU on the SD Card to switch.
I just noticed this thread of someone switching from Nougat to Marshmallow but he was S_OFF, Rooted, TWRP etc.
But based on the Video he posted to finally make it work, if he put the ZIP on the SD Card my recollection is S-OFF wouldn't matter.
Anything other than RUU makes me nervous trying to go backwards manually flashing old firmware with S-OFF (with partition changes etc.).
I've also lost S-OFF that I paid for in the M9. I don't mind at all in paying once, but I'm not paying multiple times.
Also it shows 2.42.651.66 Are their Android 7 updates I can apply?
If I check for software updates, it might kick off the Android 8 update and I may not be able to stop it. What are my options there?
Click to expand...
Click to collapse
The last update for the Sprint HTC 10 was for 2.51.651.31
You can download the RUU.exe directly from HTC for it, or you could check for updates in settings > about for the OTA
Here's a link for the RUU.exe Scroll down to the "Manual System Update Instructions" and read them. The download is at the end of the instructions.
If you would prefer to flash the RUU via your SD card, or you don't have a Windows computer (you need one for the .exe), let me know and I'll extract the ROM.zip (RUU.zip) for you so you can flash it that way. You could also probably just find the .zip with a Google search.
EDIT: Apparently Sprint has released Oreo via OTA, but there isn't an RUU for it yet

Cool it's already S-Off, Unlocked. I think it's an "HTC 10 Unlocked/Developer" but it's hard to confirm a matching RUU with the 2PS6400 model number.
It was factory sealed. But I still don't know what RUU's are safe to use with it.
https://c1.staticflickr.com/1/795/39021848390_abec02a7e9_c_d.jpg

mswlogo said:
Cool it's already S-Off, Unlocked. I think it's an "HTC 10 Unlocked/Developer" but it's hard to confirm a matching RUU with the 2PS6400 model number.
It was factory sealed. But I still don't know what RUU's are safe to use with it.
https://c1.staticflickr.com/1/795/39021848390_abec02a7e9_c_d.jpg
Click to expand...
Click to collapse
Hmmm, well 2PS640000 is Sprint's MID so you should be careful with that. In general flashing, GSM firmware to a CDMA phone can be dangerous and lead to a brick. There is a way to convert the HTC 10, but I'm not up to speed on it. Since your phone is S-Off I have a feeling someone might have done that. You could try to do an ESN check with the IMEI and see what that brings up as far as what is was originally.
US Unlocked's MID is 2PS650000, and with your current MID you wouldn't be able to flash a US Unlocked RUU

xunholyx said:
Hmmm, well 2PS640000 is Sprint's MID so you should be careful with that. In general flashing, GSM firmware to a CDMA phone can be dangerous and lead to a brick. There is a way to convert the HTC 10, but I'm not up to speed on it. Since your phone is S-Off I have a feeling someone might have done that. You could try to do an ESN check with the IMEI and see what that brings up as far as what is was originally.
US Unlocked's MID is 2PS650000, and with your current MID you wouldn't be able to flash a US Unlocked RUU
Click to expand...
Click to collapse
Nobody did anything to it. He sold 60 of them and it was clearly factory sealed. I see it mentioned a lot when googling around with other people just as puzzled exactly what it is. It's some sort of developer phone.
Someone had a 2PS500 as well that sounded identical. It had S-Off and same bare bones Sprint firmware version.
Ting says it will activate. But it says no on other carriers. I don't care though, but if I ever sold it, it looks like Ting (at least) would work.
It would not let the Unlocked ( *.617.*) RUU Run firmware flash.
The current firmware it had is 2.42.651.66 which is a Sprint Variant.
The CID is set to 1111111
So I tried the Sprint 2.51.651.31 RUU update and it flashed fine. And now has all the Sprint Garbage on it. I don't care. I now know what I can flash to it or not.
It still shows S-Off and Unlocked and Official after Sprint RUU.
It would be nice to know if I could safely flash the Oreo Sprint RUU (which I highly suspect will also flash fine once released) and then go BACK to the Nougat Sprint one as needed back and forth.
Since it's S-Off etc. It would be handy to be to test Android 7 and 8 with one phone.
If I bricked it, I can return for 30 days. So I rather brick it now than later

I took a shot at updating to Android 8 OTA and it worked fine. Will test if I can flash back to Android 7 with the same RUU I used above.
I can't get a very good GPS lock on this thing. Every other deactivated phone I have can get a good lock.

sounds a bit like mine... a 2PS6500, came pre-Soff with SuperCID 111111 and MID converted to 2PS6200... had Nougat WWE.401 installed & GPS was great.
once i took the OTA to Oreo, i now have issues with GPS, as I can see all the satellites, but can't get any GPS-lock at all anymore

I can still get a gps lock just not a great one and sluggish to get a lock.

Tried flashing back to Android 7 with the RUU (I used earlier), no go. Once Android 8 is on their seems no easy way of going back and I'm not gonna try manually doing it as I'll brick it for sure.
Gonna probably send it back. I was willing to live with marginal GPS (which I need for my app debug) but was going to keep it if I could easily switch between Android 7 and 8 (and back).
But it doesn't look that way.
Charger just died too.

kimba99 said:
sounds a bit like mine... a 2PS6500, came pre-Soff with SuperCID 111111 and MID converted to 2PS6200... had Nougat WWE.401 installed & GPS was great.
once i took the OTA to Oreo, i now have issues with GPS, as I can see all the satellites, but can't get any GPS-lock at all anymore
Click to expand...
Click to collapse
Did you find a solution?
I think I have the same phone from ebay - pre-Soff Sprint that was converted.
And no GPS lock. (running Oreo US Unlocked.)

JohnSoong said:
Did you find a solution?
I think I have the same phone from ebay - pre-Soff Sprint that was converted.
And no GPS lock. (running Oreo US Unlocked.)
Click to expand...
Click to collapse
unfortunately no... still trying to hunt for a solution. so yours was a 2PS6400 before... sprint? mine was a 2PS6500 though, as written on its backside (XC edition with 64GB internal btw)

mswlogo said:
Tried flashing back to Android 7 with the RUU (I used earlier), no go. Once Android 8 is on their seems no easy way of going back and I'm not gonna try manually doing it as I'll brick it for sure.
Gonna probably send it back. I was willing to live with marginal GPS (which I need for my app debug) but was going to keep it if I could easily switch between Android 7 and 8 (and back).
But it doesn't look that way.
Charger just died too.
Click to expand...
Click to collapse
Just a follow up. I sent mine back. Got a new real Verizon one for $200.00 on eBay (had no box but it looks new with fairly recent build date too). Works perfect, including GPS without being activated.
I had to manually flash it to the last Android 7 update via adb/fastboot couldn't do it OTA (WIFI) which I thought was a little odd.