Hi
I have a Nexus 5 currently on KitKat 4.4, and am trying to manually update to 4.4.1 but with no success
Have read and followed all stages in posts relating to updating the firmware, have downloaded the 4.4.1 file and Android SDK.
All steps work as they should, have got as far as my PC recognising my device serial number, until I get to the step where I enter, in the command prompt opened from the platform tools folder
adb sideload KitKat.zip (KitKat.zip being the name I have given the file)
I then keep getting the error message "unable to read file KitKat.zip"
I have tried with and without .zip in the command but still no luck
Help please?? I have run out of ideas to try
The command adb sideload (filename).zip has no space between side and load.
Sent from my Nexus 7 using XDA Premium HD app
---------- Post added at 02:44 PM ---------- Previous post was at 02:40 PM ----------
Also is your 4.4.1 update file in the platform tools folder? Are you opening the command prompt in the platform tools folder?
Sent from my Nexus 7 using XDA Premium HD app
Please ask questions in q&a. General is not for questions
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
When you type in the command prompt: adb sideload update, do not type in the .zip part in the command line
Sent from my Nexus 5 using Tapatalk
nohcho said:
When you type in the command prompt: adb sideload update, do not type in the .zip part in the command line
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Wrong. First, rename the file to "update.zip" without the quotes. Make sure it's not "update.zip.zip." . Make sure the file is in the platform-tools folder. The command is "adb sideload update.zip" no quotes
marleyfan61 said:
Wrong. First, rename the file to "update.zip" without the quotes. Make sure it's not "update.zip.zip." . Make sure the file is in the platform-tools folder. The command is "adb sideload update.zip" no quotes
Click to expand...
Click to collapse
Have tried renaming the file to update.zip as well as trying several other file names, doesn't make any difference the same error message appears
I was having the same issue. I just kept the ota name as it was when I downloaded it and added .zip to the end. It worked fine after that. Just copy and paste it in cmd
red83 said:
Have tried renaming the file to update.zip as well as trying several other file names, doesn't make any difference the same error message appears
Click to expand...
Click to collapse
Maybe a corrupt download. Try downloading again. Make sure you make file extensions visible so you don't accidentally name it .zip.zip. Then try my instructions again.
Are you booting to recovery then doing the power/volume up thing then select apply update from adb?
forgive me if you did this already, does your operating system display the three letter file extension like 'update.zip, adb.exe' etc.
marleyfan61 said:
Maybe a corrupt download. Try downloading again. Make sure you make file extensions visible so you don't accidentally name it .zip.zip. Then try my instructions again.
Are you booting to recovery then doing the power/volume up thing then select apply update from adb?
Click to expand...
Click to collapse
yes I put the phone into recovery mode as described in the online tutorials by holding the power button and the down arrow volume button simultaneously and from there I can select recovery mode and then into the sub menu that you popular by hold power and tapping the up volume button and it appears at the top of the screen, I then select ''update via ADB''....... by the way by default the windows drivers package doesn't have a specific ADB driver, and as a result you get an on screen prompt to verify this is the case.
When you activate usb debugging from developer options on the android desktop is when this becomes apparent, to get round this I have loaded up a couple of generic ADB drivers and tried them, they work as when you open the command prompt and specify the location of the adb.exe file it recognises the adb device when you put in ''adb devices''...its serial number/ imei can be seen from there.
Now here is the random part...when you populate the string under command prompt and then add '' adb sideload update.zip (exactly as that) you get an on screen prompt appear stating the ' cannot read update.zip '
I was thinking this file may be corrupt but I have located several now and none work at all.......basically I can run the adb.exe file from the ''platform-tools'' folder where the ''update.zip'' file has been located....regardless of what I name it or whether it is called kitkat.zip or without the .zip extension it still says it cannot read the file....what am I doing wrong??
red83 said:
yes I put the phone into recovery mode as described in the online tutorials by holding the power button and the down arrow volume button simultaneously and from there I can select recovery mode and then into the sub menu that you popular by hold power and tapping the up volume button and it appears at the top of the screen, I then select ''update via ADB''....... by the way by default the windows drivers package doesn't have a specific ADB driver, and as a result you get an on screen prompt to verify this is the case.
When you activate usb debugging from developer options on the android desktop is when this becomes apparent, to get round this I have loaded up a couple of generic ADB drivers and tried them, they work as when you open the command prompt and specify the location of the adb.exe file it recognises the adb device when you put in ''adb devices''...its serial number/ imei can be seen from there.
Now here is the random part...when you populate the string under command prompt and then add '' adb sideload update.zip (exactly as that) you get an on screen prompt appear stating the ' cannot read update.zip '
I was thinking this file may be corrupt but I have located several now and none work at all.......basically I can run the adb.exe file from the ''platform-tools'' folder where the ''update.zip'' file has been located....regardless of what I name it or whether it is called kitkat.zip or without the .zip extension it still says it cannot read the file....what am I doing wrong??
Click to expand...
Click to collapse
Try my suggestion above, worked for me. I was having the same problem.
red83 said:
yes I put the phone into recovery mode as described in the online tutorials by holding the power button and the down arrow volume button simultaneously and from there I can select recovery mode and then into the sub menu that you popular by hold power and tapping the up volume button and it appears at the top of the screen, I then select ''update via ADB''....... by the way by default the windows drivers package doesn't have a specific ADB driver, and as a result you get an on screen prompt to verify this is the case.
When you activate usb debugging from developer options on the android desktop is when this becomes apparent, to get round this I have loaded up a couple of generic ADB drivers and tried them, they work as when you open the command prompt and specify the location of the adb.exe file it recognises the adb device when you put in ''adb devices''...its serial number/ imei can be seen from there.
Now here is the random part...when you populate the string under command prompt and then add '' adb sideload update.zip (exactly as that) you get an on screen prompt appear stating the ' cannot read update.zip '
I was thinking this file may be corrupt but I have located several now and none work at all.......basically I can run the adb.exe file from the ''platform-tools'' folder where the ''update.zip'' file has been located....regardless of what I name it or whether it is called kitkat.zip or without the .zip extension it still says it cannot read the file....what am I doing wrong??
Click to expand...
Click to collapse
I'm not following some of what you are saying. I think it may be an adb driver issue. Have a look at this thread :http://forum.xda-developers.com/showthread.php?t=2514396
Also, I don't use adb.exe. I open a command prompt and navigate to the platform-tools folder and execute the commands in the cmd window. You say you are getting into recovery by doing the button presses. You should be able to connect your phone when not in recovery and within the cmd window execute "adb reboot recovery" to get into recovery. If that's not working it's a driver problem.
Beyond that I'm not going to be much more help - not that I've been any help since you are still having the problem.
marleyfan61 said:
I'm not following some of what you are saying. I think it may be an adb driver issue. Have a look at this thread :http://forum.xda-developers.com/showthread.php?t=2514396
Also, I don't use adb.exe. I open a command prompt and navigate to the platform-tools folder and execute the commands in the cmd window. You say you are getting into recovery by doing the button presses. You should be able to connect your phone when not in recovery and within the cmd window execute "adb reboot recovery" to get into recovery. If that's not working it's a driver problem.
Beyond that I'm not going to be much more help - not that I've been any help since you are still having the problem.
Click to expand...
Click to collapse
Yes what you said works, straight into recovery no probs by putting 'adb reboot recovery in a cmd prompt window to the specific directory that the abd file is located......(in platform tools) then if I put adb devices the serial number comes up straight away with 'sideload next to it.
So then I put adb sideload update.zip, and guess what!
cannot read update.zip....
Have you tried my suggestion?
richport29 said:
Have you tried my suggestion?
Click to expand...
Click to collapse
Yes have just tried what you suggested and only added .zip to the original name of the file and still the same error message appears
marleyfan61 said:
I'm not following some of what you are saying. I think it may be an adb driver issue. Have a look at this thread :http://forum.xda-developers.com/showthread.php?t=2514396
Also, I don't use adb.exe. I open a command prompt and navigate to the platform-tools folder and execute the commands in the cmd window. You say you are getting into recovery by doing the button presses. You should be able to connect your phone when not in recovery and within the cmd window execute "adb reboot recovery" to get into recovery. If that's not working it's a driver problem.
Beyond that I'm not going to be much more help - not that I've been any help since you are still having the problem.
Click to expand...
Click to collapse
Should I be "de-activating/activating" anything else other than activating the developer options and selecting USB debugging....should I remove my SIM card??
Anything else I may have overlooked please?
red83 said:
Yes have just tried what you suggested and only added .zip to the original name of the file and still the same error message appears
Click to expand...
Click to collapse
Try re-downloading the ota. Place it in the platform-tools folder, and try again.
7ed504f678cea49ecf0974e8cd956e2974e3f943.signed-hammerhead-KOT49E-from-KRT16M.7ed504f6.zip
richport29 said:
Try re-downloading the ota. Place it in the platform-tools folder, and try again.
7ed504f678cea49ecf0974e8cd956e2974e3f943.signed-hammerhead-KOT49E-from-KRT16M.7ed504f6.zip
Click to expand...
Click to collapse
Have tried re-downloading the file from several locations, placing it directly into the platform-tools folder and only adding .zip to the file directory name.....still no joy
When you type adb devices, what comes up?
Unless you absolutely have to have the camera fix in this update right now, then I suggest you just wait til the OTA becomes available on your phone. The camera fix is the only significant thing in the update. I don't know what the issue is with what you are trying but I suspect there is something not being done right. Sounds like it's not worth the frustration tho.
Hello. Has anyone rooted the Ulefone Power 6 yet? Im looking to have TWRP installed onto my new Power 6. My goal is to figure out a way to add user profiles, as it currently does not have them activated. I read online that you could edit the .prop to have any android activate the user profiles, but i cannot do this without my phone being rooted. Thanks in advance.
Start Here
Dvalin21 said:
Start Here
Click to expand...
Click to collapse
Sorry, This is for the original Ulefone Power, not the Power 6. Different phones. The instructions didn't lead me to anything useful. I have since update my phone to the latest firmware via the stock update app. I still haven't found a successful way to root the Power 6. There is this thread (https://www.getdroidtips.com/root-ulefone-power-6/), but the ADB commands to not work, and does not fastboot my phone to install the patched image. But either way, the instructions do not include a TWRP, so Im back to square one. HELP!
How to root Ulefone Power 6 (Build Power_6_SF1_V07) Updated 9/22/2019
OK. It was tough, but I finally found a way to root the Ulefone Power 6. I still haven't figured out a way to install TWRP, but that's because i have to build a custom recovery, and that's too advanced for me. So, anyone is welcomed to help out with building a custom recovery for TWRP. As for the root, This is what you will need:
Pre-Requirements:
Device battery charged up to 50%.
Developer Options enabled with OEM Unlocking and USB Debugging enabled
Remember to take a full backup of device data (Internal Storage, SMS), it will get formatted.
A Windows or Mac PC/Laptop is necessary to flash Magisk
A USB cable to connect your device with your PC
Download Links:
Download Minimal ADB Fastboot 1.4.3 (Portable). Extract it to your desktop.
It's best to give administrator privileges to the tools before you use them. To give them admin privileges:
Right click on adb.exe and select "Properties" at the bottom of the menu. Click on the "Compatability" Tab and check the "Run this program as an Administrator" box. Click on the "Apply" button and then the "OK" button to close the properties window.
Repeat the same process for the "cmd-here.exe" and the "fastboot.exe" files.
Ulefone USB Drivers. Extract it to your desktop and make sure you install the drivers.
MTK USB Drivers. Extract it to your desktop and make sure you install the drivers.
Latest Ulefone Power 6 Stock ROM. Or you could make a back up yourself. (latest rom as of 2/25/20 is GQ3081SF1_M860B1_Ulefone_20190921_V07(Non-EU) ).Extract it to your desktop.
MTK SP Multi Port Download Tool. This will be used to flash the most recent Ulefone rom on your device. Extract it to your desktop.
Download Magisk Manager
After downloading the Stock ROM (will be a .ZIP file), extract it to your PC.
Connect your device via USB cable
Find the "boot.img" file inside the Stock Rom folder you just extracted and copy only the "boot.img" file to your devices storage.
Copy Magisk Manager.apk to your devices storage
Using your device, install Magisk Manager
Open the Magisk Manager on your device.
Select "Install" from the first option next to "Magisk is not installed" and again select install.
Now, tap on "Select and Patch a File".
Go to your devices storage where you have copied the "boot.img" file earlier and select it.
Magisk will start patching the boot image.
Once the boot image is patched, Magisk will save the image on your "Download" folder located on your devices storage.
Locate the patched image (magisk_patched.img) and copy the "magisk_patched.img" to your PC. Make sure the patched image (magisk_patched.img) is inside the same folder as the extracted ADB and Fastboot tool folder on your desktop.
Open/run MTK SP Multi Port Download Tool
Click on File from the Menu located at the top right and select "Open Download Agent File"
Locate and select "MTK_ALLInOne_DA.bin", located in the same folder as the MTK SP Multi Port Download Tool folder.
Press the "Open buton" to select the file and close the window.
Now, click on the "Scatter File" button located at the top left.
Locate and select the XXXXXXXX_scatter.txt file located inside the extracted Ulefone Power 6 Stock Rom folder.
Press the "Open buton" to select the file and close the window.
Now, tick the "BootRom+PreLoader COM Sel All" check box located under the "scatter file" button.
Now, Click on the "Scan" button located at the bottom right.
Select Yes from the pop up window
Now, power off you device and disconnect your device from your PC by removing the USB cable from your device.
Now, reconnect the USB cable to your device while it is powered off.
MTK SP Multi Port Download Tool should detect your device and a green bar should appear confirming the connection with the words "Scan Success!" to the left of the green bar.
Press the "Stop all" button located at the bottom right
Disconnect and reconnect your device from your PC
Uncheck the "BootRom+PreLoader COM Sel All" box and check only the line with the green bar.
Click on the tiny "Start" button located to the right of the green bar.
You can confirm the flash was successful when the words "PASS" is visible to the right of the tiny "Start" & "Stop" buttons
Once the flashing is complete, you can close MTK SP Multi Port Download Tool and power on your device.
Configure your device to get to the home screen (skipping as many options as you can. You will have to format one more time) and enable Developer Options, OEM Unlocking and USB Debugging again.
Make sure your device is connected to your PC.
Now, you need to open up a command window (cmd window) inside the Minimal ADB Fastboot 1.4.3 (Portable) folder. To do this, open the "cmd-here.exe" file.
Next, enter the following command in the cmd window:
adb devices
(this command will confirm your device is connected to your PC via ADB )
Your device will show a pop up window asking for permission to connect via ADB. Click on the "Always Trust This Device" and Accept the connection
If successful, you should see the word "Device" to the right of your devices name on the list that the cmd window created.
Next, enter the following command:
adb reboot-bootloader
(This command will boot your device into fastboot/bootloader mode. It will turn off and the device will have a black lit screen)
Check that your device is connected to your pc by entering the following command:
fastboot devices
(this command will confirm your device is connected to your PC via fastboot/bootloader mode ) If successful, you should see the word "Device" to the right of your devices name on the list that the cmd window created.
Next, enter the following command:
fastboot flashing unlock
(if nothing happens, press the Volume up+ on your phone to start the unlocking of the bootloader)
(this will unlock your bootloader)
Next, enter the following command:
fastboot getvar unlocked
(this will confirm you have unlocked your bootloader. It will say "unlocked: yes")
Next, enter the following command:
fastboot flash boot magisk_patched.img
(This will replace your stock image with the patched image you created using Magisk Manager)
Next, enter the following command to reboot your phone:
fastboot reboot
Install magisk manager using your file manager. Make sure to follow directions when it asks you to give special permissions to install.
Open Magisk Manager and click on "OK" when it starts up and asks you for "additional setup".
Congratulations! Your device is rooted.
Extra notes:
If you come across a red watermark with the Chinese words and "Tee Keys" and/or "Google Keys" on the top right of your devices screen, this is how you fix it.
make sure your device is turned on and connected to your PC.
Open "cmd-here.exe" located in the Minimal ADB Fastboot 1.4.3 (Portable) folder.
Next, enter the following command:
adb shell pm uninstall -k --user 0 com.mediatek.factorymode
(This command will not do anything at the moment, but will remove the watermark after you reboot your device)
Next, enter the following command to reboot your device:
adb reboot
The watermark should be removed when your device restarts again.
ENJOY!
19Henry83 said:
OK. It was tough, but I finally found a way to root the Ulefone Power 6. I still haven't figured out a way to install TWRP, but that's because i have to build a custom recovery, and that's too advanced for me. So, anyone is welcomed to help out with building a custom recovery for TWRP. As for the root, This is what you will need:
. . . . .
. . . . . . . . . . .
. . . . . . . . . . . . . . .
ENJOY!
Click to expand...
Click to collapse
Thanks a heap for all these instructions, would not have been able to do this without them.
Just a few extra pieces of information for anyone else caryring out the above steps:
- If you your stock ROM doesn't have a file manager in order to open/execute the MagiskManager APK file then using Chrome to download the APK file will allow you to execute it.
- in the SP Multi Port Tool, after checking the line with the green bar and clicking start you'll notice the time in seconds counting next to the start button. At this point you may need to unplug your USB cable and replug it in order for the SP Multi Port Tool to detect the devices and actually start properly
- If the SP Multi Port Tool requires a checksum.ini file you can follow the instructions on the hovatek site (Google 'checksum.ini generatemediatek hovatek' I'm a new user so can't post links):
Note there is a download link for the CheckSum_Gen.zip file which will require you to register for an account on the hovatek website. You can create a junk/throw away account with a fake email as it doesn't require email confirmation. Also all of the files inside the CheckSum_Gen.zip folder need to be placed inside of the stock ROM folder where the scatter file is located.
- The watermark can only be removed after the MagiskManager carries out its additional setup and after root access is complete.
Still hoping to find a compatible TWRP recovery. If anyone builds one please let us know!
Hi, 19Henry83
I did try your method and it works great. I rooted my Power 6. The thing is I did this in hope to fix a freezing touchscreen issue. Touch screen frezzes and I need to lock/unlock my phone constantly to fix it. Now I'm convinced this is not a software issue and I will return the phone to the seller. So I wanted to get back to the original firmware. When I do that however there is still that red watermark and my IMEI is deleted. Is there any way to get back to the factory software and not have the red watermark, as I assume it will void my warranty.
I Need help please ,, I need the TWRP Recovery, Tool / Utility for the Ulefone Power 6, I have looked for it in many web pages and I cannot find it, all the ones I find have the same name "3.3.1 Power 6" and not It works for me when I install them, I get the same recovery that I had when I try to enter
jiroscop said:
Hi, 19Henry83
I did try your method and it works great. I rooted my Power 6. The thing is I did this in hope to fix a freezing touchscreen issue. Touch screen frezzes and I need to lock/unlock my phone constantly to fix it. Now I'm convinced this is not a software issue and I will return the phone to the seller. So I wanted to get back to the original firmware. When I do that however there is still that red watermark and my IMEI is deleted. Is there any way to get back to the factory software and not have the red watermark, as I assume it will void my warranty.
Click to expand...
Click to collapse
Hello Jiroscop. I had the same problem and only noticed after i read your post. Now, a couple months later, i managed to use an IMEI changer to insert my IMEI found on my original box where my phone came in. It should have two IMEIs. I don't know if i can explain on this forum. Try researching it on your own and get back to me if you cannot find a way to fix your phone.
NOTE: you will need your original IMEI's, changing the IMEI's with anything other than the original ones will brick your phone.
The One-for-All Guide to rooting, improving, and fixing various errors in Xiaomi Redmi Go!Hello everyone! This thread that I made is for all people who wants to modify and gain full access, as well as to repair their Xiaomi Redmi Go devices the well-guided way, I've noticed that nobody has made an all-in-one guide for this phone so I decided to do it, this thread will keep on expanding depending on what I will discover about this phone, but for now, here is the thread, i expect that you have at least a little amount of knowledge when it comes to phones such as ADB and Developer Options.
What can we do with Xiaomi Redmi Go:
1. We can root it, and the best root manager for this phone is Magisk, SuperSU is also good, but if you're planning to use your phone for mobile banking, then Magisk is right for you. (Unfortunately this isn't true right now due to ctsProfile being hard to manipulate, Redmi Go supports hardware backed key attestation which means your device will definitely be not certified no matter what you do, so until we get a new method, don't root your phone if you want to use apps like Google Pay
2. TWRP is the current custom recovery available for this phone, it has flaws, but its currently the best out there, so its worth the shot to install it, the thread for it will guide you.
3. No custom kernels, people said that they have managed to install AOSP 9 and GSI on this device and made it boot up, but for me, it's better to wait for the official ROM update, after all, the device is still supported.
Prerequisites:
1. Xiaomi Redmi Go
2. An internet connection, a strong one is recommended if you want to download a ROM.
3. A computer with SDK Platform Tools ready to use, this is required, the link is here: https://developer.android.com/studio/releases/platform-tools
Don't forget to also get its driver! The link is also here: https://developer.android.com/studio/run/win-usb
The drivers are tricky to install but I will guide you on doing it in the easiest way possible, please continue on the thread.
4. SD card, your user data will be erased later, better back your files up, this is a warning.
5. Turning on "OEM unlocking" and USB Debugging in Developer Options, this is also really important!
Table of contents:
1. Unlocking the bootloader (and setting up ADB)
2. Rooting
3. Applying the custom recovery
4. Additional modifications
5. Stock ROM links
6. Bonus Section
WARNING: I am not responsible for anything that happens to your device as you follow my guide, do not blame me if you turned your device into a paperweight, made it explode, made it fly or whatever it may be, you chose to modify this phone and you should be accountable for it, you must know the consequences of what you're doing, try to point your finger at me because of what YOU did and I will laugh at you.
I am ready to assist though, so please feel free to ask some questions!
Let us begin, this will take several minutes, so please be patient and avoid rushing.
1. Unlocking the bootloader.
NOTE: This requires your computer to have SDK Platform Tools extracted to any location as long as its easy to access, and its really complicated to talk about it here, this step doesn't include the method where you request a code from Xiaomi, but I've provided a link for it.
A. First, get your phone up, and open the folder on where the SDK Platform Tools are placed, make sure that your in the directory where you see the .exe files of the SDK, now, hold Shift on the keyboard and click "Open Command Prompt here" and type "adb reboot bootloader", without quotes don't forget! This applies to all the steps that I will provide, don't forget to change the USB connection mode of your phone to PTP for it to be detected by ADB! (Only applies to Windows 8/8.1) Once your phone is asking for an authorization, check "Always allow this computer" then tap allow.
B. Once your device has been booted up into Fastboot or the bootloader, check first if your device is being detected, type "fastboot devices", if yes then proceed, if no, then stop here for now.
1B. If this happens then you may have to check your drivers and see if its installed correctly, once your device can be seen at "adb devices" it should also been seen in "fastboot devices" and when the phone is in adb sideload, if not then you have to reinstall ADB, get the proper drivers and do it again.
C. Now, type "fastboot oem unlock-go", the terminal will warn you that all of your user data will be removed, if you have them backed up then and go ahead and enter the command, if not, then just type "fastboot reboot" and start backing up your files, then do this again.
D. The phone will boot up and say "Erasing", to confirm that your phone has its bootloader unlocked, once it boots up again see if it says "Unlocked" on the bottom part of your screen, if there is then congratulations, it should be unlocked at this point.
1D. https://www.getdroidtips.com/unlock-bootloader-xiaomi-redmi-go/, this one particular link provides you on how to unlock the bootloader by entering a certain code, I believe this is a safer method but requires a bit of time, go here if you're interested.
NOTE: The phone supports the command "fastboot flashing unlock_critical" if you are going to unlock your phone with the normal command (fastboot oem unlock_go/fastboot flashing unlock), consider using this 2nd command too, what it does is that it allows you to also flash partitions you supposedly don't have access to, just be very careful not to flash any wrong file! It will be useful to make the "flash_all.bat" script work that you can find on the fastboot ROM for this device, more below!
Once your bootloader has been unlocked, you can now proceed to the other steps that I provided here, don't forget to enable USB Debugging on your Developer Options.
1.2 Setting up ADB
1. Grab your phone, unlock and open your Developer Options then enable "USB Debugging", then change your connection type to "PTP" if you are using Windows 8/8.1, I am not sure if this is required on 7, but it is not needed on Windows 10.
2. Go to this link: https://developer.android.com/studio/releases/platform-tools and download the .zip file, then extract it to a location that is easy to access, like your desktop.
3. Get the official Google drivers here: https://developer.android.com/studio/run/win-usb download the .zip file as well, and extract it too.
4. Go to the extracted folder of your SDK Platform Tools, and go to the directory where you can see various .exe files such as "adb.exe", now, hold the Shift key then click the Right mouse button, then click "Open command prompt here" If this doesn't work for you, open up CMD with admin rights, then type in cd *the location of your platform tools* say on mine, I will input cd C:\Users\James\Downloads\platform-tools_r31.0.3-windows\platform-tools then enter
5. Open your Device Manager by pressing Windows + R, put "devmgmt.msc" without any quotes then Enter, do not close the Device Manager until you're done with all the steps! And please be fast here too or else ADB will not work, now go to your extracted folder of the Google USB driver, and look for the file "android_winusb.inf", copy the location path of it as you will need the exact location path of the file later, in my case it was "C:\Users\Symphony\Desktop\latest_usb_driver_windows\usb_driver\android_winusb.inf".
4A. There are 3 main ADB devices that you have to install, Android ADB Interface, Android Bootloader Interface and Android Composite ADB Interface, so I will divide this into 3 sections, have your Device Manager, and the exact location of the .inf.
NOTE: Turn off the internet connection of your computer, why? Because, if you let Windows install the drivers for you, the drivers may be incorrect and will break things apart, as we will encounter several "Unknown devices" in the Device Manager and we have to update them with the extracted files from Google.
Android ADB Interface
1. Now, make sure that USB Debugging is enabled, now plug in your phone and let the drivers install WHILE your computer is offline, now go to your Device Manager after the driver installation and you should see that there is a driver named "Android" with an exclamation mark.
2. Select the "Android" driver with an exclamation mark, then click "Update device driver", click "Browse my computer for driver software" then click "Let me pick from the list of devices on my computer", click Next, then click "Have Disk", now, remember the location path you copied earlier? Now paste that path (like C:\Users\Symphony\Desktop\latest_usb_driver_windows\usb_driver\) to the white bar under "Copy manufacturers files from:", overwrite the A:\ with your copied path then Browse, select the "android_winusb.inf" and click OK, now, select the "Android ADB Interface", once the driver has been installed and the interface doesn't give errors such as "The device cannot start", then you're good to go.
NOTE: If you plug your phone and there is no "Android" device with exclamation mark, you can proceed to try and see if adb detects your device by typing "adb devices" in the command right now, it should be since this is what I experienced when setting up my device in Windows 10, this step usually applies only if you are using Windows 8/8.1
Android Bootloader Interface
1. To test, go to the command prompt you opened earlier, and type "adb devices", the device should now be detected at this point, when it does, type "adb reboot bootloader".
2. Now, make sure USB Debugging is enabled on the device before booting it into bootloader, now plug in your phone again and let the drivers install WHILE your computer is offline, Go to your Device Manager after the driver installation and you should see that there is a driver named "Android" with an exclamation mark.
3. Select the "Android" driver with an exclamation mark, then click "Update device driver", click "Browse my computer for driver software" then click "Let me pick from the list of devices on my computer", click Next, then click "Have Disk", now, remember the location path you copied earlier? Now paste that path (like C:\Users\Symphony\Desktop\latest_usb_driver_windows\usb_driver\) to the white bar under "Copy manufacturers files from:", overwrite the A:\ with your copied path then Browse, select the "android_winusb.inf" and click OK, now, select the "Android Bootloader Interface", once the driver has been installed and the interface doesn't give errors such as "The device cannot start", then you're good to go.
Android Composite ADB Interface
1. Before proceeding, type "fastboot devices", the device should now also be detected on fastboot, now, type "fastboot reboot", and afterwards, enable "USB Debugging" on the Developer Options, then go your command prompt, then type "adb reboot recovery".
2. Now, now plug in your phone again and let the drivers install WHILE your computer is offline, now go to your Device Manager after the driver installation and you should see that there is a driver named "Android" with an exclamation mark.
3. Select the "Android" driver with an exclamation mark, then click "Update device driver", click "Browse my computer for driver software" then click "Let me pick from the list of devices on my computer", click Next, then click "Have Disk", now, remember the location path you copied earlier? Now paste that path (like C:\Users\Symphony\Desktop\latest_usb_driver_windows\usb_driver\) to the white bar under "Copy manufacturers files from:", overwrite the A:\ with your copied path then Browse, select the "android_winusb.inf" and click OK, now, select the "Android Composite ADB Interface", once the driver has been installed and the interface doesn't give errors such as "The device cannot start", then you're good to go.
2. Applying the recovery/custom recovery
A. Open up your phone and ensure that USB Debugging has been enabled, now, open up your command prompt just like in Step 1 in Unlocking the Bootloader and type "adb reboot bootloader"
B. Next up, type "fastboot flash recovery path/to/recovery.img", substitute the path/to/ with the actual location of your recovery, and please make sure that the name of the image is "recovery.img"! Or else it will not overwrite/update the recovery, you can also put your recovery.img directly within the platform-tools folder so that all you have to type is "fastboot flash recovery recovery.img" then press enter.
C. Once your done, reboot the phone and press Volume Up + Power at the same time, and the recovery will start. (You may want to do this else the recovery will be automatically removed and replaced with the stock one)
1C. For the stock recovery, once you press the combination, the phone will say "No command", at this point, hold your Power button and press Volume up one time to get into recovery.
https://forum.xda-developers.com/android/development/recovery-twrp-3-3-0-redmi-t3929282 here is the link of the TWRP recovery, I encourage you to follow the steps mentioned in the post properly.
WARNING: The fix I provided below is now pushed here for 1 certain reason, before you try to root your phone and do everything else, you must decrypt your internal storage first and it is quite easy, first you must get the decrypt.zip linked in this thread (if the .zip cannot be found, I still have a copy of it), go to TWRP and do "format data", not Wipe Data! How so? Once you reboot to TWRP, it will show you the "Wipe" button, tap that, then the "Format Data" button should show up, this will require you to type in "yes" so type it in, then once it is done formatting, go back to the main TWRP screen, tap "Reboot", then "Reboot to Recovery", afterwards you must go to "Install" then proceed to install the "decrypt.zip", after that you can now flash .zip files from your internal storage too, but beware that you must do this every time you update your device!
3. Rooting your phone
A. To get started, install TWRP for your phone first.
B. Get the .zip file of Magisk/SuperSU so you can install them, the links are https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 and https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
C. Reboot your phone to recovery or just plug it in, open the command prompt again just like in the previous step and put "adb reboot recovery" without quotes.
D. Tap "Install" on your TWRP recovery and select the respective installation .zip file of your chosen root management app, and wait for it to finish.
1D. The .zip for both SuperSU and Magisk can be installed through "adb sideload", if incase you don't have an SD card! It may also work with fastboot as well but I need someone to confirm this.
E. When it's done, wipe the cache first, then reboot.
1E. If the root management app didn't appear in your phone after boot, just install the APK of it in the Play Store and check if root has been applied, if not, repeat step C and D again.
BONUS: It may be useful also to grab EdXposed or LSposed for Magisk and the link is here: https://forum.xda-developers.com/t/...or-of-xposed-oreo-pie-q-r-2020-07-19.4070199/ and here: https://forum.xda-developers.com/t/...e-magisk-module-edxposed-alternative.4228973/, please choose only one! You will use the normal Xposed if you're using a different root management app such as SuperSU, the link is here: https://forum.xda-developers.com/showthread.php?t=3034811
What this does is that if the app is an Xposed/EdXposed/LSposed framework module, any modifications it does to your phone will be based on memory only, it won't modify your phone directly which means your device will be clean, and if it incase the said modification bricks your phone, you can easily recover from it too!
BONUS 2: I also recommend getting the Busybox module from Magisk itself, it can easily be downloaded from the Magisk app, you will need this module if you want your root applications to work more efficiently and avoid errors, as most of them requires Busybox to work, don't use the Busybox installer apps on Play Store as they modify /system directly, only use it if you are using SuperSU.
4. Additional modifications
Once you've managed to root your phone and everything else, what I recommend you could do with your device is to get the following apps:
Titanium Backup - It has the ability to back up apps on your phone, and even its data! this app could do so much more than with what I just mentioned.
LSpeed - A root boosting app that has almost every root tweak packed into it, its really convenient to use! I do not recommend using Entropy tweaks as I heard it is a placebo.
Greenify - For me, this is the only legit battery saving app aside from LSpeed which also offers tons of battery saving features, it requires Xposed to have more options you have to buy it to gain full functionality
ROM Toolbox - This app pretty much contains everything a rooted user needs, such as a terminal and root-based file manager.
System app uninstaller (optional) - Just in case if you're planning to remove some bloatware (the list of it is below)
Root Browser - An alternative to ROM Toolbox, this root explorer is really popular and gets the job done without any interruptions.
Terminal emulator - This will allow you to enter various commands on your phone, like being able to reboot the phone without using any keys.
In order to make the phone as fluid as possible, just leave it with stock ROM installed, try to also use lite apps like Facebook Lite to reduce RAM and battery consumption.
Kernel Adiutor - Another great root application, it's like LSpeed but it doesn't automate tweaks, it instead allows you to modify most of it on your own, then it reapplies your tweaks every time your cellphone will boot up if you tap the "Apply on startup" switch. the link for the app is here: https://m.apkpure.com/kernel-adiutor-root/com.grarak.kerneladiutor
NOTE: Most of these apps can be found on the Play Store, and please don't install any more similar root boosting apps such as HEBF, scripts such as V6 Supercharger, or modifying files like build.prop, it is due to the fact that this will conflict with LSpeed, as LSpeed contains most of the tweaks that past scripts and apps provide, this will result in your phone slowing down a lot, Greenify will require Xposed Framework which is mentioned above on the Rooting section, the link to LSpeed is here https://github.com/Paget96/LSpeed, because the app has been removed from Play Store.
WARNING: The perf.zip https://forum.xda-developers.com/android/development/-t3935220 here, that was provided in Xiaomi Redmi Go forum section must be applied with extreme caution, you have to make a backup of your build.prop in /system, and build.prop + default.prop in /vendor for easy recovery, you can use ZipMe to easily make a backup for these files.
5. Stock ROM links
https://xiaomirom.com/en/rom/redmi-go-tiare-global-fastboot-recovery-rom/, this link so far provides all the ROMs (both recovery and fastboot) available for download on this phone, and they are actually light enough, so it will be easy to download them.
https://xiaomifirmwareupdater.com/archive/miui/tiare/ a new link I've found recently, this rom contains the .tgz format of the latest ROM for the Xiaomi Redmi Go, which could be used for fastboot and Mi Flash Tool, just search for the model and go for Global.
NOTE: Most of the ROMs for this phone provided on several sites, even on the actual Xiaomi website, has an invalid format of .zip, and doesn't contain a flashall script, as a result, Mi Flash Tool will never be able to use these ROMs, you could not also use adb sideload and fastboot for these ROMs, only the stock recovery of the phone could install the ROM, due to the links provided above finally giving the latest ROM versions for the phone, extracting the stock recovery is very easy now, you can do it yourself but if you need a link, tell me.
5A. Applying the stock ROM
This section will be divided into 2 sections, flashing the ROM through recovery, flashing the ROM through fastboot manually, or automatically with flash_all.bat
Stock recovery method.
A. Download the stock ROM with .zip format and put it into your SD Card.
B. Flash your recovery back to stock with the steps given above, boot into your stock recovery, then using your Power button and volume keys to navigate, select "Apply update from SD card".
C. Select the .zip file and wait for the update to finish.
D. The device will boot up automatically after, if not, just go back to the main menu of the recovery and select "Reboot system", enjoy!
Fastboot manual flashing method.
A. Ensure that you have prepared your device and computer for ADB, now grab the ROM given in this thread in .tgz format, and keep extracting the file until you see the files such as "flash-all.sh" after extraction, as you need to extract the .tgz ROM two times before you could use it properly.
B. Now go to the extracted folder of the stock ROM, go the "images" folder and copy the following image files: boot.img, system.img, recovery.img (make a backup of this file somewhere!), vendor.img, cache.img, userdata.img, persist.img, and splash.img.
C. Paste them to the extracted folder of your SDK Platform Tools where various .exe files are located such as "adb.exe", or in my case the location is "C:\Users\Symphony\Downloads\platform-tools_r29.0.4-windows\platform-tools".
D. Now open your command prompt on this directory, or Shift + Right click, then plug in your phone, now type "adb reboot bootloader" so your phone will go to bootloader, don't forget to enable "USB Debugging" and PTP connection mode before rebooting! (only applies to Windows 8/8.1, it may vary on Windows 7 but it is different on 10, no need for PTP connection mode, you can just turn on USB debugging and that's all)
E. Now, this is a little tricky, but try to follow me as much as you can, make sure first that you are detected with "fastboot devices", input the following commands that I will give so you can flash the ROM to your phone, now go to the command prompt and:
To flash the boot.img to your phone, put the command: "fastboot flash boot boot.img"
For the recovery, the command is: "fastboot flash recovery recovery.img"
For the system or main OS: "fastboot flash system system.img"
For cache: "fastboot flash cache cache.img"
For persist: "fastboot flash persist persist.img"
For the vendor or additional system files: "fastboot flash vendor vendor.img"
For data or apps: "fastboot flash userdata userdata.img"
For splash or probably boot animation: "fastboot flash splash splash.img"
D. After that, type "fastboot reboot", and enjoy!
Fastboot automatic flashing method (NEW!)
A. Extract the fastboot ROM 2 times as instructed, after getting the files, grab all the files and copy it to the directory of your platform tools where files such as "adb.exe" can be found, just copy all the files in there and that's all you have to do.
B. Open the "flash_all.bat" on Notepad and remove the following lines:
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *tiare" || echo Missmatching image and device
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *tiare" || exit /B 1
Afterwards, save the .bat file, that should be ready to use now
C. As instructed above, you must also do "fastboot flashing unlock_critical" after unlocking your bootloader the normal way, this will act as your 2nd unlock command, without this, the flash_all.bat will not work as it should be.
D. Boot up your phone in fastboot mode, open up your adb devices and make sure that your phone is seen in "fastboot devices", once it does, type in "flash_all.bat" without any quotes and execute it, the command will now automatically flash everything without you doing anything else, it will also automatically reboot after doing so.
Bonus section:
1. TWRP-compatible stock ROM
For this part, in order for you to generate a TWRP-flashable stock ROM is by basically making it yourself, you have to make sure that your patch is latest, and its pretty much a good idea to just tick everything in the backup selection except for the recovery, as well as the cache as you don't need those.
Once you have it, go ahead and keep it somewhere safe but easy to find, so if case that you need to use it, you could get it immediately, this is extremely useful so please just do it, as of now, I've confirmed that only the /data backup was usable, but please try to confirm if other partition backups are working for you.
Certain custom ROMs that can boot up in this device could be flashed through TWRP though, and the links of them are provided here in this thread.
2. GSI, AOSP 9 and custom ROMs
The link for AOSP is provided here: https://forum.xda-developers.com/android/development/redmi-aosp-9-t3922192
The link for GSI is right here: https://forum.xda-developers.com/android/general/tested-gsi-redmi-t3924705
These images/ROMs can be applied with TWRP, just make sure to follow the steps mentioned in these posts to avoid inconvenience, don't forget to take precautions too! I haven't tried them, but so far I believe that these are stable to use.
There are also custom ROMs released for the device but I am lazy to link all of them, they can easily be found by going here: https://forum.xda-developers.com/tags/xiaomi-redmi-go/
Please take note that I haven't tested these custom ROMs yet and I most likely never will, since the stock ROM for the device is already good enough, you can comment here and tell me what custom ROMs are stable so I can link them here for future reference.
3. Current status
My phone is still working, yes! and it's still staying strong, updated to 2.25 using the fastboot method and it is still fast, the only issue currently is that SafetyNet is a lot more secure than before, so it will be impossible to use stuff like Google Pay for now.
I usually decided to lay low and just stay with my LSpeed, Kernel Adiutor and Greenify, all I had to do is to tinker with these apps and my phone just reached into a whole new level! The performance improvement is nice, that I didn't need to use a custom ROM anymore.
4. How to install a OTA update after rooting your device
Due to the changes made by Google on SafetyNet, and the fact that this device will always require you to wipe the device every update, it is pretty much the same, it doesn't matter anymore if you are certified or not, you will still receive an OTA update even if your device is not certified as long as you are using the stock ROM, you only won't be able to install it, and if you want to install the OTA update you must install it by flashing the updated fastboot ROM, I have links for it above, you can try installing the OTA updates yourself through the settings but you will still have to do a factory reset anyway, you have to also unroot also and revert to stock recovery, else the installation will fail, and your device may slower afterwards.
5. Bloatware you can safely remove (NEW!)
So, like I said above, as much as how lightweight the device is, there are still bloatware that you can remove if you really want, but it's only 3 of them:
Mi Video
Mint Browser
Mi Music
The rest such as Mi Share and Mint Launcher are also bloatware, you can remove them but to me they are useful so I didn't, do not remove the "Cleaner" app, if it however says something like "com.CleanMaster", you can try removing it but take caution as your Play Store may be removed along with it too.
Credits to everyone who made the apps/tools that I mentioned here! such as @topjohnwu for the Magisk, and @YasiR Siddiqui for the TWRP, @Paget96 for the awesome LSpeed app, @rovo89 for the Xposed Framework and many more, you guys totally rock!
Hello and thank you for this tutorial. I'd like to ask. Do You know a way where I can unlock the bootloader without permissions or oem unlock? I have a soft-bricked device and for me, there is no way I can get into the OS and manually switch the Oem unlock setting. I've tried different softwares, different adb commands, different region firmwares, still no luck. I can't also get into the the download mode. I mean, yeah, I get the "no command" screen but after pressing power button + up volume button my phone restarts into the fastboot mode and there is no way I can normally boot. It's looping to fastboot mode over and over...
TheAngryGuitarist said:
Hello and thank you for this tutorial. I'd like to ask. Do You know a way where I can unlock the bootloader without permissions or oem unlock? I have a soft-bricked device and for me, there is no way I can get into the OS and manually switch the Oem unlock setting. I've tried different softwares, different adb commands, different region firmwares, still no luck. I can't also get into the the download mode. I mean, yeah, I get the "no command" screen but after pressing power button + up volume button my phone restarts into the fastboot mode and there is no way I can normally boot. It's looping to fastboot mode over and over...
Click to expand...
Click to collapse
Can you please elaborate all of what you've done so far? I will also ask you a few questions.
1. Is your phone usable with the platform tools? I mean with adb and such.
2. Did you try going into recovery and flashing stock ROM through there?
3. Is your phone being detected by "fastboot devices"? The fastboot mode of Redmi Go is its download mode, and i've provided the link for the stock ROM that's usable thru fastboot mode, as well as on how to apply it.
My phone is usable with adb and such, the recovery mode was not working, only the fastboot. I've tried flashing stock rom with the flash tool but I had no success with a bricked soft and a locked bootloader. I've finally fixed it by going into the edl mode by test point method then I flashed the stock rom, and I've fixed my problem this way. I couldn't unlock the bootloader manually from adb or the unlocker tool, but I've did it in the edl way.
TheAngryGuitarist said:
Hello and thank you for this tutorial. I'd like to ask. Do You know a way where I can unlock the bootloader without permissions or oem unlock? I have a soft-bricked device and for me, there is no way I can get into the OS and manually switch the Oem unlock setting. I've tried different softwares, different adb commands, different region firmwares, still no luck. I can't also get into the the download mode. I mean, yeah, I get the "no command" screen but after pressing power button + up volume button my phone restarts into the fastboot mode and there is no way I can normally boot. It's looping to fastboot mode over and over...
Click to expand...
Click to collapse
TheAngryGuitarist said:
My phone is usable with adb and such, the recovery mode was not working, only the fastboot. I've tried flashing stock rom with the flash tool but I had no success with a bricked soft and a locked bootloader. I've finally fixed it by going into the edl mode by test point method then I flashed the stock rom, and I've fixed my problem this way. I couldn't unlock the bootloader manually from adb or the unlocker tool, but I've did it in the edl way.
Click to expand...
Click to collapse
Can you please elaborate the term "edl mode"?
Good job then, usually, before you modify the phone and start doing something crazy out of stock, your number one step is to really unlock the bootloader, and in order to make things more easier, you should allow your OEM to be unlocked through the developer options, after that you can now unlock the bootloader with fastboot.
_XblackshadowX_ said:
Can you please elaborate the term "edl mode"?
Good job then, usually, before you modify the phone and start doing something crazy out of stock, your number one step is to really unlock the bootloader, and in order to make things more easier, you should allow your OEM to be unlocked through the developer options, after that you can now unlock the bootloader with fastboot.
Click to expand...
Click to collapse
Yes, it's the emergency download mode. You use it when there is nothing you can do about the soft of your device. It automatically unlock the bootloader and you can flash the stock rom. Well, my problem was another. I did not tried to flash roms or recoveries with a locked bl. My phone automatically rebooted into the fastboot mode and from there I was not able to start my phone normally. I've tried rebooting fastboot from adb, unlock bl from adb, no success. I had to dissamembly the phone and make a short-circuit to the test points while slowly pushing in the mtp cable with the battery disconnected. Once I saw the Qualcomm driver on device manager I was able to flash the stock rom. You can search if you want to, for the test pins of this device. Btw, thank for your advice, you are really helpful to the community! ?
TheAngryGuitarist said:
Yes, it's the emergency download mode. You use it when there is nothing you can do about the soft of your device. It automatically unlock the bootloader and you can flash the stock rom. Well, my problem was another. I did not tried to flash roms or recoveries with a locked bl. My phone automatically rebooted into the fastboot mode and from there I was not able to start my phone normally. I've tried rebooting fastboot from adb, unlock bl from adb, no success. I had to dissamembly the phone and make a short-circuit to the test points while slowly pushing in the mtp cable with the battery disconnected. Once I saw the Qualcomm driver on device manager I was able to flash the stock rom. You can search if you want to, for the test pins of this device. Btw, thank for your advice, you are really helpful to the community!
Click to expand...
Click to collapse
Woah, you really had to open the phone before doing it, that's an interesting method!
That part where your phone booted into fastboot was kind of scary, any ideas why it booted into fastboot in the first place? It has to be reported if incase, seems like a dangerous bug.
_XblackshadowX_ said:
Woah, you really had to open the phone before doing it, that's an interesting method!
That part where your phone booted into fastboot was kind of scary, any ideas why it booted into fastboot in the first place? It has to be reported if incase, seems like a dangerous bug.
Click to expand...
Click to collapse
I'm not really sure if a malware caused this issue or a failed system update over-night.
TheAngryGuitarist said:
I'm not really sure if a malware caused this issue or a failed system update over-night.
Click to expand...
Click to collapse
I usually had failed system updates numerous times because when i install them, the phone has already been modified by a lot, and that's actually riskier.
That's why i recommend unrooting and putting back the stock recovery before updating first, still works on mine even with "Device is not certified" by Play Store.
The TWRP linked here is for Pie 9, I couldn't get it to boot on my phone, it shows vertical lines.
This is the older version for Oreo 8...
https://forum.xda-developers.com/android/general/twrp-xiaomi-redmi-beta-t3918993
I formatted the phone from TWRP it so it was no longer encrypted.
Mounted the drive from TWRP and installed the "decrypt.zip" from the other TWRP...
https://forum.xda-developers.com/android/development/recovery-twrp-3-3-0-redmi-t3929282
I unlocked the bootloader successfully.
In the setting up ADB step, I don't clearly understand. When I connect my device to the pc, no drivers are installing. And there is no driver named "Android" with an exclamation mark. But my device is getting recognized in "portable devices >> redmi go". I'm very new with adb it would be a lot of help.
I've attached the screenshot of my device manager,
bhattinb said:
I unlocked the bootloader successfully.
In the setting up ADB step, I don't clearly understand. When I connect my device to the pc, no drivers are installing. And there is no driver named "Android" with an exclamation mark. But my device is getting recognized in "portable devices >> redmi go". I'm very new with adb it would be a lot of help.
I've attached the screenshot of my device manager,
Click to expand...
Click to collapse
Did you try turning on USB Debugging on Developer Options? Did you try installing the USB drivers from Google?
_XblackshadowX_ said:
Did you try turning on USB Debugging on Developer Options? Did you try installing the USB drivers from Google?
Click to expand...
Click to collapse
Yeah, I've done everything you told, I also turned the connection mode to PTP also. Somehow it just not showing that android with an exclamation mark.
after that, I even tried to use the 15-second ADB installer. after installing that I tried to flash recovery but that just didn't do anything. After using that flashing command, I had the same stock recovery.
I'm really thankful you took the time to answer my question.
Help!! My device stuck on screen saying your system has been destroyed. What I had done is locked the bootloader using command fastboot oem lock then this happened. Now i can boot device in stock recovery and bootloader too but when i am trying to unlock bootloader it says device is lock and also i am not able to flash anything. Plz help.
I am not able to flash TWRP on my redmi go
How to update the redmi go to the latest version without formatting/Factory Reset should I just follow Fastboot flashing method and if so which files should I just flash. Thank you
bhattinb said:
I unlocked the bootloader successfully.
In the setting up ADB step, I don't clearly understand. When I connect my device to the pc, no drivers are installing. And there is no driver named "Android" with an exclamation mark. But my device is getting recognized in "portable devices >> redmi go". I'm very new with adb it would be a lot of help.
I've attached the screenshot of my device manager,
Click to expand...
Click to collapse
Hi! sorry for the late reply, if this is the case then it's fine, you can just connect the device, open up adb tools, type adb devices and ensure that your USB debugging is on, and the device will connect immediately, at that point all you need is the adb driver for Fastboot
akki_007 said:
Help!! My device stuck on screen saying your system has been destroyed. What I had done is locked the bootloader using command fastboot oem lock then this happened. Now i can boot device in stock recovery and bootloader too but when i am trying to unlock bootloader it says device is lock and also i am not able to flash anything. Plz help.
Click to expand...
Click to collapse
oh no, but why lock your bootloader? you can try using a recovery ROM, you must have a spare SD Card within you, grab a recovery ROM, put it in your sd card then put it into the phone and use it on stock recovery, you should be able to apply it and boot back into the system, please update me
igpraan said:
I am not able to flash TWRP on my redmi go
Click to expand...
Click to collapse
you must have unlocked bootloader if you want to do so.
niknah said:
The TWRP linked here is for Pie 9, I couldn't get it to boot on my phone, it shows vertical lines.
This is the older version for Oreo 8...
https://forum.xda-developers.com/android/general/twrp-xiaomi-redmi-beta-t3918993
I formatted the phone from TWRP it so it was no longer encrypted.
Mounted the drive from TWRP and installed the "decrypt.zip" from the other TWRP...
https://forum.xda-developers.com/android/development/recovery-twrp-3-3-0-redmi-t3929282
Click to expand...
Click to collapse
that's strange, the TWRP I linked isn't giving me any vertical lines