Related
Hello guys!
I've found the way for getting Android 4.4.4 rooted without write-protection on root filesystem
Original post on 4pda.ru Warning! Russian language detected!)
So, this is small and very simple instruction:
Preparation:1. You should be on SU2-3.3 (Blur 19.6.3) or SU2-3-15 (Blur 19.5.3) rooted and have SafeStrap installed!
2. You have never flashed SU4.21 (Blur 21.11.21) Android version 4.4.4 via RSDLite and you have never taken OTA with 4.4.4!!!
Let's do it and enjoy fully rooted 4.4.4!1 I've done 2 ZIP-files, download one, you prefer:
full rooted stock 4.4.4 SU4.21 with hosts-file ADBLOCK trick.
Download 4.4.4_full here
full rooted Debloated stock 4.4.4 SU4.21, with Touchless Control, Active Display, NFC, Wireless Monitor (inc. Cromecast)
Download 4.4.4_debloated here
Debloated ROM develompent was stopped, due to my smartphone physical damage. Im' sorry.
Regards, Dmitry.
2. Copy downloaded zip in to device storage.
3. Reboot to SafeStrap
4. Select Insall button, select ZIP, you prefer.
5. For locked bootloader: when installation will finish, reboot you device in to bootloader and flash stock kernel from SU4.21
you could take it here or from ZIP-file.
6. After flashing boot.img just reboot you smartphone and enjoy 4.4.4 with root and writable /system
For unlocked bootloader - all done, just reboot your device .
DO NOT PERFORM ANY WIPES!
If something happend with you phone, you can revert to SU2-3-15 (Blur 19.5.3) via RSDLite, get root, install SafeStrap
If you need to clean bloatware, use my Custom Recovery compatibility scripts, could be downloaded in this topic
If you found any features, you need, missing, please, pm me.
i am BL Unlocked, so no need for this for me... but if this is the case and it works then great find my man!!
Given the recent vulnerability published by Dan Rosenberg, I'm hesitant to update to 4.4.4, as it may patch this vulnerability - keeping the bootloader locked indefinitely. I would just keep this in mind if considering this update.
EDIT: Got my information wrong. The date on the OTA is before the date the vulnerability was published. 4.4.4. seems good to go in that case.
has anyone tried this yet?
Thinking about trying this - doing a backup now in Safestrap.
Would like to be able to see this...
"2. You have boot.img from SU4-21, you can download it below "
Where do you see this information? How do I know what version I have in 4.4?
rdenova said:
Thinking about trying this - doing a backup now in Safestrap.
Would like to be able to see this...
"2. You have boot.img from SU4-21, you can download it below "
Where do you see this information? How do I know what version I have in 4.4?
Click to expand...
Click to collapse
Settings>About Phone>Build number
summer.cat said:
1. You should be on SU2-3.3 rooted and have SafeStrap installed!
Click to expand...
Click to collapse
This, I see under Build Number.
summer.cat said:
2. You have boot.img from SU4-21, you can download it below
Click to expand...
Click to collapse
This, I do not see any place and is why I asked.
Wait so is this a fully write protection off?
mrwinkle said:
has anyone tried this yet?
Click to expand...
Click to collapse
Looks like this fella did...
http://forum.xda-developers.com/droid-ultra/general/update-19-5-3-obake-t2845903
ceelos218 said:
Wait so is this a fully write protection off?
Click to expand...
Click to collapse
sertainly)
PS: i've read many questions about build versions and firmware versions, so if you couldn't understand which firmware you have, follow this:
First update 4.4 - SU2.3-15 (suits for gaining root and wp off by @beaups wbegone)
Second update 4.4 - SU2.3-3
Latest update 4.4.4 - SU4.21
hope, it will be helpfull.
summer.cat said:
sertainly)
PS: i've read many questions about build versions and firmware versions, so if you couldn't understand which firmware you have, follow this:
First update 4.4 - SU2.3-15 (suits for gaining root and wp off by @beaups wbegone)
Second update 4.4 - SU2.3-3
Latest update 4.4.4 - SU4.21
hope, it will be helpfull.
Click to expand...
Click to collapse
Instead of using the SU for identifying builds, you should probably the system version number as that is more frequently used. 19.5.3, 19.6.3, 21.11.21
summer.cat said:
Hello guys!
I've found the way for getting Android 4.4.4 rooted without write-protection on root filesystem
Original post on 4pda.ru Warning! Russian language detected!)
So, this is small and very simple instruction:
Preparation:
1. You should be on SU2-3.3 rooted and have SafeStrap installed!
You have never flashed 4.4.4 via RSDLite and you have never taken OTA with 4.4.4!!!
2. You have downloaded boot.img from SU4-21
can be downloaded here https://drive.google.com/file/d/0B_kAWkXp3XK9VmpnSGNaVUZtTDQ/edit?usp=sharing
Let's do it!
1. Download 4.4.4_rooted.zip here
https://drive.google.com/file/d/0B_kAWkXp3XK9amVwNjJKUjk4QmM/edit?usp=sharing
2. Copy 4.4.4_rooted.zip in to device storage.
3. Reboot to SafeStrap
4. Select Insall button, select 4.4.4_rooted.zip
5. After flashing reboot to bootloader and flash via fastboot tools boot.img file from point 2 above
Code:
fastboot flash boot boot.img
6. Reboot after flashing boot.img
7. Enjoy 4.4.4 with root and writable /system
If something happend with you phone, you can revert to SU2-3.15 via RSDLite, get root, install SafeStrap
PS: You flashing clean from bloatware system! As clean as possible, but everything works fine!
Click to expand...
Click to collapse
....So, does this mean I can finally install some ROMs on my retail Moto? I came from a bootloader-locked 4.4 install with root.
thebenshow said:
....So, does this mean I can finally install some ROMs on my retail Moto? I came from a bootloader-locked 4.4 install with root.
Click to expand...
Click to collapse
i mean, you can use 4.4.4 without write protection
I'm about to try this out to n my xt1080 on 4.4.4... I will update when I'm finished
Can this be used for the droid mini?
I should have read closer I got too excited about about getting root... I already took 4.4.4 OTA... I need root
Am I the only one waiting for clear confirmation from someone who was rooted on 19.6.3 that did the steps in this thread that they are now on 4.4.4 with root and write protection permanently off?
BriCo84 said:
Am I the only one waiting for clear confirmation from someone who was rooted on 19.6.3 that did the steps in this thread that they are now on 4.4.4 with root and write protection permanently off?
Click to expand...
Click to collapse
I am too lol. Been refreshing this thread ever since I ran across it.
Anyone try this?
He is talking about using safestrap on a 4.4 ROM. If you EVER updated to 4.4.4, this will never work for you as you will never be able to disable write-protect to be able to install safestrap.
OP: perhaps you should make this more clear in the original post. Specifically that it will not work if you ever updated to 4.4.4 (Actually, the OP DOES say this...), AND that you're not actually running the 4.4.4 rom, but rather a 4.4.4 stock-based, safestrap-compatible ROM. If you are using this successfully, your bootloader AND your partition table are still on 4.4, which allows you to retain WP-off, safestrap, and root.
But yeah...this will absolutely work if you never updated past 4.4. We have known about this for a long time...I'm surprised a guide was just recently put out about this.
i recently update my sony xperia z2 (D6502) to andriod 6.0.1. and now i want to root my phone but i can't i use every thing but happen nothing and also my phone is not getting into recovery mode i tried like other site say close ur phone press power button + volume down few times. But - when switching on, notification lights of my phone never light up.it just shows a Sony logo . and i tried kingroot apk or pc but they didn't work..
please help me to resolve my problem
PHONE :- Z2 6502
ANDRIOD ;- 6.0.1
andriod security patch level :- 1 feb 2016
baseband version :-8974-AAAAANPZQ-00068-57
KERNEL VERSION :- 3.4.0-perf-g3189667 - [email protected]#1 thu mar 17 11:17:37 2016
build number :- 23.5.A.0.570
this is a stock. there is no root and no recovery. You have to downgrade first...(im currently looking up this same thing)
Hello.
I will help you. I have sony xperia z2 6.0.1 root + recovery. Just write me on facebook. My name is Ákos Gondor. I have grey profile picture,and sun glasses.
.
Looks like you have done very minimal research into it. Easiest way would be to use flashtool, with a .314 ftf file. Downgrade your phone and then use the various rooting tools made by DoomLord and others to root. Once you have rooted successfully, run the XZ dual recovery and then read the post on how to flash the 6.0.1 stock ROM.
This http://forum.xda-developers.com/xperia-z2/development/rom-official-6-0-1-23-5-0-486-beta-t3336770 will solve your problem
have to try kingroot apk
chax_84 said:
This http://forum.xda-developers.com/xperia-z2/development/rom-official-6-0-1-23-5-0-486-beta-t3336770 will solve your problem
Click to expand...
Click to collapse
This won't work as the OP has D6502 version of the phone and not D6503.
Is there a pre rooted flashable zip file for D6502?
SidhuZ said:
i recently update my sony xperia z2 (D6502) to andriod 6.0.1. and now i want to root my phone but i can't i use every thing but happen nothing and also my phone is not getting into recovery mode i tried like other site say close ur phone press power button + volume down few times. But - when switching on, notification lights of my phone never light up.it just shows a Sony logo . and i tried kingroot apk or pc but they didn't work..
please help me to resolve my problem
PHONE :- Z2 6502
ANDRIOD ;- 6.0.1
andriod security patch level :- 1 feb 2016
baseband version :-8974-AAAAANPZQ-00068-57
KERNEL VERSION :- 3.4.0-perf-g3189667 - [email protected]#1 thu mar 17 11:17:37 2016
build number :- 23.5.A.0.570
Click to expand...
Click to collapse
If your bootloader is unlocked do this:
Install Abciot kernel v8.1 via fastboot, extract the zip and flash the boot.img file with the command:
fastboot flash boot boot.img
http://forum.xda-developers.com/xperia-z2/orig-development/kernel-abricot-kernel-v3-t2965480
then flash supersu zip
moman2000 said:
If your bootloader is unlocked do this:
Install Abciot kernel v8.1 via fastboot, extract the zip and flash the boot.img file with the command:
fastboot flash boot boot.img
http://forum.xda-developers.com/xperia-z2/orig-development/kernel-abricot-kernel-v3-t2965480
then flash supersu zip
Click to expand...
Click to collapse
my bootloader is unlocked . install Abciot kernel v8.1 via fastboot
in recovery flash supersu but my phone not rooted
flash supersu v2.74 beta and try stable version 2.67 & 2.65 too
whats wrong ?
hamidkamrani said:
my bootloader is unlocked . install Abciot kernel v8.1 via fastboot
in recovery flash supersu but my phone not rooted
flash supersu v2.74 beta and try stable version 2.67 & 2.65 too
whats wrong ?
Click to expand...
Click to collapse
Try this first : wipe your phone to be sure there are no conflicts. Install existenz 3.5.0 rom ( everything works well),
EDIT USE THIS ROM IF YOU DO NOT WANT EXISTENZ 3.5.0: http://forum.xda-developers.com/xperia-z2/development/rom-prerooted-rom-23-5-0-575-t3383221 it also has a d6502 patch you need to flash!
(Read the whole thread)
i solved my problem by flashing this 2 files
http://forum.xda-developers.com/showpost.php?p=66941958&postcount=18
u can create prerooted rom by this 2 files
hamidkamrani said:
i solved my problem by flashing this 2 files
http://forum.xda-developers.com/showpost.php?p=66941958&postcount=18
u can create prerooted rom by this 2 files
Click to expand...
Click to collapse
I'm glad that you have fixed it!
Just unlock your bootloader, it's too easy to root afterwards.
SidhuZ said:
i recently update my sony xperia z2 (D6502) to andriod 6.0.1. and now i want to root my phone but i can't i use every thing but happen nothing and also my phone is not getting into recovery mode i tried like other site say close ur phone press power button + volume down few times. But - when switching on, notification lights of my phone never light up.it just shows a Sony logo . and i tried kingroot apk or pc but they didn't work..
please help me to resolve my problem
PHONE :- Z2 6502
ANDRIOD ;- 6.0.1
andriod security patch level :- 1 feb 2016
baseband version :-8974-AAAAANPZQ-00068-57
KERNEL VERSION :- 3.4.0-perf-g3189667 - [email protected]#1 thu mar 17 11:17:37 2016
build number :- 23.5.A.0.570
Click to expand...
Click to collapse
First I did this method:
Downgrade to KK http://goo.gl/ixE2ea
Then this(Flash M with TWRP+ROOT+Xposed):
http://goo.gl/D11cBC
Hi everyone! I'm not only new here but new to all this android world so please forgive me if I mistake any of the special terms hehe
Thing is I have a Samsung Galaxy S5 that I tried rooting and for some reason it failed, I did everything as told (well, obviously not otherwise it would have worked haha), but still failed. Even Odin said Fail when doing it.
Result: It bricked my phone.
So after the initial stroke I had (I'm sure for all of you it's sooo common but I almost had to go into intensive care when it got stucked into that loop boot XD) then I searched online some more and downloaded the appropriate firmware again and flashed it through Odin. Odin said "Fail" so I almost died in there since phones are highly expensive in here and I thought it was permanently damaged and phone got frozen on the recovery page with the downloading bar just starting. Like it didn't work, I removed the battery, put it back, turned on the phone as normal and it worked!! (Although it doesn't let me check new updates for Android as if I would be rooted even if I'm not and I can't do a factory reset either since it will go back to that never ending boot loop with some words saying: Recovery booting (in blue), Recovery is not seandroid enforcing (in red) and Set warranty bit: recovery (in yellow). Even the Root Checker app says: Sorry! Root access is not properly installed on this device.
So my question is what could be happening to it and why can't I root it? To be honest, I don't wanna risk bricking it again in order to root it unless I'm 100% sure it can be reverted in case it doesn't work cause I can't really buy a new one as they are highly expensive in here, unemployed, and I'm actually glad it worked back again lol If someone can help me I'd highy appreciate it but be warned you have to be patient and detailed on your explanations since as I said before, I'm new to this haha XD Thanks everyone again!
This is the phone info:
SM-G900F
Android 5.0 lollipop
AP: G900FXXU1POEC
CP: G900FXXU1POEC
CSC: G900FOJV1POF1
Baseband version: G900FXXU1POEC
Kernel Version: 3.4.0-4884557 [email protected] #1 Tue May 12 11:54:06 KST 2015
Build Number: LRX21T.G900FXXU1POEC
Unites Arab Emirates TRA ID: 0016333/08 TA: 00000000/00
Security Software version: MDF v1.1 Release 4 VPN v1.4 Release 3
Know Version: KNOW 2.3 Standard SDK 5.3.0 Premium SDK 2.3.0 Customization SDK 2.0.0 Container 2.3.0 IM 2.0.0 CEP 2.0.1 Enterprise Billing 1.0.0 SE for Android 2.2.1 SSO 2.1.1 TIMA 3.0 VPN 2.2.0
Hope it's understandable enough since it didn't let me post a screencap of the info cause I'm new to make it easy for you to see, if you need anything else let me know
contarino said:
Hi everyone! I'm not only new here but new to all this android world so please forgive me if I mistake any of the special terms hehe
Thing is I have a Samsung Galaxy S5 that I tried rooting and for some reason it failed, I did everything as told (well, obviously not otherwise it would have worked haha), but still failed. Even Odin said Fail when doing it.
Result: It bricked my phone.
So after the initial stroke I had (I'm sure for all of you it's sooo common but I almost had to go into intensive care when it got stucked into that loop boot XD) then I searched online some more and downloaded the appropriate firmware again and flashed it through Odin. Odin said "Fail" so I almost died in there since phones are highly expensive in here and I thought it was permanently damaged and phone got frozen on the recovery page with the downloading bar just starting. Like it didn't work, I removed the battery, put it back, turned on the phone as normal and it worked!! (Although it doesn't let me check new updates for Android as if I would be rooted even if I'm not and I can't do a factory reset either since it will go back to that never ending boot loop with some words saying: Recovery booting (in blue), Recovery is not seandroid enforcing (in red) and Set warranty bit: recovery (in yellow). Even the Root Checker app says: Sorry! Root access is not properly installed on this device.
So my question is what could be happening to it and why can't I root it? To be honest, I don't wanna risk bricking it again in order to root it unless I'm 100% sure it can be reverted in case it doesn't work cause I can't really buy a new one as they are highly expensive in here, unemployed, and I'm actually glad it worked back again lol[emoji14]If someone can help me I'd highy appreciate it but be warned you have to be patient and detailed on your explanations since as I said before, I'm new to this haha XD Thanks everyone again!
This is the phone info:
SM-G900F
Android 5.0 lollipop
AP: G900FXXU1POEC
CP: G900FXXU1POEC
CSC: G900FOJV1POF1
Baseband version: G900FXXU1POEC
Kernel Version: 3.4.0-4884557 [email protected] #1 Tue May 12 11:54:06 KST 2015
Build Number: LRX21T.G900FXXU1POEC
Unites Arab Emirates TRA ID: 0016333/08 TA: 00000000/00
Security Software version: MDF v1.1 Release 4 VPN v1.4 Release 3
Know Version: KNOW 2.3 Standard SDK 5.3.0 Premium SDK 2.3.0 Customization SDK 2.0.0 Container 2.3.0 IM 2.0.0 CEP 2.0.1 Enterprise Billing 1.0.0 SE for Android 2.2.1 SSO 2.1.1 TIMA 3.0 VPN 2.2.0
Hope it's understandable enough since it didn't let me post a screencap of the info cause I'm new to make it easy for you to see, if you need anything else let me know
Click to expand...
Click to collapse
Enlace root zip g00f
http://download.chainfire.eu/932/SuperSU/BETA-SuperSU-v2.71-20160331103524.zip
TWRP
https://dl.twrp.me/klte/
Did you flash TWRP 3.0.2.0 with Odin ?
And Did you flash the zip in the TWRP for obtain super su??
If yes, go to settings - security in your phone and check if reactivation lock is disable or enable. Is necessary that this option is deactivated for flash with Odin
Sent from my SM-G900F using XDA-Developers mobile app
So then first I should do with Odin the same but this time with the first link you sent me, right?
Nope, I never did anything with TWRP cause I don't know what is that nor how to do it hehe so then aaafter I did this first link you sent me with Odin I should do the same procedure but with the second link? No changes at all on any sertings?
But nope, I don't have super su nor any root access cause as I said it failed and thank god I could at least fixed it to get it back as before (or at least most of it hehe). Oh and btw, the private mode never worked since I got it and obviously still doesn't. Thought I would mention it just in case.
1) deactivate 'Reactivation Lock' (can be found under Security in Settings).
2) copy SuperSU zip to your device.
3) boot into download mode.
4) Odin flash TWRP 2.8.7.0 (this version is known to work) or newer.
5) DO NOT allow phone to boot, (uncheck auto reboot in odin and if necessary remove the battery as soon as the TWRP flash has completed) then.....
6) boot directly into recovery. (Vol +, Power & Home button combination)
7) flash SuperSU zip.
8) boot device as normal.
Odin v3.10.7
https://www.androidfilehost.com/?fid=24338798368260130
XDA thread for TWRP 2.8.7.0 or NEWER by Dees_Troy
http://forum.xda-developers.com/showthread.php?t=2727406
For understanding how to flash and use.
Main download website for TWRP
https://twrp.me
superSU zip v2.46 by Chainfire
http://forum.xda-developers.com/showthread.php?t=1538053
http://i.imgur.com/rVnFwJM.jpg
Thanks for your answer too one question from the bottom of my ignorance lol XD I was getting everything ready to do it and tried checking before doing anything if i could enter recovery mode but it doesn't let me now, same red, blue and yellow letters show up until i pull out the baterry and reboot it as usual. After doing all this you're suggesting, will it let me access recovery mode or still won't? Thought I'd let you know in case you had to think of another way since it wasn't letting me use that one. Thanks :*
btw, I'm sorry but I didn't understand steps 6, 7. After TWRP flash has been completed I reboot it manually instead of automatically since i had to turn that feature off and then how do i flash supersu zip in recovery mode? (Assuming it will work heheeh)
At step 6, you actually have to stop the phone booting normally to android. If necessary, you pull the battery before it (in some cases, automatically) starts to boot.
Then you use the button combination (power, home & and volume up buttons) to boot into the newly installed TWRP and use TWRP to flash the SuperSU zip (step 7) which you should already have copied to your phone (see step 2).
For info.....TWRP is a custom recovery that will have replaced the 'stock' recovery that comes bundled with the firmware.
http://i.imgur.com/rVnFwJM.jpg
Strangely in the initial update prompt (which I don't have a screenshot of unfortunately, so if someone has an XT1092 and can corroborate it would be much appreciated) it says Android 6.0.1 and not security update, but the Android version remains at 6.0 and by all accounts remains 6.0. The new emoji aren't supported either. Back in Lollipop I also got an update that says Android 5.0.2 but the version stayed at 5.0 after the update. Anyways, this update is 15MB and takes around 20 minutes to install, contrary to what Motorola says.
Also, really Motorola? MAY?! I'd be expecting you to roll out the QuadRooter (August/September) patch by now.
Hi,
thnx for the info.
Any suggestions if anyone is making update zip for twrp installation?
Regards
LK82
Hi, it downloaded the 15Mb update when I came back home. Do I lose root if I update ?
YassGo said:
Hi, it downloaded the 15Mb update when I came back home. Do I lose root if I update ?
Click to expand...
Click to collapse
I think these official updates fail if you are rooted.... but if it succeeds i don't know if you retain root.
Again the RetGB variant being overlooked apparently. Spanish version got it and British version nothing...
Do anyone have some changelog for this security update? Does it fix Bluetooth issues (sometimes not routing audio via BT when connected to Nokia car kit)?
AB__CD said:
Strangely in the initial update prompt (which I don't have a screenshot of unfortunately, so if someone has an XT1092 and can corroborate it would be much appreciated) it says Android 6.0.1 and not security update, but the Android version remains at 6.0 and by all accounts remains 6.0.
Click to expand...
Click to collapse
I was surprised and exited that there was an update to 6.0.1 for my XT1092, which would fix the bluetooth BLE issue. No screenshot unfortunately, but I clearly remember it stating "6.0.1", not just a security upgrade.
I've contacted Motorola UK support though their email (sic) contact form with below message:
Hello
This weekend I got a prompt on my phone (model XT1092) to upgrade to android 6.0.1.
I was happy about this upgrade because it solves a bug that prevented me from using bluetooth tracking devices [1].
However, after the upgrade the android version mentioned in the phone settings is still 6.0 and not "6.0.1" as expected. The only change I notice is that the "security patch" level is now May 1 2016.
Please confirm which version is actually is and/or if the specific bluetooth low-energy fix mentioned in link [1] is included.
Thanks
Click to expand...
Click to collapse
[1] URL can't link to in this forum, but search for "tileapp 6.0.1" in google
No OTA when rooted.
My MOTOX is rooted and has TWRP, so no OTA possible.
Any chance of this upgrade being downloadable somewhere alreadY?
bart.cerneels said:
I was surprised and exited that there was an update to 6.0.1 for my XT1092, which would fix the bluetooth BLE issue. No screenshot unfortunately, but I clearly remember it stating "6.0.1", not just a security upgrade.
I've contacted Motorola UK support though their email (sic) contact form with below message:
Click to expand...
Click to collapse
I can confirm that notification says "New version: 24.201.3.en.EU" and "Android 6.0.1, Marshmallow".
OK, in OP there is a screenshot with 6.0 still. So no go for BT patch I think...
Screenshot Android 6.0.1 promt
They instead labeled this as the 6.0.1 update.
I tried to inform Motorola (lenovo) about it but it seems that it didn't came through, it was pretty hilarious:
Initial mail:
Subject: Software update labeled wrong
Dear Motorola,
This morning I received an software update saying that it would update my phone to Android 6.0.1 . This was not the case, it was merely the may security update (those are important to, don't get me wrong).
Response:
Dear Customer,
Thank you for contacting Motorola.
It is an official update form the Motorola end.So please update your device.
Me:
I did perform the update on my device, that was not my question/problem.
I meant to say that the update said it was 6.0.1 but it isn't. It updates the device to a new security patch, not form 6.0 to 6.0.1. This was probably not the intention (to say that it would update to 6.0.1) and I tried to attend you on this mistake.
Second response:
Dear Customer,
Thank you for contacting Motorola.
After updating the security patch update you will receive the official update of 6.0.1
And then I gave up on the matter, it would have been pointless to go on.
sgpieter said:
They instead labeled this as the 6.0.1 update.
I tried to inform Motorola (lenovo) about it but it seems that it didn't came through, it was pretty hilarious:
Initial mail:
Subject: Software update labeled wrong
Dear Motorola,
This morning I received an software update saying that it would update my phone to Android 6.0.1 . This was not the case, it was merely the may security update (those are important to, don't get me wrong).
Response:
Dear Customer,
Thank you for contacting Motorola.
It is an official update form the Motorola end.So please update your device.
Me:
I did perform the update on my device, that was not my question/problem.
I meant to say that the update said it was 6.0.1 but it isn't. It updates the device to a new security patch, not form 6.0 to 6.0.1. This was probably not the intention (to say that it would update to 6.0.1) and I tried to attend you on this mistake.
Second response:
Dear Customer,
Thank you for contacting Motorola.
After updating the security patch update you will receive the official update of 6.0.1
And then I gave up on the matter, it would have been pointless to go on.
Click to expand...
Click to collapse
Yeah, Motorola might just as well be Chinese now.
maybe this helps someone
I got this OTA update although I had root and TWRP. But to do a successful update I had to fully unroot in SuperSU and flash the stock recovery.img and the stock boot.img.
But before unrooting I copied the automatically downloaded update file from the /cache directory to my normal download directory, so I could reach it from the stock recovery menu. Therefore you need a root file explorer.
I than flashed the OTA update manually from the stock recovery using this instructions from reddit (but had to also flash boot.img as mentioned before):
4. Reboot into the bootloader, and then reflash stock recovery (download mentioned in step 1) with the command
"fastboot flash recovery 6.0_recovery.img"
5. Then reboot into recovery. From here, it will say "no command". Hold the power button and press the volume up key, then select apply patch from SD and choose the OTA you put on your internal memory. If all your system files are stock then this should run smoothly, if not, you might get a status error 7 and it will tell you which files are not stock. If you can, try to change them, but otherwise, you would need to download the stock files for 6.0 (you can also get them on the same link I suggested to get the stock recovery in step 1) and reflash everything to stock
Click to expand...
Click to collapse
After updating and checking that everything is fine I rooted again with TRWP, SuperSU-beta and this "echo SYSTEMLESS=true>>/data/.supersu" command.
As I cannot post links, you find the original instruction I used when you click on the first link after you googled "How To Root Moto G4 on Android 6.0.1 Marshmallow androidcustomrom1"
The normal SuperSu without this SYSTEMLESS command did not work in my case.
Hope I could help somebody
JonesMuc said:
I got this OTA update although I had root and TWRP. But to do a successful update I had to fully unroot in SuperSU and flash the stock recovery.img and the stock boot.img.
But before unrooting I copied the automatically downloaded update file from the /cache directory to my normal download directory, so I could reach it from the stock recovery menu. Therefore you need a root file explorer.
I than flashed the OTA update manually from the stock recovery using this instructions from reddit (but had to also flash boot.img as mentioned before):
4. Reboot into the bootloader, and then reflash stock recovery (download mentioned in step 1) with the command
"fastboot flash recovery 6.0_recovery.img"
5. Then reboot into recovery. From here, it will say "no command". Hold the power button and press the volume up key, then select apply patch from SD and choose the OTA you put on your internal memory. If all your system files are stock then this should run smoothly, if not, you might get a status error 7 and it will tell you which files are not stock. If you can, try to change them, but otherwise, you would need to download the stock files for 6.0 (you can also get them on the same link I suggested to get the stock recovery in step 1) and reflash everything to stock
After updating and checking that everything is fine I rooted again with TRWP, SuperSU-beta and this "echo SYSTEMLESS=true>>/data/.supersu" command.
As I cannot post links, you find the original instruction I used when you click on the first link after you googled "How To Root Moto G4 on Android 6.0.1 Marshmallow androidcustomrom1"
The normal SuperSu without this SYSTEMLESS command did not work in my case.
Hope I could help somebody
Click to expand...
Click to collapse
Hi, could you possibly upload the OTA file you downloaded? Could come in handy
Thnx in advance.
Cheers
Sent from my MOTO X using XDA Labs
As I'm new to this forum I cannot post links directly:
amazon.
de/clouddrive/share/dGQUmD6a5DvQrxlmSocfHr0Pm2XgIS9gBZ9b6lZAlla
(if the link is not working, you have to add https and www)
The file is called Blur_Version.24.11.18.victara_retde.retdeall.en.DE.zip so I think It's made for an update from 24.11.18 to 24.201.3
JonesMuc said:
As I'm new to this forum I cannot post links directly:
amazon.
de/clouddrive/share/dGQUmD6a5DvQrxlmSocfHr0Pm2XgIS9gBZ9b6lZAlla
(if the link is not working, you have to add https and www)
The file is called Blur_Version.24.11.18.victara_retde.retdeall.en.DE.zip so I think It's made for an update from 24.11.18 to 24.201.3
Click to expand...
Click to collapse
Thnx m8, really appreciated:good:
Cheers
Sent from my MOTO X using XDA Labs
JonesMuc said:
I got this OTA update although I had root and TWRP. But to do a successful update I had to fully unroot in SuperSU and flash the stock recovery.img and the stock boot.img.
But before unrooting I copied the automatically downloaded update file from the /cache directory to my normal download directory, so I could reach it from the stock recovery menu. Therefore you need a root file explorer.
I than flashed the OTA update manually from the stock recovery using this instructions from reddit (but had to also flash boot.img as mentioned before):
After updating and checking that everything is fine I rooted again with TRWP, SuperSU-beta and this "echo SYSTEMLESS=true>>/data/.supersu" command.
As I cannot post links, you find the original instruction I used when you click on the first link after you googled "How To Root Moto G4 on Android 6.0.1 Marshmallow androidcustomrom1"
The normal SuperSu without this SYSTEMLESS command did not work in my case.
Hope I could help somebody
Click to expand...
Click to collapse
May you tell the name of the post after searching "How To Root Moto G4 on Android 6.0.1 Marshmallow androidcustomrom1" ?
or some clues,
smthg plz ?
I suppose this is for rooting again
I'm looking for the stock recovery.img and the stock boot.img.
May you tell what to search to obtain them plz ?
Thx
You can find the recovery.img and boot.img in any stock firmware.
I used one from this site because it had the same version as mine:
androidsage.com/2016/02/09/install-official-marshmallow-ota-for-moto-x-android-6-0-ota-capture/
When you google for "blur_version.24.11.18" (or the version you need) you will find a lot of firmwares to download.
You are right, the other post is just for rooting again, after you updated
OK, thx :good:
Don't know why it took so long for you guys in Europe, but here in Brazil we've been using the may security patch since, errr... may! Hahahaha
theoblackhawk said:
Don't know why it took so long for you guys in Europe, but here in Brazil we've been using the may security patch since, errr... may! Hahahaha
Click to expand...
Click to collapse
One word: Lenovo
Actually four words: Lenovo being an ass
Software info:
Android 8.1
Samsung Experience: 9.5
Security patch level: Aug 2018
No Treble
Build version: J727PVPU4BRH5 or J727PVPS6BSK1 for SM-J727P
Build version: J727VVRU2BRH1 for SM-J727V
Build version: J727VPPVRU2BRH1 for SM-J727VPP
Build version: J727AUCU3BRH2 for SM-J727A
Build version: J727R4TYU1BRH5 for SM-J727R4
Build version: J727TUVU3BRH3 for SM-J727T
Build version: J727T1UVU3BRH3 for SM-J727T1
I have only tested magisks on SM-J727P, When you flash it you need to format your data again and then manually patch via the magisks manager then it will work properly.
SM-J727P (Galaxy J7 Perx)
J727PVPS6BSK1 (Newer)
Full rom download:
https://www.androidfilehost.com/?fid=8889791610682942431
J727PVPU4BRH5 (Older)
Full rom download:
https://www.androidfilehost.com/?fid=1322778262904004250
4 file rom download:
https://www.androidfilehost.com/?fid=1322778262904004263
SM-J727V (Galaxy J7 V)
4 file rom download:
https://www.androidfilehost.com/?fid=1322778262904007457
SM-J727VPP (Galaxy J7 V Prepaid)
4 file rom download:
https://www.androidfilehost.com/?fid=1322778262904007456
SM-J727A (Galaxy J7 2017 AT&T)
4 file rom download:
https://www.androidfilehost.com/?fid=1322778262904007526
SM-J727R4 (Galaxy J7 2017 US Cellular)
4 file rom download:
https://www.androidfilehost.com/?fid=1322778262904007527
SM-J727T (Galaxy J7 2017 T-Mobile)
full rom download:
https://www.androidfilehost.com/?fid=1322778262904011167
SM-J727T1 (Galaxy J7 2017 MetroPCS)
4 file rom download:
https://www.androidfilehost.com/?fid=1322778262904011170
Credits: @dbreed53 for the newer J727PVPU4BSK1 firmware
this can be ported to others J7? ?
J727P update
deadman96385 said:
I have gotten the 2 available firmware packages from easy firmware, One is a full rom package and the other is a traditional 4 file package. I have uploaded both but have only tested the full rom package.
Software info:
Android 8.1
Samsung Experience: 9.5
Security patch level: Aug 2018
No Treble
Build date: Aug 23rd
I have tested magisks, When you flash it you need to format your data again and then manually patch via the magisks manager then it will work properly.
Full rom download:
https://www.androidfilehost.com/?fid=1322778262904004250
4 file rom download:
https://www.androidfilehost.com/?fid=1322778262904004263
Click to expand...
Click to collapse
can you add in a how to Root 8.1.0 for this phone for all of us ! Thank you !!
Hi,
Is there Rom also for SM -G610F .
Magisk
So I flashed it and everything is working fantastic but I still can't get root. I don't have twrp anymore and can't flash twrp over again Odin keeps say fail so how would I format data?? Sorry I'm a noob...
J727P
Shaddow313 said:
So I flashed it and everything is working fantastic but I still can't get root. I don't have twrp anymore and can't flash twrp over again Odin keeps say fail so how would I format data?? Sorry I'm a noob...
Click to expand...
Click to collapse
Use the stock recovery an do a factory reset then flash twrp !
??
peter couniaz said:
Use the stock recovery an do a factory reset then flash twrp !
Click to expand...
Click to collapse
thanks for your quick reply.
So I tried started from scratch I re-flashed the 8.1 rom file, then went in to stock recovery performed data factory reset, tried to flash twrp 3.2.1-1 using odin 3.13.1 said it work but I'm still stuck with stock recovery. So I tried flashing twrp once more and odin says operation failed...
peter couniaz said:
Use the stock recovery an do a factory reset then flash twrp !
Click to expand...
Click to collapse
Wjat is meant by recovery? Is it not flashing factory rom?
Now, I don't think I understand TWRP fully, What it does. Is it used to fix root or system problems?
Thanks
---------- Post added at 11:22 PM ---------- Previous post was at 11:00 PM ----------
peter couniaz said:
Use the stock recovery an do a factory reset then flash twrp !
Click to expand...
Click to collapse
If I flash this update, will I be able to activate the phone, I am outside Sprint and legacy carrier's network. I'm in Africa.
My phone is unusable right now, I flashed August nougat update, I couldn't go past activation screen
Help please
Added AT&T, Verizon, Verizon Prepaid, US Cellular 8.1 firmwares to OP
J727P update
deadman96385 said:
Added AT&T, Verizon, Verizon Prepaid, US Cellular 8.1 firmwares to OP
Click to expand...
Click to collapse
Ok this is what worked for me to get Root !
#1 go into stock recovery data factory reset the phone pull battery !
#2 boot download mod using Odin 3.13.1 install latest twrp make shore before flashing twrp to unlock auto reboot in odin options then flash twrp pull battery again !
#3 boot into twrp wipe data in advanced options then mount system an flash magisk 17.1 zip wipe data again an boot phone setup phone an install magisk manager open manager in popup click yes it run threw an go away after that when ever you open magisk manager the popup will there an just click no thanks ! You should have no reason to open again it should just keep granting your root app access ! Hope this works for you all !!
A note about root; Magisk 17.1 will sometimes lose root. If this happens simply reflash magisk and reboot. The devs are working on it. We aren't the only one's with this problem. There is now a magisk 17.2 canary build which is in testing to bring better support for Oreo/Pie. I've tried it and had very good success so far.
Amazing!!
peter couniaz said:
Ok this is what worked for me to get Root !
#1 go into stock recovery data factory reset the phone pull battery !
#2 boot download mod using Odin 3.13.1 install latest twrp make shore before flashing twrp to unlock auto reboot in odin options then flash twrp pull battery again !
#3 boot into twrp wipe data in advanced options then mount system an flash magisk 17.1 zip wipe data again an boot phone setup phone an install magisk manager open manager in popup click yes it run threw an go away after that when ever you open magisk manager the popup will there an just click no thanks ! You should have no reason to open again it should just keep granting your root app access ! Hope this works for you all !!
Click to expand...
Click to collapse
You sir, are awesome another successful root...
I just have a question on twrp I flashed TWRP 3.2.2-0 because I couldn't get TWRP 3.2.3-0 to work for some reason. But now if I try and make a Back-up, my Data partition is empty and won't successfully back-up.. I can't figure out what I'm doing wrong I formatted Data and flashed no-dm-verity still no luck. Any idea's??
J727P
Shaddow313 said:
You sir, are awesome another successful root...
I just have a question on twrp I flashed TWRP 3.2.2-0 because I couldn't get TWRP 3.2.3-0 to work for some reason. But now if I try and make a Back-up, my Data partition is empty and won't successfully back-up.. I can't figure out what I'm doing wrong I formatted Data and flashed no-dm-verity still no luck. Any idea's??
Click to expand...
Click to collapse
Yes I know we are still having a problem with twrp even twrp 3.2.3.0 ! PS they should be fixing soon with the next update of twrp !
Shaddow313 said:
You sir, are awesome another successful root...
I just have a question on twrp I flashed TWRP 3.2.2-0 because I couldn't get TWRP 3.2.3-0 to work for some reason. But now if I try and make a Back-up, my Data partition is empty and won't successfully back-up.. I can't figure out what I'm doing wrong I formatted Data and flashed no-dm-verity still no luck. Any idea's??
Click to expand...
Click to collapse
Currently TWRP lacks quota storage support, so it can't read the Oreo /data partition. You can remove quota storage from the fstab by using the patch found here. After flashing it TWRP will be able to mount the data partition. There are some downsides though. Disabling quota storage is slightly slower than having it on. And TWRP still won't be able to make/restore a backup unless the partition is less than 649mb in size. There were changes to the bootloader in Oreo that prevents making a backup. You'll reboot midway. TWRP 3.2.3-1 should fix this when it gets released.
J727P update
Spaceminer said:
Currently TWRP lacks quota storage support, so it can't read the Oreo /data partition. You can remove quota storage from the fstab by using the patch found here. After flashing it TWRP will be able to mount the data partition. There are some downsides though. Disabling quota storage is slightly slower than having it on. And TWRP still won't be able to make/restore a backup unless the partition is less than 649mb in size. There were changes to the bootloader in Oreo that prevents making a backup. You'll reboot midway. TWRP 3.2.3-1 should fix this when it gets released.
Click to expand...
Click to collapse
Ok has anyone tried flash empire tweaks zip V1.3 on to the 8.1.0 system yet ? Using current twrp build ?
I'll be adding T-mobile and MetroPCS firmware to op hopefully tonight
J727P update
deadman96385 said:
I'll be adding T-mobile and MetroPCS firmware to op hopefully tonight
Click to expand...
Click to collapse
Can you post the firmware for Virgin mobile an Boost ? Thank you !!
peter couniaz said:
Can you post the firmware for Virgin mobile an Boost ? Thank you !!
Click to expand...
Click to collapse
They are included in the sprint firmware
J727P update
deadman96385 said:
They are included in the sprint firmware
Click to expand...
Click to collapse
Ok thank you wasn't shore about that !
peter couniaz said:
Ok this is what worked for me to get Root !
#1 go into stock recovery data factory reset the phone pull battery !
#2 boot download mod using Odin 3.13.1 install latest twrp make shore before flashing twrp to unlock auto reboot in odin options then flash twrp pull battery again !
#3 boot into twrp wipe data in advanced options then mount system an flash magisk 17.1 zip wipe data again an boot phone setup phone an install magisk manager open manager in popup click yes it run threw an go away after that when ever you open magisk manager the popup will there an just click no thanks ! You should have no reason to open again it should just keep granting your root app access ! Hope this works for you all !!
Click to expand...
Click to collapse
Did this work on the usc variant or....