Database Users

How to remove CWM please?

Hi
I'm going to update my a500 to 3.1
I have unrootedmy device but how to remove CWM completly????
Please help

Why don't just update via CWM:
http://forum.xda-developers.com/showthread.php?t=1154492

1) re root your device
2) go into acer recovery installer and reflash to the backed up recovery (or do the stock recovery for your version)
3) de root.
I had to do this to get my update to work.

Do you know where can I find stock recovery for my version?
I have Acer_A500_1.139.05_COM_GEN1
thank you!
simonsgray said:
1) re root your device
2) go into acer recovery installer and reflash to the backed up recovery (or do the stock recovery for your version)
3) de root.
I had to do this to get my update to work.
Click to expand...
Click to collapse

When i installed ARI, it backed up my current recovery. When i went back into ARI, my old recovery was the first option. Sorry, explanation sucks, i don't have screenshots for you. I know there are threads with most of the software/firmware elements of most of the different versions, maybe do some digging? This would be the best place to start: http://forum.xda-developers.com/showthread.php?t=1126364

Look in system/etc for a filed called install-recovery.sh. if its there change its permission from 444 to 544. Then reboot normally. It'll overwrite cwm with your stock recovery.
Sent from my A500 using Tapatalk

Thanks! I used stock one in ARI, woks good.
simonsgray said:
When i installed ARI, it backed up my current recovery. When i went back into ARI, my old recovery was the first option. Sorry, explanation sucks, i don't have screenshots for you. I know there are threads with most of the software/firmware elements of most of the different versions, maybe do some digging? This would be the best place to start: http://forum.xda-developers.com/showthread.php?t=1126364
Click to expand...
Click to collapse

Euclid's Brother said:
Look in system/etc for a filed called install-recovery.sh. if its there change its permission from 444 to 544. Then reboot normally. It'll overwrite cwm with your stock recovery.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
Hi Euclid, are you able to post a copy of that install-recovery.sh file? I don't seem to have it in my system/bin anymore
...That is assuming the file is not unique to each device??
I'm thinking the reason my OTA update wouldnt install is because i dont have the stock recovery menu.
Thanks!

I really don't get why everyone is spazzing over this... If you've already taken the steps to root and install CWM in the first place, why not just install the stock 3.1 image that's been provided in the dev section? It's 100% stock, no need to wait for Acer to stop twiddling their dangly bits...

Floatingfatman, that is exactly what I did, and it worked perfectly. Good advise!

FloatingFatMan said:
I really don't get why everyone is spazzing over this... If you've already taken the steps to root and install CWM in the first place, why not just install the stock 3.1 image that's been provided in the dev section? It's 100% stock, no need to wait for Acer to stop twiddling their dangly bits...
Click to expand...
Click to collapse
Yeah thats what i ended up doing to update it to 3.1.
Reason i want it back to stock is that i couldnt update via OTA at all (downloads fine but install fails at ~20% with the ! in a red triangle).
I was hoping by restoring it to stock the OTA would work, and so any future updates could also be done via OTA as opposed to finding a workaround each time.
Other than that, it's working just fine for now.

Euclid's Brother said:
Look in system/etc for a filed called install-recovery.sh. if its there change its permission from 444 to 544. Then reboot normally. It'll overwrite cwm with your stock recovery.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
I don't understand 'change permission from 444 to 544'. Root Manager lets me choose between, 'Read, Write or Execute'. Could you please elaborate?
Thanks
Never mind. Problem solved.

[Q] Shot self in foot, edited build.prop now N7 won't boot

I was testing tablet UI mode by editing the /system/build.prop file. The N7 went into Tablet UI mode OK but I didn't like it so I reedited the /system/build.prop file to undo my edits, and now the N7 doesn't boot properly. It goes to a black screen and just sit there.
I can boot into recovery and I can get adb to work. I used the pull command to get a copy of the build.prop file and it seems OK but I'm not 100% sure if I made any other edits by mistake. Of course like a fool I didn't make a backup of the original.
Can anyone make some suggestions on how to fix my N7?
Thanks.

lbloo said:
I was testing tablet UI mode by editing the /system/build.prop file. The N7 went into Tablet UI mode OK but I didn't like it so I reedited the /system/build.prop file to undo my edits, and now the N7 doesn't boot properly. It goes to a black screen and just sit there.
I can boot into recovery and I can get adb to work. I used the pull command to get a copy of the build.prop file and it seems OK but I'm not 100% sure if I made any other edits by mistake. Of course like a fool I didn't make a backup of the original.
Can anyone make some suggestions on how to fix my N7?
Thanks.
Click to expand...
Click to collapse
reflash your ROM. it'll replace your build.prop with a good copy. don't wipe a thing, just reflash.

