Database Info

[4.4 ROOT] SlapMyMoto 1.0 (Works with MotoWPNoMo)

My apologies for taking so long, life is hectic. This is a "root path" for the 4.4 update, and in this case you will retain your stock recovery so features like remote wipe will continue to work. It requires you downgrading to 4.2.2 or already be on 4.2.2 before updating to 4.4.
First you must use MotoWPNoMo, if you haven't then you will need to. Use RockMyMoto to gain root, then use MotoWPNoMo, and then restore to the 4.2.2 Camera update.
SlapMyMoto requires you to be on the 4.2.2 Camera update, you can find the firmware for your device below:
ATT- http://sbf.droid-developers.org/download.php?device=0&file=22
Verizon - http://sbf.droid-developers.org/download.php?device=0&file=55
Step1)
Unzip SlapMyMoto-1,0.zip and push the jar file to your internal storage
Code:
adb push SlapMyMoto.jar /sdcard/SlapMyMoto.jar
Step2)
Use http://www.cydiaimpactor.com/ to open up a telnet session as system user on port 2222. We covered how to use Impactor and telnet in the RockMyMoto root, I won't be covering it again since this post is going to be long enough already, see here -> http://forum.xda-developers.com/showthread.php?t=2509590 or http://rootzwiki.com/topic/107098-root-rockmymoto-yes-even-the-first-ota/
Connecting over telnet, and run Stage1 with this command:
Code:
dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto
When the device tells you to reboot, do this manually with "adb reboot" or your power button. It will not auto reboot on this step
Step3)
Once the device has rebooted, run Impactor again and connect over telnet just like in the previous step, then run the same command
Code:
dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto
Once the device has rebooted, please take the 4.4 OTA.
Step4)
Now that we are on 4.4, we can finish the process with adb shell:
Code:
adb shell
cp /sdcard/install.sh /data/local/tmp/install.sh
chmod 755 /data/local/tmp/install.sh
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
Then either wait, or toggle your bluetooth. Once the device reboots, you will have root.

{
"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"
}
After taking the 4.4 OTA in step 3, if you then take on the 4.4.2 OTA update afterwards, the write protection off will be reverted and /system/ will once again be locked. There is no known way at this time to reverse this for users with locked bootloaders.
If you are on 4.2.x, you will be prompted for the 4.4 OTA update before getting the 4.4.2 OTA. You should complete step 4 before deciding to take on the 4.4.2 OTA or not.
Other relivent quotes from jcase:
jcase said:
XxSinisteRxX said:
The only thing i didn't understand was the "restore to 4.2.2 camera update" part, and [...] i'm already on 4.2.2.
Click to expand...
Click to collapse
[...]you skipped a step...
Rooted devices rarely handle OTAs very well, especially if they do not have a recovery anymore. Restore to [stock], and continue.
Click to expand...
Click to collapse
^(From another thread, but a comon question in this one)^
jcase said:
_litz said:
Quoting from Step 3: "Once the device has rebooted, please take the 4.4 OTA."
So what happens if the only OTA available is 4.4.2?
Click to expand...
Click to collapse
The device is not rooted at the step when you are taking the 4.4 OTA. The 4.4 update.zip is available from other sources and can be sideloaded in recovery.
Click to expand...
Click to collapse
_litz said:
FYI, for Verizon, I believe I've found the 4.4 update zip here :
http://downloadandroidfiles.org/download-blur_version-139-15-1-ghost_verizon-verizon-en-us-zip/
Click to expand...
Click to collapse
Possible mirror, not verified: magnet:?xt=urn:btih:CDARPSOTRY7CO4EY6K6SNWVASPBPX46S
jcase said:
_litz said:
Ok ... so what if you use the 0.5c method, where you replace the recovery with the customized boot image, that enabled write protection?
Click to expand...
Click to collapse
You can't boot a customized image.
_litz said:
Will that method work for 4.4.2 when it comes along?
Click to expand...
Click to collapse
No it won't work in 4.4.2, nor will it work with the 4.4 bootloaders.
Click to expand...
Click to collapse
jcase said:
lulajardim said:
I know you stated before that you have no intention on developing new root methods for the Moto X.
But is there any chance you have reconsidered and decided to take a look on 4.4.2?
Click to expand...
Click to collapse
No time, sorry.
No one mentions custom bootloader.
I am aware 0.5c works, but it has it's own flaws hence no longer beign available. Don't take OTAs with root, it is not a smart move.
JC
Click to expand...
Click to collapse
jcase said:
aviwdoowks said:
[What is] the benefit gained by this procedure.
Click to expand...
Click to collapse
Starting with the MotoX, Motorola started applying low level write protection to parts of the flash memory (in this case just /system). Root alone does not give us the ability to modify anything in system. My original hackjob that we used to bypass this has been fixed in Android 4.4. This is required if you want to actually install su into the /system partition.
Click to expand...
Click to collapse
jcase said:
tacitus54 said:
What happened to the flashing recovery.img, before taking the update to 4.4 and then flashing the 4.2.2 bootloader.
Click to expand...
Click to collapse
Previously we were using my workaround to write to system, now we are using MotoWPNoMo to gain write to system, as it is a better solution. No more recovery hackery needed.
Click to expand...
Click to collapse
Note: I will be reviewing threads and duplicating posts here to ease others finding them. PM me if you feel you have been misquoted or have something I missed.

You are the MAN!!! Amazing work!

Says he won't release a root method for 4.4, has to deal with whiny, entitled people that think he's selfish for doing so, and still ends up releasing something. Now that's what I call a class act.

i just went from 6 to midnight. damn, i love this community. now just need xposed for 4.4 and all will be right in the world.

10$ sent to you sir.
Thank you!

freak4dell said:
Says he won't release a root method for 4.4, has to deal with whiny, entitled people that think he's selfish for doing so, and still ends up releasing something. Now that's what I call a class act.
Click to expand...
Click to collapse
Actually, i didn't really release a new exploit, and I won't be. This is the same primary exploits as motoroot/rockmymoto/pwnmymoto, just instead of installing su, it plants a "backdoor". Since they allowed us to downgrade, we were able to do this.

jcase said:
Actually, i didn't really release a new exploit, and I won't be. This is the same primary exploits as motoroot/rockmymoto/pwnmymoto, just instead of installing su, it plants a "backdoor". Since they allowed us to downgrade, we were able to do this.
Click to expand...
Click to collapse
True, but a method is a method, in my eyes.
I gotta wonder if Motorola left the ability to downgrade as somewhat of a subtle way of making up to the community for not being able to unlock the AT&T and Verizon versions. They're just too good at making secure bootloaders to make me think that it was just overlooked.

Thank You!!!

Thank you for all the great and hard work you do for everyone in the consumer motox community.
I will not whine or nag, I will wait patiently until it is complete and ready. I don't have as much time for testing and tinkering like in the droidx days.
So again, jcase, thank you thank you!
Sent from my XT1060 using Tapatalk

wifi tethering
This is awesome news, however, does anyone know if wifi tethering works on 4.4? I've heard that it's broken on kk.

Thanks jcase! Rooting vzw on 4.4 worked great!

If I did these steps correctly, should I see the following message when opening SuperSU:
"There is no SU binary installed, and SuperSU cannot install it. This is a problem!"

Do you mean gpt.bin and logo.bin? Those are only ones in the camera OTA. I really should have checked before pushing the setup.sh, cause now I just boot to fastboot and don't wanna flash the wrong thing.

Sinderan said:
Do you mean gpt.bin and logo.bin? Those are only ones in the camera OTA. I really should have checked before pushing the setup.sh, cause now I just boot to fastboot and don't wanna flash the wrong thing.
Click to expand...
Click to collapse
From the 4.2.2 camera firmware, I clarified in OP now.

jcase said:
From the 4.2.2 camera firmware, I clarified in OP now.
Click to expand...
Click to collapse
Ok, I thought so, but the .mismatched extensions made me a little nervous to flash.

Awesome! Can't test it yet though, as I am in Canada on Rogers and we haven't gotten the update yet. It's still a relief knowing that I can get root when I get the update though. Thanks!

goose71 said:
This is awesome news, however, does anyone know if wifi tethering works on 4.4? I've heard that it's broken on kk.
Click to expand...
Click to collapse
can anyone confirm this?

@jcase, i know we're waiting for an update/fix for the reboot recovery issue, but i thought i'd mention that step 5 didn't work as described for me:
Step 5)
adb push recovery.sh /data/local/tmp/setup.sh
adb reboot
(It will reboot, then quickly reboot straight to the bootloader)
Click to expand...
Click to collapse
the last part didn't happen. after pushing the recovery.sh file (to data local as setup.sh), then doing an adb reboot, the phone never automatically reboots to the bootloader. maybe i'm missing something though. are we supposed to "quickly reboot" or is this supposed to happen on its own?

mercado79 said:
@jcase, i know we're waiting for an update/fix for the reboot recovery issue, but i thought i'd mention that step 5 didn't work as described for me:
the last part didn't happen. after pushing the recovery.sh file (to data local as setup.sh), then doing an adb reboot, the phone never automatically reboots to the bootloader. maybe i'm missing something though. are we supposed to "quickly reboot" or is this supposed to happen on its own?
Click to expand...
Click to collapse
It is supposed to do it automatically, but the Verizon model is missing some dependency for this method.
Jcase said he has a fix and will work on it soon, but for now, do not do this on the Verizon model. Return to 4.2.2 for now.

New AT&T OTA Update

I just got a prompt for a new OTA update, but being rooted and running a ROM I couldn't install it. It gave no new information about the update such as size or fixes. Anyone else get this? I'm on an OC3 based ROM by the way.

yea i got it

Seanbest said:
I just got a prompt for a new OTA update, but being rooted and running a ROM I couldn't install it. It gave no new information about the update such as size or fixes. Anyone else get this? I'm on an OC3 based ROM by the way.
Click to expand...
Click to collapse
It is the stage fright update
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app

Will we be able to flash it some other way?

ClearD said:
Will we be able to flash it some other way?
Click to expand...
Click to collapse
I'm sure there will be soon
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app

Well, on second thought, I just went ahead and let the update run. It completed. Everything appears normal.

I confirm, it is a fix for Stagefright. Baseband version went from I337UCUFNJ4 to I337UCUFNJ5
+ SuperSU is working properly.
Below: Before & After the update
{
"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"
}

New Update Came ..
https://www.att.com/esupport/softwareUpdateArticle.jsp?sid=KB419415&cv=820

ClearD said:
Well, on second thought, I just went ahead and let the update run. It completed. Everything appears normal.
Click to expand...
Click to collapse
Were you rooted with the Flashfire method?

Anytime AT&T or Samsung offer a "security" update FOTA, I cringe. I'm on rooted Lollipop and absolutely have to remain rooted to use Total Recall call recorder (you can't imagine how many times it's saved my ass with baseless promises from AT&T and other utility vendors), so I'm always hesitant to upgrade to any FOTA's that may make it more difficult to either flash a better ROM, or other utilities that it might block. Call me paranoid, but I'm going to hold off and try to find a better solution to threats to my OS. Belarc Security Advisor (Free) is highly respected, and a non-conventional system scan that identifies real threats. Running it yesterday and just now; show no threats. I realize that Stagefright is a threat, but I'm running antivirus software that I trust and keep my phone backed up locally on a regular basis.

billbillw said:
Were you rooted with the Flashfire method?
Click to expand...
Click to collapse
Well, I also let it run. Figured worst case, it would be rejected due to root. It ran, no errors, still on root (using Flashfire method). Stagefright detector now shows my device is safe.
---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------
nukesnooper said:
Anytime AT&T or Samsung offer a "security" update FOTA, I cringe. I'm on rooted Lollipop and absolutely have to remain rooted to use Total Recall call recorder (you can't imagine how many times it's saved my ass with baseless promises from AT&T and other utility vendors), so I'm always hesitant to upgrade to any FOTA's that may make it more difficult to either flash a better ROM, or other utilities that it might block. Call me paranoid, but I'm going to hold off and try to find a better solution to threats to my OS. Belarc Security Advisor (Free) is highly respected, and a non-conventional system scan that identifies real threats. Running it yesterday and just now; show no threats. I realize that Stagefright is a threat, but I'm running antivirus software that I trust and keep my phone backed up locally on a regular basis.
Click to expand...
Click to collapse
If you're using the Stock AT&T Lolipop, and Flashfire method for rooting, you will be OK to let the update run. It ran with no issues for me and it kept root.

billbillw said:
Well, I also let it run. Figured worst case, it would be rejected due to root. It ran, no errors, still on root (using Flashfire method). Stagefright detector now shows my device is safe.
---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------
If you're using the Stock AT&T Lolipop, and Flashfire method for rooting, you will be OK to let the update run. It ran with no issues for me and it kept root.
Click to expand...
Click to collapse
That's exactly how I did it. My only concern is that it may install patches that could further restrict future modifications.
I also just completed running Lookout and it found no threats or vulnerabilities. I'm staying where I am until I hear more feedback.
Thanks for your advice. I'll be keeping an eye on it.

It's coming in as a 280mb download, I'm going to see what happens with root (previously used Flashfire)

sim_pl said:
It's coming in as a 280mb download, I'm going to see what happens with root (previously used Flashfire)
Click to expand...
Click to collapse
Please Upload .cfg File For Update My Device .. That OTA File /cache .. Check It And Upload It Please And Check fota Folder

UPDATED POST:
I upgraded with the install stock but "keep root" method, using flashfire...
The update failed at 29%.
I did a factory reset, and it still failed at 29%...
What are my options now?
Update:
I used Flashfire to install the tethering addon... I wonder if that is the culprit.
Installing without thethering... will update with results.
And It's a pain to download that ATT update each time. --- Their servers are SLOW!

Same story here. Update stops and phone reboots about a third of the way through. Defrosted all Samsung/AT&T bloat and tried again. Same story. Bummer.

