Hi there
I had 2,17 and upgraded to the leak rom 3.16. I did not use any locker or unlocker when upgrading. I am having issues with mail2web that it sends the same sent email several times. I think there is an active sync bug with the leaked rom. Anyways, I am trying to downgrade back to the official 2.17 and I when try to flash after the intial reboot it tell me error 328 invaild command
can anyone please help??
I had that same problem on one of the other roms. My email issue was fixed by hard resetting and reflashing the same rom. AS far as getting back to a different rom, not sure. You might need to find the older unlocker program from oilpro and cokeman.
Good Luck
As a matter of fact I plan on doing this within the hour. I'm ging to use the Re-locker tool and ill back report back with progress.
*Update*: Re-locker tool worked perfect Find it here
http://forum.xda-developers.com/showthread.php?t=363556http://forum.xda-developers.com/showthread.php?t=363556
Anytime you want to flash an "Official" Sprint ROM, you will need to relock the device.
Also, to make sure the reflash completely overwrites everything, I usually flash a ROM multiple times...
trying to downgrade bricked my mogul
I was having issues with the leaked rom, and wanted to downgrad back to the sprint 2.17, I was also geting error 328. and here is the part that bricked my phone, since i couldn't get teh official 2.17 to load i tried to load a custom 2.17 rom which said it installed 100%. However when i reboot i am now stuck in the preboot screen that says for testing only.
I had pretty much the same issue - upgraded to a 3.16 custom to try it out. Didn't care for the flakiness of it.
To downgrade, you will need to use the relocker to go back. After that I flashed a stock Sprint 2.17. Then unlocked again to get a 2.17 custome ROM.
Related
i upgrade my rom to load dcd rom and now i want to downgrade to 2.17 back for factory file anyone have the unlocker
thedeportee said:
i upgrade my rom to load dcd rom and now i want to downgrade to 2.17 back for factory file anyone have the unlocker
Click to expand...
Click to collapse
if it wont extract try changing the file type to .rar but try it the way it is first
Thank you
the software worked perfectly
downgrade to 2.17
Hi there
I had 2,17 and upgraded to the leak rom 3.16. I did not use any locker or unlocker when upgrading. I am having issues with mail2web that it sends the same sent email several times. I think there is an active sync bug with the leaked rom. Anyways, I am trying to downgrade back to the official 2.17 and I when try to flash after the intial reboot it tell me error 328 invaild command
can anyone please help??
I also think I want to downgrade for the time being.
Where can I find the latest stock Radio and ROM for Verizon?
mike18 said:
Hi there
I had 2,17 and upgraded to the leak rom 3.16. I did not use any locker or unlocker when upgrading. I am having issues with mail2web that it sends the same sent email several times. I think there is an active sync bug with the leaked rom. Anyways, I am trying to downgrade back to the official 2.17 and I when try to flash after the intial reboot it tell me error 328 invaild command
can anyone please help??
Click to expand...
Click to collapse
Run the unlocker posted above, after it's all said and done, you should be at the bootloader screen, just run the update for the 2.17 ROM and it should put it back on. I was having the same problem (328 error) and this fixed it for me.
thank you so much it work forr me defualt got first error then it did the recovery on vista home but it work thanks!!!
FYI the new radio doesnt work well with the old OS.
FIXED! Read below for details.
So i've been messing with my mogul for nearly 4 hours now trying to convert it to dcd's rom..and i've flashed it twice now and after it reboots from being 100% loaded it just sticks on the HTC black screen..I've read and read and searched and searched and cannot find a definite answer. Can anyone help?!
basics?
did you load the radio rom?
did you load the unlocker?
you may need to restart the phone to the boot loader and resend the rom
(press and hold camera and power and push reset button)
I did TRY and reload the radio and unlocker..now im stuck at the black htc screen where it says no radio though. bleh. i can't even get it back up and running. what do i do?
edit:
I'm at the multi color screen..ive tried running the unlocker RUU and then running dcd's ruu and it doesn't work..and the radio RUU does not run at this screen...I can't get the phone back to a working status! Argghhhh. It wont let me run the relocker unless im in activesync...but i can't be recognized in activesync unless the phone is up and functional..so..? how do i relock it to put hte stock rom on to try and unlock again?
I am kinda stuck in the same spot, but mine is is the verizon logo screen, i tryed doing the power,camera and hte reset button but its till stuck, i tryed the relocker but i need to be in active sync
any help?
what i dont get is..i flashed it with the unlocker, then the rom then the radio...isn't RUU just overwriting each one or something? it doesn't make sense to me. and all i can do is run RUU..i did the rom, then the radio and it was stuck in the bootloader so i used the exitbl and got out of it but then it just went back to going to the HTC black screen saying no radio. ..i'm gonna try and flash the rom from a sd card next..we'll see what happens..
jkrolcz said:
I am kinda stuck in the same spot, but mine is is the verizon logo screen, i tryed doing the power,camera and hte reset button but its till stuck, i tryed the relocker but i need to be in active sync
any help?
Click to expand...
Click to collapse
This just happened to me after flashing the ROM but not the RADIO yet. Flashing the Radio fixed the problem.
I've flashed the radio..then its stuck in the BL and i use the program to get me outta it then it just keeps saying i have no radio! what the hell..this sucks. i'm in the worst possible situation to have to buy a new phone
There are three parts to the "operating system" of your phone.
1. Bootloader (also called locker, unlocker, re-locker, SPL)
2. Radio
3. ROM
The three components are saved in discrete portions of the device's memory. Flashing one does not overwrite the others. All three must be compatible for the phone to operate properly. If you stop the upgrade process recommended by the ROM compiler prior to completion, your phone may not operate properly. If you flash the "leaked" 3.16 ROM package, it contains all three components.
To use the 3.16 stock OEM ROM, or a custom ROM based on the stock OEM 3.16 ROM, you must have a level 3.xx radio and a level 2.xx bootloader. The current implementations of those are the 3.27 radio and either the stock bootloader distributed with the "leaked" 3.16 ROM package, or the Olipro 2.40 unlocker.
If you are running a level 2.xx stock OEM ROM, or a custom ROM based on a stock 2.xx OEM ROM, you must have a level 1.xx bootloader and a level 1.xx radio.
Custom ROMs are not always named using the OEM convention, so you must research the custom ROM to determine whether it is based on a level 2.xx or 3.xx stock OEM ROM.
I hope this helps all of you get your phones back up and running.
FIXXXED!
So heres the best description I can give of what was going wrong for me..Its my first time trying flash to a different rom..and well it didn't go so well. First, I used the titan unlocker, then installed the radio (not sure which one) and then some form of the newer dcd rom and i was getting stuck on the black HTC smart mobility splash screen where it said "no radio". I had to have messed around for over 5 hours today at college trying to figure it out by doing different arrangements what order i installed the radio and unlocker and rom in. I couldn't get it to connect with activesync so i couldn't use the titanunlocker.exe..all i was going off of was RUU's. Im not sure whether or not what OS I was using effected it..I was playing in Vista earlier today but had done the correct steps to install the drivers, and now this last time i did it on XP. This last time I ran the 3.27 radio RUU as found.. here ( http://forum.xda-developers.com/showthread.php?t=362563 )...Theeen I ran this form of the newer sprint ROM. (I'm pretty sure they say it comes with a included in this RUU, but i'm just stating exactly what I did) the .651 rom can be found.. HERE ( http://forum.ppcgeeks.com/showthread.php?t=16806 ) He had a error when packing or something so you have to manually rename it to .exe because it was missing a e..I did this within winrar before extracting..ran that and about 10 minutes later it booted up and i've got service. I'm not going to promise that this is 100% functional all i'm saying is im out of that horrid black HTC screen where I can now go on to try and get the correct rom i wanted. Hope this helps..may be a bit confusing and probably did things wrong but this was my first time doing it all.
Hi I'm looking for some help. I tried upgrading my XV6800 to the windows 6.5 rom but I think I might of messed up. I tried to update my radio first but ran in to issues.
I used Oilpro 1.20 to try and tried to update the radio but along the way messed up while trying an older rom and I'm currently at a Verizon screen with the message "NO RADIO" at the bottom. I'm assuming the radio rom was erased. I might have gotten confused with the roms and used a rom without the appopriate Radio. When I try to flash that rom back to a stock Verizon upgrade it just ends 11% in to the flashing process and the rom update utility returns a Error 290 screen.
Currently I can get the oilpro 1.20 bootloader to still load up but I'm not sure what to do at this point. I tried updating the ROM to DCD's older 3.20 roms, which did complete but I still have that screen coming up. Can anyone give me some suggestions on what I should do next? Any help would be greatly appreciated.
Try using NueSPL 2.47 it's more current
Doesn't have have to be run on the phone itself once inside Windows? The only screen I can get up is the Verizon (splash) screen where it normally lists the rom and radio, or the oilpro boot loader screen. I actually can't get back in to windows to run the nueSPL 2.40.exe file.
Is there a way for me to flash the radio back from a bootloader screen and USB or SD card? The thing is I actually tried to take the 3.42.40 radio and use the Flash Rom Utility to see if it would flash the radio rom back on but even though the process completes successfully, I still get the no radio error so I guess it doesn't work. Thanks for the help, I think I may have been a few of the idiots out there who screwed things up and didn't make sure the radio was up before attempting any rom upgrade.
You should've changed the bootloader first. Your radios that you are trying are not compatible with your bootloader.
Flash an old stock rom via SD, then update your bootloader to 2.47 once you can get back into windows, then update your radio, and then your rom.
Yeah that was one of the first things I've tried a USB update back to the stock Verizon 6.1 ROM, but for some reason it prematurely ends at 11% with the PDA Phone Update Utility throwing a ERROR 290 message. This is the first time this has happened as I've flashed with this same rom tons of times. I've been looking online for the past hour on how to flash the ROM from a SD card if I can't get in to Windows. But all I could find was the USB update utility and it ends at 11% Am I doing it wrong? any ideas would be greatly appreciated.
If you can still get in the bootloader then you should be fine....I would put it manually in bootloader holding power and camera simultaneously and poke the hole to get it into bootloader.
Once you do that plug in the data cable and run Olipro 2.40 or Nue 2.47. It should be able to take after that.
Basics steps to flashing a phone:
correct unlocker-->stock ROM-->custom ROM
Most custom ROMs will not include Radios that why you would run the stock ROM first to install the radio and then run the custom ROM. Alot simpler then trying to update the Radio by itself.
AWESOME! I got it back up, thanks guys. For reference purposes I'm going to restate the problem and solution incase other noobs run in to the same issue.
PROBLEM:
I installed oilpro 1.2 during the process of installing a new radio then a rom. Along the way the rom install failed. I tried to reinstall a stock Verizon rom RUU 3.57 & 3.37 radio but it failed at 11%. I was then stuck at the splash screen with a message that said NO RADIO. I could still get in to the boot loader with the power and camera button. But the stock Verizon rom did not install anymore.
SOLUTION:
I used titan_exitbl.exe to exit the bootloader and I went back to an earlier rom found here, rom 2.09 & radio 1.30. That one actually installed. It seems to have worked. I'm back in windows now but I need to uninstall oil pro 1.2 and get nuSPL 2.47 on there before I move further (it looks like while it's still on the stock RUU won't work for me).
Do you guys know how I would go about uninstalling Oilpro 1.2? Will Titan_relocker do it for me? I'm not sure if installing nueSPL over oilpro will do it.
Use this ROm from Verizon to get the Stock 6.1 back up and running. It's the MR2 rom
http://www.pcdphones.com/phone_downloads.aspx?bid=89&cid=1&mid=287&carrier=Verizon Wireless
Beyond888 said:
AWESOME! I got it back up, thanks guys. For reference purposes I'm going to restate the problem and solution incase other noobs run in to the same issue.
PROBLEM:
I installed oilpro 1.2 during the process of installing a new radio then a rom. Along the way the rom install failed. I tried to reinstall a stock Verizon rom RUU 3.57 & 3.37 radio but it failed at 11%. I was then stuck at the splash screen with a message that said NO RADIO. I could still get in to the boot loader with the power and camera button. But the stock Verizon rom did not install anymore.
SOLUTION:
I used titan_exitbl.exe to exit the bootloader and I went back to an earlier rom found here, rom 2.09 & radio 1.30. That one actually installed. It seems to have worked. I'm back in windows now but I need to uninstall oil pro 1.2 and get nuSPL 2.47 on there before I move further (it looks like while it's still on the stock RUU won't work for me).
Do you guys know how I would go about uninstalling Oilpro 1.2? Will Titan_relocker do it for me? I'm not sure if installing nueSPL over oilpro will do it.
Use this ROm from Verizon to get the Stock 6.1 back up and running. It's the MR2 rom
http://www.pcdphones.com/phone_downloads.aspx?bid=89&cid=1&mid=287&carrier=Verizon Wireless
Click to expand...
Click to collapse
Glad to hear you got your phone back up
As far as I know you should be able to just install 2.47 and it will overwrite your old bootloader without problems. I could be mistaken but there isn't really a way to "uninstall" a bootloader, just overwrite it with a different one.
unL33T is correct...just run Nue 2.47 and let it overwrite the old one. 8p
Yeah that's what I thought too, but when I tried to over right it with 2.47 the 1.20 showed up again so I used the titan_relocker tool. Maybe I did something wrong. I'll go recheck, thanks for the replies guys.
Hoping there are people out there with similar issues as me and have found a resolution.
So I was able to successfully debrand my ATT Titan to an EU rom and then flash HSPL 2.5 to my Titan.
However, when I tried to flash a different radio as required by some roms (Deepshining) I noticed that it would remain on the 16.23 radio (which ultimately results in hanging during boot).
Since I couldn't seem to get the radio to flash via RUU or through goldcard I figured I could try reverting back to ospl2.5, apply the HTC provided fix for 2.6spl and try to update via zune in order to get radio 17 or so. ( I read about this possible solution here: http://forum.xda-developers.com/showpost.php?p=32322090&postcount=69)
However, reverting back to ospl seems to be a no go. I keep running into error 384 indicating a sha1(?) checksum mismatch.
Any suggestions on a way to flash radio 17 would be appreciated.
Thanks
I have the same problem. Still no luck to fix it
I'm trying to return my HTC One back to being unrooted because I wanna update it and almost everywhere I read, you need to unroot to get over the air updates. So I got S-Off and I relocked my bootloader, but whenever I try running the RUU, it always fails. I tried flashing it and I tried running the exe file. Why does it keep failing? Also, is it true you can't get OTA updates while being rooted? The RUU I use is for Cingular (which from my understanding is the one AT&T uses) and I have Super CID. Lastly, if anyone knows an easier way to return my phone to being completely stock and unrooted that would be great. Thanks in advance!
Which RUU did you use? Apparently the last official one was JB 4.3 w/ Sense 5.0, ver. 3.17.502.3. The one for KK4.4.2 w/ Sense 5.0, ver. 4.18.502.7 was apparently not actually released by ATT and many people were having problems with it.
clsA said:
Well near as I can tell the RUU did not originate from HTC, someone was able to create it and sign it same as HTC would. But the files behave differently than the "Real" HTC RUU. The only solution I found was to use the True HTC RUU from 3.xx.502.x and OTA to 4.xx.502.x to 5.xx.502.x. It requires s-off to flash the OTA's so it's not the perfect solution for everyone.
Click to expand...
Click to collapse
So if you tried with the KK4.4.2 RUU, download the JB4.3 RUU from http://www.htc1guru.com/. Since you're S-OFF, you can use either the .exe or the decrypted .zip. I used the decrypted .zip before and it worked fine. Once you get that flashed you can then take the OTAs to update to KK4.4.2 w/ Sense 6. You'll need to be on the AT&T network to get those OTA. Otherwise you'll need to manually flash the updates, as clsA states in his post that I quoted above.
As for not getting OTAs while being rooted....
It's not so much that being rooted prevents getting OTAs. It's the process of getting to root that modifies or deletes system files that need to be intact for the OTA to work. OTA need to be installed through stock recovery. If you're rooted, it's most likely that you have a custom recovery. Also, unlocking the bootloader deletes some files the OTA checks for. If those files not there, the OTA will not install.
Flashing an RUU is the easiest way to get completely stock. It resets the phone to an out-of-the-box state. Whereas a factory reset done from bootloader or recovery basically just wipes the data partition, which will remove any apps you installed and user data. But any modifications to the system partition that are done remain. You don't get back the files that are deleted when you unlocked the bootloader.
Also, since you are S-OFF, there's no need to relock your bootloader to run an RUU. That's only required if you're S-ON. And once you get S-OFF, there is no reason to go back to S-ON.
Since I just want to get the new OTA update, do you recommend I just flash the update as opposed to going back to stock recovery because I don't mind having a rooted phone? Also, my phones camera suddenly became blurry, is it possible that the rooting had something to do with it? If it did, would flashing the OTA update fix it or would I need to go back to stock recovery or would neither fix it? Sorry for so many questions.
First off, what version is currently on your phone? Depending on where you're currently at you may need to flash more than one update in order to get it to the latest version. And no matter what, you'll need to flash stock recovery in order for the updates to flash. OTA updates, whether taken OTA or flashed manually, require stock recovery, as I mentioned before. Also, again as I mentioned before, the process of rooting your phone (more specifically, the process of unlocking your bootloader) most likely deleted files from your system partition that need to be in place in order for the OTA updates to install. If they are not there, the update will fail. So to answer your question...No, I don't recommend "just flash the update as opposed to going back to stock recovery". It won't work.
Since you didn't answer my question and state which RUU you tried, I don't know if you tried a bad 4.4.2 RUU or if there are other issues with your device and/or computer that's preventing any RUU from installing. If you just don't want to flash the RUU, then you can try flashing the update in the phone's current state and when it fails, you can analyze the error report, try to track down stock versions of the files you're missing and restore them if you find them, then try the update again, hoping you found everything. That's a lot more of a hassle than just flashing the RUU, flashing the updates, rooting, and setting up your phone.
Another option is to just flash a custom ROM. Most of them will bring the phone up to the latest version. Some will even take it higher than what is officially available from AT&T.
As for your camera problem, can't see how just rooting would cause that, but maybe it did. Without knowing the cause of the issue, I can't say if just flashing the OTA would fix it. If it's a software issue, then possibly it would. If it's a hardware issue, then probably not. Focus on updating the phone and worry about the camera issue if it still persists once updated.
Sorry, I forgot about your question. First of all, I got it working using RUU Zip M7 UL JB43 SENSE50 MR Cingular US 3.17.502.3-decrypted. The one that didn't work for me is RUU Zip M7 UL JB 50 Cingular - 1.26.502.12. Second, I am running 4.4.2. Thats for anyone who comes across this and was wondering. Thanks for your help sharksfan7. Also, in case you were wondering, my camera is still blurry, but I'll start a different thread for that.