I kept getting flash issues after using the unlockr's root method on my Nexus S 4G, specifically the inability to flash roms due to a status 7 error.
BEFORE you run around searching every forum, or use someone else's old nandroid to revert to 2.3.1, or do any craziness... if you flashed Clockwork via fastboot, install ROM Manager from the market, and install the latest ClockworkMod recovery via Rom Manager, and give it another try.
Hopefully this is easy enough to find, that no one else has this problem.
Happy hunting
Hi,
This didn't help
I installed ROM Manage from Play Store and tried to install ClockworkMod recovery from ROM Manager. Howeve, it kept on getting stuck while installing ClockworkMod recovery....
Are there any other solutions for Status 7 error?
Flash the latest CWM manually via fastboot. Have a look at the Nexus S rooting guides, they all detail how to flash a custom recovery.
Yep, it was all about updating the CWM. In my case I had to update it to the one that supports touch mode (don't remember the version number). Once that was done all went quite smoothly.
Sent from my Galaxy Nexus using XDA
Related
I hear some people use it some say it doesent work. Does it work? Is it worth installing? Just want to know if its worth my time or not lol
Sent from my LG-P999
MIUI 2.3.2
The problem with ROM manager and the G2x is that the proper method of installing the recovery is is not used. If you install recovery from ROM manager it does install a fake recovery that is basically a use-once recovery. The proper method to install the recovery on the G2x is to use NVFLASH to low level flash it. Once you install the recovery in this method the device is almost unbrickable.
Many functions in ROM manager do not work with the NVFLASH installed recovery so this kinda renders ROM manager useless. I think the only function in ROM Manager that has some merit is the fix permissions, but you can run the same thing faster from CWM recovery that is installed through NVFLASH.
A side benefit to using NVFLASH is that you do not have to root your device to install it since it is a much lower level than the OS. You can install recovery, backup the stock OS, then flash a custom ROM. If you want to go back to stock just restore the backup and use the NVFLASH program to install the stock recovery and you are back to stock for repairs or whatever.
Link to NVFlash: http://forum.xda-developers.com/showthread.php?t=1056847
I've installed recovery with nvflash but and works great but just wondering cause roms will come with ROM manager installed and I'm just wondering if I'm missing anything I guess by not letting it install its "fake" recovery or if it will mess up my nvflash version?
Sent from my LG-P999
MIUI 2.3.2
"Thanks Richie390"
I have never tried allowing ROM Manager to install the fake recovery but I do not think that it will be harmful to the NVFLASH recovery.
I believe this because many people use ROM Manager without knowing and post here that they bricked their devices and the stock recovery is always reachable. Also I bought my G2x from craigslist from someone that used ROM Manager and "bricked" the phone. I was able to fix it using the NVFLASH to flash CWM and install CM7.
Some roms (like Bionix) come with Rom Manager because the user can track OTA updates of the Rom they're using, so if the dev releases a new version, the user will get a notification that an update is available for download, if the dev set it up right.
Sent from my G2X XDA app cuz I'm stalking your mom....
Hi every i've been trying to flash my tmobile HTC ONE S to ParanoidAndroid JellyBean v2.13,fromt this link
http://forum.xda-developers.com/showthread.php?t=1890464
I unlocked(still s-on), rooted, and tried a couple different recoveries (CWM 5.8.31,5.8.24,5.8.15 etc. and TWRP 1.7, 2.2)
what I did was first unlock,then flash recovery, and root, then flash boot.img from the ROM package, and install from SDcard. However everytime I get a Status 7 error messege, and installation fails...
And one time I tried to install from CWM ROM manger from Google Play in the OS, still failed after it reboot and goes in to recovery.
Some people on the web says that this means I need a different or newer recovery, but I've probably tried all the main and newest versions.....
pls help! thnx in advance!! =)
nvm!!! I was stupid enough to download the ROM version for HTC ONE X..hahaha..
Anyone else getting this issue? I used to be able to, but now I can no longer install custom recoveries.
I purchased the pro version of Rom Toolbox a while ago, and I'm tired of it not being compatible with my recovery (not allowing me to automatically flash roms, etc). Of course Rom Toolbox has an option to download and flash recoveries but it doesn't work any longer. Regardless of what I pick (rom toolbox allows for the download and installation of TWRP, CWR, CWR Touch, and CWR for Rom Toolbox) It always fails when flashing.
I also tried the app "Recovery Manager" which also failed to update my recovery to CWR Touch. It seems that only Rom Manager can update/change my recovery image, which seems very peculiar if you ask me...
Is there any fix to allow Rom Toolbox to flash my recovery successfully? I tried installing one via fastboot, but my computer couldn't detect my phone. (I probably just need to make sure the proper drivers are installed though) but would that really fix my Rom Toolbox issue?
It would be better to be asking the Rom Toolbox dev rather than the Nexus S community. Most people will flash their recovery using fastboot, because that's the always working way.
Disregard wrong thread
Sent from my phone using my thumbs and a keyboard
You could also use flash image gui... it's a paid app in the play store, but is also available here on xda by the dev
Sent from my ns4g using Tapatalk 2
I was able to flash TWRP Recovery via Goo Manager, so now I know that it was an issue with Rom Toolbox and not my phone.
However Rom Toolbox tasks still aren't automatically done when I reboot :/ It looks like the modded CWR for Rom Toolbox isn't up and for whatever reason the newest version of Clockwork mod recovery isn't compatible with rom toolbox, even when rom manager is installed.
Well thanks. Hopefully Rom Manager and Rom Toolbox get things worked out.
So I just rooted my Verizon Galaxy S3 and unlocked the bootloader. I flashed Clockworkmod recovery using Rom Manager to update to the latest version. Made a nandroid, installed Titanium Backup, linked it to my Dropbox and uploaded. I downloaded the latest CM10 nightly to flash but the stock android recovery appeared instead of CWM. Found some info that I need to flash a clockwork compatible kernel first. The questions I have are: If I install the latest CM 10 nightly will it automatically install a clockwork compatable kernel? If not, where can I download it from? and if I do need to flash a kernel first can anyone give me detailed instructions how to do this as i'm relatively new to this stuff and don't want to brick my phone. Thanks, any info would help.
iwearthebelt said:
So I just rooted my Verizon Galaxy S3 and unlocked the bootloader. I flashed Clockworkmod recovery using Rom Manager to update to the latest version. Made a nandroid, installed Titanium Backup, linked it to my Dropbox and uploaded. I downloaded the latest CM10 nightly to flash but the stock android recovery appeared instead of CWM. Found some info that I need to flash a clockwork compatible kernel first. The questions I have are: If I install the latest CM 10 nightly will it automatically install a clockwork compatable kernel? If not, where can I download it from? and if I do need to flash a kernel first can anyone give me detailed instructions how to do this as i'm relatively new to this stuff and don't want to brick my phone. Thanks, any info would help.
Click to expand...
Click to collapse
Did you unlock your bootloader? for a custom recovery to stick you need to unlock your bootloader. Follow this guide
http://forum.xda-developers.com/showthread.php?t=1762709
darkhawk3383 said:
Did you unlock your bootloader? for a custom recovery to stick you need to unlock your bootloader. Follow this guide
http://forum.xda-developers.com/showthread.php?t=1762709
Click to expand...
Click to collapse
I did, had it unlocked and rooted. I guess there was some sort of issue with Rom Manager on the S3. I use it on my Galaxy Nexus and have no issues. I ended up abandoning what I was doing, uninstalling Rom Manager and going a different route. I have no prior experience with Odin but figured out how to install CWM . Downloaded I535vrblk1, flashed CWM, unlocked & rooted again. . Thanks anyway for the reply.
You can reinstall ROM Manager. It is something to do with some of the newer OTA's and the leaks. I have read a few posts in the forums about this in the GS3 and I really can't remember the fix but your recovery not sticking had nothing to do with ROM Manager. I think the fix was when you rebooted to recovery to flash a kernel right away, whether it be KT747, LK, or any of the other. Now that I typed this I'm about 99% sure that was the fix. Like I said above though, it has nothing to do.with ROM Manager, so if you're like me and find a lot of the tools in it handy you should be able to reinstall it. If you have a problem again just flash a kernel.
Sent from one of the many Anthropomorphic Personalities on the Disc
hey guys, i am new to rooting and flashing roms, etc, but i did manage to root my i9023 nexus s using the nexus root toolkit and installing cyanogenmod 10.2. At first, i installed twrp and then i realised all the youtube tutorials had cwm installed, so i installed cwm. now if i use nexus root toolkit to boot into recovery, it takes me into cwm, but if i try to boot into recovery using rom manager or try to update cyanogen, it takes me into twrp. so my question is, how do i delete twrp and only keep cwm? also, it would be better if you guys could help without any commands, cause those confuse me big time. thanks!!