OPX - No Access to Recovery or Bootloader. OOS 2.2.3 Booting normally. - OnePlus X Q&A, Help & Troubleshooting

I am on OOS 2.2.3 on my Oneplus X. Rooted with Twrp recovery. Was not able to flash the new and official OOS 3.1.3 zip file through TWRP, so flashed Blue_spark TWRP in recovery mode (read somewhere that it could have enabled me to flash OOS 3.1.3). Now the phone boots into OOS 2.2.3 normally, but I cant boot into recovery or bootloader and it gets stuck at the logo screen in both these modes.
Could someone please help me out with this?

Shalabh21 said:
I am on OOS 2.2.3 on my Oneplus X. Rooted with Twrp recovery. Was not able to flash the new and official OOS 3.1.3 zip file through TWRP, so flashed Blue_spark TWRP in recovery mode (read somewhere that it could have enabled me to flash OOS 3.1.3). Now the phone boots into OOS 2.2.3 normally, but I cant boot into recovery or bootloader and it gets stuck at the logo screen in both these modes.
Could someone please help me out with this?
Click to expand...
Click to collapse
As a result of this, I am not even able to do a manual factory reset from the setting menu in OOS 2.2.3, because when i try to initiate this the phone again gets stuck at the logo screen of recovery mode.

Shalabh21 said:
I am on OOS 2.2.3 on my Oneplus X. Rooted with Twrp recovery. Was not able to flash the new and official OOS 3.1.3 zip file through TWRP, so flashed Blue_spark TWRP in recovery mode (read somewhere that it could have enabled me to flash OOS 3.1.3). Now the phone boots into OOS 2.2.3 normally, but I cant boot into recovery or bootloader and it gets stuck at the logo screen in both these modes.
Could someone please help me out with this?
Click to expand...
Click to collapse
blu.spark TWRP v41 uses the updated Marshmallow bootloader from OOS3.1.3, and you are on the Lollipop bootloader.
Lollipop Bootloader recovery won't boot on Marshmallow bootloader and Marshmallow bootloader recovery won't boot on Lollipop bootloader.
If you wanna flash the 3.1.3 zip, then use these instructions.
Download Oxygen OS 3.1.3 full ROM
Download MM based unofficial TWRP
Downloaded Modded SuperSU if you want root
You will require a PC with WinRAR & Notepad++, because as we are running custom ROMs the zip will give an error 7 saying that The package is for OnePlus, this is an onyx, we need to remove that.
Don't worry, its super easy.
- Download the OOS3 zip, copy it to your PCs desktop
- Open it with winRAR, dont extract it, just open it
- There will be a META-INF folder, open it
- Then open com, then google, then android, there will be 2 files here, updater-binary & updater script
- Double click on updater-script
- It will ask which app to use to open the file, then select to open with Notepad++ (designate it from its installed directory if it isn't visible in the initial list)
- The file will look like this
{
"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"
}
- Delete the entire first line that starts with getprop
- Now it should look like this
- Now press Ctrl+S to save the file and close the window
- WinRAR will ask weather to update changes in the archive, say yes to that
- Let it finish its job
- Done !
Moving on to the flashing now...
Assuming you on OOS2.2.3, goto settings, enable Advanced Reboot.
Then reboot to bootloader, this is fastboot mode.
Flash this recovery.
Done, now...
- Copy the modded OOS3 zip into your Device
- Boot into TWRP recovery
- Wipe system, data, cache & dalvik/art cache
- Flash the modified OOS3 zip
- Let it complete
- After it completes, press the wipe cache/dalvik button below
- Now reboot to system
- Complete the initial setup
- Goto settings, unlock developer options by tapping 7 times on build number in about phone
- Enable advanced reboot
- Then reboot to bootloader
- Flash the MM based unofficial TWRP via fastboot
- Remember to boot into this newly flash TWRP before booting into system so that it doesn't overwite it
- Done
Now you are on OOS 3.1.3, and have a working TWRP, you can proceed to flash SuperSU etc to gain root

Joshwin Aranha said:
blu.spark TWRP v41 uses the updated Marshmallow bootloader from OOS3.1.3, and you are on the Lollipop bootloader.
Lollipop Bootloader recovery won't boot on Marshmallow bootloader and Marshmallow bootloader recovery won't boot on Lollipop bootloader.
If you wanna flash the 3.1.3 zip, then use these instructions.
Download Oxygen OS 3.1.3 full ROM
Download MM based unofficial TWRP
Downloaded Modded SuperSU if you want root
You will require a PC with WinRAR & Notepad++, because as we are running custom ROMs the zip will give an error 7 saying that The package is for OnePlus, this is an onyx, we need to remove that.
Don't worry, its super easy.
- Download the OOS3 zip, copy it to your PCs desktop
- Open it with winRAR, dont extract it, just open it
- There will be a META-INF folder, open it
- Then open com, then google, then android, there will be 2 files here, updater-binary & updater script
- Double click on updater-script
- It will ask which app to use to open the file, then select to open with Notepad++ (designate it from its installed directory if it isn't visible in the initial list)
- The file will look like this
- Delete the entire first line that starts with getprop
- Now it should look like this
- Now press Ctrl+S to save the file and close the window
- WinRAR will ask weather to update changes in the archive, say yes to that
- Let it finish its job
- Done !
Moving on to the flashing now...
Assuming you on OOS2.2.3, goto settings, enable Advanced Reboot.
Then reboot to bootloader, this is fastboot mode.
Flash this recovery.
Done, now...
- Copy the modded OOS3 zip into your Device
- Boot into TWRP recovery
- Wipe system, data, cache & dalvik/art cache
- Flash the modified OOS3 zip
- Let it complete
- After it completes, press the wipe cache/dalvik button below
- Now reboot to system
- Complete the initial setup
- Goto settings, unlock developer options by tapping 7 times on build number in about phone
- Enable advanced reboot
- Then reboot to bootloader
- Flash the MM based unofficial TWRP via fastboot
- Remember to boot into this newly flash TWRP before booting into system so that it doesn't overwite it
- Done
Now you are on OOS 3.1.3, and have a working TWRP, you can proceed to flash SuperSU etc to gain root
Click to expand...
Click to collapse
Thank you very much Joshwin Aranha. This worked like a charm.
However I modified the last step and flashed OOS recovery instead. Want to use the phone without root for a while, because the main reason I rooted it in the first place was to install Greenify and save battery (battery used to drain heavily in OOS 2.2.2 and all prior versions), but unfortunately it did not have a great impact on battery life. So going back to stock version for now.

Shalabh21 said:
Thank you very much Joshwin Aranha. This worked like a charm.
However I modified the last step and flashed OOS recovery instead. Want to use the phone without root for a while, because the main reason I rooted it in the first place was to install Greenify and save battery (battery used to drain heavily in OOS 2.2.2 and all prior versions), but unfortunately it did not have a great impact on battery life. So going back to stock version for now.
Click to expand...
Click to collapse
Whatever rocks your boat buddy, glad you sorted that out.

OPX stuck at oneplus logo after following the procedure
@Joshwin Aranha
Hi, I followed the exact same procedure you mentioned, and the process goes smoothly. But when i reboot the phone is stuck at oneplus logo (when i check through my PC for the status it says it is in fastboot mode).
I can easily flash OOS 2.2.3 and move to lollipop , but the problem occurs in OOS 3.1.3 MM
P.S. - i am not rooted.

hbansal24x7 said:
@Joshwin Aranha
Hi, I followed the exact same procedure you mentioned, and the process goes smoothly. But when i reboot the phone is stuck at oneplus logo (when i check through my PC for the status it says it is in fastboot mode).
I can easily flash OOS 2.2.3 and move to lollipop , but the problem occurs in OOS 3.1.3 MM
P.S. - i am not rooted.
Click to expand...
Click to collapse
Which recovery did you use to flash OOS3 ? And did you properly wipe everything ? Try re-flashing.

Joshwin Aranha said:
Which recovery did you use to flash OOS3 ? And did you properly wipe everything ? Try re-flashing.
Click to expand...
Click to collapse
I have used official TWRP that you mentioned in the procedure. I can easily flash CM13 and get my phone running. The problem is only coming in flashing OOS 3.1.3 after OOS 2.2.3.
And yes i have tried it multiple times. With factory reset, user data erase . Everything.
One quirk which i faced 1 time was that while flashing OOS 3 via official twrp 3.0.2.0 , during system verification stage i got an error "system partition has unexpected contents". I cleaned dalvik/cache/data and the error went away but the problem still persists

hbansal24x7 said:
I have used official TWRP that you mentioned in the procedure. I can easily flash CM13 and get my phone running. The problem is only coming in flashing OOS 3.1.3 after OOS 2.2.3.
And yes i have tried it multiple times. With factory reset, user data erase . Everything.
One quirk which i faced 1 time was that while flashing OOS 3 via official twrp 3.0.2.0 , during system verification stage i got an error "system partition has unexpected contents". I cleaned dalvik/cache/data and the error went away but the problem still persists
Click to expand...
Click to collapse
Does the OOS3 zip give any errors ? Or flashes properly ? This seems like a peculiar issue nonetheless..

Joshwin Aranha said:
Does the OOS3 zip give any errors ? Or flashes properly ? This seems like a peculiar issue nonetheless..
Click to expand...
Click to collapse
It does flash properly when i try to flash from OOS 2.2.3->3.1.3 . What i have observed is that as soon as the phone starts it gets stuck on oneplus logo without "android" written below. When i plug it into my system and check the device, it responds to "fastboot devices". I guess there is some issue with the bootloader or something

hbansal24x7 said:
It does flash properly when i try to flash from OOS 2.2.3->3.1.3 . What i have observed is that as soon as the phone starts it gets stuck on oneplus logo without "android" written below. When i plug it into my system and check the device, it responds to "fastboot devices". I guess there is some issue with the bootloader or something
Click to expand...
Click to collapse
Very the md5 of the OOS3 zip to check for a corrupted download.
Original md5 is 162f12d4dfef0142a184e761da868c5f

Joshwin Aranha said:
Very the md5 of the OOS3 zip to check for a corrupted download.
Original md5 is 162f12d4dfef0142a184e761da868c5f
Click to expand...
Click to collapse
MD5 is the same for UNCHANGED zip. i guess md5 will differ on a modified zip due to the changes you mentioned in the process.

Related

[RECOVERY][ROOT][TWRP 3.2.1-1][Magisk v14] Samsung Galaxy Tab A6 SM-T280/SM-T285

{
"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"
}
TWRP custom recovery for the Tab A SM-T280/T285. Latest build is 3.2.1-1
Disclaimer: you flash these at your own risk. Knox counter will be tripped. Having the stock firmware to hand is also advised.
NOTE: BEFORE MAKING MODIFICATIONS, ON SOME ANDROID 5.1.1/6.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
UPDATE 08/01/2018 - TWRP updated to version 3.2.1-1
UPDATE 21/11/2017 - Magisk updated to v14
UPDATE 26/10/2016: GUI lag fix - Lag in the GUI should now be fixed
MTP fix - MTP should now be working
To install TWRP:
1. Flash with ODIN 3.10.7 in the AP slot.
Uncheck Auto reboot.
2. Load the respective file below into the AP slot and hit start.
3. After flashing when ODIN says PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
You should now see TWRP recovery.
DOWNLOAD:
TWRP_3.0.2-1_SM-T280_261016
twrp_3.2.1-1_sm-t280_080118
twrp_3.2.1-1_sm-t285_080118
NOTE: at the moment there seems to be a bug which causes the GUI to get a little laggy. If things stop responding just be patient and wait for the GUI to respond. I'm looking into this. (FIXED)
For Systemless Root with SuperSu.
1. Install Supersu via TWRP
SR1-SuperSU-v2.78-SR1-20160915123031
This step only required for the SM-T280
2 . Flash the PRE-ROOTED boot image below with ODIN(AP slot) or TWRP(extract boot.img first from tar file). Current version is [SR1-SuperSU-v2.78-SR1-20160915123031].
supersu_2.78_SR1_systemless_boot_t280
3. Reboot
4. Check you have root
To install Magisk v14:
1. Download Magisk v14 to your device
Magisk v14
2. Install the Magisk v14 zip with TWRP
This step only required for the T280
3. Flash the patched boot image below with TWRP.
magiskv14_boot_aqd1
4. Reboot
5. Install Magisk manager
Magisk Manager
PLEASE LEAVE FEEDBACK IF YOU FIND MY WORK USEFUL. THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
GUI lag fix - Lag in the GUI should now be fixed
MTP fix
Help me root my phone
Sent from my SM-G903W using XDA Free mobile app
ashyx said:
GUI lag fix - Lag in the GUI should now be fixed
MTP fix
Click to expand...
Click to collapse
interesting, what caused the lag to happen? I initially suspected it to be gpu clock throttling but didn't have time to figure it out
jedld said:
interesting, what caused the lag to happen? I initially suspected it to be gpu clock throttling but didn't have time to figure it out
Click to expand...
Click to collapse
Hi Jed, after trying various different configs in twrp and even modifying the graphics source code it made no difference.
Using the the touch debugger in twrp it was apparent that the touch was responding fine.
So I turned my attention to the kernel.
After several builds of modifying the cpu config making no difference, it turns out TWRP only supports double buffering, but the kernel was forcing triple buffering.
It seems this was causing an extra frame to be displayed causing what seemed like lag and explains why when pressing the screen a second time would cause the frame to update.
The page that was in ram had changed when tapping a button, but the wrong frame in the buffer was displayed until the next touch which then updated the display.
Disabling triple buffering in the kernel fixed the issue.
jaritico said:
PRE-ROOTED boot image can be used on 285? (needed for Systemless Root ) same at magisk patched boot
Click to expand...
Click to collapse
You don't need it for the T285.
Worked perfectly, first time.
Installed supersu via trwp and then img via boot in twrp also.
Thank you for the clear tutorial.
Excellent
just about to root mine now are there any custom roms that can go on it?
ashyx said:
TWRP custom recovery for the Tab A SM-T280. Latest build is 3.0.2-1
Disclaimer: you flash these at your own risk. Knox counter will be tripped. Having the stock firmware to hand is also advised.
NOTE: BEFORE MAKING MODIFICATIONS, ON SOME ANDROID 5.1.1/6.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
UPDATE 26/10/2016: GUI lag fix - Lag in the GUI should now be fixed
MTP fix - MTP should now be working
To install TWRP:
1. Flash with ODIN 3.10.7 in the AP slot.
Uncheck Auto reboot.
2. Load the respective file below into the AP slot and hit start.
3. After flashing when ODIN says PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
You should now see TWRP recovery.
TWRP_3.0.2-1_SM-T280_261016
NOTE: at the moment there seems to be a bug which causes the GUI to get a little laggy. If things stop responding just be patient and wait for the GUI to respond. I'm looking into this.
For Systemless Root with SuperSu.
1. Install Supersu via TWRP
SR1-SuperSU-v2.78-SR1-20160915123031
2 . Flash the PRE-ROOTED boot image below with ODIN(AP slot) or TWRP(extract boot.img first from tar file). Current version is [SR1-SuperSU-v2.78-SR1-20160915123031].
supersu_2.78_SR1_systemless_boot_t280
3. Reboot
4. Check you have root
To install Magisk v7:
1. Download Magisk v7 to your device
Magisk v7
2. Install the Magisk v7 zip with TWRP
3. Flash the patched boot image below with ODIN(AP slot) or TWRP(extract boot.img first from tar file)
magiskv7_boot_sm-t280
4. Reboot
To Install Magisk v7 with SuperSu:
1. Follow the instructions above to install SuperSu
2. Reboot to TWRP and install the Magisk v7 zip below:
Magisk v7
3. Flash the patched boot image below with ODIN(AP slot) or TWRP(extract boot.img first from tar file):
magiskv7_boot_sm-t280
4. Reboot
5. Install Magisk Manager
PLEASE LEAVE FEEDBACK IF YOU FIND MY WORK USEFUL. THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
Click to expand...
Click to collapse
I don't know how this is working for others, but installing SuperSu uninstalled android.
Ethan-56 said:
I don't know how this is working for others, but installing SuperSu uninstalled android.
Click to expand...
Click to collapse
It does what? [emoji55]
Also please don't quote the entire OP.
ashyx said:
It does what? [emoji55]
Also please don't quote the entire OP.
Click to expand...
Click to collapse
OK, I'm new to XDA. I installed TWRP and supersu, but when switching to Odin to install that other supersu thing, It wouldn't boot properly I tried deleting supersu, but I uninstalled android entirely. I got the splash screen, but TWRP warned that there was no OS installed. Does XDA Developers have a tutorial on reinstalling Android? I also can't locate the stock firmware and I forgot to back up my system.
Download the stock firmware from sammobile or UPDATO and flash with odin.
T280 comes in on Tuesday, will try this method and report back. Seems fairly easy, thanks for allowing us to have TWRP and root, it will help in debloating this 8gb version i picked up.
Any suggestion how to install Magisk v9?
Root done in five minutes, I can't believe!
Thanks ashyx!
What Gives???
magiskv7_boot_sm-t280 in first post Failed to download, registered in Microsoft Security as a Trojan! Also download page in Android file host has the developer name as "ashyt6" and not "ashyx."
Anyone else noticed this, or did I miss something???
gello924 said:
magiskv7_boot_sm-t280 in first post Failed to download, registered in Microsoft Security as a Trojan! Also download page in Android file host has the developer name as "ashyt6" and not "ashyx."
Anyone else noticed this, or did I miss something???
Click to expand...
Click to collapse
Ffs have you never heard of false positives? [emoji55] What do you expect you're installing files that compromise an operating system.
Also what relevance is it that my AFH user name is different?
ashyx said:
TWRP custom recovery for the Tab A SM-T280. Latest build is 3.0.2-1
Disclaimer: you flash these at your own risk. Knox counter will be tripped. Having the stock firmware to hand is also advised.
NOTE: BEFORE MAKING MODIFICATIONS, ON SOME ANDROID 5.1.1/6.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
UPDATE 26/10/2016: GUI lag fix - Lag in the GUI should now be fixed
MTP fix - MTP should now be working
To install TWRP:
1. Flash with ODIN 3.10.7 in the AP slot.
Uncheck Auto reboot.
2. Load the respective file below into the AP slot and hit start.
3. After flashing when ODIN says PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
You should now see TWRP recovery.
TWRP_3.0.2-1_SM-T280_261016
NOTE: at the moment there seems to be a bug which causes the GUI to get a little laggy. If things stop responding just be patient and wait for the GUI to respond. I'm looking into this.
For Systemless Root with SuperSu.
1. Install Supersu via TWRP
SR1-SuperSU-v2.78-SR1-20160915123031
2 . Flash the PRE-ROOTED boot image below with ODIN(AP slot) or TWRP(extract boot.img first from tar file). Current version is [SR1-SuperSU-v2.78-SR1-20160915123031].
supersu_2.78_SR1_systemless_boot_t280
3. Reboot
4. Check you have root
To install Magisk v7:
1. Download Magisk v7 to your device
Magisk v7
2. Install the Magisk v7 zip with TWRP
3. Flash the patched boot image below with ODIN(AP slot) or TWRP(extract boot.img first from tar file)
magiskv7_boot_sm-t280
4. Reboot
To Install Magisk v7 with SuperSu:
1. Follow the instructions above to install SuperSu
2. Reboot to TWRP and install the Magisk v7 zip below:
Magisk v7
3. Flash the patched boot image below with ODIN(AP slot) or TWRP(extract boot.img first from tar file):
magiskv7_boot_sm-t280
4. Reboot
5. Install Magisk Manager
PLEASE LEAVE FEEDBACK IF YOU FIND MY WORK USEFUL. THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
Click to expand...
Click to collapse
followed your instruction & it works, many thanks..much appreciated:good::good::good:
Hi ashyx
To start sorry for my English, I am French and a bad student.
I want to thank you for this guide and all of your contribution on the Android scene :good:
I followed your instructions successfully but I have some questions
Can I install Busybox? If so, is it useful? If yes, how?
I have to do update Magisk v7 to v9?
To finish what is the best solution to extend the internal memory? Actually I used Link2Sd but I'm not satisfied
Thanks again for your work, a little boy will be in the angels when he will receive his gift of Christmas
Error - Security check (boot)
While odin is telling me everything it's correct and shows PASS message on my tablet Sm-t280 shows Security check fail - (boot) and when i restart i can't see any changes,
Oem unlocked and usb debug activated i tried flash with twrp image file and with supersu img file.
I hope your help thanks

[GUIDE][RECOVERY][ROOT] Install TWRP and Root (Magisk) Lenovo Z5 Pro GT [L78032]

How to Install TWRP:
Note: that version is UNOFFICIAL TWRP-3.3.0-0524
.Pre-Requirements
ADB means Android Debug Bridge, and it is software that you should always do have installed on your PC.
Pre-Requisite 1
Make sure that you have the drivers for your phone installed on your PC.
If not, you can download and install them from here https://devsjournal.com/usb-drivers-...d-devices.html
Pre-Requisite 2
You must also install: Minimal ADB & Fastboot, you can download the software
from here https://devsjournal.com/download-min...boot-tool.html
Pre-Requisite 3
Your device needs this with unlocked bootloader
if it is not unlocked do the tutorial to unlock HERE
Pre-Requisite 4
Make sure you have enabled 'USB Debugging' and OEM Unlocking on your device
Settings -> Advanced settings -> Developer Options
PAY ATTENTION: If you do not see the Developer Options menu you need to do this:
Settings -> Device Info -> tap 6 or 7 times on the 'ZUI version' entry
A pop-up should appear, telling you 'now you are a developer'
------------------------------------------------
1) Download TWRP: recovery-TWRP-3.3.0-0524-LENOVO_Z5PRO_GT-CN-wzsx150.img
2) After getting the TWRP file put it in the same ADB folder
3) Now start the phone in bootlader by doing this:
Connect the phone to the PC
Start the Minimal ADB & Fastboot program from the PC
On the PC screen, type:
adb reboot bootloader
(A request may appear on the phone screen with permission of USB debugging, accept it)
The phone will now restart in Bootloader mode.
4) Now that you are in bootloader mode, from the PC, from the screen
Minimal ADB and Fastboot type:
fastboot flash recovery recovery-TWRP-3.3.0-0524-LENOVO_Z5PRO_GT-CN-wzsx150.img
Sending 'recovery' (98304 KB) OKAY [ 5.970s]
Writing 'recovery' OKAY [ 0.539s]
Done !
---------
.How to Install Root Magisk:
{
"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"
}
Done !
Credits:
Maker: wzsx150
Developer Team: LR.Team
Is there any issues related to this recovery?
firemax13 said:
Is there any issues related to this recovery?
Click to expand...
Click to collapse
I had no problem with this recovery
My device was unlocked by vendor. I'm unable to boot into twrp to root my device. The flashing is successful but it will only boot in a simple recovery where I can only install an "update.zip".
Have tried this https://forum.xda-developers.com/z5...-guide-lenovo-z5-pro-gt-t3915945#post81055547 but the problem remains.
Hope anyone can help. I need to root my device. Thanks
BlueIce84 said:
My device was unlocked by vendor. I'm unable to boot into twrp to root my device. The flashing is successful but it will only boot in a simple recovery where I can only install an "update.zip".
Have tried this https://forum.xda-developers.com/z5...-guide-lenovo-z5-pro-gt-t3915945#post81055547 but the problem remains.
Hope anyone can help. I need to root my device. Thanks
Click to expand...
Click to collapse
Have the same scenario as you but I haven't done the tutorial yet as I read your post and I got concerned. Have you fix you issue? Is it safe to do this tutorial?
No solution so far. No twrp and no root
Now I have flashed the original rom with ZUI 10. Works well and updated to ZUI 11.
luigi0824 said:
Have the same scenario as you but I haven't done the tutorial yet as I read your post and I got concerned. Have you fix you issue? Is it safe to do this tutorial?
Click to expand...
Click to collapse
I've read somewhere that you need to flash vbmeta.img if verified boot is enabled, however I couldn't find the correct img to flash anywhere. Maybe if we ask someone that has the phone already rooted.
Can anyone post wzsx150's newest TWRP 3.3.1 from October 4? It's in this thread but the download link is for registered users only. I can't sign up for a Club Lenovo account.
BlueIce84 said:
No solution so far. No twrp and no root
Now I have flashed the original rom with ZUI 10. Works well and updated to ZUI 11.
Click to expand...
Click to collapse
What method would you follow to install the stock rom, like you, it comes with the bootloader unlocked by the seller and I don't know how to flash stock rom
Use this guide:
https://forum.xda-developers.com/z5-pro-gt/how-to/guide-unbrick-guide-lenovo-z5-pro-gt-t3915945
carlshark said:
Can anyone post wzsx150's newest TWRP 3.3.1 from October 4? It's in this thread but the download link is for registered users only. I can't sign up for a Club Lenovo account.
Click to expand...
Click to collapse
I gave up on clublenovo. They require SMS authentication to post so even when you log in you can't post and download. TWRP 3.3.1 is also available from 4PDA. That's what I used.
I was able to flash the TWRP 3.3.1 but i cant root nor i cant flash anything as the folders inside the sdcard directory is showing in weird names
luigi0824 said:
I was able to flash the TWRP 3.3.1 but i cant root nor i cant flash anything as the folders inside the sdcard directory is showing in weird names
Click to expand...
Click to collapse
You need to decrypt the internal storage.
normally this is done by entering to ping code to unlock the phone in TWRP on start up.
thorvall said:
You need to decrypt the internal storage.
normally this is done by entering to ping code to unlock the phone in TWRP on start up.
Click to expand...
Click to collapse
Will I lose any data if I decrypt my phone? And where do I find that pin code?
luigi0824 said:
Will I lose any data if I decrypt my phone? And where do I find that pin code?
Click to expand...
Click to collapse
Its the pin code you use to open the phone.
And enabling does not remove data, but it does give twrp read/write permission
Is it possible to implement support for OTA updates through TWRP?
BlueIce84 said:
My device was unlocked by vendor. I'm unable to boot into twrp to root my device. The flashing is successful but it will only boot in a simple recovery where I can only install an "update.zip".
Have tried this https://forum.xda-developers.com/z5...-guide-lenovo-z5-pro-gt-t3915945#post81055547 but the problem remains.
Hope anyone can help. I need to root my device. Thanks
Click to expand...
Click to collapse
i had the same issue and discover a solution
1) you have to manually go to your phone after you finish the flash below. DO NOT cmd fastboot reboot as it will flash stock
recovery
a) fastboot flash recovery twrp.img ( i rename the tweak recovery file to twrp.img)
b) http://4pda.ru/forum/index.php?showtopic=973179&st=0
(tweak recovery version 3.31)
2) after flash quickly go to your phone fastboot mode ( reminder again: do not tyoe fastboot reboot after flash successful appear in cmd)
3) manually select recovery , select english then select reboot and TWRP will appear
issues
1) i cannot manually tweak recovery via phone ( power +volume down ) as stock recovery will appear again.
A) so you need to go your PC to redo flash recovery again
B) i did a back up and redo PC flassh recovery again and mine files are stored successful
c) there is no install root in TWRP
D) about backup...
.best to back up via OTA-USB. pixel GCI crash ( QUALCOMM CRASH DUMP MODE ) my phone and my restore
file was missing as TWRP rename the restore file. spent one hour it so decide to do stock rom
current
a) I have not flash any rom yet and my original ANTUTU benchmark hovers around 300000 to 350000 based on vendor custom global rom
b) my phone model is 8gb 128gb android version 9 and lenovo version 11.0.084
c) updatess and NFC not supported
d) i opt not too root
e) bootloader still unlock
REQUEST...
would appreciate a ROM recommendation
a) have anyone flash a rom (not china stock rom) wirh an antutu beachmark abve 400000 ?
from a novice... after 2 weeks i can finally flash tweak recovery from the phonE.
about flashing stock rom..
i opt for stock rom and my antutu hovers around 409000 to 418000. from LENOVO app centre you can install play store
butterx2341 said:
i had the same issue and discover a solution
1) you have to manually go to your phone after you finish the flash below. DO NOT cmd fastboot reboot as it will flash stock
recovery
a) fastboot flash recovery twrp.img ( i rename the tweak recovery file to twrp.img)
b) http://4pda.ru/forum/index.php?showtopic=973179&st=0
(tweak recovery version 3.31)
2) after flash quickly go to your phone fastboot mode ( reminder again: do not tyoe fastboot reboot after flash successful appear in cmd)
3) manually select recovery , select english then select reboot and TWRP will appear
issues
1) i cannot manually tweak recovery via phone ( power +volume down ) as stock recovery will appear again.
A) so you need to go your PC to redo flash recovery again
B) i did a back up and redo PC flassh recovery again and mine files are stored successful
c) there is no install root in TWRP
D) about backup...
.best to back up via OTA-USB. pixel GCI crash ( QUALCOMM CRASH DUMP MODE ) my phone and my restore
file was missing as TWRP rename the restore file. spent one hour it so decide to do stock rom
current
a) I have not flash any rom yet and my original ANTUTU benchmark hovers around 300000 to 350000 based on vendor custom global rom
b) my phone model is 8gb 128gb android version 9 and lenovo version 11.0.084
c) updatess and NFC not supported
d) i opt not too root
e) bootloader still unlock
REQUEST...
would appreciate a ROM recommendation
a) have anyone flash a rom (not china stock rom) wirh an antutu beachmark abve 400000 ?
from a novice... after 2 weeks i can finally flash tweak recovery from the phonE.
about flashing stock rom..
i opt for stock rom and my antutu hovers around 409000 to 418000. from LENOVO app centre you can install play store
Click to expand...
Click to collapse
If you boot your ZUI system, your twrp will be overwritten by a stock recovery.
However if you flash magisk, your twrp won't be overwritten anymore. If you want to preserve your twrp after rebooting on ZUI, you need to flash magisk.
whatever I do.. the twrp wont be installed (let alone the root/magisk). ADB does say the twrp is flashed... but it will always boot to or the bootloader.. or the system (not the lenovo recovery or twrp recovery). Quiet frustrating... what can I do? Want this boy rooted!
Edit: done. The twrp linked in the tutorial is not correct use this one: https://drive.google.com/file/d/13mt0RLmT83BHSUBpH-J7EhaeZQ-MPYUu/view
That worked!
I want to unlock my bootloader but the site where you request the image file for unlocking it wont accept my IMEI1.. any idea guys?

