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.
Related
Official Final GingerBread RUU Released
{
"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"
}
Thunderbolt owners have been waiting a long while to get Gingerbread -- too long, considering this phone was once Verizon's flagship. We've seen several leaked builds come around, all of which experienced a variety of problems. The most recent leak seemed to be the most stable so far, but it was still chock-full of annoying little bugs.
Fortunately, we've gotten a hold of a newer build (2.11.605.5) that fixes a lot of the issues from the 605.3 build, so HTC is clearly heading in the right direction.
Here's a summed up version of what's new in this build:
• HTC Logger removed
• Voicemail notification fixed
• Front facing camera/Gtalk fixed
• MMS/SMS Fixes
• Weather syncing fixes
• ...and more
Sound good? I thought it might. Head below for download and installation instructions.
Click to expand...
Click to collapse
Installation Instructions
• After downloading it, rename it to "PG05IMG.zip"
-Note: If you're doing this from a Windows machine, make sure you don't rename the file "PG05IMG.zip.zip," as Windows hides known file extensions by default.
• Drop the file on the root of the SD Card
• Turn off your device
• Hold Volume Down + Power to reboot into the bootloader -- the file should automatically be detected and the flashing process will begin.
• Wait for your device to complete the process and reboot
Click to expand...
Click to collapse
Source
Download (RUU)
Mirror 1
Mirror 2
Mirror 3
Mirror 4
Download (Rooted/Odex)
Download (Rooted/Deodexed/Zipaligned)
I assume it's not rooted? And if not, can it be rooted w/ revolutionary?
jv
johnnyv5 said:
I assume it's not rooted? And if not, can it be rooted w/ revolutionary?
jv
Click to expand...
Click to collapse
Follow these steps to achieve root:
1) Wipe data, cache, and dalvik (this will erase all your data so backup anything before this step)
2) Download Thunderbolt_Patched_hboot.zip from XDA by Shadowmite.
3) Open Thunderbolt_Patched_hboot.zip, you should see PG05IMG.zip inside. Take PG05IMG.zip and place it in the root of your microSD card. Reboot into Hboot.
4) It should detect PG05IMG.zip. Just install it. Then delete PG05IMG.zip
5) Download full RUU (from link in the OP) and rename the file to PG05IMG.zip and place it in the root of your microSD card (will lose root and clockworkmod).
6) Reboot into HBoot (Hboot should say UNLOCKED--highlighted in pink), it should detect PG05IMG.zip, install it, then delete PG05IMG.zip.
7) Download Clockworkmod (CWR5.0.2.1)PG05IMG.zip)
8) Rename the clockworkmod download to PG05IMG.zip. Place on root of your microSD card.
9) Reboot into HBoot, it should detect PG05IMG.zip, install it, then delete PG05IMG.zip. Now you have Clockworkmod.
10) Lastly, install Superuser (su-3.0.5-efgh-signed.zip) by downloading it from here. Place the file on your microSD and install Superuser from Clockworkmod. Reboot.
You are now flashed to the latest ROM, with root access, and clockworkmod.
How could I back up my app data if I'm not rooted?
Root is important to me, but not critical. I am installing this and then I will attempt the Revolutionary root method and report back ASAP.
Wait, how do you know this is the "final" build thats being released as an OTA update... has that process already started for some?
Sorry but another dumb question, if you are already rooted with Revolutionary shouldn't it block this RUU from overwriting hboot? I have old school root and my wife's tbolt has revolution.
jv
Finally! I'm curious where this was "found" though. Any ideas on when an official OTA might come in?
So far no rollout, at least not according to http://support.verizonwireless.com/system_update/thunderbolt.html. Still says it is coming soon. Curious if this is another "test" build like 605.0 and 605.1 were or if this is the one that will roll out. The update instructions on the vz site still have the picture showing 605.3 and the size of the .3 update, so that hasn't been updated either. Guess we will see in a couple days. In any case, thanks for the drop! It'll give me something to play with in the mean time.
rajuabju said:
Wait, how do you know this is the "final" build thats being released as an OTA update... has that process already started for some?
Click to expand...
Click to collapse
My mistake I didn't mean to say final (this is not a confirmed OTA yet). I have changed the title.
johnnyv5 said:
Sorry but another dumb question, if you are already rooted with Revolutionary shouldn't it block this RUU from overwriting hboot? I have old school root and my wife's tbolt has revolution.
Click to expand...
Click to collapse
Flashing an RUU will overwrite any previous HBoot you have unless you flash the patched HBoot I provided. That HBoot will never be rewritten and will remain unlocked even after full RUU flashes. I am not sure if Revolutionary already has this HBoot incorporated or uses the unlocked/unpatched version but I would recommend to follow the steps above and flash the patched HBoot so you won't have to worry.
johnnyv5 said:
Sorry but another dumb question, if you are already rooted with Revolutionary shouldn't it block this RUU from overwriting hboot? I have old school root and my wife's tbolt has revolution.
jv
Click to expand...
Click to collapse
Yes
Sent from my ADR6400L using xda premium
New ROM works great and is easily rootable via Revolutionary method. Cheers!
system6 said:
New ROM works great and is easily rootable via Revolutionary method. Cheers!
Click to expand...
Click to collapse
so if i am rooted i can just install this rom and root with revolution? we don't have to worry about creating bricks?
kidhudi said:
so if i am rooted i can just install this rom and root with revolution? we don't have to worry about creating bricks?
Click to expand...
Click to collapse
I can't promise anything there, but it worked for me. I just downloaded the SU file and ran it in recovery.....and ROOTED AGAIN.
It was that easy.
kidhudi said:
so if i am rooted i can just install this rom and root with revolution? we don't have to worry about creating bricks?
Click to expand...
Click to collapse
Please be advised that the Revolutionary tool does not actually root your device. It only flashes the HBoot to an unlocked S-OFF version and optionally flashes Clockworkmod recovery. In order to gain root, must follow step 10 of the method I posted here: Link. After that you should be all set.
Why not wait till its deodexed ...probably by the end of the day.
open1your1eyes0 said:
Please be advised that the Revolutionary tool does not actually root your device. It only flashes the HBoot....
Click to expand...
Click to collapse
Now you're just going to confuse people !!
---------- Post added at 03:32 PM ---------- Previous post was at 03:30 PM ----------
ponyboy82 said:
Any ideas on when an official OTA might come in?
Click to expand...
Click to collapse
No one here knows (unless they work in VZW's engineering or related group). If someone posts a date, take it with a grain of salt.... How many updates have EVER been released on time ?
hallstevenson said:
Now you're just going to confuse people !!
---------- Post added at 03:32 PM ---------- Previous post was at 03:30 PM ----------
No one here knows (unless they work in VZW's engineering or related group). If someone posts a date, take it with a grain of salt.... How many updates have EVER been released on time ?
Click to expand...
Click to collapse
Very true, on both counts. Point taken. So... maybe another year or so for VZW to push this out?
ponyboy82 said:
Very true, on both counts. Point taken. So... maybe another year or so for VZW to push this out?
Click to expand...
Click to collapse
Im betting 2 weeks after ICS code is released
Any bets on if restoring data will hose it? anyone, anyone?
I have the zip file if anyone has a way for me to get it posted here for devs to get to work on it.
chetqwerty said:
I have the zip file if anyone has a way for me to get it posted here for devs to get to work on it.
Click to expand...
Click to collapse
Upload it to android file host if you have dev status but if not you can upload it to google drive or any other hosting site.
EDIT: If you can get it uploaded somewhere, I'm sure @muniz_ri wouldn't mind looking at it and since it sounds like it prevents downgrading, we may be able to make a ROM out of it using the OD5 bootloader like what was done with the VZW S4 Lollipop update.
No not a dev, uploaded it to a free service http://www.fileconvoy.com/dfl.php?id=g71d4dc928ae33b36999687091905b660934562bab don't know why eset said it was unsafe, it downloaded fine when i allowed it. so just allow its fine.
Tried another service, FileDropper for those who have a problem
http://www.filedropper.com/update_3
ESET Antivirus didn't have a problem with this one
Shotty the first release @muniz_ri LOL
This is a OC4 to OE1 update.
timeToy said:
This is a OC4 to OE1 update.
Click to expand...
Click to collapse
Someone in another thread said they took the OTA and can't downgrage back to kikkat or lollipop via odin.
Sent from my SM-G900V using XDA Free mobile app
aholeinthewor1d said:
Someone in another thread said they took the OTA and can't downgrage back to kikkat or lollipop via odin.
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
I personally have a Dev. Ed. S5, so I don't mind, as long as I don't flash the bootloader (aboot.mbn), so I am still interested in this.
It's been confirmed by muniz_ri that the qfuse counter was updated. If you update to OE1, there's no going back.
Guess i don't care about going back as long as i can have root and tether. I deleted the file from cache just have to get rid of this nagging install update message.
@Dudash
Here is the G900V_OE1_Stock_Rooted_ROM for testing.
For safety reasons it does not include any bootloader, however I expect that it will require the G900V_OD5_Bootloader in order to run.
Warning! Do not flash if you have taken the OE1 ota update and kept root. The ROM may work but there currently is no proven unbrick method, until the OE1 full .tar is available, in case something goes wrong.
Once the OE1 .tar is available we can try repackaging the NCG .tar without the bootloader as a way to downgrade/unbrick and re-root.
muniz_ri said:
@Dudash
Here is the G900V_OE1_Stock_Rooted_ROM for testing.
For safety reasons it does not include any bootloader, however I expect that it will require the G900V_OD5_Bootloader in order to run.
Warning! Do not flash if you have taken the OE1 ota update and kept root. The ROM may work but there currently is no proven unbrick method, until the OE1 full .tar is available, in case something goes wrong.
Once the OE1 .tar is available we can try repackaging the NCG .tar without the bootloader as a way to downgrade/unbrick and re-root.
Click to expand...
Click to collapse
Awesome. Downloading now.
muniz_ri said:
@Dudash
Here is the G900V_OE1_Stock_Rooted_ROM for testing.
For safety reasons it does not include any bootloader, however I expect that it will require the G900V_OD5_Bootloader in order to run.
Warning! Do not flash if you have taken the OE1 ota update and kept root. The ROM may work but there currently is no proven unbrick method, until the OE1 full .tar is available, in case something goes wrong.
Once the OE1 .tar is available we can try repackaging the NCG .tar without the bootloader as a way to downgrade/unbrick and re-root.
Click to expand...
Click to collapse
And here is a deodexed version for testing: G900V_OE1_Stock_Rooted_Deodexed_ROM
muniz_ri said:
And here is a deodexed version for testing: G900V_OE1_Stock_Rooted_Deodexed_ROM
Click to expand...
Click to collapse
I see that you say "if you've taken the ota and kept root" does that mean that you will retain root or is it hit or miss? any reports either way? also, have you done ay tweaks to this? enabled tether or anything besides deodexing? Thanks
I have a dev. ed. and it worked for me, including Advanced Calling, but I also flashed the rest of the firmware from the update file(sbl1.mbn sdi.mbn rpm.mbn and tz.mbn)
{
"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"
}
awesome, Thanks !
muniz_ri said:
@Dudash
Here is the G900V_OE1_Stock_Rooted_ROM for testing.
For safety reasons it does not include any bootloader, however I expect that it will require the G900V_OD5_Bootloader in order to run.
Warning! Do not flash if you have taken the OE1 ota update and kept root. The ROM may work but there currently is no proven unbrick method, until the OE1 full .tar is available, in case something goes wrong.
Once the OE1 .tar is available we can try repackaging the NCG .tar without the bootloader as a way to downgrade/unbrick and re-root.
Click to expand...
Click to collapse
muniz_ri said:
And here is a deodexed version for testing: G900V_OE1_Stock_Rooted_Deodexed_ROM
Click to expand...
Click to collapse
Sorry it's taken so long to reply. I was at a party when I replied and downloaded the ROMs and didn't want to test them without having my computer in case of an Odin emergency. lol.
I'll be testing them shortly.
timeToy said:
I have a dev. ed. and it worked for me, including Advanced Calling, but I also flashed the rest of the firmware from the update file(sbl1.mbn sdi.mbn rpm.mbn and tz.mbn)
awesome, Thanks !
Click to expand...
Click to collapse
Thanks, which ROM did you test or both?
muniz_ri said:
Thanks, which ROM did you test or both?
Click to expand...
Click to collapse
I tried Odexed only, I'm not necessarily interested in deodexed until Xposed is more stable in Lollipop and TW. I also modified your script to avoid wiping. All good
timeToy said:
I tried Odexed only, I'm not necessarily interested in deodexed until Xposed is more stable in Lollipop and TW
Click to expand...
Click to collapse
Thanks, created new thread for the ROM's here: http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784
---------- Post added at 11:56 PM ---------- Previous post was at 11:24 PM ----------
chetqwerty said:
I see that you say "if you've taken the ota and kept root" does that mean that you will retain root or is it hit or miss? any reports either way? also, have you done ay tweaks to this? enabled tether or anything besides deodexing? Thanks
Click to expand...
Click to collapse
After reviewing the ota zip I have confirmed that it checks for stock /bin/ddexe which is modified when a device is rooted, therefore the official OC4-to-OE1 ota will fail on all rooted devices. I have not seen an OD5-to-OE1 ota update.zip in order to review.
chetqwerty said:
Guess i don't care about going back as long as i can have root and tether. I deleted the file from cache just have to get rid of this nagging install update message.
Click to expand...
Click to collapse
Confirming, if I'm not rooted, there's no way to disable the annoying update nag? I'm on BOC4 and I can't use the phone without the stupid msg popping up!
I'm a bit of a noob, so apologies if this question has an obvious answer:
Does any of this thread mean there's now a way to downgrade or root a non-rooted OE1?
equazcion said:
I'm a bit of a noob, so apologies if this question has an obvious answer:
Does any of this thread mean there's now a way to downgrade or root a non-rooted OE1?
Click to expand...
Click to collapse
No
Hello everyone,
Here are some step by step guides for those of you who need detailed instructions for rooting and un-rooting the T-mobile LG V10.
The guides are short and to the point and are meant to be followed one after the other (STEP#1 --> STEP#2 --> STEP#3).
For the step#3 guide, you must choose one out of the three available:
UnRoot, stock, or custom MM 6.0
Guides:
Tmobile-LGV10_pre_flash_MM_6_0_requirements_STEP_1
Tmobile-LGV10_pre_flash_MM_6_0_requirements_STEP_2
Tmobile-LGV10_flash_Stock_UnRoot_MM_6_0_STEP_3 <------ If you want to just have stock MM 6.0 only (no root, use this if you want to return the phone or sell it)
Tmobile-LGV10_flash_Root_Stock_MM_6_0_STEP_3 <------ If you want to just have stock MM 6.0 with root only
Tmobile-LGV10_flash_Root_Custom_MM_6_0_STEP_3 <------ If you want to have a custom MM 6.0 ROM with root
Tmobile-LGV10_Dirty_Cow_Root_MM_6_0 <------ If you want to gain root access on your stock MM 6.0 rom using the "dirty cow" exploit
The guides will walk you through:
Downloading and Installing the necessary drivers / tools
Unlocking your bootloader
Flashing the stock .kdz file
Flashing the rooted .TOT file
Using TWRP to gain root status
I assume the following:
Your T-mobile LG V10 phone is already on MM 6.0 not lollipop
If you are on lollipop YOU MUST follow the guides below in the exact order listed:
Tmobile-LGV10_pre_flash_MM_6_0_requirements_STEP_1
Tmobile-LGV10_pre_flash_MM_6_0_requirements_STEP_2
Tmobile-LGV10_flash_Root_Stock_MM_6_0_STEP_3
(If you don't, YOU WILL brick your phone! Also, keep in mind that once you upgrade to MM 6.0 YOU WILL NOT be able to downgrade!!)
You are using a Microsoft Windows operating system (Windows 7 or above)
You understand that all data on your phone will be deleted
You understand that your warranty is now gone
You understand that YOU MUST follow the guides one after the other (1 -> 2 -> 3). If you deviate from this YOU WILL NOT be successful in rooting your phone
You understand that YOU MUST follow the steps in the guides one after the other (1 -> 2 -> 3). If you deviate from this YOU WILL NOT be successful in rooting your phone
Your phone's USB PC Connection (mode your phone is in when connected to your PC) is on Media device (MTP) mode. ADB and Fastboot commands to the device WILL NOT work if device is not on this mode
***Un-root***
If you want to "un-root" your device (go back to default stock) use the Tmobile-LGV10_flash_Stock_UnRoot_MM_6_0_STEP_3 guide.
(Keep in mind that this WILL DELETE all data on the phone)
***Fastboot device not detected issue***
Please click on the link below and follow the guide:
Manually installing Android ADB USB Driver
***Dirty Cow Exploit for Root***
I have added a new guide Tmobile-LGV10_Dirty_Cow_Root_MM_6_0 for those of you who would like to use the "Dirty Cow" exploit to gain root access
Link to download the guide (in case the guide attached to this thread is not showing): Click --> Tmobile-LGV10_Dirty_Cow_Root_MM_6_0
Using this exploit will allow you to install TWRP on your phone which allows you to install SuperSU.
Yes, this method to gain root works on the new software update H90120L as well as the older ones
You will have to first complete all of the steps in the guides listed below before attempting to use the Dirty Cow exploit.
- Tmobile-LGV10_pre_flash_MM_6_0_requirements_STEP_1
- Tmobile-LGV10_pre_flash_MM_6_0_requirements_STEP_2
Keep in mind that this exploit will eventually be patched
I am not responsible for what you do to your phone
***Disclaimer***
I take no responsibility in what you do to your phone
The step-by-step guides in this thread were made with the assumption that you will strictly follow them one after the other.
(If you don't, YOU WILL brick your phone!)
READ! READ! READ! Search this thread, read the guides one by one step by step, and pay attention to detail! Most problems have solutions, you just have to do a little homework.
If you run into an problem, verify that you have correctly completed all the steps for each guide before posting to this thread. Most problems come from guides / steps that were skipped.
Not all phones are created equal. What works for one person's phone might not work for your phone. Some phones have hardware issues
that may not arise until you attempt to circumvent security aka (root, install TWRP, etc.)
Use a laptop that is fully charged and plugged in to an outlet instead of a regular PC (unless it has a UPS attached to it) just in case you lose power during the flashing process.
(If you use a regular PC without a UPS attached to it and you lose power during the flashing process, YOU WILL brick your phone!)
I would like to thank the following people:
Tungkick
For his support
Root for both (H90120e and H90120j) <-- You are the man sir!!
Instructions on flashing and recovering from boot-loop
Anyone else I forgot to mention and or involved in allowing the rest of us to get root on our beloved LG V10 phones again. The android community is awesome!!!
Please leave a thank you if you find any of this helpful
Confirmed Root Testers:
jun19inf
guytano86
demkantor
jamiesco12
nymica
Thanks for the great write up!
Also.... first!!
Reserved... Thank you...
Sent from my LG-H901 using Tapatalk
xtremelora said:
Reserved... Thank you...
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
You guys are awesome. Now LG can kiss my asss
ok, so here is my progress
started at never been rooted stock MM
unlocked bootloader
followed all steps in this guide (and from original posts)
at TWRP screen after .tot flash i chose read only - couldnt wipe or anything (errors)
adb sideload wouldnt work either
used tungkick's recommendation
adb shell
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc
dd if=/dev/zero of=/dev/block/bootdevice/by-name/fota
reboot
then i saw this and panicked a bit
{
"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"
}
pulled battery
held volume down/power/ etc to get to recovery
still twrp
attempted to wipe... filed
just went ahead and flashed Eliminater74's latest part2
reboot
and.....
I am rooted 6.0!!
all seems to work great so far!
will report back if i find issues
XDA has the best people, big thanks to @tungkick and @Eliminater74
and anyone else who helped along the way!
If phone have boot error then still reboot can not put twrp pls flash file this:
Fix phone boot veri......fail
https://drive.google.com/file/d/0B8mSVItI_cqRMXZ6cjBpVFdGVTA/view?usp=sharing
File tot only add bootloader can unlock in fastboot .
Flash kdz 6.0> flash file tot> go to develop option > enabable oem unlock and usb debugging> adb reboot bootloader> fastboot oem unlock> phone unlock now>> flash next file tot have add twrp again> phone can put twrp ok.
jun19inf said:
Hello everyone,
I made a step by step guide on how I managed to flash my LG V10 (tmobile) using the recently released files / methods. Hopefully this guide helps. Thank you.
I would like to thank the following people:
• Eliminater74 <-- great work with his roms / files
• Tungkick <-- followed his instructions on flashing and recovering from bootloop
• Anyone else I forgot to mention and or involved in allowing the rest of us to get root on our beloved LG V10 phones again. The android community is awesome!!
Click to expand...
Click to collapse
Wow, well articulated and simple step-by-step instructions. How much do you charge per hour....we should contract you for all installs.
Is it possible to do this and still retain data? Like not wipe data in twrp, or does it automatically wipe when flashing the tot file? I've had to flash one kdz in the past 3 years and that was to upgrade to mm, it didn't wipe data though. I'm assuming it's basically the same process with the tot?
Swizzle82 said:
Is it possible to do this and still retain data? Like not wipe data in twrp, or does it automatically wipe when flashing the tot file? I've had to flash one kdz in the past 3 years and that was to upgrade to mm, it didn't wipe data though. I'm assuming it's basically the same process with the tot?
Click to expand...
Click to collapse
Just use LG Backup. When I used it it restored even my side loaded apps.
This method requires a wipe so it will erase everything.
Double0EK said:
Just use LG Backup. When I used it it restored even my side loaded apps.
This method requires a wipe so it will erase everything.
Click to expand...
Click to collapse
That's normally what I do, but it's not so much apps as my concern as it is all my tedious settings.. Lol.. Thanks for the info..
Is this for 6.0? I got the phone with 6.0 so is it safe to root with this?
Sent from my LG-H901 using XDA-Developers mobile app
Jaimesco12 said:
Is this for 6.0? I got the phone with 6.0 so is it safe to root with this?
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
Exactly what this is for.
Swizzle82 said:
Exactly what this is for.
Click to expand...
Click to collapse
Awesome about to attempt this will report back.
Sent from my LG-H901 using XDA-Developers mobile app
Jaimesco12 said:
Awesome about to attempt this will report back.
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
Guys make sure you unlock the bootloader first
http://forum.xda-developers.com/tmobile-lg-v10/general/t-mobile-bootloader-factory-unlocked-t3236224
otherwise it wouldn't work.
---------- Post added at 07:18 AM ---------- Previous post was at 07:16 AM ----------
guytano86 said:
Guys make sure you unlock the bootloader first
http://forum.xda-developers.com/tmobile-lg-v10/general/t-mobile-bootloader-factory-unlocked-t3236224
otherwise it wouldn't work.
Click to expand...
Click to collapse
Im rooted now Yay!!!
Another confirmed!!
Thank you
jaysonic88 said:
Wow, well articulated and simple step-by-step instructions. How much do you charge per hour....we should contract you for all installs.
Click to expand...
Click to collapse
Wanted to make sure it was easy to follow. Thank you.
The only problem I have with this is that I'm going up north after work tomorrow and won't have time until Tuesday to root. ?
But seriously, great write up! And thanks for taking the time to make it simple!
Sent from my LG-H901 using Tapatalk
Can anyone confirm which version of Supersu is installed via this method and if it installs systemless? TY
Worked for me ! Now rooted!
Sent from my LG-H901 using XDA-Developers mobile app
I can't say thank you enough I missed root/recovery so much!
Sent from my LG-H901 using XDA-Developers mobile app
The latest root method for the Samsung Galaxy S7/S7E (AT&T/T-Mobile/Verizon/Sprint)
Does not void warranty and also does not trip the KNOX counter.
In order to remove root (un-root) you can flash the original firmware in Odin.
Also to answer any further questions the root does work on the latest T-Mobile update for the S7
(G930TUVU3APG1).
This root works on all Marshmallow versions on Android on the T-Mobile S7
{
"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"
}
method
Can you provide us a link to the method that you used to root the device. Also will you make a video tutorial for rooting the sm-g930t?
dantehalo said:
Can you provide us a link to the method that you used to root the device. Also will you make a video tutorial for rooting the sm-g930t?
Click to expand...
Click to collapse
Yes I am planning to make a video tutorial.
Also I used the method provided here (this is Max Lee's website)
And for now here is great video tutorial (also created by Max Lee) The Video
So, this works? I'm reading a lot of comments on the page you linked saying that users are having bootloop issues and issues across the board... Nothing I read in the comments section suggested ANYONE got this to work flawlessly. Are you on the T-Mobile variant of the S7? If so, can you post a video of your phone, with clear root and explain in depth your step by step procedure? I literally just got this phone and don't want to **** up a phone I'm paying on.
Thanks a bunch! All the files are downloaded and ready to go on my PC. Just waiting to confirm this will work.
revulv said:
So, this works? I'm reading a lot of comments on the page you linked saying that users are having bootloop issues and issues across the board... Nothing I read in the comments section suggested ANYONE got this to work flawlessly. Are you on the T-Mobile variant of the S7? If so, can you post a video of your phone, with clear root and explain in depth your step by step procedure? I literally just got this phone and don't want to **** up a phone I'm paying on.
Thanks a bunch! All the files are downloaded and ready to go on my PC. Just waiting to confirm this will work.
Click to expand...
Click to collapse
I apologize for replying so late ... Ive been busy. But this does work 100%, only a backup is required(before root because root will most likely put you in a bootloop and you have to factory reset after)... Hopefully my video will be out before July 30. But, before you root I also want you to be aware that the root uses an eng kernal which is not meant for daily use and causes lag, but you can optimize the phone to work as it did when it was stock.
Month later
Hi KillerClaw,
So it's been a month since your last post. Is this still preferred root for this device? My device encrypted storage upon setup wizard, don't know if i hit something or it did on own. Should I unencrypt before attempting root?
Thank you!
KillerClaw321 said:
I apologize for replying so late ... Ive been busy. But this does work 100%, only a backup is required(before root because root will most likely put you in a bootloop and you have to factory reset after)... Hopefully my video will be out before July 30. But, before you root I also want you to be aware that the root uses an eng kernal which is not meant for daily use and causes lag, but you can optimize the phone to work as it did when it was stock.
Click to expand...
Click to collapse
djdubyah said:
Hi KillerClaw,
So it's been a month since your last post. Is this still preferred root for this device? My device encrypted storage upon setup wizard, don't know if i hit something or it did on own. Should I unencrypt before attempting root?
Thank you!
Click to expand...
Click to collapse
It is the only root method so far. It is not required but you can unencrypt before rooting. Rooting while already encrypted won't cause any harm since /data is encrypted not /system . But I still recommend unencrypting so you don't run into any issues.
Does this work for the latest November 1st update APK1?
Hello, I too would like to know if this is still the current root method and if there have been any changes?
GeorgeNYer and kimber1982: The short answer is "no".
I did try this on my phone, and it acted like it worked (I could get the unlocked padlock with "custom") but I could never actually grant anything root access. That was when it was usable. The first round didn't get stuck in a bootloop. After I figured out that I didn't have root, I wiped the phone and started again, and again didn't get a boot loop, but did a factory reset anyway. After that point, it was too laggy to even try to use. I fought with it for a couple of hours trying to figure out a work around, but got fed up and DLed the APK1 stock firmware from Sammobile, and Odin'd the phone back to stock.
This is the first time I've used an non hacked phone since my iPhone 3G way back when. It feels really weird.
i cant root my sm9307
KillerClaw321 said:
The latest root method for the Samsung Galaxy S7/S7E (AT&T/T-Mobile/Verizon/Sprint)
Does not void warranty and also does not trip the KNOX counter.
In order to remove root (un-root) you can flash the original firmware in Odin.
Also to answer any further questions the root does work on the latest T-Mobile update for the S7
(G930TUVU3APG1).
Click to expand...
Click to collapse
i cant find any evidence that its even possible to root sm930t if there is somebody who can let me in on this big secret please indulge me
seattlestexan said:
GeorgeNYer and kimber1982: The short answer is "no".
I did try this on my phone, and it acted like it worked (I could get the unlocked padlock with "custom") but I could never actually grant anything root access. That was when it was usable. The first round didn't get stuck in a bootloop. After I figured out that I didn't have root, I wiped the phone and started again, and again didn't get a boot loop, but did a factory reset anyway. After that point, it was too laggy to even try to use. I fought with it for a couple of hours trying to figure out a work around, but got fed up and DLed the APK1 stock firmware from Sammobile, and Odin'd the phone back to stock.
This is the first time I've used an non hacked phone since my iPhone 3G way back when. It feels really weird.
Click to expand...
Click to collapse
Did the attempt trip your Knox counter?
GeorgeNYer said:
Did the attempt trip your Knox counter?
Click to expand...
Click to collapse
No, no Knox flags. Technically the engineer boot is official, even if done in a not so official way. Once I flashed back to stock APK1, it looks like it did right out of the box.
Sadly enough.
seattlestexan said:
No, no Knox flags. Technically the engineer boot is official, even if done in a not so official way. Once I flashed back to stock APK1, it looks like it did right out of the box.
Sadly enough.
Click to expand...
Click to collapse
Did you try everything in the video though?
https://youtu.be/GNInTlCpv8E
Sent from my SM-G930T using Tapatalk
---------- Post added at 09:55 PM ---------- Previous post was at 09:52 PM ----------
GeorgeNYer said:
Did you try everything in the video though?
https://youtu.be/GNInTlCpv8E
Sent from my SM-G930T using Tapatalk
Click to expand...
Click to collapse
I would try it myself but I'd hate to start over from scratch, I just wanna know if you tried all that is in the video, if not then I would try
Sent from my SM-G930T using Tapatalk
GeorgeNYer said:
Did you try everything in the video though?
https://youtu.be/GNInTlCpv8E
Sent from my SM-G930T using Tapatalk
Click to expand...
Click to collapse
What I listed is what I was able to do. I'm not certain it ever had root access. When it showed "custom" at boot, I couldn't grant anything root access. When it acted more laggy, like was described, the lag was so bad, it wasn't usable. Mind you, these instructions were written prior to the APK1 firmware that was on my G930T from new.
jveewee said:
i cant find any evidence that its even possible to root sm930t if there is somebody who can let me in on this big secret please indulge me
Click to expand...
Click to collapse
It's smg930t, just search smg930t root max lee
I can confirm that this method does indeed work. You need to be careful and follow the instructions, but it will root your device. You may notice lag after rooting. Just install a kernel tool and set it to on-demand.
troby86 said:
I can confirm that this method does indeed work. You need to be careful and follow the instructions, but it will root your device. You may notice lag after rooting. Just install a kernel tool and set it to on-demand.
Click to expand...
Click to collapse
And Knox counter wasn't tripped??
GeorgeNYer said:
And Knox counter wasn't tripped??
Click to expand...
Click to collapse
Nope.
Just got an alert from Oxygen Updater (I was checking it earlier to see if the update was available yet and it wasn't but I guess it is now lol)
{
"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 am not sure I really want to try it since that would involve flashing away from StagOS but I may try it later. Have a date I'm getting ready for at the moment so not a good time to mess with it lol.
I have a global op9 and rolled back to A11. Guessing I probably need to be on at least C-48 to get new C-61 build. Only 48 available ota or oxygen updater ?
mattie_49 said:
I have a global op9 and rolled back to A11. Guessing I probably need to be on at least C-48 to get new C-61 build. Only 48 available ota or oxygen updater ?
Click to expand...
Click to collapse
Since it's an incremental build you would have to be on C.48. Also, Oxygen Updater won't show it if you are rooted and don't deny it root access.
EtherealRemnant said:
Since it's an incremental build you would have to be on C.48. Also, Oxygen Updater won't show it if you are rooted and don't deny it root access.
Click to expand...
Click to collapse
It's a really nice build. Many small things I couldn't hardly deal with are getting fixed. Ability to deny privilges or disable main system apps is available now. Clear all recents works properly. Misaligned home screen clock. It's nice bud. Outta try it out.
mattie_49 said:
It's a really nice build. Many small things I couldn't hardly deal with are getting fixed. Ability to deny privilges or disable main system apps is available now. Clear all recents works properly. Misaligned home screen clock. It's nice bud. Outta try it out.
Click to expand...
Click to collapse
Until I can disable their SoC throttling without performance mode draining my battery, I'll never be happy with stock unfortunately. It's literally the biggest complaint I have with OOS12.
Glad that they are finally improving it though.
EtherealRemnant said:
Until I can disable their SoC throttling without performance mode draining my battery, I'll never be happy with stock unfortunately. It's literally the biggest complaint I have with OOS12.
Glad that they are finally improving it though.
Click to expand...
Click to collapse
Did they fix SoC throttling issue in C.61? How is performance and smoothness compare to C.48.
break.cold said:
Did they fix SoC throttling issue in C.61? How is performance and smoothness compare to C.48.
Click to expand...
Click to collapse
I highly doubt they fixed it because their official stance is that it's not broken and to use performance mode.
EtherealRemnant said:
I highly doubt they fixed it because their official stance is that it's not broken and to use performance mode.
Click to expand...
Click to collapse
I have no idea what Oneplus is doing with their software, it has become so crumbled that doubt have raised in user mind before using it. I really enjoyed OOS11 alot but since OOS12 released with bugs here and there, I really don't to stay on OOS12, however, I only used because of camera
I'm rooted on LE2115_11_C.48
When I try to install (with the plan of retaining root via step 4 of the OP here: https://forum.xda-developers.com/t/...apply-root-to-the-phone.4263811/post-84858863) I just get an error "Couldn't Update Installation Problem".
The "try again" button does the same thing.
Thoughts? Anyone else rooted able to update?
arebelspy said:
I'm rooted on LE2115_11_C.48
When I try to install (with the plan of retaining root via step 4 of the OP here: https://forum.xda-developers.com/t/...apply-root-to-the-phone.4263811/post-84858863) I just get an error "Couldn't Update Installation Problem".
The "try again" button does the same thing.
Thoughts? Anyone else rooted able to update?
Click to expand...
Click to collapse
arebelspy said:
I'm rooted on LE2115_11_C.48
When I try to install (with the plan of retaining root via step 4 of the OP here: https://forum.xda-developers.com/t/...apply-root-to-the-phone.4263811/post-84858863) I just get an error "Couldn't Update Installation Problem".
The "try again" button does the same thing.
Thoughts? Anyone else rooted able to update?
Click to expand...
Click to collapse
You need to restore original boot.img through magisk app and then do OTA update or use local update method by download the OTA zip file (check ot method 2 on how to root in xda oneplus 9 form) and then updating it through Oneplus 12 local update app.
break.cold said:
I have no idea what Oneplus is doing with their software, it has become so crumbled that doubt have raised in user mind before using it. I really enjoyed OOS11 alot but since OOS12 released with bugs here and there, I really don't to stay on OOS12, however, I only used because of camera
Click to expand...
Click to collapse
Yeah this was my first OnePlus and it may well be my last because of the throttling. It really irks me. Like they go so far as to make it impossible to actually disable in OOS12.
arebelspy said:
I'm rooted on LE2115_11_C.48
When I try to install (with the plan of retaining root via step 4 of the OP here: https://forum.xda-developers.com/t/...apply-root-to-the-phone.4263811/post-84858863) I just get an error "Couldn't Update Installation Problem".
The "try again" button does the same thing.
Thoughts? Anyone else rooted able to update?
Click to expand...
Click to collapse
Open Magisk, hit uninstall, hit restore images. Install the OTA and before rebooting, install to inactive slot.
arebelspy said:
I'm rooted on LE2115_11_C.48
When I try to install (with the plan of retaining root via step 4 of the OP here: https://forum.xda-developers.com/t/...apply-root-to-the-phone.4263811/post-84858863) I just get an error "Couldn't Update Installation Problem".
The "try again" button does the same thing.
Thoughts? Anyone else rooted able to update?
Click to expand...
Click to collapse
First off it's a Google ota. If any partitions are modified the intended update will fail. Go into magisk . In red uninstall magisk. Then restore images. Let that finish and don't reboot. Go into system updates and start ota. Will now work stock boot image there. Allow update to completely install. Don't reboot. Then go into magisk again like second photo. Install to inactive. Now reboot after this process . Reboot into new oos with root . Gl
Haha, thanks for the replies all! So quick
I'll reread them all a few times to wrap my head around.
Am I going to have any data loss?
arebelspy said:
Haha, thanks for the replies all! So quick
I'll reread them all a few times to wrap my head around.
Am I going to have any data loss?
Click to expand...
Click to collapse
No
EtherealRemnant said:
Open Magisk, hit uninstall, hit restore images.
Click to expand...
Click to collapse
mattie_49 said:
Go into magisk . In red uninstall magisk. Then restore images.
Click to expand...
Click to collapse
"Stock backup does not exist."
Have I already f'd up?
arebelspy said:
"Stock backup does not exist."
Have I already f'd up?
Click to expand...
Click to collapse
If you don't have a stock backup, it's not that big of a deal. Uninstall Magisk and install the OTA.Take the clean C.61 boot image and copy to the phone, open Magisk, patch, copy to PC, fastboot boot patched image, open Magisk again, direct install.
mattie_49 said:
First off it's a Google ota. If any partitions are modified the intended update will fail. Go into magisk . In red uninstall magisk. Then restore images. Let that finish and don't reboot. Go into system updates and start ota. Will now work stock boot image there. Allow update to completely install. Don't reboot. Then go into magisk again like second photo. Install to inactive. Now reboot after this process . Reboot into new oos with root . Gl
Click to expand...
Click to collapse
for me it says that backup was not found when hitting restore images. so i suppose u need to have a backup for this to work
Vladgabriel3 said:
for me it says that backup was not found when hitting restore images. so i suppose u need to have a backup for this to work
Click to expand...
Click to collapse
EtherealRemnant said:
If you don't have a stock backup, it's not that big of a deal. Uninstall Magisk and install the OTA.Take the clean C.61 boot image and copy to the phone, open Magisk, patch, copy to PC, fastboot boot patched image, open Magisk again, direct install.
Click to expand...
Click to collapse
even if u fully uninstall magisk when u press install ota it will say failed or something like that.