[Q] how to reflash to older Clockworkmod version - Xoom Q&A, Help & Troubleshooting

i have a rooted Xoom MZ600 4G LTE, android 4.1.1, EOS nightly 139, the other day I mistakenly flashed my CWM to latest... now my CWM recovery wont read my SD card.... I'm reading a lot about reflashing my current CWM to older version, i'm very new in this hobby, can someone point to me the link to get the appropriate version of ClockworkMod verion and the step by step tutorial to reflash it back to older version... I tried doing it via GooManager , it's a no go, I get an error...thanks god, i did not brick my device... do I have to re-root my device again... I originally had it rooted by a friend who's in the Service (military) and not avaiable.... thanks in advance..... smilyize

problem solved !!!
nevermind....... I decided just to use TWRP .............. for me the interface is much better.......... smilyize

Yeah it is better in my opinion as well.
Motorola Xoom, CM10 Nightly

Related

Clockworkmod Recovery issue

Hi guys I really hope someone can help me with this. I was running CM7 Nightly rom and decided to try and flash eaglesblood 2.3.5 and it flashed ok but the problem is that when I tried restoring my back-up on it I get an clockworkmod recovery error. Any Ideas?
I don't know what phone you have or which version of clockwork you are using, but for some phones clockwork recently got an upgrade to 5.x.x. If you upgraded your clockwork after you made your backup, the previous backups will not work with the new version. You may have to downgrade. Like I said, I don't know your issue, but that is a possible solution.

[Q] Is it bricked or not?

Dear all
My tf700t stops at the first Asus monitor with nVidia logo down and unlocked at the top left. Have rooted it with unlocked it with Asus tool, rooted with "RootDebugfs," added TWRP via GooManager and tested several roms, but Asus will not boot. Having thus access to Fastboot and TWRP. The following roms is tried: "Mysticial ROM v1", "Team EOS ROM for the TF700" and "Maniacs ROM" for 4.0, but the same thing happens every time. Have tried all possible ways to delete cache but no result. I need help now.
alldog said:
Dear all
My tf700t stops at the first Asus monitor with nVidia logo down and unlocked at the top left. Have rooted it with unlocked it with Asus tool, rooted with "RootDebugfs," added TWRP via GooManager and tested several roms, but Asus will not boot. Having thus access to Fastboot and TWRP. The following roms is tried: "Mysticial ROM v1", "Team EOS ROM for the TF700" and "Maniacs ROM" for 4.0, but the same thing happens every time. Have tried all possible ways to delete cache but no result. I need help now.
Click to expand...
Click to collapse
It seems you picked three ROMS with problems to try for your 1st flash. I can't say anything about the Mystical ROM v1 (although it is based on a TF300 JB OTA) but the other 2 just may not boot at all (maniac is old old, and the EOS JB Rom v3 couldn't boot).
If you can try ZEUS v4 (ICS) or unofficial CM10 alphs latest 9/25 build (JB) you would be OK.
IF you are truly stuck, and you have a microsd card, follow the restore from a soft brick guide from here: http://forum.xda-developers.com/showthread.php?t=1803343
Please note that this guide references the .26 update...if you updated to the .30 update, use that stock rom (I think you can get it from the same place). Just follow the instructions and you should be back at square one-stock. Re-root and reinstall TWRP, then choose a ROM more wisely, by reading the threads to see what is working well.
okantomi said:
It seems you picked three ROMS with problems to try for your 1st flash. I can't say anything about the Mystical ROM v1 (although it is based on a TF300 JB OTA) but the other 2 just may not boot at all (maniac is old old, and the EOS JB Rom v3 couldn't boot).
If you can try ZEUS v4 (ICS) or unofficial CM10 alphs latest 9/25 build (JB) you would be OK.
IF you are truly stuck, and you have a microsd card, follow the restore from a soft brick guide from here: http://forum.xda-developers.com/showthread.php?t=1803343
Please note that this guide references the .26 update...if you updated to the .30 update, use that stock rom (I think you can get it from the same place). Just follow the instructions and you should be back at square one-stock. Re-root and reinstall TWRP, then choose a ROM more wisely, by reading the threads to see what is working well.
Click to expand...
Click to collapse
Sorry, no luck with the ZEUS v4. Same happen again. When booting, the first screen hangs....no weel either. Have been reading for 3 days now here on xda and tryed a lot of possible solutions. I cant get TWRP to mount a microsd card, have to rely on the pad itself. So, any other ideas?
okantomi said:
It seems you picked three ROMS with problems to try for your 1st flash. I can't say anything about the Mystical ROM v1 (although it is based on a TF300 JB OTA) but the other 2 just may not boot at all (maniac is old old, and the EOS JB Rom v3 couldn't boot).
If you can try ZEUS v4 (ICS) or unofficial CM10 alphs latest 9/25 build (JB) you would be OK.
IF you are truly stuck, and you have a microsd card, follow the restore from a soft brick guide from here: http://forum.xda-developers.com/showthread.php?t=1803343
Please note that this guide references the .26 update...if you updated to the .30 update, use that stock rom (I think you can get it from the same place). Just follow the instructions and you should be back at square one-stock. Re-root and reinstall TWRP, then choose a ROM more wisely, by reading the threads to see what is working well.
Click to expand...
Click to collapse
Thanks for tips mister, since I dont can find the right version from ASUS I have to ask...in Europe is it the WW version i suppose to use, and its the Firmware not the Source code?
alldog said:
Sorry, no luck with the ZEUS v4. Same happen again. When booting, the first screen hangs....no weel either. Have been reading for 3 days now here on xda and tryed a lot of possible solutions. I cant get TWRP to mount a microsd card, have to rely on the pad itself. So, any other ideas?
Click to expand...
Click to collapse
Why not installing a stock rom (the same version you had before the issues started) with TWRP, that should get you back on track.
Edit: Yes european version should be WW_SKU and please use the firmware not the source.
Got one step further ..or did I? Tryed to put in stock .30 used "fastboot -i 0x0B05 flash system blob" in fastboot usb-mode. Seemd ok until this message arrived: Failed to prosess flash system error (0x17003)
So, close but not there. There are some problem with flashing since other images also refuse to install. What now?

