Database Info

[Q] Bricked Nexus S, have clockwork recovery running

Hi guys I've been looking around and I'm a total noob at all this, but I went ahead and tried to root my Nexus S anyway.
Here's the site I used,
http://forum.xda-developers.com/showthread.php?t=878446
I don't really know what happened, but I have the little unlocked logo under google, but that google screen is all I can get. I can start it in fastboot mode, and when I click recovery it brings me to clockwork recovery page. I kinda just tried a bunch of weird things but everytime I try anything it keeps getting stuck at the google screen over and over again.
I'm really clueless.. If anyone could help me please give me your advice!

If it helps, I have clockwork version 3.0.0.0

you have to perform a nandroid restore or flash a ROM.
might as well update your recovery too.. wouldn't hurt
http://forum.xda-developers.com/showthread.php?t=988686
rename img to recovery.img
boot into bootloader
fastboot flash recovery recovery.img
go into recovery
when you finish downloading the rom/nandriod, go into mounts and storage and mount usb and put your sdcard

I'm sorry what is rom flashing or nandroid restore?
The clockwork update is confusing too.. I'd like to avoid that if possible..
Sorry looked up both of them and it looks like I actually need my phone to be working in order to do it?
I've read and it says it doesn't really help on stocked android phones?
The nadroid restore is the -backup and restore option in clockwork yes?

lanstrange said:
I'm sorry what is rom flashing or nandroid restore?
The clockwork update is confusing too.. I'd like to avoid that if possible..
Sorry looked up both of them and it looks like I actually need my phone to be working in order to do it?
I've read and it says it doesn't really help on stocked android phones?
The nadroid restore is the -backup and restore option in clockwork yes?
Click to expand...
Click to collapse
It doesnt really help if you reboot the phone cause with stock rom, every reboot flashes back the stock recovery.
what you should do is follow the steps @Zephik described above ( but without rebooting the phone) and you'll be able to enter the clockwork recovery ( a modified recovery allowing you to do a backup or rom flashing...) '
rom flashing is installing a rom modified by users for a better and faster user experience.

lanstrange said:
Hi guys I've been looking around and I'm a total noob at all this, but I went ahead and tried to root my Nexus S anyway.
Here's the site I used,
http://forum.xda-developers.com/showthread.php?t=878446
I don't really know what happened, but I have the little unlocked logo under google, but that google screen is all I can get. I can start it in fastboot mode, and when I click recovery it brings me to clockwork recovery page. I kinda just tried a bunch of weird things but everytime I try anything it keeps getting stuck at the google screen over and over again.
I'm really clueless.. If anyone could help me please give me your advice!
Click to expand...
Click to collapse
You should tell us your carrier and phone model, it might help the guys here to get you on the right recovery.

hxxp://flickr.com/photos/asuerio/5716164499/
hxxp://flickr.com/photos/asuerio/5716163423/in/photostream/
hxxp://flickr.com/photos/asuerio/5716162899/in/photostream/
hxxp://flickr.com/photos/asuerio/5722383955/
error when trying to access the sdcard by recovery: is not possible to mount the sdcard
I try to do everything to access the sdcard has this error

Have you fixed this? I have the same issue!

Bootloop help

So I was cruising around the Nexus S forums and found a rom I liked after I unlocked and rooted my phone.
I flashed Paranoid Android and then flashed the Matr1x kernel. Thus putting me in a neverending bootloop.
No ability to go back to CWM so I can't restore. And I can't put it in download mode so no ODIN.
What the heck do I do?
Can anyone help?
BTW if this is actually called a soft brick I'm sorry my terminology might be off.
Also I did this because the last phone I did extensive flashing with was an HTC Inspire 4G and it was easy to flash stuff just clear everything and flash what you wanted no bootloops. Sadly this phone not so much.

Hmm... No recovery...I've been stuck in a bootloop but I had recovery!
Sorry for the useless post, I cant help you..

Are you able to get into bootloader?

Usually when a bootloop occurs you should still be able to go in recovery.
When you say "no ability to access CWM" do you mean ROM Manager? Or the recovery mode?
What happens when you try to access the recovery mode?

same issue like urs
http://forum.xda-developers.com/showthread.php?t=1775933
try clean install;
flash Rom-Wiper.zip
flash Dalvik-Wiper.zip
then;
factory reset,
Format the system, data, cache, boot & partitions of your device.

I mean no access to recovery. CWM is Clock Work Mod Recovery. I have no access to fastboot either. The only thing my phone can do is bootloop.

You have to be mistaken.
Press power and volume up to get into fastboot ( bootloader). Then pick recovery....
That rom or kernel will not erase recovery. If your phone is in a bootloop it is making it past the bootloader

So it appears it as if I was mistaken. I got into fastboot and booted into CWM I'm still confused as to what I did, but I think I corrupted the Kernel.
It was the weirdest thing though. I tried it at least a dozen times, then I tried to run down the battery and try it again afterwards, and it didn't work so I gave up. Then I tried it again about 5 minutes ago and it worked. I'm sorry I cause you guys so much confusion. I've been doing this for so long I guess I just didn't doubt I was doing it right.

Won't flash CWM

I unlocked my bootloader and then tried to flash CWM, but after rebooting it goes back to stock recovery.
Creating a backup via CWM worked fine though, but somehow it won' flash over stock recovery
Anyone else having this problem ?

ma_moto said:
I unlocked my bootloader and then tried to flash CWM, but after rebooting it goes back to stock recovery.
Creating a backup via CWM worked fine though, but somehow it won' flash over stock recovery
Anyone else having this problem ?
Click to expand...
Click to collapse
Yes it happened to me too. There was an option that I could select just before rebooting to prevent this, but it didn't work. I was on stock kk4.4.2 at that time, after installing cm11 nightly, the recovery partition was ok after the reboot. When I later restored the kk4.4.2 to see if it is possible, I had to flash the recovery partition again in order to restore cm11.

enaon said:
Yes it happened to me too. There was an option that I could select just before rebooting to prevent this, but it didn't work. I was on stock kk4.4.2 at that time, after installing cm11 nightly, the recovery partition was ok after the reboot. When I later restored the kk4.4.2 to see if it is possible, I had to flash the recovery partition again in order to restore cm11.
Click to expand...
Click to collapse
So you just flashed CM11, even though it booted back into stock recovery ?

ma_moto said:
So you just flashed CM11, even though it booted back into stock recovery ?
Click to expand...
Click to collapse
Yes eventually Idid. Just like you, I made a backup while at cwm. After the reboot, the recovery partition was gone, and the fallen robot was shown when I selected it. I powered the motog off, did the volume down-power combination, reconnected the usb cable and entered the 'fastboot flash recovery xxxxxx.img' . After a sec or so I pressed vol down , then vol up, and I was back in revovery. Did a test to verify that the backed up kk4.4.2 worked, it did, did it all over again, and flashed cm11. This time, the question about persisting on reboot was not asked, and the revovery persisted.
Ps
I am trying to reach 10 posts in order to report a bug in the developers forum, so if it sounds like I am pulling your leg, I am not.

enaon said:
Yes eventually Idid. Just like you, I made a backup while at cwm. After the reboot, the recovery partition was gone, and the fallen robot was shown when I selected it. I powered the motog off, did the volume down-power combination, reconnected the usb cable and entered the 'fastboot flash recovery xxxxxx.img' . After a sec or so I pressed vol down , then vol up, and I was back in revovery. Did a test to verify that the backed up kk4.4.2 worked, it did, did it all over again, and flashed cm11. This time, the question about persisting on reboot was not asked, and the revovery persisted.
Ps
I am trying to reach 10 posts in order to report a bug in the developers forum, so if it sounds like I am pulling your leg, I am not.
Click to expand...
Click to collapse
I did pretty much the same thing right now and just flashed CM11 and it's working. I did delete personal and system files before via CWM but somehow some pictures i took were still there after CM11 installed I'm also still running stock recovery
Everythings seems to work fine but still...strange

ma_moto said:
I did pretty much the same thing right now just flashed CM11 and it's working. I did delete personal and system files before via CWM but somehow some pictures i took were still there after CM11 installed I'm also still running stock recovery
Everythings seems to work fine but still...strange
Click to expand...
Click to collapse
Yes I did a factory reset or something like that while on cwm just before restoring. Allways do that for a cleaner install. Since you see your photos, I guess you didn't do that part corectly.
If I where you, I whould do it once more, making sure you are flashing 'CWM 6.0.4.7 Swipe Recovery for 4.4 bootloader: CWM-swipe-6.0.4.7-falcon.img' from the thead of dhacker29.
Also make sure you flash the latest nightly directly from cyanogen. This compination will give you a persistant cwm and a 'official' dhacker29 cyanogen rom.
Only problem I have is with audio on csipclient, and the embeded one, but I will eventually reach 10 posts

enaon said:
Yes I did a factory reset or something like that while on cwm just before restoring. Allways do that for a cleaner install. Since you see your photos, I guess you didn't do that part corectly.
If I where you, I whould do it once more, making sure you are flashing 'CWM 6.0.4.7 Swipe Recovery for 4.4 bootloader: CWM-swipe-6.0.4.7-falcon.img' from the thead of dhacker29.
Also make sure you flash the latest nightly directly from cyanogen. This compination will give you a persistant cwm and a 'official' dhacker29 cyanogen rom.
Only problem I have is with audio on csipclient, and the embeded one, but I will eventually reach 10 posts
Click to expand...
Click to collapse
I used CWM directly from their site, maybe that's why it isn't working probably.
You're right i should do a clean reflash, but I'm getting sick of constantly reinstalling and configuring everything

Recovery not starting

Hi,
I wanted to flash the just released lollipop image so I unlocked my phone and updated TWRP from 2.8.0.1 to 2.8.1.0. Then I started Recovery and it was doing some werid thing in a list (was too fast), then rebooted. Recovery came up again (only the image of TWRP) and a restart again. Since then always when I try to go into recovery the starting image will show up, after 2-3 secs it gets black for half a second, then the image will show up again. This is a permanent loop. I flashed back to the old recovery but nnothing, still the same (and this one worked before!).
Hopefully someone of you knows whats wrong.
Thanks,
S3cret

reflash twrp recovery. but to correct you on your mistake before you do it, factory imgs are not flashable via any recovery, you can only flash them via fastboot.

I reflashed recovery several times now. I just thought being on the latest recovery version would be good. I know how to flash the lollipop image via fastboot, but I still need recovery for root.
I locked and unlocked the bootloader again and the same happened. Recovery started, doing some weird things and then the loop again.
Edit: Ok, I fixed it, somehow, I dont rly know how...

TWRP only starts after flashing it on my device. After a reboot, it doesn't work.

vercety974 said:
TWRP only starts after flashing it on my device. After a reboot, it doesn't work.
Click to expand...
Click to collapse
exactly the same here

Yup, dead Android with red warning triangle appears...

My stock recovery is broken after fastbooting the latest 5 image. Shows a red triangle above the laying down android.
How are we supposed to fix this?

Moreover, I've just reflashed the entire rom, and can't access the stock recovery. But the stock recovery seems to work beacause I can to factory reset via the settings menu, backup and restore.... Maybe it is the new security policy from google, to avoid that a thief make a factory reset directly from the recovery ?
So we can't navigate in the stock recovery anymore ?
Highway 55 said:
After fastboot flashing the .img files you need to (WITHOUT REBOOTING) flash custom recovery, TWRP etc... After that from the bootloader reboot into TWRP or whatever. When your in the custom recovery you need to adb push a permissive stock kernel or custom kernel as well as suspersu.zip. Again, without rebooting into the system, flash the kernel first then supersu. Now you can reboot into the system. ?
Click to expand...
Click to collapse

vercety974 said:
Moreover, I've just reflashed the entire rom, and can't access the stock recovery. But the stock recovery seems to work beacause I can to factory reset via the settings menu, backup and restore.... Maybe it is the new security policy from google, to avoid that a thief make a factory reset directly from the recovery ?
So we can't navigate in the stock recovery anymore ?
Click to expand...
Click to collapse
Yes I think it does have to do with the new selinux security stuff. I don't know the specifics. Maybe you want to refer to this thread. http://forum.xda-developers.com/showthread.php?p=56538538 @rootSU knows far more than I do. [emoji6]

Highway 55 said:
Yes I think it does have to do with the new selinux security stuff. I don't know the specifics. Maybe you want to refer to this thread. http://forum.xda-developers.com/showthread.php?p=56538538 @rootSU knows far more than I do. [emoji6]
Click to expand...
Click to collapse
It is exactly as he said in the post you linked.
Flash TWRP recovery and immidiately after run auto root. Then TWRP recovery will survive system boots.

Stuck at Logo

Hello guys,
I have a problem, I hope you can help me with.
I used to have an EOS ROM. I decided to do factory reset and thats when my problems started. It didn't boot up anymore. After entering recovery I noticed it couldn't mount System partition. I tried reinstalling the ROM, but no success. Everytime I entered recovery, the System checkbox wasnt marked. So I decided to go back to stock, using http://androidforums.com/threads/return-your-xoom-to-stock.653230/. Now it is stuck at Logo screen and can't enter Recovery. (Goes to Reading ODM fuse, but not any further). I can still enter Fastboot and my laptop detects the tablet, when hooked up to it.
Please help me push the Recovery, cuz I'm getting "device not found" from ADB. I'm kinda lost here... Any help would be appreciated!

Update
I managed to install TWRP, but still can't mount System Partition. On wipe I get "Failed"when trying to clean the system part. I have tried Clockwork, it didn't help either.

Cmon guys! I don't want to JTAG it yet.

HexBox said:
Cmon guys! I don't want to JTAG it yet.
Click to expand...
Click to collapse
I am not very knowledgable about flashing, but one suggestion has come to my mind: if you can now get into TWRP (it wasn't clear whether you could based on your last post), try flashing a ROM without trying to clean the system partition. Just make sure the ROM matches the TWRP (i.e., big part ROM with big part TWRP).
Oh - another thought - folks in a number of threads have stated you need to explicitly follow both the recovery and ROM instructions for the XOOM. If you miss a step, people have had issues.