[Q] CM10 flashing, first time question here - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

Hi, so I'm trying to make this quick so that i can install CM10 tonight...
so I rooted my phone tonight, did everything right and stuff, but I went to go download the CM10 nightly build for my phone which is the Rogers (Canadian version). So I download the d2att version, did a backup, wiped everything and I tried installing it using CWM-Based recovery v5.5.0.4. But when I tried install it gave me status 7 aborted. I installed cwm using odin3 v1.85, what am I doing wrong, am I trying to install the wrong version? Sorry if this is a noob question but I'm new to this stuff :/
thanks for any help

Can anyone explain to me how I can update CWM? I downloaded the latest img from their website, but idk how to install it...I'm really confused...and I really need help :crying:

Go look at QBKing77 videos on YouTube or QBKing77.com he has the best videos in my opinion and installing CM10 and CWM. I am on CM10.1 without any problems.

hmm, did you use the v5 recovery? Did it work, because the version i had was cwm 5.5 and I couldn't update because of system 7 error, which is because the CWM version was too old.
If possible, could you link me the one you used?

Ok..so now I installed TWRP and I tried flashing CM10 it still didnt work and gave me status 7 error and it says:
assert failed: getpro ("ro.product.device")
E: Error in /sdcard/cm- 10.....d2att.zip
Is this because with goomanager i installed it for the d2can version and now I can't install the d2att even though thats the only version i can use? goomanager only lets me get d2can...and when I try to install the never cwm recover img using android terminal it keeps giving me No such file or directory.
Can anybody help me with this...

PhoenixBlitz said:
Ok..so now I installed TWRP and I tried flashing CM10 it still didnt work and gave me status 7 error and it says:
assert failed: getpro ("ro.product.device")
E: Error in /sdcard/cm- 10.....d2att.zip
Is this because with goomanager i installed it for the d2can version and now I can't install the d2att even though thats the only version i can use? goomanager only lets me get d2can...and when I try to install the never cwm recover img using android terminal it keeps giving me No such file or directory.
Can anybody help me with this...
Click to expand...
Click to collapse
have you tried flashing another ROM, like an-aosp or aokp-based one? If you followed their instructions, it may help you determine whether it was a bad download or something s more specific to your device. just throwing this one out there....

captican said:
have you tried flashing another ROM, like an-aosp or aokp-based one? If you followed their instructions, it may help you determine whether it was a bad download or something s more specific to your device. just throwing this one out there....
Click to expand...
Click to collapse
oh...hahaha
I just flashed AOKP and everything worked great! Thanks for that little suggestion! Custom ROMs are now my favorite!

PhoenixBlitz said:
oh...hahaha
I just flashed AOKP and everything worked great! Thanks for that little suggestion! Custom ROMs are now my favorite!
Click to expand...
Click to collapse
If you want to flash a CM ROM you will need to be on the most current d2att recovery for either CWR or TWRP. If you were getting a status 7 error, I'm going to assume that you have a d2can phone.. make sure you have a d2att recovery and you'll be able to flash anything. ROM Manager will let you install CWR or Goo Manager will let you install TWRP (which is what I use).

BAM1789 said:
If you want to flash a CM ROM you will need to be on the most current d2att recovery for either CWR or TWRP. If you were getting a status 7 error, I'm going to assume that you have a d2can phone.. make sure you have a d2att recovery and you'll be able to flash anything. ROM Manager will let you install CWR or Goo Manager will let you install TWRP (which is what I use).
Click to expand...
Click to collapse
Yes, I highly recommend TWRP.
Sent from my SPH-D710 using xda premium

HeadBlader911 said:
Yes, I highly recommend TWRP.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I tried using TWRP but when I installed it through GooManager it installed the d2can version so I couldn't install CM10. Unless there is a way to manually select which TWRP version to install through GooManager, then I'm more or less stuck on CWM.
edit: Just got TWRP for d2att installed so now I can flash whatever I want, man TWRP seems a lot better than CWM!

Related

Cannot Install ANY cm/aosp/aokp Rom

