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.
Related
I have a Nabi 2 tablet that I've rooted, installed TWRP, and flash the gapps and a few other tweaks to. It's about to go in for an RMA since the USB and charging ports are both broken. The problem in the USB port is that one of the pins got bent - I don't know how, it looks like the conductor somehow got peeled back off of the plastic. The point is, I have no USB access to the device.
In order to pass the inspection for the RMA, I need to have it stock I can flash the stock ROM by putting it on the SDCard in my laptop then transferring that to the device and flashing it through TWRP. The question I have, though, is whether I can flash the stock recovery with ADB access to it. Every thread I've been able to uncover so far about flashing a recovery requires ADB access to issue the "adb fastboot flash" command. Is there another way to do this?
If the ROM your going to return it with (stock) has the flash image binary then you can use a terminal emulator but I doubt this will work as most often stock ROMs don't. But maybe worth a shot
Otherwise depending on how the tablet and recovery are set up possibly flash the stock recovery through twrp
Would need to know a lot more about your tablet to say for sure how to do it
Sent from my Nexus 4 using Tapatalk 2
Yes. Sometimes I have seen recovery-from-boot.p and install-recovery.sh restore it on first boot after you have restored stock ROM.
If not...
Copy a stock recovery.img to your external SDcard
After restoring your Nabi ROM.
Use TWRP "mount" tab and make sure external_sdcard is checked
Use TWRP "Terminal Command"
dd if=/external_sdcard/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
I forget when TWRP add terminal command, if you have an older version you'll have to update it first.(same idea as flashing stock, just get the 2.6.0.0 TWRP image and put on external SD) There are some other methods but I think this is easiest without a functioning USB
aicjofs, thanks!
It could just be my current sleep-deprived state, but this line confused me:
aicjofs said:
Yes. Sometimes I have seen recovery-from-boot.p and install-recovery.sh restore it on first boot after you have restored stock ROM.
Click to expand...
Click to collapse
The way my brain interpreted it says that once the stock ROM is restored, it will automatically restore the recovery on first boot.
I have some part of my brain screaming "NO!" though, so I'm not sure what you were trying to say there. Care to enlighten me?
oh, and I've got TWRP 2.2.2.1, and it does have a terminal emulator, but it's clunky at best.
Dan in SA said:
aicjofs, thanks!
It could just be my current sleep-deprived state, but this line confused me:
The way my brain interpreted it says that once the stock ROM is restored, it will automatically restore the recovery on first boot.
I have some part of my brain screaming "NO!" though, so I'm not sure what you were trying to say there. Care to enlighten me?
Click to expand...
Click to collapse
Yes some have claimed it returned them to stock recovery. That file is only like 300kb though so it can't be the full image as the kernel alone is 4MB+. Maybe it's just the ramdisk, but its too large for that. I can't imagine it works but that's what people have claimed, probably shouldn't have said I have seen because I haven't personally seen it, just heard. I would do the method I talked about and dd the image from TWRP.
All can be recovered without USB port as long as you can boot either Android or TWRP just don't lose both at same time
Ok, thanks I'll try and get it charged tonight, and flash the stock ROM tomorrow and see what happens.
One more quick question - I don't have a recovery.img file. I have recovery.emmc.win and mmcblk0p1.img - they're both 8,192kb. I'm assuming I would either rename the first to recovery.img, or use the second and dd it into /dev/block/platform/sdhci-tegra.3/mmcblk0p1
Am I on the right track?
Dan in SA said:
Ok, thanks I'll try and get it charged tonight, and flash the stock ROM tomorrow and see what happens.
One more quick question - I don't have a recovery.img file. I have recovery.emmc.win and mmcblk0p1.img - they're both 8,192kb. I'm assuming I would either rename the first to recovery.img, or use the second and dd it into /dev/block/platform/sdhci-tegra.3/mmcblk0p1
Am I on the right track?
Click to expand...
Click to collapse
Yes on the first but No on second. The way you have it won't work but you are close. for dd the "if" = input file, and the "of" = output file. Both are your input file. recovery.emmc.win = mmcblk0p1.img and an image of recovery partition basically a different name for the same thing.(the same as boot.emmc.win = mmcblk0p2.img an image of boot partition) In this case the input is either of those 2 files, and the output is the recovery partition.
So you could use any of the following it's just changing the name of the input
dd if=/external_sdcard/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS (if you renamed one of the two files to recovery.img)
dd if=/external_sdcard/recovery.emmc.win of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
dd if=/external_sdcard/mmcblk0p1.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
Just use the above...but to confuse you more you could be using mmcblk naming convention in the output file as you stated. Tegra renames the mmcblk block format, think of it as a symlink so you can call a single location 2 different names.
so /dev/block/platform/sdhci-tegra.3/by-name/SOS is the same as /dev/block/mmcblk0p1 and is the recovery partition itself
another example /dev/block/platform/sdhci-tegra.3/by-name/LNX is the same as /dev/block/mmcblk0p2 and is the boot partition
knowing that you could take the first example from above
dd if=/external_sdcard/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
and write it as
dd if=/external_sdcard/recovery.img of=/dev/block/mmcblk0p1
and accomplish the same thing, so you were close just no "/platform/sdhci-tegra.3" Hopefully I didn't come across as offensive as I imagine you already know some of the above
I knew that (DUH! :cyclops: ) I told ya I was sleep deprived.
I'm going to flash it this afternoon and see what falls out.
Thanks bunches!
Ok, first step finally done.
Got the JmzNabi2Stock_OLD.zip loaded. Got the dreaded "turning wifi on" error, but skipped that step to move on. Currently waiting for "Please wait while your nabi device is being initialized. This might take a few minutes."
It has been at least 5 minutes, but to be honest this is going faster than the FC17 to FC19 upgrade I have going on on the system next to it. It's had a blank screen with the disk spinning since I started this about 30 minutes ago.
WooHoo! as I was typing that last para, the setup screen showed up. I'll go through som rudimentary things just to check and make sure this image isn't rooted, then I'll try to reload the stock recovery.
edit: crap, this wasn't the "stock" image. Now I need to head off and try to find that......
Whelp, that didn't work. One of the ROM flashes broke the recovery and lost root. Without ADB, I can't do anything more
Dan in SA said:
Whelp, that didn't work. One of the ROM flashes broke the recovery and lost root. Without ADB, I can't do anything more
Click to expand...
Click to collapse
If the recovery doesn't boot I doubt they will even look deeper then that and think you messed it up.
If you still want to attempt it you have to use an exploit to gain root again(Android still boots right?) Unfortunately most exploits are using ADB as a means to that end. ADB restore bug, elevating ADB shell to root via local.prop edit, for example. I would think the Android master key exploit would work on this device but the only good tool I have seen for it is Cydia Impactor. GUI that's compiled so its not easy to short cut and do locally without following the write up and manually doing everything(In short no one click that will work without USB). I think memdroid or something like that only worked up until 4.0.2 or something so I think Nabi is patched against it. It can be done I just don't know if you want to go to the effort. Should have used the Nabilab full stock ROM and stock recovery to restore as they are matched set.
aicjofs said:
Should have used the Nabilab full stock ROM and stock recovery to restore as they are matched set.
Click to expand...
Click to collapse
I did, but when I booted that up after I loaded the ROM, SuperSU was installed implying that the image was rooted already.
Too late now, it's in the box going back to Nabi tomorrow.
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
Greetings.
My recovery function is completely broken on my phone.
My Galaxy S4 is rooted, was on latest CM with CWM recovery installed. All was well... until I issued a shell command I saw on-line in a dev conf, 'dd' with parameters, and the recovery partition no longer boots. Device is functional expect for recovery mode. Attempts to go into recovery mode just dump into ODIN with "Cannot boot normally" line. Normal boots are fine. ODIN does work but attempt to write any recovery programs just fail.
I have since installed a number of recovery items like CWM, TWRP and even one for locked bootloaders, and all say they installed but none of them work. I am able to use ABD without issue and I have switched back to the Samsung stock rom (rooted) until I get this addressed.
I have not been able to locate a way using ABD to reinstall the recovery partition.
My guess is that the 'dd' command I executed changed the load point for the recovery partition or damaged something in the partition. I need to know how to completely reinstall (format I guess) the partition to make it usable again.
This one is a stumper. I have used rooted phones and customer ROMs for years and as you know without recovery you are pretty much stuck. I want to go back to using CM but it updates a lot and I can't install any updates.
Any help is most appreciated.
Using Odin to go back to the stock firmware should overwrite whatever you did to the recovery partition. As far as the 'dd' commands go, it depends on which variant of the S4 you have, which is probably where you messed up at. The Exynos versions and Snapdragon models have the recovery partition in different spots.
(i9505) dd if=/sdcard/recoveryfilename.img of=/dev/block/mmcblk0p21
(i9500) dd if=/sdcard/recoveryfilename.img of=/dev/block/mmcblk0p10
Thank you.. that makes sense. I will reload if necessary.
Question.... Do you think I could reissue the correct DD command for my phone?
I have the US Verizon version of the I545. I don't know how to find that, but I have nothing to lose I guess.
bthye said:
Thank you.. that makes sense. I will reload if necessary.
Question.... Do you think I could reissue the correct DD command for my phone?
I have the US Verizon version of the I545. I don't know how to find that, but I have nothing to lose I guess.
Click to expand...
Click to collapse
You would use the one for the Snapdragon/LTE version - i9505 though since you have a Verizon version - that explains it. The bootloader is locked unless you're still on an older 4.2.2 update and took the steps to keep it unlocked while upgrading.
es0tericcha0s said:
You would use the one for the Snapdragon/LTE version - i9505 though since you have a Verizon version - that explains it. The bootloader is locked unless you're still on an older 4.2.2 update and took the steps to keep it unlocked while upgrading.
Click to expand...
Click to collapse
Ok, this is all starting to make sense now. I think I did use the wrong one, killed the recovery partition, then when I upgraded to the latest stock it locked the bootloader. What a mess! I see now why I had so much trouble finding info on this. This would be a pretty rare problem.
I will reload everything, but am I stuck with a locked bootloader again? ie No work around this time?
If so I will use one of the recoveries designed for locked. I used on prior and it worked fine.
My goal is to get back to the latest CM and be able to update often.
My thanks again for the great assistance here!
bthye said:
Ok, this is all starting to make sense now. I think I did use the wrong one, killed the recovery partition, then when I upgraded to the latest stock it locked the bootloader. What a mess! I see now why I had so much trouble finding info on this. This would be a pretty rare problem.
I will reload everything, but am I stuck with a locked bootloader again? ie No work around this time?
If so I will use one of the recoveries designed for locked. I used on prior and it worked fine.
My goal is to get back to the latest CM and be able to update often.
My thanks again for the great assistance here!
Click to expand...
Click to collapse
If you updated via Odin to anything past 4.2.2 MDK, then you are really out of luck since it is not possible to load CM on locked bootloader / Safestrap recovery due to not being able to load custom kernels. I find Hyperdrive to be a good TouchWiz rom, if you don't have any other options.
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 :<(
Have a Verizon SCH-I535 running android 4.4.2 I have been trying in vain for two days now to root this phone and replace the stock recovery. I'm aiming for running clockworkmod recovery and cyanogenmod. I've followed their instructions using terminal and heimdall which DOES WORK and communicate with device.
Problem is EVERY TIME I boot to recovery and try to run anything...a stock zip to downgrade it says "failed to verify whole-file signature" and "signature verification failed."
The only thing I can do is run towelroot.apk, install superSU.apk, and use the stock ROM. Using ODIN is a waste of time and fails every file every time. At this point I'm honestly kinda amazed I don't have a brick I've done so many transfers! I also always wipe data/cache before I install zips off SDcard.
I'm out of answers. Oh! At one point my counter was too high and it was also saying, "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help. " I downloaded TriangleAway and it reset the counter back to zero and the error went away, but there for a while I couldn't even get to recovery (take battery out and cancel out of download mode FYI to boot back into device).
Samsung Kies is the closest glimmer of hope I've gotten. Twice now it has returned my phone back to stock; so I don't think its a hardware issue ie. bad ram or ROM memory...
I've rooted a couple older Galaxy S3's running 4.3 with no issue. It's been a couple years but that was a simple ODIN flash and I kept standard ROM/recovery as I was flashing carriers and didn't want to risk breaking anything.
I'd like to think I'm not an idiot, but what the hell am I missing. I've watched dozens of youtube videos and read hundreds of guides that all seem to work. It's something with this phone and kies or some type of heightened security...
Thanks in advance! You can also email me at [email protected]
Anyone? Even a, "Yeah, that's weird man! Sounds like you did everything right!" Would make me feel better...
Yes I've tried it and it worked make sure u have the unofficial safestrap the one for your phone and do the busy box and terminal emulator thing and it works if you try to install safestrap without the other things you will brick I did it twice but it very easy to unbrick so download busybox terminal emulator and the correct safestrap for you device and also I'm on 4.4.2 also and there is only one rom i have found that works and its called superliter there ya go hope I help would provide download links but I'm not home
Also I forgot to mention your bootloader won't be unlocked it'll be bypassed and you will have a custom recovery
androidforums.com/threads/verizon-verizon-bootloader-unlock.856221/page-2[/url]
forum.xda-developers.com/showthread.php?t=2605648
device specific safestrap recovery and image
4.4.2 has a 'locked bootloader' courtesy of Verizon! This is what has been giving me fits... Going to try to go back to totally stock 4.4.2 (right not my bootloader is the international version and locked out), then towelroot to root, then install root explorer/supersu, then I'll try safestrap and hopefully its the miracle cure!
schmitey said:
Have a Verizon SCH-I535 running android 4.4.2 I have been trying in vain for two days now to root this phone and replace the stock recovery. I'm aiming for running clockworkmod recovery and cyanogenmod. I've followed their instructions using terminal and heimdall which DOES WORK and communicate with device.
Problem is EVERY TIME I boot to recovery and try to run anything...a stock zip to downgrade it says "failed to verify whole-file signature" and "signature verification failed."
The only thing I can do is run towelroot.apk, install superSU.apk, and use the stock ROM. Using ODIN is a waste of time and fails every file every time. At this point I'm honestly kinda amazed I don't have a brick I've done so many transfers! I also always wipe data/cache before I install zips off SDcard.
I'm out of answers. Oh! At one point my counter was too high and it was also saying, "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help. " I downloaded TriangleAway and it reset the counter back to zero and the error went away, but there for a while I couldn't even get to recovery (take battery out and cancel out of download mode FYI to boot back into device).
Samsung Kies is the closest glimmer of hope I've gotten. Twice now it has returned my phone back to stock; so I don't think its a hardware issue ie. bad ram or ROM memory...
I've rooted a couple older Galaxy S3's running 4.3 with no issue. It's been a couple years but that was a simple ODIN flash and I kept standard ROM/recovery as I was flashing carriers and didn't want to risk breaking anything.
I'd like to think I'm not an idiot, but what the hell am I missing. I've watched dozens of youtube videos and read hundreds of guides that all seem to work. It's something with this phone and kies or some type of heightened security...
Thanks in advance! You can also email me at [email protected]
Click to expand...
Click to collapse
Verizon spends a pretty penny when it comes to making sure their devices................. stay theirs i guess you can say when it comes to the boot-loader! To my knowledge their isn't a way of getting around that with a permanent recovery flash that completely replaces Verizon's stock recovery. I can almost guaranteeing you that your problem is Verizon locked boot loader. Stock recoveries are solely only their for their technicians, so unless someone somehow has leaked a program that they use to get around that stuff without screwing it up, we the general public will never be able to flash anything permanent with any phones stock recovery unless we have their "secret" software! Every once in a while you do find a leaked one. I got lucky and found one for the T-mobile galaxy S6 Edge. As far as Odin I've noticed that the new versions seem to be very particular. Meaning if a dot or a space is misplaced anywhere in the zip or what not it will always fail. With my t-mobile S6 I spent two days figuring out I had to take a letter out of the name of the file i was trying to Odin. One letter that was it and once I did that it went flawlessly. Otherwise man i really don't know what to tell you, seems like ya followed the lines as described. Just remember its a Samsung Galaxy in my opinion Galaxies are unbrickable. Ive even pulled the cord in the middle of a Odin flash to see if i could brick it for good and was still able to go right into download mode and flash stock back onto it and everything working. So don't be afraid of bricking it. It will be way easier (sorry to say) for you to re-flash stock right now! Good luck bro wish you the best!
---------- Post added at 08:25 PM ---------- Previous post was at 08:18 PM ----------
schmitey said:
4.4.2 has a 'locked bootloader' courtesy of Verizon! This is what has been giving me fits... Going to try to go back to totally stock 4.4.2 (right not my bootloader is the international version and locked out), then towelroot to root, then install root explorer/supersu, then I'll try safestrap and hopefully its the miracle cure!
Click to expand...
Click to collapse
Are you able to disable Signature verification in the recovery?
Are you able to disable Signature verification in the recovery?
You can once I flash to say clockworkmod recovery. Stock I don't know of a way to...hence the Catch 22 there's no going forward and no going back...you're stuck with stock ROM/recovery but at least its rooted.
Well ****. Take my word for it you CAN brick a galaxy s3.
I used KIES to restore back to factory stock recovery etc etc.
I then used towelroot to root phone and install supersu. I then installed safestrap which totally worked! I was able to bypass the stock recovery and everything was running smoothly...I got overzealous and tried to install the cyanogenmod vrale6 bootloader zip through safestrap. I currently have a brick. It won't boot, no led's, no screen, no vibrate. I have another galaxy s3 charging batteries and swapped it out...removed sim and micro sd. I should have just installed the cyanogenmod app and done it that way...
So close and now I bricked it...
OK got my brick back by writing image to microSD card...pretty happy about that little trick. And that's utter nonsense about needing the same size card as your internal memory! I used a 32gig card on a 16gig phone...
Still trying but this locked 4.4.2 bootloader is BULL****. Going to try to downgrade but I'm not sure I'm going to end up with anything but a rooted stock rom...
So does anyone know of a way to downgrade or change recovery on Verizon 4.4.2?
I have s3 Verizon I-535 & clockworkmod recovery is not gonna work cuz of the locked bootloader, I used safestrap that's the only recovery for 4.4.2
slimcyril said:
I have s3 Verizon I-535 & clockworkmod recovery is not gonna work cuz of the locked bootloader, I used safestrap that's the only recovery for 4.4.2
Click to expand...
Click to collapse
Thanks for the reply. But with safestrap its a step in the right direction but every zip fails...so I don't see what it really does for us. Don't see myself ever running cyanogenmod at this rate unless you know something I don't...
schmitey said:
Thanks for the reply. But with safestrap its a step in the right direction but every zip fails...so I don't see what it really does for us. Don't see myself ever running cyanogenmod at this rate unless you know something I don't...
Click to expand...
Click to collapse
Well no zip has ever failed on my end using safestrap, does your device have init.d support?
No point me to it! I'm basically stock rom running safestrap atm. If you can walk me through this I'd be grateful.. Just remember I'm locked Verizon bootloader...
And may I say I finally got the I535 switched to selectel (was on a flashed sprint L710) and holy cow 4G LTE is fast...faster than my home internet!
schmitey said:
No point me to it! I'm basically stock rom running safestrap atm. If you can walk me through this I'd be grateful.. Just remember I'm locked Verizon bootloader...
And may I say I finally got the I535 switched to selectel (was on a flashed sprint L710) and holy cow 4G LTE is fast...faster than my home internet!
Click to expand...
Click to collapse
Go to mount on safestrap & see if your system partition is checked(mounted) e.t.c & go to playstore install universal init.d app
Note; uncheck verify signature checks if you're trying flash anything via recovery or else it will definitely fail
slimcyril said:
Go to mount on safestrap & see if your system partition is checked(mounted) e.t.c & go to playstore install universal init.d app
Note; uncheck verify signature checks if you're trying flash anything via recovery or else it will definitely fail
Click to expand...
Click to collapse
system partition is NOT checked within safestrap. Installed universal init.d but I'm out of my league on it... Init.d says stock kernel does not have support...