I flashed the unofficial 6.02 but when i tried to restore my rom backup it said invalid md5 sum, so i wanted to go back to the 5.02 official but the bootloader installs it, then says error then reboots the phone. is there anyway to go back? because had i known before i wouldnt have updated.
And after i flashed eqdkp 5.1 there was a folder called blobs in sd/clockworkmod/blobs im not sure if it had anything to do the rom at all, but its taking up about 200 mb so i wanna know if its safe to delete
Try via rom manager and flash official 1.
Sent from my HTC Wildfire S A510e using xda app-developers app
^^^^what he said. But I don't think that reverting to an older version will help you with the md5 error.
Sent from my bowl of jelly!
Related
So I just rooted and I am playing with ROMS. I have been using rom manager to make back up's. I went to restore a back up and they all say that my MD5 is missing and that it is not a valid backup.
I have searched the treads but only found things about mis matched MD5's.
Any advice?
I think this might help
http://forum.xda-developers.com/showthread.php?t=714114&highlight=md5+mismatch
Try backing up and restoring through recovery...Rom manager doesn't exactly do the job. If it still does it, flash your recovery again...I have to flash any recovery twice on my phone or it doesn't completely install for some reason
Sent from my Synergy Rom using XDA Premium App
This may be a stupid question, but the radios listed here: http://forum.xda-developers.com/showthread.php?t=970809 are usable on the desire Z? The newest one, for example, is from the G2, if I understand correctly....
Yes they are, I've flashed a few different radois from that thread on my desire z
sent from my Desire Z using XDA premium app
Thanks for your reply. I see from your signature that you use the ILWT CM7. I have a question about this. I am new to rooting, so please excuse my questions if they seem stupid . I tried to install the ILWT CM7 but the 4EXT recovery manager said that signature verification failed. Of course, I turned verification off and it installed, but it this failure a problem? The official CM7 installs with verification on (so I guess it has a valid signature).
This shouldn't be happening. Have you tried downloading the file again?
You're using the 4EXT Recovery Manager, I suppose that it is the paid application the 4EXT Recovery dev is offering? If so, have you tried installing ILWT from inside recovery? (Make sure sig verification is on, of course.)
Sent from my DZ.
crestofawave said:
This shouldn't be happening. Have you tried downloading the file again?
You're using the 4EXT Recovery Manager, I suppose that it is the paid application the 4EXT Recovery dev is offering? If so, have you tried installing ILWT from inside recovery? (Make sure sig verification is on, of course.)
Sent from my DZ.
Click to expand...
Click to collapse
Sorry for the late reply but I had some problems with my computer. I downloaded the file twice and I tried the installation from recovery, not from the app.
I've installed both ways (inside recovery and from the app) and never had a problem with signature verification. Since you've tried redownloading I would suggest checking the md5 sum after downloading(if possible) just to triple check to make sure the download is proper. Other than that make sure you've got the most updated recovery, app and ROM.
sent from my Desire Z using XDA premium app
You might want to reinstall or update your recovery. If that doesn't fix it, then the dev probably forgot to sign the file.
Done that also. Switched to ClockworkMod and then back to 4ext. The issue remained. So I stick to the official CyanogenMod for now, waiting for the ics release (I hope). Thanks for the replies.
Sent from my HTC Vision using XDA
Well, I tried Cyanogen, AOPK and now I tried PARANOID 2.0.
None of them works, GAPPS works, but I get the Status 7 error while installing a ROM, i'm using the SGH-T999V and none of them works.
How are you trying to install them?
Sent from my SGH-T999 using xda premium
You are rooted and trying to install with cwm or twrp recovery, right.
I ask because that error reminds me of stock recovery for some reason...
Sent from my SGH-T999 using xda app-developers app
Hey make sure you've rooted your phone first. I'm on cm10 with leankernel and everything works just great. Good luck!
Sent from my SGH-T999v using xda app-developers app
Sounds like stock recovery to me bud..
Sent from my T999 GS3 @ 2GHZ
d2tmo wrong device?
Status 7 errors can occur in ClockworkMod for everyone saying he's using a stock recovery.
Make sure your rooted and you should be good
Hey SGH-T999V,
I think we'd all love to help, but we need some more information. Can you tell us step by step exactly what you are doing? Once we have that, I think we will be able to help you past this.
I am fully rooted with clockworld recovery 5.0.4 or something, installing zip from sdcard then Status error 7 and yeah...
From what I've gathered, status 7 errors usually occur when the ROM is incompatible with the device e.g when flashing a CDMA rom on a GSM phone. My first advice would therefore be to confirm that the zip file is for the correct GS3 variant. You mentioned aokp and CM. Both these ROMS refer to the T999 as "d2tmo" and the zip files usually contain this in the name (e.g cm-9-20120909-NIGHTLY-d2tmo.zip). I would therefore check this first before anything else.
Assuming that's not the issue, some suggestions would be:
1. This is a longshot, but try toggling signature verification and see what happens. I doubt this is the issue but I have had update zips fail because this was accidentally toggled
2. Try updating CWM: http://forum.xda-developers.com/showthread.php?t=1766552
3. Try changing the recovery to TWRP and see if its the recovery. The easiest way I've found is to use the GooManager app. Install from the play store. Run the app. Hit the menu key and select Install OpenRecoveryScript. Reboot into the TWRP recovery and try flashing from there.
4. Try rerooting the device from scratch
I got this error when I rooted using the Sprint method. I had to reflash cwm using Rom manager before I could install Cyanogen
Sent from my SGH-T999 using xda premium
I had the same problem. I updated cwm and it fixes it. Your version is old....
Sent from my SGH-T999 using Tapatalk 2
Just updated CWM to 6.0.1.2 and tried to flash with TWRP... same Status 7 error with every single ****ing ROMs i'm trying to install.
Wiped everything many times before installing zip, nothing works... i'm giving up and downloading stock ROM until Samsung releases official JB 4.1.
You might have to go back to stock and root it again
Sent from my SGH-T999V using XDA Premium HD app
could try installing the roms with Odin
Could try downloading the roms using Rom manager pro and having it install them
You just got to get one to work and you'll be golden
Is it a setting problem in cwm?
Like toggling allow installation of unsigned packages
Sent from my SGH-T999 using xda premium
Just update cwm to a newer version. I promise that'll fix it.
Sent from my SGH-T999 using xda premium
Or pay someone to do it. Look for rooting services on craigslist
Sent from my SGH-T999 using xda premium
same here
Hi, there,
just looking for solution for the same problem and got this thread...
well, I was rooted and on cyanogen and everything worked fine.
had backups and stuff.
decided to return to stock just to have it updated and backed up and after that to return to cyanogen.
when in CWM, after stock, while re-root-ing, I did a fix permission which erased some of my system files in the backups, so all my backups on the phone became useless (lesson #1: always move your backups away from the phone).
decided to start from scratch, so using ODIN I flashed the proper stock ROM for T999V. Installed the CWM version 5. something, superuser etc.
made a backup this time and store it outside the phone
when I tried to flash the cyanogen 10.0 for m2tmo (which I've flashed before without trouble), I got the error message as our friend here.
I edited the updater-script file in order to erase the first lines and got it flashed...
the problem that I have right now is that I am stuck in the first screen when the cyanogen keeps going round and round and round.... and nothing happens
any suggestion from here?
http://wiki.rootzwiki.com/ClockworkMod_Recovery#Status_7
The status 7 error can be from a bad download, bad signature, and I have seen it from using an old version of clockwork. I would first make sure you are running the most current version of recovery. if that doesn't solve your problem try redownloading the Rom.
Hi guys how come evertime I try to install a custom rom its gives me the Error 7 (Status 7 Error). Have anyone encountered this before? How do I fix it? I tried updating my CWM but still, nothing works, I tried to install Cyanogenmod 10.1 and DarthStalker but it gives me that error. Help please, Thanks in advance :thumbup:
What version of CWM are you using? Number, please.
Do you currently have a ROM on the phone? If you go into About phone from the system settings, what phone model does it say you have?
Its says I have SGH-T999
Sent from my SGH-T999 using xda app-developers app
Are you updating CWM with ROM Manager?
Factory reset, wipe cache, and you should be able to install any ROM without any issues.
Sent from my SGH-T999 using xda app-developers app
Yes I updated my CWM using Rom Manager
Sent from my SGH-T999 using xda app-developers app
I've had this happen many many times. Check the MD5. Its more than likely a bad download. Try re downloading it again.
Try transferring the download from PC to your phone. And try to flash again.
Sent from my SGH-T999 running Chihuahua v1 ROM
re: error 7 issues
CooLoL1999 said:
Hi guys how come evertime I try to install a custom rom its gives me the Error 7 (Status 7 Error). Have anyone encountered this before? How do I fix it? I tried updating my CWM but still, nothing works, I tried to install Cyanogenmod 10.1 and DarthStalker but it gives me that error. Help please, Thanks in advance :thumbup:
Click to expand...
Click to collapse
Most likely you tried to flash some rom which was not 100% compatible with your phone.
If you can get into CWM or TWRP recovery just do a factory reset/wipe cache/wipe dalvik cache.
Do NOT wipe or format SYSTEM . This should allow your phone to boot completly.
Be sure NOT to try flashing the same rom which gave you the error 7.
If you are still having problems then continue reading...
If you have a cwm/twrp backup (nandroid) of your previous rom go back into cwm or twrp
and restore your nandroid backup.
If you don't have a nandroid backup but you do have a proper zip file custom rom saved to your sdcard
then you can flash the rom making sure you first do a factory reset/wipe cache/dalvik and system.
After that you can start over again but be sure to make a nandroid backup first.
If you still have problems after doing the above you will need to ODIN flash the stock-rooted
Samsung Galaxy S3 T999 Jellybean v4.1.1 firmware.
P.S. You would NEVER get an ERROR 7 if you would only flash stock based "Samsung Galaxy S3 T999 Jellybean v4.1.1 custom roms"
instead of those CM/AOKP/AOSP or Ported roms.
Good Luck!
CooLoL1999 said:
Hi guys how come evertime I try to install a custom rom its gives me the Error 7 (Status 7 Error). Have anyone encountered this before? How do I fix it? I tried updating my CWM but still, nothing works, I tried to install Cyanogenmod 10.1 and DarthStalker but it gives me that error. Help please, Thanks in advance :thumbup:
Click to expand...
Click to collapse
First of all, make sure that you redownload the ROM, check that the MD5's match, and that you are indeed on the latest CWM recovery.
Secondly, I've heard of these status 7 errors, even when on the latest CWM recovery. There's times when installing certain ROMs where these errors occur, which usually happens when the ROM’s updater script file checks to see if the phone model of your phone is compatible with the ROM you are installing and this portion of the script are called “asserts”. with this it prevents you from accidentally flashing a ROM intended for a different model.
Normally you can fix the issue by installing TWRP recovery but there's another possible solution for this if the TWRP method doesn't solve it but take some serious precaution. You need to be very careful and do this at your own risk.
Follow this step by step guide
http://highonandroid.com/android-roms/how-to-fix-status-7-error-with-cwm-recovery-on-rooted-android/
Following this will remove the asserts thus removing protection upon flashing the wrong ROM. Do if you choose to follow this make absolutely sure that the ROM you're flashing is for the T999.
Sent from my SGH-T999 using xda premium
---------- Post added at 01:57 AM ---------- Previous post was at 01:40 AM ----------
Status 7 errors can very well still occur through CWM recovery on stock based ROMs.. It mostly all depends on the ROMs updater script and if the dev accidentally made an error within that, which is why the asserts would normally correct that error by forcing the ROM to be flashed regardless.
Sent from my SGH-T999 using xda premium
Everyone, Thanks for helping me out, I flash back to stock firmware, I found out that I rooted my phone the wrong way (Qbking's Video). I tried rerooting but I used a different method and updated CWM, now works completely fine, Thanks for all your help!! :thumbup::thumbup:
Sent from my SGH-T999 using xda app-developers app
Hi
A few days ago my phone developed a big problem; when at home I get zero reception - msg reads 'disconnected because service is not available. Sometimes even when not at home I have a few bars but if someone calls it goes straight to voicemail or says that the service is not available. I used to get full reception at home. The problem is not due to a network fault as my wife is on the same network and she still gets a full signal.
I was using viper x rom 3.5 and had not messed with roms for several months. Just prior to the problem happening I was connected to the pc via USB . I noticed that something was wrong when poweramp stopped playing and all my music files were not recognised (this may or may not be related to the problem) and I had to restart the phone and rescan for music.
I have tried several solutions including flashing the last viper rom (3.8) and trying a different sim, but nothing has worked. I have still lost all reception where I used to have a great signal (and someone on the same network in the same house still does).
Even at work with a reception I sometimes don't receive texts and often takes a few attempts to send them.
Does this sound like a hardware fault that I will need to send my phone in for repair. Or could there be any other solutions?
Thanks
Have you flashed the corresponding boot.img?
Sent from my HTC One X using xda app-developers app
Stefan0vic said:
Have you flashed the corresponding boot.img?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Yes. The problem didn't happen when messing with a new rom. I had been on viper 3.5 for months then it just happened. I upgraded to viper 3.8 today to see if that would help, and I flashed the boot.img. The rom installed fine but I still have the same issue.
After installing did you also do a full wipe?
Edit: if you did a clean install you can always try flash a different kernel and corresponding modules
Sent from my HTC One X using xda app-developers app
Stefan0vic said:
After installing did you also do a full wipe?
Edit: if you did a clean install you can always try flash a different kernel and corresponding modules
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
If I returned to to stock would that be the same as trying a different kernel?
Yes. In the nandroid backup is your stock boot.img, that is your stock kernel
Sent from my HTC One X using xda app-developers app
Stefan0vic said:
Yes. In the nandroid backup is your stock boot.img, that is your stock kernel
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Sorry for all the questions, I have only flashed a few roms.
I downloaded a stock rom for my version from the collections thread. It is a 7zp file not a zip file. When I open it it doesn't have a boot.imag. I think this is a twrp backup and I use the emmc.win file?
I have twrp installed as my recovery but I am not sure what to do.
Do I copy the emmc.win file to the fastboot folder like I would if it was a boot.img and then flash in the same way?
I am also not sure what to do with the nandroid 7zp backup. Do I extract it (or not) and then put it direct on to my sd card? Or do I place it within my twrp folder?
Do I need a custom recovery, I am not sure which one to use for version 3.14.
Sorry for all the questions.
Thanks
columbo67 said:
Sorry for all the questions, I have only flashed a few roms.
I downloaded a stock rom for my version from the collections thread. It is a 7zp file not a zip file. When I open it it doesn't have a boot.imag. I think this is a twrp backup and I use the emmc.win file?
I have twrp installed as my recovery but I am not sure what to do.
Do I copy the emmc.win file to the fastboot folder like I would if it was a boot.img and then flash in the same way?
I am also not sure what to do with the nandroid 7zp backup. Do I extract it (or not) and then put it direct on to my sd card? Or do I place it within my twrp folder?
Do I need a custom recovery, I am not sure which one to use for version 3.14.
Sorry for all the questions.
Thanks
Click to expand...
Click to collapse
You need a recovery that supports both cwm and twrp nandroids.
http://forum.xda-developers.com/showthread.php?t=2240646
That is philz touch recovery, I use it, touch works and it supports both cwm and twrp nandroids.
Now you need a nandroid, check your CID + Version main and get your nandroid here:
http://forum.xda-developers.com/showthread.php?t=1975140
Make sure you have the nandroid you downloaded in the right folder, do a full wipe, restore it, and flash the boot.img. That is all
Thanks. What is the right folder? Do I use the recovery to do the full wipe before I flash?
I used that link and have my version for HG3__001 but there is no boot.img in the 7zp file I downloaded.
I think clockworkmod/backups
Yeah you do a full wipe with it.. well if there is no boot img or boot emmc in the file then its not a complete backup..
I just noticed that you found a boot emmc file (s/t like that) flash it like any other boot.img
Sent from my HTC One X using xda app-developers app
---------- Post added at 01:10 AM ---------- Previous post was at 01:02 AM ----------
Also, the files do not need to be unzipped. It's supposed to be like that
Sent from my HTC One X using xda app-developers app