Related
Hi guys, i need some help pleeease!
I was with the November security patch on my cell phone, I unlock the bootloader and went to use the friend tool (https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585) to activate the camera2api.
But it gave problem and the cell phone did not turn on, it was locked in the screen of android one.
So I downloaded the patched_boot.img from the version I was in and put it via fastboot. did not work.
Now, my phone is in this situation: I tried to use MiFlash (three versison: 2018528, 2017720 and 20151028) and they fail in the middle of the process, accusing "FAILED (command write failed (Unknown error))".
And: when I try to connect the cell phone normally, it shows the unlocked bootloader warning and goes straight to the fastboot, even without my request. This is strange. Perhaps because the system is damaged by the miflash unfinished
Obs: bootloader are unlocked and i can access twrp
If anyone can help me I will be very grateful and happy
What exactly did the "tool" do? I mean if you don't know that, pretty difficult to diagnose what's wrong...
AsItLies said:
What exactly did the "tool" do? I mean if you don't know that, pretty difficult to diagnose what's wrong...
Click to expand...
Click to collapse
Hi.
The tool (her topic link is up there) promised to activate camera2api without root my device (allowing OTAs in the future).
I believe she did a "temporary root" with a "temporary" boot.img just to activate the camera2api, and when it rebooted, it would return to normal boot.img without root. I do not know if I could explain it well.
The current issue is that it seems that the system is currently "destroyed or corrupted". Can not I reinstall the entire system through TWRP? Or something like this
Like I said, you don't know what it actually did. What it promised is one thing, what it did... another
That's the problem with 'tools'.
Have you tried doing a factory reset? Hold Vol up and power until it gets to Recovery (hopefully), if you do a quick press of vol up, that gets past the 'no command'. Then use vol up and down for selection and press power when on 'factory reset'.
It might work
AsItLies said:
Like I said, you don't know what it actually did. What it promised is one thing, what it did... another
That's the problem with 'tools'.
Have you tried doing a factory reset? Hold Vol up and power until it gets to Recovery (hopefully), if you do a quick press of vol up, that gets past the 'no command'. Then use vol up and down for selection and press power when on 'factory reset'.
It might work
Click to expand...
Click to collapse
You are right, friend.. this is the problems with tools! I never use tools with my A1 and past phones.. just this time :crying:
I tried the factory reset now. And it did not work, unfortunately. On the first attempt (I was in fastboot mode) he showed a white circle with the writing "ERASING" and then went back to the screen of Android One, and then I tried again Vol Up + Power and he appeared "No command" , and after I rebooted and tried again, nothing appears, it just restarts to the static screen of "Android One"
Another ideas?
erickxd said:
You are right, friend.. this is the problems with tools! I never use tools with my A1 and past phones.. just this time :crying:
I tried the factory reset now. And it did not work, unfortunately. On the first attempt (I was in fastboot mode) he showed a white circle with the writing "ERASING" and then went back to the screen of Android One, and then I tried again Vol Up + Power and he appeared "No command" , and after I rebooted and tried again, nothing appears, it just restarts to the static screen of "Android One"
Another ideas?
Click to expand...
Click to collapse
The only other thing I can think of would be to change the current slot. If that works you would be booted into the prior version of the OS vs the latest update you did.
In fastboot, do fastboot getvar current-slot
Depending on what that slot is, change it to the other one (can only be a or b)
thus fastboot set_active a (or b, whichever is not the current one)
then fastboot reboot - and hope it boots.
AsItLies said:
The only other thing I can think of would be to change the current slot. If that works you would be booted into the prior version of the OS vs the latest update you did.
In fastboot, do fastboot getvar current-slot
Depending on what that slot is, change it to the other one (can only be a or b)
thus fastboot set_active a (or b, whichever is not the current one)
then fastboot reboot - and hope it boots.
Click to expand...
Click to collapse
Well... fastboot don't recognize this command, he show the list of avaible commands
And i don't know why, but for now i can't boot in twrp.img
i'm going crazy :crying::crying::crying:
erickxd said:
Well... fastboot don't recognize this command, he show the list of avaible commands
And i don't know why, but for now i can't boot in twrp.img
i'm going crazy :crying::crying::crying:
Click to expand...
Click to collapse
That's probably because you have an old version of fastboot installed. Upgrade to the newest version, which should recognize dual slots.
dual slots are quite new.
AsItLies said:
That's probably because you have an old version of fastboot installed. Upgrade to the newest version, which should recognize dual slots.
dual slots are quite new.
Click to expand...
Click to collapse
Fastboot updated now! I changed the slot from B to A.
But doesn't work, unfortunately. After reboot, the phone can't boot and appears the screen asking between Try Boot Again or Factory Reset. I tried Factory Reset, but don't work =( return to the same screen.
What seems very strange to me, is the Miflash doesn't work. With my Mi A1 miflash ever save me
erickxd said:
Fastboot updated now! I changed the slot from B to A.
But doesn't work, unfortunately. After reboot, the phone can't boot and appears the screen asking between Try Boot Again or Factory Reset. I tried Factory Reset, but don't work =( return to the same screen.
What seems very strange to me, is the Miflash doesn't work. With my Mi A1 miflash ever save me
Click to expand...
Click to collapse
I've never used miflash, so no help there.
I'd try flashing the correct boot.img (for your software version). You can find the various boot images in the following link (don't forget to thank user ckpv5 for uploading these).
https://sourceforge.net/projects/others/files/Xiaomi_MiA2/
you would do fastboot flash boot_b boot.img
I'd suggest using b slot, as that was originally active. After flashing, set it back to active, try to reboot... then cross your fingers
AsItLies said:
I've never used miflash, so no help there.
I'd try flashing the correct boot.img (for your software version). You can find the various boot images in the following link (don't forget to thank user ckpv5 for uploading these).
https://sourceforge.net/projects/others/files/Xiaomi_MiA2/
you would do fastboot flash boot_b boot.img
I'd suggest using b slot, as that was originally active. After flashing, set it back to active, try to reboot... then cross your fingers
Click to expand...
Click to collapse
Doesn't work man.. I went to twrp and checking there in the "WIPES session", I saw that the SYSTEM partition is 0kb used and 0kb free. Appears to be entirely empty
Do not have a way to install the whole system via twrp?
erickxd said:
Doesn't work man.. I went to twrp and checking there in the "WIPES session", I saw that the SYSTEM partition is 0kb used and 0kb free. Appears to be entirely empty
Do not have a way to install the whole system via twrp?
Click to expand...
Click to collapse
No, I don't. But I can tell you, twrp is a recovery app. It shouldn't be in the boot slot. And, with dual slot configurations, there is no recovery partition. The other slot is now used to do a recovery.
In other words, the way we *used* to use twrp doesn't work on dual slot phones. I think that's a big part of the confusion people are having. While the boot images do have a small recovery part to them, it's not a separate partition.
If you're flashing boot.img, and setting that slot active, I've no idea how you're getting into twrp.
Since now your fastboot is working why don't you use miflash to flash official stock ROM
1. You need unlocked bootloader which you already have.
2. Run these command to unlock critical partition
fastboot flashing unlock_critical
3 . Download the official fastboot V9.6.14.0 ROM from
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445
Or here
http://en.miui.com/getrom.php?r=353&m=yes&app=false
4. Install with miflash (you already know the how-to)
5. Once up & running, do OTA to latest
Later .. redo what you want to do like enable camera api2 with proper guide.
E.g: https://forum.xda-developers.com/mi-a2/how-to/how-to-enable-cam2api-simply-ota-t3858861
ckpv5 said:
Since now your fastboot is working why don't you use miflash to flash official stock ROM
1. You need unlocked bootloader which you already have.
2. Run these command to unlock critical partition
fastboot flashing unlock_critical
3 . Download the official fastboot V9.6.14.0 ROM from
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445
Or here
http://en.miui.com/getrom.php?r=353&m=yes&app=false
4. Install with miflash (you already know the how-to)
5. Once up & running, do OTA to latest
Later .. redo what you want to do like enable camera api2 with proper guide.
E.g: https://forum.xda-developers.com/mi-a2/how-to/how-to-enable-cam2api-simply-ota-t3858861
Click to expand...
Click to collapse
Hello.
I've tried using Miflash several times (3 different versions), but it never ends, it end up with an error every time that he will copy the file system.img to the mobile phone (I analyzed the log).
The miflash divides the file system.img into 5 or 6 smaller parts to be able to transfer to the mobile phone, and in some of these parts gives error, everytime :crying:
AsItLies said:
No, I don't. But I can tell you, twrp is a recovery app. It shouldn't be in the boot slot. And, with dual slot configurations, there is no recovery partition. The other slot is now used to do a recovery.
In other words, the way we *used* to use twrp doesn't work on dual slot phones. I think that's a big part of the confusion people are having. While the boot images do have a small recovery part to them, it's not a separate partition.
If you're flashing boot.img, and setting that slot active, I've no idea how you're getting into twrp.
Click to expand...
Click to collapse
I can access twrp when I flash ''fastboot boot twrp.img" in powershell, so until the next reboot I have access to twrp
erickxd said:
Hello.
I've tried using Miflash several times (3 different versions), but it never ends, it end up with an error every time that he will copy the file system.img to the mobile phone (I analyzed the log).
The miflash divides the file system.img into 5 or 6 smaller parts to be able to transfer to the mobile phone, and in some of these parts gives error, everytime :crying:
Click to expand...
Click to collapse
When I read your post here - https://forum.xda-developers.com/showpost.php?p=78085858&postcount=188
"flashing is not allowed for critical partitions" usually due to critical partitions not unlocked. So .. if you already run "fastboot flashing unlock_critical" and you still have error using miflash .. nothing much I can offer to help. Hopefully you'll be able to fix it.
ckpv5 said:
When I read your post here - https://forum.xda-developers.com/showpost.php?p=78085858&postcount=188
"flashing is not allowed for critical partitions" usually due to critical partitions not unlocked. So .. if you already run "fastboot flashing unlock_critical" and you still have error using miflash .. nothing much I can offer to help. Hopefully you'll be able to fix it.
Click to expand...
Click to collapse
Hmm thanks for the answer!
Even when the operation fails after transfer a couple of archives before the system.img??? (on the Miflash)
If my phone was locked, Miflash could transfer these couple of archives before the operation fails?? Or if bootloader is locked, zero files can be passed by Miflash, and the error is apresented at the beginning of the operation?
Have you successfully unlocked critical partitions?
If yes, try to run flash_all.bat from the official stock image you downloaded. No need to use MiFlash.
prokaryotic cell said:
Have you successfully unlocked critical partitions?
If yes, try to run flash_all.bat from the official stock image you downloaded. No need to use MiFlash.
Click to expand...
Click to collapse
well... When I just run flash_all.bat from the stock image folder, the .bat file will recognize that I am running it for the connected mobile?
how exactly should I run flash_all.bat? just double clicking it in stock image folder? or should I copy the .bat to /adb folder and open power shell prompt in adb folder and execute the .bat from there? sorry for my ignorance
Can you show me, please?
erickxd said:
well... When I just run flash_all.bat from the stock image folder, the .bat file will recognize that I am running it for the connected mobile?
how exactly should I run flash_all.bat? just double clicking it in stock image folder? or should I copy the .bat to /adb folder and open power shell prompt in adb folder and execute the .bat from there? sorry for my ignorance
Can you show me, please?
Click to expand...
Click to collapse
Before someone can explain that, why don't you answer the question asked .. in fact at least 3 people was asking/telling ...
"Have you successfully unlocked critical partitions?"
Without the proper answer from you, not easy to help.
Hi everyone.
I have a OnePlus 3t. It's not rooted and bootloader is locked. The current state of my device is that the screen is completely black and shows no LEDs. I know leaving it for a few hours it will come back on, this is due to me getting into fastboot and turning off the phone. It was stuck in recovery. Everytime it was on it would boot to recovery. I've tried deleted cache, resetting and it was doing nothing. Can anyone help me as to how to fix this? I know it's not a hardware issue. Tried to research on here but I'm at a loose end.
Thanks in advance for any help.
mrandmrshemming said:
Hi everyone.
I have a OnePlus 3t. It's not rooted and bootloader is locked. The current state of my device is that the screen is completely black and shows no LEDs. I know leaving it for a few hours it will come back on, this is due to me getting into fastboot and turning off the phone. It was stuck in recovery. Everytime it was on it would boot to recovery. I've tried deleted cache, resetting and it was doing nothing. Can anyone help me as to how to fix this? I know it's not a hardware issue. Tried to research on here but I'm at a loose end.
Thanks in advance for any help.
Click to expand...
Click to collapse
I would try flashing the OOS ROM again. This might fix the problem.
Also, you should have posted this in the OnePlus 3T q&a forum, not here.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
I would try flashing the OOS ROM again. This might fix the problem.
Also, you should have posted this in the OnePlus 3T q&a forum, not here.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
What is the oos ROM? Also, can I do that via ADB and sideloading it?
mrandmrshemming said:
What is the oos ROM? Also, can I do that via ADB and sideloading it?
Click to expand...
Click to collapse
I mean the official Oxygen OS installation file that you can download from https://downloads.oneplus.com/ (if you're using OOS 5.0.8) or from https://forum.xda-developers.com/on...genos-5-0-1-android-8-0-t3728119/post75026505 (if you're using OOS 9.0.3 or 9.0.4)
And I believe you can sideload it via ADB, though I've never actually done that using the stock recovery.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
I mean the official Oxygen OS installation file that you can download from https://downloads.oneplus.com/ (if you're using OOS 5.0.8) or from https://forum.xda-developers.com/on...genos-5-0-1-android-8-0-t3728119/post75026505 (if you're using OOS 9.0.3 or 9.0.4)
And I believe you can sideload it via ADB, though I've never actually done that using the stock recovery.
Click to expand...
Click to collapse
So I did as you said, sideloaded the file via ADB. It says installation successful. I rebooted and then it boots into recovery again. Thanks for that though, still stuck however.
mrandmrshemming said:
So I did as you said, sideloaded the file via ADB. It says installation successful. I rebooted and then it boots into recovery again. Thanks for that though, still stuck however.
Click to expand...
Click to collapse
Have you tried to make a factory reset in recovery?
You have downhloaded the right file for your phone from OnePlus?
Master_TC said:
Have you tried to make a factory reset in recovery?
You have downhloaded the right file for your phone from OnePlus?
Click to expand...
Click to collapse
I have tried several files, but still no luck. Factory resetting does the same thing. Boots back into recovery. Would the unbrick method work do you think?
mrandmrshemming said:
I have tried several files, but still no luck. Factory resetting does the same thing. Boots back into recovery. Would the unbrick method work do you think?
Click to expand...
Click to collapse
I would try, but i have the feeling, that you have a hardware failer...
You could try this:
unlock bootloader
install twrp
install firmware 9.0.4
install any custom rom
I would take Dirty Unicorns, bacause file is not so big and works definitly without problems on my phone
https://download.dirtyunicorns.com/.../du_oneplus3-v13.4-20190707-1336-OFFICIAL.zip
perhaps is then the problem solved and you can install OxygenOS 9.0.4 again...
Master_TC said:
I would try, but i have the feeling, that you have a hardware failer...
You could try this:
unlock bootloader
install twrp
install firmware 9.0.4
install any custom rom
I would take Dirty Unicorns, bacause file is not so big and works definitly without problems on my phone
https://download.dirtyunicorns.com/.../du_oneplus3-v13.4-20190707-1336-OFFICIAL.zip
perhaps is then the problem solved and you can install OxygenOS 9.0.4 again...
Click to expand...
Click to collapse
Can you unlock bootloader from being stuck in recovery mode?
mrandmrshemming said:
Can you unlock bootloader from being stuck in recovery mode?
Click to expand...
Click to collapse
Install the adb - platform tools v28.0.1 on your PC.
Turn the phone off. Then boot it into fastboot mode by holding volume up + power. The phone will display "fastboot" text indicating that it has successfully entered fastboot mode.
Plug the phone into your PC, then open a command prompt window on the desktop (Shift + Right Click -> Open Command Window here) and type:
fastboot oem unlock
then
fastboot reboot
After that reboot into fastboot again and install TWRP...
Guide:
https://forums.oneplus.com/threads/...wrp-root-nandroid-efs-backup-and-more.448149/
Master_TC said:
Install the adb - platform tools v28.0.1 on your PC.
Turn the phone off. Then boot it into fastboot mode by holding volume up + power. The phone will display "fastboot" text indicating that it has successfully entered fastboot mode.
Plug the phone into your PC, then open a command prompt window on the desktop (Shift + Right Click -> Open Command Window here) and type:
fastboot oem unlock
then
fastboot reboot
After that reboot into fastboot again and install TWRP...
Guide:
https://forums.oneplus.com/threads/...wrp-root-nandroid-efs-backup-and-more.448149/
Click to expand...
Click to collapse
I used the hard brick method which successfully completed but it still boots into recovery. I am now thinking that there is an issue with the volume buttons, so therefore I think I need to disassemble the phone and replace the volume buttons.
mrandmrshemming said:
I used the hard brick method which successfully completed but it still boots into recovery. I am now thinking that there is an issue with the volume buttons, so therefore I think I need to disassemble the phone and replace the volume buttons.
Click to expand...
Click to collapse
Why the volume buttons?
Master_TC said:
Why the volume buttons?
Click to expand...
Click to collapse
It constantly reboots into recovery when turned on. Also, when I got into fastboot it continuously scrolled through the options, reboot bootloader....reboot recovery.... start....etc.
mrandmrshemming said:
It constantly reboots into recovery when turned on. Also, when I got into fastboot it continuously scrolled through the options, reboot bootloader....reboot recovery.... start....etc.
Click to expand...
Click to collapse
Oh Ok the volume buttons... Perhaps you need only to clean them.
Googd luck!
mrandmrshemming said:
What is the oos ROM? Also, can I do that via ADB and sideloading it?
Click to expand...
Click to collapse
Oxygen os . Yah you can
Hello, I have some problems on my Mi A2. I rooted the device in August to enable Camera2API (getting stuck in the security update of the same month.). I installed Magisk and everything was going well. Then came a notification regarding the October update. I clicked to upgrade and by the time it was done, the device was working perfectly until the moment it completely discharged its battery. After that it gets into Bootloop on the Android One boot screen. I would like some suggestions for the solution. Thanks.
until the moment it completely discharged its battery
Click to expand...
Click to collapse
same here! I am not rooted and not unlocked.
Exactly the same here...
fly23 said:
same here! I am not rooted and not unlocked.
Click to expand...
Click to collapse
This was 2 days ago. It worked again after about 150 reboots. Or i pushed a special button combination, I don't know.
In betweet I did one "fastboot reboot".
Now I have the same problem again after empty battery. Bootloop.
This is the worst android phone I ever bought after HTC desire, Galaxy Nexus, Nexus 5, 5X. I will never again buy a budget phone or a xiaomi.
I did a factory reset this morning, and itgot stuck on an Android One screen. I am trying to figure out how to reflash it, but it doesn't seem to like the firmware. Not sure if I have to unlock the bootloader? I am not family with any of this stuff. I was supposed to ship the phone to the buyer today, but I guess I may have to kill the deal and refund them. This may be the last Xiaomi I buy.
https://imgur.com/a/5J51w3D
for me helped that thing
1. boot manually into fastboot mode
2. Change slot, reboot to fastboot
3. Change slot again.
4. After that reboot to system completed succesfully
but that sh*t came back again in a week for me
[email protected] said:
for me helped that thing
1. boot manually into fastboot mode
2. Change slot, reboot to fastboot
3. Change slot again.
4. After that reboot to system completed succesfully
but that sh*t came back again in a week for me
Click to expand...
Click to collapse
How do you change slot? The fastboot screen does not have any options/menu for me. It is just a picture.
clocks11 said:
How do you change slot? The fastboot screen does not have any options/menu for me. It is just a picture.
Click to expand...
Click to collapse
Yeah, I wonder that as well.
The arrow down + power button combination just keeps the phone frozen on a fancy picture with "fast boot" written at the bottom of the screen.
clocks11 said:
How do you change slot? The fastboot screen does not have any options/menu for me. It is just a picture.
Click to expand...
Click to collapse
You need PC for that
Boot into fastboot (vol - + PWR)
Then use fasboot from terminal
First look which slot is active by typing
fastboot getvar current-slot
Then we can change active slot using this commands
fastboot --set-active=a
or:
fastboot --set-active=b
Unfortunately, to be able to switch booting slot one needs fully unlocked phone (bootloader and critical partitions in our case).
Being fully unlocked, one can boot device in fastboot into TWRP, and from there:
- change slots
- wipe Dalvik/Art cache (and other Cache partition if present) - which in turn very often helps to recover from OTA-generated bootloop
Aerobatic said:
Unfortunately, to be able to switch booting slot one needs fully unlocked phone (bootloader and critical partitions in our case).
Being fully unlocked, one can boot device in fastboot into TWRP, and from there:
- change slots
- wipe Dalvik/Art cache (and other Cache partition if present) - which in turn very often helps to recover from OTA-generated bootloop
Click to expand...
Click to collapse
I think this is why my phone is completely bricked. It does not have an unlocked bootloader, so it seems I can't flash firmware on it. I will likely never buy Xiaomi again after this. I just was doing a factory reset since I had sold the phone.
[email protected] said:
for me helped that thing
1. boot manually into fastboot mode
2. Change slot, reboot to fastboot
3. Change slot again.
4. After that reboot to system completed succesfully
but that sh*t came back again in a week for me
Click to expand...
Click to collapse
this method works perfectly to me :good: ! my Mi A2 update to Oct 5 2019 patch okk. but i want to restart my phone. after restart, my phone is bootloop then luckily i found this usefull guide. thanks you very much again! Android One on Xiaomi is really sh*t.
ngohoainam said:
this method works perfectly to me :good: ! my Mi A2 update to Oct 5 2019 patch okk. but i want to restart my phone. after restart, my phone is bootloop then luckily i found this usefull guide. thanks you very much again! Android One on Xiaomi is really sh*t.
Click to expand...
Click to collapse
I'm still not clear how to change slot. Does the the phone have to be unlocked for this? Is special PC software needed? My A2 has been a brick for almost a week now.
clocks11 said:
I'm still not clear how to change slot. Does the the phone have to be unlocked for this? Is special PC software needed? My A2 has been a brick for almost a week now.
Click to expand...
Click to collapse
yes. you need your phone to be unlocked Bootloader and Critical Partition to use fastboot. more info here ( read Prerequisites carefully )
after you unlocked your phone and unlock Critical Partition. turn off you phone and after that press both Power and volumn down button at the same time. then your phone is booted to fastboot mode.
in fastboot mode. type fastboot getvar current-slot . after that the system will return your current slot. example: b
then you type fastboot --set-active=a
then you disconnect your phone to PC and then reboot again.
then you turn off your phone again and turn your phone to fastboot mode. then you type this command again: fastboot --set-active=b
then you disconnect your phone and boot your phone normally. after that your phone is fixed from bootloop.
ps: remember to download the driver and minimal fastboot so that your pc recognize your phone is connected to your pc
ngohoainam said:
yes. you need your phone to be unlocked Bootloader and Critical Partition to use fastboot. more info here ( read Prerequisites carefully )
after you unlocked your phone and unlock Critical Partition. turn off you phone and after that press both Power and volumn down button at the same time. then your phone is booted to fastboot mode.
in fastboot mode. type fastboot getvar current-slot . after that the system will return your current slot. example: b
then you type fastboot --set-active=a
then you disconnect your phone to PC and then reboot again.
then you turn off your phone again and turn your phone to fastboot mode. then you type this command again: fastboot --set-active=b
then you disconnect your phone and boot your phone normally. after that your phone is fixed from bootloop.
ps: remember to download the driver and minimal fastboot so that your pc recognize your phone is connected to your pc
Click to expand...
Click to collapse
Unfortunately, I think I am screwed, as the phone was not unlocked prior to my boot issue. So I am not sure there is anything I can do. I can get to fastboot though.
A couple days ago my Redmi Note 9 (merlin) 4/128 GB NFC automically installed the Update from V12.0.3.0.QJOEUXM to V12.0.4.0.QJOEUXM over night. I had rooted and installed a TWRP on it. As I had noticed that it was not rooted anymore I tried to reflash the TWRP over Fastboot because it was overwritten by MIUI. When I tried to boot the twrp.img the phone did so and the screen was on but black. After 4 or 5 tries it hanged up in a bootloop and I cannot access Fastboot Mode or something else anylonger.
Is there something left I can try?
Already tried power and minus option.when you connect to a desktop what does it say ?
Dokrak99 said:
Already tried power and minus option.when you connect to a desktop what does it say ?
Click to expand...
Click to collapse
It goes on and Windows makes the sound for a new device connected, and then it goes off again, and Windows makes the sound for disconnecting a device. This repeats for around 4 or 5 minutes then it goes finally off.
That's bad.
Hold the power +/- longer then 15 seconds try both.
Second
Charge for about 10 minutes and try the same again.
Last drain it when down keep pushing the power button to flat it.hook it up on desktop and install miflashtools.or try power +/- again
Dokrak99 said:
Hold the power +/- longer then 15 seconds try both.
Click to expand...
Click to collapse
Same as:
LordRedstone05 said:
It goes on and Windows makes the sound for a new device connected, and then it goes off again, and Windows makes the sound for disconnecting a device. This repeats for around 4 or 5 minutes then it goes finally off.
Click to expand...
Click to collapse
Dokrak99 said:
Charge for about 10 minutes and try the same again.
Click to expand...
Click to collapse
When I try to charge it it goes in the bootloop again until I disconnect it and the battery runs out.
Dokrak99 said:
Last drain it when down keep pushing the power button to flat it.
Click to expand...
Click to collapse
It goes on, shows this battery icon, that it's empty and goes off. This repeats until I release the button.
Dokrak99 said:
hook it up on desktop and install miflashtools.or try power +/- again
Click to expand...
Click to collapse
The miflashtool does nothing when I click on Flash with the images and scripts loaded. Power +/- does the same as before.
Sorry I thought flash tools had a option in top for selecting boot options.There is a mi tool around where can select the boot options.i need to search on my desktop what it was.we need to trigger it in fastboot/recovery mode some how.most likely it was xiaomi tools V2 but I really need to check it.tools V2 got a bricked option do.but since it restarts everytime it's pretty long shot
Dokrak99 said:
Sorry I thought flash tools had a option in top for selecting boot options.There is a mi tool around where can select the boot options.i need to search on my desktop what it was.we need to trigger it in fastboot/recovery mode some how.most likely it was xiaomi tools V2 but I really need to check it.tools V2 got a bricked option do.but since it restarts everytime it's pretty long shot
Click to expand...
Click to collapse
Thanks in advance
What should I do in this tool? The tool doesn't recognize my phone. It brings nothing since I cannot access Fastboot.
Well basically there is only one real option left . contact mi service center because mi don't support or they closed there download,edl support on there phones to prevent rom swapping .there is a edl cable with mtk support around but that's a long shot.because I never had a messed up phone like this.at least not one with mtk.without recognise you're desktop I don't see a fix in this to get in fastboot or flash it.
Download platform tools drop it on c:/ so c:/platform tools .install abd drivers package if you didn't have it.go in platform tools the top line and tick Cmd hit enter.try command : fastboot devices .try a few times if a number pops up you can try .fastboot reboot fastboot
LordRedstone05 said:
A couple days ago my Redmi Note 9 (merlin) 4/128 GB NFC automically installed the Update from V12.0.3.0.QJOEUXM to V12.0.4.0.QJOEUXM over night. I had rooted and installed a TWRP on it. As I had noticed that it was not rooted anymore I tried to reflash the TWRP over Fastboot because it was overwritten by MIUI. When I tried to boot the twrp.img the phone did so and the screen was on but black. After 4 or 5 tries it hanged up in a bootloop and I cannot access Fastboot Mode or something else anylonger.
Is there something left I can try?
Click to expand...
Click to collapse
TWRP bricked my redmi Note 9 too, but i had ADB Connection in the black Screen so i rebooted to Fastboot over ADB and reflashed the Stock rom
LordRedstone05 said:
A couple days ago my Redmi Note 9 (merlin) 4/128 GB NFC automically installed the Update from V12.0.3.0.QJOEUXM to V12.0.4.0.QJOEUXM over night. I had rooted and installed a TWRP on it. As I had noticed that it was not rooted anymore I tried to reflash the TWRP over Fastboot because it was overwritten by MIUI. When I tried to boot the twrp.img the phone did so and the screen was on but black. After 4 or 5 tries it hanged up in a bootloop and I cannot access Fastboot Mode or something else anylonger.
Is there something left I can try?
Click to expand...
Click to collapse
Did you find solution on this? Please answer bro i need your help
Jayson Galang said:
Did you find solution on this? Please answer bro i need your help
Click to expand...
Click to collapse
Unfortunately i haven't found a solution. I had to send it to a service center 2 Days ago. Sorry, that i couldn't help.
the right driver is mtk this is not adb nothing happens the this you could fixs is
go to the nearest techniciann beacause they need special tools to fix properly
Is your phone still bricked, If yes, I can provide link for the factory firmware recently released for Merlin, You could give flashing that in SP Flash a try, does not need auth account.
If your device keep booting in recovery (or blackscreen), you need to erase misc partition.
Here, is the guide for erasing MISC partition: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
Good luck
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
Communos said:
Is your phone still bricked, If yes, I can provide link for the factory firmware recently leaked for Merlin, You could give flashing that in SP Flash a try, does not need auth account.
Click to expand...
Click to collapse
yow is that legit? Had my redmi note 9 bricked for a week now.
CruisaderX said:
yow is that legit? Had my redmi note 9 bricked for a week now.
Click to expand...
Click to collapse
If you got bootloop after flashed magisk, you need to flash stock rom boot.img.
If you got bootloop after flashed TWRP, you need to flash stock rom recovery.img.
If you got bootloop (or black screen) after flashed misc partition, you need to erase misc partition.
If it keeps restarting, you've made any wrong modification. You need to follow your steps back and try to unmake your modification.
If you can't enter in fastboot mode or recovery mode, you need to flash stock rom using sp flash tool.
If you are using V12.0.4.0 or lower, you can flash without EDL and authentication.
If you are using V12.0.5.0 or higher, you need EDL and authentication for flashing.
If you are using V12.0.5.0 or higher, TWRP will not work.
If you want to use sp flash tool, you need to flash the stock rom preloader using V12.0.4.0 (or lower). (It will works perfectly with lower preloader binary version).
With an older preloader version, your phone will can receive DA files and accept flashing with NO auth.
Everything you need to do is plug your phone in usb (without press any key, if you press any key it will enter in EDL mode and requests authenticaion).
Here, are PRELOADER binaries for flashing: https://forum.xda-developers.com/t/...omi-redmi-10x-4g-xiaomi-redmi-note-9.4221081/
Here, are DA files for flashing using flash tool: https://forum.xda-developers.com/t/...omi-redmi-10x-4g-xiaomi-redmi-note-9.4209767/
Here, you can find boot images for original stock and magisk patched: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
If you want to keep TWRP working on V12.0.5.0 or higher, you need to flash the stock rom lk partition using V12.0.4.0 (or lower). (It will works perfectly with lower lk partition version).
Here, are LK images for flashing: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218925/
If you want to disable TWRP, you need to flash stock rom recovery partition.
Here, are RECOVERY images for flashing: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
If your device keep booting in recovery (or blackscreen), you need to erase misc partition.
Here, is the guide for erasing MISC partition: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
If you want to know what is working for MERLIN, take a look: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204873/
Good luck
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
VD171 said:
If you got bootloop after flashed magisk, you need to flash stock rom boot.img.
If you got bootloop after flashed TWRP, you need to flash stock rom recovery.img.
If you got bootloop (or black screen) after flashed misc partition, you need to erase misc partition.
If you are using V12.0.5.0 or higher, TWRP will not work.
Here, you can find boot images for original stock and magisk patched: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
If you want to keep TWRP working on V12.0.5.0 or higher, you need to flash the stock rom lk partition using V12.0.4.0 (or lower). (It will works perfectly with lower lk partition version).
Here, are LK images for flashing: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218925/
If you want to disable TWRP, you need to flash stock rom recovery partition.
Here, are RECOVERY images for flashing: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
If your device keep booting in recovery (or blackscreen), you need to erase misc partition.
Here, is the guide for erasing MISC partition: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
If you want to know what is working for MERLIN, take a look: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204873/
Good luck
[/QUOTE
Click to expand...
Click to collapse
I tried actually before after failed attempt of flashing twrp. First, I got my redmi note 9 bricked after following one of the guides posted here (rooting), I will call this state 1 brick. In state 1 brick you can still access fastboot mode normally. Then i tried to flash twrp hoping to just flash a rom to fix it leading to state 2 brick. In state 2 brick, it seems like it is stucked on recovery (btw the recovery is only displaying black screen) and is classifying fastboot as the bootloader, meaning you can boot into fastboot using adb command reboot bootloader. Then I followed one of the guides here again and then it managed to lead my device to state 3 brick. In state 3 brick it continuously boot looping only displaying the boot image for a second then repeat. Normally it can be fixed by flashing a stock rom using sp flash tool but not with xiaomi devices. Now I am stucked with a hard bricked note 9 with no way of fixing.
CruisaderX said:
i tried before actually after failed attempt of flashing twrp. First, I got my redmi note 9 bricked after following one of the guides posted here (rooting, I will call this state 1 brick. In state 1 brick you can still access fastboot mode. Then i tried to flash twrp hoping to just flash a rom leading to state 2 brick. In state 2 brick, it seems like it is stucked on recovery (btw the recovery is only displaying black screen) and is classifying fastboot as the bootloader, meaning you can boot into fastboot using adb command reboot boot loader. Then I followed one of the guides here again and then it managed to lead my device to state 3 brick. In state 3 brick it continuously boot looping only displaying the boot image for a second then repeat. Normally it can be fixed by flashing a stock rom using sp flash tool but not with xiaomi device. Now I am stucked with a hard bricked note 9 with no way of fixing.
Click to expand...
Click to collapse
You need to read every line and every word careful and follow only specific guide for your specific problem.
If you try to do anything you see, obviously you will cause more damages to your device.
Please, read my post again: https://forum.xda-developers.com/t/redmi-note-9-merlin-4-128-nfc-hard-brick.4201717/post-84379823
If you can't enter in fastboot mode or recovery mode, you need to flash stock rom using sp flash tool.
If you are using V12.0.4.0 or lower, you can flash without EDL and authentication.
If you are using V12.0.5.0 or higher, you need EDL and authentication for flashing.
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
I hope this is the right place to post this, I'm offering $250 to the person that can assist me in getting my phone to boot again so I can extract the data I need from it. Here are the quick facts:
-Verizon Pixel 5 (locked bootloader, fastboot commands don't work)
-Woke up and phone was in Android Recovery mode (was working fine when I put it on the charger)
-adb sideload OTA hasn't worked so far (tried most recent OTA package and it loaded successfully with status 0 but still leaves me in a bootloop, older Verizon specific OTAs will not load due to being outdated)
-Even tried sideloading Android 12 dev preview, no success
-Safe mode does not work
-Verified that my backups do not contain the data I am trying to recover
I've tried pretty much everything I could find by searching here and other forums/resources and I'm pretty much at the point where I'm thinking this data may be gone forever but I'm hoping someone can prove me wrong. Willing to do a remote session with the phone connected if needed.
bsmack said:
I hope this is the right place to post this, I'm offering $250 to the person that can assist me in getting my phone to boot again so I can extract the data I need from it. Here are the quick facts:
-Verizon Pixel 5 (locked bootloader, fastboot commands don't work)
-Woke up and phone was in Android Recovery mode (was working fine when I put it on the charger)
-adb sideload OTA hasn't worked so far (tried most recent OTA package and it loaded successfully with status 0 but still leaves me in a bootloop, older Verizon specific OTAs will not load due to being outdated)
-Even tried sideloading Android 12 dev preview, no success
-Safe mode does not work
-Verified that my backups do not contain the data I am trying to recover
I've tried pretty much everything I could find by searching here and other forums/resources and I'm pretty much at the point where I'm thinking this data may be gone forever but I'm hoping someone can prove me wrong. Willing to do a remote session with the phone connected if needed.
Click to expand...
Click to collapse
Try the latest factory image for Verizon
rbouza1 said:
Try the latest factory image for Verizon
Click to expand...
Click to collapse
I appreciate the reply, unfortunately I can't flash factory images via fastboot due to the bootloader being locked. I tried both the latest factory image from April '21 and the latest Verizon labeled factory image from Feb '21.
Bounty is still out FYI, I plan on tossing the phone in a drawer for a few months to see if anyone comes up with anything. I'll be taking it out to continue trying out adb sideload of the monthly OTAs that get posted, definitely anxiously awaiting the May '21 update!
Not sure if this information helps, but I just tried sideloading the May '21 OTA and I'm still stuck in the same spot. After the sideload finished successfully (code 0, no errors) it tried to boot but I got the Android Recovery screen again. It still references RQ2A.210405.005 (May '21 OTA is RQ2A.210505.003).
Try changing the active boot slot with fastboot?
How to Change the Current Active Partition Slot? - KrispiTech
Modern Android smartphones ship with partition slots A and B and we can use a Fastboot command to manually change from one active slot to the other.
krispitech.com
bsmack said:
Not sure if this information helps, but I just tried sideloading the May '21 OTA and I'm still stuck in the same spot. After the sideload finished successfully (code 0, no errors) it tried to boot but I got the Android Recovery screen again. It still references RQ2A.210405.005 (May '21 OTA is RQ2A.210505.003).
Click to expand...
Click to collapse
Yes, that makes sense on a/b-partitioned devices. The update is always applied to the inactive slot.
So you would have to change the current slot as suggested:
l7777 said:
Try changing the active boot slot with fastboot?
How to Change the Current Active Partition Slot? - KrispiTech
Modern Android smartphones ship with partition slots A and B and we can use a Fastboot command to manually change from one active slot to the other.
krispitech.com
Click to expand...
Click to collapse
However, I don't think you can do that without unlocking your bootloader.
If you could boot into system, however, we might do it without the bootloader. But here comes the next problem: You cannot boot into system.
bsmack said:
-Woke up and phone was in Android Recovery mode (was working fine when I put it on the charger)
Click to expand...
Click to collapse
What do you even get? A screen saying "Your data may be corrupted" (known as "rescue party")?
Or your normal recovery screen?
If it actually is rescue party, hit the "try again" button – it would reboot, fail and go back to rescue party.
Do that 7-10 times without interruption (e.g. turning of the device). Your device should automatically change the slot to the 'other' slot, and then boot just fine.
bsmack said:
I hope this is the right place to post this, I'm offering $250 to the person that can assist me in getting my phone to boot again so I can extract the data I need from it.
Click to expand...
Click to collapse
Since you offer $250, you may want to invest in "chip off". Your phone will be disassembled and your chip (which holds all of your data) will be removed from the phone.
Using special hard- and software, you should be able to recovery your data.
Only thing I don't know: How do these tools handle encryption? I'm pretty sure they can offer something to insert your password etc., but you may want to research a bit further before buying those tools or paying someone to do it for you.
User699 said:
Since you offer $250, you may want to invest in "chip off". Your phone will be disassembled and your chip (which holds all of your data) will be removed from the phone.
Using special hard- and software, you should be able to recovery your data.
Only thing I don't know: How do these tools handle encryption? I'm pretty sure they can offer something to insert your password etc., but you may want to research a bit further before buying those tools or paying someone to do it for you.
Click to expand...
Click to collapse
I suspect this will be much more than $250 if they can get past the encryption. It's not just a matter of the password it's knowing how to combine the password with the devices unique hardware encryption key to ultimately decrypt the file system.
l7777 said:
Try changing the active boot slot with fastboot?
How to Change the Current Active Partition Slot? - KrispiTech
Modern Android smartphones ship with partition slots A and B and we can use a Fastboot command to manually change from one active slot to the other.
krispitech.com
Click to expand...
Click to collapse
I appreciate the response, this is something I hadn't tried before. Unfortunately it seems Verizon blocks this functionality as well.
User699 said:
What do you even get? A screen saying "Your data may be corrupted" (known as "rescue party")?
Or your normal recovery screen?
If it actually is rescue party, hit the "try again" button – it would reboot, fail and go back to rescue party.
Do that 7-10 times without interruption (e.g. turning of the device). Your device should automatically change the slot to the 'other' slot, and then boot just fine.
Click to expand...
Click to collapse
I believe it is rescue party as that is the first screen I see (data corrupt with two options; try again or wipe phone). Currently trying this now to see if I can get it to switch to slot b (fastboot currently indicates that the active slot is slot a).
Another thought, if I flash an OTA (let's say to slot b since slot a is the active one), after a successful flash wouldn't recovery flag slot b as the slot to attempt to boot into next? And on that next boot, is slot b simply failing to boot and reverting to slot a, which is why I'm seeing the "old" android version in rescue party?
*$250 BOUNTY IS STILL ACTIVE!*
Hopefully replying to myself doesn't get too annoying for everyone, just wanted to give an update and hopefully give some insight to lurkers that might be experiencing something similar.
Based on what I'm seeing, slot a contains the corrupted OS and when I do an "adb sideload" successfully it installs to slot b. Immediately after a successful adb sideload, if I don't "reboot now" and instead "reboot to bootloader" it will show at the bottom of the fastboot screen that the active boot slot is b.
After I press "start" from the bootloader menu, the phone booting takes longer than normal, will restart once, takes a long time again, then restarts again and quickly brings me to the "rescue party" screen with RQ2A.210405.005 as the active OTA version. If I go back to the bootloader after this it will show that the active boot slot is now a.
I am truly thankful for all the replies and suggestions so far and I would love nothing more than to send this $250 bounty to a forum member.
bsmack said:
*$250 BOUNTY IS STILL ACTIVE!*
Hopefully replying to myself doesn't get too annoying for everyone, just wanted to give an update and hopefully give some insight to lurkers that might be experiencing something similar.
Based on what I'm seeing, slot a contains the corrupted OS and when I do an "adb sideload" successfully it installs to slot b. Immediately after a successful adb sideload, if I don't "reboot now" and instead "reboot to bootloader" it will show at the bottom of the fastboot screen that the active boot slot is b.
After I press "start" from the bootloader menu, the phone booting takes longer than normal, will restart once, takes a long time again, then restarts again and quickly brings me to the "rescue party" screen with RQ2A.210405.005 as the active OTA version. If I go back to the bootloader after this it will show that the active boot slot is now a.
I am truly thankful for all the replies and suggestions so far and I would love nothing more than to send this $250 bounty to a forum member.
Click to expand...
Click to collapse
Have you tried to flash to both slots using fastboot --slot=all flash
rbouza1 said:
Try the latest factory image for Verizon
Click to expand...
Click to collapse
There is no factory image for Verizon. You can't unlock the bootloader on it
MOD ACTION:
Thread cleaned.
Friends, please be civil to each other and observe Rule 2 always. Be cool!
thatsupnow said:
Have you tried to flash to both slots using fastboot --slot=all flash
Click to expand...
Click to collapse
Thanks for the reply. Unfortunately this won't work because my bootloader is locked, so no fastboot flashing for me
Have you tried the RQ2A.210405.005 OTA?
Does
Code:
fastboot boot <extracted kernel image>
work? Not sure about this with locked bootloader.
l7777 said:
Have you tried the RQ2A.210405.005 OTA?
Does
Code:
fastboot boot <extracted kernel image>
work? Not sure about this with locked bootloader.
Click to expand...
Click to collapse
Unfortunately this did not work. Never buying a Verizon locked Pixel again!
bsmack said:
Unfortunately this did not work. Never buying a Verizon locked Pixel again!
Click to expand...
Click to collapse
How about:
Apply latest OTA
Reboot to bootloader/recovery
Apply latest OTA again
In theory that should update both slots A and B. Though it sounds like it attempts to boot slot B, then falls back to slot A, then to recovery. Which means something is really unhappy but we're pretty limited with the bootloader lock.
Was ADB enabled? Can you get a logcat while it tries to boot?
l7777 said:
How about:
Apply latest OTA
Reboot to bootloader/recovery
Apply latest OTA again
In theory that should update both slots A and B. Though it sounds like it attempts to boot slot B, then falls back to slot A, then to recovery. Which means something is really unhappy but we're pretty limited with the bootloader lock.
Was ADB enabled? Can you get a logcat while it tries to boot?
Click to expand...
Click to collapse
This was a great idea, unfortunately I think there's a failsafe in place for this. When I went back into recovery to apply the latest OTA again, as expected, the recovery mode menu showed the latest OTA which I have not yet successfully booted into (RQ2A.210505.003).
When running adb sideload to flash slot a, the package seems to transfer but instantly stops (I assume there's some flag that slot a has to not be overwritten because a successful boot to slot b hasn't happened yet). An interesting thing to note is that my phone seems to be regularly trying to boot slot b now instead of slot a, when the rescue party screen shows up I now see RQ2A.210505.003 as opposed to RQ2A.210405.005.
Tried this yet?
Google Pixel - Update and Software Repair
It isn't really clear whether it will wipe data or not.
Someone noted that the fastboot in rescue mode is different from the normal fastboot. I don't know if it will behave any differently when told to fastboot flash or other things not typically allowed with a locked bootloader.
l7777 said:
Tried this yet?
Google Pixel - Update and Software Repair
It isn't really clear whether it will wipe data or not.
Someone noted that the fastboot in rescue mode is different from the normal fastboot. I don't know if it will behave any differently when told to fastboot flash or other things not typically allowed with a locked bootloader.
Click to expand...
Click to collapse
Really appreciate you trying to walk me through this. This was something I had tried (neglected to mention in the OP, my bad!) and I do remember it recommended/prompted me to wipe and restore my phone.
Here's the interesting thing; when I select Verizon as my carrier now it says that it's NOT the carrier for my phone's current software. This was not the case before.
It doesn't seem like rescue mode can take fastboot commands, it is listed when I do "adb devices" though. Instead of "sideload" it says "rescue".
EDIT: And I did try some basic stuff like "adb shell" and "adb pull" in rescue mode, I get an instant "connection closed" error.