Root Infocus M430 bingo 21 - Magisk systemless root - Upgrading, Modifying and Unlocking

Finally able to root my infocus m430 running marshmallow.
To do this, you would require:
data cable
stock marshmallow running infocus m430 bingo 21
adb and fastboot installed on your computer. -> google this if never heard of.
download attachments of this post(patched_boot.img and Magisk app)
Procedure:
unlock developer options -> google this if you never knew this until now.
unlock oem. Do this by going to developer options -> oem unlocking(enable).
Install magisk application present in attachment
unzip the boot image attachment
enter fastboot by typing following command.
Code:
adb reboot bootloader.
flash patched_boot.img in the attachement. Do this by using following commands.(place your patched_boot in the current directory of terminal / cmd)
Code:
fastboot erase boot
fastboot flash boot patched_boot.img
In case you have any questions, message me or while commenting, refer my name with @

it says error in last step and my phone stuck in fastboot mode

I have the same issue

You should not face any issue if you have the files in current working directory of your terminal or command prompt. Post me a screenshot of the command prompt or terminal app and I should be able to help.
Also, after doing the process, you should do "fastboot continue" to restart mobile.
predatorswill said:
I have the same issue
Click to expand...
Click to collapse

sultanahamer said:
You should not face any issue if you have the files in current working directory of your terminal or command prompt. Post me a screenshot of the command prompt or terminal app and I should be able to help.
Also, after doing the process, you should do "fastboot continue" to restart mobile.
Click to expand...
Click to collapse
It is saying wating for device and device stuck on fast boot logo every time i tried

Related

Installing Clockwork Recovery

Hello
I am following the following tutorial below to install the clockworkmod recovery but when I enter the cmd fastboot flash recovery recovery-clockwork-touch-5.8.0.0-ace.img. The cmd prompt displays the message "waiting for device" but does not do anything. Am I doing anything wrong?
1. Download and place the package file onto your Desktop.
2. Extract files from the package to your Desktop.
3. Connect your smartphone to the PC using the USB cable.
4. Double-click the Start Here.bat file to open the Command Prompt Window.
5. Enter the following command into the Command Prompt Window:
adb reboot bootloader
6. Your smartphone should reboot into the Fastboot mode.
7. Now, enter the following command into the same Command Prompt Window:
fastboot flash recovery recovery-clockwork-touch-5.8.0.0-ace.img
8. After the recovery has been installed on your smartphone, issue the following command:
fastboot reboot
9. Your smartphone should reboot.
Thank You
mfredy said:
Hello
I am following the following tutorial below to install the clockworkmod recovery but when I enter the cmd fastboot flash recovery recovery-clockwork-touch-5.8.0.0-ace.img. The cmd prompt displays the message "waiting for device" but does not do anything. Am I doing anything wrong?
1. Download and place the package file onto your Desktop.
2. Extract files from the package to your Desktop.
3. Connect your smartphone to the PC using the USB cable.
4. Double-click the Start Here.bat file to open the Command Prompt Window.
5. Enter the following command into the Command Prompt Window:
adb reboot bootloader
6. Your smartphone should reboot into the Fastboot mode.
7. Now, enter the following command into the same Command Prompt Window:
fastboot flash recovery recovery-clockwork-touch-5.8.0.0-ace.img
8. After the recovery has been installed on your smartphone, issue the following command:
fastboot reboot
9. Your smartphone should reboot.
Thank You
Click to expand...
Click to collapse
Are your drivers installed already?
bananagranola said:
Are your drivers installed already?
Click to expand...
Click to collapse
Yh, I have installed all the latest driversss
mfredy said:
Yh, I have installed all the latest driversss
Click to expand...
Click to collapse
Is your phone in debug mode?
bananagranola said:
Is your phone in debug mode?
Click to expand...
Click to collapse
yupppppppppppp
mfredy said:
yupppppppppppp
Click to expand...
Click to collapse
No idea then. Post the entire log.
mfredy said:
yupppppppppppp
Click to expand...
Click to collapse
Were your drivers installed with the phone unplugged?
-Check your data-sync cable,It should not only allow your device to charge but also data-sync.( Try with another data-sync cable)
-As you stated drivers are installed.Then when you're on bootloader,It should show HBOOT-USB. If that shows than try doing same thing again.
Or else follow simple steps below:
-Copy CWM recovery.img into fastboot files.
-Unplug your device if connected to computer.
-Manually power off your device.
-Press Volume down + Power button,It will redirect into hboot.
-Select Bootloader by clicking on power button,It will change color of HBOOT from Blue to Red.
-Next thing you'll notice that it stated as HBOOT USB.
-Put your phone on side and do same commands fastboot flash recovery recovery-clockwork-touch-5.8.0.0-ace.img
-Fastboot reboot.
Once process been done. Unplug it and boot device normally. And to check whether there's a recovery.img installed or not,Just power off your device and put on charge. In CWM it will redirect your into recovery mode while device is switched off.
4EXT Recovery Touch
Try 4EXT Recovery Update , install app , download 4EXT Recovery . Done

