Database Users

[A] Bootloop after flashing a ROM via 3.0.0.5 Recovery image.

What you did .. .. ..
Okay so you've rooted your newly bought MyTouch4G, and you've made sure that s=off and you've flashed Clockwork ROM manager's recovery image that you got from the market. That is all the correct order. But when you flashed a ROM you got stuck in a bootloop.
Am i screwed???
Don't worry you are just in a "soft brick mode", or "limp mode" if you will.
What happened? Why is it doing this?
The Image that you downloaded and installed 3.0.0.5 is for 2.3 (Gingerbread) based ROMs only. [n3rd note] these are ext4 style ROMS. They act and store information differently than 2.2 which are Ext3 ROMs[/n3rd note].
This could also be caused by trying to flash a 2.3 using a older 2.x.x.x version of the Recovery Image. Those will only support the Ext3 style ROMs, which are FroYo (2.2) based ROM.
Okay what do i need to do to fix it, there are two methods.
This is Method one it's the older version.
You must use this method if you do not have the engineering screen
If you are using the 3.0.0.5 Recovery image
To fix your problem you need to flash any 2.3 based ROM, for time sake i will recommend Cyanogen(mod). Link to Cyanogen(mod)'s CM7RC4. While you are there you need to also store the G/Apps.
If you are using the 2.x.x.x Recovery Image
To fix your problem you need to flash any 2.2 based ROM, for time sake i will recommend RoyalGlacier Thread can be found here
- Question: How do i find out what Recovery image i am using
- Answer: Boot the phone into the recovery mode. We'll touch on that in a little bit
Now when you download both of those files you also need to store them to SDCard.
NOTE: If you are using 2.x.x.x and going to flash RoyalGlacier you will not need the g/apps. They have included this in their ROM, and MAKE sure to follow their specific directions for installing the ROM.
- Question: Now how in the world i am going to do that since my phone is in bootloop.
Answer:
Two ways one can do that
1) use a SDcard reader and just plug the card into a main USB port.
2) Mount the SDCard in the phone via the Recovery Image. *** i'd recommend this method since you are going to need to be in recovery anyway ***
Pull the battery from the phone an put it back in, then put the back on the phone. turn the phone on holding the power button along with the volume down rocker button. That will boot the phone into the HBoot (Engineering) Screen. From there you will see an option that says "recovery" [this is what i mentioned earlier, about the different versions] use the volume rocker to select it, then tap the power button to select it. The phone will reboot into what is called the recovery image. From there you will select "mount" then USB. That will mount the SDCard to the Computer.
If you are using the 3.0.0.5 Recovery image
Once you have move Cyanogen(mod) and the g/apps to the SD card unmount the SDCard.
Then navigate to "wipe data/factory reset" you will want to wipe the phone. That will format everything to a fashion that can be written over w/o problems.
Then navigate to "install .zip from sdcard" > " choose .zip " > then flash the main Cyanogen(mod) ROM. Then do the same but flash the g/apps that you downloaded.
Once those are done you can re-boot the phone. That will boot you into cyanogen.
If you are using the 2.x.x.x Recovery image
Please use the link i supplied above to get that ROM up and running once it is done, according to their instructions come back here.
Now i understand that may or may not want Cyanogen nor RoyalGlacier on your phone. Well take care of that
What can i do to prevent this from Happening again?
Once you are up and running (make sure to log into your Google Account) go to the market and download Clockwork ROM manager again, and re-flash the recovery image.
Once you are done with that i HIGHLY suggest upgrading to the newest 3.0.0.6 Recovery image. You can do that one of two ways.
one way is to flash True_Blues method for installing 3.0.0.6 recovery image. Use this thread..
This is the way that i would personally recommend.
The second way is download the 3.0.0.6 recovery image, which i've attached and flash it via the ADB commands. If you want to do it this way you do not need to download Clockwork Rom Manager, you can "just flash it". If you need help with that, if you are using Windows or Mac, see my signature for True_Blue's method on EZ ADB. If you are using Unbutu 10.10 use this This Method to get ADB running. This is the method i used to ADB running on my Linux NetBook.
Download the file that i've attached and store just the recovery image from the .zip to the SDCard, from the ADB commands type
adb shell
su
flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
More information on this process can be found here
That will flash the newest recovery image to your phone
Once you have installed the 3.0.0.6 ROM Manager you can wipe and flash ANY MyTouch4G ROM that you want. It will handle both 2.2 (ext3) and 2.3 (ext4) ROM formats.
This is the New Method - Which is a little easier.
AND YOU MUST HAVE THE ENGINEERING HBOOT
Thanks to TeeJay for inspiring this.
I am going to assume that since you have the Engineering Screen you are more familiar with what you are doing so i'll be more to the point with this walk-through.
you will need to have ADB up and running for this method.
1) Download the attached file and store just the .img to your folder from which you preform all of your ADB commands
2) plug the phone into the computer
3) boot the phone into HBoot
4) from the ADB commands change the drive to the folder where you stored the recovery image.
5) type these commands
Code:
fastboot flash recovery recovery.img
the screen should say something to the degree of
Code:
sending 'recovery' (3426 KB)... OKAY [ 1.172s]
writing 'recovery'... OKAY [ 0.797s]
finished. total time: 1.969s
6) then select "bootloader"
7) navigate to "reboot recovery"
8) flash your ROM of choice.
9) enjoy your ROM of choice.
Please feel free to use this in your signature or link people back to. If you feel i made an error in this post please PM and i'll edit it accordingly.
If this thread has helped you solve your problem please hit the "thanks" button.
THE RECOVERY IMAGE HAS BEEN UPDATED TO THE NEWEST ONE.

