Database Develop

[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] Root/Flash for Xiaomi Redmi 2

AnandMore's How-To Guide For Beginners
Xiaomi Redmi 2
{
"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"
}
Intro:
This thread will serve as a location for basic how-to guides for the Xiaomi Redmi 2. I'm going to start off with a couple of the more obvious ones and go from there. If anyone has any suggestions for additions please feel free to let me know.
By attempting any of the processes listed this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches on fire, or turns into a hipster and claims to have been modified before it was cool.
Index:
Post #1 - Rooting your Redmi 2
Post #2 - Flashing Custom Recovery
Post #3 - Flashing Custom ROMs
Post #4 - Flashing Custom Kernels
Resources:
Everything you need for Xiaomi Redmi 2 is available in the below given thread -
[INDEX] Xiaomi Redmi 2

Rooting your Redmi 2:
This guide will root your device through Stock MI Recovery(Works with TWRP also), but this is not Native Root. A new app named SuperSU will be installed, which will give root Permission.
Note:
Rooting does not Void Warranty.
Caution:
This is a safe process, but I am not responsible for anything bad that happens to your phone.
In most cases this approach of rooting should not block OTA updates.
Steps to follow for rooting:
Download the Root.zip and Copy the file to the folder 'Internal storage' (root of internal storage).
(File at the end of thread)
Open the Updater app, Press the 3 dots at Right Top Corner, A menu will open. Tap on “Choose Update Package“ and select the Root.zip File.
Wait until device will reboot.
After reboot a new app SuperSu will be installed.
Open the app and Choose "Continue".
Choose "Normal", Don't Choose TWRP/CWM, device will go into Boot Loop.
Note - Don't Choose TWRP/CWM, it will brick your device.
After sucessful updation , press ok.
Your Phone has now Root Permission.
Open any app using Root permission and SuperSU will ask for Permission.
Enjoy your rooted Redmi 2.
Un Root The Device:
For Un Root , open the SuperSU app,tap on Settings, Choose Full Unroot.
Your Device is Un Rooted Sucessfully. The SuperSU app will be removed.

Flashing Custom Recovery:
From Mobile:
Install Flashify app from Playstore
Once installed, access the application through app drawer.
Allow root access now and get navigate to Flashify’s home screen.
First take a backup of your recovery in case something goes wrong. (RECOMMENDED)
Now tap on recovery image and by "Choose the file" menu locate the .img file you want to flash.
After successful flashing it will ask you to reboot your device.
Done! You have custom recovery on your phone.
From PC:
Enable USB debugging, go to settings>about phone and then tap on Android/MIUI version 5 times. Developer Options will be enabled. Now go back to settings>Developer options and enable USB debugging.
ADB and Fastboot Drivers installed on your PC. I can provide you the drivers but it would be a better option to install MiFlash to get all the necessary drivers and Miflash software with you for future use.
Install Miflash on your PC. Lets suppose we installed it in C:\Xiaomi folder.
You can see two folders, proceed to "adb' folder
Then proceed to "Google" folder.
Proceed to "Android" Folder.
We are at our destination.
Now Hold down "Shift" button on your computer keyboard and right click with mouse on an empty part of the window. You will see that in the menu that appears, you have an option - "open command window here". Click on that
To verify if ADB is working and installed correctly, type "adb version" in the command window that opened without the code. You should get the adb version which means its working fine.
Turn off your Phone. When its completely switched off, press and hold "Volume Down" and "Power" button together and then the phone will turn on in Fastboot mode.
Use the USB cable to connect Phone to PC.
Copy the Recovery.img in the Android folder where we are running the Command prompt. (C:\Xiaomi\adb\Google\Android in my case as i installed Mi flash in C:\Xiaomi folder)
Now go back to command promt and enter the following commands -
Code:
fastboot devices
Once you enter that command, you will get a non-empty name for the device meaning the device is connected. Proceed to enter the next command to flash recovery image -
Code:
fastboot flash recovery recovery.img
Once you enter this command, the recovery image will be flashed on your device. Once it is completed, enter the final command to reboot your phone -
Code:
fastboot reboot
Your phone will reboot.
You have have now completed flashing custom recovery replacing Stock Mi recovery on your Xiaomi Redmi 2.

Flashing custom ROMs:
Steps to Follow:
Download and transfer the custom ROM you wish to flash to your device’s storage.
Boot your device into TWRP recovery.
Select “Wipe” from TWRP main menu and do a “Swipe to Factory Reset” on the bottom of screen.
Note: This will factory reset your device. If your custom ROM doesn’t require a factory reset, then simply skip this step.
Go back to TWRP main menu, tap on “Install” and select the custom ROMs .zip file that you transferred to your device in Step 1.
After selecting the .zip file, do “Swipe to Confirm Flash” on the bottom of screen to begin the custom ROM installation process. This may take some time.
Once your ROM is successfully flashed, you’ll see “Wipe cache/dalvik” option, select it and then do “Swipe to wipe” on bottom of screen.
Once cache & dalvik wipe completes, hit the “Back” button on-screen and then select “Reboot System” button.
That’s all. Your device will now reboot with the custom ROM you just flashed. Since this will be the first reboot after flashing a new ROM, it might take some time to rebuild cache and finish boot, have patience.

