• 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:
Easy fix, dont get down just yet ;-)
Download the file from here and put it on the root of your sd card
Open up the zip and extract the Recovery.img to the folder with adb and fastboot. Turn your phone on by holding Volume UP/Power. Youll see FTM on your screen. Plug your phone in and open the command window like before. Type adb reboot-bootloader then fastboot boot recovery.img Your phone will boot to stock android recovery where you can install the update.zip and your phone will be out of the box new
Click to expand...

I did what you said above.
1. got he update.zip and put to root directory. (use adb push to get it there)
2. extracted the Recovery.img and ran via adb reboot-bootloader and fastboot bot recovery.img. (Phone didn't reboot, had to do it manually).
3. install update.zip and got error:
assert failed: getprop("ro.product.name" == "zte_nex"
E:Error in /sdcard/update.zip
(status 7)
Installation aborted

I'm going to try to download the update.zip again and reload it but I have done it twice now and the same effect. Any other ideas?

BTW, I appreciate the help. You are dealing with a senior citizen who is an old mainframe programmer, so you will have to excuse the senior moments. :-)
 
JimReid said:
I did what you said above.
1. got he update.zip and put to root directory. (use adb push to get it there)
2. extracted the Recovery.img and ran via adb reboot-bootloader and fastboot bot recovery.img. (Phone didn't reboot, had to do it manually).
3. install update.zip and got error:
assert failed: getprop("ro.product.name" == "zte_nex"
E:Error in /sdcard/update.zip
(status 7)
Installation aborted

I'm going to try to download the update.zip again and reload it but I have done it twice now and the same effect. Any other ideas?

BTW, I appreciate the help. You are dealing with a senior citizen who is an old mainframe programmer, so you will have to excuse the senior moments. :-)
Click to expand...

Its going to fail in cwm because it doesnt recognize the rom as the "zte-nex" that its looking for. Also it may take a little for the phone boot into the standard recovery from fastboot
Are you booting the phone to the FTM screen? Are you getting a black screen after typing adb reboot-bootloader? At the black screen type adb devices. Do a bunch of numbers show up under devices in the command prompt? There is no reason you should be having this issue if you are following my directions to a T.
If all else fails, boot back into cwm, wipe the device like in the instructions and try again follow everything exactly as its lined out. If necessary I'll post again with pictures on exactly what you should be doing.
And again...STOP TRYING TO INSTALL THE UPDATE.ZIP FROM CWM! Dont dont dont dont dont a million times dont
 
i will post a link to a stock update.zip that works with cwm be patient:D. slow upload speed. this will make your device completely stock again [NO ROOT]
 
dragongart6505 said:
Its going to fail in cwm because it doesnt recognize the rom as the "zte-nex" that its looking for. Also it may take a little for the phone boot into the standard recovery from fastboot
Are you booting the phone to the FTM screen? Are you getting a black screen after typing adb reboot-bootloader? At the black screen type adb devices. Do a bunch of numbers show up under devices in the command prompt? There is no reason you should be having this issue if you are following my directions to a T.
If all else fails, boot back into cwm, wipe the device like in the instructions and try again follow everything exactly as its lined out. If necessary I'll post again with pictures on exactly what you should be doing.
And again...STOP TRYING TO INSTALL THE UPDATE.ZIP FROM CWM! Dont dont dont dont dont a million times dont
Click to expand...

I'll try to answer all you questions so you know but just so you know I got it to work (back to original and have to start over with rooting, etc.) The one step that I missed in your instructions was where you said to do the reboot-bootloader, You said it would reboot and then install update.zip. It didn't appear to reboot just went into the stock recovery screen so I rebooted it and went into the CWM recovery screen which gave me the error. I did it again and installed the update.zip right after the reboot-bootloader and it installed and all was back to 'out of the box'.

I appreciate you sticking with me to get through this. Your great!! :D Just wish your ROM had worked and was thinking of trying it again now that my machine is back to its original state. Maybe the way I rooted it or something screwed things up. I'm going to make a backup right away and then start over with your ROM.

As to your questions:
1. Never saw FTM screen....ever.
2. I was confused as to where to install the update.zip, you were right I was trying from the CWM screen because when I rebooted it by hand that is the screen that came up. Then I notice that after the bootoader it was a different recovery screen (very similar) and I installed the update.zip from there and it worked.

So again. I appreciate you help and I'm going to try to reinstall your ROM because it sounds so much better than the stock one and I lost all my apps and settings anyway so I might as well try again.

Thanks again and hopefully I won't be bothering you again. :rolleyes:
 
dragongart6505 said:
Easy fix, dont get down just yet ;-)
Download the file from here and put it on the root of your sd card
Open up the zip and extract the Recovery.img to the folder with adb and fastboot. Turn your phone on by holding Volume UP/Power. Youll see FTM on your screen. Plug your phone in and open the command window like before. Type adb reboot-bootloader then fastboot boot recovery.img Your phone will boot to stock android recovery where you can install the update.zip and your phone will be out of the box new
Click to expand...

Don't know if you read all my other messages but I did get my phone back to stock issue. Then I thought I'd try again at installing your ROM as I had already changes some things on my phone. No Glory. Still would stick in the reboot process with the little green robot.

So I went back and recovered to the original phone and everything is back to normal (except I have a lot of work to update all the apps I had).

Thanks for your help and please let me know when release 2.0 comes out and I'll try again.

Jim :)
 
