Related
I have rooted/flashed numerous phones and have only ever had issues with this phone. Anyways, enough with the intro...
history: had cm10 running fine but decided to try some ICS roms for better battery life / tethering with 4g still active.
-------
So I used odin 1.85, and have flashed StockCWM-EL26.tar.md5. This gets me CWM recovery 5.0.2.7, from here i tried to flash cm9 experimental build beta1 or something like that and it gives me a status 7.
I tried restoring a backup I had made previously but it failed saying mm blk9 or something like that. I believe these don't work because i had updated to the latest CWMR for the e4gt, but during flashing those custom ICS ROMS they flashed their own recovery
Odin appears to be the only thing that actually recognizes my phone. I can't get fastboot or adb to work in download mode. I believe fastboot should work. I mention this because the one click rooting methods sit waiting for me to plug in my phone.
I do have access to the SD card, so if i can get a ROM that CWMR 5.0.2.7 will flash i can put it on the card and try that. But again thats how i got to cm10 was from first installing this cm9 beta build.
Any ideas or useful info i left out that may help please let me know!
mohbandy said:
I have rooted/flashed numerous phones and have only ever had issues with this phone. Anyways, enough with the intro...
history: had cm10 running fine but decided to try some ICS roms for better battery life / tethering with 4g still active.
-------
So I used odin 1.85, and have flashed StockCWM-EL26.tar.md5. This gets me CWM recovery 5.0.2.7, from here i tried to flash cm9 experimental build beta1 or something like that and it gives me a status 7.
I tried restoring a backup I had made previously but it failed saying mm blk9 or something like that. I believe these don't work because i had updated to the latest CWMR for the e4gt, but during flashing those custom ICS ROMS they flashed their own recovery
Odin appears to be the only thing that actually recognizes my phone. I can't get fastboot or adb to work in download mode. I believe fastboot should work. I mention this because the one click rooting methods sit waiting for me to plug in my phone.
I do have access to the SD card, so if i can get a ROM that CWMR 5.0.2.7 will flash i can put it on the card and try that. But again thats how i got to cm10 was from first installing this cm9 beta build.
Any ideas or useful info i left out that may help please let me know!
Click to expand...
Click to collapse
I do not know much but it looks like the cm9 rom that you downloaded is a bad download, go back to Odin 1.85 and flash StockCWM-EL26.tar.md5. again and flash your cm10 rom or another rom to get back on track
Sent from my SPH-D710 using xda premium
jc.m said:
I do not know much but it looks like the cm9 rom that you downloaded is a bad download, go back to Odin 1.85 and flash StockCWM-EL26.tar.md5. again and flash your cm10 rom or another rom to get back on track
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I know I am trying to flash the proper cm10 rom (the one that worked before) because its the only cm10 rom on my SD card.
I'm pretty sure I followed this guide to make it all happen.
Is there a way i could flash the latest CWM recovery using ODIN? Then I would think this recovery would be able to restore my backups
Odin this:
http://shabbypenguin.com/k0/ecm/E4GT-EL29-directbootCWM-v3.tar.md5
goes in PDA slot in odin
calisro said:
Odin this:
http://shabbypenguin.com/k0/ecm/E4GT-EL29-directbootCWM-v3.tar.md5
goes in PDA slot in odin
Click to expand...
Click to collapse
Successfully used odin to flash this. I then tried using the cwm 5.0.2.7 recovery again to install cm9 and cm10, but both failed saying
Code:
assert failed: getprop("ro.product.device") == "d710" || getprop("ro.build.product") == "d710" || ..........
+several other options. I'm going to try another cm9 tonight unless anybody has another ROM suggestion *hint*hint*
I then tried to restore my backups, which said they couldn't find system/data. So then i tried advanced restore and selected boot which went fine, system gives my this:
Code:
E:format_volume: no MTD partition "/dev/block/mmcblk0p9"
Error while formatting /system!
mohbandy said:
Successfully used odin to flash this. I then tried using the cwm 5.0.2.7 recovery again to install cm9 and cm10, but both failed saying
Code:
assert failed: getprop("ro.product.device") == "d710" || getprop("ro.build.product") == "d710" || ..........
+several other options. I'm going to try another cm9 tonight unless anybody has another ROM suggestion *hint*hint*
I then tried to restore my backups, which said they couldn't find system/data. So then i tried advanced restore and selected boot which went fine, system gives my this:
Code:
E:format_volume: no MTD partition "/dev/block/mmcblk0p9"
Error while formatting /system!
Click to expand...
Click to collapse
You may also want to do a full restore look here http://www.sxtpdevelopers.com/showt...H-D710-FI27-(FI27-Modem-Kernel-ROM-Root-Stock
Sent from my SPH-D710 using xda premium
it lives!
I'm not sure where to give credit, but this is what secret sauce finally made things work..
a little bit of this
followed by using Odin v1.85, PDA loaded stock D710_CODE_SPH-D710.FI27_CL1127689_REV02_user_low_ship.tar.md5.7z from this link
So now that i at least have a booting device, i've been here before and can make my way to eventually restoring my backup.
thanks everyone!
mohbandy said:
I'm not sure where to give credit, but this is what secret sauce finally made things work..
a little bit of this
followed by using Odin v1.85, PDA loaded stock D710_CODE_SPH-D710.FI27_CL1127689_REV02_user_low_ship.tar.md5.7z from this link
So now that i at least have a booting device, i've been here before and can make my way to eventually restoring my backup.
thanks everyone!
Click to expand...
Click to collapse
Good to know that you are back on track
Sent from my SPH-D710 using xda premium
mohbandy said:
I'm not sure where to give credit, but this is what secret sauce finally made things work..
a little bit of this
followed by using Odin v1.85, PDA loaded stock D710_CODE_SPH-D710.FI27_CL1127689_REV02_user_low_ship.tar.md5.7z from this link
So now that i at least have a booting device, i've been here before and can make my way to eventually restoring my backup.
thanks everyone!
Click to expand...
Click to collapse
Credit goes to sfhub, who we hope will be back at some point!
For what its worth, now that I am back to where I originally started...
The CM10 I was flashing was putting CWM v6.0.1.7 (i believe) on my device. I made my backup using this and was able to restore to this after a failed boot of my CM10 downloaded ROM.
At this point, i then flashed the latest officially supported CWM version as reported from the cwm site. I then made another backup, this time using CWM v5.0.2.7 and now feel more comfortable/confident having the ability to re-flash this guy.
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)
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
So I was feeling all confident, ready to install a new ROM, figuring based on my experience, I should have no issues. Went to flash a rom, and now I have a new problem...
So, problem is when ever I try to install a rom, installation is aborted by CW. The error is "assert failed: getprop ("ro.product.device") == "t0lte" // getprop ("ro.product.device") -- "t0ltexx // getprop("ro.product.device") -- "GT-N7105" // .... and then so on, many more times, listing different varients of my phone T889, I317, etc.
The steps I took were: boot to recovery, factory reset/data wipe, format sdcard (I had an issue the last time I flashed where the sdcard was still full of crap after data wipe), try to flash rom, experience error, stare at my phone for 5 minutes, then helplessly post on XDA.
I tried this with two different roms, AOKP and PAC-Man... really stuck here, I can't flash anything. Hope you guys can help!
Reflash through Odin or Samsung Kies, re-root and try again
Crimson Ghoul said:
Reflash through Odin or Samsung Kies, re-root and try again
Click to expand...
Click to collapse
Reflash stock you mean? I gotta go out, but I'll give that a shot as soon as I get back home. Have you heard of this problem before? Your advice sounds pretty solid, thanks.
Not the exact same problem, but similar. Odin/Kies always fixes it
Didn't work :/ ... now I'm back on stock ROM, rooted, but same errors. Here's my error page:
http://i.imgur.com/PQdAGwv.jpg
Hope you guys can help!
Err, okay, I know nobody likes to end a thread without a true solution, but I did some googling with the exact text of my errors, and one guy said he tried to install the rom through rom manager, so i tried to install a touchwiz rom through rom manager... and it worked.... and then froze half way through.... so i pulled the battery, hit the power button, it automatically went into recovery, and i was going to try the TW rom, but gave AOKP one more try for the hell of it..and... it worked. I don't know why. It just worked.
You need to update your recovery. TWRP 2.5 or whatever is the latest.
rangercaptain said:
You need to update your recovery. TWRP 2.5 or whatever is the latest.
Click to expand...
Click to collapse
+1 to this^^^^^^^^
Here's the link to the TWRP thread so you can take a look..
http://forum.xda-developers.com/showthread.php?p=33867032
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4 Beta