good summary. originally when i flashed cm7 I had to search a bit to come up with what you said above. one addition, CWM lets you mount sd storage to usb so you can copy files to sdcard (say the recovery image). then update CWM 3.0.0.6 with ADB.

leo221 said:
good summary. originally when i flashed cm7 I had to search a bit to come up with what you said above. one addition, CWM lets you mount sd storage to usb so you can copy files to sdcard (say the recovery image). then update CWM 3.0.0.6 with ADB.
Click to expand...
Click to collapse
Added that method as well.

May want to mention that the opposite could be true as well > same boot loop but from flashing 2.3 rom with recovery 2.5.1.2

Thank you for this!! Exactly what I needed...!

austengeist said:
Thank you for this!! Exactly what I needed...!
Click to expand...
Click to collapse
Glad it helped, just make sure to hit the "Thanks" button in the first post.

dang man you're the Q&A champ, every time i'm on this you're answering questions.
well this worked like a charm, idk why people on xda always make things more complicated than it has to be.

option94 said:
May want to mention that the opposite could be true as well > same boot loop but from flashing 2.3 rom with recovery 2.5.1.2
Click to expand...
Click to collapse
Added.
aalsmadi1 said:
dang man you're the Q&A champ, every time i'm on this you're answering questions.
well this worked like a charm, idk why people on xda always make things more complicated than it has to be.
Click to expand...
Click to collapse
Well i work in the Imported Automotive parts. My job requires me to basically sit around and answer the phone when it rings. We have our own "call center" room. I just pick up the phone and answer question and sell parts. Like right now i'm working on a engine rebuild kit for a 1975 2Ton Mercedes Bens..... so i get some free time from time to time, and XDA is one of a few sites they allow me to visit.... BGR/ Android and Me, Android Central are the others....
I can see why some people blow up, spend +$200.00 on a phone then turn around and blow through something w/o taking the time to read something and then you get stuck in a bootloop.... i can see why people go bonkers. But slowing down and reading would solve alot of problems. Heck i've got 3 great threads in my signature that would solve alot question that one could have with a new device.

fixed my problem

Thread stuck.

Great guide!

Same issue, except i flashed 3.0.0.6 beforehand to prevent any problems. Iced Glacier flashed okay, I just didn't care for it much. Ive wiped all the necessary parts prior to flashing as I would before flashing any roms. Ive managed to retrieve and restore a previous back (I can haz backups) so Im not stuck. I would like to be in the cool kids cyanogen club. Any ideas?

