Develop Bugs

Someone help me? Possibly bricked.

I have been trying to find an answer for the last several hours. But I can't seem to get anything to work.
I have the AT&T GS3 and I was able to flash AOKP but then I wanted to revert back to stock. I tried the toolkit and followed the steps and what might of happened is that AOKP did not get wiped completely when I flashed the stock image. Now after successfully flashing the stock image (I get the PASS! on Odin), my phone is stuck while booting. It goes past the AT&T boot image but gets stuck on "SAMSUNG". I tries flashing through ODIN, another downloaded version of the stock image but it didn't work. What am I doing wrong?

Another problem with being stuck in bootloop is that since I flashed the stock image; I think I no longer have CWM. I can't find a way to get to recovery.

I'm not really sure how to help but if you can get to the boot animations you aren't bricked. I know you're not on verizon but in this thread: http://forum.xda-developers.com/showthread.php?t=1759642 it says when coming from an AOSP rom back to the stock rom you have to flash a stock boot.img before flashing the stock rom. Hope you can get it working again

Did you make a nandroid backup before you flashed the Rom...if you did you can restore from cwm recovery...hold power, volume up, and home...after the screen goes black let go of the power...hope this helps
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

If you can get into download mode , just flash recovery from odin.
And how long have you waited at samsung logo , it might take few minutes to bootup.

I don't have CWM recovery. It got stuck on the Samsung logo for 20 minutes before I gave up and did a battery pull.
What do I flash through odin to get it working again. Which recovery file?

Ok, I just used the method described in this article and I am still stuck at the SAMSUNG logo.
http://www.androidegis.com/how-to/unbrcik-your-us-samsung-galaxy-s3-how-to/

http://forum.xda-developers.com/showthread.php?t=1727443
Tried that. Still same problem. Noticed that the boot-stock-att-sgh-i7.tar is only 10.5 mb. I don't know much about this, but is that tar file enough to get me unbricked?

usually the .tar file should be much larger than that. It's possible that the file you downloaded got corrupted. Try re downloading the file and than flashing it again.
Sent from my SCH-I535 using xda premium

If you look in the mediafire link inside ths artivle, you will notice that the download is only 10 mb
http://forum.xda-developers.com/showthread.php?t=1727443

try this
VJKotts said:
I have been trying to find an answer for the last several hours. But I can't seem to get anything to work.
I have the AT&T GS3 and I was able to flash AOKP but then I wanted to revert back to stock. I tried the toolkit and followed the steps and what might of happened is that AOKP did not get wiped completely when I flashed the stock image. Now after successfully flashing the stock image (I get the PASS! on Odin), my phone is stuck while booting. It goes past the AT&T boot image but gets stuck on "SAMSUNG". I tries flashing through ODIN, another downloaded version of the stock image but it didn't work. What am I doing wrong?
Click to expand...
Click to collapse
Get into download mode
clear cache option
factory reset phone option
That should fix it
CC

How do you factory reset/clear cache in download mode?

VJKotts said:
How do you factory reset/clear cache in download mode?
Click to expand...
Click to collapse
just re flash stock in odin flash Flash this file http://forum.xda-developers.com/showthread.php?t=1737848

[Q] Soft Bricked....can't unbrick or revert to stock rom...any thoughts?

I got a replacement GS3 through insurance and rooted it yesterday. Instead of flashing CWM I tried going with TWRP this time but didn't realize that TWRP doesn't read external SD cards and my roms were all saved on the external SD. And of course, this was after I wiped everything. So I tried unrooting and flashing back the stock firmware but it keeps failing in ODIN. So I tried re-rooting and flashing CWM which works but none of the roms will flash. I keep getting a system 7 error or something to that effect when I try flashing any rom. So now I can either get to recovery mode, or download mode. If I power the phone on it gets stuck on the Galaxy S3 screen. Any thoughts as to processes to try? Links? Threads? I've tried just about everything I could find.

