Related
hi all,
I'm from singapore and recently have bought a htc hero. I wanted to load modaco's rom but failed. this is what i have experienced.i tried the guide on adb commands but it gave me the error "remote: failed". subsequently i try the flashrec guide but the flashrec gave me invalid error.
Can someone help?
There are my phone details:
Firmware:1.5
build number: 2.73.707.9.146733 CL#62020 release-keys
software version: 1.0.0.A6288
tianci86 said:
hi all,
I'm from singapore and recently have bought a htc hero. I wanted to load modaco's rom but failed. this is what i have experienced.i tried the guide on adb commands but it gave me the error "remote: failed". subsequently i try the flashrec guide but the flashrec gave me invalid error.
Can someone help?
There are my phone details:
Firmware:1.5
build number: 2.73.707.9.146733 CL#62020 release-keys
software version: 1.0.0.A6288
Click to expand...
Click to collapse
one assumes that you have already rooted your HTC Hero ?
If not then follow this
http://theunlockr.com/2009/08/27/how-to-root-your-htc-hero-in-one-click/
once that is done then follow this
http://theunlockr.com/2009/08/27/how-to-load-a-custom-rom-on-your-htc-hero/
This worked like a charm for me so I assume that it should work for you as well
Hope this helps
Devchef1
Devchef1 said:
one assumes that you have already rooted your HTC Hero ?
If not then follow this
http://theunlockr.com/2009/08/27/how-to-root-your-htc-hero-in-one-click/
once that is done then follow this
http://theunlockr.com/2009/08/27/how-to-load-a-custom-rom-on-your-htc-hero/
This worked like a charm for me so I assume that it should work for you as well
Hope this helps
Devchef1
Click to expand...
Click to collapse
hi, i havent root my hero. i followed the guide and could not load Amon Ra’s Hero Recovery Image into my phone. there's error
Since you are in Asia you likely have the 2.73.707.9 ROM you can check this under Settings/About Phone. Please see this thread:
http://forum.xda-developers.com/showthread.php?t=563256
there is no way to gain root and flash ROMs onto this release at this time
duplicate post
Whats a G3?
here everyone calls the Hero the G3
csasek said:
duplicate post
Click to expand...
Click to collapse
u also stuck with this version too?
csasek said:
here everyone calls the Hero the G3
Click to expand...
Click to collapse
Where, China? I've heard it called the G2 by virtue of T-Mobile branding it the G2 Touch, but never the G3!
Regards,
Dave
I have this model also, just wondering when we are able to root the hero and install different roms will it enable different android market? I'm in the US and am lacking apps that should be present e.g Pandora, ebuddy etc.
I was wondering if this way of force updating would work?
download the official rom version 1.76.405.x firmware (not rooted),
boot up the unit using home+power (to boot into recovery);
extract the official rom's rom.zip and rename into update.zip
put that update.zip into sdcard's root
on the device, apply the update in the recovery.
?
kazuni said:
I was wondering if this way of force updating would work?
download the official rom version 1.76.405.x firmware (not rooted),
boot up the unit using home+power (to boot into recovery);
extract the official rom's rom.zip and rename into update.zip
put that update.zip into sdcard's root
on the device, apply the update in the recovery.
?
Click to expand...
Click to collapse
try it, but i doubt it will work because it will check the CID in the rom.zip(or renamed to update.zip) file and that ROM does not contain CID's needed for most phones.
see here
http://forum.xda-developers.com/showthread.php?t=569730
Log:
Code:
-- Install from sdcard...
Finding update package...
Opening update package...
E:Can't open /sdcard/update.zip
(bad)
Installation aborted.
I guess that's their meaning of non-CID'd rom reply?
kazuni said:
Log:
Code:
-- Install from sdcard...
Finding update package...
Opening update package...
E:Can't open /sdcard/update.zip
(bad)
Installation aborted.
I guess that's their meaning of non-CID'd rom reply?
Click to expand...
Click to collapse
uhm, could be, or it doesn't like the rom.zip (altough renamed to update.zip) zip file, which makes sence as we can create update.zip files and sign them ourselfs (stuff that for example paul (modaco) does) i need more playing time myself, but you can try and creating a new zip with the contents of the rom.zip and sign it, then look if that works....but i'm doubtful
funny thing is, i've downloaded the signed rom from modaco, (they are signed, as far as i can be told by the file name), and tried to flash it again using the same method:
log:
Code:
-- Install from sdcard...
Finding update package...
Opening update package...
Veryfiying update package...
E:No signature (740 files)
E:Verification failed
Installation aborted.
still no go.
does renaming a file affect the signature?
kazuni said:
funny thing is, i've downloaded the signed rom from modaco, (they are signed, as far as i can be told by the file name), and tried to flash it again using the same method:
log:
Code:
-- Install from sdcard...
Finding update package...
Opening update package...
Veryfiying update package...
E:No signature (740 files)
E:Verification failed
Installation aborted.
still no go.
does renaming a file affect the signature?
Click to expand...
Click to collapse
no, but the type of signing is the problem, the update.zip (with cert/sign files inside the zip) is a different kind then doing an edit on the physical zip file and changing (signing) and thats whats being checked and we currently can't duplicate (or re-sign a changed rom.zip)
I found a solution after being told it was not possible.
The Brown Hero I purchased was also an Asian version and had no Market.
I was so scared and frustrated at first because everyone said there was no solution.
But I found one!
*1. Download Linda file manager from here and install since you don't have the market! (I had a copy already on my sdcard) goto Settings, Applications, and make sure Unknown source is checked ON.
*2. On your phone, goto Settings, SD card and phone storage, and click Unmount SD card.
*3. Then click Format SD card (it should automatically remount after this)
*4. Plug the phone into the compuer via USB, then pull down the notification bar and click on the SD card notification. Then click mount.
*5 Download the Flashrec apk from this link: http://zenthought.org/system/files/asset/2/flashrec-1.1.2-20090909.apk and install using Linda File manager.
*6. Download Amon_RA_Herov1.2.2 Recovery image and place on root of sdcard
*7. Open the FlashRec program and click on Backup Recovery Image and wait for it to finish.
*8. Once done, click on the empty text box in the FlashRec program and type
/sdcard/Recovery-RA-HERO-v1.2.2.img
Then click on the Flash Custom RecoveryImage button and wait for it to finish.
*9. Turn off the phone and turn it on into Recovery mode by holding down Home and Power to turn it on (keep holding until the recovery screen comes up has a bunch of text on a black background). So long as that screen comes up, you have done it correctly and now you can load this rom which is HTC Generic 2.73.405.5
It's also referred to as Modaco version 2.2, it's what I'm currently using.
*10. Place that rom on the root of you're sdcard and use option Apply sdcard: choose zip option and flash! Once done reboot and you're all set and will have The Android Market and all the goodness that rooting provides!
Hope this helps!
You had the same ROM version as mentioned in the original post? ^^
plbe said:
You had the same ROM version as mentioned in the original post? ^^
Click to expand...
Click to collapse
My version was a little different but it was an Asian version and did not come with the Android Market installed and had SlideMe market instead.
Here is a screen shot:
i have tried the method u suggested but to no avail. ya, your version of hero is slightly different from mine.
Hey guys I really need your help, I have an HTC Evo 4g and i was rooting my phone using S-Off and i did all the steps needed to root it until i came to the part where i had to download SU and extract into my sd card. The only way for my sd card to show up on my computer was to change my phone setting to mount as disk drive, that was the only way i could of placed the zip file into my sd card. After i was done i put it into charge only mode then i did the hboot and launched CWM. I tried to install SU as a zip file like followed but i came across an error that said installation aborted cant open file (bad file) can someone help me?
[Also i did the fix permissions thing and it didnt work]
then I get this error:
Selecting SU Superuser-3.0.7-efgh-signed.zip...
Finding update package...
Opening update package...
E:can't open /sdcard/Superuser-3.0.7-efgh-signed.zip
(bad)
Installation aborted.
just d/l it from the market
[size=+1]BEFORE YOU BEGIN[/size]
NEW UPDATE: [UPDATE][JB]Stock Android 4.1.2 JZO54K, Root, via CWM Recovery (US Wi-Fi MZ604)
CUSTOM ROM AVAILABILITY: This is a stock rooted update (stock ROM, stock kernel), NOT a full-featured custom ROM. If you want the latest custom features implemented by developers, install the ROM appropriate for your model (Team EOS Xoom 4G MZ602 JB ROM, Team EOS Xoom Wi-Fi MZ604 JB ROM, others in the forums); otherwise, if you want stock 4.1.1 JRO03H ROM and kernel with root, continue below.
COMPATIBILITY: This update is for the US Xoom Wi-Fi MZ604 ONLY!!! If you have a Xoom 3G/4G, this procedure may break your device. If you have a non-US Xoom Wi-Fi, this procedure may break your device (though some have reported success). The update script verifies only whether the device identifies itself as a Xoom, performing NO CHECKS on the exact model of Xoom before flashing rooted stock 4.1.1 JRO03H system and boot images. This means it won't stop you from flashing on a non-US or 3G/4G device; it will just flash and you're left with the mess (if any). Please proceed only if you're tech-savvy with Android and the Xoom, backed up and ready to restore in case of issues, and good at troubleshooting. Please provide feedback and corrections, and I'll update the post as quickly as I can. Thanks!
WARNING: Following this procedure may damage or permamently destroy your device. This procedure is provided with NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Perform this procedure at your own risk.
[size=+1]SUMMARY[/size]
This is a modded update package (update.zip) that updates the US Xoom Wi-Fi from any ROM to stock rooted Android 4.1.1 JRO03H using ClockworkMod Recovery:
Flashes bootloader from a previous update (3.2.1 HTK55D) to ensure integrity (bootloader remains unlocked)
Flashes the boot partition with rooted stock 4.1.1 boot image, stock kernel
Stock kernel includes no extras (overclocking, etc.) from custom kernels
Flashes system partition with rooted stock 4.1.1 image (minus the recovery overwrite script; includes gapps)
Includes Superuser.apk 3.1.3 and su binary to enable functioning root (thanks, chainsdd)
Hardware SDCard continues to be read-only via documented application permissions (now at /storage/sdcard1)
Leaves existing recovery partition intact (unmodded stock 4.1.1 update overwrites it on every reboot)
Leaves user data intact (note: some users updating from custom ROM's recommend wiping data/factory reset to prevent issues)
[size=+1]PREPARATION[/size]
Download the modded Xoom Wi-Fi Android 4.1.1 JRO03H update package
update_US-Xoom-WiFi-4.1.1-JRO03H_stachre_v01.zip
MD5: 4e502cde6902343675b57d47e3b4f722
Ensure you have flashed ClockworkMod Recovery (thanks, solarnz, bigrushdog, koush, et al)
[Recovery] ClockworkMod 3.2.0.0 (R4c) Modded for Internal media [UPDATED 10/6]
Note: there are more current recovery options available which are likely compatible; however, these instructions haven't yet been updated accordingly.
Ensure a physical SDCard with enough free space is installed in your Xoom (required for ClockworkMod Recovery updates; update package requires about 150MB; run adb shell df to get a rough idea of optional nandroid backup size) and have it functioning properly
[size=+1]PROCEDURE[/size]
Backup your data
If you have issues with this update, you may need to "wipe data/factory reset" before the system will fully boot properly. For some, simply copying the contents of the Xoom's internal storage (mostly music, pictures, videos, etc.) to their PC is enough. Others require backup of their apps, app data, etc. using more robust solutions like Titanium Backup. Backup your data according to your needs.
.
Copy/download the modded Android 4.1.1 Update package to the SDCard
.
Reboot into recovery
Reboot your Xoom
When the Motorola logo splash screen appears, press the Volume Down button to scroll through boot options and select "--> Android Recovery"
Press the Volume Up button to enter Android recovery
Wipe cache and dalvik-cache
Note that in recovery, you use the hardware volume buttons to navigate up and down, and the power button to select. Note also that if you are coming over from a custom ROM, users suggest backing up data and doing a "wipe data/factory reset" in ClockworkMod Recovery instead.
Select "wipe cache partition"
Select "Yes - Wipe Cache"
Select "advanced"
Select "Wipe Dalvik Cache"
Select "Yes - Wipe Dalvik Cache"
Select "+++++Go Back+++++"
Optional: Perform nandroid backup (long)
If you have issues with this update, you may need to "wipe data/factory reset" before the system will fully boot properly. Performing a nandroid backup in ClockworkMod Recovery allows you to fully restore your device's state if you need to revert for whatever reason. Note that backing up even a bare system runs a few minutes, so this could take a very long time and require the availability of a power charger. You also need sufficient free space on your SDCard to perform the backup; the backup process does not verify required space before starting, simply failing (and wasting your time) if it runs out.
Select "backup and restore"
Select "Backup"
Be patient
"Backup complete!" will indicate that the update is completed.
Perform update
Select "install zip from sdcard"
Select "choose zip from sdcard"
Select the modded Android 4.1.1 update package
Select "Yes - Install <filename>"
"Install from sdcard complete." will indicate that the update is completed.
.
Select "+++++Go Back+++++"
Select "reboot system now"
New bootloader will install. The message, "Congratulation! Your bootloader was successfully upgraded" will be immediately followed by an automatic reboot.
Enjoy your rooted Xoom Wi-Fi, running on Android 4.1.1 JRO03H!
[size=+1]POST-UPDATE NOTES[/size]
Stuck on Motorola logo/Bootloops: Users report "Wipe data/factory reset" in ClockworkMod Recovery often resolves this issue.
[size=+1]CHANGELOG[/size]
v01: First release, JRO03H; includes root, Superuser.apk, su
[size=+1]UPDATE PACKAGE DETAILS (v01)[/size]
BOOTLOADER: flashed with stock 4.1.1 JRO03H bootloader
Extracted from a previous update package (3.2.1 HTK55D)
Bootloader flashed after reboot
Code:
BCT[4->4] (vendor: 0x101 product: 0x5454 vers: 0x0)
RECOVERY: not flashed; left intact
BOOT: flashed with modded stock 4.1.1 JRO03H boot image with stock kernel
Kernel: flashed with stock 4.1.1 JRO03H kernel
2.6.39.4-gfd343aa [email protected] ) #1 SMP PREEMPT Thu Jun 7 21:07:05 PDT 2012
Includes no extras (overclocking, etc.) from custom kernels
default.prop: modded JRO03H default.prop (ramdisk)
Code:
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.usb.config=mtp
SYSTEM: flashed with modded stock 4.1.1 JRO03H system image
build.prop: stock 4.1.1 JRO03H build.prop
Code:
ro.build.fingerprint=motorola/tervigon/wingray:4.1.1/JRO03H/405518:user/release-keys
ro.build.description=tervigon-user 4.1.1 JRO03H 405518 release-keys
REMOVED: Stock recovery install script, patch
ADDED: Superuser.apk 3.1.3 and su binary to enable functioning root (thanks, chainsdd)
Hardware SDCard continues to be read-only via documented application permissions (now at /storage/sdcard1)
USERDATA: Launcher favorites updated with new Google Play Store intent (included in stock 4.1.1 JRO03H update from Google)
/data/data/com.android.launcher/databases/launcher.db: updated with new Google Play Store intent.
[size=+1]STOCK ROOTED UPDATE PACKAGE BUILD PROCEDURE[/size]
For the curious and do-it-yourself types, this is how I produced this stock rooted update for the Motorola XOOM Wi-Fi MZ604 (US). I use Ubuntu, but this should also work on other *nix flavors, including OSX. The handy scripts provided by alansj for unpacking and repacking boot images, however, are not Windows friendly.
Ensure Android SDK is properly installed and configured on the workstation
Both adb and fastboot must be functioning properly in order to proceed. This procedure assumes that the directory containing adb and fastboot (or their symlinks) are in the PATH environment variable, allowing them to be called from anywhere.
Ensure perl, cpio, gzip, and gunzip, are properly installed and configured on the workstation
These are necessary to unpack and repack the boot image for modding.
Ensure unpack-bootimg.pl and repack-bootimg.pl scripts are properly installed and configured on the workstation (thanks, alansj)
HOWTO: Unpack, Edit, and Re-Pack Boot ImagesThis procedure assumes that the directory containing these scripts (or their symlinks) are in the PATH environment variable, allowing them to be called from anywhere simply by their name. Note that some PERL configurations may require calling perl and passing the path to the script as an argument.
Ensure ClockworkMod Recovery is properly installed and configured on the device (thanks, solarnz, bigrushdog, koush, et al)
[Recovery] ClockworkMod 3.2.0.0 (R4c) Modded for Internal media [UPDATED 10/6]Also ensure that the ClockworkMod Recovery image is in the working directory on the workstation in case it needs to be reflashed.
Download su and Superuser.apk (thanks, chainsdd)
http://androidsu.com/superuser/Extract the ZIP file containing su and Superuser.apk into the working directory on the workstation.
Download stock images and previous OTA (Over The Air) update packages
3.0.1 HWI69 Images: http://developer.motorola.com/produ...utm_source=supportforums&utm_term=unlockboard
3.1 HMJ37 OTA: http://android.clients.google.com/p...signed-tervigon-HMJ37-from-HWI69.e379f0b9.zip
3.2 HTJ85B OTA: http://android.clients.google.com/p...igned-tervigon-HTJ85B-from-HMJ37.db223b6e.zip
3.2.1 HTK55D OTA: http://android.clients.google.com/p...gned-tervigon-HTK55D-from-HTJ85B.73617300.zip
3.2.1 HTK75D OTA: http://android.clients.google.com/p...gned-tervigon-HTK75D-from-HTK55D.01cd4f05.zip
4.0.3 IML77 OTA: http://android.clients.google.com/p...igned-tervigon-IML77-from-HTK75D.71a21bfe.zip
4.0.4 IMM76 OTA: http://android.clients.google.com/p...signed-tervigon-IMM76-from-IML77.0d062b3b.zipNote that the OTA update scripts check properties to see if the device is identified as "wingray". The above linked version of ClockworkMod Recovery identifies itself as "stingray", so you will get assert errors and the installation will fail. You can disable script asserts by using the toggle script asserts menu option (under install zip from sdcard), but keep in mind that this will allow you to install the updates out of order. The other, safer but more labor-intensive option is to edit the updater-script in each package and remove the "wingray" asserts.
Download the current stock OTA update package
Google hosts the OTA updates for the Motorola XOOM Wi-Fi MZ604 (US). The devices periodically check Google for updates, and when an update has been made available, it will be downloaded (usually to /cache/) with a notification presented to the user.
The full URL to the update package is output to the device log, which is available via logcat (adb logcat; DDMS; aLogcat app). The full URL can also be constructed from just the filename -- available in the device's /cache/ directory if downloaded, or often by searching the web -- by appending it to the following path:
Code:
http://android.clients.google.com/packages/ota/motorola_tervigon/
In this case, we find that the JRO03H update package's filename is f85d815e2b75.signed-tervigon-JRO03H-from-IMM76.f85d815e.zip, which yields the following URL:
4.1.1 JRO03H OTA: http://android.clients.google.com/p...igned-tervigon-JRO03H-from-IMM76.f85d815e.zipSee also the note on the previous step regarding "wingray" asserts.
Save all stock OTA update packages to the hardware SDCard
These will be installed via ClockworkMod Recovery later in the procedure.
Connect the XOOM to the workstation via USB
Also verify that USB debugging is enabled in the settings on the device. The device should show up if the following command is run from a terminal/command prompt:
Code:
adb devices
Backup the device
This process is going to overwrite everything on the device, so backup using whatever method is preferred. ClockworkMod Recovery's Nandroid backup is a great option.
Flash stock images via fastboot
Unpack the zip file containing the stock HWI69 images into the working directory on the workstation and run the following commands from a terminal/command prompt:
Code:
cd <path to working directory>
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
Keep this terminal/command prompt open, as it will be used further.
Install stock OTA updates via ClockworkMod Recovery
Reboot after each update to ensure that it completes -- bootloader updates (HMJ37 and HTK55D), for instance, are performed after rebooting -- but ensure the boot sequence is interrupted with the VolDown key and re-enter ClockworkMod Recovery before the boot animation begins, to prevent overwriting with stock recovery.
Without a bootloader update, press VolDown after waiting a few seconds on the red Motorola logo screen. If there is a bootloader update, however, it gets tricky; after the automatic reboot, wait about 14 seconds on the red logo before pressing VolDown. If nothing happens, reset (Power + VolUp) and try again. If the boot animation begins, try resetting but note that recovery was likely overwritten by stock, requiring a re-flash of ClockworkMod Recovery.
Repeat this procedure of installing and rebooting until the last update is complete and the device is back into ClockworkMod Recovery.
Perform a nandroid backup in ClockworkMod Recovery
This generates clean, current stock images with which to work, while also providing an easier starting point for any future mods.
Download and unpack the boot image
Run the following commands from the terminal/command prompt:
Code:
adb pull /sdcard/clockworkmod/backup/<directory name>/boot.img boot-stock.img
unpack-bootimg boot-stock.img
This will extract the kernel and ramdisk gzip files into the current directory, with the actual ramdisk files being unpacked into a subdirectory (boot-stock.img-ramdisk).
Modify default.prop in ramdisk
Open default.prop (located in the ramdisk subdirectory) in the preferred text editor and edit the following properties:
Code:
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
ro.secure=0 is the most important, for it enables adb to run as root, which is necessary for remounting the system partition as read/write and install su.
Clean up any temp/backup files the text editor may have created in the ramdisk directory before proceeding.
Repack and flash the modified boot image
Run the following commands from the terminal/command prompt:
Code:
repack-bootimg boot-stock.img-kernel.gz boot-stock.img-ramdisk boot-root.img
adb reboot bootloader
fastboot flash boot boot-root.img
fastboot reboot
The device should now boot with a rooted boot image.
Install and configure su and Superuser.apk; remove recovery overwrite files
Remount the system partition as read/write and push the files using the following commands from the terminal/command prompt:
Code:
adb remount
adb push su /system/bin/su
adb push Superuser.apk /system/app/Superuser.apk
adb shell
Once in adb shell, configure the pushed files:
Code:
chown root.shell /system/bin/su
chmod 6755 /system/bin/su
ln -s /system/bin/su /system/xbin/su
chmod 644 /system/app/Superuser.apk
While still in adb shell, remove the recovery overwrite script and patch:
Code:
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
reboot
The device should now boot fully rooted.
Extract the freshly rooted system image
Run the following command from the terminal/command prompt:
Code:
adb shell
Once in adb shell, dump the system image to the hardware SDCard:
Code:
dd if=/dev/block/platform/sdhci-tegra.3/by-name/system of=/storage/sdcard1/system-root.img
exit
Once back to the local prompt, pull the image to the working directory:
Code:
adb pull /storage/sdcard1/system-root.img
Configure the device and test
Ensure the device and apps function normally, including root apps.
Identify any updates outside of system and boot partitions (bootloader, userdata, etc.)
Open all OTA update packages in the preferred ZIP archive manager and go through each updater-script (located in /META-INF/com/google/android/) to determine if any additional updates have been made. This will require some understanding of edify script, which is straightforward and easy to read.
These additional updates will need to be included in the stock rooted update package in order to ensure safe update from any ROM.
Assemble the update package
This simple objective here is to package the rooted boot and system images, files for additional updates (if any), the updater-script with commands to perform the update, and any helper tools into an Android update package (essentially a ZIP file).
While this is a complicated task, it is made easier by starting with existing custom update packages and modifying their contents and script.
Test installation via ClockworkMod Recovery
Load other ROMS -- stock Honeycomb, custom ROM's, etc. -- and test the update using the procedure in the OP. Note that you may need to reflash ClockworkMod Recovery one final time at this point.
Restore personal device backup; dogfood
Restore the backup you made prior to flashing the stock images at the beginning of this procedure, and upgrade your device with the package you've built. Bask in glory.
Many thanks to you' rocking it now.
This is why I love XDA, our amazing developers are right on top of updates and such, creating awesome methods and procedures for updating
Excellent, it's now optimising its apps. I used the EOS R6 recovery which I already had installed. Thanks very much!
Awesome Post.Thanks for your work!
I am getting the error:
file_getprop: failed to stat "/system/build.prop": No such file or directory
E:Error in (file path to zip file)
(Status 7)
Installation apported.
Any suggestions?
Coming from Eos ICS, full wipe...
orb_526 said:
I am getting the error:
file_getprop: failed to stat "/system/build.prop": No such file or directory
E:Error in (file path to zip file)
(Status 7)
Installation apported.
Any suggestions?
Coming from Eos ICS, full wipe...
Click to expand...
Click to collapse
The update is checking that file to see if the device is calling itself a Xoom. Flashing the stock system.img will ensure this file is present. More info on stock images is on post 3 of this thread, specifically the first link in step 6, and instructions in step 11.
Anyone else having this issue?
Went from eos 125 to this stock JB with no problems. Full wipe, install. For me, it's running faster/smoother than anything that i've tried.
Yeah, coming from EOS JB 125 as well. Tried without wipe - did not work. So - wipe first for sure if on custom rom i guess...
Second thing - read instructions carefully - it needs external card during flashing even if the zip is on built in storage.
Other than that - awesome. Smoother than EOS in my opinion. Also - many more languages than AOSP. Google Now actually understands Polish now
One question - how come it has ICS boot animation rather than JB?
You're right, everything works like it should. I think the boot ani is alittle different.
can someone post the boot animation from this? I've been working on trying to extract it from the images, but haven't had much luck yet. TIA!
Error:::: File_getprop: failed to stat "/system/build.prop": No Such file or Directory
E: Error in /SDcard/File name..
(Status 7)????
thanks for any help
I installed over AOKP Milestone 6 I think it was, wiped everything and was good to go, actually started to flash the app through GooManager. Running great thus far.
Crazywhitie said:
Error:::: File_getprop: failed to stat "/system/build.prop": No Such file or Directory
E: Error in /SDcard/File name..
(Status 7)????
thanks for any help
Click to expand...
Click to collapse
Already been answered on the first page of this post.
Just a heads up, it seems that on my Xoom that the sleep functions doesn't work correctly. Instead of going into the normal sleep mode the tablet just dims and the screen never turns off.
Has anyone been brave enough to try this on a mz601?
Confirmed working on a international Xoom. Thanks a lot man. Needed this for some debugging! :good:
fidju said:
Already been answered on the first page of this post.
Click to expand...
Click to collapse
Thanks for Pointing that out.. I missed it... Worked Perfect...
Hello,
In the process of rooting and trying to install CWM Recovery in preparation to flash Cyanogenmod, I seem to have denied myself access to the phone's internal storage. In the "File Manager" app, I get the following screen:
Local: /storage
No files
No search results
In addition, any app that requires access to internal memory will not work, instead showing messages such as "Try again after scanning media files" or "Not enough storage". If I plug in the USB cable and set it to "Media sync (MTP)" mode, Windows Explorer will show the device but list the internal storage as having "0 bytes" and no files.
I already tried the following:
- Factory reset
- Flashing the official ROM through the Windows Enabler / UpTestEX tools
In both tries the phone was "reset", as in it returned to the initial Android welcome screen where you set up your Google account, but in each case I still didn't have access to internal storage.
This is what I have in the "About phone -> Software information" option:
Android version: 4.1.2
Baseband version: APQ8064T/MDM9x15M
Kernel version: 3.4.0
Build number: JZO54K
Software version: E98810b
The phone does not have Wi-Fi access either, which is why I was tinkering around with custom ROMs in the first place, so I won't be able to download anything to it as part of the solution.
Is there anything else I can try?
I'm guessing you used FreeGee to install CWM? Perhaps try restoring?
If that didn't work... Id move the EFS backups to my computer. I'd make a NAND backup in CWM. Then I'd get CM and gapps on a micro SD. I'd do a format of system, data, and cache. Then I'd install CM and gapps. Then I'd cross my fingers.
Sent from my LG-E980 using Tapatalk
ackliph,
Since I didn't have Wi-Fi access on the phone, and at the time I didn't know how to reverse tether it to the computer, I was looking for a procedure to install CWM Recovery that didn't involve downloading files directly within the phone (only transfering via USB). Right now I can't find the exact instructions I used, but it was similar to what is described by hkfriends in this thread: http://forum.xda-developers.com/showthread.php?t=2361941, the only difference being that the image I downloaded was not that one.
I rooted the phone with Universal Root, then followed those instructions to install CWM Recovery. It seemed to have worked, but when I rebooted... nothing happened! The phone booted normally, and if I tried entering recovery mode all I got was the stock LG recovery.
I continued looking for another way to install a custom recovery, but instead came upon instructions to flash KDZ files with UpTestEx. Since the immediate problem I was trying to solve was the lack of Wi-Fi access (and not really the custom ROM), I thought it couldn't hurt to try updating the stock ROM. The procedure did update my ROM, but I ended up in my current predicament: no access to internal storage, and still no Wi-Fi access! It even managed to unroot the phone.
So your suggestion would be to try installing CM via a microSD card. OK, I can get a microSD and try that. However, I do believe I will need root access to do anything of the sort. I tried Universal Root again, and got the following messages:
Beginning Root Process
/system/bin/sh: can't create /sdcard/G_security: Permission denied
Now change from Charge Only to MTP
No need to disconnect USB
Press Enter after making the change.
adbd cannot run as root in production builds
error: device not found
If uid=0(root), gid=0(root) is displayed
Press Enter to Continue
1955 KB/s (1085140 bytes in 0.542s)
mount: permission denied (are you root?)
cp: can't create '/system/xbin/busybox': Read-only file system
failed to copy 'su' to '/system/xbin/su': Read-only file system
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file system
Unable to chown /system/xbin/su: No such file or directory
You are now properly Rooted.
Click to expand...
Click to collapse
Evidently, that didn't work.
I guess I will need some other method of rooting it.
Q&A for [ROM][UNOFFICIAL] CyanogenMod 12 Nightlies
FAQ:
Q: I tried to flash the ROM and got this:
Code:
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/..path od ROM.zip
(Status 7)
Installation aborted.
Or I'm having other recovery issues.
A: Update your recovery to supported one. See the list below.
TWRP 2.8.1.2 ACE or newer
Q: I've used HTC Dev unlock and flashed the rom but it won't boot. What should I do?
A: You need to extract boot.img from the zip and flash it via fastboot. If you don't have fastboot executable anymore from flashing recovery, install Android SDK platform tools (Linux users should find it from distro's package management) and then reboot to bootloader, open command prompt and navigate to the location you extracted your boot.img and type:
Code:
fastboot flash boot boot.img
You need to repeat this everytime you flash new version of this rom to ensure everything will work fluently as long as you have just basic HTC Dev unlock.
Q: Where are my developer and performance options?
A: http://goo.gl/jpS8r
Q: Where is my root?
A: http://www.cyanogenmod.org/blog/all-about-l-part-2 (Read under "Superuser where?")
Q: Feature X doesn't work, let's make 1000 posts about it to annoy everyone.
A: Please, dont. Use search and then use search again and only then report your problem with necessary logs. [Logcat guide, thanks to MusikMonk for the link]
Q: I hate you for not fixing this issue X!!!
A: I love you too.
Q: How I can build CM12.0 myself?
A: Setup a basic Android build environment.
Code:
mkdir cm12
cd cm12/
repo init -u git://github.com/CyanogenMod/android.git -b cm-12.0
mkdir -p .repo/local_manifests
wget https://github.com/OpenDesireProject/android/raw/cm-12.0/local_manifest.xml -O .repo/local_manifests/cm_ace.xml
repo sync
. build/envsetup.sh
lunch cm_ace-userdebug
mka bacon
Once the build finishes you'll find your goods from out/target/product/ace/ directory.
Q: Something about something something something.
A: Ask the guy/gal next to you.
Thanks..reserved?
Sent from my ATRIX HD using Tapatalk
Home button not working. Have to use back button
Camera Bug
Camera is in the Apps not listen and it dont work from Lockscreen.
Sorry for my English and a big Thanks from Germany / EinfachAleks
No sounds.
---------- Post added at 11:32 AM ---------- Previous post was at 11:14 AM ----------
I don't have camera at all
Sent from my Desire HD using Tapatalk
Great job Tested on my Inspire 4G with alpha gaps all - so all works good but one problem at startup setting after ten minutus of thinking it cant set up my GSM career and tell me to set up it next time I'll think okay wait when all google sutups done ..... go to setting /mobile wireless/operator settings ... and at this moment I have a crash. I hawe an Ukrainian operator maybe this thing cause such problem Thank you a lot for you futer job at this rom And WiFi works greate ))))
For me the Home Key just working fine...im waiting for the next Snapshot
I'm gonna download zip again and flash again. Maybe bad flash.
Doge2 and recovery
Doge2 Installation doesn't work with 4EXT Recovery Touch v1.0.0.6 RC 3.
ApplyParsedPerms: lsetfilecon of /system/lost+found to ubject_r:system_file:s0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
E:Error in /sdcard/ROM CM12/cm-12-20141130-UNOFFICIAL-DOGE2-ace.zip
(Status 7)
Installation aborted.
With TWRP 2.8.1.0 it installs but these TKruzze gapps (https://s.basketbuild.com/devs/TKruzze/Android 5.0 GApps/Micro-Modular GApps/) gives error
E: Error executing update binary zip "gapps location.zip"
INSTALLATION FAILURE: Your device does not have sufficient space available in
the system partition to install this GApps package as currently configured.
You will need to switch to a smaller GApps package or use gapps-config to
reduce the installed size.
Finnaly old bug for me.
Does anyone have same problem like I do? I can't make partitions with TWRP 2.8.1.0 partition editor! With 4ext recovey I can make partition but with TWRP I can't.
http://forum.xda-developers.com/htc-desire-hd/help/qa-twrp-2-8-1-0-cwm-6-0-5-1-unofficial-t2952947
first i want to thank you for this amazing rom
and i want to ask if i update from doge 1 to doge 2 should i flash boot.img again after installing the rom
marek287 said:
Doge2 Installation doesn't work with 4EXT Recovery Touch v1.0.0.6 RC 3.
ApplyParsedPerms: lsetfilecon of /system/lost+found to ubject_r:system_file:s0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
E:Error in /sdcard/ROM CM12/cm-12-20141130-UNOFFICIAL-DOGE2-ace.zip
(Status 7)
Installation aborted.
http://forum.xda-developers.com/htc-desire-hd/help/qa-twrp-2-8-1-0-cwm-6-0-5-1-unofficial-t2952947
Click to expand...
Click to collapse
I have the same error
marek287 said:
Doge2 Installation doesn't work with 4EXT Recovery Touch v1.0.0.6 RC 3.
ApplyParsedPerms: lsetfilecon of /system/lost+found to ubject_r:system_file:s0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
E:Error in /sdcard/ROM CM12/cm-12-20141130-UNOFFICIAL-DOGE2-ace.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Try to format your system partition manually. If that doesn't help, contact 4EXT dev. Generally I can't fix recovery related issues like this seems to be.
marek287 said:
With TWRP 2.8.1.0 it installs but these TKruzze gapps (https://s.basketbuild.com/devs/TKruzze/Android 5.0 GApps/Micro-Modular GApps/) gives error
E: Error executing update binary zip "gapps location.zip"
INSTALLATION FAILURE: Your device does not have sufficient space available in
the system partition to install this GApps package as currently configured.
You will need to switch to a smaller GApps package or use gapps-config to
reduce the installed size.
Click to expand...
Click to collapse
You'll probably need even smaller gapps. Our system partition is getting very small as the base system size has increased a lot since gingerbread. I haven't tried any gapps yet as they are irrelevant to our roadblocker issues so I can't give any recommendations.
desire hd user said:
first i want to thank you for this amazing rom
and i want to ask if i update from doge 1 to doge 2 should i flash boot.img again after installing the rom
Click to expand...
Click to collapse
Yes, if you are S-ON. There are some kernel related changes which are included in the boot.img so it needs to be updated too.
Mustaavalkosta said:
Try to format your system partition manually. If that doesn't help, contact 4EXT dev. Generally I can't fix recovery related issues like this seems to be.
Click to expand...
Click to collapse
That was mine second throught but main goal was to anounce others that problem. I posted it to 4EXT recovery Q/A threat
http://forum.xda-developers.com/showpost.php?p=57171180&postcount=2
and recontacted (PM) to jrior001 TWRP recovery partition bug.
rom not working
help me. Excuse, but apparently I'm the only one that failed to install the rom.
during installation sticking a message like warnig and then something about the sound and would not start more
I've already checked MD5
DOGE2 + PA GApps ALPHA1 flash succeeded
Thank you Musta and the team for great job!
http://forum.xda-developers.com/showthread.php?p=56560109
I flashed DOGE2 + PA GApps ALPHA1, and they work fine.
(cm-12-20141130-UNOFFICIAL-DOGE2-ace.zip + pa_gapps-micro-5.0-ALPHA1-20141117a-signed.zip)
Before flashing, I made .gapps-config which containing the text "NanoGApps", and placed it in the same folder as the GApps zip.
Then, flashing has succeeded.
I didn't try "PicoGApps" option, but it will also succeed, I suppose.
matbeta said:
help me. Excuse, but apparently I'm the only one that failed to install the rom.
during installation sticking a message like warnig and then something about the sound and would not start more
I've already checked MD5
Click to expand...
Click to collapse
Install TWRP 2.8.1.0 then install the rom again. http://forum.xda-developers.com/showthread.php?t=2780164
After downloading writes: "sim card added restart your device".
bratmarat said:
After downloading writes: "sim card added restart your device".
Click to expand...
Click to collapse
Yeah, it's a bit wonky. Just hit back to skip it for now. Telephony code is still undergoing some changes.
Very good job. I wait for doge3
hello Mustaavalkosta, Great job, say thanks to you and all the dev team.
I am chinese user, i found doge 3 always crash when i install most common app.
such as baidunews, baidu market, zhihu
please check it, hope doge 4 coming as soon as possible.