DHSdrone said:
Same issue, except i flashed 3.0.0.6 beforehand to prevent any problems. Iced Glacier flashed okay, I just didn't care for it much. Ive wiped all the necessary parts prior to flashing as I would before flashing any roms. Ive managed to retrieve and restore a previous back (I can haz backups) so Im not stuck. I would like to be in the cool kids cyanogen club. Any ideas?
Click to expand...
Click to collapse
Meaning you want to run Cyanogen(mod)? Well jump over to their site and download the ROM of your picking; Nightlies are alpha builds, and the RC's are beta builds. I've ran both and both are extremely stable. I have links supplied in the first post. and directions for that matter. just make sure to do a nandroid backup before wiping and flashing.

Thanks ....Saved ME LIFE

Posting so I can see the "thanks" button. Doubley thanks you saved my bacon....err phone!! Hmmmm bacon!

Ok I am having one Problem PLEASE HELP!!!
When I click "wipe data/factory reset" it just shows the clockwork icon (hat and arrow) and nothing happens.
In fact, this happens with all of the options in the clockwork recovery.
I am running clockwork 3.0.0.5. I had CM7 and I did something stupid, tried flashing another ROM via rom manager....I did back up everything though.
Please tell me I am not bricked!!!

b0rnsusp3ct said:
Ok I am having one Problem PLEASE HELP!!!
When I click "wipe data/factory reset" it just shows the clockwork icon (hat and arrow) and nothing happens.
In fact, this happens with all of the options in the clockwork recovery.
I am running clockwork 3.0.0.5. I had CM7 and I did something stupid, tried flashing another ROM via rom manager....I did back up everything though.
Please tell me I am not bricked!!!
Click to expand...
Click to collapse
Pull the battery. Hold vol down power on them restore cm7. Then flash cwm 3.0.0.6.
Sent from my Inspire 4G using XDA Premium App

b0rnsusp3ct said:
Ok I am having one Problem PLEASE HELP!!!
When I click "wipe data/factory reset" it just shows the clockwork icon (hat and arrow) and nothing happens.
In fact, this happens with all of the options in the clockwork recovery.
I am running clockwork 3.0.0.5. I had CM7 and I did something stupid, tried flashing another ROM via rom manager....I did back up everything though.
Please tell me I am not bricked!!!
Click to expand...
Click to collapse
What button are you pressing to select the option? you should just use the trackpad.

Loll...wow, I am such a noob i def. shouldn't be rooting or anything.
Thanks so much!

b0rnsusp3ct said:
Loll...wow, I am such a noob i def. shouldn't be rooting or anything.
Thanks so much!
Click to expand...
Click to collapse
Why do you say that?

CWM Problems

UPDATE: To fix 3.0.2.4 from not formatting /system
Open rom manager and select settings, and check erase recovery. hit menu again and select clear cache, then flash 3.0.2.4 again.
now if your in recovery and you cant boot back up to use rom manager, use the file below. It will allow you to restore your backup then once booted back up use the method above to fix 3.0.2.4.
The reason im leaving custom over 3.0.2.4 is bc i know fastboot flash with this one will allow you to restore without wiping recovery or clear cache or anything else.
http://www.mediafire.com/file/b8ejhqbf3tgnsoe/recovery.img - this is CMW 3.0.1.4 just altered for installing zips. linking for people needing a recover img to boot up
To install:
1. If in recovery, open ur terminal on ur pc and type adb reboot boatloader
2. Once in bootloader it will load fast boot and say fastboot usb in red
3. cd to the folder with fastboot.exe and also place recover.img in that folder
4. then enter fastboot flash recovery recovery.img
5. adb reboot recovery
6. restore your backup and boot up

RafficaX said:
Little FYI for all, cwm recovery wont format system on a restore. made a backup, tried a flash and went to restore and it fails formatting system.
So be careful with flashing and all bc yo may not be able to restore currently with cwm.
UPDATE: format system in menu also fails! be careful bc you pretty much cant restore or flash atm!
Click to expand...
Click to collapse
Oh how I miss Amon_Ra

