Develop Bugs

[Q] Soft-Bricked after 4.3 update, what's the protocol?

Sorry if this is a repeat question, but after searching I still can't seem to find a solution (that I can understand anyway.) I relatively new, having only rooted this phone once before, successfully, but a year ago. I've been reading up for the past two days, but I can't seem to find the soft-brick solution to the new Knox problem.
Short history: Rooted 4.2 a while back, but the speakers stopped working (constant headphone mode) so I thought a software update was finally in order. Did the 4.3 update (not knowing about Knox) to see if that fixed the headphone issue (it didn't) then installed TWRP and tried to install the 4.4 OMNI nightly. After install, it hangs on Samsung logo (soft brick?). Restored to backup, but still hangs. Tried installing SlimKat 4.4, but the install fails. Unsure where to go from here.
Phone still powers up, goes into both Download and Recovery mode. TWRP is the current bootloader(?)/recovery(?).
So, is there a simple reason I'm soft-bricked? I read that Knox is in the bootloader, so is it because I'm using TWRP that it hangs? I find it odd that after restoring to previous settings it still doesn't function. Also, I don't care about the warranty bit, so anything is on the table for me.
Much love to those who spend the time to help out, please link to any resources for me and others who have the same problem. I'll append the working solution to this post for quick access in the future!

Ripptor said:
Sorry if this is a repeat question, but after searching I still can't seem to find a solution (that I can understand anyway.) I relatively new, having only rooted this phone once before, successfully, but a year ago. I've been reading up for the past two days, but I can't seem to find the soft-brick solution to the new Knox problem.
Short history: Rooted 4.2 a while back, but the speakers stopped working (constant headphone mode) so I thought a software update was finally in order. Did the 4.3 update (not knowing about Knox) to see if that fixed the headphone issue (it didn't) then installed TWRP and tried to install the 4.4 OMNI nightly. After install, it hangs on Samsung logo (soft brick?). Restored to backup, but still hangs. Tried installing SlimKat 4.4, but the install fails. Unsure where to go from here.
Phone still powers up, goes into both Download and Recovery mode. TWRP is the current bootloader(?)/recovery(?).
So, is there a simple reason I'm soft-bricked? I read that Knox is in the bootloader, so is it because I'm using TWRP that it hangs? I find it odd that after restoring to previous settings it still doesn't function. Also, I don't care about the warranty bit, so anything is on the table for me.
Much love to those who spend the time to help out, please link to any resources for me and others who have the same problem. I'll append the working solution to this post for quick access in the future!
Click to expand...
Click to collapse
TWRP is your recovery. How were you wiping in between flashes? Sounds like the phone wasnt wiped correctly, causing it to hang. You should be able to flash any ROM zip, because ROM zips dont flash the bootloader, they just flash the system and the kernel. You can flash 4.3 stock tar file in ODIN, but you cant flash anything under 4.3 in ODIN, because tar files flash all parts including the bootloader. If you flash a 4.2 stock tar in ODIN, you will brick instantly.

joeyhdownsouth said:
TWRP is your recovery. How were you wiping in between flashes? Sounds like the phone wasnt wiped correctly, causing it to hang. You should be able to flash any ROM zip, because ROM zips don't flash the bootloader, they just flash the system and the kernel. You can flash 4.3 stock tar file in ODIN, but you cant flash anything under 4.3 in ODIN, because tar files flash all parts including the bootloader. If you flash a 4.2 stock tar in ODIN, you will brick instantly.
Click to expand...
Click to collapse
I used ODIN to flash TWRP, then wiped using TWRP, factory reset/dalvik cache. It seems that the problem was actually with TWRP, however. Apparently it doesn't install 4.4 KitKat ROMs correctly, from another post that I read. I installed PhilzTouch Recovery instead, and it installed just fine. Phone is working just fine running the latest SlimKat, however I still have no audio output.. So, still gotta figure that out.

[Q] Bricked my I747 - Please Help?

Hello,
I'm sure there are many threads on about what I'm about to asked but I am a noob and I don't know what to do!!
I tried to flash cm11 to my I747 last night but it failed. So I tried to flash my recovery and it failed at first but second time around it was successful. Only thing is that when it booted, it got stuck on AT&T splash. I left it for about 15-20 minutes but nothing happened. Wasn't sure if my screen was going to burn the image so I turned it off and removed the battery. I have been doing research on how to recover but I want to make sure I do everything correct so I can at least go back to stock.
If there is anyone out there that can please give me some help I would greatly appreciate it!
Thanks!!
Is this fixable?

loc626 said:
Hello,
I'm sure there are many threads on about what I'm about to asked but I am a noob and I don't know what to do!!
I tried to flash cm11 to my I747 last night but it failed. So I tried to flash my recovery and it failed at first but second time around it was successful. Only thing is that when it booted, it got stuck on AT&T splash. I left it for about 15-20 minutes but nothing happened. Wasn't sure if my screen was going to burn the image so I turned it off and removed the battery. I have been doing research on how to recover but I want to make sure I do everything correct so I can at least go back to stock.
If there is anyone out there that can please give me some help I would greatly appreciate it!
Thanks!!
Is this fixable?
Click to expand...
Click to collapse
\
Yeah. Should be fixable. First, can you try booting to recovery and doing a wipe/reset? I presume you have custom recovery? If this doesn't work, then you can try flashing a complete compatible stock restore image via recovery to get the phone working or flash a custom ROM? What Android version were you on prior to the attempt to flash CM? This would let us know what stock version to revert to.

I was running 4.3 before trying to flash the custom rom. I tried flash the stock rom last night using Odin, but it the flash failed on me twice. I also noticed that the micro sd I had in my cell is now completely dead. When I plug it into my pc it does not show up. I think it still shows up in recovery but it doesnt seem to be working. Im worried about sticking another card in and for some unknown reason it going dead too.
I only found a flash for 4.1.1 as far as stock rom goes.

loc626 said:
I was running 4.3 before trying to flash the custom rom. I tried flash the stock rom last night using Odin, but it the flash failed on me twice. I also noticed that the micro sd I had in my cell is now completely dead. When I plug it into my pc it does not show up. I think it still shows up in recovery but it doesnt seem to be working. Im worried about sticking another card in and for some unknown reason it going dead too.
I only found a flash for 4.1.1 as far as stock rom goes.
Click to expand...
Click to collapse
If you were already on 4.3, please do not try to flash 4.1.1 now otherwise you could risk bricking your phone. If you tried doing the hard wipe/reset via (custom) recovery and this did not work, you can try flashing a complete stock restore image via recovery. See the instructions in the following thread ....
http://forum.xda-developers.com/showthread.php?t=2658486
Unfortunately, you would need to load the stock restore zip to a (micro) SD card. Unless you are able to save files to your phone, there is no other way. Once you have the restore zip ready, boot your phone to recovery mode and flash. You can revert to a custom ROM once your phone is back to working normally.

I had this problem TeamWin Recovery. I put Philz recover on there and it worked fine. You will probably have to ADB philz recovery to your phone, if you chose to try Philz. This is what worked when I rooted my girlfriend's phone.

An easy way to install Philz Touch recovery would be to download and install the latest tar version for the d2lte and flash it via Odin.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte

Thanks to everyone for your help and solutions.
My co-worker, who flashed my root and recovery, was able to get it back to 4.3 stock. Unfortunately, the backup that he made before rooting did not work in recovery [twrp]. So I lost all my pics from the last two months since getting my phone.
As sad as I was that I couldn't recover the pics, I am happy to have my phone back to normal+root.
I'm not sure, but maybe it bricked from trying to flash cm11 thru twrp?! Can't really say, but the recovery did not go thru either.... It went thru "successfully" but after I would reboot then it would stay on ATT splash.
Oh well... all is good now. I will steer away from custom roms for now and wait until the 4.4 update comes out for my i747. Or if i get another phone later on, I can use the s3 as a lab rat.
Again, thanks to everyone!

[Q] Soft Bricked my i747- HELP!

So I was able to root phone on w/o issue. I installed CWM via play store then proceeded to attempted to load Cyanogen mod via zip..and oh yeah I didn't wipe phone prior so....Now I have infinite loop issue at boot. I've searched the interwebs looking for any way to get back to stock or anything so I'll be able to use the phone again but have come up short every time. I've tried using ODIN to flash stock image but that fails. I've tried various .tar, .tz and anything else that odin will load w/o success. Will anyone take pity on my stupid ass and lens a hand?

exarkun631 said:
So I was able to root phone on w/o issue. I installed CWM via play store then proceeded to attempted to load Cyanogen mod via zip..and oh yeah I didn't wipe phone prior so....Now I have infinite loop issue at boot. I've searched the interwebs looking for any way to get back to stock or anything so I'll be able to use the phone again but have come up short every time. I've tried using ODIN to flash stock image but that fails. I've tried various .tar, .tz and anything else that odin will load w/o success. Will anyone take pity on my stupid ass and lens a hand?
Click to expand...
Click to collapse
Are you able to boot in recovery? (volume up + home + power). You could wipe and try flashing again (the first boot does take a while).
As for Odin, make sure you're using the right image (.tar) if recovery doesn't work.
Here's a little Odin guide: [ODIN] Desktop ODIN ver 3.07 for use with Samsung Galaxy S III

yeah I tried that
BWolf56 said:
Are you able to boot in recovery? (volume up + home + power). You could wipe and try flashing again (the first boot does take a while).
As for Odin, make sure you're using the right image (.tar) if recovery doesn't work.
Here's a little Odin guide: [ODIN] Desktop ODIN ver 3.07 for use with Samsung Galaxy S III
Click to expand...
Click to collapse
So I am able to boot into recovery but it's the stock recovery, not the one I intalled after root.
I've tried flashing stock images, custom images, CWM, TWRP, .TARs all w/o success. In ODIN I've flashed CWM and TWRP and it reports success but upon reboot it goes back to stock recovery and shows now 13 attempts to load custom firmware. I even tried to use Cyanogen,s windows app but even that gets stuck saying it can't communicate w/device. I've tried several driver, hiemdal, (which I can't figure out). What I'd like to do wipe EVERYTHING, like format the phone but I can't seem to remove the Samsung boot loader. Is my phone beyond repair? I'm super bummed, esp since I'm not a total noob when it comes to custom ROMs. I dropped greenpoison on my fist iPhone and had several ROMs on my old Moto Atrix. I think whatever evil Samsiung put on this device is totally screwing me.

exarkun631 said:
So I've tried flashing stock images, custom images, CWM, TWRP, .TARs all w/o success. In ODIN I've flashed CWM and TWRP and it reports success but upon reboot it goes back to stock recovery and shows now 13 attempts to load custom firmware. I even tried to use Cyanogen,s windows app but even that gets stuck saying it can't communicate w/device. I've tried several driver, hiemdal, (which I can't figure out). What I'd like to do wipe EVERYTHING, like format the phone but I can't seem to remove the Samsung boot loader. Is my phone beyond repair? I'm super bummed, esp since I'm not a total noob when it comes to custom ROMs. I dropped greenpoison on my fist iPhone and had several ROMs on my old Moto Atrix. I think whatever evil Samsiung put on this device is totally screwing me.
Click to expand...
Click to collapse
Try with a different stock image (debloated if you want a smaller download).
Also, Heimdall installs its own drivers, therefor Odin won't work on the same usb port you've installed Heimdall on.
Even in stock recovery, you should be able to do a factory reset (I think). Chances are that your ROM is corrupted atm though, you can try doing a factory reset and attempt boot. If that doesn't work, go the Odin way.
Bootloaders are not something to play with, it's the only way to hard-brick your phone (and you definitively don't wanna remove those nor stop Odin while it's flashing them, if the .tar contains them).

what about...
BWolf56 said:
Try with a different stock image (debloated if you want a smaller download).
Also, Heimdall installs its own drivers, therefor Odin won't work on the same usb port you've installed Heimdall on.
Even in stock recovery, you should be able to do a factory reset (I think). Chances are that your ROM is corrupted atm though, you can try doing a factory reset and attempt boot. If that doesn't work, go the Odin way.
Bootloaders are not something to play with, it's the only way to hard-brick your phone (and you definitively don't wanna remove those nor stop Odin while it's flashing them, if the .tar contains them).
Click to expand...
Click to collapse
I updated the phone via ota to latest android (4.3 ?). And I think the stock image I tried using was 4.1.x. Could it be I need to find a stock 4.3.x image from at&t? Any idea where to get this? I don't think AT&T provides ythis as that is where I got the previous stock image.

exarkun631 said:
I updated the phone via ota to latest android (4.3 ?). And I think the stock image I tried using was 4.1.x. Could it be I need to find a stock 4.3.x image from at&t? Any idea where to get this? I don't think AT&T provides ythis as that is where I got the previous stock image.
Click to expand...
Click to collapse
Can you check if the image you used had bootloaders? Cause if so, you might have bricked your phone. You can't downgrade bootloaders from 4.3.
The image can be found here or on sammobile.com

Strange
So after flashing my i747 30x via ODIN w/various .tar for boot and recoveries I was briefly able to boot into CWM. Stupidly, I selected the format option and foolishly restarted, intending to boot back into CWM and flash a .zip image. Once I restarted I was locked out of CWM again and can only boot into stock recovery once again. What am I doing wrong? I just can't wrap my head around why every time I flash a custom recovery like CWM or TWRP or Philz's_Touch in OdIn and it reports success, when I restart it just loads Samsung's ****ty stock recovery. I still can't flash a ROM via ODIN but I'm hoping if I can get back into CWM I'll be able to load a new ROM and use my phone again. Anyhelp would be great.
BWolf56 said:
Can you check if the image you used had bootloaders? Cause if so, you might have bricked your phone. You can't downgrade bootloaders from 4.3.
The image can be found here or on sammobile.com
Click to expand...
Click to collapse

lol
exarkun631 said:
So after flashing my i747 30x via ODIN w/various .tar for boot and recoveries I was briefly able to boot into CWM. Stupidly, I selected the format option and foolishly restarted, intending to boot back into CWM and flash a .zip image. Once I restarted I was locked out of CWM again and can only boot into stock recovery once again. What am I doing wrong? I just can't wrap my head around why every time I flash a custom recovery like CWM or TWRP or Philz's_Touch in OdIn and it reports success, when I restart it just loads Samsung's ****ty stock recovery. I still can't flash a ROM via ODIN but I'm hoping if I can get back into CWM I'll be able to load a new ROM and use my phone again. Anyhelp would be great.
Click to expand...
Click to collapse
So I think I figured out what I did wrong. Recovery mode = pwr+home+VolUp...Download mode = Pwr+home+VolDown. What an a$$hole I am, I thought Download mode and Recovery were one in the same and flashing TWRP or CWM would replace download mode. Once I figured out that one it was a simple matter to boot into recovery and wipe the drive then flash my rom (Omni 4.4.2 D2att) IDK if it's the rom or all the screwing around I did but it now takes no less than 10 min to boot into android from rom splash. Tried updating Kernel to latest but found it didn't fix problem.

exarkun631 said:
So I think I figured out what I did wrong. Recovery mode = pwr+home+VolUp...Download mode = Pwr+home+VolDown. What an a$$hole I am, I thought Download mode and Recovery were one in the same and flashing TWRP or CWM would replace download mode. Once I figured out that one it was a simple matter to boot into recovery and wipe the drive then flash my rom (Omni 4.4.2 D2att) IDK if it's the rom or all the screwing around I did but it now takes no less than 10 min to boot into android from rom splash. Tried updating Kernel to latest but found it didn't fix problem.
Click to expand...
Click to collapse
Did you do a clean flash? Sounds like you didn't factory reset.
Make sure you backup your apps before doing so if you wanna keep your app data.

[Q] Sprint Galaxy S3 will not complete boot process

I've searched around for this specific problem and haven't found anything that will help me. I have the SPH-L710 model through Sprint that was previously running Android 4.4.2. That version killed the battery, so I attempted to root and install a custom ROM. I have rooted before, so superSU was already on the phone. I opted to follow the rooting directions from galaxys3root.com, which uses ClockworkMod Recovery v5.5.0.4. I did that and installed superSU again via a .zip file. When I rebooted the phone, superSU kept stopping. After some frustration, I found that there was an updated superSU v2.01 that I installed via CWM. Being an idiot, I figured I would just go right ahead and trying to install the custom ROM without checking anything. I then attempted to install the Carbon ROM 4.4.4 from galaxys3root.com without first making a backup of my existing version (again, idiot). There was some sort of error, and after that point, I was unable to boot up the phone...it would display the Samsung GS3 screen and then do a continuous bootloop.
I tried finding stock ROMS, but they usually have to be loaded from the SD card rather than through ODIN, and they so far haven't been working. I have downloaded more than one that claimed to be an MD5, but they turned out not to be. My wife has the exact same phone so I thought maybe if I use CWM to save a backup of hers to my SD card, perhaps I could restore that and boot up my phone. I got a bit farther this time and boot up made it through the Samsung GS3 and various Sprint 4g screens before getting stuck on the last Samsung screen.
If I can get the phone to boot up again, I've since learned that once you update superSU, you can have it disable knox, thereby allowing me to root, and thereby allowing me to install a custom ROM, but at this point I just need to get the phone to boot up so I can use it again.
Summary:
Attempted to root using CWM v5.5.0.4
Did not properly disable Knox first and had an error loading custom ROM
Phone stuck in bootloop
Did not back up phone first but have a backup of my wife's exact same model
Used that backup and it gets stuck on very last Samsung screen
Any and all help is appreciated.
Matt

huntley said:
Summary:
Attempted to root using CWM v5.5.0.4
Did not properly disable Knox first and had an error loading custom ROM
Phone stuck in bootloop
Did not back up phone first but have a backup of my wife's exact same model
Used that backup and it gets stuck on very last Samsung screen
Any and all help is appreciated.
Matt
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2738533 <-----Odin stock ND8 rom use Desktop Odin
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/philz_touch_6.48.4-d2lte.tar.md5/ <------flash this recovery through Odin as well it gives you the option to root the stock ND8 rom under Philz settings choose option re-root(SuperSU)

6th_Hokage said:
http://forum.xda-developers.com/showthread.php?t=2738533 <-----Odin stock ND8 rom use Desktop Odin
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/philz_touch_6.48.4-d2lte.tar.md5/ <------flash this recovery through Odin as well it gives you the option to root the stock ND8 rom under Philz settings choose option re-root(SuperSU)
Click to expand...
Click to collapse
Thank you. That image worked perfectly, and the recovery is a newer version than I was trying to use earlier.

huntley said:
Thank you. That image worked perfectly, and the recovery is a newer version than I was trying to use earlier.
Click to expand...
Click to collapse
i know lol but its the best one for stock ND8 honestly

[Q] Bricked? Note 8 GT-N5110 stuck on boot loop

Hi all,
I've looked through several of the existing threads on the Note 8 and I've not gotten anywhere yet. I had the device happily rooted and working for months and then, stupid me, I used ROM manager to flash a new ROM this morning and on boot, it's stuck on the logo.
I CAN get to the recovery menu, but reset to factory default does nothing. I have wiped the cache from recovery and then tried to factory reset again; still stuck on logo at boot.
I can also get to download mode and have tried using KIES 2.6 (since KIES 3 is for Android 4.4.2 and up) and every time I try to do the update firmware/recovery, it starts, stops and says 'there is a problem with the download file' and then it quits.
I have tried using ODIN 3.7 and a few different recovery files but although it will say 'passed', on reboot, it's stuck on the logo.
Can someone help me, please? This is the only tablet I own and I really need it to not be a door stop
:crying:

not bricked yet, maybe. for now, try to download latest firmware from sammobile.com for n5110 and use odin to flash it.
about the factory reset of course it would still boot loop, you are trying to factory reset a bootlooped rom so it doesnt matter. you should flash a new zip through recovery.

Mr.201 said:
not bricked yet, maybe. for now, try to download latest firmware from sammobile.com for n5110 and use odin to flash it.
about the factory reset of course it would still boot loop, you are trying to factory reset a bootlooped rom so it doesnt matter. you should flash a new zip through recovery.
Click to expand...
Click to collapse
Hi Mr.201,
Thank you for the suggestion. Question, when you say download the latest firmware, will it matter if I don't use the original? I ask because I've been trying to find the original firmware (stock) and while I've found many sites with GT-N5110 FW's, they are all coded for other countries; I can't seem to find one for US. So, if I use a newer firmware, will that work?
I can still get to recovery mode and download mode. I don't know if USB debugging is on, though, which I hope won't matter at this point. I can't remember if it was on when it died on me.
I appreciate your advice! Hopefully, I can get this thing going again. That would certainly make me a happy camper!

For some reason, the US version is labelled as "Cellular South" but in general, any 5110 rom will work, although there are some quirks with wifi frequencies between the North American and European roms.

My Note 8 got stuck in a boot loop. It was rooted/custom recovery/custom ROM. I tried some of things you did, and nothing worked. I ended up downloading and installing the ODIN one click recovery/un-rooted stock image from this thread:
http://forum.xda-developers.com/showthread.php?t=2773712
This restores everything to stock (including the recovery). After flashing, it was still stuck in the boot loop. I booted into the factory recovery, and did a data wipe. After doing that, my note is working now. So ... doing this might be worth a try.

May I make a suggestion when flashing firmware... If you are flashing to something notreviously installed on the device. First flash with philz recovery and perform a full wipe for flashing new ROM. This way everything is clean for your flash to work properly.
A factory reset is not going to work as well for the new flash to take.