I rooted my wife's 0C3 with Kingroot and tried to take the update. It failed.
Maybe I should try again since I just used triangle away to get rid of the "custom" nag at boot.
Rockin' a l337 with Goldeneye v49.1 + Wanam Xposed and loving life on AT&T's 4G LTE network

billbillw said:
Were you rooted with the Flashfire method?
Click to expand...
Click to collapse
Yes. Rooted with flashfire, on oc3 bootloader. I ran the update through the normal OTA method, not trying to install it through flashfire. It worked fine and root stayed normal. Verified when titanium backup ran last night on its normal schedule.

Well, it updated fine, using just the straight rooted rom, no additional flashes. No more fails at 29%...
It appears that adding in anything extra, de-bloat, hotspot enable, etc. will cause the update to fail.
/sk

Reinstalled the rooted stock ROM and the update worked fine. Still have root. All is groovy.

Can CF-Auto Root G930F really do no harm instead of G930W8

Hey everyone,
Please bare with me, I haven't rooted a phone (using Chainfire's work with a custom stock rom) in over 3 years and I'm once again new at this.
Yesterday I flashed a stock rom (using Odin) to my S7 SM-G930W8 to downgrade from nougat back to Marshmallow 6.0.1 (G930W8VLU2APK3 , (carrier: Koodo), Canada). Now I want to root it (I know, I'll have to redo the whole process but while I have a fresh backup copy, why not) especially because of the software updates nagging. I haven't found any G930W8 root files, only G930F, and while some people say "Oh, just go ahead, doesn't matter", I just want further advice on if I should really use G930F even if my current model is G930W8. I don'T wanna mess anything with my carrier (like unable to place calls, or my IMEI numbers not showing up or anything uncool (yes, I know that my warranty will most probably be void but if it's "just" that, I can live with that)).
So, any advice ?

isnull said:
Hey everyone,
Please bare with me, I haven't rooted a phone (using Chainfire's work with a custom stock rom) in over 3 years and I'm once again new at this.
Yesterday I flashed a stock rom (using Odin) to my S7 SM-G930W8 to downgrade from nougat back to lollipop 6.0.1 (G930W8VLU2APK3 , (carrier: Koodo), Canada). Now I want to root it (I know, I'll have to redo the whole process but while I have a fresh backup copy, why not) especially because of the software updates nagging. I haven't found any G930W8 root files, only G930F, and while some people say "Oh, just go ahead, doesn't matter", I just want further advice on if I should really use G930F even if my current model is G930W8. I don'T wanna mess anything with my carrier (like unable to place calls, or my IMEI numbers not showing up or anything uncool (yes, I know that my warranty will most probably be void but if it's "just" that, I can live with that)).
So, any advice ?
Click to expand...
Click to collapse
Hi mate
Yes it does work in all Exynos variants
Check this confirmation from an user in Chainfire thread
https://forum.xda-developers.com/showpost.php?p=65982420&postcount=83
Just follow the steps as it was a G930F

MAX 404 said:
Hi mate
Yes it does work in all Exynos variants
Check this confirmation from an user in Chainfire thread
https://forum.xda-developers.com/showpost.php?p=65982420&postcount=83
Just follow the steps as it was a G930F
Click to expand...
Click to collapse
Hi, thanks for your quick reply !
But how do I know mine is not snapdragon and is exynos? Does W8 at the end imply it'S a exynos cpu ?

isnull said:
Hi, thanks for your quick reply !
But how do I know mine is not snapdragon and is exynos? Does W8 at the end imply it'S a exynos cpu ?
Click to expand...
Click to collapse
Hi
yes W8 model comes with a Exynos chipset......but you can always double check with an app like PhoneInfo

MAX 404 said:
Hi
yes W8 model comes with a Exynos chipset......but you can always double check with an app like PhoneInfo
Click to expand...
Click to collapse
Oh, thanks, neat little app. And yeah, exynos indeed:
screenshot

isnull said:
Oh, thanks, neat little app. And yeah, exynos indeed:
Click to expand...
Click to collapse
Great..now read.....and go for it
CF autoroot only works on MM in N you need to flash TWRP and then SuperSU-v2.79-SR3

MAX 404 said:
Great..now read.....and go for it
CF autoroot only works on MM in N you need to flash TWRP and then SuperSU-v2.79-SR3
Click to expand...
Click to collapse
1 - Did you mean only works on Marshmallow but that in Nougat you need TWRP ? (sorry to ask)
2 - Doing MM (and reinstalling MM) anyway (I just realized I had mistakenly typed "lollipop" in my opening question, I meant MM)
3 - Just downloaded "CF-Auto-Root-herolte-heroltexx-smg930f.zip", is it normal it's just 35 MB ? I was expecting something like ~2 GB, which would contain the modded (rooted) stock firmware
And yeah, I think I'll have more reading to do than I thought

