Develop Bugs

[HOWTO] Software Unlock; How to unlock Bell Galaxy S Vibrant i9000M

Now that we have enough people with the new version on hand already.
It's time to setup this topic.
The aim obviously is to unlock this the Bell Galaxy S Vibrant i9000M
There are possibly 3 ways to go about this:
1. Software
2. Hardware
3. Pay $75 the carrier and get the unlock code after 60 days of purchase, or until some online unlockers gets the code, which ever first.
4. Pay $35 to rhcp0112345 for the hack unlock method
5. Self Hex Hack unlock method
Past experiences in the PalmOS world leads me to believe it should be possible to be unlocked via software/firmware, so rooting the phone will be the first thing to do
For hardware unlocking we'll be able to confirm once the iSim I've ordered arrives next week more or less
Bell will not provide the unlock code until their "exclusivity" expires which is roughly November, that's when Fido/Rogers will get their own locked version for sure.
So, I'm inviting any Android/Mobiles developers to pitch in with any ideas or if they know more or what to look for, change edit, hack replace, flash, etc.
That's why i bough this device, it'll be a guineapig to possibly find the software unlocking method (flashing a ROM count as software)
Stock Bell firmware:
PDA/Phone: i9000ugjg9
CSC: i9000bmcjg9
WARNING: for anyone reading this DO NOT use the firmwares for the USA Vibrant / Captive, the Bell Vibrant is closer to the i9000 than to the USA variants
- Update 1 -
Adding unlock bounty! it actually started on the SGS Captivate subforum http://forum.xda-developers.com/showthread.php?t=739201
Condition to hit the jackpot, it must be unlocked via software ROM flash, SPL, or something along the line.
Lets all pitch in to make it work for all the SGS phones.
List of members pledge & donation:
AllGamer paid "unlocked" via ismartsim then by SGUX
MKVFTW withdrawn he paid $75 to Bell way to get it unlocked
SS2006 $25 payment pending
decepticon paid unlocked by rhcp0112345
BA_Flash_GOD paid unlocked by rhcp0112345
- Update 2 -
rhcp0112345 found out how to hex hack unlock the phone, it requires a file dump and a $35 fee.
The bounty would still apply for anyone Developer able to release a ease to use software unlock for all XDA member at no charge, but if you can't wait you can go with rhcp0112345 solution or the self hack solution.
- update 3 - [BOUNTY] goes to
rhcp0112345 for finding the hack, and allowing rbnet.it and marcopon to create the SGUX tool for all of us.
Please donate to our XDA members that made it all possible for you.
AllGamer for jump-starting this project and providing the initial bounty, and for his regular contribution in the SGS forum
rhcp0112345 for finding the hack
rbnet.it & marcopon for the SGUX tool
DaGentooBoy for keeping the Unlock Guide updated with the latest changes

