As you may know, T815c and T815 are different when it comes to Flashing ROMs, I got a T815c and would like to try T815 ROMs, but it always fail, I've tried Odin, but it failed everytime when it's just began to flash boot.img, I also tried flash with recovery(TWRP3.0.0-0) it succeed in the script, but always fail to boot, everytime I start it shows a red text on the left-up corner: "KERNEL IS NOT SEANDROID ENFORCING" and stuck at the first booting screen. I'm really stuck here , please help!
-Currently I found some reasons, I know that I need to have a MM system in order to flash in CM ROMs, but my T815C's official latest system is still 5.0.2, so the only way I can do this is by flashing in other versions of ROMs(T815), you guys normally have T815 ROMS, but I got a T815C version, so I'm stuck at how can I flash a T815 6.0.1 system in my T815C 5.0.2, like I said before, I've downloaded some T815 ROMs, but flashing them always led to fail right before flashing boot.img(Baisically just fail right after started)
possible(not sure) ways: flash in pit file or boot.img file via odin.
-I'm thinking maybe there's a restriction or a kid of lock on my device, set by the officials to prevent us from flashing other versions, so anyone knows how to get rid of those? or maybe some other problems.
extra information: might be related: on the download mode page, there's a Secure Download:enabled
Also my SElinux status is still Enforcing
KNOX is also not removed
anyways I'm not sure what's the cause of restriction, or other problems, if anyone can help with that will be a great favor!
Jackz314 said:
As you may know, T815c and T815 are different when it comes to Flashing ROMs, I got a T815c and would like to try T815 ROMs, but it always fail, I've tried Odin, but it failed everytime when it's just began to flash boot.img, I also tried flash with recovery(TWRP3.0.0-0) it succeed in the script, but always fail to boot, everytime I start it shows a red text on the left-up corner: "KERNEL IS NOT SEANDROID ENFORCING" and stuck at the first booting screen. I'm really stuck here , please help!
Click to expand...
Click to collapse
What did you actually flash with TWRP?
Re:
ashyx said:
What did you actually flash with TWRP?
Click to expand...
Click to collapse
I tried to flash
[ROM][T810/T815] AOSP 7.0 Nougat
http://forum.xda-developers.com/tab-s2/orig-development/rom-aosp-7-0-nougat-t3452672
also tried
[ROM][OFFICIAL][T815] CyanogenMod 13
http://forum.xda-developers.com/tab-s2/orig-development/rom-cyanogenmod-13-t3387898
all failed, with TWRP 3.0.0-0(I believe it's your release, thanks for the work)
anyways, I think the problem here is probably I'm currently using T815C (China Mainland version), and the ROMs are for T815, so are there any ways to deal with that?
thx
Try booting with your stock boot.img.
Re:
ashyx said:
Try booting with your stock boot.img.
Click to expand...
Click to collapse
Just tried, the first booting screen is showing perfevtly fine(without KERNEL IS NOT SEANDROID ENFORCING), BUT, after that it will just got into black screen, nothing else happend after black screen, I've waited for 20 minutes and it's still black, after reboot it's still like that.
Jackz314 said:
Just tried, the first booting screen is showing perfevtly fine(without KERNEL IS NOT SEANDROID ENFORCING), BUT, after that it will just got into black screen, nothing else happend after black screen, I've waited for 20 minutes and it's still black, after reboot it's still like that.
Click to expand...
Click to collapse
That's a marshmallow boot image?
Re:
ashyx said:
That's a marshmallow boot image?
Click to expand...
Click to collapse
No, and I got the reason it's not working, I got a T815C and the latest system version is 5.0.2, there's no 6.0.1 stock boot.img for my version, so should I try to flash other versions ROMs' boot.img(MM)? or anyways, how can I first flash in a MM system(different than the current stock ROM), you guys normally have T815 ROMS, and I got a T815C version, so I'm stuck at how can I flash a T815 6.0.1 system in my T815C
Jackz314 said:
No, and I got the reason it's not working, I got a T815C and the latest system version is 5.0.2, there's no 6.0.1 stock boot.img for my version, so should I try to flash other versions ROMs' boot.img(MM)? or anyways, how can I first flash in a MM system(different than the current stock ROM), you guys normally have T815 ROMS, and I got a T815C version, so I'm stuck at how can I flash a T815 6.0.1 system in my T815C
Click to expand...
Click to collapse
Your bootloader is likely incompatible with MM kernels.
It's unlikely you will be able to get another bootloader to flash.
ashyx said:
Your bootloader is likely incompatible with MM kernels.
It's unlikely you will be able to get another bootloader to flash.
Click to expand...
Click to collapse
That's why I'm trying to flash a whole new system to my tablet, but with Odin, that always results fail right after beginning, do you know how to deal with that(I'm trying to flash BTU version with Odin 3.11, it fails everytime right after trying to flash boot.img), thx
Re:
Jackz314 said:
That's why I'm trying to flash a whole new system to my tablet, but with Odin, that always results fail right after beginning, do you know how to deal with that(I'm trying to flash BTU version with Odin 3.11, it fails everytime right after trying to flash boot.img), thx
Click to expand...
Click to collapse
well, I found a rom with BL,AP,CSC,CP,and pit file in BTU version, but on odin, it fails everytime because of Re-partition operation failed, now I'sm thinking maybe there's a restriction or lock on my system, or that can't be this hard.
Related
I tried to flash many roms on my cell without any succes, so i wonder if anyone can tell me wich rom should i install via original recovery sideload, I got an xt1063 type MOFB9 ON TITAN_UMTS:4.4.4/kxb21.85-23/21
Please i know i can flash and downgrade many roms via fasboot,or custome recovery twrp or pholz, but i want to know, if in original, i got the latest , or what would be the next rom to flash acording to the system i have. thanks for the help.
abispac said:
I tried to flash many roms on my cell without any succes, so i wonder if anyone can tell me wich rom should i install via original recovery sideload, I got an xt1063 type MOFB9 ON TITAN_UMTS:4.4.4/kxb21.85-23/21
Please i know i can flash and downgrade many roms via fasboot,or custome recovery twrp or pholz, but i want to know, if in original, i got the latest , or what would be the next rom to flash acording to the system i have. thanks for the help.
Click to expand...
Click to collapse
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25&page=1ALL MOTO G firmware available (1st, 2nd and 3rd Gen) pick correct XT1063 in your case
reefuge said:
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25&page=1ALL MOTO G firmware available (1st, 2nd and 3rd Gen) pick correct XT1063 in your case
Click to expand...
Click to collapse
Thank you sir, but i see this roms end in xml, wich i think are for flashing via fasboot? if im wrong please correct me, im looking for the ota original to flash via original recovery.
abispac said:
Thank you sir, but i see this roms end in xml, wich i think are for flashing via fasboot? if im wrong please correct me, im looking for the ota original to flash via original recovery.
Click to expand...
Click to collapse
thats correct these are via ADB mfastboot (which ignores OTA fingerprint check) as flashes full firmware, not the ota.zip which is only a smaller (not full firmware) update
ota.zip is NOT full firmware, so will not fix a corrupted / altered or non stock firmware
but you say you've flashed many roms.... you need to be on correct rom and matching recovery and also un-rooted to flash a OTA.zip as it checks Recovery version and the build fingerprint inside /system folder of original stock rom. if any of these mismatch it will fail.
also (apologies if wrong) but dont you believe your phone to be corrupted or read only hence why you cant flash images?
reefuge said:
thats correct these are via ADB mfastboot (which ignores OTA fingerprint check) as flashes full firmware, not the ota.zip which is only a smaller (not full firmware) update
ota.zip is NOT full firmware, so will not fix a corrupted / altered or non stock firmware
but you say you've flashed many roms.... you need to be on correct rom and matching recovery and also un-rooted to flash a OTA.zip as it checks Recovery version and the build fingerprint inside /system folder of original stock rom. if any of these mismatch it will fail.
also (apologies if wrong) but dont you believe your phone to be corrupted or read only hence why you cant flash images?
Click to expand...
Click to collapse
Chanses are my phone its corrupted, i had the hope that a mayor ota, such a 5.0 (not5.0.2) would rewrite the phone and fix it, as the olny option i have not be able to tried was install an original ota or rom via recover sideload. I got recovery KXB21.85-23. Are there any fixes for read only out there? because i have found non....
Thanks for the help thought.
abispac said:
Chanses are my phone its corrupted, i had the hope that a mayor ota, such a 5.0 (not5.0.2) would rewrite the phone and fix it, as the olny option i have not be able to tried was install an original ota or rom via recover sideload. I got recovery KXB21.85-23. Are there any fixes for read only out there? because i have found non....
Thanks for the help thought.
Click to expand...
Click to collapse
what error do you get via ADB when you flash?
can you remember what was the original firmware on phone as several for xt1063
or if boots the system version in about phone
reefuge said:
what error do you get via ADB when you flash?
can you remember what was the original firmware on phone as several for xt1063
or if boots the system version in about phone
Click to expand...
Click to collapse
Phone wont boot, its gets to the point where a blue m apears the goes to a blank screen, when flahing a rom via fasboot, all seems to get right but after restart is like nothing happened, i go back to the same state, same thing happens with twrp or philz, if you want to help, we can continue here but your more then wellcome to read this (nevermind i see you allready did)
So let me make a backup of twrp and see if i can post results, thanks allot, iveen waiting to fix this for so many days now.
A bit of background, i consider myself an advance user, someone that can google problems and fix stuff with it, ivee flashed alot of cellphones in the past ,many xt1064 and other models, just like everybody ealse, easy and no problems, but this one i just cant figure out. Seems like its on read only mode or freezed as a deepfreezed computer, dont mater how many roms i flash and the way i do, everything comes back to the same state, even if i reforma partitions, eeven if i delete pictures or folders, they come back once i reboot.
Its going to take 5hrs to upload my backup
abispac said:
Phone wont boot, its gets to the point where a blue m apears the goes to a blank screen, when flahing a rom via fasboot, all seems to get right but after restart is like nothing happened, i go back to the same state, same thing happens with twrp or philz, if you want to help, we can continue here but your more then wellcome to read this (nevermind i see you allready did)
So let me make a backup of twrp and see if i can post results, thanks allot, iveen waiting to fix this for so many days now.
A bit of background, i consider myself an advance user, someone that can google problems and fix stuff with it, ivee flashed alot of cellphones in the past ,many xt1064 and other models, just like everybody ealse, easy and no problems, but this one i just cant figure out. Seems like its on read only mode or freezed as a deepfreezed computer, dont mater how many roms i flash and the way i do, everything comes back to the same state, even if i reforma partitions, eeven if i delete pictures or folders, they come back once i reboot.
Click to expand...
Click to collapse
ok ii'm thinking corrupted partitions too.... but if you are willing to try i've made a xt1063 easy installer script for you to try now normally i work on xt1068 and would test on my xt1068 - so have NO xt1063 its UNTESTED - use at own risk.....
just stock firmware / drivers / adb and mfastboot ( same as my xt1068 script) I see no reason it should not be compatible.
download to pc / unzip to folder / read instruction inside
https://mega.co.nz/#!Tok2DJ6T!ggMoQDfAzuA7cmQQjbGCbXolWZTnx_567vG02CiURVsxt1063 4.4.4 easy installer
I repeat it YOUR choice - if it works- great - if runs ok but rom remains same would suggest somethings corrupt - if it doesnt work at all back to square 1....
now im presuming your boot loader is unlocked, as will fail if locked or relocked - if you use and get error please report what they are, i would have done 5.0.2 but its only 50% downloaded with a 1 hr+ to still go, estimate 2 hrs from time of this post until I can post a link
im uploading the backup, in the mean time i dont know if this is of any use ,its the recovery log zipped...
abispac said:
im uploading the backup, in the mean time i dont know if this is of any use ,its the recovery log zipped...
Click to expand...
Click to collapse
just to let you know TWRP is now 2.5.8.0 fixes some bugs cause older versions know to break permissions in Lollipop!!
https://mega.co.nz/#!Dx03wTbD!3sDFubGomhegQqdoGzNb1RWnQwApzyaTlVq69uX1TqkFlash-able version (unzip to pc and flash from there) 2.5.8.0
https://mega.co.nz/#!n5cUQCAY!uf66vEcQlmtu6VZMLPxksEFMEioZUFpystzTP6kwU4I Temporary boot version (no flash) 2.5.8.0.
will look but cant promise
I tried your easy install tool, brand new drivers, diferent usb port, all went smooth but after restart, im at the same situation. Funny thing, and ivee done this multiple times, after reflashing a new rom, most of them never give errors, then after nothing happens , i flash twrp and boot it, and all the files (the original ones , not the just flashed ones) are there intact, even pictures and music.
abispac said:
I tried your easy install tool, brand new drivers, diferent usb port, all went smooth but after restart, im at the same situation. Funny thing, and ivee done this multiple times, after reflashing a new rom, most of them never give errors, then after nothing happens , i flash twrp and boot it, and all the files (the original ones , not the just flashed ones) are there intact, even pictures and music.
Click to expand...
Click to collapse
ok have you tried mfastboot erase userdata and mfastboot erase cache? from a command window?
i.m interested in the I flash twrp and boot..... does this mean you are able to replace recovery with a custom recovery ON phone
rather than temporary booting into it?
reefuge said:
ok have you tried mfastboot erase userdata and mfastboot erase cache? from a command window?
i.m interested in the I flash twrp and boot..... does this mean you are able to replace recovery with a custom recovery ON phone
rather than temporary booting into it?
Click to expand...
Click to collapse
Yeah i tried those erase commands many many times and same result, i cant replace recovery at all, only boot of it, so when i do " mfastbooot flash recovery twrprecovery.img " then try to boot of recovery, i boot into factory recovery not, twrp, but if i do, "mfasboot boot twrprecovery.img" i can see the recovery img gets flashed and the phone boots of twrp. Weird behavior. So when i notice that i tried to flash a rom with mfastboot, and at the end i gave the command mfasboot boot recovery.img (the original rom recovery) then it gets flashed, and phone reboots, but i gets stuck at the motorola logo. This phone its playing hard to get....
heres, my backup https://mega.co.nz/#!md0AwbLR!uWe9PLklIugOziPLV6O_plbU-Zz9EXbqRvUVpYxECk0 hope you can find something.
Im going to take this phone to a shop to see if they can fix it as i have lost all hope, thanks refuuge for your help.
How to flash Android M, TWRP, & SuperSU with out getting red corrupt triangle @ boot?
Is there a method to flash Android M with TWRP and supersu that will work with out giving the red triangle stating the device is corrupt at boot?
Thanks
I wonder the same thing. I tried to get rid of the red triange but it's impossible. I've tried a full wipe and flash everything from stock but no dice.
Also i'm unable to boot to recovery. It just freezes... Same thing if I flash back the 5.1.1 image. TWRP is working though.
Any ideas?
Does anyone have a solution to get rid of the triangle WITHOUT twrp or root? I flashed TWRP to see if I could install a custom HOSTS file and the message started popping up on boot, but even after reflashing everything from the official M image and wiping data and cache it still pops up. Any suggestions? o_o
Did you flash userdata too? Tried factory reset on top?
pszyman said:
Did you flash userdata too? Tried factory reset on top?
Click to expand...
Click to collapse
I formatted userdata because I have a 64GB device and the userdata image included is for 32GB. this is what I did without the file names because I'm mobile:
Code:
Fastboot flash bootloader mboot.img
Fastboot reboot-bootloader
Fastboot flash mradio.img
Fastboot flash system msystem.img
Fastboot flash boot mboot.img
Fastboot flash recovery mrecovery.img
Fastboot format userdata
Fastboot format cache
And then I booted and got the device corrupt message. I did all of that a few times to make sure I didn't miss anything and I have no idea what it's detecting as modified. I haven't tried factory resetting from the device itself, I figured formatting userdata would be enough but ill try that tomorrow unless anyone has other ideas.
I had this same issue today too after I flashed twrp. The only way to resolve it was to flash stock and unroot using nexus toolkit to a lollipop stock image. In time I'm sure it will be a smoother process to go to android m with twrp and root, but until then, I'm sticking with lollipop.
Sent from my Nexus 6 using Tapatalk
530farm said:
Is there a method to flash Android M with TWRP and supersu that will work with out giving the red triangle stating the device is corrupt at boot?
Thanks
Click to expand...
Click to collapse
Experienced this too, until I found this article that shows different TWRP, SuperSU, etc versions.
http://wccftech.com/root-nexus-6-android-60-mra58k-marshmallow/
I flashed it without the errors.
Hope it works for you. After a few minutes of Marshmallow I went back to Fusion 6.0 which was a bit more features based on CM12.1. I just got the Shamu yesterday coming from OnePlusOne running SultanXDA's CM CAF.
Well, the issue is this corrupted message stays even after the full stock reinstall. Some say it went away after the factory reset but returned back after a while later, after spontaneous reboot or so.
thanks the dispair kernel worked with twrp 2.8.7.1 and su 2.49 beta.
now i have no more corrupt and i am rooted and not encrypted
thanks
What I've done to get back to stock was - flash clean image and next factory reset. No corrupted message. So far so good.
I believe to get rid of it...you will have to lock and unlock bootloader again...which will factory reset in the process. Hopefully someone finds a workaround for a factory reset...I am going to continue to run it with the error message until someone does. I dont want to factory reset. The message doesnt cause any issues to my knowledge...its just a warning to the user.
dansoh said:
Experienced this too, until I found this article that shows different TWRP, SuperSU, etc versions.
http://wccftech.com/root-nexus-6-android-60-mra58k-marshmallow/
I flashed it without the errors.
Hope it works for you. After a few minutes of Marshmallow I went back to Fusion 6.0 which was a bit more features based on CM12.1. I just got the Shamu yesterday coming from OnePlusOne running SultanXDA's CM CAF.
Click to expand...
Click to collapse
kidhudi said:
thanks the dispair kernel worked with twrp 2.8.7.1 and su 2.49 beta.
now i have no more corrupt and i am rooted and not encrypted
thanks
Click to expand...
Click to collapse
I have confirmed this works. I had the "Device is Corrupt" message non-stop. Basically go to that link and download all the stuff.
Have TWRP install.
From TWRP install the Despair.R20.6.Shamu.zip
then flash BETA-SuperSU-v2.49.zip.
Reboot
PRESTO, Device Corrupt is GONE
I had tried Despair.M.CFS.R31.2.Shamu.UBER.zip and UPDATE-SuperSU-v2.46.zip before, which did not eliminate the Device is Corrupt Message
inspiron41 said:
I have confirmed this works. I had the "Device is Corrupt" message non-stop. Basically go to that link and download all the stuff.
Have TWRP install.
From TWRP install the Despair.R20.6.Shamu.zip
then flash BETA-SuperSU-v2.49.zip.
Reboot
PRESTO, Device Corrupt is GONE
I had tried Despair.M.CFS.R31.2.Shamu.UBER.zip and UPDATE-SuperSU-v2.46.zip before, which did not eliminate the Device is Corrupt Message
Click to expand...
Click to collapse
Which one makes the message go away though, the kernel or supersu? Or both? I wasn't looking to root my phone so at this point I'm just trying to get the message to go away lol
EDIT: Can confirm it's kernel related, just flashed a lollipop kernel and the message vanished but of course it bootlooped Lol.
I flashed the kernel from here http://forum.xda-developers.com/nexus-6/development/kernel-stock-kernel-root-color-control-t3218958 and it went away.
PhantomGamers said:
Which one makes the message go away though, the kernel or supersu? Or both? I wasn't looking to root my phone so at this point I'm just trying to get the message to go away lol
EDIT: Can confirm it's kernel related, just flashed a lollipop kernel and the message vanished but of course it bootlooped Lol.
Click to expand...
Click to collapse
Custom kernels that have the flag edited out will will get rid of the Corrupt message.
djkinetic said:
Custom kernels that have the flag edited out will will get rid of the Corrupt message.
Click to expand...
Click to collapse
I guess I'll have to resort to that if factory resetting doesn't fix it, sucks though cuz I would have been happy with stock.
Hey all,
So I posted what I did to **** everything up the other day: https://forum.xda-developers.com/ta...ie-tried-to-root-device-t3655848?goto=newpost
I read about 70 different forums posts and concluded (somehow) that i needed to try and flash "twrp_3.1.0" for my T810. Well, for some reason it worked. I now have twrp on my boot-looped device.
Now, I'm trying to install a different recommendation which is the "SuperSU-v2.76" ROM through dragging it onto my tablet via My Computer (Since Odin refuses to load it)
Guess what? Ran into another problem when doing this. My T810 will no longer connect with my PC. It is stating "Device driver software was not successfully installed"... throwing out an error message MTP USB Device Failed.
I came up with the wise idea to simply put the SuperSU file on my brand new 128gb micro SD card. I found a USB adaptor for the card, plugged it into my PC and now My Computer is stating that the Micro SD card only has 1.67mb of space available. Did a bunch of research and found out that the USB adaptor actually has a limitor pre programmed into it so that you cannot adapt large SD cards..
I'm striking out guys. I need help. I'm able to navigate the twrp menu.. is there an option on this screen that will help me? I cannot think of what needs to be done next to get this Tab working....
also
.... yes I have the Samsung USB driver installed for my particular device....
So I ended up running to the store and I bought a 16gb micro SD. It worked, I was able to run the SuperSU-v2.76 flash on my device. Geuss what happened next?
Bootloop again.
Currently trying another suggestion which calls for restoring the tablet to an original OEM flash. Going to try installing the "5.0.2_T810XXU1AOG6_T810XAR1AOG6_XAR" flash and ill post what happens........
NOPE! No good. twrp does not recognize booting MD5 files.... I'm stuck again.
dyrewolv said:
Click to expand...
Click to collapse
You need to flash this version of SuperSU.
http://download.chainfire.eu/1122/SuperSU/SR3-SuperSU-v2.82-SR3-20170813133244.zip
ashyx said:
You need to flash this version of SuperSU.
http://download.chainfire.eu/1122/SuperSU/SR3-SuperSU-v2.82-SR3-20170813133244.zip
Click to expand...
Click to collapse
Hey ashyx,
How does that version of SuperSU differ from the one I just tried to flash?
What causes the tab to bootloop in the first place?
Thanks for your help!!
dyrewolv said:
Hey ashyx,
How does that version of SuperSU differ from the one I just tried to flash?
What causes the tab to bootloop in the first place?
Thanks for your help!!
Click to expand...
Click to collapse
Difficult to explain, but it should prevent the bootloop.
Samsung and Google's updates can break root, so new patched versions need to be released to overcome the issue.
You should consult the Supersu beta thread for the changelog.
ashyx said:
Difficult to explain, but it should prevent the bootloop.
Samsung and Google's updates can break root, so new patched versions need to be released to overcome the issue.
You should consult the Supersu beta thread for the changelog.
Click to expand...
Click to collapse
gotcha. I'm 100% brand-new to rooting. After I get SuperSU rooted onto my tab... Can I proceed with installing other custom ROMs?
What's the standard procedure for rooting/flashing devices from one ROM to the next?
I must be ****ing up bad because the last (4) ROM's I've tried have all bootlooped.
I did notice that I forgot to enable developers options when my tab was still OEM.. haven't been able to boot into a menu to change it though
dyrewolv said:
gotcha. I'm 100% brand-new to rooting. After I get SuperSU rooted onto my tab... Can I proceed with installing other custom ROMs?
What's the standard procedure for rooting/flashing devices from one ROM to the next?
I must be ****ing up bad because the last (4) ROM's I've tried have all bootlooped.
I did notice that I forgot to enable developers options when my tab was still OEM.. haven't been able to boot into a menu to change it though
Click to expand...
Click to collapse
You don't need root to be able flash custom roms but you must enable OEM UNLOCK in developer settings or you will encounter FRP Lock and won't be able to boot until you flash the stock firmware.
You will also need to patch dm-verity before installing anything custom. SuperSU and Magisk already do this or you can can flash my boot patch which also disables forced encryption.
ashyx said:
You don't need root to be able flash custom roms but you must enable OEM UNLOCK in developer settings or you will encounter FRP Lock and won't be able to boot until you flash the stock firmware.
You will also need to patch dm-verity before installing anything custom. SuperSU and Magisk already do this or you can can flash my boot patch which also disables forced encryption.
Click to expand...
Click to collapse
I tried flashing stock firmware in Odin via the file "5.0.2_T810XXU1AOG6_T810XAR1AOG6_XAR" which I found on the stock firmware forum for the T810. Odin failed during the flash...
If I get SuperSU working can I enable OEM UNLOCK?
What is dm-verity?
dyrewolv said:
I tried flashing stock firmware in Odin via the file "5.0.2_T810XXU1AOG6_T810XAR1AOG6_XAR" which I found on the stock firmware forum for the T810. Odin failed during the flash...
If I get SuperSU working can I enable OEM UNLOCK?
What is dm-verity?
Click to expand...
Click to collapse
I suggest you flash the latest Marshmallow or Nougat update.
Dm-verity is a security mechanism.
http://updato.com/firmware-archive-select-model?q=Sm-t810&exact=1
ashyx said:
I suggest you flash the latest Marshmallow or Nougat update.
Dm-verity is a security mechanism.
http://updato.com/firmware-archive-select-model?q=Sm-t810&exact=1
Click to expand...
Click to collapse
I'm confused. So I should continue with trying to get the correct version of SuperSU flashed first..right? Then figure out what I need; Marshmallow or Nougat? I haven't even got the tablet to get past the Samsung logo, I cannot enable OEM Unlock.. Last night when I tried flashing stuff Odin did not want to cooperate. I get a "FAIL! Complete (Write) operation failed" message. Tried to flash the stock ROM file I listed below with both re-partition unchecked and checked with no success.
dyrewolv said:
I'm confused. So I should continue with trying to get the correct version of SuperSU flashed first..right? Then figure out what I need; Marshmallow or Nougat? I haven't even got the tablet to get past the Samsung logo, I cannot enable OEM Unlock.. Last night when I tried flashing stuff Odin did not want to cooperate. I get a "FAIL! Complete (Write) operation failed" message. Tried to flash the stock ROM file I listed below with both re-partition unchecked and checked with no success.
Click to expand...
Click to collapse
It probably fails because you can't downgrade.
It's up to you to whether to flash MM or NN.
You will need to update first and then flash twrp and then supersu.
Hi all - Australian here with Optus Note 9.
Got my Note9 this morning. Flashed twrp (from https://forum.xda-developers.com/ga...t/recovery-twrp-galaxy-note-9-exynos-t3833933). Flashed magisk from page 1 in same thread.
Now can't boot. Stuck on a black screen saying;
VERIFICATION FAILED
unable to restart your device. The ingerity verification has failed. You need to reset your device to factory default settings. This will erase your data
[ RESET].
Click on 'reset', it goes to twrp then loops around.
Anyone know how to fix?
Im with optus too. If you can get back into twrp just flash stock rom or a custom rom.
ciaox said:
Im with optus too. If you can get back into twrp just flash stock rom or a custom rom.
Click to expand...
Click to collapse
I just tried flashing a custom rom - stuck with it in boot loop.
So whilst I re-download the stock stuff, I tried deleting my data in twrp and I'm just about to try a no-verity-opt-encrypt6.zip with custom pie rom. Fingers crossed .
hmm strange. first boot takes a good 5mins tho. good luck
Worked fine.
Not sure whats changed, but I needed to flash the no-verity-ope-encrypt6.zip, and now it boots just fine.
Very strange. Oh well, onwards and upwards to Pie goodness (like my old Huawei mate10pro)
Mod feel free to close this one. ty
Toldorn said:
Worked fine.
Not sure whats changed, but I needed to flash the no-verity-ope-encrypt6.zip, and now it boots just fine.
Very strange. Oh well, onwards and upwards to Pie goodness (like my old Huawei mate10pro)
Click to expand...
Click to collapse
flashing magisk v16 and up would have also fixed it. but format data and factory wipe in twrp was a required step before flashing custom rom.
So i tried to root my phone and it happend. After i flashed A10 to phone (again) because my system stuck on bootloop after trying to again flash root. I booted to the system. The normal welcome screen appear, instead of complete it, i decided to go to the recovery and wipe phone again. I dont know why i did it, but i did and now the phone is stuck on bootloop. I tried many things but when i try to even flash system again without root, it stucks on logo. One boot takes time about 2,3 minutes, at the end almost black screen appears (almost because its little shining, it looks like LCD black) for 3sec then everything goes again until battery drain out. From this i can normally boot to any custom or stock recovery. It happend like 3weeks ago and phone is still on bootloop. Please help. Im on TWRP 3.2.3-1_ashyx and i cant find any newer for this phone model, there isnt any orangefox recovery too. I dont know what to do, i tried everything i can like ADB, no success, odin, no success, apps that repair system, also no success. I dont know Im a moron or something but if you can help, tell me everything step by step. Im on bootloader 8.
here is the TWRP i use
Download and flash latest stock firmware for your country via Odin:
Download Samsung Galaxy A6+ SM-A605F firmware
Download the latest Samsung firmware for Galaxy A6+ with model code SM-A605F. Check out our free download or super fast premium options.
www.sammobile.com
Then use this TWRP version for easy flashing custom roms or Magisk (root):
[RECOVERY][UNOFFICAL][LINK FIXED] TWRP 3.5.0 for Samsung Galaxy A6+ 2018
Team Win Recovery Project 3.5.0 Special Notes: 1. DON'T FORGET TO ENABLE "OEM UNLOCK" (located in Developers options). 2. KNOX will be tripped once you flashed custom binaries to your phone. (Your warranty may be voided. However this may not...
forum.xda-developers.com
However you don't need TWRP if you need only root. Instructions here:
Installation
The Magic Mask for Android
topjohnwu.github.io
When i flash latest stock rom im still in bootloop, I also have problem with flashing that TWRP because odin just errors with Complete (write) operation Failed. Re-flashing system doesnt work. I tried everything, even re-partition. I cant use ADB, also I cant do TOTAL re-install of system because my TWRP is too old and i cant delete Vendor partition, only from TWRP 3.4.0 or higher i can do that, also that old TWRP is buggy,
MDN2137 said:
When i flash latest stock rom im still in bootloop
Click to expand...
Click to collapse
How did you do that? Just putted AP, BL, CP and CSC (not HOME_CSC) in Odin and flashed?
nqnxev said:
How did you do that? Just putted AP, BL, CP and CSC (not HOME_CSC) in Odin and flashed?
Click to expand...
Click to collapse
Im not that stupid . I putted AP fle in AP slot like everything else, i also used CSC not Home CSC.
nqnxev said:
How did you do that? Just putted AP, BL, CP and CSC (not HOME_CSC) in Odin and flashed?
Click to expand...
Click to collapse
Im 100% sure i putted everything in right slot
If you have working properly TWRP at the moment, then just flash newer version TWRP from current TWRP (get IMG file and flash as "Recovery" (choose "Recovery" partition for flashing) and reboot).
MDN2137 said:
and i cant delete Vendor partition
Click to expand...
Click to collapse
Why would you do that? Don't mess with partitions ifself without reason. Just try to update TWRP and then wipe partitions: cache, dalvik, data. You can then try also flashing GSI. Follow instructions from this thread. Maybe it will help.
well... the phone is still stuck on bootloop, but i updated the TWRP thanks to you, but before i had to wipe several partitions to do that, because without that i had error with that SEANDROID bla bla bla, it just means i propably installed wrong recovery or system. I dont know what to do i tried everything i know and Im out of ideas. Please help, this phone is trying to kill me, i want to throw this phone from scycraper and i think this is the best idea.
I think that phone is bricked really hard, like a real brick, but maybe there is still some chance.
The same situation after flashing GSI? Also bootloop?
I dont know how to flash GSI on latest Android10 update
MDN2137 said:
I dont know how to flash GSI on latest Android10 update
Click to expand...
Click to collapse
Instructions here.
Well...... it worked! Thanks.