Database Info

[Q] Help! After wipeing can't install CM7!

I am following the tutorial "http://forum.xda-developers.com/showthread.php?t=955719". I put the update-cm-7-7.0.0-RC1-NS-signed.zip on the sd card. Then in ClockworkMod Recover v3.0.0.5 I did the steps: 1) format /data, format /cache, and wiped Dalvick Cache.
Then I went to install zip from sdacrd and clicked on "update-cm-7-7.0.0-RC1-NS-signed.zip" to install the zip. I got:
-- Installing: /sdacrd/update-cm-7.0.0-RC1-NS-signed.zip
Finding update package....
Opening update package....
E: Can't open /sdcard/update-cm-7.0.0.0-RC1-NS-signed.zip (bad) Installation aborted.
Can anyone help please????

phone is not bricked though. i tried this again and got the same problem. i also had this problem when trying to install the su.zip utility(first time was successful, but after fastboot oem unlock i tried tried to reinstall it just to be safe but it kept failing out also. however, i checked with root checker and it said i had super user access). could my sdcard filesystem be corrupter? any suggestions?

Most likely bad download. Download again. Check md5 if you're still not sure.

From inside the phone normal OS I erased USB and replaced the file on the usb and it worked! Maybe a corrupted filesystem.

[Q] Possibly bricked - what are my options?

Have a Telstra One XL 1.89 - after hours of reading/researching I finally rooted the phone and flashed TWRP (ver 2.2.2.0) recovery with a custom ROM.
Everything was working fine until I tried to install a different ROM - I made a backup via TWRP, installed the new ROM but it wouldn't boot ... no worries I had the backup ... I accidentally selected FACTORY RESET from the bootloader instead of RECOVERY which seemed to have wiped all my data on the internal SD card - so my backup has been wiped.
I'm still able to access TWRP so I thought I could simply mount my SD card to my computer and copy my old ROM to flash - however I can't mount the SD card from TWRP - TWRP's console is throwing up "E:failed to mount /sdcard (Invalid argument)" and "E:Unable to mount /sdcard when trying to read settings file." errors - hence in the Mount menu, I can't check the "Mount SDCard" checkbox! (WTF?) - I Google'd this and someone advised that you will need to partition the SD card from within TWRP before it will allow you to mount it - I tried partitioning it but still throwing up those errors
I can also access the device from command prompt via adb - so I tried to flash a rom directly via fastboot but it throws up a "FAILED (remote: not allowed)" when it tries to flash it.
What are my options here? Am I completely screwed? I'm currently in the process of downloading the Telstra RUU - will this even work in my case?? Any help would be GREATLY appreciated - pulling my hair out here ... 2 week old phone

The RUU will make it all better
just lock your bootloader again before you run it

Look who's still floating
Sent from my HTC One X using xda premium

So you could post here when you didn't have a hox but I can't? Oooookayyyy.

In my heart I always had a hox......now I hate this p.o.s yet I'm still here, smh
My fastboot oem unlock tabby will be here Tuesday tho
Sent from my HTC One X using xda premium

slavlazar said:
Have a Telstra One XL 1.89 - after hours of reading/researching I finally rooted the phone and flashed TWRP (ver 2.2.2.0) recovery with a custom ROM.
Everything was working fine until I tried to install a different ROM - I made a backup via TWRP, installed the new ROM but it wouldn't boot ... no worries I had the backup ... I accidentally selected FACTORY RESET from the bootloader instead of RECOVERY which seemed to have wiped all my data on the internal SD card - so my backup has been wiped.
I'm still able to access TWRP so I thought I could simply mount my SD card to my computer and copy my old ROM to flash - however I can't mount the SD card from TWRP - TWRP's console is throwing up "E:failed to mount /sdcard (Invalid argument)" and "E:Unable to mount /sdcard when trying to read settings file." errors - hence in the Mount menu, I can't check the "Mount SDCard" checkbox! (WTF?) - I Google'd this and someone advised that you will need to partition the SD card from within TWRP before it will allow you to mount it - I tried partitioning it but still throwing up those errors
I can also access the device from command prompt via adb - so I tried to flash a rom directly via fastboot but it throws up a "FAILED (remote: not allowed)" when it tries to flash it.
What are my options here? Am I completely screwed? I'm currently in the process of downloading the Telstra RUU - will this even work in my case?? Any help would be GREATLY appreciated - pulling my hair out here ... 2 week old phone
Click to expand...
Click to collapse
Hey mate,
RUU will work but before you do just try mounting it through twrp then plugging it into your pc.
When you're in the mount menu in twrp make sure you hit mount usb storage for Windows to recognise it.
When I did this I got a prompt in Windows that said it needed to format the drive so I formatted it then just copied over the rom I wanted to flash then unmounted and flashed the rom.
Sent from my HTC One XL using xda premium

[Q] Help! Can't restore galaxy s3 to factory rom

