yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 4 Q&A, Help & Troubleshooting] xjimmy:
T337A Temp root, boot(LP fix).tar, & official 5.1.1 firmware. Help w/permanent root?

I just thought that all of this might help a permanent root be developed. I have no idea how to work the magic that developers here perform all the time. I just thought I would post this information if it helps to get a permanent root on the T337A running 5.1.1, and politely ask that if anyone out there is able to check this out, I would greatly appreciate it. So, here's my b.s. :

TechNyne66 posted that Kingroot apk temporarily roots T337A and knox is not tripped:

http://xdaforums.com/tab-4/general/att-tab-4-8-t337a-temp-root-t3301345

I've rooted it this way, but reboot softbricks the tablet. It can be rebooted with the boot(LP fix).tar via odin:

http://xdaforums.com/tab-4/general/rooted-nk2-att-t377a-t2992639

This will boot it back up with a custom logo and root is essentially removed.

In my experience, after all this has happened, the battery life sucks.

Now the 5.1.1 firmware is available here, to fully return to stock:

http://xdaforums.com/tab-4/general/official-att-lollipop-firmware-tab-4-sm-t3439252

Just throwing it out there. Maybe people have seen all of this and it doesn't help at all. It just sounded like it could be toyed with, now that there's an official firmware for 5.1.1 available. Anyone I could approach with this to ask for help? I don't want to go bugging people though...

If you read all this shiz, thank you.
[Galaxy Tab 4 Q&A, Help & Troubleshooting] xjimmy:
Nobody? Is there anyone who could help, or direct me to someone who can possibly help with rooting the T337A with this information?
[XDA Assist] engloa:
This is not the right place.

You were already advised to post in the Ask any Query Newbie Friendly thread last month.

Please post there with all relevant details.

Thanks and thread closed
[Huawei MediaPad X2] STEKAM:
Hello,

After trying to update the B211 using the dload version ( extract zip and put all files into the dload forlder of my sd card )

the software update got stucked at 90% and now i cannot boot anymore...

What should i do ? Use dload with full zip ? shoudl that be working ?

