Database Info

[Q]recovery flash and nexus s driver issue

Hi
A couple of days ago I tried to flash the newer version of ClockWorkMod recovery (from v3.0.2.4 to 5.0.2.0) via ROM Manager, it seemed to install properly but when I tried to enter the recovery it sent me to the BOOTLOADER and there was written that I have no boot or recovery image installed, when I try to install the CWM manually via ADB it cant recognize my Nexus S when I'm in the bootloader (I re-installed the drivers but it didn't help) but when the phone is on I have access to the phone via ADB but I cant flash the CWM.
I tried the next commands:
adb shell
SU
flash_image recovery /sdcard/filename.img
and it showed me allot of memory errors.
Does anyone can help me?

someone can help me?

itkinbenny said:
someone can help me?
Click to expand...
Click to collapse
Flash 5.0.10 then 5.0.20 right after via rom manager
Sent from my Nexus S using xda premium

nbeebe24 said:
Flash 5.0.10 then 5.0.20 right after via rom manager
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
thanx, I tried it but it also didn't work

same problem here noob in nexus s please help

After I sent my NEXUS to a lab it works OK with the recovery they say that they don't know what this issue was but after the changed the rom to stock every thing worked OK

I am also suffering from the same issue, I think itnis caused by only a certain amount of memory being aloted for a recovery image as the newer version is a bit larger, anyone know how to fix this?
Sent from my Nexus S 4G using XDA App

ejleverett said:
I am also suffering from the same issue, I think itnis caused by only a certain amount of memory being aloted for a recovery image as the newer version is a bit larger, anyone know how to fix this?
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
in the lab they said that they pushed stock rom via some linux script they have to the nexus and after that they flashed recovery but I think that you can find how to do this in this forum (going back to stock) and to root it again and then you can flash recovery

I'm going thru the same thing after flashing ics rom. Now I had to downgrade to 3.0.0.1 in order ffor my recovery to work.....I even tried flashing each recovery one by one until I was on. 5.2
But its the same issue. No recovery unless I downgrade. Also none of my back ups are recognized.....
Sent from my Nexus S 4G using XDA App

Having trouble rooting my Nexus S

Hey,
When I first rooted my phone, it was easy and took 30 mins max, but now I've updated to jellybean and trying to root again, I just can't seem to install adb and the drivers (reinstalled OS).
I've tried various tutorials, but it's just not working.
If anyone could help via teamviewer, it'd be very much appreciated.

jh1997sa said:
Hey,
When I first rooted my phone, it was easy and took 30 mins max, but now I've updated to jellybean and trying to root again, I just can't seem to install adb and the drivers (reinstalled OS).
I've tried various tutorials, but it's just not working.
If anyone could help via teamviewer, it'd be very much appreciated.
Click to expand...
Click to collapse
Why not just install a custom ROM. Isn't that what you're going to end up doing anyways?
Sent from my Nexus S using Codename Android Jelly Bean

jh1997sa said:
Hey,
When I first rooted my phone, it was easy and took 30 mins max, but now I've updated to jellybean and trying to root again, I just can't seem to install adb and the drivers (reinstalled OS).
I've tried various tutorials, but it's just not working.
If anyone could help via teamviewer, it'd be very much appreciated.
Click to expand...
Click to collapse
Try this works like a charm http://forum.xda-developers.com/showthread.php?t=1544940
Sent from my Nexus S using xda premium

simonb255 said:
Try this works like a charm http://forum.xda-developers.com/showthread.php?t=1544940
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Hi, thanks for telling me about this but once I've selected Nexus S blah... my phone reboots into fastboot mode and then on the tool window it just says,
< waiting for device >
I don't know why I'm having so much trouble, I've rooted many phones so far.

jh1997sa said:
Hi, thanks for telling me about this but once I've selected Nexus S blah... my phone reboots into fastboot mode and then on the tool window it just says,
< waiting for device >
I don't know why I'm having so much trouble, I've rooted many phones so far.
Click to expand...
Click to collapse
You need to install the Nexus S adb drivers. Just flash a ROM that's rooted already. There is a ota rooted ROM if you're trying to stay stock.
Sent from my Nexus S using Codename Android Jelly Bean

Recovery
Do you have a custom recovery installed such as CWM?

No I don't have a custom recovery because it was removed when I flashed ota jellybean
Sent from my Nexus S using Tapatalk 2

jh1997sa said:
No I don't have a custom recovery because it was removed when I flashed ota jellybean
Sent from my Nexus S using Tapatalk 2
Click to expand...
Click to collapse
just flash the new CWM 6.0.1 and install a custom rom..