I have a galaxy S3 phone (AT&T i747) and I've rooted it. Also I've backed up the factory rom using clockworkmod and get several files in one folder named "1970-04-15.10.19.58", and then I install "rom manager" and tried several different roms. Then I want the factory rom back, but when I went into the clockworkmod recovery mode, I can't find the backup! I tried to back up the phone again to see if they are stored in the same place, but very weirdly, I couldn't find the back-up folder anywhere while I still can see the back up folder when I want to restore in clockworkmod recovery mode. I do remember the version of clockworkmod changes (probably) because of the rom manager (which asks to flash a recovery before install roms), and I wonder if it's the difference in version that cause this problem.
Could anyone tell me why this happens and how I can get the back-uped version in the clockworkmod recovery mode? Thank you very much!

question update
It seems the clockworkmod messes up the folders. Now I get a folder with name 0, and other folders with "legacy" and "obb", does anybody how to fix the folder problem in clockworkmod? Thank you!
yixiaxian said:
I have a galaxy S3 phone (AT&T i747) and I've rooted it. Also I've backed up the factory rom using clockworkmod and get several files in one folder named "1970-04-15.10.19.58", and then I install "rom manager" and tried several different roms. Then I want the factory rom back, but when I went into the clockworkmod recovery mode, I can't find the backup! I tried to back up the phone again to see if they are stored in the same place, but very weirdly, I couldn't find the back-up folder anywhere while I still can see the back up folder when I want to restore in clockworkmod recovery mode. I do remember the version of clockworkmod changes (probably) because of the rom manager (which asks to flash a recovery before install roms), and I wonder if it's the difference in version that cause this problem.
Could anyone tell me why this happens and how I can get the back-uped version in the clockworkmod recovery mode? Thank you very much!
Click to expand...
Click to collapse

