yashsingh1/xdaforums huggingface dataset:
[MeMO Pad 7 General] Treklof:
OTA-Update missing in Lollipop-settings?

Hey Guys,

after my Lollipop-update failed (bigtime) I did RMA my tabled to Asus.

The changed the mainboard (Sic!). I got it back with 201 and updated to Lollipop OTA. Worked fine this time.

I instandly did a factoryreset and a backup with tethered CWM.

(I noticed that now boot.img and recovery.img are in the backup. That wasn´t the case before when I was stuck on 201.)

I rooted and restored my Titanium-Backup.

Now I noticed that there is no Update-function left in the settings menu.

Anybody seen the same thing? Is it normal?

Is it the Asus-way of saying thank you, thats it. No more Updates. I know that Asus would be capable of that.

Regards.

---------- Post added at 02:03 PM ---------- Previous post was at 01:46 PM ----------

Forget it!

I froze dmclient and fotaservice.

Sorry.
[MeMO Pad 7 General] pecuecas:
Reboot problem

Hi, I had the same problem of constant freeze/reboot, what I did is deactivate all system and app notifications, thats is in setup - sounds & notifications .... thats seems to have worked in my tablet, at this time I have been a full day whitout any reboot, hope this work por you.
[MeMO Pad 7 General] Treklof:
No factory_reset-menu after RMA

I just found out that I can not access factory_reset-menu by pressing the middle key from recovery. And in droidboot my serial number is something like 123456789012345678.

I am on lollipop after RMA.

Is this normal?
[MeMO Pad 7 General] thebulletfromhell:
Got my tab back from warranty (exactly 5 business days). Motherboard replaced, Lollipop installed.

For anyone with the stuck on 201 problem, I'd suggest just bite the bullet and just RMA it. Repair report mentioned EMMC problem
[MeMO Pad 7 General] Treklof:
s/n Serial Number

Can you check what serial number you got in droidboot-menu after the motherboard change.

Mine was changed to a "dummy-number". Does that happen to everybody with new motherboard?

