So after almost 3 weeks of trying and trying and trying to unlock the bootloader on my new RN3, it finally happened. I had grown so used to seeing the 50% error, that i couldnt beleive my eyes when i saw the percentage figure move past 50% mark, and before i could realize, the MiFlashUnlock program had give a big green confirmation on the unlock.
So here is how i did it.
As a prerequisite - Go through this thread http://en.miui.com/thread-342144-1-1.html and try out everything from onwards. It has some helpful tips and I found this thread to be most comprehensive than any other thread.
If it doesnt work, try these:
Part 1.
Check how many devices you have EVER enrolled on your MI account. Now, the idea here is to ensure your current device is the ONLY device you EVER enrolled on your MI account. If need be, you should create a new account.
1.a - sign in to i.mi.com and verify your current device is listed.
1.b - goto the below link on chrome [replace the XXYYZZWWAA with your MI ID]
https://device.id.mi.com/dev/web/us...ang=cn&frameId=hidden_message_frame_1&userId=[highlight]XXYYZZWWAA[/highlight]#index
1.c - if the page loads fine, you will see something like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1.d - right click and do inspect
1.e - the chrome web page inspector will open. Now go to 'Source'. it will show the source code of the javascipt file. Make sure the name of the file you are looking at is jquery-1.8.3.min.js. Click on "{ }" at the bottom of the window to pretty print the file.
Now scroll down to line 4505 where it says "c.text = a.responseText"
The purpose is to inspect the value in 'c' that is returned by the server. Insert a breakpoint at line 4504 (not 4505) by clicking on the number 4504 (a blue highlight will be shown).
1.f - once you have inserted the breakpoint, add "c.text" into 'watch' by right clicking clicking "add to watch". Then just do a refresh in the main window. The page will reload and stop at the breakpoint. Then press F-11, to step into line 4505. Once you do this, you will see the value of c.text getting populated. This is all you need. Just right click and copy the text and paste into a notepad.
1.g Now, what are we looking for? These things:
- make sure this is the only device you have on your MI account.
- ensure your device is correctly reflected, i.e., check the name, status should be 'ONLINE'. Dont bother about the phone number (more on this in Part 2)
- If you have multiple devices, follow Part 2 to remove the device in question and add it to a NEW ACCOUNT.
As an example, refer this screenshot which shows multiple devices (all deleted/ removed) on my OLD account.
1.h In case you have only one device listed here, then you need to ensure the device is showing online most of the time, and not just when you login in to the i.mi.com website and do a find device. Read Part 2 to ensure chances of reflecting online are better.
Part 2
how to ensure you have only one device on your MI account that has EVER been enrolled.
Simple solution - create a new account with a new phone number and a new email ID. Follow these steps if you have access to a seperate SIM:
2.a - remove the device from your existing MI account by (1) - signing out of the MI account on your phone and (2) - removing the device from the i.mi.com console. Do both the steps to ensure the device is completely removed.
2.b - Create a new MI Account on i.mi.com by using the separate email account. No need to enter a phone number at this stage. Sing in using the email ID / new account number to ensure it works. Again, no need to enter a phone number.
2.c - insert the new Sim (preferably one that has never been associated with an MI account) in slot 1 (this is critical)
2.d - flash a new MIUI rom (you can use global dev version) via EDL. When it comes to the MI account sign in, enter the new account ID and password to log in. Login using the account ID as there is no phone number on record.
2.e - once done, go back to i.mi.com and sign in and when it asks about second level sign in (the one where it sends a sms to you phone number, ensure it is sending it to your new phone number - if there is no phone number, ensure you add the number at this stage.
2.f - make sure the device is now listed on the console. You can repeat Part 1 to make sure only one device is visible at back end.
2.g - also ensure your device and ROM version are correctly listed on the MIUI form settings page. Refer the MIUI forum link i posted above.
2.g - goto Part 3. Ensure you have the sim installed all the time and you are online through a data connection.
Basically, what you have done is removed your device from the old account and added it to the new account.
Part 3 - this has been fairly discussed. Apply for the unlock permission and wait for confirmation. once you have got it, download the tool and try to unlock.
Just to let you know - i successfully unlocked my phone with this process. I was able to unlock within a few hours of receiving the confirmation message for the new account.
Good luck.
Hit thanks if this helped you
I cannot find jQuery1.8.3.js
Any workaround ?
T3h said:
I cannot find jQuery1.8.3.js
Any workaround ?
Click to expand...
Click to collapse
why cant you find it? whats the error?
can you post a screenshot or something
Unable to add breakpoint at 4504. It automatically goes to 4505.
Even after devId and ChannelId shows, I was only able to unlock officially when my mobile # and model was showing inside _phone :[<inside this>]. i think unless it shows, you will get the 50% error. And for me to have the details shown I had to flash dev ROM + added Xiaomi account and avoided adding any account till xiaomi account sync as well as all the other operations like Find Device( from phone + mobile browser) is complete. Also, I had added my phone number into the phone settings.
Note: Miui version was not showing in the forum settings but I was able to unlock. So, that as others referred to as required was not for me (But I had changed device correctly in that page ).
Hope this helps.
Edit: I also made sure only one SIM (one used for request unlock) is present in the 1st SIM slot while doing the DEV ROM flash. DEV Rom (EDL flashed this fastboot: kenzo_global_images_6.8.18)
Thanks
Sent from my Redmi Note 3 using Tapatalk
T3h said:
Unable to add breakpoint at 4504. It automatically goes to 4505.
Click to expand...
Click to collapse
add it to 4503 or anything just a bit before 4505 and keep stepping in using F11.
rajumack07 said:
Even after devId and ChannelId shows, I was only able to unlock officially when my mobile # and model was showing inside _phone :[<inside this>]. i think unless it shows, you will get the 50% error. And for me to have the details shown I had to flash dev ROM + added Xiaomi account and avoided adding any account till xiaomi account sync as well as all the other operations like Find Device( from phone + mobile browser) is complete. Also, I had added my phone number into the phone.
Note: Miui version was not showing in the forum settings but I was able to unlock. So, that as others referred to as required was not for me (But I had changed device correctly in that page ).
Hope this helps.
Edit: I also made sure only one SIM (one used for request unlock) is present in the 1st SIM slot while doing the DEV ROM flash. DEV Rom (fastboot: kenzo_global_images_6.8.18)
Click to expand...
Click to collapse
Great. It worked for you. For me, phone number never showed in there.. like in the screenshot but i was able to unlock.
I think the critical thing is to have the device listed as the only device on the account. For me the other account which had other devices mapped to it before, didnt work.
Was it the same for you? I mean, did you sign up for a new account and maybe using a new phone number?
dastan4eva said:
Thanks
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
Did it work for you? Helpful to feedback pls
+1 to switching to global dev.
However, I did install global dev via EDL flashing, because nothing seemed to work (I was in Global Stable 7.2.3)
I had signed in Mi Account using phone number on both Phone and Computer, accessed mi cloud via both Phone and Computer and was able to locate device on both, synced some test stuff to like photos. Did this when I got sms notification that unlock permission has been granted
Its worth noting that after getting my unlock permission, I only EDL flashed global beta after 2 days.:highfive:
So in summary, applied for unlock on day 1, got confirmation on day 3, unlocked offically on day 5.
Only one device on mi account used since it was created (which was on day 1)
candiesdoodle said:
add it to 4503 or anything just a bit before 4505 and keep stepping in using F11.
Great. It worked for you. For me, phone number never showed in there.. like in the screenshot but i was able to unlock.
I think the critical thing is to have the device listed as the only device on the account. For me the other account which had other devices mapped to it before, didnt work.
Was it the same for you? I mean, did you sign up for a new account and maybe using a new phone number?
Click to expand...
Click to collapse
I had my number connected to my existing miui a/c with MI3 but still after changing the model I never got the unlock request page. So, i created another a/c and used the same no. (first I removed from the existing a/c) and then i got the unlock page and got the permission after 3 days. But since then, I was seeing the value part of the key "_phone" always blank until I flashed global dev and followed the steps I had posted above. The moment I saw my mobile number and the model in the value part, I thought let's try again and voila! it went past 50% (like you achieved something you desperately needed ).
candiesdoodle said:
add it to 4503 or anything just a bit before 4505 and keep stepping in using F11.
Great. It worked for you. For me, phone number never showed in there.. like in the screenshot but i was able to unlock.
I think the critical thing is to have the device listed as the only device on the account. For me the other account which had other devices mapped to it before, didnt work.
Was it the same for you? I mean, did you sign up for a new account and maybe using a new phone number?
Did it work for you? Helpful to feedback pls
Click to expand...
Click to collapse
Yes it worked , i followed your guide and ensured everything's synced (though it took some time - around 24hours) and was able to unlock successfully yesterday! That's why i said thanks
Sent from my Redmi Note 3 using Tapatalk
What happens after getting stuck at 50% ?
Does the phone dont boot anymore ? Or can i reboot it to system just like it was before ?
Sent from my Redmi Note 3 using XDA-Developers mobile app
a.broken.star said:
What happens after getting stuck at 50% ?
Does the phone dont boot anymore ? Or can i reboot it to system just like it was before ?
Click to expand...
Click to collapse
You can boot.. No issues
candiesdoodle said:
You can boot.. No issues
Click to expand...
Click to collapse
Thanx..
Sent from my Redmi Note 3 using XDA-Developers mobile app
The creation of new account part is mandatory ?
I did not create a new account because I only had a linked phone. But after many tests and verify that appeared the phone, and online status, could not unlock.
Finally I flashed Chinese ROM DEV via EDL flash, and have unlocked at first try.
I think it's false that can be unlocked with stable rom, or at least should wait to them (Xiaomi) authorizes something more than MI account.
Related
Hi
recently bought an AT&T Focus from Ebay, the seller says its unlock but I forget about it and purchase the unlock code anyway.
So , here's the problem :
First time I insert my country Simcard I would expect a warning something like "Sim error, please input unlock code" ( this is my 3rd time bought AT&T Focus and been there 2x unlock my previous Focus)
But this time its boot right up and shows 2 bar on the signal bar (so I guess the seller is right, its unlock already) but when I try to call provider customer service the signal suddenly gone and its gone forever
Tried to switch another simcards in still no signal. Do a hard reset, still no go
Each time I turn it on, the phone tab on the home screen says : Searching......and few second after it says..No Service...
I confirm all the simcard I've been using is valid, they all work on my blackberry.
Can anyone give a solution ?
If this is matter, this is what says on the About Phone :
Phone Information :
Name : Samsung SGH-i917
Model : Samsung SGH-i197
Carrier : AT&T Wireless
Software : WIndows Phone 7.5
OS Version : 7.10.7720.68
Firmware : 2103.11.8.1
Hardware : 3.1.0.7
Radio Software : 2103.11.8.1
Radio Hardware : 0.0.0.3
Bootloader : 5.8.0.2
Also it says SIM ID : 8962100xxxxx ( is this means it already read my current SIM inside the phone ?)
I hope you guys can help me, I can't afford to pay the Focus just for a paperweight ....arrrrghhhhhh
I usually use the Samsung 'Network Profile' app to help setup the phone to use a new network with a new sim card.
You can download it from the 'Samsung Zone' Marketplace. Maybe it will help. Good luck.
Edit: I've found it can take a few minutes for the 'no signal' to go away. Perhaps it's registering something. I'm not familiar with what goes on in the background. That's just been my experience.
peterfnet said:
I usually use the Samsung 'Network Profile' app to help setup the phone to use a new network with a new sim card.
You can download it from the 'Samsung Zone' Marketplace. Maybe it will help. Good luck.
Edit: I've found it can take a few minutes for the 'no signal' to go away. Perhaps it's registering something. I'm not familiar with what goes on in the background. That's just been my experience.
Click to expand...
Click to collapse
Hi Peter
Thank for your reply, however when I try to search Network Profile app, I got a warning says Not available in your country, I'm in South East Asia
What should I do now?
I wonder if the problem cause by any forced Mango update? or something like that?
I can see the phone is able to read my Sim card since I can import contacts to the phone
If you're unlocked, use the attached.
metie said:
Hi Peter
Thank for your reply, however when I try to search Network Profile app, I got a warning says Not available in your country, I'm in South East Asia
What should I do now?
Click to expand...
Click to collapse
Install this or the attached.
If you're not (dev) unlocked go to WindowsBreak project or read this mini-guide.
EnderPsp said:
Install this or the attached.
If you're not (dev) unlocked go to WindowsBreak project or read this mini-guide.
Click to expand...
Click to collapse
Hi EnderPsp
I just gone through the WindowsBreak , one of the step that not complete is after choosing the windowsbreak it stays on Loading bla bla... ( I think that windowbreak contain custom provisioning setting? but how I edit it or is it already set up ? )
Also in order to instal the Network Profile app I installed TOM Xap Installer, but it crashed each time I click on instal after browse the network profile app.
I'm missing something here ?
metie said:
Hi EnderPsp
I just gone through the WindowsBreak , one of the step that not complete is after choosing the windowsbreak it stays on Loading bla bla... ( I think that windowbreak contain custom provisioning setting? but how I edit it or is it already set up ? )
Also in order to instal the Network Profile app I installed TOM Xap Installer, but it crashed each time I click on instal after browse the network profile app.
I'm missing something here ?
Click to expand...
Click to collapse
Can you try to deploy using WXapAssistant by WINCO instead?
EnderPsp said:
Can you try to deploy using WXapAssistant by WINCO instead?
Click to expand...
Click to collapse
Ok, here's what I just did, download and instal the SDK and the TOM Xap able to run but when I hit the install button, I got warning says :
1. make sure your phone is unlocked
2. make sure you device connected to PC and Zune Launched
I did open the Zune.
metie said:
Ok, here's what I just did, download and instal the SDK and the TOM Xap able to run but when I hit the install button, I got warning says :
1. make sure your phone is unlocked
2. make sure you device connected to PC and Zune Launched
I did open the Zune.
Click to expand...
Click to collapse
#1. close any browser and skype you have opened, before you do #2 below (as these interfere with the deployment)
#2. make sure your phone is synced in Zune and NOT as guest (full sync) and Zune is in the background
and try again.
EnderPsp said:
#1. close any browser and skype you have opened, before you do #2 below (as these interfere with the deployment)
#2. make sure your phone is synced in Zune and NOT as guest (full sync) and Zune is in the background
and try again.
Click to expand...
Click to collapse
I don't have skype installed, all browsers closed. Still gave me the same error message
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
=============================
Ok, I tried the W.I.N.C.O.'s AppStore PC client v.2.3.5 and it works, the Network Profile app is installed on the phone.
Playing with it, set the correct profile, reboot,....still No Service
metie said:
I don't have skype installed, all browsers closed. Still gave me the same error message
=============================
Ok, I tried the W.I.N.C.O.'s AppStore PC client v.2.3.5 and it works, the Network Profile app is installed on the phone.
Playing with it, set the correct profile, reboot,....still No Service
Click to expand...
Click to collapse
You're welcome
Do you need any special APN details from your provider?
EnderPsp said:
You're welcome
Do you need any special APN details from your provider?
Click to expand...
Click to collapse
I don't see any reference between APN and the problem I'm having ?
I don't get any provider signal (No Service) not that I can't connect to the internet
metie said:
I don't see any reference between APN and the problem I'm having ?
I don't get any provider signal (No Service) not that I can't connect to the internet
Click to expand...
Click to collapse
Sorry, got mixed with another thread and replied without checking.
If Network Profile app didn't work, it might not be a software configuration issue. I would suggest a backup/full sync and then either a hard reset or try to flash a fresh ROM. If that doesn't fix the issue either, then it's hardware. But wait, maybe someone else has a better idea/solution.
EnderPsp said:
Sorry, got mixed with another thread and replied without checking.
If Network Profile app didn't work, it might not be a software configuration issue. I would suggest a backup/full sync and then either a hard reset or try to flash a fresh ROM. If that doesn't fix the issue either, then it's hardware. But wait, maybe someone else has a better idea/solution.
Click to expand...
Click to collapse
I would like to thank you for respond to my problem but I think I don't have more times to find the solution.
I will return it tomorrow and get another Focus.
metie said:
Hi
recently bought an AT&T Focus from Ebay, the seller says its unlock but I forget about it and purchase the unlock code anyway.
So , here's the problem :
First time I insert my country Simcard I would expect a warning something like "Sim error, please input unlock code" ( this is my 3rd time bought AT&T Focus and been there 2x unlock my previous Focus)
But this time its boot right up and shows 2 bar on the signal bar (so I guess the seller is right, its unlock already) but when I try to call provider customer service the signal suddenly gone and its gone forever
Tried to switch another simcards in still no signal. Do a hard reset, still no go
Each time I turn it on, the phone tab on the home screen says : Searching......and few second after it says..No Service...
I confirm all the simcard I've been using is valid, they all work on my blackberry.
Can anyone give a solution ?
If this is matter, this is what says on the About Phone :
Phone Information :
Name : Samsung SGH-i917
Model : Samsung SGH-i197
Carrier : AT&T Wireless
Software : WIndows Phone 7.5
OS Version : 7.10.7720.68
Firmware : 2103.11.8.1
Hardware : 3.1.0.7
Radio Software : 2103.11.8.1
Radio Hardware : 0.0.0.3
Bootloader : 5.8.0.2
Also it says SIM ID : 8962100xxxxx ( is this means it already read my current SIM inside the phone ?)
I hope you guys can help me, I can't afford to pay the Focus just for a paperweight ....arrrrghhhhhh
Click to expand...
Click to collapse
See whether enabling cellular data in Settings>Cellular makes any difference. My phone started working, had same issues as yours.
not able to change the Active Profile
peterfnet said:
I usually use the Samsung 'Network Profile' app to help setup the phone to use a new network with a new sim card.
You can download it from the 'Samsung Zone' Marketplace. Maybe it will help. Good luck.
Edit: I've found it can take a few minutes for the 'no signal' to go away. Perhaps it's registering something. I'm not familiar with what goes on in the background. That's just been my experience.
Click to expand...
Click to collapse
Hi
I am facing exactly same problem. I installed Network Profile. In active profile it shows ATT. with searching available profiles it shows AIRTEL IND (sim network), but I am not able change the profile form ATT to AIRTEL IND.
I tried changing but it still remains ATT as active profile.
Please help
http://forum.xda-developers.com/images/icons/icon9.gif
Network profile not working
EnderPsp said:
Install this or the attached.
If you're not (dev) unlocked go to WindowsBreak project or read this mini-guide.
Click to expand...
Click to collapse
Hi EnderPsp,
I am facing the similar problem. I amusing my Samsung Focus for past 6 months. It is unlocked.
Suddenly, my Samsung focus, started showing "No Service". I did Hard Reset of device, but still same problem.
I installed Network Profile. In active profile it shows the network provider name as per the sim card inserted. But, the device is still showing "No Service". And I cannot make any call.
Please guide me how to solve this problem. Thanks in advance!
metie said:
Hi
recently bought an AT&T Focus from Ebay, the seller says its unlock but I forget about it and purchase the unlock code anyway.
So , here's the problem :
First time I insert my country Simcard I would expect a warning something like "Sim error, please input unlock code" ( this is my 3rd time bought AT&T Focus and been there 2x unlock my previous Focus)
But this time its boot right up and shows 2 bar on the signal bar (so I guess the seller is right, its unlock already) but when I try to call provider customer service the signal suddenly gone and its gone forever
Tried to switch another simcards in still no signal. Do a hard reset, still no go
Each time I turn it on, the phone tab on the home screen says : Searching......and few second after it says..No Service...
I confirm all the simcard I've been using is valid, they all work on my blackberry.
Can anyone give a solution ?
If this is matter, this is what says on the About Phone :
Phone Information :
Name : Samsung SGH-i917
Model : Samsung SGH-i197
Carrier : AT&T Wireless
Software : WIndows Phone 7.5
OS Version : 7.10.7720.68
Firmware : 2103.11.8.1
Hardware : 3.1.0.7
Radio Software : 2103.11.8.1
Radio Hardware : 0.0.0.3
Bootloader : 5.8.0.2
Also it says SIM ID : 8962100xxxxx ( is this means it already read my current SIM inside the phone ?)
I hope you guys can help me, I can't afford to pay the Focus just for a paperweight ....arrrrghhhhhh
Click to expand...
Click to collapse
can you double check the sim slot and see if all the contacts ( small pin like contacts which touch the sim when installed) are all OK?
try to raise them a little with a pin or a small knife and re-insert the sim.
i had the same issue when i got my focus. it would always say no signal or something similar and a "SIM card is missing" icon on the top but would show sim ID just fine...
let me know if it works
Debloater by Gatesjunior
Disclaimer:
I nor XDA are responsible for anything that you choose to do with this program to your device or others. Modifying my code or redistributing it is not allowed without prior approval from me. Yes, that includes Kanging it, I will be able to tell. Neither is trying to use any of my code to create an apk file with my code logic allowed without prior approval from me.
Donations:
"If this application helps you out, please consider a small monetary donation to further improve development of this application. You can Donate by clicking the "Donate to Me" button on your left, underneath my Profile picture.
Background:
So after many times of going back and forth blocking / disabling apps on my devices through the command line and or shell, I decided to write a program to make this all much easier for myself. Well, after I got it all finally running and doing what I wanted, for each particular device I own, I decided that his was a pretty nice program and I wanted to share it with the community. After all, this community is where I started and learned a lot of the things I know today. So why not share with my family of Android enthusiasts.
Requirements:
The program requires that your manufacturer USB drivers are installed for your specific device as well as the following:
• Windows Operating System
• USB Debugging turned on for your device
• Root or KitKat and above running on your device
Some people have had trouble getting their PC to see their device, even with the device manufacturer drivers installed. Watch your device when you plug it in and authorize your computer to access it, the device should display a popup something for you to grant access to the PC. If it does not, go into Settings, Developer Options and look for an option that says something about Revoke USB debugging authorizations and tap it. Click ok. Now, unplug your device and plug it in while watching your device and click on the option to always allow this computer and then grant when the popup window displays.
What does it do?:
• Block / Disable applications on your device
• UnBlock / Enable applications on your device
• Allow UnBlock / Enable all applications at once on your device
• Allows filtering of the displayed packages for quicker decision making
• Allows exporting your blocked / unblocked listing to a file (Right click on Read Device Packages after list is loaded)
• Allows importing your blocked, or someone else's, listing (Right click on Read Device Packages after list is loaded)
• Allows complete removal of application(s) if you have root (It will backup the original folder structure and apk for you, just in case you need to restore the application(s) back to your device.
So, essentially what it does is this. It will disable / block any system and third party application on your device with ease and allow you to enable / unblock the application just as easy. It also reads everything, real-time, directly from your device, so that there are no messy batch files, scripts and txt files, etc. that you have to maintain and keep track of for every device you own. I mean let’s be honest, most of us own more than one device. Phones, tablets, etc. Who wants to maintain all those scripts and files for every device? The other nice thing that this program does is allow you to, at a granular level, control what is blocked/disabled and what is not. There are quite a few scripts and things like this available in the community that give everyone a start on what to disable/block, but who wants to scour through these scripts and decide what they want or don’t want with something someone else put together. The other nice feature of the program is it will display information for you about your device. Such as Model number, Serial number and battery status. As well as whether or not your device is rooted or not.
What audience of device does it support?:
This program supports many devices. It will support any device running KitKat or above, whether rooted or not. That’s right, if your running KitKat or above, your device does not need to be rooted. If you’re running anything other than KitKat or above, your device does need to be rooted. As long as these requirements are met the program will run. The program will also auto-detect whether or not your device is supported. So if you are not sure, plug it in and let the program tell you. If your device is not supported, it will put up a message saying as much and close the program.
Program Functionality:
The first thing you need to make sure of is that USB debugging is turned on for your device. The video at the end of this OP is a must to watch. It will describe this process as well as allowing adb shell permissions.
So when you first connect your device you will need to wait for the program to detect your device and whether or not it is supported. Once this is established, usually within a couple of seconds, it will display a warning message to you reminding you to be careful with what you disable and block. Yes, it will allow you, if your device is supported, to disable/block even system dependent applications. This message will also include, if your device does not support block mode, a message indicating that block mode is not supported and that it will disable the applications. Here is a sample screenshot of this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Once the program has initialized, and the warning message has been presented, it will put you into the main program screen itself which will look like the following.
From here the first thing you need to do is click the Read Device Packages button on the upper left. This will initiate the process to start reading all of the applications on your device and then list them in a list in the window. It will also indicate to you what it detects as applications that are already disabled/blocked on your device by putting a checkmark in the box next to the application. It will look similar to this.
As you can see it will tell you in the upper right how many applications it detects as blocked and not blocked. You will notice that on the bottom left it has an indicator that is labeled Synced. As you make changes to the device application listing this will turn red. In other words, it will indicate whether you have made changes to the device application listing since the last sync. Also, in the upper right there is a counter labeled Changed. This indicates the number of changes you have made to the device application listing since last sync.
Once you have made any changes to the device application listing an Apply button will show up in the upper left replacing the existing Read Device Packages button, it will look like the following.
Once you click the Apply button the existing changes you made to the device application listing will be applied to your device. Keep in mind that you can disable/block and enable/unblock applications all at the same timeand then apply those changes to your device. After you have applied the changes to your device a message will be displayed stating the status of your changes as seen below.
Once the changes are applied to your device you now just click the Read Device Packages button again to reload the information from your device and you will now notice that the application(s) you just made changes to will indicate as much in the refreshed listing. As seen below.
You will notice that the particular application I asked it to disable/block has now a check mark next to it indicating that the device itself has disabled/blocked this application.
So now on to filtering. Lets say you want to limit the listing to specific items you are searching for within the package name. Like packages that contain "vzw" for Verizon. You will see below by clicking the filter checkbox and then typing in what I want to filter on, it will limit the list to your specific filter criteria immediately.
And here is the results of our filter below.
From here I can make changes to the listing, by checking the box next to the packages or I can simply uncheck the filter checkbox and return back to the full listing unfiltered.
O.k., so far so good. Now let’s say that you want to enable/unblock all the applications on your device. Maybe you’re selling it or maybe you have an issue with it and you want your carrier to take a look at it. By clicking the Unblock All Packages button and then click Apply this will enable/unblock all applications on your device. As if it is back to factory with no changes made.
Remove mode turned on. For all you root users, this will completely remove the application(s) in the exact same manner and will keep a backup for you in the install folder under Backup of the original apk files. They will also be kept in the original file structure they came from on the device so that it will make it easy for you if you have to push one back to your device. Here is an example of the remove mode turned on and the warning you will receive when it is active for the device that is rooted.
Also, after you have removed the application(s) you want, if you Reload Device Packages again, you will notice them in the list and checked. This is in fact accurate, it sees them as removed / uninstalled. To not have them show up in the list any longer, just reboot your phone and run the program again and you will see that they no longer show up in the listing.
Sharing your blocked list or re-import it to your device:
So there are times when you get a replacement device and do not want to have to go through all the pain remembering what you had blocked. Well to the rescue comes the export/import functionality of the application. This will allow you to export and import your blocked list. You also might want to share it with someone. So this is how it works:
Once you launched the program and have clicked the Read Device Packages and your list is up, you can right click on the Read Device Packages button and export the blocked packages to a file and share it. Then the person receiving it just does the same process, but when they right click on the Read Device Packages, they just choose import blocked packages and then click the Apply button. Done.. You of course can do this yourself to your device. This can come in very handy if you have to Wipe Data, because you blocked something you should not have and your device is experiencing issues.
Well community people that is it. I hope you enjoy the program as much as I do and look forward to your feedback. Gatesjunior signing out…
Full Install:
Download link: https://1drv.ms/u/s!AjfH26Z4pHaFk1V8rA5Zj_p5vtkx
Upgrade Install: (Just replace debloater.exe in your "Crogram Files (x86)DebloaterDebloater" folder)
Download link: http://rootjunkysdl.com/?device=Gates&folder=DeBloater
OSX Version (dmg file): Thank @eyekyu for the port over with Wineskin..
Download link: http://rootjunkysdl.com/?device=Gates&folder=DeBloater
Mirror: https://onedrive.live.com/redir?resid=8576a478a6dbc737!831
Video by our own RootJunky:
Credits:
RootJunky - For finding the original KitKat weakness
Misterxtc - For all of his hard work already on helping people with a script process for this purpose
Er. Aditya - For testing with me and going back and forth with builds to finally resolve the no packages issue
XDA:DevDB Information
Debloater, Tool/Utility for the Android General
Contributors
gatesjunior
Version Information
Status: Stable
Current Stable Version: 3.85
Stable Release Date: 2015-02-07
Created 2015-02-07
Last Updated 2018-01-12
Change Log:
01/09/2015: Initial Release
01/10/2015: Updated the handling of application filtering determining what is disabled / blocked
01/11/2015: Updated application (v2.1) to hopefully help address the local Administrator issues
01/12/2015: Major update v2.8 (Fixes all the users not being able to see packages - Xposed Framework fix)
1/13/2015: (v2.9) Fixed an issue with an Out of Bounds Exception in certain cases.
1/15/2015: (v2.10) Complete rewrite of the filter engine, all interactive and immediate now. Also some cleanup.
1/16/2015: (v3.0) Root mode added with ability to completely remove application(s), with backup feature.
1/17/2015: (V3.1) Added new intro screen as well as import blocked list functionality.
1/18/2015: (V3.2) Added some hover helper text. If you hover over a major item it will display helper text.
1/19/2015: (V3.3) Fixed some more Xposed framework issues that would impact rooted users and removing packages as well as fixed some import logic to make it more reliable and optimized.
1/23/2015: (V3.4) Major update and bug fixes as follows:
•Interactive search now also supports searching through the package name(s) as well as the apk file(s)
•Bugs related to duplicate entries showing up when you Read Device Packages multiple times with filter on and off are fixed. This could have caused issues with some users saying it will not remove something.
•Blocking mode fully supported on 4.4.x, found a major bug that was preventing this with rooted devices
•APK file backups now include Odex files if they exist with the APK
•Remove option now completely removes both apk and odex, so yes, previous builds would have left the odex files behind. They will not hurt anything, but take up space. I will release a quick fix for the cleanup of those soon, if you cannot do it yourself.
•Buttons appearing where they should not at times with filter is fixed
•If you have disabled something on the phone itself or in a script, and are rooted, the program will not care any longer and will unblock them anyway.
(1/31/2015: (V3.5) Major logic update. I think I finally put a nail in the coffin with the Xposed Framework issues and removing applications. Also added the functionality where once you import a blocked list all the items will turn red for the changes it has made.
(2/6/2015): V3.6 Quite a few additional options. Including the following:
Ability to only show blocked packages, unblocked packages and all packages. (Just right click on either Read Device Packages button or Apply button after initial package listing is displayed.)
Ability to right click now on not only the Read Device Packages button, but also the Apply button.
Ability to import unblocked listing (Yes, changes will be made red to identify what would be unblocked before Applying)
Ability to sort by either APK Filename or Package Name and be able to sort in either Ascending order or Descending order in each area.
Complete removal of all associated data and folders that pertains to a package if the Remove option is selected (Root Mode only)
(2/7/2015): V3.7 Added a checkbox identifier on Display mode to let users know which Display Mode they are in currently.
------ (Fix was placed into this build later that fixes the UnBlock All Packages button bug..)
(3/28/2015): V3.8 Added Lollipop support for rooted / non-rooted users. It will now support hiding the packages, if you are rooted it will disable them instead. Also, you will notice if you right click on the Read Device Packages after it loads there is also a Backup / Restore menu option. Do not use those yet, I am still working on them.
(4/4/2015): V3.85 Fixed issue with base.apk flags being read incorrectly from device. Logic issue.
(4/12/2015): Updated a logic issue in the detection of the device and it's abilities. Same release number, v3.85
(5/24/2015): Fixed an issue during import of a blocked list that would flag all "base.apk" files..
(1/7/2018): Added newer Android Debug Bridge Files..
Hold
For me..
Looking Good video coming soon
I can't wait to give this a run.
Well be getting a note edge soon for testing, and looking forward to giving this a shot.
OP updated now with Video..
Great application but not working on my Droid Razr M (XT907) with latest OTA firmware on it.
Pressing "Read Device Packages" and nothing comes up.
Just tried it on my AT&T Note 4. It seemed to work, great job and thanks for building this app.
0rtli said:
Great application but not working on my Droid Razr M (XT907) with latest OTA firmware on it.
Pressing "Read Device Packages" and nothing comes up.
Click to expand...
Click to collapse
Try this one and let me know:
https://drive.google.com/file/d/0B31X8bH_5Gl-OHpva0dCbHBTb2c/view?usp=sharing
Great idea. Tried it with my ASUS MeMO Pad 8 (ME581CL) but after "Read Device Packages" nothing happens
[email protected] said:
Great idea. Tried it with my ASUS MeMO Pad 8 (ME581CL) but after "Read Device Packages" nothing happens
Click to expand...
Click to collapse
Look back a post and try that one.. Also, send me a screen shot.. Make sure USB debugging is on and in the correct mode as well.
This version works, thanks!
Will be great if this soft give option to disable modem fast dormancy service without root access.
Anyway, thanks.
My AV detects Malware.
Using licensed ESET - no malware detected.
Just disabled FastDormancy.apk (com.motorola.fastdormancy) - how to check if its disabled? In Running programs still see this service is running.
Maximus1a said:
My AV detects Malware.
Click to expand...
Click to collapse
It doesn't like the behavior of the program LOL
I cant get it to download from the webpage. I tried the one in the drive folder and it does not see my phone. Verizon Note 4. Looks awesome, cant wait to get it working!
Got it. I guess the server is overloaded!
Great job on this project addition. I'll be adding your link to my XDA signature this afternoon. Like you and many others, I too believe that until root is achieved on our devices (for those unable to at this time) that having this capability to do with our devices is the next best thing; hands down!
Again, great job to you and to the others like RootJunky and Misterxtc for making this possible for the community here at XDA.
Dear gatesjunior,
I wonder how you'r software disable/enable apk's?
For example: on my device (xt907) I'm not able to complete disable fast dormancy service (see screenshot) only "Force stop" it for a while.
Wonder which method you are using to disable it complete (are you disable it or just force stop it?)
howellcp said:
I cant get it to download from the webpage. I tried the one in the drive folder and it does not see my phone. Verizon Note 4. Looks awesome, cant wait to get it working!
Got it. I guess the server is overloaded!
Click to expand...
Click to collapse
Make sure your USB debugging is on and in the right mode.
I've noticed since I've followed the thread the days prior to my device arriving many have struggled to follow the current guides available. I am not responsible for your inability to read, bricked, or internally explosions on devices.
Step 1:
Go to your desktop and create a new folder I labeled mine 'KIWISDK' but you can call it whatever you want. This is where you will store all files during this process so you can easily access them.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 2:
Create and save a blank Wordpad/Word document into the newly created folder on the desktop title it 'bootloadercode'
Step 3:
Assuming you're not android developers or have the massive android SDK on your computers you need to download and install adb and fastboot from here.
Go ahead and put the installer in that folder just for safe keeping, run the exe to natively install adb/fastboot from anywhere on your PC. We will use this a few steps later.
Step 4:
Prior to unlocking your bootloader we have to do a few things first. Go ahead and power on your phone and go through the initial setup process.
You can use the following link (corrected from all the other ones) to create a new Huawei account (click register for free below the login. This website can be found here
Once you've created a user ID you can use this same link to access the bootloader unlock page later.
Step 5:
Once your device is fully initialized go to settings>about phone
click the build number 7 times as shown above. It will display a toast notification that you are now a developer.
press the back button (2) up from the about phone area of the settings you will now see
file:///C:/Users/Jesse/Desktop/developeroptions.png
Be sure that the 'developer options', 'enable OEM unlock' and 'USB debugging' toggles are in the on position.
Step 6:
Open the Huawei website posted in step 4. Login and accept the terms.
On your device go to the dialer and type the following into the keypad:
*#*#1357946#*#* Open the bootloadercode document we created in step 2 and record this number here, leave the word pad open to record the unlock code created on the Huawei website.
With the website open,
Carefully go to About Phone> After you select smart phone and type your model number KIW-L24 into the website open your about Phone>Status enter your Serial number and IMEI number (if your IMEI 1 number doesnt work, try again with your IMEI 2 number. Make sure you have all numbers and letters in this step complete with accuracy. DOUBLE AND TRIPLE CHECK.
Product Identification is the number located on the wordpad/word document copy and past it into this area. Generate the unlock code after typing in the pin.
Copy and paste the generated number onto the wordpad document for future reference and save the wordpad document.
Step 7:
Download TWRP revovery from here
Download the 3.0.2.0 version and save it to your folder you created in step 1
Download SuperSU from here
Save it into the folder on your desktop.
Download opengapps here
Save which ever version you choose to your desktop file (I go with Nano and Micro) Be sure to select the ARM64 and android 6.0 versions.
Also at this time download your favorite custom rom from the ROM/Kernel portion of our website and store it in that file (be sure to check if it needs gapps flashed along with it) if it is a CM based ROM it has to have the gapps either way I always like to keep a gapps zip on my SD card.
Step 8:
Plug your phone into your computer, open your external SD card drag and drop the superSU zip, Open Gapps Zip, and rom if you selected one for future access.
open a command prompt (cmd from Cortana or runcmd in earlier versions of windows.
type the following:
adb reboot bootloader
Your phone should reboot with a white screen, once it has type the following:
fastboot oem unlock 5019482736699543
(these are the numbers the website generated for your specific Identification# copy and paste from the wordpad document 'bootloadercode' It is the 16 digit long code.
Your device will factory reset do not unplug the device until complete.
unplug the device and redo the initial setup. Once complete repeat step 5 to enable USB debugging
Step 9:
Plug the device back into your computer, open the cmd prompt window and type
adb reboot bootloader
FLASHING CUSTOM RECOVERY:
locate the twrp-3.0.2-0-kiwi.img we placed in the folder on your desktop
to ensure you dont misstype anything in the command prompt type:
fastboot flash recovery then drag and drop the twrp-3.0.2-0.img file from the desktop folder to the cmd prompt
It will look something like this:
fastboot flash recovery C:\Users\Name\Desktop\KIWISDK\twrp-3.0.2-0-kiwi.img
**BE SURE THERE IS A SPACE BETWEEN recovery and C:\**
Hit enter.
Once complete type:
fastboot reboot
Step 10:
Let your phone fully reboot, once rebooted Power off your phone.
NANDROID BACKUP - THE MOST IMPORTANT STEP
1) With the phone off hold volume up , the while holding volume up press and hold the power button. You will see the boot logo come up hold for about 2 seconds more and release ( just to ensure )
2)Your phone will boot into TWRP Recovery
3) PRIOR TO FLASHING ANYTHING: Click Backup
Select your External SD card to backup too.
Swipe to backup.
once the STOCK ROM is backed, you can flash the superSU zip from your sd card rooting the stock rom, be sure to wipe cache/dalvik before rebooting.
If you choose to flash a custom rom you placed on your SD card: once stock is backed up:
1. Go to wipe and swipe to wipe stock
2. hit back and go to install
3. select the ROM file you wish to flash
4. select the gapps file
5. you can include SU even if rom is already rooted
wipe cache/dalvik and then reboot. Happy flashing!
will update screenshots and pics soon
this is a holding place
Thanks for this guide. I created an account but for the past 3 days I get the sorry, the server is busy..... Message on every phone and browser I've tried. I tried 3 phones, 7 browsers a windows laptop and an iPad and iPhone they all give me the same silly message after I hit the agree button to the unlock terms and conditions.
What have I done to screw up such an easy process?
954wrecker said:
Thanks for this guide. I created an account but for the past 3 days I get the sorry, the server is busy..... Message on every phone and browser I've tried. I tried 3 phones, 7 browsers a windows laptop and an iPad and iPhone they all give me the same silly message after I hit the agree button to the unlock terms and conditions.
What have I done to screw up such an easy process?
Click to expand...
Click to collapse
Did you try the link I provided?
Wow you are a genius, I wonder why all the others look exactly the same yet only yours works?
954wrecker said:
Wow you are a genius, I wonder why all the others look exactly the same yet only yours works?
Click to expand...
Click to collapse
Was merely trying to delute the guide to a step by step process leaving out no details for people not familiar with root.
954wrecker said:
Wow you are a genius, I wonder why all the others look exactly the same yet only yours works?
Click to expand...
Click to collapse
Did the link work for you? I fixed some link issues in my html link I hope it works as flawlessly for everyone as it did myself.
The page looked the exact same when I agreed to the huge list of terms, but yours took me to the correct place to get the unlock code instead if the servers are busy page. Thanks for the help
Stuck on stock for 3 days really makes the non stock ROMs 10000% smoother! That emui is a trainwreck, it's going to be impossible to go back to that mess.
kobos311 said:
I've noticed since I've followed the thread the days prior to my device arriving many have struggled to follow the current guides available. I am not responsible for your inability to read, bricked, or internally explosions on devices.
Step 1:
Go to your desktop and create a new folder I labeled mine 'KIWISDK' but you can call it whatever you want. This is where you will store all files during this process so you can easily access them.
Step 2:
Create and save a blank Wordpad/Word document into the newly created folder on the desktop title it 'bootloadercode'
Step 3:
Assuming you're not android developers or have the massive android SDK on your computers you need to download and install adb and fastboot from here.
Go ahead and put the installer in that folder just for safe keeping, run the exe to natively install adb/fastboot from anywhere on your PC. We will use this a few steps later.
Step 4:
Prior to unlocking your bootloader we have to do a few things first. Go ahead and power on your phone and go through the initial setup process.
You can use the following link (corrected from all the other ones) to create a new Huawei account (click register for free below the login. This website can be found here
Once you've created a user ID you can use this same link to access the bootloader unlock page later.
Step 5:
Once your device is fully initialized go to settings>about phone
click the build number 7 times as shown above. It will display a toast notification that you are now a developer.
press the back button (2) up from the about phone area of the settings you will now see
file:///C:/Users/Jesse/Desktop/developeroptions.png
Be sure that the 'developer options', 'enable OEM unlock' and 'USB debugging' toggles are in the on position.
Step 6:
Open the Huawei website posted in step 4. Login and accept the terms.
On your device go to the dialer and type the following into the keypad:
*#*#1357946#*#* Open the bootloadercode document we created in step 2 and record this number here, leave the word pad open to record the unlock code created on the Huawei website.
With the website open,
Carefully go to About Phone> After you select smart phone and type your model number KIW-L24 into the website open your about Phone>Status enter your Serial number and IMEI number (if your IMEI 1 number doesnt work, try again with your IMEI 2 number. Make sure you have all numbers and letters in this step complete with accuracy. DOUBLE AND TRIPLE CHECK.
Product Identification is the number located on the wordpad/word document copy and past it into this area. Generate the unlock code after typing in the pin.
Copy and paste the generated number onto the wordpad document for future reference and save the wordpad document.
Step 7:
Download TWRP revovery from here
Download the 3.0.2.0 version and save it to your folder you created in step 1
Download SuperSU from here
Save it into the folder on your desktop.
Download opengapps here
Save which ever version you choose to your desktop file (I go with Nano and Micro) Be sure to select the ARM64 and android 6.0 versions.
Also at this time download your favorite custom rom from the ROM/Kernel portion of our website and store it in that file (be sure to check if it needs gapps flashed along with it) if it is a CM based ROM it has to have the gapps either way I always like to keep a gapps zip on my SD card.
Step 8:
Plug your phone into your computer, open your external SD card drag and drop the superSU zip, Open Gapps Zip, and rom if you selected one for future access.
open a command prompt (cmd from Cortana or runcmd in earlier versions of windows.
type the following:
adb reboot bootloader
Your phone should reboot with a white screen, once it has type the following:
fastboot oem unlock 5019482736699543
(these are the numbers the website generated for your specific Identification# copy and paste from the wordpad document 'bootloadercode' It is the 16 digit long code.
Your device will factory reset do not unplug the device until complete.
unplug the device and redo the initial setup. Once complete repeat step 5 to enable USB debugging
Step 9:
Plug the device back into your computer, open the cmd prompt window and type
adb reboot bootloader
FLASHING CUSTOM RECOVERY:
locate the twrp-3.0.2-0-kiwi.img we placed in the folder on your desktop
to ensure you dont misstype anything in the command prompt type:
fastboot flash recovery then drag and drop the twrp-3.0.2-0.img file from the desktop folder to the cmd prompt
It will look something like this:
fastboot flash recovery C:\Users\Name\Desktop\KIWISDK\twrp-3.0.2-0-kiwi.img
**BE SURE THERE IS A SPACE BETWEEN recovery and C:\**
Hit enter.
Once complete type:
fastboot reboot
Step 10:
Let your phone fully reboot, once rebooted Power off your phone.
NANDROID BACKUP - THE MOST IMPORTANT STEP
1) With the phone off hold volume up , the while holding volume up press and hold the power button. You will see the boot logo come up hold for about 2 seconds more and release ( just to ensure )
2)Your phone will boot into TWRP Recovery
3) PRIOR TO FLASHING ANYTHING: Click Backup
Select your External SD card to backup too.
Swipe to backup.
once the STOCK ROM is backed, you can flash the superSU zip from your sd card rooting the stock rom, be sure to wipe cache/dalvik before rebooting.
If you choose to flash a custom rom you placed on your SD card: once stock is backed up:
1. Go to wipe and swipe to wipe stock
2. hit back and go to install
3. select the ROM file you wish to flash
4. select the gapps file
5. you can include SU even if rom is already rooted
wipe cache/dalvik and then reboot. Happy flashing!
Click to expand...
Click to collapse
My PC finds the adb device before I type "adb reboot bootloader" but once in fastboot, it wont find it. How can I fix that?
It's already been found (on the first part) just type fastboot oem unlock fastboot and adb go hand in hand.
Remember once your bootloader is unlocked you will have to go through the initialization process and toggle developer options on again
AsapJuno said:
My PC finds the adb device before I type "adb reboot bootloader" but once in fastboot, it wont find it. How can I fix that?
Click to expand...
Click to collapse
Please follow the guide as stated.dont deviate thank you.
definitely tried that. Wouldn't be commenting if I didn't. Can you help
Pin Code Telephone # no longer works
I've tried a few days to get the PIN code with * # * # 1357946 # * # * however the number no longer works. Is there a new tele # or an alternate way to unlock the bootloader ?
error msg:
Connection problem or invalid MMI code
Mine worked 2 days ago. So clearly the code works fine check your about phone settings and make sure you have an imei 1 and an imei 2
AsapJuno said:
definitely tried that. Wouldn't be commenting if I didn't. Can you help
Click to expand...
Click to collapse
ASAP Juno, it's already detected your device via adb adb/fastboot are linked just type the commands don't worry about checking fastboot.
any other methods for retrieving the pin code ?
jusdef said:
Pin Code Telephone # no longer works
I've tried a few days to get the PIN code with * # * # 1357946 # * # * however the number no longer works. Is there a new tele # or an alternate way to unlock the bootloader ?
error msg:
Connection problem or invalid MMI cod
Click to expand...
Click to collapse
kobos311 said:
Mine worked 2 days ago. So clearly the code works fine check your about phone settings and make sure you have an imei 1 and an imei 2
Click to expand...
Click to collapse
I have both imei's and actually tried with a two different sim cards...AT&T and Google Fi.
I get the same error message since Saturday night., 7/16/16
Does anyone know of any other methods for retrieving the pin code ?
jusdef said:
I have both imei's and actually tried with a two different sim cards...AT&T and Google Fi.
I get the same error message since Saturday night., 7/16/16
Does anyone know of any other methods for retrieving the pin code ?
Click to expand...
Click to collapse
Let me be more clear, not the ones on the box, you need the digital file backed up via nandroid which originally you said you didn't have? The numbers on the box won't help
So when I install SuperSU, wipe, and reboot... it boots back into twrp
kobos311 said:
Mine worked 2 days ago. So clearly the code works fine check your about phone settings and make sure you have an imei 1 and an imei 2
Click to expand...
Click to collapse
kobos311 said:
Let me be more clear, not the ones on the box, you need the digital file backed up via nandroid which originally you said you didn't have? The numbers on the box won't help
Click to expand...
Click to collapse
Wrong user, I didnt say I did not have imei's and I can't do a Nandroid backup if my phone isnt rooted. I'm trying to unlock my bootloader so I can take the steps to root and install TWRP. Huwai site will not let me submit the request without the pin #.
Recently I bought this phone and I've gone through all problems, error and struggles to unlock the bootloader. This tutorial will solve:
86012 error
10008 error
Cannot connect to network
Not receiving confirmation SMS
Stuck at 50%
Stuck at 99%
Current account is not bound to this device
Couldn't verify device
Requirements:
Mobile
PC
USB Cable
Internet connection
Let's start with the tutorial, the main advantage is that you don't need Developer ROM, it will work on Official builds also:
Setup your MIUI account by going to Settings -> Mi Account
Open the MIUI Browser from your phone, don't use PC on this step
Apply for permission here
Use your phone number with your country prefix to log in (ex. +38970123456 is for Macedonia)
Write a genuine reason, 2-3 sentences
After some time you will receive a confirmation SMS (it may take a few days, but with this method I got the SMS in 2 hours on 4 different Xiaomi devices)
Download Mi Unlocker from here
Enable developer options by going to Settings -> About phone and tap 7 times on MIUI version
Go to Settings -> Additional Settings -> Developer Settings and tick OEM Unlocking and USB debugging
Go to Settings -> Additional Settings -> Developer Settings -> Mi Unlock Status and press Unlock
Turn your Mobile data, Sync , WiFi and GPS on and wait for 5 minutes and don't turn them off afterwards
Go to Mi Cloud by clicking here
Login with your phone number
Click on Find device and locate your phone
In the folder where you've extracted the Mi Unlock tool, you will find a program called MiUsbDriver, open it and press Install
Log in to Mi Unlock by opening miflash_unlock on PC with the same phone number you used in obtaining the unlock permission
Switch off your phone and go into Fastboot by pressing Volume down and Power simultaneously and connect your phone to the PC
Once it shows a handset in Mi Unlock click on Unlock button
Wait for a minute and you are done
Your phone's bootloader is now UNLOCKED
NOTE: Some users may see something like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's not a big deal, just wait the amount of hours that are shown there and then try unlocking the phone again. By using this tutorial you will get only 48 hours.
Good tutorial.
Thanks!
Maybe I can a little requirement.
It will be easier and faster to get SMS approval if you are at least Diamond Member at MIUI forum.
Got the permission yesterday but not able to unlock with lastest tool as it shows ''current account is not bound to this device'' error even though I added my account in dev option also the find my device is on
I can't even register my account and device in the Mi Unlock tab. Always getting the error "Couldn't verify, wait a minute or two and try again.". Any tips? Got my unlock permission about a week ago.
am not able to click on apply option at the bottom of page.. have tried it both on miui device as well as the computer
Is unlocking wipe the phone ?
drmuruga said:
Is unlocking wipe the phone ?
Click to expand...
Click to collapse
Nope. It doesn't.
LilBlinx said:
Recently I bought this phone and I've gone through all problems, error and struggles to unlock the bootloader. This tutorial will solve:
86012 error
10008 error
Cannot connect to network
Not receiving confirmation SMS
Stuck at 50%
Stuck at 99%
Current account is not bound to this device
Couldn't verify device
Requirements:
Mobile
PC
USB Cable
Internet connection
Let's start with the tutorial, the main advantage is that you don't need Developer ROM, it will work on Official builds also:
Setup your MIUI account by going to Settings -> Mi Account
Open the MIUI Browser from your phone, don't use PC on this step
Apply for permission here
Use your phone number with your country prefix to log in (ex. +38970123456 is for Macedonia)
Write a genuine reason, 2-3 sentences
After some time you will receive a confirmation SMS (it may take a few days, but with this method I got the SMS in 2 hours on 4 different Xiaomi devices)
Download Mi Unlocker from here
Enable developer options by going to Settings -> About phone and tap 7 times on MIUI version
Go to Settings -> Additional Settings -> Developer Settings and tick OEM Unlocking and USB debugging
Go to Settings -> Additional Settings -> Developer Settings -> Mi Unlock Status and press Unlock
Turn your Mobile data, Sync , WiFi and GPS on and wait for 5 minutes and don't turn them off afterwards
Go to Mi Cloud by clicking here
Login with your phone number
Click on Find device and locate your phone
In the folder where you've extracted the Mi Unlock tool, you will find a program called MiUsbDriver, open it and press Install
Log in to Mi Unlock by opening miflash_unlock on PC with the same phone number you used in obtaining the unlock permission
Switch off your phone and go into Fastboot by pressing Volume down and Power simultaneously and connect your phone to the PC
Once it shows a handset in Mi Unlock click on Unlock button
Wait for a minute and you are done
Your phone's bootloader is now UNLOCKED
NOTE: Some users may see something like this
It's not a big deal, just wait the amount of hours that are shown there and then try unlocking the phone again. By using this tutorial you will get only 48 hours.
Click to expand...
Click to collapse
Still not able to unlock the bootloader.....Even after following the same procedure, am getting the following exception:
Current account is not bound with this device.
Please help me on this. Either we could try with fastboot commands.
sachin n said:
Nope. It doesn't.
Click to expand...
Click to collapse
Unlocking bootloader factory reset my Nexus 7 grouper and Moto G falcon instantly.Are u sure that isn't the case with Xiaomi?
hailahaiela said:
Unlocking bootloader factory reset my Nexus 7 grouper and Moto G falcon instantly.Are u sure that isn't the case with Xiaomi?
Click to expand...
Click to collapse
Am quite sure my man, it won't wipe data on mi devices.
Jagadeesh Reddy said:
Still not able to unlock the bootloader.....Even after following the same procedure, am getting the following exception:
Current account is not bound with this device.
Please help me on this. Either we could try with fastboot commands.
Click to expand...
Click to collapse
Resetting the phone helped me with this problem instantly.
Sent from my Redmi Note 4 using Tapatalk
I haven't had a problem unlocking my Bootloader. After an approved request from Xiaomi, I have unlocked it in just a minute or two. Plus, when my bootloader accidentally got locked, I can do it again and again without bothering to request an approval.
just found out that the china set is able to unlock without trouble, the global set is on trouble now, before Oct was okay, now xiaomi changed something and caused unknown error.
I have ordered my device recently and it is yet to be received, and to buy some time I made an unlock request with mi account, the first time it didn't send an SMS to my phone number, so I tried a virtual US number to receive the confirmation SMS and after the permission, The question is:
Will I be able to unlock my device without my phone number being the same as the one in the request form?
Hello there. I seem to be stuck in the permission request. I complete the form but it does not accept my name, it writes in red lettering "Please input correct name". I have tried using my email address, my Mi account name, my Mi account number, my real name ...nothing works.
Any ideas are more than welcome
Something that everyone missess
Something that everyone missess....Xiaomi server tries to locate you first before unlocking.
Different numbers wont work. You need the same number. Turn on your WiFi and GPS as well as data, just in case.
If you dont have a FB account create one. Link it to phone and number. Go to locate my phone and let Xiaomi server locate you on the map.
Try unlocking now and voila!
Charismagic said:
Something that everyone missess....Xiaomi server tries to locate you first before unlocking.
Different numbers wont work. You need the same number. Turn on your WiFi and GPS as well as data, just in case.
If you dont have a FB account create one. Link it to phone and number. Go to locate my phone and let Xiaomi server locate you on the map.
Try unlocking now and voila!
Click to expand...
Click to collapse
I have got the permission after 7 hours of the request without even having the device yet, and asked about the different numbers on Xiaomi forums and a moderators replied that I still can unlock it the regular say. Just waiting for the device to test.
aser_elhbayeb said:
I have ordered my device recently and it is yet to be received, and to buy some time I made an unlock request with mi account, the first time it didn't send an SMS to my phone number, so I tried a virtual US number to receive the confirmation SMS and after the permission, The question is:
Will I be able to unlock my device without my phone number being the same as the one in the request form?
Click to expand...
Click to collapse
Yes, You can unlock your device without any SIM inserted on device. Only thing is your account should be verified with valid number.
---------- Post added at 01:54 PM ---------- Previous post was at 01:44 PM ----------
@Shette said:
Got the permission yesterday but not able to unlock with lastest tool as it shows ''current account is not bound to this device'' error even though I added my account in dev option also the find my device is on
Click to expand...
Click to collapse
This error does not matter for unlocking. Try unlocking after 3 days
The reason which you mentioned during asking for unlock permissions matters on how fast you can unlock.
I have given reason like " I am android developer and I want to take advantage of root access", I was able to unlock in 2 days after getting permissions
PS : even I had same error " current account is not bound to device" but I was able to unlock it!
Making sure.
Should I give it a try, i am on miui global 9 stable, 9.0.5.0.. waiting for reply, device is mido
cutecrocodile said:
Should I give it a try, i am on miui global 9 stable, 9.0.5.0.. waiting for reply, device is mido
Click to expand...
Click to collapse
have followed instructions but get this error on miui 9
If you flashed the Stock ROM using “Download All + Format” option in SP Flash Tool or you wiped NVRAM partition accidently then you probably lost IMEIs, WiFi/Bluetooth Mac Address and Serial No.
Disclaimer:
Code:
/*
*Your Warranty is now void.
*Neither me nor the developers of tools are responsible.
*You are doing this at your own risk and will
*solely be responsible if something happens to the device.
*Make sure you only use the original “IMEI_1, IMEI_2,
*WiFi/Bluetooth Address, Serial Number” that came with your phone.
*/
Note:
Although, I have tried to keep this guide as simple as possible, I am assuming that you have already flashed Stock ROM using this thread/guide:
https://forum.xda-developers.com/k8-note/how-to/lenovo-k8-note-xt1902-3-fix-dead-hard-t3791839
Which also means the required drivers i.e. “MTK (USB DA COM, Preloader USB VCOM, USB Port, USB VCOM) Driver” and “Lenovo USB Driver” in the thread mentioned above are also installed.
Requirements:
Lenovo K8 Note with Stock ROM.
Original IMEI_1, IMEI_2, WiFi/Bluetooth Mac Address, Serial Number. (Find on Phone’s box)
SN Write Tool (Download)
Database Files
ADB Tools (Inside SN_Write_Tool\Android)
Basic ADB know-how.
And a PC. (obviously)
USB Debugging:
Before we proceed, make sure “USB Debugging” is enabled on phone:
Navigate to, Settings > System > About Phone > Build Number (Tap 7 times) to enable “Developer Options”.
Now, Enable “USB Debugging” in Settings > System > Developer Options.
Flashing Procedure:
Extract SN Write. (For Example, Location: “E:\ SN_Write_Tool_v1.1916.00”)
Open SN Write Tool (SN_Writer.exe).
Make sure all the Preliminary steps mentioned in below sections have been performed – Obtaining DB files, Configuring SN Write Tool, Understanding Barcode.
Switch off the phone, while keeping the cable unplugged
Click “Start”.
Enter Original IMEI_1, IMEI_2, WiFi/Bluetooth Mac Address, Barcode and press “Ok”
Connect your phone.
Now your phone will automatically boot in Meta Mode.
Wait for the Process to finish.
Now you will see “Pass” message if everything completes successfully.
Now it will again ask to enter the details. Click “Cancel”
The phone will now switch off. Then boot it manually.
That’s it. Your phone is now back to normal. Now, you can see Serial No. in adb too.
Obtaining Database(DB) files:
In order to restore everything we need 2 Database files, which can be obtained by following the procedure below:
Extract SN_Write Tool. (For Example, Location: “E:\ SN_Write_Tool_v1.1916.00”)
Navigate to “Android” folder inside SN_Write_Tool folder.
Keep Shift Key Pressed and Right Click inside the folder. Select “Open Command / PowerShell window here”.
Type
Code:
adb devices
You will receive a prompt on your phone. Select “Ok”. The device will appear in the list. (Something like “0123456 device”)
Now, type these commands:
Code:
adb pull /vendor/etc/mddb Database
adb pull /system/etc/apdb Database
Now, navigate to “E:\ SN_Write_Tool_v1.1916.00\Android\Database”. There will be around 23 Files. We only Need 2 files from that.
APDB_MT6797_S01_alps-trunk-o0.tk_W19.10 (Approx. size 145kb)
MDDB_InfoCustomAppSrcP_MT6797_S00_MANNING_O_Vxx_x_ulwctg_n.EDB (Approx. size 59mb)
Note: Name and size may slightly vary depending upon your firmware.
Copy the above two files to some other destination (optional).
Note: If you are using PowerShell then, instead of “adb” type “./adb”
Configuring SN Writer Tool:
Open “SN_Writer.exe” inside “E:\ SN_Write_Tool_v1.1916.00”.
Now Click “System Config”.
Check “Dual IMEI” (Do not check “Dual IMEI Same” under that).
In Write options select Barcode, IMEI, BT Address, WiFi Address. (If you don’t have WiFi/BT Address then don’t check/select them).
Check “Load AP DP from DUT” and “Load Modem DB from DUT”.
Click “MD1_DB” and select the file that you pulled using ADB i.e.
“MDDB_InfoCustomAppSrcP_MT6797_S00_MANNING_O_Vxx_x_ulwctg_n.EDB”
Click “AP_DB” and select the file that you pulled using ADB i.e.
“APDB_MT6797_S01_alps-trunk-o0.tk_W19.10”
Now click “Save”.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Understanding Barcode:
It took me lots n lots of trial & error and googling before finding the correct (probably) Barcode format that we need to use in SN Writer. Trust me, it was not an easy task. Below are three iterations of barcode, use any:
First Iteration (recommended):
The Barcode field consists if two parts, call them Spaces and Serial No.
Total Length(33 Characters) = (25 Spaces) + SN(8)
For Example,
If my SN written on the box is “XYZ1223W”, my barcode will be (without quotes):
Code:
“ XYZ1223W”
or
Second Iteration (recommended 2):
In this iteration, we'll assume that the Barcode field in SN Write Tool is a combination of three parts. Lets call it First (PN), Second and Third Part (SN). You can find PN & SN on the box of phone. I am not sure about the second part with 15 characters. You can leave the second part, just give 15 Spaces.
Total Length(33 Characters) = PN(10) + (15 Spaces) + SN(8)
For Example,
If my PN written on the box is “AB1D1112IN” and SN is “XYZ1223W”, my barcode will be (without quotes):
Code:
“AB1D1112IN XYZ1223W”
or
Third Iteration:
There can also be a third iteration for barcode, though I am not sure about this and is completely based on my assumption. In the second part, as mentioned above we are leaving 15 spaces, but in this, we will use the product barcode of 13 characters (Refer Barcode No. 2 in the attached image below) instead of 15 spaces
For Example,
If my barcode (no. 2 in image above) of 13 charcters is “0123456789012”, then in SN Writer we will write (without quotes):
Total Length(33 Characters) = PN(10) + (Space) + (13) + (Space)+ SN(8)
Code:
“AB1D1112IN 0123456789012 XYZ1223W”
Note the space after each part, which makes up for two characters that we require.
As you can see in the Screenshot attached in this post, “Lenovo Help” app recognizes the device as it is meant to be recognized.
WiFi/Bluetooth Mac Address:
Though, it is not a big deal if you lost WiFi/Bluetooth Mac Addresses. They will still work fine even without it.
If you didn’t backup nvram before or didn’t note down WiFi/Bluetooth Mac address then you can’t get it back. But, if you did TWRP backup of nvram then you can restore it and get back both the original Mac addresses.
FAQs:
SN Writer not booting phone into Meta Mode automatically.
Make sure drivers are installed
or
Boot Manually in Meta Mode using Power Button + Volume Down. Check Already in Meta Mode.
Do I need to be on Stock ROM?
Yes.
Changelog:
27 September 2020:
Update post.
Added one more iteration of barcode.
Added more Screenshots.
Correct minor typos.
thanks alot man
I managed to get apdb files but when i try your command to get mddb i get that error
adb: error: failed to copy '/etc/mddb' to 'Database\mddb': read failed: Is a directory
any help?
and how to know if my bluetooth or wifi mac address is missing and where to find them because nothing of that is written on the phone box
softmaster3 said:
thanks alot man
I managed to get apdb files but when i try your command to get mddb i get that error
adb: error: failed to copy '/etc/mddb' to 'Database\mddb': read failed: Is a directory
any help?
and how to know if my bluetooth or wifi mac address is missing and where to find them because nothing of that is written on the phone box
Click to expand...
Click to collapse
Edit: Solved
Android will automatically generate Wi-Fi / Bluetooth address if not found. No need to worry about that. Thats why I I have mentioned in the post that it will still work fine even without it.
You mentioned wrong paths, /etc/apdb is fine but /etc/mddb doesn't exist(empty folder was created in latest update but still no contents in it). mddb is under /vendor/etc/mddb. Just to avoid confusion and even to make this guide suitable for users who pull the file from TWRP make the /etc/apdb to /system/etc/apdb
---------- Post added at 01:03 PM ---------- Previous post was at 01:00 PM ----------
softmaster3 said:
thanks alot man
I managed to get apdb files but when i try your command to get mddb i get that error
adb: error: failed to copy '/etc/mddb' to 'Database\mddb': read failed: Is a directory
any help?
and how to know if my bluetooth or wifi mac address is missing and where to find them because nothing of that is written on the phone box
Click to expand...
Click to collapse
instead of "adb pull /etc/mddb" use "adb pull /vendor/etc/mddb"
M.A.P said:
You mentioned wrong paths, /etc/apdb is fine but /etc/mddb doesn't exist(empty folder was created in latest update but still no contents in it). mddb is under /vendor/etc/mddb. Just to avoid confusion and even to make this guide suitable for users who pull the file from TWRP make the /etc/apdb to /system/etc/apdb
---------- Post added at 01:03 PM ---------- Previous post was at 01:00 PM ----------
instead of "adb pull /etc/mddb" use "adb pull /vendor/etc/mddb"
Click to expand...
Click to collapse
thanks a lot guys
u two just made my day
and M.A.P u r a life saver i cant thank you enough for ur work on treble for k8 note and ur help here
M.A.P said:
You mentioned wrong paths, /etc/apdb is fine but /etc/mddb doesn't exist(empty folder was created in latest update but still no contents in it). mddb is under /vendor/etc/mddb. Just to avoid confusion and even to make this guide suitable for users who pull the file from TWRP make the /etc/apdb to /system/etc/apdb
Click to expand...
Click to collapse
Done. Thanks for suggestion.
i did write the serial, check warranty and its good
but noticed that the serial written on phone box is 12 Character long not just 8 and sn writer did write 8 only not the whole 12
is that correct??
softmaster3 said:
i did write the serial, check warranty and its good
but noticed that the serial written on phone box is 12 Character long not just 8 and sn writer did write 8 only not the whole 12
is that correct??
Click to expand...
Click to collapse
May I see the image of your box. PM me the image.
done
softmaster3 said:
thanks a lot guys
u two just made my day
and M.A.P u r a life saver i cant thank you enough for ur work on treble for k8 note and ur help here
Click to expand...
Click to collapse
Your welcome, I'm always ready to help
Hi, with the help of your guide, i have recovered my phone. But the problem is still same as it restarts repeatedly,sometimes it worked for 1 day but then again rewstarting. Is there any permanent solution for this?
psbtheone said:
Hi, with the help of your guide, i have recovered my phone. But the problem is still same as it restarts repeatedly,sometimes it worked for 1 day but then again rewstarting. Is there any permanent solution for this?
Click to expand...
Click to collapse
Show your phone to a technician. It may be due to battery or some other reason.
Im getting remote object does not exist error for both commands
WP7 Barcode
Hi,
I was wondering how did you find the correct Barcode format? I have spent 2 days trying with different combinations and I still have not succeeded in restoring the serial number in my Oukitel WP7. It still gives me the generic serial number 123456789ABCDEF.
oxord said:
Hi,
I was wondering how did you find the correct Barcode format? I have spent 2 days trying with different combinations and I still have not succeeded in restoring the serial number in my Oukitel WP7. It still gives me the generic serial number 123456789ABCDEF.
Click to expand...
Click to collapse
Did some Trial and Error to figure out correct (probably) barcode format. In addition to this, you'll also need specific database files for your phone in order restore it.
kk9999gada said:
Did some Trial and Error to figure out correct (probably) barcode format. In addition to this, you'll also need specific database files for your phone in order restore it.
Click to expand...
Click to collapse
Man this thing is driving me crazy. I have tried every single combinations and did so many googling and there are not a lot of information about this. The other problem is that the Oukitel WP7 does not have a Product Number written on the box or on the back of the device, there is only a serial number and a barcode with 13 numbers under it. I even tried the FCC ID that is written at the top. I have been spending few days trying. I think the only way to know the correct format is to ask someone who has the same device to view it using Maui Meta by viewing the hex format or exporting the NVRAM to an ini file. I doubt anyone would help me with this though. I have the database files from the stock image. Anyways thanks man
oxord said:
Man this thing is driving me crazy. I have tried every single combinations and did so many googling and there are not a lot of information about this. The other problem is that the Oukitel WP7 does not have a Product Number written on the box or on the back of the device, there is only a serial number and a barcode with 13 numbers under it. I even tried the FCC ID that is written at the top. I have been spending few days trying. I think the only way to know the correct format is to ask someone who has the same device to view it using Maui Meta by viewing the hex format or exporting the NVRAM to an ini file. I doubt anyone would help me with this though. I have the database files from the stock image. Anyways thanks man
Click to expand...
Click to collapse
That would be better.
There is no need for Part No. or Barcode (both can be replaced with spaces). The only thing required is Serial No.
kk9999gada said:
That would be better.
There is no need for Part No. or Barcode (both can be replaced with spaces). The only thing required is Serial No.
Click to expand...
Click to collapse
I tried that as well with so many different ways and with spaces and without. I guess the length also matters. I even filled all 63 characters to see if anything changed in settings but it still showed the generic serial number. I am starting to wonder if sn tool is writing the data in the correct location. I am sure I am using the correct database files because I got them from the factory image from the official website and I am able to write the IMEIs correctly.
I am thinking now to go through the serial number which is 16 characters from left to right. Each time I add a space on the left and no spaces after the serial so first try would be only the serial then a 1 space before it then two spaces before it until I reach the 63 characters. This is like 50 restarts and if that does not work I will try in a same manner but this time full up spaces after the serial and do the same by adding one space on the left each time so first try would be the serial number and the remaining will be spaces up to 63 characters the second time will be one space before the serial and remaining spaces after it up to 63 and so one. I know it's crazy but if all that does not work I am not sure what else to do.
Hi
This happened to me with this dangerous spflash tool. WIPED everything. I followed this guide , It PASSES without any errors but doesnt write anything to my phone. Box has a code bar like this 6 970502 270581 then MEID code of 14 characters , than IMEI1 code and a IMEI2 code and finaly a S/N code of 15 characters.
As i said it PASS but doesnt show IMEI, version base band , bluetooth address, Serial number ,
Thank you very much spflash tool. Had to get another phone.
Phone is a MEDIATEK mt6763T.
Only thing that i dont understand from guide is how to enter Serial number in sn writer. Did it many ways. 33 characters and 64 characters with spaces.
If anyone has any idea , please show me the way. thx.