yashsingh1/xdaforums huggingface dataset:
[MeMO Pad 7 General] Mis012:
Grub + verbose kernel support = easy debugging?

Hello everyone. I hope you are doing well. I have looked around for that verbose boot and it seems that

1. You need to allow support in kernel

2. add console=tty0 to cmdline

3. need to disable bootanimation?

4. may not work with other bootloaders? Grub has already so many things built in...

And, have you already tried compiling the ASUS kernel from source? It may be a good first step to see if this one works (and seems to have some features implemented but not enabled)
[MeMO Pad 7 General] seamo123:
*EDIT* Panic over, I figured it out. Sorry! :)

Oh boy... I have a problem here. My rooted Lollipop .33 is shot.

I tried to use a theming app in Xposed (I know, I know, but I thought restoring my nandroid backup via temp TWRP recovery would be a cinch if anything went wrong)

So, my pad won't boot properly - it stops at the 'Asus in search of excellence' logo and stays that way.

The BIG problem here is, the fastboot tethered recovery launcher won't recognise my pad - 'Device status - unknown' etc. So I effectively have no recovery to snap my pad out of this!

H...E...L...P

---------- Post added at 14:14 ---------- Previous post was at 13:53 ----------

Meant to ask you, is that zip ROM you posted on mediafire deodexed? I don't seem to see any of the usual 'odex' files cluttering up my folders.. ;)
[MeMO Pad 7 General] sutekh137:
seamo,

Glad you got things working. I'm afraid I have no clue as to your follow-up question, though. I did not remove any files, though -- the zip file was the straight download as far as I can recall (didn't even remember putting that up there, actually...)

Thanks,

sutekh137
[MeMO Pad 7 General] jerbear294:
Haven't seen you in this thread for a while (might just not remember), how have you been?
[MeMO Pad 7 General] social-design-concepts:
[MENTION=5479482]jerbear294[/MENTION]

android-ia just started pushing some brillo code some of the kf stuff :)

maybe we'll get some android-m love too.

Minnowboard is also in AOSP for brillo now too so some Baytrail code might trickle into AOSP too.
[MeMO Pad 7 General] sutekh137:
Jerbear,

Been fine, thanks for asking! Just been keeping up on the thread seeing all you amazing folks get closer to customizability. I suck and have nothing to offer on that front. *smile* So, I've just been lurking...

I recently froze more apps on my tablet (including the ZenUI service) and have been having much longer run-times in between Angry Birds 2 crashing the thing (it had gotten pretty dang bad). So, my tablet experience has been pretty good as of late.

Hope all is well with you (and everyone) in the new year, and thanks to everyone for all their work on this!

Thanks,

sutekh137
[MeMO Pad 7 General] TalhaGirgen9:
New Update. Yay!
[MeMO Pad 7 General] russy23:
whats it say, is this a battery drain fix
[MeMO Pad 7 General] TalhaGirgen9:
update is 20-30mb

Bios updated to same version again strange?, i noticed some SystemUI Changes and update some apps

also they improved general performance a bit i think?
[MeMO Pad 7 General] jerbear294:
I'm certainly not flashing it until I know something...

Is Secure Boot still disabled? If it is, hold off on the update until I get a Nandroid, as the Nandroid doesn't touch the UEFI.

Also, could someone link the OTA file? I'd like to analyze it.

When I get home I'll update my brother's tablet and make a Nandroid from it, just like last time.

In the meantime, I guess you could install it, but if Secure Boot is enabled it's game over, so just to be safe wait for the Nandroid.
[MeMO Pad 7 General] Mis012:
It's UEFI! It's NOT bios! You should read the link in my signature. It will open your eyes.

I think I will wait for custom roms anyways. If some kind person gets the update package, you can hex diff the uefi update.
[MeMO Pad 7 General] russy23:
Wait for a custom rom..well the tablet came out in 2014 and theres not one out yet, wishful thinking
[MeMO Pad 7 General] jerbear294:
That's because up until recently it was COMPLETELY IMPOSSIBLE to put a custom ROM on here.

