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?

Stuck On bootanimation

No matter what custom firmware i flash it always is stuck on the boot animation, Ive left it booting for 5 hours today and it never reached the setup screen, just constant booting, I erase EVERYTHING everytime I go to twrp, except for my internal and external storage. Aswell as If i flash/restore my stock rooted and unrooted firmware, it does boot, but NO wifi or data works, even with the removal and reinsertion of the simcard. Please help. If i didnt explain it well enough i can reply and add more detail.

DeliriousHD said:
No matter what custom firmware i flash it always is stuck on the boot animation, Ive left it booting for 5 hours today and it never reached the setup screen, just constant booting, I erase EVERYTHING everytime I go to twrp, except for my internal and external storage. Aswell as If i flash/restore my stock rooted and unrooted firmware, it does boot, but NO wifi or data works, even with the removal and reinsertion of the simcard. Please help. If i didnt explain it well enough i can reply and add more detail.
Click to expand...
Click to collapse
You may have to follow this https://forum.xda-developers.com/moto-x-style/general/guide-return-to-stock-relock-bootloader-t3489110 to get back to stock. There's a section about returning to stock without relocking the bootloader.

ccic2491 said:
You may have to follow this https://forum.xda-developers.com/moto-x-style/general/guide-return-to-stock-relock-bootloader-t3489110 to get back to stock. There's a section about returning to stock without relocking the bootloader.
Click to expand...
Click to collapse
Ill try that. Ill report back if it works or fails.

ccic2491 said:
You may have to follow this https://forum.xda-developers.com/moto-x-style/general/guide-return-to-stock-relock-bootloader-t3489110 to get back to stock. There's a section about returning to stock without relocking the bootloader.
Click to expand...
Click to collapse
It did not work, Keeps saying "Could not find 'meta-inf/com/google/android/update-binary' in zip file.

DeliriousHD said:
It did not work, Keeps saying "Could not find 'meta-inf/com/google/android/update-binary' in zip file.
Click to expand...
Click to collapse
One thing to try is formatting the internal storage to make sure you have a clean start. TWRP wipes /data without wiping userdata by default; to completely wipe the internal storage you have to go into the format data wipe where you must type "yes" to confirm instead of a slider. Sometimes leftover files can cause permissions problems and roms fail to boot. It is more common on other phones than this one, but I've seen some people report your problem before here too.
If you do this, obviously make sure you back up all the files you care about on internal storage to a microSD or off device. Also make sure you have rom/gapps to flash and a working TWRP backup stored on a microSD, or you've verified you can USB copy with MTP or adb push files from a computer to your phone before formatting. Don't find out after wiping and formatting that your computer is missing something it needs to copy files to your phone properly when your phone is booted into TWRP, test it first if you're going this route. Otherwise you could be stuck with a blank phone and nothing to flash on it.
I do this every once in a while just to keep internal storage from getting too cluttered from chronic flashing; just be careful about how you go about it.

Okay, I can try that.

jason2678 said:
One thing to try is formatting the internal storage to make sure you have a clean start. TWRP wipes /data without wiping userdata by default; to completely wipe the internal storage you have to go into the format data wipe where you must type "yes" to confirm instead of a slider. Sometimes leftover files can cause permissions problems and roms fail to boot. It is more common on other phones than this one, but I've seen some people report your problem before here too.
If you do this, obviously make sure you back up all the files you care about on internal storage to a microSD or off device. Also make sure you have rom/gapps to flash and a working TWRP backup stored on a microSD, or you've verified you can USB copy with MTP or adb push files from a computer to your phone before formatting. Don't find out after wiping and formatting that your computer is missing something it needs to copy files to your phone properly when your phone is booted into TWRP, test it first if you're going this route. Otherwise you could be stuck with a blank phone and nothing to flash on it.
I do this every once in a while just to keep internal storage from getting too cluttered from chronic flashing; just be careful about how you go about it.
Click to expand...
Click to collapse
I did this and its still stuck on boot. Im trying to flash AICP

