Hey guys I am kind of freaking out here and just made an account because I literally have no clue what to do. I just recently was running drakeys jb and upgraded to kitkat, but realized I did not follow one of the steps and that was to make put it as my stock rom. My phone rebooted and seemed to be working with some changes to it. After I attempted to flash the stockrom theme and realized I was no longer rooted? and didn't have safestrap. Now my phone boots up, it shows the samsung note 3 screen and then the screen is just black but the phone does go into recovery mode and download mode. I really don't know what to do so some guidance or solution would be amazing. Got work in the morning so the faster the help the better.
Thank you
Just restore to mj5 then follow the instructions
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
There's a thread to restore to stock maybe specify what your process was that got you to this point
Sent from my SM-N9005 using xda premium
Related
OK, Stupid me for even trying to load roms on my note. I managed to finally root my note, used clock works rom manager to download a rom, tried to install it now my phone wont boot up. It just vibrates once says samsung and just loops. Like its restarting everytime. I can still boot into recovery with clock works recovery and enter download mode, I think I just need the stock rom and flash it through oden but I dont know where to get it. Please Help!!!
....
tried recovery through CWM, system recovered but still, phone will not boot. Just keeps restarting then samsung logo then reboots again and again.....ganna try advanced restor...
ok....
ok, restored boot, now restoring system, ganna go down the line and advanced restore everything I made a back up of before my little problem...will post results
Success! IM glad I backed up my entire phone before I started screwing around with roms! I guess I did not need you guys help after all. X) Oh what a little google research can do! Thanks anyway.
Sent from my SGH-T879 using xda app-developers app
Glad you could resolve this by you're self.I had something similar happen to me while trying to flash Blackstars ROM. Turned out to be a bad download of his ROM and I got stuck in boot loops zone lol. All I did was download the stock odex ROM from the Dev section and all went back to normal.
Sent from my SGH-T879 using xda premium
Please help me!!!
I have same problem with my T-Mobile Samsung galaxy note..
It won't turn on and cannot put download mode or recovery mode.
I think, flashed wrong ROM
Do you have any idea to get out of this situation.
Thanks
Sent from my SGH-T999 using xda premium
kim621973 said:
Please help me!!!
I have same problem with my T-Mobile Samsung galaxy note..
It won't turn on and cannot put download mode or recovery mode.
I think, flashed wrong ROM
Do you have any idea to get out of this situation.
Thanks
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
If you can't get into recovery or download mode you might be in a bit of a pickle. Recently did that to my GS3 and I had to send it back to Samsung. I would find and try a USB Jig first, that might get you into download mode so you can use Odin to flash stock firmware back onto the phone. Just do a google search for Samsung USB Jig.
Thank you for your advise:thumbup:lol
That is only way to unbricking the phone?
Sent from my SGH-T999 using xda premium
kim621973 said:
Thank you for your advise:thumbup:lol
That is only way to unbricking the phone?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Well that is the way you can do it, if the USB Jig gets you into download mode. If it doesn't, then you can have it JTaged. There are companies out there that offer JTag Service for some fee. Can't remember now but like 60-70 bucks maybe. Again, I'm sure it's just a google search away. Other than those two options I don't know if anything else, besides sending it back for warranty replacement.
Make a JIG, its' super easy. I made one to fix a friends Galaxy S2.
http://galaxys2root.com/galaxy-s2-hacks/how-to-make-a-usb-jig-for-your-galaxy-s2/
mechanix619 said:
Make a JIG, its' super easy. I made one to fix a friends Galaxy S2.
http://galaxys2root.com/galaxy-s2-hacks/how-to-make-a-usb-jig-for-your-galaxy-s2/
Click to expand...
Click to collapse
Great. this is exactly what I did. Couldn't remember the link. Didn't work for me GS3 though. That thing was hard bricked.
Hi Guys,
I'm a noob so please send me in the right direction if I seem out of place. I have an Exhibit 4G that I managed to root. It was 2.3.6 I believe. All was great until I decided I wanted to change the operating system to a Peach Sunrise (I think) then it became stuck in a boot screen loop. I have tried resetting to factory but that doesn't help. I'm not too savvy with these phones so I'm stuck at a dead end. I'm looking for someone in the Atlanta area to fix it for me. I'm willing to pay. It was a brand new phone bought from an individual. It was only used about two week by me. Please let me know if you can help or have a relatively easy solution. Thanks in advance, Les
Is it the galaxy exhibit 4G T679? It the original exhibit? There are multiple phones with the same name. Also wiping cache/dalvik cache and fix permissions will usually fix a problem like this.
Sent from my SGH-T679 using xda app-developers app
patches0616 said:
Hi Guys,
I'm a noob so please send me in the right direction if I seem out of place. I have an Exhibit 4G that I managed to root. It was 2.3.6 I believe. All was great until I decided I wanted to change the operating system to a Peach Sunrise (I think) then it became stuck in a boot screen loop. I have tried resetting to factory but that doesn't help. I'm not too savvy with these phones so I'm stuck at a dead end. I'm looking for someone in the Atlanta area to fix it for me. I'm willing to pay. It was a brand new phone bought from an individual. It was only used about two week by me. Please let me know if you can help or have a relatively easy solution. Thanks in advance, Les
Click to expand...
Click to collapse
What do you mean by reset to factory? Wiping data does not change the operating system. However do you have cwm installed and yea is it even the t679
Sent from my Nexus 7 using xda app-developers app
i bricked my phone
:i cant get in recovery mode i have bricked my phone i was puting a costum rom on my phone stuck in boot logo and odin is not working please help :crying
allenw420 said:
:i cant get in recovery mode i have bricked my phone i was puting a costum rom on my phone stuck in boot logo and odin is not working please help :crying
Click to expand...
Click to collapse
Do you have the right drivers? Just download Samsung kies and it should be fixed
Sent from my Nexus 7 using xda app-developers app
Dvarl said:
Is it the galaxy exhibit 4G T679? It the original exhibit? There are multiple phones with the same name. Also wiping cache/dalvik cache and fix permissions will usually fix a problem like this.
Sent from my SGH-T679 using xda app-developers app
Click to expand...
Click to collapse
Hi Dvarl,
I'm extremely sorry but I forgot to bookmark the sight and finally decided to search my laptop history to find the thread. The phone is the newer model SGH-T679 galaxy exhibit, not the exhibit II. I have tried wiping the cache but i'm not sure exactly how to proceed to do all the procedures that you are talking about. It does not have cwm installed. I did manage to root it before I got myself in this mess.
I can assure you I will be checking the replies frequently and any help is appreciated.
theAPANT said:
What do you mean by reset to factory? Wiping data does not change the operating system. However do you have cwm installed and yea is it even the t679
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I would like to put it back to way it came out of the box or really I would like to have the newest OS on it. After that I think I could root it myself (after performing a backup). It does not have cwm installed on it. It is the newer 4G Exhibit not the exhibit II. Thanks for the reply and sorry I lost the forum and finally searched my history to find it.
Regards,
Les
patches0616 said:
I would like to put it back to way it came out of the box or really I would like to have the newest OS on it. After that I think I could root it myself (after performing a backup). It does not have cwm installed on it. It is the newer 4G Exhibit not the exhibit II. Thanks for the reply and sorry I lost the forum and finally searched my history to find it.
Regards,
Les
Click to expand...
Click to collapse
The t679 IS the exhibit 2 (although it was renamed the galaxy exhibit). The original exhibit aka just plain exhibit 4g t759 is the older model. It sounds like you have the t679 if that is correct, follow these instructions http://forum.xda-developers.com/wiki/Samsung_Galaxy_Exhibit_4G
Do not follow those instructions if you do not have that phone. Google if you are unsure about the phone you have because if done right for the right phone these steps are perfectly safe. If however you have the wrong phone you will ruin it pretty badly. On that cheerful note, good luck!
Sent from my Nexus 7 using xda app-developers app
theAPANT said:
The t679 IS the exhibit 2 (although it was renamed the galaxy exhibit). The original exhibit aka just plain exhibit 4g t759 is the older model. It sounds like you have the t679 if that is correct, follow these instructions http://forum.xda-developers.com/wiki/Samsung_Galaxy_Exhibit_4G
Do not follow those instructions if you do not have that phone. Google if you are unsure about the phone you have because if done right for the right phone these steps are perfectly safe. If however you have the wrong phone you will ruin it pretty badly. On that cheerful note, good luck!
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Wow that was a fast response! I have saved your link so I can try it. You are right, it is the renamed exhibit II. The startup screen used to say exhibit NOT exhibit II. I just wished I had backed it up before I made the big mistake. I have learned my lesson. I'll give it a shot tomorrow and let you know the results. Thanks again for your help, Les
I'm having the same problem. I tried odin but it's not working.. what am I missing?
What I do because it is much much faster IMHO, I would use Odin to put cwm back on the phone then download any ROM I want or the flash to stock, or even better if you followed the rules restore a nandroid
Sent from my SGH-T679 using xda app-developers app
theAPANT said:
The t679 IS the exhibit 2 (although it was renamed the galaxy exhibit). The original exhibit aka just plain exhibit 4g t759 is the older model. It sounds like you have the t679 if that is correct, follow these instructions http://forum.xda-developers.com/wiki/Samsung_Galaxy_Exhibit_4G
Do not follow those instructions if you do not have that phone. Google if you are unsure about the phone you have because if done right for the right phone these steps are perfectly safe. If however you have the wrong phone you will ruin it pretty badly. On that cheerful note, good luck!
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I do have the renamed t679. I must be doing something wrong. First I put it into restore mode and clear the cache then restart in download mode. Then I start the Odin Multi Downloader (Ancora) and insert into the OPS field the Ancora.ops then insert into the One Package field the T679LG3.tar file then hit start until all automatically finishes.
I am still left with a phone in the boot logo loop. I noticed when I wiped the cache and restarted the phone script said something about " unable to mount \system .... I didn't take a snapshot so I'm not exactly sure of what it was but I know the phone will not start up if it can't mount the system partition, at least I think I saw that somewhere in a thread.
Any suggestions? I wish I knew someone around Atlanta that I could join up with and get this thing working. I loved this phone and only used it for about a week. I'm thinking before all this is over I will be a phone geek instead of a newbie. All the information that I have gotten here is super helpful, I just don't know enough to effectively utilize it.
patches0616 said:
I do have the renamed t679. I must be doing something wrong. First I put it into restore mode and clear the cache then restart in download mode. Then I start the Odin Multi Downloader (Ancora) and insert into the OPS field the Ancora.ops then insert into the One Package field the T679LG3.tar file then hit start until all automatically finishes.
I am still left with a phone in the boot logo loop. I noticed when I wiped the cache and restarted the phone script said something about " unable to mount \system .... I didn't take a snapshot so I'm not exactly sure of what it was but I know the phone will not start up if it can't mount the system partition, at least I think I saw that somewhere in a thread.
Any suggestions? I wish I knew someone around Atlanta that I could join up with and get this thing working. I loved this phone and only used it for about a week. I'm thinking before all this is over I will be a phone geek instead of a newbie. All the information that I have gotten here is super helpful, I just don't know enough to effectively utilize it.
Click to expand...
Click to collapse
OK now use the volume up and power to get to a screen with a box and then hit menu that will bring you to a recovery and just click wipe data factory reset and you should be fine.
Sent from my Nexus 7 using xda app-developers app
theAPANT said:
OK now use the volume up and power to get to a screen with a box and then hit menu that will bring you to a recovery and just click wipe data factory reset and you should be fine.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I've tried that more than ten times to no avail. I get the feeling that the original OS may be corrupt or missing or maybe that "unable to mount" message that I saw.
patches0616 said:
I've tried that more than ten times to no avail. I get the feeling that the original OS may be corrupt or missing or maybe that "unable to mount" message that I saw.
Click to expand...
Click to collapse
OK well if it boots to the android icon with green fire or whatever then you have an os. My only advice is to make sure you check the right things when using Odin.
Edit: there is a very slim possibility that you have a fried emmc chip but I doubt it. Also make sure it says pass before you unplug
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 09:44 PM ---------- Previous post was at 09:20 PM ----------
How far do you boot to? How long does it take for Odin to finish?
Sent from my Nexus 7 using xda app-developers app
Odon does the same thing to me, it says pass but still boot loops, that's why I recommend just doing cwm through Odin and flash the b2s or any ROM you desire
Sent from my SGH-T679 using xda app-developers app
theAPANT said:
OK well if it boots to the android icon with green fire or whatever then you have an os. My only advice is to make sure you check the right things when using Odin.
Edit: there is a very slim possibility that you have a fried emmc chip but I doubt it. Also make sure it says pass before you unplug
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 09:44 PM ---------- Previous post was at 09:20 PM ----------
How far do you boot to? How long does it take for Odin to finish?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
When I run the Odin Multi Downloader program it takes 5 mins and 38 secs to finish. The phone restore Odin is fairly fast when I reset to factory settings but I've never timed it. The phone boots to the t-mobile exhibit screen just beyond the plain white Samsung start up screen.
patches0616 said:
When I run the Odin Multi Downloader program it takes 5 mins and 38 secs to finish. The phone restore Odin is fairly fast when I reset to factory settings but I've never timed it. The phone boots to the t-mobile exhibit screen just beyond the plain white Samsung start up screen.
Click to expand...
Click to collapse
Hmm when I've done it it took about 10min, so perhaps the 300 sec reset option is not set. Try what tazmanion said by using Odin to flash cwm and then you can Mount system in revovery
If it doesn't get to boot animation then yea you have no os
Sent from my Nexus 7 using xda app-developers app
I'm also still having bootloop issues, I wiped cache/dalvik, fixed permissions, wiped battery stats, etc. but best it did was sit on the SAMSUNG for like 2 minutes then go back into a bootloop.
I'd like to keep the original rom/system in tact to not loose any data (didn't backup beforehand, I know...) anyone have suggestions?
Thanks in advance.
(yes this is crossposted, need answer asap, sorry)
You do not have a ROM if it sits in Samsung
Sent from my SGH-T679 using xda app-developers app
Long story short, I was trying to install Dynamic Kat but it wouldn't work. Each time I would try to install SS 3.72, it wouldn't boot into recovery. If I tried to flash the ROM with SS 3.70, the ROM wouldn't boot--it would just get stuck on a black screen with a blue LED. I was advised to flash Odin and start over. I've been trying to flash stock with several files, however nothing is working (N900AUCUBMI9_OneClickBin.exe). It fails everytime.
Anybody know what I can do to resolve this issue? Needless to say, my phone is soft-bricked at the moment.
Are you able to get into safe strap at all?
As in safe strap recovery.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Thank you for your response.
I actually got it resolved. I was on a ROM which I thought was 4.4.2, however it was 4.3 so it was causing a bunch of problems. All sorted out now
Glad you got it figured out.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
So I have an LG G2 that I used AutoRec on and it flashed a different kernel not compatible with the display type. I flashed the stock ROM back thinking it would fix the problem but it did not. Does anyone know how to flash the right kernel for the display? I've been looking but it seems I'm going to have no luck since I just flashed back to stock and I need root and a custom recovery to do so. Any help would be appreciated, thanks.
Pictures of my problem below.
Sent from my SM-N900V using XDA Free mobile app
mexicanhobo said:
So I have an LG G2 that I used AutoRec on and it flashed a different kernel not compatible with the display type. I flashed the stock ROM back thinking it would fix the problem but it did not. Does anyone know how to flash the right kernel for the display? I've been looking but it seems I'm going to have no luck since I just flashed back to stock and I need root and a custom recovery to do so. Any help would be appreciated, thanks.
Pictures of my problem below.
Sent from my SM-N900V using XDA Free mobile app
Click to expand...
Click to collapse
The OP has a link under the warning to get the JDI version. http://forum.xda-developers.com/showthread.php?t=2715496 Read ,read, read. There's also a tool in G2 Android Development that will detect if your pannel is LGD or JDI.
Sent from my XDABBEB VS98025A v2.0.0 using XDA free mobile app
I have looked through that whole thread and it seems you need to be able to use recovery and have root permission. Most of them claim to have only a few lines but they are still able to see their screen. Mine stays how it looks in the picture 100% of the time. I used the TOT method before to flash it back to stock but it seems that didn't do anything to fix it, that's why I'm asking on this forum. Since it's complete stock and I have no way of seeing what's going on on the display. For some reason it seems to boot up into download mode also without me doing anything but turning it on. If you have any experience with this issue could you inform me about it? Thanks, man.
Sent from my SM-N900V using XDA Free mobile app
mexicanhobo said:
I have looked through that whole thread and it seems you need to be able to use recovery and have root permission. Most of them claim to have only a few lines but they are still able to see their screen. Mine stays how it looks in the picture 100% of the time. I used the TOT method before to flash it back to stock but it seems that didn't do anything to fix it, that's why I'm asking on this forum. Since it's complete stock and I have no way of seeing what's going on on the display. For some reason it seems to boot up into download mode also without me doing anything but turning it on. If you have any experience with this issue could you inform me about it? Thanks, man.
Sent from my SM-N900V using XDA Free mobile app
Click to expand...
Click to collapse
Can you get into recovery? Try grabbing the kernel here and flashing it.
http://forum.xda-developers.com/showpost.php?p=51974589&postcount=281
Otherwise if the screen is like this 100% of the time, I'd say it's farked, use the return to stock guide and take it back for a replacement.
Thank for replying, unfortunately that is the answer to my question. It is like that 100% of the time and I flashed stock back on to it thinking it would fix the problem. This leaves me with a messed up screen and a phone without any root or custom recovery. I will ask, is it possible to flash a kernel in stock somehow with adb or anything of the sort? I have already sent it in for a replacement so I don't think I will be able to send it in again.
Sent from my SM-N900V using XDA Free mobile app
Hi I have an A&TT S900A. I just installed Unity Rom and upon reboot all is the S-5 Boot screen without ever getting to safestrap. How can I fix this?
I can tell you the same thing hapenned to me and going back to stock was my only option. The only thing to remember here though is that the file to odin back to stock will wipe everything off your internal memory, so you should probably make a back up of your internal memory first if you can. Good luck man.
Sent from my SM-G900A using XDA Premium 4 mobile app
Thanks a lot. I don't see an Odin return to stock thread specific to this model, so I assume it's pretty standard and will look for just a general walk through online.
ok odin worked fine, now to try if I can get this rom to install again... Thanks for the help!