isnull said:
1 - Did you mean only works on Marshmallow but that in Nougat you need TWRP ? (sorry to ask)
2 - Doing MM (and reinstalling MM) anyway (I just realized I had mistakenly typed "lollipop" in my opening question, I meant MM)
3 - Just downloaded "CF-Auto-Root-herolte-heroltexx-smg930f.zip", is it normal it's just 35 MB ? I was expecting something like ~2 GB, which would contain the modded (rooted) stock firmware
And yeah, I think I'll have more reading to do than I thought
Click to expand...
Click to collapse
Hi
1 That is right
2 I thought so...
3 Yes 35MB is about right ....is not the whole rom is only patching some modifying

MAX 404 said:
Yes 35MB is about right ....is not the whole rom is only patching some modifying
Click to expand...
Click to collapse
Oh cool, thanks! Is there any comprehensible guide here (or anywhere) for this? Like is it's just a patch if I load it in Odin's AP or BP or whatever... (not specified in Chainfire's post) ? I'm willing to read a 24 hour long paper if I need to

isnull said:
Oh cool, thanks! Is there any comprehensible guide here (or anywhere) for this? Like is it's just a patch if I load it in Odin's AP or BP or whatever... (not specified in Chainfire's post) ? I'm willing to read a 24 hour long paper if I need to
Click to expand...
Click to collapse
Ok , get your reading glasses out....
This is the official post....
https://forum.xda-developers.com/galaxy-s7/development/sm-g930-exynos-cf-auto-root-t3337353
And here the instructions for CF Autoroot
ODIN flashable devices
BASIC INSTRUCTIONS
All downloads contain .tar.md5 files flashable in ODIN as PDA.
Make sure your device is in ODIN download mode (usually you can get there by holding VolDown+Home+Power when the device is turned off), then start the included Odin3-v1.85.exe file, press the PDA button, select the .tar.md5 file, and click Start. You can find more detailed instructions and assistance at XDA.
A modified recovery and cache partition will be flashed, which will install (only) SuperSU, then clean-up the cache partition and re-flash the stock recovery.
For the root to work, the device must reboot into recovery. Most devices will do this automatically after flashing these files, but in case that does not happen, please boot into recovery manually.
UNLOCK BOOTLOADERS
If you have locked bootloaders, flashing one of these will probably brick your device - with the exception of Nexus devices, which will usually automatically "OEM unlock" and wipe your data !
Extract from here
https://autoroot.chainfire.eu/

MAX 404 said:
Ok , get your reading glasses out....
This is the official post....
https://forum.xda-developers.com/galaxy-s7/development/sm-g930-exynos-cf-auto-root-t3337353
And here the instructions for CF Autoroot
ODIN flashable devices
BASIC INSTRUCTIONS
All downloads contain .tar.md5 files flashable in ODIN as PDA.
Make sure your device is in ODIN download mode (usually you can get there by holding VolDown+Home+Power when the device is turned off), then start the included Odin3-v1.85.exe file, press the PDA button, select the .tar.md5 file, and click Start. You can find more detailed instructions and assistance at XDA.
A modified recovery and cache partition will be flashed, which will install (only) SuperSU, then clean-up the cache partition and re-flash the stock recovery.
For the root to work, the device must reboot into recovery. Most devices will do this automatically after flashing these files, but in case that does not happen, please boot into recovery manually.
UNLOCK BOOTLOADERS
If you have locked bootloaders, flashing one of these will probably brick your device - with the exception of Nexus devices, which will usually automatically "OEM unlock" and wipe your data !
Extract from here
https://autoroot.chainfire.eu/
Click to expand...
Click to collapse
Wow, thanks so much!
Quick question: once I'm flashed & rooted (when everything's been successful), can I turn off "OEM Lock" or do I leave it on?

isnull said:
Wow, thanks so much!
Quick question: once I'm flashed & rooted (when everything's been successful), can I turn off "OEM Lock" or do I leave it on?
Click to expand...
Click to collapse
Up to you mate......mine is in unlock position

