Database Develop

help installing cm - too many different guides, any verified?

hi there,
so i am slightly new at this and have searched for hours and hours trying to find a consistent formula for rooting and installing my g1 to cyanogen mod 4.2 (or latest stable one, thus not cm 5). I seriously stayed up until 1am last night and now i am at work (started at 8) still searching.. I have used google, youtube, and several other cm sites. Basically the problem is there is not one guide and I am not sure if because I followed the CM wiki guide if i can switch because I am having problems with that one. So one question: does anyone know which is the latest and verifiably the best CM 4.latest guide to installing?
I am pretty sure i have rooted the phone because I successfully downgraded to RC29, the old school android OS. However when I try completing this guide: [cant put a URL in but the webpage title is: "G1 CM4.2 installation" and I already completed this wikiguide title: "Full Update Guide - G1/Dream Firmware to CyanogenMod" but it continues into the next page to install cm)
I get freaking stuck. I put all three files on my SD and when I try to push "Alt-A" there is not an option there for it, its not an option on my recovery mode menu. I tried putting the files back there after reformatting several times but still no 'alt-a' so I am stuck on step 5 because there is no option for step 5 on my recovery mode on the above web guide..
Does this mean I did not install something? should I try and install the ota radio, cm update, drc83 zip files separately (like load one on the sd card and install it, then reformat the sd card and then repeat with the other two files?) ? If so what order should I do that in??
Sorry I suck and have not been able to find these answers, there are just a plethora of guides and I am not confident in my modding to start deviating away from the wiki guide in case I brick my beautiful g1..
thanks so much, this has been a huge headache for me.. i literally spent 4 hours yesterday trying to get to this step.. aww...

At Step 5 select "apply any zip from sd" in Recovery.
Select "DRC83_base_defanged.zip" on your SD.
Press Home to confirm flashing.
Then select "update-cm-4.2.x-signed.zip" on your SD to flash CyanogenMod.
After everything is completed reboot your Phone normally.
Edit:
Here is the Link to the Tutorial.

zerocoolriddler said:
At Step 5 select "apply any zip from sd" in Recovery.
.
Click to expand...
Click to collapse
Yup you hit the nail on the head. Sorry I must not have been too clear on what was I was saying earlier. That is exactly the problem, you see I would select that in recovery mode, But "apply any zip from SD" is not there! Did I load some file wrong??
It only gives me:
Android system recovery utility
E: Can't open /cache/recovery/command
Home+Back - reboot system now
ALt+L - toggle log text display
Alt+S - apply sd:update.zip
Alt+W - wipe data/factory reset
could it be this: "E: Can't open /cache/recovery/command" that is the problem? I only found one reference to this message during my internet searches and the guy said it always says that..

