Go Back   Android Forums > Android Phones > ZTE AT&T Avail (ZTE Merit) > Avail - All Things Root

New Forums: Nexus Player | Nexus 9
Like Tree5Likes
  • 1 Post By stayboogy
  • 1 Post By stayboogy
  • 1 Post By valueforvalue
  • 1 Post By stayboogy
  • 1 Post By algree

test: Reply
 
LinkBack Thread Tools
Old October 3rd, 2012, 06:38 PM   #1 (permalink)
Senior Member
Thread Author (OP)
 
stayboogy's Avatar
 
Join Date: Jun 2012
Posts: 800
 
Device(s):
Carrier: Not Provided

Thanks: 39
Thanked 249 Times in 137 Posts
Default [OBSOLETE] ClockWorkMod Recovery for Non-Rooted Phones [temporary]


Advertisements
stayboogy is offline  
Last edited by stayboogy; November 3rd, 2012 at 02:24 PM.
Reply With Quote
The Following 2 Users Say Thank You to stayboogy For This Useful Post:
algree (October 6th, 2012), cell2011 (October 4th, 2012)
sponsored links
Old October 4th, 2012, 09:28 AM   #2 (permalink)
Member
 
Join Date: Mar 2011
Location: charleston WV
Gender: Male
Posts: 472
 
Device(s): warp
Carrier: wifi lol

Thanks: 41
Thanked 34 Times in 30 Posts
google now
Default

This is great for people that dont like adb commands to get rooted. I did this and backup and restore and then flash the real stock rom and now rooted on one two three. Couldnt be easier. Took less than 5 mins
cell2011 is offline  
Reply With Quote
Old October 5th, 2012, 08:04 PM   #3 (permalink)
Member
 
Join Date: Sep 2012
Posts: 152
 
Device(s): ZTE MERIT Z990G Rooted (net10)
Carrier: Not Provided

Thanks: 19
Thanked 31 Times in 29 Posts
Default

Very nice stayboogy glad to see you are making good progress.
valueforvalue is offline  
Reply With Quote
The Following User Says Thank You to valueforvalue For This Useful Post:
stayboogy (October 5th, 2012)
Old October 5th, 2012, 10:01 PM   #4 (permalink)
Senior Member
Thread Author (OP)
 
stayboogy's Avatar
 
Join Date: Jun 2012
Posts: 800
 
Device(s):
Carrier: Not Provided

Thanks: 39
Thanked 249 Times in 137 Posts
Default

Quote:
Originally Posted by valueforvalue View Post
Very nice stayboogy glad to see you are making good progress.
i wish i had figured this out before i rooted actually. it would have been nice to have a full stock nandroid of the merit without root.

and no one seems to be using this and posting their non-root nandroid like i have asked...

i may have to try to unroot my extra one and do this. idk if that will work or not though
stayboogy is offline  
Reply With Quote
Old October 6th, 2012, 12:43 AM   #5 (permalink)
Member
 
Join Date: Sep 2012
Posts: 152
 
Device(s): ZTE MERIT Z990G Rooted (net10)
Carrier: Not Provided

Thanks: 19
Thanked 31 Times in 29 Posts
Default

Un rooting might be a bit risky... I'm not sure or at best difficult. When I buy my backup merit I will be sure to use this method!
valueforvalue is offline  
Reply With Quote
The Following User Says Thank You to valueforvalue For This Useful Post:
stayboogy (October 6th, 2012)
Old October 6th, 2012, 05:34 PM   #6 (permalink)
New Member
 
Join Date: Jul 2012
Posts: 7
 
Device(s):
Carrier: Not Provided

Thanks: 6
Thanked 2 Times in 2 Posts
Default

Thanks a Million. I unbox'd a new merit ST. bootup while pluged into pc put your zip on root of sd card and then follow'd your instructions and made A CWM backup I'm uploading it to my GDrive and I will post a link when Its done.

PS: I used 7z to compress it 50%

and again THANKS I also downloaded your stock but rooted CWM rom I have'nt Tried to load it yet I'll let you Know how I made out

Here is a link to GDrive (Stock ZTE Merit_clockworkmod.7z)
https://docs.google.com/open?id=0B4BoCRM5_3JNQlRMYWd0THhDV0k
algree is offline  
Last edited by algree; October 6th, 2012 at 06:08 PM.
Reply With Quote
The Following User Says Thank You to algree For This Useful Post:
stayboogy (October 6th, 2012)
Old October 6th, 2012, 05:56 PM   #7 (permalink)
Senior Member
Thread Author (OP)
 
stayboogy's Avatar
 
Join Date: Jun 2012
Posts: 800
 
Device(s):
Carrier: Not Provided

Thanks: 39
Thanked 249 Times in 137 Posts
Default

Quote:
Originally Posted by algree View Post
Thanks a Million. I unbox'd a new merit ST. bootup while pluged into pc put your zip on root of sd card and then follow'd your instructions and made A CWM backup I'm uploading it to my GDrive and I will post a link when Its done.

PS: I used 7z to compress it 50%

and again THANKS I also downloaded your stock but rooted CWM rom I have'nt Tried to load it yet I'll let you Know how I made out

great!!! if you have trouble with the stock rooted backup let me know. i'm in the process of uploading the same thing just made with the most recent M 1.03 recovery.img.

i anxiously await your upload--thank you so much for this
stayboogy is offline  
Reply With Quote
Old October 7th, 2012, 12:35 AM   #8 (permalink)
New Member
 
Join Date: May 2012
Posts: 10
 
Device(s): ZTE z990 Avail (AT&T GoPhone)
Carrier: Not Provided

Thanks: 2
Thanked 2 Times in 1 Post
Default

I rooted my avail in june with the tcard downgrade and the dialer codes so when my wife wanted a smartphone I talked her into the Avail as well (thinking the root would be cake). After 10+ failed tcard flashes, I even tried to manually root her Avail but I couldn't get it to keep root after a reboot. I gave up and told her I couldn't root it but she wasn't mad...

Forward to this week and I see this thread pop up and immediately this popped into my head:

can I flash this CWM to her non rooted phone and then use CWM to restore one of my nandroid backups? AND, would that then transfer the root to her phone as well? (without losing it during reboots)?

The main reason I even want to spend any more time on her phone is that the limited app space has already come up a few times.

thanks!
gr1mlock is offline  
Reply With Quote
Old October 7th, 2012, 12:45 AM   #9 (permalink)
Senior Member
Thread Author (OP)
 
stayboogy's Avatar
 
Join Date: Jun 2012
Posts: 800
 
Device(s):
Carrier: Not Provided

Thanks: 39
Thanked 249 Times in 137 Posts
Default

