Related
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.
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...
Hello,
I kind of messed up with my nexus 4's build.prop file and forgot to back up
Will someone be kind enough and upload their unmodified build.prop file (JWR66Y).
Thanks.
avi619 said:
Hello,
I kind of messed up with my nexus 4's build.prop file and forgot to back up
Will someone be kind enough and upload their unmodified build.prop file (JWR66Y).
Thanks.
Click to expand...
Click to collapse
Go to https://developers.google.com/android/nexus/images and download the 4.3 factory image, then extract the build.prop file
Desno365 said:
Go to https://developers.google.com/android/nexus/images and download the 4.3 factory image, then extract the build.prop file
Click to expand...
Click to collapse
How do I extract the .img file? 7zip does not seem to work.
avi619 said:
How do I extract the .img file? 7zip does not seem to work.
Click to expand...
Click to collapse
I forgot the img file sorry.
I will upload it for you, wait a moment
Desno365 said:
Go to https://developers.google.com/android/nexus/images and download the 4.3 factory image, then extract the build.prop file
Click to expand...
Click to collapse
Desno365 said:
I forgot the img file sorry.
I will upload it for you, wait a moment
Click to expand...
Click to collapse
I found a tool here and extracted the image via linux reader. Replaced the build.prop file and when I restarted my phone it went completely blank.
The google logo also did not show. I think I bricked it
avi619 said:
I found a tool here and extracted the image via linux reader. Replaced the build.prop file and when I restarted my phone it went completely blank.
The google logo also did not show. I think I bricked it
Click to expand...
Click to collapse
Don't worry you didn't brick it, how do you replace the build.prop file?
Desno365 said:
Don't worry you didn't brick it, how do you replace the build.prop file?
Click to expand...
Click to collapse
ES File Manager. My phone is rooted.
avi619 said:
ES File Manager. My phone is rooted.
Click to expand...
Click to collapse
Did you set the correct permissions (rw-r--r--)? Maybe this is the problem.
If your phone doesn't boot, restore a nandroid backup or flash a ROM
Desno365 said:
Did you set the correct permissions (rw-r--r--)? Maybe this is the problem.
If your phone doesn't boot, restore a nandroid backup or flash a ROM
Click to expand...
Click to collapse
No I did not set those permissions. Just replaced the build.prop file. I don't know what nandroid backup is but I have TWRP installed.
PS: The phone is still on the blank screen.
avi619 said:
No I did not set those permissions. Just replaced the build.prop file. I don't know what nandroid backup is but I have TWRP installed.
PS: The phone is still on the blank screen.
Click to expand...
Click to collapse
If you have a ROM in sdcard flash it, if you haven't you have to flash a ROM with adb sideload or a factory image with fastboot (the factory image will erase your data!)
Desno365 said:
If you have a ROM in sdcard flash it, if you haven't you have to flash a ROM with adb sideload or a factory image with fastboot (the factory image will erase your data!)
Click to expand...
Click to collapse
Thanks, I m going to flash 4.4 stock rom from http://forum.xda-developers.com/showthread.php?t=2535728
Alright, quick update:
I used adb sideload to flash the rom from my above post. Worked like a charm, and I have Kitkat running with root. Also, no data was lost.
First thing I am gonna do now is backup my build.prop and data
Thanks for the help.
Cheers.
avi619 said:
Alright, quick update:
I used adb sideload to flash the rom from my above post. Worked like a charm, and I have Kitkat running with root. Also, no data was lost.
First thing I am gonna do now is backup my build.prop and data
Thanks for the help.
Cheers.
Click to expand...
Click to collapse
Great!
I made the same mistake before, when I hide the softkeys
just for reference, you could have fixed it easily, just by using TWRP's File manager:
1. Mount System
2. Replace with the original Build.prop inside the system directory
3. Click the file -> Change file permissions chmod 775
Hi everybody,
First post ! unfortunately it is because I need help...
I recently upgrade my firmware and I was about to reinstall the xdabbed's camera mod but I unfortunately backup the already modified file system.
Therefore, it would be really helpfull if someone could send me their backup of the system folder.
thanks!
izanaghi said:
Hi everybody,
First post ! unfortunately it is because I need help...
I recently upgrade my firmware and I was about to reinstall the xdabbed's camera mod but I unfortunately backup the already modified file system.
Therefore, it would be really helpfull if someone could send me their backup of the system folder.
thanks!
Click to expand...
Click to collapse
Do you have access to custom recovery ?
bender_007 said:
Do you have access to custom recovery ?
Click to expand...
Click to collapse
the phone is rooted but I haven't installed any custom recovery.
I thought i could be possible to grab someone's backup system archive and use the xdabbed apk to restore default applications.
Actually I should describe a bit more the problem, the camera is there, the player is there but the gallery has disappeared.
There is an LGgallery.apk that comes with xdabbed package but i can't install it. When I try a manual install (just launch the apk), it is just telling me that the app couldn't be installed.
hope we can do something from it, otherwise I'll install a custom recovery and follow any advises you might have,
Thanks,
The thing is:
I can provide you with a restore package(also apk) but I wouldn't advise it. (it's unsafe replacing files on a LIVE android system)
If something happens and you don't have a custom recovery then your only solution is to flash a kdz.
So the best thing would be to install recovery.
If you want the apk I'll send it to you, until now it worked 2 of 2 times for restoring. Again..i would advise the recovery.
+you don't install the lggallery.apk, you copy it to /system/priv-app and chmod 644
first delete the lggallery.odex
bender_007 said:
The thing is:
I can provide you with a restore package(also apk) but I wouldn't advise it. (it's unsafe replacing files on a LIVE android system)
If something happens and you don't have a custom recovery then your only solution is to flash a kdz.
So the best thing would be to install recovery.
If you want the apk I'll send it to you, until now it worked 2 of 2 times for restoring. Again..i would advise the recovery.
+you don't install the lggallery.apk, you copy it to /system/priv-app and chmod 644
first delete the lggallery.odex
Click to expand...
Click to collapse
Ok so i replaced the old LGgallery, remove the odex, changed permission and reboot but no luck with that.
installing a custom recovery sounds quite complex and I am ready to take a risk and try your archive. (hope it'll do the trick)
Otherwise I'll resort to install a recovery,
Many thanks
Actually it's 1 click and it's installed. If the apk fails and you bootloop then you can't install recovery(or boot).
Sent from my LG-D802 using Tapatalk
:
If you want to risk:
modified xdabbeb's installer(install the stock files)
If you want the recovery way(installing recovery is one click job) tell me
bender_007 said:
Actually it's 1 click and it's installed. If the apk fails and you bootloop then you can't install recovery(or boot).
Sent from my LG-D802 using Tapatalk
If you want to risk:
modified xdabbeb's installer(install the stock files)[/URL]
If you want the recovery way(installing recovery is one click job) tell me
Click to expand...
Click to collapse
I am usually stubborn but I listen the advise this time, could you advise me on the best way to do it or direct me to an appropriate thread?
Since you are already rooted.
first: download this
It's the flashable zip for the camera(thx to bruce) (put it on sdcard(internal storage))
then
1. AutoRec d802 You say you've got the d802 right ? Then this one.
Install..Run..Press YES. Allow permissions. Press Flash, wait.. When it says it's done then it's done.
Then press "to recovery" see if it reboots. If it does, you should see TWRP..just press install zip, choose the newly dloaded file.
bender_007 said:
Since you are already rooted.
first: download
It's the flashable zip for the camera(thx to bruce) (put it on sdcard(internal storage))
then
1. You say you've got the d802 right ? Then this one.
Install..Run..Press YES. Allow permissions. Press Flash, wait.. When it says it's done then it's done.
Then press "to recovery" see if it reboots. If it does, you should see TWRP..just press install zip, choose the newly dloaded file.
Click to expand...
Click to collapse
Many thx to Bruce and yourself but I did as described installed TWRP (worked), install the zip (worked), reboot (updated 1 app) but still no sign of the damned Gallery????
What am I missing?
let me see first. 1 minute please.
EDIT: ahh I see.. there is no gallery inside..Wait a min.
Additionally flash this (gallery)
bender_007 said:
let me see first. 1 minute please.
EDIT: ahh I see.. there is no gallery inside..Wait a min.
Additionally flash (gallery)
Click to expand...
Click to collapse
Downloaded it, flashed it, loved it!
Thank you very much for your (and Bruce? ) time, patience and expertise .
First post great support
Again many many thanks :highfive:
No problem
where can i delete the faulty file through file manager in twrp? i dont wanna flash a bunch of images or anything can someone PLZ tell me an easier way to get rid of the bootanimation?
can i flash any flashable zip bootanimation? would that replace the current one n fix it?
Did you make a backup of the original bootanimation? If so use Terminal in TWRP to restore it, or try using adb shell command to fix it. That happened to me once on an older phone and that's how I fixed it.
i have a working bootanimation.zip file on my PC, i can flash it via adb?
and no i did not make a backup
Lord. Tech said:
and no i did not make a backup
Click to expand...
Click to collapse
Which ROM are you using?
Lord. Tech said:
i have a working bootanimation.zip file on my PC, i can flash it via adb?
Click to expand...
Click to collapse
You can try adb push bootanimation.zip > /system/media/bootanimation.zip
I'm using benzo and i think my permissions are wrong maybe, is it 644 or 755? I want the marvel theme of changing superheroes but i just can't get it to work why does a bootanimation get stuck? Is it the numbering of the images?
Lord. Tech said:
I'm using benzo and i think my permissions are wrong maybe, is it 644 or 755? I want the marvel theme of changing superheroes but i just can't get it to work why does a bootanimation get stuck? Is it the numbering of the images?
Click to expand...
Click to collapse
You can try fixing the permissions via TWRP recovery.
Another thing that might help, is to dirty flash the ROM again, over the current installation, without wiping anything.
Sent from my Nexus 6P using XDA-Developers mobile app
Next time, please only post your question in one place, double posting isn't allowed.
Can't he just remove the boot animation and not transfer one over? I believe the phone will boot but a stock "Android" letter boot animation will load and then the phone will boot where he can install a new boot animation (or maybe put back the old boot animation)