Related
I can't for the life of me find any sort of documentation for this update, Nothing is listed on T-Mobile's website and I cant find any immediate changes in the UI. The only info I can find about the tmo G3 is that it should be at D85110c. Anyone else get this D85110m update?
I just installed this update but can't find anything about it either.
Here's a screenshot of the build number and the baseband, in case that changed too.
someone help please. I accidentally clicked update even though I was rooted. Now when I try to enter download mode, it goes straight to TWRP and when I turn off my phone and then press the volume up button as it's turning off, it shows a screen saying firmware update but the percentage bar doesn't move. HELP
Did this update lock me in custom recovery?
Late yesterday (20140909) I got a status bar notification that a T-Mobile Software Update had been downloaded, and that I should click on it to update. I left it alone for some hours but then, used to a couple of years of easy Cyanogenmod updates (I'm rooted stock on this phone), I went ahead and clicked on the update. It threw me into TRWP and just sat there. I went looking for the download, to update manually from there, and couldn't find it. Now I can't get the phone to boot to system, just the recovery. After a few attempts, I tried restoring a five week old backup, but it still dumps me in recovery. Can't seem to get out of it. I can't even verify that this is the same update you guys are talking about (can't get to settings), although the timing is right. What can I do from here?
LG_D851
Rooted stock
Ripped out Carrier IQ stuff
If this is the wrong spot for this post, Mods, please help me out.
Lawrence
With this update, I can launch camera app from the lock screen.
bemusedsamadhi said:
Late yesterday (20140909) I got a status bar notification that a T-Mobile Software Update had been downloaded, and that I should click on it to update. I left it alone for some hours but then, used to a couple of years of easy Cyanogenmod updates (I'm rooted stock on this phone), I went ahead and clicked on the update. It threw me into TRWP and just sat there. I went looking for the download, to update manually from there, and couldn't find it. Now I can't get the phone to boot to system, just the recovery. After a few attempts, I tried restoring a five week old backup, but it still dumps me in recovery. Can't seem to get out of it. I can't even verify that this is the same update you guys are talking about (can't get to settings), although the timing is right. What can I do from here?
LG_D851
Rooted stock
Ripped out Carrier IQ stuff
If this is the wrong spot for this post, Mods, please help me out.
Lawrence
Click to expand...
Click to collapse
after NUMEROUS attempts and deleting all my data, I found an incredibly simple solution...
http://forums.androidcentral.com/ge...ricked-lg-g2-stuck-twrp-no-download-mode.html
DrakalDragon said:
I can't for the life of me find any sort of documentation for this update, Nothing is listed on T-Mobile's website and I cant find any immediate changes in the UI. The only info I can find about the tmo G3 is that it should be at D85110c. Anyone else get this D85110m update?
Click to expand...
Click to collapse
I've gotten what appears to be this update but I am rooted and TWRP so I know I cant select it to install like a few other users have done. Is there anyway to remove this update from the notification bar or maybe download it and apply through TWRP... I thought I turned off the call home feature when I bought the device and rooted a few months ago...
Heitem said:
With this update, I can launch camera app from the lock screen.
Click to expand...
Click to collapse
Ive had shortcuts on the lock screen to do this since the first week I had the phone... Im sure there has to be more to this update than this...
Long press on the notification and go into app info and turn off notifications to remove it from your notification bar
OhioDroid80 said:
Long press on the notification and go into app info and turn off notifications to remove it from your notification bar
Click to expand...
Click to collapse
Done... Any chance this decide to update on its own without any human intervention?? I dont have time to deal with fixing the phone if it does install and then fails because of TWRP right now...
I'm under the impression that human intervention is necessary for the update to apply itself on the phone. You don't chose yes it shouldn't load.
I think there is a battery life improvement.
tmo 10m update discussion is already going on in the tmo g3 general section: http://forum.xda-developers.com/tmobile-lg-g3/general/update-t2872755/post55357425
typicalgamer said:
someone help please. I accidentally clicked update even though I was rooted. Now when I try to enter download mode, it goes straight to TWRP and when I turn off my phone and then press the volume up button as it's turning off, it shows a screen saying firmware update but the percentage bar doesn't move. HELP
Click to expand...
Click to collapse
You can open the terminal emulator in TWRP and run "dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota". That might help. Helped with the LG G2 all the time.
I'm on Sprint. I think I can speak for everyone with a locked bootloader that we wish we had this problem. Haha. You just need stock recovery installed probably.
try another command
typicalgamer said:
someone help please. I accidentally clicked update even though I was rooted. Now when I try to enter download mode, it goes straight to TWRP and when I turn off my phone and then press the volume up button as it's turning off, it shows a screen saying firmware update but the percentage bar doesn't move. HELP
Click to expand...
Click to collapse
anjini said:
You can open the terminal emulator in TWRP and run "dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota". That might help. Helped with the LG G2 all the time.
Click to expand...
Click to collapse
Right .. then type:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
and enjoy
tested on d851 t-mobile
DrakalDragon said:
I can't for the life of me find any sort of documentation for this update, Nothing is listed on T-Mobile's website and I cant find any immediate changes in the UI. The only info I can find about the tmo G3 is that it should be at D85110c. Anyone else get this D85110m update?
Click to expand...
Click to collapse
Beginning September 10, the LG G3 received a software update to D85110m. This update provides features and improvements (Hide)
New Features
•T-Mobile Free Inflight Texting support
Improvements
•NA
This goes along with the Uncarrier 7.0 announcement from today, that T-Mobile has partnered with GOGO inflight Wi-Fi and will allow text, MMS and visual voicemail support inflight
updated while rooted and dragon rom
typicalgamer said:
someone help please. I accidentally clicked update even though I was rooted. Now when I try to enter download mode, it goes straight to TWRP and when I turn off my phone and then press the volume up button as it's turning off, it shows a screen saying firmware update but the percentage bar doesn't move. HELP
Click to expand...
Click to collapse
I updated on accident also and now I cant boot phone I tried to install new rom and nothing just bots right back to twrp . I cant connect from sideload as it doesn't finish loading sideload on my phone can I reinstall twrp from my sdcard ?? want to try updating that and see what happens
I also cant get download to connect it doesn't even make a sound like its connected to the pc like where it would install a driver nothing
bassmek2 said:
I updated on accident also and now I cant boot phone I tried to install new rom and nothing just bots right back to twrp . I cant connect from sideload as it doesn't finish loading sideload on my phone can I reinstall twrp from my sdcard ?? want to try updating that and see what happens
I also cant get download to connect it doesn't even make a sound like its connected to the pc like where it would install a driver nothing
Click to expand...
Click to collapse
I had the same problem and using these two commands in TWRP terminal emulator should work (as stated above). It will give you a 'no space' error, but that is expected. After that the phone should boot back to normal.
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
Be sure to not make any typos - apparently you can completely mess up your device. It took me quite a while to find out about the misc command - just the fota one didn't do it for me...
I got the OTA yesterday.
I traded in my S4 on the jump program yesterday, (9.16.14), and got an LG G3. When I got home I noticed that an update was downloaded and ready to install and since I had barely got it and it wasn't rooted or anything I decided what the heck. I applied the update and my version is now 110m and like the other guy said there is a "camera slider" on the lockscreen that I don't think was there before. But I have had this phone for less that 24 hours so maybe I'm wrong.
Phone - Moto Z play XT1635-02-DS
Android- 7.1.2
Installed TWRP 3.1.1.0
Viper addison 7.1.2
Here are my problem:
1. Flashed with supersu v2.79 and also v2.82, neither works. Phone still not rooted. When i tried toa access supersu app, it says "there is no su binary installed and supersu can't install it..."
2. Camera does open but it doesn't function, it stays dark. (I have custom gapps 7.1.x)
3. Proximity sensor does not seem to be working in other cases, but the phone goes dark as soon as i press dial or as soon as i pick a call and remains so untill the other party cuts the call. Otherwise i need to shut down the phone if i have to end the call from my phone.
4. When i shut down the phone, in order to reboot manually from recovery-reboot-bootloader. Otherwise it remains in twrp recovery.
Can anyone help please?
Have you tried flashing back to stock and seeing if that fixed these issues?
Pal Guite said:
Phone - Moto Z play XT1635-02-DS
Android- 7.1.2
Installed TWRP 3.1.1.0
Viper addison 7.1.2
Here are my problem:
1. Flashed with supersu v2.79 and also v2.82, neither works. Phone still not rooted. When i tried toa access supersu app, it says "there is no su binary installed and supersu can't install it..."
2. Camera does open but it doesn't function, it stays dark. (I have custom gapps 7.1.x)
3. Proximity sensor does not seem to be working in other cases, but the phone goes dark as soon as i press dial or as soon as i pick a call and remains so untill the other party cuts the call. Otherwise i need to shut down the phone if i have to end the call from my phone.
4. When i shut down the phone, in order to reboot manually from recovery-reboot-bootloader. Otherwise it remains in twrp recovery.
Can anyone help please?
Click to expand...
Click to collapse
This is not really a problem with the phone per se but the rom you chose to flash. The reboot issue can be checked by setting a command at bootloader using "fastboot oem fb_mode_clear".
gman88667733 said:
Have you tried flashing back to stock and seeing if that fixed these issues?
Click to expand...
Click to collapse
Thanks. But i don't have the stock rom. I didn't intend to use a custom rom. I tried to root it to recover some deleted photos and the moron that i am, i didn't back up the stock firmwares and while tweaking around in the recovery i somehow deleted the stock rom. This is my 1st time...
DroneDoom said:
This is not really a problem with the phone per se but the rom you chose to flash. The reboot issue can be checked by setting a command at bootloader using "fastboot oem fb_mode_clear".
Click to expand...
Click to collapse
Thanks... I tried the above command (it does recognize my device) bur this is what i get :
{bootloader} slot-count: not found
{bootloader} slot-suffixes: not found.
Pal Guite said:
Thanks... I tried the above command (it does recognize my device) bur this is what i get :
{bootloader} slot-count: not found
{bootloader} slot-suffixes: not found.
Click to expand...
Click to collapse
Is there an option for the bootloader in developer settings in your rom similar to the screenshot I attached? Make sure it's enabled.
DroneDoom said:
Is there an option for the bootloader in developer settings in your rom similar to the screenshot I attached? Make sure it's enabled.
Click to expand...
Click to collapse
Thanks for your concern. Developer option is 'on' and Multiprocess webView renderers seperately - 'on'. But i get the same problem. (and how do you attach screenshots ? I don't see any option for attaching files) In anycase, like you said, i think the problem has more to do with the rom. Can you please suggest me another rom or if possible link from where i can download stock rom for my phone.
Pal Guite said:
Thanks for your concern. Developer option is 'on' and Multiprocess webView renderers seperately - 'on'. But i get the same problem. (and how do you attach screenshots ? I don't see any option for attaching files) In anycase, like you said, i think the problem has more to do with the rom. Can you please suggest me another rom or if possible link from where i can download stock rom for my phone.
Click to expand...
Click to collapse
If your on xda with your browser, it's the paperclip icon to attach files. If you are using a 3rd party app that wraps xda into it then I can't help you there. As for going back to stock, Motorola made things a little critical when they released Nougat. Depending on how far you were on keeping the device up to date through stock, flashing the available stock images (which aren't signed) could brick the device if you aren't careful. There use to be an account on androidfilehost that uploaded current stock packages but it seems they're all gone now. If you remember the build number of the device before you rooted, that will help in picking the right stock files. I've taken a break in keeping my device rooted so I haven't kept track of the resources used to help go back to stock but they're in the MZP guide threads.
EDIT: a word of caution when reverting to stock:
-Don't use flash tools that don't let you see/edit the fastboot commands
-Do not use commands that touch modem/radio or gpt partitions
Found an upload of the latest build release keep it around when you figure out what you need to flash. It's best to clear system, data, and cache before flashing. Also have a rom (and twrp) at hand to adb sideload in case stock doesn't boot.
https://androidfilehost.com/?a=show&w=files&flid=215703
This Android version 7.1.1
Security patch: Sept 2017
Build number: NPN26.118-22-2
Thanks alot... ?
I´m using the latest firmware available for oneplus 3 and the volume on call is low! Using whatsapp the volume is good.
I´ve instaled and existing fix and the problem is solved but everytime that oneplus launch an firmware update I need to root the phone and install the fix!
Anyone with the same problem?
romaolp said:
I´m using the latest firmware available for oneplus 3 and the volume on call is low! Using whatsapp the volume is good.
I´ve instaled and existing fix and the problem is solved but everytime that oneplus launch an firmware update I need to root the phone and install the fix!
Anyone with the same problem?
Click to expand...
Click to collapse
I have the same. Which fix do you installed?
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
sakarya1980 said:
I have the same. Which fix do you installed?
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Click to expand...
Click to collapse
I use this fix https://androidfilehost.com/?fid=673368273298967516 - TWRP-OxygenOS-Low-InCall-Volume-Fix.zip
But in every update that is launched by oneplus you need to install it.
romaolp said:
I use this fix https://androidfilehost.com/?fid=673368273298967516 - TWRP-OxygenOS-Low-InCall-Volume-Fix.zip
But in every update that is launched by oneplus you need to install it.
Click to expand...
Click to collapse
Does this fix still work? I need to find a solution to the low volume when using the earpiece on the latest OxygenOS (5.0.1) with Oreo 8.0. I thought was a configuration issue, so tried a factory reset but the issue continues.
If I try this, when installing TWRP recovery, the device will lose all data, right? or this will not be the case?
pulsorock said:
Does this fix still work? I need to find a solution to the low volume when using the earpiece on the latest OxygenOS (5.0.1) with Oreo 8.0. I thought was a configuration issue, so tried a factory reset but the issue continues.
If I try this, when installing TWRP recovery, the device will lose all data, right? or this will not be the case?
Click to expand...
Click to collapse
Unlocking bootloader or wiping internal storage will result in loss of data. Mere flashing TWRP, if your bootloader is unlocked already, will not affect your data.
tnsmani said:
Unlocking bootloader or wiping internal storage will result in loss of data. Mere flashing TWRP, if your bootloader is unlocked already, will not affect your data.
Click to expand...
Click to collapse
Thank you @tnsmani. Yes, I just remembered that. I don't recall unlocking the bootloader on this device before.
So, can anyone using OxygenOS with Oreo 8.0 confirm if this patch works, I could go ahead and try it. It would suck going to the steps and wiping everything for it not to resolve the low volume issue.
Thanks!
Low volume in custom roms using nos
i can tell you for sure that it does not work, better, that specific ZIP does not wwork on Oreo.
The folder is wrong, you could simply extract the xml file and drop it to
Code:
/system/vendor/etc/mixer_paths_tasha.xml
Then it should work, i'm checking right now, report back if working. Maybe i'll update the zip too..
Edit:
Tested, almost broke my ear, here is the link for the fixed one for Android Oreo (I don't know if it works with AOSP)
TWRP-OxygenOS-5.0.1-Oreo-Low-InCall-Volume-Fix.zip
Enjoy
davide136 said:
i can tell you for sure that it does not work, better, that specific ZIP does not wwork on Oreo.
The folder is wrong, you could simply extract the xml file and drop it to
Code:
/system/vendor/etc/mixer_paths_tasha.xml
Then it should work, i'm checking right now, report back if working. Maybe i'll update the zip too..
Edit:
Tested, almost broke my ear, here is the link for the fixed one for Android Oreo (I don't know if it works with AOSP)
TWRP-OxygenOS-5.0.1-Oreo-Low-InCall-Volume-Fix.zip
Enjoy
Click to expand...
Click to collapse
I OEM unlocked my OP3 and then flashed TWRP (3.2.1-0). After flashing, I rebooted into recovery to make sure TWRP was installed. Then I rebooted the system. After booting system, it went back to stock recovery (when I checked again).
Tried again flashing TWRP and flashing your attached zip file immediately before rebooting the system again. Still, very low volume on call and it also went back to stock recovery again. How can I avoid this? Is it goes back to stock recovery does it means the patched file will be overwritten?
When flashing TWRP, do I need to "allow system modifications" the first time TWRP is flashed? I read that will cause a boot loop. I really don't need root, just need to be able to have the volume louder.
Thanks!
Does it give you any error during flash of the zip?
pulsorock said:
I OEM unlocked my OP3 and then flashed TWRP (3.2.1-0). After flashing, I rebooted into recovery to make sure TWRP was installed. Then I rebooted the system. After booting system, it went back to stock recovery (when I checked again).
Tried again flashing TWRP and flashing your attached zip file immediately before rebooting the system again. Still, very low volume on call and it also went back to stock recovery again. How can I avoid this? Is it goes back to stock recovery does it means the patched file will be overwritten?
When flashing TWRP, do I need to "allow system modifications" the first time TWRP is flashed? I read that will cause a boot loop. I really don't need root, just need to be able to have the volume louder.
Thanks!
Click to expand...
Click to collapse
After flashing twrp.. Reboot into recovery and root your phone
---------- Post added at 12:46 PM ---------- Previous post was at 12:45 PM ----------
Is there a similar file for low loudpeaker volume fix?
davide136 said:
Does it give you any error during flash of the zip?
Click to expand...
Click to collapse
No, no error at all. Everything looks like it worked fine. just after reboot system, it seems it did nothing the patch. Then when rebooting recovery, it was reverted to stock.
---------- Post added at 08:12 AM ---------- Previous post was at 08:10 AM ----------
drfox96 said:
After flashing twrp.. Reboot into recovery and root your phone
Click to expand...
Click to collapse
So rooting is required to avoid twrp being replaced by stock recovery again?
pulsorock said:
No, no error at all. Everything looks like it worked fine. just after reboot system, it seems it did nothing the patch. Then when rebooting recovery, it was reverted to stock.
---------- Post added at 08:12 AM ---------- Previous post was at 08:10 AM ----------
So rooting is required to avoid twrp being replaced by stock recovery again?
Click to expand...
Click to collapse
Yes
davide136 said:
i can tell you for sure that it does not work, better, that specific ZIP does not wwork on Oreo.
The folder is wrong, you could simply extract the xml file and drop it to
Then it should work, i'm checking right now, report back if working. Maybe i'll update the zip too..
Edit:
Tested, almost broke my ear, here is the link for the fixed one for Android Oreo (I don't know if it works with AOSP)
TWRP-OxygenOS-5.0.1-Oreo-Low-InCall-Volume-Fix.zip
Enjoy
Click to expand...
Click to collapse
Hi, I tried your fix on Open Beta Experience ROM 8.0. The volume issue was sorted but it broke the wake up system. I use face unlock and the moment I click any button, it wakes up my screen and looks for my face. After this patch, don't know how but phone stopped waking up. I had to use my fingerprint to unlock the phone. No other button was waking up the phone. Also the phone started getting hot and there was a tremendous amount of lag. I had to reflash the original OS to get it back to normal.
Know why ?
phrozenwire said:
Hi, I tried your fix on Open Beta Experience ROM 8.0. The volume issue was sorted but it broke the wake up system. I use face unlock and the moment I click any button, it wakes up my screen and looks for my face. After this patch, don't know how but phone stopped waking up. I had to use my fingerprint to unlock the phone. No other button was waking up the phone. Also the phone started getting hot and there was a tremendous amount of lag. I had to reflash the original OS to get it back to normal.
Know why ?
Click to expand...
Click to collapse
I can tell you that i tested with my phone and this never happened, considering that's not touching any file but this "/system/vendor/etc/mixer_paths_tasha.xml", I think it's something else causing what happened to your phone. Did you flash something else? Otherwise i'll take it down
amg_driver said:
i took a look in this file/fix.
my advice: dont flash this. imo the values are set too high and this fix could damage the hardware. as davide136 said "almost broke my ear"...
Encloused my fix created for latest NOS (Oreo).
But should work on other roms as well (if path to mixer_paths_tasha.xml is /system/vendor/etc/)
Try "88-fix". If it's a bit too low for you than flash "90-fix" - as filename suggets, its 2db louder.
Click to expand...
Click to collapse
Is it Oneplus 3T compatible?
Thank you for your work!
Hello everyone, i want to clarify something, it was never a software issue.it's just DUST, believe me.
After trying all the mods and flashable zips and increasing the values, it only increase the volume but it becomes like a walkie talkie and not clear at all. So i decided to open the phone and it's very simple you can watch a video, nothing very dagerous.
Remove the 2 screws and the sim tray, carefully try to rise the screen with a credit card from the lower part of the phone.
Disconnect the battery, remove the 8 screws and remember their placement( there is one hidden screw middle left under the white stick)
Remove the signal cable and screen and extentions ones, and carefully unclip the motherboard from the top middle and try to rise it, slowly
I advice to put some ductape on the camera lenses so no dust can go in
Remove your speaker
You'll find it clean and be surprised, but the remove the black mesh a'd then you'll be shocked.
Clean the black one with alcohol and then use alcohol+toothbrush to clean the speaker grill on the phone
Clean it till you can see light through it and when you blow on it air can pass through
Reassemble your phone and connect the battery at lassst you dont provoke a shortcut when you screw or something and VOILAAA
So after a few months of using my google pixel 2 xl, while I was using it I randomly got a black screen with the message:
"Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device: g.co./ABH
PRESS POWER BUTTON TO CONTINUE".
Now it happens every time I turn on my phone. :/
I Have tried doing a factory reset and it still appears.
My phone is not rooted, I have the official OS that I got it with it (updated it through the phone's updater).
The phone was purchased directly from the us google online store.
I've tried to contact their support but they didn't have a solution.
Please help me!!
almogsad said:
So after a few months of using my google pixel 2 xl, while I was using it I randomly got a black screen with the message:
"Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device: g.co./ABH
PRESS POWER BUTTON TO CONTINUE".
Now it happens every time I turn on my phone. :/
I Have tried doing a factory reset and it still appears.
My phone is not rooted, I have the official OS that I got it with it (updated it through the phone's updater).
The phone was purchased directly from the us google online store.
I've tried to contact their support but they didn't have a solution.
Please help me!!
Click to expand...
Click to collapse
Sounds like one of those non harmful, annoying messages at boot up. Is your bootloader still locked I assume? If so, have you tried side loading the March OTA. I think sometimes during the OTA updater process that some files don't always make it to the system, which is why you get those messages. Is your phone still functioning properly??
Badger50 said:
Sounds like one of those non harmful, annoying messages at boot up. Is your bootloader still locked I assume? If so, have you tried side loading the March OTA. I think sometimes during the OTA updater process that some files don't always make it to the system, which is why you get those messages. Is your phone still functioning properly??
Click to expand...
Click to collapse
First of all thanks for the response!
yes my bootloader is still locked.
Badger50 said:
have you tried side loading the March OTA
Click to expand...
Click to collapse
How do I do that? ^^
and it seems like the phone still functions properly, but I guess only time will tell
almogsad said:
First of all thanks for the response!
yes my bootloader is still locked.
How do I do that? ^^
and it seems like the phone still functions properly, but I guess only time will tell
Click to expand...
Click to collapse
Just follow these instructions if you want to side load an OTA. It's really not that hard ??
https://developers.google.com/android/ota
Badger50 said:
Just follow these instructions if you want to side load an OTA. It's really not that hard
Click to expand...
Click to collapse
Thanks! I'll try that...
Do you think it might fix the problem?
Edit:
it says in the guide:
"find the appropriate driver for your device from the OEM drivers"
but I don't know which one is mine ^^
almogsad said:
Thanks! I'll try that...
Do you think it might fix the problem?
Edit:
it says in the guide:
"find the appropriate driver for your device from the OEM drivers"
but I don't know which one is mine ^^
Click to expand...
Click to collapse
Once you choose the proper OS version for your pc, and install SDK, when you plug your phone in, it should automatically update your device drivers :good:
And yes, there's a good chance it'll fix your problem. Never any guarantees with this tech stuff though
Badger50 said:
Once you choose the proper OS version for your pc, and install SDK, when you plug your phone in, it should automatically update your device drivers :good:
And yes, there's a good chance it'll fix your problem. Never any guarantees with this tech stuff though
Click to expand...
Click to collapse
Hey! It seems like it worked!!!! Thanks!!
I only wish I hadn't listened to the google support team , and hadn't done a factory reset to phone before lol they don't seem to understand too much about their phones, the guy told me he thinks it's just an add
Thanks again man!
almogsad said:
Hey! It seems like it worked!!!! Thanks!!
I only wish I hadn't listened to the google support team , and hadn't done a factory reset to phone before lol they don't seem to understand too much about their phones, the guy told me he thinks it's just an add
Thanks again man!
Click to expand...
Click to collapse
Oh sweet! Glad to hear it my friend, well done. Now you can help others out with the same issue if it comes up :good: Yeah, the Google folks are kinda funny sometimes. The factory reset is their standard MO! And right, an add on the boot up screen....yeah that's funny! I'd be willing to bet most of them use iPhones!!??????
Badger50 said:
Oh sweet! Glad to hear it my friend, well done. Now you can help others out with the same issue if it comes up :good: Yeah, the Google folks are kinda funny sometimes. The factory reset is their standard MO! And right, an add on the boot up screen....yeah that's funny! I'd be willing to bet most of them use iPhones!!
Click to expand...
Click to collapse
How ironic! lol ???
Badger50 said:
Sounds like one of those non harmful, annoying messages at boot up. Is your bootloader still locked I assume? If so, have you tried side loading the March OTA. I think sometimes during the OTA updater process that some files don't always make it to the system, which is why you get those messages. Is your phone still functioning properly??
Click to expand...
Click to collapse
Thanks!! I also had this issue and following your suggestion to sideload the latest OTA, it appears to have fixed the problem.
I've been getting the same corrupt error on reboots on my xl 2(also not rooted), but I have not been able to get the latest OTA to sideload. It nearly completes but aborts last second and gives a Status 1 error. I'm not sure what I'm doing wrong here. Any help will be appreciated.
Got a similar run-around with Google support. When the factory reset was unsuccessful, they've recommended replacing the phone since it's under warranty, however they think replacing my virtually brand new phone with a refurbished phone is appropriate.
Apsel said:
I've been getting the same corrupt error on reboots on my xl 2(also not rooted), but I have not been able to get the latest OTA to sideload. It nearly completes but aborts last second and gives a Status 1 error. I'm not sure what I'm doing wrong here. Any help will be appreciated.
Got a similar run-around with Google support. When the factory reset was unsuccessful, they've recommended replacing the phone since it's under warranty, however they think replacing my virtually brand new phone with a refurbished phone is appropriate.
Click to expand...
Click to collapse
Are adb/fastboot tools the very newest?
Apsel said:
I've been getting the same corrupt error on reboots on my xl 2(also not rooted), but I have not been able to get the latest OTA to sideload. It nearly completes but aborts last second and gives a Status 1 error. I'm not sure what I'm doing wrong here. Any help will be appreciated.
Got a similar run-around with Google support. When the factory reset was unsuccessful, they've recommended replacing the phone since it's under warranty, however they think replacing my virtually brand new phone with a refurbished phone is appropriate.
Click to expand...
Click to collapse
Unlock then re-lock your bootloader(/s) maybe?
Great job guys, this solution with sideload latest OTA worked for me too with no need to unlock bootloader! :good::good::good:
I can confirm this working again. Pixel 2 XL with 9.0 and November security update.
Thanks!
I just had the corrupt message pop up (bootloader locked), and the sideload ota update seems to have worked!
michaelbsheldon said:
Are adb/fastboot tools the very newest?
Click to expand...
Click to collapse
I'm experiencing the same problem as Apsel, yes the adb/fastboot are the latest.
Error applying update: 15 (ErrorCode : kNewRootfsVerificationError)
E:Error in /sideload/package.zip (status 1)
Badger50 said:
Just follow these instructions if you want to side load an OTA. It's really not that hard ??
https://developers.google.com/android/ota
Click to expand...
Click to collapse
I know this is an old post but I'm having the same issue. Also cannot connect to pc due to, I'm assuming daughterboard issue this and previous pixel models have. I have been rooting phones since the S3 and am no virgin to the sdk. I tried to take it to ubreakifix which was a 4 hour round trip for me. I was told I would have to sign a waiver since the screen is glued to the phone and that was the only way to get to the internals. When I arrived I watched 4 bozos poke at the charging port for 20 min and then contradicting what I was told the night before over the phone that they were not comfortable doing the repair and then they tried to sell me a new device. I just got off chat with google and they want to charge me 270 dollars to fix even though I went to an authorized service center when it was in warranty. Will fastboot work over wifi?
Toolmighty said:
Will fastboot work over wifi?
Click to expand...
Click to collapse
'fraid not. Both the bootloader and recovery have stripped down hardware support, limited essentially to the display and storage. Neither has WiFi support that I know of, thus you have to use a USB cable.
I figured it out after I figured out how to fix the daughterboard issue w/o replacing the daughterboard. Verizon are some sneaky *^&$^s. Thx for the reply tho. I'm sure ur quite busy.
Code:
[B][U]Disclaimer:[/U][/B]
I am not responsible for any damage to you your device. Everything you do, you do on your own risk!
Last year I got a Galaxy Tab E (SM-T560) from Samsung for free as gift to my new mobile phone.
Unfortunately the ROMs for SM-T560NU tabs are not working on that device, but I found a working ROM of LineageOS 14.1 (Android Nougat 7.1.2) on the following page:
How to install Android Nougat on the Galaxy Tab E (SM-T561)
Click to expand...
Click to collapse
Original source (Russian language)
Click to expand...
Click to collapse
LineageOS 14.1 (formerly known as CyanogenMod) ROM is based on the Android stock ROM released by Google, which the LineageOS team modifies.
Credits go to the LineageOS team for making this ROM available to many devices and to independent developers like Ma3a_XaTa for porting this ROM to the Tab E SM-T561.
Click to expand...
Click to collapse
Just installed it to my tab and it seems working well!
I used the instructions from a comment at the bottom of the page:
Downloads:
ROM: LineageOS 14.1
Gapps: The Open GApps Project
Boot Image: boot.img
SoftKeyFix: KeyFix
Recovery: TWRP Recovery for Tab E
Root: SuperSU
Click to expand...
Click to collapse
Prerequisites:
1. Make sure you have TWRP 3 installed (HowTo)
2. Move the downloaded files to your Micro SD Card (>4GB recommended)
3. >50% battery charge
4. Some patience.
Click to expand...
Click to collapse
Installation:
1. Boot to TWRP 3 (Power + Home + Volume Up) and Swipe to allow modifications
Note: Make sure to Backup EFS and Modem to Micro SD Card in TWRP.
2. Wipe > Advanced Wipe > (Select Dalvik Cache, System, Data, Internal Storage, Cache ONLY) > Swipe to WIPE
3. Install > Select Storage > Micro SD Card > Select lineage-14.1-20180419-UNOFFICIAL-gtel3g.zip
4. Add More Zips > open_gapps-arm-7.1-pico-2018xxxx.zip
5. Add More Zips > keys.zip
6. Swipe to confirm flash and wait for 5-10 mins
7. After the Flash process DO NOT restart system.
8. Go back to Install > Install Image > boot.img > Select Boot Partition > Swipe to confirm flash
9. After the boot.img has been flashed DO NOT restart system IF you want Root.
10. Go back to Install > Install Zip > SR3-SuperSU-v2.82-SR3-20170813133244.zip > Swipe to confirm flash
11. Now Restart System.
12. Wait 10-15 mins, it will take some time.
13. Enjoy Lineage OS!
Click to expand...
Click to collapse
Known bugs:
- Charging while the device is off works, but does not show battery charge indicator animation.
Click to expand...
Click to collapse
Good luck and enjoy!
Code:
[B][U]Miscellaneous:[/U][/B]
[URL="https://www.hardreset.info/devices/samsung/samsung-t560-galaxy-tab-e-96-wifi/download-mode/"]HowTo bring the Tab to DownloadMode[/URL]
Hints & Tips:
1. To improve the speed of the tablet, turn of animations inside Developer Options.
2. You can also install an app freezer called "Icebox" to temporarily disable RAM hungry apps like Facebook, Chrome etc.
3. To ensure longer battery life, disable “double tap to wake” hidden somewhere in the settings (use the app called "Kernel Adiutor" from the Playstore).
4. If you don’t plan to put a SIM on this thing or if you are having a SM-T560 only, put it in airplane mode and then turn on your WiFI when needed. Turn of GPS/location or even sync when not necessary.
5. Disable "Adaptive Display" in the settings. It seems to make the tablet slower.
6. Improve the battery life of the tab by using an app called “L Speed“ (available in Playstore).
Hello, great post. I used this ROM before, but after some time it just stops working. You can't boot it anymore.
How long do you use it already?
mimuta said:
Hello, great post. I used this ROM before, but after some time it just stops working. You can't boot it anymore.
How long do you use it already?
Click to expand...
Click to collapse
I'm using it now for approx. 3 weekswithout any problems. How long did you use it?
BR, See
SeeDoubleYous said:
I'm using it now for approx. 3 weekswithout any problems. How long did you use it?
BR, See
Click to expand...
Click to collapse
I was wondering what version are you running? Everytime j download one it fails to flash through TWRP? You got a link to a download ??
V3rdeV1ntage said:
I was wondering what version are you running? Everytime j download one it fails to flash through TWRP? You got a link to a download ??
Click to expand...
Click to collapse
What version of TWRP are you using & what error do you get?
Have someone passed safetynet check ? Can you help me with pass?
The ROM is running ok so far on my T560, but I noticed some problems:
* If the tablet runs out of battery with Wifi activated, charging and booting it up causes a boot loop until Wifi is turned off. Something like that... it sometimes gives you the time to open the settings and turn off Wifi before it reboots.
* The Tablet's battery is drained by "Mobile Standby" in approx. two days, regardless of power save, battery saver and/or flight mode. When the Tab is idle all the time, the battery graph runs down in a straight diagonal line until the battery is empty, approx. 2 % per hour. Did not find a way to disable Mobile Standby on my T560 which doesn't even have a modem (maybe that's the problem).
* The system is a bit laggy given that it's a quad core, but turning off Animations helped. I suspect hardware acceleration does not work.
I'd switch to a better rom if I find one. But thanks anyways for the information and work! Better than nothing, I guess
Problems of ignition and charge of battery
Hello friends, I need a help I have a Samsung Tab E 9.6 = SM.T561, I installed Roon Custom Lineage 14.1 with TWRP, but the Tablet was downloaded and I can not charge it or turn it on, I searched everywhere and nobody gives me answers . I appreciate the help given. Thank you
Hi, I hope someone who has tried this rom can give me some feedback on it. My main concern its if this is stable and faster than ron. Any idea?
s5minimalist said:
The ROM is running ok so far on my T560, but I noticed some problems:
* If the tablet runs out of battery with Wifi activated, charging and booting it up causes a boot loop until Wifi is turned off. Something like that... it sometimes gives you the time to open the settings and turn off Wifi before it reboots.
* The Tablet's battery is drained by "Mobile Standby" in approx. two days, regardless of power save, battery saver and/or flight mode. When the Tab is idle all the time, the battery graph runs down in a straight diagonal line until the battery is empty, approx. 2 % per hour. Did not find a way to disable Mobile Standby on my T560 which doesn't even have a modem (maybe that's the problem).
* The system is a bit laggy given that it's a quad core, but turning off Animations helped. I suspect hardware acceleration does not work.
I'd switch to a better rom if I find one. But thanks anyways for the information and work! Better than nothing, I guess
Click to expand...
Click to collapse
I have my T560 all the time in airplane mode with Wifi on. Battery drain is no problem at all.
It is also written in my second post:
HTML:
https://forum.xda-developers.com/showpost.php?p=78977223&postcount=2
aribetty said:
Hello friends, I need a help I have a Samsung Tab E 9.6 = SM.T561, I installed Roon Custom Lineage 14.1 with TWRP, but the Tablet was downloaded and I can not charge it or turn it on, I searched everywhere and nobody gives me answers . I appreciate the help given. Thank you
Click to expand...
Click to collapse
I had a similar problem in the beginning. Seemed as the tab was in a bootlooporsomething similar with black screen.
The only solution I found was to wait some days until the battery was empty, charge the tab and directly started to download/recovery mode and flash it again.
Now it is working fine with this ROM.
Rittachi said:
Hi, I hope someone who has tried this rom can give me some feedback on it. My main concern its if this is stable and faster than ron. Any idea?
Click to expand...
Click to collapse
I am using it now for ~2.5 months and I am quite happy with it.
It is much better then the stock ROM.
Hi @SeeDoubleYous and guys. I was reading the Forum and decided to share with you my experience with this ROM. Well, I'm owner of a SM-T560 (in US and Canada this model is T560NU I don't know why it's different just in these two countries ). Anyway....
I made all the steps described on the step-by-step Instructions. (TWRP Recovery via ODIN, Root, ROM, GAPPS, etc etc etc).
I'll be honest with you. My t560 turned in a piece of sh... Very Slow, Apps Stucking all the time, sometimes bootlooping too... i used the Tab for almost 3 weeks. After that I decided to reset the device and I did all steps again using the same ROM (I reinstalled the TWRP RECOV via ODIN, proceeded a Factory + Internal Memory Wipe, Installed the LINEAGE 14.1 OS, etc, etc, etc) But this time I choose the "Micro" GAPPS option instead "PICO". Installed Root SU, etc, etc exactly as the directions wrote in the top page.
For my surprise, It's perfect Now!!!! ROM is great.... No problems of RAM, Bootlooping, Stucking, APP crashing... Absolutelly Nothing!
I don't know why, but it seems that the secret is install for first time and use for some weeks even its is not working fine. And After that, proceed All the step-by-step again from the very beggining. (Reinstall TWRP, ROM, GAPPS, Keys, "Boot Image" and ROOT SU). It will work fine on SM-T560 just from the second Install on.....
All Best guys
I need help. My screen is stuck on boot again
Am I bricked?
Hi guys, I've got a T560 tablet with the official ROM and I'm researching to upgrade it's software.
Currently I'm away off-shore for work but as soon as I get home I'll try this ROM.
I've been a fan of CyanogenMod since the early days and I'm eager to try it so I can bring some new life into my old tablet.
Since this ROM is for the SIM card variant T561 I was searching for a way to disable the Radio altogether and I found this:
https://android.stackexchange.com/q...le-radio-signal-in-a-phone-without-a-sim-card
Basically it disables the RIL with a simple Terminal Command:
Code:
su -c "setprop persist.radio.noril 1"
Can someone try this and see if its working properly? (OFC after a Back-up is done) Its persistent through reboots so you don't need to use Airplane Mode anymore and maybe it will help with the battery draining problem.
Also one question for the guys who are currently using this ROM:
Is Magisk working? After everything is set-up can we uninstall SuperSU and install Magisk for root?
Thank you,
Have a nice day!
SpawNyK said:
Code:
su -c "setprop persist.radio.noril 1"
Click to expand...
Click to collapse
I've tried the command and it worked, no reboots even if the airplane mode is off and no problem so far.
I don't know if the battery life is better now because I've just done it.
For the other question, I haven't tried because I like SuperSu, but I think there's no problem.
gucio1976 said:
And what do you think about it.
https://mega.nz/#!49QXRIAb!7FtqWknBNzIe5-Ak-Jgmq7N71JB4TcGEi-MjuQCuvhw
Click to expand...
Click to collapse
Can you please provide a guide for flashing this?
Like which GApps version should I use, etc...
I get in red, does something affect ROM? e: unknown command [log]
Hey,
does this rom works with SM-T562??? (3G)
Is there any updated ROMs like LOS 15 or 16 for SM-T561 (gtel3g), I tried to Port LOS 16 but I get error 7 while flashing in TWRP(V3).
gucio1976 said:
And what do you think about it.
https://mega.nz/#!49QXRIAb!7FtqWknBNzIe5-Ak-Jgmq7N71JB4TcGEi-MjuQCuvhw
Click to expand...
Click to collapse
gucio1976 said:
I found it here .
https://www.youtube.com/watch?v=-4h_3qDRiv8
Click to expand...
Click to collapse
Why should you use the old version, if this thread offers a newer one?
gucio1976 said:
---------- Post added at 11:33 ---------- Previous post was at 11:13 ----------
Something else. Maybe it will be useful to someone.
https://www.youtube.com/watch?v=7JpUomQs2ok
Click to expand...
Click to collapse
I think that's the same version as offered here...
shreejalm said:
Is there any updated ROMs like LOS 15 or 16 for SM-T561 (gtel3g), I tried to Port LOS 16 but I get error 7 while flashing in TWRP(V3).
Click to expand...
Click to collapse
I did not find any new version. The ones available are only working with the SM-T560NU....
Sorry!