Database Users

[Q] nexus s just shows google logo after rebooting

So i tried to root my phone using one of the tutorials and ended up with a padlock screen on my phone. after researching i ALOT i decided on hard reseting my phone from the recovery menu. but all i see now is the google logo i believe i have deleted the 2.3.4 while reseting. can someone guide me from here. i am a n00b and i have had this phone for just 2 days. thanks in advance

anyone who can help?

youngballer said:
anyone who can help?
Click to expand...
Click to collapse
Please be more specific.
What tutorial did you use?
Did you download clockwork recovery?
Do you have the superuser zip?
If you can enable fast boot and fastboot flash recovery you should be able to mount your usb storage in CWM and then install a ROM and the su zip.

stuck on the nexus s boot screen
Babydoll25 said:
Please be more specific.
What tutorial did you use?
Did you download clockwork recovery?
Do you have the superuser zip?
If you can enable fast boot and fastboot flash recovery you should be able to mount your usb storage in CWM and then install a ROM and the su zip.
Click to expand...
Click to collapse
i used the one mentioned in addictive tips website (http://www.addictivetips.com/mobile/how-to-root-nexus-s-with-a-single-click-using-superboot/). i basically followed what these guys had mentioned.
since this failed i read that the other option is to go through fastboot > recovery > and clear everything but this did not change anything.
can someone give me a step by step guideline on how to continue. i dont mind going back to the stock 2.3.4 android. i just bought the phone yesterday

Which version do you have? The sprint or t mobile? Check if you can go into fast boot hold down volume up and then powerbutton. If not you may have to Odin it if not. That super one click looks old..
Sent from my Nexus S 4G using XDA App

chewbz said:
Which version do you have? The sprint or t mobile? Check if you can go into fast boot hold down volume up and then powerbutton. If not you may have to Odin it if not. That super one click looks old..
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
I am in Canada but the model is 19020 A. I can get to the fastboot mode but don't know what to do after that.

I have the 4g so I don't want to give you the wrong information and never encountered this situation so sorry dude. Hopefully a more experanced user can help you out.
Sent from my Nexus S 4G using XDA App

Btw if all fails you can Odin it
Sent from my Nexus S 4G using XDA App

its all good thanks for trying to help

If your ROM flashed incorrectly, it would lead to your phone being in a state where it just shows a GOOGLE with a Padlock; kind of like turning on a computer without an operating system.
You would have to read the instructions on rooting your phone, which involves using fastboot and flash recovery from fastboot (All this is in the rooting guide). Simply reflash the recovery so you boot up back in recovery and try flash the rom again.

The same happened to me, I fixed it buy flashing a stock boot.img
Sent from my Nexus S using XDA App

thanks for the replies. how do i flash from the fastboot mode? when i plug it in to my computer i cant see the drive but my computer can detect the nexus s is plugged in

Set up adb first, they have the guides in the dev section, I used wolverines guide, you'll have to look for the software img, I don't know where it is at for the GSM model. Good luck
Sent from my Nexus S 4G using XDA App

Sounds like you're rooted and have recovery installed, but your OS is hosed.
Flash a ROM.

thanks for the replies guys. i have the adb setup on my laptop. i took it to one of the stores and he said he cant reflash it for some reason. he said he needs to get some software off samsung and it will take him a day. my phone is brand new and i didnt wanna trust him. do u guys think i should use odin? one of my friend has a galaxy s and he said odin should work fine on my phone.

Can you get into the ClockworkMod recovery menu? Turn the phone completely off then hold VolUp and Power until you get into Recovery.
If you get there, you're golden. Just download a ROM (I recommend Deck's) and away you go.

i can get into recovery but it gives me option like wipe everything and i selected that. but when i reboot the phone the same locked screen pops up. anyone from toronto here who i can contact?

youngballer said:
i can get into recovery but it gives me option like wipe everything and i selected that. but when i reboot the phone the same locked screen pops up. anyone from toronto here who i can contact?
Click to expand...
Click to collapse
Basically with those wipe commands you make the Rom unuseable. You have to flash a new one or apply it via Odin. There are various guides on this forum section. Odin requires less technical knowledge but is a bit more risky then flashing via recovery. Odin and the Roms for that method can be obtained from samfirmware.com. Zipped roms can be found in the development section here.
Sent from my Nexus S

Stuck in a bootloop after trying to flash a new 2.3.4 ROM?

