[Q] About the Lollipop update - Galaxy Tab S Q&A, Help & Troubleshooting

I have a SMT805, rooted and all, but since I'm abroad for several more months, I dont have a PC.
Is there any way to upgrade from KitKat without requiring a pc?
Like, I dunt know, flashing the update through recovery or something.
Anything I can do?

I don't think it's possible
There are some flashable zips of lollipop ROMs but you need to install the official update first to make them work and that requires a PC. To make it worse, you won't even get the OTA update as you have rooted. So as far as I know, you will need a PC to update.

Unfortunately not. Odin is required to flash the files as boot loader access is required via download mode.

Related

[Q] Manually flash OTA on stock recovery?

Seems this is either something I should just know or ya just can't do it.
I've brought my device back stock, sitting on 4.2.2.
However it doesn't want to take an OTA for whatever reason. Seems to be a device issue based on a search on google, but I was curious, since I have the OTA files for the 4.3 update and 4.4 update, why not just push them manually? Doesn't seem the stock recovery allows for an option to install from internal storage. I mean, there is an option to select, but all it seems to do is retart the phone.
You help is appreciated, even if this is a noob question.
Are you s-off or bootloader unlocked? You say you have the ota files. If so you need a usb otg cable and a usb flash drive. You take the ota zip and rename it to update.zip and place it on your fat32 formated usb drive in no folders. Boot to stock recovery and select apply update from external storage. Its should do some stuff, reboot a couple times and then you should be updated. If your otas are downloading, but not installing you can select apply update from cache and it should install it.
I brought it back to 100% Verizon Raped Stocked. I am having a camera defect issue, but I want to make sure my phone isn't bjorked in the event they try to pin the camera problem on something else. I'd like to get my phone all the way to current software, stock. So I can walk in and be like, hey it's updated, it's messed up still, give me a new phone, k thx.
The issue I'm having is that the phone will not recognize an update is there. Even though I'm running old software. So I searched for various OTAs and seems I can download them from various threads/links found here on XDA, but I am not able to figure out how to easily flash them in the stock recovery.
Are you talking about ota files or ruu's. Ota files are zips that where pulled from somebodys phone who recieved it ota, they are just updates. They flash thru recovery, but are hard to find. Ruus are zips that are full phone images that get flashed in hboot using fastboot.
I would ruu to 4.3 and hope you get the ota notification for 4.4. I would tell you to just ruu to 4.4, but we do not yet have one available.
I am S-On so I had figured I didn't have the choice to use a ruu file. The files I have are the zips people have posted after pulling them from their devices before doing the update.
I guess what I'll do that probably makes the most sense and least time is S-Off again. Flash a newer ruu and go back to S-On. Guess I didn't anticipate having this OTA problem. Of course, I could still have the issue even if I flash the 4.3 ruu.
Sent from my Nexus 7 using Tapatalk
You can do an ruu while s-on, you just need a signed one. You can get them here http://forum.xda-developers.com/showthread.php?p=46506621 at the bottom of the post.
Awesome, well, I'm back up to 4.3. However I'm still in the same boat where the phone refuses to acknowledge an update. I'll just be content with that for now. haha
Thanks for the help.

Which of these two possibilities is better for installing updates on a rooted phone?

