[Q] wp7 rom questions - Windows Phone 7 Q&A, Help & Troubleshooting

So what exactly are the risks of flashing? And what are the benefits besides debranding to get NoDo update? (coz that seems to be the only reason lately)
Is there a way to return to original if everything screws up??
(I mean if i flash to another rom, would i still be able to use the back up created by zune previously?)
If i get back to original, surely i would still be able to use my warranty service?
How do you extract your own rom for back up??
I have an unbranded HTC Mozart 7, running NoDo bought in ASIA
Firmware revision number: 2250.09.12902.707
Thanks

The main risk of flashing is that, if it goes very wrong, you end up with a bricked device. Besides that, it almost always voids any warranty you may have. Right now the only benefits are (possibly) a better radio ROM for your locale and updated internal tools/drivers from the manufacturer.
If you're flashing an official Microsoft update via Zune, then Zune backups can be used. If you're flashing a full ROM via some manufacturer tool, then Zune backups are useless if something goes wrong.
Assuming you can find the original ROM that was installed on your device and flash it back on, then I suppose warranty people wouldn't know that it was ever flashed. No guarantee though.

Related

[Q] Possible to restore my backups after flashing a custom rom?

I want to Interop-unlock my Trophy and from the treads i read i need a custom for that. But can i still restore my current backups after installing a custom rom?
I've installed stock ROM in the past which changed the backup folder name (C:\Users\username\AppData\Local\Microsoft\Windows Phone Update\xxxxxxxx - xxxxxxxx - xxxxxxxx - xxxxxxxx) and i couldn't restore my backups
I personally have never been able to get a backup to successfully retake on the phone I took the backup from. Your mileage may vary but I don't think it works.
You can interop-unlock a Trophy (or almost any other HTC first-gen phone) if your firmware version isn't too high. Just rolling back the version should be enough to do that.
However, to answer your question, no you can't restore a (Zune) backup into a custom ROM, not without losing the custom ROM. The backup includes the ROM image, and restoring it completely wipes the phone and restores it exactly as it was before, ROM included.
Can i interop-unlock with Mango or do i have to roll back to NoDo? My phone is dev-unlocked btw.
My current OS version: 7.10.7720.68
I said your Firmware version, not your OS version. However, if you're still on 7720, there's a decent chance (but not a guarantee) that you're OK.
Did you even *try* looking at the official interop-unlock thread under dev&hacking? It's almost always on the first page, very easy to find by search, and linked from the sticky thread at the top. It does require dev-unlock, but you have that...
http://forum.xda-developers.com/showthread.php?t=1271963
Yes trust me i know where the seach button is, tried everything going back to NoDo and follow ansar's guide - also tried your interlop hack.
I believe i should be OK as long as my bootloader is 4.6.
I read your comment in another tread about interop-unlock and full unlock correct me if im wrong, i need to flash the bootloader with a custom bootloader before my phone becomes fully unlocked? And is it even possible to be fully unlocked with stock ROM?
My bad don't know why i wrote the OS version, here is the phone info:
OS version: 7.10.7720.68
Firmware revision number: 2250.09.16907.401
Hardware revision number: 0003
Radio software version: 5.69.09.05a_22.50.50.21U
Radio hardware version: A.102.0.D4
Bootloader version: 4.6.2250.0(129185)
Chip SOC version: 2.2.5.0
Did you try Heathcliff74's app? It uses the same hack as mine but works on more phones; I don't even know why I left my XAP up. I don't know how Ansar's stuff works, which means I don't entirely trust it, but people have reported it working... Of course, he's published enough different things that "ansar's guide" could be any of several procedures.
Your firmware version is surprisingly low for a first-gen phone; I'd expect Heathcliff74's interop-unlock to work just fine. Note that if it's a Verizon Trophy (hybrid GSM/CDMA) there's a few additional steps you'll need to take, which are available in Heathcliff74's "official" interop-unlock thread as well.
SPL (bootloader) 4.6 is too high to install HSPL (required for a custom ROM) directly, but is somewhat easier to downgrade than 5.x (which typically requires a goldcard or similar shenanigans). if you want to use a custom ROM, though, you'll certainly be able to get full unlock.
I'm personally working on a full-unlock for stock ROMs, based on my HtcRoot project. It will require interop-unlock (or NoDo) and at least temporarily downgrading to an outdited firmware, though (2250.*.3XXXX.* works on my HD7).
Yes also tried Heathcliff74's app, but i gave it a try again and it seems to be interop unlocked now. I uninstalled HTC Connection Setup and Heathcliff74's app then restartet the phone which i didn't do the many times before!! After reinstalling the apps it worked!
Does the low firmware ver. mean anything?
Sounds good, looking forwards it
Low firmware version just usually means that your phone's HTC drivers that are used for high-privilege apps (like TouchXplorer, Advanced Config, etc.) haven't yet been crippled. In this case, it's a good thing. However, different phones use different version numbers for the same level of functionality in their firmware, so comparing yours and mine doesn't necessarily mean anything.
You shouldn't have had to either uninstall Connection Setup nor reboot the phone, but I'm glad you got your interop-unlock working!

