Develop Bugs

Messed up kernel install

I wanted to try Merruk's kernel so I download the 4 files that are to be used. I flashed KernelUpdate.zip first and rebooted twice. A friends required urgent help so i didnt continue the process. After waking up in the morning, I decided to continue the process. I flashed the next file i was supposed to after formatting /cache and Dalvik cache.
Now i cant boot. The phone stay stuck at the galaxy y splsh screen. I can boot into recovery. It says /cache/recovery/log cant be open. Also, it cant mount /cache/recovery/last_log
Cant open /cache/recovery/last_log
I have ADB but it seems I didnt enable the USB debuggin option. If that was possible, I could have flashed a stock kernel and tried again.

Are you sure you cant enter download mode (HOLD power+home+volume DOWN)? Remove backcase if you have, remove the battery , keep aside for 5 min, then put it back and hold the download mode combination

DiGtal said:
I wanted to try Merruk's kernel so I download the 4 files that are to be used. I flashed KernelUpdate.zip first and rebooted twice. A friends required urgent help so i didnt continue the process. After waking up in the morning, I decided to continue the process. I flashed the next file i was supposed to after formatting /cache and Dalvik cache.
Now i cant boot. The phone stay stuck at the galaxy y splsh screen. I can boot into recovery. It says /cache/recovery/log cant be open. Also, it cant mount /cache/recovery/last_log
Cant open /cache/recovery/last_log
I have ADB but it seems I didnt enable the USB debuggin option. If that was possible, I could have flashed a stock kernel and tried again.
Click to expand...
Click to collapse
just flash back to stock via odin
i advise you not to use the "ext4.zip"
use only the system 1.0.8 zip <-- extract to sdcard

hitme987 said:
Are you sure you cant enter download mode (HOLD power+home+volume DOWN)? Remove backcase if you have, remove the battery , keep aside for 5 min, then put it back and hold the download mode combination
Click to expand...
Click to collapse
So THATS how you enter download mode
leodasal2 said:
just flash back to stock via odin
i advise you not to use the "ext4.zip"
use only the system 1.0.8 zip <-- extract to sdcard
Click to expand...
Click to collapse
Well, I flashed my backup and it rebuilt the /cache. All is fine. Thank you.
A new problem has risen. I was trying to flash Creed v4.0.
I had Merruk's Kernel.
I did a reset and tried flashing the ROM. It started wiping the /system partition and came across with an error in /boot(Error 7). Im guessing its due to the kernel. It aborted.
I tied again by doing a data reset again thinking that there might have be a random error in the wiping process.
It started cleaning /data. The progress bar never moved. I waited for 15 mins and did a battery pull. When i try to boot into the recovery mode, it stays at the Galaxy Y logo.
Dowload mode works. Adb doesnt detect my device though. I wonder why.

DiGtal said:
So THATS how you enter download mode
Well, I flashed my backup and it rebuilt the /cache. All is fine. Thank you.
A new problem has risen. I was trying to flash Creed v4.0.
I had Merruk's Kernel.
I did a reset and tried flashing the ROM. It started wiping the /system partition and came across with an error in /boot(Error 7). Im guessing its due to the kernel. It aborted.
I tied again by doing a data reset again thinking that there might have be a random error in the wiping process.
It started cleaning /data. The progress bar never moved. I waited for 15 mins and did a battery pull. When i try to boot into the recovery mode, it stays at the Galaxy Y logo.
Dowload mode works. Adb doesnt detect my device though. I wonder why.
Click to expand...
Click to collapse
There is no Creed 4 for galaxy y...re flash to stock and flash Creed 3.5

I cant boot into recovery. How do I use the download mode to do so?
Edit: I installed the correct drivers for my phone while it was trying to restart(it didnt ofcourse). I booted into download mode and connected odin. Odin is not showing any signs of it connecting to the phone.
Edit2: Got it working(v1.85). I need bootloader, CSC, Modem and phone tar balls. i downloaded 2 rar files but they dont have Phone and bootloader tar balls

