Related
Okay so I was running CM9 3/22/2012 just fine. I noticed a nightly went up listed as 3/23/2012. So I downloaded and clicked on the downloaded file, for some reason Rom Manager took over and asked if I wanted to go into CWM. So I agreed and it took me to the AT&T screen with the exclamation mark. I then rebooted and got stuck on the same At&T screen. So I decided to use Odin to go to stock and start from scratch. For some reason Odin 1.81 was supposed to go back to stock with Root. For some reason it got stuck I turned off my phone and now it is unresponsive to most of the tricks listed on this forum.
So will a jig get me out of this jam, a quick search pulled up nothing reliable or I would have to wait 3 weeks to receive, I need it this week like tomorrow if possible.
Searched the forums before going to work real quick couldn't get anything concrete So I'm posting this and I will search some more when I get to work.
Thanks for any help.
logicrulez said:
Okay so I was running CM9 3/22/2012 just fine. I noticed a nightly went up listed as 3/23/2012. So I downloaded and clicked on the downloaded file, for some reason Rom Manager took over and asked if I wanted to go into CWM. So I agreed and it took me to the AT&T screen with the exclamation mark. I then rebooted and got stuck on the same At&T screen. So I decided to use Odin to go to stock and start from scratch. For some reason Odin 1.81 was supposed to go back to stock with Root. For some reason it got stuck I turned off my phone and now it is unresponsive to most of the tricks listed on this forum.
So will a jig get me out of this jam, a quick search pulled up nothing reliable or I would have to wait 3 weeks to receive, I need it this week like tomorrow if possible.
Searched the forums before going to work real quick couldn't get anything concrete So I'm posting this and I will search some more when I get to work.
Thanks for any help.
Click to expand...
Click to collapse
not sure why you would even be using Rom Manger other then maybe renaming backups. This is i known issue with our phones and Rom Manager and has been stated way too many times. Try holding the power button down for a while to see if it resets. A jig is going to put you in download mode so that you can use Odin again.
Thanks for the reply. Yes I have heard of issues with Rom Manager and i stopped using it. But for some reason or another I kept it on my phone and idiotically agreed to having it put me into CWM. Also I kept the battery in the phone till I got to work, pulled it out of my bag to try the suggestion that was given above and noticed my phone is warm. Not sure what's up with that, I immediately pulled the battery and will let it cool for a while and then I will try with the above suggestion.
Can you recommend a jig for our phones or does any jig work on any phone.
Thanks for all your help and wisdom.
logicrulez said:
Thanks for the reply. Yes I have heard of issues with Rom Manager and i stopped using it. But for some reason or another I kept it on my phone and idiotically agreed to having put me into CWM.
Can you recommend a jig for our phones or does any jig work on any phone.
Thanks for all your help and wisdom.
Click to expand...
Click to collapse
you can get a jig from just about anywhere. you probably dont need one though. have you even tried manually putting your device into download mode by powering down the phone, plug usb into comp, then holding down both volume buttons, then plugging in the device?
http://www.ebay.com/sch/i.html?_fro..._nkw=galaxy+s+2+jig&_sacat=See-All-Categories
Yes I have held the power and up/down volume buttons(that's what works on my phone) and plugged usb into phone while it was plugged in to my computer to get into download mode but nothing happened. Too late I already ordered a jig as I am despearate and hopefully it will be of further use in the future. I also tried holding the power button down for a while and still nothing. Hopefully the jig comes in a couple of days and works.
Thanks for all your help and wisdom.
Okay, so I got my jig today and put it into my phone and nothing happened. I put my phone on the charger and left it til I got home so it should be charged up.
So am I bricked or is there any other options I can try.
Thanks for your help.
Did you try holding both Vol and power keys (all 3) together for 30 seconds? It's saved my bacon a few times, despite how nonintuitive it seems. Also try the USB thing with battery removed, or try putting USB in and inserting battery while holding all 3 keys.
Still a no go I'll call warranty to see if I can get it replaced. If not I'll just wait for sgsiii to come out since its supposed to come in April now.
Thanks for all your help!
If your phone locked up while flashing bootloaders..
All,
I've been following posts on XDA since my original droid incredible days. I've rooted and maintained two phones, never have any issues.
Recently I purchased a T-Mobile Springboard (got a crazy promotion price through my company) which ran stock TMo Honeycomb. Eager to get ICS and eager to get rid of the power-on tmobile jingle, I installed the latest S7-302u firmware update from Huawei's website. I am aware that my device is technically S7-303u, but the update worked fine and I had little-to-no bugs. I am very pleased with this tablet.
Now here where I get stupid.
A coworker of mine then tells me that he has a S7-303u update.zip file that he can give me, which I don't object to. I give him my micro SD, he places the file in the 'dload' folder with 'unlmt.cfg'. I then reconsider my predicament, and decide that I'm happy with my current firmware, even if it's not made specifically for my tablet hardware version. If it ain't broke, don't fix it.
By the evening, I forget that the update file is on my SD card.
Before going to bed, I extinguish the battery and let it power down. I then plug it in the the wall and fall asleep.
Around 3 am (3 hours later) I was woken up to my springboard rebooting. Confused, I pick it up and see that it's in some kind of boot-loop. The screen turns on, but stays black, and then immediately powers down, and restarts. This process repeats indefinitely. I hold the power button down, trying to do a hard-reboot, but it doesn't seem t work. Then, after about 5 "holding the power button down for 10 seconds", the device reboots and I am graced with the gracious Huawei MediaPad logo.
The device automatically goes into recovery mode and installs the forgotten update.zip....
Now I'm pissed, specifically because I've lost my high scores in Trainyard Express and just because I now how to re-install all my apps. It's annoying, but it's not the end of the world. Or so I thought.
I use my tablet 75% of the time for reading through the kindle app, and on this version of ICS the kindle app doesn't work! So immediately I decide to revert back to the old S7-302u update that I originally had installed, following the same steps I did to manually update the device previously.
I now cannot, for the life of me, get this thing to boot into recovery mode. The only thing I can get this device to do is get to the "Enter into fastboot mode" screen by holding the power button and the volume+ key (the one closest to the power button).
A few other symptoms:
1. The device is set to quickstart mode by default and I don't see any option to deactivate it. The only way to get the device to actually "turn off" is to choose restart to hold the power button down for a hard reboot.
2. If I hold down the power button for ten seconds, I expect the device to power down and stay down. This is not the case. It always reboots immediately. I have no way of actually fully powering this device down (not counting the quick-start power-down).
3. No charging indication. I'm not sure if this is a hardware or software issue. My device will charge, but it does not give any indication on the screen or the battery icon.
Now I'm stuck wondering what to do. Did I ruin this device? I wanted to avoid rooting it because of the loss of 4G data, but now I'm afraid that I might need root-permissions to fix whatever I messed up.
Thanks in advance for your help.
Daniel
PS. Just so you all know my experience, I've rooted and maintained a droid incredible and currently, my galaxy nexus. I however, have no programming experience what-so-ever. I'm just good at following directions (usually).
What happens if you pull the micro sd card out? It should stop the boot loop (in theory). If the install didn't go through it should boot up normally to the previous version. In settings you can turn off FastBoot.
You might have to look at the sd card on a computer and either get rid of the unlmt.cfg from the dload folder and it shouldn't try to boot to the dload folder.
eurobass said:
All,
I've been following posts on XDA since my original droid incredible days. I've rooted and maintained two phones, never have any issues.
Recently I purchased a T-Mobile Springboard (got a crazy promotion price through my company) which ran stock TMo Honeycomb. Eager to get ICS and eager to get rid of the power-on tmobile jingle, I installed the latest S7-302u firmware update from Huawei's website. I am aware that my device is technically S7-303u, but the update worked fine and I had little-to-no bugs. I am very pleased with this tablet.
Now here where I get stupid.
A coworker of mine then tells me that he has a S7-303u update.zip file that he can give me, which I don't object to. I give him my micro SD, he places the file in the 'dload' folder with 'unlmt.cfg'. I then reconsider my predicament, and decide that I'm happy with my current firmware, even if it's not made specifically for my tablet hardware version. If it ain't broke, don't fix it.
By the evening, I forget that the update file is on my SD card.
Before going to bed, I extinguish the battery and let it power down. I then plug it in the the wall and fall asleep.
Around 3 am (3 hours later) I was woken up to my springboard rebooting. Confused, I pick it up and see that it's in some kind of boot-loop. The screen turns on, but stays black, and then immediately powers down, and restarts. This process repeats indefinitely. I hold the power button down, trying to do a hard-reboot, but it doesn't seem t work. Then, after about 5 "holding the power button down for 10 seconds", the device reboots and I am graced with the gracious Huawei MediaPad logo.
The device automatically goes into recovery mode and installs the forgotten update.zip....
Now I'm pissed, specifically because I've lost my high scores in Trainyard Express and just because I now how to re-install all my apps. It's annoying, but it's not the end of the world. Or so I thought.
I use my tablet 75% of the time for reading through the kindle app, and on this version of ICS the kindle app doesn't work! So immediately I decide to revert back to the old S7-302u update that I originally had installed, following the same steps I did to manually update the device previously.
I now cannot, for the life of me, get this thing to boot into recovery mode. The only thing I can get this device to do is get to the "Enter into fastboot mode" screen by holding the power button and the volume+ key (the one closest to the power button).
A few other symptoms:
1. The device is set to quickstart mode by default and I don't see any option to deactivate it. The only way to get the device to actually "turn off" is to choose restart to hold the power button down for a hard reboot.
2. If I hold down the power button for ten seconds, I expect the device to power down and stay down. This is not the case. It always reboots immediately. I have no way of actually fully powering this device down (not counting the quick-start power-down).
3. No charging indication. I'm not sure if this is a hardware or software issue. My device will charge, but it does not give any indication on the screen or the battery icon.
Now I'm stuck wondering what to do. Did I ruin this device? I wanted to avoid rooting it because of the loss of 4G data, but now I'm afraid that I might need root-permissions to fix whatever I messed up.
Thanks in advance for your help.
Daniel
PS. Just so you all know my experience, I've rooted and maintained a droid incredible and currently, my galaxy nexus. I however, have no programming experience what-so-ever. I'm just good at following directions (usually).
Click to expand...
Click to collapse
Thanks
What is the firmware version of S7-302u are you installed in your S7-303u?
Hey, I have the springboard and did the exact thing you did, somehow the stock recovery was all messed up, best bet is to install twrp using fastbood and cm10. just follow after_silences instructions here,
http://forum.xda-developers.com/showthread.php?t=2045808
[Edit]once you change tmo stock firmware you'll lose your 4g option(there my be a fix for this now)but you will be able to text and make calls over 2g, edge2 and 3g"no need for WiFi or side app"[Edit]
HELP!
1st gen Nexus 7. Came home today and found it in the google 4 color boot loop swishing the balls around and around. I don't remember rebooting it or installing any updates, so I just let it run.
20 minutes later- still there.
I powered it off, press the down+power, get to the restore- only to get 'system command not recognized' (unfortunately I didn't write it down, but it showed a flat android with a red ! over the open chest).
Kids started screaming about some trauma... came back... tablet was black. Tried rebooting- nogo. Tried powering up/down- nogo. Hold power for 2 minutes, all buttons, no buttons, down, up, etc- nothing.
Plugged it into the PC- get a 'APX mode', but still no screen and no power charging logo.
I've had the damn thing for not even 3 weeks. Can't even tell you what the last update was but it wasn't lollipop as I hadn't seen that yet when my nexus 4 got updated 2 weeks ago.
No, I didn't do wheelie or any backups because I hadn't made any changes to the system. I've got nothing.
32gb model. Don't know what else I can get off of this brick.
Yes, I've read all the threads I can find on APX mode- installed android toolkit, tried to find the dropbox files to get the windows restore- nogo.
I'll take any suggestions or ideas. And no, I really wasn't f-ing around with it either- it's for the 6 year old kid who needs work on sight words and math... I don't need to be running crazy stuff on it... (Feel free to move to appropriate forum as I only saw Nexus 7 2013)
Anyone? Bueller ?
Did I post in the wrong forum? Or am I really just SOL?
Hi there! Long time reader, first time poster (TL;DR below...but it should be a quick read anyways )
So I've been using this S2 of mine for almost 4 years now, haven't had any trouble (other than a couple of battery swaps). For the past 6 months or so I've been using CM 12.1 nightlies without issue.
The events:
- The other day, my phone froze (I wasn't using it when it froze, it was when I went to use it that I noticed...it was on the wifi selection screen if it matters), so I held the power button to shut it down, and when I powered it back up, it just froze at the Samsung boot screen (with the usual yellow triangle).
- At this point, I was able to reboot into download mode at will, but any attempt to boot to recovery just led to the freeze at the Samsung boot screen. Also, the phone would automatically reboot itself at this point any time I inserted the battery (I was of course putting the battery in and out trying everything I could).
- I would have reflashed from Odin at this point, but since I was away for a few days I just kept trying to reboot into recovery, to no avail. On one of these attempts (power+vol up+ home) it showed the Samsung boot screen, and then immediately shut down and I haven't been able to get anything onto the screen since
I'm now home, and I can't seem to fix it. If I plug the phone into a charger, the top half or so of the phone gets warm, and it also seems to get warm if it isn't plugged in and I try to power it up. I was thinking maybe the phone was maybe doing the same thing as before and just not showing anything on screen, but I blindly do the steps to get it into download mode, and Odin doesn't recognize anything (drivers are definitely installed). I have also tried other batteries, no luck.
Any ideas of what I might try? I'm willing to do anything. For the record nothing happened to the phone at all when this all happened (no dropping or water damage or anything, just my attempts at booting into recovery). Maybe I should try a jig? I'm also open to opening the phone if there's something I can do, though I don't have experience with this.
Thanks so much for any suggestions!
TL;DR: phone froze (running CM 12.1 nightly), held power to shut it down, and then consistently froze at the boot screen on any attempts to power it on. After a few attempts at booting into recovery (the phone would only freeze or enter download mode) the screen suddenly shut off and I haven't seen anything on it since no matter what I try. I can't think of anything that happened to the phone I'm open to any and all suggestions! Thanks
One sentence amongst your description stands out like a 'sore thumb'.....
That the device heats up towards the top when you attempt to charge it.......
Until you try a jig I can't be certain, but that heating coupled with a dead/unresponsive screen along with a lack of recovery and/or download modes (download mode is 'hardwired' into the device, and NOTHING should be able to corrupt it) are the primary symptoms of a failed motherboard.......
That is my opinion based on my experience in these forums and personal experience with a (now dead) S2 (one of two that I own).........
Get the jig just to be sure, but I'd be surprised if it had any effect.....sorry to be typing something you don't want to read, but you said it yourself, the device is 4 years old....it's been in service roughly twice as long as most smartphones, and they don't last forever....
http://i.imgur.com/rVnFwJM.jpg
Thanks dude! It's nice to have some idea of what happened. I am indeed very happy my phone has lasted me this long, and my friend is gonna give me an extra S2 she has anyways it seems so it's all good!
I'll try the jig and update here with the result (I ordered one online...will arrive in January sometime)...just in case anyone is curious.
smacsmac said:
Thanks dude! It's nice to have some idea of what happened. I am indeed very happy my phone has lasted me this long, and my friend is gonna give me an extra S2 she has anyways it seems so it's all good!
I'll try the jig and update here with the result (I ordered one online...will arrive in January sometime)...just in case anyone is curious.
Click to expand...
Click to collapse
Yeah....be good to know the results.....If only to confirm or refute what I've suggested.....
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
Yeah....be good to know the results.....If only to confirm or refute what I've suggested.....
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
Sorry it took me a while...the jig was in the post haha. It didn't do anything at all (no response when I plugged it in) so I think it's safe to say you were bang-on and the motherboard failed! Happily using a new S2 (with CM13.0 now ) on behalf of my friend though.
Thanks again.
Sounds familiar. Happened to me also due to failed cyanogenmod update (CM13). Only thing that works is download mode, so i'm not given up hope yet.
I can't post a link but google ''Apply Update Failure samsung galaxy s II'' there's a thread about this on the cyanogenmod forum.
Elaias said:
Sounds familiar. Happened to me also due to failed cyanogenmod update (CM13). Only thing that works is download mode, so i'm not given up hope yet.
I can't post a link but google ''Apply Update Failure samsung galaxy s II'' there's a thread about this on the cyanogenmod forum.
Click to expand...
Click to collapse
oh mine was just straight up dead...no download mode or anything visible on the screen (and nothing to do with CM13 either)
hope you get yours sorted out! have you tried reflashing anything via Odin while in download mode?
Its hard to tell you and hard to accept. You can almost give up the hope, your NAND Chip is just what we call " wear-out ". In the most cases no write is possible anymore, the funny part is -> sometimes read is still fine. If that is the case: The system is booting and working, but saving just nothing. The NAND is frozen to its state before it broke.
At our local store, customers come to us with issues like " Factory Reset impossible ", "Can't delete my Files" "Can't create files". All these Devices have inaccessible NAND's and inaccessible Recovery. Only Bootloader is working, but as the NAND is broken, flashing doesn't change anything.
smacsmac said:
oh mine was just straight up dead...no download mode or anything visible on the screen (and nothing to do with CM13 either)
hope you get yours sorted out! have you tried reflashing anything via Odin while in download mode?
Click to expand...
Click to collapse
yeah, flashing with odin did the trick. now running cm13 and everything works fine. sorry to hear that your phone turned to brick.
Well, I maybe should have listened. So I had just flashed a ROM on my 6P, set a few things up, it was charged 98%, I downloaded an app, checked an e-mail, then walked away. Then after 30 minutes I went to the phone to check e-mail, and it was dead. I mean, wouldn't boot in any way complete black screen. Hooked up to computer, nothing. No buttons will boot the device.
So ridiculous....a $500 paper weight. Now I have to find a decent Verizon phone with good development to buy.
Well, had fun for 2 months!
Bye Nexus 6P forums!
OK - I held volume down button and power button for almost 3 minutes and it finally booted. This never happened before. Scary, but if this happens to you take note! :silly:
So my phone is unusable and I have to find a new Verizon phone that has good development. Good luck to me - guess I'll have to sacrifice my unlimited data I've had for many years for a phone with a new carrier so I can root it with good development. I hate Verizon.
darbylonia said:
So my phone is unusable and I have to find a new Verizon phone that has good development. Good luck to me - guess I'll have to sacrifice my unlimited data I've had for many years for a phone with a new carrier so I can root it with good development. I hate Verizon.
Click to expand...
Click to collapse
Unusable how? You just said it booted.
Is your bootloader unlocked? Can you get into bootloader mode? If so, you could try flashing a factory image.
Don't give up so quickly. Your issues might be related to the ROM or something else you installed.
Jeez... Jump to conclusions much? Can we get more info please?
Sent from my Nexus 6P using XDA-Developers Legacy app
darbylonia said:
Well, I maybe should have listened. So I had just flashed a ROM on my 6P, set a few things up, it was charged 98%, I downloaded an app, checked an e-mail, then walked away. Then after 30 minutes I went to the phone to check e-mail, and it was dead. I mean, wouldn't boot in any way complete black screen. Hooked up to computer, nothing. No buttons will boot the device.
So ridiculous....a $500 paper weight. Now I have to find a decent Verizon phone with good development to buy.
Well, had fun for 2 months!
Bye Nexus 6P forums!
Click to expand...
Click to collapse
I almost want to say just send it to me because I could almost guarantee I could help get it booted. If when you plug it in to your computer does the computer recognise it at all? Edl mode? Can you enter bootloader or anything?
Since your 6P is only 2 months old, why not use the warranty?
Sent from my Nexus 6P using Tapatalk
Thanks guys. I was able to revive it again and flashed a different ROM. It would not boot in any way - plugged into my computer, bootloader mode, nothing. Then it went into a bootloop. Finally I got it to boot and flashed an older ROM after transferring the appropriate vendor image to internal from my computer. I'm nervous it will happen again. I will switch to a new ROM now and hopefully won't see this happen again. Very frustrating evening.
darbylonia said:
Thanks guys. I was able to revive it again and flashed a different ROM. It would not boot in any way - plugged into my computer, bootloader mode, nothing. Then it went into a bootloop. Finally I got it to boot and flashed an older ROM after transferring the appropriate vendor image to internal from my computer. I'm nervous it will happen again. I will switch to a new ROM now and hopefully won't see this happen again. Very frustrating evening.
Click to expand...
Click to collapse
i know this is a old post but do you by any chance remember how you got it to boot again. I am having the same problem and after shutdown i was able to turn it on one time by pressing the power button for 30 sec but now it's dead again and wont turn on after long power button press.
RØ35 said:
i know this is a old post but do you by any chance remember how you got it to boot again. I am having the same problem and after shutdown i was able to turn it on one time by pressing the power button for 30 sec but now it's dead again and wont turn on after long power button press.
Click to expand...
Click to collapse
Have you tried volume down and power? Hold it for up to a few minutes...
jaytv said:
Have you tried volume down and power? Hold it for up to a few minutes...
Click to expand...
Click to collapse
did that too. But nothing seems to work.It doesn't even get noticed by pc.
Would you recommend a battery swap.
I remember freaking out when that happened to me. My 6P was dead for like 20 minutes. I kept plugging it in, holding power and volume, etc. I got so mad I banged it against something and created a small dent near the power button, which I lived with for the rest of the year until I bought my OP5T.
Hope you were able to fix it. I kept trying and trying to resuscitate it and finally it booted. :good: