yashsingh1/xdaforums huggingface dataset:
[Huawei MediaPad X2] audioralf:
It seems that you installed the KangVIP Rom before you installed the universalCustB112?

The UniveralCustB112 is a configuration zip file , wich enables to install 703 software on an 701 or a 702.

To come out of the bootloop you have to connect the USB cable and start the phone via Power and Vol- Button. Then you are in fastboot modus.

If the device is not recognized by adb anymore, then

unconnect USB

and uninstall Huawei Hisuite and install it again.

Then uninstall "adb minimal" and reinstall.

Boot your PC

Then connect it in fastboot and start a command window and type "adb devices": The phone shoud answer with the serialnumber.

If this is ok then install the files for the B112 https://drive.google.com/file/d/0By1mhgPLc1LqUndJZmt2MGRlbmc/view

Then Install TWRP 5.11 https://drive.google.com/file/d/0B5I_q70mNuR4Uy1XdXVoSG1SMXc/view

Then type adb boot recovery and press Return key.- > this boots phone in TWRP

Then do a factory reset on TWRP via WIPE and advanced Wipe and check "dalvic, dalvic cache, and userdata"

If you don't already have transferred the univeral Cust B112 to your device press MOUNT and then "Mount USB storage"

Then the external SD card becomes visible on your PC as external drive and you can copy files on it.

After this you must unmount the USB via the button and return to TWRP Main menu

Press Install and select external_sd to find the transfrerred file.

Install the univeral-cust-B112.zip

Goto Fastboot and install the recovery for B112

Then boot the phone via vol- vol+ and Powerkey .

Then dload will start and flash B112
[Huawei MediaPad X2] under-developed:
Hi,

eventually I managed to reboot the phone into fastboot mode - I guess I just needed to wait until the battery died enough for it to forget it was stuck !

I have put back the B015 files and powered down - it will boot from this state

("about phone" still says it's a GEM-703 with build number currently the B111_kangvip and emui 3.0.5 so I think I'm back to where I was yesterday and can try again)

It is now charging so that I can have another (proper) try later.

so, from here I am planning to do as follows - please tell me if it's wrong (I'll wait for advice this time !)

---------------

Install TWRP 5.1.1

and install universalcust for B112

(I think this is where I've been going wrong - somewhere in the "how to" thread I go the idea that kangvip b112 was "universal cust")

Do a factory reset in TWR

Then flash boot,system, and recovery

and userdata ??

and try to start the dload via the vol- vol+ buttons.

If it runs into error on about 5 % flash userdata.img and try again.

If it runs into error repeat staring dload up to 4 times

If the dload process was successful, don't check the "about phone" info, but install TWRP and the universal cust B112.

Then do a nandroid

You mean a nandroid backup, or something else ?

and then install NearStock B111 the SimplyGoogle112

---------- Post added at 02:39 PM ---------- Previous post was at 02:31 PM ----------

Oh, and I'm most of the way to getting the back off the phone too !!

- I think I need a little bit more patience
[Huawei MediaPad X2] audioralf:
have you now flashed the files for b112?

I wrote by purpose not to flash userdata and cust! It may work. If not, flash also userdata, but not cust.img. Report please what happened.

And yes nandroid is the Backup in TWRP

Gesendet von meinem GEM-703L mit Tapatalk
[Huawei MediaPad X2] under-developed:
Thanks a-r

I made it almost all the way to the end !

(when I saw your comment

" I wrote by purpose not to flash userdata and cust! It may work. If not, flash also userdata, but not cust.img. Report please what happened."

I had already flashed the userdata file but not "cust" so I carried on anyway and got quite a long way through) on the "how to" method I am at step 16

I think my phone now has the simply google version installed but I can't find out because about 1 second after the setup screen appears (where you'd configure wifi, accounts etc) the screen "wipes" upwards and I'm left with a blank white/grey screen.

At the bottom of the screen there is ONLY the normal "back" button (not the usual 3) but it is not active - pressing it does nothing

If I leave that screen for long enough (a few minutes), the phone reboots and does the same again.