Welcome to my thread on bootloop fixes for flashing new ROM's through CWM. ​
I have seen many cases where people will get stuck in a bootloop from flashing a newer 2.3.4 ROM with CWM, and this has also happened to me. Please be aware I made this guide for AT&T Atrix 4G's. I am unaware if this works for international devices.
Click to expand...
Click to collapse
DISCLAIMER:
I AM NOT RESPONSIBLE FOR ANYTHING THAT MAY GO WRONG WHILE FOLLOWING MY INSTRUCTIONS. YOU SHOULD ALREADY KNOW THERE IS ALWAYS A RISK OF BRICKING YOUR DEVICE WHILE FLASHING.
DO NOT DO THIS IF YOU ARE COMING FROM A 2.3.4 STOCK AT&T OTA UPDATE ROM.
THIS WILL WIPE ALL DATA EXCEPT INTERNAL MEMORY AND THE SD CARD, AND MAKE YOUR PHONE LIKE NEW.
ALSO, BE AWARE THIS IS FOR AT&T, NOT INTERNATIONAL.
Click to expand...
Click to collapse
WHY?:
In almost every bootloop case, it is because the CWM version installed on your atrix is older then what the ROM maker made it for. For example, if you were like me and flashed the HKTW ROM right when it came out with Tenfar's first unlocked CWM recovery, then tried to flash a new ROM such as Kenneth's 2.3.4 AT&T, then you would be stuck in a bootloop. So again, you always need the latest CWM.
Click to expand...
Click to collapse
SOLUTION?:
WINDOWS ONLY:
Prerequisites:
1.2.6 SBF file (the password to extract the file is "atrixbl")
RSD Lite 5.0
Drivers: 32 bit OR 64 bit
INSTUCTIONS:
1. Make sure your phone is turned off
2. Take out your microSD card and SIM card for the flashing process
3. While turning the phone on, hold the Volume Up button until it acknowledges RSD
4. Your device will say “Starting RSD protocol support”
5. Run “RSD Lite” on your computer
6. Press the “. . .” button next to the box labeled “Filename”
7. Load up the SBF file (The SBF file is located inside of the .gz file, you must extract it out before loading it into RSD Lite)
(Use WinRAR or 7-Zip to extract the .gz file on your computer)
8. Plug your device into your computer
9. RSD Lite should recognize your device and say “Model: NS Flash Olympus” and “Connected…”
10. Press the “Start” button
11. Be patient while the phone reboots. It will take a long time.
12. OTA update from 1.2.6, all the way to 1.8.3
Download "Rom Manager" from the android market.
13. Click the first option "Flash ClockworkMod Recovery"
14. Select Motorola Atrix 4G.
15. Now you're all set and back in the game. You are safe to flash any new ROMs with this OFFICIAL CWM. And Rom Manager will let you know when a new CWM version is available.
Click to expand...
Click to collapse
IF ANYTHING IS INCORRECT, PLEASE LET ME KNOW. ALSO, IF THESE METHODS DO NOT WORK, LET ME KNOW AND I WILL UPDATE THE GUIDE. WHAT I HAVE POSTED HERE IS BASED ON WHAT WORKED FOR ME, AND EVERYONE I HAVE HELPED.
Click to expand...
Click to collapse
If you would like to donate to me, I will put a link below. What I do with donations is find ROM developers, and see their current work progress, and donate to them. So anything you donate to me, gets donated to future ROM making.
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=8Q3MSD9KW2GD6
Click to expand...
Click to collapse
Thank you for everyone who has given us ROMs, hacks, mods, you name it. This device is nothing without you guys!
Click to expand...
Click to collapse

Reserved
Sent from my MB860 using XDA Premium App

jbrussee said:
Does this not effect anyone?
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
People who are on the ota DO NOT flash back to 1.83 or prior op make this clear please although most will know some noobs wont lol
edit my fault you did, maybe a little bigger? if not its ok at least you have it

Yeah, I made sure I said that.
Sent from my MB860 using XDA Premium App

hi im posting this so I can post in the development section.

LMAO Techno. You got punked on two consecutive threads. Why do you have to be so rude and arrogant? Oh and please follow your own advice.....read before posting any comment.
Sent from my MB860 using XDA App

logantyler said:
hi im posting this so I can post in the development section.
Click to expand...
Click to collapse
+1 This place is way to aggressive with new users.

bootloop
Hi All,
I wanted to add my solution for having my phone stuck in a bootloop and then soft bricking it. My phone did not unlock successfully
1. Download a working version of 1.83
2. Download RSD Lite for your computer
3. When starting phone enter recovery by holding the volume down and pressing the power button, when the recovery option at the top shows up, use the volume down to get to RSD Mode. Volume Up selects.
4. Launch RSD Lite
5. Plug phone into computer using USB and RSD Lite should recognize phone.
6. Select the 1.83 file. Then run it
7. This may take some time, but it will boot your phone back to stock settings.
8. Read directions more carefully next time when you install a custom rom.
Hope this helps someone!