Quote:
Originally Posted by gr1mlock View Post
I rooted my avail in june with the tcard downgrade and the dialer codes so when my wife wanted a smartphone I talked her into the Avail as well (thinking the root would be cake). After 10+ failed tcard flashes, I even tried to manually root her Avail but I couldn't get it to keep root after a reboot. I gave up and told her I couldn't root it but she wasn't mad...

Forward to this week and I see this thread pop up and immediately this popped into my head:

can I flash this CWM to her non rooted phone and then use CWM to restore one of my nandroid backups? AND, would that then transfer the root to her phone as well? (without losing it during reboots)?

The main reason I even want to spend any more time on her phone is that the limited app space has already come up a few times.

thanks!
yes, you can use this to put cwm recovery on your wife's phone and then restore a nandroid from your phone that is rooted onto her's and then she will be rooted too. easy as pie

*backup her contacts and anything else she wants to keep first though as they will be erased*

in order to install cwm on an un-rooted device it first factory resets the device and then immediately installs the update.zip--blame zte for this because there is no way around it using this method; and this is the only way to get cwm on an un-rooted phone

and root won't disappear after reboot (not with this--as long as your device is fully rooted). it totally replaces the whole filesystem on the phone--it's not a temporary thing...

just use the update.zip for your phone [A 1.00]
gr1mlock likes this.
stayboogy is offline  
Reply With Quote
Old October 7th, 2012, 12:49 AM   #10 (permalink)
New Member
 
Join Date: May 2012
Posts: 10
 
Device(s): ZTE z990 Avail (AT&T GoPhone)
Carrier: Not Provided

Thanks: 2
Thanked 2 Times in 1 Post
Default

Nice! Thanks for the quick reply stayboogy

Now to see if I can pry it out of her hands for a bit!
gr1mlock is offline  
Reply With Quote
sponsored links
Old October 7th, 2012, 12:53 AM   #11 (permalink)
Senior Member
Thread Author (OP)
 
stayboogy's Avatar
 
Join Date: Jun 2012
Posts: 800
 
Device(s):
Carrier: Not Provided

Thanks: 39
Thanked 249 Times in 137 Posts
Default

Quote:
Originally Posted by gr1mlock View Post
Nice! Thanks for the quick reply stayboogy

Now to see if I can pry it out of her hands for a bit!
no prob. let me know how it goes.

the avail stock recovery may actually have an option that says "install update.zip" in the menu, which would not do a factory reset by default like it has to be done on the merit. i've never flashed the stock avail to my merit to see it's menu actually.

but, it's always good to backup contacts before doing something like this anyway, cause when you restore you're going to lose everything that's on there now
gr1mlock likes this.
stayboogy is offline  
Reply With Quote
Old October 7th, 2012, 10:10 AM   #12 (permalink)
New Member
 
Join Date: May 2012
Posts: 10
 
Device(s): ZTE z990 Avail (AT&T GoPhone)
Carrier: Not Provided

Thanks: 2
Thanked 2 Times in 1 Post
Default

I installed the upright CWM on my phone. I still had the upside down 5.0.2.0 CWM version and it kinda bugged me too.

Next was her phone but she had gone to bed with an alarm set so I snuck in and grabbed it all ninja like

The stock recovery does have the option to install update.zip from the sd card so I ran it on her's and up popped CWM!

I immediately made a nandroid backup in CWM (stock/unrooted) and then backed up her entire sd card to my computer. I put my 2nd nandroid backup on her sd card (I tweaked in stages and created nandroids along the way).

Here's where it gets weird: I turn the phone off and boot into recovery (menu and vol+) to wipe the phone/data/cache/etc and what pop's back up? The stock android recovery menu. After testing it a few times the CWM recovery says it installs and runs normally, but upon reboot the stock recovery is back

I ran the update.zip file again from the sd card and up popped CWM again. I then used it to restore my nandroid backup from the card and then wiped everything to be sure. After a lengthy boot I could tell the restore worked because the bootanimation and sound were gone.

After it settled down for a few mins I set up her google account. Root checker stated that root access was not available. I'm curious as to why the root didn't make it over?

Anywho, I looked around and noticed that my build number had dropped from b19 to b14 so I tried the dial codes. I was able to get root and disable QID

Everything is fine on the root end so far, su rights are getting granted and root checker says yes. I was able to remove bloat and speed it up so she's happy!

If there's anything I should check or verify please list it because I will definitely be hearing about any problems with it. When I handed it back to her all I told her was "I rooted it, cleared up a ton of app space and sped up sd card reads/writes by almost 20 times". She asked what that would help and I had her open the gallery app and she about flipped

Thanks again
gr1mlock is offline  
Reply With Quote
Old October 7th, 2012, 11:21 AM   #13 (permalink)
Senior Member
Thread Author (OP)
 
stayboogy's Avatar
 
Join Date: Jun 2012
Posts: 800
 
Device(s):
Carrier: Not Provided

Thanks: 39
Thanked 249 Times in 137 Posts
Default

Quote:
Originally Posted by gr1mlock View Post
I installed the upright CWM on my phone. I still had the upside down 5.0.2.0 CWM version and it kinda bugged me too.

Next was her phone but she had gone to bed with an alarm set so I snuck in and grabbed it all ninja like

The stock recovery does have the option to install update.zip from the sd card so I ran it on her's and up popped CWM!

I immediately made a nandroid backup in CWM (stock/unrooted) and then backed up her entire sd card to my computer. I put my 2nd nandroid backup on her sd card (I tweaked in stages and created nandroids along the way).

Here's where it gets weird: I turn the phone off and boot into recovery (menu and vol+) to wipe the phone/data/cache/etc and what pop's back up? The stock android recovery menu. After testing it a few times the CWM recovery says it installs and runs normally, but upon reboot the stock recovery is back

I ran the update.zip file again from the sd card and up popped CWM again. I then used it to restore my nandroid backup from the card and then wiped everything to be sure. After a lengthy boot I could tell the restore worked because the bootanimation and sound were gone.

After it settled down for a few mins I set up her google account. Root checker stated that root access was not available. I'm curious as to why the root didn't make it over?

Anywho, I looked around and noticed that my build number had dropped from b19 to b14 so I tried the dial codes. I was able to get root and disable QID

Everything is fine on the root end so far, su rights are getting granted and root checker says yes. I was able to remove bloat and speed it up so she's happy!

If there's anything I should check or verify please list it because I will definitely be hearing about any problems with it. When I handed it back to her all I told her was "I rooted it, cleared up a ton of app space and sped up sd card reads/writes by almost 20 times". She asked what that would help and I had her open the gallery app and she about flipped

Thanks again

i'm not quite sure how that can happen...

but, even when you have cwm recovery on the phone, it will backup the stock recovery every time. don't ask me how that happens, but it does. all my nandroids have a recovery.img in them that is 6144KB which is the size of the stock recovery.img--and they are made using cwm recovery and even after restore cwm is still on the phone which is only 4654KB.

it could be that cwm runs from the cache when you use the update.zip method on an unrooted phone, and since you are in recovery already it can't flash it right away and instead does it upon next boot--and since you wiped the cache and everything that is why stock recovery come back up. of course this is a stretch and is just my attempt at trying to reason how that is possible in the first place.

either way, i'm glad you got it rooted.

as far as not having root after restoring a nandroid of your rooted phone--that doesn't make any sense. people have used my stock rooted nandroid to root their phones that were unrooted and it stuck on their's...

unless att did something to the phone to prevent rooting in B19, which i'm not sure what they could've done, it should have been just fine.

weird is definitely what this all is. but again, either way you got it done and now it's rooted so, glad for you and glad there's testimony my update.zip works
stayboogy is offline  
Reply With Quote
Old October 7th, 2012, 12:09 PM   #14 (permalink)
Member
 
Join Date: Sep 2012
Posts: 152
 
Device(s): ZTE MERIT Z990G Rooted (net10)
Carrier: Not Provided

Thanks: 19
Thanked 31 Times in 29 Posts
Default

Quote:
Originally Posted by stayboogy View Post
i'm not quite sure how that can happen...

but, even when you have cwm recovery on the phone, it will backup the stock recovery every time. don't ask me how that happens, but it does. all my nandroids have a recovery.img in them that is 6144KB which is the size of the stock recovery.img--and they are made using cwm recovery and even after restore cwm is still on the phone which is only 4654KB.

it could be that cwm runs from the cache when you use the update.zip method on an unrooted phone, and since you are in recovery already it can't flash it right away and instead does it upon next boot--and since you wiped the cache and everything that is why stock recovery come back up. of course this is a stretch and is just my attempt at trying to reason how that is possible in the first place.

either way, i'm glad you got it rooted.

as far as not having root after restoring a nandroid of your rooted phone--that doesn't make any sense. people have used my stock rooted nandroid to root their phones that were unrooted and it stuck on their's...

unless att did something to the phone to prevent rooting in B19, which i'm not sure what they could've done, it should have been just fine.

weird is definitely what this all is. but again, either way you got it done and now it's rooted so, glad for you and glad there's testimony my update.zip works
I am pretty sure the reason for the odd behavior being seen here is explained here.

" There is also another important file you
should know about. In /system/
recovery.img there is a full copy of
everything that is loaded on mtd1. This
file is automatically flashed onto mtd1
every time you shut down. That means
two things: 1. Any changes you make
directly to /dev/mtd/mtd1 get blown
away on reboot and 2. If you want to
change /dev/mtd/mtd1 you're probably
better off just sticking the image in /
system/recovery.img and rebooting.
When creating your own custom
update.zip files (especially when adapting
the stock images), you can get tripped up
if you forget to replace /system/
recovery.img and it ends up overwriting /
dev/mtd/mtd1 unbeknownst to you.
Watch out."

This is an excerpt from an article found here. http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images

It's not a big problem, I'm sure with this information stayboogy will be able to fix this in a snap. If he feels it is even necessary.
valueforvalue is offline  
Last edited by valueforvalue; October 7th, 2012 at 12:13 PM.
Reply With Quote
Old October 7th, 2012, 12:27 PM   #15 (permalink)
Senior Member
Thread Author (OP)
 
stayboogy's Avatar
 
Join Date: Jun 2012
Posts: 800
 
Device(s):
Carrier: Not Provided

Thanks: 39
Thanked 249 Times in 137 Posts
Default

Quote:
Originally Posted by valueforvalue View Post
I am pretty sure the reason for the odd behavior being seen here is explained here.

" There is also another important file you
should know about. In /system/
recovery.img there is a full copy of
everything that is loaded on mtd1. This
file is automatically flashed onto mtd1
every time you shut down. That means
two things: 1. Any changes you make
directly to /dev/mtd/mtd1 get blown
away on reboot and 2. If you want to
change /dev/mtd/mtd1 you're probably
better off just sticking the image in /
system/recovery.img and rebooting.
When creating your own custom
update.zip files (especially when adapting
the stock images), you can get tripped up
if you forget to replace /system/
recovery.img and it ends up overwriting /
dev/mtd/mtd1 unbeknownst to you.
Watch out."

This is an excerpt from an article found here. HOWTO: Unpack, Edit, and Re-Pack Boot Images - Android Wiki

It's not a big problem, I'm sure with this information stayboogy will be able to fix this in a snap. If he feels it is even necessary.
but that information isn't true (all the time anyway). there is no recovery.img file in that location or any other location on our phones. i've looked up and down and left and right because i've read that same thing in other places...

and it doesn't get flashed every boot because i've rebooted my phone dozens upon dozens of times since installing cwm and it's still there.

unless there's a way to make that file invisible to root su access, i don't think that information is correct.

another reason i don't believe that thread is because the way they have given directions for unpacking and repacking .img files is bunk and doesn't work like it's supposed to. believe me, that tutorial is what got me into actually 'building' cwm for our phone because unpacking and repacking didn't work for the upside down image.

so i'm not really sure what happened with your phone unless it's what i mentioned above about being in the cache until it was properly flashed at reboot.

what matters is that it worked in the end LOL
stayboogy is offline  
Reply With Quote
Old October 7th, 2012, 12:47 PM   #16 (permalink)
Member
 
Join Date: Sep 2012
Posts: 152
 
Device(s): ZTE MERIT Z990G Rooted (net10)
Carrier: Not Provided

Thanks: 19
Thanked 31 Times in 29 Posts
Default

Quote:
Originally Posted by stayboogy View Post
but that information isn't true (all the time anyway). there is no recovery.img file in that location or any other location on our phones. i've looked up and down and left and right because i've read that same thing in other places...

and it doesn't get flashed every boot because i've rebooted my phone dozens upon dozens of times since installing cwm and it's still there.

unless there's a way to make that file invisible to root su access, i don't think that information is correct.

another reason i don't believe that thread is because the way they have given directions for unpacking and repacking .img files is bunk and doesn't work like it's supposed to. believe me, that tutorial is what got me into actually 'building' cwm for our phone because unpacking and repacking didn't work for the upside down image.

so i'm not really sure what happened with your phone unless it's what i mentioned above about being in the cache until it was properly flashed at reboot.

what matters is that it worked in the end LOL
I see stayboogy is already on top of it. Hmmm if that is incorrect I am unsure. The method for repack in that thread does work though because I have done it and the images boot perfectly. It's just that the tools for doing so in that thread suck. I was able to find a better set of tools which I thought I posted a link to. And they work flawlessly. But it doesn't matter your method works perfect, and unpacking and repacking from what I have seen serves no purpose unless you want to change the images in the recovery LOL.
valueforvalue is offline  
Reply With Quote
Old October 7th, 2012, 01:03 PM   #17 (permalink)
Senior Member
Thread Author (OP)
 
stayboogy's Avatar
 
Join Date: Jun 2012
Posts: 800
 
Device(s):
Carrier: Not Provided

Thanks: 39
Thanked 249 Times in 137 Posts
Default

Quote:
Originally Posted by valueforvalue View Post
I see stayboogy is already on top of it. Hmmm if that is incorrect I am unsure. The method for repack in that thread does work though because I have done it and the images boot perfectly. It's just that the tools for doing so in that thread suck. I was able to find a better set of tools which I thought I posted a link to. And they work flawlessly. But it doesn't matter your method works perfect, and unpacking and repacking from what I have seen serves no purpose unless you want to change the images in the recovery LOL.

yeah, i'm not sure how you got them unpacked and repacked and they still booted. that wasn't happening here lol

it's for the best though that it didn't work for me; i've gotten more enjoyment out of playing in the sdk
stayboogy is offline  
Reply With Quote
Old October 7th, 2012, 01:30 PM   #18 (permalink)
Member
 
Join Date: Sep 2012
Posts: 152
 
Device(s): ZTE MERIT Z990G Rooted (net10)
Carrier: Not Provided

Thanks: 19
Thanked 31 Times in 29 Posts
Default

Quote:
Originally Posted by stayboogy View Post
yeah, i'm not sure how you got them unpacked and repacked and they still booted. that wasn't happening here lol

it's for the best though that it didn't work for me; i've gotten more enjoyment out of playing in the sdk
Did you try the tools in the link I posted?

Note:after some checking I have found that you are correct there is no recovery.img in system or anywhere that I can find. So I decided to scour the init.rc to see if it flashes any file on start up, didn't find that either. So I guess that simply doesn't apply to our phones. I did find an interesting setting relating to CIQ which after running red pill it said CIQ was not found or disabled on my phone after looking on the init.rc I believe it finally lol.
stayboogy likes this.
valueforvalue is offline  
Reply With Quote
Old October 7th, 2012, 02:02 PM   #19 (permalink)
New Member
 
Join Date: May 2012
Posts: 10
 
Device(s): ZTE z990 Avail (AT&T GoPhone)
Carrier: Not Provided

Thanks: 2
Thanked 2 Times in 1 Post
Default

ok, any idea why the update.zip starts CWM but doesn't overwrite the recovery partition?

for now I'm leaving the update.zip on the sd card since I won't be flashing her phone much (if at all)

thanks
gr1mlock is offline  
Reply With Quote
Old October 7th, 2012, 02:09 PM   #20 (permalink)
Senior Member
Thread Author (OP)
 
stayboogy's Avatar
 
Join Date: Jun 2012
Posts: 800
 
Device(s):
Carrier: Not Provided

Thanks: 39
Thanked 249 Times in 137 Posts
Default

Quote:
Originally Posted by gr1mlock View Post
ok, any idea why the update.zip starts CWM but doesn't overwrite the recovery partition?

for now I'm leaving the update.zip on the sd card since I won't be flashing her phone much (if at all)

thanks

i'm not sure.

if you want it on there permanently, then you will have to flash it like normal.

this was built so people without root could make a backup of their phones with cwm recovery. and if they wanted to restore they could be doing the procedure again and then restore

and, if someone wanted to root their merit, they could just use this to backup their un-rooted system, then immediately restore my rooted system backup.

to be honest i didn't realize that this wasn't permanent--reason being is that every time i tested it i was actually backing up and restoring various nandroids, some with cwm recovery, some without. so thanks for the info. i'll add it above
gr1mlock likes this.
stayboogy is offline  
Last edited by stayboogy; October 7th, 2012 at 02:20 PM.
Reply With Quote
sponsored links
Old October 7th, 2012, 02:24 PM   #21 (permalink)
Senior Member
Thread Author (OP)
 
stayboogy's Avatar
 
Join Date: Jun 2012
Posts: 800
 
Device(s):
Carrier: Not Provided

Thanks: 39
Thanked 249 Times in 137 Posts
Default

unneeded post.

sorry
stayboogy is offline  
Reply With Quote
Old October 7th, 2012, 03:05 PM   #22 (permalink)
Senior Member
 
out of ideas's Avatar
 
Join Date: May 2012
Posts: 642
 
Device(s): ZTE Merit. ICScamwich OC. Galaxy Prevail CTMod 3.68
Carrier: Pigeons

Thanks: 61
Thanked 145 Times in 114 Posts
Default

Quote:
Originally Posted by algree View Post
Thanks a Million. I unbox'd a new merit ST. bootup while pluged into pc put your zip on root of sd card and then follow'd your instructions and made A CWM backup I'm uploading it to my GDrive and I will post a link when Its done.

PS: I used 7z to compress it 50%

and again THANKS I also downloaded your stock but rooted CWM rom I have'nt Tried to load it yet I'll let you Know how I made out

Here is a link to GDrive (Stock ZTE Merit_clockworkmod.7z)
https://docs.google.com/open?id=0B4BoCRM5_3JNQlRMYWd0THhDV0k
Is this link still working for the stock recovery?
out of ideas is offline  
Reply With Quote
Old October 7th, 2012, 03:11 PM   #23 (permalink)
Member
 
Join Date: Sep 2012
Posts: 152
 
Device(s): ZTE MERIT Z990G Rooted (net10)
Carrier: Not Provided

Thanks: 19
Thanked 31 Times in 29 Posts
Default

Stayboogy have a look at this http://pastebin.com/RbQRMYAh

It is your update-script from the update.zip after you look through it I bet you will be able to figure out why the recovery flash is not perminant.
valueforvalue is offline  
Reply With Quote
Old October 7th, 2012, 03:35 PM   #24 (permalink)
Senior Member
Thread Author (OP)
 
stayboogy's Avatar
 
Join Date: Jun 2012
Posts: 800
 
Device(s):
Carrier: Not Provided

Thanks: 39
Thanked 249 Times in 137 Posts
Default

Quote:
Originally Posted by valueforvalue View Post
Stayboogy have a look at this stayboogy update.zip update-script - Pastebin.com

It is your update-script from the update.zip after you look through it I bet you will be able to figure out why the recovery flash is not perminant.
but see the thing is i didn't build the updater-script

cyanogen sdk does this automatically

but i see your point. it doesn't actually flash recovery.img

and you know, when it was built i was curious why it had every other file but the actual recovery.img in it.

maybe i'll see about fixing that, only thing is, i'm not good with building update.zip files.
stayboogy is offline  
Reply With Quote
Old October 7th, 2012, 03:49 PM   #25 (permalink)
Member
 
Join Date: Sep 2012
Posts: 152
 