[Q] CWM recovery issue with Rom Manager

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

[Q] from EOS 3.0.5 to Jelly Bean?

I have a xoom wifi. When I bought it, it had the stock HC version of android (Asian). I rooted and flashed Tiamat 3.0.5 ICS rom. I am considering flashing a JB rom, but have encountered some problems. First, I have Clockworkmode v.5.8.3.1 and can't backup because I have problems with this version of cwm detecting my sdcard or something. I read that I should have cwm v.3.2.0.0 or something and don't know how to install an older version of cwm from my Ubuntu 12.04 os. I do have access to Windough$$ 7, but am more comfortable in Linux. My questions are as follows:
1. is JB worth the trouble?
2. how is app compatability with JB? (most important apps == gtasks( and other google stuff) and repligo pdf reader.
3. is there an easy way to get to JB from where I sit now?
Thanks in advance.
You can fastboot another recovery. TWRP and Rogue recoveries work as well as CWM 3.2.0.0. Jellybean is not bad, still some things to be worked out. Maybe just wait for a stable release of EOS4.

[Q] My ace plus won't boot after flashing Kitkat roms and even cwm v6

I have 3 android phones, and the oldest one is getting me crazy..
First flashed a JB rom, after a bunch of troubles, finally got it done.
But then this phone had a little problem, i flashed back to stock and send it for repair.
The phone now is returned and reset to GB. And found that there are many Kitkat roms to flash which is really tempting me to do it.
First, i tried to flash Speed rom, with cwm 6.0.3.5. I got Status 7. Flashed back cwm 5.5 and successful in flashing the rom, but it won't boot and stuck in a white screen.
I googled a lot, searched in XDA, found that someone suggested flashed Kitkat with the latest CWM version or TWRP.
But, none of these works on my phone. This is the first time I got stuck in flashing recovery. Both give me a white screen.
Does the CWM version really matter? or it's just my phone's problem which could not work with android 4.4?
Any help would be appreciated..
thyau said:
I have 3 android phones, and the oldest one is getting me crazy..
First flashed a JB rom, after a bunch of troubles, finally got it done.
But then this phone had a little problem, i flashed back to stock and send it for repair.
The phone now is returned and reset to GB. And found that there are many Kitkat roms to flash which is really tempting me to do it.
First, i tried to flash Speed rom, with cwm 6.0.3.5. I got Status 7. Flashed back cwm 5.5 and successful in flashing the rom, but it won't boot and stuck in a white screen.
I googled a lot, searched in XDA, found that someone suggested flashed Kitkat with the latest CWM version or TWRP.
But, none of these works on my phone. This is the first time I got stuck in flashing recovery. Both give me a white screen.
Does the CWM version really matter? or it's just my phone's problem which could not work with android 4.4?
Any help would be appreciated..
Click to expand...
Click to collapse
if your stock rom is indian or chinese flash stock english rom through odin, then you are good to go
ShadowsDie said:
if your stock rom is indian or chinese flash stock english rom through odin, then you are good to go
Click to expand...
Click to collapse
any english rom would be good?
thyau said:
any english rom would be good?
Click to expand...
Click to collapse
any EUROPEAN rom is good, doesnt matter if it is german or irish, must be european
but i recommend any rom from england, as they usually support most of the languages

Categories

Resources