Root SM-T580 with Odin/TWRP and upgrade afterward - Samsung Galaxy Tab A series Questions & Answers

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

Related

Taking Ota Questions.

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.

Lolipop OTA capture

Update 2 after some fiddling I found that after flashing Pico Capps hdxposed is needed to make the play store work on this build http://forum.xda-developers.com/showthread.php?t=2618158
Update 1 New lolipop ota, this appears to be based on lolipop 5.1 and as such requires xposed unofficial by romracer if you want to use xposed Xposed for 5.0 would not flash for me. Same upgrade steps as before just this one instead of the bottom one and change your xposed package
https://mega.nz/#!i5RRCKQZ!NC291mcIo-2yzr23j8Vg_mLZ11ECql4lL_xen6xwXuM
update-kindle-devpreview_ariel-20.5.2.2_user_522041550.bin
siegesoldier said:
this is the developer preview, sorry if the title is a little misleading. Thanks to http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-4-5-4-twrp-root-t3141648
Use at your own risk.
https://www.dropbox.com/s/38i2lqq5p...review_ariel-20.5.2.0_user_520033250.bin?dl=0
Hopefully someone can figure out how to make this thing boot when flashed from TWRP
Click to expand...
Click to collapse
Important update, the instructions below are not to be followed !!! They are historical ...
Same drill as in here :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-4-5-4-twrp-root-t3141648
Replace the original META-INF/com/google/android/updater-script with the one from the zip below. Remove "images" directory. This will ensure that your bootloader stays 4.5.3 and unlocked. When TWRP asks to add root, say yes.
If for some reason you lose TWRP (recovery), reflash it from within 5.0. Since you have root, no biggie. I'll play with this a bit too, but later.
I tried yours and tried my attempt. I'm getting a bootloop with both, let me know if you have any luck. TWRP protects itself from getting replaced.
siegesoldier said:
I tried yours and tried my attempt. I'm getting a bootloop with both, let me know if you have any luck. TWRP protects itself from getting replaced.
Click to expand...
Click to collapse
OK. Does it flash successfully? Does it ask to install root? If it does and bootloops, the bootloader probably needs to be updated too. You could try to flash the new bootloader (just grab my uboot_4.5.3.zip, replace both files in /images, and re-zip).
The trick is that you install Lollipop, install root, and install the new bootloader separately. It should boot OK and you should have root in 5, but you'll lose TWRP (it won't be able to boot since the bootloader will probably be signed). To get TWRP back you'll need to downgrade to 4.5.3
bibikalka said:
OK. Does it flash successfully? Does it ask to install root? If it does and bootloops, the bootloader probably needs to be updated too. You could try to flash the new bootloader (just grab my uboot_4.5.3.zip, replace both files in /images, and re-zip
Click to expand...
Click to collapse
Yes it flashes successfully and asks to install root. Looks like I'll be trying that tonight, thanks!
Edit we have a winner.
Flashed lolipop without bootloader
Installed su
Reboot to recovery
Installed superuser flashable zip
Flashed uboot file with lolipop images folder
Fire has booted and is currently doing the very long lolipop upgrading screen
Currently booting to home screen but then back to the fire screen, etc. Probably my fault for not clearing the cache or a factory reset. I'm not at a computer at the moment but any ideas on how to fix this?
siegesoldier said:
Currently booting to home screen but then back to the fire screen, etc. Probably my fault for not clearing the cache or a factory reset. I'm not at a computer at the moment but any ideas on how to fix this?
Click to expand...
Click to collapse
Turn it off with a long press of "power" button. Then press "power" and "vol+" together, this should get you into the Amazon recovery. It should offer you a factory reset option. Your system should be pretty much stock Lollipop, so I don't see why it should be doing what it does ...
Actually, does it now have stock Amazon recovery or TWRP ? My suspicion is that it should have flashed recovery during the first upgrade cycle.
Upon reflection, there is a chance you have a bit of a soft brick. If the factory reset option does not come up, it may end up a little tricky to fix things. I wonder if you'd be able to connect via adb before it reboots.
bibikalka said:
Turn it off with a long press of "power" button. Then press "power" and "vol+" together, this should get you into the Amazon recovery. It should offer you a factory reset option. Your system should be pretty much stock Lollipop, so I don't see why it should be doing what it does ...
Actually, does it now have stock Amazon recovery or TWRP ? My suspicion is that it should have flashed recovery during the first upgrade cycle.
Click to expand...
Click to collapse
it appears to have TWRP but it will not boot to it with holding keys. I can get the device to appear in ADB but I can not authorize it. Appears to not actually be rebooting. just crashing to fire screen for some reason then back to launcher etc. I may be able to try again at home with a usb port that it remembers.
siegesoldier said:
it appears to have TWRP but it will not boot to it with holding keys. I can get the device to appear in ADB but I can not authorize it. Appears to not actually be rebooting. just crashing to fire screen for some reason then back to launcher etc. I may be able to try again at home with a usb port that it remembers.
Click to expand...
Click to collapse
I wonder if Lollipop does not update recovery at all, and just uses the one from 4.5.4 You do have your old settings around, so there is a chance that prior USB authorization will help. It looks like one should have updated to stock recovery while in TWRP as the last step, after updating the bootloader, ir order to be able to do a factory reset in a situation like this.
If it comes to worst, Amazon reps never ask "did you brick the device yourself?". They only ask if you can get to the home screen, and if not, proceed with the replacement
I think TWRP just blocked it from updating. Oh well, if the ports at home don't work, I was eventually going to get it replaced anyway since I had a blue discoloration on my screen. Glad to be of some moderate use to the community instead of a leecher for once. May the next person have some luck!
bibikalka said:
I wonder if Lollipop does not update recovery at all, and just uses the one from 4.5.4 You do have your old settings around, so there is a chance that prior USB authorization will help. It looks like one should have updated to stock recovery while in TWRP as the last step, after updating the bootloader, ir order to be able to do a factory reset in a situation like this.
If it comes to worst, Amazon reps never ask "did you brick the device yourself?". They only ask if you can get to the home screen, and if not, proceed with the replacement
Click to expand...
Click to collapse
ok I was able to get adb on a previously used port. I do not have root though. What are my options? What recovery should I flash? I also have a replacement kindle coming tomorrow so this is mostly for science now. I am also able to get into bootloader.
erased cache via fastboot. stuck on fire instead of boot to homescreen
siegesoldier said:
ok I was able to get adb on a previously used port. I do not have root though. What are my options? What recovery should I flash? I also have a replacement kindle coming tomorrow so this is mostly for science now. I am also able to get into bootloader.
erased cache via fastboot. stuck on fire instead of boot to homescreen
Click to expand...
Click to collapse
So no adb anymore? I am not sure how SuperSu comes in, there gotta be su program somewhere.
Anyway, the great news is that JMZ is going to be back soon. That's going to boost our tinkering capabilities by 300%
siegesoldier said:
Yes it flashes successfully and asks to install root. Looks like I'll be trying that tonight, thanks!
Edit we have a winner.
Flashed lolipop without bootloader
Installed su
Reboot to recovery
Installed superuser flashable zip
Flashed uboot file with lolipop images folder
Fire has booted and is currently doing the very long lolipop upgrading screen
Click to expand...
Click to collapse
And then soft brick ...
So I wonder now if one could do this :
install 5.2.0 via TWRP
install supersu.zip
and here it gets very tricky:
without any reboots, replace TEE1, UBOOT, and recovery to stock versions 5.2.0
The hope is to end up in 5.2.0 with root. If things fail, then booting into 5.2.0 recovery (which must be installed!!!) should give one an option to do 1) factory reset 2) downgrade to stock 4.5.3 as in here : http://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351
The problem is that I don't see a way to boot into 5.2.0, and then flash GAPPS after (since your TWRP was replaced by stock recovery earlier). So one would have to install GAPPS those via something like Titanium backup if root does work.
Please, if you already had 1 warranty replacement, don't do this. And, if you replace TEE1 and UBOOT (5.2.0) but not recovery, then you won't have any way to recover.
bibikalka said:
And then soft brick ...
So I wonder now if one could do this :
install 5.2.0 via TWRP
install supersu.zip
and here it gets very tricky:
without any reboots, replace TEE1, UBOOT, and recovery to stock versions 5.2.0
The hope is to end up in 5.2.0 with root. If things fail, then booting into 5.2.0 recovery (which must be installed!!!) should give one an option to do 1) factory reset 2) downgrade to stock 4.5.3 as in here : http://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351
The problem is that I don't see a way to boot into 5.2.0, and then flash GAPPS after (since your TWRP was replaced by stock recovery earlier). So one would have to install GAPPS those via something like Titanium backup if root does work.
Please, if you already had 1 warranty replacement, don't do this. And, if you replace TEE1 and UBOOT (5.2.0) but not recovery, then you won't have any way to recover.
Click to expand...
Click to collapse
Yes I've used my warranty replacement so I'll be waiting until the official release before breaking my kindle again . How do you stop TWRP from preventing the recovery from being flashed? I noticed it gave a message about protecting itself.
siegesoldier said:
Yes I've used my warranty replacement so I'll be waiting until the official release before breaking my kindle again . How do you stop TWRP from preventing the recovery from being flashed? I noticed it gave a message about protecting itself.
Click to expand...
Click to collapse
Interesting, at what stage of the update did this happen? 5.2.0 file system is slightly packaged and is pain in the neck to peak into, but in 4.5.3 the recovery is updated via a pretty specific command install-recovery.sh , and I cannot find any references to this in updater-script. So I wonder at what stage will this be run. Also, there is no direct image for recovery, one has to reconstruct it as the commands below do. A bit messy ...
install-recovery.sh
Code:
#!/system/bin/sh
if ! applypatch -c EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery:5888256:6d9d1bbc4172c107db3228ed8d9f97111219c617; then
log -t recovery "Installing new recovery image"
applypatch -b /system/etc/recovery-resource.dat EMMC:/dev/block/platform/mtk-msdc.0/by-name/boot:5370112:c2c686ada1b194050a3c8f05e2102345df48e9ce EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery 6d9d1bbc4172c107db3228ed8d9f97111219c617 5888256 c2c686ada1b194050a3c8f05e2102345df48e9ce:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
Edit: It kind of looks like /system/etc/install-recovery.sh will be run at every boot. So I wonder if TWRP just renames it to something and calls it "protection". I guess one can double check the file system after 5.2.0 update while still in TWRP, and see what happened to recovery files.
Help
If someone can please help me. I downloaded the update to 5.0, unzipped it, replaced the updater script, but when I zip it back and try to flash it says that it failed. Am I doing something wrong.
Also, if someone has the zip file already and wouldn't mind uploading and sharing it, I would appreciate it.
Thanks for all the help.
hawkazn said:
If someone can please help me. I downloaded the update to 5.0, unzipped it, replaced the updater script, but when I zip it back and try to flash it says that it failed. Am I doing something wrong.
Also, if someone has the zip file already and wouldn't mind uploading and sharing it, I would appreciate it.
Thanks for all the help.
Click to expand...
Click to collapse
Last time this procedure ended up with a soft brick. Are you sure you want to pursue this route?
Help
Maybe not, but if someone can help me with something else. The developer preview for the camera is extremely sharp and the 4.5.4 really isn't. Is there a way to make it crystal clear and sharp?
hawkazn said:
Maybe not, but if someone can help me with something else. The developer preview for the camera is extremely sharp and the 4.5.4 really isn't. Is there a way to make it crystal clear and sharp?
Click to expand...
Click to collapse
Meaning exactly what? It'd be possible to replace the camera app, one for another. Do you think some other system stuff is involved such as some sort of settings?
You'll have to find a way to mount the big 5.2.0 system update file as a filesystem, then you could read what's in there, including the camera stuff.
TWRP help
So I downloaded the zip file for 5.0 and it flashed and asked to install super user. I had to download the apk for supersu and then update it.
But the problem is that I lost my twrp. I push the volume + and power and it just reboots. I also lost my play store. Any thoughts how to get twrp back on?