Device(s): ZTE MERIT Z990G Rooted (net10)
Carrier: Not Provided

Thanks: 19
Thanked 31 Times in 29 Posts
Default

Quote:
Originally Posted by stayboogy View Post
but see the thing is i didn't build the updater-script

cyanogen sdk does this automatically

but i see your point. it doesn't actually flash recovery.img

and you know, when it was built i was curious why it had every other file but the actual recovery.img in it.

maybe i'll see about fixing that, only thing is, i'm not good with building update.zip files.
I didn't figure you wrote the script, it would be a very slow process writing that line by line. I've never tried to make an update.zip so I don't know how difficult it is and I don't have a computer to work on it with. I suppose you can edit the script and rezip the update.zip and just resign the zip file with zip signer app?
valueforvalue is offline  
Reply With Quote
Old October 7th, 2012, 03:54 PM   #26 (permalink)
Senior Member
Thread Author (OP)
 
stayboogy's Avatar
 
Join Date: Jun 2012
Posts: 800
 
Device(s):
Carrier: Not Provided

Thanks: 39
Thanked 249 Times in 137 Posts
Default

nothing has to be "signed" to install

i'll figure it out
stayboogy is offline  
Reply With Quote
Old October 7th, 2012, 04:11 PM   #27 (permalink)
Member
 
Join Date: Sep 2012
Posts: 152
 
Device(s): ZTE MERIT Z990G Rooted (net10)
Carrier: Not Provided

Thanks: 19
Thanked 31 Times in 29 Posts
Default

Oh really I just assumed that the zip file had to be signed like the apk files. Since they are just zips with a different extention.
valueforvalue is offline  
Reply With Quote
Old October 7th, 2012, 04:14 PM   #28 (permalink)
Senior Member
Thread Author (OP)
 
stayboogy's Avatar
 
Join Date: Jun 2012
Posts: 800
 
Device(s):
Carrier: Not Provided

Thanks: 39
Thanked 249 Times in 137 Posts
Default

Quote:
Originally Posted by valueforvalue View Post
Oh really I just assumed that the zip file had to be signed like the apk files. Since they are just zips with a different extention.
not all the time. they will install just fine from cwm without being signed

it might require signing though since it's installing from the stock recovery menu. (i didn't think about that)
stayboogy is offline  
Reply With Quote
Old October 7th, 2012, 07:15 PM   #29 (permalink)
New Member
 
Join Date: Jul 2012
Posts: 7
 
Device(s):
Carrier: Not Provided

Thanks: 6
Thanked 2 Times in 2 Posts
Thumbs up Stock ZTE Merit_clockworkmod

Quote:
Originally Posted by out of ideas View Post
Is this link still working for the stock recovery?

yes it is. It is my GDrive the link will bring you to the CWM
Stock ZTE Merit_clockworkmod.7z download page when you click on download it will bring you to a page that says

Sorry, we are unable to scan this file for viruses.

The file exceeds the maximum size that we scan. Download anyway

thats the google site that scans it you can scan the zip after download
if you want. I promise it is clean
algree is offline  
Reply With Quote
The Following User Says Thank You to algree For This Useful Post:
out of ideas (October 8th, 2012)
Old October 7th, 2012, 08:38 PM   #30 (permalink)
Member
 
Join Date: Sep 2012
Posts: 152
 
Device(s): ZTE MERIT Z990G Rooted (net10)
Carrier: Not Provided

Thanks: 19
Thanked 31 Times in 29 Posts
Default

Quote:
Originally Posted by stayboogy View Post
not all the time. they will install just fine from cwm without being signed

it might require signing though since it's installing from the stock recovery menu. (i didn't think about that)
Your suspicions were correct boogy it appears according to this thread that the update.zip files must be signed for stock recovery
" Default recovery requires a signed zip.
CWM will take anything."

http://forum.xda-developers.com/showthread.php?t=1704040

This page may also come in handy for working on the update-script.

http://forum.xda-developers.com/wiki/Edify_script_language


Also just a quick note the M 1.0 version of update.zip is signed so I assume the sdk signed it up creation, automatically. So it won't be necessary to try and sign it unless you modify it.

Something that I keep wondering about is if there is a way to make this perminant or if it will require a regular flash because, I see no way to use flash_image from an update.zip on an unrooted phone. So the update.zip may just be a way to get the stock backup and then after root flash the actual recovery.img you created. Which works just fine, will just have to add a note at the beginning of this thread telling the user to flash an actual image after they root.

Another thing that I am wondering about is if the file called "recovery", in the update.zip which is in the sbin directory that the update-script refers to is the actual kernel image its size is thing like 700kb would you mind comparing it with an extracted kernel just to satisfy my curiosity because at the moment I have no way to do so myself. Near as I can tell an update.zip is essentially the ramdisk from the recovery.img just molded to a very precise purpose. Of course I could be wrong.

Ps if you have already read this information I'm sorry for posting it lol. I have a bad habit of posting things you already know, because you seem to be two to three steps ahead of me most of the time lol.
valueforvalue is offline  
Last edited by valueforvalue; October 7th, 2012 at 09:29 PM.
Reply With Quote
sponsored links
Old October 7th, 2012, 10:10 PM   #31 (permalink)
Senior Member
Thread Author (OP)
 
stayboogy's Avatar
 
Join Date: Jun 2012
Posts: 800
 
Device(s):
Carrier: Not Provided

Thanks: 39
Thanked 249 Times in 137 Posts
Default

Quote:
Originally Posted by valueforvalue View Post
Your suspicions were correct boogy it appears according to this thread that the update.zip files must be signed for stock recovery
" Default recovery requires a signed zip.
CWM will take anything."

<<<TeamRainless>>> The DEFINITIVE Guide to Making Update.zip Files for The Galaxy SII - xda-developers

This page may also come in handy for working on the update-script.

Edify script language - XDA-Developers


Also just a quick note the M 1.0 version of update.zip is signed so I assume the sdk signed it up creation, automatically. So it won't be necessary to try and sign it unless you modify it.

Something that I keep wondering about is if there is a way to make this perminant or if it will require a regular flash because, I see no way to use flash_image from an update.zip on an unrooted phone. So the update.zip may just be a way to get the stock backup and then after root flash the actual recovery.img you created. Which works just fine, will just have to add a note at the beginning of this thread telling the user to flash an actual image after they root.

Another thing that I am wondering about is if the file called "recovery", in the update.zip which is in the sbin directory that the update-script refers to is the actual kernel image its size is thing like 700kb would you mind comparing it with an extracted kernel just to satisfy my curiosity because at the moment I have no way to do so myself. Near as I can tell an update.zip is essentially the ramdisk from the recovery.img just molded to a very precise purpose. Of course I could be wrong.

