Related
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.
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.
*ATTENTION MODS* I am reposting.... sort of... the original thread is here
http://forum.xda-developers.com/showthread.php?p=9074948#post9074948
Hello! I am not new to rooting...I did get a new EVO 4G at best buy yesterday...
Went home and tried to root following another method than unrEVOked 3.21 and long story short had to RUU with "RUU_SuperSonic_S_Sprint_WWE_3.26.651.6_Radio_2.15 .00.07.28_NV_1.40_release_140444_signed"
I then tried unrEVOked 3.21 which SEEMED to work... I followed all onscreen prompts...
Plugged in my phone, ran the program, phone rebooted, selected HBOOT USB, Program reported that everything was going along nicely...even saw the program say waiting for root..."this was a triumph" Rebooted..then came back up to desktop...didnt reboot in recover like i have seen... the program then reverts to saying the thing about HBOOT USB.... there is NO SuperUser app and it is NOT rooted...
Please tell me where I went wrong...and what I need to do to fix it...
Info about MY Phone
Android Version 2.2
Baseband Version 2.15.00.07.28
Kernel 2.6.32.15-g746f4f0
Software Version 3.26.651.1
PLEASE help....I am having withdrawals lol...
***UPDATE***
Following this Guide
http://forum.xda-developers.com/showthread.php?t=829045
I made it to Step 19...then S#*+ went crazy...It appears that the recover did NOT flash...not really sure...I am now trying to RUU my phone back...and start over but it keeps saying the phone is low battery <30% and its NOT...I looked at 3 batterys on a Hero and it says all are over 70%...
and ..since im pretty sure this matters...with S-OFF
When I try to flash PC36IMG.zip Radio_V2 FAIL-PU and...Bootloader FAIL-IC is what I get...
ALL help greatly appreciated...thankfully I am off work the next two days...So I know I can get this resolved
Ok I have done a lot of reading that seems to indicate that I have no ROM or my ROM is Broken...and seeing as how RUU keeps saying my battery level is too low I am going to put it on the charger til the light turns green...Try to RUU in the Morning...
***SOMEONE PLEASE CORRECT ME IF I AM WRONG ***
I am under the impression that RUU'ing will NOT Turn S-ON and will Leave S-OFF
But will just load a ROM and allow me to boot in and then run unrEVOked and be on my merry rooted way...
If ANYONE knows that it will turn S-ON please stop me lol...I am going to stop trying for now and get some sleep... will check this post before continuing..
Like the titles says, I bought a rooted phone from someone and it's messing up so now I'd like to take it back to factory settings 100% with the latest update, and unrooted as well. I'm currently frustrated to be honest...I've been trying to do this for the last 6 hours and it's not working out.
Recently my number has not been showing up when I call people it just shows as withheld/unknown, and also when people call me it always shows their numbers as unknown even if they are saved in my phone already. I was told at T-Mobile these problems are just part of the version software I'm running on my phone and I should update it.
I've tried doing the latest update through the phone and it will restart then be stuck on the screen with the little green guy sitting under a triangle with a orange exclamation mark inside of it. I took it to T-Mobile and they tried to install the latest software and eventually (after many times trying to update it) said I just need to go home and find the latest software update and install it via my computer to bring it back to 100% normal as they cannot do it without it being hooked up to my computer.
Where can I even download the latest firmware/whatever it's called and how would I do the updating with the phone connected to my computer? Is there a guide I can be linked to to explain updating rooting/unlocking/etc all in one thread?
If there are any specific threads that already have this information please link me, I haven't found anything that helps me thus far! Thanks ahead of time for your help with this everyone!
Try this good luck
http://forum.xda-developers.com/showthread.php?t=1193033
Sent from my HTC Sensation 4G using xda premium
jmcdonald58 said:
Try this good luck
http://forum.xda-developers.com/showthread.php?t=1193033
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
Thanks for the link and attempting to help me but I've just gone to start that process and I already have a problem with it. My HBOOT version is not listed on the websites supported HBOOT versions.
I have 1.17.1111 and it's not on the list of HBOOT versions, there is only a 1.17.0011. So what should I do now?
I need to unroot and uninstall anything that would effect this process firstly (I'm not sure how to do that either). I want to do a total wipe of everything and uninstall all modifications to phone as well, then I want to re-do the best ones. So I will need to be linked to a guide to do these as, obviously, I'm one of those stupid needy nubs roaming the forums. Also, how would I go about finding and downloading the latest t-mobile update (Android 2.3.4 / software version 1.50.531.1) for this phone? The guys at the store said there was a new one that just came out and that I'd need to download it and install it via computer.
Hello
The first thing you are gonna do is write supercid follow this link : http://forum.xda-developers.com/showthread.php?t=1192300 - step 4
This is so you can flash any RUU, you want and not to brick your device.
After that find the a RUU that matches your phone company : http://forum.xda-developers.com/showthread.php?t=1074559
After that run it on your phone. When you have done that, you should be non-rotted, stock recovery(means that you can install updates from HTC), but you are still S-off. Now this is a very tricky a dangerous thing to do.
I have done it before, and I did it exactly as I am telling you to do. Now click on this link: http://forum.xda-developers.com/showthread.php?t=1192300
And go to step 5, and do as exactly it says, when done, you should be s-ON and now your phone should be as It was new
That is what I did and nothing went wrong, but don't blame me if something goes wrong
Nvm, I think I might have it now.
jctessier87 said:
Okay, I can do the above if you could tell me where I can get TMOUS_1.45.531.1_Radio_10.56.9035.00U_10.14.9035.01_M_release_208218_signed.exe downloaded, or even the newest 1.50.531.1
I followed the links on there until it sends you to filefactory.com and gives you a SUPER slow download. I have a 16mb connection and it's downloading at 20kb/s which is going to make this take 4 hours as this is 389mb to grab this replacement.
Can you tell me of another place where I could download this where it allows faster downloads without having to pay for a membership to get this update?
Click to expand...
Click to collapse
You need to download RUU Tmobile version 1.29 and then update your way up to 1.50.531.1
Sent from my Sensation using XDA App
Yeah, I finally got it to 1.50. It took a lot of trial and error and reading and re-reading though. I'm just happy its done finally now.
What's the best app to back up my phone like it is right now before I start trying to do other things to it?
What are considered the must have apps for the Sensation currently, or what are the coolest ones?
Can you add the beats audio to the regular Sensation? Or will it even effect the quality?
*Bump
Hi,
First of all, I'm new to this Forum, but i've been following it for quite a while now since almost everything Android related you can find here. And People around here seem really knowledgeable.
I've trying to update my One SV K2_UL, and i seem to got it messed up.
I was able to flash the update, and everything went smoothely, until i got to the firmware files, a cannot get them to flash.
I guess the problem is my phone is S-ON, and i cannot change it's CID, although a tried several ways of doing it.
And i cannot guet my phone to be S-OFF, i tried Moonshine but it gets stuck on second test. - "Waiting for ADB".
My phone is exactly the same as leegreenaway refers in this post:
http://forum.xda-developers.com/showthread.php?t=2512742&page=9
so i guess, it's not an equipment problem, it was really my order of doing things that screwed this.
Can someone please help me? What can I do?
I tried to revert to old version but with no luck.
Thank you in advance.
Rui
Yes, as long you are S-On, you can't flash the firmware files.
If moonshine don't work for you, you can try the new rumrunner S-Off (which is made from the same people).
Take care on the instructions on the page there, as it is new, i can not really tell you how it will work.
I have tried rumrunner also, it behaved a little different from moonshine since it passed the second test, and found the device, but than nothing, it didn't go further it just said - "Press Enter to Exit.".
Thanks for the fast reply btw.
Then maybe this post, can give you a helping hand.
If you have Norton Antivirus, disable it. Make sure, you have a sdcard in the phone.
I did had Norton in the beginning of my day, but i already uninstalled it, just to make sure,.
I do have a sdcard on my phone.
So i tried running rumrunners once again, and took a ps of what is happening.
View attachment 2398349
When i see it right, you are on windows 8?
Windows 8 is known as not "driver-friendly" related to android/adb.
Maybe you have a chance to use a Windows 7 PC or even Linux.
Maybe @beaups knows whats the problem is...
Yes you're right,
i'm on windows 8.
unfortunately i do not own any PC with win7, althought ADB looks to be working right since i was able to use the shell and other adb stuff, i might as well give it a try tomorrow at work. I just hope i can turn this around, the phone is working great appart from that fantastic noise the speaker makes.
Thank you.
Well, today I tried to use both moonshine and rumrunner at work, but with no luck. The pc at work is running win7, althought the problem persisted exactly the same in rumrunner, in moonshine it was a bit different because it only stopped the second time it was waiting for adb. I was wondering if someone with the orange phone from UK could provide the firmware from that update, and if this souls male a difference.
Thanks again,
Sent from my HTC One SV using xda app-developers app
Last idea on my side:
You wrote in first post, you flashed everything except firmware. That means, you have the Sense 5 software already installed?
I think you should try then with the stock software, moonshine is made for.
Maybe its checking the version (HTC One SV (k2_ul) 2.14.401.6) and fails, because it is wrong.
Well, actually I got that same conclusion in my mind yesterday, just when I arrived at home from work. So I used the 2.14 odexed stock you provided in a thread, and from there I was able to run moonshine, it completed successfully, and after I just had to re-flash the 3.22 odexed, change the cid and flash the firmware. Voila, problems solved everything is in order now.
So the problem was only, the boot img moonshine was trying to flash would never work on my sys version.
Thank you very much for your help, this was a great learning experience.
Cheers,
Rui
Sent from my HTC One SV using xda app-developers app
Glad you got it sorted out.
old.splatterhand said:
Yes, as long you are S-On, you can't flash the firmware files.
If moonshine don't work for you, you can try the new rumrunner S-Off (which is made from the same people).
Take care on the instructions on the page there, as it is new, i can not really tell you how it will work.
Click to expand...
Click to collapse
Thankyou thiese s-off utility helped me to take s-off