Have you seen that before ? (I have seen the fist page where it mentions allowing permission for kangvip tools - I didn't see this request)

Might it help if I go back through the steps and avoid flashing userdata ?

---------- Post added at 09:37 PM ---------- Previous post was at 09:11 PM ----------

more updates:

I have tried rebooting by holding the power button as well as just waiting for it to happen. On one of the "loops" the setup screen stayed on for a bit longer so I "skipped" all the setup options and was planning to keep going with your steps but the phone rebooted itself before I even got to look at "about phone" and the next time it booted I had a lockscreen with an image (looks a bit like waves breaking on a shore). That screen does not respond to touch and soon is replaced by the grey screen (now with 3 buttons at the bottom and the time (correct), battery level and 3G meter at the top right)

It's as though the phone is very slowly recovering/learning

---------- Post added at 09:44 PM ---------- Previous post was at 09:37 PM ----------

(I can still boot into TWRP or fastboot modes - though fastboot/ADB cannot see the phone)

will try doing some wiping, reloading of ROM)
[Huawei MediaPad X2] under-developed:
I've gone back to the nandroid backup from step 12 of the guide. Staying there for now (when I try to go from there to reinstall "simply google nearstock" I get the grey screen again)
[Huawei MediaPad X2] audioralf:
The white screen on first boot is the bug in kangvip V2 B112.

For this I returned to Near stock B111.

This Version was published by ajsmsg78 in a post, but not on opening post our that thread. There he replaced the link to the never 112 version. I tested this for about 3 weeks and could not solve the other problems this version has. Kangvip is not compatible to supersu.

For some time he origin link to Nearstock was not working anymore. I updated it here and in post 1

Please check if you have the correct version. NearStock_B111_GAPPS.zip

Gesendet von meinem GEM-703L mit Tapatalk
[Huawei MediaPad X2] under-developed:
Hi - thanks again

Yes, that is the version I used (or at least it has the same filename).

Am I right that all I should need to do from where I am now, is to do a factory reset in TWRP (that's just wiping cache & dalvik, isn't it?) and then install the new ROM, or do I need to wipe other stuff too ?
[Huawei MediaPad X2] narron:
otg audio

otg audio
[Huawei MediaPad X2] audioralf:
... Again... For factory reset wipe cache, dalvic cache and userdata.

... I am not 100% if the file is that near stock version which I had used, because some versions had the same filename.

Nearstock has 1461259 Bytes

I am uploading again wait until 09:20 pm
[Huawei MediaPad X2] under-developed:
"my" nearstock has 1,393,016,942 bytes
[Huawei MediaPad X2] audioralf:
So the upload is finnished. Now you shoud get the right one

Nearstock Jan 18 2016:

