[Q] Possible to restore my backups after flashing a custom rom? - Windows Phone 7 Q&A, Help & Troubleshooting

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!

Related

[Q] Reading Backup Data

Is there a way to read the WP7 backup data files on my PC?
They're encrypted, apparently with a device-specific key, so not as far as anybody has found.
By the way, this is a question better suited for the Q&A sub-forum.
Moved to WP7 Q&A
As GoodDayToDie says WP7 Q&A is the best place for this.
Please follow the guidelines outlined in the read before posting sticky.
Take it easy
O_G
Zune don't see my Pre Mango State any suggestion?
As in, you connect the phone and the software doesn't see it? What phone is it, what build is it on, have you made any modifications to it (custom ROMs or registry edits or anything), and is it in Tethering mode? Those are the usual culprits.
I have a Htc Trophy alias Spark updated to Mango,and I would like to go back to Nodo for downgrade Spl and install DFT...I never did any edit or installed custom Rom.
Sorry emaf83, you're still going to need to be more specific about the problem. Are you saying the phone is currently on Mango and Zune can't find your restore point to roll it back? Are you saying you flashed a Release NoDo ROM and now Zune doesn't see the phone anymore? Are you saying you rolled back to pre-Mango using Zune and now Zune doesn't see the phone anymore? Are you saying something else entirely?
Please explain what you are expecting to find but aren't finding, or what you're looking for. Also, please describe the current state of the phone (OS version, does it run normally, etc.)
If you're looking to downgrade the bootloader, one possibility is to find an official (RELEASE) ROM and flash that. This can be done on the original bootloader. I've been able to do this with 4.x SPL to downgrade it to something that works with RSPL/HSPL. Reports of whether that downgrade method works with 5.x range from "I think so" to "No" to "this may damage your phone" though, so be careful.
Pre Mango State is back up I did to install the beta of Mango whitout being developers...
The guide said to copy the folder to back up that was in the path C:\PreMangoState\, and place it in the folder C: \ Users \ username \ AppData \ Local \ Microsoft \ Windows Phone Update \. I did everything but Zune does not recognize the restore point. The phone has no problems with Mango runs well here are the specs:
Version OS: 7.10.7720.68
Number revision firmware: 2250.21.40600.177
Number revision hardware. 0003
Version software radio: 5.69.09.05a_22.50.50.21U
Version hardware radio: A.102.0.D4
Version bootloader: 4.6.2250.0(129185)
Version SOC: 2.2.5.0
In bootloader:
PC40100 SS-BC (4K)
SPL-4.6.2250.0(129185) MNG
MicroP(LED) 0x09
TUOCH A1(v10,20)
SD SANDISK 7580MB
Partition Info-v211v413
I cannot flash it whith an official Rom because the firmware of my Austrian operator A1 (CV 177) not found! I can also do the unbrand,but using the method of the Gold Card, you also need an Android phone that I don't have. Sorry for my bad English Anyway, thank you for your interest.
Well, if you're going to use HSPL and flash a custom ROM anyhow, it doesn't really matter if the ROM you flash matches your carrier. You just need any official ROM that is old enough that it will have an SPL (bootloader) of version 3.1 or less. The ROM *does* need to match the phone, but doesn't have to match the operator.
If your backup is in the Windows Phone Update folder but Zune isn't seeing it (it should show up in Settings -> Phone -> Update -> Restore button near the bottom), then this approach may be the best.
I understand,but I don't have a SPL 3.1 or less...my SPL is 4.6.2250.0...and then I have to do the downgrade. But when I go to flash the ROM crashes and gives me " Invalid Id Error " and the phone restarts...because it don't corresponds to my operator.

[Q] How to update diagnosis?

Hi, my samsung omnia 7 (7740) has 0.628 as diagnosis menĂ¹. Interop unlock doesn't work with that. How can I update my diagnosis app?
If you read the Interop Unlock thread, I'm pretty sure it has directions. If you doa search, I *know* there are directions. If you instead make a new thread about it, you may get snarky answers.
That said, just un-installing Diagnostics from the app list, then re-installing it using the phone dialer, will install the new version (assuming your firmware has been updated to a new version since you installed it before).
Maybe i made a new thread because this doesn't work? I'm on 8107 now and diagnosis 0.628 installed again. I'm going back to 7740, but I don't find a solution to update diagnosis.
Well, if you want people to assume you've read the relevant info, it's a good idea to mention the things that somebody who has read it (and still can't update) would have told us, like:
A) The fact that you actually tried the standard update method already.
B) The steps you took and the result of them.
C) What firmware (*not* OS, firmware!) version your phone has.
That said, if the standard method doesn't work for you, I can't really help here. You could try a custom ROM if nothing else is working, I guess...
Firmware : 2424.11.11.2
Hardware: 3.15.0.4
Radio : 2424.11.9.1
Hardware radio : 0.0.0.800
Bootloader : 5.11.1.8
SOC: 0.36.2.0
I don't like custom rom for now, it's v1 and still not full stable..waiting..

