(I'm not permitted to post in the developers forum, i.e. roms, kernels, recoveries, etc., so I'm posting this here).
My original post can be found here in the Blu Development Group on Google+. (Forgive me if this is considered redundant):
https://plus.google.com/u/0/106948556420593597970/posts/Lp8cCUR8AZq
TWRP v3.0.3 BLU VIVO XL V0030UU - MT6753 for Android 6.0 (kernel 3.18.19) by lopestom
(And TWRP v3.0.2-1 Materialized)
Special thanks for +lopestom for compiling these custom recoveries and for all his instruction and help.
Instructions for minimal ADB installaion:
https://forum.xda-developers.com/showthread.php?t=2317790
Instructions for TWRP boot load:
- Turn on developer options
- Turn on USB debugging
- Turn on OEM unlocking in developer options. Using fastboot oem unlock doesn't matter, I believe, but I did it anyway. It doesn't cause a boot loop on Android 6.0, but using fastboot oem unlock on my android 5.1 version did cause a boot loop for me.
- ADB reboot bootloader
- Fastboot boot <twrp_recovery_file.img>
- Wait about 1-2 minutes
THIS IS IMPORTANT. I had no luck flashing the twrp recoveries using the conventional means of either SP flash tool or Fastboot flash of the recovery. The device would always boot loop at least once and revert back to the stock recovery. However, I did have success using "fastboot boot recovery recovery.img" in the bootloader. TWRP would take a while to load, but it did. This was the first TWRP recovery I personally was able to load on Android 6.0 of the Blu Vivo XL. If you are successful in permanently flashing the TWRP, please share your method
TWRP download files:
5 - recoveryTWRPv3.0.3 BLU VIVO XL V0030UU - by lopestom
https://drive.google.com/open?id=0B3FJHUCtGU9sc0dQT2Q5TUpuMG8
OR
4 - recoveryTWRPv3.0.2-1 Materialized BLU VIVO XL V0030UU - by lopestom
https://drive.google.com/open?id=0B3FJHUCtGU9sNnVEWTVfOTZfUzQ
You can try both of the above. I was able to successfully root the device using v3.0.3, but both would load.
The prior STOCK ROMs (Android 5.1 V07 and Android 5.1 V10) for Blu Vivo XL are on the repository by +William Smith. Please note that no stock rom for the Blu Vivo XL on Android 6.0 has been released by Blu. You must upgrade to Android 6.0 through the OTA update.
I used this to root (not sure who to credit, my apologies):
https://www.google.com/url?q=https:...sntz=1&usg=AFQjCNGdP_Scd5jn9Dgri61Yz-mhA1B7zQ
*I shall not be held responsible for any errors/issues caused using this custom recovery.
(Please see below for the images of the TWRPs that loaded)
Shoot, I meant to post this in the guides section. Newbie mistake. Are there any moderators that can move this thread? Thanks.
don't work , tryed on SPlus on 3.18.19 , both recovery got blackscreen and reboot
IacobIonut-DW said:
don't work , tryed on SPlus on 3.18.19 , both recovery got blackscreen and reboot
Click to expand...
Click to collapse
Thanks for letting us know. Do you currently have another custom recovery on there?
It's important to wait for it to load for about 1 to 3 minutes. Or did the phone go back to system booting on its own? During that time the "screen" may go into sleep mode. Just tap power button to wake it up and see if TWRP is there. Also, is your bootloader unlocked? I believe that may be required on the Gionee elife S Plus, where you actually have to go through the process of "fastboot oem unlock", and let it reboot. BEWARE: this will wipe your device.
In any case, I didn't test this recovery on the Gionee elife S Plus, as I don't have that device. Although they're the same phone, maybe there are slight differences in the booting process?
Likewise, for instance, this TWRP from Hovatec below for the Gionee e life S plus didn't work on my Blu VIVO XL. I believe others may have had luck booting to recovery using it on the VIVO XL, however. Not positive. But for me, I had no luck.
https://forum.hovatek.com/thread-15270.html
I read somewhere the Gionee S Plus has Android 6.0.1. Is that correct? The VIVO XL still has Android 6.0 (same kernel), but I'm not sure that would make a difference.
can you provide me a TUT on how to replace the recovery using ADB just the way you flashed Your Phone.. Please
Same as the 3rd floor. Black screen and then bootloop
Related
This thread is meant to address all the common hurdles that are commonly faced by people who are new to treble devices (chef to be specific) and help them to troubleshoot/avoid some small yet critical steps during flashing new ROMs and working with fastboot and recovery in general. It will be continually updated with new stuff as it goes along.
I will be referring to the Motorola One Power and Moto P30 Note as chef only from now on.
The unlocking guide is available in This XDA Thread!
IMPORTANT:
1. Flashing refers to the process of doing a clean flash, with the inclusion of fastboot -w command
2. Latest ADB and Fastboot drivers are required to be installed, else the installation may halt mid-way.
3. Stock ROM refers to the Android One ROM for the Motorola One Power [XT 1942-2]
IMPORTANT: AS OF RIGHT NOW, PEOPLE WHO HAVE INSTALLED STOCK PIE (EITHER VIA UPDATE OR FIRMWARE) WILL NOT BE ABLE TO USE ANY OTHER ROM OTHER THAN THE STOCK PIE ROM. RADIO INTERFACE LAYER IS BROKEN IN OREO SOURCE BUILT ROMS AND THAT CURRENTLY INCLUDES LINEAGE 16 SO PLEASE WAIT FOR PIE SOURCE CODE FROM MOTOROLA FOR THAT TO BE FIXED.
1. I unlocked my chef . How do I flash TWRP in place of the stock recovery?
Solution:Currently you cannot as there is no recovery partition in the device. You have to manually boot TWRP onto the device using fastboot to use it. Follow as directed:
Boot the device into fastboot mode
Use command fastboot boot <path/to/TWRP.img> to boot TWRP temporarily.
2. I am done with TWRP and I want to flash Lineage OS 16 on my chef. I simply flash the .zip archive right?
Solution:No. Before you flash anything,
Take a backup of atleast your EFS and PERSIST partitions using TWRP and off-load it for safekeeping to restore in future if needed. You can also trigger a full backup if you require.
SUPER IMPORTANT: Flash this .zip file to copy the System A/B partitions. If this step is skipped, you will be responsible to brick your own device. THIS STEP IS ONLY REQUIRED ONCE AND ONLY ONCE IN THE LIFETIME OF YOUR DEVICE! YOU WON'T BE NEEDING THIS THE NEXT TIME YOU FLASH ANY ROM. .
After that, flash your dearest custom ROM and get going.
For Lineage OS 16, follow This XDA Thread.
3. I am done testing LOS 16, I want to flash a GSI. Shall I use a stock Vendor Image for the GSI on my chef?
Solution:No. The stock Vendor image is causing bootloop issue in most GSIs. It is recommended to use Lineage OS Vendor to flash a GSI on chef. So flash LOS and then flash your favourite GSI.
Also, Super Important: for those who haven't used lineage before flahing a GSI, it is required to boot Lineage OS first before flashing a GSI.
4. I am done experimenting, I want to go back to the stock image. How do I proceed?
Solution:Follow this XDA thread for it. And don't install OTA updates directly from the device. It will come in the next step.
5. I want to install OTA updates on the stock ROM. How do I proceed?
Solution:Follow this XDA post for it. The installation process is described here. You have to be clever enough to get the appropriate OTA update.
Credits:
@erfanoabdi : TWRP, LOS 16, AB partition management
@rushiranpise : Unlocking guide
@dayask : Testing the process, guide for reflashing stock ROM
@nageen9211 : Testing ROMs
For any additional queries, feel free to contact us at our Telegram Group
For more regular updates, follow our Telegram Channel
Always remember: You have to be smarter than your smartphone to be able to use it!
Cheers and Happy Flashing!
Note to readers
The above guide is for stock kernels only (including lineage)
The custom Darkone Kernel has constant updates and fixes major bugs often. Please follow the linked thread to test it out if you want to. Cheers!
Anyone have flashed GSI ROM? FOr me after flash GSI HavocOS have bootloop :/
DIdn't flash copy system A/B partitions, stuck on bootloop with custom roms.
Watched some youtube videos and didn't read this post before flashing custom ROM. Flashed Custom ROM without flashing A/B partitions. Now I have a phone stuck on bootloop when done anything in TWRP. or I can use my phone with stock ROM installed by fastboot method.
Installing or restoring anything from TWRP results in boot loop.
Restoring the backup I made before flashing, completes the restoration process normally. But when rebooting to system, TWRP prompts me that no OS is installed. If I reboot anyway, its either stuck on bootloop or reboots to recovery and asks me to try again or factory reset, or boots into bootloader mode.
Installing custom ROM begins with Step 1, takes a bit time and starts step 2 and shows completed. Doesn't echos any comments. But when i reboot, same prompt shows saying no OS installed. Reboot anyway and stuck on bootloop or reboots to recovery and aks me to try again or factory reset, or boots into bootloader mode.
Now I installed stock ROM with fastboot method and phone is boots up into system just fine.
Sometimes TWRP can't mount anything.
So am I stuck with stock rom or is there any solutions?
Also, installing stock ROM with fastboot mode showed this error in between scripts
(bootloader) is-logical:xxx_a: not found
and
(bootloader) is-logical:xxx_b: not found
but is able to use the phone just fine with stock ROM.
First- I am NOT Responsible if you brick your Device! You do everything at your own Risk!
As I cannot find successfull thread here guiding to root this tablet I am posting the success with rooting with Magisk, all is seen on Russian forum 4pda,but the firmware I am on is not here ,it was little hard to find it(paid) but at the end it works, I have full root:
1 .You must have UNLOCKED BOOTLOADER!!! You can do it here are 2 threads guiding to it,mine was with DC_unlocker-4USD;
2. You must download Magisk from its original thread :Link
3.You must Look at which firmware you are,download the patched ones :С170B003
С170B253
C100B270
Or you can download you full Rom, extract it using Huawei Firmware Extractor extract the BOOT.img from UPDATE.APP file transfer it to your tablet and using Magisk--> install choose boot.img and patch it, then copy the patched_boot.img from folder "Downloads" in the internal memory back to PC,rename to boot.img.
4.You must have installed ADB and fastboot.
5.Using fastboot command on PC install the patched boot.img to tablet:
-First on your tablet enable Developer Options, thick Enable OEM Unlock,thick USB Debugging on,when connected to PC must ask for Fingerprint Security Rsa key,thick Always Trust to this PC"
-Second Tunoff Tablet, then hold volume Down button and connect to PC with USB Cable,Fastboot menu must appear: With green at bottom must be written that it is not FRP locked! If so -dont do proceed disable remove Huawei Account if you have one!
-Third-copy patched boot.img to folder where is located ADB and fastboot, then hold shift and right click mouse button and click Open Command Prompt here.
Now on fastboot menu enter following:
fastboot.exe flash boot boot.img
At the end everything must be OK!
Reboot with power button and check in Magisk !
Regards
I just wanted to confirm that this method works for my tablet. My Huawei Mediapad M3 10.1" BAH-L09 had bootloader unlocked. Emui5.1.2 and OS 7.0. Following these instructions, I extracted the BOOT.img from the stock ROM, then used Magisk Manager app (6.0.1) to create the patched-boot.img. Flashing this patched-boot.img using fastboot mode with command:
fastboot flash boot patched_boot.img
My tablet now is ROOTED without any problems (camera works normally). In short, just follow exactly these instructions and your tablet will be ROOTED
This works for me on BAH-L09 with Build Number BAH-L09C100B270. My Tab ist now rooted with Magisk 17.1 installed. Next i do flash special version of TWRP from the TWRP Builder site. I took the version for the BAH-W09 (WIFI version of the tab) on my own risk. I KNOW thats not the correct version, so please dont criticize.
Installation via fastboot worked. I can boot into Huawei recovery (Power+Vol-up) and TWRP (Power + Vol-Up and Vol-down same time). System boots without problem too. Also i can flash back the original huawei rcovery.img in fastboot mode.
But there is an issue in this TWRP recovery version 3.2.1-0. It does not decrypt data. I tried to format data and flash "no-verity-opt-encrypt". But there is still an Huawei secure mechanism, that wants me to format data in Huawei recovery again. Without format data my tab do not boot into system.
Next step i tried to get TWRP for my device on TWRP-builder app. but no succes because the build queue ist full. So i have to wait...
Sorry but how did you unlock the bootloader?
DragonautMk said:
Sorry but how did you unlock the bootloader?
Click to expand...
Click to collapse
I used dc-unlocker (you can google for). Its easy but it costs ca. 4 €.
Does this method still works on latest ota ?
The4anoni said:
Does this method still works on latest ota ?
Click to expand...
Click to collapse
My M3 10 lite was on latest frmware C100B270 as i used dc-unlocker. Unlock worked well for me.
Does rooting enable you to install Google Services on the tablet? Is so, how?
Is there an international ROM that can be used (with Google tools)
Thanks! Worked for my Mediapad M3 lite 10 (BAH-L09), but now... How can I update Magisk? The Magisk manager doesn't support the version installed.
Can't install twrp either
---------- Post added at 08:40 PM ---------- Previous post was at 07:51 PM ----------
ossizwei said:
This works for me on BAH-L09 with Build Number BAH-L09C100B270. My Tab ist now rooted with Magisk 17.1 installed. Next i do flash special version of TWRP from the TWRP Builder site. I took the version for the BAH-W09 (WIFI version of the tab) on my own risk. I KNOW thats not the correct version, so please dont criticize.
Installation via fastboot worked. I can boot into Huawei recovery (Power+Vol-up) and TWRP (Power + Vol-Up and Vol-down same time). System boots without problem too. Also i can flash back the original huawei rcovery.img in fastboot mode.
But there is an issue in this TWRP recovery version 3.2.1-0. It does not decrypt data. I tried to format data and flash "no-verity-opt-encrypt". But there is still an Huawei secure mechanism, that wants me to format data in Huawei recovery again. Without format data my tab do not boot into system.
Next step i tried to get TWRP for my device on TWRP-builder app. but no succes because the build queue ist full. So i have to wait...
Click to expand...
Click to collapse
The same for me. Have you got the appropiatte twrp recovery?
wanlus said:
Thanks! Worked for my Mediapad M3 lite 10 (BAH-L09), but now... How can I update Magisk? The Magisk manager doesn't support the version installed.
Can't install twrp either
The same for me. Have you got the appropiatte twrp recovery?
Click to expand...
Click to collapse
This is an old post. Development has going forward. Look here:
For a LineageOS rom
https://forum.xda-developers.com/mediapad-m3/development/rom-t3945684
For TWRP
https://forum.xda-developers.com/mediapad-m3/development/twrp-t3914531
For the first step use the 3.2.0 version of TWRP if you are in Huawei's stock Rom.
For me its the best for this moment. Only issue is, that camera dont work in this early lineage rom. But developer is working on it.
ossizwei said:
This is an old post. Development has going forward. Look here:
For a LineageOS rom
https://forum.xda-developers.com/mediapad-m3/development/rom-t3945684
For TWRP
https://forum.xda-developers.com/mediapad-m3/development/twrp-t3914531
For the first step use the 3.2.0 version of TWRP if you are in Huawei's stock Rom.
For me its the best for this moment. Only issue is, that camera dont work in this early lineage rom. But developer is working on it.
Click to expand...
Click to collapse
Ok, thank you so much. I've got installed Twrp properly, and it boots ok... but no more. Now it stays on the recovery home screen. I'll try again
Hi everyone,
I'm right now facing the issue that none of the flashed custom ROMs can boot.
I'm right now on MIUI 10.0.2.0, the bootloader is unlocked and TWRP was installed, but since I returned to the original global ROMs via XiaomiMiFlash Tool I think it's not on the decide anymore.
I tried to install Havoc and Pixel Experience.
What is the correct procedure to flashed the roms ?
I followed the instructions on the Havoc OS Thread for "Coming from MIUI 10.0.2.0". After installing the device kept boot looping and basically "flashing" the MI Logo with the "Unlocked" Label at the bottom.
Thank you for your time and help.
This could be a problem with your data partition and encryption. You need to full wipe your data (you loose all your sdcard data, so backup as much as possible) with twrp.
I used "Format Data" under "Wipe" in TWRP.
And I tried to run the decryption zip.
Same thing.
Lighthex said:
Hi everyone,
I'm right now facing the issue that none of the flashed custom ROMs can boot.
I'm right now on MIUI 10.0.2.0, the bootloader is unlocked and TWRP was installed, but since I returned to the original global ROMs via XiaomiMiFlash Tool I think it's not on the decide anymore.
I tried to install Havoc and Pixel Experience.
What is the correct procedure to flashed the roms ?
I followed the instructions on the Havoc OS Thread for "Coming from MIUI 10.0.2.0". After installing the device kept boot looping and basically "flashing" the MI Logo with the "Unlocked" Label at the bottom.
Thank you for your time and help.
Click to expand...
Click to collapse
Try this:
1. Flash MIUI PIE 8.12.20 global Rom DON'T REBOOT
2. Flash Disable_Dm-Verity_ForceEncrypt Here DON'T REBOOT
3. Wipe Data,System,Cache Your Data will be lost
4. Flash HavocRom + Gapps
5. Reboot and Enjoy
the link to the post is here: https://forum.xda-developers.com/mi-8/development/prepare-t3841106
I followed that instructions and now I'm at least seeing the boot logo, but its stuck at the animation.
I left it for 1 hour and it's not booting...
What can I do ?
There is confusion over which recoveries to install for Redmi 6 (cereus).
Failure to install the correct TWRP will result in a hard brick with no chance of restoring the device without an authorised account or going to a Mi Service Centre.
If you are currently on the MIUI Oreo ROM:
You may ONLY use TWRP 3.3.0 OR 3.2.3-0 OR 3.2.3-1
The recovery by either TWRP or LR.Team is both ok.
If you are on the PIE rom:
You MUST use TWRP 3.3.1 or OrangeFox Recovery. R10.0-2 nocrypt Pie is confirmed to be working by me.
To root MIUI pie, follow the instructions in this post from 4PDA. This is because you will be unable to decrypt data.
You need to create an account to download the patched boot.img. You can either create one yourself or ask me or someone else to PM you with the boot.img. I will not attach it to this thread because it is not my work. The files have now been attached. See post below.
All credits go towards the respective recovery authors and 4pda
OK here are the boot files from 4pda
You MUST follow the instructions from this guide: http://4pda.ru/forum/index.php?showtopic=907017&st=5020#entry87853533
All files obtained from 4pda.ru - from a post by MCMXCII
Full credits go towards the authors of the respective .imgs
I did something wrong just don't know what
I tried with OrangeFox and when rebooted in recovery the phone would not turn on and just vibrates.
I was lucky because I just needed to open and remove the battery to get the phone back up.
So just to get it right (please correct me if i'm wrong):
Starting from unlocked MIUI stock with android 8.1 base:
0) Download patched boot image from OP
1)Download TWRP 3.3.0 OR 3.2.3-0 OR 3.2.3-1
2)Download Magisk 19.3 Stable (would the latest stable also work https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445?)
3)Download official Pie Rom: http://bigota.d.miui.com/V10.4.4.0.PCGMIXM/miui_HM6Global_V10.4.4.0.PCGMIXM_99304098f7_9.0.zip
4)Enter Fastboot -> Flash TWRP
5)Enter TWRP -> Flash the Pie Rom -> Flash patched boot.img -> flash Magisk
6)Boot into system -> Leave the device alone for 2-3 minutes and install Magisk Manager
7)Download -> TWRP 3.3.1 or OrangeFox Recovery. R10.0-2
8)Enter Fastboot -> Flash TWRP/OrangeFox
would this be the correct procedure?
cheers
snoerme said:
So just to get it right (please correct me if i'm wrong):
Starting from unlocked MIUI stock with android 8.1 base:
1)Download TWRP 3.3.0 OR 3.2.3-0 OR 3.2.3-1
2)Download Magisk 19.3 Stable (would the latest stable also work https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445?)
3)Download official Pie Rom: http://bigota.d.miui.com/V10.4.4.0.PCGMIXM/miui_HM6Global_V10.4.4.0.PCGMIXM_99304098f7_9.0.zip
4)Enter Fastboot -> Flash TWRP
5)Enter TWRP -> Flash the Pie Rom -> flash Magisk
6)Boot into system -> Leave the device alone for 2-3 minutes and install Magisk Manager
7)Download -> TWRP 3.3.1 or OrangeFox Recovery. R10.0-2
8)Enter Fastboot -> Flash TWRP/OrangeFox
cheers
Click to expand...
Click to collapse
?????????????????????
Why don't you skip steps 1-3 and just use XiaoMi Flash to install 10.4.4.0 via Fastboot by 'saving user data', then follow the instructions here? XiaoMiFlash will overwrite your recovery with the default so there is no risk of a brick. Then Flash TWRP Pie, flash boot img, flash magisk.
As I have said, you will brick your device. If you have TWRP Oreo, and then you install MIUI Pie, you will brick your device. You are doing EXACTLY what I told you not to do!
It didn't come out as clearly as you think. maybe it's my own deficiency.
btw whenever i flashed any update via TWRP the recovery got replaced by stock recovery as well.
(I don't tell this to call into question that your suggested way of doing was the most safe way.)
Is XiaoMi Flash available for linux as well?
edit: do you know if the latest magisk stable 20.0 would also work?
snoerme said:
It didn't come out as clearly as you think. maybe it's my own deficiency.
btw whenever i flashed any update via TWRP the recovery got replaced by stock recovery as well.
(I don't tell this to call into question that your suggested way of doing was the most safe way.)
Is XiaoMi Flash available for linux as well?
Click to expand...
Click to collapse
I'm not sure - I have never flashed any MIUI ROM in TWRP. It seems normal though - the updaterscript probably tells TWRP to overwrite itself.
https://forum.xda-developers.com/android/software/tool-miflash-linux-t3708847 It's a bit complicated
This work for me :
1 - Install Pie Rom https://bigota.d.miui.com/V10.4.4.0.PCGMIXM/miui_HM6Global_V10.4.4.0.PCGMIXM_99304098f7_9.0.zip with TWRP 3.3.1 https://mifirm.net/downloadtwrp/62 or with another method.
2 - Shut down the phone , go to fastboot (Vol - and power), plug to computer.
3 - From the computer fastboot flash boot boot_10.4.4.0_R6_mgsk_193.img (see the second post of this thread).
4 - fastboot flash recovery recovery-TWRP-3.3.1-0602-REDMI6-CN-wzsx150.img
5 - Recovery (Vol+ and power)
6 - Install Magisk 19.3
Reboot and enjoy
Hi, currently I'm on stable China mui v10.4.3.0. Do you have boot.img on that v10.4.3.0. Currently link only provide boot.img for v10.4.2.0 for the china version. If no how do I get those, can I just backup them from twrp, Then create patched boot img with those backup boot? Thanks
Che0063 said:
OK here are the boot files from 4pda
You MUST follow the instructions from this guide: http://4pda.ru/forum/index.php?showtopic=907017&st=5020#entry87853533
All files obtained from 4pda.ru - from a post by MCMXCII
Full credits go towards the authors of the respective .imgs
Click to expand...
Click to collapse
Thanx for boot_10.4.4.0_R6_mgsk_193.img :good:
ribou said:
This work for me :
1 - Install Pie Rom https://bigota.d.miui.com/V10.4.4.0.PCGMIXM/miui_HM6Global_V10.4.4.0.PCGMIXM_99304098f7_9.0.zip with TWRP 3.3.1 https://mifirm.net/downloadtwrp/62 or with another method.
2 - Shut down the phone , go to fastboot (Vol - and power), plug to computer.
3 - From the computer fastboot flash boot boot_10.4.4.0_R6_mgsk_193.img (see the second post of this thread).
4 - fastboot flash recovery recovery-TWRP-3.3.1-0602-REDMI6-CN-wzsx150.img
5 - Recovery (Vol+ and power)
6 - Install Magisk 19.3
Reboot an denjoy
Click to expand...
Click to collapse
ThanX ! ! !
This work for me :good:
EDIT:
The flashlight and the camera does not work after flash the boot boot_10.4.4.0_R6_mgsk_193.img [emoji848]
Does anyone else have a similar problem?
View attachment 4862683
I have the camera and flashlight problem too. Any fix?
Unfortunately, I didn't find any solution.
Currently, my phone does not start, has a black screen and vibrates all the time. I can't run it in any way
EDIT:
Hi.
I was able to bring the phone to life. Get instructions on how to get to the battery https://www.youtube.com/watch?v=L9FH88b16bc https://www.youtube.com/watch?v=fAflA4UKLLY. In orangeFox recovery I checked the flashlight, it works.
That makes us two. My phone is unusable at the moment. I thought the root was responsible for the camera bugs, I uninstalled magisk, the bug was still there. I tried to reinstall MIUI 10.4.4 ang got an error. I've wiped everything including vendor and system.
I clean dalvik and cache and for now the phone is working even, after flash the patch boot.img
ribou said:
This work for me :
1 - Install Pie Rom https://bigota.d.miui.com/V10.4.4.0.PCGMIXM/miui_HM6Global_V10.4.4.0.PCGMIXM_99304098f7_9.0.zip with TWRP 3.3.1 https://mifirm.net/downloadtwrp/62 or with another method.
2 - Shut down the phone , go to fastboot (Vol - and power), plug to computer.
3 - From the computer fastboot flash boot boot_10.4.4.0_R6_mgsk_193.img (see the second post of this thread).
4 - fastboot flash recovery recovery-TWRP-3.3.1-0602-REDMI6-CN-wzsx150.img
5 - Recovery (Vol+ and power)
6 - Install Magisk 19.3
Reboot an denjoy
Click to expand...
Click to collapse
Hello this is the steps i did but when rebooting to recovery i end up on blackcreen or mai i say powered off screen with the device unable to boot to recovery,any ideas what i did wrongly?
It seems there is something wrong with that boot patch. I followed a procedure on youtube and my phone is succesfully rooted without any bug
@ambyy
what guide did you use on YouTube?
Wysłane z mojego Redmi 6 przy użyciu Tapatalka
https://www.youtube.com/watch?v=I_4Zmco9R78&t=25s
Hard brick caused by flashing wrong TWRP is indeed able to get solved with unplugging the battery.
Miui v11 boot.img please
hello fellas , i have s10 ,problem : always booting up to recovery mode ( couldn`t find solution for it )
,,,, oem is locked and there is no way i can flash twrp or custom rom off course ( btw i am noob)
i tried flashing combination rom using odin ( just to enable usb debugging ) but many msesages of (please get the approval ) for pit ,bootloader, system ...etc
googled the issue , found someone saying it is sort of protection that requires unique key should be requested from samsung
So , how can in bypass it to make successful combination rom flashing ?
any extra files needed plus to the combination rom and pit file ?
please help me out
note : repeat: my phone is oem locked , at flashing stock rom is success but reboots directly to recovery mode ...this is my major problem ,
if anyone can post me sm-g973f (bit15) adb enabler file ?????
it might help
if you guys can hand me in either of those it will be deeply appreciated
thank you all
giants....does combination flashing successful with test points ? and where can i find them inside s10 ?
Hello Rossen, since you have no experience in this area, I know a lot of things that I took the simplest for my S10 exons SM-G973 F. Installation. John WU the official firmware with magisk modify AP official firmware that you transfer to your S10, then once do you transfer magisk patches with Adb to your PC with Adb pull.
Then with Odin you flash the following 4 files BL-AP magisk patched-Cp-Home CSC you let start, you open magisk active Zygisk restarted if rooted...
I forgot TRWP even if I managed once to install it with magisk then bugs and loss of rooting following updating magisk, normally to install TRWP you must already be rooted with magisk then install TRWP either by modify TRWP image with magisk or by the managed TRWP application you directly flash the TRWP image of the application.
https://topjohnwu.github.io/Magisk/install.html
meric57 said:
Hello Rossen, since you have no experience in this area, I know a lot of things that I took the simplest for my S10 exons SM-G973 F. Installation. John WU the official firmware with magisk modify AP official firmware that you transfer to your S10, then once do you transfer magisk patches with Adb to your PC with Adb pull.
Then with Odin you flash the following 4 files BL-AP magisk patched-Cp-Home CSC you let start, you open magisk active Zygisk restarted if rooted...
I forgot TRWP even if I managed once to install it with magisk then bugs and loss of rooting following updating magisk, normally to install TRWP you must already be rooted with magisk then install TRWP either by modify TRWP image with magisk or by the managed TRWP application you directly flash the TRWP image of the application.
https://topjohnwu.github.io/Magisk/install.html
Click to expand...
Click to collapse
thanks for reply , sadly the device can take only the stock rom , any custom will be rejected due to oem lock , and if i flashed stock one it will boot up to recovery not the system ,
So you haven't done the unlocking of oem well you can't do anything, the best thing to do is redo these cleanly you reflash the official rom then you unlock your S10 you press power plus bixby and you connect to the pc, then you press and hold volume up and unlocking is done.
Then you will restart as at the first start you install magisk, activate developer mode about the phone press on low version 7 times then in developer you activate USB debugging.
And you do as I explained.
meric57 said:
So you haven't done the unlocking of oem well you can't do anything, the best thing to do is redo these cleanly you reflash the official rom then you unlock your S10 you press power plus bixby and you connect to the pc, then you press and hold volume up and unlocking is done.
Then you will restart as at the first start you install magisk, activate developer mode about the phone press on low version 7 times then in developer you activate USB debugging.
And you do as I explained.
Click to expand...
Click to collapse
already said when i flash stock rom device turns up to recovery mode not to the system . the only thing i see is flashing combinations which is now impossible without token , is there a trick or workaround to bypass getting in the recovery mode after flashing stock ?
put device in download mode start from scratch with odin official firmware
meric57 said:
put device in download mode start from scratch with odin official firmware
Click to expand...
Click to collapse
like i said before , successful flashing stock rom , after that the mobile goes to recovery mode not to the system
Hello Rose, I had the concern like you these for its that it is necessary to start from zero. I also did like you too when I start with power back TRWP direct, I had to reinstall official rom Android 12, use which TRWP for your S10 exynos the one the twrp-3.6.2_9-2-beyond1lte.img yes or no you know that you have to patch its image with magisk 25.2 then rename it in recovery and replace the one in AP with the recovery modify then flash with odin.
In your quote start with TRWP then you take the boot.img of the AP flashed it then try to restart in recovery.
watch this video
i dont have active android in my device and it can NOT boot up to system if i flashed stock
before stupidly activate oem lock i had zero problems , locked oem and flashed stock and then i got recovery interface , can not log in system
i have LG 4k tv which i messed its software , but managed to reset it all by shorting pins >>> can it be done the same way with my s10 ? if yes , anyone can show me where circuit shorting pins are ?
not at all the only thing to do if you manage to boot trwp recovery in boot do boot download and flash the official rom with csc and not home
meric57 said:
not at all the only thing to do if you manage to boot trwp recovery in boot do boot download and flash the official rom with csc and not home
Click to expand...
Click to collapse
not working ,,,, any instructions or updates to flash factory binary without fail via odin ?
googled to download sboot to fix the whole thing , no luck , can anyone attach it here please ? bit15 (uf protection)
Hello Roseen, so how does your S10 react starting on TRWP or getting stuck on the Samsung logo. I don't see that you tried to do things without having looked at the tutorials on XDA. well a 4G exynos G973F you have the Android 12 UI 4.1 rom.
Does your pc recognize the S10 when it starts up, did you get the message in red safety e and the yellow triangle plus the message, at worst try with another smartphone to film the start-up.
What does your last post mean with bit15.
I put you the link for the tutorial s 10 of the forum
Tutorial : Root Galaxy S10 Series Android 12 One UI 4.1 Stock Firmware
Root Samsung Galaxy S10 Series Android 12, WITHOUT Ramdisk Root Samsung S10+ - S10 - S10e SM-G97xxx, Stock Rom Android 12 - UI 4.1 Latest Version (I tested G970FXXSGHWC2) (Without combination keys for active Magisk after normal restart –...
forum.xda-developers.com