Database Users

CWM recovery not working on HC 3.2.1

After the OTA 3.2.1 update, CWM Recovery would just not install. After flashing the CWM recovery image on stock 3.2.1 and rebooting into recovery, I get the android guy with the exclamation mark. I saw another person in the CWM thread having the same issue.
I did flash CWM before on HC 3.2 successfully, but for some reason it is not working after the last OTA update.
Any thoughts ?

Any luck on this? I'm trying to root my Xoom 3.2.1 and have no idea what to do and looks like the one click tool has been removed...any direction is better than no direction ;-)
Thanks!!
Faslane

I had this same issue yesterday.
Use adb and fastboot to manually install clockwork again...and then if you need to root you can use one click root.
I would give you the code for fastboot command but I'm not home.
Sent from my ADR6350 using xda premium

Do not use one click root-you'll brick it.
Use the Univetsal Xoom Root.
http://forum.xda-developers.com/showthread.php?t=1242241

okantomi said:
Do not use one click root-you'll brick it.
Use the Univetsal Xoom Root.
http://forum.xda-developers.com/showthread.php?t=1242241
Click to expand...
Click to collapse
Thank you okantomi that's what I meant.
Sent from my ADR6350 using xda premium

well, it seems that you need to immediately boot up into CWM recovery after flashing it without letting your device boot up completely, then you need to root it from there to retain the CWM recovery. This worked for me.

Yazan76 said:
well, it seems that you need to immediately boot up into CWM recovery after flashing it without letting your device boot up completely, then you need to root it from there to retain the CWM recovery. This worked for me.
Click to expand...
Click to collapse
That is exactly right.

Yazan76 said:
well, it seems that you need to immediately boot up into CWM recovery after flashing it without letting your device boot up completely, then you need to root it from there to retain the CWM recovery. This worked for me.
Click to expand...
Click to collapse
Can you expand on this a little bit? I am on stock rom, rooted and unlocked, and running 2.6.36Tiamat_Xoom kernel and build HTJ85B.
IF i do the new update what do I need to do to keep root? Will I have to wipe everything?
Thanks

texasez said:
Can you expand on this a little bit? I am on stock rom, rooted and unlocked, and running 2.6.36Tiamat_Xoom kernel and build HTJ85B.
IF i do the new update what do I need to do to keep root? Will I have to wipe everything?
Thanks
Click to expand...
Click to collapse
these instructions seem to work
http://forum.xda-developers.com/showpost.php?p=17832798&postcount=78

texasez said:
Can you expand on this a little bit? I am on stock rom, rooted and unlocked, and running 2.6.36Tiamat_Xoom kernel and build HTJ85B.
IF i do the new update what do I need to do to keep root? Will I have to wipe everything?
Thanks
Click to expand...
Click to collapse
Yes. What I did is backup everything, flash back to stock, wait for my device to download and install the 3.2.1 update, and finally flash the recovery, root my device, and install the tachi kernel. Restored all my applications after making sure that everything is fine.
I know it looks like a long a process but google market applications restore saved me a lot of time.

Yazan76 said:
Yes. What I did is backup everything, flash back to stock, wait for my device to download and install the 3.2.1 update, and finally flash the recovery, root my device, and install the tachi kernel. Restored all my applications after making sure that everything is fine.
I know it looks like a long a process but google market applications restore saved me a lot of time.
Click to expand...
Click to collapse
To save even more time and get back your app data, first back up aps and data in Titanium Backup and make sure the backup is on your external sdcard, just to be safe. Then, after wiping, and once you have rebooted, reinstall TB and then run a batch restore of missing apps and data. It is much faster and better than letting google restore the apps.

.
Yesterday just rooted my xoom but now i have a problem when i try to flash something or do something in recovery doesnt work it say cant open sd or cant mount sd any help

