Develop Bugs

[Q] Stuck in Boot Loop

I'm new to Android and tried to flash a customer ROM and am now stuck in a boot loop. Any help will be appreciated and I'll try to explain myself the best I can.
1. I have a Bell Note 2 and rooted with the CF auto root process
2. I upgraded SuperSU after the root reboot and installed the reboot checker. it said i was rooted.
3. I used titanium backup to backup candy crush
4. I installed ROM Manager and installed ClockWorkMod Recovery. My Note 2 wasn't supported, but I read that i could use the international version from the list so i did that. Everything said it was successful.
5. I downloaded the DN3 Rom from the forums here and transferred to my SD card.
6. I booted into CWM Recovery and did a backup from the options there.
7. Then I chose to install a customer rom and searched for the zip file on my microSD card.
8. The DN3 splash screen came up and took me through some install screens. I chose everything for the SGH-i317M options during the install.
9. it rebooted and loops between the samsung note II splash screen the CWM recovery 6.0.4.3 screen for a second and continues to loop between the two.
I can't get to the CWM recovery screen. if i try it just keeps looping. I'm sitting in the odin mode screen now and i think i need to install a stock rom. Can anyone point me in the right direction to at least get it working? then i'll need to see what i did wrong. thanks.

So i'm in odin mode and found a stock rom to reinstall. it gets to Modem, then fails so i'm not sure if i grabbed the wrong one. I believe i can install a rom through odin now that i can get to odin mode, is that right? but i can't really find any roms around to load cause all the ones i fond are zip files. Do i need to find an MD5/tar file? and where would i find them?

Try sammobile.com

Thanks for the reply. I tried that but the share for the firmware was no good. I ended up resolving it through Keis emergency firmware update.

AntonovichNS said:
Thanks for the reply. I tried that but the share for the firmware was no good. I ended up resolving it through Keis emergency firmware update.
Click to expand...
Click to collapse
That's good you figured it out yourself...:thumbup:
That's what I was going to recommend to you...
Me 2¢®
Sent from my SAMSUNG-SGH-I317 using Tapatalk

[Q] TWRP 2.6.3.1 Asks for password

I woke up this morning to my phone perpetually rebooting.
I was running a nightly of CM 11.
Now when I try to go into Recovery I get a screen that asks for a password. I have no idea what that password is as I did not set one. I tried wiping data to no avail. I tried flashing a new recovery via Odin this did not work (Odin said successful but the screen on the phone never showed the transfer of the file). No matter what wipe method I use in recovery it just says fail, doesn't work at all and hangs or will say it can't mount. I have searched and searched and tried and tried and I'm stuck. I even tried ADB that didn't work either. Please help!

Try flashing Philz Touch (based on CWM) over TWRP via Odin. I have always had good luck with CWM and Philz.
Download the tar version: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att

audit13 said:
Try flashing Philz Touch (based on CWM) over TWRP via Odin. I have always had good luck with CWM and Philz.
Download the tar version: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att
Click to expand...
Click to collapse
I tried this already. I cannot flash ANYTHING via ODIN. Odin states that the process completed but the bar on the phone on the download screen never shows up to show that it has accepted a file.

therecker said:
I tried this already. I cannot flash ANYTHING via ODIN. Odin states that the process completed but the bar on the phone on the download screen never shows up to show that it has accepted a file.
Click to expand...
Click to collapse
Did you unchecked F . reset and unchecked auto reboot when you flashed recovery in Odin? After you flash the file you have to pull the battery then replace it and boot to recovery do not allow the phone to boot to OS or you have to flash again as your recovery will only stick if you pull the battery and boot to recovery after flashing it. After you get into it the first time all will be well with the world again you can flash your heart out.
I had twrp ask me for a password once I hit the back arrow key and told it to mount my external SD card then flashed my rom, bootloader, kernel and modem then rebooted no problem.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