So you have CM-Recovery?
Flash Amon_RA`s Recovery, it´s more comfortable to me. I´m using 1.6.2.
For G1: http://forum.xda-developers.com/showthread.php?t=566669
For MT3G(Magic 32b): http://forum.xda-developers.com/showpost.php?p=4029315&postcount=1

Nope. I am also using Flash Amon_RA's recovery.. (v1.6.2)
I loaded it up on the flash drive and also used telnet app to flash it in (wrong terminology? I typed it in the telnet box and hit return and it gave me the # # which I read means I did it right)

Try flashing again using fastboot.
Following Points should be listed:
1. Reboot system now
2. Go to console
3. USB-MS Toggle
4. Backup/Restore
5. Flash zip from sdcard
6. Wipe
7. Partition sdcard
8. Other
9. Power off
Install via Fastboot:
Copy recovery-RA-dream-v1.6.2.img to a location where fastboot can find it.
Boot your G1 into fastboot mode (boot while holding BACK)
Connect your G1 via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your device)
fastboot flash recovery recovery-RA-dream-v1.6.2.img

maybe i get something wrong
but did you boot into the recovery menu already? (press home and power when you turn the phone on)
from there you can choose your task with the trackball nice and easy...
(you r from vienna?)

zerocoolriddler said:
Try flashing again using fastboot.
Following Points should be listed:
1. Reboot system now
2. Go to console
3. USB-MS Toggle
4. Backup/Restore
5. Flash zip from sdcard
6. Wipe
7. Partition sdcard
8. Other
9. Power off
Install via Fastboot:
Copy recovery-RA-dream-v1.6.2.img to a location where fastboot can find it.
Boot your G1 into fastboot mode (boot while holding BACK)
Connect your G1 via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your device)
fastboot flash recovery recovery-RA-dream-v1.6.2.img
Click to expand...
Click to collapse
those points are not listed!
I did not try flashing via fastboot before but rather via terminal app.. Do I need some special software for fastbooting? Amon_RA's post says i need "Requires engineerings SPL!" which I do not have ..
and I now I loaded it via fastboot and I cant get out of it! how do I reboot out of fastboot? Because I can do not know how to "fastboot devices (to make sure that fastboot "sees" your device)
fastboot flash recovery recovery-RA-dream-v1.6.2.img" .. can you explain that in more detail?
skarboy- no i am not from vienna but the USA. and yea I tried to boot from the recovery menu but when i am there it does not show the option of flashing zip from sd (see above)

You did not succesfully apply the recovery image then. Find amon_ra 1.6.2, rename it to recovery.img (make sure that you don't accidentally name it to recovery.img.img because of windows explorer on your computer). Put it on the root of your sdcard. From there, open the telnet app and type "su", then type "flash_image recovery /sdcard/recovery.img" power back on to recovery (home+power), and apply DRC83, CM4.2.15.1, and radio 2.22.23.02.

mejorguille said:
You did not succesfully apply the recovery image then. Find amon_ra 1.6.2, rename it to recovery.img (make sure that you don't accidentally name it to recovery.img.img because of windows explorer on your computer). Put it on the root of your sdcard. From there, open the telnet app and type "su", then type "flash_image recovery /sdcard/recovery.img" power back on to recovery (home+power), and apply DRC83, CM4.2.15.1, and radio 2.22.23.02.
Click to expand...
Click to collapse
oh okay. shoot.. I followed your instructions. do I hit return after typing 'su' in telnet? I did and then typed in the flash image stuff and hit return again. it gave me '##'
i am not rebooting in recovery.. hopefully it will work .
can i have all 4 files on the SD card at the same time? or should i erase it then load the DRC83, CM4.2.15.1, and radio 2.22.23.02 files??
also if i dont get the alt+a option should i just keep trying ??
EDIT: NOPE IT did not work, maybe I should just rename the file recovery, i looked under file properties last time but it didnt say it was hiding the file extension.. I am not quite sure what I am doing wrong.. if someone could show lead me through each individual step by step that would be swell.. of post a video (not outdated).
awwwwwww this is soo painful

austriker27 said:
oh okay. shoot.. I followed your instructions. do I hit return after typing 'su' in telnet? I did and then typed in the flash image stuff and hit return again. it gave me '##'
i am not rebooting in recovery.. hopefully it will work .
can i have all 4 files on the SD card at the same time? or should i erase it then load the DRC83, CM4.2.15.1, and radio 2.22.23.02 files??
also if i dont get the alt+a option should i just keep trying ??
EDIT: NOPE IT did not work, maybe I should just rename the file recovery, i looked under file properties last time but it didnt say it was hiding the file extension.. I am not quite sure what I am doing wrong.. if someone could show lead me through each individual step by step that would be swell.. of post a video (not outdated).
awwwwwww this is soo painful
Click to expand...
Click to collapse
First make sure you have all the files needed (recovery.img, DRC83_base_defrangled, CM4.2.15.1, and radio 2.22.23.02). Tell me if you are missing anything. Load them all up on your sdcard. Make sure that none of the files are in any folders. Next you are going to want to download the "terminal emulator" app from the market (by ZTA). Once downloaded, open the app and type "su" (enter). After that, type "flash_image recovery /sdcard/recovery.zip"(enter). Type "reboot recovery" (enter). If you do not see this image below, then something went wrong.
{
"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, that image shows 1.7 but you are going to want to install 1.6.2. v1.7 is for CM5-based roms)

okay, so after a much needed break of watching the US draw with England (world cup!!) i am back..
yes I have all of those files but my radio file is different (older?).. It is "ota-radio-2_22_19_26I".. should I have the radio file you mentioned? can you link it to me?
EDIT: Okay I found that file that you referenced and downloaded it. I will throw it in my sd card instead of the 26I because it sounds like it is a better radio flash..
also the 'radio', update cm, and DRC83 files are really zipped folders (.zip) that I have not extracted. Do I need to extract the contents into a folder and put the files from these extracted folders on the SD card root (so that there are ZERO folders on the sd? (no one mentioned this)
and so I use terminal emulator as opposed to telnet?? I was using telnet before because the CM wikiguide says so..

You don't need to unzip. They're zipped to flash via Recovery.
Flash the Recovery via Fastboot.
PS: It's called Terminal, not Telnet. ;-)

mejorguille said:
First make sure you have all the files needed (recovery.img, DRC83_base_defrangled, CM4.2.15.1, and radio 2.22.23.02). Tell me if you are missing anything. Load them all up on your sdcard. Make sure that none of the files are in any folders. Next you are going to want to download the "terminal emulator" app from the market (by ZTA). Once downloaded, open the app and type "su" (enter). After that, type "flash_image recovery /sdcard/recovery.zip"(enter). Type "reboot recovery" (enter). If you do not see this image below, then something went wrong.
(note, that image shows 1.7 but you are going to want to install 1.6.2. v1.7 is for CM5-based roms)
Click to expand...
Click to collapse
okay so I tried all that.. and freaking a! awwwwww no success it just gave me the old screen like before
when I typed in "su" it said permission denied so I think I have to go back and do something that I missed. I cant keep track of how many times I have done everything, then erased then tried again.. I wish someone would be specific and just walk me through this without skipping a single detail..

zerocoolriddler said:
You don't need to unzip. They're zipped to flash via Recovery.
Flash the Recovery via Fastboot.
PS: It's called Terminal, not Telnet. ;-)
Click to expand...
Click to collapse
this is exactly what i am talking about everyone is saying something different:
here is the CM site telling me to use telnet:
Open Android Telnet Client and type (include all spaces)
flash_image recovery /sdcard/recovery.img [enter]
If completed correctly you will simply see # # appear on your screen beneath the line you've just typed. If you get the "permission denied" message, type "su" (without quotes), press enter and repeat the previous step. If you get a file not found message, you may need to remount your sd card or make sure you typed the file name correctly.
Press Home key and proceed to next step

austriker27 said:
okay, so after a much needed break of watching the US draw with England (world cup!!) i am back..
yes I have all of those files but my radio file is different (older?).. It is "ota-radio-2_22_19_26I".. should I have the radio file you mentioned? can you link it to me?
EDIT: Okay I found that file that you referenced and downloaded it. I will throw it in my sd card instead of the 26I because it sounds like it is a better radio flash..
also the 'radio', update cm, and DRC83 files are really zipped folders (.zip) that I have not extracted. Do I need to extract the contents into a folder and put the files from these extracted folders on the SD card root (so that there are ZERO folders on the sd? (no one mentioned this)
and so I use terminal emulator as opposed to telnet?? I was using telnet before because the CM wikiguide says so..
Click to expand...
Click to collapse
the 2.22.23.02 radio is newer and its supposed to have better reception and less battery usage as compared to the .26I radio but the difference should be minimal. Everything is supposed to be in a zipped folder exept for the recovery image. Terminal is similar to telnet in that you can put in commands but it works a little different. It is what I usually use to flash recovery's, etc, so since telnet was not working for you I though terminal might make a difference.
Again, open terminal and type:
Code:
su(enter)
flash_image recovery /sdcard/recovery.img(enter)
reboot recovery(enter)
Tell me if this works.
Edit:look at my next post

austriker27 said:
this is exactly what i am talking about everyone is saying something different:
here is the CM site telling me to use telnet:
Open Android Telnet Client and type (include all spaces)
flash_image recovery /sdcard/recovery.img [enter]
If completed correctly you will simply see # # appear on your screen beneath the line you've just typed. If you get the "permission denied" message, type "su" (without quotes), press enter and repeat the previous step. If you get a file not found message, you may need to remount your sd card or make sure you typed the file name correctly.
Press Home key and proceed to next step
Click to expand...
Click to collapse
The "su" command signifies root access. If it says permission denied, then that means that you are not rooted or you skipped a step.
CYANOGEN WIKI said:
Rooting the phone
You need to have root (or 'admin') access to the phone so that you can install whatever software you want and not just what your provider gives you. This is not the same as unlocking your phone.
Finish booting up your phone, and sign-in to your Google account.
If you don't have access to a 3G network, then follow the G1 logon to google via wifi guide to sign-in via wifi. The original guide to do this is out of date.
You could try and add your networks provider's APN. To do this press Menu key -> APN Settings, press Menu again -> Add APN and enter 4 things: Name, MCC (Mobile Country Code), MNC Mobile Network Code and APN - all this info should be available here: http://en.wikipedia.org/wiki/Mobile_network_code and on your network provider's site. The image you booted with might also have the extensive APN list. If so, and you can't get a data connection, then you might try the wifi guide.
Once you're at the Home screen, open the keyboard, and press the Enter (Return) button twice.
Type
telnetd [enter]
Typing will bring up the Contacts screen, but you can just ignore that.
There will be no indication to let you know you did it right. Just continue on to the next step.
If you get an error when trying to connect (step 5), try pressing Enter twice and type "telnetd" and press Enter again
Open the Android Market, and install "Telnet" by ClockworkMod (Formerly by Koushik Dutta)
Open Android Telnet Client, enter "localhost" in the large text box and press connect. (You may have to enter "23" in the smaller text box on the right)
Click to expand...
Click to collapse
Do those steps again.

okay so I am in the telnet client and have entered localhost and 23 and hit return. so now i am in a black screen. i typed in what cm wikiguide told me and it gave me :
## (good sign!)
now do I turn off the phone and go into recovery mode or this where I am missing a step??
Sorry I am so ornery (wow and i can spell) there are just a number of things frustrating me.. besides me knowing this should only take like 2 hours at the most and knowing I keep messing up some mundane detail or something.. Also I am doing it in windows on my macbook and the wireless keeps disconnecting. Also I would take photos of the screens to show you but I do not have any photo software on the windows partition of my laptop (i mostly use mac os x) so I cannot... and i am very tired from working 6 days a week (and only getting 6 hours of sleep last night due to this issue) and frustrated from this whole fiasco.. And I have a headache.. yup call me a whiner if ya want but i am just trying to explain why i am kinda mad...

HALELUJAH! it worked and the android system recovery looks like your image mejor!!!!!!!! hopefully this works, i will let you know.. thanks soo much! i have no idea what i did differently

YESSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
wow so that wasnt a giant headache, although now i pretty have the process memorized and have learned tons in the process. I think I may have the longest time to root a g1 record so far of any human haha... Lets see I worked on it yesterday from 8pm-1am while kind of watching world cup. This morning for about 2 hours from 9-1130 at my job. And this afternoon for about 2 hours..So like 9 hours give or take an hour of two.. NEW RECORD!! haha
THANKS SO MUCH for you help guys I love you. Especially mejor because he/she lead me down the finishing stretch... Now to install apps2sd (after my class 6 card comes) and take a nap

[Tutorial][How to] Unlock Bootloader and Install Custom Recovery and Root

Hello,
I know there are some tutorials for this already but I felt like they missed out a few steps that might not be obvious to some who are new to this.
This tutorial applies to all of Android One Device (Micromax Canvas A1, Karbonn Sparkle V Blue, Spice Mi-498 Dream Uno).
Unlocking bootloader will lead to formating of your phone. The stuff inside your sd card is safe but all your apps and their data will be deleted.
Unlocking bootloader:
1. Download Universal ADB Driver installer from here.
2. Connect your phone and run the Universal ADB Driver installer. Click 'Install' button and a warning should pop up. Just click "Install anyway" and it should look like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3. Download ADT Bundle from here for Win-32 Bit and from here for 64-Bit . If you are unsure which version of windows you have just download the 32-Bit one.
4. Extract the zip file in your C:\ drive like this (You can install it wherever you like but this tutorials assumes this location for simplicity). Add adb and fastboot to system path by following this tutorial . This will allow you to run adb and fastboot commands from any location on cmdline.
3. Switch off your phone. Now, Press POWER BUTTON + VOLUME UP button for about 5 seconds. A menu should appear. Note: VOLUME UP allows to navigate the menu (move down the menu). Press VOLUME DOWN button for selecting/choosing fastboot. On your phone, it should say something like
Code:
=> FASTBOOT MODE...
Connect your phone to the computer if it wasn't already.
4. (Assuming Win 7) Click on start menu > Search for 'Command Prompt' and right click and select 'Run as Administrator'.
5. On command prompt, Type:
Code:
fastboot devices
If it shows something, that means we can proceed to unlocking bootloader. Otherwise, it means that the driver was not installed correctly.
6. Now, Type the following commands:
Code:
fastboot oem unlock
fastboot format userdata
fastboot reboot
Now, your bootloader is unlocked.
Install a custom recovery.
1. Download custom recovery from this thread.
2. Place the download file, 'recovery.img' file in C:\ drive. (Again, you can place it anywhere but this tutorial assumes this path).
3. Run the following command (Assuming already in fastboot mode again. If not, follow the above steps to go to fastboot mode). :
Code:
fastboot flash recovery c:\recovery.img
After doing so, it should look like this:
4. Reboot your phone and you are done by typing:
Code:
fastboot reboot
Now, you have installed CWM custom recovery. On to installing root.
Rooting your phone:
1. After installing custom recovery, download Super-Su .zip file.
2. Place the .zip file on your sd-card. If your computer doesn't show your phone as MTP device, download the drivers from here.
3. Boot into recovery, by pressing POWER OFF + Volume UP button for 5 secs and choosing Recovery by pressing Volume Down (NOTE: Use Volume UP for menu navigation)
4. After booting into recovery, Choose 'Install Zip'. You can use Volume UP and Volume Down for navigating here and Power Off button for selecting a menu item.
5. Now, select 'choose zip from /external_sd' and not '/sdcard'
6. Select the Super-Su zip file you placed on your sd card and install it.
Now, Reboot your phone. It might say something like 'su may have been removed' but ignore and press 'No'.
Tutorial Complete
Let me know if there are any errors in this Tutorial.

Hi, thanks for the tutorial. Can you explain the necessity for using "fastboot format userdata" given "oem unlock" command in addition to unlocking the bootloader clears user data.

littleromeo said:
Hi, thanks for the tutorial. Can you explain the necessity for using "fastboot format userdata" given "oem unlock" command in addition to unlocking the bootloader clears user data.
Click to expand...
Click to collapse
Someone in this thread reported that they got stuck on the recovery, meaning the phone boot normally.
The port maker for recovery for our phone mentioned formatting userdata command in his post, so I did the same. I didn't want newbies to experience any trouble.

nice guide ..
but I guess "add adb and fastboot to system path " shall be made optional .. this will make guide little simpler and shorter ..

Hey
Can anybody please insure any android device that has been successfully rooted by this method ? Also is waiting for towelroot worth it ??

tanuj123 said:
Can anybody please insure any android device that has been successfully rooted by this method ? Also is waiting for towelroot worth it ??
Click to expand...
Click to collapse
I have used this method myself, but I am also the OP so.... :victory:

Iam in a weird situation , I did flash many times before but I dont know how it made my device like this ... THE PROBLEM IS WITH DRIVERS and also SDcard
First I unlocked my bootloader then flashed cm11 on it ( Which was on lollipop official) and I forgot to download gapps so in connected my phone to pc only to find my computer doesnt recognise my phone it make sound but nothing shows up I tried clicking MTP again and again but nothing happens , WHEN I TRIED ADB it shows no devices in the list , I took out the sd card to copy files manually and the sd card says its write protected ..... GUYS HELP @stirredo

What are you using to read your SD card on your computer?
If you are using SD card adapter, make the sure write lock is turned off.

Man thankyou but After installing the driver you gave my phone gets detected by pc but only when I turn on usb debugging @stirredo
Sent from my Xperia P using XDA Free mobile app

Kaushik124 said:
Man thankyou but After installing the driver you gave my phone gets detected by pc but only when I turn on usb debugging
Sent from my Xperia P using XDA Free mobile app
Click to expand...
Click to collapse
That is the same issue faced by me .

Saurabh K said:
That is the same issue faced by me .
Click to expand...
Click to collapse
Did you find any solution
Sent from my Xperia P using XDA Free mobile app

Not yet, but trying....
Sent from my Sparkle V

thanks for this awesome tutuorial.... But i have a problem in unlocking the tutorial
The problem is that how can i unlock my bootloader when oem unlocking is turned off...
Recently i tried to flash CM12.1 on my YU YUNIQUE YU4711 without turning on OEM unlocking and now I am stuck at the Fastboot mode so i cant start up my phone.... So i wanted to know that how i can unlock the bootloader when OEM unlocking is turned off..
PS- I cant even go to recovery moded
thanks in advance

Format Userdata
stirredo said:
Someone in this thread reported that they got stuck on the recovery, meaning the phone boot normally.
The port maker for recovery for our phone mentioned formatting userdata command in his post, so I did the same. I didn't want newbies to experience any trouble.
Click to expand...
Click to collapse
I did got stuck at bootloader when I dedn't format Userdata. Thanx for the tip.
---------- Post added at 03:01 PM ---------- Previous post was at 02:53 PM ----------
When I opened SuperSu after installing SuperSu through recovery, it says "There is no SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device!"
What do I do now?

stirredo said:
Hello,
I know there are some tutorials for this already but I felt like they missed out a few steps that might not be obvious to some who are new to this.
This tutorial applies to all of Android One Device (Micromax Canvas A1, Karbonn Sparkle V Blue, Spice Mi-498 Dream Uno).
Unlocking bootloader will lead to formating of your phone. The stuff inside your sd card is safe but all your apps and their data will be deleted.
Unlocking bootloader:
1. Download Universal ADB Driver installer from here.
2. Connect your phone and run the Universal ADB Driver installer. Click 'Install' button and a warning should pop up. Just click "Install anyway" and it should look like this:
3. Download ADT Bundle from here for Win-32 Bit and from here for 64-Bit . If you are unsure which version of windows you have just download the 32-Bit one.
4. Extract the zip file in your C:\ drive like this (You can install it wherever you like but this tutorials assumes this location for simplicity). Add adb and fastboot to system path by following this tutorial . This will allow you to run adb and fastboot commands from any location on cmdline.
3. Switch off your phone. Now, Press POWER BUTTON + VOLUME UP button for about 5 seconds. A menu should appear. Note: VOLUME UP allows to navigate the menu (move down the menu). Press VOLUME DOWN button for selecting/choosing fastboot. On your phone, it should say something like
Code:
=> FASTBOOT MODE...
Connect your phone to the computer if it wasn't already.
4. (Assuming Win 7) Click on start menu > Search for 'Command Prompt' and right click and select 'Run as Administrator'.
5. On command prompt, Type:
Code:
fastboot devices
If it shows something, that means we can proceed to unlocking bootloader. Otherwise, it means that the driver was not installed correctly.
6. Now, Type the following commands:
Code:
fastboot oem unlock
fastboot format userdata
fastboot reboot
Now, your bootloader is unlocked.
Install a custom recovery.
1. Download custom recovery from this thread.
2. Place the download file, 'recovery.img' file in C:\ drive. (Again, you can place it anywhere but this tutorial assumes this path).
3. Run the following command (Assuming already in fastboot mode again. If not, follow the above steps to go to fastboot mode). :
Code:
fastboot flash recovery c:\recovery.img
After doing so, it should look like this:
4. Reboot your phone and you are done by typing:
Code:
fastboot reboot
Now, you have installed CWM custom recovery. On to installing root.
Rooting your phone:
1. After installing custom recovery, download Super-Su .zip file.
2. Place the .zip file on your sd-card. If your computer doesn't show your phone as MTP device, download the drivers from here.
3. Boot into recovery, by pressing POWER OFF + Volume UP button for 5 secs and choosing Recovery by pressing Volume Down (NOTE: Use Volume UP for menu navigation)
4. After booting into recovery, Choose 'Install Zip'. You can use Volume UP and Volume Down for navigating here and Power Off button for selecting a menu item.
5. Now, select 'choose zip from /external_sd' and not '/sdcard'
6. Select the Super-Su zip file you placed on your sd card and install it.
Now, Reboot your phone. It might say something like 'su may have been removed' but ignore and press 'No'.
Tutorial Complete
Let me know if there are any errors in this Tutorial.
Click to expand...
Click to collapse
bro, my bootloader is already unlocked, so i was using the flash recovery command directly, and i was unable to flash recovery, everytime i go into recovery it opens stock recovery, what should i do to flash recovery now, no method is working, is it compulsary to unlock bootloader every time flashing recovery, mine is already unlocked, but cant able to flash recovery, please help ,its urgent.

I am on a custom ROM right now( Resurrection ) and have unlocked the bootloader
Can I relock the bootloader using Androidone tool
Will it format userdata?
Can I keep the Custom ROM after relocking?
Please help
Device-Mi-498

hi my device is not boot after restart.always need to run fastboot continue. have you any idea how to resolved ?

my phone showing device not found error in ADB driver installer. actually phone is unable to start, it is continuously looping in start logo

is the fastboot format userdata command required? what will happen if i fail to issue the fastboot format command following fastboot oem unlock command?

hello i want the unlocked bootloader file for my Micromax e313 please send me the link to get it please help me

[GUIDE] Gain Root Access v3 (3 Methods!)

Hello people,
This is for Mi Note Pro (leo)
Disclaimer:
I'm not responsible for any devices being bricked, your device blowing up or world war 3 starting! You are doing this at your own risk.
Click to expand...
Click to collapse
A lot of people ask how to gain root on the Mi Note Pro without actually searching the posts so I decided to make a quick tutorial on how to do it. This is the way I have done it and I have found it to be the easiest way!
1st Method (THE EASIEST AND SAFEST!)
1. Go to http://en.miui.com/download-273.html and download the Developer ROM
{
"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"
}
2. If you have downloaded the file through your phone it will be in the Download folder, if not plug your phone into the PC and move the .zip file over to your device.
3. Open Updater app, tap on 3 dots to open the menu and tap on Choose update package
4. Navigate to where you have put in the zip file and click on it and let the phone update. (This will wipe all your data apart from pictures etc.)
5. Once it has loaded go through the setup. Open Security app > Permissions > Root Access.. There you are all done
Make sure you open an app that requires root access first before going to Security app as it will not show up on there.
2nd Method (Advanced Users!)(Temporary TWRP Recovery)
Requirements:
fastboot driver (Link attached)
twrp.img - https://mega.nz/#!nR0jHZqL!2cksl ... 5H76ut8UVtnu97HHAEo
supersu - https://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip
common sense
mi note pro!
1. First of all download all the things you need. Which are fastboot driver, twrp and supersu. All links are above ^ Copy SuperSu over to your device and keep other files on your PC
2. Power off your device and turn it back on by holding Power button and Volume Down at the same time. This will get you into fastboot menu.
3. Woohoo great now what you will have to do is plug your phone to your PC using a usb cable.
4. Open up the Command Promt and navigate to the location of your fastboot driver. Mine is C:/adb so I would type cd C:/adb in the command promt
5. Now type in fastboot devices just to make sure that your device is listed correctly.
6. Extract the TWRP zip so you have just the .img file. Place it inside same folder as fastboot. I tend to rename it to twrp.img (makes lifes easier)
7. Type fastboot boot twrp.img
8. Now your phone should boot into TWRP!! Go to install and flash the SuperSU zip.
9. Reboot and you are all rooted with Stock Recovery and Stable ROM!
3rd Method (Advanced Users!)(Permanent TWRP Recovery)
Requirements:
fastboot driver
twrp.img - https://mega.nz/#!nR0jHZqL!2ckslQxV-ODWnswRYpfDCp2M5H76ut8UVtnu97HHAEo
supersu - https://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip
common sense
mi note pro!
1. First of all download all the things you need. Which are fastboot driver, twrp and supersu. All links are above ^ Copy SuperSu over to your device and keep other files on your PC
2. Power off your device and turn it back on by holding Power button and Volume Down at the same time. This will get you into fastboot menu.
3.Woohoo great now what you will have to do is plug your phone to your PC using a usb cable.
4. Open up the Command Promt and navigate to the location of your fastboot driver. Mine is C:/adb so I would type cd C:/adb in the command promt
5. Now type in fastboot devices just to make sure that your device is listed correctly.
6. Extract the TWRP zip so you have just the .img file. Place it inside same folder as fastboot. I tend to rename it to twrp.img (makes lifes easier)
7. Type fastboot flash recovery twrp.img
8. Now your phone should boot into TWRP!! Go to install and flash the SuperSU zip.
9. Reboot and you are all rooted with TWRP recovery, the only problem is that your OTA updates will break. You can flash them manually, when Updater downloads an update go into TWRP>Install and navigate to downloaded_rom folder
In case you need to go back to stock Recovery because you have flashed TWRP Permanently please follow instructions on this thread.http://en.miui.com/thread-124319-1-1.html

GREAT! EASY!
Need to wipe cache or data?

Nope no need to do that

nice thanks for the advice

I followed ur step but no show root access...
Did I miss anything?

Absent6775 said:
I followed ur step but no show root access...
Did I miss anything?
Click to expand...
Click to collapse
Yea step 5

Absent6775 said:
I followed ur step but no show root access...
Did I miss anything?
Click to expand...
Click to collapse
Well their Root Access works a bit different to SuperSU instead of popping up with a box promting you to give root access what you have to do is open the app the requires root access, do an action that needs root access then you go to Security > Premissions > Root Access and you have to grant it then.

Is only way to root to do a full wipe?
Can we still do normal updates after installing this developer rom?

Yup you get newest weekly updates and they work perfectly fine! I'm on 5.7.2 currently

Updated.

Is it equally safe to flash the latest 1.0.0 supersu from chainfire? Is there any compatibility constraints? or are all version compatible with all devices? thanks for shedding some light into this

Can you use Flashify and install twrp and supersu or is supersu not needed using method 1? ?
sent from mobile thingy

Super su is not needed using method 1 as they use their own root manager.

Kahun said:
Super su is not needed using method 1 as they use their own root manager.
Click to expand...
Click to collapse
How to unroot in method 2 ?
Incase I want to sell this phone so the warranty still valid to the new owner.

deddo86 said:
How to unroot in method 2 ?
Incase I want to sell this phone so the warranty still valid to the new owner.
Click to expand...
Click to collapse
Just flash stable ROM.

Added a permanent recovery method but "might" break OTA

Problem with Method 1
Hi People /Mr. Kahun ,
I'm absolutely new but i would like to root my :
Mi Note Pro
Android 5.0.2.
MIUI 66.55.44.00
because some original programs make me creasy . I tried method 1. I followed your steps, i downloaded different DEVELOPER Rom (5.9.10 and 5.9.17) , but i had always with the step 4 the message GETTING INFO ..... and this is the end of the process .....
PLEASE PLEASE tell ma what can i do to root the device .
Thank you in advance

Try installing HappyMIUI rom from the android development section.

i don't know how to install .....i will try method 2.
thank you Kahun!

where can i find the fastboot driver (Link is NOT attached)

[Q] need help to get my phone working again

hey guys.
My M7 is stuck in the bootloop. I tried to install a new rom like 2 years ago and it didnt worked out, but i already had a new phone, so i didnt care too much. now id like to reactivate my old m7 but dont know how.
here is a link to a picture of my fastboot
imgur.com/tzQe7Xi
Im running Windows 10 on my computer
thanks in advance

zuppiger said:
hey guys.
My M7 is stuck in the bootloop. I tried to install a new rom like 2 years ago and it didnt worked out, but i already had a new phone, so i didnt care too much. now id like to reactivate my old m7 but dont know how.
here is a link to a picture of my fastboot
imgur.com/tzQe7Xi
Im running Windows 10 on my computer
thanks in advance
Click to expand...
Click to collapse
Boot into fastboot mode and install the latest version of TWRP, which is 2.8.7.0. You can download it from the TWRP official website.
Code:
fastboot flash recovery recovery-file-name.img
Boot into recovery and connect your phone to the PC.
Download any ROM from the forum, transfer it to the phone and flash it. Don`t since we don`t know anything about your previous ROM wipe cache, dalvik, data and system before flashing your chosen ROM.
Since you`re S-On, extract the boot.img file from the ROM zip and flash it manually in fastboot mode
Code:
fastboot flash boot boot.img
Reboot phone and enjoy.