Step 1. root your phone
Bell's I9000M is slightly different than the regular I9000
most of the root methods mentioned on other topics will not work.
Even the 3 button recovery mode has been disabled
After some experimentation this is the working method
download the update.zip from this topic (Thanks to jentech)
http://ip208-100-42-21.static.xda-developers.com/showpost.php?p=7536130&postcount=11
then you need to run adb devices to make sure your phone is listed
(ADB is part of Android SDK, download it from the source http://developer.android.com/sdk/index.html )
if you get something like
Code:
adb.exe devices
List of devices attached
900098c722a9 device
(if you run adb.exe devices and comes back with an empty list, then make sure you have set the phone into debugging mode Application > Settings > Development > USB Debugging)
then you are can execute
adb.exe reboot recovery
this will take you to the recovery screen
now if your device works with the Power + Volume Up + Home button, then you can skip that, however in my case the 3 button mode didn't work
select the update.zip with the volume up/down button, then hit home screen, it should say installing in yellow, then you are done, it reboots back to normal, and now you can install Busy Box
Step 2. Self Hex Hack unlock method
Once you are done Rooting the phone
1. Run ADB Devices on your PC
open CMD
change to your Android SDK folder
type ADB devices
hit Enter
it should show your phone listed
if not then check to make sure you have Enabled the USB debugging in Applications < Settings in your phone
2. Once successful with the above step
type ADB Shell
hit Enter
type SU
hit Enter
back on your phone screen you should see a pop up for "Superuser Permission" (try to keep your screen on, the timer automatically turns the screen off, you might miss the pop up message)
"grant it permission" to allow, else you will get a "permission denied"
3. back on the ADB shell
type cd /dev/block
hit Enter
type dd if=/dev/block/bml3 of=/sdcard/bml3.bak
hit Enter
you should get something like
Code:
20480+0 records in
20480+0 records out
10485760 bytes transferred in 0.826 secs (12694624 bytes/sec)
the bml3.bak file should now be at the root of your internal SD card
4. Unplug the USB cable from the phone
Disable the USB debugging in Applications < Settings
5. Plug the USB cable back to the phone
Use either Samsung Kies mode, or Mass Storage mode
6. Copy the bml3.bak file from the internal SD card to your working folder where you have downloaded SGUX2
7. Run CMD
CD (change directory ) to the folder where you have the files
execute/run sgux2.exe bml3.bak (assuming both files are in the same folder)
then you should get something like this
Code:
SGUX v0.92b (C) 2010 By Mark0 & rbnet
Samsung Galaxy Unlock code eXtractor
(based on info by rhcp0112345 & RazvanG)
Opening file <bml3.bak>...
Searching code block...
Found.
Searching codes...
Freeze code : 98765432
Network Control Key: 12345678
8. power off your phone
9. power the phone back on
10. now enter the NCK (Network Control Key) code you found on step 2 part 7
It should say "Requesting network unlock"
followed by "Network unlock successful"
Done, enjoy your phone with your favorite network.
*** Alternative Unlock Methods ***
Hardware unlock method
Get an imartsim from ebay or deal extreme
Software unlock method
easier than ever please see guide for details
http://forum.xda-developers.com/showthread.php?t=761045
{
"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"
}
Bell unlock method
Call Bell convince them to unlock you, and Pay $75
Paid Hack unlock method
rhcp0112345 said:
Guys.
If you cannot wait. I found an easier way for me to get the codes for you. And the file is 10MB. and if you zip prob smaller as hell.
Code:
adb shell
cd /dev/block
# dd if=/dev/block/bml3 of=/sdcard/bml3.bak
copy to computer / upload
Send me $35 USD to [email protected]
Click to expand...
Click to collapse
original topic link http://forum.xda-developers.com/showpost.php?p=7772955&postcount=588

Well first thing is have you tried flashing a different MODEM file onto the phone using Odin?

I tired flashing Asian EU version of radio but no luck.
I believe simlock is something totally different,
I ended up using a sim adapter that was lying around for last 2 years.
Put the sim adapter along with my fido sim
settings, APN typein APN setting (internet.fido.ca)
3G is now active,
I can make calls and recieve calls.
EDIT:+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
http://www.dealextreme.com/
you can order any sim adapter, they all do the same thing.
+++++++++++++++++++++++++++++++
When you FLASH to JP3
don't flash the RADIO, (just flash PDA with 512)
I find RADIO FW on Stock BELL ROM works better than the one included in the JP3.
=======================================================================
BTW you don't have Vibrant,
you have I9000 don't flash CAPTIVATE, VIBRANT ROMS
=======================================================================
Another weird thing I noticed,
the "download mode" for Odin (press vol down home pwr)
works on one of the phones only.
for the other phone, I had to plug in debugging mode and use "ADB reboot in recovery command.
======================================================================
I ended up exchanging my 2nd galaxy S, If you can't put your phone into ""download mode"
there's something wrong with your phone.
as far as the unlock sim goes, yes it's like a turbo sim, any adapter will do.
but the problem I noticed, 3G works great, I can make outgoing calls, BUT 1 out of 2 times, incoming call goes directly to my voicemail.
it's probably because of my sim not seen as fido sim on the network.
neways, I am going to try.
http://unlockgenie.com/ for factory unlock code.
they have the lowest price for bell unlock so far 26$
====================================================
I assembled one click solution for ADB , no need for command line,
double click the bat file while connected in DEBUG mode.
it's for those people who are having trouble getting into the download mode by pressing keys.
http://www.megaupload.com/?d=3H9UZNI4

you can also unlock it using SAMSUNG factory code.
you can get one code for around 25~30$ US
seeing that EU version of the froyo rom JP3
works fine with i9000m 3G
I'm guessing I am on NAM network. (despite the radio rom being EU version)

Well I started looking through the Android source for where it determines if a device is network locked but I got lost after a while (I'll have another go later). Presumably it's stored on a chips firmware that you can't easily flash, however just in case... Would someone mind backing up their whole system exactly prior to unlocking and then again afterwards using clockwork mod so we can look for changes.

Benjamin Dobell said:
Well I started looking through the Android source for where it determines if a device is network locked but I got lost after a while (I'll have another go later). Presumably it's stored on a chips firmware that you can't easily flash, however just in case... Would someone mind backing up their whole system exactly prior to unlocking and then again afterwards using clockwork mod so we can look for changes.
Click to expand...
Click to collapse
that's my plan, in the worse case scenario then we can de-brick and reload the original firmware that came with Bell
i'll be trying more stuff later today, still at work

Im looking into getting this phone as well... problem im not sure if the deving for the tmobile vibrant will transfer directly over to the bell galaxy s...
Anyone try rooting the bell one with the root out for that phone??
Edit: Nvm just saw that the root is for the i9000 :|
But still would the root for the tmobile version work on this and vice versa?

Subscribed. Going to follow this thread til DEATH. Now i need solution to buy one. Someone please find a vendor that ships to US.

leegoon84 said:
you can also unlock it using SAMSUNG factory code.
you can get one code for around 25~30$ US
seeing that EU version of the froyo rom JP3
works fine with i9000m 3G
I'm guessing I am on NAM network. (despite the radio rom being EU version)
Click to expand...
Click to collapse
Which site can I pay & sim unlock it please?

Yea same, subscribed.
Im on the same boat as some of u : Want to trade up my magic for bell i9000
But first i must wait for unlock. Root is already done. Then for a vibrant cm6 to be out and see if someone can flash and see how well it works out. Considering its identical hardware except for a few soft buttons + front facing camera, i wouldn't be surprised if its the same deal as with g1 / 32a magic.

leegoon84 said:
BTW you don't have Vibrant,
you have I9000 don't flash CAPTIVATE, VIBRANT ROMS
Click to expand...
Click to collapse
True for anyone reading this DO NOT use the firmwares for the USA Vibrant / Captive, the Bell Vibrant is closer to the i9000 than to the USA variants

AllGamer said:
Now that we have enough people with the new version on hand already.
It's time to setup this topic.
The aim obviously is to unlock this the Bell Galaxy S Vibrant i9000M
There are possibly 3 ways to go about this:
1. Software
2. Hardware
3. Pay $75 the carrier and get the unlock code after 60 days of purchase, or until some online unlockers gets the code, which ever first.
Past experiences in the PalmOS world leads me to believe it should be possible to be unlocked via software/firmware, so rooting the phone will be the first thing to do
For hardware unlocking we'll be able to confirm once the iSim I've ordered arrives next week more or less
Bell will not provide the unlock code until their "exclusivity" expires which is roughly November, that's when Fido/Rogers will get their own locked version for sure.
So, I'm inviting any Android/Mobiles developers to pitch in with any ideas or if they know more or what to look for, change edit, hack replace, flash, etc.
That's why i bough this device, it'll be a guineapig to possibly find the software unlocking method (flashing a ROM count as software)
Stock Bell firmware:
PDA/Phone: i9000ugjg9
CSC: i9000bmcjg9
Click to expand...
Click to collapse
Guys,
I just called "Bell" again & I was transfered to a "level 2" technical support informing me that these are the conditions to sim unlock it:
1- Have to be on an Active account even a prepaid is ok.
2- Have to be after 30 days of activating the account.
3- Unlocking will be instant right on the phone for $75.
Seems like we can't do it that way, anyone knows a paid way of sim unlocking it rightaway from any site?

Has anyone managed to root the phone yet? If yes, can you point to where? I've tried a few to no avail. Thanks.

I'm looking for the modem.bin from the Bell Vibrant. If anyone has it could they please send me a PM.

Yay
Hah glad to see it, and glad there will be quick dev on this device. I'm with the other USA folks in here like stated before, we just need to wait a bit to see it around online or know one of our fine neighbors to the north to hook a bro up hah. Thanks guys will be checking this out.
** at least it's not so bad having to wait for us US folk then if it's currently unlockable. Heck i'll thrown down a couple bucks to whomever pulls it off as well

leegoon84 said:
I tired flashing Asian EU version of radio but no luck.
I believe simlock is something totally different,
I ended up using a sim adapter that was lying around for last 2 years.
Put the sim adapter along with my fido sim
settings, APN typein APN setting (internet.fido.ca)
3G is now active,
I can make calls and recieve calls.
EDIT:+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
http://www.dealextreme.com/
you can order any sim adapter, they all do the same thing.
+++++++++++++++++++++++++++++++
When you FLASH to JP3
don't flash the RADIO, (just flash PDA with 512)
I find RADIO FW on Stock BELL ROM works better than the one included in the JP3.
=======================================================================
BTW you don't have Vibrant,
you have I9000 don't flash CAPTIVATE, VIBRANT ROMS
=======================================================================
Another weird thing I noticed,
the "download mode" for Odin (press vol down home pwr)
works on one of the phones only.
for the other phone, I had to plug in debugging mode and use "ADB reboot in recovery command.
Click to expand...
Click to collapse
what adapter are you using? kind of turbo sim? what is called to use it while waiting for unlock code?
i have old iphone turbo sim, i have no clue if this can be used , as i tried it still no network

I'll donate 20$ to any dev who cracks this
im anxously awaiting a solution my galaxy is just sitting on the table right now collecting dust

Guys, just get a code from unlockallcellular.com. I got my European I9000 unlock code from there.
Sent from my GT-I9000 using XDA App

post removed

HTC One M8 Rooting and S-Off Guide for Newbies (US/International)

Welcome to the HTC One M8 S-Off GUIDE FOR NEWBIES!​
Disclaimer:​I am not responsible for any damage to your phone, in part, or in whole; including bad SD cards, broken reception, bad wifi, Windows 8 being installed, or anything else that could go wrong: Bricking, Bootloops, blips, beeps, boops, or sweeps. You chose to follow these instructions on your own accord and if you do so, agree that I am not liable in anyway, shape or form.
What Models/Carries Should this Work for?
USA: ATT, TMobile
European: Tmobile, VodaFone
I'm unsure if all of this works for Verizon/Sprint versions. You'll have to check the Toolkit's thread and the Firewater thread or official site for confirmation. The above models are just what I've read on the forums)
Credits:
Hansoon2000 for the HTC One Toolkit
Shrimp208 for Minimal ADB and Fastoot
Beups and Fuses for Firewater​.
Ok, so, you want to achieve Root/S-Off and its many benefits. I'm going to walk you through what I did to make this process fairly simple.
Requirements:
HTC One M8
Windows 7, 8, 8.1
No Lockscreen on your phone.
Developer Options Enabled with the following:
1. USB Debugging Enabled
2. Allow Mock Locations (this may not be necessary, but I always do it just in case)
Hint: Don't know how to enable developer options? Go to Settings>About>Software Information>More and tap on "Build Number" 7 times. This will open Developer Options in the Settings menu.
Let's Root!​Use the All-In-One toolkit here:
http://forum.xda-developers.com/showthread.php?t=2699065
Process:
When you open the ToolKit, you'll notice lots of little boxes with text inside. We're going to focus on the box at the very top left that says "To root the phone, follow in order." Fairly simple, right?
First, Download and install HTC Sync Manager and make sure it sees your One M8. Do not use the Install Drivers option from the toolkit, they're outdated/don't work for most people. HTC Sync will install the latest driver for the M8. You can then uninstall the HTC Sync Manager program itself. Link: http://www.htc.com/www/software/htc-sync-manager/
Register at HTCDev. This is needed for this process to gain permaroot at the time I write this. If it doesn't allow you to register, either use a different email address, or ask a friend to do this.
Once logged in, go to "Unlock Bootloader" and Select HTC One (M8) from the drop down list. Follow the steps/prompts and directions on the site.
Get Token ID. Plug your phone in to a USB 2.0 port on your PC (not a hub, not USB3.0, USB 2.0). You should be notified that the HTC One M8 has been plugged in. If so, Proceed. If not, you'll have to figure out the issues you're having with the drivers first.
Two windows will Pop Up. Hit close on the First Window.
The second window should pop up with text. Your token ID is a long series of alpha-numeric text. This is an example of everything you should copy:
{
"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"
}
Note: Copy ALL off that text. From the <<<<Identifier Token Start down to Identifier Token End>>>>
Now, Take that copied text and submit it at HTCDev where it asks you to. If it's successful and you've copied what you need to, an Unlock_Code file will be emailed to you. Download and Place this file in the HTC One Toolkit's Data folder.
Unlcok Bootloader: Again, two windows will pop up, close the first. Your Phone should reboot and the token ID Applied. Your phone will ask you if you want to proceed. Hit Volume Up for "Yes" and Power Button to confirm. This might take a minute, don't freak out.
Flash a Recovery. Once your phone is booted back to the Home screen, go to the far right top window and Select TWRP as the recovery. Select Flash Recovery. Your phone will again pop up with two windows, close the first, and let it do it's thing. Reboot back into the Recovery after this is all done.
Flash Supersu. Go into "Install" in TWRP and select "SuperSu" from the list, swype to begin process.
Congratulations, you should now be rooted!
Time to S-Off!​
WARNING: Not all devices are supported by Firewater. There's really no way to tell until you start running the process to S-Off. If Firewater tells you that your device is not compatible, then it's not compatible. You'll have to wait until Firewater does support your device and is updated.
REQUIRMENTS:
ROOTED HTC ONE M8
ADB and HTC Drivers (htc drivers should be installed from Rooting)
Developer Options Enabled with the following:
1. USB Debugging Enabled
2. Allow Mock Locations (this may not be necessary, but I always do it just in case)
Hint: Don't know how to enable developer options? Go to Settings>About>Software Information>More and tap on "Build Number" 7 times. This will open Developer Options in the Settings menu.
Don't have ADB and don't know where to start? Then download and install MINIMAL ADB AND FASTBOOT:
http://forum.xda-developers.com/showthread.php?t=2317790
Once Downloaded and installed, go to your Start window on the PC and search "ADB". Minimal ADB and Fastboot (here on referred to as ADB) will show up, click on it to bring up a Command Prompt. Using Admin Rights isn't a bad idea either when using ADB.
Go to http://firewater-soff.com/instructions/ And make sure you Follow the Prerequisits to the letter! Read the Instructions for "Rooted, Normal Device Method"
Now that you have the Firewater file, go to Start and Search for ADB, RIGHT CLICK and choose SHOW FILE LOCATION. Drop your Firewater file here. Now we can begin!
Process:
Connect your phone to a USB 2.0 Port if you already haven't and make sure your phone is on the Home screen with NO LOCKSCREEN OF ANY SORT
In the Command Terminal, Type:
adb device (this should show you that your phone is connected. If it says that the phone is inactive/offline, then unplug your phone and replug it. Try again. It should now show up).
Type:
adb Reboot (this will reboot your phone)
After your device has rebooted, there's a 99.9999% chance that it will ":go offline" and not connect to adb (we can confirm this with "adb device" command. Unplug, Replug your phone and ensure it's online and ADB can see it).
Type:
adb wait-for-device push firewater /data/local/tmp
Type:
adb shell
Type:
su
Type:
chmod 755 /data/local/tmp/firewater
Type:
/data/local/tmp/firewater
If you're successful up to this point, Firewater will ask you if you're sure. Type:
Yes
At this point, the Command Prompt will start Chugging bottles of Firewater. Some Command Prompts only Chug One, others, 5,6, up to 12. If you reach 13 Bottles, Abort and try the steps again. This may take a while and several resteps, just be patient. The command prompt, when successful, will notify you that you are now S-Off!
To check this, boot in to Bootloader to confirm (it will say S-Off, not S-On).
The Why:
I believe the reason you need an internet connection is that the Firewater file connects to a server and the voodoo is all done by the server. Why would they do this? Probably to ensure that HTC doesn't screw us out of S-Offing our device like they're known to do by downloading and decompiling files used to S-Off or reverse engineering steps taken to S-Off If anything, this slows them down (and possibly makes it impossible for them to stop us from doing so.)
Special Thanks:
Beups, Fuses, Hasoon2000, and all Developers that are supporting our device with lots of goodies. Don't forget to donate to them to encourage them to spend time on our device, or, just buy them a beverage for all of the hard work and time they spend doing this for us.
If I have forgotten anything or forgot to give credit to someone, please let me know and I'll be sure to add it.

You might want to add that if firewater says your device is not compatible then it means exactly that and you just need to wait for firewater to be updated. There's no pattern to what is and isn't compatible its just luck of the draw and likely down to hardware variances.
Sent from my HTC One_M8 using Tapatalk

stuart0001 said:
You might want to add that if firewater says your device is not compatible then it means exactly that and you just need to wait for firewater to be updated. There's no pattern to what is and isn't compatible its just luck of the draw and likely down to hardware variances.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Ah, yes, you're correct. Thank you!

i'm having a nightmare.
having issues all the way through, seems the htc drivers i get from the toolkit don't install correctly. adb just wouldnt play. i got round that by installing htc sync from phone, that installed correct htc drivers. i then un installed htc sync.
now i've got as far as...
C:\Program Files (x86)\Minimal ADB and Fastboot>adb wait-for-device push firewat
er /data/local/tmp
3082 KB/s (4519496 bytes in 1.431s)
C:\Program Files (x86)\Minimal ADB and Fastboot>shell
'shell' is not recognized as an internal or external command,
operable program or batch file.
any ideas what i've f'ed up?
---------- Post added at 01:47 AM ---------- Previous post was at 01:39 AM ----------
ok i think it should be adb shell yes?

Yes adb shell
Sent from my HTC One_M8 using xda app-developers app

Learoy1 said:
i'm having a nightmare.
having issues all the way through, seems the htc drivers i get from the toolkit don't install correctly. adb just wouldnt play. i got round that by installing htc sync from phone, that installed correct htc drivers. i then un installed htc sync.
now i've got as far as...
C:\Program Files (x86)\Minimal ADB and Fastboot>adb wait-for-device push firewat
er /data/local/tmp
3082 KB/s (4519496 bytes in 1.431s)
C:\Program Files (x86)\Minimal ADB and Fastboot>shell
'shell' is not recognized as an internal or external command,
operable program or batch file.
any ideas what i've f'ed up?
---------- Post added at 01:47 AM ---------- Previous post was at 01:39 AM ----------
ok i think it should be adb shell yes?
Click to expand...
Click to collapse
Did you get it all worked out?
Also, I updated the OP to use "adb shell," I apologize, I should have remembered that adb need to be there. As well, I've updated the OP to point to the latest HTC Sync with drivers.

Sorry for the question but it's my first HTC device and I'm studying in deep all the aspects of bootloader, s-off and so on.
What about I need to come back the M8 for warranty?
If I am right I can restore stock rom and recovery and relock the bootloader through s-off. At this point, what about s-off? Is there a way to revert it to stock s-on?

This Rooting method works for the International variant as well right?

Just can't seem to get my device online. I've tried just about everything, restarted phone, laptop, server, different port, different cable, etc. I see a notification that says "Media Device [MTP] connected", and I have an inkling that it could be causing issues, but I can't seem to find a way to disable it. Is anyone else having this issue?
(T-Mobile M8, perma-rooted)
*edit* After several attempts, I seem to have gotten the timing right, using the version of ADB that came with the all in one tool. Somehow it just started to work, but only with that version. Other versions of ADB still saw the device offline. Just one of those annoying things. Either way, I'm now S-OFF. That was the last piece I was missing. Thank you.

Not working!
Have htc one m8 (at&t version) and have tried all the steps but always fails at the end. It saids it wil not work with my device? Don't other people use this with at&t and it works for them? Why doesn't it work for me? Is there another method to s-off? Like from twrp recovery?

patstar5 said:
Have htc one m8 (at&t version) and have tried all the steps but always fails at the end. It saids it wil not work with my device? Don't other people use this with at&t and it works for them? Why doesn't it work for me? Is there another method to s-off? Like from twrp recovery?
Click to expand...
Click to collapse
HTC patched the old S-OFF method, it doesn't work anymore unless you're really lucky to get a device that's before the patch and you don't first update it...
You can try Sunshine S-OFF it's $25 but it seems to do the job right. It actually checks your device for compatibility before you even pay for it, at least that way you won't end up paying for something that "might" not work.
[Android][HTC S-OFF] SunShine for modern HTC devices It's from the same developers of firewater. So far those that did it seems quite happy about it.
Your choice though, it's the only alternative method available.

BerndM14 said:
HTC patched the old S-OFF method, it doesn't work anymore unless you're really lucky to get a device that's before the patch and you don't first update it...
You can try Sunshine S-OFF it's $25 but it seems to do the job right. It actually checks your device for compatibility before you even pay for it, at least that way you won't end up paying for something that "might" not work.
[Android][HTC S-OFF] SunShine for modern HTC devices It's from the same developers of firewater. So far those that did it seems quite happy about it.
Your choice though, it's the only alternative method available.
Click to expand...
Click to collapse
I can't believe I paid $25 but it did work. Wanted to change my software buttons to stock android. Well I guess now I can put other roms on it. If I flash a different custom rom on it, it would be like getting a new phone so I would have to transfer all my data again? Took forever to get apps to restore from helium (carbon) backup and some did not work, really don't want to put custom Rom if it does that again. If I make nandroid backup to internal storage, can I transfer it to my pc for use later on?

patstar5 said:
I can't believe I paid $25 but it did work. Wanted to change my software buttons to stock android. Well I guess now I can put other roms on it. If I flash a different custom rom on it, it would be like getting a new phone so I would have to transfer all my data again? Took forever to get apps to restore from helium (carbon) backup and some did not work, really don't want to put custom Rom if it does that again. If I make nandroid backup to internal storage, can I transfer it to my pc for use later on?
Click to expand...
Click to collapse
Yeah unfortunately if you flash any new ROMs it'll be like a "new" phone like you yourself stated. There will be no apps, nothing. You can back it up and restore with something like Titanium. Even through Google Store it's easy enough if you lock in with the same account again, just reinstall, easy as pie.
Yes if you make a nandroid backup of your device you can store it on your computer for use later on. It's actually advisable to do so, you "might not" find a nandroid backup for your device whilst searching online, so at least if something goes wrong you have a backup on your PC and all is good :good: If only more people would make backups before doing anything though...

BerndM14 said:
Yeah unfortunately if you flash any new ROMs it'll be like a "new" phone like you yourself stated. There will be no apps, nothing. You can back it up and restore with something like Titanium. Even through Google Store it's easy enough if you lock in with the same account again, just reinstall, easy as pie.
Yes if you make a nandroid backup of your device you can store it on your computer for use later on. It's actually advisable to do so, you "might not" find a nandroid backup for your device whilst searching online, so at least if something goes wrong you have a backup on your PC and all is good :good: If only more people would make backups before doing anything though...
Click to expand...
Click to collapse
Titanium backup won't let me backup to sd card, I guess I could backup to internal storage and put it on pc like nandroid or move it to sd card afterwards? I could just download custom rom to my phone, goto twrp and flash it without pc? Is there any dual boot method of roms? I know for m7 there was something that let you switch from sense to stock android with press of button.

Lost & Puzzled Newbie
Hi Guys,
I'm hoping someone can help me out here because I've ben sat in front of my pc for 16 hours straight through the night & I now don't appear to be much nearer than when I started!
So, I picked up my new One M8 & having had some success rooting my ASUS TF700T tablet, I decided that I would root my phone before I got started using it properly & wasted time personalising it. Before I get started, I'm currently on Android 4.4.2, Sense 6.0, & software number 1.54.206.10; if you need anything else, let me know.
I did loads of reading first, hence the night sat in front of my pc, & amongst many others, I was following this thread & the instructions here:
http://forum.xda-developers.com/showthread.php?t=2799796
http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
I was doing really well to begin with & I managed to unlock the bootloader, flash TWRP, & install SuperSU. Then things started to go wrong. I was undecided whether or not to go for S-Off &/or Super CID but I'd read that S-Off might maximise my battery life even more, so I went for it. I only installed the HTC drivers, absolutely no HTC Sync, my USB Debugging was on, Security was off, & Fastboot was disabled. I downloaded Firewater & after discovering that the ADB folder on my pc wasn't just the folder I'd extracted my ADB zip file to, I found the correct ADB folder on my C: drive, dropped Firewater in & plugged my in M8. It's my own fault because normally, when my phone asks, 'do you want me to do this every time?', I say 'no, just once'......but for some unknown reason, once I'd hooked it up & was using the adb command window (Win 8.1), when the message popped up on the M8 about the phone allowing my pc to connect via adb every time, I, apparently stupidly, said yes.
What happened then was that the adb console, would recognise my phone, so when I typed 'adb device' (or whatever the instruction was), it gave me a page of all sorts of details but then every time I typed 'adb reboot', I got a message saying that the device was offline. If I typed 'adb device' again, I'd get the same page of data & I could see the phone in explorer, so I'm sure the drivers are there, but I also got the same message asking for the reboot.
I've spent hours trying to sort this out & if I'm honest, I got a bit lost (I'm normally quite good at problem solving but I don't suppose it helped not having slept for almost 30 hours now). Anyway, I remembered with my tablet that I just went into TWRP & flashed the 'CHROMi X' ROM from there & by this time, I just wanted to try to get things finished, so because I was most familiar with CyanogenMod, I downloaded it on the pc, transferred it to the phone & tried to flash it I thought I'd read that I neded the ClockworkMod bootloader but I was kind've hoping that TWRP would do the job......it didn't & just failed!
Then my problems really started because the phone went into a boot loop, staying on for only about 10-20 seconds after it booted up. Obviously, by this point I was quite worried that I was about to wreck my shiny new phone but I did some more reading & saw that for someone else, SuperSU had caused this, so I booted back to TWRP, wiped the Dalvik cache & re-flashed SuperSU. Thankfully, that stopped the boot loop
However, I now seem unable to access TWRP? When I hold down the volume down & power buttons, the phone just boots straight through to Android? SuperSU is still installed & it opens up fine (albeit with no apps logged) but it seems like now, the phone might not be unlocked, &/or rooted, or both, though that doesn't seem to make sense to me if SuperSU still runs?
EDIT: I've just tried deleting a folder on the external micro SD card using ES File Explorer & the 'operation failed', so it looks SuperSU, although it asked if I wanted to grant/deny the relevant permissions, isn't working. On 2nd attempt, it worked, so I'm still lost!
EDIT: Fastboot had sneaked back on, so I've switched it back off & I'm back into the bootloader, which says 'Tampered' & 'Unlocked' at the top, & I can boot into TWRP to make the backup of what I've got now that I wanted to make earlier
ANOTHER EDIT: I've now backed up the stock ROM with TWRP & downloaded a root checker app, so I now know that I'm still unlocked & rooted Now I could just do with some help deciding what ROM to install & help on how to go about it.....please
EDIT: After all that, I couldn't sleep, so I didn't try & I stayed up & have managed to sort it. I've got Android Revolution HD on for now but I think I'm correct in thinking that I'll be able to change to another ROM at a later date if I don't like this one? I was going to delete all this, so that people didn't think I was an idiot but it might prove useful to someone else, if only to prove that you probably shouldn't miss a night's sleep because you're trying to root your new phone!!!!
I hope all that makes sense to someone else though? All I wanted to do was get rid of all the O2 bloatware, & most of all, actually be able to write to my external micro SD card, without having to take it out of the phone constantly, so I wanted to install a custom ROM that would be as good as CHROMi X is on my tablet!! but as I said at the beginning, I now feel completely lost & unwilling to start trying again until I know what's happening/has happened.........oh, & I need some sleep!!
If anyone can help get me back on track again, I'd really appreciate it because I really have put the effort in & I don't normally give up but I'm worried that if I keep at it now, I'll end up bricking my phone!! I do want to get this sorted out & enjoy this amazing device for the next couple of years, so any advice on where to start next, which ROM I should use (at this point, I'm easy), or whatever, like I said, I'd really appreciate it
p.s. I didn't mention but once I've sorted my phone out, my girlfriend wants me to sort her HTC One Mini 2 out because she wants to be able to use her external micro SD card too!!

delete

[TROUBLESHOOTING] Bootloader Unlock Fail: (bootloader) [KillSwitch] Last Byte is 0X01

if you're reading this thread, you're likely tearing out your hair in apt frustration because you're just trying to unlock your bootloader and its a no-go. If you're coming from a One M7 or M8, just be aware that HTC's switched up the game since then. Also, everything mentioned below is indirectly applicable to HTC 10 owners as well.
Writing up this thread as that was me, and I scoured pretty much every link pulled from variations of google keyword searches; and as I was successful in finally unlocking the damn thing, here is my braindump:
[in no particular order], and YMMV, much of this is a compilation of things that saved other people experiencing such errors, every rock unturned is a rock unturned.
There's a new "download mode"---the ol' white backgrounded fastboot that you used to know and love, that's sidelined, you must run fastboot on the black backgrounded Download mode format.
you CANNOT use the standard Google/Android SDK's fastboot. I know, wtf. you MUST use HTC's fastboot (the one they provide on HTCdev.com; note that their's is missing an ADB, you can pluck the ADB portion from the standard Android SDK).
If you are experiencing a fail, I recommend immediately wiping the whole device (reset all data), and then starting anew: from there, be sure to: --get Developer, and check the: allow OEM unlocking + allow USB debugging boxes. also, while you're in settings, might as well: increase the screen off time, put 'no lock screen', allow unknown sources installations, etc. then after all that's set, then try and run the fastboot.
for whatever reason, the Gmail web client might not work happily with your unlock_code.bin that you get sent---and/or you're getting weird HTCdev login errors even though you put in the right password---eff that noise; start anew: create a new account, don't use a Gmail email (I used a live.com email to get the unlock_code.bin that ended up being the golden goose egg). yeah, for reasons unknown, there's some RNGmagic mojo crap going on here, so if you're experiencing errors, there's really nothing to lose by going new routes.
don't use Chrome to go to the HTCdev website; I used Edge (no deliberate Microsoft plug or anything here, fyi)
the HTCdev website won't accept your fastboot paste of oem unlocking info if its not the right number of characters, I tested this, so that's not the problem if you thought it was; I recommend opening up a Notepad and just copying and pasting it there and then double-checking that, and then pasting it onto the HTCdev site.

Dont mean to burst your bubble.. Thats all old news.
Beamed in by telepathy.

Updating AT&T OTA issues; need help sideloading

Hey all, I recently purchased my Moto Z2 Force att branded phone from motorola.com (when it was on sale for $300); love it so far...but. it's currently on 7.1.1...and refuses to update. I've talked to att customer service for over an hour, and they swear they've done everything they can do from the network side; that it must be a phone issue (...I don't buy it). Moto says they aren't in charge of updates, must be an update issue. Thanks guys.
So I want to get to Oreo, *without* invalidating my warranty.
I downloaded the Lenovo MOTO Smart Assistant (pointed out in other threads), and it recognized that I was out of date. The Flash section of the LMSA seemed to download the latest image, rebooted my phone...and stopped. Showed 51% done, and didn't move once left for hours. The phone is showing the fastboot screen (as if you had held the volume buttons and the power button), but doesn't seem to be going any further.
What the crud.
So I have an "official" image downloaded with the tool, ADB tools installed, and while I haven't rooted and reflashed this phone, I've done it in the past to others. Is there any way to use the image I DL'd with ADB or something else, without invalidating my warranty? (Pics show what was downloaded by the LMSA tool).
{
"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"
}

If you have an official firmware for your variant (ATT), you can use a convertor to convert the flashfile.xml to a .bat file and flash your firmware from command prompt. The "how to return to stock" thread will help you, but keep in mind that it is tested on TMO and SPIRNT, ATT isn't much different, but flashall.bat in the flashall util zip might not be sufficient for ATT. That's what the convertor is for, you can make your own flashall with your own xml from the firmware you have. Use the return to stock thread as a guide, and it has links for ATT official firmwares provided from the Moto Firmware Team.

This is exactly what I needed; not necessarily a hand-holding or step by step, but a path forward to investigate. Thanks!

So I also bought the ATT Z2 Force and LOVE IT. I got all the mods too Similarly, I can't get the OTA updates to work, and the lenovo tool hangs at 51%.
Just to be certain, does the method below work on locked bootloaders without root? Thanks so much!!!
41rw4lk said:
If you have an official firmware for your variant (ATT), you can use a convertor to convert the flashfile.xml to a .bat file and flash your firmware from command prompt. The "how to return to stock" thread will help you, but keep in mind that it is tested on TMO and SPIRNT, ATT isn't much different, but flashall.bat in the flashall util zip might not be sufficient for ATT. That's what the convertor is for, you can make your own flashall with your own xml from the firmware you have. Use the return to stock thread as a guide, and it has links for ATT official firmwares provided from the Moto Firmware Team.
Click to expand...
Click to collapse

westec2 said:
So I also bought the ATT Z2 Force and LOVE IT. I got all the mods too Similarly, I can't get the OTA updates to work, and the lenovo tool hangs at 51%.
Just to be certain, does the method below work on locked bootloaders without root? Thanks so much!!!
Click to expand...
Click to collapse
With a locked bootloader you can flash an official firmware that is the same revision or newer. So in short, yes.

Hello! I ended up using the smart tool; it hangs at 51 pct because it doesn't have the right drivers loaded for your device in bootloader mode; it's not recognizing your phone once it reboots back over into bootloader mode. I ended up installing the right drivers and using that tool; it was the easiest way without root to get updated. Once I had the right drivers installed and it recognized bootloader mode, LMSA was really easy to use.

despree said:
it hangs at 51 pct because it doesn't have the right drivers loaded for your device in bootloader mode; it's not recognizing your phone once it reboots back over into bootloader mode. I ended up installing the right drivers and using that tool.
Click to expand...
Click to collapse
How did you get the "right drivers" and how did you install them? Does the PC download them automatically when you attach the phone or did you need to find them and manually install them?

Hey, had to get home to do some digging. I tried different drivers from a few different places, but I'm pretty sure the ones that worked for me are "15 Second ADB Installer", forum.xda-developers.com/showthread.php?t=2588979 . Install those guys, then start the update process. Before the update process, under Device Manager, your phone should show up as "Universal Serial Bus devices -> Moto Z (2)" (or similar). This is correct when your phone is normally operating and connected to the PC with USB debugging.
Then, during the update process, it will put your phone in bootloader mode (with the android dude on his back, chest open). This is where the problem is. Whatever device it loads your phone as (I forget now), is wrong. Under device manager it should be "SAMSUNG Android Phone-> Android Bootloader Interface". So whatever device it loads as, update the drivers; and, with the new drivers you installed above, select that one (Samsung Android Phone/Android Bootloader Interface). I'm not sure at this point; you may need to restart the update process, or it may detect the new device and go from there. But either way, once it gets your phone back to that bootloader mode (android dude on his back), scroll over to "Bootloader Logs", and you should actually see some entries happening. If you do, DO NOT DO ANYTHING ELSE UNTIL IT'S DONE. Or you'll be restoring your phone and blowing everything away. Personal experience.
After that, you should be good and able to update!
Worth noting: I was hoping once I did this, the OTA update process would fix itself. While testing this out for you and writing this up, LMSA said I had an update...and my OTA "check for updates" feature said I did not. So I think long term, this is now how we update our phones. Hopefully that means we'll get 9 sooner, as a silver lining...
Feel free to reply if this doesn't make sense or something isn't clear, and I'll try to clarify further.

New to updating here
despree said:
Hey, had to get home to do some digging. I tried different drivers from a few different places, but I'm pretty sure the ones that worked for me are "15 Second ADB Installer", forum.xda-developers.com/showthread.php?t=2588979 . Install those guys, then start the update process. Before the update process, under Device Manager, your phone should show up as "Universal Serial Bus devices -> Moto Z (2)" (or similar). This is correct when your phone is normally operating and connected to the PC with USB debugging.
Then, during the update process, it will put your phone in bootloader mode (with the android dude on his back, chest open). This is where the problem is. Whatever device it loads your phone as (I forget now), is wrong. Under device manager it should be "SAMSUNG Android Phone-> Android Bootloader Interface". So whatever device it loads as, update the drivers; and, with the new drivers you installed above, select that one (Samsung Android Phone/Android Bootloader Interface). I'm not sure at this point; you may need to restart the update process, or it may detect the new device and go from there. But either way, once it gets your phone back to that bootloader mode (android dude on his back), scroll over to "Bootloader Logs", and you should actually see some entries happening. If you do, DO NOT DO ANYTHING ELSE UNTIL IT'S DONE. Or you'll be restoring your phone and blowing everything away. Personal experience.
After that, you should be good and able to update!
Worth noting: I was hoping once I did this, the OTA update process would fix itself. While testing this out for you and writing this up, LMSA said I had an update...and my OTA "check for updates" feature said I did not. So I think long term, this is now how we update our phones. Hopefully that means we'll get 9 sooner, as a silver lining...
Feel free to reply if this doesn't make sense or something isn't clear, and I'll try to clarify further.
Click to expand...
Click to collapse
I am pretty new to updating andriod devices, is there a toturial that might have some type of step by step out there that you might know about? thanks a lot

omiCar said:
I am pretty new to updating andriod devices, is there a toturial that might have some type of step by step out there that you might know about? thanks a lot
Click to expand...
Click to collapse
Hey omiCar, I do not; not for this. Just did a lot of tinkering. I'll add some more info below to my previous post; this assumes you know how to change device drivers for a device on a windows machine. If not, Google should be able to fill you in on that process!
This is an atypical upgrade method; on the flip side, it's also a lot less "technical" than most upgrade processes. On a windows machine, first install the other drivers I mention above. Then power off your phone, then press and hold the power and volume down buttons until it turns on; this will turn on your phone in bootloader mode. Connect it to your PC, and verify under Device Manager it comes up as "SAMSUNG Android Phone"; if it's anything different, change the driver so that it's that. Now, when the update process reboots your phone for you and puts it in bootloader mode, it will be able to find your phone.
Download the Lenovo mobile smart assistant tool (LMSA, above), and in there is an "update" function; that's the one I refer to above. Reboot your phone so it starts normally, and launch the "Mobile Assistant" app on your Moto Z2; connect your phone to your PC, and make sure the Mobile Assistant can see your phone. Navigate to the update process, and start that. It will take a really long time to download the 1GB+ image with almost no change on screen, so be ready to wait; then it will reboot your phone, and you'll see that android on it's back again screen. It will take another long time to update your phone (30-60 min?). I think it may self reboot a few times during that process? It will then "optimize" the apps, and then you'll be back to your lock screen, ready to go.

despree said:
Hey omiCar, I do not; not for this. Just did a lot of tinkering. I'll add some more info below to my previous post; this assumes you know how to change device drivers for a device on a windows machine. If not, Google should be able to fill you in on that process!
This is an atypical upgrade method; on the flip side, it's also a lot less "technical" than most upgrade processes. On a windows machine, first install the other drivers I mention above. Then power off your phone, then press and hold the power and volume down buttons until it turns on; this will turn on your phone in bootloader mode. Connect it to your PC, and verify under Device Manager it comes up as "SAMSUNG Android Phone"; if it's anything different, change the driver so that it's that. Now, when the update process reboots your phone for you and puts it in bootloader mode, it will be able to find your phone.
Download the Lenovo mobile smart assistant tool (LMSA, above), and in there is an "update" function; that's the one I refer to above. Reboot your phone so it starts normally, and launch the "Mobile Assistant" app on your Moto Z2; connect your phone to your PC, and make sure the Mobile Assistant can see your phone. Navigate to the update process, and start that. It will take a really long time to download the 1GB+ image with almost no change on screen, so be ready to wait; then it will reboot your phone, and you'll see that android on it's back again screen. It will take another long time to update your phone (30-60 min?). I think it may self reboot a few times during that process? It will then "optimize" the apps, and then you'll be back to your lock screen, ready to go.
Click to expand...
Click to collapse
Hi, thank you for your quick response, I will be attempting to do this tonight or tomorrow, I will circle back with an update, again thank you !

Backup phone first with LMSA
That's what I had to do so it would stop hanging at 51%. Use LMSA backup feature first then upgrade

I just got one of these phones and it came with 7.1.1. And says no updates. If I connect it in Download mode it shows under "Android Device" -> "Motorola ADB Interface". You're telling me that's not correct and it should be Samsung? That's strange. I'll check this out.

Quick question and I'm sorry it doesn't relate to your guys update issues but I've been looking desperately for a copy of the Z2 Force-Nougat SystemUI apk, and I can't find anyone who can upload it because they've all already upgraded to Oreo... So if possible, could 1 of you guys who are still on Nougat upload a copy of your SystemUI apk ?? It would be so GREATLY APPRECIATED, I've been searching forever...

bdizzle1686 said:
Quick question and I'm sorry it doesn't relate to your guys update issues but I've been looking desperately for a copy of the Z2 Force-Nougat SystemUI apk, and I can't find anyone who can upload it because they've all already upgraded to Oreo... So if possible, could 1 of you guys who are still on Nougat upload a copy of your SystemUI apk ?? It would be so GREATLY APPRECIATED, I've been searching forever...
Click to expand...
Click to collapse
You can take any flashing all, use a tool to merge the sparsed system images and mount the system img and pull it that way if you really need it

wrenhal said:
I just got one of these phones and it came with 7.1.1. And says no updates. If I connect it in Download mode it shows under "Android Device" -> "Motorola ADB Interface". You're telling me that's not correct and it should be Samsung? That's strange. I'll check this out.
Click to expand...
Click to collapse
Answered my own question. The flash worked fine. I switched over to the log at 51% and watched it copying files and eventually it finished up and the phone rebooted to Oreo. All in all, if say it took only fifteen to twenty minutes.
Sent from my KIW-L24 using Tapatalk

despree said:
Hey all, I recently purchased my Moto Z2 Force att branded phone from motorola.com (when it was on sale for $300); love it so far...but. it's currently on 7.1.1...and refuses to update. I've talked to att customer service for over an hour, and they swear they've done everything they can do from the network side; that it must be a phone issue (...I don't buy it). Moto says they aren't in charge of updates, must be an update issue. Thanks guys.
So I want to get to Oreo, *without* invalidating my warranty.
I downloaded the Lenovo MOTO Smart Assistant (pointed out in other threads), and it recognized that I was out of date. The Flash section of the LMSA seemed to download the latest image, rebooted my phone...and stopped. Showed 51% done, and didn't move once left for hours. The phone is showing the fastboot screen (as if you had held the volume buttons and the power button), but doesn't seem to be going any further.
What the crud.
So I have an "official" image downloaded with the tool, ADB tools installed, and while I haven't rooted and reflashed this phone, I've done it in the past to others. Is there any way to use the image I DL'd with ADB or something else, without invalidating my warranty? (Pics show what was downloaded by the LMSA tool).
Click to expand...
Click to collapse
https://forum.xda-developers.com/z2-force/help/how-to-manually-update-att-motorola-z2-t3879143

Question Can't unlock my Poco f3 bootloader with mi tool

Hi there
It's been two days that I want to unlock my Poco f3 bootloader with mi tool but i can't, i've been very frustrated, i am worried if i'm stuck with official rom! could you please help me, I've searched google and the forums and tried a lot of workarounds but nothing works.
So first issue is that i do not receive the sms verefication when i log in to MI tool.
Then I tried the QR code method, i scanned it, openned the URL and allowed sign in. MI tool says local verefication is done, and wants me to relogin, I click on the login button and the tool starts loading but won't load anything!
After that, i tried loging in with facebook, it showed me an error and i clicked on not now, and it showed me a login page, i tried loging in and it logged in successfully!
however, once i connect my phone in fastboot mode to my computer, the tool shows "checking phone status" then says "unknown error 1004, try again later)
Is the mi tool service down or i'm doing something wrong. I tried with two accounts so far.

I've had a similar problem if the if you can't sign in while you're in fast Boot and you have the mi tool open use another phone to try to get the verification that's what I had to do and then you can sign in with the mi tool , I just used Google voice so there was no need for another phone but that's what I did

jefffrom said:
I've had a similar problem if the if you can't sign in while you're in fast Boot and you have the mi tool open use another phone to try to get the verification that's what I had to do and then you can sign in with the mi tool , I just used Google voice so there was no need for another phone but that's what I did
Click to expand...
Click to collapse
Sorry I got confused a bit, do you mean that i have to go to fast boot on my phone and it needs to be connected to the pc, and then try to sign in with mi tool?
because the way i do it, i have the phone on, i try to sign in first, so i can scan the QR code or get the SMS code.

maybe it is a problem with the drivers, try to download the ones from that guide and connect the phone in normal mode (allow usb debug when the message appears) and also connect it in fastboot mode so that it recognizes the drivers
https://www.getdroidtips.com/unlock-bootloader-poco-f3/

viroxnet said:
maybe it is a problem with the drivers, try to download the ones from that guide and connect the phone in normal mode (allow usb debug when the message appears) and also connect it in fastboot mode so that it recognizes the drivers
https://www.getdroidtips.com/unlock-bootloader-poco-f3/
Click to expand...
Click to collapse
no luck.
mi unlock tool does not send me my sms verefication and when i login with qr code it just gets stuck in loading screen

oasis1701 said:
no luck.
mi unlock tool does not send me my sms verefication and when i login with qr code it just gets stuck in loading screen
Click to expand...
Click to collapse
Send image

Rstment ^m^ said:
Send image
Click to expand...
Click to collapse
so first i open mi unlock tool on pc and then click i agree, and then on the button that shows the qr code.
then i go to my phone, settings, mi account, scan qr code, and i scan the code on the screen, and click sign in when it prompts me to. then this screen appears: https://www.dropbox.com/s/1zthjiod03fotwd/Screenshot 2022-05-12 20.33.30.png?dl=0
then i click on the text that says login and this shows up: https://www.dropbox.com/s/5kyepva0zdc6m34/Screenshot 2022-05-12 20.33.47.png?dl=0
and just stays there forever

maybe version? in the images it is different from the current one.
Sometimes is windows permission, use the app in your desktop and execute as administrator
https://miuirom.xiaomi.com/rom/u1106245679/6.5.224.28/miflash_unlock-en-6.5.224.28.zip

viroxnet said:
maybe version? in the images it is different from the current one.
Sometimes is windows permission, use the app in your desktop and execute as administrator
https://miuirom.xiaomi.com/rom/u1106245679/6.5.224.28/miflash_unlock-en-6.5.224.28.zip
Click to expand...
Click to collapse
tried with this version too, still no luck. in fact when i use this version it wants me to update to another latest version.
IS the message "relogin to your account" normal? does it happen for all QR logins?

oasis1701 said:
tried with this version too, still no luck. in fact when i use this version it wants me to update to another latest version.
IS the message "relogin to your account" normal? does it happen for all QR logins?
Click to expand...
Click to collapse
maybe the problem is the account on the phone, try to delete the account and add it again.
On the phone and in the app you must log in with the same method (hopefully with the phone number)

viroxnet said:
maybe the problem is the account on the phone, try to delete the account and add it again.
On the phone and in the app you must log in with the same method (hopefully with the phone number)
Click to expand...
Click to collapse
thanks for helping
I signed out from mi account in the phone, rebooted, then signed back in. though interestingly enough, it did not ask me for my password but signed in without it. i had to turn on find my device and that one asked for the password though.
But again it didn't work for me same things keep happening

Hi there. A couple of days ago I was dealing with the same issues you're dealing with now. Here is some input which might help you and others who are currently stuck at the loading screen:
First, notice that there's a log file created by Mi Unlock on your computer which, at any rate, may help you mitigatating any issues. The file is located at:
C:\Users\YourUserName\AppData\Roaming\Xiaomi\miflash_unlock\Log\miflash_unlock.log
The error 1004 is, as far as I know, related to the unlockAPI being unreachable. Specifically, the QR login method results in an 401 error and for this reason, the loading page gets stuck.
Ditch the QR login method and instead log in with your password (the default method). If the SMS verification screen appears, wait for 60 seconds (there should be a timer indicating that) and click on RESEND. In my case, it was the second attempt that worked and the SMS transmitted successfully.
Now, as everybody else, I assumed this login method wouldn't work, as previously there were reCAPTCHA issues. That's probably why everyone recommended the QR method. In any event, as of today, this method should work again and might get you logged in successfully, without receiving the 1004 error.
I'm afraid there is the possibility that you'll need to wait for another 168 hours as you logged out of your account on the POCO F3. If that's the case, try next week the same aforementioned method again. If that doesn't work, try the QR method.
Good luck!
EDIT: Clarifications and formatting.

I also face the same problem earlier this month! I think I try a different version and the older version is working for me with the QR code solution. Good luck!

I have a similar problem. I tried different versions of the unlock tool (5.5.224.24, 6.5.224.28, 6.5.406.31) and I get the same error (Local verification has been completed please re-login your account) when checking the authentication with a barcode. Clicking on Login button doesn't do anything.
However, I can log in with an email address or phone number and SMS verification works. If I try to unlock the device i get an error Couldn't unlock. Please rebind and try again.
{
"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"
}
Also the driver for the Fastboot connection is the original Xiaomi.
If it helps anyone, there is a log file of the unlock tool on https://www.miamit.si/miflash_unlock.log

i got same issue, i got error 1004. i was try every method and got 1 solution and maybe can help. first to know i only one laptop running windows 10 and already have miunlock tool and has been install all driver. first try to Disable Driver Signature (you can find how to do on google) and restart. after boot reinstall driver you have, if you have miflash you can reinstall driver from that, make sure windows ask you to have permission to install driver. and last step try to open miunlock (my miunlock is latest version) and login to your account for unlocking, recommend to login using email or facebook to avoid SMS verification. if you can login you can see your error status at miunlock homescreen,if status error is not showing now you can unlock your bootloader. i hope my method can help everybody. good luck

185F8DB3227 said:
Hi there. A couple of days ago I was dealing with the same issues you're dealing with now. Here is some input which might help you and others who are currently stuck at the loading screen:
First, notice that there's a log file created by Mi Unlock on your computer which, at any rate, may help you mitigatating any issues. The file is located at:
C:\Users\YourUserName\AppData\Roaming\Xiaomi\miflash_unlock\Log\miflash_unlock.log
The error 1004 is, as far as I know, related to the unlockAPI being unreachable. Specifically, the QR login method results in an 401 error and for this reason, the loading page gets stuck.
Ditch the QR login method and instead log in with your password (the default method). If the SMS verification screen appears, wait for 60 seconds (there should be a timer indicating that) and click on RESEND. In my case, it was the second attempt that worked and the SMS transmitted successfully.
Now, as everybody else, I assumed this login method wouldn't work, as previously there were reCAPTCHA issues. That's probably why everyone recommended the QR method. In any event, as of today, this method should work again and might get you logged in successfully, without receiving the 1004 error.
I'm afraid there is the possibility that you'll need to wait for another 168 hours as you logged out of your account on the POCO F3. If that's the case, try next week the same aforementioned method again. If that doesn't work, try the QR method.
Good luck!
EDIT: Clarifications and formatting.
Click to expand...
Click to collapse
Thank you, this helped me quite a lot. I waited another day and the sms verefication works now.
The fact that the sms and QR method didn't work for 24 hours throw me off, now i know that the QR method is broken.