theramsey3 said:
Did you unchecked F . reset and unchecked auto reboot when you flashed recovery in Odin? After you flash the file you have to pull the battery then replace it and boot to recovery do not allow the phone to boot to OS or you have to flash again as your recovery will only stick if you pull the battery and boot to recovery after flashing it. After you get into it the first time all will be well with the world again you can flash your heart out.
I had twrp ask me for a password once I hit the back arrow key and told it to mount my external SD card then flashed my rom, bootloader, kernel and modem then rebooted no problem.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
This did not work. When I use ODIN all that is happening is that ODIN says it has succeeded but the little progress bar that usually shows up on the phone when you are in download mode never comes up. I did try this method though and it didn't work.
I restarted the phone in ODIN mode then opened ODIN then connected the USB cable then unchecked the two boxes you mentioned then flashed a new non TWRP recovery then waited for ODIN to say successful then the phone never showed the progress bar so I waited 2 mins until I pulled the battery then I restarted phone directly to recovery and still have the password prompt. Even after hitting cancel I cannot interact with recovery because every option I choose just says fail. I cannot even mount external sd card.

What phone do you have? What was the most recent stock ROM on your phone? Maybe you can flash a stock ROM.

There is a copy of the stock Samsung 3e recovery (which we can't use to flash zips with) I'm curious if maybe it can overwrite what you have going on? On the password screen I wasn't hitting cancel I was simply hitting the back arrow key. I will see if I have a copy of the stock recovery, just maybe you can flash it then flash another recovery after that so you can fix your phone.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

I have Samsung Galaxy S 3 At&T (d2att) SGH-I747 whichever one of those you want. The most recent stock rom on the phone was when I bought it brand new a few months after it came out. I tried installing a stock rom. I tried this using ODIN and it failed. The issue here is that TWRP somehow encrypted the entire file system so NOTHING at all in recovery works. When I use ODIN mode it never shows on my phone that it is accepting a transfer from the computer. When I tried the stock rom via ODIN method it actually failed in ODIN instead of telling me it succeeded and then just not work. It failed at the point when it says Firmware Update Start...aboot.mbn...NAND Write Start!...Complete(Write) operation failed. I am up for any suggestions but I need them to be detailed instructions because I have tried so many things I need to know what exact steps to follow.

I believe the aboot file is a bootloader. Did you ever have a stock 4.3 ROM on the phone? If you did, it probably has the stock 4.3 AT&T bootloader which cannot be downgraded without bricking the phone which means you cannot flash a ROM with an older bootloader via Odin.

audit13 said:
I believe the aboot file is a bootloader. Did you ever have a stock 4.3 ROM on the phone? If you did, it probably has the stock 4.3 AT&T bootloader which cannot be downgraded without bricking the phone which means you cannot flash a ROM with an older bootloader via Odin.
Click to expand...
Click to collapse
To my knowledge I never had a stock 4.3 ROM on the phone. The only stock ROM to touch this phone was the one that came on it. So be specific what are you actually suggesting in this post that I do?

therecker said:
To my knowledge I never had a stock 4.3 ROM on the phone. The only stock ROM to touch this phone was the one that came on it. So be specific what are you actually suggesting in this post that I do?
Click to expand...
Click to collapse
I am surprised that the aboot file was giving you a problem because the bootloader can be downgraded as long as it is not a 4.3 bootloader.
Do you recall exactly which ROM was on the phone when you got it? Where did you get the stock ROM?

audit13 said:
I am surprised that the aboot file was giving you a problem because the bootloader can be downgraded as long as it is not a 4.3 bootloader.
Do you recall exactly which ROM was on the phone when you got it? Where did you get the stock ROM?
Click to expand...
Click to collapse
It was a CM11 Nightly ROM from the very beginning of February. And before that it was a CM10.2 Stable ROM.

Which stock ROM was on your phone before you loaded a custom ROM?

audit13 said:
Which stock ROM was on your phone before you loaded a custom ROM?
Click to expand...
Click to collapse
I have no idea. It was when I first got the phone in November of 2012.

Sounds like your phone may be running a 4.3 bootloader which means your bootloader is locked and cannot be downgraded. This may explain why you are getting errors when trying to flash Odin. There is no stock AT&T 4.3 ROM that can be flashed via Odin.

No command Recovery problem Sprint Tab 3

Okay so here's the thing. I been following XDA for a while and I never had a problem with rooting and installing roms. Yesterday we received a Samsung Galaxy Tab 3 from Sprint. I believed it's the T217S version but anyways I looked up info and found out how to root it and put a custom recovery. Everything went fine until I decided to install the Remedy Rom. Now I wasn't sure if I had to wipe anything but just to be safe I did except the SD card. After that I Installed the Remedy Rom but before I could install the Knox Remover 1.2 it had already rebooted when it rebooted it bricked on the Samsung Logo. Now I began to panic but I researched and found out running the Stock Rom from Odin would fix this little issue. After running it back to stock. I again tried to get into Recovery but this time I got a different Recovery it said no command in the background and in the top Android system recovery. I remember I installed TWRP. I'm not sure what went wrong but now I can't restore it back to how it was. I can't even get into download mode to re root it.
Can anyone help me with this dilemma?

Can no one help me with this issue?

There was a recent sprint update to this device as of a few days ago. It's possible that the older rooting and recovery may not be compatible.
You might be able to Odin back to the prior version, then try root/recovery.

cougarcougar said:
There was a recent sprint update to this device as of a few days ago. It's possible that the older rooting and recovery may not be compatible.
You might be able to Odin back to the prior version, then try root/recovery.
Click to expand...
Click to collapse
Thank you for the reply. As I said I cant access download mode anymore so how can I run Odin through it? I can still boot into the Device itself I just can't enter recovery or download mode.

[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.

GS3 ATT Overwrites CWM, can I use this version of cfautoroot to root?

Hey guys,
Im not new to rooting and custom roms and all, but I never had something like this happen before. I'm on 4.4.2 on my i747 and I got the cwm from Clockworkmod.com and every time I flash the custom recovery with odin 3 my stock recovery overwrites cwm. Can I use the 4.0.4 version of cf autoroot to root my phone or will it brick?
Any help is appreciated, thanks again

Easiest way to root this phone is just flash supersu in custom recovery.
1) Download a recovery flashable supersu.zip to the phone storage.
2) Use Odin to flash custom recovery (consider using TWRP, CWM hasn't been developed in quite some time). Be sure to uncheck auto-reboot in Odin. Upon success do not reboot into system, unplug the USB cable and pull the battery.
3) Replace battery and boot straight into recovery. Hold vol up + home + power together and don't let go until you see "recovery booting" in little blue text in the upper left.
4) Make a backup in recovery, just in case things go wrong.
5) Flash the supersu.zip in custom recovery.
6) Reboot into system.
You might have to update the supersu binary and reboot a few times until it gets Knox properly disabled and everything settles. Once you're rooted the stock rom will stop overwriting your custom recovery every time you boot into it.
This phone is very brickable, but generally not when messing with recovery, rooting, or custom roms. The things that tend to result in hard bricks are messing with the bootloader and modem (keep them matched and don't ever downgrade), accidentally flashing a rom intended for i9300 (the other S3), or attempting to unlock the already not locked bootloader. Use caution in those areas and this is actually a pretty modder friendly phone (especially for a Samsung).

jason2678 said:
Easiest way to root this phone is just flash supersu in custom recovery.
1) Download a recovery flashable supersu.zip to the phone storage.
2) Use Odin to flash custom recovery (consider using TWRP, CWM hasn't been developed in quite some time). Be sure to uncheck auto-reboot in Odin. Upon success do not reboot into system, unplug the USB cable and pull the battery.
3) Replace battery and boot straight into recovery. Hold vol up + home + power together and don't let go until you see "recovery booting" in little blue text in the upper left.
4) Make a backup in recovery, just in case things go wrong.
5) Flash the supersu.zip in custom recovery.
6) Reboot into system.
You might have to update the supersu binary and reboot a few times until it gets Knox properly disabled and everything settles. Once you're rooted the stock rom will stop overwriting your custom recovery every time you boot into it.
This phone is very brickable, but generally not when messing with recovery, rooting, or custom roms. The things that tend to result in hard bricks are messing with the bootloader and modem (keep them matched and don't ever downgrade), accidentally flashing a rom intended for i9300 (the other S3), or attempting to unlock the already not locked bootloader. Use caution in those areas and this is actually a pretty modder friendly phone (especially for a Samsung).
Click to expand...
Click to collapse
Thanks. 2 more questions,
1) Do I use the .img.tar file [twrp-3.0.2-0-d2att.img.tar] or the .img file [twrp-3.0.2-0-d2att.img] here > https://dl.twrp.me/d2att/
2) I have the kot94h....NJ2 build number on my phone as I attempted root before, does this matter?

