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
Related
Hi,
Last night my Galaxy S was low on battery, and I kept trying to turn it on for it to die right away (it was working as expected I guess)
This morning after I charged my phone it wouldn't turn on at all! It loads to the logo screen, makes that jingle sound and then holds and doesn't turn on.
I can get to recovery and download mode.
I put OCLF on like 2 months ago, but haven't modded/flashed ANYTHING since. It is very bizarre how it just died.
I'm wondering what my options are now. Obviously I would rather not loose all my personal files. Since I can get into download mode, can I just flash a new firmware? I'd like FroYo anyway, but I haven't got a clue what to do.
Great start to the year – !
Cheers,
Mitch
EDIT: I just decided to try the "Clear User Cache" option and then reboot to no avail. Now I can't get back into recovery mode!?!? Download mode still works. Huhh?? Is this expected? Have I lose Recovery Mode entirely now? Crap.
seeeems like an odin flash via the download mode is the only way. There are a few tutorials on this site and even tut vids on youtube so you should be fine if you just follow everything they do (as long as it works for them of course)
How do I know what version to flash? I have read a few tutorials and they all have started with "Dial x and check you have y" etc. Obviously I can't do any of that.
What is the *safest* firmware I can flash?
My phone currently has some optus variety.
Please forgive the noodish question.
Mitch
Where are you located? And who is your provider?
Hi,
I'm in Sydney Australia and my provider is Optus.
Thanks
Hi,
I still can't get my phone working and am not clear how to proceed.
What would be the best firmware to flash to my Optus Galaxy S that bricked out of the blue? Should I just send it back to Samsung?
Thank You
m1tch37 said:
Hi,
I still can't get my phone working and am not clear how to proceed.
What would be the best firmware to flash to my Optus Galaxy S that bricked out of the blue? Should I just send it back to Samsung?
Thank You
Click to expand...
Click to collapse
Hey mate go to samfirmware and get I9000DTJG4 thats the stock optus rom once you get phone up and running then upgrade to 2.2.1.
Sounds like you'll need to do a flash of a stock rom..
By the way, the old oclf had some issues that might lead to system corruption (unfortunately I'm not very sure exactly what it does, or whether it could lead to this problem). I'd suggest getting one of the newer lag fixes available here when you do get your phone running again
tragusman said:
Hey mate go to samfirmware and get I9000DTJG4 thats the stock optus rom once you get phone up and running then upgrade to 2.2.1.
Click to expand...
Click to collapse
tragusman has got it right. Depending on what the issue is, you'll either recover nicely or your phone is toast. Flash the above stock firmware and give it a shot. Note that you'll likely loose your data and settings.
If you're new to flashing firmwares, check the great reference guide on where to find Odin and how to use it (this is the app you'll use to flash the above firmware).
http://forum.xda-developers.com/showthread.php?t=723596
After flashing, try getting into recovery mode. If you can look for an error message under the standard menu. Can't get to d/l mode? You're probably in trouble. Get into recovery and see an error msg? Post the error here or google it for a solution. No error msg? You're probably ok - restart the phone.
Good luck.
Thanks guys.
I'm about to try it now, but before I start potentially breaking my phone even more, I was just thinking: Could I just send it back to Samsung? Would they fix it, or identify right away I have changed something and void my warranty.
Mitch
m1tch37 said:
Thanks guys.
I'm about to try it now, but before I start potentially breaking my phone even more, I was just thinking: Could I just send it back to Samsung? Would they fix it, or identify right away I have changed something and void my warranty.
Mitch
Click to expand...
Click to collapse
If it's broke, you can't break it any more I've sent phones back in for support after flashing back stock firmware (flashing it after it "died").
The story so far...
Bought a new Optimus Black and gave it to my girlfriend for her birthday a couple of days ago. After playing with it for about an hour she put it down, I picked it up and decided to have a tinker. I installed Cyanogen mod 3.5.1 after rooting it with Gingerbreak. So far so good but I didn't really like the look of the ROM and the absence of a Market seemed like hassle so I used ClockworkMod to restore the backed up stock ROM.
It's still working fine but now I see there is an official update from inside the phone. I presume it's the upgrade to Android 2.3 so run it and reboot the phone. That's when it all goes wrong. I'm now stuck in the CWM recovery screen. I try all the options, following any online guides I can find that were supposed to have worked for people. I try restoring the backup, restoring cyanogen, clearing the cache, dalvik, everything but nothing happens and I keep booting back into the CWM recovery screen.
Next day I try the LGUnitedMobileDriver and the phone recovery option but despite trying several times I can get no further. A friend tried to use Odin to restore it but got no success. Finally, we tried restoring with a KDZ file with
KDZ_FW_UPD_EN, Windows Enabler and LG B2CTool and now the phone got stuck in yet another loop - a black screen with 'updating firmware'. The LEDs flash for a minute and it reboots and does the same again.
What's more, the phone will now no longer charge or turn on without being connected to the mains.
What are my options here?
Follow the tutorial given below.
http://forum.xda-developers.com/showthread.php?t=1275315
Thanks, but I've already tried that and it doesn't work. I'm forever stuck in the firmware update screen.
pickarooney said:
Thanks, but I've already tried that and it doesn't work. I'm forever stuck in the firmware update screen.
Click to expand...
Click to collapse
have you tried the CS_EMERGENCY option in R&D TOOLS? Wait I'll find the link..
Here >>> http://forum.xda-developers.com/showpost.php?p=18841596&postcount=8
http://forum.xda-developers.com/showpost.php?p=18740082&postcount=45
The CS_EMERGENCY is the only thing worked, he used a german V10A ROM. If you managed to unbrick it, you can flash it again with your desired KDZ, or use CS_EMERGENCY and flash directly your desired KDZ. TRIAL AND ERROR.
Emergency c-section... nope, I will try that now!
Said that it will get stuck at 4% but it is still flashing. Just wait for the phone to reboot by itself.
It just crashes with a fatal error as soon as it gets to the second tab (downloading) on both PCs I tried it on. I tried several KDZ files with the same result.
Does anyone know if it's possible to physically change the ROM on this phone and if it would be worth trying that before binning the thing?
pickarooney said:
Does anyone know if it's possible to physically change the ROM on this phone and if it would be worth trying that before binning the thing?
Click to expand...
Click to collapse
Does it have warranty? Why not RMA it, I think it has a hardware problem now since you mentioned it doesn't charge anymore. Also, have you tried a different USB cable?
The warranty gets voided as soon as you root or mod a phone and it's probably as expensive to get it fixed outside of warranty as to buy a new one.
pickarooney said:
The warranty gets voided as soon as you root or mod a phone and it's probably as expensive to get it fixed outside of warranty as to buy a new one.
Click to expand...
Click to collapse
Most of the time they change the board right away if it can't boot (as many as I've read) board was changed and none just revived the OS. So they won't know you rooted it. Just specify that they should contact you first before making any changes.
gabwerkz said:
Most of the time they change the board right away if it can't boot (as many as I've read) board was changed and none just revived the OS. So they won't know you rooted it. Just specify that they should contact you first before making any changes.
Click to expand...
Click to collapse
true.. you can just tell them that you received an update and upon getting it the phone wont boot anymore.. just dont tell them that you rooted it or tinkered it in any way.. i'm sure you'll be able to get your warranty that way..
darkzorn said:
true.. you can just tell them that you received an update and upon getting it the phone wont boot anymore.. just dont tell them that you rooted it or tinkered it in any way.. i'm sure you'll be able to get your warranty that way..
Click to expand...
Click to collapse
Well, that's exactly what I did so we'll see in two weeks if I get a fixed phone free of charge
pickarooney said:
Well, that's exactly what I did so we'll see in two weeks if I get a fixed phone free of charge
Click to expand...
Click to collapse
Fingers crossed for you !!!
pickarooney said:
Well, that's exactly what I did so we'll see in two weeks if I get a fixed phone free of charge
Click to expand...
Click to collapse
IT will mostly work..Good luck though and please do reply here and let us know if it worked..
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.
i bricked my phone and i cant do anything i am using samsung galaxy s6 and when phone turns on just samsung logo appears but stays there forever
and i cant go to the recovery mode it is like deleted. Tried to re-root phone thought it could help. Guess not... anyways i need help just got that phone...
I have the exact same issue. Xposed bricked my phone (S7 Edge, SM G935F). My own fault, but I need to fix it asap. Getting phone back tomorrow in factory reset state. My only back-up is TWRP. I managed to create that back-up while the phone was already in bootloop status. Question is if I root again and restore the back-up I created, won't the Xposed being part of that back-up file simply brick my phone again. I can't figure out how to remove xposed from my TWRP back-up so it doesn't cause issues.
Any help would be much appreciated. I am paying $50 to have the phone fix and if I mess it up, it will be another issue.
Nougat or Marshmallow ?
Which firmware, model numbers? Have you tried flashing your preferred firmware via Odin in PC or Mac? List what you've done for us...
mynicknameiscool said:
i bricked my phone and i cant do anything i am using samsung galaxy s6 and when phone turns on just samsung logo appears but stays there forever
and i cant go to the recovery mode it is like deleted. Tried to re-root phone thought it could help. Guess not... anyways i need help just got that phone...
Click to expand...
Click to collapse
You need to put the phone on download mode and refresh the entire firmware. I think Samsung do it via ODIN still.. but not sure.
Hi,
Just received my note 9 and downloaded the latest firmware. Installed via odin. One of the files failed so I redownloaded the file and updated just the AP. I probably should have done all files. It installed fine but i'm now stuck in a boot loop.
I can't get into recovery with ether volume up, bixby and power. I just get a blue screen with an android on its side?
Any tips. Very worried the phone is bricked. Hoping I don't have to wait for the battery to die as that could take a couple of days.
mardon85 said:
Hi,
Just received my note 9 and downloaded the latest firmware. Installed via odin. One of the files failed so I redownloaded the file and updated just the AP. I probably should have done all files. It installed fine but i'm now stuck in a boot loop.
I can't get into recovery with ether volume up, bixby and power. I just get a blue screen with an android on its side?
Any tips. Very worried the phone is bricked. Hoping I don't have to wait for the battery to die as that could take a couple of days.
Click to expand...
Click to collapse
Can you get into download mode?
Nope can't seem to get into ether.
Any tips?
mardon85 said:
Nope can't seem to get into ether.
Any tips?
Click to expand...
Click to collapse
At this point, your only two options are EDL (emergency download mode) which technically requires you to crack op the device and mess with the board inside of the device, or just a warranty replacement if you haven't tripped Knox.
Ok thanks for the info. I was only trying to install the latest stock firmware via odin so i'd hope Knox wasn't tripped.
Interestingly my SM-N9600 doesn't have any serial number on the back. When I took it to samsung to see if they had any special tools they wouldn't touch it because they said it was a refurb phone.
I'm wondering if the refurb is infact not a SM-N9600 which would be why the flashing a new recovery bricked the phone.
mardon85 said:
Ok thanks for the info. I was only trying to install the latest stock firmware via odin so i'd hope Knox wasn't tripped.
Interestingly my SM-N9600 doesn't have any serial number on the back. When I took it to samsung to see if they had any special tools they wouldn't touch it because they said it was a refurb phone.
I'm wondering if the refurb is infact not a SM-N9600 which would be why the flashing a new recovery bricked the phone.
Click to expand...
Click to collapse
Well, that's a crap move by them. I know for sure that they have a proprietary software that can revive pretty much any Samsung phone as long as it's not hard bricked. They could've just flashed it and helped you. I have a friend who works for Samsung and I have seen him use that software at best buy once. I mean, you've spent your own money to use their phone after all. I don't know why it matters if it's just software.