Related
Guys after days of searching Internet to find a solution to fix WiFi reboot loop problem, I confirmed that this custom rom is the 100% guaranteed fix
It has fixed Samsung Tab SM-T110 which was restarting every time I enabled the WiFi. thanks to (CriskeloROM Custom Rom).
For those asking about the step-by-step Instructions, here you go:
Before you start, you should visit this thread (http://forum.xda-developers.com/showthread.php?t=2766612) and download some files:
1) Root Fix (https://mega.co.nz/#!tFYCkS4Y!W4piaGG5nxP9vlecFR4Z5E85q9-IcivEsBez2Tk_9-c)
2) Stock Recovery (https://mega.co.nz/#!cAZCTAbY!Mwt5N58yxNFzMDDkA5Y2qq5SDr8laAcEBK8CkXi2W_Q)
3) Philz Recovery (https://mega.co.nz/#!sUQyBIBb!NAEMOLl3GOcwj3KAHe6h2hXFYSOdw5fqUr-JNqLJzG0)
4) CriskeloROM (https://mega.co.nz/#!BUgXQKzQ!sa2GBqTG3mDpAquMlU6fCvFLT8lZjn_jvlZflVTU36w)
Now lets start:
1. Wipe Your Device:
1.1: Reboot in "Stock Recovery" Mode: "Volume-Up, Power, Home".
1.2: Wipe your device.
2. Install TWRP Custom Recovery:
2.1 Reboot in "Download" Mode.
2.2 Start Odin.
2.3 Use "AP" to install TWRP custom recovery.
2.4 Restart your Device when finished.
3. Install CriskeloROM Custom Rom:
3.1 Start the device.
3.2 Copy the three zip files after downloading is complete to SDCARD or Device: (Root Fix, Stock Recovery, CriskeloROM Rom) .
3.3 Reboot in "Recovery" Mode.
3.4 Select Install from Zip.
3.5 Use TWRP to browse to location where you copied the three files on your SDCARD or Device.
3.6 Select all zip files one by one.
3.7 Click Install and follow the on screen instructions (no restarts in-between) until all finished.
3.8 Reboot and Enjoy.
4. Install philz_touch (fix bootloop)
4.1 Start Odin.
4.2 Use "AP" to install philz_touch.
4.3 Restrat your Device when finished.
Good Luck !
philz_touch (fix bootloop) - no such thing afaik
khaledkoush said:
4. Install philz_touch (fix bootloop)
Click to expand...
Click to collapse
wtf ure talking about?
afaik there is no PhilZ on T110 which has the boot loop fixed.
Also the T110 does usually not reboot upon Wifi switch-on. That seems to be a individual problem with ure very T110.
khaledkoush said:
Guys after days of searching Internet to find a solution to fix WiFi reboot loop problem, I confirmed that this custom rom is the 100% guaranteed fix
It has fixed Samsung Tab SM-T110 which was restarting every time I enabled the WiFi. thanks to (CriskeloROM Custom Rom).
For those asking about the step-by-step Instructions, here you go:
Before you start, you should visit this thread (http://forum.xda-developers.com/showthread.php?t=2766612) and download some files:
1) Root Fix (https://mega.co.nz/#!tFYCkS4Y!W4piaGG5nxP9vlecFR4Z5E85q9-IcivEsBez2Tk_9-c)
2) Stock Recovery (https://mega.co.nz/#!cAZCTAbY!Mwt5N58yxNFzMDDkA5Y2qq5SDr8laAcEBK8CkXi2W_Q)
3) Philz Recovery (https://mega.co.nz/#!sUQyBIBb!NAEMOLl3GOcwj3KAHe6h2hXFYSOdw5fqUr-JNqLJzG0)
4) CriskeloROM (https://mega.co.nz/#!BUgXQKzQ!sa2GBqTG3mDpAquMlU6fCvFLT8lZjn_jvlZflVTU36w)
Now lets start:
1. Wipe Your Device:
1.1: Reboot in "Stock Recovery" Mode: "Volume-Up, Power, Home".
1.2: Wipe your device.
2. Install TWRP Custom Recovery:
2.1 Reboot in "Download" Mode.
2.2 Start Odin.
2.3 Use "AP" to install TWRP custom recovery.
2.4 Restart your Device when finished.
3. Install CriskeloROM Custom Rom:
3.1 Start the device.
3.2 Copy the three zip files after downloading is complete to SDCARD or Device: (Root Fix, Stock Recovery, CriskeloROM Rom) .
3.3 Reboot in "Recovery" Mode.
3.4 Select Install from Zip.
3.5 Use TWRP to browse to location where you copied the three files on your SDCARD or Device.
3.6 Select all zip files one by one.
3.7 Click Install and follow the on screen instructions (no restarts in-between) until all finished.
3.8 Reboot and Enjoy.
4. Install philz_touch (fix bootloop)
4.1 Start Odin.
4.2 Use "AP" to install philz_touch.
4.3 Restrat your Device when finished.
Good Luck !
Click to expand...
Click to collapse
Please give me new link for files ,because invalid all link!
What?
A TWRP bootable-image and installer ZIP for stock-based ROM's (i.e. not LOS 15.1) and maybe others (untested).
Based on:
Latest TWRP build provided by @pl_blaze
The official TWRP installation script for Pixel 2 by Dees_Troy (will install to both slots automatically - more resilient than the other TWRP script)
The IMG uses official kernel 8.1.10 so might be flashable (not tested!)
Not compatible with LineageOS 15.1 because it uses some custom update API that isn't in this TWRP. I considered using the LOS 15.1 TWRP build in this, but it's not compatible with stock encryption (it always thinks the passcode is wrong).
Full credits to @pl_blaze and Dees_Troy for this. I just packaged up something new and wrote clear instructions.
Why?
The old TWRP thread is not maintained and people keep asking/reporting the same questions/problems. I will try to keep this up to date as long as necessary. This is also a more robust installation script, using magiskboot binary to unpack/repack the boot image.
How?
Uninstall Magisk first if you have it installed, just to be safe. Or reflash stock boot.img. (Might not be necessary - a dirty flash worked OK for me but YMMV).
Fastboot boot (hotboot) any existing working TWRP image. Don't worry about working encryption/data, we only need kernel access. For example...
Code:
fastboot boot oreo_3.2.2_recovery.img
... which can be downloaded from Google Drive here (thanks to whoever shared this, I think it's a pl_blaze reshare).
Download attachment ZIP installer and flash in hot-booted TWRP (it will flash to both slots)
Reboot to Recovery and (re-)flash Magisk, if you use it.
Profit
@pl_blaze brother always thank you for the contributions that you do without coming to the light .and thanks for you @op to post working twrp for stock
this twrp will work on 7.1.2 ? i'm now on aex rom
Thanks @CosmicDan for starting this thread. I started to implement @pl_blaze changes into the official TWRP but I've been failing miserably (I'm a noob). Can you provide sources for the images?
I can't trust binaries floating all over the internet if it's not from a reliable dev. If you've compiled it yourself I'll give a try.
I reshare this twrp img on Telegram group,I tested it, works without problem
Flash of permaent twrp not tested by me
It's a good twrp!
CosmicDan said:
What?
A TWRP bootable-image and installer ZIP for stock-based ROM's (i.e. not LOS 15.1) and maybe others (untested).
Based on:
Latest TWRP build provided by @pl_blaze
The official TWRP installation script for Pixel 2 by Dees_Troy (will install to both slots automatically - more resilient than the other TWRP script)
The IMG uses official kernel 8.1.10 so might be flashable (not tested!)
Not compatible with LineageOS 15.1 because it uses some custom update API that isn't in this TWRP. I considered using the LOS 15.1 TWRP build in this, but it's not compatible with stock encryption (it always thinks the passcode is wrong).
Full credits to @pl_blaze and Dees_Troy for this. I just packaged up something new and wrote clear instructions.
Why?
The old TWRP thread is not maintained and people keep asking/reporting the same questions/problems. I will try to keep this up to date as long as necessary. This is also a more robust installation script, using magiskboot binary to unpack/repack the boot image.
How?
Uninstall Magisk first if you have it installed, just to be safe. Or reflash stock boot.img. (Might not be necessary - a dirty flash worked OK for me but YMMV).
Fastboot boot (hotboot) any existing working TWRP image. Don't worry about working encryption/data, we only need kernel access. For example...
Code:
fastboot boot oreo_3.2.2_recovery.img
... which can be downloaded from Google Drive here (thanks to whoever shared this, I think it's a pl_blaze reshare).
Download attachment ZIP installer and flash in hot-booted TWRP (it will flash to both slots)
Reboot to Recovery and (re-)flash Magisk, if you use it.
Profit
Click to expand...
Click to collapse
what does mean "hot boot", sorry am novice, Not even he could boot boot recovery from Minimal ADB and fastboot ,,, What am I doing wrong?
View attachment 4438212
teacapan said:
Fastboot boot (hotboot) anwhat does mean "hot boot", sorry am novice, Not even he could boot boot recovery from Minimal ADB and fastboot ,,, What am I doing wrong?
Click to expand...
Click to collapse
Hot boot means you are not flashing the recovery image just running it temporarily. Stock boot image is untouched in this process.
Run
fastboot devices
To check whether your device is connected.
alkesh95 said:
Hot boot means you are not flashing the recovery image just running it temporarily. Stock boot image is untouched in this process.
Run
fastboot devices
To check whether your device is connected.
Click to expand...
Click to collapse
thanks for reply, if you look at the screenshot it looks I am connected, the point is that it does not load the file, it does not find it, so if it does not start in recovery I can not do anything I'm stuck.
teacapan said:
thanks for reply, if you look at the screenshot it looks I am connected, the point is that it does not load the file, it does not find it, so if it does not start in recovery I can not do anything I'm stuck.
Click to expand...
Click to collapse
Did you put your recovery into the fastboot forder?
Did you unpack the zip ?
Also check if the name of recovery image is the same
It's possible to make password for twrp
DELETED.
lef7er1s said:
Did you put your recovery into the fastboot forder?
Did you unpack the zip ?
Also check if the name of recovery image is the same
Click to expand...
Click to collapse
1-yes
2-yes
3-yes
Anyway thanks for try help me.
Yeah well, I'm still stuck where, some help would be very appreciated.
View attachment 4438552
View attachment 4438553
Polluktus said:
this twrp will work on 7.1.2 ? i'm now on aex rom
Click to expand...
Click to collapse
Not sure, I've only tested on stock Oreo. Try and and let us know!
atttoush said:
Thanks @CosmicDan for starting this thread. I started to implement @pl_blaze changes into the official TWRP but I've been failing miserably (I'm a noob). Can you provide sources for the images?
I can't trust binaries floating all over the internet if it's not from a reliable dev. If you've compiled it yourself I'll give a try.
Click to expand...
Click to collapse
Indeed, no I have not compiled it myself - just ripped from pl_blaze.
I have a Oreo source repo cloned now for other reasons, but I might try and compile TWRP myself. Although it's been a couple years since I've tried to compile device-specific stuff from an AOSP tree so I don't know how long that will take.
teacapan said:
thanks for reply, if you look at the screenshot it looks I am connected, the point is that it does not load the file, it does not find it, so if it does not start in recovery I can not do anything I'm stuck.
Click to expand...
Click to collapse
Sounds like you just need to learn more about how to use console tools. You need to make sure the "fastboot boot filename.img" command will have a "filename.img" that matches the img filename in the current directory. This is just an example - substitute "filename.img" for the real filename. Use the CD command to change directory to where the img is.
teacapan said:
Yeah well, I'm still stuck where, some help would be very appreciated.
View attachment 4438552
View attachment 4438553
Click to expand...
Click to collapse
Try renaming the img file to something simpler like oreo_twrp.img
Edit: ah yes, the file you are pointing to has to be in the same directory where you opened cmd window, as cosmicdan stated above
CosmicDan said:
Indeed, no I have not compiled it myself - just ripped from pl_blaze.
I have a Oreo source repo cloned now for other reasons, but I might try and compile TWRP myself. Although it's been a couple years since I've tried to compile device-specific stuff from an AOSP tree so I don't know how long that will take.
Click to expand...
Click to collapse
Glad you open this thread. I'll wait for your compiled version to give it a try
teacapan said:
Yeah well, I'm still stuck where, some help would be very appreciated.
Click to expand...
Click to collapse
I don't know man, these adb and fastboot binaries look old (2014?). Try to get recent ones. And repeat the process.
silv3rfox said:
Glad you open this thread. I'll wait for your compiled version to give it a try
I don't know man, these adb and fastboot binaries look old (2014?). Try to get recent ones. And repeat the process.
Click to expand...
Click to collapse
Thanks, i will.
teacapan said:
Yeah well, I'm still stuck where, some help would be very appreciated.
Click to expand...
Click to collapse
Before flashing recovery
CD C:\Users\YOUR_USERNAME\Desktop\Adb
teacapan said:
Yeah well, I'm still stuck where, some help would be very appreciated.
Click to expand...
Click to collapse
The name of the file is ending with .img, delete ending " .img ", see below that patched_boot without .img in the end
Thanks for this. I checked out the differences between this and the flashable zip I was using (twrp-3.2.1-1-installer-tissot-FIXED_By_DroiDMester) and found this:
Code:
# write the new boot image to boot block
write_boot() {
print "Writing new boot image to memory..."
cd "$tmp"
if $use_dd; then
dd if=boot-new-a.img of="$boot_block"_a
[ $? = 0 ] || abort "Failed to write boot image A! You may need to restore your boot partition"
dd if=boot-new-b.img of="$boot_block"_b
[ $? = 0 ] || abort "Failed to write boot image B! You may need to restore your boot partition"
else
flash_image "$boot_block" boot-new.img
fi
[ $? = 0 ] || abort "Failed to write boot image! You may need to restore your boot partition"
}
This also flashes it into boot_a and boot_b correct?
What other differences does this have over that?
I Made both a fold with. Bat executable files to double click on and install boot.img files that have twrp and magisk preinstalled. Also a secondary executable that copy both magisk2.1.4 and a orangefox recovery zip files to your phone once in recovery or adb mode.
Just made them as quick installers and restoring root on The phone.
Installation
1. Extract zip file.
2. Goto bootloader mode or recovery mode. (bootloader mode to install root/twrp and recovery mode to send files to your phone.)
3. Just goto the folder and execute either. Bat files you want.
Enjoy
10.3.8
Beta2
{Mod edit: Links removed}
spheady said:
I Made both a fold with. Bat executable files to double click on and install boot.img files that have twrp and magisk preinstalled. Also a secondary executable that copy both magisk2.1.4 and a orangefox recovery zip files to your phone once in recovery or adb mode.
Just made them as quick installers and restoring root on The phone.
Installation
1. Extract zip file.
2. Goto bootloader mode or recovery mode. (bootloader mode to install root/twrp and recovery mode to send files to your phone.)
3. Just goto the folder and execute either. Bat files you want.
Enjoy
10.3.8
Beta2
Click to expand...
Click to collapse
Is this for oos 11 beta 2
spheady said:
Yeah. It just installs the Open beta 2 boot. Img with a batch file inside the folder i made. Make sure you don't run the other version I made for oxygen 10.3.8. Theirs another batch file I also included witch sends the orangefox recovery and a magisk zip file. It should help ad I just tested today before uploading it to my mega. Nz cloud.
Click to expand...
Click to collapse
Ok so i tried this last night it does install the orangefox recovery but still cant boot recovery without getting stuck on the screen flashing so i just flashed my own patched boot.img do you have a working recovery on your device
if so can you help me get it to flash to y device im on beta2 gm1917 8gb 256gb
I'd advise against using this. I received a virus message for Troj/Agent-ABZF.
@spheady THREAD CLOSED pending investigation! Download links removed.
Downloads checked by VirusTotal:
VirusTotal
VirusTotal
www.virustotal.com
VirusTotal
VirusTotal
www.virustotal.com
Please contact me or any other moderator and explain how these results are possible!
WARNING: THIS IS EXPERIMENTAL BETA MEANT FOR DEVELOPERS AND TESTERS NOT AS DAILY DRIVER
Caution: Android 11 builds are incompatible with Android 12. Beware!
Credits:
@Woomymy
@J6idot
@mastersenpai05
@myst33d
https://github.com/notmyst33d
Developers WoomyMy, J6idot , mastersenpai05 and Myst33d have helped develop an unofficial TWRP for rosemary - xiaomi redmi note 10s
Installation Video:
Code:
https://www.mediafire.com/file/f4zcls9sgi3nkoj/352+redmi+note+10s.rar/file
http://www.mediafire.com/file/p3zhivru97bdlke/no-verity-opt-encrypt-6.1.zip/file
https://github.com/RedmiNote10S/recovery_device_xiaomi_rosemary
Since this is not yet official, only proceed if you are competent enough and brave.
(If you need instructions on how to flash, please do not flash this with fastboot method)
Feel free to discuss any bugs or issues and fixes so that everybody can benefit from our findings.
TWRP 3.6+ Development Build status, fixes, bugs and downloads: [here]
TWRP -3.6.2_11-2
NameModifiedTWRP-3.6.2_11-208/03/2022
Changelog
Fix brightness when max brightness is 255
Render GUI at 60FPS
Reposition statusbar icons and remove top offset
A lot of code cleanup
Update TWRP sources
DONT INSTALL THIS ON MIUI 13
Install instructions
Without TWRP/OrangeFox
Note: You need a copy of your ROM boot.img
Click to expand...
Click to collapse
This device DOES NOT support fastboot boot twrp.img
Click to expand...
Click to collapse
Reboot your phone into fastboot mode
Download Blank VBmeta and flash it using fastboot flash vbmeta vbmeta.img
Next, download TWRP .IMG file and flash it using fastboot flash boot IMAGE_NAME.img
Reboot into recovery mode (fastboot reboot recovery)
When booted into recovery, reflash stock boot.img (Install -> Install Image -> Select stock boot.img -> “Flash to: Boot”)
Next, go in Advanced -> Flash current TWRP and swipe to flash TWRP.
Reboot and enjoy!
With custom recovery
Download TWRP .ZIP installer and flash it in recovery (you can also use adb sideload for recoveries like LineageOS recovery)
Compatibility
Android 11 Roms: YES
Android 12 Roms: NO
TWRP-3.6.2_12-rc1
NameModifiedTWRP-3.6.2_12-rc108/04/2022
Changelog
Sync TWRP sources
Add support for Android 12 decryption
Fix booting on MIUI13
DONT INSTALL THIS ON MIUI 12.5
Install instructions
Without TWRP/OrangeFox
Note: You need a copy of your ROM boot.img
Click to expand...
Click to collapse
This device DOES NOT support fastboot boot twrp.img
Click to expand...
Click to collapse
Reboot your phone into fastboot mode
Download Blank VBmeta and flash it using fastboot flash vbmeta vbmeta.img
Next, download TWRP .IMG file and flash it using fastboot flash boot IMAGE_NAME.img
Reboot into recovery mode (fastboot reboot recovery)
When booted into recovery, reflash stock boot.img (Install -> Install Image -> Select stock boot.img -> “Flash to: Boot”)
Next, go in Advanced -> Flash current TWRP and swipe to flash TWRP.
Reboot and enjoy!
With custom recovery
Download TWRP .ZIP installer and flash it in recovery (you can also use adb sideload for recoveries like LineageOS recovery)
Compatibility
MIUI 13 vendors: COMPATIBLE
MIUI 12 vendors:
A11 GSI / MIUI 12 system: FULLY INCOMPATIBLE
A12 GSI: COMPATIBLE, but you CAN NOT flash the boot.img, you need to flash the UPDATE ZIP using a custom recovery / Magisk
OrangeFox-R11.1_1-Unofficial
NameModifiedOrangeFox-R11.1_1-Unofficial07/01/2022
Changelog
Fix brightness when max brightness is 255
Render GUI at 60FPS
Reposition statusbar icons and remove top offset
A lot of code cleanup
Update OrangeFox sources
DONT INSTALL THIS ON MIUI 13
Update Magisk OrangeFox addon to v25.2
Install instructions
Without TWRP/OrangeFox
Note: You need a copy of your ROM boot.img
Click to expand...
Click to collapse
This device DOES NOT support fastboot boot twrp.img
Click to expand...
Click to collapse
Reboot your phone into fastboot mode
Download Blank VBmeta and flash it using fastboot flash vbmeta vbmeta.img
Next, download OrangeFox .IMG file and flash it using fastboot flash boot IMAGE_NAME.img
Reboot into recovery mode (fastboot reboot recovery)
When booted into recovery, reflash stock boot.img (Select stock boot.img -> “Flash to: Boot”)
Next, go in Menu -> Flash current OrangeFox and swipe to flash OrangeFox.
Reboot and enjoy!
To get Fox addons working, you need to reflash OrangeFox .zip file
With custom recovery
Download OrangeFox .ZIP installer and flash it in recovery (you can also use adb sideload for recoveries like LineageOS recovery)
Compatibility
Android 11 Roms: YES
Android 12 Roms: NO
Older versions:
NameModifiedBeta-07-11-30-202112/17/2021
🗞 Changelog
Sync TWRP sources (Version number updated to 3.6.0)
Symlink /dev/block/bootdevice -> /dev/block/platform/bootdevice (required by some scripts like OrangeFox installer)
Allow flashing VBMeta
Disable "Reflash TWRP after flashing ROM". (Causes AVB problem when installing MIUI, can still be done manually)
Build ZIP TWRP installer
Publish build logs for more transparency
Known bugs
Mounting Adopted storage
Vibrator
NameModifiedRC-01-01-09-20221/9/2022
🗞 Changelog
Fix Bootctrl
Fix vibrator
Known bugs
Mounting Adopted storage
TWRP Version 3.6.1_11-1
NameModifiedTWRP-3.6.1_11-13/13/2022
🗞 Changelog
Fix BootCTRL
Update TWRP sources
Fix vibrator
Enable DT2W in recovery
Install instructionsWithout TWRP/OrangeFox
Note: You need a copy of your ROM boot.img
Click to expand...
Click to collapse
This device DOES NOT support fastboot boot twrp.img
Click to expand...
Click to collapse
Reboot your phone into fastboot mode
Download Blank VBmeta and flash it using fastboot flash vbmeta vbmeta.img
Next, download TWRP .IMG file and flash it using fastboot flash boot IMAGE_NAME.img
Reboot into recovery mode (fastboot reboot recovery)
When booted into recovery, reflash stock boot.img (Install -> Install Image -> Select stock boot.img -> “Flash to: Boot”)
Next, go in Advanced -> Flash current TWRP and swipe to flash TWRP.
Reboot and enjoy!
With TWRP/OrangeFox
Download TWRP .ZIP installer and flash in recovery
TWRP Version 3.6.2_11-1
NameModifiedTWRP-3.6.2_11-16/14/2022
🗞 Changelog
Sync TWRP sources
Orangefox Recovery Version R11.1_1-Beta
NameModifiedOrangeFox-R11.1_1-Beta3/13/2022
🗞 Changelog
Fix BootCTRL
Update OrangeFox sources
Fix vibrator
Enable DT2W in recovery
Update Magisk OrangeFox addon to 24.2
Install instructionsWithout TWRP/OrangeFox
Note: You need a copy of your ROM boot.img
Click to expand...
Click to collapse
This device DOES NOT support fastboot boot twrp.img
Click to expand...
Click to collapse
Reboot your phone into fastboot mode
Download Blank VBmeta and flash it using fastboot flash vbmeta vbmeta.img
Next, download OrangeFox .IMG file and flash it using fastboot flash boot IMAGE_NAME.img
Reboot into recovery mode (fastboot reboot recovery)
When booted into recovery, reflash stock boot.img (Select stock boot.img -> “Flash to: Boot”)
Next, go in Menu -> Flash current OrangeFox and swipe to flash OrangeFox.
Reboot and enjoy!
To get Fox addons working, you need to reflash OrangeFox .zip file
With TWRP/OrangeFox
Download OrangeFox .ZIP installer and flash in recovery
Nice, it's beta 2
to apply encrypt patch, you must decrypt first.
So
- you have to disable security password/fingerprint in your parameter first.
- then reboot in recovery
- format data
- reboot again to recovery and apply patch.
How to use redmi note 10s unofficial twrp recovery
test (beta 2) after disabling security (fingerprint and pin)
- flashing magisk.zip -> ok
- backup -> ok
- restore -> ok
- MTP internal SD -> ok
- MTP external SD -> nok, file manager stuck on it (win10 or linux mint)
Please full prosses explain and 1 question flash fastboot method
This the link of the Official Tutorial from the Unofficial TWRP Website:
unofficial twrp 3.6.1 Root Redmi Note 10s (rosemary) - unofficial twrp
Download unofficial twrp 3.6.1 root Redmi Note 10s, user who own Redmi Note 10s can root it by following the below instructions
unofficialtwrp.com
Great
miravision said:
Developer WoomyMy has released an unofficial TWRP for rosemary - xiaomi redmi note 10s
Installation Video:
Code:
https://www.mediafire.com/file/f4zcls9sgi3nkoj/352+redmi+note+10s.rar/file
http://www.mediafire.com/file/p3zhivru97bdlke/no-verity-opt-encrypt-6.1.zip/file
Since this is not yet official, only proceed if you are competent enough and brave.
(If you need instructions on how to flash, please do not flash this with fastboot method)
Feel free to discuss any bugs or issues and fixes so that everybody can benefit from our findings.
Click to expand...
Click to collapse
I'm sorry but, do you atleast have the permission to share this?
Also, WommyMy should be the guy to upload it, not you.
Edit: thanks for fixing the thread
Also you're missing the device tree.
Hello. As one of the developpers of this TWRP DT, I am not really OK with that.
Firstly, you linked the wrong device tree Real link here
Also, I didn't published this on XDA because this TWRP is still in BETA. And it contains major bugs, like flashing dynamic partitions in fastbootd. Even if bugs will me fixed, I was planning to wait a release candidate before publishing the release here (this will require even more testing, if people want to help us testing, this will be even better).
So please, can you delete this or add clear warnings about the beta state?
Regards, Woomy
@miravision I think we should also add credits to people like @J6idot , @mastersenpai05 and Myst33d who did a great job helping building twrp.
Woomymy said:
@miravision I think we should also add credits to people like @J6idot , @mastersenpai05 and Myst33d who did a great job helping building twrp.
Click to expand...
Click to collapse
Yes, I believe they should get their work credit.
Will be fix soon.. don't too hurry.
mastersenpai05 said:
Will be fix soon.. don't too hurry.
Click to expand...
Click to collapse
Thanks bro
Keeps restarting when i try to flash a custom ROM from xiaomi eu, any Fix please ?
Wow., Hoping for releasing custom roms for our handsets.,keep up the good work devs
Katho536 said:
Keeps restarting when i try to flash a custom ROM from xiaomi eu, any Fix please ?
Click to expand...
Click to collapse
Xiaomi eu has no support for 10s iirc
No support for Mediatek devices on Xiaomi.eu, Global.rom and other
@miravision can u provide the vbmeta.img file?
Original post updated with attached vbmeta.img
langithitam said:
@miravision can u provide the vbmeta.img file?
Click to expand...
Click to collapse
Hi and thanks for sharing
Is it possible just to boot from TWRP recovery via Fastboot without flashing it on the phone?
I have also a Poco X3 NFC with stock MIUI 12.5 with Magisk root, but with stock recovery (so I can do all OTA updates) where I'm doing the same.
When I need it, I just do
fastboot boot TWRP-file.img
Thanks
REQUIREMENTS - BL UNLOCKED
You need to be on VERSION : RMX3312_11.C.12_IN_202304230924
If not on RMX3312_11_C.12 version - download the entire OTA PACKAGE from the above link & LOCAL INSTALL
Reboot to Bootloader adb reboot bootloader or Power + Volume Down
Take the ROOT BOOT image from the zip file given below and PASTE it in platform tools folder
FLASH the ROOT BOOT IMAGE fastboot flash boot RMX3312_11.C.12_ROOTBOOT.img
Type - fastboot reboot
Finished - Now your Realme GT2 - RMX3312 is now ROOTED!
P.S. : FLASH ON BOTH SLOTS
To keep ROOT when you receive an OTA update
DOWNLOAD THE OTA UPDATE
Let it UNZIP
When it shows - INSTALL / REBOOT TO INSTALL option, put to recents - Open MAGISK
There in MAGISK - SELECT THE INSTALL OPTION on the TOP RIGHT
& then select INSTALL TO INACTIVE SLOT (AFTER OTA) OPTION
Click on OK on the POP-UP MENU in MAGISK
NOW THE DEVICE WILL REBOOT - UPDATE TO THE LATEST OTA & STILL KEEP ROOT!
DOWNLOADS : Both STOCK & ROOT boot images are attached below in one ZIP FILE!
Each Boot Image is 192MB & the compressed ZIP FILE below is 72.6MB.
NOTE : I'm NOT RESPONSIBLE FOR BRICKS, STONES, BLASTS, WIPES etc. of RMX3312
Thank you of the guide.
Just questions, what is meant by "P.S. : FLASH ON BOTH SLOTS"?
and What is the SafetyNet status?
gx7x said:
Thank you of the guide.
Just questions, what is meant by "P.S. : FLASH ON BOTH SLOTS"?
and What is the SafetyNet status?
Click to expand...
Click to collapse
He means you need to run the flash boot command for each slot
for instance your system runs on a slot, as soon as you type the
fastboot flash boot [boot image]
if it shows writing boot_a
then you need to type
fastboot flash boot_b [boot image]
to flash in the b slot also
if it shows writing boot_b
then you need to type
fastboot flash boot_a [boot image]
to flash in the a slot also
and you can pass the safteynet easily even when in root, u can use zygisk and magiskhide to pass the safteynet and you can run any banking app you want
Please do not use the boot images provided if you have not updated to the current latest version
Note: EU version boot image might be different so don't try
p.s you can extract boot images yourself from any version you want!
Stano36 said:
How to extract images from OTA zip files:
Extract the OTA zip file
Download and extract payload-dumper-go
Drag and drop payload.bin on payload-dumper-go executable
Spoiler: Video instructions
Click to expand...
Click to collapse
HIGHLY recommend to extract boot for your version, tnx to Stano36 we have well prepared collation of update. Thanks to Prajwal_Beast for this guide!
I have some questions about "a" and "b" partitions, where can I found some information why we have two partitions and all have two or some of them and etc..
b0nb0n3v said:
HIGHLY recommend to extract boot for your version, tnx to Stano36 we have well prepared collation of update. Thanks to Prajwal_Beast for this guide!
I have some questions about "a" and "b" partitions, where can I found some information why we have two partitions and all have two or some of them and etc..
Click to expand...
Click to collapse
We have two partitions so that if one fails the other can safely boot however most of us are careless and flash on both partitions so it's not really helpful for us
How to root gt 2 running on pixel os?
_PsyDuck_ said:
How to root gt 2 running on pixel os?
Click to expand...
Click to collapse
extract the pixel os file & patch the boot image using magisk & flash the magisk patched boot image
Thanks