Flash AT&T Focus Flash back to stock for Tango...?

So I used the disconnect internet trick and got Tango to install on my phone. Problem is, it stopped with the 3 updates and did not install (or find) the Samsung one that I know was supposed to be installed (for firmware), so my firmware is now 2103.11.10.1 instead of what it is supposed to be.
Does anyone know a way to force the OEM firmware to be sent to Zune. The internet disconnect trick isn't work now, so I'm stuck. Also, my backups aren't showing up, even though during the update process it said it was creating a backup (for all the OS updates it installed all the way up to 8773).
If there is no way to get the OEM firmware to be pushed, does anyone know how to get the Focus Flash to stock? I know I have a backup on my computer, but Zune isn't recognizing it (I had forced 8107 on my phone, and Zune made a backup of that ROM).
I just updated to Tango using the cab sender on my Focus Flash. Everything worked fine. My firmware ver. is the same as yours. It has been that rev since as far as i can remember. I don't think there is a firmware newer than that for the Focus Flash.
Firmware is 2103.11.10.1
OS ver is 7.10.8773.98
b4malevolent said:
I just updated to Tango using the cab sender on my Focus Flash. Everything worked fine. My firmware ver. is the same as yours. It has been that rev since as far as i can remember. I don't think there is a firmware newer than that for the Focus Flash.
Firmware is 2103.11.10.1
OS ver is 7.10.8773.98
Click to expand...
Click to collapse
Someone at wpcentral posted this for their Focus Flash:
Look like Firmware Update, Radio Software, BootLoader
Firmware Revision 2103.12.05.04
Hardware Revision Number 23.1.0.8
Radio Software Version: 2103.12.5.4
Radio Hardware Version: 0.0.0.6
BootLoader Version 6.5.17.0
Chip SOC Version 0.74.21.1
So there must be one out there (plus, everyone else has been receiving firmware updates, like Nokia, so I can't see Samsung not making one).
Since you used the debrand trick to update to 8107, you'll most likely have to reset your phone to get the Samsung update. I did the same thing & then did the cab send method to update to 8773. Didn't have any problems. Kept trying to get the Samsung update via the disconnect trick. No luck. As soon as I reset my phone, it popped right up. I'm installing it now. Good luck.
Steve

"Downgrade" WP7 OS using offline files and Zune

As it looks like theres no way using a Developer unlocked Mobile to run Apps or now that Samsung have blocked the Interop Unlock - even when you restore.
Is it possible to download a Previous update and "update" the phone that way. An update that doesnt have the block and so it doesnt affect the data on the phone?
Thanks in Advance.
"Updating" to an older version is not possible, no. It might be possible to spoof the current version to an old one, if the phone is interop-unlocked, and then "upgrade" to a firmware release that's actually older than your current one... but even that might not actually work, if the updater checks the checksums of the "old" files. It wouldn't work with OS updates for sure; those contain differential (rather than canonical) patches.
Installing an old, stock ROM with the old firmware does work. However, while this is possible with Samsung gen1 phones, I don't believe anybody has found a way to do it with gen2 phones yet.
Finally, restoring a phone backup (as made by Zune when updating, or as made using the Easy Backup tool which just spoofs the update process), definitely does restore both your unlocks and your ability to unlock - that is, it restores the registry (where the unlocks are controlled from) and it restores the firmware (where the ability to unlock is implemented). If this didn't work for you, it's due to one of two things:
A) Your backup (more properly called a "restore point") was created at a time when your phone already had relocked and lost the ability to unlock.
A.1) You can use an older restore point, if you kept them (which I strongly recommend); just move it back to %LOCALAPPDATA%\Microsoft\Windows Phone Update.
A.2) Before you ask, no, you can't use somebody else's restore point; they have device-specific encryption that we haven't broken yet.
B) Your restore worked, but trying to interop-unlock again failed because you updated your Diagnostics app from the Marketplace.
B.1) You can undo this by first uninstalling Diagnostics from the app list, then re-installing it using the phone dialer.
The other option is to use the stock flash tool and just update to Mango from stock.
I have the files for the Samsung Focus v1.3
I can upload them, but if you use it on another device, or on v1.4 it might brick your phone.
Just say if wanted.
I have used it a number of times, because of screwing up my phone and it not being able to boot up, even after formatting.
You will just need to put the phone into download mode, and it takes about two minutes.

Any way to downgrade from Nougat to MM without losing FP Sensor,Haptic Feedack&Camera

