Related
PROBLEM: ZL LockedDualRecovery is causing bootloop (DO NOT USE IT IN PRFCreator)
Downloads
PRFCreator
FTF LOLLIPOP XPERIA ZL 10.6.A.0.454
SuperSU.Zip
ZL LockedDualRecovery (Flashable).zip
Requirements[LB/UB]
Have ROM 10.5.1.A.0.292 INSTALLED with ROOT and ZL LockedDualRecovery (Installer).zip
Instructions
1 - Open PRFCreator and Select the items that were downloaded above: .FTF (Lollipop), SuperSU.Zip, ( NO )ZL LockedDualRecovery. Ticks all the boxes like the picture! E Click Create!
{
"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"
}
2 - After Create flashable-signed.zip move to the memory of the Xperia ZL! (Watch has to be "signed" the file name if flashable.zip may have been an error sign for lack of java probably).
3 - Turn it off Turn and enter the Recovery
4 - In philz Recovery or TWRP Recovery Do it!
* Format Data
* Wipe Cache
* Wipe Dalvik
* Factory reset
5 - Last step Install ROM.zip you moved to the Memory.
Note: Pay attention to PRFCreator can not occur errors make sure to have java installed.
PORTUGUESE
Downloads
PRFCreator
FTF LOLLIPOP XPERIA ZL 10.6.A.0.454
SuperSU.Zip
ZL LockedDualRecovery (Flashable).zip
Requisitos [LB/UB]
Tenha a ROM 10.5.1.A.0.292 INSTALADA com ROOT e ZL LockedDualRecovery (Installer).zip
Instruções
1 - Abra o PRFCreator e Selecione os itens que foram baixados acima: .FTF (Lollipop), SuperSU.Zip, ZL LockedDualRecovery. Marque todas as caixas igual a imagem! E Clique em Create!
2 - Após Criar mova flashable-signed.zip para a memoria do Xperia ZL! (preste atenção tem que ficar "signed" o nome do arquivo se ficar flashable.zip pode ter ocorrido um erro ao assinar por falta do java provavelmente).
3 - Desligue o aparelho, Ligue e entre no Recovery
4 - No Philz Recovery ou TWRP Recovery Faça isso!
*Format Data
*Wipe Cache
*Wipe Dalvik
*Factory reset
5 - Ultimo passo Instale a ROM.zip que você moveu para a Memoria.
OBS: Preste atenção no PRFCreator não pode ocorrer erros assegure-se de ter o java instalado.
Click to expand...
Click to collapse
Is a rule in Xda the English language, i speak spanish, portuguese is out of limits to me...
Very Good.
Sent from my D5833 using XDA Free mobile app
How you install the recovery? You don't need the root access for that?
Sorry, I have done the correction.
murphy46 said:
Is a rule in Xda the English language, i speak spanish, portuguese is out of limits to me...
Click to expand...
Click to collapse
Sorry, I have done the correction.
You need the rom .292 or .283 with root and installed dualrecovery...
nemerio said:
How you install the recovery? You don't need the root access for that?
Click to expand...
Click to collapse
You need the rom .292 or .283 with root and installed dual recovery or recovery...
Tested this method got me into bootloop.
Anyone here can report if it is working?
Abadeer said:
Tested this method got me into bootloop.
Anyone here can report if it is working?
Click to expand...
Click to collapse
The bootloop is because of the XZ Dual recovery isn't it?
Can we flash using Cyanogen Recovery? Getting "Signature Verification Failed..."
*EDIT* Nevermind, I'm a dummy, the ZIP has to say -signed on it. Flashing now!
Yes Functional.
Abadeer said:
Tested this method got me into bootloop.
Anyone here can report if it is working?
Click to expand...
Click to collapse
Please send me print the "LOG" in PRFCreator
Yes Functional. It is possible that you do not have java installed then the ROM.ZIP was not signed
Murilo Barbosa said:
Yes Functional. It is possible that you do not have java installed then the ROM.ZIP was not signed
Click to expand...
Click to collapse
No, I have, but yet got me in bootloop but I rooted it my own way.
Abadeer said:
No, I have, but yet got me in bootloop but I rooted it my own way.
Click to expand...
Click to collapse
Give me Logs in PRFCreator
hi! can we make this without recovery? because i think that will cause bootloop, have you try this? im on locked BL
do not use the DualRecovery in PRFCreator to avoid bootloop
Jaycel0820 said:
hi! can we make this without recovery? because i think that will cause bootloop, have you try this? im on locked BL
Click to expand...
Click to collapse
Do not use the DualRecovery in PRFCreator to avoid bootloop! Thanks:good:
Murilo Barbosa said:
Do not use the DualRecovery in PRFCreator to avoid bootloop! Thanks:good:
Click to expand...
Click to collapse
Is there any working recovery?
So using OTA kills root this time again?
DoubleYouPee said:
So using OTA kills root this time again?
Click to expand...
Click to collapse
Yes .I tried coming from 4.4.2 (root)-->4.4.4 (root survived)-->5.0.2 (root lose)
Hey guys, is the problem with dual recovery a conflict with the PRFcreator or does it stem from the dual recovery files being outdated??
Xposed Framework and Xperia Xposed (LP) - WORKING!!
Steps:
1. Flash Pre-rooted fw without dual-recovery, but SuperSU (booted till home screen)
2. Flash (fastboot) @Gustavo RD78's Advanced KK Stock Kernel (unlocked BL only) - (He is working on new advanced stock kernel for lollipop)
3. Enter TWRP Recovery and flash BusyBox-v1.23.1-Stericson.zip (Stericson) to get working busybox
4. Power Off device (DO NOT REBOOT)
5. Flash original 10.6.A.0.454 kernel with FlashTool (excluding everything but kernel)
6. Boot device till home screen
7. Repeat step 2
8. Enter TWRP Recovery and flash xposed-sdk21-arm-20150430.zip (alpha 4)
9. Power Off device (DO NOT REBOOT)
10. Repeat step 5
11. Repeat step 6
12. Install XposedInstaller_3.0-alpha2.apk
13. Done!!
.
pointblank_limited said:
Hey guys, is the problem with dual recovery a conflict with the PRFcreator or does it stem from the dual recovery files being outdated??
Click to expand...
Click to collapse
I can only guess it's the recovery... If you have a properly rooted stock LP ROM, installing XZDR the usual way with a PC installer also consistently results in a bootloop, even though the install finishes successfully with no problems. Speaking of proper root, the method from this thread works great, unlike Kingroot, which didn't work for me at all (seems like you are rooted, but you are not; can't mount /system as r/w).
I have been looking for ANY working recovery for ZL on 5.0.2 with locked BL. So far, found nothing...
XIAOMI.EU started uploading xiaomi.eu ROMs For Mi Mix 3
Stable Release from here https://xiaomi.eu/community/threads/miui-10-0-10-1-stable-release.47170/
Weekly Builds from here https://xiaomi.eu/community/forums/miui-rom-releases.103/
TWRP Recovery as per xiaomi.eu is https://androidfilehost.com/?fid=11410963190603869442
also its uploaded inside the shared links above
Installation procedure - 2nd post
Enjoy
Just few hours i got my bootloader unlocked. i did the installation and everything is working fine except one thing which is the magisk , the 18.0 version couldn't be installed. i keep 17.1 , Full screen is fine and no issue. the twrp is done and no more going to stock recovery.
my installation was :
1. unlocking bootloader
2. installation of twrp via fastboot.
3. reboot while pressing the volume up to reach recovery.
4. switch recovery language to english
6. format data from wipe.
7. reboot to recovery from reboot menu of twrp.
8. copying the rom file 8.12.7 to the internal storage
9. installing the rom.
10.reboot.
after finishing wizards and configure google account reboot again and install the magisk 17.1
Enjoy
Please give us complete guide to install, from unlock to final installation
I believe in we should have unlocked bootloader, then using fastboot to flash the twrp recovery -i had November 24 build-
Factory reset via twrp and installation of this build.
Myself i need around 3days to get my bootloader unlocked and install it. Maybe newer build will be available.
Work like a charm[emoji41]
And Google assistant on the AI press Button !
{
"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"
}
Envoyé de mon MIX 3 en utilisant Tapatalk
croisade said:
Work like a charm[emoji41]
And Google assistant on the AI press Button !View attachment 4661926
Envoyé de mon MIX 3 en utilisant Tapatalk
Click to expand...
Click to collapse
Happy to hear this.. awaiting my bootloader unlocking....:good:
Do not wipe the system partition before flashing the ROM. And you should come from a MIUI ROM.
I installed it via the following steps:
- Flash fastboot factory dev ROM 8.11.8 from here: http://www.miui.com/shuaji-393.html (flash_all.sh)
- Validate that the Device boots
- Flash TWRP Recovery "recovery-TWRP-3.2.3-1205-XIAOMI_MIX3-CN-wzsx150.img"
- Reboot and hold volume up until you get into the Recovery menu. Mostly the device will reboot 2 times here.
- Download and push the xiaomi.eu ROM to the device via "adb push xiaomi.eu_multi_MIMix3_8.11.30_v10-9.zip /sdcard/xiaomi.eu_multi_MIMix3_8.11.30_v10-9.zip"
- Flash the zip and reboot
- Enjoy
croisade said:
Work like a charm[emoji41]
And Google assistant on the AI press Button !
Envoyé de mon MIX 3 en utilisant Tapatalk
Click to expand...
Click to collapse
Had u problem with fingerprint or pattern?
PeppeCNN said:
Had u problem with fingerprint or pattern?
Click to expand...
Click to collapse
Works fine
andikicker said:
Do not wipe the system partition before flashing the ROM. And you should come from a MIUI ROM.
I installed it via the following steps:
- Flash fastboot factory dev ROM 8.11.8 from here: http://www.miui.com/shuaji-393.html (flash_all.sh)
- Validate that the Device boots
- Flash TWRP Recovery "recovery-TWRP-3.2.3-1205-XIAOMI_MIX3-CN-wzsx150.img"
- Reboot and hold volume up until you get into the Recovery menu. Mostly the device will reboot 2 times here.
- Download and push the xiaomi.eu ROM to the device via "adb push xiaomi.eu_multi_MIMix3_8.11.30_v10-9.zip /sdcard/xiaomi.eu_multi_MIMix3_8.11.30_v10-9.zip"
- Flash the zip and reboot
- Enjoy
Click to expand...
Click to collapse
With or without unlocking the bootloader?
Iluminatus23 said:
With or without unlocking the bootloader?
Click to expand...
Click to collapse
unlocked bootloader
i can confirm this works i would wipe data before installing as i causes issues with camera not being able to locate storage to save
Magisk 18 doesnt work, 17.3 is working, SafetyNet check - Success
Adaway - Copying of hosts file failed. Fixed, i am not sure is it because of Magisk/Settings/Systemless hosts, or restart cpl of time. But now its working.
Bluetooth cant find my Amazfit watch.
MGC 6.1.021 MI8 V1d - works perfectly
Those are bugs I am facing after install.
OK Google word is working? Even with screen off?
I get this error
D:\Download\MiMIX3\perseus_images_8.11.8>fastboot getvar product 2>&1 | findstr /r /c:"^product: *perseus" || echo Missmatching image and device
how can i do? it's the first time. image of perseus is correct
mastercut said:
I get this error
D:\Download\MiMIX3\perseus_images_8.11.8>fastboot getvar product 2>&1 | findstr /r /c:"^product: *perseus" || echo Missmatching image and device
how can i do? it's the first time. image of perseus is correct
Click to expand...
Click to collapse
What you trying to do? Install TWRP?
Mackay53 said:
What you trying to do? Install TWRP?
Click to expand...
Click to collapse
No Iwas flashing the fastboot rom 8.11.8
now i'm on stable 10.0.12.0
mastercut said:
No Iwas flashing the fastboot rom 8.11.8
now i'm on stable 10.0.12.0
Click to expand...
Click to collapse
You shouldn't need to flash that, worked fine for me not being on 8.11.8.
Boot TWRP
Wipe data/dalvik
Install EU zip
Factory reset
Reboot
Mackay53 said:
You shouldn't need to flash that, worked fine for me not being on 8.11.8.
Boot TWRP
Wipe data/dalvik
Install EU zip
Factory reset
Reboot
Click to expand...
Click to collapse
cannot boot in recovery
Mackay53 said:
You shouldn't need to flash that, worked fine for me not being on 8.11.8.
Boot TWRP
Wipe data/dalvik
Install EU zip
Factory reset
Reboot
Click to expand...
Click to collapse
what are the diferences to the China rom? Can someone paste few screenshots
Reboot2recovery Version 5.1 LatestFOR VERSION 4.0 check latest reply section.
Hello Nokia G10 and G20 users.
I have created this simple tool which sends your Nokia G10 or G20 to Recovery mode from fastboot mode.
Simply put your phone in fastboot mode and then open this tool and your phone will boot to recovery mode.
Please ensure your have fastboot and adb drivers installed on your computer before using this script ot software.
I'm planning to add more features to this software in future releases.
How to use?
Connect your Nokia Device in Fasboot or any preferred mode using usb to your computer.
Extract the zip given and run the .bat or .exe file.
AppName: Reboot2recovery
Version: 1.0
Platform: Windows 32 and 64 bit
Credits: UI based on 15 seconds adb installer.
{
"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"
}
Here comes the updated 2.0 version with source code!
For source code just open the bat file in any text editor.
Changelog: Version 2.0
-Now you can select how you want to reboot to particular mode.
- Check Connected Nokia Devices.
- ADB to FASTBOOT is added.
- FASTBOOT to Recovery is added.
- ADB to RECOVERY mode added.
Updated script with more options alongwith source code!
For source code just open the bat file in any text editor.
Changelog: Version 3.0
-Option 1 now precisely updated to show mode of connection
-Added option to Exit the script
-Added about and instructions just press "6" and then enter
Version 4 is under development and will come with major design overhaul and more options......
Smooth UI
Changelog: Version 4.0
-Smooth UI
-Optimised Script
Smooth UI
Changelog: Version 5.0
-Smooth UI
-Optimised Script
-Extended Menu View
-Added Support for Android 11 recovery menu for Nokia G10 and G20 devices (thanks to areallydumbperson).
-Added option to check devices in fastboot mode
seems pretty decent i could defo try and make this crossplatform with some libusb tricks and netcore
Hi. I easily entered recovery mode using reboot 2 recovery v5.zip but after rebooting the phone stopped loading into the system. for a moment the android logo appears and then the inscription "no suitable OS"
В fastboot входит Fastboot enters freely, but when exiting it, the same red banner appears: virsit this link on another device to learn more: https: при выходе из него появляется тотже красный баннер:virsit this link on another device to learn more:https ://www.nokia.com/mobille-support user version rollback warning.
leonn46 said:
В fastboot входит Fastboot enters freely, but when exiting it, the same red banner appears: virsit this link on another device to learn more: https: при выходе из него появляется тотже красный баннер:virsit this link on another device to learn more:https ://www.nokia.com/mobille-support user version rollback wa
Click to expand...
Click to collapse
leonn46 said:
В fastboot входит Fastboot enters freely, but when exiting it, the same red banner appears: virsit this link on another device to learn more: https: при выходе из него появляется тотже красный баннер:virsit this link on another device to learn more:https ://www.nokia.com/mobille-support user version rollback warning.
Click to expand...
Click to collapse
What did you do after getting into fastboot mode? This should not cause the issue.
after entering fastboot I connected to my computer and using reboot 2 recovery v5. entered recovery mode. Before that, all attempts to enter recovery mode through v1-v4 were useless. Then I logged in and the phone stopped booting.
leonn46 said:
after entering fastboot I connected to my computer and using reboot 2 recovery v5. entered recovery mode. Before that, all attempts to enter recovery mode through v1-v4 were useless. Then I logged in and the phone stopped booting.
Click to expand...
Click to collapse
Set your phone to fatboot mode and then type fastboot --set-active=b and then type fastboot reboot and then your phone will start.
I have a problem. Phone in fastboot mode. I choose 4 "Fastboot to fastbootd" and nothing happens. Message: "usage: unknow reboot target fastboot". what to do?
shakernow said:
I have a problem. Phone in fastboot mode. I choose 4 "Fastboot to fastbootd" and nothing happens. Message: "usage: unknow reboot target fastboot". what to do?
Click to expand...
Click to collapse
Which phone do you have?
mvikrant97 said:
Which phone do you have?
Click to expand...
Click to collapse
Nokia G10 (ta-1334)
have nokia g20
After using recovery mode v5 this popped up
After using reboot recovery tool v5 thus popped up
Pabalelo said:
After using reboot recovery tool v5 thus popped up
Click to expand...
Click to collapse
Which phone? Nokia G10 or G20.
mvikrant97 said:
Which phone? Nokia G10 or G20.
Click to expand...
Click to collapse
Nokia G10
Pabalelo said:
After using reboot recovery tool v5 thus popped up
Click to expand...
Click to collapse
Hello guys, I recently tried to Downgrade the Moto g30, but something went wrong, the screen was all black, the cell phone does not load, but it recognizes on the computer as Qualcomm HS-USB QDLoader 9008, I already downloaded the drivers from Motorola and Qualcomm, I downloaded BlankFlash and tried to make it go back to normal or when I do fastboot devices the cell phone does not recognize and perform the commands. I already downloaded the drivers but it still isn't going please I ask someone to help me.
{
"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"
}
My guess is that your phone isn't hard bricked but soft bricked:
When the phone has gone through problematic conditions such that it quits the detection of USB, charging and everything that you provide to it then the phone is unfortunately hard bricked.
A soft brick is something that occurs when you perform a dirty flashing, will say if you flash any ROM on your device without doing the factory reset. Or else if you flashed a ROM which was not made for your phone.
This is incredibly suspicious, my Moto G30 ceased to work yesterday as well. I found this discussion about Pixel 3 phones failing en masse, with similar symptoms. I'm still prodding the phone with whatever tools I can find, but I probably will try to get it back to the carrier to get it replaced.
Are you sure you flashed your channel Stock ROM?
I think that was it... Well, try to make Blank Flash with the file that I leave attached to this comment.
Instructions: Please press Volume Down and power on at the same time for 10 seconds, then connect to PC and run blank flash. Just in case it's the .bat file
Sammm77 said:
Are you sure you flashed your channel Stock ROM?
I think that was it... Well, try to make Blank Flash with the file that I leave attached to this comment.
Instructions: Please press Volume Down and power on at the same time for 10 seconds, then connect to PC and run blank flash. Just in case it's the .bat file
Click to expand...
Click to collapse
THANK YOU SOU MUCH REALLY THANK´S
Sammm77 said:
Are you sure you flashed your channel Stock ROM?
I think that was it... Well, try to make Blank Flash with the file that I leave attached to this comment.
Instructions: Please press Volume Down and power on at the same time for 10 seconds, then connect to PC and run blank flash. Just in case it's the .bat file
Click to expand...
Click to collapse
Hello good morning I managed to pass blank flash correctly, but I can't pass any rom, I always have the message (bootloader) permission denied ,and in the lenovo program in 50% of the single partition fastboot flash, flash failed, it was like this after dongrade android 12 to 11 was working normally on 11 until I lock the bootloader it doesn't start anymore it just stays on the image screen if you can help
juninhovam said:
Hello good morning I managed to pass blank flash correctly, but I can't pass any rom, I always have the message (bootloader) permission denied ,and in the lenovo program in 50% of the single partition fastboot flash, flash failed, it was like this after dongrade android 12 to 11 was working normally on 11 until I lock the bootloader it doesn't start anymore it just stays on the image screen if you can help
Click to expand...
Click to collapse
Do you have unlocked bootloader?
Sammm77 said:
Do you have unlocked bootloader?
Click to expand...
Click to collapse
yes, I installed android 11 but I blocked the bootloader that's where my problems started, at the moment the bootloader is blocked
juninhovam said:
yes, I installed android 11 but I blocked the bootloader that's where my problems started, at the moment the bootloader is blocked
Click to expand...
Click to collapse
Write to my Telegram
@Samw622
I'll help you better there
Hello
Sammm77The same for me. I try to downgrade from android 12 to android 11 but someting worked wrong. Right now I have no android installed and now my moto g30 start with fastboot. I can access recovery mode but I can`t access my phone to flash. Right now flash is locked and I don`t know how to activate the usb debbuging to access my phone on my computer to flash it. Any help please...
This is what I have now. And I try to
find a way to unlock usb debugging and set OEM unlocking. After that I presume I can reinstall android OS.
CristianPN said:
This is what I have now. And I try to View attachment 5584115find a way to unlock usb debugging and set OEM unlocking. After that I presume I can reinstall android OS.
Click to expand...
Click to collapse
I think you just killed your Moto g30. It can be recovered, but I have no idea how... :/
CristianPN said:
Isto é o que tenho agora. E eu tento View attachment 5584115encontrar uma maneira de desbloquear a depuração USB e definir o desbloqueio OEM. Depois disso, presumo que posso reinstalar o sistema operacional Android.
Click to expand...
Click to collapse
CristianPN said:
Isto é o que tenho agora. E eu tento View attachment 5584115encontrar uma maneira de desbloquear a depuração USB e definir o desbloqueio OEM. Depois disso, presumo que posso reinstalar o sistema operacional Android.
Click to expand...
Click to collapse
Como conseguio o desbloqueio do OEM
Sammm77 said:
I think you just killed your Moto g30. It can be recovered, but I have no idea how... :/
Click to expand...
Click to collapse
Hey Sam do you have discord i bricked mine while trying to root it
TwinCamTurbo said:
Hey Sam do you have discord i bricked mine while trying to root it
Click to expand...
Click to collapse
sure, i'm happy helping u
t.me/Samw622
only if it is brick, hard brick, soft brick. I DO NOT HAVE SUPPORT FOR OEM LOCK
Sammm77 said:
sure, i'm happy helping u
t.me/Samw622
only if it is brick, hard brick, soft brick. I DO NOT HAVE SUPPORT FOR OEM LOCK
Click to expand...
Click to collapse
i am getting no valid operating system found error while installing stock firmware , please help bro
juninhovam said:
Hello good morning I managed to pass blank flash correctly, but I can't pass any rom, I always have the message (bootloader) permission denied ,and in the lenovo program in 50% of the single partition fastboot flash, flash failed, it was like this after dongrade android 12 to 11 was working normally on 11 until I lock the bootloader it doesn't start anymore it just stays on the image screen if you can help
Click to expand...
Click to collapse
most of programmer files with blank flash are locked and not allow system and boot.img flashing, try with qfil if works, otherwise jtag or try to find a similar lenovo phone (if exist) and use programmer from that
juninhovam said:
Hello good morning I managed to pass blank flash correctly, but I can't pass any rom, I always have the message (bootloader) permission denied ,and in the lenovo program in 50% of the single partition fastboot flash, flash failed, it was like this after dongrade android 12 to 11 was working normally on 11 until I lock the bootloader it doesn't start anymore it just stays on the image screen if you can help
Click to expand...
Click to collapse
hey! bro i have the same problem as you. did you find any way to correct it.Please help am also stuck there.
jack_little_london said:
hey! bro i have the same problem as you. did you find any way to correct it.Please help am also stuck there.
Click to expand...
Click to collapse
unfortunately there is no repair brother only via box or sending the device to lenovo
{
"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"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/12.1/README.mkdn
Flashing Instructions:
Pre-installation:
TWRP (Download from here)
gapps (Download from here)
First time installation:
Flash ofox (after installing the rom, flash crDroid recovery)
Wipe data, caches, system and vendor
Flash the ROM zip either from adb sideload or internal storage
Reboot in to recovery
Format data
Flash GApps (If wanted)
Reboot and enjoy!
Update installation:
Reboot to recovery
Flash the ROM in twrp or use adb sideload
Reboot and enjoy!
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/crdroidandroid/android_kernel_motorola_msm8953-2
Download:
ROM AHANNAH https://sourceforge.net/projects/cr...droid-12.1-20220901-ahannah-v8.8.zip/download
ROM RHANNAH
https://sourceforge.net/projects/crdroid/files/rhannah/8.x/crDroidAndroid-12.1-20220902-rhannah-v8.8.zip/download
Known issues:
- You Tell Me
Visit official website @ crDroid.net
crDroid Community Telegram
crDroid Updates Channel
Donate to help our team pay server costs
@SH4ND
My device is Moto E5 Plus XT1924-7 which I believe is the hannah varient...
Will this Rom work on hannah? If so which version should I use?
Ahannah or Rhannah
bigjoncoop said:
@SH4ND
My device is Moto E5 Plus XT1924-7 which I believe is the hannah varient...
Will this Rom work on hannah? If so which version should I use?
Ahannah or Rhannah
Click to expand...
Click to collapse
no, only rhannah and ahannah are stable in 4.9 kernel, audio is dead in hannah
Thank you very much for this ROM. On official LineageOS I had freezes, random reboots and other issues that don't exist in this ROM. It's perfect on my Rhannah XT1924-4.
A warning for anyone installing this ROM is that after flashing ROM and Gapps do not restart on OrangeFox because the ROM is encrypted and recovery cannot read data. When I did that, it stuck on the OrangeFox home screen and to exit it, I had to press the 3 buttons on the device to enter fastboot mode and restart. Instead install the official crDroid recovery with ADB to avoid this problem.
Ex novo said:
Muito obrigado por esta ROM. No LineageOS oficial, tive congelamentos, reinicializações aleatórias e outros problemas que não existem nesta ROM. É perfeito no meu Rhannah XT1924-4.
Um aviso para quem está instalando esta ROM é que, depois de piscar a ROM e os Gapps, não reinicie no OrangeFox porque a ROM é criptografada e a recuperação não pode ler os dados. Quando fiz isso, ele travou na tela inicial do OrangeFox e, para sair, tive que pressionar os 3 botões do aparelho para entrar no modo fastboot e reiniciar. Em vez disso, instale a recuperação oficial do crDroid com o ADB para evitar esse problema.
Click to expand...
Click to collapse
eexactly my friend, thanks for the support, Android 13 is almost ready, and no bugs, only problem is encryption
I can't get this ROM to boot on my rhannah XT-1924-1 device. I followed the flashing instructions to the letter, including rebooting the recovery and formatting data after flashing the ZIP. It doesn't even get to showing the Motorola logo, just goes into an infinite loop of showing 'N/A' in the top left corner (which this phone always shows if the bootloader is unlocked).
The OrangeFox recovery is also unable to start unless the userdata partition is formatted as EXT4. The "format data" operation in both TWRP and OrangeFox makes an F2FS partition, and the only way to get out of that bootloop is flashing the latest Lineage Recovery (TWRP also can't start with F2FS in userdata) and manually reformat the partition with `mkfs.ext4 /dev/block/by-name/userdata`
The ROM and the recovery image included in the ZIP is still unable to get past the 'N/A' screen though, even with EXT4 formatted userdata.
Any clues on what could be causing this?
OvenCrate said:
I can't get this ROM to boot on my rhannah XT-1924-1 device. I followed the flashing instructions to the letter, including rebooting the recovery and formatting data after flashing the ZIP. It doesn't even get to showing the Motorola logo, just goes into an infinite loop of showing 'N/A' in the top left corner (which this phone always shows if the bootloader is unlocked).
The OrangeFox recovery is also unable to start unless the userdata partition is formatted as EXT4. The "format data" operation in both TWRP and OrangeFox makes an F2FS partition, and the only way to get out of that bootloop is flashing the latest Lineage Recovery (TWRP also can't start with F2FS in userdata) and manually reformat the partition with `mkfs.ext4 /dev/block/by-name/userdata`
The ROM and the recovery image included in the ZIP is still unable to get past the 'N/A' screen though, even with EXT4 formatted userdata.
Any clues on what could be causing this?
Click to expand...
Click to collapse
for some reason we don't know, some versions don't work kernel 4.9, is your rhannah china version?
OvenCrate said:
I can't get this ROM to boot on my rhannah XT-1924-1 device. I followed the flashing instructions to the letter, including rebooting the recovery and formatting data after flashing the ZIP. It doesn't even get to showing the Motorola logo, just goes into an infinite loop of showing 'N/A' in the top left corner (which this phone always shows if the bootloader is unlocked).
The OrangeFox recovery is also unable to start unless the userdata partition is formatted as EXT4. The "format data" operation in both TWRP and OrangeFox makes an F2FS partition, and the only way to get out of that bootloop is flashing the latest Lineage Recovery (TWRP also can't start with F2FS in userdata) and manually reformat the partition with `mkfs.ext4 /dev/block/by-name/userdata`
The ROM and the recovery image included in the ZIP is still unable to get past the 'N/A' screen though, even with EXT4 formatted userdata.
Any clues on what could be causing this?
Click to expand...
Click to collapse
Try to update fw to last fw
It's not (supposed to be) China version, I bought it from a carrier in EU (Hungary).
My firmware version is OPPS27.91-179 as far as I can tell, and the only newer-looking one that I could find is OPPS27.91-179-8-5. Should I try that?
OvenCrate said:
It's not (supposed to be) China version, I bought it from a carrier in EU (Hungary).
My firmware version is OPPS27.91-179 as far as I can tell, and the only newer-looking one that I could find is OPPS27.91-179-8-5. Should I try that?
Click to expand...
Click to collapse
Yes
SH4ND said:
for some reason we don't know, some versions don't work kernel 4.9, is your rhannah china version?
Click to expand...
Click to collapse
I bought it from T-Mobile in Hungary (EU), so I don't think it's China version
FPSensor said:
Try to update fw to last fw
Click to expand...
Click to collapse
I'm on firmware OPPS27.91-179 and the only newer-looking one I could find is OPPS27.91-179-8-5. Should I try that?
OvenCrate said:
Comprei na T-Mobile na Hungria (UE), então não acho que seja a versão chinesa
Estou no firmware OPPS27.91-179 e o único com aparência mais recente que encontrei é o OPPS27.91-179-8-5. Devo tentar isso?
Click to expand...
Click to collapse
https://t.me/+kNkSQnjKXMEzNGNh join to improve communication
SH4ND said:
https://t.me/+kNkSQnjKXMEzNGNh join to improve communication
Click to expand...
Click to collapse
I will, as soon as I can get something to boot on my phone so I can use Telegram
SH4ND said:
https://t.me/+kNkSQnjKXMEzNGNh join to improve communication
Click to expand...
Click to collapse
Soon admins ban u xd
FPSensor said:
Em breve os administradores banem vc xd
Click to expand...
Click to collapse
🫠
Well, all I achieved by flashing the OPPS27.91-179-8-5 was losing modem functionality, including IMEI. Fortunately I've made a full blockwise backup, so I was able to revert.
The ROM still didn't boot after installing it over the newer firmware.
Update: Lenovo Rescue and Smart Assistant managed to save my brick, and got me up to OPPS27.91_179-8-16. The radio still refused to work with the stock rom, but LineageOS 18.1 can use it.
crDroid 8.10 still doesn't even start to boot though. Maybe kernel 4.9 hates XT1924-1 for some reason...
OvenCrate said:
Update: Lenovo Rescue and Smart Assistant managed to save my brick, and got me up to OPPS27.91_179-8-16. The radio still refused to work with the stock rom, but LineageOS 18.1 can use it.
crDroid 8.10 still doesn't even start to boot though. Maybe kernel 4.9 hates XT1924-1 for some reason...
Click to expand...
Click to collapse
true, send pstore [sys/fs/pstore]
FPSensor said:
true, send pstore [sys/fs/pstore]
Click to expand...
Click to collapse
In the LineageOS 18.1 build that I currently have running, /sys/fs/pstore contains a single file called 'annotate-ramoops-0' which has zero size
OvenCrate said:
In the LineageOS 18.1 build that I currently have running, /sys/fs/pstore contains a single file called 'annotate-ramoops-0' which has zero size
Click to expand...
Click to collapse
Ok but this post it's about crDroid lol