I'm trying to get my hands on NK1 and NG6 Debrick .img (s) I messed up another phone flashing something and not paying attention to the zip package... trying to port something from AT&T 4.4.4 TW anyway if someone could upload me an .img for nk1 ASAP I'd be greatful. I'll turn this OP into a guide for recovering from QHSUSB Hardbrick for our phones once I gather the .imgs need an nc5 one as well. Already have mdk, mk2 and mj7 but cant find any of the 4.4.2 imgs online except these SDC files which apparently require an ATF JTAG Box which is what im trying to avoid having to do!
Thanks in advance!
-gogolie
PS This file should be run from safestrap or your recovery: https://www.androidfilehost.com/?fid=23329332407577222 its a debrick img creator hosted by Surge (thanks) hopefully this one will work I havent tested it and I lost my own 512 creator and have no phone or whatever to test with... thanks whoever helps me out... I'll be able to continue development of my ROMs then
what bootloader is that?
I cannot get that debrick to work. Appreciate the effort... When u had used it just popping it in and then battery worked for you? I tried a variety of ways including using the sdcard and a jig at the sametime with no luck.
Anyone able to do me a favor and either upload an nk1 debrick.IMG so I can try again. Or upload proper QPST style .mbn and .hex backups from a working nk1 phone. From what I've read I should able to flash them via USB to the emmc while in this mode to kick me out of this dam qhusb download mode.
If anyone can help get this phone up and going I'll donate to them just for saving me hassle of sending it in.
Thanks
Gogolie
gigilie said:
I cannot get that debrick to work. Appreciate the effort... When u had used it just popping it in and then battery worked for you? I tried a variety of ways including using the sdcard and a jig at the sametime with no luck.
Anyone able to do me a favor and either upload an nk1 debrick.IMG so I can try again. Or upload proper QPST style .mbn and .hex backups from a working nk1 phone. From what I've read I should able to flash them via USB to the emmc while in this mode to kick me out of this dam qhusb download mode.
If anyone can help get this phone up and going I'll donate to them just for saving me hassle of sending it in.
Thanks
Gogolie
Click to expand...
Click to collapse
Although I am unable to do so today, if you PM tomorrow, I'll be near my S4, and will happily shoot over what you need.
(The Pm is just so that I remember to do it )
debrick
yeah that would be cool if we could have all the dbrick images in one thread I know a lot of people have them but I'll hold it back
ng6
anyone have a mirror for that thanks.
Please PM the debrick img 4.4.2 NK1 to unbrick my phone, thanks very much.
tomy1986.nt said:
Please PM the debrick img 4.4.2 NK1 to unbrick my phone, thanks very much.
Click to expand...
Click to collapse
I tried 2 bricked phones both last on NK firmware and no matter what debrick I tried I had no response from the S4. I also tried in combo with a jig that I tested on my gf's S3 and it'd boot directly to dl mode but with the S4 nothing. Maybe it was my type of brick but its showing up as a qc modem or qc usb mode on a pc which matches the same hard brick I've read about these but I'm guessing that this type of brick recovery isnt possible anymore maybe due to knox 2.0 or changes Samsung made in the firmware/bl or its just my phones and luck. my only thoughts are that maybe using some combo of QPST or similar to make an NV backup or whole phone backup and restoring the bl / phone using a full .bin backup might work. obviously we'd have to be aware that this would include the original phone's IMEI info and similar so we'd have to modify this before trying it so if anyone has any info or abilities using QPST and can hook it up with a viable escape from this qshusb mode hell that'd be awesome! Or if someone wants to fix one of my phones via JTAG i'd pay with my other bricked s4. I know the VZW S4 Scene's all but dead so I'm losing hope. I think its time to start looking for a Note4 Dev edition or something :<(
Related
Ok so if you don't know now, now you know!!!! There's evidence of people fixing bricked Note 3's by using a unbrick sdcard method or a jig. Now im not saying i've done it myself but i want to try. I know one method to bricking your Note 3 is flashing an older bootloader. From my experience odin won't flash one but recoveries have no limitations in what it flashes. Im' going to order a jig and get a 32gb sdcard and try both of these.
The only reason being is because im on NC4 the no going back bootloader. But i also know that a dump of the download mode thats on NC2 or older can be used for the download mode sdcard. We don't have a dump but stated in this thread http://forum.xda-developers.com/showthread.php?t=2531224 a lot of note 3's already do have one.
I would need someone with a VZW note 3 NC4 or lower to make a dump using this post http://forum.xda-developers.com/showpost.php?p=48463979&postcount=33. That would be used to make the img file need to make the sdcard.
From what i understand id be able to flash a rom thru odin which is when the downgrade would come into play. Ill be trying roms NC2 and lower to see if it works. If it works out then we will have a downgrade method thru bricking first. I already made a bricking zip and it works. My note 3 is bricked and still responds when plugged into the pc as "qualcomm hs-usb qdloader 9008" so im sure i can unbrick it easily. The only thing im trying to determine is will it let me flash an older rom which was possible for other phones.
I also found a downgrade method that i did on the Note 2 when Knox was released so if you know me you know i go hard or go home and don't mind bricking lol!!!!! http://forum.xda-developers.com/showthread.php?t=2541395 so ill try my best to get us off this locked terror!!!!
lorjay589 said:
Ok so if you don't know now, now you know!!!! There's evidence of people fixing bricked Note 3's by using a unbrick sdcard method or a jig. Now im not saying i've done it myself but i want to try. I know one method to bricking your Note 3 is flashing an older bootloader. From my experience odin won't flash one but recoveries have no limitations in what it flashes. Im' going to order a jig and get a 32gb sdcard and try both of these.
The only reason being is because im on NC4 the no going back bootloader. But i also know that a dump of the download mode thats on NC2 or older can be used for the download mode sdcard. We don't have a dump but stated in this thread http://forum.xda-developers.com/showthread.php?t=2531224 a lot of note 3's already do have one.
I would need someone with a VZW note 3 NC4 or lower to make a dump using this post http://forum.xda-developers.com/showpost.php?p=48463979&postcount=33. That would be used to make the img file need to make the sdcard.
From what i understand id be able to flash a rom thru odin which is when the downgrade would come into play. Ill be trying roms NC2 and lower to see if it works. If it works out then we will have a downgrade method thru bricking first. I already made a bricking zip and it works. My note 3 is bricked and still responds when plugged into the pc as "qualcomm hs-usb qdloader 9008" so im sure i can unbrick it easily. The only thing im trying to determine is will it let me flash an older rom which was possible for other phones.
I also found a downgrade method that i did on the Note 2 when Knox was released so if you know me you know i go hard or go home and don't mind bricking lol!!!!! http://forum.xda-developers.com/showthread.php?t=2541395 so ill try my best to get us off this locked terror!!!!
Click to expand...
Click to collapse
I have looked at this method previously and have used the sprint downgrade before. Has there been any progress and if so are there any results.
Will not work. QFPROM is blown to boot from SDC3 and verify the images just as it does on the eMMC. Because the rollback bit for NC4 aboot has been blown, a downgrade is not possible. However, this only applies to aboot at the moment.
I TAKE NO CREDIT FOR CORE METHOD. I APPLIED IT FOR OUR DEVICE !
To make long story short, I've hard bricked my device while trying to patch/unlock the bootloader after successfully flashing a custom kernel (this tripped knox counter). After reading all guides that addresses the problem for other devices, I'm posting a 100% working solution for the most hated disaster in the Android rooting/flashing world. Moreover, this is very promising info for testing bootloader exploits.
What is Hard Brick?
Hard brick is the state of android device that occurs when your device won’t boot/respond/charge at all. This is mainly caused by flashing corrupted firmware, damaged bootloader, incomplete flashing in Odin/Download mode, or interrupted OTA upgrade. You can't recover from hard brick by traditional methods since your phone is ~dead & you can't enter any Recovery or Download Modes; You'll need to use JTAG (expensive service), USB JIG (cheap, but no gurantee), or this free guide/files to get it repaired.
What do you need?
- Hard Bricked Device: Samsung Galaxy Note 3 (N900V)
- Micro SD Card: 4/8/16/32 GB micro SD card
- Unbrick Image: working dump with the same bootloader/version
- Image Writer: native commands on Linux/MacOSx or Win32 Disk Imager on Windows
How to recover?
1- Download Unbrick Image for your bootloader (MJE, NC2 or NC4) from here
2- If you're using Windows, download Win32 Disk Imager
3- Backup all files in the micro SD card you 'll use
4- Write the Unbrick Image to your micro SD card using Win32 Disk Imager or Linux/MacOSX commands
5- Remove battery, Insert micro SD card & then the battery
6- Hold Power + Home + Volume Down to enter Download Mode by bootloader on SD card
7- Flash Stock firmware via Odin & Enjoy
YOU MAY NEED TO TEST MICRO SD CARDS WITH DIFFERENT TYPES/SIZES & FORMAT AS EXFAT BEFORE WRITING AN UNBRICK IMAGE ACCORDING TO YOUR BOOTLOADER!
This method should work for most Hard Brick cases, especially those with flashing failures. However, some cases might need a repair service or a hardware treatment to recover. One thing you may try if you can't get a replacement (warranty claim) is from Samsung guide for N900 device that includes disassembly & making short of R4075 resistance (which isn't tested & for another device + I don't recommend it) as described here.
Click to expand...
Click to collapse
For Developer Edition, you need to create your own Unbrick Image since I can't share it for the device-specific bootloader. Just run this Unbrick Image Creator in recovery & it'll create "/sdcard/Unbrick_Files" in your internal SD card.
For more details, read the guides provided bellow in the credits section.
Downloads:
All files you may need are available in this folder.
Credits:
- designgears - for this guide
- Shabbypenguin - for this guide
- theramsey3 - for this guide
- dstruct2k - for this guide
- -Mr. X- - for this guide
Thanks to:
- @soundrizm - for creating the MJE image from his device
- @jrbxx7 - for creating the NC2 image from his device
- @K03WL3R - for creating the NC4 image from his device
XDA:DevDB Information
How to recover from a HARD BRICK, Tool/Utility for the Verizon Samsung Galaxy Note 3
Contributors
hsbadr
Version Information
Status: Stable
Created 2014-08-01
Last Updated 2015-02-15
Nice work! Thanks
Tapped from an annihilated N10.1
This is amazing progress for our devices @hsbadr. I, for one, can't thank you enough for all you're doing to keep our beautiful albeit locked down Note 3's on the forefront! Donation coming asap!
Sent from my SM-G900V using Tapatalk
Wait, how can this help with unlocking bootloader? I have no developing background so this would be nice to know
This won't reset knox to 0 though, correct? So there's no way to reset to 0 yet?
I see there is a nc2 and nc4 unbrick image... If i am on the unified kk Jasmine rom firmware which image do i use... I thought i read on the Jasmine thread that it contained components of both...
Samsung Note 3 - VZW
Jasmine 2.0 v4
XDA Pro
ihavenewnike said:
Wait, how can this help with unlocking bootloader? I have no developing background so this would be nice to know
Click to expand...
Click to collapse
Testing bootloader exploits could easily HARD BRICK the device; now, we've a tested fully working fix for this disaster. So, devs can feel better with their tests.
kvnhmmd said:
This won't reset knox to 0 though, correct? So there's no way to reset to 0 yet?
Click to expand...
Click to collapse
This just enables booting the device from SD card so that you can enter Download Mode & revive it from HARD BRICK state. The knox counter won't change unless you've already tripped it while messing with your device at/before HARD BRICK.
Night_Watcher said:
I see there is a nc2 and nc4 unbrick image... If i am on the unified kk Jasmine rom firmware which image do i use... I thought i read on the Jasmine thread that it contained components of both...
Click to expand...
Click to collapse
It only depends on the bootloader version. The unified KK firmware doesn't include any bootloader; so, you'll need to use the Unbrick Image based on your bootloader (NC4 for OTA update or full NC4 tar via Odin & NC2 otherwise). You may try the NC2 image 1st which won't boot if you're on a newer NC4 bootlooder; if so, use the NC4 image.
hsbadr said:
Testing bootloader exploits could easily HARD BRICK the device; now, we've a tested fully working fix for this disaster. So, devs can feel better with their tests.
This just enables booting the device from SD card so that you can enter Download Mode & revive it from HARD BRICK state. The knox counter won't change unless you've already tripped it while messing with your device at/before HARD BRICK.
It only depends on the bootloader version. The unified KK firmware doesn't include any bootloader; so, you'll need to use the Unbrick Image based on your bootloader (NC4 for OTA update or full NC4 tar via Odin & NC2 otherwise). You may try the NC2 image 1st which won't boot if you're on a newer NC4 bootlooder; if so, use the NC4 image.
Click to expand...
Click to collapse
So now we can just randomly try bootloaders, like maybe the DE bootloader modified for a device?
ihavenewnike said:
So now we can just randomly try bootloaders, like maybe the DE bootloader modified for a device?
Click to expand...
Click to collapse
NO, don't! This is only for devs or users who know exactly what they're doing. If you flashed another device's bootloader, you may kill your device forever. However, you can use it to recover when you ACCIDENTALLY made your device hard bricked.
Ok. Thanks. Curious, how do you learn about these things. I would love to try some stuff. Hey I got the device for 50 off contract.
Thank you, Thank you, Thank you! Makes me feel better about trying different roms &mods.
had a Droid HD unlocked bootloader, bricked it many times.
Could the unbrick files be made flashable. The DE 4.4 bootloader is now on new devices and many DE guys (me too) are interested in upgrading from 4.3? I bow low to @hsbadr really great work!
ol`DXer said:
Thank you, Thank you, Thank you! Makes me feel better about trying different roms &mods.
had a Droid HD unlocked bootloader, bricked it many times.
Click to expand...
Click to collapse
You're welcome! Glad I could help.
LillieBennett said:
Could the unbrick files be made flashable. The DE 4.4 bootloader is now on new devices and many DE guys (me too) are interested in upgrading from 4.3? I bow low to @hsbadr really great work!
Click to expand...
Click to collapse
The purpose of Unbrick Image(s) is to revive a ~dead (hard bricked) device by booting from external SD card to enter Dwonload Mode & flash firmware to recover. You can pull all images from your device & on DevED, all of them can be flashable.
Is the process similiar for a phone that was on MJE?
Scenario:
Phone was stock MJE.
Rooted w/ TowelRoot, installed SS 3.7.1
Rebooted to DL mode, Odin'd "unified firmware" from Jasmine thread (*I think this is where things went sideways b/c no NC2/4 rom was installed to stock slot, just the leftover MJE+TR+SS install).
Phone shutdown at the end of that Odin, and now will not power up / vibrate / enter DL mode / nothing ...
I put the NC2 debrick image on a 32GB Class4 MicroSD - no joy.
I was wondering if it's because the MJE bootloader is still there? Wouldn't I then need an MJE unbrick microSD img?
I figured as much so I made one by Odin'ing another phone back to Stock MJE, and doing a "dd if=/dev/block/mmcblk0 of=/sdcard/unbrickMJE.img count=524288" and used that .img to make the MicroSD card (with Win32DiskImager)...
Still no joy... No power-up/buzz/dl-mode off of power button OR voldn+home+pwr, with and w/out USB cable...
(Yes, the card is fine, the battery is at 100%...)
I'm wondering if I made the .img incorrectly? OR, is this phone just completely eff-screwed now?? :crying:
Thoughts?
NetworkPIMP said:
Still no joy... No power-up/buzz/dl-mode off of power button OR voldn+home+pwr, with and w/out USB cable...
(Yes, the card is fine, the battery is at 100%...)
I'm wondering if I made the .img incorrectly? OR, is this phone just completely eff-screwed now?? :crying:
Thoughts?
Click to expand...
Click to collapse
Does your phone vibrate when you attempt to turn it on? With the battery or without the battery but plugged into the charger? In my experience with hard bricks, the phone should at least vibe when you go to power it up. Also, not sure if it will make a difference but, try a class 10 card with the same amount of memory as the phone.
Other than that everything you did sounds correct.
Sent from my SM-G900V using XDA Premium HD app
NetworkPIMP said:
Is the process similiar for a phone that was on MJE?
Scenario:
Phone was stock MJE.
Rooted w/ TowelRoot, installed SS 3.7.1
Rebooted to DL mode, Odin'd "unified firmware" from Jasmine thread (*I think this is where things went sideways b/c no NC2/4 rom was installed to stock slot, just the leftover MJE+TR+SS install).
Phone shutdown at the end of that Odin, and now will not power up / vibrate / enter DL mode / nothing ...
I put the NC2 debrick image on a 32GB Class4 MicroSD - no joy.
I was wondering if it's because the MJE bootloader is still there? Wouldn't I then need an MJE unbrick microSD img?
I figured as much so I made one by Odin'ing another phone back to Stock MJE, and doing a "dd if=/dev/block/mmcblk0 of=/sdcard/unbrickMJE.img count=524288" and used that .img to make the MicroSD card (with Win32DiskImager)...
Still no joy... No power-up/buzz/dl-mode off of power button OR voldn+home+pwr, with and w/out USB cable...
(Yes, the card is fine, the battery is at 100%...)
I'm wondering if I made the .img incorrectly? OR, is this phone just completely eff-screwed now?? :crying:
Thoughts?
Click to expand...
Click to collapse
1st: you should have flashed full firmware to upgrade from JB; the unified firmware is for KK only !!!
2nd: If you can enter Download Mode, flash the firmware linked above to recover.
3rd: You should use Unbrick Image for the same bootloader & device (N900V MJE in your case)
Update: you may also try a USB JIG to enter Download Mode & flash the required firmware; you can create one or order it from Amazon.com (it's very cheap).
Can someone do a video tutorial on this.
An unbrick image may only be viable on a 32GB+ MicroSD. It must be at least the size of the eMMC chip on-board.
Kudos to all the folks that are involved in this, a life saver for those in need for sure!:good:
Any luck with mj7 debrick.img
Long story short, bootloader is stuck. -- Phone is stuck in a boot-loop of sorts ... it keeps showing the very first screen that shows the Galaxy name and some other info and then flashes that screen over and over again. It is not a boot-loop that loads the OS and keeps loading that continuously. From what I know about phones/programming, which is limited, the bootloader either doesn't exist anymore or the code is not executing properly.
I know there are guides that are similar to my issue, but none of them seem to answer my questions specifically. And when I have attempted some other fixes, nothing happens. I am hoping for a direct answer if anyone has one.
Here's what led to this:
1. I wanted to install the new Android Revolution rom which suggested I have the MJ5 bootloader. I have not attempted to install this rom yet, my issue occurred when I tried to flash the new bootloader.
2. Followed a thread that explained bootloaders and how to install mj5 on note 2 via Odin. --> then got this boot-loop. MD5 and all that jazz was fine. Downloaded from reputable source too.
3. I was/am running a custom rom (JellyBeans build 26 I think) with TWRP recovery. I was previously running CWM recovery, but switched to TWRP because the guide suggested TWRP or Philz recovery for MJ5. Switch between recoveries went just fine. Also, I don't remember what bootloader was installed before I broke it.
I am not a developer (obviously), but I am fairly computer savvy. I can do most things if explained properly. Although I am prone to being an idiot so if someone is feeling a little helpful a step-by-step guide may be best.
I am hoping that someone could (1) provide me with a how-to fix this issue, (2) provide me with a link to the right bootloader that I need to flash in ODIN in order to fix this issue.
PLEASE HELP! I am waiting for some job interview calls this upcoming week and I will be F***ed without my phone. I know it's my fault that the phone is stuck, but I know one of you geniuses here will be able to provide me with some information.
In Summary:
Bootloader is stuck
Phone can get into Download mode, but that's it.
Odin will connect and phone shows up on COM port.
I am an idiot.
I am fine going back to stock recovery/build if necessary to fix this issue.
Thank you all in advance.
P.S. Soul is available upon resolution of the issue; shipping and handling extra ; ) If you don't want my soul I will send you a holiday card with my dogs on it.
You flashed a bootloader for a different phone. Mj5 is for the n7100. The Verizon Note 2 is i605. You have 2 options to get your phone back to 100%. Either use kobols unbrick method found in the general section or send it off to mobiletechvideos and pay them to get it working.
Here is a link to kobol's method: http://forum.xda-developers.com/showthread.php?t=2615587
BluGuy said:
You flashed a bootloader for a different phone. Mj5 is for the n7100. The Verizon Note 2 is i605. You have 2 options to get your phone back to 100%. Either use kobols unbrick method found in the general section or send it off to mobiletechvideos and pay them to get it working.
Here is a link to kobol's method: http://forum.xda-developers.com/showthread.php?t=2615587
Click to expand...
Click to collapse
Thank you for the reply, I will try this now. I saw this thread but was hoping I wouldn't have to do this because of its requirements (screwing with the hardware and such).
Like I said, I'm an idiot.
Thank you for the tip though, it is much appreciated.
axpaxp said:
Thank you for the reply, I will try this now. I saw this thread but was hoping I wouldn't have to do this because of its requirements (screwing with the hardware and such).
Like I said, I'm an idiot.
Thank you for the tip though, it is much appreciated.
Click to expand...
Click to collapse
axpaxp,
You may try the method in this thread: How To: Unbrick A Hard Bricked i605 [n7100 Bootloader Flash] NO Resistor , as an alternative to Kobol's method.
I have been trying to switch from TWRP to CWM but every time it always ended up with "Secure Fail Kernel" message. So, after many hours of frustrations, I have tried EZ-Unlock to unlock my bootloader, which was a very bad idea.
So, phone is dead now. Power button does not do anything... So, my last hope, before paying for JTAG services, is to try to boot from a unbrick file from sdcard. So, if someone would kindly post/upload/PM the S4 unbrick file, I would appreciate it..
16GB Verizon SCH-I545 S4
ME7 with TWRP
ROM - 4.4.4 Dan&Ktoonsez CM (final) 09-18-2014
How to save your bootloader image (unbrick file) so that you could upload:
dd if=/dev/block/mmcblk0 of=/sdcard/backup.bin bs=1024 count=131072
xdatufoz said:
I have been trying to switch from TWRP to CWM but every time it always ended up with "Secure Fail Kernel" message. So, after many hours of frustrations, I have tried EZ-Unlock to unlock my bootloader, which was a very bad idea.
So, phone is dead now. Power button does not do anything... So, my last hope, before paying for JTAG services, is to try to boot from a unbrick file from sdcard. So, if someone would kindly post/upload/PM the S4 unbrick file, I would appreciate it..
16GB Verizon SCH-I545 S4
ME7 with TWRP
ROM - 4.4.4 Dan&Ktoonsez CM (final) 09-18-2014
How to save your bootloader image (unbrick file) so that you could upload:
dd if=/dev/block/mmcblk0 of=/sdcard/backup.bin bs=1024 count=131072
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2560961 be warned if you use the wrong bootloader you may trip the aboot counter and permanently lock it so you can't run custom kernels/recovery EVER AGAIN THERE IS NO GOING BACK IF YOU DO THIS~ tho I fear its to late for that now
trying to go from twrp to cmw is unpossible whatever possessed you to try and use a GS3 utility on a GS4 congrats you get the Darwin award
if you send it out to be jtagged you will lose custom recovery forever unless they flash the exact bootloader which I assume is MDK and you are running ME7 baseband on a loki'd MDK bootloader
I don't know what possessed me to do that. It was middle of the night and I was desperate...
Anyways, trying to move forward... So, I have already tried the debrick file in that URL. It didn't work because I suspect that's for MJ7.
You said "exact bootloader which I assume is MDK and you are running ME7 baseband on a loki'd MDK ". Does that mean I need MDK or ME7 debrick file - I thought I needed ME7.
Can anyone help out and dump their bootloader image please... I am without a phone!... Use the command below to dump bootloader:
dd if=/dev/block/mmcblk0 of=/sdcard/backup.img bs=1024 count=131072
anyone? can someone post their MDK bootloader please...
Dump via the command below:
dd if=/dev/block/mmcblk0 of=/sdcard/backup.img bs=1024 count=131072
xdatufoz said:
anyone? can someone post their MDK bootloader please...
Dump via the command below:
dd if=/dev/block/mmcblk0 of=/sdcard/backup.img bs=1024 count=131072
Click to expand...
Click to collapse
did you try and boot into download mode with the bootloader image in that thread it can take several trys
I don't have a MDK phone available
Using a 32GB microSD card,I wrote the backup.bin to the SD card via Win32 Disk Iimager. Then I tried to power on using different combinations, vol up/down/home/power... Nothing... Unless, I misunderstood the instructions, that image is not working. Another issue might be that I need a 16GB card to match my internal storage.... I did use Partition Wizard to carve out 16384MB FAT32 to mimic a 16GB card but no luck...
Do you think I can extract and use the recovery images from the link below on my SDCard?
http://forum.xda-developers.com/showthread.php?t=2637686
Thanks again,
xdatufoz said:
Using a 32GB microSD card,I wrote the backup.bin to the SD card via Win32 Disk Iimager. Then I tried to power on using different combinations, vol up/down/home/power... Nothing... Unless, I misunderstood the instructions, that image is not working. Another issue might be that I need a 16GB card to match my internal storage.... I did use Partition Wizard to carve out 16384MB FAT32 to mimic a 16GB card but no luck...
Do you think I can extract and use the recovery images from the link below on my SDCard?
http://forum.xda-developers.com/showthread.php?t=2637686
Thanks again,
Click to expand...
Click to collapse
size of the card doesn't matter don't mess with the partitioning that will screw it up reformat the card as fat 32
the combonation is always as follows
insert sd card containing image
power button and volume down
retry until you get into download mode
honestly I don't know what the process is for recovering a loki'd phone via MDK when you have managed to toast the bootloader
I would assume you would flash a ODIN package containing the MDK bootloader with the ME7 baserom..
wait for somebody that knows what they are doing to post don't be tinkering with stuff without knowing what you are doing thats what got you here
if you where running a custom kernel it means you where using loki and your bootloader must have been MDK because there is no other option
and no you can't use developer edition stuff on a VZW phone
pokes @Surge1223
Those big red letters for Developer Edition only is tough to miss.. So, yeah, that's not for my phone..
" Do you think I can extract and use the recovery images from the link below on my SDCard? http://forum.xda-developers.com/show....php?t=2637686 "
I just installed Cygwin so that I could dd the img file to the sdcard instead of using the win32 disk imager. Still, no luck. I feel that the MJ7 image file on that thread is not what I need. I need a MDK bootloader image. Anyone?
I am going nuts. Probably tried to power on above 200 times or more... Yes, I am ok with TWRP or no recovery. If I get any vibration/light out of my phone, I ll take it...
btw, can I use any of these files in this URL to boot from the SD card?
http://forum.xda-developers.com/showthread.php?t=2720163
xdatufoz said:
btw, can I use any of these files in this URL to boot from the SD card?
http://forum.xda-developers.com/showthread.php?t=2720163
Click to expand...
Click to collapse
nope
you need a image of the mdk boot-loader from a Verizon i545
you also might need a different SD card
odds are you are gonna need to have it jtagged I am not even sure the Verizon version has the functionality needed to recover from a sdcard as far as I know only the GT-l9500/95004 have that functionality enabled
make sure you pull the battery between try's if the functionality does exist its only gonna try on a cold boot
IF YOU HAVE IT JTAGGED MAKE SURE YOU SPECIFY YOU WANT VRUAMDK FLASHED AND ONLY THAT ANYTHING ELSE WILL RESULT IN A PERMANENT LOSS OF ABILITY TO RUN CUSTOM NON TW ROMS
At this point, unless someone else that's an expert on this and fix it up, yeah, I would like to have it JTAG to be fixed but unfortunately the only place I know is MobileTechVideos which currently has a backlog of over 4 weeks. That's too long..
So, JTAG service would cost $50 from them but I don't want to wait that long... Anyone that could help me get the bootloader working, I would be ok donating them the money... Anyone?
I hard bricked my first S4 and found several JTAG services on eBay.
I picked the one that had the highest number of positive feedbacks and sent it off.
There was no guarantee that they would be able to restore it to MDM but they guaranteed they could unbrick it or a full refund.
They did unbrick it but unfortunately it was not MDK.
I had the phone back in less than a week.
sent from a Galaxy S4 far far away.
Well, I have sent my S4 to mobiletechvideos and also spoke with Josh about the backlog. It seems like he wants to be on top of his business and really wants to make his customers happy. I ll keep this thread posted.
I have received my S4 today from mobiletechvideos and it is alive now!! I have worked with Josh and he has JTAG my S4 to unbrick, updated my recovery to CWM, put back my baseband to MDK again. After he has fixed my phone in under 2 days, he has sent it back via priority to me. The only reason it took this long is because when I sent him the phone, USPS delayed my package.
So, I must say, I would recommend mobiletechvideos to anyone looking to get specialized work done on their phones.
I am very happy today to have my phone back!!! ok, lets see what are the latest ROMs...
xdatufoz said:
I have received my S4 today from mobiletechvideos and it is alive now!! I have worked with Josh and he has JTAG my S4 to unbrick, updated my recovery to CWM, put back my baseband to MDK again. After he has fixed my phone in under 2 days, he has sent it back via priority to me. The only reason it took this long is because when I sent him the phone, USPS delayed my package.
So, I must say, I would recommend mobiletechvideos to anyone looking to get specialized work done on their phones.
I am very happy today to have my phone back!!! ok, lets see what are the latest ROMs...
Click to expand...
Click to collapse
Good for you!
Wish my experience would have been so good, would have saved me the hassle of selling it on eBay and then finding another MDK 32gig Verizon S4.
I'll know who to send it to if it ever happens again
if you are indeed still on MDK should just be a matter of running the loki exploite and you should be good to go
next time don't go fiddling with stuff you don't fully understand
Legitsu said:
next time don't go fiddling with stuff you don't fully understand
Click to expand...
Click to collapse
The more I learn, the more I realize how little I know. I am pretty sure that applies to you as well.
here is a jpeg of phone info see attachment. no matter where i look i hit dead links on this because it is so old i guess the rom files dont keep forever. so what do i do after trying to twrp it after kingoroot succes it now it only boots into download mode. but i dont know what to flash it with being on 4.2.2?
devtinagub said:
here is a jpeg of phone info see attachment. no matter where i look i hit dead links on this because it is so old i guess the rom files dont keep forever. so what do i do after trying to twrp it after kingoroot succes it now it only boots into download mode. but i dont know what to flash it with being on 4.2.2?
Click to expand...
Click to collapse
Theoretically you should be-able to use motochopper and install a custom recovery without any drama .... just don't quote me on that as I am not sure ...
Sorry couldnt get anything from motochopper.
WAS RESEARCHING MY PROBLEM AND FOUND THE FOLLOWING LINK :
http://samsung-updates.com/device/?id=SCH-I545
Is anyone familiar with this site ? Should I try one one of these archive firmware downloads to flash and hope it gets my phone going again ? Is my thinking that starting with MK2 is right? And what is the unlock link for? I guess I can try it and see make sure they arent dead links. Heres to hoping someone can answer some of my ? and to something working from this samsung update site. Thanks for any and all help.
So those links were also dead. Ended up flashing OC1. I know it's not the best since it's not easy to work with. But kingroot actually worked and so I may not have a custom rom but at least it's rooted. Now I am trying to figure out how to use it without becoming a Verizon customer beyond WiFi.