How to fix DM-VERITY issue for 7.0 flashed updates

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.

Need stock Ascend XT recovery

Does anyone have a copy of the stock recovery? I'm trying to upgrade to b150 (both automated via the setting menu and manually by secret menu) but every time it tries to flash the firmware, the phone just reboots to TWRP and sits there.
Any help would be appreciated.
The directions you should be following have a copy of the stock recovery, don't they? If not, post a link to those directions.
Bill R said:
Does anyone have a copy of the stock recovery? I'm trying to upgrade to b150 (both automated via the setting menu and manually by secret menu) but every time it tries to flash the firmware, the phone just reboots to TWRP and sits there.
Any help would be appreciated.
Click to expand...
Click to collapse
divineBliss said:
The directions you should be following have a copy of the stock recovery, don't they? If not, post a link to those directions.
Click to expand...
Click to collapse
The first attempt was not following a guide. It was by going into the AT&T Software Update settings applet (my phone is on b140 and b150 was downloaded this way). That would start to load the update, reboot the phone into TWRP and then sit there. Subsequent booting into the OS would only re-attempt to install the update which would again reboot to TWRP.
After recovering my phone from a pre-update backup I tried, somewhat, following this method:
https://forum.xda-developers.com/android/development/guide-how-to-update-b130-to-b140-b150-t3555254
I was able to install the stock b140 image from my SD card but where it said TWRP would be gone, mine still had it. Attempting the secret menu would start the firmware update which would, again, boot to TWRP and sit there.
The stock ROMs in that guide thread should have stock recovery images. Just restore one of those stock recovery images using TWRP. Does your phone still have root?
Bill R said:
The first attempt was not following a guide. It was by going into the AT&T Software Update settings applet (my phone is on b140 and b150 was downloaded this way). That would start to load the update, reboot the phone into TWRP and then sit there. Subsequent booting into the OS would only re-attempt to install the update which would again reboot to TWRP.
After recovering my phone from a pre-update backup I tried, somewhat, following this method:
https://forum.xda-developers.com/android/development/guide-how-to-update-b130-to-b140-b150-t3555254
I was able to install the stock b140 image from my SD card but where it said TWRP would be gone, mine still had it. Attempting the secret menu would start the firmware update which would, again, boot to TWRP and sit there.
Click to expand...
Click to collapse
divineBliss said:
The stock ROMs in that guide thread should have stock recovery images. Just restore one of those stock recovery images using TWRP. Does your phone still have root?
Click to expand...
Click to collapse
I checked when you asked and surprisingly it does not. I'm surprised because I thought I re-installed it when I flashed the b140 ROM from that thread.
I'll try again this evening.
Also, if you followed the rooting guides, you should have your own copy of the stock recovery in your first TWRP backup.
Bill R said:
I checked when you asked and surprisingly it does not. I'm surprised because I thought I re-installed it when I flashed the b140 ROM from that thread.
I'll try again this evening.
Click to expand...
Click to collapse
Bill R said:
I checked when you asked and surprisingly it does not. I'm surprised because I thought I re-installed it when I flashed the b140 ROM from that thread.
I'll try again this evening.
Click to expand...
Click to collapse
The roms do NOT include Stock Recovery or any recovery for that matter ...Roms don't flash recovery (none that I have ever flashed anyway)
If you need B140 Stock recovery it's here B140.Stock.recovery.img
The Guide kind of assumes you just did the B130 to B140 update and you already have stock recovery installed
and yes if your phone was B140 when you rooted it you should already have your own stock backup of B140
I have to confess to a case of cranial flatulence. I had made a stock recovery backup. I'll proceed to banging my head on my desk now.
Back to business. So, after breaking my phone three times today, I finally got it back to the stock b140 (H1611C07B140) from the other thread and I'm ready to try the firmware upgrade again. I still have TWRP on it though so I'm wondering if I should reinstall the stock recovery first before trying the firmware upgrade. The other thread states that the b140-to-b150 firmware should overwrite the recovery but for me every time I do the firmware it boots to TWRP and sits there.
Bill R said:
I have to confess to a case of cranial flatulence. I had made a stock recovery backup. I'll proceed to banging my head on my desk now.
Back to business. So, after breaking my phone three times today, I finally got it back to the stock b140 (H1611C07B140) from the other thread and I'm ready to try the firmware upgrade again. I still have TWRP on it though so I'm wondering if I should reinstall the stock recovery first before trying the firmware upgrade. The other thread states that the b140-to-b150 firmware should overwrite the recovery but for me every time I do the firmware it boots to TWRP and sits there.
Click to expand...
Click to collapse
Yes I corrected the Guide
Flash stock recovery before doing the dload/ update.app flash
as soon as the firmware update is done boot to the bootloader
fastboot boot H1611.TWRP.New.img
then mount cust / system and data and flash the B150.Stock.rom
also flash Supersu and reboot
Thanks guys! I was finally able to get the b150 on with the additional instructions. Key was a couple of items:
Me confusing TWRP that I already had with H1611.TWRP.New.img.
Needing to go back to the stock recovery for the firmware upgrade
Discovering, by chance, that to get to fastboot mode with the power + volume down button it had to be connected to the PC via USB. It doesn't work if not connected.
Tomorrow I will get to where I've been wanting by installing the ROM to get rid of the AT&T bloat.
So thanks again!
Bill R said:
Thanks guys! I was finally able to get the b150 on with the additional instructions. Key was a couple of items:
Me confusing TWRP that I already had with H1611.TWRP.New.img.
Needing to go back to the stock recovery for the firmware upgrade
Discovering, by chance, that to get to fastboot mode with the power + volume down button it had to be connected to the PC via USB. It doesn't work if not connected.
Tomorrow I will get to where I've been wanting by installing the ROM to get rid of the AT&T bloat.
So thanks again!
Click to expand...
Click to collapse
It's pretty clear in the guide
When it's done it will reboot the phone so now boot to the bootloader with power + volume down while hooked to the PC via USB
Click to expand...
Click to collapse
Anyway congratulations
I hope you Enjoy the CleanRom