Cascabreu said:
just flash the new CWM 6.0.1 and install a custom rom..
Click to expand...
Click to collapse
Yea, I've been telling him this. Quit trying to root your phone. Just install a ROM that's rooted already. Quicker and easier.
Sent from my Nexus S using Codename Android Jelly Bean

He can't flash it if he doesn't have root or fast boot! Try installing pdanet on tour computer, it magically made it work for me. Also try a couple different USB cables, for example my girlfriends USB cable that came with her WP7 doesn't let me do a adb or fastboot
Sent from my Nexus S 4G using xda premium

AlphaEchoViktorSierra said:
He can't flash it if he doesn't have root or fast boot! Try installing pdanet on tour computer, it magically made it work for me. Also try a couple different USB cables, for example my girlfriends USB cable that came with her WP7 doesn't let me do a adb or fastboot
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Uhh he has fast boot. Vol up and power boots into fastboot. He doesn't need to be rooted to get there. Now from fastboot, install clockwork... then flash ROM. Simple.
Sent from my Nexus S using Codename Android Jelly Bean

Sounds like he is having problems with the Android SDK http://developer.android.com/sdk/index.html
Use the sticky to help http://forum.xda-developers.com/showthread.php?t=1623481 or this
http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
http://forum.xda-developers.com/showthread.php?t=1785672
Or I could be wrong but I think he can't cmd fastboot flash recovery recovery.img.

When I try to flash recovery via fast boot it just says waiting for device.
I have pdanet installed too.
I'm going to try it on my laptop tomorrow, maybe it will work on that.
Sent from my Nexus S using Tapatalk 2

jh1997sa said:
When I try to flash recovery via fast boot it just says waiting for device.
I have pdanet installed too.
I'm going to try it on my laptop tomorrow, maybe it will work on that.
Sent from my Nexus S using Tapatalk 2
Click to expand...
Click to collapse
No need for padnet. Just the right drivers and of course know how to install them. Go to nexushacks.com and watch the tutorial

dEris said:
Uhh he has fast boot. Vol up and power boots into fastboot. He doesn't need to be rooted to get there. Now from fastboot, install clockwork... then flash ROM. Simple.
Sent from my Nexus S using Codename Android Jelly Bean
Click to expand...
Click to collapse
Uhh he has fastboot on his phone but the fastboot commands are not working for him, aka he doesn't have fastboot.
Drivers and getting it is a total pain in the ass, keep trying new things and eventually it will work out. Did you try a different USB cable?

AlphaEchoViktorSierra said:
Uhh he has fastboot on his phone but the fastboot commands are not working for him, aka he doesn't have fastboot.
Drivers and getting it is a total pain in the ass, keep trying new things and eventually it will work out. Did you try a different USB cable?
Click to expand...
Click to collapse
https://docs.google.com/folder/d/0B7O2O1p4iWXTU1R2R0hra3VaQmc/edit
Here are the drivers

AlphaEchoViktorSierra said:
Uhh he has fastboot on his phone but the fastboot commands are not working for him, aka he doesn't have fastboot.
Drivers and getting it is a total pain in the ass, keep trying new things and eventually it will work out. Did you try a different USB cable?
Click to expand...
Click to collapse
Uhh he does have fast boot. He just needs the adb drivers and the SDK. That is all. Then he can boot into fastboot then flash recovery then ROM. Viola!
Sent from my Nexus S using Codename Android Jelly Bean

If your device is a i9023, you may have to follow this guide.
i9023 has particularities on installation.
forum.xda-developers.com/showthread.php?t=1007782

Problems flashing custom recovery

I have a strange problem. A while ago I successfully unlocked my infinity. That was before the jb update. I also successfully flashed custom recoveries and several roms. Didn't ran into any problems. When the official jb update came out, I restored original recovery and flashed a stock ics Rom, and after that successfully applied the jb update. The second update .30 also went smooth. I used the update file from Asus servers. Now I want to flash a custom recovery again in order to flash cleanrom. In adb I see my device and I can reboot with fastboot and stuff. So I think my drivers are ok. However as soon as I start to flash recovery.img it just says sending recovery and that's it. It just hangs there. Nothing happens. I tried everything, from changing usb ports and uninstalling drivers... It just can't send the recovery img. I use Scott's script to flash the recovery.blob. any ideas?
Sent from my HTC One X using xda app-developers app

might try the GOOManager in the play store

hillyard said:
might try the GOOManager in the play store
Click to expand...
Click to collapse
I can't use it because it needs root, and as long as I don't have a custom recovery I'm unable to root my stock jellybean Rom. Or is there already another way to root?
Sent from my HTC One X using xda app-developers app

glenner05 said:
I can't use it because it needs root, and as long as I don't have a custom recovery I'm unable to root my stock jellybean Rom. Or is there already another way to root?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Are you saying you can not get TWRP or CWM installed ? or are you saying you do have one installed but no root ?
If it is the latter then can't you just flash a custom rom that has root built in ( like Baked ) then go back to twrp and now with root you can wipe and flash stock. ? I am sorry if I am miss understanding your question. But at least you get a free 'bump'

Thibor69 said:
Are you saying you can not get TWRP or CWM installed ? or are you saying you do have one installed but no root ?
If it is the latter then can't you just flash a custom rom that has root built in ( like Baked ) then go back to twrp and now with root you can wipe and flash stock. ? I am sorry if I am miss understanding your question. But at least you get a free 'bump'
Click to expand...
Click to collapse
He said he has no root (why he couldn't use Goomanger) and he can't flash recovery.

buhohitr said:
He said he has no root (why he couldn't use Goomanger) and he can't flash recovery.
Click to expand...
Click to collapse
Thats correct, i am trying to get custom recovery, after that root is no problem.
Edit: i just installed a clean windows 8 installation. So no old drivers left behind or other weird stuff. I put my transformer in fastboot mode, driver is automatically installed, i see it under device manager. Stillno luck.... it hangs saying sending recovery.... no error messages. My previous attempt was under win7.
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app

glenner05 said:
Thats correct, i am trying to get custom recovery, after that root is no problem.
Edit: i just installed a clean windows 8 installation. So no old drivers left behind or other weird stuff. I put my transformer in fastboot mode, driver is automatically installed, i see it under device manager. Stillno luck.... it hangs saying sending recovery.... no error messages. My previous attempt was under win7.
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
Click to expand...
Click to collapse
Glenner, did you make sure you have the img file in the same folder as you fastboot/adb command files?

If it says "sending recovery", I'd assume that it found the local file.
I don't use Windows, but I always read about driver issues in Windows. Maybe the auto-installed driver is wrong? Does "fastboot devices" return question marks or nothing?

i'm happy to report that finally it worked! seemed something strange with drivers/USB ports after all. Despite i already changed USB ports under my win 7 installation, i tried it again under win8, and suddenly it worked. I didn't reinstall the drivers or something, all went automatically. So the strange issues are driver issues for sure. Anyway, currently happy running cleanrom 2.3
thanks for all your suggestions and thinking along.....
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app

Strange TWRP problem, no OS detected etc. Boots fine to stock

I ran the causal root applet on a new SG3 on 4.1.2. Ran root, the unlock script and installed TWRP. Booted into recovery and I got the error for a locked bootloader. I used download mode to get back to the stock rom and then used E-Z unlock to unlock the bootloader. Was able to boot into recovery this time but TWRP read internal and external memory as 0mb, unable to make a backup, and gave a no OS error when went to reboot. I updated TWRP with TWRP manager but the problems are still persistent. Phone boots fine and reboots fine at the moment.
I'm not sure what to do now though. I'm at the point were I don't care if I get stuck with the OTA update but I'm afraid that will brick the phone. I'm not sure what went wrong with TWRP, since this is the second S3 I've rooted.
Any sugestions? I'm afraid to use odin or try anything else since the phone currently works fine. But I'd prefer to not have to sleep in fear it might force the OTA update while I'm asleep and wake up to a bricked phone.
I tried searching, the best I could find is that newer versions of TWRP can't read the memory on a 4.1.2 rom, but the problems were there when I originally started with the recommended version.
Thanks for any help anyone can give.

Try to use cwm or philz and see if you have the same issue.
Sent from my SCH-I535 using Tapatalk 2

Xx

BadUsername said:
Try to use cwm or philz and see if you have the same issue.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Can you install a different custom recovery over one using the causal applet? I was planning on trying to reinstall TWRP but I wasn't sure if I had to do it a certain way like through odin or Using the unified tool kit?
Thanks for the help so far!

Smogon said:
Can you install a different custom recovery over one using the causal applet? I was planning on trying to reinstall TWRP but I wasn't sure if I had to do it a certain way like through odin or Using the unified tool kit?
Thanks for the help so far!
Click to expand...
Click to collapse
No.
Download latest philz touch recovery d2lte zip, then flash it in recovery, then reboot recovery.
Then check and see if you're getting a similar error message.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
No.
Download latest philz touch recovery d2lte zip, then flash it in recovery, then reboot recovery.
Click to expand...
Click to collapse
I can't, recovery doesn't detect my internal or external memory. That's my main issue.

Smogon said:
I can't, recovery doesn't detect my internal or external memory. That's my main issue.
Click to expand...
Click to collapse
OK.
Then download the Odin version and flash through that. Then boot the phone into recovery.
Or download ez recovery, and the latest cwm image file, and flash through that from your rom.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
OK.
Then download the Odin version and flash through that. Then boot the phone into recovery.
Or download ez recovery, and the latest cwm image file, and flash through that from your rom.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I'll try the second option, Thanks!

BadUsername said:
OK.
Or download ez recovery, and the latest cwm image file, and flash through that from your rom.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I tried CWM and the stock recovery through EZ, both gave the same error as TWRP, unable to mount /
I'm really confused as to whats wrong. At this point I don't care if I get stuck with the OTA 4.3, but I don't want to try to update it with the recovery still not reading either my SD cards.
Any Ideas?

Are you sure of your phone model? I believe it puts it on the screen in download mode and also on a sticker under the battery. I'm mostly curious because you mention that this is a new phone with 4.1.2. Are you trying older versions of cwm as well?
Sent from my SCH-I535 using XDA Premium 4 mobile app

Smogon said:
I ran the causal root applet on a new SG3 on 4.1.2. Ran root, the unlock script and installed TWRP. Booted into recovery and I got the error for a locked bootloader. I used download mode to get back to the stock rom and then used E-Z unlock to unlock the bootloader. Was able to boot into recovery this time but TWRP read internal and external memory as 0mb, unable to make a backup, and gave a no OS error when went to reboot. I updated TWRP with TWRP manager but the problems are still persistent. Phone boots fine and reboots fine at the moment.
I'm not sure what to do now though. I'm at the point were I don't care if I get stuck with the OTA update but I'm afraid that will brick the phone. I'm not sure what went wrong with TWRP, since this is the second S3 I've rooted.
Any sugestions? I'm afraid to use odin or try anything else since the phone currently works fine. But I'd prefer to not have to sleep in fear it might force the OTA update while I'm asleep and wake up to a bricked phone.
I tried searching, the best I could find is that newer versions of TWRP can't read the memory on a 4.1.2 rom, but the problems were there when I originally started with the recommended version.
Thanks for any help anyone can give.
Click to expand...
Click to collapse
by any chance did u try to setup dualboot? I have a similar issue where nothing gets mounted and o mb for storage, .only receovery i get to work is cwm. im pretty sure its a partition issue but idk. i tried flashing pit files for my phone but so far the issue remains.

xevildoerxx said:
by any chance did u try to setup dualboot? I have a similar issue where nothing gets mounted and o mb for storage, .only receovery i get to work is cwm. im pretty sure its a partition issue but idk. i tried flashing pit files for my phone but so far the issue remains.
Click to expand...
Click to collapse
No I just used the causal tool.
dpeeps74 said:
Are you sure of your phone model? I believe it puts it on the screen in download mode and also on a sticker under the battery. I'm mostly curious because you mention that this is a new phone with 4.1.2. Are you trying older versions of cwm as well?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm pretty sure, has all the verizon bloat and logos, also I'm pretty sure the causal applet bricks the international ones. I don't remember the version of twrp that the causal script flashed, but I tried that one, the most recent one, and 2.5 i think from EZ recovery. The stock recovery from EZ has the same issue now though which is what really confuses me. at the moment I have root dissabled and the bootloader is locked and its back with the stock recovery, it still says custom when i reboot the phone though.

[Q] Backup won't restore.

So I installed the lateat CM12 nightly, wasn't really impressed yet and went to go restore my backup and once it's done restoring, it get stuck at the bootscreen animation. Just keeps going and going abs going. I used the latest cwm touch recovery as CM12 is not compatible with MultiROM. I would just flash the factory img back but my computer decided to it doesn't ever want to recognize adb avid fastboot on Linux.
Anyone know where I can find a flashable zip for the factory 5.0.1 ROM? Any help would be appreciated!

Try googling Nexus 5 factory image...

Here's a flashable 5.0 : http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523

Niflheimer said:
Here's a flashable 5.0 : http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523
Click to expand...
Click to collapse
Now I'm assuming I'd have to unroot it and flash stock recovery and lock the bootloader to get it to update to 5.0.1?

No, it's flashable in your custom recovery. It's 5.0 though
Sent from my Nexus 5 using XDA Free mobile app

Yeap , ota needs stock recovery. Also , switch to twrp since cwm isn't playing nice with L.

jd1639 said:
No, it's flashable in your custom recovery. It's 5.0 though
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I was talking about the 5.0.1 update but thanks.

Niflheimer said:
Yeap , ota needs stock recovery. Also , switch to twrp since cwm isn't playing nice with L.
Click to expand...
Click to collapse
I'm on the stock ROM you linked too, stock recovery, and unrooted but, when I get the update for 5.0.1 and try and install it, I get an error. Do I need to relock my boatloader?

asd87 said:
I'm on the stock ROM you linked too, stock recovery, and unrooted but, when I get the update for 5.0.1 and try and install it, I get an error. Do I need to relock my boatloader?
Click to expand...
Click to collapse
You're on a custom Rom. The ota isn't going to work. And you don't need to relock your bootloader. If you can afford to wipe your data download the 5.0.1 factory image. Extract it and use the flash-all.bat
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
You're on a custom Rom. The ota isn't going to work. And you don't need to relock your bootloader. If you can afford to wipe your data download the 5.0.1 factory image. Extract it and use the flash-all.bat
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
My computer is Linux, and adb and fastboot for whatever reason unknown to me, won't install. That's why I asked for a zip file of the factory image. Thanks for the help though.

asd87 said:
My computer is Linux, and adb and fastboot for whatever reason unknown to me, won't install. That's why I asked for a zip file of the factory image. Thanks for the help though.
Click to expand...
Click to collapse
Well, unfortunately, there isn't a 5.0.1 flashable rom available right now. If you can't get fastboot to work on your Linux machine you're kind of sol as you need to be 100% stock to get the ota to work. That means stock recovery in your case. Google recovery zip collection xda. There's a custom recovery flashable stock recovery there.
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
Well, unfortunately, there isn't a 5.0.1 flashable rom available right now. If you can't get fastboot to work on your Linux machine you're kind of sol as you need to be 100% stock to get the ota to work. That means stock recovery in your case. Google recovery zip collection xda. There's a custom recovery flashable stock recovery there.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I have the stock 5.0 recovery that I installed through Flashify. I'll barrow a windows computer or something lol

asd87 said:
I have the stock 5.0 recovery that I installed through Flashify. I'll barrow a windows computer or something lol
Click to expand...
Click to collapse
I'd work on getting adb/fastboot working on your Linux machine. You're going to need it in the long run.
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
I'd work on getting adb/fastboot working on your Linux machine. You're going to need it in the long run.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I've spent hours trying to get it work one night. I'll do some note searching for more advice and again thanks.

jd1639 said:
I'd work on getting adb/fastboot working on your Linux machine. You're going to need it in the long run.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Did some more digging, got it install, and flashed the factory img for 5.0.1 and twrp recovery then superSU through twrp.
Mods please lock the thread thanks.

Get wugfreshes Toolbox. It has access to all factory images. Some people are not fans of "one click solutions" but this has never let me down.
There's a flushable zip on here also. Put it in a search in the app and you should come across it. It IS the full version.

Did you ever find out why the CWM restore led to getting stuck on boot animation??
Just ran into this last night. Tried restoring 2 different CWM backups and both got stuck on boot animation.
I eventually got a new ROM flashed. Going to try TWRP recovery I suppose.
I know I never had this problem with 4.4, this was the first time I have restored a LP ROM..

one7dchevy said:
Did you ever find out why the CWM restore led to getting stuck on boot animation??
Just ran into this last night. Tried restoring 2 different CWM backups and both got stuck on boot animation.
I eventually got a new ROM flashed. Going to try TWRP recovery I suppose.
I know I never had this problem with 4.4, this was the first time I have restored a LP ROM..
Click to expand...
Click to collapse
My guess would be; cwm hasn't been optimized for Lollipop. Cyanogen has just recently started working on 5.0 and they probably haven't touched the recovery too much. But that's just my guess.

asd87 said:
My guess would be; cwm hasn't been optimized for Lollipop. Cyanogen has just recently started working on 5.0 and they probably haven't touched the recovery too much. But that's just my guess.
Click to expand...
Click to collapse
Yea figured something like that.
Got TWRP installed, will try to update after my next nandroid restore so that any old CWM users will know..