Flashing Custom Kernels:
Steps to Follow:
Download and transfer the custom Kernel you wish to flash to your device’s storage.
Boot your device into TWRP recovery.
In the TWRP main menu, tap on “Install” and select the custom Kernel .zip file that you transferred to your device in Step 1.
After selecting the .zip file, do “Swipe to Confirm Flash” on the bottom of screen to begin the custom Kernel installation process. This may take some time.
Once flashing completes, hit the “Back” button on-screen and then select “Reboot System” button.
That’s all. Your device will now reboot with the custom Kernel you just flashed. Since this will be the first reboot after flashing a new Kernel, it might take some time to rebuild cache and finish boot, have patience.

For list of all available Roms visit this thread :
http://forum.xda-developers.com/redmi-2/how-to/available-custom-marshmallow-roms-redmi-t3278535
Click to expand...
Click to collapse
Better if you make lollipop ROMs thread too

Superb work bro thanks ...u

Isn't MIUI rooted out of the box already? [emoji52]

Stachura5 said:
Isn't MIUI rooted out of the box already? [emoji52]
Click to expand...
Click to collapse
Developer ROMs are. Global ROMs aren't.
Device comes with global ROM :3

noobpremium said:
Better if you make lollipop ROMs thread too
Click to expand...
Click to collapse
I made both lollipop and marshmallow roms in one thread. So you think i should make seperate one for lollipop.

Stachura5 said:
Isn't MIUI rooted out of the box already? [emoji52]
Click to expand...
Click to collapse
All roms(Beta,developer,stable) for Redmi 2 are not Pre rooted.

Added videos tutorials for better understanding.

Great info, thanks a lot!
I have a very basic, very likely extremely stupid question: I flashed an early CM12.1 build (using CWM afaik) and for unknown reasons, I cannot boot into recovery and don't have root. How can I re-gain root access from here?

my phone also rebooting. please help me. how to go to recovery?

srmohanrajan said:
my phone also rebooting. please help me. how to go to recovery?
Click to expand...
Click to collapse
1) Switch off the phone.
2) Press the Volume Down, Volume Up and the Power Button at the same time, about 2-3 seconds until the mi logo shows up.
3) Recovery mode menu will appear.

Fr3ak23 said:
Great info, thanks a lot!
I have a very basic, very likely extremely stupid question: I flashed an early CM12.1 build (using CWM afaik) and for unknown reasons, I cannot boot into recovery and don't have root. How can I re-gain root access from here?
Click to expand...
Click to collapse
Follow the same steps to boot into recovery and flash SuperSU v2.4.6 zip via recovery
(And remember you are responsible if anything happens to the device)

omg, I am so stupid. I tried vol up + power, vol down + power and all possible combinations including the home button, but never vol up + vol down + power button. Thank you!

Fr3ak23 said:
omg, I am so stupid. I tried vol up + power, vol down + power and all possible combinations including the home button, but never vol up + vol down + power button. Thank you!
Click to expand...
Click to collapse
No problem bro !
✌

Great !

New CM 12.1 is awesome, finally the camera works
I am curious on why I keep on losing root access. I never had that issue with any other phones and custom ROMs.

[GUIDE][9.0][ROLLBACK] Complete Guide to Upgrade to Android 9 From JUI or Nougat ROM

