• 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]

dragongart6505 said:
I actually keep forgetting that....doh >_<
So basically no better than the one in the rom atm. Except that it probably won't boot lol
Click to expand...
The new kernel works fine! :P I'm trying to build a multi-device kernel, but something happened to my source code o.0 so I have to start from fresh source and add the changes again, which i've needed to do for the repo anyway.
 
FattyAcidTrip said:
Ok it just happened to me two times in a row, both times it starts to chime that I got a text message than it reboots. Before on version 1.0 it would do it when I would access the microphone on the google search bar (Chimes than halfway through the chime than it reboots) or when I would access the mic in the keyboard and other random times it would reboot out of blue. Will keep you informed of anymore occurrences.
Click to expand...

Thanks for the info, I'll look into it. Might be something to do with the audio engine Zte has in place by the sound *lol* of it. (Not related to srs). Again my phone does not have these issues and I use those features frequently. I'm looking into adding a different engine entirely, but let's get this thing stabilized.
I have to break off for a few days til I can work on it again because unfortunately I have to backup all my stuff and prepare for a drive swap. Hopefully I can come across one with a faster speed, 5400rpm isnt enough to do what I need and the drive is being given to my business partner cuz I need the $ and he needs the drive. Mmm...SSD would be lovely but too expensive. I digress...
Cdz...could you upload a flashable zip of the new kernel in the mean time? I'll relink it in the OP then with comments to test the included one and switch if problems arise
 
Cdz...could you upload a flashable zip of the new kernel in the mean time? I'll relink it in the OP then with comments to test the included one and switch if problems arise
Click to expand...
Gotta come around irc for that. Keep the accidental breaks to a minimum. Still a lil unstable afaik.
 
rbheromax said:
Gotta come around irc for that. Keep the accidental breaks to a minimum. Still a lil unstable afaik.
Click to expand...
I probably could release a new version, but after I fix whatever happened to the source code last night -_-

It's probably as unstable as the one that's already released, but more battery efficient and universal, meaning it's better. I'll work on that tonight and tomorrow.
 
Ive been at this for a bit and I can not understand what I am doing wrong, just getting red light/bootloop every time I try to install this and I have to restore to a backup. I am definitely new to this, but I did not think I would have this much trouble. I am following your instructions precisely even watched your video.

What I do: adb devices, adb reboot-bootloader, fastboot boot cwm.img, then in cwm i wipe data, then wipe cache, then dalvik, then install awesomeromv1.1.zip, wipe cache, dalvik, reboot now select no, then i get bootloop... Where am I going wrong here please?

If anyone can help with this I would really appreciate this.
 
niche9111 said:
Ive been at this for a bit and I can not understand what I am doing wrong, just getting red light/bootloop every time I try to install this and I have to restore to a backup. I am definitely new to this, but I did not think I would have this much trouble. I am following your instructions precisely even watched your video.

What I do: adb devices, adb reboot-bootloader, fastboot boot cwm.img, then in cwm i wipe data, then wipe cache, then dalvik, then install awesomeromv1.1.zip, wipe cache, dalvik, reboot now select no, then i get bootloop... Where am I going wrong here please?

If anyone can help with this I would really appreciate this.
Click to expand...

Its prolly not you. Your phone might be rejecting the kernel much like a body might reject a blood transfusion. We're almost done with the kernel and that means an update to the rom which should boot for you :D
 
OK thanks for the fast reply. I was really hoping it was not me. Really appreciate all of your hard work guys thank you very much! This has been very fun to customize my phone.
 
niche9111 said:
OK thanks for the fast reply. I was really hoping it was not me. Really appreciate all of your hard work guys thank you very much! This has been very fun to customize my phone.
Click to expand...
The released version of the oc kernel works with most of the phones, but not all. Those that don't work get the reboot behavior you experienced. The new version that's almost ready for release fixes that.
 
niche9111 said:
OK thanks for the fast reply. I was really hoping it was not me. Really appreciate all of your hard work guys thank you very much! This has been very fun to customize my phone.
Click to expand...

Did you wipe system and data as well BEFORE flashing the rom?
Even though it says in CWM that its wiping those I'm not sure it is completely. Its important to do so when flashing a new rom because files get left behind, particularly the framework. As this is de-odexed any odex files left behind by the stock rom will cause this issue. If they are present the phone tries to load those, but the file they are linked to already contains the information its trying to get.
Give that a try and let me know. If not, then yeah its the kernel
 
dragongart6505 said:
Did you wipe system and data as well BEFORE flashing the rom?
Even though it says in CWM that its wiping those I'm not sure it is completely. Its important to do so when flashing a new rom because files get left behind, particularly the framework. As this is de-odexed any odex files left behind by the stock rom will cause this issue. If they are present the phone tries to load those, but the file they are linked to already contains the information its trying to get.
Give that a try and let me know. If not, then yeah its the kernel
Click to expand...

I agree when switching roms always format data and system and clear dalvik cache and regular cache
 