DiGtal said:
I cant boot into recovery. How do I use the download mode to do so?
Edit: I installed the correct drivers for my phone while it was trying to restart(it didnt ofcourse). I booted into download mode and connected odin. Odin is not showing any signs of it connecting to the phone.
Edit2: Got it working(v1.85). I need bootloader, CSC, Modem and phone tar balls. i downloaded 2 rar files but they dont have Phone and bootloader tar balls
Click to expand...
Click to collapse
Hi. Make sure you have the the drivers installed correctly. Try the one from this thread. http://forum.xda-developers.com/showthread.php?t=961956 credits to SamHaLeKe. if you have an existing driver uninstall if first, reboot your pc then install the new one. you can download stock ROMS from this thread and its complete. http://forum.xda-developers.com/showthread.php?t=1465800 credits to Doky73. If everything is ok when your phone is in download mode ODIN should be able to detect it.

Thank you all!
You have been of great help.
My phone is running fine now.
Just waiting for Merruk's kernel to get overcloking capability.

DiGtal said:
Thank you all!
You have been of great help.
My phone is running fine now.
Just waiting for Merruk's kernel to get overcloking capability.
Click to expand...
Click to collapse
Nope. There is no stable overclocking capability yet and merruk is outdated. I recommend to use kuros kernel or savies rev 73

Phone Not booting
hitme987 said:
Nope. There is no stable overclocking capability yet and merruk is outdated. I recommend to use kuros kernel or savies rev 73
Click to expand...
Click to collapse
Hello,
I have same problem,When I want to Install Stock ROM with ODIN error shows ""
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
""
and when I go to "Android System Recovery" (vol up + home bot + power bot) and choose Wipe data/factory reset OR wipe cache partition, Error Show "Failed to mount /Cache (invalid argument) " & "Can't mount /cache/recovery/lastlog"
What should I do?

Fire TV boots into white "amazon" logo screen and just hangs

