Ok so it's been a while since I've done any new ROMs or anything, mainly did things on my GS2 but now going with the GS3 and have been for a little bit now. It's all rooted and everything fine, but I decided to finally install the CM10 ROM and am having a difficult time. I finally got it to install and boot up (had a slight issue with the boot loop which I got passed) but now my home screen says Sprint on the bottom. Maybe I downloaded the wrong CM10 zip? Or maybe they're all like this but I didn't think it was. On to the bigger problem, no mobile connection. I'm able to restore to my backed up status so that's what I'm going with for now but I'd really like to get this working. Any suggestions? Have I supplied enough info. Any help would be greatly appreciated, thanks to anyone that can give me some direction here.
You flashed the wrong zip.
for AT&T you need d2att http://get.cm/?device=d2att
If you need a different carrier then ATT try checking the CM10 thread http://forum.xda-developers.com/showthread.php?t=1778270
Randomacts said:
You flashed the wrong zip.
for AT&T you need d2att http://get.cm/?device=d2att
If you need a different carrier then ATT try checking the CM10 thread http://forum.xda-developers.com/showthread.php?t=1778270
Click to expand...
Click to collapse
Thank you for that! Will that solve the network problem too? Seems like something like that would solve my problem all together. Anything else I should know?
Imnice777 said:
Thank you for that! Will that solve the network problem too? Seems like something like that would solve my problem all together. Anything else I should know?
Click to expand...
Click to collapse
yeah it should if not go back to complete stock and try again.
If none of that works check in settings, about phone and make sure your imei number is still intact (not showing zeros).
Ok so my IMEI is still intact but that zip for AT&T didn't work, I got an error. I cleared cache and user data and chose it from my internal memory, not sure what the issue is except maybe my CWM is outdated? Wasn't sure if it'd be a problem but maybe that's it. Any other suggestions?
Sent from my SAMSUNG-SGH-I747 using xda premium
Might be an APN issue. Try adding the APN for your carrier and see if your data works. What error are you getting when you try to flash the at&t version?
jethro650 said:
Might be an APN issue. Try adding the APN for your carrier and see if your data works. What error are you getting when you try to flash the at&t version?
Click to expand...
Click to collapse
The error reads "asset failed: getprop("ro.product.device") == "d2att" l l getprop(("ro.build.product") == "d2att" E:error in /emmc/cm-10-20121024-NIGHTLY-d2att (1).zip (Status 7) Installation aborted."
Update your recovery.
Sent from my iPad 4
Update CWM recovery to latest version.
And you can get a newer version here. http://forum.xda-developers.com/showthread.php?p=28611956
Official ClockworkMod Recovery Images for AT&T
Ok so I figured it out and fixed it! All I had to do was update my CWM with ROM Manager like I thought I might have to do. I saw another thread with a similar issue, too so I guess this is somewhat common. Gotta update everything when it comes to this stuff. Thanks for all the responses though, I appreciate it.
Somehow I didn't see the replies telling me to update CWM before I.posted that I figured it out. Either way, I'm currently running it and all is awesome so far. If anyone has suggestions on specific things to do now?
Sent from my SAMSUNG-SGH-I747 using xda premium
please help
Hi there, i've been having issues trying to install cm10 since last week and it's been frustrating. After doing hours of search I found a thread that says I should reinstall cwm recovery. I've tried doing this with rom manager from google play but it didn't work. It says, make sure you have stable internet connection and that your sd card is installed and working. Now, do have to Odin again to flash the newest clockworkmod recovery. If not how do I do then cuz I keep getting aborted and every time have to restart system and set it up all over. by the way my phone is a galaxy s3 i747 android 4.0.4 rooted cwm 5.5.0.4. thanks
androidehca said:
Hi there, i've been having issues trying to install cm10 since last week and it's been frustrating. After doing hours of search I found a thread that says I should reinstall cwm recovery. I've tried doing this with rom manager from google play but it didn't work. It says, make sure you have stable internet connection and that your sd card is installed and working. Now, do have to Odin again to flash the newest clockworkmod recovery. If not how do I do then cuz I keep getting aborted and every time have to restart system and set it up all over. by the way my phone is a galaxy s3 i747 android 4.0.4 rooted cwm 5.5.0.4. thanks
Click to expand...
Click to collapse
Download this cwm 6.0.1.4 http://db.tt/te3vInsu , reboot into recovery and flash it, reboot recovery and flash cm10.
tonymtl said:
Download this cwm 6.0.1.4 http://db.tt/te3vInsu , reboot into recovery and flash it, reboot recovery and flash cm10.
Click to expand...
Click to collapse
that's not the problem, I already have the file. it's kind of my question, I keep getting aborted from the process of flashing. no errors, only aborted
androidehca said:
that's not the problem, I already have the file. it's kind of my question, I keep getting aborted from the process of flashing. no errors, only aborted
Click to expand...
Click to collapse
If that's the case I'd probably completely go back to stock and root with the updated CWM. Kind of a pain but might be your best bet. Updating for me was the solution. Try that and let me know how it goes.
Sent from my SAMSUNG-SGH-I747 using xda premium
Related
i didnt see anyone having this problem but got my gn and unlocked it yest, i came fr evo3d and we used to wiping everything n cache n dalvik so i tried to flash my first rom and im getting error " error in /sdcard/toro_aokp_b8.zip(status7) installation aborted assert failed:getprop(ro.product.device==toroII
i thought it was that rom but i tried flashing another rom and getting same message , if someone can help i appreciate it, i came fr the evo3d left sprint after 11yrs and woow what a difference in network, awesome network but im spoiled with rooting my ogevo n evo3d lol i love this phone hope i can fix this issue
Could you let us know what roms you've tried and the exact process you used please. Also are you using CWM?
RTContent said:
Could you let us know what roms you've tried and the exact process you used please. Also are you using CWM?
Click to expand...
Click to collapse
k first rom i tried AOSP 4.0.3ANDROID OPEN KANG PROJECT-TORO BUILD8 so i wiped data factory reset and cache n dalvik and flashed the rom, it looks like it starts to flash but aborts with the message above, then i restored my nan backup rebooted and went back to cwm to reflash the second time around i only wipe data factory reset cuz thats what the op says to do on his thread so i only wipe data factory n flash the rom still same error, so i went to try another rom GUMMYNEX 0.2.3 and i did the same process with both im following the steps their stating in the op in have cwm
From what the error sounds like is that it doesn't think you have the correct device. You have a CDMA phone and not a GSM?
RTContent said:
From what the error sounds like is that it doesn't think you have the correct device. You have a CDMA phone and not a GSM?
Click to expand...
Click to collapse
ui
yup, i got it fr verizon cdma, im starting to stress man, ive been so used the rooting world n having custom roms i dont know how i could do without it lol, i hope i can get this issue resolve
Flip35 said:
ui
yup, i got it fr verizon cdma, im starting to stress man, ive been so used the rooting world n having custom roms i dont know how i could do without it lol, i hope i can get this issue resolve
Click to expand...
Click to collapse
sure you are using the lastest CWM???
sure you are rooted??
did you try downloading the files from another puter??
i think i might know what the problem is my cwm says 5.5.0.2 and im looking here at somebody posted in the development section for a cdma cwm and it says 5.5.0.4 could that be the problem? if so how do i redo my recovery, follow the same steps i did my first one, i downloaded and extracted the files to my c drive and opened cmd and typed the commands, can i do that again while having already cwm to flash the new cwm on top of the old one? if thats the problem
Download rom manager. Then you can flash it while your booted in android.
RTContent said:
Download rom manager. Then you can flash it while your booted in android.
Click to expand...
Click to collapse
how ive never flashed cwm using rom manager, u meand download the file of cwm5.5.0.4 putting in the root like i do any rom and go into rom manager and install?
No just download the app Rom Manager. It will download the latest version and flash it with a single click within this app!
RTContent said:
Download rom manager. Then you can flash it while your booted in android.
Click to expand...
Click to collapse
wooooord, aight RTcontent good looking out, i guess when u said it looks like it sound it was reading my phone wrong was right, i had a gms cwm, thanx man used rom manager and since i put the new cwm in my root of sdcard when i press install cwm it automatically update it without even booting into recovery but just finished intalling a rom and IT WORKED!!!! UR DA MAN im excited thanx
Hi guys. I have a huge problem. Few minutes ago I tried to install CyanogenMod 7.2-GIO-KANG by use CWM v5.0.2.7. Everything appeared to be ok, but when phone reboot I just can see white word ANDROID on a black background and nothing more. Phone just stop on this screen. Is there any resolution for my problem? I modded lot of phones, this is my first crash. Thx for every advice. Bye
Same issue. Is there a way to restore to stock firmware without odin? Such as from the recovery console?
If before you had an official rom, you must use the ext4 formatter. I think you'll find it in the thread! Hope to be useful
Sent from CM9 Gio with the XDA app v.v
i've noticed sometimes is does take a minute or two to get past that screen.
tooviral
Now I have a new problem, it no longer allows me to boot the device, it displays an image of a phone connected to a pc. Does this mean I have to flash in odin?
gruntlord6 said:
Now I have a new problem, it no longer allows me to boot the device, it displays an image of a phone connected to a pc. Does this mean I have to flash in odin?
Click to expand...
Click to collapse
Happened to me once, I just found a stock rom and flashed with odin. Since I've put cwm recovery I've backed up and haven't had a prob since
tooviral
tooviral said:
Happened to me once, I just found a stock rom and flashed with odin. Since I've put cwm recovery I've backed up and haven't had a prob since
tooviral
Click to expand...
Click to collapse
Well as you can tell I am new to android, I tried using odin with a stock rom I found on this site, but I keep getting the error:"an unnamed file was not found"
gruntlord6 said:
Well as you can tell I am new to android, I tried using odin with a stock rom I found on this site, but I keep getting the error:"an unnamed file was not found"
Click to expand...
Click to collapse
Have you downloaded gio_v1.0.ops?
That may cause the "an unnamed file was not found" problem
all you need to do is "wipe data/factory reset" ... i didn't use any ext4-formatter and it works well..
matt_galaxygio said:
Have you downloaded gio_v1.0.ops?
That may cause the "an unnamed file was not found" problem
Click to expand...
Click to collapse
That helps, but now it tells me "cannot open the usb serial port. code: 2"
Edit: Never mind, found out it was kies conflicting. Thanks for the help!
Ok, I used odin and newest stock rom. Now the phone is working fine, like new Thx for all advices guys, that was really helpful. Cya
I have this issue too.
Im new to android but I followed the thread, I:
Root
install CWM, then nandroid backup
flash CM7 in CWM
I downloaded the CM7 KANG file and tried several times, thinking file might be corrupt. Same problem.
Unfortunately my backup didn't work, so I'm ordering a Jig to fix my phone.
But I'd like to know what went wrong.
I didnt reformat my SD card with 4ext though, should I have?
Thanks
tioammar said:
all you need to do is "wipe data/factory reset" ... i didn't use any ext4-formatter and it works well..
Click to expand...
Click to collapse
I tried this and it didnt work for me
Hello,
I got this problem trying to install RC4 and RC5 as well, but now still getting it with the fresh CM10.1.0 update. I am running CWM 6.0.3.1 and tried updating CM but got the status 7 error due to the asserts. I checked md5 just to be sure and made sure I have proper d2att file for my phone. I went in and manually removed the 2 assert lines in the beginning of the updater-script file and zipped back up and tried to flash again but now I just get "installation aborted..." right after "installing update..." with no explanation or error at all.
I tried searching, got nothing, anybody seen this before?
Thanks,
J
madtorq said:
Hello,
I got this problem trying to install RC4 and RC5 as well, but now still getting it with the fresh CM10.1.0 update. I am running CWM 6.0.3.1 and tried updating CM but got the status 7 error due to the asserts. I checked md5 just to be sure and made sure I have proper d2att file for my phone. I went in and manually removed the 2 assert lines in the beginning of the updater-script file and zipped back up and tried to flash again but now I just get "installation aborted..." right after "installing update..." with no explanation or error at all.
I tried searching, got nothing, anybody seen this before?
Thanks,
J
Click to expand...
Click to collapse
Are you on a Canadian carrier?
Sent from my SGH-I747 using xda app-developers app
Nope, southern california ATT.
I edited using vim and did it cleanly, no chance of a carriage return or something stupid contributing to this.
Are you on the proper bootloader?
mrhaley30705 said:
Are you on the proper bootloader?
Click to expand...
Click to collapse
I have tried running the zip manually from recovery mode in CWM, tried installing it from Rom Manager where it reboots and automatically selects it and I have tried directly from the CM10 update button within the About Phone settings menu.
Is that what you are referring to?
No. Have you installed the jelly bean bootloader? If not, you will need to update them before cm, or any aosp based Rom, will install.
Also, you need the latest modem too.
mrhaley30705 said:
No. Have you installed the jelly bean bootloader? If not, you will need to update them before cm, or any aosp based Rom, will install.
Also, you need the latest modem too.
Click to expand...
Click to collapse
I do not follow, what is the jelly bean bootloader? I understood it to be an alternative to CWM? Why have I been able to flash every update for CM10 until this?
Link to this jelly bean bootloader update?
Bootloaders are not a type of recovery. Perhaps you should read through this:
http://forum.xda-developers.com/showthread.php?t=1903437
Then this:
http://forum.xda-developers.com/showthread.php?t=2292957
madtorq said:
Hello,
I got this problem trying to install RC4 and RC5 as well, but now still getting it with the fresh CM10.1.0 update. I am running CWM 6.0.3.1 and tried updating CM but got the status 7 error due to the asserts. I checked md5 just to be sure and made sure I have proper d2att file for my phone. I went in and manually removed the 2 assert lines in the beginning of the updater-script file and zipped back up and tried to flash again but now I just get "installation aborted..." right after "installing update..." with no explanation or error at all.
I tried searching, got nothing, anybody seen this before?
Thanks,
J
Click to expand...
Click to collapse
I have the same problem. Guess I'll never get 10.1, because it looks like you have to put a new bootloader on it, not sure why, and it risks a hard brick. It doesn't make any sense to require a new bootloader, seeing as I already have cyanogenmod 10, but the devs chose that for their reasons. I really want the camera in 4.2.
Well, if you've flashed any of the stock ROMS here, rooted or not rooted, you've flashed bootloaders.
well I guess I am confused. I am currently running cm-10.1-20130411-EXPERIMENTAL-d2att-M3.zip with the same bootloader I flashed with Odin back when I got the phone in september 2012. My roomate got the same phone except on sprint and we flashed his with the appropriate CM10.1 experimental release for the sprint phone. Since then we both have been updating via the built in CM updater and he has been able to go to the new stable CM 10.1.0 release today and has not flashed any new boot loader or anything, just updated CWM like I did.
So my question to you mrhaley30705, which no amount of searching or reading links has helped me thus far, is this something specific to the ATT version of the Galaxy S3? I do not understand what changed and why he can do it and I cannot.
More importantly, will flashing the newer boot loader you suggested require a wipe of everything? The only post actually referencing this for my phone is http://forum.xda-developers.com/showpost.php?p=41503727 and it is vague to say the least.
Your answers are much appreciated.
Here is the screen shot of what was posted on g+ by cm. I would say he is on the new bootloader. If you check the second link I posted above, there's a way to tell which bootloader you and your buddy have.
It doesn't wipe anything. You'll probably never notice the difference, with the exception of being able to run aosp based ROMS
thank you, that is informative, but still leaves me confused since I am running 4.2.2 (although the build is before that May release) and I am currently running I747UCLH9.
Checking my roomate's phone he is running XXXXXXLJ7 so either he started with a newer one or something. I guess that clears it up. Also, this thread was very helpful incase anybody searches and stumbles on my posts: http://forum.cyanogenmod.com/topic/73407-how-to-update-bootloader-and-do-i-need-to-do-this/
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
Hello,
First off I'd like to say I'm sorry. I know this has probably been covered countless times, but I have been trying to fix this for the past 5 hours and I just can't get it, so I have turned to you.
I have a Galaxy S3 of course and I'm trying to flash a custom rom. Here is the process I use.
#1: I flash the stock rom via Odin to get the phone to the state just as it came out of the box (JB 4.1.1)
#2: I root via Unified ToolKit which uses Odin and then adb to push SU and related files to my phone.
#3: I download ROM manager and flash the latest CWM recovery (6.0.3.7 if i remember right)
#4: I place my ROM in .zip format on my internal SD card. I got CM 10.3.1 here: http://get.cm/?device=d2att&type=stable
#5: I wipe data/factory reset, wipe cache, wipe delvik cache
#6: I attempt to install zip from SD card
it will sit for a little bit and then give me this
installing update...
set_perm: some change failed
E: error in /sdcard/ROOT/CM 10.1.3
(status 7)
Installation aborted
So what the hell am I doing wrong? The same thing happens when I try to flash LiquidSmooth 2.9.
Thanks for any advice. Its just really hard to wade through all the outdate info on this type of stuff online.
Hi. Ive never run CM. So Im not sure but maybe you need to update your boot loader to flash that ROM version?
Only other thing I could say to try..which may make no difference is put the zip on your external
jasvncnt1 said:
Hi. Ive never run CM. So Im not sure but maybe you need to update your boot loader to flash that ROM version?
Only other thing I could say to try..which may make no difference is put the zip on your external
Click to expand...
Click to collapse
How do I update my bootloader? I've never had to do that before, but I'll do some googling.
I've tried flashing from both the internal and External SD cards already, no difference.
Jeoster said:
How do I update my bootloader? I've never had to do that before, but I'll do some googling.
I've tried flashing from both the internal and External SD cards already, no difference.
Click to expand...
Click to collapse
Try checking out this thread...
http://forum.xda-developers.com/showthread.php?t=2321310
Again, im not positive if you need to for that ROM. Its just something that may be an issue.
Actually looks like the first part of that thread I linked talks about updating your bootloader for C
Jeoster said:
Hello,
First off I'd like to say I'm sorry. I know this has probably been covered countless times, but I have been trying to fix this for the past 5 hours and I just can't get it, so I have turned to you.
I have a Galaxy S3 of course and I'm trying to flash a custom rom. Here is the process I use.
#1: I flash the stock rom via Odin to get the phone to the state just as it came out of the box (JB 4.1.1)
#2: I root via Unified ToolKit which uses Odin and then adb to push SU and related files to my phone.
#3: I download ROM manager and flash the latest CWM recovery (6.0.3.7 if i remember right)
#4: I place my ROM in .zip format on my internal SD card. I got CM 10.3.1 here: http://get.cm/?device=d2att&type=stable
#5: I wipe data/factory reset, wipe cache, wipe delvik cache
#6: I attempt to install zip from SD card
it will sit for a little bit and then give me this
installing update...
set_perm: some change failed
E: error in /sdcard/ROOT/CM 10.1.3
(status 7)
Installation aborted
So what the hell am I doing wrong? The same thing happens when I try to flash LiquidSmooth 2.9.
Thanks for any advice. Its just really hard to wade through all the outdate info on this type of stuff online.
Click to expand...
Click to collapse
Try using goo manager on play to install twrp then download cm/gapps through goo manager.
jasvncnt1 said:
Try checking out this thread...
http://forum.xda-developers.com/showthread.php?t=2321310
Again, im not positive if you need to for that ROM. Its just something that may be an issue.
Actually looks like the first part of that thread I linked talks about updating your bootloader for C
Click to expand...
Click to collapse
Thank you! This looks very plausible. I'll give it a go. I looked into updating the bootloader yesterday, but I could not find much info on it.
updating the bootloader did not work for me. I still get status 7. I don't know if its just me, but I think it did more stuff on screen before giving me the status 7. I tried flashing LiquidSmooth 2.9 this time. I'm going to start over and try flashing CM 10.1.3.
ok so i was able to flash and run CM 10.0.0 with no problems. Still havent figured out my status 7 error.
Doing more research i see people sometimes simply delete the compatibility check that causes the status 7 error. im scared to do that. is it a bad idea?
Jeoster said:
ok so i was able to flash and run CM 10.0.0 with no problems. Still havent figured out my status 7 error.
Doing more research i see people sometimes simply delete the compatibility check that causes the status 7 error. im scared to do that. is it a bad idea?
Click to expand...
Click to collapse
Sorry the boot loader didn't help. At least you know how to do it now. I'm not really sure about your other question. Hopefully someone else will chime in.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
jasvncnt1 said:
Sorry the boot loader didn't help. At least you know how to do it now. I'm not really sure about your other question. Hopefully someone else will chime in.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
I really appreciate the time anyone takes to even try to help, so thank you. Its no big deal. CM10.0.0 is working fine, but I wish I could figure out how to run the newer versions.
OK well turns out I'm getting the phone warrantied and they're upgrading me to an S4. Time to flash back to stock, lol. My S3 experience has been a good one.
Jeoster said:
OK well turns out I'm getting the phone warrantied and they're upgrading me to an S4. Time to flash back to stock, lol. My S3 experience has been a good one.
Click to expand...
Click to collapse
How'd you pull the upgrade off
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
jasvncnt1 said:
How'd you pull the upgrade off
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Well its a really long story, but I'll try to shorten it. My screen is cracked on my S3 and i have accidental damage warranty on it through AT&T, but the deductible is $200. So I only wanted to warranty it if they could upgrade me to the S4, and I called them back today and they were out of the S3 so they are giving me an S4.
Cool beans, huh?
The real story is much longer and complicated but thats the jist of it.