hello all,
I'm having trouble understanding something with my SIII. I have a Canadian Rogers SIII currently running DJJOHNNYBLAZE's rom.
great rom, no problems at all!
But when I try to, I haven't been able to install any CM, AOKP or AOSP rom on my phone through TWRP or CWM recovery... only the stock based roms work when I install them..
is there something I'm missing? or doing rom? I'm quite familiar with the flashing process, I've done it a million times on my SIII and my previous Sony Xperia..
Any help, tips or direction to an answer is much appreciated
RoshanDoon said:
But when I try to, I haven't been able to install any CM, AOKP or AOSP rom on my phone through TWRP or CWM recovery... only the stock based roms work when I install them..
Click to expand...
Click to collapse
First question: what fails about the install process?
Second question: how did you install the recovery images?
Most of the time when I hear something like this on a Canadian S3, it's because of the different device code (d2can vs. d2att) of the Canadian model; the images you get through goomanager or ROM Manager or similar will see that you're trying to install a d2att ROM on a device it sees as a d2can, fails to get that the two are software-compatible, and aborts with a "status 7" error.
If that's the case, you can manually flash, say, the d2att TWRP image (look here for the image and instructions), which will happily flash d2att ROMs onto your device.
smelenchuk said:
First question: what fails about the install process?
Second question: how did you install the recovery images?
Most of the time when I hear something like this on a Canadian S3, it's because of the different device code (d2can vs. d2att) of the Canadian model; the images you get through goomanager or ROM Manager or similar will see that you're trying to install a d2att ROM on a device it sees as a d2can, fails to get that the two are software-compatible, and aborts with a "status 7" error.
If that's the case, you can manually flash, say, the d2att TWRP image (look here for the image and instructions), which will happily flash d2att ROMs onto your device.
Click to expand...
Click to collapse
thanks for the quick reply
to answer your first question: when i flash any of them, in recovery it just says "Failed" in red letters.. the funny part is I've installed a couple open source roms before and they worked (ie Liquid, Ktoonez AOKP rom), now i can't :S the ones i flashed were d2att, possibly my problem now, however, why did they work before?
to answer the second: i do a factory reset, wipe cache, flash rom, install gapps, wipe dalvik (as stated in most forums)
also, i've installed TWRP by installing GooManager on my phone and installing it from there, is that wrong? is it different than manually doing it with the command?
thanks again
RoshanDoon said:
i've installed TWRP by installing GooManager on my phone and installing it from there, is that wrong? is it different than manually doing it with the command?
Click to expand...
Click to collapse
Yes - that means you have the d2can TWRP image and not the d2att recovery image, which causes the problem I described. You will probably want to manually install the d2att image in its place.
smelenchuk said:
Yes - that means you have the d2can TWRP image and not the d2att recovery image, which causes the problem I described. You will probably want to manually install the d2att image in its place.
Click to expand...
Click to collapse
ahhhh... gracias!
will do that now then, thanks
I'm having a similar problem.
I've rooted my s3 i747m (virgin), and I have backed up using TWRP.
Attempting to install Cyanogen mod from a .zip on internal sdcard. In recovery mode I've gone in and tried to install from the zip, but I'm getting status 7. Any ideas?
ultrashaun said:
I've rooted my s3 i747m (virgin), and I have backed up using TWRP.
Attempting to install Cyanogen mod from a .zip on internal sdcard. In recovery mode I've gone in and tried to install from the zip, but I'm getting status 7. Any ideas?
Click to expand...
Click to collapse
Exactly the same problem, exactly the same cause; read the earlier posts in this thread for an idea of what to do.
smelenchuk said:
Exactly the same problem, exactly the same cause; read the earlier posts in this thread for an idea of what to do.
Click to expand...
Click to collapse
Again! You've done it sir. This worked exactly right. Thank you so much.

[Q] Nexus doesnt let me do anything

