Related
Hi all, I'm a normal XDA user with my HTC hero.
My girlfriend recently bought the Rogers Samsung Captivate, and had a few issues with it. First the battery life was only lasting half the day. Then one day, it restarted itself 5 times. Then it seemed like it was laggy. At first when she told me about the battery issue I thought, ok maybe if we put a custom ROM on, it may help. So I rooted, put clockwork recovery, then installed Assonance ROM. We seemed to have gotten rid of the lag but the random restarts seemed to persist, then she was having Sms's coming in weird, so I decided we should put it back to stock and get it back to rogers. So i tried doing a restore from clockwork, but it still has the AT&T logo, and when the phone boots, I have a black screen that says no service on the top right, and swipe screen to unlock, but it won't unlock.
All I want is this thing back to stock, no AT&T screen so I can try to warranty this thing.
Thanks in advance for any help, I've done some searching and can't seem to get this thing back to life.
Thanks,
AZ
AbsoluteZero said:
Hi all, I'm a normal XDA user with my HTC hero.
My girlfriend recently bought the Rogers Samsung Captivate, and had a few issues with it. First the battery life was only lasting half the day. Then one day, it restarted itself 5 times. Then it seemed like it was laggy. At first when she told me about the battery issue I thought, ok maybe if we put a custom ROM on, it may help. So I rooted, put clockwork recovery, then installed Assonance ROM. We seemed to have gotten rid of the lag but the random restarts seemed to persist, then she was having Sms's coming in weird, so I decided we should put it back to stock and get it back to rogers. So i tried doing a restore from clockwork, but it still has the AT&T logo, and when the phone boots, I have a black screen that says no service on the top right, and swipe screen to unlock, but it won't unlock.
All I want is this thing back to stock, no AT&T screen so I can try to warranty this thing.
Thanks in advance for any help, I've done some searching and can't seem to get this thing back to life.
Thanks,
AZ
Click to expand...
Click to collapse
Go here....http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/SGH-I896
Scroll down and you will see a link to the stock Roger's ROM.
Microwave...15 seconds...you don't want to overcook
I have that, i'm trying to install it, but it's taking a long time to start installing update. I've tried reformatting everything, I've tried renaming the Rogers stock to update.zip.
any thoughts on how long it should take to install, or any better instructions on how to get back to stock?
Still stuck at installing update after 15 minutes.
also, is there go instructions on how to get rid of the AT&T Logo, or will the stock rom/firmware fix that?
Ok So, I unzipped the stock firmware and it seems to have installed, but I still get the AT&T logo, and I'm still frozen at the swipe screen to unlock section. I can't swipe at all or do anything for some reason.
AbsoluteZero said:
Ok So, I unzipped the stock firmware and it seems to have installed, but I still get the AT&T logo, and I'm still frozen at the swipe screen to unlock section. I can't swipe at all or do anything for some reason.
Click to expand...
Click to collapse
I'd just like to post that I had this exact same issue when I tried to restore to my original ROM Manager backup, and a solution would benefit both of us.
Auridran said:
I'd just like to post that I had this exact same issue when I tried to restore to my original ROM Manager backup, and a solution would benefit both of us.
Click to expand...
Click to collapse
Did you end up being able to boot ok somehow?
AbsoluteZero said:
Did you end up being able to boot ok somehow?
Click to expand...
Click to collapse
Nope. I'd always be stuck at that black lock screen unable to unlock. After one erase and restore there was a background image instead of blackness, but it didn't go any further. I just decided to stick with Assonance, but that's not really an option for you unfortunately.
so I was wrong right from the beginning, I didn't flash Assonance, i flashed Cognitionv2.3b8. Sorry for the confusion
I clipped this from the above link to the rogers stock rom.
"Be aware when installing AT&T Firmware 2.2 and trying to recover to Rogers stock, you will have a short AT&T display on boot up. One way to remove this is to flash the phone with firmware from a Samsung I9000 model and then reflash it with the Rogers Firmware. This will remove the AT&T logo. However, there is a chance that this method may, in certain circumstances, leave a seemingly random pixlation on screen upon boot-up for the time the AT&T logo was meant to be displayed. A very minor issue and doesn't affect the phone or boot process"
So try to find a stock I9000 rom I guess. The assonance rom is based off the I9000(Or at least that what it says on boot :/). I'm not sure if that will be good enough. I'm running Assonance right now on my fiance's rogers captivate. It's been working great since she has gotten it. So maybe even just flashing Assonance will fix things for you.
As a side note, I returned my x10 with a custom rom on it for warranty and I never heard from them. My understanding(hearsay) is that it doesn't even go to rogers. I'm in Ontario, and I believe it goes to a refurbishing company that is contracted by rogers where they check for water damage.
So I'm not sure where you are located but it may be the same.
(Disclaimer: I'm not saying you WONT get billed for the phone if you send it back with custom rom on it.. I'm simply saying that I didn't and I have heard of others not being as well. Perhaps we were just lucky)
Good Luck.
If you try this let me know if it works, should I ever need to send hers in for warranty.
check your pm
I recently bought this Nexus off eBay and it worked fine.
Owner said it had problems with the SD card, but it seemed to be working, for they said it wouldnt read, when it does.
Anyway, it had cyanogen mod 6.1.1 on it, and I hate the setup...so i changed roms. That was a success, but when i flashed a sense rom thru clockwork(most updated) it said:
E:Error in /sdcard/N1Sensation_v0.4.zip
(Status 0)
Installation aborted.
Now, when i flash any roms, whether it says it installed correctly, it doesnt change anything. Now it's stuck at the 4 color x with the unlock icon. Any advice is good advice!
In my hboot, it says:
*** UNLOCKED ***
NEXUSONE PVT SHIP S-ON
HBOOT-0.35.0017
MICROP-0b15
TOUCH PANAL-SYNT0103
RADIO-5.00.00.04
Oct 12 2010, 14:33:16
HBOOT
Etc. Etc. Etc.
Thanks for any help!
Edit: I fixed the issue with why it failed, was my fault, didnt partition the card...but i was flashing a stock rom and it said complete and when i rebooted it stayed at the X and then powered off. Since then has never turned on. I don't know what to do. Nothing will turn it back on. I have a universal charger that charges the battery and it said the battery is full. I need help!
Ok lets see here try this plug in the charger then pull the battery place it back in wait a few seconds and repeat until you see the splash screen (the static X). This could get the phone to at least boot.
But just to check did you flash a radio in all that stuff??
Dude Random21 said:
Ok lets see here try this plug in the charger then pull the battery place it back in wait a few seconds and repeat until you see the splash screen (the static X). This could get the phone to at least boot.
But just to check did you flash a radio in all that stuff??
Click to expand...
Click to collapse
That did not work. I work at a cellphone repair store, but im yet to open it up. But i flashed a sensation rom...
http://forum.xda-developers.com/showthread.php?t=1083035
After then i got stuck on the X
Then i used... well i cant find the link, but it's PureGoogleMod.
From what I saw, there was no radio or kernal being flashed. I just know i flashed a rom, it said completed, then went to the X, rebooted, but never turned on. And ive tried other batteries.
matistight said:
That did not work. I work at a cellphone repair store, but im yet to open it up. But i flashed a sensation rom...
http://forum.xda-developers.com/showthread.php?t=1083035
After then i got stuck on the X
Then i used... well i cant find the link, but it's PureGoogleMod.
From what I saw, there was no radio or kernal being flashed. I just know i flashed a rom, it said completed, then went to the X, rebooted, but never turned on. And ive tried other batteries.
Click to expand...
Click to collapse
Try flashing CM7. Also...before you do...you may want to search for a format.zip from a member named temasek. It'll wipe your phone...clean. Real clean. Then flash CM7. try that.
also....those sense roms sometimes take at least 5 minutes to boot. Sometimes it'll stay on the X screen for 5 minutes or it'll stay on the bootanimation screen for 5 minutes. FYI.
SiNJiN76 said:
Try flashing CM7.
those sense roms sometimes take at least 5 minutes to boot. Sometimes it'll stay on the X screen for 5 minutes or it'll stay on the bootanimation screen for 5 minutes. FYI.
Click to expand...
Click to collapse
I can't flash anything. Phone wont react to anything anymore. Hoping one of my family members can fix it. But if I get it on I will try that.
I am pretty sure i waited long enough, but who knows. I didn't partition my card, which may have been the problem. And also it was S-On....which i thought was odd when it had a custom firmware.
Unlock bootloader. Flash recovery. Boot into recovery. Wipe everything. Flash rom.
Why do you guys keep suggesting software stuff when it's probably a hardware problem he can't get the phone to boot up so he can't do any of that.
Although there is one thing I want you to try before your family take a crack at it to take it apart and what not, it's a long shot but it's your last chance if it's software. Hold down trackball and press power keep holding trackball for another 5-10 seconds (better to long then to short) then connect it to the computer via USB you could see a popup notification saying that it's looking for driver software if you do then it's software and we need to reflash everything and might need to unlock the bootloader. Now if you don't see a popup notification I would still go check in the device manager and check for an unidentified device probably in other (it should be extracted so that you can see it).
If this doesn't work then sorry but I think it's a brick
Because in order to find out if its truly a hardware problem you need to try every software fix first.
Op mentioned nothing of trying fastboot as well. Software fix is free hw is not. That is why we suggest software fixes.
Sent from my Nexus S using XDA App
Let me remind you guys, THE PHONE WONT TURN ON AT ALL REGARDLESS OF WHAT I DO. I can post a YouTube video to show everything. It'd be very random for it to be hardware because it just turned off and will not turn back on. If there is any software like an RUU out there, that would help, if not, ill have to buy a bottom piece and warranty it out. But I'd feel bad because that isn't the right thing to do.
I don't expect you guys to fix it and I and very thankful of your help! But the phone won't turn on at all. So telling me to flash roms doesn't work. Imagine it as flashing a rom with the battery out of your phone. I am wondering if there's an adb way or something to get it to turn on and restore to stock?
With all that said, any help is amazing help and I am very grateful that this isn't a post I have to bump! Thank you so much, when I go on the PC, ill thank the helpful posts
Sent from my (finally) permanent root Sensation 4G
Then it is a brick if it won't turn on at all. The entire getting stuck at the x thing confused me to think it was powering on.
You have me confused sir, I'm not quite sure what good it is your looking for a RUU for. If the phone truly won't turn on/go past the X screen and you have it on a charger with no LED notification, then the phone is bricked. When you said you flashed a Sensation rom, I truly hope you just meant a Sense rom. If you can still get to the bootloader screen then you are not bricked and should retry everything from scratch.
Thread Closed
xsnipuhx said:
When you said you flashed a Sensation rom, I truly hope you just meant a Sense rom.
Click to expand...
Click to collapse
Sensation based, but it was a Sense rom
Confirmed it is bricked.
Sold on eBay for $100
Bought for $77
Semi-Winning.
Thread Closed
I was attempting to flash the ICS4 ROM. I had formatted /system and was done with installing the from from zip. Before I could do anything else, the phone just stopped being responsive. I pulled and restored the battery but the phone will not boot up. What to do now, short of going to my VZW store?
When you say it doesnt boot.. what exactly do you mean? Does anything come up on the screen?
nothing comes when you press the power button, screen remains blank.
ronaldheld said:
nothing comes when you press the power button, screen remains blank.
Click to expand...
Click to collapse
Did you try booting up into recovery and then going to fastboot and reinstalling the stock fxz file to see if that fixed it?
Sure the battery didn't die also?
The phone does not boot into recovery. Pressing the power button does nothing at all, as far as I can see.
I found out that the phone is literally fried. Whether the ICS4 ROM contributed is unknown.
You are most likely covered under manufacturer warranty - seems like a hardware failure. Never known of a ROM flash to fry a phone's board.
They also most likely won't know you even tried to flash a custom ROM.
That part is very good to know.
I will have restart again with rooting, and proceed with flashing Eclipse 2.2.
Is the place you live in very statically charged? When you touch metal do you get shocked alot?
If you touched the battery ports it could have discharged into the phones board and killed it.
Let us know what they do for you.
ronaldheld said:
That part is very good to know.
I will have restart again with rooting, and proceed with flashing Eclipse 2.2.
Click to expand...
Click to collapse
Compared to everything else we do here at XDA, the process to get rooted and flash a ROM is very basic. Getting the phone back up and running is the more difficult part.
What I can say to try is attempt to use a different battery. I had a problem once where both of my batteries functioned properly because I was able to test them in other phones. But when I placed that specific battery into my phone, it wouldn't boot up. I ended up using a different battery and was then able to boot into AP Fastboot and fxz to fix it. Then my "dysfunctional" battery worked properly again.
I have had my Sm-N910T for about a year now. When I first got it I rooted it without thinking it through. I used Odin and flashed cf autoroot. I unrooted it when it started giving me issues. Then it would restart, freeze, etc. I now have an app called wakelock and it prevents my phone from turning off. It works great it has the original firmware that installed through Samsung kies but when I try to restart it just shuts down. When I power off I can't always power back on right away. I have to pull the battery and hold the power button for 1 minutes release, then put the battery back in and it works again. I have put the original firmware and it is not rooted anymore. Is there any way I can fix this issue? So basically it works fine but if I turn it off I have to pull the battery to be able to turn it back on. Every once and awhile it'll go into download mode on its own too.
Enalay527 said:
I have had my Sm-N910T for about a year now. When I first got it I rooted it without thinking it through. I used Odin and flashed cf autoroot. I unrooted it when it started giving me issues. Then it would restart, freeze, etc. I now have an app called wakelock and it prevents my phone from turning off. It works great it has the original firmware that installed through Samsung kies but when I try to restart it just shuts down. When I power off I can't always power back on right away. I have to pull the battery and hold the power button for 1 minutes release, then put the battery back in and it works again. I have put the original firmware and it is not rooted anymore. Is there any way I can fix this issue? So basically it works fine but if I turn it off I have to pull the battery to be able to turn it back on. Every once and awhile it'll go into download mode on its own too.
Click to expand...
Click to collapse
Hi,
I have reported this thread to be moved to the right Q & A section where you might be able to get help quickly.
-Vatsal
Enalay527 said:
I have had my Sm-N910T for about a year now. When I first got it I rooted it without thinking it through. I used Odin and flashed cf autoroot. I unrooted it when it started giving me issues. Then it would restart, freeze, etc. I now have an app called wakelock and it prevents my phone from turning off. It works great it has the original firmware that installed through Samsung kies but when I try to restart it just shuts down. When I power off I can't always power back on right away. I have to pull the battery and hold the power button for 1 minutes release, then put the battery back in and it works again. I have put the original firmware and it is not rooted anymore. Is there any way I can fix this issue? So basically it works fine but if I turn it off I have to pull the battery to be able to turn it back on. Every once and awhile it'll go into download mode on its own too.
Click to expand...
Click to collapse
sounds like the same software issue I had. Idk what happened but the internal memory failed on my note 4. Have you experienced constant freeze ups? also have you gone into download mode with an error that says "mmc_failed can't boot"? It was something along the lines of that.
Re:
alfadog77 said:
sounds like the same software issue I had. Idk what happened but the internal memory failed on my note 4. Have you experienced constant freeze ups? also have you gone into download mode with an error that says "mmc_failed can't boot"? It was something along the lines of that.
Click to expand...
Click to collapse
Yes I have those same issues. I am getting a new phone but I have to give this one to someone else and I need it in good shape to give it to them. Do I need to just buy a replacement or is there any way I can get it fixed?
Enalay527 said:
Yes I have those same issues. I am getting a new phone but I have to give this one to someone else and I need it in good shape to give it to them. Do I need to just buy a replacement or is there any way I can get it fixed?
Click to expand...
Click to collapse
Have you tried to update to the latest firmware? DOK2 fixes a lot of issues including the memory leak.
Sent from my SM-N910T using Tapatalk
aaldiar said:
Have you tried to update to the latest firmware? DOK2 fixes a lot of issues including the memory leak.
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
I updated it ota then on Samsung kies with the latest firmware. Everything works fine except the power off issues.
I think this is a common 5.0.1 issue, same thing started happening to me after update. Gotta wait for update or back to 4.4.4.
Enalay527 said:
I have had my Sm-N910T for about a year now. When I first got it I rooted it without thinking it through. I used Odin and flashed cf autoroot. I unrooted it when it started giving me issues. Then it would restart, freeze, etc. I now have an app called wakelock and it prevents my phone from turning off. It works great it has the original firmware that installed through Samsung kies but when I try to restart it just shuts down. When I power off I can't always power back on right away. I have to pull the battery and hold the power button for 1 minutes release, then put the battery back in and it works again. I have put the original firmware and it is not rooted anymore. Is there any way I can fix this issue? So basically it works fine but if I turn it off I have to pull the battery to be able to turn it back on. Every once and awhile it'll go into download mode on its own too.
Click to expand...
Click to collapse
I would recommend downloading the full DOK2 firmware. You can find it in the below linked thread. Make sure you use the newest version of ODIN to flash it 3.10.7.
It should give the phone aq complete clean install of the firmware. Kies sometimes can be janky. It you are going to get rid of the phone the best is to do a full ODIN flash.
http://forum.xda-developers.com/note-4-tmobile/development/mirror-stock-tw-t3260858
I been having the same issues ...even with full firmware flashed DOK2....I get internal memory failure. Hope someone finds a fix. Have to pull out battery, sim cards, and spen, then press all the buttons, thennnnn....put everything back to boot up. Power button won't work, and reboot won't reboot. It Just turns off. Sucks...I love this phone. Right now it's acting ok...occasionally I get freezes and major lag. Someone please help!
notufatjesus said:
I been having the same issues ...even with full firmware flashed DOK2....I get internal memory failure. Hope someone finds a fix. Have to pull out battery, sim cards, and spen, then press all the buttons, thennnnn....put everything back to boot up. Power button won't work, and reboot won't reboot. It Just turns off. Sucks...I love this phone. Right now it's acting ok...occasionally I get freezes and major lag. Someone please help!
Click to expand...
Click to collapse
I had this problem too except it got really really laggy and would constantly reboot anytime I tried to do anything. Best I could figure out was it was a problem with the internal sd. Called TMO tech support, told them I did factory reset, tried it without the sd card, blah blah blah. I said it's a hardware issue that is beyond my control and I don't feel like I should have to pay for it. They said well it sounds like you already did the work for us. I guess it was still under warranty but I got a new phone the next day and no problems since. Hopefully whatever was wrong they have fixed the issue by now but so far so good.
Definitely mention the mmc read fail error or whatever it says. All it cost me was a $5 charge. Give em a call.
I have the same problem, and it only happen when I update the phone to newest firwame, DOK2.
When I use COG1 firwame it very fast and easy use. but when I update DOK2 over Odin, I few very lag and usually restart the phone when I run a big application, then It can't restart after, just turn off.
And after that, can't turn on the phone. I had remove pin in 10s, pull in and it power on normal.
Sometime I turn on the power and the phone go into download mode with notice "mmc_fail can't boot".
Now I just only want to download my phone to old firwame, COG2 and use it normal, but the new firwame with new bootloader don't allow to download old bootloader. So sad
anyone can't show me how to download to COG2 firwame, Please....
tony yayo said:
I had this problem too except it got really really laggy and would constantly reboot anytime I tried to do anything. Best I could figure out was it was a problem with the internal sd. Called TMO tech support, told them I did factory reset, tried it without the sd card, blah blah blah. I said it's a hardware issue that is beyond my control and I don't feel like I should have to pay for it. They said well it sounds like you already did the work for us. I guess it was still under warranty but I got a new phone the next day and no problems since. Hopefully whatever was wrong they have fixed the issue by now but so far so good.
Definitely mention the mmc read fail error or whatever it says. All it cost me was a $5 charge. Give em a call.
Click to expand...
Click to collapse
Hello there, I'm having the same exact issue lately, phone is a Year old, and I think its failing, One question though!
Was your phone ever rooted? mine is, but I flashed the Stock DOK2, so its official with NO root now, but I think the Device status is CUSTOM not official, Also KNOX has tripped while rooting, would T Mobile honor a replacement? At least its on the Official OS with NO Root now.
Please enlighten me
Willy318is said:
Hello there, I'm having the same exact issue lately, phone is a Year old, and I think its failing, One question though!
Was your phone ever rooted? mine is, but I flashed the Stock DOK2, so its official with NO root now, but I think the Device status is CUSTOM not official, Also KNOX has tripped while rooting, would T Mobile honor a replacement? At least its on the Official OS with NO Root now.
Please enlighten me
Click to expand...
Click to collapse
Not really sure. Mine was never rooted. I've heard of plenty of people sending their rooted phones in with no problem.
thiennvbk said:
I have the same problem, and it only happen when I update the phone to newest firwame, DOK2.
When I use COG1 firwame it very fast and easy use. but when I update DOK2 over Odin, I few very lag and usually restart the phone when I run a big application, then It can't restart after, just turn off.
And after that, can't turn on the phone. I had remove pin in 10s, pull in and it power on normal.
Sometime I turn on the power and the phone go into download mode with notice "mmc_fail can't boot".
Now I just only want to download my phone to old firwame, COG2 and use it normal, but the new firwame with new bootloader don't allow to download old bootloader. So sad
anyone can't show me how to download to COG2 firwame, Please....
Click to expand...
Click to collapse
Make sure you are using the ODIN version 3.10.7 if you are using an older version of may be what caused the issue.
If you did use the newest Odin, then I would factory reset your device, but into twrp and wipe everything but external SD Card, boot back into download mode and flash the firmware again. Most likely a few files for messed up during your Odin flash and it messed up the process. Also make sure you are using the USB cord that came with the device.
I found the fix for this mmc_failed. Making a new thread for this.
---------- Post added at 06:11 AM ---------- Previous post was at 05:38 AM ----------
http://forum.xda-developers.com/showthread.php?t=3277144
Here's is the fix. Don't forget to hit Thanks button
(While I was in a rooted DOK2 FW - Tmobile SM-910T3)
So heres the deal, trying to walk around I wanted to mock my location but was interrupted and placed my phone in my pocket which "locked" the bootload.
I managed to flash the stock image and unlocked the bootloader loaded TWRP and restored from my backup
Now this is where hell starts. It looked fine until I rebooted my phone.
Symptoms:
On a reboot the phone will not turn back on after I opt to reboot my phone
At this time the phone will not turn back on (i noticed this when i rebooted while plugged in the charging light was not on) I pull the battery for a few minutes to turn it back on
When I power the device back on sometimes it is stuck in the Bootloader Screen (unable to get into recovery and download) so I need to pull battery wait and turn back on
When the device does boot I can get into recovery and download mode on when it boots properly
Sometimes its stuck on the tmobile screen and I need to reboot it.
When the phone is operational it will occasionally lock up and I will need to wait a few minutes before the device is able to respond.
Any ideas what I can do? I had thought flashing a stock rom (from sammobile) would fix the boot issues
As of now:
I've recently flashed to the new Tmobile marshmallow stock via odin. I am still seeing these symptons. I'm currently installing the Maximum Overdrive Rom hoping it will fix some issues
Still seeing some of the same issues. Stock romantic and a deflated romantic did nothing. Is there a way to reflash a bootloader?
I'm having the same issues....I have odined back to stock dok2 twice....I think the pe3 bootloader files are floating around the forums somewhere...http://forum.xda-developers.com/showpost.php?p=67514260&postcount=4
When my N4 boots up I occasionally get the emmc boot error...I brought it to tmobile and explained the issue to the rep. She brushed it off as being my battery. I know its not my battery as its a 3 month old 10000mah zerolemon. So I'm going to just limp this phone along until its time to jump to the Note 7. I've been flashing roms since the golden era of windows mobile/palm os days and on android since my G1...And some rookie rep who doesn't even know how to put a phone in recovery or download mode tries to brush it off as the battery.... My girl has the sprint note 4 and hers did the same thing, she took it to a store the rep ended up giving her a fully functional refurb... (which is the right thing to do if the phone has emmc failures) Anyways I hope you have better luck than I've had
i had the exact same issue as you guys started 2 months ago got worse overtime now my emmc is dead it wont write anything or even go into recovery or download i had tried all types of roms stock firmwares even took the phone apart swapped the power button and bought a new battery now my memory is dead and i can actually say its the emmc chip, seems to me these note 4s are starting to die i bought mine when it first came out in 2014 kind of feel ripped off but best phone i ever had imo