Database Users

Your device is corrupt. It cant be trusted and may not work properly. FIXED!

*** NOTE: Please excuse my English.
*** WARNING: I'm not responsible if anything happens to your device, I'm just sharing my experience and what I did to fix my own phone. Proceed at your own RISK.
I bought my Nexus 6p 64gb and as soon as I took it out of the box, I went directly and followed the guide here. So i unlocked the bootloader, flashed TWRP as a custom recovery, flashed CM13 + OpenGapps.
I noticed that every time I boot my device I get this warning:
Your device is corrupt. It can’t be
trusted and may not work properly.
Visit this link on another device:
go.co/ABH
and it does not seem to be a normal warning because when my OS boots up it shows me this
"Android system:
There’s an internal problem with your device. Contact your manufacturer for details"
Later on when I updated to the latest nightly image my camera crashes and doesn't function properly. I also already has an issue with Bluetooth and "Bluetooth share" crashing but that was unrelated. Anyways I was crippled in my day to day usage. Then I thought that I need to fix this asap because it might cause performance/security/hardware problems in the future.
So basically the fix is you should flash the latest bootloader image and radio image. Personally I wanted to start clean and make sure I have no corrupted files so here is what I did,
1. What i did is erase all boot, system, kernel & recovery files by typing the below command using fastboot just incase they were corrupted,
(Note: YOU DONT NEED TO DO THIS STEP, but i prefer starting clean incase i had some corrupted files. YOU WILL ALSO LOSE ENCRYPTION DOING THE FIRST STEP)
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
Source: http://devs-lab.com/...i-nexus-6p.html
2. Then i flashed the latest factory images in this sequence using fastboot, which can be found here: https://developers.g...s/images#angler
(Note: 6.0.1 (MMB29M) was latest image at the time i did this. For people who are doing this for the first time, then you just need to download the image then extract the needed files from it)
fastboot flash bootloader bootloader-angler-angler-xx.xxx.img
fastboot reboot-bootloader
fastboot flash radio radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash vendor vendor.img
fastboot format userdata
fastboot reboot
Source: http://forum.xda-dev...operly-t3268407
3. From there i reflashed TWRP using fastboot, then flashed the latest beta SuperSU v2.62 at the time, and then CM13, then OpenGapps, then again reflashed SuperSU v2.62 just incase, lol. (Do not flash the version of SuperSU that TWRP offers to flash for you in order to give you root, it is not compatible and will cause problems. When using TWRP before you've actually flashed SuperSU 2.50+, when you attempt to reboot out of TWRP it will tell you that it's detecting that you don't have root and it will offer to root for you, skip past this.)
What got fixed ?
-FIXED, this won't show up anymore:
Your device is corrupt. It can’t be
trusted and may not work properly.
Visit this link on another device:
go.co/ABH
-FIXED, this won't show up anymore:
Android system:
There’s an internal problem with your device. Contact your manufacturer for details.
-FIXED, Camera is working !
-NOT FIXED, "Bluetooth share" still crashes but I think its unrelated to this issue.
Hope this helps everyone as it helped me, thanks.
Sent from my Nexus 6P using Tapatalk

\*O / Thank you !!

Thanks, but better option? Don't reboot.
Sent from my Nexus 6P using Tapatalk

bob_mord_les said:
\*O / Thank you !!
Click to expand...
Click to collapse
Ur welcome [emoji1]
Sent from my Nexus 6P using Tapatalk

Followed your guide, thanks, but the message "Your device is corrupt. It can’t betrusted and may not work properly." still appears during a CM boot.
The message "There’s an internal problem with your device. Contact your manufacturer for details" appears when I boot into recovery (TWRP)
The camera is working now.
Also, before I was able to flash CM-13 I had to do "WIPE >> Format Data" from TWRP, otherwise CM was exiting with error 7.
The following packages were used:
original 6.0.1 (MMB29P) factory image
BETA-SuperSU-v2.66-20160103015024.zip
cm-13.0-20160115-NIGHTLY-angler.zip
open_gapps-arm64-6.0-micro-20160115.zip
twrp-2.8.7.2-angler.img
I also noticed that when rebooting into factory image, the same warning message appears as well.
Any way to fix it or did I do something wrong?

Why are people trying to fix an non issue? To get rid of the message you need to relock the bootloader which is more of a risk if your rooted. Its a message that only appears for a few seconds when you reboot and you don't need to do anything to get past it.
There is no corruption and the phone is trusted by YOU as you unlocked it and nothing else cares. Where is the issue?

g_kos said:
Followed your guide, thanks, but the message "Your device is corrupt. It can’t betrusted and may not work properly." still appears during a CM boot.
The message "There’s an internal problem with your device. Contact your manufacturer for details" appears when I boot into recovery (TWRP)
The camera is working now.
Also, before I was able to flash CM-13 I had to do "WIPE >> Format Data" from TWRP, otherwise CM was exiting with error 7.
The following packages were used:
original 6.0.1 (MMB29P) factory image
BETA-SuperSU-v2.66-20160103015024.zip
cm-13.0-20160115-NIGHTLY-angler.zip
open_gapps-arm64-6.0-micro-20160115.zip
twrp-2.8.7.2-angler.img
I also noticed that when rebooting into factory image, the same warning message appears as well.
Any way to fix it or did I do something wrong?
Click to expand...
Click to collapse
It's just telling you what you already know. You modified your system partition yourself so don't worry about it.
https://support.google.com/nexus/answer/6185381?hl=en

XxMORPHEOUSxX said:
It's just telling you what you already know. You modified your system partition yourself so don't worry about it.
https://support.google.com/nexus/answer/6185381?hl=en
Click to expand...
Click to collapse
Thanks. I read it in the original Heisenberg's unlock guide and was surprised when I read this post that it was possible to get rid of the warning message without locking the bootloader .

I'm new here in the forum's..I usually just read and carry on..the one think I'd like to say is..I don't understand why people got to say 'why you doing that for, ya don't need to' far as I know..this an educational site to learn..if he wants learn how to get rid of the warning..I don't see any problems in that whatsoever.

The message "There is an internal problem with your device..." seems to be related to the security patch version. This was my biggest issue, the message I get when booting the phone was annoying and I knew it was not a big deal, but having an internal problem warning was concerning, flashing the vendor image was the solution for me. But if you like to start clean then I have the steps written, but if you update then again you'll get the warning when booting up.
Sent from my Nexus 6P using Tapatalk

zooman31 said:
I'm new here in the forum's..I usually just read and carry on..the one think I'd like to say is..I don't understand why people got to say 'why you doing that for, ya don't need to' far as I know..this an educational site to learn..if he wants learn how to get rid of the warning..I don't see any problems in that whatsoever.
Click to expand...
Click to collapse
I think what people are trying to say is the risk/reward for getting rid of the message is not worth it. Especially since its just a brief warning you only see during boot. Just flashing twrp recovery will give the red message. SuperSU will help get rid of it which is why the OP was able to remedy it. It will not work for everyone though. Modifying the bootloader is the only sure fire way to snuff it out for good and you would be a fool to try and mess with your bootloader for something aesthetic. That's how most real bricks happen, is when a bootloader gets corrupted.

XxMORPHEOUSxX said:
I think what people are trying to say is the risk/reward for getting rid of the message is not worth it. Especially since its just a brief warning you only see during bouot. Just flashing twrp recovery will give the red message. SuperSU will help get rid of it which is why the OP was able to remedy it. It will not work for everyone though. Modifying the bootloader is the only sure fire way to snuff it out for good and you would be a fool to try and mess with your bootloader for something aesthetic. That's how most real bricks happen, is when a bootloader gets corrupted.
Click to expand...
Click to collapse
I assume that most people know the drill..you proceed to test at your own risk..the how to in the first post seemed to have worked after it was tested by the author.

zooman31 said:
I assume that most people know the drill..you proceed to test at your own risk..the how to in the first post seemed to have worked after it was tested by the author.
Click to expand...
Click to collapse
Basically just flash SuperSU last in whatever sequence, and as long as it boots,the red message will be gone. But change anything after and it will probably come back. I have nothing negative to say about this thread. I originally posted the nexus link just so people can rest assured that it is not an actual problem and a normal, albeit annoying, side effect of modifying the Nexus 6p. Happy Flashing

XxMORPHEOUSxX said:
Basically just flash SuperSU last in whatever sequence, and as long as it boots,the red message will be gone. But change anything after and it will probably come back. I have nothing negative to say about this thread. I originally posted the nexus link just so people can rest assured that it is not an actual problem and a normal, albeit annoying, side effect of modifying the Nexus 6p. Happy Flashing
Click to expand...
Click to collapse
all i did was flash twrp and unlocked the bootloader and still got the red message. so all i have to do is flash supersu and root? to get rid of it?

TechMillz93 said:
all i did was flash twrp and unlocked the bootloader and still got the red message. so all i have to do is flash supersu and root? to get rid of it?
Click to expand...
Click to collapse
Yes. The SuperSU beta 2.66 is what I use.

XxMORPHEOUSxX said:
Yes. The SuperSU beta 2.66 is what I use.
Click to expand...
Click to collapse
so i just reflashed the vendor and now im in bootloop ;(

TechMillz93 said:
so i just reflashed the vendor and now im in bootloop ;(
Click to expand...
Click to collapse
Why did you flash vendor? Try clearing caches and then reboot. Let it sit for 10 min too while starting up.

XxMORPHEOUSxX said:
Why did you flash vendor? Try clearing caches and then reboot. Let it sit for 10 min too while starting up.
Click to expand...
Click to collapse
im good now i just reflashed all the images im good.
but i have to feflash twrp now, what would u recommend
systemless or traditional ?

TechMillz93 said:
im good now i just reflashed all the images im good.
but i have to feflash twrp now, what would u recommend
systemless or traditional ?
Click to expand...
Click to collapse
Systemless unless you want to use xposed otherwise it doesn't matter. Systemless just makes it so you can use root apps like android pay. I use the 2.66 systemless. The instructions are a little all over the place on that thread. You no longer need a modified boot.IMG. the SuperSU zip patches whatever boot.IMG you have. So all you need to flash is the supersu2.66 for systemless or the traditional zip if going that route.

XxMORPHEOUSxX said:
Systemless unless you want to use xposed otherwise it doesn't matter. Systemless just makes it so you can use root apps like android pay. I use the 2.66 systemless. The instructions are a little all over the place on that thread. You no longer need a modified boot.IMG. the SuperSU zip patches whatever boot.IMG you have. So all you need to flash is the supersu2.66 for systemless or the traditional zip if going that route.
Click to expand...
Click to collapse
so i dont need gapps etc?
its all in there?

Get softbrick with bootloop

Hey guys,
This afternoon I tried to change my file system fo f2fs, I failed and got into bootloop. Follow some instructions, I flash the factory image (I was using stock 7.1.1 Feb and EX Kernel before trying f2fs) but I still face the bootloop. As I know this is a softbrick, because I can still boot into bootloader and flash recovery. But no matter how I try (flash stock, flash rom cook, flash older stock)...my 6P is still in the bootloop. I check in the TWRP that my phone is still in ext4, not f2fs anymore.
I really need some advice to wake him up. Really appreciate your help.

In all honesty bro, I never noticed much difference if any with ext4 vs f2fs. On another note, what kernel and ROM did you flash with f2fs? The the version that supports f2fs gives bootloops when you flash a custom kernel with that recovery. Try flashing the official version of recovery, reboot, then ROM and kernel if you wish and try again.
Sent from my Nexus 6P using XDA-Developers Legacy app

nhatminhng said:
Hey guys, I really need some advice to wake him up. Really appreciate your help.
Click to expand...
Click to collapse
Fastboot format your partitions and use flash-all.bat with a stock Google image.

nhatminhng said:
Hey guys,
This afternoon I tried to change my file system fo f2fs, I failed and got into bootloop. Follow some instructions, I flash the factory image (I was using stock 7.1.1 Feb and EX Kernel before trying f2fs) but I still face the bootloop. As I know this is a softbrick, because I can still boot into bootloader and flash recovery. But no matter how I try (flash stock, flash rom cook, flash older stock)...my 6P is still in the bootloop. I check in the TWRP that my phone is still in ext4, not f2fs anymore.
I really need some advice to wake him up. Really appreciate your help.
Click to expand...
Click to collapse
Why do you still have TWRP if you flashed stock? You need to flash the complete stock image including the stock recovery.

MidnightDevil said:
In all honesty bro, I never noticed much difference if any with ext4 vs f2fs. On another note, what kernel and ROM did you flash with f2fs? The the version that supports f2fs gives bootloops when you flash a custom kernel with that recovery. Try flashing the official version of recovery, reboot, then ROM and kernel if you wish and try again.
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
jhs39 said:
Why do you still have TWRP if you flashed stock? You need to flash the complete stock image including the stock recovery.
Click to expand...
Click to collapse
v12xke said:
Fastboot format your partitions and use flash-all.bat with a stock Google image.
Click to expand...
Click to collapse
Thanks guys for helping. I fixed it.
I always flashed the stock image step by step followed by heisenberg, and never use the flash-all.bat just because I dont understand how to run it. However a guy in the f2fs told me to add in some steps
fastboot format system
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
And it works. It seems like the step by step way is not clear enough. Any guys can tell me how to run the flash-all.bat please? When I run it always said fastboot is not etc...

nhatminhng said:
Thanks guys for helping. I fixed it. I always flashed the stock image step by step followed by heisenberg, and never use the flash-all.bat just because I dont understand how to run it. However a guy in the f2fs told me to add in some steps And it works. It seems like the step by step way is not clear enough. Any guys can tell me how to run the flash-all.bat please? When I run it always said fastboot is not etc...
Click to expand...
Click to collapse
It's a good sign you formatted and received no errors in fastboot. Google provides instructions for flash-all.bat on the same page you download the images from. https://developers.google.com/android/images
If you are not comfortable using the command window in Windows, you could also use a toolkit like Wugfresh's NRT or Skipsoft's Toolkit to automate the whole process.

v12xke said:
It's a good sign you formatted and received no errors in fastboot. Google provides instructions for flash-all.bat on the same page you download the images from. https://developers.google.com/android/images
If you are not comfortable using the command window in Windows, you could also use a toolkit like Wugfresh's NRT or Skipsoft's Toolkit to automate the whole process.
Click to expand...
Click to collapse
Yes sir of course I read it. But I dont understand this step.
Open a terminal and navigate to the unzipped system image directory.
Click to expand...
Click to collapse
Is it I open the fastboot cmd, use cd command to navigate to that directory? I already tried but failed to run :'( Although I have fixed it but I want to know just in case the next time. Thanks.

nhatminhng said:
Yes sir of course I read it. But I dont understand this step.
Is it I open the fastboot cmd, use cd command to navigate to that directory? I already tried but failed to run :'( Although I have fixed it but I want to know just in case the next time. Thanks.
Click to expand...
Click to collapse
Hi... Here's a pretty good detailed process on how to unlock/flash, etc...
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page549
Also, before using any toolkit, I suggest using manual commands and getting comfortable with it. At least, you learn exactly what command do what! Simply pressing a button in a program may result in a bricked device. Plus with command line you learn something. :good:

@nhatminhng How did you get your phone fixed? is your phone unlocked?

tjchuot287 said:
@nhatminhng How did you get your phone fixed? is your phone unlocked?
Click to expand...
Click to collapse
What do you mean "unlocked"? The bootloader is unlocked and I can flash recovery too. I use the command line in heisenberg thread and flash my phone to stock. Add in some more steps I mentioned above. Boom. It's back again.

nhatminhng said:
What do you mean "unlocked"? The bootloader is unlocked and I can flash recovery too. I use the command line in heisenberg thread and flash my phone to stock. Add in some more steps I mentioned above. Boom. It's back again.
Click to expand...
Click to collapse
@nhatminhng oh, im sorry, i mean unlocked bootloader. So my bootloader is locked, it still doesnt have any solutions yet.

tjchuot287 said:
@nhatminhng oh, im sorry, i mean unlocked bootloader. So my bootloader is locked, it still doesnt have any solutions yet.
Click to expand...
Click to collapse
Do you have access to recovery or just boot loader?
Sent from my Nexus 6P using XDA-Developers Legacy app

CyberpodS2 said:
Do you have access to recovery or just boot loader?
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes i can. I tried to sideload multiple version of OTA but all have failed.

tjchuot287 said:
Yes i can. I tried to sideload multiple version of OTA but all have failed.
Click to expand...
Click to collapse
I'm guessing you've already tried a factory reset from the stock recovery. Because your bootloader is locked you are limited to sideloading OTA's. And yes, sideloading an older or equal version OTA will fail. You can try a newer revision OTA when available. The 7.1.2 beta may come out before the March security update.

v12xke said:
I'm guessing you've already tried a factory reset from the stock recovery. Because your bootloader is locked you are limited to sideloading OTA's. And yes, sideloading an older or equal version OTA will fail. You can try a newer revision OTA when available. The 7.1.2 beta may come out before the March security update.
Click to expand...
Click to collapse
Good point. It didn't occur to me that equal version would fail. Folks need to unlock their boot loaders! Lol
Sent from my Nexus 6P using XDA-Developers Legacy app

CyberpodS2 said:
Good point. It didn't occur to me that equal version would fail. Folks need to unlock their boot loaders! Lol
Click to expand...
Click to collapse
I agree. Unless you absolutely cannot live without Android Pay or Wallet, work phone, etc., there is no reason to not unlock the bootloader as a safeguard. Of course it's no guarantee, but you just have a whole lot more tools at your disposal when SHTF, including restoring a recent backup or flashing a complete stock image. The initial pain of losing your data can be largely mitigated by pulling it off first, and eventually you even forget about the boot nag screen.

v12xke said:
I agree. Unless you absolutely cannot live without Android Pay or Wallet, work phone, etc., there is no reason to not unlock the bootloader as a safeguard. Of course it's no guarantee, but you just have a whole lot more tools at your disposal when SHTF, including restoring a recent backup or flashing a complete stock image. The initial pain of losing your data can be largely mitigated by pulling it off first, and eventually you even forget about the boot nag screen.
Click to expand...
Click to collapse
Now i have unlocked bootloader but the phone keep restart and stuck at logo again. i followed @Heisenberg thread but same result.

[HELP] Moto G PLus 4 booting only in recovery, not system

Hi,
I just unlocked the bootloader of my Moto G Plus 4 via adb, and after that I switched it on, it worked fine and I transferred SuperUser.zip into my phone's internal memory, and then tried to flash it through recovery, (following the sleps I read somewhere), since then my phone is not rebooting - it is rebooting into bootloader and I can enter recovery as well, but Im not able to reboot my phone. The device is being detected via adb when it is in recovery mode, but not in bootloader. Is this issue fixable? Please help me fix this.
EDIT: I forgot to mention, I'm not getting the boot animation as well. I press the power key and nothing at all happens.

d1nesh said:
Hi,
I just unlocked the bootloader of my Moto G Plus 4 via adb, and after that I switched it on, it worked fine and I transferred SuperUser.zip into my phone's internal memory, and then tried to flash it through recovery, (following the sleps I read somewhere), since then my phone is not rebooting - it is rebooting into bootloader and I can enter recovery as well, but Im not able to reboot my phone. The device is being detected via adb when it is in recovery mode, but not in bootloader. Is this issue fixable? Please help me fix this.
Click to expand...
Click to collapse
You got into bootloop, just download the stock ROM and then flash it again, follow any guide over XDA or see YouTube for more help. Flash ROM without locking bootloader will be good.
Sent from my Moto G4 Plus using Tapatalk

avirk said:
You got into bootloop, just download the stock ROM and then flash it again, follow any guide over XDA or see YouTube for more help. Flash ROM without locking bootloader will be good.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
I forgot to mention, I'm not getting the bootanimation as well, I press the power button and nothing at all happens.

d1nesh said:
I forgot to mention, I'm not getting the bootanimation as well, I press the power button and nothing at all happens.
Click to expand...
Click to collapse
Yes that is what happen after unlocking Boot loader, just flash the stock ROM using any tutorial over XDA without locking the boot loader and then follow the proper instructions to root your mobile. Rooting is very easy on Android N. So I will say flash android N and then proceed.
Sent from my Moto G4 Plus using Tapatalk

avirk said:
Yes that is what happen after unlocking Boot loader, just flash the stock ROM using any tutorial over XDA without locking the boot loader and then follow the proper instructions to root your mobile. Rooting is very easy on Android N. So I will say flash android N and then proceed.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
DO you mind posting the link to the proper article, since phone is not being detected via adb as well.

d1nesh said:
DO you mind posting the link to the proper article, since phone is not being detected via adb as well.
Click to expand...
Click to collapse
First thing, your query doesn't belong to the development thread. It should had been created in "Questions and Answers"
Second thing, if you flash supersu on stock rom it won't boot due some security measures of Moto. Instead flash ElementalX kernel first and then flash supersu.

d1nesh said:
DO you mind posting the link to the proper article, since phone is not being detected via adb as well.
Click to expand...
Click to collapse
All information that you will need can be found here. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
For the latest stock nougat firmware for XT1643 check this link https://mega.nz/#!ystC2ZSL!ql6cyC5v5RgLQfo7G44mhi7Ng-AQBvtsouKxKinbHi8
If you have some confusion about flashing, be sure to check it out before going on. I believe you have some knowledge about fastboot and using it.

==vj== said:
First thing, your query doesn't belong to the development thread. It should had been created in "Questions and Answers"
Second thing, if you flash supersu on stock rom it won't boot due some security measures of Moto. Instead flash ElementalX kernel first and then flash supersu.
Click to expand...
Click to collapse
i'm really sorry about posting in wrong thread.
While trying to flash ElementalX kernel through memory card, I'm getting error: Zip signature verification failed, (in red).

nazim7 said:
All information that you will need can be found here. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
For the latest stock nougat firmware for XT1643 check this link https://mega.nz/#!ystC2ZSL!ql6cyC5v5RgLQfo7G44mhi7Ng-AQBvtsouKxKinbHi8
If you have some confusion about flashing, be sure to check it out before going on. I believe you have some knowledge about fastboot and using it.
Click to expand...
Click to collapse
Last time I used fastboot was more than one year ago. Also, my device is not being detected by adb when in bootloader.

d1nesh said:
DO you mind posting the link to the proper article, since phone is not being detected via adb as well.
Click to expand...
Click to collapse
You can try one thing if you have twrp and your phone is booting into recovery then do this.
Download any custom rom based on Android N, don't go with RR for now as it is not for newbie cause new build has some issue while flashing.
Download the gapps recommend the opengapps Nano package from the opengapps.org.
Place both zip on your sd card and boot into recovery and then wipe everything like, system, dalvik cache, cache, system and then install the both zip, first rom and then install gapps. Then reboot. I hope it will fix the bootloop issue.

d1nesh said:
Last time I used fastboot was more than one year ago. Also, my device is not being detected by adb when in bootloader.
Click to expand...
Click to collapse
What did you mean by your device not being detected in bootloader mode. Did you install the right drivers. Did you install minimal adb and fastboot. Can you do the below steps and tell me the result.
1. Download the drivers from here.
For Windows: http://www.devfiles.co/download/5eEx...ager_2.5.4.exe
2. Download the Minimal ADB and Fastboot = https://www.androidfilehost.com/?fid=745425885120698566
3. Install Minimal ADB and Fastboot = https://forum.xda-developers.com/sho....php?t=2317790
4. Restart the Moto G4 in fastboot mode. (Bootloader mode)
5. Connect the Phone to the computer.
6. In adb fastboot folder shift+right click and then in the pop up click "open command window here"
7. In the command line type: "fastboot devices"
Seeing your serial number means we know all is good and your phone is connected and you can go on flash the stock firmware. If the serial number is not showing, the drivers are not properly installed.
---------- Post added at 01:33 PM ---------- Previous post was at 01:25 PM ----------
avirk said:
You can try one thing if you have twrp and your phone is booting into recovery then do this.
Download any custom rom based on Android N, don't go with RR for now as it is not for newbie cause new build has some issue while flashing.
Download the gapps recommend the opengapps Nano package from the opengapps.org.
Place both zip on your sd card and boot into recovery and then wipe everything like, system, dalvik cache, cache, system and then install the both zip, first rom and then install gapps. Then reboot. I hope it will fix the bootloop issue.
Click to expand...
Click to collapse
I thought he don't have TWRP installed. If TWRP is installed, then go on with what he said. That is the best solution for you. :good:

avirk said:
You can try one thing if you have twrp and your phone is booting into recovery then do this.
Download any custom rom based on Android N, don't go with RR for now as it is not for newbie cause new build has some issue while flashing.
Download the gapps recommend the opengapps Nano package from the opengapps.org.
Place both zip on your sd card and boot into recovery and then wipe everything like, system, dalvik cache, cache, system and then install the both zip, first rom and then install gapps. Then reboot. I hope it will fix the bootloop issue.
Click to expand...
Click to collapse
I tried the same, but the flashing process is stuck on "Patching system image unconditionally..." I tried two different ROMs, and in both cases, it is stuck in the same step

d1nesh said:
I tried the same, but the flashing process is stuck on "Patching system image unconditionally..." I tried two different ROMs, and in both cases, it is stuck in the same step
Click to expand...
Click to collapse
Try with wiping everything, wipe system and internal storage as well, I know your important data will be gone but it will be worth a try. If anything comes up let us know, also what have you tried so far tell us in details so we don't repeat it over and over, also in above post some links are provided try them.

avirk said:
Try with wiping everything, wipe system and internal storage as well, I know your important data will be gone but it will be worth a try. If anything comes up let us know, also what have you tried so far tell us in details so we don't repeat it over and over, also in above post some links are provided try them.
Click to expand...
Click to collapse
I had tried wiping everything already, still I'm getting this error.
Also i'm getting one more error: Unable to load "/system".

d1nesh said:
I had tried wiping everything already, still I'm getting this error.
Also i'm getting one more error: Unable to load "/system".
Click to expand...
Click to collapse
Try with other pc or change the port for data cable. It seems your system partition got corrupted, also you can mount system partition under twrp and then try to format it.

d1nesh said:
I had tried wiping everything already, still I'm getting this error.
Also i'm getting one more error: Unable to load "/system".
Click to expand...
Click to collapse
When in TWRP, go to Mount and see if system is ticked or not. If not, mount the system and wipe it. Then flash the rom again. BTW which TWRP version are you using. From where you get it.

nazim7 said:
When in TWRP, go to Mount and see if system is ticked or not. If not, mount the system and wipe it. Then flash the rom again. BTW which TWRP version are you using. From where you get it.
Click to expand...
Click to collapse
System is not ticked when i go to Mount, neither am I able to tick it. BTW, I have twrp-3.0.2-0-athene.img.

d1nesh said:
System is not ticked when i go to Mount, neither am I able to tick it. BTW, I have twrp-3.0.2-0-athene.img.
Click to expand...
Click to collapse
So that is the problem. You have to install TWRP latest version. Version 3.0.2 r4 or higher by shreps will work for you. You can find it here. https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337
The latest version is 3.0.3 n4. Flash it, mount the system and everything will be good for you

d1nesh said:
System is not ticked when i go to Mount, neither am I able to tick it. BTW, I have twrp-3.0.2-0-athene.img.
Click to expand...
Click to collapse
As @nazim7 suggested you to flash the latest TWRP and then try to flash the rom again, also you can try to resize the partition and try to format it from twrp from the option in twrp. Just let us know what the result come back.

nazim7 said:
So that is the problem. You have to install TWRP latest version. Version 3.0.2 r4 or higher by shreps will work for you. You can find it here. https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337
The latest version is 3.0.3 n4. Flash it, mount the system and everything will be good for you
Click to expand...
Click to collapse
There's one more problem like I've mentioned previously. I have the latest drivers even then the device is not being detected via adb when in bootloader, but as soon as I boot into recovery, the device shows up on adb after command. How do I flash the recovery if the device doesn't show up in bootloader on adb?

Phone has no OS at all after rooting

After doing the root method located here: https://forum.xda-developers.com/v20/how-to/instruction-to-root-h918-10i-t3536472 my phone only boots into twrp and only has the twrp file on it. When i try to reboot into system it just sends me right back into twrp. I have no idea how that happened and i might of done the impossible but, is there any way to fix it? It's a T-Mobile 10j V20
Update: Tried installing therom from: https://forum.xda-developers.com/v20/development/rom-maximum-ovrdrive-lg-v20-v2-0-t3518475 and yet it still only shows twrp folder and wont boot to the start screen

Strasius said:
After doing the root method located here: https://forum.xda-developers.com/v20/how-to/instruction-to-root-h918-10i-t3536472 my phone only boots into twrp and only has the twrp file on it. When i try to reboot into system it just sends me right back into twrp. I have no idea how that happened and i might of done the impossible but, is there any way to fix it? It's a T-Mobile 10j V20
Click to expand...
Click to collapse
The fast thing to come to mind is too flash a stock rom

Still_living714 said:
The fast thing to come to mind is too flash a stock rom
Click to expand...
Click to collapse
I'll give that a try as soon as i can find a rom for stock

Strasius said:
I'll give that a try as soon as i can find a rom for stock
Click to expand...
Click to collapse
There is. Flash MEGAROM v5 it's 10k base

Still_living714 said:
There is. Flash MEGAROM v5 it's 10k base
Click to expand...
Click to collapse
my phone was 10j, will it work?

Strasius said:
my phone was 10j, will it work?
Click to expand...
Click to collapse
Yup and remember to press that thanks button ?

Still_living714 said:
Yup and remember to press that thanks button
Click to expand...
Click to collapse
i will, but one last question. is flashing a rom the same as installing something like SuperSU where i just select install and then the zip?

Strasius said:
i will, but one last question. is flashing a rom the same as installing something like SuperSU where i just select install and then the zip?
Click to expand...
Click to collapse
Yeah, MEGAROM wise it will take you into aroma installer which you can choose exactly what you want, like you can chose to flash magisk or supersu, lg sounds or pixel etc... Of everything else fails then just grab kdz file and flash through lg up

Still_living714 said:
Yeah, MEGAROM wise it will take you into aroma installer which you can choose exactly what you want, like you can chose to flash magisk or supersu, lg sounds or pixel etc... Of everything else fails then just grab kdz file and flash through lg up
Click to expand...
Click to collapse
That is awesome! I hope it finally works and lets me see that beautiful start screen

It did not, and LGUP isnt working with a Failed to load error (5)

sounds like ur in a twrp loop.. are you checking to see if system is getting mounted in twrp?
there are a few ways to fix a twrp loop, try booting into recovery using the vol down method, and see if just hitting reboot works,
if not, fastboot commands that address this would be fastboot erase etc; fastboot erase misc ; fastboot erase fota ; and then reboot and see if it boots.
be aware boot up times take a lot longer then usual when you root, as the aboot is a little slower.
you could also try the twrp file manager route and delete the above directories also, etc/misc/fota/cache
if you have never done a FORMAT data with twrp you need to do that 1st and remove encryption as the stock rom is encrypted and will not boot after root.
Wipe using format data, type yes, then wipe the directories i mentioned and then flash the stock rom mentioned by the other member then reboot and let it sit for 15min. If it dosn't instantly shoot you back to twrp then ur good, just wait wait wait for that long 1st boot to complete.

Unsure what I did

but ....... I am in twrp unable to reboot into my rom. When I click on Install I see all these folders with letters and numbers and what my original folders.
Can somone help me boot into my rom again?

ms.journie said:
but ....... I am in twrp unable to reboot into my rom. When I click on Install I see all these folders with letters and numbers and what my original folders.
Can somone help me boot into my rom again?
Click to expand...
Click to collapse
You will more than likely need to format data. This will cause you to loose everything. But that is what you are seeing, those folders, are your data. Just encrypted.
Also make sure you are on the latest version of TWRP. Sometimes the older unsupported version had encryption errors.

Omg this saddens me! So there's no way I am unable to at least retrieve my pictures?
Scott said:
You will more than likely need to format data. This will cause you to loose everything. But that is what you are seeing, those folders, are your data. Just encrypted.
Also make sure you are on the latest version of TWRP. Sometimes the older unsupported version had encryption errors.
Click to expand...
Click to collapse

Have u tested change boot partition ?

yup
J3zz said:
Have u tested change boot partition ?
Click to expand...
Click to collapse

ms.journie said:
yup
Click to expand...
Click to collapse
Simple test are:
- change boot partition
- reflash system
- Say goodbye too all
Got the same problem, Solved After reboot in twrp and enter the good decryption code

I'm right in the middle of reflashing. I am trying everything else before I do say goodbye to my pictures! :crying:
How did you figure out the decryption code?
J3zz said:
Simple test are:
- change boot partition
- reflash system
- Say goodbye too all
Got the same problem, Solved After reboot in twrp and enter the good decryption code
Click to expand...
Click to collapse

ms.journie said:
I'm right in the middle of reflashing. I am trying everything else before I do say goodbye to my pictures! :crying:
How did you figure out the decryption code?
Click to expand...
Click to collapse
First time entering in twrp after flashing update, I did not get folder to flash magisk, did a reboot and get it, just a bad encryption code I think
Did u flash rom or anything else before getting this problem ?

Yup, I sure did! 4am couldn't sleep so I thought I would finally put a fingerprint mod on; which I have done this before with no issues. For the life of me, I don't remember which mod I tried to install thru Magisk.
My phone is currently stuck on "Phone is starting"
I also think it's time to look into some sort of automatic back up service..... Got any ideas?
J3zz said:
First time entering in twrp after flashing update, I did not get folder to flash magisk, did a reboot and get it, just a bad encryption code I think
Did u flash rom or anything else before getting this problem ?
Click to expand...
Click to collapse

ms.journie said:
Yup, I sure did! 4am couldn't sleep so I thought I would finally put a fingerprint mod on; which I have done this before with no issues. For the life of me, I don't remember which mod I tried to install thru Magisk.
My phone is currently stuck on "Phone is starting"
I also think it's time to look into some sort of automatic back up service..... Got any ideas?
Click to expand...
Click to collapse
Use msmdownloadtool, have u tried using magisk uninstall in twrp with zip file ? Then boot and uninstall the "****in" fantastic module... maybe it works

I did try to uninstall Magisk in twrp using adb shell. I never had any luck with that msmdownloadtool and not only that it relocks your bootloader.
I usually go this route [ROM][STOCK][FASTBOOT][OP6T] Stock Fastboot ROMs for OnePlus 6T https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
Thanks for trying to me!
J3zz said:
Use msmdownloadtool, have u tried using magisk uninstall in twrp with zip file ?
Click to expand...
Click to collapse

ms.journie said:
I did try to uninstall Magisk in twrp using adb shell. I never had any luck with that msmdownloadtool and not only that it relocks your bootloader.
I usually go this route [ROM][STOCK][FASTBOOT][OP6T] Stock Fastboot ROMs for OnePlus 6T https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
Thanks for trying to me!
Click to expand...
Click to collapse
Good luck !!

I saw this happen when I used the official TWRP app.
It went away when I used this TWRP. Hope that helps.

I'm glad you already know not to use the MSM tool. Too many people jump straight to this.....
You just need to boot the correct recovery and your data will decrypt, and you will be able to back it up to a PC, then you can reload your ROM via TWRP or Fastboot to get the phone bootable again. So now it's a question of what ROM were you running before. Do you need a recovery with the latest security patch or something older? What TWRP are you running. Try 3.3.1-6 psychen6 linked too first. Boot that image from Fastboot. See if your password/pin will work to decrypt your data.