Today I will make a guide as complete as possible to guide new user into flashing custom ROM for their Coolpad Cool 1 Dual. This guide as far as I can tell is usable for all C103, C106 and R116 version.
Introduction :
So our device finally got Android 9 in custom ROM development. Unfortunately, to flash Android 9 you need to be on EUI Android 6 Marshmallow. For those who are already on Android 7 you need to rollback to stock EUI to upgrade to Android 9 or else your device wouldn't boot or stuck in bootloop even with full wipe in TWRP.
Preparations :
1. Microsoft .NET Framework 4.7.1 (Offline Installer)
2. Visual C++ Redistributable for Visual Studio 2015
3. Coolpad Download Assistant Setup V1.94_170421.exe
4. Coolpad keys for Assistant ( you need to sign up an account at 4pda to download )
5. Stock EUI18 ROM package for Coolpad Download Assistant
6. Coolpad Driver
7. MiFlash 2015
8. TWRP 3.1.0 by Cuoco92.zip ( you need to sign up an account at 4pda to download )
9. Qualcomm HS-USB QDLoader 9008 driver. ( Windows 10 already has this driver automatically )
10. Android 9 ROM of your choice, of course.
Step 1 : Rolling Back to EUI18
1. Install everything. In the install directory of Coolpad Download Assistant, extract the "Coolpad keys for Assistant" files into main folder. Run Coolpad Download Assistant as administrator.
2. Put phone into bootloader (fastboot) mode. To do this, turn off your phone. Press Vol Down and connect your phone into your PC. The device will boot into bootloader mode with chinese letters and android icon on screen. Check your device manager and it should detect your phone as "Coolpad Android Bootloader Interface". If it didn't detect, make sure you install the driver or try changing USB ports.
{
"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. Extract the EUI18 .zip file into a folder. It should contain 2 files, "init.cpb" and "ROM.cpb"
4. Open Coolpad Download Assistant. Browse to the folder where you extracted both files. First, select "init.cpb" and click the green button in Coolpad Download Assistant. This "init.cpb" will prepare your device to flash stock EUI and wipe everything.
5. After it finished, now select "ROM.cpb" and click the green button to start flashing. This is the main ROM files to install stock EUI18 into your phone. Your phone screen will change into chinese letters with gears icon.
6. If everything went well, it will say upgrade finished without any error message or red letters at the blue smiley screen. You're now back to stock EUI and stock recovery.
Step 2 : Installing TWRP custom recovery to EUI
1. Now that you successfully rollback to EUI you need to flash new custom recovery TWRP to your phone because you now have stock recovery.
2. Put your phone into QDLoader 9008 mode. To do this, turn off your phone. Press Vol Up + Vol Down button and connect to your phone to PC. Check your device manager and it should detect your phone as "Qualcomm HS-USB QDLoader 9008" (COMXX). Your LED should be blinking red if it enter this mode.
3. Extract TWRP 3.1.0 by Cuoco92 in folder. There's a lot of files here so make sure you put it into separate folder.
3. Open MiFLash 2015 and browse to TWRP 3.1.0 by Cuoco92 folder that you have extracted in your PC.
4. Click refresh in MiFlash and if you got all the correct files earlier, it should detect your phone in it identifies by COMXX ( XX is any number ). If it doesn't detect, try rebooting and booting into QDLoader mode or just change USB ports.
5. In MiFlash, select "Flash all except storage" and click "Flash". Wait for the green bar to finish and it says completed.
6. If everything went smooth without any error, disconnect your phone from the PC. The LED should stop blinking.
7. FIRST BOOT AFTER MIFLASH IS VERY IMPORTANT OR YOU HAVE TO DO THIS AGAIN MAYBE FROM THE COOLPAD DOWNLOAD ASSISTANT.
8. While the phone is still turned off, hold down Vol Up and press power button. This should boot your phone into recovery mode. If it boots into TWRP, then you have done everything perfectly. If it doesn't, try repeating MiFlash steps.
Step 3 : Flashing Android 9 with TWRP
1. Backup your images and document from your phone because we will wipe everything.
2. In TWRP, Wipe>Advanced Wipe, wipe everything, system, cache, data. After that, back to Wipe and choose wipe>format data. Type yes and let it format data to erase your device clean and remove encryption to be able to flash Android 9.
3. After wiping and format data, in TWRP, select Reboot>Recovery to reboot into recovery again. This is important because TWRP need to mount the partitions again after formatting the device.
4. At this point, you're now free to flash any Android 9 ROM of your choice.
*no pictures for Coolpad Download Manager steps in this guide. Will probably put them later. (or not because that would mean I have to rollback my already on 9 Cool1 back to EUI and it might brick)

Reserved

are banking apps working on custom roms?
now i am on 18s (Found a zip file from some where and its working).But while i try to flash [rom] [official] [evolution - x] [pie] [c106/c103] after wiping data,caches , it saying the zip file is for c106,103 etc.One thing i am missing that i didnot format data as i think it will erase saved files from internal storage.Help please

nageswarswain said:
are banking apps working on custom roms?
now i am on 18s (Found a zip file from some where and its working).But while i try to flash [rom] [official] [evolution - x] [pie] [c106/c103] after wiping data,caches , it saying the zip file is for c106,103 etc.One thing i am missing that i didnot format data as i think it will erase saved files from internal storage.Help please
Click to expand...
Click to collapse
You need to edit the updater-script in rom .zip file.

hello can somebody upload the 4/8 step files from 4pda to some other host?
thanks

Back from Android 9 to eui 5.9 cuoco92
vulturext said:
Today I will make a guide as complete as possible to guide new user into flashing custom ROM for their Coolpad Cool 1 Dual. This guide as far as I can tell is usable for all C103, C106 and R116 version.
Introduction :
So our device finally got Android 9 in custom ROM development. Unfortunately, to flash Android 9 you need to be on EUI Android 6 Marshmallow. For those who are already on Android 7 you need to rollback to stock EUI to upgrade to Android 9 or else your device wouldn't boot or stuck in bootloop even with full wipe in TWRP.
Preparations :
1. Microsoft .NET Framework 4.7.1 (Offline Installer)
2. Visual C++ Redistributable for Visual Studio 2015
3. Coolpad Download Assistant Setup V1.94_170421.exe
4. Coolpad keys for Assistant ( you need to sign up an account at 4pda to download )
5. Stock EUI18 ROM package for Coolpad Download Assistant
6. Coolpad Driver
7. MiFlash 2015
8. TWRP 3.1.0 by Cuoco92.zip ( you need to sign up an account at 4pda to download )
9. Qualcomm HS-USB QDLoader 9008 driver. ( Windows 10 already has this driver automatically )
10. Android 9 ROM of your choice, of course.
Step 1 : Rolling Back to EUI18
1. Install everything. In the install directory of Coolpad Download Assistant, extract the "Coolpad keys for Assistant" files into main folder. Run Coolpad Download Assistant as administrator.
2. Put phone into bootloader (fastboot) mode. To do this, turn off your phone. Press Vol Down and connect your phone into your PC. The device will boot into bootloader mode with chinese letters and android icon on screen. Check your device manager and it should detect your phone as "Coolpad Android Bootloader Interface". If it didn't detect, make sure you install the driver or try changing USB ports.
3. Extract the EUI18 .zip file into a folder. It should contain 2 files, "init.cpb" and "ROM.cpb"
4. Open Coolpad Download Assistant. Browse to the folder where you extracted both files. First, select "init.cpb" and click the green button in Coolpad Download Assistant. This "init.cpb" will prepare your device to flash stock EUI and wipe everything.
5. After it finished, now select "ROM.cpb" and click the green button to start flashing. This is the main ROM files to install stock EUI18 into your phone. Your phone screen will change into chinese letters with gears icon.
6. If everything went well, it will say upgrade finished without any error message or red letters at the blue smiley screen. You're now back to stock EUI and stock recovery.
Step 2 : Installing TWRP custom recovery to EUI
1. Now that you successfully rollback to EUI you need to flash new custom recovery TWRP to your phone because you now have stock recovery.
2. Put your phone into QDLoader 9008 mode. To do this, turn off your phone. Press Vol Up + Vol Down button and connect to your phone to PC. Check your device manager and it should detect your phone as "Qualcomm HS-USB QDLoader 9008" (COMXX). Your LED should be blinking red if it enter this mode.
3. Extract TWRP 3.1.0 by Cuoco92 in folder. There's a lot of files here so make sure you put it into separate folder.
3. Open MiFLash 2015 and browse to TWRP 3.1.0 by Cuoco92 folder that you have extracted in your PC.
4. Click refresh in MiFlash and if you got all the correct files earlier, it should detect your phone in it identifies by COMXX ( XX is any number ). If it doesn't detect, try rebooting and booting into QDLoader mode or just change USB ports.
5. In MiFlash, select "Flash all except storage" and click "Flash". Wait for the green bar to finish and it says completed.
6. If everything went smooth without any error, disconnect your phone from the PC. The LED should stop blinking.
7. FIRST BOOT AFTER MIFLASH IS VERY IMPORTANT OR YOU HAVE TO DO THIS AGAIN MAYBE FROM THE COOLPAD DOWNLOAD ASSISTANT.
8. While the phone is still turned off, hold down Vol Up and press power button. This should boot your phone into recovery mode. If it boots into TWRP, then you have done everything perfectly. If it doesn't, try repeating MiFlash steps.
Step 3 : Flashing Android 9 with TWRP
1. Backup your images and document from your phone because we will wipe everything.
2. In TWRP, Wipe>Advanced Wipe, wipe everything, system, cache, data. After that, back to Wipe and choose wipe>format data. Type yes and let it format data to erase your device clean and remove encryption to be able to flash Android 9.
3. After wiping and format data, in TWRP, select Reboot>Recovery to reboot into recovery again. This is important because TWRP need to mount the partitions again after formatting the device.
4. At this point, you're now free to flash any Android 9 ROM of your choice.
*no pictures for Coolpad Download Manager steps in this guide. Will probably put them later. (or not because that would mean I have to rollback my already on 9 Cool1 back to EUI and it might brick)
Click to expand...
Click to collapse
Hi
1- The first question
After going to Android 9
How to get back to eui 5.9 cuoco92 ?
2- The second question
To install different versions of Android 9 on the base
[Pixel Experience] or [Remix OS] or [evolution-x] or [Havoc OS]
wipe everything, system, cache, data, format data
On twrp
You are satisfied ?
Thanks :good:

Is it possible to flash android 9 ROM over Cool1_26S_ROW_BETA01_CUOCO92 ROM?
Thanks

[Android 11] Unofficial Lineage OS 18.1 for A21s

WARNING + DISCLAIMER:
By installing this custom ROM, you are VOIDING your warranty. Also, installation of this ROM WILL TRIP KNOX PERMANENTLY, and render apps such as Samsung Health, Private Folder, (+ any apps that depend on KNOX) useless until you get the phone's motherboard replaced at the Samsung C/S center.
Although this software is released in the hope that it will be useful, there is NO GUARANTEE that installing this will not cause any harm to your device. I TAKE NO RESPONSIBILITY FOR ANY BRICKED DEVICES, DAMAGED HARDWARE, OR ANY OTHER PROBLEMS CAUSED BY THIS ROM. You are using this ROM at YOUR OWN RISK. I strongly recommend that you DO NOT continue to the steps below UNLESS YOU FULLY UNDERSTAND WHAT YOU ARE DOING.
While this ROM has been tested with South Korean variant of Galaxy A21s (SM-A217N, CSC changed from LUC->SKC), please keep in mind that it hasn't been tested on any other variant (such as A217F, A217M.)
Click to expand...
Click to collapse
I would like to express special thanks to all the developers who contributed to the LineageOS port for Galaxy Tab S6 Lite + all the other developers who contributed to sepolicy & hardware parts for Samsung SLSI (Exynos) devices. Porting LineageOS to A21s would have been much harder without them.
Click to expand...
Click to collapse
After doing some research on this device, I was able to port LineageOS. The original sources are based on Galaxy Tab S6 Lite Wi-Fi version (gta4xlwifi), with some heavy modifications made for the A21s. In the process, I was able to fix some of the problems that were found on GSI (MTP, Fingerprint removal issues, NFC, Wi-Fi hotspot and direct), and added in some enhancements to the kernel.
Unfortunately, installation of this ROM requires Lineage Recovery, and since FBE (File-based-encryption) is enabled by default, it is incompatible with the TWRP.
Screenshot:
{
"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"
}
NOT WORKING:
- Cell Broadcast (Emergency Messages) is broken in South Korea. The phone shows notifications, but the messages appear broken. Not sure about other countries. FIXED in South Korea as of 2021/9/2. However, its functionality in other countries hasn't been tested.
- Samsung's Proprietary Apps
- In order to use Wi-Fi Direct, you need to install a Wi-Fi direct sharing app from Google Play, as LineageOS doesn't have a sharing app installed by default
- Auto Brightness (The phone doesn't have the sensors for it anyway)
- On very rare occasions(probably once in more than 20 boots), the device's RIL (Phone calls, Data) might start up late when booting. If you see "No service" after booting, please wait for 30-60 seconds.
- VoLTE & VoWifi(not tested) - Unfortunately, this is located deep within Samsung's framework. AOSP-based roms for other Samsung devices don't support it either. Someday, this might be fixed.....
WORKING:
- Everything Else
GITHUB:
Device Source Tree: android_device_samsung_a21s, android_device_samsung_universal3830-common
Kernel: android_kernel_samsung_universal3830-common
Instructions for Installation:
1. BEFORE INSTALLING, make sure that you have UNLOCKED the bootloader of your device. This is a great guide that show how to do it. Also, the phone must be on the Stock ANDROID 11. If you are on binary U6, please use the recovery tar for U6.
2. Download the Lineage Recovery, ROM, Google Apps, ADB, and Odin. Unzip ADB and Odin to somewhere appropriate.
- ROM
- Recovery / Recovery(for U6)
- Google Apps
- ADB
- Odin
3. Enable USB Debugging on the device. Go to settings->About phone->Software information, and tap the build number several times until you see the notification that the devloper settings have been enabled. After enabling developer settings, go to settings->developer settings and check USB debugging.
4. Open Command Prompt, and type "cd <the path where you saved ADB to>".
4-1. As a test, type "adb devices". After typing it, the phone should show a screen that asks you to grant permissions for USB debugging. Select Yes.
5. On the phone, start holding down the Volume Up and Down keys. KEEP THE KEYS PRESSED UNTIL THE PHONE REBOOTS AFTER YOU TYPE THE COMMAND IN THE NEXT STEP.
6. While holding the keys down. type in the command "adb reboot recovery" on the command line.
11. After the phone reboots into download mode, press volume up to continue. Make sure that you see the "OEM LOCK: OFF" before continuing.
12. Open Odin. After opening Odin, click on AP, and select the Lineage Recovery Tar file that you downloaded in the step 2. After that, click on Start.
13. After a few seconds, if everything goes well, Odin should show "PASS" and the device should reboot into Lineage Recovery. After the device enters recovery, tap on Apply update->Apply from ADB. In some cases, touchscreen may be unresponsive or slow. If that happens, use Volume Keys to navigate and Power key to select. KEEP THE DEVICE CONNECTED TO THE COMPUTER.
14. After choosing Apply from ADB, type "adb sideload <the path where you saved the ROM file>" on the command prompt and press enter.
<CONTINUED ON THE NEXT POST>

15. If everything goes right, the device should show "script succeeded: result was [1.000000]" While ADB may show errors such as "Failed to read command" at 47%, this is no problem as long as the device says that the script succeeded.
16. Now it is time to install Google apps. On the phone, tap on Apply from ADB again, and on the computer, type "adb sideload <the path where you saved Google apps to>" and press enter.
17. After about 1-2 minutes, installation should be complete. Again, ADB might show "Failed to read command" errors. As long as the phone says that it was success, this is no problem. After installing, click on the "back" icon shown below.
18. Choose Wipe data/factory reset, and reboot the device.
19. If everything went well, the phone should reboot into LineageOS. Set up the device and Enjoy!

ADDITIONAL TIP: HOW TO ROOT THE PHONE ON LINEAGE 18
On Lineage 18, I patched the kernel so that it would have no problem with the official Magisk app.
Therefore, you DON'T need to use a version that has been modified for A21s.
If you want to have root, you can get the Official Magisk App.
1. Download & Install Magisk from the official source.
2. Select Install. When it asks you to select the boot image, choose the boot image from the Lineage OS ROM file that you downloaded from the step above. After patching the boot image, move & rename it to something you can type easily (ex. /sdcard/rooting.img)
3. Enable developer settings (Settings->About phone->Tap on build number)
4. Go to developer settings and enable USB debugging & root permissions for usb debugging.
5. Connect the phone to the PC.
6. Open the command prompt, and type "cd <the folder where you installed adb>. After that, type "adb root". If the phone asks you for permissions for USB debugging, allow it.
7. After the adb shows "Restarting adbd as root", type "adb shell dd if=/sdcard/<the path to saved boot image>" of=/dev/block/by-name/boot". The output should be something like
" *** records in
*** records out
*** bytes (** M) copied, *** s, **M/s"
8. After seeing the output above, reboot the phone. After rebooting, it should be rooted.

Good news. Thank you very much

Then, my friends, write here how it works and thank you for your observations

Thanks for your work buddy.....
I got Magisk installed an easier way...
Download Magisk Canary .apk
Change .apk to .zip then install the same way as the Rom and Gapps, by ADB sideload.
Factory reset/Format data and reboot.
Done
All we need is a working TWRP.... I've got one working but it shows no files and won't mount anything..... e.g. system, data etc

Pharcanal40 said:
Thanks for your work buddy.....
I got Magisk installed an easier way...
Download Magisk Canary .apk
Change .apk to .zip then install the same way as the Rom and Gapps, by ADB sideload.
Factory reset/Format data and reboot.
Done
All we need is a working TWRP.... I've got one working but it shows no files and won't mount anything..... e.g. system, data etc
Click to expand...
Click to collapse
What is your device model ...is it SM A217F/DS android 11 U6? Pls reply..

Gxzllen said:
What is your device model ...is it SM A217F/DS android 11 U6? Pls reply..
Click to expand...
Click to collapse
A217F on U5

Pharcanal40 said:
A217F on U5
Click to expand...
Click to collapse
Can i download it on u6?i'm afraid my phone brick if i do it

Gxzllen said:
Can i download it on u6?i'm afraid my phone brick if i do it
Click to expand...
Click to collapse
If you're on U6, there's a chance that Odin might fail on vbmeta.
A possible solution is:
1. Download Magisk (version doesn't matter)
2. Download the U6 firmware that you're on
3. Using Magisk, patch the AP tar of U6 firmware
4. In the Lineage recovery tar file that you downloaded from above, replace the vbmeta.img with the one from Magisk-patched AP tar file
5. Proceed with the installation as written above
A more fail-safe method would be:
1. Root the phone using a patched Magisk app
2. unpack the recovery.img in the Lineage recovery tar file and copy it into your device's SD card
3. Enable USB debugging on the phone, and connect the phone to adb
4. Using command prompt, type
"cd <path to adb>"
"adb shell"
"su"
"dd if=/sdcard/<path to lineage recovery image> of=/dev/block/by-name/recovery"
"reboot recovery"
After typing these, your device will reboot into Lineage Recovery. After entering recovery, select apply update->apply from adb, and proceed with the installatiom above from Step 14.

grccorps said:
If you're on U6, there's a chance that Odin might fail on vbmeta.
A possible solution is:
1. Download Magisk (version doesn't matter)
2. Download the U6 firmware that you're on
3. Using Magisk, patch the AP tar of U6 firmware
4. In the Lineage recovery tar file that you downloaded from above, replace the vbmeta.img with the one from Magisk-patched AP tar file
5. Proceed with the installation as written above
A more fail-safe method would be:
1. Root the phone using a patched Magisk app
2. unpack the recovery.img in the Lineage recovery tar file and copy it into your device's SD card
3. Enable USB debugging on the phone, and connect the phone to adb
4. Using command prompt, type
"cd <path to adb>"
"adb shell"
"su"
"dd if=/sdcard/<path to lineage recovery image> of=/dev/block/by-name/recovery"
"reboot recovery"
After typing these, your device will reboot into Lineage Recovery. After entering recovery, select apply update->apply from adb, and proceed with the installatiom above from Step 14.
Click to expand...
Click to collapse
nice thankyou bro

Or you can extract just the boot.img from the AP.tar. Patch it in Magisk then repack in the AP and flash with Odin

Pharcanal40 said:
Or you can extract just the boot.img from the AP.tar. Patch it in Magisk then repack in the AP and flash with Odin
Click to expand...
Click to collapse
Ohh okay its easy this way

Can I use adb fastboot instead of Odin?

Successfully Flashed! Everything work fine.
Model- A217f /DS
U6 binary ,Android 11 latest.

NuzzaimStark said:
Successfully Flashed! Everything work fine.
Model- A217f /DS
U6 binary ,Android 11 latest.
Note: Encountered some problems when I flash (vbmeta) ie, its because of its only for u5.
Odin showed failed at last ,
Phone was unable to boot but
By using hijacking software , bootloader was again running . but when auto reboot lineage recovery was automatically loaded, and tryed your above steps and everything working fine,
Note: pubg is very very better in this ROM.
Close range is also better.
Thankyou grccorps .
Click to expand...
Click to collapse
Thank you for your review. It's such a great news that it's working on U6.
Yes, PUBG is a hell of a game, Krafton has done such a great job with it The kernel has newer mali graphics driver (R26P0 -> R31P0), maybe that could've done the trick (or it may just be due to LineageOS being much, much lighter than One UI)
How is the battery? While I wasn't able to find any abnormal battery drains (both in standby and stress conditions), I'm concered about how it would perform in other devices.

NuzzaimStark said:
Successfully Flashed! Everything work fine.
Model- A217f /DS
U6 binary ,Android 11 latest.
Note: Encountered some problems when I flash (vbmeta) ie, its because of its only for u5.
Odin showed failed at last ,
Phone was unable to boot but
By using hijacking software , bootloader was again running . but when auto reboot lineage recovery was automatically loaded, and tryed your above steps and everything working fine,
Note: pubg is very very better in this ROM.
Close range is also better.
Thankyou grccorps .
Click to expand...
Click to collapse
Can you be a little more specific? my phone U6 but idk how to flash recovery can or you give me email so i can exchange?

Phuc230204 said:
Can you be a little more specific? my phone U6 but idk how to flash recovery can or you give me email so i can exc(hange?
Click to expand...
Click to collapse
First look on A21s LineageOS 18.1

hi,so i get this message "only official released binaries are allowed''in download mode,after the vbmeta failed...
SM-A217F/DSN
and in frp hijacker i get ''check device connection or com ports''

Update:so i succeded to hijack my phone after the error but it wouldn't boot into recovery,and i got everytime a screen with a warning that my phone is not using samsung's official software,and when i press the power button to continue,like it shows,it boots automatically into android.
So what should i do?
And do i need root to do this?

General [GUIDE][UNBRICK] Realme 8 Unbrick/Upgrade/Downgrade [RMX3085]

Hello everyone! So after the new MediaTek DAA and SLA protection bypasses you can find GitHub repo of here , using the bypass we are able to use SPFlash Tool, here is a guide how you can do it! This guide is for RMX3085 (Realme 8) ONLY. DON'T DO ANY OF THESE IF YOU HAVE SOMETHING ELSE!
ALWAYS USE DOWNLOAD ONLY MODE OF SP FLASH TOOL.
DON'T TOUCH ANYTHING RELATED TO FORMAT ON SP FLASH TOOL! (IT'S WRITTEN EVERYWHERE, YOU WILL LOSE YOUR IMEIS IF YOU USE FORMAT ALL + DOWNLOAD. YOU ARE SAFE IF YOU USE DOWNLOAD ONLY.)
Requirements:
PC or Laptop
Internet connection
Realme 8
USB cable
Windows Method
Requirements:
Bypass Tools Pack - (DRIVER AND BYPASS FILES)
SP Flash Tool
Decrypted OFP (OPPO FIRMWARE PACKAGE) :
Indian
A.22 (Indian) - GDrive
A.24 (Indian) - GDrive
A.26 (Indian) - Gdrive
C.05 (Indian) - GDrive
C.09 (Indian) - GDrive
C.11 (Indian) - GDrive
Global
A.22 (Global) - GDrive
A.24 (Global) - GDrive
A.26 (Global) - GDrive
Install Python from Windows Store
libusb-win32 - Having Issues? Use this.
Get usbdk installer (.msi) from here and install it
Steps:
1) Extract the zip
2) Go to driver folder, find the .inf file right click and press install.
{
"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 this file and install it, after installing power off phone and connect to pc while holding Vol+- (don't leave the buttons after connecting) . You might need this driver as well if it's not detected.
4) Press next, connect your device to PC while holding Vol+- buttons (your device needs to be powered off, and don't leave the buttons) and you will see the mtkdriver down below. Install it.
5) Choose MediaTek USB Port and install it.
6) Then run the brom.bat under Bypass folder.
7) Now power off the phone and connect the phone while holding volume + and - (Don't leave the buttons until the bypass is done)
8) After the above step Go into Flash Tool folder and open the SPFlash tool go to Options>Option
9) Click on Connections and select UART and set Baud Rate to 921600
10) After that choose scatter file and also if not set, set your download-agent. You don't need to select auth file as authorization is disabled. Once you do it, it should look like this. ALWAYS MAKE SURE DOWNLOAD ONLY MODE IS SELECTED! DON'T SELECT OTHER MODES!
Select all the Partitions except opporeserve2 and cdt_engineering. otherwise you will get errors.
*11) If you want to flash super.img partition also then download this scatter.txt file and replace it with the another scatter file which is present in the decrypted firmware folder. After that select it again in sp flash tool.
Again Make SURE "Download Only" is selected. Don't select ANYTHING ELSE! You will lose your IMEIs, Serial Numbers, Capability of Hardware Attestation etc. if you choose "Format data + Download" make SURE you selected "Download Only".
Now, you can start downloading with the button and after that a checkmark will appear. You can reboot your phone and use it like before now! All your userdata will (inevitably) be cleared!
After flashing it should look like this. Download has been complete. Enjoy!
"Congrats Now your Realme 8 is Unbricked "
Credits :
https://github.com/bkerler/ for decryptor and for creating the tool.
If you face any issues write them down below...