Any way to downgrade from Nougat to MM without losing FP Sensor,Haptic Feedack&Camera
I recently purchased a new S7 not realizing that it was equipped with a Nougat OS. I would like to restore my current phone to the new one, but my current phone runs on MarshMallow. After restoring the backup, my new phone has no haptic feedback, no fingerprint sensor with "an error has occurred with the fingerprint sensor. if this message appears repeatedly, restart your phone" message and the Camera doesn't work.
I'm sure it has something to do with bootloader N using MM. Even restoring Stock Marshmallow firmware (Including BL) on the new phone removes these functions. Does anyone have any ideas on how I can get these to operate?
My current phone has
Bootloader Version: G930W8OYA2APK3 (MM)
Baseband and PDA Version: G930W8OYA2API1 (MM)
When I restore my old phone to the new one, it ends up with
Bootloader Version: G930W8OYA2BQK4 (N)
Baseband and PDA Version: G930W8OYA2API1 (MM)
EDIT: Just tried the Nougat firmware with MM Bootloader. All of the functionality is present.
Bootloader Version: G930W8OYA2API1 (MM)
PDA Version: G930W8OYA2BQK4 (N)
Just restored old backup with MM bootloader (Boot, Data, System only).
No Fingerprint Sensor or Camera.
BTW, ignore the HAPTIC FEEDBACK portion of this post. I believe it is working.
Any help with this matter would be greatly appreciated.
Not possible to downgrade since the bootloader block you from flashing lower version of that. You may try to flash without BL, but your phone will be malfunction
Thank you for your reply. I don't think I'll be able to get the fingerprint wizard to work but having a functional camera would be a necessity. From the System/Priv-App folder I copied the SamsungCamera5 (from MM) and the SamsungCamera6 (from N) onto an SD Card. I guess I can try to play around with them to see if either will work, but I don't think they will since my restored backup should already have SamsungCamera5 and the SamsungCamera6 apk probably isn't compatible with MM. Kinda disappointing that I'll have to continue to use my old phone with a broken screen instead of the brand new one I purchased.
Sleaze0 said:
Thank you for your reply. I don't think I'll be able to get the fingerprint wizard to work but having a functional camera would be a necessity. From the System/Priv-App folder I copied the SamsungCamera5 (from MM) and the SamsungCamera6 (from N) onto an SD Card. I guess I can try to play around with them to see if either will work, but I don't think they will since my restored backup should already have SamsungCamera5 and the SamsungCamera6 apk probably isn't compatible with MM. Kinda disappointing that I'll have to continue to use my old phone with a broken screen instead of the brand new one I purchased.
Click to expand...
Click to collapse
do not flash AP from a firmware set made prior to the bootloader youre on, it will more than malfunction, itll probably brick
i went back and read all the tl : dr stuff and saw that you seem to have got it working, oddly enough. The camera issue is likely the kernel
Thanks for the info on the thanks button. I've just about given up trying to get Marshmallow to work properly on this phone. Looks like it'll take weeks to configure my new Nougat phone to be similar to the three years of tweaks I've made to my old MM one. Oh well, first world problems I guess.
As others have pointed out, you can't use Odin to successfully flash a ROM with a bootloader that is earlier (in version) than the bootloader you have installed. The "gatekeeper" is Odin, however, not the bootloader.
Though I haven't tried it, it is my understanding that there is a way around this. Install TWRP, and use it to install a custom ROM which uses the version of bootloader that you want/need. Once the bootloader has been rolled back, you can use Odin to reinstall Nougat (or whatever). I don't know whether this might require a particular build of Odin, but I doubt it
Droiderat said:
As others have pointed out, you can't use Odin to successfully flash a ROM with a bootloader that is earlier (in version) than the bootloader you have installed. The "gatekeeper" is Odin, however, not the bootloader.
Though I haven't tried it, it is my understanding that there is a way around this. Install TWRP, and use it to install a custom ROM which uses the version of bootloader that you want/need. Once the bootloader has been rolled back, you can use Odin to reinstall Nougat (or whatever). I don't know whether this might require a particular build of Odin, but I doubt it
Click to expand...
Click to collapse
i cant even begin to imagine how/why that would work. the bootloader doesnt really care what ROM you install, its the other way around. The ROM being installed has to be compatible with the bootloader. So, installing a ROM wouldnt really do anything to the bootloader and therefore wouldnt be able to bypass the lock in knox.
The procedure I outlined apparently works where the custom ROM includes a related bootloader. Thus, when it is installed via TWRP, it replaces both the existing ROM and the bootloader. I know that TWRP can be used to install a bootloader, as I have done it (on a SM-930F). And if the gatekeeper is Odin and not the bootloader itself, then this could work.
As I stated, I haven't tried this, nor have I extensively researched it. I've only read about it, and am passing it along as a possible solution.
This post can be closed since the phone was deemed Lost or Stolen by the carrier, therefore they couldn't unlock it for me to use my SIM card. I've since returned the phone. At least I learned a few lessons for my next one. Mainly, back up the phone when you first get it. Thanks again for all of the feedback.

Categories

Resources