DeliriousHD said:
I did this and its still stuck on boot. Im trying to flash AICP
Click to expand...
Click to collapse
It was worth a try. What bootloader and twrp version are you using?

jason2678 said:
It was worth a try. What bootloader and twrp version are you using?
Click to expand...
Click to collapse
regular bootloader for the xt1575 I havent chnged it, and twrp 3.0.2-0

DeliriousHD said:
regular bootloader for the xt1575 I havent chnged it, and twrp 3.0.2-0
Click to expand...
Click to collapse
TWRP 3.1 is out. I doubt that's your problem since you're flashing successfully and failing to boot, but updating recovery is something else to check off the list.
Are you on the L or M bootloader? It changed. Just looking for anything that might be causing the trouble.
Code:
getprop ro.bootloader
returns 0xA04C for me, and aicp is working good.

jason2678 said:
TWRP 3.1 is out. I doubt that's your problem since you're flashing successfully and failing to boot, but updating recovery is something else to check off the list.
Are you on the L or M bootloader? It changed. Just looking for anything that might be causing the trouble.
Code:
getprop to.bootloader
returns 0xA04C for me, and aicp is working good.
Click to expand...
Click to collapse
I think im on L but do i just put that in cmd when in bootloader? I also just updated twrp to 3.1 just now.
EDIT: I actually cant even do that in cmd.

DeliriousHD said:
I think im on L but do i just put that in cmd when in bootloader? I also just updated twrp to 3.1 just now.
Click to expand...
Click to collapse
Fastboot says what bootloader version you're on close to the little reclining robot, but I think it displays it a bit differently. A0.4C trailed by a date if I recall correctly.
You could enter that command in TWRP's built-in terminal. I think the terminal is under the Advanced menu. That should get you the same output.

jason2678 said:
Fastboot says what bootloader version you're on close to the little reclining robot, but I think it displays it a bit differently. A0.4C trailed by a date if I recall correctly.
You could enter that command in TWRP's built-in terminal. I think the terminal is under the Advanced menu. That should get you the same output.
Click to expand...
Click to collapse
I just tried putting that into terminal and it does nothing.

jason2678 said:
Fastboot says what bootloader version you're on close to the little reclining robot, but I think it displays it a bit differently. A0.4C trailed by a date if I recall correctly.
You could enter that command in TWRP's built-in terminal. I think the terminal is under the Advanced menu. That should get you the same output.
Click to expand...
Click to collapse
also BL: A0.1C (SHA-E29F91E, 2015-7-28 16;16;36)

DeliriousHD said:
I just tried putting that into terminal and it does nothing.
Click to expand...
Click to collapse
Well that's odd

jason2678 said:
Well that's odd
Click to expand...
Click to collapse
In your code you put to not ro XD

jason2678 said:
Well that's odd
Click to expand...
Click to collapse
Mine is 0xa01C

DeliriousHD said:
also BL: A0.1C (SHA-E29F91E, 2015-7-28 16;16;36)
Click to expand...
Click to collapse
2015-7-28 date is definitely from lollipop. I'd suggest heading over to the firmware thread and grabbing the newest marshmallow full firmware update (I think the sept patch is the newest out there), fastboot flash all of that, then try again.

jason2678 said:
2015-7-28 date is definitely from lollipop. I'd suggest heading over to the firmware thread and grabbing the newest marshmallow full firmware update (I think the sept patch is the newest out there), fastboot flash all of that, then try again.
Click to expand...
Click to collapse
Which thread? I can go looking but ive been to so many its confusing how to use the files.

jason2678 said:
2015-7-28 date is definitely from lollipop. I'd suggest heading over to the firmware thread and grabbing the newest marshmallow full firmware update (I think the sept patch is the newest out there), fastboot flash all of that, then try again.
Click to expand...
Click to collapse
This thread https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833 Shows a couple firmwares. but idk if i should get MPH24.49-18 , MPH24.49-18-3 or MPH24.49-18-4

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.

Baseband file for XT1643 (ATHENE_INDIA) needed