Some people having this problem so I want to add one more thing to the guide. If you are not having any issues related to boot then don't follow these steps.
After waiting more then 10 minutes, if it doesn't boot up/bootloop. Or shows DM-Verity corrupt error then do this.
1) Try boot into stock recovery by pressing volume up + power button after that when your screen flashes quickly unpress buttons.
2) Now press volume down + power button, by pressing these you will boot into stock recovery.
3) Go to format option and do a full format.
4) Your phone will definitely boot up after that.

Hi
I would like to ask how you obtained the system for realme 8 in the latest version.
Can you download somehow from your device?

HowWof said:
Hi
I would like to ask how you obtained the system for realme 8 in the latest version.
Can you download somehow from your device?
Click to expand...
Click to collapse
From realme offical site

Could you send a link because there is no information on the Polish realme site

HowWof said:
Could you send a link because there is no information on the Polish realme site
Click to expand...
Click to collapse
Realme 8 Firmware (RMX3085) - Realme Firmware
Realme 8 Firmware RMX3085 Official Flash File (Stock ROM). flash your phone using realme flashtool or MSM Download tool.
realmefirmware.com

if "Brick" occured in rooting process - then can recovery be done without data loss :
Prerequisite: firmware version on the body must the same as downloaded "Decrypted OFP" (as example both is A.22 )
HowTo:
at step of SPFlashing (currently that is 10-th)
- check ONLY next partitions in SPFlash to restore :
PRELOADER RECOVERY VBMETA LK LK2 BOOT
... and NO any of other
(as thats only are touched by currently described rooting processes)