I'm rooted but on stock. Can I just download a copy of the stock rom and flash that with CWM?

lbloo said:
I'm rooted but on stock. Can I just download a copy of the stock rom and flash that with CWM?
Click to expand...
Click to collapse
rooted stock ROM yea. I've also flashed a pure aosp ROM over stock without any reprocussions.

Before I go ahead and reflash I just want to make sure I'm getting it right. I've downloaded the stock rom, extracted image-nakasi-jro03d.zip. I should push this file to my internal storage, then use CWM to flash? Or should I just find a pure aosp ROM and flash that?
Sorry for all the questions, I just don't want to make things worse.

lbloo said:
Before I go ahead and reflash I just want to make sure I'm getting it right. I've downloaded the stock rom, extracted image-nakasi-jro03d.zip. I should push this file to my internal storage, then use CWM to flash? Or should I just find a pure aosp ROM and flash that?
Sorry for all the questions, I just don't want to make things worse.
Click to expand...
Click to collapse
I don't know what you picked up, but here's a stock/rooted ROM that you can flash in your cwm recovery http://forum.xda-developers.com/showthread.php?t=1776330
Aosp works too, its your choice

if you know how to use adb you can just boot to recovery and push the stock build.prop to your tab

I downloaded a stock copy of the stock build.prop, used the adb push command to push it into /system rebooted and nothing. Still hangs on black screen upon boot.
I then downloaded the stock ROM which simms22 kindly pointed me to, used the adb push command to copy the zip file into /data/media/Firmware, used CWM v6.0.1.0 to "install zip file from sdcard" and I got an error, here is the output:
Installing:/sdcard/Firmware/Nexus7 - JRo03d-Odexed-ROOT_4.1.1_signed.zip
Finding update package...
Opening update package...
Installing update package...
E:Error in /sdcard/Firmware/Nexus7 - JRo03d-Odexed-ROOT_4.1.1_signed.zip
(Status 0)
Installation aborted.
I tried both the Odexed and Deodexed files, both gave same results.
Am I missing a step in the process?

It's working now!
I was afraid I was messing up some of the adb commands so I downloaded the Nexus 7 Toolkit 2.0 (Great tool for someone like me)
- via Toolkit re-transferred the odexed and deodexed ROM files, reflashed, same errors as above
- via Toolkit re-installed CWM Recovery 6.0.1.0, reflashed, same errors as above
- via ADB Shell used CHMOD to modify file rights of the ROM files (stab in the dark), same errors as above
- downloaded stock image from CWM site (JRO03D_grouper.zip), pushed via tool kit, flashed via CWM....WORKED!!!
Everything is as it was before, no need for a full wipe! I'm going to do a backup right now!
Not sure why the other ROMS would not flash, but at this point I'm not going to mess around to try to figure it out.
Many thanks to simms22 and PhxkinMassacre for getting me pointed in the right direction.

prly a bad download.
after pushing the file you need to set the correct mode:
Code:
adb shell chmod 644 /system/build.prop

Me too - also hosed my own build.prop
lbloo said:
- downloaded stock image from CWM site (JRO03D_grouper.zip), pushed via tool kit, flashed via CWM....WORKED!!!
Everything is as it was before, no need for a full wipe! I'm going to do a backup right now!
Click to expand...
Click to collapse
Ok, I did the exact same thing and followed these instructions but haven't had any luck.
First, thanks lbloo and the folks who have responded for all the info here. I have downloaded JRO03D_grouper.zip and I am grateful for the tip to the toolkit.
When I have pushed JRO03D_grouper.zip to the N7, it appears to have worked, but I can't find it on the sdcard. I am pushing from the default location to /sdcard/. I then select "install zip from sdcard" and "choose zip from sdcard" but the only zip there is supersu (from Day 1).
For reference, this is CWM Recovery v 6.0.0.6.
Thanks in advance for any help anyone can offer.
Jack

Looking back I don't recall resetting the file rights after modifying the file and that was likely the root cause of my problems.
You should try the chmod command a couple of posts back.

JackinNC said:
Ok, I did the exact same thing and followed these instructions but haven't had any luck.
First, thanks lbloo and the folks who have responded for all the info here. I have downloaded JRO03D_grouper.zip and I am grateful for the tip to the toolkit.
When I have pushed JRO03D_grouper.zip to the N7, it appears to have worked, but I can't find it on the sdcard. I am pushing from the default location to /sdcard/. I then select "install zip from sdcard" and "choose zip from sdcard" but the only zip there is supersu (from Day 1).
For reference, this is CWM Recovery v 6.0.0.6.
Thanks in advance for any help anyone can offer.
Jack
Click to expand...
Click to collapse
What location did you push it to? /sdcard/?
Sent from my Nexus 7 using xda app-developers app