Ulti2x said:
Thanks. 2 more questions,
1) Do I use the .img.tar file [twrp-3.0.2-0-d2att.img.tar] or the .img file [twrp-3.0.2-0-d2att.img] here > https://dl.twrp.me/d2att/
2) I have the kot94h....NJ2 build number on my phone as I attempted root before, does this matter?
Click to expand...
Click to collapse
The twrp files that end in .tar are packaged to be flashed with Odin.
I never updated my i747 past NJ1, but I've not seen any discussion that NJ2 changed anything with respect to rooting on this phone. Just try the stable TWRP flashable supersu.zip.
My experience has been that even if rooting this way fails the worst thing that happens is your rom won't boot, so you pull the battery, boot back into recovery, restore a backup, and you're back up and running. I've never had rooting this way fail on the good old i747, only on newer phones with stock marshmallow.

jason2678 said:
The twrp files that end in .tar are packaged to be flashed with Odin.
I never updated my i747 past NJ1, but I've not seen any discussion that NJ2 changed anything with respect to rooting on this phone. Just try the stable TWRP flashable supersu.zip.
My experience has been that even if rooting this way fails the worst thing that happens is your rom won't boot, so you pull the battery, boot back into recovery, restore a backup, and you're back up and running. I've never had rooting this way fail on the good old i747, only on newer phones with stock marshmallow.
Click to expand...
Click to collapse
Thanks so much. I will do what you told me and report back. By the way, do all att s3's have unlocked bootloaders?, and how do you update the supersu binary?

