Related
*** 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?
The phone is the Huawei Nexus 6P (MMB29M). No clue how this happened, but I managed to get root (working fine I can run apps that require root), but TWRP isn't on my phone. When I try to boot to recovery, it gives me the dead android symbol (dead android with front flap opened up and little red exclamation point). I can get into the boot loader just fine though, it's ONLY the recovery that is missing. Is it okay to use the TWRP app to install recovery the easy way? I have the TWRP app on my phone from the (failed) TWRP install, I guess. Or do I need to go through the whole root/recovery fastboot process again?
I don't know how I even got root without recovery, tbh. I was obviously in TWRP when I flashed superSU and busybox, but for whatever reason, it didn't stick. The only thing I can think of is that the phone took the liberty of replacing the recovery on its own when I restarted the phone (I didn't think to go back into recovery immediately, so the phone overwrote it...is that possible?)
The reason I'm asking about the TWRP app is because it has a very specific directory that it says it needs to install into and if that directory is wrong, the phone could be bricked. I've had the phone for less than a week, I'd prefer not to brick it. This is my 5th android device and I've never run into this issue before...in fact, I didn't even know it was POSSIBLE to get root without recovery. I did get a soft-brick earlier in the process, but I fixed it by re-flashing the stock android ROM (I also had to go change my pants afterward, but that's a story for another thread).
Thanks in advance for any assistance you can provide and have a nice Friday.
baronmax said:
The phone is the Huawei Nexus 6P (MMB29M). No clue how this happened, but I managed to get root (working fine I can run apps that require root), but TWRP isn't on my phone. When I try to boot to recovery, it gives me the dead android symbol (dead android with front flap opened up and little red exclamation point). I can get into the boot loader just fine though, it's ONLY the recovery that is missing. Is it okay to use the TWRP app to install recovery the easy way? I have the TWRP app on my phone from the (failed) TWRP install, I guess. Or do I need to go through the whole root/recovery fastboot process again?
I don't know how I even got root without recovery, tbh. I was obviously in TWRP when I flashed superSU and busybox, but for whatever reason, it didn't stick. The only thing I can think of is that the phone took the liberty of replacing the recovery on its own when I restarted the phone (I didn't think to go back into recovery immediately, so the phone overwrote it...is that possible?)
The reason I'm asking about the TWRP app is because it has a very specific directory that it says it needs to install into and if that directory is wrong, the phone could be bricked. I've had the phone for less than a week, I'd prefer not to brick it. This is my 5th android device and I've never run into this issue before...in fact, I didn't even know it was POSSIBLE to get root without recovery. I did get a soft-brick earlier in the process, but I fixed it by re-flashing the stock android ROM (I also had to go change my pants afterward, but that's a story for another thread).
Thanks in advance for any assistance you can provide and have a nice Friday.
Click to expand...
Click to collapse
This happened to me after the first time I installed twrp. I selected read only system after booting into twrp for the first time(they ask you if you want a read only option) and the stock rom would over write twrp with the stock recovery. Only fix for me was starting from scratch using step 11 here http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928. When you install twrp dont select the read only option and you'll be fine. Just remember not to let twrp install Su when it asks you to.
did you not read and follow the VERY detailed and specific instructions on how to do all of this, before beginning the process?
mistakes happen, and we are all here to help, but a softbrick followed by no recovery etc just seems like you tried to wing it without taking the proper time to read how to do it on your new device.
I'm sure someone will be able to give you a definite answer, but I also advise you to read @Heisenberg's guide on how to do it all on your 6P in the General section
Soulfly3 said:
did you not read and follow the VERY detailed and specific instructions on how to do all of this, before beginning the process?
mistakes happen, and we are all here to help, but a softbrick followed by no recovery etc just seems like you tried to wing it without taking the proper time to read how to do it on your new device.
I'm sure someone will be able to give you a definite answer, but I also advise you to read @Heisenberg's guide on how to do it all on your 6P in the General section
Click to expand...
Click to collapse
I read everything and my only mistake was selecting the read only option which clearly tell you that if you select read only it cant prevent the stock rom from over writing twrp with its own recovery. Mistakes happen.
can you not just install twrp again from the bootloader?
ahfu25 said:
I read everything and my only mistake was selecting the read only option which clearly tell you that if you select read only it cant prevent the stock rom from over writing twrp with its own recovery. Mistakes happen.
Click to expand...
Click to collapse
I was responding to the OP, not you.
uicnren said:
can you not just install twrp again from the bootloader?
Click to expand...
Click to collapse
Yes, but I was wondering if it was a bad idea to just let the TWRP app do it? That's what it's designed to do (that, and update TWRP). That's why I asked the question, I wasn't sure if that was a viable way to go about this or whether I just needed to re-do it from the nexus 6p "how to" that's on the site here.
Soulfly3 said:
I was responding to the OP, not you.
Click to expand...
Click to collapse
OK...have a nice day
I can't say for sure that I understand what you mean by using twrp when you don't even have it... but maybe see this post. (The bottom of that post.)
---------- Post added at 11:51 AM ---------- Previous post was at 11:46 AM ----------
oh, I get what you're saying now - can you do it with the twrp app - as in an actual app. i missed that word. I think i remember Heisenburg saying that, no, you shouldn't use the app. I think it doesn't get the right twrp version. the version we need for the 6p is in beta and not available throught the app.
---------- Post added at 12:07 PM ---------- Previous post was at 11:51 AM ----------
In a previous post of mine, I quoted the explanation from TWRP of the system read-only vs read-write thing: http://forum.xda-developers.com/showpost.php?p=64707169&postcount=2143 I think you may need to mount the system read-write to get twrp to "stick". ...or you need root (according to sirxdroid)? I don't know which... I'd love to know how you get it working again!
p.s. Sorry to keep appending to my response...
Good explanations and links, I had the same issue when I decided to root. I did not choose read only during my initial flash of TWRP and could not figure out why every time I flashed TWRP, rebooted then went into recovery, I lost TWRP! After I did my due diligence and read the threads, I realized what I did wrong. I flashed back to stock, then flashed TWRP as recovery. I went into recovery via bootloader and chose read only. Then I installed the su.zip, rebooted the bootloader, then it was all good. Good luck.
I think what I did wrong is fail to wipe the caches (not sure how I missed it, but I did, originally). I'm not entirely sure why that makes any difference, but I went through the rooting process again and installed TWRP, now things are working properly. I did two things differently, wiping the cache and booting directly back into recovery after installing recovery. I saw on the TWRP website that some ROMs will overwrite the boot.img and recovery sections if you don't boot back into recovery immediately (it doesn't overwrite them after the second time, for whatever reason). I'm not sure if this is what happened or not, but it's the one thing that actually makes SOME sense to me.
It's interesting that there's an app out there which claims to install TWRP, but people shouldn't use it, that would be a mighty handy app to have if it worked properly, no more worries and very little fuss.
Why not just fastboot flash recovery........takes 10 seconds.
For the longest time while installing a new ROM or working in TWRP, I have been asked if I want TWRP to go ahead and install SuperSU for me even if sometimes the device is already rooted. Every guide and advice ever, has always said to ignore this completely. This remains true with Heisenberg's guide.
Heisenberg said:
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 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.[/b]
Click to expand...
Click to collapse
Heisenberg mentions it is not compatible. My question is why is this true? I flashed a 6P specific version of TWRP.
Also, are there specific circumstances where one would want TWRP to install SuperSU? To me it just seems like a handy time saver especially if you forgot to download it or something.
tsuttie99 said:
For the longest time while installing a new ROM or working in TWRP, I have been asked if I want TWRP to go ahead and install SuperSU for me even if sometimes the device is already rooted. Every guide and advice ever, has always said to ignore this completely. This remains true with Heisenberg's guide.
Heisenberg mentions it is not compatible. My question is why is this true? I flashed a 6P specific version of TWRP.
Also, are there specific circumstances where one would want TWRP to install SuperSU? To me it just seems like a handy time saver especially if you forgot to download it or something.
Click to expand...
Click to collapse
Root with marshmallow is different to all previous Android versions, it requires a modified boot.img. The most recent versions of the beta branch of SuperSU patches the boot.img for you, and you get working root. The version that TWRP offers to install is outdated and doesn't perform thief modification of the boot.img, flashing it will result in a boot loop. For the above reasons there are no circumstances where you'd want TWRP to install it for you.
PS. You could have just asked this question in the guide thread.
Heisenberg said:
Root with marshmallow is different to all previous Android versions, it requires a modified boot.img. The most recent versions of the beta branch of SuperSU patches the boot.img for you, and you get working root. The version that TWRP offers to install is outdated and doesn't perform thief modification of the boot.img, flashing it will result in a boot loop. For the above reasons there are no circumstances where you'd want TWRP to install it for you.
PS. You could have just asked this question in the guide thread.
Click to expand...
Click to collapse
Thank you for the clear explanation. I suppose you are correct about that, my apologies. I think I was getting it confused for a different thread which was closed. In case you can't tell, I'm new here. Lol
tsuttie99 said:
Thank you for the clear explanation. I suppose you are correct about that, my apologies. I think I was getting it confused for a different thread which was closed. In case you can't tell, I'm new here. Lol
Click to expand...
Click to collapse
Well, welcome to XDA then! Here's the thread in case you need it:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Not that I want to, but if I wanted to.. Is there a way to return the unlocked bootloader version back to stock to where I can receive OTA's?
Like I said, I don't necessarily want to, but if I needed to for some reason.
tele_jas said:
Not that I want to, but if I wanted to.. Is there a way to return the unlocked bootloader version back to stock to where I can receive OTA's?
Like I said, I don't necessarily want to, but if I needed to for some reason.
Click to expand...
Click to collapse
Yes you can via Rczrider 's TWRP backup
tele_jas said:
Not that I want to, but if I wanted to.. Is there a way to return the unlocked bootloader version back to stock to where I can receive OTA's?
Like I said, I don't necessarily want to, but if I needed to for some reason.
Click to expand...
Click to collapse
XblackdemonX said:
Yes you can via Rczrider 's TWRP backup
Click to expand...
Click to collapse
Yeah, it looks like @tenfar updated their tool to use the stock files from my untouched B20: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
rczrider said:
Yeah, it looks like @tenfar updated their tool to use the stock files from my untouched B20: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
Click to expand...
Click to collapse
if someone can make a guide on HOW-TO (Steps + FIles + Images needed) i can give it a shot...
just send me a PM if you know the HOW-TO :good:
Mmmmm, noone yet?.... I guess I'll start gathering info.
One thing I wanna make sure flashing @tenfar boot. Img = need Data wipe right?
DrakenFX said:
Mmmmm, noone yet?.... I guess I'll start gathering info.
One thing I wanna make sure flashing @tenfar boot. Img = need Data wipe right?
Click to expand...
Click to collapse
I've been flashing custom ROM's for several years, but I've bricked one too many phones over the years "not knowing" the correct way to do certain things... So I started this thread to see what those steps were because I'm too scared to attempt it myself. :silly:
So, I know I'd appreciate your efforts in this!
tele_jas said:
I've been flashing custom ROM's for several years, but I've bricked one too many phones over the years "not knowing" the correct way to do certain things... So I started this thread to see what those steps were because I'm too scared to attempt it myself. :silly:
So, I know I'd appreciate your efforts in this!
Click to expand...
Click to collapse
I'm curious too and I wanna give it shot,
P. S. Any way to use terminal or adb to pull the partition list with their Extension?
Like for sample. " ext4 system /dev/block/sde13 " or something similar with extension?
Has anyone got a step-by-step for this yet? I searched, but don't see a "Back to Stock" thread
tele_jas said:
Has anyone got a step-by-step for this yet? I searched, but don't see a "Back to Stock" thread
Click to expand...
Click to collapse
i created a Thread for users who have run into the No Boot issues and those problems , so i can gather more info of the causes of their problems but nobody had reply yet,
just waiting so i can test things and get back to Stock B20 with Root + TWRP and lock bootloader
It is still not clear where the unlock bootloader state is recorder. I have checked a couple of partitions but they are identical to locked B20 (aboot, devinfo were my prime suspects)
So assuming that this is not a permanent thing for the bootloader state and can be reversed, steps would be something like this
1. lock bootloader
2a. flash Stock B20 image and signed(tenfars) TWRP via axon7root
3. Reboot in TWRP (read only mode), full factory wipe (wipe plus /data format), flash original system image via twrp, wipe data again
4. turn off phone, don't reboot (no system start)
5. flash stock recovery via axon7root
6. Reboot to Stock Recovery direct (do not boot)
7. Factory reset from stock recovery
8. Reboot
But there are a few unknowns yet, even with stock system, boot and recovery we still have stuck loops unless using modded boot. My guess is that TWRP mods /system on exit, that's why i put read only mode but not sure if you can restore it if it's not rw. Since it's image to device it should work, RW is for mounting partition
And big one is if unlock state is permanent or not, not sure anyone tried yet
peramikic said:
It is still not clear where the unlock bootloader state is recorder. I have checked a couple of partitions but they are identical to locked B20 (aboot, devinfo were my prime suspects)
So assuming that this is not a permanent thing for the bootloader state and can be reversed, steps would be something like this
1. lock bootloader
2a. flash Stock B20 image and signed(tenfars) TWRP via axon7root
3. Reboot in TWRP (read only mode), full factory wipe (wipe plus /data format), flash original system image via twrp, wipe data again
4. turn off phone, don't reboot (no system start)
5. flash stock recovery via axon7root
6. Reboot to Stock Recovery direct (do not boot)
7. Factory reset from stock recovery
8. Reboot
But there are a few unknowns yet, even with stock system, boot and recovery we still have stuck loops unless using modded boot. My guess is that TWRP mods /system on exit, that's why i put read only mode but not sure if you can restore it if it's not rw. Since it's image to device it should work, RW is for mounting partition
And big one is if unlock state is permanent or not, not sure anyone tried yet
Click to expand...
Click to collapse
those steps were the same i was planning to do plus flashing something else, but seems like i may be not doing the other flashing file now......well still gathering more info and will see.
P.S. Thanks for the info. @peramikic
DrakenFX said:
i created a Thread for users who have run into the No Boot issues and those problems , so i can gather more info of the causes of their problems but nobody had reply yet,
just waiting so i can test things and get back to Stock B20 with Root + TWRP and lock bootloader
Click to expand...
Click to collapse
Gottcha.... I was just curious, because I'm starting to have a few random issues (reboots, apps opening without tapping them, google voice commands not working like they did just a few days ago) I'd like to get back to stock and maybe start over. Of course, I didn't make a backup up until after I flashed SuperSU and my apps downloaded so I have no "stock" TWRP backup. **But, this all could be "theme" related too, since I'm running a dark theme that isn't quite compatible with the A7 yet.
I may try removing the theme and let it run a day or two and see how it does?
I've read the guides on how to unlock bootloader, install twrp & gain root (magisk preferred) with 10.3.0 and I still do not quite understand.
This is the best Android I've had and I'd really like to do this right. Would anyone please help me? Thank you, Stephen
stovo06 said:
I've read the guides on how to unlock bootloader, install twrp & gain root (magisk preferred) with 10.3.0 and I still do not quite understand.
This is the best Android I've had and I'd really like to do this right. Would anyone please help me? Thank you, Stephen
Click to expand...
Click to collapse
You can't go wrong with the guide here https://r.tapatalk.com/shareLink/to...9&share_fid=3793&share_type=t&link_source=app
It's very simple to follow
Just update to the newest version TWRP and Magisk
Sent from my ONEPLUS A6010 using Tapatalk
clsA said:
You can't go wrong with the guide here https://r.tapatalk.com/shareLink/to...9&share_fid=3793&share_type=t&link_source=app
It's very simple to follow
Just update to the newest version TWRP and Magisk
Click to expand...
Click to collapse
I thought this was for 9.x.x
stovo06 said:
I thought this was for 9.x.x
Click to expand...
Click to collapse
Nothing has changed but the versions of TWRP and Magisk
Sent from my ONEPLUS A6010 using Tapatalk
clsA said:
Nothing has changed but the versions of TWRP and Magisk
Click to expand...
Click to collapse
Thank you. Definitely need to get this done.
Atm I think I'm gonna stick with stock ROM but maybe a custom kernel.
Any suggestions?
clsA said:
Nothing has changed but the versions of TWRP and Magisk
Sent from my ONEPLUS A6010 using Tapatalk
Click to expand...
Click to collapse
Thanks for trying to help, but I don't think this is entirely correct. The "fastboot boot" command was removed in a10, and an alternative method was eventually developed AFAIK.
I never did get a successful root on this device after spending a whole day on it. It's difficult because little bits of information are scattered everywhere instead of in a single up-to-date guide. And a few months ago, no one could agree on anything. Just look at how many other people got semi-hard bricked.
flyoffacliff said:
Thanks for trying to help, but I don't think this is entirely correct. The "fastboot boot" command was removed in a10, and an alternative method was eventually developed AFAIK.
I never did get a successful root on this device after spending a whole day on it. It's difficult because little bits of information are scattered everywhere instead of in a single up-to-date guide. And a few months ago, no one could agree on anything. Just look at how many other people got semi-hard bricked.
Click to expand...
Click to collapse
Fastboot boot command has been allegedly fixed in 10.3.0 and this fix has been confirmed by several people. So yes the philosophy and method hasn't changed since years. At worse you use 'fastboot flash boot' command instead. That's only one change.
You can still extract boot img from payload.bin on your computer, transfer it to your phone and use Magisk manager to patch it and then transfer and flash it with fastboot from your computer. Then you flash twrp installer as a module in Magisk Manager once your phone is rooted. That also hasn't changed for years, this method has always existed.
Most of people bricking their device are doing one thing or another wrong.
Striatum_bdr said:
Fastboot boot command has been allegedly fixed in 10.3.0 and this fix has been confirmed by several people. So yes the philosophy and method hasn't changed since years. At worse you use 'fastboot flash boot' command instead. That's only one change.
You can still extract boot img from payload.bin on your computer, transfer it to your phone and use Magisk manager to patch it and then transfer and flash it with fastboot from your computer. Then you flash twrp installer as a module in Magisk Manager once your phone is rooted. That also hasn't changed for years, this method has always existed.
Most of people bricking their device are doing one thing or another wrong.
Click to expand...
Click to collapse
This is where I start getting confused lol.
I appreciate the help, but this is not what I'll accustomed to.
Anything you recommend reading to help educate myself?
stovo06 said:
This is where I start getting confused lol.
I appreciate the help, but this is not what I'll accustomed to.
Anything you recommend reading to help educate myself?
Click to expand...
Click to collapse
https://forum.xda-developers.com/on...l-oxygenos-beta-1-oneplus-6t-t3881099/page484
Read Cultofluna post
And search Google for it, many tutorials
Striatum_bdr said:
https://forum.xda-developers.com/on...l-oxygenos-beta-1-oneplus-6t-t3881099/page484
Read Cultofluna post
And search Google for it, many tutorials
Click to expand...
Click to collapse
Nice instructions, But I'm curious why you think he needs them ?
all he needs is
unlock bootloader
fastboot flash boot TWRP.img
boot to TWRP / Flash TWRP installer.zip
Reboot recovery
Flash Magisk.zip in TWRP
reboot
done
the guide I linked earlier goes into great detail explaining each of these steps
He could even use the All in one tool after downloading the correct versions of TWRP and Magisk
clsA said:
Nice instructions, But I'm curious why you think he needs them ?
all he needs is
unlock bootloader
fastboot flash recovery TWRP.img
boot to TWRP / Flash TWRP installer.zip
Reboot recovery
Flash Magisk.zip in TWRP
reboot
done
the guide I linked earlier goes into great detail explaining each of these steps
He could even use the All in one tool after downloading the correct versions of TWRP and Magisk
Click to expand...
Click to collapse
I know that it's the way Android works since years....
But a guy warned him about bricked phones and other very alarming prophecies... So I gave him a plan B in case of...
Striatum_bdr said:
I know that it's the way Android works since years....
But a guy warned him about bricked phones and other very alarming prophecies... So I gave him a plan B in case of...
Click to expand...
Click to collapse
That's what I've read as well. And there are many solutions but I find them scattered all over the forms.
And I don't trust YouTube videos lol
I just want to make sure it works with 10.3.0.
I can downgrade if necessary but trying to find the easiest method.
Thanks guys for all your help. Maybe I'll post a 10.3.0 thread after this if it's needed to avoid confusion
stovo06 said:
I just want to make sure it works with 10.3.0.
I can downgrade if necessary but trying to find the easiest method.
Thanks guys for all your help. Maybe I'll post a 10.3.0 thread after this if it's needed to avoid confusion
Click to expand...
Click to collapse
I don't think there is the need of another thread. Many are already talking about rooting and flashing twrp.
What makes people confuse is that perhaps some of them think things have changed... And that methods are bound to an Android version.
Nothing has changed.
Fastbooting TWRP and then flashing it, is the way we do it since years. Patching boot img as an alternative is also a classical way to root.
People are blinded by tiny differences and don't see that the frame hasn't changed. You unlock the bootloader, then boot to twrp and then either you flash only Magisk either you flash twrp then Magisk. Very simple. Always with latest versions.
It's because xda threads are not moderated except for offenses, etc that many users post their 'own' recipe every 2 pages without anybody cleaning and organizing things to make them understandable. And the fact that threads are not well maintained in time, with titles and first posts instructions that can seem obsolete.... Especially on old phones like our when devs are quitting the scene without designating a maintainer
clsA said:
Nice instructions, But I'm curious why you think he needs them ?
Click to expand...
Click to collapse
Thanks for clarifying.
Even for someone experienced with flashing and modding in the past, but I've been away from the flashing world.
There is a lot of conflicting info about this. Some say to patch boot img manually.
The TWRP thread says to install TWRP as a magisk module.
But seriously, Thanks. I'm glad I came across this thread. I thought the old way of doing things was done with Android 10, until I read this.
aaron74 said:
Thanks for clarifying.
Even for someone experienced with flashing and modding in the past, but I've been away from the flashing world.
There is a lot of conflicting info about this. Some say to patch boot img manually.
The TWRP thread says to install TWRP as a magisk module.
But seriously, Thanks. I'm glad I came across this thread. I thought the old way of doing things was done with Android 10, until I read this.
Click to expand...
Click to collapse
You can do that, installing TWRP as a module, since one year or so. So you just fastboot boot twrp, flash Magisk zip, then once phone booted back to Android, flash twrp as a module with Magisk Manager
Same thing if you just want to flash kernels, no need to have TWRP, Ex Kernel Manager or Franco Kernel Manager can do this as long as you're rooted
Striatum_bdr said:
You can do that, installing TWRP as a module, since one year or so. So you just fastboot boot twrp, flash Magisk zip, then once phone booted back to Android, flash twrp as a module with Magisk Manager
Same thing if you just want to flash kernels, no need to have TWRP, Ex Kernel Manager or Franco Kernel Manager can do this as long as you're rooted
Click to expand...
Click to collapse
@Striatum_bdr you've been very helpful person here in a bit.
Since this a/b partition has come around, I have gotten multiple ways to unlock bootloader and root with my moto x4. And before I owned that Motorola, I've never had a reason to use a/b partitions. Long story short, my TWRP got screwed and I've become hesitant about doing anything with a new device. And this is the best device I've owned in many years so I have to do it right.
Unless any further issues arise, I'm going to go for it.
Thank you everyone that's helped guide me thru this.
Edit :I've no idea what patching a boot img is lol.
stovo06 said:
Thank you. Definitely need to get this done.
Atm I think I'm gonna stick with stock ROM but maybe a custom kernel.
Any suggestions?
Click to expand...
Click to collapse
Wait for render zenith
stovo06 said:
@Striatum_bdr you've been very helpful person here in a bit.
Since this a/b partition has come around, I have gotten multiple ways to unlock bootloader and root with my moto x4. And before I owned that Motorola, I've never had a reason to use a/b partitions. Long story short, my TWRP got screwed and I've become hesitant about doing anything with a new device. And this is the best device I've owned in many years so I have to do it right.
Unless any further issues arise, I'm going to go for it.
Thank you everyone that's helped guide me thru this.
Edit :I've no idea what patching a boot img is lol.
Click to expand...
Click to collapse
Yeah, this is an awesome device. Only device I've been happy with since my old Samsung note 4. Biggest thing I miss, it'd be nice to have an SD card slot!
Patching a boot image is what Magisk does when you install it. But you just would manually do this.
Last question, I've been reading too install Magisk 19.4.
Does that still apply?
Apologies for all the questions (and great appreciation for the help), but the information here is scattered and at times contradicting when all I need now is a simple magisk manager and mod ?.
Thank you all for your help.