Related
I have bootloader unlocked, I downloaded nougat 7.0 firmware and tried to update manually, everything installs normally, but at the time of calling it says that the system is corrupted.
I already tried to put the boot and recovery of the version 7.0, already tried to put of the old, but always of the same thing, only version that works is previousor, someone knows how to do?
luizflb said:
I have bootloader unlocked, I downloaded nougat 7.0 firmware and tried to update manually, everything installs normally, but at the time of calling it says that the system is corrupted.
I already tried to put the boot and recovery of the version 7.0, already tried to put of the old, but always of the same thing, only version that works is previousor, someone knows how to do?
Click to expand...
Click to collapse
Whats the link for the manual download, ill experiment with it when i can update
Sm0k3r83 said:
Whats the link for the manual download, ill experiment with it when i can update
Click to expand...
Click to collapse
i used this link: http://dlcdnet.asus.com/pub/ASUS/Ze...ser.zip?_ga=1.245707268.1656347377.1488140054
Finished the update, all went well. Was a little laggy at first, so i cleaned the cache. Then rooted. Everything seems to be fine for me
same issue here. I can't update both with trwp and stock recovery. Originally my zenfone 3 was TIM SKU. Should be that the reason?
Hai.... someone could help me, I need recovery.image for asus ze520kl
zulfikarbugis said:
Hai.... someone could help me, I need recovery.image for asus ze520kl
Click to expand...
Click to collapse
mega.nz/#F!ok0V0RIA!5WKtHe98opzjVI3NPbM7Ww
Nobody knows a solution? I have tried to change the reocvery and the boot to the nougat version, and install the firmware manually, everything installs normally without errors, but when it connects it appears the following message "your device software can not be checked for corruption, Please lock the bootloader".
The cell phone is just that and I have to go back to the previous version!
I already took root, xposed and everything, and it always gives the same thing!
luizflb said:
Nobody knows a solution? I have tried to change the reocvery and the boot to the nougat version, and install the firmware manually, everything installs normally without errors, but when it connects it appears the following message "your device software can not be checked for corruption, Please lock the bootloader".
The cell phone is just that and I have to go back to the previous version!
I already took root, xposed and everything, and it always gives the same thing!
Click to expand...
Click to collapse
Same issue here =(
luizflb said:
Nobody knows a solution? I have tried to change the reocvery and the boot to the nougat version, and install the firmware manually, everything installs normally without errors, but when it connects it appears the following message "your device software can not be checked for corruption, Please lock the bootloader".
The cell phone is just that and I have to go back to the previous version!
I already took root, xposed and everything, and it always gives the same thing!
Click to expand...
Click to collapse
Updating thru TWRP results in an Error 7.
mxdxl said:
Updating thru TWRP results in an Error 7.
Click to expand...
Click to collapse
You did not understand, I installed the original recovery, both the last version of 6.0 and the version of 7.0, all install the update without error, but when it goes online does not work and I have to go back to the previous version
Raw firmware
I have the same issue. My phone was branded "tim italy". When i bought it, I flashed the WW version via asus flash tool, and I'm currently able to update till the last M version, which is the ......152.
If i try to update to Android N, my phone will not boot, giving me the corruption message and shutting down after 10 seconds. I also tried to perform the dm restore procedure; the dm error disappeared but the system is stuck on the Asus boot screen
I believe that the only solution is to flash a Nougat RAW firmware via asus Flash tool. Does Anyone have a download link for the N version ?
I have the same problem .. is there who can help?
`same problem can't update to nougat but my error is signature verification
hope someone can help us both
---------- Post added at 11:00 AM ---------- Previous post was at 10:48 AM ----------
Sm0k3r83 said:
Finished the update, all went well. Was a little laggy at first, so i cleaned the cache. Then rooted. Everything seems to be fine for me
Click to expand...
Click to collapse
Did you unlocked before updating?
same problem here....i downloaded the update and put it in internal storage...it automatically detected system update but when i try to update it it failed during installation....anyone help pls
mxdxl said:
Updating thru TWRP results in an Error 7.
Click to expand...
Click to collapse
if you want to update with twrp you must modify the update-script file placed in
UL-ASUS_Z012D-WW-14.2015.1701.8-user/META-INF/com/google/android
i have uploaded my one, if you can't modify the file you can download it and replace it in zip file
ExperienceTesla said:
if you want to update with twrp you must modify the update-script file placed in
UL-ASUS_Z012D-WW-14.2015.1701.8-user/META-INF/com/google/android
i have uploaded my one, if you can't modify the file you can download it and replace it in zip file
Click to expand...
Click to collapse
This works well? I have unlocked the bootloader and root my device. if this works for it?
zulfikarbugis said:
This works well? I have unlocked the bootloader and root my device. if this works for it?
Click to expand...
Click to collapse
The solution to the picture is Flash through the course
JadeKubPom said:
The solution to the picture is Flash through the course
Click to expand...
Click to collapse
I've done this but still fails. My phone will not boot, giving me the corruption message and shutting down after 10 seconds.
zulfikarbugis said:
I've done this but still fails. My phone will not boot, giving me the corruption message and shutting down after 10 seconds.
Click to expand...
Click to collapse
mine does the same even with the right update-script.
When i try to update using stock recovery i get failed signature message
My friend has p8 lite and he cant relock and unlock.
The device says "phone unlocked" but we cant install twrp.
How can we fix ıt ? ?
kadirc5 said:
My friend has p8 lite and he cant relock and unlock.
The device says "phone unlocked" but we cant install twrp.
How can we fix ıt ? ?
Click to expand...
Click to collapse
You need to tell more details. What kind of error it's showing when you try to install TWRP?
keikari said:
You need to tell more details. What kind of error it's showing when you try to install TWRP?
Click to expand...
Click to collapse
Always shows FAİLED
kadirc5 said:
Always shows FAİLED
Click to expand...
Click to collapse
That's a bit too little still. But if you believe you are doing everything correct and the TWRP file isn't corrupted then there's one thing that you could try. Though if it works I have no idea why.
When installing use auto-complete when typing the TWRP file name into flash command. (Type few first letters and then press tab)
This helped one guy earlier who I believe had same problem.
[TA-1053] Official OTA 8.1 - Stuck at Recovery with "No command" warning after update
Hey guys,
I received the official update for Android 8.1 on my Nokia 5 TA-1053. I had no root, no Custom Recovery and bootloader locked.
During the update, as usual, the phone rebooted, and I got a error waring "No command". The waring is in recovery mode and I can access recovery options like "updtade from ADB, SD Card. Tried uptading with Android 8.0, but after reboot, still get the same error.
Does anyone have any clue?
Erkyem said:
Hey guys,
I received the official update for Android 8.1 on my Nokia 5 TA-1053. I had no root, no Custom Recovery and bootloader locked.
During the update, as usual, the phone rebooted, and I got a error waring "No command". The waring is in recovery mode and I can access recovery options like "updtade from ADB, SD Card. Tried uptading with Android 8.0, but after reboot, still get the same error.
Does anyone have any clue?
Click to expand...
Click to collapse
That happened to me too, I had to rollback to 7.1 flashing December update and flashing OST before I was able to use my phone again.
If you haven't yet recovered your phone, I uploaded April and May OTAs here:
https://forum.xda-developers.com/showpost.php?p=76513215&postcount=61
If that doesn't work, you will have to do what I did to get my phone up and running
Hi, and thanks.
I spent the night, without any success, trying to downgrade, using this https://forum.xda-developers.com/nokia-5/how-to/guide-how-to-downgrade-official-oreo-to-t3746007.
The OST flashing the nb0 but always fails with error "BATTERY_VOLTAGE_TOO_LOW_FAIL (0xA24B)". I Tried many, many times. If I sideload the OTA through adb (OTA is around 1.7 GB) it will fail at around 47%. Error message on ADB: "adb: failed to read command: No error". Error on phone: "Warning: no" and cannot read anymore. Then it goes to the little android screen with the no command warning, again.
Tried unlock bootloader now, without success. Maybe I need the full OTA for 8.1, but I'm not able to find it.
Erkyem said:
Hi, and thanks.
I spent the night, without any success, trying to downgrade, using this https://forum.xda-developers.com/nokia-5/how-to/guide-how-to-downgrade-official-oreo-to-t3746007.
The OST flashing the nb0 but always fails with error "BATTERY_VOLTAGE_TOO_LOW_FAIL (0xA24B)". I Tried many, many times. If I sideload the OTA through adb (OTA is around 1.7 GB) it will fail at around 47%. Error message on ADB: "adb: failed to read command: No error". Error on phone: "Warning: no" and cannot read anymore. Then it goes to the little android screen with the no command warning, again.
Tried unlock bootloader now, without success. Maybe I need the full OTA for 8.1, but I'm not able to find it.
Click to expand...
Click to collapse
Did you try the OTAs I listed?
If they didn't work, try to flash one of the OTAs here:
https://forum.xda-developers.com/nokia-5/development/ota-nokia-5-ta-1053-monthly-ota-zip-t3655123
They are much smaller. Then you can try flashing OST
BTW I hope you didn't try flashing any of the nb0 files from the mega link in the post you mentioned. None of them are Nokia5 nb0s
If you don't have one, you can try the one in this link:
https://drive.google.com/file/d/0B60NFIDB93wudDNXaG5vMkEyWVE/view
redweaver said:
That happened to me too, I had to rollback to 7.1 flashing December update and flashing OST before I was able to use my phone again.
If you haven't yet recovered your phone, I uploaded April and May OTAs here:
https://forum.xda-developers.com/showpost.php?p=76513215&postcount=61
If that doesn't work, you will have to do what I did to get my phone up and running
Click to expand...
Click to collapse
Please, what did you do? Flashing Dec Update then using an nb0 file with OST, it got stuck at "Connection Failed, 0xc6da" Error; do you have any idea of what I should do?
K1r1k4z3 said:
Please, what did you do? Flashing Dec Update then using an nb0 file with OST, it got stuck at "Connection Failed, 0xc6da" Error; do you have any idea of what I should do?
Click to expand...
Click to collapse
You got this error when flashing the nb0?
redweaver said:
You got this error when flashing the nb0?
Click to expand...
Click to collapse
Yes, I did. I have no idea what it means.
K1r1k4z3 said:
Yes, I did. I have no idea what it means.
Click to expand...
Click to collapse
How many times did you try again?
redweaver said:
How many times did you try again?
Click to expand...
Click to collapse
Severally.
Meanwhile, the OST tool won't run on my Windows 10 PC. I get this error. Is there something I'm missing if you've run this tool on Windows 10 before. Meanwhile I'm at PH.
K1r1k4z3 said:
Severally.
Meanwhile, the OST tool won't run on my Windows 10 PC. I get this error. Is there something I'm missing if you've run this tool on Windows 10 before. Meanwhile I'm at PH.
Click to expand...
Click to collapse
I don't like Windows 10. My lappy comes with Win 8.1. I had to dual boot win 7 just to run OST
redweaver said:
I don't like Windows 10. My lappy comes with Win 8.1. I had to dual boot win 7 just to run OST
Click to expand...
Click to collapse
Could you help me with the specific nb0 file you used in flashing yours.
K1r1k4z3 said:
Could you help me with the specific nb0 file you used in flashing yours.
Click to expand...
Click to collapse
I got it from one of those links
https://mega.nz/#!HoNX1CBT!AORGMLndzcbc5iOBrJlLlLKyncZ5hImJirnPApRGj_s
redweaver said:
I got it from one of those links
https://mega.nz/#!HoNX1CBT!AORGMLndzcbc5iOBrJlLlLKyncZ5hImJirnPApRGj_s
Click to expand...
Click to collapse
I'm kinda confused; what's the difference between "ND1-3320-0-00WW-A02.nb0" and "ND1-3700-0-00WW-B03.nb0"
Cos I'm flashing this "ND1-3320-0-00WW-A02.nb0 with the OST right now and it's still stuck at "Reflash Service Bootloader" for over 20mins now. Is this normal?
K1r1k4z3 said:
I'm kinda confused; what's the difference between "ND1-3320-0-00WW-A02.nb0" and "ND1-3700-0-00WW-B03.nb0"
Cos I'm flashing this "ND1-3320-0-00WW-A02.nb0 with the OST right now and it's still stuck at "Reflash Service Bootloader" for over 20mins now. Is this normal?
Click to expand...
Click to collapse
I honestly have no idea. Wait for it to finish or give an error, otherwise you risk bricking your phone for good. Did you "downgrade" to nougat before flashing?
FINALLY! I got my Nokia 5 working like new.
Thanks @redbeaver! You've got no idea, but you helped alot!
redweaver said:
I honestly have no idea. Wait for it to finish or give an error, otherwise you risk bricking your phone for good. Did you "downgrade" to nougat before flashing?
Click to expand...
Click to collapse
I sent you a PM sir, please attend to it.
Jack_Sparrow_Thats_Very_Interesting.gif
I've come into possession of a device with something displaying in Download mode that I've never seen before - on any Samsung device. All of the threads that I've found on rooting or BL unlocking have been closed. Is there anyone still around who knows enough to help me reverse engineer this? @Acoustichayes @BotsOne @elliwigy
iBowToAndroid said:
Jack_Sparrow_Thats_Very_Interesting.gif
I've come into possession of a device with something displaying in Download mode that I've never seen before - on any Samsung device. All of the threads that I've found on rooting or BL unlocking have been closed. Is there anyone still around who knows enough to help me reverse engineer this? @[email protected]@elliwigy
Click to expand...
Click to collapse
just saw ur message lol.. if u dont mind me asking, whered u get it from lol..
either way, you have an S8 with eng mode enabled. Typically on newer phones there are eng certs or "tokens" that can be flashed to the device enabling eng mode and allowing custom firmware.. the certs are pretty much impossible to find unless ur in good with samsung or pay a good amount of money for..
to my knowledge, they are device specific also. meaning no way to pull the cert/token to use on other devices..
i could be wrong but based on @partcyborg coming across a similar eng mode that is what i have learned lol
elliwigy said:
just saw ur message lol.. if u dont mind me asking, whered u get it from lol..
either way, you have an S8 with eng mode enabled. Typically on newer phones there are eng certs or "tokens" that can be flashed to the device enabling eng mode and allowing custom firmware.. the certs are pretty much impossible to find unless ur in good with samsung or pay a good amount of money for..
to my knowledge, they are device specific also. meaning no way to pull the cert/token to use on other devices..
i could be wrong but based on @partcyborg coming across a similar eng mode that is what i have learned lol
Click to expand...
Click to collapse
It's cert based? Damn. Thought maybe it was another bootloader partition that isn't in the BL Odin tar. I didn't think the cert carried anything other than the IMEI. But I guess that's a foolproof way to do it, since it's coded according to the CPID. And no, they can't be read from the device. Guess we're stuck...
iBowToAndroid said:
It's cert based? Damn. Thought maybe it was another bootloader partition that isn't in the BL Odin tar. I didn't think the cert carried anything other than the IMEI. But I guess that's a foolproof way to do it, since it's coded according to the CPID. And no, they can't be read from the device. Guess we're stuck...
Click to expand...
Click to collapse
pm me,would like to chat on hangouts or tgram n check afew things to be sure
Sent from my SM-G965U using Tapatalk
iBowToAndroid said:
It's cert based? Damn. Thought maybe it was another bootloader partition that isn't in the BL Odin tar. I didn't think the cert carried anything other than the IMEI. But I guess that's a foolproof way to do it, since it's coded according to the CPID. And no, they can't be read from the device. Guess we're stuck...
Click to expand...
Click to collapse
elliwigy said:
pm me,would like to chat on hangouts or tgram n check afew things to be sure
Sent from my SM-G965U using Tapatalk
Click to expand...
Click to collapse
Whoa whoa whoa guys.
I want in You know I know a bit about the certs lol having bricked and restored mine several times lol:silly::silly::silly:
TheMadScientist said:
Whoa whoa whoa guys.
I want in You know I know a bit about the certs lol having bricked and restored mine several times lol:silly::silly::silly:
Click to expand...
Click to collapse
I don't have it anymore
iBowToAndroid said:
I don't have it anymore
Click to expand...
Click to collapse
You know it sucks too I know several people with s8 or 9 maybe even a note 8 or 9 with Eng certs and unlocked bootloader on Snapgragon U model Makes me jealous
Wish we could find a way to copy or something with em
TheMadScientist said:
Whoa whoa whoa guys.
I want in You know I know a bit about the certs lol having bricked and restored mine several times lol:silly::silly::silly:
Click to expand...
Click to collapse
Hello guys,
I own a SM-N960F ENG MODE: DEV DEVICE which is in "custom binary blocked by frp lock". I have tried to flash all sorts of firmware including the latest stock version CSDE to no avail. ODIN passes it successfully but when it tries to reboot it goes again into "custom binary blocked by frp lock"
Hope you might shed some light...
besmirgogu said:
Hello guys,
I own a SM-N960F ENG MODE: DEV DEVICE which is in "custom binary blocked by frp lock". I have tried to flash all sorts of firmware including the latest stock version CSDE to no avail. ODIN passes it successfully but when it tries to reboot it goes again into "custom binary blocked by frp lock"
Hope you might shed some light...
Click to expand...
Click to collapse
It sounds like the binary being referred to is a partition that is not touched by a standard firmware flash. Have you tried flashing the Combination/Factory firmware?
Ive seen guys mention the error but I've never seen it so I'm not sure. Sounds like it's frp locked so i would search on a way to bypass frp on your device. They've changed a bit and i haven't read up on the newer devices really yet I'm not ready to upgrade
iBowToAndroid said:
It sounds like the binary being referred to is a partition that is not touched by a standard firmware flash. Have you tried flashing the Combination/Factory firmware?
Click to expand...
Click to collapse
iBowToAndroid, thank you for replying. I tried this specific combination through AP section of ODIN:COMBINATION_FAC_FA81_N960FXXU2ARK4.rar. ODIN flashed successfully but phone is in continuous boot loop stating "Boot Image Signature Check Fail!!!. Reboot to avoid warranty bit set!!!" Combination ARK4 is based on Oreo 8.1 meanwhile device had stock Pie 9.
What do you mean exactly when you say Combination/Factory Firmware if you don't mind...
besmirgogu said:
iBowToAndroid, thank you for replying. I tried this specific combination through AP section of ODIN:COMBINATION_FAC_FA81_N960FXXU2ARK4.rar. ODIN flashed successfully but phone is in continuous boot loop stating "Boot Image Signature Check Fail!!!. Reboot to avoid warranty bit set!!!" Combination ARK4 is based on Oreo 8.1 meanwhile device had stock Pie 9.
What do you mean exactly when you say Combination/Factory Firmware if you don't mind...
Click to expand...
Click to collapse
5th digit back is your bootloader number you are flashing a older boot loader than what's on your device
TheMadScientist said:
Ive seen guys mention the error but I've never seen it so I'm not sure. Sounds like it's frp locked so i would search on a way to bypass frp on your device. They've changed a bit and i haven't read up on the newer devices really yet I'm not ready to upgrade
Click to expand...
Click to collapse
No, it's not actually FRP locked. It just means that the FRP security is enabled. If he did a factory reset from the Recovery menu, then yes, it would actually be "locked". But he has specifically stated that his device is bootlooping - so how would he do a bypass anyways...?
TheMadScientist said:
5th digit back is your bootloader number you are flashing a older boot loader than what's on your device
Click to expand...
Click to collapse
Huh? Dude, that makes no sense. First of all, he stated that it flashed successfully. And regardless, the newest bootloader for his model is 2. So it's impossible for his device to have anything newer.
besmirgogu said:
iBowToAndroid, thank you for replying. I tried this specific combination through AP section of ODIN:COMBINATION_FAC_FA81_N960FXXU2ARK4.rar. ODIN flashed successfully but phone is in continuous boot loop stating "Boot Image Signature Check Fail!!!. Reboot to avoid warranty bit set!!!" Combination ARK4 is based on Oreo 8.1 meanwhile device had stock Pie 9.
What do you mean exactly when you say Combination/Factory Firmware if you don't mind...
Click to expand...
Click to collapse
That is exactly what I meant - a Combination firmware. It sounds like whatever changes were made to put it into "Eng mode" prevent it from accepting a stock retail device flash - or at least prevent it from booting on that firmware. Sounds like you might need to look into obtaining a different device
Hello, I just came across a S8 International G950FD phone with this option on Download screen. Not sure if it is worth anything to anyone before I use it. I wonder what this mode means on a Exynos Samsung, because these already allow the bootloader to be unlocked. Anyone know? I could see the G950U utilizing this because the bootloader is locked on the US phones, but unsure what this would benefit on a International model G950FD. Maybe it just means that this S8 does not have RMM or KG State to be prenormal? Like ever maybe, even if I factory reset.
I know this is a bit late, but I have a US note 20 ultra that also says this on the download screen. I recieved the phone about 3 months before the note 20 actually came out.
I was just trying to install the 9.0.6 update manually following the instructions in the thread for it here on xda and it wouldn't work. I uninstalled magisk and restored images through magisk manager as the directions stated to do. I couldn't get the update to show in the local upgrade section under system update so decided to reboot to see if that would fix it but now my phone will not boot. It goes to a screen that says my device is corrupt and won't go past that. It says to hit the power button to continue but that just makes it boot back to that screen and if I just wait the phone shuts off.
Any help is appreciated.
(UPDATE) Thanks for the help guys. I got the phone booting again by flashing the 9.0.6 ROM in fastboot. I'm still getting the "device is corrupt" message and have to hit the power button twice to get it to boot so if anyone knows a fix for this I would appreciate it. At least I can use the phone now.
imucarmen said:
I was just trying to install the 9.0.6 update manually following the instructions in the thread for it here on xda and it wouldn't work. I uninstalled magisk and restored images through magisk manager as the directions stated to do. I couldn't get the update to show in the local upgrade section under system update so decided to reboot to see if that would fix it but now my phone will not boot. It goes to a screen that says my device is corrupt and won't go past that. It says to hit the power button to continue but that just makes it boot back to that screen and if I just wait the phone shuts off.
Any help is appreciated.
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-6t/how-to/tool-t-mobile-oneplus-6t-msmdownloadtool-t3868916
Worked for me. Unzip to a folder....run it.....with phone off press and hold all 3 buttons......it will find device.... press start.....Yahtzee....hope this helped
imucarmen said:
I was just trying to install the 9.0.6 update manually following the instructions in the thread for it here on xda and it wouldn't work. I uninstalled magisk and restored images through magisk manager as the directions stated to do. I couldn't get the update to show in the local upgrade section under system update so decided to reboot to see if that would fix it but now my phone will not boot. It goes to a screen that says my device is corrupt and won't go past that. It says to hit the power button to continue but that just makes it boot back to that screen and if I just wait the phone shuts off.
Any help is appreciated.
Click to expand...
Click to collapse
Are you able to boot into fastboot?
mang0 said:
Are you able to boot into fastboot?
Click to expand...
Click to collapse
Yes.
mang0 said:
Are you able to boot into fastboot?
Click to expand...
Click to collapse
Mine wouldn't boot into anything....said hardware/software mismatch.
headcreepz said:
https://forum.xda-developers.com/oneplus-6t/how-to/tool-t-mobile-oneplus-6t-msmdownloadtool-t3868916
Worked for me. Unzip to a folder....run it.....with phone off press and hold all 3 buttons......it will find device.... press start.....Yahtzee....hope this helped
Click to expand...
Click to collapse
That says it's for the T Mobile version only. I have the global version.
imucarmen said:
That says it's for the T Mobile version only. I have the global version.
Click to expand...
Click to collapse
Shoot...sorry
There is one on here for international.....look in guides
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
imucarmen said:
Yes.
Click to expand...
Click to collapse
You could try to use msm download tool linked above or flash the full rom again since you can get into fastboot. I'd prob try that before the msm tool though.
mang0 said:
You could try to use msm download tool linked above or flash the full rom again since you can get into fastboot. I'd prob try that before the msm tool though.
Click to expand...
Click to collapse
do you have any instructions on how to go about flashing a rom in fastboot? I've never done it before.
imucarmen said:
do you have any instructions on how to go about flashing a rom in fastboot? I've never done it before.
Click to expand...
Click to collapse
Check this link
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
imucarmen said:
do you have any instructions on how to go about flashing a rom in fastboot? I've never done it before.
Click to expand...
Click to collapse
Just download full zip of fastboot rom, extract into a folder, connect you phone in fastbbot mode and run flash all bat file.
You can find all in this thread:
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
VampireHeart said:
Just download full zip of fastboot rom, extract into a folder, connect you phone in fastbbot mode and run flash all bat file.
You can find all in this thread:
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
Click to expand...
Click to collapse
Thanks. I got that part and was able to get my phone booting again but I still get the corrupt device message when I start the phone. Wish I knew how to get rid of it. IS there any return to full stock methods that also locked the bootloader and restore all partitions to stock? That is the only thing I can think of that might work.
imucarmen said:
Thanks. I got that part and was able to get my phone booting again but I still get the corrupt device message when I start the phone. Wish I knew how to get rid of it. IS there any return to full stock methods that also locked the bootloader and restore all partitions to stock? That is the only thing I can think of that might work.
Click to expand...
Click to collapse
Someone say that wiping all with stock recovery solved, but device work fine also whit that message, otherwise you can try MSM Download Tool, it will restore all stock to 9.0.5 with locked bootloader.
imucarmen said:
Thanks. I got that part and was able to get my phone booting again but I still get the corrupt device message when I start the phone. Wish I knew how to get rid of it. IS there any return to full stock methods that also locked the bootloader and restore all partitions to stock? That is the only thing I can think of that might work.
Click to expand...
Click to collapse
Use the MSMDownloadTool for the international version, it's the only way to bypass the verity trigger, it will restore the device to full stock as if you never unlocked the bootloader to begin with.
VampireHeart said:
Someone say that wiping all with stock recovery solved, but device work fine also whit that message, otherwise you can try MSM Download Tool, it will restore all stock to 9.0.5 with locked bootloader.
Click to expand...
Click to collapse
Dark Nightmare said:
Use the MSMDownloadTool for the international version, it's the only way to bypass the verity trigger, it will restore the device to full stock as if you never unlocked the bootloader to begin with.
Click to expand...
Click to collapse
Thanks guys. I will try this out in the future. For now I'm just going to ride with what I got since I don't feel like setting my phone up again. I don't reboot much so it shouldn't bother me too bad. I guess it's good I learned something new.
Dark Nightmare said:
Use the MSMDownloadTool for the international version, it's the only way to bypass the verity trigger, it will restore the device to full stock as if you never unlocked the bootloader to begin with.
Click to expand...
Click to collapse
Can you provide me a link? The only MSMDownloadTool I see says it's only for the T-Mobile version. Thanks.
imucarmen said:
Can you provide me a link? The only MSMDownloadTool I see says it's only for the T-Mobile version. Thanks.
Click to expand...
Click to collapse
Msm download tool for int : https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
Just paste this in terminal and device is corrupt message will be gone
su
Reboot "dm-verity enforcing"
Hit enter
Enjoy
[email protected] said:
Just paste this in terminal and device is corrupt message will be gone
su
Reboot "dm-verity enforcing"
Hit enter
Enjoy
Click to expand...
Click to collapse
Yep this should do the trick. It worked for me!
[email protected] said:
Just paste this in terminal and device is corrupt message will be gone
su
Reboot "dm-verity enforcing"
Hit enter
Enjoy
Click to expand...
Click to collapse
I keep getting this error and I typing it wrong?