TNX.
[MeMO Pad 7 General] Kittie-hime:
Did a factory reset yesterday. The tablet worked well for a day but now the clock is running late again. I called Asus and they told me to RMA it. But since I've already RMAed the tablet twice before, I'm gonna ask the store for a refund on Friday. (it breaks my heart that I'll have to unroot it)
[MeMO Pad 7 General] thebulletfromhell:
Same generic number here.
[MeMO Pad 7 General] Mike9376:
Hello,

I'm new here and first of all I'd like to thank everyone for making this thread a must read for every Asus 176 C(X) user.

Here's my problem:

I have updated the Asus from KitKat to Lollipop and since then I am not able to use application specific passwords for my Google account any more. It just tells me to enter the password, which I have done numerous times.

When I try to set up an Gmail account it tells me explicitly to not use app specific passwords but the normal password including two way authorization.

Using my normal password works but I do not want to use it for security reasons.

Which passwords do you use in order to access your Google account?

Does it have anything to do with the Lollipop update?

Any suggestions?
[MeMO Pad 7 General] Alexadro:
Tell all that concerns soldering desoldering memory RAM?

All that is necessary to increase the RAM ?

Photo RAM memory ?
[MeMO Pad 7 General] thebulletfromhell:
[MENTION=5479482]jerbear294[/MENTION]

There is a ro.isn line in our prop. However, the zenphone method does not work, at least on my tab. Rebooting into fastboot does nothing.

Probably has to do with the lack of necessary file. They needed that 2.19 update for things to work, which was probably added to prepare for official bootloader unlcok
[MeMO Pad 7 General] sutekh137:
Recovery?

Hey all,

My tablet just started acting up this week, no apparent reason why.

At first it was freezing, hard, unable to even return to launcher/home. So, I wanted to clear cache, holding down Vol- and Power at the same time. No effect. Instead of getting to the recovery menu, the tablet just booted up in "Safe Mode", something I had never seen before.

However, After booting back into normal mode, things ran fine all yesterday -- no lockups. But now today, I had a spontaneous reboot and a game that has been working fine now won't start (Stella POP!). Shows the Rovio logo and then closes. I cleared cache for the app, no effect.

I also tried "adb reboot recovery" and it took me to the lying down android and "Error!" screen. Tried Vol+ and Power at the same time, no effect.

I am on Lollipop and did a full factory reset a few weeks ago when I got Lollipop all updated and the machine rooted again. So what is up now? Does recovery no longer work with the Vol/Power buttons? How can I wipe the cache? I am frankly getting tired of doing factory resets and having to restore all my apps and data. Help?

*** UPDATE *** I backed up the game data, reinstalled, and the game runs fine. But when I restored my data, it crashes immediately again. Restoring from a previous backup works, so something must have gotten corrupted with my data file. Nice job Rovio. Game uninstalled, will never try it again. I'd still like to know how to get booted into recovery, though!

Thanks,

sutekh137
[MeMO Pad 7 General] Kittie-hime:
I can't even access Fastboot with vol- and power. I always have to use ADB.
[MeMO Pad 7 General] sutekh137:
OK, so at least I'm not crazy.

How do you use adb to get into recovery? When I do "adb reboot recovery" I just get the dead android screen, and I don't know where to go from there...?

But I know I used to be able to access recovery using the buttons -- did that change with Lollipop? Now that I think about it, I don't think I ever tried to get into recovery in that way since getting Lollipop fully installed. Wait, no, that's not true. I factory reset Lollipop by using the recovery menu. So why the heck can I no longer access it? What am I doing wrong?

Thanks,

sutekh137
[MeMO Pad 7 General] Kittie-hime:
I do "adb reboot fastboot" then select recovery. When I get the dead android, I press vol+ and power. The recovery mode displays when I let go of the bottons.

From what I gathered from previous posts, being unable to access fastboot/recovery with the buttons seems to be linked with replaced motherboards? (Asus changed mine twice)

On another matter, I unrooted today and factory resetted. I decided to install some games and apps to see whether I would be getting the late clock problem. When I installed Facebook, my tablet acted up, turning black, displaying the launcher, then turning black and so forth for a while. After that, Facebook was installed but I didn't get the message from Google Play that it was. When I tried opening Google Play Kiosque, I got a message saying I could not access my account. And then I got a message from the Google app saying the connection wasn't working (though the Wi-Fi worked on other devices I own), and though I closed it, the app would pop up again and again. In the end I turned off my tablet and decided not to use it again until I go to the store tomorrow.

tldr: This tablet is damaging my sanity.
[MeMO Pad 7 General] sutekh137:
OK, thank you! I realize now that my "adb reboot recovery" WAS taking me to the right place, I just wasn't holding down VOL+ and POWER correctly (apparently). I finally got it to work and got cache wiped no problem.

But I am certain that VOL- and POWER used to get me to the fastboot menu, and there have been no changes to my tablet other than normal app updates. So, it is still very strange that VOL- and POWER now seem to put me into "Safe Mode" instead of displaying the fastboot menu.

As for your sanity, I can't help you there other than to say I hear you. Over the past nine months or so I have wondered many, many times whether or not the low price on this thing was worth it. And I have no idea how someone less techie would handle all the oddities in this in regards to upgrading to Lollipop, factory resets, etc.

Thanks,

sutekh137
[MeMO Pad 7 General] spookmeister101:
bad customer support

So I just called Asus customer support re lollipop woes. As expected they were totally not helpful. I told him about all the problems, (slow system clock, crashes, reboots, slow performance etc.) He talked to a higher up and came back saying "unfortunately, there isn't going to be a system update anytime soon, and was there anything else he could help with?" I said "well, a system update would be nice." He said "I'll forward your report, and hopefully there will be a update very soon." I said "you just said there wouldn't be an update any time soon.

He hung up, and I got the computer asking for me to do a satisfaction survey LOL it didn't go well. :mad:
[MeMO Pad 7 General] Kittie-hime:
They told me yesterday to RMA my tablet but from what they've told you, it seems there's hardly anything they would be able to do with it.
[MeMO Pad 7 General] daspex:
Bootloader will not changed while updating to LP

Hi dev´s and Co,

what is about flashing the LP bootloader with the intelflashing tool and writing the LP with tmpcwm or twrc recovery for people having stuck on bootloader and kernel .201

like me and many other´s?:confused:
[MeMO Pad 7 General] thebulletfromhell:
Intel flashing tool (DNX mode) only accepts 2 commands:

1. fastboot boot (insert droidboot image here). This didn't work on my device, it'd just freeze

2. fastboot flash ifwi (insert ifwi image here). We have no publicly available ifwi image, unlike the Zenphone.

So no.
[MeMO Pad 7 General] daspex:
UEFI

could somebody make a custom rom that directs the UEFI to another bootloader than fastboot?if i understand the post from the link that Mis012 gave to us right this has to be possible?

Never mind,i think i missunderstood parts of the post,but i think the key is the UEFI management or not?
[MeMO Pad 7 General] Mis012:
I think that you can install any os with UEFI and the os will use it's own bootloader - if you read the page I posted a link to, then you know there has to be an .efi file somewhere, which starts the droidboot, which acts as a bootloader and loads android system. Or the button combinations are connected with different .efi files, one for android, one for droidboot, and (maybe) one for recovery. This are two options, and without lollipop (so without UEFI) I cannot say which of this versions is correct (but the second makes more sense in context of something what I read, it sayed something like "droidboot is an app on top of UEFI, which provides access to fastboot commands") and in fact, the droidboot doesnt have options like launch android or launch recovery, only reboot (to recovery)
[MeMO Pad 7 General] social-design-concepts:
I'll chime in on this later but despite its name droidboot is not a bootloader it used to be back in the 4.0.4 days but now its just a provisioning os. The .efi in the esp partition is the bootloader.
[MeMO Pad 7 General] daspex:
so it would be possible someone modifies the LP rom to install a second bootloader to another efi partition wich the UEFI can use to start the LP rom?
[MeMO Pad 7 General] therealprof:
In theory it should be sufficient to create an USB stick with a GPT and EFI partition and connect that using an OTG adapter.
[MeMO Pad 7 General] Mis012:
social-design-concepts said that kitkat is even not driven by UEFI, so I don't know
[MeMO Pad 7 General] thebulletfromhell:
Just take the thing to warranty. It takes like literally 5 days, or even less if they just outright give you a replacement. Asus will release a new device before we get a sniff at bootloader unlock.
[MeMO Pad 7 General] groovychap:
I went to bed last night with my battery at 82%. I've got up this morning and it's now down to 50%.

How the hell could it drop 32% in eight hours?
[MeMO Pad 7 General] Ystrem:
Hello guys, I'm having problem to root my tablet. I can successfully reach the CWM, but when I want to install UPDATE-SuperSU-v2.46 from it. It writtes that can't mount SDcard. Anyone has the same problem ?

I followed this steps : http://www.htcmania.com/showthread.php?t=1029161

Thanks

EDIT: I successfully rooted the device with this http://www.asus.com/zentalk/tw/forum.php?mod=viewthread&tid=82819&highlight=root , then installed XposedFramework and XposedInstaller. :)
[MeMO Pad 7 General] dms76:
I've noticed since updating to lollipop that I have the random reboot issues, but only when not connected to wifi. I have clock issues, but clocksync has fixed those, Otherwise I have no problems with this tablet since lollipop. I was about to throw this tablet away due to slowness and non responsive, lollipop has saved it.
[MeMO Pad 7 General] Ystrem:
yep, I got it the same :D
[MeMO Pad 7 General] tonzky24:
bluetooth speaker

Anyone experienced lag when streaming music from the tablet to a bluetooth speaker? My speaker works fine on my phone but is sluggish on the tab, i already tried playing an mp3 directly from it but its still the same..
[MeMO Pad 7 General] daspex:
This is the content of the partition.tbl file from the lollipop.zip maybe someone can find out why the upgrade does not change the bootloader?

partition_table=gpt

create -z /dev/block/mmcblk0

create /dev/block/mmcblk0

boot -p /dev/block/mmcblk0

reload /dev/block/mmcblk0

add -b 40 -s 290816 -t data -u 80868086-8086-8086-8086-FFFFFFFFFFF0 -l reserved -T 0 -P 0 /dev/block/mmcblk0

add -b 290856 -s 2048 -t data -u 80868086-8086-8086-8086-000000000001 -l metadata -T 0 -P 0 /dev/block/mmcblk0

add -b 292904 -s 67584 -t efi -u C12A7328-F81F-11D2-BA4B-00A0C93EC93B -l ESP -T 0 -P 0 /dev/block/mmcblk0

add -b 360488 -s 32768 -t data -u 80868086-8086-8086-8086-000000000100 -l boot -T 3 -P 15 /dev/block/mmcblk0

add -b 393256 -s 32768 -t data -u 80868086-8086-8086-8086-000000000101 -l recovery -T 3 -P 14 /dev/block/mmcblk0

add -b 426024 -s 32768 -t data -u 80868086-8086-8086-8086-000000000102 -l fastboot -T 3 -P 13 /dev/block/mmcblk0

add -b 458792 -s 65536 -t data -u 80868086-8086-8086-8086-0000000000FF -l reserved_1 -T 0 -P 0 /dev/block/mmcblk0

add -b 524328 -s 65536 -t efi -u 80868086-8086-8086-8086-000000000002 -l panic -T 0 -P 0 /dev/block/mmcblk0

add -b 589864 -s 262144 -t data -u 80868086-8086-8086-8086-000000000003 -l factory -T 0 -P 0 /dev/block/mmcblk0

add -b 852008 -s 2048 -t data -u 80868086-8086-8086-8086-000000000004 -l misc -T 0 -P 0 /dev/block/mmcblk0

add -b 854056 -s 262144 -t data -u 80868086-8086-8086-8086-000000000005 -l config -T 0 -P 0 /dev/block/mmcblk0

add -b 1116200 -s 1325056 -t data -u 80868086-8086-8086-8086-000000000006 -l cache -T 0 -P 0 /dev/block/mmcblk0

add -b 2441256 -s 614400 -t data -u 80868086-8086-8086-8086-000000000007 -l APD -T 0 -P 0 /dev/block/mmcblk0

add -b 3055656 -s 65536 -t data -u 80868086-8086-8086-8086-000000000008 -l ADF -T 0 -P 0 /dev/block/mmcblk0

add -b 3121192 -s 3670016 -t data -u 80868086-8086-8086-8086-000000000009 -l system -T 0 -P 0 /dev/block/mmcblk0

add -b 6791208 -s $calc($lba_end-33) -t data -u 80868086-8086-8086-8086-00000000000A -l data -T 0 -P 0 /dev/block/mmcblk0

reload /dev/block/mmcblk0

---------- Post added at 11:13 PM ---------- Previous post was at 10:52 PM ----------

@thebulletfromhell

i don´t want to send it to warranty yet cause it seems to be a script error or something like that.Many of the guy´s who send it back to asus and get a new mainboard still have problems with there devices,so i don´t think it is a mainboard error.
[MeMO Pad 7 General] thebulletfromhell:
Its not a script error. The thing is ****ed. Most of the bug people are having are related to the lollipop upgrade, not because their mainboard got replaced.

The failed update bricked the bootloader, and nothing will write to it. Go back and read this thread, I've tried just about everything bar opening it up and using a hardware flasher. You can right now take a random file, rename it to boot.img and flash it through fastboot, and there would be no change. OTA doesn't work because recovery can't write anything to boot and droidboot, thus it fails at verifying boot files.
[MeMO Pad 7 General] thelegendy:
How to install Xposed on Lollipop? Could anyone help me?
[MeMO Pad 7 General] thebulletfromhell:
http://xdaforums.com/android/development/unofficial-xposed-lollipop-rom-t3126306
[MeMO Pad 7 General] Flaxe:
Hey all,

I had some issues upgrading to Lollipop so I decided to start over from .182 and work my way up. I've installed .182 without any issues, but I can't manage to install .191. I've tested installing it via the "normal" unbrick/flashing method aswell as trying to install it with temporary CWM (Trigger 4), but it won't install. I've downloaded the .zip file several times and from different mirrors and confirmed the MD5/SHA1 hash is the same, so the file is correct.

Anyone got any ideas what to do?

Edit: Just noticed it says my kernel is 3.2.23.201 #1 , but the ROM version itself is .182. :/

Edit2: The error message I get in CWM is:

Thanks.
[MeMO Pad 7 General] Mis012:
You have to use 201 cwm backup (I posted a link before), but as you can read above, you will most likely fail installing lollipop :(

I will try to try going to the shop and let them replqce the motherboard, not having UEFI when I could is really annoying :'(

The only way to flash lollipop droidboot is now to obtain .raw file for asus flash tool :( Could anyone please try to write/call to asus support and request it? Maybe some kind person which wikl not be afraid of his/her boss will upload it somewhere :) We just have to spam asus support until we will actually get respond from someone helpful. Maybe saying we have warranty and sending us a link to the file will cost them nothing will help?
[MeMO Pad 7 General] thebulletfromhell:
There is no Asus flash tool. All intel board uses their own personal flash tool, which is a very restricted version of fastboot (DNX), which accepts 2 commands: boot droidboot.img and flash ifwi. However, on a bricked device like that, boot droidboot.img does not work, and there is no publicly available ifwi. So unless you want to get a hardware (JTAG) flasher and flash the lollipop droidboot right onto the NAND, its either stay with Kitkat (which is much superior to Lollipop on this device), or take it to warranty.
[MeMO Pad 7 General] Flaxe:
Thanks! I managed to find the file and successfully restored it with CWM. Tablet is running .201 again :) Unsure if I should try updating to Lollipop again... :P

In case someone else is looking for it aswell, the post with .201 CWM Backup is here.
[MeMO Pad 7 General] AndrewRBX:
Wi-Fi Off, GPS off, zero apps in the multitasking menu...

last night battery was 86%... 8 hours later? 23%... I'm speechless.

This battery draining is a pain in the axx.

Apparently Google Play Services is causing this draining.

Never happened to me when I had KK.
[MeMO Pad 7 General] vampirefo:
Have you tried the xposed leak fix? Seems to be working for me on my nextbook Ares 8, it came with llollipop 5, which has a memory leak up to 5.1.

Xposed created a patch for it, have to use x86 version of xposed.
[MeMO Pad 7 General] AndrewRBX:
I'll give it a try, thank you! :good:
[MeMO Pad 7 General] slayeralive:
Me176c

I had trouble with clock sync and bluetooth audio on loolipop and i was trying to flash zip thru stock recovery and i got an error but both clock and bluetooth audio works now:)

