-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root [Rom/Kernel]AWEsome Rom[V1.6]
- Thread starter dragonhart6505
- Start date
-
- Tags
- zte awe
dragonhart6505
Android Expert
MD5 error due to it not recognizing the phone being the N800, similar to not being able to flash stock update.zip. Or could be a bad backup.
The date is a cwm bug. Never been right I dont believe lol
edodson84
Android Expert
I have found changing kernel makes backups fail md5 eg: backing up stock rom, flashing oc kernel, then trying to restore stock backup
dragonhart6505
Android Expert
Strange, I dont have this problem. Instead if I do as you suggested it restores my backup but keeps the kernel. I believe I reported this a while back during our testing of the recovery. I believe it doesnt restore the boot.img, or doesnt back it up
edodson84
Android Expert
Maybe it was a coincidence, when i flash different kernels i always got md5 error??
dragonhart6505
Android Expert
My phone...nuff said >_<
It seems to enjoy all the abuse I throw at it. Its just like me so a perfect match lmao
starkraving
Android Expert
This rom runs fine on my device, no issues. Came from rooted stock with no ota update.
dragonhart6505
Android Expert
The recovery doesnt make a single file, it splits the system/data/cache/boot into separate images. If there is only one file inside a folder with the same date (which will be wrong btw) then this is not a backup or is a bad one
dragonhart6505
Android Expert
Which recovery are you using?!
dragonhart6505
Android Expert
Its just an app that needs to be put back in. I can't seem to get it to work within the Phone app
A android B
Newbie
Which app specifically? Could i just extract it from the official update.zip?
dragonhart6505
Android Expert
Yea, its called vtt-"something".apk in /system/app . You will need to place it in the same folder with root explorer and change its permissions to rw--r--r
edodson84
Android Expert
This is a current issue with my rom as well, im looking into it
, no work around as of nowdragonhart6505
Android Expert
Only way to know is to flash and find out. I havent had too much time to look into it lately, but I will be releasing a version with stock kernel and flashable zips for alternates, but they have varying results as well. Hopefully when me and brittnearl get a chance to Hangout well get things stabilized.
dragonhart6505
Android Expert
Oh your stock? Idk then. Likely an app issue or just poor optimized android by ZTE. Only thing i can suggest is restore to factory from recovery or ##786#
DsyMnapTic
Android Expert
Okay so I have a bit to say. First off, this stuff above. I was messing around last night trying to figure out what the hell was going on. I flashed the latest version of philz touch recovery 6.19 and was seeming to have compatibility issues (eg: wasn't formatting anything properly) so I went back to 6.17 version and that one was formatting successfully, maybe a little slow but it was working. Anyhow I try to flash your Rom after I do the wipe and I get these errors. I'm not super tech savvy or anything, but I figured that by what it was saying was that something wasn't formatting properly from the Roms side, which obviously I attributed to the update.binary because that's what tells the Rom how to install. So out of curiosity, there's an option to disable use of old update.bi (whatever that is)...so it was checked by default and I unchecked it and after that it allowed the install of your Rom. What I'm saying is I don't know if this is helpful, but is it possible that there's a problem in your update.binary?
**other small things** I vote for either TouchPal or Swype to be included in future builds.
*seems to be an issue with defaults holding true (namely kitkat launcher for now)
*ummm, not sure what issue with new Philz touch recovery is?
*oh, tricksterMod doesn't allow you to do diddly squat without the donate version.
dragonhart6505
Android Expert
use cwm recovery. next revision will have the formatting removed
cooldudezach
Android Enthusiast
The issue is that newer CWM (this includes philz, it's based off of cwm) are based off of kitkat source code. Kitkat completely changed how the update-binary commands work, so until we start switching over to the newer syntax, you just have to uncheck that option. His update-binary is fine, just old lol
DsyMnapTic
Android Expert
That was my next thought, but I don't have an SD card yet, so if I want to flash from internal memory I have to use philz. I don't know maybe you want to tell people that they can flash the Rom with Philz if they just use the "allow use of old update.bi" option in recovery. I'm just curious, where is it getting the update.binary if it's not using the one from your Rom?