[GUIDE] Unlocking bootloader and Rooting Micromax Q394

UNLOCKING BOOTLOADER:
a) Download Koush Universal adb driver from https://clockworkmod.com and adb setup.
b) Install the driver first and install adb after that.
c) Type n and press Enter when adb setup asks for installing drivers.
d) After the installation, run command prompt as administrator.
e) Open File explorer, and navigate to C:\adb
f) Please take backup of your data before proceeding further.
g) In C:\adb press Shift+right click and select Open Command Window here.
h) Enable USB debugging on your phone and connect your phone to pc using USB cable.
i) Type
Code:
adb devices
and press enter.
j) If it shows some device to be connected, only then proceed further.
k) Type
Code:
adb reboot bootloader
and press enter.
l) Phone will boot into fastboot mode.
m) Type
Code:
fastboot devices
and press enter.
n) If it shows some device to be connected, only then proceed further.
o) Type
Code:
fastboot oem unlock
and press enter.
p) On the phone screen, the phone will ask for confirmation to unlock bootloader.
Once fastboot shows "Success" or "Done" or something else signifying that the command was successful, type
Code:
fastboot reboot
and press enter.
q) Your phone will reboot normally.
Congrats, you have successfully unlocked bootloader.
ROOTING:
1. For Dr. Fone - Root:
a) Download and install Dr. Fone - Root on your PC.
b) Enable USB debugging on your phone.
c) Open Dr. Fone - Root and select Root option.
d) Connect your phone to your PC with USB cable.
e) Dr. Fone - Root will detect your phone in a few minutes.
f) Click "Root" button and wait.
Congrats, you have a rooted phone now.
2. For Magisk:
You'll find instructions to install Magisk over here.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
3.Through TWRP:
a) Download SuperSU.zip or Magisk.zip
SuperSU link:
http://download.chainfire.eu/696/supersu/
THIS IS A LINK FOR AN OLDER VERSION OF SUPERSU SINCE supersu.com IS SHOWING DOWNLOAD ERRORS.
Magisk link:
Given in method 2 of rooting.
b) Download and flash TWRP from this thread, instructions have been provided in the thread for flashing it:
https://forum.xda-developers.com/ca...nofficial-twrp-3-2-3-micromax-canvas-t3833332
c) Boot into TWRP.
d) Select "Install" option.
e) In the File Manager that opens, select the zip you want to flash.
f) Follow the instructions on the screen.
g) Select "Reboot System"
Congrats, you have a rooted phone now.
Note: Kingoroot used to work before but it only provides temporary root now. Once you reboot, you lose root.
HIT THANKS IF FOUND USEFUL
mali_ said:
Any custom rom for this phone?
Click to expand...
Click to collapse
Not yet
mali_ said:
Is there an official stock firmware download link or just the thirdparty links?
Click to expand...
Click to collapse
androidmtk.com provides official firmware
mali_ said:
Magisk works on this?
What are the safe to remove apps?
Click to expand...
Click to collapse
Yes, Magisk works on this. I am using it right now.
You can uninstall any app you want without any side effects as long as the app is not an essential part of system.
For example, Firsttouch Launcher, Swiftkey Keyboard, Email, Amazon Kindle, App Center, App Bazaar, Chaatz, Hangouts etc.
You can use Debloater.
It is a magisk module you can use by terminal emulator to remove bloatware.
HIT THANKS IF FOUND USEFUL
if device doesn't show anything after writing fastboot devices command what is to be done...???
Masumilicioz said:
if device doesn't show anything after writing fastboot devices command what is to be done...???
Click to expand...
Click to collapse
Have you installed the drivers I mentioned or some other ones?
Btw, are you running adb and fastboot in Windows or Linux?
Thanks You for this post.
WHen I get to step "K" the device simply reboots fully back into normal OS
then further steps are not recognized if I do not keep putting "adb" in front
like it will not recognize fastboot devices
but it will recognize "adb fastboot devices"
---------- Post added at 08:15 AM ---------- Previous post was at 08:13 AM ----------
Not sure if I got the adb drivers right because I did not see any "koushes adb" I mesn the site was clearly koushes but no where did I see a download names or called "koushes adb" Am I missing something?
protomind said:
WHen I get to step "K" the device simply reboots fully back into normal OS
then further steps are not recognized if I do not keep putting "adb" in front
like it will not recognize fastboot devices
but it will recognize "adb fastboot devices"
---------- Post added at 08:15 AM ---------- Previous post was at 08:13 AM ----------
Not sure if I got the adb drivers right because I did not see any "koushes adb" I mesn the site was clearly koushes but no where did I see a download names or called "koushes adb" Am I missing something?
Click to expand...
Click to collapse
You can get adb from SDK Tools from
https://developer.android.com/studio/ and Universal ADB Drivers from https://clockworkmod.com
I got TWRP recovery installed created by you. Big thanks !
I'm having issues in installing magisk via zip as well as patched boot image. Was the process smooth for you?
I got it to work by editing boot.img.
Are you working on any custom rom ?
Do you have any roms which can be ported to Q394 ?
Ashishoswal said:
I got TWRP recovery installed created by you. Big thanks !
I'm having issues in installing magisk via zip as well as patched boot image. Was the process smooth for you?
Click to expand...
Click to collapse
Yes, there were no problems at all.
Tell me the problem in detail so that I would be able to help.
Augustoandro said:
Yes, there were no problems at all.
Tell me the problem in detail so that I would be able to help.
Click to expand...
Click to collapse
Solved by changing some values in default boot image.
Are you working on any custom rom for this device ?
Ashishoswal said:
Solved by changing some values in default boot image.
Are you working on any custom rom for this device ?
Click to expand...
Click to collapse
I am working on creating a device tree first, but it will take some time.
Im not a developer but if there's any task which can be done by following a guide, and is helpful for you then let me know. I will be glad to help you.

