-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root ZTE Max Stock B06 4.4.2 Deodexed, Custom, and Unmodified
- Thread starter SuperR
- Start date
-
- Tags
- zte iconic phablet
Odin89
Android Enthusiast
Hey guys, so I bought one of these off someone as is for $20 bucks. I have access to stock b06 recovery, and dfu but no ftm. Adb comes up as unauthorized when I try to enter adb commands (on KitKat I have to accept debugging while device is in os but I cannot because it will not power into anything other than dfu or stock recovery. honestly don't know how they messed it up but I am wondering if I can fix it. First off the stock recovery has errors and is somewhat dysfunctional but I believe I can use the apply update from SD card to fix, iv just never honestly used the stock recovery so I am unsure how to flash or what would be flashable through the apply update from SD. When I power into recovery it automatically spits out these errors
E: failed to mount /cache (invalid argument)
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E: can't mount or open /cache/recovery/last_log
E: can't mount or open /cache/recovery/last_install
E: can't mount or open /cache/fota/error _code
E: can't mount or open /cache/fota/source_code
Wiping cache partition or wipe data/factory reset in stock recovery spits out the same error codes. Also I have made a live CD with your stormer fix on it. Ran the fix, PC says the device has been unbricked 9412+0 records in 9412+0 records out. But rebooting to recovery leads me back to the messed up stock recovery. Any help at all would be amazing!!
Two things (not necessarily in order of importance):
1.You can try using this other unbrick tool that contains ALL partitions for this device in case something other than recovery is messed up.
2. Try flashing this update.zip from stock recovery. It is an official rom from zte that is stock recovery flashable.
Odin89
Android Enthusiast
Omw home to download now, tyvm!
Odin89
Android Enthusiast
When trying to update from stock recovery I get the error
E: failure closing /Dev/block/platform/msm_sdcc .1/by-name/misc
I/O error
Edit: also the tool starts and says unbricking device
8192+0 records in
8192+0 records out
DD: writing '/Dev/sdb' : Input/output error
1+0 records in
0+0 records out
Last edited:
Unfortunately I don't have any further advise. If you have access to fastboot mode on the stormer you could try manually flashing recovery.
Odin89
Android Enthusiast
Ok so progress made! I don't have access to fastboot or adb because the device was already updated to 4.4.2 (where I have to authorize adb and fastboot while os is running, I can't access the os) .running the fix_full.ISO must have fixed things a bit, now whenever booting to recovery I get no error messages, also the .ISO tool runs completely through without error or hanging. I can boot the system! It goes past boot screen and automatically says encryption unsuccessful. I tried to install update via SD card through stock recovery and run into this error
Assert failed: getprop ("ro.product.device") == "stormer | | getprop ("ro.build.product") == " stormer"
E: error in /tmp/sideload/package.zip
(Status 7)
Installation aborted
I looked up status 7 error and found it had to do with the asserts line in the updater script and removing it is kind of like a bypass. Tried to edit it and repackage ota update with edited updater-script but when I tried to install it gives me a footer is wrong error, am I doing something wrong? Familiar with any of these errors? And as always thank you for help! I see you guys have done a lot with the max since we were trying to test out the philz bugs
That is indeed an assert error, however it is strange that you get it with stock recovery and the stock update.zip. Not sure where to go from here. Sorry man.Ok so progress made! I don't have access to fastboot or adb because the device was already updated to 4.4.2 (where I have to authorize adb and fastboot while os is running, I can't access the os) .running the fix_full.ISO must have fixed things a bit, now whenever booting to recovery I get no error messages, also the .ISO tool runs completely through without error or hanging. I can boot the system! It goes past boot screen and automatically says encryption unsuccessful. I tried to install update via SD card through stock recovery and run into this error
Assert failed: getprop ("ro.product.device") == "stormer | | getprop ("ro.build.product") == " stormer"
E: error in /tmp/sideload/package.zip
(Status 7)
Installation aborted
I looked up status 7 error and found it had to do with the asserts line in the updater script and removing it is kind of like a bypass. Tried to edit it and repackage ota update with edited updater-script but when I tried to install it gives me a footer is wrong error, am I doing something wrong? Familiar with any of these errors? And as always thank you for help! I see you guys have done a lot with the max since we were trying to test out the philz bugs
@Odin89 - I should have said so before but I ran out of time...you can't edit the updater-script in an official rom and still be able to flash it in stock recovery. It breaks the signature in the zip.
edit: Have you tried wiping data from stock recovery? I ask because the encryption the error refers to is in the /data partition.
edit: Have you tried wiping data from stock recovery? I ask because the encryption the error refers to is in the /data partition.
Last edited:
Odin89
Android Enthusiast
Ah I see. Yes I have tried to wipe data/factory reset in stock recovery as well as clearing cache. If the ota updates update scripts aren't recognizing the phone as the stormer would it be possible it is a hardware malfunction, such as corrupt data partition? Your tool recognizes it. Its curious.
I have had similar problems with the update zip for the ZTE Sync.. Kept saying it wasn't a warp4 or something. Do you think there's a device name change involved in the update?
Odin89
Android Enthusiast
How would I be able to tell? Also I found this sry I forget link just screenshotted it and uploaded to my db later. https://www.dropbox.com/s/7uvb17qjtaj958i/Screenshot_2016-02-15-20-09-44.png?dl=0
Would this help? I would use it but somewhat unsure the " and >> uses
It may help if you could access adb in order to issue the commands. Unfortunately you said you can't so it won't work
95EscortDriver
Newbie
Sorry for the revival of a really old thread, but I have a question about installing Philz recovery: where do I put put it on the phone to install it? Do I need to ADB sideload it?
I've also got the same problem as Odin89 with the wipe cache erroring out, but instead of giving a error, it just locks up. Also, I did a MD5 check and it comes up with a ton of errors. I am rooted via Kingo Root, but that's as far as I got in this.
I purchased this phone used from Amazon, and the PO had updated it without using the partition updater, so I currently only have 1GB phone space, and 2GB internal SD storage, and is a nightmare to get the external to read. Is there a partition updater for 4.4.2?
Sorry for the long post, but hopefully someone can help
I've also got the same problem as Odin89 with the wipe cache erroring out, but instead of giving a error, it just locks up. Also, I did a MD5 check and it comes up with a ton of errors. I am rooted via Kingo Root, but that's as far as I got in this.
I purchased this phone used from Amazon, and the PO had updated it without using the partition updater, so I currently only have 1GB phone space, and 2GB internal SD storage, and is a nightmare to get the external to read. Is there a partition updater for 4.4.2?
Sorry for the long post, but hopefully someone can help
95EscortDriver
Newbie
*Update* Finally figured out ADB sideload and fastboot to get PhilZ to flash, installed the Deoxed ROM, and everything runs okay, but I have a feeling the error when wiping the Cache is still there, as it takes a minimum of 10 minutes to wipe, and the phone seems to lock up during that time, even in PhilZ Recovery. Was thinking of downgrading to Jellybean to do the partition updater, then upgrade back to Kit-kat and see if maybe some of the many issues resolve themselves. I know SuperR is a busy man and all, but a little advice may help. If needed, I could run a logcat and send it your way.
there is also the slight possibility that when I got the new UICC card from Boost mobile it clashed with it, since we had to do a ton of work to get it to even recognise it, as the numbers did not match the phone at all. That card was the 4th one they had sent me, the rest didn't even fit the slot, (looked like my old Iphone 4S's UICC card).
there is also the slight possibility that when I got the new UICC card from Boost mobile it clashed with it, since we had to do a ton of work to get it to even recognise it, as the numbers did not match the phone at all. That card was the 4th one they had sent me, the rest didn't even fit the slot, (looked like my old Iphone 4S's UICC card).