So, I've tried literally every video, or walkthrough I could find via youtube or this site and I am still stuck in a boot loop right now at the unlock custom screen.
I've tried using odin to go back to stock completely, i've tried the battery removal / wipe data etc option, I don't know what else to do here.
If anyone could help, I'd really appreciate it. At this point I'm pretty desperate.
Which firmware version are you on? What were you doing when it bricked (flashing a ROM, rooting, etc)? Am I correct in assuming you're rooted because of the custom padlock icon?
Have you tried giving it a few minutes to boot up before pulling the battery? I thought my phone was bricked once, but all it needed was ~5 minutes to get going. Give it a good 10 minutes or so to boot up. If that doesn't work, report back with the information I requested and we'll go from there.
Face_Plant said:
Which firmware version are you on? What were you doing when it bricked (flashing a ROM, rooting, etc)? Am I correct in assuming you're rooted because of the custom splash screen?
Click to expand...
Click to collapse
MJ5 ... flashing FireNote Rom
Problem I was having is I was using KnoxRaid Rom, well that rom is dead / thread locked so I figured I would try FireNote. When I rebooted to flash FireNote, I noticed Safestrap wasn't there anymore. I tried re-installing Safestrap a few times with no luck. After a factory wipe / reset, Safestrap magically re-appeared and was available for me to use. I figured what the hell, I'll flash FireNote. When I did, I noticed it was more or less a hodge-podge of the two Rom's and not a clean install. When I did the wipe again to re-install FireNote, I'm now stuck at the spash screen and have been since early this morning.
And yea, I've given it quite some time ... 10+ minutes, even an hour. Nothing.
daigled said:
And yea, I've given it quite some time ... 10+ minutes, even an hour. Nothing.
Click to expand...
Click to collapse
try mj5 restore, if that fails just call AT&T and they will send you a new one free in the mail (takes about a week though)
BeastSpencer said:
try mj5 restore, if that fails just call AT&T and they will send you a new one free in the mail (takes about a week though)
Click to expand...
Click to collapse
I tried MJ5 restore. Maybe there's a different method I can try that you can point me to directly?
Were you on the Jellybean or KitKat version of Knoxraid? If you were on the KitKat version then the problem sounds like you tried to flash a JB ROM on top of a KK ROM without reverting back to JB first. Have you tried the MJ5 restore yet? I believe the thread is in the general section. I'll grab the link for you in a minute.
Edit- here's the link: http://forum.xda-developers.com/showthread.php?t=2559715
daigled said:
I tried MJ5 restore. Maybe there's a different method I can try that you can point me to directly?
Click to expand...
Click to collapse
really? are you sure you followed all steps? what happened when you finished? worked for my brick
Face_Plant said:
Were you on the Jellybean or KitKat version of Knoxraid? If you were on the KitKat version then the problem sounds like you tried to flash a JB ROM on top of a KK ROM without reverting back to JB first. Have you tried the MJ5 restore yet? I believe the thread is in the general section. I'll grab the link for you in a minute.
Click to expand...
Click to collapse
I think you're right. I was on the KK version and FireNote is on JB.
daigled said:
I think you're right. I was on the KK version and FireNote is on JB.
Click to expand...
Click to collapse
bad idea :/
BeastSpencer said:
really? are you sure you followed all steps? what happened when you finished? worked for my brick
Click to expand...
Click to collapse
Yea, definitely followed all the steps ... haven't moved from my computer chair for the last 6hrs lol. Only thing it did when I was finished is to go back to the splash screen and sit there.
Looks like Beast beat me to mentioning the MJ5 restore Check out the link I posted. Make sure you follow all of the steps EXACTLY how they're posted and you should be able to get going again.
daigled said:
Yea, definitely followed all the steps ... haven't moved from my computer chair for the last 6hrs lol. Only thing it did when I was finished is to go back to the splash screen and sit there.
Click to expand...
Click to collapse
as a last resort, you can call at&t i guess :/
try flashing MJ5 images from sammobile.com in odin
Face_Plant said:
Looks like Beast beat me to mentioning the MJ5 restore Check out the link I posted. Make sure you follow all of the steps EXACTLY how they're posted and you should be able to get going again.
Click to expand...
Click to collapse
I found that thread, followed it EXACTLY and still am having the same outcome =/
Maybe some of the files are corrupt. Try uninstalling Heimdall, the Microsoft plugins, delete everything you downloaded (Odin, the .tar files, etc), and redownload them and try again. On top of that, I would delete all of your USB drives and have Windows reinstall them or download them from Samsung's website. That way you will start nice and fresh and hopefully get out of this mess.
Face_Plant said:
Maybe some of the files are corrupt. Try uninstalling Heimdall, the Microsoft plugins, delete everything you downloaded (Odin, the .tar files, etc), and redownload them and try again. On top of that, I would delete all of your USB drives and have Windows reinstall them or download them from Samsung's website. That way you will start nice and fresh and hopefully get out of this mess.
Click to expand...
Click to collapse
Ok, I'll try that next... Thanks bro, i'll check back in after and let you know.
No problem. Let me know how it goes.
Oh, one more thing: have you tried different USB ports on your PC and/or different USB cables? In the past I've found that it's a must to use the USB cable that came with the phone for anything other than charging.
Face_Plant said:
No problem. Let me know how it goes.
Oh, one more thing: have you tried different USB ports on your PC and/or different USB cables? In the past I've found that it's a must to use the USB cable that came with the phone for anything other than charging.
Click to expand...
Click to collapse
Yea, I've used different ports and only used the cable that came with it from the start.
Good. I'm betting it's a bad file or something didn't install properly that's causing your problem. I've used the MJ5 restore several times to get off of KitKat versions of Knoxraid with no problems, so I don't see why it shouldn't work for you.
Here's a tip: when you place the CSC file and the 28whatever file on your external SD card, rename them to "flash first" and "flash second" or something like that to avoid mixing them up. Renaming them won't hurt anything.
daigled said:
Yea, I've used different ports and only used the cable that came with it from the start.
Click to expand...
Click to collapse
try restoring with N900AUCECMLG_OneClickBin.exe ...i think it should work. http://forum.xda-developers.com/showthread.php?t=2619941
Related
I have been looking through the threads, and havent seen what I am looking for. So hopefully i will not get flamed to bad. I tried to install mikeymikes GR12, I got through the first stage of downloading the gingerbread rom to the phone through odin, but then it went south. I lost root and was unable to get back to the download screen. I then tried to use the all in one tool to root the phone, and that put me to the recovery screen where i could not use the ok button, just the volume up and down buttons. I just managed to get the download screen to come back, but i cant get anything else to work. Any suggestions on what to do, where to go from here.
Thank you for your help
I would go back to stock first. I believe your problem lies in the bootloaders. There are two bootloaders in the beginning and if you don't have the gingerbread ones installed, you won't install gingerbread properly.
I would use DesignGears One Click Odin to go back to stock and load the Froyo drivers. http://forum.xda-developers.com/showthread.php?t=731989. Make sure you open up Odin first before plugging in your phone, then hit the Start button.
Once that is done, you can try again, but read about getting the GB bootloaders installed properly before you try to flash a GB ROM. Any of the GB ROM instructions should get you there. Just make sure you know all the steps before you try it again.
Good Luck!!
I don't see why you would be flamed for your question. That is what Q&A is for and you are in a bad spot. The biggest thing to remember is to be as specific as possible when you post a question. This includes what you were trying to do, what steps you took, what was the result, when did the problem occur (which step) and what you have tried to do, if anything to fix it.
One more thing. It is always possible that the USB cable is bad or that the USB port you are plugging into (on the computer) isn't working properly. You might also want to plug into a different USB port.
Sorry these posts are broken up, but as I'm coming up with ideas, I'm posting.
Here's something you should try:
(I wrote this for Team Phoenix, hence the sig.. But it works the same with every ROM. There's a link to a very nice tutorial I suggest you follow).
http://forum.xda-developers.com/showpost.php?p=13503747&postcount=2
Hope it helps
You guys are awesome, Odin one click worked, It's on eclair, but it works! Thank you again
donkeyboy said:
You guys are awesome, Odin one click worked, It's on eclair, but it works! Thank you again
Click to expand...
Click to collapse
Glad it worked!
Make sure you read and understand before going forward with flashing
Otherwise... well.. I'll still be in here ready to help lol
BWolf56 said:
Glad it worked!
Make sure you read and understand before going forward with flashing
Otherwise... well.. I'll still be in here ready to help lol
Click to expand...
Click to collapse
Me too. If we can ... Remember not all things can be recovered from so please read everything twice before ever touching your phone.
10-4. My next question is: where do I get froyo from. Kies sees my eclair version as unregistered, so it wont update. And my ota sees an update is needed, but when i tried, the area im in has crappy signal, so the update failed and now i have to wait 24 hours to do it.
Any suggestions?
Thanks again
are you planning on flashing a custom rom?
if so updating to official froyo is A HUGE WASTE OF TIME
EDIT:are you Canadian by chance? if so check this thread:http://forum.xda-developers.com/showthread.php?t=979133
I only plan to root the official froyo right now, that is what I had before I jacked it up. I am not Canadian.
donkeyboy said:
I only plan to root the official froyo right now, that is what I had before I jacked it up. I am not Canadian.
Click to expand...
Click to collapse
Going on official froyo will get you the signature failed error (which you need the 3e recovery fix if you ever want to flash a custom ROM).
So, basically, if you want more than 2.2 official release. We suggest you don't update. If you're perfectly fine staying on 2.2 Froyo, then there's no problem lol
As for Kies, you shouldn't have any problem using Kies mini. Other than that, there is a 2.2 flash around here. I'm sure you'll find it doing a little search
I had root on my official froyo for a couple of months without a problem. Right now i cant get my phone to go into download mode, it only goes to the battery screen. If i can get to download i can make some headway
donkeyboy said:
I had root on my official froyo for a couple of months without a problem. Right now i cant get my phone to go into download mode, it only goes to the battery screen. If i can get to download i can make some headway
Click to expand...
Click to collapse
If the battery pull way isn't working. You could always go read on abd. It send SU commands and you could get your phone in downlaod mode that way.
Is there an easy way to get adb without getting the sdk. I downloaded the sdk and it keeps saying i need java, when i download the java crap it says the same thing.
donkeyboy said:
Is there an easy way to get adb without getting the sdk. I downloaded the sdk and it keeps saying i need java, when i download the java crap it says the same thing.
Click to expand...
Click to collapse
Did you reboot your pc?
Yes i did, no change
i believe you need microsoft .net framework installed also...
easy adb setup link in my sig.
files and everything needed to get going.
you may want to build a jig yourself or buy one online just in case:
MOD EDIT: No links to commercial products please.
I'm not sure whats going on with my D3. However, I have RSD and I have .890 and .959 downloaded as well as Fastboot.
What I want to do is just wipe the phone completely and just flash it like its a brand new phone.
Anyone know how to do so? Please post a link or instructions, I would greatly appreciate it.
atquick said:
I'm not sure whats going on with my D3. However, I have RSD and I have .890 and .959 downloaded as well as Fastboot.
What I want to do is just wipe the phone completely and just flash it like its a brand new phone.
Anyone know how to do so? Please post a link or instructions, I would greatly appreciate it.
Click to expand...
Click to collapse
http://goo.gl/7NoAv
Androidsims said:
http://goo.gl/7NoAv
Click to expand...
Click to collapse
Tried that. It keeps failing saying something about size was not as expected or something like that.
Redownload?
Avelnan said:
Redownload?
Click to expand...
Click to collapse
I have. MD5 sums match up each time. Should I try removing the ext sd card?
I would redownload everything and try agian
littleneutrino said:
I would redownload everything and try agian
Click to expand...
Click to collapse
Alright, attempt will be made again. Should I redownload RSD again or just the sbf's?
atquick said:
Alright, attempt will be made again. Should I redownload RSD again or just the sbf's?
Click to expand...
Click to collapse
Downloading the sbf's again. Went over to check and see if the phone was still on, The charging led is on, however the screen is off..
Held power, nothing. Held M + Power. Still nothing... Any thoughts on whats going on now?
I didn't see if you have pulled the SD card but yeah it can't hurt.
Sent from my DROID3 using XDA App
http://forum.xda-developers.com/showthread.php?t=1278056
Follow the first portion of the instructions on how to flash back to original 5.6.890. Note the making of a folder and it's name for the 890 flash.
Ignore the part about flashing the new ROM. These are the best instructions I've found so far for flashing back to stock via RSD lite.
Good luck, keep us posted.
Download and follow exactly and you'll be good to go.
Hope that helps.
Sent from my DROID3 using xda premium
wattnxt said:
http://forum.xda-developers.com/showthread.php?t=1278056
Follow the first portion of the instructions on how to flash back to original 5.6.890. Note the making of a folder and it's name for the 890 flash.
Ignore the part about flashing the new ROM. These are the best instructions I've found so far for flashing back to stock via RSD lite.
Good luck, keep us posted.
Download and follow exactly and you'll be good to go.
Hope that helps.
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
It keeps failing.
Step 3 mbmloader.bin
Step 4 mbm.bin
Step 8 logo.bin
Step 9 'lbl'
I'm stuck.
Let me do some looking when I get home tonight. I remember there being a file for certain versions of XP that helped some people and they couldn't flash without it.
I never had it happen personally, but I know those that did were terribly frustrated.
I also hear the 959 version is easier to flash for some reason. Never flashed that version, so this is only hear-say. But I know it did flash easier according to posts.
I will try to dig up a link for you.
i am getting the same thing also getting the bad CG boot.. now this may be a fix but idk how this guy got it it.. i have been asking eveywhere maybe you guys could help me... here is the thread http://forum.xda-developers.com/showthread.php?t=1248721
I found this by Psouza. He is likely the foremost expert on making things easy as far as unbricking your D3. Rumor has it he has a set of unbrick tools floating around this forum somewhere, though I haven't found it yet. Try in the Development thread, for sure it has to be there somewhere.
Post number 84
psouza4 said:
For those of you having problems flashing this and/or are suspicious of flashing ebr, mbr, and parts of the bootloader, you can selectively just flash the rest of it.
See attachment.
Click to expand...
Click to collapse
http://forum.xda-developers.com/attachment.php?attachmentid=715510&d=1315657647
Hope this helps.
I also saw that flashing the pre-installs file alone first helped someone. That file borked on me once, but I was able to adb it over and then execute it via adb to get my phone unbricked.
Please let us know what works for you, as all of this is a work in progress right now.
Good luck!
i don't know to much about adb and are looking for help on pre-installed files. I don't understand what that means or how to go about it? i also cant get past the bootloader screen, "invalid CG version". i can not boot up at all.
How bricked are you? can you boot into CWM? Are you able to boot into tools, or how far can you get?
What version were you running? 5.959 (stock) or 6.890 OTA or Leaked OTA or Soak test (all the same as far as 6.890 goes).
i can get into boot tools and just tryed another flash got to step 6 till it failed instead of 3.. I'm running stock. Cannot get passed boot tools... scratch all that just tried to flash again just on the off chance it mnight work and i got it. Going to try and re-root and CWN recovery with sdteel froids rom... will keep you in the loop
Awesome!!
Here is the link about the adb commands for preinstall.sh
http://forum.xda-developers.com/showpost.php?p=17196391&postcount=88
It helped me when I borked my leaked update. I ran into the same problem as limaxray did with too many files in /system. So make sure you clean out any apps you made into system apps before trying the update via the standard update route, and that all stock system apps are in place and properly named.
I had to remove some that updated partially with the leaked update when mine borked. I used the posted system dump to push them to the phone and then the update ran properly and updated them anyhow.
If for some reason re-rooting doesn't work for you. Go to /system/bin and remove su, busybox. Do the same in /system/xbin. For some reason if you already have them in there when you run the process, it will say success but no root after reboot. My 2c as it happened to me. You do not need to remove superuser.apk, but you will have to update it in the market after you re-root.
Congrats!!
I see now too there is a fastboot and moto-fastboot. moto-fastboot has worked for some who had issues from what I've found.
Keep us posted, and smile knowing you've recovered from a bork; none of us got where we are without doing it at least once, so you're in good company.
re-rooted and installed bootstrap, just got steel droid all loaded up and all is good.... thanks for your speedy responses and detailed instructions and links. I realy think all that happened was i took everything aet it sone last time tried to flash and it went threw. All i used was RSD lite and flashed the 8.6.590 fast boot file and after a several retries it went threw. If anyone needs help on this i will post the file links if you need the ones i used
Sorry for the long read, this is half rant and half question.
Alright, I got a captivate a long time ago (about a year and 3 months ago), loved it, rooted it and installed cyanogenmod as soon as I got home, changed roms and kernals constantly, did whatever I wanted to do.
About 3 months ago my screen stopped working.. So I take it in and they give me a refurb captivate, looked brand new so I didn't mind. However, when I tried to get into recovery it didn't work, the 3-button-method just wouldn't work at all, period, so I try to get it to work, gets stuck in bootloop.. pretty much every time I try to flash a rom something goes wrong and I get stuck in a bootloop but I can usually get into recovery or download mode because I had CWM.
So I'm on maxq's rom and it's working great for the past 2 months, decide not to mess with kernals or anything, however today I decided to try ICS, load it up, everything's fine, then I realize my soft keys aren't working, search for awhile, can't find anything, finally just manually start looking through the rom pages, and someone said that if you have the problem to just odin back to stock and try again.
I odin back to stock, but now 3 button combo doesn't work.. So more searching, find that I can run the 3e fix by TRusselo, doesn't work because I need root, more searching on how to root without recovery, find "SuperOneClick", root with superoneclick, then run 3e fix, everything is working fine, I check my email and load the ICS files onto SD card, go to restart and go into recovery mode.. Bricked, stuck in a bootloop, won't go to recovery, won't go to download, nothing.
Why the **** was I able to do anything I wanted with my old captivate, but if I even root this one it bricks? And what did I do to even brick it? I only ran the 2 programs and both of them worked flawlessly.
I guess my only option is to usb jig it, but honestly now I'm convinced that the phone is just faulty, I want to run the thing over.
-Pirate said:
So I'm on maxq's rom and it's working great for the past 2 months, decide not to mess with kernals or anything, however today I decided to try ICS, load it up, everything's fine, then I realize my soft keys aren't working, search for awhile, can't find anything, finally just manually start looking through the rom pages, and someone said that if you have the problem to just odin back to stock and try again.
Click to expand...
Click to collapse
If you would have actually searched you would have known it was a bug in the glitch. There are atleast 40 pages about that.
-Pirate said:
I odin back to stock, but now 3 button combo doesn't work.. So more searching, find that I can run the 3e fix by TRusselo, doesn't work because I need root, more searching on how to root without recovery, find "SuperOneClick", root with superoneclick, then run 3e fix, everything is working fine, I check my email and load the ICS files onto SD card, go to restart and go into recovery mode.. Bricked, stuck in a bootloop, won't go to recovery, won't go to download, nothing.
Click to expand...
Click to collapse
If you flashed ICS you should know it takes 2 flashes for it to work first time. Having a jig around is always a good idea as well.
-Pirate said:
Why the **** was I able to do anything I wanted with my old captivate, but if I even root this one it bricks? And what did I do to even brick it? I only ran the 2 programs and both of them worked flawlessly.
Click to expand...
Click to collapse
Stuff doesn't work as intended. Keep in mind everything is still in dev and not all devices are the same. But you should have searched a little more and it would have ran =/
U def don't need a jig. If it's booting it's not bricked. Try removing battery, start Odin, hold down power and down, plug in and put battery in. This should bring u to download mode.
prbassplayer said:
If you would have actually searched you would have known it was a bug in the glitch. There are atleast 40 pages about that.
Click to expand...
Click to collapse
I did start to see a few people with the problem, however many people do not follow up with what fixes their problem, and I did what a few people had said to do.
prbassplayer said:
If you flashed ICS you should know it takes 2 flashes for it to work first time. Having a jig around is always a good idea as well.
Click to expand...
Click to collapse
I should of mentioned that I did flash a few times, 3 total I think, it was getting stuck at boot.
prbassplayer said:
Stuff doesn't work as intended. Keep in mind everything is still in dev and not all devices are the same. But you should have searched a little more and it would have ran =/
Click to expand...
Click to collapse
I understand that **** happens but honestly my old captivate could always get into recover mode and download mode no matter what, it's extremely frustrating that something changed with the newer models. One of my questions was what caused the brick? I did nothing wrong from what I see and it was running perfectly until I tried to restart/boot into recovery.
Oh and mbc663, thanks but download mode doesn't work at all, nor does recovery obviously.
I can't say exactly what you are doing. Best advice I can do Re download your .zips Flash back to stock GB and try again.
-Pirate said:
About 3 months ago my screen stopped working.. So I take it in and they give me a refurb captivate, looked brand new so I didn't mind. However, when I tried to get into recovery it didn't work, the 3-button-method just wouldn't work at all, period, so I try to get it to work, gets stuck in bootloop.. pretty much every time I try to flash a rom something goes wrong and I get stuck in a bootloop but I can usually get into recovery or download mode because I had CWM.
So I'm on maxq's rom and it's working great for the past 2 months, decide not to mess with kernals or anything, however today I decided to try ICS, load it up, everything's fine, then I realize my soft keys aren't working, search for awhile, can't find anything, finally just manually start looking through the rom pages, and someone said that if you have the problem to just odin back to stock and try again.
I odin back to stock, but now 3 button combo doesn't work.. So more searching, find that I can run the 3e fix by TRusselo, doesn't work because I need root, more searching on how to root without recovery, find "SuperOneClick", root with superoneclick, then run 3e fix, everything is working fine, I check my email and load the ICS files onto SD card, go to restart and go into recovery mode.. Bricked, stuck in a bootloop, won't go to recovery, won't go to download, nothing.
Why the **** was I able to do anything I wanted with my old captivate, but if I even root this one it bricks? And what did I do to even brick it? I only ran the 2 programs and both of them worked flawlessly.
I guess my only option is to usb jig it, but honestly now I'm convinced that the phone is just faulty, I want to run the thing over.
Click to expand...
Click to collapse
Last year, I had issues with my original Cap, and got a "new" one. I learned that the bulk of the Caps going out as replacements are referbs. The one I got was a 1008 build, and does not have 3 button recovery. There are minor differences with each and every Cap that's out there. That's why some have issues with ROM's and some don't, some can over clock like crazy, and some can't at all. My guess is you have a 1008 as well, but that really doesn't matter. You just have a different device and as you seem to already have learned.
It sounds like there is more research you need to do. Even though the devices are a bit different, if you are having issues with ROM's loading, then I would say it's more of a procedure issue, than one with your device.
My procedure, is,
Remove SD/Micro SD
Odin1 Click to Stock JF6, and Master Clear(This will erase EVERYTHING)
Root with One-Click Root
Use Sideload Wonder Machine to install ROM Manager, copy update.zip and 3buttonFix to my SD, then reboot into recovery
Once in recovery I install the 3buttonFix, and install my new ROM
For me this has proven to be a very good method versus going from one ROM to another. The Master Clear cleans EVERYTHING off of your SD, so there is no chance for anything to corrupt your new install. Anytime I read a post of a install gone FUBAR, USUALLY a Flash To Stock/Master Clear (FTS/MC) fixes it
Before using Odin 1 Click, check your devices build number!! If it is higher than 1012, I would NOT recommend using 1 click, there is a higher chance of hard brick on the newer devices
Kangi...if you flash a firmware package without bootloaders, you won't have to do the 3 button fix every time. And if you keep a copy of the update.zip on your pc you don't have to even root, let alone bother with side loading ROM manager.
Cezar has a no boots jf6 and after you run that, you can still use master clear in one click.
Sounds like you got one of the refurbs that is missing the SBL. Have you looked at this thread? http://forum.xda-developers.com/showthread.php?t=1129821
I've not had this problem myself but it sounds like that might help. If I remember reading correctly, once this is flashed it should stick as long as you don't flash any other bootloaders on top of it.
Its not missing the sbl. The sbl it has doesn't respond to key combos. Derpa sherpa moment for samsung I guess?
Rofl yeah...if it was missing the sbl it would be fuggin bricked!
studacris said:
Kangi...if you flash a firmware package without bootloaders, you won't have to do the 3 button fix every time. And if you keep a copy of the update.zip on your pc you don't have to even root, let alone bother with side loading ROM manager.
Cezar has a no boots jf6 and after you run that, you can still use master clear in one click.
Click to expand...
Click to collapse
I know, thanks. I'm such a creature of habit, I started doing it like this a bit over a year ago, and has worked flawlessly for me(just jinxed myself!) so I never saw a reason to "fix what aint broke".
I'll take a look at Cezar's thanks!
Yeah, missing SBL was a poor choice of words. My bad.
kangi26 said:
Last year, I had issues with my original Cap, and got a "new" one. I learned that the bulk of the Caps going out as replacements are referbs. The one I got was a 1008 build, and does not have 3 button recovery. There are minor differences with each and every Cap that's out there. That's why some have issues with ROM's and some don't, some can over clock like crazy, and some can't at all. My guess is you have a 1008 as well, but that really doesn't matter. You just have a different device and as you seem to already have learned.
It sounds like there is more research you need to do. Even though the devices are a bit different, if you are having issues with ROM's loading, then I would say it's more of a procedure issue, than one with your device.
My procedure, is,
Remove SD/Micro SD
Odin1 Click to Stock JF6, and Master Clear(This will erase EVERYTHING)
Root with One-Click Root
Use Sideload Wonder Machine to install ROM Manager, copy update.zip and 3buttonFix to my SD, then reboot into recovery
Once in recovery I install the 3buttonFix, and install my new ROM
For me this has proven to be a very good method versus going from one ROM to another. The Master Clear cleans EVERYTHING off of your SD, so there is no chance for anything to corrupt your new install. Anytime I read a post of a install gone FUBAR, USUALLY a Flash To Stock/Master Clear (FTS/MC) fixes it
Before using Odin 1 Click, check your devices build number!! If it is higher than 1012, I would NOT recommend using 1 click, there is a higher chance of hard brick on the newer devices
Click to expand...
Click to collapse
I didn't think anyone else was going to reply to this thread, whoops.
Thank you for helping me, but I'm still having trouble.
Rom manager doesn't show up in Market, Sideload wonder machine tells me [INSTALL FAILED OLDER SDK] with any apk of Rom manager I find.
kangi26 said:
3buttonFix to my SD, then reboot into recovery
Click to expand...
Click to collapse
How do you reboot into recovery when 3buttonfix hasn't been applied yet?
This sucks and is extremely frustrating, I feel like my captivate is just trolling me.
-Pirate said:
I didn't think anyone else was going to reply to this thread, whoops.
Thank you for helping me, but I'm still having trouble.
Rom manager doesn't show up in Market, Sideload wonder machine tells me [INSTALL FAILED OLDER SDK] with any apk of Rom manager I find.
How do you reboot into recovery when 3buttonfix hasn't been applied yet?
This sucks and is extremely frustrating, I feel like my captivate is just trolling me.
Click to expand...
Click to collapse
When I get home later tonight I'll link you everything you'll need. Again, VERY important, what is your build number? If it's 1012 or higher, don't use Odin 1 click
Sent from a autonomous device
kangi26 said:
When I get home later tonight I'll link you everything you'll need. Again, VERY important, what is your build number? If it's 1012 or higher, don't use Odin 1 click
Sent from a autonomous device
Click to expand...
Click to collapse
Ok, finally got it working, I did exactly what you said, I found the rom manager 3.00.002 or whatever and that worked with sideloader, it took some messing around with but I'm running ICS now, thank you so much man, you've helped me so much, and now I can change roms and keep up to date without worrying about constantly soft-bricking.
As for my build number, I'm not sure, the only thing I see under build number in settings is: "IML74k"
-Pirate said:
Ok, finally got it working, I did exactly what you said, I found the rom manager 3.00.002 or whatever and that worked with sideloader, it took some messing around with but I'm running ICS now, thank you so much man, you've helped me so much, and now I can change roms and keep up to date without worrying about constantly soft-bricking.
As for my build number, I'm not sure, the only thing I see under build number in settings is: "IML74k"
Click to expand...
Click to collapse
The build number is actually under your battery, and looks like 10.06, 10.07, 10.08 and so on. It is the production date
Edit** And as a side note, do NOT try to use the 3buttonFix with a GB ROM, it WILL brick your phone in a really bad way. ONLY use it with 2.1 or 2.2
kangi26 said:
The build number is actually under your battery, and looks like 10.06, 10.07, 10.08 and so on. It is the production date
Edit** And as a side note, do NOT try to use the 3buttonFix with a GB ROM, it WILL brick your phone in a really bad way. ONLY use it with 2.1 or 2.2
Click to expand...
Click to collapse
Is it weird that I don't have a build number? It seems I can't post pictures without a few more posts, maybe this will work: deleted
And thanks for the warning on the 3buttonfix, I'm going to have to read more about bootloaders though, I don't understand what you and studacris were talking about earlier in the thread, haha.
-Pirate said:
Is it weird that I don't have a build number? It seems I can't post pictures without a few more posts, maybe this will work: imgurDOTcom/26sXGl.jpg
And thanks for the warning on the 3buttonfix, I'm going to have to read more about bootloaders though, I don't understand what you and studacris were talking about earlier in the thread, haha.
Click to expand...
Click to collapse
I havent seen that before, there doesnt seem to be a build#
Might want to pull that photo, it's not too good having your IMEI number publicly displayed
kangi26 said:
I havent seen that before, there doesnt seem to be a build#
Might want to pull that photo, it's not too good having your IMEI number publicly displayed
Click to expand...
Click to collapse
Maybe because it's a refurb? and whoops didn't think about that.
-Pirate said:
Maybe because it's a refurb? and whoops didn't think about that.
Click to expand...
Click to collapse
I'm not sure why, mine is a referb, and I have a sticker with mine on it. Ooh well, it is what it is
Sent from a autonomous device
To start this off im going to say that i am very new to Android devices, ive owned my Note 3 (The AT&T SM-N900A one) for nearly three weeks now spending time researching on rooting and the methods, etc. Well i just tried to and didnt quite have much success.
I followed this guide and its steps very thoroughly. http://forum.xda-developers.com/showthread.php?t=2559715
Yet it all ended with it booting up looking like new but nearly every 3 seconds errors appear about processes crashing and trying to stop, for example "Unfortunately, Direct pen input has stopped."
After that failure i went ahead and tried to undo it which probably wasnt a good idea, i followed this tutorial: http://www.droidviews.com/how-to-unbrick-att-galaxy-note-3-sm-n900a/.
I ended up at the exact same place, same error over and over. Does anyone know how to fix this?
Thank you.
(I apologize if this had been brought up before i went searching but found nothing that was a solution to my problem.)
baileynapier said:
To start this off im going to say that i am very new to Android devices, ive owned my Note 3 (The AT&T SM-N900A one) for nearly three weeks now spending time researching on rooting and the methods, etc. Well i just tried to and didnt quite have much success.
I followed this guide and its steps very thoroughly. http://forum.xda-developers.com/showthread.php?t=2559715
Yet it all ended with it booting up looking like new but nearly every 3 seconds errors appear about processes crashing and trying to stop, for example "Unfortunately, Direct pen input has stopped."
After that failure i went ahead and tried to undo it which probably wasnt a good idea, i followed this tutorial: http://www.droidviews.com/how-to-unbrick-att-galaxy-note-3-sm-n900a/.
I ended up at the exact same place, same error over and over. Does anyone know how to fix this?
Thank you.
(I apologize if this had been brought up before i went searching but found nothing that was a solution to my problem.)
Click to expand...
Click to collapse
Have you performed a factory data reset since the last attempt?
440bro said:
Have you performed a factory data reset since the last attempt?
Click to expand...
Click to collapse
Yes i have,a few times, it just then reboots with the setup and that error still occurring.
baileynapier said:
Yes i have,a few times, it just then reboots with the setup and that error still occurring.
Click to expand...
Click to collapse
That error is a bugger to get rid of, if you even can. i had this happen and had to return my device to the store. BUT that was before we had a working back to stock MJ5 solution.
http://forum.xda-developers.com/showthread.php?t=2559715
If you were on MJ5 this will get you back to out of the box stock with or without Root, its up to you.
i have used this twice and has worked smoothly both times, just make sure you download the files needed and follow the steps.
the2rrell said:
That error is a bugger to get rid of, if you even can. i had this happen and had to return my device to the store. BUT that was before we had a working back to stock MJ5 solution.
http://forum.xda-developers.com/showthread.php?t=2559715
If you were on MJ5 this will get you back to out of the box stock with or without Root, its up to you.
i have used this twice and has worked smoothly both times, just make sure you download the files needed and follow the steps.
Click to expand...
Click to collapse
That is the method OP used to get root....
OP, you should have used Kingo... Now you will have to redo that whole process just to restore back to stock. You had a bad flash or a bad download.
Sent from my SM-N9005A using XDA Premium 4 mobile app
28248965 286a
the2rrell said:
That error is a bugger to get rid of, if you even can. i had this happen and had to return my device to the store. BUT that was before we had a working back to stock MJ5 solution.
http://forum.xda-developers.com/showthread.php?t=2559715
If you were on MJ5 this will get you back to out of the box stock with or without Root, its up to you.
i have used this twice and has worked smoothly both times, just make sure you download the files needed and follow the steps.
Click to expand...
Click to collapse
That was the method that originally got me into this situation and i just tried it again step by step and i am still having the issue.
One thing that has caught my eye is that this was my devices information before ever trying any rooting process or anything:
MODEL NUMBER: SAMSUNG-SN-N900A
ANDROID VERSION: 4.3 (Jelly Bean)
BASEBAND VERSION: N900AUCUBNB4
KERNEL INFO -
3.4.0-1625098
se.i[email protected] #1
Mon Feb 10 21:13:28 KST 2014
BUILD NUMBER: JSS15J.N900AUCUBNB4
SELINUX STATUS: Enforcing
Is there any possible way to get it back to being a BNB4 device like the information above?
graydiggy said:
That is the method OP used to get root....
OP, you should have used Kingo... Now you will have to redo that whole process just to restore back to stock. You had a bad flash or a bad download.
Sent from my SM-N9005A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
tis the reason i directed him back to that thread. i know they are working on a easier odin flash to return to stock in another thread. dont know why he was using that to get root, but he will now need to use it to get booting back to normal again.
anyway, apologies for not being more clear.
so to sum it all up, redownload the files in case you got a bad one and repeat the process my good sir.
the2rrell said:
tis the reason i directed him back to that thread. i know they are working on a easier odin flash to return to stock in another thread. dont know why he was using that to get root, but he will now need to use it to get booting back to normal again.
anyway, apologies for not being more clear.
so to sum it all up, redownload the files in case you got a bad one and repeat the process my good sir.
Click to expand...
Click to collapse
Okay, thank you guys very much but its back to functioning properly! :victory:
Now am i just trying to accomplish a root, but that doesnt seem to be working, after i put the root de la vega files onto the sdcard SuperSU never installs upon restart, why is it not auto-installing like it seems to be expressed as in the tutorial?
EDIT: Okay guys, nevermind about the root, i just used Kingo.
baileynapier said:
Okay, thank you guys very much but its back to functioning properly! :victory:
Now am i just trying to accomplish a root, but that doesnt seem to be working, after i put the root de la vega files onto the sdcard SuperSU never installs upon restart, why is it not auto-installing like it seems to be expressed as in the tutorial?
Click to expand...
Click to collapse
use kingo 1.1.8 it is a lot easier
baileynapier said:
ive owned my Note 3 (The AT&T SM-N900A one) for nearly three weeks now spending time researching on rooting and the methods, etc.
Click to expand...
Click to collapse
How did you NOT find Kingo right away?
What kind of research did you do for 3 weeks? lol
Well, I'm glad you're good to go now. The devs on this site are exceptional and you are lucky to have them. (me too).
baileynapier said:
Okay, thank you guys very much but its back to functioning properly! :victory:
Now am i just trying to accomplish a root, but that doesnt seem to be working, after i put the root de la vega files onto the sdcard SuperSU never installs upon restart, why is it not auto-installing like it seems to be expressed as in the tutorial?
EDIT: Okay guys, nevermind about the root, i just used Kingo.
Click to expand...
Click to collapse
So how did you get it back functioning properly? I am at the same point. I bricked my N3 screwing around with getting Face Unlock to work. So I followed the steps of Restore for MJ5 post, and immediately upon the final boot into setup, the Direct Pen Input error started, and makes the device useless. What fixed yours?
Re-download all the files and retry. Also, verify the size. I think you may have a corrupt file somewhere.
And factory reset after installing a ROM, even if it's the same ROM you had. Any ROM, on any phone, not just this one. Different ROMs store data in different locations, and if a ROM picks up the data from a previous ROM, that may bot be the data it wants, so it causes things to crash.
Ok thanks for the replies. I actually tried a factory reset after seeing the error, but it didn't help at all. And I did run a checksum on the only file that displayed a number, when I originally downloaded the files. But as would be expected, after all simple efforts to fix the issue failed, I started fresh on a whole different PC, downloaded all of the files again, used a different USB cable, and installed everything all over again. And low and behold, the second time was a total success. I can't explain what made the difference, and the checksum result showed an accurate download both times. But this is the nature of the beast isn't it?
Thanks,
NO MORE SUPPORT.....GAME OVER
Did you delete your data, system, safestrap is gone, only download mode and stock recovery are available? Do you want to start fresh and out of the box new?
(( FOR s 5 ACTIVE )) NE4Thanks to @ted77usa & @Intub8 for the help. SAM MOBILE for the Firmware and steps. KNOX was not tripped. Nothing was after this. It worked perfectly.
Just FOLLOW INSTRUCTIONS
Do this at your own risk. If you don't read and mess up your phone, its not my fault . As long as you can get into download mode, this will help out a lot. I am not responsible for what you do to your device.
Odin Back to s5 Active Stock. NE4
Make sure you have the Samsung drivers installed before starting.
Samsung USB drivers
Make sure USB debugging is checked under settings/developer options. If you don't know how to do that, go to "about device" in settings, and click on "Build Number x5 till you unlock Developer options".
Extract (unzip) the firmware file (NE4) HERE
Download Odin v3.09 HERE
Extract Odin zip-file
Open Odin v3.09
Reboot phone in Download Mode (press and hold Home + Power + Volume Down buttons)
Connect phone and wait until you get a blue sign in Odin
Add the firmware file to AP / PDA
Make sure re-partition is NOT ticked
Click the start button, sit back and wait a few minutes
Note : Some users are getting stuck at long At&t screen, once odin finishes and you happen to get stuck, reboot to stock recovery and factory reset your phone.
It should boot up just fine after that. The At&t screen sometimes takes a while.
You can do this below if you want. I have done this about 5 or 6 times. #6 and 7 happens sometimes.
I wanted to be totally fresh and wanted to use "Wipe Data (YES)" in safestrap. Here is what I did and what happened.
My phone has been really good since this and all is smooth.
Things to do to be fresh and start all the way over out of box style:
1. Make sure you have done a back up, and your ready to restore with Odin.
2. Go into Safestrap
3. Go to WIPE tab > Factory reset
4. Advanced wipe, (Wipe > Dalvik Cache, "NOT Micro SDcard"> Data, Cache, System)
5. For really starting over > next to Advanced wipe is "Format Data" do that and type YES
6. This will get rid of safestrap and everything so you will get a black screen once it deletes all.
7. Try to catch it and go into download mode before it boots to the Samsung screen (Which it will stay there FOREVER)
(As soon as your phone does this, try to catch it before the samsung screen and go into download mode. When it turns black, quickly hold Power + Volume down + home button. )
8. While in download mode, flash the restore firmware.
9. Let it do its thing and you will be factory new.
10. After it all settles down and you are back up and running, you can start like I do.
(Root with V3 (Make it Rain), Install and update SU, Reboot 3 times lol, install busybox, install safestrap, install xposed, reboot, install your modules, reboot, power down and boot back but go into safestrap and wipe dalvik cache and regular cache. Reboot. lol- Install all your apps you like or have your backups from titanium on your sd card and restore) Reboot and go into safestrap again and fix permissions and reboot lol...... BAM. (Your phone should be sick and you should throw up on it)
LINKS
NE4 (THE MAIN FILE YOU NEED)
[KITKAT:ND3]
LATEST BETA FILE: Safestrap-KLTEATT-ND3-3.75-B03.apk
XDA Downloads Safestrap
Mirror 1 (Crackflasher) Safestrap
BUSYBOX
SUPERSU
Just make sure the model number matches yours and you should be all set. That file should contain everything you need to get back to stock. Follow the directions listed underneath the firmware.
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
Thanks. All is good and I can confirm this works on the At&t S 5 Active (NE4).
I am fresh to start over.
Edit: All is good. Rooted, Busybox, Froze bloat etc. Safestraped, Backuped, Phone is running great!!
Intub8 said:
Just make sure the model number matches yours and you should be all set. That file should contain everything you need to get back to stock. Follow the directions listed underneath the firmware.
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks. Its working!!!!! I thought this wasn't out yet. Looks out to me.
I will update OP and get on my XDA app to hit thanks. Thanks for pointing out the simple directions I failed to see on SAM mobile. My phone is back
LuckyColdJohnson said:
Thanks. Its working!!!!! I thought this wasn't out yet. Looks out to me.
I will update OP and get on my XDA app to hit thanks. Thanks for pointing out the simple directions I failed to see on SAM mobile. My phone is back
Click to expand...
Click to collapse
Glad that worked out for u bud.....[emoji41][emoji106]
☆Swyped From SFive SS Edition☆
I wonder if this would work on the regular S5? If someone tries and it does please report back....THanks
LuckyColdJohnson said:
I wonder if this would work on the regular S5? If someone tries and it does please report back....THanks
Click to expand...
Click to collapse
WWWHYY would you even want to know if this will work when you have your own firmware?! Then you try and convince someone else to take the plunge and try instead of you doing it? Just wondering why... cause i'm very baffled right now.
Caliesv said:
WWWHYY would you even want to know if this will work when you have your own firmware?! Then you try and convince someone else to take the plunge and try instead of you doing it? Just wondering why... cause i'm very baffled right now.
Click to expand...
Click to collapse
Uhhhh. I'm sorry you feel that way. I was running s 5 ROMS just fine on my phone. Their basicly the same but with a few different specs.
What plunge are you talking about dude? I have soft bricked my phone (formated data) and used this to start fresh. The more we know the better. I have done it. Its fine. I have ran NCE NE4, you must not know whats going on here. That what this thread is for. Restoring your phone to factory defaults. I have done it for the Active and if someone did it on their regular s 5 than I want to know.
LuckyColdJohnson said:
Uhhhh. I'm sorry you feel that way. I was running s 5 ROMS just fine on my phone. Their basicly the same but with a few different specs.
What plunge are you talking about dude? I have soft bricked my phone (formated data) and used this to start fresh. The more we know the better. I have done it. Its fine. I have ran NC2 NE4, you must not know whats going on here. That what this thread is for. Restoring your phone to factory defaults. I have done it for the Active and if someone did it on their regular s 5 than I want to know. THATS IT. Now go here for being mean > CLICK ME @Caliesv
Click to expand...
Click to collapse
LOL! nice actually made me laugh! lol i hear ya man. i was just wondering why. and you full fulled my wondering. thanks
Caliesv said:
LOL! nice actually made me laugh! lol i hear ya man. i was just wondering why. and you full fulled my wondering. thanks
Click to expand...
Click to collapse
Its all good. I'm glad I made you laugh too. Really. I'm just messing with ya a little....This thread is for Active users. Like I said, if this can work for the regular S 5, then I will update the OP for S5/S5 Actives only. Thats all. I was on NCE (A regular S 5 ROM) when I did this and it worked perfectly.
LuckyColdJohnson said:
Its all good. I'm glad I made you laugh too. Really. I'm just messing with ya a little....This thread is for Active users. Like I said, if this can work for the regular S 5, then I will update the OP for S5/S5 Actives only. Thats all. I was on NCE (A regular S 5 ROM) when I did this and it worked perfectly.
Click to expand...
Click to collapse
No worries man lol. yeah i have an active too. i hope we get our own thread soon. And thanks for the steps, tons of people are going to need it lol
Caliesv said:
No worries man lol. yeah i have an active too. i hope we get our own thread soon. And thanks for the steps, tons of people are going to need it lol
Click to expand...
Click to collapse
10-4.....It really helped me when I screwed up. This worked 100% for me. I have flashed over 5 different ROMS from T-Mobile, International, as well as At&t ROMs we have. Sometimes its better to start all the way over fresh. Sometimes we get into a pickle and need to start over. This will help us.....Thanks !!!!
Continued thanks for being our official S5 Active tester. I'm glad to hear you got it back to running and that you were able to find the firmware for our G870A. This will come in handy when I get my phone past the point of no return, it usually takes me a month or so but I'll get there.
Please keep us informed as your tests, trials and discoveries continue!
thepktrckt said:
Continued thanks for being our official S5 Active tester. I'm glad to hear you got it back to running and that you were able to find the firmware for our G870A. This will come in handy when I get my phone past the point of no return, it usually takes me a month or so but I'll get there.
Please keep us informed as your tests, trials and discoveries continue!
Click to expand...
Click to collapse
No problem. Looking at a GPS issue now. Something has screwed it all up. Probably a module or two (exposed) Almost tempted to restore again and test before each install.
Sent from my SAMSUNG-SM-G870A using XDA Premium 4 mobile app
If you go back to stock and the GPS still doesn't initiate let me know. There was a way to hard reset the GPS that I came across on the gs3 that may work. Every time I flash a rom if it's acting goofy I wipe everything and go back to 100% stock. Sometimes things get stuck and left behind that can muck things up. Think of it like a colon clense for your phone. Glad the Odin worked for you.
Sent from my SAMSUNG-SM-G900A using XDA Premium HD app
Intub8 said:
If you go back to stock and the GPS still doesn't initiate let me know. There was a way to hard reset the GPS that I came across on the gs3 that may work. Every time I flash a rom if it's acting goofy I wipe everything and go back to 100% stock. Sometimes things get stuck and left behind that can muck things up. Think of it like a colon clense for your phone. Glad the Odin worked for you.
Sent from my SAMSUNG-SM-G900A using XDA Premium HD app
Click to expand...
Click to collapse
Yes, Please share if you don't mind. I broke the GPS lol. I don't believe flashing this official firmware did it though, I think flashing different ROM's did it but who am I......I found a GPS fix I used for my Note 3 (Kit Kat) You have to flash it in recovery. Is that how yours is? Here is the file for you to check out if you want to. I haven't flashed it yet though. >>>> Deleted Link ....That didnt work. Got random reboots.
LuckyColdJohnson said:
Yes, Please share if you don't mind. I broke the GPS lol. I don't believe flashing this official firmware did it though, I think flashing different ROM's did it but who am I......I found a GPS fix I used for my Note 3 (Kit Kat) You have to flash it in recovery. Is that how yours is? Here is the file for you to check out if you want to. I haven't flashed it yet though. >>>> Deleted Link ....That didnt work. Got random reboots.
Click to expand...
Click to collapse
Found it after about an hour of looking , You must Odin back to a stock ROM first.
((((2. Enter into dialer *2767*3855# (Will do a HARD reset, no internal storage will be lost except the usual data)
3. Boot up again and run... )))
keep in mind this was the method to fix the gps on the note 2 and it may or may not still be a good dialer code for your s5.
Intub8 said:
Found it after about an hour of looking , You must Odin back to a stock ROM first.
((((2. Enter into dialer *2767*3855# (Will do a HARD reset, no internal storage will be lost except the usual data)
3. Boot up again and run... )))
keep in mind this was the method to fix the gps on the note 2 and it may or may not still be a good dialer code for your s5.
Click to expand...
Click to collapse
I restored a back up and it's working again. Something I installed did it. I'm trying to figure out what did. It could be anything. Thanks for this.
Caliesv said:
WWWHYY would you even want to know if this will work when you have your own firmware?! Then you try and convince someone else to take the plunge and try instead of you doing it? Just wondering why... cause i'm very baffled right now.
Click to expand...
Click to collapse
And @Caliesv I would ask you Why Not? The whole point of unlocking/rooting/building custom ROMs is because WE CAN, and how better to learn what we can and can't do then by trying? Just because a device has its own firmware has absolutely no bearing on what ROM you flash, granted as the default firmware it likely wont flash do to a signature mismatch but as a custom ROM why not?
I might just build one for the Heck of it.
GPS is a problem still. About to re-flash the restore and see what happens without root. Will report back.