Related
Hi all,
I am trying to flash my G1 to one of the nice custom roms. I flashed the recovery and spl just fine.
Now I cannot flash anything. I've tried different roms (cyanogen and dude's) and even tried flashing the radio. No love. The error is that it cannot find my sdcard or update.zip.
Phone is pvt and is rooted.
Any thoughts?
Thanks,
Hank
What steps did you take to root? Is your card fat32?
Did you mount the sdcard on windows? If you did, rename the file to update not update.zip on WINDOWS! Also, can you even mount your sdcard? If not, then there's your problem.
I followed the rooting instructions from this site. i do have # in the local terminal.
i can mount the sd card and i did mount in windows to transfer fikes over. i should just name them update not update.zip?
djscamper said:
I followed the rooting instructions from this site. i do have # in the local terminal.
i can mount the sd card and i did mount in windows to transfer fikes over. i should just name them update not update.zip?
Click to expand...
Click to collapse
That will probably help.. By default Windows hides the extension (the .zip part) so when you rename it to "update.zip" you actually make it update.zip.zip
Easy way to check is look at the original file.. if it says something like
Code:
update-cm-3.6.6-signed.zip
you need to rename to
Code:
update.zip
if it says
Code:
update-cm-3.6.6-signed
then just call it
Code:
update
Thanks. Getting a signature error now.
Will try a different version of the file once I am off Caltrain.
Yeah - if you have a modded recovery and get that error, it's most likely a bad download. Good luck.
That did it. It is always something so simple.
Thanks a ton. Hopefully this thread will help someone else as well.
Guys
I've extracted the boot animation from nprussell's VillainROM 5.1 because I think it's much better than the one on VillainROM 5.22, but I can't flash it.
It's a zip file but when I use the system recovery tool to flash it, I'm told there's no signature and verification failed.
How can I get around this?
I've attached the ZIP file.
Okay, managed to sign it using the below link, but I don't have a boot script..! Tut!
http://forum.xda-developers.com/showthread.php?t=656536
sonnysoul said:
Guys
I've extracted the boot animation from nprussell's VillainROM 5.1 because I think it's much better than the one on VillainROM 5.22, but I can't flash it.
It's a zip file but when I use the system recovery tool to flash it, I'm told there's no signature and verification failed.
How can I get around this?
I've attached the ZIP file.
Click to expand...
Click to collapse
Just push it with adb
Code:
adb remount
adb push bootanimation.zip /system/media/
tristan202 said:
Just push it with adb
Code:
adb remount
adb push bootanimation.zip /system/media/
Click to expand...
Click to collapse
Worked a treat, mate.
Cheers!
P.S. Really liking your theme for VillainROM. Keep it up!
I've been trying for sometime now to install a custom rom (CM11 or anything else for that matter) on my Atrix HD. I got as far a unlocking my boot loader so now every time I reboot, I get a scary warning message saying, my phone has been tampered with.
I've made several attempts to install CWM and even though it seems to install, if I try to boot my phone by holding the power and volume down buttons at the same time, it seems to do nothing, or it will just boot normally. I did try to hold down the power and volume up and volume down buttons and that leads to a menu. One of the options was recovery. I selected that, but then a display of android robot with a red triangle.
Can anyone give me some tips on what I'm doing wrong. I'm a programmer, but I have no experience with android, so you can stay technical but not too "android specific" technical.
Thanks,
Mark
Are you installing it via fastboot? Once you flash recovery, do not allow the phone the reboot. Try and boot into recovery.
If you still can boot into cwm, boot the phone, install Root Explorer, and rename recovery.sh to recovery.sh.bak, boot to fastboot, install cwm, and boot into cwm.
audit13 said:
Are you installing it via fastboot? Once you flash recovery, do not allow the phone the reboot. Try and boot into recovery.
If you still can boot into cwm, boot the phone, install Root Explorer, and rename recovery.sh to recovery.sh.bak, boot to fastboot, install cwm, and boot into cwm.
Click to expand...
Click to collapse
These are the commands I used.
adb devices
adb reboot bootloader
fastboot devices
fastboot flash recovery recovery.img
fastboot reboot
Where recovery.img was the CWM one.
Based on another thread, I attempted to rename ~/system/etc/install_recovery.sh, but even though I'm rooted, ES File Explorer not Root File Explore is able to rename that file.
Any help would be appreciated.
Thanks,
Mark
After renaming the file, stock recovery still comse up?
Sorry, there was a typo. I was NOT able to rename the file.
Use root explorer to do it. That's what I did.
audit13 said:
Use root explorer to do it. That's what I did.
Click to expand...
Click to collapse
I had tried that.
I had installed
ES File Explorer
Root File Explorer
Root File Manager Explorer
All seemed to either give an error or just not change the name. Is there a trick? I'm pretty sure my phone is rooted since I am prompted to ask permission to do these things. I think if I can get past this the renaming issue, I may actually be able to install a new rom. Can you help?
Thanks,
Mark
Did you change the permission in root explorer to r/w from r/o?
Can you be more specific about "root explorer" which app is it. I've used a couple of root file explorers and none of them can seem to rename /system/etc/install-recovery.sh.
I tried to use Root File Manager to change the permissions on that file to have write permissions. The problem is that it says it does, but then when I look again, it's unchecked.
I checked the /system/etc folder and it has write permissions for "owner". I tried to create a test folder in it. It said it was granted permission, but in the end, the test folder was not created.
Maybe my phone is not rooted properly?
I'm not sure at which point in the rooting process I got this, but I have an app named "#SuperSU". If I open it and check it's logs, I can now see an error message saying "SuperSU Pro is required for this feature". Did I screw up with rooting? Should I use something else. Any help to remedy this would be greatly appreciated.
Thanks,
Mark
markdemich said:
Can you be more specific about "root explorer" which app is it. I've used a couple of root file explorers and none of them can seem to rename /system/etc/install-recovery.sh.
I tried to use Root File Manager to change the permissions on that file to have write permissions. The problem is that it says it does, but then when I look again, it's unchecked.
I checked the /system/etc folder and it has write permissions for "owner". I tried to create a test folder in it. It said it was granted permission, but in the end, the test folder was not created.
Maybe my phone is not rooted properly?
I'm not sure at which point in the rooting process I got this, but I have an app named "#SuperSU". If I open it and check it's logs, I can now see an error message saying "SuperSU Pro is required for this feature". Did I screw up with rooting? Should I use something else. Any help to remedy this would be greatly appreciated.
Thanks,
Mark
Click to expand...
Click to collapse
I upgraded to SuperSU Pro. It was only $2.50. Now the log says, "Unable to chmod /system/etc/install-recovery.sh: Read-only file system"
This happened when trying to give write permissions to that file. Am I doing something wrong?
if your adb is setup and working try using this command in adb 'adb reboot recovery' and see if the phones boots to little android with its heart open given a excalmation mark there press all three buttons at the same time and recovery should open
mega_man said:
if your adb is setup and working try using this command in adb 'adb reboot recovery' and see if the phones boots to little android with its heart open given a excalmation mark there press all three buttons at the same time and recovery should open
Click to expand...
Click to collapse
I did that and when the screen you described displayed, pressed the power, and center of the volume up and down rocker switch so I can get but up and down. After a few seconds the screen went blank and I let go. The phone then just booted normally without going into recovery.
markdemich said:
I upgraded to SuperSU Pro. It was only $2.50. Now the log says, "Unable to chmod /system/etc/install-recovery.sh: Read-only file system"
This happened when trying to give write permissions to that file. Am I doing something wrong?
Click to expand...
Click to collapse
Root Explorer: https://play.google.com/store/apps/details?id=com.speedsoftware.rootexplorer&hl=en
audit13 said:
Root Explorer: https://play.google.com/store/apps/details?id=com.speedsoftware.rootexplorer&hl=en
Click to expand...
Click to collapse
Thanks. I purchased that app and when I tried to set the permissions of the file it prompted to mount the volume with write permissions. Once it did that, everything else worked.
Thanks again,
Mark
Good Night,
First of all, I hope this will be of use to someone
I own a Z3 Compact which I rooted yesterday. I followed the steps detailed in here, and today I was getting ready to start using XPosed but I am unable to install it, since I am getting a nice :
SD Card: /storage/emulated/0/Android/data/de.robv.android.xposed.installer/files
Copying Xposed-Disabler-Recovery.zip...
Mounting /system writable...
mount: permission denied (are you root?)
Could not mount /system writable
Trying to continue anyway...
cp: can't create '/system/bin/
app_process.orig': Read-only file system
Failed to create a backup of /system/bine/app_process
Click to expand...
Click to collapse
I followed every step, even flashed the part specified at the FAQ that asks me to flash RICDefeat.zip
FAQ
- Some root apps don't work, because /system can't be remounted rw, what's up with that?
Sony has a special in kernel protection that disallow remounting /system read-write, even for root. Flash this in recovery (copy it to the sdcard and reboot in recovery with volume UP pressed, then install it): https://github.com/dosomder/SonyRICD.../RICDefeat.zip
Click to expand...
Click to collapse
So since I could not get through, even after following every step, opted for a different Installation Mode, to see if I could avoid that by flashing stuff instead
Installation Mode
Classical (write to /system directly)
Recovery (flash zip automatically)
Recovery (write zip to SD card, flash manually)
Click to expand...
Click to collapse
I've tried all three methods
- The first one throws that error
- The second reboots the phone without flashing a thing,
- The third one ... well, it says the following
SD card: /storage/emulated/0/Android/data/de.robv.android.xposed.installer/files
Copying Xposed-Disabler-Recovery.zip...
Copying Xposed-Installer-Recovery.zip...
Copying XposedBridge.jar...
Please flash Xposed-Installer-Recovery.zip from the SD card to complete the operation.
Click to expand...
Click to collapse
So then you just have to reboot in recovery, dig to that same folder and find in there the zip to flash.
Anyway, just posting this in case anyone has that same problem, because it has driven me crazy not being able to fix that /system non writable problem with Sony. geez....
Cheers
Thank you so much. It works for my Z3C Docomo (already flashed with US ROM - D5803_23.0.1.A.5.77_US.ftf).
Thanks!
I had another Z3c that broke and the installation was as smoth as possible, but i had unlocked bootloader and rooted by the old method (that needed BU).
I got a new phone from assistence and did the root without UB.. and got the same problem .. thanks for the "tutorial"
Alright so this fixes some issue you had with the actual flashing of xposed in TWRP? I'm assuming it doesn't fix the bootloop problem that happens if you don't wipe the cache between every restart?
I'm not sure I follow your original thread,or what you actually did to resolve whatever issue it is that you were having...
NeLk said:
Installation Mode
Classical (write to /system directly)
Recovery (flash zip automatically)
Recovery (write zip to SD card, flash manually)
I've tried all three methods
- The first one throws that error
- The second reboots the phone without flashing a thing,
- The third one ... well, it says the following
So then you just have to reboot in recovery, dig to that same folder and find in there the zip to flash.
Anyway, just posting this in case anyone has that same problem, because it has driven me crazy not being able to fix that /system non writable problem with Sony. geez....
Click to expand...
Click to collapse
I'm currently being driven crazy by Sony's ridiculous R/W restriction, so I'd like to be able to lift it. If I understand correctly, your thread is partially about that. I'm having trouble flashing RICDefeat from recovery.
I don't understand the difference between flashing a zip automatically and flashing it manually. The only method I know is copying to SD/internal memory, booting into recovery and install/flash zip from there. Which recovery did you use?
Thanks.
The latest XPosed Installer is missing last option, but I found the file downloaded at /sdcard/Android/data/de.robv.../cache/downloads/framework
Here's a couple to start I'll be adding more
Also just post me a link to a gif animation you like and I'll turn it into a flashable boot animation for you
Flash instructions-
1- Download zip to phone and send it to you watch using file manager for wear
2- Boot into TWRP and flash zip
Reboot & Enjoy
Non flashable Instructions - plug you watch into your computer
And in terminal type in "adb push (location of boot animation) /system/media/ " Then boot into TWRP and mount system then go into files then to system/media and click on the boot animation then click chmod and change permissions to 0644 and reboot and enjoy
Downloads
NONFLASHABLE (ADB method)-
Droid in green circle
FLASHABLE ZIPS -
Droid in green circle
Dancing droid
Nexuslike
Stock wear
will this work on my huawei watch it is rooted and i have TWRP installed
Thanks
Robshr said:
Here's a couple to start I'll be adding more
Also just post me a link to a gif animation you like and I'll turn it into a flashable boot animation for you
Flash instructions-
1- Download zip to phone and send it to you watch using file manager for wear
2- Boot into TWRP and flash zip
Reboot & Enjoy
Non flashable Instructions - plug you watch into your computer
And in terminal type in "adb push (location of boot animation) /system/media/ " Then boot into TWRP and mount system then go into files then to system/media and click on the boot animation then click chmod and change permissions to 644 and reboot and enjoy
Downloads
NONFLASHABLE (ADB method)-
Droid in green circle
FLASHABLE ZIPS -
Droid in green circle
Dancing droid
Nexuslike
Stock wear
Click to expand...
Click to collapse
I just flashed the dancing droid boot animation on my LG Urbane with TWRP. But when I reboot the watch I'm still getting the stock boot animation. Help please?? Gracias senor.
Bricking1 said:
I just flashed the dancing droid boot animation on my LG Urbane with TWRP. But when I reboot the watch I'm still getting the stock boot animation. Help please?? Gracias senor.
Click to expand...
Click to collapse
Hmm idk it works fine for me
Robshr said:
Hmm idk it works fine for me
Click to expand...
Click to collapse
Well that's bizarre. Thanks for the reply though. Please let me know if you think of anything I may try to get it working properly. Thank you sir.
Robshr said:
Hmm idk it works fine for me
Click to expand...
Click to collapse
I've tried to flash several other boot animations as well as yours and every time my watch boots with the stock animation? WTF. Maybe I need to manually copy the animation zip into the proper directory? Do you know if the proper directory is /data/local/ ?
Bricking1 said:
I've tried to flash several other boot animations as well as yours and every time my watch boots with the stock animation? WTF. Maybe I need to manually copy the animation zip into the proper directory? Do you know if the proper directory is /data/local/ ?
Click to expand...
Click to collapse
To do it manually just in terminal type in "adb push (location of boot animation) /system/media/ " Then boot into TWRP and mount system then go into files then to system/media and click on the boot animation then click chmod and change permissions to 644 and reboot
Robshr said:
Hmm idk it works fine for me
Click to expand...
Click to collapse
I've tried every different method I found to install your boot animations but nothing works. I still get the stock boot animation. HOWEVER, I did notice something odd. When I put the zip in the /system/media directory I am NOT able to change its permissions in TWRP? It give me a red error message. I'm rooted with TWRP and I have Root Checker to confirm root. Is it not letting me change the permissions because I am unable to mount the system? But in TWRP I check the box to mount the system. Is there a quick way for me to confirm whether or not I am able to mount the system? Any help you may offer is greatly appreciated and compensated....
Bricking1 said:
I've tried every different method I found to install your boot animations but nothing works. I still get the stock boot animation. HOWEVER, I did notice something odd. When I put the zip in the /system/media directory I am NOT able to change its permissions in TWRP? It give me a red error message. I'm rooted with TWRP and I have Root Checker to confirm root. Is it not letting me change the permissions because I am unable to mount the system? But in TWRP I check the box to mount the system. Is there a quick way for me to confirm whether or not I am able to mount the system? Any help you may offer is greatly appreciated and compensated....
Click to expand...
Click to collapse
did you try and just flash it? Because that should work it has on both my urbane and huawei watches
Can you post me a screen shot of the error or what the error says, also try using 0644 instead of just 644.