Related
Hello people
i'm aware that there are guides out there, but i'm honestly not the best at all this flashing stuff, i have done it to a few phones but this one needs to be done just right!
So, where should i begin?, i reckon i should start with unlocking the phone via the unlock tool (i am registered and accepted) and then flash TWRP via that tool?
or is the best/only way of flashing TWRP with the ADB fastboot?
Citroon said:
Hello people
i'm aware that there are guides out there, but i'm honestly not the best at all this flashing stuff, i have done it to a few phones but this one needs to be done just right!
So, where should i begin?, i reckon i should start with unlocking the phone via the unlock tool (i am registered and accepted) and then flash TWRP via that tool?
or is the best/only way of flashing TWRP with the ADB fastboot?
Click to expand...
Click to collapse
There is a Mi5 flashing tool, but I've never used it.
sent from my Mi5
Citroon said:
Hello people
i'm aware that there are guides out there, but i'm honestly not the best at all this flashing stuff, i have done it to a few phones but this one needs to be done just right!
So, where should i begin?, i reckon i should start with unlocking the phone via the unlock tool (i am registered and accepted) and then flash TWRP via that tool?
or is the best/only way of flashing TWRP with the ADB fastboot?
Click to expand...
Click to collapse
Use MiUnlock tool to unlock BL
Then flash TWRP through fasboot
otonieru said:
Use MiUnlock tool to unlock BL
Then flash TWRP through fasboot
Click to expand...
Click to collapse
my problem now is i have no idea how to get miui 7 on it. Iknow that all CM based roms will end in a bootloop if i try to flash with that on.
i have tried a number of things, last time i tried i ended up with it not detecting my sim card, so i had to revert back to Miui 8
Citroon said:
my problem now is i have no idea how to get miui 7 on it. Iknow that all CM based roms will end in a bootloop if i try to flash with that on.
i have tried a number of things, last time i tried i ended up with it not detecting my sim card, so i had to revert back to Miui 8
Click to expand...
Click to collapse
Use miflash tool to flash latest stable global miui 8, then flash CM
It will be fine. I went to CM that way
otonieru said:
Use miflash tool to flash latest stable global miui 8, then flash CM
It will be fine. I went to CM that way
Click to expand...
Click to collapse
i guess ill trust you then! =)
i have the latest stable rom with my bootloader unlocked i'll try to flash TWRP now
did you do that with ADB? seems like im a tad unlucky there as well. (i'm not a noob at this, nor a pro)
Citroon said:
i guess ill trust you then! =)
i have the latest stable rom with my bootloader unlocked i'll try to flash TWRP now
did you do that with ADB? seems like im a tad unlucky there as well. (i'm not a noob at this, nor a pro)
Click to expand...
Click to collapse
No, the MIUI need to be flashed through Miflash tool
TWRP through fastboot
And CM through TWRP
No adb at all
otonieru said:
No, the MIUI need to be flashed through Miflash tool
TWRP through fastboot
And CM through TWRP
No adb at all
Click to expand...
Click to collapse
my miflash wont detect my phone :/
Citroon said:
my miflash wont detect my phone :/
Click to expand...
Click to collapse
let me correct that, it wont detect the file
Citroon said:
let me correct that, it wont detect the file
Click to expand...
Click to collapse
What do you mean by that?
marcoly said:
What do you mean by that?
Click to expand...
Click to collapse
in the flash tool it simply says "error could not find the package"
Citroon said:
in the flash tool it simply says "error could not find the package"
Click to expand...
Click to collapse
Could you post screenshot of MiFlash showing path too?
marcoly said:
Could you post screenshot of MiFlash showing path too?
Click to expand...
Click to collapse
This is what it does, it finds my phone
Gyazo link: https://gyazo.com/a68917c96a4e9d6b3aa4da60ae671454
i locate the file, i've tried both in zip and as a normal folder.
Citroon said:
This is what it does, it finds my phone
Gyazo link: https://gyazo.com/a68917c96a4e9d6b3aa4da60ae671454
i locate the file, i've tried both in zip and as a normal folder.
Click to expand...
Click to collapse
this is another problem, when i want to flash TWRP it cant find my device
https://gyazo.com/9ef62b14719dcc9049b7103167921853
Your thread is getting slightly confusing so let's do it step by step.
Is your phone currently unlocked?
To check, put it into fastboot mode manually without adb:
Turn off your device. Then turn on your device again while holding volume down button.
Plug in your device. Use fastboot:
Code:
fastboot oem device-info
Post screenshots.
Reboot your phone. Post a screenshot of your "About phone" settings menu.
Citroon said:
Hello people
i'm aware that there are guides out there, but i'm honestly not the best at all this flashing stuff, i have done it to a few phones but this one needs to be done just right!
So, where should i begin?, i reckon i should start with unlocking the phone via the unlock tool (i am registered and accepted) and then flash TWRP via that tool?
or is the best/only way of flashing TWRP with the ADB fastboot?
Click to expand...
Click to collapse
I also tried this way.But not miflash tool. I use twrp to flash global stable rom,boot up the rom and flash twrp through fastboot.And then you can flash your favourite rom.
Hi,
sorry to hijack this thread, but i also have problem flashing TWRP.
I have unlocked phone.
I have USB debugging enabled.
I can reboot to fastboot via adb.
I ca flash twrp (twrp-3.0.2-1-gemini.img 25.2M 2016-07-19 18:48:36 EDT).
But when i go to recovery i still see Mi PcSuite thing. No twrp.
What am i doing wrong? IS there some other, more appropriate twrp image?
Svashtar said:
Hi,
sorry to hijack this thread, but i also have problem flashing TWRP.
I have unlocked phone.
I have USB debugging enabled.
I can reboot to fastboot via adb.
I ca flash twrp (twrp-3.0.2-1-gemini.img 25.2M 2016-07-19 18:48:36 EDT).
But when i go to recovery i still see Mi PcSuite thing. No twrp.
What am i doing wrong? IS there some other, more appropriate twrp image?
Click to expand...
Click to collapse
I got mine sorted out, what you are missing is when you are done flashinh you have to type "Fastboot reboot" and then set TWRP to default recovery
hope that helps you out
Same problem for me, when i type "Fastboot reboot", my Mi5 reboot quickly and after when i go to recovery i see also Mi PC Suite....
Do you have a workaround ?
Second question, is it normal that time to send TWRP.img to phone in ADB is only 0,9s ?
http://forum.xda-developers.com/showthread.php?p=69249337
sent from my MI5
Hi all
Sorry that my vocabulary wont be so pro.
I flashed yesterday EU stable rom 10.0.1.0.
Today I flashed back global 8.8.30 using twrp, wiped data and it has finish ok, but made loop boot and backed to twrp once again.
then flashed 9.5.13.0 global, ended OK, didn't boot well and backed me to recovery screen.
by ADB I tried to go back to TWRP and it boot to "the system has been destroyed".
Nothing i do not help, by info with ADB looks like the bootlouder is closed some how.
I cannot open in since it is writing me that the account not connected to the to the phone, and i cannot do anything since the phone is not going up.
any ideas?
dorone said:
Hi all
Sorry that my vocabulary wont be so pro.
I flashed yesterday EU stable rom 10.0.1.0.
Today I flashed back global 8.8.30 using twrp, wiped data and it has finish ok, but made loop boot and backed to twrp once again.
then flashed 9.5.13.0 global, ended OK, didn't boot well and backed me to recovery screen.
by ADB I tried to go back to TWRP and it boot to "the system has been destroyed".
Nothing i do not help, by info with ADB looks like the bootlouder is closed some how.
I cannot open in since it is writing me that the account not connected to the to the phone, and i cannot do anything since the phone is not going up.
any ideas?
Click to expand...
Click to collapse
if this is a Chinese version phone, you need to flash the region fix, and also the dm-verity disabler after the ROM and also wipe DATA.
Agimax said:
if this is a Chinese version phone, you need to flash the region fix, and also the dm-verity disabler after the ROM and also wipe DATA.
Click to expand...
Click to collapse
Hi
many thanks for your answer
How i am doing it?
phone is not working, not twrp.
tried now to flash chinese last rom - nogo
dorone said:
Hi
many thanks for your answer
How i am doing it?
phone is not working, not twrp.
tried now to flash chinese last rom - nogo
Click to expand...
Click to collapse
If you don't have TWRP anymore, and MIflashtool isn't working, then if your phone is still unlocked, flash the TWRP again through fastboot. If not, i'm not sure.
I have a Chinese to Global thread here-->https://forum.xda-developers.com/mi-8/help/chinese-mi8-to-global-instructions-t3839665
10.0.1.0 has ARB hasn't it?
_katho_ said:
10.0.1.0 has ARB hasn't it?
Click to expand...
Click to collapse
I not 100% sure but I will go for that also, its sad but probably he screw his phone.
1. he confirm he have locked bootloader
2. no access to system nor miflash detect so no bootloader unlock
3. no bootloader, so no flashing twrp.
I dont have any good news, nor any solution to even help you.
freeman94 said:
I not 100% sure but I will go for that also, its sad but probably he screw his phone.
Click to expand...
Click to collapse
Yep, everywhere I've seen MIUI 10 10.x stable have ARB. It's the reason I haven't flashed it, as I read before..
Hello all, i unlocked the bootloader on the xiaomi mi A2 , and i was trying to follow this guide :https://forum.xda-developers.com/mi-a2/how-to/tutorial-camera2api-gcam-root-t3842475 to install the gmcam, but after the point 5. i just rebooted the phone from the recovery, just cause i wanted to try it, after that is stucked in android 8.1 animation, but i have access to the recovery (even if the tool shouldnt have installed it), but dunno what can i do from the recovery, and the device can go in fastboot mode but is not recognized by adb, what can i do?
What version of software was your Mi A2, if it was V9.6.13.0.ODIMIFE, then download the full stock ROM from here
http://en.miui.com/download-353.html
In fastboot mode, adb is not working, fastboot commands works there.
Extract boot.img from images of downloaded ROM.
Put the boot.img in adb folder.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
it should start normally
If not, then flash every image like in this post.
https://forum.xda-developers.com/showpost.php?p=77302899&postcount=4
minnuss said:
What version of software was your Mi A2, if it was V9.6.13.0.ODIMIFE, then download the full stock ROM from here
http://en.miui.com/download-353.html
In fastboot mode, adb is not working, fastboot commands works there.
Extract boot.img from images of downloaded ROM.
Put the boot.img in adb folder.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
it should start normally
If not, then flash every image like in this post.
https://forum.xda-developers.com/showpost.php?p=77302899&postcount=4
Click to expand...
Click to collapse
Thanks for the help, but, I don't know why, ADB driver were not working properly, didnt recognize the phone so I couldnt follow this guide, and i couldnt switch off the phone either, it was stuck in bootloop, the only thing I was able to do is to put the device in fastboot mode using the button combination..
Luckly the Mi Flash tool was able to recognize the device so I flashed the stock rom with that and now everything is back to normal, I've just a question, the phone sais that the bootloader is still unlocked, is that true? Even if I've flashed from zero the stock rom?
fuffy841 said:
Thanks for the help, but, I don't know why, ADB driver were not working properly, didnt recognize the phone so I couldnt follow this guide, and i couldnt switch off the phone either, it was stuck in bootloop, the only thing I was able to do is to put the device in fastboot mode using the button combination..
Luckly the Mi Flash tool was able to recognize the device so I flashed the stock rom with that and now everything is back to normal, I've just a question, the phone sais that the bootloader is still unlocked, is that true? Even if I've flashed from zero the stock rom?
Click to expand...
Click to collapse
Yep, it's true. You have to relock the bootloader, but this cause full wipe. IMO there's no need to relock the bootloader if you not enable the usb dev mode.
Also, theres an option in mi flash tool to lock the bootloader after flash. Something like flash_all_lock
DO NOT use flash_all_lock_crc. This will cause dead wifi and Bluetooth modem.
I am stuck on the exact same issue. Can you explain in detail all the steps you followed.
Mine was updated to September patch and it is Indian variant.
---------- Post added at 06:16 PM ---------- Previous post was at 05:31 PM ----------
rt1279_isBITW said:
I am stuck on the exact same issue. Can you explain in detail all the steps you followed.
Mine was updated to September patch and it is Indian variant.
Click to expand...
Click to collapse
Nvm I was able to flash that rom but now after the phone locks once the touch is gone until I reboot the device.
Are there any hardware differences in my indian variant or did I just flash it wrong?
I used flash_all.bat and clean all option.
Daniesz said:
Yep, it's true. You have to relock the bootloader, but this cause full wipe. IMO there's no need to relock the bootloader if you not enable the usb dev mode.
Also, theres an option in mi flash tool to lock the bootloader after flash. Something like flash_all_lock
DO NOT use flash_all_lock_crc. This will cause dead wifi and Bluetooth modem.
Click to expand...
Click to collapse
Nono i want to keep the bootloader unlocked, that's why I asked ! Thanks man.
Nvm I was able to flash that rom but now after the phone locks once the touch is gone until I reboot the device.
Are there any hardware differences in my indian variant or did I just flash it wrong?
I used flash_all.bat and clean all option
Click to expand...
Click to collapse
I used the same option, cause it didnt work with the other ones.. I didnt have any issue so far tho, and I dont know about hardware differences, but I dont think a bad flash can cause this kind of problem, not sure tho. Maybe now that everything is working try to flash again a stock rom.
TLDR: I tried installing AEX rom and I bricked my mi9, getting it in a fastboot loop. Flashed a bunch of things and now I think my firmware is messed up. Help.
First I flashed TWRP, then I flashed the AEX rom and gapps, but phone got in bootloop, then I tried just flashing the ROM and it worked. After I flashed gaps it got into bootloop again.
Then I read the instructions from the AEX thread and I flash the recommended Firmware file (v9.6.13), and the flash failed.
I wiped everything, reflashed the ROM without gapps, and at restart the phone. Got stuck in fastboot.
Tried reinstalling TWRP with no success. Tried flashing MIUI with their flash tool but it didn't ended the flash procedure even after 20 minutes...
I tried to directly boot the recovery image (TWRP) and I was surprised that the phone booted in MIUI, but wifi wasn't working. Did not test anything else. Restarting the phone got me again in fastboot loop.
I tried again flashing with mi flash tool and this time was succesfull.
Then I tried to flash a MIUI eu ROM and got the phone again in fastboot loop. Flash was succesfull, but when restarting TWRP said that there is no OS installed.
I decided to give up and flash global MIUI 10.2.13 back.
But now my phone has some problems. Auto brightness doesn't work and video recording freezes the camera app when image stabilization is enabled.
So, is there a way to reflash 10.2.13 rom firmware using mi flash tool?
I suppose the first Firmware flash that was unsuccessful messed the firmware up...
Or how do I get my phone back to factory status...
I suppose v9.6.13 firmware is China developer and was an upgrade and that I should downgrade to 10.2.13 rom firmware.
Or flashing developer global will solve the problem? And how do I do that?
TWRP: https://forum.xda-developers.com/Mi-9/development/recovery-twrp-3-3-1-siankatabg-t3934962
AEX: https://forum.xda-developers.com/Mi-9/development/rom-aospextended-v6-6-t3956100
Have you ever tried fastboot rom ? Now it's the only solution to recover your phone !
macgyverx86 said:
TLDR: I tried installing AEX rom and I bricked my mi9, getting it in a fastboot loop. Flashed a bunch of things and now I think my firmware is messed up. Help.
First I flashed TWRP, then I flashed the AEX rom and gapps, but phone got in bootloop, then I tried just flashing the ROM and it worked. After I flashed gaps it got into bootloop again.
Then I read the instructions from the AEX thread and I flash the recommended Firmware file (v9.6.13), and the flash failed.
I wiped everything, reflashed the ROM without gapps, and at restart the phone. Got stuck in fastboot.
Tried reinstalling TWRP with no success. Tried flashing MIUI with their flash tool but it didn't ended the flash procedure even after 20 minutes...
I tried to directly boot the recovery image (TWRP) and I was surprised that the phone booted in MIUI, but wifi wasn't working. Did not test anything else. Restarting the phone got me again in fastboot loop.
I tried again flashing with mi flash tool and this time was succesfull.
Then I tried to flash a MIUI eu ROM and got the phone again in fastboot loop. Flash was succesfull, but when restarting TWRP said that there is no OS installed.
I decided to give up and flash global MIUI 10.2.13 back.
But now my phone has some problems. Auto brightness doesn't work and video recording freezes the camera app when image stabilization is enabled.
So, is there a way to reflash 10.2.13 rom firmware using mi flash tool?
I suppose the first Firmware flash that was unsuccessful messed the firmware up...
Or how do I get my phone back to factory status...
I suppose v9.6.13 firmware is China developer and was an upgrade and that I should downgrade to 10.2.13 rom firmware.
Or flashing developer global will solve the problem? And how do I do that?
TWRP: https://forum.xda-developers.com/Mi-9/development/recovery-twrp-3-3-1-siankatabg-t3934962
AEX: https://forum.xda-developers.com/Mi-9/development/rom-aospextended-v6-6-t3956100
Click to expand...
Click to collapse
Hmm, so where are you at now!? Have you got twrp installed? and 10.2.13 but with issues, right? or are you on stock recovery?
Current status: I managed to flash fastboot global ROM in mi flash, and stock recovery.
But the firmware is messed up.
Camera doesn't work well. And from normal use I saw that Gyroscope, light sensor and compas aren't working at all...
Phone reboots itself and I can't unlock it because pattern isn-t recognized anymore, untill I reset it by long pressing the power button.
From CIT menu gyro, light sensor and compass are definitely not working.
Would flashing latest firmware from TWRP be a possible solution? My bootloader is still unlocked and I can flash TWRP.
Or should I format vendor partition first? And then flash firmware?
Fastboot flash did solved firmware problem.
macgyverx86 said:
Current status: I managed to flash fastboot global ROM in mi flash, and stock recovery.
But the firmware is messed up.
Camera doesn't work well. And from normal use I saw that Gyroscope, light sensor and compas aren't working at all...
Phone reboots itself and I can't unlock it because pattern isn-t recognized anymore, untill I reset it by long pressing the power button.
From CIT menu gyro, light sensor and compass are definitely not working.
Would flashing latest firmware from TWRP be a possible solution? My bootloader is still unlocked and I can flash TWRP.
Or should I format vendor partition first? And then flash firmware?
Fastboot flash did solved firmware problem.
Click to expand...
Click to collapse
To be honest I'm not entirely sure if it'll help, but, I'd put global stable flashable zip on otg, then I'd flash twrp again, boot to twrp using buttons not commands, wipe cache, dalvik, vendor, system, data, internal. Then format data, swiping with confirmation 'yes'. Then flash latest global again over the clean device from otg. You could try using mauronfrio's twrp 3.3.1-35 instead of the one you linked get it here. That's just what I'd try, can't say whether it'll help and no guarantees it'll fix anything... Let us know the outcome bud.
You can download the latest flashable rom from here
I can't see why ur sensors etc aren't working anymore, it's got to be all software related me thinks
Do not try to reboot after wipes, you'll have nothing installed
reg66 said:
... I'd put global stable flashable zip on otg, then I'd flash twrp again, boot to twrp using buttons not commands, wipe cache, dalvik, vendor, system, data, internal. Then format data, swiping with confirmation 'yes'. Then flash latest global again over the clean device from otg. ....
Click to expand...
Click to collapse
Correct me if I am wrong, but flashing a stock MIUI zip form twrp won't work.
Or you are saying that I should flash a xiaomi eu ROM?
Got another sugestion:
Someone said that there is the posibility that mi flash didn't flash persist partition and that I should try to force flash it.
Referred thread here: https://forum.xda-developers.com/re.../how-to-flash-persist-partiton-redmi-t3830310
Is this a possibility?
And shouldn't mi flash reflash everything?
macgyverx86 said:
Correct me if I am wrong, but flashing a stock MIUI zip form twrp won't work.
Or you are saying that I should flash a xiaomi eu ROM?
Click to expand...
Click to collapse
Hold tight bud, just checking. I remember doing that - and the stock rom flashes but you no longer have twrp, it flashes the whole system/vendor including recovery. But hang on 'cos I might be recalling my pocophone F1 for that proceedure. The reason I suggest to reflash twrp is simply to have better control over a fully clean wipe, before progressing to flash rom again. Like I say, hang on just checking...
---------- Post added at 08:49 PM ---------- Previous post was at 08:47 PM ----------
macgyverx86 said:
Got another sugestion:
Someone said that there is the posibility that mi flash didn't flash persist partition and that I should try to force flash it.
Referred thread here: https://forum.xda-developers.com/re.../how-to-flash-persist-partiton-redmi-t3830310
Is this a possibility?
And shouldn't mi flash reflash everything?
Click to expand...
Click to collapse
Yes, miflash should flash everything, but you say you started flashing other stuff when it all went wrong, so I'm really not sure what's happened to ur device. Hang on anyway, still checking on the flashable zip ..
---------- Post added at 09:06 PM ---------- Previous post was at 08:49 PM ----------
Nope, I think you're right, it was the poco I was getting muddled with - haven't had to do this in while (poco has flashable stock zips somewhere...). It is possible to do it with lazy flasher, but that may start getting messy again. Have you tried re-flashing fastboot? Can you wipe much at all in the stock recovery - again, I can't remember.
Failing that, yeah, I'd seriously consider flashing twrp and flashing mi-globe or eu rom. I prefer mi-globe (although currently using beast rom) over eu simply because you can customize it more on the website. Though, I wouldn't recommend pre-rooting it. Root after, if need be. Any way, we'll cross that bridge later... For now just try to re-flash
reg66 said:
Can you wipe much at all in the stock recovery - again, I can't remember.
Click to expand...
Click to collapse
Didn't get this.
Is it ok to format vendor partition? will it be recreated wen flashing again? using mi flash or from twrp?
macgyverx86 said:
Didn't get this.
Is it ok to format vendor partition? will it be recreated wen flashing again? using mi flash or from twrp?
Click to expand...
Click to collapse
I'm pretty sure you won't be able to wipe much in stock recovery, but just wipe what you can and try and re-flash fastboot. Don't flash twrp yet. You could try downloading again the fastboot file, in case of any corruption. Hopefully on the second flash all will be well. But that said, it should've been OK on the first flash :/ in theory
just flashed xiaomi eu rom and everything seems to work now. All sensors are working.
I had to disable signature check, and i got an mounting /system error -> got the message that is installed without changes... whatever that means
And now in TWRP, I think, my files are encrypted without enabling it.
Will try other roms later.
Thanks for the help.
macgyverx86 said:
just flashed xiaomi eu rom and everything seems to work now. All sensors are working.
I had to disable signature check, and i got an mounting /system error -> got the message that is installed without changes... whatever that means
And now in TWRP, I think, my files are encrypted without enabling it.
Will try other roms later.
Thanks for the help.
Click to expand...
Click to collapse
Glad you got it working, phew!
macgyverx86 said:
just flashed xiaomi eu rom and everything seems to work now. All sensors are working.
I had to disable signature check, and i got an mounting /system error -> got the message that is installed without changes... whatever that means
And now in TWRP, I think, my files are encrypted without enabling it.
Will try other roms later.
Thanks for the help.
Click to expand...
Click to collapse
Go the same problem as you,i tried Android Q beta rom and after reflashing stock fastboot rom with mi flash,the sensors and video not working,any solution?
gm007 said:
Go the same problem as you,i tried Android Q beta rom and after reflashing stock fastboot rom with mi flash,the sensors and video not working,any solution?
Click to expand...
Click to collapse
I just flashed Xiaomi EU rom, did a CIT test and all sensors were working.
Try that. I'm curious it it works for you.
macgyverx86 said:
I just flashed Xiaomi EU rom, did a CIT test and all sensors were working.
Try that. I'm curious it it works for you.
Click to expand...
Click to collapse
Yes it worked with eu rom,but i managed to fix it on stock global stable by flashing an old miui 10.2.6 fastboot rom,Than updated to the latest one 10.2.13
gm007 said:
Yes it worked with eu rom,but i managed to fix it on stock global stable by flashing an old miui 10.2.6 fastboot rom,Than updated to the latest one 10.2.13
Click to expand...
Click to collapse
So 10.2.13 fastboot image is to blame here.
macgyverx86 said:
So 10.2.13 fastboot image is to blame here.
Click to expand...
Click to collapse
Not sure maybe flashing eu rom first have fix it .
Hello, i have a redmi note 9,
I was using lineage OS from here https://t.me/HelioG85_Updates/265
Custom firmware, custom opensource vendor
I wasnt able to boot into the recovery today for some reason, i was using the recovery from here https://t.me/HelioG85_Updates/268
In a moment of genius, i decided to get this app https://play.google.com/store/apps/details?id=net.mxbi.reboot and used it to boot to the recovery , now my device is bricked, doesnt enter fastboot or the recovery , and i cant turn the device of meaning i cant flash with sp flash tool
My bootloader is unlocked. i do not have a xiaomi account anymore
I have my imei and nvdata backed up, so i should be fine on that regard
Please do help me, This is the only phone i have and i cannot get a another one . If you help me i will be forever greatfull to you, Please help me i am desperate
Ifuckinghatemyselfandall said:
Hello, i have a redmi note 9,
I was using lineage OS from here https://t.me/HelioG85_Updates/265
Custom firmware, custom opensource vendor
I wasnt able to boot into the recovery today for some reason, i was using the recovery from here https://t.me/HelioG85_Updates/268
In a moment of genius, i decided to get this app https://play.google.com/store/apps/details?id=net.mxbi.reboot and used it to boot to the recovery , now my device is bricked, doesnt enter fastboot or the recovery , and i cant turn the device of meaning i cant flash with sp flash tool
My bootloader is unlocked. i do not have a xiaomi account anymore
I have my imei and nvdata backed up, so i should be fine on that regard
Please do help me, This is the only phone i have and i cannot get a another one . If you help me i will be forever greatfull to you, Please help me i am desperate
Click to expand...
Click to collapse
So sp flash tool will lock your phone to engineer mode if it turns off follow this instruction:
prepare sp flash tools to only flash recovery (the one you want to boot into)
then click the download button to start flash
then wait for phone to get to boot( when image appears, before it gets to reboot plugin your phone to pc)
sp flash tools will flash then when done make sure you reboot to the custom recovery
then if you can access your system from recovery , look next to build.rop for recovery or rebootfromrecovery.p
copy the file somewhere
edit in notepad to clear everything, save it then use the edited one to overwrite
flairepathos.info said:
So sp flash tool will lock your phone to engineer mode if it turns off follow this instruction:
prepare sp flash tools to only flash recovery (the one you want to boot into)
then click the download button to start flash
then wait for phone to get to boot( when image appears, before it gets to reboot plugin your phone to pc)
sp flash tools will flash then when done make sure you reboot to the custom recovery
then if you can access your system from recovery , look next to build.rop for recovery or rebootfromrecovery.p
copy the file somewhere
edit in notepad to clear everything, save it then use the edited one to overwrite
Click to expand...
Click to collapse
I am going to try the mtk bypass tool, is that going to work? if not i am going to try your instructions, however it did not boot into the recovery even after reflashing , i have tried that before with the twrp app
It cannot detect the device, it isnt in device manager either, i am getting scared
edit: actually it gets detected in device manager as "usb serial device (com4)" when i hold the power button, volume up and volume down at the same time, when i do that, the device stays with a black screen
SP flash tool still does not detect it
it seems to be disconnecting while in this state
Please help, i cant turn the device off
sp flash tool says STATUS_EXT_RAM_EXCEPTION i was trying to flash miui 12.5 R i will try flashing 12.0.5 q since thats what people are using
Ifuckinghatemyselfandall said:
sp flash tool says STATUS_EXT_RAM_EXCEPTION i was trying to flash miui 12.5 R i will try flashing 12.0.5 q since thats what people are using
Click to expand...
Click to collapse
You need to flash the SAME miui version present on the device first.
VD171 said:
You need to flash the SAME miui version present on the device first.
Click to expand...
Click to collapse
But i do not know which version was present before, i was using a custom rom when it bricked...
I do think it was running 12.0.6 EEA Q
i am trying to flash miui 12.0.5 global, will that be okay?
It is now giving me "error status error" please help
Ifuckinghatemyselfandall said:
But i do not know which version was present before, i was using a custom rom when it bricked...
I do think it was running 12.0.6 EEA Q
i am trying to flash miui 12.0.5 global, will that be okay?
Click to expand...
Click to collapse
Certainly, mixing files from different miui versions, bricked your device.
You need to flash the correct miui version to fix the partition table.
And then, you can flash another miui version using fastboot.
VD171 said:
Certainly, mixing files from different miui versions, bricked your device.
You need to flash the correct miui version to fix the partition table.
And then, you can flash another miui version using fastboot.
Click to expand...
Click to collapse
No, this is not waht bricked my device, i rebooted to a custom recovery while on a custom rom and thats when it happened
Ifuckinghatemyselfandall said:
No, this is not waht bricked my device, i rebooted to a custom recovery while on a custom rom and thats when it happened
Click to expand...
Click to collapse
Custom recovery will never brick a device.
VD171 said:
Custom recovery will never brick a device.
Click to expand...
Click to collapse
You dont seem to understand what i am saying, It does not if you disable boot verification, which i did , please reread the post
Ilovethewholeworldbutme said:
You dont seem to understand what i am saying, It does not if you disable boot verification, which i did , please reread the post
Click to expand...
Click to collapse
Just flash the full stock miui again.