I'm using a Verizon Galaxy Nexus. For half a year now I've been missing every all-day event that I don't have a reminder setup for because the 4.0.2 calendar widget had a bug that wouldn't display them. There was a thread on here about it, and the bug was fixed in the next version that launched in 4.0.3. As you all know however, Verizon has been downright sinful in their slowing of updates to this "flagship Google device". So, I have yet to see all-day events on my calendar widget.
I don't want to unlock my bootloader. I don't want to root (been there, done that on my Droid. No need to try to convince me of the merits.). I don't want to use a different calendar widget. I just want the stock calendar widget to work.
Is it possible to just compile an apk for the calendar widget from 4.0.4 and install it to my phone to hold me over until the 4.0.4 OTA lands?
Or download Android Agenda Widget, which is virtually identical, fully customisable and displays all day events without a hitch
!!11oneone said:
Or download Android Agenda Widget, which is virtually identical, fully customisable and displays all day events without a hitch
Click to expand...
Click to collapse
Thanks. I'll consider it in the interim.
Is there really no way to just compile the apk for the 4.0.4 calendar widget. It's open source, no?
I've switched to Android Agenda Widget to hold me over. However, this is still an interesting question in general. Can you compile individual apps, widgets, etc. from the Android sources? I'll give this a last bump and keep my fingers crossed.
jedidove said:
Thanks. I'll consider it in the interim.
Is there really no way to just compile the apk for the 4.0.4 calendar widget. It's open source, no?
Click to expand...
Click to collapse
Just pulling the calendar APK from 4.0.4 and putting on 4.0.2 isn't going to work I don't think. It does a check to make sure that you're on 4.0.4 because surely the changes it has rely on other changes to the system that come w/ 4.0.4.
martonikaj said:
Just pulling the calendar APK from 4.0.4 and putting on 4.0.2 isn't going to work I don't think. It does a check to make sure that you're on 4.0.4 because surely the changes it has rely on other changes to the system that come w/ 4.0.4.
Click to expand...
Click to collapse
Ah, excellent point. Thanks, I hadn't thought of that.
given no-root, what u require may not be possible. Calendar app is not an independent apk which needs two or three cooperative parts to work properly. changing calendar.apk means u must change the "adapter app" which requires root previlege
qwsdert4 said:
given no-root, what u require may not be possible. Calendar app is not an independent apk which needs two or three cooperative parts to work properly. changing calendar.apk means u must change the "adapter app" which requires root previlege
Click to expand...
Click to collapse
I miss the old days when applying an OTA ahead of schedule was as simple as moving the signed update.zip to the sd card, then telling the stock recovery to update with it.
jedidove said:
I miss the old days when applying an OTA ahead of schedule was as simple as moving the signed update.zip to the sd card, then telling the stock recovery to update with it.
Click to expand...
Click to collapse
That's still true now... you can flash with fastboot, even easier.
martonikaj said:
That's still true now... you can flash with fastboot, even easier.
Click to expand...
Click to collapse
I've been put under the impression that you need to unlock the bootloader (unless you have root) first. For me, anything that requires wiping and performing a cover up or undoing before returning a possibly damaged phone in the future is as out of the way as rooting. Am I mistaken about this?
EDIT: I should note that I've been through the whole rooting thing before, custom roms, etc. etc. but I've just grown to like the simplicity of a completely stock Nexus device that I don't need to tinker with. I just came to have too much going on to worry about updating ROM's, tweaking, flashing recoveries, and such.
jedidove said:
I miss the old days when applying an OTA ahead of schedule was as simple as moving the signed update.zip to the sd card, then telling the stock recovery to update with it.
Click to expand...
Click to collapse
actually when I first got an android phone, I would flash third party ROMs at once so I dont have any idea of ur "old days". waiting for OTA sounds a little bit "passive" isn't it?
qwsdert4 said:
actually when I first got an android phone, I would flash third party ROMs at once so I dont have any idea of ur "old days". waiting for OTA sounds a little bit "passive" isn't it?
Click to expand...
Click to collapse
I know, I know lol... Like I said, I don't wan't to make this a thread about the merits of rooting. I totally get it. Just doesn't fit what I need right now.
It looks like the OTA is set to launch soon (tomorrow?) anyway. However, I'm sure I'm going to run into some aggravation with this in the future and end up rooting to get the next BIG update (4.1, or whatever). So, just for clarification in case my last post got buried at the end of the last page, you *do* have to at least unlock your bootloader to flash signed OTAs without root, right?
jedidove said:
I've been put under the impression that you need to unlock the bootloader (unless you have root) first. For me, anything that requires wiping and performing a cover up or undoing before returning a possibly damaged phone in the future is as out of the way as rooting. Am I mistaken about this?
Click to expand...
Click to collapse
Well yes, of course the bootloader has to be unlocked.
It really sounds like you should just wait for the OTA.
---------- Post added at 08:10 PM ---------- Previous post was at 08:09 PM ----------
jedidove said:
It looks like the OTA is set to launch soon (tomorrow?) anyway.
Click to expand...
Click to collapse
Don't count on it. I'm sure its coming soon, but I highly doubt it'll be tomorrow.
martonikaj said:
Well yes, of course the bootloader has to be unlocked.
It really sounds like you should just wait for the OTA.
Click to expand...
Click to collapse
Okay, thanks. I'm just going to wait on this one. When Verizon undoubtedly withholds a much bigger update in the future, I'll free this phone. But for now, it's just not worth it to me.
Don't count on it. I'm sure its coming soon, but I highly doubt it'll be tomorrow.
Click to expand...
Click to collapse
I know...I'm not holding my breath.
jedidove said:
I know, I know lol... Like I said, I don't wan't to make this a thread about the merits of rooting. I totally get it. Just doesn't fit what I need right now.
It looks like the OTA is set to launch soon (tomorrow?) anyway. However, I'm sure I'm going to run into some aggravation with this in the future and end up rooting to get the next BIG update (4.1, or whatever). So, just for clarification in case my last post got buried at the end of the last page, you *do* have to at least unlock your bootloader to flash signed OTAs without root, right?
Click to expand...
Click to collapse
No I've never heard any requirements of rooting by any OTAs. OTAs are designed for a fully automatic, without-bother experience. OTA packages has official encryption codes in it so they do pass an locked bootloader. if cumstomers are told to unlock the bootloader before performing an official OTA, the manufacturer must be crazy
qwsdert4 said:
No I've never heard any requirements of rooting by any OTAs. OTAs are designed for a fully automatic, without-bother experience. OTA packages has official encryption codes in it so they do pass an locked bootloader. if cumstomers are told to unlock the bootloader before performing an official OTA, the manufacturer must be crazy
Click to expand...
Click to collapse
I thought so too...but apparently you need to unlock the bootloader to manually apply an OTA from a zip. I would love it if someone came in here and proved me wrong, because it seems asinine that Verizon has gone this far in their freedom-denying practices.
jedidove said:
I thought so too...but apparently you need to unlock the bootloader to manually apply an OTA from a zip. I would love it if someone came in here and proved me wrong, because it seems asinine that Verizon has gone this far in their freedom-denying practices.
Click to expand...
Click to collapse
Its not Verizon. Its the exact same way on the GSM model. You need to unlock the bootloader to do Fastboot flash commands, or need to be rooted (which requires unlocked bootloader) to put it in the cache and update manually.
martonikaj said:
Its not Verizon. Its the exact same way on the GSM model. You need to unlock the bootloader to do Fastboot flash commands, or need to be rooted (which requires unlocked bootloader) to put it in the cache and update manually.
Click to expand...
Click to collapse
I realize the subtleties, but I'm making a broad claim about the practice among other phones as well. Verizon has stood out in extreme support of locked bootloaders to the FCC and others, has made unlocking a bootloader a "violation" of their terms, and has undoubtedly pressured manufactures to lock bootloaders for Verizon bound phones. They certainly don't get away scott-free in my book when it comes to this topic.
jedidove said:
I thought so too...but apparently you need to unlock the bootloader to manually apply an OTA from a zip. I would love it if someone came in here and proved me wrong, because it seems asinine that Verizon has gone this far in their freedom-denying practices.
Click to expand...
Click to collapse
It seems that I didn't quite get u (before this post) because my mother tongue is not English. yes u need to unlock the bootloader before manually apply an OTA package.
returning to the calendar thing, have u set up a default event notifying method in calendar? or try to reset to factory and see if the problem still exists. didn't encounter this issue before
qwsdert4 said:
It seems that I didn't quite get u (before this post) because my mother tongue is not English. yes u need to unlock the bootloader before manually apply an OTA package.
returning to the calendar thing, have u set up a default event notifying method in calendar? or try to reset to factory and see if the problem still exists. didn't encounter this issue before
Click to expand...
Click to collapse
Ah, np.
Yes. It's a well documented issue. http://forum.xda-developers.com/showthread.php?t=1391191 Just have to wait for the *long* overdue update. For now, Agenda Widget is doing fine. I'll probably switch back though when I get 4.0.4.
Related
Hi,
I have a stock Wildfire which I'm perfectly happy with. However, over time I purchased a few apps from the market and would like to take a backup.
What can I do? My ideal would be a simple application with which to switch on/off root permissions before starting the backup process - read-only access to the system and data partition would be perfectly sufficient.
Is this possible? I read about Temp Root in the forums, but couldn't find a clear statement which way (if any) would work on the Wildfire. Also, is read-only root with access to all partitions even possible without flashing or do I need a custom ROM for this?
As I understand, another way would be to flash a new recovery image and use Nandroid backup. However, I'd rather avoid flashing anything.
I'd be glad if someone could give me a few pointers.
Get Visionary+. This app can do a temp root easily.
It's meant for Desire Z, but it still works. If you want permroot then use AlphaRevX instead, the method this app uses does not apply to Wildfire.
For backing up I would recommend Titanium Backup.
Why would you want to temproot anyway? You can use AlphaRevX to get S-OFF and flash custom ROMs.
If you want to do warranty return, just use a RUU tool. It clears everything back to factory state.
Just wondering why you want to backup the paid apps? Can't you just reinstall them when needed as your license is on your Google account right?
Sent from my HTC Desire S using Tapatalk
YES, no need to backup the paid apps purchased from market.
Even after hard reset, if u use the same google market account to install those apps, ur licence should be back. Licence should be stored in your account AFAIK....
xc1024 said:
If you want to do warranty return, just use a RUU tool. It clears everything back to factory state.
Click to expand...
Click to collapse
A ruu doesn't reset the s-off state! The only way you can flash a new hboot is when it has a version higher the the 6.x hboot that alpharevx puts on your phone. It just like htc's hboot: you cannot downgrade it.
If you want s-on again, you need a tool from AlphaRev that does it for you. But I don't know if that is released yet.
bharatgaddameedi said:
YES, no need to backup the paid apps purchased from market.
Click to expand...
Click to collapse
It is? Super, somehow it never occured to me that the purchase could be tied to the account instead of to the phone. Thanks for the hint!
That solves my immediate problem, I guess I can forgo a backup then.
What would happen if I entered the same googlemail-account into a new phone: Would the old one be deactivated then? One might want to use the same mail account on two or more phones. Would he then also get access to all of the applications on all phones, or would it simply not work at all?
Even after hard reset, if u use the same google market account to install those apps, ur licence should be back. Licence should be stored in your account AFAIK....
Click to expand...
Click to collapse
I never entered a "google market account" ID, I guess my googlemail-account (which I created on setting up the phone for the first time) was used for that automatically. Or has such an account been automatically created for me without any further prompting?
Regards,
150d
xc1024 said:
Get Visionary+. This app can do a temp root easily.
Click to expand...
Click to collapse
Thanks, I'll remember that.
Why would you want to temproot anyway? You can use AlphaRevX to get S-OFF and flash custom ROMs.
Click to expand...
Click to collapse
That's just it: the phone is working great, I'm really not missing anything. I wouldn't even know what to use root for. ;-)
On the other hand, I have a little experience with cooked ROMs from my previous phone, a WM-based Kaiser. Granted the two might not be directly comparable, but back then I had a lot of issues with stability, working-but-not-perfect bootloader, GPS sensitivity, radio ROMs...
I'd rather not take any chances now, at least not until I have a good reason to do so.
Regards,
150d
150d said:
On the other hand, I have a little experience with cooked ROMs from my previous phone, a WM-based Kaiser. Granted the two might not be directly comparable, but back then I had a lot of issues with stability, working-but-not-perfect bootloader, GPS sensitivity, radio ROMs...
I'd rather not take any chances now, at least not until I have a good reason to do so.
Regards,
150d
Click to expand...
Click to collapse
And it always should be this way this wilfire forum is getting stalked by people who want root and new ROMs, but i'll bet that most of them will be satisfied with the stock one.
The only reason why you should root is to install usefull apps that requier root (like titanium backup) and to install new ROMs. Those roms provide updates that htc disable for us: gingerbread should be more powerfull and JIT, something that can make your phone two to three times faster, is disabled because sense can't handle it. But you are right: custom roms will never be bugg free. But on the other hand, the stock rom isn't bugg free as well
Altough I'm on the stock rom ATM, I will change if I have the time. "Basic" things like gps and stuff will work on most roms (unless reported otherwise), so you do not have to be afraid of that. The most problematic things can always be solved, but most of the time it requiers a lot of time untill you have figured out what exactly you should do to solve your problem. So do not try to change rom if you do not have the time for it.
To finalize this off topic statement: it is usefull to gain root: you can do much more with it than just "flash roms". But it absorbs a lot of time, and you shouldn't start with it if you do not have any. But when you commit yourself to it, you will gain a lot.
Erwin
150d said:
What would happen if I entered the same googlemail-account into a new phone: Would the old one be deactivated then? One might want to use the same mail account on two or more phones. Would he then also get access to all of the applications on all phones, or would it simply not work at all?
I never entered a "google market account" ID, I guess my googlemail-account (which I created on setting up the phone for the first time) was used for that automatically. Or has such an account been automatically created for me without any further prompting?
Regards,
150d
Click to expand...
Click to collapse
Don't know about that thing. They shouldn't be discussed too anyway. But I strongly think that google knows the device identity of the market attached account.
Yes, google account / gmail account / maket account all are the same.
edit : And better not to speak about cooked roms untill u check them. There are many people pretty much satisfied with those.
ErwinP said:
And it always should be this way this wilfire forum is getting stalked by people who want root and new ROMs, but i'll bet that most of them will be satisfied with the stock one.
Click to expand...
Click to collapse
I saw a TV spot when the first iPad was released. They interviewed a guy waiting in line in front of an Apple store for why he wanted an iPad. He said: "I don't even know what it is, but I'm sure I need it!"
One can only wish for customers like that!
Those roms provide updates that htc disable for us: gingerbread should be more powerfull and JIT, something that can make your phone two to three times faster, is disabled because sense can't handle it.
Click to expand...
Click to collapse
I didn't know that. Yes, sometimes I do wish it would be quicker to handle, I have a feeling that sometimes the CPU is maxed out so it can't handle the touch screen any more. But to me it's only a minor hassle.
To finalize this off topic statement: it is usefull to gain root: you can do much more with it than just "flash roms". But it absorbs a lot of time...
Click to expand...
Click to collapse
I believe it, both of it. I've owned the phone for about half a year now and I'm still adjusting to how much more it can do for me than my old phone could. It goes beyond just having an application to do some job - it all is much more "usable" than before. But I can really, really not imagine what else I would like to do with the phone. Maybe there is something that I can't even think of now, but so far... ;-)
Regards,
150d
My bootloader is still locked and I've never had root on this phone got it too late to unlock. I'd like to root and if I can get a custom recovery and flash a rom. Can anyone help?
Sent from my XT907 using Xparent Cyan Tapatalk 2
Gblake13 said:
My bootloader is still locked and I've never had root on this phone got it too late to unlock. I'd like to root and if I can get a custom recovery and flash a rom. Can anyone help?
Click to expand...
Click to collapse
Right now, there is no way to root or unlock the bootloader in your situation. It sucks, but it's where we are.
Don't hold your breath for an exploit, either. Motorola/Verizon closed all known holes for BL-unlocking in the penultimate Jellybean OTA, and the only root method that worked in the last JB no longer works here.
Enough with the KK unlock and root threads.
I'm going to start reporting people that make these threads without doing some homework first.
If you have a locked bootloader, you're pretty much up the creek without a paddle. End of discussion
If there is an exploit available, trust me, you'll know about it.
gtmaster303 said:
Enough with the KK unlock and root threads.
I'm going to start reporting people that make these threads without doing some homework first.
If you have a locked bootloader, you're pretty much up the creek without a paddle. End of discussion
If there is an exploit available, trust me, you'll know about it.
Click to expand...
Click to collapse
We can say this in every thread where they ask about root. We put warnings out prior to the OTA. Heck, we could probably put a sticky thread in this section about there being no root on KK, yet people will still ask. Why? Because they refuse to take 5 minutes to read through the other 37 KK related threads.
RikRong said:
We can say this in every thread where they ask about root. We put warnings out prior to the OTA. Heck, we could probably put a sticky thread in this section about there being no root on KK, yet people will still ask. Why? Because they refuse to take 5 minutes to read through the other 37 KK related threads.
Click to expand...
Click to collapse
I of course can't speak for anyone else, but I knew the risks well before taking the update, and updated anyway.
I knew it was the very un-XDA thing to do, but frustration with the short battery life and UI lag on my phone was nearing a breaking point.
I tried to make the most of it; hence the "list of changes" thread, which hopefully has scared away locked users who are still n JB.
Any luck with a rootkeeper/root survival of any kind?
pnwsr6 said:
Any luck with a rootkeeper/root survival of any kind?
Click to expand...
Click to collapse
Haven't seen it yet.
Strife89 said:
I of course can't speak for anyone else, but I knew the risks well before taking the update, and updated anyway.
Click to expand...
Click to collapse
My story is somewhat different. I tried to find a way to get rooted KK on my phone (trying to play junior hacker again), ended up soft-bricking my phone to where the only way to fix it was to flash stock KK using RSDLite (did try RSD'ing JB first, but my bootloader was having none of that).
So now I'm hopelessly stuck with a completely stock phone without root.
I feel like the only way to get past this is to attack it politically, like if every single Verizon XDA user banded together and flooded Verizon corporate inboxes with legitimate reasons why we need unlocked bootloaders.
Or maybe if someone is good friends with a politician who is more left of center and concerned about consumer rights over corporations. Maybe convince them that it's better for the environment because potentially millions of phones could be saved from going into landfills if we mandate companies must allow bootloader to be unlocked when certain conditions are fulfilled, like if a phone reaches 1-year of age.
Strife89 said:
I of course can't speak for anyone else, but I knew the risks well before taking the update, and updated anyway.
I knew it was the very un-XDA thing to do, but frustration with the short battery life and UI lag on my phone was nearing a breaking point.
I tried to make the most of it; hence the "list of changes" thread, which hopefully has scared away locked users who are still n JB.
Click to expand...
Click to collapse
I new I was losing root with it as well. I liked the features that KK brought with the update and still did it. The update finally got me using Smart Actions and I'm getting pretty decent battery life, nothing mind blowing, but pretty good. Buying a portable battery pack has pretty much solved the problem I had with nonroot. Now I can go about 2 days as long as I carry it around, lol. Luckily it's small.
if I have an unlocked BL, and the latest stock version on KK, how would I get root? Is it possible?
thanks.
Ahoalton said:
if I have an unlocked BL, and the latest stock version on KK, how would I get root? Is it possible?
thanks.
Click to expand...
Click to collapse
Flash a custom recovery via fastboot, and then flash SuperSU zip in recovery.
http://forum.xda-developers.com/moto-x/orig-development/root-4-4-x-pie-motorola-devices-t2771623 <-- this thread (not saying it works) is getting popular with Motorola devices. I attempted it myself and got errors just like some other people. Only difference is they still had root and I don't. I suggest following the thread and seeing if it does someday work for us or somebody could attempt it themselves. I'm currently on windows 8.1 so that could be a problem.
megaghostgamer said:
http://forum.xda-developers.com/moto-x/orig-development/root-4-4-x-pie-motorola-devices-t2771623 <-- this thread (not saying it works) is getting popular with Motorola devices. I attempted it myself and got errors just like some other people. Only difference is they still had root and I don't. I suggest following the thread and seeing if it does someday work for us or somebody could attempt it themselves. I'm currently on windows 8.1 so that could be a problem.
Click to expand...
Click to collapse
^^^He doesn't need an exploit since he has an unlocked BL. Also, this has been checked on the M and HD family of devices, it WILL NOT work because the the current KK updates have already patched the hole that this exploit is meant to take advantage of.
Ahoalton said:
if I have an unlocked BL, and the latest stock version on KK, how would I get root? Is it possible?
thanks.
Click to expand...
Click to collapse
Yes!.. Just use URL="http://androidhosting.org/Devs/Dhacker29/msm8960/CWM6049-RAZR-HD_M-KITKAT.img"]custom recovery[/URL] and flash Superuser zip
And what about aka test points? Many Motorola models had such special test points using which you could get unlock of BL. How about our XT907? Any ideas about test points or shortcircuit of contacts?
No need now! Towelroot will root stock KK, and what magic it does allows Motopocalypse to unlock BL again.
http://www.droid-life.com/2014/06/16/motorola-bootloader-unlock-razr-hd-towelroot/
Confirmed working!
Root and bootloader unlock!
Sent from my Droid RAZR M
GnatGoSplat said:
No need now! Towelroot will root stock KK, and what magic it does allows Motopocalypse to unlock BL again.
Click to expand...
Click to collapse
Towel Root only allows the root access that Motopocalypse needs. The old trust zone was accidentally (or purposely) put back into this OTA, that's what Motopocalyse exploits.
Sent from my HTC6525LVW using Tapatalk
RikRong said:
Towel Root only allows the root access that Motopocalypse needs. The old trust zone was accidentally (or purposely) put back into this OTA, that's what Motopocalyse exploits.
Click to expand...
Click to collapse
Ah, I see. Good to know. :good:
Hello guys and gals, we are coming closer to the update which I strongly believe will mess around with our phones to force a return. How can we stop this update on a device already up to date? Do far I have tried package disabler but it doesn't show system update 1 and system update 2... Any suggestions?
seriousc said:
Hello guys and gals, we are coming closer to the update which I strongly believe will mess around with our phones to force a return. How can we stop this update on a device already up to date? Do far I have tried package disabler but it doesn't show system update 1 and system update 2... Any suggestions?
Click to expand...
Click to collapse
You could root your phone
LightningJay said:
You could root your phone
Click to expand...
Click to collapse
I am rooted and I know usually that would help but do we know that just by being rooted this would stop the update? Would a custom rom also stop this update? How well do we know samsung's tactic here I mea if they REALLY wanted to could they ignore root or custom rom an overwrite or is this not possible?
seriousc said:
I am rooted and I know usually that would help but do we know that just by being rooted this would stop the update? Would a custom rom also stop this update? How well do we know samsung's tactic here I mea if they REALLY wanted to could they ignore root or custom rom an overwrite or is this not possible?
Click to expand...
Click to collapse
I'm really not sure...
I installed a custom ROM so I would think that Samsung couldn't push an update to it, but I’m new to Samsung/Android (Note7 is my first Android) so I could be mistaken.
LightningJay said:
I'm really not sure...
I installed a custom ROM so I would think that Samsung couldn't push an update to it, but Iâ??m new to Samsung/Android (Note7 is my first Android) so I could be mistaken.
Click to expand...
Click to collapse
Same. I installed Hydra-Rom (excellent rom btw) and then uninstalled all update packages with Titanium Backup. I think that'll cover it. People are pretty confident in freezing the same packages with Package Disabler if still on unrooted stock. I think rooting and a custom rom is a good idea at this point as it opens up more options if Samsung keep doing crappy things from here on in.
Karnax_ said:
Same. I installed Hydra-Rom (excellent rom btw) and then uninstalled all update packages with Titanium Backup. I think that'll cover it. People are pretty confident in freezing the same packages with Package Disabler if still on unrooted stock. I think rooting and a custom rom is a good idea at this point as it opens up more options if Samsung keep doing crappy things from here on in.
Click to expand...
Click to collapse
For me one of the coolest features is the secure folder, and to my knowledge all the custom roms so far break that because they break knox. That's a big minus for me.
Karnax_ said:
Same. I installed Hydra-Rom (excellent rom btw) and then uninstalled all update packages with Titanium Backup. I think that'll cover it. People are pretty confident in freezing the same packages with Package Disabler if still on unrooted stock. I think rooting and a custom rom is a good idea at this point as it opens up more options if Samsung keep doing crappy things from here on in.
Click to expand...
Click to collapse
What do you mean by "uninstalled all update packages with Titanium Backup"? Could you explain this point please.
---------- Post added at 10:29 AM ---------- Previous post was at 10:28 AM ----------
Chippy_boy said:
For me one of the coolest features is the secure folder, and to my knowledge all the custom roms so far break that because they break knox. That's a big minus for me.
Click to expand...
Click to collapse
There is a private mode with HydraRom
LightningJay said:
What do you mean by "uninstalled all update packages with Titanium Backup"? Could you explain this point please.
---------- Post added at 10:29 AM ---------- Previous post was at 10:28 AM ----------
There is a private mode with HydraRom
Click to expand...
Click to collapse
There's an app on the store which backs up any and everything (requires root). It also allows you to freeze/disable packages (like package disabler does) or flat out remove them from phone, which is probably overkill and can cause issues if you do it to the wrong packages.
Seeings I'll never use the updater again I opted to go with that. Hasn't caused me any issues so far and can still get OTA updates via Hydra-Rom's inbuilt OTA app if it did happen to get updated again.
Karnax_ said:
There's an app on the store which backs up any and everything (requires root). It also allows you to freeze/disable packages (like package disabler does) or flat out remove them from phone, which is probably overkill and can cause issues if you do it to the wrong packages.
Seeings I'll never use the updater again I opted to go with that. Hasn't caused me any issues so far and can still get OTA updates via Hydra-Rom's inbuilt OTA app if it did happen to get updated again.
Click to expand...
Click to collapse
Could you give me the name of the packages you disabled?
Chippy_boy said:
For me one of the coolest features is the secure folder, and to my knowledge all the custom roms so far break that because they break knox. That's a big minus for me.
Click to expand...
Click to collapse
Yeah pretty sure one of the devs said it'll never work sadly. It doesn't really affect me as I've never really kept much in the way of sensitive data on my phone.
LightningJay said:
There is a private mode with HydraRom
Click to expand...
Click to collapse
Thanks - I missed that.
I hope this isn't too OT, but having never flashed a custom rom before, is this something achievable (or sensible to try) for a noob like me? I am computer literate, but I know very little about phone workings and roms etc. I wouldn't want to chance bricking my device.
Karnax_ said:
There's an app on the store which backs up any and everything (requires root). It also allows you to freeze/disable packages (like package disabler does) or flat out remove them from phone, which is probably overkill and can cause issues if you do it to the wrong packages.
Seeings I'll never use the updater again I opted to go with that. Hasn't caused me any issues so far and can still get OTA updates via Hydra-Rom's inbuilt OTA app if it did happen to get updated again.
Click to expand...
Click to collapse
I'm tempted to try hydra but the downfall for me is I like everything to be as stock as possible. There's always a feature in custom roms which isn't added and it irritates me. What did you disable? Are you running hydra old kernel for the 100% battery or which kernel did you choose?
Chippy_boy said:
Thanks - I missed that.
I hope this isn't too OT, but having never flashed a custom rom before, is this something achievable (or sensible to try) for a noob like me? I am computer literate, but I know very little about phone workings and roms etc. I wouldn't want to chance bricking my device.
Click to expand...
Click to collapse
Its pretty simple, download twrp recovery, put the newest su binary on the Sd card, flash the twrp with odin using the ap button, one in recovery allow modifications, then install Su binary, then reboot to recovery, then install hydra rom it will give you options of what you want added to the rom etc. If ever you mess up just open Samsung smart switch go to the "more" tab then click second tab and insert your model number and seriel and it does the rest for you (this is if you want to revert back to stock)
Chippy_boy said:
Thanks - I missed that.
I hope this isn't too OT, but having never flashed a custom rom before, is this something achievable (or sensible to try) for a noob like me? I am computer literate, but I know very little about phone workings and roms etc. I wouldn't want to chance bricking my device.
Click to expand...
Click to collapse
I'm like you, this was my first time rooting, and flashing a costom ROM on a phone. I followed these steps and it worked fine for me.
http://forum.xda-developers.com/note-7/development/recovery-official-twrp-galaxy-note-7-t3446047 to root
http://forum.xda-developers.com/note-7/development/rom-hydra-rom-v1-0-t3447611 Costum Rom (HydraRom) and Kernel
---------- Post added at 11:04 AM ---------- Previous post was at 10:56 AM ----------
seriousc said:
I'm tempted to try hydra but the downfall for me is I like everything to be as stock as possible. There's always a feature in custom roms which isn't added and it irritates me. What did you disable? Are you running hydra old kernel for the 100% battery or which kernel did you choose?
Click to expand...
Click to collapse
Hydra is very very similar to stock. I didn't activate any extra features in the setup process. What I liked about it is that all the bloat wear is not installed, and phone is smother than with stock and has better battery life.
I am running the new Hydra on a replacement Note7 (green battery and 100%)
Thanks guys.
seriousc said:
I'm tempted to try hydra but the downfall for me is I like everything to be as stock as possible. There's always a feature in custom roms which isn't added and it irritates me. What did you disable? Are you running hydra old kernel for the 100% battery or which kernel did you choose?
Click to expand...
Click to collapse
I'm also othe latest hydra-kernel and replacement Note. The installer is pretty comprehensive so you can retain most of the stock functionality. If you're sticking close to stock the most suitable options are labelled as such so it's reasonably straight forward.
I'm going to make a full guide with all information in including changing country code for WiFi calling etc if you bought a different network device to what you are on.
Chippy_boy said:
Thanks - I missed that.
I hope this isn't too OT, but having never flashed a custom rom before, is this something achievable (or sensible to try) for a noob like me? I am computer literate, but I know very little about phone workings and roms etc. I wouldn't want to chance bricking my device.
Click to expand...
Click to collapse
I have made a full guide if your interested
http://forum.xda-developers.com/note-7/how-to/everything-n930f-fd-rooting-flashing-t3488573/page1
seriousc said:
I have made a full guide if your interested
http://forum.xda-developers.com/note-7/how-to/everything-n930f-fd-rooting-flashing-t3488573/page1
Click to expand...
Click to collapse
Thanks - very useful.
I am still considering this since I am not sure I want to live without knox and the Samsung secure folder. I plan on returning the phone in a month or so anyway, so maybe better to simply put up with Samsung's INCREDIBLY INFURIATING battery restriction. Boy they are really p1ssing me off by doing this!
Chippy_boy said:
Thanks - very useful.
I am still considering this since I am not sure I want to live without knox and the Samsung secure folder. I plan on returning the phone in a month or so anyway, so maybe better to simply put up with Samsung's INCREDIBLY INFURIATING battery restriction. Boy they are really p1ssing me off by doing this!
Click to expand...
Click to collapse
If you are returning it then out touch it. As far as secure folder goes you can get hydra rom for example it has secure folder built in. Knox though is more of a burden than useful.
The last time I rooted a phone was with a GS3 to install CyanogenMod. I've recently picked up a Pixel 2 XL, and I had some fairly noob-esque questions:
1. Do I have to wipe my phone to root it? That is, there is no "in-place" rooting?
1a. Are there any good methods to make a full backup *without* root before rooting it, and then restore it after I root?
2. Does rooting my phone make future OS updates more difficult/impossible? Ie: Will I still get OS updates, or will I have unroot my phone to get updates, then reroot it, possibly wiping everything?
3. What's the best method to go about doing this now? Googling around, and looking around here, I see a few different, but similar methods. I also see references to a "critical unlock," but no matter how many guides I read, I don't understand it. I'm starting to feel like I don't understand enough anymore to root my phone :-/
I really want to just be able to get back hosts-file based ad blocking again, and maybe a few other tweaks.
1, 1a: Go here and start reading, if you haven't already done so. To root requires unlocking the bootloader, which will cause the device to be wiped. It's best not to put anything important on the device until afterward.
2: OTAs must be applied manually. See the link I provided for instructions.
3: The P2XL is apparently unique in having two unlock commands. The non-critical unlock unlocks the bootloader while still providing some protection. The critical unlock strips all protections from the bootloader. To be on the safe side, execute both commands as mentioned in the link I provided.
Strephon Alkhalikoi said:
2: OTAs must be applied manually. See the link I provided for instructions.
Click to expand...
Click to collapse
Does that require re-wiping the device? Will I still get notified of updates, or will I have to keep track of new releases on my own?
The linked thread specifically says that OTAs do not require a device wipe. You should still get notifications.
Strephon Alkhalikoi said:
The linked thread specifically says that OTAs do not require a device wipe. You should still get notifications.
Click to expand...
Click to collapse
Sorry, I must have missed that. Thanks for pointing me to an answer! I appreciate all your help.
LucentPhoenix said:
Sorry, I must have missed that. Thanks for pointing me to an answer! I appreciate all your help.
Click to expand...
Click to collapse
Seems daunting. But read and ask till your comfortable. Lots of really helpful and Patient people on this lovely site. Stock + Root is the ish.
G
Ok, another question.... I'm looking to try out Android P. Will I be able to upgrade to that without wiping my phone?
LucentPhoenix said:
Ok, another question.... I'm looking to try out Android P. Will I be able to upgrade to that without wiping my phone?
Click to expand...
Click to collapse
Some have "dirty flashed" P over oreo with removing the -w flag from flash-all.bat script in the P factory image with mixed results. Your best bet is to clean flash the P build with fastboot to avoid any potential problems. However, yes, it will wipe your phone
Drat. Restoring apps and settings is far less painful than it used to be, but re-enabling all my 2FA is a pain in the ass.
If I do a clean flash of P, will I be able to upgrade P as new releases come out, or will I have to clean flash every time there's a new release, until it goes public?
LucentPhoenix said:
Drat. Restoring apps and settings is far less painful than it used to be, but re-enabling all my 2FA is a pain in the ass.
If I do a clean flash of P, will I be able to upgrade P as new releases come out, or will I have to clean flash every time there's a new release, until it goes public?
Click to expand...
Click to collapse
Yes you would be able to upgrade to the beta releases. However, you'd likely have to go back to Oreo, which would require a full wipe and clean flash, then upgrade to the betas. The first beta release is due out this month according to all the scuttlebutt I've read, so I think your best bet is just to wait a little longer. Here's a thread on the PDP1 that several folks are using :good:
https://forum.xda-developers.com/pixel-2-xl/how-to/android-9-0-developer-preview-1-t3757268
I have been into the Android scene since the original Samsung Galaxy S. I couldn't even tell you how many phones I had since then but I was always big into rooting and flashing more ROMs than healthy. I lost the ability to get endless company phones and ended up with locked bootloader phones for a few years. One day I saw a friend with the Pixel 2 and I got the itch again. I got the Pixel 3XL and unlocked the bootloader and rooted it immediately. At the time I didn't realize how much different the process was as far as updating and installing ROMs than it used to be on my older phones like my beloved Nexus phones. Basically I'm paranoid about doing anything because the process sounds extremely complicated to me. Maybe I'm just getting older. I build server and storage solutions every day but this is foreign to me. Sorry for all the rambling. Basically I'm rooted and still on the November 2019 build. I'm starting to get OTA update prompts a lot but I just ignore them. I just really want to update the easiest way and hopefully be able to do more going forward. Thanks for any help anyone can provide.
Download latest factory image. Extract the boot.img from it and save to your phone. Open magisk manager and patch that boot.img. Save /download/magisk_patched.img to your computer. Disable or remove any magisk modules that you might have running. In bootloader run the flash-all.bat, after editing to remove -w, and boot into system. Reboot to bootloader and run "fastboot flash boot --slot all magisk_patched.img" and you should be good to go. Make sure to back everything up before hand just in case something does wrong. I use a mix of titanium backup, sms backup/restore, export contacts, and manually saving files. There are other ways, but this is what I am comfortable with.
pside15 said:
I have been into the Android scene since the original Samsung Galaxy S. I couldn't even tell you how many phones I had since then but I was always big into rooting and flashing more ROMs than healthy. I lost the ability to get endless company phones and ended up with locked bootloader phones for a few years. One day I saw a friend with the Pixel 2 and I got the itch again. I got the Pixel 3XL and unlocked the bootloader and rooted it immediately. At the time I didn't realize how much different the process was as far as updating and installing ROMs than it used to be on my older phones like my beloved Nexus phones. Basically I'm paranoid about doing anything because the process sounds extremely complicated to me. Maybe I'm just getting older. I build server and storage solutions every day but this is foreign to me. Sorry for all the rambling. Basically I'm rooted and still on the November 2019 build. I'm starting to get OTA update prompts a lot but I just ignore them. I just really want to update the easiest way and hopefully be able to do more going forward. Thanks for any help anyone can provide.
Click to expand...
Click to collapse
Here ya go... https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117
Google offers their own flashing update tool. You can find it here, https://pixelrepair.withgoogle.com/carrier_selection.
Thanks for all the replies guys. Will all these methods keep by bootloader unlocked and phone rooted? I definitely want those as they are now. Going to look a lot closer into the kernel and ROM situation. Also, is it safe to go from 9 to 10 without wiping? I'd obviously rather not wipe but if it might cause issues then I'd go with the wipe.
I know it's an old phone but I miss my old HTC Desire HD. So much awesome development for that phone. Released with Froyo and eventually got functioning Marshmallow builds. That phone and my Nexus 4 are probably my favorites of the countless phones I've had over the years. Anyway, thanks again for the replies. Gonna get this thing updated tomorrow.
pside15 said:
Thanks for all the replies guys. Will all these methods keep by bootloader unlocked and phone rooted? I definitely want those as they are now. Going to look a lot closer into the kernel and ROM situation. Also, is it safe to go from 9 to 10 without wiping? I'd obviously rather not wipe but if it might cause issues then I'd go with the wipe.
I know it's an old phone but I miss my old HTC Desire HD. So much awesome development for that phone. Released with Froyo and eventually got functioning Marshmallow builds. That phone and my Nexus 4 are probably my favorites of the countless phones I've had over the years. Anyway, thanks again for the replies. Gonna get this thing updated tomorrow.
Click to expand...
Click to collapse
You will need to wipe data on the upgrade to 10.
You will need to root again after the update. Bootloader will remain unlocked.
Once you have rooted, there is a method to take an OTA, and stay rooted. A description of the procedure is in the forums somewhere.
Again, I would recommend to follow the guide posted by Homeboy76. It will comprehensibly explain all the steps you need to achieve root,update etc. With links to downloads.
Gone are the days of flashing with just your phone. My first rooting experience was with an HTC Amaze. Then an S4 Samsung.
Good luck..
Edit: I stand corrected on data wipe when going to 10. I perhaps was overly cautious, and followed other recommendations.
pside15 said:
Thanks for all the replies guys. Will all these methods keep by bootloader unlocked and phone rooted? I definitely want those as they are now. Going to look a lot closer into the kernel and ROM situation. Also, is it safe to go from 9 to 10 without wiping? I'd obviously rather not wipe but if it might cause issues then I'd go with the wipe.
I know it's an old phone but I miss my old HTC Desire HD. So much awesome development for that phone. Released with Froyo and eventually got functioning Marshmallow builds. That phone and my Nexus 4 are probably my favorites of the countless phones I've had over the years. Anyway, thanks again for the replies. Gonna get this thing updated tomorrow.
Click to expand...
Click to collapse
You do not need to wipe data to update to 10. It is perfectly safe, we all did it. And so did all the people with locked bootloaders. You only have to wipe going down. Up is fine.
---------- Post added at 10:53 PM ---------- Previous post was at 10:51 PM ----------
And here is the link to take an ota without losing root.
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation).
Anyone tried Google's flashing update tool?
Homeboy76 said:
Anyone tried this?
Click to expand...
Click to collapse
Just a heads up, your link is broken. Looks like the period at the end of the sentence accidentally got included in the hyperlink. The one in spotmark's post works. https://pixelrepair.withgoogle.com/carrier_selection
sliding_billy said:
Just a heads up, your link is broken. Looks like the period at the end of the sentence accidentally got included in the hyperlink. The one in spotmark's post works. https://pixelrepair.withgoogle.com/carrier_selection
Click to expand...
Click to collapse
It's working now
Homeboy76 said:
The link is in spotmark's quote: How can it be my link?
When I click it it works.
Click to expand...
Click to collapse
It's only if you click the link from your post. You copied the . into the link. It comes up with 'Not Found
The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.
Look closely at the hyperlink highlighting, and you'll see the . at the end.
sliding_billy said:
It's only if you click the link from your post. You copied the . into the link. It comes up with 'Not Found
The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.
Look closely at the hyperlink highlighting, and you'll see the . at the end.
Click to expand...
Click to collapse
It's working now
Homeboy76 said:
Read the edited post above yours.
Click to expand...
Click to collapse
Not kidding, it is still not clicking without the . included. When you look at spotmark's post, the dot is black. Yours is blue and part of the hyperlink. I tried it in two browsers.
sliding_billy said:
Not kidding, it is still not clicking without the . included. When you look at spotmark's post, the dot is black. Yours is blue and part of the hyperlink. I tried it in two browsers.
Click to expand...
Click to collapse
@sliding_billy
It's working now
Homeboy76 said:
@sliding_billy
It's working now
Click to expand...
Click to collapse
Winner, winner. Even better when you can't see the link.