https://drive.google.com/file/d/0By1mhgPLc1LqQWd4NERTSkxGYzA/view?usp=sharing
[Huawei MediaPad X2] under-developed:
DONE ! - as far as I can tell I have now upgraded my 702L/B006 to 703/B112 (or 111 anyway as that's what the nearstock reports as)

I'll upload a screenshot of the about phone page to show what it thinks it is

audioralf, THANK YOU ! you've been really patient & helpful
[Huawei MediaPad X2] audioralf:
Great,

so can you resume what was the special thing with the B006?

Gesendet von meinem GEM-703L mit Tapatalk
[Huawei MediaPad X2] under-developed:
I'll try, but I'm no expert and all of this may be wrong:

I was mostly just following your instructions, with slight alterations when things didn't seem to work

I did do the steps in part 3 as going straight from 2 to 4 wasn't working for me

I eventually managed to flash the B112 system and userdata files as well as the boot and recovery. (many, many times I was unable to flash the system & userdata - "remote: command not allowed")

Not sure how it happened but one thing I wondered about was that maybe this refusing to flash files was what an unrooted phone might do, so I reflashed superSU about 3 times at points along the way, just to make sure it was always active. (I also went to developer options a few times and made sure I told it to allow mock locations and stopped it from monitoring apps installed by ADB)

(when I started out, I didn't really know what "flash" meant and even just adding "flash using ADB/fastboot" would have helped me)

The main difference after that was installing the universalcustB112 as in your post #182 -this seems to be what got the "dload" of B112 UPDATE.app to work (when I read the instructions I thought that the universal cust was the kangvip file but I see that this has now been changed - I think that will help people a lot)

(to help people like me, you could add a very short description explaining that the dload method involves putting the dload folder onto your sd card and then booting into phone normally before going "settings" > "update" > menu > "local update")

I hope that helps somebody

thanks again audioralf

(one thing to add - when I go to settings>update>update settings, it tells me that the download is disabled because my system has been altered)
[Huawei MediaPad X2] ajsmsg78:
If you can do the dload method by putting the update.app from B112 on your SD card in a dload folder and update successfully to it (even if you're actually already on B112) then you know you have really updated successfully. I'm not at my phone but have audioralf take a look at the baseband and see if it matches his B112 baseband. Your kernel looks like it's the B111 kernel.
[Huawei MediaPad X2] under-developed:
It does let me do this ("fails" at ninety-something % as predicted in the guide)

Phone now suggests a lower storage size and android v 4.3 - again as described

Baseband version has also changed, to 20.201.81.35.320

kernel now 3.10.30-20174-768

emui 2.0
[Huawei MediaPad X2] audioralf:
Oh why did you do flash again?

You had done a clean b112 dload and even a backup from tis

on near stock it was all ok. Even baseband. Same on my device.

What you see now after dload of b112 again is normal, because dload flashes the 703 cust on phone and this corrupted the about phone info.

Install near stock again. Don't wipe and you will keep your data.
[Huawei MediaPad X2] audioralf:
There was one user with untouched B006 cust. I asked him to send it to you.

Please inform me, if there is a new universal cust including modification for b006.

The way including downgrade and multiple supersu is possible, but seems too complex.

I uploaded your special version 111 kang VIP v1 including Huawei backup and king root as nearstock to my Google drive, because kang VIP v2 had too much problems for me. White screen on first boot, white icons in landscape on white background...

Gesendet von meinem GEM-703L mit Tapatalk
[Huawei MediaPad X2] ajsmsg78:
Was this after flashing the B112 update.app? If so, just flash the B112 universal cust and you should be good and on full B112. Then the next time you dload or take an ota is shouldn't fail at ninety something percent anymore. Here's a screen shot of my About Phone (702L converted to a 703L and on B112)

---------- Post added at 12:29 PM ---------- Previous post was at 12:27 PM ----------

Yeah it should be integrated into all the roms as well as the universal cust.

---------- Post added at 12:33 PM ---------- Previous post was at 12:29 PM ----------

I don't think he was on full B112 as his baseband and kernel changed after he did the dload to B112. The About Phone info is wrong simply because even when you flash to a 703L the phone still knows it's not a 703L and looks for the cust folder of the actual phone model (701L, 702L) If it's not present the phone shows the wrong info. That's why I created the universal cust so it's all integrated and any model can just flash it and have the proper cust folder for their device along with all the other cust folders from other phone models for rom compatibility. Just have a look in the B112 universal cust. In the cust/hw folder are all the cust that everyone has sent me. (meafnaf, seas, spcseas, malaysia, etc) If anyone's original cust folder has something in it that's not present in the universal cust then I would advise them to send me their cust folder as there are quite a few different ones as you already know.
[Huawei MediaPad X2] audioralf:
I understand. But this user came from B006, which is not supported yet.

So the dload must fail on his device.

The cust in near stock b111 from Jan, 18 Rom even is a downgrade from the b112 stock, he had flashed before.

So if he flashed again the cust did not fit.

I guess if he install the 112 cust on the near stock 111, it might not fail on dload, if his hardware is included in the uni cust.

The baseband and kernel have a lower number, so this is a hint that his hardware is different.

Did your get the untouched b006 form the other user I mentioned, yet?

See post #179
[Huawei MediaPad X2] under-developed:
Hi audioralf and ajsmsg78,

reflashed the 112 cust and then the simply google 112 ROM

I've now got the simply google 112 ROM installed (this was the one that gave me whitescreen problems previously, I think - certainly the lockscreen image is the same)

My "about phone" screen looks pretty much exactly like ajsmsg78's thumbnail picture (other than the ROM names and slightly different amount of available storage)

Does this mean that I have successfully gone to b112 this time?

(when I go "settings" > "update", this ROM doesn't seem to open an emui screen like the others I've had during this process. It tells me that I'm up to date but I don't see, for example, how to start a local update for a "dload" installation. Is this normal ?)
[Huawei MediaPad X2] the-bunker:
Hi - my 702L is on B006 & reading this thread it seems I need to downgrade to B003 first. The link for B003 is for 701L - so can I use this on my 702L to downgrade to B003 ?

Many thanks

Paul
[Huawei MediaPad X2] audioralf:
No you are of ajsmsg78 custom Roms.

You had been compete to B112 after the first dload of b112. If you followed my guide you made a Nandroid from this, because only this official stock version had the manual update function, and would receive ota updates.

If your don't have a Nandroid, you come to stock via flashing boot, recovery userdata and system, and then do the dload and then install the universal cust again.

But this is a version for the Chinese market, so youre fine with ajsmsg78 5.1.1 Roms until he publishes the update for 6.0.

my device: 701->703 B111 kang VIP v1
[Huawei MediaPad X2] audioralf:
I guess so. If you make a Nandroid and a copy of your cust folder your are save to restore everything and try the b003.

send zipped cust to ajsmsg78, he could check, if this is a variant, he has to integrate in universal cust. B112.

my device: 701->703 B111 kang VIP v1
[Huawei MediaPad X2] under-developed:
Oh, I think I see - I did take a nandroid backup (at step 12 of your guide) so I can easily go back to that if I need to (would I just boot into twrp and go to the backup or do some things need to be wiped also ?).

I don't really understand the discussion you're having with ajsmsg78; mostly I just follow suggestions.

Phone seems OK on this current ajsmsg version so I'll probably stay with it at least for a while - I'm back to work tomorrow after some time off

Thanks again
[Huawei MediaPad X2] the-bunker:
Many thanks, I'll do that.

Best regards

Paul

---------- Post added at 05:26 PM ---------- Previous post was at 05:01 PM ----------

Update: Found this link to various firmwares, inc 702L B003:

http://xdaforums.com/mediapad-x2/general/mediapad-x2-firmware-702l-703l-t3168925

So I guess it should be cleaner to downgrade to 702L B003 (but I will still ask ajsmsg78 to take a look at my zipped cust)
[Huawei MediaPad X2] audioralf:
Before trial downgrading, install the newest universal cust B112 on TWRP 5.11.

Do a full wipe in TWRP.

Then flash the B112 files: boot, system, userdata and recovery but not cust.

Then use the 3 finger vol+ and vol- and power key while device is usb-unplugged and dload folder contains the B112 update.

If it fails at about 5% repeat 3 finger start up to 4 times.

If ok ( 95% abort is still ok) then flash TWRP and universal cust 112

Then system could start.

For save repeat dload from emui.

If TWRP starts instead of software installing, change USB connecting, and report if it is a difference. If software installing fails then flash recovery.img again and cust.img. Please report, if this was necessary and successful.

If it does not work at all try rule save with the b015 files

If this also does not work, downgrade to b003 and try again

my device: 701->703 B111 kang VIP v1
[Huawei MediaPad X2] the-bunker:
Many thanks - it's been a while since I did any rooting, so I'm a bit slow. Just finishing up the Nandroid backup before zipping Cust folder & then will try your steps & let you know.

Cheers, Paul

---------- Post added at 06:09 PM ---------- Previous post was at 05:14 PM ----------

Hi audioralf, I'm just reading your 1st step which says to install cust B112 on TWRP 5.1.1

B006 is Android 5.0.1, so at the moment I'm on TWRP 5.0 .

Can I just flash TWRP 5.1.1 without needing to upgrade to an Android 5.1.1 build first ? - or do I need to follow the steps to get me to a 5.1.1 firmware first - like B106 & then use TWRP5.1.1 ??

In your 2nd step you say flash the B112 files - I don't see any links for those, so do you mean the B015 files posted at the beginning of this thread ??

Many thanks

Paul
[Huawei MediaPad X2] audioralf:
The guide in post #1 was written when we did not have b112. No one can go back to 5.0 and so new users can test new variations.

I hope that there could be an easier way.

It is reported that TWRP for 5.11 also runs on 5.0. So please try and report.

Take the links form #1

I guess you will fail on dload of 112 on Android 5.0. But no one has tested that with the new custB112.

Some people said that dload works after 3 attempts. So I asked you to try that.

Some people said it is important to wipe everything before dload. So please try.

my device: 701->703 B111 kang VIP v1
[Huawei MediaPad X2] the-bunker:
OK Thanks - I've already installed cust_112 via TWRP 5.0, did a full wiped & then tried to flash the 4 img files (boot, system, userdata & recovery) from B112 (I extracted from the B112 updat.app) - but that just went into a bootloop.

So I flashed the 4 img files from B015 (links as posted) & now the 3 finger salute has kicked off the update - but it failed at about 60%.

---------- Post added at 09:07 PM ---------- Previous post was at 08:52 PM ----------

UPDATE: looks like I wrong about 60% - I retried & it got to over 95% but didn't complete. The wording was in chinese 2nd time round.

Have restarted now - it says I'm in EMUI 2.0 with a quad core 1.2ghz, 1gb ram android 4.3 !

---------- Post added at 09:16 PM ---------- Previous post was at 09:07 PM ----------

UPDATE: ok have now installed TWRP 5.1.1 & am doing a full Nandroid backup...

---------- Post added at 09:42 PM ---------- Previous post was at 09:16 PM ----------

SUCCESS ! - GEM 703L, Android 5.1.1, 3.0gb Ram, EMUI 3.1

Other info:

Baseband: 21.600.20.00.010

Kernel: 3.10.74-gfbf694f
[Huawei MediaPad X2] audioralf:
So we can say: It is not possible to use the B112 files for the upgrade proces: We MUST flash the the B015 files on 701/702 models.

Ok, this is validating that repeating dload is correct.

Aborting at 95% is correct, because the software checks for the hardware and recognizes that it was tricked and will not update the "about phone". This is like expected.

The "about phone" info is patched because you installed the Universal cust on TWRP.

Baseband and kernel is ok. Same as on my device.

Thank you for your test. :)

This gives evidence that B006 is no problem and it is not neccessary to downgrade. :o:o

Two questions left, to be sure:

Did you keep the B112 update.app in dload folder, or did you use the B015 update.app?

Did do do the wipes at the beginning?
[Huawei MediaPad X2] the-bunker:
Many, many thanks to you audioralf for your help - and to answer your questions:

Yes - I went straight for the B112 update.app in the dload folder - so I upgraded from B006 directly to B112

Yes - I followed your steps including full wipe & shorter wipe (dalvik & cache I think)

I'm now really happy with this phone - for the first time since I gave up my Galaxy Mega.

All I need now is to be able to hide the statusbar (mainly for the browser) & then it's perfect.

Thanks again for all your help.

Best regards

Paul
[Huawei MediaPad X2] ajsmsg78:
In boat browser when the phone is in landscape it automatically hides the statusbar.
[Huawei MediaPad X2] the-bunker:
So, to summarise the steps with audioralf's guidance:

1. Unlock bootloader, flash TWRP & root - see guide by ajsmsg78 http://xdaforums.com/mediapad-x2/general/mediapad-x2-unlock-bootloader-root-guide-t3212325

a. note that audioralf suggests that TWRP 5.1.1 should work even though on android 5.0 at this point - I didn't get to test this & needed to upgrade in step 7.

b. Once rooted, reboot & use a file manager to zip up the cust folder from the root of the internal sd & copy that to a safe place (I believe this is a precautionary step in case you need to get back to original state)

2. Download the following in prep for steps 3 & 5 (see post #1 for the links) - place onto the root directory of the external SD card

a. Universal Cust B112.zip - copy as is to the root directory of the external SD card

b. B112 firmware - unzip & copy the 'dload' folder with the B112 update.app into the root directory of the external SD card

c. NearStockB111.zip - copy as is to the root directory of the external SD card

3. Boot into Recovery mode (vol up & power button)

a. Do a backup (in case you ever need to get back) - change the backup location to the external SD card first.

b. Install universal cust B112 you downloaded in step 2

c. Do a full wipe

4. Boot into Bootloader mode & use fastboot - for help see guide by Benjiro http://xdaforums.com/mediapad-x2/general/mini-guide-adb-installation-usage-t3183906

a. Use fastboot to flash the 4 B015 img files (boot, system, userdata, recovery) - see post #1 for links & exact syntax to use.

5. 3 finger salute - to invoke the manual update to B112 (it will pick up from the dload folder you did in step 2)

I ran this twice (1st time I wasn't sure how far it got before giving an error, 2nd time it got to > 95%)

6. Reboot (note it takes a while as it completes the upgrade to 5.1.1), and skip past screens to check the About phone & I noted it said Android 4.3, 1gb ram, EMUI 2.0 (this is just a temporary blip - that is fixed with cust 112)

7. Upgrade to TWRP 5.1.1 (if you hadn't already used this in step 1)

a. Boot into Bootloader mode (vol down + power button with usb connected to pc/laptop - with ADB & drivers installed - see step 4 above)

b. fastboot TWRP 5.1.1 (if you had used TWRP5.0 in step 1) - syntax: fastboot flash recovery TWRP-ENG-5.1.1.img

8. Boot into Recovery mode (vol up & power button)

a. Select backup (so you can get back to stock B112 to upgrade to Android 6.0 in the future) - change the backup location to the external SD card first.

b. Select Wipe - and do a factory reset

c. Select Install and choose the NearStockB111.zip from your external SD Card.

d. Select Wipe & choose Advanced Wipe & check boxes to wipe cache and dalvic and Data

e. Reboot into system.

It took a few minutes to reboot & when I checked About Phone it says Android 5.1.1, 3gb Ram

Hope I haven't missed anything

ps: Apart from the Nandroid backups & zip of cust folder, these steps do not cover backing up your apps, data, etc & then restoring - as I don't bother with this - I just rely on google sync & re-install apps I want.

Many thanks to audioralf !