Rooting nexus-s stuck booting up? - Nexus S Q&A, Help & Troubleshooting

Hi all.
Had my nexus-s for a week now, formally came from a nexus-one but 1 is damaged and i lost the other.
Have been trying to root it and such today and now im stuck!
I was using this guide here on unlockr as it was easier to use and understand then the one here on xda and is maintained so the downloads work: http://theunlockr.com/2010/12/17/how-to-root-the-samsung-nexus-s/
I followed the guide,
'fastboot oem unlock' - Completed.
Clockwork Recovery - Flashed.
After flashing the Superuser zip, and rebooting the system its just stuck on where the colours all come together making the X....
Im stuck as to what to do, ive tried wiping everything on the phone etc but nothing does the same thing, i cant flash update.zip, nor flash a cyanogen rom...
Is it Bricked?
Kyle.

Meh, sorted it.

Related

[Q] Desire S boots into recovery mode automatically!!

hello, I have a problem with a desire s phone which keeps booting into recovery mode when i turn it on. here's my step by step of what I did that got me into this predicament.
the phone had a stock 1.48 asia rom 0.98.0002 bootloader locked, and unrooted. so first I ran revolutionary had no problems there, had a revolutionary logo on my bootloader afterwards and the bootloader version was now 6.98.0002 or something I forget. anyway the next thing i did was I downloaded the stock euro rom 2.10.401.9 and extracted the rom.zip then renamed it to PG88img.zip copied it to the memcard ran fastboot, then fastboot automatically installed the zip after installation restarted the phone, now the phone was stuck on the white htc screen, so I ran recovery press the power and vol up and did a factory reset, had no luck with it still stuck on htc screen, now after reading a lot of threads, downloaded the ENGpg88img bootloader flashed it using fastboot and it was successful, the revolutionary logo was gone and the bootloader was now 6.98.0000 ( PG880000) but now when I rebooted the phone it would go directly back to recovery!! So the next thing i did was ran the euro rom again from the memcard thru fastboot and it updated the bootloader to the newest version and had a "locked"on top of the screen, so i did a boot unlock using htcdev and now its unlocked, then downloaded the clockwork recovery for saga then flashed it using fastboot with no problems. so now when I turn on the phone it goes straight to clockwork recovery! So last thing I did which also failed was I downloaded a pre rooted stock rom euro 2.10, placed it on memcard installed the zip from clockwork recovery then wiped all the data, dalvik cached and all then rebooted. But it still went back to clockwork recovery now I'm stumped. Really need help on this one.
long story short, I can only use fastboot, and if I use clockwork mod recovery to mount system i can do some adb commands. i also tried putting it in fastboot and ran an official RUu but I always get error 150. any help would be greatly appreciated.
It seems that your chip is gone. I have the same problem (boot looping) and had to try reclamation by phone provider. Find thread with "boot looping", or "white screen". You will find some software for a searching of your chip. Finaly all depends on your mobile vendor
yeah i thought it was the chip, but after 3 days of tinkering with it and reading a lot of threads i finally got everything back to normal. thanks for replying though zdech
batmite said:
yeah i thought it was the chip, but after 3 days of tinkering with it and reading a lot of threads i finally got everything back to normal. thanks for replying though zdech
Click to expand...
Click to collapse
Could you tell us how you solved it?
batmite said:
yeah i thought it was the chip, but after 3 days of tinkering with it and reading a lot of threads i finally got everything back to normal. thanks for replying though zdech
Click to expand...
Click to collapse
Hi, I have the same problem with HTC Desire.
Could you tell how you solved this please?
I don't know if he did what he wrote, but a big mistake was the last step.
batmite said:
So last thing I did which also failed was I downloaded a pre rooted stock rom euro 2.10, placed it on memcard installed the zip from clockwork recovery then wiped all the data, dalvik cached and all then rebooted. But it still went back to clockwork recovery now I'm stumped. Really need help on this one.
Click to expand...
Click to collapse
he installed ROM and wiped afterwards. Of course it fails at booting ;-)
If you really are in the same situation like him, wiping first and install ROM afterwards should solve the problem ;-)
Sent by my fingers to your head.
eyahl said:
I don't know if he did what he wrote, but a big mistake was the last step.
he installed ROM and wiped afterwards. Of course it fails at booting ;-)
If you really are in the same situation like him, wiping first and install ROM afterwards should solve the problem ;-)
Click to expand...
Click to collapse
Have to disagree with you there, what he said was
installed ROM
wiped DATA
wiped CACHE
rebooted
The ROM ZIP would have been flashed into SYSTEM not DATA, so wipe shouldn't have caused a problem
question is did BOOT flash ok?

[Q] stuck in bootloop, recovery unaccecable, only fastboot

hey guys,
i flashed cm10 a few days ago, coming from viperone rom. today i decided to change back. i booted into recovery, wiped and flashed the viper.zip in recovery.
since then ive been in a boot loop. i can still access the bootloader and get fastboot to work. if i boot into recovery it will bootloop.
tryed flashing roms with
fastboot flash zip rom.zip ; with respective
fastboot flash boot boot.img
flashing the zip i get the error:
writing "zip"...
FAILED: (remote: not allowed)
tryed flashing new recovery, i get a notivifacation that flashing finished. but it will still bootloop if i go into recovery.
im kinda stuck, any suggestions, id be really thankful if someone could help me out?
Hi, are you sure your bootloader is unlocked?
Remote: Not Allowed usually means your bootloader is locked.
thx for the quick answer,
i unlocked my bootloader ages ago and have flashed many roms in the last few months. additionaly wenn i get into the bootloader at the top of the screen it sais :
***UNLOCKED***
so im pretty sure i used the htc dev unlock
there is no prob when i flash new recoveries. ive tryed clockworkmod, clockworkmodtouch and twrp. all have worked on this phone.
in bootloader when i tell it to boot into recovery. i see the recovery screen for a split second. then it reboots
Lumbricus said:
thx for the quick answer,
i unlocked my bootloader ages ago and have flashed many roms in the last few months. additionaly wenn i get into the bootloader at the top of the screen it sais :
***UNLOCKED***
so im pretty sure i used the htc dev unlock
there is no prob when i flash new recoveries. ive tryed clockworkmod, clockworkmodtouch and twrp. all have worked on this phone.
in bootloader when i tell it to boot into recovery. i see the recovery screen for a split second. then it reboots
Click to expand...
Click to collapse
It might sound dumb but try to flash the recovery 2 or 3 times back to back before you try to get into it.
The time that happened to me was when I didn't fast boot flash the boot.img. That did nothing for you?
Sent from my HTC One S using xda app-developers app
Lumbricus said:
hey guys,
i flashed cm10 a few days ago, coming from viperone rom. today i decided to change back. i booted into recovery, wiped and flashed the viper.zip in recovery.
since then ive been in a boot loop. i can still access the bootloader and get fastboot to work. if i boot into recovery it will bootloop.
tryed flashing roms with
fastboot flash zip rom.zip ; with respective
fastboot flash boot boot.img
flashing the zip i get the error:
writing "zip"...
FAILED: (remote: not allowed)
tryed flashing new recovery, i get a notivifacation that flashing finished. but it will still bootloop if i go into recovery.
im kinda stuck, any suggestions, id be really thankful if someone could help me out?
Click to expand...
Click to collapse
You sound like what happened to me last night... was stuck in bootloop after flashing rom.. I thought.. no biggy reflash rom but couldn't mount sdcard.. so I had to do relock bootloader.. RUU install and then root/unlock bootloader procedure again.. Only way I got mine to work..
thx guys,
flashing boot.img didnt help. already tried.
will lock phone and try cruzers method in the morning. no sense doing this after being out for some beers
This happened to me last Monday. I used flashboot to wipe the cache after reflashing the twrp, I don't remember the command at the moment though. I also made sure to disconnect my USB when I restarted the phone.
Thx guys, i got it to boot!
Erasing cach got me back into recovery but couldnt not push rom or flash zip
Relocked, flashed ruu, and unlocked Again and its good as new.
<3 U guys Thx for the hel

[Q] Stuck on bootanimation. HELP

Tried looking everywhere, but couldn't really find anything. Any help is appreciated!
Alright some background info
I rooted my phone and unlocked the bootloader successfully. I wanted to do more, so I flashed TWRP onto my phone using JRummy's ROM Installer. I followed all the steps and successfully booted into TWRP recovery. I created a Nandroid backup and when I tried rebooting my phone it gets stuck on the 4G LTE boot animation.
I then tried wiping the cache etc. and restoring the backup I had just created. To no avail, the phone kept getting stuck on the boot animation. I've tried restoring the backup multiple times with no success.
On my last attempt I checked another box on the TWRP restore page, I think it was the VG5 verification or something. Halfway through what I though was going to be a successful restore, my phone reset and got stuck in the boot animation again. Now when I boot into recovery it's the stock recovery, not the custom TWRP as before. Tried clearing everything/factory reset and it still stuck on boot animation.
As a college student I'd like to get this figured out as soon as possible (hopefully before midweek, Friday at latest). If I can figure this out with your help I'll be very grateful.
If I can't find any other way, I'm willing to flash stock back using ODIN and seeing how that turns out. Also my home button is a little sticky so I doubt the Verizon worker would be able to boot into recovery or download mode.
Any suggestions?
For those of you TL;DR
1) Rooted phone / unlocked bootloader
2) Flashed custom TWRP recovery onto phone
3) Created a Nandroid backup from recovery
4) Tried rebooting and gets stuck on 4G LTE boot animation screen
5)Wiped cache etc. and retried multiple times. Doesn't work
EDIT: I flashed stock through ODIN and everything seems to be in order. I'll be trying to root and recover everything through TWRP again and if it doesn't work oh well. My end goal is to have a custom ROM
Maybe this will help you
Okay for your problem, if you can go to Download Mode and your recovery back to its stock form, your last option will be flashing it through Odin. There are several method and guides How to Flash via Odin. I will link to you all the guide and try it so your phone will be back to normal. Choose only 1 method
1.) [HOW-TO] Unbrick your soft bricked Galaxy S III (+ bootloader brick)
2.) Verizon Offcial VRBMB1 Odin Files, VRBMF1 Odin Files, and VRBMF1 Update Files
Must read first the guide and download all the necessary.
If your phone gets revived, you can try this method and choose TWRP recovery and update the recovery.
Click Here If Your Ready To Root/Unlock Bootloader/Flash Recovery
Note: You know the responsibility when you root your phone, I am not nor them who created this thread have responsibility to your phone, it is your choice.
Thanks for replying
I've got everything back in order now. I'll try installing AOKP or something
Your Welcome
That's good to hear

HELP!! Mate 9 Stuck in ERROR MODE After Reset.

Hello all, this is my first post so I apologize if anything isn't right.
I recently flashed my Mate 9 to stock Nougat B19x through a method I found on this site and then decided I wanted root. Bootloader was already unlocked so I flashed TWRP and then tried to flash a couple different root methods that all failed... So I factory reset through TWRP and tried again but they still failed so on the initial boot everything worked except the screen was blank except for the soft keys. I rebooted and the same again so I put it in fastboot and tried to re-install Nougat through the same method that worked before. It went through the whole process seemingly fine and finished with 'Update should start automatically' but then the phone boot into error mode. I've looked through everything I can find here and done everything I can think of myself but nothing has worked. I can boot into to fasboot but nothing else, not even after flashing any recoveries or stock images extracted from UPDATE.app.
Func no is 14 and error no is 1.
It's a MHA-L09 and I really need to fix it as I can't really afford anything else right now. Any help would be really appreciated and I'm happy to add more info if I've missed anything.
Thanks guys!!!
BUMP
Sorry if it's not very concise, just really need help!
What commands are you using to flash the stock files?
CandyFoxJ said:
What commands are you using to flash the stock files?
Click to expand...
Click to collapse
Standard fastboot flash recovery/system/boot
Not sure if I'm flashing all the right files or if huawei needs different commands.
Follow this guide.
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Thanks for your help. That's the one that I used in the first place but everytime I try again, TWRP either doesn't flash even though it says success or I can't get into recovery.
Everytime I try to access recovery using the hardware keys it boots to error mode so is there another way??
I've been looking into this some more and have found it could be a motherboard issue. Is this correct? And if so how much would that kind of repair cost and would it even be possible considering I've unlocked the bootloader?
Thanks again.

I had an error in rooting my Moto G4 Plus, and I fear I might've ruined the phone?

When I decided to root my phone, I looked up the exact procedure and followed it step by step. I unlocked my bootloader and even got the confirmation email from Motorola, and I did this, using the general fastboot procedure. I then flashed a custom recovery, by flashing a twrp.jpg file successfully, and after every step, I rebooted my phone. After that, I closed the guide and installed magisk manager on my phone. I didn't start the phone, and instead opened it in recovery mode, and it opened up showing Flash recovery Twrp, by tywinlannister7. I then installed the official pixel ROM I had downloaded, and that also got done perfectly. But after tht when I booted my phone, nothing happened an d the screen was blank.
This is where I started panicking and installed the rom multiple times, and advance cleared my entire phone. But now, all I have is a black box, that opens in recovery mode perfectly, and can install ROMs, but doesn't start.
Please Help.
belladonnatook said:
When I decided to root my phone, I looked up the exact procedure and followed it step by step. I unlocked my bootloader and even got the confirmation email from Motorola, and I did this, using the general fastboot procedure. I then flashed a custom recovery, by flashing a twrp.jpg file successfully, and after every step, I rebooted my phone. After that, I closed the guide and installed magisk manager on my phone. I didn't start the phone, and instead opened it in recovery mode, and it opened up showing Flash recovery Twrp, by tywinlannister7. I then installed the official pixel ROM I had downloaded, and that also got done perfectly. But after tht when I booted my phone, nothing happened an d the screen was blank.
This is where I started panicking and installed the rom multiple times, and advance cleared my entire phone. But now, all I have is a black box, that opens in recovery mode perfectly, and can install ROMs, but doesn't start.
Please Help.
Click to expand...
Click to collapse
Did you make a stock image backup before flashing custom ROM? If yes, did you try to flash it?
Sent from my HTC 10 using Tapatalk
It's cool. I didn't do that, but I fixed it now. Turned out it was a hard brick. I used this another thread on XDA as a guide. I'm using nitrogenos rom now, and it's working fine.
Thanks, though.

Categories

Resources