Hello. I'm coming from a old windows mobile phone and just got my first Android device "Samsung Galaxy S4 mini GT-i9195" and obviously i'm loving it.
Still being a newbie to Android i already did a bit of advanced stuff (at least for a novice android user) like installing CWM Recovery and rooting the phone in order to be able to install apps on and external SD card.
But a new question arose: What about new Android updates, can i still install them without loosing root or even worse, damaging the phone?
After searching a bit on google i came up with two possible and contraditory possibilities which are:
-Yes, and afterwards i would only need to restart the phone in CWM mode and reapply the zip root file i used previously;
-No, it will likely mess the phone and i should wait 1 or 2 weeks for a updated rooted rom and "install" that instead.
So, i'm a bit confused here, what would be more advisable?
I suggest to make a nandroid backup, then try a custom rom from the dev forum.
There are 4.4.4 kikat roms for our beloved S4 mini, and i dont think samsung will go further.
Envoyé de mon GT-I9190
rick6 said:
-Yes, and afterwards i would only need to restart the phone in CWM mode and reapply the zip root file i used previously;
Click to expand...
Click to collapse
...... if, as has been said, you ever get an update. An update certainly will not damage the phone.
You certainly won't have to wait for anything. I agree with zlaz, flash a new ROM such as Carbon - you get regular updates and great support here on XDA (whichever ROM you try).
Custom ROMs like CarbonRom (see the development section) is the way to go for this phone I would say. But if you wanna stay on stock and if we would get an update, Samsung probably wont let you install it via the usual OTA or Kies method, because your device is flagged as "Modified" after flashing a custom recovery (you can see this in the about this device section in the settings). You would still be able to flash the update manually with Odin, but you will then probably have to reroot it.
LanderN said:
Custom ROMs like CarbonRom (see the development section) is the way to go for this phone I would say. But if you wanna stay on stock and if we would get an update, Samsung probably wont let you install it via the usual OTA or Kies method, because your device is flagged as "Modified" after flashing a custom recovery (you can see this in the about this device section in the settings). You would still be able to flash the update manually with Odin, but you will then probably have to reroot it.
Click to expand...
Click to collapse
That's 100% true, I don't remember now exactly when your phone say, that it is modified and you can't update - moment you search for update in it or moment you try to download update that it has find.
Samsung oryginal software is not that greate anyways
Thank you all for the replies.
I think i got what i wanted with your awnsers, i just need to dig a bit more about the avaiable roms what what i can get from them. At the moment i'll keep my s4 mini as it is for a while longer i guess.
As for warranty i get something while booting up saying "Set warranty Bit: Kernel", but that seems to be what you normaly get when root a stock rom.

Possible Brick HTC M8

Hello All,
I think I may have possibly bricked my m8.
I was using cyanogen 11, when I decided to try and flash the GPE rom that is available.
However I did not flash the latest firmware. I am not able to get into fast boot. When I press Power + Volume Down, it takes me too bootloader but no options are available other then press power to reboot.
When it reboots I do get into the rom however, wifi, and service are unavailable for obvious reasons. My Stupidity may have costed me this phone :/ I wasn't able to get s-off with my t mobile variant. It is unlocked, and had TWRP installed.
Any help would be greatly appreciated!
Bricked? But you can get into ROM? Do you even know what a "brick" means?
Just restore your device to Stock and do an OTA to get latest firmware in order to have a working custom ROM on latest firmware. You are T-Mobile, US? Do an RUU, or head over to the Collection thread in General section and download a nandroid backup for your device and restore it from within TWRP(Instructions is also available in the first 2 posts of the Collection Thread).
If you can get it into bootloader/fastboot it ain't "bricked", it's recoverable.
BerndM14 said:
Bricked? But you can get into ROM? Do you even know what a "brick" means?
Just restore your device to Stock and do an OTA to get latest firmware in order to have a working custom ROM on latest firmware. You are T-Mobile, US? Do an RUU, or head over to the Collection thread in General section and download a nandroid backup for your device and restore it from within TWRP(Instructions is also available in the first 2 posts of the Collection Thread).
If you can get it into bootloader/fastboot it ain't "bricked", it's recoverable.
Click to expand...
Click to collapse
Okay maybe not bricked but I messed it up quite badly, Im not able to get it into the recovery or have it be detected via fastboot. I did try and do a ruu to have it be put back to stock but Im not sure how to go about doing that since ruu cannot see it since it isnt in fastboot... :/
Did you Make sure you update you SDK. Only the latest fastboot and adb will work with lollipop
subarudroid said:
Did you Make sure you update you SDK. Only the latest fastboot and adb will work with lollipop
Click to expand...
Click to collapse
I did get the latest one from the official site, I was able to use it perfectly fine last night. Now however when I try adb shows the device offline, even if I kill and start the server, and disable and renable the debugging, try different ports etc. I can get it to show the device name, but it says offline next to it, I get no prompt on the device. I was reading the gpe doesnt use fastboot, ( I may be wrong) But that would explain why I dont see anything at the bootloader screen, other then press power to reboot the device.
Good news everyone! I was able to fix it in the most impractical way ever.
So why nothing else worked, I did still have access to the rom which of course had no wifi or service. So what I did was install the terminal emulator via browsers onto my phone, from there I was able to type reboot recovery and restore my backup that I had! and wala, whatya know, now it works, and I dont have a useless phone anymore