No network on any ROM (stock & LOS-based ROMs). I might have flashed the wrong baseband file, can someone please give me the baseband specifically for India? Baseband required - M8952_70030.25.03.62.01R ATHENE_INDIA_DSDS_CUST

meraj99 said:
I'm on RR Remix N and have TWRP 3.1.1 shreps for the recovery. I can flash RR without any issues but whenever I try flashing either a JX series ROM or a fully stock ROM, TWRP says 'Invalid Zip File Format'. I have access to both bootloader and recovery, everything else works fine. Can someone please guide me on what to do? Do I have to sideload the ROM via ADB? If so, please enlighten me about the procedure
Click to expand...
Click to collapse
Why not trying to reflash the twrp(may try another one from official website or of silesh nair on his thread).
I think you might have turn on md5 checksum or another this which keeps verifying the zip and no signature is found.
Reflashing is a good course as it do not erase any data of yours.

DgnrtnX said:
Why not trying to reflash the twrp(may try another one from official website or of silesh nair on his thread).
I think you might have turn on md5 checksum or another this which keeps verifying the zip and no signature is found.
Reflashing is a good course as it do not erase any data of yours.
Click to expand...
Click to collapse
I used 3 different versions of TWRP Still didn't help. And the MD5 checksums matched, zip signature verification has been disabled too

meraj99 said:
I used 3 different versions of TWRP [emoji14] Still didn't help. And the MD5 checksums matched, zip signature verification has been disabled too
Click to expand...
Click to collapse
Try this and report. After installing wipe cache, dalvik.
If flashing recovery is problem, reflash stock rom w/ stock recovery n boot ans try again to flash twrp, might sovle the issue
Link : https://drive.google.com/file/d/1EGS-uU1QBDbrP3G4lFUSVqDSHC_ZGpMR/view?usp=sharing
Sent from my Moto G4 Plus using Tapatalk

DgnrtnX said:
Try this and report. After installing wipe cache, dalvik.
If flashing recovery is problem, reflash stock rom w/ stock recovery n boot ans try again to flash twrp, might sovle the issue
Link : https://drive.google.com/file/d/1EGS-uU1QBDbrP3G4lFUSVqDSHC_ZGpMR/view?usp=sharing
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
can you please tell me how to use the stock recovery? It just says 'No Command' everytime I boot into it

meraj99 said:
can you please tell me how to use the stock recovery? It just says 'No Command' everytime I boot into it
Click to expand...
Click to collapse
Its power button followed by vol up, but hey that recovery ain't gonna help you. Im just saying you to reflash it as it will erase all the data of current twrp recovery which might interfere with another recovery(changes are negligible, but then too).
I gave you link to a 64-bit twrp made by dreamester and silesh nair. Try it and see if it works.

You can not flash stock ROM from TWRP or other custom recovery. You need a PC with Moto Drivers and fastboot tools installed. Then you have to flash the stock rom from fastboot (generally instructions are given inside rom zip in a file called 'flashfile.xml'). I can't say about flashing JX series ROM (maybe it needs you to be on stock first or something like that) but here are the files needed to install Motorola ADB and FASTBOOT drivers and ADB & FASTBOOT tools on windows pc:
https://firmware.center/software/Android/platform-tools/win/ and https://firmware.center/software/Motorola/
---------- Post added at 10:15 PM ---------- Previous post was at 10:11 PM ----------
meraj99 said:
can you please tell me how to use the stock recovery? It just says 'No Command' everytime I boot into it
Click to expand...
Click to collapse
To get into stock recovery press VOLUME UP while pressing and holding POWER button but you can't flash custom ROM or wipe SYSTEM from there. For that purpose use Official latest TWRP recovery from their website.