okantomi said:
To save even more time and get back your app data, first back up aps and data in Titanium Backup and make sure the backup is on your external sdcard, just to be safe. Then, after wiping, and once you have rebooted, reinstall TB and then run a batch restore of missing apps and data. It is much faster and better than letting google restore the apps.
Click to expand...
Click to collapse
Even simpler... fastboot flash just boot, system, and recovery stock images. Leave userdata alone. Allow the update. Don't worry about letting it fully boot.. let it.. no harm.. but no root.
Then flash CWM (using fastboot).. boot to recovery.. CWM univ root. Good to go. Or CWM a different kernel

CARLITOZ18 said:
Yesterday just rooted my xoom but now i have a problem when i try to flash something or do something in recovery doesnt work it say cant open sd or cant mount sd any help
Click to expand...
Click to collapse
You need to have an exernal sdcard for the recovery images to work.

Chipster0 said:
... Fastboot flash just boot, system, and recovery stock images.
Click to expand...
Click to collapse
Do you (or anyone else) have any (US VZ 3G MZ600) stock images later than HMJ37? Moto stopped carrying at HRI66 for some reason

Can't get passed boot logo..

This isn't my very first time with flashing/rooting/etc. but I'm not that adept with it.
Got my S4 2 days ago but managed to get time today to work on it. I rooted successfully and everything was running perfect. I flashed over the newest Beanstalk ROM w/ gapps and it ran fine the first time it ran.
I can't get passed the Samsung Galaxy S4 boot logo every time I try to reboot the phone though...
If I wipe the cache/dalvik and reflash it still doesn't boot passed logo.
If I wipe the cache/dalvik and then wipe data (including the internal SD card, completely wiping it clean), flashing the ROM will work the first time it runs; once I reboot or just power it off then power it back on, stuck at Galaxy S4 logo... I let the ROM run first time through, input only what is needed to get to the home screen (google account/wifi setup/phone name/etc.), then I've tried rebooting it, shutting it down and powering it back up, letting everything update and waiting half an hour and restarting it... all have the same result, stuck at boot logo
I'm using TWRP, I have a recovery for stock but I don't want to use stock.
If anyone can help me out I'd appreciate it.

Try flashing a different compatible kernel.

ObrienDave said:
Try flashing a different compatible kernel.
Click to expand...
Click to collapse
This is EXACTLY what I was about to try... I'm literally reflashing the ROM fresh right now, going to put the kernel on the SD card, then reboot into recovery and wiping cache then flashing the kernel.
Will using a recovery that was made on a different kernel have any effect if I decide to use the recovery? I've heard bad things about flashing the wrong kernel (even though I know the one I'm about to use is the correct one) and really screwing stuff up if not done properly. I just want to make sure I don't screw anything up permanently.
Thanks.

Spazzzin said:
This is EXACTLY what I was about to try... I'm literally reflashing the ROM fresh right now, going to put the kernel on the SD card, then reboot into recovery and wiping cache then flashing the kernel.
Will using a recovery that was made on a different kernel have any effect if I decide to use the recovery? I've heard bad things about flashing the wrong kernel (even though I know the one I'm about to use is the correct one) and really screwing stuff up if not done properly. I just want to make sure I don't screw anything up permanently.
Thanks.
Click to expand...
Click to collapse
Use twrp 2.5.0.2 because if your using 2.6 its bringing problems. Also report this to their thread for better help
Sent from my SPH-L720 using xda app-developers app

Since there are no recovery categories according to this page,
http://forum.xda-developers.com/showthread.php?t=2303917
I don't see where it would matter. No guarantees though.
I do know it is ESSENTIAL to match the type (TW or AOSP) ROM and kernel to avoid major problems.
I also recommend TWRP 2.5.0.2
D/L TWRP from here:
http://techerrata.com/browse/twrp2/jfltespr

ObrienDave said:
Since there are no recovery categories according to this page,
http://forum.xda-developers.com/showthread.php?t=2303917
I don't see where it would matter. No guarantees though.
I do know it is ESSENTIAL to match the type (TW or AOSP) ROM and kernel to avoid major problems.
I also recommend TWRP 2.5.0.2
D/L TWRP from here:
http://techerrata.com/browse/twrp2/jfltespr
Click to expand...
Click to collapse
How do you go about installing TWRP? I used Goomanager and installed it from there when I was following the rooting guide

