yashsingh1/xdaforums huggingface dataset:
[Huawei Ascend P7] PEYMANSTAR:
problem

I have a serious problem, I installed the B133 and now the update and has left me a window constantly open

"Sorry, Unfortunaly the process com.android.phone has stopped." and do not let me do anything

I already restored but I get the fine not to the cust, any ideas?
[Huawei Ascend P7] Simona Simmy:
Just go to settings and erase whole mobile..

Backup before..
[Huawei Ascend P7] eldivino69:
installed everything ok. The procedure of Root no longer works with RootGenius ...

Inviato dal mio iPad utilizzando Tapatalk
[Huawei Ascend P7] patch12:
i have this problem too.after install rom emui 3.0, Unfortunaly the process com.android.phone has stopped
[Huawei Ascend P7] eldivino69:
Root

I solved. B133SP01 install and maintain Root with RootGenius and last upgrade to 3.0 Emiu in Local.

When you restart the root remains active. :D
[Huawei Ascend P7] goby92:
I guess it still the beta version, right?
[Huawei Ascend P7] habbaz:
1. Downgrade from B136 to B133SP01

2. Setup B602

And All right
[Huawei Ascend P7] osnapitzpacho:
Yes, I totally forgot to mention that it's BETA. :)
[Huawei Ascend P7] Radule1990:
Me to,can somebody help us?
[Huawei Ascend P7] Falcon1:
Yes, I can help you

The same thing happened to me when I tried to install 3.0 from B133 and the problem is when you use 3 buttons or Hisuite (Do not update with these methods), what you have to do is to put the update.zip (3.0 emui version) in the sdcard (remember place it in the carpet /doad/ you must create it), and then you must use the cellphone in the menu update/ choose local update and allow the device reboot itself and start updating properly emui 3.0.

I recommend you go back to emui 2.3 B133 first and do these things before doing any change.
[Huawei Ascend P7] ajoynk:
Huawei Ascend P7 L-10 EMUI 3.0 Beta

I've installed the beta version on my P7-L10. The interface looks cool, awesome. But it doesn't have many features in the 2.3 official version. For example, dlna, screen sharing on other smart devices, backup, hide folders and files, Select app to play Gallery files. (images & videos) Also, the battery consumption is high compared to the previous EMUI. When can we expect the official update with all bugs fixed?
[Huawei Ascend P7] Sekypapa:
update flashing

Good evening guys!

I want to update to EMUI 3.0, but I have TWRP. Can I flash with TWRP or fastboot the update.zip?
[Huawei Ascend P7] Falcon1:
Only stock recovery

Flash it with stock recovery, TWRP or CWM are used for updating Custom Roms only and TWRP only works in 2.3 roms, not in 3.0 roms. All the information you need to ugrade can be found in this thread: http://xdaforums.com/ascend-p7/general/ascend-p7-b602-emui-3-0-international-t2971697 :good:
[Huawei Ascend P7] BigDre:
Hello all. today i started to search about EMUI 3.0 and found this forum. :) and now i have question about that file with can be downloaded in official Huawei site? in EMUI section. :)
[Huawei Ascend P7] Falcon1:
It is the kernel

That files that you mention is the KERNEL for the P-7, it is not any FACTORY ROM, so I do not recommend you downloading it unless you are a Developer who wants to design your own Rom. :D
[MeMO Pad 7 General] slayeralive:
Enter recovery and sideload CN ROM

http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ME176C-CN-3_2_23_182.zip

To return to WW rom its a litle complicated becouse when you try to sideloade ww version it gives error for not having inough space. So you need to give command to recovery to instal zip from location you want.

1. root with rootzenfone.apk

http://23pin.logdown.com/posts/230216-root-rootzenfone-14r

2. turn on usb debuging

3. download ww rom and rename it update.zip

http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ME176C-WW-3_2_23_182.zip

4. download es or some other file menager that has root access.

5. go to / (root) and manualy copy update.zip to /data folder

6. Download https://drive.google.com/file/d/0B6...drivesdk&resourcekey=0-W0btfSuQS9kq5iNNsCuWgQ and copy command file to cache/recovery folder

6. open ADB and type line by line:

adb remount

adb shell

su

echo 'boot-recovery ' > /cache/recovery/command

echo '--update_package=/data/update.zip' >> /cache/recovery/command

echo '--wipe_cache' >> /cache/recovery/command

echo 'reboot' >> /cache/recovery/command

reboot recovery

after this reboot to recovery and automaticly instal ww rom :)
[MeMO Pad 7 General] sutekh137:
This is fantastic, and smart move making a new thread...