proone said:
Boot into fastboot mode and install the latest version of TWRP, which is 2.8.7.0. You can download it from the TWRP official website.
Code:
fastboot flash recovery recovery-file-name.img
Boot into recovery and connect your phone to the PC.
Download any ROM from the forum, transfer it to the phone and flash it. Don`t since we don`t know anything about your previous ROM wipe cache, dalvik, data and system before flashing your chosen ROM.
Since you`re S-On, extract the boot.img file from the ROM zip and flash it manually in fastboot mode
Code:
fastboot flash boot boot.img
Reboot phone and enjoy.
Click to expand...
Click to collapse
No need to extract anything. S-on doesn't matter for kernel flashing on this phone. So, flash ROM.zip and enjoy

proone said:
Boot into fastboot mode and install the latest version of TWRP, which is 2.8.7.0. You can download it from the TWRP official website.
Code:
fastboot flash recovery recovery-file-name.img
Click to expand...
Click to collapse
Code:
fastboot flash recovery recovery-file-name.img
fastboot erase cache
fastboot reboot-bootloader
Always erase the cache and reboot the bootloader after flashing a recovery to avoid problems booting the recovery.
Download any ROM from the forum
Click to expand...
Click to collapse
"any ROM" from the forum won't work on his phone. For example, his actual firmware is way to old to run roms based on Sense + Lollipop. With this firmware version (2.24.401.8), he is limited to JellyBean or Kitkat Roms.
Since you`re S-On, extract the boot.img file from the ROM zip and flash it manually in fastboot mode
Code:
fastboot flash boot boot.img
Reboot phone and enjoy.
Click to expand...
Click to collapse
Won't hurt but not needed on the M7 (unlike some other HTC phones). The kernel partition isn't secured and is flashed with the rom from twrp.
@zuppiger
If you want the phone back to stock and be able to intall ota updates (or if you want to install a custom lollipop + sense rom), flash this rom using twrp recovery. Select "yes" for stock recovery and stock radio, select "no" to root. then reboot the phone to the OS, install all the ota updates (a lot) until your version is 7.19.401.30. Then you can use the phone like this or you'll be ready to flash a lollipop custom rom. Otherwise you can go like suggested above but with older (JB or KitKat) Sense rom or any CM/AOSP roms.

