Note to NON SHV-E160L users
This software & this thread is aimed at developers Mainly, Please don't post 3 line request like "my device is bricked , please help" as you will be ignored, if you cant do the research required to provide the right details plus finding the correct files required then this thread is not for you and you should post in the device thread for your device, This program and it's associated files & thread is NOT being actively developed but the thread remains open for user to post more information, additional files, updates from the public etc.
It's not here for lazy people to scream fix my device, can those type of users please speak to your retailer, cell phone service shop.
I will reiterate again, THIS IS A DEVELOPMENT THREAD AND NOT A REQUEST PAGE FOR "fix my device"
PLEASE NOTE: This tool only comes pre-packed with files for the Korean SHV-E160L galaxy note. Usage on other devices requires that you understand the requirements, this includes but not limited to :-
1. Alteration of the scripts to use the files specific to your device
2. Correct HEX and SD-CARD loader also known as sdcard mbn
3. Correct partition information (knowing if it's MBR/GPT or hybrid)
4. Correct bootloaders for your device (SBL1/2/3/ABOOT)
I am not currently doing further development on this tool, it is here for anyone to expand on use how they seem fit so long as the authors involved are given the credit.
Users are welcome to build and post altered versions specific to their device but PLEASE post plenty of information as to what device/model it is for or the post may be deleted to protect other less educated users.
darkspr1te
Hi All,
I've updated my Debrick tool to Version 2.
Many Changes to the base code, inclusion of new tools, Almost a one click Linux solution for Qualcomm Development and debricking of Qualcomm devices.
As documented on this thread SHV-E160L home debrick thread I debricked a qualcomm based msm8660 device without using any special devices.
my first tools were internal development and had more bugs than a sewer, so after many hours of work i can now bring this new version to you.
Please do not pm with bugs, POST HERE Only.
This tool currently only supports the SHV-E160L , if users willing to provide the files from their devices I can expand the support of this tool.
in most cases linux is required for this, a ubuntu live cd/flash will work perfectly.
New Feature, Windows Based BACKUP of partitions and bootloaders, ROOT/Python27-windows is required and cannot function without this.
*nix backup coming soon,
Rules for posting backups
Post ONLY the link here, use www.sendspace.com to upload your backup zip (remember to change the .zip filename to reflect your device, example SHV-E160L-16GB.zip )
zip up only the backup folder, not the whole program, right click on backup folder, sent to compressed folder, rename.
this program does not backup personal or device specific data like IMEI number, it only backups the bootloaders, partition table and .pit file for samsung SHV based devices
When Posting links, please include your device details well, a example would be
SHV-E160L 16 GB, 9000lang rom,
The rom part is only so if we a tracing possible backup issues that may be rom specific.
Future backup features will include automatic detection of .mbn partitions based on qualcomm header.
Support for non SHV devices will be slow, but future versions will include other devices.
Well Enjoy,
EDIT: some users are reporting cookie not present error could be fixed by using a winxp/another qpst driver windows driver. this is unconfirmed bu i thought i should mention it. 04-12/2013
Changelog:- V2-2(dev version only - not a public release)
added command line device/folder parameter, you can now specify a unzip copy of posted bootloaders and it will restore them
added additional file to specify output sectors based on getpart data, testing option for building partition0.bin by hand based on known simalr devices
added dev switches for wiriting specified parts only
added skip aboot option (for now it is specified to skip writing of aboot.mbn, public release will be opposite, you will have to force writing aboot , sbl1/2/4/tz/rpm seems to come as one package, interchangeable as a package, aboot is totally device specific)
bugs:-
there is a known bug in the getpartbin.py python program, it cannot handle greater than 29 partitions.
Changelog:- V2-1
added windows backup.bat program to backup all bootloaders and partition0.bin
minor changes to code for changing device (current version support only changing of variable $DEVICE, feature will eventually be cmd line based)
tesing of backup files
bugs:-
there is a known bug in the getpartbin.py python program, it cannot handle greater than 29 partitions, and one will to help in python please let me know. I am not the author of the program
Changelog : V2
Improved error checking*
automated qdload detection*
automated qdload hex & .mbn upload
automated detection of device in sd-card mode*
user input*
colours
major code changes to start support for automatic parition information & collection allowing backup to be one command and upload to a website for distribution & recovery for all
development documentation
Code changes to allow expansion to other Qualcomm devices
Sendspace Links
BrixFix V2-1-Inc Python27-Inc cwm recoveries
http://www.androidfilehost.com/?fid=9390355257214632490 mirror tanks too Marduk191
Brixfix V2-1 No Python for windows, No cwm-recovery-Slim Version
Brixfix V2-1-Super-SlimNo drivers, bootloaders, python-win.
Media Fire Links
BrixFix V2-1-Inc Python27-Inc cwm recoveries
SHV-E160K 32GB Recovery files
SHV-E160L 32GB Recovery Files
SHV-E120L Recovery Files (posted on another page)
-------------------------
Here is the README
brixfix V2
=================================
By dakrspr1te ========Doc=V=1====
=================================
Thanks To :-
E:V:A, SLS, JCSullins(Rootz Wiki), Adam Outler, many more, sorry if i've missed you out.
Warning, Although i've tested this tool many times on my own devices, it always has the potential to damage both computer & cell phone device, YOU HAVE BEEN WARNED!!!!
This tool is designed to repair SHV-E160L Korean Galaxy Note 1 based on the MSM8660 & MDM9600 Qualcomm Chips
It Only works with devices that are stuck in QDLOAD mode or 05c6:9008 as the PID/VID
It uses Tool/info Written By Others as well as myself.
Namely :-
qdload - http://github.com/jcsullins/qdloader
getpartbin.py - http://blog.csdn.net/su_ky/article/details/7773273
hex2bin - hex2bin.sourceforge.net
Instructions
############
connect Qualcomm based device to usb port on linux PC, not tested under windows via USB redirection,
on command line run
sudo ./brickfix
Follow on screen instructions, tool will detect device in QDLOAD mode (05c6:9008) and switch to DMSS protocol, upload a hex (converted to bin for this purpose)
the hex is then executed and the device switches to Streaming Protocol, at this point we write a .mbn file to the internal emmc chip, at the end of the emmc write process the device then reboots
after the reboot re-running brixfix with detect the device in the second stage for repair , the device's emmc is accssable as a sd-card, we then write back the damaged parts of the bootchain,
at a minimum you must write a new partition table or the device will always boot in sd-card mode, WARNING, failure to write the rest of the boot chain could leave your device in a situation
which give only black-screen, no usb enumeration, dead. The only way around that is jtag, or finding the Boot resistor which switches the device back to QDLOAD mode, or emergency boot.
goto http://forum.xda-developers.com/showthread.php?t=1914359 for further details.
Come give me thanks on XDA if this tool helped you
Additional Tools (DEV Level)
===========================
getpartbin.py - A tool for backing up the primary partition & extended parition tables and combines them into a writable parition0.bin file (python)
qdload.pl - A tool for talking in the HDLC framed DMSS & Streaming Protocol's used by Qualcomm (Perl)
switchmode.sh - A executes qdload.pl for msm8660 device upload
get-part.sh - **DEV** unfinished tool by darkspr1te for creating partition tables in sfdisk format and .csv format (to be used in the future to create parition0.bin plus more automated collection)
tools/ - Folder containing armv5 (arm7 compatible) tools for parition manipulation and data collection
SHV-E160L-16GB/ - Folder contain SHV-E160L bootloaders & pit file
ADB/ - Folder containing adb programs
extras/ - Folder containing odin and clock work mode recovery installers for 160l devices
QUALCOMM/ - Windows drivers (For QPST, Not required in linux, included for backwards compatability with older guides)
hex2bin - convert your xxxxMPRG.hex file to bin for use with qdload
Tips
====
Additional
==========
I will accept brick qualcomm devices for developing further debricks. pm me via XDA Forums
Darkspr1te
Click to expand...
Click to collapse
Re: SHV-E160L Debricking Tool / Qualcomm Tool Pack
Kudos to u.
Nicely done ..OP
I'll get this thread added into the note super thread .
An amazing resource to be sure ...
Many thanks ....g
Very nice!
< reserved >
Thank you!
Re: SHV-E160L Debricking Tool / Qualcomm Tool Pack
I'll take a deeper look at it later.
You should note that qualcomm chipsets do not have support for USB 3.0. While the linux USB 3.0 driver is backwards compatible with the older standards, it is still buggy so it's best to only use USB 2 and lower ports.
Also, you should be using a 32bit Linux distro with a kernel from 2012 or later.
-SLS-
Will this work on SHV-E160S??
Two days ago I tried to flash the 'N7000XXLSA_N7000OXALSA_DBT' into a SHV-E160S.. Odin failed two times
When tried to reboot the phone nothing appears(just black screen). When i connect it to my PC, windows device manger shows ' QHSUSB DLOAD'..
Can this tool fix my problem? Please help me..
Re: SHV-E160L Debricking Tool / Qualcomm Tool Pack
BarakOsama said:
Two days ago I tried to flash the 'N7000XXLSA_N7000OXALSA_DBT' into a SHV-E160S.. Odin failed two times
When tried to reboot the phone nothing appears(just black screen). When i connect it to my PC, windows device manger shows ' QHSUSB DLOAD'..
Can this tool fix my problem? Please help me..
Click to expand...
Click to collapse
Probably. You'll need Linux. If you don't have linux, go grab the above mention ubuntu live cd (I suggest version 12.04 32bit)
As I'm not familiar with that device I don't know exactly what will need to be fixed.
-SLS-
Re: SHV-E160L Debricking Tool / Qualcomm Tool Pack
BarakOsama said:
Two days ago I tried to flash the 'N7000XXLSA_N7000OXALSA_DBT' into a SHV-E160S.. Odin failed two times
When tried to reboot the phone nothing appears(just black screen). When i connect it to my PC, windows device manger shows ' QHSUSB DLOAD'..
Can this tool fix my problem? Please help me..
Click to expand...
Click to collapse
Please state specs of your model, you flashed the wrong firmware which has crashed your pit/partition and your running a boot chain for another device, which is failing due to signing issues
By specs I mean device size, original few etc, we can recover it, I am sure of that, I just need some info , don't jump the gun, if we have your device files already it would be a simple case of running ./brixfix.sh I was able to recover all my files from my device, same would be you all sure, but you WILL need a copy of Ubuntu as SLS said
Sent from my A210 using Tapatalk 2
darkspr1te said:
Please state specs of your model, you flashed the wrong firmware which has crashed your pit/partition and your running a boot chain for another device, which is failing due to signing issues
By specs I mean device size, original few etc, we can recover it, I am sure of that, I just need some info , don't jump the gun, if we have your device files already it would be a simple case of running ./brixfix.sh I was able to recover all my files from my device, same would be you all sure, but you WILL need a copy of Ubuntu as SLS said
Sent from my A210 using Tapatalk 2
Click to expand...
Click to collapse
What files do you need from the ATT Note? I know what you have done, but don't understand it, but sure as hell would like to help !!!!!!!!!!
I have Ubuntu...(Yay !) ..... let me know the steps to dump files.
PS: Is there any chance of getting Tegrak kernel or ROMs for ATT Note. Maybe I should ask what is the status of the Tegrak kernel etc.? I see it on the app store, but I know its not for ATT Note. I remember Tegrak from when I used to use Voodoo Sound that Tegrak kernel supported. But I have never found anything comparable to voodoo sound for our more 'advanced' phones like the note.
PS: Does this make any sense to you ? Or am I rambling ?
Shv-e160s 32gb..
darkspr1te said:
Please state specs of your model, you flashed the wrong firmware which has crashed your pit/partition and your running a boot chain for another device, which is failing due to signing issues
By specs I mean device size, original few etc, we can recover it, I am sure of that, I just need some info , don't jump the gun, if we have your device files already it would be a simple case of running ./brixfix.sh I was able to recover all my files from my device, same would be you all sure, but you WILL need a copy of Ubuntu as SLS said
Click to expand...
Click to collapse
SHV-E160S 32GB, Thats all I know about this..
I'm downloading ubuntu right now. Then I'll try this tool on my device
Re: SHV-E160L Debricking Tool / Qualcomm Tool Pack
This tool works only on the 16gb right now, as soon as I can get a 32gb partition and S about file I will extend it
Sent from my A210 using Tapatalk 2
darkspr1te said:
This tool works only on the 16gb right now, as soon as I can get a 32gb partition and S about file I will extend it
Sent from my A210 using Tapatalk 2
Click to expand...
Click to collapse
Oh.. No luck for me then..
Tool Updated, Please go my OP
SouL Shadow said:
Probably. You'll need Linux. If you don't have linux, go grab the above mention ubuntu live cd (I suggest version 12.04 32bit)
As I'm not familiar with that device I don't know exactly what will need to be fixed.
-SLS-
Click to expand...
Click to collapse
BarakOsama said:
Two days ago I tried to flash the 'N7000XXLSA_N7000OXALSA_DBT' into a SHV-E160S.. Odin failed two times
When tried to reboot the phone nothing appears(just black screen). When i connect it to my PC, windows device manger shows ' QHSUSB DLOAD'..
Can this tool fix my problem? Please help me..
Click to expand...
Click to collapse
As soon as a user uploads a backup for the 160S (16 or 32GB depending on your device) I will include it in a repair file.
chappatti said:
What files do you need from the ATT Note? I know what you have done, but don't understand it, but sure as hell would like to help !!!!!!!!!!
I have Ubuntu...(Yay !) ..... let me know the steps to dump files.
PS: Is there any chance of getting Tegrak kernel or ROMs for ATT Note. Maybe I should ask what is the status of the Tegrak kernel etc.? I see it on the app store, but I know its not for ATT Note. I remember Tegrak from when I used to use Voodoo Sound that Tegrak kernel supported. But I have never found anything comparable to voodoo sound for our more 'advanced' phones like the note.
PS: Does this make any sense to you ? Or am I rambling ?
Click to expand...
Click to collapse
you can find all tegrak roms/kernels via my clean korean rom link in my signature,not sure on ATT but i've ported a few ATT kernels to the 160L so it's possible to convert back. *nix backup coming soon but for those that want to jump the gun, just run the same adb commands as in backup.bat and also the python command. please note they will download the files to the current directory so make a directory first, cd into it and refer back to the scripts. to run python partition0.bin script just use python ../getpartbin.py to create a partition0.bin file in current directory.
root is required for backup, python27 is required for windows backup (13mb file, included)
Thank
darkspr1te said:
As soon as a user uploads a backup for the 160S (16 or 32GB depending on your device) I will include it in a repair file.
Click to expand...
Click to collapse
I found some useful links (I hope) to the understanding of some mechanisms useful in debricking of devices using Qualcomm chipsets. I hope this may help generally, even to unbrick the i8150 (Ancora)!
http://blog.csdn.net/su_ky/article/details/7773273
http://www.anyclub.org/search/label/emmc boot
http://www.anyclub.org/2012/04/how-to-build-emmc-flash-programmer.html
Some stuff is in chinese, other in english but reading a bunch of articles I became convinced that the explanations available can be very useful!
Regards!
Just curious, why not post under original development? Love to see you there, you deserve it. :thumbup:
Sent from my SAMSUNG-SGH-I717 using xda premium
shv-e160L 32GB
Any success on the SHV-e160L 32GB yet?
Related
I have been working on some boot/recovery ROM rebuilds for the Garmin/Asus Garminfone A50 (T-Mobile), as well as the scripts and instructions... I'm not sure where to host them.
I personally don't want to host them myself, and was wondering if there is a repository of sorts.
At the moment, I have the following:
* The tools necessary (dump_image & flash_image) to dump the firmware from the phone
* The scripts necessary to unpack/repack the boot/recovery ROM's (modified to support the Garminfone's different address layout). Linux based.
* Pre-built boot and recovery images that give permanent root and mount the system/data partitions as r/w by default.
* Instructions on how to do it yourself, complete with some tech info on the layut of the Garminfone boot/recovery images and how to verify before you flash it that it built properly.
* Instructions on how to flash the phone without risking bricking it, since there is no hardware key combo to get into recovery and a fastboot that's not fully implemented. The technique goes like:
- Verify with a hex editor that the proper addresses are in the header
- Flash the new boot image to recovery
- Reboot into recovery to make sure it boots the new boot image properly
- Flash the rooted recovery image to the recovery partition
- Reboot into recovery once more and verify that works
- Flash the tested boot image to the boot partition
- Reboot normally and have fun
That method works fairly well, and unless you target the wrong partition, and gives you a 99.9% success rate
I'm going to post what I can on the Wiki (as far as instructions go), but it would be nice if I had a place to put the tool set as well.
I'd rather not use one of the temporary sites like Mediafire or what not, since files on those sites have a tendency to disappear.
Please no PM's on having me send them the files directly. I don't have a heck of a lot of spare time and don't want to get into the habit of sending these out manually.
If you're against the typical file hosts and the files aren't too big you could try using dropbox or sugarsync and sharing the links.
Can I ask you a question? I have a Kyocera ZIO M6000 and have the openzio clockworkmod 2.5.1.1 port that only works with "fastboot boot openzio-recovery" and we have tried flashing to our recovery partition with no success. What will it take to break the tether and reboot recovery locally without fastboot?
Sent from my Zio using XDA App
merwin said:
I have been working on some boot/recovery ROM rebuilds for the Garmin/Asus Garminfone A50 (T-Mobile), as well as the scripts and instructions... I'm not sure where to host them.
I personally don't want to host them myself, and was wondering if there is a repository of sorts.
At the moment, I have the following:
* The tools necessary (dump_image & flash_image) to dump the firmware from the phone
* The scripts necessary to unpack/repack the boot/recovery ROM's (modified to support the Garminfone's different address layout). Linux based.
* Pre-built boot and recovery images that give permanent root and mount the system/data partitions as r/w by default.
* Instructions on how to do it yourself, complete with some tech info on the layut of the Garminfone boot/recovery images and how to verify before you flash it that it built properly.
* Instructions on how to flash the phone without risking bricking it, since there is no hardware key combo to get into recovery and a fastboot that's not fully implemented. The technique goes like:
- Verify with a hex editor that the proper addresses are in the header
- Flash the new boot image to recovery
- Reboot into recovery to make sure it boots the new boot image properly
- Flash the rooted recovery image to the recovery partition
- Reboot into recovery once more and verify that works
- Flash the tested boot image to the boot partition
- Reboot normally and have fun
That method works fairly well, and unless you target the wrong partition, and gives you a 99.9% success rate
I'm going to post what I can on the Wiki (as far as instructions go), but it would be nice if I had a place to put the tool set as well.
I'd rather not use one of the temporary sites like Mediafire or what not, since files on those sites have a tendency to disappear.
Please no PM's on having me send them the files directly. I don't have a heck of a lot of spare time and don't want to get into the habit of sending these out manually.
Click to expand...
Click to collapse
I would also suggest dropbox or even id host them off my computer via ftp
Can your method work with Garminasus A10?
Merwin you still working on this?
Yeah, I am working on it still. I am still looking for a better place than dropbox or hosting off of someone's home PC...
As for the A10, if you can get me a dump of the boot and recovery images I can make one for that too... you will want to preferably use the dump_image utility to get the image and the flash_image utility to flash it.
I can probably attach those to a post with dump instructions. They're tiny.
Basically, you root your phone, copy the files to a certain location, type a couple commands to fix permissions on the executables, then run a command to dump the image.
Flashing back requires clearing the boot or recovery partition with a command and then using the flash_image command to flash it.
My method tests the new boot image first by flashing it to recovery first and rebooting into recovery to make sure the new image works. Then flash the modified recovery image to the recovery and make sure it is rooted (so you can get things up again if something does go wrong). Then you flash the new tested boot image to boot. If, for some reason, that fails, it should reboot automatically into recovery after a few boot failures. Never had to test that, since I pre-test all images I make.
hi merwin, we are a fans group of GA a10 and we trust a lot in your work! if you need any kind of help contact me! probably you are the first in the world who can flash a GA phone
Merwin, Im not completely sure which type of place your looking for if its not either ftp or online file sharing
Rapidshare
2shared
Filefront
4shared
Hi merwin,
I found this page, is that similar to your method? Hope you guys can find out something.
http://mygarminfone.blogspot.com/
afoster1003 said:
Merwin, Im not completely sure which type of place your looking for if its not either ftp or online file sharing
Rapidshare
2shared
Filefront
4shared
Click to expand...
Click to collapse
You forget one widely used protocol. Good old http on a standard web server.
Those other sites annoy me greatly, between the amount of ads, having to wait to download and daily limits, and the fact that they are temporary unless I pay. I am against them on principle.
I figure if there is enough interest, someone will step up to host them, otherwise I will just provide scripts, instructions, and technical info for people to do it themselves.
slumpz said:
Hi merwin,
I found this page, is that similar to your method? Hope you guys can find out something.
http://mygarminfone.blogspot.com/
Click to expand...
Click to collapse
You are my hero That blog has the missing pieces I need to keep going.
A couple of days ago I found some info on how to decompile the .update files which gives us the recovery image and system partition from any other phone that uses a similar format, like the Asus A10... providing a whole host of opportunities for the Asus phones that are still being maintained.
For instance, I grabbed the files from the Chinese A50 that has newer firmware.
With the info from the blog, I may be able to at least compile and integrate the newer kernel and wifi firmware (which is stored on the phone and loaded into memory at boot). The Chinese version does have newer wifi module firmware in it... whether it is compatible or not is another story.
On another note, has anyone successfully downloaded the open sources kernels from Asus? I have tried every method on their site and all but a couple of the kernel versions in the zip are corrupt. One from march extracts fine, so I may use that as a base to start with.
merwin said:
You are my hero That blog has the missing pieces I need to keep going.
A couple of days ago I found some info on how to decompile the .update files which gives us the recovery image and system partition from any other phone that uses a similar format, like the Asus A10... providing a whole host of opportunities for the Asus phones that are still being maintained.
For instance, I grabbed the files from the Chinese A50 that has newer firmware.
With the info from the blog, I may be able to at least compile and integrate the newer kernel and wifi firmware (which is stored on the phone and loaded into memory at boot). The Chinese version does have newer wifi module firmware in it... whether it is compatible or not is another story.
On another note, has anyone successfully downloaded the open sources kernels from Asus? I have tried every method on their site and all but a couple of the kernel versions in the zip are corrupt. One from march extracts fine, so I may use that as a base to start with.
Click to expand...
Click to collapse
I have, magically I might add. I downloaded the source for v.5.0.70 and managed to get it compiled. The resulting files can be found on on my blog, the one Slumpz posted(I can't post links yet, lol.)
The only problem is, I don't have much experience with anything linux. But, If you have any questions Merwin, email me, [email protected].
Here's a little how to, just check my blog, or google: How To: Build Garmin-Asus Kernel from Source.
am willing to giv a subdomain/storage ftp access on this domain for the good of the community if it helps any
Domain darkjester.net
Disk Usage 5.4 / 1500.0 MB
Bandwidth 100000 MB (100GB)
Home Root /home/a2931495
Apache ver. 2.2.13 (Unix)
PHP version 5.2.*
MySQL ver. 5.0.81-community
Activated On 2011-05-15 14:42
Status Active
Hello guys, are you still working on this.
I found out that A10 has a new firmware posted, which is versioned 5.2.7 instead of 5.0.x like the others. I wonder if there's any method to test this firmware on foreign A10 (non Chinese firmware)?
So, got an HTC Sensation 4G... meaning not much more work on the Garminfone for me.
Still trying to find time to compile everything that I have done into some semi-coherent document with the unlocked boot and recovery images. I still have the Garmin, so if someone manages a huge breakthrough then I may pick it up again. Really didn't want to get rid of the phone but there just isn't enough community development going on to make it worthwhile.
By the way, the Garminfone GPS blows every other phone away. The Sensation 4G is crap in comparison.
If you just switched from iPhone or BB or this is ur first android. Read this thoroughly and see ur questions get eliminated by this guide. if you find this helpful than show your appreciation and hit that thnx button.
I don't take any credit I Googled everything. I do take credit of modifying some stuff in word. I won't have this Phone but I am just being helpful to the community.
Little in-depth information about Android. Must Read. Thank You Pirateghost.
Pirateghost said:
Android itself is OPEN. you can go and build your very own version of 4.0 ICS right now from source code. there are very few phones you can STABLY and RELIABLY run it on though.
The NEXUS line of phones exists for a reason. they are untouched by carriers (verizon teabagged the Galaxy Nexus a little), and do not have some stupid overlay on them. they are developer devices in that it is the first phone to get android updates straight from google (no manufacturer interference required).
every other phone is tainted with a manufacturer's UI. Touchwiz on Samsung phones (galaxy nexus is a samsung but they provided the hardware not the software), Sense on HTC, 'non-blur' on Motorola, whatever Sony calls theirs...lol, LG, etc
on top of that tainted Android interface is a carrier branding or lockdown (doesnt apply to the entire world, but im only referring to US here)
so google releases new version of Android
manufacturers build phone, and customize android to fit their model (this is where android almost stops being OPEN)
carriers get a hold of the manufacturers build of android and tweak and modify it themselves (more than likely they just tell the manufacturers what they want), as you know they love to include bloat and lock it down from the user
you receive your android phone after it has gone through all those steps....long process huh? we dont get updates to newer versions as quickly because of that long process...and they would rather us buy new phones instead of improving perfectly good hardware.
Android is open in the sense that manufacturers can use it however they wish, within reason. it is not necessarily meant to be 'open' to the average end user, and manufacturers dont want you messing with the phone they built. its the reason XDA is what it is today, albeit with roots deep in WinMo hacking.
Click to expand...
Click to collapse
ADB → Android Debug Bridge (adb) is a versatile command line tool that lets you communicate with an emulator instance or connected Android-powered device..
Android →Unveiled on 5 November 2007, Android is a mobile operating system running on the Linux kernel developed by Google.
AOSP → Android Open Source Project
Apps2SD → Move applications from the internal NAND memory on the device to a removable SD Card.
BLN → BackLight Notification
Bloatware → Software bloat is a process whereby successive versions of apps include an increasing proportion of unnecessary features that are not used by end users, or generally use more system resources than necessary, while offering little or no benefit to its users. Like all the crap that comes from At&t
Brick → When used in reference to consumer electronics, "brick" describes a device that cannot function in any capacity (such as a device with damaged firmware). This usage derives from the fact that some electronic devices (and their detachable power supplies) are vaguely brick-shaped, and so those which do not function are useful only as actual bricks. The term can also be used as a verb. For example, "I bricked my phone when I tried to modify its firmware."[
Hard Brick → When your phone does not turn on at all. When you can’t get in to CWR/CWM Or Stock recovery. You are basically screwed.
Soft Brick → When your phone bootloops. When you can get into CWR/CWM. When You can use jigtag to get into download mode.
Busybox → BusyBox provides several stripped-down Unix tools in a single executable. It runs in a variety of POSIX environments such as Linux, Android, FreeBSD and others, such as proprietary kernels, although many of the tools it provides are designed to work with interfaces provided by the Linux kernel. It was specifically created for embedded operating systems with very limited resources. Platforms counterparts, but they are pretty close and useful nonetheless.
CWR OR CWM ClockworkMod Recovery →A custom recovery for Android phones and tablets that allows you to perform several advanced recovery, restoration, installation and maintenance operations on your Android device that aren’t possible with the stock recovery.
DEODEX → Apk files have respective odexes that devs use to supposedly save space. Deodexing means you convert it back to a .dex file and put it back inside the apk. This allows you to easily replace file (not having to worry about odexes), but the main point was to deodex services.jar so that you can change all text to different colors (such as the clock color to white) and to deodex services.jar, you need to deodex everything.
Flashing → The process of applying a firmware image (or ROM) to a device. It generally entails a very specific order of steps. Failing to complete any one of these steps properly may result in bricking the device.
Firmware → is a term often used to denote the fixed, usually rather small, programs and/or data structures that internally control various electronic devices. Programs stored in the ROM, EPROM, or flash memory that usually control various internal electronic devices (Hard Drives, Keyboards, Displays, etc). Firmware is typically 'fixed' software that is not updated in consumer devices, however it is often updated (or 'flashed') by advanced users to fix bugs or add features to the device. Flashing firmware designed for one device onto a different device, or not following a specific procedure while flashing will often render the device unusable.
Kernel → is the main component of most computer operating systems; it is a bridge between applications and the actual data processing done at the hardware level. The kernel's responsibilities include managing the system's resources (the communication between hardware and software components
Radio → The cellular radio on the device which needs control software called firmware to control it.
ROM → Read Only Memory. In the context of an Android device, ROM is the internal flash memory where the core operating system resides. It can also refer to a specific version firmware that can be applied to a device through a process usually referred to as flashing. An improperly flashed ROM can often brick the device, rendering it unusable.
Superuser→ A program, which gives unlimited access privileges to perform any or all operations on the operating system.
ODIN → Odin is the Samsung software used to update Samsung phones. It does not work with any other devices other than official Samsung phones.
OTA or FOTA → (F)OTA stands for (Firmware) Over The Air and is the process by which required updates and enhancements to your phone's basic operating system can be sent to you through the cellular network. The Galaxy S II software update will be sent via FOTA and is available through Samsung Kies mini.0
ODEX → In Android file system, applications come in packages with the extension .apk. These application packages, or APKs contain certain .odex files whose supposed function is to save space. These ‘odex’ files are actually collections of parts of an application that are optimized before booting. Doing so speeds up the boot process, as it preloads part of an application. On the other hand, it also makes hacking those applications difficult because a part of the coding has already been extracted to another location before execution.
SDK → Software Development Kit.
Logcat → A debugging tool built into Android devices that displays system logs as they occur. See Logcat.
NANDroid → A set of tools that will enable anyone who has root on their Android device to make FULL system backups, in case something goes wrong or you want to try out that new experimental ROM/theme. NANDroid will backup (and restore) /system, /data, /cache, and /boot partitions.
Recovery Mode → A special environment that you can boot into for troubleshooting and upgrading purposes.
Kang → The process of creating a code based of someone else's code or reapplying code that someone else created into your own code (e.g. git cherry-pick)
Rooting → is a process that allows users of mobile phones and other devices running the Android operating system to attain privileged control (known as "root access") within Android's Linux subsystem with the goal of overcoming limitations that carriers and manufacturers put on some devices.
How to Root Your note????
There are two root methods for YOUR ATT GALAXY NOTE!
1 which uses kernel to root.
2 This one flash with Odin but in system level not boot kernel.
#1 root by Da_G!
Da_G said:
Hi!
This kernel enables custom boot animations (/system/media/sanim.zip), adb root, init.d support, runs a script to auto-root your /system partition, and then you're on your merry way
You may need the USB Drivers available here. (Support & Downloads for SGH-I717)
Once the USB Drivers are installed, power off the phone, then hold volume down and power it on, you'll get a screen asking you to hit vol up to continue, do so. This puts the phone in download mode.
Stick the provided pda.tar in the PDA box of Odin3 1.85, flash away!
Install Superuser from the market after booting.
Note that this will increase your flash counter, which is presumably used by Samsung as a reason to decline warranty service (not aware of any reports of this occuring yet...?)
Don't forget the donate link in my signature if you found this useful and want to motivate me to work on overclock/undervolt
Click to expand...
Click to collapse
#2 Root by mashi!
How to backup your current ROM????
Hard Way!
Get into CWR!
Scroll down to backup and restore!
Press backup.
How to Restore Your backup????
If You used ROM manager than!
Go to manage and restore backups!
And press the one you like to restore!
If you have Nandroid than!
Go to CWR!
Scroll down to backup and restore!
Press restore!
How to Flash a ROM????
Basic Steps
! Choose the ROM that you want and download its .zip file
!! Transfer the zip file to your phone’s sd card. Do not put it into any folder.
!!! Turn off your phone and reboot into recovery, usually by holding the down button and power button at the same time.
!!!! Do a Nandroid backup
!!!!! Wipe the phone 3 times by clearing cache/factory restore 3 times and wiping dalvik cache and system format
!!!!!! Flash the zip file that you put on your sd card
!!!!!!! Reboot phone
You can find all ROMS here!
How to flash Kernel with CWM????
_Download the Kernel You want to flash and put it in sd card.
__Boot in to CWM!
___Wipe cache & Dalvik Cache
____Press install from Sd card!
_____Select the kernel that you dloaded!
______Flash it!
_______Reboot!
________Check in CPU SPY to see if you successfully flashed Kernel.
You can find Kernels in development forum.
These will set you back to Stock and Unroot Your phone.
Da_G said:
Hi,
This is an odin .tar prepared with the stock AT&T Kernel, System, and Recovery.
Flash it from odin using the same instructions as my root thread
After flashing, you may need to boot into recovery by powering off, holding vol up + vol down, and holding power until you get into recovery. Then perform a factory reset, this should get you up and running after most brickery.
Note that this is a large file (~450MB), please spare my web host if you don't particularly need it
Download .rar here
Below are stock kernel-only odin tars:
AT&T stock kernel-only odin pda tar
TELUS stock kernel-only odin pda tar
Bell stock kernel-only odin pda tar
Rogers stock kernel-only odin pda tar
Don't forget the donate link in my signature if you find this useful
Click to expand...
Click to collapse
Very cool thank you! I will finally be upgrading from an iP 3G!
LOL . . . . ever since I got it no phone really wowed me until I saw the G Note in November. Anywhoo. . . I was hoping for a noob friendly guide like this
appdroid said:
reserved 1
How to Root Your Skyrocket????
Click to expand...
Click to collapse
Not sure why do i need to know how to root the Skyrocket for the ATT Note here? just saying
Sry just fixed it.
sweetboy02125 said:
Not sure why do i need to know how to root the Skyrocket for the ATT Note here? just saying
Click to expand...
Click to collapse
look at you go! haha good work !!!
I figure this is the least i can do to help young community here!
00mred00 said:
look at you go! haha good work !!!
Click to expand...
Click to collapse
tx appdroid, us noob's really appreciate it!
(in all my years i never seen the "Reserve" post idea b4...it was a DUH moment for me lol)
Excellent guide for us that are really green on the Android platform.
thank you for helping this noob
appdroid said:
I figure this is the least i can do to help young community here!
Click to expand...
Click to collapse
I'm just so young and I need your help
How do you permanently change the hostname on Android?
On CyanogenMod ROMs this is easy, there was an option for it in Applications -> Development Options. But I don't know what hooks that uses and I don't know how to do it on this flavor of Android we have.
Thanks for your post, it help me a a lot. I done a little scripting on unix using mostly tcl. I hope I can get back on it and develop a few applications for this phone once I have it on march.
Thanks!
Thanks for the noob thread. Switched over from an iP4 and its taking a little getting used to. Luckily I already had the Revue and TF101 to help a little.
On a side note I found the http://forum.xda-developers.com/showthread.php?t=1505062 root method was very easy and didnt involve the counter getting screwed up or having to flash a whole new rom. Highly recommend it for anyone just wanting to root their device.
ANother Android Newbie
Coming from IP4 and looking forward to learning hot to make Android work for me.
How do I read your "Reserveds"???
For now simply follow the instructions and use the provided file download from the link posted below
http://forum.xda-developers.com/showpost.php?p=48392009&postcount=1
I have personaly tested this method in full on My AT&T Samsung Galaxy S4 ZOOM SM-C105AUCUAMJ2 (4.2.2 Jelly Bean)
although it should be safe to use on any AT&T Samsung Galaxy S4 ZOOM running an android version prior to Kit-Kat
All Credit for this, "exellent completely safe", Root method goes to its creator k1mu
And please Know that it is only being shared with you via his explicit permission.
EDIT:
Q&A for [ROOT] Saferoot: Root for AT&T Galaxy S4 ZOOM SM-C105AUCUAMJ2_On 4.2.2 JB
Please if you are not on an AT&T Galaxy S4 ZOOM C-150a, Feel Free to Read
but Do not seek help,instruction, or any other type of advice by posting in this thread as it is hard enough to find information about a specific device when the said device does not have a dedicated forum. Thank You for your Understanding in this.
Instructions & Advice
If ?'s arise
and time allows I will add device specific instruction as well as any advice, Please bear with me. Same as above Q&A Link
Will this same method also work on the SM-C105AUCUAMJ2?
kbracing6 said:
Will this same method also work on the SM-C105AUCUAMJ2?
Click to expand...
Click to collapse
Most Definitely as this was the reason for my post
Hey @Phatboyj420, as far as converting a raw OTA file to Odin files, here's what I can tell you. The OTA file should be filename.cfg, i.e. a cfg file. Believe it or not, this can be manipulated like an archive (like zip or rar or tar) so open that cfg file in 7zip, WinRar, or whatever. You're going to want to extract the files like (I can't guarantee this a full list, just the ones I can remember) modem.bin, NON-HLOS.bin, boot.img, recovery.img, aboot.mbn, rpm.mbn, sbl1.mbn, sbl2.mbn, sbl3.mbn (you might not have all 3, idk), and tz.mbn. Again, there may be others you need, and/or not all the ones I just listed might be necessary, they're just the ones I remember dealing with before. Oh, you're going to need to make sure the system, cache, and persdata partitions are all packed into .img.ext4 files, idk if they're like that in the OTA cfg archive.
Here's where it gets even hazier for me. So, I know from personal experience that you can take any of these files (I'll just use recovery.img for this example). In a linux terminal (I use Ubuntu for convenience's sake, my laptop has windows and ubuntu partitions) run this command:
Code:
tar -H ustar -c recovery.img > recovery.tar
So that's how you can take any one of those files I mentioned last paragraph and pack it into an Odin-flashable tar. I'm still a n00b when it comes to the linux terminal, so I can't really say the syntax for packing more than one at once.
So I guess I haven't really given you the complete process, but hopefully this is at least a decent starting point. Honestly I consider myself a hobbyist at best, not an expert. muniz_ri, who Devo7v mentioned earlier, did all the heavy work in this regard so he can probably help you much more, I just didn't want to volunteer him for the job
thisisapoorusernamechoice said:
Hey @Phatboyj420, as far as converting a raw OTA file to Odin files, here's what I can tell you. The OTA file should be filename.cfg, i.e. a cfg file. Believe it or not, this can be manipulated like an archive (like zip or rar or tar) so open that cfg file in 7zip, WinRar, or whatever. You're going to want to extract the files like (I can't guarantee this a full list, just the ones I can remember) modem.bin, NON-HLOS.bin, boot.img, recovery.img, aboot.mbn, rpm.mbn, sbl1.mbn, sbl2.mbn, sbl3.mbn (you might not have all 3, idk), and tz.mbn. Again, there may be others you need, and/or not all the ones I just listed might be necessary, they're just the ones I remember dealing with before. Oh, you're going to need to make sure the system, cache, and persdata partitions are all packed into .img.ext4 files, idk if they're like that in the OTA cfg archive.
Here's where it gets even hazier for me. So, I know from personal experience that you can take any of these files (I'll just use recovery.img for this example). In a linux terminal (I use Ubuntu for convenience's sake, my laptop has windows and ubuntu partitions) run this command:
Code:
tar -H ustar -c recovery.img > recovery.tar
So that's how you can take any one of those files I mentioned last paragraph and pack it into an Odin-flashable tar. I'm still a n00b when it comes to the linux terminal, so I can't really say the syntax for packing more than one at once.
So I guess I haven't really given you the complete process, but hopefully this is at least a decent starting point. Honestly I consider myself a hobbyist at best, not an expert. muniz_ri, who Devo7v mentioned earlier, did all the heavy work in this regard so he can probably help you much more, I just didn't want to volunteer him for the job
Click to expand...
Click to collapse
Thanks My guy,
This definately gives me a good jumping off point.
The phone shipped with JB-4.2.2 and I think there has been an AT&T OTA for KK so it would have to be a complete Firmware so thats good news.
I'm working on several projects at once so I don't know exactly when I'll get to this but when I do the first thing will be to verify whether the .img's for data/system/cache are img.ext4 or not and if not how to produce correctly.
Also I don't have a Linux Dev setup yet I'm running Windows On a 2011 Dell XPS-17_L702x with an intel 2720 quad core. So from your post I take it Ubuntu would be your suggestion for Linux Distro. and should I make a separate Linux Partition and run from it, or run from a VM-Box inside of windows? Which do you think would be most efficient?
Now that I think of it I'm going to start a dedicated thread for development discussion for this specific device. If I start the thread in the Development section for the general S$-ZOOM but title it specifically for the " AT&T-C105a_ZOOM " do you think the mods would want to move it to the general Q&A section?
" I would hope that, as it would pertain directly to the development of the specific device they would see fit to leave it in the development section.
Sorry for the randomness of my thoughts but I will link you to the thread when I get around to starting on it.
For now I'm going to get back to work on the S4_Active for My daughters B-day I intend to have it Rooted and rommed out for her. When I get that done I'll make my way back to this Project, and start the dedicated thread.
Thanks again,
" I look forward to future collaboration as it seem we share a similar Hobie at the least ",
Phatboyj
Unfortunately for the few lonely SM-C105a users still hanging on out there this does not appear to be a completely effective root. I get this in dmesg: <3>[ 2130.920856] c0 Restricted changing UID. PID = 11580(su) PPID = 11575(sh)
capt_planit said:
Unfortunately for the few lonely SM-C105a users still hanging on out there this does not appear to be a completely effective root. I get this in dmesg: <3>[ 2130.920856] c0 Restricted changing UID. PID = 11580(su) PPID = 11575(sh)
Click to expand...
Click to collapse
What is your build # because this is a fully effective root method for the ATT SM-C105a running build# SM-C105AUCUAMJ2
Please elaborate on where your dmesg is coming from.
Is it from running Saferoot to obtain Root?
Or is it from some other function you are attempting after obtaining root?
@Phatboyj420 Great to see you here--when I'm sure your S4 Zoom is long gone. Yeah, that's my build and I should point out that I get that in dmesg only for certain operations in the system folder (trying to copy modules I think). No biggie, for day to day this method works fine. I'm more interested in whatever happened with that unbrick image you were trying to make from dd. Did you ever test it? Was it effective? My current efforts are focused on developing a reliable unbrick method for our phones. Rather than the complete image I think we may need to extract and flash the original bootloader in many cases. Can you provide any feedback on this?
capt_planit said:
@Phatboyj420 Great to see you here--when I'm sure your S4 Zoom is long gone. Yeah, that's my build and I should point out that I get that in dmesg only for certain operations in the system folder (trying to copy modules I think). No biggie, for day to day this method works fine. I'm more interested in whatever happened with that unbrick image you were trying to make from dd. Did you ever test it? Was it effective? My current efforts are focused on developing a reliable unbrick method for our phones. Rather than the complete image I think we may need to extract and flash the original bootloader in many cases. Can you provide any feedback on this?
Click to expand...
Click to collapse
@ capt_planit
while I have moved on from using my [email protected] S4-Zoom, I do still have it and the dd dumps of it the problem with providing said dumps publicly is that some "idiot would inevitably flash the complete dd.image to there phone giving them an exact clone of my phone explicitly the IMEI via EFS parition are my concerns.
That being said if I know that the dd.images were to be used in a proper manner, by say a knowledgeable Dev. I would gladly supply them to further /Kickoff Development,
It sounds as if we are of like mind but I found myself at a stand still and did not recieve any response from the plea in my Sig.
But rest assured if there is something I can do to assist I will.
as far as an unbrick.img for the Zoom c105a
I did make one but have had no reason to use it to know if it works or if the SD unbrick method even works for the Zoom like it does on the Galaxy S3 that the method was originally discovered on.
Even if it does work the SD-Unbrick method only gets you to a state where Download
mode works SO unless I am mistaken and you can access adb through Download Mode witch I'm pretty sure you cant, we would still be at a stand still as there is no stock firmware publicly available for our device " Ludacris I know " but true none the less.
Edit:
1 thing we need is the OTA update from JB to KitKat available for our device we need some one to extract it before updating then and only then might we be able to create an install-able firmware for our device.
if I'm not mistaken after you download the OTA update you should be able to find it in /cache/fota just zip the entire fota folder move it to your sd-card and make it available to me and we'll make it happen from there.
If you don't want to except the update just delete it at this point and reboot.
...
...
I think this user @awwar describes an inability to access download mode>here. In anycase, I think that thread would be a great place to post your unbrick. image. I think your dd image seems too small. But if you still have it, that is what @moomoo was asking for when he started that thread. I can't provide mine, except as separate img files. My understanding is that flashing an efs image won't provide a real IMEI. I think flashing some combination of boot, system, cache (I'm surprised this would be necessary) and recovery should get the operator some kind of system. But so far it doesn't seem to work that way. Your help getting some working phone flash would be greatly appreciated. I believe, BTW that the OTA is dead...
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.
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