Related
There are how-tos from 2012 about using Voodoo to store root access (like squirrels storing their nuts for the winter) but is there a better way now? ... Am I wrong in anticipating a problem here?
9.18.94.XT926.Verizon.en.US with saferoot
Thanks
I wouldn't take the OTA until someone figures out a way to root the OTA, and that doesn't look very promising. Honestly, I don't think Voodoo will help out here, either.
RikRong said:
I wouldn't take the OTA until someone figures out a way to root the OTA, and that doesn't look very promising. Honestly, I don't think Voodoo will help out here, either.
Click to expand...
Click to collapse
Guess I could educate myself about how Saferoot works, but ... I'm still learning Java! Will be a while before I know how things _really_ work.
Thanks
From the play store:
{
"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"
}
For the unlocked fellows and fellowettes out there, it's as simple as 1) unrooting, 2) taking OTA, and 3) flashing SuperSU in TWRP / CWM to regain root access, correct?
LifeAsADroid said:
For the unlocked fellows and fellowettes out there, it's as simple as 1) unrooting, 2) taking OTA, and 3) flashing SuperSU in TWRP / CWM to regain root access, correct?
Click to expand...
Click to collapse
As long as you haven't frozen or removed any other system apps, then yes. I usually just do a clean wipe and install with RSD Lite since I remove all kinds of crap when I use stock.
And yeah, you can always flash SuperSU in recovery if your bootloader is unlocked.
/e: On second thought, take that first sentence with a grain of salt. I realized I've never actually taken an OTA the traditional way with a custom recovery installed. It seems like that wouldn't work properly.
killrhythm09 said:
As long as you haven't frozen or removed any other system apps, then yes. I usually just do a clean wipe and install with RSD Lite since I remove all kinds of crap when I use stock.
And yeah, you can always flash SuperSU in recovery if your bootloader is unlocked.
/e: On second thought, take that first sentence with a grain of salt. I realized I've never actually taken an OTA the traditional way with a custom recovery installed. It seems like that wouldn't work properly.
Click to expand...
Click to collapse
Holy cow, I am thanking you all over the place tonight! Such great useful information you have! I was wondering if you wouldn't mind explaining in a little more detail what you mean by "clean wipe and install with RSD Lite". I have a feeling I may or may not have deleted something important along the way. I know I have frozen things in TiBu (which I can defrost, update, and re-freeze or finally delete since this will be our last update from Motorola), and I don't think I have deleted any of the system files as of yet, but I am pretty certain I have modified system files (changing things in SystemUI, etc) for certain mods.
In case the modded files forbid me from taking the OTA, could you explain a little about how you clean wipe and install with RSD Lite?
After final install of KitKat (by whichever method), if I have clean wiped, I'll lose my photos, messages, etc, yes? Is there a way to save that stuff? TiBu backup of the "text messaging" app or the "gallery" app perhaps?
I promise you I am not thread-stalking you around XDA, but thanks again for all your time tonight!
RSD Lite is a software tool you install on your PC to flash Motorola phones in fastboot. If you ever see an fxz package (which I think stands for fastboot xml zip) they can be used by RSD Lite to basically restore your phone to stock. They usually come with a file with different sections that you can comment or uncomment if you only want to flash specific partitions (i.e. only the modem, or just the kernel).
There's probably a better solution for backing up, but I just use TiBu and then copy everything off my internal storage & SD onto my PC temporarily, then copy it back after. I do it so infrequently that I haven't bothered to figure out a better way, sorry.
/e: Meant to include this site, since it has lots of different firmware releases that you can use with RSD Lite:
http://sbf.droid-developers.org/phone.php?device=5
If you have any other questions, let me know.
LifeAsADroid said:
For the unlocked fellows and fellowettes out there, it's as simple as 1) unrooting, 2) taking OTA, and 3) flashing SuperSU in TWRP / CWM to regain root access, correct?
Click to expand...
Click to collapse
1.5) flash stock from custom recovery.
Note m recovery is in my button goodies. I think hd & m share the same img. Check the md5.
---------- Post added at 09:44 AM ---------- Previous post was at 09:42 AM ----------
Voodoo root keeper will work for easy unroot but not for keeping root beyond 4.2.
I personally won't take the update until sometime figures out a way to have root in kit kat.
LifeAsADroid said:
In case the modded files forbid me from taking the OTA, could you explain a little about how you clean wipe and install with RSD Lite?
Click to expand...
Click to collapse
The best solution is to use SamuriHL's House of Moto tools. You must read, read again, and read one more time before installing and using the tool. Once it's set up correctly, it is very easy to use. You can get it here -> http://www.droidrzr.com/index.php/topic/28162-house-of-moto-20-for-now/
Read the OP in the thread first. Again, read it and then once more, as he states. The instructions are all there, but you have to read through them entirely before you attempt to use the tools.
I use this all the time when I'm ready to flash back to stock after being on a custom ROM when a new OTA comes out.
I use Titanium Backup to backup all my apps and data to my external SD card.
I use Backup to Gmail app to backup my call log, sms and mms messages so I can restore them later.
I backup my contacts and such to Google as well.
I use Listables to generate a list of the apps I had installed. I have so many that I sometimes forget which ones I used.
After that, I use HoM to flash back to stock and then reinistall TiBu to restore my apps.
Then, I use HoM to flash back the custom recovery (TWRP in my case) and flash root back onto my device (I'm unlocked so I don't have to use an exploit).
However, it would be best to hold off on root if you are wanting to obtain the OTA, unless of course you are using a locked device. Then, you might want to hold off until it's determined if there is a root exploit that will work.
Even though I'm unlocked, I'm going to wait and make sure they don't find a way to relock it. I don't believe they can since it was a physical change in the device (blown fuse - can't unblow it - is that a real word?)
That's it.
My capasitive back, home and recent apps buttons has stopped working so I would like to have the on screen buttons as I do on my Nexus 10.
I tried to root the device to be able to modify the /system/build.props file. I used the superboot method but that din't work as I have S-ON. I then continued trying to install CM 10.2, and in the process, when installing CWM recovery, that asked If I wanted to root and I did. I then booted back in to the stock ROM now with root but after changing the build.props file it just reverted after reboot. I then continued to flash the CM10.2 and gapps for 4.3, but the device fails to boot... Now I have reverted to backup and use the button savior, but I don't like it...
I suspect that trying to flash this superboot messed up something... ? On one of the start up screens I have a disclaimer in red about HTC development software which came up after I tried to flash that...
{
"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"
}
Can anybody help me?
Having root does not grant you automatically rights to modify system files. For altering build.prop you should have mount /system partition in R/W mode before trying to edit the file. Even if you have root, /system is read only so you cannot save changes. You could mount system as R/W either by ADB commands issuing the following from command prompt:
su
adb shell mount -o rw, remount /system
Or by mounting system R/W from the root file Explorer you're using
Sent from nowhere over the air...
I used root explorer to alter the file, and before edit i clicked the mount r+w button. I read somewhere that on-screen buttons does not work on HTC sense anyways, so I may have to install CM or an other rom... I tried to flash just the CM10.2 an not the gapps now, but it fails to boot. The HTC splash screen comes up, the screen goes black, the splash comes, goes black, and so it goes...
I forgot to flash the boot.img... inside the zip
buestad said:
I forgot to flash the boot.img... inside the zip
Click to expand...
Click to collapse
Although this is for another HTC model, the basic idea should get you started again.
http://htc-one.wonderhowto.com/how-to/fix-soft-bricked-htc-one-by-flashing-new-rom-via-adb-0154361/
I Guess that when i tried the superboot, that did something to my kernel. Inside the .bat file it actually flashes the boot (isn't that the kernel?)
Cyanogenmod also has a note in the install procedure which I initialy didn't do:
Note:
This device, if unlocked with HTCDev Unlock, must have its kernel flashed via fastboot. Extract boot.img from the CyanogenMod .zip package and flash it from the bootloader with: fastboot flash boot boot.img
Click to expand...
Click to collapse
So I flashed the boot.img inside the Cyanogenmod .zip first, than I wiped and installed the Cyanogenmod .zip from the CWM recovery. I ended up using the M7 snapshot of CM11, and that worked! I then flashed gapps for Android 4.4.
After everything was up and running I edited the /system/build.props using root explorer (I mounted /system as r+w inside root explorer) adding the line qemu.hw.mainkeys=0, rebooted and got the softkeys!
So what happens if you flash TWRP as the link says?
808phone said:
So what happens if you flash TWRP as the link says?
Click to expand...
Click to collapse
I din't use TWRP. I used CWM Touch 6.0.4.8.
I probably could just flashed the boot.img after the device didn't boot, but I reverted to backup, and started over and started with the boot flash...
buestad said:
I din't use TWRP. I used CWM Touch 6.0.4.8.
I probably could just flashed the boot.img after the device didn't boot, but I reverted to backup, and started over and started with the boot flash...
Click to expand...
Click to collapse
Can you get to the boot loader menu?
You can still flash TWRP on there and follow the instructions. If you really want CWM afterwards, simply flash CWM back on. I would try the link since it is talking about stopping your boot loop.
808phone said:
Can you get to the boot loader menu?
You can still flash TWRP on there and follow the instructions. If you really want CWM afterwards, simply flash CWM back on. I would try the link since it is talking about stopping your boot loop.
Click to expand...
Click to collapse
As I said: I'm OK! Flashing the boot.img from inside the zip did the trick. Everything is working like a charm now.
buestad said:
As I said: I'm OK! Flashing the boot.img from inside the zip did the trick. Everything is working like a charm now.
Click to expand...
Click to collapse
Oh OK! Great you got it going.
Unlocking, rooting, relocking and unrooting simplified! (and much more!)
VERSION 2.1.4 - This program will automatically bring together all the files you need to unlock and root your device in a few clicks, or flash it back to stock and re-lock it. You can also use this program to backup/restore all your important data, flash zips, set file permissions, push and pull files, install apps, generate logcats/bugreports, and much more! With the included file association options, you can perform tasks like flashing zips, installing apps, restoring android backup files, and flashing/booting img files with just a double click! The program includes a full featured interface for automating tasks in TWRP, enhanced restore features, an in-built auto-updater/notification system, ‘any build’ mode, advanced restore features,’NRT- Live Log’ for viewing the adb/fastboot cmds that are run in the background, quick tools utilities, and tools for taking screenshots/screen-recordings. All the latest official Android builds and Nexus devices are supported. The program intelligently and selectively downloads the files it needs for your device and makes sure you are using the latest files available. The program can even auto-detect your device and build. This release brings full Marshmallow root support plus all automated features by utilizing a new system that no longer requires modified boot.imgs. Check out the updated changelog for a more comprehensive breakdown of the feature set and changes in this release.
~ my goal for this project is make the entire process as smooth and simple as possible ~
{
"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"
}
Please read the FAQs before posting questions: http://www.wugfresh.com/nrt/faqs/
Looking for a walk-through? >> Excellent Instructional/How-To Videos: http://www.wugfresh.com/videos/
More information & Download Links: http://www.wugfresh.com/nrt/
Changelog: http://www.wugfresh.com/nrt/changelog/
Enjoy! ^_^
{{ WugFresh }}
Reserved
*I am big fan of this device. Looking forward to using it as my daily driver, and very happy to extend NRT support*
just added to index
[INDEX] LG NEXUS 5X Resources Compilation Roll-Up
Nice to see you here WugFresh!
Good to see you, glad you've joined us :thumbup:
Hi! Very nice to see you here! You're always been my backup when I screw up something in the past with my nexus devices. I'm know I can always get back to stock with NRT
Verstuurd vanaf mijn Nexus 5X met Tapatalk
@WugFresh
Love your NRT on the Nmmexus 6. Glad you're here. Makes life a lot easier
I couldn't install busybox as mentioned in the instructions provided for "rooting", it's the last step (confirmation for root). It prompted me to change installation directory but system/bin doesn't work as well. And i can't boot recovery as well after the whole rooting process. It just shows me a dead android there
edit: i may have download stock recovery as well, as prompted by your toolkit after rooting.
#2 edit: reflashed twrp to solve my problems, but you may want to mention something to prevent something like that from happening again. Or maybe i'm just dumb
#3 edit: so sorry, it seems that the busybox provided was outdated, update it from playstore and installation will be good to go
imadiu said:
I couldn't install busybox as mentioned in the instructions provided for "rooting", it's the last step (confirmation for root). It prompted me to change installation directory but system/bin doesn't work as well. And i can't boot recovery as well after the whole rooting process. It just shows me a dead android there
edit: i may have download stock recovery as well, as prompted by your toolkit after rooting.
#2 edit: reflashed twrp to solve my problems, but you may want to mention something to prevent something like that from happening again. Or maybe i'm just dumb
#3 edit: so sorry, it seems that the busybox provided was outdated, update it from playstore and installation will be good to go
Click to expand...
Click to collapse
I am having BusyBox issues also.
mmartenn said:
I am having BusyBox issues also.
Click to expand...
Click to collapse
If you tried to install busybox right after you root your phone, as what the Root toolkit tells you to, it will not work like mine. That's because it's outdated. So just go to play store and update that app first before you reinstall any other app. I presume you rooted your device right after you unlock your bootloader which factory resets your device.
I have issue gaining write access to /system, busybox can't install to system/bin or system/xbin, had to install busybox through recovery.
also no /system write access through adb shell, it says system file read only
coolineho said:
I have issue gaining write access to /system, busybox can't install to system/bin or system/xbin, had to install busybox through recovery.
also no /system write access through adb shell, it says system file read only
Click to expand...
Click to collapse
Same problem here. Any solutions?
riceknight said:
Same problem here. Any solutions?
Click to expand...
Click to collapse
Not yet, still waiting ;(
I'm also facing the same issue, can't install busy box. It force closes after it fails to install. I tried updating to 124.1 but that didn't work, I also uninstalled and installed again from the playstore but that didn't work.
I also can't reboot into TWRP, unless I reboot through the NRT updater.
If I try to reboot normally without the updater, then I get the red warning message saying my phone is corrupt, followed by the green android robot with a red warning triangle coining out of it's stomach.
I'm running MDB08L
What I'm doing wrong?
Thanks
Sent from my Nexus 5X using Tapatalk
Install notes:
In options menu disable installing busybox, install busybox from play store after root process.
After root, Flashboot Flash Recovery in Advanced Utilities.
I have had no problems after using these steps.
I followed the steps above and busybox still wouldn't install so I found a 1.24.1 flashable zip flashed it and it worked . just another option to try if all others are not working
Does the "Restore: Flash Stock + Unroot" option completely wipe any trace of unlocking, rooting so that the phone could be sent to Google for repair. (I'm just asking, in case my screen breaks)
Tank87 said:
Does the "Restore: Flash Stock + Unroot" option completely wipe any trace of unlocking, rooting so that the phone could be sent to Google for repair. (I'm just asking, in case my screen breaks)
Click to expand...
Click to collapse
Yup, just did mine to send it back to google for warranty replacement of intermittent power button.
Guys here is a flashable zip. It's busybox 1.24.1 permissive. It's works 100% for me many times. If anyone wants 1.24.1 SElinux just let me know and I'll upload it
https://www.dropbox.com/s/e8tpfd4d8qcsqo5/Busybox-1.24.1.zip?dl=0
Sent from my Nexus 5X using Tapatalk
skulldreamz said:
Guys here is a flashable zip. It's busybox 1.24.1 permissive. It's works 100% for me many times. If anyone wants 1.24.1 SElinux just let me know and I'll upload it
https://www.dropbox.com/s/e8tpfd4d8qcsqo5/Busybox-1.24.1.zip?dl=0
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I just tried flashing this file (through twrp right?). It doesn't look like it worked through TWRP I got an "Updated process ended with error=1, error flashing 1.24.1.zip", and busybox is still not present on the phone when I restarted it. I tried downloading it from the play store directly and it still gives me the "it looks like it was not installed successfully" error message. Should I be flashing this file some other way? Thanks in advance!
Posting this here because it seems that @Chainfire prefers to do technical work publicly, and I think we need his help.
This is the userdebug boot image for the LG G5. I also have a flashable TOT with this in it so it it is actually usable, but I (nor anyone else that I am aware of) will provide that until we have it 100% working as we don't want any possibility or rooting someone's phone. These were both provided by tungkick, so if anyone wants to donate or give thanks they belong to her (I am just the messenger for now as her english is not very good).
The userdebug boot has root enabled by default, but the system is in read-only mode (just like how the Galaxy S7 was with its eng boot). It would be EXTREMELY helpful if someone who knows what they are talking about (i.e. Chainfire) could take a look at this and talk to tungkick through Skype or PM. We also have a Skype chat and if you would like to to contribute ways to get this to work I can add you to it
EDIT: I am adding the flashable TOT with the userdebug boot.img. If you attempt to flash this PLEASE have a backup of your data in case something goes wrong!!! I believe this should work on all variants, so please post if this works for you!
*You may brick your device, break your phone, or start a nuclear war with this. I am warning you now, please take this into consideration before you go around flashing things*
{
"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"
}
Bumping this
Although you caused us to lose the main people working towards root originally, if this works I may take back my feelings about you
Can you not run
Code:
mount -o remount,rw /system
Any news with this? I want muh roots
tabp0le said:
Can you not run
Code:
mount -o remount,rw /system
Click to expand...
Click to collapse
Doesn't work, we tried... This is why we need @Chainfire help. We think is has to do with modifying the actual SU binary
Nathamio said:
Any news with this? I want muh roots
Click to expand...
Click to collapse
Lol so do we. I promise we will keep you updated!
I just want to thank everyone who has been working on rooting our device. If I had a way to contribute I would, but sadly I do not. Keep up the good work!
I thought there was root for the G5 available already?
mkdr said:
I thought there was root for the G5 available already?
Click to expand...
Click to collapse
Only for certain models (T-Mo and H850 international in Europe). This could mean we can root all models.
I hope root will come to the H860 . C'mon @Chainfire, I'm sure you can find the key easily ^^
It's really a great phone, but I'm missing the good optimizations we can have with root...
YassGo said:
I hope root will come to the H860 . C'mon @Chainfire, I'm sure you can find the key easily ^^
It's really a great phone, but I'm missing the good optimizations we can have with root...
Click to expand...
Click to collapse
me too waiting for root. @Chainfire
please make it happen
Guys, please stop summoning him. He has been asked already.
It is actually the userdebug kernel, not eng. Fixed that.
Honestly Annoying said:
It is actually the userdebug kernel, not eng. Fixed that.
Click to expand...
Click to collapse
Ah, hmmm. Again, I might be talking out my buthole but.....
If this is a user-debug build, ADB commands that didnt work before might work now no? An enginering build would have root by default but a user debug build might have enough for you to push through & use commands that might not work on a normal build.
For example, Have you guys tried to use 'adb disable-verity' on this build? Pushing SU for root would be easy at this point no?
JF-GINO said:
Ah, hmmm. Again, I might be talking out my buthole but.....
If this is a user-debug build, ADB commands that didnt work before might work now no? An enginering build would have root by default but a user debug build might have enough for you to push through & use commands that might not work on a normal build.
For example, Have you guys tried to use 'adb disable-verity' on this build? Pushing SU for root would be easy at this point no?
Click to expand...
Click to collapse
You are 100% correct, but in order to do that we have to run the system as userdebug also.
When we put the userdebug kernel inside the userdebug TOT, it gives a bootloop. This is because on a standard user build the data is set to encrypt, while userdebug is unencrypted. Since our userdebug system is TECHNICALLY a user system (all we did is change the build.prop to userdebug), it throws a bootloop. If we can get past that then we would be good to go and everything would work, such as disabling dm-verity and then pulling that dm-verityless boot.img and pushing it regularly.
Honestly Annoying said:
You are 100% correct, but in order to do that we have to run the system as userdebug also.
When we put the userdebug kernel inside the userdebug TOT, it gives a bootloop. This is because on a standard user build the data is set to encrypt, while userdebug is unencrypted. Since our userdebug system is TECHNICALLY a user system (all we did is change the build.prop to userdebug), it throws a bootloop. If we can get past that then we would be good to go and everything would work, such as disabling dm-verity and then pulling that dm-verityless boot.img and pushing it regularly.
Click to expand...
Click to collapse
Wait,. so if the kernel already has encryption disabled,. then Im not sure where the problem is. Encription is not on the Rom level, its located in the ramdisk on of the kernel.
Maybe you should :
A) flash your TOT
b) then push your kernel
c) then 'fastboot format userdata' - wipe it,
reboot and see if it takes?
Or is there encryption or a hash check in the bootloader?
Also, what are you adding to your build.prop?
ro.secure=0
ro.debuggable=1
ro.kernel.android.checkjni=1 ??
JF-GINO said:
Wait,. so if the kernel already has encryption disabled,. then Im not sure where the problem is. Encription is not on the Rom level, its located in the ramdisk on of the kernel.
Maybe you should :
A) flash your TOT
b) then push your kernel
c) then 'fastboot format userdata' - wipe it,
reboot and see if it takes?
Or is there encryption or a hash check in the bootloader?
Also, what are you adding to your build.prop?
ro.secure=0
ro.debuggable=1
ro.kernel.android.checkjni=1 ??
Click to expand...
Click to collapse
Do you have a skype? I would like to add you to a chat we have and explain more in depth
What model are you working on? And also how did you build a TOT? I can't find it anywhere on XDA.
JF-GINO said:
Wait,. so if the kernel already has encryption disabled,. then Im not sure where the problem is. Encription is not on the Rom level, its located in the ramdisk on of the kernel.
Maybe you should :
A) flash your TOT
b) then push your kernel
c) then 'fastboot format userdata' - wipe it,
reboot and see if it takes?
Or is there encryption or a hash check in the bootloader?
Also, what are you adding to your build.prop?
ro.secure=0
ro.debuggable=1
ro.kernel.android.checkjni=1 ??
Click to expand...
Click to collapse
Bootloader checks if the further images (boot, recovery, system) are signed digitally - if not, either it won't boot, or if the BL is unlocked, it will display a quite nice warning about the system being insecure.
Encryption check is not enforced, but if encryption is disabled WHILE userdata is encrypted, it will bootloop. Your method of wiping data should work (or flashing the TOT without userdata and formatting the device).
I just received the Android 7 update.
Model XT1650-03 UNLOCKED unbranded version.
Go to the bottom of the post to download the update.zip and the TWRP flash file
{
"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"
}
BEFORE THE UPDATE
AFTER THE UPDATE
here is the update.zip
http://forum.xda-developers.com/showpost.php?p=69903354&postcount=44
https://mega.nz/#!RlckjLAB!kKTc1196PhimDtVte6OdCWF6aXSWGSNLToEkvUePymE
credits to: @Lepezon
Guys, here is the ZIP to update via TWRP,
https://mega.nz/#!wA8C3RJJ
is the backup of my entire system, it contains boot, recovery (stock) and system partitions, it's safe to flash due I made a full wipe of the system before doing this backup. Should be easy to update as a piece of cake.
Copy the uncompressed file to the root of your MicroSD card should be something like TWRP/backups
1. Reboot into TWRP
2. cancel if ask for code
3. Don't allow system modifications
4. MAKE YOUR OWN BACKUP just in case
5. Optional, erase data, always is good a fresh install
6. Go to Restore
7. Select system and boot.
8. Reboot and enjoy
Sent from my XT1650 using XDA-Developers mobile app
juliospinoza said:
I just received the Android 7 update.
Model XT1650-03 UNLOCKED unbranded version.
...
Click to expand...
Click to collapse
Nice!
If you are rooted/with TWRP installed simply don't do it...
P.S.: if you decide to install it (and all go fine... ) could you kindly boot on TWRP (not installing it, only booting to it from fastboot...) and without modifying system taking a backup of: recovery, boot, system? Thank a LOT!
If you are rooted, you can pull the OTA from your /cache and share it ^^
Bender1987 said:
If you are rooted, you can pull the OTA from your /cache and share it ^^
Click to expand...
Click to collapse
enetec said:
Nice![emoji14]
If you are rooted/with TWRP installed simply don't do it...
P.S.: if you decide to install it (and all go fine... ) could you kindly boot on TWRP (not installing it, only booting to it from fastboot...) and without modifying system taking a backup of: recovery, boot, system? Thank a LOT!
Click to expand...
Click to collapse
Sorry guys. I am completely stock. I will install TWRP later this day and drag all partitions, except recovery, of course.
Sent from my XT1650 using XDA-Developers mobile app
[Puts iPhone back in the box]
juliospinoza said:
Sorry guys. I am completely stock. I will install TWRP later this day and drag all partitions, except recovery, of course.
Click to expand...
Click to collapse
Hi Julio, listen to me... :highfive:
If you boot in TWRP *before* flashing it, you can take a full backup, included (stock) recovery!
Don't swipe to allow /system modification before taking I too... :fingers-crossed:
enetec said:
Hi Julio, listen to me... :highfive:
If you boot in TWRP *before* flashing it, you can take a full backup, included (stock) recovery!
Don't swipe to allow /system modification before taking I too... :fingers-crossed:
Click to expand...
Click to collapse
I know that man. But before the update I was fully stock.
Now I can take the partitions with root and terminals or TWRP. Your call.
Sent from my XT1650 using XDA-Developers mobile app
Unable to check for updates at present, please try again later. Stock UK, any ideas?
Sent from my XT1650 using XDA Free mobile app
HEEEELP xD, I'm on MM Stock with Turbo Kernel and the update 7.0 notification poped up. What do I do ? What happens if I update ?
-03 Dual Sim, Unlocked, Unbranded
Lepezon said:
HEEEELP xD, I'm on MM Stock with Turbo Kernel and the update 7.0 notification poped up. What do I do ? What happens if I update ?
-03 Dual Sim, Unlocked, Unbranded
Click to expand...
Click to collapse
If you've not got stock recovery it will download the OTA, reboot into custom recovery, try to flash, fail and nothing else. No damage will be caused.
Lepezon said:
HEEEELP xD, I'm on MM Stock with Turbo Kernel and the update 7.0 notification poped up. What do I do ? What happens if I update ?
-03 Dual Sim, Unlocked, Unbranded
Click to expand...
Click to collapse
nothing happens, donwload the OTA and don't install it yet, you can pull the update.zip and upload it to the community. I wasn't able because I was (and still) stock, but you can contribute to us doing that, if you need help me and my friend @enetec can guide you.
regards paisano
juliospinoza said:
nothing happens, donwload the OTA and don't install it yet, you can pull the update.zip and upload it to the community. I wasn't able because I was (and still) stock, but you can contribute to us doing that, if you need help me and my friend @enetec can guide you.
regards paisano
Click to expand...
Click to collapse
OK , Downloading now. Whats next ?
Lepezon said:
OK , Downloading now. Whats next ?
Click to expand...
Click to collapse
*you need to be root
1. Download some root explorer, like root explorer
2. Go to the root of your phone and find the cache directory
3. Hit the 'Mount R/W' in the corner (root explorer)
4. Copy the update file .zip from the ~/cache/ to your sdcard.
5. that's it, now you can take it to your computer and upload it to any server you want, like mega or drive.
please report how it went
saludos!
http://forum.xda-developers.com/showthread.php?t=2188158
juliospinoza said:
*you need to be root
1. Download some root explorer, like root explorer
2. Go to the root of your phone and find the cache directory
3. Hit the 'Mount R/W' in the corner (root explorer)
4. Copy the update file .zip from the ~/cache/ to your sdcard.
5. that's it, now you can take it to your computer and upload it to any server you want, like mega or drive.
please report how it went
saludos!
http://forum.xda-developers.com/showthread.php?t=2188158
Click to expand...
Click to collapse
For root do I need to unencrypt ? Just flash SuperSU in TWRP? Magisk & phh's SuperUser?
Lepezon said:
For root do I need to unencrypt ? Just flash SuperSU in TWRP? Magisk & phh's SuperUser?
Click to expand...
Click to collapse
Flash this version "SuperSU v.2.78" using TWRP and you will obtain root inmediatly.
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
juliospinoza said:
Flash this version "SuperSU v.2.78" using TWRP and you will obtain root inmediatly.
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Click to expand...
Click to collapse
It didn´t work
Lepezon said:
It didn´t work
Click to expand...
Click to collapse
sometimes the super su apk doesn't install automatically (beta), you need to install it manually via play store, or check with root checker.
https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=es_419 <-----supersu
https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=es_419 <---- root checker
juliospinoza said:
sometimes the super su apk doesn't install automatically (beta), you need to install it manually via play store, or check with root checker.
https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=es_419 <-----supersu
https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=es_419 <---- root checker
Click to expand...
Click to collapse
SuperSU apk says " theres no bin..."
Root check says No Root Detected
Lepezon said:
SuperSU apk says " theres no bin..."
Root check says No Root Detected
Click to expand...
Click to collapse
here is the solution...
http://forum.xda-developers.com/moto-z/how-to/moto-z-hacking-experiences-t3502409
maybe the OP could help you, seems that you will lose all you data
@enetec
juliospinoza said:
I know that man. But before the update I was fully stock.
Now I can take the partitions with root and terminals or TWRP. Your call.
Click to expand...
Click to collapse
Uhm.... I'm not sure you have well understood what I mean...
If you are still STOCK and update to Nougat, remaining STOCK yet, (only unlocked bootloader is needed I think...) and before flashing TWRP and/or obtaining root, you can boot on TWRP without flashing it.
If you do so, you can take a full stock boot, with (original) /recovery too and with untouched /boot & /system...
Was it already clear?