[Q] Frustrated Xperia Z1C T-Mobile UK owner.

Hi,
I have the CDA 1280-7858 Sony Xperia Z1 Compact model. I have yet not been able to upgrade my phone to latest lollipop, since T-mobile UK have not released it yet.
My phone is carrier unlocked, but bootloader CANNOT be unlocked, this leaves no possible way for me to add a custom rom , right?
What are my options here? Sit and wait forever or just get a new phone?
As you can see in the attachment, only T-mobile remains on the 14.4.A.0.157 release in the UK carriers.
You can always flash stock or custom stock based lollipop from some other region. You don't need unlocked bootloader for that. There are a couple of them prerooted+dual recovery in general z1c forum.
templeka said:
You can always flash stock or custom stock based lollipop from some other region. You don't need unlocked bootloader for that. There are a couple of them prerooted+dual recovery in general z1c forum.
Click to expand...
Click to collapse
Ok, but this would erase my phone completely right? i would use flashtool to upgrade?
Is t here any reason why its taking so long to get the OTA update? I mean, optimally, i want that one and not really need to bother to reset the phone entirely for this update.
You can always make a backup in recovery (I'm thinking you have a recovery already) just in case you don't like lollipop (I didn't). You lose any app installed and preferences (for sms u can backup those and contacts you can sync with Google account) so you will have to reinstall those. If you want root for your phone you need one of those prerooted ones and those are flashed from recovery usually. Best thing is to read the instructions in those threads.
I don't have recovery mode i think. Since this comes with unlocking bootloader, which i CANNOT on my phone.. (its not possible, not even paid with jinx13).
You don't need unlocked bootloader for recovery. Just go here http://nut.xperia-files.com/ and browse to XZDualRecovery > XZDualRecovery 2.8.15 > Z1C-lockeddualrecovery2.8.15-RELEASE.installer.zip and install that from your PC (with the phone connected to your PC via USB). I think you need to enable USB debugging before doing this and you definitely have to be rooted. You should read around how to install stuff there are some guides and resource threads in General forum.
Edit: Also get the flashable version and store it somewhere safe on your phone. Anytime you flash a new ROM you need to also flash the recovery else you have to connect phone to PC and do the install version and that takes longer.
Thanks templeka, I have been unsuccessful in any attempt to root this phone also.. What would be the best way? it just seems to be locked in all ways possible for me to get this done.
edit: i tried the towelroot selection 3 from file you suggested.. it just stopped after libdvm opened (loljavasucks), and after reboot, i was unable to enter recovery mode. (pressed volume up or down, and there was no light on any diode, at any time)
You need to flash a stock .108 rom, root and install dual recovery.
Towelroot will not work on v157. Follow the guide here http://forum.xda-developers.com/showthread.php?t=2977774
In short you need to flash v108 kernel, root and flash v157 kernel back with Flashtool. Be sure to install the necesary drivers after installing Flashtool (they are in the folder where you installed it).
Sorry for being noob still.. But how do i enter flash mode now? I mean reboot and holding volume down will only enter Safe Mode of the phone. (i think its because i have the wrong kernel?)
Just when i was about to give up.. 14.5.A.0.270 just released on t-mobile.. FINALLY!

Flash stock software update through TWRP?

First of all this phone belongs to my dad. This means I haven't used it and I'm not familiar with many things about it.
The phone is running a stock ROM. It is not rooted, but it does have TWRP.
A software update prompt popped up trying to install "v20p-apr-03-2018" (why is an update for the G4 called v20 lol).
Telling it NOT to download it and NOT check for updates ever doesn't work. The update prompt comes back in 2 days tops. So **** you LG.
Since it's not rooted the easiest option seems to be to flash the update, however it just launches TWRP and does nothing. I found no way to actually download the update and keep it on the device so that I can manually tell TWRP to flash it.
So: Is there a way to download said update and flash it through TWRP? Or should I root it and delete the stupid update tool? I really don't want to flash a stock recovery.
ast00 said:
First of all this phone belongs to my dad. This means I haven't used it and I'm not familiar with many things about it.
The phone is running a stock ROM. It is not rooted, but it does have TWRP.
A software update prompt popped up trying to install "v20p-apr-03-2018" (why is an update for the G4 called v20 lol).
Telling it NOT to download it and NOT check for updates ever doesn't work. The update prompt comes back in 2 days tops. So **** you LG.
Since it's not rooted the easiest option seems to be to flash the update, however it just launches TWRP and does nothing. I found no way to actually download the update and keep it on the device so that I can manually tell TWRP to flash it.
So: Is there a way to download said update and flash it through TWRP? Or should I root it and delete the stupid update tool? I really don't want to flash a stock recovery.
Click to expand...
Click to collapse
Freeze or uninstall Software Update (LG proprietary, i.e., closed source, app) - may require root. That should stop the annoying requests. If you are able to upgrade you will lose TWRP and will have to re-flash TWRP again. You may want to consider that you do not have the latest Google security patches by not doing the update, putting your Dad's phone more at risk.
sdembiske said:
Freeze or uninstall Software Update (LG proprietary, i.e., closed source, app) - may require root. That should stop the annoying requests. If you are able to upgrade you will lose TWRP and will have to re-flash TWRP again. You may want to consider that you do not have the latest Google security patches by not doing the update, putting your Dad's phone more at risk.
Click to expand...
Click to collapse
It's not like LG updates security patches that often so it's not that big of a deal if I can't update it.
It's also fine if I lose TWRP during the process, I just want to avoid flashing stock recovery just for the sake of updating it.
And I still can't download the update and keep it. I don't know where it puts the update after downloading it. I couldn't find it in TWRP.
ast00 said:
It's not like LG updates security patches that often so it's not that big of a deal if I can't update it.
It's also fine if I lose TWRP during the process, I just want to avoid flashing stock recovery just for the sake of updating it.
And I still can't download the update and keep it. I don't know where it puts the update after downloading it. I couldn't find it in TWRP.
Click to expand...
Click to collapse
It helps if you include your phone model when looking for specific firmware updates.
If you're Dad's phone is an H815, there are some v20p downloads available here: https://lg-firmwares.com/lg-h815-firmwares/firmwares/
In order to flash in TWRP without losing TWRP, you would have to remove the stock recovery and create a flashable zip ...
Easiest is to simply freeze or remove the lg Software Update app as I indicated - the annoying update notification should then disappear ...
Note: XDA courtesy is to hit the Thanks button (bottom right of post), when members are trying to help and solve your issues. As a Senior Member you know this.
This update does not contain any security fixes it's just for the new European data protection law..
First thing you should try is:
Upgrade TWRP.
Do a full TWRP backup!
Test android update again.
Second thing:
Have you tried the LG bridge windows software to update?
If so and it fails there too you can find the update when you try to Flash it within the LG folder of your Windows PC afterwards use this KDZ file and lgup to flash it.
There is a chance that when using the internal updater that you can find the update file when in TWRP in /cache in a folder fota but it will likely be in a LG specific format so may don't help you much.
Third thing :
Disable the LG updater within TWRP (search for a howto)
Sent from my LG-H815 using XDA Labs

Categories

Resources