Related
Hello everbody,
sadly i can't get into the recovery mode of my sony xperia z5c.
i want to install supersu, but sadly i can't do it without twrp D:
what i did so far:
- i unlocked the bootloader
- i flashed a the newest twrp (3.0.2.0) via fastboot ony my device
- i tried to get into the recovery mode with vol up or down in the boot sequence (but the flashligth never turns blue or orange... or even on at the bootsequence)
- i tried to enter the recovery mode via adb (adb reboot recovery)
sadly nothing worked D:
has anybody a idea what i am doing wrong? D:
thank you for your help
love
acy <3
* Download Latest AndroPlus Kernel From The Below Link:
https://goo.gl/mHJOFN
* Extract the zip file and find boot.img
* Flash the boot.img using cmd and fastboot.
Then,
* Download TWRP Recovery from Below Link :
https://goo.gl/AQ9Edi
* Flash the TWRP Recovery using cmd and fastboot.
* Now Download Latest SuperSu From Below Link :
http://download.chainfire.eu/supersu
* Transfer the file in to the device.
* Now Reboot the device.
* When booting press the volume rockers to access TWRP Recovery.
* Click Install and Flash the SuperSU zip file.
what he said, and also check the Firmware youre on and see which build is it, I think androplus works on .305
(kernel must be compatible withe build number you have)
Code:
#include "std_disclaimer.h"
/*
* Your warranty is now void... Well, probably not.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
* A lot.
*
* Tl;dr: if your device crashes and burns, I'm sorry, but I'm not to be blamed.
*/
Hey guys.
This is a guide on how to install official Android 8.1.0 "Oreo" on our beloved, forgotten, poor Moto G5s (montana). As you all may know, Lenovorola still hasn't released Oreo for everyone worldwide. Only a few Latin American countries are receiving the update, with Brazil due to receive it Soon™, since we've already received the August security patch (still Nougat though :/).
Update 2018.09.29: Brazil and India have also started receiving Oreo, but with a different build (OPP28.65-37-2).
However, this is Lenovorola we're dealing with, so I went ahead, captured the OTA and created a TWRP flashable zip, by patching the June firmware (NPPS26.102-49-11) with said OTA. And also, there's the standard .xml.zip to be used with fastboot, directly from Moto.
For those of you who want to keep everything stock, locked bootloader and all, I recommend going with the fastboot zip. For those who already have unlocked their phone's bootloaders and have TWRP installed, or are coming from a custom ROM but don't want to fiddle around with fastboot, you should use the TWRP flashable zip.
I can't stress this enough. ALWAYS BACK UP YOUR STUFF!!!! Do a TWRP backup (data, system, boot). I recommend backing up the contents of your internal storage as well. And for those willing to downgrade at some point, back up your persist and efs partitions, otherwise you'll lose IMEI!
Oh, and I assume you already have adb, fastboot and the Motorola USB drivers installed. In case you don't...
Motorola USB Drivers
Android SDK Platform Tools (includes adb & fastboot)
If you use Linux, you don't need to install any drivers, but you may have to configure udev to allow fastboot to detect your device. But that, along with telling how to configure adb and fastboot, is beyond the scope of this thread.
I don't know how things work in the Apple side, so kindly don't ask me how to do that on macOS.
This firmware should work on all Moto G5s models (XT1791/2/3/4/5/7). I can't tell if it works on model XT1799-2 (aka Green Pomelo / Qingyou).
A few warnings:
1. Forced encryption has not been disabled. So, if your phone is not encrypted, it will be encrypted again upon the very first boot. Don't interrupt the process, otherwise you'll lose ALL of your data! (You can flash @Zackptg5's dm-verity / forced encryption disabler if you want to)
2. Xposed doesn't work, whether it's installed to /system or via Magisk (systemless). I've already opened an issue on GitHub and am awaiting a reply.
3. (Fastboot only) Updating to this firmware will also update your bootloader and partition table. If you're unsure about that and/or afraid of a possible hard brick, skip the gpt and bootloader lines.
4. Please install the proper build for your software channel. For retbr and retin, use OPP28.65-37-2. For the other channels, go with OPP28.65-37.
5. If your phone's software channel is retbr or retin and you have already flashed the -37 build, you can simply dirty flash the -37-2 build over it. No need to factory reset / fastboot erase userdata.
With that out of the way, let's get to what matters most.
Downloads:
Build OPP28.65-37 (retla):
Fastboot ZIP (Android File Host | MEGA)
TWRP Flashable ZIP (Google Drive)
Click to expand...
Click to collapse
Build OPP28.65-37-2 (retbr & retin):
Fastboot ZIP (Android File Host)
TWRP Flashable ZIP (Google Drive)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Installation Guide:
Fastboot ZIP:
1. Download (obviously)
2. Extract the contents to a folder of your choice
3. Go to the folder which you extracted the files to
3. Inside the folder, open a command prompt, PowerShell, terminal or whatever you use as a command line interface
4. Put your device into fastboot mode if you haven't already done that (just hold Vol Down + Power for a while) and connect it to your PC
5. Execute the following commands:
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
reboot
6. Have fun
Click to expand...
Click to collapse
TWRP Flashable ZIP:
1. Download (duh)
2. Put the file at the root of your internal storage (/sdcard)
3. Reboot to TWRP
4. Do a factory reset (optional if coming from stock Nougat) and then format /system
(If your device is encrypted and you want to remove encryption, you will have to format /data and then flash the forceencrypt disabler I mentioned above after flashing the ROM)
5. Flash the zip
6. Reboot
7. Have fun
Click to expand...
Click to collapse
Thanks to:
@NZedPred for the excellent tutorial on how to build flashable zips based on stock firmware and/or OTAs
@Cesarcami53 for telling us that the update was out for retla
@erfanoabdi for his Motorola OTA Link Generator and IMG Patch Tools
@lohanbarth for mirroring the fastboot zips to AFH / Mega
In case I forgot someone, please do let me know.
F.A.Q. (Read this before crying!!!!)
Q: Why did you come up with this?
A: Because Lenovorola is pulling a Samsung, taking forever to officially deliver the Oreo update to everyone.
Q: ERMAHGERD DIS ROM SUCKZ, MAH BATTERY IS DEAD IN 30 MINS, PLZ HALP!
A: Please do blame Motorola, or yourself, or your apps' developers, but not me. I haven't got anything to do with that. I haven't changed anything.
Q: What works and what doesn't?
In theory, everything should work, and nothing should be broken, since this is a stock ROM.
Q: Will you add feature xyz?
A: No.
Q: Why no inbuilt root/Magisk/xyz/abc?
A: Because not. 1. There's something called freedom of choice, and that must be respected. / 2. I want to keep everything as bit-perfect as possible, and as close as possible to what you would get by flashing a real OTA.
Q: How do I report bugs?
A: If you wanna report a bug, send me a logcat. In case of a kernel panic, /proc/last_kmsg will help.
Q: How do I flash this?
A: I suggest you scroll up and read the OP. The instructions are there.
Q: How do I tweak this ROM?
A: For theming, there's full OMS/Substratum support. Xposed doesn't work, so no extra tweaks for now.
Q: This kid is such a n00b!
A: Oh well then, why don't you go do something like this yourself, instead of criticizing my work and wasting your time?
Reserved again
Oh look! Another reserved post!
And as a bonus, have this nice little dark boot logo from me, which hides that dreaded "N/A" and also "bad key" things. Extract the zip file and flash the logo3.bin file inside using fastboot:
Code:
fastboot flash logo logo3.bin
Good Night Guys, if I install it for twrp will the installation fiddle with the bootloader?
Which security pet
Official or Soak test?
Kamin4ri said:
Thanks to:
@NZedPred for the excellent tutorial on how to build flashable zips based on stock firmware and/or OTAs
[/SIZE]
Click to expand...
Click to collapse
Hey man, I am so thankful that someone has found my guide and made something for another device.
Well done, and best of luck with this thread. :good:
I can tell you that this build work very well in european distribution (reteu).
Basicly everything work including sim and nfc(paying not tested yet)
The link with the Fastboot ZIP doesn't work for me, I guess I'm the unlucky one. Is there any chance that you can upload it elsewhere? Thanks.
Also not able to download, please offer another download Location!
Do I need to unlock my bootloader on Russian type of XT1794 to flash this firmware via PC?
ilovepanda said:
Good Night Guys, if I install it for twrp will the installation fiddle with the bootloader?
Click to expand...
Click to collapse
No. Your bootloader will be updated if, and only if, you install via fastboot and actually execute the respective command.
[email protected] said:
Official or Soak test?
Click to expand...
Click to collapse
This is the official firmware released for retla (Latin America). However, the soak tests in Brazil haven't finished yet. I'll update the OP with the link for the Brazilian firmware as soon as it's available.
NZedPred said:
Hey man, I am so thankful that someone has found my guide and made something for another device.
Well done, and best of luck with this thread. :good:
Click to expand...
Click to collapse
Thank you, friend! I'll be definitely using that guide again.
7opex0 said:
Do I need to unlock my bootloader on Russian type of XT1794 to flash this firmware via PC?
Click to expand...
Click to collapse
Only if you're flashing via TWRP. If you're using fastboot, there's no need to unlock your bootloader, since this is an official firmware signed by Motorola.
giugiura said:
The link with the Fastboot ZIP doesn't work for me, I guess I'm the unlucky one. Is there any chance that you can upload it elsewhere? Thanks.
Click to expand...
Click to collapse
dau999 said:
Also not able to download, please offer another download Location!
Click to expand...
Click to collapse
I have the zip here, but uploading it using my home Internet connection would take ages. I'll do it next Monday, I'll use my university's connection. I can get 100+ Mbps transfer rates, so it should be really quick for a file this size (1.5 GB).
Kamin4ri said:
If you're using fastboot, there's no need to unlock your bootloader, since this is an official firmware signed by Motorola.
Click to expand...
Click to collapse
Okay then! Thanks for information.
7opex0 said:
Okay then! Thanks for information.
Click to expand...
Click to collapse
Not at all!
Kamin4ri said:
I have the zip here, but uploading it using my home Internet connection would take ages. I'll do it next Monday, I'll use my university's connection. I can get 100+ Mbps transfer rates, so it should be really quick for a file this size (1.5 GB).
Click to expand...
Click to collapse
Please upload it on some other cloud so that we can download it thanks for help sir
In advance
# I assume you are confident with ADB and Fastboot commands and you know what you are doing. #
# If you don't, search on Google before messing with your device. #
# I am not responsible for...you know what I mean. On the other hand, please feel free to point out any error in this guide. #
# Lots of useful information can be found on Telegram Group for Mi 9 SE #
# If you already unlocked your bootloader and flashed TWRP, go directly to part 2 of this guide #
PART 1 - UNLOCK DEVICE AND FLASH TWRP
# Before starting, be sure that you can unlock your bootloader and you have these files: #
- Mi Unlock tool (http://en.miui.com/unlock/)
- Minimal ADB & Fastboot 1.4.3 (https://forum.xda-developers.com/showthread.php?t=2317790)
- TWRP recovery for your device (please check the development section).
Install ADB and Fastboot drivers on your PC, if you don't have them already.
- enable developer options on device, allow OEM unlock and ADB debug.
- install Minimal ADB & Fastboot tool and run a command window. PLEASE DON'T USE WINDOWS 10 POWER SHELL. Double click on "cmdhere.dll" in root folder instead.
- move twrp image in the same folder where Minimal ADB & Fastboot is installed.
- for your convenience, rename twrp file as "twrp" only.
- connect your device to your PC USB port, pair it with PC then reboot it to bootloader (power + volume down combo).
Unlock bootloader using Mi Unlock tool (full unlocking guide at https://c.mi.com/thread-1635834-1-1.html)
Unlocking bootloader will erase all of your data, including storage.
Once you unlocked:
- reboot and setup device
- enable developer options again
- double check bootloader status and allow ADB debug
- connect to USB port and pair device with PC for ADB debug bridge then type in command window:
Code:
adb devices
Code:
adb reboot bootloader
once in bootloader screen code:
Code:
fastboot devices
Code:
fastboot flash recovery twrp.img
- don't give fastboot command "fastboot boot recovery twrp" or "fastboot reboot recovery twrp". Just press and hold power+volume up for about 10 seconds to reboot to recovery.
- swipe to allow twrp modifications.
- I would suggest to NOT format data to get rid of encryption unless you actually need it. Encryption does not slow down your device or harm your battery life.
- I would also suggest to NOT wipe system and reboot to recovery because it could lead to a fastboot bootloop.
PART 2 - HOW TO FLASH A GSI ROM
# IMPORTANT #
When flashing a GSI ROM, it is recommended to use a Stable firmware as base.
If device is running different builds, flash latest Global or China Stable before starting using MiFlash tool.
Beware that device could have the anti-rollback enabled, so be careful when flashing another firmware.
Mi 9 SE is a system-as-root device, so you must flash A/B type GSI ROMs.
You will need these files:
- GSI A/B ROM (FlokoROM at https://treble.andro.plus/ or choose one at https://forum.xda-developers.com/project-treble/trebleenabled-device-development)
- vbmeta.img (https://androidfilehost.com/?fid=818070582850505317)
- gapps for Google services (https://opengapps.org/) - select ARM64 - 9.0 - I would suggest nano or pico package.
- magisk for root and modules (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)
- MiFlash flashable STABLE stock firmware (http://en.miui.com/download or https://mirom.ezbox.idv.tw/en/phone/grus/)
- MiFlash tool (https://www.xiaomiflash.com/)
If you are already running a Stable firmware start from here, if you don't, flash a Stable firmware.
- move GSI and vbmeta images in the same folder where Minimal ADB & Fastboot is installed.
- for your convenience, rename GSI file as "system" only.
- reboot device to bootloader, ensure you are connected with your PC properly
- to double check it, run a command window and type:
Code:
fastboot devices
once you get the device recognized type:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
this command will disable dm-verity and AVB on device. PLEASE DON'T USE WINDOWS 10 POWER SHELL to disable vbmeta or you will get an error feedback. Double click on "cmdhere.dll" in root folder instead.
then:
Code:
fastboot flash system system.img
this command will flash system.img
Code:
fastboot -w
this command will wipe data on device
Reboot your device in recovery using button combo and resize system partition to install Gapps.
From TWRP Wipe menu > advanced wipe > system > repair or change file system > resize system > swipe to resize
- move magisk and gapps from PC to device
- go to mount menu and tick mount system
- go back to install menu and flash gapps
- once you flashed gapps unmount system
- go to install and flash magisk
- go to wipe menu and swipe for factory reset
- reboot
once rebooted, complete the device setup.
be aware that some GSI could bootloop or not boot at all even if you followed the guide properly.
in case rely on GSI devs for assistance or fixes.
Of course you can flash a GSI ROM using TWRP.
The only fastboot command you need to perform is to disable dm-verity and AVB.
If you already disabled it while flashing TWRP for the first time, you can follow these steps to flash a GSI using TWRP:
- Tap on advanced Wipe menu and wipe cache, dalvik, data and system
- Tap on Install > Install Image > select image and flash it to system
- Install Gapps with the same process shown above.
- Swipe for factory reset and reboot.
-----------------------------------------------------------------------------------------------------------------------------------------------
If updating GSIs builds from the same branch (e.g. Floko 060219 to Floko 060919) you are not required to wipe data. You can update flashing system.img on TWRP and Gapps time by time.
If you are moving from unofficial builds to official, or if you are moving between branches (e.g. Floko to Havoc), you need to wipe data as well.
@pengus77 provided for a very useful Magisk Module that will fix adaptive brightness, battery stats and in-call BT. You will find it here: https://forum.xda-developers.com/showpost.php?p=79762257&postcount=242
If you flashed a GSI ROM, you are basically using a system.img flashed on top of your stock firmware so, unless you performed modifications to vendor or boot partition, you can revert to stock using fastboot or TWRP.
You need to extract system.img (and boot and vendor, if needed) from the stock firmware.
You will need the vbmeta file as well to re-enable AVB and dm-verity otherwise the device will reboot in fastboot mode only.
Beware: you must flash EXACTLY the same system.img of the firmware you were running before flashing a GSI
Once you have both files, you can follow these steps to go back to stock using fastboot:
- place the files on Minimal ADB & Fastboot root folder
- reboot bootloader
- start a command window from Minimal ADB and type: fastboot devices
once your device has been recognized type the following commands:
- fastboot -w
- fastboot flash system system.img
- (optional) fastboot flash vendor vendor.img
- (optional) fastboot flash boot boot.img
- fastboot flash vbmeta vbmeta.img
- fastboot reboot
You can also revert to stock using TWRP, by the way you will still need fastboot to flash vbmeta partition.
These are the steps to follow if you are using TWRP:
- place system.img on your device and vbmeta.img in Minimal ADB & Fastboot root folder.
- reboot to twrp and wipe dalvik, cache and data
- flash system.img to system partition
- (optional) flash vendor.img to vendor partition
- (optional) flash boot.img to boot partition
- reboot to bootloader
Start a command window in Minimal ADB & Fastboot, then type:
- fastboot devices
- fastboot flash vbmeta vbmeta.img
- fastboot reboot
Thansk for your work.
Does TWRP backup work?For getting back to stock?
Moh3n.B said:
Thansk for your work.
Does TWRP backup work?For getting back to stock?
Click to expand...
Click to collapse
I hope it is helpful
Backup worked for me on the TWRP I mentioned above.
If you want revert to stock you can flash again stock firmware using MiTool (fastboot ROM) or twrp (Recovery ROM).
Good thread! Might be confusing if there's no guide to install TWRP and GSI ?
Great guide. It will help a lot of people to flash and test roms. And us by extension to find the best rom for our device !
Today I had some time and I tried to install the latest Havoc Gsi, unfortunately the result was negative, I ran the guide both from xda and from here, my basic rom was 10.2.3.0, arrived at the command fastboot -w performs the various wipes, but then it does not allow me to go into recovery, it always and only goes in fastboot, and the only way to make the smartphone work is to use miflash and put the official version back.
scorpionredblack said:
Today I had some time and I tried to install the latest Havoc Gsi, unfortunately the result was negative, I ran the guide both from xda and from here, my basic rom was 10.2.3.0, arrived at the command fastboot -w performs the various wipes, but then it does not allow me to go into recovery, it always and only goes in fastboot, and the only way to make the smartphone work is to use miflash and put the official version back.
Click to expand...
Click to collapse
Try to flash vbmeta.
For me is not necesary.
Try like this from twrp:
- Wipe cache, dalvik cache, system, data
- Flash latest weekly eu firmware as base xiaomi.eu_multi_MI9SE_9.6.5_v10-9.zip
- Than flash havoc as system
Optional: flash magisk and custom kernel
Just stuck on bootloader unlocking.
Got this error "current account is not bound to this device"
I added device from mi unlock status too.
Moh3n.B said:
Just stuck on bootloader unlocking.
Click to expand...
Click to collapse
Search on Google. It looks like to be a common issue. If needed, follow the unlocking guide I linked on OP.
successfully flash Foloko ROM to Mi9 se, run very well!
just a small queastion, is DT2W is not working in all GSI rom?
Anyone try it yet?
Is there way to enable DC dimming (anti-pwm)?
I am using Havoc OS and my eyes are hurting..
sky104hk said:
successfully flash Foloko ROM to Mi9 se, run very well!
just a small queastion, is DT2W is not working in all GSI rom?
Anyone try it yet?
Click to expand...
Click to collapse
For now all gsi have same problem.
how to flash gapps ... i got error 70
raber111 said:
how to flash gapps ... i got error 70
Click to expand...
Click to collapse
Read carefully post n.2
Before I flash this, I world like to know from those already using this rom: How is the camera quality and finger print unlock response /speed?
I'm pissed at the frequent snow down of the miui system because I run vpn all day on my phone.
Sent from my Mi 9 SE using Tapatalk
krispuniq said:
Before I flash this...
Click to expand...
Click to collapse
Generally speaking, all the GSIs ROMs are based on Phhusson AOSP GSI ROM, so they have more or less the same performance and bugs.
At he moment FOD is not working well. You cannot unblock the device while on screen off or while on AOD.
For camera, you can install BSG Google Camera mod, that is working quite good.
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Changelog:
• Updated sources to latest
• Almost Everything working fine.
Only for MIUI 13 Android 11
Creator: @Aghora7
Download
Installation instructions
whats is with data encrypten? is it working or problems with: "cant decrypt fbev2 partition"?
lurchiii said:
whats is with data encrypten? is it working or problems with: "cant decrypt fbev2 partition"?
Click to expand...
Click to collapse
I can't answer to this question, because it depends on you made any mistakes during the installation or not
Its support for A12 miui 13.0.4
Does it support A12 eea europe rom ?
xristos1925 said:
Does it support A12 eea europe rom ?
Click to expand...
Click to collapse
it supports a11
It seems Poco M4 Pro is not supported by TWRP and OrangeFox and that this unofficial TWRP is only for Android 11..
In my case I rooted (with magisk) from the latest ROM with Android 12..
And then installed LineageOS (Android 13). Everything works fine..
But I want to have a custom recovery for installing e.g. Gapps...
How can I do that?
Or do I need to rollback to previous ROM, install this TWRP then root with magisk and then go and install Lineage OS (and in that case I will still have TWRP and rooted)?
Thanks for any details..
sanjibukai said:
It seems Poco M4 Pro is not supported by TWRP and OrangeFox and that this unofficial TWRP is only for Android 11..
In my case I rooted (with magisk) from the latest ROM with Android 12..
And then installed LineageOS (Android 13). Everything works fine..
But I want to have a custom recovery for installing e.g. Gapps...
How can I do that?
Or do I need to rollback to previous ROM, install this TWRP then root with magisk and then go and install Lineage OS (and in that case I will still have TWRP and rooted)?
Thanks for any details..
Click to expand...
Click to collapse
Once you have lineageos installed, you must to flash twrp via fastboot and then flash Gapps
1. Flash system ( when it's done, don't reboot phone, just flash twrp
2. If you already are on twrp flash your Google apps
3. When you're done with flashing gapps, restart phone to system (twrp will be gone after reboot)
4. You have installed Gapps
i don't know how to flash twrp permanently, if you want further informations about this recovery, then join fleur telegram development channel
BloxetPL said:
1. Flash system ( when it's done, don't reboot phone, just flash twrp
Click to expand...
Click to collapse
Hello and thanks for the reply..
Currently when I'm installing LineageOS I do the following:
Code:
# SMINORI SCRIPT
fastboot flash system system.img
fastboot reboot fastboot
fastboot getvar is-userspace
fastboot erase system
fastboot delete-logical-partition product_a
fastboot flash system system.img
# <- here?
fastboot reboot recovery
Do you mean that after installing LineageOS above, I need to run:
Code:
fastboot flash boot twrp.img
fastboot boot twrp.img
# Booting in TWRP despite the error
adb sideload gapps_file.zip
And then just install Gapps using the TWRP GUI?
sanjibukai said:
Hello and thanks for the reply..
Currently when I'm installing LineageOS I do the following:
Code:
# SMINORI SCRIPT
fastboot flash system system.img
fastboot reboot fastboot
fastboot getvar is-userspace
fastboot erase system
fastboot delete-logical-partition product_a
fastboot flash system system.img
# <- here?
fastboot reboot recovery
Do you mean that after installing LineageOS above, I need to run:
Code:
fastboot flash boot twrp.img
fastboot boot twrp.img
# Booting in TWRP despite the error
adb sideload gapps_file.zip
And then just install Gapps using the TWRP GUI?
Click to expand...
Click to collapse
Remove "fastboot reboot recovery" from SMINORI tool and instead of this type "fastboot flash boot twrp.img
fastboot boot twrp.img"
I currently have MIUI13 and Android 11.
Tried to install TWRP with the instructions given but my phone will keep on bootloop.
TWRP interface shows for a few seconds but it shuts down after.
Im looking everywhere for answers but couldnt find any
globalfandemic said:
I currently have MIUI13 and Android 11.
Tried to install TWRP with the instructions given but my phone will keep on bootloop.
TWRP interface shows for a few seconds but it shuts down after.
Im looking everywhere for answers but couldnt find any
Click to expand...
Click to collapse
I saw that your question on telegram, as they said do "fastboot reboot recovery" no "fastboot boot twrp.img"
BloxetPL said:
I saw that your question on telegram, as they said do "fastboot reboot recovery" no "fastboot boot twrp.img"
Click to expand...
Click to collapse
Already tried, still same issue.
Tried using a couple new commands too with no result:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot_a twrp.img
fastboot flash boot_b twrp.img
fastboot reboot recovery
Also tried using only the commands you gave:
fastboot flash boot twrp.img
fastboot reboot recovery
Hi!
I created a simple .bat script that roots poco m4 pro and redmi note 11s
Code:
/*
** Your warranty is now void.
**
** We are not responsible for bricked devices, dead SD cards,
** thermonuclear war, or you getting fired because the alarm app failed. Please
** do some research before rooting!
** YOU are choosing to make these modifications, and if
** you point the finger at us for messing up your device, we will laugh at you.
**
**/
Requirements:
1. Internet
2. Unlocked bootloader
3. Brain
Instructions:
1. Download magisk app from internet
2. Copy boot.img from your miui version to your phone
3. Patch boot.img with magisk app
4. When done, copy rooted image to computer
5. You MUST rename boot.img to rootedboot.img, if you don't rename it, the script simply won't work
6. Reboot phone to bootloader (vol+ & Power button)
7. Start the script
Code:
@echo off
adb devices
adb reboot bootloader
fastboot flash boot rootedboot.img
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot reboot
rootdone.vbs
You can download already rooted boot.img from RKEMIXM 13.0.7.0 that is attached below (but only if you have global 13.0.7)
Download easyROOT below:
The script:
Code:
adb devices
adb reboot bootloader
fastboot flash boot rootedboot.img
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot reboot
I can't recommend this.
It won't work, as you haven't included the vbmeta.img in your .zip.
But also, it's important to learn what you're doing when rooting your phone, and this is an extremely fragile solution that will only work if you have exactly the right device and firmware, have already unlocked your bootloader and enabled USB debugging, have installed the magisk app (at least, if you want anything useful from your root), have the right USB drivers installed, have the adb platform tools installed, etc.
This solution (if it worked) would go out of date as soon as Magisk or the system firmware is updated.
aricooperdavis said:
The script:
Code:
adb devices
adb reboot bootloader
fastboot flash boot rootedboot.img
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot reboot
I can't recommend this.
It won't work, as you haven't included the vbmeta.img in your .zip.
But also, it's important to learn what you're doing when rooting your phone, and this is an extremely fragile solution that will only work if you have exactly the right device and firmware, have already unlocked your bootloader and enabled USB debugging, have installed the magisk app (at least, if you want anything useful from your root), have the right USB drivers installed, have the adb platform tools installed, etc.
This solution (if it worked) would go out of date as soon as Magisk or the system firmware is updated.
Click to expand...
Click to collapse
You are right! I edited it so now that zip have vbmeta, also i added which results can bring rooting