Sorry i havent been on in a bit but i have a new version ready for release once i get internet access. Fixed prl and profile updates, modded the settings menu a little bit and some other fixes. Full details on release.
 
dragongart6505 said:
Sorry i havent been on in a bit but i have a new version ready for release once i get internet access. Fixed prl and profile updates, modded the settings menu a little bit and some other fixes. Full details on release.
Click to expand...

Oh you are killing me man! :D
Seriously though, been looking forward to it. Very excited about it.
 
FattyAcidTrip said:
Oh you are killing me man! :D
Seriously though, been looking forward to it. Very excited about it.
Click to expand...

Its nothing MAJOR except for fixing PRL/Profile updates, completely removed the ZTE and Firmware update from the System Updates menu (renamed Network Updates) Activate this device (renamed Activation) also works, removed Connections Optimizer option from Mobile Networks menu (since it isnt available anyway) swapped Android Tuner for TricksterMod (will give details in FAQ on setting options for peak performance/stability) swapped to KK Launcher, and added Titanium Backup and Busybox On Rails (until I get busybox implemented permanently).
I think thats it for now. Lots more to do, including lockscreen quick settings and reboot menu. Those are my next main features to add, but probably one at a time. I'll see about just making them incrimental updates, but well see what happens.
I wont release anything until I have a chance to test it out on my own device and so far I'm loving it, so I hope you guys will too. The kernel is still the same so I dont know about the whole reboot thing. We do have another kernel available but I redid the updater-script and I want some feedback on whether or not it fixes those issues. If not I will rerelease with the new kernel.
I also found the 1.94 and 2.1 ghz kernels. They are reported to be UNSTABLE for most people though they work great for me. So if they dont work, dont say I didnt tell you so.
 
electro00nerd said:
How much longer dragonhart for this update ?
Click to expand...

Impatient much? :-P
Id like to roll out today, but I have to be able to get across town to my office to upload it. With this snow itll be a bit difficult. I really hate snow and I dont have a vehicle. Something about walking 2 miles in this isnt very appealing. And we have another one coming, so bleh.
I would have uploaded it from my phone...except upon testing if I fixed the PRL/Profile updates (which I did at that point) I broke my free internet. I'm on my g/fs phone to write back and forth now but shes throttled so it would take a few hours and she won't wait that long.
All good things come to those who wait
 
Nope thats saying that i cant Have a cookie when the cookie jars in front of your face...lol....jp yeah believe it or not i have a lot of patients
 
i hate d-hst...
QyeeX2r.png


20 friggin minutes!!!
 
electro00nerd said:
Are you gonna upload those kernels too?i want that 2.1 oc try it out
Click to expand...

Just to post this here: For everyone's information, the 2.1 oc is essentially a farce. It's a display bug (which has been fixed) causing it to display a higher clock value than it was clocking to. The real max clock value is 1.836, which is ~= the 2.1 oc.
 
cooldudezach said:
Just to post this here: For everyone's information, the 2.1 oc is essentially a farce. It's a display bug (which has been fixed) causing it to display a higher clock value than it was clocking to. The real max clock value is 1.836, which is ~= the 2.1 oc.
Click to expand...

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
 
So far I'm digging the update. No random reboots as of yet. No persistent "yada yada has stopped working" messages. I am getting a "Package file is invalid" when Google Search tries to update, a few of them did that at first but eventually updated. Otherwise it's very smooth and fast.

Question: My girlfriend wants to put the rom on her phone too but she really likes her swype. Is there a way I can put the stock version back on there for her?

Appreciate everyone involved for your hard work. This is my first android and so far it's been a fun learning experience. :D
 
FattyAcidTrip said:
So far I'm digging the update. No random reboots as of yet. No persistent "yada yada has stopped working" messages. I am getting a "Package file is invalid" when Google Search tries to update, a few of them did that at first but eventually updated. Otherwise it's very smooth and fast.

Question: My girlfriend wants to put the rom on her phone too but she really likes her swype. Is there a way I can put the stock version back on there for her?

Appreciate everyone involved for your hard work. This is my first android and so far it's been a fun learning experience. :D
Click to expand...

I will add it back in next release. You can rip the apk from the stock update.zip in /system/app/. Also Live Wallpaper support will be included.
Would like to see some more results concerning the reboots/bootloops on those who experienced them before I make these changes. Were you one of them?
 
dragongart6505 said:
I will add it back in next release. You can rip the apk from the stock update.zip in /system/app/. Also Live Wallpaper support will be included.
Would like to see some more results concerning the reboots/bootloops on those who experienced them before I make these changes. Were you one of them?
Click to expand...

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.
 
You must log in or register to reply here.
Back
Top Bottom