kinjo1023 said:
I got a replacement GS3 through insurance and rooted it yesterday. Instead of flashing CWM I tried going with TWRP this time but didn't realize that TWRP doesn't read external SD cards and my roms were all saved on the external SD. And of course, this was after I wiped everything. So I tried unrooting and flashing back the stock firmware but it keeps failing in ODIN. So I tried re-rooting and flashing CWM which works but none of the roms will flash. I keep getting a system 7 error or something to that effect when I try flashing any rom. So now I can either get to recovery mode, or download mode. If I power the phone on it gets stuck on the Galaxy S3 screen. Any thoughts as to processes to try? Links? Threads? I've tried just about everything I could find.
Click to expand...
Click to collapse
Since when does TWRP not read external SD cards? It see's mine just fine, for well over a year. Where is your nandroid backup, you know the one you made before you did anything just incase it didn't go as planned? In any case you didn't give much information to help troubleshoot. 'I tried unrooting' - if you were going to flash a stock ROM there is no need to unroot anything as the stock firmware is just that, stock. How did it fail in ODIN? Did it say why it failed, what file were you trying to flash? More often than not the system 7 error is caused from an out of date recovery, normally i would tell you to start there but given the fact you admitted to just randomly attempting to flash things to the device you are going to want to start from stock. The second sticky thread in this sub-forum is where you should start reading, because based on your post you either need a refresher or never have read it to begin with.

dntesinfrno said:
Since when does TWRP not read external SD cards? It see's mine just fine, for well over a year. In any case you didn't give much information to help troubleshoot. 'I tried unrooting' - if you were going to flash a stock ROM there is no need to unroot anything as the stock firmware is just that, stock. How did if fail in ODIN? Did it say why it failed, what file were you trying to flash? More often than not the system 7 error is caused from an out of date recovery, normally i would tell you to start there but given the fact you admitted to just randomly attempting to flash things to device you are going to want to start from stock. http://forum.xda-developers.com/showthread.php?t=1725839
Click to expand...
Click to collapse
For whatever reason, TWRP wouldn't read my sd card. And when I said I tried unrooting - I just meant flashing back to the stock ROM. Odin fails when it gets to system write. It goes down a bunch of lines of code successfully but when it gets to system write, it fails every time. I've downloaded a few different stock ROM versions for AT&T and tried switching USB ports around my laptop. I've also tried a few different versions of ODIN but I'm not coming up with anything but a soft bricked phone still.

kinjo1023 said:
For whatever reason, TWRP wouldn't read my sd card. And when I said I tried unrooting - I just meant flashing back to the stock ROM. Odin fails when it gets to system write. It goes down a bunch of lines of code successfully but when it gets to system write, it fails every time. I've downloaded a few different stock ROM versions for AT&T and tried switching USB ports around my laptop. I've also tried a few different versions of ODIN but I'm not coming up with anything but a soft bricked phone still.
Click to expand...
Click to collapse
Did you have usb debugging enabled before you attempted to flash via ODIN? It sounds like it doesn't have permission to write to the /system partition. You can try doing a factory reset from recovery to get past the bootloader and make sure, or use Kies to flash to stock via this thread.

dntesinfrno said:
Did you have usb debugging enabled before you attempted to flash via ODIN? It sounds like it doesn't have permission to write to the /system partition. You can try doing a factory reset from recovery to get past the bootloader and make sure, or use Kies to flash to stock via this thread.
Click to expand...
Click to collapse
I could have swore I made sure to check before I started the process but I cant' check now because the phone won't boot. Can't flash back to stock. Can't flash any roms. I can get into download mode and recovery though. It's weird. I've reverted other phones back to stock plenty of times. It just keeps failing no matter what I do with this.

dntesinfrno said:
Did you have usb debugging enabled before you attempted to flash via ODIN? It sounds like it doesn't have permission to write to the /system partition. You can try doing a factory reset from recovery to get past the bootloader and make sure, or use Kies to flash to stock via this thread.
Click to expand...
Click to collapse
Here's another question for you, I've looked all over for the newest CWM in .tar format but everything comes in .img format. I can't use the .img in ODIN to flash to the phone and can't boot my phone to use the CWM app to flash. I suppose I could try TWRP again but when I flashed the first time - TWRP wouldn't read my EXT SD card.....

kinjo1023 said:
Here's another question for you, I've looked all over for the newest CWM in .tar format but everything comes in .img format. I can't use the .img in ODIN to flash to the phone and can't boot my phone to use the CWM app to flash. I suppose I could try TWRP again but when I flashed the first time - TWRP wouldn't read my EXT SD card.....
Click to expand...
Click to collapse
if you could wipe everything get on odin with 4.1.2 update reboot use cf root to root it (if you dont have root) after reboot download ROM Manager from Play Store install CWM recovery (easiest way to root) hope this works

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

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

Seriously Stuck!

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.