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.
Related
Hello,
Want to know if there is a problem to update my Samung Focus unlocked (not the one with token) from 7740 to 8107 without losing my unlock?
I'm having a backup, but it's a long process if I have to restore it and I always scared to do it.
Thanks
Anikachiktou said:
Hello,
Want to know if there is a problem to update my Samung Focus unlocked (not the one with token) from 7740 to 8107 without losing my unlock?
I'm having a backup, but it's a long process if I have to restore it and I always scared to do it.
Thanks
Click to expand...
Click to collapse
You have a backup, thats good (make sure it shows up in Zune)
What I recommend to do is go to "C:\Users\[username]\AppData\Local\Microsoft\Windows Phone Update"
And copy the file that's called something like "f3874e8d - c6f37f88 - c1504a27 - f0452346" to another location (external HDD or so) just in case the update deletes the backup you have (has been reported in some threads, but shouldnt happen)
---
Secondly if you update from 7740 -> 8107 nothing should change in terms of Unlock & Interop Unlock so you should be safe to just update it through the Zune program. A good mate of mine uses a Samsung and updated earlier this week tp 8107, and its still (interop) unlocked so..
IF however the phone gets locked (which I highly doubt will happen) you can just restore the backup you have and nothing bad will happen while restoring IF you leave your phone plugged in (I did the mistake of unplugging it during a restore... worst mistake ever! )
---
That said you should be safe, just plug it in and update to 8107.
If the device happens to get locked, just Restore, you have 2 (the same) backup files anyway so you're safe
Good luck!
[edit] the only device (so far) that is affected aka locking the device again is the Samsung Omnia 7, that is NOT cause of the 8107 itself but cause of the KK2, from Samsung, update paired with the 8107.
IF your device gets locked and you think its cause of that, and you have restored it through Zune, AND you still want 8107, read this. Scroll down to Samsung section and read how to do it (its in red)
Wow, thanks! I'll do it maybe tomorrow, let you know
Anytime,
take yours the thread aint going anywhere.
Hope it works!
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!
Hello folks,
I know there are a lot of threads going around that cater to this topic but I had just one little question. I have an Omnia 7 (8107, updated via zune) which is developer unlocked (no interop).
Is there any way, or will there be any way via which I can put custom accent colors on my phone?
I loved doing that using advanced config but I flashed my rom & all the changes I made were lost.
Also I loved having the 3g/2g toggle button, but ever since I flashed the new rom & updated it is no longer there. Is there anyway by which I can get back the toggle?
Thanks!
Why didn't you interop-unlock again? You can still use Advanced Config or similar apps if you do...
Use WindowBreak or any of the Interop-Unlock apps. If your firmware is incompatible, roll back first using Zune (it should be the last update, so easy to restore).
Hi, Thanks for replying. I don't want to roll back because I am unable to! I have a backup restore but my phone never restores to that point (gives me a weird error, I don't remember the code right now, my phone reboots twice and the restore fails giving me an error code. I did some digging around but didn't find anything useful)
It's the same story with ALL the restores that I have, I cannot roll back to any of those. Does windowbreak work on 8107?
Thanks for replying!
I said firmware, not OS (7.10.8107 is an OS build version). 8107 doesn't matter one way or the other, but some phones get a firmware update (Samsung's KK2 update) that disables hacks like WindowBreak and the other Interop Unlock tools.
Oh okay
my specs are :
PDA : i8700xxkk2
phone : i8700xxki1
csc : i8700xenjk1
So I guess, I have the kk2 which won't let me run windowbreak or any other tools. Am I right?
japmeet said:
Oh okay
my specs are :
PDA : i8700xxkk2
phone : i8700xxki1
csc : i8700xenjk1
So I guess, I have the kk2 which won't let me run windowbreak or any other tools. Am I right?
Click to expand...
Click to collapse
japmeet, unfortunatly kk2 was just to break the project, nothing more.
I have an Omnia 7 and i can give you two advices about what i did:
A)First, i have downgrade to 7.0.7004.0 and run windowbreak or chevronwp7 and then u can update,i suggest manually to 8107 : http://forum.xda-developers.com/showthread.php?t=1306415
B) I also tried after downgrade to 7.0.7004.0, done a clean reset and tried the custom already unlocked roms:
mi7ROM from mirolg: http://forum.xda-developers.com/showthread.php?t=1499102
xda-devs from ceesheim: http://forum.xda-developers.com/showthread.php?t=1533229
Maybe you can try it!
Thanks for replying but doing so will result in a loss of my text messages which I don't want to go through again. I think I'll wait until the devs come up with something that can break the kk2's defences. Thanks!
After manually installing Tango (8773) on my Samsung Focus S and using Jaxbot's workaround to keep it Interop unlocked, I keep getting an alert that a firmware update is available. Is it safe to update the firmware without losing my Interop unlock, or should I keep it at its current state?
revxx14 said:
After manually installing Tango (8773) on my Samsung Focus S and using Jaxbot's workaround to keep it Interop unlocked, I keep getting an alert that a firmware update is available. Is it safe to update the firmware without losing my Interop unlock, or should I keep it at its current state?
Click to expand...
Click to collapse
before updating you must make sure that you have done all your unlocks, interop, MMS, de branding, jaxbot relock work around etc,
you then must make a backup of your phone,
then you can apply the Samsung update, this WILL stop you unlocking, however because you have the unlocks already applied you will be able to re apply them if needed, (it wont allow you to add new xml data but as it was already applied before the update then you should be ok)
if you need to update your OS again I would strongly recommend that you revert to your PRE Samsung update backup
apply the new OS update,
make a new backup before applying the Samsung update again,
re apply the Samsung update an go from there.
ive heard of people having issues restoring backups when jumping across different versions of OS so making backups at each OS update BEFORE the Samsung update is probably a good habit to get in to,
its also a good habit to check that it is in fact interop/dev unlocked before applying the Samsung update
Firmware updates will not re-lock your phone (at least, none of them ever have). What they can do is prevent future hacks (unlocks or otherwise) from working.
If you already have WP7 Root Tools installed and working, you probably are afe to update. I do suggest creating a restore point first though, and backing up your old one.
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.