after recovery exist on every boot:
"dm-verify corrupted..."
how to get out of this message?
Reset with clearing data not helps ...

DaLiV said:
after recovery exist on every boot:
"dm-verify corrupted..."
how to get out of this message?
Reset with clearing data not helps ...
Click to expand...
Click to collapse
Wait for 10mins if it didn't boot then.
Format with mtk client
python mtk e metadata,userdata,md_udc

that boots ... BUT
on every boot thet alerts about "corruption"
ok cleared partitions with python...
still the same alert ...

DaLiV said:
that boots ... BUT
on every boot thet alerts about "corruption"
ok cleared partitions with python...
still the same alert ...
Click to expand...
Click to collapse
Try booting into stock recovery and format from there

Ok. format from recovery menu solves ...
now that boots normally =
- no alert
-no boot allowing by pressing key required
good behaviour to see when boot subsystem altered, as at every boot alerted and required to press longer power button to confirm/allow starting ...
interesting, that is something new on mine (device versions) or overall ...

I have it anyway. have you solved it yet? Do I understand correctly?

after doing the insstruction, mine bootlooping and enters recovery mode

XCentrialG said:
after doing the insstruction, mine bootlooping and enters recovery mode
Click to expand...
Click to collapse
Maybe you missed some step. Can u explain ur problem briefly. What u did and what happened.

