Hi guys!
You can donate to me https://www.paypal.me/penvineeth and @cerg2010cerg2010 through paypal.
@cerg2010cerg2010 PAYPAL EMAIL: [email protected] OR QIWI: +79157840294
Disclaimer:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired. Please
* do some research if you have any concerns about features included in this Recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Click to expand...
Click to collapse
No more secure boot error!
I thank my friend @cerg2010cerg2010 for helping me out in patching the aboot.
-> Steps:
(1) Downgrade to v10f version of Android.
(2) Root your device.
(3) Download this patched aboot file. Click Here
(4) Connect your phone to the computer. In command prompt, type "adb shell".
(5) Transfer the aboot file into /sdcard/ folder.
(6) Type "su" to enter the root shell. Then type "dd if=/sdcard/aboot_v10f.bin of=/dev/block/<your aboot partition>".
(7) Restart your phone by typing "reboot".
You have unlocked your bootloader!
If you get a black screen there is a problem with your recovery.
For more detailed guide. Follow this by @Korelev.
Refer Notes for more information.
-> Notes:
1) The aboot_v10f.bin is the patched version of aboot partition of your device. Secure boot validation has been patched such that secure boot is always valid, so you can flash your own TWRP and Custom ROM.
2) Don't upgrade to any updated version of Android if you get any through OTA update. It might brick your device.
pvineeth97 said:
Hi guys!
Click to expand...
Click to collapse
Hi there! I tried your method an followed fobos explanation to found the required block (which is mmcblk0p5 in this case) but i'm still getting secure boot error when I try to get into TWRP, as far as I understand that shouldn't happen.
any ideas of what can I do to?
Korelev said:
Hi there! I tried your method an followed fobos explanation to found the required block (which is mmcblk0p5 in this case) but i'm still getting secure boot error when I try to get into TWRP, as far as I understand that shouldn't happen.
any ideas of what can I do to?
Click to expand...
Click to collapse
Did you downgrade your firmware as I told you in the guide?
Korelev said:
Hi there! I tried your method an followed fobos explanation to found the required block (which is mmcblk0p5 in this case) but i'm still getting secure boot error when I try to get into TWRP, as far as I understand that shouldn't happen.
any ideas of what can I do to?
Click to expand...
Click to collapse
First you have to flash the patched aboot and then flash TWRP. @Fobos needs to correct it.
After you finish flashing the TWRP. Run these commands on terminal/command line:
Code:
adb shell
su
cd /cache/recovery/
echo "--show_text" >> command
chmod 644 command
reboot recovery
I used the same method on my phone. It works!
pvineeth97 said:
First you have to flash the patched aboot and then flash TWRP. @Fobos needs to correct it.
After you finish flashing the TWRP. Run these commands on terminal/command line:
I used the same method on my phone. It works!
Click to expand...
Click to collapse
yeah, I downgraded
Oh, ok. I'll reflash everything then report. Many thx
Korelev said:
yeah, I downgraded
Oh, ok. I'll reflash everything then report. Many thx
Click to expand...
Click to collapse
I edited the post. Refer to it again.
pvineeth97 said:
I edited the post. Refer to it again.
Click to expand...
Click to collapse
done, I'm on it
---------- Post added at 08:54 PM ---------- Previous post was at 08:09 PM ----------
pvineeth97 said:
Korelev said:
Did you downgrade your phone to v10f as mentioned in the guide?
First you have to flash the patched aboot and then flash TWRP. @Fobos needs to correct it.
After you finish flashing the TWRP. Run these commands on terminal/command line:
Code:
adb shell
su
cd /cache/recovery/
echo "--show_text" >> command
chmod 644 command
reboot recovery
I used the same method on my phone. It works!
Click to expand...
Click to collapse
No luck, the message remains, I'm able to get into stock recovery but as soon as I flash TWRP there's the verity message
Do I have to reboot after aboot is replaced in order to flash twrp?
Click to expand...
Click to collapse
pvineeth97 said:
Hi guys!
Disclaimer:
No more secure boot error!
I thank my friend @cerg2010cerg2010 for helping me out in patching the aboot.
-> Steps:
(1) Downgrade to v10f version of Android.
(2) Root your device.
(3) Download this patched aboot file. Click Here.
(4) Connect your phone to the computer. In command prompt, type "adb shell".
(5) Transfer the aboot file into /sdcard/ folder.
(6) Type "su" to enter the root shell. Then type "dd if=/sdcard/aboot_v10f.bin of=/dev/block/<your aboot partition>".
(7) Restart your phone by typing "reboot".
You have unlocked your bootloader!
For more detailed guide. Follow this by @Fobos531.
Refer Notes for more information.
-> Notes:
1) The aboot_v10f.bin is the patched version of aboot partition of your device. Secure boot validation has been patched such that secure boot is always valid, so you can flash your own TWRP and Custom ROM.
2) Don't upgrade to any updated version of Android if you get any through OTA update. It might brick your device.
Click to expand...
Click to collapse
Not working man. Still getting the secure boot error as i boot into twrp :crying:
Any suggestions?
mayankjet said:
Not working man. Still getting the secure boot error as i boot into twrp :crying:
Any suggestions?
Click to expand...
Click to collapse
Please try this: https://yadi.sk/d/1Dw4_bod3EgUMU
cerg2010cerg2010 said:
Please try this: https://yadi.sk/d/1Dw4_bod3EgUMU
Click to expand...
Click to collapse
I'll give it a try!
Edit: I think that might be it! I get a black screen but no secure error msg. I'll give it another try
Edit2: OMG it works! It seems to be an issue with TWRP, CWM actually boots! I'll update
{
"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"
}
cerg2010cerg2010 said:
Please try this: https://yadi.sk/d/1Dw4_bod3EgUMU
Click to expand...
Click to collapse
I'm trying this right now and seems to hang for me when I reboot into recovery.
edit: I'm able to boot into the system normally. Will try to reboot into recovery again.
edit 2: Multiple people have confirmed that, when using this aboot and rebooting into recovery, they only get a black screen and it stays like that. the secure boot error ISN't there.
Korelev said:
I'll give it a try!
Edit: I think that might be it! I get a black screen but no secure error msg. I'll give it another try
Edit2: OMG it works! It seems to be an issue with TWRP, CWM actually boots! I'll update
Click to expand...
Click to collapse
Im also getting a black screen. How did you fix that, seems like an issue with twrp itself, right ?
mayankjet said:
Im also getting a black screen. How did you fix that, seems like an issue with twrp itself, right ?
Click to expand...
Click to collapse
SEEMS to be so, I can't confirm because I just found out CWM boots, but probably since many people reported the same according to fobos
anyway, no secure boot error so I guess we're fine
Korelev said:
SEEMS to be so, I can't confirm because I just found out CWM boots, but probably since many people reported the same according to fobos
anyway, no secure boot error so I guess we're fine
Click to expand...
Click to collapse
Thanks dude , it finally booted into cwm but it takes unusually long to boot into cwm.Cheers mate
mayankjet said:
Thanks dude , it finally booted into cwm but it takes unusually long to boot into cwm.Cheers mate
Click to expand...
Click to collapse
glad to hear!
Korelev said:
glad to hear!
Click to expand...
Click to collapse
If you get a black screen there is a problem with your recovery. Enjoy
Fobos531 said:
I'm trying this right now and seems to hang for me when I reboot into recovery.
edit: I'm able to boot into the system normally. Will try to reboot into recovery again.
edit 2: Multiple people have confirmed that, when using this aboot and rebooting into recovery, they only get a black screen and it stays like that. the secure boot error ISN't there.
Click to expand...
Click to collapse
There is a problem with your recovery. Edit your detailed guide. First flash patched aboot then flash TWRP/CWM.
pvineeth97 said:
There is a problem with your recovery.
Click to expand...
Click to collapse
We figured out CWM recovery works, so the aboot provided by your friend made the trick
Korelev said:
We figured out CWM recovery works, so the aboot provided by your friend made the trick
Click to expand...
Click to collapse
Made some changes in patched aboot. I updated that link into the main post. Enjoy XD
pvineeth97 said:
Made some changes in patched aboot. I updated that link into the main post. Enjoy XD
Click to expand...
Click to collapse
Thanks man, I think I can speak for almost everyone here if I say we thought this phone was dead for good. We probably will make a thread with detailed explanations and give all the credit to you and your friend, you might as well leave us a donate link in case anyone wants to.
again, thanks a lot!
Related
So I recently flashed a self made ROM for my watch and it totally bricked it, it cannot boot into a system (just bootloops), Cannot access recovery mode (just turns off and bootloops) and last but not least PC Companion will not detect it. All I have now is fastboot mode so if someone can please help me flash each partition via fastboot that would amazing. I do how ever all of the correct drivers so I am guessing that it will not detect is due to the fact my device has no build.prop.
I really DON'T want to call sony support unless I really have to, so any help would be beyond amazing.
Screenshot from PC Companion:
{
"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"
}
If you need ANYTHING, Video's Pictures, etc feel free to ask as I will try my best to help.
Grab the stock recovery (or the version of twrp) which is appropriate for your build.
Put the watch in fastboot and on your computer in a terminal window type
Code:
fastboot boot <recovery.img>
Then in recovery, install the Os you want.
You have two options. Use stock recovery and then factory reset. Or, use twrp and go all the way back to the 5.0.1 image. If nothing else works. The later will. Do not forget to factory reset after you roll back.
lekofraggle said:
Grab the stock recovery (or the version of twrp) which is appropriate for your build.
Put the watch in fastboot and on your computer in a terminal window type
Code:
fastboot boot <recovery.img>
Then in recovery, install the Os you want.
You have two options. Use stock recovery and then factory reset. Or, use twrp and go all the way back to the 5.0.1 image. If nothing else works. The later will. Do not forget to factory reset after you roll back.
Click to expand...
Click to collapse
Tried it, just reboots
Then you are using the wrong recovery. What did you build?
lekofraggle said:
Then you are using the wrong recovery. What did you build?
Click to expand...
Click to collapse
Well I think what happened is all of the partitions got messed up, does this watch use system.img? Because then I could flash that through FASTBOOT
UPDATE: I got twrp to boot but... It cannot mount any partitions
1619415 said:
Well I think what happened is all of the partitions got messed up, does this watch use system.img? Because then I could flash that through FASTBOOT
UPDATE: I got twrp to boot but... It cannot mount any partitions
Click to expand...
Click to collapse
The closest thing I have seen to a system.img is the roll back zip file of 5.0.1 in this thread
http://forum.xda-developers.com/smartwatch-3/general/guide-roll-watch-to-previous-software-t3176801
I also can't access my SDCard/Internal Storage
UPDATE: I just think I have no OS installed, nothing installed at all actually. So I think I just need to reinstall system and other important data
Okay so that is my guide. Use the 5.0.1 image. I think the issue is precisely that you have no system. A normal flash does not usually touch the boot loader or partition map. So, do not jump to that conclusion yet. If twrp does not work for you, try using the fast boot flash of the 5.0.1 Recovery image.
Which version of twrp worked for you?
lekofraggle said:
Okay so that is my guide. Use the 5.0.1 image. I think the issue is precisely that you have no system. A normal flash does not usually touch the boot loader or partition map. So, do not jump to that conclusion yet. If twrp does not work for you, try using the fast boot flash of the 5.0.1 Recovery image.
Which version of twrp worked for you?
Click to expand...
Click to collapse
The 5.0.1 twrp would not boot but, the 5.1.1 one does just does not mount anything and the stock recovery does not boot either. I did however try to adb sideload stuff but could not find a system.img.
So, what you should try to do is adb push the 5.01 file while booted in the 5.1.1 twrp.
Did you try the 5.1.1 stock recovery? I am not sure it will help even if you get it to boot.
lekofraggle said:
So, what you should try to do is adb push the 5.01 file while booted in the 5.1.1 twrp.
Did you try the 5.1.1 stock recovery? I am not sure it will help even if you get it to boot.
Click to expand...
Click to collapse
I already tried twrp, it can't mount any partitions
Did you try pushing from the computer?
Code:
adb push <originalsystem.zip> /sdcard
If so, what was the exact error you received?
lekofraggle said:
Did you try pushing from the computer?
Code:
adb push <originalsystem.zip> /sdcard
If so, what was the exact error you received?
Click to expand...
Click to collapse
Twrp can't mount anything at all, im guessing that it cannot create a folder on my internal storage. Adb sideload wont work either because it cannot mount
Again, what is the specific error you receive trying adb push (not sideload) after you boot to the somewhat working twrp?
lekofraggle said:
Again, what is the specific error you receive trying adb push (not sideload) after you boot to the somewhat working twrp?
Click to expand...
Click to collapse
error: device not found
Okay, so try adb devices and see if it shows up. If it does, you are correct and need to repartition. That is neither easy nor unrisky. It is easy to brick your device.
If it does not show up, you need to install the drivers. Twrp uses different adb drivers than the watch Os for some reason.
I think this is my main problem...
@lekofraggle
Potentially. What happened when you ran adb devices? You need to do that on your computer.
---------- Post added at 10:16 PM ---------- Previous post was at 10:15 PM ----------
Adb has different permissions than twrp.
Do a format of the system, recovery, userdata and then reinstall from a custom rom online
****************
* SENT FROM *
* A *
* MOD KING *
* DEVICE *
****************
lekofraggle said:
Potentially. What happened when you ran adb devices? You need to do that on your computer.
---------- Post added at 10:16 PM ---------- Previous post was at 10:15 PM ----------
Adb has different permissions than twrp.
Click to expand...
Click to collapse
Either it does not show up or... it just says "error: device not found"
Hi! Could you please explain if this ROM will be compatible with my smartphone? I'm not sure, I don't found it on the list on LineageOS website.
Well, someone need to compile it for our bv9600 - i also would appreciate it, but i don't have thoose skills...
Also, lenovo vibe c2
i am not even not able to root my device (blackview bv9600 pro) i don't think that you will be able to have any lineage rom also...
have anyone success to root this device?
giannhs_n said:
i am not even not able to root my device (blackview bv9600 pro) i don't think that you will be able to have any lineage rom also...
have anyone success to root this device?
Click to expand...
Click to collapse
jup, runs root - magisk
AMDFenics said:
jup, runs root - magisk
Click to expand...
Click to collapse
can you explain how did you get root? or give me a guide, all the internet guides i tried failed!
thanks
giannhs_n said:
can you explain how did you get root? or give me a guide, all the internet guides i tried failed!
thanks
Click to expand...
Click to collapse
simply follow this guide -> LINK
- allow OEM unlock in the dev-settings (hit 5 times build number to see)
- allow usb debugging
- reboot to fastboot
- send "fastboot devices" command
- send "fastboot oem unlock" -> acknowledge
- send "fastboot flashing unlock" -> acknowledge
- flash the twrp image "fastboot flash recovery name_of_the_image.img"
- reboot into twrp by power of the device
- after that press vol+ up and power button (if i remember correct.. ) to get into twrp
- now u need a sd-card (micro) put no verity opt encrypt on it and magisk
- Backup all partitions u find.
- format data partition to get the size
- install magisk
- install no verity opt...
reboot
BV9600 should be rooted. Took me serveral times to get it working, because u need directly after "Flashing unlock command" to get the twrp stuff done.
Credits
The TWRP.img comes from www.unofficialtwrp.com
The encryption disabler comes from @Zackptg5 all credits to him. THANKS -> his site LINK
Enjoy
AMDFenics said:
simply follow this guide -> LINK
- allow OEM unlock in the dev-settings (hit 5 times build number to see)
- allow usb debugging
- reboot to fastboot
- send "fastboot devices" command
- send "fastboot oem unlock" -> acknowledge
- send "fastboot flashing unlock" -> acknowledge
- flash the twrp image "fastboot flash recovery name_of_the_image.img"
- reboot into twrp by power of the device
- after that press vol+ up and power button (if i remember correct.. ) to get into twrp
- now u need a sd-card (micro) put no verity opt encrypt on it and magisk
- Backup all partitions u find.
- format data partition to get the size
- install magisk
- install no verity opt...
reboot
BV9600 should be rooted. Took me serveral times to get it working, because u need directly after "Flashing unlock command" to get the twrp stuff done.
Credits
The TWRP.img comes from www.unofficialtwrp.com
The encryption disabler comes from @Zackptg5 all credits to him. THANKS -> his site LINK
Enjoy
Click to expand...
Click to collapse
thanks for the detailed information,
can you also tell me your frimewire version also because i am not available to boot on recovery!
{
"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"
}
giannhs_n said:
thanks for the detailed information,
can you also tell me your frimewire version also because i am not available to boot on recovery!
View attachment 4705498
Click to expand...
Click to collapse
exact same version.
---------- Post added at 10:29 PM ---------- Previous post was at 10:27 PM ----------
First u need to go to fastboot mode, to unlock "OEM UNLOCK"
This is easy via adb
-> reboot fastboot
Did u install the correct driver? (ADB driver) is ur device listed?
i tried repacking it myself but with no luck so far, also tried various treble GSI, all booting on my BV9600Pro and basically working but mobile data and phone are broken so that's not an option for now
I don’t understand why unblock the bootloader at all if everything is installed on the MTK platform using the SP Flash Tool !?
Why these dances with adb and fastboot? if a everything is done much easier ...
You do not install the factory software using adb ? not ?? so why can't TWRP be installed and installed using the SP Flash Tool!? Why complicate things?
Root with sp Flash tool
Hi please Anyone could explain this procedure with Sp Flash Tool and post it?
serg2327 said:
I don’t understand why unblock the bootloader at all if everything is installed on the MTK platform using the SP Flash Tool !?
Why these dances with adb and fastboot? if a everything is done much easier ...
You do not install the factory software using adb ? not ?? so why can't TWRP be installed and installed using the SP Flash Tool!? Why complicate things?
Click to expand...
Click to collapse
Because the vendor (Blackview) locks the bootloader (like any other brand does) and does not allow installing any other recovery without it.!?
AMDFenics said:
Because the vendor (Blackview) locks the bootloader (like any other brand does) and does not allow installing any other recovery without it.!?
Click to expand...
Click to collapse
Is this a statement or a question? Sorry, I do not know English and I use a translator ..
II repeat once again, in order to install TWRP you do not need to unlock the bootloader!
it installs without problems using the SP Flash Tool
and this is not an assumption but a statement!
My first copy of the smartphone received TWRP. It was on my copy that all the first tests of TWRP and ROOT were conducted.
serg2327 said:
Is this a statement or a question? Sorry, I do not know English and I use a translator ..
II repeat once again, in order to install TWRP you do not need to unlock the bootloader!
it installs without problems using the SP Flash Tool
and this is not an assumption but a statement!
My first copy of the smartphone received TWRP. It was on my copy that all the first tests of TWRP and ROOT were conducted.
Click to expand...
Click to collapse
I'm glad to hear that it works that way to you. But that doesn't worked for me. So i wrote the way i took, to root. Let the others choose, wich way works for them. :fingers-crossed::good:
I am using another MTK device and SP FlashTool is great it lets you recover from any software brick. So I will advice people to use this method.
I am planning on buying bv9600 pro and having twrp ported and root is a good start to custom roms.
The touch driver issue on twrp should be easily solved with the good kernel module for the twrp. And official twrp support would be nice.
Subscribed to the thread will see where it goes.
hi guys, can you share a clean system twrp backup of bv9600? because my USB is damaged and i can not use sp flash tool to clean restore. thanks!
Hi, i try to root my bv9600 pro, but all i end up is on reboot the system restores to factory no TWRP or anything on it. I connected it to MTKdroidtools and it complains about a file /system/recovery-from-boot.p which restores recovery and obviously after it the system too.
Thanks for any help
edit: LOL nevermind, working fine now, don't know what was going wrong, in a last try just downloaded the latest stable magisk again. Thanks AMDFenics for the howto
Just one thing, can i get rid of this 5 sec. warning that the mobile is unlocked?
dark-wulf said:
Hi, i try to root my bv9600 pro, but all i end up is on reboot the system restores to factory no TWRP or anything on it. I connected it to MTKdroidtools and it complains about a file /system/recovery-from-boot.p which restores recovery and obviously after it the system too.
Thanks for any help
edit: LOL nevermind, working fine now, don't know what was going wrong, in a last try just downloaded the latest stable magisk again. Thanks AMDFenics for the howto
Just one thing, can i get rid of this 5 sec. warning that the mobile is unlocked?
Click to expand...
Click to collapse
Maybe there is a way, but i don't know him. It is a common way for many manufacturer, to say, "here u did something you are not supposed too"
https://www.mediafire.com/file/0j0bx6cb0cb58f5/BV9600Pro_30042019_full.zip/file
Latest Firmware (04.2019) Clean SP Flash tool Backup
Kernel source code for the Motorola Moto G7 Play is now available
(twrp available soon)
https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-PPY29.68-28
edit: all credits @scritch007 @Alberto97 @vache
(i completely failed on building toolchains and was miles away from twrp, i have nothing to do with it)
please report testing, don't forget to attach log files,
hit :good: thanks button to scritch007 (not me)
@scritch007 link to following up is posted here as soon as you opened the thread
Can't wait get back to custom and root.
Any news on this
Good News and Bad news.
I've got a booting recovery, but I managed to brick my device. Now I'm stuck in EDL mode.
Big thanks to @Alberto97, @vache for their help
As always if you want to try this out I cannot be held responsible for any damage or if you brick your device
So if you want to try this out, be aware it might not be without consequences
It requires to flash the dtbo.img
Code:
fastboot flash dtbo dtbo.img
And then you can
Code:
fastboot boot recovery.img
If you only try to fastboot boot recovery.img (without flashing the dtbo.img before) you should get into recovery but screen will be black because not recognized but adb should be available.
As for the Moto G7 it requires to be installed from recovery. You should most probably copy the current slot partitions to the second one, so that you don't brick the device. But I can't say for sure this is the only issue.
This is when I bricked my device. I don't really know why but I think it's because the second slot partitions are more or less empty, because I never done an OTA and the slot was switched so when I booted it starts on nothing. I didn't have time to test anything, I think encryption was also not working correctly.
Source code
Device tree
Kernel
There might be some missing use cases if device have different touchscreen then mine. It should be patched here
To build the kernel you have to use the following command line
Code:
make -j4 -C $kernel O=$kernel_out_dir DTC_EXT=dtc CONFIG_BUILD_ARM64_DT_OVERLAY=y CROSS_COMPILE=$bcross ARCH=arm channel_defconfig
make -j4 -C $kernel O=$kernel_out_dir DTC_EXT=dtc CONFIG_BUILD_ARM64_DT_OVERLAY=y CROSS_COMPILE=$bcross ARCH=arm
where
Code:
bcross=$TWRP_FOLDER/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9/bin/arm-linux-androidkernel-
kernel is the folder which contains the kernel
kernel_out_dir is the directory where the kernel will be built (out of tree built)
Binaries:
https://drive.google.com/open?id=1VEUuI42xTBrVdZCnqinEoskbEh_XUm8U
dtbo.img isn't uploaded yet, but I'll upload it on Monday when I can reach my other computer
What works:
Since I bricked it nearly immediately I didn't have time to test much.
Tested on a XT1952-? RETEU version used. Phone was running CHANNEL_RETEU_PPY29.105-57 build.
boots
Mounting the various partitions
Hoping I can get my phone fixed, I contacted Motorola support.
Uploaded the dtbo.img file, that I used, this should make the screen work now.
---------- Post added at 04:15 PM ---------- Previous post was at 03:56 PM ----------
I need someone willing to help me trying to make my phone work again.
I've found the following instructions for the z3-play
Can someone do provide me with the loader.img
To do that I need someone with a XT1952-1 device running CHANNEL_RETEU_PPY29.105-57 just to be sure we have the same phone
This person should try to boot the twrp I provided just above. and then run the dd command
Code:
fastboot boot recovery.img
dd if=/dev/block/mmcblk0 of=/sdcard/loader.img bs=1024 count=168960
exit
adb pull /sdcard/loader.img
You can change /sdcard to /external_sd (I don't remember the full name)
Running twrp like this shouldn't make any harm to the device.
Then you can pm me in order to send me the file or upload it anywher.
Thanks for helping me, hoping this does work on the Moto G7 Play
Is this a AB device I just bought it today and it's on it's way.
Segue o link para a firmware
Follow the link to the firmware
https://mirrors.lolinet.com/firmware/moto/channel/official/RETEU/
scritch007 said:
Uploaded the dtbo.img file, that I used, this should make the screen work now.
---------- Post added at 04:15 PM ---------- Previous post was at 03:56 PM ----------
I need someone willing to help me trying to make my phone work again.
I've found the following instructions for the z3-play
Can someone do provide me with the loader.img
To do that I need someone with a XT1952-1 device running CHANNEL_RETEU_PPY29.105-57 just to be sure we have the same phone
This person should try to boot the twrp I provided just above. and then run the dd command
Code:
fastboot boot recovery.img
dd if=/dev/block/mmcblk0 of=/sdcard/loader.img bs=1024 count=168960
exit
adb pull /sdcard/loader.img
You can change /sdcard to /external_sd (I don't remember the full name)
Running twrp like this shouldn't make any harm to the device.
Then you can pm me in order to send me the file or upload it anywher.
Thanks for helping me, hoping this does work on the Moto G7 Play
Click to expand...
Click to collapse
InfinityXDA said:
Is this a AB device I just bought it today and it's on it's way.
Click to expand...
Click to collapse
Yes it's a/b
Rickjfer said:
Follow the link to the firmware
https://mirrors.lolinet.com/firmware/moto/channel/official/RETEU/
Click to expand...
Click to collapse
Thanks but this is not what I'm looking for. The device is hardbricked so it doesn't find any bootloader to start. I can't go into fastboot
The loader.img I'm asking for is a partial copy of the internal memory hoping it can think it's bootable and then I'll have fastboot and I can reflash the bootloader on the internal memory.
I'm not even sure our device can start from sdcard.
Another solution would be a valid blankflash
Great news for me and bricked moto g7 Play. I managed boot from the sdcard the River variant of the bootloader. I am then stuck because it only takes river's (Moto G7) files but this means that with a proper channel version of the loader.img I can hopefully manage to fix it.
Eagerly waiting for a friendly Moto G7 Play user to backup the Emmc and upload it.
{
"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"
}
scritch007 said:
Great news for me and bricked moto g7 Play. I managed boot from the sdcard the River variant of the bootloader. I am then stuck because it only takes river's (Moto G7) files but this means that with a proper channel version of the loader.img I can hopefully manage to fix it.
Eagerly waiting for a friendly Moto G7 Play user to backup the Emmc and upload it.
View attachment 4772083
Click to expand...
Click to collapse
Hello,
I hope I can help. Currently I am not allowed to post external links (to the file). Maybe the URL works like this.
The spaces around "://" have to be removed. The file is an image of a g7 play...
I keep my fingers crossed
https :// drive.google.com/file/d/1p6AFbt9OX2WdP8NjTWAJN0R6tsTO9Bna/view?usp=sharing
realsine said:
Hello,
I hope I can help. Currently I am not allowed to post external links (to the file). Maybe the URL works like this.
The spaces around "://" have to be removed. The file is an image of a g7 play...
I keep my fingers crossed
https :// drive.google.com/file/d/1p6AFbt9OX2WdP8NjTWAJN0R6tsTO9Bna/view?usp=sharing
Click to expand...
Click to collapse
Thanks you very much. The loader.img does boot, but it doesn't want to flash my gpt.bin for the reteu. I think it's because there is a signature in the EFI partition.
It seems like you are running a RETAIL version. Don't know which version though.
Please can someone with a xt1952-1 RETEU do the same thing.
scritch007 said:
Thanks you very much. The loader.img does boot, but it doesn't want to flash my gpt.bin for the reteu. I think it's because there is a signature in the EFI partition.
It seems like you are running a RETAIL version. Don't know which version though.
Please can someone with a xt1952-1 RETEU do the same thing.
Click to expand...
Click to collapse
Hello,
I pulled the data after an OTA update. I guess it's this version:
XT1952-1_CHANNEL_RETEU_9.0_PPY29.105-57_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Maybe I was in a state where the bootloader had a problem (lock / unlock). I will repeat the procedure (after when I have time) and deploy the thing again.
some news on this subject
Phone still dead trying everything I can. Or I'll have to buy a new one. So I hope someone takes over
scritch007 said:
Phone still dead trying everything I can. Or I'll have to buy a new one. So I hope someone takes over
Click to expand...
Click to collapse
Did you enable oem unlocking before flashing twrp? The screenshot of your bootloader indicates that you didn't. (It could be wrong though since that's a different bootloader you're running.) If that's the case, then your emmc will be set to read only and you can't get out of it without Jtag or firehose. A blank flash file might work, but I doubt you guys have one out yet. This has happened to a few people in the G6 Play forums already.
Edit: What's your device code name? I'll try to help you out.
Spaceminer said:
Did you enable oem unlocking before flashing twrp? The screenshot of your bootloader indicates that you didn't. (It could be wrong though since that's a different bootloader you're running.) If that's the case, then your emmc will be set to read only and you can't get out of it without Jtag or firehose. A blank flash file might work, but I doubt you guys have one out yet. This has happened to a few people in the G6 Play forums already.
Click to expand...
Click to collapse
Thanks for the answer, yes my phone had an unlocked bootloader (OEM enabled for that), otherwise I wouldn't have been able to boot twrp. The issue seems to be the A/B error where second bank has never been flashed before, and twrp changes for the new slot (Might be something else but this seems to be an issue for a lot of devices). And bam no bootloader bricked. Although it seems to be fixed with the loader.img for G7Plus devices, in my case I might have broken too much the internal emmc.
The fastboot even though booted from the SDCard also initializes the internal eMMC and seems to look in there for the unlock information. Since nothing can be read it fallbacks to oem_lock .
scritch007 said:
Thanks for the answer, yes my phone had an unlocked bootloader (OEM enabled for that), otherwise I wouldn't have been able to boot twrp. The issue seems to be the A/B error where second bank has never been flashed before, and twrp changes for the new slot (Might be something else but this seems to be an issue for a lot of devices). And bam no bootloader bricked. Although it seems to be fixed with the loader.img for G7Plus devices, in my case I might have broken too much the internal emmc.
The fastboot even though booted from the SDCard also initializes the internal eMMC and seems to look in there for the unlock information. Since nothing can be read it fallbacks to oem_lock .
Click to expand...
Click to collapse
I've seen this with A/B devices. You might want to check this thread out. This looks relevant to your situation, and it might be promising. 1st & 2nd post.
Just saw this thread. Check it out. https://forum.xda-developers.com/g7-play/development/recovery-dirty-ported-twrp-g7-play-t3947205
scritch007 said:
It requires to flash the dtbo.img
Code:
fastboot flash dtbo dtbo.img
And then you can
Code:
fastboot boot recovery.img
If you only try to fastboot boot recovery.img (without flashing the dtbo.img before) you should get into recovery but screen will be black because not recognized but adb should be available.
Click to expand...
Click to collapse
I followed your instructions. I can get to TWRP recovery. But installing magisk doesn't work. And I get the "bad key" screen. TWRP recovery isn't permanent either.
Firstly, when plugging my 7t in to my windows 10 PC, I am asked to choose which mode to go in within usb preferences, as I did previously in order to achieve and ADB driver connection I chose file transfer.......
this didn't work for some reason, only when in MIDI did I get a confirmation with adb devices.....even though there is still no sign of adb interface in device manager.....
any ideas? I can get adb connection with MIDI but is this good enough to flash recoveries/boot images etc....?
I tried to flash twrp and I could successfully boot into twrp directly via fastboot but twrp couldn't seen any of my storage, despite having all security methods turned off...
all i want to do is gain root access but I am having no joy....
ever since android 10 rooting anything for me has been a pain in the ass......truly fed up....it shouldn't be this hard......
I also flashed a patched boot image in an attempt to gain root access but it all did was break my wifi........which i fixed by copying over the latest image and installing locally......
please HELP....
Everything about this issues is already said in this forum.
Try looking at this topic here:
https://forum.xda-developers.com/oneplus-7t/development/recovery-unofficial-twrp-recovery-t3976961
ontwykende said:
Try looking at this topic here:
https://forum.xda-developers.com/oneplus-7t/development/recovery-unofficial-twrp-recovery-t3976961
Click to expand...
Click to collapse
sweet, ill check it out.....
ontwykende said:
Try looking at this topic here:
https://forum.xda-developers.com/oneplus-7t/development/recovery-unofficial-twrp-recovery-t3976961
Click to expand...
Click to collapse
It would seem that TWRP is a no go, for awhile at least.....
anyone managed to gain root access by flashing a patched boot.img?
mediaman123 said:
It would seem that TWRP is a no go, for awhile at least.....
anyone managed to gain root access by flashing a patched boot.img?
Click to expand...
Click to collapse
Lots of people have. Just boot your version and use magisk to direct install and reboot then you have root
Josh McGrath said:
Lots of people have. Just boot your version and use magisk to direct install and reboot then you have root
Click to expand...
Click to collapse
Normally I would be able to carry out such tasks but because I now feel so fed up with it all could I trouble you to tell my step by step how that is done.....?
many thanks..
mediaman123 said:
Normally I would be able to carry out such tasks but because I now feel so fed up with it all could I trouble you to tell my step by step how that is done.....?
many thanks..
Click to expand...
Click to collapse
I made a tool to install the latest ADB, Fastboot and USB drivers for windows, its very easy to use, just double click the file to start the installation process
you can see it here:
https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445
Screenshot:
{
"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"
}
fawazahmed0 said:
I made a tool to install the latest ADB, Fastboot and USB drivers for windows, its very easy to use, just double click the file to start the installation process
you can see it here:
https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445
Screenshot:
Click to expand...
Click to collapse
I can operate that fine, its just how to obtain boot.img files etc, patch them and so on..
mediaman123 said:
I can operate that fine, its just how to obtain boot.img files etc, patch them and so on..
Click to expand...
Click to collapse
Oh, I thought, you are have issues with adb, and for root, you just have to flash magisk using twrp
fawazahmed0 said:
Oh, I thought, you are have issues with adb, and for root, you just have to flash magisk using twrp
Click to expand...
Click to collapse
This isn't functional at the minute as TWRP, whether its flashed or booted from, cant get past the encryption.......it cant see/mount the internal storage....
mediaman123 said:
This isn't functional at the minute as TWRP, whether its flashed or booted from, cant get past the encryption.......it cant see/mount the internal storage....
Click to expand...
Click to collapse
You will have to wipe the data and then twrp can access internal storage.
This is how I did (in my phone, which is not Oneplus, but the process remain same for all phones), boot to fastboot mode and type this:
fastboot -w
Now, boot your phone to recovery mode:
(Now take complete twrp backup of your phone, and save it in your pc, before proceeding futher)
flash DM verity disabler: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
flash magisk: https://github.com/topjohnwu/magisk_files/raw/canary/magisk-release.zip
Now boot the phone back to OS and you will have root access
fawazahmed0 said:
You will have to wipe the data and then twrp can access internal storage.
This is how I did (in my phone, which is not Oneplus, but the process remain same for all phones), boot to fastboot mode and type this:
fastboot -w
Now, boot your phone to recovery mode:
(Now take complete twrp backup of your phone, and save it in your pc, before proceeding futher)
flash DM verity disabler: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
flash magisk: https://github.com/topjohnwu/magisk_files/raw/canary/magisk-release.zip
Now boot the phone back to OS and you will have root access
Click to expand...
Click to collapse
thanks for this......want to try and avoid wiping if possible but if I really want root I will do it.....
what does the command fastboot -w do?
mediaman123 said:
thanks for this......want to try and avoid wiping if possible but if I really want root I will do it.....
what does the command fastboot -w do?
Click to expand...
Click to collapse
it wipe's the data
mediaman123 said:
This isn't functional at the minute as TWRP, whether its flashed or booted from, cant get past the encryption.......it cant see/mount the internal storage....
Click to expand...
Click to collapse
fawazahmed0 said:
You will have to wipe the data and then twrp can access internal storage.
This is how I did (in my phone, which is not Oneplus, but the process remain same for all phones), boot to fastboot mode and type this:
fastboot -w
Now, boot your phone to recovery mode:
(Now take complete twrp backup of your phone, and save it in your pc, before proceeding futher)
flash DM verity disabler: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
flash magisk: https://github.com/topjohnwu/magisk_files/raw/canary/magisk-release.zip
Now boot the phone back to OS and you will have root access
Click to expand...
Click to collapse
TWRP is not functional at the moment, so stay away from it.
The only way to root right now is to use the patch boot image method.
Lossyx said:
No don't do this.... This is not about encryption at all. It's about the major partitioning changes that has happened in Android 10. Wiping the system will just make everything worse.
Avoid using TWRP at all.
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
Oh, I didn't know this phone was on Android 10, Thanks for letting me know.
TWRP doesn't support Android 10 yet.
You can see it here
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
Actually there is a twrp compiled for this phone, but that doesn't work , you can see the messages in thread:
https://forum.xda-developers.com/oneplus-7t/development/recovery-unofficial-twrp-recovery-t3976961
The steps I told, was for Android 9 and earlier devices, I assumed, this is an old device.
@mediaman123, So please wait, until twrp starts supporting the Android 10.
And for rooting, I am not sure, whether magisk supports this new phone or not.
Maybe @Lossyx can help you on that.
https://forum.xda-developers.com/oneplus-7t/how-to/guide-how-to-root-oneplus-7t-twrp-t3979307
Sent from my OnePlus7TPro using XDA Labs
Lossyx said:
https://forum.xda-developers.com/oneplus-7t/how-to/guide-how-to-root-oneplus-7t-twrp-t3979307
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
Seen this, however my device, the European version, is running on 10.0.6.....
The only boot images available with that post is the 10.0.3...
wouldn't feel comfortable using them.....
I would like to know how to extract the stock boot image from either the firmware file or the phone itself...
mediaman123 said:
Seen this, however my device, the European version, is running on 10.0.6.....
The only boot images available with that post is the 10.0.3...
wouldn't feel comfortable using them.....
I would like to know how to extract the stock boot image from either the firmware file or the phone itself...
Click to expand...
Click to collapse
You can go ahead and just fastboot boot them. If it works then just proceed, if it doesn't, just hold volume up+down and power button. (To boot into fastboot or restart phone)
Nothing will change in the system because it only boots a temporary image.
If your want to extract your own boot image you can use this tool.
https://github.com/cyxx/extract_android_ota_payload
Sent from my OnePlus7TPro using XDA Labs
Lossyx said:
You can go ahead and just fastboot boot them. If it works then just proceed, if it doesn't, just hold volume up+down and power button. (To boot into fastboot or restart phone)
Nothing will change in the system because it only boots a temporary image.
If your want to extract your own boot image you can use this tool.
https://github.com/cyxx/extract_android_ota_payload
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
So if it boots an older image successfully I can move it over to the phone to patch to then flash it or use the already patched one and flash that...?..
I AM NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR DEVICE YOUR WARRANTY MAY BE VOID AFTER THIS PROCEDURE
UPDATED 06/04/23
You are now on your way to degoogle your Realme GT Master edition!
1. Figuring out your device model
This guide was tested on the RMX3363 with LineageOS built for RMX3360
Click to expand...
Click to collapse
2. Now let's figure out what you need to download:
Deep testing app (this can be found on the realme forums, some versions may not work)
Click to expand...
Click to collapse
ADB/Fastboot (always download from the official site/repo) [15 seconds ADB installer]
Click to expand...
Click to collapse
Magisk apk 25.2 (always download from the official site/repo) [github repo]
Click to expand...
Click to collapse
Your custom ROM, i recommend using LineageOS
LineageOS lunaa build [pjgowtham releases]
Click to expand...
Click to collapse
LineageOS recovery [you must use THIS recovery if you are installing the "lunaa" build]
Click to expand...
Click to collapse
3. Now you need to
enable Developer options (clicking build number multiple times)
Click to expand...
Click to collapse
enable USB Debugging
Click to expand...
Click to collapse
enable OEM Unlocking in developer options
Click to expand...
Click to collapse
4. Let's start!
Plug your phone into your pc usb
Click to expand...
Click to collapse
Install and launch the Deep test apk
Click to expand...
Click to collapse
Restart into fastboot mode (fastboot reboot bootloader)
Click to expand...
Click to collapse
Now from the pc side
Code:
fastboot devices
Code:
fastboot flashing unlock
In the fastboot menu you will be prompted with 2 selections:
DO NOT UNLOCK THE BOOTLOADER
UNLOCK THE BOOTLOADER
Navigate to "unlock the bootloader" with volume buttons and confirm with power button
YOUR DEVICE DATA WILL BE WIPED
Now your device bootloader is unlocked!
Q: How can i check if my bootloader is unlocked?
A: Go into developer settings and find the "OEM Unlock" slider, it should be locked to the right
5. Custom ROM
Restart into fastboot
Click to expand...
Click to collapse
Run code:
Code:
fastboot devices
Code:
fastboot flash boot_a recovery.img
Code:
fastboot flash boot_b recovery.img
Restart into recovery
Click to expand...
Click to collapse
Launch ADB sideload ("Apply update" then "Apply from ADB")
Click to expand...
Click to collapse
Run code
Code:
adb sideload <rom name>.zip
After the sideload you can start using your phone normally, or:
6. Patch your custom ROM with Magisk
CAN SKIP IF YOU DO NOT WANT ROOT PRIVILEGES
Extract boot.img from you custom ROM
Click to expand...
Click to collapse
How do you do this?
Use the LineageOS extractor [github]
Click to expand...
Click to collapse
Run code:
Code:
py extract.py <rom name>.zip
Find "boot.img" in the "output" folder and patch with Magisk (if you use the .apk you have to push the file on an android device, install magisk on it and then pull it back to your pc)
Click to expand...
Click to collapse
Code:
fastboot flash boot_(a/b) patched-boot.img
Now you have root privileges!
Congratulations, maikuITA! Your simplified guide on how to unlock the RMX336X bootloader is very helpful to the community. Your effort to make the process easier for users is truly appreciated. Keep up the great work!
Great basic tutorial Thanks...But here help me out please I already unlocked bootloader and installed custom rom (pixelplus ui), now just want to have root so how to do it?
after extracting pixel plus ui and payload dumper for my device I got no recovery img instead I got this files..image below :
{
"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"
}
so like what to patch and flash?
ASIFPIAL said:
Great basic tutorial Thanks...But here help me out please I already unlocked bootloader and installed custom rom (pixelplus ui), now just want to have root so how to do it?
after extracting pixel plus ui and payload dumper for my device I got no recovery img instead I got this files..image below :
View attachment 5878259
so like what to patch and flash?
Click to expand...
Click to collapse
You need to patch with Magisk and then flash back boot.img and vendor_boot.img
maikuITA said:
You need to patch with Magisk and then flash back boot.img and vendor_boot.img
Click to expand...
Click to collapse
Patching and flashing only boot.img worked
ASIFPIAL said:
Patching and flashing only boot.img worked
Click to expand...
Click to collapse
It's fine, it was only boot.img for my RMX
After downloading recovery tool i got few files instand of only recovery.img can u help me what i need to flash from this
If you have installed LOS recovery, to have root privileges that's easier to change Magisk extension from apk to zip and flash it by adb sideload, no need to extract boot.img.
enonaw said:
If you have installed LOS recovery, to have root privileges that's easier to change Magisk extension from apk to zip and flash it by adb sideload, no need to extract boot.img.
Click to expand...
Click to collapse
I got recovery tool in zip dont in img file where u have boot.img and few others
KSTT03 said:
I got recovery tool in zip dont in img file where u have boot.img and few others
Click to expand...
Click to collapse
Where did you get LOS recovery zip ? You have .img files into it and a script with commands : it couldn't be easier.
LOS recovery : here
And why did you quote me because I was talking about Magisk to get root, which has nothing to do with recovery ?
i cant find any working deep test apk. can someone provide me a link or anything?
ajamboboy said:
i cant find any working deep test apk. can someone provide me a link or anything?
Click to expand...
Click to collapse
If you are on RUI4
enonaw said:
If you are on RUI4
Click to expand...
Click to collapse
thanks will try
Hello,
After trying the step 5, my phone broke.
This is the command I typed in adb :
So, I used the flash.bat in the lunaa recovery. All seems fine but now my phone is in the Fastboot mode page where I can choose between : START, Restart bootloader, Recovery mode, Show barcode, Power off.
If I choose "start", restart bootloader, recovery mode, I just return on the same screen. Can't find my phone in adb window.
What should I do ?
Thanks
Restored to stock rom by following those lines : https://forum.xda-developers.com/t/...360-unlcoked-only-access-to-fastboot.4479597/
Will try LOS recovery tomorrow.
Worked on 2nd try. Got an "cannot read" error when I had to sideload lineage ROM, I just needed to use Large Adress Aware to patch "adb.exe".
Any one who use Los can you post you screen on time
I hate this phone everything is good but software is bad rui 4 battery life less than 4 hours on normal use thats not acceptable before i was getting 6-7 hours normally
sym_m said:
Any one who use Los can you post you screen on time
I hate this phone everything is good but software is bad rui 4 battery life less than 4 hours on normal use thats not acceptable before i was getting 6-7 hours normally
Click to expand...
Click to collapse
(Edited : statistics removed because under calculation)
enonaw said:
(This corresponds to the reality for me with LOS 20230415, I never managed to discharge my battery completely in 1 day. PS : no games)
View attachment 5904443
Click to expand...
Click to collapse
Its less than expected u cant use lower frimware? The rui frimware was the best in terms of battery life
sym_m said:
Its less than expected u cant use lower frimware? The rui frimware was the best in terms of battery life
Click to expand...
Click to collapse
LOS uses the RUI firmware. But I admit that I had more autonomy with LOS CXX (RUI3) firmware than with LOS FXX (RUI4) firmware.
I also noticed that the battery discharges quickly when using on the move (changing 5G/4G/3G antennas). Less when the network is fixed. And the 5G network is the least consuming (faster data exchange so less used chip ?)
You can try to do a calibration :
*undisturbed
Don't trust the estimated data I posted, I had just installed the app and the range is increasing. I'll give you some numbers after the weekend.