my Nexus S just died on its own! - Nexus S General

it was a rutine day as usual, running the GPS with CoPilot and playing music stream via BT to the car
and all of the sudden BAMN! the scary grey Google screen with the unlocked lock shows up
I was like *** BEEP ***, in my head i though oh, it might just be that reboot bug that is plaguing everybody but me, and now it's finally catching up
but noooooo... after i got to work i tried to reboot the phone (pulling battery out), nada, nothing, zero, zip... still the same dead google screen
then the worse case scenarios flashes through me head (knowing samsung past issues ) so i'm blazing for the worse...
currently i confirmed it can go into CW recovery screen and also go into the Odin Download Mode screen
so i'll try a nandroid backup first
if that is a no go, Odin is next...

Good luck, man. I feel your pain.
Hope you don't have to resort to odin, but if you do, that safety net will have proved its utility.
Again good luck!
Sent from my Nexus S using XDA Premium App

I can almost guarantee that ODIN will work. I resurrected a Fascinate that was locked out from itself using ODIN as well as a Captivate that had this same problem you are describing. ODIN dont **** around.

AllGamer said:
it was a rutine day as usual, running the GPS with CoPilot and playing music stream via BT to the car
and all of the sudden BAMN! the scary grey Google screen with the unlocked lock shows up
I was like *** BEEP ***, in my head i though oh, it might just be that reboot bug that is plaguing everybody but me, and now it's finally catching up
but noooooo... after i got to work i tried to reboot the phone (pulling battery out), nada, nothing, zero, zip... still the same dead google screen
then the worse case scenarios flashes through me head (knowing samsung past issues ) so i'm blazing for the worse...
currently i confirmed it can go into CW recovery screen and also go into the Odin Download Mode screen
so i'll try a nandroid backup first
if that is a no go, Odin is next...
Click to expand...
Click to collapse
hey what is your "flashing" history? (i.e. roms, kernels, etc.)

serialtoon said:
I can almost guarantee that ODIN will work. I resurrected a Fascinate that was locked out from itself using ODIN as well as a Captivate that had this same problem you are describing. ODIN dont **** around.
Click to expand...
Click to collapse
Well, that's if Odin is used right, otherwise it can ruin the phone. I've used it to bring back my Vibrant a bunch. It's good knowing that these Galaxy S phones are nearly brick proof.

All is not lost, honest...
AllGamer said:
it was a rutine day as usual, running the GPS with CoPilot and playing music stream via BT to the car
and all of the sudden BAMN! the scary grey Google screen with the unlocked lock shows up
I was like *** BEEP ***, in my head i though oh, it might just be that reboot bug that is plaguing everybody but me, and now it's finally catching up
but noooooo... after i got to work i tried to reboot the phone (pulling battery out), nada, nothing, zero, zip... still the same dead google screen
then the worse case scenarios flashes through me head (knowing samsung past issues ) so i'm blazing for the worse...
currently i confirmed it can go into CW recovery screen and also go into the Odin Download Mode screen
so i'll try a nandroid backup first
if that is a no go, Odin is next...
Click to expand...
Click to collapse
Hi AllGamer.
I had a similar disaster with the black google screen, and I had the unlocked bootloader as well, first I relocked bootloader, then used odin to reflash (http://forum.xda-developers.com/showthread.php?t=947950 ) then used the e0b546c442bf.signed-soju-GRI40-from-GRH78.e0b546c4 update (http://android.clients.google.com/p...2bf.signed-soju-GRI40-from-GRH78.e0b546c4.zip) renamed it to update.zip, put it on root of memory, and ran it via the built in recovery mode after..phew.
Odin saved my life to!!
Good luck...

i guess i should have updated the post before heading out to lunch
not too long after i posted the original message, i was able to reflash any ROM, and got it to boot back to normal.
it was weird for some odd reason the ROM just got corrupted? i don't see how's that possible
I was on Bionix 1.3 beta for the longest time, and i've been on Bionix pretty much ever since December 2010/Jan 2011
I'm now back to Stock 2.3.3, but i replaced the stock recovery with CW recovery
I simply booted into the CW recovery mode, and then loaded a new ROM from zip

Yipee
AllGamer said:
i guess i should have updated the post before heading out to lunch
not too long after i posted the original message, i was able to reflash any ROM, and got it to boot back to normal.
it was weird for some odd reason the ROM just got corrupted? i don't see how's that possible
I was on Bionix 1.3 beta for the longest time, and i've been on Bionix pretty much ever since December 2010/Jan 2011
I'm now back to Stock 2.3.3, but i replaced the stock recovery with CW recovery
I simply booted into the CW recovery mode, and then loaded a new ROM from zip
Click to expand...
Click to collapse
Glad your sorted....

Related

Stuck After Boot

Hey guys i know "Help!" threads get annoying (at least in the Fascinate forum they do.) but i could really use some help.
Rooted my friends phone today (root,clockwork,rom manager), and was going to install regular JAC kernal /voodoo w/o color fix.. I made sure the phone had the smaller NAND chip. Installation went fine (phone booted, voice told me it was switching to ext. 4.) and the voice said voodoo was complete. The phone was stuck at the S logo for about an hour and it was then i decided voodoo was botched. From there i rebooted to clockwork and went to restore the nandroid i made when i rooted. The nandroid got stock at one of the Data files for about 30 minutes. (i have a feeling this is around where i messed things up myself) Decided screw it and was going to flash JI6(T959UVJI6) and the stock kernal with ODIN. Now the phone boots past the S logo but the screen stays black and only the backlight menu buttons light up. It wont go past there. Any quick help is appreciated.
You didn't disable the lagfix I'm assuming.
Odin Eugene's Froyo that doesn't brick, then Odin JFD, install ROM of you're choosing.
Did you even try to search for a fix before posting???
~SB
problem0atique said:
Hey guys i know "Help!" threads get annoying (at least in the Fascinate forum they do.) but i could really use some help.
Rooted my friends phone today (root,clockwork,rom manager), and was going to install regular JAC kernal /voodoo w/o color fix.. I made sure the phone had the smaller NAND chip. Installation went fine (phone booted, voice told me it was switching to ext. 4.) and the voice said voodoo was complete. The phone was stuck at the S logo for about an hour and it was then i decided voodoo was botched. From there i rebooted to clockwork and went to restore the nandroid i made when i rooted. The nandroid got stock at one of the Data files for about 30 minutes. (i have a feeling this is around where i messed things up myself) Decided screw it and was going to flash JI6(T959UVJI6) and the stock kernal with ODIN. Now the phone boots past the S logo but the screen stays black and only the backlight menu buttons light up. It wont go past there. Any quick help is appreciated.
Click to expand...
Click to collapse
If you can still boot into clockwork recov. you can save it by pushing the undo voodoo zip file that was mentioned about. Assuming that u have adb access. If not odin froyo that doesnt brick tepartition checked. Turn off. Boot back in download. Odin stock jdf. Ji6 isnt a standalone rom. Its more like a no wipe update. Lucky his vibrant wasnt hardware locked lol. He will have a 90% chance of losing EVERYTHING
Had to odin flash froyo that doesnt brick then jfd and yep he lost all his data but he didnt have much to begin with. Now happily running Fusion. Thanks for the help guys!

Endless Rebooting, about to smash phone to bits

Alright, this issue has seriously driven me insane over the last few days, and today it's gotten to the point where I'm going to do something I'll regret if somebody can't help me out. As you can tell, I'm pretty desperate.
Using Fresh 3.5.0.1, I've encountered more reboots than I can count. Whether it's checking an email or playing Asphalt, the phone frequently decides it doesn't want to cooperate and restarts itself. I decided to try to get rid of the reboots for good today with a complete wipe and new rom.
First, I made a nandroid backup, followed by a data/system wipe and cache/dalvik cache wipe. Afterward, I flashed the ZenDroid 1.1.0 kernel in case that was the issue. I then proceeded to flash CyanogenMod 7 RC1 with gapps.
That worked for all of three minutes, and then it got even worse. The phone started restarted itself when I wasn't even doing anything, up to the point where it would restart on the CM7 boot animation. I took my rage out on a nearby pillow and decided to try something else.
I downloaded the final release MIUI rom and used Calkulin's format all to wipe my phone as instructed. This time around I flashed Savage-Kernel 1.6 along with MIUI. Lo and behold, after rebooting I was finally able to swipe through the home screens again.
And then I wasn't. It started rebooting on the boot animation again. At the moment it's even worse, rebooting three seconds into the damned splash screen. I've tried keeping the battery pulled for half an hour with the HTC battery and two after market batteries. I wiped the ext partition on the micro sd card. I even physically removed the card itself. This effing phone is still rebooting on the splash screen.
I'm at the end of my wits. All I want is for my Evo to WORK, without any constant reboots or force closes that make it utterly unusable outside. If anyone could help me out with this issue, I'd be extraordinarily grateful.
Mecha2142 said:
Alright, this issue has seriously driven me insane over the last few days, and today it's gotten to the point where I'm going to do something I'll regret if somebody can't help me out. As you can tell, I'm pretty desperate.
Using Fresh 3.5.0.1, I've encountered more reboots than I can count. Whether it's checking an email or playing Asphalt, the phone frequently decides it doesn't want to cooperate and restarts itself. I decided to try to get rid of the reboots for good today with a complete wipe and new rom.
First, I made a nandroid backup, followed by a data/system wipe and cache/dalvik cache wipe. Afterward, I flashed the ZenDroid 1.1.0 kernel in case that was the issue. I then proceeded to flash CyanogenMod 7 RC1 with gapps.
That worked for all of three minutes, and then it got even worse. The phone started restarted itself when I wasn't even doing anything, up to the point where it would restart on the CM7 boot animation. I took my rage out on a nearby pillow and decided to try something else.
I downloaded the final release MIUI rom and used Calkulin's format all to wipe my phone as instructed. This time around I flashed Savage-Kernel 1.6 along with MIUI. Lo and behold, after rebooting I was finally able to swipe through the home screens again.
And then I wasn't. It started rebooting on the boot animation again. At the moment it's even worse, rebooting three seconds into the damned splash screen. I've tried keeping the battery pulled for half an hour with the HTC battery and two after market batteries. I wiped the ext partition on the micro sd card. I even physically removed the card itself. This effing phone is still rebooting on the splash screen.
I'm at the end of my wits. All I want is for my Evo to WORK, without any constant reboots or force closes that make it utterly unusable outside. If anyone could help me out with this issue, I'd be extraordinarily grateful.
Click to expand...
Click to collapse
hmm...
i don't know what kernel fresh comes with, but both of the other kernels are more aggressive ones, and i would guess your phone doesn't like them. i would try this:
Wipe twice using calk, wipe again using recovery, flash mikfroyo or stock rooted (stock kernel). If you still get reboots... unroot and take your phone back in because its a hardware problem.
I had this problem. Drove me insane. Ultimately just unrooted and got a new one from sprint. Not one reboot since I got the new one.
Sent from my PC36100 using XDA App
Well I'm still super new to the whole flashing of the ROM's. But from what you have explained the only thing I can think of is that you missed a step when you rooted your phone. Because of this that is why your phone keeps brick. You should go and check out HTC EVO Hacks (go Google it) and the guy who runs the site made a sweet video & write-up on how to root your phone. Just re-do everything and follow directions, then when your done just flash Kings Unleashed. And when you check out the HTC EVO hacks root page look for the link to the XDA root forum which has more info on how to root your HTC the proper way.
Sent from my PC36100 using XDA App
aimbdd said:
hmm...
Wipe twice using calk, wipe again using recovery, flash mikfroyo or stock rooted (stock kernel). If you still get reboots... unroot and take your phone back in because its a hardware problem.
Click to expand...
Click to collapse
Yeah, I guess I should try the stock rooted rom. If I'm only able to use that instead of any other custom rom, though, I'm going to lose it. There's something inherently frustrating about a device refusing to work for no apparent reason.
chickut123 said:
I had this problem. Drove me insane. Ultimately just unrooted and got a new one from sprint. Not one reboot since I got the new one.
Click to expand...
Click to collapse
I'm sort of hoping I won't have to do that, considering I'll likely get a refurbished unit.
Fredrow425 said:
But from what you have explained the only thing I can think of is that you missed a step when you rooted your phone. Because of this that is why your phone keeps brick. You should go and check out HTC EVO Hacks (go Google it) and the guy who runs the site made a sweet video & write-up on how to root your phone. Just re-do everything and follow directions, then when your done just flash Kings Unleashed. And when you check out the HTC EVO hacks root page look for the link to the XDA root forum which has more info on how to root your HTC the proper way.
Click to expand...
Click to collapse
I'm pretty sure that isn't the case at all. If there was an issue with the way I rooted my phone, it would have been present eight months ago when I bought it. This rebooting issue is relatively new, and it isn't bricked. I appreciate the advice, though.
It could be just a defective phone - memory isn't immortal or impervious to defects.
I'd downgrade to a Sprint ROM, and keep it stock and see how that works. You have to rule out bad hardware first, and that's the only way to do it.
I agree on all of your guys suggestions but one thing i noticed was that he said he wiped data then dalvic cache then he said he flashed the kernel then the rom. Maybe he should try and rewipe everything with calk format all then flash the rom and reboot. Then go back into recovery and flash your new kernel then reboot again and see whats up from there.
Have you tried repartitioning your SD card and formatting? I was getting random reboots on every single rom I tried, and every single kernel. Turns out my partitions somehow got messed up on my SD card and that was causing it randomly. Now I have no reboots.
akrod2as said:
Have you tried repartitioning your SD card and formatting? I was getting random reboots on every single rom I tried, and every single kernel. Turns out my partitions somehow got messed up on my SD card and that was causing it randomly. Now I have no reboots.
Click to expand...
Click to collapse
Yes, I first formatted the sd card in Windows and then partitioning it on the phone's recovery. Still no luck.
Yeah... Sprint rom or if you go through with the unrooting process (I forgot how...) then you can figure out if it is hardware.
But yeah, endless reboots are frustrating.
If Sprint rom is giving you troubles, then just return it and get a new one. It's gotta be hardware then.
Also you could try running stock rooted without any downloaded market apps. Just run what came with the phone.
You can also try stock rooted eclair 2.1
Mine started the reboot bs after the december update. Mine seems to reboot when I use it heavily even though I'm not overclocked (heats up). Before the 2.2 update, it was very fussy being outside during the summer. I would like to exchange mine for another, even though I don't use it anymore. It would be nice to have a fully functioning backup. My gf's daughter wants the evo very much. Even if I would do that, which I wouldn't, I wouldn't let someone use a possibly unstable phone. If an emergency happened, and the phone started it's rebooting bs, it would be very bad to not be able to use the phone when you need it the most.
I am guessing I would have to reactivate the evo, run it for a month or so, unroot and lock it, then take it to a service center and see if I can make it start rebooting like crazy. Maybe I will get lucky and they would give me another one. I don't care too much if it is a refurb as long as it is in good shape and works good.
Try removing the SD card and booting.
Sent from my PC36100 using XDA App
rebooting
I had this same problem with my evo. Sometimes it would be ok, but then others it wouldnt stop doing it, didnt matter what I did. It could be sitting by itself and I would hear it rebooting. Drove me mad!!!
My first evo was awesome, it was a hardware ver 3. My camera lens cracked and the gave me a refurb, hardware version 2. This is when my reboots started happening.
After 3 batteries from Sprint and two more refurbs I finally blew in front of a store full of customers telling them that either give me a NEW evo, hardware version 3 like I originally had with no problems or it was going against their wall.
I havent had one problem since.
I wasnt rooted yet so cant comment along those lines but if you take it back to stock and it still does it I recommend throwing it at one of Sprints walls. No need to do any drywall patching at your place LOL.
I hope you get it resolved as I can feel your pain!
It may not be hardware. Did you restore any apps using any back up app (Titanium Backup) after flashing the AOSP roms? If so, make sure you did NOT restore any system apps or data. This is especially important when you go from Sense to AOSP.
The test is what everyone is suggesting. Flash back to Sprint rom and see what happens.
Also, you need to flash the kernel after flashing the rom, otherwise you'll just get the kernel packaged with the rom. I usually reboot and art least try the default kernel unless I know that my phone hates it.
bigmoogle said:
It may not be hardware. Did you restore any apps using any back up app (Titanium Backup) after flashing the AOSP roms? If so, make sure you did NOT restore any system apps or data. This is especially important when you go from Sense to AOSP.
The test is what everyone is suggesting. Flash back to Sprint rom and see what happens.
Also, you need to flash the kernel after flashing the rom, otherwise you'll just get the kernel packaged with the rom. I usually reboot and art least try the default kernel unless I know that my phone hates it.
Click to expand...
Click to collapse
No, I haven't even been able to get to the stage of installing any apps before the rebooting cycle starts again. I tried installing the stock Sprint rom this morning with the stock radios and kernel and it was stable for about five minutes. It's back to rebooting again, though.
Do you guys think it's time to unroot and go to the Sprint store for an exchange?
Mecha2142 said:
No, I haven't even been able to get to the stage of installing any apps before the rebooting cycle starts again. I tried installing the stock Sprint rom this morning with the stock radios and kernel and it was stable for about five minutes. It's back to rebooting again, though.
Do you guys think it's time to unroot and go to the Sprint store for an exchange?
Click to expand...
Click to collapse
If it was me, I would take it back. I just downloaded the newest ruu and will flash it later tonight. The only thing I'm worrying about is they won't be able to reproduce the problem. I really have to be multitasking a lot and pushing the phone hard. Actually the last time it had rebooting fits was with wireless tether running. The back of the phone was warm. I put it in front of the ac vent in the car for a minute or two and that seemed to help it stop rebooting.
herbthehammer said:
If it was me, I would take it back. I just downloaded the newest ruu and will flash it later tonight. The only thing I'm worrying about is they won't be able to reproduce the problem. I really have to be multitasking a lot and pushing the phone hard. Actually the last time it had rebooting fits was with wireless tether running. The back of the phone was warm. I put it in front of the ac vent in the car for a minute or two and that seemed to help it stop rebooting.
Click to expand...
Click to collapse
Well, it looks like I'll be taking it to the store after all. I just finished unrooting my phone with the RUU, so it's as if I had never touched the software. Lo and behold, the damned thing still rebooted a minute into using the phone.
I guess that in some sick way, I can consider myself more 'fortunate' than you, seeing as how my phone doesn't even need to be used in order to begin rebooting. It's ridiculous that I have to part with my Evo because of this bs.
Mecha2142 said:
Well, it looks like I'll be taking it to the store after all. I just finished unrooting my phone with the RUU, so it's as if I had never touched the software. Lo and behold, the damned thing still rebooted a minute into using the phone.
I guess that in some sick way, I can consider myself more 'fortunate' than you, seeing as how my phone doesn't even need to be used in order to begin rebooting. It's ridiculous that I have to part with my Evo because of this bs.
Click to expand...
Click to collapse
Did you even try removing the sd card and booting the phone?
Same thing happend with my old evo it started after i install one of the first cm safe roms not nightlies not saying tyat was the cause, i tried evverything wiping unrooting botting without sd, ive been on android sice g1 and i tried everything nothing worked, ended up going to sprint and getting another refurnished it was prolly hardware issue maybe cpu overheating or something, anyways not sure why ppl are so scared of refurnished phones i believe they do a lot more tests on those phone than retail ones lol
akrod2as said:
Did you even try removing the sd card and booting the phone?
Click to expand...
Click to collapse
Yes. I've already said I tried booting the phone without the sd card several times now without success.

[GUIDE] Sprint sph p100 stock firmware RECEOVERY: last resort.

Ok i decided i post what i did to recovery my sprints tab from a bad kernel flash that i didn't install clock work recovery, I thought my tab was a lost cause which i even chatted with hsn were i bought mine at for a replacement which would've took up to 30days.. So awhile i wait for that i decided to try and get it working till i get the prepaid label lol
Matter what i did it kept getting stuck at the samsung screen and couldn't get into recovery but download mode work luckly. i tried all kernels listed and it still got stuck which at the time i thought my tab was bricked or semi brick.
What i did is keep searching for the stock firmware which was hard to find but i found this thread http://forum.xda-developers.com/showthread.php?p=9753941#post9753941
Heres a direct link http://www.multiupload.com/WDKOUJSM2G
Thanks to ZoinksS2k for the tab sprint no modem firmware
And downloaded the stock no modem firmware the modem one is listed too but it will kill your gps and 3g might not work so i just did the no modem one.
So i downloaded it and odin was package with it and i couldn't get it to detect my tab in download mode ony when the tab was off it detected it..
So i tried heimdall and at first i couldn't get it to flash the start button was grayed out because i was putting the tar file into pda/code so i open the tar file and found factory.rfs param.ifs and cache.rfs and dbdata.rfs so i loaded all thoes in the heimfall boxes and than loaded the stock zimage which is in the tar too.
And than i flashed and saw the samsung screen and it went right pass it and played the samsung splash screen so i knew i was getting somewhere so it got stuck on the next samsung screen again.. So i turn it off and hold home button and volume up button than i push the power button and hold all 3 buttons till i saw the samsung screen and i left go the power button and the stock recovery loaded right up
So i did the wipe data/factory reset and i also did the wipe cache data just in case but im sure just the factory reset would work, And i restarted the tab and it went pass all screens and it loaded android!!! And everything was working 3g wifi gps and everything else.
So hopefully this guide will help others as a last resort if you ony get the samsung screen and download mode ony,If you get the receovery than just do the factory wipe.
This is worth a try first than sending it back to samsung and having to wait too get your tab back It sure saved me from having to send it back too hsn or samsung.
If you want you can thank me if this help you for providing the info
Gordesky,
Any idea how to go back to stock firmware + stock modem and all that from using the voodoo kernel? I have CWM Recovery 3.0 working.
Because, after going into Voodoo CWM Recovery, using wipe data/factory reset still keeps the kernel that I installed on - which is what makes my camera screwy.
If you want to go back to fully stock then follow his instructions and flash the stock kernel from the Zephyr thread. I actually am in the same boat as the OP and followed his instructions and now I'm fully back to stock.
Yep just do what I said which the tar file also have the stock kernel too.
Right now im on the voodoo kernel which works perfect except that cdrom problem but camera works for me so im gonna still with.this kernel so far. It seems the new sprint update doesint work right with the voodoo kernel problaby why I dont have any problems because I didint install the sprint update.
So when you go back too stock and want too give the voodoo another try dont install the sprint update when it asks you too, And everything should work other than the sdcard cdrom problems, Which I can deal with till it gets fixed because I do love the speed of this voodoo kernel
And the sound
Thank you gordesky1 for posting your experience because I was going through the exact same thing and I was at a loss as to how to resolve it. Unfortunately I did install the update but I'm pretty sure if I flash the same files again that I will go back to the original rom if that's necessary. The big problem with that is that the exchange fix in the update was something i was waiting for =\ so I think i'm going to wait and see if some of these issues are fixed in the next update but I wonder if we have to get Boushh a Sprint tab though =\ every day I curse myself for not getting a t-mobile or at least a Verizon tab *sigh*
No problem
Ya tell me about it... Bad thing for me is the sprint was my ony option which i got it because hsn were i bought it from had a flex pay on this tab which they ony have the sprint tab, and at the time i couldint pay 400 or 600$ right out. And i also got a 3years warranty on top of it from them even if i break it or drop it anywere which i pretty much got for free because they made a mistake at first with some software
The other tabs have cheaper 3g too like 5gb for 15 too 30$ a month.. But so far sprint is treating me good and the 3g has been stable so far and pretty fast loading webpages and can usely watch a youtube video but dont want too use up my monthy usage lol i usely use up too 500 too 600mbs max out of 2g and i useit every day and even download apps with it when im not near a wifi spot and listen too pandora too so i was suprized i didint get close too the 2gb limit yet.
Hopefully this thread will help more and save them from having too send it back too samsung or were they got it from, i know how it feels not having this tab which i use everyday at work.
I knew not to flash the modem from the restore package posted but when I tried to restore I used the .pit and the .tar. Failed at modem. So, being dumb I flashed the modem file. ugh.
Now I know all you need to do is flash the .tar, nothing else, no pit.
Your Post Saved Me!!!!!
10 characters
Your welcome and glad it helped I figure it was worth posting sense it brought my tab back too life which i thought i would've had too sent it back and waited a month or so, And wanted others too get there tab back too life with out playing the wait game which i really hate .. lol
this worked! I was able to get rid of CWM, my tab is 100% stock again! thanks a bunch!
well, I tried installing the update from sprint and goes back to CMW and starts doing the freaking back up again!! What the heck!!! anyone can tell me how to get back to stock recovery!! this is driving me nuts!
jcaf77 said:
this worked! I was able to get rid of CWM, my tab is 100% stock again! thanks a bunch!
Click to expand...
Click to collapse
I flash the above .tar and .pit with Odin and I still can't get rid of CWM. I had CWM 3.0 working. Then I flashed a Kernel (Khasmek) with kernel flasher and the damn thing froze on the splash screen. So I odin and it doesn't do a full factory reset. CWM folder is still there. Does anbody know how to completely revert back to stock firmware?
I basically want to start over from scratch and never use Kernel flasher.
Any help will be greatly appreciated.
lphillips80 said:
I flash the above .tar and .pit with Odin and I still can't get rid of CWM. I had CWM 3.0 working. Then I flashed a Kernel (Khasmek) with kernel flasher and the damn thing froze on the splash screen. So I odin and it doesn't do a full factory reset. CWM folder is still there. Does anbody know how to completely revert back to stock firmware?
I basically want to start over from scratch and never use Kernel flasher.
Any help will be greatly appreciated.
Click to expand...
Click to collapse
Flash the zImage from the stock rom in the recovery slot using hiemdall and it will flash the stock recovery over cwm.
I performed that action and it works it does get rid of CWM but now I am still unable to install sprint updates they fail half way into it
jcaf77 said:
I performed that action and it works it does get rid of CWM but now I am still unable to install sprint updates they fail half way into it
Click to expand...
Click to collapse
I am having the exact same problem, really wish I had read your post before I attempted to get CWM on my sprint galaxy tab.
I believe the update failed for me due to mismatch baseband (EB28) and system build (DJ30), I am looking for a roto backup copy of system build EB28, if anyone have it, please help and upload!
Many thanks.
I flashed the zImage with heimdall and it still wont do a sprint system update and also I cannot do the cwm process again to format to ext4.
Sent from my SGH-T959V using XDA Premium App
lphillips80 said:
I flashed the zImage with heimdall and it still wont do a sprint system update and also I cannot do the cwm process again to format to ext4.
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
Check out the newly leaked EA24 flasher, it will update both system and baseband to EA24 and you will be able to update after that.
Thanks technote. I used the above and worked awesome!
Sent from my SPH-P100 using XDA Premium App
okay, im farily new to the galaxy tab forums, only reason im here is because my friend bricked his tab and figured i could take a stab at it, i mean im good at fixing my galaxy s so i figured, how hard can this be. Wrong, my head is killing me because i cant figure this out. His tab is stuck in a boot loop mean it goes to the "samsung" screen and then stays there forever. I tried using odin with the stock firmware with no modem, everything went good but when it attemped to restart still nothing ? can someone please school me on how to do this properly please. Im a pretty good listener if im given descent instructions lol please by all means HELP lol

Constant Reboots, Hanging and Annoying Me

Okay, so first off, I'm literally about to light this fking thing on fire.
This damn phone has been the death of me. I have a Tbolt and Galaxy Tab, and NEITHER have been as much of a pain in my ass.
This seems impossible because since I got the phone, I've had nothing but problems.
1. Unlocked bootloader via fastboot. K, done.
2. Flash AmonRa Recovery (I did this before AND after using CWM recovery, having custom rom, etc, it never worked) Always sat in a loop at the google X with unlock symbol, or just reboots into normal (and yes, the MD5s are correct) 3. I've had the phone get into the rom both with SIM and without, and randomly reboot, from using anything from market, to file explorer, to hitting the lock screen.
Honestly, I'm tempted to just sell it again (since I bought it off ebay) and buy something different, though that's a pain to do, and I need it for a trip to europe in a week, so I would love to have a phone I'm not pissed off at. And yea, already got mad enough I threw it.
I've literally spent HOURS looking through Google results on all the issues. And have YET to make this lil pos stable enough for me to use like I do my tbolt. nice 100 battery pulls. Seriously. Heeelllpp on this, :-/
hkbladelawhk said:
Okay, so first off, I'm literally about to light this fking thing on fire.
This damn phone has been the death of me. I have a Tbolt and Galaxy Tab, and NEITHER have been as much of a pain in my ass.
This seems impossible because since I got the phone, I've had nothing but problems.
1. Unlocked bootloader via fastboot. K, done.
2. Flash AmonRa Recovery (I did this before AND after using CWM recovery, having custom rom, etc, it never worked) Always sat in a loop at the google X with unlock symbol, or just reboots into normal (and yes, the MD5s are correct) 3. I've had the phone get into the rom both with SIM and without, and randomly reboot, from using anything from market, to file explorer, to hitting the lock screen.
Honestly, I'm tempted to just sell it again (since I bought it off ebay) and buy something different, though that's a pain to do, and I need it for a trip to europe in a week, so I would love to have a phone I'm not pissed off at. And yea, already got mad enough I threw it.
I've literally spent HOURS looking through Google results on all the issues. And have YET to make this lil pos stable enough for me to use like I do my tbolt. nice 100 battery pulls. Seriously. Heeelllpp on this, :-/
Click to expand...
Click to collapse
try
fastboot erase cache
fastboot erase userdata
fastboot erase system
and then flash via fastboot the AmonRa recovery again.
BTW, which ROM are you trying to flash? ICS or Gingerbread? And do you have Blackrose installed?
taodan said:
try
fastboot erase cache
fastboot erase userdata
fastboot erase system
and then flash via fastboot the AmonRa recovery again.
BTW, which ROM are you trying to flash? ICS or Gingerbread? And do you have Blackrose installed?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=872441 << Flashed this.
So far, I've knocked my network to 2g and it's been fine. though not really much of a fix. And I had cleared all of the above using CWM prior to the attempted flash. I'd rather not have to wipe everything again just to get AmonRa. I've wiped quite a few times. Though did get something about /sd-ext missing when erasing via CWM. Also, I tried erasing recovery, and got this: "erasing 'recovery'... FAILED (remote: not allowed)". Not sure if that matters. Just seems that flashing via Fastboot has failed everytime. I flashed CWM via fastboot and that failed too, I ended up getting it working via RomManager.
I had the same problem. After i dropped my phone on the floor everything worked fine
Sent from my GT-I9001 using Tapatalk
jojogangsta said:
I had the same problem. After i dropped my phone on the floor everything worked fine
Sent from my GT-I9001 using Tapatalk
Click to expand...
Click to collapse
Yea, though I still feel like I'm getting intermittent reboots. IT's not an everyday use phone, so I'll have to see how it fares when I'm overseas.
flash 4ext touch via 4ext recovery control app
Then install a different rom like miui or cm7 or hypersense nova
Sent from my Nexus One using XDA
joelshawdow said:
flash 4ext touch via 4ext recovery control app
Then install a different rom like miui or cm7 or hypersense nova
Sent from my Nexus One using XDA
Click to expand...
Click to collapse
Done and done. Still have a problem with boot looping. Google X with vibration, then goes black and does it again, and it loops like that indefinitely. Though this isn't new, been since I unlocked it....POS.
Deleted
Leave it in a freezer for a day no joke
Sent from My Samsung Galaxy S2 running Paranoidandroid Rom.What else if not?=P
First of all any ROM you find here for an update is going to have bugs. So have to prepared for reboots, and/or no boots.
On the other hand, you have to verify to see if you have any hardware issues. In order to do so, you have to flash to a stock ROM to see if the issue continues. If stock ROM is just fine, then its the custom ROM that is causing grief! So try another custom ROM, until the one that suits your needs.
my sugestion 2 u - use cm7.2. use 4ext touch recov, wipe all ur stuff, flash blackrose hboot with no repartitioning, flash cm7.2 rom, finally, stop b!tching!
ai6908 said:
First of all any ROM you find here for an update is going to have bugs. So have to prepared for reboots, and/or no boots.
On the other hand, you have to verify to see if you have any hardware issues. In order to do so, you have to flash to a stock ROM to see if the issue continues. If stock ROM is just fine, then its the custom ROM that is causing grief! So try another custom ROM, until the one that suits your needs.
Click to expand...
Click to collapse
Did it when it went back to stock. And Whoever said put it in the freezer, I did, and worked on it with AC on it, and it worked better . Though for some reason, never been able to flash recoveries via fastboot. Oh well. 4ext rocks.
hkbladelawhk said:
Did it when it went back to stock. And Whoever said put it in the freezer, I did, and worked on it with AC on it, and it worked better . Though for some reason, never been able to flash recoveries via fastboot. Oh well. 4ext rocks.
Click to expand...
Click to collapse
I never had any luck flashing recovery using fastboot either. Anyhow, it sounds like a motherboard issue to me. Sorry pal!
ai6908 said:
Anyhow, it sounds like a motherboard issue to me. Sorry pal!
Click to expand...
Click to collapse
This. The description fits overheating and overly sensitive to temperature CPU.
yon can flash another rom
yon can flash another rom
Still having bootup problems
Okay, sorry to bring this back up, but I am still having an issue with the phone booting. If I get the phone on, it's fine, doesn't randomly turn off or anything. However, if I try to reboot, power off and power back on for any reason....it becomes a pain to get back up and running. I usually have to do a couple battery pulls before it comes back up. Does the same thing. Hits the X, vibrates once like it's gonna turn on. Then a few seconds to a min later, goes black, then flashes the x and vibrates once again. It loops like this until I pull the battery and try again. Sometimes it takes a couple times to work. Its not the ROM either, because this is the issue I had when I first got the phone and did fastboot oem unlock. It would hang on stock. It's done it on all 3 ROMs I've tried. I don't wanna say fully it's a CPU issue, because I don't have issues once it's on.
Any new idears?
PS. I tried CM7, and I didn't like it. Not a fan of AOSP ironically enough.
The Nexus One will give off 7 Vibrations to indicate a hardware issue, we will just have to wait and see

How I almost made a brick

My 2 cents..
I was using ICSSGS from 1st RC. But it becomes very laggy after 3-4 weeks, so factory reset every month was necessary. I decided to change ROM.
I installed DOC's v12 ( I assume is is the same Doc that was cooking ROMs for my Omnia, and I was werry pleased with those ROMs). Did wipe, cleaned cache, cleaned Dalvik, formatted /system, flashed ROM, wipe again and it was working. But after two days it was still very laggy (talking about waiting for response for 3-5 seconds) so I wanted something faster. I had choose this Openkang milestone 6.
And then the fun begins.
Downloaded, copied to sd, booted to CWM, all wipes, flashed ROM, flashed gapps and went to bootloop. 3 button combo worked only for download mode, not for entering CWM. There was no way I could access CWM. I even could not enter Android boot (don't know exactly how it is called, but it saved my TF101 more than once.)
So after 1/2 hour of unsuccessful trying to get to CWM, phone just shows logo for icyglitch kernel and went to boot again, I have seen that only option to do anything was Odin. I downloaded Odin, downloaded some 2.3.6 ROM and downloaded CWM for that rom.
First I had to find driver for phone. I remembered phone on ICS wants nexus drivers so I installed those, booted phone to download mode and flashed 2.3.6 rom with Odin.
Phone booted, boot animation was on screen, but it did not boot to working Android. I didn't care too much, just booted to download mode again, flashed CWM and now I had at least access to my sd card. Did all wipes again, flashed DOC again and went to bootloop (Icyglitch kernel logo) again.
....
So I repeated Odin procedure, and when I had working CWM I flashed good old ICSSGS 4.02. This one worked.
I had spent 4 hours to solve this problem mostly because I was not full prepared to flash.
-I had no working USB driver on PC
-I did not had Odin
-I do not have ADB installed. Even if I had it, I don't know much how to use it.
-I did not have any working 2.3.6 ROM WITH bootloader
-Nandroid backup... hmmmm... what is that? Bah, don't need it...
Luckily I flashed my phone so many times I already roughly know what to do, but I still have experienced my share of "OMGOMGOMGOMG".
My advice to new and seasoned flashers:
Don't be cocky. After million of successful flashes once will go wrong. If nothing else Murphy will kick in. And when something goes wrong, be sure that all that you need to rescue phone is on your HDD and you know WHERE it is and how to use it. And read guides. And when you finish reading read them again, then go to sleep and flash next day.
Now I'm even more satisfied with myself because I do not flash other people's phones. If it happens that I create a 400€ brick, it will be at least mine.
If this helps anyone to restore phone, click Thanks button :good:
Thankyou for being man enough to share this, I hope all noobs read this and start getting the message!
slaphead20 said:
Thankyou for being man enough to share this, I hope all noobs read this and start getting the message!
Click to expand...
Click to collapse
Lol you were faster .
I had the same problem today trying to flash aokp m6...
Got bootloop and then Odin was hanging at various points when I tried going back to stock GB.
I thought I was goosed but the good old SGS came through in the end!
Sent from my GT-I9000 using xda premium
Flashing can be frightful. I'm sure every seasoned flasher here on XDA has had their fair share of OMG moments. I know I sure have.
Future advice: after you lost recovery, you didn't need to go back to GB. Stratosk (of Semaphore Kernel) has a .tar version of his ICS kernel that can be flashed with Odin, which will then restore your CWM. This would have been a faster, simpler fix for you. Keep that in mind for next time.
I would suggest you try SlimICS the next time you get sickend of (laggy) ROM. I for one, absolutely love SlimICS, and as all, it does have some drawbacks (no lag, though) when you're pimping it out too much.
upichie said:
Flashing can be frightful. I'm sure every seasoned flasher here on XDA has had their fair share of OMG moments. I know I sure have.
Future advice: after you lost recovery, you didn't need to go back to GB. Sratosk (of Semaphore Kernel) has a .tar version of his ICS kernel that can be flashed with Odin, which will then restore your CWM. This would have been a faster, simpler fix for you. Keep that in mind for next time.
Click to expand...
Click to collapse
Too bad I didn't know that. Somehow I was convinced that no ICS rom or kernel is flashable via Odin. But Later when everything worked and I finally had time to breathe I thought that I didn't need to go to GB. I think maybe only to flash any GB CWM with Odin would be enough. All I needed was working CWM, not entire rom.
Anyway, I'll try Slim now, let's hope I won't need to rescue phone again.
I bricked my phone twice yesterday, trying to install a CM9. It was my first attempt to modify a phone. Nice start.
bpp9 said:
I bricked my phone twice yesterday, trying to install a CM9. It was my first attempt to modify a phone. Nice start.
Click to expand...
Click to collapse
Happens to everyone! 2years in and I accidentally wiped my sd card yesterday! Was a long night! It's a fast learning curve but fun when you get the hang of it!
Always brick my phone in the past, nearly one time a day
Well some tips for flashing:
- On stock ROMs, try flashing all partition firmware (i.e. 3 files in Odin) with re-partition checked before finding for help.
- Always backup you data with apps like Titanium backup, I don't usually use nandroid because it is not so flexible.
- Get GB bootloader before going to CM based ROMs, and go back to froyo bootloader if you want to have froyo back (search EzBoot for this).
- CM based ROMs and stock ROMs use a different filesystem, so flash all partition firmware before going back from CM to stock.
- Same reason, you will mostly get bootloops when going to CM ROMs. In this case, just hold the 3-button combo to enter recovery and flash it again.
- Same reason again, don't use CWM2 recovery to flash CM.
In case that anyone don't know, CM means CyanogenMod.
Hope this helps!
Sent from my GT-I9000 using xda app-developers app
tt0204 said:
Always brick my phone in the past, nearly one time a day
Click to expand...
Click to collapse
Uauuu, and you still didn't have heart attack?
I'm not sure if the fact that I managed to rescue my phone is good. Now I still don't have reason to buy SGS II.
And yes, Slim is woking, you can see my new signature. :highfive:
Managed to flash properly before I did
Wait at least until we get a working jelly bean before getting a new phone!
Sent from my GT-I9000 using xda app-developers app
slaphead20 said:
Happens to everyone! 2years in and I accidentally wiped my sd card yesterday! Was a long night! It's a fast learning curve but fun when you get the hang of it!
Click to expand...
Click to collapse
Ahaha, I did the exact same thing the day before yesterday!
Using GT-I9000 my sent Tapatalk 2 from.
First time i flashed my phone was a heart in mouth moment when it boot looped for the first 2 or 3 times.
Swore I'd never flash my phone again. Over a year later and my phone has gone through countless changes and still going strong.
The only other issue I've had with customizing my phone is telling my flatmate about it. Problem being that he doesn't quite understand the concept of 'rooting' or 'flashing'. At least not in the geek sense of the words.
Yesterday,i was reverting to stock from ics you know...And rooted JW4 with cf.then i wanted to flash semaphore's 2.7.4.I am %100 sure that there was nothing wrong.Just semaphore over cf.Did that ten times!... so here it is;
when flashing process started odin gave fail WHILE flashing zImage.not after or before.Just at the middle of flashing zImage.
I dunno why maybe that one was a random error of odin who nows....
Anyway after it said fail,phone shutted down itself from download mode..First thing that i tried,entering to recovery.But phone was not responding.No boot logo or..just black screen.
I took a deep breath.Restarted my pc while it is restarting i put out the battery from phone wait for 30sec.
Then after pc started up ,i opened odin and put the files etc etc.
Then magical thing happened
I tried directly to the d.mode it worked and flashed JVQ then got JW4 from kies
This was my story...
GT-I9000 cihazımdan Tapatalk 2 ile gönderildi
dreamer94 said:
Yesterday,i was reverting to stock from ics you know...And rooted JW4 with cf.then i wanted to flash semaphore's 2.7.4.I am %100 sure that there was nothing wrong.Just semaphore over cf.Did that ten times!... so here it is;
when flashing process started odin gave fail WHILE flashing zImage.not after or before.Just at the middle of flashing zImage.
I dunno why maybe that one was a random error of odin who nows....
Anyway after it said fail,phone shutted down itself from download mode..First thing that i tried,entering to recovery.But phone was not responding.No boot logo or..just black screen.
I took a deep breath.Restarted my pc while it is restarting i put out the battery from phone wait for 30sec.
Then after pc started up ,i opened odin and put the files etc etc.
Then magical thing happened
I tried directly to the d.mode it worked and flashed JVQ then got JW4 from kies
This was my story...
GT-I9000 cihazımdan Tapatalk 2 ile gönderildi
Click to expand...
Click to collapse
Actually boot directly into download mode without rebooting computer/phone will work
i know but wanted to live with that action,adrenaline
GT-I9000 cihazımdan Tapatalk 2 ile gönderildi
I think we should start a membership here. Anyone who wants to join must expirience "OMG" factor for at least 20 min. I had it 4-5 times, if I count my hassling with Omnia too.
Isn't something interesting? I mean, look at us. We flash phones, sometimes we manage to make it useless, we spend hours for rescuing them, all that time we swear to god that we will never do that again, but 5 minutes after we manage to make our phones work we are ready for next flashing. Here in Slovenia we use to say that even donkey goes on ice only once, but looks like we newer learn...
My current favorite thread, it's refreshingly honest to see people laughing at themselves, and sharing their disasters, we all do it, in fact that's why we do it! Nice to see so much humility
About not bricking other people's phones....
Right now I'm in the process of bricking my boss's phone. He wants ICS on his Dell Streak 5, even if it is only pre-alpha ... Wish me luck.

Categories

Resources