[Q] How to save the OTA update file

Hi all.
As I said in my previous posts I'm waiting for a operator branded HTC Desire S.
I've read just now that the operator realeased an update few days ago (on 17th of february) and I'd like to know if there is a way to save the update file for future use (warranty purpose mainly).
Infact there is no file for the original brand firmware so if I debrand my phone I'll lose the warranty!
In this case if I can save the update file I can go back to my operator firmware solving the problem!
Thank you in advance!
mylostnick said:
Hi all.
As I said in my previous posts I'm waiting for a operator branded HTC Desire S.
I've read just now that the operator realeased an update few days ago (on 17th of february) and I'd like to know if there is a way to save the update file for future use (warranty purpose mainly).
Infact there is no file for the original brand firmware so if I debrand my phone I'll lose the warranty!
In this case if I can save the update file I can go back to my operator firmware solving the problem!
Thank you in advance!
Click to expand...
Click to collapse
I think what you'd want in this case is probably a RUU. What it does is basically return your phone completely to stock, removing anything you might have done to it. You can find a list of them here:
http://forum.xda-developers.com/showthread.php?t=1002506
I would recommend creating a goldcard to reduce the chance of any error and to help it go smoothly if you ever decide to do it.
Hi dan.
I've read that very useful thread but my operator firmware is not listed there.
So I'd loke to know if there is a way to get the image file from the OTA update (I think it's saved somewhere... but I don't know where!)
Can I ask what network branding your phone has? I'm not entirely sure how to download an OTA update for a stock rom so not entirely sure how to get the ROM from it. Maybe someone can shed some light here. I'm not entirely good with RUUs.
On a side note, if you're going to install custom ROMs I would recommend not updating just to make it easier to install custom ROMs.
Sent from my HTC Desire Saga using xda premium
I'm waiting for a Desire S branded from TIM Italy.
As I said, right now there is no way to find the original branded firmware but now that there is this update maybe it can be catched!!!

[Q] Update after flashing custom rom

