I unlocked phone as normal and flashed twrp to slots A and B but in twrp it shows no internal storage, I tried every solution, but nothing worked. Only thing that worked was flashing xiaomi.eu stable via fastboot. When I enter twrp with xiaomi.eu flashed all files are shown, but i can't boot back into system (after restart it comes back to twrp). I don't really know what to do I can stick to stable xiaomi.eu, but I can't update it, I can't install any other custom rom, and MiFlash as always throws errors left and right. It's my first dual slot phone, before I didn't have any problems with other Xiaomi devices. I hope someone can help, things I tried:
-wipe everything
-change file format
-relock bootloader
-reflash twrp
-flashing different twrp
Thanks in advence if someone manage to help.
EDIT
I bought USB OTG adapter and can flash from usb stick, only problem is that i can't transfer files from PC to phone while in twrp.
Debeciak said:
I unlocked phone as normal and flashed twrp to slots A and B but in twrp it shows no internal storage, I tried every solution, but nothing worked. Only thing that worked was flashing xiaomi.eu stable via fastboot. When I enter twrp with xiaomi.eu flashed all files are shown, but i can't boot back into system (after restart it comes back to twrp). I don't really know what to do I can stick to stable xiaomi.eu, but I can't update it, I can't install any other custom rom, and MiFlash as always throws errors left and right. It's my first dual slot phone, before I didn't have any problems with other Xiaomi devices. I hope someone can help, things I tried:
-wipe everything
-change file format
-relock bootloader
-reflash twrp
-flashing different twrp
Thanks in advence if someone manage to help.
Click to expand...
Click to collapse
You relock the bootloader, with Xiaomi.eu ??
Are you able to get to TWRP?
If you are not able to use TWRP, find Xiaomi repair center to revive your device.
pl1992aw said:
You relock the bootloader, with Xiaomi.eu ??
Are you able to get to TWRP?
If you are not able to use TWRP, find Xiaomi repair center to revive your device.
Click to expand...
Click to collapse
I relocked and unlocked bootloader while there was no rom installed
I can enter twrp but i can't flash roms because internal storage is 0mb and on pc it's show unknow storage amount.
TWRP is in alpha
Debeciak said:
I relocked and unlocked bootloader while there was no rom installed
I can enter twrp but i can't flash roms because internal storage is 0mb and on pc it's show unknow storage amount.
Click to expand...
Click to collapse
Go into fastboot and boot twrp
Code:
fastboot boot twrp_file_name.img
Then format data
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After it's done, reboot to fastboot and run the above command again to get to TWRP.
See if this help.
pl1992aw said:
Go into fastboot and boot twrp
Code:
fastboot boot twrp_file_name.img
Then format data
After it's done, reboot to fastboot and run the above command again to get to TWRP.
See if this help.
Click to expand...
Click to collapse
As I said I tried to wipe everything (including format data), pretty much everything that is on forum i tried it.
Robert314 said:
TWRP is in alpha
Click to expand...
Click to collapse
So it is twrp fault? And if it is will it maybe work in future?
Then MiFlash is your hope.
Use the 20210226 version.
Do not lock bootloader in MiFlash.
Post screenshots what error it's showing to you, so people know what it means.
pl1992aw said:
Then MiFlash is your hope.
Use the 20210226 version.
Do not lock bootloader in MiFlash.
View attachment 5345137
Post screenshots what error it's showing to you, so people know what it means.
Click to expand...
Click to collapse
Phone is stuck on POCO screen right now. I used offical eea rom.
Debeciak said:
Phone is stuck on POCO screen right now. I used offical eea rom.
Click to expand...
Click to collapse
Same as this:
https://forum.xda-developers.com/t/4284821/page-2#post-85174225
The answer to that problem from user:
https://forum.xda-developers.com/t/4284821/post-85174245
pl1992aw said:
Same as this:
https://forum.xda-developers.com/t/4284821/page-2#post-85174225
The answer to that problem from user:
https://forum.xda-developers.com/t/4284821/post-85174245
Click to expand...
Click to collapse
But my phone didn't reboot into setup, it's stuck on logo and isn't starting.
Debeciak said:
But my phone didn't reboot into setup, it's stuck on logo and isn't starting.
Click to expand...
Click to collapse
Wait for it.
It takes some time for first booting. (wait 10 minutes)
pl1992aw said:
Wait for it.
It takes some time for first booting.
Click to expand...
Click to collapse
I waited for like 15 minutes and I'm pretty sure the phone vibrates from time to time.
Debeciak said:
I waited for like 15 minutes and I'm pretty sure the phone vibrates from time to time.
Click to expand...
Click to collapse
I also am trying to download latest official rom but server is very bad and it's pretty slow.
Debeciak said:
I also am trying to download latest official rom but server is very bad and it's pretty slow.
Click to expand...
Click to collapse
You said your phone works if flashing xiaomi.eu stable via fastboot.
Maybe try Xiaomi.eu again, at least getting a working phone.
Then use the built-in updater to update. Hope this work.
pl1992aw said:
You said your phone works if flashing xiaomi.eu stable via fastboot.
Maybe try Xiaomi.eu again, at least getting a working phone.
Click to expand...
Click to collapse
I guess that's my only option but it's not ideal and I can only flash the one stable version that is avaible via fastboot. Thanks for trying to help if latest official won't work with MiFlash im gonna use xiaomi.eu. Maybe in the future twrp update will solve that issue.
Debeciak said:
I guess that's my only option but it's not ideal and I can only flash the one stable version that is avaible via fastboot. Thanks for trying to help if latest official won't work with MiFlash im gonna use xiaomi.eu. Maybe in the future twrp update will solve that issue.
Click to expand...
Click to collapse
Try the built-in updater to update.
I read somewhere here saying you can flash update zip through built-in updater. (Tap the MIUI 12 icon a few times)
Read from Xiaomi.eu tutorial to update:
https://xiaomi.eu/community/threads...all-xiaomi-eu-rom-for-xiaomi-redmi-k40.60379/
If following their tutorial but you still cannot update, you can ask them how to, or read some replies there to see if there's similar cases.
pl1992aw said:
Try the built-in updater to update.
I read somewhere here saying you can flash update zip through built-in updater. (Tap the MIUI 12 icon a few times)
Read from Xiaomi.eu tutorial to update:
https://xiaomi.eu/community/threads...all-xiaomi-eu-rom-for-xiaomi-redmi-k40.60379/
If following their tutorial but you still cannot update, you can ask them how to, or read some replies there to see if there's similar cases.
Click to expand...
Click to collapse
The tutorial is how to update in case rom is fastboot variant since twrp is avaible xiaomi.eu roms are twrp only. It's working fine I will wait for new twrp version and then try.
Worst thing is that I can't go back to stock rom.
I went through something like this as well.
As long as you can boot into fastboot. Then no worries. Just Flash the official stockrom. If something goes wrong. Reboot into fastboot (everytime you do something through fastboot. If you keep doing multiple processes, you'll keep having errors, always. Well that's what I went through. Rebooting into fastboot fixed my problem)
But your last pic declares that it was successfully flashed though.
Debeciak said:
The tutorial is how to update in case rom is fastboot variant since twrp is avaible xiaomi.eu roms are twrp only. It's working fine I will wait for new twrp version and then try.
Worst thing is that I can't go back to stock rom.
Click to expand...
Click to collapse
When u flash xiaomi.eu, u set up the pin/pattern code in order to decrypt the internal storage in twrp?
Idk what's happening there.
It's just, flash xiaomi.eu via fastboot, boot it and set up pin/pattern code, fastboot boot twrp.img, go to twrp, insert the pin or pattern to decrypt internal storage and flash the latest update from xiaomi eu, simple as that..
And I don't get what's the A or B slot thing, I didn't had to chose or touch any of that, I saw that thing in twrp but didn't touched it..
Related
Fastboot rom install with
-miflashtool
6.6.3 GLOBAL Official Alpha Fastboot rom
6.6.3 eu_multi -Unofficial Global rom (install with twrp revovery )
6.6.3 china twrp alpha rom
6.5.31 fastboot rom Download
miui7
6.5.30 Global fastboot rom
6.5.30 Global TWRP rom
7.2.9 Global Stable Fastboot Rom
6.5.20 Global TWRP Beta Rom
install with TWRP (please dont try with system updates>choose packet)
murattiy said:
6.5.20 global beta
https://drive.google.com/file/d/0B2UMSvqNe0deY0h3YW1aX20wdDQ/view?usp=sharing
https://youtu.be/xadfdqTrnjo
Click to expand...
Click to collapse
Where did you take it? There is no post in xiaomi official forum. And how to install it over 7.2.4 global?
Thanks
murattiy said:
6.5.20 global beta
https://drive.google.com/file/d/0B2UMSvqNe0deY0h3YW1aX20wdDQ/view?usp=sharing
https://youtu.be/xadfdqTrnjo
Click to expand...
Click to collapse
There is also a official URL: http://bigota.d.miui.com/6.5.20/miui_MI5Global_6.5.20_e785fae0e6_6.0.zip
---------- Post added at 13:37 ---------- Previous post was at 13:35 ----------
giardux91 said:
Where did you take it? There is no post in xiaomi official forum. And how to install it over 7.2.4 global?
Thanks
Click to expand...
Click to collapse
It should be flashable in fastboot mode or at least in EDL mode with the latest MiuiFlash.
shade.sh said:
There is also a official URL: http://bigota.d.miui.com/6.5.20/miui_MI5Global_6.5.20_e785fae0e6_6.0.zip
---------- Post added at 13:37 ---------- Previous post was at 13:35 ----------
It should be flashable in fastboot mode or at least in EDL mode with the latest MiuiFlash.
Click to expand...
Click to collapse
But the rom doesn't seem to be fastboot version. Infact I try and it's possible to install it with updater app, but the system says that it is an older version of stable.
giardux91 said:
But the rom doesn't seem to be fastboot version. Infact I try and it's possible to install it with updater app, but the system says that it is an older version of stable.
Click to expand...
Click to collapse
You're right... looks like a OTA or something image... i don't have my Mi5 with me to check if you can flash it via TWRP.
shade.sh said:
You're right... looks like a OTA or something image... i don't have my Mi5 with me to check if you can flash it via TWRP.
Click to expand...
Click to collapse
The strange thing is that this rom doesn't exist on xiaomi forum.
giardux91 said:
The strange thing is that this rom doesn't exist on xiaomi forum.
Click to expand...
Click to collapse
There was a thread in the English forum, but was deleted very quick:
http://webcache.googleusercontent.c...94-1-1.html&gws_rd=cr&ei=JaFBV5alFIX7UpfbgOgE
shade.sh said:
There was a thread in the English forum, but was deleted very quick:
http://webcache.googleusercontent.c...94-1-1.html&gws_rd=cr&ei=JaFBV5alFIX7UpfbgOgE
Click to expand...
Click to collapse
I think it's not safe to install it, what do you think about?
giardux91 said:
I think it's not safe to install it, what do you think about?
Click to expand...
Click to collapse
Well, i never had it installed, so i cannot say anything about it... maybe the thread starter could say something about it
We only know its not "official" available.
I flashed it and am using it since yesterday. So far I haven't encountered any issues but I'm kind of put off by the state of their ROMs for this phone currently and hence haven't exactly 'tested' anything out.
The thread on the Chinese forum is still alive but they aren't letting people post it International apparently.
http://www.miui.com/thread-4296538-1-1.html
In case anyone needs info how to install it -> installed it via Updater which brings you to TWRP, after which the devices was decrypting and after it installed as any other update. Took about 20mins. Installed it "over" xiaomi.eu_multi_gemini_6.5.19_v7-6.0.zip
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This rom rewrites recovery to the stock one and decrypts data. I re-flashed twrp recovery but in twrp it asks me for password to access/decrypt the data (the data thats on the phone, such as TWRP backups and other ROM .zip's) ? I have no lock screen/no password on my phone. Tried booting in system and setting lock screen password and using that in TWRP but no luck. Tried "default password" but it does not work. I wan't to restore other version of en.miui rom, but I can't access it via TWRP now. Any ideas for the password or way around? I am too lazy to reflash MiFLash version of 6.4.21 and then copy my TWRP backups onto the phone..
jemeljsh said:
This rom rewrites recovery to the stock one and decrypts data. I re-flashed twrp recovery but in twrp it asks me for password to access/decrypt the data (the data thats on the phone, such as TWRP backups and other ROM .zip's) ? I have no lock screen/no password on my phone. Tried booting in system and setting lock screen password and using that in TWRP but no luck. Tried "default password" but it does not work. I wan't to restore other version of en.miui rom, but I can't access it via TWRP now. Any ideas for the password or way around? I am too lazy to reflash MiFLash version of 6.4.21 and then copy my TWRP backups onto the phone..
Click to expand...
Click to collapse
Check over at the MIUI forums, I think someone mentioned this issue and how to fix it. I have locked bootloader so no experience with TWRP on this phone yet.
murattiy said:
6.5.20 global beta
official rom but boot error official rom rom .official rom link : http://bigota.d.miui.com/6.5.20/miui_MI5Global_6.5.20_e785fae0e6_6.0.zip
my link diffirent and working rom.(changed boot.img)
https://drive.google.com/open?id=0B2UMSvqNe0deU0ZkRHcxNUdFMkE
https://youtu.be/xadfdqTrnjo
Click to expand...
Click to collapse
Surprisingly original one works through updater. But in the yesterday morning when nI tried via TWRP it does not worked for me and showed boot.img related error but flashed successfully and device never booted up and stuck on boot logo. Then I flashed 7.2.4.0 again and just for checking I tried to flash manually via updater apps and it works. Unlike other updater ROM this one wiped all data (though I did not have any) and had a clean install.
kamrul.auntu said:
Surprisingly original one works through updater. But in the yesterday morning when nI tried via TWRP it does not worked for me and showed boot.img related error but flashed successfully and device never booted up and stuck on boot logo. Then I flashed 7.2.4.0 again and just for checking I tried to flash manually via updater apps and it works. Unlike other updater ROM this one wiped all data (though I did not have any) and had a clean install.
Click to expand...
Click to collapse
this doesn't look like a fastboot ROM!
Just to add details:
Xiaomi names fastboot Roms with "phone_name"_"version"...
like the Mi5 fastboot Roms are: gemini_images_V....
And Mi5 Recovery ROms are miui_MI5...
So if you tried to flash it as a fastboot ROM it's likely to not work.
---------- Post added at 08:55 AM ---------- Previous post was at 08:53 AM ----------
giardux91 said:
But the rom doesn't seem to be fastboot version. Infact I try and it's possible to install it with updater app, but the system says that it is an older version of stable.
Click to expand...
Click to collapse
I had the similar message when going from 7.3.3.0 China to the latest China developer. I would not mind it.
SavageDamage said:
Check over at the MIUI forums, I think someone mentioned this issue and how to fix it. I have locked bootloader so no experience with TWRP on this phone yet.
Click to expand...
Click to collapse
I could not find the solution to get back to 6.5.19 eu.miui rom. Whatever password options I tried within TWRP data would not unlock/decrypt (tried -> password, default_password, default password, "lock screen password/lock screen pin").
To resolve the issue I:
1. copied contents (including made backups with TWRP 3.0.2) of the phone while booted into the system to my pc 2. reflashed MiFLash version of 6.4.21 eu.miui rom via MiFlash in FastBoot;
3. reflashed TWRP to the one version which matched the version of my TWRP backups (3.0.2)
4. while booted into 6.4.21 eu.miui rom copied TWRP backup from pc to the phone
5. booted into TWRP and restored my TWRP backup.
So the test of this rom version costed my 2 hours :laugh:
TheUltrametricSpace said:
this doesn't look like a fastboot ROM!
Just to add details:
Xiaomi names fastboot Roms with "phone_name"_"version"...
like the Mi5 fastboot Roms are: gemini_images_V....
And Mi5 Recovery ROms are miui_MI5...
So if you tried to flash it as a fastboot ROM it's likely to not work.
Click to expand...
Click to collapse
@TheUltrametricSpace
I never told that it looks like a fastboot ROM kind of a thing! Looking at the inside of zip file also can indicate that which one fastboot or which one is recovery ROM. BTW, I am still waiting for your comment on another of mine thread where I mentioned you. This is, I am not getting mobile network signal most of the times and get it back network barely. Impossible to use the phone. Please help.
I was just trying to say OP that original one (leaked) worked for me through phone updater rather TWRP. TWRP can flash it but firmware don't have ability to boot the device. That is why I 1st rollback to to Global stable 7.2.4.0 and then update this ROM. Even not seen any verification error in the flashing process. But TWRP presented me error in boot.image which OP mentioned. I think this ROM leaked from any closed alpha/beta tester and that is why updater apps not shows any error. If you try to install 7.2.8.0 over 7.2.4.0 recovery ROM it shows verification error.
kamrul.auntu said:
@TheUltrametricSpace
I never told that it looks like a fastboot ROM kind of a thing! Looking at the inside of zip file also can indicate that which one fastboot or which one is recovery ROM. BTW, I am still waiting for your comment on another of mine thread where I mentioned you. This is, I am not getting mobile network signal most of the times and get it back network barely. Impossible to use the phone. Please help.
I was just trying to say OP that original one (leaked) worked for me through phone updater rather TWRP. TWRP can flash it but firmware don't have ability to boot the device. That is why I 1st rollback to to Global stable 7.2.4.0 and then update this ROM. Even not seen any verification error in the flashing process. But TWRP presented me error in boot.image which OP mentioned. I think this ROM leaked from any closed alpha/beta tester and that is why updater apps not shows any error. If you try to install 7.2.8.0 over 7.2.4.0 recovery ROM it shows verification error.
Click to expand...
Click to collapse
ja ja, i wrote this in general. Sorry.
Dunno about the other parts you wrote sorry.
Has anyone tried Global Stable 7.2.9?
Is it possible install ufficial rom over xiaomi.eu rom?
I got a new OnePlus 3 for my dad and the device showed OTA update for august 21. I tried installing it but it showed signature verification error and the OTA could not be installed. Then I tried sideloading the update via adb but the process stops at 47%.
It displays message saying "Total xfer: 1.00x"
I have installed the latest version of adb but to no success.
Help me out guys. Thanks.
Here is the snippet of the error shown by adb
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Dunno for sure but for xiaomi devices you have to unlock your bootloader (for some reason) in order to flash/ota update your phone , plus additional info would be helpfull ,like current ROM you are running
Enviado desde mi ONEPLUS A3000 mediante Tapatalk
marmeak7 said:
I got a new OnePlus 3 for my dad and the device showed OTA update for august 21. I tried installing it but it showed signature verification error and the OTA could not be installed. Then I tried sideloading the update via adb but the process stops at 47%.
It displays message saying "Total xfer: 1.00x"
I have installed the latest version of adb but to no success.
Help me out guys. Thanks.
Here is the snippet of the error shown by adb
Click to expand...
Click to collapse
How does your phone show up under device manager?
marmeak7 said:
I got a new OnePlus 3 for my dad and the device showed OTA update for august 21. I tried installing it but it showed signature verification error and the OTA could not be installed. Then I tried sideloading the update via adb but the process stops at 47%.
It displays message saying "Total xfer: 1.00x"
I have installed the latest version of adb but to no success.
Help me out guys. Thanks.
Here is the snippet of the error shown by adb
View attachment 4281534
Click to expand...
Click to collapse
Try switching the port. The error you mentioned is either due to an incomplete download or an unstable USB connection. Give a try to both.
Puddi_Puddin said:
How does your phone show up under device manager?
Click to expand...
Click to collapse
Device Manager lists the device as ONEPLUS A3003
DJBhardwaj said:
Try switching the port. The error you mentioned is either due to an incomplete download or an unstable USB connection. Give a try to both.
Click to expand...
Click to collapse
I did try switching the ports and I also tried three different zip files just to be sure but the result is still the same. I even tried switching cables but it did not work
demonoid phenomenom said:
Dunno for sure but for xiaomi devices you have to unlock your bootloader (for some reason) in order to flash/ota update your phone , plus additional info would be helpfull ,like current ROM you are running
Enviado desde mi ONEPLUS A3000 mediante Tapatalk
Click to expand...
Click to collapse
I am on stock OOS with Marshmallow 6.0.1 and I am trying to update it to OOS 4.1.7 released on august 21st and I got the device just two days ago. I tried updating via OTA and it presented me with signature verification error and while trying to sideload the OTA, I ended up with the error mentioned above.
marmeak7 said:
I did try switching the ports and I also tried three different zip files just to be sure but the result is still the same. I even tried switching cables but it did not work
Click to expand...
Click to collapse
Have you tried flashing the full ROM zip file via stock recovery?
DJBhardwaj said:
Have you tried flashing the full ROM zip file via stock recovery?
Click to expand...
Click to collapse
The stock recovery does not have the option to flash zip files or am I not seeing the option?
marmeak7 said:
The stock recovery does not have the option to flash zip files or am I not seeing the option?
Click to expand...
Click to collapse
Do you know the process to flash recovery via fastboot?
Here is the latest recovery image: http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img
You will need to use the command: fastboot flash recovery recovery_op3.img
Then reboot into stock recovery to see if an update option for internal storage/local is available. I have a OnePlus 5, so I am not sure if this is specific to the device or just because there's an older recovery version installed.
DJBhardwaj said:
Do you know the process to flash recovery via fastboot?
Here is the latest recovery image: http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img
You will need to use the command: fastboot flash recovery recovery_op3.img
Then reboot into stock recovery to see if an update option for internal storage/local is available. I have a OnePlus 5, so I am not sure if this is specific to the device or just because there's an older recovery version installed.
Click to expand...
Click to collapse
I have already tried updating the recovery via fastboot but fastboot was not able to update the recovery as well it displayed an error while flashing via fastboot. I was using the latest recovery available from OnePlus
marmeak7 said:
I have already tried updating the recovery via fastboot but fastboot was not able to update the recovery as well it displayed an error while flashing via fastboot. I was using the latest recovery available from OnePlus
Click to expand...
Click to collapse
Oh.. How about installing TWRP and then flashing the ROM through that?
DJBhardwaj said:
Oh.. How about installing TWRP and then flashing the ROM through that?
Click to expand...
Click to collapse
I guess that is the last resort for me now. I was skeptical about unlocking bootloader since it is my dad's device but I have no option left now.
Anyways thanks for your help ?
marmeak7 said:
I guess that is the last resort for me now. I was skeptical about unlocking bootloader since it is my dad's device but I have no option left now.
Anyways thanks for your help
Click to expand...
Click to collapse
No. Don't worry, unlocking the bootloader is rather a very good choice. Unlocking the bootloader is totally different than root. So, in case you find yourself in such situations, an unlocked bootloader can allow you to do a lot.
Make sure that you take a complete backup of your device first. It will also wipe the internal storage.
DJBhardwaj said:
No. Don't worry, unlocking the bootloader is rather a very good choice. Unlocking the bootloader is totally different than root. So, in case you find yourself in such situations, an unlocked bootloader can allow you to do a lot.
Make sure that you take a complete backup of your device first. It will also wipe the internal storage.
Click to expand...
Click to collapse
plus ,you dont void your warrantie , thanks oneplus!!
Enviado desde mi ONEPLUS A3000 mediante Tapatalk
demonoid phenomenom said:
plus ,you dont void your warrantie , thanks oneplus!!
Enviado desde mi ONEPLUS A3000 mediante Tapatalk
Click to expand...
Click to collapse
Exactly, all courtesy of OnePlus. Not all OEM offer this liberty.
Ok here is the Solution with 100% work.... (Same happened to me also)
Formating some times breaks file system of storage...
So
1. Install Twrp by Blue spark 3.1.1 (you can give a try to official TWRP)
2. Go to wipe and then Repair partitions
3. Repair System partition and Storage partition (it will delete all your data so keep a backup.. I would suggest repair each and every partition using Twrp Repair)
4.Farmat again
5. Your Welcome!
info2shail2010 said:
Ok here is the Solution with 100% work.... (Same happened to me also)
Formating some times breaks file system of storage...
So
1. Install Twrp by Blue spark 3.1.1 (you can give a try to official TWRP)
2. Go to wipe and then Repair partitions
3. Repair System partition and Storage partition (it will delete all your data so keep a backup.. I would suggest repair each and every partition using Twrp Repair)
4.Farmat again
5. Your Welcome!
Click to expand...
Click to collapse
Sorry for the late reply but I am going to try this right now.
Thanks for the help :angel::angel:
marmeak7 said:
Sorry for the late reply but I am going to try this right now.
Thanks for the help :angel::angel:
Click to expand...
Click to collapse
Just in case you run into a brick...?..I did once so I found this thread handy
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
So i encountered this problem a while back, after doing some digging and analyzing adb, i came to the conclusion that adb could only address memory in 32bit on pc, so it couldn't handle the size when sideloading the extracted OS with STOCK recovery. If you want to still do it with stock you will have to do some digging around in forums, i found a software that modded the program to be able to use 64bit memory access. cant give you the link though since it was a while back.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi Guys, i need help, i was playing with my leeco x720 flashing several Rooms, Mooka, Google Experience, after i flash EUI 20 s, flashable zip and the system works well.
After i download anf flash > LEX720-ML_BB72-5902303282S-5.9.023S_Root_V1 , always performing the right wipes etc.
after this ill never be abled to have new system again, i have always the twrp ...
Now when i try to flash again the EUI 20s zip, it seems flash fast , like 4 sec, and on reboot system, first start, stuck on leeco logo.\when i try to flash lineageos 15.1, show error 7.
Plz help.
Update >
i take a recovery backup from another leecco findet online.
o put it on twrp backups, restore it from twrp 3.2.1 ..
first bot crashes many apps on the start messages etcc soo i bot to recovery again, factory reset ...now stuc on EUI logo.
UPDATE :
all the problem can be solved with MAURO Tool or TOOL_ALL_IN_ONE .
for more info go to thread > https://forum.xda-developers.com/le-pro3/development/tool-tool-one-mauronofrio-t3580611
dont forget to thanks @mauronofrio DDDDD
Ferdinantstr said:
Hi Guys, i need help, i was playing with my leeco x720 flashing several Rooms, Mooka, Google Experience, after i flash EUI 20 s, flashable zip and the system works well.
After i download anf flash > LEX720-ML_BB72-5902303282S-5.9.023S_Root_V1 , always performing the right wipes etc.
after this ill never be abled to have new system again, i have always the twrp ...
Now when i try to flash again the EUI 20s zip, it seems flash fast , like 4 sec, and on reboot system, first start, stuck on leeco logo.\when i try to flash lineageos 15.1, show error 7.
Plz help.
Click to expand...
Click to collapse
If ur on latest twrp and 20s+ firmware I would go into fastboot and make sure ur bootloader didn't get locked for some mysterious reason.I doubt it but worth checking.never know.lol...hope u get it fixed.good luck.
marcukial said:
If ur on latest twrp and 20s+ firmware I would go into fastboot and make sure ur bootloader didn't get locked for some mysterious reason.I doubt it but worth checking.never know.lol...hope u get it fixed.good luck.
Click to expand...
Click to collapse
thanks for reply, i have twrp 3.2.1 but no system so i cant verify if my latest is 20s and if boatloader is locked...? you think maybe the boatloaderr its relocked after i flash the EUI 21s stock zip ? .. now i m trying to restore from an twro recovery make from another person..
Lex727 bootloader unlock
1.download bootloader unlock zip.
https://www.mediafire.com/file/nvsw2fhnt1e2q7d/x727-5.8.019s_bootloader-unlock.zip
Have ADB/Fasboot tools on your computer*(I am not helping you here, it you're lucky, maybe your friends will help)Make sure you have enabled the developer tools, turned on USB debugging, and authorized your computer on your device*(again, I'm not helping with that)Make sure adb can see your device when you run "adb devices"Run "adb reboot bootloader"Run "fastboot devices" to make sure you see your deviceRun "fastboot oem unlock-go" to unlock your device temporarilyRun "fastboot oem device-info" to verify unlock statusRun "fastboot boot recovery_twrp.img"*(or whatever the twrp image filename is on your computer)to boot up to TWRP
If this fails you need to flash bootloader.
Fastboot flash emmc_appsboot.mbn.
I person personally did this command and drag and drop file minimal adb program work perfect.
If you need this program here it is.
https://www.mediafire.com/file/9gxfrob1d3idric/minimal_adb_fastboot_v1.4_setup.exe
Sent from my LEX727 using xda premium[/QUOTE]
Sent from my LEX720 using xda premium
If you need stock OS, you have to install stock recovery;
https://forum.xda-developers.com/le-pro3/how-to/guide-simple-to-return-to-stock-x720-t3618658
If you need custom ROM, you have to flash correct recovery (3.2 is good for Oreo, earlier for Nougat). In twrp you should to transfer correct file, or try to adb push commands (googling for it).
Ferdinantstr said:
thanks for reply, i have twrp 3.2.1 but no system so i cant verify if my latest is 20s and if boatloader is locked...? you think maybe the boatloaderr its relocked after i flash the EUI 21s stock zip ? .. now i m trying to restore from an twro recovery make from another person..
Click to expand...
Click to collapse
Possibly. Go to fastboot and type fastboot oem device-info to check.
marcukial said:
Possibly. Go to fastboot and type fastboot oem device-info to check.
Click to expand...
Click to collapse
Thank U, ill try after the FQL mode...if dont work..ill do this..thnx.:good::good::good::good:
ps, the first method didnt work, now i verify on adb, is <
(bootloader) Device unlocked: true
so ok now i have to flash twrp again and after flash supersu, after flash an normal room ?
Ferdinantstr said:
Thank U, ill try after the FQL mode...if dont work..ill do this..thnx.:good::good::good::good:
Click to expand...
Click to collapse
ps, the first method didnt work, now i verify on adb, is <
(bootloader) Device unlocked: true
so ok now i have to flash twrp again and after flash supersu, after flash an normal room ?
Ferdinantstr said:
ps, the first method didnt work, now i verify on adb, is <
(bootloader) Device unlocked: true
so ok now i have to flash twrp again and after flash supersu, after flash an normal room ?
Click to expand...
Click to collapse
AFTER I flash the twrp and supersu, i copy the room files to internal storage
, the problem persist .. .
Ferdinantstr said:
AFTER I flash the twrp and supersu, i copy the room files to internal storage
, the problem persist .. .
Click to expand...
Click to collapse
Try format data in twrp maybe if u haven't tried.and don't flash SuperSU until after u flash a rom like lineage or aicp etc.I would stay clear of flashing stock factory ROMs in twrp unless it has been modded to flash in twrp.
marcukial said:
Try format data in twrp maybe if u haven't tried.and don't flash SuperSU until after u flash a rom like lineage or aicp etc.I would stay clear of flashing stock factory ROMs in twrp unless it has been modded to flash in twrp.
Click to expand...
Click to collapse
always 7 error., on twrp, dont letme flash lineageos or stock rooms.
Ferdinantstr said:
always 7 error., on twrp, dont letme flash lineageos or stock rooms.
Click to expand...
Click to collapse
Try to flash a different rom.
Sent from my LEX727 using xda premium
mchlbenner said:
Try to flash a different rom.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
ill try 4 different rooms so i dont think is room problems . .
the last i try pixel experience.. and the same.
start flashing and endo after 2 seconds with the indication >
flashing system files...
flashing boot image..
script succeded > resulta was (1.000000)
updating partiton details....
done... ]
THE SAME LIKE THE OTHER ROOMS.... i think i do something wrong,,but i dont know what../:crying:
Followed my guide? You should go to stock, then do all the process again.
Ferdinantstr said:
ill try 4 different rooms so i dont think is room problems . .
the last i try pixel experience.. and the same.
start flashing and endo after 2 seconds with the indication >
flashing system files...
flashing boot image..
script succeded > resulta was (1.000000)
updating partiton details....
done... ]
THE SAME LIKE THE OTHER ROOMS.... i think i do something wrong,,but i dont know what../:crying:
Click to expand...
Click to collapse
I have the exact same problems, my device is completly useless right now :crying:
StormPlayzz said:
I have the exact same problems, my device is completly useless right now :crying:
Click to expand...
Click to collapse
Go back to twrp 3.2.0.0
Sent from my LEX727 using xda premium
mchlbenner said:
Go back to twrp 3.2.0.0
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
Where to find that?
StormPlayzz said:
Where to find that?
Click to expand...
Click to collapse
This should be it.
I don't use the news one
https://www.mediafire.com/file/0hhywv26neg86q1/recovery.zip
Sent from my LEX727 using xda premium
mchlbenner said:
This should be it.
I don't use the news one
https://www.mediafire.com/file/0hhywv26neg86q1/recovery.zip
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
Still getting Error 7
All Praise And All Thanks To God
Note: Please take full twrp backup of your phone before you proceed with the below steps
Steps for Magisk root:
1. Unlock bootloader if not done yet.
see this guide to unlock:
https://forum.xda-developers.com/realme-3/how-to/guide-bootloader-unlock-guide-realme-3-t3999463
2. Install TWRP in your phone
Follow this guide on installing TWRP on your phone:
https://forum.xda-developers.com/realme-3/development/screen-doesnt-twrp-realme-3-t3944022
3. Boot your phone to TWRP.
4. Install magisk-release.zip using TWRP
5. Reboot, Done
6. Refer this for Magisk lagging Fix:
https://forum.xda-developers.com/android/general/magisk-lagging-issue-fix-t4012863/
Links:
Magisk: https://github.com/topjohnwu/Magisk/releases
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
------------------------------------------------------------------------------------------------------------------------------------------------------
OLD Method, Only root shell access, Please follow the above method for rooting , this method is only for reference to help get root access shell for new Realme and oppo phones launched in market
Steps to get Root Shell access in Realme 3, I have tested it on my phone, it works:
Part 1:
1. Unlock bootloader if not done yet.
see this guide to unlock:
https://forum.xda-developers.com/realme-3/how-to/bootloader-unlock-realme-3guide-t3920394
2. Commands to Execute:
adb reboot bootloader
fastboot erase system
fastboot -w (this will erase all the userdata)
fastboot flash system system_adbroot.img
fastboot reboot
3. let the system reboot and do the following command (Also Enable USB Debugging if not enabled):
adb shell
4. Now you have shell root access
System image with root shell access:
https://www.androidfilehost.com/?fid=1395089523397966779
Stock System image:
https://www.androidfilehost.com/?fid=1395089523397966778
Note: If you want to unroot the shell access, just flash back the Stock system image.
--------------------------------------------------------------------------------------------------------------------------------------
Credits:
1. Bjoern Kerler
For reverse engineering the ozip keys
Link to Bjoern Kerler's Github repo: https://github.com/bkerler/oppo_ozip_decrypt
Link to his awesome ozip reverse engineering guide:
https://bkerler.github.io/reversing/2019/04/24/the-game-begins/
2. @topjohnwu
For Magisk and adding full system as root support in it
3. @haditriw
For Testing all other realme 3 stuff without fear of getting hard brick and helping in the development of Realme 3, when no one is ready to help.
For real??
Keep up the good work mate
after fastboot flash boot magisk_patched.img,then fastboot reboot,now my realme 3 got bootloop,any advice?
myeganz said:
after fastboot flash boot magisk_patched.img,then fastboot reboot,now my realme 3 got bootloop,any advice?
Click to expand...
Click to collapse
I have been advised that this phone should rebooted ONLY with power switch and never from fastboot instruction...
May be I am wrong...?
Anyway you have to flash OZIP rom (may be only update) in order to reset the phone.
Hope that work.
If this is correct, OP will add BIG advice in opening post.
EDIT:
I see the stock boot link in first post op, did you try to flash it back?
myeganz said:
after fastboot flash boot magisk_patched.img,then fastboot reboot,now my realme 3 got bootloop,any advice?
Click to expand...
Click to collapse
I am not sure, currently don't have phone to test on,
see this guide:
https://forum.xda-developers.com/realme-3/how-to/realme-3-recover-soft-brick-boot-loop-t3920401
After you get the phone working properly, Instead of fastboot flash boot magisk_patched.img , try fastboot boot magisk_patched.img and follow the next steps written in instructions
Fastboot boot magisk_patched.img command doesn't work. My Realme 3 still boots normally and have no root access for Magisk Manager to install Magisk as direct install.
ReveHavan said:
Fastboot boot magisk_patched.img command doesn't work. My Realme 3 still boots normally and have no root access for Magisk Manager to install Magisk as direct install.
Click to expand...
Click to collapse
I have updated the guide
fawazahmed0 said:
I have updated the guide
Click to expand...
Click to collapse
I feel afraid to flash my boot.img with the patched img. I don't quite understand how it boots differently between fastboot reboot and by pressing manual power button. Has anyone tried flashing the Realme 3 stock boot.img when having bootloop? Is the stock boot.img for Realme 3 3/32 and 4/64 the same?
Does this work on 3/64 variant?
ReveHavan said:
I feel afraid to flash my boot.img with the patched img. I don't quite understand how it boots differently between fastboot reboot and by pressing manual power button. Has anyone tried flashing the Realme 3 stock boot.img when having bootloop? Is the stock boot.img for Realme 3 3/32 and 4/64 the same?
Click to expand...
Click to collapse
The boot image is extracted from ozip file for Realme 3, There is only one ozip for both 3gb and 4gb variant , So it should work
yametekudasai said:
Does this work on 3/64 variant?
Click to expand...
Click to collapse
Yes, it should work
fawazahmed0 said:
Yes, it should work
Click to expand...
Click to collapse
Ok thank you maybe ill root after few months just to be sure.
ReveHavan said:
. I don't quite understand how it boots differently between fastboot reboot and by pressing manual power button. ?
Click to expand...
Click to collapse
Even I don't know, but in Realme U1 doing 'fastboot reboot' will cause bootloop, so same applies here.
See this: https://forum.xda-developers.com/android/help/method-rooting-realme-u1-t3916683/
fawazahmed0 said:
Even I don't know, but in Realme U1 doing 'fastboot reboot' will cause bootloop, so same applies here.
See this: https://forum.xda-developers.com/android/help/method-rooting-realme-u1-t3916683/
Click to expand...
Click to collapse
Ah I see. I guess I'll try it then. I'll report back the result.
Edit: It bootlooped . My phone displayed the white REALME logo over and over but never went to the animated yellow logo. Thankfully the stock boot.img works. Now my phone boots normally again and it keeps all the apps and data. Still no access to root.
ReveHavan said:
Ah I see. I guess I'll try it then. I'll report back the result.
Edit: It bootlooped . My phone displayed the white REALME logo over and over but never went to the animated yellow logo. Thankfully the stock boot.img works. Now my phone boots normally again and it keeps all the apps and data. Still no access to root.
Click to expand...
Click to collapse
Currently I don't have my phone to test, I got it hardbricked, while trying to build twrp for the phone, I will see into this, when I get my phone back. Thanks for trying and letting me know the recovery steps
ReveHavan said:
Ah I see. I guess I'll try it then. I'll report back the result.
Edit: It bootlooped . My phone displayed the white REALME logo over and over but never went to the animated yellow logo. Thankfully the stock boot.img works. Now my phone boots normally again and it keeps all the apps and data. Still no access to root.
Click to expand...
Click to collapse
Can you try one more time, I have updated the patched boot image , it is patched using magisk beta channel
fawazahmed0 said:
Can you try one more time, I have updated the patched boot image , it is patched using magisk beta channel
Click to expand...
Click to collapse
I did it and the result was exactly the same as before.
ReveHavan said:
I did it and the result was exactly the same as before.
Click to expand...
Click to collapse
Thanks for trying, I think Magisk does not support our phone yet, I will file an issue at Github for bootloop problem, I will wait for my phone, before filing the issue, as it requires logs to submit.
waiting for magisk or twrp too.. i have build smali patcher, but still waiting twrp or magisk patch for install it,,
Ok, so for some reason, my poco f3 global (alioth, miui 12.5.1) is stuck on boot logo (the screen that shows poco f3) after flashing a magisk patched boot image of the same firmware.
I don't have twrp, also adb command to remove magisk doesn't work. any workaround to remove magisk using a fastboot command? :/ any other way? can I install twrp at this stage without losing data?
I am genuinely sick of this device, a part from the very VERY bad quality of the hardware, NFC did not work for me even on stock bl locked firmware, a lot of issues happened when I rooted it for the first time and made me lose data. now today the device updated automatically to miui 12.5.1 and made me lose root despite having all auto update options disabled. I am genuinely considering throwing away this phone if I lose data this time. please help.
just flash a new boot image without magisk from the rom you were flashing.
next time you want magisk just boot the alpha twrp the F3 has and flash magisk as normal from there
metalspider said:
just faslh a new boot image without magisk from the rom you were flashing.
next time you want magisk just boot the alpha twrp the F3 has and flash magisk as normal from there
Click to expand...
Click to collapse
Thanks for the reply, Im on it right now, also curious about the second part, what is the alpha twrp? can you elaborate? As you see I mentioned having not installed twrp.
Ghostface009 said:
Thanks for the reply, Im on it right now, also curious about the second part, what is the alpha twrp? can you elaborate? As you see I mentioned having not installed twrp.
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/recovery-alpha-teamwin-recovery-project.4272625/
Code:
Fastboot boot
the TWRP
This way will not install TWRP in the device but can use TWRP.
There's option in Developer option as Automatic system updates.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Free phones welcomed.
pl1992aw said:
https://forum.xda-developers.com/t/recovery-alpha-teamwin-recovery-project.4272625/
Code:
Fastboot boot
the TWRP
This way will not install TWRP in the device but can use TWRP.
There's option in Developer option as Automatic system updates.
Free phones welcomed.
Click to expand...
Click to collapse
That sounds really good. could be useful.
Sadly this option in dev options was already disabled, yet it updated itself automatically. which is the thing that enraged me the most.
Ghostface009 said:
That sounds really good. could be useful.
Sadly this option in dev options was already disabled, yet it updated itself automatically. which is the thing that enraged me the most.
Click to expand...
Click to collapse
As you wrote earlier, you had root access before MIUI update.
Once you get root, use Debloater to debloat the updater.
Code:
com.android.updater
is one of it.
Maybe there's other ones, but I don't have this phone, can't tell much about it.
Ghostface009 said:
Ok, so for some reason, my poco f3 global (alioth, miui 12.5.1) is stuck on boot logo (the screen that shows poco f3) after flashing a magisk patched boot image of the same firmware.
I don't have twrp, also adb command to remove magisk doesn't work. any workaround to remove magisk using a fastboot command? :/ any other way? can I install twrp at this stage without losing data?
I am genuinely sick of this device, a part from the very VERY bad quality of the hardware, a lot of issues happened when I rooted it for the first time and made me lose data. now today the device updated automatically to miui 12.5.1 and made me lose root despite having all auto update options disabled. I am genuinely considering throwing away this phone if I lose data this time. please help.
Click to expand...
Click to collapse
have you managed to fix your issue? what rom version are you running, do you need stock boot.img still?
Ghostface009 said:
Thanks for the reply, Im on it right now, also curious about the second part, what is the alpha twrp? can you elaborate? As you see I mentioned having not installed twrp.
Click to expand...
Click to collapse
Alpha TWRP is simply an unofficial TWRP developed by Nebrassy. It can do most of the things. One of which, flashing magisk. So you should give it a shot.
Issue solved after flashing unmodified boot.img, thanks all.
laid1995 said:
Alpha TWRP is simply an unofficial TWRP developed by Nebrassy. It can do most of the things. One of which, flashing magisk. So you should give it a shot.
Click to expand...
Click to collapse
Unfortunately it doesn't boot, I entered the fastboot command and it's just a black screen. I guess this doesn't work with MIUI 12.5.1, and that means Im stuck without root thanks to xiaomi
I also tried the adb command to remove magisk modules, didn't work, says inaccessable or not found
Cmn, stop blame Xiaomi and read and learn more before doing something that can mess up ur phone. Just a friendly advice
If u can boot to fastboot u can try to flash a stock ROM using MiFlash with "keep user data" checked....maybe u'll be lucky and ur phone will boot normally.
Alin45 said:
Cmn, stop blame Xiaomi and read and learn more before doing something that can mess up ur phone. Just a friendly advice
If u can boot to fastboot u can try to flash a stock ROM using MiFlash with "keep user data" checked....maybe u'll be lucky and ur phone will boot normally.
Click to expand...
Click to collapse
...But they did tho
The phone boots now, but still, I lost magisk and now I cannot install it on this update.
The phone also can't pass safetynet for some reason, despite having stock boot.img restored and leaving no trace of magisk.
All that could've been avoided if the device just did as it was told to, not to automatically update itself.
reg66 said:
have you managed to fix your issue? what rom version are you running, do you need stock boot.img still?
Click to expand...
Click to collapse
12.5.1
flashing stock boot.img of 12.5.1 (extracted using payload dumper tool) solved the issue
However, I can't root rhe phone on this update anyway, tried to boot alphatwrp and failed, Also safetynet fails
Ghostface009 said:
12.5.1
flashing stock boot.img of 12.5.1 (extracted using payload dumper tool) solved the issue
However, I can't root rhe phone on this update anyway, tried to boot alphatwrp and failed, Also safetynet fails
Click to expand...
Click to collapse
Safetynet fails because of the unlocked bootloader (most probably). Being unable to use TWRP is strange. Did u use the correct command in fastboot mode (fastboot boot xxxxx.img)? Also, what error did u get when TWRP failed to boot?
Alin45 said:
Safetynet fails because of the unlocked bootloader (most probably). Being unable to use TWRP is strange. Did u use the correct command in fastboot mode (fastboot boot xxxxx.img)? Also, what error did u get when TWRP failed to boot?
Click to expand...
Click to collapse
Thanks for the reply, yep unlocked bl also could be a reason, I want to think reasonably now
No error when booting twrp, just a black screen, tried to press power button or vol buttons and swipe on screen to unlock (even tho nothing appears) and its still a black screen.
Ill post on alphatwrp, maybe it doesn't support miui 12.5.1 firmware.
Ghostface009 said:
Thanks for the reply, yep unlocked bl also could be a reason, I want to think reasonably now
No error when booting twrp, just a black screen, tried to press power button or vol buttons and swipe on screen to unlock (even tho nothing appears) and its still a black screen.
Ill post on alphatwrp, maybe it doesn't support miui 12.5.1 firmware.
Click to expand...
Click to collapse
Strange....TWRP works fine with my xiaomi.eu weekly ROM (which is 12.5.x version), so I guess this isn't the problem. Seems ur issue is over my knowledge, so....I give up lol
Alin45 said:
Strange....TWRP works fine with my xiaomi.eu weekly ROM (which is 12.5.x version), so I guess this isn't the problem. Seems ur issue is over my knowledge, so....I give up lol
Click to expand...
Click to collapse
Maybe due to the difference between global and eu roms
Ik you gave all you can but what would you suggest to do for my situation in order to root this phone and pass safetynet again?
have you double checked it's not a corrupt twrp img, and that you are using the '2' version of twrp? (there's two floating around) from here
Download the TWRP again.
Follow the guide with pictures: https://forum.xda-developers.com/t/4288121/post-85137963
Do Clean Flash custom ROMs steps up to step 13. Ignore step 8, 9 and the flash part of 12.
If this way still can't get you TWRP, then you might want to try latest MIUI by Xiaomi.eu. Read somewhere it has built in TWRP, so once flashed, you have TWRP. Verify yourself by reading in other posts though.
Remember
EEA (official) is different from Xiaomi.eu (custom ROM)
Click to expand...
Click to collapse
reg66 said:
have you double checked it's not a corrupt twrp img, and that you are using the '2' version of twrp? (there's two floating around) from here
Click to expand...
Click to collapse
yep, the one I used was '2' version. I double checked for corruption and downloaded the same twrp again with same result :/
pl1992aw said:
Do Clean Flash custom ROMs
Click to expand...
Click to collapse
So my only way to get magisk again is flashing custom roms? it is how it is? :/