[Guide][Rom][Root][official][MIUI 11] for Rooted Devices & root guide

Keeping it short:
This is the official STABLE global MIUI 11 Rom for Mi 9T
Official download links:
For rooted devices - Recovery full zip (2.3GB)
For stock unrooted devices - OTA upgrade zip (779MB)
Magisk Root without TWRP:
Objectives :
Have root using Magisk
Be able to install OTA from the settings without bootloops
Avoid boot loop
Very important :
Your phone has to have an unlocked bootloader
Your phone has to have stock recovery. TWRP WILL cause bootloop for root and/or OTA updates from system.
I like to have root with magisk and don't want to install TWRP because I want to be able to install OTA from system without boot loops. This guide will help you achieve this with ease.
Download the rooted boot image for your correct ROM version from here: https://mega.nz/#F!1kwETAwD!O5iPgAaocQ8WxfUK2V7RVA
Restart your phone in fastboot mode (hold vol-down and power buttons for a few seconds)
Flash the rooted boot image using fastboot. (fastboot flash boot Magisk_9T_Global_V11.0.1.0.PFJMIXM.img)* **
Reboot device (fastboot.exe reboot)
(install then) Open Magisk manager
Follow instruction shown in the magisk manager for adding necessary files (you might not need this)
*Download the latest Minimal ADB /fastboot and USB drivers for your device if you are having a problem with this.
** Using some data cables will result in your fastboot not seeing your device (showing < waiting for any device >). If you have this problem change your USB cable with another or use the one that comes with the device
I have attached the following root files:
V10.3.11.0.PFJMIXM (MIUI10) global stable room - Global 9T stock boot image
V11.0.1.0.PFJMIXM (MIUI11) global stable room - Global 9T stock boot image
V11.0.1.0.PFJMIXM (MIUI11) global stable room - Global 9T Magisk rooted boot image
Things to consider doing after the update:
Remove ads using this guide: https://miblog.co/miui-remove-system-ads/
Enable Android style notification (instead of the default MiUI one) from the notification settings
Disable option: “Settings / Additional settings / Privacy / Location / Scanning / WLAN scanning” to improve battery life
Use this guide to install Xiaomi Mi 9 Google Camera (GCam) (no root needed): https://miblog.co/xiaomi-mi9-google-camera/
Disable autostart for all apps excluding the ones you want to autostart to fix the battery drainage issue
{
"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"
}
Hey, quick question. I'm trying to install the new MIUI11 stock global ROM for my Mi 9T. The thing is, the phone's updater takes forever to download and the download itself even gets cancelled out of nowhere (my internet is pretty slow) Can I just download the 779MB OTA Upgrade zip you provided and move it to my phone and proceed selecting it from the updater app? Is it the same file you get as downloading it from the app? I'm on global, PFJMIXM version 10.3.11.0
Thanks!
Danielxgl said:
Hey, quick question. I'm trying to install the new MIUI11 stock global ROM for my Mi 9T. The thing is, the phone's updater takes forever to download and the download itself even gets cancelled out of nowhere (my internet is pretty slow) Can I just download the 779MB OTA Upgrade zip you provided and move it to my phone and proceed selecting it from the updater app? Is it the same file you get as downloading it from the app? I'm on global, PFJMIXM version 10.3.11.0
Thanks!
Click to expand...
Click to collapse
I'm not sure how the update app does the file check. Can you try it and report?
I know that if you're rooted, the OTA will fail to install and the update app automatically starts downloading the full ROM, which is pretty cool.
Kiwironic said:
I'm not sure how the update app does the file check. Can you try it and report?
I know that if you're rooted, the OTA will fail to install and the update app automatically starts downloading the full ROM, which is pretty cool.
Click to expand...
Click to collapse
Wish I could try it, but my update app miraculously decided not to fail this time, and I was able to update the phone normally. Maybe someone else could try it?
What im i do wrong if i get twrp while trying to boot miui? Installed Patched boot installed firmware cannot boot
Still Android 9, no?
SeriousX said:
What im i do wrong if i get twrp while trying to boot miui? Installed Patched boot installed firmware cannot boot
Click to expand...
Click to collapse
Flash the stock or rooted boot image and recovery for your device. It should work normally. That's my main reason to root without TWRP
robi10101298 said:
Still Android 9, no?
Click to expand...
Click to collapse
Yes
Kiwironic said:
Keeping it short:
This is the official STABLE global MIUI 11 Rom for Mi 9T
Official download links:
For rooted devices - Recovery full zip (2.3GB)
For stock unrooted devices - OTA upgrade zip (779MB)
Magisk Root without TWRP:
Download the rooted boot image for your correct ROM version from here: https://mega.nz/#F!1kwETAwD!O5iPgAaocQ8WxfUK2V7RVA
Restart your phone in fastboot mode (hold vol-down and power buttons for a few seconds)
Flash the rooted boot image using fastboot. (fastboot flash boot Magisk_9T_Global_V11.0.1.0.PFJMIXM.img)* **
Reboot device (fastboot.exe reboot)
(install then) Open Magisk manager
Follow instruction shown in the magisk manager for adding necessary files (you might not need this)
*Download the latest Minimal ADB /fastboot and USB drivers for your device if you are having a problem with this.
** Using some data cables will result in your fastboot not seeing your device (showing < waiting for any device >). If you have this problem change your USB cable with another or use the one that comes with the device
I have attached the following root files:
V10.3.11.0.PFJMIXM (MIUI10) global stable room - Global 9T stock boot image
V11.0.1.0.PFJMIXM (MIUI11) global stable room - Global 9T stock boot image
V11.0.1.0.PFJMIXM (MIUI11) global stable room - Global 9T Magisk rooted boot image
Things to consider doing after the update:
Remove ads using this guide: https://miblog.co/miui-remove-system-ads/
Enable Android style notification (instead of the default MiUI one) from the notification settings
Disable option: “Settings / Additional settings / Privacy / Location / Scanning / WLAN scanning” to improve battery life
Use this guide to install Xiaomi Mi 9 Google Camera (GCam) (no root needed): https://miblog.co/xiaomi-mi9-google-camera/
Disable autostart for all apps excluding the ones you want to autostart to fix the battery drainage issue
Click to expand...
Click to collapse
If I don't want root anymore I can install this via Twrp: Recovery full zip (2.3GB)rooted devices + V11.0.1.0.PFJMIXM (MIUI11) global stable room - Global 9T stock boot image
Is this right?
Drakar88 said:
If I don't want root anymore I can install this via Twrp: Recovery full zip (2.3GB)rooted devices + V11.0.1.0.PFJMIXM (MIUI11) global stable room - Global 9T stock boot image
Is this right?
Click to expand...
Click to collapse
Yes the full rom. But no need to flash boot, flashing the full image will automatically rewrite the boot image to a stock unrooted one.
Anybody who needed a root boot image, can send me the version of their ROM or send me the boot image from their phone and I'll root it for you using magisk. You can do that yourself as well by downloading the full ROM zip file, take the boot file and use magisk to create a root boot image. Can provide more details if you don't know how to do it.
Kiwironic said:
Anybody who needed a root boot image, can send me the version of their ROM or send me the boot image from their phone and I'll root it for you using magisk. You can do that yourself as well by downloading the full ROM zip file, take the boot file and use magisk to create a root boot image. Can provide more details if you don't know how to do it.
Click to expand...
Click to collapse
Do provide more details. I'm on stock miui (davinciin), with unlocked bl and would like to root tf outta this
geeknoob said:
Do provide more details. I'm on stock miui (davinciin), with unlocked bl and would like to root tf outta this
Click to expand...
Click to collapse
I wrote a guide and made some videos here :
https://forum.xda-developers.com/showpost.php?p=80835573&postcount=1
Updated the post because people using the guide while having TWRP will have bootloop . Please read the instructing carefully. You need a stock recovery for this root to work and for OTA to install from settings
Thanks for this guide, I couldn't get official TWRP to stick so that I could flash Magisk. I used your guide and now I have root. Many thanks
i need to ask.
when miui release a new update i usually update and after that i had to re flash the "recovery-TWRP-3.3.1-0916-REDMI_K20-CN-wzsx150" then again flash the magisk.
but this time i try to install it boot the recovery but when i go to the internal memory it appear a lot of weird folders and it won't allow me to paste the magisk to install it.
"+KPcZ3jsjybn9M850BgrhB"
3zitjokdIMQE++oQFL8PxA
9AmJcdRgO71ehKtIhWg3oB
9Y0e9H1NkAr4FMzOz9X,UD
882G73cfQNPbaXm2zAzXiD
---------- Post added at 11:34 AM ---------- Previous post was at 11:24 AM ----------
Jctatis said:
i need to ask.
when miui release a new update i usually update and after that i had to re flash the "recovery-TWRP-3.3.1-0916-REDMI_K20-CN-wzsx150" then again flash the magisk.
but this time i try to install it boot the recovery but when i go to the internal memory it appear a lot of weird folders and it won't allow me to paste the magisk to install it.
"+KPcZ3jsjybn9M850BgrhB"
3zitjokdIMQE++oQFL8PxA
9AmJcdRgO71ehKtIhWg3oB
9Y0e9H1NkAr4FMzOz9X,UD
882G73cfQNPbaXm2zAzXiD
Click to expand...
Click to collapse
NVM already fixed installed the twrp-3.3.1-0-davinci.img and flashed the magisk v.20
Kiwironic said:
Anybody who needed a root boot image, can send me the version of their ROM or send me the boot image from their phone and I'll root it for you using magisk. You can do that yourself as well by downloading the full ROM zip file, take the boot file and use magisk to create a root boot image. Can provide more details if you don't know how to do it.
Click to expand...
Click to collapse
Thanks for this! Would you be able to make a patched boot.img for V11.0.5.0.QFJMIXM? Please? Mi net is too bad to download the whole rom
galelouch993 said:
Thanks for this! Would you be able to make a patched boot.img for V11.0.5.0.QFJMIXM? Please? Mi net is too bad to download the whole rom
Click to expand...
Click to collapse
Just downloaded the whole ROM with no problem from:
https://mirom.ezbox.idv.tw/en/phone/davinci/
Anyway, try with the following - patched from my Magisk Canary:
https://mega.nz/file/09M13QhI#4AXcEYviHw_1xyhCoDYZh_J41Iu58ulozuRJbhQZP6w
You can test just by temporarily booting to the patched image (if it boots ok, then you would really flash it):
fastboot boot boot-Magisk_Canary_20405-davinci_v11.0.5.0_QFJIMXM_aaab5b40c7_10.0.img
Download and install the corresponding Canary Magisk Manager e.g. app-release.apk, from:
https://github.com/topjohnwu/magisk_files/find/canary?q=
If you have a bootloop it could be due to the previously installed Magisk modules - you would need to disable them in TWRP:
/data/adb/modules
and to every subfolder add an empty file named "disable" (or delete the whole modules folder)
zgfg said:
Just downloaded the whole ROM with no problem from:
https://mirom.ezbox.idv.tw/en/phone/davinci/
Anyway, try with the following - patched from my Magisk Canary:
https://mega.nz/file/09M13QhI#4AXcEYviHw_1xyhCoDYZh_J41Iu58ulozuRJbhQZP6w
You can test just by temporarily booting to the patched image (if it boots ok, then you would really flash it):
fastboot boot boot-Magisk_Canary_20405-davinci_v11.0.5.0_QFJIMXM_aaab5b40c7_10.0.img
Download and install the corresponding Canary Magisk Manager e.g. app-release.apk, from:
https://github.com/topjohnwu/magisk_files/find/canary?q=
If you have a bootloop it could be due to the previously installed Magisk modules - you would need to disable them in TWRP:
/data/adb/modules
and to every subfolder add an empty file named "disable" (or delete the whole modules folder)
Click to expand...
Click to collapse
Ty very much for replying with a complete guide and files needed. I managed to get a boot.img for my version and patched it successfully with stable magisk manager. I'm very grateful for your efforts tho.
Btw, any special reason for using canary builds in your steps?
9
galelouch993 said:
Ty very much for replying with a complete guide and files needed. I managed to get a boot.img for my version and patched it successfully with stable magisk manager. I'm very grateful for your efforts tho.
Btw, any special reason for using canary builds in your steps?
Click to expand...
Click to collapse
Canary has some early fixes and features, but also some new bugs
E.g., for a long time, Canary has a new UI. It was buggy and with issues but now is already good and stable andI I like its new features
But just realized that V4A cannot install driver with yesterday's Magisk Canary 20401 so I returned back to Canary 20405
Edit:
Btw, you can try Magisk Manager Canary - install from the link in my previous post.
It should work with your stable Magisk
By using Stable Channel, you can always return to stable Manager version