Custom recovery TWRP for Infocus bingo 21 m430

Working TWRP custom recovery for infocus m430 bingo 21.
To do this, you would require:
data cable if not rooted phone
stock marshmallow running infocus m430 bingo 21
if not rooted, you need adb and fastboot installed on your computer-> google this if never heard of.
download attachments of this post(twrp_recoveryimg)
Problems:
Before you do this, you need to know the temporary problems you would encounter and their solutions
TWRP is in other language but you can use this link to bring it back to english, 1 time thing
http://www.teamandroid.com/2017/04/30/change-twrp-recovery-language-english/
if the above link does not work out, there are lot of youtube videos to enable english in twrp. google out.
once mobile boots into recovery, it will not come back to normal. There is a bit being set by infocus on some partition to reboot to recovery always. Until i find it, you would have to use following the process below to come back to normal boot.
Steps to come back to normal boot
1. in recovery, select option advanced
2. select adb sideload option
3. swipe to start sideload(this will start adb in recovery mode)
4. cancel
5. in your computer type
Code:
adb reboot bootloader
6. After mobile shows fastboot mode: in top of the screen with infocus logo type the below command
Code:
fastboot continue
7. This should boot your device back to normal android boot.
8. You have to do this every time you boot to recovery.
Now follow the below procedures to get a custom recovery on your mobile.
Procedure 1 : (does not require root)
unlock developer options -> google this if you never knew this until now.
unlock oem. Do this by going to developer options -> oem unlocking(enable).
unzip the recovery image attachment
enter fastboot by typing following command.
Code:
adb reboot bootloader.
flash twrp_recovery.img in the attachement. Do this by using following commands.(place your twrp_recovery.img in the current directory of terminal / cmd)
Code:
fastboot erase recovery
fastboot flash recovery twrp_recovery.img
Procedure 2 : (requires root) I have not tried this but it would work. Try it on your own risk.
Download the attachments
send them to your mobile sdcard
install mobile uncle tools or similar app from play store which would flash recovery images
select install recovery and point to the twrp_recovery.img in your sdcard.
Message me in case of questions or reply this thread.
Sir,where to type the code 'adb reboot bootloader' and other codes?
Want your contact number, for the purpose of custom recovery.
I tried that steps many times on my phone via pc. So help me for the custom recovery. I want your contact number to do this process correctly without worrying any problem occurs on my phone.
You should be able to find youtube video on how to install adb and fastboot online. After that, you should type those commands in command prompt in windows computer if you have or in terminal if you have linux or mac.
[email protected] said:
Sir,where to type the code 'adb reboot bootloader' and other codes?
Click to expand...
Click to collapse
Gimme your whatsapp or telegram number, i should be able to reach you out.
iyyappan001 said:
I tried that steps many times on my phone via pc. So help me for the custom recovery. I want your contact number to do this process correctly without worrying any problem occurs on my phone.
Click to expand...
Click to collapse
Problem while using adb fastboot method in In focus M425
What about infocus M425 phone ????