Hello
I have purchased a second hand Nexus. It is rooted and has got custom rom. Also Teamwinner or so is installed. When i boot into recovery to install some other rom it exits with error 7. Same when i try to update the teamwinner to the newest version.
Any idea what to try?
dosada said:
Hello
I have purchased a second hand Nexus. It is rooted and has got custom rom. Also Teamwinner or so is installed. When i boot into recovery to install some other rom it exits with error 7. Same when i try to update the teamwinner to the newest version.
Any idea what to try?
Click to expand...
Click to collapse
i remember seeing error 7 before on a rom i tried to flash.. i was using CWM so its not the recovery's fault. turns out there was a problem with the rom...
so find another rom to flash would be my answer for now.
The problem is that i get this error whatever i tried to flah. Even cwm or some other rom result in same error
dosada said:
The problem is that i get this error whatever i tried to flah. Even cwm or some other rom result in same error
Click to expand...
Click to collapse
What procedure are you using to flash? What file are you trying to flash and where did you get it from?
I start up the phone using volume down and power. Then in teamwinner i chose install zip and then the file
so far have tried, all downloaded from here or linked from here, those files
CWM-Touch-6.0.2.5-DJ
Hellybean-20130405-crespo
TWRP-2.4.4.0-DJ
jellyshot_crespo-v3.3
nothing works. all of them exist with error 7
dosada said:
I start up the phone using volume down and power. Then in teamwinner i chose install zip and then the file
so far have tried, all downloaded from here or linked from here, those files
CWM-Touch-6.0.2.5-DJ
Hellybean-20130405-crespo
TWRP-2.4.4.0-DJ
jellyshot_crespo-v3.3
nothing works. all of them exist with error 7
Click to expand...
Click to collapse
.....
This is the Galaxy Nexus forums, that firmware aka ROM is for crespo aka Nexus S
Sent from my Nexus
Fair enough about the roms, but why cant i even install cwm? This shows me just the error 7 too
I wouldn't be surprised if your recovery is either not for your device or not even a flash able zip.
dosada said:
Fair enough about the roms, but why cant i even install cwm? This shows me just the error 7 too
Click to expand...
Click to collapse
Where did you get that CWM? http://www.clockworkmod.com/rommanager? If so those are img files, for flashing from fastboot. But I have no idea what "DJ" is for. To flash from recovery it needs to be packaged in a flashable zip.
Or you can install CWM from the ROM Manager app. Or TWRP from GooManager.
quite frankly i wouldnt use CWM. The UI is annoying as hell, and it tends ot be a lot slower, at least from my own experience.
I recommand TWRP, http://www.teamw.in/project/twrp2/90 latest version here for maguro.
if you have adb set up, installing twrp is cake, simply open adb and type:
1) adb reboot bootloader
2) fastboot flash recovery TWRP.img <-----assuming you are in the directory of that img file you just downloaded, and TWRP is just the name of the img file, its usually attached with version, so i would rename it for easier access.
3) after you flashed it just boot into recovery and start flashing your new rom.
If all else fail.....use the toolkit and flash factory image for a fresh start, i havnt failed with factory image yet

[Q] Can't flash ROM Official CM 10.2

Hi,
I can't flash this ROM onto my N5100: [ROM][N5100]Official CM 10.2[JLS36I][11/18/13]
I have twrp 2.6.0 installed and everytime I try to install the zip it says error executing updater binary in zip and it fails.
Also tried this with other recovery, but always getting the same error.
I must be doing something fundamentally wrong, can anyone help me out?
Thanks for any hints.
Try the version of TWRP that I made here or one of civatos CWM recovery.
Cool, thanks, worked like a charm. :good:
nickdollahz said:
Try the version of TWRP that I made here or one of civatos CWM recovery.
Click to expand...
Click to collapse
Another solution
500e said:
Hi,
I can't flash this ROM onto my N5100: [ROM][N5100]Official CM 10.2[JLS36I][11/18/13]
I have twrp 2.6.0 installed and everytime I try to install the zip it says error executing updater binary in zip and it fails.
Also tried this with other recovery, but always getting the same error.
I must be doing something fundamentally wrong, can anyone help me out?
Thanks for any hints.
Click to expand...
Click to collapse
Here is another solution.

CWM Help!