Spazzzin said:
How do you go about installing TWRP? I used Goomanager and installed it from there when I was following the rooting guide
Click to expand...
Click to collapse
Flashing a different kernel didn't do anything, I still keep getting stuck at the boot logo :/

Spazzzin said:
How do you go about installing TWRP? I used Goomanager and installed it from there when I was following the rooting guide
Click to expand...
Click to collapse
Just flash it by odin by the link provided above. Make sure to use the tar file v 2.5.0.2
Sent from my SPH-L720 using xda app-developers app
---------- Post added at 09:22 PM ---------- Previous post was at 09:19 PM ----------
Spazzzin said:
Flashing a different kernel didn't do anything, I still keep getting stuck at the boot logo :/
Click to expand...
Click to collapse
By the way can you provide the steps and which files you flashing. Also redownload everything could be a bad download. Make sure to download them in computer and transfer them to your sd card
Sent from my SPH-L720 using xda app-developers app

I did a fresh install of the LiquidSmooth ROM and it's not hanging at boot logo whenever I reboot, and everything is working well. I suppose I'll stick with this for a while.
For my steps trying Beanstalk:
Boot into recovery (TWRP 2.6.0.0)
Factory reset;wipe cache/dalvik
Format Data
Factory reset;wipe cache/dalvik
Install ROM + Gapps
Wipe cache/dalvik
Reboot
I then tried doing that exact process, after letting it boot once I rebooted into recovery and flashed KT Kernel and wiped then rebooted and it hung at boot logo.
I did it again but I installed ROM + Gapps + Kernel then wiped then rebooted and it still hung at boot logo.
I'll download and prepare a new install of Beanstalk and give it another try tomorrow. I'll make sure to backup Liquid in case I want to switch back.
Thanks again for the help!

Glad it's working out for you.

If I may ask here; how do I know if a certain kernel is compatible with a ROM? I know to match the version (4.2, 4.3. etc,) and base (AOSP/ TW) but is there anything else specific that I need to watch out for that could cause problems with flashing a kernel on a ROM?

Spazzzin said:
If I may ask here; how do I know if a certain kernel is compatible with a ROM? I know to match the version (4.2, 4.3. etc,) and base (AOSP/ TW) but is there anything else specific that I need to watch out for that could cause problems with flashing a kernel on a ROM?
Click to expand...
Click to collapse
Not really unless the rom dev for some reason doesn't recommend using a certain one. Kernels will act differently for everyone even on the same device with the same rom. Just need to flash them and find out which one works the best for you (battery life, overheating, smoothness, etc).
Always have a backup handy just in case something doesn't work right.

[Q] uninstalling slimkat (cm11)

Hi guys, need some help here. I'm sure this has been asked before but i just couldn't find any
Installed slimkat 20140406-0134 rom (cm11) last night and it's basically working. But I'm still not feeling comfortable using it as there's still bugs around. So thought of going back to cm7.2 for now. But for the life of me couldn't figure out how to get to the tool section so I can re-partition it back to ext3!!!
All I could get in to is twrp recovery and that's it. how do I even get into the bootmenu section where I can choose recovery, cpu settings, tools, etc? There's no red Moto logo with blue LED at boot up anymore
Is there any uninstall instruction somewhere, or perhaps someone should write one?

44 viewers but no reply
any idea if i can install some sort of apps to achieve the same end? like a wipe app to re-partition it to ext3, and then an older recovery to install cm7 rom, or restore my cm7 backup?
don't really want to just try and see what will happens. also trying to avoid flashing sbf and start from scratch.....
edit: will aromawiper work? reboot to twrp recovery 2.6.3.0, aromawipe to ext3 and then flash cm7.2 rom straight after? expert opinion and advice please.
edit 2: oh well, tried it and didn't work. might be because i didn't install an older, compatible recovery before i rebooted. stuck at red moto logo and had to flash sbf and start all over again......
case closed...........