Thanks guys.
but i think i might need some more help.
i downloaded the sdk manager to install TWRP, but when i try to write "adb reboot bootloader" it says "is not recognized as an internal or external command, operable program or batch file" (not entirly sure if this is the correct translation, in german it says the command is either wrong or could not be found)
i think it could be because of some driver issues.
any advice??

zuppiger said:
Thanks guys.
but i think i might need some more help.
i downloaded the sdk manager to install TWRP, but when i try to write "adb reboot bootloader" it says "is not recognized as an internal or external command, operable program or batch file" (not entirly sure if this is the correct translation, in german it says the command is either wrong or could not be found)
i think it could be because of some driver issues.
any advice??
Click to expand...
Click to collapse
Download the android sdk tools:
https://developer.android.com/sdk/index.html#Other
Make sure you have the latest htc drivers installed:
http://www.mediafire.com/download/2lyl151pt5pah2v
Make sure you don't have HTC Sync installed on your computer, if yes, uninstall it since it will interfere with fastboot/adb commands
To use adb or fastboot commands, open a command window from the same folder where adb.exe and fastboot.exe are located on your computer (C::\Programs\Android SDK Tools\platform-tools). To start a command window from this folder, hold your left "shift" key and right click a blank space in that folder, then in the contextual menu, select "open a command window here".
Don't forget that adb commands can only works when the phone is booted in the OS with "USB debugging" turned on from the developer option menu or from a custom recovery. Fastboot commands only works from the bootloader (in the fastboot menu).
{
"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"
}