stucked at Honor logo shining :(
[Huawei MediaPad X2] STEKAM:
I tried putting the dload/update.app from 112 into the SD and POWER+VOLUP+VOLDOWN... Failed...

Tried to extract system/recovery/.... from the update.app and flash using fastboot got an error : "WRITE" remote command not allowed

I'm out of idea...

I've got 2 zips ( 1 for 112 and one for 211 )....

the one from 112 contains only 1 update.app the one from 211 contains 1 update app + sytem folders etc etc...

Any help ?

br

SK
[Huawei MediaPad X2] audioralf:
Exctracting B211 zip file and dload the included update.app leads excatly in this problem.

Update.zip has to be started via EMUI firmware update as incremental update.

DO NOT UNZIP update.zip. WARNING FOR EVERYONE who thinks he can update with this files with the 3 Button press method.

To get back your system do this:

you must unlock bootloader (see root thread)

fastboot oem unlock xxxx ( xxxx is the booloader code wich you can get via chinese site

it's a bit difficult and requires some data about your device. but I hope you have written down your IMEI and serial number or find it somewhere on the box.

If you have not rooted before and can not unlock your bootloader, you have no chance to get back a running system, as far as I know.

If you have unlocked then you can flash root, system and recovery extracted from B112 update.app (huawei update extractor).

Then start Huawei recovery (vol + on boot) and select factory reset if available.

Then put update.app from B112 to dload folder and boot device with vol+ and vol -

If you are on B112 then do a factory reset from EMUI.

Then delete the update.app in dload folder and replace it by the update.zip

Then start the system and select incremental update.

After sytem starts do minimal configuration and restart device in fastboot mode.

Then flash the neweset twrp for android 6.0

fasboot flash recovery2 X2-TWRP-3.0-2-BLACK-BLUE.img

start TWRP via rebooting device with volume up key pressed and USB connected.

in TWRP flash KANGVIP-SLIM-B211 7-27-16.zip

---------- Post added at 09:25 PM ---------- Previous post was at 09:18 PM ----------

There is a rollback file for Android 6.0 which brings you back to Android 5.0

If you can't root, you can try this as last chance.

unpack this file .

It includes a "dload folder" and put the content to dload folder of your device /SD card and start with 3 finger
[Huawei MediaPad X2] STEKAM:
hey, thanks for your answer...

when you say that : " If you have unlocked then you can flash root, system and recovery extracted from B112 update.app (huawei update extractor). "...

the thing is i do have an error while flashing system and recovery ? " Cannot Write ... "

stekam
[Huawei MediaPad X2] STEKAM:
screenshot bellow :(
[Huawei MediaPad X2] audioralf:
Have you enabled USB Debugging and unlocked successful by yourself?

We have seen many devices showing unlocked, but were relocked.

My device: 701->703 B211 xposed 86
[Huawei MediaPad X2] STEKAM:
I think you might be correct but...

with my huawei ID i cant request unlock code...

Any one can sent me an unlock code if i sent you all necessary info ???
[Huawei MediaPad X2] audioralf:
Look into your pm

My device: 701->703 B211 xposed 86
[Huawei MediaPad X2] STEKAM:
sorry !

answer supplied !

thanks buddy
[Huawei MediaPad X2] STEKAM:
thanks in advance!
[Huawei MediaPad X2] STEKAM:
:good:

Feeling Crazy, no tablet, no unlock code ! :silly: :crying: :(

Any help is welcome if you cant supply me an unlock code i do have all necessary info's :)
[Huawei MediaPad X2] audioralf:
Huawei requires the 14 days 'online' for his 701 device.

My device: 701->703 B211 xposed 86
[Huawei MediaPad X2] STEKAM:
What if impossible?!
[OnePlus X Q&A, Help & Troubleshooting] crazykas:
I was having extremely low volume mic issue/mic distorting issue on my OPX almost every ROM. I have tried almost every mix fixes as well. The only fix i've found was Paranoid Android ROM. But with the new official MM update , i wanted to try that too. Thing is here i again im having this mic issue :eek: anyone else having this or only for me?? i tried to flash back to PA but every time phone stuck on a bootloop may be coz of new firmware update.. Any fix guys?
[Galaxy Ace II Q&A, Help & Troubleshooting] genisagan:
Hello there. So I made a quick search here about this problem, and it seems that many people complain that after installing Cyanogenmod, speaker makes this buzz noise. Well, I just installed Cyanogenmod 11 to my Galaxy Ace II (I8160) and I noticed that when I play a song I can also hear a buzz noise, after I pause it, the noise stays there for 2 sec and then it goes away. This happens everytime the speaker is activated, even when the volume off, for example, when playing games, even tho the volume is down (at 0) I still can hear that noise.

It doesn't seem to be a hardware problem, because it occurred right after I installed the new rom. I have tried installing another equalizer (besides DSP which comes preinstalled) , and even trying some odd solutions like turning off the system sounds. I don't know what else to do, but for sure I don't wanna go back to CM 10.2 or stock rom. So is there any solution?

p.s sorry for my bad english
[Xiaomi Mi 5 Questions & Answers] Sam0654:
I've got a Xiaomi mi5 Chinese model purchased at the beginning of July 2016.

It had these ads that would not disappear, I saw a few complaints around the web about them, but no solutions, so I decided to unlock, root and ROM.

I unlocked the bootloader and used twrp recovery and installed/flashed "Resurrection Remix M v5.7.3-20160810 gemini".

On installing/flashing Resurrection Remix, the recovery seemed to die and not be accessible. Whenever I tried it would just come up with the 'Mi" logo and stay there. I managed to get around this by going into FastBoot and flashing a new recovery, "twrp_gemini_v8.img", which is apparently for "MIUIv8", this worked, although the language is set to Chinese and I can't seem to find how to change this, but hasn't stopped me navigating around it using google translate from another phone!

Now my issue is that as a China version, there is no google applications and for some reason, I can not install using apk or flash using recovery. I've tried the following

- com.android.vending_6.8.21.F-all_0_3036847-80682100_minAPI14(nodpi)_apkmirror.com.apk

- com.google.android.gms_8.7.03_(2645110-480)-8703480_minAPI23(x86,x86_64)(nodpi).apk

- PlayStore_v7.0.12.H-all.apk

But all either close Google Play as soon as it opens barely showing a white screen or come up with a message saying that "Unfortunately, Google Services Framework has Stopped" repeatedly. I've tried clearing the cache and app data from each of the apps before uninstalling them and then starting again, but no luck.

Not sure where to go from here, the phone is pretty close to being thrown in the bin tbh, but would like to get some feedback from this forum before I give up.

Thanks

Sam
[Xiaomi Mi 5 Questions & Answers] chiragkrishna:
use this method to change into MIUI 8 Global version

skip the miflash tool,... extract everything using 7zip,... move files to root directory example C:\miui8

connect phone into fastboot mode and run flash_all.bat
[Xiaomi Mi 5 Questions & Answers] Sam0654:
Okay, thanks. That's put a new ROM on that does have Google Apps, but no longer Resurrection Remix. Also, strangely, the closest Locale to Australia was Vietnam!

Any pointers?
[Galaxy Grand Duos i9082 Q&A, Help & Troubleshootin] md41111@gmail.com:
please tell me, resurection remix offered the nav bar option in settings ,so can i enable it , does it any battery juice
[Nexus 4 Original Android Development] kldoc:
​

What is Omni?

Omni Gerrit Review

Disclaimer

#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/

DOWNLOADS:

omni-7.0-20161022-mako-HOMEMADE.zip

Because of the nature of Xposed framework, NO SUPPORT will be given to those running Xposed framework on Omni 6

CHANGELOG:

[CENTER]
2016-10-22:
-Video recording fixed on stock camera (snapdragon camera still have some issues there, jerky video)
-Omni features progressively backported

2016-10-4:
Initial Release[/CENTER]

You MUST DO A FULL WIPE, whether you are coming from homemade builds (aka my builds), or a previous version of OmniROM. Be certain to do a full backup of your data, apps, call logs, sms/text and so on before flashing.

GAPPS must be flashed BEFORE initial boot, they will NOT work properly if you flash them afterwards !!!

KNOWN BUGS:

[CENTER]- Camera recording only works with Google Camera
- Screen rotation isn't working
[/CENTER]

Omni only supports TWRP recovery, use any alternate recovery at your own risk.

RECOMMENDED TWRP

Source

OmniROM Source​

Only a few changes are taken from CyanogenMod, but thanks to them for those

CyanogenMod Source​

XDA:DevDB Information

OmniROM 7, ROM for the Google Nexus 4

Contributors

kldoc, MaR-V-iN, Maxwen, Entropy512, Xplodwild, Jiangyi

ROM OS Version: 7.x Nougat

Based On: AOSP

Version Information

Status: Testing

Created 2016-10-04

Last Updated 2016-10-21
[Nexus 4 Original Android Development] ddaggebi:
Wow.... already?

Thanks for the hard work! Any features?
[Nexus 4 Original Android Development] kldoc:
More or less the same features than in Omni 6, everything is being backported.

Battery led and custom notification led will be there in next build.
[Nexus 4 Original Android Development] ze7zez:
We expect android 8

Why such a hurry !?

Before you refine the A-7 will have A-8.

Of course it was a joke, but journalists already predict the future:

Android 8 : ce que l'on attend
[Nexus 4 Original Android Development] kldoc:
Mostly because I'm in vacations, and got the time this week to do the bringup for Nexus 4, then OmniROM got gerrit fixed so we could merge everything that needed to, from there, things go quite fast, team is actually quite efficient :)

I noticed a few kernel side commits i didn't merge yet, so tomorrow's build, you should expect a few things fixed, rotation should be fixed, and some omnigear stuff are coming back :)
[Nexus 4 Original Android Development] mandgeo:
Do you know if the future official omni 7 will require full wipe if coming from official omni 6???
[Nexus 4 Original Android Development] kldoc:
I think I stated it the header, yes, it will be needed to avoid any problem, Android 7 has a lot of changes.
[Nexus 4 Original Android Development] kldoc:
New build delayed for tomorrow, have been hard at work trying to solve the camera video recording, failed. Rotation is fixed.

Video recording seems to be a recurring issue on Android 7 for older devices, and none of the ROM I checked managed to really fix it for good. From there, I'm not actually certain it will ever get fixed, and because of this, I don't know if Nexus 4 will reach nightlies or not. I will publish builds as OmniROM features get backported, but won't go any further than this.

Given Google's pricing for Pixel, I am soon buying a Oneplus 3, and will switch to it for OmniROM support.

I'm not giving up totally on Nexus 4, but dev won't be as up to date as it was when I did Marshmallow or Lollipop.
[Nexus 4 Original Android Development] Chefov01:
Hi all! I have been wondering if Snapdragon camera is included, cuz that's the only thing stopping me from switching to Omni 7 or CM 14? :)
[Nexus 4 Original Android Development] kldoc:
Yes, Snapdragon Camera is included, it's actually replacing the stock AOSP camera, only video recording is broken on Nexus 4 atm, that's what I was mentioning earlier, no one has this properly working 100%, camera itself is able to take pictures, no issues there, but just video recording isn't possible atm.
[Nexus 4 Original Android Development] mrk2815:
I remember stepen wolf with cm 14 unofficial figuring on how ot fix it. but I am not sure if he has done so as of yet or not. but he di state it was on hhis list of things to do to fix the rom. so whwho knows between you and stepean with cm14 you guys can figure it eventually.

---------- Post added at 01:35 PM ---------- Previous post was at 01:18 PM ----------

just read his post he still has the same issue with camera video recording having issues it will record in 720 p ok but with 1080p has issues. so he will be working on it. so hopefully between kldoc and stepan the issue will get resolved.thats the only issue with nexus 4 having had the AOSP 7 rom on my nexus 4 over 2 months now. kldoc I am also agreeing with you google made a big disservice to the developer by raising the price of the pixel for the development community. as soon as I have some fund I will be joining in support and getting a 1 plus 3 as well. the only thing will be to get older nexus device and keep them up to date and then going forward go with other vendor to prove to google that they are not the only premium product with a outrageous price that the development community cant afford and then will end up jumping ot other product lines to support going forward in the future . that's one thing that google has now gotten out of touch with its community. they are forgetting that the development community got them to the big Android dance. The developers developers . I respect what all you guys and gals do here on XDA for all of us!!!!
[Nexus 4 Original Android Development] kldoc:
Feedback i have, is most devices actually have camera issues on Android 7, things will eventually smooth out and get polished :)

I still have a build to publish today, been working on that camera issue, but also working on cleaning up stuff to get that on OmniROM's gerrit and github.

I checked his work, but he's more or less at the same point everyone else is, sill no real solution atm.

Oh and by the way, my builds are also Selinux enforced ;)
[Nexus 4 Original Android Development] mrk2815:
will be patiently waiting ot test the next build you have out for nexus 4.thanksfor maintaining and building android 7 for nexus 4.
[Nexus 4 Original Android Development] kldoc:
Uploading the new build as we speak, Battery light are back, Custom notification lights are also back (didn't in Omni 6).

Rotation is fixed, battery display is back, and a lot of Omni features are back, doze mode isn't there yet, but should be soon.

EDIT: Link in the OP updated, enjoy :)

Have fun with OmniROM !

P.S.: I merged my commits on Omni repos for kernel and device trees
[Nexus 4 Original Android Development] kanishkad:
Awesome ROM, keep up the good work. :)

