Database Info

Stopping an ota

I just picked up my m8 from Verizon. Here's what it's running. Is there a way to stop it from updating to the new ota it's wanting to install?
If I try weaksauce and then firewater can I accept the ota or should I not because it will lock the boot loader down? It's always been don't accept otas when unlocked with the s3.
Can anyone help me with the steps I should use? I'm thinking weaksauce, then firewater, then twrp install, then flash su zip? Then what do I do about otas trying to install? Besides flashing a new Rom?
Also, there is a way to go back to full stock right?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

From what I've read the ota doesn't break anything that would stop you from being able to s-off. However if you want to s-off before taking the ota then you can do so. There should be a thread around here that contains the zip of the latest ota firmware and radios, etc that you can flash and be up to date without going through the hassle of returning the recovery and such to stock.

On the Verizon m8? Cause I'm reading that firewater may not work on the newest ota. Any ideas?

Nobody has any input? Surely some here have experience on this device that they got recently from Verizon?

silver04v said:
Nobody has any input? Surely some here have experience on this device that they got recently from Verizon?
Click to expand...
Click to collapse
I used Firewater on mine without doing the OTA and I'd recommend you do the same just incase.

S1L3nTShaDoWz said:
I used Firewater on mine without doing the OTA and I'd recommend you do the same just incase.
Click to expand...
Click to collapse
What did you do afterwards to prevent the ota after soff was done? Did you install twrp and flash su in recovery after?

silver04v said:
What did you do afterwards to prevent the ota after soff was done? Did you install twrp and flash su in recovery after?
Click to expand...
Click to collapse
I believe after I went S-OFF I just flashed a custom ROM. On the other hand I think flashing SuperSU would make the updates fail in the future if thats good enough to you. & Yes I did that too I think.
I know on the Galaxy S4 you could freeze the app giving you notifications about the OTA updates, not sure if you can do that on the M8 or not as I haven't really needed to do it but you could check that out too if all else fails.

Maybe I'll just stop being a new device wuss and flash clean rom. As I want stable and no fussing right now.
What about going stock? Is it possible to lock it all back up if needed?

silver04v said:
Maybe I'll just stop being a new device wuss and flash clean rom. As I want stable and no fussing right now.
What about going stock? Is it possible to lock it all back up if needed?
Click to expand...
Click to collapse
It's not really being a wuss, honestly you're quite smart to ask questions before doing stuff. Let's just say for example, you did everything with no research no questions asked and pretended you were the master of everything you didn't know YET you would eventually screw up if not immediately. Sooo congrats to you for being smart : D!
Yes I'm quite sure you can lock it back up or at least to a point where it'd be extremely hard to tell whether it was or not. If you like trying new things I'd just try a few ROM's and find one you really like before you settle with one and then just set your stuff up and enjoy it
On the other hand if you like stock and prefer it over it then you can use Xposed and get some of the cool stuff you would from a ROM or even stuff you don't see in ROM's.

S1L3nTShaDoWz said:
It's not really being a wuss, honestly you're quite smart to ask questions before doing stuff. Let's just say for example, you did everything with no research no questions asked and pretended you were the master of everything you didn't know YET you would eventually screw up if not immediately. Sooo congrats to you for being smart : D!
Yes I'm quite sure you can lock it back up or at least to a point where it'd be extremely hard to tell whether it was or not. If you like trying new things I'd just try a few ROM's and find one you really like before you settle with one and then just set your stuff up and enjoy it
On the other hand if you like stock and prefer it over it then you can use Xposed and get some of the cool stuff you would from a ROM or even stuff you don't see in ROM's.
Click to expand...
Click to collapse
Yeah, I'm all for roms, been flashing since my droidx days. HTC is just new to me. I'm coming from a galaxy s3. So this is a bit different. But I think I'm understanding things.
Just nerve racking since I just paid outright for this to keep my unlimited.

Any other suggestions?
I'm thinking my steps are going to be weaksauce, then firewater, then download twrp and flash it. Then delete weaksauce and supersu then go into twrp and flash a super su zip for permanent root. Then start with cleanrom.
Sound about right?

I did firewater after taking the ota and it worked. Any way you choose to do it is fine. But taking ota definitely does not break the possibility of s-off on vzwM8