JackFrost said:
You can not flash stock ROM from TWRP or other custom recovery. You need a PC with Moto Drivers and fastboot tools installed. Then you have to flash the stock rom from fastboot (generally instructions are given inside rom zip in a file called 'flashfile.xml'). I can't say about flashing JX series ROM (maybe it needs you to be on stock first or something like that) but here are the files needed to install Motorola ADB and FASTBOOT drivers and ADB & FASTBOOT tools on windows pc:
https://firmware.center/software/Android/platform-tools/win/ and https://firmware.center/software/Motorola/
---------- Post added at 10:15 PM ---------- Previous post was at 10:11 PM ----------
To get into stock recovery press VOLUME UP while pressing and holding POWER button but you can't flash custom ROM or wipe SYSTEM from there. For that purpose use Official latest TWRP recovery from their website.
Click to expand...
Click to collapse
I already have these installed! But when I run RDS and connect my phone in fastboot mode to the computer, RDS doesn't detect it in the program. I mean, the device doesn't show up in the boxes below. But when I run 'fastboot devices' in CMD I can see my device connected. And can you pleeease tell me how to flash ROMs through the stock recovery?

meraj99 said:
I already have these installed! But when I run RDS and connect my phone in fastboot mode to the computer, RDS doesn't detect it in the program. I mean, the device doesn't show up in the boxes below. But when I run 'fastboot devices' in CMD I can see my device connected. And can you pleeease tell me how to flash ROMs through the stock recovery?
Click to expand...
Click to collapse
Stock recovery don't flash roms, thats why we use customs recovery. As he mentioned just flash the stock rom, enable usb debugging and oem unlocked. Just flash the files and again flash the recovery which ever suits you and thats it.
Note : take backup first as it wipes your internal storage.

DgnrtnX said:
Stock recovery don't flash roms, thats why we use customs recovery. As he mentioned just flash the stock rom, enable usb debugging and oem unlocked. Just flash the files and again flash the recovery which ever suits you and thats it.
Note : take backup first as it wipes your internal storage.
Click to expand...
Click to collapse
well, how do I flash...? When I try to flash using TWRP it gives the error. I've tried almost all available TWRP v3+ recoveries

meraj99 said:
well, how do I flash...? When I try to flash using TWRP it gives the error. I've tried almost all available TWRP v3+ recoveries
Click to expand...
Click to collapse
Go into bootloader and then flash the file linked below from computer.
Note : usb debugging is must.
Link : https://www.google.co.in/amp/s/foru...tock-rom-npjs25-93-14-4-march-1-t3608138/amp/

DgnrtnX said:
Go into bootloader and then flash the file linked below from computer.
Note : usb debugging is must.
Link : https://www.google.co.in/amp/s/foru...tock-rom-npjs25-93-14-4-march-1-t3608138/amp/
Click to expand...
Click to collapse
yoooo!!! IT worked! Thank you so much! ^_^

DgnrtnX said:
Go into bootloader and then flash the file linked below from computer.
Note : usb debugging is must.
Link : https://www.google.co.in/amp/s/foru...tock-rom-npjs25-93-14-4-march-1-t3608138/amp/
Click to expand...
Click to collapse
erm, my SIM isn't being detected... WiFi works fine

meraj99 said:
erm, my SIM isn't being detected... WiFi works fine
Click to expand...
Click to collapse
Just flash twrp and which ever rom you like, and see if they are working or not.

DgnrtnX said:
Just flash twrp and which ever rom you like, and see if they are working or not.
Click to expand...
Click to collapse
Not working

meraj99 said:
Not working
Click to expand...
Click to collapse
I think reflashing the stock rom is the only thing to do. Read carefully whatever is written in that thread. And see if all the commands are properly exicuted.
I dont know any work around for sim as i have never had that issue. Tell me if its solved or not for just a bit of knowledge.
Edit : just for reference you are not using moto g4 play device, are you?

Standard ROM and recovery cannot be flashed by TWRP, only in fastboot mode.

DgnrtnX said:
I think reflashing the stock rom is the only thing to do. Read carefully whatever is written in that thread. And see if all the commands are properly exicuted.
I dont know any work around for sim as i have never had that issue. Tell me if its solved or not for just a bit of knowledge.
Edit : just for reference you are not using moto g4 play device, are you?
Click to expand...
Click to collapse
nah, G4+. Problem is with the baseband

meraj99 said:
nah, G4+. Problem is with the baseband
Click to expand...
Click to collapse
I flashed that firmware 2 days ago and is working fine for me, try flashing baseband then. Idk link for it search in Google for it