I'm rooted on stock 4.1 but i didn't have a custom recovery so I flashed cwm rom manager. I was able to make a nandroid backup fine but when I tried rebooting in to the recovery, it would just take me to stock recovery. How do I fix this? Thanks, in advance!
Sent from my Nexus 7 using xda app-developers app
|| Acer || said:
I'm rooted on stock 4.1 but i didn't have a custom recovery so I flashed cwm rom manager. I was able to make a nandroid backup fine but when I tried rebooting in to the recovery, it would just take me to stock recovery. How do I fix this? Thanks, in advance!
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
For some phones, it seems Rom manager doesn't flash the recovery properly. Just like Goomanager, for me, will not flash TWRP at all. I prefer to flash it using MSkips Toolbox or ODIN by itself if you know how. If you use the toolbox, it will be an older version of CWM, but after you flash the older version and make sure it works by rebooting your phone into recovery, then you can flash the newest version of either CWM or TWRP in ZIP format HERE. ODIN can be tricky for some who've never used it before. The Toolbox automates this process for you.
joeyhdownsouth said:
For some phones, it seems Rom manager doesn't flash the recovery properly. Just like Goomanager, for me, will not flash TWRP at all. I prefer to flash it using MSkips Toolbox or ODIN by itself if you know how. If you use the toolbox, it will be an older version of CWM, but after you flash the older version and make sure it works by rebooting your phone into recovery, then you can flash the newest version of either CWM or TWRP in ZIP format HERE. ODIN can be tricky for some who've never used it before. The Toolbox automates this process for you.
Click to expand...
Click to collapse
Thanks for the help! I didn't know about goomanager until you mentioned it, and it happened to work perfectly for me so I don't have to go through all the trouble
|| Acer || said:
Thanks for the help! I didn't know about goomanager until you mentioned it, and it happened to work perfectly for me so I don't have to go through all the trouble
Click to expand...
Click to collapse
If you prefer CWM, give Philz Touch a try, it is a very advanced version of CWM, and works great for a lot of users, myself included. There are flashable .zip files for Philz and CWM, if you install both on your SD card there is no harm in switching to Philz in order to check it out, you can then easily flash back to CWM if you want.
http://forum.xda-developers.com/showthread.php?t=2446393
P.S. Knowing how to use Odin is a valuable skill, nothing wrong with having an app perform a task like installing a custom recovery as long as you also know the more "nuts and bolts" approach.

Trouble flashing custom rom on T999L

I had no problems rooting my s3 and putting custom recovery but when I attempt to flash either cyanogenmod or resurrection remix I get the status error 7. Then if I delete the Assert portion I either get status 6 error or it goes into a boot loop and I have to reinstall stock again with odin. I have also downloaded notepad++ as recommended to no avail.
You need to be on at least MD5 bootloader/firmware.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
You need to be on at least MD5 bootloader/firmware.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I just looked on the firmware I flashed on my phone whenever it wouldn't boot and it is md5.
So are you saying you tried to flash MD5 and it would not boot? What were you running before flashing? Did you factory reset?
DocHoliday77 said:
So are you saying you tried to flash MD5 and it would not boot? What were you running before flashing? Did you factory reset?
Click to expand...
Click to collapse
I have tried multiple roms and sometimes got error 7 sometimes error 6 and sometimes unable to boot, at which point I would then flash the stock firmware with odin on it and then it would work again, but I want to be able to put a firmware with kitkat on it.
Youd probably be best off updating to 4.3 firmware if you haven't already. If you're out of warranty there is little reason not to update imo.
Then use twrp 2.7.0.0 for your recovery. Some have had recent problems flashing with cwm.
If you still have issues, let us know exactly what steps you followed and exactly what you were trying to flash.
Sent from my SGH-T999 using Tapatalk
It came with 4.3, that's not the issue, I have tried both twrp and cwm to flash a cyanogenmod kitkat rom and I get the status error 7 at first, if I do what is said to get rid of that and delete the lines at the start then it gets a status error 6. At which point it no longer boots then I need to flash it back to the stock firmware.
Did you try the latest version of either Recoveries ? If its not the latest version you'd get error.
With the 4.3 firmware, you do not have to remove any Assert Lines from the updater Script. Just in case go back to the last stable release of CM 11.
27a
Just updated to a newer cwm to no avail, still getting status 7 error.
What CWM Version is that ?
6.0.4.5
Please post the Recovery Log. Its present in /cache/recovery
62453634 08
I don't see a cache folder
deadly8123 said:
I don't see a cache folder
Click to expand...
Click to collapse
You need a Root Explorer with Root access. Remount System as R/W in your Root Explorer.
Finally was able to do it I flashed a d2lte rom instead of a d2tmo rom.

Categories

Resources