After Installing Custom rom, OS is not detected! - Xiaomi Redmi 7 Questions & Answers

Model - Redmi 7
I have installed ASOP Extended from downloaded from here. Following are the steps that i have followed to install ASOP.
Go to TWRP recovery.
Wiped the data!
Installing using adb sideload.
Reboot to load the OS.
But now when I reboot, It gets stuck on Logo Screen of "Redmi by Xiaomi" and eventually stuck at that screen. While Logo appears sometimes a line at the bottom of the phone appears saying "unlocked"(This screens appears like lights on night club). I'm stuck at this screen. I can go back to TWRP recovery but when I do restart again this screens appears again.
One more thing at the time of installing ASOP when it was completed it showed this message "Total xfer: 1.00x".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is screenshot!
Any help regarding this issue would be lot helpful!
Thanks in Advance!

Try with orange fox recover. Maybe solve problem

May be you are first at rom flashing. If you are you should know you have to first flash vbmeta.zip one time ( not every time ). After that you can flash any custom rom maded for redmi 7. And you can use twrp 3.3.2b version because it is the most stable and it can flash all rom without any error. And you should always keep the stock recovery zip in your sd card so if any problem occures like no os installed you can always revert to stock rom.

Mes shahadat said:
May be you are first at rom flashing. If you are you should know you have to first flash vbmeta.zip one time ( not every time ). After that you can flash any custom rom maded for redmi 7. And you can use twrp 3.3.2b version because it is the most stable and it can flash all rom without any error. And you should always keep the stock recovery zip in your sd card so if any problem occures like no os installed you can always revert to stock rom.
Click to expand...
Click to collapse
I follow this steps but get the same problem i think. Unlocked sucesfully redmi, install twrp 3.3.2b and installed aosp extended but i get redmi by xiaomi forever...

Need help
Bro did you found the solution for this problem. I have flashed pixel experience [10] but after finishing flashing the rom before rebooting it is showing "warning no os installed do you want to continue" after that same redmi screen with unlocked written below flashing again and again. Pls help.

Related

DHD boot img problem

Hi,
I have a desire hd (Asia). Using the guide http://forum.xda-developers.com/showthread.php?t=1528925 I successfully rooted/unlocked using the HTC dev method, and installed the Nik Project X v4.1 By Nikhil007 rom for DHD http://forum.xda-developers.com/showthread.php?t=1843300. As mentioned in the steps, I fast booted the boot image to run the rom by booting in boot loader and then fast boot.
I recently tried to install miui_DHD_2.4.13_mf8r9wz1x6_2.3. After installing the rom, I again fast booted the boot image file from the zip of the rom. After trying out for few days, I thought of trying out the newer rom for dhd, MIUI.us v4 JB 4.1.
I wiped the cache partition, the davlik cahce and data/factory reset and then installed the rom for the SD card.
After installing the rom, when I tried to fast boot the boot image, I got stuck at
“sending ‘boot’ <..kb>...”
After waiting for few minutes, I disconnected my phone and got the message in command prompt saying:
“FAILED <data transfer failure <too many links>>”
I checked “fastboot devices”, and my phone is displayed.
Then I tried boot image of nik projectX rom, which didn’t worked. In fact I cannot flash any boot image.
I then had to reinstall Miui 2.3 rom. Right now the rom is working fine. But I want to install back Nik project x rom.
Please Help.
Please find below screen shot of the boot loader screen. I am using CWM based recovery v5.0.2.7.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Error while flashing the boot image:
I have installed HTC sync. I also have java installed, and downloaded the bundle from android development. I tried the mini-adb also but didn’t work. I have changed cable, tried on different USB ports and a different installation of OS. I am using WIN 7. I had successfully flashed the boot image using the following files.
I have taken a backup from recovery when I had ProjectX installed before installing Miui 2.3.
Please help.

[Q] weird BOOTSCREEN - how to fix it???

Hi
When i boot my P6, on the bootscreen there are 3 wierd pixels iluminated. Look at phone screen on bottom right corner:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
They apeared when i had stock rom (B606)
i only did root using eRoot Tool
i had instaled busybox because an app to hide softkeys required busybox to be instaled, but i didnt changed anything in busybox (unless some app did)
How can i fix that? when i brought this phone one month ago they were not there.
Someone sugested i could flash boot.img??? is that image part of boot.img? is that right? i dant want to brick my phone.
Now i'm on firmware B506 with recovery TWRP 2.6.3.7, all is working fine but i just want to get rid of that pixels.
Help would be apreciated! Thanks in advance!
Remove SD card. Boot in to recovery with 3 buttons push, in recovery do a wipe data and phone will start normaly.
alex.79 said:
Remove SD card. Boot in to recovery with 3 buttons push, in recovery do a wipe data and phone will start normaly.
Click to expand...
Click to collapse
I've flashed yesterday trough TWRP 2.6.3.7 the newest B506 stock rom and i did a full wipe except external storage. the pixels stills there
No wipe data will fix that. Your screen is the problem.
ZuperStyler said:
No wipe data will fix that. Your screen is the problem.
Click to expand...
Click to collapse
But that bug is only in bootscreen. It's not bad pixels. Don't u think its possible to be a bug in ASCEND P6 logo image? Can i flash boot.img to see if it fixes? If i flash boot.img will i lose my recovery or rom?
No, you will not lose anything, you can flash the boot animation, maybe it will fix the problem.
ZuperStyler said:
No, you will not lose anything, you can flash the boot animation, maybe it will fix the problem.
Click to expand...
Click to collapse
do i have to flash a specific boot.img or there are ony one comom file to all P6 devices? Is boot.img the kernel?
im running stock B506-CN rom(latest oficial kitkat firmware), with TWRP 2.6.3.7