jlevy73 said:
Oh how I miss Amon_Ra
Click to expand...
Click to collapse
im really hoping Amon_Ra does do his recovery on T-Bolt. I like Rom Manager and its features but would rather loose features for stability and reliability on each use.

RafficaX said:
im really hoping Amon_Ra does do his recovery on T-Bolt. I like Rom Manager and its features but would rather loose features for stability and reliability on each use.
Click to expand...
Click to collapse
QFT
can't wait for amon-ra

raffica, what version of CWM worked for you?

MYxdaUSERNAME said:
raffica, what version of CWM worked for you?
Click to expand...
Click to collapse
A custom compiled one 3.0.1.4, working on porting The Ultimate Droid to T-bolt so blackdroid also compiled cwm to make sure it would install the zip but has working restore. i messaged koush on cwm twitter about the issue so hopefully he fixes it quickly. only problem is the one im running you need to flash through fastboot with adb.

Thanks for the heads up I agree I always loved CWM on my N1 but it started giving me all kinds of grief for several different reasons so I finally went to Amon Ra.

RafficaX said:
A custom compiled one 3.0.1.4, working on porting The Ultimate Droid to T-bolt so blackdroid also compiled cwm to make sure it would install the zip but has working restore. i messaged koush on cwm twitter about the issue so hopefully he fixes it quickly. only problem is the one im running you need to flash through fastboot with adb.
Click to expand...
Click to collapse
Can you help me out and provide it because right now i cant even boot

RafficaX said:
A custom compiled one 3.0.1.4, working on porting The Ultimate Droid to T-bolt so blackdroid also compiled cwm to make sure it would install the zip but has working restore. i messaged koush on cwm twitter about the issue so hopefully he fixes it quickly. only problem is the one im running you need to flash through fastboot with adb.
Click to expand...
Click to collapse
isnt UD banned on these forums?
just curious dont flame me or anything! cuz when a Ud rom hit the inc the thread was deleted in minutes

superchilpil said:
isnt UD banned on these forums?
just curious dont flame me or anything! cuz when a Ud rom hit the inc the thread was deleted in minutes
Click to expand...
Click to collapse
yeah, if you go on their forums all they do is flame XDA left and right. But I find it funny since their roms take advancements from XDA developers and then they incorporate it into their roms...

nosympathy said:
yeah, if you go on their forums all they do is flame XDA left and right. But I find it funny since their roms take advancements from XDA developers and then they incorporate it into their roms...
Click to expand...
Click to collapse
See that's what I thought, but wasn't sure
Sent from my ADR6300 using XDA Premium App

Yes Clockwork 3.0.2.4 is borked on Thunderbolt. I've been helping people on AndIRC's thunderbolt channel all day. Install 3.0.2.2, it's given me no problems.

jgrimberg1979 said:
Can you help me out and provide it because right now i cant even boot
Click to expand...
Click to collapse
I ran into the same problem. I tried to do a restore and got stuck. I used an sd card reader and put the 3rd file from the root thread PG05IMG.zip on the root of my sd card. I then put the card back in. Rebooted into recovery holding the volume down and the power button. It reflashed the file automatically and I followed the steps from 7 on to regain root. Worked for me, but now I have to start over. Hopefully they will get CWM working again. I will be much more careful about what I delete from now on. I think I will freeze it in TiBackup first to make sure everything is still working correctly. Hope this helps.

lynseyw said:
I ran into the same problem. I tried to do a restore and got stuck. I used an sd card reader and put the 3rd file from the root thread PG05IMG.zip on the root of my sd card. I then put the card back in. Rebooted into recovery holding the volume down and the power button. It reflashed the file automatically
Click to expand...
Click to collapse
This is the exact procedure I used when the same thing happened on my N1

i added the recovery.img i used to OP with instructions for those stuck in recovery or bootloader.