[MENTION=7057426]Penguineh[/MENTION] and I are both working on getting AOSP to run, once that's ported everything else will fall into place.
[MeMO Pad 7 General] Ruben Craveiro:
i need the link.. i forgot to logcat (to get the url of ota) and it gave an error of some changed files on recovery (i dont know why...) , and then it reboit and i tried to search ahain and i couldnt and i dont want to format the tablet to just install the update
[MeMO Pad 7 General] TalhaGirgen9:
lol, I dont know so much about x86 soo, its my fault sorry :p
[MeMO Pad 7 General] seamo123:
I see there's a 29.67MB update to LP .36 available. Wonder what the deal with it is: i.e. would it still be rootable and have they secured the bootloader? Hmm.. I'm staying clear of this one for a while methinks.
[MeMO Pad 7 General] jerbear294:
I'll need a copy of the OTA to analyze it.
[MeMO Pad 7 General] HampTheToker:
This post deserves all the likes.

I've been lurking and paying attention to the progress you guys have made. Your work is totally appreciated, and I'm glad that I chose a device for my six year old that he can enjoy all (well, almost) the benefits of root. So glad no one ever tried to sell him on an iPad.

Anyway, you all do great work, and I just want to remind you that it isn't going unnoticed and to thank you for dedicating your time to this community.
[MeMO Pad 7 General] Ruwin:
Has anybody applied the 36 update? As I understand there is some battery drain fix, it's making me curious.
[MeMO Pad 7 General] bedman77:
I did apply it. I had to adb sideload the . 33 version and then it asked to update to . 36. Maybe it's a placebo effect but it seems snappier, same as it was with update . 33 in the beginning. I don't use xposed but root working just fine. Can't say anything about the battery since I've just update it an hour ago.
[MeMO Pad 7 General] seamo123:
Sounds promising! I'm waiting on the Xposed verdict re..36 myself, because if Xposed doesn't work then fuhgettaboutit.. ;)
[MeMO Pad 7 General] jerbear294:
I won't be able to give the all-clear until I get a copy of the OTA.

I'll check the ASUS website but knowing them it's not there yet.

EDIT: EVERYTHING's gone from the Download page again, except for the .17 kernel source... Fantastic.
[MeMO Pad 7 General] Mis012:
I have downloaded the .33 kernel source about 30 mins ago, If you wanted to look at it. It seems to have drivers and modules source also. You may use it for the aosp build. And it also has hid gadget mode so if you have two tablets (on lollipop) you may be able to browse uefi setup with only normal otg?
[MeMO Pad 7 General] jerbear294:
I've got the .33 kernel source, downloaded it a few days ago. I was experimenting with it for AOSP.
[MeMO Pad 7 General] social-design-concepts:
I had to grab the kernel source from here : https://www.asus.com/support/Download/28/6/0/23/3HzHuNmdcAgeMhJ1/32/

But a lot of projects seem to be overlaying the zenfone2 kernel source.

I've been playing with the AOSP x86 android wear source the last couple of days it seems to have the most complete commit history.
[MeMO Pad 7 General] Mis012:
Keep experimenting, it has to work once ;)

P.S someone wanted to know if you can load android from sdcard with no impact on current setup.

theoreticaly as you can edit both kernel and ramdisk, you should be able to redirect fhe mount of /system and /data to microsd. Then using either grub2 or fastboot boot (the second needs insecure bootloader) you can boot your own kernel+ramdisk which in turn will load system from microsd (and other things from emmc possibly, but lot of them should not be required)
[MeMO Pad 7 General] Droopy Dawg:
Hello All,

I just joined this forum. I own 5 of these tablets and before the battery drain standby issue they were pretty good for the money. Gamestop had them for 75 dollars, so I couldn't resist. I have been beating ASUS up about this issue and I was hoping that new update that came out a couple days ago would resolve the issue. But sadly, it did not. The last email I received from the ASUS tech stated that he was going to send the problem to their engineers.

I appreciate all the the Dev community does for our Android devices. Without you all our devices would be obsolete in a year.
[MeMO Pad 7 General] Ruben Craveiro:
you went to wrong model support page... go to the me176c not the me176cx
[MeMO Pad 7 General] jerbear294:
Huh.

Last I checked they had the same things.

Well now I know.
[MeMO Pad 7 General] social-design-concepts:
[MENTION=5479482]jerbear294[/MENTION]