Ps if you have already read this information I'm sorry for posting it lol. I have a bad habit of posting things you already know, because you seem to be two to three steps ahead of me most of the time lol.
well, what i've figured out is that it's impossible to flash recovery when you are using recovery--whether it is stock or running the temporary cwm

the phone will not let you format and flash what is already being used. i should have figured this out before, seeing as when it's built in cyanogen repo it's called "recovery fake flash" because it's not permanent.

the file 'recovery' you refer to in /sbin is actually init.rc from the stock recovery that is renamed recovery.rc in order to actually build cwm, and when it's put into the zip by the sdk it becomes just 'recovery'

and the fake flash update.zip contains just the absolute minimum of files that are required to build cwm recovery, and the images (not the whole ramdisk) so that it can just run from memory.

there is not a way to make this permanent from what i can tell...

[only if you want to, and still want to help] if you find a rom [not nandroid] (for any phone or device) that has cwm recovery.img included in it, that is installed as an update.zip from recovery, download it and check the updater-script and find what commands it's using to flash recovery form recovery. i've tried everything and it's not working. so either it's impossible or there's something i'm missing, and i can sign them just fine to run on stock recovery on our phones...
stayboogy is offline  
Reply With Quote
Old October 7th, 2012, 11:05 PM   #32 (permalink)
Senior Member
 
out of ideas's Avatar
 
Join Date: May 2012
Posts: 642
 
Device(s): ZTE Merit. ICScamwich OC. Galaxy Prevail CTMod 3.68
Carrier: Pigeons

Thanks: 61
Thanked 145 Times in 114 Posts
Default

Quote:
Originally Posted by algree View Post
yes it is. It is my GDrive the link will bring you to the CWM
Stock ZTE Merit_clockworkmod.7z download page when you click on download it will bring you to a page that says

Sorry, we are unable to scan this file for viruses.

The file exceeds the maximum size that we scan. Download anyway

thats the google site that scans it you can scan the zip after download
if you want. I promise it is clean
Cool. Yea i downloaded it yesterday fine and it looked fine and had all the files but i got an md5 mismatch. Saw that now the dl is a bunch of numbers.bn and wanted to make sure.

Want to see if this will unroot me. So thanks a lot for posting that.
out of ideas is offline  
Reply With Quote
Old October 7th, 2012, 11:36 PM   #33 (permalink)
Member
 
Join Date: Sep 2012
Posts: 152
 
Device(s): ZTE MERIT Z990G Rooted (net10)
Carrier: Not Provided

Thanks: 19
Thanked 31 Times in 29 Posts
Default

Quote:
Originally Posted by stayboogy View Post
well, what i've figured out is that it's impossible to flash recovery when you are using recovery--whether it is stock or running the temporary cwm

the phone will not let you format and flash what is already being used. i should have figured this out before, seeing as when it's built in cyanogen repo it's called "recovery fake flash" because it's not permanent.

the file 'recovery' you refer to in /sbin is actually init.rc from the stock recovery that is renamed recovery.rc in order to actually build cwm, and when it's put into the zip by the sdk it becomes just 'recovery'

and the fake flash update.zip contains just the absolute minimum of files that are required to build cwm recovery, and the images (not the whole ramdisk) so that it can just run from memory.

there is not a way to make this permanent from what i can tell...

[only if you want to, and still want to help] if you find a rom [not nandroid] (for any phone or device) that has cwm recovery.img included in it, that is installed as an update.zip from recovery, download it and check the updater-script and find what commands it's using to flash recovery form recovery. i've tried everything and it's not working. so either it's impossible or there's something i'm missing, and i can sign them just fine to run on stock recovery on our phones...
I won't promise anything but I will search around tomorrow when I get off work, and see what I come up with. I'll get back to ya ASAP, maybe we can come up with something. I bet that you are correct though I doubt it's possible but it never hurts to try.
valueforvalue is offline  
Reply With Quote
Old October 8th, 2012, 11:13 PM   #34 (permalink)
Member
 
Join Date: Sep 2012
Posts: 152
 
Device(s): ZTE MERIT Z990G Rooted (net10)
Carrier: Not Provided

Thanks: 19
Thanked 31 Times in 29 Posts
Default

From what I have read I don't think it's possible or desirable to make this perminant. It appears that the recovery from the update.zip is a very stripped down version of course and that it runs from /sbin/ on the root of the internal memory. Stayboogy the recovery file you and I talked about in a previous post that you said was the init file, turns out to be busybox. The init file from the image may very well be busybox because busybox is capable of doing its own init. As it was originally designed for boot floppies. The update script symlink all busybox commands to the recovery file we discussed. So short answer is if you want a perminant recovery image it will have to be flashed after root with adb. The update.zip version works well as a means to obtain an unrooted nandroid. All subsequent nandroids after root would be best made with stayboogy's full recovery.img. I don't know if the nandroids are interchangeable, but if they are not and a user decides to unroot with his original image provided all is still well on his system he can always just re flash update.zip temporarily.

On a side note stayboogy while looking through the recovery.fstab file contained in the update.zip I noticed this line.

/sd-ext ext3 /dev/block/mmcblk0p2

Would it be possible to change that line on your full recovery fstab to read:

/sd-ext vfat /dev/block/mmcblk0p2

And then recompile?
If so it may be possible to have a recovery image that will backup my sd-ext partition that is fat32.
The error that I get when I make a nandroid suggests that cwm sees the partition is there but doesn't mount it. I assume it's because it's expecting ext3 instead of fat. So if it's made to look for vfat then I bet it will work. Then again I could be wrong.
valueforvalue is offline  
Last edited by valueforvalue; October 8th, 2012 at 11:40 PM.
Reply With Quote
Old October 8th, 2012, 11:41 PM   #35 (permalink)
Senior Member
Thread Author (OP)
 
stayboogy's Avatar
 
Join Date: Jun 2012
Posts: 800
 
Device(s):
Carrier: Not Provided

Thanks: 39
Thanked 249 Times in 137 Posts
Default

Quote:
Originally Posted by valueforvalue View Post
From what I have read I don't think it's possible or desirable to make this perminant. It appears that the recovery from the update.zip is a very stripped down version of course and that it runs from the cache I believe it is just symlinked to the recovery partition so that booting into recovery simply causes a redirection to the temporary recovery once the cache is cleared it goes bye bye. The kill recovery.sh script contained in the zip basically does that. So short answer is if you want a perminant recovery image it will have to be flashed after root with adb. The update.zip version works well as a means to obtain an unrooted nandroid. All subsequent nandroids after root would be best made with stayboogy's full recovery.img. I don't know if the nandroids are interchangeable, but if they are not and a user decides to unroot with his original image provided all is still well on his system he can always just re flash update.zip temporarily.

On a side note stayboogy while looking through the recovery.fstab file contained in the update.zip I noticed this line.

