HELP!
My S7 Edge keeps getting into recovery mode and gets blocked from the FAP lock.
I screwed my phone.
I can only get into download mode but i don't know what to do to reset it or solve this damn issue.
HELP PLEASE!!!
This is why fapping is bad guys.
Give this a try OP http://www.androidpolice.com/2015/1...msung-phones-due-to-a-flaw-in-their-software/
Dameon87 said:
This is why fapping is bad guys.
Give this a try OP http://www.androidpolice.com/2015/1...msung-phones-due-to-a-flaw-in-their-software/
Click to expand...
Click to collapse
I thank you for the suggestion.
However i cannot get into recovery (otherwise it would be easy), only in download mode
On the splash screen it just says RECOVERY IS NOT SEANDROID ENFORICING and then the phone turns off.
I can get into download mode but i can't do anything else...
Rareba said:
I thank you for the suggestion.
However i cannot get into recovery (otherwise it would be easy), only in download mode
On the splash screen it just says RECOVERY IS NOT SEANDROID ENFORICING and then the phone turns off.
I can get into download mode but i can't do anything else...
Click to expand...
Click to collapse
I found this post...
http://forum.xda-developers.com/s7-edge/help/fap-lock-booy-help-t3396334
Maybe i can just flash one of the stock firmwares with ODIN and at least boot the phone, and disable the OEM option in the developer settings?
That may work. Sorry I don't have much experience on the matter. Disabling frp was probably the first thing I did to give me peace of mind. Give it a try!
Dameon87 said:
That may work. Sorry I don't have much experience on the matter. Disabling frp was probably the first thing I did to give me peace of mind. Give it a try!
Click to expand...
Click to collapse
Solved by Flashing a stock rom.
This video is a good example: https://www.youtube.com/watch?v=9qAX1xTRAGg
Rareba said:
Solved by Flashing a stock rom.
This video is a good example: https://www.youtube.com/watch?v=9qAX1xTRAGg
Click to expand...
Click to collapse
Glad to hear you got it fixed.
Dameon87 said:
Glad to hear you got it fixed.
Click to expand...
Click to collapse
Now the problem is that TWRP is installed but not working properly
Gotta fix that as well!
Happened to me a few weeks back. Download and flash stock with Odin, boot, put in your Google account details when asked (phone won't work without it), go into dev options and make sure OEM Unlock is selected. You're now good to go again to flash TWRP with Odin again.
Beefheart said:
Happened to me a few weeks back. Download and flash stock with Odin, boot, put in your Google account details when asked (phone won't work without it), go into dev options and make sure OEM Unlock is selected. You're now good to go again to flash TWRP with Odin again.
Click to expand...
Click to collapse
That's what i did!
However TWRP for some reason is installed but, aside of the fact that always asks about being read only or not every boot, i can't access any storage
Must be some weird permissions stuff!
Rareba said:
That's what i did!
However TWRP for some reason is installed but, aside of the fact that always asks about being read only or not every boot, i can't access any storage
Must be some weird permissions stuff!
Click to expand...
Click to collapse
Try searching over the forum, follow (ALL) the instructions on this post to get TWRP working properly. (All data will be lost so you'd better make a backup).
Rareba said:
That's what i did!
However TWRP for some reason is installed but, aside of the fact that always asks about being read only or not every boot, i can't access any storage
Must be some weird permissions stuff!
Click to expand...
Click to collapse
It's because, when you install stock back, the phone will be encrypted again. TWRP can't read Samsung encryption. In TWRP you will need to formate (not wipe) the data partition. As said above, you will lose everything.
Related
I tried to unroot my phone via OCLF from the market. It went dark, then got the normal Vibrant screen, the the Galaxy S screen, then it went dark again. Now, it just sits. Black screen. All the buttons at the bottom are lit up. :-/
Anyone?
Silly question, I know. But did you have a nandroid backup, by any chance?
This is probably a last resort, but try boot into recovery and wipe everything. This fix the problem for me, the downside is you lose all you data.
Sent from my SGH-T959 using XDA App
If you are anything like me, recovery didn't work and using Odin and reflashing Stock with repartition didn't work either.
You'll need to use odin to flash Eugenes "Vibrant that doesn't brick" (NO REPARTITION), then use odin again to flash Stock (check repartition this time) and you'll be good to go.
You can try to flash the froyo rom with odin...... I had that same exact problem and this is what fixed it for me. Once froyo us flashed then you can flash whatever rom you want. Hth
Ok, I probably should have stated that I'm a complete newby and have no idea what I'm doing. I believe I do have nandroid, but other than that you all are speaking French to me.
Right now I'm in the recover mode (I think). It's hooked up to my computer and I'm in the "Downloading... Do not turn off target!!" mode. This is where I'm stuck...I have no idea where to go from here.
Please talk to me like I'm a 5 year old, because as far as this is concerned, I am!
Oh, and thank you so much for any help you can give me!
hospo said:
Ok, I probably should have stated that I'm a complete newby and have no idea what I'm doing. I believe I do have nandroid, but other than that you all are speaking French to me.
Right now I'm in the recover mode (I think). It's hooked up to my computer and I'm in the "Downloading... Do not turn off target!!" mode. This is where I'm stuck...I have no idea where to go from here.
Please talk to me like I'm a 5 year old, because as far as this is concerned, I am!
Oh, and thank you so much for any help you can give me!
Click to expand...
Click to collapse
Well, good news is... you didn't brick your phone, this is recoverable. Best idea would be to search the forums on how to ODIN back to Stock. Theres plenty of posts on how to do it. You should also be able to find this in the tips & tricks threads. Good Luck.
Thank you all for your help! I recovered it!! Seems as though I was just going about it the wrong way!! I got into the actual recovery mode and cleared it all out. Now it's as good as new!
Again, appreciate your help and patience with what I'm sure is the 120,000th post on this subject. ;-)
Kienz said:
Silly question, I know. But did you have a nandroid backup, by any chance?
Click to expand...
Click to collapse
Is it even possible to make a nandroid backup before rooting?
hospo said:
Thank you all for your help! I recovered it!! Seems as though I was just going about it the wrong way!! I got into the actual recovery mode and cleared it all out. Now it's as good as new!
Again, appreciate your help and patience with what I'm sure is the 120,000th post on this subject. ;-)
Click to expand...
Click to collapse
Hey - what does you doing? Please told me, I've the same problem:
If I start the phone with an USB cable and the battery symbol with the running point under this, the PC recognize that something is connected, but Windows found no driver....
How could you could flash the Stackfirmware back, if the recovery and download menu does not work ?
PLS help !!!
Check out this thread http://forum.xda-developers.com/newreply.php?do=newreply&p=8129898
Go to the section where it says "Did You Flash Something Before Disabling Voodoo? 2 Fixes to Help You Out."
And do fix #1 it is pretty easy and it wont take you more than 20 minutes.
Let us know if that works
And do fix #1 it is pretty easy and it wont take you more than 20 minutes.
Let us know if that works
Click to expand...
Click to collapse
If I following the link and the next one, I can read:
Caution!!! You Must be on STOCK Vibrant Rom & NEVER Have Already Flashed the JP3 Froyo Image
Click to expand...
Click to collapse
It isn't -> it's a Firmware for the normal Galaxy (3key)[I'm a idiot]
First,
You must already Have Odin installed & Know how to boot into Down-loader Mode!!
Click to expand...
Click to collapse
Thats also the problem as described in front : I have had no chance to received the DL Mode.. maybe I make something wrong? The phone is booting up till the "S" is there, after that, the screen is black, keys are lightning...
The recovery 3button are blocked from the beginning; the DL Menu - I did not have reached it successfully
The PC recognize, that is something on USB, but not what ... so Odin did not see the Mobile, too.
Hey guys
So I just received my BRAND NEW S4 (i9505), and decided to root/flash it almost out of the box. (Smart, huh?)
I did exactly what CURSED4EVA mention in the 2 videos on youtube about rooting and flashing. The only difference is, when I need to hit REEBOT NOW (after doing the zip, wipes etc), it asks me: "ROM may flash stock recovery on boot. Fix?"
(It doesn't ask HIM that in that video) - Can't link to him, but search: "cursed4eva Galaxy S4 google edition" - and it is the first video about flashing
I tried clicking yes, tried no, tried "avoiding it", tried restore backup and tried all that in both CWM and TWRP.
All in all I end up with the Google colors just looping and looping. Even tried flashing StockDroids Rom, just to see if it was helping.. but no, same problem.
So now I have a brand new phone, DEAD :good:
Any suggestions on what I am doing wrong? It is a i9505 from Denmark.
And and, sorry if this has already been answered. Just coudnt find it anywhere..
Thanks a bunch!
saktown said:
Any suggestions on what I am doing wrong? It is a i9505 from Denmark.
Click to expand...
Click to collapse
I did the exact same thing and had the same problem! I eventually got it sorted, turned out I forgot to turn on USB Debugging mode before installing CF-Auto-Root. I got stuck at the Nexus loading screen.
I am pretty new to this but thought I would save you the headache, - head over to samersh72's post on unbricking [here], follow the instructions, and you should be just fine, though you'll lose your root and be back at your original stock firmware!
If you need any more help feel free to reply
supjackary said:
I did the exact same thing and had the same problem! I eventually got it sorted, turned out I forgot to turn on USB Debugging mode before installing CF-Auto-Root. I got stuck at the Nexus loading screen.
I am pretty new to this but thought I would save you the headache, - head over to samersh72's post on unbricking [here], follow the instructions, and you should be just fine, though you'll lose your root and be back at your original stock firmware!
If you need any more help feel free to reply
Click to expand...
Click to collapse
Dude, thanks man. Will have a look tonight. So basically follow the guide to get back to stock. And after, Awhen Cf auto rooting this time remember to turn on USB debugging mode, right?
Thanks again
well, went back to stock firmware with a perfectly fine phone.
remembered this time enable the usb debugging mode, but problem is still the same. Still stuck at the nexus boot colors.
When I hit reboot now in cwm, it first asks me:
"rom may flash stock recovery on boot. fix"
Then:
"root access possibly lost"
saktown said:
well, went back to stock firmware with a perfectly fine phone.
remembered this time enable the usb debugging mode, but problem is still the same. Still stuck at the nexus boot colors.
When I hit reboot now in cwm, it first asks me:
"rom may flash stock recovery on boot. fix"
Then:
"root access possibly lost"
Click to expand...
Click to collapse
ignore that and just boot, will be fine.
Hazerd said:
ignore that and just boot, will be fine.
Click to expand...
Click to collapse
Does not work tried hoosing "no" to both questions
Even if I choose "go back" it's just going to ask next question.
So do I choose "no" to both AFTER a fresh stock firmware install? Maybe try that?
saktown said:
Does not work tried hoosing "no" to both questions
Even if I choose "go back" it's just going to ask next question.
So do I choose "no" to both AFTER a fresh stock firmware install? Maybe try that?
Click to expand...
Click to collapse
if nothing worked, you prob have a different s4 variant. go back to stock couse it will prob not work.
Hazerd said:
if nothing worked, you prob have a different s4 variant. go back to stock couse it will prob not work.
Click to expand...
Click to collapse
Found this:
/showthread.php?t=2341026
Will see if I can pull it off tonight.
I tried putting in a rom earlier for my note 3 and it didn't take.
I ended up on that, vibration boot loop.
Odin still worked fine so I tried putting in an original stock rom with root, so I can add recovery.
I could not actually find a fully suitable rom choice, and the samsung website didn't play well with me either. firstly it would not let me register for some reason...anyway.
I am UK on O2 running 9005 SO I put in N9005XXUDMJ7-PRE-ROOTED-KNOX-FREE-ODEX-BL-FREE
I don't know if that was the right choice, I set it up on PDA, and unclicked partition
It's been stuck possibly hanging on ext4 sys for over an hour.
The references I have seen suggest it takes a long time but how long is too long?
I don't want to pull the plug to brick the device completely.
I have a cwm recovery so all I need is to put the recovery back in and I should be good to go...
If this is hanging, what other options do I have?
How long is too long?
Any help fixing this would be greatly appreciated, and a drinks on me...
I am kinda freaking out, have seen similar threads, but because the firmwares are so different they didn't really help..or perhaps I misread things...but nothing really covered not being able to load the recovery software itself
consider me lizard brain in freak out mode right now..
please reply promptly with something.
Can you still boot to cwm or download mode only?
hey_joe said:
Can you still boot to cwm or download mode only?
Click to expand...
Click to collapse
Odin mode only. But it's still hanging.And I am worried that if I pull it now it's going to brick it and not even give me access to ODIN.
8thsiner said:
Odin mode only. But it's still hanging.And I am worried that if I pull it now it's going to brick it and not even give me access to ODIN.
Click to expand...
Click to collapse
Over one hour is too long to flash something even a full stock rom. Something is wrong there.
So you're saying you have no access to an original stock rom of your phone? If there is a problem like this flashing, I would flash the stock rom first then just root and install cwm. The first thing you want to do is have a working phone then just do the other stuff after like rooting, etc..
If what you posted is your stock rom, then download here and flash through odin.
There's also a newer one which is MK2 which you can download here.
Either one is stock.
Downloading the mk 2 now to test
That sorted me out thank you very much.
If you got a pay9all or something let me know, drink on me
8thsiner said:
That sorted me out thank you very much.
If you got a pay9all or something let me know, drink on me
Click to expand...
Click to collapse
No problem. Don't have paypal though and it's not necessary.
Enjoy your phone.
8thsiner said:
That sorted me out thank you very much.
If you got a pay9all or something let me know, drink on me
Click to expand...
Click to collapse
Mate the reason you got into trouble was you weren't flashing a stock rom...
N9005XXUDMJ7-PRE-ROOTED-KNOX-FREE-ODEX-BL-FREE means it has been altered and is considered custom...
A stock rom has not been altered.
8thsiner said:
That sorted me out thank you very much.
If you got a pay9all or something let me know, drink on me
Click to expand...
Click to collapse
There are a lot of good people here that will help you. You don't need to give anything back. And be sure to ALWAYS have a NANDROID backup so that you can restore your phone if anything bad happens.
Forgot to activate OEM-Unlock for Root. Phone Bricked: "Custom binary blocked by FRP"
Hello,
today i rooted my J5 (SM-J500FN) via Odin and CF-Auto-Root.
Everyting went well but after the root i unticked OEM-Lock (please dont ask me why i did it) and restarted my phone and this nice screen greeted me: "Custom binary blocked by FRP. SECURE FAIL: KERNEL"
So I tried everything I found on the Web and found nothing really helpful. Then i tried flashing the recovery and reflashing CF-Auto-Root but both got blocked in the Download Mode with the message "FRP Block".
Please can someone help me, i really hope i dont have to reset my phone because my google authenticator is stored on it, and it would be a real pain to write to the support of every account i connected to reset my Security Options.
Thanks, Toby
P.S: when i flash the boot.img does it wipe my device?
Toby9 said:
Hello,
today i rooted my J5 (SM-J500FN) via Odin and CF-Auto-Root.
Everyting went well but after the root i unticked OEM-Lock (please dont ask me why i did it) and restarted my phone and this nice screen greeted me: "Custom binary blocked by FRP. SECURE FAIL: KERNEL"
So I tried everything I found on the Web and found a few things like flashing the recovery. I tried reflashing CF-Auto-Root but both got blocked in the Download Mode with the message "FRP Block".
Please can someone help me, i really hope i dont have to reset my phone because my google authenticator is stored on it, and it would be a real pain to write to the support of every account i connected to reset my Security Options.
Thanks, Toby
P.S: when i flash the boot.img does it wipe my device?
Click to expand...
Click to collapse
Just flash the stock firmware.
ashyx said:
Just flash the stock firmware.
Click to expand...
Click to collapse
Doesn't it reset my phone?
I saw a video about it but after he started the phone the device setup greeted him...
Toby9 said:
Doesn't it reset my phone?
I saw a video about it but after he started the phone the device setup greeted him...
Click to expand...
Click to collapse
It will reset it...
Try using Smart Switch from Samsung to backup you stuff and accounts. Maybe it will work. Using Smart Switch you can also easily reflash the latest Marshmallow firmware.
Amarius1 said:
It will reset it...
Try using Smart Switch from Samsung to backup you stuff and accounts. Maybe it will work. Using Smart Switch you can also easily reflash the latest Marshmallow firmware.
Click to expand...
Click to collapse
And if i only flash the boot.img which is inside the firmware archive? would that be "save" to try?
Toby9 said:
And if i only flash the boot.img which is inside the firmware archive? would that be "save" to try?
Click to expand...
Click to collapse
I don't know about that... Try asking someine more experienced.
I do know that even in Recovery mode the ROM locks you out and doesn't let you factory reset for example
Amarius1 said:
I don't know about that... Try asking someine more experienced.
I do know that even in Recovery mode the ROM locks you out and doesn't let you factory reset for example
Click to expand...
Click to collapse
Ok thank you I just went for the boot.img flash and it worked! puh im relieved
Now you know that it does not reset.
I will write a guide to finally get rid of this stupid FRP error once and for all!
Toby9 said:
Ok thank you I just went for the boot.img flash and it worked! puh im relieved
Now you know that it does not reset.
I will write a guide to finally get rid of this stupid FRP error once and for all!
Click to expand...
Click to collapse
Congrats! Had the sane problem last summer and I had to completely reset it...
(Btw why thank you? I didn"t do anything ???)
Toby9 said:
Ok thank you I just went for the boot.img flash and it worked! puh im relieved
Now you know that it does not reset.
I will write a guide to finally get rid of this stupid FRP error once and for all!
Click to expand...
Click to collapse
I did a guide in past: https://forum.xda-developers.com/showpost.php?p=68408932&postcount=65 . I'll add it to the new Q&A thread after I'll update that thread (when I'll have time).
Feel free to do a new guide.
Toby9 said:
Doesn't it reset my phone?
I saw a video about it but after he started the phone the device setup greeted him...
Click to expand...
Click to collapse
No it does not. You are not affecting the data partition.
This would only happen if you flashed the factory repair firmware.
Thank you all. Here is my Guide: https://forum.xda-developers.com/android/general/complete-guide-to-rid-custom-binary-t3541403
It is generally for all (Samsung) Smarphones as i believe that it wont be any different.
Amarius1 said:
Congrats! Had the sane problem last summer and I had to completely reset it...
(Btw why thank you? I didn"t do anything )
Click to expand...
Click to collapse
Im just glad it worked
Toby9 said:
Thank you all. Here is my Guide: https://forum.xda-developers.com/android/general/complete-guide-to-rid-custom-binary-t3541403
It is generally for all (Samsung) Smarphones as i believe that it wont be any different.
Im just glad it worked
Click to expand...
Click to collapse
Happy for you ^^
When activating the oem unlock you can install Twrp, kernel or custom rom without the activation of FRP security that is activated when you establish a security pattern in the device
When the binary is blocked by the FRP you must install the factory firmware, then enter the recovery and do a factory reset since the FRP prevents external access to the system and data as prevention
You will be prompted for the email and password of the previously used account
Demicro said:
When activating the oem unlock you can install Twrp, kernel or custom rom without the activation of FRP security that is activated when you establish a security pattern in the device
When the binary is blocked by the FRP you must install the factory firmware, then enter the recovery and do a factory reset since the FRP prevents external access to the system and data as prevention
You will be prompted for the email and password of the previously used account
Click to expand...
Click to collapse
You only need to enter your login details if you factory reset.
Flashing the stock firmware is enough to remove frp. No need to factory reset.
ashyx said:
You only need to enter your login details if you factory reset.
Flashing the stock firmware is enough to remove frp. No need to factory reset.
Click to expand...
Click to collapse
This problem I had several months ago, I did not remember well. You are right ?
custom binary blockby frp lock on samsung j510gn
ashyx said:
Just flash the stock firmware.
Click to expand...
Click to collapse
hi. i really need help with this. tried several times flashing stockrom using different versions of odin and trying out several firmwares. always result: FAIL. Its a company phone. I honestly didn't do anything with it. Went to bed, next day woke up with the phone off. when I turned it on, bam! custom binary message.
MoximuZ said:
hi. i really need help with this. tried several times flashing stockrom using different versions of odin and trying out several firmwares. always result: FAIL. Its a company phone. I honestly didn't do anything with it. Went to bed, next day woke up with the phone off. when I turned it on, bam! custom binary message.
Click to expand...
Click to collapse
Can you send the logs u get from odin? Also make sure u got the correct model of stock rom for ur device.
I also have frp lock om my phone. It will not boot past maim boot screen. I cannot install twrp due to cuatom binary blocked error. Adb doesnt recognkze my phone either. Odin does, i installed the stock firmware and still will not reboot. Any suggestions or thoughts?? I havent tried to turn oem yet via android studio. Currently in the middle of that. Please help
ndiddy88 said:
I also have frp lock om my phone. It will not boot past maim boot screen. I cannot install twrp due to cuatom binary blocked error. Adb doesnt recognkze my phone either. Odin does, i installed the stock firmware and still will not reboot. Any suggestions or thoughts?? I havent tried to turn oem yet via android studio. Currently in the middle of that. Please help
Click to expand...
Click to collapse
Which device? Don't you know your Google login details?
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?