Develop Bugs

[Q] m8_dugl (M8 Dual SIM) boots only in bootloader

Hello everyone,
I really could need some help. I'm new to this forum and new to "rooting" an android device. I did a lot of reading before I made my first try, but how it seems not enough :crying:.
I followed the instructions in this thread. Everything worked as described just fine and I didn't get any errors. I did the following:
1) Unlock the bootloader
2) Flash custom recovery from fastboot - fastboot flash recovery openrecovery-twrp-2.8.3.0-m8.img
3) Flash boot.img from fastboot - fastboot flash boot boot.img
4) Fastboot erase cache - fastboot erase cache
5) Boot into custom recovery and flash root and busybox
6) reboot into bootloader
7) flash stock recovery - fastboot flash recovery stock_recovery.img
8) reboot device
The last step doesn't work. I'm stuck in the bootloader. Every time I try to reboot the device, the bootloader starts. When I choose "HBOOT" I get the following messages:
{
"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"
}
Now I think, I did not realize that dual sim version of the m8 is different from the single sim version. Am I right here? Or did I just miss something? Is there any way to fix this and get my device working again? Do I need a boot.img for the m8_dugl? Can perhaps anyone provide it? Every help is really appreciated! I'm totally stuck here
Many thanks in advance
Guss

Problem solved with boot.img from this Post. Thanks to Captain_Throwback.

Installing TWRP Problem

I have uncloked bootloader and I Flashed TWRP Recovery via ADB and when I send comand "adb reboot recovery" I have the Android guy (SS) I drop SS with Adb comand prompt too
{
"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"
}

Domol™ said:
I have uncloked bootloader and I Flashed TWRP Recovery via ADB and when I send comand "adb reboot recovery" I have the Android guy[/IMG]
Click to expand...
Click to collapse
Hey I had this exact same problem just a few moments ago. I didn't necessarily fix it but I found a different way of installing TWRP:
Basically what I did was temporarily boot into the recovery image I had (instead of properly flashing it) and then flashed a zip version of the recovery which works permanently.
To do that, go into the bootloader as normal (adb reboot bootloader) and then use [fastboot boot {filename}.img] (so replace filename with whatever file you have) to boot into the recovery temporarily, then flash the recovery zip.
Here's the link to the zip I used: https://www.androidfilehost.com/?fid=24407100847292484
UPDATE: OK turns out after a few reboots the recovery went back to not working, but I did try another method which definitely works. Temporarily boot into the recovery image as above, but this type install a Supersu zip. This will root the phone. Then boot into the phone as normal, install Flashify from the Play Store and use that to install the recovery image (which you should move onto the phone).
Here are some links:
Supersu zip I used: http://download.chainfire.eu/supersu-stable
Flashify: https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en_GB

System update today

{
"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"
}
I'm rooted and running ex kernel
I'm assuming I DO NOT want to apply this update lest I lose root and kernel ??
Sent from my Pixel XL using XDA-Developers Legacy app

It will fail. You should install the update and then reroot and rekernel. Just grab the full image, edit the flashall bat file and remove the-w to save your data.

jk8260 said:
DO NOT DO THIS IF YOU DO NOT KNOW WHAT YOU ARE DOING,
OR AT LEAST DO NOT BLAME ME WHEN YOU PHONE STARTS ON FIRE
- Started with 8.0 August, SU rooted with SUHide on TMO
(working Substratum, Adaway and Android Pay)
- Downloaded September Factory Image
marlin-opr1.170623.026-factory-1ed9b4b2.zip
- Unzip factory image to \marlin-opr1.170623.026\
- Removed the -W from the FlashAll.bat
- Copy \platform-tools\ folder to \marlin-opr1.170623.026\ (so you have adb & fast boot in same folder as flash-all.bat)
- Connect Pixel to PC USB
- open command prompt in \marlin-opr1.170623.026\
- check you can see the pixel
adb devices
- Boot the device into bootloader
adb reboot bootloader
- Run the Flash-All.bat (phone will reboot several times)
- Once done it will reboot to system
If you want root, re-root again the same as before, works fine...
used - ([Guide] How to systemlessly root your Pixel XL on Android 8.0 (SuperSU) ) in this forum
I still have my substratum themes intact, everything is working smooth.
Click to expand...
Click to collapse
I used this method provided by jk8260. Make sure you download the September image that applies to your phone.

Is marlin-opr1.170623.026 the one that works with Verizon's Pixel XL?
Edit: Maybe nevermind. Verizon's website says OPR3.170623.007.
Source: https://www.verizonwireless.com/support/google-pixel-xl-update/

How to upload the original build.prop file?

Hey,
I made root on my Shield TV 2017 16GB. All worked great.
I decided to edit the bulid.prop file to change the device name, but I don't think I did everything right.
I made a copy of this file on a PC before editing.
The trouble is that the device does not start. The Nvidia logo and the animation of the android logo are shown, which loads indefinitely.
I started the menu with A + B. I chose option 2 (Boot recoovery kaenel) and the second menu came up.
I chose (apply upade from ADB).
ADB detects the device in "sideload" mode.
Can I upload the file itself?
Do I need to restore the entire system?
Sorry for my bad English.
Best regards,
Menu 1
{
"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"
}
Menu 2

use twrp to push the build.prop to system..
if u cant figure it out then flash stock and start over
you can only flash official updates through stock recovery and adb sideload

elliwigy said:
use twrp to push the build.prop to system..
if u cant figure it out then flash stock and start over
you can only flash official updates through stock recovery and adb sideload
Click to expand...
Click to collapse
Thank you. I was able to upload files using ADB Sideload.
The system started and works as it should.

Root Realme 9 4G (RMX3521) Without Custom Recovery

Hello,
As we all know there is no Custom Recovery available yet for our device. I decided to root the device with patched_boot.img.
I am able to root my Realme 9 4G successfully. I am sharing the procedure if someone like me, who cannot use a android mobile without root can follow the steps to root his Realme 9.
Before starting Make sure you are on RMX3521_11_A.31.
As the attached boot.img files are only for RMX3521_11_A.31.
To check your OS version Go to Settings > About device > Version and Match your Build Version. It should be RMX3521_11_A.31
First of all you have to unlock the bootloader.
Follow this Guide to unlock your bootloader.
Once your Bootloader is Unlocked. Follow the steps below
1. Download the magisk_Patched_boot.img from attachment and move it your PC.
2. Reboot your device into bootloader.
3. Open cmd in adb & fastboot directory and type the command
Code:
fastboot flash boot <drag magisk_patched_boot.img here>
And press enter.
4. Now restart your device by entering the command
Code:
fastboot reboot
5. Download the Magisk Manager and install it.
Your Device is Rooted Now. Make sure to disable the auto software update to avoid getting bootloop.
{
"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"
}

Btw there is an unofficial custom recovery for this device. It works and is tested. Here's the github link; https://github.com/cd-Crypton/custom_recovery_tree_realme_messi