x86_64-linux-android-ld: error: drivers/external_drivers/built-in.o: multiple definition of 'intel_scu_ipc_update_register'
x86_64-linux-android-ld: drivers/platform/built-in.o: previous definition here
x86_64-linux-android-ld: error: drivers/external_drivers/built-in.o: multiple definition of 'intel_scu_ipc_ioread8'
x86_64-linux-android-ld: drivers/platform/built-in.o: previous definition here
x86_64-linux-android-ld: error: drivers/external_drivers/built-in.o: multiple definition of 'intel_scu_ipc_iowrite8'
x86_64-linux-android-ld: drivers/platform/built-in.o: previous definition here
x86_64-linux-android-ld: error: drivers/external_drivers/built-in.o: multiple definition of 'intel_scu_ipc_readv'
x86_64-linux-android-ld: drivers/platform/built-in.o: previous definition here
x86_64-linux-android-ld: error: drivers/external_drivers/built-in.o: multiple definition of 'intel_scu_ipc_writev'
x86_64-linux-android-ld: drivers/platform/built-in.o: previous definition here

err . . . annoying
[MeMO Pad 7 General] jerbear294:
That looks like fun[emoji14]
[MeMO Pad 7 General] social-design-concepts:
Its not lol.

Same error regardless of the kernel base I use, well haven't build against your devices kernel yet but I suspect the same error will occur,

guess I need to build against the kernel source I pulled the kernel config another user generated for my tab from and start there.
[MeMO Pad 7 General] jerbear294:
You're getting farther than I am. I haven't gotten one compilation to succeed. It works fine for a few hours, then Java complains about memory.

Either it's because I'm using Arch or I'm using too many make threads. I'll try a j2 build tomorrow.
[MeMO Pad 7 General] social-design-concepts:
my cm-12.1 source builds fine, it's when trying to build the kernel i'm getting the error, i might try building a couple other byt kernel configs, though ones that are not the generic byt_x86_64 are few and far between, with all the kernel sources having the same build error, i'm hoping to stick to the aosp android-wear x86 source since it's commit history is complete.

if your wanting to work on building the kernel you could always use make -j$(nproc) bootimage or make -j$(nproc) recoveryimage so you don't have to wait for a full android build.
[MeMO Pad 7 General] Droopy100:
All,

I received a reply from ASUS tech support this evening. They appear to be listening. Although the new update did not resolve the issue on any of my tablets, the battery drain during sleep is slightly better. Also, the new firmware gave me a notification that google+is draining the battery, which I have never seen before. Until there is a custom ROM, maybe if we all open a case with ASUS, they will fix this issue.

Dear Droopy100,

Thank you for contacting ASUS Customer Service.

Sorry for waiting.

I just got the engineers reply.

The new fw V12.10.1.36 (WW) is released in 3 Feburary. Please update the fw to the latest to see whether the problem still remains.

Thanks.
[MeMO Pad 7 General] sutekh137:
jerbear,

You still need the OTA dlpkgfile? I have it here:

https://www.mediafire.com/?716nfcfn0uiqe57

File is called "dlpkgfile_OTA_36". As usual it failed to properly install, not sure when the full WW firmware will be out (or is it already out somewhere that I just can't find?)

Thanks for all your work on this, as usual...

Thanks,

sutekh137
[MeMO Pad 7 General] jerbear294:
Analyzing it now, thanks.

EDIT: From my quick analysis- seems like quite a bit has changed, but nothing that should break Xposed- and if Xposed is broken, it'll be easy enough to Nandroid back to .33.
[MeMO Pad 7 General] seamo123:
Tried to OTA .36 update a minute ago. Failed. I've never been able to update OTA actually, is this purely because my device is rooted? I was wondering, where does the device store the OTA update before it applies it? Maybe I could just download the update OTA, then when prompted to install I could just hit the home button, open Root Explorer and get the update zip?

Is that possible?

Aside from that, do ASUS have that update posted yet? I've tried to find their K013 firmware but their site is kind of labyrinthine.... :)
[MeMO Pad 7 General] :
whats improved in the new update?
[MeMO Pad 7 General] jerbear294:
Yep, solely because the device is rooted.

If any modifications to /system are detected the installer stops. You'll need to wait for a Nandroid (I'll have one soon)
[MeMO Pad 7 General] seamo123:
The update isn't applicable by flashing the zip with TWRP, no? I was one of the ones that found it impossible to root with your previous .33 nandroid you see, not until someone kindly gave me a link for an alternative version. I'm a little wary of it now. ;)
[MeMO Pad 7 General] Ruben Craveiro:
just make some basic updater script modifications and flash the zip... thays what i did (deleted fingerlrint stuff and first or 2nd line i dont remember) and delete one of the mount line of system, it flashed well on twrp
[MeMO Pad 7 General] seamo123:
Where did you get the zip and what changes did you make to it?
[MeMO Pad 7 General] Lautaro Mondaca:
Link to download full update zip to flash