Now the phone is totally messed up by me... Can't boot, can't go to download mode, only be able to go to cwm recovery mode, but couldn't do anything in that mode... if anyone knows how to solve the problem please do tell me...
Problem:
CWM-based Recovery v5.5.0.4
1. When choose "wipe data/factory reset":
-- Wiping data...
Formatting /data...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Error mounting /sdcard/.android_secure!
Skipping format...
Data wipe complete.
2. When choose "backup and restore"->"restore from internal sdcard":
Couldn't open directory.
No files found.
3. When "install zip from sdcard" -> "choose zip from internal sdcard":
-- Installing: /emmc/0/SD Card/0/cm-10.0-20130904-EXPERIMENTAL-d2att-M2.zip
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "d2att" || getprop(ro.build.product")=="d2att"
E:error in /emmc/0/SD Card/cm-10.1-20130304-EXPERIMENTAL-d2att-M2.zip
(Status 7)
Installation aborted.

Problem solved
Update: Try to use Odin to install Samsung original stock firmware and it works!
Samsung firmware (AT&T): I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5
Odin version v3 3.07 (I tried 3.04 but it doesn't work.)
yixiaxian said:
Now the phone is totally messed up by me... Can't boot, can't go to download mode, only be able to go to cwm recovery mode, but couldn't do anything in that mode... if anyone knows how to solve the problem please do tell me...
Problem:
CWM-based Recovery v5.5.0.4
1. When choose "wipe data/factory reset":
-- Wiping data...
Formatting /data...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Error mounting /sdcard/.android_secure!
Skipping format...
Data wipe complete.
2. When choose "backup and restore"->"restore from internal sdcard":
Couldn't open directory.
No files found.
3. When "install zip from sdcard" -> "choose zip from internal sdcard":
-- Installing: /emmc/0/SD Card/0/cm-10.0-20130904-EXPERIMENTAL-d2att-M2.zip
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "d2att" || getprop(ro.build.product")=="d2att"
E:error in /emmc/0/SD Card/cm-10.1-20130304-EXPERIMENTAL-d2att-M2.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse

Summary
Rooting is easy, installing ROM is easy, as long as you do according to the online articles, but keep everything correct is not!
Flash original factory firmware using Odin is very powerful. (It even works when phone can't boot)
I first use Odin to root my galaxy s3, then backup the rom, and then use rom manager to install different roms, however those roms aren't as good as in introduction. And worsemore, when I want to switch back using restore, the restore function goes wrong.
I then did a lot of stupid things, try the functions on recovery and try to move the backup to "right" places, the result is I totally messed up the phone and it can't boot.
Luckily I still can go to the download mode by pressing "volumn down"+"home"+"power" -> "volumn up". I use Android 4.1.1 AT&T Samsung i747 firmware and Odin v3 3.07 to get everything back to normal. (thank goodness I back up the data before I play this game).
All in all, new version Odin + original factory firmware is powerful! :good:

[Q] how to fix error E:/ can't mount cache log on htc desire sv (magnids)

Hi..XDA Team, i have rooted htc desire sv (magnids), During the installation of "Firmware FULL DEODEX for HTC Desire SV cid HTC_A48" according to the guide of "Karaman_deniz" through "http://forum.xda-developers.com/showthread.php?t=2323678&page=2 ".
My cwm recovery version is 6.0.2.7. when i trying to wipe cache through cwm recovery, i got error E:/ can't mount cache log after that i ignored error and click on advanced menu -click on wipe dalvik cache then nothing happened and cwm recovery returned on advanced menu..
it show error
E:can't mount /cache/recovery/command
E:cant mount /cache/recovery/log
E:cant mount cache/recovery/last_log
after that i click on - install zip from sd card then choose zip from sd card and installed Firmware FULL DEODEX for HTC Desire SV cid HTC_A48, then i got message installation complete and then i click on reboot system.
after rebooting first time everything seem to be ok.. but when i run google play store and trying to update apps, i got new error " insufficient storage available" now i am unable to update apps and manually installation of .apk file... guys pls help ASAP..

[Q] I have broken my Moto G

Hi, I have recently tried to revert my Moto G from Cyanogenmod to stock firmware using a zip file I downloaded called "RETAIL-GB_4.3_14.10.0Q3.X-76-LGG-8_cid7_CFC_1FF_svc.xml.modaco.r3". That got me stuck in a boot loop so I tried to boot into recovery, which had been uninstalled, so I reinstalled twrp from my computer.
I then tried to reinstall Cyanogenmod 12 but it said it couldn't mount storage and data and failed every time. Please help me because I don't think my parents are going to be getting me a new phone anytime soon because i'm on a contract.
Phone
-Moto G (falcon)
-Recovery = TWRP
-Bootloop
EDIT: Does anyone know how to fix the no service problem?

Try flashing the Retail GB 4.4.4 using fastboot or mfastboot.

mrbrokenphone said:
Hi, I have recently tried to revert my Moto G from Cyanogenmod to stock firmware using a zip file I downloaded called "RETAIL-GB_4.3_14.10.0Q3.X-76-LGG-8_cid7_CFC_1FF_svc.xml.modaco.r3". That got me stuck in a boot loop so I tried to boot into recovery, which had been uninstalled, so I reinstalled twrp from my computer.
I then tried to reinstall Cyanogenmod 12 but it said it couldn't mount storage and data and failed every time. Please help me because I don't think my parents are going to be getting me a new phone anytime soon because i'm on a contract.
Phone
-Moto G (falcon)
-Recovery = TWRP
-Bootloop
Click to expand...
Click to collapse
In twrp you have to format data partition
Remember wiping is different from format
After format it will mount data partition and flash whatever you want it will work
Sent from falcon
PRESS THANKS IF HELPED?

sjandroiddeveloper said:
In twrp you have to format data partition
Remember wiping is different from format
After format it will mount data partition and flash whatever you want it will work
Sent from falcon
PRESS THANKS IF HELPED
Click to expand...
Click to collapse
Thanks, I wiped the data. When I tried to install CyanogenMod again, it said:
Installing '/sdcard/cm.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
This package supports bootloader(s): 0x4118, 0x4119; this device has bootloader 0x4113.
E: Error executing updater binary in zip '/sdcard/cm.zip'
Error flashing zip '/sdcard/cm.zip'
Updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/system'
...done
The install failed but took longer than my other attempts before your advice. Is this good or bad?

mrbrokenphone said:
Thanks, I wiped the data. When I tried to install CyanogenMod again, it said:
Installing '/sdcard/cm.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
This package supports bootloader(s): 0x4118, 0x4119; this device has bootloader 0x4113.
E: Error executing updater binary in zip '/sdcard/cm.zip'
Error flashing zip '/sdcard/cm.zip'
Updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/system'
...done
The install failed but took longer than my other attempts before your advice. Is this good or bad?
Click to expand...
Click to collapse
It says your bootloader is outdated, you have a kitkat bootloader, for newer versions of cyanogenmod-based lollipop ROMs you need the lollipop bootloader, wich is 41.18 for the versions XT1032,XT1033,and google play edition of motorola, and 41.19 for the CDMA version of the phone. You can search in Original development thread of CM12 on how to upload the bootloader the safest way, because it's the most easiest and risky way to brick your phone permanently. In the thread you have precise instructions on how to do that the most safe way, so i won't write any tutorials to you here.
Good luck and hope i helped!/

mrbrokenphone said:
Thanks, I wiped the data. When I tried to install CyanogenMod again, it said:
Installing '/sdcard/cm.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
This package supports bootloader(s): 0x4118, 0x4119; this device has bootloader 0x4113.
E: Error executing updater binary in zip '/sdcard/cm.zip'
Error flashing zip '/sdcard/cm.zip'
Updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/system'
...done
The install failed but took longer than my other attempts before your advice. Is this good or bad?
Click to expand...
Click to collapse
The installation took longer because now the phone was able to mount data partition, which is obviously a good thing
Your error is because of older bootloader
U can either update the bootloader which I would suggest is better option or you can install a nightly older than 24th March which is compatible with even older bootloader
PS : I told you to format and not wipe, what did you do exactly ?
Sent from falcon
PRESS THANKS IF HELPED?