I'm panicking a bit and i'd really need help :(

Hello ! So i'm bit stressed now cause i never had an unpullable battery before on my samsung.
So i just got from my cousin a galaxy s6 edge plus, and i want to root it. so installed odin and flashed twrp-3.1.0-0-zeroflte.img.tar
However now it kept being on the samsung logo. So i had to e press and hold the Volume down and Power/Lock keys on the device for 10–20 seconds to power it off. But it keeps rebooting, and now, it's only a black screen with a blue led. I don't know what to do, i'd really need your help. Thank you I'm so worried gosh.
update 1: i tried to force shut down by pressing the buttons and it used to display the samsung and carrier logo then be stuck on samsung logo, but now it just shows samsung galaxy, turn off and the recent apps et return buttons blinking. Kinda scary. I'm waiting for the battery to discharge, hopefully it will work I need your help
The zerolte is for the S6 EDGE, you want the zenlte
http://twrp.me/devices/samsunggalaxys6edgeplus.html
You should be able to hold vol down, home and power buttons to get into download mode to flash it.
Use the power and volume down button to force reset and when it does quickly press all 3.
Thank you for your time ! i did as you said, i entered twrp recovery mode and performed a wipe, but i'm still in a bootloop ! any ideas ?
EDIT : but i installed the new twrp over the old one might it be conflicting ?
I went back to 3.0.2.0 and don't have a bootloop issue anymore, it may be the latest update giving the issues.
Ehhh going back to the 3.0.2.0 didn't work either. I have the TWRP menu, have wiped, but i'm still in a bootloop. :/ I'm happy cause it's not bricked but i still use my phone...any help appreciated guys :<
So are you using a custom rom?
You can enter twrp to install/wipe etc?
nope i'm on stock rom and yeah i can enter twrp and install and wipe !
Like i just wanted to root my phone with stock rom, how can i achieve it ? :c
sleepyGrin said:
Like i just wanted to root my phone with stock rom, how can i achieve it ? :c
Click to expand...
Click to collapse
cf auto root can root and keep stock rom
oh nice i've just looked it up. How can i go from my current state to cf auto root ? RIght now it's boot loop with twrp, what can i do to go back to stock rom and use my phone again ? thanks
sleepyGrin said:
oh nice i've just looked it up. How can i go from my current state to cf auto root ? RIght now it's boot loop with twrp, what can i do to go back to stock rom and use my phone again ? thanks
Click to expand...
Click to collapse
Well you can download your stock rom for your model, mine is sm-g928r4 not sure what yours is but ya. Then use odin to flash the stock img and then use cf auto root to get root.
i flashed my rom but it failed and now im stuck with samsung smart switch but its not working, i don't know what to do really..
sleepyGrin said:
i flashed my rom but it failed and now im stuck with samsung smart switch but its not working, i don't know what to do really..
Click to expand...
Click to collapse
Just download the latest firmware for your smartphone (SM-G928x (Replace the x with your spessific model number on the back)) and your country from sammobile.com and flash it through odin. This should wipe your data and perform a clean reflash of the stock ROM. After that procedure it will take about 10 minutes to boot and it should be working again
sammobile is pretty slow is SamFirm okay ? And thanks i'l ltry this !
ok so i tried to flash the rom from sam firm for my SM-G928F SFR but it just shows up with a failed... any ideas ?
I had an issue trying to flash stock Rom back, I was trying to flash an older version and it failed, i downloaded the latest for my model and it worked. Are you sure you downloaded the right one?
sleepyGrin said:
oh nice i've just looked it up. How can i go from my current state to cf auto root ? RIght now it's boot loop with twrp, what can i do to go back to stock rom and use my phone again ? thanks
Click to expand...
Click to collapse
I presume you ave the SM-G928F S6 Edge +. Just flashing TWRP will cause boot loop. Please see post and flash via twrp the section 12. This should stop the bootloop. Allways remember never turn of OEM locking if you have a custom recovery.
" If you only want a bootable system partition or readable data in TWRP:
Download dm-verity and force encryption disabler.
Without exiting TWRP, transfer no-verity-opt-encrypt.zip to your device over MTP* and flash it using [Install] in TWRP.
** If your internal storage is encrypted, you will need to use adb sideload instead."
https://forum.xda-developers.com/s6...ecovery-official-twrp-galaxy-s6-edge-t3354492

Categories

Resources