So today I flashed Razziell's RR 7.1.2 from his MK but there were bugs and decided to roll back everythings was working fine until I rebooted to twrp, It blinks the TeamWin logo and does not enter twrp, downloaded again TWRP from 4pda but still no luck the rom works fine...but I am unable to enter TWRP it just blinks the damn logo...any help I guess?
UPDATE
fixed problem by flashing newest Kernel
Have you tried adb command "fastboot boot twrp.img"? This happened to me before where i can't boot into TWRP by manually pressing "VOL UP + POWER" or Reboot to Recovery via app, but "fastboot boot twrp.img" via PC works fine. What i did is i restored back into stock by flashing Fastboot ROM through MiFlash then after that i flash TWRP, now it works fine.
Flynhx said:
Have you tried adb command "fastboot boot twrp.img"? This happened to me before where i can't boot into TWRP by manually pressing "VOL UP + POWER" or Reboot to Recovery via app, but "fastboot boot twrp.img" via PC works fine. What i did is i restored back into stock by flashing Fastboot ROM through MiFlash then after that i flash TWRP, now it works fine.
Click to expand...
Click to collapse
Yeah tried to do that still the same it blinks,then tried to reflash the twrp which I donwnloaded from 4pda still it blinks
Related
Hey guys,
I have an stock, unlocked and rooted xt905 lying here with stock recovery right now.
For several times now I tried to flash either cwm or twrp but had no luck.
Thats what I did:
- complete backup
- unlock bootloader
- restore backup
- fastboot flash boot twrp.img
- fastboot reboot
Flashing twrp doesnt throw up any error but as soon as I say reboot, the phone reboots into twrp instead of booting the system.
If I try to reboot to system within twrp, it reboots to twrp again. Booting to recovery from twrp brings me to stock recovery.
Its the same thing with cwm and I dont have any clue why, as other users are saying that twrp is working fine.
Till now I tried several different versions of fastboot, twrp and cwm and none of them worked.
Any ideas?
You're using the wrong fastboot command.
By typing "fastboot flash boot twrp.img" you are flashing TWRP in place of the boot.img. You need to type "fastboot flash recovery TWRP.img."
RikRong said:
You're using the wrong fastboot command.
By typing "fastboot flash boot twrp.img" you are flashing TWRP in place of the boot.img. You need to type "fastboot flash recovery TWRP.img."
Click to expand...
Click to collapse
OMG....
I am working on this phone since yesterday and couldnt figure it out....till now.
Embarrassing! I flashed about a dozen phones before and never had any problems whatsoever and now this.....
Thanks anyway! I am glad that I didnt brick the phone with flashing the wrong partition.
Dear Community,
I tried to flash TWRP 3.1.1 for Oreo rom with my Red Mi 3S. And I found some thing strange.
3S is flashed to MIUI 9.7.11.23 DEV. And BL is unlocked via XiaoMi's MiFlash_Unlock.
In Developer settings, OEM unlock is ON, and Lock status is unlocked.
Then I tried fastboot on my Mac to flash TWRP 3.1.1 in the Xperience Oreo ROM thread.
In the console after "fastboot flash recovery TWRP-3.1.1-0-unnoficial-oreo-v2-land.img", result showed OKAY. However, after a reboot, holding Volume+ and Power or "adb reboot recovery" will bring me to XiaoMi Recovery instead of TWRP.
I tried "fastboot boot TWRP-3.1.1-0-unnoficial-oreo-v2-land.img", and it works fine.
Anyone could help me to figure out why flash TWRP could not be done successfully?
Thanks much.
sirotaku said:
Dear Community,
I tried to flash TWRP 3.1.1 for Oreo rom with my Red Mi 3S. And I found some thing strange.
3S is flashed to MIUI 9.7.11.23 DEV. And BL is unlocked via XiaoMi's MiFlash_Unlock.
In Developer settings, OEM unlock is ON, and Lock status is unlocked.
Then I tried fastboot on my Mac to flash TWRP 3.1.1 in the Xperience Oreo ROM thread.
In the console after "fastboot flash recovery TWRP-3.1.1-0-unnoficial-oreo-v2-land.img", result showed OKAY. However, after a reboot, holding Volume+ and Power or "adb reboot recovery" will bring me to XiaoMi Recovery instead of TWRP.
I tried "fastboot boot TWRP-3.1.1-0-unnoficial-oreo-v2-land.img", and it works fine.
Anyone could help me to figure out why flash TWRP could not be done successfully?
Thanks much.
Click to expand...
Click to collapse
Have you tried rebooting the phone in recovery via the key combination( press all 3 buttons power+ vol up+ vol down and when you get vibration release power button and vol down but not vol up because i have faced similar issues while pressing vol up and power ) as far as i know after flashing a custom recovery you need to give the command " fastboot boot recovery.img" where recovery should be replaced by the file name of your recovery and adb reboot recovery is not working may be due to some other reasons but dont worry flash the twrp recovery via fastboot and then reboot using the above command
Ash225 said:
Have you tried rebooting the phone in recovery via the key combination( press all 3 buttons power+ vol up+ vol down and when you get vibration release power button and vol down but not vol up because i have faced similar issues while pressing vol up and power ) as far as i know after flashing a custom recovery you need to give the command " fastboot boot recovery.img" where recovery should be replaced by the file name of your recovery and adb reboot recovery is not working may be due to some other reasons but dont worry flash the twrp recovery via fastboot and then reboot using the above command
Click to expand...
Click to collapse
with mine redmi 3s also only command works to boot in twrp but all 3 or either button combination is not working
Vinayakn73 said:
with mine redmi 3s also only command works to boot in twrp but all 3 or either button combination is not working
Click to expand...
Click to collapse
In this case, I think it means flash not successful right? using command fastboot boot twrp.img means only boot this time ...
hey guys.i am in a bad situation now.I unlocked bootloader on my mi a1 and,installed twrp successfully.then,i wanted to install custom rom.I downloaded AEX and Gapps-ARM64-8.1-NANO.I followed all steps correctly,flashed rom;but,when i pressed reboot to system,it got stuck in bootloop for 30 minutes.So,i immediately rebooted to twrp recovery.then,i wiped data.then,i pressed reboot to bootloader,but suddenly i pressed do not install twrp.it then rebooted to stock recovery.then,i pressed reboot,and then,it booted succesfully to aex.but,i am not able to install playstore,or any app.also,device is not detecting in pc in fastboot mode.
Someone please help, am stuck on aex with no function app except phone and via browser......on stock recovery.....unable to install any apps,not even playstore
Harold128 said:
hey guys.i am in a bad situation now.I unlocked bootloader on my mi a1 and,installed twrp successfully.then,i wanted to install custom rom.I downloaded AEX and Gapps-ARM64-8.1-NANO.I followed all steps correctly,flashed rom;but,when i pressed reboot to system,it got stuck in bootloop for 30 minutes.So,i immediately rebooted to twrp recovery.then,i wiped data.then,i pressed reboot to bootloader,but suddenly i pressed do not install twrp.it then rebooted to stock recovery.then,i pressed reboot,and then,it booted succesfully to aex.but,i am not able to install playstore,or any app.also,device is not detecting in pc in fastboot mode.
Someone please help, am stuck on aex with no function app except phone and via browser......on stock recovery.....unable to install any apps,not even playstore
Click to expand...
Click to collapse
Flash stock boot.img using fastboot command
Then use mi flash tool and install fastboot ROM
akashavel said:
Flash stock boot.img using fastboot command
Then use mi flash tool and install fastboot ROM
Click to expand...
Click to collapse
Hey,Akshay.Can u give me the needful links for stock boot.img, mi flash tool and fastboot ROM ,?
Also,what command should I enter?
Harold128 said:
Hey,Akshay.Can u give me the needful links for stock boot.img, mi flash tool and fastboot ROM ,?
Also,what command should I enter?
Click to expand...
Click to collapse
Download stock and flash according to the instructions given on that site
http://en.miui.com/getrom-333.html?m=yes&mobile=2
I messed up and accidentally flashed the old oreo B32-based bootstack to use Candy ROM using NFound's TWRP 3.2.1-8 which was specifically made for the newer b12-based bootstack. Now I can't boot into TWRP at all but the phone still works just fine for day-to-day use. I tried to flash NFound's TWRP 3.2.1-7 via fastboot but after entering "adb reboot bootloader" command, I got stuck on the ZTE logo screen and was unable to proceed into the bootloader menu to continue with the TWRP reflashing process. I am able to reboot back into the ROM by holding down the power button for 10 seconds but I would really like to be able to get my TWRP working again.
I love NFound's work and I brought this problem onto myself by accident but any help or guidance will be greatly appreciated!
Use EDL to go back to stock and flash it again......
you're fine because you can boot into your ROM. Reboot to EDL and use EDL Tool to flash recovery of choice.
Sorry guys, but I couldn't boot into EDL mode either. I tried different button combinations (power + vol down, power + vol up + vol down), the EDL tool, command lines, etc but none of them could get the phone to boot into fastboot nor EDL. It always just reboots back into the ROM.
ileikpi said:
Sorry guys, but I couldn't boot into EDL mode either. I tried different button combinations (power + vol down, power + vol up + vol down), the EDL tool, command lines, etc but none of them could get the phone to boot into fastboot nor EDL. It always just reboots back into the ROM.
Click to expand...
Click to collapse
Do you have root?? If you do, I recommend actually just using flashify app to flash the correct 3.2.1-7 TWRP to recovery. No need to mess with EDL
from computer adb
adb reboot edl
or
su
reboot edl
Sent from my Xperia Z3C using XDA Labs
JTruj1ll0923 said:
Do you have root?? If you do, I recommend actually just using flashify app to flash the correct 3.2.1-7 TWRP to recovery. No need to mess with EDL
Click to expand...
Click to collapse
Tried to flash TWRP 3.2.2-0 that way but no luck. The app says that the recovery image has been flashed successfully but when I try to boot into recovery, the led blinks once and the screen goes black.
Infy_AsiX said:
from computer adb
adb reboot edl
or
su
reboot edl
Sent from my Xperia Z3C using XDA Labs
Click to expand...
Click to collapse
Yea I tried that as well but the phone just reboots back into the ROM instead of going into edl. Tried using a terminal app on the phone to run "reboot edl" as well but got the same result.
ileikpi said:
Tried to flash TWRP 3.2.2-0 that way but no luck. The app says that the recovery image has been flashed successfully but when I try to boot into recovery, the led blinks once and the screen goes black.
Yea I tried that as well but the phone just reboots back into the ROM instead of going into edl. Tried using a terminal app on the phone to run "reboot edl" as well but got the same result.
Click to expand...
Click to collapse
Is your problem solved ?
CelesteBlue said:
Is your problem solved ?
Click to expand...
Click to collapse
Sorry mate still no luck haha and I just got a new phone as well. But my ZTE still works perfectly fine, just no way to boot into recovery, bootloader, or edl mode. The only thing I haven't tried is using an edl cable but I don't have access to those at the moment. If you have the same problem as me, you might wanna give the edl cable a try if all else fails.
i flashed Oreo Rom and then flash Twrp 3.2.1.8. after restart i select that phone should boot into recovery. but phone led blinks and then phone goes off. I want to boot into recovery?
I was a running my Redmi note 7 with DerpFest rom and with Ofox custom recovery
The phone suddenly got into a bootloop and now I can only access the fastboot screen (not even the Custom recovery screen)
How can I proceed to reinstall the sistem and the Custom Recovery?
I've already downloaded Minimal ADB and fastboot ulitily to make things faster
Edit: Also, I couldn't get the MiFlash program working, some errors are happening
advanced_gamerBR said:
I was a running my Redmi note 7 with DerpFest rom and with Ofox custom recovery
The phone suddenly got into a bootloop and now I can only access the fastboot screen (not even the Custom recovery screen)
How can I proceed to reinstall the sistem and the Custom Recovery?
I've already downloaded Minimal ADB and fastboot ulitily to make things faster
Edit: Also, I couldn't get the MiFlash program working, some errors are happening
Click to expand...
Click to collapse
Just copy the ZIP file of the ROM and flash, as you dos when you first installed. Maybe just wipe caches
advanced_gamerBR said:
I was a running my Redmi note 7 with DerpFest rom and with Ofox custom recovery
The phone suddenly got into a bootloop and now I can only access the fastboot screen (not even the Custom recovery screen)
How can I proceed to reinstall the sistem and the Custom Recovery?
I've already downloaded Minimal ADB and fastboot ulitily to make things faster
Edit: Also, I couldn't get the MiFlash program working, some errors are happening
Click to expand...
Click to collapse
Try to reflash the recovery with fastboot first. Need to have xiaomi usb drivers installed to can use adb/fastboot connection. When the phone is in fastboot mode connect with a good (original) USB cable and check the connection with "fastboot devices" command in cmd/powershell window. Extract and use "recovery.img" from latest orangefox zip file. Flash to phone using "fastboot flash recovery recovery.img" command then reboot holding together "Volume Up + Power" until you see the MI logo, release "Power" button but keep pressing "Volume Up" until you see the recovery. When you have working orangefox recovery, try to flash new rom. More information about driver/fastboot/recovery here (skip "unlock the bootloader" part): https://forum.xda-developers.com/redmi-note-7/how-to/one-redmi-note-7-unlock-bootloader-t3890751
The MiFlash program issue can be caused by missing/wrong xiaomi usb driver, if you will have answer from "fastboot devices" command (phone detected), can try the MiFlash again, just be careful: DON'T LOCK the BOOTLOADER. Good luck.