Just flashed my XT1622 (UK Moto G4, NOT the plus version) using Nougat stock rom with September security patch(https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138). Thanks @tywinlannister7 who made the guide. It worked smoothly although it's in Moto G4 Plus forum.
Now, I got some questions regarding root. I did a forum search to find the post (https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918), which is quite good actually. However, I flashed my xt1622 for two reasons. The first is to upgrade to the latest system - Nougat (well, it not 'the latest' at the moment). The second is because I flashed TWRP on Marshmallow immediately after buying my Moto G4 to get root access, which stopped me to update the phone via OTA for a long time. I can still get the OTA notification, but it just won't let me update - failed after ~20 minutes. So what I did is just manually delay the update notification for 24 hours every day at 12.00pm. It bothered me a lot so I decided to go for a clean flash.
By flashing the new system, I lost some features I used quite a lot.
1. The root access for sure. I am not going to flash TWRP this time in case new patches would come over OTA again. If I flashed TWRP, I will face the same issue as I was on Marshmallow before this flashing. Is it possible to root without flashing TWRP that stops me to update over OTA?
2. I used to flash a specially made logo.bin to prevent the unlocked bootloader screen to appear. Now on Nougat, is there any similar logo.bin to do the same? A download link would be appreciated.
3. I used Llama with different profiles for some automated work such as change alarm volume at home or at workplace, make the phone ring loudly everywhere else, switch to flight mode at 12.00am at midnight and go back at 6.00am in the morning, automatically restart my phone at 1.00am while I am sleeping, and so on. This app won't work properly without root access. - well, looks like we go back to the first question of gaining root access.
Thanks for reading anyway.
Related
EDIT: phone is currently unlocked/rooted
I've had a G2 since it almost came out, i don't have nearly the time to spend on here as i used to. Thus i've stuck with jellybean because everything works well and i have it set up how i want but it's a bit long in the tooth and the phone needs to have a full clean factory wipe so i figured i'd take the time to update to something newer.
My thought process is the following:
Save everything i want to keep and take off phone (including titanium backups)
Factory reset phone
Allow OTA updates to download and install
Then root
Then install custom roms (if i so choose)
Now fellow XDAers, anything wrong with my logic? I did do some reading and some searching and it seems like lollipop is rootable with a script and i can install customer recoverys with a script as well. I'd like the phone to still be able to unlock and root my device.
Thanks for any help and/or links to tutorials.
I am not sure but I think OTA updates need a unrooted system with stock recovery.
I had a rooted KK and I could not OTA to LP because the download was over 1.5 GBs!
The best solution may be to back everything up, connect the phone to LG Tools, and choose the upgrade recovery method to get the latest ROM for your phone.
Hi all,
A couple quick questions here. I've done some reading up, but most of the information is more in depth than I need at the moment so I'm looking for some quick answers.
My SO has a Verizon S5, that has a locked bootloader, is not rooted, and is still on 5.0.
She swapped carriers a while back, so is no longer on the Verizon network. The IMEI is clean, and her Verizon account is fully paid, and everything on the phone works fine, aside from it being stuck on 5.0.
It will not update via the automated system, because I assume it's trying to reach out to straight talk for the update and gets a response that it's on the newest version.
I downloaded the Verizon OTA update file (approximately 1 gb) for 6.0.1. It's named update.zip to allow for automated updating.
Here are my questions:
1. Would it be ok to just slap the update file on her phone and let it auto-update using the built in software?
2. Are there any major downsides to updating to marshmallow, considering it's an official release on the correct version of that phone?
3. Will root be needed prior (I'm assuming not) for using the OTA update file?
4. Will her information stay intact; email accounts, contacts, apps, samsung account, etc?
5. While root would be nice for locking down some of the bloatware after, it isn't a deal breaker, simplicity is the key here as she is not an advanced user, but would updating via the OTA file remove all possibilities of rooting the device after (it seems to be the impression I get, as her bootloader is locked)?
Thank you very much for your assistance!
Hi bladebarrier, I actually just did the same thing a few weeks ago with a used S5 from Verizon going to Straight Talk.
1. Would it be ok to just slap the update file on her phone and let it auto-update using the built in software?
I'm unsure if that would work, someone else may be able to answer as to that method, however I used the Odin tool v3.11.1, downloaded the PD1 image from here. There are some good video tutorials on YouTube and on writeups on this forum as well regarding how to flash the Marshmallow update using Odin.
2. Are there any major downsides to updating to marshmallow, considering it's an official release on the correct version of that phone?
No downsides that I've noticed and seems to have slightly better battery life.
3. Will root be needed prior (I'm assuming not) for using the OTA update file?
You do not need root to flash it if using the Odin tool.
4. Will her information stay intact; email accounts, contacts, apps, samsung account, etc?
Yes, but it's always a good idea to make a backup of everything.
5. While root would be nice for locking down some of the bloatware after, it isn't a deal breaker, simplicity is the key here as she is not an advanced user, but would updating via the OTA file remove all possibilities of rooting the device after (it seems to be the impression I get, as her bootloader is locked)?
The only thing that the locked boot loader affects for now is the ability to flash custom ROMs. I was able to downgrade to 5.0 Lollipop which you can still root, even after upgrading, however I decided to just go back to Marshmallow and wait for an exploit to be found, if one ever is.
jesimpki89 said:
Hi bladebarrier, I actually just did the same thing a few weeks ago with a used S5 from Verizon going to Straight Talk.
1. Would it be ok to just slap the update file on her phone and let it auto-update using the built in software?
I'm unsure if that would work, someone else may be able to answer as to that method, however I used the Odin tool v3.11.1, downloaded the PD1 image from here. There are some good video tutorials on YouTube and on writeups on this forum as well regarding how to flash the Marshmallow update using Odin.
2. Are there any major downsides to updating to marshmallow, considering it's an official release on the correct version of that phone?
No downsides that I've noticed and seems to have slightly better battery life.
3. Will root be needed prior (I'm assuming not) for using the OTA update file?
You do not need root to flash it if using the Odin tool.
4. Will her information stay intact; email accounts, contacts, apps, samsung account, etc?
Yes, but it's always a good idea to make a backup of everything.
5. While root would be nice for locking down some of the bloatware after, it isn't a deal breaker, simplicity is the key here as she is not an advanced user, but would updating via the OTA file remove all possibilities of rooting the device after (it seems to be the impression I get, as her bootloader is locked)?
The only thing that the locked boot loader affects for now is the ability to flash custom ROMs. I was able to downgrade to 5.0 Lollipop which you can still root, even after upgrading, however I decided to just go back to Marshmallow and wait for an exploit to be found, if one ever is.
Click to expand...
Click to collapse
Thank you very much for your thorough response. It sounds like it will be a nice smooth flash, and I will use the full Odin version instead of the OTA file, to ensure it goes through comfortably.
Odin looked like it wanted to wipe the apps, so I ended up using the stock recovery/installer that's built in, and placing the OTA update file on the external SD card.
That worked like a charm. It took a bit, as expected, but all of the apps and info were ok after.
The only thing I can't sort out is why I can't find an option for the "Themes" setting in touch wiz. Any suggestions? I realize I could have her go to a third party launcher, like nova, but I have all of the theme options on my note 3, that's ported to MM note 5, and the theme option is still right there in the settings list, per normal. Maybe I'm just not seeing it, but I couldn't find an option on her S5 during 5.0, or now on 6.0.1. Is that something they never updated for the older phones?
hey guys
i just brick my phone (no idea how, flashed android 7 firmware) after flash my phone was working for like 2 hours, then i let himself update a security options. After update my phone went brick
As far i found :
- installed Qualcoom QDLOADER 9008 driver
- found QFIL programmer
i need to have programmer path (something related to JTAG) and build xmp path
Where i can find them? Or is it a other way to resscue my phone?
I feel your pain. My timeline:
- The phone was unlocked but still in Stock Nougat (7.0?). Got that from OTA in Brazil.
- I tried to update to LineageOS 7 via TWRP. After a full wipe (everything, system, data, card, cache etc) I installed the new ROM. Turned on, bootlooped forever.
- Searching around I found out that there was no modem in the Nougat roms and for some reason I needed to flash a Marshmallow modem for my region to make that work (I think there is no Nougat modems around or something).
- I found a LA_DS modem for 6.0, flashed that using TWRP, still bootloop. Tried other roms using TWRP, still bootloop.
- I then downloaded a full stock old 6.0 firmware to go back to stock but the phone wouldn't accept some files ("preflash validation failed").
- Searched around and found out that you can't downgrade a bootloader from Moto.
- Using fastboot, I flashed the files the phone was willing to accept and it finally booted the 6.0 Marshmallow stock rom, but with no networking (radio/modem/baseband/IMEI missing).
- Flashed the 6.0 modem for my region again and everything worked. Connected on WiFi, dual sim cards detected etc.
- I started to install every update the phone showed to try to update it back to latest MM version.
- The three first updates went ok, the fourth turned off the phone to never turn on again.
Looks like there is no way out of this. My phone is pretty old and MotoCare in Brazil will charge a lung and a half for repair.
dsnunes said:
I feel your pain. My timeline:
- The phone was unlocked but still in Stock Nougat (7.0?). Got that from OTA in Brazil.
- I tried to update to LineageOS 7 via TWRP. After a full wipe (everything, system, data, card, cache etc) I installed the new ROM. Turned on, bootlooped forever.
- Searching around I found out that there was no modem in the Nougat roms and for some reason I needed to flash a Marshmallow modem for my region to make that work (I think there is no Nougat modems around or something).
- I found a LA_DS modem for 6.0, flashed that using TWRP, still bootloop. Tried other roms using TWRP, still bootloop.
- I then downloaded a full stock old 6.0 firmware to go back to stock but the phone wouldn't accept some files ("preflash validation failed").
- Searched around and found out that you can't downgrade a bootloader from Moto.
- Using fastboot, I flashed the files the phone was willing to accept and it finally booted the 6.0 Marshmallow stock rom, but with no networking (radio/modem/baseband/IMEI missing).
- Flashed the 6.0 modem for my region again and everything worked. Connected on WiFi, dual sim cards detected etc.
- I started to install every update the phone showed to try to update it back to latest MM version.
- The three first updates went ok, the fourth turned off the phone to never turn on again.
Looks like there is no way out of this. My phone is pretty old and MotoCare in Brazil will charge a lung and a half for repair.
Click to expand...
Click to collapse
Pretty similar situation on my part. I downgraded back to 6.0 and when it tried to take the December update I ended up with the same thing as you. I ended up getting a replacement from Moto for under 100 dollars which was worth it rather than trying to find a solution that doesn't exist.
I recently bought a T560NU, in really nice shape except it's been upgraded to Nougat.
I don't know these Galaxy tablets, mostly Moto phones (have unlocked/rooted/ROM'd several) plus have rooted an Asus tablet and a couple of Samsung phones . . . I know those can't be downgraded, but I'm in the dark about Samsung tablets. Just hoping.
1. Second title-question first, as I would prefer this if it's possible: Can I downgrade Nougat on this Tab E 9.6 to Marshmallow? I have the 6.0.1 BQF1 firmware downloaded from sammobile. The phone is now running CQK2.
2. If it can't be downgraded, is it safe to install TWRP 3.1.1-1 gtelwifiue on stock Nougat? And then root with SuperSU or Magisk?
Thanks very much in advance for whatever help/advice might be offered.
I realize these questions might seem a little noobish-ignorant, but after reading that (for example) the LG G Pad 8.3 can apparently be downgraded (at least the bootloader) and it is (or used to be) necessary to downgrade the bootloader to KK before TWRP could be installed; thus I ask both questions here . . . and because after browsing (and searching) a large part of of the Tab E forum, I read a lot of general talk-around, and think, well, it would probably be okay to try installing TWRP, but I don't really get a clear and solid feeling about basic prerequisites or do's and don'ts. I just bought a nearly-brand-new SM-T560NU running Nougat 7.1.1, and you can understand I don't want to take any unnecessary chances.
So I took this specific question and answer as an endorsement for installing TWRP on a T560NU with 7.1.1 (despite reading of several problems getting TWRP on the T377x). The title of the above-referenced thread threw me, because the OP's question is not about root, it's about TWRP. I installed twrp-3.1.1-1-gtelwifiue successfully on my T560NU with Nougat, flashed via Odin clean as a whistle. Just mentioning this for posterity.
As for downgrading stock firmware, it seems like this post (xTujirox's part at the bottom) is telling me I can do that. But considering that downgrading firmware (bootloader etc) can be a much more risky proposition, I'm still waiting/hoping for a more specific response to the question before I even think about trying it.
After 10+ days of waiting I decided to bite the bullet and dive in. It was nerve-wracking, but I got 7.1.1 downgraded to 6.0.1. About 40 minutes after starting, I was thinking I'd gotten a bad download from sammobile. But I finally got it working.
It turns out all I needed to do was clear cache and wipe data (in the stock recovery, since TWRP was blown away by the firmware flash). But it was a slow walk through he11 getting there . . .
After the phone rebooted from Odin and I got the Andy screen "updating" screen, and then apps optimization for the Marshmallow "update". After optimizing 218 apps (or so I thought), the phone went into a loop where 3-4 processes kept crashing/not starting. Most critical I'm sure was "android.process.acore" and the System UI. With the System UI not starting up, it was a real trick to get a shutdown to take -- lots of quick double-thumb-taps because the error pop-ups kept obscuring power-off.
It finally did shut down, and I powered-up into recovery with no problem. Once there I wiped cache and then data/factory reset. After watching the "Samsung" screen for 10 minutes plus, Marshmallow started up clean as a whistle. Another power-down and -up to make sure it started up okay, and then back to download mode to reflash TWRP.
Again this is all for "posterity" in case anybody else comes along with the same question(s).
PS . . .
Files Used:
T560NUUEU1BQF1_T560NUXAR1BQF1_XAR.zip (downloaded from sammobile)
. . . the US or "Cellular South" version of MM 6.0.1
. . . this zip file extracts to one rar.md5 file, which is flashed in the AP slot.
twrp-3.1.1-1-gtelwifiue.img.tar
Odin 3.12.3
Hi, I get a notification to update magisk. then I update it and use the recommended action to update it. After that it asks me to reboot the device. After rebooting the device it goes to fastboot only. And I see the device now changes to US996 while what I have is H990DS.
Can someone explain to me what's wrong and how to fix it without losing all my data?
thanks...
Hi there,
all I can say is that is happened exactly the same to me just some minutes ago, I installed latest magisk update like I've been doing with no problems, just that today, after reset, its always booting stuck into fastboot mode.
I have a H910 and I also see the message about US996, maybe this is related to the method used to root the phone, If I recall correctly it had something to do with installing a US996 modified bootloader.
I still haven't found a way to get my phone back to life. All I can say is that I do manage to boot into recovery (TWRP, via the appropriate key combination at power on), so I guess I'll manage to flash something to fix this and return it back to life I hope
aliks00 said:
Hi there,
all I can say is that is happened exactly the same to me just some minutes ago, I installed latest magisk update like I've been doing with no problems, just that today, after reset, its always booting stuck into fastboot mode.
I have a H910 and I also see the message about US996, maybe this is related to the method used to root the phone, If I recall correctly it had something to do with installing a US996 modified bootloader.
I still haven't found a way to get my phone back to life. All I can say is that I do manage to boot into recovery (TWRP, via the appropriate key combination at power on), so I guess I'll manage to flash something to fix this and return it back to life I hope
Click to expand...
Click to collapse
It's common knowledge that if you root your phone you never apply an OTA
Sent from my LG-H910 using XDA Labs
cnjax said:
It's common knowledge that if you root your phone you never apply an OTA
Click to expand...
Click to collapse
Thanks, but who said I ever applied an OTA? It was magisk that wanted to update itself, I've been performing magisk updates regularly for quite some time and never had a problem, in fact I can't even perform an OTA phone update as I have AT&T variant but with a different sim...
Other times, when updating magisk, I lost root but never lost the ability to boot...
I was running alpha-omega oreo with mk2000 kernel and updating rom, kernel and magisk regularly through TWRP (or direct install in case of magisk though magisk app) and never had this problem before... at least I can manage to boot from recovery/TWRP so hopefully I will soon manage to get things working again... that is, if I can copy some images to my SD card that windows insists that is corrupted but that's another story...
I ended up flashing whole rom again and everything is back to normal