alray said:
Download the android sdk tools:
https://developer.android.com/sdk/index.html#Other
Make sure you have the latest htc drivers installed:
http://www.mediafire.com/download/2lyl151pt5pah2v
Make sure you don't have HTC Sync installed on your computer, if yes, uninstall it since it will interfere with fastboot/adb commands
To use adb or fastboot commands, open a command window from the same folder where adb.exe and fastboot.exe are located on your computer (C::\Programs\Android SDK Tools\platform-tools). To start a command window from this folder, hold your left "shift" key and right click a blank space in that folder, then in the contextual menu, select "open a command window here".
Don't forget that adb commands can only when the phone is booted in the OS with "USB debugging" turned on from the developer option menu or from a custom recovery. Fastboot commands only works from the bootloader (in the fastboot menu).
Click to expand...
Click to collapse
Thanks. I installed everything like explained.
It worked better this time, but now I get "waiting for device".
On the phone itself it says "FASTBOOT USB"

zuppiger said:
but now I get "waiting for device".
Click to expand...
Click to collapse
When using what command?

alray said:
When using what command?
Click to expand...
Click to collapse
"fastboot flash recovery c:\twrp.img"

zuppiger said:
"fastboot flash recovery c:\twrp.img"
Click to expand...
Click to collapse
what is the output of "fastboot devices" ?