/sd-ext ext3 /dev/block/mmcblk0p2

Would it be possible to change that line on your full recovery fstab to read:

/sd-ext vfat /dev/block/mmcblk0p2

And then recompile?
If so it may be possible to have a recovery image that will backup my sd-ext partition that is fat32.
The error that I get when I make a nandroid suggests that cwm sees the partition is there but doesn't mount it. I assume it's because it's expecting ext3 instead of fat. So if it's made to look for vfat then I bet it will work. Then again I could be wrong.
nandroids are compatible from one version to another as far as i know. i'm not run into any issues, but this fake flash is identical to the M and A 1.03 versions, which for all general purposes are perfect.

as far as your fat32 issues is concerned, your suggestion will not work

here's the recovery.fstab
Code:
# mount point    fstype        device            [device2]

/boot        mtd        boot
/cache        yaffs2        cache
/data        yaffs2        userdata
/misc        mtd        misc
/recovery    mtd        recovery
/sdcard        vfat        /dev/block/mmcblk0p1    /dev/block/mmcblk0
/system        yaffs2        system
/sd-ext        ext3        /dev/block/mmcblk0p2
as you can see the very first partition of the sdcard is vfat

now, i can try to add a line
"/sdcard vfat /dev/block/mmcblk0p3 /dev/block/mmcblk1 /dev/block/mmcblk1p1"
or
"/sd-ext vfat /dev/block/mmcblk0p3 /dev/block/mmcblk1 /dev/block/mmcblk1p1"
and that may fix your issue, but i'm not sure. that's just a shot in the dark though. it'll be a few days before i can build you one to test though... i'm swamped with term papers at the moment...

but i will do this and you can test and let me know.
stayboogy is offline  
Last edited by stayboogy; October 8th, 2012 at 11:43 PM.
Reply With Quote
Old October 9th, 2012, 12:12 AM   #36 (permalink)
Member
 
Join Date: Sep 2012
Posts: 152
 
Device(s): ZTE MERIT Z990G Rooted (net10)
Carrier: Not Provided

Thanks: 19
Thanked 31 Times in 29 Posts
Default

No hurry on this end, when you get the chance. I see that the first partition is vfat, what I meant was change the last line in the recovery.fstab the one that is partition 2 /sd-ext to vfat as well. As you can see its currently set to ext3.

As the setting is now it seems that it serves no purpose unless the sd-ext is ext3?
valueforvalue is offline  
Last edited by valueforvalue; October 9th, 2012 at 12:15 AM.
Reply With Quote
Old October 9th, 2012, 12:34 AM   #37 (permalink)
Member
 
Join Date: Sep 2012
Posts: 152
 
Device(s): ZTE MERIT Z990G Rooted (net10)
Carrier: Not Provided

Thanks: 19
Thanked 31 Times in 29 Posts
Default

This is what the edit that I propose would look like I only changed the last line.

Code:
# mount point    fstype        device            [device2]

/boot        mtd        boot
/cache        yaffs2        cache
/data        yaffs2        userdata
/misc        mtd        misc
/recovery    mtd        recovery
/sdcard        vfat        /dev/block/mmcblk0p1    /dev/block/mmcblk0
/system        yaffs2        system
/sd-ext        vfat        /dev/block/mmcblk0p2
I don't think that adding a line will work especially since /sd-ext is already defined. And other reported success on backing up sd-ext when the partition was formatted in ext3. As I said the errors shows that I have sd-ext cwm just acts confused because it expects it to be ext3 not vfat. Since I only have two partitions on my sd-card changing it to p03 will most likely not work either. What is already in the file should suffice as long as the last line is vfat rather than ext3.
valueforvalue is offline  
Reply With Quote
Old October 9th, 2012, 12:34 AM   #38 (permalink)
Senior Member
 
out of ideas's Avatar
 
Join Date: May 2012
Posts: 642
 
Device(s): ZTE Merit. ICScamwich OC. Galaxy Prevail CTMod 3.68
Carrier: Pigeons

Thanks: 61
Thanked 145 Times in 114 Posts
Default

Quote:
Originally Posted by algree View Post
yes it is. It is my GDrive the link will bring you to the CWM
Stock ZTE Merit_clockworkmod.7z download page when you click on download it will bring you to a page that says

Sorry, we are unable to scan this file for viruses.

The file exceeds the maximum size that we scan. Download anyway

thats the google site that scans it you can scan the zip after download
if you want. I promise it is clean
Yup i just tried it out and works great. Flased to stock unrooted and back to rooted no problem.
out of ideas is offline  
Reply With Quote
Old October 9th, 2012, 09:10 AM   #39 (permalink)
Senior Member
Thread Author (OP)
 
stayboogy's Avatar
 
Join Date: Jun 2012
Posts: 800
 
Device(s):
Carrier: Not Provided

Thanks: 39
Thanked 249 Times in 137 Posts
Default

Quote:
Originally Posted by valueforvalue View Post
This is what the edit that I propose would look like I only changed the last line.

Code:
# mount point    fstype        device            [device2]

/boot        mtd        boot
/cache        yaffs2        cache
/data        yaffs2        userdata
/misc        mtd        misc
/recovery    mtd        recovery
/sdcard        vfat        /dev/block/mmcblk0p1    /dev/block/mmcblk0
/system        yaffs2        system
/sd-ext        vfat        /dev/block/mmcblk0p2
I don't think that adding a line will work especially since /sd-ext is already defined. And other reported success on backing up sd-ext when the partition was formatted in ext3. As I said the errors shows that I have sd-ext cwm just acts confused because it expects it to be ext3 not vfat. Since I only have two partitions on my sd-card changing it to p03 will most likely not work either. What is already in the file should suffice as long as the last line is vfat rather than ext3.
well, i can't change that one line like that and release it for everyone because it will break ext support for those that need it. but i'll build you a few and you can test them.
stayboogy is offline  
Reply With Quote
Old October 9th, 2012, 07:53 PM   #40 (permalink)
New Member
 
Join Date: Jul 2012
Posts: 7
 
Device(s):
Carrier: Not Provided

Thanks: 6
Thanked 2 Times in 2 Posts
Default

Quote:
Originally Posted by out of ideas View Post
Yup i just tried it out and works great. Flased to stock unrooted and back to rooted no problem.
I can't seem to boot back into recovery mode. It gets to the zte screen and just hangs there. The only way to get it out of that screen and to boot up is to pull the battery
algree is offline  
Reply With Quote
sponsored links
Old October 9th, 2012, 08:05 PM   #41 (permalink)
Member
 
Join Date: Sep 2012
Posts: 152
 
Device(s): ZTE MERIT Z990G Rooted (net10)
Carrier: Not Provided

Thanks: 19
Thanked 31 Times in 29 Posts
Default

