I have the nexus s 4g flashed to boost mobile. it has ran great for over a year now. i have flashed many roms and kernals to it and it has worked like a charm with only the occational hickup. but a few weeks ago when i would power it down and change may battery it would start to get stuck on the google screen. i could pull the battery a few times and it would eventually take off and work fine for a few day and then do it again. this last time it done it i cant get it to go past the google screen for nothing. i can get into the fast boot mode and also into clockworkmod touch recovery but when i go into flash zip from sd it say error loading sd, when i plug it into my computer it conects when in fastboot but i cannot access my sd memory at all. i tried the pdanet but it wont work due to no access to the sd. i downloaded the program wugs nexus tool kit and tried to flash stock and unroot with option bootloop / soft-brick in my boot loader. the program seems like it is working, it takes control of my phone restarts bootloader a few times then says restarting your now stock phone, but my phone just sits in bootloader. i have tried to manually reboot system and it just goes to the google screen and stops. when i power on my phone the google logo comes up, flashes away for a split second then pops back up with the leds at the bottom of my phone on this time but thats all i can get. please help i dont know what to try next. let me know if any of you have had this problem before and what you did to get it fixed. Please help i miss my Nexus...
** UPDATE *** Well i havnt really given up on my Nexus but i gave in and bought a new Galaxy S II so i could have a working smart phone again. Ill still be working on the Nexus in my spare time so ill update if i have any luck.
Sent from my SPH-D710 Galaxy S II running Crossbones JB ROM with matrix using xda app-developers app
Related
I was curious if anybody could help me. I have a g2x from Wind (p-999dw). I am pretty new to rooting and such but wanted to update my phone. I got it rooted successfully and then tried installing the CM7 Rom update. Backed up with cwm first and then continued. Now my phone is pretty f'd. Every time i try to turn it on it just hangs on the LG screen. I tried the flash recovery method with nv flash and was able to get a cwm recovery menu up but when i try loading the previous working setup, it says successful, i restart the phone and now i get the LG logo with the blue status bar below (which wasn't there before I used the flashing tool) it which moves for a few seconds, then freezes. I've tried every option in the menu and i still cant get past the LG logo screen. Can anybody help me? I've spent hours trying and can't seem find a way to fix it. Don't care if i lose all my data and apps just want my phone to work. Any help would be much appreciated. Thanks.
I believe you need to remove the battery then try to boot into recovery (hold volume down and power)
Sent from my G2X
Need to pull battery let sit for a couple seconds reinsert battery. Hold volume rocker down and power until you see the second LG screen should have some blue and purple surrounding the LG logo. After that select wipe data factory reset, then go to mounts and storage and select wipe cache/data/system. If you want do each one twice. Then you can go through the process to flash cm7, don't forget to flash gapps (google apps) as well. If you don't flash those you won't be able to sync your phone with Google and retrieve your contacts and such... hope this helps.
Sent from my LG-P999 using xda premium
If none of the above works, rom for recovery will definetly fix your problem. Check the development thread it's in there.
Sent from my LG-P999 using xda premium
Hello fellow XDA members! I am a Noob.
So I believe I have a Bricked Galaxy Note 10.1. Model GT-N8013
I Rooted Stock ROM, and flashed Collective Edition 5 Dark Side.
So heres what happened, everything seemed fine, until I made a mistake, I was Pimping my ROM with the PimpMyRom app. Every change seemed fine and my note worked, but when i saw the double boot screen slide in the app, i did what it said, i have the imf support or something like that. Then after i had the ''support'' needed, i clicked install button on the double boot slide, it seemed to do something and requested nothing, so i went ahead chose a second clip, and clicked set as second boot screen. It said it wont take effect until the 3rd boot, so i rebooted 3x, but at the third time, it was stuck at the boot screen with the galaxy note 10.1 logo ! It did not start or did anything, over time it would turn off and automatically reboot, but it would get stuck again !.
To attempt to fix it, I Booted into recovery (CWM) and did everything i could. I wiped nearly all cache, factory reseted, then out of fear, i flashed the stock firmware ROM from Sammobile website, with ODIN, and to my knowledge, it got worse!! It booted, seemed to do something then in the logo screen it got stuck once again!! Stock recovery says unable to mount /efs, i don't believe EFS is completely corrupted, I left it stuck for awhile and it shut down in like an hour. Help, what can i do to fix this!?!?!?!
Device cannot boot up.
I could boot into recovery and download mode only.
I thought that I too had bricked my 8013 the past weekend. Trying to do something that I shouldn't. It took me a bit of work and a lot of worry (my wife gave me my 8013 for Xmas and if I had to tell her that it was now a doorstop, she would have killed me). I used this method to get back to stock and then was able to work my way back to the ROM I use. I disremember in which order I Odin'd things, but in the end was able to un-brick. All I can say is give it a shot.
jusliloleme said:
I thought that I too had bricked my 8013 the past weekend. Trying to do something that I shouldn't. It took me a bit of work and a lot of worry (my wife gave me my 8013 for Xmas and if I had to tell her that it was now a doorstop, she would have killed me). I used this method to get back to stock and then was able to work my way back to the ROM I use. I disremember in which order I Odin'd things, but in the end was able to un-brick. All I can say is give it a shot.
Click to expand...
Click to collapse
i did what u said...but all i got is i able to get through the logo but without seeing anything only able to hear the sound. any other tip? i got the same problem as above.
Hi everyone!! New here, but not new to Forums in general. I searched around and couldn't find my exact issue, so I figured I’d start a new thread. This is gonna be kinda long, but I wanna give as many details as I can to keep things accurate.
My wife and I both have the Galaxy S2 T989 (T-Mobile). Both purchased like new off eBay. When I got hers a couple months ago, as soon as I got it I factory reset and wiped the caches, upgraded to JB via Kies, and then turned right around and rooted it via Odin using the instructions found on galaxys2root.com. Everything went flawless, took me less than a half an hour total for everything. I got mine a couple months later and did the exact same process as soon as I got it in the mail. However after rooting on Odin and getting the green pass just like hers, it got stuck in a boot loop when it rebooted. It would go as far as the "galaxy S2" splash screen, and sometimes past that to where the Android takes off, then reboot, or freeze. It then became unresponsive to any button pushes and I had to pull the battery to get it to shut off (The battery is a new OEM Samsung battery incidentally). I ultimately had to unroot, re-install ICS and re-upgrade back to JB via Kies again to get out of the loop. I did this whole process 3 times to make sure it wasn’t something I did. So I’m still running unrooted with JB on it now.
The only thing I noted that was kinda odd was that when I open Rom Manager in my current non rooted state, it shows that I already have CWM and TWRP installed on it. Even though when I go to recovery mode it's the standard OEM Samsung menu. I never installed TWRP, and CWM was only on it for a bit when I was in the boot loop. Could this be my issue? Are they both still somewhere on my phone interfering with each other and I can only see them via ROM manager?
Sorry for such a long first post, and thanks in advance!
addamT989 said:
Hi everyone!! New here, but not new to Forums in general. I searched around and couldn't find my exact issue, so I figured I’d start a new thread. This is gonna be kinda long, but I wanna give as many details as I can to keep things accurate.
My wife and I both have the Galaxy S2 T989 (T-Mobile). Both purchased like new off eBay. When I got hers a couple months ago, as soon as I got it I factory reset and wiped the caches, upgraded to JB via Kies, and then turned right around and rooted it via Odin using the instructions found on galaxys2root.com. Everything went flawless, took me less than a half an hour total for everything. I got mine a couple months later and did the exact same process as soon as I got it in the mail. However after rooting on Odin and getting the green pass just like hers, it got stuck in a boot loop when it rebooted. It would go as far as the "galaxy S2" splash screen, and sometimes past that to where the Android takes off, then reboot, or freeze. It then became unresponsive to any button pushes and I had to pull the battery to get it to shut off (The battery is a new OEM Samsung battery incidentally). I ultimately had to unroot, re-install ICS and re-upgrade back to JB via Kies again to get out of the loop. I did this whole process 3 times to make sure it wasn’t something I did. So I’m still running unrooted with JB on it now.
The only thing I noted that was kinda odd was that when I open Rom Manager in my current non rooted state, it shows that I already have CWM and TWRP installed on it. Even though when I go to recovery mode it's the standard OEM Samsung menu. I never installed TWRP, and CWM was only on it for a bit when I was in the boot loop. Could this be my issue? Are they both still somewhere on my phone interfering with each other and I can only see them via ROM manager?
Sorry for such a long first post, and thanks in advance!
Click to expand...
Click to collapse
Try flash a stock firmware by using flashtool, it will work 100%:angel:
revernwe therefore
addamT989 said:
Hi everyone!! New here, but not new to Forums in general. I searched around and couldn't find my exact issue, so I figured I’d start a new thread. This is gonna be kinda long, but I wanna give as many details as I can to keep things accurate.
My wife and I both have the Galaxy S2 T989 (T-Mobile). Both purchased like new off eBay. When I got hers a couple months ago, as soon as I got it I factory reset and wiped the caches, upgraded to JB via Kies, and then turned right around and rooted it via Odin using the instructions found on galaxys2root.com. Everything went flawless, took me less than a half an hour total for everything. I got mine a couple months later and did the exact same process as soon as I got it in the mail. However after rooting on Odin and getting the green pass just like hers, it got stuck in a boot loop when it rebooted. It would go as far as the "galaxy S2" splash screen, and sometimes past that to where the Android takes off, then reboot, or freeze. It then became unresponsive to any button pushes and I had to pull the battery to get it to shut off (The battery is a new OEM Samsung battery incidentally). I ultimately had to unroot, re-install ICS and re-upgrade back to JB via Kies again to get out of the loop. I did this whole process 3 times to make sure it wasn’t something I did. So I’m still running unrooted with JB on it now.
The only thing I noted that was kinda odd was that when I open Rom Manager in my current non rooted state, it shows that I already have CWM and TWRP installed on it. Even though when I go to recovery mode it's the standard OEM Samsung menu. I never installed TWRP, and CWM was only on it for a bit when I was in the boot loop. Could this be my issue? Are they both still somewhere on my phone interfering with each other and I can only see them via ROM manager?
Sorry for such a long first post, and thanks in advance!
Click to expand...
Click to collapse
hi,
can 'be that your device has some residual old. Do as you have advised. install a stock rom and firmware, so it becomes a new cell phone. After odin starts TWRP (much better) and root.
I would flash a complete bone stock Rom using Odin and start over. Also rom manager was highly discouraged on the AT&T version of the s2 so I don't know what the stance is on T-Mobile's version
Sent from my CLEAN Note ll
brandonarev said:
I would flash a complete bone stock Rom using Odin and start over. Also rom manager was highly discouraged on the AT&T version of the s2 so I don't know what the stance is on T-Mobile's version
Sent from my CLEAN Note ll
Click to expand...
Click to collapse
Thanks for the advice! Should i flash it back to ICS then try to root again via Odin before i upgrade back to JB? I'm guessing there's something that isn't getting wiped. Since i can run CWM and Root with Odin without a hitch. it's the initial reboot after all that is done that I go into the boot loop.
tainiun rioters
pierm said:
hi,
can 'be that your device has some residual old. Do as you have advised. install a stock rom and firmware, so it becomes a new cell phone. After odin starts TWRP (much better) and root.
Click to expand...
Click to collapse
Sorry for my ignorrance, what exactly is TWRP, and is it now on there because i used Odin and it installed it automaticly? And do i want to use this vice CWM?
One more question...before i try all this, can i backup everything on Kies just like i would be able to with CWM and reinstall if my root fails again? I've only used Kies for firmware upgrade, never to reinstall a backed up copy of my phone.
Thanks!
addamT989 said:
Sorry for my ignorrance, what exactly is TWRP, and is it now on there because i used Odin and it installed it automaticly? And do i want to use this vice CWM?
Click to expand...
Click to collapse
addamT989 said:
One more question...before i try all this, can i backup everything on Kies just like i would be able to with CWM and reinstall if my root fails again? I've only used Kies for firmware upgrade, never to reinstall a backed up copy of my phone.
Thanks!
Click to expand...
Click to collapse
Hi
TWRP and the 'one touch recovery, better than CWM.
The backup kies can not recover from CWM
steps:
install odin, after recovery, nandroid backup, ROM, and root.
hi
Flash the stock firmware using odin!!..it will work!
Sent from my GT-N7100 using xda premium
freezes then booted
Hello I have this problem with my galaxy s2 i9100. After reboot the phone wasn't booting something like "boot loop" so I re flashed the firmware and now the phone boots up but after the boot it freezes immediately. So I decided to install clock work mod recovery and install cyanogen mode 11 with cyanogen mode the phone boots up and are able to be used again until the screen goes to sleep mode or the power button is pressed then the screen goes black and doesn't turn on after long pressing the power button it reboots. So I don't know what else to do I have tried kernels, operating systems re flashing reseting and nothing helps. No need to tel me to do resettings. Also my galaxy s2 i9100 chip has insane chip bug but I don't know if it has to do something with my problem.
Hi there everyone, recently signed up on here as xda seems to be the holy grail when it comes to all thing smartphone.
I'm fairly new to these type of phones and recently was given an infuse 4g that was suffering a power button problem.
The power button problem has been resolved with a new one and the phone was working fine for 3 / 4 weeks.
One day the phone shut down by itself and entered the boot loop syndrome. Factory clearing it hasnt seemed to do anything to resolve the problem as it continued to reboot continuosly.
I came across the thread about gtg ultimate unbrick guide in the developers forum and this seemed like a good way to go, get the phone all the way back to stock and then work from there.
Kies installed and all drivers installed fine. downloaded the gtg unbrick pack and followed the instructions line for line. Odin reports everything passed, took about 2:59 to complete.
phone rebooted and continued to do boot loop so went into recovery as stated and wiped data and cache and rebooted again.
phone is still stuck in some sort of boot loop, but it gets to display the 1st of the setup android phone screens, then just as you get a chance to select next to go onto the next screen, the phone reboots.
Any one have any idea what could be going wrong or as im fairly new to this, is there anything im doing or not doing right that is causing this.
The phone is an at&t infuse.
regards
Trevor
sound like an issue with stuck power button. it's a know issue with this model. google "infuse 4g boot loop" there's few youtube videos you can try.
tt33333 said:
sound like an issue with stuck power button. it's a know issue with this model. google "infuse 4g boot loop" there's few youtube videos you can try.
Click to expand...
Click to collapse
I've already replaced the power button with a new one, but the technician i use did say he will remove the power button completely to see if it does the same, just to rule that out
Trev
just redone the gtg flash and it boots into the os (ver2.2.1) and then within about 5 seconds turns off and reboots
can the new on off switch be faulty......im not so sure as in recovery mode, i can leave it on that screen forever and it doesnt attempt to reboot
Tried the one click repair with hemdial or what its called, updating thisnpost via a moto defy mini so excuse any typos.. The hemdiaOl just seemed to meas it up further. So got baxk into downliad mode with odin and reflashed to gtg brick recovery. Not fixed, still booting but at least the screen is now viewable.
To recover one of these phones, is there like a definitive guide as to what to do to first prepare one of these phones for recovery, ie, first, flash to this with cwm and then clear data, cache, dalcik etc. like an idiots fuide, i feel i may need one
Regards
Trev
this is my first htc and so far i am missing my samsung and motos
the phone is now completely non responsive and is stalled at the HTC boot screen with the text "this build is for development purposes only " i have the verizon htc one m8 ive tried removing the sd and sim holding power holding volume and power nothing makes a difference.
rooted with s off twrp is my custom recovery
started by putting slimrom on for a change of pace i had horrible signal strength and decided to try another rom somewhere in the process of flashing venom one my sd lost its backups the phone had stayed on the same screen for a while but eventually booted to a stable seeming venom rom and had 3g but no 4g service i ended up rebooting the phone today around 11 am and its been in this loop / screen since. i let the battery die down and was able to get to recovery and searched for my back ups but they were gone i ended up rebooting and now am stuck on the same screen as before. even after trying to enter recovery twrp it goes back to htc and not twrp
i tried every combination of buttons the few times and have drained the battery twice and now it just boots to this screen and is non responsive. hope that i can manage to find a way to push something to it or enter recovery and go back to stock using ruu's
anyone with input or advice would be a blessing at this point id be happy to make a donation for any useful help / anything to get me out of this screen even so i can push another rom or ruu to get me to stock
im afraid ive ruined a perfectly awesome phone
update got back to twrp and tried to re flash the venom one rom after full wipe but used their option for "stock" install said 100% and sucessful but upon the reboot is now seems to be stuck in the same screen.
got into the recover after battery died re flashed venom
after about 15 minutes on the htc screen it went to set up ....still very buggy more so than last time the phone was actually working but it is at least from what i can tell working ... going to try to get back to square one somehow
screen wont turn on and acts very buggy only time it stays on is holding power and gives reboot options... i done f ' ed this phone up.
How long are you waiting after I restarts when the install is finished? It will take a long time on that first boot. I have seen them take more than 5 minutes and if you interrupt it it can cause problems.