Related
I own a nexus 7 2012, unlocked, rooted, twrp recovery and stock lollipop.After following this
guide http://nexus7.wonderhowto.com/how-to/boost-stock-volume-levels-your-nexus-7-for-louder-sounds-all-around-0158699/#
i lost all the sound in my device!!!Even when i flashed the back-to stock-level zip, nothing happened and i have no sound at all.Probably this guide is not for lollipop, but i want your help.Is there any way to get back the sound, avoiding clean install and setting up the whole tablet from the beggining?
If you open the zip you downloaded, you will notice It contains an xml file. Find a copy of the same file and place it in /system/etc
Technically, you could download a factory image from google, extract the system.img from it and flash it using fastboot
I am not a programmer and have little knowledge about flashing the ROM so to make sure I understand what I need to do and the order it needs to be done.
My Nexus 10 works great still, I have not had a security update for 2 some years and am concerned about this. Last October I tried to upgrade to 6.0 but it would not recognize the new rom and I ended up going back to the original 5.1 rom.
What I need to know is how to do it in a way I can understand. I have seen a utube video of someone that has been able to do it. So I know it can be done. Just need to know how.
Thanks,
Mike B.
Assuming you have a PC use this tool to unlock then root and install a custom recovery
Next download a Nougat rom like Lineage
Also download gapps and SuperSU
Copy the rom, gapps, and supersu into a folder on your tablet
Now reboot the tablet into recovery and do a full wipe then from recovery
Flash the rom
Flash gapps
Flash SuperSu
Reboot to system and give it a few minutes on the first boot
DISCLAIMER
I am not responsible for anything that happens to your device on following these steps. These are untested steps that worked for me and might work for you.
PREREQUISITES
1. PC with adb
2. Unlocked Bootloader
3. TWRP
4. MIUI 9 [Might work with other ROMs, not tested]
5. Lazyflasher zip
NOTES
1. If you are on a custom ROM, chances are that camera2 api is already enabled. Use Manual Camera Compatibility to verify.
2. If you are on MIUI, updating using ota might reset build.prop file. This might help, not tested. Update: I successfully updated to MIUI 9 Global 7.10.19 | Beta, see below for steps,
3. I am using Google Camera v4.4.020.163412804 on MIUI 9 Global 7.9.7 | Beta, and it is a HUGE improvement over the stock camera.
STEPS
1. Boot into TWRP. (Guide if you don't have TWRP)
2. Mount System.
3. Take NANDroid backup. (Optional but HIGHLY RECOMMENDED)
4. Connect to PC and execute the following command in terminal:
Code:
[SIZE="3"]adb pull /system/build.prop[/SIZE]
5. This copies build.prop to the current directory. (C:\Users\[USERNAME] by default on windows)
6. Copy it to another directory for backup.
7. Open in editor and add the following line at end:
Code:
[SIZE="3"]persist.camera.HAL3.enabled=1[/SIZE]
8. Save and exit.
9. Execute following commands:
Code:
[SIZE="3"]adb push build.prop /system/
adb shell
cd system
chmod 644 build.prop
[/SIZE]
10. Copy lazyflasher to internal storage.
11. Flash using TWRP.
12. Reboot to system.
13. Use Manual Camera Compatibility Checker to verify.
14. PROFIT!
15. Install the latest Google Camera HDR+ Port. (Optional but HIGHLY RECOMMENDED ;P)
UPDATING MIUI
1. Download the official recovery zip from here.
2. Download latest TWRP from here
2. Reboot into TWRP.
3. Take NANDroid. (Optional, just in case . . .)
4. Transfer ROM zip, TWRP img and Lazyflasher zip to internal storage.
5. Flash ROM zip. (Took about 10 minutes)
6. Flash TWRP img. (Go to flash -> select flash image -> select twrp-[v].img)
7. Flash Lazyflasher zip.
8. Follow steps 4 through 9 of above instructions. (Yes, build.prop also gets replaced on update)
9. Reboot to system.
10. Wait patiently.
11. VOILA !!
LINKS
1. Manual Camera Compatibility Checker
2. Lazyflasher Zip
3. Google Camera HDR+ Port
4. Latest MIUI Recovery Image
5. Official TWRP for mido
6. Sources: (1) (2) (3)
Hope this helps. Try and comment if this works for you in other ROMs. Also let me know if anything is unclear.
TWRP Tweaks (MIUI 9 Beta)
The method in this thread basically allows you to edit build.prop without rooting, which opens up a lot of possibilities. Here are some other useful tweaks to build.prop that I use.
(Note: If a line is already present in the file, edit the line otherwise add at end.)
1. Enable MIUI's full screen gestures
Code:
[SIZE="3"]
qemu.hw.mainkeys=0
[/SIZE]
2. Add EIS and disable noise cancellation
Code:
[SIZE="3"]
persist.camera.eis.enable=1
persist.camera.HAL3.enabled=1
ro.qc.sdk.audio.fluencetype=fluencepro
[/SIZE]
3. Turn off noise cancellation for audio recordings
Code:
[SIZE="3"]
persist.audio.fluence.voicerec=false
[/SIZE]
4. Fix Google Assistant talkback
Code:
[SIZE="3"]
mm.enable.qcom_parser=245389
[/SIZE]
Sources: (1)
Do reply if you are using some build.prop tweak and I'll add it here!
is it possible to make the flash-able zip work with stock recovery?
What does the lazyflasher zip actually do? A quick search on google shows a custom kernel installer.
joefso said:
is it possible to make the flash-able zip work with stock recovery?
Click to expand...
Click to collapse
I am not sure if it is safe to flash zips from stock recovery. Even if you could, you would not be able to take NANDroid, so you are doomed if things go south. Still, if you want, you could try and then we'll know
mato_d007 said:
What does the lazyflasher zip actually do? A quick search on google shows a custom kernel installer.
Click to expand...
Click to collapse
The source of the lazyflasher zip (2 in sources) says:
This device uses dm-verity
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab.
Click to expand...
Click to collapse
When I was trying the adb method, I was getting a bootloop, because (I think) the system partition had been modified (new build.prop replaced old one). Flashing this zip solved this, so I guess it essentially allows modifications to the system partition.
A_K_S_H_ said:
I am not sure if it is safe to flash zips from stock recovery. Even if you could, you would not be able to take NANDroid, so you are doomed if things go south. Still, if you want, you could try and then we'll know
Click to expand...
Click to collapse
I am willing to try because it would be great if this could work withouth using twrp, root or a unlocked bootloader.
Are the scripts compatible?
joefso said:
I am willing to try because it would be great if this could work withouth using twrp, root or a unlocked bootloader.
Are the scripts compatible?
Click to expand...
Click to collapse
They should be, as I used them with stock MIUI, stock kernel. However, are you going to flash a zip on locked bootloader? Is that even possible? Why would modifications to the system partition be allowed with locked bootloader? What would be the point of locking if that is the case?
A_K_S_H_ said:
They should be, as I used them with stock MIUI, stock kernel. However, are you going to flash a zip on locked bootloader? Is that even possible? Why would modifications to the system partition be allowed with locked bootloader? What would be the point of locking if that is the case?
Click to expand...
Click to collapse
I assumed that if OTA updates can be flashed through bootloader then by that logic /system could be modified too, right? hmmm
In Android devices, Recovery is an Android-based, lightweight runtime environment separate from and parallel to the main Android operating system. Recovery's original purpose was:
to apply software updates to the device, e.g. OTA updates, and
to erase user data and cache, e.g. for troubleshooting or preparing the device for resale (factory reset) and
to run (another) external tool from microSD flash memory
https://forum.xda-developers.com/wiki/Recovery
Click to expand...
Click to collapse
Thanks... BTW..
You can simply add that line using any file manager with root permissions and after rebooting device it works..
amit.tiger12 said:
Thanks... BTW..
You can simply add that line using any file manager with root permissions and after rebooting device it works..
Click to expand...
Click to collapse
Read the title : WITHOUT ROOT
A_K_S_H_ said:
Read the title : WITHOUT ROOT
Click to expand...
Click to collapse
yep I found..
do you have any solution for locked bootloader or everything stock??
amit.tiger12 said:
yep I found..
do you have any solution for locked bootloader or everything stock??
Click to expand...
Click to collapse
Unfortunately I don't have access to a stock mido right now, and I don't want to lock my bootloader.
If you're willing to risk it, you could try these steps:
1. Go to developer settings and enable adb.
2. Follow steps 4 to 9 of main post (with device switched on)
3. Reboot.
You might get a bootloop on rebooting, in which case you'd have to get into stock recovery and factory reset, because afaik, stock recovery doesn't give you adb.
Do tell what happens if you try this, good luck!
When I replace the build.prop the phone goes bootloop. It does not matter I use adb or root explorer or something... Why is that? BTW only this method worked: I used an app called build prop editor and worked like a charm! Thank you. If you did not tell that it was possible to enable camera 2 api on miui 9, all my hopes would be lost. So I suggest everyone to use another methods in case this does not work.
Does this work for MIUI 8? I dont want to root my phone but would like camera2
qun said:
Does this work for MIUI 8? I dont want to root my phone but would like camera2
Click to expand...
Click to collapse
It should, provided you have unlocked bootloader, but I haven't tested yet. Take a backup and try! Also, don't forget to reply what happens if you do try.
Can someone tell me what is this?it was set to no hdr+ on default.im on miui 9 global beta 7.12.8
In the end of the TWRP guide it says to flash lazyflasher.zip . In the end of this guide it also says you have to install lazyflasher.zip .
Do you have to install it both times or is once enough ? What would happen if you follow both guides to the letter and install it twice ?
Ghavio1516 said:
Can someone tell me what is this?it was set to no hdr+ on default.im on miui 9 global beta 7.12.8
Click to expand...
Click to collapse
These are configs, check and see which one works best for you.
foxhunt said:
In the end of the TWRP guide it says to flash lazyflasher.zip . In the end of this guide it also says you have to install lazyflasher.zip .
Do you have to install it both times or is once enough ? What would happen if you follow both guides to the letter and install it twice ?
Click to expand...
Click to collapse
No, once should be enough, but flashing twice won't cause any trouble either.
This is based on the semi-guides found here:
https://forum.xda-developers.com/honor-7x/how-to/finally-android-pie-t3830416
https://forum.xda-developers.com/honor-view-10/development/rom-aosp-pie-t3829466/page3
Both were a bit vague about certain parts, and also used Bitgapps, which doesn't give you the full functionality of open gapps, which I prefer, so I decided to make my own with more detail to hopefully help people avoid some of the issues I ran into. This is running very well on my BND-L24, I am not responsible for any damage to your phone.
Files you will need:
HuRUpdater (Only if not on stock rom): HURUpdater
The latest build from here: Roms
This twrp: Twrp
9.0 Open Gapps *Use the 10/1 version, the 10/2 google play services constantly crashes* (I used the mini version since it overwrites unnecessary apps and stock with cause any app that uses webview to crash): Open Gapps
1. You need to flash your stock firmware if you are on a custom rom, I used HuRUpdater, pretty easy, just follow their instructions.
2. Extract the rom and go to /META-INF/com/google/android and open updater-script with Notepad++
3. Delete all the text that comes before the first "ui_print" and save
4. Rezip and load the rom and gapps onto your micro sd
5. Flash the rom, but not gapps yet (If you flash both, you will get stuck in the setup wizard when you boot)
6. Boot into the rom, then restart and boot back into twrp
7. Flash gapps and boot into the rom
8. Now there will be a notification saying the phone is trying to run the google pixel setup, just hold down that notification, it will take you to that app in the setting and you can just disable it to get rid of the notification
9. You're all set!
Also, Magisk works perfectly with this
Enjoy!
TiklMiPickles said:
This is based on the semi-guides found here:
https://forum.xda-developers.com/honor-7x/how-to/finally-android-pie-t3830416
https://forum.xda-developers.com/honor-view-10/development/rom-aosp-pie-t3829466/page3
Both were a bit vague about certain parts, and also used Bitgapps, which doesn't give you the full functionality of open gapps, which I prefer, so I decided to make my own with more detail to hopefully help people avoid some of the issues I ran into. This is running very well on my BND-L24, I am not responsible for any damage to your phone.
Files you will need:
HuRUpdater (Only if not on stock rom): HURUpdater
The latest build from here: Roms
This twrp: Twrp
9.0 Open Gapps *Use the 10/1 version, the 10/2 google play services constantly crashes* (I used the mini version since it overwrites unnecessary apps and stock with cause any app that uses webview to crash): Open Gapps
1. You need to flash your stock firmware if you are on a custom rom, I used HuRUpdater, pretty easy, just follow their instructions.
2. Extract the rom and go to /META-INF/com/google/android and open updater-script with Notepad++
3. Delete all the text that comes before the first "ui_print" and save
4. Rezip and load the rom and gapps onto your micro sd
5. Flash the rom, but not gapps yet (If you flash both, you will get stuck in the setup wizard when you boot)
6. Boot into the rom, then restart and boot back into twrp
7. Flash gapps and boot into the rom
8. Now there will be a notification saying the phone is trying to run the google pixel setup, just hold down that notification, it will take you to that app in the setting and you can just disable it to get rid of the notification
9. You're all set!
Also, Magisk works perfectly with this
Enjoy!
Click to expand...
Click to collapse
Hey do you mind uploading your patched rom here??...for some reason mine is always giving error 7. Cheers
https://www94.zippyshare.com/v/dQwUSJWD/file.html
There's the modified updater-script for the 09/20 build, let me know if that doesn't work
TiklMiPickles said:
https://www94.zippyshare.com/v/dQwUSJWD/file.html
There's the modified updater-script for the 09/20 build, let me know if that doesn't work
Click to expand...
Click to collapse
Cheers mate! now it went through! but for some reason it is booting into a black screen, where volume button and power button is showing UI cards but the rest is blank! Hhaha
Did you go back to stock and do a full factory reset first?
I came from stock when I did it and still had to do a full reset
TiklMiPickles said:
Did you go back to stock and do a full factory reset first?
I came from stock when I did it and still had to do a full reset
Click to expand...
Click to collapse
Thanks for the help mate! Dont know! Tried the whole thing again and it worked! on the 25th SEP one !
I got a brand new Samsung Tab E 9.6" (SM-T560). Shame on me, I didn't notice before it comes with Android 4.4.4
As many apps require newer OS, I'm wondering if I can upgrade it to Android 6.0.
Plase note:
1. I'm not an expert, so please explain me as easy as possible how to do it, if it can be done;
2. please tell me, in case,if it's 100% legal and/or if it can void warrant.
Thank you.
Samsung Tab E
Check again --- Just picked up the same thing this week at Walmart for $129.00 + $25 Google Play credits - it came with 7.1.1. - Take it back sounds like you got some real old stock..
They do come with Android 4.4, however if you go to Samsungs web page you can find a crispy 7.1.1 image you can flash with Odin. Then if you wish you can unlock bootloader and flash a custom recovery like CWM or TWRP and then chainfires systemless root. Cheers! Upgrading to just 7.1.1 with Odin will not void your warranty, anything else that involves unlocking the bootloader will and is will trip samsungs knox security feature. If warranty is important only flash the 7.1.1 image using Odin.
Hello,
I'm searching forsuch an update, too. But It seems, that it was only released for USA and CA. But I'm from Germany. @xSLAYERx do you have a link to the ROM?
xSLAYERx said:
They do come with Android 4.4, however if you go to Samsungs web page you can find a crispy 7.1.1 image you can flash with Odin. Then if you wish you can unlock bootloader and flash a custom recovery like CWM or TWRP and then chainfires systemless root. Cheers! Upgrading to just 7.1.1 with Odin will not void your warranty, anything else that involves unlocking the bootloader will and is will trip samsungs knox security feature. If warranty is important only flash the 7.1.1 image using Odin.
Click to expand...
Click to collapse
heya, could you please share a link of this 7.1.1 with me? or the image itself, I can't find it anywhere and I'm stuck with 4.4.4
thank you!
hurkagyurka123 said:
heya, could you please share a link of this 7.1.1 with me? or the image itself, I can't find it anywhere and I'm stuck with 4.4.4
thank you!
Click to expand...
Click to collapse
Hi, I was with the same problem, and I posted here in XDA, I'm from Brazil, i have the model SM-T560, and now i'm using nougt, from Lineageos 14.1, and this was only possible, because someone from Xda, gave me the following link:
http://www.gearappsnap.com/2018/03/14/how-to-install-android-nougat-on-the-galaxy-tab-e-sm-t561/
The rom is of the SM-T561 model, but also works on the SM-T560, read everything before doing anything. When installing TWRP, you can install the version of the SM-t560, which will not make any difference.
One more thing, I advise you to see some YouTube tutorials how to install TWRP. Just in case.
Thank You for your help!
hurkagyurka123 said:
Thank You for your help!
Click to expand...
Click to collapse
For nothing, follow step by step that will work perfectly. Except this will end your warranty, but it's the only way to install an update. If you need any help, just talk.
gearappsnap site is not really good made.. The download links behind text which look like a normal one and also that it says, flash boot.img only when the memory is wrong..
Well, CM14.1 did not work for me.. I had to flash boot.img before EVERYTHING else, then rebooted again to TWRP and THEN install cm14.1.
Um, did you follow step by step?
I followed what was written, and for me it worked normal, The boot.img file is to fit just the memory of the table because it had some problem with the rom, without installing it, has tablet that got locked in infinite loop. And the links were working normal for me.
Links that i download:
ROM: https://drive.google.com/file/d/1D0wrGM4XyZMo-t3ll4trvJ93Pl1KEZ1V/view
Boot.img: https://drive.google.com/file/d/1bqGmu4NTlEeKdsFPGjIY9lnPqujjazr4/view
softkeys: https://drive.google.com/file/d/1ddSB28g1xTd0J7sl8V6QmlPZA1aX77ot/view
Gaps: https://opengapps.org/
First the TWRP is installed, with the battery above 70%, then restarts the tablet.
Within the TWRP:
1) Wibe-> advanced wibe-> selects almost anything but not microSD and OTC. and Wibe.
2) Back to the home page-> Install-> select the external storage (the files must be saved on the SD card).
3) The first file to be installed is the rom.
4) Once installed, go back to the files and at the bottom of the page you will click install image and install boot.img.
5) After Boot.img is installed, switch back to Install Zip, and Install the Softkeys.
6) After installing the softkeys go back and install the Gaps. (I used the ARM-7.1-Pico) and restart the tablet.
In my case I did not install superSU. That's what I did. This rom has some flaws but better than Kitkat, that's what I think.
thE_29 said:
gearappsnap site is not really good made.. The download links behind text which look like a normal one and also that it says, flash boot.img only when the memory is wrong..
Well, CM14.1 did not work for me.. I had to flash boot.img before EVERYTHING else, then rebooted again to TWRP and THEN install cm14.1.
Click to expand...
Click to collapse
HEY!
download this: https://mega.nz/#!yEpjCITA!9EA101hYDOajDwmBHKxSZhv3QkV-RI61MkLn0JYNRZY
unzip and install and follow steps.
1-install TWRP 3.0.2-1 via odin
2- copy ALL files of .zip in one folder in storage (mem stick)
3- power off and then power on IN TWRP (vol + + home + power button)
4- make full wipes except externar storage
5- install zip (first choice lineage -14, then choice open gapps, next choice key.zip)
6- install img (choice boot.img)
7- WIPE (Dalvik, cache)
enjoy android 7.1 in your tab e T560
63or63 said:
HEY!
download this: https://mega.nz/#!yEpjCITA!9EA101hYDOajDwmBHKxSZhv3QkV-RI61MkLn0JYNRZY
unzip and install and follow steps.
1-install TWRP 3.0.2-1 via odin
2- copy ALL files of .zip in one folder in storage (mem stick)
3- power off and then power on IN TWRP (vol + + home + power button)
4- make full wipes except externar storage
5- install zip (first choice lineage -14, then choice open gapps, next choice key.zip)
6- install img (choice boot.img)
7- WIPE (Dalvik, cache)
enjoy android 7.1 in your tab e T560
Click to expand...
Click to collapse
In reality you have to install boot.img and softkeys before, the reason is because they are modified for the T56X, otherwise install themselves after the gaps will give error when to use. At least it is what was written on the site, and so far I have been using no defect at all.
marcelo010 said:
In reality you have to install boot.img and softkeys before, the reason is because they are modified for the T56X, otherwise install themselves after the gaps will give error when to use. At least it is what was written on the site, and so far I have been using no defect at all.
Click to expand...
Click to collapse
I do not think that is effective. if you come from 4.4.4 and install it before the lineage ROM (BASE 7.1 for example) it will be erased again because with the new base everything is overwritten.
63or63 said:
I do not think that is effective. if you come from 4.4.4 and install it before the lineage ROM (BASE 7.1 for example) it will be erased again because with the new base everything is overwritten.
Click to expand...
Click to collapse
Well that didnt work for me.. Was coming from Stock 4.4 ROM. Flashed the CM14.1 AND softkeys, but NOT the boot.img, because you cannot flash zip and img files at the same time. Then I booted it and it crashed 10-60secs after it booted. Sometimes it had a boot loop.
Then I tried CM 13 which worked fine and in a german board, someone wrote (based on the gearappsnap site) that the boot.img has to be the first thing to flash and even reboot into twrp again and then flash CM14.1 + softkeys + gapps.
If you could install it, that's what matters, in my case it worked the way it was on the site, there are some bug's, but it's a lot better than the stock rom, and I was already using a custom rom on the T560 before installing this LineageOS 14.1,and it was this link:
https://forum.xda-developers.com/galaxy-tab-e/development/rom-lightning-t3716039
Szia!
did the upgrade work for You For galaxy tab e?
Done this and it worked but.........
The tablet is really slow, not netflix compatible with this version, and so on....
I think I just might downgrade again
After I have tried step 3, it didnt open in twrp mode. My tab stucks in black screen with "Samsung galaxt tab e " text in background.Please let me know how to proceed.
[QUOTE = "63or63, Post: 78613279, Mitglied: 4438103"]
HI THERE!
Download this: https://mega.nz/#!yEpjCITA!9EA101hYDOajDwmBHKxSZhv3QkV-RI61MkLn0JYNRZY
unzip and install and follow the steps.
1-install TWRP 3.0.2-1 through odin
2- Copy ALL .zip files to a folder in memory (mem stick).
3- turn off and then turn on IN TWRP (vol + + home + power button)
4- Make full towels except for external storage
5- install zip (first choice line -14, then select open gaps, next choice key.zip)
6- install img (choose boot.img)
7- WIPE (Dalvik, Cache)
enjoy Android 7.1 in your Tab e T560
[/ZITAT]
1000 tanks BR
.
1000 x danke es hat funktioniert
Translation: 1000 x thank you it worked