[Q] Something Wrong with Custom ROM installation

I unlocked my bootloader and rooted my HTC One X. I have used the ClockworkMod recovery.
I had CyanogenMod 10.2 installed and it ran perfectly fine.
Later on, I downloaded the 'cm-11-20140308-SNAPSHOT-M4-endeavoru.zip' file to install the the CM 11.2
But it seems something terribly has gone wrong.
This error message was shown during installing CM 11.2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and it got stuck on this screen after rebooting
Later on I tried flashing the 'boot.img' of CM 10.2 to get back to that ROM, but I encountered this error.
But when I tried installing the 'cm-10.2.1-endeavoru.zip', it was a success, but I am still stuck at the same position.
Please help me restoring the phone back, I dont care if I have to revert back to HTC's Original ROM, as long as the phone is back working.
I am novice at this thing, so please bear with me if I ask some stupid questions.
khepacheley said:
I unlocked my bootloader and rooted my HTC One X. I have used the ClockworkMod recovery.
I had CyanogenMod 10.2 installed and it ran perfectly fine.
Later on, I downloaded the 'cm-11-20140308-SNAPSHOT-M4-endeavoru.zip' file to install the the CM 11.2
But it seems something terribly has gone wrong.
Please help me restoring the phone back, I dont care if I have to revert back to HTC's Original ROM, as long as the phone is back working.
I am novice at this thing, so please bear with me if I ask some stupid questions.
Click to expand...
Click to collapse
First of all if you want to install CM11 you must to use latest CWM from CM11 thread or TWRP2.7 or Philz latest. And now mount sd card copy your sense rom to the card install it, flash the boot img. and you are good to go. After this read again thread for CM11 and how to install and try agin but be shure you read the thread
use the recovery that thommy put in the first page of the cm11 post (or the philz last recovery) it seems that the cmw that you have doesen't support kitkat

unable to install or launch TWRP

Hey,
I've unlocked my Mi 6 today (i'm using the global developer ROM 8.9.13 (MIUI10)) and wanted to root it, as many guides said I have to replace the default recovery with something like TWRP
result was:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
after leaving it like that for 30 minutes nothing has changed, the screen on my mobile was the the default fastboot screen nothing ever changed
so i tried to just launch TWRP without installing it:
nothing changed like before and i've stopped after 5minutes
i also have the same result with RedWolf Recovery Project:
I also tried using XiaoMiTool but all i got was the message that my phone is not connected to my MiAccount and still locked and did nothing
Does anyone have any idea whats going?
Edit:
seems like flashboot commands dont work? tried flashboot continue to reboot the device after checking with fastboot devices to see if it was recognized by the system and it was indeed.
and the result were the same as above cmd was stuck mobile didnt react....
Thanks
Dugma
Dugma said:
Hey,
I've unlocked my Mi 6 today (i'm using the global developer ROM 8.9.13 (MIUI10)) and wanted to root it, as many guides said I have to replace the default recovery with something like TWRP
[...]
Click to expand...
Click to collapse
I'd rather flash the recovery than just booting to it. You can flash it with fastboot flash recovery recovery.img
You should be able to boot to recovery afterwards. Or at least that's what I did when I bought my phone. I updated to the latest version of MIUI (android 8.0), then I enabled "oem unlock") and I was able to flash twrp with no problems. Keep in mind that the stock rom erases any custom recovery with the default one on boot.
Facing the same issue. Tried everything but no success.

Realme x2 Fingerprint enrollment is not working anymore after RUI downgrade

Realme X2​
Hi, I have a problem with my Realme X2 RMX1993
When realme UI 2 was released I was already rooted with magisk and had the TWRP recovery installed. In order to update from RUI 1 to RUI 2 I un-rooted the phone and reverted back to stock recovery, updated the system (everything went fine and worked fine) then flashed back the TWRP recovery, and the phone has begun to boot directly to the fastboot mode even if I wanted it to boot either normally or in the recovery mode.
After messing around I managed to flash the stock recovery from which I flashed a down-grade package to go from RUI 2 to RUI 1. After that, I got the previous version of stock recovery and flashed the latest RUI 1 version and finally, the system booted up.
Everything is working nice now apart from the fingerprint enrollment which keeps flashing and vibrating without making appear the icon on the sensor.
Here is a short I recorded:
I followed step by step the instructions in these videos:
- (in the first seconds here it is how the fingerprint enrollment page flashes after the phone reset)
-
I even tried to flash the stock ozip package and tried to install other ROMs but the fingerprint enrollment still doesn’t work.
When I unlocked the bootloader the first time and flashed TWRP and magisk the fingerprint was still working fine and now it doesn't.
I even downloaded the ofp package and tried to flash it through the Realme Flash Tool but the program gives me an error message saying “Cannot find central directory”.
Can you help me, please?
Do you have any suggestions?
Thank You
Same issue on Realme Q5 pro (rmx3372 => global rom rmx3371)
i did everything nothing worked
Same issue on my realme x2 pro (RMX1931). Downgrading from android 13 custom rom to official version (android 11) led to this awful result. Any clues/solutions?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Categories

Resources