New Razer Phone (1) stuck on download mode.

I bought a refurbished Razer phone one from the official razer eBay page, and it's stuck on download mode. I haven't tried flashing anything, I haven't even ever been to the home screen. What can I do to fix this?
Get the Google USB Driver and make sure your Razer phone is installed with these drivers
https://developer.android.com/studio/run/win-usb
Get Android SDK Platform Tools for latest ADB and fastboot tool
https://developer.android.com/studio/releases/platform-tools
Open command prompt to that folder and run these commands
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot set_active a
from what i've gathered from other threads with similar problems, that's the jist of it...
It says "Waiting for any device" the problem is that it's not recognized by the computer.
Thank you ! Same problem. This is halp! after first run, works. Question, can I block it now? and how please... fastboot flashashing lock ?
Now I can block back? fastboot flashashing lock ?
ShadowVlican said:
Get the Google USB Driver and make sure your Razer phone is installed with these drivers
Open command prompt to that folder and run these commands
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot set_active a
from what i've gathered from other threads with similar problems, that's the jist of it...
Click to expand...
Click to collapse
Hello. Same problem. ( I bought a refurbished Razer phone one from the official razer eBay page, and it's stuck on download mode. I haven't tried flashing anything). It helped me. Now I can block back? fastboot flashashing lock ? Please, sorry my english...
EDIT: The links did not copy paste appropriately. I fixed them now.
These are all posts from various places in this thread:
https://forums.redflagdeals.com/raz...b-1yr-warranty-8gb-64gb-octacore-9-0-2336958/
"Find the driver here:
https://dl-ssl.google.com/android/repository/latest_usb_driver_windows.zip
unzip the files/folder to a location you will remember
Follow the instructions below, point the windows driver update to the .inf file in that folder then driver will install. Make sure you have the latest Android platform tools, the link is also in the PDF below.
https://s3.amazonaws.com/cheryl-fac...stall_Android_Fastboot_Drivers_on_Windows.pdf
open a command prompt from within the Android sdk folder while the phone is still in download mode (phone stays and reboots to download mode through each process below making the process fairly easy)
type: fastboot devices
your phone should show up once drivers are installed correctly
type: fastboot flashing unlock
use the phone vol + - and power to select yes
phone should stay in download mode
type: fastboot flashing unlock_critical
use vol + - and power to select yes
phone should stay in download mode
Download the firmware image below or if you want to try the following command type: fastboot set_active a && fastboot reboot
to see if the phone boots, not sure if all the phones have Android installed. One poster below seems to and also seems to have his bootloader unlocked. This won't be the case for everyone. If phone does not boot continue downloading the firmware to install it
https://s3.amazonaws.com/cheryl-factory-images/cheryl-o-global-6033.zip
unzip all the files and put them in the android sdk folder, from the same command prompt if you're on Windows
type: flash_all.bat
For Mac type: flash_all.sh
Will take a few minutes but firmware will install. These instructions are for RFD members that do not either 1) want the hassle of RMA or 2) take a chance at voiding the warranty (any phone flashing via adb is frowned upon by Razer)"
------------------------------------------------------------
"Yes. Reverse the locking procedure. Put phone back into Download mode (from power off, press and hold Vol up and then plug phone into computer) then issue fastboot commands to lock boatloader starting with critical."
------------------------------------------------------------
"if you have a ryzen pc and getting some error while unlocking... dont plug the phone in at the beginning... type the command when it says [waiting for device] then plug it in ... also dont forget to unlock critical right after"
Now I can block back? fastboot flashashing lock ?
ShadowVlican said:
Get the Google USB Driver and make sure your Razer phone is installed with these drivers
Open command prompt to that folder and run these commands
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot set_active a
from what i've gathered from other threads with similar problems, that's the jist of it...
Click to expand...
Click to collapse
it helped, now it is loaded; but after each reboot it writes, the phone is unlocked and that it is unsafe. can it be blocked back, is it safe that everything continues to work? please write what commands to enter?
365Thanks said:
it helped, now it is loaded; but after each reboot it writes, the phone is unlocked and that it is unsafe. can it be blocked back, is it safe that everything continues to work? please write what commands to enter?
Click to expand...
Click to collapse
Repeat the unlock commands using lock instead of unlock but in reverse order so:
fastboot flashing lock_critical
fastboot flashing lock
again you must place the phone in download mode (powered off...hold volume down key down...plug in) between each command and follow the onscreen instructions.
Open command prompt to that folder and run these commands
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot set_active a
from what i've gathered from other threads with similar problems, that's the jist of it...[/QUOTE]
flopticalcube said:
Repeat the unlock commands using lock instead of unlock but in reverse order so:
fastboot flashing lock_critical
fastboot flashing lock
again you must place the phone in download mode (powered off...hold volume down key down...plug in) between each command and follow the onscreen instructions.
Click to expand...
Click to collapse
after each command you need to disconnect from the computer? fastboot flashing unlock
fastboot flashing unlock_critical
fastboot set_active a
I used to enter these commands , the instructions were only after 1
I did not turn off the phone and the question on the screen was only after the first command. I probably entered only 1 command <if it was necessary to disconnect phone? ... thank you for help.
Sudo.
If ur using linux - run it with sudo. always run fastboot with sudo
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot set_active a
error: Device does not support slots

