Database Info

[Q] Need help with CWM! SD card not mounted??

Today I managed to succesfully root my device. Then I wanted the 2.3.4 update so I did that following this guide (I have i9023 GRI54, KB3). Now comes the strange part: my Android-version is indeed 2.3.4, but my Smallband version is I9023XXKD1 now. And my Build-number has changed to GRJ22. Is this normal?
Anyway, then I flashed CWM again, because I lost root. I don't know what went wrong, but when I'm trying to get into recovery mode, it shows a exclamation mark in a triangle together with a small droid. I can't turn off my phone, so I can only get away from that screen by pulling out the battery.
I flashed CWM exactly the same as I did before the update to 2.3.4, 2 hours ago. Then it all went perfectly fine. What did I do wrong??

Maybe I need the i9020 version of CWM now? According to the bootloader interface my version is i9020. But it also said that before the 2.3.4 update.

Ok, now I managed to get root back. According to Rom Manager I have CWM installed, but I can't access it with bootloader interface.
And my phone also doesn't recognise my "sd-card" anymore.... That's probably the reason why I can't access recovery mode (it goes into normal recovery mode, not CWM)? If I flash CWM again, there is no error message, but it still doesn't work. I can't go back to stock because I need CWM for that!

[Q] unable to update and can't connect via usb anymore

Okay here are my problems:
I'm running a Nexus S - Rogers version (i9020AUCKE1)
My goal is to get to 2.3.6.
I can't connect via the USB anymore, whenever I try Windows says that it doesn't recognize the USB device. Mac doesn't say anything at all. I have tried turning USB debugging on (though I didn't before and it worked previously) - and I've tried multiple cables.
I can't install / update anything I've found so far through the recovery - everything I've tried fails signature validation.
I'm currently running this version:
Android 2.3.4/GTJ61/UCKE1 Radio/KA3 Bootloader
Unofficial, unsigned, must flash through ClockworkMod Recovery. Contains recovery, radio and bootloader.
Courtesy of XDA forum member scott8281
My phone is unlocked and was previously rooted; though through a series of unfortunate events, I no longer have superuser access directly on the phone (though there is a superuser.zip on my sdcard) and I'm on stock recovery instead of clockwork.
What I'm hopeful to do, at this point, is to get super user access again, get Clockwork back on it and skip the signature validation so I can get it updated. But I haven't figured out a way to do it yet.
I tried z4root but when I tried to root it, the app started but closed itself after about 2 minutes and didn't seem to actually do anything.
Anyone have any ideas of what I can try?

update - I've tried Gingerbreak and it's just hanging on me - doesn't seem to work for either.
Also - I can't find the USB Settings anywhere. I'm wondering if that's my problem with the ROM - it doesn't have the proper USB settings.

Hi,
I got a similiar problem a few weeks ago and found a solution in the internet, that worked for me: Just shut down the phone, put the battery out for approx. a minute. Put it back in and boot, and try again.
I could not believe it, because I don't see the technical explaniation how this could solve this problem - but it did worked, and that is what counts.
Good luck

If your phone is unlocked download rom manager and flash cwm from the app. Do this just after a fresh boot of the phone. If cwm isn't there when you boot into recovery reboot the phone and again flash cwm from rom manager as soon as the phone boots. This time it should stick. From cwm flash superuser.zip and you are rooted again. Then just flash the rooted version of the update.
Normally I recommend flashing recovery from fastboot, but in your case rom manager is the only way to go.
Sent from my Nexus S 4G using xda premium

[Q] [HELP] NS hangs on boot, no recovery, no USB

After checking lots of other recent posts, nothing has come close to the problems I'm having.
Nexus S (of course), i9020T, running CM7 before the trouble started. In order to load the OTA update I tried to flash back to stock 2.3.6. Flashed to 2.3.6 successfully (quickly went through setup process on 2.3.6, just to check.)
Then went back onto clockwork mod to install the ICS update. update went very quickly and I then tried rebooting the phone. Just get the ICS boot screen on an endless loop. Start the phone in fastboot mode, but now can't get to recovery (get "dead droidbug" image). Device doesn't show up when connected with USB on Mac, Windows or Linux. Ran ADB on computer and it says the device is not connected. Tried using Unbrickable, didn't detect the device. HOWEVER, when connected to Windows it shows up as "Android 1.0" in device manager, but says that there are no drivers isntalled for it, and none of the drivers from Android SDK work.
Device can still charge from USB, and I can get to fastboot on the device itself. If I can some how get the device to show up on USB I know I'd be set. Any thoughts?

filmgeekben said:
After checking lots of other recent posts, nothing has come close to the problems I'm having.
Nexus S (of course), i9020T, running CM7 before the trouble started. In order to load the OTA update I tried to flash back to stock 2.3.6. Flashed to 2.3.6 successfully (quickly went through setup process on 2.3.6, just to check.)
Then went back onto clockwork mod to install the ICS update. update went very quickly and I then tried rebooting the phone. Just get the ICS boot screen on an endless loop. Start the phone in fastboot mode, but now can't get to recovery (get "dead droidbug" image). Device doesn't show up when connected with USB on Mac, Windows or Linux. Ran ADB on computer and it says the device is not connected. Tried using Unbrickable, didn't detect the device. HOWEVER, when connected to Windows it shows up as "Android 1.0" in device manager, but says that there are no drivers isntalled for it, and none of the drivers from Android SDK work.
Device can still charge from USB, and I can get to fastboot on the device itself. If I can some how get the device to show up on USB I know I'd be set. Any thoughts?
Click to expand...
Click to collapse
i made this suggestion in another thread just a bit ago. I would try to slip a knife or something else thin under the tab in the phones usb port and push it up just a bit. My device was not being recognized or anything on my pc but would charge just fine. I did the afore mentioned and it works like a charm now.
other than that can't you push a recovery img through a terminal emulator on your phone?

I was able to connect to USB only a few minutes before this whole problem started, I even copied my backup folder from the device on to my computer. After the update, the drive disappeared.
On Windows it will appear as "Android 1.0" but says that drivers aren't installed, and the drivers installed from either Samsung or the Android SDK do not work for the device. I also tried using Odin as well as Unbrickable, which showed that it was connected, but failed when I tried pushing an image that way and said "Device not found".
I can get the device into Download mode in addition to fastboot, but neither can be recognized.

My phone did exactly the same connect very rarely and then only briefly, adb , fastboot and usb ( even sdcard on CWM) not working. I tried almost everything, even format all .....and then broke all....works only bootloader and CWM ...but what did not work anything ( adb, fastboot, usb) - I decided to go for repair because it was in warranty. Three weeks have passed since it is repaired....but they said that I will get back shortly. If you see that you can not do anything .... Think it take to repair....
When you start to have problems with usb will not take long and the phone will become unusable ! Get it repaired as quickly as you can , even if it's unlocked bootloader , if it have warranty will fix it....Good luck !

Surdu, I think you're right. I have arranged to have Samsung check it out, if they do wind up charging me for the repair hopefully it won't be too much.

filmgeekben said:
After checking lots of other recent posts, nothing has come close to the problems I'm having.
Nexus S (of course), i9020T, running CM7 before the trouble started. In order to load the OTA update I tried to flash back to stock 2.3.6. Flashed to 2.3.6 successfully (quickly went through setup process on 2.3.6, just to check.)
Then went back onto clockwork mod to install the ICS update. update went very quickly and I then tried rebooting the phone. Just get the ICS boot screen on an endless loop. Start the phone in fastboot mode, but now can't get to recovery (get "dead droidbug" image). Device doesn't show up when connected with USB on Mac, Windows or Linux. Ran ADB on computer and it says the device is not connected. Tried using Unbrickable, didn't detect the device. HOWEVER, when connected to Windows it shows up as "Android 1.0" in device manager, but says that there are no drivers isntalled for it, and none of the drivers from Android SDK work.
Device can still charge from USB, and I can get to fastboot on the device itself. If I can some how get the device to show up on USB I know I'd be set. Any thoughts?
Click to expand...
Click to collapse
that dead droidbug image is stock recovery. update your drivers(pdanet is an easy way how), fastboot a recovery, access the usb option in your newly flashed custom recovery, load a rom unto your sd storage, WIPE, then flash the rom. i think your problem was that you didnt wipe before flashing the ics rom. it was a big step between gingerbread and ics, you usually want to wipe when roms are that different.

simms22 said:
that dead droidbug image is stock recovery. update your drivers(pdanet is an easy way how), fastboot a recovery, access the usb option in your newly flashed custom recovery, load a rom unto your sd storage, WIPE, then flash the rom. i think your problem was that you didnt wipe before flashing the ics rom. it was a big step between gingerbread and ics, you usually want to wipe when roms are that different.
Click to expand...
Click to collapse
He can not update the drivers because when the phone connects to the computer nothing happens !!! And if you try to install PdaNetA300.exe or x64.exe you can not because you must have phone connected to it!
---------- Post added at 07:51 PM ---------- Previous post was at 07:46 PM ----------
If your computer detects the phone you can enter in the device manager and click rigt on the android drivers and update with : http://www.4shared.com/rar/_bgEMHqk/Nexus_S_Drivers_x86__x64.html
---------- Post added at 08:02 PM ---------- Previous post was at 07:51 PM ----------
filmgeekben said:
Surdu, I think you're right. I have arranged to have Samsung check it out, if they do wind up charging me for the repair hopefully it won't be too much.
Click to expand...
Click to collapse
Hey I'm very happy now!!!
Today I received the phone back after being in service....very curious : they left bootloader unlocked ....mention that so I sent and with CWM 5.0.2.0 installed ....
On receipt of repair writes that changed the screws and update the software ...with 2.3.6 but still it was installed before breaks!
And all that free because the phone was in warranty!

[Q] Help!, phone now not working after update

This morning my phone (nexus S) told me it had an update to 4.0.4, which i tapped install. I previously had ICS 4.0 (i think).
When the phone boots up all i get is the flashing colourful spash screen, and it doesn't move on from there.
I tried to get into recovery mode, but all i get is a android man lying down with an exclamation mark over him.
What can i do? what commands for ADB do i need to revert it back to a functional state? I hope its not bricked :-{

Was your phone rooted?
Sent from my GT-I9100 using XDA

rooted
Im not sure what the defination of rooted is but i previously had cyanogen mod on, but reverted back to standard android 2.3 then to the standard android 4, which when installed seem to also remove CWM which i had on.
It is unlocked though

it may work
I will suggest you either you can go to Samsung service center as your phone warranty is not void or nigher you have done anything that is not supported by Samsung or 2nd solution is that download the suitable official ROM from this forum for your phone, and also ODIN, and flash it by going into download mode.
also i will suggest you gain some knowledge how to flash your phone with ODIN before flashing it.

Sounds like you bricked it to me... good luck!!

jackwoz said:
This morning my phone (nexus S) told me it had an update to 4.0.4, which i tapped install. I previously had ICS 4.0 (i think).
When the phone boots up all i get is the flashing colourful spash screen, and it doesn't move on from there.
I tried to get into recovery mode, but all i get is a android man lying down with an exclamation mark over him.
What can i do? what commands for ADB do i need to revert it back to a functional state? I hope its not bricked :-{
Click to expand...
Click to collapse
pull the battery out..and try to enter recovery mod and wipe data/factory resert

Brick or no brick
Hi,
In order to find out if your phone is bricked you need to first remove the battery, replace it and then the do the three key boot to get the phone to boot into download mode.
If that works then you can locate the right firmware and then install via Odin.
If not the next step is to get a jig that forces the phone into download mode (provided it still has bootloaders) and then via Odin again install your firmware.
Otherwise it's a trip to Samsung I think.

Try pulling the battery and wait a few minutes, insert battery and try entering recovery mode again.

[Q] Help a n00b - Attempted root/custom ROM resulted in hard brick

My son was trying to unlock his Verizon Galaxy S3 and install Cyanogen Mod (KitKat). I didn't supervise, so I only have what he told me:
https://www.youtube.com/watch?v=AQdSOTdV06Q
I followed this guy's instructions to the T, but I forgot to unlock the bootloader for the phone, which the guy never mentions. He just assumes that you know that you have to have your phone rooted and the bootloader unlocked so you can flash a custom os to the phone's kernel. I flashed the image, and then put it into recovery mode, and it came up with the big yellow triangle with the message "THIS PHONE HAS SOFTWARE ON IT THAT IS NOT AUTHORIZED BY VERIZON WIRELESS!!!" I reset the phone by plugging it into my computer, and then tried to unlock the bootloader with an app and reboot and flash the image again. After i restarted the phone to put it into recovery mode, it wouldn't turn on.
I made an attempt to fix it, using the post on this board: http://forum.xda-developers.com/showthread.php?t=2581166 and got to a point where it would boot off of the microSD. I then tried to get it back to stock, so we could start all over again but wound up back to where it will now boot, but goes directly to the "THIS PHONE HAS SOFTWARE ON IT THAT IS NOT AUTHORIZED..." and I can't seem to get past this point.
Thanks for any help you can provide. He is currently stuck using a Galaxy S that I was able to put Cyanogen Mod on, so it's not as bad as it could have been!
Rob

rallen911 said:
My son was trying to unlock his Verizon Galaxy S3 and install Cyanogen Mod (KitKat). I didn't supervise, so I only have what he told me:
https://www.youtube.com/watch?v=AQdSOTdV06Q
I followed this guy's instructions to the T, but I forgot to unlock the bootloader for the phone, which the guy never mentions. He just assumes that you know that you have to have your phone rooted and the bootloader unlocked so you can flash a custom os to the phone's kernel. I flashed the image, and then put it into recovery mode, and it came up with the big yellow triangle with the message "THIS PHONE HAS SOFTWARE ON IT THAT IS NOT AUTHORIZED BY VERIZON WIRELESS!!!" I reset the phone by plugging it into my computer, and then tried to unlock the bootloader with an app and reboot and flash the image again. After i restarted the phone to put it into recovery mode, it wouldn't turn on.
I made an attempt to fix it, using the post on this board: http://forum.xda-developers.com/showthread.php?t=2581166 and got to a point where it would boot off of the microSD. I then tried to get it back to stock, so we could start all over again but wound up back to where it will now boot, but goes directly to the "THIS PHONE HAS SOFTWARE ON IT THAT IS NOT AUTHORIZED..." and I can't seem to get past this point.
Thanks for any help you can provide. He is currently stuck using a Galaxy S that I was able to put Cyanogen Mod on, so it's not as bad as it could have been!
Rob
Click to expand...
Click to collapse
Go to download mod (volume down + home + power button) then flash stock 4.3 or 4.4.2 via odin the one you was on.

To add to the above reply. If you are on 4.3 or 4.4.2 stock bootloader, you cannot unlock it to install custom recovery and custom ROM. You are limited to safestrap and compatible (same OS version, 4.3 or 4.4.2) touchwiz ROMs only. Do not attempt to use the app to unlock your phone once you are back on stock or you will brick again.