alray said:
what is the output of "fastboot devices" ?
Click to expand...
Click to collapse
Nothing.
I made the command again in the platform-tools folder

Anyone some more help? :good:

zuppiger said:
Anyone some more help? :good:
Click to expand...
Click to collapse
Well without any connectivity to the phone there is nothing we can do unfortunately. Might worth to try on another computer. Otherwise if you are 100% sure that the problem isn't the usb cable, the drivers or the computer then the phone usb port might be broken. This can be replaced (probably the "easiest" part to replace on that phone), you'll need to open the cover and replace that small usb/front mic board.
But the fact that your phone says FASTBOOT USB when in bootloader makes me believe its more a driver/computer problem since it would only says FASTBOOT if there were no connection detected...

thanks a lot for your help. I don't think I will get it working again anytime soon.
But i will look for a way

How To Guide [GUIDE] Beginner's guide on how to root Redmi Note 10 Pro (sweet) without TWRP

I decided to make this guide since I didn't see a guide thread which explains how to root the phone.
DISCLAIMER: I am not responsible for ANY damage that occurs to the phone, you getting fired because the alarm app failed or the world getting nuked, etc...
Requirements:
-A unlocked bootloader (if you don't know how to unlock it, search "How to unlock bootloader Xiaomi"
-boot.img extracted from your phone's fastboot rom (MAKE SURE YOU DOWNLOADED THE EXACT SAME ROM THAT YOUR PHONE HAS (Check "About phone" in settings. Make sure that the version AND the code (RK(something)XM) match, if you have MIUI).
xiaomifirmwareupdater site contains unmodified MIUI roms for your device.
-If you have a custom rom, extract the rom's zip and get the boot.img from there.
-ADB and Fastboot drivers installed on phone and PC
-SDK Platform tools downloaded from official android website. Extract the downloaded zip to desktop and rename it to platform_tools
-A Computer
-Basic understanding of CMD, ADB and Fastboot commands.
-The phone
If you see an error, scroll down to the troubleshooting section.
Steps:
(on the pc)
-Copy the boot.img file to the phone's downloads folder
(in the phone)
-Download the magisk app from the official github site
-Install the app, then open it.
-In the app, select install on the magisk card
{
"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"
}
-Select patch a file, then find and select boot.img.
-Tap "let's go".
(on the pc)
-Connect your phone to your PC and copy magisk_patched.img from the phone (should be in downloads folder) back to the pc.
-Rename the file to magisk.img, then move it to the platform_tools folder which contains fastboot.exe.
-Now reboot the phone and when the screen goes fully black, hold volume down button until you see "fastboot".
-Your phone should now be in fastboot mode. Connect the phone to the pc.
-Press win+r, then type cmd
-Type cd desktop
-Type cd platform_tools
-Type fastboot devices (if you see nothing, make sure you have adb and fastboot drivers, that the phone is connected and is in fastboot mode.)
-Type this carefully: fastboot flash boot magisk.img
-Done! Now reboot the phone by typing: fastboot reboot
-If you did everything correctly, the magisk app should say that it is installed.
TROUBLESHOOTING:
Q:Fastboot says it couldn't find "magisk.img" or CMD says fastboot doesn't exist
A: Make sure that cmd says that its in C:\Users\(name)\Desktop\platform_tools and that magisk.img is also in there.
Q: Phone is in bootloop
A: Hold volume down button until phone is in fastboot and flash stock boot.img with fastboot flash boot.img. (You will not have root access) If the phone is still somehow in a bootloop, execute the flash_all_except_storage.bat script by double clicking it (found in the sweet_(region)_images folder you extracted from the full fastboot rom .tgz file).

usernamenotrequired said:
I decided to make this guide since I didn't see a guide thread which explains how to root the phone.
DISCLAIMER: I am not responsible for ANY damage that occurs to the phone, you getting fired because the alarm app failed or the world getting nuked, etc...
Requirements:
-A unlocked bootloader
-boot.img extracted from your phone's fastboot rom (MAKE SURE YOU DOWNLOADED THE EXACT SAME ROM THAT YOUR PHONE HAS (Check "About phone" in settings. Make sure that the version AND the code (RK(something)XM) match, if you have MIUI).
xiaomifirmwareupdater site contains unmodified MIUI roms for your device.
-If you have a custom rom, extract the rom's zip and get the boot.img from there.
-ADB and Fastboot drivers installed on phone and PC
-SDK Platform tools downloaded from official android website. Extract the downloaded zip to desktop and rename it to platform_tools
-A Computer
-Basic understanding of CMD, ADB and Fastboot commands.
-The phone
If you see an error, scroll down to the troubleshooting section.
Steps:
(on the pc)
-Copy the boot.img file to the phone's downloads folder
(in the phone)
-Download the magisk app from the official github site
-Install the app, then open it.
-In the app, select install on the magisk card
View attachment 5474787
-Select patch a file, then find and select boot.img.
-Tap "let's go".
View attachment 5474793
(on the pc)
-Connect your phone to your PC and copy magisk_patched.img from the phone (should be in downloads folder) back to the pc.
-Rename the file to magisk.img, then move it to the platform_tools folder which contains fastboot.exe.
-Now reboot the phone and when the screen goes fully black, hold volume down button until you see "fastboot".
View attachment 5474801
-Your phone should now be in fastboot mode. Connect the phone to the pc.
-Press win+r, then type cmd
-Type cd desktop
-Type cd platform_tools
-Type fastboot devices (if you see nothing, make sure you have adb and fastboot drivers, that the phone is connected and is in fastboot mode.)
-Type this carefully: fastboot flash boot magisk.img
-Done! Now reboot the phone by typing: fastboot reboot
-If you did everything correctly, the magisk app should say that it is installed.
TROUBLESHOOTING:
Q:Fastboot says it couldn't find "magisk.img" or CMD says fastboot doesn't exist
A: Make sure that cmd says that its in C:\Users\(name)\Desktop\platform_tools and that magisk.img is also in there.
Qhone is in bootloop
A: Hold volume down button until phone is in fastboot and flash stock boot.img with fastboot flash boot.img. (You will not have root access) If the phone is still somehow in a bootloop, execute the flash_all_except_storage.bat script by double clicking it (found in the sweet_(region)_images folder you extracted from the full fastboot rom .tgz file).
Click to expand...
Click to collapse
Very good but easier with unlocked bootloader and flashing twrp via adb flash recovery "name of twrp file". Afterwards you can flash directly magisk (I prefer 23 canary debug apk) to root.

if i may add to the troubleshooting: if it says magisk.img isn't found, just type this (after confirming connection with fastboot devices command:
fastboot flash boot
then drag and drop the patched magisk file onto the cmd window/line where you typed the command above. worked for me.

Tanks you

For beginners, "assuming bootloader is unlocked if not click here" should be mentioned.

hello, I've been trying to login to my account since this morning. after half a day I was able to get in via facebook. problem is when i want to root my phone it shows error 1004. what did I do wrong?

Bastio001 said:
hello, I've been trying to login to my account since this morning. after half a day I was able to get in via facebook. problem is when i want to root my phone it shows error 1004. what did I do wrong?
Click to expand...
Click to collapse
I've searched around, and it seems to be caused by a VPN. If you use a VPN, turn it off and try again. If not, it could be that the Xiaomi unlocking API is down temporarily.

When I root my Redmi Note 10 Pro (sweet) by using twrp to flash magisk 25.2 and lazyflasher-no-verify-opt-encrypt.zip, I receive following message
.
Nevertheless, I reboot my phone which is effectively rooted.
I can then install Magisk manager.
Has someone an idea about the meaning of this error message ?
Thanks in advance.

cocopipou said:
When I root my Redmi Note 10 Pro (sweet) by using twrp to flash magisk 25.2 and lazyflasher-no-verify-opt-encrypt.zip, I receive following message
View attachment 5704507.
Nevertheless, I reboot my phone which is effectively rooted.
I can then install Magisk manager.
Has someone an idea about the meaning of this error message ?
Thanks in advance.
Click to expand...
Click to collapse
No need to flash lazy flasher since you already flashed Magisk. They both do the same which is to disable dm verity. Also, lazy flasher is an old zip intended for old devices so maybe that's why it failed.

BigChungus321 said:
No need to flash lazy flasher since you already flashed Magisk. They both do the same which is to disable dm verity. Also, lazy flasher is an old zip intended for old devices so maybe that's why it failed.
Click to expand...
Click to collapse
I thank You very much.

BigChungus321 said:
No need to flash lazy flasher since you already flashed Magisk. They both do the same which is to disable dm verity. Also, lazy flasher is an old zip intended for old devices so maybe that's why it failed.
Click to expand...
Click to collapse
then what is the solution bro...still i cant install some custom roms showing error 1...please help me.

cocopipou said:
When I root my Redmi Note 10 Pro (sweet) by using twrp to flash magisk 25.2 and lazyflasher-no-verify-opt-encrypt.zip, I receive following message
View attachment 5704507.
Nevertheless, I reboot my phone which is effectively rooted.
I can then install Magisk manager.
Has someone an idea about the meaning of this error message ?
Thanks in advance.
Click to expand...
Click to collapse
bro am facing this erros 1. will u pls help me.

THis is the stupidest guide for beginners, this article assumes you have unlocked your phone in the first place. All the important steps are just skipped and is stuffed in the requirements. And just shows simple screenshots that even a child would know where to click.
No external links to find the sources.

While unlocking the bootloader I'm having the issue linked below, thanks in advance for all and any responses. https://forum.xda-developers.com/t/mi-unlock-country-code-broken.4572339/

r4nchy said:
THis is the stupidest guide for beginners, this article assumes you have unlocked your phone in the first place. All the important steps are just skipped and is stuffed in the requirements. And just shows simple screenshots that even a child would know where to click.
No external links to find the sources.
Click to expand...
Click to collapse
AGREE 100%!!!