I used this SPH-L710_ND8_Full Restore_UNROOTED (Compressed Archive).exe
to update my gs3 to ND8. then I Odin PhilZ Touch recovery and used re-root
Rebooted downloaded supersu from play store ran and updated. Used root checker to verify root. all ok
Now flashing new rom. Problems
Wicked X would flash but not boot up
Spirit would flash and boot but not the gapps. When I try to flash the gapps would get a permission error and not flash.
Any ideas would be helpful even if it is "search" please tell me where.
In have you verified md5 of your Wicked X download? Are you using the KK gapps with Spirit? When you flashed Wicked X did you first wipe cache, dalvik, and then wipe for new ROM in Philz before flashing?
mattzeller said:
In have you verified md5 of your Wicked X download? Are you using the KK gapps with Spirit? When you flashed Wicked X did you first wipe cache, dalvik, and then wipe for new ROM in Philz before flashing?
Click to expand...
Click to collapse
Did not check md5 (Never learned how). Using the PA-Apps found in the OP for Spirit. Wiped everything I found to wipe in PhilZ before flashing all ROMs.
inunishi said:
Did not check md5 (Never learned how). Using the PA-Apps found in the OP for Spirit. Wiped everything I found to wipe in PhilZ before flashing all ROMs.
Click to expand...
Click to collapse
Download an md5 checking app from the Play Store. When you download a ROM, load it into the md5 checking app to generate the md5 and then check and see if it matches what it's supposed to be. If they don't match it means it was a bad download and can cause all kinds of funky problems when flashed, like not booting. As far as gapps go any of the KitKat should work, I personally use slimgapps and I haven't had a problem.
mattzeller said:
Download an md5 checking app from the Play Store. When you download a ROM, load it into the md5 checking app to generate the md5 and then check and see if it matches what it's supposed to be. If they don't match it means it was a bad download and can cause all kinds of funky problems when flashed, like not booting. As far as gapps go any of the KitKat should work, I personally use slimgapps and I haven't had a problem.
Click to expand...
Click to collapse
all md5 are a match. I noticed that I get a error in philZ with flashing some zips:
E: unknown error (file name) {sd-ext}
or something like that. Looks like some zips are looking for an E folder on an ext-sd. any ideas?
inunishi said:
Did not check md5 (Never learned how). Using the PA-Apps found in the OP for Spirit. Wiped everything I found to wipe in PhilZ before flashing all ROMs.
Click to expand...
Click to collapse
in PhilZ recovery when you choose a zip file to flash before you press yes there will be a thin gray line that fills up with a blue color and when the line fills up it will show the MD5 of the file you chose now all you have to do is compare it to the one on the download page to see if they match
Related
Okay it's gotten to a pretty dire situation where I can't flash any Roms in recovery. I'm using CWM 3.0.2.6. This is what I try and do.
1.Full Wipe 1.5
2.Flash Rom
So far I tried it with ARHD 5.1.9 and Leedroid 3.1.3 and it starts flashing for no longer than 10 seconds then stops and says status 1 (or 7 I've seen) and aborted. I've had zero problems in the past flashing ext3 rom but ever since I tried to flash ARHD 5.1.8 from ARHD 3.5 it's been downhill
I think it's to do with the ext4 partitions. *don't use full wipe* - instead run the "partition /data as ext4" script and then flash the rom. Full wipe is for ext3 and ARHD is for ext4.
Otherwise just restore the nandroid you made before full wiping.
Thanks for the reply, how would I go about running that script in CWM. I have Mike's 'format_data_partition_EXT4' file. Also the Full Wipe I was using was 1.5 which says format to EXT4
double check downloaded rom's checksum - provided in the topic's op (md5).
u can use zip in cwm under install zip from sdcard menu.
letom said:
Okay it's gotten to a pretty dire situation where I can't flash any Roms in recovery. I'm using CWM 3.0.2.6. This is what I try and do.
1.Full Wipe 1.5
2.Flash Rom
So far I tried it with ARHD 5.1.9 and Leedroid 3.1.3 and it starts flashing for no longer than 10 seconds then stops and says status 1 (or 7 I've seen) and aborted. I've had zero problems in the past flashing ext3 rom but ever since I tried to flash ARHD 5.1.8 from ARHD 3.5 it's been downhill
Click to expand...
Click to collapse
Sent from my Desire HD using XDA App
Status 7
I had this when flashing Leedroid 3.1.3. Always got status 7 error. I tried the torrent and ftp downloads.
I checked the MD5 number on both files against the MD5 number on the developers site , and both downloads were corrupt.
Downloaded again and checked MD5 numbers and they matched. Flashed with that file and all worked fine.
Always check the MD5 before flashing.
Cheers
shovett said:
I had this when flashing Leedroid 3.1.3. Always got status 7 error. I tried the torrent and ftp downloads.
I checked the MD5 number on both files against the MD5 number on the developers site , and both downloads were corrupt.
Downloaded again and checked MD5 numbers and they matched. Flashed with that file and all worked fine.
Always check the MD5 before flashing.
Cheers
Click to expand...
Click to collapse
Thanks, I got that error too, I thought a corrupt file would be unlikely because it didn't work with LeeDroid too. How do I check the MD5 of the Rom I download?
Download an MD5 Checker, most ROM authors provide a MD5 which is like an electronic signature. If the MD5's match the file you downloaded is 1:1 copy of the file the ROM author uploaded.
You can find an MD5 checker on my site, just click my Signature and head to tools. Even MD5.exe has an MD5
I checked the MD5 to see if it matched and it did, so I imagine it has something do with EXT4. I've managed to flash TB Fusion and it runs very well and stable so I'll stick with that.
Thank you all for the help.
if you plan to use an ext3 rom, u should wipe using cwm not zip cause cwm does it to ext3. or use an ext3 based wiper.
letom said:
I checked the MD5 to see if it matched and it did, so I imagine it has something do with EXT4. I've managed to flash TB Fusion and it runs very well and stable so I'll stick with that.
Thank you all for the help.
Click to expand...
Click to collapse
Sent from my Desire HD using XDA App
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.
I just rooted and unlocked my note 2 and followed these steps
Step 1-
Wipe Data Factory Reset!
Step 2-
Wipe davlick cache
Step 3-
install zip and pick your options
Step 4-
Reboot and enjoy!
But it says if failed to open the zip what is wrong?
Try rebooting your recovery and flashing...this may be a TWRP feature.
Alternatively you may have a boken or corrupt ZIP. In which case, verify your MD5.
Skripka said:
Try rebooting your recovery and flashing...this may be a TWRP feature.
Alternatively you may have a boken or corrupt ZIP. In which case, verify your MD5.
Click to expand...
Click to collapse
I checked the md5 matches and the zip isnt broken because i am able to extract all files without any problems. I am gonna try another rom and see if that works.
Coldashes said:
I checked the md5 matches and the zip isnt broken because i am able to extract all files without any problems. I am gonna try another rom and see if that works.
Click to expand...
Click to collapse
jelly beans is not a sprint rom. it isnt going to work in the sprint gn2 without modification
I only know of build 5 of jellybeans ROM that mackentosh ported over for our sprint devices. You must be flashing a different carriers ROM like t3project has stated.
Sent from my SPH-L900 using xda premium
I've been wanting to upgrade my Tmobile S3 sgh-t999 to any of the 4.2 ROM that I could find in XDA, but when I tried to flash it from recovery, it always come back with "Installation aborted".
I tried upgrading to LiquidSmooth ROM, PAC-man ROM, CM10.1 and so on. still same.
I did place the zip files on my ext SD card and I'm able to see them when in recovery mode. I do wipe data, cache, dalvik and so on on each attempt, but still same..
If I did try with any of the new ROMs that required Google Apps to be flashed, if I would try flashing the Google app zip files first, that went successfully, but not the other zip file.
I'm a newbee, so I know I might be doing something wrong, although I have done upgrades before and was successful (but on Sprint phones)
My phone right now has 4.1.1 BUILD # JRO03L T999UVDLJA. Would it help if I go to STOCK rom for the upgrade? and which stock should I go down to if necessary?
Any suggestions?
I would check the zip file is good file first. check with MD5 checker to find out Maybe bad/incomplete download?
Or did you try reflashing recovery?
If you can flash gapps, I'm assuming you just need to verify that zip you downloaded.. Again I Can't see it so just an assumption..
Or start over by flashing stock and reroot it?
Sent from my SGH-T999 using xda premium
Your rom may be corrupted due to a bad download or your recovery may be out of date so I recommend redownloading the ROM, making sure it does complete and intended for your specific device, and if possible check for an MD5 sum on the ROM. Also, if on TWRP recovery (recommended) you may wanna download Goomanager from the Play Store and check to see if your recovery needs updating by tapping the menu key and selecting "Install openscript recovery". See if that helps bud.
Sent from my Galaxy Nexus using xda premium
Your recovery could be out of date, check if update is available
Sent from my SGH-T999 using xda premium
Successful install finally
I really have to thank you and all the others for their quick responses.
I did try different thinks after seeing the various responses:
..downloading MD5 checkers on both PC and phone, updating the recovery software and others..
But what I liked the most was.. I went to the goo.im site, selected the CM10.1 ROM, it expands and shows not only the MD5 # so I can verify it, but had a barcode, so I downloaded it directly to my phone and when done, i used the hash checker on the phone and the MD5 that was showing on the website matched the hash checker, so I went ahead and started the process and it did install successfully.
Noticed that Google play was not there so I also flashed the GPlay app.
It seems nice, even though I might back it up and then try another ROM to see which one I like the best.
Any suggestions on which is the most stable and improves both battery and other performances, while also giving you some cool tools or software?
Anthony
alomenzo said:
I've been wanting to upgrade my Tmobile S3 sgh-t999 to any of the 4.2 ROM that I could find in XDA, but when I tried to flash it from recovery, it always come back with "Installation aborted".
I tried upgrading to LiquidSmooth ROM, PAC-man ROM, CM10.1 and so on. still same.
I did place the zip files on my ext SD card and I'm able to see them when in recovery mode. I do wipe data, cache, dalvik and so on on each attempt, but still same..
If I did try with any of the new ROMs that required Google Apps to be flashed, if I would try flashing the Google app zip files first, that went successfully, but not the other zip file.
I'm a newbee, so I know I might be doing something wrong, although I have done upgrades before and was successful (but on Sprint phones)
My phone right now has 4.1.1 BUILD # JRO03L T999UVDLJA. Would it help if I go to STOCK rom for the upgrade? and which stock should I go down to if necessary?
Any suggestions?
Click to expand...
Click to collapse
myowin said:
I would check the zip file is good file first. check with MD5 checker to find out Maybe bad/incomplete download?
Or did you try reflashing recovery?
If you can flash gapps, I'm assuming you just need to verify that zip you downloaded.. Again I Can't see it so just an assumption..
Or start over by flashing stock and reroot it?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
If you want stability with lots of customization/features and good battery life I HIGHLY recommend trying out the ROOTBOX ROM, new updated version 3.8 that you can find in the op here.
http://forum.xda-developers.com/showthread.php?t=2117372
The downloads section will take you to the Rootbox site with a list of devices. Find your model and click on ”Official Releases” and it will take you straight to goo.im. If you happen to have battery issues with the default kernel you can always flash another one.
Sent from my Galaxy Nexus using xda premium
I'm trying to flash this rom and it just fails every time, saying "error flashing zip." Is there something I have to do to flash this rom? The recovery I'm using is TWRP.
muddy130 said:
I'm trying to flash this rom and it just fails every time, saying "error flashing zip." Is there something I have to do to flash this rom? The recovery I'm using is TWRP.
Click to expand...
Click to collapse
I would check MD5 first and make sure that the file is good. You can use something like Android File Verifier to do this fairly easily. It's free on the Play Store. Just compare the MD5 of the file on your phone versus the MD5 of the download on the host server. If the MD5 does not match exactly then the download is bad. Also, as stated in the OP for that ROM, if you experience issues with installation you should perform a full wipe (Factory reset and System) in recovery prior to flashing.
Just curious, why are you wanting to use a Froyo ROM that's over two years old? Also, I know this sounds dumb, but your device is the EVO 4G, correct?
The advice is free....the bandwidth, not so much
Okay I bet your problem is your recovery. You are using Twrp and it is a version higher than 2.2.2.0 correct? If so there are a couple of options. Downgrade to 2.2.2.0, use armon ra based recovery, or redo the zips update binary and script.
Sent from my PC36100 using xda app-developers app