Related
Hey guys,
Im quite new to android and all that comes with it regarding flashing roms. Now i've had the mi mix 3 cn version since october and been wanting to flash to the global rom ever since. So far i have unlocked the bootloader only on my Mix 3. Now Ive started doing some experimenting with an old one plus 1 device of mine before i fully try it on my mix 3 (and **** it up) and so far been able to unlock bootloader and install twrp. But it seems i cant get through the rooting part because every time i download supersu.zip (on my mac) it doesnt actually show as a zip file. So when i copy/paste it into the oneplus directory and try to install through twrp, basically nothing happens because its not a zip file. Is the solution as simple as: " i should just download the same file using Windows??"
Magisk:
in order to root my my Mix 3 and Oneplus 1 i need to install and run Magisk. But after installing it and opening it, it always says 'Magisk is not installed" and under that "Magisk Manager installed".
Question 1: How to fix this.....
Question 2: Do i need to root my Mix 3 in order to flash the global rom?
Currently running MIUI 10.2 Stable 10.2.2.0(PEECNXM)
Many thanks!
Safari unzips after downloading. You can disable it in the settings I think.
TheArchangel123 said:
Hey guys,
Im quite new to android and all that comes with it regarding flashing roms. Now i've had the mi mix 3 cn version since october and been wanting to flash to the global rom ever since. So far i have unlocked the bootloader only on my Mix 3. Now Ive started doing some experimenting with an old one plus 1 device of mine before i fully try it on my mix 3 (and **** it up) and so far been able to unlock bootloader and install twrp. But it seems i cant get through the rooting part because every time i download supersu.zip (on my mac) it doesnt actually show as a zip file. So when i copy/paste it into the oneplus directory and try to install through twrp, basically nothing happens because its not a zip file. Is the solution as simple as: " i should just download the same file using Windows??"
Magisk:
in order to root my my Mix 3 and Oneplus 1 i need to install and run Magisk. But after installing it and opening it, it always says 'Magisk is not installed" and under that "Magisk Manager installed".
Question 1: How to fix this.....
Question 2: Do i need to root my Mix 3 in order to flash the global rom?
Currently running MIUI 10.2 Stable 10.2.2.0(PEECNXM)
Many thanks!
Click to expand...
Click to collapse
Flash magisk 19 then install the magisk app
TheArchangel123 said:
Hey guys,
Im quite new to android and all that comes with it regarding flashing roms. Now i've had the mi mix 3 cn version since october and been wanting to flash to the global rom ever since. So far i have unlocked the bootloader only on my Mix 3. Now Ive started doing some experimenting with an old one plus 1 device of mine before i fully try it on my mix 3 (and **** it up) and so far been able to unlock bootloader and install twrp. But it seems i cant get through the rooting part because every time i download supersu.zip (on my mac) it doesnt actually show as a zip file. So when i copy/paste it into the oneplus directory and try to install through twrp, basically nothing happens because its not a zip file. Is the solution as simple as: " i should just download the same file using Windows??"
Magisk:
in order to root my my Mix 3 and Oneplus 1 i need to install and run Magisk. But after installing it and opening it, it always says 'Magisk is not installed" and under that "Magisk Manager installed".
Question 1: How to fix this.....
Question 2: Do i need to root my Mix 3 in order to flash the global rom?
Currently running MIUI 10.2 Stable 10.2.2.0(PEECNXM)
Many thanks!
Click to expand...
Click to collapse
You do not need to root your device to flash it to the Global ROM. Unless you need root for something specific, I would suggest forgetting about TWRP and root and using fastboot to flash to the Global ROM. You can find the fastboot flashing guide, here. Click on fastboot, read the instructions, download the correct fastboot image for the Mi Mix 3, unzip it, boot your device into fastboot, connect it via USB to a Windows based machine, and run the flash_all.bat. The device will reboot when finished.
Thanks!
jcsww said:
You do not need to root your device to flash it to the Global ROM. Unless you need root for something specific, I would suggest forgetting about TWRP and root and using fastboot to flash to the Global ROM. You can find the fastboot flashing guide, "https://en.miui.com/a-232.html"]here. Click on fastboot, read the instructions, download the correct fastboot image for the Mi Mix 3, unzip it, boot your device into fastboot, connect it via USB to a Windows based machine, and run the flash_all.bat. The device will reboot when finished.
Click to expand...
Click to collapse
Ok thanks! Will definitly check it out. However i would like to get twrp working as well even just for the sake of it. But every time after i do the "reboot flash recovery rocovery.img" cmd it keeps booting into either the normal OS or into fastboot mode. Ive read about installing the force disable encryption zip file but how do i install that if i cant boot into twrp?
TheArchangel123 said:
Ok thanks! Will definitly check it out. However i would like to get twrp working as well even just for the sake of it. But every time after i do the "reboot flash recovery rocovery.img" cmd it keeps booting into either the normal OS or into fastboot mode. Ive read about installing the force disable encryption zip file but how do i install that if i cant boot into twrp?
Click to expand...
Click to collapse
Which TWRP are you flashing? When I was attempting to root my Chinese Mi Mix 3 running the GLobal Stable ROM, it was very hit and miss getting TWRP to stick. I couldn't get fastboot reboot-recovery to work for me so I had to power the device off after flashing TWRP and then hold Volume Up and Power until it vibrates again to get it into TWRP.
To root in that particular situation (Chinese device/Global ROM), you need to flash this region hiding thing right after you flash root. My device kept bootlooping so I gave up and used fastboot to debloat the ROM, which took a few minutes compared to the almost hour I spent on trying to get TWRP to stick and try to get the device rooted. This is one of my many gripes with Magisk root and how inferior it is to Chainfire's discontinued implementation.
Final stage!
Ok so my last post can be ignored as i was finally able to boot into twrp and also installed magisk so now my device is rooted.
I have now uploaded MIMIX3GLOBAL_V10.2.2.0 PEEMIXM into my phones directory.
Now before i install it thru twrp.... Do i need to wipe/erase/clean my phone first? Or can i just install it without doing so?
Many thanks in advance!
TheArchangel123 said:
Ok so my last post can be ignored as i was finally able to boot into twrp and also installed magisk so now my device is rooted.
I have now uploaded MIMIX3GLOBAL_V10.2.2.0 PEEMIXM into my phones directory.
Now before i install it thru twrp.... Do i need to wipe/erase/clean my phone first? Or can i just install it without doing so?
Many thanks in advance!
Click to expand...
Click to collapse
You can dirty flash it. It's just a minor update. The current beta will bring some new features though, once it is released in the next stable version.
jcsww said:
You can dirty flash it. It's just a minor update. The current beta will bring some new features though, once it is released in the next stable version.
Click to expand...
Click to collapse
Even though my current rom is the chinese version and i want to flash to a global version?
And how about if I flash to Mi Mix 3’s MIUI 10 Global Stable ROM based on Android 9 Pie (MIUI v10.0.11)??
TheArchangel123 said:
Even though my current rom is the chinese version and i want to flash to a global version?
And how about if I flash to Mi Mix 3’s MIUI 10 Global Stable ROM based on Android 9 Pie (MIUI v10.0.11)??
Click to expand...
Click to collapse
You can't dirty flash it...
Wipe in twrp
Install zip in twrp
format data in twrp
Reboot
If you want to root it you'll need the hardware origin magisk module that's somewhere in the mix 3 forums
Region, china?!
So i just clean flashed my phone and then formatted the data and rebooted. After i chose my language i have to choose my region, and the only option it gives me is China!????
TheArchangel123 said:
So i just clean flashed my phone and then formatted the data and rebooted. After i chose my language i have to choose my region, and the only option it gives me is China!????
Click to expand...
Click to collapse
China has the most content, it's not a bad thing. All themes become available etc
Mackay53 said:
China has the most content, it's not a bad thing. All themes become available etc
Click to expand...
Click to collapse
ok fair enough. However I have a situation now... after installing the process goes into a loop after selection china as region. The last small message it gives is "find device quit unexpectedly" and then it loops for 5 minutes untill it boots into recovery mode. Here i can only choose boot system (which will go into the same loop again), wipe data, or connect to MIUI assistent...
What did i do wrong?? Did i flash the wrong rom?
TheArchangel123 said:
So i just clean flashed my phone and then formatted the data and rebooted. After i chose my language i have to choose my region, and the only option it gives me is China!????
Click to expand...
Click to collapse
When cross-flashing, clean/factory reset is always the way to go. With TWRP though, there seems to be some sort of region options not changing issue. There are a few ways to work around it I personally never bothered with, but I have flashed two Chinese devices via fastboot with the Global Stable ROM and haven't ran into the region issue at all.
TheArchangel123 said:
ok fair enough. However I have a situation now... after installing the process goes into a loop after selection china as region. The last small message it gives is "find device quit unexpectedly" and then it loops for 5 minutes untill it boots into recovery mode. Here i can only choose boot system (which will go into the same loop again), wipe data, or connect to MIUI assistent...
What did i do wrong?? Did i flash the wrong rom?
Click to expand...
Click to collapse
Google miui region fix, download and flash and it should sort it
Mackay53 said:
Google miui region fix, download and flash and it should sort it
Click to expand...
Click to collapse
ok got the miui region fix. But how do i flash it... my phone wont boot into twrp anymore. Im also not sure how to get into fastboot either because it doesnt seem to connect if i type in the commands in cmd
TheArchangel123 said:
ok got the miui region fix. But how do i flash it... my phone wont boot into twrp anymore. Im also not sure how to get into fastboot either because it doesnt seem to connect if i type in the commands in cmd
Click to expand...
Click to collapse
Fastboot is the bootloader. Once you boot your device into the bootloader (Volume Down + Power), you can use ADB through the command prompt to flash TWRP or just flash the Global ROM properly. This thread on it is still very relevant and useful.
Got it!
jcsww said:
Fastboot is the bootloader. Once you boot your device into the bootloader (Volume Down + Power), you can use ADB through the command prompt to flash TWRP or just flash the Global ROM properly. This thread on it is still very relevant and useful.
Click to expand...
Click to collapse
Thanks guys, after a few long days ive finally succeeded to flash a global rom for the first time. Nxt step, try to get all my apps/data etc back. Hopefully i made a correct back up...
Hello
Need kelp here
Problem 1:
When I try to install any Android 10 based ROM on my Violet, it ends up with an error 7 saying either " are you installing onto the correct device" or sometimes "requires firmware version #*#*#* even though I flash the latest Chinese firmware everytime I flash a ROM.
Obviously, I'm able to bypass this problem by deleting the 2 assert lines in it's script using note++
I also flash fcrypt disabler after ROM flashing.
But still OTA updates keep failing and leads to boot loops
Problem 2:
OK,
now am in ROM, I try to flash magisk now, that leads to bootloop too
So can't flash root
Any solution?
Also I use orangefox recovery
mj25m said:
...
Problem 1:
When I try to install any Android 10 based ROM on my Violet, it ends up with an error 7 saying either " are you installing onto the correct device" or sometimes "requires firmware version #*#*#* even though I flash the latest Chinese firmware everytime I flash a ROM.
Click to expand...
Click to collapse
ROM installers that have that kind of assert are usually looking for a specific firmware version. Just flashing "the latest Chinese firmware" does not mean that you are flashing the specific version that the ROM's installer is looking for.
mj25m said:
....I also flash fcrypt disabler after ROM flashing.
Click to expand...
Click to collapse
Why?
mj25m said:
.But still OTA updates keep failing and leads to boot loops
Click to expand...
Click to collapse
Your intervention, which I just queried above, could easily cause that. Secondly, there is a specific ROM (which will remain nameless) which forces you to use its own recovery for everything - including and especially OTA updates - and if you try using another recovery, heaven help you. If you have that ROM, dump it!
mj25m said:
.Problem 2:
OK,
now am in ROM, I try to flash magisk now, that leads to bootloop too
So can't flash root
Any solution?
Click to expand...
Click to collapse
Ask your ROM dev. Or dump the ROM.
DarthJabba9 said:
ROM installers that have that kind of assert are usually looking for a specific firmware version. Just flashing "the latest Chinese firmware" does not mean that you are flashing the specific version that the ROM's installer is looking for.
Why?
Your intervention, which I just queried above, could easily cause that. Secondly, there is a specific ROM (which will remain nameless) which forces you to use its own recovery for everything - including and especially OTA updates - and if you try using another recovery, heaven help you. If you have that ROM, dump it!
Ask your ROM dev. Or dump the ROM.
Click to expand...
Click to collapse
Like I said, I'm facing the same kind of problems on all kind of ROMs that I flash
I don't know if I've messed up my Violet but it seems to be like a permanent issue.
I flash fcrypt 'cause one day, when i was without my senses, I flashed a ROM without wiping the previous ROM's encrypted storage and I think maybe tht it was since tht day on tht I started to face these issue
mj25m said:
Hello
Need kelp here
Problem 1:
When I try to install any Android 10 based ROM on my Violet, it ends up with an error 7 saying either " are you installing onto the correct device" or sometimes "requires firmware version #*#*#* even though I flash the latest Chinese firmware everytime I flash a ROM.
Obviously, I'm able to bypass this problem by deleting the 2 assert lines in it's script using note++
I also flash fcrypt disabler after ROM flashing.
But still OTA updates keep failing and leads to boot loops
Problem 2:
OK,
now am in ROM, I try to flash magisk now, that leads to bootloop too
So can't flash root
Any solution?
Also I use orangefox recovery
Click to expand...
Click to collapse
For this go to File Manager, select data then change the file system from f2fs to ext4. Then the error 7 issue will get solved.
Note: This will format all internal data.
Go ahead! All the Best! Happy Flashing!!:laugh:
Flash 9.9.3 firmware version .. most of the roms require that specific version. Then flash rom ... Also flash magisk after first boot not right after you flash rom this might help !
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?
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
I've owned Samsung, Lenovo and Moto phones before, and I never had any problems unlocking them and flashing custom recoveries and ROMs. This is my 2nd Xiaomi phone and like the 1st I keep bricking and unbricking it. The only thing I can manage to do is sometimes get TWRP on it, or the normal ROM.
- Version: European version of the Redmi Note 11 Pro, codename veux.
- TWRP: https://forum.xda-developers.com/t/twrp-3-7-0_12-for-veux-peux.4520689/
- ROM: https://forum.xda-developers.com/t/rom-13-veux-peux-official-evolution-x-11-09-22.4497785/
___
1st attempt:
1 - After unlocking the bootloader it reinstalled a clean ROM. I then forgot to turn USB debugging on so that was my fault. Because after that I went into fastboot and flashed this TWRP with fastboot flash boot name.img
2 - On this first try I then rebooted to recovery, but it sent me to the normal one instead. In essence I bricked it so I followed this guide to reset it
___
2nd attempt:
1 - I enable USB debugging
2 - go into fastboot: fastboot flash boot name.img
3 - reboot to recovery
4 - in TWRP I try to flash the ROM from the internal storage. It fails after around 33% or something. Errors about not being able to mount certain folders
___
3rd attempt:
1 - reboot to recovery
2 - try and sideload the ROM from my laptop with the command adb sideload name.zip
3 - fails around 40% with similar errors
___
4th attempt:
1 - reboot to bootloader
2 - try instead fastboot boot name.zip to flash the ROM. It gives me the error: requested download size is more than max allowed fastboot
___
In between these tries TWRP sometimes loses touchscreen functionality. I notice when I flash OrangeFox and then TWRP again, I get touchscreen functionality back. I know this is a well known issue but it's interesting I can back TWRP working again when doing the above.
Another interesting is that when I flash OrangeFox and reboot to recovery, it's still TWRP.
When you flash a new ROM, you need to format the userdata and the cache partitions.
EDIT:
Btw, i'm curious to know where you found your OrangeFox build. ^^
Sneilas said:
When you flash a new ROM, you need to format the userdata and the cache partitions.
EDIT:
Btw, i'm curious to know where you found your OrangeFox build. ^^
Click to expand...
Click to collapse
I believe I did format data, cache and dalvik cache as usual. Hm, will check again.
I forgot where I got the OrangeFox from. Might be nothing though.
kerelberel said:
I believe I did format data, cache and dalvik cache as usual. Hm, will check again.
I forgot where I got the OrangeFox from. Might be nothing though.
Click to expand...
Click to collapse
Btw, i do not recommand to flash unofficial images if the maintainer not released it's device tree on GitHub and not linked it on his thread.
We can't know what's inside the recovery.
The recovery can be infected by a malicious code.
Sneilas said:
When you flash a new ROM, you need to format the userdata and the cache partitions.
EDIT:
Btw, i'm curious to know where you found your OrangeFox build. ^^
Click to expand...
Click to collapse
So I made sure to format everything this time. But because I am stoopid I then accidentally sideloaded a MIUI ROM instead of Evolution. I copy/pasted the wrong file name in the cmd window, lol. I was surprised to see the Evolution logo after rebooting, so I got the ROM I wanted by accidentally flashing the other one.
Do I have MIUI on one partition and Evolution on the other? Is that even possible?
kerelberel said:
So I made sure to format everything this time. But because I am stoopid I then accidentally sideloaded a MIUI ROM instead of Evolution. I copy/pasted the wrong file name in the cmd window, lol. I was surprised to see the Evolution logo after rebooting, so I got the ROM I wanted by accidentally flashing the other one.
Do I have MIUI on one partition and Evolution on the other? Is that even possible?
Click to expand...
Click to collapse
From here, i recommand you to ask the maintainer of the Evolution X ROM of your device.
Send him your device infos (code name, processor, etc...).
If you can't access to these info on from phone, contact the reseller of your phone.
Maybe your specific device is not compatible with the ROM.
I'm not enough experienced to help you more.
I don't know if twrp works on veux.
I flashed the boot.img and vendor_boot.img provided by the custom ROM.
The custom ROM was updated using the sideload in recovery mode.
It must be unlocked. USB debug doesn't matter.
Sneilas said:
From here, i recommand you to ask the maintainer of the Evolution X ROM of your device.
Send him your device infos (code name, processor, etc...).
If you can't access to these info on from phone, contact the reseller of your phone.
Maybe your specific device is not compatible with the ROM.
I'm not enough experienced to help you more.
Click to expand...
Click to collapse
I'm fine now, the ROM works, afterwards I also installed Magisk successfully so TWRP works as expected too.
osebee said:
I don't know if twrp works on veux.
I flashed the boot.img and vendor_boot.img provided by the custom ROM.
The custom ROM was updated using the sideload in recovery mode.
It must be unlocked. USB debug doesn't matter.
Click to expand...
Click to collapse
It does, the one I linked in my first post is the one from this specific subforum.
If you need help you can PM me.
Seems like you've managed to fix the problem, and USB debugging only works when you're booted inside the rom, it doesn't do anything in recovery/fastboot.
kerelberel said:
I'm fine now, the ROM works, afterwards I also installed Magisk successfully so TWRP works as expected too.
It does, the one I linked in my first post is the one from this specific subforum.
If you need help you can PM me.
Click to expand...
Click to collapse
Oh ok, i thought you still had problems. ^^
Ritik17 said:
Seems like you've managed to fix the problem, and USB debugging only works when you're booted inside the rom, it doesn't do anything in recovery/fastboot.
Click to expand...
Click to collapse
USB debugging works in some stock/custom recoveries, but in stock recoveries it is limited to sideloading updates signed by the device manufacturer.