However, there are some issues I noticed;

1. Can't seem to change the SELinux mode to Permissive with SELinux mode changer.

2. Permission requests appear as in the screenshot with no way to take an action (can grant from settings though).

Btw, is SuperSU integrated into the ROM?
[Nexus 4 Original Android Development] kldoc:
No you will not be able to change SELinux to Permissive rom within the system, if you want to run OmniROM permissive, you need to build it by yourself, OmniROM (not only me) is really strict about this. The initial build was permissive, but it was a proof of concept. Android N changes a lot of things, there might be bugs here and there, but SElinux is relatively working well now.

Permission granting, i will have to check things on that, but ROM is barely coming together, 80% of our maintained devices are barely uploading a semi working build, will ask your for a bit of patience ;)

Supersu never was a part of OmniROM, and probably won't be anytime soon (if ever).

A screenshot without a logcat is more or less useless ...
[Nexus 4 Original Android Development] kanishkad:
Just to clarify if my post seemed like a complaint, this is awesome work and really glad that devs like you are keeping a 4 year old device alive :) Just wanted to point out the issues I faced in order to help you make it better..

I was able to set it to permissive by the command "setenforce 0". Need it to get Viper4Android working :D

I will post a logcat if I encounter any issues. Keep up the good work :good:
[Nexus 4 Original Android Development] kldoc:
Oh, I wasn't aware Viper4Android was still being maintained, external modifications aren't something we bring support to, mostly because it changes initial behavior and it's hard to predict what changes towards drivers support throughout system updates.