niki.rsb said:
I have it anyway. have you solved it yet? Do I understand correctly?
Click to expand...
Click to collapse
I Think that is not so solvable /possible if someone decode debug and finds /... but that is quite acceptable for rooting /if you don't want to make illegal spionage and so on/ ... also as if your device will be rooted by someone - you will see alert of changes on boot ... that is good ...
if you are rooted - you must be alerted .
but if you will going to stock rom and have protection - then flashing "stock" (surely without 3 partitions that IMEI-and-so-on-related ) and then format from recovery menu helps return to "factory" operation

Tony Stark said:
Maybe you missed some step. Can u explain ur problem briefly. What u did and what happened.
Click to expand...
Click to collapse
just a casual day to update my firmware, reboot and my phone refused to boot anymore, and then i came here, following all the steps very carefully (i read every steps twice so i dont make any mistake), and no luck.

XCentrialG said:
just a casual day to update my firmware, reboot and my phone refused to boot anymore, and then i came here, following all the steps very carefully (i read every steps twice so i dont make any mistake), and no luck.
Click to expand...
Click to collapse
There should be some mistake in your process. Because this guide is working and tested by many people.

Does global firmware have realme dialer instead of google dialer?
Can I flash Global firmware my indian device?

on your firmware package, it does not flashes super.img by default. Because in scatter file
- partition_index: SYS48
partition_name: super
file_name: super.img
is_download: false
changing false to true helps fixing destroyed super partition