I have a rooted Moto G8 Plus with stock ROM. And today I was trying to remove Cerberus, which I had installed as an hidden system app with root.
When hidden, Cerberus is shown as an application "System Framework". But I had troubles getting it removed the normall way, so I've tried my chances with "System app remover" from the app store.
I had removed this "System Framework" app. but then after checking I noticed that it was still there in the app menu, and that it had another install size of the one I had removed. My phone was still working so no problems so far. Unless I've decided to reboot. Now it's stuck on start up. So it seems I accidentally had removed the wrong app called "System Framework", not being aware of it that there was another one of it.
Seems I'm stuck on a "Fastboot Flash Mode (Secure)" acreen now, asking to connect a USB data cable.
{
"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"
}
Does annyone knows how to repair this and acces still acces my phone and data?
Thanks in advance!
- connect phone in fastboot mode usb to PC
- install Android Bootloader Interface drivers
- download platform-tools
- download TWRP recovery
- type in cmd.exe
Code:
fastboot devices
fastboot boot twrp-3.4.0-0-doha-mauronofrio.img
- decrypt /data (unlock pin/pattern)
- create backup of /data from menu
- install Android ADB Interface drivers
- pull all files /sdcard to PC
Code:
adb devices
adb pull -a /sdcard
- flash /system_image
Thanks!
This is for copying content from the internal memory to a PC?
Could I also repair it by reloading "System Framework" and acces the phone and my data in a normall way too?
Still have the same image somewhere on my PC that I've used to flash with while booting. Could I still do something with that?
you can try anything you want - after you saved that backup to PC
Yes, you're right with that. Maybe it's the safest step to do first.
I'm no pro with ADB etc. Just used it once in a while to root evices and needed somekind of guides then first.
But this: "adb pull -a /sdcard" is copying the internal storage to the PC? Where is it getting coppied to? I suspose somekind of default dir in C:\ or so?
right. you can specify target path as last argument. with no path given, current dir is used.
type 'adb help' for usage
Code:
device commands:
adb push <local>... <remote>
- copy files/dirs to device
adb pull [-a] <remote>... <local>
- copy files/dirs from device
(-a preserves file timestamp and mode)
I'm somehow a bit stuck.
I've managed to do the first part. Everything was still installed and the TWRP image was the same as used the first time. Still had the file of it in the Fastboot folder.
After doing the first part:
Code:
fastboot devices
fastboot boot twrp-3.4.0-0-doha-mauronofrio.img
My cmd screen shows that the file is uploaded and that that the phone is restarting. The phone actually restarts.
And it returns to the fastboot screen of the image above.
But after that I'm stuck.
I think the seccond part is about the TWRP configuration?
But it seems I'm not able to enter TWRP.
Powering on while holding volume-up and power is not doing annything. And when selecting "recovery mode" from fastboot it's resulting in a black screen with an Android with the text "no command"
Rockel said:
And it returns to the fastboot screen of the image above.
Click to expand...
Click to collapse
Do you mean fastbootd from within TWRP? Or did you mean it simply returned to normal fastboot mode (fastboot boot didn't work)?
aIecxs said:
Do you mean fastbootd from within TWRP? Or did you mean it simply returned to normal fastboot mode (fastboot boot didn't work)?
Click to expand...
Click to collapse
It returns to this screen when selecting "recovery mode":
I got confused with the word 'image' for 'picture' please use latest platform-tools from link above. the no command screen is part of stock recovery. booting with Volume key won't work, it requires TWRP to be installed in boot.img recovery_ramdisk (you don't have)
in case fastboot boot cmd is not working, this leaves no option other than flashing TWRP into boot partition. however, this will soft-brick device until boot.img is restored. do you still have magisk patched boot.img matching current buildno?
Code:
fastboot getvar ro.build.fingerprint
Well yes, but "volume-down & power" was used to enter fastboot mode if I remember correctly. And I thought I was accesing TWRP with "volume-up & power. So when I suppose I should be able to enter TWRP this way now when everything should have been ok?
I'm still having a stock ROM on my PC, it's from this specific phone and I believe I've used it for rooting back then.
Fastboot is displaying XT2019-1, which is a common name of my backed up ROM file on the PC. So I asume it's the same. I believe I even had to use this file for the unlock proces.
wait.. you already installed TWRP before the bootloop?
Yes, I had completely rooted my phone. Unlocked bootloader, installed exactly the same TWRP version as you linked above and used it to load Magisk.
The only thing I've done so far now is accidentally removing the real "System Framework" which had started to cause this after reboot, and tried to re-load the exact same version of TWRP as you discribed above.
Still having all the files used in the booting proces. So all the files I use should be exactly te same now.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
ZY227HDV34 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp-3.4.0-0-doha-mauronofrio.img
downloading 'boot.img'...
OKAY [ 0.738s]
booting...
OKAY [ 10.280s]
finished. total time: 11.030s
C:\Program Files (x86)\Minimal ADB and Fastboot>
you are sure you previously installed TWRP already, then you can boot into TWRP recovery with "volume-up & power" (or press + keep holding Vol Up while rebooting from fastboot reboot) then provide lock screen pin/pattern to TWRP so it can decrypt files (TWRP will ask for in case device is encrypted).
in case TWRP is not installed, kindly answer post #10 + following cmds
Code:
fastboot getvar securestate
fastboot getvar verity-state
fastboot getvar current-slot
(please note that Minimal ADB and Fastboot is not recommended anymore, it won't work nice with new fastbootd, for example 'fastboot reboot recovery')
Volume-up & power isn't working. Holding down volume-up while booting with fastboot is also not.
It's 2 years ago already since I rooted this device. But always backup the orriginal files used in the rooting process, just in case I will need them on a later moment.
I'm not working with this fastboot, ADB or TWRP etc on regular base. Therefore I forgot about TWRP and I didn't tried it to enter before post #2. So I can't tell if it was working before reloading TWRP through fastboot. However I do not know if loading the exact same version of TWRP using fastboot is causing something to brick?
When using the code in post #10 it shows me:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar ro.build.fingerprint[0]
(bootloader) ro.build.fingerprint[0]: not found
getvar:ro.build.fingerprint[0] FAILED (remote failure)
finished. total time: 0.116s
When using codes in post #14:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar securestate
securestate: flashing_unlocked
finished. total time: 0.003s
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar verity-state
verity-state: enforcing (0)
finished. total time: 0.007s
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar current-slot
current-slot: a
finished. total time: 0.001s
Note that fastboot boot cmd only boot file from PC, it does not install anything.
kindly check what files you have on PC
✓ boot.img
✓ magisk_patched.img
✓ twrp-3.4.0-0-doha-mauronofrio.img
if not, try to get buildno without [0] maybe?
Code:
fastboot getvar ro.build.fingerprint
Oh this code did not install or overwrite annything?
Code:
fastboot boot twrp-3.4.0-0-doha-mauronofrio.img
I notice the "boot" command now in it. I thought it was installing/ overwriting TWRP.
I still have the following files on my PC:
Magisk:
- boot.img
- magisk_patched.img
Others:
- twrp-3.4.0-0-doha-mauronofrio.img
- XT2019-1_DOHA_RETEU_10_QPI30.28-Q3-28-26-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Without [0] worked
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar ro.build.fingerprint
(bootloader) ro.build.fingerprint[0]: motorola/doha_reteu_n/doha_n:10/QP
(bootloader) ro.build.fingerprint[1]: I30.28-Q3-28-26-3/a320d:user/relea
(bootloader) ro.build.fingerprint[2]: se-keys
ro.build.fingerprint: Done
finished. total time: 0.022s
good, buildno matches the already downloaded stock ROM. then most likely the files are matching, too. let's start with flashing...
first flash TWRP into boot partition. then reboot phone, it now has no way to boot into android anymore, but will boot into TWRP instead.
use current-slot: a
Code:
fastboot devices
fastboot flash boot_a twrp-3.4.0-0-doha-mauronofrio.img
fastboot reboot
TWRP will now ask for pin/pattern (if required)
first thing to do in TWRP, restore boot partition from adb to restore its bootable state.
(may require adb drivers re-installed)
Code:
adb devices
adb push magisk_patched.img /tmp
adb shell
# dd if=/tmp/magisk_patched.img of=/dev/block/bootdevice/by-name/boot_a
# exit
now you've been temporary booted into TWRP. you can now proceed with backup (post #2).
for installing TWRP, download Magisk, add suffix zip to file name, then install this order (I recommend older previously installed Magisk version, latest is not always best):
Code:
adb devices
adb push boot.img /tmp
adb push twrp-3.4.0-0-doha-mauronofrio.img /tmp
adb push Magisk-v25.2.apk.zip /tmp
adb shell
# dd if=/tmp/boot.img of=/dev/block/bootdevice/by-name/boot_a
# echo 'KEEPVERITY=false' >/cache/.magisk
# echo 'KEEPFORCEENCRYPT=true' >>/cache/.magisk
# exit
(last line depends wether phone is currently encrypted or not)
1) install TWRP into stock boot ramdisk via TWRP menu (refer to TWRP Other Install guide)
- TWRP > Advanced > Install Recovery Ramdisk
- navigate to /tmp, choose twrp-3.4.0-0-doha-mauronofrio.img
- swipe to install TWRP
2) Now re-install Magisk into boot partition
- TWRP > Install
- choose /tmp/Magisk-v25.2.apk.zip
- swipe to install
assuming everything went well, you have successfully installed TWRP and should now be able to boot into TWRP recovery with Volume Up + Power Buttons any time*
*use TWRP A/B Retention Module on each OTA/Magisk update to preserve TWRP ramdisk in both slots
Ah thanks!
Yes, it should actually be the same ROM as was installed on the phone at the moment. Can't remember exactly, but I needed it in the root proces. I believe for unlocking. That's why I still have the file on my PC. Should be exactly the same.
I see I was using the wrong term "loading" before. But (re) flashing (the same version) TWRP or anything else does still keep the data intact or accessable (if still the case)?
Retrieving the data has my priority now. Since I already have a new phone. So "unbricking" is less important now. Although it will be necessary to retrieve the data I suppose.
the goal is to backup data. it depends on
- TWRP is booting
- device is encrypted or not
- TWRP is able to decrypt or not
in case something does not work, we still have other options without TWRP
Related
Hi there,
I'm new to all things development. I have an HTC Sensation on Virgin mobile in Canada. I am trying desperately to root my phone and I have followed this guide (http://forum.xda-developers.com/showthread.php?t=1632553). I've done lots of searching on this forum and google and can't find anyone with my specific problem.
I have put the SupperSU.zip file into my SD root, unlocked my bootloader through the HTC dev website and flashed CWM using the One X program. However, when I try to boot into recovery it stalls on the white HTC loading screen. I have tried to boot into recovery using One X, a command control from my android folder on my computer and using the power button and down volume button but it always stalls. Since I cant boot into recovery I cant use CWM flash the SuperSU.zip, which I understand finishes the rooting process.
Also: I am pretty sure my drivers are up to date but when I tried to install the drivers from One X it always interrupts the installer saying the Device is in Use...andnI dont know if that means my phone (which its not) or my computer. I uninstalled my antivirus because I read that might be blocking it... but still no luck!
I would really appreciate any help or guidance you can offer! I am a complete newbie when it comes to this and I have done my best to search out answers and tutorials before coming here for help.
reflash the recovery.img using the fastboot command(rename it as recovery.img)
fastboot flash recovery recovery.img then do
fastboot reboot bootloader
after that try to enter to recovery
note:i assume you know how to use fastboot commands
if you still can't enter to recovery then try this
place the recovery.img in the folder where you have adb and fastboot files
boot the device to bootloader and connect it to pc via usb(in the hboot screen must say fastboot usb)
open in the folder a cmd window and do
fastboot reboot recovery.img
rzr86 said:
reflash the recovery.img using the fastboot command(rename it as recovery.img)
fastboot flash recovery recovery.img then do
fastboot reboot bootloader
after that try to enter to recovery
note:i assume you know how to use fastboot commands
if you still can't enter to recovery then try this
place the recovery.img in the folder where you have adb and fastboot files
boot the device to bootloader and connect it to pc via usb(in the hboot screen must say fastboot usb)
open in the folder a cmd window and do
fastboot reboot recovery.img
Click to expand...
Click to collapse
Thanks for your advice! I just want to double check what you mean before I try anything.. Do you mean that I should rename the fastboot file to 'recovery.img' and then use the fastboot commands (by holding shift and right click on my android folder to open command folder)? I am really quite new an d I think I know how to use fastboot commands but I'm not positive. I'm not sure where to find the recovery.img file!
I'm a complete beginner and I'm really trying to understand this Thanks for being patient and helping!
kellai15 said:
Thanks for your advice! I just want to double check what you mean before I try anything.. Do you mean that I should rename the fastboot file to 'recovery.img' and then use the fastboot commands (by holding shift and right click on my android folder to open command folder)? I am really quite new an d I think I know how to use fastboot commands but I'm not positive. I'm not sure where to find the recovery.img file!
I'm a complete beginner and I'm really trying to understand this Thanks for being patient and helping!
Click to expand...
Click to collapse
exactly as you said
about recovery.img use the one from the guide you used to root the device(CMW 5.8.0.9 )
or check 4ext recovery from this guide
http://forum.xda-developers.com/showthread.php?t=1631861 (step 2)
rzr86 said:
exactly as you said
about recovery.img use the one from the guide you used to root the device(CMW 5.8.0.9 )
or check 4ext recovery from this guide
http://forum.xda-developers.com/showthread.php?t=1631861 (step 2)
Click to expand...
Click to collapse
So when I renamed my CMW recovery file as recovery.img and put it in my android folder, booted my phone into fastboot usb mode and connected it to my pc. I opened a command window from the android folder with the recovery.img file in it and typed fastboot reboot recovery.img all I got was this:
C:\android>fastboot reboot recovery.img
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
What should I do now? Thank you again!!
--
I also tried to open a command window there and reflash the recovery.img by typing fastboot flash recovery recovery.img ...except it said "error: "cannot load recovery.img" except the file is definitely in that folder and named recovery.img
kellai15 said:
So when I renamed my CMW recovery file as recovery.img and put it in my android folder, booted my phone into fastboot usb mode and connected it to my pc. I opened a command window from the android folder with the recovery.img file in it and typed fastboot reboot recovery.img all I got was this:
C:\android>fastboot reboot recovery.img
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
What should I do now? Thank you again!!
Click to expand...
Click to collapse
try this
fastboot boot recovery.img
rzr86 said:
try this
fastboot boot recovery.img
Click to expand...
Click to collapse
I tried that but it keeps saying - Cannot Load "recovery.img" and I know that the file is in the folder I'm opening the command window from and named recovery.img .
kellai15 said:
I tried that but it keeps saying - Cannot Load "recovery.img" and I know that the file is in the folder I'm opening the command window from and named recovery.img .
Click to expand...
Click to collapse
ok then flash it again with fastboot command
don't use the tool
then from bootloader select recovery
rzr86 said:
ok then flash it again with fastboot command
don't use the tool
then from bootloader select recovery
Click to expand...
Click to collapse
Sorry - can you explain exactly how and what I should flash again? I'm just a little unclear.
kellai15 said:
Sorry - can you explain exactly how and what I should flash again? I'm just a little unclear.
Click to expand...
Click to collapse
as you are in the folder with cmd window opened do
fastboot flash recovery recovery.img
fastboot reboot bootloader
then from bootloader select recovery
i assume you still have the recovery.img in the folder
rzr86 said:
as you are in the folder with cmd window opened do
fastboot flash recovery recovery.img
fastboot reboot bootloader
then from bootloader select recovery
i assume you still have the recovery.img in the folder
Click to expand...
Click to collapse
That worked!! I realized I had renamed the recovery file 'recovery.img' instead of just 'recovery)" (the second .img was redundant) which is why it wouldnt find the file. Anyway, it's rooted now!
You are the best! Thanks so much for helping a newbie out
kellai15 said:
That worked!! I realized I had renamed the recovery file 'recovery.img' instead of just 'recovery)" (the second .img was redundant) which is why it wouldnt find the file. Anyway, it's rooted now!
You are the best! Thanks so much for helping a newbie out
Click to expand...
Click to collapse
congratulations mate
but i suggest you to have 4ext recovery instead of cwm because of the smartflash feature(for S-ON devices only)
as i understand you are on S-ON
rzr86 said:
congratulations mate
but i suggest you to have 4ext recovery instead of cwm because of the smartflash feature(for S-ON devices only)
as i understand you are on S-ON
Click to expand...
Click to collapse
I have now flashed 4ext and installed a customROM! Couldn't have done it without your help
Hi i use this rom http://forum.xda-developers.com/moto-g/development/stable-aosp-caf-t3284323
and i have a problem , my phone rebooted and stuck after the boot animation in a black screen.
I tried wipe cache , nothing and then i tried fix permission and now i cant go into my recovery , restarts itself, flassed revovery again , same thing.
Now i want to flass the rom with fastboot , what wipe commands i have to do?
I found online this
fastboot erase system -w
fastboot erase boot
fastboot update rom.zip
is this ok?
Thanks
[email protected] said:
Hi i use this rom http://forum.xda-developers.com/moto-g/development/stable-aosp-caf-t3284323
and i have a problem , my phone rebooted and stuck after the boot animation in a black screen.
I tried wipe cache , nothing and then i tried fix permission and now i cant go into my recovery , restarts itself, flassed revovery again , same thing.
Now i want to flass the rom with fastboot , what wipe commands i have to do?
I found online this
fastboot erase system -w
fastboot erase boot
fastboot update rom.zip
is this ok?
Thanks
Click to expand...
Click to collapse
I literally JUST unbricked my Moto G XT1032 after searching for a long while and piecing instructions together. Here's how:
PREPARATIONS
1) Download XT1032_RETAIL-BR-SS_4.4.4_KXB21.14-L1.40_42_cid12_CFC_1FF.xml.zip
This is the stock firmware you need to flash. I haven't tried it with anything else. The instructions that follow are specific to this file, although you should be able to follow the general idea to install different ROMS.
Get the firmware (or a different one) here: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
2) Ensure that you also have the correct Motorola drivers for this phone. Download 32-bit or 64-bit versions depending on your PC.
Get them here http://forum.xda-developers.com/showthread.php?t=2550635
3) Download MFastBoot v2
Go to http://forum.xda-developers.com/gen...ng-mfastboot-exe-to-unbrick-motorola-t3203518
or simply download the file at (https://mega.nz/#F!xUh10AAD!5NvRwDf6eAfjE3bUWZfk7g)
Note: From what I've experienced, you CANNOT use normal Fastboot on this phone. You will keep getting errors such as Failed (remote failure). You have to use MFastBoot.
Open the downloaded file. There will be two other zip files inside it. Extract all contents of mfastboot-v2.zip to a folder of your choice.
4) Download TWRP Recovery. It's usually a good idea to have a recovery, even though it's not used to flash the ROM.
Get the highest version of it here: https://dl.twrp.me/falcon/
Extract the .img file to the SAME folder as where you extracted mfastboot and rename it to twrp.img (not really necessary, but it's easier to type into the command prompt).
5) Extract all contents of XT1032_RETAIL-BR-SS_4.4.4_KXB21.14-L1.40_42_cid12_CFC_1FF.xml.zip to the SAME folder as where you extracted mfastboot.
6) Ensure the phone is off. Hold VOL DOWN first, and then press POWER button for about 5 seconds, then release POWER button before releasing VOL DOWN. You should be in fastboot mode. Plug the USB cable into the phone now.
If you see Device is locked. Status 0, follow the instructions in the UNLOCKING THE BOOTLOADER section.
If you see Device is unlocked. Status 3, continue to step 7.
FLASHING THE FIRMWARE
7) Open the folder where everything has been extracted to.
Hold CTRL+Shift and right click in an empty area of the folder. You will see a normally hidden option to "Open Command Window Here". Select that option and a command prompt window will open. If you are not seeing this, you may not have administrative rights on your account.
Type this into the command prompt: mfastboot reboot
I'm unsure if this is required or not, but mfastboot wouldn't work unless I rebooted it from the command prompt before any other instruction.
8) This is the step where the TWRP recovery and ROM files are flashed.
Type the following into the command prompt, pressing enter after each line. Alternatively, just copy each line and right click>paste into the command prompt. Credits to AgentChaos for the following:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot flash recovery twrp.img
If you used normal fastboot at this step, it will fail and give you an error of "Failure (remote failure)". or it will say it could not find or write to some directory.
Hopefully it does not fail, and should say OKAY after writing each file. This step will take several minutes.
If you used a different firmware than I did, you will have to flash the correct files to the correct directories, and they MAY be different than the ones listed above. I think (but I am not sure) that the only difference would be having to flash and additional sparsechunk.3 or 4. I would not suggest doing this if you aren't sure.
After all files have been flashed, do one final mfastboot reboot and press VOL DOWN and select Recovery, then press VOL UP to start it. You should see the TWRP recovery screen. The screen may glitch out but otherwise be operable. You can press REBOOT then SYSTEM to start the phone normally.
I hope this has been helpful.
UNLOCKING THE BOOTLOADER
A) Open the folder where everything has been extracted to.
Hold CTRL+Shift and right click in an empty area of the folder. You will see a normally hidden option to "Open Command Window Here". Select that option and a command prompt window will open. If you are not seeing this, you may not have administrative rights on your account.
Connect the USB and type this into the command prompt: mfastboot oem get_unlock_data
You will see a string of characters that looks like:
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
B) Go to Motorola's unlocking bootloder tool website here:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
You will need to create an account with a legitimate email account, which takes 1-2 minutes.
There is a text box on Motorola's site where you need to type the exact combined code you received from top to bottom with symbols included, but don't include "(bootloader)". Agree to their terms and services.
C) You will receive an email with your bootloader unlock code.
Go to the command prompt and type: mfastboot reboot to reboot the device. Alternatively, just reboot it manually.
Type: mfastboot oem unlock UNIQUE_KEY where UNIQUE_KEY is the unlock code you received. The screen should go black and you should see the word "Unlock...". The phone may stop responding at this point, in which case simply wait 1-2 minutes to ensure it is finished doing what it was doing, and then manually reboot it.
Boot into fastboot again and now your device should say "Device is unlocked. Status 3"
Hi Team,
I was able to unlock the bootloader on motg3 and do a twrp img. However when I ran the command
adb reboot recovery it doesn't boot into the recovery img and it just says no command on the phone screen. Please help.
Thanks,
Arun
'No Command' means you've still got the stock recovery. Flash TWRP again by:
Code:
fastboot flash recovery twrp.img
(Where twrp.img is the filename of the custom recovery).
Do *not* reboot the phone into system, instead scroll down to select 'recovery' and press power button to load TWRP.
TWRP should load now, swipe to confirm modification (important). Now go to reboot>recovery. Allow the phone to reboot back to TWRP. Now you can select reboot>system and TWRP shall stick permanently.
Broadcasted from Zeta Reticuli
Volume buttons aren't working on the mobile. So I tried adb reboot recovery. But still it didn't boot into recovery. Here is what I had tried.
https://pasteboard.co/HhTTVr1n.png
TWRP will be overwritten by stock recovery if the system is booted up before booting TWRP once.
If the volume buttons are broken, then I'd suggest you first copy twrp.img into phone memory, boot the recovery by :
Code:
fastboot boot recovery.img
Allow modifications, then go to Install>Select Image (img), browse twrp.img on phone>select 'recovery' and swipe to flash.
Now reboot>recovery and then reboot>system. Now it should stick.
I'd recommend being extra careful if your volume button, especially volume down button is broken. If you somehow end up with a non-booting phone, you'd have no way (that I know of) to get to the bootloader mode.
Broadcasted from Zeta Reticuli
I tried fastboot boot recovery.img but it says waiting for device and nothing happens.
https://pasteboard.co/HhVmOD9.png
Make sure your phone is in the bootloader mode and is being recognized by the pc. Run:
Code:
fastboot devices
and make sure it returns with 1 entry of the device along with the text 'fastboot'. Then the command should work.
Broadcasted from Zeta Reticuli
arunkumar413 said:
Hi Team,
I was able to unlock the bootloader on motg3 and do a twrp img. However when I ran the command
adb reboot recovery it doesn't boot into the recovery img and it just says no command on the phone screen. Please help.
Thanks,
Arun
Click to expand...
Click to collapse
Make sure you have installed proper Motorola drivers & Fastboot on you're PC / laptop,
You can get those files from this thread https://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
After installing proper drivers goto this thread https://forum.xda-developers.com/2015-moto-g/orig-development/twrp-twrp-moto-g-2015-t3170537 download & flash latest twrp by given instructions by OP..
I just checked the usb drivers page but there aren't any usb drivers for Linux.
https://mobilesupport.lenovo.com/us/en/solution/MS88481
I tried the command sudo fastboot boot recovery.img and it returned there is no such file or directory. Should recovery file be on phone or on the laptop. Also should all these commands be run from a specific folder either on phone or system?
[email protected] ~ $ sudo fastboot boot recovery.img
cannot load 'recovery.img': No such file or directory
[email protected] ~ $
arunkumar413 said:
I just checked the usb drivers page but there aren't any usb drivers for Linux.
https://mobilesupport.lenovo.com/us/en/solution/MS88481
I tried the command sudo fastboot boot recovery.img and it returned there is no such file or directory. Should recovery file be on phone or on the laptop. Also should all these commands be run from a specific folder either on phone or system?
[email protected] ~ $ sudo fastboot boot recovery.img
cannot load 'recovery.img': No such file or directory
[email protected] ~ $
Click to expand...
Click to collapse
Yes, the terminal should be open to the directory containing the recovery.img file. For simplicity, place twrp into your home folder. The default location for most terminals is home, so no worries about directory now.
Just to be sure, type in :
Code:
ls
(LS lowercase)
Your file should be in the list. You are ready to flash now.
Try the fastboot boot command again.
As you're using GNU/Linux (guessed it early from your screenshots), drivers should not be a problem, at least for this device; unless you are running a minimal or highly customised distro like Gentoo or Arch.
Note: And yes, you'll need another copy of TWRP inside phone storage to actually flash into the device, the PC one is just used to boot temporarily into TWRP.
Broadcasted from Zeta Reticuli
To add more clarity. There are two files here:
1) recovery.img
2)twrp.img
I was able to get the twrp.img file but where do I get the recovery.img file?
Hi All,
Thanks for all the help. I'm now able to root into the device.
arunkumar413 said:
To add more clarity. There are two files here:
1) recovery.img
2)twrp.img
I was able to get the twrp.img file but where do I get the recovery.img file?
Click to expand...
Click to collapse
I apologize for confusing you. They are the one and same. Just rename the downloaded TWRP img file to twrp.img and copy it over to both home folder in pc and into phone.
Use fastboot boot command on pc to temporarily boot up twrp in phone, allow modifications by swiping, go to Install>Install Image (img) option on the bottom>select the twrp.img inside the phone and flash it to 'recovery' partition.
Now reboot>recovery. This time the twrp should be permanently flashed and working properly. You are done.
Edit: Didn't see your last post, glad that you worked it out
Broadcasted from Zeta Reticuli
arunkumar413 said:
To add more clarity. There are two files here:
1) recovery.img
2)twrp.img
I was able to get the twrp.img file but where do I get the recovery.img file?
Click to expand...
Click to collapse
There can be only one either recovery.img file or twrp.img.....as you are trying to replace your stock recovery by TWRP... And you need .img file for this.... Just check the name there should be just one if you have TWRP.img then there is no need for recovery.img file
Hi All,
After I was able to flash twrp and root into the phone I switched off the phone and turned on after couple of days. But now the display isn't turning on. However adb is able to detect the device and also I was able to access the file system through usb. Could you please help me troubleshoot the display issue?
arunkumar413 said:
Hi All,
After I was able to flash twrp and root into the phone I switched off the phone and turned on after couple of days. But now the display isn't turning on. However adb is able to detect the device and also I was able to access the file system through usb. Could you please help me troubleshoot the display issue?
Click to expand...
Click to collapse
Try rebooting into the recovery mode by:
Code:
adb reboot recovery
And doing a Cache/ART cleanup.
If the phone boots up (it should vibrate) but the screen doesn't light up (not even a blank dark grey screen), then I'm afraid the display is at fault.
How to root moto g3
I try to root my motor but network has gone
Then how I root
Hi guys,
On this post I will share with you a method to root Wiko Jerry.
You will get a TWRP recovery installed too.
Sorry if my english is a bit bad
Sorry if the print screens if you find are in Portuguese, as it would be boring to change my Windows language.
DISCLAIMER:
I AM NOT responsible for bricked devices and lost warranties.
If you don't feel safe modifying your device DO NOT do anything.
Backup the data you have on your phone. Accidents can happen.
That said, let's go to the fun!
What you need:
Your Wiko Jerry
This TWRP 3.1.1 recovery: https://mega.nz/#!rZM2XIhY!tuneB9pGNQzhbGWz1kRY-mzeCGtRjUAP2QqX791r4Go
ADB / Fastboot on your computer. I will explain how to set it up on your PC later.
Magisk flashable ZIP. Magisk thread: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Connect your phone to your PC with your USB cable.
1- Preparing your PC:
If you already have ADB on your PC, you can skip this part.
After downloaded the files you need, let's get your computer ready.
You will need fastboot and ADB for this method, so download from here:
Installing ADB on Windows:
Open this link and click on SDK Platform-tools for Windows.
After downloaded, extract the ZIP anywhere you want.
You should now have a folder 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"
}
Keep the folder open (or just minimize it) and go ahead to the next step.
Installing ADB on Linux:
Run one of this commands on your terminal.
-Ubuntu/Debian based Linuxes (APT):
Code:
sudo apt install android-tools-adb android-tools-fastboot
-Fedora (YUM):
Code:
sudo yum install android-tools
Test with:
Code:
sudo adb version
You should get something like this:
Code:
Android Debug Bridge version 1.0.40
Version 4986621
2- Getting your phone ready:
To get your phone ready you need to enable ADB on Settings.
Open Settings>About phone and tap "Buid number" 7 times.
Go back one time and you sholud get a "Developer options" menu on Settings.
Open the "Developer options" and enable "USB debugging" option.
Now you have ADB enabled on your device.
3- Installing TWRP on your phone
Do you remember the TWRP file you downloaded before? Now you will need it.
-Copy the TWRP_3.1_JERRY.img file to your platform-tools folder.
-Rename the file to recovery.img.
-Open a command prompt.
-On command prompt do this to open your platform-tools folder on it:
Code:
cd INSERT PATH TO YOUR platform-tools FOLDER
Now, unlock your phone and run this command:
Code:
adb devices
It should appear something like this on your PC:
Code:
List of devices attached
<your-device-id> offline
And this on your phone:
On that window, check the box and tap OK. This will allow your phone to communicate with ADB running on your PC.
Check if everything is ok doing the "adb devices" command again. If it is ok, this will show up:
Code:
List of devices attached
<your-device-id> device
Now, on your command line run the command:
Code:
adb reboot-bootloader
Your phone will reboot in fastboot mode. It should look like this:
Run this on your command line:
Code:
fastboot flash recovery recovery.img
If you get <waiting-for-device> on command prompt, check this:
-Open Device Manager (Win key+X, click on Device Manager)
-Find a device called "fastboot Gadget" or similar name with a exclamation mark.
-Right click it and click on "Update drivers..."
-Click on second option on the setup (search manually)
-Click on the second option again.
-On the list, look for Universal Serial Bus Devices and double click it
-Inside the Manufacturer list select WinUsb Device
-On the right list select ADB Device and double click it
-Click on yes
-After installed, close and its fixed!
When the command finishes, you should get this:
Code:
Sending 'recovery' (12866 KB) OKAY [ 0.550s]
Writing 'recovery' OKAY [ 0.762s]
Finished. Total time: 1.317s
Congratulations! Now you have TWRP on your phone!
4- Booting into TWRP and root the phone with Magisk
Now you need to turn off your phone. You can just take the battery out and put it again.
This phone has a weird way to boot into the recovery. You need to press the power button and a second later, the VOL+ button.
The Wiko logo will appear and the phone MUST NOT VIBRATE. If it vibrates, the normal Android will start.
Do this procedure anytime you want to go into TWRP.
Connect your USB cable.
Tap "Keep Read Only"
In your PC, go to This PC and open the JERRY device.
Copy the previously downloaded Magisk ZIP file into the Internal Storage.
In TWRP, tap Install
Search for the Magisk ZIP in the file explorer.
Swipe to confirm the flash
Tap Home button
Tap Reboot
Tap System
Android should boot normally
Warning: It could take a few seconds to Magisk Manager to appear on apps list.
Congratulations! You have done it! You have TWRP and Magisk!
help
i always get error remote replacing recovery not allowed something like that
what should i do
edit : its this error
remote: 'download for partition 'recovery' is not allowed
GnarlyBuzzard50 said:
i always get error remote replacing recovery not allowed something like that
what should i do
edit : its this error
remote: 'download for partition 'recovery' is not allowed
Click to expand...
Click to collapse
hey you'll need to unlock your bootloader first
FIRST BACKUP EVERYTHING USEFUL FROM YOUR PHONE, THI WILL FACTORY RESET YOUR DEVICE
after getting adb working (debug on and all that stuff)
enter in your cmd prompt
Code:
adb reboot bootloader
then wait till your phone is in fastboot mode
now you'll type in cmd
Code:
fastboot flashing unlock
read carefully what appears in your phone screen and accapt it (at your own risk, it will probably void your warranty)
now type in cmd
Code:
fastboot reboot
done
TWRP file is not working
Code:
fastboot flashing unlock
Click to expand...
Click to collapse
I get "Unlock Failed"
When I try to enter recovery mode, it says: no command
is this recovery image meant for the SPD or the MTK variant?
Tried this on an SPD Jerry & it didn't work
Any other help?
KitK4t said:
Hi guys,
On this post I will share with you a method to root Wiko Jerry.
You will get a TWRP recovery installed too.
Sorry if my english is a bit bad
Sorry if the print screens if you find are in Portuguese, as it would be boring to change my Windows language.
DISCLAIMER:
I AM NOT responsible for bricked devices and lost warranties.
If you don't feel safe modifying your device DO NOT do anything.
Backup the data you have on your phone. Accidents can happen.
That said, let's go to the fun!
What you need:
Your Wiko Jerry
This TWRP 3.1.1 recovery: https://mega.nz/#!rZM2XIhY!tuneB9pGNQzhbGWz1kRY-mzeCGtRjUAP2QqX791r4Go
ADB / Fastboot on your computer. I will explain how to set it up on your PC later.
Magisk flashable ZIP. Magisk thread: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Connect your phone to your PC with your USB cable.
1- Preparing your PC:
If you already have ADB on your PC, you can skip this part.
After downloaded the files you need, let's get your computer ready.
You will need fastboot and ADB for this method, so download from here:
Installing ADB on Windows:
Open this link and click on SDK Platform-tools for Windows.After downloaded, extract the ZIP anywhere you want.You should now have a folder like this:
Keep the folder open (or just minimize it) and go ahead to the next step.
Installing ADB on Linux:
Run one of this commands on your terminal.-Ubuntu/Debian based Linuxes (APT):
Code:
sudo apt install android-tools-adb android-tools-fastboot
-Fedora (YUM):
Code:
sudo yum install android-tools
Test with:
Code:
sudo adb version
You should get something like this:
Code:
Android Debug Bridge version 1.0.40[/INDENT]
[INDENT]Version 4986621
2- Getting your phone ready:
To get your phone ready you need to enable ADB on Settings.
Open Settings>About phone and tap "Buid number" 7 times.
Go back one time and you sholud get a "Developer options" menu on Settings.
Open the "Developer options" and enable "USB debugging" option.
Now you have ADB enabled on your device.
3- Installing TWRP on your phone
Do you remember the TWRP file you downloaded before? Now you will need it.
-Copy the TWRP_3.1_JERRY.img file to your platform-tools folder.
-Rename the file to recovery.img.
-Open a command prompt.
-On command prompt do this to open your platform-tools folder on it:
Code:
cd INSERT PATH TO YOUR platform-tools FOLDER
Now, unlock your phone and run this command:
Code:
adb devices
It should appear something like this on your PC:
Code:
List of devices attached
<your-device-id> offline
And this on your phone:
On that window, check the box and tap OK. This will allow your phone to communicate with ADB running on your PC.
Check if everything is ok doing the "adb devices" command again. If it is ok, this will show up:
Code:
List of devices attached
<your-device-id> device
Now, on your command line run the command:
Code:
adb reboot-bootloader
Your phone will reboot in fastboot mode. It should look like this:
Run this on your command line:
Code:
fastboot flash recovery recovery.img
If you get <waiting-for-device> on command prompt, check this:
-Open Device Manager (Win key+X, click on Device Manager)-Find a device called "fastboot Gadget" or similar name with a exclamation mark.-Right click it and click on "Update drivers..."-Click on second option on the setup (search manually)-Click on the second option again.-On the list, look for Universal Serial Bus Devices and double click it-Inside the Manufacturer list select WinUsb Device-On the right list select ADB Device and double click it-Click on yes-After installed, close and its fixed!
When the command finishes, you should get this:
Code:
Sending 'recovery' (12866 KB) OKAY [ 0.550s]
Writing 'recovery' OKAY [ 0.762s]
Finished. Total time: 1.317s
Congratulations! Now you have TWRP on your phone!
4- Booting into TWRP and root the phone with Magisk
Now you need to turn off your phone. You can just take the battery out and put it again.
This phone has a weird way to boot into the recovery. You need to press the power button and a second later, the VOL+ button.
The Wiko logo will appear and the phone MUST NOT VIBRATE. If it vibrates, the normal Android will start.
Do this procedure anytime you want to go into TWRP.
Connect your USB cable.
Tap "Keep Read Only"
In your PC, go to This PC and open the JERRY device.
Copy the previously downloaded Magisk ZIP file into the Internal Storage.
In TWRP, tap Install
Search for the Magisk ZIP in the file explorer.
Swipe to confirm the flash
Tap Home button
Tap Reboot
Tap System
Android should boot normally
Warning: It could take a few seconds to Magisk Manager to appear on apps list.
Congratulations! You have done it! You have TWRP and Magisk!
Click to expand...
Click to collapse
<thanks man, worked fine for me.
just like he says...
adb reboot-bootloader
fastboot flash recovery <pathoftherenamedTWRP.img>
Take the battery out, back in
press and hold start button, sec later vol down button too
Now TWRP should start
read only
transfer the magisk.zip file to internal storage(PC)
install button(TWRP, Smartphone)
tap on the magisk.zip file and swipe to accept
wait till its done
press on reboot
done
Zaki4t said:
is this recovery image meant for the SPD or the MTK variant?
Tried this on an SPD Jerry & it didn't work
Any other help?
Click to expand...
Click to collapse
Worked for me. Where can i see which i have. maybe i can help
z0mb13m4ch1n3 said:
Worked for me. Where can i see which i have. maybe i can help
Click to expand...
Click to collapse
and if you messed up(like I do in my first try) here...
Wiko Mobile: Kundenbereich / Verbindung.
customer-de.wikomobile.com
take out the battery, theres the imei number
youll download a .exe file. stressed me in linux and lend a win 7 laptop. 5min or so and i had a factory fresh jerry to try again
The problem is there is no WinUsb there i dont have it.
Hi, I have a big trouble i followed all the instructions and everything was just fine, until the step 4- Booting into TWRP and root the phone with Magisk, after a take out and put the battery again in the cell, it doesn't boot from logo, just reset an reset, I already try o hard reset, try to enter TWRP, I try all kind of button combination, nothing works can someone helpme. Thks...
I recently tried the dumb move of updating Magisk through the app itself. When rebooted it got stuck on bootloop, I then booted to Orangefox on my Redmi K20 Pro. I then did resetting to defaults in settings which showed 2 errors- Unable to mount system root and vendor(invalid arguement something like that) which resulted in my data being encrypted.
When I tried to reboot it said no OS installed. I didn't know what to do so I watched a youtube video instructing to wipe data and rebooting to recovery to fix this(encrypion) and so i did another dumb move of doing it which resulted in my device getting rid of Orangefox then, and now I am stuck on either boot loop with no recovery or in fastboot mode which isn't really doing much since it's not being recognised by my pc.
I am not much of a knower in this side but I knew some of the basics and followed instructions to install recovery and root and now have managed to break it. And now I'm panicking. SOMEONE HELP!!
If you are still able to go into fastboot mode and bootloader unlocked then you need to download firmware or use your back up of firmware then write them in fastboot mode and see it can help. /user might need to be wiped if it is encrypted. /cache maybe need to erase too if phone does not boot.
I don't know if it is you are already installed custom recovery such as TWRP, CWM, if it is installed then you need to flash /system and /boot. if it is not installed, flash /system and /boot and /recovery (or /recovery_ramdisk).
Make sure you have using same version installed firmware you try to flash.
aheadofsingularity said:
If you are still able to go into fastboot mode and bootloader unlocked then you need to download firmware or use your back up of firmware then write them in fastboot mode and see it can help. /user might need to be wiped if it is encrypted. /cache maybe need to erase too if phone does not boot.
I don't know if it is you are already installed custom recovery such as TWRP, CWM, if it is installed then you need to flash /system and /boot. if it is not installed, flash /system and /boot and /recovery (or /recovery_ramdisk).
Make sure you have using same version installed firmware you try to flash.
Click to expand...
Click to collapse
How do I write them in fastboot mode. Pardon but I don't know more technical stuff that much. My pc is unable to detect my phone so how can I write it. And I didn't quite fully understand the rest of it as well. Could you dumb it down?
Watch this video
Shiromani said:
How do I write them in fastboot mode. Pardon but I don't know more technical stuff that much. My pc is unable to detect my phone so how can I write it. And I didn't quite fully understand the rest of it as well. Could you dumb it down?
Click to expand...
Click to collapse
If your device is in fastboot mode
Its should recognised by pc
Check your driver's on device manager
Or download adb drivers
Then download firmware for your device
Fastboot type : fastboot devices
Then drag the flash all bat from flash file on cmd press enter
Note- u must have unlocked bootloader
samsujjamanrifat said:
If your device is in fastboot mode
Its should recognised by pc
Check your driver's on device manager
Or download adb drivers
Then download firmware for your device
Fastboot type : fastboot devices
Then drag the flash all bat from flash file on cmd press enter
Note- u must have unlocked bootloader
Click to expand...
Click to collapse
Update- I manged to install TWRP on my device but it was encrypted so unfortunately had to format data to remove it, but it still aks me to "keep data in red only mode?" Anyhow I ccopied the rom to my internal storage but it still shows the error- Failed to mount system_root and vendor(invalid argument). How do I fix that
Download ADB from Here
Download Xiaomi Redmi K20 Pro USB Driver Here
Install Usb driver
If you using windows then select "Download SDK Platform-Tools for Windows"
If you finished downloading zip file, open zip, then put "platform-tools" folder in C:\
{
"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"
}
Then add "C:\platform-tools" to your environment variables
To add it to environment variables,Ctrl+X, "system details">"environment variables">"User variables"
>"path" variables, add "C:\platform-tools" to "path" variables into the last.
Now you can use adb and fastboot commands everywhere in cmd, but you need to stick with image file, so you need to use Change Directory (cd) command for path of image folder.
Then put all firmware file (img) into platform-tools folder.
If you don't have firmware file go easy-firmware you should pay for it (I am not sure Xiaomi hosting free firmwares)
Ctrl+R then type "cmd" then Enter
In CMD type "cd C:\platform-tools", so you now cmd is looking at where your image files located.
type "fastboot devices"
type "flash-all.bat" or
"fastboot flash system <your system img file name>" / "fastboot flash system_root <your system img file name>"
"fastboot flash boot <your boot img file name>"
"fastboot flash recovery <your recovery img file name>" / "fastboot flash recovery_ramdisk <your recovery img file name>"
"fastboot flash vendor <your vendor img file name>"
"fastboot reboot"
you may need to execute these command too
"fastboot erase user"
"fastboot erase cache"
PS firmware files for Huawei P20 Pro
Filenames should vary but maybe looks like this (I'm not xiaomi user so...)
aheadofsingularity said:
Download ADB from Here
Download Xiaomi Redmi K20 Pro USB Driver Here
Install Usb driver
If you using windows then select "Download SDK Platform-Tools for Windows"
If you finished downloading zip file, open zip, then put "platform-tools" folder in C:\
View attachment 5809235
Then add "C:\platform-tools" to your environment variables
To add it to environment variables,Ctrl+X, "system details">"environment variables">"User variables"
>"path" variables, add "C:\platform-tools" to "path" variables into the last
View attachment 5809249
Then put all firmware file (img) into platform-tools folder
If you don't have firmware file go easy-firmware you should pay for it (I am not sure Xiaomi hosting free firmwares)
Ctrl+R then type "cmd" then Enter
In CMD type "cd C:\platform-tools"
type "fastboot devices"
View attachment 5809239
type "flash-all.bat" or
"fastboot flash system <your system img file name>"
"fastboot flash boot <your boot img file name>"
"fastboot flash recovery <your recovery img file name>" / "fastboot flash recovery_ramdisk <your recovery img file name>"
"fastboot reboot"
you may need to execute these command too
"fastboot erase /user"
"fastboot erase /cache"
PS firmware files for Huawei P20 Pro
Filenames should vary but maybe looks like this (I'm not xiaomi user so...)
View attachment 5809261
Click to expand...
Click to collapse
He made it look easy do that
Shiromani said:
Update- I manged to install TWRP on my device but it was encrypted so unfortunately had to format data to remove it, but it still aks me to "keep data in red only mode?" Anyhow I ccopied the rom to my internal storage but it still shows the error- Failed to mount system_root and vendor(invalid argument). How do I fix that
Click to expand...
Click to collapse
Device system and vendor formated i think
i have no os, how do i flash my custom rom, via adb or normal flash?
Why are you declining follow my tutorial?
@aheadofsingularity do not waste your time at stupid HELP PLEASE!!! threads