FIRMWARE MEDIAPAD ICS 4.0.3 HWMOD C232B005
Kernel: 3.0.8 ([email protected]_server) Thu Jun 7 17:50:45 CST 2012
Compiler: (gcc version 4.4.3 (GCC)) #1 SMP PREEMPT
Baseband: 314007 - Android: 4.0.3 - GAPPS: 4.0.4
Incremental Build: V100R002C002B010SP030
This is a modified copy of the official firmware released by Huawei C232B005 General Version (June 2012). It doesn't require running "sanix" patches nor modifications to the system partitions "boot.img"/"system.img".
As in the original, the zip file contains instructions on how to upgrade from a MicroSD memory card. The firmware contains updated GAPPS ICS 4.0.4 (gapps-ics-20120429-signed.zip).
It has been said several time however you know you will void your warranty by modifying your device.
I have tried these modified firmware several times on my MediaPad before rendering them available.
On "Androidiani.com", in the MediaPad forum, I have been releasing these same kind of modifications for the following firmwares:
C232B002, C167B003, C170B008, C170B009 and currently C232B005
I have to say thanks to many users on that forum for their contributions and suggestions.
Before you start the upgrade
Download the firmware ZIP file, unpack the file on your PC and copy the "dload" folder found in the archive on the external MicroSD card. In the same archive you will also find Huawei original PDF document in English explaining how to upgrade the device and a "readme.txt" file that lists version numbers of the various components of the firmware (kernel, baseband, build etc.).
Remember to use Huawei's "All Backup" (suggested) or similar tools to backup all the applications and data on the external MicroSD card before proceeding with the update. In this firmware it is possible to activate a remote Google backup of the applications installed from the Market using a personal Google account ("Setting -> Backup and reset -> Backup account").
Standard update method
Only copy the "dload" folder in your MicroSD card, reset the device by switching the device off (press "power" button for 10 sec). If the device doesn't start automatically again press the power button. If the update does not start repeat the operation and additionally keep pressing the Volume+ button (on the right).
Alternate update method
Use the phone application to dial the following number * # * # 2 8 4 6 5 7 9 # * # * then, from the menu that appears, select:
"Project Menu Act -> Upgrade -> SD Card Upgrade -> SD Card Upgrade External Storage".
For both methods
Follow the instructions on the device screen (in green), the complete update process will be about 10 minutes, then the device will reboot a couple of times, be patient and let the device be quiet a couple of minutes more before touching it (while updating the sim, sn, touch & coulometer firmware).
I always suggest executing a "Factory reset" after a firmware upgrade. You can do that from "Setting -> Backup & reset -> Factory data reset" and if possible also check the box related with the formatting of the device internal memory (after ensuring you have made a backup of all you may need).
IMPORTANT !!!
To avoid touching key partitions of the Android OS and the original firmware I decided to leave the duplicated "Gallery2" application (found in the "system" partition). For this reason, after the upgrade you will end up with two "Gallery" applications. Deactivate or remove the first one of the two, the one which is smaller in size. The second one has more options (Google+/PicasaWeb sync) than the one pre-installed by Huawei. Since the device is "rooted" any file manager capable of browsing folders with "root" privileges will be enough to perform the removal.
Informations
This firmware uses an alternate method to obtain "root" permissions on the MediaPad avoiding modifications to important parts of the original firmware ("boot" and "system"), at the same time it adds missing Huawei/Google applications and enable some of the functionalities that were not enabled in the original firmware.
Modifications have been applied exclusively to the device "cust" partition ("cust.img.ext4") all the remaining partitions and files have been left untouched compared to the originals Huawei ICS 4.0.3 firmware released 21 June (C232B005).
Updated:
all ICS Google Apps (gapps-ics-20120429-signed.zip)
modified permissions for "busybox" executable (755)
International language selected as "default" (English)
International wifi settings for channels (13)
Added:
Huawei applications missing in the official version
GenieWidget application included in newer gapps-ics
Removed:
"Huawei Input Method" add-on keyboard and all related Language Packs (42)
Gmail, Maps, Music2, PlusOne, Street, TagGoogle, Talkback, Youtube
Aldiko, Facebook, FoxitReader, Twitter, YozoOffice and related libraries
two space hungry games, Asphalt6, LGolf and related libraries
images and demo animations (media)
List of added/updated applications and their versions:
AccountAgent-1.1.17.apk
AllBackup-4.1.33.apk
HiDisk-3.0.21.apk
HwOUC-2.3.8.apk
PhoneFinder-2.2.0.apk
PushAgent-2.2.1.apk
Superuser-3.0.7.apk
List of functionalities added to this firmware:
"root" permissions, Superuser.apk, busybox v1.20.1, su v3.0.3.2
firmware updates from "Settings" (Huawei/Google components)
Google GenieWidget & Google Backup Transport functional
Huawei applications: All Backup, HiDisk, PhoneFinder
* FIRMWARE DOWNLOAD *
ZIP containing firmware and software (essential: huawei_apps + google_apps):
Download size: 258.649.399 bytes (247Mb) - md5: 8c8bac1094d7dcb87d959a3be1482f6f
MIRROR 1 (GameFront)
* HUAWEI KEYBOARD DOWNLOAD *
ZIP containing the new keyboard and 42 additional language packs (Huawei Input Method):
Download size: 16.266.684 bytes (15Mb) - md5: 22b4aeddd6c214ffc7e5ef753216d68b
MIRROR 1 (GameFront)
Have fun,
.:HWMOD:.
HWMOD Linux kernel 3.0.42 Overclocked + customizations update
This update replaces (overwrite) the "boot" and "cust" partitions of the device.
The update process should retain all installed applications and data.
To achieve "non destructive" update I used the same method used in OTA updates.
At the end of the update process the tablet will reboot once more after restoring the
serial number, sim/imei, firmwares for touch-screen and coulometer etc.
The update methods remain unchanged (no need to use "fastboot/adb"):
1) download the compressed ZIP archive and unpack it on your PC
2) copy the "dload" folder contained in the archive on the external SD card
3) restart the device and follow exactly the on-screen instructions (in yellow)
The "boot" contains the new kernel 3.0.42 Overclocked and the initialization "ramdisk".
The "cust" partition has been updated with the new "Superuser.apk", "su" and "busybox".
Inside the ZIP compressed archive you will find a "readme.txt" with expanded informations and instructions.
Credits to "arkusuma" for the modifications related to the touch screen driver and to "contributors/modders" on XDA.
* FIRMWARE DOWNLOAD (updated 2012/09/10) *
ZIP contains kernel (boot.img) and customization software (cust.img)
Size: 82.463.617 (∼80Mb) - md5: 05dc4f0a5aa564dc8f628659540bbb8d
MIRROR 1 (GameFront)
* HUAWEI KEYBOARD DOWNLOAD *
ZIP containing the new keyboard and 42 additional language packs (Huawei Input Method):
Download size: 16.266.684 bytes (15Mb) - md5: 22b4aeddd6c214ffc7e5ef753216d68b
MIRROR 1 (GameFront)
Have fun,
.:HWMOD:.
what modifications did you made?
441Excelsior said:
what modifications did you made?
Click to expand...
Click to collapse
Sorry for the short description, really, many more info are missing. I will do my best to update and translate asap the rest of what I have published on "Androidiani" forum.
Basically I have added "root" permissions, removed all the extra applications and updated the Google Apps to a newer version (gapps-20120429-signed.zip).
I also added a few missing Huawei utilities like AllBackup, HiDisk and PhoneFinder that were found on previous Huawei releases.
The method I used to add "root" permissions is a bit different than on other modified firmwares. I only changed "cust" partition to achieve that, all the other partitions have been left untouched as the originals from Huawei.
I probably trust Huawei developers a bit more than others
441Excelsior said:
what modifications did you made?
Click to expand...
Click to collapse
OK, I added the expected informations in the op.
I will add more info and corrections.
How bout the edge to.H/3G? In 002 when there's still stuck problem..
Sent from my SPH-D710 using Tapatalk 2
It should work in this firmware (also I haven't tried yet).
The problem you mentioned was already fixed in both Russian releases.
There are no known problems for the phone to switch between 3G <-> HDSPA.
no gmail in this release? Noticed it when i was to replace gmail apk with a modified one.
mangoman said:
no gmail in this release? Noticed it when i was to replace gmail apk with a modified one.
Click to expand...
Click to collapse
Right ... not there. Why include Gmail if you wanted to replace it anyway ?
It would have happened anyway at first update (if you decided to install it).
I have tried to remove everything that can be installed later through the Market or by placing the file in the SD card. That gives end users more freedom and let them sort out OS/firmware related problems vs. applications bugs/problems.
This also avoid keeping duplicates in your device.
Since this firmware have "root" privileges, I suggest users to install their "preferred" applications in "/cust/channel/normal/delapp/" folder so if they later want to do software reset (Factory data reset) they will not loose their "preferred" applications.
Copying the ".apk" in that folder has to be done using a file manager that works and let you browse folder with "root" privileges (read/write).
Hope I answered the question and left additional informations.
There's a bug on HWMOD b005.
Double Galery icon.
I've big mistake to disable it, and my device freeze.
fortunately i can recover it with hard reset.
I think it'll better if you add V6Supercharger too.
Thank you very much
arekwaru said:
There's a bug on HWMOD b005.
Double Galery icon.
I've big mistake to disable it, and my device freeze.
fortunately i can recover it with hard reset.
I think it'll better if you add V6Supercharger too.
Thank you very much
Click to expand...
Click to collapse
This has both galery applications, one from the ICS and another from Gapps pack. You can safely uninstall anyone using Titanium Backup. I uninstalled the default ICS one. No problems so far...
Sent from my HUAWEI MediaPad using XDA Premium HD app
arekwaru said:
There's a bug on HWMOD b005.
Double Galery icon.
I've big mistake to disable it, and my device freeze.
fortunately i can recover it with hard reset.
I think it'll better if you add V6Supercharger too.
Thank you very much
Click to expand...
Click to collapse
you right agan gigiku.com
shiranmotha said:
This has both galery applications, one from the ICS and another from Gapps pack. You can safely uninstall anyone using Titanium Backup. I uninstalled the default ICS one. No problems so far...
Sent from my HUAWEI MediaPad using XDA Premium HD app
Click to expand...
Click to collapse
Exactly, you are correct, this is not a bug, it was on purpose.
No freezing and no crashes that we know about in C232B005.
I wanted to leave the choice to the users installing this firmware.
Users can remove the one they want/prefer, one is part of the manufacturer ICS release the other is in Google Apps, they have similar options but different functionalities. The one from Google can sync your picture with those uploaded in G+/PicasaWeb. I personally prefer to keep the second one, the bigger in size.
Since this firmware has "root" privileges it will be easy to remove the duplicate Gallery2 application by using a file manager or Titanium Backup as suggested.
I have not included V6 Supercharger and other stuff because it is not sure everybody wants it on their devices. It can be installed though, for those that want it, however I doubt it's needed on the MediaPad.
Updated the OP with needed informations for applying the upgrade process.
Added an additional mirror for the download of the firmware.
Please tell if you find mistakes or have suggestions.
.:HWMOD:.
hwmod said:
Exactly, you are correct, this is not a bug, it was on purpose.
No freezing and no crashes that we know about in C232B005.
I wanted to leave the choice to the users installing this firmware.
Click to expand...
Click to collapse
Thank you for your respond. I don't know exactly how my mediapad freeze. Now I reinstall your ROM again, and no problem so far.
If you don't mind, I have request. How about change boot animation? may be like OsiMood.
actualy, I love OsiMood User Interface, but cause They stop updating, I'm not using it anymore.
But, If you don't want to add it on HWMOD, could you tell me how to change it, please. I've try many application to change it, and change from /system/media/bootanimation.zip . But, it still not change.
Thank you very much.
arekwaru said:
Thank you for your respond. I don't know exactly how my mediapad freeze. Now I reinstall your ROM again, and no problem so far.
If you don't mind, I have request. How about change boot animation? may be like OsiMood.
actualy, I love OsiMood User Interface, but cause They stop updating, I'm not using it anymore.
But, If you don't want to add it on HWMOD, could you tell me how to change it, please. I've try many application to change it, and change from /system/media/bootanimation.zip . But, it still not change.
Thank you very much.
Click to expand...
Click to collapse
I never did it myself and it depends on what are your objectives.
If you want to just change the boot animation in your device doing what you did should be enough (make sure you use a correctly formatted/packed "bootanimation.zip") and give the right attributes to the files you modify.
If you need to modify an existing firmware and add a different boot animation then you have to handle "ext4" partitions images files under Linux ("system.img.ext4" in the update archive) and substitute that file in the "ext4" image.
If you just want to modify the boot logo, not the animation, you have to rewrite the "splash" partition using "fastboot" (called "logo" in MediaPad mmcblk0p10).
I need to do a test on a brand new Mediapad (not "rooted") but I don't have access to one.
Could someone execute the following "fastboot" command on a new device:
Code:
fastboot oem device-info
and report their results here ?
I have used 2-3 roms in my mp, is it ok?
dark_fighter said:
I have used 2-3 roms in my mp, is it ok?
Click to expand...
Click to collapse
Post them anyway, also they shouldn't be different from mine (more or less):
Code:
[email protected]:~# fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
OKAY [ 0.294s]
finished. total time: 0.294s
[email protected]:~#
I am not sure the internal "fuse" is set up to allow people some chance
I believe it is a one shot only sw "fuse", that's why I asked for a brand new device, one with the original manufacturer firmware and never rooted/unlocked.
Thank you.
Hotmail over active sync as a cooparate account not works for me. Any other faced the same issue? It says couldn't connect to server.
Sent from my HUAWEI MediaPad using XDA Premium HD app
Related
This is meant to be a basic guide to installing and maintaining Android (SD CARD/RAM) on your HD2
NOTE: This guide is not meant for NAND versions of Android installation !!
I want to thank all the XDA forum developers who have made it possible to put Android on the HD2. This is my attempt to make a simple guide for what can be confusing and somewhat scary process (It certainly felt like that to me!!).
For detailed information guide and FAQ please read this thread by mskip
For clear explanation of how things work in Android on HD2 these two threads have excellent detailed information:
http://forum.xda-developers.com/showthread.php?t=813434
http://forum.xda-developers.com/showthread.php?t=790095
Click to expand...
Click to collapse
Before you start you need this Info
Windows ROM version > All Ship ROMs are compatible
Radio Version > Radio needs to be 2.08.50.xx or more (x.xx.51.xx are not compatible)
SPL
Click to expand...
Click to collapse
How to get the Info
For items 1,2 in WinMo look under Settings>About Phone>Software information
This info is also displayed on the bottom left corner (the numbers after the alphabets R,D,G) of your initial boot up white screen with green HTC logo
For item 3 >> Turn phone off > Press and hold Volume down button >briefly press release power button >SPL version is displayed on bootloader screen (Red/Green/White)
Click to expand...
Click to collapse
For those with Radio > 2.08.50.xx you can install Android >> GO TO STEP B
Click to expand...
Click to collapse
For those with Radio < 2.08.xx.xx you cannot install Android without upgrading your Radio (Flashing a new Radio) >> GO TO STEP A then STEP B
Click to expand...
Click to collapse
STEP A (Flashing a new Radio)
If you do not have a compatible Radio version follow the steps below:
Upgrading to the newest HTC stock ROM: This process will upgrade your Radio version anyway (The latest 3.14 ROM has Radio version 2.14.50.4 which is compatible with Android installation): LINK HERE
If you don't want to / or can't upgrade to the latest HTC stock ROM you are going to have a slightly more complicated way
If SPL is 2.10.xxxx or below then use HSPL method. Click here
If SPL is more than 2.10.xxxx you have 2 choices (since HSPL does not work)
Use SSPL method click here
Downgrade your SPL and then use HSPL method click here
Note:
>>Please check the radio version recommended by the Android Build maker>>
>> Click here if you want to download Radio versions
Click to expand...
Click to collapse
STEP B (Installing Android)
If your Radio is compatible (>2.08.50.xx) then here is how to install Android on your HD2
1) Micro SDHC card
Should be atleast 4 Gb, Class 2/4/6/8/10
Formatted clean with 32 or 64 Kb cluster size
2) Install automatic boot loader on WinMo :
This allows you to choose between booting into Windows or Android on start up. From 2nd Android bootup onwards these programs will make it easier to load Windows/Android at startup and you can even specify autoboot into Android if you wish.
Download this as a cab file and install in the phone memory (not in SD card)
Android Loader v6.0 Final for HD2
Exceller bootloader
You can of course manually always boot up Android anytime from Windows File Explorer by running CLRCAD and then HaRET files included in the Android build (see below).
3) Android Build :
Download your chosen Android build on your computer.
Extract / Unzip the folder on the computer
Now copy into the Root of your SD card.
Folder should be labelled "Android"
Once copied into SD card you will see 2 files: CLRCAD.exe and HaRET.exe which have to be run to boot into Android.
There will also be other folders / files (Android Apps, initrd.gz, system.ext2, rootfs.img, zimage, startup.txt, ts-calibration) please leave them as they are.
There are many choices in builds available, such as - MDJ, Darkstone, MIUI,. Please search the forum to look at the different features. I can't advise you on what clothes to buy. The same reasoning applies to advising on Android builds, you have to find out what is right for you...Try the build, if you dont like it, just go for another build..copy and paste your new android folder over the old one and its done.....
4) Data.img :
Your build may have a ready-made one included in the build folder or available to download separately. Size of data image is upto you, 256Mb/512Mb/1Gb (or more). This determines the Size of your Android operating system space for settings and downloaded apps etc. Bigger size allows you to keep more apps etc.
>> At start up if you have a ready-made data.img file, booting up in Android is much faster (5-10 min). (You can choose the image size yourself with this option)
>> If you boot up without a ready-made data.img (Clean Install), then this is created by Android system at first bootup which takes longer (up to 30 min) Here the system will choose its own set default image size depending on startup commands in the build. Its not easy to change this size once its created (although it is possible)
5) First Android Boot
Once you have reached this step you are all set. It really is that simple!
These steps are performed with the phone booted in WinMo
Charge your phone to 100%. This ensures proper battery calibration.
In your File Explorer open the Android folder on the SD card
Run CLRCAD - Nothing seems to happens - This is normal. !!!
Run HARET - Small pop up window with grey progress bar appears with message HaRET LINUX BOOTING - You should then see some text lines in the top left corner of the screen and then a Splashscreen (blank screen with a HTC logo) Please be patient and allow time for the initial bootup.
If Android loads successfully, then (depending on your build )another Splashscreen will appear and then the Lockscreen for Android is launched.
Set up your phone for first use as per onscreen instructions and let all account finish syncing before doing anything else
Click to expand...
Click to collapse
Once you are up and running here are some of my own tips to maintain your system.
1) Always back up of your data.img file on to your pc/mac (weekly)
This is better done in WinMo. This will mean that you can always have a failsafe arrangement for troubleshooting.
2) Troubleshooting (If you start getting data corruption errors or force closes .
> Make another Clean Install of the build -Boot into Android- Reboot in WinMo - Connect to Computer - Copy backedup data.img file into the New (compatible) Android folder.
DONE! you are back where you started. All apps, settings, contacts,emails, messages are saved as they were at the time of backup.
You can also use a backup programme like Titanium Pro. This is useful when going over to a completely different chef build as you cannot (usually) take your old data.img file across.
3) Changing kernels
Follow instructions on the relevant thread.
For MDJ / Hastarin Kernels the following steps work
Boot up in windows - copy 'zimage' and 'Root' folder (which has modules) from the new kernel and paste into your /Android folder on SD card (i.e replace zimage of old kernel).-
Boot up android - check for successful upgrade under Settings>About phone>Software>Kernel ... the new kernel should be listed.
On boot up android will copy the contents of the /Android/Root folder to the relevant place.
If upgrade is successful then while in Android use a File explorer (with root permissions) to delete the 'Root' folder within Android folder, as this is no longer needed.
Note: Some kernels require the Modules (wifi,bt,lights etc) to be copied manually using Root File explorer while booted in Android. Please check the relevant posts for correct steps.
4) Upgrading Android Builds
I always do a clean install i.e let the Android build its own data.img with a clean formatted SD card.
Once this is done then copy your old backed up data.img and overwrite the newly created data.img to get all your info and settings as they were.
Caution: data.img is usually not compatible across different chef builds and its best to start a clean install if you are going to use a completely different build altogether. You can get you settings back by using a backup programme such as Titanium. Google sync will get your Contacts and Calendar back anyway if you have synced it previously to Gmail account.
5) Improving Battery Life
Having read through a lot of forums and trying out various techniques here are tips that have worked for me.
Charge your phone in WinMo to 100% (Green LED) While still connected to charger boot to Android and wait for the LED to go green. Then disconnect from charger.
Autoboot before launching into windows/sense fully, I use Exceller autoboot in 3 sec.
Rebooting Android 2-3 times after initial install and letting it 'settle' for a 1-2 days
Turn off any functions not required e.g BT, WiFi, GPS, Autosync
Turn down screen brightness to minimum
Use a battery current widget to monitor drain
Conditioning of battery: Boot into windows when battery is @ 5%, Discharge the battery fully and let the phone turn off> charge fully to green LED while phone off >> Boot up in Android and continue charging till LED green>> One cycle every 2 weeks
Recalibration: In Android with File explorer (e.g ES Explorer), Choose settings, enable root access and then in Root delete ... /data/system/batterystats.bin . This should be done when 100% charged, Now disable root access in file explorer and close, Run the battery down fully and follow the step above...
Fully conditioned battery should show about 4.2 - 4.3 V charge at 100% (Free app Battery Indicator)
Dataswitch (free app) allows switching mobile data when phone is not in use such as during night time etc
I keep Airplane mode in windows as default before first boot in Android (Not sure if this really helps)
For me greatest battery drain seems to be when i am in area of poor phone signal> switching to 2G helps using Dataswitch app
Things that don't work:
Task killers are not really very useful according to Hastarin
For more detailed information regarding battery life issues have a look at this post
Click to expand...
Click to collapse
Have fun and enjoy your HD2 with Android
"Radio Version > Radio needs to be 2.08.50.xx or more"
more correct
Noob question
Hi!
ive done all this last summer, and it all works fine.
but i wonder if android will work if you have the original WM6.5 insted of Chucky, and other costum ROM?
i mean, the customs are really ugly, and i never use them on dual boot - but i would use WM6.5 if i had the original one, with sense and everything.
the dual boot would be more useful. now i only use android.
Proz00 said:
"Radio Version > Radio needs to be 2.08.50.xx or more"
more correct
Click to expand...
Click to collapse
Updated, Thanks for that.
loni90 said:
Hi!
ive done all this last summer, and it all works fine.
but i wonder if android will work if you have the original WM6.5 insted of Chucky, and other costum ROM?
i mean, the customs are really ugly, and i never use them on dual boot - but i would use WM6.5 if i had the original one, with sense and everything.
the dual boot would be more useful. now i only use android.
Click to expand...
Click to collapse
I agree with you on that. The stock ROM work fine (check my sig) and to be honest I tried the custom ROMs but felt more comfortable with the Stock ROM. It means less messing around with your phone!
Its most important however that your Radio is compatible though. If its not then there is no choice but to Flash a new Radio ROM.
Seems to be well explained, thanks
What is the advantage of letting the Android build create its own data.img first and then overwriting it with your previous data.img?
Ahh i just told mate at work copy android to sd card run cllr then haret.
Worked fine lol
omershahab said:
What is the advantage of letting the Android build create its own data.img first and then overwriting it with your previous data.img?
Click to expand...
Click to collapse
This only applies for Upgrading and not a New install. For a new install its always better to let the system create a data image or use the 'empty' image supplied with the build. Most builds have codes to create a default size image. If thats not to your liking then you can choose a supplied image of desired size and do the first boot up...
For upgrading purposes this method has advantages
1) it ensures a clean trouble free installation first time (makes sense to avoid any conflicts with the old data image on boot up.)
2) If there are any problems with the build then at least you can identify them before you transfer the old data image.
solid.snake said:
Seems to be well explained, thanks
Click to expand...
Click to collapse
Your welcome
Difficult to express how easier you made this process for me, with all info provided.
In my name, and the name of all the rest,that will use this thread to start with Android on HD2...... txs
Updated
updated info on maintanence and battery life
despy1989 said:
updated info on maintanence and battery life
Click to expand...
Click to collapse
I just added a link to your thread in my signature if you don't mind. Hoping it will provide easy access for all users
KrewsialNL said:
I just added a link to your thread in my signature if you don't mind. Hoping it will provide easy access for all users
Click to expand...
Click to collapse
Not at all Reminds me I have to do the same on my signature too
Hey, would doing this void my warranty/contract insurance?
Im on virgin media UK, if that helps.
Thanks for the great tutorial anyway
Unless u install a HSPL my understanding is that there is no reason to void your warranty. But I m no expert in these matters. Having said that my old hd2 touchscreen was freezing and I had hspl on it but managed to reinstall the original SPL back and returned it to virgin and this one is the replacement..they didn't complain ..
Sent from my HTC HD2 using XDA App
I have radio 2.07.51,22_2 and spl 1.42
Does that mean the only way I can do this is the HSPL method?
Great guide m8 good job well explained, but I dont know if this helps anyone but I always un-mount my SD card before a reboot or shutdown, on some builds it can reduce corruption to your data image (ie cedesmiths builds)
JR
@ samdeath . Have u considered upgrading your HTC stock ROM? The new 3.14 ROM also upgrades ur radio. In that case there is no messing with HSPL. The other option is SSPL which does not change ur original SPL.
@ JR . In theory if u umnount the SD Card in Android, it only delinks the the SD card portion outside of your data image? If u umnount the whole SD card then android would crash.
Sent from my HTC HD2 using XDA App
I cant upgrade the stock rom, there isnt a virgin media rom on the htc website, and the normal one says my device is not eligible for it. However, ive installed HSPl now, and followed all the steps, changed the radio to 2.15 etc, However now ive just "installed" android for the first time and its been on the htc spash screen for like an hour. I did not use a data file, is this normal?
Using froyo hd v4.6 btw
Hi all
I am opening up this Q&A thread as extension to my ROM threads, for the simple reason that ever since there is a limitation preventing new users from posting in development threads, I get flooded with PM's. So I intent to move any Q&A, help requests, as well as free and open discussions between users here.
Since the A750 and A789 are so similar, and I put the same stuff in them, I extent both into this one Q&A thread, and in fact, much of it knowledge applies to other Lenovo's like the P700, P700i, S880, A660 which are again very similar and I even use them as basis of my ROM.
Also, I am not intending to be topic police. Like in my other threads, I do not mind if you guys share knowledge about APKHOT or Smileyvvv or Etotalk ROM. As long as it is helpful. Also, I may not always reply myself, so feel free to help each other.
Link to the original threads:
[ROM][2012.xx.xx] Lenovo A750 custom ROM (GB&ICS). <last page>
[ROM][2012.xx.xx] Lenovo A789,P700i,A660 factory&custom ROM (ICS). <last page>
Other related threads (not all mine):
CWM flashing tutorial (update using recovery)
MT6575 flashing tutorial (update using flash utility
Lenovo Original recovery tutorial
[SCRIPTS] Unpack / repack MT65xx boot.img, recovery.img or logo.bin
[REF] Unpacking and repacking stock rom .img files
[UTIL][APP]Lenovo Security / LeSec app (anti-virus/spam/theft/firewall)
[TOOL][TUT]Backup and Restore Mediatek based phone's IMEI
How to DIY : Self root/gapps/playstore/locationfix/clean my ROM
This is a guide on how to root & cleanup your China ROM yourself. It will probably work on all ICS China phones. But it requires & starts with the availability of a recovery image for your phone
There are in fact a few steps:
- Get a proper recovery image for your phone.
- Root it by installing Chainfire's root package
- Install Google GMS ('GAPPS') to get Play Store and Localisation to work
And optionally
- Install Mobile UncleToolset
- Install an extra small fix with location services
- Install an extra small fix with latest APN list
- Install an extra fix to remove well known Chinese system apps
Recovery image
The Recovery Image allows you to boot into an alternative small Linux that you can then use to update the main Android. Updates usually come in "update.zip" scripted files. And the recovery has some other utilities like backup or wipe the entire phone. Getting a working recovery for your phone is step number one, because if you have a recovery, you can do everything else.
To check if you already have a recovery: Well, try to boot into it. The boot sequence may vary with the phone, but on MediaTek phones it is usually to replace the battery and then press&hold both volume buttons while powering up. I have seen it where you need to actually press the power button a split second before pressing both volume buttons. Try a few times, replacing the battery each time.
If you get to a screen that reads CWMR or CWMR Touch (short for ClockWorkModRecovery), you are all set and can continue with rooting. CWMR it is the most common open recovery image. If your recovery is closed, then you need to search the web for a working recovery for your specific model. Each brand and model needs its own recovery, because screen drivers, buttons and partition tables may differ.
Search the web is the best advise. Search wide and search deep. If you cannot find any recovery, then see if you can find a full ROM for your phone. If you have a working ROM image, then there are people on XDA that can make a recovery for you, but typically you need to show/prove that you have really tried to find one yourself.
Flashing a recovery
If you do find a recovery, that you suspect is the correct one for your ROM, then comes the scary part: Flashing the recovery to the phone.
This paragraph is specific to Mediatek based phones. On different hardware you also need a recovery, and once you have a recovery, you can use the other parts of this post, but how to flash other hardware, I do not know, sorry
Flashing using the flash tool is scary to new users. Because new users suspect that if they mess it up, the phone dies. And this is correct! But if you only flash the recovery.img part, you should be fairly safe. Read this manual on flashing. Getting the USB driver installed is sometimes a bit tricky, you may also want to read post #21 and post #25 for help.
I have seen several people asking 'where to find the scatter file'. Well, it comes with the ROM you want to flash. If your ROM file does not come with a scatter file, then is not a ROM file that can be flashed with the flash utility, but with an open recovery.
Rooting
Once you have a working recovery, the rest is simple. For rooting, simply install (from inside the recovery) chainfire's "CMW installable ZIP"
Link to his post: (ignore his big red 'requires root' warning). The file you need is labeled "CWM installable ZIP" at the bottom. Direct link to the file you need to install via recovery update.zip
This usually works by putting the zip file on the SD card (its name can be anything, though for some limited recoveries it sometimes must be named 'update.zip'), booting into recovery, and selecting the zip file to update.
Google GMS (Market/Play Store, Location, etc)
Simply install the latest Google Mobile Services (better known as GAPPS) from CyanogenMod V9. This is their explaining wiki from CyanogenMod
The file you need is called gapps-ics-20120429-signed.zip for ICS and gapps-jb-20121212-signed.zip for JB and can be found here. You probably also want to wipe your cache partition after doing this.
Mobile Uncle toolset
Just install this program apk (so not through the recovery, just install it normally). Or search the web for the latest one.
Fix location services
If location services does not work, do apply Google GMS (GAPPS) above. If it still does not work, it may be because the phone is programmed to use Chinese location services. This patch will tell it to use GMS. The patch will apply, and probably even work, on all ICS phones. But was originally made&tested on a Lenovo A750 ICS. Its called V1.3 because many people have downloaded the A750 v1.3 patch and used it on many MT6575 phones. It is still the same patch, except the update.zip is tweaked to work on any ICS phone, not only MT6575 ones.
Sometimes you also need to go into MobileUncle tool, the MTK Engineer mode, and in location settings. Depending on your exact model, somewhere in there is a NetLoc or NetLocation and a GeoCoding setting, with options of MEDIATEK and GOOGLE. Ensure they are set to GOOGLE.
After messing with location settings, it is best to also wipe cache.
Fix APN list (or My 3G does not connect!)
You can always add your own APN (Access Point Names) from the settings menu. Just add your own, and select that over the pre-build one. But this package will update with the latest list as maintained by CyanogenMod 9. The update.zip was made in such a way it should work on all ICS phones, Mediatek or other.
Clean well known Chinese system apps
<patch still coming>
==========================================
List of known recovery images for Mediatek Flash tool:
Lenovo A750 : 592zn : See also this post #607, nandroid backup does not work.
Lenovo A789 : 592zn or APKHOT
Lenovo P700i : My own, based on APKHOT with CWM.
Lenovo P700 : My own, based on CWMT / 592zn. nandroid backup will not work.
Lenovo A660 : My own, based on APKHOT with CWM
Lenovo S560 : My own, based on APKHOT with CWM (as yet untested)
Additional Recovery Images in this post.
If you feel you searched all over the web, and could not find a recovery for your model, and you next feel you should ask me or one of the other people on XDA to make you one (which I am not encouraging), than please be aware we need at least a 'standard ROM' for your phone to start from. Without it, I can do nothing. So go back out there, and find a standard ROM, does not matter what language, as long as it is for your specific phone model and known to work.
Also, as an extra warning : If you are flashing, and you experiment with 'suspicious' ROM sources, *never ever* flash the preloader, mbr, ebr uboot. Only flash those from a trusted source and if they belong to your exact brand and model phone.
One more reserved
lolo250612 said:
Hello from France,
Just a little message to thank you very much for your very useful "Lenovo A789 factory&custom ROM (ICS)" thread. I have just bought a A789 from etotalk, and your posts really help to master the beast.
I can't participate to the thread because I am a new member and consequently can't post message to this development thread. And this very sad, because I have discovered a shortcoming of this phone. Apparently, the ICS entire phone encryption does not work and, according to some information I have gathered around the web, it may be due to the fact that the internal sd partition is not ext4 which seems to be required.
It may be due to the fact that the kernel does not support ext4. If this was the case, I would be very pleased to activate the option, recompile it and share the result with other people at xda. I have done it for two types of Samsung Galaxy phones.
In this case, the two problems I would be faced with are:
1) Getting the kernel sources. For Samsung it is quite easy. For Lenovo, I am not able to find them (I can't read Chinese).
2) The process to package the new compiled kernel to a zip, compatible with cwm.
Anyway, thanks for your help and to share your knowledge.
Sheers,
Laurent
Click to expand...
Click to collapse
cybermaus said:
well, not sure about encryption, but I can *assure* you that the phone supports ext4, because in fact the root; system; cache; secro and data partitions are all in ext4 . I know that quite certain, because to unpack/repack, I need to recreate an ext4 loop device.
Internal SD is indeed FAT partition. But it is normal for SD to be FAT
Click to expand...
Click to collapse
It is possible the encryption fails on the FAT of the SD card. It is an internal device, if that encryption utility tries to parse all the internal partitions, it may fail on FAT, but I am guessing here. However, then it would fail on pretty much all recent china phones, they all seem to have this internal SD card. You could try to simply format the internal SD as ext4.
I do not think it would fail on the recovery or boot sections. Those are all nicely wrapped up in the first partition of the emmc chip (emmc0p0 or something) in a proprietary filesystem, as I suspect true for all Androids. So your tool would know to exclude that the first one. However, if you want, you can get the original recovery you asked about from the original A789 ROM in my Dev-Host.
Edit: Encryption issue solved, see post#9 below
I already managed to build a multilang framework-res.apk for the A789 ROM. But now there are all those apps that need to be made multilang also - settings.apk and more... a lot of work.
Is it possible to take a P700 ROM with A750 kernel and flash it to the A750? Or a P700i ROM and A789 kernel for the A789? They seem to be almost identical.
Any plans to integrate the long press home button function in A750_ROW_S114_cybermaus_ICS_V3.1? Would like to test this rom but this missing feature is essentail for me...and onother question: V3.1 is also for A789, right? Same problem with long press home feature?
@oz42
Well, I am a little disappointed about that question. Putting the P700_ROW on the A750 is *exactly* what my V3 series is. Works wonderful. It's the reason I have been updating this thread for the last two weeks. Problem is that the only extra language is Vietnamese. You may want to re-read posts #2 and #585 in the A750 thread.
I suspect the same is true for P700i and A789, but I did not find a P700i_ROW rom yet. I did find a S880_ROW, and when I have time (later this weekend) I will check if that has proper multilanguage (edit: No. It adds ru, vi, id to en and zh. Not quite what I had hoped for)
@metzner
Yes. When I know how. But I do not have a clue at this moment. I am very pleased about the V3.1, but the missing long press is annoying me at times.
No, V3.1 is not for A789 (yet). They have different partitions, different schreen driver. YOU CANNOT flash a A750 on A789 (or any MT6575 on MT7577) without 'porting' the ROM. I do have a Frankenstein ROM, using p700_ROW with kernel/partition/modules/baseband from A789. But it was not tried out yet.
A789: Encryption problem
I have installed aLogcat to determine what could block the encryption service on the different ROMS I have tested on my A789. The interesting part revealed to be:
E/Cryptfs ( 87): Orig filesystem overlaps crypto footer region. Cannot encrypt in place.
Googling for this problem, it appears that there is a strong probability that the culprit is CWMR that I have installed almost right after getting my phone. See: http://forum.xda-developers.com/showthread.php?t=1792101 or http://rootzwiki.com/topic/25652-fixing-galaxy-tab-2-encryption/.
So if somebody has a package that can be safely used with mt6575-flashing tools, to recover the stock recovery or, much better, to install a "clean" version of CWMR, I would be glad to test it and see if it is actually the origin of the encryption problem.
Edit:
@Cybermaus: I have just noticed that you have already addressed part of this message. I have already tried to format the internal sd as ext4 with Minitool partition Wizard on Windows. This fails also. Moreover, the system reports a failure on this partition and ask to reformat it as vfat. I will try by putting back the original recovery from your 4shared. Thanks a lot.
@lolo250612
If I read that post you found, the problem is not so much CWMR or CWMRT itself, but the fact it wipes and formats /data completely, without leaving 16KB of unused space at the end of the partition.
That means replacing it with factory recovery will not help, unless if you then also wipe using that factory recovery, and that factory recovery does leave 16KB. You could also try wiping it from the settings menu.
After you have tried the factory , let me know. I think I can make an empty /data for you that is 16KB shorter than the partition, but you would have to apply it using the flash-utility method.
Edit: checking, I found that the userdata.img that is inside the original S228 factory flash ROM is already 1024K short of 768M. So 767M. No need to build one with only 16K short, just use the one you already have.
Hi cybermaus
Thanks for your contribution. Please help me if you've free time.
Does this custom ROM support traditional Chinese character?? I'm sure Chinese support would include simplified Chinese.....
@loimlo
The A750 V1 and A789 V2has two forms of Chinese, which I cannot read, but I suspect are traditional and simplified. The A750 V3 has one form of Chinese, which I still cannot read, so I am not sure which of the two, but here is a screenshot of it, let me know which it is.
Amadis223 said:
Hi, I wrote with yuweng on this subject. And it is very strange. He says, that mt6575 has only ext4 filesystem, but I,am sure,that I have mt6575 and yaffs filesystem. What do you think ?
Click to expand...
Click to collapse
Well, all the MT6575 and MT6577 based ROM's that I have dissected have ext4. This is probably because mediatek provides ext4 in their development kit. So yeah, I think all mt6575 are on ext4, and not yaffs. I think maybe the mt6573 has yaffs.
cybermaus said:
@lolo250612
If I read that post you found, the problem is not so much CWMR or CWMRT itself, but the fact it wipes and formats /data completely, without leaving 16KB of unused space at the end of the partition.
Click to expand...
Click to collapse
I agree with you.
Edit: checking, I found that the userdata.img that is inside the original S228 factory flash ROM is already 1024K short of 768M. So 767M. No need to build one with only 16K short, just use the one you already have.
Click to expand...
Click to collapse
I have flashed userdata.img. That WORKS :victory:. The phone reboots and then encryption starts. Done in less than 5 minutes. Great. Now, just have to tried one of the utility around that allows to have an encryption password different from the lock one. Many thanks for your help :good:.
hi there,
I just got a Lenovo A789 and i just installed A789_S228_cybermaus_V2.1 and it works perfecly...
i'm new to android and i can't get cellular data to work ( i have reason to believe that it worked in original ETOTALK rom, but im not sure ).
1) i do have a data plan
2) cellular data / mobile data is turned on
3) 3G card with cellular data plan is in slot 1
wrong basebands or apn settings (Portugal, Vodafone) ? ( i can see them in mobileuncletools but i cant change them )
help?
note: i cant follow most of android tips that i googled because some of the menus to edit APN settings do not exist on this rom :\
@spinal2k
Well, the simply solution would be to try and apply the A750 V1.4 as listed in post#2. It only applies location fix and new APN list, so its safe on the A789, even if it was originally for A750.
Second option would be to Google for the keyword APN together with your provider and country names.
Last option is to tell us the mcc/mnc that mobile uncle found, as well as your current APN settings, and maybe we can figure it out.
Edit: you can change APN in Settings->Wireless->More->MobileNetworks->AccessPointNames
cybermaus said:
Last option is to tell us the mcc/mnc that mobile uncle found, as well as your current APN settings, and maybe we can figure it out.
Edit: you can change APN in Settings->Wireless->More->MobileNetworks->AccessPointNames
Click to expand...
Click to collapse
ok, thanks for the tip... how can i see mmc/mnc on mobileuncle tools?
According to that wikipedia page, my MMC/MNC is 268/01 and that it uses GSM 900 / GSM 1800 / UMTS 2100.... On mobile uncle engineer mode i can see that on the 1st sim card UMTS 2100 doesn't exist ( only UMTS 2000 )... :\
acoording to the "you can change APN in..." i can't changed them, just see them... they look fine to me, they're not wrong...
:\
@spinal2k
Don't tell me the ones from that Wiki page, but the ones you find in the APN settings. And then also the "market name" of the service you have. You cannot change, but you can add a new APN, and then select that to use.
But simply applying the V1.3 may be easier, it has the APN list maintained by Cyanogenmod, and will probably solve it anyway.
cybermaus said:
@spinal2k
Don't tell me the ones from that Wiki page, but the ones you find in the APN settings. And then also the "market name" of the service you have. You cannot change, but you can add a new APN, and then select that to use.
But simply applying the V1.3 may be easier, it has the APN list maintained by Cyanogenmod, and will probably solve it anyway.
Click to expand...
Click to collapse
oh, i couldn't see that i could add new.... Now i added an optional apn ( even though the one listed was on official carriers page ) ... now its working...
Thank you for the tips... keep them updates coming
note: i did update with A750 v1.3 and i saw no changed in apn list...
A750 V3.1 battery life
I have been using the cybermaus V1.3 ICS for ages, and it works really well. Recently tried the V3.1 ICS.
Also seems to work really well as well, and a definite plus is the 3G signal strength - I see a definite improvement.
There is a dealbreaker problem for me, though - the battery life is noticeably worse than the excellent life on the V1.3 rom. I'm a noob - tried clearing user cache/dalvik, but not reset (I want to keep my apps/data).
Any suggestions before I go back to V1.3 - thanks.
zapzog said:
Any suggestions before I go back to V1.3 - thanks.
Click to expand...
Click to collapse
Well, a request more than a suggestion: your battery is now a few months old, so slightly less good then when new, but you got used to it. But now, due to the flashing of a new ROM, you are playing on it more, and it is in your attention very much.
I cannot properly test myself, I have to tether it daily for data access. So please try to get a proper test of it:
Stay with V3.1 a few bit longer, at least 2 battery cycles extra. (you can barely have had one) so you get a better baseline. Charge the same method as before (I find that charger works better than PC-USB) After two more cycles, when you have a proper idea on the life, go back, and get a renewed baseline on V1.3 also. And then report your results
As in another thread, I just complete bricked my TS but with help from cheahcl and Lokifish Marz I come back a alive! With more and more people receiving their TS, I feel the need to summarize what I experienced so others wont need to go through all those sh*t. I didn't create any of the tools/step here... All things belongs to the great DEVs of XDA. I just summarize as my personal experiences for your convenience~
<A little background: I am on the 4th list of 1/8/2100>
First of all: Do a backup immediately after you got your TS!
===========================================================
MTK based system is actually very difficult to become brick (almost impossible) as long as YOU HAVE THE F/W SPECIFIC to your TS! The problem is that it seems OMate made changes between each delivery. For Example, the 4th list of 1/8/2100 is different in of the 3rd or earlier 1/8/2100. At least from F/W's point of view. Thus, any F/W that are posted on XDA is NOT guaranteed to compatible with YOUR TS, unless you are lucky!
Since there is NO official/complete deposit of "stock F/W". Once you modified what in your watch, there is no guarantee you will get same version of F/W and it's very possible that your watch will never return to stock!
Part I --- back up the F/W
============================================================
First of all, please get all necessary tools directly from this post "All Tools" http://forum.xda-developers.com/showthread.php?t=2734687 (Do NOT download or install any other things there!)
*if above link doesn't work, I have a mirror in end of this post.
Follow those steps: (modified from link above)
1. Download "All Tools"
2. Install Universal ADB Drivers (included in All Tools) <--If you already have ADB up and running, it's not necessarily, then.
3. Enable USB Debugging on watch
4. Launch MTKDroid Tools
5. Connect watch to PC
6. Please follow the instruction from here: http://www.chinaphonearena.com/foru...up-MTK6592-MTK6589-MTK6577-and-all-MTK-Phones
a. Skip everything above and just starts from "B) Open ADB prompt to begin communication with the phone" .
b. Don't worry about the recovery thing... TS comes with a recovery which is not locked and you can do everything this article said with only stock recovery. (also no busy box is needed, nor su since TS run everything in root!)
c. You could also refer to the video guide below for details
7. After Step D), you will have a backup of your F/W which 100% compatible with your TS!
Part II --- back up the IMEI and NVRAM
============================================================
Please follow this guide here: http://forum.xda-developers.com/showthread.php?t=2631953 under "IMEI Backup Procedure" before proceed anything dangerous!
Tools:
============================================================
Currently I mirror "All tools" here https://www.dropbox.com/sh/tsa2jottw...uIEpOyyDiYWFva until it's shutdown by Dropbox for too much traffic. (Any one can provide me a better place?)
I also add a FW backup for "4h list 1/8/2100", which ONLY work with this version of TS. It ONLY works if your original build version is "20140513.103530". If NOT, DON'T TRY IT. It will just waist your time! You had been warned!
After you played with your TS, maybe you will come to an end that your TS is no longer turn on! Fear NOT! It's just the fan part of playing with your TS!
Return to Stock Steps (F/W and IMEI, NVRAM)
======================================
1. If your TS still can start in system, then just simply follow the excellent guild prepared by MasterZen88 at http://forum.xda-developers.com/showthread.php?t=2641261
2. The only difference is you must use the F/W you backup yourself DO NOT DOWNLOAD THE F/W list in that page!
3. If your TS no longer powers on, or cannot enter the system, please do:
a. Disconnect your TS from PC
b. Still follow the steps on above link to prepare your PC to install the MTK USB driver, read in the "Scatter file" from your backup
c. The only difference is Step 11. Since your TS won't power on, you need to pull the battery, than re-install the battery than connect to the PC.
d. After you did this, You should see the MTK SP Flash Tool start flashing your TS!
4. After restore system, please follow http://forum.xda-developers.com/showthread.php?t=2631953 "Restoring Your IMEI After A Full Firmware Flash" to restore your IMEI and NVRAM or you will not able to make phone call!
Trouble Shooting (common error message from SP Flash Tool)
=======================================================
1. "S_FT_ENABLE_DRAM_FAIL (4032)"
Ｔhe F/W you try to flash is NOT compatible with your TS. If the F/W is not backup by yourself, downloaded from XDA or anywhere, there is a 99% chance it won't work on your TS!
Sometimes it also indicate you have a bad connection between TS and PC, maybe a bad cable or cradle...
2. "S_FT_READBACK_FAIL(4009)"
I don't really know what caused this... I experienced twice but I just pull the battery again and it's go like normal
3. "S_COM_PORT_OPEN FAIL(1013)"
a. The MTK USB VCOM driver is not properly installed, or
b. Your connection between PC and TS is not good (bad cable?)
c. Due to previous error, you NEED to pull the battery out of TS and put in the battery than link to PC again! The TS will go offline once any failure during flashing process.
I hope this small guide will save someone from the panic time I had....
How to install Play store and (super)SU?
Installation Play Store
====================================================================
It's really easy... just forget code like *#*#2013.... Doesn't work on newer batch! (I only confirmed this on 4th list of 1/8/2100 developer version)
1. Download Google play here: http://www.xda-developers.com/andro...densities-and-the-rest-of-this-weeks-updates/
2. Make sure on TS you enabled the "Setting/Device/Security/Unknown Sources"
2. transfer the file into the internal SD of TS
3. Use the TS' built in file explorer to locate the apk, than just click the apk to start installation.
4. Profit!
Install (super)SU
====================================================================
Just follow the steps below (I only confirmed this on 4th list of 1/8/2100 developer version) , I saw this somewhere in XDA but forget where... credit to the original poster!
1. Launch MTKDroid Tools (please configure it as the steps in OP)
2. Connect TS to PC
3. Click on "root, backup, recovery" tab
4. Push the SuperSU button then choose which version of SU you want (I use SuperSU)
5. After success installation, go to your TS (TS must have access to internet) and launch SuperSU. SuperSU will prompt to update SU binary
6. Profit!
Great Guide. Following your guide I've backed up all the necessary files to go back to stock for AW-420
:good::good::good::highfive::highfive::highfive:
I have a problem making backups - both the nvram and full system backups fail. I suspect it is not finding an md5 application since files.md5 is zero bytes but the filesystem seems to have been copied OK. (with a fairly clean Win8.1 64 install, just android dev tools installed, this is my gaming machine...)
Code:
--->>> Connect to device <<<---
--- NVRAM Bin Region is write to the file: : C:\omate\tools\All Tools (14-2-8)\1 MtkDroidTools v252\BackupNVRAM\TrueSmart_86xxxxxxxx59988_nvram_140522-194022.bin
--- ERROR during copying file between phone and PC : C:\omate\tools\All Tools (14-2-8)\1 MtkDroidTools v252\BackupNVRAM\TrueSmart_86xxxxxxxx59988_nvram_140522-194022.tar
tshoulihane said:
I have a problem making backups - both the nvram and full system backups fail. I suspect it is not finding an md5 application since files.md5 is zero bytes but the filesystem seems to have been copied OK. (with a fairly clean Win8.1 64 install, just android dev tools installed, this is my gaming machine...)
Code:
--->>> Connect to device <<<---
--- NVRAM Bin Region is write to the file: : C:\omate\tools\All Tools (14-2-8)\1 MtkDroidTools v252\BackupNVRAM\TrueSmart_86xxxxxxxx59988_nvram_140522-194022.bin
--- ERROR during copying file between phone and PC : C:\omate\tools\All Tools (14-2-8)\1 MtkDroidTools v252\BackupNVRAM\TrueSmart_86xxxxxxxx59988_nvram_140522-194022.tar
Click to expand...
Click to collapse
Actually I been to this before... However I don't remember what exactly I did to resolve this....
Basically this tool relie on ADB to get access to this watch. It seems your watch is not communicate correctly via ADB. Maybe reinstall the ADB driver from the All in one tool I linked in OP (even your ADB works)
Sent from my HTC_One_max using XDA Premium HD app
New link to "All Tools"?
Since Loki removed his files, is there another link to "All Tools"? Can't download it at link above.
Thanks!
Sorry about that. Bad part is older firmware and root/patch methods are causing serious issues due to Omate changing the hardware yet again.
Lokifish Marz said:
Sorry about that. Bad part is older firmware and root/patch methods are causing serious issues due to Omate changing the hardware yet again.
Click to expand...
Click to collapse
However, the "All Tools" is still working and a valuable piece for everyone here! Could you please at least keep that?
Without the "All tools" I worry when people run into trouble, there would be even harder for them to go back.... (not only need to get correct FW but also need to get correct tools). There are so many version on the internet which is at best too old as not working, at worst infested by something...
Currently I put this "All tools" here https://www.dropbox.com/sh/tsa2jottw6f1f72/AAAgDEcvmo7uIEpOyyDiYWFva until it's shutdown by Dropbox for big traffic.
I also add a FW backup for "4h list 1/8/2100", which ONLY work with this verion of TS. if anyone need it...
(Dear Lokifish, please PM me if you have concern of my hosting of "All tool".)
FYI:
Just as Lokifish Marz said, looks like omate changed hardware for the 4th EU patch of deliveries.
The latest EU batch from the 4th list has the following firmware:
Baseband: MOLY.WR8.W1315.MD.WG.MP.V4, 2013/08/14 18:16
Kernel: 3.4.5
OUI: 2.1
Build: Omate_TrueSmart_20140513.103530_V2.0
My TS was from the 3rd EU batch which has the following firmware:
Baseband: MOLY.WR8.W1315.MD.WG.MP.V4, 2013/08/14 18:16
Kernel: 3.4.5
OUI: 2.1
Build: Omate_TrueSmart_20140328.182336_V2.0
Out of curiosity, I was already in Unified Rom, I tried to flash "Build: Omate_TrueSmart_20140513.103530_V2.0" for my TS.
I bricked my device! lucky I had made all the relevant backups, and got my TS back to factory ROM that came from the 3rd list batch.
Then Unified it again.
tshoulihane said:
I have a problem making backups - both the nvram and full system backups fail. I suspect it is not finding an md5 application since files.md5 is zero bytes but the filesystem seems to have been copied OK. (with a fairly clean Win8.1 64 install, just android dev tools installed, this is my gaming machine...)
Code:
--->>> Connect to device <<<---
--- NVRAM Bin Region is write to the file: : C:\omate\tools\All Tools (14-2-8)\1 MtkDroidTools v252\BackupNVRAM\TrueSmart_86xxxxxxxx59988_nvram_140522-194022.bin
--- ERROR during copying file between phone and PC : C:\omate\tools\All Tools (14-2-8)\1 MtkDroidTools v252\BackupNVRAM\TrueSmart_86xxxxxxxx59988_nvram_140522-194022.tar
Click to expand...
Click to collapse
Did you run the tool as administrator to make the backups?
Stu| said:
Did you run the tool as administrator to make the backups?
Click to expand...
Click to collapse
Yes, tried that. I'm quite happy with my adb access, managed to root my HTC M8, and get shell access on the TS fine (it now has SU working).
I've installed cygwin (overnight!) in the hope that will provide the missing exe that the tool was seeming to want.
lssong99 said:
(Dear Lokifish, please PM me if you have concern of my hosting of "All tool".)
Click to expand...
Click to collapse
It's all good. I'm fine with it. Seeing that folks are now looking at almost 10 different HW versions to deal with, AllTools is going to become really popular.
lssong99 said:
However, the "All Tools" is still working and a valuable piece for everyone here! Could you please at least keep that?
Click to expand...
Click to collapse
I have also uploaded the zip to gdrive as another mirror. https://drive.google.com/file/d/0B099RU3-XRVgVW5HeEpqUXZPMGs/edit?usp=sharing
Fixed my issue. As per the MTKDroidtools log file:
Code:
23/05/14 11:40:34 --- NVRAM Bin Region is write to the file: : C:\omate\tools\All Tools (14-2-8)\1 MtkDroidTools v252\BackupNVRAM\TrueSmart_86xxxx
xxxx59988_nvram_140523-114031.bin
23/05/14 11:40:34 /system/bin/sh: tar: not found
23/05/14 11:40:34 --- ERROR during copying file between phone and PC : C:\omate\tools\All Tools (14-2-8)\1 MtkDroidTools v252\BackupNVRAM\TrueSmar
t_86xxxxxxxx59988_nvram_140523-114031.tar
the issue was with missing functions running _on_the_watch_ Installed busybox, and good to go. Now, this does leave a problem for anyone wishing to do a backup before making mods.My original backup extracted the system partition (as a dos copy of the filesystem, which must be incomplete for permissions etc) but when done with tar on the device I get proper img files.
I suspect it is possible to manually 'mount -remount,rw /system' then adb push busybox, as it happens I've already installed su so just installed from playstore.
lssong99 said:
1. Download "All Tools"
Click to expand...
Click to collapse
Where is the all tools?
sorry i have find it in GDrive!
xs4all said:
FYI:
Just as Lokifish Marz said, looks like omate changed hardware for the 4th EU patch of deliveries.
The latest EU batch from the 4th list has the following firmware:
Baseband: MOLY.WR8.W1315.MD.WG.MP.V4, 2013/08/14 18:16
Kernel: 3.4.5
OUI: 2.1
Build: Omate_TrueSmart_20140513.103530_V2.0
My TS was from the 3rd EU batch which has the following firmware:
Baseband: MOLY.WR8.W1315.MD.WG.MP.V4, 2013/08/14 18:16
Kernel: 3.4.5
OUI: 2.1
Build: Omate_TrueSmart_20140328.182336_V2.0
Out of curiosity, I was already in Unified Rom, I tried to flash "Build: Omate_TrueSmart_20140513.103530_V2.0" for my TS.
I bricked my device! lucky I had made all the relevant backups, and got my TS back to factory ROM that came from the 3rd list batch.
Then Unified it again.
Click to expand...
Click to collapse
My TS was from the 2nd EU batch and it have the same firmware as yours.
There are two backup folders for TrueSmart in the location of "backups"
I just tried to backup my TrueSmart and everything went quite smoothly until I was meant to prepare blocks for Flash Tool. I could find 2 separate backups for TrueSmart with different time stamps on them. I downloaded the AllTools.zip that was hosted in this thread in Google Drive. Is that someone elses backup or what? I have to just choose the later backup, correct?
EDIT: Went with the latest because the earlier already had !FilesForFlashTool folder in it.
How can I actually use SuperSU? When a root request pops up, there aren't any buttons visible except for ask again. I cannot scroll. How do you do this?
soulcrusher said:
How can I actually use SuperSU? When a root request pops up, there aren't any buttons visible except for ask again. I cannot scroll. How do you do this?
Click to expand...
Click to collapse
That happened to me as well. It turned out that if you change the font size in Settings - Display - Font size to Small it will work just fine and show the buttons. Your welcome.
Just found a beautiful ROM on 4pda forum. The ROM is developed by user booroondook. A few specifications, thanks to Google translate:
- DIY kit for all resolutions/platforms (well, all means RK3066 or RK3188 and the two main resolutions our units support). Just download the archive and run the setup script. Warning! Lollipop ROM only for RK3188!
-FUSE support - File system in User space. internal_sd is part of /data
-OTA system updates
-mostly untouched UI
-support for SD-card located startup script
For my GA2114 this is the most stable ROM to date.
The install procedure a little bit long-enter recovery, install, reset, enter recovery, install again, wait a long time for the intialization scripts to end. When done, enter settings and change the language to English as default is Russian - by far the most complicated part of the setup
You can take a look at it here.
A more detailed install procedure in this post
Latest KitKat build from March 2016 HERE
NEW Lollipop build - March 9, 2017 :Details and download link
Personally I need more info before installing this one. Perhaps Malaysk can comment on this rom
That ROM is significant step forward with FUSE. Installation is not problematic - it justbit strange. You have to install TWICE! First time, after initial boot, the new system partitions and links and file-system permissions are setup (this step cannot be done in recovery during initial firmware update). Then, for redefined OS and file sys mapping, SECOND firmware update (without wipping!) sets up everything in adequate locations (with FUSEd linkage among storage volumes). As you may figure out, you should let device to reboot after first install, but you dont have to let it go into full loading as it will usualy stuck (because needed foles are messesd up as the SECOND install is needed to put them in FUSEd locations).
So if you have problem with Russian and Google Translated very strange output, just do as above. Two times install ROM image. And its all fine.
Now, on the poibt:
I hope Malaysk will pay attention on this. The FUSEd ROM is much advanced option to better utilize our ibternal storage than 2GB or even 4GB data partitions fixed resizing (which is huge improvement itself from idiotic 1GB OEM Chinese 'design' I'm pritty sure is just blind copy-paste from some seed OS image they took from somewhere and they even after several years dont understand at ALL).
So I would kindly ask Malaysk to consider joining efirt with his Russian coleague who did FUSE but is not updating nor customizing his ROM as much and as dynamicaly (and passionately) as Malaysk.
So if Malaysk can adopt, merge, FUSE in his ROM it will be great leap forward for everyone. Original FUSE contribution would continu to live and power up the great Malaysk ROM branch. A I hope other devs them may find interest to join efforts, to contribute to that UNIFIED branch ratger than we have nu.ber of branches, at different stages, with different strengths and weaknesses....
Learning from mature dev teams working for years on phone ROMs, it is important to join, coordinate, split in modular but UNIFIED and at the end combined ROM released. It provided much better results. And it pays off for both us, users, and devs (if we pay respect they deserve for their noble effort).
I will always stress that I personally feel interest to stimulate this community to develop and matture. I'm very disapointed by Chinese very poor SW support, but I have beleive that HW is much more capable. So if we can get advanced SW for these units, it may well pay off for ALL of us who bouth them for fraction of price of OEM ones. An even we can have much better SW and overal functionalities than OEM. So the price difference allows us to dinate deacent sums to devs here if they provided us with good ROMs.
manicuspanicus said:
Personally I need more info before installing this one. Perhaps Malaysk can comment on this rom
Click to expand...
Click to collapse
Well, it was Malaysk who actually gave me the idea to look for these ROMS, in this post he mentions the other cooks.
Yes he did in a post where people want different colour on his rom . What I'm saying is I would like to know more like the description Malaysk has in his roms. Is it a big deal to ask you to give us a review of the rom and a step by step guide on installing it if there are some different steps from all the other roms?
Στάλθηκε από το ONE A2003 μου χρησιμοποιώντας Tapatalk
As I wrote, ROM us stock modded to have FUSEd partitions for data. Stabile as stock, looks like stock, perfirms as stock...
I explained install procedure as it is but strange and someone NOT knowing Russian may be buzzed with Google Translation (thinking it is transkation mistake to have double install needed).
But the real problem here us that devs are not joining and coordinating efforts. So we have Malaysk point insatisfied users to other ROMs... When dev starts to divert users to other ROMs, it looks something is wrong here, isnt it?
manicuspanicus said:
Yes he did in a post where people want different colour on his rom . What I'm saying is I would like to know more like the description Malaysk has in his roms. Is it a big deal to ask you to give us a review of the rom and a step by step guide on installing it if there are some different steps from all the other roms?
Στάλθηκε από το ONE A2003 μου χρησιμοποιώντας Tapatalk
Click to expand...
Click to collapse
I can do that, no issue. Just give me a couple of days. It's the least I can do for fellow xda members
FUSE seems to be the right way to go, i hate the fact that as standard i can only use 1gig for user data, and i also don't want to decompile and replace the file for partition and recompile every time i want to update/change rom etc etc.
So i hope Malaysk will pick it up and some proper documentation written by someone
m00n61 said:
I can do that, no issue. Just give me a couple of days. It's the least I can do for fellow xda members
Click to expand...
Click to collapse
:good:
Booroondook DIY ROM details
WARNING! Make sure you can boot into recovery even with the screen off. This will allow you to install a factory ROM if anything goes wrong.
Back up your user data. This ROM has to format the internal Flash so all user data will be deleted.
DISCLAIMER. I am not affiliated in any way with the developer of this ROM. All credits should go to 4pda user Booroondook. I only wanted to share this ROM that works perfectly for my unit, keeping the OEM flavor and vastly improving on functionality - yet is pretty much unknown due to language barriers.
Preparing for installation
1. Download the DIY kit to your computer. Unpack into any empty folder on your computer (the full path to the folder should not contain spaces, non-Latin characters, punctuation marks and special characters, so it is not recommended unpacking on the desktop, in the "My Documents"folder, etc.
2. Switch to the folder where you unpacked the archive.
2. Run start_eng.bat. Since you are reading this HOWTO I assume you are not familiar with Russian.
3. You will be prompted to select a processor. Only two options - RK3066 and RK3188. The selection is made by entering the numbers in front of said processor type, followed by pressing the Enter key
4. Next - the choice of screen resolution. There are also two variants - 800x480 and 1024x600. Selection is carried out in the same manner as in the preceding paragraph
5. After that begins the process of assembling the firmware, which takes less than 10 seconds.
4. Wait for the ROM to be prepared and, when done, exit the batch file.You will have a new file, called update_yourprocessor_yourresolution.img
5.Rename the generated file to update.img
6. Copy the file to an SD-card
Installation
1. Insert the Sdcard containing update.img in your HU.
2. Boot into recovery. On my unit I can do that in two ways:
a. Press the reset button. Keep ot pressed while also pressing the Power button. Release the reset button and keep the power pressed a few more seconds
b. Press the reset button. Press both Home and Power buttons for about 10 seconds (the button light will flash shortly) and release the Home button followed by releasing the Power button then pressing Power again .
2. Do a factory reset - the last option in the list - to clear data and cache
3. Update the firmware. Wait for the unit to reboot.
4. Whe you see the animated logo, reset the HU and re-enter recovery mode
5. Update the firmware again. Wait for reboot
6. The first start will take longer than usual due to the need to re-create the primary filesystem and running of initialization scripts.
Release notes:
Base firmware: HA-20151010
Initial DPI is set to 160 for 800*480 screens and 240 for 1024*600. You can change this in Settings
Initial language is set to Russian. Just go to Settings (you should recognize the icon) and look for язык - this means language in Russian. Click on that and change to your preferred language.
In the release notes, Booroondook says the ROM has USB debugging enabled which will prevent using a USB stick. I don't have that issue so maybe the article is outdated. Anyway, if you have this issue, either type ADBOFF in factory settings password field or delete the file /system/etc/init.d/01adbon
Custscript
If the root GPS-card contains a file with the name custscript, it will be executed when you start the HU.The requirements for the file are the same as in conventional Linux executable scripts. That is, an indication of the shell in the first line and the line breaks Unix-style.
The first line can be: #! / System / bin / sh
For example, if you are experiencing problems with the rebooting in recoveryi (no suitable hardware buttons, or other reasons), then you could put on the card a file with the following content:
PHP:
#! / system / bin / sh
reboot recovery
And your HU will reboot in recovery mode. However, don't forget to delete it when done.
This script can also be used for "early loading" applications and services.
The advantage of the script placed on the SDcard is that unlike install-recovery.sh, if something went wrong, you can simply pull out the card to fix the script. In addition, in some cases, through a script, you can "revive" the HU.
Other features - in no particular order
1. FUSE - no need for App2SD since all space is available for apps or data;
2. OTA system updates;
3. Both OEM launchers available - not in the initial kit, appeared after a second OTA;
Screenshots
Excellent job !
Booroondook is on XDA also, hes posted a good few times in the "original thread" (RIP - the thread, not Booroondook !).
I was aware he used to make ROMs for these units, but this past year its all been about Malaysk's, not heard anything about @booroondooks's.
bootloop after instalation
Great rom in the first half hour
same here
zorantoma said:
Great rom in the first half hour
Click to expand...
Click to collapse
Mine won't even fully boot after the 2nd update from recovery..Good to see that its not just me..
Edit
Tried with a newly created image from the Bat file.
Still looped but I was able to get it to work from the recovery screen by using the "reset to factory/clear data option"
After that the setup script worked.
New version is out
New version is out, based on HA-20151204. Get it here.
The following is taken from the author's post on 4pda:
Since the original is only for RK3188 / 1024x600, the kernel versions for other combinations of CPU and resolutions are from earlier firmware:
RK3188 / 800x480 - from JY-20150824
RK3066 / 1024x600 - from HA-20151010
RK3066 / 800x480 - from KLD-20151127
New features :
1. Two factory launcher - "HA / JY" and "KLD" - you can change the settings (Display -> Desktop). Both are fully functional (weather, radio, music, Bluetooth)
2. Support for trip computer "Multitronics MPC-800" - no need for Xposed module
3. Changes to preinstalled applications in the "OEM" section:
3.1 preinstalled applications (can be completely or selectively removed (Settings - Applications)):
- Chrome
- Root Explorer
- Terminal
- Titanium Backup
- True Contacts
- DPI Changer
3.2 Preloaded set of Xposed modules
3.3 APKs for manual installation ( OEM ):
- AirPin PRO
- CarService 2.1.3
- DAB
- EasyConnected.HT01.4.0.4-151012
- GScript_v.1.1.2_Rus
- Headunit 2.15
- IOnRoad.apk
- Multitronics_2015-12-24_beta
- RemoteADB
- Torque
- TPMS
4. Removed DPI change from the "Settings". Added app "DPI Changer" (pre-installed)
Hi @m00n61,
Is the version you just posted the one for 1024x600 rk3188?
If I understood well, have to install that twice?
Thanks!
magnificus said:
Hi @m00n61,
Is the version you just posted the one for 1024x600 rk3188?
If I understood well, have to install that twice?
Thanks!
Click to expand...
Click to collapse
The link is for the so-called "constructor" that can generate the Rom for your CPU/resolution combination. Just follow the steps in the first post to generate the one you need.
If you come from stock or another ROM, yes, you have to install twice and clear data/cache before and between installations.
If you already have the previous version installed then you only need to install once and it will be upgraded, keeping all your apps.
Im still new to MTCB, will this rom work on my Eonon GA5151F? http://www.eonon.com/Car-GPS/Specific-Car-GPS/Mazda/GA5151F.html
Thanks in advance
SkiRac3rDud3 said:
Im still new to MTCB, will this rom work on my Eonon GA5151F? http://www.eonon.com/Car-GPS/Specific-Car-GPS/Mazda/GA5151F.html
Thanks in advance
Click to expand...
Click to collapse
It should work. looks like you have a RK3188/800*480 unit. To be sure, go to Settings ->About tablet and check the 3rd line. If it starts with MTCB, this ROM will work for you.
What about RK3188 with 1024*600? I only see 1024*600 for RK3066, not for RK3188...
m4f1050 said:
What about RK3188 with 1024*600? I only see 1024*600 for RK3066, not for RK3188...
Click to expand...
Click to collapse
Well, post #14 says:
"Since the original is only for RK3188 / 1024x600, the kernel versions for other combinations of CPU and resolutions are from earlier firmware."
So yes, it's there.
WARNING - THESE TOOLS WRITE TO THE DEVICE PARTITIONS DIRECTLY
If you don't know what that means...
THIS CAN REALLY SCREW UP YOUR ---
I HAVE ONLY TESTED THESE ON THE A2020U (NON-5G) - I CANNOT SAY THEY ARE SAFE ON ANY OTHER VERSION OF THE PHONE (YET)(If you want to test it on a specific model you own, send a PM or post and I can tell you to run a few (safe) things from these tools to make them compatible your phone.)
See my next post down for some more "beginner friendly" general tips and tricks for this phone, including some fixes for common problems and a quick guide for installing Magisk!
If you can't afford to brick your phone, these tools aren't made for you.
There aren't really any protections from doing damage. I made them for myself because doing them on a command line constantly is a pain. I'm just sharing them for two reasons:
1) So myself or other people have tools available to make it easier when advising someone on how to fix their phone.
2) For tinkerers who are okay taking the risk that they'll mess something up.
Thanks to @djkuz / @Unjustified Dev for the EDL tool. These scripts really just expand the use of fh_loader commands in that tool. If you are able to read C++ and want to understand fh_loader I suggest searching on google, the source code is available and from that you can better understand what the tool does / what the command line options do. Feel free to ask here too, I'll do my best to share what I know.
Anyway - below I'll go into plenty of detail of what each "tool" does and some helpful information about using them.
I write in a kind of permanent verbose mode, so if you're impatient and need a TL;DR for these... tough. =)
CURRENT VERSION: Version 1.1d
Changelog:
Version 1.1d:
- Fixed reset scripts
Version 1.1c:
- Fixed a typo in backup_GPT ¯\_(ツ)_/¯
Version 1.1b:
- Fixed errors in GPT_Tools - apparently these existed since v1.0 DO NOT USE PREVIOUS VERSIONS
- Removed the v1.1a download (use 1.1b)
Version 1.1a:
- Added script to find the COM port automatically
- Updated all scripts to use the COM port in the file COMPort (created by the above script)
- Added the missing AB Partition manipulation files (accidentally left out of v1.0)
- Added script to run the phone reset EDL command
- Fixed all the filename inconsistency in the XML files - HOPEFULLY. Please post any errors you find. Unfortunately this will make this version incompatible with v1.0 backups without some work - either rename your backup files to match the new format or use the old XML files included.
-- Especially fixed the XML typo of "uefi_sec.mbn" being backed up from both A and B to the same file (overwriting the A copy with B during an ALL backup).
- Added support for installing firmware packages created for this tool. Put them in the Firmware_Package_Restore directory and use the scripts included with them.
Basic Instructions:
1) Download zip (See attachment at the bottom, or here - Download from AndroidFileHost)
2) Unpack zip
3) Move folder to the root directory, or inside any chain of directories that do NOT have spaces in any of the names
4) Right-click on scripts and select "Run with Powershell" to run
5) If running scripts fails due to permissions, see these instructions: https://superuser.com/questions/106360/how-to-enable-execution-of-powershell-scripts
Make a "Complete Backup" (minus userdata):
1) Run Load Programmer
2) Run "backup_all"
3) Check the backup directory and verify the files were backed up and sizes make sense - a full backup should be 10,387,202,048 bytes / 39 files for the critical files and 1,626,697,728 bytes / 64 files for the non-critical (Don't include the port_trace log file when checking size)
Note: You will see a lot of "warnings" before the files begin to download, the program checking if the files already exist.
How to Use These Tools:
Important:
When the scripts run there will be a lot of information dumped to the console. It's not necessary to read all of that BUT - IF YOU DO NOT SEE THE ASCII ART "DONE" AT THE END of running any of these scripts it is likely the script encountered a serious issue. "WARNING" art is normal for some scripts, but "ERROR" means something went wrong.
None of these find the COM port automatically. It is possible (the EDL tool does) but it's just extra work I'm not paid to do =P
You will need to edit each program and change the variable at the top (usually $COMPort = "6") to whatever port number your phone shows up on.
Sorry that's inconvenient, but it should just be once per script - my port number never changes so it wasn't worth implementing automatic port finding.
This is no longer needed after v1.1a.
1. Load Programmer
This is a simple but extremely important tool! You need to run this before running anything else. This script will open a window that runs a command to open a connection to the phone (when it is in EDL / "9008" mode). The window will stay open until you close it. When working on backups I often need to re-connect the programmer, so this makes that easy - just alt-tab to it and hit enter. If you look at the script, it's fairly straightforward - just read the instructions on the screen after running it. The "secret sauce" for this is really the firehose protocol for our chipset that Unjustified Dev provided in the EDL tool.
2. Backup / Restore:
backup_all: This will backup everything on the phone EXCEPT for the huge userdata partition. It will create a backup in two directories, which I'll explain.."critical" / "non-critical": You can see that I have scripts to run these two "types" of backups. Non-critical DOES NOT MEAN NOT IMPORTANT. It means that it is not critical TO ME to back up those files EVERY time I do a backup, because they rarely change. They're EXTREMELY important to have at least one backup of for your phone. The "critical" backup files are files that change often, although some of them are extreme non-critical (cache for example). Use a different name than "critical" if you like, but the point is that only with BOTH backups run (which is what backup_all does) will you have a complete backup.restore_all: This will restore a full (both critical and non-critical) backup set. The backup files have to be in the "restore_critical" and "restore_non-critical" directories respectively. If you didn't make the backup you're trying to restore with this tool CHECK THE FILENAMES, e.g. if you used Unjustified's EDL tool you have to rename the "abl.elf" file his backup generates to "abl_a.elf" for mine. I put _a and _b on every partition that has an a/b version because I got tired of getting them confused. Of course you can always install a backup to either slot.Files moved to the "restore_" directories won't be changed at all by the restore process so you can cut/paste the files from your backup into the directory instead of copying them.
3. A/B Partition Manipulation
These are no more complicated than the backup/restore tools. But they are written to make manipulations of the A/B partitions easier.My main use for these is when I know I have a good, working ROM setup on slot A, I run A2B copy. Then no matter which slot I end up booting I'm sure it will work. (That is, if you have a working, booting slot, copying all the files from that slot to the other slot using this tool will make both slots the same.)Backup/Copy:run_AB-partition-backup: As it says, it will backup both the A/B partition files - WARNING this is NOT a full backup of the phone.run_AB-partition-swap: This will backup all the A/B partition files, then it will write the B files to A and A to B, effectively swapping the partitions and leaving you with a backup in case it screwed up. This backup is ONLY OF THE A/B FILES.. NOT the whole device!run_A2B-partition-copy (and run_B2A-partition-copy): These will do a backup of both A/B partition files, then write the A partition onto the B partition (A2B) or vice versa (B2A), effectively mirroring that partition.
Write/Restore:All the restore scripts try to find their files in the "restore_Partitions" directory - place the files from one of the backups to be restored there.restore_AB-partition-backup: Restore a backup of both the A and B partition files.restore_A-partition-backup (and B): Restore just the backup of one partition to the same partition it was taken from (A to A and B to B).restore_A2B-partition-backup (and B2A): These write from one partition backup to the other partition as the name suggests.
4. GPT Tools
These are some basic tools to directly interact with the partition tables - these are not going to be of any use to 99% of people, so just ignore them if you don't know what they do.run_fixGPT: This issues the --fixgpt command to each of the LUNs. USE AT YOUR OWN RISK. As I understand it, this will use the onboard device configuration information from each LUN (e.g. logical size) and try to rebuild the GPTs. It's similar to running patch XMLs, it can clean up flashing messes. It isn't magic and won't fix everything.Rarely will anyone need it unless they've been messing around with the flash tools recklessly... I certainly don't know anyone who would do something that dumb backup_GPT: Backup all of the header and footer (main/backup) GPTs for all the partitions (lun 0-5). I am not aware of whether any other models of the phone have more LUNs, so be careful if you're using this on a non A2020U phone.restore_GPT: Simply write an entire GPT backup set (both main and backup 0-5) onto the phone. The backups must be in the restore_GPT folder. This DOES NOT BACKUP before it runs so make sure you did your backup.
6. Set Bootable Partition:
Alright this one is important for everyone. There are two scripts here - one for slot A and one for slot B. These just run a simple command, but they will fix a common problem I (and probably others) have - when the ROM active-slot information does NOT match the partition (hard drive) bootable flag, the phone will bootloop EVEN THOUGH EVERYTHING IS GOOD.So when you flash an EDL backup (depending on which files you flash, I believe this happens because of either the bootloader or the GPT files) there is a chance the backup you're flashing was originally from a different slot than the one you're restoring it to. The config thinks it should be on slot A while the hardware thinks slot B should be booting.This will result in a fast ~3 second bootloop as the two disagree and reset.This tool changes which partition is expecting to boot - "1" for slot A and "2" for slot B.This does NOT change the active slot - the phone will continue to boot the same slot it's trying to boot. You just need to make the partition that it is trying to boot has a bootable flag.AFAIK there is no way to change the active slot (the one XBL (I think) is trying to boot), except through fastboot or when the phone fails to load the OS 8 times in a row (note - if it fail to load the OS - if the phone bootloops before "boot" is called it won't ever switch slots on its own).This was a common cause of fast bootloops for me before I figured this fix out.
It does no harm to try this as you can always switch again. If neither one works for you, then it's something wrong with the files you're flashing. If you know which slot the phone is trying to boot (the one it was on last), run the script that matches that slot.
7. Write "Unlocked" Bootloader and FRP:
Just like the original EDL tool, these very simply overwrite your existing (probably stock) bootloader (abl) files with the fastboot enabled version, and/or your FRP with the "unlocked" flag on (see description below). This will allow you to enter the bootloader menu (Vol+/- on booting) and use fastboot to unlock the bootloader.backup_FRP-and-bootloaders: As it says, this will make backups of both the FRP file and current bootloader files (ABLs).run_all: Literally just runs both of the below scripts *shrug*write_UD-bootloader: This automatically backs up both your existing A/B bootloaders before overwriting them (BOTH) with the unlocked/fastboot bootloader.WARNING - an unfortunate fact is that if you're using the stock ROM and you have this bootloader installed, it borks the USB mode so it's stuck in charge only. There's a way to fix it temporarily, I'll post it in my "tips" thread, but you have to do it every time you boot, very annoying. I can't fix it permanently because I don't know how the bootloader file was built!WARNING 2 - Android 10 will NOT BOOT with this bootloader installed. You can still install it, trying to boot will bootloop, but you can get into the bootloader menu and use fastboot - but there are no recoveries I know of that work with Android 10 right now, so there's very limited use to having fastboot right now. Hopefully we can get a port of TWRP 3.4 going for this phone..write_unlock-frp: This is also in the EDL tool, but maybe poorly explained - the FRP file holds the flag you change in the OS Developer Options to designate "allow bootloader unlock". If you FORGOT to switch that flag on and unlock, as I understand it, you get bootlooped. This can fix that for you without having to go through all the work of undoing that mess.WARNING - I have only tested this with a brand new factory reset OS WITHOUT any fingerprint/code set. It may not work if you set one. I warn against using this if you are not ready to lose your data. It's convenient if you just forgot, but if you set a pattern/fingerprint security and encrypted the filesystem overwriting the FRP might remove your ability to decrypt which would force you to factory reset. Again, I haven't tested it for that so it may work, but be careful.If you already screwed up and ran this to set the flag - the script runs a quick backup of your old FRP just in case. So you can try to restore that FRP and pray lol)
8. Specific Files:
This is just a generic program to backup/write(restore) "specific files".I include a "Reference.XML" which has a full <program> line for every partition you might want to write/read on the phone. To use this, you need to copy the lines from the reference XML into "rawprogram-specific-files.xml" for the files you want to read/write.As an example I already set up "rawprogram-specific-files.xml" with the two lines for "abl_a" and "abl_b" in it. So the script will backup or restore those files (provided you put the abl's you want to restore in the restore_files directory).I personally use this template a lot - I have one for ABLs, one for AOPs, one for BOOTs, and so on. If you are trying to fix a specific file(s) it's convenient.
9. Userdata Backup:
I put this last because, to be honest, I'm not sure how good of an idea including this even is.VERY IMPORTANT - DO NOT USE THIS USERDATA TOOL IF YOUR PHONE IS NOT THE 256GB VERSION!!!!!I will need someone with the 128GB version to send me their GPT files if they want me to make an XML that works for them. Because the userdata size for SURE depends on your phone version.Also, I wrote a script that breaks up the file into download slices (and can be written back to the phone in slices, of course) - one, to see if I could do it and if it would work (it does)... and two, so that in the horrible case that something goes wrong during the... nearly 2hrs of transfer time, for my 256gb image ... that I can at least not have to start all over. If something happens, you should be able to remove the entries in the XML for what you already have and start again.Finally - is it even worth doing? Is backing up the userdata even useful?I don't know yet.For an unecrypted pre-A10 phone I do know it works to fully flash ALL the files on the phone + the userdata all at the same time to return the phone to the exact "state" it was backed up in - all the apps and settings and everything, exactly as they were.But A10 is encryption enabled always, and it uses file encryption which sounds even worse for this idea.. and I don't know if the crypto keys change and when. So flashing an entire encrypted partition might just leave you unable to decrypt all, some, or none and you lose everything.OR it might just work - you throw the whole image on there and the decrypt key is the same, boom, easy backup.If anyone tries it, let me know how it goes (or doesn't). I'll update with any results I find.Update 1: I have confirmed that for the 256gb A2020U backing up the full phone and userdata allows you to restore the phone to that exact state. Doesn't matter if it's encrypted, password set or not, etc. If you backup the entire userdata image and reflash it that is where the phone will be. In most cases you also need all the other partitions too, but if they have not changed they don't have to be reflashed. (I confirmed going from encrypted with password -> encrypted with no password -> back up encrypted with password.. This is on Android 10 with its more complicated encryption).Another nice thing to note - of course the image of the phone will be the size of the partition (ie. 256gb for mine, 128gb for others). But if your phone storage is largely empty, you compress the backup using something like 7z once the image has been backed up. It won't take up so much space then. How much less? My 256gb image compressed is 4.5gb. lol.... it makes sense, the phone is new and there's basically no information on the userdata. Many of the pieces of my userdata backup have the same exacty hashes - meaning they are literally just all 0's... 260gb of zeros. Unfortunately you can't get away with just backing up part of the image as data could be anywhere. And over time as the sectors get written to, it will get more difficult to compress.Anyway, if anyone has a 128GB version they want to donate to science (kidding - I just need backups of the GPT) I can make the XML file to use for backing those up too.
Extra Note: All the programs automatically build a log of the console window, so if something goes by too fast just check the log. The fh_loader also creates a log and dumps it somewhat randomly about... lol.. the filename is port_trace.txt. This tends to get deleted and overwritten easily so if you want to keep it, move it when the script finishes,. it does often contain more information than the console shows - it can be useful understanding what's going on.
Extra Note 2: You'll notice a script "Create Hash List" in practically every directory. That's to strongly hint that using that script is super useful. All the files backed up through these tools, by definition, have the exact same size. If you hash your files though, you can tell if they have changed at all. This is extremely useful in troubleshooting problems.
How to install an EDL firmware package:
Note: This tool is specifically made for the firmware packages I posted. It won't work with any other package (although it can, with a little work).
1. Install the EDL tools
2. Run a backup of your phone! Even if it isn't booting.
3. Download a firmware package from this thread: [ROM][STOCK] Stock Firmware Packages (For Expanded EDL Tools)
4. Unpack the firmware archive into the tool directory "Firmware_Package_Restore"
5. Put phone in EDL mode and run Load Programmer
6. Run whichever "Write Firmware vX to Y.ps1" you want (X = firmware version, Y = A or B partition) (If you don't know which partition is currently booting, just install both.)
7. Wait for the install to finish ("done"), then reset the phone with either the power button or the reset tool
8. You might see a few bootloops and then the phone ask you to do a factory reset / system wipe.
9. Done.
PLEASE POST IN THE FIRMWARE THREAD _NOT HERE_ IF YOU RUN INTO ANY ISSUES!
Enjoy!
Also, while I'm here... some other helpful notes for this phone:
-------------------------------
General Information:
As of right now there are a lot of working options for Android 9 and quickly expanding thanks to work @Unjustified Dev did and work @rafyvitto is continuing to do! Check out some of his sGSI ROMs, lots of options!
Thanks to Unjustified LOS 16 is available for Android 9 also, and is the base install for most ROMs. See his threads for that. I may write up an install guide here that's a little more in depth than his.. not today though.
Upgrading to Android 10 with the bootloader unlocked is possible but requires a workaround:
You must unlock on Android 9 then use recovery to side-load the Android 10 update available from ZTE USA (HERE).
This will remove the fastboot enabled bootloader and requires a complete system wipe.
You will retain bootloader unlock.
Once you have updated to A10 you can run OTA updates to get up to the latest version.
Downsides to A10 include - NO RECOVERY (yet), NO CUSTOM ROMs (yet), and if you flash the fastboot enabled bootloader you CAN use fastboot, but you cannot boot- the phone will be in a bootloop until you restore the stock A10 bootloader.
-------------------------------
Resetting the phone manually:
In EDL Loop - Hold power for 20 seconds
In EDL Not-Looped - Hold power for 5 seconds
In System (booted after ZTE logo) - Hold power for 10 seconds
----------------------------------
Entering Modes:
All of these start by using reset above, THEN the button(s) below - in all except one case (EDL), when the phone resets it will vibrate and then show the blue ZTE logo.
When you feel the vibration you want to immediately release the power button and press the mode buttons.
This can be confusing and tricky - most people say "hold power + button" - that is incorrect. Most cases if you hold any button other than power the phone will not finish resetting until you release that button.
What you want to do is right before or as the phone vibrates, then you hold the button. Once the ZTE screen is up it is probably too late if you missed it. So hold power for your reset and be ready to push the button you want when you feel the vibration.
The one exception - EDL mode. For EDL mode you can (and must) hold the key combo just before/during the restart.
Recovery Mode: Vol+ Button
Factory Test Mode: Vol- Button
Bootloader/Fastboot Mode: Vol+/- Button (both) when phone is NOT plugged into USB (if you are too early pressing the combo, even with the USB unplugged, you will get EDL mode)
Emergency Download Mode: Vol+/- Button (both) when phone IS plugged into USB
--------------------------------
EDL Flash Errors (esp. when EDL looped):
There is NO indication the phone is even ON when you are EDL stuck/looped. Other than when you plug into the computer with the right drivers it shows up as a 9008 device (9008 mode is EDL for Qualcomm).
Even when you can see the phone on your computer, it can often "freeze" in EDL if it is left idle for too long (not connected to and being used by a Sahara programmer).
If you try the EDL tool or another flash tool and they give you errors related to the Sahara programmer not loading or no "hello", do this:
Reset the phone - use a clock to count if you need, has to be accurate since there's no indication of when it resets. Press down Vol+/- and the power button, count to 20sec, then release JUST the power button. Keep holding both of the volumes for another 5 sec, then release them. That will get you back into a fresh EDL. You can watch your Device Manager to see the phone disconnect as an indicator when to let go of the power button. If you mess up the timing, wait a bit before trying again so the phone isn't in the middle of rebooting.
Easiest way to tell if you're in EDL is to watch the Device Manager while you do it. Otherwise there is just a lot of guess work, since there's no logo or vibration when you get it right, phone just appears off.
--------------------------------
USB Mode Stuck After Unlocking:
Something about the fastboot/"unlocked" bootloader causes the USB mode when you boot in the OS to be stuck on "Charge Only" mode.
Luckily I found @meow sir 's comment tucked away in this thread, and he knew a way to fix it (thanks!):
1. Open the phone dialer
2. Dial in "*#*#DEBUG#*#*" (debug = 33284)
(Sometimes takes a little bit to open, but a debugger menu will open)
3. Select the 2nd option for USB
4. Pick the only option - this will unset some strange "testing" mode and you can use MPT again.
Unfortunately this fix doesn't stick, you have to do it every time unless you switch back to the stock ABL. =(
--------------------------------
Installing Magisk, Quick Guide:
- You must have your bootloader unlocked already! This works on both A9 and A10.
1. Use this tool to create a full backup! (backup_all)
2. Go into the "critical" directory created by the backup and find the files for boot_a.img and boot_b.img - rename them to boot_a_bak.img and boot_b_bak.img and keep that window open, need them in a second
2. Boot into the OS. Download the Magisk Manager APK from HERE
3. Copy the APK and both of those boot files to your phone, open a file manager and install the APK
4. Open Magisk Manager and click on "Install" for Magisk (upper right)
5. Select "Patch Boot ROM" (or whatever it says.. something like that..)
6. Navigate to boot_a_bak.img and patch it.
7. Go to your Downloads directory (where Magisk dumps the patched file) and rename it to boot_a_magisk
8. Go back to Magisk and repeat those steps for boot_b
9. Copy the two patched Magisk boot files to your computer, into the folder with your "critical" files backup.
10. Rename the Magisk files to "boot_a.img" and "boot_b.img"
11. Move all the files from the "Backup\backup_all-critical-(...)" directory to the "Restore\restore_critical" directory in my tools
12. Finally, reboot into EDL.. almost there!
13. Run "restore_all-critical" (don't forget to run Load Programmer first..)
14. It will restore all you files, kinda a waste of time - if you know how to use the "Specific Files" tool this is a perfect time to use it to flash JUST the boot files. But anyway - this will get it done.
15. When done flashing, reboot the phone and open Magisk Manager to confirm it is installed!
The Magisk team recommend you DO NOT FLASH your stock boot files back to uninstall it, instead they say you should run their uninstaller.zip. However, I am not sure how to uninstall it if you're on A10 since we don't have a recovery that can flash zips? (Unless the stock recovery works for that, I don't think it would..)
I suspect (but have not tried) that on our phone flashing the boot files back over Magisk will not really be a problem since the recovery and ramdisk are all wrapped up into the boot image. But I don't recommend trying it if you value your data! Fair warning.
---------------------------
Alright that's everything. Good luck!
This will be useful for a lot of folks on here, thanks for taking the time to look for a work around.
rafyvitto said:
This will be useful for a lot of folks on here, thanks for taking the time to look for a work around.
Click to expand...
Click to collapse
Glad to be helpful! Usually I lurk the forums getting information I need to unlock/root/etc lol.. but I saw I actually could contribute something to this forum so hopefully it encourages people to get interested in this phone. It's looking pretty sweet now that I'm not spending days fighting with bootloops!
Indeed,on the note of attracting more users. im going to be releasing something for the pixel lovers very soon ?
Thanks Bob!
I'm on A10 with unlocked bootloader. I made all EDL tool backups when on A9 but these were done before correcting the typos as suggested. So I am not confident of successfully flashing back to A9 (preference).
Therefore I will likely flash the magisk-patched boot files to attempt root and report my experience...
Sent from my ZTE A2020U Pro using Tapatalk
big thx, glad to see some life to this almost dev-dead device
Hey thanks for the post. I'm thinking about buying the phone but have a quick question. Can I update to the latest version of Android 9 before unlocking or will the OTA be Android 10. How would I go about updating to the latest version version of Android 9 and not go to Android 10. Can I download the Android 9 OTA from somewhere and flash that one? Thanks in advance for the help!
Crackass said:
Hey thanks for the post. I'm thinking about buying the phone but have a quick question. Can I update to the latest version of Android 9 before unlocking or will the OTA be Android 10. How would I go about updating to the latest version version of Android 9 and not go to Android 10. Can I download the Android 9 OTA from somewhere and flash that one? Thanks in advance for the help!
Click to expand...
Click to collapse
:good: I think your question borderlines on needing its own thread in the Q&A section but I'll answer you anyway...
Currently as long as you are on A9 when you get the phone you can just do OTA updates from firmware version 1.10 to 1.11 to 1.13 (not sure what android security update that is), after 1.13 it goes to A10.
There is an A10 firmware available from ZTE to SD card sideload. Once installed it has to be updated to the latest A10 via a couple OTA updates.
Going directly from A9 to A10 via OTA goes directly to the latest version.
You cannot flash the A9 OTA... because flashing an OTA is an oxymoron... but I guess you mean can you download the A9 firmware and flash them. The answer is... maybe. ZTE does not offer official downloads any A9 firmware for A2002U (USA version), only A10.
They do offer A9 firmware for A2020G (european) and I think other foreign versions (RU, CN). These cannot be interchanged, if you have the US or EU or CN phone you need to use that firmware... from what I have read. I could be wrong, I don't have those phones.
But there is an unofficial stock A9 firmware for the A2020U here on the forums, uploaded by @rafyvitto . That will get you to.. I forget.. 1.11? That can be flashed using the original EDL tool or, with a little modification, the EDL tools in this thread.
Additionally.. if I ever get around to it... I plan to upload all three A9 firmware packages for the US version which can be flashed with the EDL tools in this thread. Not sure if it's really necessary, but I have them.. it's just a matter of figuring out hosting them and spending the time to upload them.
bobthenormal said:
:good: I think your question borderlines on needing its own thread in the Q&A section but I'll answer you anyway...
Currently as long as you are on A9 when you get the phone you can just do OTA updates from firmware version 1.10 to 1.11 to 1.13 (not sure what android security update that is), after 1.13 it goes to A10.
There is an A10 firmware available from ZTE to SD card sideload. Once installed it has to be updated to the latest A10 via a couple OTA updates.
Going directly from A9 to A10 via OTA goes directly to the latest version.
You cannot flash the A9 OTA... because flashing an OTA is an oxymoron... but I guess you mean can you download the A9 firmware and flash them. The answer is... maybe. ZTE does not offer official downloads any A9 firmware for A2002U (USA version), only A10.
They do offer A9 firmware for A2020G (european) and I think other foreign versions (RU, CN). These cannot be interchanged, if you have the US or EU or CN phone you need to use that firmware... from what I have read. I could be wrong, I don't have those phones.
But there is an unofficial stock A9 firmware for the A2020U here on the forums, uploaded by @rafyvitto . That will get you to.. I forget.. 1.11? That can be flashed using the original EDL tool or, with a little modification, the EDL tools in this thread.
Additionally.. if I ever get around to it... I plan to upload all three A9 firmware packages for the US version which can be flashed with the EDL tools in this thread. Not sure if it's really necessary, but I have them.. it's just a matter of figuring out hosting them and spending the time to upload them.
Click to expand...
Click to collapse
Just wanted to chime in, interchanging firmware between each model is possible, you would only need to reflash your model/nonhos/tz partitions to the ones of your variant to have working ril/fod fp/sensors.
Ok Bob I gave it a go and successfully rooted my A2020U running stock A10 v2.09. This is my experience...
Firstly, my A2020U could not connect so I used the @Unjustified Dev Tool ("original tool") to easily determine my com port (i.e. 3). I edited the your scripts accordingly (using Notepad++) and got connected.
I'd rather not fiddle with the hardware buttons to change modes so I used the CLI to "adb reboot edl" to get into EDL mode.
I executed the backup_all.ps1 script.
It echoed several "warnings" indicating that it could not find files. However, the created backup folders did in fact include those files.
I noted that none of the "A" slot files include the "_a" postfix; the "B" slot files did include "_b".
Now I needed to transfer those boot files to my device by first rebooting my device and connecting via MTP.
I noted that the original tool offered a reboot menu option (but sadly only after executing a successful operation). So, not wanting to fiddle, I used the original tool to backup my boot files, then used the menu option to reboot; On my device I then manually selected it to connect via MTP.
After transferring the "boot.img" and "boot_b.img" files to my device, and installing Magisk Manager. I patched them and transferred them back to my PC.
To "flash" (restore) the patched files I decided to cut 'n' paste the two lines regarding them from your Reference.xml file into your rawprogram-specific-files.xml file, replacing your example lines.
I executed your run_write-files.ps1 script and it completed successfully.
Not wanting to fiddle again with the hardware buttons (just so that I can get the reboot option), I backed up the patched files using the original tool and rebooted. Now my device is successfully rooted.
Thank you!
Additional notes and suggestions:
1. Can you please investigate the "false" warnings? See my (redacted) log file attached;
2. It would be great if you could create/duplicate a script within your expanded tool set (or main program) to determine and set the appropriate COMPort (and teach us non-coders the actual commands);
3. Would you also consider investigating and including a reboot device script? (It looks like the original tool calls reset.xml);
4. Note that, at the time of reporting this, the latest versions for the Manager and Magsk are 8.02 (307) and 21.0 (21000) respectively, and that I had to switch the update channel to "beta" for the patched files to pass SafetyNet;
5. Because rooting is a likely use of your tool I am attaching my modified rawprogram-specific-files.xml file which targets the boot files for convenience.
bobthenormal said:
...
Additionally.. if I ever get around to it... I plan to upload all three A9 firmware packages for the US version which can be flashed with the EDL tools in this thread....
Click to expand...
Click to collapse
If this can help me get my A10 device to a state where I can install a custom recovery and cutom ROMs, I would appreciate it!
eKeith said:
Ok Bob I gave it a go and successfully rooted my A2020U running stock A10 v2.09. This is my experience...
Firstly, my A2020U could not connect so I used the @Unjustified Dev Tool ("original tool") to easily determine my com port (i.e. 3). I edited the your scripts accordingly (using Notepad++) and got connected.
I'd rather not fiddle with the hardware buttons to change modes so I used the CLI to "adb reboot edl" to get into EDL mode.
I executed the backup_all.ps1 script.
It echoed several "warnings" indicating that it could not find files. However, the created backup folders did in fact include those files.
I noted that none of the "A" slot files include the "_a" postfix; the "B" slot files did include "_b".
Now I needed to transfer those boot files to my device by first rebooting my device and connecting via MTP.
I noted that the original tool offered a reboot menu option (but sadly only after executing a successful operation). So, not wanting to fiddle, I used the original tool to backup my boot files, then used the menu option to reboot; On my device I then manually selected it to connect via MTP.
After transferring the "boot.img" and "boot_b.img" files to my device, and installing Magisk Manager. I patched them and transferred them back to my PC.
To "flash" (restore) the patched files I decided to cut 'n' paste the two lines regarding them from your Reference.xml file into your rawprogram-specific-files.xml file, replacing your example lines.
I executed your run_write-files.ps1 script and it completed successfully.
Not wanting to fiddle again with the hardware buttons (just so that I can get the reboot option), I backed up the patched files using the original tool and rebooted. Now my device is successfully rooted.
Thank you!
Additional notes and suggestions:
1. Can you please investigate the "false" warnings? See my (redacted) log file attached;
2. It would be great if you could create/duplicate a script within your expanded tool set (or main program) to determine and set the appropriate COMPort (and teach us non-coders the actual commands);
3. Would you also consider investigating and including a reboot device script? (It looks like the original tool calls reset.xml);
4. Note that, at the time of reporting this, the latest versions for the Manager and Magsk are 8.02 (307) and 21.0 (21000) respectively, and that I had to switch the update channel to "beta" for the patched files to pass SafetyNet;
5. Because rooting is a likely use of your tool I am attaching my modified rawprogram-specific-files.xml file which targets the boot files for convenience.
Click to expand...
Click to collapse
Nice! :good:
For the questions..
0. Thanks for the heads up on filenames! I completely missed that the _a files don't have the labels... As you probably noticed all the files are backed up correctly still (no missing/overwritten files), but I removed the _a from all the A slot files. That was my original "fix", so I guess I started building this package before I got annoyed by not having the _a/_b consistency. I'll update the correct XML file and upload it as a new version.
1. Don't worry about those! They're part of using the fh_loader interface. Warnings are usually just fine, ERRORS are bad. I'll add a note to the post when I get a chance so people don't get scared by that.
It's only when you do a backup the program is really only designed in the "writing" sense, for backups you literally run an identical XML to writing but you send a flag that reverses the process. So it weirdly checks if the files it is going to copy (which of course don't exist) exist, and it throws the standard warning, but then it just creates them (of course).
I can't turn those off without lowering the verbosity setting for that tool. I decided to leave it set to high because if someone has a problem and they post their log file (like so!) it's very useful to troubleshoot.
2. I'll think about it / try. Not very hard to program but a little time consuming.
I'll throw a copy of lsusb.exe in the next version. Windows port of the linux command. People can simply run that on a command prompt and it will list all the active COM ports/devices. If you're not familiar with it - you can also find out by clicking on the windows start bar or pressing the windows key and typing in "Device Manager". In the hardware list there is a category for COM ports where it lists them.
3. Yeah that's very easy I'll put one in the next version as well.
4. Helpful to know. Interesting that you needed beta to pass... I didn't think to mention I use the canary builds (not really recommended... the current one crashes when I try to hide Magisk Manager lol)
5. Thanks! Maybe I should make a directory specific to boot backup/write... but I do think anyone not comfortable doing the change you did might not want to be flashing their boot files anyway haha.. things to consider I guess.
As for getting you back from A10, definitely. I'll figure out how to upload them to one of those file sharing sites in a week or two.
In the mean time, with a backup from this tool you're safe (as far as bricking goes, you'll have to system wipe) to try rafy's EDL backup to revert to A9. I'll find the actual post... I should have been less lazy and linked it in my post lol... HERE - rafyvitto's EDL.
If flashing his backup doesn't boot right away try the tool I included to fix the bootable partition. If it still doesn't work after that (maybe mention here what happened) then just restore your backup.
Do you have the 128gb phone by chance?
Thanks much, especially for your detailed clarifications and convenient link!
I have the 8/256GB (P855A03_NA) model.
PS
I want to spend more time on ensuring I have a complete device backup before nuking with another EDL; will dedicate some time this week...
Sent from my ZTE A2020U Pro using Tapatalk
eKeith said:
Thanks much, especially for your detailed clarifications and convenient link!
I have the 8/256GB (P855A03_NA) model.
PS
I want to spend more time on ensuring I have a complete device backup before nuking with another EDL; will dedicate some time this week...
Sent from my ZTE A2020U Pro using Tapatalk
Click to expand...
Click to collapse
Oh nice, with the 256gb model you're good to use the userdata backup program too. Sounds ideal for you since, like me, you want a really bulletproof backup. If you run a full backup and then run the userdata backup you literally have a "phone state" so you can return your phone back to exactly where it was, not have to wipe system or anything.
Of course I'd hate to be wrong so as usual, do at your own risk! Lol. But I am using that method and it has worked great. The downside being over an hour of waiting for the userdata to download or upload... and having to store 256gb (for long term storage you can compress it down to literally a few gb).
I've been kinda busy, but working on getting some of those things from my last post done hopefully this week.
bobthenormal said:
Oh nice, with the 256gb model you're good to use the userdata backup program too. Sounds ideal for you since, like me, you want a really bulletproof backup. If you run a full backup and then run the userdata backup you literally have a "phone state" so you can return your phone back to exactly where it was, not have to wipe system or anything.
Of course I'd hate to be wrong so as usual, do at your own risk! Lol. But I am using that method and it has worked great. The downside being over an hour of waiting for the userdata to download or upload... and having to store 256gb (for long term storage you can compress it down to literally a few gb).
I've been kinda busy, but working on getting some of those things from my last post done hopefully this week.
Click to expand...
Click to collapse
That's great to know! Your user data backup option has simplified my life.
I will wait for your next revision to do a full backup plus user data before nuking.
I am looking forward to moving on from ZTE's A10 to one of Ray's ROMs...
Sent from my PH-1 using Tapatalk
Updated to 1.1a - kind of had to rush on some things so keep an eye out for mistakes, especially in the XML files, and let me know if you find any.
Should have an 1.09 (A9) firmware package up "Soon(TM)", just have to make the xml files then upload the file somewhere.
EDIT: Already needed to update to 1.1b - I found that the GPT_Tools had a big error that probably was there since 1.0 and no one noticed! Backups of the GPT should now actually work...
Thank you @bobthenormal !
Looking forward to your A9 EDL backup...
Sent from my PH-1 using Tapatalk
eKeith said:
Thank you @bobthenormal !
Looking forward to your A9 EDL backup...
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
It's up -- see the new thread.
I didn't have time to test it so make sure you backup but I'm 99,99% sure it will work. I tested it several times in the past, but to make the firmware package I took out all the (I hope) unnecessary files.
There's one thing I'm not sure of - whether you'll need to use the Fix Bootable tool after installing it. IF you need to, then I believe you will have to install it to partition B and then run fix bootable B. (The 1.10 backup was taken originally from the B partition).
If you find that it works without having to do that, let me know... it may not be necessary if wherever that bootable flag is stored didn't get included in the firmware package.
bobthenormal said:
It's up -- see the new thread.
I didn't have time to test it so make sure you backup but I'm 99,99% sure it will work. I tested it several times in the past, but to make the firmware package I took out all the (I hope) unnecessary files.
There's one thing I'm not sure of - whether you'll need to use the Fix Bootable tool after installing it. IF you need to, then I believe you will have to install it to partition B and then run fix bootable B. (The 1.10 backup was taken originally from the B partition).
If you find that it works without having to do that, let me know... it may not be necessary if wherever that bootable flag is stored didn't get included in the firmware package.
Click to expand...
Click to collapse
Thank you @bobthenormal !
I should be able to give it a go this weekend and inform...
Sent from my PH-1 using Tapatalk