http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/UL-K013-WW-12.10.1.36-user.zip
[MeMO Pad 7 General] sutekh137:
Cool, how did you find that? I could still only find .33 when I went searching...

I assume we need to change updater-script to remove that weird K013 check from the top, then re-zip? I might just skip this update since it appears to be very incremental, and things have been running OK on my tablet since I froze a bunch more stuff...

Thanks,

sutekh137
[MeMO Pad 7 General] tonzky24:
can i use this to update mine? im rooted on .17 i haven't tried ota yet, if so.. how can i update mine using this zip file?
[MeMO Pad 7 General] seamo123:
Hi! Speaking of that weird K013 check, how do you change the updater script? I'm looking to keep upgrading as quickly as possible, because this Lollipop thing so far is a real POS. Well it is on my pad anyway. ;)
[MeMO Pad 7 General] sutekh137:
Basically, you need to unzip the whole file somewhere and then dive down in the folders and find a file called "updater-script". Edit that file with an editor that won't screw up line-feed characters. Then you can zip that whole folder back up again, maintaining the directory structure, and you've got a zip file you can flash.

As far as how to edit the updater-script, let's see if I can find a previous post... I think updater-script is in folder:

META-INF/com/google/android

and you have to edit it there, in place, removing the first line (I think that is all that needs doing...) What the heck, I am going to see if I can't download it, fix it, update, and then place the fixed zip file somewhere for download...

Thanks,

sutekh137
[MeMO Pad 7 General] Lautaro Mondaca:
I just edit the download link for .33 to .36 :P
[MeMO Pad 7 General] sutekh137:
Damn that's smooth... Good to know!

I am in the process of editing the updater-script file, re-zipping, and trying to flash (screwed up the re-zip, trying again). When it works, I'll put the update file somewhere so people can download it and avoid that K013_1 error (if they get that).

Thanks,

sutekh137
[MeMO Pad 7 General] tonzky24:
up
[MeMO Pad 7 General] russy23:
this means i will need to root again to debloat, sigh
[MeMO Pad 7 General] sutekh137:
OK, I am having a heck of a time trying to flash the zip file... I am using the normal method of:

Copy the zip file to /data and name it "update.zip"

Copy the correct "command" file to /cache/recovery

From my Windows command line, with the tablet connected via USB and recognized by "adb devices", run "adb reboot recovery"

But even using the original update file for .36 I get an "Error!" android, NOT the message about K013_1 being the wrong device. So, there is no need for me to try to change updater-script because I can't even seem to get the original zip file to be properly recognized.

Can I just flash the zip via the Intel tethered boot thingamabob (where we use "T4" as the trigger)? I am not sure if I can flash full firmware that way?

So, sorry I suck, but I can't seem to get to the point of creating a zip file for folks to use (at least, I can't trust it if I can't flash it myself...)

Thanks,

sutekh137
[MeMO Pad 7 General] jerbear294:
I keep forgetting to get a Nandroid from my brother's tablet. I really need to do that.
[MeMO Pad 7 General] sutekh137:
I don't know anything about nandroid stuff. Would that help with this?

Any idea why I can't get updates to work now? I updated .33 with this method and it worked fine.

Can I flash the zip via the Intel bridge thingy, or does that not work for full firmware updates?

Thanks,

sutekh137
[MeMO Pad 7 General] smsalom:
i managed to update .36 fw using the tethered recovery
[MeMO Pad 7 General] Dengis:
Is it safe to upgrade to this new version without losing the ability to install a custom ROM?
[MeMO Pad 7 General] jerbear294:
Basically a Nandroid is a system backup- if I backup the latest update from my brother's tablet via temp TWRP, you'll be able to "install" the update by restoring that backup. It'll come unrooted as it's from my brother's stock tablet though.

Another option is to take the .33 Nandroid I made, restore that, then update. Since it's a completely unmodified /system partition the update will flash fine.
[MeMO Pad 7 General] smsalom:
i think it is, i guess they didn't touch anything related to that, also tethered recovery still works!
[MeMO Pad 7 General] russy23:
updated to .36 and now tablet screwed, boots up and when unlocked a white screen flickering away, reboot didnt help,,bollox
[MeMO Pad 7 General] sutekh137:
Thanks for this, I gave it a go and am up to .36 now. Just need to see if i can get rooted again and then I will upload the zip file with the corrected updater-script...

