Related
http://forum.xda-developers.com/showthread.php?t=518851
I flashed last night from RC33 Rooted to cyanogen's 1.51 build (linked above). This morning I tried listening to some music through the headset (the USB adapter that came with the G1, and a normal pair of headphones). Everything went to a crawl for a few seconds and then the phone just rebooted.
I then attempted to do nothing but change the volume up/down (so the little ping sound would play) and even that caused the phone to crash and auto-reboot.
When the headset is not plugged in, the sound works fine. But it seems that any sound playing whatsoever through the usb adapter causes the phone to crash and reboot. There is also a bit of constant static audible in the head phones, even though it was working fine last night before updating.
Anyone else run into this problem?
-----
I should mention that I did wipe during the update (Alt + W).
-----
I actually decided to try it again. Literally 2 minutes ago I wiped again and re-flashed. I put in my google account and got into the home screen. I did absolutely nothing else.
Then I plugged in the usb adapter, and increased/decreased the volume for about 5 seconds.
BAM crash and reboot once again. Just to reiterate, I re-flashed the update (including a full wipe) less than 5 minutes ago.
(Yes the USB adapter is in all the way; Yes I tried taking it out and plugging it in multiple times; Yes the USB cord to connect to PC and transfer files works perfectly fine. I even tried turning on/off USB Debugging)
Do I need to upgrade anything below? (Does anything look weird?)
Firmware version: 1.5
Baseband version: 62.33.20.08H_1.22.14.11
Kernel version: 2.6.27-00392-g8312baf [email protected] #2
Build number: CRB43
Any ideas?
I just re-flashed/updated to the following build:
http://jf.andblogs.net/2009/05/24/jfv151-images-are-out/#more-88
JFV1.51 CRB43 US (2451)
Same issue =\
Is it possible my USB adapter died somehow since yesterday?...
All the info is the same:
Firmware version: 1.5
Baseband version: 62.33.20.08H_1.22.14.11
Kernel version: 2.6.27-00392-g8312baf [email protected] #2
Build number: CRB43
(But I don't have PDF viewer anymore etc).
Again, do I need to update any of the above? Anyone have any comments?
had some problems, but uninstalled tunewiki now everything works fine,
also check your radio, if what u listed is correct, you have the wrong radio!!
rasturn said:
had some problems, but uninstalled tunewiki now everything works fine,
also check your radio, if what u listed is correct, you have the wrong radio!!
Click to expand...
Click to collapse
- I went into Manage Applications and do not see it listed. (Remember this is immediately after a wipe.) Is there anywhere else I should look to see if TuneWiki is installed?
- Oh really. What radio is the correct one? Link if possible?
just use the jf updater you can find it on the market
rasturn said:
just use the jf updater you can find it on the market
Click to expand...
Click to collapse
"No JF OS Updates found."
So...
1. Is there anywhere else I should look to see if TuneWiki is installed?
2. What radio version # should I have?
3. Do I need to update SPL before the radio? (What is SPL anyway?)
Paul22000 said:
Firmware version: 1.5
Baseband version: 62.33.20.08H_1.22.14.11
Kernel version: 2.6.27-00392-g8312baf [email protected] #2
Build number: CRB43
Click to expand...
Click to collapse
Nevermind. I updated the radio from here:
http://code.google.com/p/sapphire-port-dream/
I now have:
Firmware version: 1.5
Baseband version: 65.50S.20.17H_2.22.19.26I
Kernel version: 2.6.27-00392-g8312baf [email protected] #2
Build number: CRB43
Aaaaaand the sound works with the USB adapter! Yay!!!
(Too bad I ordered a new USB adapter from Amazon an hour ago, lol...)
----
Now, do I need to update the SPL for any reason at all?
Any benefit?
http://sapphire-port-dream.googlecode.com/files/ota-radio-2_22_19_26I.zip
use that radio.
El Daddy said:
http://sapphire-port-dream.googlecode.com/files/ota-radio-2_22_19_26I.zip
use that radio.
Click to expand...
Click to collapse
Wish you had posted 20 minutes ago!
So yeah, is there any reason at all to update the SPL? What benefits does it give?
try lucids program to change the audio version. Maybe it will fix it after a reboot
I havent installed it yet but, I think it just doubles the system partition and is required for haykuro's builds 6.0 and up.
There have been reports of the process bricking phones so read up and use caution before trying.
the new SPL gives u more room on the rom from what i can tell, i didnt do it cause alot of people bricked their phone, if u use a2sd u have room so didnt see the point of taking the risk
El Daddy said:
I havent installed it yet but, I think it just doubles the system partition and is required for haykuro's builds 6.0 and up.
There have been reports of the process bricking phones so read up and use caution before trying.
Click to expand...
Click to collapse
Is that all it does? I think I can live without that, and I'll be using Cyanogen's 1.51 ROM anyway.
So I guess I'll just not risk the SPL update.
Thanks guys. Time to re-do my phone again (I've wiped/flashed my phone literally 7 times today)
I currently have the .6 software and I am trying to downgrade to .5 to root. I have been using various RUUs. Once I run it, all of them get stuck at the "waiting for bootloader" part and the black HTC screen is on the phone. What should I do?
Anyone, please?
bump.......
................................
I have also created a gold card successfully, but im still unable to get to the bootloader screen while trying to downgrade
Try using this one, worked great for me.
Credit to regaw_leinad.
4shared.com/get/2uQunBaV/RUU_Hero_C_Sprint_2276515_R_si.html
Add www as I can't post links yet.
I figured it out... YOU CANNOT DOWNGRADE HTC HERO ON WINDOWS 7
is there another way to revert back on windows 7 or are we stuck?
aandkharris said:
is there another way to revert back on windows 7 or are we stuck?
Click to expand...
Click to collapse
Google "VirtualBox" and start reading.
Or, take the ROM.zip from the RUU and rename it HERC.zup and place it on the root of your SDcard, and flash using the stock Android recovery.
Or, enter all of the RUU commands by hand into ADB.
Your options are there.
Same problem
Same problem here. I have HTC Hero on Sprint. Ver. 2.1-update1 and can't root or downgrade. Anyone found a way to do this yet?
http://unrevoked.com
Does 'unrevoked' work on the updated .6 firmware? I thought it did not.
GoSabres26 said:
I figured it out... YOU CANNOT DOWNGRADE HTC HERO ON WINDOWS 7
Click to expand...
Click to collapse
I am running Windows 7 and had no problems going from .6 to .5 with the .5 RUU. Usually, it would run once, then error, I would exit RUU and start over and it always worked on the 2nd time. I have done it 3 different times with success on the 2nd run of the RUU every time.
Yeah, I rooted it on windows 7 and tested the downgrade on win7 and NEVER once had a problem. maybe it's because I'm using ultimate?
Don't know if I'm replying too late to this but if you right click on the wizard and select run as administrator, the wizrd runs and it lets you downgrade with no problems
Same problem here. I have HTC Hero on Sprint.
Ver. 2.1-update1
2.42.01.04.27 baseband
2.6.29.ba77cf03 kernal
2.31.651.7 software number
and can't root or downgrade to a version that is able to be rooted. Anyone found a way to do this yet?
Have you tried to boot the Hero into Fastboot mode?
Turn your phone off
Hold the VOLUME UP button while turning your phone back on
Start the RUU
That makes it work for me.
Hope this helps.
Tyler1989 said:
Same problem here. I have HTC Hero on Sprint.
Ver. 2.1-update1
2.42.01.04.27 baseband
2.6.29.ba77cf03 kernal
2.31.651.7 software number
and can't root or downgrade to a version that is able to be rooted. Anyone found a way to do this yet?
Click to expand...
Click to collapse
watch the video in my signature it shows how to root the latest update
juniorunprofessional said:
Have you tried to boot the Hero into Fastboot mode?
Turn your phone off
Hold the VOLUME UP button while turning your phone back on
Start the RUU
That makes it work for me.
Hope this helps.
Click to expand...
Click to collapse
I know this post is old, but I was having problems getting the downgrade RUU to run on my friends hero with from computer on Win 7 64 bit. Was receiving the error [170] usb connection error. I currently have the Evo, and adb drivers, android sdk, etc was all already installed for my phone. Ran RUU from the fastboot and it worked no problem. Thanks again
Why did u bump this ancient thread up u don't need to downgrade to root Google z4root its aone click app thatll work on any software build
Sent from my HERO200 using XDA Premium App
[Solved]
Hi there.
I got hold of this second hand phone.
I dont think its been modified in any way yet.
Last night the phone asked me about doing a update. So i did.
After the green progress bar completed i got to a white screen containing a green htc logo. And its stuck there in a loop.
So... I cant turn my device on... whyyyy? :'(
All i can do is to get into the standard htc recovery.
And into the hboot. Some place there it says:
HERO CVT SHIP S-ON
HBOOT-1.76.0007 (HERO10000)
MICROP-010f
TOUCH PANEL-SYN0104
RADIO-6.35.15.11
Aug 4 2009,19:43:30
I have done a wipe and a hard reset. Still it get this white screen on death. (WSOD) Im sodding of to bed...
You now know that it doesnt have a nandroid backup, and that I cant connect the phone via a usb connection to pc. And I dont have any custom recovery installed.
Ive tried to recover from a offical rom with a update.zip copied with a card reader onto the sd. Ive tried a few. The recovery see's the file. But when i try to install it it says "Verification failed Installation aborted"
Ive tried the recovery-RA-hero-v1.7.0.1.img, but without a usb I cant figure out how. Is there a way around for installing RA with just a sd card?
Please, does anyone have a good solution here.
Or some helpfull info to point me in the right way.
Sincererly,
Thor
See these threads similar,... Should be easy to sort.
http://forum.xda-developers.com/showthread.php?t=786938
and http://forum.xda-developers.com/showthread.php?t=787483
Good morning
Thanks, ive been looking at that.
My Win7 pc wouldnt show the ADB Interface in manage devices.
Only thing that pops up is a disk drive called HTC Android Phone USB Device, USB Mass Storage Device and a USB Composite Device.
Im gonna try this on my windows xp machine later today.
Hope it finds my phone, if not... what can i do?
So you need to update drivers as per the link in those threads,... Have you done that already pal?
Sent from my HTC Hero using XDA App
Hi again
Yes, I followed every step on that RUU driver guide on my win 7. But the drivers doesnt pop up as they should.
So I cant install the correct drivers since it doesnt show.
Halfway solution!
I got a breakthrough.
1. Remove the battery and replace it.
2. Hold volume down/up and tap power button. (htc enters hboot)
3. Taps back (enters fastboot)
4. Connects USB Cable (fastboot changes to fastboot usb)
5. Computer finds device My HTC.
Then i run this:
_HTC Hero_RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver.exe
I got this from the htc pages. The software says i have ROM version 3.32.405.1
So i have a newer one installed then the one they have on web!?
I choose update on the software, now it tries to install 2.73.405.5
I got a half working usb connection now.
Fastboot restarted and changed to RUU USB.
Then i get a Error: 140 / 131 Bootloader version fail.
Can it be that the hard reset ive done messed up the bootloader version.
For me it looks like the phone is still in a new version ROM.
Anyone vise got anything to say about this?
Kind regards,
Thor
Aha,.... Ok, thats probs because the RUU you're using is older than the ROM already installed.
Try this one... RUU_Hero_HTC_WWE_3.32.405.1_R_Radio_63.18.55.06P_6 .35.15.11_release_signed.exe
That is the unbranded ROM,...
Wow
Suddenly everything klicked back into place!
Im past the white screen of death!
That RUU link was flawless for my device.
And the fastboot RUU USB installed everything.
Im back in business.
Much appericated m8
No problem. Now do us a favour and put [SOLVED] into your thread title. Thanks.
So...
Any suggestions on what i should do with it now?
Gotta root it i guess.
Then install recovery RA.
Any suggestions for a good rom to try?
Thanks again,
Thor
theres loads, but my suggestion would be villainrom 12 for a 2.1 sense rom, or froydvillain for a 2.2 rom
Ok
How do i know if i have a 2.1 sense rom or a 2.2 rom?
Or was that a dumb question from me, since you meant to install those?
Im kind of new, just left ye olde nokia behind
lol... Ok,... So you used the 3.32 RUU yeah? That is stock 2.1. If you used the other one, that is 1.5. Use BTDAGs guide in my sig to find out how to flash custom ROMs.
I also recommend Villain 12 for 2.1,... Or Froyd for 2.2. Depends if you like the SenseUI or not. Take a look at both in the Dev section.
Ok
Yes, I definitly want to have the Sense UI.
So then i wanna try out installing a villainrom 12 on a 2.1 sense rom.
Settings - Software Information now says:
Firmware version: 2.1-update1
Baseband version: 63.18.55.06PU_6.35.15.11
Kernel version: 2.6.29-063c4d24 [email protected] #1
Build number: 3.32.405.1 CL191507 release-keys
Software number: 3.32.405.1
This is what i have on it now.
I tried doing the phone software update again, when it asked me again.
Got the same error. So I did the usb install over again. All ok again.
Note: The update it tries out is 3.32.405.2 (5.87MB)
So... can i follow BTDAG's guide from here?
Or do i have to downgrade or update something first?
Guess i have to choose Superuser for Android 2.0~2.2 when i do the rooting with androot.
I got a problem in that guide when typing su in the terminal window.
I didnt get the "Super User Request Prompt" as it told about.
Ive now tried terminal from both usb and the terminal emulator.
WHen i try to do the SU or the flash_image recovery command i get permission denied!?
Without su rights i can do the flash_image recovery /sdcard/recovery.img command, since i need the su permissions.
Thanks again,
Thor
Hi again
I cant seem to get the SU rights i need.
Ive used universal nandroid for the rooting! (it tells its now ok)
But i cant flash in the custom recovery image.
Ive now tried a different approach:
1. Installing the ROM Manager and trying out ClockworkMod recovery(its installs ok)
2. Then I boot into recovery by holding the home(house) and power on, I get the white screen of htc death again and it goes into a black screen with a red triangle and a ! on it.
3. Then I release home and power on.
4. Presses down volume up and taps power on.
5. The hero boots into the standard recovery!?
(I think the way im starting up, are reflashing the recovery. am i right?)
Clockwork also have a "flash RA 1.7 recovery" option, ive tried that one too.
But with the same result...
Any one know about this?
Best regards,
Thor Elvin
Solution for life!
After a lot of surfing i found it!
This great tut worked for my device:
http://www.villainrom.co.uk/forum/s...o-Root-The-2.1-RUU-or-OTA-Update-For-The-Hero
I got a blue carebear in the background, and im making a big grin!
Now im rooted and backed up.
Great thanks to Pulser for a great tut.
Edit: VillainROM12 installed 1
PEACE Y'ALL!!!
QUOTE=thorelvin;8284640]After a lot of surfing i found it!
This great tut worked for my device:
Pulser did...
I got a blue carebear in the background, and im making a big grin!
Now im rooted and backed up.
Edit: VillainROM12 installed 1
PEACE Y'ALL!!![/QUOTE]
Dude, nice that you got sorted. I have kids so Carebears are good to have around. Respect to Carebears, and at the same time it would be cool and revisit the forum and thank Pulser, else thank him here as Pulser_g2 (i think). He sort of wrote, reworked the tut originally from the cdma version here. Sorted me too going 2.1 to 2.2. I had shedloads of fun with roms in between but its only thanks to him.
I guess this could be classed as one of those "Circle of life" philosophy budhist type **** things cuz the answer was really where you started, but for me... its all about takin care of the Carebears....
For the record his contract ends around May so get your Hero fix requests in early...!
Soz Pulser... And massive thanks for the opening to a new dimension for my hero...
Hi all,
Yesterday I tried to root my legend to flash a custom rom (CyanogenMod 7).
Everything worked fine until I decided I also wanted to flash an unsigned Data2Ext zip.
So I first Wiped everything, then flashed CM7 ( successful ) and then tried to flash Data2Ext.
This didn't work (I think the error was something like "no signature").
After that I quit the recovery mode and my legend was stuck in a boot loop. Also, when connecting my legend to the pc and trying to get into recovery mode, my Legend was recognized as being "Qualcomm CDMA Technologies MSM". Windows tries to install drivers but unsuccesful, so I can't get into recovery mode anymore.
The only solution I found to get out of the boot loop was to unroot my Legend again. (Using this guide )
However, I still can't get into recovery mode for the same reason (and thus can't root my Legend anymore).
Also, when connecting my legend with the pc when already booted (I'm back to htc sense android 2.1), it doesn't let me get a good usb connection. My phone is charging, but windows says "One of the USB devices attached to this computer has malfunctioned, and Windows does not recognize it".
I think these problems might be related, but the first problem is my main concern, as I want to flash a custom rom again.
I've used many search terms, but could not find an answer that would solve my problems. Does anyone know how to solve this?
Note: I don't have root access anymore and am running Windows XP.
Also, the rest of my phone's functions is working correctly it seems.
Hi!
First I would try to install some FOTA, since you obviously can't install anything else... you might look to Shipped ROMs...
(don't install Froyo if you can, you'd probably end up with HBOOT 1.01 which is not that easily rooted, but still can be done...)
As those are most probably properly signed, you should be able to flash them from SD card, so no USB connection needed...(choose LEGEIMG starting archives, .exe needs USB) - the filename to flash from SD must be legeimg.zip
That should fix your USB connection issues I hope...
Then I'd try to re-root (See stickies in Development)
I tried flashing a FOTA (LEGEIMG_Legend_HTC_WWE_1.31.405.5_R_Radio_47.26.35.04_7
.05.35.26L_release_126592_signed.zip) but I think that's the one I already flashed using this topic. It reads the legeimg.zip but doesn't give me the option to update, so I guess they're the same?
For some reason I now also get the "Qualcomm CDMA Technologies MSM" notification when trying to connect as USB Disk station to the computer, so not the "One of the USB devices attached to this computer has malfunctioned, and Windows does not recognize it" error.
Edit: Now I get the malfunction error again..
Could the solution to my problem be to find the drivers for the Qualcomm thing? And if so, where can I find those?
Edit2: New development;
Legend now freezes completely when connecting to USB. I have to take out the battery to get it working again..
Edit3:
I've taken another look at the hboot screen and it gives me the following info:
LEGEND PVT SHIP S-ON
HBOOT-1.01.0000 <-- isn't that strange, since I'm running 1.31?
MICROP-0816
TOUCH PANEL-SYN07-0103
RADIO-7.05.35.26L
Nov 8 2010,15:24:15
Also, when I try to flash the 2.03 zip from here, it finds the legeimg.zip and asks me if I want to update. When I do so, it tells me "CID incorrect! Update Fail!"
Oh maan, I guess HBOOT-1.01 and 1.31 is not working out then...And since there's no way to downgrade HBOOT, you have to flash Froyo ROM...but to do that you need a goldcard: Here is a HowTo
Then you can flash a ROM with different CID then your own...
note: 2.03 is not Froyo, and since shipped-roms only has RUU, you might look into this: HowTo Extract RUU
And then you just ROOT again
Could the solution to my problem be to find the drivers for the Qualcomm thing? And if so, where can I find those?
Click to expand...
Click to collapse
try using attached driver by replacing the current one on your xp box. had the same problem before. HTH
aw, man! you missed your chance on s-off. anyway, since you're on hboot 1.00+ already (& from the looks of it, you lost your root), Dr Romca's link for rooting should work
Dr.Romca said:
Oh maan, I guess HBOOT-1.01 and 1.31 is not working out then...And since there's no way to downgrade HBOOT, you have to flash Froyo ROM...but to do that you need a goldcard: Here is a HowTo
Then you can flash a ROM with different CID then your own...
note: 2.03 is not Froyo, and since shipped-roms only has RUU, you might look into this: HowTo Extract RUU
And then you just ROOT again
Click to expand...
Click to collapse
Thanks for the help!
However, yesterday I couldn't make a new goldcard, since my device wasn't recognized. I will try to make one again this afternoon, using a W7 machine.
I will let you know the results!
maxq1 said:
try using attached driver by replacing the current one on your xp box. had the same problem before. HTH
aw, man! you missed your chance on s-off. anyway, since you're on hboot 1.00+ already (& from the looks of it, you lost your root), Dr Romca's link for rooting should work
Click to expand...
Click to collapse
Thanks! I will try this as well!
Edit:
Still no luck trying to create a goldcard, since the pc doesn't recognize my device, regardless what type of connection (charge-only, htc sync etc) I select. In windows 7 I also get the device malfunctioned error.
Trying to use the adb command only returns "No Device found" (or sth like that).
Using the driver Maxq1 gave me doesn't seem to work (unless I'm doing it wrong that is)
edit: usb bug fixed
Azaruc said:
edit: usb bug fixed
Click to expand...
Click to collapse
You mean you've rooted your Legend?
I am experiencing the exact same problem as you've described while trying desperately to root my HTC Legend.
I start up Fastboot, run Step1, then go into Bootloader (and also getting the same error message about the .zip file), then Recovery mode, and my computer (W7) recognizes the device at this point as Qualcomm CDMA Technologies MSM, and fails to install the drivers.
When trying to run step2, I get an error message telling me "device not found".
I am also running 1.31 and Hboot 1.01.0000
Would really appreciate some help
I didn't really document my steps (I should have ), but I think the Qualcomm bug was fixed by following this guide.
Let me know if it works out for you.
So let's start this thread by saying I was stupid.
In my desperation to upgrade my ROM I went and flashed my Focus with the new Omnia engineering rom. Stupid yes but it flashed. The reason I did it was non of the Samsung focus retail Roms would flash with the WP7 flashing tool not even the jK2 ROM. Which is suppose to be the basic 7004 ROM.
Every time I flashed it would say "This Rom does NOT match the device" or "this device is NOt retail."
So let me just state I had the "RTM Mango" flash on my device already flashed and worked. I was trying to upgrade the firmware and radio stacks. The phone aways worked and was NOT a demo device.
I have tried to flash:
1. jK2 stock Rom same error as above
2. Rom for v1.4 won't work same error as above
3. Rogers Rom on my AT&T focus same error as above.
Basically the only rom that flashed was the engineering rom for the Omnia.
Now the phone boots (with a Omnia splash screen ) I can get it to download mode I can even use the phone just none of the buttons work! I really just want to get a Samsung focus rom back on don't care if it's not Mango at the moment.
My questions:
1. Anyone got an engineering rom for the focus seems to be the only Roms that can load on my device
2. Anyone got some advise to get it back to a Samsung focus rom?
I know I shouldn't have but it's done and can't cry over spilt milk.....
I would really appreciate the help.
What OS version did you have before and what revision of the phone is it?
Thank you for your reply I appreciate it!
If I used the diagnostic menu to check the Revision it said HW:1.0 which is weird as I thought there was only HW1.3 and HW1.4...
Is there any other way I can check to confirm for you?
I had Mango RTM on it the internal MS one that was leaked to the net. It was mango but the Firmware and Radio stacks where accent! That's why I was trying to flash the bugger.
Any idea?
If I look at the sticker behind the battery it says:
REV1.3
The Diag menu also allows one to check the HW and SW version from the Diag menu it said HW = RV1.0 The sticker on the phone says REV1.3'
Would you like a picture of the sticker?
Why in the name would you flash an entire rom ( bootloader, CSC?)
What's the Omnia7 Rom that you flashed?> details, link?
If you flashed the bootloader from Omnia it could mean a lot problems... because it screws the values for the buttons, and I mean it, you'll no longer have VOL-/+...
Thy to get a Samsung jig to see of you can put it in download mode
---------- Post added at 07:11 PM ---------- Previous post was at 07:05 PM ----------
You should've searched....
http://forum.xda-developers.com/showpost.php?p=11197071&postcount=1
Hi all,
I recently bought a samsung focus through ebay but the phone was stuck in demo mode and I wanted to get rid of the demo.
What I have done is: I flashed the phone with the XENJK1 rom for omnia 7.
now the phone works perfect except these problems:
"down" volume button increases the volume instead of decreasing it.
"up" volume button does not do anything at all.
back button sometimes does not work
start button is not working at all
the accelerometer orientation of the screen is opposite than it should be!
any one got any idea how to fix these?! please!
Click to expand...
Click to collapse
Try to keep pressed the Vol- and power to see if it comes to download mode...otherwise use the 300k ohms JIG...
myphonerules said:
If I look at the sticker behind the battery it says:
REV1.3
The Diag menu also allows one to check the HW and SW version from the Diag menu it said HW = RV1.0 The sticker on the phone says REV1.3'
Would you like a picture of the sticker?
Click to expand...
Click to collapse
No need. I think I got the picture.
Let me guess: you bought the phone on eBay or similar?
I think the previous owner hacked and forced the bootloader of the engineering rom that was previously leaked before the 7004 roms on the phone. The problem is, once there I don't know how you can go back to the original bootloader. I suggest you post this in the general WP7 forum and someone (like ansar) might be able to help you.
I know I was stupid!
I can get it into download mode easily no problem. The problem I have is even when in download mode and I use:
WP7 Downloader 7.05, 7.21 and the one I used to flash 7.41 I still get the error (with the normal UJK2 or even the Rogers ROM's)
"The Device does NOT match with the selected binary"
I have tried the "Phone" alone the "Phone Boot" alone both together and even ESC, PDA etc together and alone (basically every option and combination) with the same error message every time "The Device does NOT match the selected binary"
This is true for each of the WP7 Downloaders (so its not a WP7 Downloader issue).
When the phone had Mango (used the update to mango with the leaked MS internal RTM bits) and I tried to get it back to 7004 with WP7 Downloader and UJK2 or Rogers I would get the EXACT same error.
I am not sure what it's doing, maybe I need to find a Focus engineering flash for the device?
The only flash that worked was the engineering flash for the Omnia.
EnderPsp said:
No need. I think I got the picture.
Let me guess: you bought the phone on eBay or similar?
I think the previous owner hacked and forced the bootloader of the engineering rom that was previously leaked before the 7004 roms on the phone. The problem is, once there I don't know how you can go back to the original bootloader. I suggest you post this in the general WP7 forum and someone (like ansar) might be able to help you.
Click to expand...
Click to collapse
I hope they wont mind the double post but here goes thank you for the replies so far!
BTW it wasn't a EBAY phone At Teched 2011 in Atlanta we attended a ATT event and they gave away "Used phones" I got a Focus. Worked perfectly till I was stupid
myphonerules said:
I know I was stupid!
I can get it into download mode easily no problem. The problem I have is even when in download mode and I use:
WP7 Downloader 7.05, 7.21 and the one I used to flash 7.41 I still get the error (with the normal UJK2 or even the Rogers ROM's)
"The Device does NOT match with the selected binary"
This is true for each of the WP7 Downloaders (so its not a WP7 Downloader issue).
When the phone had Mango (used the update to mango with the leaked MS internal RTM bits) and I tried to get it back to 7004 with WP7 Downloader and UJK2 or Rogers I would get the EXACT same error.
Click to expand...
Click to collapse
It's not porper download mode then... or your device is an engineering sample
WP7_Downloader_Ver_7.05_for_Retail_Device_(Product_Force_Select_MD5_X).exe should flash regardless of the phone id...
What do you see if you go to settings>about>more info?
Ok so tried 7.05 and get a error of: "This Device is NOT a retail device" - HUH?????
How can it not be a retail device I have been using it for ages and even updated it to Mango...
OK About info:
OS version: 7.10.722.68
Firmware revision number: 2424.11.8.2
Hardware revision number: 3.15.0.4
Radio software version: 2424.11.7.2
Radio hardware version: 0.0.0.0
Bootloader version: 5.8.0.8
Chip SOC version: 0.36.2.0
Any other info you need?
What are the values on more info screen?
htc9420 said:
What are the values on more info screen?
Click to expand...
Click to collapse
OS version: 7.10.722.68
Firmware revision number: 2424.11.8.2
Hardware revision number: 3.15.0.4
Radio software version: 2424.11.7.2
Radio hardware version: 0.0.0.0
Bootloader version: 5.8.0.8
Chip SOC version: 0.36.2.0
Is there something I am missing?
myphonerules said:
OS version: 7.10.722.68
Firmware revision number: 2424.11.8.2
Hardware revision number: 3.15.0.4
Radio software version: 2424.11.7.2
Radio hardware version: 0.0.0.0
Bootloader version: 5.8.0.8
Chip SOC version: 0.36.2.0
Is there something I am missing?
Click to expand...
Click to collapse
These values are AFTER you flashed the engineering ROM from Omnia?
Yes sir! this is what I am getting now when I boot my Samsung Confusion (Focus\Omnia) Settings>about>more info
Is it developer unlocked ?
It is very strange that you got an unsigned FW to flash on your device but you can't a signed one , that really tells me that you're holding an developer device.
The way I see it :
1.Do you have a ZUNE backup? try to restore from it.
2.Try to download AGAIN the ROMS ( ATT& ROGERS), try to run the WP& downloader 7.05 on ADMIN mode
http://forum.xda-developers.com/showpost.php?p=14875358&postcount=1
3.Try to EMAIL Samsung and ask them what's up with the device, tell them you used ZUNE update and have them check your IMEI.
From the values you posted, the radio HW is missing the version, the bootloader is newer,....
Yup well it was DEV unlocked when I had it as a focus and Mango, I own a Dev account
Yup signed ones it's saying NO - Is there NO unsigned FOCUS rom I can get onto this monkey phone?
I will try redownload the ROM's
I am running WP7 in Admin mode and even in Windows XP SP3 mode ....
I do have a Zune backup but will it pick my phone up as a Omnia or the same Focus?
myphonerules said:
Yup well it was DEV unlocked when I had it as a focus and Mango, I own a Dev account
Yup signed ones it's saying NO - Is there NO unsigned FOCUS rom I can get onto this monkey phone?
I will try redownload the ROM's
I am running WP7 in Admin mode and even in Windows XP SP3 mode ....
I do have a Zune backup but will it pick my phone up as a Omnia or the same Focus?
Click to expand...
Click to collapse
The backup will restore to the stat when you made the backup. I suppose that was a correct Focus rom.
2424.11.8.2 >> this version tells me you're on Focus you might get lucky with the backup....
On the other hand, what's NOT working when you're running the Omnia7 Rom?
The 7.05 should FORCE the flashing no matter what...unless you have a diff NAND layout than the other Focuses ( this is why so many bricked Omnias), it's the only check that could spit the binary error, it this case you're pretty hopeless...you need to get an pit file and only God knows where you could get it from...