Thanks for more input!
Sent from my Motorola Atrix 4G MB860 using XDA Premium App

Hello, I installed GingerBlur and Now want to upgrade to Gingerbread. I am having some issues with doing an OTA upgrade. I aslo no longer have a PC which I used to root and flash before. Any help would be greatly appreciated.

I believe your instructions are only for AT&T users (judging by the files and OTA numbers).
If so, you should state that so some new International user doesn't try this and hard brick.

Zero-k, thank you for informing me of this.
Sent from my Motorola Atrix 4G MB860 using XDA Premium App

[Q] 3.2 wifi only root

hi all i cant seem to root my xoom.
to start i have a uk wifi only model and have flashed the 3.2 usa wifi.
works perfectly, i have unlocked the bootloader flashed root boot and then when i give the command fastboot reboot to then try and enter the recovery it just gets jammed on motorola logo does anyone know what im doing wrong i have followed several guides to the letter know and i cant seem to get root,

You didn't explain exactly what you are doing (have done) when you get stuck at the dual core screen.
One problem that can occur when rooting is overwriting your new Clockworkmod Recovery with stock recovery. In case this is the problem, here is
some important information to help get the new CWM recovery to stick.
From a thread called "an Idiot's Guide to flashing the Xoom" with info originally by public animal:
To install recovery image (CWM)
Download the recovery image file and save it to your computer
1 Boot into flash mode with 'adb reboot bootloader'
2 Install your downloaded recovery image
C:\Documents and Settings\Anders> fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
3 Restart the device with 'fastboot reboot'. Timing is essential here, so be alert when the device restarts, or you will have to redo this process
4 Enter CWM with the following procedure: Once the Motorola logotype is shown, start counting to 3. At 3, press the Volume Down button. This should result in the text 'Android Recovery' in the top left corner. If it does not work, experiment with the timing ... 5 When 'Android Recovery' is shown press the Volume Up button. This should invoke the CWM recovery menu. If that works, then congratulations for reaching this far .
Here is a potential pitfall. If you are unable to enter CWM *before* the device boots into Honeycomb, then the newly installed recovery image will be overwritten by the system default recovery.

When it gets jammed after the bootloader unlock process it stays on the Motorola dualcore logo' if I press power and up to restart it won't boot normally at all it just stays on moto logo and then I have to reflash for it to boot up normal' I don't understand where I'm going wrong' I have followed the threads to the letter a DB and fastboot fully working but something is stopping me from getting root.
Sent from my Xoom using XDA Premium App

bearusa said:
When it gets jammed after the bootloader unlock process it stays on the Motorola dualcore logo' if I press power and up to restart it won't boot normally at all it just stays on moto logo and then I have to reflash for it to boot up normal' I don't understand where I'm going wrong' I have followed the threads to the letter a DB and fastboot fully working but something is stopping me from getting root.
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
I would like to add I had no probs rooting my Sony experia play using adb and fastboot its weird I just can't put my finger on it'
Sent from my Xoom using XDA Premium App

bearusa said:
I would like to add I had no probs rooting my Sony experia play using adb and fastboot its weird I just can't put my finger on it'
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
It would help if we knew which guide you were using.

Guide for usa 3.2 wifi and 3g posted by jase33 in xoom android dev' than for your help guys
Sent from my Xoom using XDA Premium App

okantomi said:
It would help if we knew which guide you were using.
Click to expand...
Click to collapse
Than mate your guide sorted me out I'm now rooted and have recovery' I'm thinking I may have been entering a cmd incorectly'
or something or my recovery.img was corrupted I redownloaded files followed the guide you posted for me and it worked a treat.
Thanks for your help mate much gratitude and appreciation to you.
Sent from my Xoom using XDA Premium App

bearusa said:
Than mate your guide sorted me out I'm now rooted and have recovery' I'm thinking I may have been entering a cmd incorectly'
or something or my recovery.img was corrupted I redownloaded files followed the guide you posted for me and it worked a treat.
Thanks for your help mate much gratitude and appreciation to you.
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
I'm so glad it worked out. Now enjoy your rooted Xoom!

okantomi said:
I'm so glad it worked out. Now enjoy your rooted Xoom!
Click to expand...
Click to collapse
This thing is flying now' got rid of bloat once again thanks for your help
Sent from my Xoom using XDA Premium App

Cwm recovery issues

Hey guys, i have a few weeks experience flashing and all that leet stuff, but it seems i have a problem! I started to modify my ATRIX on 2.3.4, i unlocked sim, rooted, unlocked bootloader, and flashed custom recovery. I played around with a few roms, then i decided to update my fw to 2.3.6, well before i could do that i had to undo all mods so i ended up flashing a stock 2.3.4 fw and upgraded OTA. Im pretty sure that was my mistake... i may have needed an unlocked 2.3.6 sbf.. i re-rooted, and flashed cwm with rom manager, now when i go to boot in recovery mode i get failed to boot 2 starting rsd protocol. Everything is fine i just need to know where i messed up and how to get cwm running again. P.S. ive also been having an issue with my camera! I open the cam app and i get black screen, factory reset does NOT fix! Ive seen post's saying that the module is bad if that does not work BUT, when using flashlight app the flash lights up for a sec and then shuts off. When i switch to front camera it will stop responding, i'll click wait and after a min it will show image and i can take a pic(only with front cam). If i could get both issues solved i would be very grateful! If any other info is needed ill be sure to respond asap! Thank you in advanced for reading and assisting with my issues!
Sent from my MB860 using XDA

Get the cwm recovery img & flash with Fastboot and that should fix your recovery.
Sent from my MB860 using Tapatalk 2

Thanks for a reply but I did that as well and ended up getting an error. "Failed to process command flash:recovery error(0x180002)". I tried this method at first, received that error then tried to flash cwm through rom manager and recieved failed to boot2 starting rsd protocol.
Sent from my MB860 using XDA

Try unlocking bootloader again just to make sure ... Maybe that factory firmware closed hole on you when flashed.. Then flash cwm image ....

xRawwRRRRx said:
Thanks for a reply but I did that as well and ended up getting an error. "Failed to process command flash:recovery error(0x180002)". I tried this method at first, received that error then tried to flash cwm through rom manager and recieved failed to boot2 starting rsd protocol.
Sent from my MB860 using XDA
Click to expand...
Click to collapse
XRange said:
Try unlocking bootloader again just to make sure ... Maybe that factory firmware closed hole on you when flashed.. Then flash cwm image ....
Click to expand...
Click to collapse
+1. You'll always need to re-flash pudding BL after using an .sbf.

ghost_og said:
+1. You'll always need to re-flash pudding BL after using an .sbf.
Click to expand...
Click to collapse
Would you happen to have the file? 2.3.6
Sent from my MB860 using XDA

xRawwRRRRx said:
Would you happen to have the file? 2.3.6
Sent from my MB860 using XDA
Click to expand...
Click to collapse
Think what you seek lies here in Puddling thread..
http://forum.xda-developers.com/showthread.php?t=1136261

XRange said:
Think what you seek lies here in Puddling thread..
http://forum.xda-developers.com/showthread.php?t=1136261
Click to expand...
Click to collapse
adding to this: the automatic unlocker should work for you too. I had to re-unlock my phone after Motorola upgraded it when it was out for repairs. Worked like a charm.
(IF you're on AT&T)

ghost_og said:
adding to this: the automatic unlocker should work for you too. I had to re-unlock my phone after Motorola upgraded it when it was out for repairs. Worked like a charm.
(IF you're on AT&T)
Click to expand...
Click to collapse
Thank you soo much! I had to "re-unlock" bootloader! Now i have my custom recovery! One more thing have you or any other reader out there figured out a solution to my camera problem?
Sent from my MB860 using XDA

Try one custom roms see if that fixes camera, if not you might have carry phone for bad camera...

Am I Bricked forever? Weird Error

http://gyazo.com/c7b4bbfdb69ba1de32e472063a362e96
I am unable to boot into anything buy AP FASTBOOT and it is failed

Use rsdlite 6.1.4 and try again
Try this XML http://db.tt/XKakqGhK

tadgerloks said:
Use rsdlite 6.1.4 and try again
Try this XML http://db.tt/XKakqGhK
Click to expand...
Click to collapse
Follow up, Where would one goto get the latest version of RSDlite?

It was a problem with the phone I messed with the image a bit and went in fine
Sent from my XT907 using xda app-developers app

straylight said:
Follow up, Where would one goto get the latest version of RSDlite?
Click to expand...
Click to collapse
Just Google rsdlite 6.1.4 or if needed I can upload it and share the link

Here you go. This has everything you need.
http://www.phonearena.com/news/How-...-M-back-to-stock-ICS-from-the-JB-leak_id35580

Moved To Q&A​
Do not post questions in the dev section!​

had same exact issue, and followed guide. However, it still only boots into fastboot with the reason: Sticky Bit factory_fastboot. tried doing the flash again a couple more times (each time successfully through rsdlite), but same result each time.
Any thoughts?
EDIT: Nevermind, found that I could still boot into the white text boot menu, and choose factory from there (this was after trying a factory wipe from the recovery menu, but still failed to boot). This FINALLY brought it back to life, and back to ICS