• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root root cricket zte grand x max

Hey there everyone, Im here to offer you all some assistance with getting a safer way to have full root access. Some of you may have seen the zips that i have made for the ZMax z970 which allow you to have full root access without losing TWRP. I can make these for the Grand X Max+ as well but i will need someone to supply me with the files I need because I dont own a Grand X Max+. If anyone is interested, what I need is a boot.img. You can copy your boot.img by installing terminal emulator and using fhe following commands(without the quotation marks)

"su"
"dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/boot.img"

You will have the stock boot.img in the root of your internal storage.
If someone can pull this file and upload it for me I can give all of you a much safer way of getting access to the system partition. I will also need a md5 checksum for the boot.img which you can get by using MD5 CHECKER. Post the md5 checksum along with the download link for the boot.img and I'll start making some stuff to help yall out.

Edit: What I really need is a stock system.img, boot.img, & recovery.img from someone who has not yet installed TWRP or supersu. To do this, install kingroot and terminal emulator and run kingroot to get temp root. Then open terminal emulator and enter the following commands without the ""

"su"
"cd /dev/block/platform/msm_sdcc.1/by-name"
"dd if=boot of=/sdcard/boot.img"
"dd if=recovery of=/sdcard/recovery.img"
"dd if=system of=/sdcard/system.img"

You will need to make sure you have at least 3GB of internal storage space before doing this just to be safe. The system.img will probably be about 1.5GB in size but could be bigger. I'm not sure because I have no way to check.
 
Last edited:
Masterchief87 said:
Hey there everyone, Im here to offer you all some assistance with getting a safer way to have full root access. Some of you may have seen the zips that i have made for the ZMax z970 which allow you to have full root access without losing TWRP. I can make these for the Grand X Max+ as well but i will need someone to supply me with the files I need because I dont own a Grand X Max+. If anyone is interested, what I need is a boot.img. You can copy your boot.img by installing terminal emulator and using fhe following commands(without the quotation marks)

"su"
"dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/boot.img"

You will have the stock boot.img in the root of your internal storage.
If someone can pull this file and upload it for me I can give all of you a much safer way of getting access to the system partition. I will also need a md5 checksum for the boot.img which you can get by using MD5 CHECKER. Post the md5 checksum along with the download link for the boot.img and I'll start making some stuff to help yall out.

Edit: What I really need is a stock system.img, boot.img, & recovery.img from someone who has not yet installed TWRP or supersu. To do this, install kingroot and terminal emulator and run kingroot to get temp root. Then open terminal emulator and enter the following commands without the ""

"su"
"cd /dev/block/platform/msm_sdcc.1/by-name"
"dd if=boot of=/sdcard/boot.img"
"dd if=recovery of=/sdcard/recovery.img"
"dd if=system of=/sdcard/system.img"

You will need to make sure you have at least 3GB of internal storage space before doing this just to be safe. The system.img will probably be about 1.5GB in size but could be bigger. I'm not sure because I have no way to check.
Click to expand...
I am waiting for my phone off eBay so I can repair mine. Should be Friday I can do that for you master chief.
 
Last edited:
I could probably supply these files, however I already have supersu and the new twrp installed. If there is anything I can do, please let me know.
 
Masterchief87,

If you have the time I would be very interested in your comparing the boot partition between the ZMax Z970 and our phone. I suspect that they are virtually identical as I believe that the only hardware difference is the display.
 
If one of you could get me a boot.img with an md5sum to go with it that would be a big help. I posted some instructions a few posts back.
 
If the terminal commands are too intimidating then just install Rashr Flash Tool and Md5 Checker from Google Play. Rashr will make a copy of the boot.img with one click. It will be stored in /sdcard/rashr/kernel-backups. Then open md5 Checker and navigate to the folder I mentioned above and select the kernel backup that rashr made and it will tell you the md5 checksum. Upload the kernel backup to Dropbox, Google drive, or whatever cloud storage you have(everyone with a Google account has 15GB Google drive for free) and post a link along with the md5 that you got from md5 Checker. This can be done in 5 minutes or less without having to type any commands.
 
We have confirmation that's the zmaz bliss pop romband others work on the grand x max +. Maybe this can help with building a rom or even full root.

There also a kernel that can be tried and tested for this phone from the zmax.
 
DrewOnion said:
We have confirmation that's the zmaz bliss pop romband others work on the grand x max +. Maybe this can help with building a rom or even full root.

There also a kernel that can be tried and tested for this phone from the zmax.
Click to expand...

So the max+ had a unlocked bootloader?
 
Do you need root to pull the boot img using the second method you posted master chief?
 
Last edited:
jvillejoe said:
So the max+ had a unlocked bootloader?
Click to expand...
The bootloader isn't completely locked or unlocked. You can Flash roms kernels and recoveries but you can only mount /system rw when you boot from the recovery partition. This means that in order to mount /system as rw while booted in Android you have to Flash the boot.img (your kernel) to the recovery partition and "reboot recovery" which will then boot you into Android with the ability to mount the system as rw. This is called system write protection and is designed to make the phone more secure by preventing you from being able to root it. We just so happened to be able to find a way around this by getting temp root and then flashing twrp and rooting through twrp. We should actually consider ourselves lucky because a lot of zte devices have all of the partitions write protected which makes root impossible.
 
Yeah this is my first ZTE device, and I've read they lock their devices down pretty solid. So basically the only system partition that isn't write protected is the recovery partition? Also I'm not rooted as of yet. Is ZTE known for updating their devices? I know wishful thinking, but I haven't gotten a straight forward answer from ZTE, or Cricket.
 
jvillejoe said:
Yeah this is my first ZTE device, and I've read they lock their devices down pretty solid. So basically the only system partition that isn't write protected is the recovery partition? Also I'm not rooted as of yet. Is ZTE known for updating their devices? I know wishful thinking, but I haven't gotten a straight forward answer from ZTE, or Cricket.
Click to expand...
It is highly unlikely that this phone will get a lollipop update. At the most they might come out with an update that will completely lock the bootloader and block kingroot from working without upgrading it to a newer version of Android. I have a favor to ask of you, would you be willing to temp root your phone and get the images I need to make a stock rom? It won't make any permanent changes to your phone and is 100% risk free. As soon as you uninstall kingroot and restart your phone it would be exactly the same as it was before.
 
It seems like nobody who has already rooted can supply me with these files. I can show you a way that does not require you to use a command line. It is very easy and would help a lot of other people who own this device.
 
jvillejoe said:
Sure, should I use the second method? I have used dd before, so that's not a problem either. Which ever works the fastest.
Click to expand...
Since you know how to dd we will do it that way because it will require less explanation in your case. Are you also familiar with how to check an md5?
 
You must log in or register to reply here.
Back
Top Bottom