[ROM][10][OFFICIAL] Lineage 17.1 NIGHTLY for MOTO G5. (Cedric)

OFFICIAL LINEAGE OS 17.1 NIGHTLIES
LineageOS Downloads
download.lineageos.org
The most recent build was dated 25th Feb 2021. [Edit UPDATED to most recent build date].
The previous offerings were 2021-01-28; 2021-02-04 ; 2021-02-11; 2021-02-18.
{
"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"
}
CEDRIC WIKI
Info about cedric | LineageOS Wiki
wiki.lineageos.org
Hi, I tried to install it on OPP28.85-19-4-2 but the installation failed (infinite loop at start-up). According to this https://wiki.lineageos.org/devices/cedric/install the latest Android 8.1 firmware is required. Which one is it ? Thanks !
QRXpMUvS said:
Hi, I tried to install it on OPP28.85-19-4-2 but the installation failed (infinite loop at start-up). According to this https://wiki.lineageos.org/devices/cedric/install the latest Android 8.1 firmware is required. Which one is it ? Thanks !
Click to expand...
Click to collapse
Any oero firmware will do as your base
Flash via fastboot - if you don't know which to choose use the latest retail version
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
How to flash rom
Go to twrp
Select wipe
Format data - option on the right (will format everything on phone including personal files so backup first!)
Restart to twrp
Wipe then advanced wipe
Wipe system data and cache
Select install from main menu
Install rom zip
Install gapps (you want arm64 android 10 nano)
Install magisk (optional for root access & to hide apps from detecting root/custom rom)
Wipe delvik cache
Restart
Encrypt phone again if required once booted from phone settings menu
Thanks, I did as you explained, but I am still stuck with a lineageos logo looping for a few dozens of minuts before the phone restarts and goes straight to TWRP.
QRXpMUvS said:
Thanks, I did as you explained, but I am still stuck with a lineageos logo looping for a few dozens of minuts before the phone restarts and goes straight to TWRP.
Click to expand...
Click to collapse
Wipe system data cache and flash rom without gapps or magisk
Does it boot?
If yes wipe everything again and flash rom zip but flash gapps as well this time. And if it boots flash magisk (no need to wipe to flash magisk)
If magisk causes it to boot loop flash an older version
If none of the above works and you have the same issue trying to flash another rom eg lineage mint then its user error somewhere or an issue unrelated to the rom zip
Hi,
i updated my G5 to the official LOS. Although VoWifi and VoLTE are enabled in settings, none of them are working (They didn't work on the unofficial version either).
According to my network operator, these functions are activated.
Unter Phone Info (*#*#4636#*#* in dialer's app) it says "IMS Registration: Not Registered"
Is there anything I can do about this?
Thanks!
TheFixItMan said:
Wipe system data cache and flash rom without gapps or magisk
Does it boot?
If yes wipe everything again and flash rom zip but flash gapps as well this time. And if it boots flash magisk (no need to wipe to flash magisk)
If magisk causes it to boot loop flash an older version
If none of the above works and you have the same issue trying to flash another rom eg lineage mint then its user error somewhere or an issue unrelated to the rom zip
Click to expand...
Click to collapse
I tried without gapps and magisk, it does not boot, same with Mint.
So if I understand well, the problem is probably on my side
What I did :
New firmware using fastboot following these commands.
At this stage, TWRP had disappear (!), I reinstalled it using fastboot. Is it normal ?
Then I installed lineageos.
QRXpMUvS said:
I tried without gapps and magisk, it does not boot, same with Mint.
So if I understand well, the problem is probably on my side
What I did :
New firmware using fastboot following these commands.
At this stage, TWRP had disappear (!), I reinstalled it using fastboot. Is it normal ?
Then I installed lineageos.
Click to expand...
Click to collapse
I have the same problem. I can't get Lineage or Mint to boot on my Cedric.
I've tried TWRP 3.4 , and 3.5 and neither made a difference. I have been through the instructions on the lineage site many times, and I'm sure I'm not missing a step
But every time the device sticks at lineage boot logo for a long time, before returning to fastboot mode.
If I re-flash 8.1 using fastboot, the phone works again, then go from the top with twrp and lineage, and we're back to logo and eventually fastboot again.
So, although I cannot help yet, you are not alone.
Edit:
My cedric is the 3GB RAM XT1676 model which I think might be somewhat rare version?
HarpingOn said:
So, although I cannot help yet, you are not alone.
Click to expand...
Click to collapse
Thanks ! By chance, do you know any unofficial rom (not necessarely 17.1) correctly booting on 8.1 ?
QRXpMUvS said:
Thanks ! By chance, do you know any unofficial rom (not necessarely 17.1) correctly booting on 8.1 ?
Click to expand...
Click to collapse
I have only tried mint and official 17.1. Get the same problem with both sadly.
I just realised, on the installation instructions it says to flash the recovery from the lineage download page, not twrp
So I tried:
motog5> fastboot flash recovery lineage-17.1-20210225-recovery-cedric.img
target reported max download size of 535822336 bytes
Sending 'recovery' (18390 KB)...
OKAY [ 0.586s]
Writing 'recovery'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
The cedric recovery image on the download page is about 2MB larger than the TWRP recovery.
So should I be using the lineage provided recovery to flash this?
edit:
I managed to get the cedric to boot the lineage supplied recovery by doing:
motog5> fastboot boot lineage-17.1-20210225-recovery-cedric.img
I then used that recovery (looks good by the way, smart looking recovery), but after flashing the matching lineage-17.1 image ( adb sideload lineage-17.1-20210225-nightly-cedric-signed.zip) , I still get the long running boot animation, and dumped back into bootloader after a while.
I think I should stop now, I'm getting tired
For your info everyone: the OP is not the developer. I am neither. I just patch the official builds and that is Mint.
HarpingOn said:
I just realised, on the installation instructions it says to flash the recovery from the lineage download page, not twrp
So I tried:
motog5> fastboot flash recovery lineage-17.1-20210225-recovery-cedric.img
target reported max download size of 535822336 bytes
Sending 'recovery' (18390 KB)...
OKAY [ 0.586s]
Writing 'recovery'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
The cedric recovery image on the download page is about 2MB larger than the TWRP recovery.
So should I be using the lineage provided recovery to flash this?
edit:
I managed to get the cedric to boot the lineage supplied recovery by doing:
motog5> fastboot boot lineage-17.1-20210225-recovery-cedric.img
I then used that recovery (looks good by the way, smart looking recovery), but after flashing the matching lineage-17.1 image ( adb sideload lineage-17.1-20210225-nightly-cedric-signed.zip) , I still get the long running boot animation, and dumped back into bootloader after a while.
I think I should stop now, I'm getting tired
Click to expand...
Click to collapse
If you could give me logs, I'll check.
nift4 said:
If you could give me logs, I'll check.
Click to expand...
Click to collapse
My problem was that I was starting from the GB release of Cedric stock 8.1 as I'm in the UK. If I flashed the GB version, then no Lineage ROM would boot. Not this, and not the Mint one.
If you check out the Mint thread, what I did was use Fastboot to flash an international version of stock 8.1, then I could add TWRP and flash this successfully.
I ended up testing Lineage With microG, but actually successfully flashed this, and Mint as well.
So I'd say to anyone struggling to get a working flash of this ROM, try a different CEDRIC set of fastboot files.
as im aware, you need to flash from stock 8.1 but sometimes if youre on pie you gotta flash nougat and then oreo to flash custom roms i tried flashing that rom before but got no succes with bootlop but i didnt knew this i have tried unnoficial los 17 but never though about trying again the one from los page, guess its Worth a try
update: i got to flash and boot but the system reboots randomly, mostly when i open apps
also twitter doesnt login into my account for a weird reason dunno why. guess ill loke other roms around
Lighto97 said:
update: i got to flash and boot but the system reboots randomly, mostly when i open apps
also twitter doesnt login into my account for a weird reason dunno why. guess ill loke other roms around
Click to expand...
Click to collapse
You need to been on oreo firmware to flash this rom - preferably the latest retail version
You also need gapps that are arm64 android 10 nano
See my instructions above for how to flash rom correctly (post #3)
Without any logs the devs will put it down to user error
TheFixItMan said:
You need to been on oreo firmware to flash this rom - preferably the latest retail version
You also need gapps that are arm64 android 10 nano
See my instructions above for how to flash rom correctly (post #3)
Without any logs the devs will put it down to user error
Click to expand...
Click to collapse
oh damm i always forgot i have to send the log for them to track the issue, i already uninstaled anyway.
i did followed the steps the right way (thank you), right now im flashing stock nougat to try out LOS 14.1 (which i love and seems to be reeealy stable)
thank you very much to all involved for this … this gives a new lease of life to the moto g5. i tried both the official version and a microg4lineageos build - both work flawlessly afaict.
a few observations:
camera works, both photos and videos. the new camera app is quite usable.
coming from a build derived from codezeros 16.0-tree, i had to revert to the stock firmware to be able to install this. not doing so resulted in boot loops, wiping everything did not help
the los recovery cannot be flashed, it seems to be too big for the recovery partition. twrp works fine.
tfbb said:
thank you very much to all involved for this … this gives a new lease of life to the moto g5. i tried both the official version and a microg4lineageos build - both work flawlessly afaict.
a few observations:
camera works, both photos and videos. the new camera app is quite usable.
coming from a build derived from codezeros 16.0-tree, i had to revert to the stock firmware to be able to install this. not doing so resulted in boot loops, wiping everything did not help
the los recovery cannot be flashed, it seems to be too big for the recovery partition. twrp works fine.
Click to expand...
Click to collapse
i know how to boot with that LOS recovery, instead of flash comand you use boot command so the device will bot into recovery suing the image.

Question TWRP 3.5.2_11-Nebrassy and unable to decrypt FBE device [Solved]

Hi,
after flashing TWRP 3.5.2_11-Nebrassy on my Redmi Note 10 (sunny) and flashing Havoc OS after reboot I always come back to twrp. Cannot boot Havoc OS. And I see E: Unable to decrypt FBE device. What should I do to resolve this problem?
dario-20 said:
Hi,
after flashing TWRP 3.5.2_11-Nebrassy on my Redmi Note 10 (sunny) and flashing Havoc OS after reboot I always come back to twrp. Cannot boot Havoc OS. And I see E: Unable to decrypt FBE device. What should I do to resolve this problem?
Click to expand...
Click to collapse
Always wipe dalvic cache data storage and format data before you flash any rom
It
akoaypinoy said:
Always wipe dalvic cache data storage and format data before you flash any rom
Click to expand...
Click to collapse
It was done! But still have the same error and still come back to trwp instead of the new rom (Havoc). :-(
dario-20 said:
It
It was done! But still have the same error and still come back to trwp instead of the new rom (Havoc). :-(
Click to expand...
Click to collapse
How you flash havoc? Vanilla or Gapps version?
akoaypinoy said:
How you flash havoc? Vanilla or Gapps version?
Click to expand...
Click to collapse
Gapps
If you installed a new rom, clear the data and delvik cache at the end.
StaryMuz said:
If you installed a new rom, clear the data and delvik cache at the end.
Click to expand...
Click to collapse
I did this. Every time when I reboot it always comes back to twrp. Strange! In my opinion it is a matter of error: E: Unable to decrypt FBE device. How to overcome it?
Ok, finally I found solution: Installed OrangeFox https://forum.xda-developers.com/t/orangefox-recovery-for-redmi-note-10-sunny-mojito.4293709/
and no problem! Maybe this will be helpfull for somebody else...
dario-20 said:
I did this. Every time when I reboot it always comes back to twrp. Strange! In my opinion it is a matter of error: E: Unable to decrypt FBE device. How to overcome it?
Ok, finally I found solution: Installed OrangeFox https://forum.xda-developers.com/t/orangefox-recovery-for-redmi-note-10-sunny-mojito.4293709/
and no problem! Maybe this will be helpfull for somebody else...
Click to expand...
Click to collapse
That's weird, havoc is not kind of caf rom , hnnn
akoaypinoy said:
That's weird, havoc is not kind of caf rom , hnnn
Click to expand...
Click to collapse
After this installation I cannot boot into recovery! Probably I installed twrp in wrong way for the very first time. But still don't know how to make it right. It means when I install twrp in the wright way I cannot install Havoc... Maybe tommorow I will try to come back to twrp...
The correct way to install TWRP is to run it without installing it first and then install it to the ramdisk. If you do it any other way, you will delete the boot and replace it only with the recovery one. Then the phone can't go anywhere but recovery.
only boot from twrp. dont flash it
inn0ichi said:
only boot from twrp. dont flash it
Click to expand...
Click to collapse
Thank you very much for your responses. What does it mean exactly now in my situation? What steps should be exactly taken now by me?
dario-20 said:
Thank you very much for your responses. What does it mean exactly now in my situation? What steps should be exactly taken now by me?
Click to expand...
Click to collapse
fastboot boot twrp.img
Automatic it reboot to twrp recovery ,next steps is
Go to mount and check if mtp is enable once mtp enable go to your phone storage then paste twrp.image on internal storage of your phone ,once you place that twrp. Disconnect your USB cord on phone then go to advance/flash on ramdisk/then you will click the TWRP img. And flash .
That's it
I recommend a different procedure. Take the boot.img file from the ZIP file of the installed ROM. Then flash it in fastboot with the fastboot flash boot boot.img command. This should boot the ROM normally. You will at that point have a stock recovery of the ROM. To change it you must follow the specific installation procedure, otherwise you will not start the ROM again. If you cannot get the boot.img from the ZIP file, you must reinstall the entire ROM.
akoaypinoy said:
fastboot boot twrp.img
Automatic it reboot to twrp recovery ,next steps is
Go to mount and check if mtp is enable once mtp enable go to your phone storage then paste twrp.image on internal storage of your phone ,once you place that twrp. Disconnect your USB cord on phone then go to advance/flash on ramdisk/then you will click the TWRP img. And flash .
That's it
Click to expand...
Click to collapse
Thanks but: Now I am on OrangeFox recovery (which I cannot boot - it was the last flashed recovery). Typing fastboot boot twrp.img gives back: not found
What do you suggest in this situation?
StaryMuz said:
I recommend a different procedure. Take the boot.img file from the ZIP file of the installed ROM. Then flash it in fastboot with the fastboot flash boot boot.img command. This should boot the ROM normally. You will at that point have a stock recovery of the ROM. To change it you must follow the specific installation procedure, otherwise you will not start the ROM again. If you cannot get the boot.img from the ZIP file, you must reinstall the entire ROM.
Click to expand...
Click to collapse
In the ZIP file of HAVOC ROM there were no boot.img file :-(
So I am still on OrangeFox which I cannot boot. I only can boot the ROM (HAVOC). So if I understand you well I should reinstall my ROM (loosing my data), yes?
Reinstalling the ROM will not delete the data itself. You must not delete data before or after installation.
Reinstallation should not need data deletion.
For what reason are you trying to change the recovery included in the ROM?
I can also offer to pull the boot.img from the ZIP ROM. But you would have to give me a link to the ZIP file you used.
StaryMuz said:
Reinstalling the ROM will not delete the data itself. You must not delete data before or after installation.
Reinstallation should not need data deletion.
For what reason are you trying to change the recovery included in the ROM?
I can also offer to pull the boot.img from the ZIP ROM. But you would have to give me a link to the ZIP file you used.
Click to expand...
Click to collapse
Okay but now I cannot install anything because I have no access to recovery! Maybe I explain what I did:
1. Installed TWRP in wrong way (Error: unable to decrypt FBE device and unable to mount data)
2. Installed OrangeFox (zip file through TWRP)
3. Installed Havoc OS
4. Now I have no access to OrangeFox. I have access only to recovery of Havoc OS ROM. But it is useless because I can do nothing with it.
4. How can I start the new flashing of TWRP the proper way? I don't care about the present HAVOC OS because I have a backup of my all data.
5. I want TWRP or OrangeFox recocery for installing Magisk (rooting) what is now impossible.
{
"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"
}
Reboot to recovery → I return to the same recovery as above.
dario-20 said:
In the ZIP file of HAVOC ROM there were no boot.img file :-(
So I am still on OrangeFox which I cannot boot. I only can boot the ROM (HAVOC). So if I understand you well I should reinstall my ROM (loosing my data), yes?
Click to expand...
Click to collapse
orangefox is that your recovery now. Orangefox and twrp are recovery both. The difference is that orangefox can no flash the kernel unlike twrp. Please be specific what you are doing,
Orangefox and twrp are recovery
HavocOS is a rom
Before you do make specific, or else you get messed.
dario-20 said:
Okay but now I cannot install anything because I have no access to recovery! Maybe I explain what I did:
1. Installed TWRP in wrong way (Error: unable to decrypt FBE device and unable to mount data)
2. Installed OrangeFox (zip file through TWRP)
3. Installed Havoc OS
4. Now I have no access to OrangeFox. I have access only to recovery of Havoc OS ROM. But it is useless because I can do nothing with it.
4. How can I start the new flashing of TWRP the proper way? I don't care about the present HAVOC OS because I have a backup of my all data.
5. I want TWRP or OrangeFox recocery for installing Magisk (rooting) what is now impossible.
View attachment 5449627View attachment 5449629
Reboot to recovery → I return to the same recovery as above.
Click to expand...
Click to collapse
Everytime you install a new make it read . Because other rom have own recovery. (Ex. Pixelplus) once you install that automatically you have a pe recovery once it reboot , so the proper way to maintain twrp is "flash current twrp" which you can find in advance in twrp recovery. Remember once you flash a new rom don't reboot and go to advance then flash the current twrp. After that reboot.

Categories

Resources