Related
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.
Hello,
I've got a Galaxy Tab Pro 8.4 that I bought during the few months when it was the top of the line small tablet from Samsung (before the S series came out). Since it seems clear that Samsung has abandoned it and it won't get an Android update, I want to see what it'll take to upgrade to at least Lollipop. I'm pretty tech savy, but I've never tried to do anything like this with Android and I'm not at all sure where to start.
I've started to read the thread on rooting, but I quickly got a bit lost as I don't understand the terminology.
My goal would be to simply get to stock Lollipop or Marshmallow and have a stable, functional tablet that I don't have to tweak or mess with much. I'd also like to be able to go back if it proves too buggy. Is that feasible, or is rooting plus upgrading pretty much something that will require constant maintenance and tweaking? If it is possible, can someone point me to a how to for complete newbies?
Rooting will not help you upgrade your tablet to Lollipop or Marshmallow as they aren't available for your device. You might want to google "what is rooting" and find out what it does before proceeding.
The only thing you could do to get L or MM is install a custom ROM such as this:
http://forum.xda-developers.com/gal...5-1-x-cyanogenmod-13-0-nightlies-tab-t3256093
CafeKampuchia said:
Rooting will not help you upgrade your tablet to Lollipop or Marshmallow as they aren't available for your device. You might want to google "what is rooting" and find out what it does before proceeding.
The only thing you could do to get L or MM is install a custom ROM such as this:
http://forum.xda-developers.com/gal...5-1-x-cyanogenmod-13-0-nightlies-tab-t3256093
Click to expand...
Click to collapse
What makes you thin that his device is not have any Third Party ROMs (i.e CyanogenMod)? FYI this is the Tab Pro Fourm, and his Device should damned well be able to get to Lollipop or Marshmallow. e.g. CM12.1, or CM13.
As for rooting which you have to do at the start. Will most likely send him back to SamFirmware's where he'll need to likely first downgrade his Firmware to one that has a rootable exploit. i.e. a 'BOC1' ROM for the T325. (Which is the version I have). Through Odin (Samsung's Android Firmware Windows PC flashing Software). Then run something like the CFRoot App to get root.
NOTE: THIS WILL THROW YOUR KNOX FLAG!
This means that you'll never be able to use Knox services on that Device ever again. It will also throw the Warranty Flag as well Alerting Samsung that the Firmware was tampered with. For the moment (As I gather there is no known way to reset either of these Flags.) Not that this should stop you from installing either CM12.1 Lollipop (Seems to have lost support to) CM13 Marshmallow which is currently on a nightly release.
So the better question to ask is which T32x does Op even have? The T320 (Wi-Fi) The most common, and cheapest version has the greatest support. Where as the T325 (LTE), and T321 (3G) versions seem to be leaving behind. though even these are currently well into Marshmallow, and like with most ROMs there are some small bugs. But, on the whole My Device is more or less working as it should be.
Ichijoe said:
What makes you thin that his device is not have any Third Party ROMs (i.e CyanogenMod)? FYI this is the Tab Pro Fourm, and his Device should damned well be able to get to Lollipop or Marshmallow. e.g. CM12.1, or CM13.
As for rooting which you have to do at the start. Will most likely send him back to SamFirmware's where he'll need to likely first downgrade his Firmware to one that has a rootable exploit. i.e. a 'BOC1' ROM for the T325. (Which is the version I have). Through Odin (Samsung's Android Firmware Windows PC flashing Software). Then run something like the CFRoot App to get root.
NOTE: THIS WILL THROW YOUR KNOX FLAG!
This means that you'll never be able to use Knox services on that Device ever again. It will also throw the Warranty Flag as well Alerting Samsung that the Firmware was tampered with. For the moment (As I gather there is no known way to reset either of these Flags.) Not that this should stop you from installing either CM12.1 Lollipop (Seems to have lost support to) CM13 Marshmallow which is currently on a nightly release.
So the better question to ask is which T32x does Op even have? The T320 (Wi-Fi) The most common, and cheapest version has the greatest support. Where as the T325 (LTE), and T321 (3G) versions seem to be leaving behind. though even these are currently well into Marshmallow, and like with most ROMs there are some small bugs. But, on the whole My Device is more or less working as it should be.
Click to expand...
Click to collapse
1) I read the OP. He said, "stock Lollipop or Marshmallow."
2) You don't have to root TouchWiz to install a custom ROM. All you have to do is install TWRP, but it doesn't matter because of #1 above.
Well yes if he wanted Stock then he'd be outta luck. But that is not how I read it. I read it that he has accepted the fact that Samsung have left us in the lurch concerning any future updates.
That's how I read it, so the question follows in how to install a Custom ROM. Granted it should be possible to install TWRP v. 3.0.1-0, though Odin, and then the Device appropriate ROM. It should go without saying that the T320, and T325 are not the same Device, even if they are both collectively known as Galaxy Tab Pro's 8.4. As such it would be upnto the owner to know which version he might need.
Ichijoe said:
Well yes if he wanted Stock then he'd be outta luck. But that is not how I read it.
Click to expand...
Click to collapse
The problem, is folks really need to stop using the word "stock" as it really doesn't mean jack. Or at the least, means so many different things to different people, as to be basically meaningless. I would take stock to mean, what belongs on the device per the manufacturer, so that would be Kitkat TouchWiz in this case. To others (and probably what the OP is getting at) is a "pure" unskinned Google experience like Nexus. But seeing as Nexus is limited to such a small number of devices, I don't personally feel you can consider that "stock". CM is AOSP based, and at one time considered by many to be close to a pure AOSP experience. But those days are long gone, and there are so many proprietary CM features and apps now, you can't even begin to consider this "stock" by any means.
---------- Post added at 03:36 PM ---------- Previous post was at 03:22 PM ----------
_salguod said:
My goal would be to simply get to stock Lollipop or Marshmallow and have a stable, functional tablet that I don't have to tweak or mess with much. I'd also like to be able to go back if it proves too buggy. Is that feasible, or is rooting plus upgrading pretty much something that will require constant maintenance and tweaking?
Click to expand...
Click to collapse
What you are asking for is CM12 or CM13 (LP or MM) or one of the CM based ROMs. Those are really your only choice when it comes to anything past KK on this device. The CM ROMs are are very stable at this point. You might run into an obscure bug, but to be honest, its less laggy and overall a much better experience than the official Samsung TouchWiz ROM. And if you want to be free of Samsung bloat, CM definitely does that as well.
Tweak or maintain? You don't have to do anything after flashing the ROM, if you don't want to. You can decide to update to newer nightly CM builds from time to time, but that is completely optional. And to be honest, even CM13 is so stable at this point, that the nightly updates don't really change much of anything.
Go back? That's a breeze. Just do a backup in TWRP custom recovery before flashing a ROM, and you can restore to that backup (basically a snapshot of your existing configuration).
_salguod said:
If it is possible, can someone point me to a how to for complete newbies?
Click to expand...
Click to collapse
Honestly, just searching and reading are your best friend. You'll learn a lot more that way, than folk spoon-feeding you the info. The process isn't really all that hard. There may be a lot of esoteric lingo, but you can easily Google or use the XDA site search to find out what those terms mean. And once you've gone through the process, you'll likely be happy for the learning experience.
XDA is a wealth of information, for those willing to take the time to learn and search. All the answers you want are here in one form or other. Difficult to wade through at first, I'll agree with that. But all of us here had to go through the same thing at one time or other.
Its really hard to help someone when they say is "I'm a newb, tell me how to do this". Make a lot more sense for you to just dive in, then come back here with some specific questions, which we will gladly answer.
it would help to know what version OS you're running and the build #.
I rooted my tablet late last year (bought it in May 2015). Wasn't hard to do after some reading. Knox is still good too...1 yr warranty will be over soon.
Thanks all, I appreciate it. I've been doing some more digging to try to learn what everything means so I might know what I'm talking about. I started with the Lifehacker rooting guide (I can't post links yet, add this to lifehacker dot com: /5789397/the-always-up-to-date-guide-to-rooting-any-android-phone) and their how to flash a ROM guide (/how-to-flash-a-rom-to-your-android-phone-30885281) as well. Let me know if those aren't good places to start. I've also read through the CyanogenMod how to for the 8.4, which seems pretty thorough.
I definitely appreciate the push to search and learn, but it can feel like drinking from a firehose. Most "how to" posts are written assuming the reader knows the terminology and every post I read means Googling a half a dozen terms to understand it. For example, I have no idea what the Knox flag is or why I'd care if it got triggered. I don't care about the warranty flag, I'm past the 1 year mark so it doesn't really matter, right?
When I said "stock" I was referring to stock out of the box Android, not stock Samsung. Stock Samsung means staying with KitKat which I'd rather not do. My phone is a Motorola Droid Turbo, which I think is pretty close to stock Android Lollipop, so that I'm familiar with that.
However, I think I'm seeing that going stock Android isn't necessarily possible, or rather, other ROMs are easier to come by. Cyanogenmod seems to be the most popular and sounds very stable, I'll likely try that.
So, I don't need to root in order to flash a new ROM. What's unclear is do I need to do anything special to make sure I can go back to the out of the box Samsung KK that I have now in case I really screw it up or just don't like it and want to go back? Will the process of installing Cyanogenmod wipe my device (apps, files, accounts, data, etc.?
Any other surprises that a guy who has never done this might want to know before going in?
Thanks again for your patience and help.
I forgot to mention, I've got the wifi model, T-320. It's running 4.4.2, build number KOT49H.T320UEU1AOC1.
Well you have a number of choices for your T320 (WiFi), Sadly nonmof those stock. Since Samsung has never seen fit to ever giving us one. For me the Samsung (e.g. Vender ROMs), were always the 'Stock' ROMs. 'Pure' ROMs (al-la Nexus), are clearly Custom ROMs.
The best, and quickest way to learn how to update from Stock to Custom would be to hit up YouTube for a few short Vids on the subject.
_salguod said:
I've been doing some more digging to try to learn what everything means so I might know what I'm talking about. I started with the Lifehacker rooting guide (I can't post links yet, add this to lifehacker dot com: /5789397/the-always-up-to-date-guide-to-rooting-any-android-phone) and their how to flash a ROM guide (/how-to-flash-a-rom-to-your-android-phone-30885281) as well. Let me know if those aren't good places to start. I've also read through the CyanogenMod how to for the 8.4, which seems pretty thorough.
Click to expand...
Click to collapse
Those aren't bad general guides, to just introduce you to the basic concepts and terms. Just keep in mind that every different Android device has its nuances, which vary by manufacturer and over time (from one device to another - even from the same manufacturer). So you'll be referring back to Tab Pro 8.4 specific guides eventually.
_salguod said:
I have no idea what the Knox flag is or why I'd care if it got triggered. I don't care about the warranty flag, I'm past the 1 year mark so it doesn't really matter, right?
Click to expand...
Click to collapse
Basically, if you don't know what the Knox flag is, then it probably doesn't matter.
The longer story, Knox is a enterprise mobile solution made by Samsung. If you company doesn't use Knox (and you don't use your device for work), you don't need it. The huge majority of folks will never need Knox or want it.
You're right, that if the warranty is expired, the warranty flag doesn't matter. And honestly, I rooted my device while it still had a valid warranty. I'd rather have a device that I can use how I wish, and install what software I want (especially if Samsung isn't going to support it with updates) and warranty is a secondary concern, at most.
_salguod said:
What's unclear is do I need to do anything special to make sure I can go back to the out of the box Samsung KK that I have now in case I really screw it up or just don't like it and want to go back?
Click to expand...
Click to collapse
Once you install TWRP custom recovery, you can make a backup of the current Samsung TouchWiz KK ROM; and revert to that if needed or desired.
But honestly, you won't want to go back. CM runs faster and smoother, with no Samsung bloat. You won't want to go back to the crappy TouchWiz ROM, that is 2 generations (Android versions) obsolete.
But it is a good idea to have a backup, in case flashing CM doesn't go right the first time, and the device won't boot.
_salguod said:
Will the process of installing Cyanogenmod wipe my device (apps, files, accounts, data, etc.?
Click to expand...
Click to collapse
You will absolute want to wipe user data when installing CM. Not doing so will likely cause major bugs and/or failure to boot. This is the general rule whenever flashing a new ROM. Although for similar ROMs (such as minor CM updates) you can try to keep user data. This is called a "dirty flash".
You can backup a lot of your data before flashing CM:
Apps: After root, you can use the app Titanium Backup (highly recommended) to backup apps and app data
Accounts: Titanium can backup a lot of this stuff, as well. Depends on what you are talking about, specifically.
Files: just move them to SD card or your computer. Or use a cloud solution (there are many)
You should always be backing up your data, anyway, if its important to you.
_salguod said:
I forgot to mention, I've got the wifi model, T-320. It's running 4.4.2, build number KOT49H.T320UEU1AOC1.
Click to expand...
Click to collapse
Same firmware as what I had prior to rooting it.
The cyanogen articles give a good rundown on how to install it. The only thing that I'm not sure about is whether getting the sdcard to be formatted/recognized is still an issue or not.
When last I checked back in Feb. it seemed like that was still unresolved. I have a 64gb card and getting it to be read by CM13 was absolutely critical. So any move to CM13 was postponed.
Running Kitkat is fine for me...after rooting it, I uninstalled/froze a lot of software incl. a lot of Samsung crap that was eating the battery. The battery is my only complaint with the tablet.
AndroidPrince1 said:
The cyanogen articles give a good rundown on how to install it. The only thing that I'm not sure about is whether getting the sdcard to be formatted/recognized is still an issue or not.
When last I checked back in Feb. it seemed like that was still unresolved. I have a 64gb card and getting it to be read by CM13 was absolutely critical. So any move to CM13 was postponed.
Click to expand...
Click to collapse
The SD card issue on CM13 was solved in early March. It was holding me back as well (stayed on CM12.1) , until I saw it was solved. Now I've been using CM13 for over a month. My 64GB card works great with CM13.
AndroidPrince1 said:
Running Kitkat is fine for me...after rooting it, I uninstalled/froze a lot of software incl. a lot of Samsung crap that was eating the battery. The battery is my only complaint with the tablet.
Click to expand...
Click to collapse
If you flash CM, you'll see its a lot smoother and snappier, especially on the home screens, app drawer, etc.
Thanks all, I plan on biting the bullet some time soon. Too much other stuff on my plate (like car repairs, etc.) so it'll have to wait for a bit. I'll check back in when I do. I'm looking forward to it.
redpoint73 said:
The SD card issue on CM13 was solved in early March. It was holding me back as well (stayed on CM12.1) , until I saw it was solved. Now I've been using CM13 for over a month. My 64GB card works great with CM13.
If you flash CM, you'll see its a lot smoother and snappier, especially on the home screens, app drawer, etc.
Click to expand...
Click to collapse
Good to know on the sdcard thing...looks like I'll have to read up again on how to do.
Thanks for the note.
_salguod said:
What's unclear is do I need to do anything special to make sure I can go back to the out of the box Samsung KK that I have now in case I really screw it up or just don't like it and want to go back?
Click to expand...
Click to collapse
BTW, you can always restore your device to 100% stock (Samsung) by downloading the firmware from sammobile.com/firmwares and flashing it using Odin. If you get into trouble, this will help get you back out.
But since flashing CM13 nightlies is relatively easy, I don't think you'll have any serious trouble, just the normal learning curve.
I've had my SM-T320 on Cyanogenmod since the day after I bought it in 2014 and never looked back :good:
CafeKampuchia said:
BTW, you can always restore your device to 100% stock (Samsung) by downloading the firmware from sammobile.com/firmwares and flashing it using Odin. If you get into trouble, this will help get you back out.
But since flashing CM13 nightlies is relatively easy, I don't think you'll have any serious trouble, just the normal learning curve.
I've had my SM-T320 on Cyanogenmod since the day after I bought it in 2014 and never looked back :good:
Click to expand...
Click to collapse
I don't see any US firmwares on the sammobile.com site. Am I looking in the wrong place?
_salguod said:
I don't see any US firmwares on the sammobile.com site. Am I looking in the wrong place?
Click to expand...
Click to collapse
Cellular South is the US firmware for some reason.
I'm trying to load the latest CM 13.0 nightly this morning and running into issues.
I'm following the install instructions on the CM website and the loading of a custom recovery is failing at step 7. I get the start of the blue bar on my tablet, but I get this error in the command prompt:
Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
I've tried twice with the the factory cable and a third time with an alternate cable same result.
How do I fix that?
I should mention that I'm working on a Windows 10 computer.
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.
Hi all
Hope this is the correct area...
My hubby bought me a S20 plus for my birthday through a local dealer.
I noticed a few issues like not being able to use biometrics or install certain apps.
I've since found out the phone has been rooted.
I've tried to do a factory reset, but this hasn't helped.
I've downloaded root checker and it confirms the phone is rooted. I've downloaded SuperSU yet is won't work as ver 2.82 claims it's for an older Version of Android.
I've downloaded solid explorer to delete the root access files such as Busybox and SU however I cannot find these files in the system folder or the system/bin folder.
Can anyone advise on how I can unroot my phone? I am unable to install certain needed apps due to this.
Phone details below. Sorry am unable to upload pics.
UI Version = 1
Android Version = 10
Let me know if other info is needed.
I've even tried calling the Samsung Center and they are unable to assist...
Thanks all
Lee
Lee KZN said:
Hi all
Hope this is the correct area...
My hubby bought me a S20 plus for my birthday through a local dealer.
I noticed a few issues like not being able to use biometrics or install certain apps.
I've since found out the phone has been rooted.
I've tried to do a factory reset, but this hasn't helped.
I've downloaded root checker and it confirms the phone is rooted. I've downloaded SuperSU yet is won't work as ver 2.82 claims it's for an older Version of Android.
I've downloaded solid explorer to delete the root access files such as Busybox and SU however I cannot find these files in the system folder or the system/bin folder.
Can anyone advise on how I can unroot my phone? I am unable to install certain needed apps due to this.
Phone details below. Sorry am unable to upload pics.
UI Version = 1
Android Version = 10
Let me know if other info is needed.
I've even tried calling the Samsung Center and they are unable to assist...
Thanks all
Lee
Click to expand...
Click to collapse
You will need to get hold of the stock firmware from somewhere like Sammobile and flash back to stock using ODIN. There's tons of guides knocking about on here for the step by step. The damage is done though as far as any Knox related features go, it's like a fuse that blows when you root and you can never fix that.
Having said that, biometrics should have never been affected by rooting so that's a bit unusual. Flash stock and set up from scratch then go from there, could be faulty also
Thanks for the guidance Dave. I'll search the forums for the steps.
For clarity, when I say biometrics didn't work, it works allow me to record etc, but when I tried to enable it, like on my banking app, it wouldn't allow me. This is how I eventually figured out my phone was rooted. While I know the benefits of being rooted, a normal everyday user like myself, certainly won't benefit from it.
I've had a Samsung my entire life, and always saw the secured by knox logo... When you say damage has been done, does this mean that all my security in the device, such as my banking details etc, may be compromised?
Jees. I hope not. As this would really freak me out...
Ok so Finding the firmware wasn't to difficult. Sanmobile quite easy to navigate.
Just a query please... My phone base band version lists g985fxxu1atb2 however the closest I could find to this is G985FXXU1ATBM
Is this ok or does it have to be the exact same description?
Shoo. Lol. Really hope I'm going to be able to get this right **insert nervous smile emoticon here**
Lee KZN said:
Ok so Finding the firmware wasn't to difficult. Sanmobile quite easy to navigate.
Just a query please... My phone base band version lists g985fxxu1atb2 however the closest I could find to this is G985FXXU1ATBM
Is this ok or does it have to be the exact same description?
Shoo. Lol. Really hope I'm going to be able to get this right **insert nervous smile emoticon here**
Click to expand...
Click to collapse
The last letters are the region/operator of the Rom. Not necessarily has to be the exact description, the really important are the first that indicate model number.
Ok. So have downloaded Odin and am busy downloading the flash firmware.
May I please be so bold as to ask someone on here to please share a link tot he step by step guide that I will need to follow in order to flash my phone back to the original boot thingie :silly::silly::silly:
I have tried to search but seem to only come up with a nexus thread with no mention of Odin.
~Sorry to ask, but little overwhelmed LOL and want to make sure I do this properly and not screw up my phone.
REAL noob here, so apologies if I come across lazy and getting others to do the work, but am really grateful for the help.
Maybe I'm searching incorrectly???
I found this somehow....
Is this it?
https://forum.xda-developers.com/galaxy-s20/how-to/howto-root-s20-series-upgrade-firmware-t4079353
**fingers crossed**
Can you unlock your phone with biometrics? Im guessing only the banking apps don't work because it's rooted. If i remember correctly most banking apps and maybe Google pay(not sure about that) stop working after rooting because the phone is "compromised" and it's not safe. You have to hide your root status from these apps and they will work properly then. Maybe someone else can help you with that because i do not remember how to do it.
Hi Marto
Yes, biometrics does work, although not really good. But that's probably due to the hectic screen protector.
Correctly so, it's mostly the banking / payment apps that won't work, and I can't check or download any software updates... Although I belive this can also be done manually....
But wow, there's an app that hides the root status? That might be a whole lot easier than re flashing. Truthfully I'm Sh!tting myself at the thought of attempting this ????
Hi Marto
Yes, biometrics does work, although not really good. But that's probably due to the hectic screen protector.
Correctly so, it's mostly the banking / payment apps that won't work, and I can't check or download any software updates... Although I belive this can also be done manually....
But wow, there's an app that hides the root status? That might be a whole lot easier than re flashing. Truthfully I'm Sh!tting myself at the thought of attempting this ????
if the phone was bought as new, go back to the dealer and demand a new one that is not rooted.
could also be that your husband rooted the phone and installed software that keep tabs on what you do.
Hello,
I have recently entered the world of Xiaomi after a history with Sony Devices (Xperia, Xperia SP, Xperia Z3). I'm so far delighted with the Mi 10T Lite, it's feature rich and blazingly fast. However, I miss one feature I had installed on my SP and Z3 that made their batteries live extra long. It's this:
Battery Charge Limit [ROOT] - Apps on Google Play
Stop charging at desired level to preserve battery health for most devices!
play.google.com
With this tool, you can essentially leave your device permanently on the charger and it will stay within the limits you have set. I used to have it set to 71-80%. So when the charge dropped to 70% it started charging, until reaching 80%. I therefore balanced keeping the battery charged for short intervals and at a sweet spot for its health, with having enough charge in case I wanted to grab my phone and leave the house. I really love this app.
The problem is, it requires root privileges.
I understand that rooting my Xiaomi is not particularly hard, but since it is a new device I would not want to void its warranty. It's possible that some defect shows up and I am left without a warranty. It would be a particularly big bummer if I discovered I rooted the device only to see that the app does not work properly with it.
So, could someone with a rooted device try out this fantastic app and let me know if it works? You might end up with a battery life extender you never knew existed!
Many thanks,
Yanni
Athens/Greece
Friendly bump! Could somebody try this nifty app for battery life optimization on their rooted 10T Lite? Let me know if it works so I can go ahead with arcane rooting magick, hehe.
I have been using it for the last two years. It is a great app.
It does work fine on the mi10t lite, you just need to change the control file from default to "input_suspend" pixel2/xiaomi mi6. After that the limit is respected. Another alternative is a magisk muddle called "Advanced Charging Controller" it is more technical than bcl.
egor27 said:
I have been using it for the last two years. It is a great app.
It does work fine on the mi10t lite, you just need to change the control file from default to "input_suspend" pixel2/xiaomi mi6. After that the limit is respected. Another alternative is a magisk muddle called "Advanced Charging Controller" it is more technical than bcl.
Click to expand...
Click to collapse
Thank you! Both for the confirmation and also the control file's location.
I think I'll be rooting my device, using magisk. Briefly browsing a couple of guides, I guess it won't be very involved. Besides voiding warranty I'll be losing OTA firmware updates. I presume I will have the option to manually updating by flashing a new official ROM.
funkyjester said:
Thank you! Both for the confirmation and also the control file's location.
I think I'll be rooting my device, using magisk. Briefly browsing a couple of guides, I guess it won't be very involved. Besides voiding warranty I'll be losing OTA firmware updates. I presume I will have the option to manually updating by flashing a new official ROM.
Click to expand...
Click to collapse
Just FYI - you should not void the warranty (at least in Europe - https://www.piana.eu/root/) and OTA updates will arrive normally. You will need to restore stock boot image from Magisk manager before installing OTA and then re-root the phone afterwards, but that's the only complication.
_mysiak_ said:
Just FYI - you should not void the warranty (at least in Europe - https://www.piana.eu/root/) and OTA updates will arrive normally. You will need to restore stock boot image from Magisk manager before installing OTA and then re-root the phone afterwards, but that's the only complication.
Click to expand...
Click to collapse
Thanks for the link. Besides the EU statutory warranty, a quick search reveals that the company itself allows rooting without voiding your warranty. So I'm a happy camper I guess.
Guys, please, if anyone can upload the .xqcn file generated by the backup in QPST, thank you. It has to be a Mi10T Lite Global or EEA.
Hemerson Silva said:
Guys, please, if anyone can upload the .xqcn file generated by the backup in QPST, thank you. It has to be a Mi10T Lite Global or EEA.
Click to expand...
Click to collapse
You do not need to ask in every unrelated topic. I guess that no one has the file and/or no one wants to share his IMEI publicly.
_mysiak_ said:
You do not need to ask in every unrelated topic. I guess that no one has the file and/or no one wants to share his IMEI publicly.
Click to expand...
Click to collapse
In fact, there is the issue of IMEI. I wanted the file to go through my device and see how it would behave, taking the risks. Unfortunately the XDA community was once more collaborative.
Hemerson Silva said:
In fact, there is the issue of IMEI. I wanted the file to go through my device and see how it would behave, taking the risks. Unfortunately the XDA community was once more collaborative.
Click to expand...
Click to collapse
Maybe if you provide step by step guide how to extract xqcn file and remove sensitive information from it before uploading to the internet, someone will be willing to do it.
In each case, we are heavily offtopic here.
Hello, I thought of hijacking my own thread again.
After painfully waiting for a week (go Xiaomi!), I unlocked my bootloader, and got an instant factory reset with all my data gone (again, go Xiaomi! I didn't expect that).
But now all is unlocked and I am left with the task of rooting my device. I think I 'll use Magisk. From what I understand I need a boot.img file to patch and then flash. Thinking I 'd like to keep my current ROM, I looked around for a full ROM image to get the boot.img file. But I couldn't find it.
My current ROM is MIUI Global 12.0.5.0 (QJSEUVF), which like I said, I could not find anywhere. It must be an early 12.0.5 ROM used on the first phones shipped. I have two questions:
a) Is it possible to somehow extract the boot.img file from the running phone?
b) If not, and if I can't find the installed ROM zip, what ROM zip would you pick to stay as close as possible to the one I have now? The reason I want this is that the phone works pretty damn fine up to now, and I see reports of problems after major upgrades, like version 12.5.
Any info much appreciated!
Best Wishes,
Yanni
Athens/Greece
funkyjester said:
Hello, I thought of hijacking my own thread again.
After painfully waiting for a week (go Xiaomi!), I unlocked my bootloader, and got an instant factory reset with all my data gone (again, go Xiaomi! I didn't expect that).
But now all is unlocked and I am left with the task of rooting my device. I think I 'll use Magisk. From what I understand I need a boot.img file to patch and then flash. Thinking I 'd like to keep my current ROM, I looked around for a full ROM image to get the boot.img file. But I couldn't find it.
My current ROM is MIUI Global 12.0.5.0 (QJSEUVF), which like I said, I could not find anywhere. It must be an early 12.0.5 ROM used on the first phones shipped. I have two questions:
a) Is it possible to somehow extract the boot.img file from the running phone?
b) If not, and if I can't find the installed ROM zip, what ROM zip would you pick to stay as close as possible to the one I have now? The reason I want this is that the phone works pretty damn fine up to now, and I see reports of problems after major upgrades, like version 12.5.
Any info much appreciated!
Best Wishes,
Yanni
Athens/Greece
Click to expand...
Click to collapse
Bootloader unlocking always results in a factory reset (unless vendor seriously screwed up), it's standard security feature of Android since..like pretty much forever.
If you do not have boot.img at hand, the most easy solution is probably to hot boot TWRP ("fastboot boot twrp.img") and flash Magisk from there. Also it might be a good idea to reflash your phone with normal global version which is already available for download, QJSEUVF sounds like Vodafone version, I would certainly get rid of it and replace it with QJSEUXM.
_mysiak_ said:
Bootloader unlocking always results in a factory reset (unless vendor seriously screwed up), it's standard security feature of Android since..like pretty much forever.
If you do not have boot.img at hand, the most easy solution is probably to hot boot TWRP ("fastboot boot twrp.img") and flash Magisk from there. Also it might be a good idea to reflash your phone with normal global version which is already available for download, QJSEUVF sounds like Vodafone version, I would certainly get rid of it and replace it with QJSEUXM.
Click to expand...
Click to collapse
I should have figured out what VF means. I think I will take the straightforward way and use QJSEUXM which I have found readily available. Thanks!