Question Attempting to unlock bootloader (T-Mobile). Bootloader issues.

I'm attempting to follow this guide here https://forum.xda-developers.com/t/how-to-unlock-the-t-mobile-bootloader.4256319/ and I'm finding myself having issues at step #5. ADB picks up my device while it's on no issue but when I reboot into bootloader, it no longer picks up my device to get the unlock code.
Anyone know what the issue could be? Any help is appreciated.
Edit: when I use the command "fastboot oem get_unloock_code" the CMD window says "Waiting for any device"
You don't have fastboot drivers.
craznazn said:
You don't have fastboot drivers.
Click to expand...
Click to collapse
I installed ADB and Fastboot through this, does it not include Fastboot? When I open CMD in the install folder and use "fastboot --version" I get " eac51f2bb6a8-android " https://developer.android.com/studio/releases/platform-tools
Edit: Believe I've got it now..Had to go to Windows 10 optional Updates and select Google Bootlader Interface. After that, I was able to get my unlock code.
MushroomElm said:
I installed ADB and Fastboot through this, does it not include Fastboot? When I open CMD in the install folder and use "fastboot --version" I get " eac51f2bb6a8-android " https://developer.android.com/studio/releases/platform-tools
Edit: Believe I've got it now..Had to go to Windows 10 optional Updates and select Google Bootlader Interface. After that, I was able to get my unlock code.
Click to expand...
Click to collapse
Glad you figured it out

Categories

Resources