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.
Related
Merry Christmas everyone. I tried to resolve this issue my self but was unable to. I had stock 4.3 rooted and flashed MOAR. MD5 matched. Everything seemed ok but when I flashed, it was stuck on "updating apps" for over 20 min. I did a battery pull. My phone started and I was able to go to TWRP recovery. I did a cache wipe and factory reset with plans of reflashing but everything was gone, including my nandroid. I tried to flash stock firmware from http://samsung-updates.com/ it said "failed". I cannot get back into TWRP. Is there any way I can restore to 4.1.2? Or 4.3? I just want to get the phone working again. Ideally I would like to get root back but my main priority is obviously just to get the phone working. Thank you.
jeppuda said:
Merry Christmas everyone. I tried to resolve this issue my self but was unable to. I had stock 4.3 rooted and flashed MOAR. MD5 matched. Everything seemed ok but when I flashed, it was stuck on "updating apps" for over 20 min. I did a battery pull. My phone started and I was able to go to TWRP recovery. I did a cache wipe and factory reset with plans of reflashing but everything was gone, including my nandroid. I tried to flash stock firmwa.
Click to expand...
Click to collapse
I had a similar bad expreience with updating my rooted S3,
to recover your phone try to get md5 recovery room and install it using odin, try to get the one that called recovery (runs stock 4.0.4) then you can update by Kies to 4.3.
If stock means the Samsung update you need to flash the 4.3 firmware. If stock means the de-Knoxed version from here, I would start by flashing a new recovery image then reinstalling the de-Knoxed one.
Can you not get into any recovery at all?
mjkubba said:
I had a similar bad expreience with updating my rooted S3,
to recover your phone try to get md5 recovery room and install it using odin, try to get the one that called recovery (runs stock 4.0.4) then you can update by Kies to 4.3.
Click to expand...
Click to collapse
MD5 recovery room (or rom I googled both)? I could not find it. I'm sorry i have never done this before...could you post the link for it?
Kevets said:
If stock means the Samsung update you need to flash the 4.3 firmware. If stock means the de-Knoxed version from here, I would start by flashing a new recovery image then reinstalling the de-Knoxed one.
Can you not get into any recovery at all?
Click to expand...
Click to collapse
When I press the volume up, home and power button it says "firmware upgrade encountered an issue. Please select recovery mode in kies and try again."
I installed the de-knoxed version..I would like to go back to the de-knoxed version if possible. Is there a way to flash new recovery image through ODIN...again, I'm not very confident in my abilities right now and don't want to flash anything to make it worse. Would it be possible to send me a link with what to flash. Thank you
Sorry I meant rom not room, but youv still can get it from the dev "room" forums. I got it from there.
sorry I cant post links here yet, i dont have the enough posts, but google "unroot sprint galaxy s3" it's one of he first links and once you get the md5 file you can use it with Odin, it's a simple process.
fixed it
Fixed it, got to keep root also. Flashed a new recovery image through ODIN (link for recovery in case anyone else needs it: http://forum.xda-developers.com/showthread.php?p=38079994). Then flashed ROM. Thanks for your help guys.
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!
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.
So, after years of flashing roms on my phones, this is the first time I got a bootloop issue.
First of all, I tried to install the new Dn3 5.5 rom, which didnt get installed properly and ended up having my Knox warranty bit triggered.
Now on the 'downloading' screen, it shows two more lines,
KNOX WARRANTY VOID: 1
SWREV: A2
I read the forums and am guessing that even after this I should be able to flash custom roms, but I cant.
I tried installing the stock firmwares through Odin, but everything failed giving me an 'Invalid magic string' error, except the new FNI1 firmware, which I am assuming, worked because its the latest one and I cant downgrade due to the Knox bit being set.
Now although my phone has booted up, I rooted it using CF Auto root and de-knoxed it using Dr.Ketan's Multitool, I cant seem to turn off the phone.
Everytime I perform a reboot or 'power off' or even perform a hard restart, it shows the grey battery icon, turns off and loops again.
I have to clear the cache, after which it boots normally.
So, summarizing,
Phone gets a bootloop on the charging screen, and cannot install custom roms.
I am assuming its a bootloader issue, but need some guidelines by someone who has an idea about why this is happening just so that I dont mess up my phone more.
I need to perform a downgrade, and if possible reset the Knox bit too if anyone knows how to by now.
I think Dr.Ketan might be able to help out.
Thanks a lot.
Tan9890 said:
So, after years of flashing roms on my phones, this is the first time I got a bootloop issue.
First of all, I tried to install the new Dn3 5.5 rom, which didnt get installed properly and ended up having my Knox warranty bit triggered.
Now on the 'downloading' screen, it shows two more lines,
KNOX WARRANTY VOID: 1
SWREV: A2
I read the forums and am guessing that even after this I should be able to flash custom roms, but I cant.
I tried installing the stock firmwares through Odin, but everything failed giving me an 'Invalid magic string' error, except the new FNI1 firmware, which I am assuming, worked because its the latest one and I cant downgrade due to the Knox bit being set.
Now although my phone has booted up, I rooted it using CF Auto root and de-knoxed it using Dr.Ketan's Multitool, I cant seem to turn off the phone.
Everytime I perform a reboot or 'power off' or even perform a hard restart, it shows the grey battery icon, turns off and loops again.
I have to clear the cache, after which it boots normally.
So, summarizing,
Phone gets a bootloop on the charging screen, and cannot install custom roms.
I am assuming its a bootloader issue, but need some guidelines by someone who has an idea about why this is happening just so that I dont mess up my phone more.
I need to perform a downgrade, and if possible reset the Knox bit too if anyone knows how to by now.
I think Dr.Ketan might be able to help out.
Thanks a lot.
Click to expand...
Click to collapse
Knox trigger can't be reversed.
Of course, it is a bootloader issue. Follow the procedure and it should work out well for you.
1. Use stock recovery to wipe cache and factory reset.
2. Don't use cf-auto root.
3. Download Philz recovery latest version and supersu zip file. (For Note 2 )
4. Flash Philz. Uncheck auto reboot option in ODIN. Once you get pass message, unplug. Don't start your phone yet. Boot directly into recovery.
5. Install supersu zip file
6. Reboot to check if you are rooted.
7. DN3 5.5 has given me a headache. But it must be something ---- looking at the number of people using it.
8. I prefer Dr. Ketan's V12 Touchwiz ROM.
With Aroma installer, it is almost impossible to go wrong. Support is amazing. Doc himself answers all queries as fast as he can. But choice is yours.
Press thumps up if you found this suggestion helpful.
Link to all the files: http://www.ibtimes.co.uk/root-galax...d-4-4-2-kitkat-install-philz-recovery-1447891
Sent from my GT-N7100 using Tapatalk
Hi...Thanks for the quick reply.
Your solution did help, although partially. I liked the idea of unchecking the auto-reboot option.
I installed the SuperSU as you said, but the problem still remains. I think the bootloader resets all the root access everytime it boots. I had to go with CF autoroot to get it booting again.
But the good news is, with the autoreboot turned off, I was able to install a custom rom.
Here's what happened.
I installed the rom successfully, rebooted the phone n got back to the same battery screen again. Tried hard resetting it but couldnt get too the boot screen. Then I flashed the CF autoroot after which it booted fine into the Aosb rom.
I think a patched bootloader which removes the root disabling would do the trick here. Also, the recovery also gets removed during the next boot.
So is there any way to flash a different bootloader from ODIN? I have this Patched MJ5 bootloader, but there's an error saying 'SWREV: CHECK FAIL, DEVICE:2, BINARY:1'
Tan9890 said:
Hi...Thanks for the quick reply.
Your solution did help, although partially. I liked the idea of unchecking the auto-reboot option.
I installed the SuperSU as you said, but the problem still remains. I think the bootloader resets all the root access everytime it boots. I had to go with CF autoroot to get it booting again.
But the good news is, with the autoreboot turned off, I was able to install a custom rom.
Here's what happened.
I installed the rom successfully, rebooted the phone n got back to the same battery screen again. Tried hard resetting it but couldnt get too the boot screen. Then I flashed the CF autoroot after which it booted fine into the Aosb rom.
I think a patched bootloader which removes the root disabling would do the trick here. Also, the recovery also gets removed during the next boot.
So is there any way to flash a different bootloader from ODIN? I have this Patched MJ5 bootloader, but there's an error saying 'SWREV: CHECK FAIL, DEVICE:2, BINARY:1'
Click to expand...
Click to collapse
Don't flash old bootloaders. Now you are on NI1. (Only a 4.4.2-based bootloader can rewrite the existing bootloader)
Also, losing recovery is common. On 4.4.2, it gets rewritten. Hence, after flashing recovery you should not reboot the phone immediately.
Instead, as I said you press the key combo to enter recovery (preferably Philz recovery) as soon as you flash it.
Clear cache and factory reset.
Then you start the phone
Also, most custom ROMs are prerooted. You don't even have to use cf-auto or supersu zip to root your device if you intend to flash a custom ROM.
I don't know which ROM you like, but, ideally, a ROM should be prerooted, zip aligned and deodexed. For instance, DN3 5.5 and Dr.Ketan's V12 are the leading ones in this category. In fact, you have Omni, Phantom, Ultra, Diamond, etc, etc. One is simply spoilt for choice.
Caution: Bootloaders are sensitive. If they get screwed up, your phone will end up in service centre.
Sent from my GT-N7100 using Tapatalk
ceomaverick said:
Don't flash old bootloaders. Now you are on NI1. (Only a 4.4.2-based bootloader can rewrite the existing bootloader)
Also, losing recovery is common. On 4.4.2, it gets rewritten. Hence, after flashing recovery you should not reboot the phone immediately.
Instead, as I said you press the key combo to enter recovery (preferably Philz recovery) as soon as you flash it.
Clear cache and factory reset.
Then you start the phone
Also, most custom ROMs are prerooted. You don't even have to use cf-auto or supersu zip to root your device if you intend to flash a custom ROM.
I don't know which ROM you like, but, ideally, a ROM should be prerooted, zip aligned and deodexed. For instance, DN3 5.5 and Dr.Ketan's V12 are the leading ones in this category. In fact, you have Omni, Phantom, Ultra, Diamond, etc, etc. One is simply spoilt for choice.
Caution: Bootloaders are sensitive. If they get screwed up, your phone will end up in service centre.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Yes, but I am losing the recovery everytime when I boot. Its like, Once the rom gets set up and running. I should not switch off or restart my phone at all. Else it again goes back to the battery charging screen and gets stuck.
In case I have to reboot, I must flash the CF autoroot so that it restarts the rom.
Sounds weird right?
Tan9890 said:
Yes, but I am losing the recovery everytime when I boot. Its like, Once the rom gets set up and running. I should not switch off or restart my phone at all. Else it again goes back to the battery charging screen and gets stuck.
In case I have to reboot, I must flash the CF autoroot so that it restarts the rom.
Sounds weird right?
Click to expand...
Click to collapse
Very weird. Never heard of such a thing. Btw, which recovery you are using? TWRP or CWM. Also, chk if the version is latest. The latest versions are fixed for these very issues.
Probably, flashing N7100XXUFNI1 out of the box should solve your problem.
Beyond that I don't have answers.
Sent from my GT-N7100 using Tapatalk
Snippet taken from: http://mark.candleshoreblog.com/2013/06/13/tip-steps-to-prevent-clockwork-or-any-custom-recovery-from-being-overwritten-by-factory-stock-roms-at-android-system-reboot/:
The reason your stock recovery system keeps getting overwritten at Android startup is because of a script that is being run. All you need to do is either rename this script or simply delete it.
Please keep in mind that if you restore your stock ROM, this script will be restored with it so you will have to rename or delete it again. Do the following:
1.
Make sure your device is powered on and running normally,
2.
Make sure you have rooted your device and that you have all of the necessary permissions in order to manipulate system files.
3.
In the root file system go to \system\etc
4.
Find the file named install-recovery.sh and either rename it or, as I did, delete it.
That’s all there is to it.
A couple days ago, I tried to flash my i747 back to stock, but unfortunately it froze at the Samsung Galaxy S III logo, and is no longer accessible. Another mistake that I think I made was I failed to realize that my phone would go back to stock recovery with flashing the stock rom. As a result, I now can't flash any custom rom or recovery due to "signature verification failed" error. Lastly, my phone can't seem to connect to the computer, so I can't use Odin either. When I connect my phone (in download mode) to the computer, an error would pop up saying that "one of the USB devices has malfunctioned"...I already tried to use different USB cables, different computers, update driver, battery pull, wipe data/factory reset, wipe cache, etc...but nothing prevailed. I'm a newbie to the android system, and I would really appreciate any suggestion on how I might get out of this conundrum, and get my phone back. Thank you!
Before you attempted to flash back to stock what ROM were you running?
What bootloader and modem were on your device before trying to flash stock?
Which stock rom did you attempt to flash to your phone?
If you were not flashing an older bootloader than was on your phone, you may need to do a factory reset from the stock recovery and reflash the stock rom. If you attempted to flash an older bootloader than had been on the device, you may need to search the forums for a debrick image with the same bootloader that was on the device before this started.
Before you attempted to flash back to stock what ROM were you running? __Dirty Unicorns 5.1.1__
What bootloader and modem were on your device before trying to flash stock? Baseband version: I747UCUFNJ1 (DU rom); does flashing a custom rom change the bootloader/modem? if not, i think the modem is I747UCUEMJB
Which stock rom did you attempt to flash to your phone? Jellybean 4.1.1 _I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5_
Actually, I was able to successfully flash back to the stock rom before the hanging at logo problem occurred, except for the fact that there was no sound and apps such as youtube failed to function properly. And so, what I did was I put a debrick.img into the internal storage and run "su dd if=/sdcard/debrick.img of=/dev/block/mmcblk0" in terminal, because I have bricked my phone and this has worked to bring back the sound in the past. If I remember correctly, I've used the the "debrick command" several times before and occasionally the phone would hang just like now, but then I just had to reflash the rom with the custom recovery and the phone would go back to normal. However, im stuck with the stock recovery this time and can't flash anything. Anyway, is there something that i can try with the new infos? Thank you for helping!
zynl said:
...what ROM were you running? __Dirty Unicorns 5.1.1__
...before trying to flash stock? Baseband version: I747UCUFNJ1 (DU rom);
i think the modem is I747UCUEMJB
Which stock rom did you attempt to flash Jellybean 4.1.1 _I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5_
Click to expand...
Click to collapse
No, flashing a custom ROM will not change bootloader and modems, but stock ROMs will.
Baseband and modem are the same thing, as is radio (in most instances). Since you had DU running successfully, in all probability your bootloader and modem were both NJ1. Everything I have seen indicates all AOSP and CM 5.x.x and their derivatives must be on at least NE4 bootloader and modem. If you can get into download mode, and their is anything on the screen about "Warranty Bit" you were on a 4.3 or higher bootloader.
Now for the negative; if you were on a 4.3 or higher bootloader downgrading the bootloader will brick the device. Once you are on any of the 4.4.2 bootloaders, NE4 or newer, you must keep the bootloader and modem versions paired. That is: they must both be NE4, or both NJ1, or both NJ2 otherwise you risk bricking the device. (This is why I think your bootloader was NJ1.) More negative is that the 4.1.1 stock rom you flashed contains the LK3 bootloader and modem.
zynl said:
Actually, I was able to successfully flash back to the stock rom before the hanging at logo problem occurred, except for the fact that there was no sound and apps such as youtube failed to function properly. And so, what I did was I put a debrick.img into the internal storage and run "su dd if=/sdcard/debrick.img of=/dev/block/mmcblk0" in terminal, because I have bricked my phone and this has worked to bring back the sound in the past. If I remember correctly, I've used the the "debrick command" several times before and occasionally the phone would hang just like now, but then I just had to reflash the rom with the custom recovery and the phone would go back to normal. However, im stuck with the stock recovery this time and can't flash anything. Anyway, is there something that i can try with the new infos? Thank you for helping!
Click to expand...
Click to collapse
I am surprised you were able to boot at all after flashing the stock ROM. If you are still able to boot froman external sdcard, flashing a debrick image is what I would suggest next. Once you boot, install a custom recovery and verify bootloader and modem on the device from the recovery terminal if possible. The next step would be flashing the NJ1 bootloader and modem. Two threads for reference:
http://forum.xda-developers.com/galaxy-s3-att/general/solution-hard-brick-fix-amazing-t2962611
http://forum.xda-developers.com/showthread.php?t=2549068
If this doesn't work you may be looking needing a jtag service. Worse than that would be a new motherboard for the phone.
Hello
To me it look like you get stuck in boot. First you will need to download correct ATT ROM. Then you will need to select appropriate option in ODIN. Let me know if you have any question. I will help you out. Guaranteed))
If you are able to boot into recovery and download mode, the debrick sdcard method won't do any good. Not saying to not try it if you want to, but I've never seen it work unless the device is truly hard bricked (totally unresponsive). It's only in those cases that it will even look for the image on an SD.
When you boot download mode and connect to the computer, does Odin show a COM# in the upper left? Does it respond in any way at all?
Also check to make sure kies is NOT installed on the computer. It can interfere with Odin. If you still cannot connect, try an older driver version. (See my sig).
Uninstall the old first. Then install the other version and reboot. Connect the device and open device manager. Right click on the USB device that isn't working and update driver. Try auto if you want, but if that doesn't work select manual. Browse to the Samsung folder in Program files and try selecting it that way. (I can't recall the exact location, but you should be able to find it if you poke around a little).
Hope that helps.
Good luck!
Sent from my SGH-T999 using Tapatalk
thanks everyone for helping. after abt a week trying to revive my phone, i finally gave up. recently though, i bought a bricked motherboard for cheap and successfully unbricked it. everything seems to be working fine except i can't switch on the wifi. I already tried wiping cache, factory reset, and even reflashing stock rom (4.3 from samsung) via odin but nothing worked. So, i wonder what could be the source of this? (hardware?.... software??... bc the volume up button also does not work!) and is there something that i can try to possibly fix this? The phone is currently on 4.3, bootloader and modem are both i747UCUEMJB.