So to take the ota. I am rooted and safestrapped with 3 slots open. To take ota I must enable root survival install stock recovery and Odin the new update correct? Thanks for the help
EDIT: FIGURED IT OUT
Sent from my SM-N900V using xda app-developers app
XzxBATTxzX said:
So to take the ota. I am rooted and safestrapped with 3 slots open. To take ota I must enable root survival install stock recovery and Odin the new update correct? Thanks for the help
EDIT: FIGURED IT OUT
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
How bout a step by step for those like me not familiar with odin, how to install stock recovery (MJ7 tar?)... I'm beginning to miss my UNLOCKED Gnex (flash rom, gapps, kernel, profit) with this learning curve using safestrap, odin, slots, ota, re-root...
Some details would be REALLY appreciated, thx
az_biker said:
How bout a step by step for those like me not familiar with odin, how to install stock recovery (MJ7 tar?)... I'm beginning to miss my UNLOCKED Gnex (flash rom, gapps, kernel, profit) with this learning curve using safestrap, odin, slots, ota, re-root...
Some details would be REALLY appreciated, thx
Click to expand...
Click to collapse
I have not tried this method yet, i will try tomorrow when i have time. I take no credit for any threads linked in this process. I am simply laying out the process i will be trying out for any others that would like to try. I like to start with a clean slate for a major system update like this so this method will wipe data and start you out with a fresh. You WILL have to reroot and reinstall Safestrap.
I take no responsibility for this messing up your phone if you try it, again, this is my OPINION only and the method i will try.
Backup your data thats important on the phones internal memory to the MicroSD or PC and then -
1. Boot into factory recovery by turning phone off, then booting up by holding the Power, Home, and Volume Up buttons simultaneously until you see "Recovery Booting" in blue on the top left corner of the screen. Then release the buttons.
2. Once stock recovery has booted, wipe data and cache from here. I usually just pull the battery after this since its the easiest way to power the device off after a wipe in factory recovery.
3. Boot the device up by holding Power, Home, and Volume Down simultaneously until the phone prompts you too press either Volume Up for Download mode, or Volume Down for reboot. Press Volume Up to go into Download Mode(Odin Mode).
4. Once the phone goes into Download Mode(Odin Mode) go to this link and follow this process to flash back to Factory MJ7. This will wipe your internal memory, which is why i suggested backing anything on it up FIRST.
http://forum.xda-developers.com/showthread.php?t=2483380
5. After the flash in Odin is complete and you have booted into MJ7 take the OTA through the normal means in About Phone.
6. Once the update has completed use Kingo to root just like before (remember sometimes it just takes a few times to work right, if it fails try it a few times before you get discouraged) when you rooted MJ7. It is reported by a users to have worked in this thread.
http://forum.xda-developers.com/showthread.php?t=2565693
Instructions
az_biker said:
How bout a step by step for those like me not familiar with odin, how to install stock recovery (MJ7 tar?)... I'm beginning to miss my UNLOCKED Gnex (flash rom, gapps, kernel, profit) with this learning curve using safestrap, odin, slots, ota, re-root...
Some details would be REALLY appreciated, thx
Click to expand...
Click to collapse
as far as help if you are currently rooted safestrapped and running a custom rom, you should visit the return to stock/ recover from soft brick thread and that will get you back to stock verizon firmware, then buy supersu pro, enable root survival, then take the ota an renable supersu. If root does not get preserved kingo root works with mje too. Sorry for the late reply
willjohnson said:
I have not tried this method yet, i will try tomorrow when i have time. I take no credit for any threads linked in this process. I am simply laying out the process i will be trying out for any others that would like to try. I like to start with a clean slate for a major system update like this so this method will wipe data and start you out with a fresh. You WILL have to reroot and reinstall Safestrap.
I take no responsibility for this messing up your phone if you try it, again, this is my OPINION only and the method i will try.
Backup your data thats important on the phones internal memory to the MicroSD or PC and then -
1. Boot into factory recovery by turning phone off, then booting up by holding the Power, Home, and Volume Up buttons simultaneously until you see "Recovery Booting" in blue on the top left corner of the screen. Then release the buttons.
2. Once stock recovery has booted, wipe data and cache from here. I usually just pull the battery after this since its the easiest way to power the device off after a wipe in factory recovery.
3. Boot the device up by holding Power, Home, and Volume Down simultaneously until the phone prompts you too press either Volume Up for Download mode, or Volume Down for reboot. Press Volume Up to go into Download Mode(Odin Mode).
4. Once the phone goes into Download Mode(Odin Mode) go to this link and follow this process to flash back to Factory MJ7. This will wipe your internal memory, which is why i suggested backing anything on it up FIRST.
http://forum.xda-developers.com/showthread.php?t=2483380
5. After the flash in Odin is complete and you have booted into MJ7 take the OTA through the normal means in About Phone.
6. Once the update has completed use Kingo to root just like before (remember sometimes it just takes a few times to work right, if it fails try it a few times before you get discouraged) when you rooted MJ7. It is reported by a users to have worked in this thread.
http://forum.xda-developers.com/showthread.php?t=2565693
Click to expand...
Click to collapse
I used this process tonight and can confirm that it worked for me, Running Clean ROM 1.5.
Related
Hi all, I'm new here (great place, very informative) and pretty new to the Android scene in general.
As the title said, My AT&T S4 won't boot to recovery after I flashed 4.3 JWR663. Worked fine before and 4.3 is working great, but I can't get to TWRP. When I hold "power + volume up" I get the blue text dialog indicating its going to boot to recovery and the phone just shuts off. I can boot to download mode, but haven't done anything out of fear. I'm not rooted (which is what I'd like to do once this is fixed).
Should I try and re-flash TWRP? Any other suggestions? Feel free to break it down like you're talking to a child. Thanks in advance.
Try flashing it. Get goomanager from the play store. Open it and hit the menu button. Hit install openrecoveryscript.
Sent from my SGH-I337 using xda premium
graydiggy said:
Try flashing it. Get goomanager from the play store. Open it and hit the menu button. Hit install openrecoveryscript.
Sent from my SGH-I337 using xda premium
Click to expand...
Click to collapse
Will that work without root?
Vikingod said:
Will that work without root?
Click to expand...
Click to collapse
You'll need root to flash a recovery with GooManager.
How did you install 4.3? I assume that it's a custom 4.3 as I don't think it has been officially released yet. If it's custom, I'd assume that the ROM had been rooted as well...
theSpam said:
You'll need root to flash a recovery with GooManager.
How did you install 4.3? I assume that it's a custom 4.3 as I don't think it has been officially released yet. If it's custom, I'd assume that the ROM had been rooted as well...
Click to expand...
Click to collapse
I was rooted, but the ROM had it removed and I need to flash Chainfire to get it back. But I can't get into recovery to do so. I think the ROM was done by Jah0n
Is it safe to flash TWRP with Odin now? If so, could you point me to the directions to help me do so. Thanks again for the help.
Found a fix!
My recovery is fine. All I did was power down, try to boot into recovery with "power + volume up + home" and just when the phone vibrated to boot into recovery, I let go of the power button but continued holding the other buttons. It booted into TWRP just fine.
Vikingod said:
Found a fix!
My recovery is fine. All I did was power down, try to boot into recovery with "power + volume up + home" and just when the phone vibrated to boot into recovery, I let go of the power button but continued holding the other buttons. It booted into TWRP just fine.
Click to expand...
Click to collapse
Yep, that's the way you're supposed to get into recovery.
I an able to get in with only power+vol up. Both work for me.
Sent from my SGH-I337 using xda premium
Vikingod said:
Hi all, I'm new here (great place, very informative) and pretty new to the Android scene in general.
As the title said, My AT&T S4 won't boot to recovery after I flashed 4.3 JWR663. Worked fine before and 4.3 is working great, but I can't get to TWRP. When I hold "power + volume up" I get the blue text dialog indicating its going to boot to recovery and the phone just shuts off. I can boot to download mode, but haven't done anything out of fear. I'm not rooted (which is what I'd like to do once this is fixed).
Should I try and re-flash TWRP? Any other suggestions? Feel free to break it down like you're talking to a child. Thanks in advance.
Click to expand...
Click to collapse
Did you try manually booting into recovery with the power and volume button?
quattros said:
Did you try manually booting into recovery with the power and volume button?
Click to expand...
Click to collapse
He fixed his problem a few posts ago...
Sent from my SGH-I337 using xda premium
I have an older phone and after flashing the twrp recovery it won't let me boot into recovery mode at all can someone please give some advice on how I should fix this?
Which phone do you have?
An Alcatel One touch POP D3 4037A
Try using the Alcatel mobile tool to flash back to stock.
TWRP doesn't work
My LG G3 running lineage os 14.1 won't boot into TWRP.
graydiggy said:
He fixed his problem a few posts ago...
Sent from my SGH-I337 using xda premium
Click to expand...
Click to collapse
The blue and black screen start up screen comes up. But it stays like this. This happened since I flashed the lineage ROM. What should I do?
my phone agua rio 4.4.2 kitkat .
After flashing twrp recovery img .
After rebooting it .twrp not installed and it only reboot normal i didnt get to twrp recovery
Need solution pls pls
This thread is about the Samsung Galaxy s4.
Hi there. I'm new of this forum and even of the Android customization scenario. I have a Samsung Galaxy s4 i-9505 with 5.0.1 firmware and build LRX22C.I9505XXUHPK2. I've tried to install TWRP with Odin3 (so without root my phone) and all the procedure goes well. After reboot, I have turned-off my phone and I've tried to enter in the TWRP's recovery mode (using the combo buttons: VolumeUP + Home button + Power button) but the "TEAMWIN" logo didn't appear and the normal "Android Recovery Menu" were visualized.
I need some help to undestand if I did some mistakes during the flashing process. I've used the last versione of TWRP (3.1.1-0 for jfltexx). Any help will be appreciated. Thanks for your attention to this matter.
If you want to root with TWRP, try this for the gt-i9505:
open Odin 3.07 and uncheck everything except r reset time;
download the tar version of twrp for the gt-i9505: https://dl.twrp.me/jfltexx/
download the latest version of supersu.zip and copy it to an sd card or the phone's internal storage: http://www.supersu.com/download;
place the sd card in the phone if twrp has been saved to the sd card from the step above;
connect the phone in download mode and flash twrp in Odin's PDA slot;
when you see the word "reset" in the status window, remove USB cable from the phone, remove battery, replace battery, boot into recovery, install supersu.zip, reboot.
If you just want to install a custom ROM, copy the ROM to the internal or external sd card, install twrp, and install the ROM. Root is not required to install a custom ROM, only a custom recovery.
Warning: whenever you flash anything to a phone, it is always possible for something to go wrong and you must be prepared to deal with any consequences. I have used this method for several note 2, note 3, s3, and s4 phones without any issues. With this being said, I can't guarantee that the above steps will work for your phone or your phone won't be bricked.
I rooted my Note3 when an exploit first became available using RootDeLaVega. I haven't touched it since as I was waiting for the custom ROMs to roll out. I'm ready for Beans, but I want to be sure I'm going from rooted stock(no OTA's taken)...to upgraded Baseband(currently on M19)...to safestrap...to Beans.
Correct me if I'm wrong, but from what I've read I must do the following:
1. Use method 2 here: http://forum.xda-developers.com/showthread.php?t=2528707
2. Use Kingo to get root again.
3. Install safestrap: http://forum.xda-developers.com/showthread.php?t=2528707
Use Beta or Stable here?
4. Download and flash Beans to an open slot after making a backup.
I miss anything? Thanks.
cooch said:
I rooted my Note3 when an exploit first became available using RootDeLaVega. I haven't touched it since as I was waiting for the custom ROMs to roll out. I'm ready for Beans, but I want to be sure I'm going from rooted stock(no OTA's taken)...to upgraded Baseband(currently on M19)...to safestrap...to Beans.
Correct me if I'm wrong, but from what I've read I must do the following:
1. Use method 2 here: http://forum.xda-developers.com/showthread.php?t=2528707
2. Use Kingo to get root again.
3. Install safestrap: http://forum.xda-developers.com/showthread.php?t=2528707
Use Beta or Stable here?
4. Download and flash Beans to an open slot after making a backup.
I miss anything? Thanks.
Click to expand...
Click to collapse
1. Use method 2 only,download ODIN 3.09 and MJE Firmware Full Stock ROM 1.3 GB, Boot into Stock Recovery using Vol Up+Home+Power Button, Wipe Factory Reset/Data & Wipe Cache Partition, Reboot the device, as soon as screen goes black press Vol Down+Home Button to enter Download mode and connect the device to PC...then flash the MJE firmware...
2. After flashing boot again into Stock Recovery using Vol Up+Home+Power Button, Wipe Factory Reset/Data & Wipe Cache Partition
3. Use Kingo to root the device and make sure that Screen Display time is set to 10 Minutes..because u have to accept some confirmation while Kingo is rooting the device.
4. Install Safestrap 3.65 no problems till now...
5. Go into safestrap and go into Wipe then do Factory Data reset then advance wipe ( System, data, Internal Storage, cache , dalvik cache) then flash Beans ROM
6. Done.
Thank you for the detailed steps. I'll try it tonight.
cooch said:
Thank you for the detailed steps. I'll try it tonight.
Click to expand...
Click to collapse
Did you have any problems? I'm in the exact same situation.
I'm also curious about why we have to flash the odin image first. Is that for new radios? I'm already rooted, why not install SS and go from there?
cooch said:
I rooted my Note3 when an exploit first became available using RootDeLaVega. I haven't touched it since as I was waiting for the custom ROMs to roll out. I'm ready for Beans, but I want to be sure I'm going from rooted stock(no OTA's taken)...to upgraded Baseband(currently on M19)...to safestrap...to Beans.
Correct me if I'm wrong, but from what I've read I must do the following:
1. Use method 2 here: http://forum.xda-developers.com/showthread.php?t=2528707
2. Use Kingo to get root again.
3. Install safestrap: http://forum.xda-developers.com/showthread.php?t=2528707
Use Beta or Stable here?
4. Download and flash Beans to an open slot after making a backup.
I miss anything? Thanks.
Click to expand...
Click to collapse
I have a full on step by step, very detailed instruction for all the processes you need to take on your N3, check the link in my sig.
---------- Post added at 12:24 PM ---------- Previous post was at 12:19 PM ----------
dclutter1 said:
Did you have any problems? I'm in the exact same situation.
I'm also curious about why we have to flash the odin image first. Is that for new radios? I'm already rooted, why not install SS and go from there?
Click to expand...
Click to collapse
You only need to flash in Odin if you are on previous software (MI9, MJ7) in stead of current MJE. Flashing MJE in Odin installs latest modem, kernel and OS software updates. YOu'sd have issues running a MJE based Rom on a device with MJ7 or MI9 firmware...
If you're on MJE and rooted, start with the installation of Safestrap (custom recovery work around) on link in my sig. Everything is right there...
Yeah I read your thread, it looks great. Thanks for putting that together. And, thanks for the clarification.
Sent from my SM-N900V using Tapatalk
I have a Samsung Google Nexus 10 (Wi-Fi) GT-P8110HAAPHE Which was running Android 4.4.3 (I think but it is definitely the latest version) and I simply wished to root it.
I started following a video on Youtube and now I am stuck at what I think is called the Fastboot mode where My options are to scroll through START/RECOVERY MODE/RESTART BOOTLOADER/POWER OFF. I was using the Wugs Nexus Root Toolkit v1.8.3.
No matter which I select it returns me to the screen with the START option. When I select POWER OFF it does indeed power off but when I switch it on again it returns to the fastboot mode START option. I can get into download mode if that helps.
I did create a backup but cannot restore it.
I have done some research and downloaded the Android SDK Suite and fastboot/ADB and drivers etc ready to try and recover but I don't know where to start.
I have a Samsung Galaxy S3 which I have rooted and installed a number of different ROMS on so I am familiar with rooting but not sure if I can use Odin or something similar.
I think I have included all the information I have and hope someon can assist.
Thanks.
matrixmainframe said:
I have a Samsung Google Nexus 10 (Wi-Fi) GT-P8110HAAPHE Which was running Android 4.4.3 (I think but it is definitely the latest version) and I simply wished to root it.
I started following a video on Youtube and now I am stuck at what I think is called the Fastboot mode where My options are to scroll through START/RECOVERY MODE/RESTART BOOTLOADER/POWER OFF. I was using the Wugs Nexus Root Toolkit v1.8.3.
No matter which I select it returns me to the screen with the START option. When I select POWER OFF it does indeed power off but when I switch it on again it returns to the fastboot mode START option. I can get into download mode if that helps.
I did create a backup but cannot restore it.
I have done some research and downloaded the Android SDK Suite and fastboot/ADB and drivers etc ready to try and recover but I don't know where to start.
I have a Samsung Galaxy S3 which I have rooted and installed a number of different ROMS on so I am familiar with rooting but not sure if I can use Odin or something similar.
I think I have included all the information I have and hope someon can assist.
Thanks.
Click to expand...
Click to collapse
This is why I tell people not to use toolkits. Since everything is automated, it's hard to tell what went wrong and where. When it comes to Nexus devices, toolkits are entirely unnecessary IMO. These Nexus devices are so super simple to flash manually it's ridiculous. /END RANT
Okay. Sorry about that. Now, back to the issue at hand. The menu you are describing is, in fact, the Bootloader (aka Fastboot mode). Prior to using the NRT, were you completely stock? Was your bootloader already unlocked? To me, it sounds like you may have wiped your OS. Have you tried flashing the 4.4.3 factory image?
I was completely stock. Whilst using NRT I believe I had just succeeded in unlocking the Bootloader and the video then stated that with 4.4.3 a Factory reset was required which is what I did but I did not realise that deleted the O2. I thought that was on a protected partition like my S3 phone.
I can't flash the factory image as I can't get into recovery or is there another way of doing it?
I suppose where tablets are concerned I'm a book but if you could point me to any instructions on how to flash manually I'm hoping I can recover my tablet. Thanks.
Sent from my GT-I9300 using Tapatalk
Sorry, predictive text is rubbish. O2 should read OS and last paragraph I'm a book should read I'm a noob
Sent from my GT-I9300 using Tapatalk
matrixmainframe said:
I was completely stock. Whilst using NRT I believe I had just succeeded in unlocking the Bootloader and the video then stated that with 4.4.3 a Factory reset was required which is what I did but I did not realise that deleted the O2. I thought that was on a protected partition like my S3 phone.
I can't flash the factory image as I can't get into recovery or is there another way of doing it?
I suppose where tablets are concerned I'm a book but if you could point me to any instructions on how to flash manually I'm hoping I can recover my tablet. Thanks.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Dont know how you got your os erased. But im using a custom recovery since I got mine so maybe the stock recovery erses the os when doing a factory reset. A factory image cant be flashed via recovery and must be flashed via fastboot. Its really easy. But it will wipe the entire device. If you dont want to wipe everything you need to edit it..
Sent from my Galaxy Nexus using XDA Free mobile app
Cannot access Recovery Mode. Can Access Download Mode!
mrgnex said:
Dont know how you got your os erased. But im using a custom recovery since I got mine so maybe the stock recovery erses the os when doing a factory reset. A factory image cant be flashed via recovery and must be flashed via fastboot. Its really easy. But it will wipe the entire device. If you dont want to wipe everything you need to edit it..
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
I don't mind wiping the device but I cannot access Recovery Mode. When I select RECOVERY MODE and press the Power button to take me there it just returns me to the START screen.
I don't know if the fiollowing is relevent but it displays the word START vertically in the top left of the screen and next to it
Device Information
Product Name: manta
Variant: wifi
H/W Version: 8
Bottloader Version: MANTAMF01
Carrier Info: None
Serial Number: Don't think I should show that
Lock State: Unlocked
Reboot Mode Flag: None.
I have tried RESTART BOOTLOADER and that brings me back to the Start screen but still cannot access RECOVERY MODE.
Holding down the Power Button and Volume Up/Down brings me back to the Start screen again
I can get into DOWNLOAD MODE
Is there ANY way I can flash anything onto my Nexus 10 without using RECOVERY MODE like using Odin or Heimdall with a Samsung phone?
SORTED
Great news everyone..........well for me that is :laugh:
Thanks to Androidbeat.com I now have a fully operational Nexus 10.
Just in case anyone else was following this I did it by downloading all the necessary files into on folder on my Windows Desktop, opening a Command Prompt from there and followed the instructions.
Thank you to those who offered advice here and although my Nexus 10 is showing itself to be unlocked I think I'll give a miss to rooting it and just suffer the limitations rather than risk bricking it again.
matrixmainframe said:
Great news everyone..........well for me that is :laugh:
Thanks to Androidbeat.com I now have a fully operational Nexus 10.
Just in case anyone else was following this I did it by downloading all the necessary files into on folder on my Windows Desktop, opening a Command Prompt from there and followed the instructions.
Thank you to those who offered advice here and although my Nexus 10 is showing itself to be unlocked I think I'll give a miss to rooting it and just suffer the limitations rather than risk bricking it again.
Click to expand...
Click to collapse
Glad everything worked out for you. Just an FYI for future reference, the stock recovery factory reset does not wipe the OS (at least it shouldn't). By default, AFAIK there are no custom recoveries that will wipe your OS either while doing a factory reset. It must've been something with the toolkit.
Regarding root, it's super easy to get root on this device. All you have to do is download the custom recovery image file of your choice. I prefer Philz, but you can use CWM or TWRP as well. Then, download the latest SuperSU zip file (I believe it's v1.99r4 now). Simply fastboot flash the recovery image, boot into recovery, and install the SuperSU zip, and you're good to go. The whole process takes two minutes, and no toolkit required.
charesa39 said:
Glad everything worked out for you. Just an FYI for future reference, the stock recovery factory reset does not wipe the OS (at least it shouldn't). By default, AFAIK there are no custom recoveries that will wipe your OS either while doing a factory reset. It must've been something with the toolkit.
Regarding root, it's super easy to get root on this device. All you have to do is download the custom recovery image file of your choice. I prefer Philz, but you can use CWM or TWRP as well. Then, download the latest SuperSU zip file (I believe it's v1.99r4 now). Simply fastboot flash the recovery image, boot into recovery, and install the SuperSU zip, and you're good to go. The whole process takes two minutes, and no toolkit required.
Click to expand...
Click to collapse
charesa39 thanks for that. All done so thanks again.
Here is how you fix it.
Step 1. download OnePlus3t toolkit (note: don't attach the phone to PC yet)
step 2. reboot your phone into bootloader (if in twrp hit restart -> bootloader) if not in twrp try turning phone on and as you see the oem unlock screen hit volume up and down and choose fastboot (or bootloader)
step 3. open oneplus3t toolkit
step 4. choose option 8 (flash stock recovery)
step 5. hit enter and when it says waiting 4 devices attach your device to pc
step 6. let it finish
step 7. when recovery comes up, hold power button for 10 seconds or hit exit (if you can choose it) and reboot into system
step 8. if it keeps rebooting into a stock recovery and you cant decrypt... then when your phone first boots and goes into oem-unlock error hit volume up and click restart.
step 9. Reflash TWRP and SuperSU if needed
Step 10. Enjoy!
Did not work for me. Stock recovery, stock nougat, locked bootloader and I still have dm-verity error.
Skwerl23 said:
Here is how you fix it.
Step 1. download OnePlus3t toolkit (note: don't attach the phone to PC yet)
step 2. reboot your phone into bootloader (if in twrp hit restart -> bootloader) if not in twrp try turning phone on and as you see the oem unlock screen hit volume up and down and choose fastboot (or bootloader)
step 3. open oneplus3t toolkit
step 4. choose option 8 (flash stock recovery)
step 5. hit enter and when it says waiting 4 devices attach your device to pc
step 6. let it finish
step 7. when recovery comes up, hold power button for 10 seconds or hit exit (if you can choose it) and reboot into system
step 8. if it keeps rebooting into a stock recovery and you cant decrypt... then when your phone first boots and goes into oem-unlock error hit volume up and click restart.
step 9. enjoy!
Click to expand...
Click to collapse
Can TWRP be installed afterwards or will it come back when TWRP is installed?
Michalko5896 said:
Did not work for me. Stock recovery, stock nougat, locked bootloader and I still have dm-verity error.
Click to expand...
Click to collapse
Try flashing TWRP and back to stock recovery.
If all keeps happening you may need to follow the guide to unbrick the phone.
I'd personally keep flashing different things if data is important. Sorry to hear this happened. Sounds like dm-verity should never have been a thing. So frustrating. Please update us on what you find. You can always erase system and all then reflash image.
Skwerl23 said:
Try flashing TWRP and back to stock recovery.
If all keeps happening you may need to follow the guide to unbrick the phone.
I'd personally keep flashing different things if data is important. Sorry to hear this happened. Sounds like dm-verity should never have been a thing. So frustrating. Please update us on what you find. You can always erase system and all then reflash image.
Click to expand...
Click to collapse
I have tried everything. DM-verity error every fricking time.. Tbh, I really hate oneplus. They are not releasing factory images, with factory images I could fix every issue in 5 minutes.
I feel your frustration. There is this forum
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Michalko5896 said:
I have tried everything. DM-verity error every fricking time.. Tbh, I really hate oneplus. They are not releasing factory images, with factory images I could fix every issue in 5 minutes.
Click to expand...
Click to collapse
Go to TWRP>Wipe>Advanced Wipe>Select system>Repair or change file system>Change filesystem>EXT4>Flash your ROM
That fixed it for me
Michalko5896 said:
I have tried everything. DM-verity error every fricking time.. Tbh, I really hate oneplus. They are not releasing factory images, with factory images I could fix every issue in 5 minutes.
Click to expand...
Click to collapse
I used the hard brick fix to go back to 3.5.1? I let the system update to 3.5.4. Go into developer settings and check allow oem unlock. Went into bootloader and oem unlocked. It will erase everything. Downloaded and put the OTA patch(940gb~not full) and supersu 2.79 on the device somewhere and did a local update with the patch through stock recovery. Went into bootloader and flashed TWRP 3.0.2.0(not 3.0.3.0). Do not exit bootloader. In bootloader I fastboot BOOT the 3.0.2.0 TWRP(3.0.3.0 would not boot up and screwed the dm-verity). If it(3.0.2.0) doesn't want to boot then quickly hold the power button in and wait till it starts rebooting and go into recovery menu option). Swipe to allow modifications and flash the supersu 2.79 that was placed on the device somewhere. This worked for me and no dm-verity error with f2fs.
Long process but it worked.
does dm-verity error mean anything? I have it also currently but nougat seems to be running fine...
PaKii94 said:
does dm-verity error mean anything? I have it also currently but nougat seems to be running fine...
Click to expand...
Click to collapse
https://source.android.com/security/verifiedboot/
In a nutshell, extra security on the boot partition to "ensure chain of trust" one of the possible requirements for Android Pay backend.
********EDIT***********
This method didn't work on the newest beta, and the OP3T ToolKit way has never worked for me on any version of OOS.
card13 said:
https://source.android.com/security/verifiedboot/
In a nutshell, extra security on the boot partition to "ensure chain of trust" one of the possible requirements for Android Pay backend.
********EDIT***********
This method didn't work on the newest beta, and the OP3T ToolKit way has never worked for me on any version of OOS.
Click to expand...
Click to collapse
I see thanks. I guess it doesn't matter to me cause I haven't started using android Pay and since I'm rooted currently
What causes the dm-verity issue in the first place?
guys if my device is unlocked will i still get the ota updates?
how about root ? if my device rooted willi still get ota updates?
saberzaid said:
guys if my device is unlocked will i still get the ota updates?
how about root ? if my device rooted willi still get ota updates?
Click to expand...
Click to collapse
Yes to first. No to second, It will try but will fail.
Sent from my ONEPLUS A3000 using Tapatalk
Mine is unlocked and rooted. The update failed. Then it redownloaded the full 1.4gb. That's how I found the URL. Then it flashed fine but brought recovery to stock and wiped root. Had to use the toolkit to get TWRP and root back.
So yes, even rooted gets the update
noahvt said:
Go to TWRP>Wipe>Advanced Wipe>Select system>Repair or change file system>Change filesystem>EXT4>Flash your ROM
That fixed it for me
Click to expand...
Click to collapse
I did a system restore previously and it set system to ext4. Maybe that's why I didn't have issues.
This dm-verity issue could be showing the instability of f2fs. Hmmm
Hello, just reset original rom under 6.0.1 and the problems and then twrp then flash rom custom
jejemc said:
Hello, just reset original rom under 6.0.1 and the problems and then twrp then flash rom custom
Click to expand...
Click to collapse
Hi guy, I followed your instruction, however, it still has the problem.
When I use the stock recovery to flash the beta1 package, it could not be flashed in.
lanbingxuanyi said:
Hi guy, I followed your instruction, however, it still has the problem.
When I use the stock recovery to flash the beta1 package, it could not be flashed in.
Click to expand...
Click to collapse
Hello, I am going under the beta with the message in red dm-verity for the removed I returned under original rom then I handed twrp then rom custom
card13 said:
https://source.android.com/security/verifiedboot/
In a nutshell, extra security on the boot partition to "ensure chain of trust" one of the possible requirements for Android Pay backend.
********EDIT***********
This method didn't work on the newest beta, and the OP3T ToolKit way has never worked for me on any version of OOS.
Click to expand...
Click to collapse
PaKii94 said:
I see thanks. I guess it doesn't matter to me cause I haven't started using android Pay and since I'm rooted currently
Click to expand...
Click to collapse
I'm running 7.0 stable, unlocked bootloader and dm-verity warning. Android Pay still functions with the workaround.
Hi,
My goal is just to root the device so that I can remove bloatware. I don't intend to run custom ROM. I'm currently running 7 QF1 build
Found https://forum.xda-developers.com/galaxy-tab-a/how-to/newbie-friendly-twrp-root-tab-tablets-t3552509 but want to confirm a few details before proceeding.
1. It seems the first the step is to flash TWRP with Odin. Is this correct? Is there a particular version of Odin or TWRP that I would need?
2. Once that's done, it's to install SuperSU using TWRP. Is that correct? Once that's done, what should I do if the SuperSU tells to upgrade later?
3. Once step 1 and 2 complete, the device would be rooted. At that point, what should I do with system upgrade? Can I still take it OTA? Or it has to be manual? If manual, how do I disable auto update?
Thanks
i know this is old but if you install twrp through ODIN you will no longer be able to get OTA. it will recognize that the recovery partition has been tampered with and refuse to update. only way around this is to update to current first before putting twrp and attempting root. As far as your other questions i cant help because im having trouble installing twrp myself, have to keep reverting to stock....
AesopRock127 said:
i know this is old but if you install twrp through ODIN you will no longer be able to get OTA. it will recognize that the recovery partition has been tampered with and refuse to update. only way around this is to update to current first before putting twrp and attempting root. As far as your other questions i cant help because im having trouble installing twrp myself, have to keep reverting to stock....
Click to expand...
Click to collapse
If you keep reverting to stock after flashing TWRP it is because you are allowing the tab to reboot to system after the flash. When it does that, it rewrites the stock recovery. You have to uncheck the auto reboot option prior to flashing. Then, after flashing, hold the Home, Vol down and Power buttons for about ten seconds. As soon as the screen goes black, switch your finger from Vol down to Vol up and the tab will boot to TWRP instead of system. You have to quick when switching from Vol down to up.
As to OTAs, that is pretty much a lost cause. What you have to realize is that once you have flashed TWRP, for all intents and purposes you are now running a "custom ROM" and won't get OTAs from Samsung. You might as well go ahead and install a ROM like RR and a minimal Gapps rather than manually erasing apps. That is pretty much their purpose. That and getting the latest Android versions without wait forever to get them from Samsung. They DO NOT need to be rooted and that is what most people that avoid custom ROMs are worried about.
lewmur said:
If you keep reverting to stock after flashing TWRP it is because you are allowing the tab to reboot to system after the flash. When it does that, it rewrites the stock recovery. You have to uncheck the auto reboot option prior to flashing. Then, after flashing, hold the Home, Vol down and Power buttons for about ten seconds. As soon as the screen goes black, switch your finger from Vol down to Vol up and the tab will boot to TWRP instead of system. You have to quick when switching from Vol down to up.
As to OTAs, that is pretty much a lost cause. What you have to realize is that once you have flashed TWRP, for all intents and purposes you are now running a "custom ROM" and won't get OTAs from Samsung. You might as well go ahead and install a ROM like RR and a minimal Gapps rather than manually erasing apps. That is pretty much their purpose. That and getting the latest Android versions without wait forever to get them from Samsung. They DO NOT need to be rooted and that is what most people that avoid custom ROMs are worried about.
Click to expand...
Click to collapse
Thanks for the info.... i was aware of all that and i was doing everything right i just didn't realize i couldn't use any old twrp posted for my device in my devices rom and recoveries section. Reading through the 50 some odd pages i found one that worked for oreo and voila everythings fine now