I, like everyone, am looking forward to installing this update. However, I have heard from others (people with other phones or carriers) that Android L isn't all that great, mainly because of some bugs. Of course this may have had to do with a carrier's modification of Lollipop, so while this would likely be fixed, it certainly gives me pause to go to the effort and update (restore stock recovery, unroot, and other necessary prep work) to find out it's really not that fantastic or T-Mobile needs to fix some things.
So, I was hoping that those if you who have successfully updated could tell me (and others who might want to know) how Lollipop is for you.
Also, if you could tell us what you were before updating (rooted, S-off, using Xposed, none of the above, etc.) it would give us an idea of the difference in systems.
Thanks!
I was rooted, boot loader unlocked, TWRP installed. So I restored a non-root version and restored the recovery.img (took me a bit as I had downloaded an older version not realizing that so the OTA failed).
Upon the first boot up after the OTA, my wifi failed to work at all no matter what I did. I ended up doing a factory wipe (which wiped all my programs and settings - ouch) and now all seems to be working (but I am still setting things up).
-brad
I was stock unrooted, with S-Off and SuperCID. It took the OTA without a hitch. Had a little trouble getting play services to update, but after a restart it did fine. So far everything seems to be working. No bugs that I've found yet. Liking the new features a lot. Really wish they had brought VoLTE with this update.
I'm a long-time user of Team Venom's ViperROM, and only come back to stock for things like this.
I used an RUU to go back to stock, as the stock recovery I had wouldn't work with the OTA from my backup, and AndroidFileHost is down, so I couldn't use the only link I could find to get the latest recovery before this update.
Anyway, I downloaded the update just fine, and it installed just fine, and everything works just fine so far. It feels a whole lot snappier than before. I like the new notification system. The only thing that's driving me crazy is that I can't make the recent apps button into the menu button without installing anything extra. Come on, HTC, add that!
In conclusion, everything is as snappy and pretty as ever before, Wi-Fi speeds are good, call quality is good, and I am thoroughly enjoying it. When Team Venom pushes out their custom ROM, I'll be ecstatic.
I installed the new update this morning and rerooted after. I can't get AdAway to work properly. Otherwise, everything has been much faster and more responsive than it was previously. Feels like a fresh install. Only big issue I've come across is it uses GPS constantly which heats up the phone and kills the battery. I had to turn off GPS to avoid this. I think it may be related to the new Trusted places feature, as the updated Google service uses the GPS a lot.
I RUU'd back to stock after realizing that just going back to an old backup would still result in "Software Status: Modified." After I did that, update installed smooth. I haven't had any of the problems with wifi or data that some people have complained about. I still am not a huge fan of all the t-mobile bloatware, and will probably root/rom it within the month to something a little(lot) cleaner.
StormChaser46 said:
I installed the new update this morning and rerooted after. I can't get AdAway to work properly. Otherwise, everything has been much faster and more responsive than it was previously. Feels like a fresh install. Only big issue I've come across is it uses GPS constantly which heats up the phone and kills the battery. I had to turn off GPS to avoid this. I think it may be related to the new Trusted places feature, as the updated Google service uses the GPS a lot.
Click to expand...
Click to collapse
Just out of curiosity, what method did you use to obtain root?
dysfunkshun said:
Just out of curiosity, what method did you use to obtain root?
Click to expand...
Click to collapse
It was already rooted and the bootloader was unlocked before the update. I just had to reflash TWRP recovery, reflash the supersu.zip file, and then reinstalled supersu from the Play store.
Voice Dial
Discovered today that when you use a bluetooth to activate voice dialing now it gives you the choice to use the google/now app instead of the pre packaged voice dialer.
I was full stock and locked and accepted the OTA without issue of course. Had a little trouble with Google Play Services wanting to update but failing to finish the update. Did some reading and found a solution on androidforums that worked - cleared data and cache on both Google Play Servies and Google Play and then the update succeeded. Since then all works well and I too feel it is much snappier than KitKat. Haven't tried all apps yet but so far so good.:good:
Edit: I had used lollipop on my M7 reconfigured as GPE and really liked the Nexus experience. Since Jumping to the M8, I have chosen not to unlock and root (yet) as I anticipate a jump to the M9. That being said, I like the added features I have seen so far in the pure Sense experience. Notification on the lock screen are better, the Smart Lock works great at home and at work, so far no issues. Loving it. Will write back after a few days of exercise.
Hey, sorry for the basic question here. Just bought an used HTC M8. When I booted, i got the message "this build is for development purposes only do not distribute outside of htc without written permission. Failure to comply may lead to legal action," which I gathered means the phone is unlocked. What steps can I get to get updated to Lollipop?
Can I just download TWRP and flash RUU 4.20.531.4 from http://forum.xda-developers.com/showthread.php?t=2714456 ?
Or do I need to find a way to get to stock t-mobile rom and then back up and recover to 3.32.531.2 recovery before I can get OTA updates?
Thanks!!
pewpew22 said:
Hey, sorry for the basic question here. Just bought an used HTC M8. When I booted, i got the message "this build is for development purposes only do not distribute outside of htc without written permission. Failure to comply may lead to legal action," which I gathered means the phone is unlocked. What steps can I get to get updated to Lollipop?
Can I just download TWRP and flash RUU 4.20.531.4 from http://forum.xda-developers.com/showthread.php?t=2714456 ?
Or do I need to find a way to get to stock t-mobile rom and then back up and recover to 3.32.531.2 recovery before I can get OTA updates?
Thanks!!
Click to expand...
Click to collapse
You can do an RUU, but the first thing I would do is get S-Off. I don't know if it is still Sunshine (an app that was $25) that is the leading method, but even still, it's worth it. If you have S-Off, there are really no mistakes you can make and can't undo....[well, you can't brick it or throw it in a lake].
I am so dependent on customizations, such as button modifications, definitely Ad-Away, and other things, most of which were possible with a custom ROM, or Xposed, but since Dalvik is gone, I understand Xposed won't work. This gives me pause. No matter how nifty Lollipop is, if there is no way to do certain customizations/modifications, and if Ad-Away won't work, I would seriously consider waiting until these things are remedied.
StormChaser46 said:
I installed the new update this morning and rerooted after. I can't get AdAway to work properly. Otherwise, everything has been much faster and more responsive than it was previously. Feels like a fresh install. Only big issue I've come across is it uses GPS constantly which heats up the phone and kills the battery. I had to turn off GPS to avoid this. I think it may be related to the new Trusted places feature, as the updated Google service uses the GPS a lot.
Click to expand...
Click to collapse
No luck on Ad-Away yet?
syntropic said:
No luck on Ad-Away yet?
Click to expand...
Click to collapse
It works fine, UNLESS you haven't disabled system RW protection but I thought everybody knew about that. If you are not s-off, or have not applied the mod to disable system RW protection, you will never be able to modify the hosts file while booted into Android system and so Ad Away app won't be able to either.
In this case all you can do is manually create a modified hosts file and push it with ADB or copy it through file manager while booted to recovery.
{
"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"
}
Messenger cannot send nor receive MMS
It's my only concern so far, HTC messages app works though, I've seen various reports about it but no fix so far. Everything else is running smoothly and I'm liking it. I wish wifi networks would be added to trusted locations but there are apps that allow this
I like T-Mobile Lollipop better than international, for one you don't get those annoying notification vibration.
Did they disable HTC Backup? Havent been able to get a backup to start when connected to wifi.
phil.culler said:
Did they disable HTC Backup? Havent been able to get a backup to start when connected to wifi.
Click to expand...
Click to collapse
Did you try manually running it? My backup didn't run properly and it managed to install apps that I had deleted.
Sent from my HTC One_M8 using XDA Free mobile app
Behold_this said:
It works fine, UNLESS you haven't disabled system RW protection but I thought everybody knew about that. If you are not s-off, or have not applied the mod to disable system RW protection, you will never be able to modify the hosts file while booted into Android system and so Ad Away app won't be able to either.
Click to expand...
Click to collapse
Ok, well I'm S-off, and the only thing I know about the system RW protection is that it exists and while I have one xposed module note that purports to enable it, it does not work. I know this because I can't get Root Logger to work. But right now ad-away on kit Kat is fine.
So is there an disable RW system protection mod I need to run? If so, when should I run it? Now before I upgrade (as I have been still hesitating, but it's getting difficult to resist at this point..especially with La Pollo replacement for Xposed (even though there are no modules written for it yet...at least we have the framework. )
Strange I didn't know about this system RW mod.... I will look around in the regular M8 forum, but if anyone can fill me in, I'd appreciate it.
Related
This is to confirm that I managed to install the most recent OTA JB leak from my out-of-the-box Bell Galaxy S3, without having to flash anything, no CWR, no rooting required. Also didn't have to wipe any data or factory reset, after the update all my apps and data were in order as if I did a Kies update.
This is all you need to do - keep in mind this only works for UNROOTED stock Bell firmare (I747MVLALH) cannot by any means guarantee results for any other carrier/version.
Download latest OTA leak here
Save zip file to EXTERNAL SD CARD of your phone, do not unzip or rename.
Boot phone in stock recovery (Turn off phone & start up by holding down Volume Up+Home+Power, let go when the Samsung logo appears)
From Recovery menu select ->Wipe cache partition (this step, if ignored may be the reason why this didn't work for other users)
From Recovery menu select ->Apply update from external storage->select zip file you saved on external SD earlier and let the phone do its thing. It will take a few minutes before the slider bar shows up so don't panic thinking that its not working, in my case the upgrading process took about 15min
Restart phone, and enjoy JB!
All apps and data were still there, no need to reconfigure anything. Flash counter did not get tripped, ROM still shows as "Samsung Official".
Bell TV app still works, which means that Bell still recognizes the phone, however KIES does not, so for upcoming official OTA update you will need to revert back to stock ROM.
Google Now works great, the speech recognition is almost flawless, has recognized everything I said and I have a pretty thick accent in English. To get it working, you just need to update Google Voice search, for me the update request showed up automatically.
As far as bugs, only thing I found so far is WiFi tethering will only work when set as open (no password) and grey notifications bar (which may be just part of design). Some people reported issues with music player but its working fine for me.
As for performance, I find that apps open with zero lag, I did find some choppiness when scrolling lists in certain applications and websites. See attached quadrant result.
For those who try it please post experience and other issues/bugs that may be there.
Update: To enable voice response from Google Now, download this from Play Store, then select US English language, thats it!(credits to DEEZENUTSZ)
Update: some users reported GPS inaccuracies, this can be resolved by clearing cache data for the maps application. Mine works great so far.
Update: ***IMPORTANT PLS READ*** All app related issues reported by users in this thread (GPS, maps, bluetooth, music player etc) are resolved by clearing cache and data for each app. Alternatively, you can do a factory reset and it will take care of every app issue and force closes. Again, the above method works only for STOCK UNROOTED Bell ROM, any other ROM would require ODIN flashing and/or flashing stock Bell ROM first. I will no longer reply to issues that have already been discussed, so before you start firing your negativity bombs, please take the time to carefully read this step-by=step guide and all the updates I added. Oh, and don't forget to thank me once in a while
{
"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"
}
cozanostra said:
This is to confirm that I managed to install the most recent OTA JB leak from my out-of-the-box Bell Galaxy S3, without having to flash anything, no CWR, no rooting required. Also didn't have to wipe any data or factory reset, after the update all my apps and data were in order as if I did a Kies update.
This is all you need to do - keep in mind this only works for stock Bell firmare (I747MVLALH) cannot by any means guarantee results for any other carrier/version.
Download latest OTA leak here
Save zip file to EXTERNAL SD CARD of your phone, do not unzip or rename.
Boot phone in stock recovery (Turn off phone & start up by holding down Volume Up+Home+Power, let go when the Samsung logo appears)
From Recovery menu select ->Wipe cache partition (this step, if ignored may be the reason why this didn't work for other users)
From Recovery menu select ->Apply update from external storage->select zip file you saved on external SD earlier and let the phone do its thing. It will take a few minutes before the slider bar shows up so don't panic thinking that its not working, in my case the upgrading process took about 15min
Restart phone, and enjoy JB!
All apps and data were still there, no need to reconfigure anything
Bell TV app still works, which means that Bell still recognizes the phone, however KIES does not, so for upcoming official OTA update you will need to revert back to stock ROM.
Google Now works great, the speech recognition is almost flawless, has recognized everything I said and I have a pretty thick accent in English. To get it working, you just need to update Google Voice search, for me the update request showed up automatically.
As far as bugs, only thing I found so far is WiFi tethering will only work when set as open (no password) and grey notifications bar (which may be just part of design). Some people reported issues with music player but its working fine for me.
As for performance, I find that apps open with zero lag, I did find some choppiness when scrolling lists in certain applications and websites.
For those who try it please post experience and other issues/bugs that may be there.
Click to expand...
Click to collapse
Thanks for the info. I'm on stock rooted, will this work or do I have to revert to the non-rooted? If it works with stocked rooted will I lose root?
MagicMan3 said:
Thanks for the info. I'm on stock rooted, will this work or do I have to revert to the non-rooted? If it works with stocked rooted will I lose root?
Click to expand...
Click to collapse
I believe you will loose root, so maybe better off reverting it before you apply update
cozanostra said:
I believe you will loose root, so maybe better off reverting it before you apply update
Click to expand...
Click to collapse
Is there a way to root this one without tripping the flash counter?
MagicMan3 said:
Is there a way to root this one without tripping the flash counter?
Click to expand...
Click to collapse
Just went in download mode to check, and surprisingly the counter was not tripped, more specifically:
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Official
:victory::victory::victory::victory:
cozanostra said:
Just went in download mode to check, and surprisingly the counter was not tripped, more specifically:
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Official
:victory::victory::victory::victory:
Click to expand...
Click to collapse
You flashed over a rooted rom?
I got error 7 with both rooted stock and just stock.
Odd though, I went into download mode by accident first and System Status showed "custom"... hmm...
MagicMan3 said:
You flashed over a rooted rom?
I got error 7 with both rooted stock and just stock.
Odd though, I went into download mode by accident first and it showed "custom"... hmm...
Click to expand...
Click to collapse
That might be your problem, bring the phone back to its out-of-the-box state. Here's the stock rom: http://www.hotfile.com/dl/170455695/ba5821b/I747MVLALH1_I747MOYCALH1_BMC.zip.html
cozanostra said:
That might be your problem, bring the phone back to its out-of-the-box state. Here's the stock rom: http://www.hotfile.com/dl/170455695/ba5821b/I747MVLALH1_I747MOYCALH1_BMC.zip.html
Click to expand...
Click to collapse
I will try that again.
If it works, how can you root without tripping the counter?
http://forum.xda-developers.com/archive/index.php/t-1758914.html
I can confirm this works! I'm on stock Bell not rooted and installed the OTA file and worked like a charm. Got 5178 in Quadrant right after update. Seems to be some issue with WidgetLocker not always engaging on the lock. Also the ebay app is constantly stop working so I uninstalled it for the time being. So far loving the changes
UPDATE: I guess eBay recalled the 2.0 update of their app so once I unistalled 2.0 and re-installed from the app store I am no longer having the crashing issues!
Who's going to try it on the AT&T SG3?
Works Amazing!
Confirm it works AMAZING!
Upgraded from the L1 patch earlier this week from Bell!
0 issues with any apps!
Smooth AS BUTTER!
NO MEMORY LEAK!
NO LAG!
VERY RESPONSIVE!
Only issue! Tethering is as the original post confirms not working.
Any fix would appreciate.
THANK YOU! HIGHLY RECOMMEND TO ALL BELL/VIRGIN S3ers!
*DAMN I HATED THAT L1 UPDATE! MADE MY PHONE SLOW AS HELL!*
it will fail on ATT when i verifies the system image. flash team insomnia's rom of this, it is modded in the build.prop for att.
I have noticed if you flash stock LH1 through MOBILE odin with ever root. the JB update will fail system verification.
But if you flash LH1 stock through regular odin it works like a charm.
Flash unrooted LH1 stock with odin
Boot into recovery and flash the JB update from external SD
Odin flash CWM.CWM_Recovery_6.0.1.2.tar (yes trips flash counter. but use triangle away app chickens.)
Use cwm to root with the CWM-SuperSU-v0.96.zip
Bluetooth audio for music doesn't come through my headset but call audio does
EDIT: After a reboot looks like Audio now comes through the headset. Not sure if it will always stay working but it's working for now
Trussello
Please make working CWM image out of this, aye! With root and about. This manual steps and Odin usage make me nervous. And everybody else.
TRusselo said:
it will fail on ATT when i verifies the system image. flash team insomnia's rom of this, it is modded in the build.prop for att.
Click to expand...
Click to collapse
team insomnia HAS a working rooted CWM image out of this... i said that in the post you quoted.
{09/11/2012}(V2)TeAm_InSoMnIa ARISTODEMOS JELLY BEAN BELLS NEW LEAK VLALI3
direct link....
http://team-insomnia.org/GalaxyS3ROMs.html (then click the jelly bean Tab)
and personally i prefer Odin to heimdall or cwm... i have used it on all my samsung devices hundreds of times with no real problems... odin works. odin is safe. odin is samsungs tool for loading firmware.
Can anybody confirm if this would work for telus? Heard that it does!
Sent from my SGH-I747M using xda premium
TRusselo said:
it will fail on ATT when i verifies the system image. flash team insomnia's rom of this, it is modded in the build.prop for att.
I have noticed if you flash stock LH1 through MOBILE odin with ever root. the JB update will fail system verification.
But if you flash LH1 stock through regular odin it works like a charm.
Flash unrooted LH1 stock with odin
Boot into recovery and flash the JB update from external SD
Odin flash CWM.CWM_Recovery_6.0.1.2.tar (yes trips flash counter. but use triangle away app chickens.)
Use cwm to root with the CWM-SuperSU-v0.96.zip
Click to expand...
Click to collapse
Thanks for the added info. Question: would re-flashing the stock unrooted LH1 with odin affect the counter? I'm thinking of doing that when the official JB OTA is out but would need to bring it to a state that Kies recognizes first.
RageATheM said:
Bluetooth audio for music doesn't come through my headset but call audio does
EDIT: After a reboot looks like Audio now comes through the headset. Not sure if it will always stay working but it's working for now
Click to expand...
Click to collapse
Can you give any more details on this? I just went down to try on my motorola hands free box, and media audio was disabled by default, so I enabled it. but with bluetooth on, the music player crashes, but works fine again when I disable bluetooth.
codo27 said:
Can you give any more details on this? I just went down to try on my motorola hands free box, and media audio was disabled by default, so I enabled it. but with bluetooth on, the music player crashes, but works fine again when I disable bluetooth.
Click to expand...
Click to collapse
I have the motorola S10-HD bluetooth headphones. They were already paired before I did the upgrade. After the upgrade the first time I turned them on, they auto synced to the phone as usual (including both media and phone checked in settings) but when I pressed play on my music it came through my phone speaker. Next I called the phone and answered with the headphones and audio came through the headphones. I rebooted the phone. Turned the headphones back on, auto connected and everything worked. I get no crashing just wasn't putting the audio through the right device at first.
{
"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 was able to get advanced calling back on my line. I was currently on Andy Bone's Fluent Rom but I lost my advanced calling feature when I first switched to Neo's Adrenaline Rom.
1) Log into your phones account on Verizon Wireless website, go to manage my apps and features and turn off advanced calling on your line.
2) The message from Verizon says to wait 15 minutes to see the changes take effect. During this time, I downloaded Dotatt's RUU.
3) RUU'd back to stock and then enabled the advanced calling feature on the PHONE
4) I did not restart my phone because it was downloading the OTA (2.xx to be specific). The OTA restarted the phone.
5) Advanced calling was back! Then I took the next OTA to 3.xxx
6) Advanced calling was still enabled, after the 3.xxx OTA, So then I installed TWRP/Root (all in one restart)
7) I then created a nandroid backup of my stock rooted configuration.
8) I then installed Andybone's deodexxed 5.1.1 Rom. (I wanted to install Fluent but I could not find confirmation that it works well with the new FW)
9) Now my phone is stock 5.1.1 with Xposed Modules installed and is running flawlessly with Advanced calling!!
The only reason I cared for advanced calling was because it would cut out my streaming music from Plex and then it would have trouble getting reconnected, now it never disconnects so when I receive calls i no longer have any issues.
Obviously your mileage may vary but I think this is an effective method of getting advanced calling back without having to send your phone into HTC.
Thanks for the post, I also lost advanced calling after a rom flash and have tried a similar process with no luck. I'll try again following your exact steps when i get the chance and report back.
Edit: No luck for me, followed the above steps exactly and still no advanced calling. I'd pretty much done the same before but just rebooted before applying the 1st OTA, tried again in the hopes that letting the ota install first would kick something in. Seems like some folks lose Volte permanently once it's gone with the only known resolution getting a replacement device. Guess i'm one of the lucky ones.
I may play with this some more but am giving up hope, and have not gotten very far with Verizon online support either. They just stated everything looked fine on their end after "looking into it" then closed the ticket, and just getting to that point took 3 different chat sessions with 3 different reps. I asked the last one I chatted with if this must be an issue with my specific device and if it should be replaced, to which the answer was a generic "well everything looks good so it should be working. if you have any more issues call 1-800-whatever" then they ended the session.
I was worried I had lost VoLTE for good, thanks for this. Worked like a charm! I can't stand not having data while in call. lol.
PrizmaticSmoke said:
Thanks for the post, I also lost advanced calling after a rom flash... have not gotten very far with Verizon online support either.... 3 different chat sessions with 3 different reps.
Click to expand...
Click to collapse
...and this is why Verizon works so hard to lock their phones down. Someone breaks a feature by loading non-VZW firmware, expects VZW to provide support for the phone, and gets mad (!!!) when VZW can't fix an issue of the user's own making.
mike.s said:
...and this is why Verizon works so hard to lock their phones down. Someone breaks a feature by loading non-VZW firmware, expects VZW to provide support for the phone, and gets mad (!!!) when VZW can't fix an issue of the user's own making.
Click to expand...
Click to collapse
You got me there, though i wouldn't really say that i'm "mad (!!!)" about losing VoLTE lol, just at VZW's support in general. I did my (very thorough) research before modifying anything on my device, and am not new to modifying devices or software. I was fully aware of the risks involved (including that some folks were reporting loss of VoLTE after device modifications) and pulled the trigger anyways, as the benefits outweigh the possible risks IMO.
But the truth is they don't know why it's broke, and if it could be fixed simply by sending me a new sim or a reconfiguration on their end of the network or something then I wanted to at least investigate. But their support for me has just been plain unhelpful in every way on numerous items, unless you like having scripted responses that aren't even relevant to your question/issue regurgitated to you at every turn.
And why do you have any sympathy in this scenario for the multi-billion dollar mega-corporation whose restrictions are what brought many of us here in the first place anyways? Maybe just playing devil's advocate?
If you're not mad, you shouldn't use the mad emoticon. If you break it, you own both pieces. It's unreasonable to expect them to know or spend any time trying to figure out why modified firmware breaks things. Can you point to someone who's always had stock firmware who's had VoLTE issues which VZW hasn't been able to fix?
mike.s said:
If you're not mad, you shouldn't use the mad emoticon. If you break it, you own both pieces. It's unreasonable to expect them to know or spend any time trying to figure out why modified firmware breaks things. Can you point to someone who's always had stock firmware who's had VoLTE issues which VZW hasn't been able to fix?
Click to expand...
Click to collapse
Nope. Didn't say I could.
more M9 Advanced Calling
If you know for sure that Advanced Calling is enabled on your line and it's not working now:
Just discovered that after 100% stock factory reset, then enable Advanced Calling on the phone, it will work perfectly
on first request. The feature will continue to work fine afterwards if you do not ever use TWRP recovery to do a complete
wipe of everything available to wipe.
To flash custom roms and nandroids (and have Adv. Calling still functioning) , only do the "Swipe to Factory Reset".
Then flash your favorite custom stuff.
Doing more wipe than that ruins the phone for Advanced Calling until there's been another factory reset done
with stock recovery and kernel.
michaelbsheldon said:
If you know for sure that Advanced Calling is enabled on your line and it's not working now:
Just discovered that after 100% stock factory reset, then enable Advanced Calling on the phone, it will work perfectly
on first request. The feature will continue to work fine afterwards if you do not ever use TWRP recovery to do a complete
wipe of everything available to wipe.
To flash custom roms and nandroids (and have Adv. Calling still functioning) , only do the "Swipe to Factory Reset".
Then flash your favorite custom stuff.
Doing more wipe than that ruins the phone for Advanced Calling until there's been another factory reset done
with stock recovery and kernel.
Click to expand...
Click to collapse
Has this been tried more than once? Just curious.
Sent from my HTC6535LVW using XDA Free mobile app
meandg5 said:
Has this been tried more than once? Just curious.
Sent from my HTC6535LVW using XDA Free mobile app
Click to expand...
Click to collapse
3 M9's on our family account: all 3 S-0ff and rooted.
Only 1 had HDVoice-Advanced Callling working correctly. Could not nandroid the
working system to one of the other phones with no HDVoice to get them running.
Did process above and got the 2 that weren't working to function correctly.
Took the original one whose HDVoice was good, did nandroid of it, did FULL MERCILESS
wipe on it and restored the nandroid. HDVoice no longer worked anymore.
Used dottat's files to restore to factory stock, got HDVoice working instantly,
then nandroided the previous backup that did not yield working HDVoice before, works again.
Now HDVoice works fine on all 3 devices. Proved to me that full wiping took away HDVoice.
So, I've lost VoLTE/Advanced calling on my m9. Not exactly sure when or what caused it. Not all that concerned. I have tried everything from RUU all the way back to 1.33.x and let it do the OTA updates up to MM as well as full wipes from stock recovery at every stage of the process. Or not wiping at all. If there is anything else someone would like me to try, I am more than willing to give it a shot. Would be nice to find a solution even though there probably isn't one except getting a replacement.
jsaxon2 said:
So, I've lost VoLTE/Advanced calling on my m9. Not exactly sure when or what caused it. Not all that concerned. I have tried everything from RUU all the way back to 1.33.x and let it do the OTA updates up to MM as well as full wipes from stock recovery at every stage of the process. Or not wiping at all. If there is anything else someone would like me to try, I am more than willing to give it a shot. Would be nice to find a solution even though there probably isn't one except getting a replacement.
Click to expand...
Click to collapse
Did you remove it from your account and then ruu and factory reset and attempt to add it from the phone again? If you did that exactly and nada it's time for replacement.
dottat said:
Did you remove it from your account and then ruu and factory reset and attempt to add it from the phone again? If you did that exactly and nada it's time for replacement.
Click to expand...
Click to collapse
Yep, tried that also. I've tried everything that has been posted and maybe even some other things. If there is anything off the wall that you want me to try, I'm game. Other than that, I'm just gonna keep it as I use CandySix which doesn't support VoLTE anyway and plan on getting m10 once it's out in a couple months.
jsaxon2 said:
So, I've lost VoLTE/Advanced calling on my m9. Not exactly sure when or what caused it. Not all that concerned. I have tried everything from RUU all the way back to 1.33.x and let it do the OTA updates up to MM as well as full wipes from stock recovery at every stage of the process. Or not wiping at all. If there is anything else someone would like me to try, I am more than willing to give it a shot. Would be nice to find a solution even though there probably isn't one except getting a replacement.
Click to expand...
Click to collapse
I've had two of my friends follow my instructions to the letter and both got Advanced Calling back.
I read somewhere that the full wipe is what causes the Advanced Calling to break (I'm 70 percent sure I read that somewhere and I am too lazy to find it)
So when you are trying to get it back via RUU and everything I would refrain from a "Full Wipe" and use "Factory Reset"
If all else fails send it to HTC
Threefifty said:
I've had two of my friends follow my instructions to the letter and both got Advanced Calling back.
I read somewhere that the full wipe is what causes the Advanced Calling to break (I'm 70 percent sure I read that somewhere and I am too lazy to find it)
So when you are trying to get it back via RUU and everything I would refrain from a "Full Wipe" and use "Factory Reset"
If all else fails send it to HTC
Click to expand...
Click to collapse
At what point did you Factory Reset? Or not at all? I am going to try again step by step. I just removed Advanced Calling via verizonwireless and downloaded dottat's ruu version 1.33.605.15 I am waiting for the 15 minutes to be up and I will install RUU via SDCard method.
Any other tips?
So, no luck with getting it working yet. I did the steps exactly, but no luck. I'm still not done though. Like I said, It doesn't really concern me that it's not working, but I'll keep trying to see if I can find a way to bring it back to life in case others have the issue.
jsaxon2 said:
At what point did you Factory Reset? Or not at all? I am going to try again step by step. I just removed Advanced Calling via verizonwireless and downloaded dottat's ruu version 1.33.605.15 I am waiting for the 15 minutes to be up and I will install RUU via SDCard method.
Any other tips?
Click to expand...
Click to collapse
I never really factory reset throughout my process.
However, I did RUU from the computer, not from SD card. I don't believe that is the case but if you're trying to replicate my steps exactly that's the only difference.
About once a week, not really sure on the frequency, (if I notice the popup) it says it rebooting the phone with two toggles on the bottom of the box. (box and lettering all in black and white) Your choice on the toggles is reboot or later. Today I push later and it it popped up twice more. But on the third time, there was not toggles and was doing a count down for reboot.
Anyway, before it rebooted, I pulled down the notifications and and found the notification and did a long press on it and then went into info. I then it looked like I was in settings with two choices there. (when on this settings, there was not back button to see were I was at in settings) To block notifications with on or off and the other doing something with quite mode. I turn off notifications and minimized the box. After it rebooted, the box was still minimized until wanted to bring it back up in the screen, it disappears. Anyone know what this is??? or know how to figure out what's doing it?
Stock Sprint Note 4 running 5.1.1 software Ok1 with hotspot hack (why I'm not running current software)
Open root browser and see if you have this folder: /carrier/ItsOn
If so, you may also have this file in dalvik (i think that's the proper location for Lollipop but you could search keyword itson) : /data/dalvik-cache/carrier @itson@[email protected]@classes.dex
If your ROM is fully stock, you may have another folder at /system/vendor/ItsOn. If so, look inside that folder for resource zip. Extract that zip and look in the folder and file install locations then browse to those in your phone's folders and delete all that correspond to that mapping.
If you have those, delete all you find and reboot. Hopefully that cures the random reboots.
If this applies, ItsOn has a bootstrapper that tries to install itself. If you have a custom kernel, it cannot complete this process but will try repeatedly to complete that failed setup process, prompting you continually reboot. If you were to factory reset, the prompts would most likely be more persistent.
If you flash a stock tar, then flash custom ROM and don't wipe internal memory, ItsOn remains unless developer has a script in place to remove that from root of your carrier folder.
Sent from my SM-N910P using Tapatalk
Thanks for the info. Phone is not rooted, bone stock with the exception of the hotspot hack.
Only thing I found using File Viewer under Root (/) folder /system/vender/Itson. And it shows nothing is in there and one year old.
I believe all this started when I upgrade Lollipop about one year ago. Was rooted at the time and wanted the newer android. Then I found out I did not need to root to get the hotspot working.
btb601 said:
Thanks for the info. Phone is not rooted, bone stock with the exception of the hotspot hack.
Only thing I found using File Viewer under Root (/) folder /system/vender/Itson. And it shows nothing is in there and one year old.
I believe all this started when I upgrade Lollipop about one year ago. Was rooted at the time and wanted the newer android. Then I found out I did not need to root to get the hotspot working.
Click to expand...
Click to collapse
OK. Check ItsOn status next. Goto /data/local/tmp and look for ItsOn log. It shouldn't get added on boot if you've removed it but last successful bootstrapper log will be present, unless deleted.
FWIW, I don't have random reboots on rooted phone. When I had them, ItsOn was the culprit. I usually clean install, wiping internal memory before and after stock tar but didn't coming from Lollipop.
What I noticed was that ItsOn showed in hidden menu ##data# as NetworkSystemProvider. See before and after wiping internal memory screenshots. I suspect this carried over from Lollipop. Perhaps yours did too?
{
"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"
}
Sent from my SM-N910P using Tapatalk
I could not find /data/local/tmp and look for ItsOn log, but I did get into data and the NetworkSystemProvider is there. Got into in and hit button for more settings and little window say "intent sent."
Also under more settings it says two things,
Module 1 is insmoded
Module 2 is insmoded
And at the top, it has a green icon for on button and a blacken icon for the off button. It will not let me do crap there.
Since it's stock, I have done nothing to it. Can't remember how I did the update. My guess since it was rooted, I had to flash OK1 myself but I don't see my stock download from Samsung. I have major memory issues, way more than I should at my age and I have no idea on how I did things......LOL And not even sure what Itson is, only thing I found with quick search a sprint software to add software and updates easily. That would explain the random downloads and install I did not do.
So now what, I need to root my phone to make this go away? Oh, and thanks again for your help. Don't go out or your way to dig further. I'm wanting to upgrade to MM but don't know much about it (rootable or hotspot wise).
The way I got rid of it was to wipe data and internal memory, flash marshmallow stock tar and wipe both again and flash a ROM that has it removed. Dunno but maybe it works the same way with a TWRP backup if you prefer stock with hotspot only?
I can't confirm there's another method or if that's your problem. But my random reboots are gone. FWIW, my log was inactive but had an existing log that dated months back. I only had a few random reboots until I did a factory reset to see if that would help. Once I did that, the reboots were much more frequent. Some boots were resulting in immediate request to reboot again. I had to do something at that point.
I couldn't tell you if updating to marshmallow makes it better but you could still could go back to Lollipop if it didn't.
I dunno if you need to root to make it go away but I can tell you there is hotspot mods for marshmallow. You can go back to Lollipop if you don't like marshmallow.
Sent from my SM-N910P using Tapatalk
Thanks again, guess I'll give marshmallow a try here real soon. Maybe even try a custom rom, never played with any of those. But I getting to where I'll have to do something soon. I feel it's picking up the pace. Then again, new Notes will be coming out soon. We'll see what Samsung brings us. Thanks again.
btb601 said:
Thanks again, guess I'll give marshmallow a try here real soon. Maybe even try a custom rom, never played with any of those. But I getting to where I'll have to do something soon. I feel it's picking up the pace. Then again, new Notes will be coming out soon. We'll see what Samsung brings us. Thanks again.
Click to expand...
Click to collapse
I've had this happen before and the only way I was able to get rid of it was to flash a completely stock tar and let the device provision itself thru initial setup. Others have had luck with the removal of ItsOn, but this has happened on ROMS where ItsOn wasn't even present.
ianmb said:
I've had this happen before and the only way I was able to get rid of it was to flash a completely stock tar and let the device provision itself thru initial setup. Others have had luck with the removal of ItsOn, but this has happened on ROMS where ItsOn wasn't even present.
Click to expand...
Click to collapse
Thanks, I do just that when I decide where to go from here.
Multi CSC Panama (TPA):
Since OTA "upgrade" (or update) to the official Android 12, all I have is trouble with the phone, issues that I didn't have before. I asked about it in this forum, either no one else experiences this or people refuse to answer.
Can I Factory Reset and go back to G975FXXSEFUL1? Anything specific I need to do, order of things, etc? (yes, I know I need to fully backup before).
Thank you.
Nope. It will still be on 12 however if you haven't done a factory reset since the upgrade, do so.
It may straighten it out. There's probably incompatible apps loaded. Don't use SmartSwitch to transfer apps on the reload.
You may be able to reflash it back to 11. A Samsung Experience center can also do it... if they want to.
In the future if you don't want OTA updates, disable it. That's one of the first things I disable.
blackhawk said:
Nope. It will still be on 12 however if you haven't done a factory reset since the upgrade, do so.
It may straighten it out. There's probably incompatible apps loaded. Don't use SmartSwitch to transfer apps on the reload.
You may be able to reflash it back to 11. A Samsung Experience center can also do it... if they want to.
In the future if you don't want OTA updates, disable it. That's one of the first things I disable.
Click to expand...
Click to collapse
Thanks @blackhawk .
So, if I download the 11 image from SamMobile for example, I cannot revert it back to 11 after a factory reset?
If not SmartSwitch, how do you suggest I bring apps back, one by one?
OTA update wasn't done automatically, I clearly could have reject it, I didn't imagine it would cause so many problems, the most serious of which is the phone re-boots out of the blue while I am on a call.
Not sure how to roll it back, sorry. I run stock and been lucky enough to have never had to reflash any of my devices. You're starting to understand why I almost never upgrade. My two N10+'s are still running on what was factory loaded, 9 and 10. No issues.
A reset may sort things out. 12 is causing a lot of cursing from what I'm reading.
If you load the apps from Playstore it should flag any that aren't compatible. For now use the factory loaded versions of the preloaded apps especially system apps. Update those carefully after the reload if at all.
So after a factory reset and another OTA update (right after reset) to G975FXXUEGVA2 - my phone still reboots out of the blue, always in the middle of calls.
My original problem returned quickly, which is while on a call I stop hearing the other party while they hear me loud and clear. I start hearing them again after a minute or so.
Then yesterday 2 days after full reset the crash/reboot problem started again.
I suppose something got screwed up in the phone "radio" or whatever it's called, a hardware issue.
No problems at all with Wifi calling such as WhatsApp audio calls, so it has to be with the cell part of the phone.
Again - it started after updating from 11 to 12.
Can someone weigh in if it's possible to force a downgrade back to official android 11?
Thanks.
sbi1 said:
So after a factory reset and another OTA update (right after reset) to G975FXXUEGVA2 - my phone still reboots out of the blue, always in the middle of calls.
My original problem returned quickly, which is while on a call I stop hearing the other party while they hear me loud and clear. I start hearing them again after a minute or so.
Then yesterday 2 days after full reset the crash/reboot problem started again.
I suppose something got screwed up in the phone "radio" or whatever it's called, a hardware issue.
No problems at all with Wifi calling such as WhatsApp audio calls, so it has to be with the cell part of the phone.
Again - it started after updating from 11 to 12.
Can someone weigh in if it's possible to force a downgrade back to official android 11?
Thanks.
Click to expand...
Click to collapse
Does it happen in safe mode?
If not it's likely an incompatible app.
Otherwise it may be a mobo failure. A rollback to 11 may bypass the damage.
If the bootloader was upgraded too a roll back is possible.
blackhawk said:
Does it happen in safe mode?
If not it's likely an incompatible app.
Otherwise it may be a mobo failure. A rollback to 11 may bypass the damage.
If the bootloader was upgraded too a roll back is possible.
Click to expand...
Click to collapse
I never go to safe mode, don't even know how to
I only loaded a handfull of apps after the reset to try and eliminate the issue. How do I go to safe mode?
Can't tell you anything about the bootloader, how do I check that? The upgrade was done OTA, all official firmware, no rooting or 3rd party stuff.
sbi1 said:
I never go to safe mode, don't even know how to
I only loaded a handfull of apps after the reset to try and eliminate the issue. How do I go to safe mode?
Can't tell you anything about the bootloader, how do I check that? The upgrade was done OTA, all official firmware, no rooting or 3rd party stuff.
Click to expand...
Click to collapse
Google for the safe mode sequence. I rarely use it.
[Guide] How to Read Firmware Information
Hello Members, Today I'm sharing a firmware guide with you in which you can read and know about your Firmware information. Basic Firmware Information Firmware information consists of 3 information. Build version, CSC version, and baseband version. Let's suppose that firmware search result...
r2.community.samsung.com
You can go the same or higher for the significant number in the bootloader but not lower.
In this case it's a 2.
{
"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"
}
blackhawk said:
Google for the safe mode sequence. I rarely use it.
[Guide] How to Read Firmware Information
Hello Members, Today I'm sharing a firmware guide with you in which you can read and know about your Firmware information. Basic Firmware Information Firmware information consists of 3 information. Build version, CSC version, and baseband version. Let's suppose that firmware search result...
r2.community.samsung.com
You can go the same or higher for the significant number in the bootloader but not lower.
In this case it's a 2.
View attachment 5544327
Click to expand...
Click to collapse
OK, so these are the four recent versions that I had, old to knew:
Android 11 - G975FXXSEFUJ2
Android 11 - G975FXXSEFUL1
Android 12 - G975FXXUEGULB (problem started with this one)
Android 12 - G975FXXUEGVA4 New update right after the reset.
Am I understanding correctly that E is the bootloader version on all 4?
sbi1 said:
OK, so these are the four recent versions that I had, old to knew:
Android 11 - G975FXXSEFUJ2
Android 11 - G975FXXSEFUL1
Android 12 - G975FXXUEGULB (problem started with this one)
Android 12 - G975FXXUEGVA4 New update right after the reset.
Am I understanding correctly that E is the bootloader version on all 4?
Click to expand...
Click to collapse
I believe so. Apparently they shifted to letters.
Someone else here on a S10 I think it was successfully rollback from 12 to 11.
A safer course might be to let a Samsung Best Buy Experience Center roll it back. They can also do advanced troubleshooting.
I avoid mucking with the firmware and so far haven't had any reason to.
Don't let it OTA updated again as they may update the bootloader and then you're boned...
blackhawk said:
I believe so. Apparently they shifted to letters.
Someone else here on a S10 I think it was successfully rollback from 12 to 11.
A safer course might be to let a Samsung Best Buy Experience Center roll it back. They can also do advanced troubleshooting.
I avoid mucking with the firmware and so far haven't had any reason to.
Don't let it OTA updated again as they may update the bootloader and then you're boned...
Click to expand...
Click to collapse
Well, I am boned either way
Thanks!
You're welcome.
Yeah it sucks. Malware is far easier to deal with than upgrades.
Was able to downgrade it back to 11, no crash yet, however my call issues are still going on (other side can hear me, I cannot hear other side), so it has to be a mobo issue. I installed only a handfull of apps for now but can't see how any of these apps cause it. These are all apps that I've been using before, major banks, WhatsApp, Waze, the minimal things I need. I guess a new phone it is.
sbi1 said:
Was able to downgrade it back to 11, no crash yet, however my call issues are still going on (other side can hear me, I cannot hear other side), so it has to be a mobo issue. I installed only a handfull of apps for now but can't see how any of these apps cause it. These are all apps that I've been using before, major banks, WhatsApp, Waze, the minimal things I need. I guess a new phone it is.
Click to expand...
Click to collapse
Try it in safe mode and do a network reset there, see if that works.
blackhawk said:
Try it in safe mode and do a network reset there, see if that works.
Click to expand...
Click to collapse
I tried safe mode but it doesn't help me because safe mode puts it in Airplane mode and you can't turn mobile data on or make calls.
Also, why would I need network reset if I just did a full factory reset?
sbi1 said:
I tried safe mode but it doesn't help me because safe mode puts it in Airplane mode and you can't turn mobile data on or make calls.
Also, why would I need network reset if I just did a full factory reset?
Click to expand...
Click to collapse
Did you test phone before loading the apps or updating any?
If a 3rd party app screwed it up already again.
WhatsApp I would never install... it only takes one. I doubt it's a hardware failure.
I did not test it. Some of the apps that I installed are needed for work and all of them, including WhatsApp, I have had for years. I am pretty sure it's a hardware failure as well.
You need to be methodical and not make assumptions. 3rd party apps can cause a lot of issues. It's more likely a 3rd party app than a hardware failure but only one way to know which it is. Something changed...
But there were no changes to apps when it started, just an update to android 12. And any recent app that I installed in the days/weeks prior to the update is not on the phone now.
sbi1 said:
But there were no changes to apps when it started, just an update to android 12. And any recent app that I installed in the days/weeks prior to the update is not on the phone now.
Click to expand...
Click to collapse
You need to factory reset and before you install any 3rd party apps see if it's functioning normally.
If you suspect an app is causing the problem uninstall it. This doesn't always work.
Rarely a poorly written app can change settings that aren't user accessible and fail to change them back. A factory reset is the only way to correct this.
{
"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"
}
PixelExperience for Google Pixel 6 Pro[raven]
What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher mod, wallpapers, icons, fonts, boot animation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 12.1
Whats working?
Everything I believe
Known issues
Not sure, none so far
DON'T FLASH GAPPS, IT IS ALREADY INCLUDED
Download
Install instructions
From custom recovery
** If not already installed, please download vendor_boot.img & flash via fastboot ( fastboot flash vendor_boot "location to downloaded file" ), then select boot recovery in fastboot after flash in finish.
vendor_boot.img
1. Factory Reset
2. Apply Update via ADB, sideloading the downloaded file
3. Reboot to bootloader
4. Apply Magisk Boot ( Patched Magisk Boot v25.2 )
5. Start
Donate
Not needed but always welcomed
Keep in touch
Telegram channel
PixelExperience blog
Android OS version: 12.1
Kernel Source
Awesome to see PE on the 6 Pro! Any chance it becomes Raviole or if there will be a Pixel 6 Oriole build as well?
Pixel-ception right there, experiencing Pixel on a Pixel lol
Always wanted to get a pixel experience on my pixel!
device and kernel source ?
@alvin14
​
Can someone who's tested this post a couple of screenshots of any special settings this might have over stock? I mostly want to compare those against DerpFest that was released a couple of days ago and to avoid flashing again since we don't have a way to backup and restore a rom at this point. Unless - could Slot B be used to dual boot two different roms?
Ulyaoth said:
Can someone who's tested this post a couple of screenshots of any special settings this might have over stock? I mostly want to compare those against DerpFest that was released a couple of days ago and to avoid flashing again since we don't have a way to backup and restore a rom at this point. Unless - could Slot B be used to dual boot two different roms?
Click to expand...
Click to collapse
Currently, you cannot dual boot multiple roms. I remember with OP6T, there was a guy/gal that provided us with a recovery that allowed dual boot for two different roms. It was a wip, but functioned pretty well. Can't recall the Dev's name.
Concerning screenshots of custom settings, I'm sure it's similar to other Pixel Experience roms for other devices. I can't provide any, because I'm not using this particular custom rom at the moment.
@alvin14 Please check your PM inbox. Thank you.
-Regards: Badger50
@alvin14, to sideload you'll need to provide both the boot.img and vendor_boot.img, otherwise we can't use adb sideload since stock recovery will reject it and it's looking pretty unlikely we'll get twrp anytime soon. For those of us who are technically minded, grabbing the 2 .img files I mentioned isn't too hard, but I'm guessing there's some who likely can't.
Also, you might want to provide your kernel source as per XDA rules like the mod has likely PMed you about. This thread will likely get removed/locked and your links taken down if you don't.
Sorry, have not done this since the S4. Kernel source added, forked from PE-Raven. Other files added as well. Not much options added to pixel experience, I personally prefer stock android which i did some development on about 8 years ago. Just light modifications added, very stable.
alvin14 said:
Sorry, have not done this since the S4. Kernel source added, forked from PE-Raven. Other files added as well. Not much options added to pixel experience, I personally prefer stock android which i did some development on about 8 years ago. Just light modifications added, very stable.
Click to expand...
Click to collapse
For the vendor_boot.img to even boot recovery, you need the boot.img from your build as well. Stock boot.img won't work in almost all cases of custom roms.
Appreciate the work, and newer devices are kind of a pain to know what to do. So I feel ya there.
dragynbane222 said:
For the vendor_boot.img to even boot recovery, you need the boot.img from your build as well. Stock boot.img won't work in almost all cases of custom roms.
Appreciate the work, and newer devices are kind of a pain to know what to do. So I feel ya there.
Click to expand...
Click to collapse
Boot not needed. After flashing vendor_boot via fastboot you can select boot bootloader and it goes straight in. Magisk Boot is also provided should anyone still need the boot image.
Ulyaoth said:
Can someone who's tested this post a couple of screenshots of any special settings this might have over stock? I mostly want to compare those against DerpFest that was released a couple of days ago and to avoid flashing again since we don't have a way to backup and restore a rom at this point. Unless - could Slot B be used to dual boot two different roms?
Click to expand...
Click to collapse
Isn't most things backed up online lately? Before every custom ROM flash, backup your data to Google & restore after flash. Don't really use much apps however I would believe they all offer online backup via Google. Signing back into everything should be a breeze since your passwords are also backed up wether to Google or whichever backup app used for that with auto sign in activated.
alvin14 said:
Isn't most things backed up online lately? Before every custom ROM flash, backup your data to Google & restore after flash. Don't really use much apps however I would believe they all offer online backup via Google. Signing back into everything should be a breeze since your passwords are also backed up wether to Google or whichever backup app used for that with auto sign in activated.
Click to expand...
Click to collapse
Yeah but there's still things that are either not backed up or not restored. For example call logs and device settings are backed up but they've never successfully restored on any of my devices. Then there are things like the pixel launcher home screen layout, signing in to apps, setting my ringtone etc., setting up a multilingual keyboard and so on. The ideal scenario for me is to be able to switch roms without wiping data, but I need to have a backup fallback or else it's going to take me hours of tweaking and setting management to be comfy(not to mention any ROM-specific settings that have crazy amounts of time-consuming customizations)
Ulyaoth said:
Yeah but there's still things that are either not backed up or not restored. For example call logs and device settings are backed up but they've never successfully restored on any of my devices. Then there are things like the pixel launcher home screen layout, signing in to apps, setting my ringtone etc., setting up a multilingual keyboard and so on...
Click to expand...
Click to collapse
I had to comment here because this is both true and not true. The backups seem to work, however, they usually don't restore ALL of said data when you restore from a backup onto a wiped phone. Oddly enough, when I wiped my phone yesterday and updated to the final Android 13 beta build (A13B4.1), I was able to restore my data and it kept all of my settings intact... So, not only did I get all of my apps back (and put onto the home screen in the correct locations), but I also got my home screen wallpaper set again; I got my QS tile's arranged how I had previously customized them and I got my other settings restored to how they were...
I'm not entirely sure why this occured, however, with a few past beta updates I had lost all of the settings that I had mentioned... I would usually only get my apps restored (without them being placed on the home screen at all)...
One thing to note is that I happened to do this update differently than a bunch of my previous updates. I did this update manually over adb instead of using the Android Flash Tool site. Of course, take this with a grain of salt as I'm not entirely sure if this is what made my backup restore yesterday so perfect. But my only thought is that by doing the update manually, you won't be missing out on any of the fastboot commands that may be dismissed via the Android Flash Tool
Wifi calling is missing in action..
yyz71 said:
Wifi calling is missing in action..
Click to expand...
Click to collapse
I don't have that feature in my country so I never looked into that.
Thanks will look into it.
alvin14 said:
I don't have that feature in my country so I never looked into that.
Thanks will look into it.
Click to expand...
Click to collapse
Thanks great ROM
BMHater12 said:
Pixel-ception right there, experiencing Pixel on a Pixel lol
Click to expand...
Click to collapse
dex2grigg said:
Always wanted to get a pixel experience on my pixel!
Click to expand...
Click to collapse
Awesome contribution! For all you give to the community i would like to buy you both lunch!
What is it exactly that trolls eat by the way?
NippleSauce said:
I had to comment here because this is both true and not true. The backups seem to work, however, they usually don't restore ALL of said data when you restore from a backup onto a wiped phone. Oddly enough, when I wiped my phone yesterday and updated to the final Android 13 beta build (A13B4.1), I was able to restore my data and it kept all of my settings intact... So, not only did I get all of my apps back (and put onto the home screen in the correct locations), but I also got my home screen wallpaper set again; I got my QS tile's arranged how I had previously customized them and I got my other settings restored to how they were...
I'm not entirely sure why this occured, however, with a few past beta updates I had lost all of the settings that I had mentioned... I would usually only get my apps restored (without them being placed on the home screen at all)...
One thing to note is that I happened to do this update differently than a bunch of my previous updates. I did this update manually over adb instead of using the Android Flash Tool site. Of course, take this with a grain of salt as I'm not entirely sure if this is what made my backup restore yesterday so perfect. But my only thought is that by doing the update manually, you won't be missing out on any of the fastboot commands that may be dismissed via the Android Flash Tool
Click to expand...
Click to collapse
I recommend Swift Backup. I've been using it for quite awhile and it backs up everything!! Call logs, messages, apps and their data. You can backup to the device and transfer to pc for safe keeping or you can even have the option to backup and restore from the cloud. You can also do what I do and get a OTG cable and backup and restore right from that which is much faster.