Thanks,

sutekh137

---------- Post added at 02:13 PM ---------- Previous post was at 02:12 PM ----------

jerbear,

Thanks for the explanation... I have been upgrading these last few times WITHOUT doing a factory reset, and I'd like to keep it that way. Sounds like the vanilla nandroid method would be a bit too clean-slate for me.

Thanks,

sutekh137
[MeMO Pad 7 General] jerbear294:
Vanilla Nandroid doesn't wipe /data, it only contains the system image.
[MeMO Pad 7 General] Mis012:
You may be right, but it seems you know nothing about it so please don't guess. Tethered recovery has nothing to do with UEFI. And it may have touch something related becouse the UEFI update is present.

Please find a time to read the link in my signature. It's not by me, but so nice for begginers. And this is really not-hurting way to stop thinking bad way.

P.S is there anything I could do? All my little projects are taking dead ends :( Although I may share my progress on booting live linux from emmc (frugal) with no powered otg things - I actually got asked for password on command line (but it should be graphical, it showed some error before jumping to login shell. Making it working without powered otg seems to need debugging the problem with it, so I can read logs and try to run xorg manualy.
[MeMO Pad 7 General] sistah:
Hey, I tried to upgrade to .36 via OTA but it showed the Dead Droid with Error!

I tried to install it with tethered but I still get the error, what the hell happened?

I guess my recovery is f@#ed up?

What can I do?
[MeMO Pad 7 General] sutekh137:
When trying tethered, I assume you got the "K013_1" error? That's slightly different from the "Error!" android and relates to the updated-script in the zip file having a check for the unit's code (and inexplicably doing it wrong).

Let me check my upload... four more minutes before a zip file with that issue fixed is up on MediaFire...

OK, it's up: https://www.mediafire.com/?ny29yhv5tzfea58

Download that zip and try installing it via tethered recovery. It worked for me, and I was able to restore root later as well...

Thanks,

sutekh137

---------- Post added at 03:06 PM ---------- Previous post was at 03:05 PM ----------

Ah, cool...thanks for the info!

Thanks

sutekh137
[MeMO Pad 7 General] sistah:
It's not the K013_1 error.

The moment I enter the recovery after choosing T1-4 I got the dead droid with the plain "Error!".

I can vol Up to get the recovery but its the android one not the cwm.

Till the last update (.33) I managed to fix any issues with the help of related posts right here in this thread but this time I can't even boot to recovery.

Should I try the zip you provided nevertheless?
[MeMO Pad 7 General] sutekh137:
I am not sure how you an "try" any zip file if tethered recovery is not getting you to the recovery menu...? It sounds like things are not at the recovery menu yet when you see the "Error!" dead android. I am not sure why that would be happening.

Do you still have root? Is there still an "update.zip" file in your /data folder (mine stayed there even when I didn't want it to). Perhaps that is still stuck in its craw?

Thanks,

sutekh137
[MeMO Pad 7 General] seamo123:
Anyone try the new .36 with Xposed? Dare I ask what happened? :p
[MeMO Pad 7 General] jerbear294:
Well that's not good- however, assuming the tethered recovery exploit is fixed it's still entirely possible to install the insecure bootloader and install permanent TWRP.

[MENTION=5248213]sutekh137[/MENTION] can you still enter TWRP?

Haven't tried it (still on .33) but my quick analysis indicates it should still work.
[MeMO Pad 7 General] seamo123:
I might give it a whirl then and see what happens, any update to Lollipop has got to be an improvement over what I'm currently running.

Presumably there's nothing in the .36 update that'd make restoring a .33 nandroid backup problematic?
[MeMO Pad 7 General] jerbear294:
Unless it blocks TWRP, nothing.
[MeMO Pad 7 General] sutekh137:
jerbear,

I am not the one with an issue, I'm fine. sistah is having the issue. It would appear he/she is still getting the error icon when using tethered recovery. That's why I asked if he/she still had an update.zip hanging out. That might cause problems? This shows how little I know compared to the other kung fu masters here....

Thanks,

sutekh137
[MeMO Pad 7 General] jerbear294:
Yeah, I know, but you said you were already updated so I was trying to figure out whether temp TWRP still works.
[MeMO Pad 7 General] sutekh137:
That's what I was trying to figure out, too. If the android error comes up immediately, then it's not in recovery (TWRP), is it?

(Maybe now you see why I lurk instead of participate. *smile*)

Thanks,

sutekh137