WHAT THIS IS FOR:
This is for those of you that upgraded to the newest rogers rom, and caught yourselves with an unrooted device.
IMPORTANT NOTE: Emergency phone calls are broken in this version (the whole reason for the upgrade), so see to it that you switch to a rom / boot.img that doesn't suck. (thanks a lot rogers >_>)
http://haykuro.polygonize.com/ROGERSDREAM.nbh.zip
Steps to take:
1. Download the file
2. Extract and rename to DREAIMG.nbh
3. Place on root of SD card (your SD card has to be formatted as FAT32 if it fails to find it in the next step!)
4. Power off, hold camera button, power on. This will boot into SPL and prompt you to install. Proceed.
5. After your phone is done flashing, it will prompt you to press another key to reboot the phone. Do so.
6. Use flashrec, and follow procedures to root again.
Haykuro strikes again! I didnt put the update on but im sure this will be put to good use.
wow dat was quick, so downgrade and follow the rooting process again is it ?
Gonna be the first guinea pig then...
------
UPDATE: REJECTED!!! Shiat!
Message:
"Main Version is older!"
Update Fail!
Do you want to reboot device?
<ACTION> Yes
<POWER> No
Btw, I think someone already tried this.
Somehow, it's got to be higher than the build 1.89 that Rogers/HTC gave us.
Any other ideas?
What is this supposed to do? Should this be applied if we've already updated to the new Rogers rom?
What will this do if we haven't updated yet, but are still using something like CM 4.2.13?
Sejanus said:
What is this supposed to do? Should this be applied if we've already updated to the new Rogers rom?
What will this do if we haven't updated yet, but are still using something like CM 4.2.13?
Click to expand...
Click to collapse
if u havent update to the new rogers rom and having CM 4.2.13 then forget abt this,
if u flash rogers rom u will lose your root as i did
so better not to if u like the root, cos there is nothing special with the rogers update,
but the Magic update is awesome
dotster said:
Gonna be the first guinea pig then...
------
UPDATE: REJECTED!!! Shiat!
Message:
"Main Version is older!"
Update Fail!
Do you want to reboot device?
<ACTION> Yes
<POWER> No
Btw, I think someone already tried this.
Somehow, it's got to be higher than the build 1.89 that Rogers/HTC gave us.
Any other ideas?
Click to expand...
Click to collapse
I get the same thing! arrgghgh
Haykuro: can we use goldcard for this???
dotster said:
Gonna be the first guinea pig then...
------
UPDATE: REJECTED!!! Shiat!
Message:
"Main Version is older!"
Update Fail!
Do you want to reboot device?
<ACTION> Yes
<POWER> No
Btw, I think someone already tried this.
Somehow, it's got to be higher than the build 1.89 that Rogers/HTC gave us.
Any other ideas?
Click to expand...
Click to collapse
Get the same thing. Thanks for the effort Haykuro. Anything else up your sleeves?
ok update failed
dammm... was hoping for a fix!
Dropped the nbh file in my goldcard....nada....failed the same way.
I even ran the 1.89 RUU and replaced the rom.nbh file in the temp folder with the old one we all downloaded and named it rom.nbh.... just to see what would happen....failed
I'll have to try another goldcard....I might have messed up somewhere.
Can someone please try this with a goldcard and see if it works?
Thanks haykuro for getting on the ball on this....
Rogers.....karma is gonna be a B*&%$......for you guys one day....
I already tried the older rom and it failed. I also tried with a goldcard and got the same response.
maybe I made a booboo, so if someone can make a goldcard image and send it to me ([email protected]) I'll give it another try.
This is my cid:
Code:
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:a32a/cid
0353445355323536802111d32400892e
weird, I have lost all the signal ever since trying to flash the nbh file
copolii said:
I already tried the older rom and it failed. I also tried with a goldcard and got the same response.
maybe I made a booboo, so if someone can make a goldcard image and send it to me ([email protected]) I'll give it another try.
This is my cid:
Code:
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:a32a/cid
0353445355323536802111d32400892e
Click to expand...
Click to collapse
lol I find your signature funny
your the one who chose to run the ruu
you can only blame yourself
also htc makes the software not rogers
alan090 said:
lol I find your signature funny
your the one who chose to run the ruu
you can only blame yourself
also htc makes the software not rogers
Click to expand...
Click to collapse
I actually spoke to HTC customer service on the phone. They said Rogers wanted it this way (a 1.5 build with no other fixes besides the 911 fix). So yes, HTC makes it, but Rogers wanted it this way.
Even without all this, still **** Rogers. They're still spineless sacks of ****.
copolii said:
I actually spoke to HTC customer service on the phone. They said Rogers wanted it this way (a 1.5 build with no other fixes besides the 911 fix). So yes, HTC makes it, but Rogers wanted it this way.
Even without all this, still **** Rogers. They're still spineless sacks of ****.
Click to expand...
Click to collapse
... and that is even though HTC would be perfectly happy to make a 1.6 for them.
I assume that the 1-click-root vulnerability is gone, anybody try it?
Annoyances
So, I called Rogers tech support on Monday morning after they turned off my 3G and told the tech guy there that I've been running a ROM with the 911 fix since last September or so, and could they please turn my 3G back on. He did something on his end to re-provision my phone. I had to take out the battery for a little while and then boot my phone, and 3G came back up for me.
This wasn't good enough for Rogers. They have been sending me two text messages a day (one English and one French) and then calling me (twice) with recorded messages warning me about the 911 problem and that I need to 'upgrade'. This is a serious customer satisfaction issue with me. So, I figured it'd set me back for a few days, but I did the following to downgrade my phone from Cyanogen to the Rogers Donut-Hole release:
1) Installed Windows XP mode on my Windows 7 64 Bit OS, because the HTC Sync program wouldn't work on Windows 7 64-bit.
2) Downloaded and installed the HTC Sync program on my Windows XP virtual machine.
3) Dug around and found an old JACxHERO 1.0 ROM and I flashed it, hoping that the Rogers updater wouldn't detect this as a violation and abort.
4) Rebooted the phone, and joy of joys was able to get HTC Sync to connect to my virtual machine. The JACx HERO ROM has HTC Sync inside it, which was enough to fool the installer.
5) Ran the Rogers downgrader. This ran successfully... I just had to babysit the USB 'Attach' menu. If you're not on a virtual machine, you shouldn't need to worry about it.
6) Now I have the updated Radio image, and a downgraded 1.5 Android image.
I miss 1.6 terribly already. I wonder how long it'll be before Rogers detects that I've performed the upgrade so that I can try out this new Hakuro goodness (thanks Man!) and get my phone to a decent OS again. Anyone know how Rogers is detecting the upgraded version? Are they simply looking at the Radio image version? Or do they also know what OS Build I'm running?
I also upgraded my wife's phone. I hope the SMS and Recorded message abuse will now go away.
My message to Rogers would be: Get out of my life. I already pay you far too many dollars for the privilege of holding and using an HTC Dream on your golden network. It is super nice that you regard my safety above all else, however I have never in my life called 911, and really my safety is not your responsibility. I already know about the 911 bug, and had it fixed before you decided to meddle with all of your Canadian customers by removing their network connectivity and abusing them with myriads of reminders. Get out and stay out of my life!
Have a nice day.
I've tried all the usual methods with fastboot. Flashrec doesn't work. Logging in via adb doesn't give me shell access. Someone's tried the goldcard method.
Sigh.
Haykuro, what was your process for initially rooting the Magic? Didn't we send you one and you had to hook up some wires to it to get some port #s or something? (Sorry, it was long time ago.)
If need be, I'm getting an Magic upgrade once they are in stock and I'd be willing to lend you my Dream to hack at.
Sorry to here that you did that but as of now you are fooked.
There were steps in 1 of the 5 threads that told you how to perform the upgrade without flashing the "perfected perfect" spl but it's too late now.
sorry for your luck.
Same issue as everyone else, unable to flash old image...
My phone has been unusable since the update, reception has dropped to emergency calls only in my house, and 1 bar outside.
Every hour or so I have to reboot the phone, I get some ".process" error that keeps popping up in an infinite loop.
I need the droid from telus to be released, I have to ditch this garbage.
Related
Today I was reminded that being nice to people can pay off! I was lucky enough to get my hands on the new Sprint RUU thanks to syscrasher13!
What is this?
RUU (radio unit upgrade) is the way that our phones are flashed at the factory. It flashes all the factory images on to your phone.
The 1.29 RUU has always been available, however people that purchased phones that came with 1.56 on them were unable to use that RUU: http://geekfor.me/news/sprint-ruu-fails/
This is the updated version for those people that have "with Google" branded phones that came with software version 1.56 on them.
What can I do with it?
You can use this to "unroot" your phone before sending it in for warranty work.
Use it to flash back to stock if you are having any random issues on your phone that you can't fix.
It can 100% flash your phone back to how it came from the factory. As long as your phone turns on at all (even if it's not booting) then you should be able to save it by using this.
This means your phone is virtually unbrickable, unless you go flashing a radio or SPL or something that you shouldn't.
You can flash this on a phone that originally came with 1.29 on it, just know that once you do you will no longer be able to use the 1.29 RUU. You will have to use this one.
How do I use it?
Download the file below and run the exe.
Go in to the folder that the exe created and run ARUWizard.exe
What else do I need to know?
The phone is still rootable. I tested it successfully using the auto-rooter in the pre-kitchen.
Fresh ROM still works just fine (as should any 1.56 based rom)
You will not be able to use the 1.29 RUU after this one, but I don't know of any reason that you would want to
Although some img's in the RUU have different dates than the original it appears that they are identical other than system.img
You don't need to run this unless you are trying to return your phone to stock. You won't get anything special from running it.
Download here: http://geekfor.me/news/sprint_ruu_156/
Thank you so much flipz!! As always sharing the goods with the comunity!!!
Amazing work
thanks for sharing!
appreciate this very much!
thanks flipzmode....always a chance this could come in handy at some point
THANKS! was worried about having a with Google phone until now
thanks flipz
Many thanks!
Now, with this file on hand, I think it might be time to go ahead and root my new phone. Mostly I just want proper control over the device -- not likely to flash any ROMs until they evolve a little more -- but your work looks real solid and I plan on keeping up with it. Good show!
(on a side note, fwiw -- jumping ship from the Touch Pro to the Hero, after being with WinMo since the i730, has been my most satisfying smartphone experience, ever)
Hey, Thanks!
One minor request, though: Could you include the md5 values to your file releases from now on?
While it does not increase security, it gives assurances that the file has not been altered... and it allows us to verify downloaded files.
I think a RUU file deserves this, don't you?
JohnP
Ooops: You did - on this page. Sorry.
johnp2343 said:
Hey, Thanks!
One minor request, though: Could you include the md5 values to your file releases from now on?
While it does not increase security, it gives assurances that the file has not been altered... and it allows us to verify downloaded files.
I think a RUU file deserves this, don't you?
JohnP
Click to expand...
Click to collapse
I've included md5 values on my releases since fresh 1.0. It's not in this post but if you click the link to go to the download page you'll see it there.
This definitely needs to be stickied...I know myself and others have often referenced the RUU in many troubleshooting posts throughout my (admittedly short) stay at xda so far.
Thank Flipz for getting and posting this stuff!
Thanks for this! Looks like we can root non Sprint CDMA Heroes now. (Cellular South, Bluegrass Cellular)
Any idea exactly how we managed to get this? From HTC? From Sprint?
I really want to find one for Cellular South and might as well try for Bluegrass Cellular since it has its own CID as well.
Doesn't look like the different version radio will be an issue, but would be nice to have the RUU around just in case.
johnp2343 said:
Hey, Thanks!
One minor request, though: Could you include the md5 values to your file releases from now on?
While it does not increase security, it gives assurances that the file has not been altered... and it allows us to verify downloaded files.
Click to expand...
Click to collapse
It's been modified, it won't match Sprint's (or HTC's) md5sum in any case. So having the md5sum for this one doesn't buy you much.
posguy99 said:
It's been modified, it won't match Sprint's (or HTC's) md5sum in any case. So having the md5sum for this one doesn't buy you much.
Click to expand...
Click to collapse
Sprint and HTC aren't exactly providing an md5 on a file that hasn't been officially released. But I did create an md5 when I uploaded it so you know the file downloaded is the same one I uploaded.
Additionally the zip of the images located inside of the RUU are unmodifiable which is why we couldn't modify the old RUU to work with the new phones. When you start the RUU it will push the files to your phone and then check them. If they aren't what they are supposed to be, it will fail.
someone share the direct download link(eg, rapidshare link) to me?
i live in China and i cannot use the bit.ly services(because the gov blocked it)
fyi to those who are wondering this will work on a non google branded phone...however it does not fix the Rev 0 Rev a problem as it does not appear to update the pri to match that of the "with google" phones.
I dont care what sprint says and what htc says. My non google and my wifes google phone have two different speeds...
im exchanging mine for a with google phone today
Thanks!
this saved my phone. I was about to throw it away.
USB Connection Error
Tried running the RUU and got ERROR [170]: USB CONNECTION ERROR. Got in on a Windows XP and 7 laptop. Need help.
nemesys504 said:
Tried running the RUU and got ERROR [170]: USB CONNECTION ERROR. Got in on a Windows XP and 7 laptop. Need help.
Click to expand...
Click to collapse
Just because we always have to ask to rule out the obvious...did you run it as administrator? (Right click on the file, select "Run as Administrator")
Same Problem
I am having same issue as above on Win 7 64 bit. However everything else works from this machine to my phone. Rooting it, usb mount of SD, screen shots, etc. Please help me. I want to flash back to starting point and start over.
Thanks.
Jamie
Universal Androot confirmed working. This method is no longer needed and is to dangourous for some people so please use universal androot 1.5.3+
IF READ CORRECTLY YOU WILL NOT BRICK. BUT, Since a few of you dont have that ability, I AM NOT RESPONSIBLE FOR YOU BRICKING YOUR PHONE. There are no pros to rooting this phone yet, leave it alone if you dont know what your doing PLEASE. I beg you. You are in essence almost bricking your phone in order to root it in the first place. These arent fun and games, It is dangerous to rush this stuff
Listen.. Im more then happy to help people. BUt I fully understand why so many devs have left this place. Some of you are so utterly ridiculous with your questions, wanting someone to hold your hand. I cant sit on gtalk for hours helping you go through what should take 10 min , I have a life and kids and other things to do. I did this because I was bored and wanted to see if I could. There is not point in rooting it yet, there are no roms, nor will there be for at least a month. Please, if you cant even understand simple questions, have never rooted or even used an android phone before, please.. do not bother me. This place is insane with stupidity. I will change the tutorial in a little more detail later, but fo rnow, DO NOT DO THIS IF YOU DONT KNOW WHAT YORU DOING. IF YOUR BREAK YOUR CRAP< I DONT CARE, BECAUSE IT WASNT MY FAULT.
I am in no way an angry or mean person, but you people have given me a migraine. I see why all the rom devs hide from here so much
THERE IS NO POINT IN ROOTING THIS PHONE YET PEOPLE, SO STOP.. OMG PLEASE STOP LOL
IT HAS BEEN DONE!!! lol
After 3 days, sleepless night and 5 min from returning the phone, Together with the Awesome Cursordroid We have achieved full root of the fender mytouch/ Mytouch 1.2 revision.
Now.. Understand.. not many will have the fender Mytouch.. but this is the hardware they WILL be using in the fully confirmed Mytouch 1.2
If you do not follow my instructions fully, NOTHING WILL WORK.
Start by making a working gold card, pay VERY CLOSE attention to what the instructions for making a gold card say
http://theunlockr.com/2009/08/14/how-to-root-your-mytouch-3g/
READ READ READ. DO NOT download the SAPPimg.zip file it says on that page.
Get the top fixed SPL file 2010 from here
http://forum.xda-developers.com/showpost.php?p=4332591&postcount=1
Once you have you working goldcard (remember, apply to PHYSICAL not LOGICAL) rename the fixed SPL/rom you just downloaded to SAPPIMG.img
Put that file on your gold card
Hold volume down while hitting power
You will boot into Hboot, and if goldcard was made correcly and file is in root, it will begin to read. MAke sure battery is full or chargeing. follow on screen directions for flashing. Reboot into Hboot.
You are now screwed with a downgraded SPL and radio that do not work on this phone YAAAAAAY.
Now grab the stock radio and SPL from Cursordroid here http://forum.xda-developers.com/showthread.php?p=5451898&posted=1#post5451898
From there on follow hiw directions for reupdating your radio and spl, plus give yourself a new recovery making ROOT.
Im not good at tutorials or typing on a tiny netbook keyboard so please forgive. Anyquestions please ask and I will go into more detail
In order
Goldcard
Amen ras fixed spl rom renamed SAPPIMG.img
Boot into Hboot volume down/power
let rom install saying yes to what it says. If it works..
Now boot into your recovery through fastboot
Flash phone with stock fender rom
reboot into fastboot
back out of update when it asks and flash STOCK radio and SPL back, now reboot
your splash screen for fender IS GONE, get over it. You can make a new one later if you realllly need to.
if you build the thread they will come, oh yes, they will come.
thebluecoat said:
if you build the thread they will come, oh yes, they will come.
Click to expand...
Click to collapse
lol.. I figured if I could get a thread up with all our info, maybe I could get more people interested just for the fact hat nothing now works... which means this could be the same build in the coming Mytouch 1.2 that is basicly the same exact phone as the fender.
hey, im new here but i have a rooted g1. and i've been skimming thru the fender pages.
I also work at tmobile and used my discount to snag the fender. but as of now im still using my rooted g1 which currently has a tiny scratch on it which i cant stand "hence why i got a fender".
seems to me once the new mytouches come out with the 32a and 3.5 mm jack there will be more attempting to pwn his phone.
im still fairly new to all of this soo im tryin to soak up as much knowledge as i can.
but still w/o the root. the fender still is a sweet phone haha.
idk what to do with it, it just sits in my room i havent even put my sim into it yet. im deciding either to sell it or just let it sit until it can be rooted.
i use the wireless tether too much to switch to the mytouch.
in the mean time g'luck! kinda rough for us LE owners cuz only few people have it to play around with.
This might be noob as I am not 100% sure what perfected SPL means, but I had a SPL that gave the fastboot "no remote" error.
I used an official SEA RUU that comes with a ENG SPL, then I could update change what ever I wanted.
Thought I would just through it out there.
My phone is a model A6161.
Make a goldcard.
Then try to find an official HTC RUU with version higher than 2.08.531.1 but which has an open SPL or is only Cupcake so 1-click-root will work.
If that doesn't work just try a regular sappimg.nbh, but with goldcard too.
maxisma said:
Make a goldcard.
Then try to find an official HTC RUU with version higher than 2.08.531.1 but which has an open SPL or is only Cupcake so 1-click-root will work.
If that doesn't work just try a regular sappimg.nbh, but with goldcard too.
Click to expand...
Click to collapse
The problem is after days of reading and trying 5 different sapp.img every file gets the same device id failure. But I do understand having to find a higher number rom so Ill start on that quest.
So basicly what you saying is I need to find a pre rooted "offcial" rom that has and eng SPL allready or a 1.5 rom with open spl?
Ill try the 1.5 cupcake idea because the goldcard methos so far doesnt seem to work but that would make sense if we are trying to use to old a versions to root.
Looks like I have a new project for the day lol
crypysmoker said:
The problem is after days of reading and trying 5 different sapp.img every file gets the same device id failure. But I do understand having to find a higher number rom so Ill start on that quest.
So basicly what you saying is I need to find a pre rooted "offcial" rom that has and eng SPL allready or a 1.5 rom with open spl?
Ill try the 1.5 cupcake idea because the goldcard methos so far doesnt seem to work but that would make sense if we are trying to use to old a versions to root.
Looks like I have a new project for the day lol
Click to expand...
Click to collapse
I've already tried that, didnt work for me, got "Invalid device ID" however, I cannot make a gold-card because I always get "damaged sd card" or windows says I need to format it right. I'm 100% sure I did it right to three different SD cards, and I still got the same error.
--edit-- if you successfully make a goldcard for this phone, Ill pm you for shipping info LOL!
crypysmoker said:
The problem is after days of reading and trying 5 different sapp.img every file gets the same device id failure. But I do understand having to find a higher number rom so Ill start on that quest.
So basicly what you saying is I need to find a pre rooted "offcial" rom that has and eng SPL allready or a 1.5 rom with open spl?
Ill try the 1.5 cupcake idea because the goldcard methos so far doesnt seem to work but that would make sense if we are trying to use to old a versions to root.
Looks like I have a new project for the day lol
Click to expand...
Click to collapse
I think, your current way will not end with success.
Wrong model id or device id means, that HTC decided pick out Fender in another serie. Yes, i agree, that Fender has same SPL as Magics, but trying flash anything, that has another model id like trying flash Hero's ROM to Tattoo.
SPL ia like a computer's BIOS. SO if you flash foreign bios - your comp will probably die....
Saddened by the fact that Fender is limited edition. So it will not have big knowledgebase like Magic.
5[Strogino] said:
I think, your current way will not end with success.
Wrong model id or device id means, that HTC decided pick out Fender in another serie. Yes, i agree, that Fender has same SPL as Magics, but trying flash anything, that has another model id like trying flash Hero's ROM to Tattoo.
SPL ia like a computer's BIOS. SO if you flash foreign bios - your comp will probably die....
Saddened by the fact that Fender is limited edition. So it will not have big knowledgebase like Magic.
Click to expand...
Click to collapse
While the Fender is le, the mt3g 1.2 is the same hardware, so hopefully someone will get it figured out.
chrys9989 said:
While the Fender is le, the mt3g 1.2 is the same hardware, so hopefully someone will get it figured out.
Click to expand...
Click to collapse
Oh. Chances growing up.
I'm new here, but typically how do people go about getting the attention of devs? Is it just create a thread an hope enough people show interest? Should we do a roll call of how many actually are interested in rooting this phone?
thebluecoat said:
I've already tried that, didnt work for me, got "Invalid device ID" however, I cannot make a gold-card because I always get "damaged sd card" or windows says I need to format it right. I'm 100% sure I did it right to three different SD cards, and I still got the same error.
--edit-- if you successfully make a goldcard for this phone, Ill pm you for shipping info LOL!
Click to expand...
Click to collapse
No.. I got the gold card made. The only reason it ever comes up as damged or reformat is because you applied the goldimg to the logical drive which is at top of list as opposed to Physical REMOVABLE DISK at the bottm. Its the only time I can get the error. but if I apply the goldimg to the logical drive it makes a perfect goldcard everytime. I tested it on aspar g1. So... its not a godl card problem lol
maxisma said:
Make a goldcard.
Then try to find an official HTC RUU with version higher than 2.08.531.1 but which has an open SPL or is only Cupcake so 1-click-root will work.
If that doesn't work just try a regular sappimg.nbh, but with goldcard too.
Click to expand...
Click to collapse
Looking through here for HTC RUU roms I seem to keep geeting dragged to the hero and WinMob forums which I dont think I should be. Where exactly would I find this?
My ideas are..
Find a rom of higher version that is rooted see if it works.
Find an older 1.5 build (which is proving hard) and go from there
Try and flash the rooted fender donut over it and see the results.
My main problem with this is, I dont think its able to be downgraded past 1.6.. Just like newer PSP's cant be downgraded to 1.5
After formatiing my 2gb sandisk (which may be the problem) now when using the 98mb SAPPIMG.zip I get "Main version is older" instead of "Device id failed"
Is this a good sign to on the right track? Im going to try the 62mb SappIMG.zip from amon ra's tut as soon as its done downloading and see if theres a difference.
Now.. what does main version is older mean? The firmware or the spl/radio. if so... is there a newer version i can use/or substitute a file for the Sappimg.nbh to just install a higher version rom.
Man.. The G1 is so much easier to do all this with lol
YEEEEES. Ok. I freaking fracking diddley did it. OMG i was sooo scared.
Wooo So happy now.
I unable to update my OP and thread title if a mod can help me with that.
If noone minds I am going to post my first ever tutorial on something. this was a real pain but I am up and running on Amon ras latest rom for now. On to the recovery....
EDIT-- Got a fully functioning Manups 2.1 1.5 going. THEBLUECOAT if you want to know how to do it PM me... Otherwise give me about an hour or so and I will have a full tut posted
AHHH.. EVEN worse.. I noticed now that it says I have a 32b board NOOOO
EDIT2- Such a dumbass I didnt make a backup of the orignal. Poop.. I liked the boot image and music apps. I just wish I could figure out why all roms so far dont recognize the touch screen as being there and want me to use the track ball. Even power button has 1 option Power off lol
UMMM touch screen not working. What didnt I do?
How do I get my SDCARD to not show up under logical, its under logical but the drive says "removable disk" all I have are phones to use, would this not be possible or would I need a driver replacement
thebluecoat said:
How do I get my SDCARD to not show up under logical, its under logical but the drive says "removable disk" all I have are phones to use, would this not be possible or would I need a driver replacement
Click to expand...
Click to collapse
you HAVE to use a card reader. thats where your problem has been. You have to use a card reader so that it sees the reader AND the card seperatly. So in hex, you dont see Logical drive then a row and then Physical and a row?
Im not pissed... I had the 2010 eng spl... trying to flash roms. No rom would use touch screen. so started over and ened up with a 32 b board now and a perfected spl again.... lol Argh... trying through it again now.
crypysmoker said:
you HAVE to use a card reader. thats where your problem has been. You have to use a card reader so that it sees the reader AND the card seperatly. So in hex, you dont see Logical drive then a row and then Physical and a row?
Im not pissed... I had the 2010 eng spl... trying to flash roms. No rom would use touch screen. so started over and ened up with a 32 b board now and a perfected spl again.... lol Argh... trying through it again now.
Click to expand...
Click to collapse
Ok, so how did you get the spl changed? and what did you flash that was 32b?
chrys9989 said:
Ok, so how did you get the spl changed? and what did you flash that was 32b?
Click to expand...
Click to collapse
I used Amen ras newest Fixed spl fix 1.33.2010, made my gold card, renamed that file to SAPPIMG.zip, went into Hboot and it flashed without a problem.
I then rebooted into Hboot seeing the new Info.. Didnt look at the 32a/32b part yet so not sure if it happened there.
It then rebooted into whatever rom that file came with (look for Amen ras Fixed spl thread) the rom came up, with no tocu screen. only the track ball worked.
I rebooted and stupidly jumped right into flashing a couple of the new clair builds from king and.. the othe rguy lol. neither had touch support. I then went back to update to manups newest and used the 32a port file, and no touch screen...
I then rebooted and flashed the amen ra rom and rebooted into a Mytouch boot loop... went into Hboot and had a perfected spl and S-on. ARGH.
Just started from scratch again. Im really wondering why i loose touch screen support and why in the hell it say 32b now
(If ROM installed via official HTC RUU- RUU_Sapphire_Rogers_WWE_3.05.631.7_R_release_signed_NoDriver.exe)
UPDATE!! **SOLVED** April 25, 2010
Download new RUU
http://www.multiupload.com/XQEH9NVGY7
Flash with Goldcard method http://theunlockr.com/2010/03/10/how-to-create-a-goldcard/
1. Download RUU linked above.
2. Install update using RUU.
3. Turn on phone and connect to computer.
4. Get RA recovery and SPL also linked above and drop them to sdcard root directory.
5. Run SDK: adb shell
6. Install recovery: flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img http://forum.xda-developers.com/showthread.php?t=561124
6. Turn off phone and turn on again holding Power+Home. RA Recovery should appear.
7. Flash zip from sdcard.
8. Use file: update-hboot-1762007-signed
9. Done. PSPL broken.
10. Build a shrine for orange_24
****************************************************
**Not Successfully Rooted: Feb. 2, 2010 (AFAIK)
I decided to start this thread because the info for again obtaining root, for those of us dumb enough to update to the official Rogers ROM 3.05.631.7 via the RUU, is all over the place in about a million different threads. My hope is that we can organize it all in 1 place.
At this point, yes, we all know we were impatient and newbs and everything else. Ok, lesson learned. So, lets move forward and try to get this thing rooted.
If you are a developer who has the talent to help root this ROM and have lost interest in the Magic or moved on to the Nexus One or Droid, we ask that you please try to spend a few moments on this and help out those of us who are really stuck here. Personally, I'm getting pretty desperate and thinking of even replacing the phone.
Please post what you've tried in attempting to again obtain root, your failures and hopefully successes.
*One Click Root: http://theunlockr.com/2009/08/29/how-to-root-the-htc-magic-in-one-click/ Cant' back up Recovery.img Error(Tried clicking the hidden Star next to "Back Up Recovery" and skipping this step...and just flashing recovery-RA-sapphire-v1.5.2H.img. Didn't work either) Tried with Amon_RA Hero recovery.img also, without success.
*Tried downgrading to Rogers' last official ROM via the RUU for (Rogers)_RUU_Sapphire_Rogers_WWE_2.17.631.2_release_signed_NoDriver.exe RUU would not let me proceed because the ROM was older than the one installed. Attempted several times both with and without a goldcard installed.
*ADB: Will see the device, initially, but a command of "adb remount" kills the connect. same with "adb root" **EDIT
*Fastboot: Error- Does not allow access
*Relentless Rooter: http://forum.xda-developers.com/showthread.php?t=556200 No luck obtaining root
*Fix Perfect SPL: http://forum.xda-developers.com/showthread.php?t=548218&highlight=create+gold+card With one GoldCard getting Update Fail error that SAPPIMG is older than one installed. When trying the other GC, get Update Fail Error that Model ID is incorrect. Tried 2 different micro sd cards, one Sandisk and one Patriot. The card was recognized by my pc after I was done creating the GoldCard, so unless I'm doing something wrong the GC was created properly. Is the goldcard.img supposed to dissapear or remain on the card after your copy/paste write/save to the sd card disk?
* Tried RUU for RUU_Sapphire_HTC_Europe_3.04.401.2_HTC_AT_test_signed_NoDriver.exe http://forum.xda-developers.com/showthread.php?t=625108 RUU would not let me proceed because the ROM was older than the one installed or Device ID was wrong. Attempted several times both with and without a goldcard installed.
*Tried RUU for RUU_Sapphire_HTC_Europe_3.05.401.3_release_signed_NoDriver.exe http://forum.xda-developers.com/showthread.php?t=621415 RUU would not let me proceed because the ROM was older than the one installed or Device ID was wrong. Attempted several times both with and without a goldcard installed.
*Tried RUU_Sapphire_HTC_Asia_WWE_2.53.707.2_SEA_test_signed_NoDriver.exe RUU would not let me proceed because the ROM was older than the one installed or Device ID was wrong. Attempted several times both with and without a goldcard installed.
I've probably tried a few more methods to obtain root. Those were all fails, too. I'll post the links, as well, when I find them again.
Hopefully this thread will lead us all in the right direction.
Here is the link to the same topic in the HTC Dream Forum-in case they find out something that might help us out: http://forum.xda-developers.com/showthread.php?t=625732
i guess its time to play doctor with my new phone from rogers and swap the board from my old one.....
considering nothing works, i think any new idea would be a good idea
novadoc said:
considering nothing works, i think any new idea would be a good idea
Click to expand...
Click to collapse
like i said my idea was to swap my old motherboard into the new phone
you can give it a shot
but personally, unless you know exactly what your getting into, i wouldn't mess with the hardware
novadoc said:
you can give it a shot
but personally, unless you know exactly what your getting into, i wouldn't mess with the hardware
Click to expand...
Click to collapse
i already did it lol im more of a hardware then software
I know it might be nothing but when the Rogers RUU unpacks the img file loads as sappdimg and not sappimg. I don't know if the extra d in there means anything or if its something that shows up later.
I also try every method above and not luck also...
is there a possible way of tricking the system... with a higher build number and SPL with a custom installation from files that I see from one of the post where rogers send the user some files because they were running Win7?
I think that's the problem
We have the highest spl# and its perfected
So until someone gets their hands on a higher version than ours that is imperfect or engineering...
We are SOL, although I am hopeful someone is working on this for us.
shael said:
i already did it lol im more of a hardware then software
Click to expand...
Click to collapse
Did it work?
I have an Rogers HTC Magic and I didn't apply any update from Rogers since I bought it on June 2nd.
It's very strange that "adb devices" doesn't see the device?
have you enable the "USB debugging" ?
That part should work (when the devices is started).
novadoc said:
Did it work?
Click to expand...
Click to collapse
pfft ya ofcourse it worked... i have my older motherboard with my old rom and my old info all i did was swap the screen and case.... done deal... 5 min job lol
Would someone please report the radio and SPL versions (for the result of the 3.05.631.7 update)?
feisty_noodle said:
would someone please report the radio and spl versions (for the result of the 3.05.631.7 update)?
Click to expand...
Click to collapse
apphire pvt 32a ship s-on h
hboot-1.76.0010 (sapp50000)
cpld-12
radio-6.35.10.18
feisty_noodle said:
would someone please report the radio and spl versions (for the result of the 3.05.631.7 update)?
Click to expand...
Click to collapse
apphire pvt 32a ship s-on h
hboot-1.76.0010 (sapp50000)
cpld-12
radio-6.35.10.18
Well, until it gets cracked, here's something that will make you feel a little better about being stuck on this ROM.
Google Search by Voice, installable .apk from Euro Android Market. Just run the installer through Astro, etc., and G Search by Voice is back on the Search button of your phone. You might need to launch the app first via the icon in the app tray, then reboot the phone to make the search button recognize its there. But it will be there.
http://www.eclosion-android.com/com.google.android.voicesearch.apk
BTW, not my link in case mods want to get involved.
Enjoy!
i think the first step would be to getting ADB working again
any ideas?
novadoc said:
i think the first step would be to getting ADB working again
any ideas?
Click to expand...
Click to collapse
I can used adb devices to see my connected htc magic.... but other function permission not allow...
Is this thread in the Dream Forum a path to follow to try, or just a good way to brick your Magic? I haven't fully read through it to see if this is to keep root, if you already have it and flash the Rogers Dream ROM for data/ or to regain root if you flashed the official Rogers RUU with a Dream. The post says should work on all Rogers phones, but i feel a brick coming on for me.
http://forum.xda-developers.com/showpost.php?p=5480955&postcount=416
Ok, just like all of you I have rooted, experimented to the limits and pushed them well little did i Know is that you cant reflash the 1.56 ruu so needless to say I ended up with a brick but luckily for us it will still connect in fastboot
so this is a solution to at least get it up and running
Pros-
Reactivate your phone since it will be formated
All functions will work
can still root, install .apk's use wifi etc
camera etc
so the pros are it will operate just like nothing ever happened now to the con's
YOU WILL HAVE TO DO THIS EVERYTIME YOU TURN OFF YOUR DEVICE
Ok here is how to fix it
Connect your phone to your PC
open command and navigate to your android tools folder
type in
fastboot devices
make sure it detects your device
should show the HTC logo on your phone
now simply type
fastboot oem boot
wait a couple minutes while your phone reboots
viola you phone is back to running again...just dont turn it off LOL
can you launch the RUU again and (hopfully) have it restore your phone correctly?
You can launch but it will still fail like before, I havent been successful in finding a full solution as of yet
rayborn said:
You can launch but it will still fail like before, I havent been successful in finding a full solution as of yet
Click to expand...
Click to collapse
hmmmm interesting man. honestly you should be able to rebuild all the / partitions. such as /misc and /radio. we need some linux junkies in this thread to tell us how to rebuild failed / partitions
This is amazing. Sure did work for me. I just wish there was a way to get it flash the original radio. I have only had this thing two weeks and would love to take it back and exchange it, but I am just paranoid since it shows radio 2.41.04.02.03.
wait, what exactly did you do to get your near-bricked phone?
you used the 1.56 RUU on your phone that had a 2.xxxxxx radio?
have you tried both of the RUU's? the original and 1.56?
My phone was the Sprint Hero *with Google model, so I had rooted it and loaded a custom rom on it etc and was playing around with it but I wanted to go back to stock so i flashed this ruu
RUU_Hero_C_Sprint_1.56.651.2_signed_release
And BAM at the end error 110
wouldnt boot anylonger
spent all day on figuring out this solution
did you try the 1.29 RUU?
yeah i tried every sprint hero ruu i promise you i left no stone unturned trying to fix this
BRILLIANT!
I can't tell you how impressed I am that somebody has found what i now consider to be the first step towards getting the RUU 110 error solved.
I still feel that the issue comes down to the lack of ADB that seems to happen once you get 110... maybe a driver issue on the phone vs. driver issue on the computer? after all the RUU starts failing on all the ADB commands when you check out the RUU logs...
sorry i can't help take it from there, i returned my phone to sprint inside of the 30-day window and just told them something i installed form the market "bricked" my phone...
I eagerly await your results though for a final step towards solution, as I am dreading the day i have to RUU my phone for whatever reason that may be, although I've been running a personally customized Pancake ROM for almost a week and totally happy with it so won't be doing anything until 2.1 is official...
R
rayborn said:
My phone was the Sprint Hero *with Google model, so I had rooted it and loaded a custom rom on it etc and was playing around with it but I wanted to go back to stock so i flashed this ruu
RUU_Hero_C_Sprint_1.56.651.2_signed_release
And BAM at the end error 110
wouldnt boot anylonger
spent all day on figuring out this solution
Click to expand...
Click to collapse
Same exact thing for myself. Multiple people said the way to go back to the stock radio was to use the RUU. I tried both RUU's and same results. Now I am just trying to decide what is better.
Live with this and hope for a better option to come or take back a "bricked" hero that shows Radio 2.41.04.02.03 and hope I don't end up getting charged later.
IMHO I think the best thing for you guys to do is wait for our 2.1 update, which will more than likely have a smiliar radio update. Then you can just say the update bricked the phone.
If we get the same radio version, then just take it back, if we get a different version then maybe we can find a file to edit the number to make it say what ever version you want it to say, something like editing Build.prop. Then Sprint has nothing to ask questions about. Should be out in a few weeks if the rumors are right. Maybe you can deal with this soultion until then.
As far as the don't turn your phone off issue, mines been up for 13 days. I hate turning it off, partially because of the missed emails and partially because I worry that it won't come back up.
Subscribing. When Sprint releases the official 2.1 in a few weeks, I was planning on using the 1.56 RUU and then doing the 2.1 update. Apparently this isn't going to be possible since I did the Radio update. What is going to be the proper way to get the 2.1 update through Spring for phones with the Radio update to keep from bricking a phone?
SamXp said:
Subscribing. When Sprint releases the official 2.1 in a few weeks, I was planning on using the 1.56 RUU and then doing the 2.1 update. Apparently this isn't going to be possible since I did the Radio update. What is going to be the proper way to get the 2.1 update through Spring for phones with the Radio update to keep from bricking a phone?
Click to expand...
Click to collapse
I was of the same mind, but reading this thread has me wondering the same thing. Are we just screwed now?
mginther said:
I was of the same mind, but reading this thread has me wondering the same thing. Are we just screwed now?
Click to expand...
Click to collapse
There's been plenty of people who have flashed back and forth between the radio versions, using the RUU programs...there's only been a few that have bricked from what I've read.
It's still a bit iffy on whether or not it's actually safe to go between the two, but it shouldn't matter since the new radio versions apparently work just fine with all ROM's that I've seen
tatonka_hero said:
There's been plenty of people who have flashed back and forth between the radio versions, using the RUU programs...there's only been a few that have bricked from what I've read.
It's still a bit iffy on whether or not it's actually safe to go between the two, but it shouldn't matter since the new radio versions apparently work just fine with all ROM's that I've seen
Click to expand...
Click to collapse
True, and if we elect to continue to use either a Fresh or Damageless version of an official 2.1 Sprint ROM, then we should be ok. But if we wanted to go to the Sprint ROM, there are going to be a lot of bricked phones if there isn't a way to understand what is going on when a 1.56 RUU is used over a phone with the 2.x Radio update.
Just wanted to pass along some more information in case anyone else is having this problem. I had reactivated an old phone temporarily since this one was bricked. This morning I reactivated my hero due to this semi fix and immediately I could call and textimg was fine, but i kept getting vision error 67 for data. Sprint reset my data about three times and it never worked. I tried updating my profile multiple times and it never worked. Finally I Ran the RUU again and sure enough after a reboot or an "oem boot" I had error 67again. I went ahead and updated my profile and this time it worked and data started working. Still hoping someing else comes along though.
well I think the issue here might be that it does not have the recovery backup on it after you do an RUU. I could be wrong but who knows? I would say install flashrec-1.1.3-20091107-2.apk on your phone once you are able to get it up and running then flash the recovery backup and restart. That could possibly fix the issue? I have the files if anyone needs them, I'm not sure how to upload them on here...
~Danny
I'm not sure if it's possible boot into recovery console using this method, but if you can, has anyone tried manually flashing the old radio in the same manner they flashed the new one to revert back and then RUU. Perhaps that may do the trick.
My phone isn't bricked so I can't try it out, but seems like it might be worth a shot in theory.
I did something really dumb even though I was advised not to. I managed to get the Windows Phone 10 Technical Preview on my HTC One M8 for Windows. The OS version that got pushed to it simply is not compatible with this hardware and so many things don't work. I want to go back but the Microsoft-provided recovery tool doesn't detect the phone because it was never intended to work with this model. In short, my question is does anyone have a way to just flash an HTC One M8 for Windows back to the factory T-Mobile ROM that it came with out of the box? If so, where do I get it and how can I flash to it? HTC has no recovery tool to speak of for this phone, Microsoft was just as much help, and TMo wants me to pay an insurance deductible before they will replace the thing. I will be ever so grateful if someone can help out.
Thanks!
reptarsaurusflex said:
I did something really dumb even though I was advised not to. I managed to get the Windows Phone 10 Technical Preview on my HTC One M8 for Windows. The OS version that got pushed to it simply is not compatible with this hardware and so many things don't work. I want to go back but the Microsoft-provided recovery tool doesn't detect the phone because it was never intended to work with this model. In short, my question is does anyone have a way to just flash an HTC One M8 for Windows back to the factory T-Mobile ROM that it came with out of the box? If so, where do I get it and how can I flash to it? HTC has no recovery tool to speak of for this phone, Microsoft was just as much help, and TMo wants me to pay an insurance deductible before they will replace the thing. I will be ever so grateful if someone can help out.
Thanks!
Click to expand...
Click to collapse
Generally I think you are out of luck until they launch the Windows 10TP for HTC M8's. When that happens, you should be able to use the Windows Phone Recovery Tool to re-flash your phone. It looks like it's basically a re-skinned version of the Lumia Software Recovery tool, and it only makes sense for them to release this as well if they are going to be providing a way to recover and flash non-Lumia branded phones in the future.
There is a way to re-flash the HTC One M8 for Windows if you have the ROM, but so far only the Verizon version has leaked. I hope this is not your only phone, because if you wait a month or so you should be able to re-flash using the Microsoft tool
You have absolutely no right to be mad at Microsoft, HTC and/or T-Mobile for the problems. They are completely justified making you pay the deductible to get this fixed, why should they eat the cost of fixing it?
Don't get me wrong, I don't blame anyone but myself for this. I'm simply surprised that there isn't a recovery option out there in general. Someone could have a problem that isn't their fault at all that could benefit from having this. That being said, I have an open ticket with the HTC dev team. All I really want is access to a ROM that must clearly already exist. The software got on the phone in the first place, right? Of course I am not a dev and probably have no idea what I'm talking about. I apologize if I'm coming off as an ass looking for a hand out. It just seems to me that this is a simple issue with a simple fix. I know from when I had a Lumia device that I could open up the navifirm+ software and download any ROM for any windows phone from any region of the world.
reptarsaurusflex said:
Don't get me wrong, I don't blame anyone but myself for this. I'm simply surprised that there isn't a recovery option out there in general. Someone could have a problem that isn't their fault at all that could benefit from having this. That being said, I have an open ticket with the HTC dev team. All I really want is access to a ROM that must clearly already exist. The software got on the phone in the first place, right? Of course I am not a dev and probably have no idea what I'm talking about. I apologize if I'm coming off as an ass looking for a hand out. It just seems to me that this is a simple issue with a simple fix. I know from when I had a Lumia device that I could open up the navifirm+ software and download any ROM for any windows phone from any region of the world.
Click to expand...
Click to collapse
Fair enough. Its a bit weird that only Nokia put out any kind of program to re-flash phones, but I have a feeling that the app Microsoft has put out will, going forward, be used to reflash any Windows Phone that is having problems. They kind of need to provide that functionality if they are going to take control of the update process from the carriers (which i know they want to do, whether they actually pull it off remains to be seen).
I'd say just hang in there, you will likely be able to re-flash in a month or so. I hope you can somehow get access to the rom, but there isn't program released to flash it on the phone (though there are ways, look at the Verizon RUU thread. There is also a Youtube video out there showing how to do it)
i was the first with htc w8 (tmous) to hack the w10 beta on it if you check my twitter.
the only reason why i even considered to do this is because i have a way out.
that can't be said for public. so why the hell you didn't check if you have
a way to go back to stock before even considering such a highly
experimental thing to your precious device?
sure you can't expect any support from ms or tmous for that scenario.
i flashed back to w81 the next day already because of htc related bugs.
i will restore it for you if you send it to me and pay 2-way shipping.
this is a one time personal offer from me that i will do for you.
contact me via pm if you didn't send it in yet.
let this be a lesson to you guys...
reptarsaurusflex said:
I did something really dumb even though I was advised not to. I managed to get the Windows Phone 10 Technical Preview on my HTC One M8 for Windows. The OS version that got pushed to it simply is not compatible with this hardware and so many things don't work. I want to go back but the Microsoft-provided recovery tool doesn't detect the phone because it was never intended to work with this model. In short, my question is does anyone have a way to just flash an HTC One M8 for Windows back to the factory T-Mobile ROM that it came with out of the box? If so, where do I get it and how can I flash to it? HTC has no recovery tool to speak of for this phone, Microsoft was just as much help, and TMo wants me to pay an insurance deductible before they will replace the thing. I will be ever so grateful if someone can help out.
Thanks!
Click to expand...
Click to collapse
You might be out of luck for now at the moment. I'm sure the TMo ROMS aren't available, otherwise you would be able to. Remember that the trick to update to Windows 10 Preview was AT YOUR OWN RISK due the fact that the phone isn't OFFICIALLY SUPPORTED
HD2Owner said:
i was the first with htc w8 (tmous) to hack the w10 beta on it if you check my .
the only reason why i even considered to do this is because i have a way out.
that can't be said for public. so why the hell you didn't check if you have
a way to go back to stock before even considering such a highly
experimental thing to your precious device?
sure you can't expect any support from ms or tmous for that scenario.
i flashed back to w81 the next day already because of htc related bugs.
i will restore it for you if you send it to me and pay 2-way shipping.
this is a one time personal offer from me that i will do for you.
contact me via pm if you didn't send it in yet.
let this be a lesson to you guys...
Click to expand...
Click to collapse
I'd like to know how you did this instead of sending you my phone.
flashed the stock rom.
HD2Owner said:
flashed the stock rom.
Click to expand...
Click to collapse
Is it possible to flash the stock rom on a verizon phone?
sure. by stock rom i mean the original rom meant for the device/carrier.
on verizon w8 -> verizon rom
on at&t w8 -> at&t rom
on tmous w8 -> tmous rom
don't try to flash different carrier rom. it won't work.
all 3 carrier variants have different modelID which is checked before allowing flash.
HTC One M8 for Windows
HD2Owner said:
sure. by stock rom i mean the original rom meant for the device/carrier.
on verizon w8 -> verizon rom
on at&t w8 -> at&t rom
on tmous w8 -> tmous rom
don't try to flash different carrier rom. it won't work.
all 3 carrier variants have different modelID which is checked before allowing flash.
Click to expand...
Click to collapse
I have been looking everywhere for the Verizon rom and software so I can reflash my phone. Do you happened to know where I can get these?
dans95tbird said:
I have been looking everywhere for the Verizon rom and software so I can reflash my phone. Do you happened to know where I can get these?
Click to expand...
Click to collapse
there: http://forum.xda-developers.com/showpost.php?p=55201370&postcount=2
download the htc RUU that i attached to this post and extract with winrar.
place the htc w8 verizon nbh in the extracted RUU folder with filename "RUU_Signed.nbh".
then go into bootloader (power off, then hold vol-&vol+ while pressing power until it vibrates).
it will show white bootloader screen with hardware info.
when the pc installed the drivers for bootloader mode it switches from "serial" to "usb" on the bottom.
then doubleclick the ROMUpdateUtility.exe and it will flash the phone.
everything will be wiped of course.
HD2Owner said:
there: http://forum.xda-developers.com/showpost.php?p=55201370&postcount=2
download the htc RUU that i attached to this post and extract with winrar.
place the htc w8 verizon nbh in the extracted RUU folder with filename "RUU_Signed.nbh".
then go into bootloader (power off, then hold vol-&vol+ while pressing power until it vibrates).
it will show white bootloader screen with hardware info.
when the pc installed the drivers for bootloader mode it switches from "serial" to "usb" on the bottom.
then doubleclick the ROMUpdateUtility.exe and it will flash the phone.
everything will be wiped of course.
Click to expand...
Click to collapse
since ppl dnt seem to give u a thanks ill spam the thread any say thank and the "thanks" button....ppl appreciate his help!!!
The latest build of Win10 works way better on a One M8 btw. I have installed it using the registry method and running it without many problems. So if you have a t-mobile/at&t version of this phone (where there is no RUU availible) with windows 10 installed i advice upgrading to the latest build.
really? i noticed bugs with background picture not showing and many htc apps/settings not working..
they work now on latest build?
in the new version of windows phone recovery tool, ms added support for htc devices.
http://go.microsoft.com/fwlink/?LinkID=525569
Any luck with Verizon HTC One?
HD2Owner said:
in the new version of windows phone recovery tool, ms added support for htc devices.
Click to expand...
Click to collapse
I downloaded the newest version, 2.0.3, of the recovery tool. Even though it says it supports HTC devices it still fails to rollback my Verizon HTC M8. I receive the error: "Software Package is not found on server"
This is after the tool recognizes my device and asks me to restart in boot-loader mode.
Anyone else have success with using ver. 2.0.3 with a HTC M8?
Shockakohn said:
I downloaded the newest version, 2.0.3, of the recovery tool. Even though it says it supports HTC devices it still fails to rollback my Verizon HTC M8. I receive the error: "Software Package is not found on server"
This is after the tool recognizes my device and asks me to restart in boot-loader mode.
Anyone else have success with using ver. 2.0.3 with a HTC M8?
Click to expand...
Click to collapse
Recognized my T-Mobile M8 and flashed WP8.1 successfully.
Not able to update to latest Windows 10 mobile TP build
My HTC One is currently on 10.0.12562.84 (Build 10080). For some reason I am not able to see the latest build 10.0.12648.133 (Build 10149). Any one able to update to the latest build. Any idea why I'm not seeing it still?
Tried using the phone recovery tool to flash back to 8.1 but it says no builds available.
germanh said:
Tried using the phone recovery tool to flash back to 8.1 but it says no builds available.
Click to expand...
Click to collapse
which variant? verizon, at&t or tmous?