Related
Are there other ways to flash a recovery with a locked bootloader?
My Problems:
I can't flash my stock recovery through fastboot with a locked bootloader.
I can't boot into my recovery because my current recovery is TWRP 2.5.0.1 and I have a locked bootloader.
I can't unlock my bootloader because I have used an IMEI Hack Tool and set my IMEI to 0 (I guess).
I can't boot into my ROM because I used an IMEI Hack Tool.
I can't Force Upgrade too (Vol Up + Down + Power). It only shows a pink/purple screen.
Solutions:
I can only flash a recovery with an unlocked bootloader.
I can only boot into a recovery with an unlocked bootloader (except for stock).
I can only unlock bootloader if my IMEI has restored.
I can only restore my IMEI if I can boot into my ROM.
I can only boot into my ROM if I have a stock recovery.
I can only Force Upgrade if I have restored my IMEI.
If I could only restore my IMEI through fastboot, that would be great!
So, please help!
You cant restore stock recovery ?
You cant enter to trwp ?
You cant restore IMEI cuz rom bootloop ?
You cant force flash stock firmware cuz fastboot is pink ?
I also "zero" my imei many times to flash stock firmware, but i allways can enter trwp and restore buckup or flash rom in zip
OmenHTX said:
You cant restore stock recovery ?
You cant enter to trwp ?
You cant restore IMEI cuz rom bootloop ?
You cant force flash stock firmware cuz fastboot is pink ?
I also "zero" my imei many times to flash stock firmware, but i allways can enter trwp and restore buckup or flash rom in zip
Click to expand...
Click to collapse
I can force upgrade now since i formatted my sd card. But the force upgrade fails at step 2/2.
.vonpatrick. said:
I can force upgrade now since i formatted my sd card. But the force upgrade fails at step 2/2.
Click to expand...
Click to collapse
If upgrade fail as step 2/2 your IMEI its not "zero" cuz IMEI block upgrading firmware from branded to nonbranded
OmenHTX said:
If upgrade fail as step 2/2 your IMEI its not "zero" cuz IMEI block upgrading firmware from branded to nonbranded
Click to expand...
Click to collapse
If my imei is not zero, then why can't i boot my phone?
And why can't i unlock my bootloader with my unlock code?
.vonpatrick. said:
If my imei is not zero, then why can't i boot my phone?
And why can't i unlock my bootloader with my unlock code?
Click to expand...
Click to collapse
OK, lest start from beggining
1.You must unlock bootloader by code ( first run check Lock / Unlock status ) (fastboot mod)
2. Flash TRWP (fastboot mod)
3. Flash SuperSU or Superuser zip (trwp)
4. Backup IMEI on running rom
5. Hack IMEI on running rom
6. Update phone by forceupdate flash update.app (rom in root of sd card > folder dload > update.app)
7. Run stock rom , lest install, shut down phone
8. Run TRWP to install SuperSU/Superuser zip
8. Restore IMEI (on working rom)
9. Go to TRWP and Wipe dalvik cache
10. Now you have working newest stock rom with root
So :
1. You cant have trwp in lockedbootloader
2. If update fail on 2/2 IMEI is not "zero"
3. Pink LCD on "update mod" = no rom in sd card
Next :
Hold Vol Down + Vol Up + Power to forceupdate firmware mod
Hold Vol Up + Power to run TRWP or stock recovery ( hold about 5s)
Hold Vol Down + Power for fastboot mod (5s-10s)
If you now have locked bootloader , with stock recovery, and force update fail, you cant unlock bootloader and flash trwp > Last hope is in "oryginal" rom, your IMEI will not block it.
OmenHTX said:
OK, lest start from beggining
1.You must unlock bootloader by code ( first run check Lock / Unlock status ) (fastboot mod)
2. Flash TRWP (fastboot mod)
3. Flash SuperSU or Superuser zip (trwp)
4. Backup IMEI on running rom
5. Hack IMEI on running rom
6. Update phone by forceupdate flash update.app (rom in root of sd card > folder dload > update.app)
7. Run stock rom , lest install, shut down phone
8. Run TRWP to install SuperSU/Superuser zip
8. Restore IMEI (on working rom)
9. Go to TRWP and Wipe dalvik cache
10. Now you have working newest stock rom with root
So :
1. You cant have trwp in lockedbootloader
2. If update fail on 2/2 IMEI is not "zero"
3. Pink LCD on "update mod" = no rom in sd card
Next :
Hold Vol Down + Vol Up + Power to forceupdate firmware mod
Hold Vol Up + Power to run TRWP or stock recovery ( hold about 5s)
Hold Vol Down + Power for fastboot mod (5s-10s)
If you now have locked bootloader , with stock recovery, and force update fail, you cant unlock bootloader and flash trwp > Last hope is in "oryginal" rom, your IMEI will not block it.
Click to expand...
Click to collapse
Wait, let me put this in summary:
1.
- I have a locked bootloader.
- I can't unlock the bootloader because it says "recovery image verify failed".
- It can only mean one thing: my IMEI must have changed.
2.
- I have a TWRP recovery.
- At first, my original recovery was the stock when I have a locked bootloader.
- Then I flashed the TWRP recovery even if I have a locked bootloader and didn't warned me. (Shoudn't it be accepted to be flashed since I have a locked bootloader).
- In my experience, if I have a stock recovery when I'll hack my IMEI, it will format my cache and data and let me boot into my phone.
- If I have a TWRP recovery when I'll hack my IMEI, it will only redirect me to the TWRP menu.
3.
- I can access Force Upgrade.
- But it doesn't show any text. (For example: it doesn't show if it is unpacking or installing, only a bar.)
- When I access Force Upgrade, the loading stops at 1/4 of the bar. (So I'm not really sure if it failed at step 2/2.)
So my questions are:
1. Why can't I unlock my bootloader with my original IMEI's unlock code if my IMEI is not "zero"?
2. Why is it when I Force Upgrade, it doesn't show any text?
3. Why did fastboot accepted the TWRP recovery being flashed when my bootloader was locked?
And, what do you mean by "original"? Do you mean the B182 firmware upgrade, not the B175?
After hacking IMEI you cant have stock recovery, cuz you need root for shell script. So its not making "auto wipe" to change OEM info.
TRWP should not be installed on lockbootloader, but i dont make it ...
So , do you have working trwp or not ?
Oryginal firmware ... version when you get with phone, like my Y300-0100 branded T-Mobile PL B167
OmenHTX said:
After hacking IMEI you cant have stock recovery, cuz you need root for shell script. So its not making "auto wipe" to change OEM info.
TRWP should not be installed on lockbootloader, but i dont make it ...
So , do you have working trwp or not ?
Oryginal firmware ... version when you get with phone, like my Y300-0100 branded T-Mobile PL B167
Click to expand...
Click to collapse
I am sure i have twrp.
If i have a stock recovery, i would be able to boot into recovery.
Based in my experience:
1. To hack the imei, you must first root your phone.
2.a. Next, the phone will reboot, but it won't boot into system.
2.b. Fastboot, force upgrade, and recovery is still accessible.
3.a. If you have a twrp recovery when you hacked the imei and rebooted, it will redirect you to the twrp menu.
3.b. If you tried to restore from twrp recovery, it still won't reboot into system.
3.c. If you have a stock recovery, it will directly boot into stock recovery and format your cache and data and reboot to system (still leaves your imei to zero)
4. If you go to force upgrade, you can flash any official roms (leaves your imei to zero)
5. After you have flashed a rom or was redirected to stock recovery, your phone will reboot.
6.a. Then root your phone and restore imei then your phone will reboot.
6.b. If you have a stock recovery, it will wipe your cache and data.
6.c. If you have a twrp recovery, it will redirect you to the twrp menu (you can manually reboot into system)
Am i right?
And where can i get the original rom for my b182? There's no local huawei store here.
.vonpatrick. said:
I am sure i have twrp.
If i have a stock recovery, i would be able to boot into recovery.
Click to expand...
Click to collapse
So why you dont run TRWP and flash any rom in zip ?
OmenHTX said:
So why you dont run TRWP and flash any rom in zip ?
Click to expand...
Click to collapse
Twrp is not accessible if you have a locked bootloader.
bricked
I have a big problem. My Ascend y300 started to work strange yesterday, my PC didnt see the internal sd nor the external SD correctly. Today I restarted it and now I get blue screen when I start it. I had TWRP installed, but when I try to access it, it gives blue screen aswell. Any solutions?
gery0518 said:
I have a big problem. My Ascend y300 started to work strange yesterday, my PC didnt see the internal sd nor the external SD correctly. Today I restarted it and now I get blue screen when I start it. I had TWRP installed, but when I try to access it, it gives blue screen aswell. Any solutions?
Click to expand...
Click to collapse
Try this through fastboot:
fastboot erase recovery
fastboot flash recovery <path to recovery.img>
.vonpatrick. said:
Try this through fastboot:
fastboot erase recovery
fastboot flash recovery <path to recovery.img>
Click to expand...
Click to collapse
My problem is a little bit more complex unfortunately. I tried what you said. When I push the buttons to enter fastboot, my phone dont freez at splashscreen and I get bluescreen. When I connect it to my PC my PC recognizes it though, BUT ADB cant see it. I reinstalled the drivers any times, without success.
gery0518 said:
My problem is a little bit more complex unfortunately. I tried what you said. When I push the buttons to enter fastboot, my phone dont freez at splashscreen and I get bluescreen. When I connect it to my PC my PC recognizes it though, BUT ADB cant see it. I reinstalled the drivers any times, without success.
Click to expand...
Click to collapse
What did you do anyway why it got the blue screen?
.vonpatrick. said:
What did you do anyway why it got the blue screen?
Click to expand...
Click to collapse
That is the most strange part of the story. I totally did nothing. I opened bootloader, installed twrp, rooted it, installed init.d support, installed a ramscript. The phone worked totally fine until yesterday. I did a restart yesterday and bumm, bluescreen. And I did nothing before this happened. Srsly, no problems detected, it came from nothing...
gery0518 said:
That is the most strange part of the story. I totally did nothing. I opened bootloader, installed twrp, rooted it, installed init.d support, installed a ramscript. The phone worked totally fine until yesterday. I did a restart yesterday and bumm, bluescreen. And I did nothing before this happened. Srsly, no problems detected, it came from nothing...
Click to expand...
Click to collapse
Can't you really boot into fastboot (Power + up)?
Hold it for like 10 seconds.
If it still shows blue screen, try connecting it to pc, maybe it'll read it.
Then erase recovery and flash twrp.
Wipe everything and restore a backup you made.
.vonpatrick. said:
Can't you really boot into fastboot (Power + up)?
Hold it for like 10 seconds.
If it still shows blue screen, try connecting it to pc, maybe it'll read it.
Then erase recovery and flash twrp.
Wipe everything and restore a backup you made.
Click to expand...
Click to collapse
Well, my problem is, that despite of the blue screen, fastboot seems to work. My pc sees my device, BUT ADB refuses to see it, and I dont know why. I will try it from win xp under virtualbox now.
hi Gery
How do you manage to get the phone into fastboot mode?
my y300 also enters blue screen everytime now. I try to press voldown + power for like 10 seconds, yet the fastboot command is not working.
gery0518 said:
Well, my problem is, that despite of the blue screen, fastboot seems to work. My pc sees my device, BUT ADB refuses to see it, and I dont know why. I will try it from win xp under virtualbox now.
Click to expand...
Click to collapse
Well, that's perfect! If the PC can read the device from fastboot, you can erase the recovery and flash the twrp and restore from backup. But if it still goes blue, flash the system, data, cache, boot, recovery from your twrp backup.
Hi
I have a UHANS A101.
The official rom is quite old, and after read this post, I try to flash with AospExtended my UHANS (it's my first time).
I unlock the bootloader.
With volume + and power I access to the boot menu
I install TWRP in the recovery part
I boot t TWRP
Backup the current system
Wipe
Flash with Aosp and gapps.
But when I reboot, my phone reboot on TWRP ...
Volume + and power won't work anymore ...
On TWRP I click on reboot to system, but it's reboot to TWRP.
I try to restore the backup, but it don't work, maybe I fail when I did it ...
The only way I found to boot on the system is
Boot on TWRP
Click on reboot to bootloader
With my computer use the command : "fastboot continue"
And everthing work wells on my new ROM
But when I reboot, TWRP show up again ...
The trick with fastboot continue still work, but it's quite anoying ...
On this site, I found many other post about this issue, but the aswser seem to be specific for the phone model, or I didn't understand the answser.
Do you know what I'm missing ?
Thanks a lot for your help
Sababo
OK here is my problem I have a rooted Huawei y7 Prime 2018 (LDN-L21).
I made a backup in TWRP 3.2.1.0 and when i rebooted it brought me into a TWRP recovery Bootloop.
I cant go into erecovery or fastboot mode.
And my computer doesnt even reconigse the phone so cant even to adb commands.
I try to put my backup back and it doesnt seem to see the files.
I downloaded a the right stock rom and certain .img files and tried to flash them and get a error unable to mount /system /data /cache and so on so on.
So this is my siituation is::
Stuck in twrp bootloop.
Cant ercovery or fastboot.
Computer wont reconize the phone no more.(so no adb commands).
Cant flash anything due to the mounting error in twrp.
Please help me i I think my os is fine I think.
Im willing to try anything at this point.
PLEASE HELP ME.
Moonlighter
Similar question, hope to get more help .
You can not go into TWRP also?! Or you can go into TWRP and can not reboot to system/erecovery/bootload ?
Problem seems to be /misc partition. If you somehow wipe it (in twrp terminal) or flash recovery without /misc in fstub, MAYBE it would go out of recoveryloop.
Do you have unlocked bootloader with notification screen on boot like "bootloader is unlocked and phone is not trusted.... press Power button to continue..." ? If not, how you bypass it? If yes, you can hold Vol+ for 3 sec to go to eRecovery. Any change to download stock rom to external SDcard to dload folder and to hold Vol- and power on phone?
yes my bootloader is properly unlocked and no still get the loop with stockrom and try do anything in twrp have problems with mounting errors
m00nlight3r said:
yes my bootloader is properly unlocked and no still get the loop with stockrom and try do anything in twrp have problems with mounting errors
Click to expand...
Click to collapse
Where do you find or made twrp for LDN-L21? must be error in fstub or wrong busybox/toybox version.
Did you fastboot flash recovery twrp.img or fastboot flash recovery_ramdisk twrp.img ?!
Hello
I 'm using Lenovo Tab 2 a7-10f
I tried to flash TWRP recovery throught fastboot.
But i didnt succeed before, so this time, i tried to enter command to open TWRP without need to install it.
___________
I entered fastboot mode via command
adb reboot bootloader
and yes, i did unlocked bootloader
___
then i used this command to put recovery in my tablet just to open that recovery
fastboot -c "lge.kcal=0|0|0|x" boot c:\twrp.img
______
i found this solution on this site
https://android.stackexchange.com/questions/86936/how-to-flash-root-zip-in-fastboot/102597
_______
And now, it is in bootloop, until i click both volume up and down , then it enters TWRP
_______
Tried to go in TWRP , Reboot > Power Off
And it shows logo and dont proccedd more, just stuck there and spining
Until i press both volume up and down, so it opens me TWRP recovery
________
Also tried to go into Reboot > System
But still same issue, not booting up at all
___
If i click Reboot > Recovery
Then it boots me back in TWRP
______
I tried already SPFlash tool before, but it doesnt detect my tablet, even if i have all drivers, and google drivers, and USB debbuging, i'm using this tablet for android app development, so it have all drivers.
_______
I managed to get my data from tablet.
I dont know what to do next.
Should i make some command from computer to boot system, using ADB, i know to use ADB, just i stucked in this weird bootloop.
_____
I'm thinking that i should flash stock ROM from TWRP while it is still alive.
Should i do that, i dont want to lose my data, i have many programs.
I dont care if i lose TWRP recovery, i dont need it after this experience right now???
What should i do
If you flash stock can you resume control and appreciate with repatching of recovery
([emoji813]9/[emoji725]/9[emoji813])
PoochyX said:
If you flash stock can you resume control and appreciate with repatching of recovery
([emoji813]9/[emoji725]/9[emoji813])
Click to expand...
Click to collapse
O, oh man, i just got shocked !!! By all this.
I understood that my problem is in boot,
because this command
fastboot -c "lge.kcal=0|0|0|x" boot c:\twrp.img
tells android that when i press power button, to boot into whatewer it is pointed to.
So this command tells android to boot recovery instead of normal system.
So i just reverted it in bootloader (fastboot) mode, by pushing command
fastboot flash boot c:\boot.img
So it booted up again ) , and also important, without losing any precious data. ))
______
It is true when people say that if everything fails in android, there is always a bootloader that you cant destroy.
And also here are commands for other partitions, in this way you can flash whole system without root or anything, for anybody who face this problem which is very hard to break without ADB, because i think even if i flash stock ROM it will boot recovery because somewhere deep inside, it is written from that bootloader,
Again, never joke with bootloader, if it dont support, it dont support and over, i dont want TWRP anymore.
Dont get in this trouble, mybe nobody will be able to fix it if he dont know how it happened.
______
Commands
_______
adb reboot bootloader (to go into bootloader)
fastboot flash boot boot.img (this is i used)
fastboot flash system system.img (this is ROM, like kitkat, or lolipop)
fastboot flash userdata userdata.img (this can be optional, it means full reset)
fastboot flash recovery recovery.img ( if on twrp , dont flash this thing if not cause problems)
indestructible master said:
O, oh man, i just got shocked !!! By all this.
I understood that my problem is in boot,
because this command
fastboot -c "lge.kcal=0|0|0|x" boot c:\twrp.img
tells android that when i press power button, to boot into whatewer it is pointed to.
So this command tells android to boot recovery instead of normal system.
So i just reverted it in bootloader (fastboot) mode, by pushing command
fastboot flash boot c:\boot.img
So it booted up again ) , and also important, without losing any precious data. ))
______
It is true when people say that if everything fails in android, there is always a bootloader that you cant destroy.
And also here are commands for other partitions, in this way you can flash whole system without root or anything, for anybody who face this problem which is very hard to break without ADB, because i think even if i flash stock ROM it will boot recovery because somewhere deep inside, it is written from that bootloader,
Again, never joke with bootloader, if it dont support, it dont support and over, i dont want TWRP anymore.
Dont get in this trouble, mybe nobody will be able to fix it if he dont know how it happened.
______
Commands
_______
adb reboot bootloader (to go into bootloader)
fastboot flash boot boot.img (this is i used)
fastboot flash system system.img (this is ROM, like kitkat, or lolipop)
fastboot flash userdata userdata.img (this can be optional, it means full reset)
fastboot flash recovery recovery.img ( if on twrp , dont flash this thing if not cause problems)
Click to expand...
Click to collapse
You good now...
([emoji813]9/[emoji725]/9[emoji813])
m
EDIT:
In my way of trying to apply to warranty and flashing the stock package into the phone and Windows being Windows, I had problems using the batch script, it stopped for long time and didn't do nothing forcing me to restart the phone and restart the batch, until I uninstalled the driver and make Windows reinstall it automatically (manage devices) and it finally flashed it all, actually I flashed the package three times just to be sure lol. So, in the end I wanted to turn off the friggin phone because I was very done with it (what a PITA it has been) and wanted to apply for my warranty so as there is no command in fastboot to shutdown the phone I didn't know how to shut it down so I tried pressing Power button and releasing it the moment the screen goes off but I think I didn't do it right or the phone can't be shutdown that way (this is most probably the answer), well the phone rebooted and by the grace of Zeus it booted for the first time into MIUI and now is waiting for me to configure the phone, none of the times I flashed this packaged into the phone it booted into MIUI, never, and just when I want to turn the phone this thing boots, I don't know if I'm going to venture into flashing anything again being the phone how it is but goddamnit it was a real PITA, I had to use my old Redmi Note 3.
So, tl;dr: Flashed stock package, phone booted finally, all is OK for now.
====================================================================================================
====================================================================================================
Sooo, I was having problems with flashing stuff on this phone but I solved them and I was able to flash HavocOS, it was OK and I could use my phone kinda well (some reboots but nothing serious, or so I thought). So, until 12 hours ago my phone was having problems with the File Manager (I used FX app and also the stock one), it hanged and didn't respond and made the phone reboot itself a couple times, that was weird, actually the whole time I used this ROM I was having problems with my files, it used to took long time to read some files and I was thinking that maybe my SD was bad but apparently it's not. So, after the second reboot I was able to finally open the file manager but navigating through the SDCard was buggy and the app didn't show me any file (it show me an empty list) so I rebooted my phone manually (this time wasn't done by the phone itself) and now is when the phone never passed from the Havoc logo, I waited something close to 30 min and nothing, rebooted and waited 10 min and nothing, it still hanged on the logo, went into recovery to wipe everything and re-flash all and after doing all that and tried to boot to system my phone was booting to recovery and didn't past that, tried installing stock (flash_all script) and then installing recovery and everything again and nothing, it booted to recovery always. So there is when I realized I couldn't change anything in the slot A (at least to what boot refers), I can't install TWRP nor OrangeFox, I can do it in slot B, and even if I boot into recovery on slot B I can flash the zip installer, change the slot and try to boot to recovery from slot A but it boots to the bootloader, and yes, TWRP didn't output any error when flashing the installer.
Yes, the script flashes everything OK, well not everything, system and vendor partitions (A and B) I had to flash them manually because it gave me some errors with the script (reading errors, and yes I compared checksums so it was super weird) but in the end supposedly the stock ROM must have been installed, which I couldn't try because even after flashing everything on the script the phone was booting to bootloader, I didn't give importance to this because before I was able to flash and boot HavocOS I did the same thing because my phone was bootlooping into fastboot: I ran the script, flashed manually those images because it gave me the same errors, tried to boot to system and the phone booted to bootloader, didn't give a sheat, flashed OrangeFox recovery, ROM, recovery installer, GApps, nofde patch and then I was able to boot to HavocOS. But now this time I tried to install TWRP with fastboot command but it didn't worked, fastboot doesn't throw any errors while flashing, it reported:
Sending 'boot_a' (39780 KB) OKAY [ 1.042s]
Writing 'boot_a' OKAY [ 0.208s]
Finished. Total time: 1.263s
But if I try to boot into recovery it sends me to fastboot/bootloader, if I do this in the slot B I can successfully boot into recovery and, as I said, if I flash the installer, change the slot and reboot to recovery, my phone reboots to fastboot.
This has happened to someone else?
Does anybody knows of any solution?
I still have warranty (phone has less than 3 months) so I probably can flash the stock package and lock my bootloader so I can get my phone checked as probably it is a hardware failure, probably and hopefully .
Oh, and also I have to add that the recovery was also lagging sometimes (OrangeFox). Sometimes when I was looking into files on the SD, also when I pressed the "reboot system" button it hanged for half a minute and the it proceeded to reboot, and also once when I was flashing the nofde patch the phone also hanged and rebooted into recovery by itself. So this indicates that maybe is a hardware thing right? Because there is no way that the recovery could have gotten corrupted or something just out of the blue.
Yes. I'm another victim here... And now I can't install recovery on slot b either. Can't figure out what's wrong. This giving me such a hard time...
RthurPendragon said:
Yes. I'm another victim here... And now I can't install recovery on slot b either. Can't figure out what's wrong. This giving me such a hard time...
Click to expand...
Click to collapse
What I ultimately did was wipe everything on slot A, then wipe everything on slot B, then I proceeded to install the ROM on the slot A then re-flash the recovery and reboot to system and that's all. But I did had to wipe both slots A and B. If nothing works you can apply the original ROM (search for it on these forums) and go back to stock.
Jhon_Locke said:
What I ultimately did was wipe everything on slot A, then wipe everything on slot B, then I proceeded to install the ROM on the slot A then re-flash the recovery and reboot to system and that's all. But I did had to wipe both slots A and B. If nothing works you can apply the original ROM (search for it on these forums) and go back to stock.
Click to expand...
Click to collapse
In my case, I wiped system and installed Evolution X ROM (OSS version) with Custom Recovery (SHRP) Then when I want to reboot into recovery again to flash Magisk, There's no recovery... It always opens with fastboot mode. I tried flashing recovery.zip from slot b. Still no result.
Yes. I'm next victim here... And now I can't install recovery on slot b nor slot a. Can't figure out what's wrong. When i flash twrp recovery it flash successfully but when I boot into recovery it stuck in fastboot mode
Change slot and flash again but nothing worked it again stuck in fastboot mode even i flash different version of Twrp(3.2.1) but again it stuck in fastboot mode both a and b slot.
So i flashed stock rom and lock bootloader.
If have any solution how to install custom recovery please help me.
Thanks
Iamdchandan said:
Yes. I'm next victim here... And now I can't install recovery on slot b nor slot a. Can't figure out what's wrong. When i flash twrp recovery it flash successfully but when I boot into recovery it stuck in fastboot mode
Change slot and flash again but nothing worked it again stuck in fastboot mode even i flash different version of Twrp(3.2.1) but again it stuck in fastboot mode both a and b slot.
So i flashed stock rom and lock bootloader.
If have any solution how to install custom recovery please help me.
Thanks
Click to expand...
Click to collapse
Because there are 2 different twrp's.
One of which is for Android 9 and the other for Android 10. You are flashing the wrong one which is why you go to fastboot.
All documentation is on the applicable threads.
People need to stop blindly flashing stuff without reading the documentation or even know what they are doing.
So many people have bricked mi A3 because they don't read first
garylawwd said:
Because there are 2 different twrp's.
One of which is for Android 9 and the other for Android 10. You are flashing the wrong one which is why you go to fastboot.
All documentation is on the applicable threads.
People need to stop blindly flashing stuff without reading the documentation or even know what they are doing.
So many people have bricked mi A3 because they don't read first
Click to expand...
Click to collapse
I have flashed twrp latest 3.4.4 for Android 10 but it is stuck in fastboot mode either slot a or b.
What happened if i downgrade Android 10 to 9 and then flash twrp. Maybe it will successfully flashed.
Iamdchandan said:
I have flashed twrp latest 3.4.4 for Android 10 but it is stuck in fastboot mode either slot a or b.
What happened if i downgrade Android 10 to 9 and then flash twrp. Maybe it will successfully flashed.
Click to expand...
Click to collapse
Don't do it you will mess up your persist partition.
How are you flashing? You must be after typing something wrong
garylawwd said:
Because there are 2 different twrp's.
One of which is for Android 9 and the other for Android 10. You are flashing the wrong one which is why you go to fastboot.
All documentation is on the applicable threads.
People need to stop blindly flashing stuff without reading the documentation or even know what they are doing.
So many people have bricked mi A3 because they don't read first
Click to expand...
Click to collapse
garylawwd said:
Don't do it you will mess up your persist partition.
How are you flashing? You must be after typing something wrong
Click to expand...
Click to collapse
First if all reboot into fastboot mode then connect with pc then type command " fastboot flashing unlock" enter now again forcefully reboot into fastboot mode then type next command "fastboot flashing_critical unlock" now bootloader unlock.
Again reboot into fastboot mode then type command "fastboot getvar current-slot"
Now change current active slot and then type command " fastboot erase boot" . Now finally flashed twrp latest (3.4) for Android 10 with command "fastboot flash boot twrp.img" now it flash successfully then type command "fastboot reboot" and then press volume up then hit enter and it return in fastboot mode then i have again change slot and repeat all process with that slot but it again stuck in fastboot mode. After all i have changed twrp version but again same thing repeat so I flashed stock Android 10 through Mi flash and lock bootloader.
That's all whole process.
If do something wrong please help me to figure out.
Waiting for your reply ?.
Love
try sharp recovery
Sami Devo said:
try sharp recovery
Click to expand...
Click to collapse
I don't know installation process of sharp recovery.
Iamdchandan said:
I don't know installation process of sharp recovery.
Click to expand...
Click to collapse
install on the other slot... dont flash it on running rom slot... if rom running A.. chng it to B. then flash to B.. then goto recovery flash the sharp zip when sharp opens..then again chng slot to A.. running rom slot..
okk ur phn boots.