Related
Ive tried to flash three seperate ROM's using the fake flash method but when I select the zip from my sd card I get the following:
Opening update package.....
E: cant open /sdcard/*ROM NAME*
(bad)
Installation aborted
Why is this happening?
Any help would be greatly received
are you sure it's fake flash problem...??? i had it too but with the default rooting recovery too....after several reboots it accepted the rom and flashed it regularly
lambrospower said:
are you sure it's fake flash problem...??? i had it too but with the default rooting recovery too....after several reboots it accepted the rom and flashed it regularly
Click to expand...
Click to collapse
no lol
I just presumed it was as I dont remember having the issue before trying this method.
I'll keep trying
pwoyorkie said:
no lol
I just presumed it was as I dont remember having the issue before trying this method.
I'll keep trying
Click to expand...
Click to collapse
Maybe your ROM is corrupted. Try downloading it again just for make shure.
And if fake-flash doesn't work you can try AMDesireRecovery if you have a computer nearby... old methods work better sometimes
BlackLine7 said:
Maybe your ROM is corrupted. Try downloading it again just for make shure.
And if fake-flash doesn't work you can try AMDesireRecovery if you have a computer nearby... old methods work better sometimes
Click to expand...
Click to collapse
Its been the same for 3 different ROM downloads so the chances of all three being corrupt are slim
I'm going to try using a different SD card and then i'll try and different recovery method
well using a different sd card seemed to fix teh problem.
Odd but there you go
I get the error:Can't open /sdcard/.....zip(bad)
Any other solutions besides the one in the older thread. It's directions were not clear at all.
It's a bad dowload.....try redownloading....happens to me all the time when DL'in from my PC....not sure what the other responses to u were.....but that's what's happeneing
Sent from my PC36100 using XDA Premium App
Reverepats...I downloaded two different MikG Roms and neither worked, I also tried Kings Alliance it had the same error. When I ran the Rom I was running before, SalvageRom, it worked. I see you are running MikG, where did u download from?
I'm assuming that you've tried reflashing recovery? Or possibly switching recoveries?
(from... Evo/MIUI/Tapatalk)
The file corrupted, and you just need to download it again.
No Plainjane, I didn't try flashing recoveries. I am currently using Amon RA's recovery v 2.3 I believe. Is there a newer version? If so, where do I find it to flash?
corey140 said:
No Plainjane, I didn't try flashing recoveries. I am currently using Amon RA's recovery v 2.3 I believe. Is there a newer version? If so, where do I find it to flash?
Click to expand...
Click to collapse
2.3 is the latest version. If you choose to reflash just do it via PC36IMG; though I'm positive its just a bad download.
teh roxxorz, I tried the download from HTCEVOHacks.com and MikMik Website and they both failed. I think both were 250MB, which was bigger than usual so it is possible, but I also tried flashing the Alliance Kingdom Rom from this site and got the same error. That's why I figured it was something with my phone. I got an (Oops Error, something went wrong, when I tried to do a Nandroid Restore also. I was able to reflash Salvage Rom and it worked perfect. SO CONFUSED...LOL!
corey140 said:
teh roxxorz, I tried the download from HTCEVOHacks.com and MikMik Website and they both failed. I think both were 250MB, which was bigger than usual so it is possible, but I also tried flashing the Alliance Kingdom Rom from this site and got the same error. That's why I figured it was something with my phone. I got an (Oops Error, something went wrong, when I tried to do a Nandroid Restore also. I was able to reflash Salvage Rom and it worked perfect. SO CONFUSED...LOL!
Click to expand...
Click to collapse
Well the bad zip [can't flash] means something is wrong with the zip file, the 'oops something went wrong,' means that the backup became corrupted.
http://dl.dropbox.com/u/19699565/PC36IMG.zip
Download that [ra recovery] place on the root of your sd card, boot into the bootloader, then apply update, reboot; and amon_ra 2.3 will be reflashed.
teh roxxorz said:
Well the bad zip [can't flash] means something is wrong with the zip file, the 'oops something went wrong,' means that the backup became corrupted.
http://dl.dropbox.com/u/19699565/PC36IMG.zip
Download that [ra recovery] place on the root of your sd card, boot into the bootloader, then apply update, reboot; and amon_ra 2.3 will be reflashed.
Click to expand...
Click to collapse
I really appreciate your help!!! So this flash will enable me to perform my Back-up right. I apologize for all the questions, I just started flashing and I am learning the basics.
corey140 said:
I really appreciate your help!!! So this flash will enable me to perform my Back-up right. I apologize for all the questions, I just started flashing and I am learning the basics.
Click to expand...
Click to collapse
You're straight, and well, potentially. IF the recovery backup itself is corrupted, you'll get the 'oops, something went wrong' error; if it was the recovery. Though you will be able to create and restore backups.
teh roxxorz said:
You're straight, and well, potentially. IF the recovery backup itself is corrupted, you'll get the 'oops, something went wrong' error; if it was the recovery. Though you will be able to create and restore backups.
Click to expand...
Click to collapse
Cool, downloaded the Amon RA Recovery you posted in the link. Flashed it and it went through. Will try to perform my Nandroid backup and post results.
corey140 said:
Cool, downloaded the Amon RA Recovery you posted in the link. Flashed it and it went through. Will try to perform my Nandroid backup and post results.
Click to expand...
Click to collapse
OK, it went more than the first time, but then got the same error:
Oops... something went wrong!
Please check the recovery log!
corey140 said:
OK, it went more than the first time, but then got the same error:
Oops... something went wrong!
Please check the recovery log!
Click to expand...
Click to collapse
Yea, unfortunately, that backup is corrupted, and you'll have to scrap it. Hopefully you have another one, or in a position to create a newer one.
Can I just Reboot and go back to what I was using?
corey140 said:
Can I just Reboot and go back to what I was using?
Click to expand...
Click to collapse
If you reboot, you'll be on whatever you were running before; as long as the backup didn't restore.
teh roxxorz said:
If you reboot, you'll be on whatever you were running before; as long as the backup didn't restore.
Click to expand...
Click to collapse
Cool that's what I will do. Hopefully I can get one of the new Gingerbread Roms here(MikG Preferably) with a .zip that is not corrupted. Since you and Plainjane are pretty sure it is the file that is corrupted. THANKS for all the help.
corey140 said:
Cool that's what I will do. Hopefully I can get one of the new Gingerbread Roms here(MikG Preferably) with a .zip that is not corrupted. Since you and Plainjane are pretty sure it is the file that is corrupted. THANKS for all the help.
Click to expand...
Click to collapse
Well I'm certain it is.
IF all else fails, go to the link on your evo, then download the zip from your phone, make your backup, do a full wipe, then locate it in the folder when you flash.
I'm almost certain it's an issue with your SD card. I've seen it before, but just recently remembered what the problem was. Sorry for the late reply, I was at work.
Backup everything on your card to your computer, this will erase all of your files. Also try to have a full battery, this could take some time depending on the size of your SD card, the class, and the number of files. Then, boot into recovery and select partition SD card (I can't remember where it is, sorry). If you move apps to your SD card - which I think is kind of necessary with the ginormous Sense 3.0 roms - use a larger size for the Ext partition. I never move apps to my SD card, so I set mine to the smallest option other than zero. For the swap size you can use the default 32mb - you may want to look into this more to see if there's a more recommended size.
When it finishes partitioning, go back to the main screen in recovery, plug your phone into your computer and select USB-MS toggle. This will mount your SD card so you can move files back to the SD card. If you're using Windows, it may want to scan and fix the card... just skip it. If you want to save time and/or battery, you can power down the phone and use a card reader instead. Then you can try to restore/make a nandroid backup or flash a rom - it should work.
Good luck, hope you get it fixed!
(from... Evo/MIUI/Tapatalk)
Download MikG 1.04 from http://dev-host.org/lv6fjpxaq9x4/MikG-Sense2.1-v1.04-signed.zip
After downloading the file, get an MD5 checker application such as this one: http://getmd5checker.com/download
The MD5 sum for the zip of MikG 1.04 is: fb81c61a19b5db6d4fa67acbfb17907f
When you run the MD5 check on the downloaded zip, it should match.
If it doesn't then the download is corrupted.
If it does match but you're still having issues flashing it, then there's a pretty good chance that it's the SD card. MicroSD cards are a dime a dozen nowadays so it should be pretty trivial to get some other card that you can pop in and try to flash with.
I use ClockWorkMod on an HTC EVO 4G ( Rolls Eyes ),
I have been trying to install a more customized rom on my Evo and I cannot seem to do it.
-I'm Not New To Android Or Linux-
But I sometimes get a Status 7 Error or a " BAD " Error and cannot install any rom.
ANY IDEAS?!
jonahly said:
I use ClockWorkMod on an HTC EVO 4G ( Rolls Eyes ),
I have been trying to install a more customized rom on my Evo and I cannot seem to do it.
-I'm Not New To Android Or Linux-
But I sometimes get a Status 7 Error or a " BAD " Error and cannot install any rom.
ANY IDEAS?!
Click to expand...
Click to collapse
What rom are you installing? A status 7 error only occurs when there are problems with the updater-script, and i dont think any dev would release a rom with a faulty updater script
Check the md5sum of your downloaded file, and download over a hardline and transfer to your phone if needed because it may just be a bad download that corrupted your the updater-script
Also try flashing other roms, and what version of CWM are you using? Try smelkus-mod recovery
CNexus said:
What rom are you installing? A status 7 error only occurs when there are problems with the updater-script, and i dont think any dev would release a rom with a faulty updater script
Check the md5sum of your downloaded file, and download over a hardline and transfer to your phone if needed because it may just be a bad download that corrupted your the updater-script
Also try flashing other roms, and what version of CWM are you using? Try smelkus-mod recovery
Click to expand...
Click to collapse
Rom: I've been trying a few, they never really work at all.
I have tried flashing others.
5.0.2.2 ( Unless I forgot )
jonahly said:
Rom: I've been trying a few, they never really work at all.
I have tried flashing others.
5.0.2.2 ( Unless I forgot )
Click to expand...
Click to collapse
Switch over to smelkus-mod and see if that fixes it
Did you check the md5sums and they line up?
The problem is in your opening sentence; Clockwork Mod. Read my guide in my signature. It'll tell you all you need to know
From the Hip-Phone
The Status 7 Error is not a script error either. It is an error installing the boot.img. This has become an ever more popular error on the evo. If you check you recovery log it will show everything installed fine until it got to the boot.img install and then it errors out. So please lets stop calling it something it is not.
jlmancuso said:
The Status 7 Error is not a script error either. It is an error installing the boot.img. This has become an ever more popular error on the evo. If you check you recovery log it will show everything installed fine until it got to the boot.img install and then it errors out. So please lets stop calling it something it is not.
Click to expand...
Click to collapse
It means that something went wrong with the updater-script, not necessarily that something is an error in the script itself, no ones calling it something that its not
im not a noob and never had thid problem in years. i installed twrp through goo mananger. The weird thing is it installs kernels just fine, but not a rom, any ideas? please help
Luthien1 said:
im not a noob and never had thid problem in years. i installed twrp through goo mananger. The weird thing is it installs kernels just fine, but not a rom, any ideas? please help
Click to expand...
Click to collapse
What error does it give when it fails to flash a ROM? What ROM are you trying to flash?
lordcheeto03 said:
What error does it give when it fails to flash a ROM? What ROM are you trying to flash?
Click to expand...
Click to collapse
it says e error, its very strange, i tried installing cwm and that recovery wont even let me make a backup, this is terrible uhhh... sorry it just says E: error and doesnt say anything else
Luthien1 said:
it says e error, its very strange, i tried installing cwm and that recovery wont even let me make a backup, this is terrible uhhh... sorry it just says E: error and doesnt say anything else
Click to expand...
Click to collapse
It says E: error when you try to make a backup as well?
lordcheeto03 said:
It says E: error when you try to make a backup as well?
Click to expand...
Click to collapse
ok i had twrp through goo manager, and i was able to make backups and install kernels just finel but when i tried a rom such as infamous it gave me the error, so i tried to install through micro sd card, no luck same error something about it not being mounted. So, i installed cwm and tried to make a backup but then i ran out of space, so the backup failed, so i had to delete some stuff, now im trying to back up again, then i will try to install a rom with cwm
this is so strange, i didnt do anytihng out of the ordinary, i got root by chainfire, then installed goo manager, and then a custom kernel...the most viewed one right now, so i thought it was legit which im sure it is, then a rom..... to end the madness, then i keep getting errors, its so frustrating
Luthien1 said:
ok i had twrp through goo manager, and i was able to make backups and install kernels just finel but when i tried a rom such as infamous it gave me the error, so i tried to install through micro sd card, no luck same error something about it not being mounted. So, i installed cwm and tried to make a backup but then i ran out of space, so the backup failed, so i had to delete some stuff, now im trying to back up again, then i will try to install a rom with cwm
Click to expand...
Click to collapse
Ok, see, now that is getting to the meat. Try flashing another ROM... I understand you might just want Infamous, but try flashing another one just for testing purposes. I'm thinking you're one to add to the list of having a bad Infamous d/l.
lordcheeto03 said:
Ok, see, now that is getting to the meat. Try flashing another ROM... I understand you might just want Infamous, but try flashing another one just for testing purposes. I'm thinking you're one to add to the list of having a bad Infamous d/l.
Click to expand...
Click to collapse
i did i tried flashing jedi rom and that failed too, soo this is just weird
i got frusturated and said if i cant have a custom rom, ill debloat now im getting errors, im on my way to a bricked device
Luthien1 said:
i got frusturated and said if i cant have a custom rom, ill debloat now im getting errors, im on my way to a bricked device
Click to expand...
Click to collapse
I may be overboard with my suggestion, but it wouldn't hurt to Odin back to 100% stock and restart your journey.
now it says E cant open/sdcard/o/download/jedi(bad)
Luthien1 said:
now it says E cant open/sdcard/o/download/jedi(bad)
Click to expand...
Click to collapse
Before you Odin back; are you still able to successfully flash any of the kernels you've downloaded? Also, if you downloaded any of the ROMs onto your computer, try browsing through the zips real quick on your computer.
lordcheeto03 said:
Before you Odin back; are you still able to successfully flash any of the kernels you've downloaded? Also, if you downloaded any of the ROMs onto your computer, try browsing through the zips real quick on your computer.
Click to expand...
Click to collapse
yes i can install kernels just fine, just not roms... it says it cant open the zip file, so weird.....i think i need to odin completely back too
Luthien1 said:
yes i can install kernels just fine, just not roms... it says it cant open the zip file, so weird.....i think i need to odin completely back too
Click to expand...
Click to collapse
Slow down, re-group, you are NOT going to brick...
First off, lets try some things, my first would be try a different recovery, copy a rom you want to the internal sdcard, then try. Bet it works.
I had a issue like this also, day 2 of my g4, pull the battery for 5-10 min, it seems the recovery gets confused and it will error.
another item to try...check to make sure the md5 file size is correct. common mistake, people for get to do a check.
try these, if you have the same issues, odin back to stock and start over.
Good luck. Your welcome.
lordcheeto03 said:
I may be overboard with my suggestion, but it wouldn't hurt to Odin back to 100% stock and restart your journey.
Click to expand...
Click to collapse
Probably this...and a formatting of the internal storage couldn't hurt either to make sure everything is cleared out.
Hey I had same problem. Download through Firefox not reg browser. And for infamous use the last download link
Goomanger gave me 3 bad downloads. To test this theory try and open the zip through a file manager, it probably won't let you because of bad download.. Happened to me 4 times but stopped using stock browser to download those files and has been working ever since
Sent from my SGH-M919 using XDA Premium HD app
---------- Post added at 10:54 AM ---------- Previous post was at 10:50 AM ----------
Also if you can't flash most things from more than 1 recovery still(happened to me when first got my gs4) I did Odin again but used 2.5.0.2 twrp and everything fixed as well. I recently was having the problem you have now and my first suggestion fixed it
Sent from my SGH-M919 using XDA Premium HD app
so, thank you everyone for your replys in this matter. I did odin back to stock and guess what, i got stuck at the splash screen for t mobile. This never happened before with odin, it always worked 100 percent, this is the first time i odined back to stock and it broke my phone, so weird. So, im going to try again. I wil def use firefox next time, and twrp you said the latest is having problems?
Luthien1 said:
so, thank you everyone for your replys in this matter. I did odin back to stock and guess what, i got stuck at the splash screen for t mobile. This never happened before with odin, it always worked 100 percent, this is the first time i odined back to stock and it broke my phone, so weird. So, im going to try again. I wil def use firefox next time, and twrp you said the latest is having problems?
Click to expand...
Click to collapse
Might want to thank people for the effort...there is a thanks button
get into recovery now, and do a factory reset, flash the correct kernel for your device, it will boot.
T989 without any SD card in it, the one I had died apparently new one on order. Went to flash the latest PA rom but kept getting error 7 using CWM. I updated my recovery to the latest TWRP and still will not flash. I tried updating to the newest radio UVMC6, but that wont flash. I am currently on CM10.1 nightly. My process for flashing is recovery, superwipe, flash, which is when the flash errors out and I re wipe and then I can flash my CM10 back on. So I can flash CM10 all day long but nothing else. I searched on here and found that the ATT version of this phone has this problem and you have to flash an AOKP and then flash whatever you want, other phones with similar problems say use ODIN and flash stock and then go from there. I am just looking for any advice on this situation. I could not find anything specific enough in my search to help me and I am hoping someone here can. Thanks in advance.
Note: I have also tried flashing CM10.1 RC5 and has the same problems.
moebawlz said:
T989 without any SD card in it, the one I had died apparently new one on order. Went to flash the latest PA rom but kept getting error 7 using CWM. I updated my recovery to the latest TWRP and still will not flash. I tried updating to the newest radio UVMC6, but that wont flash. I am currently on CM10.1 nightly. My process for flashing is recovery, superwipe, flash, which is when the flash errors out and I re wipe and then I can flash my CM10 back on. So I can flash CM10 all day long but nothing else. I searched on here and found that the ATT version of this phone has this problem and you have to flash an AOKP and then flash whatever you want, other phones with similar problems say use ODIN and flash stock and then go from there. I am just looking for any advice on this situation. I could not find anything specific enough in my search to help me and I am hoping someone here can. Thanks in advance.
Note: I have also tried flashing CM10.1 RC5 and has the same problems.
Click to expand...
Click to collapse
For onw those superwipe scripts are not needed with twrp, u might be getting the error from that, are u trying to flash from internal SD card since ur external died? That might cause it but I don't think so, I would suggest trying a manual wipe of all partitions, data, system, cache, dalvik, 2x , then flash, if that doesn't work try using Odin, go back to stock and start over, that should fix it definetly
Sent from my SGH-T989 using xda premium
soupysoup said:
For onw those superwipe scripts are not needed with twrp, u might be getting the error from that, are u trying to flash from internal SD card since ur external died? That might cause it but I don't think so, I would suggest trying a manual wipe of all partitions, data, system, cache, dalvik, 2x , then flash, if that doesn't work try using Odin, go back to stock and start over, that should fix it definetly
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Thank you... I wasnt sure about superwipe on TWRP since I just put it on and came from CWM. I am trying to flash from the internal card and the new external card will be at my doorstep tomorrow so I will drop that in as well. I will drop back in once I get all this done and hopefully all goes well.
Again thanks.
moebawlz said:
Thank you... I wasnt sure about superwipe on TWRP since I just put it on and came from CWM. I am trying to flash from the internal card and the new external card will be at my doorstep tomorrow so I will drop that in as well. I will drop back in once I get all this done and hopefully all goes well.
Again thanks.
Click to expand...
Click to collapse
Good glad I can help, let me know how it all goes, now I'm interested lol
Sent from my SAMSUNG-SGH-T989 using xda premium
Ok so I got my new SD card. Tossed that in, just figured I would try flashing from the external, no luck there. Same issues.
Odin back to stock using this tutorial http://forum.xda-developers.com/showthread.php?t=1513359&page=3
Used http://forum.xda-developers.com/showthread.php?t=2195283 this to regain root.
Got CWM back on but now I cannot flash SuperUser
When I go to flash Superuser it says
Mounting System
Deleting System:bin/su...
Deleting System:xbin/su
Extracting files to SYSTEM
Setting SYSTEM:bin/su permissions to 06755...
Creating SYSTEM:xbin/su symbolic link...
E: Error in /emmc/Superuser-3.0.7-efghi-signed.zip
(Status 0)
Installation aborted
So on the plus side I didn't brick the phone... downside now I am back to Gingerbread and currently stuck here...
Possibly a bad zip file?
Any ideas on this?
Quick update... I am a moron... Did not realize that root is kept with this restore... Got Superuser from market and am good to go.
Installing TWRP now and will have an update on the flash soon.
OK... the fun seems to have just begun
I cannot install TWRP from GooManager. No clue why, looking on here and I found //techerrata.com/browse/twrp2/hercules (cant link too new of a member)
So as it seems I can download the .img and GooManager should see it and if that doesnt happen I can install it through the terminal with these commands
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
OR flash it with ODIN... Which I would assume I get the .tar file and follow the same process as putting the recovery files in?
Aside from TWRP being an issue, I tried installing the PA rom with CWM and I got this:
Installing update
set_perm:some changes failed
E:Error in /sdcard/pa_hercule...zip
(Status 7)
Installation aborted
The same error I had in the first place
moebawlz said:
OK... the fun seems to have just begun
I cannot install TWRP from GooManager. No clue why, looking on here and I found //techerrata.com/browse/twrp2/hercules (cant link too new of a member)
So as it seems I can download the .img and GooManager should see it and if that doesnt happen I can install it through the terminal with these commands
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
OR flash it with ODIN... Which I would assume I get the .tar file and follow the same process as putting the recovery files in?
Aside from TWRP being an issue, I tried installing the PA rom with CWM and I got this:
Installing update
set_perm:some changes failed
E:Error in /sdcard/pa_hercule...zip
(Status 7)
Installation aborted
The same error I had in the first place
Click to expand...
Click to collapse
I'm not sure what your overall problem is, but if you are going to install TWRP do not use Goo Manager or the img file. They have been messing up peoples phones. Odin the tar or try the zip from the TWRP thread.
meekrawb said:
I'm not sure what your overall problem is, but if you are going to install TWRP do not use Goo Manager or the img file. They have been messing up peoples phones. Odin the tar or try the zip from the TWRP thread.
Click to expand...
Click to collapse
Well that could be a problem... I just got GooManager to do what I wanted it to do before I saw this message. If I overwrite it with the tar will that be ok or am I better off starting this process over and Odin back to factory stock again?
Along with that after I got TWRP working through Goo Manager again I tried flashing PA again and I had the same error as I did in the first place.
Maybe my phone just hates anything but the nightly I had before...
moebawlz said:
Well that could be a problem... I just got GooManager to do what I wanted it to do before I saw this message. If I overwrite it with the tar will that be ok or am I better off starting this process over and Odin back to factory stock again?
Click to expand...
Click to collapse
If you can boot into TWRP, then they must have fixed the Goo problem.
It seems like you have tried most everything. Maybe you should Odin back to stock. If you are comfortable doing it, that is.
i went to flash with goo last night and it bricked the phone kind of, i had to ODIN and reflash the CWM again and bam the phone rebooted no problem
meekrawb said:
If you can boot into TWRP, then they must have fixed the Goo problem.
It seems like you have tried most everything. Maybe you should Odin back to stock. If you are comfortable doing it, that is.
Click to expand...
Click to collapse
I did Odin back to stock before. I am still on stock gingerbread right now with root access and am getting the errors I have been. I followed the tutorials in the sticky thread that I posted before that got me back to stock.
Within TWRP I tried installing the newest Cyanogen Mod and got
E:Error executing updater binary in zip
Error flashing zip
When I try installing the PA rom I get the same error
Any thoughts? Would going back to stock through Odin and doing this again potentially fix it? or is that a shot in the dark?
Lucky for me I kept a backup saved on my PC from before I did anything here. So I am back to the CM 10.1 Nightly I started on for the time being.
Is there any other method of flashing a rom that I might be able to try?
moebawlz said:
I did Odin back to stock before. I am still on stock gingerbread right now with root access and am getting the errors I have been. I followed the tutorials in the sticky thread that I posted before that got me back to stock.
Within TWRP I tried installing the newest Cyanogen Mod and got
E:Error executing updater binary in zip
Error flashing zip
When I try installing the PA rom I get the same error
Any thoughts? Would going back to stock through Odin and doing this again potentially fix it? or is that a shot in the dark?
Click to expand...
Click to collapse
It would be a shot in the dark. I did a Google search for your error and a couple of people said they were able to fix it by using TWRP 2.3. That was for different phones though. Maybe try that before going stock.
I am by no means a pro at this and am still learning as I go. Just to make sure of what I am doing, can I Odin TWRP 2.3? I also found this
http://forum.xda-developers.com/showthread.php?t=1639673
or
http://forum.xda-developers.com/showthread.php?t=1658418
Just a thought here... I keep gettin emmc errors... I was reading about upgrading and downgrading TWRP through the Terminal Emulator and it said use emmc or sdcard depending on what the phone reads it as.
When I first got the phone i recall seeing emmc when i would go into any file browser. Now it just says sdcard0 (internal) & sdcard1 (external)
So how can I get recovery to stop looking for emmc and start looking for sdcard0?
Unless I am way off in left field here with this.
moebawlz said:
I am by no means a pro at this and am still learning as I go. Just to make sure of what I am doing, can I Odin TWRP 2.3?
Click to expand...
Click to collapse
Yes, use Odin and the 2.3.3.0 tar from the techerrata website. I like using the Odin method because I have never had a problem upgrading recovery that way. I don't know about the emmc errors because I have only used the dd method like twice.
Edit: Maybe your internal memory is corrupted? I'm not sure how to test for that though.
moebawlz said:
Well that could be a problem... I just got GooManager to do what I wanted it to do before I saw this message. If I overwrite it with the tar will that be ok or am I better off starting this process over and Odin back to factory stock again?
Along with that after I got TWRP working through Goo Manager again I tried flashing PA again and I had the same error as I did in the first place.
Maybe my phone just hates anything but the nightly I had before...
Click to expand...
Click to collapse
I think u must be getting bad DL then because none of that sounds right lol, if u got twrp to load into your device and all is working fine then the only other option is a bad DL, try checking the DL with a root browser or something to see the size of the file, status 7 errors are from the zip, usually bad install script in the ROM, which could be caused by a bad DL, check the DL size and let me know
Sent from my SGH-T989 using xda premium
went back to 2.3.3 and still having the same error.
Is there a way to correct any possible errors in my internal memory?
moebawlz said:
went back to 2.3.3 and still having the same error.
Is there a way to correct any possible errors in my internal memory?
Click to expand...
Click to collapse
If the DL is good, I don't know what else to tell u that is very strange indeed, but interesting too, I've never not been able to install at all, I'm curious..
Sent from my SGH-T989 using xda premium