jh20 said:
44 viewers but no reply
any idea if i can install some sort of apps to achieve the same end? like a wipe app to re-partition it to ext3, and then an older recovery to install cm7 rom, or restore my cm7 backup?
don't really want to just try and see what will happens. also trying to avoid flashing sbf and start from scratch.....
edit: will aromawiper work? reboot to twrp recovery 2.6.3.0, aromawipe to ext3 and then flash cm7.2 rom straight after? expert opinion and advice please.
edit 2: oh well, tried it and didn't work. might be because i didn't install an older, compatible recovery before i rebooted. stuck at red moto logo and had to flash sbf and start all over again......
case closed...........
Click to expand...
Click to collapse
you can flash cm10 to get the boot menu to format to ext3 then flash to cm7.2.
Thats what i did when i tested cm11.

Or use Aroma wiper to format to ext3 and flash CM7.2.
Sent from my Nexus 7 using Tapatalk

aperture said:
you can flash cm10 to get the boot menu to format to ext3 then flash to cm7.2.
Thats what i did when i tested cm11.
Click to expand...
Click to collapse
thanks. i'll remember that next time. don't know why i didn't think of that. panic striken maybe
hotdog125 said:
Or use Aroma wiper to format to ext3 and flash CM7.2.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
that's exactly what i did but didn't work. aromawiper seems to have worked properly but twrp 2.6.3.0 keep saying "no os installed" after i installed the gb rom and tried to reboot. tried maniac's cm7.2 and an older wiui gingerbread rom. i thought it might be a hickup and rebooted anyway and that was it.
don't know what went wrong there. has anyone actually tried this method before and got it to work?
edit: imho twrp is not worth it. it rebooted 8-10 times on me after installing cm11 and tried to get back into recovery to flash gapps. also other problems like blank backup files and my failures to install rom problem. they should have stuck to cwm until the problems are fixed.
edit 2: and i think removing bootmenu is not a good idea. more steps to take if you want to go back to cm7.2.

[Q] Where is the kernel files for CM11 stable?

Long story short a custom kernel completely screwed up the graphics on my N4 CM11 so I'm trying to flash the original kernel from the ROM which is NOWHERE to be found in the cyanogen site.
Anyone got a link?

MGREX said:
Long story short a custom kernel completely screwed up the graphics on my N4 CM11 so I'm trying to flash the original kernel from the ROM which is NOWHERE to be found in the cyanogen site.
Anyone got a link?
Click to expand...
Click to collapse
Just reflash the rom.
If you don't want to, tell me what version of cm11 your'e running and i'll make a flashable kernel zip :good:

or pull the boot.img out of the rom zip and use the flashify app to flash it. the boot.img is the kernel. but honestly, it sounds like you have absolutely no idea what you are doing. if you have any questions, please ask, im willing to help. can you explain what happened?

Yeah I screwed up, didn't notice it wasn't CAF
22sl22 said:
If you don't want to, tell me what version of cm11 your'e running and i'll make a flashable kernel zip :good:
Click to expand...
Click to collapse
It's 11.0-InstallerXNPQ08Q
Thanks!

So after a reboot to enter recovery my N4 is stuck in the splash screen with the white google logo.
This is getting worse by the minute...

MGREX said:
So after a reboot to enter recovery my N4 is stuck in the splash screen with the white google logo.
This is getting worse by the minute...
Click to expand...
Click to collapse
just fastboot flash a recovery, this shouldnt an issue. did you flash a recovery before, or just boot one? it makes a difference if it sticks around or not.