I have attached log if someone is interested:)

It seams that recovery did some kind of fix :)
[MeMO Pad 7 General] Mis012:
... In case someone else is looking for it aswell, the post with .201 CWM Backup is here.

Yes, why don't credit the person who used my link and posted the direct link without giving credits to person who made the backup?

It's not that hard to translate from Russian to English and look at that Russian thread, look at the original post and finally find the link. Becouse someone else can now say thanks to person, who basicaly took the final link an posted it, so everyone will think he made the backup, or that he was the one who found it and posted it here. And not he profits on my post :'(
[MeMO Pad 7 General] vampirefo:
Sometimes posting another link is better, no need to go through Russian translation when a direct link can be posted.

As far as credit how many people even bother to credit me with the cwm recovery? Very few.
[MeMO Pad 7 General] fran1563:
I have a ME176CX, I upgraded the SO I got the message "it said 'Unable to detect power status' for me was weird but I keep going pressing the volume button it started but in the black screen with this message:

"FastBoot Starting...

FastBoot Starting...#1

FastBoot Starting...#2

FastBoot Starting...#3" I don't know what to do, It doesn't move from this screen.
[MeMO Pad 7 General] Mis012:
Maybe try to power off by holding the power button for so long, then try if you can get in droidboot, or if you can reboot normally.. But if you will get back there, download the lollipop firmware from asus site, unzip, get droidboot.img, connect tablet to pc, and with cmd, within folder with droidboot.img, run fastboot boot droidboot.img I haven't tried this becouse I am stuck on kitkat, but it should reboot in fastboot. Then use temp cwm to flash entire firmware. Hope this helps ;)

---------- Post added at 07:43 PM ---------- Previous post was at 07:36 PM ----------

I remeber your nick very well from the background image of the cwm recovery. Noone will ever remember the name of person who made the backup, and noone will ever remember my name (unless I will do something amazing in the future) I could be remembered like the one who managed to run windows on this device, but I am stuck on kitkat now, so no UEFI, no Windows.. :'(
[MeMO Pad 7 General] spookmeister101:
Can you use this cwm backup to downgrade from lollipop? I'm seriously regretting upgrading from kitkat.

When I was talking to Asus customer support, he said that I'd have to root my tablet to downgrade to kitkat and that would void my warranty. I'm wishing I'd told him I was willing just to find out how.
[MeMO Pad 7 General] fran1563:
Thanks for you quick answer, I was bring my tablet from the tecnician he said who I erased the boot's unid, then I need something to set up boot's unit and then will install the S.O. Nobody in my town can handle with this problem I walked a lot!
[MeMO Pad 7 General] Mis012:
Just try what I said ;)
[MeMO Pad 7 General] Alexadro:
People !!!