silver04v said:
Any other suggestions?
I'm thinking my steps are going to be weaksauce, then firewater, then download twrp and flash it. Then delete weaksauce and supersu then go into twrp and flash a super su zip for permanent root. Then start with cleanrom.
Sound about right?
Click to expand...
Click to collapse
That's almost exactly like I did it, except I don't think you have to flash SuperSU after installing TWRP since you will install CleanROM anyway. The rom is rooted out of the box.
The way I understand it (and I'm also new to HTC - have done all my flashing on Asus tablets and Moto phones), flashing a rom will format and overwrite /system anyway. And that's where root lives, right?

Well I got it done. Didn't take the ota and I used weak sauce, then firewater, then fastboot flashed twrp, installed SuperSU zip and I'm off and rolling. Ready to install clean ROM. I'm loving this device.

[Q] How to update rooted Moto G?

Hi,
I hope this has not been covered more than once - I've really searched for it on this forum but couldn't find anything about it.
I rooted my Moto G. All I wanted was to use the "Greenify" App and to fix a wakelok that seems to happen occasionally, getting my battery time back to ~10 days again (I hardly use the phone). I don't need root for anything else.
I am very interested in the Android L update, though, because of a couple of features I have been waiting for for very long.
And of course I would appreciate getting rid of the "update available" notification.
What is the easiest/most foolproof way for me to update my Moto G, possibly using OTA?

fertchen said:
Hi,
I hope this has not been covered more than once - I've really searched for it on this forum but couldn't find anything about it.
I rooted my Moto G. All I wanted was to use the "Greenify" App and to fix a wakelok that seems to happen occasionally, getting my battery time back to ~10 days again (I hardly use the phone). I don't need root for anything else.
I am very interested in the Android L update, though, because of a couple of features I have been waiting for for very long.
And of course I would appreciate getting rid of the "update available" notification.
What is the easiest/most foolproof way for me to update my Moto G, possibly using OTA?
Click to expand...
Click to collapse
Download VooDoo OTA RootKeeper on the Google play store, it temporary disables root. After that, you can restore root. Hope that helps.
Sent from my SM-T310

thebestiam said:
Download VooDoo OTA RootKeeper on the Google play store, it temporary disables root. After that, you can restore root. Hope that helps.
Sent from my SM-T310
Click to expand...
Click to collapse
Thanks. This seems to be intended to keep root only, though. My problem is (sorry that I was unable to clarify this in my first post) that I can not use the OTA update for my Moto G at all because it is rooted. If I try to apply the OTA update the phone will get stuck in an endless reboot-loop because of some checksum failure or so (as desribed here: http://forum.xda-developers.com/moto-g/help/android-4-4-2-to-4-4-4-failed-t2819308
Is there a foolproof way to get around this issue as well?

This should help you.

I rooted my Moto G using this excellent tutorial: http://www.swedroid.se/forum/showthread.php?t=106595
As I see it, the only reason the OTA update does not work is the fact that the recovery partition was changed and thus the checksum does not match. I also assume that I would just need to restore the stock recovery in order for the OTA updates to work again. Is that correct?
As I said, I am really not interested in any custom tinkering at all. The only thing I wanted was root access and I have grown to like Greenify. It is my understanding that I do not need CWM in order to retain root access. What I would like to achieve now is to install the OTA updates without worries. I could live with having to root the device again after each update, provided that does not involve flashing recovery and unlocking again.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mokkami said:
This should help you.
Click to expand...
Click to collapse
Thanks for the pointer. But maybe there is a different way.

fertchen said:
As I said, I am really not interested in any custom tinkering at all. The only thing I wanted was root access and I have grown to like Greenify. It is my understanding that I do not need CWM in order to retain root access. What I would like to achieve now is to install the OTA updates without worries. I could live with having to root the device again after each update, provided that does not involve flashing recovery and unlocking again.
Click to expand...
Click to collapse
You could reflash stock recovery and then OTA should work if that's what it was falling over on. If you lose root and need to re-root, you can do so by reflashing the recovery installable zip version of SuperSU from acustom recovery, which of course you now won't have.
However, you can always boot into a custom recovery from a PC without actually flashing it, i.e. get into fastboot mode and do:
Code:
fastboot boot yourfavouritecustomrecovery.img
that should boot you into CWM (or whatever) temporarily without overwriting your stock recovery so you can re-root. You won't need to unlock the bootloader again.
If you upgrade to the premium version of SuperSU it has a feature that attempts to survive OTA updates that may save you having to re-root, but YMMV.

fertchen said:
Hi,
I hope this has not been covered more than once - I've really searched for it on this forum but couldn't find anything about it.
I rooted my Moto G. All I wanted was to use the "Greenify" App and to fix a wakelok that seems to happen occasionally, getting my battery time back to ~10 days again (I hardly use the phone). I don't need root for anything else.
I am very interested in the Android L update, though, because of a couple of features I have been waiting for for very long.
And of course I would appreciate getting rid of the "update available" notification.
What is the easiest/most foolproof way for me to update my Moto G, possibly using OTA?
Click to expand...
Click to collapse
You can try to update the OTA by following the steps in the OP of this Post. It worked for me
http://forum.xda-developers.com/moto-g/general/ota-file-indian-dual-sim-4-4-4-t2810166
Just follow the steps below the text:
REVERT TO STOCK WITHOUT LOSING DATA OR ANYTHING ELSE
Basically you have to do this. Restore stock, do the OTA and than reroot using superboot to root.
Phone is unlocked, rooted and had xposed modules on it

Get back to stock ROM and check for updates

You can also try to find an official 4.4.4 firmware, flash it without wiping anything except the cache partition, and re-root afterwards.
So your phone is being updated, you won't lose anything and you still get root.
I did that with my Moto G 4G/LTE and it works beautifully.
Hope that helps.

Thanks for all your input.
Going back to stock recovery did not fix the OTA update problem/boot loop.
Even though I never installed a custom ROM I ended up re-installing the stock 4.4.2 firmware (without erasing userdata) and then just applying the OTA update.
Now I tried booting into CWM (fastboot boot recovery.img) but that just leads to "waiting for device", so I flashed CWM recovery again, rooted and then restored stock recovery. Works.
And I have learnt quite a bit in the process. That's always nice.
Thank you guys, you reign supreme.

Zte Prestige N9132 Temp root achieved

Hello, New poster long time reader. Anyway lets get on with it.
I was able to achieve temp root with Kingo Root v1.4.4 today about 3 mins ago. Lmao
but like I said its temp root I'm trying to get a perm root method with adb. still have a locked boot loader.
if anyone eles wants to help with a perm root that woud be wonderful.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

root n9132
AcidicTyranny said:
Hello, New poster long time reader. Anyway lets get on with it.
I was able to achieve temp root with Kingo Root v1.4.4 today about 3 mins ago. Lmao
but like I said its temp root I'm trying to get a perm root method with adb. still have a locked boot loader.
if anyone eles wants to help with a perm root that woud be wonderful.
Click to expand...
Click to collapse
i also want root it . this device have gsm capabilities any one know how use it on tmobile or att.

Did you try Kingo and did the temp root work for you? Let me know. Thanks

do this before you use Kingo
http://androidforums.com/threads/zte-write-protection-for-zmax-and-other-phones.1040331/

Didn't work on my bootlooped ztemax in ftm mode. But I'm in the process of trying this on my n9132. I have one question about this. The N9132 has a boot loader. Will the boot loader block this from working or won't have any effect? This is the first phone I've encountered a bootloader on so I have 0 experience with a bootloader. I'm still going to do it anyway I was just curious.
I just want to confirm that it works for a permanent root for the N9132
"This was found by me (Hroark13),I can not believe it was this easy
To turn off nand / system write protection on the ZTE ZMAX and maybe other phones
run this command in adb shell or terminal
reboot disemmcwp
to re-enable write protection issue this command
reboot emmcwpenab
I AM A FARKING GENIUS"
Massive credit goes to Mr. Hroark13
So basically use this command and then use ur favorite way to root and same as usual. Bada-boom Bada-bing permanent root. Restarted 10 times and never lost root.

AcidicTyranny said:
Didn't work on my bootlooped ztemax in ftm mode. But I'm in the process of trying this on my n9132. I have one question about this. The N9132 has a boot loader. Will the boot loader block this from working or won't have any effect? This is the first phone I've encountered a bootloader on so I have 0 experience with a bootloader. I'm still going to do it anyway I was just curious.
I just want to confirm that it works for a permanent root for the N9132
"This was found by me (Hroark13),I can not believe it was this easy
To turn off nand / system write protection on the ZTE ZMAX and maybe other phones
run this command in adb shell or terminal
reboot disemmcwp
to re-enable write protection issue this command
reboot emmcwpenab
I AM A FARKING GENIUS"
Massive credit goes to Mr. Hroark13
So basically use this command and then use ur favorite way to root and same as usual. Bada-boom Bada-bing permanent root. Restarted 10 times and never lost root.
Click to expand...
Click to collapse
Did running this command affect the bootloader? what was your preferred method to root after? Will it be possible to pull a system dump on this phone after I root it?

Mcrmpi said:
i also want root it . this device have gsm capabilities any one know how use it on tmobile or att.
Click to expand...
Click to collapse
That would be a SIM unlock. Rooting just allows access to the device's internals, such as for linking apps to the SD card or removing the pre-installed bloatware. I've been researching trying to figure out a full-root; not just a temp one.

When I try typing those command it returns "reboot: permission denied". Anything I can do about this? Thanks

There ya go
Turn USB Debugging on
Download ADB tools and driver
http://forum.xda-developers.com/show...8#post48915118
Open cmd and go to c:\adb\ then type adb reboot disemmcwp
After That install kingoroot from your pc then your finished
make sure your phone is plugged into your computer

Custom recovery and roms
Hi i just achieved root. Is there a custom recovery and roms

Still no recovery or any other development for this device? I'm just curious I like to play around with multiple phones/devices.. I usually carry around 3 at a time lol.. but since my main device my idol 4(cricket variant 6055U) is trailing behind the others ? I started messing with this ZTE prestige I came across for free... It was Google locked of course but I already got round that and also used the same root method as mentioned above.. it is permanent, not sure of the bootloader issue.. I do know it's not technically locked just not accessible.. even if you chose from recovery to reboot to the bootloader it just boots up normally.. I don't expect any crazy custom Roms but TWRP sure would be nice... ?. But for now.. at least we have permanent root!!
KiD •6055U•

omg it worked for n9130

Command
AcidicTyranny said:
Didn't work on my bootlooped ztemax in ftm mode. But I'm in the process of trying this on my n9132. I have one question about this. The N9132 has a boot loader. Will the boot loader block this from working or won't have any effect? This is the first phone I've encountered a bootloader on so I have 0 experience with a bootloader. I'm still going to do it anyway I was just curious.
I just want to confirm that it works for a permanent root for the N9132
"This was found by me (Hroark13),I can not believe it was this easy
To turn off nand / system write protection on the ZTE ZMAX and maybe other phones
run this command in adb shell or terminal
reboot disemmcwp
to re-enable write protection issue this command
reboot emmcwpenab
I AM A FARKING GENIUS"
Massive credit goes to Mr. Hroark13
So basically use this command and then use ur favorite way to root and same as usual. Bada-boom Bada-bing permanent root. Restarted 10 times and never lost root.
Click to expand...
Click to collapse
Where do we run this command at?
---------- Post added at 11:24 PM ---------- Previous post was at 11:10 PM ----------
HERPDERP202 said:
Turn USB Debugging on
Download ADB tools and driver
http://forum.xda-developers.com/show...8#post48915118
Open cmd and go to c:\adb\ then type adb reboot disemmcwp
After That install kingoroot from your pc then your finished
make sure your phone is plugged into your computer
Click to expand...
Click to collapse
Where do we download this adb and drivers at? To our ZTE device or pc? And where do we preform the command?

If you can't find the adb drivers for PC, or you are not able to install them, just connect the device to the PC with device debugging mode enable, and run Kingo Root connected to the Internet until you get to the part where the big "ROOT" button is.
Don't press root yet..
Kingo will download and install the drivers for you, then run cmd again, as administrator, and type the command: "adb reboot disemmcwp" without the quotes like briandelafresh says above, your phone will reboot, and then you can continue with the root. It was a success on my ZTE Prestige N9132.
Note: Before all of that, Enable "OEM Unlock" located at settings-developer options in your device if that is the case, and make sure "Unknown Sources" is checked too at settings-security on your device.

Any just to let those who have not rooted there ZTE Prestige N9132 yet. There are a ton of people including me that need the stock firmware for that device. Don't be an idiot like the rest of us and not make a backup of that firmware before you root cause there is not one to be found anywhere on the net. And maybe share it with the rest of the class too. I'll be the first to tell you I'm still a noob any I have been playing with phones for like 2 yrs now. So I don't know the first thing about getting a copy of the stock firmware. But I assume it would happen something like this.. Right after you unlock bootloader with the above mentioned adb code and before you use your rooting tool, that would be the time to get the stock firmware. Nothing is change yet on the rom only the read and write permissions. And with read and write permissions active you should be able to use adb to make a copy of that recovery. But never done this type of thing before so I could be wrong. And please correct me if I am...

Chrisrobbins30 said:
There are a ton of people including me that need the stock firmware for that device. Don't be an idiot like the rest of us
Click to expand...
Click to collapse
FWIW, I am an idiot like most other average idiots that I find myself surrounded by.
However, I do have 3 ZTE Prestiges in my possession. Never even tried to root them. They are Boost phones. I don't know how that figures into it. I am tech savvy but am still learning the advanced root stuff as a hobby.

discoweasel said:
FWIW, I am an idiot like most other average idiots that I find myself surrounded by.
However, I do have 3 ZTE Prestiges in my possession. Never even tried to root them. They are Boost phones. I don't know how that figures into it. I am tech savvy but am still learning the advanced root stuff as a hobby.
Click to expand...
Click to collapse
What do you guys need? I've had mine rooted a long time

Sands207 said:
What do you guys need? I've had mine rooted a long time
Click to expand...
Click to collapse
A recovery ROM is needed to help some return to scratch. I could make one but as stated mine is a Boost phone. If it would be helpful I could put it up. I'm not sure how difficult it would be to backup though.

Someone please tell me how to accomplish this without a PC.

discoweasel said:
A recovery ROM is needed to help some return to scratch. I could make one but as stated mine is a Boost phone. If it would be helpful I could put it up. I'm not sure how difficult it would be to backup though.
Click to expand...
Click to collapse
If you can pull system dump that would greatly help

Cannot ROOT, SU BINARY OCCUPIED!!!

Hello all!
I cannot get root on my S7 as the title states.
I have loaded the ENG BOOT to my phone:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have followed this guide: https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502
with this New ROOT.BAT:
Code:
**EDIT: @jrkruse on 5/29/17 has created a new ROOT.BAT including SuperSU v2.82, it has been outlined in this post #480 of his custom rom thread. As always, please take a moment to hit the thanks button! Without the work of these amazing dev's we would NOT have root PERIOD! It is free for you, and mean's a lot to everyone involved in bringing these releases to you the public!!!
Here is latest root zip with SuperSU 2.82 (5/29/2017)
Nougat_S7_Root_2_82_All_Carriers_V1.zip
I let the phone reboot and when I open SuperSU, I receive the error "SU Binary Occupied". This happened the absolute very first time I attempted to root the phone, nothing has ever been done to the phone, it was 100% stock. I then unrooted the phone with the unroot.bat. I have been getting device disconnects when running the root.bat. My phone is connected and it is not actually disconnecting as far as I can see. I am also getting a "Protocol Error" occasionally when the script is attempting to install SuperSU. I can run the command by hand and it installs no problem, it only errors out with the script. I then use the unroot.bat and start over which the script will run fine again. The apps uninstall when the unroot.bat runs and they then re-install when the root.bat runs.
I have yet been able to root this phone successfully.
I did get the error to not show at one point after I ran the unroot.bat. I installed SuperSU v2.79 via adb cmd prompt, and then opened the app. It then gave me the SU binary needs to be updated error, which it fails at doing.
I really do not want to reset the phone as I'm not even sure that would solve anything as it didn't work the first time from stock.
I have read that there is TWRP working for the S7 but i cant tell if it's for the US version or not, I didn't look into it very deeply.
Does anyone have any advice?

Well, bit the bullet and re-flashed my phone using QH7 odin files and attempted root again. This time it has worked successfully!
It appears that there may have been something that installed funny when the upgrade to Nougat occurred as my reboot time is about 20 seconds now, compared to the 60 seconds it took previously.
Guess if you are getting the same problems when you've never rooted before, a re-flash may result in these issues resolving themselves.

eweo911 said:
Hello all!
I cannot get root on my S7 as the title states.
I have loaded the ENG BOOT to my phone:
I have followed this guide: https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502
with this New ROOT.BAT:
Code:
**EDIT: @jrkruse on 5/29/17 has created a new ROOT.BAT including SuperSU v2.82, it has been outlined in this post #480 of his custom rom thread. As always, please take a moment to hit the thanks button! Without the work of these amazing dev's we would NOT have root PERIOD! It is free for you, and mean's a lot to everyone involved in bringing these releases to you the public!!!
Here is latest root zip with SuperSU 2.82 (5/29/2017)
Nougat_S7_Root_2_82_All_Carriers_V1.zip
I let the phone reboot and when I open SuperSU, I receive the error "SU Binary Occupied". This happened the absolute very first time I attempted to root the phone, nothing has ever been done to the phone, it was 100% stock. I then unrooted the phone with the unroot.bat. I have been getting device disconnects when running the root.bat. My phone is connected and it is not actually disconnecting as far as I can see. I am also getting a "Protocol Error" occasionally when the script is attempting to install SuperSU. I can run the command by hand and it installs no problem, it only errors out with the script. I then use the unroot.bat and start over which the script will run fine again. The apps uninstall when the unroot.bat runs and they then re-install when the root.bat runs.
I have yet been able to root this phone successfully.
I did get the error to not show at one point after I ran the unroot.bat. I installed SuperSU v2.79 via adb cmd prompt, and then opened the app. It then gave me the SU binary needs to be updated error, which it fails at doing.
I really do not want to reset the phone as I'm not even sure that would solve anything as it didn't work the first time from stock.
I have read that there is TWRP working for the S7 but i cant tell if it's for the US version or not, I didn't look into it very deeply.
Does anyone have any advice?
Click to expand...
Click to collapse
The TWRP is not for S7 T-mobile sm-g930t, becouse it has the bootloader locked, and no way to unlock it.

Somebody found a way to unlock bootloader on verizon s7, can it waork also with a t-mobile version???
Thanks

pippone121263 said:
Somebody found a way to unlock bootloader on verizon s7, can it waork also with a t-mobile version???
Thanks
Click to expand...
Click to collapse
Pics or it didn't happen. JK but really though where'd you see that? That's very exciting!

pippone121263 said:
Somebody found a way to unlock bootloader on verizon s7, can it waork also with a t-mobile version???
Thanks
Click to expand...
Click to collapse
I highly doubt this...
There's a lot of people who get confused with carrier unlocks and bootloader unlocks. If you know what you are talking about and aren't confused please share a link or pictures.

Was this ever resolved? I'm having the exact same problem. Even tried flashing back to prior firmware. No success.

penn263 said:
Was this ever resolved? I'm having the exact same problem. Even tried flashing back to prior firmware. No success.
Click to expand...
Click to collapse
Use the latest root script and binary...

KillerClaw321 said:
Use the latest root script and binary...
Click to expand...
Click to collapse
I used Nougat_S7_Root_2_82_All_Carriers_V1.zip like the OP. No success because it's saying SU binary occupied. Isn't that the latest?

penn263 said:
I used Nougat_S7_Root_2_82_All_Carriers_V1.zip like the OP. No success because it's saying SU binary occupied. Isn't that the latest?
Click to expand...
Click to collapse
Did you by any chance try installing tinysu?

penn263 said:
Was this ever resolved? I'm having the exact same problem. Even tried flashing back to prior firmware. No success.
Click to expand...
Click to collapse
Yes, this was resolved by flashing back to stock and attempting root again through the exact same method.

Themes / Apps / Mods Magisk

I'm going to attempt to get magisk up and running on my brand new Moto Edge (berlna), and maybe twrp if i can manage the device port and build. i will document the trial and error drama here, success or failure. wish me luck

first thing we need is the current firmware. pulling that down from moto RSA
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
edit:
1. boot.img successfully patched by magisk,
2. fastboot flash boot magisk_patched_boot.img completed successfully.
3. root obtained, w00t!

tom.etc said:
I'm going to attempt to get magisk up and running on my brand new Moto Edge (berlna), and maybe twrp if i can manage the device port and build. i will document the trial and error drama here, success or failure. wish me luck
Click to expand...
Click to collapse
I have attempted and succeeded to root the phone through magisk by the magisk APK boot.img way ...
Root holds works well...
Any news from anybody on TWRP for "Berlna"?
I have tried TWRP for "Racer"and other variants...
She no work for this "girl" ..
But it's new and I just thought I'd post the question regardless thanks everybody for your time!

XT2141-2 Berlina here. How did you unlock bootloader before flashing patched boot.img? Thanks.
NVM its the standard procedure for moto phones, sorry!

yeah, i haven't had time to dig into TWRP for myself, but i'd love to. let me know if someone manages it before me please!

tom.etc said:
first thing we need is the current firmware. pulling that down from moto RSA
View attachment 5443919
edit:
1. boot.img successfully patched by magisk,
2. fastboot flash boot magisk_patched_boot.img completed successfully.
3. root obtained, w00t!
Click to expand...
Click to collapse
Would you be able to post a short guide on how you accomplished this root without using TWRP for the Berlna/where you found the files to patch with Magisk? I recently picked up this phone and would love to root it myself, but any tutorials I've found use TWRP to install Magisk on the phone.
Thanks!

curtissimo said:
Would you be able to post a short guide on how you accomplished this root without using TWRP for the Berlna/where you found the files to patch with Magisk? I recently picked up this phone and would love to root it myself, but any tutorials I've found use TWRP to install Magisk on the phone.
Thanks!
Click to expand...
Click to collapse
It is exactly the same process for patching any other device with an unlocked bootloader without using TWRP.
1) Download device image from Motorola,
2) Extract boot.img from firmware file,
3) Use another device with Magisk to patch the extracted boot.img file within the Magisk App,
4) Unlock the bootloader on the device to be flashed,
5) Flash modified boot.img file in Fastboot mode.

