Related
Hey i need a different recovery than rom manager all i get now is error messages when flashing new roms something about it being updated to 3.0 gingerbread and i dont understand then it says flashing aborted??? wtf does that mean??? I never had a problem before. Im thinking of getting a different phone so i can start fresh and not install that stupid program. Why update a perfectly good program to the point of not even being able to use it?? Someone save me im going crazy. If anyone has a link to a different recovery or an older rom manager version plzzz hook me up with it.
What version of CWM are you on. I'm assuming 3.0.0.5 ........
It sounds like you are most likely using the new RM (3.x) with an old recovery (2.x)
For more info on the changes to recovery:
[RECOVERY][UNOFFICIAL]Clockworkmod 3 series
That will also explain why you are seeing certain scripts fail.
If you want to update your recovery, in RM go to your settings and check off "erase recovery." Then in the main screen again, scroll down to "All ClockworkMod Recoveries" and choose 3.0.0.8
kickingharold73 said:
Im thinking of getting a different phone so i can start fresh and not install that stupid program.
Click to expand...
Click to collapse
That would be a massive overreaction to a very fixable problem. Also, it doesn't matter what phone you are using: to use RM's functionality, you have to be using a compatible version of recovery.
kickingharold73 said:
Why update a perfectly good program to the point of not even being able to use it??
Click to expand...
Click to collapse
The link I provided above will fill you in.
Sounds like youre trying to flash a zip not using edify...ask the developer to update to 3.x, i also never use rm to flash roms, and i advise you to go into recovery manually. 2.x is going to be obsolete if it technically isnt already. So eventually well only b using 3.x
Sent from my Incredible using XDA App
Hello,
I just wondering if why i got this error on flashing the new update for WC...
Im using CWM revcovery 5...6..??
this is the error message;
assert failed: write_raw_image("/tmp/boot.img". "boot")
E;Error in /sdcard/HTCRoms/Roms/WC1.5-Full-Odex.zip
(Status 7)
Installation aborted
:C.. Please Help.. Many Thanks!
Try downloading the rom again....then flash it
If that doesnt work, try a different recovery(TWRP touch or RZR recovery)
I redownload the rom now its WC2.0 .... Still same Error (Status 7)...
I'm using a Marvel version of the Rom...
Edit: Try TWRP as a alternate recovery... Still no Luck.. same Error of Status 7... i wonder why but before i always reflash the version 1.1 and no problems but when the 1.6 is release (and tried 2.0) now it show up...
Now im stuck on CM7 03-24-12. with BT-fix alpha... :C
Maybe i could try CWM 5.0.2.8 coz i use alquez's MOD 5.0.2.6...
P.S. i only find a .IMG version is there a .ZIP version of it?? Many Thanks!
Thank you Mr. cSoulr666 i wont lose hope..
if you are on CM7....use the IMG file to flash CWM....First rename the file to a simpler name, e.g- "recovery.img"
Put the IMG file in the root(no folders) and then open terminal emulator and type the following commands
First, type "su" (without quotes) for root permissions
Then "flash_image recovery /sdcard/recovery.img"
And presto!!! The img file will be flashed
Here you go
hassan89 said:
Here you go
Click to expand...
Click to collapse
Thanks but this method only works on S-OFF phones....i was providing a universal solution to it
csoulr666 said:
Thanks but this method only works on S-OFF phones....i was providing a universal solution to it
Click to expand...
Click to collapse
It worked on my phone and its S-ON with an unlocked bootloader ofcourse!
You just flashed it in recovery?
csoulr666 said:
You just flashed it in recovery?
Click to expand...
Click to collapse
Nope i didnt have a custom recovery back then.All i did was put this file into my sd card.Open the bootloader.It automatically installed the recovery within the zip file.
try a different recovery
csoulr666 said:
if you are on CM7....use the IMG file to flash CWM....First rename the file to a simpler name, e.g- "recovery.img"
Put the IMG file in the root(no folders) and then open terminal emulator and type the following commands
First, type "su" (without quotes) for root permissions
Then "flash_image recovery /sdcard/recovery.img"
And presto!!! The img file will be flashed
Click to expand...
Click to collapse
Thank You so much..!! now i've .8 version.. now i'll try again if this works...
the ZIP didnt work for me..
P.S. im BOOTLOADER unlocked and S-OFF...
Tried to install on my HTC Wildfire S all WilChild mods (tried full and light, odex and de-odex) - roms installed succesfully but after I pass startup wizard I get error that Nemus app got an exception and asked me to close it.
Is there any fix of this.
Hense Mod works fine so not sure that it's problem on my side (but maybe, I only can confirm that each time I installed mod after full wipe)
DJ_ZX said:
Tried to install on my HTC Wildfire S all WilChild mods (tried full and light, odex and de-odex) - roms installed succesfully but after I pass startup wizard I get error that Nemus app got an exception and asked me to close it.
Is there any fix of this.
Hense Mod works fine so not sure that it's problem on my side (but maybe, I only can confirm that each time I installed mod after full wipe)
Click to expand...
Click to collapse
I'm working on a full Sense version of WildChild (due to request) so that might be a bit more stable for you.
The odex version of WildChild uses some funky install routines that I may abandon on future release. The funny thing is that only a very tiny portion of users are experiencing the fc problem (something like 1%!) so I'm not entirely convinced it's a ROM issue, but I'll see what I can do to add more stability. Stay tuned.
The Sense ROM is nearly finished...
Tigger31337 said:
I'm working on a full Sense version of WildChild (due to request) so that might be a bit more stable for you.
The odex version of WildChild uses some funky install routines that I may abandon on future release. The funny thing is that only a very tiny portion of users are experiencing the fc problem (something like 1%!) so I'm not entirely convinced it's a ROM issue, but I'll see what I can do to add more stability. Stay tuned.
The Sense ROM is nearly finished...
Click to expand...
Click to collapse
Woooo!! cant w8 for that!!! :d
Sir tigger.. Maybe some user experience status 7 because of the size of Boot.img... i just guessing cause im using ur rom right now but i overwrite the boot.img using one form the Hensemod... 3.5mb?? vs. 2.7mb?? i dunno maybe some WFS user got a limitation for that... that way i got rid of that status 7....
about the Sense version of WC.. could take a look of this:
http://forum.xda-developers.com/showthread.php?t=1652187
Maybe you could ask the guy who made it and put it on the sense rom.. (just hoping...) But i'll surely use it after u finish the sense version.. Godbless...
about WildChild 2.0 rom, how about battery consumption? my wife have Wildfire S and still using stock rom on it... maybe i will change to Wildchild rom if it makes the battery stamina longer...
arronov said:
about WildChild 2.0 rom, how about battery consumption? my wife have Wildfire S and still using stock rom on it... maybe i will change to Wildchild rom if it makes the battery stamina longer...
Click to expand...
Click to collapse
I get a full day of normal use and at the end off the day I have 30-40% left you can use some tweaks to lower your battery drain check the forum
Send from my HTC Wildfire S
ROM. Wildchild. v2. 0
I have CWM 6.0.1.2 installed but when I go to install cm10 stable i get status 7 yet CM10 M1 installed fine any ideas?
bulldog2000 said:
I have CWM 6.0.1.2 installed but when I go to install cm10 stable i get status 7 yet CM10 M1 installed fine any ideas?
Click to expand...
Click to collapse
Did you make sure you downloaded the correct build for your phone? Something so simple, but sometimes overlooked.
yup the att (i747) im on telus but its the same model
bulldog2000 said:
yup the att (i747) im on telus but its the same model
Click to expand...
Click to collapse
Try redownloading the d2att zip, just in case of a bad download. Still have the problem, switch out your recovery for TWRP. There's a verification problem happening.
still get it with TWRP
the full error message is
Code:
asser faild : getprop("rp.product.device") '' " (status 7)
bulldog2000 said:
still get it with TWRP
the full error message is
Code:
asser faild : getprop("rp.product.device") '' " (status 7)
Click to expand...
Click to collapse
Well the number one thing I see is there is no such thing as "rp.product.device" should be "ro.product.device" this may be causing your trouble, check your build prob in root explorer.
BAM1789 said:
Well the number one thing I see is there is no such thing as "rp.product.device" should be "ro.product.device" this may be causing your trouble, check your build prob in root explorer.
Click to expand...
Click to collapse
it is ro.product.device
bulldog2000 said:
it is ro.product.device
Click to expand...
Click to collapse
Does is say d2att under that? I really do not know beyond an incorrect build being flashed.. if all else fails go back to stock.
I'm sure you figured it out already, but just incase you didn't. I had the same issue when trying to flash a cm rom over a ported rom from a different phone like serenity and such. Two things worked for me, One do a factory reset with all the usual wipes, then reboot recovery, Two is to do a Odin flash back to stock and start over. I've only had this happen twice and both times I was coming from a ported rom.
Hope this helps.
Thanks had the wrong recovery.img, its always the simple things under your nose that you miss
im not a noob and never had thid problem in years. i installed twrp through goo mananger. The weird thing is it installs kernels just fine, but not a rom, any ideas? please help
Luthien1 said:
im not a noob and never had thid problem in years. i installed twrp through goo mananger. The weird thing is it installs kernels just fine, but not a rom, any ideas? please help
Click to expand...
Click to collapse
What error does it give when it fails to flash a ROM? What ROM are you trying to flash?
lordcheeto03 said:
What error does it give when it fails to flash a ROM? What ROM are you trying to flash?
Click to expand...
Click to collapse
it says e error, its very strange, i tried installing cwm and that recovery wont even let me make a backup, this is terrible uhhh... sorry it just says E: error and doesnt say anything else
Luthien1 said:
it says e error, its very strange, i tried installing cwm and that recovery wont even let me make a backup, this is terrible uhhh... sorry it just says E: error and doesnt say anything else
Click to expand...
Click to collapse
It says E: error when you try to make a backup as well?
lordcheeto03 said:
It says E: error when you try to make a backup as well?
Click to expand...
Click to collapse
ok i had twrp through goo manager, and i was able to make backups and install kernels just finel but when i tried a rom such as infamous it gave me the error, so i tried to install through micro sd card, no luck same error something about it not being mounted. So, i installed cwm and tried to make a backup but then i ran out of space, so the backup failed, so i had to delete some stuff, now im trying to back up again, then i will try to install a rom with cwm
this is so strange, i didnt do anytihng out of the ordinary, i got root by chainfire, then installed goo manager, and then a custom kernel...the most viewed one right now, so i thought it was legit which im sure it is, then a rom..... to end the madness, then i keep getting errors, its so frustrating
Luthien1 said:
ok i had twrp through goo manager, and i was able to make backups and install kernels just finel but when i tried a rom such as infamous it gave me the error, so i tried to install through micro sd card, no luck same error something about it not being mounted. So, i installed cwm and tried to make a backup but then i ran out of space, so the backup failed, so i had to delete some stuff, now im trying to back up again, then i will try to install a rom with cwm
Click to expand...
Click to collapse
Ok, see, now that is getting to the meat. Try flashing another ROM... I understand you might just want Infamous, but try flashing another one just for testing purposes. I'm thinking you're one to add to the list of having a bad Infamous d/l.
lordcheeto03 said:
Ok, see, now that is getting to the meat. Try flashing another ROM... I understand you might just want Infamous, but try flashing another one just for testing purposes. I'm thinking you're one to add to the list of having a bad Infamous d/l.
Click to expand...
Click to collapse
i did i tried flashing jedi rom and that failed too, soo this is just weird
i got frusturated and said if i cant have a custom rom, ill debloat now im getting errors, im on my way to a bricked device
Luthien1 said:
i got frusturated and said if i cant have a custom rom, ill debloat now im getting errors, im on my way to a bricked device
Click to expand...
Click to collapse
I may be overboard with my suggestion, but it wouldn't hurt to Odin back to 100% stock and restart your journey.
now it says E cant open/sdcard/o/download/jedi(bad)
Luthien1 said:
now it says E cant open/sdcard/o/download/jedi(bad)
Click to expand...
Click to collapse
Before you Odin back; are you still able to successfully flash any of the kernels you've downloaded? Also, if you downloaded any of the ROMs onto your computer, try browsing through the zips real quick on your computer.
lordcheeto03 said:
Before you Odin back; are you still able to successfully flash any of the kernels you've downloaded? Also, if you downloaded any of the ROMs onto your computer, try browsing through the zips real quick on your computer.
Click to expand...
Click to collapse
yes i can install kernels just fine, just not roms... it says it cant open the zip file, so weird.....i think i need to odin completely back too
Luthien1 said:
yes i can install kernels just fine, just not roms... it says it cant open the zip file, so weird.....i think i need to odin completely back too
Click to expand...
Click to collapse
Slow down, re-group, you are NOT going to brick...
First off, lets try some things, my first would be try a different recovery, copy a rom you want to the internal sdcard, then try. Bet it works.
I had a issue like this also, day 2 of my g4, pull the battery for 5-10 min, it seems the recovery gets confused and it will error.
another item to try...check to make sure the md5 file size is correct. common mistake, people for get to do a check.
try these, if you have the same issues, odin back to stock and start over.
Good luck. Your welcome.
lordcheeto03 said:
I may be overboard with my suggestion, but it wouldn't hurt to Odin back to 100% stock and restart your journey.
Click to expand...
Click to collapse
Probably this...and a formatting of the internal storage couldn't hurt either to make sure everything is cleared out.
Hey I had same problem. Download through Firefox not reg browser. And for infamous use the last download link
Goomanger gave me 3 bad downloads. To test this theory try and open the zip through a file manager, it probably won't let you because of bad download.. Happened to me 4 times but stopped using stock browser to download those files and has been working ever since
Sent from my SGH-M919 using XDA Premium HD app
---------- Post added at 10:54 AM ---------- Previous post was at 10:50 AM ----------
Also if you can't flash most things from more than 1 recovery still(happened to me when first got my gs4) I did Odin again but used 2.5.0.2 twrp and everything fixed as well. I recently was having the problem you have now and my first suggestion fixed it
Sent from my SGH-M919 using XDA Premium HD app
so, thank you everyone for your replys in this matter. I did odin back to stock and guess what, i got stuck at the splash screen for t mobile. This never happened before with odin, it always worked 100 percent, this is the first time i odined back to stock and it broke my phone, so weird. So, im going to try again. I wil def use firefox next time, and twrp you said the latest is having problems?
Luthien1 said:
so, thank you everyone for your replys in this matter. I did odin back to stock and guess what, i got stuck at the splash screen for t mobile. This never happened before with odin, it always worked 100 percent, this is the first time i odined back to stock and it broke my phone, so weird. So, im going to try again. I wil def use firefox next time, and twrp you said the latest is having problems?
Click to expand...
Click to collapse
Might want to thank people for the effort...there is a thanks button
get into recovery now, and do a factory reset, flash the correct kernel for your device, it will boot.
T989 without any SD card in it, the one I had died apparently new one on order. Went to flash the latest PA rom but kept getting error 7 using CWM. I updated my recovery to the latest TWRP and still will not flash. I tried updating to the newest radio UVMC6, but that wont flash. I am currently on CM10.1 nightly. My process for flashing is recovery, superwipe, flash, which is when the flash errors out and I re wipe and then I can flash my CM10 back on. So I can flash CM10 all day long but nothing else. I searched on here and found that the ATT version of this phone has this problem and you have to flash an AOKP and then flash whatever you want, other phones with similar problems say use ODIN and flash stock and then go from there. I am just looking for any advice on this situation. I could not find anything specific enough in my search to help me and I am hoping someone here can. Thanks in advance.
Note: I have also tried flashing CM10.1 RC5 and has the same problems.
moebawlz said:
T989 without any SD card in it, the one I had died apparently new one on order. Went to flash the latest PA rom but kept getting error 7 using CWM. I updated my recovery to the latest TWRP and still will not flash. I tried updating to the newest radio UVMC6, but that wont flash. I am currently on CM10.1 nightly. My process for flashing is recovery, superwipe, flash, which is when the flash errors out and I re wipe and then I can flash my CM10 back on. So I can flash CM10 all day long but nothing else. I searched on here and found that the ATT version of this phone has this problem and you have to flash an AOKP and then flash whatever you want, other phones with similar problems say use ODIN and flash stock and then go from there. I am just looking for any advice on this situation. I could not find anything specific enough in my search to help me and I am hoping someone here can. Thanks in advance.
Note: I have also tried flashing CM10.1 RC5 and has the same problems.
Click to expand...
Click to collapse
For onw those superwipe scripts are not needed with twrp, u might be getting the error from that, are u trying to flash from internal SD card since ur external died? That might cause it but I don't think so, I would suggest trying a manual wipe of all partitions, data, system, cache, dalvik, 2x , then flash, if that doesn't work try using Odin, go back to stock and start over, that should fix it definetly
Sent from my SGH-T989 using xda premium
soupysoup said:
For onw those superwipe scripts are not needed with twrp, u might be getting the error from that, are u trying to flash from internal SD card since ur external died? That might cause it but I don't think so, I would suggest trying a manual wipe of all partitions, data, system, cache, dalvik, 2x , then flash, if that doesn't work try using Odin, go back to stock and start over, that should fix it definetly
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Thank you... I wasnt sure about superwipe on TWRP since I just put it on and came from CWM. I am trying to flash from the internal card and the new external card will be at my doorstep tomorrow so I will drop that in as well. I will drop back in once I get all this done and hopefully all goes well.
Again thanks.
moebawlz said:
Thank you... I wasnt sure about superwipe on TWRP since I just put it on and came from CWM. I am trying to flash from the internal card and the new external card will be at my doorstep tomorrow so I will drop that in as well. I will drop back in once I get all this done and hopefully all goes well.
Again thanks.
Click to expand...
Click to collapse
Good glad I can help, let me know how it all goes, now I'm interested lol
Sent from my SAMSUNG-SGH-T989 using xda premium
Ok so I got my new SD card. Tossed that in, just figured I would try flashing from the external, no luck there. Same issues.
Odin back to stock using this tutorial http://forum.xda-developers.com/showthread.php?t=1513359&page=3
Used http://forum.xda-developers.com/showthread.php?t=2195283 this to regain root.
Got CWM back on but now I cannot flash SuperUser
When I go to flash Superuser it says
Mounting System
Deleting System:bin/su...
Deleting System:xbin/su
Extracting files to SYSTEM
Setting SYSTEM:bin/su permissions to 06755...
Creating SYSTEM:xbin/su symbolic link...
E: Error in /emmc/Superuser-3.0.7-efghi-signed.zip
(Status 0)
Installation aborted
So on the plus side I didn't brick the phone... downside now I am back to Gingerbread and currently stuck here...
Possibly a bad zip file?
Any ideas on this?
Quick update... I am a moron... Did not realize that root is kept with this restore... Got Superuser from market and am good to go.
Installing TWRP now and will have an update on the flash soon.
OK... the fun seems to have just begun
I cannot install TWRP from GooManager. No clue why, looking on here and I found //techerrata.com/browse/twrp2/hercules (cant link too new of a member)
So as it seems I can download the .img and GooManager should see it and if that doesnt happen I can install it through the terminal with these commands
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
OR flash it with ODIN... Which I would assume I get the .tar file and follow the same process as putting the recovery files in?
Aside from TWRP being an issue, I tried installing the PA rom with CWM and I got this:
Installing update
set_perm:some changes failed
E:Error in /sdcard/pa_hercule...zip
(Status 7)
Installation aborted
The same error I had in the first place
moebawlz said:
OK... the fun seems to have just begun
I cannot install TWRP from GooManager. No clue why, looking on here and I found //techerrata.com/browse/twrp2/hercules (cant link too new of a member)
So as it seems I can download the .img and GooManager should see it and if that doesnt happen I can install it through the terminal with these commands
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
OR flash it with ODIN... Which I would assume I get the .tar file and follow the same process as putting the recovery files in?
Aside from TWRP being an issue, I tried installing the PA rom with CWM and I got this:
Installing update
set_perm:some changes failed
E:Error in /sdcard/pa_hercule...zip
(Status 7)
Installation aborted
The same error I had in the first place
Click to expand...
Click to collapse
I'm not sure what your overall problem is, but if you are going to install TWRP do not use Goo Manager or the img file. They have been messing up peoples phones. Odin the tar or try the zip from the TWRP thread.
meekrawb said:
I'm not sure what your overall problem is, but if you are going to install TWRP do not use Goo Manager or the img file. They have been messing up peoples phones. Odin the tar or try the zip from the TWRP thread.
Click to expand...
Click to collapse
Well that could be a problem... I just got GooManager to do what I wanted it to do before I saw this message. If I overwrite it with the tar will that be ok or am I better off starting this process over and Odin back to factory stock again?
Along with that after I got TWRP working through Goo Manager again I tried flashing PA again and I had the same error as I did in the first place.
Maybe my phone just hates anything but the nightly I had before...
moebawlz said:
Well that could be a problem... I just got GooManager to do what I wanted it to do before I saw this message. If I overwrite it with the tar will that be ok or am I better off starting this process over and Odin back to factory stock again?
Click to expand...
Click to collapse
If you can boot into TWRP, then they must have fixed the Goo problem.
It seems like you have tried most everything. Maybe you should Odin back to stock. If you are comfortable doing it, that is.
i went to flash with goo last night and it bricked the phone kind of, i had to ODIN and reflash the CWM again and bam the phone rebooted no problem
meekrawb said:
If you can boot into TWRP, then they must have fixed the Goo problem.
It seems like you have tried most everything. Maybe you should Odin back to stock. If you are comfortable doing it, that is.
Click to expand...
Click to collapse
I did Odin back to stock before. I am still on stock gingerbread right now with root access and am getting the errors I have been. I followed the tutorials in the sticky thread that I posted before that got me back to stock.
Within TWRP I tried installing the newest Cyanogen Mod and got
E:Error executing updater binary in zip
Error flashing zip
When I try installing the PA rom I get the same error
Any thoughts? Would going back to stock through Odin and doing this again potentially fix it? or is that a shot in the dark?
Lucky for me I kept a backup saved on my PC from before I did anything here. So I am back to the CM 10.1 Nightly I started on for the time being.
Is there any other method of flashing a rom that I might be able to try?
moebawlz said:
I did Odin back to stock before. I am still on stock gingerbread right now with root access and am getting the errors I have been. I followed the tutorials in the sticky thread that I posted before that got me back to stock.
Within TWRP I tried installing the newest Cyanogen Mod and got
E:Error executing updater binary in zip
Error flashing zip
When I try installing the PA rom I get the same error
Any thoughts? Would going back to stock through Odin and doing this again potentially fix it? or is that a shot in the dark?
Click to expand...
Click to collapse
It would be a shot in the dark. I did a Google search for your error and a couple of people said they were able to fix it by using TWRP 2.3. That was for different phones though. Maybe try that before going stock.
I am by no means a pro at this and am still learning as I go. Just to make sure of what I am doing, can I Odin TWRP 2.3? I also found this
http://forum.xda-developers.com/showthread.php?t=1639673
or
http://forum.xda-developers.com/showthread.php?t=1658418
Just a thought here... I keep gettin emmc errors... I was reading about upgrading and downgrading TWRP through the Terminal Emulator and it said use emmc or sdcard depending on what the phone reads it as.
When I first got the phone i recall seeing emmc when i would go into any file browser. Now it just says sdcard0 (internal) & sdcard1 (external)
So how can I get recovery to stop looking for emmc and start looking for sdcard0?
Unless I am way off in left field here with this.
moebawlz said:
I am by no means a pro at this and am still learning as I go. Just to make sure of what I am doing, can I Odin TWRP 2.3?
Click to expand...
Click to collapse
Yes, use Odin and the 2.3.3.0 tar from the techerrata website. I like using the Odin method because I have never had a problem upgrading recovery that way. I don't know about the emmc errors because I have only used the dd method like twice.
Edit: Maybe your internal memory is corrupted? I'm not sure how to test for that though.
moebawlz said:
Well that could be a problem... I just got GooManager to do what I wanted it to do before I saw this message. If I overwrite it with the tar will that be ok or am I better off starting this process over and Odin back to factory stock again?
Along with that after I got TWRP working through Goo Manager again I tried flashing PA again and I had the same error as I did in the first place.
Maybe my phone just hates anything but the nightly I had before...
Click to expand...
Click to collapse
I think u must be getting bad DL then because none of that sounds right lol, if u got twrp to load into your device and all is working fine then the only other option is a bad DL, try checking the DL with a root browser or something to see the size of the file, status 7 errors are from the zip, usually bad install script in the ROM, which could be caused by a bad DL, check the DL size and let me know
Sent from my SGH-T989 using xda premium
went back to 2.3.3 and still having the same error.
Is there a way to correct any possible errors in my internal memory?
moebawlz said:
went back to 2.3.3 and still having the same error.
Is there a way to correct any possible errors in my internal memory?
Click to expand...
Click to collapse
If the DL is good, I don't know what else to tell u that is very strange indeed, but interesting too, I've never not been able to install at all, I'm curious..
Sent from my SGH-T989 using xda premium