Someone in Omni pointed me at a modified video recording handling ( coming from slimrom actually), will give it a shot tomorrow.

I'm also planning to enable LTE support for those who need it in the future, even though I won't be able to test it (China's network don't handle those frequencies)
[Nexus 4 Original Android Development] DontPushButtons:
Your existing build actually already picked up LTE for me, with no modifications needed. Working just fine on my end :)
[Nexus 4 Original Android Development] kldoc:
Good to know, wasn't intended :p If it works well, glad that you're happy with it :D
[Nexus 4 Original Android Development] chrrh:
Can confirm this, but interestingly it is the same with a hommade build of my Nexus 5X.

Looks like an upstream bug :D

Unbelievable that our beloved Nexus4 is getting Nougat already, and that in a shape I would have never expected.

Keep up the great work :good:

Kindest regards,

chrrh...
[Nexus 4 Original Android Development] kldoc:
Can't work on this right now, my vacations ends today, I will first focus on blocking bugs, such as camera recording, my guess is that since more than one device is affected, it should have a patch rather soon.
[Nexus 4 Original Android Development] ddaggebi:
I really like Omni 7. It has unique apps and features, unlike other roms which is basically CM or pure AOSP + features. I'm not saying that they are bad, they have less bugs and more stability. But sometimes I miss the jellybean/kitkat era when there were 15+ different roms with unique designs and features. Omni 7 reminded me of those times. So big thanks to the omni team and dev kldoc!
[Nexus 4 Original Android Development] kldoc:
You'll manage to make me blush hahaha