simms22 said:
just fastboot flash a recovery, this shouldnt an issue. did you flash a recovery before, or just boot one? it makes a difference if it sticks around or not.
Click to expand...
Click to collapse
I'm able to force-access recovery and CWM but that's it, once it boots it gets stuck on the splash screen, and thanks to the lack of a SD port I'm unable to easily load a kernel or ROM, and despite having the android SDK I'm unable to sideload the file through adb on Windows.
Any ideas? besides trying the adb through Linux (I'm doing that now)

Here's the flashable kernel zip taken from Snapshot M7 build :good:

Okay now it gets stuck in the cyanogenmod boot animation
Any ideas? that don't involve wiping everything I mean

simms22 said:
or pull the boot.img out of the rom zip and use the flashify app to flash it
Click to expand...
Click to collapse
Can't do since it no longer boots into android, but I tried to do what you say and sideload the zip but I get a "installation aborted" error on CWM

MGREX said:
Can't do since it no longer boots into android, but I tried to do what you say and sideload the zip but I get a "installation aborted" error on CWM
Click to expand...
Click to collapse
What about TWRP?
Sent from my Nexus 4 using Tapatalk

22sl22 said:
What about TWRP?
Click to expand...
Click to collapse
You mean installing TWRP?
BTW that problem is with the kernel I assembled using a CM11 ROM, your zip actually does boot into cyanogenmod but it gets stuck in the CM boot animation

Okay I'm not sure why or how, but this time it booted alright:laugh::highfive::good:
Thank you guys for the assistance, I'll do a full backup in case it decides to crash again so I can do a total wipe and flash a new ROM from scratch

MGREX said:
Okay I'm not sure why or how, but this time it booted alright:laugh::highfive::good:
Thank you guys for the assistance, I'll do a full backup in case it decides to crash again so I can do a total wipe and flash a new ROM from scratch
Click to expand...
Click to collapse
No problem
Do a titanium backup that backs up all your apps with data. Always have a backup so if things do go wrong you can just wipe and restore apps afterwards :good:
Sent from my Nexus 4 using Tapatalk

[Q] Custom Recovery Lost after Flashing cm-11-20141028-NIGHTLY-mb52x.zip

Hi all, I met a problem after flashing cm-11-20141028-NIGHTLY-mb52x.zip.
I cannot enter Custom Recovery (TWRP) any more. Other functions are OK, but I cannot upgrade to new ROM now.
Is there a simple way to restore Custom recovery in CM11?
Otherwise, I will have to use the method: "flashing stcok ROM (Android 2.3) -> root -> 2nd Init -> flashing Custom recovery", to restore it.
Thanks in advance.

hi, don't know if you still need an answer but you can try this:
http://forum.xda-developers.com/showthread.php?t=2708771

Hi jh20, thanks for the information.
I checked the post you provided. However, my problem is that I cannot enter the Custom Recovery anymore, let alone flashing another ROM.
jh20 said:
hi, don't know if you still need an answer but you can try this:
http://forum.xda-developers.com/showthread.php?t=2708771
Click to expand...
Click to collapse

perhaps i should explained a little more. these are based on memory as i haven't done these a while now.
cwm recovery had been permanently removed from cm11, and you can only flash cm10 and not anything earlier (cm7 or cm9) with cm11's twrp because of ext4 partition. so as long as you can still get into twrp, you can flash cm10 which still has both twrp "and" cwm recovery. cm10's cwm recovery allows you to repartition it back to ext3 and hence allows you to flash cm7.
i did a little google on how to revert from cm10, and here are the hits:
https://www.google.com.au/search?q=...hannel=sb&gfe_rd=cr&ei=rXBiVP7-GqGN8Qfiz4HYCw
and the first one on xda:
http://forum.xda-developers.com/showthread.php?t=2095518
if you need more just read the other posts. hope they help.

Thanks a lot, jh20.
I think I made a mistake in the post, that I was not use CWM recovery in CM11, it is TWRP recovery instead. I've update my post to reflect this.
So the problem is that I cannot enter TWRP recovery any more, and cannot flash another ROM or anything via TWRP recovery.
Is there a simple way to restore TWRP recovery, otherwise I have to start from scratch by flashing stock ROM, ...
I'm not trying to go back to CM7.2.
jh20 said:
perhaps i should explained a little more. these are based on memory as i haven't done these a while now.
...
if you need more just read the other posts. hope they help.
Click to expand...
Click to collapse

swest said:
So the problem is that I cannot enter TWRP recovery any more, and cannot flash another ROM or anything via TWRP recovery.
Is there a simple way to restore TWRP recovery, otherwise I have to start from scratch by flashing stock ROM, ...
Click to expand...
Click to collapse
Sorry, not with my knowledge. So unless some experts/developers here have any ideas, you might have to start from scratch.