Currently I'm having HTC HD7 with Windows 7.5 (7.10.8107.79) Chevron unlocked (9$) ..
Now i need my device to be interop unlocked. I know there is no other way than reverting back method (Healthcliff)..
So, I'm planning to flash to custom roms like DFT
Now Consider that i've flashed custom rom, (not flashed actually now, just consider! )
My questions are ,
1.How can i revert back to official rom , if i need to claim warranty?
2.Will i be able to update the device through Zune (after flashing custom rom)?
3.How do i connect my device to computer, does zune recognize it ?
1: Flash a stock ROM. There are many of them available for the HD7. This should also restore the OSPL.
2: Some ROMs are updatable directly. Others can receive CAB files but you need to send custom CABs. Others can't be upgraded. Read the details on the ROM you flash; there is a considerable variety.
3: Yes, Zune will recognize and sync with a custom ROM (assuming said ROM isn't completely and horribly broken).

[Q] HTC General FlashUtility and OEM Rom Release?

Posting this here in the hopes that someone with more expertise and experience with HTC products will read and respond as I haven't had luck with Google and have only had Motorola and Samsung phones myself.
Very short background:
My friend has an HTC Sensation through TMobile that has been having glitches and random reboots after receiving carrier updates. I told him it wasn't hardware related and could be fixed.
I see 3 options:
1. Backup all data to SD Card/Computer and do a full factory data reset. Hope everything is fixed.
2. Root phone, unlock bootloader, and find a good custom rom to install
3. Backup all data and reflash to an earlier/original HTC Rom
With #2, the phone is out of warranty anyway and I am guessing development for this device has peaked so any custom roms out there are probable pretty stable.
With #3, They aren't very techie and don't care if the phone is rooted or not, but asked me if it was an option.
I know Motorola has RSD Lite, Samsung has Odin, Google has ADB.
Does HTC also have their own proprietary flashing utility that is readily available for download?
Also, how protective is HTC of their phone ROMS/image files and do they still manage to get released anyway--because I would need them to be able to flash.
With Moto it seemed like they would get released involuntarily and then the cease and desist letters would go out and they would be removed.
With my Verizon Samsung Galaxy Nexus, Google freely distributes them on their website, so I have seen both extremes.
#3 may be the best option for my friend since it will basically restore their phone to the software it had before the update and normally flashing a phone is pretty easy and doesn't require root, though it would be nice to be able to block further carrier updates once the phone is restored.
If it was my own phone, I would probably choose #2 since I appreciate developer enhancements. However, I will always keep the factory image files close at hand so I can easily restore the phone if needed.
Has any HTC ROM or image file been released for the Droid DNA yet? The device is carrier unlocked and developer support seems to be strong, but do you guys have an easy way to get back to 100% stock if you need to?

Stock Android ROM on S10e

Hey,
I don't know if I'm publishing in the most correct subforum, since I'm new here on the forum, but I need some help from you.
About a year ago I bought the Samsung S10e and although my experience was good, I miss the stock android I had on my Nexus 5x (previous smartphone). On that phone, I flashed the Pixel Experience ROM to install android 10 verious times (since google only supported it until android 9) so I can say that I have some experience in the matter. The problem came with Knox, and all the impositions that samsung added to make life difficult for nerds who want to control their smartphones.
I am thinking of installing LineageOS 18.1 (unofficial) published here (I don't have much need for VoLTE and VoWiFi, I think).
My question is this: Despite following all the instructions that the ROM publisher wrote, there is still a possibility of something going wrong, a soft brick can occur or even worse a hard brick right? In soft brick, do I still have the possibility to recover it? What about hard brick? My phone's still under warranty until December this year. If I flash a custom ROM, will completely I lose it 100%?
I just want to know what I'm getting into. I don't want to keep a 500€ brick at home.
Thanks.
Look into Warranty Card that came with phone to find out what is covered in your warranty / when you loose it.
Personally think tampering a phone always voids warranty. And Samsung detects this!
jwoegerbauer said:
Look into Warranty Card that came with phone to find out what is covered in your warranty.
Personally think tampering a phone always voids warranty. And Samsung detects this!
Click to expand...
Click to collapse
You're right! I've looked into it and voids warranty unfortunately.. but thats to be expected, I just thought that you could revert back like you can do on some devices when you root, but seems like when knox is tripped, a fuse blows or something, making it impossible to revert back without them noticing the device was tampered.
I've flashed successfully an Android 11 based rom (lineage os 18.1) but then I wanted to try out pixel experience, which was on 10 and now I'm getting a Rev check fail Device 9 binary 8 message. Could anyone help me?
AFAIK an error like this indicates that the phone cannot use the ROM provided ( via Samsung's ODIN loader ) because the ROM is either not legitimate or is a version prior to the one currently installed.
jwoegerbauer said:
AFAIK an error like this indicates that the phone cannot use the ROM provided ( via Samsung's ODIN loader ) because the ROM is either not legitimate or is a version prior to the one currently installed.
Click to expand...
Click to collapse
Exactly what I understood from the error message. Do I have any options right now?
I can flash the recovery, but it doesn't let me access it.
Downloaded Samsung's Stock Android 11 One UI 3 firmware and flashed with odin while in download mode. Device is now booting correctly.

Categories

Resources