DgnrtnX said:
I flashed that firmware 2 days ago and is working fine for me, try flashing baseband then. Idk link for it search in Google for it
Click to expand...
Click to collapse
that's what I'm looking for. I need the Indian baseband file, do you know where i can get it

How do I update my 6T rooted without erasing datas?

Dear all,
first of all I would like to be sorry if I'm saying something worng. I'm not so expert about Android world.
I've got a OnePlus 6T that I've rooted with the help of a friend some months ago.
Not it's a lot that I keep see the notification abount the OS update and I keep skipping it but it's bothering me so... I searched for a guide and I found this (https://oneplus.gadgethacks.com/how...thout-losing-root-no-computer-needed-0192638/) (I hope I can post it also if it's from another website).
It seems so simple, I've downloaded the OTA update, the TWRP and the Magisk. My issue is that whene I reboot to the recovery I'm not booting into TWRP but I suppose into the OnePlus recovery instead.
I searched angain and found this other guide (https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953) that is more complete but I can't understand if it's the proper guide I need to follow to update my device keeping it rooted and most of all without loosing any data.
Thanks,
Riki

The first guide you linked to is wrong. Do not follow that. That is why you don't have TWRP anymore. The second guide you linked to on XDA is correct. Follow the TWRP guide. Once you have TWRP reinstalled.
You must download the zip from the second link you posted here at XDA.
Flash the Zip in TWRP. This flash the update to the opposite slot. It also wipes out TWRP and replaces it with the stock recovery.
Now you must reinstall TWRP. Flash the TWRP installer. This will flash TWRP to both slots.
Now reboot to recovery. This will reboot to the new slot where you update was just flashed.
This is when you install Magisk to the updated slot. You MUST do this.
Now reboot to system after you installed Magisk.
Now you have updated without losing any data.
The guide in the second link says to use the Magisk uninstaller. I've personally never done this. This is probably for people who use all sorts of weird add-ons and such. I don't know. Never uninstalled Magisk, never had a problem. That's all I can say. You can try it, or you can follow the official instructions.

OhioYJ said:
The first guide you linked to is wrong. Do not follow that. That is why you don't have TWRP anymore. The second guide you linked to on XDA is correct. Follow the TWRP guide. Once you have TWRP reinstalled.
You must download the zip from the second link you posted here at XDA.
Flash the Zip in TWRP. This flash the update to the opposite slot. It also wipes out TWRP and replaces it with the stock recovery.
Now you must reinstall TWRP. Flash the TWRP installer. This will flash TWRP to both slots.
Now reboot to recovery. This will reboot to the new slot where you update was just flashed.
This is when you install Magisk to the updated slot. You MUST do this.
Now reboot to system after you installed Magisk.
Now you have updated without losing any data.
The guide in the second link says to use the Magisk uninstaller. I've personally never done this. This is probably for people who use all sorts of weird add-ons and such. I don't know. Never uninstalled Magisk, never had a problem. That's all I can say. You can try it, or you can follow the official instructions.
Click to expand...
Click to collapse
Thanks OhioYJ,
so, before I can follow the TWRP guide, I must reinstall it. Could you please give me a link to a guide on how to do it?
Thanks again,
Riki

RikiBez said:
Thanks OhioYJ,
so, before I can follow the TWRP guide, I must reinstall it. Could you please give me a link to a guide on how to do it?
Click to expand...
Click to collapse
[Guide] OnePlus 6T [Fajita]: Unlock | Flash TWRP | Root | Nandroid & EFS Backup !!
Thanks to Funk Wizard again. Don't forget the section about backing up your modem, this is always important in case something really goes wrong. You'll probably never need it, but if you ever do you'll be really glad you have it.

OhioYJ said:
[Guide] OnePlus 6T [Fajita]: Unlock | Flash TWRP | Root | Nandroid & EFS Backup !!
Thanks to Funk Wizard again. Don't forget the section about backing up your modem, this is always important in case something really goes wrong. You'll probably never need it, but if you ever do you'll be really glad you have it.
Click to expand...
Click to collapse
I followed the guide but I get stucked into a loot without been able to boot into TWRP. I'm only able to enter the recovery mode and the fastboot mode but when I launch the command from Windows it finish with no error but the phone still stuck on the fastboot logo or the oneplus logo. After many tryes now I've got only this and also errors on PC:
Old_video_link_removed
EDIT: At the moment I'm not event able to enter the recovery mode, I keep restarting it and it will only boot to the fastmode.

RikiBez said:
I followed the guide but I get stucked into a loot without been able to boot into TWRP. I'm only able to enter the recovery mode and the fastboot mode but when I launch the command from Windows it finish with no error but the phone still stuck on the fastboot logo or the oneplus logo. After many tryes now I've got only this and also errors on PC:
https://youtu.be/7Re-p7Z1yhc
EDIT: At the moment I'm not event able to enter the recovery mode, I keep restarting it and it will only boot to the fastmode.
Click to expand...
Click to collapse
It's booting into recovery, but the OnePlus recovery. That is what the menu that is asking you to select a language is. When you enter the command fastboot boot trwp.img you don't get any sort of error? Or the phone doesn't respond?

OhioYJ said:
It's booting into recovery, but the OnePlus recovery. That is what the menu that is asking you to select a language is. When you enter the command fastboot boot trwp.img you don't get any sort of error? Or the phone doesn't respond?
Click to expand...
Click to collapse
At the beginning I had no error nor on PC not on phone. Now that I’m stuck into the fastboot I keep getting the error on windows that say he donno the fastboot command but the phone stand still.

RikiBez said:
At the beginning I had no error nor on PC not on phone. Now that I’m stuck into the fastboot I keep getting the error on windows that say he donno the fastboot command but the phone stand still.
Click to expand...
Click to collapse
Is fastboot installed? Are you typing the commands correctly?
Sent from my OnePlus 6T using XDA-Developers Legacy app

RikiBez said:
At the beginning I had no error nor on PC not on phone. Now that I’m stuck into the fastboot I keep getting the error on windows that say he donno the fastboot command but the phone stand still.
Click to expand...
Click to collapse
Sounds like you're not running the command from the folder where fastboot.exe is located.
Makes me wonder why you did it this way in the first place. And why people suggested it. Easiest way to install updates on a rooted 6T is to install the update through the normal updater without rebooting, going to Magisk Manager and selecting install to inactive slot and rebooting only after that. That's really all there is to it.

CazeW said:
Sounds like you're not running the command from the folder where fastboot.exe is located.
Makes me wonder why you did it this way in the first place. And why people suggested it. Easiest way to install updates on a rooted 6T is to install the update through the normal updater without rebooting, going to Magisk Manager and selecting install to inactive slot and rebooting only after that. That's really all there is to it.
Click to expand...
Click to collapse
If I want to clean flash my 9.0.13 rooted TWRP. What do I need to uninstall or wipe? Im on 9.0.13 currently
Sent from my OnePlus 6T using XDA-Developers Legacy app

i7vSa7vi7y said:
Is fastboot installed? Are you typing the commands correctly?
Sent from my OnePlus 6T using XDA-Developers Legacy app
Click to expand...
Click to collapse
Fastboot was working until I reinstalled adb and OnePlus drivers.

CazeW said:
Sounds like you're not running the command from the folder where fastboot.exe is located.
Makes me wonder why you did it this way in the first place. And why people suggested it. Easiest way to install updates on a rooted 6T is to install the update through the normal updater without rebooting, going to Magisk Manager and selecting install to inactive slot and rebooting only after that. That's really all there is to it.
Click to expand...
Click to collapse
I didn’t know any other way. That’s why I asked how to do it. Anyway I’m running the command from the right folder. Maybe something broke on my laptop.
Yesterday evening I tried from a new laptop windows 10, installed adb and OnePlus driver for the first time and I was able to run the commands without the error not finding the command but:
Fastboot boot twrp.image returned me an error
If I run fastboot flash boot twrp.image it does not give me error but the phone does not response. It only boot to the boot loader.

RikiBez said:
I didn’t know any other way. That’s why I asked how to do it. Anyway I’m running the command from the right folder. Maybe something broke on my laptop.
Yesterday evening I tried from a new laptop windows 10, installed adb and OnePlus driver for the first time and I was able to run the commands without the error not finding the command but:
Fastboot boot twrp.image returned me an error
If I run fastboot flash boot twrp.image it does not give me error but the phone does not response. It only boot to the boot loader.
Click to expand...
Click to collapse
Try uninstalling adb. Delete the whole folder and install it again. Try updating your netframework on your PC and the latest C++
Sent from my OnePlus 6T using XDA-Developers Legacy app

I'm creating a new tread about the issue and the state where I am because now I can't update or keep data, I just need to recover the phone to a normal state.

RikiBez said:
I'm creating a new tread about the issue and the state where I am because now I can't update or keep data, I just need to recover the phone to a normal state.
Click to expand...
Click to collapse
Use the msm tool for that
Sent from my OnePlus 6T using XDA-Developers Legacy app

Flashing the fastboot rom would probably have gotten you back in and maybe with your data in tact. Now fair warning I'm a Linux user anyways, but really fastboot and adb are so much easier in Linux. For people that have issues, it sometimes is easier just to make a bootable USB / CD of Linux Mint or Ubuntu and then from Synaptic or the Package manager install adb and fastboot. No drivers or anything else to install, everything will just work.
Last time I got stuck in fastboot I just used the fastboot ROM to get back to bootable.

OhioYJ said:
Flashing the fastboot rom would probably have gotten you back in and maybe with your data in tact. Now fair warning I'm a Linux user anyways, but really fastboot and adb are so much easier in Linux. For people that have issues, it sometimes is easier just to make a bootable USB / CD of Linux Mint or Ubuntu and then from Synaptic or the Package manager install adb and fastboot. No drivers or anything else to install, everything will just work.
Last time I got stuck in fastboot I just used the fastboot ROM to get back to bootable.
Click to expand...
Click to collapse
Those fastboot roms have sure saved me from raging before
I would also recommend using migrate, it's in the play store and it backs up all your data and then puts it in a flashable zip

i7vSa7vi7y said:
If I want to clean flash my 9.0.13 rooted TWRP. What do I need to uninstall or wipe? Im on 9.0.13 currently
Sent from my OnePlus 6T using XDA-Developers Legacy app
Click to expand...
Click to collapse
Do a factory reset from TWRP and flash the full ROM.

One best method...and the method that works 100% tested for upgrading a rooted OOS to new OOS version without any loss of data, without any issues.
I'll mention the guide that I have used to upgrade from 9.0.12 rooted to 9.0.13 rooted. Without any loss of data
Download latest OOS full ROM
Boot to TWRP
Flash OOS 9.0.13
Flash TWRP installer zip
Reboot system
Phone will boot.
Now go back to recovery mode
Flash Magisk if u want root again
Done
No confusion. No data loss. Not being stuck. Sweet and Simple.

sanjeev7 said:
One best method...and the method that works 100% tested for upgrading a rooted OOS to new OOS version without any loss of data, without any issues.
I'll mention the guide that I have used to upgrade from 9.0.12 rooted to 9.0.13 rooted. Without any loss of data
Download latest OOS full ROM
Boot to TWRP
Flash OOS 9.0.13
Flash TWRP installer zip
Reboot system
Phone will boot.
Now go back to recovery mode
Flash Magisk if u want root again
Done
No confusion. No data loss. Not being stuck. Sweet and Simple.
Click to expand...
Click to collapse
So I don't have to wipe my system data or anything. I heard some people had the problem of getting stuck or that there was a red warning screen that popped up when booting, and I'm not talking about the bootloader message. I'm currently on 9.0.11. Also should I download the latest version of TWRP or should I use the one I'm using currently. Don't wanna mess anything up. Another guide I read said I should flash the oos rom, then TWRP, than magisk