jeffnucci said:
Yes Clockwork 3.0.2.4 is borked on Thunderbolt. I've been helping people on AndIRC's thunderbolt channel all day. Install 3.0.2.2, it's given me no problems.
Click to expand...
Click to collapse
Latest Rom manager is 3.0.1.3 sorry if I am missing something I am a bit of a clockwork noob.
Sent from my ADR6400L using XDA App

miketoasty said:
Latest Rom manager is 3.0.1.3 sorry if I am missing something I am a bit of a clockwork noob.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Newest Rom Manager is 3.0.1.3 but the newest ClockworkMod Recovery for the tbolt is 3.0.2.4
Under flash clockworkmod recovery it stats the current and latest recovery.

My battery died and am in the same position. Got an expensive paperweight at the moment. I'll try to get another battery today and give this a try. After fooling around with it last night, the computer wouldn't even recognize the phone. Ughh!

RafficaX said:
Newest Rom Manager is 3.0.1.3 but the newest ClockworkMod Recovery for the tbolt is 3.0.2.4
Under flash clockworkmod recovery it stats the current and latest recovery.
Click to expand...
Click to collapse
Good call just checked and 3.2 does wipe date and cache properly.
Sent from my ADR6400L using XDA App

miketoasty said:
Good call just checked and 3.2 does wipe date and cache properly.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Where did you get 3.2? 3.0.2 you mean?

[Q] Clockworkmod recovery disappears after reboot

I have looked through all clockworkmod recovery topics, but it seems I am the only one with this issue?
I have a US Xoom wifi-only, HMJ37, with an official 3.1 OTA. Yesterday I unlocked my Xoom, flashed the latest Recovery image(but also a previous version) of CWM. Then I typed fastboot reboot and I could get into the CWM recovery. Nice, no problems. Then I rebooted again, everything works fine and my Xoom works fine. Then I reboot again in recovery and I suddenly get the stock Android Recovery! I flashed it again and the same problem, after the first reboot I have CWM. Reboot to android and reboot again in recovery and I get the stock Android recovery again!
Who knows what is going wrong here? What am I doing wrong or what can this be?

If you flashed CWM 3.2.0.0, that may be your problem. Look at this thread > http://forum.xda-developers.com/showthread.php?t=1074979
Note in the last several pages that some posts were having the same problem as you. I flashed back to 3.0.2.8, and it solved my problem.

Thanks cam30era, I thought I have tried 3.0.2.8 already but I will give it a try this evening and let you know.

olafski72 said:
I have looked through all clockworkmod recovery topics, but it seems I am the only one with this issue?
I have a US Xoom wifi-only, HMJ37, with an official 3.1 OTA. Yesterday I unlocked my Xoom, flashed the latest Recovery image(but also a previous version) of CWM. Then I typed fastboot reboot and I could get into the CWM recovery. Nice, no problems. Then I rebooted again, everything works fine and my Xoom works fine. Then I reboot again in recovery and I suddenly get the stock Android Recovery! I flashed it again and the same problem, after the first reboot I have CWM. Reboot to android and reboot again in recovery and I get the stock Android recovery again!
Who knows what is going wrong here? What am I doing wrong or what can this be?
Click to expand...
Click to collapse
Without a rooted boot.img if will keep deleting The recovery. You can also delete the recovery-boot.p file from the system folder to stop it.
Sent From My Evo

olafski72 said:
Thanks cam30era, I thought I have tried 3.0.2.8 already but I will give it a try this evening and let you know.
Click to expand...
Click to collapse
Bwcorvus is right.
Sent from my ADR6300 using Tapatalk

I have flashed with 3.0.2.8, with my Xoom rooted. Again, the first attempt was succesfull, I came into the CWM menu. I rebooted again to Android. Rebooted with the Sirius Fastboot in Recovery, but there it was again, the stock recovery!
I have not deleted the recovery-from-boot.p since that sounds kind of scary? What can go wrong? When I delete it, that will stop the stock recovery and bring me into the CWM recovery?
Someone also told me I need a SDcard. Is this true and what should I do with it then? The img is on my PC in the same folder as the ADB tools. So why should I need the SDcard for then?

You must have a SD card for CWM.
Sent from my Xoom using Tapatalk

