Issue Flashing Roms - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

So for some reason, I catch an error everytime I try to flash a rom to my phone. Then I am forced to restore my backup.
I have it rooted with CWM v5.5.0.4.
i747.
Not sure what other information you guys would need to assist. Would I need to re-root it? Different version of CWM?

Are you wiping data before you flash any new roms? That could be it..

Yep, always wipe data/factory.

.... i'm pretty sure that telling us what the error message says would help, too....

I'll take a wag and say since your recovery is 5.5.0.4 your probably getting a status 7 error which simply means you need to update your recovery to the newest version. Check in the dev section for the cwm recovery thread.

jethro650 said:
I'll take a wag and say since your recovery is 5.5.0.4 your probably getting a status 7 error which simply means you need to update your recovery to the newest version. Check in the dev section for the cwm recovery thread.
Click to expand...
Click to collapse
Agreed, almost undoubtedly...in every recovery flashable .zip there is an update-binary file which is the actual executable that is commanded by the update-script on what operations to perform. The newer versions of this binary are incompatible with older versions of the recoveries. This effect is not necessarily one way either, an older recovery trying to flash a new .zip or vice versa can produce this error but as a general rule using the newest recoveries should minimize this problem. The only time the reverse is a problem is when there is an update to the recovery api and there hasn't been an updated update-script built into a .zip. The easiest way to check is download the appropriate rom manager for your recovery, Clockwork Rom Manger for CWM or Goomanager for TWRP.

Related

ROM Manager Premium v.2.5.0.5

When trying to download a new Clockworkmod recovery 2.5.1.1 I'm getting an error occurred while flashing your recovery.
I'm able to flash 2.5.0.1.
Why is this happening. Is it because of my Kernel or ROM?
Wallabe said:
When trying to download a new Clockworkmod recovery 2.5.1.1 I'm getting an error occurred while flashing your recovery.
I'm able to flash 2.5.0.1.
Why is this happening. Is it because of my Kernel or ROM?
Click to expand...
Click to collapse
You must have denied permissions with setcpu to change the recovery. If not, just use fastboot and do it manually. Get klutsh's clockworkmod which lets you hack the ps3.
Also post your questions in the Q & A and not here.
also wrong section
nice rom
puertoblack2003 said:
nice rom
Click to expand...
Click to collapse
LMAO!!
10 chars
I just installed the new version of ROM Manager premium, but it's still saying the latest recover is 2.5.0.1. Where are you seeing the newer one?
Wallabe said:
When trying to download a new Clockworkmod recovery 2.5.1.1 I'm getting an error occurred while flashing your recovery.
I'm able to flash 2.5.0.1.
Why is this happening. Is it because of my Kernel or ROM?
Click to expand...
Click to collapse
I dont think that recovery is for our phones...looking at the mirror where the file comes from i dont see one for the evo of that version
http://koush.tandtgaming.com/recoveries/
2.5.0.1 is the latest (recovery) the app on the other hand is different
The guy above me is correct. 2.5.1.1 is the latest for certain phones, but not for the EVO. I don't know why it lists itself as a possibility though, I would think it could filter the results based on your type of phone.

Updgrading Clockwork mod

During the summer I rooted my phone and i have Clockworkmod v2.5.0.7 installed.
I am trying to upgrade to the latest version and it never seems to stick.
Using Rom manager. It says that im flashed to v5.0.2.0 yet when i boot to recovery from rom manager it loads to v2.5.0.7. Does the same thing if i choose to flash a rom though ROM MANAGER. each time v2XXX loads
So i fire up recover and try loading the zip. Bingo it works. The screen turns from green to blue and V5.0.2.0 is now there for me to use. But if i reboot and later return to recovery its back to the old V2xxxx..
Any ideas why this is happening? Is it really necessary to move on to the V5xxxx versions? I was going to try out some new roms and they failed to load yesterday through v2.5.0.7 yet the rom i had been using loaded fine.
Thanks in advance..
When you use Rom Manager to flash a rom or reboot into recovery from Rom Manager, it boots the recovery from a downloaded recovery file. It's known as fake flash or in other words, it's temporary. If you want a permanent recovery, you would need to flash a recovery.img through fastboot.
Meaple said:
When you use Rom Manager to flash a rom or reboot into recovery from Rom Manager, it boots the recovery from a downloaded recovery file. It's known as fake flash or in other words, it's temporary. If you want a permanent recovery, you would need to flash a recovery.img through fastboot.
Click to expand...
Click to collapse
if your Desire is s-off, then ROM Manager flashes recovery normally.
Sent from my HTC Desire using XDA App
rom manager now works only if u have s-off..no fake flash anymore is possible
revolutionary.io will upgrade cwm if you want
I think this thread answers one of my own questions but will ask it anyway to confirm; when I rooted my Desire (via Unrevoked) a few months back, the ROM Manager app that continues to be updated via the market offers the option to upgrade the version of CWM... is it OK to proceed with this?
I've been wary of upgrading from the version installed via the rooting process, just in case, but seeing this thread has made me think there isn't actually an issue with whatever version of recovery you have installed?
TKG26 said:
I was going to try out some new roms and they failed to load yesterday through v2.5.0.7 yet the rom i had been using loaded fine.
Click to expand...
Click to collapse
Out of curiosity - what roms you tried to load? As far as I know 2.5.0.7 was the last cwm supporting both amend and edify scripting and it never failed for me personally.
To upgrade recovery (or hboots) I always use Fastboot Commander and it's very easy to use and never let me down.
erklat said:
Out of curiosity - what roms you tried to load? As far as I know 2.5.0.7 was the last cwm supporting both amend and edify scripting and it never failed for me personally.
Click to expand...
Click to collapse
I agree. Unless you need to maintain an ext 4 partition (as 2.5.0.7 converts it to lower apparently when backing up) I see no reason to change from 2.5.0.7.
I use it even today. Best recovery IMHO.

[Q] ClockworkMod Recovery Update

Hi,
I have ClockworkMod Recovery v5.8.0.2. on my Galaxy Nexus. I'm running on XenonHD, but now I want to flash the latest 4.2 rom of Xenon.
Is my recovery outdated and should I update?
If so how do I update a recovery?
According to the cwm recovery page, the latest version for the gnex is 6.0.1.5
I can't remember which version added support for 4.2 (older versions would recursively create the /0 folder...), so you probably want to update it.
To update the recovery, just follow the same steps you did for install.
Your old backups may no longer work properly, although I think there might be a couple solutions mentioned in these forums on how to keep them.
meisanerd said:
According to the cwm recovery page, the latest version for the gnex is 6.0.1.5
I can't remember which version added support for 4.2 (older versions would recursively create the /0 folder...), so you probably want to update it.
To update the recovery, just follow the same steps you did for install.
Your old backups may no longer work properly, although I think there might be a couple solutions mentioned in these forums on how to keep them.
Click to expand...
Click to collapse
Thanks for the reply. I used a one click for all method, so I am not sure how I should install a recovery.
I found this thread: http://forum.xda-developers.com/showthread.php?t=1757146 can I just flash this flashable zip with CWM?
I can't post in the development section that is why I am asking about this here.
Sorry, I do not know if you can just flash the zip over it, as I just did the "fastboot flash recovery cwm.img" method.
If your original method was just clicking on a .bat file, you might be able to replace the .img file that was included with it with the latest img file for cwm, as chances are the bat file just executes the command I listed above. If the script also installed XenonHD, though, I would probably avoid using it as it might overwrite your existing install.
https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager&hl=en
There you go OP. Install that app, hit the "flash CWM" button, grant root permission (set to remember), when it finishes I would hit the "flash CWM" button again and have it run w/o asking for root permission. You should be on the new CWM, it will show the # for the version you are on. :good:
Okay I will try the Rom manager app.
Just so you know Rom Manager is the official app from Koush, the dev behind CWM.
WiredPirate said:
Just so you know Rom Manager is the official app from Koush, the dev behind CWM.
Click to expand...
Click to collapse
Ooh okay, I heard about the app before but I never used it.
If you search here on the forums I believe you will find the "touch" version of CWM, or you can purchase it within the Rom Manager app and get the updates. I purchased it and I prefer it to the old method of using the volume buttons.

Issue updating CWM for 4.4 install

