Wiped phone, Trying to get a Firmware on it, Failing miserably. - Sprint Samsung Galaxy S6 Edge

Yo, I've been trying to fix the damned phone for ages now. I accidentally wiped it by being a dumb idiot. Now I'm trying to fix the situtaton. So, I've tried installing a stock firmware and just flashing it with Odin. After trying this with like three different Firmwares, and sequential failures, I moved on to trying to flash it with a custom rom using adb, as the s6 doesn't have a removable sd. So I tried this, It said it worked. I used an installer and everything. But after I reboot, it still says there's no os and I cant find the zip anywhere on my phone to install. I'm not sure what to do. I'm a noob with this hence why my phone is in this state. Help MUCH obliged, S6 edge Sprint

http://forum.xda-developers.com/showthread.php?t=3219484

Related

[Q] Verizon Galaxy S3- Me Messing up

As the title of this suggests, I messed up BIG TIME when attempting to get Cyanogenmod on my Verizon Galaxy S3.
Long story short, I tried putting CWM on my phone without looking up things about it, like whether or not the bootloader was locked for 4.4.2 Kitkat, which it was, and has been since 4.3 Jellybean, which I did not know at the time I tried screwing with my device (which was around a week ago), and I started trying to mess with the phone without knowing what the hell I was doing, since the last time I tried modding a GS3 was over two years ago.
Long story, well, long, I tried installing CWM via the ROM Manager app, and, upon installing it, I screwed up the recovery mode on the phone. It wasn't a big deal, until I decided I wanted to put the latest version of Cyanogenmod on it, instead of using the stock Touchwiz interface.
Well, a couple days ago, I stuck Safestrap on it, and was able to use that as a recovery mode, since the normal recovery mode was locked off, entirely.
I figured that, tonight, I would look up ways to stick Cyanogenmod on my GS3.
I found a couple ways to do so, downloaded the gapps file I needed, the SU binary update, as well as an unofficial version of Cyanogenmod to let me use 5.1 Lolipop.
Well, I wiped the cache on the phone, as well as the dalvik cache, and factory reset the thing, ad went to the folder I put the gapps, SU binary update, and CM files in, and tried installing them.
Well, the SU update went fine.
gapps won't install.
The CM file I'm using SAYS it's installed, but the phone doesn't have an OS, which is confusing me.
I don't know if the phone is bricked, I just know that I did something stupid, and I don't know how to put an operating system back on the phone, either through Kies or Odin (I can't install anything from the SD card in the phone, because now I can't access it, since when I boot it up, there's no OS, and I need one to access the files on the device).
Whenever I try using Odin to put either a stock firmware version on it, it fails.
My phone, in DL mode, says: "SECURE CHECK FAIL : RECOVERY"
I don't know what this means, but I think it means I'm pretty well screwed.
I need to get rid of CWM and Safestrap via my computer, THEN reinstall the stock recovery mode on my computer, too.
I NEED to know how to do this.
If there is ANYONE out there who can help me out, or direct me to some other thread, that would be amazing, and GREATLY appreciated.

Kernel/System Load Issues

Hey guys,
I've used XDA for quite a while now as a resource for rooting and flashing my phones. After some trial and error, I finally got a custom rom and root onto my previous phone, the Samsung Galaxy Light (SGH-T399). However, I booted the T-MOBILE kernel, not MetroPCS, and got locked out. So I bought a Galaxy Core Prime, and after a bit decided to root that as well. But when I did some sort of permission modification and tried to make my extSD writeable, the phone crapped out. It would not load the kernel past the bootloader. I tried flashing everything and anything. It just would not allow it to write or mount properly.
So I went back and tried restoring the T399 until I sorted that out, and the same thing is happening. I even flashed ShabbyPenguins stock rom which never failed me before, to no avail . I was able however to successfully install TWRP again. Someone please help me out, I can't afford another phone at the moment. Im still a novice, but I know enough to know it's more than just a mistake in Odin or a file I didn't upload. I've tried searching for an answer to no avail.
P.S. -I'm 90% sure it's a partition issue of some sort, where the filesystem isn't being communicated with properly.

I might have permanently bricked my phone

Hey, I made this account to ask this question I'm pretty desperate,
My phone was acting up (overheating, WiFi didn't work half the time), so I decided to reflash my cyanogenmod rom, me being the idoit that I am I didn't do a backup before formatting my phone, I tried to flash the zip file but twrp kept crashing, so the next logical step was to use ADB sideload to flash the rom, that didn't work as well as I expected either the install kept failing at 88% as I was rebooting the phone for yet another attempt, recovery wouldn't start at all, at that point I was pretty frustrated, so I decided to flash the phone back to stock touchwiz, I downloaded the stock firmware and attempted to flash it with odin, low and behold that didn't work either (auth error), I tried again multiple times with firmware files downloaded from different sites but those didn't work either, I also tried flashing stock PIT files to no avail.
So here I am at 5 am with a bricked phone and 8gb of tar files on my desktop any help at all would be greatly appreciated.
Thanks in advance.
i know this thread is old, but can you get to download mode still?
What's the model and type of phone is this ?

Bricked? This shouldn't be happening.

Here's a basic rundown of what happened. I completely rooted my Galaxy S III i535 on 4.4.2, and i installed SafeStrap (A Version of TWRP) since the Verizon S3 has a locked bootloader.
So here's what I tried to do. Using SafeStrap, I backed up my stock rom. And i selected another ROM slot. Using this, i tried experimenting by installing a ROM for another Carrier (They say not to do this, but i have in the past with success, so i thought it mightve worked)
(KEEP IN MIND, THE STOCK OS WAS STILL INSTALLED AND I EVEN HAD A BACKUP)
So, it didnt work and stopped halfway. I rebooted the phone, and Hard bricked.
Doesnt boot up, does not turn on, will not boot recovery or download, or any sign of some boot at all.
And, i get the qhsusb_dload sign on my pc.
Can anyone point me in the right direction, or at least tell me the cause of this problem? Thanks.
CrimsonKatsuro said:
Here's a basic rundown of what happened. I completely rooted my Galaxy S III i535 on 4.4.2, and i installed SafeStrap (A Version of TWRP) since the Verizon S3 has a locked bootloader.
So here's what I tried to do. Using SafeStrap, I backed up my stock rom. And i selected another ROM slot. Using this, i tried experimenting by installing a ROM for another Carrier (They say not to do this, but i have in the past with success, so i thought it mightve worked)
(KEEP IN MIND, THE STOCK OS WAS STILL INSTALLED AND I EVEN HAD A BACKUP)
So, it didnt work and stopped halfway. I rebooted the phone, and Hard bricked.
Doesnt boot up, does not turn on, will not boot recovery or download, or any sign of some boot at all.
And, i get the qhsusb_dload sign on my pc.
Can anyone point me in the right direction, or at least tell me the cause of this problem? Thanks.
Click to expand...
Click to collapse
The solution may be a debrick image. They are designed to boot the phone from an external sdcard and from there reinstall the stock rom/firmware. I haven't searched yet, but check the general and development threads, possibly the stickied summary thread.
Check this thread

J7 Perx Won't Root - need it to recover photos

Good morning. This is my first time posting here.
My father gave me his J7 Perx (for Boost) because he accidentally ran it over and whatever reason factory reset (phone still works). I have been trying with no luck to root this stupid phone because I am trying to recover photos that we need in an upcoming lawsuit. Evidently only way to do so is to root the phone to gain access to internal storage. I can't afford to pay someone to do this - which is why I am doing it myself.
I haven't rooted in years but over the past week I've literally spent hours combing this website - reading almost every thread I can find. I've flashed the stock 8.1 rom more times than I can count because no matter what I do the phone either wind's up not rooted or stuck as the "Samsung J7 Perx Warranty Set Kernel" screen.
My latest attempt was installing TWRP; wiping and formatting data; installling MAGISK through the SD Card and rebooting. This doesn't work. MAGISK is not installed; Root is not obtained and I am back at square one. I also found another thread that included a .tar file for the J7 which was supposed to have Super SU. I flash through ODIN and nothing works. This winds up making the phone not even boot up (stuck on the Samsung J7 screen). I think at one point I even tried a combination of: flashing stock 8.1 ROM; Installing TWRP; immediately erasing and formatting data; installing MAGISK; booting back into download; flashing that .tar file - and then I get stuck at no boot and wind up re-flashing stock.
I don't remember ever having this much trouble rooting a device and frankly, all I need to do is try and recover photos. What am I doing wrong? Why won't this MAGISK program install? Can someone give me a hand? I've combed through all those threads but can't seem to get a clear cut answer (wife is now getting angry at me for not paying attention to her this week).
Root
sdemat0201 said:
Good morning. This is my first time posting here.
My father gave me his J7 Perx (for Boost) because he accidentally ran it over and whatever reason factory reset (phone still works). I have been trying with no luck to root this stupid phone because I am trying to recover photos that we need in an upcoming lawsuit. Evidently only way to do so is to root the phone to gain access to internal storage. I can't afford to pay someone to do this - which is why I am doing it myself.
I haven't rooted in years but over the past week I've literally spent hours combing this website - reading almost every thread I can find. I've flashed the stock 8.1 rom more times than I can count because no matter what I do the phone either wind's up not rooted or stuck as the "Samsung J7 Perx Warranty Set Kernel" screen.
My latest attempt was installing TWRP; wiping and formatting data; installling MAGISK through the SD Card and rebooting. This doesn't work. MAGISK is not installed; Root is not obtained and I am back at square one. I also found another thread that included a .tar file for the J7 which was supposed to have Super SU. I flash through ODIN and nothing works. This winds up making the phone not even boot up (stuck on the Samsung J7 screen). I think at one point I even tried a combination of: flashing stock 8.1 ROM; Installing TWRP; immediately erasing and formatting data; installing MAGISK; booting back into download; flashing that .tar file - and then I get stuck at no boot and wind up re-flashing stock.
I don't remember ever having this much trouble rooting a device and frankly, all I need to do is try and recover photos. What am I doing wrong? Why won't this MAGISK program install? Can someone give me a hand? I've combed through all those threads but can't seem to get a clear cut answer (wife is now getting angry at me for not paying attention to her this week).
Click to expand...
Click to collapse
Yep I´M having same trouble, but wife not angry lol
centaur1 said:
Yep I´M having same trouble, but wife not angry lol
Click to expand...
Click to collapse
I'm ready drive over the phone a second time. I can't feasibly understand why this won't root.

Categories

Resources