Thanks. So I don't need to do anything with it? Just stick it in there? Do I need to format it in some way? The SDcard is not supported in 3.1 yet, is it? I need the Tiamat kernel for it. But I cannot flash without the CWM. Or just stick it in there and flash recovery again? Which I did and again the first time it worked, after reboot it did not anymore and I am back to stock recovery.
When I reboot with Sirius to recovery, I still need USB debugging on but I do not need to attach it to my PC with the USB cable? I have tried it all, but just need to know to this ;-)
And what about deleting(renaming) recovery-from-boot.p ? Is it safe?

olafski72 said:
Thanks. So I don't need to do anything with it? Just stick it in there? Do I need to format it in some way? The SDcard is not supported in 3.1 yet, is it? I need the Tiamat kernel for it. But I cannot flash without the CWM. Or just stick it in there and flash recovery again? Which I did and again the first time it worked, after reboot it did not anymore and I am back to stock recovery.
When I reboot with Sirius to recovery, I still need USB debugging on but I do not need to attach it to my PC with the USB cable? I have tried it all, but just need to know to this ;-)
And what about deleting(renaming) recovery-from-boot.p ? Is it safe?
Click to expand...
Click to collapse
You need the Tiamat kernel to be able to access the SD card from the OS, once it's booted. But you can access the SD card from CWM without the Tiamat kernel, although I don't know what good it would do you. If you really want to use this thing, you should root and install the Tiamat kernel.
There are lots of threads in the development section which will help you. Make sure that you read the appropriate thread(s) for your type of Xoom, and your country. If there is anything that you don't understand, be sure to ask questions in the appropriate thread.

cam30era said:
You need the Tiamat kernel to be able to access the SD card from the OS, once it's booted. But you can access the SD card from CWM without the Tiamat kernel, although I don't know what good it would do you. If you really want to use this thing, you should root and install the Tiamat kernel.
Click to expand...
Click to collapse
I want to install the language pack and the Tiamat kernel. If I need to flash recovery again and again, this is quite annoying. I just want it to work ;-)
There are lots of threads in the development section which will help you. Make sure that you read the appropriate thread(s) for your type of Xoom, and your country. If there is anything that you don't understand, be sure to ask questions in the appropriate thread.
Click to expand...
Click to collapse
I have looked, but did not find the same problem yet.
And what about renaming recovery-from-boot.p ? I read other topics about it as well, but still anxious to do so.

olafski72 said:
I want to install the language pack and the Tiamat kernel. If I need to flash recovery again and again, this is quite annoying. I just want it to work ;-)
I have looked, but did not find the same problem yet.
And what about renaming recovery-from-boot.p ? I read other topics about it as well, but still anxious to do so.
Click to expand...
Click to collapse
We have a misunderstanding. You need to root your Xoom and install a Tiamat kernel to get SDCard support. You need to refer to the appropriate thread(s) in the development section to do this. You need to find a thread that is for your country, your type of Xoom (3g+wifi, or wifi only), and the version of Honeycomb that is currently running on your Xoom (3.0 or 3.1). Hope this helps.
Sent from my Xoom using Tapatalk

We have a misunderstanding. You need to root your Xoom and install a Tiamat kernel to get SDCard support.
Click to expand...
Click to collapse
Hm, I have copied the language pack zip file on my sdcard(via my PC and my X10 phone :-D ) and then put it back in my Xoom. I have not the Tiamat kernel yet. This is a Xoom US wifi version, HMJ37, it came with 3.0 but I got 3.1 OTA(although I live in the Netherlands). Then I flashed CWM and rebooted in recovery. I choose to install zip from SDcard and the language pack.zip was there. With CWM I probably CAN browse on my SD without the Tiamat. I installed and rebooted. Unfortunately it got stuck in the animation screen. I rebooted (power button and vol up button) and when Motorola logo showed I pressed vol down. I came in the stock recovery again and did a factory reset. This worked fine and it reboot again. When I went through the wizard succesfully, it surprised me too that the language pack was succesfully installed. I have a Dutch version now and finally a Dutch dictionary for my keyboard. And I am very happy.
Since I have put the Tiamat kernel on my sdcard as well, I could flash the Tiamat kernel the same way. I can flash CWM again(AGAIN!) and install the ZIP from the SD like I did with the language pack. But I am a bit scared to do so.... yet