Technically speaking, I'm not really a dev, I contribute, can read code, but it's been an eternity since the last time I actually wrote code. I still am on OmniROM for very simple reasons, its strict policy towards AOSP code makes it tougher to actually modify the core framework, when you add a feature, or modify the framework because of one device or another, it's always done with respect to the core code and other devices, we're not allowed to break AOSP compatibility.

A very simple example is the core sepolicy changes that most ROM have done on Nexus 4, I actually had to encapsulate it for userdebug builds only, and had to make sure it wouldn't break other devices.

Same thing goes for the libc clang flag, had to create a flag to disable clang for libc and enable it in boardconfig.

All those things are time consuming, and they often come at the cost of more advanced features, but they bring more stability and smoothness over time.

I'm actively following the work done by a few devs here in Xda that are working on Nexus 4, so don't worry, as soon as bugfix come, i'll integrate those.

Nightlies are already around the corner, devs have been hard at work, and most of the backport is done.

I don't know yet if Nexus 4 will make it, it all depends on that camera video recording thing, and for now, I'm going nowhere, lacking the time to go deeper. It does start recording, but file isn't kept, not sure why yet, since it's still broken, didn't publish a new build with those changes.

That's where I am now, waiting for some more advanced and skilled dev to find a solution that I could use to fix Omni 7 on Nexus 4.

Have fun with OmniROM :D
[Nexus 4 Original Android Development] Dav1_d:
Had a problem with the GPU touch boost on stock kernel. It runs at the highest frequency and scrolls down when the screen is touched, basically working in reverse; using another kernel solved this. This happened on the 06/10 build, I don't remember it happening on the build the day before.

Really appreciate the work that you are doing on mako with omnirom. Keep up the good work.
[Nexus 4 Original Android Development] kldoc:
What is GPU touch boost ? And what kernel did you use ?
[Nexus 4 Original Android Development] Dav1_d:
Touch Boost - When the user touches the screen and the GPU (or CPU) ramps up (boosts)the frequency accordingly.

The kernel I changed to was Revival by Spezi.
[Nexus 4 Original Android Development] kldoc:
I see, that's a particular power mode, you shouldn't use it on AOSP, this requires specific power management commits that I didn't and will not include in AOSP kernel, those were never proven stable, nothing I can do here. Only power modes that I support are the one originally planned by Google for Mako.

I'm betting it's tied to the rotation commits I did merge, blobs are already being sensitive due to the fact they're outdated, this might triggers more issues in the end, that's why this kind of modification won't be included in OmniROM for Nexus 4, at least not by me.

Kernel they are using is based on the msm kernel, either CAF or CM, while OmniROM uses AOSP one.

If you're happy with a secondary kernel, well, i'm glad it works for you, sorry that I can't use their kernel (number of commits to merge to include those specific changes are legions, too much work involved, with little support in case of failure).

Lte is working without me really doing anything for it (Android 7 modifications), but USB OTG and power modes tied to Marshmallow and now Nougat won't be integrated in Omni 7 for Nexus 4 (and I don't think any of the devices supported actually have kernel wise modification) for the very good reason it kills AOSP compatibility.