Ulti2x said:
Thanks so much. I will do what you told me and report back. By the way, do all att s3's have unlocked bootloaders?, and how do you update the supersu binary?
Click to expand...
Click to collapse
The i747 and i747m were all unlocked by default. I'm pretty sure t999's are too.
Verizon's were locked. There was an unlock exploit for Verizon. Occasionally I read about someone trying it on an AT&T S3 and bricking it here.
I think supersu will pop up something on it's own if it is out of date, and retrieves what it needs from the Play store. It has been ages since I actually rooted stock on this phone. I vaguely remember Knox blocking root, supersu updating, rebooting a time or two then supersu eventually offering to disable Knox.

jason2678 said:
The i747 and i747m were all unlocked by default. I'm pretty sure t999's are too.
Verizon's were locked. There was an unlock exploit for Verizon. Occasionally I read about someone trying it on an AT&T S3 and bricking it here.
I think supersu will pop up something on it's own if it is out of date, and retrieves what it needs from the Play store. It has been ages since I actually rooted stock on this phone. I vaguely remember Knox blocking root, supersu updating, rebooting a time or two then supersu eventually offering to disable Knox.
Click to expand...
Click to collapse
I got backed up and successfully rooted. Thanks so much for the help. By the way, in logs and apps in supersu free it shows the loading circle forever, does that matter? I still have full root access to all apps.
EDIT: Turned out I needed a reboot to disable KNOX, you were right. Thanks for all your help jason!