Hey Guys,
Before I decided to do this post I looked around A LOT, for roughly over 2 weeks in order to get my HTC back to stock firmware. I'll try to break it down as much as possible without having too much writing on the screen.
The original issue:
Gave my wife the HTC m8 because she fell in love with the phone. The phone is unlocked however its the unlocked version from Vodaphone. When we inserted her sim card, she could do everything except send receive mms and browse internet because Voda APN settings were locked down and were overwriting her Lebara APN settings. I tried many methods to get it to work without rooting and it still would not work. Eventually looking around, I found that I had to root the phone, install some applications to remove the locked APN.
The issue aftewards.
I after soo many attempts finally rooted the phone, only to find out that every method to remove APN did not end up working. To some miracle we reinserted the APN settings for lebara again and it started working. HOWEVER, this time around she could not send or receive any attachment from any application(some examples, Whatsapp, Viber, Mail).
Troubleshooted and nothing worked. My wife became over it and gave the phone back to me. I wanted to bring it back to stock firmware and do update to latest firmware.
Searching for the stock APN for HTC VODAP021 is a nightmare. Hardly anywhere to be seen. Eventually after many attempts at bringing this thing back to life, it corrupted the original back up file I had of the stock firmware and whenever I would revert to that backup, 1 issue after the other made the phone useless and the back up useless.
Eventually found a thread on XDA with a guy who had a VODAP021 with MID: 0PB1100 which fits the description of the get var information i got from the phone. I finally got a working rom, only to find that the rom is a telstra one and not the original vodaphone one. This didnt affect the phone in anyway except for the fact that I was stuck on AOS4.4.4 and that OTA would download but not install at all.
What Im looking for.
I just want to get this phone back to its original stock firmware so that I can at least get the OTA and use it again per normal.
Phone Info:
MID: 0P6B11000
CID: VODAP021
Baseband: 1.26.21331147A1.16G
Bootloader: 3.19.0.000 S-ON
Any help is really most appreciated, and once the issue is resolved, maybe the article will help many others who want to revert to stock with VODAP021.
My phone has the same CID number, when I wanted to upgrade to lollipop (when you have S-ON you can only upgrade firmware through OTA) all I did was flash clockworkmod recovery then restore the nandroid backup from [http://forum.xda-developers.com/showthread.php?t=2701376] for CID: VODAP021 (you can find it under stock nandroid backups, all other CID), there should only be one, then flash the stock recovery for 1.12.710.17. When you boot back up, your phone will be stock, unrooted and will be able to receive OTA`s.
Just be warned, if you are on a higher software version than 1.12.710.17, then you`re WiFI will not work due to firmware mismatching but you can still download the OTA through USB internet pass through and once updated, it will work again, hope this helps.
ryanjsoo said:
My phone has the same CID number, when I wanted to upgrade to lollipop (when you have S-ON you can only upgrade firmware through OTA) all I did was flash clockworkmod recovery then restore the nandroid backup from [http://forum.xda-developers.com/showthread.php?t=2701376] for CID: VODAP021 (you can find it under stock nandroid backups, all other CID), there should only be one, then flash the stock recovery for 1.12.710.17. When you boot back up, your phone will be stock, unrooted and will be able to receive OTA`s.
Just be warned, if you are on a higher software version than 1.12.710.17, then you`re WiFI will not work due to firmware mismatching but you can still download the OTA through USB internet pass through and once updated, it will work again, hope this helps.
Click to expand...
Click to collapse
I followed that method before as well. however in CWM when i got to restore and find the location of that file, it finds the restore but fails to restore everytime. I'll back my stuff up and try again. Maybe I missed a step, because I went back to that thread many times and downloaded that file twice thinking maybe first time something went wrong and it wouldn't restore.
If your wife loves the phone, let me suggest you S-off and switch to WWE. That should put an end to the fishiness in the carrier supplied firmware, and since the device was otherwise working well with your desired carrier, would completely resolve the problem.
It is not uncommon for carriers to muck with the default install to make what you are doing a PITA...
Does it start restoring then fail? you have to turn off md5 check and unzip the file before copying it onto your sd. If not, I`ve had corrupted downloads before, you can try downloading the backup again and attempting the restore again.
ryanjsoo said:
Does it start restoring then fail? you have to turn off md5 check and unzip the file before copying it onto your sd. If not, I`ve had corrupted downloads before, you can try downloading the backup again and attempting the restore again.
Click to expand...
Click to collapse
Hey man, sorry for such a belated post. I finally got around to doing it all again. and so far OTA has worked to update to 4.4.2 but nothing for 5.0.1. has there been an OTA available for 5.0.1 for AUS Voda? and funny thing is, after OTA the wifi stopped working.. Before OTA wifi worked fine. weird
Related
Hello,
I own a HTC One V that is t-mobile(germany)-branded.
I s-off'ed it using the official HTC procedure and then rooted it using this guide (theandroidsoul.com/root-one-v).
Ever since then, I am having connection problems, as in, no connection unless I reboot it. This especially occurs while talking on the phone,
but also at random. I then attempted to apply the RUU_PRIMO_U_ICS_40A_HTC_Europe_2.08.401.2_Radio_20.72.30.0833U_3831.17.00.18_M_release_263376_signed.exe following tutorials
-> first, locking the bootloader, then flash the recovery, then apply the RUU - flashing the recovery worked, however, the RUU failed because the CID does not match. Changing to SuperCID does not seem to be possible at the moment.
Plus, ever since I flashed the RUU recovery, I can't change sounds anymore, so whenever I try to change alarms/ringtones/notification sounds, the personalizer oder settings application crashes.
In order to check if the connection issue is related to the rooting process (and if it isn't, to get it replaced by t-mobile) I need to revert to the stock t-mobile ROM, however, I can't find any.
Is there any other way to solve this dilemma or can you help me?
Chikari said:
Hello,
I own a HTC One V that is t-mobile(germany)-branded.
I s-off'ed it using the official HTC procedure and then rooted it using this guide (theandroidsoul.com/root-one-v).
Ever since then, I am having connection problems, as in, no connection unless I reboot it. This especially occurs while talking on the phone,
but also at random. I then attempted to apply the RUU_PRIMO_U_ICS_40A_HTC_Europe_2.08.401.2_Radio_20.72.30.0833U_3831.17.00.18_M_release_263376_signed.exe following tutorials
-> first, locking the bootloader, then flash the recovery, then apply the RUU - flashing the recovery worked, however, the RUU failed because the CID does not match. Changing to SuperCID does not seem to be possible at the moment.
Plus, ever since I flashed the RUU recovery, I can't change sounds anymore, so whenever I try to change alarms/ringtones/notification sounds, the personalizer oder settings application crashes.
In order to check if the connection issue is related to the rooting process (and if it isn't, to get it replaced by t-mobile) I need to revert to the stock t-mobile ROM, however, I can't find any.
Is there any other way to solve this dilemma or can you help me?
Click to expand...
Click to collapse
Now just hold on a sec. You can't S-Off at the moment, as far as I know, and there is no HTC software for it. You just unlocked the bootloader, to give yourself some priviledges, but that is not S-Off, so you cannot change the CID of the phone (or debrand it).
Stock ROM for T-Mobile is not available at the moment (or at least for the public) Ask Football for it, but it will cost some EUR for you.
If the RUU sees anything wrong with the phone (including CID) it won't even start flashing the device, so it cannot do any harm for you. But since you unlocked BL I suggest to install custom firmware to see if anything is wrong with the hardware. Just be sure to do a nandroid backup before, so you can revert to the "stock" if possible.
Hi all,
so I got my M8 like three weeks ago and made the ultimate mistake of not backing up MY factory ROM before flashing stuff. I went ahead and, following a guide from 'teh internets', turned my phone into a Google Play Edition after a successful S-Off with SunShine. About a week later, I started missing some Sense features and tried to revert back to stock which proved difficult at first due to partition size issues. Finally, I was successfully following a mixture of several guides in this very forum, flashing different combinations and versions of stock ROMs, firmwares and recoveries. I'm on Sense again. Last thing I can't get rid of is a message in HTC Tell that's talking about a testing device and how I could not turn off HTC Tell for that reason.
Long story short, I do now have a phone that reads:
Code:
*** Software status: Official ***
*** UNLOCKED ***
M8_UL PVT SHIP S-OFF
CID-HTC__102
HBOOT-3.19.0.0000
RADIO-XXX
OpenDSP-XXX
OS-3.28.401.7
eMMC-boot 2048MB
Oct 10 2014,00:20:35.0
Unfortunately, I do not exactly remember which Recovery I flashed last. I'm pretty sure it was one from the Stock Backup & OTA Collection thread. If I go into recovery, I get a red triangle and nothing happens.
Now for my question, I want some features of Lollipop really bad and I know HTC is going to come out with their Lollipop-Sense in about two weeks. I would gladly wait and go for it instead of starting over and turn my phone into a GPE again. Question is, will I get the Sense OTA or is there anything that will keep me from it?
Thanks a lot for reading and any information I got (and hopefully will get in the future) from the folks on this awesome forum!
If you are on the appropriate stock ROM for your CID, and corresponding stock recovery, you will get the OTA.
---------- Post added at 09:47 AM ---------- Previous post was at 09:40 AM ----------
jndvid said:
Unfortunately, I do not exactly remember which Recovery I flashed last. I'm pretty sure it was one from the Stock Backup & OTA Collection thread. If I go into recovery, I get a red triangle and nothing happens.
Click to expand...
Click to collapse
Red triangle is stock recovery. However, its not clear whether its the right stock recovery. You need to be on the stock ROM for your CID, and the recovery needs to be the one that matches that software number. Just find the stock ROM (and corresponding recovery) for your CID on the following thread.
http://forum.xda-developers.com/showthread.php?t=2701376
There is no harm in restoring the correct stock ROM and recovery over whatever you have now (whether the current state is correct for your CID or not). But being on the correct stock ROM and recovery will put you in the right place for OTA.
Thanks for the explanation.
So it is safe to assume that if I flash TWRP now and restore the 3.28.401.6 nandroid and recovery from this thread, I should A) get the OTA from .6 to .9 and later on B) the Sense-Lollipop OTA?
Sorry for the redundancy of my question but without a speedy internet connection, downloading ROMs is a time-consuming project, so I want to get it right the first time now.
jndvid said:
So it is safe to assume that if I flash TWRP now and restore the 3.28.401.6 nandroid and recovery from this thread, I should A) get the OTA from .6 to .9 and later on B) the Sense-Lollipop OTA?
Click to expand...
Click to collapse
If you restore to .6, it won't install the .6 OTA since its already on that version. But yes, it should install any "more up-to-date" OTAs (and then any future OTAs as they are released) in sequence once you return to stock and check for updates.
Thanks again. I will report back after flashing.
Well, it worked - I think. However, a little more research showed that the red text in HTC Tell is present because I unlocked my phone, particularly the bootloader, via HTCDev. I will consider to revert that change in the future.
I restored (via TWRP) the stock 3.28.401.6 and flashed the corresponding stock recovery. Unfortunately, no update is to be found yet (according to the OTA collection, there should be an update from .6 to .9 which I hoped to get automagically or on manual query in phone settings).
For the time being, I can download the OTA myself from the awesome collection and then update manually through stock recovery, I suppose.
jndvid said:
Well, it worked - I think. However, a little more research showed that the red text in HTC Tell is present because I unlocked my phone, particularly the bootloader, via HTCDev. I will consider to revert that change in the future.
Click to expand...
Click to collapse
The device will come up as a "test device" since its s-off.
jndvid said:
I restored (via TWRP) the stock 3.28.401.6 and flashed the corresponding stock recovery. Unfortunately, no update is to be found yet (according to the OTA collection, there should be an update from .6 to .9 which I hoped to get automagically or on manual query in phone settings).
Click to expand...
Click to collapse
I'm not that familiar with the WWE updates, as its not my version. So I don't know of the .7 and .9 updates deployed to all folks in all regions that have the WWE version, etc. You might check with folks that know more about the WWE updates.
HELP, I've bricked my phone.
I'll try to be as brief as possible.
I had android 5.0.1 (4.16.401.10). unlocked bootloader, installed TWRP, rooted.
a few months later today, my phone had an OTA update notification (4.16.401.13), tried to do it, failed and it kept sending me to TWRP.
Googled it, people said I should restore the stock recovery, I did, tried to install the OTA again. phone got stuck on splash screen.
From there I have been online for hours trying to fix this but nothing. (there has been many flashing attempts, some fail some success) so the phone is pretty much a mess now.
My question is, what's the easiest way (if there is) to just restore the phone to stock firmware? I don't care if it's going to be rooted or not, I don't care if It's going to be wiped, I just need it to work.
Currently I have (relocked) bootloader, S-On
Thanks.
Same problem here, Got this update yesterday and stuck at the splash screen.
rooted, S-on, stock recovery
tried everything from changing recovery, FUU, RUU, nothing worked
Fortunately, I have full NAND backup months ago ( old,but better than nothing), restore it, update the new update and everything looks ok so far.
I suspect its related to the xposed relared problem as the old backup its not installed.
AHOHA said:
Fortunately, I have full NAND backup months ago ( old,but better than nothing), restore it, update the new update and everything looks ok so far.
Click to expand...
Click to collapse
Sorry if this is a noob question, but how can I do that? is there somewhere where I can download backups and restore them on my phone? And if so, will I need anything like an S-Off or something?
Because I've tried everything else I think, I tried RUU (both from PC or from bootloader, and with both Unlocked and Relocked bootloader) and nothing seems to work.
Hi there, got the same problem just dont have nan backup so i'm stucked.
Phone is rooted, unlocked, s-on
cid: VODAP001
mid: 0P6B10000
got latest twrp.
Tried to flash 2 (diferent date builds) roms acording to my cid, NO LUCK,
tried ruu - no luck
read hundrets of pages and found only one thing that I need is S-OFF, but how can I do s-off when my phone doesnt boot up?
pls help
mizaras said:
Hi there, got the same problem just dont have nan backup so i'm stucked.
Phone is rooted, unlocked, s-on
cid: VODAP001
mid: 0P6B10000
got latest twrp.
Tried to flash 2 (diferent date builds) roms acording to my cid, NO LUCK,
tried ruu - no luck
read hundrets of pages and found only one thing that I need is S-OFF, but how can I do s-off when my phone doesnt boot up?
pls help
Click to expand...
Click to collapse
I finally got mine to work today!!
What worked with me is this:
I got the RUU Zip file for my CID, renamed it to 0P6BIMG.zip , and copied it to the root of my SD Card (using an adapter or using TWRP to mount it)
then I flashed the stock recovery for my phone, then RELOCK your bootloader (fastboot oem lock)
Onve you've done all that just put the SD card in your phone and boot it in bootloader mode (Vol Down + Power) and it should detect the 0P6BIMG.zip file automatically and ask you if you want to update it.
P.S: I have S-On and it worked.
I hope this helps.
Hey so here's my situation:
Installed the CM Nightly on my AT&T One M9, didn't like it, so I tried to revert to stock. I didn't want to pay $25 to S-OFF so I just tried installing various RUUs, but none would work. I read somewhere that I needed to relock my bootloader in order for the RUUs to work, so I did that, and now my phone just boots to Recovery Mode. I've tried installing AT&T RUU 2.6.502.16 (which didn't work because my phone is on a more recent firmware) and reinstalling 2.11.502.18/flashing its 0PJAIMG.zip (which didn't work because it's apparently broken). I've even tried installing T-Mobile's 2.11.531.19 RUU, which of course didn't work because my CID doesn't match and I can't change it because I'm S-ON.
I realize I went about this very badly almost from the start--no stock backup in TWRP, etc. This is my first Android phone so I've been learning this as I go and I was a bit sloppy.
I'm pretty sure I'm screwed, at least until a new update comes out or the current AT&T RUU is fixed, but I'm wondering if there's something else I can try. Any ideas? Thanks.
StageProps said:
Hey so here's my situation:
Installed the CM Nightly on my AT&T One M9, didn't like it, so I tried to revert to stock. I didn't want to pay $25 to S-OFF so I just tried installing various RUUs, but none would work. I read somewhere that I needed to relock my bootloader in order for the RUUs to work, so I did that, and now my phone just boots to Recovery Mode. I've tried installing AT&T RUU 2.6.502.16 (which didn't work because my phone is on a more recent firmware) and reinstalling 2.11.502.18/flashing its 0PJAIMG.zip (which didn't work because it's apparently broken). I've even tried installing T-Mobile's 2.11.531.19 RUU, which of course didn't work because my CID doesn't match and I can't change it because I'm S-ON.
I realize I went about this very badly almost from the start--no stock backup in TWRP, etc. This is my first Android phone so I've been learning this as I go and I was a bit sloppy.
I'm pretty sure I'm screwed, at least until a new update comes out or the current AT&T RUU is fixed, but I'm wondering if there's something else I can try. Any ideas? Thanks.
Click to expand...
Click to collapse
I downloaded and flashed the 2.11.502.18 ruu from the HTC website with no problem. Ate you getting an error?
Edit: in my experience, if an ruu.exe starts to run and then never does (like you get the spinning wheel for a minute and then nothing) it's either a bad download or antivirus is blocking the file. But just to repeat...the exe on the HTC website works fine. I used it about three weeks ago.
Hm. Out of the myriad RUU.exes I've tried the most recent AT&T one was the only one I couldn't get to start, and when I tried installing it via .zip it would just restart the phone and nothing else. That in combination with other posts I've seen on this forum saying it's borked (although I might have misread the numbers/misinterpreted the jargon) just lead me to think it was broken. I'll redownload and try again. Thanks!
Edit: Well, it worked! I don't know what I was doing wrong. Thanks a lot!
Hi,
I have bought a used HTC M9 on Kijiji (I'm in Québec, Canada)
It must be faulty because it kept randomly restarting (sometimes once, sometimes for periods of 20 minutes, which made it hardly usable)
After clearing the cache partition and factory resetting it a couple times, I decided to flash it.
What I did:
- enabled the developer mode and USB debugging
- unlocked the bootloader
- flashed TWRP
- flashed SuperSU v2.74-2
Now, Android won't boot. When I start the phone, I see the green HTC logo on a white background with a red text saying it's a development build, then after about 10 seconds it restarts to the same screen. Over and over again.
In download mode, I am able to see the device with fastboot, but adb does not show anything.
In recovery mode, it's the opposite.
The phone is still S-ON so I have tried S-OFF methods (moonshine and firewater), but the fact of not having fastboot AND adb working at the same time made them fail.
Here's my phone info:
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) imei: ************
(bootloader) version-main: 3.38.666.2
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440801_96.01.51207G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: BM___001
Any help would be greatly appreciated...
Thanks in advance!
youre flashing the wrong superuser. Try 2.64. And btw, moonshine and firewater wont work. The only way to s off is sunshine
Roobwz said:
youre flashing the wrong superuser. Try 2.64. And btw, moonshine and firewater wont work. The only way to s off is sunshine
Click to expand...
Click to collapse
Thanks for your reply.
I used Squabbi's HTC one M9 Toolkit to flash
It does not offer 2.64, but 2.52 and 2.66 are the closest ones. Both in BETA as well.
Should I try one of them?
zzzer51 said:
Thanks for your reply.
I used Squabbi's HTC one M9 Toolkit to flash
It does not offer 2.64, but 2.52 and 2.66 are the closest ones. Both in BETA as well.
Should I try one of them?
Click to expand...
Click to collapse
You shouldnt use toolkits imo, no offence squabbi. You should just download the 2.64 file from chainfires thread and flash it in twrp. It isnt harder than that. Btw 2.64 was the only superSu that worked for me
Ok, I have been able to find a zip for 2.64 and will install it with TWRP when my phone's battery is drained out (it tried to boot on the OS and is currently stuck on the HTC logo...)
I have also tried installing files directly from the microSD
downloaded from:
https://docs.google.com/spreadsheets/d/1ZaiJ3F_f76sVa4daU5H62OYi5Bj23LEBBv4xDTQ8y-M/pubhtml
http://androidruu.com/index.php?developer=M9
using fastboot flash zip zipfile.zip
but I get errors like
9 RU_SECURITY_FAIL
android-version information is missing
I'm not sure I'm trying to flash the right file anymore...
EDIT:
I have tried to flash both 0PJAIMG_HIMA_UL_L50_SENSE70_ATT_BM_1.32.666.30 and 0PJAIMG_HIMA_UL_L50_SENSE70_ATT_BM_1.32.666.6 files by going to TWRP -> Install but I get the error message 'zip file is corrupt!' every time...
And when I try to flash with fastboot, I get "Invalid sparse file format at header magi"
EDIT2:
Ok, I have made some progress!
What I did:
1/ Downloaded the image from this page http://forum.xda-developers.com/one-m9/general/guide-return-to-stock-canadian-htc-one-t3108236
2/ Formated my 8GB microSD card to exFAT (because the system image file is over 4GB)
3/ Extracted the system.emmc.win and boot.emmc.win files to the microSD card in path: E:\TWRP\BACKUPS\<myPhoneIDThatFastbootCanGiveYouIfYouTypeFastbootDevices>\Stock Bell
4/ Started the phone in recovery mode (TWRP)
5/ Tapped on Restore
6/ Selected the two files and hit Restore
7/ Performed a Factory reset (through TWRP, by tapping Wipe)
8/ Rebooted the phone in System mode
And Android started!
I'm not 100% sure it fully works as I haven't been able to finish the configuration yet (I don't have access to a wifi network where I am) so I will do that when I get home tonight.
But it looks a lot better than these past few days.
In the meantime, a quick question:
My bootloader is still unlocked. Can I leave it like that or should I re-lock it?
Thanks
No need to relock it unless you plan on updating. There is conflicting information on whether a locked bootloader is absolutely necessary.. Maybe someone could chime in?.
Otherwise it's safe to leave it and probably best to.
Beamed in by telepathy.
shivadow said:
No need to relock it unless you plan on updating. There is conflicting information on whether a locked bootloader is absolutely necessary.. Maybe someone could chime in?.
Otherwise it's safe to leave it and probably best to.
Beamed in by telepathy.
Click to expand...
Click to collapse
You can OTA with an unlocked bootloader but you need to be 100 % stock. It's always best to not relock bootloaders as if you get into problems, you'll not be able to flash stuff. The only time a locked bootloader is needed is when running RUU.exe while S-On. The SD card method works with an unlocked bootloader. I'd recommend to leave it unlocked
Thanks for the advice!
Ok so I have been able to boot the phone and set it up with my GMail account using wifi.
However, now:
1/ I have a red text mentioning that the build the phone is running is meant for development purposes only. It does not really matter to me, I just thought I'd mention it.
2/ There is no network service. I have tried my girlfriend's SIM card as well, but nothing happens. It doesn't say it can't register the SIM card nor say that the SIM card is not detected. Just nothing.
I tried changing the radio mode to GSM auto using *#*#4636#*#*, but when the phone reboots, it's back to WCDMA
3/ No IMEI (*#06# shows an empty window)
4/ It still randomly reboots as before. I was able to save a 'system crash' error report that popped up after a reboot. Please find it here: https://docs.google.com/document/d/13QBaeA1_Vo-b9mndffvbulG8epMq42Pnguawa2GcQTA/edit?usp=sharing
5/ When I press the physical button to lock the screen, it makes it go black then reboot, 50% of the time
zzzer51 said:
Thanks for the advice!
Ok so I have been able to boot the phone and set it up with my GMail account using wifi.
However, now:
1/ I have a red text mentioning that the build the phone is running is meant for development purposes only. It does not really matter to me, I just thought I'd mention it.
2/ There is no network service. I have tried my girlfriend's SIM card as well, but nothing happens. It doesn't say it can't register the SIM card nor say that the SIM card is not detected. Just nothing.
I tried changing the radio mode to GSM auto using *#*#4636#*#*, but when the phone reboots, it's back to WCDMA
3/ No IMEI (*#06# shows an empty window)
4/ It still randomly reboots as before. I was able to save a 'system crash' error report that popped up after a reboot. Please find it here: https://docs.google.com/document/d/13QBaeA1_Vo-b9mndffvbulG8epMq42Pnguawa2GcQTA/edit?usp=sharing
5/ When I press the physical button to lock the screen, it makes it go black then reboot, 50% of the time
Click to expand...
Click to collapse
did you restore the correct backup for your firmware?? ex 3.35,401.12 needs 3.35.401.12 and not 3.35.701.12. Everything needs to match. This might also solve your issues.
Roobwz said:
did you restore the correct backup for your firmware?? ex 3.35,401.12 needs 3.35.401.12 and not 3.35.701.12. Everything needs to match. This might also solve your issues.
Click to expand...
Click to collapse
I don't think I did...
The main-version that shows in download mode is 3.38.666.2 ... whereas the version of the backup I restored is 1.32.666.30.
I have been searching for a while, but have no idea where to find the right rom... Should I send an email to Bell?
zzzer51 said:
I don't think I did...
The main-version that shows in download mode is 3.38.666.2 ... whereas the version of the backup I restored is 1.32.666.30.
I have been searching for a while, but have no idea where to find the right rom... Should I send an email to Bell?
Click to expand...
Click to collapse
That's why you are getting these issues. You can try out the RUU service. Keep in mind that it costs around 20$, but at least you'll get a phone that's 100 % stock again. Either that or getting s off and downgrade firmware with a RUU
Skickat från min HTC One M9 via Tapatalk
Roobwz said:
That's why you are getting these issues. You can try out the RUU service. Keep in mind that it costs around 20$, but at least you'll get a phone that's 100 % stock again. Either that or getting s off and downgrade firmware with a RUU
Click to expand...
Click to collapse
Thanks for the suggestion, I did not know that service.
I always prefer doing things on my own, but I might have to use them because I have already spent around 20 hours trying to fix my phone...
That is, if we are sure there is absolutely no other way to find the RUU for free?
zzzer51 said:
Thanks for the suggestion, I did not know that service.
I always prefer doing things on my own, but I might have to use them because I have already spent around 20 hours trying to fix my phone...
That is, if we are sure there is absolutely no other way to find the RUU for free?
Click to expand...
Click to collapse
The service is remotely done over the computer, so you'll see everything that happens.
Well, if you find a RUU that matches everything (cid, mid and firmware), you'll be able to do it for free. Either that or s off (25$ as well), and you'll be able to convert your phone into a world wide edition model or dev edition. S off opens up a whole new world for you. Ex - you can flash exactly what you want (no need for Canadian firmware) and you're able to downgrade etc. The rest is up to you.
Roobwz said:
Well, if you find a RUU that matches everything (cid, mid and firmware), you'll be able to do it for free.
Click to expand...
Click to collapse
I found the version I was looking for from this link: http://www.htcdev.com/devcenter/downloads/P100
However, it's only 206MB, so I'm guessing it's not a firmware... what do I need to do with it?
EDIT: It's .tar.gz files. apparently source code
zzzer51 said:
I found the version I was looking for from this link: http://www.htcdev.com/devcenter/downloads/P100
However, it's only 206MB, so I'm guessing it's not a firmware... what do I need to do with it?
EDIT: It's .tar.gz files. apparently source code
Click to expand...
Click to collapse
That's kernel source I believe. Your only luck would be flippys thread in the general section
Skickat från min HTC One M9 via Tapatalk
The latest news:
I went S-OFF yesterday with Sunshine.
I was able to install Cyanogenmod, which looked cool, but I still did not have any network service.
So, I flashed an Bell stock firmware, version 1.xxx
Still did not have network.
I let Android download and install the update for version 2.xxx
When it finished, I got my network back!
Now, I would like, but am afraid to, update firmware to version 3.xxx or try Cyanogenmod again.
But, obviously, I'm afraid that I won't have any service anymore...
Anyways, thanks a lot guys for your help!
zzzer51 said:
The latest news:
I went S-OFF yesterday with Sunshine.
I was able to install Cyanogenmod, which looked cool, but I still did not have any network service.
So, I flashed an Bell stock firmware, version 1.xxx
Still did not have network.
I let Android download and install the update for version 2.xxx
When it finished, I got my network back!
Now, I would like, but am afraid to, update firmware to version 3.xxx or try Cyanogenmod again.
But, obviously, I'm afraid that I won't have any service anymore...
Anyways, thanks a lot guys for your help!
Click to expand...
Click to collapse
I would recommend upgrading to 3.xx for several reasons like doze, custom ROMs that are up to date etc. If you did the OTA from 1.x to 2.x, you shouldn't have any problems with the OTA to 3.x. in the worst case, just re flash the RUU or just convert the device to an European version.
Heyyy, it's me again
So, Android downloaded the update, but when I try to install it, it reboots to download mode.
Also, I cannot access the Recovery Mode.
I tried flashing TWRP 3.0.2.0 with fastboot a couple times, but when I try to access the Recovery Mode from the bootloader, I get :
Code:
Failed to boot to recovery mode
Press volume up or down to back to menu
Anyone knows why?
I am S-OFF and my bootloader is UNLOCKED
Thanks
zzzer51 said:
Heyyy, it's me again
So, Android downloaded the update, but when I try to install it, it reboots to download mode.
Also, I cannot access the Recovery Mode.
I tried flashing TWRP 3.0.2.0 with fastboot a couple times, but when I try to access the Recovery Mode from the bootloader, I get :
Code:
Failed to boot to recovery mode
Press volume up or down to back to menu
Anyone knows why?
I am S-OFF and my bootloader is UNLOCKED
Thanks
Click to expand...
Click to collapse
what was flashed prior to the OTA? OTAs fail if you arent 100% stock.
Roobwz said:
what was flashed prior to the OTA? OTAs fail if you arent 100% stock.
Click to expand...
Click to collapse
A looooot of stuff!
But even after flashing the original HTC recovery again, I get the same message.
And I can't access the recovery menu either.
Thanks