If you use with the HDD BOX USB (SATA - USB) and is connected to the output of the device run UEFI see it ( the drive ) ?

Around here (HDD - (SATA - USB) - tablet - UEFI

Apparently this is not in the UEFI driver and sadness trouble , I cry

---------- Post added at 07:27 PM ---------- Previous post was at 07:18 PM ----------

People !!!

How is it faring Windows

Is it possible or not? if you run Windows x32 :

install Grub or refind?
[MeMO Pad 7 General] Mis012:
I wold love ro have lollipop, becouse of the UEFI thing etc., but if you want kitkat, everyone will say you cannot get it. Even with root. In theory, you can go to UEFI and instlall intel x86 android, which is basicaly pure android for x86 UEFI devices, but if you will not find out how to install it on sdcard or new partition or so, you will never get asus's android back. And latest intel's android is 4.4.2 AFAIK
[MeMO Pad 7 General] therealprof:
Well, yes and no. The latest Android for Intel is obviously not 4.4.2 but whatever the latest version of AOSP is, what you're probably referring to is the Android x86 project whose aim it is to make it run on regular PCs; it's not a good idea to put that on a tablet anyway since it doesn't support much (most?) of that hardware.

UEFI has somewhat strict minimum requirements what needs to be supported by a compliant implementation which includes the way that UEFI finds its executables, so it should be very well possible to just keep the important ASUS stuff and simply use the main partition of the OS for the new implementation or resize it; then it should be possible to revert back to ASUS. Or alternatively one could put an alternate OS on sdcard (iff there's a UEFI driver available which might not be) or boot via USB -- which of course would be a PITA to do permanently.