mvmacd said:
What location did you push it to? /sdcard/?
Click to expand...
Click to collapse
Yes. And, to further test, I created a little zip file called test.zip and pushed it to the tablet. I can see it just fine. It's just the grouper zip that I can't find.
Thanks
Jack

I just noticed a diff in filesize between the JRO03D_grouper.zip file I am using and one shown in a Youtube video entitled "how to put a rom to flash on a semi-bricked nexus 7 with recovery" by Youtube user metroid031993. (I'm too green to post outside links on XDA)
Mine is 261814702 bytes, the one shown in the video is 32650144 bytes.
Perhaps this is my problem, an invalid zip file. What do you think? And, can someone please tell me the correct size of JRO03D_grouper.zip?
Thanks
Jack
[Note to moderator(s): If I am heading off track in this thread, please don't hesitate to move it or to instruct me to create a new thread. I think the issue may have changed, but I have stayed here since this is where the conversation is for my root issue. Thx!]

JackinNC said:
can someone please tell me the correct size of JRO03D_grouper.zip?
Click to expand...
Click to collapse
Not sure what's up with the youtube video you're using, but 261814702 bytes is the correct size.

Visa Declined said:
Not sure what's up with the youtube video you're using, but 261814702 bytes is the correct size.
Click to expand...
Click to collapse
Thanks for the confirmation.
Ok, back to trying to figure out why it doesn't appear in CWM Recovery after I've pushed it...
---------- Post added at 11:19 AM ---------- Previous post was at 10:51 AM ----------
JackinNC said:
Ok, back to trying to figure out why it doesn't appear in CWM Recovery after I've pushed it...
Click to expand...
Click to collapse
Well, I got the grouper zip into /sdcard/ and was able to upgrade without losing anything. w00t!
Theory:
I was in the same adb "session" this time since I was using adb from the command line. Meaning, the daemon was still running from the first push I did. So, while I couldn't see the grouper zip after the first push (consistent with your experience, dark_samus), I could see it and upgrade with it after second push (also consistent). And, perhaps my previous attempts didn't work before because I was closing and opening the Nexus 7 Toolkit each time, therefore stopping and restarting the daemon, which meant that each push attempt was the first attempt for that "session."
I don't have any solid technical basis to support or refute that theory, it's just one possible theory that, if true, would result in the experience I had.
My problem is resolved. Thanks to everyone who contributed to this, I truly appreciate your help!
Jack

simms22 said:
reflash your ROM. it'll replace your build.prop with a good copy. don't wipe a thing, just reflash.
Click to expand...
Click to collapse
how to put the stock image if my n7 doesnt boot to android? pls help
i have CWM already

Either replace the complete system partition using 'fastboot flash',
or, probably less intrusive, boot into recovery mount system partition writeable and push build.prop manually using 'adb push'.
Sent from my Nexus 7 using xda app-developers app

AndDiSa said:
Either replace the complete system partition using 'fastboot flash',
or, probably less intrusive, boot into recovery mount system partition writeable and push build.prop manually using 'adb push'.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
my bad i already flash a fresh stock rom again, but thanks anyways...

[Q] 4.4.2 to 4.4.3 update failure in rooted N7

Received the OTA update on my rooted/TWRP'd N7. Clicking on download and install takes me to TWRP Recovery. I cannot find the update file anywhere. If I reboot, the file is right there in my download folder. If I move it to the folder that contains files visible in TWRP recovery flash folder, it still doesn't appear.
I have read threads about updating without unrooting but remain confused.
Is there a way to accomplish this, and if so, do any of you have links that would take me to "how-to" instructions?

gmermel said:
Received the OTA update on my rooted/TWRP'd N7. Clicking on download and install takes me to TWRP Recovery. I cannot find the update file anywhere. If I reboot, the file is right there in my download folder. If I move it to the folder that contains files visible in TWRP recovery flash folder, it still doesn't appear.
I have read threads about updating without unrooting but remain confused.
Is there a way to accomplish this, and if so, do any of you have links that would take me to "how-to" instructions?
Click to expand...
Click to collapse
is this stock rom? TWRP isnt seeing the file ext..
if you were to .zip it. , it would

dareino said:
is this stock rom? TWRP isnt seeing the file ext..
if you were to .zip it. , it would
Click to expand...
Click to collapse
Currently on Smooth ROM.
I'll try to compress and see what happens. Thanks.

dareino said:
is this stock rom? TWRP isnt seeing the file ext..
if you were to .zip it. , it would
Click to expand...
Click to collapse
I zipped the file and yes, TWRP accessed it. Flashing resulted in failure, however.
To add insult, my tablet alerts me to the availability of the update every 2nd/3rd day, prompting me to download it again. If I do that, I'm taken to the "install" page. Attempting to install takes me back to TWRP, where the flash fails. Round and round I go......

XT1052 India 4.4.4 OTA

I've captured the OTA zip for XT1052 India 4.4.4 update.
Instructions (You should be on android 4.4.2)
For both locked and unlocked bootloaders
1. Place the downloaded file in sdcard
2. Don't rename the file, it should be exactly as it is
3. Rooted users make sure you're as close to stock as possible
4. Go to settings-> about-> system updates
5. It will prompt to install the update
Download XT1052 India 4.4.4 OTA

Could you post the stock recovery image of the 4.4.2 ROM, please?

ron_gangte said:
Could you post the stock recovery image of the 4.4.2 ROM, please?
Click to expand...
Click to collapse
Sorry, I don't have that right now.

Thanks anyway. It'd be awesome if someone who has it posted. Anyone?

Yep, the update just popped up. How do you capture it by the way? What's the path?

devilsdouble said:
Yep, the update just popped up. How do you capture it by the way? What's the path?
Click to expand...
Click to collapse
/cache - find it w/Root Explorer, or similar.

samwathegreat said:
/cache - find it w/Root Explorer, or similar.
Click to expand...
Click to collapse
There are three folders under cache, backup, lost+found and recovery, none of them contain the update.

devilsdouble said:
There are three folders under cache, backup, lost+found and recovery, none of them contain the update.
Click to expand...
Click to collapse
You already installed it? Once you install it, the file is erased - forever. All OTAs are this way. You MUST extract it before you install it.
Confirm: Did you install it or not? Also, if not - has it downloaded completely?
EDIT: I'll take your lack of response as you confirming that you did install it...

I am downloading ota update my phone is rooted so should i unroot it first and remove xposed framework.. reply??

Hitesh1802 said:
I am downloading ota update my phone is rooted so should i unroot it first and remove xposed framework.. reply??
Click to expand...
Click to collapse
Yes, un-root, and remove all traces of having rooted. That includes any changes done to your System Files which Xposed might have done. You will have to flash the stock recovery too.

ron_gangte said:
Yes, un-root, and remove all traces of having rooted. That includes any changes done to your System Files which Xposed might have done. You will have to flash the stock recovery too.
Click to expand...
Click to collapse
thanks for the reply mate i have removed su by app option full unroot yes i am on stock recovery and uninstalled all modules and xposed framework..
after update i have to done that again..
Due to this i miss my old Samsung device just flash and you are on...

samwathegreat said:
You already installed it? Once you install it, the file is erased - forever. All OTAs are this way. You MUST extract it before you install it.
Confirm: Did you install it or not? Also, if not - has it downloaded completely?
EDIT: I'll take your lack of response as you confirming that you did install it...
Click to expand...
Click to collapse
No, my lack of response was because of the reading I was doing here on XDA as why I wasn't seeing the OTA zip file under cache. Then I realized that I did not download the OTA, I thought that it was downloaded already as I had data on and it was just asking me to whether it should install or not.
Now I downloaded the OTA, and it's there under cache folder, and now at a safe place on my desktop.
I would never install it on my phone without flashing back stock ROM again anyway. I like to do things fresh.

devilsdouble said:
No, my lack of response was because of the reading I was doing here on XDA as why I wasn't seeing the OTA zip file under cache. Then I realized that I did not download the OTA, I thought that it was downloaded already as I had data on and it was just asking me to whether it should install or not.
Now I downloaded the OTA, and it's there under cache folder, and now at a safe place on my desktop.
I would never install it on my phone without flashing back stock ROM again anyway. I like to do things fresh.
Click to expand...
Click to collapse
Good Deal. Thanks for clarifying, and glad you were able to extract it. :good:
I can relate -- I also prefer to always "do things fresh"

samwathegreat said:
Good Deal. Thanks for clarifying, and glad you were able to extract it. :good:
I can relate -- I also prefer to always "do things fresh"
Click to expand...
Click to collapse
Thanks. It's always nice to have the latest of Android. The new dialer is meaningless for me, again, it just changed it's viewing type, nothing else has been changed! Need to install ExDialer as usual. Will see if there's really something done with the camera, can't take any meaningful photos at 3:30 in the morning :laugh:
Just one thing, as I have taken the OTA after a fresh install of stock ROM, now I don't need to format it again from recovery right?

There is already a thread for the 4.4.4 rollout here, please use it instead of having two similar discussions going on in 2 separate threads. Thanks
Thread closed

Can we get a Step by Step to update to 27?

So my scenario.
I'm on the unlocked B20_boot Build. Rooted. TWRP.
What files are needed to upgrade to B27?
What are the step by step?
I have read through the different threads, but it is confusing at times and rather not make a mistake. It would probably benefit multiple people.
Cheers!

I'm in the same boat. I downgraded to B20 and cannot get the .up file provided recognized in recovery to flash. Using the system updater just puts me right back on B20_Boot. Just using the twrp backup does not flash the B27 firmware.

bhazard451 said:
I'm in the same boat. I downgraded to B20 and cannot get the .up file provided recognized in recovery to flash. Using the system updater just puts me right back on B20_Boot. Just using the twrp backup does not flash the B27 firmware.
Click to expand...
Click to collapse
Change the .up to .zip and try again. This is the safest method to B27.

jkuczera said:
Change the .up to .zip and try again. This is the safest method to B27.
Click to expand...
Click to collapse
Changing it to .zip does not work.

B4oE said:
Changing it to .zip does not work.
Click to expand...
Click to collapse
From stock recovery?

jkuczera said:
From stock recovery?
Click to expand...
Click to collapse
Correct. I was on stock B20 and downloaded the .up file from the following link: https://dl1.ztems.com/zxmdmp/download.do?doWhat=getUp&filename=firmwarepackages/US/ZTE/ZTE%20A2017U/81526/update_P996A01_B20_to_B27.up. After I downloaded it, I simply changed the .up extension to .zip to try to install through stock recovery. However, it was not even recognized. I even moved it to my SD Card but got the same results.

B4oE said:
Correct. I was on stock B20 and downloaded the .up file from the following link: https://dl1.ztems.com/zxmdmp/downlo...TE A2017U/81526/update_P996A01_B20_to_B27.up. After I downloaded it, I simply changed the .up extension to .zip to try to install through stock recovery. However, it was not even recognized. I even moved it to my SD Card but got the same results.
Click to expand...
Click to collapse
Maybe verify checksum? That's the method I used (from SD card).

Interesting. ADB Sideload should work if the Apply Update from SD Card method doesn't.

B4oE said:
Correct. I was on stock B20 and downloaded the .up file from the following link: https://dl1.ztems.com/zxmdmp/download.do?doWhat=getUp&filename=firmwarepackages/US/ZTE/ZTE%20A2017U/81526/update_P996A01_B20_to_B27.up. After I downloaded it, I simply changed the .up extension to .zip to try to install through stock recovery. However, it was not even recognized. I even moved it to my SD Card but got the same results.
Click to expand...
Click to collapse
Enable OEM unlocking under dev. Option and go back to stock recovery > Apply using SDCard.

DrakenFX said:
Enable OEM unlocking under dev. Option and go back to stock recovery > Apply using SDCard.
Click to expand...
Click to collapse
I did that already too. But it still didn't work. Don't worry about it, though. I appreaciate the help, however, I am just going to wait for CyanogenMod to be released. I only wanted to test out the new update. It's not worth the frustration, though. I honestly prefer CyanogenMod.

B4oE said:
I did that already too. But it still didn't work. Don't worry about it, though. I appreaciate the help, however, I am just going to wait for CyanogenMod to be released. I only wanted to test out the new update. It's not worth the frustration, though. I honestly prefer CyanogenMod.
Click to expand...
Click to collapse
Don't expect it anytime soon within the next 3 months.
The updates to the firmware and software are substantial enough that I need to find a 100% working method that I can confirm that takes me from B20_boot, downgraded to B20, then updated to B27 from stock recovery.

bhazard451 said:
Don't expect it anytime soon within the next 3 months.
The updates to the firmware and software are substantial enough that I need to find a 100% working method that I can confirm that takes me from B20_boot, downgraded to B20, then updated to B27 from stock recovery.
Click to expand...
Click to collapse
I am with you. @DrakenFX Do you have the steps mentioned above? What is the best way to get back to B20 so it can be updated to B27?

swehes said:
I am with you. @DrakenFX Do you have the steps mentioned above? What is the best way to get back to B20 so it can be updated to B27?
Click to expand...
Click to collapse
The best way would be a System Image from ZTE, but we are SOL on that for now.