Hey guys, I just rooted my S3 and I was looking forward to installing the CM10, but when I several errors while doing so. First of the error was when I tried to factory reset using CWM, it skipped a certain step; iirc it had something to do with mounting. The other error was when I wanted to install CM10. There was an error saying something aboutassets and that the installation was aborted. Am I missing anything?
Also, I started using Android a few months ago so I may not be familiar with some terms. Thanks guys!
I will post the exact error when I get to try again.
I have a very similar problem. CWMRecovery just doesn't seem to click for my device (SGH-T999v). My recommendation is to re-install recovery.
Two easy ways to do this that I can think of: #2 is easier I think, but most people use CWM, so whatever u want.
1. a) Sticking with CWM. Get an app called Mobile Odin Lite here. Install that on your phone.
b) Download the latest version of CWMRecovery FOR YOUR PHONE from their site here. (I copied the link for SGH-T999 for you here.)
c) Put the file on your device, open up Mobile Odin Lite, select the recovery.img in the appropriate spot, and go ahead and flash it to your phone
2. Install TWRP instead. Go over to the play store and install GooManager. You can use it to install TWRP touch recovery (and do a bunch of other stuff).
Now if you haven't made a backup already, DO SO NOW. Boot into recovery, select backup, and make that hang.
Now, it sounds like your getting a status 7 error. This is often a problem with old versions of CWM, so hopefully now this isn't a problem. Go ahead and try to flash your ROM. If you continue to get the error, here's how to fix it, just be cautious.
What's happening is the script that is being run to flash the ROM is checking if your device is the exact build that the ROM was intended for. The following is how to skip this check, SO BE 100% SURE THE ROM YOU HAVE IS FOR THE PHONE YOU HAVE. Check in your phone /system/build.prop that ro.product.device = d2tmo (or d2can if your canadian on WIND Mobile). Check t
a) Open up the zip file your trying to flash on your computer.
b) Navigate to /META-INF/com/google/android/, open up updater-script.
c) Take out the first line, it should say " assert(getprop("ro.product.device") == "d2tmo" || getprop("ro.build.product") == "d2tmo"); " If it says d2 something else, than this ROM is not for your device. stop here and get CM10 from here.
d) Save the changes, make sure the changes are saved in the file in the .zip.
e) Flash the ROM. You won't get the error, since it's not going to check for your build.
Remember, do this with the wrong ROM and you just soft-bricked your device.
Good Luck, I hope this was helpful
dudds4 said:
I have a very similar problem. CWMRecovery just doesn't seem to click for my device (SGH-T999v). My recommendation is to re-install recovery.
Two easy ways to do this that I can think of: #2 is easier I think, but most people use CWM, so whatever u want.
1. a) Sticking with CWM. Get an app called Mobile Odin Lite here. Install that on your phone.
b) Download the latest version of CWMRecovery FOR YOUR PHONE from their site here. (I copied the link for SGH-T999 for you here.)
c) Put the file on your device, open up Mobile Odin Lite, select the recovery.img in the appropriate spot, and go ahead and flash it to your phone
2. Install TWRP instead. Go over to the play store and install GooManager. You can use it to install TWRP touch recovery (and do a bunch of other stuff).
Now if you haven't made a backup already, DO SO NOW. Boot into recovery, select backup, and make that hang.
Now, it sounds like your getting a status 7 error. This is often a problem with old versions of CWM, so hopefully now this isn't a problem. Go ahead and try to flash your ROM. If you continue to get the error, here's how to fix it, just be cautious.
What's happening is the script that is being run to flash the ROM is checking if your device is the exact build that the ROM was intended for. The following is how to skip this check, SO BE 100% SURE THE ROM YOU HAVE IS FOR THE PHONE YOU HAVE. Check in your phone /system/build.prop that ro.product.device = d2tmo (or d2can if your canadian on WIND Mobile). Check t
a) Open up the zip file your trying to flash on your computer.
b) Navigate to /META-INF/com/google/android/, open up updater-script.
c) Take out the first line, it should say " assert(getprop("ro.product.device") == "d2tmo" || getprop("ro.build.product") == "d2tmo"); " If it says d2 something else, than this ROM is not for your device. stop here and get CM10 from here.
d) Save the changes, make sure the changes are saved in the file in the .zip.
e) Flash the ROM. You won't get the error, since it's not going to check for your build.
Remember, do this with the wrong ROM and you just soft-bricked your device.
Good Luck, I hope this was helpful
Click to expand...
Click to collapse
Thank you so much! It turns out that my CWM was not updated, and I think that caused the problem. I updated it and it seemed to work fine.
Related
I'm rooted multiple devices, and while the process is rarely an easy straight shot for me, this sprint gs2 of my wife's has proven to be my hardest. I've managed to at this point get it rooted though oden plus get cwm installed on it through oden as well.
Now my issue is whenever I try to install cm through cwm I'm getting the same error, regardless of if it's cm7, 9, and 10.
It is as follows:
-- Installing: /sdcard/cm-9.1.0-epicmtd.zip
Finding update package...
Opening update package...
Installing update...
assert failed:
getprop("ro.product.device") == "epic" ||
getprop("ro.build.product") == "epic" ||
getprop("ro.product.device") == "epicmtd" ||
getprop("ro.build.product") == "epicmtd" ||
getprop("ro.product.device") == "SPH-D700" ||
getprop("ro.build.device") == "SPH-D700"
E:Error in /sdcard/cm-9.1.0-epicmtd.zip
(Status 7)
Installation aborted.
If I try to have rom manager install it from within the app, it gets stuck at the point where I tell it yes, reboot into recovery.
I've gotten to the point of being able to use cwm after quite a bit of non-straightforward steps, mostly revolving around walkthroughs and zip references that referred to older ota builds.
Not complaining, just saying the point I'm out now is not as reliable as I'd like it to be.
I'm pretty familiar with pulling logs, not so familiar with adb but fine with command prompt. I'll be happy to try whatever anyone thinks of and if someone has the time I'd be happy to webcast the screen as I follow someone's instructions.
PS. I did find this explanation as a possible cause of the issue so food for thought -
http://forums.androidcentral.com/ep...p-fixing-wifes-phone-root-rom-sd-problem.html
Its been quite some time since I've messed with the Epic 4g but you flashed to the EpicMTD ROM. When you did this you changed your phones file partitioning to a completely different format.
In simple terms the Epic 4g and most devices of its time comes formatted in RFS format and along came EXT 4 format with many custom ROMs which allowed faster write times, speed improvements etc. Then they discovered this MTD format which again changes things.. I believe the problem your running into is when the device was formatted over to this MTD your having issues doing restores and such because your old recovery data is in RFS or EXT 4 format. Bottom line it won't work.
You will have to use the guide below to restore your device back a working state and remove the MTD formatting.
Thanks
Flash through odin the el26 repack from chris41g. I believe the format of system is what is causing that as well. I use the twrp packed up by chris which can be foumd on goo.im personally. Has never resulted in a brick. For me.
sent from MY BAD A$$ ET4G
are you sure you're using ROMs for the sph d710?
Also, rom manager apparently bricks this phone...don't use it
yea you're definitely using the wrong ROMs...note that there is an epic 4g and epic 4g touch
best way to flash a rom (unless stated otherwise in OP of ROM)
install odin
download el26 cwm kernel http://www.mediafire.com/?hkydca9ob98z89m
turn ur phone off. hold volume down and power to get into download mode
once in download mode plug it in pc (make sure drivers are installed)
open odin
click pda option and select that el26 cwm
hit start
after it finishes and the phone starts to reboot hold volume up and power
you'll be in cwm recovery.. from there clear data clear cache clear dalvik cache
flash ROM
flash gapps if u want
reboot
Your flashing roms for the wrong device. Sph-d700= epic4g/galaxy s sph-d710=epic 4g touch/galaxy s2
We are legion, for we are many
replies to op
Thanks everyone. I'll start from the top and work my way down. I'll go search this sub-forum for the specific packages you mentioned, and then google if that doesn't work. If you know they are hard to find or there are variations that I might choose accidentally, please pm or post up the page/link you would go to for it. Know that sounds needy, but like I said I've managed to find only half-right walkthroughs thus far, so apparently I'm not too bright.
Thanks
Read evils post. I didn't even notice that.
sent from MY BAD A$$ ET4G
got it done
okay I went back, started from the beginning again with
SPH-D710.FF18_CL663858_ROOTED-OneClick to redo the root (yeh, I know, once it's rooted it's rooted so no need, but I like to trial and error with similar starting points)
then use odin3 v1.85 from GalaxyS2Recovery.zip to install CWM
- this time I knew about the pageup, pagedown, pageup, pagedown to unlock the power button - I didn't last time and resorted to installing AGAT's recovery, which may have confused the process
used the cm build and gapps from http://e4gtcm.blogspot.com/ and was able to get it to install
- even though I did a [factory wipe, wipe partition, wipe dalv cache, and wipe batt stats], it got stuck on the cm animation, so did the [ ] again and I made it in
one question - with my htc hero, gs3, and different tablets, there was a steady stream of builds...nightlies, stables, etc
with this phone I'm seeing almost nothing now that I'm search for d710...is this device not that heavily developed for? thanks
idk if you know but there are tons of ROMS for this phone on XDA
a thread title with [ROM] in it means it's a ROM
go here..
http://forum.xda-developers.com/forumdisplay.php?f=1734
http://forum.xda-developers.com/forumdisplay.php?f=1284
So, I recently rooted my i747 and used Odin to load CWM v5.5.04 on my phone. I backed everything up, and proceeded to get into recovery to flash a new ROM, so I wiped as needed and I cannot install a ROM.
Particularly, this ROM: http://www.androidauthority.com/galaxy-s3-i747-jelly-bean-paranoidkangdroid-rom-143982/
This comes up whenever I try:
"assert failed: getprop("ro.product.device") == "d2att" || getprop("ro.product.device") == "d2att"
E:Error in /sdcard/PAC Man/ PK-1.40-d2att.zip
(Status 7)
Installation Aborted
It also happens when I try installing PAC Man.
HELPPP
Encerspay said:
So, I recently rooted my i747 and used Odin to load CWM v5.5.04 on my phone. I backed everything up, and proceeded to get into recovery to flash a new ROM, so I wiped as needed and I cannot install a ROM.
Particularly, this ROM: http://www.androidauthority.com/galaxy-s3-i747-jelly-bean-paranoidkangdroid-rom-143982/
This comes up whenever I try:
"assert failed: getprop("ro.product.device") == "d2att" || getprop("ro.product.device") == "d2att"
E:Error in /sdcard/PAC Man/ PK-1.40-d2att.zip
(Status 7)
Installation Aborted
It also happens when I try installing PAC Man.
HELPPP
Click to expand...
Click to collapse
First of all, take a deep breath. It can get pretty frustrating and that's when you make mistakes that lead into a brick.
You might wanna look into a newer CWM or TWRP (GooManage in the market).
Have you tried flashing another ROM? Also, did you grab the version for the i747?
Encerspay said:
So, I recently rooted my i747 and used Odin to load CWM v5.5.04 on my phone.
Click to expand...
Click to collapse
Here is the issue. This version is outdated. CWM is on 6 point something now. Load the latest version and you should be able to flash the ROM of your choice. :highfive:
Gee, thanks guys!! It's comforting to a little nooblet such as myself to have help from members.
How can I load another recovery, though? I've already wiped everything
Encerspay said:
Gee, thanks guys!! It's comforting to a little nooblet such as myself to have help from members.
How can I load another recovery, though? I've already wiped everything
Click to expand...
Click to collapse
Get in download mode and flash stock. From there, get GooManager from the market, open it, hit menu and install the recovery. Finally, you can get in recovery and flash the ROM + Gapps you want.
Encerspay said:
Gee, thanks guys!! It's comforting to a little nooblet such as myself to have help from members.
How can I load another recovery, though? I've already wiped everything
Click to expand...
Click to collapse
I followed this guide
http://forum.xda-developers.com/showthread.php?t=1739426
Starting from THIRD step, you can either use adb or grab a terminal emulator from the play store.
BWolf56 said:
Get in download mode and flash stock. From there, get GooManager from the market, open it, hit menu and install the recovery. From there, you can get in recovery and flash the ROM + Gapps you want.
Click to expand...
Click to collapse
That's twice you beat me. I need to learn to type faster.
Encerspay said:
Gee, thanks guys!! It's comforting to a little nooblet such as myself to have help from members.
How can I load another recovery, though? I've already wiped everything
Click to expand...
Click to collapse
If you want to stick with cwm, flash stock s3 firmware and root again. Boot up, download rom manager and "update recovery". That will install version 6.0.2.3
BYOBret said:
I followed this guide
http://forum.xda-developers.com/showthread.php?t=1739426
Starting from THIRD step, you can either use adb or grab a terminal emulator from the play store.
That's twice you beat me. I need to learn to type faster.
Click to expand...
Click to collapse
Haha sorry, boring day at work makes me extra productive here
xBeerdroiDx said:
If you want to stick with cwm, flash stock s3 firmware and root again. Boot up, download rom manager and "update recovery". That will install version 6.0.2.3
Click to expand...
Click to collapse
One thing though, uninstall ROM Manager afterwards and don't use it for anything else than installing the custom recovery if you decide to go with CWM instead of TWRP.
I was planning on using Goo Manager after restoring my only nandroid backup, but it's corrupt.... Go Figure. :crying:
Anyway, I'm a bit confused on what is trying to be meant by flashing stock in download mode...
How does one go about doing that?
Encerspay said:
I was planning on using Goo Manager after restoring my only nandroid backup, but it's corrupt.... Go Figure. :crying:
Anyway, I'm a bit confused on what is trying to be meant by flashing stock in download mode...
How does one go about doing that?
Click to expand...
Click to collapse
There's a link to stock firmwares on the android development link. It has carrier downloads and instructions. There's a link just below the downloads that has the stock firmware downloads with root already injected
Encerspay said:
I was planning on using Goo Manager after restoring my only nandroid backup, but it's corrupt.... Go Figure. :crying:
Anyway, I'm a bit confused on what is trying to be meant by flashing stock in download mode...
How does one go about doing that?
Click to expand...
Click to collapse
Below is your answer:
BYOBret said:
I followed this guide
http://forum.xda-developers.com/showthread.php?t=1739426
Starting from THIRD step, you can either use adb or grab a terminal emulator from the play store.
That's twice you beat me. I need to learn to type faster.
Click to expand...
Click to collapse
Encerspay said:
So, I recently rooted my i747 and used Odin to load CWM v5.5.04 on my phone. I backed everything up, and proceeded to get into recovery to flash a new ROM, so I wiped as needed and I cannot install a ROM.
Particularly, this ROM: http://www.androidauthority.com/galaxy-s3-i747-jelly-bean-paranoidkangdroid-rom-143982/
This comes up whenever I try:
"assert failed: getprop("ro.product.device") == "d2att" || getprop("ro.product.device") == "d2att"
E:Error in /sdcard/PAC Man/ PK-1.40-d2att.zip
(Status 7)
Installation Aborted
It also happens when I try installing PAC Man.
HELPPP
Click to expand...
Click to collapse
This happens because you most likely have a i747m (Canadian S3). I have had this problem before and it is easy to fix. The recovery checks to see if you a flashing the right rom for your device, and it sees that the rom is an At&t one. Easy fix though, go into a file manager, I used total commander, and find the rom you are trying to flash, click the file, then META-INF>com>google>android> and then long press on updater-script. Unpack+edit, and delete the first line, which refers to it being an At&t rom. Save the file, reboot and make sure the change sticks, then flash away!
I live in the US, and I am on at&t. I did, however, order a refurb model.
Is it possible I could have gotten a Candian Model?
As of now, I am downloading the at&t stock rom from sammobile.com and I plan on installing it via Odin and then re rooting, followed by a Titanium Backup, then installing Goo Manager to get the latest CWM Recovery, finally getting my ROM on and I'll finish it off with a Titanium Backup.
Sounds like a 4-5 hour process. Awesome.
I just like to write everything down before I do it. Thanks so much guys!
Encerspay said:
I live in the US, and I am on at&t. I did, however, order a refurb model.
Is it possible I could have gotten a Candian Model?
As of now, I am downloading the at&t stock rom from sammobile.com and I plan on installing it via Odin and then re rooting, followed by a Titanium Backup, then installing Goo Manager to get the latest CWM Recovery, finally getting my ROM on and I'll finish it off with a Titanium Backup.
Sounds like a 4-5 hour process. Awesome.
I just like to write everything down before I do it. Thanks so much guys!
Click to expand...
Click to collapse
Definitely not that long of a process unless it's the download time.
Twrp comes from goo manager and titanium backup is apps. I think you meant nandroid.
I'm not trying to nitpick misunderstanding the processes and steps are a quick way to a brick.
Sent from my SGH-I747 using xda app-developers app
KorGuy123 said:
Definitely not that long of a process unless it's the download time.
Twrp comes from goo manager and titanium backup is apps. I think you meant nandroid.
I'm not trying to nitpick misunderstanding the processes and steps are a quick way to a brick.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
No, no, I understand. TWRP is what I meant, and since my nandroid is corrupt, I'm just going to restore the apps with Titanium.
Download time is definitely awful over here with at&t DSL rockin' 0.22 mbps.
Encerspay said:
No, no, I understand. TWRP is what I meant, and since my nandroid is corrupt, I'm just going to restore the apps with Titanium.
Download time is definitely awful over here with at&t DSL rockin' 0.22 mbps.
Click to expand...
Click to collapse
Awesome! Lol see you in a couple hours
Sent from my SGH-I747 using xda app-developers app
This is what I personally would do
1st. Odin to a stock rooted ROM
2nd. Once its all booted up download GooManager from play and install the recovery directly from GooManager (make sure its the correct recovery for your device. Its TWRP recovery)
3rd. Once installed reboot into recovery
Wipe, install, fix permissions, the whole 9
4th. Victory
I would recommend TWRP over CMW
Very few bugs, it fixes your internal partitions when going back and forth from 4.1 to 4.2 and making Nands is 1million times faster then CMW .. No status 7 or 0 errors
Sent from an ATM machine
Encerspay said:
I live in the US, and I am on at&t. I did, however, order a refurb model.
Is it possible I could have gotten a Candian Model?
As of now, I am downloading the at&t stock rom from sammobile.com and I plan on installing it via Odin and then re rooting, followed by a Titanium Backup, then installing Goo Manager to get the latest CWM Recovery, finally getting my ROM on and I'll finish it off with a Titanium Backup.
Sounds like a 4-5 hour process. Awesome.
I just like to write everything down before I do it. Thanks so much guys!
Click to expand...
Click to collapse
Does your phone boot up normally now, as is? If so, all you need is the new recovery.
http://forum.xda-developers.com/show....php?t=1739426
Starting from THIRD step, you can either use adb or grab a terminal emulator from the play store.
Really, only takes a couple minutes. Copy recovery.img file to your phone's internal /sdcard and then run the adb commands.
Erm, not exactly, I have a stock file for my phone (no root, but my speeds are so slow I'll just go through rooting again)
Odin can't load it.
So now I have a phone that can't boot.
What should I do with this tar.md5 file I have, exactly?
I'm lost here
Encerspay said:
Erm, not exactly, I have a stock file for my phone (no root, but my speeds are so slow I'll just go through rooting again)
Odin can't load it.
So now I have a phone that can't boot.
What should I do with this tar.md5 file I have, exactly?
I'm lost here
Click to expand...
Click to collapse
Remove the ".md5" from the file name so it ends with ".tar" and ODIN should load it correctly.... maybe, hold on.
edit: How did you attempt this first? Does ODIN give any error messages?
Here is ODIN procedure:
Use Odin, put phone into download mode [with phone off, hold vol. down + home + power ], connect to computer and open Odin.
once in odin click the PDA field and select the rom_xxx.tar.md5 you downloaded.
Leave Auto Reboot and F. Reset Time checked.
click start and
when done let phone reboot.
If you have issues flashing with Odin please ensure you are using the microusb cable that came with the phone, users have had issues using other cables.
I have scoured tons of threads looking for help but the basic solutions don't seem to be working. I'm at a loss on where to turn, so I'm starting a new thread.
I am trying to install CM10.0 stable from the Cyanogenmod wiki (cm-10.0.0-d2att, md5 checks out using HashTab) using Odin v3.07). The SD Card has been properly formatted using 3rd party software. I have Clockwork 6.0.1.2 installed (and thank goodness I figured out the backup/restore feature)
When I go to
install zip from sdcard -> choose zip from external sdcard -> cm-10.0.0-d2att.zip
I get:
Code:
assert failed: getprop(ro.product.device") == "d2att" || getprop(ro.build.product") == "d2att"
E:Error in /external_sd/cm-10.0.0-d2att.zip
(Status 7)
Installation aborted.
I know a bit of programming, so I assume that it thinks my phone (or at least the current software installed) is not for the d2att version. My phone is the Rogers version, so it's the correct one.
I don't know what to do from here. I've heard so many great things about CM10 but it's such a pain to get going, apparently. Any help would be appreciated. I've spent a long time tonight searching and reading to see if there is another way around it, and frankly I'm starting to get confused. Lots of different info and different programs that all say something else of that something else is wrong.
Thank you all for half-listening to me rant, and I appreciate any help you fine folks can throw me
Good night, I'm off to bed.
zeropaladn said:
I have scoured tons of threads looking for help but the basic solutions don't seem to be working. I'm at a loss on where to turn, so I'm starting a new thread.
I am trying to install CM10.0 stable from the Cyanogenmod wiki (cm-10.0.0-d2att, md5 checks out using HashTab) using Odin v3.07). The SD Card has been properly formatted using 3rd party software. I have Clockwork 6.0.1.2 installed (and thank goodness I figured out the backup/restore feature)
When I go to
install zip from sdcard -> choose zip from external sdcard -> cm-10.0.0-d2att.zip
I get:
Code:
assert failed: getprop(ro.product.device") == "d2att" || getprop(ro.build.product") == "d2att"
E:Error in /external_sd/cm-10.0.0-d2att.zip
(Status 7)
Installation aborted.
I know a bit of programming, so I assume that it thinks my phone (or at least the current software installed) is not for the d2att version. My phone is the Rogers version, so it's the correct one.
I don't know what to do from here. I've heard so many great things about CM10 but it's such a pain to get going, apparently. Any help would be appreciated. I've spent a long time tonight searching and reading to see if there is another way around it, and frankly I'm starting to get confused. Lots of different info and different programs that all say something else of that something else is wrong.
Thank you all for half-listening to me rant, and I appreciate any help you fine folks can throw me
Good night, I'm off to bed.
Click to expand...
Click to collapse
There are two reasons for your error. Yes the rogers phone and the at&t are identical phones but at a recovery level they aren't your phone will have a d2can recovery installed and the error is telling you you need to have the d2att recovery.
Also your recovery is out of date.
I don't have a link for clockwork mod but if you go here
http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.5.0.0-d2att.tar
This is the latest twrp for d2att. Flash this through Odin and it'll overwrite your current recovery. You'll be good to go after that.
Sent from my SGH-I747 using xda app-developers app
KorGuy123 said:
There are two reasons for your error. Yes the rogers phone and the at&t are identical phones but at a recovery level they aren't your phone will have a d2can recovery installed and the error is telling you you need to have the d2att recovery.
Also your recovery is out of date.
I don't have a link for clockwork mod but if you go here
http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.5.0.0-d2att.tar
This is the latest twrp for d2att. Flash this through Odin and it'll overwrite your current recovery. You'll be good to go after that.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Just a tip, you don't have to go through ODIN to flash a recovery if you already have a recovery installed. There are recovery flashable files to install which are super easy to use. Just like flashing a ROM. They can also be found on TRWPs website.
Cheers.
flexfulton said:
Just a tip, you don't have to go through ODIN to flash a recovery if you already have a recovery installed. There are recovery flashable files to install which are super easy to use. Just like flashing a ROM. They can also be found on TRWPs website.
Cheers.
Click to expand...
Click to collapse
The twrp site provides .tar and .img
The cwm site provides just the .img
Neither one flashable in recovery.
Because he's on a d2can the phone recognizes it and won't let him flash through ROM manager and goo manager to a d2att.
@zeropaladn In case you don't want to odin.
This is the flashable recovery for d2att twrp
http://forum.xda-developers.com/attachment.php?attachmentid=1879305&d=1365812877
In case you want to stick with clockworkmod and don't want to Odin.
Flashable cwm 6.0.3.1 http://forum.xda-developers.com/attachment.php?attachmentid=1888710&d=1366136727
Sent from my SGH-I747 using xda app-developers app
Here is about every way we know to install recovery
http://forum.xda-developers.com/showthread.php?t=1903913
I flashed the new CWM and the d2att recovery and it worked! I didn't know that even though the phone is physically the same it wouldn't take the d2att rom from a a2can recovery. Got it working and TouchWiz is GONE! Thanks to everyone (i found the button don't worry)
I got the stock ROM off of amazon. Converted it to update.zip, couldn't flash it cuz it said "blaze" as the codename in the updater script. Updated it to otter, still can't flash it. What am I doing wrong? Help is appreciated, thanks.
GalaxyExhibit said:
I got the stock ROM off of amazon. Converted it to update.zip, couldn't flash it cuz it said "blaze" as the codename in the updater script. Updated it to otter, still can't flash it. What am I doing wrong? Help is appreciated, thanks.
Click to expand...
Click to collapse
Revert to an earlier version of TWRP (preferably one before the different "otter" and "blaze" versions) or install COTR. I'd recommend COTR though.
Also, DON'T FORGET TO FACTORY RESET!!! Otherwise, you will need a factory cable to fix it.
soupmagnet said:
Revert to an earlier version of TWRP (preferably one before the different "otter" and "blaze" versions) or install COTR. I'd recommend COTR though.
Also, DON'T FORGET TO FACTORY RESET!!! Otherwise, you will need a factory cable to fix it.
Click to expand...
Click to collapse
Thanks, will do.
Ok, so here is what I did to fix the issue. Instead of installing TWRP (this is a smarter idea), I installed ubuntu as a side OS, after installed, downloaded stock firmware. After that, changed it to zip format and named it update.zip. After that, I changed the name from blaze to otter in the update-script. Guess what, it worked. Recommending this method to anyone who has either this issue, TWRP 2.6 installed, or just likes to play around with their KF.
LGHater said:
Ok, so here is what I did to fix the issue. Instead of installing TWRP (this is a smarter idea), I installed ubuntu as a side OS, after installed, downloaded stock firmware. After that, changed it to zip format and named it update.zip. After that, I changed the name from blaze to otter in the update-script. Guess what, it worked. Recommending this method to anyone who has either this issue, TWRP 2.6 installed, or just likes to play around with their KF.
Click to expand...
Click to collapse
Alright, I'm having the same issue, but I'm not sure how to do the things you've described here, being a complete noob. Could you provide a bit more of a detailed instruction, including what difference installing Ubuntu made and how one goes about changing the name from blaze to otter in the update-script? (Starting with where does one find the script.)
I'm currently running TWRP 2.6.0.0 and just want to go back to stock...which is now 6.3.2.
Thx.
bembley said:
Alright, I'm having the same issue, but I'm not sure how to do the things you've described here, being a complete noob. Could you provide a bit more of a detailed instruction, including what difference installing Ubuntu made and how one goes about changing the name from blaze to otter in the update-script? (Starting with where does one find the script.)
I'm currently running TWRP 2.6.0.0 and just want to go back to stock...which is now 6.3.2.
Thx.
Click to expand...
Click to collapse
Get a virtual machine, download ubuntu and select the ISO file in whatever VM software you use. When it's done installing, download the stock software and when it's done downloading, change the format from BIN (I think it's a bin I might be wrong) to ZIP. Then go into the ZIP file and go into Meta-Inf, and edit the update-script with the text software on ubuntu and change the code name from blaze to otter if you're having a status 7 error. And you're done. Get ready to flash the software by performing a factory reset. Then go back and install the update.zip. And you're done. If this didn't work, post on this thread again with any confusion or errors.
LGHater said:
Get a virtual machine, download ubuntu and select the ISO file in whatever VM software you use. When it's done installing, download the stock software and when it's done downloading, change the format from BIN (I think it's a bin I might be wrong) to ZIP. Then go into the ZIP file and go into Meta-Inf, and edit the update-script with the text software on ubuntu and change the code name from blaze to otter if you're having a status 7 error. And you're done. Get ready to flash the software by performing a factory reset. Then go back and install the update.zip. And you're done. If this didn't work, post on this thread again with any confusion or errors.
Click to expand...
Click to collapse
Worked marvelously...and confirmed my suspicion of hardware problems. The stock image loaded, but processes keep failing and it reboots itself over and over again...similar to what it was doing with the cyanogen mod I was using.
Anyway...Thanks for your help!!
bembley said:
Worked marvelously...and confirmed my suspicion of hardware problems. The stock image loaded, but processes keep failing and it reboots itself over and over again...similar to what it was doing with the cyanogen mod I was using.
Anyway...Thanks for your help!!
Click to expand...
Click to collapse
Well I'm glad things worked out for you and the error was gone. Enjoy stock, I guess. lol
I own a Galaxy S3 (Fido, a Rogers subsidiary), and recently updated to the klunky bloated nightmare that is the 4.3 update; thus my motivation to switch to Cyanogenmod. I have successfully rooted the device using chainfire's auto-root (CF-Auto-Root-d2can-d2vl-sghi747m). In addition I am using the latest clockworkmod (6.0.4.3)
I downloaded the CM 10.2 stable release (link: http://download.cyanogenmod.org/get/jenkins/49846/cm-10.2.0-d2att.zip) and the gapps package, and pushed them to /sdcard/. However, when I try to install the CM package, I get an assert error at ro.bootloader. When I tried restoring using a NANDroid backup, my phone constantly popped up that " Unfortunately, the process com.google.process.gapps has stopped". So frequently that it was next to impossible to do anything on the phone. I tried resetting all apps in the application manager to no avail. Fortunately I backed up most of my important apps using Titanium so I'm not completely screwed after a factory reset.
My ro.bootloader is I747MVLUEMK5. After some searching, I tried flashing the bootloader to the one provided here: http://forum.xda-developers.com/showpost.php?p=41503727&postcount=13716, but I was unable to do so (got SW REV CHECK FAIL : Fused 1 > Binary 0). Bupkis.
I'd really like to get CM on my device, and any help would be appreciated. Failing that, is there a way to fix the gapps errors cropping up when I use my NANDroid backup?
Thanks in advance.
I don't know what the problem is with cm10.2 but I had the same problem restoring a 4.3 nandroid. I had to reboot into recovery and wipe data, cache and dalvik. Reboot and set everything up fresh. That's the only way I could get the nandroid to get me back to 4.3.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Glad to know it's not just me!
I have a sneaking suspicion that I may have to actually replace the bootloader, and not just unlock it. But most of the bootloader downloads I've searched for provide links to ICS bootloaders, and something tells me it's not a simple thing to roll back.
review.cyanogenmod.org/#/c/55060/
Forgive the double post, but it looks like it's a known problem with CM that they've fixed in 11.0. I guess I need to wait for them to backport it or until 11.0 gets a stable release.
I'd still like to know how to fix my NANDroid backup, though.
Edit: Looks like they've fixed it and it'll be in the next stable build! review.cyanogenmod.org/#/c/55061/
Vergeh said:
review.cyanogenmod.org/#/c/55060/
Forgive the double post, but it looks like it's a known problem with CM that they've fixed in 11.0. I guess I need to wait for them to backport it or until 11.0 gets a stable release.
I'd still like to know how to fix my NANDroid backup, though.
Edit: Looks like they've fixed it and it'll be in the next stable build! review.cyanogenmod.org/#/c/55061/
Click to expand...
Click to collapse
I had this problem as well but I managed to do some digging and fix the problem. The problem was that the developers forgot to add I747MVLUEMK5 as a bootloader in the "updater-script". The updater script is responsible to make sure you don't flash the wrong rom with the wrong samsung model. Since i747mvluemk5 was not added, the phone failed the inspection. To solve this, add the bootloader "I747MVLUEMK5" into the d2att cyanogenmod zip file. Basically, this is what you do:
1) Download the d2att stable 10.2 cyanogenmod
2) unzip the d2att stable 10.2 cyanogenmod
3)And then open META-INF>com>google>android>updater-script
4)Once you found updater-script, open it with notepad
5)Then you must add this bootloader script since it is missing: || getprop("ro.bootloader") == "I747MVLUEMK5"
6)Obviously, don't just copy exactly like mine, but make sure I747MVLUEMK5 is there. Not sure, but i think you can delete one of the bootloaders such as I747MUMBLL1 and replace it with I747MVLUEMK5 instead.
7)after you made your change of the updater-script, rezip the files and flash it.
Cooro said:
I had this problem as well but I managed to do some digging and fix the problem. The problem was that the developers forgot to add I747MVLUEMK5 as a bootloader in the "updater-script". The updater script is responsible to make sure you don't flash the wrong rom with the wrong samsung model. Since i747mvluemk5 was not added, the phone failed the inspection. To solve this, add the bootloader "I747MVLUEMK5" into the d2att cyanogenmod zip file. Basically, this is what you do:
1) Download the d2att stable 10.2 cyanogenmod
2) unzip the d2att stable 10.2 cyanogenmod
3)And then open META-INF>com>google>android>updater-script
4)Once you found updater-script, open it with notepad
5)Then you must add this bootloader script since it is missing: || getprop("ro.bootloader") == "I747MVLUEMK5"
6)Obviously, don't just copy exactly like mine, but make sure I747MVLUEMK5 is there. Not sure, but i think you can delete one of the bootloaders such as I747MUMBLL1 and replace it with I747MVLUEMK5 instead.
7)after you made your change of the updater-script, rezip the files and flash it.
Click to expand...
Click to collapse
Worked like a charm; had no idea that it'd be so simple to fix! You, sir, are awesome.
Edit: One week later and I've had zero problems. If anything, CM 10.2 is more stable than the Samsung 4.3 release.