For a long time i thought i was the only edge 2021 owner! Nice seeing you guys here and thanks for your efforts.

Just out of curiosity, can anyone verify that tap to pay, secured apps(banking mostly) and all the normal OS functions will continue to work as usual? I haven't had a rooted phone in ages, I might see what's changed since.

tap to pay i only figured out last night. forgive me for being sleep deprived and rambling a bit, i ended up pulling an all nighter o_0
itsfitts said:
Just out of curiosity, can anyone verify that tap to pay, secured apps(banking mostly) and all the normal OS functions will continue to work as usual? I haven't had a rooted phone in ages, I might see what's changed since.
Click to expand...
Click to collapse
standard disclaimer:
IF YOU READ PAST HERE, YOU ARE DOING SO AT YOUR OWN RISK, AND IF YOU END UP WITH A BRICK THAT'S ON YOU, NOT ME.
i know this list of stuff installed resulted in my phone working with magisk, riru, lsposed, viper and gravitybox AND passes the whole shebang regarding safety net while they're running.. after clearing the user data and cache to the play store app, the play store shows my device is certified, as well.
*****************************************************************************************************************
you had better know what you're doing or be prepared to have to deal with data loss as we don't have twrp to save us. use great care. if the unexpected happens, you'll be running the lenovo phone rescue tool
*****************************************************************************************************************
you need (some subset of the following, i haven't completely nailed down what the critical minimum is, but i know this combo is working for me.):
1. Magisk, with the following modules:
Magisk Hide Props Config
in the thread here on XDA for the module above, there is a reference to "safetynet-fix-2.1.3.zip" in one of the replies, (use search in the thread) follow the link, you need that.
EDIT: see here: https://github.com/Magisk-Modules-R.../master/README.md#force-basic-key-attestation
you also need Riru along with it's modules:
Sui
(i installed this, but dunno if necessary or not) enhanced mode for storage isolation (as well as the companion app "storage isolation" on the author of Riru's site in the downloads section
(i installed this, but dunno if necessary or not) IFW-Enhance
(i installed this, but dunno if necessary or not) Location Report Enabler
(i installed this, but dunno if necessary or not) Clipboard Whitelist
(i installed this, but dunno if necessary or not) LSPosed 1.6.5
some time around 5am the above ensemble got my berlna to pass safetynet basic and cts profile, and was able to add a card to the gpay app
bonus time: i was also able to get the magisk module for installing Viper4AndroidFX working (hint, use "legacy mode" in the settings) as well as the xPosed mod GravityBox[R] (which also works for me, atleast in rearranging the QS tile layout <3 )
sadly, my notes died when there was a power outage this morning so i will need to review my work if you want the details, but here's some screen shots. i've included what might be superfluous hides from within Sui, but this is what is currently working as i sip this pepsi i just bought with my phone.

Finally came back to this thread, got sidetracked on wanting to root my phone for a bit. But I got it rooted successfully, am using CF.lumen for a real blue light filter experience that isn't an overlay, and am very happy!
Thanks everyone for the help

I am not sure should I root it.
The main concern is Widevine L1.
I rooted many Motorola phones and I don't think this one is an exception

I've been having an tiny issue with step 4, unlocking the bootloader. The website is trying to say my phone is not "eligible for unlock". Only a small speed bump as far as I'm concerned, because I know someone here on XDA has a way around this!
Anyone? ..........."crickets*

Gregbmil1 said:
I've been having an tiny issue with step 4, unlocking the bootloader. The website is trying to say my phone is not "eligible for unlock". Only a small speed bump as far as I'm concerned, because I know someone here on XDA has a way around this!
Anyone? ..........."crickets*
Click to expand...
Click to collapse
If your phone is a carrier bought model, then you won't be able to unlock it.
If you bought it unlocked (not from a carrier or a carrier store) and the website won't give you a token, then you'll need to contact Lenovo for support, possibly an exchange.

twelfth said:
If your phone is a carrier bought model, then you won't be able to unlock it.
If you bought it unlocked (not from a carrier or a carrier store) and the website won't give you a token, then you'll need to contact Lenovo for support, possibly an exchange.
Click to expand...
Click to collapse
Yeah, from Verizon

Gregbmil1 said:
Yeah, from Verizon
Click to expand...
Click to collapse
You're boned. Sorry bud. If you ever want to be able to unlock the bootloader of a device, never buy it directly from the carrier or get a carrier branded device via resale. Most of the time you can order an unlocked device from Motorola directly and use it on verizon, just need to swap the simcard.

I wouldn't say that it cant be unlocked if it is a carrier edition. More accurately, Verizon specifically makes an issue of this. I don't think I've ever had a Verizon phone I could unlock, especially Samsung.
Is your phone paid-in-full? There's a possibility its ineligible because of this.
If rooting isn't an option, you can still accomplish a lot via other means. I've been playing around a lot with the Shizuku API myself.

I was looking for information on TWRP for the XT2141-2 if anyone has any. I'm looking at flashing an Android 12 GSI and wanted TWRP available as a backup if things went south

twelfth said:
You're boned. Sorry bud. If you ever want to be able to unlock the bootloader of a device, never buy it directly from the carrier or get a carrier branded device via resale. Most of the time you can order an unlocked device from Motorola directly and use it on verizon, just need to swap the simcard.
Click to expand...
Click to collapse
Thanks, I'm going to be looking into a different phone. Having root is important to me. I had a rooted Note 10 with an unlocked bootloader. I thought i drove away with it laying on to of the bed cover if my truck. So i got the Motorola edge. Hours later i found my Note 10, with a dead battery under a dresser just barly enough to not be able to see it when standing. Just my luck.
At least i have a rooted phone still even if it has no service anymore

tom.etc said:
tap to pay i only figured out last night. forgive me for being sleep deprived and rambling a bit, i ended up pulling an all nighter o_0
standard disclaimer:
IF YOU READ PAST HERE, YOU ARE DOING SO AT YOUR OWN RISK, AND IF YOU END UP WITH A BRICK THAT'S ON YOU, NOT ME.
i know this list of stuff installed resulted in my phone working with magisk, riru, lsposed, viper and gravitybox AND passes the whole shebang regarding safety net while they're running.. after clearing the user data and cache to the play store app, the play store shows my device is certified, as well.
*****************************************************************************************************************
you had better know what you're doing or be prepared to have to deal with data loss as we don't have twrp to save us. use great care. if the unexpected happens, you'll be running the lenovo phone rescue tool
*****************************************************************************************************************
you need (some subset of the following, i haven't completely nailed down what the critical minimum is, but i know this combo is working for me.):
1. Magisk, with the following modules:
Magisk Hide Props Config
in the thread here on XDA for the module above, there is a reference to "safetynet-fix-2.1.3.zip" in one of the replies, (use search in the thread) follow the link, you need that.
EDIT: see here: https://github.com/Magisk-Modules-R.../master/README.md#force-basic-key-attestation
you also need Riru along with it's modules:
Sui
(i installed this, but dunno if necessary or not) enhanced mode for storage isolation (as well as the companion app "storage isolation" on the author of Riru's site in the downloads section
(i installed this, but dunno if necessary or not) IFW-Enhance
(i installed this, but dunno if necessary or not) Location Report Enabler
(i installed this, but dunno if necessary or not) Clipboard Whitelist
(i installed this, but dunno if necessary or not) LSPosed 1.6.5
some time around 5am the above ensemble got my berlna to pass safetynet basic and cts profile, and was able to add a card to the gpay app
bonus time: i was also able to get the magisk module for installing Viper4AndroidFX working (hint, use "legacy mode" in the settings) as well as the xPosed mod GravityBox[R] (which also works for me, atleast in rearranging the QS tile layout <3 )
sadly, my notes died when there was a power outage this morning so i will need to review my work if you want the details, but here's some screen shots. i've included what might be superfluous hides from within Sui, but this is what is currently working as i sip this pepsi i just bought with my phone.
Click to expand...
Click to collapse
Hey bro I have a question, is there a possible way to get the firmware for edge 2021 12 (S1RMS32.48-18-11-2-3) (WITHOUT A PC) I unlocked my bootloader but I can't get the boot.img anywhere so I came here for help.