My Note 3 is rooted, and running the stock MJ5 build that came from AT&T. No modifications, except installing Titanium and removing a bunch of the apps I do not use. Eaerlier today I was trying to run the update that came out, and mine failed at 25%. No big deal, I decided to re-install the AT&T bloat that I had removed from my phone, and then try again.
I rebooted my phone, and now it keeps saying "Unfortunately AT&T Ready2Go has stopped" usually this would not be a big deal. But in this case, nothing else works on the phone. If I click OK, it simply tried to run AT&T Ready2Go again and then pops up the same error. I was able to get into settings, and did a factory reset on the phone, but it still does the same thing. I then tried a reset from recovery, still the same thing, and now when I pull down the notifications from the top, my settings button also does nothing.
I can switch off wifi, bluetooth etc, but other than that, and clicking OK on the Ready2Go stopped warning can do nothing at all.
Help!!! Thanks.
Did you unroot before trying to update? You need to at least put SuperSU into survival mode (unrooting it) while the update runs, otherwise it's sure to not go well - which sounds like is what happen.
OTA updates on a phone with a locked bootloader are generally something you should react to with terror, invocations of a higher power, and profanity. Until there's a nice Odin-flashable set of files like there is with MJ5 now, I would never, ever, allow it to update (since you can't downgrade with locked bootloader, no flashable firmware means no way to recover if something goes wrong).
Are you able to get into bootloader mode or recovery mode, or can you get all the version information any other way? (to see what the phone is actually running). We need the versions of all the components to make judgement on your options at this point.
Thanks for the reply, no I did not unroot before trying to update. The initial update did not go well (which I am sure was due to what you suspect happened) at that point since I have only had the phone about a week I essentially decided to try a factory reset as I did not have a whole lot on there. After that I started getting the error with AT&T Ready2Go (what even is this app?).
I can get into recovery with no problems, but I do not see anything in there that shows me the version number. I do know that last I checked before hitting factory reset it was on N900AUCUBMJ5. I have not yet attempted to get into bootloader mode. I have started downloading all the files from here http://forum.xda-developers.com/showthread.php?t=2559715 but on a 1.5MB DSL connection, downloading a 1.9GB file is taking forever. In fact, it just failed, after about 3 hours and 181MB.
Go onto download mode. That will give the info needed.
Fully powered off
Press and hold power, home, vol down.
When the warning screen shows, hit the vol up to continue. That will bring you to where you need to be.
Sent from my SM-N9005A using XDA Premium 4 mobile app
graydiggy said:
Go onto download mode. That will give the info needed.
Fully powered off
Press and hold power, home, vol down.
When the warning screen shows, hit the vol up to continue. That will bring you to where you need to be.
Sent from my SM-N9005A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
OK, here is what it says when in download mode:
ODIN MODE
PRODUCT NAME: SM-900A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S2, T2, A2, A2, P2
WRITE PROTECTION: Enable
And then I have an Android in the middle, and it says Downloading... Do not turn off target!! at the bottom.
Go ahead with that restore back to MJ5. Knox is good and the bootloader version hasn't changed.
Sent from my SM-N9005A using XDA Premium 4 mobile app
graydiggy said:
Go ahead with that restore back to MJ5. Knox is good and the bootloader version hasn't changed.
Sent from my SM-N9005A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks, that's what I suspected I would have to do. Just wish my connection would be a little faster to get my phone back up and running!! Oh well, hopefully if I leave it overnight it will have finished downloading in the morning.
Edit: Downloaded the files overnight, went through the process this morning and now have a working phone again. Very relieved!!
naiku said:
Thanks, that's what I suspected I would have to do. Just wish my connection would be a little faster to get my phone back up and running!! Oh well, hopefully if I leave it overnight it will have finished downloading in the morning.
Edit: Downloaded the files overnight, went through the process this morning and now have a working phone again. Very relieved!!
Click to expand...
Click to collapse
Glad to hear it (As I read down this thread, I was about to give this advice straight from the can't-get-there-from-here department. "1.5 mbit DSL? Eew, just download it using your phone's 4G"...)
DrAzzy said:
"1.5 mbit DSL? Eew, just download it using your phone's 4G"...)
Click to expand...
Click to collapse
Using the 4G would have been ideal, but I get no service at home. I don't just mean no 4G either, I mean no service at all, no EDGE, 3G, nada, zip!
I have a phone Samsung Note 3 that belonged to my boss. I did a factory reset on it and bought a card for At&t gophone, went through the Ready2go process on the phone and completed that. When I enter the number for the phone to add the time it says the number isn't recognized. Any idea's on what I need to do? Please help.
Related
Has anyone had this happen to them? Axura beta 4 was running quirky so i flashed my phone with odin 3 and then did a factory format *2767*3855#
to clear everything that odin did not. Everything nice and new all bloated and what not, thought I would give the samsung update a try "so i could use kies again" then the phone prompted to restart and did so but without the starting back up thing. I tried everything from puling the battery, download mode, recovery mode and cussing furiously at it and it did nothing. What went wrong? Is samsung gonna be able to see if i rooted the phone and all even after I did all the formatting? Before I did the update I checked to see what all was on the phone and it was like out of the box.........
Sickmutt
Happened to me when JH7 just came out. Phone was a paperweight. No power would go to the phone at all.
I exchanged it at the AT&T store...
As for them checking the root - doubt it and you reverted to stock regardless.
dang att sent me to samsung to get my phone fixed instead of helping me. that sucks that my phone gets bricked by a factory update
thanks for the fast response
I cant get my phone to boot past the ATT screen. I screwed up somewhere trying to change from the X-note rom and lost my data connection. Tried changing roms and that just went down hill so they i went to the MJ5 restore steps and now its really screwed up. I can get it to go into download mode and it finished a restore process but then it wont boot up do anyone have a file that i can use or something. Im totally lost now and without an actual MJ5 odin file seems like nothing works. Can anyone point me in the right direction.
redalertlb said:
I cant get my phone to boot past the ATT screen. I screwed up somewhere trying to change from the X-note rom and lost my data connection. Tried changing roms and that just went down hill so they i went to the MJ5 restore steps and now its really screwed up. I can get it to go into download mode and it finished a restore process but then it wont boot up do anyone have a file that i can use or something. Im totally lost now and without an actual MJ5 odin file seems like nothing works. Can anyone point me in the right direction.
Click to expand...
Click to collapse
Odin does not work on MJ5... That is why there are so many threads warning you not to mess with Changing from MJ5 to something else... Or anything based on MJ5... MJ5 has a locked bootsector and there is nothing to unlock it right now meaning it cannot be written over. Once you mess it up, it will stay that way till somebody cracks the boot loader and we can then use any rom... I would just try to hard brick it now and make a warranty claim. If it is hard bricked they cannot test it to see if you have tampered with it...
Solarenemy68 said:
Odin does not work on MJ5... That is why there are so many threads warning you not to mess with Changing from MJ5 to something else... Or anything based on MJ5... MJ5 has a locked bootsector and there is nothing to unlock it right now meaning it cannot be written over. Once you mess it up, it will stay that way till somebody cracks the boot loader and we can then use any rom... I would just try to hard brick it now and make a warranty claim. If it is hard bricked they cannot test it to see if you have tampered with it...
Click to expand...
Click to collapse
Spoke with Samsung and they told me to take my phone to best buy and have a samsung tech look at it because at the moment its stuck in emergency recovery. Does that make it detectable?
Once they get it to boot which they can, they will see the KNOX has tripped and you will be out of a warranty and charged for their work..
Solarenemy68 said:
Once they get it to boot which they can, they will see the KNOX has tripped and you will be out of a warranty and charged for their work..
Click to expand...
Click to collapse
Knox isnt tripped or at least when the emergency recovery screen is up knox still says 0x0
redalertlb said:
I cant get my phone to boot past the ATT screen. I screwed up somewhere trying to change from the X-note rom and lost my data connection. Tried changing roms and that just went down hill so they i went to the MJ5 restore steps and now its really screwed up. I can get it to go into download mode and it finished a restore process but then it wont boot up do anyone have a file that i can use or something. Im totally lost now and without an actual MJ5 odin file seems like nothing works. Can anyone point me in the right direction.
Click to expand...
Click to collapse
Just to be clear, your device is a samsung captivate? what about calling at&t, on another phone of course. you might also try searching the forums.
Paulita1 said:
Just to be clear, your device is a samsung captivate? what about calling at&t, on another phone of course. you might also try searching the forums.
Click to expand...
Click to collapse
No its a Samsung Galaxy Note 3 and im outside my ATT warranty but still under samsung warranty. This is what my screen says when i turn my phone on.
Odin Mode
Product Name: sm-n900a
Current Binary: Samsung Official
System Status: Official
Knox Kernal Lock: 0x0
Knox Warranty Void: 0x0
Qualcomm secureboot: Enable (CSB)
AP SWREV: S2, T2, R2, A2, P2
Write Protection: Enable
Firmware upgrade encountered an issue. Please select recovery mode in kies & try again.
And it stays that way no matter what i do unless i try to manually put it into download mode. Other then that the phone doesnt do anything at all.
So have you tried getting Kies for your PC and using it instead of Odin?? Then use it as the phone is suggesting?
Solarenemy68 said:
So have you tried getting Kies for your PC and using it instead of Odin?? Then use it as the phone is suggesting?
Click to expand...
Click to collapse
Yes i have tried both ways and nothing works. Samsung is telling me that i need to mail them my phone and that they will try and fix it. Which basicly means that i will be without a phone until next year. So now im stuck between should i wait and hopefully a fix will be released or found or should i just send it back and feel naked for some weeks.
This is why you should always keep an old flip phone or older smart phone as a back up. I have an old Sony Ericsson flip as well as an HTC Pure in the event I need to send my Note back for service and not be without a phone. By phone I mean the actual phone. Worse case I can go two weeks with out portable internet.
I would just send it in as it looks like that will take less time then waiting for a bootloader crack..
Ok some how i got the phone to boot back up through odin with various files and it but now i have a bunch forced closes on like the direct pen input and process system isnt responded. And i dont have data...anyone know a way for me to fix the data issue?
Flash this in recovery (either side load or put it on your external sd
http://www.firmware-files.com/download.php?id=2&token=XkOmuTVDz8jO5NFRkaoxVbocRoKoQIeE
Thanks bro got it up and running smoothly now.
Sent from my SAMSUNG-SM-N900A using Tapatalk
I have an AT&T Note 3. I was rooted using the KINGO app, but returned my phone to stock several weeks ago and the rom shows official and the knox count is 0. I am running the stock AT&T Note 3 Android 4.3
The other day, an official AT&T android update was pushed to my phone. The update bricked my phone and now I am unsure if I can even recover what was on my phone...or at the very least get it running again. For now, I am without a phone.
When I can get the phone to power up, the phone attempts to "Recovery Booting" (this is displayed in blue letters in the top left corner with the galaxy Note 3 Logo in the middle). It tries to install this AT&T update following the recovery wording when powering it on normally and when using Volume UP/Home/Power . The update progresses towards 100% then "completes" sometimes, but then the screen goes black and the phone does not start back up. I have to remove the battery for a period of time and replace to get the phone to do anything
I can get the phone to go into download mode (Volume down/Home/power), but my phone did not have USB debugging turned on the last time I was able to access the options, so it is not recognized by kies/odin, etc!
Even though their update caused the problem, AT&T wont help me (over the phone or at the store) as my phone is over a year old...their solution is to buy a new phone and plan as they say they can't do anything to fix the phone.
ANY HELP WOULD BE GREATLY APPRECIATED!
Can you get into recovery?..if so try to factory reset then maby you will be able to power up get to developer options and turn on debug so you can use odin...other option..I have heard of some doing this..go to Bestbuy Samsung counter..ask them if they have the odin tool. If they do they may be able to get you up and running.
FIREKAT V11/S5-V1
Don't worry bro.
Just follow this post to put your phone back to stock and get it rooted again. My phone used to brick and I went through it.
Follow the steps carefully, and you'll get your phone back.
http://forum.xda-developers.com/showthread.php?t=2559715
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
So, I have a Galaxy note 3 G900A. Not sure what version and I don't have access to that. So, it has the Alliance rom installed on it. It was working fine for months with absolutely no problems. Then all of a sudden, earlier, it said NFC has stopped working, over and over again. Then, I turned off the phone and it failed to turn on. It will not get past the splash screen. It just wants to stay dark and if I leave it alone long enough, it automatically goes into recovery mode. I can get into recovery mode and download mode normally. I already tried factory reset and all of that. None of my computers will recognize the phone and I have tried multiple cables as well. Odin won't recognize it and neither will samsung kies. I tried installing stock rom through SD card and it says
Verifying update package:
E:Footer is Wrong
E: Signature Verification Failed.
It does that no matter what rom I try to install. I can't afford to get another phone right now and it is the only one I have and I just don't know what else I can do. Any help is greatly appreciated.
Well to start backwards, the stock recovery isn't really meant to flash zips, but it should go farther than saying Footer Is Wrong
Signature Verification has failed. For me, it says that, then if you wait a few seconds, it'll say a few other things, then install from sd card complete and it wipes data and cache then reboots. Next, you have to use an official cable for that, Media Transfer doesn't work correctly without oem cable
Sent from my SM-N9005 using Tapatalk
Have you tried reinstalling the drivers on your pc or tried a different pc?
spookykidmm said:
Well to start backwards, the stock recovery isn't really meant to flash zips, but it should go farther than saying Footer Is Wrong
Signature Verification has failed. For me, it says that, then if you wait a few seconds, it'll say a few other things, then install from sd card complete and it wipes data and cache then reboots. Next, you have to use an official cable for that, Media Transfer doesn't work correctly without oem cable
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
I do use an oem cable. Same thing. The rest of what you said does happen though.
dustincrock said:
I do use an oem cable. Same thing. The rest of what you said does happen though.
Click to expand...
Click to collapse
The cord is funky sometimes. Try to "mangle" it a little bit to see if odin will say "Added!". I know I have to basically wrap mine around the computer to get it to work correctly
Sent from my SM-N9005 using Tapatalk
sparx said:
Have you tried reinstalling the drivers on your pc or tried a different pc?
Click to expand...
Click to collapse
Yes I have. Still the same problems.
dustincrock said:
Yes I have. Still the same problems.
Click to expand...
Click to collapse
Any luck?
Sent from my SM-N9005 using Tapatalk
spookykidmm said:
Any luck?
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
No. No luck..
A Last Resort
dustincrock said:
So, I have a Galaxy note 3 G900A. Not sure what version and I don't have access to that. So, it has the Alliance rom installed on it. It was working fine for months with absolutely no problems. Then all of a sudden, earlier, it said NFC has stopped working, over and over again. Then, I turned off the phone and it failed to turn on. It will not get past the splash screen. It just wants to stay dark and if I leave it alone long enough, it automatically goes into recovery mode. I can get into recovery mode and download mode normally. I already tried factory reset and all of that. None of my computers will recognize the phone and I have tried multiple cables as well. Odin won't recognize it and neither will samsung kies. I tried installing stock rom through SD card and it says
Verifying update package:
E:Footer is Wrong
E: Signature Verification Failed.
It does that no matter what rom I try to install. I can't afford to get another phone right now and it is the only one I have and I just don't know what else I can do. Any help is greatly appreciated.
Click to expand...
Click to collapse
As a last resort, put the device into download mode and connect to KIES 3. Go to tools and do a complete reinstallation. This will return you device to full factory specs and latest approved software, no custom ROM, no root, and no saved data. But at least you will have a functioning device. As soon as possible look into getting a new battery.
zancro said:
As a last resort, put the device into download mode and connect to KIES 3. Go to tools and do a complete reinstallation. This will return you device to full factory specs and latest approved software, no custom ROM, no root, and no saved data. But at least you will have a functioning device. As soon as possible look into getting a new battery.
Click to expand...
Click to collapse
I even used different batteries. And kid won't work because the phone isn't detected by the computer as being a phone. Kies doesn't pick up the phone, even in download mode
dustincrock said:
I even used different batteries. And kid won't work because the phone isn't detected by the computer as being a phone. Kies doesn't pick up the phone, even in download mode
Click to expand...
Click to collapse
Your only remaining option might be to send your device away for professional help. In the past I have used the services of Josh at: http://mobiletechvideos.com/ . (I am not related to that organization in any way.) For around $50.00 they can do a complete refresh, and in my case offered to root and load the custom ROM of my choice for a small additional fee. It took about one week.
Good luck.
G900A?
zancro said:
Your only remaining option might be to send your device away for professional help. In the past I have used the services of Josh at: http://mobiletechvideos.com/ . (I am not related to that organization in any way.) For around $50.00 they can do a complete refresh, and in my case offered to root and load the custom ROM of my choice for a small additional fee. It took about one week.
Good luck.
Click to expand...
Click to collapse
I checked back to see if you had solved the problem and noticed something I missed earlier... Your OP says you are using a G900A. Are you referencing a Note 3 or some other device?