Database Info

Clueless what to do next?

Hi
I'm completely clueless as to what to do next here. I've rooted my Xoom which worked and was fully functional, etc.
Now I wanted to try the Tiamat ROM. I installed Clockword Mod Recovery from the ROM Manager yesterday. It reads version 4.0.0.4. Now I downloaded the ROM and tried to install via clock word but nothing happens. What's worse now is that my Wifi says "error" and can't be turned on.
At this point if someone can point me in the right direction to getting the ROM installed, I would greatly appreciate it. If not, I'll also go for stock 3.1 rooted if that's possible at this point.
Please help me out
Thanks

This exact same thing happened to me. Made me really nervous and I wound up rolling back to stock and rerooting - all unnecessarily. All you need to do is put the Tiamat recovery back on, wipe your data (yes, everything on your internal storage, so make a backup), and install Tiamat 1.1 from an SD card. I detailed my experience with instructions for another person on how to fix it in this thread:
http://forum.xda-developers.com/showthread.php?t=1152121
Any questions just ask.

mikeserv said:
This exact same thing happened to me. Made me really nervous and I wound up rolling back to stock and rerooting - all unnecessarily. All you need to do is put the Tiamat recovery back on, wipe your data (yes, everything on your internal storage, so make a backup), and install Tiamat 1.1 from an SD card. I detailed my experience with instructions for another person on how to fix it in this thread:
http://forum.xda-developers.com/showthread.php?t=1152121
Any questions just ask.
Click to expand...
Click to collapse
I've been trying to warn people about that incompatible recovery from Rom Manager for several weeks. I wish we could have a sticky post about it. So many people fall into that trap and get all messed up. I know cause it happened to me.

Clockwork Mod Not Flashing ROMS

Hello, please let me know what I'm doing wrong, I've looked exhaustively for a solution to my problem on my own but I can't seem to find one:
1.) Rooted my G2x
2.) Installed Clockwork ROM Manager
3.) Copied two separate Gingerbread ROMs, Cyanogen 7, and Modaco into Root Folder (no sd card, just phone storage)
4.) Tried flashing both Roms multiple times with Rom Manager by both rebooting into recovery and installing from .zip (this option won't display either of the ROMs, just the log file folder.) I have tried installing .zip from SD in ROM Manager, and the phone just reboots as if nothing has happened.
*I believe ROM Manager does have difficulty mounting the phone storage, as it takes a full twenty count before attempting to flash the ROM.
**I don't know if this helps, but I have not received the OTA Gingerbread update from T-Mobile (even when my phone was unrooted), and when I prompt for the OTA update, I receive a "connection error" message. The LG Updater Tool indicates that my phone is "up to date" when it clearly, is Froyo 2.2.2.
Any help would be greatly appreciated with this issue guys, I usually scour forums for answers to my questions or fumble my way through it myself, but this has really sucked out lots of hours from my life.

No external sd card
You have to have a external to flash roms if im not mistaken

when you install recovery there are 2 choices external storage and internal storage if you dont have an sdcard reinstall clockwork using the internal option. that should do the trick for you.

eagle1967 said:
when you install recovery there are 2 choices external storage and internal storage if you dont have an sdcard reinstall clockwork using the internal option. that should do the trick for you.
Click to expand...
Click to collapse
I am going to try with an external SD card. Also, I am unsure of how to flash it to use internal storage, I checked the settings through ROM manager and couldn't find out how to do it. Is this something I access during Recovery mode? Thanks for the suggestions so far guys, I'll definitely post with results.

pathmarkpolice said:
Hello, please let me know what I'm doing wrong, I've looked exhaustively for a solution to my problem on my own but I can't seem to find one:
1.) Rooted my G2x
2.) Installed Clockwork ROM Manager
3.) Copied two separate Gingerbread ROMs, Cyanogen 7, and Modaco into Root Folder (no sd card, just phone storage)
4.) Tried flashing both Roms multiple times with Rom Manager by both rebooting into recovery and installing from .zip (this option won't display either of the ROMs, just the log file folder.) I have tried installing .zip from SD in ROM Manager, and the phone just reboots as if nothing has happened.
*I believe ROM Manager does have difficulty mounting the phone storage, as it takes a full twenty count before attempting to flash the ROM.
**I don't know if this helps, but I have not received the OTA Gingerbread update from T-Mobile (even when my phone was unrooted), and when I prompt for the OTA update, I receive a "connection error" message. The LG Updater Tool indicates that my phone is "up to date" when it clearly, is Froyo 2.2.2.
Any help would be greatly appreciated with this issue guys, I usually scour forums for answers to my questions or fumble my way through it myself, but this has really sucked out lots of hours from my life.
Click to expand...
Click to collapse
I can't quite tell if you used rom manager to flash CWM, but if you did then make sure to use nvflash. I don't know if it could cause things not to work, but it's the only way to guarantee you can always get into recovery. As people have said above, try to use external, although I hadn't read anything about problems with using internal to flash roms, at least if nvflash has been used.
I'll assume you've already heard of wiping/factory reset and all that since you joined a few years back, but make sure to do it when going to a new rom. As for the update issues, I would say just restore stock froyo, maybe from the nandroid tgagunman created if something is wrong with yours, factory reset it just to be careful, unroot using superoneclick, flash stock recovery using tgagunman's one click recovery flasher, and make sure usb drivers are up to date.
If you really can't get the new baseband and roms working after all that... tell t-mobile you can't get the update and ask for a new one haha.

Thanks Guys...
Danish, Eagle, Water, thanks a lot to all of you guys. I was able to flash a new ROM using an External SD card, I'm still having problems finding a ROM that is stable and is compatible with all of the apps I want to use (I'm currently having difficulty installing Tooyoou on the Bionix ROM I downloaded, which is otherwise AWESOME). I mean, it's not that big of a deal, but I'd like to get my extra $2.50 a month from the program.

Oh and NV Flash...
NV Flash helped me when I messed up my G2x's ability to boot into recovery with a Cyanogenmod 7 ROM build. Here's a link to a guide that helped immensely for anyone who finds themselves in this thread with a similar issue:
http://forum.xda-developers.com/showthread.php?t=1056847

[Q] PLEASE HELP!!! Cannot Boot Nexus S!!

Hi everyone,
I'm sorry I'm quite new to this, and I'm afraid I've gotten myself somewhat stuck with my Nexus S. Yesterday I managed to root it, install superuser, as well as clockwork mod. Today I wanted to try a new rom and after some attempts, it seems I no longer have any working roms on my phone. After much searching with no luck, I turn to you guys for your expertise.
So I am able to see fast boot upon pressing the volume up and power buttons, and am certainly able to choose recovery and get into clockwork mod. Within clockwork mod I can mount USB storage, so I can transfer roms to the internal SD card. I've tried 3 or 4 roms, some say they install correctly, others not, and after trying to boot after any installation I simply get stuck at the google screen with the lock image at the bottom. The only things I have "deleted" is wiped the data and cache. I have no idea, but I think I may have erased the bootloader image or something else that I should not have that is required.
I have a i9020a model (non-4g model I believe), can you pleeeeeeeeeeeeeaaaassee help me!! I just want to get back to gingerbread 2.3.6, and my phone back up and running the way it was. I've become quite nervous after some searching with some saying a resistor mod is needed on the hardware!!

Your okay cause you can get into fastboot and recovery so don't worry. Maybe the rom you downloaded is not for your phone. Did you make a nandroid backup before flashing the rom? If yes then go into backup and restore from clockwork recovery to go back to stock.
Sent from my A500 using Tapatalk

If you can get to recovery, just flash the stock image FOR YOUR PHONE. Then you can go through and reroot..don't worry, you'll get the hang of it.
Sent from my Nexus S using Tapatalk

So my phone is not "bricked" as they say?? I'm not in big trouble?
I did not make a nandroid backup What kind of image am I looking for and how do I install it on the phone? I know my phone is of the variant i9020a, but how am unsure of how much more specific I should be looking for.
Looking at the following post: http://forum.xda-developers.com/showthread.php?t=1063664.
Should I try installing the Android 2.3.6/GRK39F/UCKF1 Radio/KA3 Bootloader option?

Choose the latest 9020a version of the FULL ROM, which is what you have already have eyes on.

I've tried installing the file I mentioned above, but I get a status 7 error when trying to install, and the install is aborted.
Could I get some more assistance please? Can anyone point me to a correct, full rom? Or perhaps I'm installing it incorrectly, could someone be so kind to outline the correct steps to a proper install?
Edit: I think the above mentioned file is for a GSM model, I'm sure I have the CDMA version.
Also, somewhat good news. I managed to install the oxygen rom, but for the 4g version and installed fine with no errors, but I have no service. What does this indicate, as I still want to restore back to a factory version (non-4g) of gingerbread 2.3.6.

What CWM version do you have? Is it 3.0.0.0?
Also, if you have no service, it's likely that you downloaded a ROM with an incorrect radio.
Edit:
If you have CWM 3.0.0.0, make sure to download the latest version, found in this thread: http://forum.xda-developers.com/showthread.php?t=988686 (use 5023-cyan.img). You flash this the same way you did CWM previously, though in the terminal make sure you type out the 5023-cyan.img file name.
Next, download the stock ROM from this thread: http://forum.xda-developers.com/showthread.php?t=1063664. Simply look for your phone version, and you'll find the correct software variant.
Maybe you've fixed your phone already; if not, I hope this helps!
I wish you the best of luck. Oh, and through problems like these, you come to learn a lot more about your phone. That's what I've found, at least.

At the thread you mentioned above there is a version with a different radio, you might want to give that one a try.
You also said that you only wiped data and cache, so maybe you should do a full wipe before. Not doing that can sometimes lead to problems.
Sent from my Nexus S using XDA App

To be brief, the phone is up and running as brand new! Thank you so very much everyone. It seems the error was with CWM, as I was able to install and boot a 4g oxygen rom on my phone, I went into rom manager, and at the bottom of the list was an option to upgrade to 5.x. Installed the CWM update, wiped everything and was able to install the factory rom, no issues, and everything works just as I remember
I have most certainly learned more about my phone, and I am going to look at it as a rather stressful learning experience rather than a mistake on my part.
But a sincere thanks to everyone once again, I posted this at like 4am here and had a response within a few minutes, I was pulling my hair out haha!

Flashing to stock rom will help you out. You can get stock roms from Internet simply by searching in Google...
Sent from my Nexus S using XDA App

[Q] NexusS (i9020T) hard bricked, at which step did I go wrong?

Hi everyone, I had a problem with my previous nexus s (I have since gotten a working replacement) and I was wondering where exactly I messed up so in the future I can avoid this
Here is what I did on my previous phone:
1. I flashed ics onto my device from the ota update package from androidcentral, it was 4.0.3. (This worked great and I had it on my phone for 2-3 months before I tried the next steps.)
2. I rooted my device successfully using the guide at nexusshacks.
3. I also flashed TWRP recovery (fastboot) and superuser using the above guide/links
4. When I would turn off my phone it would boot to a screen with a red triangle and an opened android bot. So what I would have to do is flash twrp recovery everytime I turned the phone on just to get it to work.
5. What I wanted to do was keep the stock rom but still have twrp recovery without it making me reflash it on every boot. So I clicked install and tried to flash the stock rom (update package from the link in step 1) with twrp recovery. It then turned off my phone and hard bricked it. I couldn't turn it on anymore and a new battery didn't fix it.
I was able to get a replacement now and I was just wondering at which step did I go wrong? I THINK that I should have wiped my cache before I tried to reflash the stock rom but maybe I'm way off base here. This is why I posted a question here so hopefully some of you guys can help.
I did think about posting in another thread, but I didn't wanna threadjack or anything... and his problem also seemed a bit different then mine. Also, sorry about not being able to provide the specific links it won't let me post them until I've posted 8 times.

I don't know for sure but team win recovery has been reported to corrupt the device's efs directory. I've even had problems myself using clockwork recovery. I've moved on to razor recovery and haven't looked back.
This is the most flash-friendly phone I've ever owned, and razor recovery rivals amon ra (which was awesome on my g1 and evo). I really think it may have just been the recovery you were using... Somebody correct me if i'm wrong.
Sent from my Nexus S 4G using Tapatalk

I had once corrupted one of the partition. I fixed to by flashing stock recovery and stock rom.
Use adam outler's unbrickable mod tool. It can be found in android development section.
Sent from my Nexus S using XDA

Thanks for the replies.
That's interesting about twrp... I didn't know that. Truth be told, the only reason I went for it over other ones like clockwork mod was because the UI looked pretty nice and easy to use. Also the guide I followed at nexusshacks used that, so I wanted to stay consistent with it.
jishnu7, it's a little late for that now however as I actually have already received a working replacement from my carrier, but in the future if something ever does go wrong (hopefully not) I will definitely check that out.
The main thing I'm wondering is if it messed up because I tried to reflash the stock rom essentially over top itself (was hoping that by doing that, it would stop making me reflash twrp on every reboot) or if it was because I didn't wipe the cache before the flash.
Also, what I really wanted to do with my phone was to keep the stock rom but be able to overclock my cpu/gpu. I was hoping I could set different overclocks for different things (I've heard of kernels where you can downclock your phone when the screens off and have it overclocked slightly while you're using it, that would be something I'd like to have). I figured to install those kernels I would have to root my phone, replace stock recovery and install superuser so that's why I tried to do that. Once again, I'm pretty new to all this stuff for my phone.

Sorry to bump this thread again, but I would really like to know how I could avoid what happened to me for the future. I think it's because I flashed the stock 4.0.3 rom over itself (was hoping that by doing that twrp recovery would stay on the phone after reboot).
What I would like to do is install something like CM9 or AOKP and use the Matr1x kernel so I could undervolt or overclock my phone.

I seriously dont get how u hard bricked your phone...
the reason you are thinking is you reflashed stock rom without wiping cache, as per my experiece its not at all the reason
now, whats my experience??
...I have some fault with my nexus device and I'm working on it,,and I did everything I could do...one of the thing out of those things was reflashing stock rom without wiping,and i did it quite a several times...my device never hard bricked,,however it was soft bricked for many times,,and i recovered from it
so reflasing a stock rom over stock rom, over ICS, over some themed custom rom,will not hard brick your device, you must be missing something none of your steps sounds suspecious
P.S:- pulling out battey while flashing something like this sounds suspecious, never tried though

I'm not sure what happened either to be quite honest with you. Since giving it another shot now with my new fresh phone I have had great success!
I did everything I wanted to do all in one go. Rooted it, install CWM touch, install AOKP (went with milestone 4 cuz I heard newest build 29 has some bugs) + gapps and installed matr1x kernel 18.5 bfs.
The only thing I did different from last time was installing CWM touch (instead of twrp) and flashed aokp this time (instead of reflashing 4.0.3 over itself).

I would just avoid step 2 at all cost.
The nexus s hacks dude is a tool.

Htc one S. Time of the month.

Hi need a bit of help with this one if possible.
start the top..
went to flash leedroids rom..flashed boot image but forgot to pull rom over.
so had various issues getting over in the end had to mess around with recoverys and totally wipe my sd for it to be recognized.
so i solved all this then..now the issue is..of everything i push over..only one rom boots up and installs fine..and that is a cm9 test without sd mounting..so it solves nothing.
any ideas of how to get a rom on there where i can mount the sd..download a rom and put it on..
ill be honest..htc+internal sd card=not happy
ive pushed leedroids..virtuous..utbs rom but nothing.
i tried aokp but it didnt even push.
with these also some get corrupted by a protocol failure..
many questions. currently has cm9 on..but no mounting..so great

Did you already try a factory reset after flashing the stock recovery (e.g. from MoDaCo)?

-
Hi rootrider, yeah i followed a post i found..
basically i used the one click toolkit to flash the stock recovery..then cleared storage and all data etc.then installed clockwork back..it doesnt like the working roms though
cm9 is the only one i can boot up..at least it sees the sd card again in clockwork though

Had your problem as well... I don't remember exactly what I did to get out among many other things (sh..).
Had some trouble as well flashing stock recovery with the one click tool kit. It didn't work as expected. So I did it with adb. Just keep on trying, there is a way out.

-
My next course of action is, to flash the stock recovery, clear everything,reinstall clockwork then install aokp..if its something with the type of rom.maybe that will work..i can mount..get a rom on the sd and resume business as usual..
debatebale whether itll work lol

If this doesn't help get Thor's hammer and flash your appropriate RUU (again).

Easiest method would be to run an RUU and start over again. I see your vodafone UK so try this one
http://dl.dropbox.com/u/69014495/RU..._2_10.23.31501S.10L_release_258386_signed.exe
It also includes the new radio too !
Just relock bootloader before running it, After its finished unlock and fastboot flash cwm..
easy peasy !!

--
thanks people, im running leedroids rom now, seemed my issue was is after pushing the file over i just tried to install immediatley..after a couple of reboots just for the hell of it,untouchables rom started installing...phew..
sadly all my sd contents have gone..very dissapointed with the sd card business!
still least its working again!
thankfully azzle didnt need to go back to ruu

Aye, captain. Glad to read this.