Hello,
As unlocking our Huawei Nova became very difficult, I wanted to share with you a service that I bought to unlock my own. It is https://www.gsmzambia.com.
It costs only $3, which is a very low price compared to other known services, and it just works.
Though, the way they operate can be a little scary because they unlock you phone by remotely taking the control of your PC with Teamviewer (you will have to send them your ID + Password), your phone must be connected with USB and set in "Manufacture mode". It works only on Windows with an account having administrator rights because they have to install some phone maintenance and unlock softwares on your PC in order to reveal the bootloader unlock code (As I am a little paranoid, I deleted all my files and made a restoration point before).
The process is very well described in the emails they send to you after purchase.
After the code is revealed by their software, the operator copy/pasted it for me in a text file. And it was done.
So they don't unlock your phone, they just communicate the bootloader unlock code to you. You will have to type the corresponding fastboot command with this code as parameter.
Even if I really think it is safe and they didn't do anything apart from their business, I restored Windows in its previous state, just to be 100% sure.
I really hope this can helps.
EDIT: As @zgfg said, the android security patch is important here. Mine was from 1st march 2017, so pretty old. This is why it worked.
berturion said:
Hello,
As unlocking our Huawei Nova became very difficult, I wanted to share with you a service that I bought to unlock my own. It is https://www.gsmzambia.com.
It costs only $3, which is a very low price compared to other known services, and it just works.
Though, the way they operate can be a little scary because they unlock you phone by remotely taking the control of your PC with Teamviewer (you will have to send them your ID + Password), your phone must be connected with USB and set in "Manufacture mode". It works only on Windows with an account having administrator rights because they have to install some phone maintenance and unlock softwares on your PC in order to reveal the bootloader unlock code (As I am a little paranoid, I deleted all my files and made a restoration point before).
The process is very well described in the emails they send to you after purchase.
After the code is revealed by their software, the operator copy/pasted it for me in a text file. And it was done.
So they don't unlock your phone, they just communicate the bootloader unlock code to you. You will have to type the corresponding fastboot command with this code as parameter.
Even if I really think it is safe and they didn't do anything apart from their business, I restored Windows in its previous state, just to be 100% sure.
I really hope this can helps.
Click to expand...
Click to collapse
What is your Android Security Patch date as from Settings/About?
If your Security Patch date is before June 2018, then there are alse other services where you can buy the Bootloader code for the similar price of 4-5 $
But problems start for Huawei phones with firmwares whose Security Patch date is newer than June 2018
E.g., my Security Patch date is well past June 2018, hence gsmzambia redirected me to their another page/service which costs 12$ (no more 3$), but even worse, page says that such service is offline - hence pretty much as expected, similar situation as with many other services who do not support Bootloader codes for Huawei phones/firmwares with the new (already 19 months old) Bootloader
zgfg said:
What is your Android Security Patch date as from Settings/About?
If your Security Patch date is before June 2018, then there are alse other services where you can buy the Bootloader code for the similar price of 4-5 $
But problems start for Huawei phones with firmwares whose Security Patch date is newer than June 2018
E.g., my Security Patch date is well past June 2018, hence gsmzambia redirected me to their another page/service which costs 12$ (no more 3$), but even worse, page says that such service is offline - hence pretty much as expected, similar situation as with many other services who do not support Bootloader codes for Huawei phones/firmwares with the new (already 19 months old) Bootloader
Click to expand...
Click to collapse
I think your right, I checked my phone and the security patch is from the 1st march 2017. So this is why the bootloader unlock code was easier to discover.
Related
I have an XDA 2 which I haven't used for some time now. I was just about to sell it but wanted to copy some more or less important files (mostly selfmade pictures and some sent messages) from the device before I hard-reset it.
Unfortunately I enabled the security code feature some months ago. Which doesn't mean the SIM pin but the 4 digit security code which the device then asks for every time you switch it on. And of course I forgot that code after that long time.
I know that I can hard-reset the device, and I will to that anyway in preparation for the sale. But as said, I'd like to have these old files before I do that.
An ActiveSync connection does not help because ActiveSync asks for this code as well before it would let me access the device.
Is there a tool available that reads out or clears this code somehow? Something like the ShowPin tool for the SIM PIN? Or do I have to forget about my files?
No one any idea about that? :roll:
not that i know of would not be much of a security code if you could bypass it though....
Rudegar said:
not that i know of would not be much of a security code if you could bypass it though....
Click to expand...
Click to collapse
Well, the same would be true for a Simlock code, however it's pretty easy to retrieve/remove it...
Do you have a backup of the device on the PC (via ActiveSync)? If so, I believe that it disables the PIN when it restores - At least Sprite does and Ithink I recall AS doing it too. Alternatively you could extract the files from the backup directly with the STG viewer?
Can someone please simplify all this for me?
The information on this site is so convoluded in terms of methods, some expired , some still valid, and guesses that are plain wrong, and irrelevancies.
I have been reading, installing, and uninstalling for hours into days.
Samsung Focus
1. Can Mango unlock be achieved with unlock from 7004?
2.I was on NoDo unlock and followed some instructions for the Focus that did not work. It went right to Mango LOCKED (as many others have reported).
I made a nice little back up of my NoDo unlock but can't get back to it using any version of Zune or any method, they all result in restore errors.
My back up might as well be on the north pole because I can't get to it.
3.I flashed back to 7004 and couldn't get chevron to unlock again like I used to be able to on XP or WIN 7 with various zune versions back to 4.7.
I'm wondering if the newer Zunes corrupted that somehow because last time it worked was on a fresh zune install on windows 7.
And besides that, they all ask to be upgraded before they do a back up, usually.
4.But even if it is unlocked at ROM 7004, zune updates (if chosen) will send it back to mango and locks it agian right? That's what happened last time , it just kept updating the phone for hours and then it was back to mango.
5.It appears my only option now is Mango locked or 7004 flash Rom with possible unlock.
Hopefully answers here will help others as well.
A few answers, though not compreheensive:
1) You don't have to let WP7 install each update, if you wanted to stop at, for example, NoDo 7392, you could. Just wait untilt he update gets that far, then pull the plug and/or hit Ccancel in Zune. Left to itsself, it will install all available updates.
2) The phone automatically dev-relocks whenever a major update is installed - this happens even to people with legitimate develop-unlock (and it's annoying!) For Samsung, I believe the technique for preserving unlock is the same one used to get interop-unlock on Mango: place an unlock provxml file in \provxml\ on the phone's filesystem (you can either use Heathcliff74's WP7 Root Tools to do this, or you can just install his interop-unlock XAP) and make sure you have a working version of the Samsung Diag app (should allow you to process provxml files). Once you have that, you can install all the way up to the Mango update safely, I think (I don't have a Samsung, but it should work) and use the Diag app to process your provxml file, which will both dev-unlock and interop-unlock the phone.
Not sure what's up with your backups; I can't really help you there without more information. What error do you get? What version of Zune are you using (you probably should use the latest version, 4.8.whatever)? How big is the backup (it's in %localappdata%\Microsoft\Windows Phone Update\)?
As for what guides to follow, starting with the stickies is always a good idea.
Hello,
I have a HTC Mozart device wich is momentarily running on unlocked NoDo.
I have followed various guides from xda but I end up running a locked Mango (most of the guides require after Mango update to run HTC Connection Setup to unlock... which I am unable to run (black scren) and all other apps tell me revoked by Microsoft).
is there any latest guide a little more foolproof?
It seems that after 18th October something happened with Zune which prevents Mango unlock...
Gyuritzy said:
Hello,
I have a HTC Mozart device wich is momentarily running on unlocked NoDo.
I have followed various guides from xda but I end up running a locked Mango (most of the guides require after Mango update to run HTC Connection Setup to unlock... which I am unable to run (black scren) and all other apps tell me revoked by Microsoft).
is there any latest guide a little more foolproof?
It seems that after 18th October something happened with Zune which prevents Mango unlock...
Click to expand...
Click to collapse
After you install the interop-unlock xap while on nodo then goto mango you reinstall the diag app and in the Diagnosis app dial: *#9908#.. Select "Heathcliff74 Interop Unlock"
then tap Save, tap Close and exit the Diagnosis app
@lucasryan: Those are the instructions for a Samsung phone. They don't work at all on an HTC phone.
@Gyuritzy: Currently, Microsoft is pushing the Mango update and an HTC update together. The HTC update blocks the unlock path used with Mango. If your phone gets that update - which means if it gets Mango through the retail update path - there's no current way to interop-unlock it.
If you can get Mango through an atypical upgrade path (I came from the beta, which worked), or if you use a custom ROM (be *very careful* of the bootloader version if you try this!!), you can get interoop-unlocked Mango on HTC. It's not easy, though.
Ahh i see that i quoted his post now. as alan93 has focus
What solution do I have to load Mango without HTC update? Should I try with RCT2RTM type of packagge?
@GoodDayToDie
#1 - ahh ok, but I'm sure watching the update tentativley is required right? For like an hour and a half.
#2 - now see, there you go again, this is only for dev-unlock people which , i'm not even sure what that is..what? you pay $100 to MS to get it? It needs to be stated more clearly where ever that solution is posted AT THE VERY TOP like this "IF YOU ALREADY HAVE A DEV UNLOCK ....
@ lucasryan - That can't be right, -->"installing interop unlock on NoDo then go to Mango"...STOP RIGHT THERE. when you go to Mango it wipes everything out and you have no more access...unless of course ..YOU ALREADY HAVE A DEV UNLOCK...what ever that is.
I did try the diagnosis trick on update to mango after putting that file on there but the diagnosis version would not go higher than 908 or what ever. Couldn't get 1112 or what ever the one that is needed.
Please, just say there is no way to unlock Mango unless you have a dev unlock and that is low percentage as it is...then I won't expect so much.
Thanks for the replies.
Here is the zune error I get on trying to restore to my NoDo unlock.
http://answers.microsoft.com/en-us/...-restore/3ec7091d-d79d-422c-9995-cfe186e0155b
As you can see nobody is dying to answer it.
I think the code number means "this goon is trying to restore to an unlocked version, don't answer him".
@alan93: Developer Unlock is the term used for the change to your phone made by the Windows Phone Registration Tool (if you have a marketplace developer account), ChevronWP7 Unlocker (possible on pre-NoDo), ChevronWP7 Labs (coming soon), or changing the DeveloperUnlockState registry value located at HKLM\Comm\Security\LVMod to 1 (possible with the LG registry editor, or by using the Samsung diag app or HTC Connection Setup app to process to provxml file). The registry change is actually what matters; the other methods are simply ways to achieve it.
Dev unlock allows you to install XAP files - a renamed ZIP file with some manifest XML files, one or more managed (.NET-based) DLL files, and possibly other files needed by the application. Due to a bug in the application installer, you can also use a XAP to put arbitrary files almost anywhere in the filesystem (the installer can't write to the \Windows\ directory).
One of those manifst files specifies capabilities that the app has, which controls permissions of the app (for example, ID_CAP_ISV_CAMERA allows access to the public camera APIs). As of Mango, including beta versions, it is no longer possible to install apps with the ID_CAP_INTEROPSERVICES capability unless the MaxUnsignedApp registry value (located in HKLM\Software\Microsoft\DeviceReg\Install) is set to at least 300 (the default value is either 10 or 3, depending on the unlock method used). ID_CAP_INTEROPSERVICES is required for interfacing with drivers, a way for applications to run at high permissions (for example, to write to the registry). Each time you install a major upgrade, such as Mango, this value is reset to its default. An app with ID_CAP_INTEROPSERVICES therefore can't be installed (or run, if it was installed before upgrading to Mango) until this MaxUnsignedApp registry value is changed, a process referred to as Interop-unlock (term coined by Heathcliff74 on this forum). Marketplace-installed apps are exempt from this restriction, which is why things like Connection Setup (which has ID_CAP_INTEROPSERVICES) can be used.
For what it's worth, I got my dev-unlock by purchasing a marketplace developer account ($100 from MS). One day I may even submit an app to the marketplace, but so far all the apps I've written use homebrew and wouldn't be acceptable for the marketplace, so I just publish them here.
Thanks great explanation.
I intend to write my own too, I wrote one and have a few more great ideas but didn't want to pay until i made sure I was able to write them completely and testing on the simulator sux. And last I heard, the media player doesn't work with it.
I just think the fee and lockout just hurts development thereby limiting the success of WP7.
If it was $50 or less I would probably pay it.
I mean for crying out loud I'm a certified MCP/MCAD, they should give me a break here.
For a project, I needed a low cost 32GB tablet and noticed that Best Buy was about to introduce a new version of their 10 inch tablet. It is now available and I am creating this post to attempt to gather useful information into a single thread as I doubt this tablet will merit it's own forum.
What is possible so far...
1. Bootloader Unlock
Root Status
I tried Kingroot v3.5 and it was not able to root the tablet.
Links:
Specifications: https://www.insigniaproducts.com/pdp/NS-P10A8100/5855801
Manufacturer and Model: Lightcomm Technology Co., Ltd. MID1023MA http://www.light-comm.com/en/productinfo-176-193-75.html
Brief Review:
The tablet is pretty much what you would expect for a low cost tablet. The build quality is pretty good (it doesn't give much when you twist it, everything fits well) and the screen is better than I had expected. They had the old model on display and this is a pretty good improvement over the previous model. I may do a more complete review but just want to share some observations...
Camera - Low megapixel but fairly snappy response with autofocus.
Crapware - Very little - File Manager, FM Radio, and Sound Recorder - All else is standard android/Google apps
Storage - About 23 GB available (reports firmware is 9.19GB)
Speakers - Adequate but not very good
OS - Android 7.0 - May 5, 2017 Security Patch - No updates currently available
No problems getting ADB and Fastboot acess but will report more after I have time to work with it.
Saved for future use...
Bootloader Unlock
It is possible to unlock the bootloader. NOTE: This may void your warranty and the unlocking process triggers a factory reset. ALSO NOTE: Like many other devices, the tablet will display a warning at every boot that the device is no longer secure.
STEPS:
1. Enable ADB via Developer Options in Settings
2. Enable OEM Unlocking in Developer Options in Settings
3. Via ADB, reboot into bootloader mode
4. Ensure you are able to access the tablet via Fastboot
5. 'fastboot oem unlock' - Follow the prompts
6. Your device will reset (as it explains) and will be bootloader unlocked
Bootloader lock
It may be possible to relock the bootloader. When I gave it the command "fastboot oem lock", I got a message on the tablet asking me to confirm. However, it indicated that I *might* need to put the original software back on. At this point, I wasn't willing to try without a recovery option.
Hi. I just purchased the new flex 11 from BB myself. It appears to have the exact same processor, chip, and GPU as another tablet I have used before. The Lenovo Tab3 8. The only difference I can see is the emmc size (Lenovo 16Gb & Insignia 32Gb respectively) and the screen sizes. The processor is the same however limited to 1Ghz on the Lenovo whereas I believe the 1.3Ghz is the base CPU speed (I think the European version of the Lenovo came with a 1.3Ghz speed). So out of curiosity would the finished Lenovo's TWRP recovery work on the Insignia? Just a thought. Also, in case of brick could you use the Lenovo's firmware to flash it (after modding the scatter file of course). I'm just a noob to development but have no problem getting my hands dirty (I have 2 Lenovo's both broken but modified heavily)
I'm stuck in this in this problem, I can do the Bootloader Unlock but no furder. Is there any update for this device?
Is there a way to know if or when it will be possible to root this tablet?
Hidden Developer Mode
While browsing the net today I came across an article about unlocking the OEM so having a NS-P10A8100 I decided to give it a try and it worked.
Go to your about tablet setting, Model number and tap on it 7 times, a message will come up saying You are one step away from being a developer, this came up 2 times but after I did it the third time and checked my settings the new hidden Developer mode was in my settings and inside was a button, OEM unlocking.
I haven't tried anything else yet as I am new to all this but maybe this will help to get a Root Strategy for this model of tablet.
So it's there a way to fix this piece of sh!!! Cause it's so anointing that you can't even look at it with a ugly face cause it will start to stall.. I'm new on all this stuff so if there is away to fix it or making a little better please put all the steps to do it... Thank you so much!
flash file for this device?
Hey everyone as i mention above have using the device abot a week more, since i get this devices i also used another Xiaomi devices no need to mentions all of them here, so basically it's not a new things for me unlocking, applying, and executes the UBL. day one i use the existing MID to loggin in the micloud/miaccount on my 5s (i've two old existing MID)both of them has permissions to UBL already.
Activating developer mode through setting, and heads to that options, activating debug, oem unlock allowance, and last step binding the MID in miunlock status, day one after many tries its still failed to bind with tost messages said "failed to verify, wait a minute or two, please try again", ok i leaves that for a next day, assuming that i might to hurry doing that. Next two days still gimme the same error, trying to find some post and thread to solve and try some of tutorial to fix that.
signing out the MID, and factory reset the devices setting up as new without signing MID on the 1s settup, log in in MID (Two MID) through chrome and cleaning all devices connected and leaves it empty (not even one devices left connected to that MID), entering MID on the setting app on my devices (try using email,phone number, just the ID) and activating the developer mode and trying to bind the MID in miunlock status , Crap its still gimme the same error (trying winth cellular/wifi).
Okay some told me to create fresh and new account with new number and applying unlock done 24X1 i receved messages granted to unlock. reseting device to factory setting, signing a new and fresh MID and heads to miunlock status trying to BIND the MID again its failed with the same error message.
I do have flashing the devices through testpoint EDL mode to make sure that i'm on official Miui not a fake one, (try both stable,dev, CN and Global) still no luck.. Please can somene here help and share me another guides, thanks
Please ask this directly in the English Miui forum. There you can also check if you still have the unlock permission.
Sometimes their servers are overloaded and it can take some days until they work fine again.
patoberli said:
Please ask this directly in the English Miui forum. There you can also check if you still have the unlock permission.
Sometimes their servers are overloaded and it can take some days until they work fine again.
Click to expand...
Click to collapse
Did it, no attentions there, contacting mi global service through email 4times without solutions yet, and now seems they ignoring my email ni respons at all, F"#£K!!!
I don't know if you need to get a fresh unlock permission for your phone. If you do, then this can take 2 weeks after you applied for it.
1st,
I know there are some threats concerning this issue, but did not found the right hint.
I was going forward and back, again and again - also by offline update, which went well only for the 1st stage:
-1st stage to 10586.107
-2nd stage, only found the cab links for 10586.962 full
but this did fail with same error, does not matter if starting from 8.1 or from 10
Lastly have completly gone back to original ffu 8.1 and than went forward only by using MS-servers...still always the same error <initial download works, then the preparation and install procedure as well, but shortly before 100% the error shows up>
My device should be supported, but later I even spoofed for an RM-1085 from which were used the obviously right boot loader files...I did this before knowing of the log output thought it has to do with lifecycle of the product
pls refer to attached update/install log @the last third - saying there are collisions (0x80070020 - ERROR_SHARING_VIOLATION) and not found files (iot device relelateds?).
Would be fine if someone could inspect the log - escpecially one of the build collector cracks
maybe to try online update or update over USB?
on 10586 make hard reset
enable developer settings and device portal
install Interop Tools https://forum.xda-developers.com/showpost.php?p=74628972&postcount=1071
make interop unlock
change registry to any W10M device (depend did you want AU or FCU), for AU use x30 device, for FCU use x50
now use online update or tool for update over USB https://www.microsoft.com/en-us/download/confirmation.aspx?id=56726
i always do n this way and never have any problem for old 8.1 lumia devices.... but i not recommend upgrade to FCU because AU work much better with old devices
you made my day dxdy
:good::good::good:
can't enough thank you...I will achieve this by pinning your advises onto the wall
not a word too much...this is so useful!
I think I had not the best packages and from now on I do not use "iutool"; the "OtcUpdater" seems so much more reliable - only it is hard to find which packages the files are representing (name scheme)
Also I'll do make hard resets even directly after flashing an full ffu
...will follow your suggestion to stay on AU; currently 14393.1066 - all updates by offline mode
so, :good::good::good: