Went on the market and my phone went pop and keeps bootlooping. Now I can get into the bootloader and fastboot mode but nothing else.
Now what should I do any suggestions?
Flash Google's stock images?
It went pop? Trying to picture that.
tgerbracht said:
It went pop? Trying to picture that.
Click to expand...
Click to collapse
It made a pop sound, like when an old filament light blew.
restore an old backup try flashing a ROM or flash stock image
Did you do a battery pull? Sounds like it just crashed.
done a battery pull etc. just flashed stock images now and its booted up ill see how everything goes. It was just weird because I was already on stock images so I don't see how what I done made a difference.
tgerbracht said:
It went pop? Trying to picture that.
Click to expand...
Click to collapse
My phone will make that speaker pop when I use ROM Manager to reboot into recovery.
champers said:
My phone will make that speaker pop when I use ROM Manager to reboot into recovery.
Click to expand...
Click to collapse
Well then that's a bug in your kernel/rom you're currently using. :/. I've also had this too, but haven't seen it for approximately 2 1/2 months (first two weeks it scared the **** out of me and thought it was gonna blow the speaker, lol).
anton2009 said:
Well then that's a bug in your kernel/rom you're currently using. :/. I've also had this too, but haven't seen it for approximately 2 1/2 months (first two weeks it scared the **** out of me and thought it was gonna blow the speaker, lol).
Click to expand...
Click to collapse
Stock 4.0.2?
champers said:
Stock 4.0.2?
Click to expand...
Click to collapse
No... but you have a custom recovery but on stock...? O-o okay. Anyway. It was Android Revolution HD (4.0.2-based).
Related
OK....long story short...finally decided to delve into rooting and custom roms. Flashed CM6 yesterday and everything was going great. Then suddenly yesterday evening as I was swiping between home screens on my device everything froze, and I have been trying to recover ever since.
Anything I flash now just freezes, and i have a touch panel-fail so even when i do get a rom to boot i cant actually get into set it to usb mode or anything.
using bootloader i can not get it to connect using the adb driver so that I can push via adb.
about an hour ago I was successfully able to run the latest RUU and it ran successfully, but device is still way laggy (takes 15 minutes to boot) and no touch screen.
Any help would be greatly appreciated!!! don't know where to go from here. From what I have read its not bricked because I can get into Bootloader and Recovery???
Just a shot in the dark here, but it sounds like since you're stock now it's an actual hardware failure.
lil-dice said:
Just a shot in the dark here, but it sounds like since you're stock now it's an actual hardware failure.
Click to expand...
Click to collapse
Is there way I can verify that the RUU did indeed flash *EVERYTHING* back to stock?
It seen like you have a HARDWARE issues, Re-Boot the Stock Rom. Call Sprint and explain what's going on with your phone, please *DO NO'T MENTION YOU ROOTED YOUR PHONE* Tell them you try to wipe your phone and it was really laggy before you wipe, since you gonna Re-Boot the stock rom the phone is going to get UNROOTED, I know this cause I work at Sprint... So good luck...
jalexishg said:
It seen like you have a HARDWARE issues, Re-Boot the Stock Rom. Call Sprint and explain what's going on with your phone, please *DO NO'T MENTION YOU ROOTED YOUR PHONE* Tell them you try to wipe your phone and it was really laggy before you wipe, since you gonna Re-Boot the stock rom the phone is going to get UNROOTED, I know this cause I work at Sprint... So good luck...
Click to expand...
Click to collapse
I definitely wont rule out hardware issues...this is a refurb device i just swapped my original EVO for on Monday. I guess I just want to rule out any software issues for sure.
You mention that re-booting the stock rom will UNROOT the phone...however I hav no way to currently re-boot the rom??
Also looks like i can not get into recovery now, when I select the option in the bootloader it just takes me to the screen with a picture of a device and a red triangle
azkevman said:
I definitely wont rule out hardware issues...this is a refurb device i just swapped my original EVO for on Monday. I guess I just want to rule out any software issues for sure.
You mention that re-booting the stock rom will UNROOT the phone...however I hav no way to currently re-boot the rom??
Click to expand...
Click to collapse
Get a Memory Card adapter for PC or use anything that will let you connect your SD card to your computer... As soon as you put the *ORIGINAL STOCK ROM* in your SD card your phone will do everything by itself...
jalexishg said:
Get a Memory Card adapter for PC or use anything that will let you connect your SD card to your computer... As soon as you put the *ORIGINAL STOCK ROM* in your SD card your phone will do everything by itself...
Click to expand...
Click to collapse
ok, going to try this now...
I assume I need to load it onto my sd card as the pc36IMG.zip so that i can load it from the bootloader?
you got it...just put it on the root of sdcard and good luck.
Sent from my PC36100 using Tapatalk
azkevman said:
ok, going to try this now...
I assume I need to load it onto my sd card as the pc36IMG.zip so that i can load it from the bootloader?
Click to expand...
Click to collapse
Yeah... Good luck... Let me know how everything went..
OK, so I loaded this ROM: http://forum.xda-developers.com/showthread.php?t=874091 onto my sd card as PC36IMG.zip
It loads the zip then says parsing for about 1 second then just reverts back to the HBOOT option ???
Doesn't ask me if i want to install????
Looks like I grabbed only the OTA update rom that was posted on that page. I am going to try the odexed version on this page: http://forum.xda-developers.com/showthread.php?t=874251
azkevman said:
Looks like I grabbed only the OTA update rom that was posted on that page. I am going to try the odexed version on this page: http://forum.xda-developers.com/showthread.php?t=874251
Click to expand...
Click to collapse
I can upload the version I use... Give a sec.(Uploading)
OK here you go !! http://www.megaupload.com/?d=EKDYV9I5 I hope this help you !
jalexishg said:
OK here you go !! http://www.megaupload.com/?d=EKDYV9I5 I hope this help you !
Click to expand...
Click to collapse
Thanks, I will let you know how it goes.
is nand unlocked on the phone?
asafegous said:
is nand unlocked on the phone?
Click to expand...
Click to collapse
I think so, on the bootloader it still shows "S-off" ...doesn't that indicate it is still unlocked?
OK, so I was able to flash the file in the bootloader. It looks like it won't load past the 'HTC EVO 4g' splash screen.
ARGGGGGGGGGGGGGG!!!!!!!!!!!!
But the Installation finish without problems ?
jalexishg said:
But the Installation finish without problems ?
Click to expand...
Click to collapse
yeah, as far as i can tell. It said it completed and gave me the option to press the power button to reboot.
It did finally load up...after about 15 minutes, but touchscreen is still erroring out and not funtional.
Ok wasn't sure if I should post this in Q&A or Dev... but since it's a question:
"Can anyone help with this?" ..
Here's the situation.
Sprint Galaxy S3.. using Blazer ROM 1.6
Team Epic Recovery (non-touch), don't recall exact version
Everything has been fine the last week or so.
I changed 2 things earlier today:
1) Using NFC Task Manager, I enabled "NFC during AirPlane mode" after which it asked me to reboot. I did not at that moment...
2) I modified build.prop to change the default alarm ringtone.
I also did not reboot as I was about to make some other changes...
Since I'm at work, I got sidetracked, but noticed something since the phone was on my desk face up. It suddenly rebooted on it's own.
No big deal, I had thought... except it never came back on.
And now.. It won't boot up at all. I cannot go into recovery either!!
I CAN go into download mode... so I did so and tried to reflash recovery.
Still unable to boot up or go into recovery..(Phone flashes the samsung logo , then disappears forever).
I'm attempting to download the stock ROM via the toolkit and see if that will fix things, but without recovery I'm pretty sure nothing is going to work.
Has anyone seen something like this before? Where it will go into download mode but NOT recovery?
Try flashing the stock tar in odin if nothing else works.
DroidGnome said:
Ok wasn't sure if I should post this in Q&A or Dev... but since it's a question:
"Can anyone help with this?" ..
Here's the situation.
Sprint Galaxy S3.. using Blazer ROM 1.6
Team Epic Recovery (non-touch), don't recall exact version
Everything has been fine the last week or so.
I changed 2 things earlier today:
1) Using NFC Task Manager, I enabled "NFC during AirPlane mode" after which it asked me to reboot. I did not at that moment...
2) I modified build.prop to change the default alarm ringtone.
I also did not reboot as I was about to make some other changes...
Since I'm at work, I got sidetracked, but noticed something since the phone was on my desk face up. It suddenly rebooted on it's own.
No big deal, I had thought... except it never came back on.
And now.. It won't boot up at all. I cannot go into recovery either!!
I CAN go into download mode... so I did so and tried to reflash recovery.
Still unable to boot up or go into recovery..(Phone flashes the samsung logo , then disappears forever).
I'm attempting to download the stock ROM via the toolkit and see if that will fix things, but without recovery I'm pretty sure nothing is going to work.
Has anyone seen something like this before? Where it will go into download mode but NOT recovery?
Click to expand...
Click to collapse
Just flash the stock tar ur downloading in Odin. Ur fine even if you managed to Bork recovery as long as u can still get into dl mode ur ok
I've haven't seen this problem on the Sprint variant yet but it definitly sounds like it's fixable
Like others have pointed out, since you can get into Download mode fine flash the Stock Odin tar file found here
When you boot up I would consider doing a data wipe (Factory Reset option in Settings>Back up and reset) but that's up to you
Yep.. that stock ROM fixed it... now to 're-root' and reapply my ROM... fun fun fun.
I'm thinking that the build.prop change must have caused it.. will be testing that over the weekend to be sure
DroidGnome said:
Yep.. that stock ROM fixed it... now to 're-root' and reapply my ROM... fun fun fun.
I'm thinking that the build.prop change must have caused it.. will be testing that over the weekend to be sure
Click to expand...
Click to collapse
That is weird tho.. I edit my build.prop all the time and haven't seen this before.
Sent from my SPH-L710 using xda premium
DroidGnome said:
Yep.. that stock ROM fixed it... now to 're-root' and reapply my ROM... fun fun fun.
I'm thinking that the build.prop change must have caused it.. will be testing that over the weekend to be sure
Click to expand...
Click to collapse
Ya Ive seen some build.prop changes mess things up. Luckily you could get back up.
Fun feeling huh! lol
fergie716 said:
That is weird tho.. I edit my build.prop all the time and haven't seen this before.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
So far all is working and I didn't even have to wipe the data (actually couldn't at first because I couldn't get into recovery hehe) , and I'm guessing the build prop must have been because I did it on the device, and 'maybe' I hit a stray key or something.. usually I edit at home and push it to the phone but I was in sort of a hurry.
WILL NEVER DO THAT AGAIN!
As I watched it attempt to boot up each time, I kept coming up with different excuses to try to tell the Sprint store
DroidGnome said:
So far all is working and I didn't even have to wipe the data (actually couldn't at first because I couldn't get into recovery hehe) , and I'm guessing the build prop must have been because I did it on the device, and 'maybe' I hit a stray key or something.. usually I edit at home and push it to the phone but I was in sort of a hurry.
WILL NEVER DO THAT AGAIN!
As I watched it attempt to boot up each time, I kept coming up with different excuses to try to tell the Sprint store
Click to expand...
Click to collapse
Glad to hear you're up and running again!!
Best excuse ever to Sprint is when I woke up it was like that haha
I've been using my Galaxy Nexus for a month or so, with the official JB ROM (JR30C or whatever, deodexed and rooted) and today I opened Gmail.
That's it. I opened GMail, switched accounts, and my phone has been bootlooping ever since.
I wiped everything in CWM multiple times and reflashed it, and I can't get the phone to do anything else.
Any clues?
Do you have a working nandroid? Have you tried flashing a different ROM?
Allons-y
Xfanatic said:
Do you have a working nandroid? Have you tried flashing a different ROM?
Allons-y
Click to expand...
Click to collapse
I do not have a working NANDROID. I wasn't sure about the Internet policies at work, but it looks like I can at least make it on here, I'm not sure I'll be able to download another ROM.
I'm confused though, I mean I know it would help to try as many options as possible (to fix it) - but this ROM has been working for weeks. And the phone died randomly, not due to a recent file change or a botched program. The only boot loops I've experienced before were on the Nexus One, and it was always due to a buggy/bad flash or a corrupted ROM download - this one just developed epilepsy on its own...
Here's my plan, since these are the only things I can manage to download due to restrictions on Internet usage at work.
Factory 4.1.1 takju image from here : https://developers.google.com/android/nexus/images#takju
Modified ODIN software here: http://forum.xda-developers.com/showthread.php?t=1586807
ODIN won't rewrite my bootloader, recovery, or userdata, since I already OEM unlocked, but will reflash a stock image.
EDIT: ODIN won't do anything with my device. Trying this ROM instead:
http://forum.xda-developers.com/showthread.php?t=1801664 was using bigxie OTA before.
is your (sd)storage recognized? thus is a similar symptom to when the stirage goes bad.
Hook the phone up to adb, boot it, and let logcat run. Maybe that will turn something up.
Sent from my Galaxy Nexus using Tapatalk 2
simms22 said:
is your (sd)storage recognized? thus is a similar symptom to when the stirage goes bad.
Click to expand...
Click to collapse
Hmm, you know, I'm not able to find the option to mount to USB in CWM...and just in case I forgot where that is, when I plug it in, I get the "hardware failed" noise from Windows and not the usual friendly "plug in" sound.
infazzdar said:
Hook the phone up to adb, boot it, and let logcat run. Maybe that will turn something up.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'm at work, and I only have my work computer. Group/secpolicy won't allow me to install anything, no admin rights, etc.
Would it even do anything? The phone barely makes it through one second of the boot animation before it loops.
sheik124 said:
Hmm, you know, I'm not able to find the option to mount to USB in CWM...and just in case I forgot where that is, when I plug it in, I get the "hardware failed" noise from Windows and not the usual friendly "plug in" sound.
Click to expand...
Click to collapse
you cant mount the sd card. there is no USB mass storage period. not in recovery or booted normally.
Zepius said:
you cant mount the sd card. there is no USB mass storage period. not in recovery or booted normally.
Click to expand...
Click to collapse
Oy. Then how do I get another ROM on here? fastboot/adb?
sheik124 said:
Oy. Then how do I get another ROM on here? fastboot/adb?
Click to expand...
Click to collapse
Adb push.
Sent from my Galaxy Nexus using Tapatalk 2
Zepius said:
you cant mount the sd card. there is no USB mass storage period. not in recovery or booted normally.
Click to expand...
Click to collapse
sheik124 said:
Oy. Then how do I get another ROM on here? fastboot/adb?
Click to expand...
Click to collapse
Got more than one additional ROM on there via adb/recovery - my clue that CWM hasn't actually been able to do anything since the phone start looping is I'm still getting my custom boot animation.
I'm using the toolkit to reflash a stock image now. What a mess.
Even reflashing a stock image via fastboot did nothing. WTF happened to my phone? Won't stay on long enough to get a logcat
I'm having the same problem as this guy:
http://forum.xda-developers.com/showthread.php?t=1827685&page=2
I just got finished trying to flash 4.1.1 using ODIN. It still shows me the custom animation from bigxie's ROM (which has supposedly since been overwritten 2-4x times).
Screw you Samsung...this phone is a month old, I flashed -once- to rooted Jelly Bean, and the phone dies when I open the GMail app.
EDIT: WTF - I write screw you Samsung, it boots to the Welcome screen! Just long enough for me to see that my files aren't on it anymore, then it bootloops again. And again. Now it's re-stuck in a bootloop.
And now I'm at the homescreen. I can't rely on this thing like this...is my flash dying or something?
Nobody?
It worked long enough for me to re-enter all of my different Google account information and now it's dead again. Now it only flashes the boot animation for a split second for bootlooping.
I'm thinking of a hardware defect.
Beamed from my Grouper
Mach3.2 said:
I'm thinking of a hardware defect.
Beamed from my Grouper
Click to expand...
Click to collapse
Mee too. As you can see from my signature, I gave up and bought a One S yesterday night from Craigslist. Feels like a true successor to the Desire / N1. It's nice to finally have an AMOLED screen that actually seems color calibrated after the ugly mess that was my RAZR and my less than perfect GNex. It's a damn shame how much more painless flashing a recovery was on this thing.
Sent from my HTC VLE_U using xda app-developers app
Last month, my gnex suddenly rebooted itself when texting, then it just stuck in bootloop forever.
I got it work again only after several times of factory reset and even pushing factory image.
I was using xenon + franco at that time.
However, 3 days ago it rebooted itself again when playing a music app, then the bootloop problem happened again. Somehow it could boot, but within a minute, it reboots and bootloops again.
i was using xylon + ak kernel this time.
I started to think if this is due to hardware problem.. and i took it to store yesterday after pushing the factory image to it. they said this is due to some incompatibility of some apps... (i dun understand why factory image could have this issue...) and did a recovery for me. My phone is reset back to 4.0.4 and it seemed working fine..
Then i pushed back the 4.2.1 factory image to it and still nothing happened. i started flashing back xylon and ak kernel to see if it works. It did run perfect for the whole night until this morning. When i was installing some ordinary apps, eg. air, skout, it rebooted itself again...
Flashing factory image of 4.2.1, 4.1.2, and even 4.0.4 all do not work.
it got past the google screen, and then to the bootanimation for a few seconds and it freezes and color seems weird, and then reboot again.
i have tried flashing through the toolkit and also through fastboot command..
does anyone know what is the problem causing this...
thanks in advance.
Anyone help please..
thyau said:
Anyone help please..
Click to expand...
Click to collapse
ok lets see if my craziness can help lol
ok this will seem crazy but it is a last resort which i did the other day .
if you have nothing to lose do this its a 50-50 shot
but first
what recovery and what toolkit do you have before i tell you this
I'm using cwm touch 6.0.2.3 and gnex toolkit v10
What's the method I'm driven crazy by this phone.. So this may be useful for me... :angel:
thyau said:
I'm using cwm touch 6.0.2.3 and gnex toolkit v10
What's the method I'm driven crazy by this phone.. So this may be useful for me... :angel:
Click to expand...
Click to collapse
ok i have twrp and this tool kit
http://www.wugfresh.com/nrt/
but idk if the v10 is the same way
but i wiped the system and took the whole os off the phone than restored the factory image
idk if that option is in your recovery tho
or download the toolkit i linked go to fastboot flash the stock image in that toolkit root it (it will install the recovery i use also)
and restore you apps if it happens again wipe the system and do as i said.
i highly trust the toolkit i use it saved my ass alot. i couldnt get the v10 toolkit to work for me at all
Alpha_wolf said:
ok i have twrp and this tool kit
http://www.wugfresh.com/nrt/
but idk if the v10 is the same way
but i wiped the system and took the whole os off the phone than restored the factory image
idk if that option is in your recovery tho
or download the toolkit i linked go to fastboot flash the stock image in that toolkit root it (it will install the recovery i use also)
and restore you apps if it happens again wipe the system and do as i said.
i highly trust the toolkit i use it saved my ass alot. i couldnt get the v10 toolkit to work for me at all
Click to expand...
Click to collapse
If this is the case... I have been crazy already.. lol as I've tried wiping all the things including the system partition..
But I haven't tried using your combination, so Ill give it a try :good:
Thanks bro
thyau said:
If this is the case... I have been crazy already.. lol as I've tried wiping all the things including the system partition..
But I haven't tried using your combination, so Ill give it a try :good:
Thanks bro
Click to expand...
Click to collapse
nothing to lose right? might as well try anything lol
sounds like your device might have a problem with its internal storage
Alpha_wolf said:
nothing to lose right? might as well try anything lol
Click to expand...
Click to collapse
All user data has been lost due to the crash already, really nth to lose.. lol
simms22 said:
sounds like your device might have a problem with its internal storage
Click to expand...
Click to collapse
You mean physically right??
thyau said:
All user data has been lost due to the crash already, really nth to lose.. lol
You mean physically right??
Click to expand...
Click to collapse
yea, physically. when/if it finally goes, you wont be able to recover from the bootloop.
simms22 said:
yea, physically. when it finally goes, you wont be able to recover from the bootloop.
Click to expand...
Click to collapse
I think I'm going to store tmr again..
But how to stress that this may be due to hardware problem? Since if I just describe the issue, I'm afraid they may think that this is software incompatibility again..
thyau said:
I think I'm going to store tmr again..
But how to stress that this may be due to hardware problem? Since if I just describe the issue, I'm afraid they may think that this is software incompatibility again..
Click to expand...
Click to collapse
well, it is a common issue with the nexus devices without a sd slot(nexus s and the galaxy nexus).
after a clean flash of Maguro Overdrive milestone 1, the phone is running again...
restored some of the apps.
let's see how long can the phone stand before another round of bootloop...
thyau said:
after a clean flash of Maguro Overdrive milestone 1, the phone is running again...
restored some of the apps.
let's see how long can the phone stand before another round of bootloop...
Click to expand...
Click to collapse
Op the same thing is happening to me, i also was on xylon and it was running fine and it just started bootlooping. i tried everything toolkit, flashing factory image lie you did and nothing, the only one that works now is ics stock 4.0.4 .if i try any other rom stock or custom the bootloops starts again and it wont boot, it only boots on 4.0.4 .so pretty much the same thing happened to me .
So last night, I guess my phone was trying to download and install security update from samsung and failed. My battery died later cause it was low and after I recharged my phone and turned it on, my phone literally took a crap. Everything crashes even settings. Cant send a text out. Bluetooth wont turn on etc.
Now after I back up my photos somehow, what would be the best way to restore to keep root and CWM?
Settings-restore?
dl note 3 os then flash with CWM?
Thanks guys.
Hmmmm
steve45058 said:
So last night, I guess my phone was trying to download and install security update from samsung and failed. My battery died later cause it was low and after I recharged my phone and turned it on, my phone literally took a crap. Everything crashes even settings. Cant send a text out. Bluetooth wont turn on etc.
Now after I back up my photos somehow, what would be the best way to restore to keep root and CWM?
Settings-restore?
dl note 3 os then flash with CWM?
Thanks guys.
Click to expand...
Click to collapse
I did have a similar issue. My quick fix wasn't so quick though. I completely formatted, flashed stock ROM back, chainfire root, CWM to bootloader then you're free. I got my files from galaxynote3root.com
Sent From My Hyperdrive Note 3 SM-G900T
Jack Ketch said:
I did have a similar issue. My quick fix wasn't so quick though. I completely formatted, flashed stock ROM back, chainfire root, CWM to bootloader then you're free. I got my files from galaxynote3root.com
Sent From My Hyperdrive Note 3 SM-G900T
Click to expand...
Click to collapse
So its weird, after I let the phone stay on for like an hour, everything seems to load properly and nothing crashes. Planning on reformatting, but I am kind of worried on why this happened. I am on stock rom.
steve45058 said:
So its weird, after I let the phone stay on for like an hour, everything seems to load properly and nothing crashes. Planning on reformatting, but I am kind of worried on why this happened. I am on stock rom.
Click to expand...
Click to collapse
It's possible during your update critical files were missed do to power loss and were replaced on reboot? I unfortunately was not able to get passed the bootscreen to recovery or the system itself. So i was forced to divert back to stock firmware and start from the beggining. So if you run into any more issues you might start there. If you kept root all should be well i believe. :good:
Jack Ketch said:
It's possible during your update critical files were missed do to power loss and were replaced on reboot? I unfortunately was not able to get passed the bootscreen to recovery or the system itself. So i was forced to divert back to stock firmware and start from the beggining. So if you run into any more issues you might start there. If you kept root all should be well i believe. :good:
Click to expand...
Click to collapse
Well my phone didn't die when it was updating, the update failed well before that. I was just saying that after it did die and I turned it on, everything went downhill from there. Really weird
steve45058 said:
Well my phone didn't die when it was updating, the update failed well before that. I was just saying that after it did die and I turned it on, everything went downhill from there. Really weird
Click to expand...
Click to collapse
I have a backup of all my pictures on google + they give 15GO i have all my video and importants stuf backed up. When I have a problem with the phone hard reset and reinstall the rom. I use philz recovery is working like a charm to me