Related
I've made some of mistakes and now I need your help determining if I'm screwed or if there's a solution.
1st Mistake: I let my new VZ GS4 update to MJ7.
2nd Mistake: I thought I found a guide to get a rooted MJ7 so I tried using Odin to flash VRUDMI1...which errored.
Well that didn't work. Time to reboot...except now it wont boot. Now it displays:
Firmware upgrade encountered an issue. Please select recover mode in Kies & try again.
At least it's suggesting a solution, right? So I download Kies 3. It connects. I follow a guide which tells me how to re-initialize the firmware.
1. I enter the model "SCH-I545"
2. I enter the IMEI
3. The firmware downloads
4. Nothing. It eventually gives an error that it can't connect.
I've tried that on multiple computers with various cables with the same results.
So do I go back to Staples where I got it on Black Friday and tell them that my phone stopped working?
First off youre in wrong forum. Questions go in the questions section. You need to download the stock mj7 image and flash it in odin.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
I did the same thing was up all night finally found out about Kies but it worked for me. Once you update to mj7 you can't go back. my problem with odin was I was trying to go back to me7 so I have mj7 odin image to try if it happens again.
Sent from my SCH-I545 using Tapatalk
Sorry about posting in the wrong area. I knew better, but was completely exhausted when I made the thread and didn't think about it.
If anyone else makes the same mistake I did, I'm back up and running after downloading SCH-I545_VZW_1_20131023084910_v4vth34m5z_fac.zip and flashing with Odin.
I have a Verizon galaxy note II, and had been running AllianceROM.
AllianceROM seemed to be running pretty good until one day when my accelerometer stopped working. I thought it may be a software bug, so I tried to reflash the ROM. I got a bootloop, and tried again.
I tried to flash cyanogenmod 11 and still got a bootloop. Then I realized I didn't have a safe backup.
I attempted to flash some stock firmware through ODIN, since I couldn't get anything to work through cwm.
In the end, I'm stuck with a note II that can't boot. When I try to turn it on, I see the galaxy note II logo, but then the screen goes black (not off, I have to pop the battery out before I can try again.) Power+home+volume up now brings me to android system recovery/manual mode, and power+home+volume down gets me to ODIN mode.
Any suggestions or help would be greatly appreciated. I really wasn't planning on getting a new phone at this point, so I hope it's not beyond fixing! Thanks in advance.
Ethan,
It sounds like you should be able to fix your device if you are careful. If you can boot into the stock recovery using power+ home + volume up buttons, then do a factory reset and wipe cache... that might fix your problem and let the device boot up normally.
You should also check out Droidstyle's restore guide at this link: http://forum.xda-developers.com/showthread.php?p=34891181. His guide has links and detailed instructions on how to restore back to stock. (Hit the thanks button for him too... as he spent a lot of time making the guide).
Remember that 4.1.2 is the last build that allows us to unlock our bootloader, so don't restore the device to 4.3 or 4.4.2 unless you want to permanently lock your bootloader. Also, there's no current root method for our phones if they get updated to stock 4.4.2, so don't odin that unless you decide you don't want root and custom ROM'S anymore.
Good luck!
mattnmag said:
Ethan,
It sounds like you should be able to fix your device if you are careful. If you can boot into the stock recovery using power+ home + volume up buttons, then do a factory reset and wipe cache... that might fix your problem and let the device boot up normally.
You should also check out Droidstyle's restore guide at this link: http://forum.xda-developers.com/showthread.php?p=34891181. His guide has links and detailed instructions on how to restore back to stock. (Hit the thanks button for him too... as he spent a lot of time making the guide).
Remember that 4.1.2 is the last build that allows us to unlock our bootloader, so don't restore the device to 4.3 or 4.4.2 unless you want to permanently lock your bootloader. Also, there's no current root method for our phones if they get updated to stock 4.4.2, so don't odin that unless you decide you don't want root and custom ROM'S anymore.
Good luck!
Click to expand...
Click to collapse
I just tried following that guide, installing the .pit file and the suggested stock firmware, but Odin reported "FAIL" instead of "PASS."
Now when I try to turn my phone on or go to stock recovery, I get the message "Firmware upgrade encountered an issue. Please use Software Repair Assistant & try again."
Any hope left?
Ethan.S said:
I just tried following that guide, installing the .pit file and the suggested stock firmware, but Odin reported "FAIL" instead of "PASS."
Now when I try to turn my phone on or go to stock recovery, I get the message "Firmware upgrade encountered an issue. Please use Software Repair Assistant & try again."
Any hope left?
Click to expand...
Click to collapse
Yes, there's still hope to fix it if you can get the phone into download mode.
Here's some info to clarify before you try something else.... What firmware did you try to install when you used Droidstyle's guide? Also, in your initial post, you said "I attempted to flash some stock firmware through ODIN, since I couldn't get anything to work through cwm." What firmware did you flash at that point.... was it one of the Verizon stock firmwares? And what build number was it ( 4.1.2 VRAMC3 , 4.3 VRUEMJ9, 4.4.2 VRUFND7)?
I ask this because, if you flashed 4.3 or 4.4.2, then you can no longer restore back to 4.1.2....you would have to restore back to one of those newer versions (and those newer firmwares actually lock the bootloader and install Knox security features... so that's why I was suggesting not to use them--- unless you already did before you had placed your original post for help).
If you can't restore the phone through ODIN using Droidstyle's guide, then you might try the emergency firmware recovery feature that's available through the Samsung Kies program. You can find Kies at this link: http://www.samsung.com/us/kies/
**The KIES instructions say to use Kies version 2.6 for Firmware recovery back to 4.1.2, and use Kies version 3 for Firmware 4.3 and 4.4.2.
Here's a link to Kies 3 FAQ as well: ( http://www.samsung.com/us/support/SupportOwnersFAQPopup.do?faq_id=FAQ00059191&fm_seq=81528 ). Scroll down under Basic Functions and look for the link to "How do I Perform an Emergency Firmware Recovery..." The process should be similar if you plan to use KIES 2.6 instead - (that's only if you're able to restore back to 4.1.2 and you never Odin flashed one of the newer 4.3+ firmwares) .
I hope you can get it fixed. If you're not sure of things, I would suggest researching more and asking more questions before going forward. There is risk that we all take whenever we start modifying our phones, and the more knowledge we can get, the better chances of recovering from errors when we mess something up. (I know I've made plenty of errors as I've tried to learn... I even bricked my Tranformer Prime tablet shortly after receiving it from EBay :banghead: ). If worst comes to worst, you might end up having to pay someone to do a Jtag repair to unbrick it.... but let's hope it doesn't come to that.
Also-- you could try Verizon's Software Upgrade/Repair Assistant found here: ( http://www.verizonwireless.com/support/devices/knowledge_base.html/80201/ ). I have no idea what the differences are between Verizon's software repair assistant and Kies.... **
So i have a stock sprint note 3 that had 4.4.4 on it.
I attempted to install twrp/cwm through odin, but it failed and now i'm stuck in the failed firmware update loop.
I have tried installing older versions of the stock firmware, seems like i'm stuck looking for a 4.4.4 which seems kinda hard to find right now.
What are my other options, my friend is looking for the serial numbers to see if i can just use keis to recover.
k0ncept said:
So i have a stock sprint note 3 that had 4.4.4 on it.
I attempted to install twrp/cwm through odin, but it failed and now i'm stuck in the failed firmware update loop.
I have tried installing older versions of the stock firmware, seems like i'm stuck looking for a 4.4.4 which seems kinda hard to find right now.
What are my other options, my friend is looking for the serial numbers to see if i can just use keis to recover.
Click to expand...
Click to collapse
Although your thread will probably be moved to the Q&A section, you stated you are able to install older versions...... take it back into DL mode and Odin 4.4.4. There are several threads you can download the NK4 Firmware from including the Sammobile site.
SM-N900P Spint (cdma) 2014 December 4.4.4 N900PVPUDNK4 N900PSPTDNK4
shadowcliffs Thread in the General Section
.
k0ncept said:
So i have a stock sprint note 3 that had 4.4.4 on it.
I attempted to install twrp/cwm through odin, but it failed and now i'm stuck in the failed firmware update loop.
I have tried installing older versions of the stock firmware, seems like i'm stuck looking for a 4.4.4 which seems kinda hard to find right now.
What are my other options, my friend is looking for the serial numbers to see if i can just use keis to recover.
Click to expand...
Click to collapse
Honestly it sounds like you're making this more difficult than it really is.
All you need is;
NK4 .tar
SU
&
TWRP
So i'm fairly new to this the last phone i did was my vz s4 (and it went off with less bumps).
I'm stuck in the boot load loop. I can't flash any ROM on it right now, i think i'm trying to find the right 4.4.4 rom. Any place with good rom support would help. sammobile is far too slow on downloads...also there are a few 4.4.4 roms by now.
So the phone was purchased in early Nov 2014, already on a 4.4.4.
I dl'd odin and a TWRP, foolishly didn't make sure 4.4.4 could be flashed in the same way. Odin marked it as failed and when i re-start the phone it runs into the "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
The phone can get into download mode just fine (cannot boot)...tho i have no idea what to flash onto it now.
k0ncept said:
So the phone was purchased in early Nov 2014, already on a 4.4.4.
I dl'd odin and a TWRP, foolishly didn't make sure 4.4.4 could be flashed in the same way. Odin marked it as failed and when i re-start the phone it runs into the "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
The phone can get into download mode just fine (cannot boot)...tho i have no idea what to flash onto it now.
Click to expand...
Click to collapse
As Nickitt stated, don't make it more than it is. If you can get into DL mode then you are not fully bricked which is good. You need to flash an " Official 4.4.4 Firmware " to get you out of this situation, whether it be a slow download or not. I provided a link in my original first response of several uploads of 4.4.4 that you could possibly use that were uploaded by member shadowcliffs in his same thread/post. After you have flashed the official firmware and gone through the initial setup once again with the stock firmware, get the phone back into DL Mode and flash TWRP or Philz CWM recovery via ODIN. Once you have your custom recovery loaded, flash the Custom Rom of your choice.
Hey dark,
thanks for the quick and very very useful response. i wish i hit this up way sooner i did find those links after hours of searching through garbage. i've been downloading a few 4.4.4 images for the last 2hours. Hopefully this will help me! sadly those are the same slow connections i've scene. damn 50kb/sec so sad haha
I'll keep the board posted. but mostly bump that og thread
Damn, fails on the nk4 image and the nh7.
fails on the same spot system.img.ext4
any other suggestions board? please?
make sure your using the hltespr version of either TWRP or philz recovery, if its not working on TWRP switch to philiz. Could also be a bad download - re-download and flash again
Why don't you just use TWRP Manager to install TWRP after you root?
Sent from my GALAXY Note 3 via Tapatalk
not being able to root was the problem
FIXED my issues!!
Never use vmware and Mac to run heimdall or Odin... They should more prominently tell you that.
Thank you board for the concern
problem solved
Thanks for updating that you fixed the problem and what it was. It sounded like you were doing everything correctly. i was getting concerned that it wasn't working. I don't use mac, but if i did i would have been very grateful for that knowledge. thanks for the update. too often someone fixes the problem and just quits posting on the thread.:good:
k0ncept said:
FIXED my issues!!
Never use vmware and Mac to run heimdall or Odin... They should more prominently tell you that.
Thank you board for the concern
Click to expand...
Click to collapse
Parallels is a better option imo as far as v-machines are concerned but anything after Mountain lion doesn't work well. The newest mac osx doesn't work at all with Heimdall. It won't download the pit file. If your running mavricks you can try using a program called winebottle
How to Run Odin On Mac: http://youtu.be/j7fpouzMSsk also jOdin is another desktop tool to use. jOdin is a early stage online flashing tool with limited capabilities at this time.Beings its a online flashing tool. I would make sure to have a good internet connection or you could run into trouble im guessing. All in all I think its a good idea I just hope this project keeps going.
JOdin - Using Odin on a Mac: http://youtu.be/MiPRXq207Ug
It's only right jag.
Goat, thanks for the additional information. I hope there are improved options for the mac and Linux one day
k0ncept said:
It's only right jag.
Goat, thanks for the additional information. I hope there are improved options for the mac and Linux one day
Click to expand...
Click to collapse
Me too bro, me too!
Hey all. I had Hypderdrive installed. I updated it to 21 but had a force close issue. I wiped to reinstall in safestrap and realized that I didn't have the ROM on the device anymore. Whoops. All of a sudden I had no OS and couldn't connect to the phone via USB to put the ROM onto it.
After trying some stuff I got a bit more stuck. I can only reboot into 3 places: 1) Download mode (with volume down) 2) stuck at samsung unlocked icon (no buttons pressed) and 3) default recovery mode (with volume up). I tried with Kies to just install the latest firmware, figuring I'd be happy with lollipop and just go ahead and get a new phone in the near future. That firmware upgrade process fails right when the status bar shows up on the screen. Now rebooting the phone says Software Update Failed.
What are my options via Kies, Odin, or something else to either get back to rooted Hyperdrive or just get the latest firmware up and running? Thanks!
ODIN v3.10
https://docs.google.com/file/d/0B4RU_ZH5QUASNmxLX3JpejBXREE/edit?usp=docslist_api
This is the SCH-I545 lollipop image:
https://docs.google.com/file/d/0B4RU_ZH5QUASaU9LcDJ3WWZfdXM/edit?usp=docslist_api
And once you go forward..There is NO ROOT or ROMMING!!!
If you want to stay NK1 and ROOT:
https://docs.google.com/file/d/0B4RU_ZH5QUASdHE1b2Q2NXpVX0U/edit?usp=docslist_api
In ODIN, WITH EITHER file select these checkboxes:
Auto-Reboot
Re-Partition
F. Reset Time
NAND Erase All
Phone Bootloader Update
Phone EFS CLEAR
Thanks a ton. Haven't gotten it to work yet. I followed your directions and Odin fails with "SW REV. CHECK FAIL : fused : 7, Binary : 6". My guess is that is a mismatch of the bootloader versions? I believe I was on NC5 before, so I tried flashing the No Wipe file from here: http://forum.xda-developers.com/showthread.php?t=2735172 and had no luck.
Any idea what version I should be trying to get it to work? Thanks for the help so far!
No. That means you are on lollipop Bootloader already! You have to flash lollipop
KaosMaster said:
No. That means you are on lollipop Bootloader already! You have to flash lollipop
Click to expand...
Click to collapse
Yup. Learned that while I was thinking about it. Such is life, right? Currently trying to just get OC1 installed via Odin but it keeps failing late in the process with XmitData_Write. If anyone has an idea beyond changing cables and ports (which I'm doing now) then I'm all ears.
Quick update. I've been following the instructions and advice from this thread: http://forum.xda-developers.com/galaxy-s4-verizon/help/unbrick-taking-oc1-t3122230
I have not yet gotten my phone working, but have made slight progress. I'm currently flashing from the Software Update Failed screen and not the Odin Download Mode screen. I've been checking all the listed boxes. I've tried flashing as CSC and as AP and it is now failing on the NON-HLOS.bin file. It's failed there 4 or 5 times now.
Any advice on what changes to try next?
volantis said:
Quick update. I've been following the instructions and advice from this thread: http://forum.xda-developers.com/galaxy-s4-verizon/help/unbrick-taking-oc1-t3122230
I have not yet gotten my phone working, but have made slight progress. I'm currently flashing from the Software Update Failed screen and not the Odin Download Mode screen. I've been checking all the listed boxes. I've tried flashing as CSC and as AP and it is now failing on the NON-HLOS.bin file. It's failed there 4 or 5 times now.
Any advice on what changes to try next?
Click to expand...
Click to collapse
the Single Service File goes in the CSC box. Not sure why it keeps failing, but my OPinion is that you should Try to Load into Recovery, Perform A Factory Data Reset then Try again!
Flash with the Check-Boxes befoire without the "Phone EFS Clear" option...When THe phone turns on....if it is The firmware Recovery screen...Flash there, if it is the Samsung LOGO, Pull the Battery, and LOAD into "Odin Mode" and Flash AGAIN There!
KaosMaster said:
the Single Service File goes in the CSC box. Not sure why it keeps failing, but my OPinion is that you should Try to Load into Recovery, Perform A Factory Data Reset then Try again!
Flash with the Check-Boxes befoire without the "Phone EFS Clear" option...When THe phone turns on....if it is The firmware Recovery screen...Flash there, if it is the Samsung LOGO, Pull the Battery, and LOAD into "Odin Mode" and Flash AGAIN There!
Click to expand...
Click to collapse
Thanks. I finally got it working. I'm not sure exactly what did it. I kept trying various combinations of flashing at CSC or AP and in Download mode and Software Upgrade Failed. I believe the one that actually took was the Sammobile stock OC1 file flashed as AP, but I'm not 100% and not sure that really is what made the difference. I did have all the options checked when it finally took.
After the Odin flash passed it did just boot to a black screen with the LED on solid blue. I went to recovery and did a factory reset and the phone booted up. Maybe that'll help someone else.
Don't have root anymore, but Lollipop seems like a very nice update coming from KK.
Thanks! - but still in trouble.
Spoke too soon!! Yours was the only one that actually loaded with Odin. After that phone will not reboot, just comes on for 2 seconds and then turns off. Any ideas would be greatly appreciated.
I have tried the following firmware versions, except for yours, they all get fused: 7 , binary : 6:
I545_VZW_I545VRUDMI1_I545VZWDMI1_Original
I545_VZW_I545VRUEMJ7_I545VZWEMJ7_Original
VZW-I545VRUFNC5-20140429111807
VZW-I545VRUFNG6-20141021092718
plus several others
--------------
Thanks, bricked my Verizon S4 and tried 5 different firmware files, including the ones from the Samsung site. Yours is the only one that worked.
Looks like you need to flash a more recent file. You'll probably have to go with the latest stock version without root.
volantis said:
Looks like you need to flash a more recent file. You'll probably have to go with the latest stock version without root.
Click to expand...
Click to collapse
Sorry, thought I updated the post. I tried again and the second time around it worked all the way through with the file on this thread.
I was simply messing around with my old Verizon GN2, because I need a phone to use in the absence of my htc one M9. I went to flash the "stock" version of the bootloader (the bootloaderbaseline2.tar) before I went in to do any real damage and the phone rejected it. The phone screen read the error message "wrong magic string" and the odin display reported that it dropped out after sboot.bin. Just curious whether you guys and your wisdom would have any insight in the matter? I would really prefer not to have to go out and buy another phone.
Also, woohoo for a first post on the forums.
Cordially,
Nixon
logannixon.la said:
I was simply messing around with my old Verizon GN2, because I need a phone to use in the absence of my htc one M9. I went to flash the "stock" version of the bootloader (the bootloaderbaseline2.tar) before I went in to do any real damage and the phone rejected it. The phone screen read the error message "wrong magic string" and the odin display reported that it dropped out after sboot.bin. Just curious whether you guys and your wisdom would have any insight in the matter? I would really prefer not to have to go out and buy another phone.
Also, woohoo for a first post on the forums.
Cordially,
Nixon
Click to expand...
Click to collapse
Are you flashing the full firmware or just bootloader? What options did you have checked and where (in what slot, PDA?) did you put the file to run it? What version are you on, 4.4.2; 4.3? Have you unlocked it before?
bigmike35 said:
Are you flashing the full firmware or just bootloader? What options did you have checked and where (in what slot, PDA?) did you put the file to run it? What version are you on, 4.4.2; 4.3? Have you unlocked it before?
Click to expand...
Click to collapse
I had this phone rooted before, but it wasn't playing well with what my sister wanted it for. So, I flashed a stock image and it rebooted into its stock form. That was two ish years ago. The bootloader was never unlocked. When I brought it back out to begin tinkering, a lot of guides said to flash the stock bootloader (the bootloaderbaseline2 file) and to repartition it before going ahead with something like CASUAL. Considering my sister used it as a daily driver for quite a while, it was probably on 4.3 or whatever the last update Verizon handed out was. I do remember checking to see whether or not it had any available updates and it said it was completely up to date. When I set it up to repartition and flash the BB2 file, it was in the bootloader slot. The Odin flash then failed at the sboot.bin output and the phone proceeded to slide into the good old "connect to Kies" screen. I tried several attempts to get the BB2 file to stick (putting it in all the slots and trying it without partition and auto reboot), but all were to no avail. I have since flashed multiple firmwares in the PDA slot with only the root66_vzw_stock_system.tar.md5 version completing. However, it now displays the "Device firmware is not from verizon. Please bring it into a Verizon store for help." I know the verizon reps will be useless, so I asked you beautiful people.
The only odin boxes that I played with were the top three.
Also, thanks for responding. I appreciate it.
Nixon
logannixon.la said:
I had this phone rooted before, but it wasn't playing well with what my sister wanted it for. So, I flashed a stock image and it rebooted into its stock form. That was two ish years ago. The bootloader was never unlocked. When I brought it back out to begin tinkering, a lot of guides said to flash the stock bootloader (the bootloaderbaseline2 file) and to repartition it before going ahead with something like CASUAL. Considering my sister used it as a daily driver for quite a while, it was probably on 4.3 or whatever the last update Verizon handed out was. I do remember checking to see whether or not it had any available updates and it said it was completely up to date. When I set it up to repartition and flash the BB2 file, it was in the bootloader slot. The Odin flash then failed at the sboot.bin output and the phone proceeded to slide into the good old "connect to Kies" screen. I tried several attempts to get the BB2 file to stick (putting it in all the slots and trying it without partition and auto reboot), but all were to no avail. I have since flashed multiple firmwares in the PDA slot with only the root66_vzw_stock_system.tar.md5 version completing. However, it now displays the "Device firmware is not from verizon. Please bring it into a Verizon store for help." I know the verizon reps will be useless, so I asked you beautiful people.
The only odin boxes that I played with were the top three.
Also, thanks for responding. I appreciate it.
Nixon
Click to expand...
Click to collapse
So it it on 4.4.2 then since all updates are up to date? If that is the case, you can only root using towel root. You can downgrade to 4.3 or 4.2.1 but you would need to send it in ($75) i believe or try the method here that is posted. If it is still on 4.3 i believe you can flash the 4.2.1 firmware and then run root running casual (disable firewall and antim virus else wont complete). Then find Beanstown thread and download the zip for the updated wifi/bootloader for 4.3 with ND7 radio (zip somewhere as well) to upgrade completely to newest radio/images (so it would be a 4.2.1 or 4.3 stock with complete root and unlocked). Then install TWRP and roms
bigmike35 said:
So it it on 4.4.2 then since all updates are up to date? If that is the case, you can only root using towel root. You can downgrade to 4.3 or 4.2.1 but you would need to send it in ($75) i believe or try the method here that is posted. If it is still on 4.3 i believe you can flash the 4.2.1 firmware and then run root running casual (disable firewall and antim virus else wont complete). Then find Beanstown thread and download the zip for the updated wifi/bootloader for 4.3 with ND7 radio (zip somewhere as well) to upgrade completely to newest radio/images (so it would be a 4.2.1 or 4.3 stock with complete root and unlocked). Then install TWRP and roms
Click to expand...
Click to collapse
So, for the moment, is there any way to get it back to stock? I was trying to go the custom recovery route in the beginning, but I now just need a phone that works. I'm pretty sure it's the bootloader firmware that is preventing the device from booting completely. Thanks for all your help.
Nixon
logannixon.la said:
So, for the moment, is there any way to get it back to stock? I was trying to go the custom recovery route in the beginning, but I now just need a phone that works. I'm pretty sure it's the bootloader firmware that is preventing the device from booting completely. Thanks for all your help.
Nixon
Click to expand...
Click to collapse
You can see if you can flash the full Verizon firmware. Should be able to find it here or on Samsungs website.
bigmike35 said:
You can see if you can flash the full Verizon firmware. Should be able to find it here or on Samsungs website.
Click to expand...
Click to collapse
So the stock Verizon firmware will repair the broken bootloader? I'll give it a go. Thanks for the info.
Just a quick update. I flashed the stock firmware for 4.4.2 and everything went over swimmingly. The phone now boots all the way into the Verizon boot splash screen. It then sits there and will not progress. I've tried wiping cache and factory resetting, but it still hangs on the Verizon splash screen. Any pointers?
Thanks again,
Nixon
Another side update. It's still held up on the Verizon boot splash screen, but the led is now pulsing. *Shrugs in confusion
Nixon
logannixon.la said:
Another side update. It's still held up on the Verizon boot splash screen, but the led is now pulsing. *Shrugs in confusion
Nixon
Click to expand...
Click to collapse
Ya i have had that issue before, but I did what you did is to wipe cache, data, factory and that normal let me get a full boot in.
bigmike35 said:
Ya i have had that issue before, but I did what you did is to wipe cache, data, factory and that normal let me get a full boot in.
Click to expand...
Click to collapse
Yeah, I've tried the factory reset and wipe cache, it still gets caught in the Verizon boot loop. I'm not particularly sure what that else to do. The 4.4.2 stock md5 is the only one that will stick in Odin.
logannixon.la said:
Yeah, I've tried the factory reset and wipe cache, it still gets caught in the Verizon boot loop. I'm not particularly sure what that else to do. The 4.4.2 stock md5 is the only one that will stick in Odin.
Click to expand...
Click to collapse
are you flashing it with the PIT file as well?
bigmike35 said:
are you flashing it with the PIT file as well?
Click to expand...
Click to collapse
I think I tried with and without, but I'll give it a shot.
logannixon.la said:
I think I tried with and without, but I'll give it a shot.
Click to expand...
Click to collapse
Ya put that in the PIT tab and firmware in PDA. When it finished, does it say complete or done (box turns green, near top left?)
Also, maybe try another firmware/version?
bigmike35 said:
Ya put that in the PIT tab and firmware in PDA. When it finished, does it say complete or done (box turns green, near top left?)
Also, maybe try another firmware/version?
Click to expand...
Click to collapse
I tried the pit to no avail. Currently wiping again just for fun. Not sure if it helps, but the system recovery screen reads this