Thanks,

sutekh137
[MeMO Pad 7 General] pjim:
And if you're not bricked, but can't update from the old software version. Copy and paste the commands in terminal emulator to force the update. Worked out great. Thanks for the tip.
[MeMO Pad 7 General] bravesoul:
I'm having a lil problem here. Could you elaborate a little more, like in /root. <-- What does this mean? Do i write root or am I to go to root of the tablet's memory? And should I use adb on my PC connecting by usb cable to the tablet? I'm having a little problem understanding some of the steps.

(Remember, it's my sex life that it's in danger here)! :P
[MeMO Pad 7 General] jerbear294:
I would assume root of the device itself as the next step is to put update.zip in /data

(Get me in on the fun. I helped. :P)
[MeMO Pad 7 General] bravesoul:
I tried terminal emulator to write adb remount, but just after I wrote it, it gives me an error.

I've put the the update.zip in data folder. but there's like two data folders in my tablet's memory root. Do I put it after mnt or before (I,m using root browser v2.3)? Like in the real root of everything? Another question. Must I use the zip inside another zip of the asus ww rom, or just the unzipped zip file. (LOL, confusing, i know).

(I dunno JerBear, they're very peculiar about what/who they blow)!! :D
[MeMO Pad 7 General] jerbear294:
They should be symlinked to the same thing. Let me check...

Well. I only have the data folder that's in the root. Peculiar.

As for the zip file question, go for trial and error. Worst case scenario recovery rejects it.

(We'll work around it :P)
[MeMO Pad 7 General] bravesoul:
This is what I get in terminal emulator:
[MeMO Pad 7 General] slayeralive:
Me176c

You need that command only when you are using ADB over PC
[MeMO Pad 7 General] bravesoul:
Thanks, but I have other issues.

What zip file should I use? The original we download from ASUS or the zip file inside the original.

JerBear told me to try one or another, but he doesn't know I'm in a place where Internet speed is like 50 Kbps... Which means it takes about two hours to download the original file.

However,(and this will sound strange), if anyone can give me the original names of both the original .182 zip file and the one inside the original, I think I can use a previously (and renamed) downloaded .182 ROM.
[MeMO Pad 7 General] slayeralive:
Me176c

Use zip inside original.
[MeMO Pad 7 General] bravesoul:
So to be clear. I'll use ES File Manager to rename the file (update.zip) and copyit into Root->Data->Turn off the tablet and on again->enter into recovery->in PC I'll use adb->type adb remount and other commands->The tablet will reboot and update into the WW.182 ROM.

Right?
[MeMO Pad 7 General] slayeralive:
Me176c

No man can you read? Do not turn of. Connect to pc and use adb or use terminal. If you are using terminal skip adb commands and start at "su" command. After typing last command it will automaticly reboot to recovery and start instalation than just wait...
[MeMO Pad 7 General] bravesoul:
Ok, ok. Don't get your intelligence in a twist.

Thanks for helping me with my absurd noobiness. :good:
[MeMO Pad 7 General] jerbear294:
Have fun with your "reward" :D
[MeMO Pad 7 General] bravesoul:
Not yet I'm afraid. I've tried via terminal emulator and indeed it goes to recovery, but afterwards, it just reboots into the CN version untouched.

(And JerBear, i'm kidding about the chicks...They aren't 3. It's only one). ;)
[MeMO Pad 7 General] slayeralive:
Try again you did somethin wrong
[MeMO Pad 7 General] slayeralive:
Folow the steps download->extract->rename to update.zip->copy to /data folder->type in terminal
[MeMO Pad 7 General] slayeralive:
If you missd or typed wrong one character in terminal it wont work. Try again.
[MeMO Pad 7 General] pjim:
From the top, you must be rooted and you must know what that is.

I used the file from inside the download. I believe it has user in the name.

Rename this file to be update.zip.

Place update.zip into the data folder in the root directory, ie. root/data/update.zip.

Back out of that when it's finished and find the original post with the instructions, touch it and touch the message symbol like you are going to reply.

Copy all of the commands from after su, to the end.

Open terminal emulator, Type su and give root permission at the prompt, touch and paste, you should see what you copied, if you don't, do it again. If you do, touch enter and the process will begin.

Do not do anything until the device reboots COMPLETELY. It will go through several reboots, just wait.

Viola, you will be updated.
[MeMO Pad 7 General] cambridge79:
hi have a problem my asus 176cx bricked. I was using this tablet, one day it simply went black ( battery was charged ) and i couldn't start it anymore. i never done anything strange with it, never rooted, always updated with official updates, very few apps installed.

At its current status, if i restart it it just flashes blackscreen ( as when the battery is dead ) doesn't even load asus logo.

When i charge it it doesnt load the battery logo. i've tried to open disconnect and reconnect the battery, nothings happens but the battery doesn't look damaged.

if i press vol+ vol- power it goes into "fastboot starting... fastboot starting #1 #2 #3" and gets stuck there forever, this is the only sign i get from it to show something is still alive.

i followed post 163 advice , installed adb 1.4.3. from here

https://xdaforums.com/showthread.php?p=48915118#post48915118

downloaded the 2 file and copied in the folder.

i connect my tablet to pc. nothing happens.

i connect my tablet to pc when stuck on "fastboot starting" screen and is recognized as generic android device.

i've updated drivers as suggested selecting ADB drivers, now is recognized as "android device/android adb interface"

i go to adb folder in cmd, launch the two commands as described by post 163 and i get this screen:

https://i.imgur.com/iUXZcf2.jpg

when second command is over i hear a sound from the pc ( win10 64 ) as if the device gets disconnected.

nothing else happens, if i restart the tablet it still flashes on the black screen.

if i restart it with vol+/vol-/pwr still remains stuck on fastboot starting screen as it was before.

if i write fastboot reboot when is connected nothing happens.

what am i doing wrong? is my tablet gone forever? I don't care about apps and datas on it, don't care about android version, i would just want it to restart, it wasn't the best tablet but to read books and use it on the toilet was still worth it, would love to have it back working.
[MeMO Pad 7 General] Ruben Craveiro:
download .36 rom, inside the zip you should have another zip called ESP, unpack it and grab the file efilinux.efi and put it on adb folder(also add the droidboot.img to the folder), go to the fastboit starting screen, do fastboot flash osloader efilinux.efi and then fastboot boot droidboot.img it should boot to bootloader, from there i think you can boot the twrp recovery(if you dont have the permanent twrp, use temporary recovery session) and reinstall stock rom
[MeMO Pad 7 General] cambridge79:
thank you for the quick reply

are the two files you're mentioning the files mentioned and provided in post 163? because if they are it looks exactly what i've described i've done and it did nothng.

by the way i tried it anyway: for the rom, i've donwloaded the .36 file from this page

https://www.asus.com/Tablets/ASUS_MeMO_Pad_7_ME176C/HelpDesk_Download/

i've found ESP.IMG inside, i've managed to open it with 7-zip ( dont know why winrar and winzip don't let me do it ) and in fact there was the file suggested. I've copied both files in adb folder.

Started cmd as administrator, done again the procedure as you suggested ( connecting the tablet to the pc when stuck on fastboot...1 2 3 screen, wich is the only way that let the pc feel the tablet is connected ).

once again when launching the fastboot boot droidboot.img it tells me the procedure is done, i hear the sound of the usb disconnecting, but nothing happens, the tablet won't reboot and it remain stuck on that screen.

If i shut it down and relaunch that screen it keeps being stuck. If is of any help i can record me doing the whole procedure and upload it on youtube just to show you what exactly happens and to see if i'm doing something wrong.

by the way, the fastboot seem to recognize the device when connecting it, but i've seen on the asus support page there's also a package named "ADB DRIVERS". is it possible that i need them to make the tablet speak with the pc the proper way? In case the answer is yes, how do i install them? if i go through device manager, update drivers, he won't let me use them. If i select install on "android_winusb" it says "install error: the ash for the file is not present in the specified catalog file"

i have a feeling the tablet might be just broken. In fact i was doing nothing but using it normally and he just went to black on its own, probably some hardware just went kaput. With the tablet in this condition, if i connect it to the power should i see at least the battery icon telling me it is charging? because that doesn't happen. I've read on another forum that if you don't even see battery charging firmware may be too damaged to be rescued.

But still the battery seems connected and charged otherwise i think it won't even turn up and remain stuck on "fastboot starting...." page forever.

also i've tried to disconnect the battery and reconnect it a couple of time, just in case it went lose or something, hadn't noticed any difference.

should i check the voltage of the battery with a tester or try to temporarly connect a phone battery to + / - to see if it starts just to exclude is a power thing or it helps nothing?

Funny thing is i had bought back in the days an asus memopad8 too and not only asus completely forgot about that tablet ( not a single update was released ) but that too gave me hardware problems after a year but luckly with that i got my money back. I've bought asus products since forever and i have never had a problem but with the tablets i've been completely unlucky, never an asus tablet ever again for me ( these two were a bit sloppy even when still working to be honest ).
[MeMO Pad 7 General] SJMarty:
OK, I've got a pretty good mess here that I'm hoping that someone can help.

I just got a brand new ME176CX to replace an old one that I used for home automation. I had forgotten about all of these steps needed to get the thing to Lollipop. So I took the first OTA that was offered. That took the thing from .182 to .191. Then the next OTA failed and I then recalled the thread above.

At this point, I started to go though the steps to take it from .191 to .198 (which worked). At this point I was stuck...it would not take the .199 update (dead Android). It would also not take .210 nor the Lollipop update. It also would not take the WW .182.

So I found this thread and decided I would flash the Chinese .182 and then start over. Well, it took the Chinese .182 but now it won't take the WW .182. I can still boot to temp TWRP but when I select the ROM and and swipe to flash, it immediately throws up "Failed" with no details in the progress window other than "Error flashing zip."

Help!
[MeMO Pad 7 General] slayeralive:
Hi, i wrote this method a long time ago before TWRP was even available for this tablet. If you are stuck on Chinese rom you will have to follow steps on first page and use asus original recovery to flash WW rom and not TWRP. I was inactive on development for this tablet for a while, i hope some one from community who is more up to date will jump in and help you. Good Luck
[MeMO Pad 7 General] SJMarty:
Thanks for the information. I was actually able to figure out what was going on.

Turns out that the tablet didn't like the fact that the Micro SD card that I copied the updates from was formatted exFAT. Once I reformatted the card as FAT32, everything flashed fine.

Hopefully this gets someone else out of a jam some day.

:D
[MeMO Pad 7 General] jerbear294:
For future reference, if you would like exFAT support in the future, there is a LineageOS build that has support for it.

https://xdaforums.com/memo-pad-7/orig-development/rom-unofficial-lineageos-14-1-asus-memo-t3633341/
[MeMO Pad 7 General] jerbear294:
I knew that. I was playing along the whole time :P
[MeMO Pad 7 General] pjim:
Besides, you have split them up 3 ways. If there aren't 3, well.....
[MeMO Pad 7 General] bravesoul:
I know dude. ;)

You wish! :laugh:

About the steps. Via terminal it doesn't work. Tried it once again and still no joy.

Here are the screenshots, and JerBear. There are two data folders, only one is Root->Data and the other is (I believe) Root->Data->Data.

Just to be on the safe side, I copied both 900+ MB files to both data folders: :cool:

Btw. That upload site is very "Forum photo friendly", so, spread the word.
[MeMO Pad 7 General] pjim:
Try it after the su command. Type su, then enter, it should ask for root permission, then paste everything after that. It works, I wouldn't have said that if it didn't. My mistake. You need terminal to get root first. I will edit the instructions for others.
[MeMO Pad 7 General] bravesoul:
Ok, I've run it thru a compiler (or my friend did for that matter), and apparently there are some errors.

In "echo 'boot-recovery ' > /cache/recovery/command" it should be "echo 'boot-recovery' >> /cache/recovery/command".

Sintax error.

I don't know if that's even the problem. but I have typed once again all of it, line by line, and there are no mistakes. But this time I've used the ">>" and it started to update, but then it reboot and again it went to the CN version. Meaning... what I had before using the terminal. I've checked if I some how had the wrong version, but the CN version is 600+ MB and the WW is 900+ MB, so, there's no error there too. I'm starting to believe that God doesn't like me very much...

(Probably because of all the girl jokes). ;)
[MeMO Pad 7 General] pjim:
I used the ww and just copied the commands, there are no syntax errors or that wouldn't work. I'll bet your file is bad. There has to be a simple error, this is a really simple task, you shouldn't be having this much trouble. And these same commands work from a pc and adb, go that way maybe, I know you will get it
[MeMO Pad 7 General] bravesoul:
I don't know what else to do.

I just tried with the CN.182 file and it also didn't work out.

And that one I'm sure

it is not

corrupted.

I use Rom Toolbox Pro v6.0.6.1 and in it there's the root browser and terminal emulator.

Maybe I should try some other terminal...

Any ideas about that?

Btw. I've made a script with those commands using a scripter on rom toolbox pro.
[MeMO Pad 7 General] $nowblind:
I had the same problem, it started to update, errormessage and then reboot. I changed the file permissions on the update.zip file to rwxrwxrwx, typed su in terminal emulator and pasted the rest, hit enter the update started and finished OK. Downgraded from WW 191 to WW 161.
[MeMO Pad 7 General] bravesoul:
And how does one changes the file permissions?

Can you write the whole commands and just copy and paste all rest from the first post into the terminal emulator?

Write them here please.
[MeMO Pad 7 General] slayeralive:
Easyest way download root explorer long hold on file and select permisions and check all boxes.
[MeMO Pad 7 General] slayeralive:
OR TRY COMMAND

set_perm(0, 0, 0755, "/data/update.zip");
[MeMO Pad 7 General] $nowblind:
In Terninal IDE app I typed su and hit enter, copied and paste the following and hit enter.

echo 'boot-recovery' > /cache/recovery/command

echo '--update_package=/data/update.zip' >> /cache/recovery/command

echo '--wipe_cache' >> /cache/recovery/command

echo 'reboot' >> /cache/recovery/command

reboot recovery
[MeMO Pad 7 General] bravesoul:
Mission Accomplished!

Got the Tablet updated into WW.182! :good:

Kept my sanity! :cyclops:

And even got the girl!!!!! :cool:

Thank you so much to everyone who helped me out. :victory:
[MeMO Pad 7 General] pjim:
Well.......

How? What happened?
[MeMO Pad 7 General] bravesoul:
All I done was follow your lead.

The permissions were the issue.

When I turned it to rwxrwxrwx, the tablet updated, but even then it hanged, so I reboot it again and that time it went all the way.

hoorah! ;)
[MeMO Pad 7 General] dms76:
Maybe I'm doing something wrong, but I am unable to locate the drivers for a sideload. When I boot into recovery and select update via adb push I get a driver not found.
[MeMO Pad 7 General] jerbear294:
It should be the same drivers as the ones used for normal ADB.
[MeMO Pad 7 General] slayeralive:
http://adbdriver.com/
[MeMO Pad 7 General] dms76:
Thank you that did it, I was trying http://xdaforums.com/showthread.php?t=2588979 which didn't work.
[MeMO Pad 7 General] GuyInDogSuit:
198 update failed, 'cause I forgot to unfreeze a couple non-ASUS apps, I guess, and I couldn't get the retarded updater to find the update again, so I forced a downgrade to try it over again. Worked like a charm. Still can't get it to find the update, though. Grrrrr. I'm doing yet another factory restore to see if that fixes it.

I'm shocked that ASUS STILL hasn't put up the 191 firmware on their support site.
[MeMO Pad 7 General] wesleythedev19:
help

so will this work on a bricked ww firmware? I need help anybody im in a bootloop guys or do I need to wipe /system with fastboot im good with adb and fastboot! thanks guys! ps:I need this Tablet Or im dead:confused:
[MeMO Pad 7 General] jerbear294:
From what I know, this method will work. Heck, it works even if the tab doesn't go past the bootloader. I see no reason why it wouldn't work now.
[MeMO Pad 7 General] wesleythedev19:
okay

okay im downloading the side load ROM now im going to attempt to resurrect my tablet:highfive:
[MeMO Pad 7 General] namagakumon:
You're awesome, OP. I had a bricked Memo collecting dust in my drawer. Thanks to you I can put it into good use.
[MeMO Pad 7 General] GuyInDogSuit:
I can verify that this not only works with downgrading as well, but you can also apply OTA updates with this method, too, for those who have problems doing it the normal way like I did. The 198 OTA failed for me despite unfreezing all of my apps, and it wouldn't prompt to update again, so I downgraded to 182, thinking it would upgrade from there. Nope. But I got both the 191 and 198 OTAs to flash from 182 using this method.
[MeMO Pad 7 General] FreeZeee:
Can i downgrade it from 1.98 do 1.82 without update.zip on root/data?
[MeMO Pad 7 General] bravesoul:
Not that I know of.
[MeMO Pad 7 General] hansennn:
Is this instruction that returning from CN Rom to WW Rom, right?

So, the prior thing is this, I guess..

Then, I'm wondering how to enter recovery and sideload CN rom?

EDIT: Okay, I found this, I guess this is it.

I think this is the key point that might be possible to unbrick bricked device.

One more thing, why should I sideload CN rom first, and need complicated method to return WW rom?

If the sideloading method is refresh the device to factory new, Is it impossible that sideload WW rom directly?

Always many thanks :)
[MeMO Pad 7 General] bravesoul:
The main reason is that asus screwed everyone by applying an encrypted bootloader that doesn't allow anyone to **** around with recovery and custom roms. I don't know. Maybe asus is sick of the dev community that for years have being improving their products with no cost, maybe they're an elite think tank!

Whatever the reason, someone in asus is not doing its job properly.

In any case, the direct sideloading of the WW ROM isn't possible at the time.