MAX 404 said:
Up to you mate......mine is in unlock position
Click to expand...
Click to collapse
Oh cool, thanks. Think I'm ready now, will post a screenshot when I'm done, after re-reading a couple of things (Samsung Pay (which I don't use anyway), etc). You've been a huge help!

MAX 404 said:
Up to you mate......mine is in unlock position
Click to expand...
Click to collapse
It worked! Hell yeah. Thanks again! I'm def' gonna donate to Chainfire, this was rather easy
{
"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"
}

isnull said:
It worked! Hell yeah. Thanks again! I'm def' gonna donate to Chainfire, this was rather easy
Click to expand...
Click to collapse
Yeah he deserve it !!!
Cool mate glad for you.

@MAX 404
Is it normal when I wipe cache partition now I get a red text saying "dm-verity verification failed" ? I just Googled it and some say it's because I might have flashed an incompatible ROM before rooting but I for sure flashed a compatible one. Otherwise, does it even matter whether it says that or not?
Also, unrelated, I tried a trick to quit having software updates (firmware by Samsung) by clicking on the FotaAgent and "installing" it (doesn't actually install it, in /system/priv-apps/ (going by memory here, might be mistaken) but then I had the nagging "Unfortunately, Software Update has stopped" message a couple of times in a row on each boot or every time I turn on Wi-fi. I then tried fixing THAT by disabling DiagMonAgent through BK Disabler, but that now gives me a message (on boot up) saying "All apps associated with this action have been blocked, disabled or uninstalled". Not the end of the world but still, is there a way to end all this? I was thinking re-flashing the ROM (stock) but I'm hoping there's another solution.

Just in case someone was going to reply to this here, I moved the "Software update" question here since it's a whole other story.

isnull said:
@MAX 404
Is it normal when I wipe cache partition now I get a red text saying "dm-verity verification failed" ? I just Googled it and some say it's because I might have flashed an incompatible ROM before rooting but I for sure flashed a compatible one. Otherwise, does it even matter whether it says that or not?
Also, unrelated, I tried a trick to quit having software updates (firmware by Samsung) by clicking on the FotaAgent and "installing" it (doesn't actually install it, in /system/priv-apps/ (going by memory here, might be mistaken) but then I had the nagging "Unfortunately, Software Update has stopped" message a couple of times in a row on each boot or every time I turn on Wi-fi. I then tried fixing THAT by disabling DiagMonAgent through BK Disabler, but that now gives me a message (on boot up) saying "All apps associated with this action have been blocked, disabled or uninstalled". Not the end of the world but still, is there a way to end all this? I was thinking re-flashing the ROM (stock) but I'm hoping there's another solution.
Click to expand...
Click to collapse
Hi
Regarding Dm-Verity ,, is a message that detects that the sytem is not 100% original , is easy to solve if you have a custom recovery installed then you can flash a dm-verity and force encryption disabler zip. without a custom recovery is a little harder... but if it is not giving you any trouble let it be....
Regarding the software update issue ..no idea how to solve it , never had that problem..sorry only thing i can think of is to re flash rom...BTW once you are rooted ther will not be updates for your device....OTA check your binary status if is not original...there is no OTA

MAX 404 said:
Hi
Regarding Dm-Verity ,, is a message that detects that the sytem is not 100% original , is easy to solve if you have a custom recovery installed then you can flash a dm-verity and force encryption disabler zip. without a custom recovery is a little harder... but if it is not giving you any trouble let it be....
Regarding the software update issue ..no idea how to solve it , never had that problem..sorry only thing i can think of is to re flash rom...BTW once you are rooted ther will not be updates for your device....OTA check your binary status if is not original...there is no OTA
Click to expand...
Click to collapse
Thanks for taking the time. Oh, I see, so from what I understand the dm-verity is not really an issue. Thanks for the tip on the custom recovery. But from what you know (doesn't have to be exact), even if I have the capability (say with twrp) do I really need to flash the dm-verity & force encryption disabler? Or is it for those who are just nagged by the small text when they're in recovery mode?
It's REALLY GOOD to know about the OTA not pushing through or by push-notifications if rooted, next time I flash it (still didn't have time to get around it) I'll just root it directly after and nevermind all the steps to deactivate the firmware updates, thanks!

isnull said:
Thanks for taking the time. Oh, I see, so from what I understand the dm-verity is not really an issue. Thanks for the tip on the custom recovery. But from what you know (doesn't have to be exact), even if I have the capability (say with twrp) do I really need to flash the dm-verity & force encryption disabler? Or is it for those who are just nagged by the small text when they're in recovery mode?
It's REALLY GOOD to know about the OTA not pushing through or by push-notifications if rooted, next time I flash it (still didn't have time to get around it) I'll just root it directly after and nevermind all the steps to deactivate the firmware updates, thanks!
Click to expand...
Click to collapse
Hi mate
If your only modification to the system is just root and you do not notice any thing strange let it be do not flash dm verity zip , that error is caused by a "flag" set by the kernel as far as i know it should not be a problem , actually latest SuperSu should take care of it also

H910 January Update

My phone just received the January security update. See screenshot.
{
"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"
}
Sent from my LG-H910 using Tapatalk

haris163 said:
My phone just received the January security update. See screenshot.
Click to expand...
Click to collapse
Still 7.0......sigh...

Is it still ARB 0?

It's been giving me a real headache. I'm on stock rooted and don't want it. Downloaded automatically and resets my phone to recovery. Does some of the reset phone in 10 seconds thing. Anyone know where the ota is stored in root so I can delete it?

runningnak3d said:
Is it still ARB 0?
Click to expand...
Click to collapse
Yep. Already reset and dumped it.

Yeah it hosed my phone this morning and I had to do the dance to get to where I was.

Rooted and flashed LOS to my h910 right as I got the 10t software update notification. Got out of it. Until @runningnak3d gets ahold of 10t then.

texascbx said:
Yeah it hosed my phone this morning and I had to do the dance to get to where I was.
Click to expand...
Click to collapse
What exactly did you do? Still having to tiptoe around or it resets my phone. Even with auto update turned off.

Ryuk359 said:
What exactly did you do? Still having to tiptoe around or it resets my phone. Even with auto update turned off.
Click to expand...
Click to collapse
Use ti backup to disable the fota app and the software updater app. Should keep the notification from popping up. As for the file location it's under /cache and is the dlpkgfile. Should be about 70mb. Delete that and the stuff in the /cache/fota folder. For twrp loops manually rebooting to twrp from power off should fix it

toastyp said:
Use ti backup to disable the fota app and the software updater app. Should keep the notification from popping up. As for the file location it's under /cache and is the dlpkgfile. Should be about 70mb. Delete that and the stuff in the /cache/fota folder. For twrp loops manually rebooting to twrp from power off should fix it
Click to expand...
Click to collapse
Gotcha. I figured out the disabling in titanium. Had that done. And I wiped cache on twrp before hearing from you. There's no dlpkg in there or anything in the fota folder so that must've taken care of it. Thanks for the help sir.

If someone could get me the files from the cache and fota dirs before they wipe them, it would be appreciated. If the phone can decrypt them, then so can I -- or at least that is what I want to try.
For H910 users that are rooted, this is VERY important. When they finally release Oreo, they WILL increment ARB, and if we don't have a way to decrypt them, then no Oreo for us (and keep root).
-- Brian

Ryuk359 said:
What exactly did you do? Still having to tiptoe around or it resets my phone. Even with auto update turned off.
Click to expand...
Click to collapse
I had 10r no root but TWRP still working. So I went in and reflashed the 10r in the thread about rooting up to 10r. Then I downloaded the 10m firmware and Megarom along with the restock 1.3 kernel.
https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500

runningnak3d said:
If someone could get me the files from the cache and fota dirs before they wipe them, it would be appreciated. If the phone can decrypt them, then so can I -- or at least that is what I want to try.
For H910 users that are rooted, this is VERY important. When they finally release Oreo, they WILL increment ARB, and if we don't have a way to decrypt them, then no Oreo for us (and keep root).
-- Brian
Click to expand...
Click to collapse
Alright grabbed the entire fota folder and zipped it up. Hopefully has everything you need.
https://drive.google.com/open?id=1V8ArFzFzg6hwbeE88K5Xdw39aAjqi7Gv
Also if anyone has a link to the dumped 10t files that would be awesome to share. Looking to create a flashable zip to update myself.

If no one has posted a link to the 10t files, I will reset my H910 when I get my H918 back and dump them.
-- Brian

I use a python script to talk directly to lafd (the daemon that runs in download mode).
It is no different than using the patched LG UP, but I hate Windows

hawkeye29 said:
Rooted and flashed LOS to my h910 right as I got the 10t software update notification. Got out of it. Until @runningnak3d gets ahold of 10t then.
Click to expand...
Click to collapse
How is LOS running?

hawkeye29 said:
Rooted and flashed LOS to my h910 right as I got the 10t software update notification. Got out of it. Until @runningnak3d gets ahold of 10t then.
Click to expand...
Click to collapse
You don't have to worry about taking updates if you freeze the 2 update apps. FOTA and System Update I believe. I have the 2 frozen and haven't gotten an Ota notification for 10t.

My question is does this upgrade degrade performance? I assume this addresses spectre and meltdown vulnerabilities?
Sent from my [device_name] using XDA-Developers Legacy app

@runningnak3d I attempted to go back to full stock to update and grab us those 10t files. Don't know what happened but the full_stock 10q zip installation failed. Said reverted. tried multiple flashes and redownloads but no dice. Upon reboot I got thrown into the bootloop of corruption. Figured it was something with my custom twrp not flashing correctly so I rerooted, redownloaded and tried to flash it with twrp 3.1.1. Same thing. Zip failed and my phone got into a bootloop with the stock locked bootloader with no fastboot/recovery. Have no idea what is going on. Anyways rerooting for the second time and will not attempt that again. The whole return to stock method and dump for att updates is such a pain in the ass. Are there any reports of that full stock 10q zip failing or am I just doing something stupid?

Did you check the SHA hash?

A way to stop android 12 update after it was downloaded?

Hi, i got samsung tab s7 and it auto downloaded the update to android 12 and now it says that I can postpone it 9nly 3 times. Is there a way to get rid of it? I wouldn't be able to use the color calibrator app once it will get the update, which makes the tablet pretty useless for me. Thanks

Clear the system cache... I never tried it but was told that would clear it.

blackhawk said:
Clear the system cache... I never tried it but was told that would clear it.
Click to expand...
Click to collapse
blackhawk said:
Clear the system cache... I never tried it but was told that would clear it.
Click to expand...
Click to collapse
Thanks, I'll give it a try. How do I do a system cache clean?

sltwtr said:
Thanks, I'll give it a try. How do I do a system cache clean?
Click to expand...
Click to collapse
It's on the boot menu. Not sure for that device.
It can be a little tricky if you don't get the timing and button sequence right.
It would have been better to force power off the phone before it completed the download. Perhaps using ADB editing you could kill it. Not sure if disabling OTA updates now would stop it but that be worth a shot.
If it updates you may be able to flash it back to 11 if it doesn't upgrade the boot loader too.
You may want to see if someone has a better, more detailed plan. I always keep OTA updates package blocked. Package Disabler can be used to kill updates, that might be the easiest way.
OTA updates...
{
"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"
}

blackhawk said:
It's on the boot menu. Not sure for that device.
It can be a little tricky if you don't get the timing and button sequence right.
It would have been better to force power off the phone before it completed the download. Perhaps using ADB editing you could kill it. Not sure if disabling OTA updates now would stop it but that be worth a shot.
If it updates you may be able to flash it back to 11 if it doesn't upgrade the boot loader too.
You may want to see if someone has a better, more detailed plan. I always keep OTA updates package blocked. Package Disabler can be used to kill updates, that might be the easiest way.
OTA updates...
View attachment 5567769
Click to expand...
Click to collapse
Thank you vm. Ckearing cache didnt work, theres still a scheduled update. I thought to try and reset the tablet (its still running android 11) and not to connect it to the wifi before ill disable the auto software updates in the settings. You think it might work or is it possible that after ill reset it, it will upgrade itself?
Btw, are there any drawbacks if ill flash it back to android 11? (security-wise, warranty-wise etc')

sltwtr said:
Thank you vm. Ckearing cache didnt work, theres still a scheduled update. I thought to try and reset the tablet (its still running android 11) and not to connect it to the wifi before ill disable the auto software updates in the settings. You think it might work or is it possible that after ill reset it, it will upgrade itself?
Btw, are there any drawbacks if ill flash it back to android 11? (security-wise, warranty-wise etc')
Click to expand...
Click to collapse
Sorry that didn't work.
Try disabling the update app itself.
You can roll back to 11 as long as it doesn't update the bootloader to a new version.
No warranty implications unless you root it.
Security isn't an issue. I'm running on Pie.

blackhawk said:
Sorry that didn't work.
Try disabling the update app itself.
You can roll back to 11 as long as it doesn't update the bootloader to a new version.
No warranty implications unless you root it.
Security isn't an issue. I'm running on Pie.
Click to expand...
Click to collapse
What do you mean by disabling the app itself? What app?
How can i tell if it uploaded the bootloader?
Will i still have all the samsung features and apps?
Can you refer me to a reliable guide for downgrading?
Sorry for all the questions, thank you

sltwtr said:
What do you mean by disabling the app itself? What app?
How can i tell if it uploaded the bootloader?
Will i still have all the samsung features and apps?
Can you refer me to a reliable guide for downgrading?
Sorry for all the questions, thank you
Click to expand...
Click to collapse
My previous post shows the app in it com.wys... whatever. Install package disabler and see if that can kill the install. It probably can.
If you end up on 12... deal with that then.
I recommend you do everything you can to keep it from installing... tick-tock Mr. Wick, no time to dilly dally.

blackhawk said:
My previous post shows the app in it com.wys... whatever. Install package disabler and see if that can kill the install. It probably can.
If you end up on 12... deal with that then.
I recommend you do everything you can to keep it from installing... tick-tock Mr. Wick, no time to dilly dally.
Click to expand...
Click to collapse
I ended up doing a factory reset. I didn't connect it to wifi at first and disabled auto update in the setting. So far it seems to work. Thank you

sltwtr said:
I ended up doing a factory reset. I didn't connect it to wifi at first and disabled auto update in the setting. So far it seems to work. Thank you
Click to expand...
Click to collapse
You're welcome.
Yay. Glad you were about to kill it.
Thank you for that information about the cache fix being invalid.