I was trying to install Wanamlite through TWRP, but I did a couple things wrong. I have flashed custom ROMS before, but I think I was just careless this time.
The things I did wrong are:
I installed the wrong kernel, I used this one KT747-TW-JB-4.1.2-ATT-05-31-2013.zip for the GS3.
I did not click "reboot" after install of the ROM and kernel, I held down the power button. Don't know what I was thinking!
I then tried the factory ROM through ODIN as discussed in this thread http://forum.xda-developers.com/showthread.php?t=2261573, everything in ODIN told me things were going smooth. Now when my phone tries to boot up it just vibrates every few seconds repeatedly with nothing displaying on the screen.
I thought my phone was supposed to boot right up after installation!! Any ideas?
It will be better to keep the discussion to this thread instead of the ODIN thread. However, here is a thread...
http://forum.xda-developers.com/showthread.php?t=2327226
...with a very similar issue to yours. If you definitely can't get into recovery (keep trying different key combinations and timing) and Odin doesn't work, you appear to be screwed at the moment. Maybe you can try some ADB options. You will need to search for information about it and there is no guarantee it will help you.
Unless something else surfaces, Jtag repair might be the only option. You can search for information about that as well. Good luck.
scott14719 said:
It will be better to keep the discussion to this thread instead of the ODIN thread. However, here is a thread...
http://forum.xda-developers.com/showthread.php?t=2327226
...with a very similar issue to yours. If you definitely can't get into recovery (keep trying different key combinations and timing) and Odin doesn't work, you appear to be screwed at the moment. Maybe you can try some ADB options. You will need to search for information about it and there is no guarantee it will help you.
Unless something else surfaces, Jtag repair might be the only option. You can search for information about that as well. Good luck.
Click to expand...
Click to collapse
Thank you, I treid the button combinations but sadly I don't think that's the problem. I'll try some ADB options and look closely at some other threads. Looks like I'll have to reactivate my iPhone 5 until I get this problem sorted out! What a bummer!
so you're able to get into download mode but not recovery, correct?
xBeerdroiDx said:
so you're able to get into download mode but not recovery, correct?
Click to expand...
Click to collapse
Yes that's completely correct!
since you've already flashed back to stock via odin, i want you to try booting into recovery again. just to start from the beginning and cover all the bases.
pull the battery and wait a few seconds
reinsert the battery and immediately press the recovery combo: vol up + home + power (in that order). release just the power button as soon as your device vibrates while still holding down vol up and home.
if this does not get you into recovery initially, try the method a few more times and report back.
if this does get you into recovery, wipe data/factory reset, wipe cache and reboot.
Thank you for the thorough instructions. However, it did not work. I tried 12 times with no success.
Phone just kept vibrating every few seconds and would not go into recovery.
until we find out a little bit more about this issue, i personally dont have much advise to offer. are you familiar with adb?
scott14719 linked a thread pertaining to your issue. i'm sure you read it and see that you're the only one in this situation.
i will continue to do some research.
Isn't there a Kies emergency recovery or something. Just putting it out there.
hamzer11 said:
Isn't there a Kies emergency recovery or something. Just putting it out there.
Click to expand...
Click to collapse
Yep, but kies has to recognize the phone, which is hit and miss. If kies recognizes the phone, it would be worth a try.
Try to flash your carrier rom again using odin. Download links can be found here http://www.sammobile.com/firmwares/ once you get the PASS in odin your phone may still be stuck in a bootloop. As xBeerdroiDx mentioned , try removing the battery then go into recovery and restore to factory settings. I had the same problem with twrp ,I was stuck in a bootloop , no restore , no boot nothing. My phone is working now thank god.
Try this and report back
---------- Post added at 12:53 AM ---------- Previous post was at 12:52 AM ----------
I also found an old thread on XDA suggesting that it could be a hardware problem with your power button http://forum.xda-developers.com/showthread.php?t=2311660
Related
Hey everyone!
I have never posted anything on a forum before, so please tell me if I do anything wrong. I have searched everywhere to find a solution for my problem, but I found nothing.
Today I accidentally got into the Samsung Recovery Utils of my galaxy 3. I have done nothing to the phone, all original, nothing flashed or rooted. But now I can't get out of this mode, if I restart the phone it automatically goes back into it.
Does anyone know how to get out of there?
Thank you a lot for helping me!
And I hope that this is the right forum to ask this question, as I said, I have never posted in a forum before.
Usually you should be able to reboot from recovery mode. Scroll to reboot Phone with the Volume Keys and klick with the Home Key... Your phone should restart.
Otherwise remove the battery, wait a few moments, plug the battery back in and try it again.
Good Luck
Thank you, I tried both several times, but I always end up in the recovery mode... I have no idea how i can get out of there! Do you maybe know something else I could do?
do the battery thing mentioned above. turn on your phone with vol up+ vol down+home +power (hold them for a while) and then try rebooting from the menu
here's the solution
Pilzwachtel said:
Hey everyone!
I have never posted anything on a forum before, so please tell me if I do anything wrong. I have searched everywhere to find a solution for my problem, but I found nothing.
Today I accidentally got into the Samsung Recovery Utils of my galaxy 3. I have done nothing to the phone, all original, nothing flashed or rooted. But now I can't get out of this mode, if I restart the phone it automatically goes back into it.
Does anyone know how to get out of there?
Thank you a lot for helping me!
Click to expand...
Click to collapse
Hey.. If ur on a Android 2.1 firmware and stuck on recovery every time...
just use the volume keys and chose the option "reboot" ... by the way.. its on default there.
after that just press the central key or called the "home key" two times consecutively..
ur good to go
I tried this several times, but I always end up in the Recovery Menu. When I pull out the battery, restart the phone and hold all those buttons including the power button my phone shows the Samsung Galaxy Logo and then reboots again, and then shows the Logo and reboots again. Only without holding the power button, and only the other ones I get into the Recovery Menu again. I really hope there is a way to get out of this mode! Thank you for all your help so far!
Hey I just saw the post in front of my other one
So yes I'm on Android 2.1 if that helps. And I tried this method several times, but when my phone restarts I always end up in the recovery mode by pressing nothing.
But thank you
try wipeing data and cache
I tried that out, but still rebooted into recovery mode all the time.
Because I couldn't find anything that solved my problem I just decided to flash my phone to a newer original firmware via odin. I just finished flashing and everything works fine as it did before, till now tho. I used the tutorial that is on this forum for flashing my I5800 and it worked perfectly fine, thank you for everyone's help anyway!
Now I hope that they will soon bring back froyo on kies, because it was deleted from the servers again today in Germany so I can't update. Hope that will happen soon!
I would recommend to forget about KIES... I am sorry but this software is a piece of crap!
Keep using the Odin Flasher. If you have some spare time install gsams nice lagfix and be happy about a very fast Froyo I5800
Edit:
Another funny thing about Kies: You can download the current version by using a US Proxy Server, which is also free of these annoying error messages at startup. But still there are much better alternatives, and the newest version (Kies 5 I think) is also incompatible to the I5800 Phone :-/
Yes, I really hate kies, that software is nothing good!
I think I will follow your advise to continue using odin flasher. Which froyo version is the best to install? I still have 2.1 on my phone. and then how do you install that lagfix? Sorry for all those questions, but I'm new to all this.
Sent from my GT-I5800 using XDA App
you are new to this? ok, then go to the development section and see the READ FIRST thread
I have already read through those threads, I just meant that I just started some days ago, I'm not a pro, I'm only someone who just started haha
So today I flashed to xxjpf froyo and I'm having no problems so far. everything is fine so my problem is solved and in addition I have froyo now
Sent from my GT-I5800 using XDA App
...but after flashing hundreds of times I've never had this problem before.
Flashed one of intratech's frankenstein roms (GT-I9100_XEU_I9100XWKJ3_I9100XEUKH2_I9100XXKI3.tar.md5) and it just stayed on the booting page for seriously more than an hour.
Went back to download mode and flashed the kernel that goes with it (Kernel_I9100XWKJ3.tar.md5) and now I have no recovery mode and no download mode!
I do know how to get into both modes, it just isn't doing it. Instead of going into download or recovery, it just tries to boot as normal, so it's properly stuck.
Not sure Samsung would take kindly to me walking into their service centre with a custom rom etc, what do you reckon?
Try to buy a USB JIG off ebay, plug it in to see if it works
Sent from my GT-I9100 using xda premium
JUST done that actually lemin, thanks.
I guess if that doesn't work I'll have to take it to be fixed.
Wonder what could have gone wrong with the flashing...
Have you tried to remove the battery?
Sent from my GT-I9100 using xda premium
Seems all you needed in the first place is a factory reset from recovery, if the phone is trying to boot, it means the boot partition is intact and you are probably not executing the button combination properly.
Hold Volume up and home, then press power, keep holding the buttons until you are in recovery mode, then do a factory reset and reboot, enjoy your phone
Achilles, you might have thought so, and I wouldn't normally rule out the possibility of me being a dumbass, but really there is no recovery or download mode available. It just doesn't go into either. :-(
fergusstrachan said:
Achilles, you might have thought so, and I wouldn't normally rule out the possibility of me being a dumbass, but really there is no recovery or download mode available. It just doesn't go into either. :-(
Click to expand...
Click to collapse
You are not being a dumbass, just probably not timing the button presses correctly, if you don't hold those three buttons down until the recovery is actually on the screen, the phone will try to boot normally, talking from experience here
If you are doing this but the phone is still trying to boot normally, then a jig might be the only way to force download mode as you have said that it is trying to boot, so the partitions are intact, a full brick shouldn't boot at all....
Also, I flashed the same ROM, it is not really a custom ROM in the true sense, just a stock ROM with different CSC and MODEM, I really doubt "they" can call that a custom ROM and I doubt they would be able to tell anyway, "it's all stock parts" so long as you didn't flash any custom kernels or anything.
Good Luck.......
Just my humour achilles.
Trust me, as sure as I am about putting one foot in front of the other to walk, I know how to get this baby into download/recovery mode, and it aint playing.
Jig, then service centre it is. Until then, have to use the Galaxy Tab a la Dom Joly.
I have a phone I am fixing for a friend, so I don't have a complete accurate history of what happened, so please bare with me.
Basically, you put the battery in and it boots right to download mode (Factory Mode), no power button required. I can then reboot it using the power, hold down the Vol-Down button and then I am prompted if I want to enter D/L mode, in which you can use Vol-Down to cancel and it boots like normal.
I have tried the following, nothing fixes it!
Factory Wipe
Root using CF-Auto Root
Every Key Combination Possible on Boot
Odin Stock Install
Kies Upgrade (just stalls on that)
It was not rooted when I got it, and now it is. I haven't installed any recovery yet, but am willing too. It has possible water damage, so it ain't going back to the store anytime soon. I can't even get USB Debugging to appear that it is connected, nor will ADB recognize it. But the USB is working and read/writing.
This isn't my first time working with this sort of stuff, I am just at my wits end, plus I'm a Sony/HTC/LG person, so if there is something I am missing with this wonderful(ly crappy) bootloader, let me know.
Thanks in advance!
shroomun said:
I have a phone I am fixing for a friend, so I don't have a complete accurate history of what happened, so please bare with me.
Basically, you put the battery in and it boots right to download mode (Factory Mode), no power button required. I can then reboot it using the power, hold down the Vol-Down button and then I am prompted if I want to enter D/L mode, in which you can use Vol-Down to cancel and it boots like normal.
I have tried the following, nothing fixes it!
Factory Wipe
Root using CF-Auto Root
Every Key Combination Possible on Boot
Odin Stock Install
Kies Upgrade (just stalls on that)
It was not rooted when I got it, and now it is. I haven't installed any recovery yet, but am willing too. It has possible water damage, so it ain't going back to the store anytime soon. I can't even get USB Debugging to appear that it is connected, nor will ADB recognize it. But the USB is working and read/writing.
This isn't my first time working with this sort of stuff, I am just at my wits end, plus I'm a Sony/HTC/LG person, so if there is something I am missing with this wonderful(ly crappy) bootloader, let me know.
Thanks in advance!
Click to expand...
Click to collapse
If you can hold the vol-down and home button when you boot it up and get into Odin mode you should be about to flash the stock MD5 for your phone. Stock Canadian Odin files here:
http://forum.xda-developers.com/showthread.php?t=2269304
Also make sure to use the lastest version of Odin, 3.07 I believe. After you are done flashing with Odin you will have to boot into Recovery (vol-up when booting) and do a factory reset. This has always fixed any boot problems with my phone.
Jdiesel87 said:
If you can hold the vol-down and home button when you boot it up and get into Odin mode you should be about to flash the stock MD5 for your phone. Stock Canadian Odin files here:
http://forum.xda-developers.com/showthread.php?t=2269304
Also make sure to use the lastest version of Odin, 3.07 I believe. After you are done flashing with Odin you will have to boot into Recovery (vol-up when booting) and do a factory reset. This has always fixed any boot problems with my phone.
Click to expand...
Click to collapse
So did you go into settings, more, developer mode to check usb/debug?
USB debugging isn't required to flash the Odin MD5. One thing I did notice is that you should boot into Odin download mode before connecting your USB cable. I was having issues with Odin not detecting my phone and waiting to connect the USB cable solved that.
Sent from my Nexus 7 using xda app-developers app
sloanster said:
So did you go into settings, more, developer mode to check usb/debug?
Click to expand...
Click to collapse
Duh...
I was referring going to adb fastboot
see the thing is that flashing did work fine, it just didn't fix the problem. I guess in Samsung terms I am stuck in Odin download mode when turning the phone on. This is why I wanted to see of I could push some standard reboot command via adb to see of it would "jig" it into place, but no matter what I try it always boots into download mode first.
and yes, I did turn on usb debugging
shroomun said:
see the thing is that flashing did work fine, it just didn't fix the problem. I guess in Samsung terms I am stuck in Odin download mode when turning the phone on. This is why I wanted to see of I could push some standard reboot command via adb to see of it would "jig" it into place, but no matter what I try it always boots into download mode first.
and yes, I did turn on usb debugging
Click to expand...
Click to collapse
Could you have bent pins maybe where you plug it in? Its doing exactly what a jig would do..
TheAxman said:
Could you have bent pins maybe where you plug it in? Its doing exactly what a jig would do..
Click to expand...
Click to collapse
Nothing is wrong with the pins, USB is working fine and can be used in any other mode. I got ADB finally, I guess it was just not playing nice with me before. However, still anything I try the bloody thing still insists on booting first into download mode.
Just an update, it is still booting into download mode, tried a couple different stocks and still no good result. Anyone suggest any of the options in Odin might help work? Like F Reset Time or Phone EFS Clear?
shroomun said:
Just an update, it is still booting into download mode, tried a couple different stocks and still no good result. Anyone suggest any of the options in Odin might help work? Like F Reset Time or Phone EFS Clear?
Click to expand...
Click to collapse
I have seen this elsewhere, one guy suggested, using Keis, and it took him 2-3 times to get the stock to stick.
As far as checking those items in odin, could brick the phone. he also said, he got nowhere using odin in this situation.
Have you tried maybe flashing a recovery via odin? could be the recovery is corrupt.
what does this mean: in which you can use Vol-Down to cancel and it boots like normal. <<< Can you boot to the OS?
I can imagine your frustration here...good luck.
I did try Kies and it would keep getting stuck at 10% (I let it sit overnight) so I had no luck with that...
Have you tried maybe flashing a recovery via odin? could be the recovery is corrupt.
what does this mean: in which you can use Vol-Down to cancel and it boots like normal. <<< Can you boot to the OS?
Click to expand...
Click to collapse
Yes, I have gone from stock recovery to CMW and back to Stock and still nothing. As for you other question, yes, I can boot into Android. The downside is I can't turn the phone off unless the battery is pulled out. This is why I bought an HTC One and not an S4 lol .. thank god this isn't my phone, but it is frustrating because of all the things I've tried to do to fix it.
Hello, I tried searching for this but came up empty. I have a completely stock Nexus 4, received the OTA push for 4.3. Phone has never been rooted. After going through the install process it showed the android on it's back with a red triangle and said error. After a restart the phone just sits at the Google screen!!! I'm I boned or is there a fix for this? Any info would be greatly appreciated! Thank you!
Jesmuris said:
Hello, I tried searching for this but came up empty. I have a completely stock Nexus 4, received the OTA push for 4.3. Phone has never been rooted. After going through the install process it showed the android on it's back with a red triangle and said error. After a restart the phone just sits at the Google screen!!! I'm I boned or is there a fix for this? Any info would be greatly appreciated! Thank you!
Click to expand...
Click to collapse
Try going into fastboot and flashing the stock rom from google.
gmaxpwnage said:
Try going into fastboot and flashing the stock rom from google.
Click to expand...
Click to collapse
Not sure what mode I entered, Held vlm down + power. Says Fastboot Mode in red with a big green Start at the top. Options it gives me is Start, restart bootloader, recovery mode, and power off. If I try to enter Recovery mode it says no command. Don't see anything that allows me to reinstall
Jesmuris said:
Not sure what mode I entered, Held vlm down + power. Says Fastboot Mode in red with a big green Start at the top. Options it gives me is Start, restart bootloader, recovery mode, and power off. If I try to enter Recovery mode it says no command. Don't see anything that allows me to reinstall
Click to expand...
Click to collapse
Ok, found out on the no command screen I can hold power and hit vlm up and it brings me to system recovery with these options. Reboot system, apply update from ADB, wipe data/factory reset, wipe cache partition.
Not sure what to do sadly
Try following step:
1. Press Vol up and down and powerbutton same time to get to the fastboot mode as you mention.
2. Choice Recovery Mode and press power button. If you got luck you will see an android guy with red mark on the screen.
3. Press Vol Up and Power button same time for while don't let go it will pop up a list of option clean the cache and do factory reset, then reboot system.
If this method not working. Then hard method is flash your Nexus 4 with fastboot. Search the forum there few people already post how to flash 4.3 ROM with fastboot
Johnsonyc said:
Try following step:
1. Press Vol up and down and powerbutton same time to get to the fastboot mode as you mention.
2. Choice Recovery Mode and press power button. If you got luck you will see an android guy with red mark on the screen.
3. Press Vol Up and Power button same time for while don't let go it will pop up a list of option clean the cache and do factory reset, then reboot system.
If this method not working. Then hard method is flash your Nexus 4 with fastboot. Search the forum there few people already post how to flash 4.3 ROM with fastboot
Click to expand...
Click to collapse
Ok thank you, trying this now will update:good:
Didn't work Will try other method
Jesmuris said:
Didn't work Will try other method
Click to expand...
Click to collapse
Sorry to hear this bad news Hope the other method work for you!
Well, first try, couldn't get my PC to recognize fastboot in adb. Was getting frustrated beyond hell and had to walk away for a bit. Came back about an hour later and for some reason it finally recognized it... Back to the start screen like when I first bought the phone. So far working ok, except for being able to log into my google account... 2-step verification giving me issues now lol. Thank you again for your assistance. Very much appreciated!!:good::good:
Jesmuris said:
Well, first try, couldn't get my PC to recognize fastboot in adb. Was getting frustrated beyond hell and had to walk away for a bit. Came back about an hour later and for some reason it finally recognized it... Back to the start screen like when I first bought the phone. So far working ok, except for being able to log into my google account... 2-step verification giving me issues now lol. Thank you again for your assistance. Very much appreciated!!:good::good:
Click to expand...
Click to collapse
I had a similar experience (kind of). I had issues side-loading 4.2.2 -> 4.3 on my N4. After it finished update and rebooted I got a black screen and nothing more. I ran through it and tried to update to 4.3 again, and then it worked.
Even though it worked I've been noticing issues with it. For example, I now can no longer uninstall anything. When I attempt to uninstall any app, the phone reboots. I'm backing up now with Titanium and am about to flash. I was hoping there would be a quick fix here, but such is life. Viva la impatience.
I have same problem my stock 4.2.2 stuck x boot load , did vol up+dwn +power now stuck in "Download Mode" do not unplug the device until the process is complete .
oneguy77 said:
I have same problem my stock 4.2.2 stuck x boot load , did vol up+dwn +power now stuck in "Download Mode" do not unplug the device until the process is complete .
Click to expand...
Click to collapse
This is what I eventually followed to get mine working. I just did scenario 2 and that worked perfectly for me, so far no issues, just having to get things back to where I had them before. The second link is actually more detailed. Just make sure you follow step by step. I guess i could have not done step D10 but wanted to make sure this route worked for me. Thank you again for those who pointed me in the right direction
http://www.androidpolice.com/2013/0...-to-android-4-3-jwr66v-and-root-it-right-now/
http://forum.xda-developers.com/showpost.php?p=34552123&postcount=1
Jesmuris said:
Well, first try, couldn't get my PC to recognize fastboot in adb. Was getting frustrated beyond hell and had to walk away for a bit. Came back about an hour later and for some reason it finally recognized it... Back to the start screen like when I first bought the phone. So far working ok, except for being able to log into my google account... 2-step verification giving me issues now lol. Thank you again for your assistance. Very much appreciated!!:good::good:
Click to expand...
Click to collapse
I have the exact same problem but not sure how to get my PC to recognize fastboot in adb mode...
FYI if you flash to stock android 4.3 and you have the 16 GB Nexus 4, make sure that after you re-flash you have the full 16 GB and not 8 GB (unless you want to re-setup your phone twice like me). If you get this problem you can wipe cache and data from recovery and voila, all of your free space is back.
---------- Post added at 10:52 PM ---------- Previous post was at 10:44 PM ----------
zpilot said:
I have the exact same problem but not sure how to get my PC to recognize fastboot in adb mode...
Click to expand...
Click to collapse
If this is what I think it is, I was having the same problem. If I went into Control Panel on my PC and it would say that the driver is failing to load. To fix this I uninstalled the driver, rebooted, reinstalled Google USB Driver from the Android SDK Manager, restarted, and all was well after that.
I really have no explanation for why this fixed it, or it didn't work before, because other than fastboot, everything was working flawlessly with getting my phone to communicate with my PC.
I have a Verizon Galaxy Note 3 (SM-N900V) that is stuck in a boot loop. I get "RECOVERY BOOTING" in blue at the top left corner of the screen. No combination of power, volume up, volume down, or home buttons have any effect. I've tried all combinations. I have to pull the battery to get it out of the boot loop. Any advice?
Toaplan said:
I have a Verizon Galaxy Note 3 (SM-N900V) that is stuck in a boot loop. I get "RECOVERY BOOTING" in blue at the top left corner of the screen. No combination of power, volume up, volume down, or home buttons have any effect. I've tried all combinations. I have to pull the battery to get it out of the boot loop. Any advice?
Click to expand...
Click to collapse
Were you running Safestrap and a custom ROM... or were you totally stock before the phone started bootlooping and did you try to flash anything through Odin or Safestrap before it started? What build version is your phone on (4.4.2, 4.4.4, etc...)? Can you still get into Odin mode?
If you could provide some information, it should help others to give you some suggestions.
If you were rooted and had Safestrap installed, then this thread might provide some useful information to help you get the phone out of the bootloop. If your situation is similar to the others in the linked thread and you think that flashing the NC2 Kernel might get you out of the bootloop... then you should be able to grab the NC2 kernel from Beanstown106’s thread here.
You should also check out Droidstyle's restore guide here, which should help you restore the phone back to factory stock if necessary.
mattnmag said:
Were you running Safestrap and a custom ROM... or were you totally stock before the phone started bootlooping and did you try to flash anything through Odin or Safestrap before it started? What build version is your phone on (4.4.2, 4.4.4, etc...)? Can you still get into Odin mode?
If you could provide some information, it should help others to give you some suggestions.
If you were rooted and had Safestrap installed, then this thread might provide some useful information to help you get the phone out of the bootloop. If your situation is similar to the others in the linked thread and you think that flashing the NC2 Kernel might get you out of the bootloop... then you should be able to grab the NC2 kernel from Beanstown106’s thread here.
You should also check out Droidstyle's restore guide here, which should help you restore the phone back to factory stock if necessary.
Click to expand...
Click to collapse
Hey thanks for the help. I was running Safestrap and the leaked KitKat 4.4.2. There's not much more to say other than in my first post. It just kind of randomly starting happening. All recovery options are failing because I can't get any combination of button presses to register when it's first booting up. This means I can't get into odin mode, bootloader, recovery... anything.
Toaplan said:
Hey thanks for the help. I was running Safestrap and the leaked KitKat 4.4.2. There's not much more to say other than in my first post. It just kind of randomly starting happening. All recovery options are failing because I can't get any combination of button presses to register when it's first booting up. This means I can't get into odin mode, bootloader, recovery... anything.
Click to expand...
Click to collapse
If holding the volume down + home + power buttons all together doesn't work any more to boot the phone into download mode, then it might be worth trying a usb jig to see if it would force the phone into download mode. Here's a listing for a usb jig on eBay that is less than $5 and the seller seems to have good feedback. The listing says it should work on a Note 3. If you'd rather make your own usb jig, there are several guides on YouTube and xda on how to make one.
Before trying the jig... here's an idea to get the phone into download mode...(it probably won't work, but shouldn't hurt anything to try)-- Take the battery out of the phone, then with the micro usb cable plugged into the phone, hold the volume down button on the phone and plug the other end of usb cable into the computer. Hopefully that will turn the phone screen on and prompt you to hit the volume up button to enter download mode.
If you can't get into download mode, then you might see if the Verizon Repair Assistant or Kies Emergency Firmware Recovery would work to restore the phone while in bootloop. I read someone else's post where they said that when using the Repair Assistant, they accidentally updated their phone to 4.4.4, so you'll probably want to research that more before using it so you don't lose ability to root.
If none of these things work, then I can't think of any other ideas other than sending it to someone for jtag repair. Maybe someone else can chime in with some other suggestions.
@Toaplan,
If you haven't been able to fix your phone yet, I was thinking you may also want to check this unbrick thread: ( http://forum.xda-developers.com/showthread.php?p=54534374 ). Per info in the thread... it sounds like jtag isn't an option for our version of the note 3, so please disregard my above comment about jtag.
mattnmag said:
If holding the volume down + home + power buttons all together doesn't work any more to boot the phone into download mode, then it might be worth trying a usb jig to see if it would force the phone into download mode. Here's a listing for a usb jig on eBay that is less than $5 and the seller seems to have good feedback. The listing says it should work on a Note 3. If you'd rather make your own usb jig, there are several guides on YouTube and xda on how to make one.
Before trying the jig... here's an idea to get the phone into download mode...(it probably won't work, but shouldn't hurt anything to try)-- Take the battery out of the phone, then with the micro usb cable plugged into the phone, hold the volume down button on the phone and plug the other end of usb cable into the computer. Hopefully that will turn the phone screen on and prompt you to hit the volume up button to enter download mode.
If you can't get into download mode, then you might see if the Verizon Repair Assistant or Kies Emergency Firmware Recovery would work to restore the phone while in bootloop. I read someone else's post where they said that when using the Repair Assistant, they accidentally updated their phone to 4.4.4, so you'll probably want to research that more before using it so you don't lose ability to root.
If none of these things work, then I can't think of any other ideas other than sending it to someone for jtag repair. Maybe someone else can chime in with some other suggestions.
Click to expand...
Click to collapse
mattnmag said:
@Toaplan,
If you haven't been able to fix your phone yet, I was thinking you may also want to check this unbrick thread: ( http://forum.xda-developers.com/showthread.php?p=54534374 ). Per info in the thread... it sounds like jtag isn't an option for our version of the note 3, so please disregard my above comment about jtag.
Click to expand...
Click to collapse
Hey mattnmag,
Thanks for all the suggestions! This phone isn't my daily driver and I haven't been able to try any of this yet. I'll let you know how I make out when I get a chance to try some of this out. Thanks!