Related
Hi. For some reason, I'm not able to make my phone working with any custom ROM but MIUI ones. I tried the guides about flashing the 9.5.9 first, flashing the firmware but still, every time I flash a custom ROM (with flash result 1 in TWRP) and I reboot into the system, the phone keeps rebooting quickly after displaying only the MI logo. Apparently it shows that there isn't a valid firmware installed, but I followed the guides with no success. Any advice? Thanks!
Takenfal said:
Hi. For some reason, I'm not able to make my phone working with any custom ROM but MIUI ones. I tried the guides about flashing the 9.5.9 first, flashing the firmware but still, every time I flash a custom ROM (with flash result 1 in TWRP) and I reboot into the system, the phone keeps rebooting quickly after displaying only the MI logo. Apparently it shows that there isn't a valid firmware installed, but I followed the guides with no success. Any advice? Thanks!
Click to expand...
Click to collapse
Hello try to install magisk after installing the rom it worked for me so i hope it does for you as well but don't reboot literally flash the rom when it's done flash magisk and i think it should do it
Format data after flash, not just wipe
Sammy1221 said:
Hello try to install magisk after installing the rom it worked for me so i hope it does for you as well but don't reboot literally flash the rom when it's done flash magisk and i think it should do it
Click to expand...
Click to collapse
Ok, I'll do it when I'll try to install a custom ROM again; I can't keep trying formatting my data and then returning back to MIUI I need to be sure it will work!
siggey said:
Format data after flash, not just wipe
Click to expand...
Click to collapse
Did it! The process I did was:
Boot on TWRP and format data
reboot TWRP
Wipe cache, dalvik, data and System
Flash FW, ROM, GAPPS
Takenfal said:
Hi. For some reason, I'm not able to make my phone working with any custom ROM but MIUI ones. I tried the guides about flashing the 9.5.9 first, flashing the firmware but still, every time I flash a custom ROM (with flash result 1 in TWRP) and I reboot into the system, the phone keeps rebooting quickly after displaying only the MI logo. Apparently it shows that there isn't a valid firmware installed, but I followed the guides with no success. Any advice? Thanks!
Click to expand...
Click to collapse
Which twrp version did you use? Also try Resurrection Remix, it had simple flashing method.
GVN.Gallus said:
Which twrp version did you use? Also try Resurrection Remix, it had simple flashing method.
Click to expand...
Click to collapse
Actually that was the ROM I wanted to use XD I tried 3 different Kernels but noone worked :/ I'm using the twrp-3.3.1-5
Takenfal said:
Actually that was the ROM I wanted to use XD I tried 3 different Kernels but noone worked :/ I'm using the twrp-3.3.1-5
Click to expand...
Click to collapse
Hmm, unofficial twrp 3315 by mauronofrio?
Which device variant do you have, china or global? And device code name are perseus(4g)?
I suggest make a clean flash (without relock) with miflashtool, then install any new EU rom, after that try flash RR, with these step nothing could go wrong.
GVN.Gallus said:
Hmm, unofficial twrp 3315 by mauronofrio?
Which device variant do you have, china or global? And device code name are perseus(4g)?
I suggest make a clean flash (without relock) with miflashtool, then install any new EU rom, after that try flash RR, with these step nothing could go wrong.
Click to expand...
Click to collapse
Yes, It should be the 3.3.1.5 by mauronofrio; my Mi MIX 3 is the global version and right now I'm using the MIUI 11 9.10.10. What version of MIUI should I install using miflashtool? Thanks!
I cannot get data decryption with Android Q on any of the twrp builds.
Sent from my MIX 3 using Tapatalk
Takenfal said:
Yes, It should be the 3.3.1.5 by mauronofrio; my Mi MIX 3 is the global version and right now I'm using the MIUI 11 9.10.10. What version of MIUI should I install using miflashtool? Thanks!
Click to expand...
Click to collapse
Try last global beta 9.6.27, its the most stable with new feature, even better than global stable.
Then install any eu miui10 rom newer than 9.6.27, after that install custom rom.
Remember to boot up after each install, not necessary to complete set up, just boot up to welcome screen.
you saved my life
Sammy1221 said:
Hello try to install magisk after installing the rom it worked for me so i hope it does for you as well but don't reboot literally flash the rom when it's done flash magisk and i think it should do it
Click to expand...
Click to collapse
Even though the thread is quite old I have exactly the same problem with no suggestion here in the forums working to fix it
Can anybody please help me getting this figured out. My goal is to install the Pixel experience Rom for perseus (non 5g) posted here.
You MUST FORMAT data partition when you install anything from stock roms. It should boot after you format, and I'm not saying with the rm -rf option in settings if you have TWRP. It must be a full format of data. I know some of the older ROMs used to take many minutes to boot the first time (like up to 10). I am not actively developing for android after they turned on the hardware backed verity states and broke Google Pay with unlocked bootloader, I left android.
So I was using PixelExperiece ROM and decided to switch back to MIUI. I downloaded latest fastboot ROM from MIUI website, Flashed it using MI FLash Tool.
While flashing my phone displayed "System has been destroyed" in between. And MIFlash tool showed some error.
So, I tried flashing again and MIFlash tool now said Bootloader was locked. (Because lock_all_and_install was selected previously).
Therefore I downloaded MI Bootloader unlock tool. (The phone still shows "System has been destroyed"). Ignoring that warning, I went to fastboot and ran unlocker. To my surprise, after unlocking was complete and phone restarted it booted into MIUI. I thought "System has been destroyed" problem would be solved. But later I realised, my camera was not focusing on close range object. It wasnt focusing at all. Then after playing around to check everything I found out, my camera was not focusing, gyro was not working (No auto rotate and noting in CIT test) neither was my compass working. So there is some kind of problem with my hardware now.
Later I tried flashing same fastboot ROM again hoping it will install fully now and not ending up in "System has been destroyed" error. And I also chose option to not lock bootloader while flashing in MI Flash tool. This time the phone did started on to MIUI but in MI Flash tool it kept showing flashing as status. Even after I disconnected my phone USB cable it said flashing. And those hardware things are still not working.
While using PixelExperience I did changed SELinux mode to make ANXCamera work. Would it (SELinux mode) be a problem for hardware not working? Or is there any other problem?
Thanks in advance for any help.
DragonSlayer7# said:
So I was using PixelExperiece ROM and decided to switch back to MIUI. I downloaded latest recovery ROM from MIUI website, Flashed it using MI FLash Tool.
While flashing my phone displayed "System has been destroyed" in between. And MIFlash tool showed some error.
So, I tried flashing again and MIFlash tool now said Bootloader was locked. (Because lock_all_and_install was selected previously).
Therefore I downloaded MI Bootloader unlock tool. (The phone still shows "System has been destroyed"). Ignoring that warning, I went to fastboot and ran unlocker. To my surprise, after unlocking was complete and phone restarted it booted into MIUI. I thought "System has been destroyed" problem would be solved. But later I realised, my camera was not focusing on close range object. It wasnt focusing at all. Then after playing around to check everything I found out, my camera was not focusing, gyro was not working (No auto rotate and noting in CIT test) neither was my compass working. So there is some kind of problem with my hardware now.
Later I tried flashing same recovery ROM again hoping it will install fully now and not ending up in "System has been destroyed" error. And I also chose option to not lock bootloader while flashing in MI Flash tool. This time the phone did started on to MIUI but in MI Flash tool it kept showing flashing as status. Even after I disconnected my phone USB cable it said flashing. And those hardware things are still not working.
While using PixelExperience I did changed SELinux mode to make ANXCamera work. Would it (SELinux mode) be a problem for hardware not working? Or is there any other problem?
Thanks in advance for any help.
Click to expand...
Click to collapse
Wait what u said u flashed recovery rom via mi flash ? U have to flash persist.img (u will find this in your fastboot rom) from custom recovery in system/persist partition. Thats it.
hackermssharma said:
Wait what u said u flashed recovery rom via mi flash ? U have to flash persist.img (u will find this in your fastboot rom) from custom recovery in system/persist partition. Thats it.
Click to expand...
Click to collapse
Im sorry, my mistake. I flased fastboot ROM only. Not recovery. MIFlash tool won't allow you to flash recovery ROM at all.
DragonSlayer7# said:
Im sorry, my mistake. I flased fastboot ROM only. Not recovery. MIFlash tool won't allow you to flash recovery ROM at all.
Click to expand...
Click to collapse
Mmmm... No need to worry extract persist.img from fastboot rom folder and flash via OF recovery in system/persist partition. Then boot u get all your sensors back.
hackermssharma said:
Mmmm... No need to worry extract persist.img from fastboot rom folder and flash via OF recovery in system/persist partition. Then boot u get all your sensors back.
Click to expand...
Click to collapse
Instead of fixing existing sensors, flashing persist.img screwed up my wifi and hotspot. After flashing whole fastboot ROM againg they are now working. But other sensors are still not working.
DragonSlayer7# said:
Instead of fixing existing sensors, flashing persist.img screwed up my wifi and hotspot. After flashing whole fastboot ROM againg they are now working. But other sensors are still not working.
Click to expand...
Click to collapse
Really? I mean i used same method last time for my sensors to work again and that worked for me. Next workaround is u should clean flash miui 10 fastboot rom then update to miui 11 using updater app. Hope it should work for u.
flashing persist.img worked for me.
hackermssharma said:
Really? I mean i used same method last time for my sensors to work again and that worked for me. Next workaround is u should clean flash miui 10 fastboot rom then update to miui 11 using updater app. Hope it should work for u.
Click to expand...
Click to collapse
I flashed same MIUI fastboot ROM again, and miraculously all sensors started working again.:good::good:
DragonSlayer7# said:
I flashed same MIUI fastboot ROM again, and miraculously all sensors started working again.:good::good:
Click to expand...
Click to collapse
Great ??
Sensors
DragonSlayer7# said:
I flashed same MIUI fastboot ROM again, and miraculously all sensors started working again.:good::good:
Click to expand...
Click to collapse
I am also facing the same problem (sensors are not working) after i switched back from Pixel Experience to MIUI 11. Though i read all replies i did get some ideas but not clearly. Can you please little explain how to do it. Step by step method explanation will be much appriciated !! (only installation part, i have all required software and ROM ready for fastboot) I am just not clear how fix my sensors.
--------------------------------------------------------------
EDIT: No need guide. I understood how to do it. Some the things mentioned in reply were new for me so it was hard time for me to understand?.. I am new to Redmi phone
Widevine L1
hackermssharma said:
Mmmm... No need to worry extract persist.img from fastboot rom folder and flash via OF recovery in system/persist partition. Then boot u get all your sensors back.
Click to expand...
Click to collapse
Well i just got to know that by flashing 'persist.img' from a recovery will void Widevine L1 certification (Netflix with no HD, also other HD content streaming platform that requires Widevine L1 certification). I heard it will be permanent warrenty void and i don't know it can be fixed or not.
Azhar001 said:
I am also facing the same problem (sensors are not working) after i switched back from Pixel Experience to MIUI 11. Though i read all replies i did get some ideas but not clearly. Can you please little explain how to do it. Step by step method explanation will be much appriciated !! (only installation part, i have all required software and ROM ready for fastboot) I am just not clear how fix my sensors.
--------------------------------------------------------------
EDIT: No need guide. I understood how to do it. Some the things mentioned in reply were new for me so it was hard time for me to understand?.. I am new to Redmi phone
Click to expand...
Click to collapse
This persist.img thing might work for you or might not.
The full proof way is to reinstall Pixel Experience (Android 10) so that you get your sensors up and running again, then flash MIUI 10 and upgrade to MIUI 11 using system updater app.
Azhar001 said:
Well i just got to know that by flashing 'persist.img' from a recovery will void Widevine L1 certification (Netflix with no HD, also other HD content streaming platform that requires Widevine L1 certification). I heard it will be permanent warrenty void and i don't know it can be fixed or not.
Click to expand...
Click to collapse
Its fine. Just install Netflix from ApkMirror (not from Google Play) and it should work.
Azhar001 said:
Well i just got to know that by flashing 'persist.img' from a recovery will void Widevine L1 certification (Netflix with no HD, also other HD content streaming platform that requires Widevine L1 certification). I heard it will be permanent warrenty void and i don't know it can be fixed or not.
Click to expand...
Click to collapse
Also if you are coming back to MIUI, use this method...
DragonSlayer7# said:
This persist.img thing might work for you or might not.
The full proof way is to reinstall Pixel Experience (Android 10) so that you get your sensors up and running again, then flash MIUI 10 and upgrade to MIUI 11 using system updater app.
Click to expand...
Click to collapse
DragonSlayer7# said:
This persist.img thing might work for you or might not.
The full proof way is to reinstall Pixel Experience (Android 10) so that you get your sensors up and running again, then flash MIUI 10 and upgrade to MIUI 11 using system updater app.
Click to expand...
Click to collapse
should i flash MIUI 10 using custom recovery or fastboot after reinstalling Pixel Experience ?
Azhar001 said:
should i flash MIUI 10 using custom recovery or fastboot after reinstalling Pixel Experience ?
Click to expand...
Click to collapse
Fastboot ROM using MIFlashTool
DragonSlayer7# said:
Fastboot ROM using MIFlashTool
Click to expand...
Click to collapse
okay, i willl let you know if it works
I think you should try reflashing the stock firmware using the Mi Flash and select wipe data option.
Sent from my Redmi Note 7 Pro using Tapatalk
DragonSlayer7# said:
Fastboot ROM using MIFlashTool
Click to expand...
Click to collapse
I got all the sensors back again, everything working fine.
Here is what is did (using PC):
1) i installed Pixek Experience ROM (Android 10) using ADB Fastboot method.
Pros: Every sensors started to work, back to normal.
Cons: None i noticed.
2) Then i turn off the phone and entered into fastboot mode
3) I flashed MIUI 10 fastboot ROM using MIFlash Tool. Though i didn't get the "Success" message on MIFlash Tool but phone booted itself (did show MIUI 10 during boot up, and Set Up screen was appearing) so i assumed flashing was complete. Then i unplugged phone from USB cable.
After setup,
Pros: Every sensors was working perfectly fine.
Cons: None i noticed.
4) i updated from MIUI 10 to MIUI 11 using System update on phone. Now i am on MIUI 11 and everything works FINE!!
So what i found is there is some problem with MIUI 11 fastboot ROM itself. Directly flashing MIUI 11 fastboot ROM is the reason sensors stops working!!
Azhar001 said:
I got all the sensors back again, everything working fine.
Here is what is did (using PC):
1) i installed Pixek Experience ROM (Android 10) using ADB Fastboot method.
Pros: Every sensors started to work, back to normal.
Cons: None i noticed.
2) Then i turn off the phone and entered into fastboot mode
3) I flashed MIUI 10 fastboot ROM using MIFlash Tool. Though i didn't get the "Success" message on MIFlash Tool but phone booted itself (did show MIUI 10 during boot up, and Set Up screen was appearing) so i assumed flashing was complete. Then i unplugged phone from USB cable.
After setup,
Pros: Every sensors was working perfectly fine.
Cons: None i noticed.
4) i updated from MIUI 10 to MIUI 11 using System update on phone. Now i am on MIUI 11 and everything works FINE!!
So what i found is there is some problem with MIUI 11 fastboot ROM itself. Directly flashing MIUI 11 fastboot ROM is the reason sensors stops working!!
Click to expand...
Click to collapse
Yes, its kernel problem. It happens if you are flashing MIUI 11 based on Android Pie from any AOSP based ROM running Android 10.
Hi guys,
I made a mistake installing the Android 11 firmware update and afterwards flashing TWRP and installing Magisk.
Second mistake because I couldn't boot I flashed an old Fastboot ROM, but that doesn't help me.
Can anyone please point me to the fastboot rom for android 11 update?
Thank you very much.
ConsoleHax said:
Hi guys,
I made a mistake installing the Android 11 firmware update and afterwards flashing TWRP and installing Magisk.
Second mistake because I couldn't boot I flashed an old Fastboot ROM, but that doesn't help me.
Can anyone please point me to the fastboot rom for android 11 update?
Thank you very much.
Click to expand...
Click to collapse
Did you ever get any help? I am in the same boat.
ConsoleHax said:
Hi guys,
I made a mistake installing the Android 11 firmware update and afterwards flashing TWRP and installing Magisk.
Second mistake because I couldn't boot I flashed an old Fastboot ROM, but that doesn't help me.
Can anyone please point me to the fastboot rom for android 11 update?
Thank you very much.
Click to expand...
Click to collapse
I guess the best way to go back to stock is using msmtool you can find it here: with android 10 for international and European version: Thread '[OP7PRO][LATEST OOS 10.3.8 GM21AA | OOS 10.0.10 GM21BA] Collection of unbrick tools' https://forum.xda-developers.com/t/...0-gm21ba-collection-of-unbrick-tools.3956595/
Piricho said:
Did you ever get any help? I am in the same boat.
Click to expand...
Click to collapse
If you ended with a blinking TWRP just flash the stock/rooted boot.img if you are using stable you can obtain it here(Post in thread 'Android 11 Release - Finally!' https://forum.xda-developers.com/t/android-11-release-finally.4251267/post-84717089)
Or if you are on a Open Beta here: Thread 'OxygenOS Android 11 Betas (OnePlus 7 Pro) released (Open Beta 4 now available)' https://forum.xda-developers.com/t/...o-released-open-beta-4-now-available.4221067/
RokCruz said:
I guess the best way to go back to stock is using msmtool you can find it here: with android 10 for international and European version: Thread '[OP7PRO][LATEST OOS 10.3.8 GM21AA | OOS 10.0.10 GM21BA] Collection of unbrick tools' https://forum.xda-developers.com/t/...0-gm21ba-collection-of-unbrick-tools.3956595/
If you ended with a blinking TWRP just flash the stock/rooted boot.img if you are using stable you can obtain it here(Post in thread 'Android 11 Release - Finally!' https://forum.xda-developers.com/t/android-11-release-finally.4251267/post-84717089)
Or if you are on a Open Beta here: Thread 'OxygenOS Android 11 Betas (OnePlus 7 Pro) released (Open Beta 4 now available)' https://forum.xda-developers.com/t/...o-released-open-beta-4-now-available.4221067/
Click to expand...
Click to collapse
Hey,
I bricked my OP7 after what seemed like successfully installing and using Android 11. I am getting the Teamwin blinking brick.
This(
) seems like something I can do- flashing Fastboot ROM(even though I'll lose data, but wth). Can you please tell me if this comment of yours applies in my case- i.e. is the link you are suggesting for Android 11 Fastboot ROM valid?
saurabh_op7 said:
Hey,
I bricked my OP7 after what seemed like successfully installing and using Android 11. I am getting the Teamwin blinking brick.
This(
) seems like something I can do- flashing Fastboot ROM(even though I'll lose data, but wth). Can you please tell me if this comment of yours applies in my case- i.e. is the link you are suggesting for Android 11 Fastboot ROM valid?
Click to expand...
Click to collapse
Just flash stock boot.img
RokCruz said:
Just flash stock boot.img
Click to expand...
Click to collapse
As a rain check, as I am new to this, and don't want to screw up more,
You mean I can use this method-
Restore OnePlus 7/7T/7T Pro to Stock via Fastboot Commands - DroidWin
to flash the latest stable build on OnePlus support, i.e. this-
https://otafsg1.h2os.com/patch/amaz....P.35_OTA_0350_all_2103221240_3e944b9d067.zip(OnePlus7Oxygen_14.P.32_OTA_032_all_2101280019_b2a62765ba0c485e.zip)
??
Or do you suggest to use the Android 11 firmware available on XDA?
saurabh_op7 said:
As a rain check, as I am new to this, and don't want to screw up more,
You mean I can use this method-
Restore OnePlus 7/7T/7T Pro to Stock via Fastboot Commands - DroidWin
to flash the latest stable build on OnePlus support, i.e. this-
https://otafsg1.h2os.com/patch/amaz....P.35_OTA_0350_all_2103221240_3e944b9d067.zip(OnePlus7Oxygen_14.P.32_OTA_032_all_2101280019_b2a62765ba0c485e.zip)
??
Or do you suggest to use the Android 11 firmware available on XDA?
Click to expand...
Click to collapse
You can do it with the fastboot zip but you need to download all the firmware, in some threads you will find the stock/rooted boot.img from stable and OB, I shared both in this message
RokCruz said:
If you ended with a blinking TWRP just flash the stock/rooted boot.img if you are using stable you can obtain it here(Post in thread 'Android 11 Release - Finally!' https://forum.xda-developers.com/t/android-11-release-finally.4251267/post-84717089)
Or if you are on a Open Beta here: Thread 'OxygenOS Android 11 Betas (OnePlus 7 Pro) released (Open Beta 4 now available)' https://forum.xda-developers.com/t/...o-released-open-beta-4-now-available.4221067/
Click to expand...
Click to collapse
RokCruz said:
You can do it with the fastboot zip but you need to download all the firmware, in some threads you will find the stock/rooted boot.img from stable and OB, I shared both in this message
Click to expand...
Click to collapse
I am pretty sure I know my OS, but is there a way to find out?
I was running the stable, but flashing stock boot just led me to a boot loop with the Original Recovery, it's giving me options to
1. Wipe data and cache
2. Reboot to fastboot
3. Reboot to recovery
The fastboot flash commands above to flash stock OS didn't work, due to one error or another.
Anyhow, I had read somewhere fastboot continue works(here: it wasn't working before for me), so I tried that again, and now I am just stuck on 1+ Fastboot screen. I will wait it out to see if it boots into system.
Otherwise, I am thinking I reload fastboot and flash stock boot just like I did- and from there wipe data, but what do I expect then??
The way I see it, I am just stuck in some serious boot issue, and might eventually have to go down the path of msndownloadtool, any suggestion?
saurabh_op7 said:
I am pretty sure I know my OS, but is there a way to find out?
I was running the stable, but flashing stock boot just led me to a boot loop with the Original Recovery, it's giving me options to
1. Wipe data and cache
2. Reboot to fastboot
3. Reboot to recovery
The fastboot flash commands above to flash stock OS didn't work, due to one error or another.
Anyhow, I had read somewhere fastboot continue works(here: it wasn't working before for me), so I tried that again, and now I am just stuck on 1+ Fastboot screen. I will wait it out to see if it boots into system.
Otherwise, I am thinking I reload fastboot and flash stock boot just like I did- and from there wipe data, but what do I expect then??
The way I see it, I am just stuck in some serious boot issue, and might eventually have to go down the path of msndownloadtool, any suggestion?
Click to expand...
Click to collapse
Flashing the stock boot.img should be enough to boot into system without problems because TWRP can't decrypt data in android 11.
In this point you can try a factory reset from stock recovery this will keep device files but will erase all your config and apps
To figure out what version of firmware you had you can run this command in fastboot
Fastboot getvar all
RokCruz said:
Flashing the stock boot.img should be enough to boot into system without problems because TWRP can't decrypt data in android 11.
In this point you can try a factory reset from stock recovery this will keep device files but will erase all your config and apps
To figure out what version of firmware you had you can run this command in fastboot
Fastboot getvar all
Click to expand...
Click to collapse
Flashing didn't work to boot into system, I was just getting stuck in the Recovery boot loop, it finally booted into system once I wiped my data(files, music, etc -option);
I did try factory reset, only once I cleared the partition, did the boot loop give way to boot into system;
It booted back to Android 11, but it's all glitchy: Boot taking too long, WiFi not switching on, Call not working, Data is working though- basically it's very screwed up, got a couple of errors too- it's like watching an amnesiac old person.. if you get the gist.
So, now I am considering a stable build from Oneplus support website as a local upgrade and booting back to that..
I am hard pressed for options, let me know if you think something else works better, thanks!
saurabh_op7 said:
Flashing didn't work to boot into system, I was just getting stuck in the Recovery boot loop, it finally booted into system once I wiped my data(files, music, etc -option);
I did try factory reset, only once I cleared the partition, did the boot loop give way to boot into system;
It booted back to Android 11, but it's all glitchy: Boot taking too long, WiFi not switching on, Call not working, Data is working though- basically it's very screwed up, got a couple of errors too- it's like watching an amnesiac old person.. if you get the gist.
So, now I am considering a stable build from Oneplus support website as a local upgrade and booting back to that..
I am hard pressed for options, let me know if you think something else works better, thanks!
Click to expand...
Click to collapse
I guess msmtool it's the best way to restore your phone, remember that msmtool will re-lock your bootloader so if you want root you need to unlock your bootloader again.
Use msmtool and instructions form Here(there's an android 9 and android 10 for Global and Europe versions, use android 10)
RokCruz said:
I guess msmtool it's the best way to restore your phone, remember that msmtool will re-lock your bootloader so if you want root you need to unlock your bootloader again.
Use msmtool and instructions form Here(there's an android 9 and android 10 for Global and Europe versions, use android 10)
Click to expand...
Click to collapse
My model is GM1901, in support intro for the link you provided, that's not included?
saurabh_op7 said:
My model is GM1901, in support intro for the link you provided, that's not included?
Click to expand...
Click to collapse
Wait GM1901 is a OnePlus 7(non pro) right?
RokCruz said:
Wait GM1901 is a OnePlus 7(non pro) right?
Click to expand...
Click to collapse
Yeah.. ?
saurabh_op7 said:
Yeah.. ?
Click to expand...
Click to collapse
This is the OnePlus 7 pro forum so, I assume you was a 7 pro user, now all makes sense you don't flash the correct boot.img for your device so all woes wrong.
You need to use msmtool from Here
RokCruz said:
This is the OnePlus 7 pro forum so, I assume you was a 7 pro user, now all makes sense you don't flash the correct boot.img for your device so all woes wrong.
You need to use msmtool from HereI
Click to expand...
Click to collapse
Yeah man, I realised.. anyway, I flashed the boot image from Xda for OP7.. nevertheless, mom tool it is.. thanks..!
RokCruz said:
This is the OnePlus 7 pro forum so, I assume you was a 7 pro user, now all makes sense you don't flash the correct boot.img for your device so all woes wrong.
You need to use msmtool from Here
Click to expand...
Click to collapse
Hey, I am on Mac, I see that Msm is windows-specific.. any way out?
Update: I have been roaming around the corridors of this forum since about a week now. Thanks @RokCruz !!
Finally, used msm tool, although I suspect I still had the option of flashing TWRP and Magisk as I had access to phone and fastboot, but the system was super glitchy.
saurabh_op7 said:
Hey, I am on Mac, I see that Msm is windows-specific.. any way out?
Click to expand...
Click to collapse
I guess that the only way is using the fastboot ROM
RokCruz said:
I guess that the only way is using the fastboot ROM
Click to expand...
Click to collapse
Any idea if we're gonna get one soon?
Hi guys, I'm at my wits end with my flashing experience currently.
I just unlocked my K30 PZ, and was messing around with manuelbianco's TWRP, and I seem to have effectively softlocked my phone
I'm pretty tired and have no idea how I ended up here, so all I can really post is what I can observe.
It's constantly stuck in bootloop, and while I have access via fastboot as well as LR-TEAM TWRP(MB doesnt work, boots to logo then goes to black screen), nothing I do seems to be able to break my bootloop.
Attempting to flash MIUI via miflash results in the attempt getting stuck on super.img, while flashing by XiaoMiTool also has the same effect, with the added exit code 1.
Also noteworthy is that according to twrp, "/vendor", "/product" and "/odm" all fail to mount due to invalid arguement, which I have no idea about.
I've attempted to manually mount them via twrp, and try and flash stock miui, however there is no change in the behavior.
Any help is appreciated, thanks.
PipPasadran said:
Hi guys, I'm at my wits end with my flashing experience currently.
I just unlocked my K30 PZ, and was messing around with manuelbianco's TWRP, and I seem to have effectively softlocked my phone
I'm pretty tired and have no idea how I ended up here, so all I can really post is what I can observe.
It's constantly stuck in bootloop, and while I have access via fastboot as well as LR-TEAM TWRP(MB doesnt work, boots to logo then goes to black screen), nothing I do seems to be able to break my bootloop.
Attempting to flash MIUI via miflash results in the attempt getting stuck on super.img, while flashing by XiaoMiTool also has the same effect, with the added exit code 1.
Also noteworthy is that according to twrp, "/vendor", "/product" and "/odm" all fail to mount due to invalid arguement, which I have no idea about.
I've attempted to manually mount them via twrp, and try and flash stock miui, however there is no change in the behavior.
Any help is appreciated, thanks.
Click to expand...
Click to collapse
Which ROM did you want to flash?
I grabbed the latest Poco F2 Pro zip from the mi community, since I couldn't find any K30 Pro ROMs
PipPasadran said:
I grabbed the latest Poco F2 Pro zip from the mi community, since I couldn't find any K30 Pro ROMs
Click to expand...
Click to collapse
Do you want a miui stock rom or eu roms or aosp roms?
My end goal is an AOSP rom like arrowOS or evolutionX.
I tried flashing arrowOS after everything had happened. It seems to flash normally, but on reboot it's shows the POCO logo then proceeds to bootloop
PipPasadran said:
My end goal is an AOSP rom like arrowOS or evolutionX.
I tried flashing arrowOS after everything had happened. It seems to flash normally, but on reboot it's shows the POCO logo then proceeds to bootloop
Click to expand...
Click to collapse
Is your phone is a CN version?
Yeap
PipPasadran said:
Yeap
Click to expand...
Click to collapse
arrowOS or evolutionX have not the same firmware.
Dont relock your bootloader(otherwise the phone is dead)
1/flash this twrp with fasboot command https://androidfilehost.com/?fid=17248734326145679747
2/Twrp wipe format data write yes,reboot twrp
3/otg the rom or push in internal storage
4/flash rom(firmware)
5/format data again reboot twrp
6/flash rom(with the op instructions)
NOSS8 said:
arrowOS or evolutionX have not the same firmware.
Dont relock your bootloader(otherwise the phone is dead)
1/flash this twrp with fasboot command https://androidfilehost.com/?fid=17248734326145679747
2/Twrp wipe format data write yes,reboot twrp
3/otg the rom or push in internal storage
4/flash rom(firmware)
5/format data again reboot twrp
6/flash rom(with the op instructions)
Click to expand...
Click to collapse
To be clear, by rom u mean evoX or arrowOS right?
PipPasadran said:
To be clear, by rom u mean evoX or arrowOS right?
Click to expand...
Click to collapse
4/flash rom(firmware)
Requires CN version MIUI 12.2.1.0 firmware and vendor or
MIUI V12.2.1.0.RJKMIXM
6/flash AOSP rom(with the op instructions)
NOSS8 said:
4/flash rom(firmware)
Requires CN version MIUI 12.2.1.0 firmware and vendor or
MIUI V12.2.1.0.RJKMIXM
6/flash AOSP rom(with the op instructions)
indeed these two roms have the same firmware
Click to expand...
Click to collapse
Thanks, its about 130am over here
Evo x global firmware and arrow cn firmware.
Not the same!!!!!!!!
indeed these two roms have the same firmware
Thanks, I went back to read the flashing instructions
Tiredness isn't helping though XD
NOSS8 said:
Evo x global firmware and arrow cn firmware.
Not the same!!!!!!!!
indeed these two roms have the same firmware
Click to expand...
Click to collapse
Final update before I sleep
I've followed the steps, and managed to get arrowOS to boot screen
But I waited 20 mins for initial boot, and was stuck at the loading screen
Formatted data again to retry, and am now letting it run for as long as I can, but so far I'm 15 mins in now and have not seen anything more than the initial boot loading screen.
Thanks for the help, cheers
Evo x
PipPasadran said:
Final update before I sleep
I've followed the steps, and managed to get arrowOS to boot screen
But I waited 20 mins for initial boot, and was stuck at the loading screen
Formatted data again to retry, and am now letting it run for as long as I can, but so far I'm 15 mins in now and have not seen anything more than the initial boot loading screen.
Thanks for the help, cheers
Click to expand...
Click to collapse
So which firmware do you flash?
NOSS8 said:
Evo x
So which firmware do you flash?
Click to expand...
Click to collapse
CN firmware and arrowOS A11 from their site
PipPasadran said:
CN firmware and arrowOS A11 from their site
Click to expand...
Click to collapse
format data yes,reboot twrp
flash the rom https://sourceforge.net/projects/xi...MK30Pro_V12.2.1.0.RJKCNXM_v12-11.zip/download
reboot system
nothing else
first boot take 5/6 minutes.
if the phone restarts on this rom you will be sure that the correct firmware is installed
NOSS8 said:
format data yes,reboot twrp
flash the rom https://sourceforge.net/projects/xi...MK30Pro_V12.2.1.0.RJKCNXM_v12-11.zip/download
reboot system
nothing else
first boot take 5/6 minutes.
if the phone restarts on this rom you will be sure that the correct firmware is installed
Click to expand...
Click to collapse
Im downloading that rom but my download speed is quite slow, update tmr. But is it normal that after format data and yes, the arrowOS loading screen still comes up?
PipPasadran said:
Im downloading that rom but my download speed is quite slow, update tmr. But is it normal that after format data and yes, the arrowOS loading screen still comes up?
Click to expand...
Click to collapse
yep ,but you can before flashing the EU rom after format data,do a wipe all except OTG.
NOSS8 said:
yep ,but you can before flashing the EU rom after format data,do a wipe all except OTG.
Click to expand...
Click to collapse
So I formatted data, wiped all except OTG and then flashed the xiaomi.eu rom
Phone simply goes back into 2 bootloops before booting into twrp
Also to note, in advanced wipe system partition is missing in twrp. There is an option to mount, but it never shows up in wipe.
Hello, I have a Redmi 9A in the default stock state (no unlocked bootloader and default recovery, no TWRP).
After a random shutdown while using it normally, it's stuck in a bootloop in the default recovery.
I've read other threads, and I think I can try to recover it by using SP Flash Tool (please confirm if this is correct), but I'm more concerned about the data inside the device.
Can I somehow recover the data before flashing it, or is it impossible to do that since my bootloader is locked?
Thanks.
Well I don't think you can recover data I guess, maybe if you only select download not format + download in sp flash tool but maybe you brick again your phone.
it boots to recovery, so use adb or mount internal storage. you can also dirtyflash ROM
yaro666 said:
it boots to recovery, so use adb or mount internal storage. you can also dirtyflash ROM
Click to expand...
Click to collapse
Sorry for the delay, been doing some reading on these things.
By using adb, do you mean using adb pull to get the files? In the recovery, Connect to MI Assistant only gets the device in sideload, so I don't think that's possible. Don't have the option to mount storage either.
You have sideload?? If yes open adb in pc and type : adb sideload file.zip ( your rom ** btw you need recovery rom not fastboot**) idk if you will delete data or no
I tried that, but without success apparently. The rom is loading for some time, and then reports the error:
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
From what I've read, it might be due to a bad driver installation, I will look at it and update
madafaka7 said:
I tried that, but without success apparently. The rom is loading for some time, and then reports the error:
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
From what I've read, it might be due to a bad driver installation, I will look at it and update
Click to expand...
Click to collapse
Ok
Reinstalled drivers, still returns the same error.
try older ROMs - either you have faulty hardware or some minor bug
yaro666 said:
try older ROMs - either you have faulty hardware or some minor bug
Click to expand...
Click to collapse
I've tried to sideload the latest recovery ROMs for 12.0 and 12.5, the device was 12.5 when it "crashed". Should I try MIUI 11, or is it enough with older 12 versions?
madafaka7 said:
I've tried to sideload the latest recovery ROMs for 12.0 and 12.5, the device was 12.5 when it "crashed". Should I try MIUI 11, or is it enough with older 12 versions?
Click to expand...
Click to collapse
Try 12.0.20, the 12.5 have a lot of bugs and yeah
Rares6567 said:
Try 12.0.20, the 12.5 have a lot of bugs and yeah
Click to expand...
Click to collapse
That's the one I've tried already, it's the latest 12.0 version.
I guess I'll try to use SP Flash Tool, but it looks like the hardware is messed up...
Ok, a bit late but I'm going to update just in case anyone faces the same problem.
After trying every option with no success, I gave up on recovering user data and wiped all data from the stock recovery menu, and that solved the bootloop somehow. I'm guessing an app was messing up the system, but I don't know.
Thanks @Rares6567 and @yaro666 for your help.
madafaka7 said:
Ok, a bit late but I'm going to update just in case anyone faces the same problem.
After trying every option with no success, I gave up on recovering user data and wiped all data from the stock recovery menu, and that solved the bootloop somehow. I'm guessing an app was messing up the system, but I don't know.
Thanks @Rares6567 and @yaro666 for your help.
Click to expand...
Click to collapse
Happy to hear that