Long time lurker first time poster. I have a sprint gs3. Clockwork recovery is on it but i keep getting status 7 error when trying to update my rom. I cleared cache and storage n all that n reflashed recovery with odin still error 7. I was able to odin a stock rom back on still that status 7 error. I wanted supernexus build 5. Any chance someone could get a tar of that so i could just odin it on. Im getting frustrated. Id appreciate the help. I was going to post in dev but i cant yet. Thanks for taking time to check this out for me.
Status 7 error usually means the ROM was not intended for your device. CWM looks at your build.prop and kernel to determine if it's compatible. Double-check in the thread for the ROM if others with your phone are using it successfully. Also, the 1st post in any ROM's dev thread usually has a link to a discussion thread. The discussion thread is intended for all discussion not related to development.
post-mortem said:
Status 7 error usually means the ROM was not intended for your device. CWM looks at your build.prop and kernel to determine if it's compatible. Double-check in the thread for the ROM if others with your phone are using it successfully. Also, the 1st post in any ROM's dev thread usually has a link to a discussion thread. The discussion thread is intended for all discussion not related to development.
Click to expand...
Click to collapse
thnaks for the heads up but it says I'm unable to post there yet. I've tried to flash the stock rom and cm10 (which was previously on there) still same error. that being said maybe my build prop is messed up or something? Do you have any idea how to fix that? I haven't messed with flashing since cupcake days. lol
dcninja said:
thnaks for the heads up but it says I'm unable to post there yet. I've tried to flash the stock rom and cm10 (which was previously on there) still same error. that being said maybe my build prop is messed up or something? Do you have any idea how to fix that? I haven't messed with flashing since cupcake days. lol
Click to expand...
Click to collapse
i've had this happen as of recently, too. What's weird is i can attempt to flash the rom and it works fine. A few hours later, after i have flashed and wiped off another rom i go back to the original rom i just flashed. But this time it says status 7. I don't understand why it's working one hour and then a few hours down the road, the same one (un touched and un modified) will throw a status 7 at me. I get the same with CWM6 and TWRP 2.3.
**Flashing cm10 and aokp**
Related
I have been trying my best for the last 3 hours to flash a rom on this damn phone. I have rooted it and installed a custom Recovery. However ever time I flash any ROM to this phone through clockwork I get an error in clockwork mod stating assert failed and gives a bunch of code and then says status 7. What the heck is going on here ? I have flashed roms for years using this site and I have never had so much trouble. Can someone help me PLEASE ?
If you are getting status 7,you should Odin back to stock..then read the thread for the one you want to flash.
Sent from my SCH-I500 using XDA App
This is NOT development. This belongs in the Questions and Answers, or General Section.
Sent from my Fascinate with MIUI Gingerbread
Shakes is right. Odin back to stock (check md5 first), root, make sure you install the right version of clockwork. There are at least two flavors of CWM 4.0, two of 3.0, and something like four of 2.x. After you've figured the right CWM, DL your chosen ROM and run a checksum to make sure the zip is intact. Then flash away. If you break/brick, Odin back to stock again. Repeat until you get a config you like.
RE:
Okay I am trying to flash this build http://forum.xda-developers.com/showthread.php?t=1168068. I have no idea how to on this device. I have went back to stock 5 or 6 times. And started over. Can you guys please tell me how I would flash this after flashing CWM and rooting ?
cjegan2008 said:
Okay I am trying to flash this build http://forum.xda-developers.com/showthread.php?t=1168068. I have no idea how to on this device. I have went back to stock 5 or 6 times. And started over. Can you guys please tell me how I would flash this after flashing CWM and rooting ?
Click to expand...
Click to collapse
What rom (which stock) were you running before? Even more important what kernal? And which CWR? Before you flashed back to stock were you running a voodoo kernal? and if so did you disable lagfix? I had the same problem and it was that lagfix was still enable.
I was running the Spike Pure ICS on my SGS2, before which I had the ICS version of MIUI. I tried flashing Lite'ning Rom 3.6 through Odin, but was unsuccessful. Also, that's time I noticed the 7.2 version of CM and decided to flash that and that's when the problem occurred.
Although I could flash CM 7.2 properly and could also install the GApps through CWM, on rebboting it through the CWM, my phone got stuck and it wouldn't go into Recovery any more.
Luckily, it would boot into Download Mode and I could flash the stock rom through Odin and get my phone back to stock, thereby losing the Root and CWM.
I wanna know as to what could cause such an issue to arise. so that I can prevent it later!
Your help and time are appreciated!!
Why start a 2nd thread ?
That's because every person who replied told me how to go about the problem, but nobody told me why it occurred in the first place!
I posted this thread so that I can know how to avoid such a problem in the first place, as such a problem seemed very unique to all the people I talked to.
And you couldn't make another post to your initial post along the lines of 'Why did this occur in the first place ?' You could even easily change the title of your initial thread to reflect your desire to know the answer to this question.
One of the main rules of XDA is don't spam.
I'm extremely sorry if I've spammed as it wasn't my intention at all!
This thread was and still is a genuine question which I want to know!!
Also, could you please tell me about the occurrence of such a problem on my phone??
gadgyfreak said:
That's because every person who replied told me how to go about the problem, but nobody told me why it occurred in the first place!
I posted this thread so that I can know how to avoid such a problem in the first place, as such a problem seemed very unique to all the people I talked to.
Click to expand...
Click to collapse
I think answer was there but might be not clear......
When you flash gb over ICS you have to wipe, when you mix stuff after that, meaning trying different kernels to fix the issue it might get worse.
Because recovery is somewhat linked to kernel in s2, you won't get recovery in a messed up system.
So when you flash a complete firmware using Odin and then do data cache wipe, it get fixed.
Hope this helps.
But then how is it possible that my phone didn't get all messed up when I flashed CM 9(Nightly) over my pre-existing CM 7.1, while it happened when I tried it vice versa?
already told you, when you go from ICS newer kernel to GB older kernel, wipe is necessary. Going from GB to ICS will work but wipe is better there too.
Thanks a lot for your help.
So what exact procedure do I have to follow if I want to mover from ICS to GB?
Flash a GB rom.
gadgyfreak said:
Thanks a lot for your help.
So what exact procedure do I have to follow if I want to mover from ICS to GB?
Click to expand...
Click to collapse
save data
Wipe dial *2767*3855#
Flash GB Rom, preferably stock using Odin.
Should boot now, if not go into recovery and wipe data cache.
It will boot now.
Here's the deal:
I rooted my phone a long time ago, and have been using CM since ICS. Mostly nightlies.
A few weeks ago I decided installing a Carbon nightly (4.3), and everything went smooth as usual.
Then new nightly came, so I decided flashing it. (Dirty flash, but it's that way from what I read in the Carbon thread)
The thing is, my phone boots up correctly, but I can't get into recovery mode. Whenever I try booting recovery mode, the logo appears, then the screen flashes gray. I have tried both the advanced reboot menu, the button combo, and ROM Man...jk
I think something might be wrong with the recovery included in the kernel. If that's the case, would it be OK to flash just a new kernel or do I have to reflash the whole thing?
I have already seen some guides on flashing kernels with mobile ODIN, but they're either ancient or for another model. Also, I don't know if that's the right thing to do under this situation.
I'd appreciate if someone pointed me in the right direction. I don't wanna frak up my phone.
You can install a kernel to see if that will solve the issue, but as far as I can see, the Carbon devs do not provide a stand alone kernel for their rom. You could use AJK or one of the other kernels though. Or you could just reinstall the rom to see if it would clear up the problem.
Or, you could extract the zImage from the full rom and use Mobile Odin.
I didnt want to create a new thread for this and get yelled at.. so I am asking the question here:
I had to do the ODIN method and returned my phone from ShoStock 3 to Stock Gingerbread, because for some reason my phone was getting stuck at the "samsung galaxy s2" boot screen.
So I am back on Stock Gingerbreak Rom and trying to install ClockWork Mod Recovery, so that I can restore the backup of ShoStock that I had created.
I am doing the Mobile Odin Lite method and I downloaded the i777 kernel. When I try to install it, I boot in the Android System Recovery (3e) and get the following errors:
Installing package...
Finding Package...
Verifying Update Package...
E: failed to verify whole-file signature
E: signature verification failed.
Before I get yelled at, I searched google and came up with the solution -- all of which say that the issue can be easily fixed by toggling the setting in ClockWork Mod Recovery Mode, but I have to install it first, and whenever I try to install it, I get the above error.
Can someone help please?
jjack0310 said:
I didnt want to create a new thread for this and get yelled at.. so I am asking the question here:
I had to do the ODIN method and returned my phone from ShoStock 3 to Stock Gingerbread, because for some reason my phone was getting stuck at the "samsung galaxy s2" boot screen.
So I am back on Stock Gingerbreak Rom and trying to install ClockWork Mod Recovery, so that I can restore the backup of ShoStock that I had created.
I am doing the Mobile Odin Lite method and I downloaded the i777 kernel. When I try to install it, I boot in the Android System Recovery (3e) and get the following errors:
Installing package...
Finding Package...
Verifying Update Package...
E: failed to verify whole-file signature
E: signature verification failed.
Before I get yelled at, I searched google and came up with the solution -- all of which say that the issue can be easily fixed by toggling the setting in ClockWork Mod Recovery Mode, but I have to install it first, and whenever I try to install it, I get the above error.
Can someone help please?
Click to expand...
Click to collapse
3e recovery is the stock recovery. It means you have not installed a custom kernel yet. Please look at the links in my signature and use the guide information there, which will help you understand what you need to do to install mobile odin lite and then install a custom kernel.
Also, remember that you will need to have the correct version of ClockworkMod Recovery to restore your backup. If the backup and the version of CWM recovery are not compatible, it will not restore.
If you have questions, ask them here, but be aware, I only come on line usually two or three times a day to check the forums.
creepyncrawly said:
3e recovery is the stock recovery. It means you have not installed a custom kernel yet. Please look at the links in my signature and use the guide information there, which will help you understand what you need to do to install mobile odin lite and then install a custom kernel.
Also, remember that you will need to have the correct version of ClockworkMod Recovery to restore your backup. If the backup and the version of CWM recovery are not compatible, it will not restore.
If you have questions, ask them here, but be aware, I only come on line usually two or three times a day to check the forums.
Click to expand...
Click to collapse
I followed Step 3a on this post: http://forum.xda-developers.com/showthread.php?p=18576627#post18576627
Unfortunately, for some reason, ODIN Lite was not recognizing DD_03042012.zip file. So I went with Siyah and downloaded the TAR file used ODIN to get the clockwork mod. It worked.
Now the problem is I cant restore my backup. I know the same backup has worked before, not it is giving me an error "Error while restoring /system". wth!
I dont remember what version of Clockwork Mod I had. I know it was an older version, becuase it didnt have touch.
How do I get a previous version of CWM?
But my problem isn't even remotely similar to this guy!
I'm trying to ask if there's some way to flash a new kernel/rom without using recovery, taking advantage of the fact that my phone boots fine but I can't boot recovery. That's the reason why I mentioned ODIN.
Also, go make your own thread. My question didn't even get answered
Actually,
Creepyncrawly, thanks for your help.
I downloaded ShoStock 3 and flashed it to get the previous version of CWM, and then was able to do a restore.
Sigh.. no harm done.
You can have your thread back... good luck!!
Mighty_Rearranger said:
But my problem isn't even remotely similar to this guy!
I'm trying to ask if there's some way to flash a new kernel/rom without using recovery, taking advantage of the fact that my phone boots fine but I can't boot recovery. That's the reason why I mentioned ODIN.
Also, go make your own thread. My question didn't even get answered
Click to expand...
Click to collapse
Yes, as stated by creepyncrawly, u can use mobile odin or regular odin to flash a kernel.
But i would suggest doing a MD5 check on the Rom u downloaded, because the Rom u flashed may be that of a corrupted download. If MD5 doesn't match then redownload, check MD5 and if good, reflash the Rom.
.....or maybe the nightly is messed up.
Sent from my SAMSUNG-SGH-I747 using xda premium
Mighty_Rearranger said:
Here's the deal:
I rooted my phone a long time ago, and have been using CM since ICS. Mostly nightlies.
A few weeks ago I decided installing a Carbon nightly (4.3), and everything went smooth as usual.
Then new nightly came, so I decided flashing it. (Dirty flash, but it's that way from what I read in the Carbon thread)
The thing is, my phone boots up correctly, but I can't get into recovery mode. Whenever I try booting recovery mode, the logo appears, then the screen flashes gray. I have tried both the advanced reboot menu, the button combo, and ROM Man...jk
I think something might be wrong with the recovery included in the kernel. If that's the case, would it be OK to flash just a new kernel or do I have to reflash the whole thing?
I have already seen some guides on flashing kernels with mobile ODIN, but they're either ancient or for another model. Also, I don't know if that's the right thing to do under this situation.
I'd appreciate if someone pointed me in the right direction. I don't wanna frak up my phone.
Click to expand...
Click to collapse
Mighty_Rearranger said:
But my problem isn't even remotely similar to this guy!
I'm trying to ask if there's some way to flash a new kernel/rom without using recovery, taking advantage of the fact that my phone boots fine but I can't boot recovery. That's the reason why I mentioned ODIN.
Also, go make your own thread. My question didn't even get answered
Click to expand...
Click to collapse
I can see why you could be upset that someone hijacked your thread.
I only see one question in your original post, which I believe I answered. You also requested assistance which I thought I provided.
Let me be a little more specific for you. Yes, you can flash just a kernel without re-flashing the system. However, you will need either an Odin flashable tar of the kernel, or you will need to install Mobile Odin and then you can flash a kernel directly from a zImage file.
However, I think 4-2ndtwin has the right of it. It was probably a bad flash, even though the phone booted normally. You should consider re-flashing the entire rom.
If you are not clear about anything, please ask questions.
Never mind.
I concluded it wasn't worth it just because I was lazy backing up stuff.
I used this: http://forum.xda-developers.com/showthread.php?t=1525821, then flashed a clean ROM.
Thanks for the help, you guys are awesome.
I'm no noob when it comes to flashing roms but due to my account cannot post to appropriate thread. I have the Samsung S950c (which fascinate roms are the ones Ive always been told to use after using the romkonverter app on them) and have installed the Pacman 905 build and the Gapps as per the thread and now the screen just sits on the Insert Coin Game Over Screens. It never actually reboots and has no problem responding to the reboot into recovery so not "locked up". I know that the partitions afre changed now due to the 4.3 ROM so what now? Is there another 4.3 that is more stable that I should use or am I stuck with using ODIN and going back to the latest 10.2 nightly?
It's my fiances phone so If you could help me figure this out before she finds out it'd save me alot of grief LOL:crying:
Original thread:http://forum.xda-developers.com/showthread.php?t=2197171
I rebooted recovery and just did another wipe/factory reset. Sorry for the alarm
overman2k said:
I'm no noob when it comes to flashing roms but due to my account cannot post to appropriate thread. I have the Samsung S950c (which fascinate roms are the ones Ive always been told to use after using the romkonverter app on them) and have installed the Pacman 905 build and the Gapps as per the thread and now the screen just sits on the Insert Coin Game Over Screens. It never actually reboots and has no problem responding to the reboot into recovery so not "locked up". I know that the partitions afre changed now due to the 4.3 ROM so what now? Is there another 4.3 that is more stable that I should use or am I stuck with using ODIN and going back to the latest 10.2 nightly?
It's my fiances phone so If you could help me figure this out before she finds out it'd save me alot of grief LOL:crying:
Original thread:http://forum.xda-developers.com/showthread.php?t=2197171
I rebooted recovery and just did another wipe/factory reset. Sorry for the alarm
Click to expand...
Click to collapse
Go into Odin. That's your best bet
Sent from my SCH-I500 using Tapatalk 4
10 posts [email protected][email protected]
I need to ask a serious question and CANT due to 10 posts so here goes... is fascinate build 20130927-202524 alright? there were two
post 3
I need to ask a serious question and CANT due to 10 posts so here goes... is fascinate build 20130927-202524 alright? there were two. this is from the one stated up top btw..
No offense but the last 3 posts of the pac thread answer that exact question
Edit: realized I posted in the wrong section.
I have an AT&T Galaxy S3.
So I updated to the Kit Kat 4.4.2 thinking it would finally speed up my phone, but nope still very sluggish.
I decided that I wanted to root it and install cyanogen mod so it would speed up. Little did I know how difficult of a task this would be. I tried doing the one click install on their site. Didn't work. I had to scour these forums for a good guide to root my 4.4.2 firmware, after going through 5 guides. Eventually had to use Odin and TWRP to root it and get rid of Knox. Finally I tried to install canogen mod with ROM Manager. It wasn't downloading and I accidentally replaced TWRP with clockwork mod. I tried to install cyanogen mod with sidestep. Didn't work. Replaced clockwork mod with TWRP and it still didn't work, but after googling the errors from this, it turned out it had something to do with my bootloader.
So I went to the http://forum.xda-developers.com/showthread.php?t=1831898 thread, and I flashed the I747UCDMG2: modem_CWM_I747UCDMG2.zip - 19.01 MB - July 2nd, 2013.
I tried flashing cyanogen mod again, and it had the same error. At this point, I just gave up and I would just restore my Kies files. I go into my phone and my wifi isn't working and I'm not getting a signal.
I check the baseband and it says unknown, and my IMEI is null/null.
My original baseband said I747UCUFNE4.
I don't know what to do. I've read that I should just flash the original bootloader, but I can't find it anywhere.
Would following this guide work? http://forum.xda-developers.com/showthread.php?p=53572812
I also have a kies backup, but I don't think it has the EFS data.
edit: Just found this http://forum.xda-developers.com/showthread.php?p=53627484 a 4.4.2 modem. Would flashing this work? I don't want to mess around anymore without seeking help from others. I'm getting way in over my head.
Edit2:
Alright, I followed the http://forum.xda-developers.com/showthread.php?p=53627484 after seeing more people fix the same issue. It worked! Can a moderator delete this topic? Sorry for not being more thorough in my search for the solution. It just took me a while to find it, had to dig deep in a 100 page topic before I found it. Just wanted to take a precaution with this topic in case I didn't find it.
I have another problem.
I noticed my reception is incredibly low now after flashing that modem. I don't know how to fix it. I also flashed SlimKat.
Visit link best option for you.
http://forum.xda-developers.com/showthread.php?t=1804117
Hit thanks if you like?
Sent from my GT-I9300 using XDA Free mobile app
wrong thread. Delete plz :silly: