Database Info

[Q] Bricked Xoom?

So im running 3.1 rooted with the 1.4.4 Tiamat Kernel. I had this weird force closing issue where gapps would force close whenever i tried to connect to wifi. I powered down, turned on, and am now stuck in a boot animation loop. I can hold down the Vol Down button and it says "Starting Fastboot Protocol Support." but nothing changes. Is there anything I can do it fix it/turn it off until i get home to my computer with the SDK? On another note I did install the wpa supplicant (sp?) files to allow it to connect to an adhoc wifi source (eris tether). Please and thank you
EDIT: I have booted into recovery, but I am unable to mount any of the drive locations or wipe them. I did a factory data reset (as much as it could I guess?), but im still at the boot loop.

Hook it up to computer while its in fastboot and open a command prompt from the folder you have fastboot. Type "fastboot reboot-bootloader" and you should get adb to recognize, then push stock images or root images and recovery.
What recovery were you using? Did you flash the one from ROM manager?

I am using the CM from the ROM manager the latest one I think that it is version 4 something. does this make a difference? I have backups from my previous flash but when I tried to recover it won't take them. where can I get the root image? I might have it already since I rooted using adb, I will have to look on my laptop when I get home. Any other info you have will help. Thank you,,,,

razor532 said:
I am using the CM from the ROM manager the latest one I think that it is version 4 something. does this make a difference? I have backups from my previous flash but when I tried to recover it won't take them. where can I get the root image? I might have it already since I rooted using adb, I will have to look on my laptop when I get home. Any other info you have will help. Thank you,,,,
Click to expand...
Click to collapse
You will need to flash a good recovery, I suggest you you use the .img file in this thread through adb when you get to your laptop:
http://forum.xda-developers.com/showthread.php?t=1074979
The recovery version you updated to won't look at your external sdcard, so you can't flash from it until you re-install a good recovery.
Can't we get a pinned warning about this issue?

Thanks everyone, sorry for the delay. I ended up fixing it with a fastboot oem unlock command. However after countless flashes unable to get it to boot again i realized i was flashing the tiamat rom and then a different tiamat kernel boot.img, most likely the culprit in my boot loop. The minute i did a factory reset, updated cwr and only flashed the rom, everything works fine. Thanks for everyones help
Sent from my Eris using XDA App

So glad you were able to fix it!

[Q] Cannot boot into recovery. Laggy phone as well.

I was just about to try updating from NScollab 1.0.39 to 1.0.40 and for some reason my nexus s refuses to boot into recovery. It doesn't seem to exist anymore. Im not sure if it is related or not but my phone became very laggy after my first failed attempt to boot into recovery. I tried fixing user permissions and rebooting many many times but it doesn't seem to help.

What does it do when u try to boot into recovery?
Sent from my HTC Sensation 4G using XDA App

It doesnt do anything. It just reboots into the bootloader.
Thank you for the quick reply
edit:
i tried flashing recovery again through rom manager and now whenever i try to boot into recovery it just hangs at the google logo with the unlocked padlock.

Hmmm
Do me a quick favor.
go here:
http://wiki.cyanogenmod.com/wiki/Ne...de#Installing_the_ClockworkMod_Recovery_Image
and download the 4.0.0.2 recovery image and save it to some directory on ur computer
then follow these steps:
1. Open up command prompt/terminal and plug in phone to computer
2. Type "adb reboot bootloader"
3. It will take you to fastboot mode. Now type "fastboot erase recovery"
4. Then type fastboot "flash recovery ____.img"
( ____ is the name of the recovery img file)
5. Now it will flash and once it says "OKAY" then scroll down using volume down into recovery and see what happens
plz get back to me bout this!

IT WORKS! It went into recovery! Thank you so so much! Is there anything else I should do or am i set to go?

i so hate rom manager! i cant believe that people still use it

shahravi94 said:
IT WORKS! It went into recovery! Thank you so so much! Is there anything else I should do or am i set to go?
Click to expand...
Click to collapse
Since it works, you can wipe and flash ns collab lol
Sent from my HTC Sensation 4G using XDA App

Thank you so much for the quick help! btw i updated recovery from rom manager and i ran into the same problem with it not booting into recovery so i am guessing there is a problem with the latest version of recovery? I'll just reflash through the instructions you gave me.

Yeah prolly a ROM manager issue
Sent from my HTC Sensation 4G using XDA App

shahravi94 said:
Thank you so much for the quick help! btw i updated recovery from rom manager and i ran into the same problem with it not booting into recovery so i am guessing there is a problem with the latest version of recovery? I'll just reflash through the instructions you gave me.
Click to expand...
Click to collapse
the recovery generally doesnt stick if flashing it through rom manager. flash it through fastboot and itll stick.

Hmm thanks for the advice! ill keep that in mind

[Q] [i9023] Blank/Black screen in recovery

Hey everyone,
Basically I was trying to flash a new ROM onto an old Nexus S of mine and when I tried to boot into recovery there was just a black screen. I pressed the power button and a single line saying "Clockwork mod Recovery" and the version number popped up. I assumed that the recovery must've been corrupted so I erased it and installed the latest version using fastboot which seemed to work fine.
Now whenever I try to boot into recovery I just get a blank screen with nothing else. I've tried using other recovery images such as twrp but the same problem happened, I just get the background wallpaper/image and nothing else.
I searched the forums and apparently people were having this issue earlier on when the i9023 was first released but now most custom recoveries are supposed to work with both i9020 and i9023.
Also the touch buttons light up and vibrate whenever I touch them when I'm in recovery mode.
Any help to this problem would be greatly appreciated as atm I have an old ROM which is buggy as hell and I need to get rid of it.
Cheers!

I had the same Issue. If you can boot into the rom, you can try to download the rommanager-app and install the recovery from there.

Hey I tried that already that and instead of booting into recovery it just went into the bootloader and said "No Recovery or Bootloader found".
Any other ideas?

Did you clicked the first point in rommanager? Install recovery, or you only hit the second button reboot into recovery?
Sent from my Full Android on Crespo using XDA App

Hey
I have the i9023 and I install rom manager. install CWM and if I reboot into recovery it works and I get in to CWM recovery.. but after reboot into os.. if I go into Rom manager and reboot to recovery it dont work? I just get the android figur and a "!".. then I just can Power + vol up and I'm in bootloader recovery..
Do I have to install CWM every time i want to use it? and can't I access CWM on boot op ?
sorry for my bad English

Normaly you have to flash the recovery only once.
Try to flash the newer clockwork-recovery with fastboot.
http://forum.xda-developers.com/showthread.php?t=988686

Alfiedk: You need to get rid of this file:
/system/etc/install-recovery.sh
As it re-installs the stock recovery every boot.
I think you can download any custom ROM for your phone, and flash it in CWM recovery, this will also solve the problem
Edit: Did you unlock the phone? Have you tried fastboot oem unlock?
Sent from my SNES

bedalus said:
Alfiedk: You need to get rid of this file:
/system/etc/install-recovery.sh
As it re-installs the stock recovery every boot.
I think you can download any custom ROM for your phone, and flash it in CWM recovery, this will also solve the problem
Edit: Did you unlock the phone? Have you tried fastboot oem unlock?
Sent from my SNES
Click to expand...
Click to collapse
I havent unlock my phone, but I can get in to bootloader is it then necessary to unlock ?
I try to delete the /install-recovery.sh

Yes you need to unlock your bootloader, if you dont want to reflash it all the time.
Sent from my Full Android on Crespo using XDA App

Xziped said:
Yes you need to unlock your bootloader, if you dont want to reflash it all the time.
Sent from my Full Android on Crespo using XDA App
Click to expand...
Click to collapse
Then it must be unlock as default.. I havent unlock it.. just delete the install install-recovery.sh and it works every time now.
now I just have to find a ROM to try..

Xziped said:
Did you clicked the first point in rommanager? Install recovery, or you only hit the second button reboot into recovery?
Sent from my Full Android on Crespo using XDA App
Click to expand...
Click to collapse
Yes I made sure I selected install clockwork mod. Like I said the problem isn't the same when I do this, instead of a blank screen, when I boot into recovery it goes straight to fastboot and tells me that I don't have a recovery image installed at all...

Simultaneity said:
Yes I made sure I selected install clockwork mod. Like I said the problem isn't the same when I do this, instead of a blank screen, when I boot into recovery it goes straight to fastboot and tells me that I don't have a recovery image installed at all...
Click to expand...
Click to collapse
what happens when you try to temporary boot into the recovery?
instead of "fastboot flash recovery recovery.img", try to "fastboot boot recovery.img"
Just look for an recovery.img that works temporary and then try to flash it permanently.

I'll try it and get back to you Xziped. If anyone else can think of any other ideas please just throw'em at me, I'm willing to try anything!

Yeah no help there either. It does the exact same thing temporarily booting into a recovery that it did when I actually had it installed on the phone :\.
I updated ROM manager to the latest and tried installing CWM with that but to no avail. It still says that there is no recovery installed when I do that.

Simultaneity said:
Yeah no help there either. It does the exact same thing temporarily booting into a recovery that it did when I actually had it installed on the phone :\.
I updated ROM manager to the latest and tried installing CWM with that but to no avail. It still says that there is no recovery installed when I do that.
Click to expand...
Click to collapse
Sorry but if not even the temporary recovery boots up, i dont know what else we can do
did you try some of the older recoverys? is your bootloader unlocked?

I haven't tried an older recovery and my bootloader is unlocked.
could it be a problem with my computer as opposed to the phone itself? As in my computer is messing up when trying to flash the recovery?
I've also noticed now that when I boot into fastboot mode the menu just locks up and doesn't respond to anything. Sometimes I have to pull the battery and other times it'll start responding after randomly pressing the power key a lot of times...
I'll try an older recovery next

Simultaneity said:
I haven't tried an older recovery and my bootloader is unlocked.
could it be a problem with my computer as opposed to the phone itself? As in my computer is messing up when trying to flash the recovery?
I've also noticed now that when I boot into fastboot mode the menu just locks up and doesn't respond to anything. Sometimes I have to pull the battery and other times it'll start responding after randomly pressing the power key a lot of times...
I'll try an older recovery next
Click to expand...
Click to collapse
Use Odin, that might solve your problems. Search for the Nexus S version of Odin in the Dev section here.

khartaras said:
Use Odin, that might solve your problems. Search for the Nexus S version of Odin in the Dev section here.
Click to expand...
Click to collapse
There's a version of Odin for the Nexus S!?!? I'll look into that straight away thanks!

Simultaneity said:
There's a version of Odin for the Nexus S!?!? I'll look into that straight away thanks!
Click to expand...
Click to collapse
Just look @ http://www.samfirmware.com/ .
There you should find all you need
Sent from my Full Android on Crespo using XDA App

[Q] Bricked my phone :(

I recently rooted my HTC One X using djrbliss's method. I installed TWRP and used that to do a factory reset, wipe the cache and dalvik cache. I then installed the CM10 mod (cm-10-20121012-NIGHTLY-evita.zip) using the latest one. After it said it was successfully installed, I did a system reboot and now my phone is stuck at the CynanogenMod loading screen.
I'm able to get to the TWRP screen by using the "adb reboot recovery" command in the command prompt, but I have no clue what to do. I just want to go back to the stock ROM. I'm freaking out and starting to panic. Any help would be greatly appreciated. Thank you!

marcur12 said:
I recently rooted my HTC One X using djrbliss's method. I installed TWRP and used that to do a factory reset, wipe the cache and dalvik cache. I then installed the CM10 mod (cm-10-20121012-NIGHTLY-evita.zip) using the latest one. After it said it was successfully installed, I did a system reboot and now my phone is stuck at the CynanogenMod loading screen.
I'm able to get to the TWRP screen by using the "adb reboot recovery" command in the command prompt, but I have no clue what to do. I just want to go back to the stock ROM. I'm freaking out and starting to panic. Any help would be greatly appreciated. Thank you!
Click to expand...
Click to collapse
As you can boot up to recovery you are pretty much safe, even if you cant boot into recovery you are still safe if you can get into bootloader.
So don't panic, i think that CM10 was stuck on loading screen because you didnt flash the kernel (you have to flash boot.img manually).
You can connect your phone to your computer entering to the mount section on recovery, select mount usb storage and then transfer another rom to your phone, you can also try again with CM10 but this time flashing the kernel(boot.img) before booting.
Follow the last instructions from this post http://forum.xda-developers.com/showthread.php?t=1952076

I didn't know you had to flash the boot image. I did that and it worked this time! Thank you for the help!

marcur12 said:
I didn't know you had to flash the boot image. I did that and it worked this time! Thank you for the help!
Click to expand...
Click to collapse
Glad that worked!

People, look at the word "brick." What is a brick? It's a rock. If your phone powers on and does something and you can interact with it, it is not a brick, and you're probably in decent shape. Vocabulary is important.

thebobmannh said:
People, look at the word "brick." What is a brick? It's a rock. If your phone powers on and does something and you can interact with it, it is not a brick, and you're probably in decent shape. Vocabulary is important.
Click to expand...
Click to collapse
lol for cereal.... All this talk about bricking...ppl its actually boot looping and in some cases a soft brick.
I've only ever seen one hard brick in my life and it was an s2 with a bad emmc.
Sent from my One X using xda premium

ptesmoke said:
I've only ever seen one hard brick in my life and it was an s2 with a bad emmc.
Click to expand...
Click to collapse
You can get one flashing an international rom on a pre-2.20 One XL because it overwrites the boot partition.

Can't acces Recovery

Hey guys
I'm trying the whole time to accces recovery on the Moto G, but everytime I try this, the phone always reboots to Android. I tried Flashing CWM and TWRP, then it says in my fastboot flash mode: mismatched partition size. I never can go to recovery because it always reboots when I try to acces s it. And I want to install CWM or TWRP for flashing roms but nothing changes, the problem stays... Could anyone help me or has anyone also experienced this annoying problem?
Cheers

I will write a guide for it tomorrow. I don't have time right now.
Sent from my XT1032 using Tapatalk

When you flash cwm go straight to the recovery if you see a red sign with no command hold pwr+up for 2 secs it should boot into cwm
Sent from my XT1034 using xda app-developers app