You need to follow the instructions in this thread > http://forum.xda-developers.com/showthread.php?t=1078019
Read the OP, and make sure that you fully understand it. If you have questions, be sure to ask them on that thread. If you decide to proceed, be sure that you understand and follow EXACTLY each step. No shortcuts.
Also, you should not go any further if you can not afford (emotionally or financially) to brick your Xoom. While it is unlikely to happen, you must accept that it could happen before you proceed.
Good luck.

Thanks, I will look at the thread. I think I have all requirements (3.1, root, wifi only, us model) to do it. But I certainly will have a look. I don't wanna brick my Xoom and go boom.

I have just read this link you posted, but this is about rooting?! I have unlocked and rooted my 3.1 already like this. With a different root tool, but in the same way. That is not the issue. The issue is that I can(!) flash CWM and the first(!) time I reboot I can(!) enter CWM and do all you can in CWM. After I reboot again and go to recovery, the stock Android recovery is back.
The only thing I want is the Tiamat kernel now. It is on my sdcard. So I will flash CWM one more time, reboot into recovery again, and then flash the tiamat kernel into it. But I am in doubt whether I should. I will sleep over it.
Bu the main problem, as mentioned in topic subject, is that CWM will(!) install succesfully and starts the first time, but disappears after the first reboot (in CWM).

Sorry, I didn't understand from your previous posts that you were rooted. Follow the instructions in the OP for the Tiamat 1.4.4 kernel thread.
Sent from my Xoom using Tapatalk

No problem, Thanks for all your help. In here the same problem is described: http://forum.xda-developers.com/showthread.php?t=761398
Although in here the problem is a Nexus and no Xoom. But they also talk about renaming this file bwcorvus mentioned in the first page. But like I already asked a few times what the risks are of deleting this file? A shame bwcorvus does not answer anymore, maybe he knows? That would then solve the CWM issue.
For the Tiamat flash, I will have a look at the thread.
Thanks again for all your help!

You could do a nandroid backup (in CWM) and then delete the file. If things go badly, you should be able to boot into recovery and restore.
Sent from my Xoom using Tapatalk

That is a good one. But I was just thinking, after the second reboot CWM disappears, so I can't restore
I have to think about this.

olafski72 said:
No problem, Thanks for all your help. In here the same problem is described: http://forum.xda-developers.com/showthread.php?t=761398
Although in here the problem is a Nexus and no Xoom. But they also talk about renaming this file bwcorvus mentioned in the first page. But like I already asked a few times what the risks are of deleting this file? A shame bwcorvus does not answer anymore, maybe he knows? That would then solve the CWM issue.
For the Tiamat flash, I will have a look at the thread.
Thanks again for all your help!
Click to expand...
Click to collapse
There can be no problems from removing it. If you are truly scarred just rename it rec.bak. Its just a text file that runs at boot to make sure the recovery is stock. If its not, it makes it stock.
Sent From My Evo

Original transformer bricked

I updated the CMW recovery via ROM manager and now my tablet is bricked. I can only get into the recovery but it does not recognize my external sdcard and this is where my rom are. so there's no way to flash the rom.
Btw, the serial# start with B50.
Does anybody know i can resolve this?
Thanks
:crying:

pcurator said:
I updated the CMW recovery via ROM manager and now my tablet is bricked. I can only get into the recovery but it does not recognize my external sdcard and this is where my rom are. so there's no way to flash the rom.
Btw, the serial# start with B50.
Does anybody know i can resolve this?
Thanks
:crying:
Click to expand...
Click to collapse
'No way to flash the rom' is not right. Seeing you have a B50, you should be able to do it with the nvflash method. Search this forum for the methods, there are a lot of threads with instructions.
Good luck.

pcurator said:
I updated the CMW recovery via ROM manager and now my tablet is bricked
Click to expand...
Click to collapse
NEVER EVER use ROM manger on the TF101, it is a well-known source of bricks.
Bad news: you lost all your data and there's no way around it.
Good news: you can use nvflash/wheelie to reflash the device.

pcurator said:
I updated the CMW recovery via ROM manager and now my tablet is bricked. I can only get into the recovery but it does not recognize my external sdcard and this is where my rom are. so there's no way to flash the rom.
Btw, the serial# start with B50.
Does anybody know i can resolve this?
Thanks
:crying:
Click to expand...
Click to collapse
You're not bricked, just needed to do a little searching.
Cold boot:
Hold Vol Down plus Power button
Wait till you see the options of Cold boot Linux or Wipe data
Choose Cold boot Linux and it should boot into the OS (Unless you wiped the system)
Use PERI to fix your recovery
http://forum.xda-developers.com/showthread.php?p=26737790
If that don't work there's a thread that show you how to fix it via terminal our adb shell.
http://forum.xda-developers.com/showthread.php?t=1530337&
Of course NVFlash work too.

cannot get out of recovery

I do not have any back ups because i backed up on clockwork and i now have twrp. I have 3 roms on my phone but 2 say failed and aokp just puts me in bootloop. I cant do anything .please help. Thank you!

So nobody can help or what???????

kkurtz78 said:
I do not have any back ups because i backed up on clockwork and i now have twrp. I have 3 roms on my phone but 2 say failed and aokp just puts me in bootloop. I cant do anything .please help. Thank you!
Click to expand...
Click to collapse
Have you try to do a full wipe? In any case, yoy can download other rom that works sure and put in the sdcard using adb when you are in recovery mode...
Check if when you flash the rom, you are getting an error related with loky-... (Something like this)...

Why don't you try to install back cwm if you still have your cwm backup. Then after that restore your backup.
Sent from my LG-D802 using Tapatalk

mrm43 said:
Why don't you try to install back cwm if you still have your cwm backup. Then after that restore your backup.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
How can i install back to CWM? if i cant get out of Recovery?? I would just download another rom but computer wont show my phone since stuck in recovery, As you can tell i have limited access to computer privileges due to using a work computer, so I do not have any of the tools on the computer.

lomunet said:
Have you try to do a full wipe? In any case, yoy can download other rom that works sure and put in the sdcard using adb when you are in recovery mode...
Check if when you flash the rom, you are getting an error related with loky-... (Something like this)...
Click to expand...
Click to collapse
Yes i did a full wipe, when i flash AOKP 2/16 its successful but stays boot looping, but PA and CM11 says failed, but nothing mentioning loki.

Can you not mount in twrp? Or go into download mode and adb push another ROM onto the phone? If your in a bootloop just wipe everything twice. Mount or adb push a new ROM AFTER checking md5. Both those have worked for me :$
Sent from my Rezound using xda-developers app. CyanogenMod 11. S-off

Is your TWRP out of date? You can update TWRP while in TWRP. Or just adp sideload another ROM.

How do you update twrp while in recovery? When flashing the other two roms its saying something about binary?? And how do you side load, yes im real new to the g2 root game, my nexus's were so much easier and never delt with adb sdk really, ill have more luck tomorrow when im on computer i can actually download stuff , when i flash aokp i see all the files through file manager but just won't boot

kkurtz78 said:
How can i install back to CWM? if i cant get out of Recovery?? I would just download another rom but computer wont show my phone since stuck in recovery, As you can tell i have limited access to computer privileges due to using a work computer, so I do not have any of the tools on the computer.
Click to expand...
Click to collapse
By using ADB. If your pc does not detect phone. Try installing lg drivers or those on pdanet drivers.
Link for universal drivers to get ADB working.
http://koush.com/post/universal-adb-driver
Sent from my LG-D802 using Tapatalk

Adb is the way to go if your stuck in recovery. And even if you're a newb its easy to learn as there are countless tutorials out there. Just read up on it and then you can either push a new ROM or push cwm and restore your old backup
Sent from my LG-G2 using Tapatalk