I have a Fire Tv that upon boot just hangs on the white amazon logo screen. This particular fire tv was sold to me as new open box but its obvious it was messed with as upon connecting keyboard via USB and entering Alt+I+SysRq it booted into this CWM recovery screen:
CWM-based Recovery v6.0.5.1.4a
-reboot system now
-install zip
-wipe data/factory reset
-wipe cache partition
-backup and restore
-mounts and storage
Selecting -install zip from above options results in:
Install update from zip file
-choose zip from /sdcard
-choose zip from last install folder
-install zip from sideload
Selecting -choose zip from /sdcard results in:
Chose a zip to apply
/sdcard/
-0/
And selecting -0/ results in:
Chose a zip to apply
/sdcard/0/
-clockworkmod/
I can connect to the fire tv over ethernet connection via adb(ip in CWM matches ip listed in my router's connected devices section) and over USB via fastboot. I was able to install a pre-rooted rom(bueller-51.1.4.0_514006420-rooted+updated) separately in both /sdcard/ and /sdcard/0/, but after selecting reboot system now, the fire tv just boots back into the white amazon logo screen and just hangs there. Good news is I can then boot into recovery via entering Alt+i+SysRq. In /sdcard/ there is only -0/ and in /sdcard/0/ there is only -clockworkmod/.
This is what a normally functioning rooted fire tv with the latest pre-rooted custom rom from rbox shows in CWM recovery(v6.0.5.1.4a:
Choose a zip to apply
/sdcard/
-0/
-legacy/
-obb/
Choose a zip to apply
/sdcard/0/
-Android/
-DCIM/
-Download/
-Movies/
-Music/
-Notifications/
-Pictures/
-Podcasts/
-Ringtones/
-amazonmp3/
-backups/
-clockworkmod/
Clearly the fire tv I got is missing the files shown in the normally working rooted fire tv I have.
Adb shell command just gives me:
~#
And having access to CWM recovery v6.0.5.1.4a must mean the bootloader is unlocked.
Any suggestions on how I can get this fire tv set up correctly will be appreciated.
-trojan4evr

TROJAN4EVR said:
I have a Fire Tv that upon boot just hangs on the white amazon logo screen. This particular fire tv was sold to me as new open box but its obvious it was messed with as upon connecting keyboard via USB and entering Alt+I+SysRq it booted into this CWM recovery screen:
CWM-based Recovery v6.0.5.1.4a
-reboot system now
-install zip
-wipe data/factory reset
-wipe cache partition
-backup and restore
-mounts and storage
Selecting -install zip from above options results in:
Install update from zip file
-choose zip from /sdcard
-choose zip from last install folder
-install zip from sideload
Selecting -choose zip from /sdcard results in:
Chose a zip to apply
/sdcard/
-0/
And selecting -0/ results in:
Chose a zip to apply
/sdcard/0/
-clockworkmod/
I can connect to the fire tv over ethernet connection via adb(ip in CWM matches ip listed in my router's connected devices section) and over USB via fastboot. I was able to install a pre-rooted rom(bueller-51.1.4.0_514006420-rooted+updated) separately in both /sdcard/ and /sdcard/0/, but after selecting reboot system now, the fire tv just boots back into the white amazon logo screen and just hangs there. Good news is I can then boot into recovery via entering Alt+i+SysRq. In /sdcard/ there is only -0/ and in /sdcard/0/ there is only -clockworkmod/.
This is what a normally functioning rooted fire tv with the latest pre-rooted custom rom from rbox shows in CWM recovery(v6.0.5.1.4a:
Choose a zip to apply
/sdcard/
-0/
-legacy/
-obb/
Choose a zip to apply
/sdcard/0/
-Android/
-DCIM/
-Download/
-Movies/
-Music/
-Notifications/
-Pictures/
-Podcasts/
-Ringtones/
-amazonmp3/
-backups/
-clockworkmod/
Clearly the fire tv I got is missing the files shown in the normally working rooted fire tv I have.
Adb shell command just gives me:
~#
And having access to CWM recovery v6.0.5.1.4a must mean the bootloader is unlocked.
Any suggestions on how I can get this fire tv set up correctly will be appreciated.
-trojan4evr
Click to expand...
Click to collapse
To me it appears that someone wiped everything on that box. Only reason I responded is because I remember trying to help someone out with a simple factory reset/wipe data in cwm and he took it too far and just wiped everything. We never did figure out how to proceed from there I don't think.
If there's any hope at all Rbox would probably be able to tell you. If not I hope you can get your money back.

TROJAN4EVR said:
I have a Fire Tv that upon boot just hangs on the white amazon logo screen. This particular fire tv was sold to me as new open box but its obvious it was messed with as upon connecting keyboard via USB and entering Alt+I+SysRq it booted into this CWM recovery screen:
CWM-based Recovery v6.0.5.1.4a
-reboot system now
-install zip
-wipe data/factory reset
-wipe cache partition
-backup and restore
-mounts and storage
Selecting -install zip from above options results in:
Install update from zip file
-choose zip from /sdcard
-choose zip from last install folder
-install zip from sideload
Selecting -choose zip from /sdcard results in:
Chose a zip to apply
/sdcard/
-0/
And selecting -0/ results in:
Chose a zip to apply
/sdcard/0/
-clockworkmod/
I can connect to the fire tv over ethernet connection via adb(ip in CWM matches ip listed in my router's connected devices section) and over USB via fastboot. I was able to install a pre-rooted rom(bueller-51.1.4.0_514006420-rooted+updated) separately in both /sdcard/ and /sdcard/0/, but after selecting reboot system now, the fire tv just boots back into the white amazon logo screen and just hangs there. Good news is I can then boot into recovery via entering Alt+i+SysRq. In /sdcard/ there is only -0/ and in /sdcard/0/ there is only -clockworkmod/.
This is what a normally functioning rooted fire tv with the latest pre-rooted custom rom from rbox shows in CWM recovery(v6.0.5.1.4a:
Choose a zip to apply
/sdcard/
-0/
-legacy/
-obb/
Choose a zip to apply
/sdcard/0/
-Android/
-DCIM/
-Download/
-Movies/
-Music/
-Notifications/
-Pictures/
-Podcasts/
-Ringtones/
-amazonmp3/
-backups/
-clockworkmod/
Clearly the fire tv I got is missing the files shown in the normally working rooted fire tv I have.
Adb shell command just gives me:
~#
And having access to CWM recovery v6.0.5.1.4a must mean the bootloader is unlocked.
Any suggestions on how I can get this fire tv set up correctly will be appreciated.
-trojan4evr
Click to expand...
Click to collapse
First, to correct you, CWM does not mean the bootloader is unlocked. You can have CWM with a locked bootloader. An unlocked bootloader just gives you access to fastboot flashing, which you shouldn't need if you you can get into CWM.
As for your issue, it's strange that flashing 51.1.4.0 didn't fix things (assuming CWM is funcitoning correctly and the 51.1.4.0 ROM you flash was in tact). If I'm not mistaken, flashing 51.1.4.0 will wipe out the existing boot and system partition, not just overwrite files (@rbox, can you verify?), so there shouldn't be anything remaining to cause the boot loop. I would try re-downloading and installing 51.1.4.0 again. Also try wiping data and cache within CWM.

KLit75 said:
To me it appears that someone wiped everything on that box. Only reason I responded is because I remember trying to help someone out with a simple factory reset/wipe data in cwm and he took it too far and just wiped everything. We never did figure out how to proceed from there I don't think.
If there's any hope at all Rbox would probably be able to tell you. If not I hope you can get your money back.
Click to expand...
Click to collapse
Thanks for your input. I compared this fire tv's /sdcard/ and sdcard/0/ content to the working rooted fire tv and the only content it had was just -0/ in /sdcard/ and -clockworkmod/ in /sdcard/0. Seller was actually gracious enough issue me a refund. I was just hoping to get it fixed so I can pay the seller back as we would both get what we originally agreed upon!!!
AFTVnews.com said:
First, to correct you, CWM does not mean the bootloader is unlocked. You can have CWM with a locked bootloader. An unlocked bootloader just gives you access to fastboot flashing, which you shouldn't need if you you can get into CWM.
As for your issue, it's strange that flashing 51.1.4.0 didn't fix things (assuming CWM is funcitoning correctly and the 51.1.4.0 ROM you flash was in tact). If I'm not mistaken, flashing 51.1.4.0 will wipe out the existing boot and system partition, not just overwrite files (@rbox, can you verify?), so there shouldn't be anything remaining to cause the boot loop. I would try re-downloading and installing 51.1.4.0 again. Also try wiping data and cache within CWM.
Click to expand...
Click to collapse
About CWM and unlocked bootloader, I read your Kernel Boot Menu(rbox's) instructions, #2 here:
http://www.aftvnews.com/how-to-install-a-kernel-boot-menu-on-the-amazon-fire-tv/
and assumed I must have an unlocked bootloader since in order to install CWM v6.0.5.1.4a, an unlocked bootloader is required.
What's strange is that when I enter adb shell command I get:
{
"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 first saw the prompt in your guide here about installing ADB enhanced Putty:
http://www.aftvnews.com/how-to-remotely-control-clockworkmod-on-the-amazon-fire-tv-using-adb/
C:\>adb connect 192.168.1.xxx
connected to 192.168.1.xxx:xxxx
C:\>adb devices
List of devices attached
192.168.1.xxx:xxxx device
When I enter adb shell and su commands:
C:\>adb shell
~ # su
su
/sbin/sh: su: not found
I can successfully connect via adb(wifi) and fastboot(usb) to push files which I can see in CWM recovery(/sdcard/ and /sdcard/0/) but when I install the rom and reboot,...I end up at the same black screen with white amazon logo. As suggested, I wiped data and cache within CWM and reinstalled I 51.1.4.0(checked md5 before I pushed the file- can't know for sure since I can't confirm via busybox). Any further help or suggestions will be appreciated. I need some hope :fingers-crossed:

Cannot update 3.2.8 to 4.0.1 without getting dm-verity warning

So i had 4.0.1 rooted before. I decided to return to stock by flashing full 4.0.1 on TWRP. That's when I started getting the error. I flashed 3.2.8 on stock recovery 2.0 and dm-verity error is gone. But installing 4.0.1 on stock recovery 2.0 results to dm-verity error again. I cannot use adb sideload as my computer is too slow
More details: before, I successfully updated my OP3 with 3.2.8 to 4.0.1 without the dm-verity warning. After that, I flashed blu_spark's TWRP v11, swiped to allow modifications and rooted it with SuperSU 2.79 and flashed some mods, still no warning. Yesterday, I decided to return to full stock. I updated my TWRP to the unofficial 3.0.3-0 (the official one wasn't available yesterday yet), wiped system, cache, and data excluding internal storage, then flashed 4.0.1. The dm-verity warning started to show. I followed your guide and other guides here on XDA, I cannot fix it. The only solution I found is to rollback to 3.2.8, I installed the zip file on the stock recovery from your guide (flashing the recovery before). I'm having problems with adb sideload, PC lags so much and sideloading never finishes, so what I do is copy the zip file in the internal storage. After I flashed 3.2.8 and rebooted, the recovery was replaced by the V1.0 version that doesn't have the function of installing zip from internal storage, so I flashed your stock recovery again. Booting to the new recovery, I flashed the 4.0.1 zip and the dm-verity warning shows again.
Right now, my OP3 is on 3.2.8 with stock ROM, kernel, and recovery. No dm-verity warning. I don't know how to update to 4.0.1 without getting that again

Simple. New bootloader added that warning and the old one never had a dm-verity nag screen. Flash it and ignore it. It shows up due to TWRP installed.

Check the freedomos thread and download the 3.2.7 fw and flash with TWRP and its gone, I am not using the nougat fw on 4.0.2, always make nandroid backups

install beta 7 firmware

Don't bother! It's not worth it! It's just a stupid message!

I have tried by following these steps (I initially had twrp-3.0.2-1.28-oneplus3 installed):
1. booted to TWRP recovery;
2. copied recovery_OBT8N.img to phone;
3. installed stock recovery_OBT8N.img via TWRP as image > recovery;
4. booted to stock recovery (directly from TWRP);
5. while in stock recovery, I have wiped the phone (for a clean flash);
6. installed OxygenOS 4.0 (N) via ADB;
7. once the installation got completed, I rebooted the phone;
8. once the phone started, I did not finished the startup setting;
9. switched-off the phone and booted in fastboot mode;
10. flashed TWRP recovery - twrp-3.0.2-1.28-oneplus3 again;
11. switched off the phone;
12. started the phone in TWRP recovery; TWRP asks for a password to decrypt - ignore it;
13. wiped the phone (I wanted to do so to make sure it is a really clean install, even if this wipes everything);
14. rebooted again to TWRP recovery; this time I did not get any password prompt;
15. from TWRP, I copied SR1-SuperSU-v2.79-SR1-20161221223537.zip to phone storage (while connected to my laptop, obviously);
16. installed SR1-SuperSU-v2.79-SR1-20161221223537.zip, wiped data & cache and rebooted system;
17. everything went fine, with no dm-verity and rooted.

It will Keep showing Because You flashed Oxygen OS from TWRP . Try flashing this just after flashing the OS .
it will disable DM verity and disable force encryption .

cpt.macp said:
It will Keep showing Because You flashed Oxygen OS from TWRP . Try flashing this just after flashing the OS .
it will disable DM verity and disable force encryption .
Click to expand...
Click to collapse
Please try this method. Tested and it works for me.
step
Assuming your bootloader is unlocked. Copy
1. fastboot boot twrp twrp-3.0.2-1.28-oneplus3.img
2. Now you will be in TWRP, perform wipe -> Format Data, perform Wipe -> Advanced wipe "All folder" except USB-OTG
3. Reboot to recovery
4. adb sideload OnePlus3Oxygen_16_OTA_037_all_1701041839_401.zip (if adb cannot read, because filesize too big. Use laa_2_0_4.zip to fix the adb.exe first.)
5. After adb sideload done, reboot to TWRP immediately, enable MTP to copy the file: no-verity-opt-encrypt-5.1.zip into your internal storage and install no-verity-opt-encrypt-5.1.zip immediately.
Then everything will be fine.

bkcheah75 said:
Please try this method. Tested and it works for me.
step
Assuming your bootloader is unlocked. Copy
1. fastboot boot twrp twrp-3.0.2-1.28-oneplus3.img
2. Now you will be in TWRP, perform wipe -> Format Data, perform Wipe -> Advanced wipe "All folder" except USB-OTG
3. Reboot to recovery
4. adb sideload OnePlus3Oxygen_16_OTA_037_all_1701041839_401.zip (if adb cannot read, because filesize too big. Use laa_2_0_4.zip to fix the adb.exe first.)
5. After adb sideload done, reboot to TWRP immediately, enable MTP to copy the file: no-verity-opt-encrypt-5.1.zip into your internal storage and install no-verity-opt-encrypt-5.1.zip immediately.
Then everything will be fine.
Click to expand...
Click to collapse
I was not having any Issue . But Surely Your Help and concern is much appreciated
and Yes this is also one of the way to remove DM verity and use the zip

Currently using:
ROM - FreedomOS-2.1
TWRP - blu_spark_v11-oo3
Phone - Encrypted
I have the DM-Verity message at boot. Would reflashing FreedomOS-2.1 Through TWRP & then immediately flash no-verity-opt-encrypt.zip get rid of the message?
Thanks

Android 8 update with FlashFire breaks TWRP or TWRP boot-loop

Hi everyone,
I tried to update my rooted Pixel C with Android 8 and TWRP 3.1.0.0 from August build to September build with FlashFire.
All of the following have I done on my Nexus 5x as well and it worked as a charm there.
Therefore i dl'd the corresponding zip-file from google dev page and started the update with FF. It said to me it can update the boot, system, recovery and vendor partition so I unchecked the recovery partition only to keep TWRP. I also told FF it should include SuperSU again to root the new Android.
After the update the device was unrooted, so i tried to start into recovery to install superSU manually. But TWRP was gone and i get everytime the android on the back with the text "no command".
Therefore I tried to flash TWRP with NRT again. But after the flash the device always starts into TWRP and Android isn't starting anymore.
I can use NRT again to flash Android without loosing my data but than TWRP is gone again.
So either the device always starts into TWRP or I have no recovery installed.
Anyone an idea what i can do to flash TWRP again and to fix the boot order or whats broken than?
Regards,
flattervieh

I don't have the C but here's what I would try. First, have your device booting normally with the stock recovery. Then use fastboot to boot into TWRP, not flash it. When it boots into TWRP then flash supersu. From TWRP then boot back into the bootloader and then flash TWRP with fastboot.

Flash the latest (beta?) TWRP. It allows reading the encrypted data folder.

Short notice, i'm still struggling with the problem.
In the meantime I tried the following:
1. I temporarely booted TWRP 3.1.0.0, with this version I was not able to encrypt the data partion (always invalid key) but I was able to see the system partition and I installed SuperSU. After that i restarted into the bootloader and flashed TWRP 3.1.0.0.
This led to the same phenomenon, that my pixel always boots into TWRP and not into Android itself.
2. Same thing as before but with TWRP 3.1.1.1.
With this version I was able to see the size of the data partition, but I was also not able to read or write onto it. (Again invalid code) I installed SuperSU and made a device restart without flashing TWRP 3.1.1.1.
This led to a totally softbricked device with a boot into "no command" screen.
After flashing Android again via fastboot Android starts correctly and I can use the device but root is still not working.
Regards

I'm not sure why twrp isn't sticking. But the android on its back with "no command"is the stock recovery. To get into it simultaneously press and release the power and vol up keys. You might have to try it a few times as the timing can be very finicky. From there you can boot into the system, you don't need to flash the factory image and start all over.

[Q] Boot only TWRP, not system

Hello,
On clean G5s, I followed the guide bellow, in order to unlock bootloader, install TWRP and get root. I successfully unlocked bootloader, installed TWRP, flashed Magisk.zip with TWRP but then, the device is unable to boot the system. It only boot on TWRP.
https://forum.xda-developers.com/moto-g5s/how-to/guide-unlock-bootloader-moto-g5s-t3691200
The warning message on boot is displayed, then after 1 minute, only TWRP started. I can still access to bootloader (with vol. down+pwr). If I select reboot system, in bootloader or TWRP, the device still reboot in TWRP only (after 1 minute of warning message "unlocked device...").
I think the device is bricked.
Could you tell me how to unbrick it please?
Thanks in advance.

philippe734 said:
Hello,
On clean G5s, I followed the guide bellow, in order to unlock bootloader, install TWRP and get root. I successfully unlocked bootloader, installed TWRP, flashed Magisk.zip with TWRP but then, the device is unable to boot the system. It only boot on TWRP.
https://forum.xda-developers.com/moto-g5s/how-to/guide-unlock-bootloader-moto-g5s-t3691200
The warning message on boot is displayed, then after 1 minute, only TWRP started. I can still access to bootloader (with vol. down+pwr). If I select reboot system, in bootloader or TWRP, the device still reboot in TWRP only (after 1 minute of warning message "unlocked device...").
I think the device is bricked.
Could you tell me how to unbrick it please?
Thanks in advance.
Click to expand...
Click to collapse
Once again flash the stock rom and then try to flash twrp again
Which twrp did u flash

I get the feeling that you dont have an os installed.
Anyway, I'd suggest you do the following:
- get a micro sd card
- in TWRP make a complete backup first (to micro sd)
- backup all your personal data (pictures etc) if there is any (to external storage such as micro sd or computer)
- format data under 'advanced wipe' and also wipe caches and system
- copy e.g. lineage 14.1 (https://forum.xda-developers.com/moto-g5s/development/rom-lineageos-14-1-t3727918) to your micro sd and flash it from there..
If the flashing procedure was successful (I don't see why not) you are now running the latest lineage os for our device (android 7.1.2) which now you can root by flashing magisk..
good luck

Unbricked
Done!
Unbricked and rooted successfully my G5s (XT1794, Android 7.1.1) with Linux.
Here steps followed:
https://forum.xda-developers.com/showpost.php?p=77180604&postcount=33