Been a while since i updated my device so i wanted to try out the new 4.4. I see that i needed CWM 6.0.4.3 and i only have 6.0.3.0. I downloaded Rom manager and installed the update that way and Rom manager says its is running the 6.0.4.3 but when i go to the recovery it says the old version is still running and gives me the expected error when i try to flash the 4.4 ROM. I also tried to download the the update file and flash that in recovery and it didn't work either.
Any help would be greatly appreciated. It probably something simple and i will feel like an idiot when someone chimes in........
guttus said:
Been a while since i updated my device so i wanted to try out the new 4.4. I see that i needed CWM 6.0.4.3 and i only have 6.0.3.0. I downloaded Rom manager and installed the update that way and Rom manager says its is running the 6.0.4.3 but when i go to the recovery it says the old version is still running and gives me the expected error when i try to flash the 4.4 ROM. I also tried to download the the update file and flash that in recovery and it didn't work either.
Any help would be greatly appreciated. It probably something simple and i will feel like an idiot when someone chimes in........
Click to expand...
Click to collapse
I updated mine yesterday from the rom mananger and had no problems.
1 thing you should know before you go and try the 4.4 kitkat is that sd card isnt showing. I love the rom but cant get to anything on my sd card.
Good luck.
@guttus
Just a Rule of Thumb. It is advisable to flash Recoveries with ODIN. I am very well aware you can use Rom Manager or Goo Manager, but this is just a thumb rule for flashing the Recovery Partition.
Also note, flashing wrong Recovery can cause hard brick.
recoveries in my sig.
odin and recovery flashable versions
Sent from my T-Mobile MyTouch 3G Slide(HTC Espresso) using Tapatalk 2
Hi all. I'm on the i9305 and want to flash latest recovery for kitkat. I'm on philz recovery and wondered if there was one of his I could use. I searched xda but I couldn't find anything. Also I couldn't find an Odin (tar) file for normal cwm. Omni and cm only have the zip and IMG files.
Perseus71 said:
@guttus
Just a Rule of Thumb. It is advisable to flash Recoveries with ODIN. I am very well aware you can use Rom Manager or Goo Manager, but this is just a thumb rule for flashing the Recovery Partition.
Also note, flashing wrong Recovery can cause hard brick.
Click to expand...
Click to collapse
I did do this update via oden. Also flashed Phil's recovery from there. This is where i tried to flash the 4.4 gapps to fix the issue with no luck.
Please post a log of the error when you tried to flash CM Kitkat. If you can't pull the log file, take a photo.

[Q] I747 Galaxy S3 Clockworkmod Recovery Problem

Ok guys I am a noob (also new to these forums) and I'm having a lot of trouble with my phone. The other day, I rooted my phone using towelroot and confirmed it using root checker. then, I downloaded ROM manager as advised by a friend. i followed the instructions and installed Clockworkmod Recovery onto my AT&T Galaxy S3. Feeling I was finally ready to install a ROM, i tried to download Cyanogenmod 10.3.1 only to have it be "downloading" for over 14 hours without it completing. From there, i did some research and decided to utilize the Cyanogenmod Installer. it seemed to work perfectly, even showing the cyanogenmod logo under when my devicec turned on, until it told me to reboot my device. i entered clockworkmod recovery mode to officially reboot it. when i selected "reboot system now" it said "Root access possibly lost. Fix?". i was given the options to say "No" and "Yes - Fix root (/system/xbin/su). no matter which one i try, my phone boots to the stock touchwiz OS. I have installed and reinstalled both superuser, superSU, and ROM manager to no success. What am i doing wrong?
Try flashing Philz Touch via Odin and use that to flash a custom ROM.
From what I recall, CM ROMs are already rooted.
audit13 said:
Try flashing Philz Touch via Odin and use that to flash a custom ROM.
From what I recall, CM ROMs are already rooted.
Click to expand...
Click to collapse
CM is already rooted? What does that mean? I have a feeling that I will be unable to flash any ROMs due to my "possible loss of root access." Thank you for your patience as I am a noob and am very stressed out as this is my only phone.
I see two areas that are potential problems for flashing that rom. If it took 14 hours to download, its highly likely a corrupted download. But also, you may be on too new firmware. Cm uses asserts in the updater-script to check that you have the right base firmware/bootloader build. They dont update this so when newer firmware is released it will no longer flash because the script doesn't see it as allowed.
Anytime you have issues flashing something in recovery, you should copy the recovery log to sd. This will tell you what happened. I suspect it simply didn't flash, but without the log, theres no way we can tell what happened.
Also, you do not need to be rooted to flash anything from recovery. Just flash the recovery, then flash a rom from there. Nearly all roms you will ever see are already rooted. Non rooted roms are very rare and are generally only used as an alternate way to revert to stock.
I dont use cwm, but if im not mistaken, it seems to always ask to fix root. I dont know why, but I see people ask about it frequently.
I use TWRP, so try that, or philz as suggested by audit13. Just watch the flash progress for any errors and copy the log.

Categories

Resources