Related
Hi everyone.
So a few weeks ago I decided to root my HTC One. I was fairly new to rooting, and I still am. I used the rumrunner tool to get s-off. Then, I used adb to get CWM recovery, and after trying out a few different roms, I decided to stay on stock HTC Sense 5.0. Well, I downloaded Xposed and that's when my problems started. I downloaded Gravity Box, Sense 5 Toolbox, and Tinted Status Bar. After using these all for a while, I started to notice something. First off, all my notifications were expanded automatically, which I didn't like. Then, I started noticing that MMS messages would neither download, or send. I tried uninstalling the Xposed modules, and Xposed itself, but that didn't change anything. These things could've started happening prior to installing Xposed, but I didn't notice them until after I'd installed the other modules. Anyways, I got tired of it, and decided to factory reset my phone, thinking it would fix the problem. Of course, before resetting I made a back up in CWM, in case the reset didn't work. It didn't. And the reset deleted my back up. So now, my phone is factory reset, and still won't receive MMS messages. I've also tried messing with the APN settings, but that didn't help at all. I've tried looking around for some answers but I can't seem to find anything. I'm s-off, stock, and rooted. I'm pretty upset at this point and just want this fixed. Any suggestions? Would unrooting my phone solve the problem?
So you factory reset but didn't actually re-install the rom? Try going into recovery and wiping data/cache/davlik and installing the OTA stock rom from here: http://forum.xda-developers.com/showthread.php?t=2485319
I still have the stock 4.2.2, Sense 5 rom. This might sound like a stupid question, but can I install the 4.3 stock rom as an update, without having to wipe everything? I've already started setting everything up again, to the way it was before, and I really don't want to start over again.
Mono41 said:
I still have the stock 4.2.2, Sense 5 rom. This might sound like a stupid question, but can I install the 4.3 stock rom as an update, without having to wipe everything? I've already started setting everything up again, to the way it was before, and I really don't want to start over again.
Click to expand...
Click to collapse
If you're S-off I believe you can flash the stock recovery and take the OTA then flash TWRP again and the supersu zip to root. What did you set up exactly? If they're apps just use Titanium backup and restore them later
Crawshayi said:
If you're S-off I believe you can flash the stock recovery and take the OTA then flash TWRP again and the supersu zip to root. What did you set up exactly? If they're apps just use Titanium backup and restore them later
Click to expand...
Click to collapse
I set up things like my homescreens, restored my text messages, downloaded all my offline music from Google Play, restored app data, system settings, and I moved all my pictures and things from my computer onto the phone. Anyways, I flashed the 1.10.605.15 stock recovery and tried to install the OTA, but it gets a little under a third of the way through before it fails and gives me a red triangle with an exclamation point.
Hi. I downloaded Lollipop but have not installed it yet and don't want to. I didn't know it was Lollipop I was downloading. How do I get rid of the possibility of it installing? I keep having to delay it for 24 hours. Do I have to do a factory data reset?
What version of anroud are you on and are you rooted? If so you can simply go to the /cache folder and delete the .cfg file file.
If you reboot before doing that the update will be installed.
I'm on 4.4.2 and not rooted. If I do a factory data reset before I install Lollipop would that get rid of the download ?
"Luke" don't fight it, grab the lollipop and feel the Force.
The force never tasted better.
Pp.
What is your reason for not wanting to update? Anything particular?
Rhino_7 said:
I'm on 4.4.2 and not rooted. If I do a factory data reset before I install Lollipop would that get rid of the download ?
Click to expand...
Click to collapse
From what I know , when you try a factory reset it will reboot your phone to recovery and perform the reset there. It may successfully do so, or it may immediately install the update in recovery. I can't say for sure.
If it is absolutely necessary for you to avoid this update, backup your files, download a firmware from Sammobile that matches your current 4.4.2, very carefully reset to download mode (you will only have one shot at this) and Odin that old firmware into your system. Hopefully that will overwrite all your files and remove the update. On the first boot enter recovery and do a reset. That is the most likely solution I can think of which may have a remote chance of working.
Another possibility is that if your firmware has a date before Jun 5 2014, you can run towel root version 3 to root it (doesn't require a reboot) then go to the cache directory and delete the update file. Of course all of this should be done before rebooting. This should work but you will end up with a rooted system.
Finally if your were forced to take the update you can almost downgrade it back to 4.4.2.
Thanks. I just did a factory data reset and it worked fine.
The reason is I like the phone now just as it is. No WiFi issues,great battery life,ect. From what i have read even though Lollipop is a big update there is nothing new that makes me want to have it.
Anyone want to try and convince me?
Android updates seem to always be buggy. I "might" try it later.
I went straight up Kies update and the phone never ran smoother.
Running stock /rooted / debloated and everything works the way it's supposed to.
No bells, no whistles, no exposed, just straight up touchwiz.
Knox shmox, never gave it a second thought after the warranty ran out.
Pp.
I did this a while ago when development was really slow and flashing pre rooted roms was a hassle. I disabled updates via the "pm disable com.amazon.dcp" method while I had root. After a while the AFTV got sluggish and so I decided to sideload a stock image and lose root in order to stay up to date with the newest software. Well, I forgot to enable updates again before sideloading the stock rom and losing root. Now my device can't update, I can't sideload even stock images I don't believe, and I'm stuck on a version that is not rootable. Am I completely screwed because I did not "pm enable com.amazon.dcp" prior to flashing a stock image?
.Gibson. said:
I did this a while ago when development was really slow and flashing pre rooted roms was a hassle. I disabled updates via the "pm disable com.amazon.dcp" method while I had root. After a while the AFTV got sluggish and so I decided to sideload a stock image and lose root in order to stay up to date with the newest software. Well, I forgot to enable updates again before sideloading the stock rom and losing root. Now my device can't update, I can't sideload even stock images I don't believe, and I'm stuck on a version that is not rootable. Am I completely screwed because I did not "pm enable com.amazon.dcp" prior to flashing a stock image?
Click to expand...
Click to collapse
Do a factory reset.
I just posted something quite similar to this... I should've scrolled down a little bit before posting.
rbox, I'm in the same situation. I already did a factory reset before I ran the official updater, but the stock update never gets past the white fire logo after the reboot. If I hard boot it, I'm back to my old rom....
rbox said:
Do a factory reset.
Click to expand...
Click to collapse
Wow, after all these months and trying multiple solutions I never thought to factory reset. I feel silly. Thank you so much, it worked like a charm and I am able to update to the latest. Take care.
Hi,
am using a Pixel XL 1 on Android 8.1, bootloader unlocked, patch level of February. Now I have the problem that since about December no OTA updates are shown/offered at all. Therefor I always had to manually update.
Even the manual triggering of searching for updates, which has recently been changed so that the devices explicitly should get the currently available update, does not work.
The device was rooted, but I have unrooted it (Magisk) now, and is running the standard firmware from Feburar on it.
Does anyone have any clue why my device is not offered any OTA updates?
Anyone?
What kind of recovery do you have installed? Stock or TWRP?
Kream24 said:
What kind of recovery do you have installed? Stock or TWRP?
Click to expand...
Click to collapse
Stock. So everything should be as vanilla as possible! I'm really clueless.
i don't get it either. pixels running a non-stock os should get notifications about a new update. they won't install successfully though. i'm guessing, but maybe going through the unroot process to get rid of magisk did not return your os to completely stock. maybe some junk was left behind and that's causing your issue.
my suggestion is to flash a full factory image to start fresh. i would edit the flash-all.bat script to remove the -w option to keep data. if that doesn't work, put the -w option back and rerun to wipe data and flash the factory image. if you really want to see if that fixes your problem, flash an older image like the february or january one, and see if the update notification comes back. or flash the march image to be up to date and wait until april to see if you get the update notification.
altwu said:
i don't get it either. pixels running a non-stock os should get notifications about a new update. they won't install successfully though. i'm guessing, but maybe going through the unroot process to get rid of magisk did not return your os to completely stock. maybe some junk was left behind and that's causing your issue.
my suggestion is to flash a full factory image to start fresh. i would edit the flash-all.bat script to remove the -w option to keep data.
Click to expand...
Click to collapse
That's what I've did already No difference.
if that doesn't work, put the -w option back and rerun to wipe data and flash the factory image.
Click to expand...
Click to collapse
It's just the hassle installing everything from scratch again.
I wish recovery/backup was as easy as on iOS. Without necessity of any tricks, root etc.
Is this phone enrolled in the Android Beta Program ? I've had trouble getting OTA updates on my phone after the beta program ended for it until I un-enrolled from the program, then I got updates like normal. There will be warnings about having to wipe the device, but if your on the the stock/stable version already you won't have to.
shaneledford said:
Is this phone enrolled in the Android Beta Program ? I've had trouble getting OTA updates on my phone after the beta program ended for it until I un-enrolled from the program, then I got updates like normal. There will be warnings about having to wipe the device, but if your on the the stock/stable version already you won't have to.
Click to expand...
Click to collapse
Tried that one as well. I was on a beta at some point, but unsubscribed from the beta. Also tried to unsubscribe again, but it the well know link took me to a page where it said that there is no beta, hence I couldn't try to unsubscribe again.
When you flashed the full factory image did you use the newest march update? if you did then you wouldnt get anything because you are already current
Gotta say, exactly the same problem.. stuck on 8.0 November lol. Haven't found a solution, too lazy to manually flash for now. Let me know if you find a solution!
have you tried deleting the data and cache on the google services app?
Hi, I'm replacing a lost Moto G3 TE with a Moto G5 (xt1671 dual sim) that should be coming in the mail on Monday. I'd like to do whatever mods I want to my phone right away, before activating my google account on it and everything. So, I'd really like any advice any of you can give as to preferred custom rom with root that I should put on my new phone, so I can get to it right away. I've already found the thread to unlock it (same process as in past mostly), and I've found the guides for putting on TWRP (either 32-bit or 64-bit). So, now I just need to decide which custom ROM to use. Please advise!
I've also had a Moto G2 in the past. I've unlocked and used custom roms and root on all my phones so far, from Cyanogenmod 12.1 to AOSP Extended, ViperOS, and LineageOS. My wife's Moto G2 has Oreo on it (through AEX) and we're enjoying it (I had her add me as an account until I get my new phone). So, I'd like to continue using an Oreo system if possible, and I'd even prefer AEX, but it seems that it's discontinued for the Moto G5. Is that correct?
My overall goals for a custom rom are, in order of priority: reliability, speed/performance, battery life, and customization options. I found that AEX balanced all of that well on our past phones. Is the discontinued AEX for this phone reliable, or not? I've also seen the LineageOS thread and the KAOSP thread and have glanced at a few others. I use google accounts and half their apps for sure (so I'll want to install a GApps package with it). And I see there's a possibility to unlock RAW/DNG files for the camera, which I'd really like to try (as I prefer raw file editing instead of JPGs). And the customizations I like (if still possible) are mainly involving the way the launcher responds - I like having the navigation buttons hide, or to swipe up to get them back, I like being able to modify the status bar, etc.... typical customizations that were usually available in AEX that I've used. I also use root for file explorer and a few other functions - I used to always use SuperSU in the past, but just recently started using Magisk (on the Moto G2) and it seems good, though I'm open to any recommendation about which root to use.
So, please fire away! Please give your suggestion as to which currently available custom ROMs are stable, have good performance, good battery life, and offer standard customization, plus which I can root. I appreciate any suggestions and any advice you can give, especially regarding if there's a recommended rom but if it has known issues and any known workarounds. Also, I'd appreciate advice anytime today or tomorrow (since it'll likely be the afternoon or evening of Monday +3 GMT time - Madagascar - that I'm able to start working on unlocking it, installing custom recovery, etc.). But even if the advice is late, I might still be able to use it. I know this is a bit much to ask, but please give your own opinions freely!
Oh, by the way, do I need updated Motorola drivers, or will the motorola drivers and adb/fastboot I installed last time (for the Moto G3 TE) keep working with the new phone? The unlock thread I've found here doesn't say anything about motorola drivers or adb/fastboot. Thanks in advance!
the best stable rom is stock rooted
woozie.2007 said:
the best stable rom is stock rooted
Click to expand...
Click to collapse
Thanks for the response! Is there a stock oreo available? And is stock rooted still customizable (like with AEX or something - can I install some sort of thing to let me customize it more?). And is there a debloated version of the stock rom available? I saw one thread on here about a debloated stock rom, but it looked like it was still nougat.
If it's possible to customize the stock rom further, please point me in the right direction. And if not possible to customize it further... then are you suggesting that any of the custom roms available aren't very stable to be used well for a daily driver?
Again, thanks for your response and also for any more feedback you can give!
So, I have my phone now and it came with stock Nougat. I've unlocked it, and I'm currently working on getting TWRP, Dm-verity thing on it, and then magisk. After that can I still update it to Oreo or not? Please advise. Thank you!
madagascaradam said:
So, I have my phone now and it came with stock Nougat. I've unlocked it, and I'm currently working on getting TWRP, Dm-verity thing on it, and then magisk. After that can I still update it to Oreo or not? Please advise. Thank you!
Click to expand...
Click to collapse
no, you have to update oreo first, after that install twrp and magisk for root it
woozie.2007 said:
no, you have to update oreo first, after that install twrp and magisk for root it
Click to expand...
Click to collapse
Crud, that sucks! I was already finished rooting and everything on magisk, then I let the OTA update download and when it restarted my phone, it just automatically sends it into recovery (TWRP) every time now! I tried to install this TWRP stock Oreo (dirtying flashing it) hoping it would fix the boot-loop-to-TWRP-recovery problem, but it didn't. So now I need to figure out a way to get back to the original, so I can start over and try again.
I'm trying to do a factory reset and try again, but in TRWP it says ""Failed to mount '/data' (Device or resource busy)'" This sucks! Any ideas where I can go or what I can do (such as some fastboot commands or something) to get it all working again?
EDIT: It does reboot to bootloader though, so it's not hardbricked. Just need to figure out what to do from here. Thanks for any help!
try to flash via fastboot only boot, recovery, oem and system from oreo, then aply update, then root
Thanks! I downloaded the firmware (for latest Nougat) from this thread: https://forum.xda-developers.com/g5/development/stock-upgrade-to-official-stock-oreo-8-t3823598
Then I flashed everything they said through fastboot (ignoring the modem stuff) because I'm still downloading the oreo firmware right now anyway (my connection is quite slow). At first the bootloader got stuck and said "error" and I was freaking out thinking I'd hard-bricked it. But I turned it off and on again anyway and it loaded fine back into nougat for that latest version.
So now I'm downloading the latest stock Oreo and I'll probably try to ADB sideload it.
Which root do you recommend? I have the Magisk I did for nougat that worked great - 11.6 But there's this thread here (https://forum.xda-developers.com/g5/how-to/guide-how-to-root-stock-oreo-8-1-soak-t3832347) that talks about what seems like a complicated way of doing Magisk 15.3 and then getting it up to 16. What do you suggest?
magisk 17.1 its ok, but you have to flash only partition that i said, not full firmware, and DONT flash the bootloader and GPT partition
---------- Post added at 06:11 PM ---------- Previous post was at 06:10 PM ----------
better let the phone to update ota for latest security patch, dont flash via fastboot
OK, I installed the stock oreo through ADB sideload (it wouldn't read my storage for some reason).... then I reinstalled TWRP, no problem... then installed Magisk 17.1 (per your suggestion) and then the apk for the manager. Everything's working great! Didn't even need that dm-verity thing.
I'm still looking into the mods I can do to it now that it's rooted (such as changing boot logo and boot animation, adding that 'camera 2' setting, etc.) So I'm not sure I'm at a finished product yet, but I'm definitely at a stable rooted oreo with all my regular stuff installed, so that's a good place to start! I've made a nandroid backup here in case any of my further experimenting messes it up.
Thanks again for your help! And if you can give any suggestions towards the best way to customize the look (for example - is nova launcher still the best way to do that?) or other aspects of the system UI, while still being on this stock rom, then please let me know. I'll look up how to get that better camera mode working.
woozie.2007 said:
magisk 17.1 its ok, but you have to flash only partition that i said, not full firmware, and DONT flash the bootloader and GPT partition
---------- Post added at 06:11 PM ---------- Previous post was at 06:10 PM ----------
better let the phone to update ota for latest security patch, dont flash via fastboot
Click to expand...
Click to collapse
Could you help me with this: if I backup my system (everything) with TWRP.... can I then switch to a custom rom to try it out (in case I want a different user interface, more tweaks, etc.) and if I don't like it can I easily switch back to the stock rom nandroid backup I have saved in TWRP (thus restoring my previous state, but without having to start from factory reset)? Or would it be difficult to switch back - like would I have to redo it through fastboot or something and factory reset, etc.?
I'm asking because in the past I never used the stock rom much and I definitely never switched between a custom rom and the stock rom. Once I went for custom rom, I didn't go back - so I don't know if it's as simple as restoring a nandroid backup or if it's much more effort. Please let me know. Thanks a lot!
you must be very carefully because most of the custom roms need twrp on 64 bits, now you have official twrp 32. When you come back from custom roms 64bit to previous nandroid backup, you must install 32 bits twrp, otherwise you may lose the imei of the phone, just read very well when you want to do something risky
woozie.2007 said:
you must be very carefully because most of the custom roms need twrp on 64 bits, now you have official twrp 32. When you come back from custom roms 64bit to previous nandroid backup, you must install 32 bits twrp, otherwise you may lose the imei of the phone, just read very well when you want to do something risky
Click to expand...
Click to collapse
OK, thanks a lot for that helpful info! So just to clarify to be sure: basically, if I want to switch back and forth, I'll install the 64-bit twrp first, then the custom rom(s). Then if I want to come back to my stock image backup, I re-install the 32-bit twrp (like the one I'm currently using) and then I can just restore my nandroid backup I took of the stock and all is well? And it's not risky if I do it like that?
yes, its correct that