This guide will help you to convert your device to OEM totally and permanently. After this procedure you will be able to flash firmware and recieve OTA updates for non CC devices.
Don't be afraid to brick your phone, if something will go wrong, you'll be able to revert back changes without any consequences.
Follow these steps exactly, one after other:
Make backup of all your personal data because they all will be erased. But do not use twrp for backup!
Download full B148 firmware. You can get it from here: https://drive.google.com/folderview?...00&usp=sharing
Extract package with firmware to your sdcard. You should get dload\UPDATE.APP in root directory of your sdcard. If there was update to Lolipop previously, delete it first!
Copy this repacked TWRP in your adb/fastboot directory https://yadi.sk/d/xWXOpG_3hf4iu
Copy this zip-archive to your sdcard https://yadi.sk/d/gw45fwwfhfKU2
Open command shell in your adb/fastboot directory and execute:
Code:
adb reboot-bootloader
your device will reboot in fastboot mode.
Flash TWRP that you downloaded in step #4:
Code:
fastboot flash recovery twrp.img
Disconnect device from PC and power it off by holding power button untill screen off.
Boot into TWRP: press and hold vol+ and power buttons simultaneously untill you'll see boot logo.
In TWRP make backup of oeminfo partition - press "Backup" and mark "OEMinfo". Save backup to sdcard.
Return to main menu, press "Install" and select OEM.zip which was copied to your sdcard in step #5. Swipe to confirm to install package.
This package will patch your oeminfo partition and flash stock recovery. Don't press "Reboot" button after completion.
Disconnect your device from PC or charger if it was connected, power off device by pressing and holding power button untill screen off.
Power on device by three buttons method: press and hold power, vol+, vol- simultaneously untill you'll see boot logo.
Update process should be start.
After successful update to B148 you are good to go to Lollipop.
How to revert back in case if update to B148 will fail:
Switch your device in fastboot mode: power off device, then press and hold vol- and connect device to PC.
Flash repacked TWRP as was mentioned in step #7.
Boot into TWRP, press "Restore" and restore your backup of oeminfo partition made in step #10.
Reboot in system.
If you are brave and desperate enough, you can go much shorter way:
Install TWRP if you had not yet.
Install OEM.zip from step #5.
Update to Lollipop.
Note that in this way you will not have backup and ability to revert back changes and it's not a fact that Lolliip update will proceed, it was not tested, but I presume it will.
I'm not taking any responsibility if you brick your phone, all you will do with your device is on your own risk.
Requirements:
Unlocked bootloader.
I want say thanks to:
@ArkAngel06 for testing, providing me oeminfo and his patience.
@xordos for providing me his oeminfo.
@tdamocles for testing and his responsiveness.
P.S. Sorry for my poor english, it's not my native language.
I have successfully installed Lollipop, the new TWRP and rerooted. A huge thanks to Kostyan_nsk for making this possible for us, CC users and to SHM for providing TWRP for Lollipop. You guys are awesome !! We couldn't thank you enough !
Edit:
I forgot to thank xordos too . . . who has always been a huge help to HAM2 users !
Great, finally, this is another milestone. Dont know how to say in words. and Lollipop... ** Cheeeeeers **
Man, now I am thinking to get a backup phone, after one year, I still not find any other phone at this price level. I mean battery and screen size.
Hat off and Thanks all the hard work.
xordos said:
Great, finally, this is another milestone. Dont know how to say in words. and Lollipop... ** Cheeeeeers **
Man, now I am thinking to get a backup phone, after one year, I still not find any other phone at this price level. I mean battery and screen size.
Hat off and Thanks all the hard work.
Click to expand...
Click to collapse
This is all a little off track, but..
Yeah, I bought mine(CC) off ebay-used-$150/ no charger. Not in bad shape with a small nick on one corner.
This phone runs tons better than my wifes Galaxy s4 with the SD600 on lollipop. The s4 lags like hell. I tried using the s4 with the touchsquid remote app and it was unusable/laggy. The Huawei works great with touchsquid remote app.
where is all CC users?
Anyone think that this will also work for the Wind Mobile version?
Sent from my MT2L03 using Tapatalk
jscrimshaw said:
Anyone think that this will also work for the Wind Mobile version?
Sent from my MT2L03 using Tapatalk
Click to expand...
Click to collapse
Yes it works, I did it with my WIND Mobile HAM 2
Each time I try to flash the oem.zip file in TWRP I get:
E: Unable to open zip file
Error flashing zip 'sdcard/OEM.zip'
Updating partition details...
Any ideas please?
johndubs said:
Each time I try to flash the oem.zip file in TWRP I get:
E: Unable to open zip file
Error flashing zip 'sdcard/OEM.zip'
Updating partition details...
Any ideas please?
Click to expand...
Click to collapse
Trying to open your zip file on your PC to make sure it's not corrupt.
medwatt said:
Trying to open your zip file on your PC to make sure it's not corrupt.
Click to expand...
Click to collapse
Thanks Medwatt. I tried thatand all seems to be fine. Is it possible to upload each file individually and flash each of the files in turn?
johndubs said:
Each time I try to flash the oem.zip file in TWRP I get:
E: Unable to open zip file
Error flashing zip 'sdcard/OEM.zip'
Updating partition details...
Any ideas please?
Click to expand...
Click to collapse
Check file permissions and make sure zip file signature verification disabled.
Thanks! This works!
Worked the first time. I have a stock "CC" Ascend mate running L now! Thanks again!
johndubs said:
Thanks Medwatt. I tried thatand all seems to be fine. Is it possible to upload each file individually and flash each of the files in turn?
Click to expand...
Click to collapse
in es file explorer (or you can use other tools in pc), select oem.zip, property, and calc the md5 checksum, it should be
27fed6aca60059671a0208e6f190d3cb
also, you can try different sdcard
xordos said:
in es file explorer (or you can use other tools in pc), select oem.zip, property, and calc the md5 checksum, it should be
27fed6aca60059671a0208e6f190d3cb
also, you can try different sdcard
Click to expand...
Click to collapse
Thanks for your help. MD5 checksum revealed faulty SD card!
when i try to fastboot flash recovery twrp.img I get an error: cannot open 'twrp.img' .... what can be the problem? I downloaded the one in the guide and moved it to my ADB folder and overwrited my old one that was there.
Nevermind, I got it to work on my MT2-L03 SAMPLE. I ended up following the shortcut at the bottom of the guide and used my old TWRP to flash. Thanks for the help dude you're awesome!
GadgetStrutter said:
when i try to fastboot flash recovery twrp.img I get an error: cannot open 'twrp.img' .... what can be the problem? I downloaded the one in the guide and moved it to my ADB folder and overwrited my old one that was there.
Click to expand...
Click to collapse
Sounds like your typing the name of the file wrong....Download again, before moving it into your ADB folder rename it twrp2.img, then move it, then
Code:
fastboot flash recovery twrp2.img[/img]
For those new to convertion (just did it today),
1. Remember to enable USB debugging in Settings
2. Install Adb installer (to use with adb and fastboot commands)
xordos said:
where is all CC users?
Click to expand...
Click to collapse
Worked perfectly on my HAM2 and my wife's. Thanks for all your work on this!!!
OptimusPrimous said:
Worked perfectly on my HAM2 and my wife's. Thanks for all your work on this!!!
Click to expand...
Click to collapse
Thats all @Kostyan_nsk great work that successfully patched CC to OEM, every CC user should press the thanks button in the 1st post if not done that yet.
Went about installing adb and fastboot. Successfully boot unlocked and now when I am trying to flash the update package for B148 the update seems to be going no where.
It did change my CC logos to Huawei one so OEM partitions may have been correctly flashed.
The screen is now stuck at usb update starting...
What can be wrong? Is it safe to reboot at this screen. I suspect the update didnt initialize properly.
I have the update.app copied to the root folder of my microsd and thats what i selected.
Please help. Thanks
Never mind folks, rookie mistake i didnt have the update.app in a dload folder just copied the file itself.
The update is now in progress.
Related
Hi,
i had B00 with root and chinese recovery
after updating to b121 i goot bootloop
than i changed recovery back to stock
tried to delete cache and system etc. nothing worked
B100 Upgrade via dload/update.app not working cause version mismatch i think
what can i do now. I don't need 349 euro trash.
please help me
Same problem here
Try updating with the full B121 ROM. I have uploaded it here https://mega.nz/#!dgZwAQpb!XcZSZJOWvG1DIDoJRr_EYSehtqTU1ciPE53bNhII8JQ
Follow the instructions in the included documents.
flibblesan said:
Try updating with the full B121 ROM. I have uploaded it here https://mega.nz/#!dgZwAQpb!XcZSZJOWvG1DIDoJRr_EYSehtqTU1ciPE53bNhII8JQ
Follow the instructions in the included documents.
Click to expand...
Click to collapse
Thanks mate, I'll give it a try.
pappapishu said:
Thanks mate, I'll give it a try.
Click to expand...
Click to collapse
any chance?
Fixed it with honor 6 multi-tool, huwaeiupdateextractor and fw b100.
Now i'm installing the b121 right away.
@evilmumi: hope you fixed it as well.
---------- Post added at 04:26 PM ---------- Previous post was at 04:24 PM ----------
evilmumi said:
any chance?
Click to expand...
Click to collapse
sorry, i didn't see your previous post.
yes, i figured out:
- downlaod the fw b100 version
- download honor 6 multi-tool (yes, even if it's made for the 6, it worked for 7 as well) and follow the "unbrick" procedure
if you have any question please ask
flibblesan said:
Try updating with the full B121 ROM. I have uploaded it here ...
Follow the instructions in the included documents.
Click to expand...
Click to collapse
thanks
you are my hero.
back in business
i hope i can use titanium backup to restore my old data w/o root
i am in trouble! i have erased all (cache dalvick data and system) by twrp! Now obviously the phone is on bootloop...i need desperately a system rom to flash
flibblesan said:
Try updating with the full B121 ROM. I have uploaded it here https://mega.nz/#!dgZwAQpb!XcZSZJOWvG1DIDoJRr_EYSehtqTU1ciPE53bNhII8JQ
Follow the instructions in the included documents.
Click to expand...
Click to collapse
Alphasampei said:
i am in trouble! i have erased all (cache dalvick data and system) by twrp! Now obviously the phone is on bootloop...i need desperately a system rom to flash
Click to expand...
Click to collapse
just read the thread
short:
0.)download from mega
1.) copy update.app on micro sd card /dload
2.)boot with volume up down and power than you can work!
evilmumi said:
just read the thread
short:
0.)download from mega
1.) copy update.app on micro sd card /dload
2.)boot with volume up down and power than you can work!
Click to expand...
Click to collapse
nope! still boot in twrp, i have no system inside the phone
sometimes we have this problem in our german forum too! More on rooted devices!
reflashing the full B100 or B121 rom help
we do it like your user described it here:http://forum.xda-developers.com/showpost.php?p=63070827&postcount=9
BTW: Where we can find the "updateextractor"? All versions of it that i have found, doesn’t work for H7 Roms!:crying:
Back to System boot
evilmumi said:
Hi,
i had B00 with root and chinese recovery
after updating to b121 i goot bootloop
than i changed recovery back to stock
tried to delete cache and system etc. nothing worked
B100 Upgrade via dload/update.app not working cause version mismatch i think
what can i do now. I don't need 349 euro trash.
please help me
Click to expand...
Click to collapse
When the phone is in RecoveryMode try a long press vol-up/vol-down/special-key and power all together for a few seconds until the phone reboots ... after that, the phone will start in SystemMode ... for me it worked.
stalfst said:
When the phone is in RecoveryMode try a long press vol-up/vol-down/special-key and power all together for a few seconds until the phone reboots ... after that, the phone will start in SystemMode ... for me it worked.
Click to expand...
Click to collapse
I realized that when I plugged the charger to phone and then powered it, it went off the TWRP boot loop. I fdon't know if any others have same issue.
When I updated my phone I had same kind of problem so I flashed stock recovery and then made the force upgrade following the rom's intructions.
Now eveything works again.
Alphasampei said:
nope! still boot in twrp, i have no system inside the phone
Click to expand...
Click to collapse
Twrp has a bootloop bug.. I also got this after rooting. What you need to do is to get it out of the bootloop by getting the phone in fastboot/download mode. I have no clue on how I finally got it to boot in fastboot mode, but I tried and tried until it finally booted in fastboot. Then I flashed stock recovery and everything was good after that. Lesson learned was that twrp and especially Chinese twrp is buggy as hell!
kjettern said:
Twrp has a bootloop bug.. I also got this after rooting. What you need to do is to get it out of the bootloop by getting the phone in fastboot/download mode. I have no clue on how I finally got it to boot in fastboot mode, but I tried and tried until it finally booted in fastboot. Then I flashed stock recovery and everything was good after that. Lesson learned was that twrp and especially Chinese twrp is buggy as hell!
Click to expand...
Click to collapse
I had no problems at all, no bootloops or any other weird stuff. Perhaps because I wiped cache + dalvik after supersu installation?
have the same problem, what should i do?
sugarray21 said:
have the same problem, what should i do?
Click to expand...
Click to collapse
Read instruction HERE
Fix Bootloops
Breaking out of bootloops depends on your device state and what kind of problem you are having. In this section, we are going to focus on the popular case where you can’t access neither the system nor the recovery partitions.
• Step 1: Turn off the phone.
• Step 2: Press Volume UP + Power Button For 10 seconds while connecting the USB cable from your device to your computer. That must make you boot into the bootloader mode.
(Update: A user has reported that holding the power button is optional on some models. Thanks to @sminki for pointing that out).
• Step 3: Head to your computer and download and install the following tool:
http://forum.xda-developers.com/show....php?t=2433454
• Step 4: Download the latest complete update file (B121) from:
http://www.modaco.com/forums/topic/3...s-121115-b140/
Then, extract it and get its UPDATE.app file.
• Step 5: Use the Huawei Update Extractor to extract the (BOOT.img), (SYSTEM.img), (RECOVERY.img), (CACHE.img), (CUST.img), and (USERDATA.img) from the UPDATE.app file that you have extracted from Step 4.
• Step 6: Open your command prompt, and navigate to the right directory where you have extracted the image files. Use the “cd” and “..” commands to do so.
• Step 7: Type the following commands and execute them one by one >
Code:
fastboot flash boot BOOT.img
fastboot flash system SYSTEM.img
fastboot flash recovery RECOVERY.img
fastboot flash cache CACHE.img
fastboot flash cust CUST.img
• Step 8: You can also erase the user data if you like by typing and executing the following >
Code:
fastboot flash userdata USERDATA.img
• Step 9: Reboot your device using the following command >
Code:
fastboot reboot
• Step 10: You must be able to boot successfully into the system.
(Noten this model, the "fastboot erase [Partition]" command has been reported by two users that it is not working. Thus, flash the image files directly and if it did not work, then check with the Huawei support center to fix your device. Thanks to @sminki for reporting this).
http://forum.xda-developers.com/honor-7/general/guide-beginners-how-to-root-update-fix-t3255452
TWRP Terminal Emulator command method.
I followed the steps here, http://androidforums.com/threads/twrp-bootloop-fix-after-update-ota.922585/ Thanks to the Author... hash_brown.1855790
Which is actually for LG, but slightly altering for Honor7 it works!!
for Honor 7 the commands to be run from TWRP Terminal command emulator will be
dd if=/dev/zero of=/dev/block/platform/hi_mci.0/by-name/fota
Click to expand...
Click to collapse
Hit GO/enter(return)...wait, takes a few seconds
Now input this
dd if=/dev/zero of=/dev/block/platform/hi_mci.0/by-name/misc
Click to expand...
Click to collapse
Hit enter (return)...wait again.
When its complete, reboot.
:good:
Alphasampei said:
nope! still boot in twrp, i have no system inside the phone
Click to expand...
Click to collapse
I had the same problem with twrp i can walking through how to unbrick your phone happy to help
Guide to rooting infocus Epic 1 (for windows) for build 00.
This method is only tested on build 00IN_1_360 only. If you are on the older build, first update your phone to build 00IN_1_360 then proceed. Check Build number in settings->about phone.
Proceed at your own risk, I will not be help responsible if your phone bricks, Your warranty will be void after this. Also all phone data will be lost including data on internal memory like photos, etc after these steps so take necessary backups.
Prepare your system
1. Extract and Install MTK Driver Auto Installer v5.1632 (google it)
2. Install Phone F Driver (from phone CD-emulation/driver folder upon connecting your phone)
3. Minimal ADB and Fastboot installer v.1.4.2 (from xda)
4. Download latest SuperSU flashable zip file from here
5. Download twrp-3.0.3-0-epic1-noveritynoencrypt.zip from here, extract in the folder where you have installed adb and fastboot
6. Download noencryptnoverty_boot.zip from attachments and extract to folder where you have installed adb and fastboot
Steps to root:
1. Enable Developer options in phone settings (goto phone settings -> about phone -> tap build number 7 times)
1a. Enable OEM unlock
1b. Enable USB Debugging
2. Connect phone to computer, wait for hardware to auto install
3. open cmd as administrator
3a. goto the directory where adb and fastboot is installed
4. type command:
4a.
adb reboot bootloader
(Wait for phone to come in fastboot)
4b.
fastboot OEM unlock
(press vol up key on phone)
4c.
fastboot flash boot noveritynoencrypt.img
4d.
fastboot flash recovery recovery.img
4e.
fastboot reboot
You will get an phone orange state prompt, do not worry its normal. Phone may reboot once or twice. Wait for phone to normal bootup.
5. open cmd and type command
5e.
adb reboot recovery
Phone will reboot in recovery i.e. TWRP
6. Tap on Keep system read-only. Do not swipe to allow modifications. If TWRP asks for password, don't enter any press back.
7a. Tap Wipe -> Format Data. Come out to main menu, then click reboot and then recovery to restart recovery.
7b. Tap Wipe -> Advanced Wipe -> Select Dalvik /ART, Cache, Data and Internal Storage. This is important step, as these partitions are encrypted at the moment, so if you flash anything the phone rom may corrupt.
8. Come out and then Tap Reboot -> System
9. Once the phone is back, turn off the phone. Then power on with vol up key pressed to boot into TWRP
10. Tap Backup, select all partitions, select phone storage (SD card preferred) and take backup (optional step but highly recommended )
11. Now tap install, goto the location where you had copied SuperSU zip file, flash it.
Congratulations your Phone is rooted. Reboot, see SuperSU icon in app drawer.
Many thanks to @mujammil786 for providing stock files and @Bornstud for testing twrp builds
Special thanks to our devs @DespairFactor for modifying boot.img to disable Encryption and Verity and @kirito9 for creating TWRP for our device. Without their help, it wouldn’t have been possible.
MODS
(Take backup of your ROM/Data before applying any mods)
Viper4Android (Advanced Sound Enhancement)
Hugely Customizable and better than MaxxAudio or Dolby Atmos IMHO
Now working on our device Infocus Epic 1
Need to flash the 2 attached files via TWRP before installing the official app from HERE. Although latest version v2.5.0.5 also works, but i personally prefer v2.4.0.1 (busybox required)
(Note the attached files are not my work, they are picked from here and here. Say thanks to original contributors.)
Good V4A profile: HERE
Extract it to ViPER4Android Directory in internal Storage
Xposed
Needs no introduction. Every android enthusiast should know what it is. Anyway if you are new, xposed opens limitless ROM customization(s) and useful features via 100s of its modules.
Installation:
1. Flash framework xposed-v87-sdk23-arm64.zip from HERE via TWRP. Reboot after installation will take long time (~10 - 15 minutes)
2. Install app XposedInstaller_3.1.1.apk from HERE
Restoring phone back through SUT
If you are stuck somewhere or want to restore the phone factory state (like for when giving to repair), you can restore the phone back via SUT
Link for build 1280: https://firmwarefile.com/infocus-epic-1
Also dont turn off your phone as suggested in sut readme file. It only works when your phone is on. Check below vid for more instructions
https://m.youtube.com/watch?v=eV_cId5fC9E
Reduce battery consumption & phone temperature
Found an interesting thread, mod works on our device also
https://forum.xda-developers.com/red...tings-t3687897
I have tried both flavor 1 and flavor 2 over the past week. Results with flavor 1 were positive in the beginning but for some reason standby drain shot up after 3-4 days, not sure what the reason was.
On flavor 2, I have just disabled MTK perfservice by setting
ro.mtk_perfservice_support = 0 in build.prop
Yes this limits the a72 core to 1.5ghz, but i have noticed phone is heating less and need for charging the phone has reduced. I haven't noticed much drop in performance either, but that might be as I don't use intensive apps.
Mafioso said:
I've managed to unpack nb0 file through a688 tool, however its only successful in unpacking few files before it crashes with some array size error, but the good thing is I was able to extract the scatter file for this phone before it happened.
Anyway, I was hopeful that I would be able to make backup of Stock ROM and Recovery through it via spflash tools however as it turns out, spflash tool is giving me error while doing readback BROM ERROR: STATUS_BROM_CMD_SEND_DA_FAIL (0xC0060003)
Not sure how to fix it, i've updated my drivers as well as i'm using latest version of spflash tool (SP_Flash_Tool_v5.1628_Win)
Attaching scatter file.
Click to expand...
Click to collapse
From where uve downloaded the stock firmware
Romeotamizh said:
From where uve downloaded the stock firmware
Click to expand...
Click to collapse
http://firmwarefile.com/infocus-epic-1
Mafioso said:
http://firmwarefile.com/infocus-epic-1
Click to expand...
Click to collapse
Oh
---------- Post added at 08:17 AM ---------- Previous post was at 08:17 AM ----------
Romeotamizh said:
Oh
Click to expand...
Click to collapse
Look in other sites bro for img files
Romeotamizh said:
Oh
---------- Post added at 08:17 AM ---------- Previous post was at 08:17 AM ----------
Look in other sites bro for img files
Click to expand...
Click to collapse
Hmm yaa, but at the moment no sites with for .img file for this phone. All sites point to this image only. Let's hope somebody posts. Thanks!
Mafioso said:
Hmm yaa, but at the moment no sites with for .img file for this phone. All sites point to this image only. Let's hope somebody posts. Thanks!
Click to expand...
Click to collapse
Ooh bro I'm happy to help but seriously i Duno about these kind of extensions hope u understand
Mafioso said:
I'm trying to root Infocus Epic 1, its a good budget phone with decent specs. Availability is only in India, not sure other regions. Anyway I'm having hard time to root it, since not much support is available. But so far, I have tried below things:
1. Tried to root with Kingroot, doesn't work .Probably because it is very new version of Marshmallow with Oct'16 patch level and kernel dated in dec 16.
2. Tried to generate scatter file via MTK Droid tool v2.5.3, after enable USB debugging in phone. The phone get detected in the tool, however create scatter file option in block map is disabled I've read somewhere, it might be due to MTK6797 (Helios x20) is quite new and is not yet fully supported by tool yet. Not sure if its true though. But if I can generate scatter file, I can extract phone's stock recovery via SPFlash tool readback to try a hand at porting twrp/cwm with some help..
3. Downloaded stock Infocus Epic 1 firmware in hope for recovering stock recovery.img or MTK scatter file, however on unpacking the firmware package, I found it contains unknown image file of nb0 extension which is it to be flashed via SUT Tool. Not sure how to unpack this file
Any more ideas, how can i atleast start with my quest to root/put custom recovery on this phone ? @Romeotamizh Pls help.
Click to expand...
Click to collapse
I can give u stock recovery of epic 1..
mujammil786 said:
I can give u stock recovery of epic 1..
Click to expand...
Click to collapse
how bro, are you able to get it via SPFlash tool readback option or are you able to unpack the nb0 file ?
Anyway you should post it here, somebody else might pick it up and build twrp for it. At the moment, I'm stuck with SPFlash tool unable to readback my phone as stated above , doubt i would be able to flash anything to test
Mafioso said:
how bro, are you able to get it via SPFlash tool readback option or are you able to unpack the nb0 file ?
Anyway you should post it here, somebody else might pick it up and build twrp for it. At the moment, I'm stuck with SPFlash tool unable to readback my phone as stated above , doubt i would be able to flash anything to test
Click to expand...
Click to collapse
I was able to extract it from last update zip
---------- Post added at 04:45 PM ---------- Previous post was at 04:33 PM ----------
Epic 1 stock recovery
https://drive.google.com/file/d/0B4FNo4vddleCNmpwcS1hS3FLam8/view?usp=drivesdk
mujammil786 said:
I was able to extract it from last update zip
Click to expand...
Click to collapse
ok I see, please post it here. I can update it in the first post. Might be useful for anyone willing to develop for this phone.
Also did you try to read-back the phone via SPFlash tool ? I'm running into issues, but maybe i'm not doing something correctly. Might be you will have better luck.
Mafioso said:
ok I see, please post it here. I can update it in the first post. Might be useful for anyone willing to develop for this phone.
Also did you try to read-back the phone via SPFlash tool ? I'm running into issues, but maybe i'm not doing something correctly. Might be you will have better luck.
Click to expand...
Click to collapse
Well i tried but i got ctrl device error ,btw i have uploaded stock recovery
mujammil786 said:
Well i tried but i got ctrl device error ,btw i have uploaded stock recovery
Click to expand...
Click to collapse
thanks, updated first post.
Mafioso said:
thanks, updated first post.
Click to expand...
Click to collapse
Thanks let's hope for best
I like this phone and the only thing lacking is Root, Hope someone will do it
I hope so too. However, it seems its not that straight forward anymore i.e. communicating with SPFlash tool on newer MTK chipsets. I was going through guides for LeTV x620 (also with MT6797), not sure but it seems they require authentication file now for the process, which might not be available for our phone.
I already tried all the other download agents like DA_PL.bin, DA_PL_High.bin, DA_BR.bin in flash tool through which this LeTV is able to communicate, it's same error for us with all.
Also other curious thing, I was unable to run any fastboot commands on this phone. The phone gets detected in fastboot when put in fastboot mode (vol - + power) i.e. I get output on fastboot devices.
However If i try to run any commands like fastboot oem get-bootinfo or fastboot oem device-info I get error message remote command unknown
Mafioso said:
I hope so too. However, it seems its not that straight forward anymore i.e. communicating with SPFlash tool on newer MTK chipsets. I was going through guides for LeTV x620 (also with MT6797), not sure but it seems they require authentication file now for the process, which might not be available for our phone.
I already tried all the other download agents like DA_PL.bin, DA_PL_High.bin, DA_BR.bin in flash tool through which this LeTV is able to communicate, it's same error for us with all.
Also other curious thing, I was unable to run any fastboot commands on this phone. The phone gets detected in fastboot when put in fastboot mode (vol - + power) i.e. I get output on fastboot devices.
However If i try to run any commands like fastboot oem get-bootinfo or fastboot oem device-info I get error message remote command unknown
Click to expand...
Click to collapse
My device does not get detect in fastboot can u show me screen shot of command u are trying....
mujammil786 said:
My device does not get detect in fastboot can u show me screen shot of command u are trying....
Click to expand...
Click to collapse
If it's not detected maybe its related to your drivers. I've installed the following drivers
1. Try installing the Phone F Driver (from phone CD-emulation upon connecting)
2. MTK Driver Auto Installer v5.1632.00 (you can get from needrom)
3. Minimal ADB and Fastboot installer v.1.4.2 (from xda)
Run cmd as administrator:
adb reboot bootloader
When phone reboots in fastboot mode
fastboot devices
You should see your phone being detected from above.
Mafioso said:
If it's not detected maybe its related to your drivers. I've installed the following drivers
1. Try installing the Phone F Driver (from phone CD-emulation upon connecting)
2. MTK Driver Auto Installer v5.1632.00 (you can get from needrom)
3. Minimal ADB and Fastboot installer v.1.4.2 (from xda)
Run cmd as administrator:
adb reboot bootloader
When phone reboots in fastboot mode
fastboot devices
You should see your phone being detected from above.
Click to expand...
Click to collapse
Ok will try thanx
bootloder get unlocked and locked too
ok so phone get detected in fastboot mode:victory: .was able to lock and unlock boot loader but without custom recovery it is no useful for us.
unlocked bootloader.
tried flashing Vernee_Apollo_Lite_P6(same spec. as epic 1) twrp recovery.
flashing done but after flashing phone refused to boot.
flashed stock recovery from update zip.
locked bootloader.
phone booted but erased internal memory after boot.
---------- Post added at 11:47 AM ---------- Previous post was at 11:44 AM ----------
do you know any guide for making twrp and i think phone will not boot if it detect any change in system partition i think
Hello all,
First of all the story.
I used the script to rebrand, it has a fail but the phone still working.
One evening, i decided to wipe all by twrp and re run the unbrand script..... that was a huge error, the phone boot but boot loop, and after, the script stuck an no recognise the twrp on the phone.
Tried lot of things like flashing recovery etc in fastboot but nothing else happen than a boot and a black screen with nav bar only.
At this point i think the problem is that i was unable to flash cust.img with fastboot
Whad did I Do?
(Bootloarder must be unlock)
1st: Crying.
2nd: read tons of things on XDA
3rd: Try to re run the script but fail because the phone was still rooted.
4th: Crying
5th: Read lot of other things on XDA
6th: this is the good IDEA
7th: Download Huawei firmware finder
8th: Download Huawei Multitool
9th: Download Huawei Update Extractor
10th: download by the tool the full OTA firmware and dependencies (in my case VTR-L09C432)
11th: extract the update.app (chose "other" for phone model) from the big "update.zip" dowloaded before an put it in a folder of your choice
12th: extract the update.app from the "update_all_hw_xxx" dowloaded before an put it in other folders, just incase of files could have the same names (not sure of it)
13th: run Huawei Multitool (il will create a folder in the path of where the app is when you click, the folder you need is "unbrick")
14th: choose 6 on Huawei multi tool, it will show you what img's you need, and you need everthing exept data.img (the cus.img is in folder wehre you extract update_all_hw_xxx) in "unbrick" folder -> Place the .img needed in the "unbrick" folder (very important)
15th: boot your phone in bootloader mode (phone off, vol-down+plug USB)
16th: clic the button to launch procedure (press N)
17th: have a coffee during the upload it'll ask to reboot
18th: If the problem is solved: cool, stop here
IF NOT: shutdown the phone
19th: Go in classic recovery: Phone off, Vol-Up + Plug USB, when huawei logo stop pressing vol-up
DO NOT BOOT eRecovery, it will not help
20th: in classic recovery do factory reset AND cache reset
21th Reboot
You can relock your bootloader if you want with your code.
The only thing i don't know to do and if someone can telle me is, before the flash of every things or at a moment, if i can flash via ADB the OEM info for an official bootloader relock.
Thx to @mankindtw, @worstenbrood and @inside!out
Hope it will help, it work for me.
edit: can an admin put my title in bold?
Like the Parts with crying ?
Can you create a easy easy 1 click installer for the unbrand Script? ?
StonyD said:
Like the Parts with crying
Can you create a easy easy 1 click installer for the unbrand Script?
Click to expand...
Click to collapse
Unfortunately not, i'm not a dev, i don't have the knowledge......
Maybe one day i'll try
Hi thanks for sharing your experience.
I want just to ask some questions :
Where to place all folders that you talked about ? Directory?
What you mean by chose phone model ? In that new folder ?
The brick folder that will appear within huawei multitool folder ? I saw just unbrick folder.
Thanks.
dxkernel said:
Hi thanks for sharing your experience.
I want just to ask some questions :
Where to place all folders that you talked about ? Directory?
What you mean by chose phone model ? In that new folder ?
The brick folder that will appear within huawei multitool folder ? I saw just unbrick folder.
Thanks.
Click to expand...
Click to collapse
When you download the 3 files of the firmware, place them where you want.
When you lauchn Huawei Multitool, it will create the "unbrick" folder in the Huawei Multitool folder (my bad) not "brick", i update the first post.
When you use Huawei Update Extractor, you have choices for type of firmware, chose other.
help anyone i need the cust file for the p10 plus
i dont understand where im supposed to get the file
Hi, i am a bit confused.
I download all 3 files with rhe firmware tool. But then i got lost. Can you help me please?
Thanks
[email protected] said:
help anyone i need the cust file for the p10 plus
i dont understand where im supposed to get the file
Click to expand...
Click to collapse
It's in one of the ZIP (680mo in my memory)
Hello. Your post has been very helpful, after hours I've now managed to make some progress. All seems to have gone well after following your instructions, however at the end I'm unable to do a factory reset. At most it gets to 6% then fails. Any ideas on what may be going on?
I'm starting to think the phone may be beyond saving, all for one stupid mistake while rooting .
I can't find "other" or "other model" folder.
Thanks
aalmeida1972 said:
I can't find "other" or "other model" folder.
Thanks
Click to expand...
Click to collapse
It's the default option in the firmware extractor, i add the precision in case of
My bad, the explanation was not clear, i modified it.
From my french mind to english, sometimes a little bit difficult....
DidymusNoble said:
Hello. Your post has been very helpful, after hours I've now managed to make some progress. All seems to have gone well after following your instructions, however at the end I'm unable to do a factory reset. At most it gets to 6% then fails. Any ideas on what may be going on?
I'm starting to think the phone may be beyond saving, all for one stupid mistake while rooting .
Click to expand...
Click to collapse
Did you flash the two recoverys ? Can You still access to twrp?
If twrp still here use it to erase system partition
In fastoboot u can do It too
Follow these steps to :
1-Go to recovery option hold the power and volume button at same time .
2-then go advanced option.
3-Its time to factory reset your phone .
4-Finally Rebort your device and waite few seconds.
4-
Any ideas what I should do if my phone still will not reboot please ?
I'm still crying
I have a canada version of vtr-09 p10, and I dont know my firmware number I couldn't find my firmware in that software, please tell me what can I do.
---------- Post added at 09:12 AM ---------- Previous post was at 09:09 AM ----------
jimmygarison said:
Follow these steps to :
1-Go to recovery option hold the power and volume button at same time .
2-then go advanced option.
3-Its time to factory reset your phone .
4-Finally Rebort your device and waite few seconds.
4-
Click to expand...
Click to collapse
omg, how do you do that? you mean a advanced mode is in recovery mode or erecovery mode? I brought p10 at bell, I just couldnt find its firmware number.
ive done everything in this thread. the multitool installer finished without errors, then i did vol up + vol down + power, and it froze at 5 percent "installing update" then entered a reboot loop. then i tried a factory reset with vol up + power and it stoped at 25 percent.
Using the multi-tool
inoxas said:
Hello all,
First of all the story.
I used the script to rebrand, it has a fail but the phone still working.
One evening, i decided to wipe all by twrp and re run the unbrand script..... that was a huge error, the phone boot but boot loop, and after, the script stuck an no recognise the twrp on the phone.
Tried lot of things like flashing recovery etc in fastboot but nothing else happen than a boot and a black screen with nav bar only.
At this point i think the problem is that i was unable to flash cust.img with fastboot
Whad did I Do?
(Bootloarder must be unlock)
1st: Crying.
2nd: read tons of things on XDA
3rd: Try to re run the script but fail because the phone was still rooted.
4th: Crying
5th: Read lot of other things on XDA
6th: this is the good IDEA
7th: Download Huawei firmware finder
8th: Download Huawei Multitool
9th: Download Huawei Update Extractor
10th: download by the tool the full OTA firmware and dependencies (in my case VTR-L09C432)
11th: extract the update.app (chose "other" for phone model) from the big "update.zip" dowloaded before an put it in a folder of your choice
12th: extract the update.app from the "update_all_hw_xxx" dowloaded before an put it in other folders, just incase of files could have the same names (not sure of it)
13th: run Huawei Multitool (il will create a folder in the path of where the app is when you click, the folder you need is "unbrick")
14th: choose 6 on Huawei multi tool, it will show you what img's you need, and you need everthing exept data.img (the cus.img is in folder wehre you extract update_all_hw_xxx) in "unbrick" folder -> Place the .img needed in the "unbrick" folder (very important)
15th: boot your phone in bootloader mode (phone off, vol-down+plug USB)
16th: clic the button to launch procedure (press N)
17th: have a coffee during the upload it'll ask to reboot
18th: If the problem is solved: cool, stop here
IF NOT: shutdown the phone
19th: Go in classic recovery: Phone off, Vol-Up + Plug USB, when huawei logo stop pressing vol-up
DO NOT BOOT eRecovery, it will not help
20th: in classic recovery do factory reset AND cache reset
21th Reboot
You can relock your bootloader if you want with your code.
The only thing i don't know to do and if someone can telle me is, before the flash of every things or at a moment, if i can flash via ADB the OEM info for an official bootloader relock.
Thx to @mankindtw, @worstenbrood and @inside!out
Hope it will help, it work for me.
edit: can an admin put my title in bold?
Click to expand...
Click to collapse
Can you please tell me what option 6 is on the multi-tool. Do I drag files into the unbrick folder?
Pombal81 said:
Can you please tell me what option 6 is on the multi-tool. Do I drag files into the unbrick folder?
Click to expand...
Click to collapse
opt 6 is in my memory "unbrick" or recover.
You have to put all the .img files needed exept data.img that is not possible to heve because this file is on your phone and encrypted.
Thanks for helping me, how can I tell what .img files are needed? I can't see anything that will tell me this?
---------- Post added at 04:13 PM ---------- Previous post was at 04:04 PM ----------
I'm sorry, I'm a bit confused on the intructions:-
I downloaded the full update zip file from the url using the firmware finder, there was another url link that came up called full/public/update - do I need the zip for this too?
I extracted the update zip to a folder and then extracted the update.app file using the Huawei update extractor.
Now I have a very long list of .img files in the extractor and I'm not clear what I need to do next i.e do I move them all into the unbrick folder on the tool?
Hi, I have since been able to extract the right files for the multi-tool. I extracted them again from the extractor. I now have placed them into the unbrick file. My problem now is that I can't run the tool - when I open the multi-tool .bat file its asking for a proxy port, where can I find this?
Hi,(I am spanish sorry about my english)
after a long time searching how to rollback finally I have found the way thanking to this thread https://forum.xda-developers.com/p10/how-to/success-downgrade-oreo-to-nougat-t3729659.
In the thread the way to rollback isn't very extended explained so i decided to create mine and explain easy.
My phone is a Huawei P10 L29c432B.... .
Steps:
1- Download HWOTA8 from--https://drive.google.com/file/d/0B2D9GdWntw69U3N2aDEzZjY2S1E/view
2-Download Firmare L29C900B217 or L09C900B217 depending your model (only are 2 downloads) fromhttp://pro-teammt.ru/firmware-database/?firmware_model=VTR-L29c900&firmware_page=0
3-Delete the row "echo - - update_package...... update_data public. zip..." from the file "META-INF>com>google>android>update-binary" from hwota8_update.zip from the downloaded folder HWOTA8.
4. Create HWOTA8 folder and copy the following files: hwota8_update and MHA_RECOVERY8_NoCheck.img (from HWOTA8 folder), and the downloaded firmware files. After copu the firmware files you have to rename them one has to be named "update.zip" and the other one "update_all_hw.zip" (don't write.zip extension).
5- Now you have to rewrite the recovery with twrp, for that you have to go to fastbood (VOL- and Power) mode and connect to the pc. Then go to Uncompresed HWOTA8 folder and run "Replace_Recovery.bat" after that you will have the recovery TWRP installed.
6- Finally you have to to go to recovery pressing VOL+ and power button then go to Install adn search sd_external and inside HWOTA8 folder from sd card install "hwota8_update.zip". The device will resboot and start installing the nougat rom, but after that you will have to rebrand to L29c432.... to unlock all the functions.
That's all now you will have your device rollbacked from Oreo to Nougat.
Hi!
Thx for this guid, it seems to be clearly and good to understand! I have only one problem: i can not find the row "echo - - update_package...... update_data public. zip..." from the file "META-INF>com>google>android>update-binary" from hwota8_update.zip from the downloaded folder HWOTA8 for changing... ???
I tried with notepad++, but i can not do this... How did you get this step working?
Thx a lot!
stefan.irmen said:
Hi!
Thx for this guid, it seems to be clearly and good to understand! I have only one problem: i can not find the row "echo - - update_package...... update_data public. zip..." from the file "META-INF>com>google>android>update-binary" from hwota8_update.zip from the downloaded folder HWOTA8 for changing...
I tried with notepad++, but i can not do this... How did you get this step working?
Thx a lot!
Click to expand...
Click to collapse
You have to unzip the hwota8_update.zip file into another location, edit the extracted update_binary file and then repack the zip. The update_binary file in HWOTA8_<date>.zip is a binary file and shouldn't be edited with a text editor.
txonan said:
Hi,(I am spanish sorry about my english)
5- Now you have to rewrite the recovery with twrp, for that you have to go to fastbood (VOL- and Power) mode and connect to the pc. Then go to Uncompresed HWOTA8 folder and run "Replace_Recovery.bat" after that you will have the recovery TWRP installed.
6- Finally you have to to go to recovery pressing VOL+ and power button then go to Install adn search sd_external and inside HWOTA8 folder from sd card install "hwota8_update.zip". The device will resboot and start installing the nougat rom, but after that you will have to rebrand to L29c432.... to unlock all the functions.
That's all now you will have your device rollbacked from Oreo to Nougat.
Click to expand...
Click to collapse
hi there guys, i'm having problems with step number 5, i do rewrite twrp with that command, everything seems ok, have no errors, but can't go ionto TWRP like it isn't installed.
i can't run TWRP, can you please help?
pale1505 said:
hi there guys, i'm having problems with step number 5, i do rewrite twrp with that command, everything seems ok, have no errors, but can't go ionto TWRP like it isn't installed.
i can't run TWRP, can you please help?
Click to expand...
Click to collapse
First few times i had the same problem...
When the phone is off an you will hold "Power" and "Volume+" button to boot into TWRP, just hold "Volume+" after phone is vibrating... Then you will boot into TWRP...
stefan.irmen said:
First few times i had the same problem...
When the phone is off an you will hold "Power" and "Volume+" button to boot into TWRP, just hold "Volume+" after phone is vibrating... Then you will boot into TWRP...
Click to expand...
Click to collapse
You have to reinstall twrp and then continue with the steps.
pale1505 said:
hi there guys, i'm having problems with step number 5, i do rewrite twrp with that command, everything seems ok, have no errors, but can't go ionto TWRP like it isn't installed.
i can't run TWRP, can you please help?
Click to expand...
Click to collapse
The fact is that the recovery proccess is a **** in this model. Try to power completely off the phone and the Pess POWER + VOL+ when you feel the phone vibrates retire the press of power button and still pressing VOL+ button by this way sometime it goes ok. If TWRP load go ahead with the followings steps.
Other way it to reinstall again TWRP untill it loads.
Let me know if you suceed, good luck.
4. Create HWOTA8 folder and copy the following files: hwota8_update and MHA_RECOVERY8_NoCheck.img (from HWOTA8 folder), and the downloaded firmware files. After copu the firmware files you have to rename them one has to be named "update.zip" and the other one "update_all_hw.zip" (don't write.zip extension).
2. Download Firmare L29C900B217 or L09C900B217 depending your model (only are 2 downloads) fromhttp://pro-teammt.ru/firmware-database/?firmware_model=VTR-L29c900&firmware_page=0
non-functional link?
How exactly is it to be?
txonan said:
The fact is that the recovery proccess is a **** in this model. Try to power completely off the phone and the Pess POWER + VOL+ when you feel the phone vibrates retire the press of power button and still pressing VOL+ button by this way sometime it goes ok. If TWRP load go ahead with the followings steps.
Other way it to reinstall again TWRP untill it loads.
Let me know if you suceed, good luck.
Click to expand...
Click to collapse
just to let you know that nothing worked,
went to a shop, they tried everything, uploaded older firmwares, but after that the phone died, only black screen, couldn't even switch it on.
warranty did the trick
the guys replaced the mainboard, nothing else helped
so i'm waiting now for the official update
Good day! Can I use this method for installing Official Oreo from Beta? What I would like to do, is skip the deleting of row then just flash the twrp and continue with installation process.
I'm on VTR-L29C636B361.
I would like to rollback to Nougat, for root reasons. I'm trying to follow this method, but I'm not able to find the right files. All I succeded to find is the "update.zip", from Firmware Finder website, but no signs regarding others mentioned ("update_all_hw.zip"). Where can I dowload the right files?
Moreover: I flashed TWRP 3.2.1. I would like to go back on stock recovery, but again I'm facing a lot of problems. I would like to extract from update.app I have (from "update.zip" above mentioned), but HuaweiUpdateExtractor gives me a lot of error. Any help?
Thanks!
pdbc said:
I'm on VTR-L29C636B361.
I would like to rollback to Nougat, for root reasons. I'm trying to follow this method, but I'm not able to find the right files. All I succeded to find is the "update.zip", from Firmware Finder website, but no signs regarding others mentioned ("update_all_hw.zip"). Where can I dowload the right files?
Moreover: I flashed TWRP 3.2.1. I would like to go back on stock recovery, but again I'm facing a lot of problems. I would like to extract from update.app I have (from "update.zip" above mentioned), but HuaweiUpdateExtractor gives me a lot of error. Any help?
Thanks!
Click to expand...
Click to collapse
At the HWFF website the link leads you to you need to click the "filelist" (not only the "update"), that will give you links to all the files needed.
For the rest I am not sure, would also like to get back to the stock recovery but so far found no way to do so...
_Nostromo_ said:
At the HWFF website the link leads you to you need to click the "filelist" (not only the "update"), that will give you links to all the files needed.
For the rest I am not sure, would also like to get back to the stock recovery but so far found no way to do so...
Click to expand...
Click to collapse
I can give you recovery.img and recovery2.img for VTR-L29C636B162. I flashed this and then roll back to Nougat (B172) with FF.
pdbc said:
I can give you recovery.img and recovery2.img for VTR-L29C636B162. I flashed this and then roll back to Nougat (B172) with FF.
Click to expand...
Click to collapse
Thanks a lot for your offer, however unfortunately my model is VTR-L09 so I better do not mess it even more...
how do i edit update-binary? Just odd things comes up with notepad++
Question
txonan said:
Hi,(I am spanish sorry about my english)
after a long time searching how to rollback finally I have found the way thanking to this thread https://forum.xda-developers.com/p10/how-to/success-downgrade-oreo-to-nougat-t3729659.
In the thread the way to rollback isn't very extended explained so i decided to create mine and explain easy.
My phone is a Huawei P10 L29c432B.... .
Steps:
1- Download HWOTA8 from--https://drive.google.com/file/d/0B2D9GdWntw69U3N2aDEzZjY2S1E/view
2-Download Firmare L29C900B217 or L09C900B217 depending your model (only are 2 downloads) fromhttp://pro-teammt.ru/firmware-database/?firmware_model=VTR-L29c900&firmware_page=0
3-Delete the row "echo - - update_package...... update_data public. zip..." from the file "META-INF>com>google>android>update-binary" from hwota8_update.zip from the downloaded folder HWOTA8.
4. Create HWOTA8 folder and copy the following files: hwota8_update and MHA_RECOVERY8_NoCheck.img (from HWOTA8 folder), and the downloaded firmware files. After copu the firmware files you have to rename them one has to be named "update.zip" and the other one "update_all_hw.zip" (don't write.zip extension).
5- Now you have to rewrite the recovery with twrp, for that you have to go to fastbood (VOL- and Power) mode and connect to the pc. Then go to Uncompresed HWOTA8 folder and run "Replace_Recovery.bat" after that you will have the recovery TWRP installed.
6- Finally you have to to go to recovery pressing VOL+ and power button then go to Install adn search sd_external and inside HWOTA8 folder from sd card install "hwota8_update.zip". The device will resboot and start installing the nougat rom, but after that you will have to rebrand to L29c432.... to unlock all the functions.
That's all now you will have your device rollbacked from Oreo to Nougat.
Click to expand...
Click to collapse
Hi, I have one question
Your phone was VTR-L29 C432 and you used the firmware of VTR-L29 C900, so can I use the C900 in any version to rollback and after that, what would be my version? C432 or C900?
I'm asking because for some reason I have VTR-L09 8.0.0.046(04VT) and I want to rollback, then rebrand and finally upgrade to VTR-L29 C432 with a custom kernel.
Thanks a lot!
This guide realy work ??
hello, I test by cons I have a problem, once flash hwota8_update.zip, it tries to restart in recovery and redémre on oreo, a solution?
Hello, I have a problem in the rocovery that I flash wota8_update.zip I have E: unknown command [errno]
Updater process ended with ERROR: 9
Error installing zip file '/external_sd/HWOTA8/update.zip
Maybe this is a silly question. Do we need to change the recovery file since MHA is a code name for MATE 9. P10 use VTR. Is it still usable?
This is basically a copy of my Z380M TWRP thread adopted for the ZenPad 10. I decided to start a new one since the OP of justshaun's original recovery/rooting thread has gone stale, even as I had posted several new releases of TWRP over the months. Its instructions are also a little outdated. I've also compiled a version for the new Z301M(F) models and needed a place to post it. This is where I will be posting TWRP updates from now on.
In addition to this thread, referring to the Z380M TWRP thread and the original Z300M thread (links above) may be helpful. These models share the same hardware and software base, so most things that apply to one tablet also apply to the others.
DISCLAIMER
As usual, you do anything described in this post at your own risk. No one but you is responsible for any data loss, bricking or damage of your device.
REQUIREMENTS
Windows or Linux PC
SP Flash Tool version 5.1532 (only this version will bypass security checks)
MediaTek VCOM drivers (available through Windows Update)
ZenPad 10 scatter file for SPFT, attached (choose the one for your tablet)
Recovery image, attached (choose the one for your tablet)
ZenPad Z300M, Z301M or Z301MF tablet upgraded to Android N
This won't be a guide on how to use SP Flash Tool. There are plenty of good guides out there like this one on how to set up drivers, load scatter files, flash and make backups with SP Flash Tool. If you're not familiar with this software or how to flash MediaTek devices in general, please do your research before attempting this. I will just get straight to the specifics about the ZenPad 10.
FIRST TIME INSTALLATION
For a locked bootloader:
At this point you should have your tablet powered off, the drivers installed, all of your data backed up, and SP Flash Tool v5.1532's Download tab open and loaded with the tablet's scatter file. Open the download agent file DA_PL.bin, replacing the default MTK_AllInOne_DA.bin. (You can use the AllInOne DA if you want, but the procedure involves extra steps as described below.) Load the extracted TWRP recovery image for your device (twrp-3.2.1-0-z30*m.img) under the recovery partition line in the partition table. Click the Download button inside SPFT. Now just connect the USB cable to your tablet and your computer's USB port. It should start the download process automatically and disconnect when finished.
Alternative Method:
If you're using MTK_AllInOne_DA.bin, you have to hold the Volume Up key as you insert the cable, which puts the device into an emergency download mode. In addition, you will need to have the stock preloader*.bin file loaded inside SPFT for it to be able to communicate with your tablet. The preloader is available inside the official zip file download. Do not flash the preloader (untick the box) or any partitions other than recovery. You just need to have a valid bin file selected under the Preloader line.
For an unlocked bootloader:
If you have used the Asus unlock tool to unlock your device, you will still not be able to use fastboot flash to install a custom recovery. However, you can do a "hot boot" or a tethered boot of TWRP. This method doesn't require SP Flash Tool. Download the TWRP image, put your tablet in fastboot mode and connect to PC. Then run this command to boot TWRP dynamically:
fastboot boot twrp-3.2.1-0-z30*m.img
Once inside TWRP, flash twrp-3.2.1-0-z30*m.img to Recovery using Install -> Install Image. Then reboot to recovery. You may be able to use TWRP in the tethered boot mode, but that could result in glitches due to different parameters passed by the bootloader to the kernel. That's why flashing is recommended.
To update from your installed TWRP version to a new one, just transfer the image to your tablet, then boot to TWRP and install it by going to Install -> Install Image and flashing to Recovery.
START RECOVERY
With the tablet powered off, hold the Volume Up and Power keys together until you get to a menu where you can select "recovery". On the Z301M/Z301MF, that option is labeled Factory Reset. Use Vol. Up to scroll and Vol. Dn to select. If you have a locked bootloader, it will show a Yellow State message because the recovery is not signed by the OEM. Just press volume up to boot it. On the welcome screen of TWRP it will ask you about modifying the system partition, I suggest you go with Keep System Read-only. Doing otherwise will complicate your OTA updates.
WARNING: Never start the stock recovery from the bootloader menu on this device. It is programmed by the bootloader to instantly wipe your data without any warning. Also, be aware that Android installs the stock recovery at every normal boot cycle. So you either have to flash the TWRP every time you want to run it, or disable the automatic recovery installation in the stock firmware. Any kind of mod to the boot image will prevent the automatic recovery installation. If you're not sure which recovery you have installed, you can always do a 'adb reboot recovery' from Android without risk of data loss.
WARNING 2: Make sure you use the correct scatter file for your device (i.e. don't mix up the Z300 and Z301 files). For the initial flash, there is no check for scatter file correctness. If you use the wrong one, SP Flash Tool will alter and lock your GPT to that scatter file layout, possibly bricking your device. It will not be easy to restore it. Flashing with the correct scatter file later on will not work because Flash Tool will not allow you to use a different file than the one you used initially.
What works: Basically everything... access to major partitions, decrypted userdata partition, decrypted adoptable storage, external SD card, ADB, USB-OTG, touch interface, splash screen, installing stock Asus OTA/web FW updates
What doesn't work: (no known problems yet, but please report any)
Not guaranteed to work: factory reset
DOWNLOAD
SP Flash Tool v5.1532
Z300M Scatter file for all storage sizes (right click, Save link as...) -- do not use for other models
Z300M TWRP 3.2.1-0 image -- updated March 15, 2018
Z301M(F) series Scatter file for all storage sizes (right click, Save link as...) -- do not use for Z300M or other devices
Z301M TWRP 3.2.1-0 image -- updated March 13, 2018
Z301MF TWRP 3.2.3-0 image -- updated August 29, 2018
Development and experimental files
Source code
P.S. The thanks button doesn't bite.
Heya, thanks for the new thread..
Stupid question(coming from Samsung flashing)
Ive got Zenpad S3 10 P027, is this TRWP not ideal for this?
Currently, have some su (root) issues. Recovery shows Android icon chest with ! and says "No Command"
When running su in Terminal ADB via PC, says command not recognized.
Looks like I need to reflash recovery. When in TRWP (launched via fastboot boot twrp on PC) I flashed stock recovery but had system mounted read only. Could that be the problem?
Bro, I think you need to do some more homework on root, su, dm-verity, mods, etc. and read the instructions more carefully before applying these hacks. You are making a lot of simple mistakes and ending up shooting yourself in the foot for it. I don't think there's anything wrong with the Z500 TWRP. It can handle installing the stock firmware just fine. The problem is elsewhere. The unlock tool also works fine in TWRP as well in my testing.
The No Command screen is normal. That's been answered many times... you need to hold power+vol. up (or down) to get to the menu. There is no way the stock recovery image can be broken and still boot up.
The su thing, IDK what the problem is, but I'm sure if you install Magisk Manager and make your own patched image from your currently installed firmware, and fastboot-boot with it, you will have su functionality. Just like what it says in the unlock tool instructions.
Lastly and most important, never mount system in read-write mode, as I've repeated several times and exactly as it says in the directions:
7. At the TWRP welcome screen, do not select to modify the system partition and touch Keep System Read-only instead. Doing otherwise will render your tablet unbootable.
8. Mount system in TWRP (in read-only mode)
Click to expand...
Click to collapse
The only time you can mount it in read-write mode is when you are absolutely sure you have disabled dm-verity in your boot image.
I've successfully installed TWRP on Z301M using the instructions from the first post, but then I somehow managed to lose the system. Yes, I should have backed up like the OP suggests.
I thought I should be able to reinstall the original firmware downloaded from Asus (e.g. UL-ASUS_P028_1-WW-3.3.12.0-user.zip) but both the 'adb sideload' method and the TWRP failed to install that firmware zip. My device looks bricked. The only thing I can do is to boot into TWRP (I actually need to select Factory Reset on the bootloader screen to get into TWRP). The folder 'system' is empty.
Can anyone suggest what I am doing wrong when trying to restore the Asus firmware?
When I try to sideload the zip, setting TWRP in the sideload mode, the computer begins uploading but after a few seconds gives the message "Total xfer: 0.01x" and stops, while Android errors with "set boot part fail. can not open misc-sd".
When I install the firmware zip from TWRP it also starts installing fine but shortly gives the same error "set boot part fail. can not open misc-sd".
Thanks
@ahacker, first of all, thank you for the feedback on the Z301M platform. You are literally the first person to have said anything about that version of TWRP.
To see the files on system, you first have to mount the system partition. Did you do that? If not, I suggest mounting it read-only. If there was any corruption on it, then reinstalling the firmware should have fixed it. The "misc-sd" errors are normal. Pretty sure they happen on stock recovery too. The stock firmware does not have dm-verity enabled, so letting TWRP modify system to prevent overwriting recovery should not have caused any problems.
At which point did it stop booting? Also, did you use the scatter file from first post? And can you tell me if the touch screen works fine in TWRP on your tablet?
I'm not sure what the deal is with adb sideload. I don't think I've ever actually tried it....
diplomatic, thanks for replying!
diplomatic said:
[MENTION=4776997]
To see the files on system, you first have to mount the system partition. Did you do that?
Click to expand...
Click to collapse
I do mount the system partition. It appears empty. When I reboot into system TWRP says that the OS is not installed.
I don't remember the details of how I lost the system partition. First time I entered into TWRP it asked for a password, probably to mount some partition. I pressed cancel or something. Then I might have cleaned the caches. But I am sure I haven't wiped system. I might have pressed Factory Reset somewhere, because I don't have any data yet on the new tablet.
I would indeed try to mount the system read only. This is not the first Android system I rooted (maybe fifth), and I was always able to restore the system either from sideload or recovery. But here it seems Asus is making us jump extra hoops to do that.
diplomatic said:
[MENTION=4776997]
Reinstalling the firmware should have fixed it.
Click to expand...
Click to collapse
That seems to be my main problem now. I cannot reinstall the Asus firmware. It may look like I might be installing a wrong version, but I am positive that I have Z301M tablet. This is what I bought and what the boot-loader says. I download Z301M firmware from the Asus website (e.g.). So it must be a correct firmware.
diplomatic said:
[MENTION=4776997]
The "misc-sd" errors are normal. Pretty sure they happen on stock recovery too. The stock firmware does not have dm-verity enabled, so letting TWRP modify system to prevent overwriting recovery should not have caused any problems.
Click to expand...
Click to collapse
Thank you for the information.
diplomatic said:
[MENTION=4776997]
Also, did you use the scatter file from first post? Does the touch screen work fine in TWRP on that tablet?
Click to expand...
Click to collapse
Yes. I found that to be the only scatter file that worked. I tried scatter.txt from the firmware zip, but the Flash Tool refuses tio pick it up. TWRP seems to be working fine with touches working as expected.
diplomatic said:
[MENTION=4776997]
I'm not sure what the deal is with adb sideload. I don't think I've ever actually tried it....
Click to expand...
Click to collapse
This is the unbricking method described here. It probably does the same thing as the "Install Zip" from recovery, because the errors that both methods give are the same.
---------- Post added at 01:19 AM ---------- Previous post was at 12:57 AM ----------
Now system refuses to mount
ahacker said:
I don't remember the details of how I lost the system partition. First time I entered into TWRP it asked for a password, probably to mount some partition. I pressed cancel or something. Then I might have cleaned the caches. But I am sure I haven't wiped system. I might have pressed Factory Reset somewhere, because I don't have any data yet on the new tablet.
Click to expand...
Click to collapse
Er, the password should have been for decrypting your userdata. If you didn't have one set up, there might be something wrong there.... Or possibly just unformatted.
ahacker said:
That seems to be my main problem now. I cannot reinstall the Asus firmware. It may look like I might be installing a wrong version, but I am positive that I have Z301M tablet. This is what I bought and what the boot-loader says. I download Z301M firmware from the Asus website (e.g.). So it must be a correct firmware.
Click to expand...
Click to collapse
Yeah, that has to be the right one. The installation script has to match the model name reported by the recovery. Otherwise it would simply abort.
ahacker said:
Yes. I found that to be the only scatter file that worked. I tried scatter.txt from the firmware zip, but the Flash Tool refuses tio pick it up. TWRP seems to be working fine with touches working as expected.
Click to expand...
Click to collapse
Great! Guess my kernel patch was on the dot and the partition layout has not changed from the Z300.
ahacker said:
This is the unbricking method described here. It probably does the same thing as the "Install Zip" from recovery, because the errors that both methods give are the same.
Click to expand...
Click to collapse
When you installed the zip, did you unmount system completely? BTW, when you mentioned the errors, the installation does keep going for like 5 to 10 minutes afterwards, right?
If you still can't resurrect it, please post or send me the recovery & kernel log that has your installation attempt.
diplomatic said:
When you installed the zip, did you unmount system completely? BTW, when you mentioned the errors, the installation does keep going for like 5 to 10 minutes afterwards, right?
Click to expand...
Click to collapse
I've tried both ways, with and without system mounted, a few times. The installation would fail after something like 5 seconds.
diplomatic said:
If you still can't resurrect it, please post or send me the recovery & kernel log that has your installation attempt.
Click to expand...
Click to collapse
I think I am giving up on this cheap tablet. I cannot even format it in the Flash Tool: it says "To format code area is forbidden on this phone". Asus is forbidding too much for me to ever buy it again. Attached the logs.
Thanks, diplomatic
OK, found the problem. Check your PMs, ahacker.
diplomatic said:
OK, found the problem. Check your PMs, ahacker.
Click to expand...
Click to collapse
I have replied (twice), but the reply does not appear in my Sent Items. I hope it has reached you. If not, I'll paste the reply here, if you don't mind.
i not understand... i have Asus ZenPad 10 LTE Z301MFL.. a root method has been released ???
@diplomatic
Would this be compatible with Z0310M ? can't find anything for this damn model...
Hi, NeBouse,
Are you sure you have the correct information? It looks like just a misspelling of Z301M, aka P028....
I have z301m.
One thing that was a surprise for me is that the TWRP recovery flashed with the method described in the original post does not stick. You have to flash it each time you use it. If you are like me this information is important, because the original recovery plainly wipes your data without asking or warning.
After you have flashed TWRP on the device, to go to the recovery mode you have to chose "Factory Reset" in the bootloader. Then it will complain about wrong OS, which is the sign that flashing TWRP worked; choose 'yes'. The first thing you should do in TWRP is a ful nandroid backup. (Not listening the OP's advice about backing up when Installing TWRP with a wrong scatter file almost cost me the device. Thankfully diplomatic managed to remotely fix my problem, probably spending a lot of his personal time. The scatter file in the original post is a correct one now.)
Creating a nandroid backup in TWRP takes unusually long time, I even once decided that it hanged. Taking long time, like 10-30 minutes, for a full backup is normal.
Asus Z300M , Magisk 16.3 (beta) and FW 5.3.19 WW now works!
z301m, WW-3.3.12.0 firmware
For rooting I've installed in TWRP Magisk v15.3 (diplomatic warned against 16.x, someone else against 15.4) - link.
Installed in TWRP xPosed framework 88.2 - link, and xPosed Installer apk from within Android - link.
So far, so good.
What I've found is that TWRP seems to have problems with external sd cards (lots of fs corruption). I found it safer to unmount by hand by unticking the sd card checkbox in "Mount". Not very conclusive about this though.
Thanks, ahacker. Good feedback. Although to be fair, I didn't say to avoid Magisk 16.x. I said 16.0. I'm pretty sure whatever bug it had is already fixed in the latest version.
Now that you've installed root, TWRP will stick around on the emmc. The stock recovery only gets installed if you have the original unpatched boot image on it. I mean, this is not unique to these devices. That's been standard Android functionality since some 4.x or 5.x version. And this is essentially what's in the warning on the OP.
The backup I'm talking about in the installation method is done with the SP Flash Tool readback function. That will pull the partition tables and your device's "metadata" that's unique to your unit. I don't think nandroid covers that...
Oh, and what is this SD corruption you're talking about? What file system is it formatted in? Have you checked your card for errors in Windows?
Asus releases so many difference Z301M model, so I am curious if this also works on Z301MF model?
Notice Z300MF has the MTK8163BA (or MTK8163A?) CPU model while Z301M uses : 8163B
Anyone tested that already? Thanks.
my zenpad 10 has frp lock. it this a solution to remove the frp lock?
Pls help how i flash original software via fastboot ?????