dragongart6505 said:
Did you wipe system and data as well BEFORE flashing the rom?
Even though it says in CWM that its wiping those I'm not sure it is completely. Its important to do so when flashing a new rom because files get left behind, particularly the framework. As this is de-odexed any odex files left behind by the stock rom will cause this issue. If they are present the phone tries to load those, but the file they are linked to already contains the information its trying to get.
Give that a try and let me know. If not, then yeah its the kernel
Click to expand...

Ya i made sure i did that, thanks for the suggestion though. :-)
 
brittnearl said:
Its downloading and asking to install:confused:
Click to expand...

dragongart6505 said:
Ah, ok. Well I'll replace FOTAKill again then. Last I checked (while testing release candidates) it didnt affect the PRL/Profile updates. Let's hope that stays true
Click to expand...

Confirming that my install of 1.1 also downloaded and is asking to install an OTA system update. It's tricky, as the message will pop up randomly without warning...one part of the screen becomes "ignore" and one part of the screen becomes "destroy 1.1"...roulette which side I'll be pressing at any given time ;)
 
Nice rom ...one small issue ...root explorer is a paid app and shouldnt be included in the rom. Thats warez and violates site rules. Just a heads up.
 
PaganRitual said:
Confirming that my install of 1.1 also downloaded and is asking to install an OTA system update. It's tricky, as the message will pop up randomly without warning...one part of the screen becomes "ignore" and one part of the screen becomes "destroy 1.1"...roulette which side I'll be pressing at any given time ;)
Click to expand...

Just go to system/etc/security and rename the otacerts.zip file to otacerts.bak and delete the update from cache/fota if its there and reboot. That should fix it until the OP removes it.
 
starkraving said:
Just go to system/etc/security and rename the otacerts.zip file to otacerts.bak and delete the update from cache/fota if its there and reboot. That should fix it until the OP removes it.
Click to expand...

I have personally tried this and it causes the update to download in the background indefinitely causing excessive data usage, which is why i added fotakill back to my rom :D
 
syrkles said:
I don't know did not try just flashed old recovery again reflashed rom and them reflashed touch recovery
Click to expand...

dragonhart6505 said:
Error message? Does the brittnearl's rom flash or the same issue?
Click to expand...

I think I know the issue, and I need to make a note of it in the OP of the new touch recovery thread.

When you go to install a zip, there is an option "Don't allow Old update-binary" that is marked with an "(x)". Select that option so the "x" goes away, and you should be good to go.

What is happening is PhilZ recovery attempts to use a new update-binary by default, but since all of the zips released use old update-binary commands, it fails to work. You need to unselect that option before flashing. dragonhart6505: you should look into replacing the update-binary :)
 
niche9111 said:
Ive been at this for a bit and I can not understand what I am doing wrong, just getting red light/bootloop every time I try to install this and I have to restore to a backup. I am definitely new to this, but I did not think I would have this much trouble. I am following your instructions precisely even watched your video.

What I do: adb devices, adb reboot-bootloader, fastboot boot cwm.img, then in cwm i wipe data, then wipe cache, then dalvik, then install awesomeromv1.1.zip, wipe cache, dalvik, reboot now select no, then i get bootloop... Where am I going wrong here please?

If anyone can help with this I would really appreciate this.
Click to expand...

Looks like youre missing system wipe.

And I loaded this ROM up last night. Pretty sweet. Just unlocked both cores and set both to 1.83ghz. Just scored 17938 on Antutu (right between Nexus 4 and GS3) not bad! Chrome literally loads 2x as fast and Pinball Deluxe is smooth as our Note 10.1. I noticed after a second reboot a few minor issues went away. A few persist. First is text to speech isnt working so navigation wont start and GPS wont work anyway. Nothing major though. Very good work.:smokingsomb:
 
trichome said:
Looks like youre missing system wipe.

And I loaded this ROM up last night. Pretty sweet. Just unlocked both cores and set both to 1.83ghz. Just scored 17938 on Antutu (right between Nexus 4 and GS3) not bad! Chrome literally loads 2x as fast and Pinball Deluxe is smooth as our Note 10.1. I noticed after a second reboot a few minor issues went away. A few persist. First is text to speech isnt working so navigation wont start and GPS wont work anyway. Nothing major though. Very good work.:smokingsomb:
Click to expand...

Thanks ^_^ on very early builds of the kernel I was able to achieve 21000+ on Antutu. Sadly it didnt like a lot of phones, mine and a couple others being the exception. Next release will have the stock kernel and a few zips containing the available kernels. Word to the wise they are known to not boot, but they will be there if you wanna try. If not, stock kernel will be available as well. Hoping CDZ/rbheromax/junkie2100 are still working hard to resolve these issues. Well get there eventually ;-)
As for the tts, it has recently been updated though it may not from the play store. There are apks available on various trusted sources to get it. Also I found that Google Play Services may be the cause of any greyed out service. That can be resolved by reinstalling it as well. Looking into these issues for next release
 
You must log in or register to reply here.
Back
Top Bottom