Related
Hi all. I am a noob at this rooting and flashing business, and I probably did something stupid so bear with me.
The other night I rooted my Evo with Unrevoked. That same night I flashed Baked Snack 1.9 using ROM Manager. Prior to the flash, I backed up my phone using ROM Manager. It was fast and everything but I decided I wanted Gingerbread (a la Salvagemod). I backed up my phone in a similar fashion, and flashed the ROM once using ROM Manager. When rebooting, my phone became caught in a boot loop. After searching through Google for a few minutes, I learned that I simply needed to clear my cache and my dalvik cache. After clearing cache, flashing, and attempting to boot several times (all in clockworkmod... or recovery... or whatever it is called (yeah i suck)...or whichever one is orange!), I gave up and decided to restore to my second ROM Manager backup - that of Baked Snack. Error! "No files found!" I tried my previous backup. Same message.
Looking back on that, I chose "install zip from sdcard" instead of "nandroid". That was a fail.
So I decided to re-use unrevoked. Everything went fine on the PC end, but the only thing that changed on my phone, is that when it boots, it gets stuck on "htc evo" in the white screen. That and clockworkmod is now teal. I disovered the nandroid option on the recovery menu. I navigate to that, then to restore, then to my Baked Snack backup. This gave me the message "Error while flashing boot image". I tried it one more time, except instead of picking recover, I accidentally picked backup (stupid stupid careless, i know). It failed and said "Can't mount /data/!".
Then I decided to go onto xda-developers and here I am now. If you are through facepalming, I would appreciate it if anybody could help me recover my data. I believe I can still flash a completely new ROM (But what do I know? I haven't proven to be the smartest Android guy), and I don't know about you guys, but I like keeping my data.
So, uh, yeah. That's that. Help please.
I'm sorry to hear you are having issues with your phone. It looks like you still have a nandroid backup, unless you formated your SDcard. Clear data, dalvik cache, and cache then run do a restore. When using clockworks recovery clear out the data, dalvik, and cache three times.
Hope this helps.
I have performed all three wipes. After that it reads
Code:
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Error while flashing boot image!
Same as before... Any thoughts? Could the boot.img file be corrupted?
***bump***
Edit: Ive read around some more and heard 2 things. 1) If I just try recovering over and over again, nandroid will eventually give in. 2) the battery has to be 70% or higher or nandroid will just keep giving error messages.
Either way, I'll juice up my battery and report back later.
Have you tried to just do a wipe and reflash the ROM.
Have you tried to use Amon recovery? That seems to work better than clockworks. You can get that here: http://forum.xda-developers.com/showthread.php?t=705026
bccbryan said:
Have you tried to just do a wipe and reflash the ROM.
Click to expand...
Click to collapse
Yes. I tried it again just now because I was feeling lucky. Salvage Mod went smoothly, except it got stuck on the white htc screen when I rebooted. Baked Snack gave me an error message:
Code:
E:Can't open /sdcard/download/BakedSnack1.9.evo.zip
(bad)
Installation aborted
Have you tried to use Amon recovery? That seems to work better than clockworks. You can get that here: http://forum.xda-developers.com/showthread.php?t=705026
Click to expand...
Click to collapse
I'll try that tomorrow morning. Right now I'm gonna get some sleep before I do any more damage to my phone lol. Expect more questions from me about WiMAX and what to do with that .img file (if anything at all).
Do you have the latest radio/wimax? If not run Calkulin radio combo. http://forum.xda-developers.com/showthread.php?t=715485
I believe if you don't update your radio and are running a certain kernel you will get a bootloop, but don't quote me on that.
Does Hboot say s-off or s-on? Here is a rooting info and faqs. http://forum.xda-developers.com/showthread.php?t=865204
bccbryan said:
Do you have the latest radio/wimax? If not run Calkulin radio combo. http://forum.xda-developers.com/showthread.php?t=715485
Click to expand...
Click to collapse
I'm 95% sure that I do, I got my EVO in December.
Does Hboot say s-off or s-on? Here is a rooting info and faqs. http://forum.xda-developers.com/showthread.php?t=865204
Click to expand...
Click to collapse
It says S-OFF, so that's good news.
And as to Amon_RA, because I'm doing "the bootloader way", then I don't need the recovery-RA-supersonic-v2.3.img file?
When I try to recover, it givese me an error saying that the nandroid directory could not be found. I have my backups in a folder called /sdcard/clockworkmod/backup/NameOfTheRecoveryFolder/. Should I just copy the files in the backup folder to a folder on the root of the card called "nandroid"?
And as to Amon_RA, because I'm doing "the bootloader way", then I don't need the recovery-RA-supersonic-v2.3.img file?
Click to expand...
Click to collapse
Yep...just need the PC36IMG.zip and boot to the bootloader.
Since you got your phone last December I think you need to run a rom that is based off the latest code. If you are running htc sense it should be based off 3.70.651.1. For ASOP run the lastest ones.
Here is a nice wiki of the ROMs for the EVO http://forum.xda-developers.com/wiki/index.php?title=HTC_Supersonic/ROMs
Forgot to mention for the zip files you place on your sdcard for flashing check the MD5 hash before flashing your phone.
When I got my EVO the SD card went bad in about 2 months. Fortunately for me Sprint was nice enough to replace my sdcard. Since, then I have upgraded my sdcard to a 32GB sandisk.
bccbryan said:
Forgot to mention for the zip files you place on your sdcard for flashing check the MD5 hash before flashing your phone.
When I got my EVO the SD card went bad in about 2 months. Fortunately for me Sprint was nice enough to replace my sdcard. Since, then I have upgraded my sdcard to a 32GB sandisk.
Click to expand...
Click to collapse
This would be the file called "nandroid.md5"? I'm confused.
OK so I boot into recovery, go to Nandroid restore > BackupName
I am presented with a list of options:
boot.img
recovery.img
wimax.HT0CRHL08393.img
system.img
data.img
cache.img
nandroid.md5
Do I just run each of these individually or am I doin it wrong?
Don't do a nandroid restore. Flash a ROM onto your phone.Fresh EVO or Myn’s Warm TwoPointTwo are good ones to try.
Works great! I lost all my data but I'd rather have a wiped phone than a dead one!
Thanks!
When you used Unrevoked to root your phone it also downloaded Clockwork Mod recovery v. 2.6.0.1. This is what you probably used to do your original backup right after you rooted your phone (http://forum.xda-developers.com/showthread.php?t=895208). You need to go back to this version so you can restore any backups you may have made right after you rooted your phone. Here is an article by Koush explaining why you may be having problems. At the bottom he has v.2.6.0.1. Install it on your phone and then proceed restoring your backup.
Also, I'm going to suggest to you that you read the articles below to get you familiar with rooting, and then I suggest you read some more on these and other forums. Learn the rooting vocabulary and processes involved (rooting, nandroid backup, recoveries, flashing ROMs, kernels, etc.). Also, try and read up on problems people have rooting, flashing ROMs, and troubleshooting should something go wrong. You want to be able to get yourself out of a mess should problems arise. Most importantly, you want to know what you're doing so you don't brick your phone.
http://forum.xda-developers.com/showthread.php?t=865204
http://forum.xda-developers.com/showthread.php?t=790427
http://forum.xda-developers.com/showthread.php?t=881747
http://htcevorooting.x10.mx/wiki/ind...itle=Main_Page
http://androidforums.com/evo-4g-all-...g-dummies.html
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.
Hi there, I'm new to the forum but have been rooting for about a year. Here is my problem...
I was running stock firmware on my SGS3 and went through the standard cm10 root/rom install process. I flashed CMW with Odin, booted to recovery, installed cm10, jb gapps, cleared cache and delvik cache and rebooted. All the above processes worked fine and once it boots into JB, nothing seems to work. My home button does nothing, the top status bar is blank, no wifi, no keyboard (the process just crashes when I attempt to type).
I know this isn't an issue with CM10 on the SGS3 as this works for most people but does anyone have any ideas on how to remedy this? This may be a unique issue as I can't seem to find anyone else experiencing this.
Also...
I should also mention that I've tried a restore in recovery, reinstalled cm10, blah blah blah, and same results. I've also tried the cm10.m2 roms with the identical results. After reboot I don't even get the welcome wizard. It just boots right into the blank, default JB home screen and starts popping up process failure errors. I can navigate around (though the home button doesn't work) but can't use the keyboard etc.
Am I missing something? Is there a way for me to do a clean restore and try again?
Some technical info:
ClockworkMod Recovery v5.8.4.7
cm-10.0.0-d2att.zip
gapps-JB-20121130-signed.zip
Did you do a complete wipe? Data, cache, Davlik , System and then install cm10.
Coming from stock you need to fully wipe.
Sent from my SAMSUNG-SGH-I747 using xda premium
Machoscrawn said:
I should also mention that I've tried a restore in recovery, reinstalled cm10, blah blah blah, and same results. I've also tried the cm10.m2 roms with the identical results. After reboot I don't even get the welcome wizard. It just boots right into the blank, default JB home screen and starts popping up process failure errors. I can navigate around (though the home button doesn't work) but can't use the keyboard etc.
Am I missing something? Is there a way for me to do a clean restore and try again?
Some technical info:
ClockworkMod Recovery v5.8.4.7
cm-10.0.0-d2att.zip
gapps-JB-20121130-signed.zip
Click to expand...
Click to collapse
Your clockworkMod is out of date to run CM10 & the gapps. Upgrade to the latest clockwork mod, then the latest CM then the latest Gapps and you should be good to go.
dynamiclynk said:
Did you do a complete wipe? Data, cache, Davlik , System and then install cm10.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Thanks for the reply. This is what I did...
(Main cwm menu) -wipe cache partition
(Advanced) -wipe dalvik cache
+++go back+++
-reboot system now
Is there something additional I should clear?
Kweli87 said:
Your clockworkMod is out of date to run CM10 & the gapps. Upgrade to the latest clockwork mod, then the latest CM then the latest Gapps and you should be good to go.
Click to expand...
Click to collapse
Thanks for the reply,
How do i update to the latest clockworkMod? Do you happen to have a URL? I think I found the latest 6.something, but they all seem to be in .iso format.
You can't go from stock rom to CM10 without clearing factory reset thing in CWM.. I don't know the exact text string it uses but it should be right on top of clearing cache.. It looks like you only cleared cache and flashed a new rom.
i386W7 said:
You can't go from stock rom to CM10 without clearing factory reset thing in CWM.. I don't know the exact text string it uses but it should be right on top of clearing cache.. It looks like you only cleared cache and flashed a new rom.
Click to expand...
Click to collapse
Sorry I may have missed mentioning that. The first thing I did was the -factory restore/reset
If updating CWM doesn't help, I'd recommend re-downloading the CM10 zip and verifying the MD5 hash. It could be that the download got corrupted somehow...
goodtimes50 said:
If updating CWM doesn't help, I'd recommend re-downloading the CM10 zip and verifying the MD5 hash. It could be that the download got corrupted somehow...
Click to expand...
Click to collapse
Two questions:
1) What is the best way for me to update cwm?
2) I've seen this MD5 hash recommendation here and there. I have no idea what that means. How would I "verify the MD5 hash".
Machoscrawn said:
Two questions:
1) What is the best way for me to update cwm?
2) I've seen this MD5 hash recommendation here and there. I have no idea what that means. How would I "verify the MD5 hash".
Click to expand...
Click to collapse
Flash one of the rooted stock ROMs. Preferably an ICS one since you are on an older cwm. Wipe data, cache, dalvik. Download ROM manager from the play store. Update your recovery to the latest through that. Than flash back to cm10.
BAM1789 said:
Flash one of the rooted stock ROMs. Preferably an ICS one since you are on an older cwm. Wipe data, cache, dalvik. Download ROM manager from the play store. Update your recovery to the latest through that. Than flash back to cm10.
Click to expand...
Click to collapse
Ok thanks! I'm going to give that a shot and see how it goes.
Machoscrawn said:
Ok thanks! I'm going to give that a shot and see how it goes.
Click to expand...
Click to collapse
Ok so I tried flashing a stock rooted ICS ROM and now I'm stuck on the Samsung logo boot screen. Here is the method I tried, using Odin. http://forum.xda-developers.com/showthread.php?t=1739426
I used the "Bell Image (This works with Canadian Virgin Mobile SGH-I747M) - Old Image I747MVLALH1 (ICS 4.0.4)"
After flashing I booted into the stock recovery and cleared the cache partition then rebooted. Still stuck on the Samsung boot screen.
UPDATE: I just let it sit on the Samsung logo boot screen and it eventually loaded into ICS.
Machoscrawn said:
Two questions:
1) What is the best way for me to update cwm?
2) I've seen this MD5 hash recommendation here and there. I have no idea what that means. How would I "verify the MD5 hash".
Click to expand...
Click to collapse
1) I believe Rom Manager (from the Play Store) can do this.
2) Basically an MD5 value is generated when the file is created and is usually listed on the download page (on get.cm look for "md5sum" right under the download link for each build). There are apps that create an MD5 value from the file that you download and compare against the original to ensure that it's intact. If the values don't match, something's wrong with the file. Check out FastSum (there are lots of others out there too).
goodtimes50 said:
1) I believe Rom Manager (from the Play Store) can do this.
2) Basically an MD5 value is generated when the file is created and is usually listed on the download page (on get.cm look for "md5sum" right under the download link for each build). There are apps that create an MD5 value from the file that you download and compare against the original to ensure that it's intact. If the values don't match, something's wrong with the file. Check out FastSum (there are lots of others out there too).
Click to expand...
Click to collapse
Ok cool. Well i have downloaded ROM Manager but when I try to flash the latest recovery and it gives me a list of devices, mine isn't there. The only S3 listed is "Galaxy S3 (MetroPCS)". The list itself looks incomplete, maybe only 20 devices listed. I've rebooted the phone since installing ROM Manager but the list still only shows the one SGS3.
Machoscrawn said:
Ok cool. Well i have downloaded ROM Manager but when I try to flash the latest recovery and it gives me a list of devices, mine isn't there. The only S3 listed is "Galaxy S3 (MetroPCS)". The list itself looks incomplete, maybe only 20 devices listed. I've rebooted the phone since installing ROM Manager but the list still only shows the one SGS3.
Click to expand...
Click to collapse
Try to download GooManager and select the Flash Roms option, it will prompt you, select *Find one for me* reboot into recovery try to wipe/reset and reinstall the ROM and gapps and see if it works
wally3614 said:
Try to download GooManager and select the Flash Roms option, it will prompt you, select *Find one for me* reboot into recovery try to wipe/reset and reinstall the ROM and gapps and see if it works
Click to expand...
Click to collapse
Ok I tried the Goomanager route. When I'm in recovery doing the install of the rom, I get a FAILED error right after it tries updating partition... I've tried installing from internal and external sd with the same results...
I've attached a screenshot. Well I attempted to with my webcam, hopefully it's semi-readable.
Machoscrawn said:
Ok I tried the Goomanager route. When I'm in recovery doing the install of the rom, I get a FAILED error right after it tries updating partition... I've tried installing from internal and external sd with the same results...
I've attached a screenshot. Well I attempted to with my webcam, hopefully it's semi-readable.
Click to expand...
Click to collapse
Well at least you have the proper twrp definitely try and re download the ROM, carefully make sure it is absolutely the correct ROM(I rushed once, thought I was sure n dl'd the wrong one and bricked my older s3) if u have the slightest break during DL this can happen. I KNOW it is frustrating but worth it in the end
wally3614 said:
Well at least you have the proper twrp definitely try and re download the ROM, carefully make sure it is absolutely the correct ROM(I rushed once, thought I was sure n dl'd the wrong one and bricked my older s3) if u have the slightest break during DL this can happen. I KNOW it is frustrating but worth it in the end
Click to expand...
Click to collapse
Alright, I downloaded the latest stable (the only one) build of CM 10 from get.cm. Removed the current version from my internal sd and tried the process again. Same error...
So again, I'm now using GooManager, TeamWin Rocovery v2.3.1.0, CM10 Stable. Doing a factory reset, then wiping system, then install cm10, this is where it fails.
Any way that I can restore everything on my phone completely to stock and start from scratch? Anything else you/anyone can recommend?
Machoscrawn said:
Alright, I downloaded the latest stable (the only one) build of CM 10 from get.cm. Removed the current version from my internal sd and tried the process again. Same error...
So again, I'm now using GooManager, TeamWin Rocovery v2.3.1.0, CM10 Stable. Doing a factory reset, then wiping system, then install cm10, this is where it fails.
Any way that I can restore everything on my phone completely to stock and start from scratch? Anything else you/anyone can recommend?
Click to expand...
Click to collapse
If youre looking to completely start over. Just grab an unrooted stock .tar from one of the links somewhere around here, put your phone in download mode and let it flash. Clean slate.
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
I was attempting to flash a clean copy of SkyNote Air with the 3.5 update and came across a problem when wiping the internal storage using TWRP. I've noticed this error previously when wiping the cache to install an update, but everything worked fine. When attempting to wipe the internal storage, I received a failed message. I went ahead and flashed the ROM and update, but I am now encountering a Play Store error (-24) when trying to download apps that were previously on my phone. I've researched this error and have been able to delete the previous data files using a root browser. However, I am unable to erase the folder that was causing the error (turns out that it was Battery Doctor) by using the root browser. The app attempts to erase the folder, but never does. So now I am stuck with no way to wipe the internal storage to get a clean flash of this ROM. I'm pretty sure this problem is not associated with the SkyNote ROM, so I wanted to see if I could get help here first. Thanks in advance! I have attached a picture of the error messages I was getting in TWRP.
mjt010 said:
I was attempting to flash a clean copy of SkyNote Air with the 3.5 update and came across a problem when wiping the internal storage using TWRP. I've noticed this error previously when wiping the cache to install an update, but everything worked fine. When attempting to wipe the internal storage, I received a failed message. I went ahead and flashed the ROM and update, but I am now encountering a Play Store error (-24) when trying to download apps that were previously on my phone. I've researched this error and have been able to delete the previous data files using a root browser. However, I am unable to erase the folder that was causing the error (turns out that it was Battery Doctor) by using the root browser. The app attempts to erase the folder, but never does. So now I am stuck with no way to wipe the internal storage to get a clean flash of this ROM. I'm pretty sure this problem is not associated with the SkyNote ROM, so I wanted to see if I could get help here first. Thanks in advance! I have attached a picture of the error messages I was getting in TWRP.
Click to expand...
Click to collapse
What version of TWRP ?
dicksteele said:
What version of TWRP ?
Click to expand...
Click to collapse
v2.6.3.1
mjt010 said:
v2.6.3.1
Click to expand...
Click to collapse
Is battery doctor still running? Just a guess, maybe go to application manager and do a force stop on it.
Then try and delete it.
dicksteele said:
Is battery doctor still running? Just a guess, maybe go to application manager and do a force stop on it.
Then try and delete it.
Click to expand...
Click to collapse
Thanks for the suggestion. I am unable to install it on this new flash. The folder that I was trying to delete is left over from the previous ROM. There is nothing in the folder, but I still cannot delete it and it continues to give me that same error message.
mjt010 said:
Thanks for the suggestion. I am unable to install it on this new flash. The folder that I was trying to delete is left over from the previous ROM. There is nothing in the folder, but I still cannot delete it and it continues to give me that same error message.
Click to expand...
Click to collapse
So the folder is under /data/app or /system/app ? Or ????
dicksteele said:
So the folder is under /data/app or /system/app ? Or ????
Click to expand...
Click to collapse
When going through root browser, it is data/data/com.ijinshan,kbatterydoctor_en. I have cleared out all of the folders I could, but there is one folder that remains titled shared_prefs with an unnamed folder inside with no contents. That is the only thing still associated with that app but something is causing that error in recovery and preventing the full wipe.
mjt010 said:
When going through root browser, it is data/data/com.ijinshan,kbatterydoctor_en. I have cleared out all of the folders I could, but there is one folder that remains titled shared_prefs with an unnamed folder inside with no contents. That is the only thing still associated with that app but something is causing that error in recovery and preventing the full wipe.
Click to expand...
Click to collapse
Maybe try Philz recovery. You can copy to external card. Flash, reboot to recovery from TWRP.
Worth a shot....
Been a long day, can only think of easy sh*t to try.
Bump
Sent from my SAMSUNG-SGH-I317 using Tapatalk
I had something like that happen on my T889. I was running 2.7.0.0 and something got corrupted between a 4.1 rom and 4.3 with a backup and restore thrown in.
I ended up wiping my phone a couple times and odin flashing the last 4.1.2 rom (I still have the non-Knox bootloader).
Nothing worked. I ended up flashing the very first release firmware via Odin 2x times. I believe that it reset the partitions. I was then able to flash twrp 2.7.0.0 and then Jedi Master X to an intact file system.
Ir was kinda hairy for about 2 hrs though. Started a minor modified freak out for a minute...
Hastily spouted for your befuddlement