Quote:
Originally Posted by algree View Post
I can't seem to boot back into recovery mode. It gets to the zte screen and just hangs there. The only way to get it out of that screen and to boot up is to pull the battery
Have you tried re flashing the recovery image with adb or terminal emulator?
valueforvalue is offline  
Reply With Quote
The Following User Says Thank You to valueforvalue For This Useful Post:
algree (October 10th, 2012)
Old October 9th, 2012, 08:21 PM   #42 (permalink)
Senior Member
Thread Author (OP)
 
stayboogy's Avatar
 
Join Date: Jun 2012
Posts: 800
 
Device(s):
Carrier: Not Provided

Thanks: 39
Thanked 249 Times in 137 Posts
Default

Quote:
Originally Posted by algree View Post
I can't seem to boot back into recovery mode. It gets to the zte screen and just hangs there. The only way to get it out of that screen and to boot up is to pull the battery
is this a response to the recovery.img or the stock rooted nandroid???

either way, neither one have any faults, so it must be something you are doing.

recovery is perfectly operational.

stock rooted nandroid is without flaw.

maybe explain a little more about what you did before you got where you are now...
stayboogy is offline  
Reply With Quote
Old October 9th, 2012, 08:51 PM   #43 (permalink)
New Member
 
Join Date: Jul 2012
Posts: 7
 
Device(s):
Carrier: Not Provided

Thanks: 6
Thanked 2 Times in 2 Posts
Default

Quote:
Originally Posted by valueforvalue View Post
Have you tried re flashing the recovery image with adb or terminal emulator?
I'm a new at this and not sure how to flash using adb. or using the M1.03 thats why I liked your M1.00 it worked like a charm making tha CWM backup and installing your (1980-01-10.09.57.45)CWM recovery

thanks for tring to help valueforvalue I thaught I posted wrong
algree is offline  
Last edited by algree; October 9th, 2012 at 09:12 PM.
Reply With Quote
Old October 9th, 2012, 09:04 PM   #44 (permalink)
New Member
 
Join Date: Jul 2012
Posts: 7
 
Device(s):
Carrier: Not Provided

Thanks: 6
Thanked 2 Times in 2 Posts
Default

Quote:
Originally Posted by stayboogy View Post
is this a response to the recovery.img or the stock rooted nandroid???

either way, neither one have any faults, so it must be something you are doing.

recovery is perfectly operational.

stock rooted nandroid is without flaw.

maybe explain a little more about what you did before you got where you are now...
after I flashed stock rooted nandroid I moved some apps to sd to gain some space on system and I thought I would try to flash back to stock thats when I found out it would not go into recovery mode I made the mistake and removed flash and then found out its not available on play store would that have somthing to do with my problem
algree is offline  
Reply With Quote
Old October 9th, 2012, 09:14 PM   #45 (permalink)
Senior Member
Thread Author (OP)
 
stayboogy's Avatar
 
Join Date: Jun 2012
Posts: 800
 
Device(s):
Carrier: Not Provided

Thanks: 39
Thanked 249 Times in 137 Posts
Default

Quote:
Originally Posted by algree View Post
after I flashed stock rooted nandroid I moved some apps to sd to gain some space on system and I thought I would try to flash back to stock thats when I found out it would not go into recovery mode I made the mistake and removed flash and then found out its not available on play store would that have somthing to do with my problem

i don't know what you mean removed "flash" but i'm sure that has nothing to do with your issue.

this CWM for unrooted phones is called a fake flash and only runs from memory allowing you to do backups and restore, etc. you have to install it the same way from stock recovery every time you want to use it. if you want it permanently you have to use the directions in M 1.03 and that recovery.img file--it is flashed from command prompt on pc or phone terminal.

are you sure you're pushing the right buttons to get into recovery? this fake flash will not tamper with stock recovery at all so it's either you not pushing the right buttons or you messed something up.

turn the phone completely off. the press and hold volume up and menu keys. with them held then turn on the phone. if that won't bring it up you will have flash it using method in M 1.03 thread.

also, get sirius's "quick boot" app which will let you reboot into recovery from the push of a widget and no key pressing or holding.
stayboogy is offline  
Reply With Quote
Old October 9th, 2012, 10:38 PM   #46 (permalink)
Senior Member
 
out of ideas's Avatar
 
Join Date: May 2012
Posts: 642
 
Device(s): ZTE Merit. ICScamwich OC. Galaxy Prevail CTMod 3.68
Carrier: Pigeons

Thanks: 61
Thanked 145 Times in 114 Posts
Default

Quote:
Originally Posted by algree View Post
after I flashed stock rooted nandroid I moved some apps to sd to gain some space on system and I thought I would try to flash back to stock thats when I found out it would not go into recovery mode I made the mistake and removed flash and then found out its not available on play store would that have somthing to do with my problem
Weird. So it boots normally ok? I have the upside down CWM and flased from root to your noroot and back just fine.

Maybe try reinstalling CWM.

Also get quick boot and see if u can get in that way.

And flashing roms and stuff is not like the flash app. That wiuldnt mess with it.
out of ideas is offline  
Reply With Quote
The Following User Says Thank You to out of ideas For This Useful Post:
algree (October 10th, 2012)
Old October 10th, 2012, 05:25 PM   #47 (permalink)
New Member
 
Join Date: Jul 2012
Posts: 7
 
Device(s):
Carrier: Not Provided

Thanks: 6
Thanked 2 Times in 2 Posts
Default

Quote:
Originally Posted by out of ideas View Post
Weird. So it boots normally ok? I have the upside down CWM and flased from root to your noroot and back just fine.

Maybe try reinstalling CWM.

Also get quick boot and see if u can get in that way.

And flashing roms and stuff is not like the flash app. That wiuldnt mess with it.
Adpbe Flash player is what removed and I can't get it back cannot find it in play store on any whare on the net


I got it went to
http://androidforums.com/avail-all-things-root/623377-release-clockworkmod-recovery-right-side-up-avail-merit-roamer.html#post5004729
and used adb to flash the M 1.03 recovery and averything is working now Thanks all of you for the help and tips
out of ideas likes this.
algree is offline  
Last edited by algree; October 10th, 2012 at 06:01 PM.
Reply With Quote
Old November 2nd, 2012, 03:13 PM   #48 (permalink)
Senior Member
Thread Author (OP)
 
stayboogy's Avatar
 
Join Date: Jun 2012
Posts: 800
 
Device(s):
Carrier: Not Provided

Thanks: 39
Thanked 249 Times in 137 Posts
Default

links removed

my work was shared on another forum without my permission
stayboogy is offline  
Reply With Quote
Reply


Go Back   Android Forums > Android Phones > ZTE AT&T Avail (ZTE Merit) > Avail - All Things Root
Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT -5. The time now is 09:43 AM.
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.